Hi everyone,
I'm in the final stages of creating borgbackup 1.4.1-3 (some packaging fixes and
adding autopkgtests), I'll upload it today or tomorrow and then also file an
unblock request.
Greets,
Lee
On 14/06/2025 21:14, Nicholas D Steeves wrote:
Hello Simon,
I recently joined the "Borg Collective" because I've had trouble
reaching any of the maintainers. In the past Gianfranco has been AFK
for ≥6months (summer holidays, I think? When he was my mentor), so I
think we need to plan for not hearing back from him.
Reply follows inline:
Simon McVittie <s...@debian.org> writes:
Hi,
I see that there is a new upstream bug-fix release of borgbackup in
unstable, compared with what's in trixie.
This is not going to migrate to trixie without help, because borgbackup
is classified as a key package:
https://qa.debian.org/excuses.php?package=borgbackup
It's a key package because the freedombox metapackage pulls it in:
- reason: freedombox depends borgbackup
source: borgbackup
— https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Is this intended to get into trixie? If yes, please open an unblock
request so that the release team can review it.
I don't know for sure, but I believe it was most likely intended. Also,
the borg 1.x series appears to be CVE and bug-fix only, so I think the
regression potential is particularly low.
I'm willing to file the unblock address, and of course local testing,
but today I don't see myself as willing to do a serious git diff of the
upstream changes.
One thing I'd also like to do is fix the scary, complicated, an
out-of-date NEWS entry that all users who upgrade to trixie will see.
Upstream has since provided a streamlined migration protocol. Do you
think the release-team would appreciate an upload that includes this
before filing the unblock request? I would of course be happy to use
this opportunity to add the git shortlog to debian/changelog to make it
easier for the release-team to review the debdiff for the unblock
request!
There's also now #1107775
Regards,
Nicholas
