On 30/06/2021 21.38, Paul Gevers wrote:
I prefer to update libgc in buster and document this behavior in the
release notes. As far as I'm aware, this is a "cosmetic" issue in that
after the upgrade where packages are hold back, a second upgrade fixes
the issue. If that view of the situation is incomplete, please enlighten
us. If that view is correct, lets fix bug 988963.
I hadn't considered fixing this in buster where it is not broken. ;-)
Will run some tests. This will probably fix this issue.
I would probably not remove the Conflicts, but downgrade it to a
Breaks: libgc1 (<< 1:8)
In case there is no further buster point release before bullseye, the
fix could be pushed to buster-updates s.t. it is available for the
oldstable-upgrade before the dist-upgrade, at least on sane systems.
Should be docuented in the release notes.
Andreas
