On 2026-06-04 at 04:02, Joe wrote: > On Wed, 3 Jun 2026 17:54:54 -0700 Charles Chambers > <[email protected]> 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
signature.asc
Description: OpenPGP digital signature
