http://bugzilla.opensuse.org/show_bug.cgi?id=1192157 http://bugzilla.opensuse.org/show_bug.cgi?id=1192157#c4 --- Comment #4 from Jean Delvare <jdelvare@suse.com> --- (In reply to Michael Andres from comment #3)
@Jean: `zypper clean` will clear your package cache.
Yes, I'll do that eventually, but first I wanted to check what had been cached so far. 1.7 GB is a lot, and I couldn't see how downloaded-but-not-installed packages could amount for that much. Looking at what is actually in my cache : * sparse in repository OSS, date July 31st. I remember hitting a bug when trying to update that package (see bug #1188947). The cached package is the old version, I have the update installed already and locked to workaround the versioning issue. There's no reason why the old version would have been downloaded as I did not intend to install it, unless updates are fetched in advance without taking locks into account (or such a pre-fetch happened before I locked the package). But I don't remember exactly what I did back then, so I can't conclude. * libx265-199 and x265 in repository packman, date May 20th. I didn't do anything special with these packages, and can't remember any failure to install them either. I can confirm (from /var/log/zypp/history) that these specific packages have never been installed on my system, I have more recent versions installed since May 21st. Again that's too old for me to remember what I did exactly back then, but the only scenario I can think of is some kind of conflict at installation time. I'd be surprised though, as libx265 gets a new major version integrated in its name for every incompatible change, so multiple versions of libx265 can be installed in parallel, which makes conflicts virtually impossible. So that one is strange. * A lot of dxvk, wine-staging and wine-staging-32bit packages in repositories Emulators and Emulators:Wine, from March 12th to July 4th. Total weight 1.6 GB. I remember there were many updates of the wine-staging package at that time, even when no change was mentioned in the changelog. I see that Marcus Meissner made a change on July 10th to make builds "reproducible". If there's some pre-fetching in place, that would explain why many of these packages were cached. There may also have been failures to install some of the packages back then, I seem to recall some conflicts being reported. * Many small packages in the standard update repository. 9 from March 4th (all related to bind-utils, I can't remember what happened with that back then), and three dozens from November 1st, that is yesterday. But I did not attempt to install any update yesterday, so I have no idea why these packages are already in the cache. I suppose these packages would get deleted after installation if I'd run "zypper up" now. All in all, the presence of most of these files would be explained if available updates get pre-fetched somehow, but a more recent version becomes available by the time I actually install the updates. I was not aware of such a pre-fetching mechanism. Is the GNOME PackageKit front-end doing that? Or some systemd service? -- You are receiving this mail because: You are on the CC list for the bug.