Hi, ... > > This surprises me a bit: Back in July I had described a scenario for teams > > which might be problematic, and you seemed to agree at this point: > > > > https://lists.debian.org/debian-perl/2025/07/msg00027.html > > > > Has anything changed since then wrt to this constellation? > > Yes, as Simon pointed out, git-debpush will stop you from uploading if > there is a pristine-tar branch containing a tarball for the current > upload.
I would really like to use tag2upload, but many of my upstreams sign their releases and tag2upload (->dgit) will recreate those tarballs and invalidate the signatures. The tag2upload authors have said they won't implement support for pristine-tar which would keep the signatures valid, but sharing the bug-# here in case someone else wants to take a stab: #1106071 wanted: tag2upload support for pristine-tar https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106071
