Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 26 |
Nodes: | 6 (0 / 6) |
Uptime: | 64:33:16 |
Calls: | 482 |
Calls today: | 1 |
Files: | 1,072 |
Messages: | 96,304 |
I think this significantly underestimates the annoyance involved in renaming
existing long-lived branches (in that all clients have to re-clone or manually adjust), which is certainly why I generally avoid doing so unless I
absolutely have to.
This seems overly complicated. The simplest way forward if to finalize DEP-14, and let maintainers and packagers adopt it whenever they feel
the benefit. You probably also want to wait a bit for tooling
maintainers to default to what DEP-14 suggests.
Regardless of what branch names packages use today or in the future,
they should all have a debian/gbp.conf file that defines what branches
and packaging practices are being used *right now*.
While this is accurate considering the latest DEP-14 version, it
should be noted that the first DEP-14 draft allowed 'master' as the
main branch for native packages and up to 2020-11-29 DEP-14
recommended debian/master instead of debian/latest.
Earlier adopters (like me) thus probably don't follow the latest
changes to DEP-14 because what's the point of renaming a perfectly
fine branch.
Regarding "I don't want a gbp.conf", I think that we should aim for DRY,
and that adding a gbp.conf in every package doesn't sound too great for
teams that maintain hundreds or thousands of packages...
Regarding "I don't want a gbp.conf", I think that we should aim for DRY, >and that adding a gbp.conf in every package doesn't sound too great for >teams that maintain hundreds or thousands of packages...
Yes, please.
On 09/05/25 at 12:43 +0200, Lucas Nussbaum wrote:
I would love to see data about the actual acceptance of DEP-14 among packages in the archive: my feeling is that it is currently being a bit ignored by maintainers and teams (but maybe I'm wrong).
I started working on a salsa importer in UDD. It still needs some
polishing and Web pages to expose interesting results, but it already provides the following information:
* 37641 source packages in trixie/main
* of which 36083 declare a VCS URL
* of which 34644 point to a salsa project
* of which 34370 point to a salsa project that exists
[...]
* 37641 source packages in trixie/main
* of which 36083 declare a VCS URL
* of which 34644 point to a salsa project
* of which 34370 point to a salsa project that exists
[...]
This is now available at https://udd.debian.org/cgi-bin/dep14stats.cgi