Bug#1105862: git-debpush and detecting intent to use pristine-tar

2025-06-05 Thread Sean Whitton
control: tag -1 + pending Hello, On Sat 17 May 2025 at 10:05am +01, Sean Whitton wrote: > On Fri 16 May 2025 at 11:52am +01, Ian Jackson wrote: >> >> I looked in git-debpush and it doesn't say explicitly how orig >> tarballs will be created. It would be a good idea to be clearer about >> that.

Bug#1105862: git-debpush and detecting intent to use pristine-tar

2025-05-18 Thread Sean Whitton
Hello, On Sat 17 May 2025 at 12:05pm +01, Ian Jackson wrote: > Yes. Also that git-debpush doesn't attempt to transfer pristine-tar > information via git, which is a thing the user might expect it to do. Hmm, yes, I guess they might expect that. I was thinking that pristine-tar is too weird and

Bug#1105862: git-debpush and detecting intent to use pristine-tar

2025-05-17 Thread Ian Jackson
Sean Whitton writes ("Bug#1105862: git-debpush and detecting intent to use pristine-tar"): > Strictly, it's an implementation detail of the combination of the > service and the archive whether it even tries to fetch existing tarballs > from the archive versus just gener

Bug#1105862: git-debpush and detecting intent to use pristine-tar

2025-05-17 Thread Sean Whitton
Hello, On Fri 16 May 2025 at 11:52am +01, Ian Jackson wrote: > Package: git-debpush > Version: 12.12 > > Consider a user who is used to using pristine-tar, either with dgit, > or with a dput-based upload flow. > > If they prepare a new upstream version, they may be surprised that > they use t2u,

Bug#1105862: git-debpush and detecting intent to use pristine-tar

2025-05-16 Thread Ian Jackson
Package: git-debpush Version: 12.12 Consider a user who is used to using pristine-tar, either with dgit, or with a dput-based upload flow. If they prepare a new upstream version, they may be surprised that they use t2u, the .orig that ends up in the archive is not the one that they imported into