On Sun, Mar 11, 2018 at 12:54 PM, Otto Kekäläinen <[email protected]> wrote: > Yes, it is better to have a newer version, but that will not remove > the epoch thing, all the those epoch related problems will remain. The > package is from my point of view now sabotaged and I cannot fix it > because of the epoch.
Ok, I see. But why can't you just add the epoch to the 10.2 and 10.3 packages too? I mean I don't see any way you'll be able to fix this in Debian without keeping the epoch. > Because of the epoch, anybody running for example mariadb-server version > 10.3.x will have their packages either break. mariadb 10.3 isn't in any Debian or Ubuntu release so that doesn't really matter. If people are installing beta versions of low-level stuff from third-party repositories, that's not really Ubuntu's problem. Even 10.2 isn't in any *stable* release of Debian or Ubuntu, so people using it now have an unsupported system. epochs do get added to packages sometimes and sometimes the epochs didn't really need to be bumped but the Debian archive can handle epochs. Any third-party repositories should be aware of the epochs for relevant packages for the series they target. Thanks, Jeremy Bicha -- Ubuntu-release mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
