Re: Debian part of a version number when epoch is bumped
On Mon, Feb 12, 2018 at 03:23:14AM +0100, Guillem Jover wrote:
> On Fri, 2018-02-09 at 14:35:15 -0500, Jeremy Bicha wrote:
> > On Fri, Feb 9, 2018 at 2:22 PM, Andrey Rahmatullin <firstname.lastname@example.org> wrote:
> > > On Fri, Feb 09, 2018 at 06:58:49PM +0100, Philipp Kern wrote:
> > >> If Ubuntu uses an epoch without Debian following that decision, they can
> > >> never sync with Debian again, increasing the maintenance burden
> > >> indefinitely.
> > > See e.g. libpulse0 (pulseaudio), sadly (I needed to repack a $job package
> > > and fix the Depends line to use the package on Debian because of that).
> > Would it hurt to take those epoch bumps into Debian?
> Depends on what you mean by hurt. I see epochs being used w/o much
> tought or care, on many situations where they are not supposed to be
> used, and they are permanent stigmas.
I wonder where this representation of "epoch" as a "stigma" comes from.
They're a part of a version number. They're as much a stigma as the "57"
in "libavcodec57". What's the big deal? Just use it if you need to, and
be done with it.
There's really really really nothing wrong with using an epoch. If some
of our (or someone else's) infrastructure has issues dealing with them,
then that's a bug in the infrastructure and we should fix it. But nobody
should be afraid of using an epoch when the upstream version number
changes incompatibly, because *that's what they're for*.
Could you people please use IRC like normal people?!?
-- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008