Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #17362
| From | Arian Ott <arian.ott@ieee.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: RFC: python-imgviz: Repository out of sync with Archive |
| Date | 2026-01-16 11:50 +0100 |
| Message-ID | <MdPyV-aXzp-5@gated-at.bofh.it> (permalink) |
| References | <Mdx8Z-aKIJ-1@gated-at.bofh.it> <MdFgd-aQkI-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Fri, 16 Jan 2026, 00:44 Soren Stoutner, <soren@debian.org> 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 arian.ott@ieee.org
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar
RFC: python-imgviz: Repository out of sync with Archive Arian Ott <arian.ott@ieee.org> - 2026-01-15 16:10 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Soren Stoutner <soren@debian.org> - 2026-01-16 00:50 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Arian Ott <arian.ott@ieee.org> - 2026-01-16 11:50 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Carsten Schoenert <c.schoenert@t-online.de> - 2026-01-16 14:20 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Arian Ott <arian.ott@ieee.org> - 2026-01-16 16:50 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Soren Stoutner <soren@debian.org> - 2026-01-17 02:10 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Arian Ott <arian.ott@ieee.org> - 2026-01-17 19:40 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Soren Stoutner <soren@debian.org> - 2026-01-17 19:40 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Arian Ott <arian.ott@ieee.org> - 2026-01-17 19:50 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Arian Ott <arian.ott@ieee.org> - 2026-01-20 10:50 +0100
csiph-web