Path: csiph.com!weretis.net!feeder8.news.weretis.net!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Arian Ott Newsgroups: linux.debian.maint.python Subject: Re: RFC: python-imgviz: Repository out of sync with Archive Date: Fri, 16 Jan 2026 11:50:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Jan 16 10:46:24 2026 Old-Return-Path: X-Amavis-Spam-Status: No, score=-5.201 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, HTML_MESSAGE=2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 IX_MANITU=ERR(0) CL_IP_EQ_HELO_IP=-2 (check from: .ieee. - helo: .mail-oi1-x231.google. - helo-domain: .google.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -3.5 Arc-Seal: i=1; a=rsa-sha256; t=1768560359; cv=none; d=google.com; s=arc-20240605; b=SseWilLtQzO/1jiQqX5Wa+vKOTL5gE8CUfBYb9KYYMnQXG9RwTb2CDv4QNyyJKWQBZ wDSSE3b4LgClvQds28y7TLuW/166JZjTSbBL/TO6xIwbEA2vrcTxt7AltBdt/o9htnP0 Q5xcabkPMf32p0D8q8V2dn+QKWHvGik5C1QObWVERe8xi5yyptKh7xyZ5KR9elnUVNRD Txi+7ahagcjfiS/PQUQsJm2TRnK8JUQQ7Xf8eccqdf0l4D5McmVFO2c0s/trPVheQDMa yV0b5jcHtcZAdpkSqolXKi0qDAoIqi1CwnAW5PpS9OLj5Mz36H7o59vkv+Zlm48nwAtm T40Q== Arc-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=xT830/rkXfnSM7d4T7K/zQpO/ZEGGkNrSBKg6oz/cv0=; fh=eESyh4qY0FtAM+HCGIdGpQfFEk53AFo84ZpF7S99DLs=; b=MPQDDjdXVWmmoQiJ2Fx29N98gzlnjEV8orNmQALoI+r8wek3YPOPapFpSx81nPEm2h vJxhgEUswQIUWT9h8x4UM4BXYxJQt33PCjm9Yk1sn+fh5UDci+oyIjHDGbRlYODhR+EG jXt6f5uUPG5wfdnLQCSB3jWRNwG0cTyrvjtnBOA2O5r5FMAUnqtQzFe3cJqZvdAVplqS 4FU3ZN8/doT/DVTtFaw8Kjf/VX/uiEc4m723u1zRN7us06I8bL66WkRiYr5MACra1JMH CEC9Ra+fRtYxH4loJNN3KuwywaTRxr3IwVFQw5WqABqOgjKGrmfnuNv3Yil/gBQqCre2 23dQ==; darn=lists.debian.org Arc-Authentication-Results: i=1; mx.google.com; arc=none X-Gm-Message-State: AOJu0Yx+kC7kc8C5vNPjq8icAvNE1JMXQij5wsFgxqXVWKn7d7Eq2xRk 1PctSjTKe4UMVxjQ3fPE9wSUY+oTiz1B0D1QyXBZpgoPlLvoCIvsKP3HxRN1Z2X0XuT50IHJyBr I8YupIr0JtfpddNthY9MFPFWOouTlfTbIBR748NV/ X-Gm-Gg: AY/fxX76VLc5R/xhK5aygZxKqvcIAuzErjbuiBkABBorSX50QC3YntAKTO8KZBA1NVY bAlwf+Tc+B1NOVJZs+WclRxv3MAU/UIbHfM4RXgONfoEXo4quyKFKabaLAa8c/mscn2UIRb8H/o vsf2Jv2xr19uyRAyswrQPwF1XaeqoujbtVCCBNu5PIST+81wv0X8On7UHAoEeZkjtWfyFYFZk1+ QgL7YQqYqZR7oVGh4UA8aX39uHK5g09emgSWM0IPrr8Ny8SDofZCCrOvbTpC5y//CGe5ukZko1U uT8i3OL4ipzd3gy25Ohj45FlBFjCXduluw6/JjQZ7Fw2OfN6LW05i+r6xI9kgG/XcobWzZ12H6p nmPIFUKYivgoTUCGpXBkN5Mw= X-Received: by 2002:a05:6808:2507:b0:43f:5995:b192 with SMTP id 5614622812f47-45c9c02073dmr1290700b6e.30.1768560359137; Fri, 16 Jan 2026 02:45:59 -0800 (PST) MIME-Version: 1.0 X-Gm-Features: AZwV_Qjqjr-Y6H14PuJ_Gd1uQfGXg9_com5depJdfHM2_6O5KdTUYadAm8xvknU Content-Type: multipart/alternative; boundary="000000000000f88ca006487f0ba4" X-Mailing-List: archive/latest/23615 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAFR_EqqVOVg4Fw+BXrBm160A6usT0-o8M=j-JdVgQyFCbFk-Sg@mail.gmail.com Approved: robomod@news.nic.it Lines: 109 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Fri, 16 Jan 2026 11:45:48 +0100 X-Original-Message-ID: X-Original-References: <3252012.OBFZWjSADL@soren-desktop> Xref: csiph.com linux.debian.maint.python:17362 --000000000000f88ca006487f0ba4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 16 Jan 2026, 00:44 Soren Stoutner, wrote: > On Thursday, January 15, 2026 8:06:56=E2=80=AFAM Mountain Standard Time A= rian 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 --000000000000f88ca006487f0ba4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, 16 Jan= 2026, 00:44 Soren Stoutner, <soren@debian.org> wrote:
On Thursday, January 15, 202= 6 8:06:56=E2=80=AFAM 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.=C2=A0

Thanks fo= r the pointers. How would I document it in d/changelog? There would be a ga= p.=C2=A0

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 mailin= g
list.

Sounds good.=C2=A0

Furthermore, upstream's=C2=A0latest=C2=A0release is 2.0.0 alpha= and introduces breaking changes.
Is it gen= erally a good practice to package the latest stable release or can I packag= e the alpha version?


--
Arian Ott
arian.ott@ieee.org

--000000000000f88ca006487f0ba4--