Packaging the Elisa music player - Upload rejected

Aurélien COUDERC coucouf at coucouf.fr
Sat Sep 29 19:01:12 BST 2018


Le 22/09/2018 à 19:28, Sune Vuorela a écrit :
> On Friday, September 21, 2018 5:10:14 PM CEST Aurélien COUDERC wrote:

Hi Sune,

>> IIRC the policy now explicitly says that you should get consensus on
>> debian-devel before bumping an epoch. Or is the ftp masters answer enough
>> to override that requirement ?
> 
> I'd say that that requirement does not cover this exact usecase. Which is a 
> bit .. weird. 
> 
> I would just have uploaded with epoch and be done with it.
> 
> But I'd expect debian-devel also quickly to agree on it.

I’ve gone the hard way. ;-)
And it looks like it was a good idea, you may have seen that it prompted a bit
of a discussion [0] with some interesting input.
The general consensus is against bumping epoch, and in particular there is
a strong rule against ever having 2 packages with the same upstream versions,
even with different epochs in order not to break various archive tools.
Which would be a risk if we just bumped the epoch and the new elisa catches up
with some existing versions of the old elisa project.

So we’re left with keeping elisa and version 1.1+really0.2.1 or using another
package name like elisa-music-player and keeping version to 0.2.1.
I tend to prefer the first option as we can hope to catch up with the former
project’s version and in the end just have the plain "elisa" package name.

But I’m open to discussion if others have different opinions.


[0] https://lists.debian.org/debian-devel/2018/09/msg00220.html


Cheers,
--
Aurélien



More information about the pkg-kde-talk mailing list