[Bug 888919] New: When removing (not disabling) repositories, YaST should also remove their cache etc.
https://bugzilla.novell.com/show_bug.cgi?id=888919 https://bugzilla.novell.com/show_bug.cgi?id=888919#c0 Summary: When removing (not disabling) repositories, YaST should also remove their cache etc. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers@suse.de ReportedBy: antoine.mechelynck@belgacom.net QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 SeaMonkey/2.27a1 After removing repositories (already disabled) for earlier releases from the list of repositories known to YaST, I brought my HD from "0 bytes available" to "16 GiB available" by manually removing whatever concerned these obsolete versions in /var/cache/zypp/packages/. See details below. Reproducible: Always Steps to Reproduce: 0. You must have obsolete still-defined repositories which you will never use again. 1. Start up YaST 2. Select "Software → Software Repositories" 3. Select any obsolete repositories one by one, and "Delete" them. -- Note: There is no multi-select feature (no Ctrl-click) but this is only a minor annoyance and not the object of this bug. 4. OK, then close YaST. (We'll do the rest at a bash prompt.) 5. pushd /var/cache/zypp/packages 6. ls -lt 7. Identify the repositories which you just removed, and any ones removed previously and use them as operands to the "rm -Rv" command (without quotes of quotes). You may want to log the output. (by > or |tee, or by >> or |tee -a). 8. Have a look at all the files and directories deleted at step 8. Actual Results: Directory caches are not removed at steps 3-4 (by YaST) but only at step 7 (manually) Expected Results: YaST should already have removed them. Additional info: Of the directories removed at step 7, I noticed that some (the oldest ones) were empty, others weren't, and several (removed at step 3-4 immediately before) were extremely far from empty. As mentioned at top, my total win was 16 GiB of disk space, reducing /var/cache/zypp/packages/ from the biggest thing on my HD to almost nothing in comparison to e.g /root/. "Dataloss" can happen in any other application if, as was my case, failure to remove obsolete data causes the disk to become full. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=888919
https://bugzilla.novell.com/show_bug.cgi?id=888919#c
Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=888919
https://bugzilla.novell.com/show_bug.cgi?id=888919#c1
--- Comment #1 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=888919
https://bugzilla.novell.com/show_bug.cgi?id=888919#c2
--- Comment #2 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=888919
https://bugzilla.novell.com/show_bug.cgi?id=888919#c
Arvin Schnell
https://bugzilla.novell.com/show_bug.cgi?id=888919
https://bugzilla.novell.com/show_bug.cgi?id=888919#c3
Michael Andres
https://bugzilla.novell.com/show_bug.cgi?id=888919
https://bugzilla.novell.com/show_bug.cgi?id=888919#c4
--- Comment #4 from Tony Mechelynck
fixed in libzypp-13.8.4 Cleaning packages dir on repo remove and orphaned solv dirs on refresh.
*** This bug has been marked as a duplicate of bug 853065 ***
Hm, I'm skeptical. My current libzypp version is 13.10.2 and yet I won 16 GiB (which isn't nothing) by manually removing orphaned caches. (package dirs IIUC: orphaned subfolders of /var/cache/zyp/packages/). I cannot exclude the hypothesis that they had been left there by some version of YaST or zypper anterior to the fix; but then, shouldn't these two programs have realised that caches existed which did not correspond to any known repository, enabled or not? Hm, bug 853065 comment #1 says
…Obviously we do not remove the packages cached below /var/cache/zypp/packages,… The reason is not "obvious" to me, and these (with one subdirectory of …/packages per repo) were exactly those I removed manually, for a total of 16 GiB.
Is that "obviousness" still there, and can someone explain it to me? (use direct email if you think that "spamming the bug" would be off-topic). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=888919
https://bugzilla.novell.com/show_bug.cgi?id=888919#c5
--- Comment #5 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=888919
https://bugzilla.novell.com/show_bug.cgi?id=888919#c6
Michael Andres
Hm, I'm skeptical.
You are right, excuse my inattentiveness. #853065 does not remove 'orphaned' package caches, just the repos cache upon deletion. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=888919
https://bugzilla.novell.com/show_bug.cgi?id=888919#c7
Michael Andres
https://bugzilla.novell.com/show_bug.cgi?id=888919
https://bugzilla.novell.com/show_bug.cgi?id=888919#c8
--- Comment #8 from Tony Mechelynck
fixed with linzypp-13.10.4
Thanks a lot, Michael. :-) I suppose that this fix will be included in openSUSE 13.2. Do you think it is possible to port it back to one of the upcoming Online Updates for 13.1? Here are my reasons: - This fix may seem to be only an "enhancement" to a developer, but to a user whose HD is almost full, freeing tens of GiB at one stroke can make the difference between life and death; - I have found that for me (who live in Brussels), the most practical way to get the openSUSE DVD is at the SUSE stand at FOSDEM (software shops here don't sell Linux anymore because "you can't make a decent profit margin on something which can be downloaded for free"); however, FOSDEM happens once a year but there is a new release every 8 months, so I "miss" one release in every three; when I'll get the 3.2 release it'll already be 3 months old. In the meantime I apply, as I see them, the Online Updates for the release I have. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=888919
https://bugzilla.novell.com/show_bug.cgi?id=888919#c9
--- Comment #9 from Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com