Groups > linux.debian.maint.python > #17368

Re: RFC: python-imgviz: Repository out of sync with Archive

Path	csiph.com!pasdenom.info!usenet.goja.nl.eu.org!news.nntp4.net!news.hispagatos.org!srl.newsdeef.eu!news.corradoroberto.it!gothmog.csi.it!bofh.it!news.nic.it!robomod
From	Arian Ott <arian.ott@ieee.org>
Newsgroups	linux.debian.maint.python
Subject	Re: RFC: python-imgviz: Repository out of sync with Archive
Date	Sat, 17 Jan 2026 19:40:01 +0100
Message-ID	<Mejnj-bhCP-3@gated-at.bofh.it> (permalink)
References	<Mdx8Z-aKIJ-1@gated-at.bofh.it> <MdFgd-aQkI-9@gated-at.bofh.it> <MdPyV-aXzp-5@gated-at.bofh.it> <Me2Zc-b6Ci-11@gated-at.bofh.it>
X-Mailbox-Line	From debian-python-request@lists.debian.org Sat Jan 17 18:35:20 2026
Old-Return-Path	<arian.ott@ieee.org>
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 CL_IP_EQ_HELO_IP=-2 (check from: .ieee. - helo: .mail-oa1-x2d.google. - helo-domain: .google.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -3.5
X-Gm-Message-State	AOJu0Yzvo2CQjdjDYXo87Sg/LSuSUD5FYB9SoZcAZgE73IgvgkKkJ07q 8TUVnBuQXp602SuapRsJTM0EzpjROhjyNxWSs8ErtIefbKa1qakMzH8aReKwwHfdsjqiRfSt9Zt +GsD/7BHanGC/EHFeYVUxRWJfa//SmVU3tbKold/O
X-Gm-Gg	AY/fxX5FXkUXJvTR+0+azQmCezRCPTqE4g+ot7auRPtbG2iX62bqLgSmUvN3+4JZcZR ZohPlIhrbq4siD9JN2mLVEZO+TRd2cqClytrVpiAdb6hCuJr14iD5dpKUuszBz3pZ3dnIMW+OZD iIQGV9whyseqf3imLpes95UaXC11nWQPOVLjtHQWTgJrEJFg6+zcgipoMX4OWlzQTUY+Ufomf9z HJly02BvLD9kBR8j8etc6r8OplfFaqMzDm1QwxC7C12wSR7+B4xfu2lqc9DYjXwTzpqLlGp5zLK 7WxF15OFbQDTqdY7i0XmTpMRax9F+BLzELonencEs0kyVVLBf7hmYLyyBRXHSs3vveMhv14Z7Q5 2do0WlWDV6KSaZBJ0MsFIFMM=
X-Received	by 2002:a05:6820:2222:b0:661:1580:bf84 with SMTP id 006d021491bc7-66118124e5amr3052226eaf.34.1768674889200; Sat, 17 Jan 2026 10:34:49 -0800 (PST)
MIME-Version	1.0
X-Gm-Features	AZwV_QjriGQNGcsHOWMUOJpFndVUeHjjTz7DAOFlhTDxmmQeVpeEfvidW50jbIw
Content-Type	multipart/alternative; boundary="0000000000007e9ba1064899b691"
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/23625
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/CAFR_EqpoSU_GPsfe6-KF76APnbjnzPja5+qibH9E+2qaHWQVew@mail.gmail.com
Approved	robomod@news.nic.it
Lines	99
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Cc	debian-python@lists.debian.org
X-Original-Date	Sat, 17 Jan 2026 19:34:37 +0100
X-Original-Message-ID	<CAFR_EqpoSU_GPsfe6-KF76APnbjnzPja5+qibH9E+2qaHWQVew@mail.gmail.com>
X-Original-References	<CAFR_EqqvexqA8XCXV=p2SDNVt3qWqa5_xME3DF4iiRPr6fxE2Q@mail.gmail.com> <3252012.OBFZWjSADL@soren-desktop> <CAFR_EqqVOVg4Fw+BXrBm160A6usT0-o8M=j-JdVgQyFCbFk-Sg@mail.gmail.com> <2090539.lxTPI1ogt6@soren-desktop>
Xref	csiph.com linux.debian.maint.python:17368

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

>
> When you import the currently shipping version from the .dsc, it should
> import
> the current changelog as well.  Did it not do so?  If not, what procedure
> did
> you use to import the current .dsc?
>

I am in Cologne so I haven't really tried it yet. Will do tomorrow once I'm
back home.


Typically, if there are breaking changes, they should be uploaded to
> experimental first, and only moved to unstable once all dependent packages
> are
> compatible.


Can I do both? Packaging the alpha in experimental and the last stable
release in unstable? That way a new stable version is already in the repos.


If you find it helpful, you can package alpha versions,
> especially in experimental.  However, my personal preference is not to
> ship
> alpha versions in unstable unless they resolve a particularly nasty bug
> and it
> is not feasible to cherry pick the change to the current version in
> unstable
>

Totally agree. Software must be stable if it's being packaged for Debian.
Having an alpha in unstable is risky.

I'll check if there are nasty bugs being
resolved in the current alpha.

If there is no particular reason for shipping the alpha I will proceed with
the latest stable.

Best,

---
Arian
arian.ott@ieee.org

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

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