[zypp-devel] Re: [opensuse] zypper - ignore vendors & download first
Hi, Sylvester Lykkehus wrote:
Hi list,
I've skipped using the built in software management in openSUSE for the past 3-4 releases, as I have been using the 'smart package manager' to do my updates and even dist upgrades.
I have had my eyes on libzypp for a while, for it's great performance compared to smart.
Glad to read this :O)
I have 2 questions for libzypp and the zypper commandline tool:
1. Is there any way to completely and forcefully disable the vendor check ? I now that I can add trusted vendors to the list, but that is not my objective. I rely on the repo priority, and do not wish to use the vendor check feature of libzypp.
None that i know of. CCing to zypp-devel mailing list.
2. 'Download first - install after' behavior. I remember someone mentioning a 'secret' unsupported option or configuration for zypp to start installation, only after/if all packages have been downloaded first. I just don't remember what it was.
--dry-run with keeppackages turned on. It wasn't really secret, but i admit even i (one of zypp(er) developers) did not get the idea of using it for this purpose :O) Josef did. He already posted the link in the other mail, but here it is again: http://lizards.opensuse.org/2008/10/30/how-survive-zypper-dup-on-system-with... -- 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)---
On Friday 22 May 2009 18:03:29 Jano Kupec wrote:
I have 2 questions for libzypp and the zypper commandline tool:
1. Is there any way to completely and forcefully disable the vendor check ? I now that I can add trusted vendors to the list, but that is not my objective. I rely on the repo priority, and do not wish to use the vendor check feature of libzypp.
None that i know of. CCing to zypp-devel mailing list.
We can have a zypp.conf option for this. That should not be a big deal.
2. 'Download first - install after' behavior. I remember someone mentioning a 'secret' unsupported option or configuration for zypp to start installation, only after/if all packages have been downloaded first. I just don't remember what it was.
We will have better support for this in the next release. 'Download first' or 'Download only' will be doable without a bunch of cryptic options. -- 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
2009/5/25 Michael Andres
On Friday 22 May 2009 18:03:29 Jano Kupec wrote:
I have 2 questions for libzypp and the zypper commandline tool:
1. Is there any way to completely and forcefully disable the vendor check ? I now that I can add trusted vendors to the list, but that is not my objective. I rely on the repo priority, and do not wish to use the vendor check feature of libzypp.
None that i know of. CCing to zypp-devel mailing list.
We can have a zypp.conf option for this. That should not be a big deal.
Any news about the plugin system? That should allow to change all these options, shouldn't? Looking into the log there are a lot of options, I'm not sure about the meaning of some of them: fixsystem = 0 allowdowngrade = 1 allowarchchange = 1 allowvendorchange = 1 allowuninstall = 0 updatesystem = 1 allowvirtualconflicts = 0 noupdateprovide = 0 dosplitprovides = 1 onlyRequires = 0 ignorealreadyrecommended = 0 distupgrade = 1 distupgrade_removeunsupported = 0 Each user wants something different. Using zypper since 11.0, what I miss the most right now is a dist-upgrade *with* vendor check (or an update allowing downgrades). Why? Well, the KDE OBS repos sometimes (...frequently!!) have updates with a lower version-release number. To update to the latest packages I need an update method that allows downgrades, dist-upgrade does it just fine... but, since it ignores the vendor, at the same time it updates my KDE it also changes my Packman K3B package for other without MP3 support (plus the more esoteric libsndfile case from bug #500407).
2. 'Download first - install after' behavior. I remember someone mentioning a 'secret' unsupported option or configuration for zypp to start installation, only after/if all packages have been downloaded first. I just don't remember what it was.
We will have better support for this in the next release. 'Download first' or 'Download only' will be doable without a bunch of cryptic options.
When 'Download first', will a file colision check be done before starting the installation? (rpm without --replacefiles). It would be something good to have... but would also mean one method would allow installations the other would not. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Cristian Morales Vega wrote:
2009/5/25 Michael Andres
: On Friday 22 May 2009 18:03:29 Jano Kupec wrote:
I have 2 questions for libzypp and the zypper commandline tool:
1. Is there any way to completely and forcefully disable the vendor check ? I now that I can add trusted vendors to the list, but that is not my objective. I rely on the repo priority, and do not wish to use the vendor check feature of libzypp. None that i know of. CCing to zypp-devel mailing list. We can have a zypp.conf option for this. That should not be a big deal.
Any news about the plugin system?
Which plugin system?
That should allow to change all these options, shouldn't? Looking into the log there are a lot of options, I'm not sure about the meaning of some of them:
fixsystem = 0 allowdowngrade = 1 allowarchchange = 1 allowvendorchange = 1 allowuninstall = 0 updatesystem = 1 allowvirtualconflicts = 0 noupdateprovide = 0 dosplitprovides = 1 onlyRequires = 0 ignorealreadyrecommended = 0 distupgrade = 1 distupgrade_removeunsupported = 0
These are solver settings and are either configurable via zypp.conf, or passed to libzypp/satsolver by UIs according to commands the user does. E.g. updatesystem = 1 is set by 'zypper up', onlyRequires is set in zypp.conf, or by 'zypper <command> --no-recommends', etc. Some of them are not exposed to UIs yet. If you're curious about some particular things you see in the logs, just ask. They're not always really understandable for a casual observer (in fact sometimes it would help to make them more understandable) :O)
Each user wants something different. Using zypper since 11.0, what I miss the most right now is a dist-upgrade *with* vendor check (or an update allowing downgrades). Why? Well, the KDE OBS repos sometimes (...frequently!!) have updates with a lower version-release number. To update to the latest packages I need an update method that allows downgrades, dist-upgrade does it just fine... but, since it ignores the vendor, at the same time it updates my KDE it also changes my Packman K3B package for other without MP3 support (plus the more esoteric libsndfile case from bug #500407).
2. 'Download first - install after' behavior. I remember someone mentioning a 'secret' unsupported option or configuration for zypp to start installation, only after/if all packages have been downloaded first. I just don't remember what it was. We will have better support for this in the next release. 'Download first' or 'Download only' will be doable without a bunch of cryptic options.
When 'Download first', will a file colision check be done before starting the installation? (rpm without --replacefiles). It would be something good to have... but would also mean one method would allow installations the other would not.
-- 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)---
2009/5/25 Jano Kupec
Cristian Morales Vega wrote:
2009/5/25 Michael Andres
: On Friday 22 May 2009 18:03:29 Jano Kupec wrote:
I have 2 questions for libzypp and the zypper commandline tool:
1. Is there any way to completely and forcefully disable the vendor check ? I now that I can add trusted vendors to the list, but that is not my objective. I rely on the repo priority, and do not wish to use the vendor check feature of libzypp. None that i know of. CCing to zypp-devel mailing list. We can have a zypp.conf option for this. That should not be a big deal.
Any news about the plugin system?
Which plugin system?
From time to time I have read about it... never anything very specific. Searching "plugin" in the zypp ML archive I just found http://lists.opensuse.org/zypp-devel/2008-07/msg00030.html When reading these things I always though about something like yum plugins, even if I don't really know exactly what yum plugins offer... -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Monday 25 May 2009 10:23:59 Michael Andres wrote:
I have 2 questions for libzypp and the zypper commandline tool:
1. Is there any way to completely and forcefully disable the vendor check ? I now that I can add trusted vendors to the list, but that is not my objective. I rely on the repo priority, and do not wish to use the vendor check feature of libzypp.
None that i know of. CCing to zypp-devel mailing list.
We can have a zypp.conf option for this. That should not be a big deal.
JFYI: Will be available in libzypp-6.6.0. ## ## EXPERTS ONLY: Per default the solver will not replace packages of ## different vendors, unless you explicitly ask to do so. Setting this ## option to TRUE will disable this vendor check (unless the application ## explicitly re-enables it). Packages will then be considered based on ## repository priority and version only. This may easily damage your system. ## ## CHANGING THE DEFAULT IS NOT RECOMMENDED. ## ## Valid values: boolean ## Default value: false ## # solver.allowVendorChange = false -- 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)
-
Cristian Morales Vega
-
Jano Kupec
-
Michael Andres