On Fri, 16 Jan 2026, 00:44 Soren Stoutner, <[email protected]> wrote: > On Thursday, January 15, 2026 8:06:56 AM Mountain Standard Time Arian Ott > wrote: > > Hi Python Team, > > > > I'm currently adopting python-imgviz, which has been orphaned (ITA: > > #1124143). While preparing the package, I ran into an issue where I > > would appreciate some advice: > > > > The git repository on Salsa is at version 1.5.1, but the Debian > > Tracker shows that 1.7.5+ds-2 is already in the archive. > > It seems the previous maintainer uploaded without pushing the latest > > commits to Salsa. > > > > What would be the preferred way of handling this? > > > > I intend to import the 1.7.5 .dsc from the archive to sync the > > repository history before making my own changes. > > Yes, that is what is typically done, unless you can contact the previous > uploaders and get them to push their changes to the repository.
Thanks for the pointers. How would I document it in d/changelog? There would be a gap. But, given > that there has been no other response to your email, I would assume that > whoever made these changes no longer subscribes to the Debian Python > mailing > list. > > Sounds good. Furthermore, upstream's latest release is 2.0.0 alpha and introduces breaking changes. Is it generally a good practice to package the latest stable release or can I package the alpha version? -- Arian Ott [email protected]
