October 2009 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] user authorization with libzypp-3.27.3 (suse 10.3)
by Ingo Bremer 31 Oct '09

31 Oct '09

hello, i have a small question. since upgrade from opensuse 10.2 to 10.3 it's no longer possible to store passwords for nonanonymous access to repositories with yast permanently. (at least in my installation) i have the following rpm's installed: libzypp-3.27.3-0.1 zypper-0.8.26-0.1 yast2-2.15.58-12 a http://user:password@server/ notation in the baseurl of the repo-file has no effect, because this ist "optimized" away in RepoVariablesUrlReplacer::operator() from repo/RepoVariables.cc i have pached this as a workarround. a short look at newer source-code (libzypp-5.30.13 from opensuse 11.1) shows, that there are corresponding changes in this area. my question is, what is the official way in opensuse 10.3 to keep the passwords persistent? is it possible to merge a newer libzypp with this old installation? i.b. -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 1

[zypp-devel] Improving zypper dup
by Stephan Kulow 30 Oct '09

30 Oct '09

Hi, As we support now zypper dup as official distribution upgrade, there is one issue I would like to see solved: zypper dup leaving unsupported packages behind. There are 2 cases where it's obvious: - we dropped support for kfoobar as it will only crash with newer KDE, so it should be removed even if it it's still able to keep it for the solver - we have tons of old shared libraries that should be removed unless they are required by some package not from openSUSE (or that package is locked) Yast will get a list of such packages from control.xml, but zypper dup has no real access to that file and I don't want to maintain it twice actually. So I brainstormed with the two Michaels (one after the other :) and what came out of this was the following concept: The distribution algorithm will do the following before going into the solver: - check what installed packages provide products - estimate the update candidate (newest package with the same name) - of this package, check all provides with namespace weakremover (I'm open for suggestions on a better name :) - with this list of provides, create weak delete requests for all installed packages that match the name and the vendor of the package providing the product Means, openSUSE-release-11.1 is installed and provides product(openSUSE). Now zypper dup would update to openSUSE-release-11.2, but before it does that, it will check the weakremover provides of said openSUSE-release and weak delete gcc43 because openSUSE-release-11.2 provides weakremover(gcc43). Any better idea that can be implemented in a reasonable time? I know that this is kind of ugly, but I don't see any better solution atm. Putting things in the meta data is something that I see as too late now ;( Greetings, Stephan -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

10 30

[zypp-devel] Re: [yast-internal] Fwd: [Research] question on export function of yast2 "sw_single" module on SLES9
by Thomas Goettlicher 22 Oct '09

22 Oct '09

Hi Ladislav, some libzypp magic is used in yast2-qt-pkg to generate the xml file. I hope zypp guys can help you with an answer. Thomas zypp::syscontent::Writer writer; const zypp::ResPool & pool = zypp::getZYpp()->pool(); for_each( pool.begin(), pool.end(), boost::bind( &zypp::syscontent::Writer::addIf, boost::ref( writer ), _1 ) ); std::ofstream exportFile( toUTF8( filename ).c_str() ); exportFile.exceptions( std::ios_base::badbit | std::ios_base::failbit ); exportFile << writer; On Wednesday 21 October 2009 14:02:17 Ladislav Slezak wrote: > I don't know the details, forwarding to the yast mailing list... > > Thomas, Bubli? > > > -------- Original Message -------- > Subject: [Research] question on export function of yast2 "sw_single" > module on SLES9 Date: Tue, 20 Oct 2009 07:11:20 -0600 > From: Jeff R Christensen <jechristensen(a)novell.com> > Reply-To: research(a)suse.de > To: research(a)suse.de > > Hi All, > > I'm not sure that any one can readily help me with this question, but > wanted to through this out to the list of someone that may know. > > HP has asked me the following on behalf of one of their customers: > > ******************** > Customer is seeking syntax documentation of XML file created from File -> > Export in "yast2 sw_single". Customer has many SLES9 systems and now wants > to migrate to SLES11, but XML format of "user-packages.xml" is different > from SLES9 to SLES11. Customer uses this files/functionality for system > installations and recovery policies. > > But now ithe usage of "pattern" troubles the simple customization. So they > request if there s any way to force the system to export a list of packages > only. > ******************* > > What they are looking for is any documentation on the "sw_single" and how > it formats the XML that it produces. > > Is there such documentation on this and if so where might it be? > > > Thanks so much for any help you can give me. > > > Jeff R. Christensen > Advantage OS > Novell, Inc. -- Thomas Göttlicher - Software Engineer SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 - 90409 Nürnberg - Germany -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 2

[zypp-devel] yum 3.2.25 released
by Michael Schroeder 15 Oct '09

15 Oct '09

FYI: ----- Forwarded message from Seth Vidal <skvidal(a)fedoraproject.org> ----- > Yum 3.2.25 is now released. This release is almost entirely bugfixes > and translation updates but one significant feature was added. > > James added the 'yum history' feature: > > The history command allows the user to view what has happened in past > transactions (assuming the history_record config. option is set). You can > use info/list/summary to view what happened, undo/redo to act on that > information and new to start a new history file. > > The info/list/summary commands take either a transactions id or a package > (with wildcards, as in Specifying package names), all three can also be > passed no arguments. list can be passed the keyword "all" to list all the > transactions. undo/redo just take a transaction id. > > > Complete changelog here: > http://yum.baseurl.org/gitweb?p=yum.git;a=commitdiff;h=189975e534340195280d… > > Tarball: > http://yum.baseurl.org/download/3.2/yum-3.2.25.tar.gz > > Srpm: > http://yum.baseurl.org/download/3.2/yum-3.2.25-0.src.rpm Cheers, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 1

[zypp-devel] Q: Zypper solverTestCase handling
by Michael Andres 14 Oct '09

14 Oct '09

Hi. Fibonacci:~ # zypper up libzypp Loading repository data... Reading installed packages... Resolving package dependencies... The following packages are going to be upgraded: libzypp satsolver-tools 2 packages to upgrade. Overall download size: 2.1 MiB. After the operation, 1.0 KiB will be freed. Continue? [y/n/?] (y): n Fibonacci:~ # vs. Fibonacci:~ # zypper up --debug-solver libzypp Loading repository data... Reading installed packages... Resolving package dependencies... Generating solver test case... Solver test case generated successfully at /var/log/zypper.solverTestCase. Fibonacci:~ # a) Is it realy intended that --debug-solver does not perform the requested action, but stops after writing the testcase? b) What about a new key ('T') accepted by zyppers 'Continue?' and dependency problem prompt, that causes zypper to write out a testcase immediately. So one does not have to restart the whole action? Of course zypper should afterwards continue. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)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(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 2

[zypp-devel] PackageKit changes
by Duncan Mac-Vicar Prett 13 Oct '09

13 Oct '09

Hi, I did a quick review over PackageKit changes during the 0.4.x-0.5.x development period and what is our backend missing to adapt, or pending to enhance (because libzypp features). The first change, which can be done still for 11.2 (but not required), however it is required for a SP1 feature, is a one liner: change policy to download first and then install: How: When calling commit(), the ZYppCommitPolicy option passed should get the downloadMode() set to DownloadInHeaps or DownloadInAdvance See: http://svn.opensuse.org/autodocs/libzypp/HEAD/classzypp_1_1ZYppCommitPolicy… Appart of that, there are other changes; Multiple entries to WhatProvides and SearchFile http://lists.freedesktop.org/archives/packagekit/2009-September/005384.html Properties added, deprecated (should affect only bindings. I think the small glue used in kupdateapplet is not affected?): * GetActions * GetBackendDetail * GetFilters * GetGroups * GetMimeTypes http://lists.freedesktop.org/archives/packagekit/2009-September/005327.html New statuses, however our backend does not use them, may be the updater? should? + {PK_INFO_ENUM_PREPARING, "preparing"}, + {PK_INFO_ENUM_DECOMPRESSING, "decompressing"}, -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 2

[zypp-devel] Help needed for libzypp
by Dave Plater 13 Oct '09

13 Oct '09

Hi, I'm trying to get libzypp to not delete the /var/adm/mount/ temporary directory it uses when it downloads packages when retrying a download. This is to enable aria2c to use a partial download instead of starting from the beginning. I've used gdb to track down the creation of the directory in MediaHandler.cc but my time is limited and I would appreciate some help as to where the partially downloaded file is deleted on retry. Thanks Dave Plater -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 4

[zypp-devel] DownloadInAdvance bugs
by Dave Plater 08 Oct '09

08 Oct '09

Hi, I tried out the new DownloadInAdvance feature and have created :- https://bugzilla.novell.com/show_bug.cgi?id=545242 referring to zyppers handling of a skipped package. There is reference to another bug about zyppers inability to resume retried downloads and starting the download from the beginning again. Regards Dave P -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[zypp-devel] Commit download policy to use as default.
by Rastislav Krupanský 01 Oct '09

01 Oct '09

Hi. I've just updated libzypp to 6.17.2-9.6.i586, which already includes options for the ability to download all packages first and then install. Are they implemented and can we start testing all possibilities for YaST by editing /etc/zypp/zypp.conf? ## Commit download policy to use as default. ## ## DownloadOnly, Just download all packages to the local cache. ## Do not install. Implies a dry-run. ## ## DownloadInAdvance, First download all packages to the local cache. ## Then start to install. ## ## DownloadInHeaps, Similar to DownloadInAdvance, but try to split ## the transaction into heaps, where at the end of ## each heap a consistent system state is reached. ## ## DownloadAsNeeded Alternating download and install. Packages are ## cached just to avid CD/DVD hopping. This is the ## traditional behaviour. ## ## <UNSET> If a value is not set, empty or unknown, we pick ## some save default. ## ## commit.downloadMode = I just want to be sure. Thanks a lot. -- S pozdravom / Best regards, Rasto -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 1