You are not logged in.
Pages: 1
Today I was going to update my system, but I noticed that the net upgrate size was about -1030MiB.
I found out trying all the packages listed, that when upgrading wine, the net upgrade size is -1031,89MiB, which looks like a lot to me.
I tried looking for information online, but I'm not finding anything, on the wineHQ website there is no mention of a refactor or debloat, so I thought it may be Arch-specific, I looked for an announcement or some information on the forum but I found no one talking about it. (I hope I didn't miss it if someone did)
Is this problematic or should I just upgrade anyway?
If this isn't a problem, I'm still curious about what may be causing this upstream, so if you have any information I'd happily accept it.
Offline
I reread a bit better, and it looks like there is a refactor on wineHQ, but I think I should already have it, because on the website it's listed for version 10.20, and in my system I have 10.20-1 at the moment, so upgrading to 10.20-2 I think it should make no effect?
I'm not sure if this is correct.
Offline
The difference is between 10.20-1 and 10.20-2. Upstream version in both cases is 10.20, so this is Arch-specific.
You can look into the history of changes for a package by clicking on "View Changes" on a package page.
Here is the change that is responsible for this:
https://gitlab.archlinux.org/archlinux/ … bd190523ad
You can read through these for more context:
https://gitlab.archlinux.org/archlinux/ … /issues/16
https://gitlab.winehq.org/wine/wine/-/m … uests/6715
Functionally the upgrade should be transparent, and that's why you didn't find any announcements about it.
I found out trying all the packages listed
You might want to look at the "VerbosePkgLists" option, it would tell you the size change for each package simultaneously.
Offline
Thanks!
I tried looking at the commit but I couldn't understand what it was actually changing, so I didn't know if it was that.
Apparently debug symbols are very heavy.
Also thanks for the pacman tip :)
Offline
I think this is due to the included PEstrip changes with the latest pacman version, see https://gitlab.archlinux.org/pacman/lib … type=heads ![]()
Offline
Pages: 1