On Wed, Feb 14, 2018 at 2:15 PM, Michael Stone <mst...@debian.org> wrote:
> 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
> 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
How about introducing an Upstream-Version field? It can go up or down
(forwards or backwards, newer or older) independent of the Debian (package)
Then a new upload
Version: 2.0-1 (really 1.5)
Instead use a new field to correct:
foo (2.0-2 Upstream:1.5-1) unstable; urgency=low
The Depends in the control can then look for Upstream-Version and use that
if it is set and fail back to Version if there is no Upstream-Version.
Just an idea.