Re: Epoch bump for kernelshark
Mattia Rizzolo <mattia@debian.org> writes:
> On Sun, May 23, 2021 at 03:17:10PM -0500, Richard Laager wrote:
>> On 5/23/21 8:34 AM, Sudip Mukherjee wrote:
>> > And, as a result, upstream kernelshark is now at v2.0 but the Debian
>> > packaged version is at v2.9.1 and I will need to add an epoch to the
>> > version to package it directly from its new upstream repo.
>> >
>> > Current version: 2.9.1-1
>> > Proposed version: 1:2.0-1
>>
>> How close is upstream to 3.0? If not close, are they willing to bump to 3.0
>> anyway to avoid this versioning issue?
>
> And in the meantime, I recommend you use 2.0-1 as source version, and
> make the binary 2.9.1+really$(DEB_VERSION) (DEB_VERSION coming from
> /usr/share/dpkg/pkg-info.mk)
>
_If_ upstream is willing to do that, then great. Otherwise I don't see
the problem with an epoch in this kind of situation. It's exactly the
kind of change of versioning they were designed for.
d
Reply to: