[zypp-devel] zypper: Excluding packages from a repo
Hi, this may be obvious, but I didn't find anything when I searched the zypper man page for "exclude" or "ignore". How do I exclude a certain package from a repo that I am subscribed to so that it doesn't update a package that I have on my system? I imported the following repo file into zypper, which works with yum: -# cat Application:Geo.repo [Application_Geo] name=Applications related to the earth (GIS, Mapping, geodesy, GPS) (openSUSE_11.0) type=rpm-md baseurl=http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.0/ gpgcheck=1 gpgkey=http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.0/rep... enabled=1 exclude=autoconf <---------- The same exclude line put into the .repo file in /etc/zypp/repos.d doesn't have any effect. On a related note, I have also looked for something like --exclude on the commandline, but to no avail. I am aware of the way to give package names as arguments to zypper, with and without wildcards, and that works fine for me, but sometimes an exclude on the commandline is useful as well. Thanks, Peter -- Contact: admin@opensuse.org (a.k.a. ftpadmin@suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter Poeml wrote:
Hi,
this may be obvious, but I didn't find anything when I searched the zypper man page for "exclude" or "ignore".
How do I exclude a certain package from a repo that I am subscribed to so that it doesn't update a package that I have on my system?
I imported the following repo file into zypper, which works with yum:
-# cat Application:Geo.repo [Application_Geo] name=Applications related to the earth (GIS, Mapping, geodesy, GPS) (openSUSE_11.0) type=rpm-md baseurl=http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.0/ gpgcheck=1 gpgkey=http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.0/rep... enabled=1 exclude=autoconf <----------
The same exclude line put into the .repo file in /etc/zypp/repos.d doesn't have any effect.
Libzypp does not support this AFAIK. To avoid installing/upgrading/removing of some package, lock it: $ zypper addlock foo this will add the lock to /etc/zypp/locks, see also 'man locks'
On a related note, I have also looked for something like --exclude on the commandline, but to no avail. I am aware of the way to give package names as arguments to zypper, with and without wildcards, and that works fine for me, but sometimes an exclude on the commandline is useful as well.
Hmm.. right, there's nothing like that available in zypper. Once you use a wildcard, it will consider all matches. Yeah, i guess it might be useful to be able to exlcude some of the matches. Could you please file an enhancement request in bugzilla? (I'll probably close it as wontfix :O) but don't worry, it'll be still alive in http://en.opensuse.org/Zypper/Bugs_For_Adoption ... which reminds me i should advertise the page a bit :O) - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz - ---------------------------------------------------------(EOF)--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkmaomYACgkQgEhGpmN+6QHnUQCghBJVJKej0dpK5BcBwSRtRyIM iMUAnj1rfGRZyCyM4hw8jmK7DaJwIy59 =l1Ye -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Hi Jano, On Tue, Feb 17, 2009 at 12:41:26PM +0100, Jan Kupec wrote:
this may be obvious, but I didn't find anything when I searched the zypper man page for "exclude" or "ignore".
How do I exclude a certain package from a repo that I am subscribed to so that it doesn't update a package that I have on my system?
I imported the following repo file into zypper, which works with yum:
-# cat Application:Geo.repo [Application_Geo] name=Applications related to the earth (GIS, Mapping, geodesy, GPS) (openSUSE_11.0) type=rpm-md baseurl=http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.0/ gpgcheck=1 gpgkey=http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.0/rep... enabled=1 exclude=autoconf <----------
The same exclude line put into the .repo file in /etc/zypp/repos.d doesn't have any effect.
Libzypp does not support this AFAIK. To avoid installing/upgrading/removing of some package, lock it:
$ zypper addlock foo
This sounds as if updates of the package are totally blocked then. Is that the case? I don't want to avoid installing/upgrading/removing of the package. It would be wrong to block regular updates to the package (which would concern me).
this will add the lock to /etc/zypp/locks, see also 'man locks'
I also looked into that man page yesterday, because it is linked from the zypper man page, but I have to admit that I don't understand a word. Too abstract for me. :-( On a related note, I miss a feature similar to "exclude" which comes in very handy. Practically the opposite of "exclude", and I use it rather often. It's called includepkgs in yum.conf speak (see http://linux.die.net/man/5/yum.conf) and its purpose is that it lets me ignore all but (a) certain package(s) from a repository. For instance, when I want to get (and update) some tool from network:utilities, but I don't want a pcap library that happens to be there (no thanks!).
On a related note, I have also looked for something like --exclude on the commandline, but to no avail. I am aware of the way to give package names as arguments to zypper, with and without wildcards, and that works fine for me, but sometimes an exclude on the commandline is useful as well.
Hmm.. right, there's nothing like that available in zypper. Once you use a wildcard, it will consider all matches. Yeah, i guess it might be useful to be able to exlcude some of the matches. Could you please file an enhancement request in bugzilla? (I'll probably close it as wontfix :O) but don't worry, it'll be still alive in http://en.opensuse.org/Zypper/Bugs_For_Adoption ... which reminds me i should advertise the page a bit :O)
Shouldn't we rather add FATE or openFATE requests for these features? These are important features in my view on the way to make zypper usable for admins. (Yes, it is getting there :-) I am currently running yum and zypper aside on some machines, closely comparing and validating what's happening. And I can say, there are quite some things that work pleasantly already. Very happy that I can finally keep old kernels, for instance.) Thanks, Peter -- Contact: admin@opensuse.org (a.k.a. ftpadmin@suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter Poeml wrote:
Hi Jano,
On Tue, Feb 17, 2009 at 12:41:26PM +0100, Jan Kupec wrote:
this may be obvious, but I didn't find anything when I searched the zypper man page for "exclude" or "ignore".
How do I exclude a certain package from a repo that I am subscribed to so that it doesn't update a package that I have on my system?
I imported the following repo file into zypper, which works with yum:
-# cat Application:Geo.repo [Application_Geo] name=Applications related to the earth (GIS, Mapping, geodesy, GPS) (openSUSE_11.0) type=rpm-md baseurl=http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.0/ gpgcheck=1 gpgkey=http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.0/rep... enabled=1 exclude=autoconf <----------
The same exclude line put into the .repo file in /etc/zypp/repos.d doesn't have any effect. Libzypp does not support this AFAIK. To avoid installing/upgrading/removing of some package, lock it:
$ zypper addlock foo
This sounds as if updates of the package are totally blocked then. Is that the case? I don't want to avoid installing/upgrading/removing of the package. It would be wrong to block regular updates to the package (which would concern me).
this will add the lock to /etc/zypp/locks, see also 'man locks'
I also looked into that man page yesterday, because it is linked from the zypper man page, but I have to admit that I don't understand a word. Too abstract for me. :-(
On a related note, I miss a feature similar to "exclude" which comes in very handy. Practically the opposite of "exclude", and I use it rather often. It's called includepkgs in yum.conf speak (see http://linux.die.net/man/5/yum.conf) and its purpose is that it lets me ignore all but (a) certain package(s) from a repository. For instance, when I want to get (and update) some tool from network:utilities, but I don't want a pcap library that happens to be there (no thanks!).
On a related note, I have also looked for something like --exclude on the commandline, but to no avail. I am aware of the way to give package names as arguments to zypper, with and without wildcards, and that works fine for me, but sometimes an exclude on the commandline is useful as well. Hmm.. right, there's nothing like that available in zypper. Once you use a wildcard, it will consider all matches. Yeah, i guess it might be useful to be able to exlcude some of the matches. Could you please file an enhancement request in bugzilla? (I'll probably close it as wontfix :O) but don't worry, it'll be still alive in http://en.opensuse.org/Zypper/Bugs_For_Adoption ... which reminds me i should advertise the page a bit :O)
Shouldn't we rather add FATE or openFATE requests for these features?
It should not be hard to do, so bugzilla would be more appropriate - just so that i don't forget about it. It does not matter whether you choose FATE or bugzilla after all - we'll put it to FATE anyway, if it's not trivial amount of work.
These are important features in my view on the way to make zypper usable for admins.
OK, you convinced me :O)
(Yes, it is getting there :-) I am currently running yum and zypper aside on some machines, closely comparing and validating what's happening. And I can say, there are quite some things that work pleasantly already. Very happy that I can finally keep old kernels, for instance.)
That's good! :O) - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz - ---------------------------------------------------------(EOF)--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkmartIACgkQgEhGpmN+6QGf0ACfZh7ZHlN12gLVSNWBtU1R8XRz Eg0AniUnMw9q4OcQ8Uf/Ln5S88+O42Tj =PisP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter Poeml wrote:
this will add the lock to /etc/zypp/locks, see also 'man locks'
I also looked into that man page yesterday, because it is linked from the zypper man page, but I have to admit that I don't understand a word. Too abstract for me. :-(
Hm.. you're right, the man page deserves improvements. At least the description. I'll take a look at it, while Pepa will learn english :O)) - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz - ---------------------------------------------------------(EOF)--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkmar7EACgkQgEhGpmN+6QFfzACfQh4lz5rC/b7GnhGy+zwVQB0z OqIAniLRfTjGyqqndlxhEdIkWv4UoqMd =BL8d -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Tuesday 17 February 2009 13:23:54 Peter Poeml wrote:
$ zypper addlock foo
This sounds as if updates of the package are totally blocked then. Is that the case? I don't want to avoid installing/upgrading/removing of the package. It would be wrong to block regular updates to the package (which would concern me).
this will add the lock to /etc/zypp/locks, see also 'man locks'
I also looked into that man page yesterday, because it is linked from the zypper man page, but I have to admit that I don't understand a word. Too abstract for me. :-(
Basically the locks file contains a set of serialized queries. All items the query matches get locked.
On a related note, I miss a feature similar to "exclude" which comes in very handy. Practically the opposite of "exclude", and I use it rather often. It's called includepkgs in yum.conf speak (see http://linux.die.net/man/5/yum.conf) and its purpose is that it lets me ignore all but (a) certain package(s) from a repository. For instance, when I want to get (and update) some tool from network:utilities, but I don't want a pcap library that happens to be there (no thanks!).
For this we had to enhance the queries to support a "NOT". -----lock----- repo: network:utilities solvable_name: NOT some_tool -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
participants (3)
-
Jan Kupec -
Michael Andres -
Peter Poeml