Hello, On Wed 28 May 2025 at 02:14pm +01, Ian Jackson wrote:
> Sean Whitton writes ("Bug#1106266: git-debpush: should possibly always
> overwrite whatever is in the target suite"):
>> In this case, someone might think that the maintainer's git repository
>> on salsa including changes tagged as released, but that have not been
>> uploaded,
>
> The resulting state is a common out-of-course state in Debian, because
> there are already many other reasons why there might be a tag on salsa
> for an upload that never made it to the archive.
>
> Some examples include NEW rejections, sponsorships, and even
> networking failures.
The comparison with NEW is apt. After thinking about the example of
NEW, I'm no longer sure whether I would prefer tag2upload to always
overwrite NMUs or not.
> The right way to deal with this [...]
People could reasonably disagree here, though. If they think
overwriting an NMU is not much like NEW processing skew, then they might
want tag2upload to behave differently in this case in order to
prioritise reducing skew.
--
Sean Whitton
signature.asc
Description: PGP signature
