* Marc Haber <mh+debian-de...@zugschlus.de> [241127 13:52]: > On Wed, Nov 27, 2024 at 01:48:33PM +0100, Chris Hofstaedtler wrote: > > * Marc Haber <mh+debian-de...@zugschlus.de> [241127 13:28]: > > > On Wed, Nov 27, 2024 at 04:58:00PM +0500, Andrey Rakhmatullin wrote: > > > > Yup, as I said it makes sense. It just feels fragile to me when the > > > > "pristine" tarball for a given upstream tag in a given repo is not > > > > determined until someone uploads it. > > > > > > I would love to have a possibility to just push a new upstream tarball > > > into the archive at the very beginning of the process of packaging the > > > new upstream version (and without triggering anything else in Debian). > > > > I hear what you're saying, but in the end it is still a workaround, > > right? > > It's just "putting a nail" into a new upstream version. > > > Just uploading a new tarball with every debian revision seems so > > much more straightforward. > > That means that the upstream tarball is possible to get wrong with any > new upload. I am not sure whether I like that.
At least for some packages, what I consider the interesting part is the contents of the "upstream" branch, and not what is in upstream's tarball. > I might motivate me, > though, to finally explore which of the tools I am holding wrong with > upstream tarball handling. Reconciling these things seems like a lot of busywork, as you said. While I haven't given up on pristine-tar yet, this thread pushes my motivation towards exploring the +dfsgN-1 idea "fo' real". Chris
