tags 893156 - moreinfo reopen 893156 Hello!
> Please elaborate why you can't revert all the changes to 10.1.28-2 and > then upload that as 1:10.1.29+really10.1.28-1 until you are ready to > upload 10.1.29 again? Failing that, you will also need to really justify > why you cannot bump the epoch again. The epoch was introduced by another DD who uploaded a very bad 10.2 and then used the epoch to downgrade the package back to 10.1. Such use of the epoch is not what the policy states as valid use cases for the epoch (https://www.debian.org/doc/debian-policy/#version) and the policy in particular forbids 'silly orderings' which this now is. Such a change was done in a panic by the other DD and without thinking of the consequences. This will result in wide spread breakage when apt starts to upgrade all previous 10.1, 10.2 and 10.3 installs into this 1:10.1 version as I explained in my first mail. I tried my best to be very elaborate in the first mail. If the epoch isn't removed, then somebody needs to fix the world around us and introduce the epoch in all previous and future packages of any 10.1+ MariaDB in any repository out there. Coordinating such a thing is too much work for me, sorry. I don't want to accept the situation that this single change done by one DD is completely irreversible with the cost that everybody else in the world need to do a lot of work and adapt to it. At that point I'd rather give up and let somebody else deal with the fallout. > Manually modifying dak's records to fix his is, err, unlikely to happen. Yes, I know, but I have to try. I feel I should try to do something to save this package after this "sabotage" and not directly orphan it. Thanks for the polite answer, - Otto
