On Fri, Dec 19, 2025 at 02:17:57PM +0100, Daniel Gröber wrote: >... > On Thu, Dec 18, 2025 at 10:56:42AM +0200, Adrian Bunk wrote: >... > > And a git repository might disappear, or the commit might disappear, > > or the commit was never pushed anywhere. > > We should be able to migate this by having infra that pulls and archives > the git commits right after it shows up in the archive (ala > snapshots.debian.org). > > I could also imagine the repo/commit being acessible in this way (when the > Otto's metadata fields are present) being an acceptence criteria for FTP > uploads in the future to keep things consistent. >...
That would be a really bad idea, maintaining something in two different formats in two different places is not a sane architecture. If you want to have the git tree for a package mandatory in Debian, it should be part of the upload. And at that point there is no reason left for the legacy tarball format we are currently using. A modern architecture would be that a signed git tag is a source package, and the official buildds are integrated into the git hosting CI. Until then you can use tag2upload, which generates the legacy tarball format from git. > --Daniel cu Adrian
