Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Soren Stoutner Newsgroups: linux.debian.maint.python Subject: Re: RFC: python-imgviz: Repository out of sync with Archive Date: Sat, 17 Jan 2026 02:10:02 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Sat Jan 17 01:01:41 2026 Old-Return-Path: X-Amavis-Spam-Status: No, score=-114.51 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no Organization: Debian Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWIg4F7bGiws7ReTkyy kYoXFRrd6/4yMA0PAAACaklEQVQ4y22TwXabMBBFJaPuNZGSNZZp1uhM6BpkJeu4VFk3bsL/f0Lf CHC6qHyOgbl68zTDoIwaVfh3tUopTUGpbFToDiFnY9IY2oMAZYMiS4R9SfbSXepSS5EcFAa/muIU aRj8mkoUqrEraFzhYegBmqig0LyCIyM8DAwPlpBqmJVYaD2UeWZ3abVjsqKIojg+hY4omsyIcNSi qIBM6jJWOveS6kvBeVvHJ+VYzJUW88RmA12UiBx3HEcUMRuzIZI6tBQovTrPclNB3AuUXoXvs0XY C3B2baJpW4Dn2ZpVMInCirkxoyhM1qpK5nFrO65QvCrCqql2DyPgvm94iMQz5/PmISuEotxQGMD5 M5G1N9CjXJ5HQH96BZG2xx6AzejYZccxT4Re3Zr4bPKkCcGcz5Or3dVEABkAUY/znnVcQVVkrXVU vomoEJFe7x4nQuaZmZELL6qnXZGIB5YV/Q2IogtSmyNybEcBX2+QCLOAQYm+gmoORUrYzV7dc6R2 T1WPm45oVEQqsjtoIovHyTmcyxMhVVxTqapomZyLlAmTKC9AmjgamXXGZo+epNrXO3wGGiPRHbKL FnMy2RRgRb1gzFXXGjhICp8wqaTtdtyQH6nWTfkatJvJJoUCbOjSC7wR9/naEVognxrOFdLh7Ugx QpA/0QT4pRV0+u2dqsXD5y9EBDjVAJS3ZZLxmZblgmsU8x7mBeCKg48Py7WU2IiH1epbEbC8K9Ms y0cpcySVUcdQVrBY+rEsv+XpYgFKXT8B3v2yATxv8fKK2EfC358tsIMLYqfD401xA0j1EY4P/wWf IbhlOWyBv4OQsywBM8MAAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart8801513.UhI7HUTLeS"; micalg="pgp-sha512"; protocol="application/pgp-signature" X-Debian-User: soren X-Mailing-List: archive/latest/23623 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/2090539.lxTPI1ogt6@soren-desktop Approved: robomod@news.nic.it Lines: 98 Sender: robomod@news.nic.it X-Original-Date: Fri, 16 Jan 2026 18:01:16 -0700 X-Original-Message-ID: <2090539.lxTPI1ogt6@soren-desktop> X-Original-References: <3252012.OBFZWjSADL@soren-desktop> Xref: csiph.com linux.debian.maint.python:17367 --nextPart8801513.UhI7HUTLeS Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8"; protected-headers="v1" From: Soren Stoutner To: debian-python@lists.debian.org Subject: Re: RFC: python-imgviz: Repository out of sync with Archive Date: Fri, 16 Jan 2026 18:01:16 -0700 Message-ID: <2090539.lxTPI1ogt6@soren-desktop> Organization: Debian MIME-Version: 1.0 On Friday, January 16, 2026 3:45:48=E2=80=AFAM Mountain Standard Time Arian= Ott wrote: > On Fri, 16 Jan 2026, 00:44 Soren Stoutner, wrote: > > On Thursday, January 15, 2026 8:06:56=E2=80=AFAM Mountain Standard Time= Arian Ott > >=20 > > wrote: > > > Hi Python Team, > > >=20 > > > 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: > > >=20 > > > 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. > > >=20 > > > What would be the preferred way of handling this? > > >=20 > > > I intend to import the 1.7.5 .dsc from the archive to sync the > > > repository history before making my own changes. > >=20 > > Yes, that is what is typically done, unless you can contact the previous > > uploaders and get them to push their changes to the repository. >=20 > Thanks for the pointers. How would I document it in d/changelog? There > would be a gap. When you import the currently shipping version from the .dsc, it should imp= ort=20 the current changelog as well. Did it not do so? If not, what procedure d= id=20 you use to import the current .dsc? > But, given >=20 > > 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. > >=20 > > Sounds good. >=20 > 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 c= an > I package the alpha version? Typically, if there are breaking changes, they should be uploaded to=20 experimental first, and only moved to unstable once all dependent packages = are=20 compatible. If you find it helpful, you can package alpha versions,=20 especially in experimental. However, my personal preference is not to ship= =20 alpha versions in unstable unless they resolve a particularly nasty bug and= it=20 is not feasible to cherry pick the change to the current version in unstabl= e. =2D-=20 Soren Stoutner soren@debian.org --nextPart8801513.UhI7HUTLeS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmlq31wACgkQwufLJ66w tgNGaA//ZdrnHRMse1s9spHXO0u8Xv3Ena9YHtdfUoa+YpGSgiXMyzY4QqPxmxJO yWpocr6r1bRVhruGjYwQiCN5xjyR5zlmJ7SXCVKDP6ba6vRCCXcYjUMNlyPCbcqy ZRfSk0e0sP8spwJZnGs+q5oJHSP4dY48Iyxa0zFZrfBZrt5UzCUe8Z30P1/BXkxE wqdaP8ikitq/2WHyvGA7HvvX8V/h/qyq853a5Qx52sr72sKrWoL9gYsogIIv/hcp P9Xscz+1mcAPWtIXy42Ji+I4pAZRYSpaFPT00BB9c3fBWLsLwYEbeIyQPuo6zLKI A1ppjEbDWPV/jQCdBxIIhoIba8fk7Z/6fFaZ9pu0SJESB+iarrkjb9BpmmTdECjl jmiEHYuh0ltf/ZUj6Ab/SRA8Pg8g6Y7ydvLLwH+kUaYrxiHsqfpctksbE7MKl0y2 H5XTs3rOCcyQNJWBe5ILUKbCBIZhrkOIZFCQYzE6hWvh2Kzawc/cFJuVHceKJQD3 oghSh+SA1tdtoR/SuslPKNANZOmYDh2Qf3C7ynRImoPWHCtEBPsUjPEvcdbJn3dy GAkws5s+8eWCPCtVEf+Z7tLregsVoe9B8hS+fyUZSbn9ov75fjLcJBuPZpNPmoYE /dJ6PQsjBoApeQH/b7VzNx7mal0k+Kj5cu1C/Aebu16o1GBNANM= =7nH3 -----END PGP SIGNATURE----- --nextPart8801513.UhI7HUTLeS--