[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1108491: marked as done (unblock: borgbackup/1.4.1-3)

Your message dated Wed, 9 Jul 2025 14:29:38 +0200
with message-id <42474039-6f23-4acd-992e-e28b7cdb8d47@debian.org>
and subject line Re: Bug#1108491: unblock: borgbackup/1.4.1-3
has caused the Debian Bug report #1108491,
regarding unblock: borgbackup/1.4.1-3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1108491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108491
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: borgbackup@packages.debian.org, sten@debian.org
Control: affects -1 + src:borgbackup
Control: block 1107775 by -1

Please unblock package borgbackup

[ Reason ]
Borgbackup 1.4.1 has been in unstable since 2025-05-10.  The only bug
reported since then was #1107775, the request to unblock it.  It
appears that locutusofborg went on holidays or fell into the Nexus,
which is why I'm filing this unblock (as a team member).

Upstream also significantly changed the migration instructions (in
1.2.8, which affects bookworm2trixie users) but our NEWS file was not
updated to reflect these changes, and I've fixed this in this unblock.
Other than the practical user-facing reason, it's important to support
upstreams who write better migration tools, processes, and
documentation.

[ Impact ]
Starting with 1.4.1, borgbackup 1.x is security-supported upstream,
and we should take advantage of this.  The 1.4.0 release currently in
trixie is also buggy in various known ways (see git shortlog entries
included in d/changelog).  The documentations improvements are notable
and significant.

[ Tests ]
I have been using 1.4.1 since it was uploaded to unstable, and I also
have been regularly using a local bookworm-backport at two sites.

Lee Garrett added upstream's unit tests to autopkgtests, and I added
the standard (less significant) Python ones.  We made that upload to
experimental on 2025-06-18, and there have been no regressions, so I
uploaded 1.4.1-3 to unstable 2025-06-29.

As expected, 1.4.1-3 passes DebCI and reproducibility tests.

[ Risks ]
The 1.4.1 release of this key package is a bugfix, security, and
documentation release by a mature upstream.  The regression risk is
low, and I'm confident that you will agree after skimming our
changelog.

The "New Features" upstream documents in their changelog have been
implemented in a modular and minimally invasive way.  Backwards-compat
with 1.4.0 is fully retained.  With the exception of the new optional
Padme chunk size padding security feature these "New Features" are human interface changes rather than risky structural ones.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
Borgbackup also gains a new Uploader (Lee Garrett) in this release.

unblock borgbackup/1.4.1-3

Attachment: borgbackup_1.4.0-5_to_1.4.1-3.debdiff.gz
Description: application/gzip


--- End Message ---
--- Begin Message --- 
Hi,

On 6/29/25 19:14, Nicholas D Steeves wrote:

Borgbackup 1.4.1 has been in unstable since 2025-05-10.



This new upstream version is not in line with the spirit of the freeze.

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: