Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #342237 > unrolled thread

Bug#1035949: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed

Back to article view | Back to linux.debian.bugs.rc

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1035949: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed Andreas Beckmann <anbe@debian.org> - 2023-05-15 13:30 +0200
    Bug#1035949: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed Andreas Beckmann <anbe@debian.org> - 2023-05-23 00:40 +0200
      Bug#1035949: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed Otto Kekäläinen <otto@debian.org> - 2023-05-26 19:30 +0200
        Bug#1035949: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed Otto Kekäläinen <otto@debian.org> - 2023-06-03 21:30 +0200
          Bug#1035949: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed Otto Kekäläinen <otto@debian.org> - 2023-06-04 07:10 +0200

#342237 — Bug#1035949: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed

On 15/05/2023 02.38, Otto Kekäläinen wrote:
> This is not a fix, but could help make the situation easier to
> detect/debug for users:

I haven't tried that and have no time to do it right now: if you first 
upgrade apt to the bookworm version, and do the dist-upgrade afterwards, 
does that change the removal order?

Anyway you should file a bug against apt, perhaps they have some insight 
what's happening and how it could be worked around in bookworm. 
Unfortunately the upgrades have to work with apt from bullseye ...


Andreas

[toc] | [next] | [standalone]

#342526

On 18/05/2023 05.17, Otto Kekäläinen wrote:
> I am not sure what to debug next.

You could try to reintroduce mariadb-client-10.5 as a transitional 
package depending on mariadb-client (>= 1:10.11) (and make existing 
Conflicts/Breaks/Replaces against mariadb-client-10.5 versioned as (<< 
1:10.11))

Andreas

[toc] | [prev] | [next] | [standalone]

#342685

I filed now https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/47
as an exploration to fix this issue.

If we don't fix this in 10.11 the alternative would be to patch 10.5
and 10.3 to simply never fail on missing mariadb-client-10.3/5
package. I already did
https://salsa.debian.org/mariadb-team/mariadb-10.5/-/merge_requests/14
to make the problem have a proper error message users.

[toc] | [prev] | [next] | [standalone]

#342883

I adjusted your patch a bit as it didn't apply cleanly and pushed it
to https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/47
to replace the transitional mariadb-client-10.5 I had earlier.

Thanks for diving deep in piuparts testing for MariaDB 10.11 and for the patch!

Ideally the CI itself had all the install/upgrade scenarios that are
relevant. Contributions to the debian/salsa-ci.yml file are also very
welcome!

[toc] | [prev] | [next] | [standalone]

#342884

Indeed the transitional mariadb-server-10.5 fixes the issue.

What do you Andreas suggest we do now?

It is already past freeze for Bookworm, and this is not just a small
fix but also introduces a new package (albeit transitional). Let me
know how you want to proceed and I can immediately tomorrow push this
to experimental or unstable if that is aligned with your plan.
Alternatively we can ask for pre-approval from the release team.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.rc

csiph-web