mysql-client/universe was not superseded by mysql-client/main?

Bug #1842121 reported by Steve Langasek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

In processing removal of mysql-5.7 source from eoan, I was surprised to see that mysql-client
5.7.27-0ubuntu2 was in universe at the same time that mysql-client 8.0.16-0ubuntu3 was in main, both in the eoan release pocket.

I would normally expect the mysql-client binary from mysql-5.7 source package to have been superseded by mysql-client from mysql-8.0 source package when mysql-8.0 migrated to the release pocket, regardless of any difference in component (which there also really should not have been, they SHOULD have both been in main at the time the migration happened, but I haven't reviewed the history).

Both the old and new versions of the mysql-client package were Arch: all.

I wonder if this is related to Colin's recent work on fixing the race with multiple component overrides.

Revision history for this message
Colin Watson (cjwatson) wrote :

This is a long-standing property of the dominator, and not due to my recent changes. It happens any time multiple source packages in a suite build overlapping sets of binary packages.

Revision history for this message
Colin Watson (cjwatson) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.