Re: Tips for debugging/testing debian/control Depends/Breaks etc changes?
- To: Debian Developers <email@example.com>
- Subject: Re: Tips for debugging/testing debian/control Depends/Breaks etc changes?
- From: Otto Kekäläinen <firstname.lastname@example.org>
- Date: Mon, 5 Apr 2021 03:31:00 -0700
- Message-id: <[🔎] CAOU6tAByERJBNjVbtHzTPn401x_5NYdK7cWxMNEN171gfexENg@mail.gmail.com>
- In-reply-to: <20210331164012.gevwmagm63q2yc54@crossbow>
- References: <CAHj_TLD-5mnye4f1ZP31U-8x=QnrNKivyjbu+wg+brhbx1JhNw@mail.gmail.com> <20210326011346.vwfnmnbeyfzbtcum@crossbow> <CAHj_TLDuwR2HgN8V6Ar+f1brHkqPDCCKLs2Ka14kB=QpYFanVg@mail.gmail.com> <20210331164012.gevwmagm63q2yc54@crossbow>
> For me, this whole situation seems wrong though. Why do you have
> versioned package names (mariadb-server-*) when they are all mutually
> exclusive with one another due to all shipping the same binary?
This is how the MySQL packaging has been structured for the past 10
years or so. There was probably some use case that users wanted to
stick to a certain major release by installing e.g. 'mysql-server-5.1'
while installing 'mysql-server' would just auto-upgrade the major
version on dist-upgrade. I don't know for sure, this predates me by
I'd rather not start changing it now due to the potential unknown and
hard to revert consequences it could have to users.
I did however a couple years ago remove the versions from the plugin
package names, so the issue is at least limited to server and client
For the record, I solved the original issue already using the 'apt
install --with-source ./Packages -s' technique.