On Friday, May 16, 2025 1:51:49 PM Mountain Standard Time Nicholas D Steeves wrote: > Hi Soren, > > Soren Stoutner <so...@debian.org> writes: > > On Thursday, May 15, 2025 3:56:50 PM Mountain Standard Time Nicholas D > > Steeves> > > wrote: > >> "adjusting" the epoch also requires discussion, and consensus, on -devel > > > > As far as I know, nobody is proposing adding or adjusting any epochs. All > > of > > these binary packages are going to end up with the same epochs they already > > have. > > Do you disagree with the following?: You're creating two new source > packages that have to pass the NEW queue, you're adding epochs to them, > and your rationale appears to be thus: Because the old multiple-upstream > source package has an epoch, therefore both NEW source packages should > have an epoch.
Actually, my plan is to create one new source package and to refactor the other existing source package. > There's nothing in dsdt-policy about source package naming. No, but there is about binary package naming. Quoting from the policy. "Language-specific ispell dictionary packages and wordlists *must be named* the classical way, like "ifrench", "wfrench", "iswedish", etc. Use of non- English language names is discouraged; for example "ingerman" should not be named "indeutsch". (This is based on existing practice, and is for consistency and the convenience of Debian administrators in all languages.)” "myspell dictionary packages *must be called* myspell-<isocode> and hunspell dictionary packages *must be called* hunspell-<isocode> (<isocode> being the two-digit isocode of the language). Use the myspell prefix for myspell dictionaries and the hunspell prefix for hunspell only dictionaries that use hunspell features." I agree that if it were possible to modify the binary package names for one release cycle it would be possible to remove the epochs. And, if this were a different type of package that did not have a naming policy, I would do so (because I really dislike epochs). But in this case, doing so would be both against policy and not in the best interest of users, because when searching for dictionary packages there is an expectation they are able to find them using the canonical names. -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
