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

Bug#1107854: marked as done (unblock: git/1:2.49.0-2.1)

Your message dated Tue, 24 Jun 2025 19:45:11 +0200
with message-id <a59e7db3-6ee3-4763-80b6-e57b1198fcb9@debian.org>
and subject line Re: Bug#1107854: unblock: git/1:2.49.0-2.1
has caused the Debian Bug report #1107854,
regarding unblock: git/1:2.49.0-2.1
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.)


-- 
1107854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107854
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Control: affects -1 + src:git
X-Debbugs-Cc: git@packages.debian.org
User: release.debian.org@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: jrnieder@gmail.com
Severity: normal

Please unblock package git

This is a preliminary unblock request for the git package.
The version 2.49.0-2 has been uploaded to unstable addressing #1106311
("git: FTBFS: Files COPYING and /usr/share/common-licenses/GPL-2
diffe", severity serious) and #1102106 ("ftbfs on s390x"). The former is
present in testing, the latter is not but blocked migration.
It has been believed that the patch for #1102106 fixed the issue but the
fix was not complete and led to #1106786 ("ftbfs on s390x").

The fix was not complete. After debugging this for a while, I backported
the whole series from upstream addressing the issue and I am able to
confirm that the issue is gone on s390x.

Jonathan Nieder, the git package maintainer, confirmed and this and
wanted to collect the patches and perform an upload, see
	https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106786#32

This did not happen yet so I simply create this unblock request to safe
some time.

The version in testing is 2.47.2 while unstable had 2.49.0 for a while.
This makes diff rather huge (15MiB) therefore I am attaching the diff
against 2.49.0-1.

[ Reason ]
preliminary unblock request to get 2.49.0 into testing.

[ Impact ]
The 2.49.0 in unstable since mid March, the s390x stalled the migration.

[ Tests ]
The testsite is extensive and run as part of the build process.

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

     (Attached debdiff vs -2.49.0-1)

[ Other info ]
I *think* Jonathan manages to perform a regular upload once the request
is approved and he gets to it. However shouldn't he not able to then I
would aim an NMU to get things done for Trixie.

unblock git/1:2.49.0-2.1

Sebastian

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

On 23-06-2025 20:06, Sebastian Andrzej Siewior wrote:

quick question: Is this bug obsolete and can be closed now that this
goes to testing via pu?



It's done. Closing.

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: