• Updated packages

    From Charles Chambers@3:633/10 to All on Thursday, June 04, 2026 03:00:01
    I'm resurrecting an abandoned package, and I'm finding myself having to
    update a dependency also.

    Does anyone know anyone that can explain the process of getting them
    into the Debian package repository?ÿ The finished versions are being
    tested and will be supported against Bookworm, Trixie, and Forky as a maintenance release, and possibly against sid as a preview edition.

    Responses off list would be preferred.

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From David@3:633/10 to All on Thursday, June 04, 2026 05:50:02
    On Thu, 4 Jun 2026 at 10:55, Charles Chambers <cchamb2@gmail.com> wrote:

    I'm resurrecting an abandoned package, and I'm finding myself having to update a dependency also.

    Does anyone know anyone that can explain the process of getting them
    into the Debian package repository? The finished versions are being
    tested and will be supported against Bookworm, Trixie, and Forky as a maintenance release, and possibly against sid as a preview edition.

    Responses off list would be preferred.

    Hi, here's some info pages that should help "explain the process":
    https://wiki.debian.org/DebianMentorsFaq
    https://mentors.debian.net/intro-maintainers/
    https://mentors.debian.net/
    https://wiki.debian.org/Packaging/Intro

    The debian-mentors mailing list is very helpful.

    I have CC'd you my reply as you requested. But if you wish to
    reply, please reply to debian-user list, not to me, thanks.

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Joe@3:633/10 to All on Thursday, June 04, 2026 10:10:01
    On Wed, 3 Jun 2026 17:54:54 -0700
    Charles Chambers <cchamb2@gmail.com> wrote:

    I'm resurrecting an abandoned package, and I'm finding myself having
    to update a dependency also.

    Does anyone know anyone that can explain the process of getting them
    into the Debian package repository?ÿ The finished versions are being

    tested and will be supported against Bookworm, Trixie, and Forky as a maintenance release, and possibly against sid as a preview edition.


    Sid and testing are not usually more than two weeks apart until the
    freeze, unless something dreadful happened to a new package in sid. A
    sid installation will normally have a banner showing the release as
    'sid/forky' (or whatever testing is) and should contain both sets of repositories. I don't think you need worry about sid separately, it's a
    fairly fast-moving target.

    --
    Joe

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From The Wanderer@3:633/10 to All on Thursday, June 04, 2026 14:40:01
    On 2026-06-04 at 04:02, Joe wrote:
    On Wed, 3 Jun 2026 17:54:54 -0700 Charles Chambers
    <cchamb2@gmail.com> wrote:

    I'm resurrecting an abandoned package, and I'm finding myself
    having to update a dependency also.

    Does anyone know anyone that can explain the process of getting
    them into the Debian package repository? The finished versions are
    being tested and will be supported against Bookworm, Trixie, and
    Forky as a maintenance release, and possibly against sid as a
    preview edition.
    In addition to the links provided in another reply, you might want to
    start with the Debian New Maintainers' Guide: https://www.debian.org/doc/manuals/maint-guide/
    Sid and testing are not usually more than two weeks apart until the
    freeze, unless something dreadful happened to a new package in sid.
    A sid installation will normally have a banner showing the release
    as 'sid/forky' (or whatever testing is) and should contain both sets
    of repositories. I don't think you need worry about sid separately,
    it's a fairly fast-moving target.
    In point of fact - unless I'm forgetting something - uploads to the
    Debian repositories (other than backports to oldstable and the like)
    invariably start out as uploads to sid, and then get migrated to testing (currently forky) after a suitable time with no blocker issues being discovered. That applies not only to new packages, but also to new
    versions of existing packages.
    So the idea of "possibly" supporting against sid (much less as a
    different edition) seems mis-aligned with the way the system works. In
    order to get a package version into testing, it would have to go through
    sid; any edition that you want to have show up in forky would need to
    appear in sid first.
    --
    The Wanderer
    The reasonable man adapts himself to the world; the unreasonable one
    persists in trying to adapt the world to himself. Therefore all
    progress depends on the unreasonable man. -- George Bernard Shaw


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)