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

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

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-17 19:40 +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>
Organization	linux.* mail to news gateway

Show all headers | 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