On Thursday, May 15, 2025 1:54:36 PM Mountain Standard Time Simon McVittie wrote: > On Thu, 15 May 2025 at 13:39:32 -0700, Soren Stoutner wrote: > >The changelog indeed says the current epoch is 1: > > > >https://salsa.debian.org/debian/dutch/-/blob/master/debian/changelog? > >ref_type=heads#L1 > > > >Also, tracker.debian.org says the same thing: > >https://tracker.debian.org/pkg/dutch > > That's the version of the source package. The version of a binary > package defaults to the same as its source, but it can be different, and > in this case, it is: > > dh_gencontrol -p hunspell-nl -- -v2:$(DEB_VERSION_UPSTREAM_REVISION) > — https://tracker.debian.org/media/packages/d/dutch/rules-12.20.191-1 > > smcv
Thanks for the pointer. Cleaning up the debian/watch file was one of the checkboxes in splitting it into two source packages, and I had not yet read over it closely enough to realize it was making this change there. Interestingly, it only does this for the hunspell-nl binary package, not for the other binary packages. This ends up working out well for the package splitting plans because the hunspell-nl binary package will end up with its own source package which can be epoch 2, while aspell-nl, wdutch, and idutch will all be build from the other source package, which can remain epoch 1. Based on the comments so far, I am inclined to create a new hunspell-nl source package that produces a single hunspell-nl binary package with an epoch of 2 to match what is currently used. I will retain the old changelog history for this new package. I will also modify the existing dutch source package to only include one upstream source that can be appropriately followed by debian/watch. It will continue to produce the aspell-nl, wdutch, and idutch binary packages, which will remain at epoch 1. Are there any objections to handling it this way? -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
