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.
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.
On Wed, 3 Jun 2026 17:54:54 -0700 Charles ChambersIn addition to the links provided in another reply, you might want to
<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 theIn point of fact - unless I'm forgetting something - uploads to 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.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 4 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 495145:23:06 |
| Calls: | 165 |
| Files: | 574 |
| D/L today: |
29 files (9,998K bytes) |
| Messages: | 78,198 |