On 17/06/2025 17:41, Nicholas D Steeves wrote:
Nicholas D Steeves <s...@debian.org> writes:
Lee Garrett <deb...@rocketjump.eu> writes:
On 16/06/2025 21:54, Nicholas D Steeves wrote:
Lee Garrett <deb...@rocketjump.eu> writes:
On 15/06/2025 20:57, Nicholas D Steeves wrote:
Lee Garrett <deb...@rocketjump.eu> writes:
I have pushed my changes to g...@salsa.debian.org:debian/borgbackup.git -b
lgarrett/debian/latest before I saw your mail. I'm fine with adding the
autopkgtests after the release via s-p-u.
I have good news! We've received a Release Team ack to add autopkgtests
for the trixie unblock *if* they've been first tested in experimental.
Good to hear.
So we now need to preferentially target debian/latest. I would have
generated your changelog entries and uploaded immediately; however,
there's an issue that I'm unwilling to sign-off on, and I feel like it
would be mean to just revert your work. "Bump Standards-Version"
appears to have been gratuitous, and I'm not convinced that the package
is actually Policy 4.7.2-compliant at this time. See ยง10.1 Yes, this
might alternatively be a deficiency of Policy, but I'd rather remove
this issue from consideration, at this time, in the interest of saving
time getting DebCI evidence for experimental ASAP so we can pursue the
unblock (with autopkgtests/DebCI enabled). There's a proper order to
things though! :)
Alright. Shall I release the sten/debian/latet branch as-is + autopkgtests?
Out of curiosity, what violation do you believe is there? Is it because
borgbackup-is-borgbackup2 also ships /usr/bin/borg{,fs}?
Cheers,
Nicholas
