On Wed, Feb 14, 2018 at 09:05:05PM +0100, Vincent Bernat wrote:
In the example above, while in Wheezy, the dependency was perfectly correct. It became wrong because of the epoch bump (for no obvious reason). For software we distribute ourselves, this change can be caught at some point before the release (or by automation, like you suggest), but for people packaging stuff outside Debian, this can be far more painful.
It isn't clear how getting rid of epochs would prevent crazy versioning. You'd have just as much trouble with 1.8-really1.7-again1.8-fooledyou1.7
