[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Question about splitting a source package with an epoch



Manuel and I recently salvaged the dutch source package, which builds four 
different Dutch language dictionary packages.

https://tracker.debian.org/pkg/dutch

The problem is that the source code comes from two different upstreams, with 
possibly distinct release schedules.

Manuel and I would like to split this into two source packages, based on these 
two upstream source repositories:

https://github.com/OpenTaal/opentaal-hunspell

https://github.com/OpenTaal/opentaal-wordlist

The current dutch package has an epoch for reasons that happened before we 
were involved with the package:  1:2.20.19+1-1.  If we create a new source 
package named hunspell-nl, it would also need to have the same epoch.

As I have never moved a binary package to a new source package, my question is 
two-fold.

1.  Should I create an ITP for the new source package, even though the binary 
package it produces is not new?  Something about creating an ITP that includes 
an epoch feels off to me.

2.  When moving the binary package to a new source package, should the old 
changelog be preserved?  It seems even weirder to me to have a one-line 
changelog that says “Initial release” that already contains an epoch.

-- 
Soren Stoutner
soren@debian.org

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


Reply to: