Hi Marvin,
2017-12-26 20:02 Marvin Renich:
Package: aptitude
Version: 0.8.10-1
Severity: normal
/var/log/aptitude shows the default architecture (e.g. amd64) when
logging actions pertaining to an architecture:all package, e.g.
[UPGRADE] console-setup:amd64 1.171 -> 1.172
should be
[UPGRADE] console-setup:all 1.171 -> 1.172
This is making it more difficult to write a script to back out of last N
updates using debsnap, because debsnap can download debs for a specific
architecture or all available architectures, but does not automatically
select an architecture:all deb when a specific architecture is requested
(reasonable behavior for debsnap).
In the extremely rare (I think) case where an upgrade (or downgrade)
replaces a specific architecture package with an architecture all
package, or vice versa, I would be okay with my script breaking because
it does not have enough information from /var/log/aptitude to get it
right. E.g. I think it is okay to arbitrarily choose one architecture
or the other, but I think it is more useful to know the architecture of
the package being replaced than that of the one being installed.
I wonder if it's because apt treats internally :all packages as the
native arch, but it doesn't make much sense, I think that the string
printed should still be :all.
This also happen in my system, e.g.:
[UPGRADE] ieee-data:amd64 20160613.1 -> 20171227.1
Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
