On Thu, 2022-10-20 at 10:11 +0200, Johannes Schauer Marin Rodrigues wrote: > Hi Debora, > > Quoting Debora Velarde Babb (2022-10-20 08:04:35) > > The upstream package for tss2 has been renamed ibmtss. When the > > name was > > changed upstream, the version number convention also > > changed. Upstream > > tss2-1470 was updated to ibmtss-1.3.0. The current version of > > ibmtss is now > > 1.6.0. I believe I need to use an epoch number to handle the > > version change > > correctly. > > > > Initially I attempted to create the package with the new name > > ibmtss. > > There was some discussion on debian-mentors list and the response > > was > > that I should NOT change the name to ibmtss and instructed to > > instead > > use an epoch number. > > which discussion was that? I searched the last four months of the > debian-mentors list archive for your name as well as for the string > "tss" and > couldn't find the advice to use an epoch instead renaming the source > package.
Apologies, I was incorrect, I did not get that advice from debian- mentors list. I had opened a request to salvage the tss2 package and take over as maintainer. That lead to some discussions between myself and two other debian developers via direct messages. So the discussion was not included in a mailing list. > Just like pabs (and for the same reason) I would argue for a one-time > migration > rather than carrying a wrong name as well as the epoch number > forever. > > > I recently posted a packaging question to the debian-mentors list > > and someone > > kindly explained that use of an epoch number needed to be discussed > > on > > debian-devel first. > > That is correct. Thanks for reaching out to us! :) > > cheers, josch
