Current File : //usr/lib/python2.7/site-packages/salt/states/pkgrepo.pyc
�
���^c @@ s� d Z d d l m Z m Z m Z d d l Z d d l m Z m Z d d l m
Z d d l Z
d d l Z
d d l Z
d d l Z
d d l Z
d d l m Z d � Z e d � Z d � Z d S(
u�
Management of APT/DNF/YUM/Zypper package repos
==============================================
States for managing software package repositories on Linux distros. Supported
package managers are APT, DNF, YUM and Zypper. Here is some example SLS:
.. code-block:: yaml
base:
pkgrepo.managed:
- humanname: CentOS-$releasever - Base
- mirrorlist: http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os
- comments:
- 'http://mirror.centos.org/centos/$releasever/os/$basearch/'
- gpgcheck: 1
- gpgkey: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
.. code-block:: yaml
base:
pkgrepo.managed:
- humanname: Logstash PPA
- name: deb http://ppa.launchpad.net/wolfnet/logstash/ubuntu precise main
- dist: precise
- file: /etc/apt/sources.list.d/logstash.list
- keyid: 28B04E4A
- keyserver: keyserver.ubuntu.com
- require_in:
- pkg: logstash
pkg.latest:
- name: logstash
- refresh: True
.. code-block:: yaml
base:
pkgrepo.managed:
- humanname: deb-multimedia
- name: deb http://www.deb-multimedia.org stable main
- file: /etc/apt/sources.list.d/deb-multimedia.list
- key_url: salt://deb-multimedia/files/marillat.pub
.. code-block:: yaml
base:
pkgrepo.managed:
- humanname: Google Chrome
- name: deb http://dl.google.com/linux/chrome/deb/ stable main
- dist: stable
- file: /etc/apt/sources.list.d/chrome-browser.list
- require_in:
- pkg: google-chrome-stable
- gpgcheck: 1
- key_url: https://dl-ssl.google.com/linux/linux_signing_key.pub
.. code-block:: yaml
base:
pkgrepo.managed:
- ppa: wolfnet/logstash
pkg.latest:
- name: logstash
- refresh: True
.. _bug: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1249080
.. note::
On Ubuntu systems, the ``python-software-properties`` package should be
installed for better support of PPA repositories. To check if this package
is installed, run ``dpkg -l python-software-properties``.
Also, some Ubuntu releases have a bug_ in their
``python-software-properties`` package, a missing dependency on pycurl, so
``python-pycurl`` will need to be manually installed if it is not present
once ``python-software-properties`` is installed.
On Ubuntu & Debian systems, the ``python-apt`` package is required to be
installed. To check if this package is installed, run ``dpkg -l python-apt``.
``python-apt`` will need to be manually installed if it is not present.
i ( t absolute_importt print_functiont unicode_literalsN( t CommandExecutionErrort SaltInvocationError( t STATE_INTERNAL_KEYWORDS( t sixc C@ s
d t k S( uI
Only load if modifying repos is available for this package type
u pkg.mod_repo( t __salt__( ( ( s7 /usr/lib/python2.7/site-packages/salt/states/pkgrepo.pyt __virtual__i s c K@ s| d | k r8 t j j j d d � | j d � | d <n i | d 6i d 6d8 d 6d d 6} d
t k r~ t | d <d | d <| Sd | k r� d
| k s� d | k r� t | d <d | d <n d | k r� d
| k s� d | k r� t | d <d | d <n d | k r#d | k r#t | d <d | d <n d | k rGt | d <d | d <| S| j d d8 � } | j d d8 � } | d8 k r�| d8 k r�t | d <d | d <| S| d8 k r�| d8 k r�t } n | } t d d@ k rj| d8 k r,y d j
d | f � } Wq,t k
r(d j
d t j
| � f � } q,Xn | d8 k rNt j j j | � n t j j j | � | d <n� t d dA k r�d | k r�| j d � | d <n d | k r�| | d <n | d8 k r�t j j j | � n t j j j | � | d <nN t d dB k rA| d8 k r%t j j j | � n t j j j | � | d <n x t D] } | j | d8 � qHWy& t d
| d# | j d$ d8 � �} Wn4 t k
r�} t | d <d% j | | � | d <| SXd& t k r�t d& d' | | � }
n | }
t d d( k rt j j j j | � } n | r| j d) d8 � |
j d) d8 � x�|
D]�} | | k r�| d k r�t d d k r�t j j j |
| � s�Pq�q�Pq�PqB| d* k r�t |
| � t | | � k r�Pq�qB| d+ k r�t d d( k r�|
| j � } t | d, � | d, )g | | j d- � D] } | j � ^ q \ }
} } |
j � }
t |
d, � |
d, )| |
k rpPn d. | k r�t j j j j | d. � } | | k r�Pq�q�qB| d. k rt d d k rt j j j j | | � } t j j j j |
| � } | | k r�Pq�qB| d/ k rR|
| rRt |
| � t | | � k r�Pq�qBt d dC k r�t d0 � |
| | | f D� � r�t j j j |
| � t j j j | | � k r�Pq�qBt j
|
| � t j
| | � k rBPqBqBWt | d <d1 j | � | d <| Sn t d2 r�d3 j | � | d <| r�xn |
D]U } |
j | � | j | � k r;i |
j | � d4 6| j | � d5 6| d | <q;q;Wn | | d d <| S| j d6 t � r�t j j j! | d) d7 � � Wd8 QXn y? t d d( k rt d9 | d: t" | �n t d9 | | � Wn4 t# k
rV} t | d <d; j | | � | d <| SXy� t d
| d# | j d$ d8 � �} | r�xq |
D]U } | j | � | j | � k r�i | j | � d4 6| j | � d5 6| d | <q�q�Wn i | d 6| d <t | d <d< j | � | d <Wn3 t# k
rI } t | d <d= j | | � | d <n X| d rx t$ j% t d> j& j' j d? d8 � n | S(D u�
This state manages software package repositories. Currently, :mod:`yum
<salt.modules.yumpkg>`, :mod:`apt <salt.modules.aptpkg>`, and :mod:`zypper
<salt.modules.zypper>` repositories are supported.
**YUM/DNF/ZYPPER-BASED SYSTEMS**
.. note::
One of ``baseurl`` or ``mirrorlist`` below is required. Additionally,
note that this state is not presently capable of managing more than one
repo in a single repo file, so each instance of this state will manage
a single repo file containing the configuration for a single repo.
name
This value will be used in two ways: Firstly, it will be the repo ID,
as seen in the entry in square brackets (e.g. ``[foo]``) for a given
repo. Secondly, it will be the name of the file as stored in
/etc/yum.repos.d (e.g. ``/etc/yum.repos.d/foo.conf``).
enabled : True
Whether or not the repo is enabled. Can be specified as True/False or
1/0.
disabled : False
Included to reduce confusion due to APT's use of the ``disabled``
argument. If this is passed for a YUM/DNF/Zypper-based distro, then the
reverse will be passed as ``enabled``. For example passing
``disabled=True`` will assume ``enabled=False``.
humanname
This is used as the "name" value in the repo file in
``/etc/yum.repos.d/`` (or ``/etc/zypp/repos.d`` for SUSE distros).
baseurl
The URL to a yum repository
mirrorlist
A URL which points to a file containing a collection of baseurls
comments
Sometimes you want to supply additional information, but not as
enabled configuration. Anything supplied for this list will be saved
in the repo configuration with a comment marker (#) in front.
gpgautoimport
Only valid for Zypper package manager. If set to True, automatically
trust and import public GPG key for the repository. The key should be
specified with ``gpgkey`` parameter. See details below.
Additional configuration values seen in YUM/DNF/Zypper repo files, such as
``gpgkey`` or ``gpgcheck``, will be used directly as key-value pairs.
For example:
.. code-block:: yaml
foo:
pkgrepo.managed:
- humanname: Personal repo for foo
- baseurl: https://mydomain.tld/repo/foo/$releasever/$basearch
- gpgkey: file:///etc/pki/rpm-gpg/foo-signing-key
- gpgcheck: 1
**APT-BASED SYSTEMS**
ppa
On Ubuntu, you can take advantage of Personal Package Archives on
Launchpad simply by specifying the user and archive name. The keyid
will be queried from launchpad and everything else is set
automatically. You can override any of the below settings by simply
setting them as you would normally. For example:
.. code-block:: yaml
logstash-ppa:
pkgrepo.managed:
- ppa: wolfnet/logstash
ppa_auth
For Ubuntu PPAs there can be private PPAs that require authentication
to access. For these PPAs the username/password can be passed as an
HTTP Basic style username/password combination.
.. code-block:: yaml
logstash-ppa:
pkgrepo.managed:
- ppa: wolfnet/logstash
- ppa_auth: username:password
name
On apt-based systems this must be the complete entry as it would be
seen in the sources.list file. This can have a limited subset of
components (i.e. 'main') which can be added/modified with the
``comps`` option.
.. code-block:: yaml
precise-repo:
pkgrepo.managed:
- name: deb http://us.archive.ubuntu.com/ubuntu precise main
.. note::
The above example is intended as a more readable way of configuring
the SLS, it is equivalent to the following:
.. code-block:: yaml
'deb http://us.archive.ubuntu.com/ubuntu precise main':
pkgrepo.managed
disabled : False
Toggles whether or not the repo is used for resolving dependencies
and/or installing packages.
enabled : True
Included to reduce confusion due to YUM/DNF/Zypper's use of the
``enabled`` argument. If this is passed for an APT-based distro, then
the reverse will be passed as ``disabled``. For example, passing
``enabled=False`` will assume ``disabled=False``.
architectures
On apt-based systems, architectures can restrict the available
architectures that the repository provides (e.g. only amd64).
architectures should be a comma-separated list.
comps
On apt-based systems, comps dictate the types of packages to be
installed from the repository (e.g. main, nonfree, ...). For
purposes of this, comps should be a comma-separated list.
file
The filename for the .list that the repository is configured in.
It is important to include the full-path AND make sure it is in
a directory that APT will look in when handling packages
dist
This dictates the release of the distro the packages should be built
for. (e.g. unstable). This option is rarely needed.
keyid
The KeyID or a list of KeyIDs of the GPG key to install.
This option also requires the ``keyserver`` option to be set.
keyserver
This is the name of the keyserver to retrieve gpg keys from. The
``keyid`` option must also be set for this option to work.
key_url
URL to retrieve a GPG key from. Allows the usage of ``http://``,
``https://`` as well as ``salt://``.
.. note::
Use either ``keyid``/``keyserver`` or ``key_url``, but not both.
key_text
The string representation of the GPG key to install.
.. versionadded:: 2018.3.0
.. note::
Use either ``keyid``/``keyserver``, ``key_url``, or ``key_text`` but
not more than one method.
consolidate : False
If set to ``True``, this will consolidate all sources definitions to the
sources.list file, cleanup the now unused files, consolidate components
(e.g. main) for the same URI, type, and architecture to a single line,
and finally remove comments from the sources.list file. The consolidate
will run every time the state is processed. The option only needs to be
set on one repo managed by salt to take effect.
clean_file : False
If set to ``True``, empty the file before config repo
.. note::
Use with care. This can be dangerous if multiple sources are
configured in the same file.
.. versionadded:: 2015.8.0
refresh : True
If set to ``False`` this will skip refreshing the apt package database
on debian based systems.
refresh_db : True
.. deprecated:: 2018.3.0
Use ``refresh`` instead.
require_in
Set this to a list of pkg.installed or pkg.latest to trigger the
running of apt-get update prior to attempting to install these
packages. Setting a require in the pkg state will not work for this.
u
refresh_dbu Neonu� The 'refresh_db' argument to 'pkg.mod_repo' has been renamed to 'refresh'. Support for using 'refresh_db' will be removed in the Neon release of Salt.u refreshu nameu changesu resultu u commentu pkg.get_repou0 Repo management not implemented on this platformu key_urlu keyidu keyserveru@ You may not use both "keyid"/"keyserver" and "key_url" argument.u key_textuA You may not use both "keyid"/"keyserver" and "key_text" argument.u7 You may not use both "key_url" and "key_text" argument.u repoue 'repo' is not a supported argument for this state. The 'name' argument is probably what was intended.u enabledu disabledu' Only one of enabled/disabled is allowedu osu Ubuntuu Mintu :u ppau os_familyu RedHatu Suseu humannameu NILinuxRTu Pokyt ppa_authu ppa_authu! Failed to examine repo '{0}': {1}u pkg.expand_repo_deft repou Debianu fileu compsu linei u #u commentsu
architecturesc s@ s | ] } t | t � Vq d S( N( t
isinstancet bool( t .0t x( ( s7 /usr/lib/python2.7/site-packages/salt/states/pkgrepo.pys <genexpr>� s u% Package repo '{0}' already configuredu testu� Package repo '{0}' would be configured. This may cause pkg states to behave differently than stated if this action is repeated without test=True, due to the differences in the configured repositories.u newu oldu
clean_fileu wNu pkg.mod_repot saltenvu# Failed to configure repo '{0}': {1}u Configured package repo '{0}'u+ Failed to confirm config of repo '{0}': {1}u test.pingu
pkg._avail( u Ubuntuu Mint( u RedHatu Suse( u NILinuxRTu Poky( u RedHatu Suse(( t saltt utilst versionst
warn_untilt popt NoneR t Falset Truet
__grains__t joint TypeErrorR t text_typet datat is_truet _STATE_INTERNAL_KEYWORDSt getR t formatt pkgt debt strip_urit sortedt splitt partitiont stript combine_commentst rpmt sett anyt __opts__t filest fopent __env__t Exceptiont syst modulest
__module__t __context__( t namet ppat kwargst rett enabledt disabledR
t kwargt pret exct sanitizedkwargst sanitizedsplitR t reposplitt _t pre_commentst
post_commentst precommentst
kwargcommentst post( ( s7 /usr/lib/python2.7/site-packages/salt/states/pkgrepo.pyt managedp s8 �
$
$
%"
" "
5
&
%
%
c @ s� i | d 6i d 6d d 6d d 6} d � k rl t d d k rl � j d � } | j d
� sl d
| } ql n t � f d � d! D� � } | r� d t k r� t | d <d | d <| Sy& t d | d � j d d � �} Wn4 t k
r} t | d <d j | | � | d <| SX| s6d j | � | d <t
| d <| St d rWd j | � | d <| Sy t d d | � � Wn1 t t f k
r�} t | d <| j
| d <| SXt d � } | | k rz| | d d <d j | � | d <| s�t
| d <q�y t d | � � } Wn< t t f k
rE} t | d <| d c d j | � 7<q�Xt
| d <| | d d <| d c d j | � 7<n t | d <d j | � | d <| S(" u�
This function deletes the specified repo on the system, if it exists. It
is essentially a wrapper around pkg.del_repo.
name
The name of the package repo, as it would be referred to when running
the regular package manager commands.
**UBUNTU-SPECIFIC OPTIONS**
ppa
On Ubuntu, you can take advantage of Personal Package Archives on
Launchpad simply by specifying the user and archive name.
.. code-block:: yaml
logstash-ppa:
pkgrepo.absent:
- ppa: wolfnet/logstash
ppa_auth
For Ubuntu PPAs there can be private PPAs that require authentication
to access. For these PPAs the username/password can be specified. This
is required for matching if the name format uses the ``ppa:`` specifier
and is private (requires username/password to access, which is encoded
in the URI).
.. code-block:: yaml
logstash-ppa:
pkgrepo.absent:
- ppa: wolfnet/logstash
- ppa_auth: username:password
keyid
If passed, then the GPG key corresponding to the passed KeyID will also
be removed.
keyid_ppa : False
If set to ``True``, the GPG key's ID will be looked up from
ppa.launchpad.net and removed, and the ``keyid`` argument will be
ignored.
.. note::
This option will be disregarded unless the ``ppa`` argument is
present.
u nameu changesu resultu u commentu ppau osu Ubuntuu Mintu ppa:c 3@ s$ | ] } � j | � d k Vq d S( N( R R ( R
R ( R7 ( s7 /usr/lib/python2.7/site-packages/salt/states/pkgrepo.pys <genexpr>Z s u keyidu keyid_ppau pkg.del_repo_keyu8 Repo key management is not implemented for this platformu pkg.get_repoR u ppa_authu# Failed to configure repo '{0}': {1}u Package repo {0} is absentu testu� Package repo '{0}' will be removed. This may cause pkg states to behave differently than stated if this action is repeated without test=True, due to the differences in the configured repositories.u pkg.del_repoR
u pkg.list_reposu repou Removed repo {0}u , but failed to remove key: {0}u , and keyid {0}u Failed to remove repo {0}N( u Ubuntuu Mint( u keyidu keyid_ppa( R R R t
startswithR+ R R R R R R R, R t strerror( R5 R7 R8 t
remove_keyR
R= t repost
removed_keyid( ( R7 s7 /usr/lib/python2.7/site-packages/salt/states/pkgrepo.pyt absent sh 0
( t __doc__t
__future__R R R R1 t salt.exceptionsR R t
salt.stateR R t salt.utils.dataR t salt.utils.filest salt.utils.pkg.debt salt.utils.pkg.rpmt salt.utils.versionst salt.extR R R RG RM ( ( ( s7 /usr/lib/python2.7/site-packages/salt/states/pkgrepo.pyt <module>V s � �
Mini Shell