Hey Aurélien,

> 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.

me personally dislike the +really versions, because IMO it is harder to parse 
for humans, but I'm fine with doing an upload with that version number. And 
the other solution having a different package name is also not a nice 
solution. Aurélien ping me, if you updated the version number and the package 
is ready again for upload.

hefee

Attachment: signature.asc
Description: This is a digitally signed message part.

-- 
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-talk

Reply via email to