Bug#1078469: On debian testing it was possible upgrade libgtk-4-common past libgtk-4-1

[Diane Trout]

On Sun, 2024-08-11 at 13:44 -0400, Jeremy Bícha wrote:
> On Sun, Aug 11, 2024 at 2:45 AM Diane Trout <diane at ghic.org> wrote:
> > It looks like apt wasn't wanting to install various t64 packages
> > with
> > apt upgrade.
> 
> I think you are requesting that libgtk-4-1 4.14 have something like:
> 
> Depends: libgtk-4-common (>= 4.14), libgtk-4-common (<< 4.15)

I can see where you're coming from with due to the C library is what's
depending on the common package.

Over in python packaging I regularly end up with dependencies that have
Breaks: some older version of a package that depends on the package
declaring the breaks. As an example python3-pandas heavily uses the
Breaks rules.

Using your example of the soname bump, I think this might work on the 
4.14 -common package.
Breaks: libgtk-4-1 (<< 4.14), libgtk-4-2 (<< 4.14)?

It may be too annoying to keep updated and so might still not be worth
doing.

> 
> The t64 transition was exceptionally disruptive. You need to do apt
> full/dist upgrades to get to the trixie side of the transition. You
> need to ensure that all packages are upgraded without anything left
> held back.

This part is very true, and I need to go do it, I was just wishing for
a stronger hint that I really needed to do a full-upgrade now.
(And also it took me a while to figure this out.)

Diane