Created attachment 331255 [details] debuginfo-install console log Description of problem: When upgrading debuginfo packages I noticed that debuginfo-install utility downloads not only the updates but also the already installed debuginfo packages. Then it simply discards the useless downloads. With the total download of 1.1 GiB it was a lot of waste. This always happens when I play with updates-testing. I like to crash the software, well not really :-), but it happens to me often, so I need to update debuginfo from time to time. Version-Release number of selected component (if applicable): yum-utils-1.1.19-1.fc10.noarch How reproducible: Easy, see the steps below. I guess it will be the same with any package as long as there was an upgrade from updates-testing or any other repo that is not enabled by default. Steps to Reproduce: 1. Say you have kde 4.1.4 installed. 2. Install debuginfo via # debuginfo-install kde* Now you have e.g. $ rpm -qa | grep kdepim-debuginfo kdepim-debuginfo-4.1.4-1.fc10.i386 3. Upgrade kde to 4.2 from upgrades-testing # yum --enablerepo=update-testing update kde* Probably restart is a necessary for kde 4.2 4. Now try to update debuginfo # debuginfo-install --enablerepo=update-testing kde* Actual results: Many already installed packages are downloaded and discarded afterwards. The goal is achieved but at twice the price (of time and bandwidth). Full console log attached. But see the interesting snippets (I chose the biggest package as an example): 1. Dependencies resolved: kdepim-debuginfo i386 6:4.1.4-1.fc10 updates-debuginfo 105 M kdepim-debuginfo i386 6:4.2.0-2.fc10 updates-testing-debuginfo 112 M 2. Downloading Packages: (110/111): kdepim-debuginfo-4.1.4-1.fc10.i386.rpm | 105 MB 01:34 (111/111): kdepim-debuginfo-4.2.0-2.fc10.i386.rpm | 112 MB 01:32 ------------------------------------------------------------------------------------------------------- Total 1.2 MB/s | 1.1 GB 15:53 3. Running Transaction Updating : kdepim-debuginfo 37/128 Cleanup : kdepim-debuginfo 115/128 4. Installed: kdepim-debuginfo.i386 6:4.1.4-1.fc10 Updated: kdepim-debuginfo.i386 6:4.2.0-2.fc10 5. rpm -qa | grep kdepim-debuginfo kdepim-debuginfo-4.2.0-2.fc10.i386 Expected results: Already installed packages are not downloaded, e.g. kdepim-debuginfo.i386 6:4.1.4-1.fc10 is not downloaded. Actually it was not installed as stated in point 4. but rather cleaned up. Additional info: debuginfo-install is said to find the respective packages by taking the name of nondebug package and adding -debuginfo to it. When using updates-testing, there can be two instances of the *-debuginfo packages: the one from fedora/updates repo and another one from updates-testing. My guess is that the debuginfo-install does not check that. It simply takes all matching debuginfo packages (e.g. kdepims-debuginfo-*.rpm) and set them for download and install. I would expect only those matching the latest versions (of kde in my case) installed will be downloaded and updated. I also miss the equivalent of update for debuginfo - update all already installed debuginfo packages.
what does "yum list kdepim" say?
[root@localhost ~]# yum list kdepim Loaded plugins: refresh-packagekit Installed Packages kdepim.x86_64 6:4.2.0-2.fc10 installed
I can't reproduce this on Fedora 10.x86_64. Can you post the output from a "debuginfo-install -d 9 kdepim"?
Created attachment 331344 [details] console log of actions that lead to the issue I can't either. On my x86_64 F10 the update seems to be OK. Strange. Well, the original report was from my i386 F10. I already updated kde*, but I can replicate the issue with ease on any almost package in updates-testing. This time I chose my victim to be xsane. This is a list of commands I used. # rpm -qa | grep xsane # debuginfo-install xsane* # yum --enablerepo=updates-testing update xsane* # debuginfo-install --enablerepo=updates-testing xsane* (said No this time) # rpm -qa | grep xsane # debuginfo-install -d 9 --enablerepo=updates-testing xsane* # rpm -qa | grep xsane Full output is be attached, I just point out interesting info below: # rpm -qa | grep xsane xsane-gimp-0.995-5.fc10.i386 xsane-0.995-5.fc10.i386 # debuginfo-install xsane* xsane-debuginfo i386 0.995-5.fc10 fedora-debuginfo 1.0 M ... Installed: xsane-debuginfo.i386 0:0.995-5.fc10 ... # yum --enablerepo=updates-testing update xsane* ======================================================== Package Arch Version Repository Size ======================================================== Updating: xsane i386 0.996-3.fc10 updates-testing 2.0 M xsane-gimp i386 0.996-3.fc10 updates-testing 258 k Transaction Summary ======================================================== Install 0 Package(s) Update 2 Package(s) Remove 0 Package(s) # debuginfo-install --enablerepo=updates-testing xsane* ======================================================================= Package Arch Version Repository Size ======================================================================= Installing: xsane-debuginfo i386 0.995-5.fc10 fedora-debuginfo 1.0 M Updating: xsane-debuginfo i386 0.996-3.fc10 updates-testing-debuginfo 1.0 M Transaction Summary ======================================================================= Install 1 Package(s) Update 1 Package(s) Remove 0 Package(s) And that is the problem. Why it wants to download xsane-debuginfo-0.995-5.fc10 when it is already there? A said No this time to check what I actually have: # rpm -qa | grep xsane xsane-debuginfo-0.995-5.fc10.i386 xsane-gimp-0.996-3.fc10.i386 xsane-0.996-3.fc10.i386 You see it, it is there. So what happens when I say Yes: # debuginfo-install -d 9 --enablerepo=updates-testing xsane* ... Downloading Packages: (1/2): xsane-debuginfo-0.995-5.fc10.i386.rpm | 1.0 MB 00:00 (2/2): xsane-debuginfo-0.996-3.fc10.i386.rpm | 1.0 MB 00:00 ------------------------------------------------------------------------- Total 1.2 MB/s | 2.1 MB 00:01 It downloaded both despite the fact I already have the older one. Installed: xsane-debuginfo.i386 0:0.995-5.fc10 Updated: xsane-debuginfo.i386 0:0.996-3.fc10 Really? Just check: # rpm -qa | grep xsane xsane-gimp-0.996-3.fc10.i386 xsane-debuginfo-0.996-3.fc10.i386 xsane-0.996-3.fc10.i386 No, not really. The 0.995-5 was actually removed, not installed. Tomorrow I check on x86_64 with the same package.
Ok, so you had: # rpm -qa | grep xsane xsane-gimp-0.995-5.fc10.i386 xsane-0.995-5.fc10.i386 ...then you had (implied): # rpm -qa | grep xsane xsane-debuginfo-0.995-5.fc10.i386 xsane-gimp-0.995-5.fc10.i386 xsane-0.995-5.fc10.i386 ...then you had: # rpm -qa | grep xsane xsane-debuginfo-0.995-5.fc10.i386 xsane-gimp-0.996-3.fc10.i386 xsane-0.996-3.fc10.i386 ...at which point, running: sudo debuginfo-install --enablerepo=updates-testing 'xsane*'" ...asks to download both the old and new versions of xsane-debuginfo. I can't reproduce this atm. all that happens is that xsane-debuginfo moves into the "Updating:" section ... although atm. there are 13 other packages it needs to satisfy deps. for xsane-debuginfo, so maybe that fixes it?
Ok, I can reproduce the problem now. If I have all of the deps. installed before the debuginfo-install it does what you say above: % sudo yum ls xsane\* Installed Packages xsane.x86_64 0.996-3.fc10 installed xsane-debuginfo.x86_64 0.995-5.fc10 installed xsane-gimp.x86_64 0.996-3.fc10 installed % sudo debuginfo-install --enablerepo=updates-testing xsane\* [...] Installing: xsane-debuginfo x86_64 0.995-5.fc10 fedora-debuginfo 1.1 M Updating: lcms-debuginfo x86_64 1.17-6.fc10 fedora-debuginfo 809 k xsane-debuginfo x86_64 0.996-3.fc10 updates-testing-debuginfo 1.1 M ...weird. In upstream yum-utils there is a yum-auto-update-debuginfo plugin, which will solve your problem in the "best" way. I'll hunt this down too though.
And after a couple of moments tought the problem seems obvious: % sudo debuginfo-install --enablerepo=updates-testing xsane xsane-debuginfo [...] Installing: xsane-debuginfo x86_64 0.995-5.fc10 fedora-debuginfo 1.1 M Updating: lcms-debuginfo x86_64 1.17-6.fc10 fedora-debuginfo 809 k xsane-debuginfo x86_64 0.996-3.fc10 updates-testing-debuginfo 1.1 M ...here we process "xsane" and that brings in xsane-debuginfo-0.996-3.fc10, and then we process "xsane-debuginfo-0.995-5.fc10" which has a base package of "xsane-0.995-5.fc10" which has a debuginfo of "xsane-debuginfo-0.995-5.fc10" ... which isn't installed anymore because the update just marked it as "removed". bah.
This works around this problem: commit 7e6d520d260165f20e5d889fc6438d0482814a38 Author: James Antill <james> Date: Mon Feb 9 14:38:23 2009 -0500 Simple hacky workaround for BZ 484603, debuginfo-install x x-debuginfo diff --git a/debuginfo-install.py b/debuginfo-install.py index 2dfc5b7..99cc177 100755 --- a/debuginfo-install.py +++ b/debuginfo-install.py @@ -84,6 +84,8 @@ class DebugInfoInstall(YumUtilBase): self.doTransaction() self.doUnlock() def di_try_install(self, po): + if po.name.endswith('-debuginfo'): # Wildcard matches produce this + return di_name = '%s-debuginfo' % po.name if self.pkgSack.searchNevra(name=di_name, arch=po.arch): test_name = di_name
Nice :-) Thank you. I reckon the yum-auto-update-debuginfo is exactly what I need.