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

Bug#1070998: marked as done (bookworm-pu: package fossil/2.24-5~deb11u1)

Your message dated Mon, 5 May 2025 14:09:19 +0200
with message-id <531856aa-84a0-4f1f-83c5-ed3e01d35713@beuc.net>
and subject line Re: Bug#1070998: bookworm-pu: package fossil/2.24-5~deb11u1
has caused the Debian Bug report #1070998,
regarding bookworm-pu: package fossil/2.24-5~deb11u1
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.)


-- 
1070998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070998
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: bookworm
X-Debbugs-Cc: fossil@packages.debian.org
Control: affects -1 + src:fossil
User: release.debian.org@packages.debian.org
Usertags: pu

this bug was opened by previous arrangement with maintainer.

[ Reason ]
fossil is affected by a regression due to a security update of apache
CVE-2024-24795. Backport was choosen
because upstream does not document all commit needed for fixing the regression.

[ Impact ]
Fossil is broken at least server part

[ Tests ]
Full upstream test suite

[ Risks ]
Broken fossil

[ 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 (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]
Backport from sid. They are no incompatibility and this is upstream maintenance
and fix only version.

[ Other info ]
I have not attached the debdiff due to the fix beeing a backport from sid. Attached debdiff to sid instead

diff -Nru fossil-2.24/debian/changelog fossil-2.24/debian/changelog
--- fossil-2.24/debian/changelog	2024-04-30 14:32:05.000000000 +0000
+++ fossil-2.24/debian/changelog	2024-05-07 19:26:27.000000000 +0000
@@ -1,3 +1,10 @@
+fossil (1:2.24-6~deb12u1) bookworm; urgency=medium
+
+  * Non maintainer upload with acknowledgement by maintainer
+  * Backport to bookworm
+
+ -- Bastien Roucariès <rouca@debian.org>  Tue, 07 May 2024 19:26:27 +0000
+
 fossil (1:2.24-6) unstable; urgency=medium
 
   * Add "Breaks: apache2-bin (<< 2.4.59-1~)" per #1070069 discussion.

Attachment: signature.asc
Description: This is a digitally signed message part.


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

On Mon, 3 Feb 2025 20:18:16 +0000 Jonathan Wiltshire <jmw@debian.org> wrote:

 427 files changed, 45007 insertions(+), 23074 deletions(-)

This is not really workable, particularly since it includes new upstream
releases, changes to the bundled zlib, etc etc. Is the fix to the Apache
regression really not possible to isolate?
I'm closing this, the fix can be isolated, and there seems to be a confusion: the issue is fixed in the client part, not the server part. 

I'm preparing a new PU.

Cheers!
Sylvain Beucler
Debian LTS Team

--- End Message ---
Reply to: