Processed: tagging 1060775

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1060775 + upstream
Bug #1060775 [src:tmuxp] tmuxp: flaky autopkgtest: assert 
pane.capture_pane()[1] -> IndexError
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1060775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 1061518

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 1061518
Bug #1061518 {Done: Salvatore Bonaccorso } [general] (no 
subject)
Bug 1061518 is already marked as done; not doing anything.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1061518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: sugar: Stop using webkit2gtk 4.0

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1061531 https://github.com/sugarlabs/sugar/issues/974
Bug #1061531 [src:sugar] sugar: Stop using webkit2gtk 4.0
Set Bug forwarded-to-address to 'https://github.com/sugarlabs/sugar/issues/974'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1061531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1059307: marked as done (ring: CVE-2023-38703)

[Debian Bug Tracking System]

Your message dated Thu, 25 Jan 2024 20:05:14 -0500
with message-id <87zfwsewfp@gnu.org>
and subject line Re: Bug#1059307: ring: CVE-2023-38703
has caused the Debian Bug report #1059307,
regarding ring: CVE-2023-38703
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 ow...@bugs.debian.org
immediately.)


-- 
1059307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ring
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for pjsig, which is
bundled in ring:

CVE-2023-38703[0]:
| PJSIP is a free and open source multimedia communication library
| written in C with high level API in C, C++, Java, C#, and Python
| languages. SRTP is a higher level media transport which is stacked
| upon a lower level media transport such as UDP and ICE. Currently a
| higher level transport is not synchronized with its lower level
| transport that may introduce use-after-free issue. This
| vulnerability affects applications that have SRTP capability
| (`PJMEDIA_HAS_SRTP` is set) and use underlying media transport other
| than UDP. This vulnerability’s impact may range from unexpected
| application termination to control flow hijack/memory corruption.
| The patch is available as a commit in the master branch.

https://github.com/pjsip/pjproject/security/advisories/GHSA-f76w-fh7c-pc66
https://github.com/pjsip/pjproject/commit/6dc9b8c181aff39845f02b4626e0812820d4ef0d
 (2.14)

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-38703
https://www.cve.org/CVERecord?id=CVE-2023-38703

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Hi Moritz,

Thank you for the bug report.  I brought this up with some Jami core
devs, and one of them investigated and told me that Jami's use of
pjsip is not affected by this bug.  As such, I believe we don't have
to do anything for this at this stage, and can close this bug.

Thanks again,
-a--- End Message ---

Bug#1059110: marked as done (chirp: please remove extraneous dependency on python3-future)

[Debian Bug Tracking System]

Your message dated Fri, 26 Jan 2024 01:04:07 +
with message-id 
and subject line Bug#1059110: fixed in chirp 1:20240122-1
has caused the Debian Bug report #1059110,
regarding chirp: please remove extraneous dependency on python3-future
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 ow...@bugs.debian.org
immediately.)


-- 
1059110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chirp
Severity: important


both upstream & debian packaging declare
an old stale extraneousdepency on python3-future.

This lib is RC buggy and being removed.

Please remove these references.

$ grep future -r
test-requirements.txt:future
setup.py:  'future',
requirements.txt:future
debian/control: python3-future,
debian/control: python3-future,



-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: chirp
Source-Version: 1:20240122-1
Done: Dave Hibberd 

We believe that the bug you reported is fixed in the latest version of
chirp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1059...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dave Hibberd  (supplier of updated chirp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 26 Jan 2024 00:04:26 +
Source: chirp
Architecture: source
Version: 1:20240122-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Dave Hibberd 
Closes: 1059110
Changes:
 chirp (1:20240122-1) unstable; urgency=medium
 .
   [ Yogeswaran Umasankar ]
   * New upstream version 20240122.
   * Removed python3-future from d/control
 Build-Depends and Depends. (Closes: #1059110)
   * Patch for replacing python3-future in chrip/chirp_common.py,
 setup.py and requirements files.
   * Revised old patches to fit new upstream version.
   * Fixed lintian warning in copyright.
Checksums-Sha1:
 c404476c7f8c917a555f47543ec146c1dbb390f9 1755 chirp_20240122-1.dsc
 579053fbc0f9a1185dcde153cf206893e81fba1e 1850587 chirp_20240122.orig.tar.gz
 bdb3940d6a86c0316e9fe68e9ebe3dbcfdf08959 10436 chirp_20240122-1.debian.tar.xz
 9cafd5fe444b42f225eb8ec0e6980dccde8fcc91 11073 chirp_20240122-1_amd64.buildinfo
Checksums-Sha256:
 8f6509ea034ef8dbe219c10570a4843ed82da9b37f503c71f9543f205f8b8d19 1755 
chirp_20240122-1.dsc
 c74656cdae9d43349a777d2c04ec0fdfa6302bb4156ea85197070cccec8e0b0a 1850587 
chirp_20240122.orig.tar.gz
 cd126f40628cc5bcd5e7b47b357b5e53f7ae48ad4449a47c7d32df6723d53e28 10436 
chirp_20240122-1.debian.tar.xz
 f7b8138df631aec61892123bd07d25edbcb6c1fedf87d28c94962f3760e9 11073 
chirp_20240122-1_amd64.buildinfo
Files:
 96099a5c6cda77bec4ccc764fc43c979 1755 hamradio optional chirp_20240122-1.dsc
 59de47217f0c04cbb432a8bcfdbf736a 1850587 hamradio optional 
chirp_20240122.orig.tar.gz
 f8d833437e9a1d03a76ca79c21a43104 10436 hamradio optional 
chirp_20240122-1.debian.tar.xz
 b657a03049b3a10840ccd9cb14278b18 11073 hamradio optional 
chirp_20240122-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEXk9UUZPolpyKWbgKA6H7ehkEdxsFAmWy/4MACgkQA6H7ehkE
dxtneggAi0Xk+FvUS/IqguONUtU4T+3J2VPNhNjL3pxDByDo4aXyl3xRfnBXEnHJ
6rcI7lAm6Yi72zuDrZTrAe8GwyVAh27pf7KyITwU4NnOaS48jkIl0sxYY04fG5La
yrA7ZhsmyC/WD5JAT0DtrAUsd/3d915go0TxxKs5EODPLp2J71TSG3d5+vEd5gTj
+3qb7TPlUtFD+kQeW4h3iY5Ij6e1yvJ2+WGzJpAQJb8T9RA+UoKKKlIfeWLHXz6y
/HQMXBGBml+nbzTJTsJqSkDvpkkVForqTV6Tth5Ca6YLrUc6pFTkzl+f6RhN1ZLE
wE0U2qRG5KCw63MHkhraI6BJ0NMYOg==
=Fv+w
-END PGP SIGNATURE End Message ---

Bug#1061531: sugar: Stop using webkit2gtk 4.0

[Jeremy Bícha]

Source: sugar
Version: 0.120-1
Severity: serious
Tags: trixie sid
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: webkit-4.0

The webkit2gtk maintainers intend to stop building the 4.0 API soon.
Please switch to using the 4.1 API which is the same as the 4.0 API
except that it uses libsoup3 instead of libsoup2.4.

There is some documentation and many examples of libsoup2.4 porting at
https://gitlab.gnome.org/GNOME/libsoup/-/issues/218

By the way, it is not possible to use libsoup2.4 and libsoup3 in the
same process. I don't think this is a problem in the Debian archive
for Sugar beyond sugar-browse-activity. And in that case,
sugar-browse-activity was ported to libsoup3 first and appears to
still work fine.

On behalf of the webkit2gtk maintainers,
Jeremy Bícha

Bug#1061530: sugar-browse-activity: Stop using webkit2gtk 4.0

[Jeremy Bícha]

Source: sugar-browse-activity
Version: 207-2
Severity: serious
Tags: patch trixie sid
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: webkit-4.0
Forwarded: 
https://salsa.debian.org/jbicha/sugar-browse-activity/-/commits/webkit

The webkit2gtk maintainers intend to stop building the 4.0 API soon.
Please switch to using the 4.1 API which is the same as the 4.0 API
except that it uses libsoup3 instead of libsoup2.4.

My colleague has submitted a patch for this issue. It works for me
even though Sugar itself is still using libsoup2.4 and webkit2gtk 4.0.
I have cherry-picked the patch to my fork of your repo in the webkit
branch.

https://salsa.debian.org/jbicha/sugar-browse-activity/-/commits/webkit

On behalf of the webkit2gtk maintainers,
Jeremy Bícha

Bug#1061526: astroidmail: Stop using webkit2gtk 4.0

[Jeremy Bícha]

Source: astroidmail
Version: 0.16-2
Severity: serious
Tags: trixie sid
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: webkit-4.0

The webkit2gtk maintainers intend to stop building the 4.0 API soon.
Please switch to using the 4.1 API which is the same as the 4.0 API
except that it uses libsoup3 instead of libsoup2.4.

Unfortunately, astroidmail uses libsoup directly so it is necessary to
port it from libsopu2.4 to libsoup3 to fix this issue.

There is some documentation and many examples at
https://gitlab.gnome.org/GNOME/libsoup/-/issues/218

On behalf of the webkit2gtk maintainers,
Jeremy Bícha

Bug#1060413: marked as done (src:emacs-posframe: fails to migrate to testing for too long: uploader built arch:all binary)

[Debian Bug Tracking System]

Your message dated Thu, 25 Jan 2024 22:04:14 +
with message-id 
and subject line Bug#1060413: fixed in emacs-posframe 1.4.2-1.1
has caused the Debian Bug report #1060413,
regarding src:emacs-posframe: fails to migrate to testing for too long: 
uploader built arch:all binary
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 ow...@bugs.debian.org
immediately.)


-- 
1060413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: emacs-posframe
Version: 1.1.7-3
Severity: serious
Control: close -1 1.4.2-1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:emacs-posframe has been trying to migrate 
for 33 days [2]. Hence, I am filing this bug.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=emacs-posframe



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: emacs-posframe
Source-Version: 1.4.2-1.1
Done: Paul Gevers 

We believe that the bug you reported is fixed in the latest version of
emacs-posframe, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1060...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated emacs-posframe package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 10 Jan 2024 21:54:50 +0100
Source: emacs-posframe
Architecture: source
Version: 1.4.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Paul Gevers 
Closes: 1060413
Changes:
 emacs-posframe (1.4.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1060413)
Checksums-Sha1:
 3df3d44aea4eb1510fa2c9007a86852b5c1145f7 1755 emacs-posframe_1.4.2-1.1.dsc
 110355603b68ec8df713e4bfbb4554617921ff76 2036 
emacs-posframe_1.4.2-1.1.debian.tar.xz
Checksums-Sha256:
 d7d9b6fc13ea8c146ae8c3a23f9ff01927518b294421297aec45563d93b24acf 1755 
emacs-posframe_1.4.2-1.1.dsc
 b5bce1faae45ff40846f231d1addefccf87a3b16d6285ce37ceeafde9700999c 2036 
emacs-posframe_1.4.2-1.1.debian.tar.xz
Files:
 aefd49071aaa21d86beabc0b0e9438ab 1755 editors optional 
emacs-posframe_1.4.2-1.1.dsc
 9a16e8201eb37ea58162183296a345b3 2036 editors optional 
emacs-posframe_1.4.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmWfBGMACgkQnFyZ6wW9
dQo0LQgAtn7X1EX9NbU1bppdLCrYsiPVjPI4qg+RzX2QN+CAGeE0pjpvxrV5zv/g
pqw1wvQ8eY6RFNmrEMUY3ZnmMZyej6saUiwVBqynIxkfMd5SZ+p4hCcKS9hNRisW
b8qtpJDBUt8g2ShvZe2DHXj3wHoysmHZ/nGXFGUtmS3gva5ISOaPRbqQzr7IEvAP
BgZqJ0IrxBrj6P9EKg9Sw1l2XolkoFUqquzNhQzewgsXnfytHtr2Nf5EgonPJp2L

Bug#1061522: atril: CVE-2023-52076

[Salvatore Bonaccorso]

Source: atril
Version: 1.26.1-4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for atril.

CVE-2023-52076[0]:
| Atril Document Viewer is the default document reader of the MATE
| desktop environment for Linux. A path traversal and arbitrary file
| write vulnerability exists in versions of Atril prior to 1.26.2.
| This vulnerability is capable of writing arbitrary files anywhere on
| the filesystem to which the user opening a crafted document has
| access. The only limitation is that this vulnerability cannot be
| exploited to overwrite existing files, but that doesn't stop an
| attacker from achieving Remote Command Execution on the target
| system. Version 1.26.2 of Atril contains a patch for this
| vulnerability.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-52076
https://www.cve.org/CVERecord?id=CVE-2023-52076
[1] 
https://github.com/mate-desktop/atril/security/advisories/GHSA-6mf6-mxpc-jc37
[2] 
https://github.com/mate-desktop/atril/commit/e70b21c815418a1e6ebedf6d8d31b8477c03ba50

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: reassign 1061521 to src:linux, severity of 1061521 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1061521 src:linux 6.6.13-1
Bug #1061521 [linux-image-6.6.13-amd64] linux-image-6.6.13-amd64: 6.6.13-1 no 
more keyboard resuming from suspend
Bug reassigned from package 'linux-image-6.6.13-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/6.6.13+1.
Ignoring request to alter fixed versions of bug #1061521 to the same values 
previously set
Bug #1061521 [src:linux] linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard 
resuming from suspend
Marked as found in versions linux/6.6.13-1.
> severity 1061521 important
Bug #1061521 [src:linux] linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard 
resuming from suspend
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1061521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061521: linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

On Thu, Jan 25, 2024 at 10:01:04PM +0100, r2rien wrote:
> Package: linux-image-6.6.13-amd64
> Version: 6.6.13-1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: deb...@r2rien.net
> 
> Resuming from suspend keyboard totally unresponsive, thus no sysrq, no tty to
> the rescue, only power button.
> Stuck in gdm3 login screen,
> thus impossible to type password to unlock gnome-session
> I tagged it as grave so people with apt-listbugs could be informed

Please do provide some more information. Is this a regression from
6.6.11-1. In case yes, can you please try to bisect the changes in
upstreams 6.6.11 to 6.6.13 so we can isolate which change causes it?

When you resume from suspend, do you get anything logged in the kernel
log, can you attach it here?

Regards,
Salvatore

Processed: Re: Bug#1061521: linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1061521 [linux-image-6.6.13-amd64] linux-image-6.6.13-amd64: 6.6.13-1 no 
more keyboard resuming from suspend
Added tag(s) moreinfo.

-- 
1061521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061315: inn2 ftbfs with Python 3.12 as the default

[Julien ÉLIE]

Hi Matthias,

looking at m4/python.m4, this comes from getting the configuration out 
of the sysconfig module.


and _sysconfigdata_* has:

  'LOCALMODLIBS': '-lm  -lm   -lz -lm -lm   -lexpat  -lexpat '
  'Modules/_hacl/libHacl_Hash_SHA2.a -lz',


So, I'm not sure, how to better get the required information for 
linking, but this interface doesn't look very reliable.


maybe better use: python3-config --embed --libs


Oh, yes, your proposal to use python3-config is far better.
After testing, "python3-config --libs" is enough; there's no need in 
adding "--embed" as the "-lpython3.12" flag otherwise appears twice in 
PYTHON_LIBS.


Also, if python3-config (which may also be python2-config, python-config 
or any other variant) is not installed, I've kept the current check just 
to be sure we'll still have something.



I've opened a PR upstream:

https://github.com/rra/rra-c-util/pull/18/commits/63e4ddf8683c8c1dc429043ca8af7984eff21140

Thanks again.

--
Julien ÉLIE

« Le cercle est le plus long chemin d'un point au même point. » (Tom
  Stoppard, _Every Good Boy Deserves Favour_)

Bug#1057447: broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers'

[Steev Klimaszewski]

Does the cloud kernel even have wireless enabled?  My understanding
was the cloud kernels do not enable wireless.

Bug#1061521: linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend

[r2rien]

Package: linux-image-6.6.13-amd64
Version: 6.6.13-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: deb...@r2rien.net

Resuming from suspend keyboard totally unresponsive, thus no sysrq, no tty to
the rescue, only power button.
Stuck in gdm3 login screen,
thus impossible to type password to unlock gnome-session
I tagged it as grave so people with apt-listbugs could be informed


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (991, 'testing'), (990, 'unstable'), (600, 'stable'), (90, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.11-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US:en.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-6.6.13-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod31-1
ii  linux-base  4.9

Versions of packages linux-image-6.6.13-amd64 recommends:
pn  apparmor 
ii  firmware-linux-free  20200122-2

Versions of packages linux-image-6.6.13-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.12-1
pn  linux-doc-6.6   

Bug#1061519: shim: CVE-2023-40546 CVE-2023-40547 CVE-2023-40548 CVE-2023-40549 CVE-2023-40550 CVE-2023-40551

[Salvatore Bonaccorso]

Source: shim
Version: 15.7-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 15.7-1~deb11u1

Hi,

The following vulnerabilities were published for shim.

According to [6]:

* Various CVE fixes:
  CVE-2023-40546 mok: fix LogError() invocation
  CVE-2023-40547 - avoid incorrectly trusting HTTP headers
  CVE-2023-40548 Fix integer overflow on SBAT section size on 32-bit system
  CVE-2023-40549 Authenticode: verify that the signature header is in bounds.
  CVE-2023-40550 pe: Fix an out-of-bound read in verify_buffer_sbat()
  CVE-2023-40551: pe-relocate: Fix bounds check for MZ binaries

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-40546
https://www.cve.org/CVERecord?id=CVE-2023-40546
[1] https://security-tracker.debian.org/tracker/CVE-2023-40547
https://www.cve.org/CVERecord?id=CVE-2023-40547
[2] https://security-tracker.debian.org/tracker/CVE-2023-40548
https://www.cve.org/CVERecord?id=CVE-2023-40548
[3] https://security-tracker.debian.org/tracker/CVE-2023-40549
https://www.cve.org/CVERecord?id=CVE-2023-40549
[4] https://security-tracker.debian.org/tracker/CVE-2023-40550
https://www.cve.org/CVERecord?id=CVE-2023-40550
[5] https://security-tracker.debian.org/tracker/CVE-2023-40551
https://www.cve.org/CVERecord?id=CVE-2023-40551
[6] https://github.com/rhboot/shim/releases/tag/15.8

Regards,
Salvatore

Processed: shim: CVE-2023-40546 CVE-2023-40547 CVE-2023-40548 CVE-2023-40549 CVE-2023-40550 CVE-2023-40551

[Debian Bug Tracking System]

Processing control commands:

> found -1 15.7-1~deb11u1
Bug #1061519 [src:shim] shim: CVE-2023-40546 CVE-2023-40547 CVE-2023-40548 
CVE-2023-40549 CVE-2023-40550 CVE-2023-40551
Marked as found in versions shim/15.7-1~deb11u1.

-- 
1061519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 1061518

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 1061518
Bug #1061518 [general] (no subject)
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1061518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061518: closing 1061518

[Salvatore Bonaccorso]

close 1061518 
thanks

Bug#1061517: closing 1061517

[Salvatore Bonaccorso]

close 1061517 
thanks

Processed: closing 1061517

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 1061517
Bug #1061517 [asasasasasa] shgfpuahgañsfgn
Warning: Unknown package 'asasasasasa'
Marked Bug as done
Warning: Unknown package 'asasasasasa'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1061517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061518: (no subject)

[other]

Package: general
Severity: serious
X-Debbugs-Cc: a...@a.com, h...@test.com

Processed: Bug#1061272 marked as pending in sudo

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1061272 [src:sudo] sudo: Does not build from prefered source
Added tag(s) pending.

-- 
1061272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061272: marked as pending in sudo

[Marc Haber]

Control: tag -1 pending

Hello,

Bug #1061272 in sudo reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/sudo-team/sudo/-/commit/3d86b138d4dd9268f1dd6fab8b1d177393786fe7


add --with-devel configure option

Thanks: Bastien Roucariès
Closes: #1061272


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1061272

Bug#1061517: shgfpuahgañsfgn

[other]

Package: asasasasasa
Severity: serious
X-Debbugs-Cc: a...@a.com, h...@test.com




-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
PT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-13-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1060791: marked as done (pbcopper: switch to default version of boost)

[Debian Bug Tracking System]

Your message dated Thu, 25 Jan 2024 19:36:03 +
with message-id 
and subject line Bug#1060791: fixed in pbcopper 2.3.0+dfsg-2
has caused the Debian Bug report #1060791,
regarding pbcopper: switch to default version of boost
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 ow...@bugs.debian.org
immediately.)


-- 
1060791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pbcopper
Version: 2.2.0+dfsg-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

boost1.81 is scheduled for removal. Please switch the (Build-)Depends of
pbcopper to use boost1.83 or the unversioned boost packages. If
possible, the latter is preferred for future boost transitions.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: pbcopper
Source-Version: 2.3.0+dfsg-2
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
pbcopper, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1060...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated pbcopper package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 25 Jan 2024 20:05:13 +0100
Source: pbcopper
Architecture: source
Version: 2.3.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1060791
Changes:
 pbcopper (2.3.0+dfsg-2) unstable; urgency=medium
 .
   * Build-Depends: s/libboost1.81-dev/libboost-dev/
 Closes: #1060791
Checksums-Sha1:
 2f076b82cdf52fe921ed64ec99b00170f1933907 2379 pbcopper_2.3.0+dfsg-2.dsc
 a04cccf7a845e38a7f199658bee72497e2bcf2af 7728 
pbcopper_2.3.0+dfsg-2.debian.tar.xz
 09ece2714e0743313d85825f5c203b565e1b2f03 8714 
pbcopper_2.3.0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 86a503a090370e5b7601bef12b5c899b6ac252be1911ec6c1a46155129564203 2379 
pbcopper_2.3.0+dfsg-2.dsc
 249fa94ccac19d58f1261847b2e11aa8c4c167b45ed7283ac8c772d18860dc6e 7728 
pbcopper_2.3.0+dfsg-2.debian.tar.xz
 15adfd74c1480bea65254a884f4791cef229640650d697939c71db81d68b 8714 
pbcopper_2.3.0+dfsg-2_amd64.buildinfo
Files:
 d51fd4e4e2027e76e5d2f12c4f7c0037 2379 science optional 
pbcopper_2.3.0+dfsg-2.dsc
 accfafab8a2cb6ccd40e84c7c839a6bd 7728 science optional 
pbcopper_2.3.0+dfsg-2.debian.tar.xz
 d70c756e7fa205838bd4b4081995302d 8714 science optional 
pbcopper_2.3.0+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmWysg4RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHiCg/+M9KFsrBfNj7L+39cbDilwq8TO1bX1KWS
CO/vuvGR4ppaIe3P5rIlnJ1ZqAViZdbGTLRSoAYtHIVY5KT5x/JzLJZo22rqRIr1
qCObH9hMs+RNTYNb2aWURwiR7vc8l1XUjoCq+le3pXn99yH+yUd/kP0cyk1H/qJl
7QpVDPNNzGX7LV52wEW+UwTHGMfBChSbt5PLEBUm1HIpwmD2A1oVj1Lh81OW0lpj
hTKhDnMtOLiiwmIQLE12z3YYlMF8yVi66CJAD4efwgi1nmcCSY9DX27WgQ44ZU1s
dFMPtG+/ZIs2K+ojt7jBFoDAV7VQJBasqGVm8fFRSALCLPD1aLsuTpJ3GrE/LEJL
FS9CioSH1jJMOSFDyydIgQO4CwogNOlTfVWSA0ltzEnk/YtI1C1pvlVrhnojUScW
ErBtk4wOym8vukQQwlvOc2LdrLnxrlcgzkT8+ELDCSfuiaspVWSGe8m/1GAyWDBj
skwo1SaAM6isphKB3Ui+/a4qYWB4f34EDFZACgBEGeBJmUdN5khEOL2+6rnj55ve
EjBlnTJk3UAZ5zY7EAM02Q7qWRu7Y3vMctEPq0+8nD+ekJwx1FqTrDiWdFFyD1Gu
/gdG1f3Y6xjYiyC+0wEYCOAtBZ3r2LgZO+X0esVWAHPgUKF0plYqayJiqVuhXjaM
ve2/UtuI9qc=
=yXCp
-END PGP SIGNATURE End Message ---

Bug#1061499: libgssglue: disable gsasl-dovecot-gssapi-heimdal autopkgtests on armhf, re-enable them on i386

[Simon Josefsson]

Thank you -- I am uploading a newly built package with your patch.

/Simon


signature.asc
Description: PGP signature

Bug#1061456: marked as done (src:pmacct: fails to migrate to testing for too long: Build-Depends not available on s390x)

[Debian Bug Tracking System]

Your message dated Thu, 25 Jan 2024 18:19:15 +
with message-id 
and subject line Bug#1061456: fixed in pmacct 1.7.8-2
has caused the Debian Bug report #1061456,
regarding src:pmacct: fails to migrate to testing for too long: Build-Depends 
not available on s390x
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 ow...@bugs.debian.org
immediately.)


-- 
1061456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: pmacct
Version: 1.7.7-1
Severity: serious
Control: close -1 1.7.8-1
X-Debbugs-CC: Boyuan Yang 
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:pmacct has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable has a new 
Build-Depends that's not available on s390x.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=pmacct



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pmacct
Source-Version: 1.7.8-2
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
pmacct, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated pmacct package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 25 Jan 2024 12:57:41 -0500
Source: pmacct
Architecture: source
Version: 1.7.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Closes: 1061456
Changes:
 pmacct (1.7.8-2) unstable; urgency=medium
 .
   * QA upload.
   * debian/control:
 + Disable libndpi-dev on s390x and !linux-any. (Closes: #1061456)
 + Remove kfreebsd packages.
   * debian/rules: Ditto.
Checksums-Sha1:
 f87c3951f243cbfc12c1e455bab8ad17cfa67743 2075 pmacct_1.7.8-2.dsc
 3e0e77d5bef95f645ac5a6601962221c600abd6b 2175335 pmacct_1.7.8.orig.tar.gz
 ee825b7ce33bc3ccc158e8eb4c3ce1759659506f 13336 pmacct_1.7.8-2.debian.tar.xz
 31e2e13cb2e3d757b4b4d40efa78256a1be228a6 8594 pmacct_1.7.8-2_amd64.buildinfo
Checksums-Sha256:
 a535cdd19e62de85787166ad0c2619aa2259694021ad8ee6bb9120d9761f4b65 2075 
pmacct_1.7.8-2.dsc
 4df50a3c6c7bdace3345bbf3bd4f6fa7a6722ec1fb45dfd266ad956b327da98a 2175335 
pmacct_1.7.8.orig.tar.gz
 42573c7f382d6a46982ede3dc1e52f761cece1db4255c05d759308223578bee8 13336 
pmacct_1.7.8-2.debian.tar.xz
 5b301dcfca50566a6213ecc93d2e5e85c3abddc54de213bc5c49222dea55aef4 8594 
pmacct_1.7.8-2_amd64.buildinfo
Files:
 97cef2bfd20d4541e96eeefe16f80784 2075 net optional pmacct_1.7.8-2.dsc
 35a1de30d9f089bf260b9704ab383666 2175335 net optional pmacct_1.7.8.orig.tar.gz
 67e28e7c901bc34aade37e5c3a3067c2 13336 net optional 
pmacct_1.7.8-2.debian.tar.xz
 91ac716c4399a2ed4a1b471c18d82d2b 8594 net optional 
pmacct_1.7.8-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1058146: marked as done (androguard: FTBFS: RecursionError: maximum recursion depth exceeded while pickling an object)

[Debian Bug Tracking System]

Your message dated Thu, 25 Jan 2024 18:07:44 +
with message-id 
and subject line Bug#1058146: fixed in androguard 3.4.0~a1-9
has caused the Debian Bug report #1058146,
regarding androguard: FTBFS: RecursionError: maximum recursion depth exceeded 
while pickling an object
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 ow...@bugs.debian.org
immediately.)


-- 
1058146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: androguard
Version: 3.4.0~a1-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="LC_ALL=C.UTF-8 {interpreter} -m 
> pytest --verbose" dh_auto_test
> I: pybuild base:310: LC_ALL=C.UTF-8 python3.12 -m pytest --verbose
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0 -- 
> /usr/bin/python3.12
> cachedir: .pytest_cache
> rootdir: /<>
> collecting ... collected 161 items
> 
> tests/dataflow_test.py::DataflowTest::testDefUseGCD PASSED   [  
> 0%]
> tests/dataflow_test.py::DataflowTest::testDefUseIfBool PASSED[  
> 1%]
> tests/dataflow_test.py::DataflowTest::testGroupVariablesGCD PASSED   [  
> 1%]
> tests/dataflow_test.py::DataflowTest::testGroupVariablesIfBool PASSED[  
> 2%]
> tests/dataflow_test.py::DataflowTest::testReachDefGCD PASSED [  
> 3%]
> tests/dataflow_test.py::DataflowTest::testSplitVariablesGCD PASSED   [  
> 3%]
> tests/dataflow_test.py::DataflowTest::testSplitVariablesIfBool PASSED[  
> 4%]
> tests/dominator_test.py::DominatorTest::testCrossGraph PASSED[  
> 4%]
> tests/dominator_test.py::DominatorTest::testFifthGraph PASSED[  
> 5%]
> tests/dominator_test.py::DominatorTest::testFirstGraph PASSED[  
> 6%]
> tests/dominator_test.py::DominatorTest::testFourthGraph PASSED   [  
> 6%]
> tests/dominator_test.py::DominatorTest::testLinearVitGraph PASSED[  
> 7%]
> tests/dominator_test.py::DominatorTest::testSecondGraph PASSED   [  
> 8%]
> tests/dominator_test.py::DominatorTest::testTVerifyGraph PASSED  [  
> 8%]
> tests/dominator_test.py::DominatorTest::testTarjanGraph PASSED   [  
> 9%]
> tests/dominator_test.py::DominatorTest::testThirdGraph PASSED[  
> 9%]
> tests/rpo_test.py::RpoTest::testCrossGraph PASSED[ 
> 10%]
> tests/rpo_test.py::RpoTest::testFifthGraph PASSED[ 
> 11%]
> tests/rpo_test.py::RpoTest::testFirstGraph PASSED[ 
> 11%]
> tests/rpo_test.py::RpoTest::testFourthGraph PASSED   [ 
> 12%]
> tests/rpo_test.py::RpoTest::testLinearVitGraph PASSED[ 
> 13%]
> tests/rpo_test.py::RpoTest::testSecondGraph PASSED   [ 
> 13%]
> tests/rpo_test.py::RpoTest::testTVerifyGraph PASSED  [ 
> 14%]
> tests/rpo_test.py::RpoTest::testTarjanGraph PASSED   [ 
> 14%]
> tests/rpo_test.py::RpoTest::testThirdGraph PASSED[ 
> 15%]
> tests/test_analysis.py::AnalysisTest::testAPK PASSED [ 
> 16%]
> tests/test_analysis.py::AnalysisTest::testAnalysis PASSED[ 
> 16%]
> tests/test_analysis.py::AnalysisTest::testDex PASSED [ 
> 17%]
> tests/test_analysis.py::AnalysisTest::testExtends PASSED [ 
> 18%]
> tests/test_analysis.py::AnalysisTest::testInterfaces PASSED  [ 
> 18%]
> tests/test_analysis.py::AnalysisTest::testMultiDexExternal PASSED[ 
> 19%]
> tests/test_analysis.py::AnalysisTest::testMultidex PASSED[ 
> 19%]
> tests/test_analysis.py::AnalysisTest::testPermissions PASSED [ 
> 20%]
> tests/test_analysis.py::AnalysisTest::testXrefOffsets PASSED [ 
> 21%]
> tests/test_analysis.py::AnalysisTest::testXrefOffsetsFields PASSED   [ 
> 21%]
> tests/test_analysis.py::AnalysisTest::testXrefs PASSED   [ 
> 22%]
> tests/test_annotations.py::AnnotationTest::testAnnotation PASSED [ 
> 22%]
> tests/test_apk.py::APKTest::testAPK PASSED   [ 
> 23%]
> tests/test_apk.py::APKTest::testAPKActivitiesAreString PASSED[ 
> 24%]
> tests/test_apk.py::APKTest::testAPKCert PASSED  

Bug#989166: marked as done (Error: package or namespace load failed for ‘gtools’)

[Debian Bug Tracking System]

Your message dated Thu, 25 Jan 2024 09:53:32 -0600
with message-id <26034.33788.777162.908...@rob.eddelbuettel.com>
and subject line Closing stale and outdated bug report
has caused the Debian Bug report #989166,
regarding Error: package or namespace load failed for ‘gtools’
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 ow...@bugs.debian.org
immediately.)


-- 
989166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-gtools
Version: 3.8.1-1
Severity: grave
Justification: renders package unusable

Hi,

$ R -e 'library(gtools)'
R version 3.5.2 (2018-12-20) -- "Eggshell Igloo"
Copyright (C) 2018 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

  Natural language support but running in an English locale

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> library(gtools)
Error: package or namespace load failed for ‘gtools’:
 package ‘gtools’ was installed by an R version with different internals; it 
needs to be reinstalled for use with this R version
Execution halted


Note: This is only happening on stable.  The version in testing
and unstable is fine.

Kind regards
Andreas.

-- System Information:
Debian Release: 10.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (50, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages r-cran-gtools depends on:
ii  libc62.28-10
ii  r-base-core [r-api-3.5]  3.5.2-1

r-cran-gtools recommends no packages.

r-cran-gtools suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org--- End Message ---

Bug#1061502: virtaal: Please drop Build-Depends python3-libproxy

[Jeremy Bícha]

Source: virtaal
Version: 0.7.1+git20191021+ds1-2
Severity: serious
Tags: ftbfs sid trixie

virtaal Build-Depends on python3-libproxy, but this dependency is not
required for the build.

libproxy 0.5 no longer provides Python 3 bindings. Because it is
expected that Debian 13 will ship with libproxy 0.5, I am dropping the
python3-libproxy package now.

Thank you,
Jeremy Bícha

Bug#1057381: marked as done (FTBFS: error: invalid use of incomplete typedef ‘WINDOW’)

[Debian Bug Tracking System]

Your message dated Thu, 25 Jan 2024 15:34:45 +
with message-id 
and subject line Bug#1057381: fixed in aalib 1.4p5-51
has caused the Debian Bug report #1057381,
regarding FTBFS: error: invalid use of incomplete typedef ‘WINDOW’
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 ow...@bugs.debian.org
immediately.)


-- 
1057381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aalib
Version: 1.4p5-50
Severity: serious
Tags: ftbfs

Rebuilding your package in unstable currently fails:


libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-I/usr/include -I/usr/include/ncurses -c aacurses.c  -fPIC -DPIC -o 
.libs/aacurses.o
aacurses.c: In function ‘curses_getsize’:
aacurses.c:80:20: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
‘struct _win_st’}
   80 | *width = stdscr->_maxx + 1;
  |^~
aacurses.c:81:21: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
‘struct _win_st’}
   81 | *height = stdscr->_maxy + 1;
  | ^~
make[4]: *** [Makefile:726: aacurses.lo] Error 1
make[4]: Leaving directory '/<>/src'
make[3]: *** [Makefile:483: all] Error 2
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile:492: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


Best,
Chris
--- End Message ---
--- Begin Message ---
Source: aalib
Source-Version: 1.4p5-51
Done: Jonathan Carter 

We believe that the bug you reported is fixed in the latest version of
aalib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated aalib package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 25 Jan 2024 17:07:26 +0200
Source: aalib
Architecture: source
Version: 1.4p5-51
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Carter 
Changed-By: Jonathan Carter 
Closes: 1057381
Changes:
 aalib (1.4p5-51) unstable; urgency=medium
 .
   * Accept MR: Fix Netscape typo
 - https://salsa.debian.org/debian/aalib/-/merge_requests/2
   * Accept patch to fix ftbfs (Closes: #1057381):
 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057381
   * Update standards version to 4.6.2
Checksums-Sha1:
 22e9f3736a056b105ed944b23fea07dfde8b791f 2033 aalib_1.4p5-51.dsc
 a23269e950a249d2ef93625837cace45ddbce03b 391028 aalib_1.4p5.orig.tar.gz
 816ad567fc62d24f85165ada105a76b04f8f6d4e 16876 aalib_1.4p5-51.debian.tar.xz
 5e1c72ead068348c28a2624f3284368a104891f2 6686 aalib_1.4p5-51_source.buildinfo
Checksums-Sha256:
 0703b1369e956a04ed75204ecbb04cd428b3f1ffaada000e761913ff039c2958 2033 
aalib_1.4p5-51.dsc
 fbddda9230cf6ee2a4f5706b4b11e2190ae45f5eda1f0409dc4f99b35e0a70ee 391028 
aalib_1.4p5.orig.tar.gz
 7302df1cfe1c5358ba8f0018e967999b6b15b92450dd39f462ebd57b08ebccaa 16876 
aalib_1.4p5-51.debian.tar.xz
 8bbb1ba9d33bd9c3d1b37bc70b05ff497242de1fedd348b1d37789584bd54e8e 6686 
aalib_1.4p5-51_source.buildinfo
Files:
 d0de67d9e320df8ff778e7c8de5905e6 2033 libs optional aalib_1.4p5-51.dsc
 9801095c42bba12edebd1902bcf0a990 391028 libs optional aalib_1.4p5.orig.tar.gz
 228a448bbf9046ed3261b59d6bbb1264 16876 libs optional 
aalib_1.4p5-51.debian.tar.xz
 508d01f35139582676c88bb6638dd40f 6686 libs optional 
aalib_1.4p5-51_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAmWyfGkPHGpjY0BkZWJp
YW4ub3JnAAoJELAdGnKsjcmh6qYQALRYz3OuXpDHW5YhVlFj4ef3j1H/+b4uZOAi
a0Ao5F9Qzopkhlws9hJ7hW4avIVeLAtpl5YZ+atnflkUr+ASzZETGA1NYvg6MC28
8y0ZKQSbhb08KlCSQLsQxaSAb35eTutQRXaakPoLOaqTnihdPyXbh0EHL+6aSOpr
xLr37b3QDR2c4JLI/2bZv81gvgIje+VVeGweCGKpZolLhSgPjKtr4QfhQXcjhxb1
IoFNbzHDlWnoEG83SCrcNjzT7qOje7lmFquuYqCB/lkM9hq8goGn4nSZOJSFx7IU

Bug#1061501: libvorbis: Please disable test-coupling-segfault autopkgtest on armhf

[Emanuele Rocca]

Source: libvorbis
Version: 1.3.7-1
Severity: serious
User: debian-...@lists.debian.org
Usertags: 32bit-stackclash
Tags: patch

Hi,

the autopkgtest test-coupling-segfault currently fails on armhf due to
valgrind bug https://bugs.debian.org/1061496.

Please disable the test for now, it can be re-enabled once the valgrind
issue is fixed. Patch attached.

Thanks,
  Emanuele
diff -Nru libvorbis-1.3.7/debian/changelog libvorbis-1.3.7/debian/changelog
--- libvorbis-1.3.7/debian/changelog	2020-09-27 16:13:53.0 +0200
+++ libvorbis-1.3.7/debian/changelog	2024-01-25 16:25:09.0 +0100
@@ -1,3 +1,11 @@
+libvorbis (1.3.7-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable test-coupling-segfault on armhf due to valgrind bug #1061496.
+(Closes: #XXX)
+
+ -- Emanuele Rocca   Thu, 25 Jan 2024 16:25:09 +0100
+
 libvorbis (1.3.7-1) unstable; urgency=medium
 
   * Team upload
diff -Nru libvorbis-1.3.7/debian/tests/control libvorbis-1.3.7/debian/tests/control
--- libvorbis-1.3.7/debian/tests/control	2020-09-27 16:05:13.0 +0200
+++ libvorbis-1.3.7/debian/tests/control	2024-01-25 16:24:06.0 +0100
@@ -1,2 +1,6 @@
-Depends: @, vorbis-tools, build-essential, sound-theme-freedesktop, sound-icons, valgrind
-Tests: test-examples test-coupling-segfault
+Depends: @, vorbis-tools, build-essential, sound-theme-freedesktop
+Tests: test-examples
+
+Depends: @, vorbis-tools, sound-icons, valgrind
+Tests: test-coupling-segfault
+Architecture: !armhf

Processed: Re: Bug#1061315: inn2 ftbfs with Python 3.12 as the default

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1061315 [src:inn2] inn2 ftbfs with Python 3.12 as the default
Added tag(s) patch.

-- 
1061315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061315: inn2 ftbfs with Python 3.12 as the default

[Matthias Klose]

Control: tags -1 + patch

On 22.01.24 21:31, Julien ÉLIE wrote:

Hi Matthias,


Package: src:inn2
Version: 2.7.2~20231223-1
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

with python3-defaults from experimental:

[...]
checking for Python.h... yes
checking for Py_Initialize... no
configure: error: in `/<>/build':
configure: error: unable to link with Python library
See `config.log' for more details


Could you put the end of the config.log file? (the part showing the 
failure to find Py_Initialize)


Maybe a problem of Python not in the path?


FWIW, I do not run trixie, but building INN with a downloaded version of 
Python 3.12 on bookworm works for me:


checking for flags to link with Python... -L/home/news/work/py3.12.1/lib 
-lpython3.12 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic

checking Python.h usability... yes
checking Python.h presence... yes
checking for Python.h... yes
checking for Py_Initialize... yes


configure:15028: checking for Py_Initialize
configure:15028: gcc -o conftest -g -O2 
-I/home/news/work/py3.12.1/include/python3.12   conftest.c 
-L/home/news/work/py3.12.1/lib -lpython3.12 -lpthread -ldl -lutil -lm 
-Xlinker -export-dynamic   >&5


configure:15777: checking for Py_Initialize
configure:15777: gcc -o conftest -g -O2 -fno-omit-frame-pointer 
-mno-omit-leaf-frame-pointer -ff
ile-prefix-map=/home/packages/tmp/inn2-2.7.2~20231223=. -flto=auto 
-ffat-lto-objects -fstack-pro
tector-strong -fstack-clash-protection -Wformat -Werror=format-security 
-fcf-protection -fdebug-
prefix-map=/home/packages/tmp/inn2-2.7.2~20231223=/usr/src/inn2-2.7.2~20231223-1build2 
-I/usr/in
clude/python3.12 -Wdate-time -D_FORTIFY_SOURCE=3 
-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-o
bjects -Wl,-z,relro -Wl,-z,now conftest.c -L/usr/lib/x86_64-linux-gnu 
-lpython3.12 -ldl -lm -lm
-lm -lz -lm -lm -lexpat -lexpat Modules/_hacl/libHacl_Hash_SHA2.a -lz 
-Xlinker -export-dynamic -
Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -g -fwrapv -O2 
 >&5
/usr/bin/ld: cannot find Modules/_hacl/libHacl_Hash_SHA2.a: No such file 
or directory

collect2: error: ld returned 1 exit status
configure:15777: $? = 1


looking at m4/python.m4, this comes from getting the configuration out 
of the sysconfig module.


and _sysconfigdata_* has:

 'LOCALMODLIBS': '-lm  -lm   -lz -lm -lm   -lexpat  -lexpat '
 'Modules/_hacl/libHacl_Hash_SHA2.a -lz',


So, I'm not sure, how to better get the required information for 
linking, but this interface doesn't look very reliable.


maybe better use: python3-config --embed --libs

patch attached.

diff -Nru inn2-2.7.2~20231223/debian/changelog inn2-2.7.2~20231223/debian/changelog
--- inn2-2.7.2~20231223/debian/changelog	2024-01-19 20:41:48.0 +0100
+++ inn2-2.7.2~20231223/debian/changelog	2024-01-25 16:06:27.0 +0100
@@ -1,3 +1,9 @@
+inn2 (2.7.2~20231223-1ubuntu1) noble; urgency=medium
+
+  * Fix configury with Python 3.12.
+
+ -- Matthias Klose   Thu, 25 Jan 2024 16:06:27 +0100
+
 inn2 (2.7.2~20231223-1build2) noble; urgency=medium
 
   * No-change rebuild with Python 3.12 as default
diff -Nru inn2-2.7.2~20231223/debian/patches/python3.12.diff inn2-2.7.2~20231223/debian/patches/python3.12.diff
--- inn2-2.7.2~20231223/debian/patches/python3.12.diff	1970-01-01 01:00:00.0 +0100
+++ inn2-2.7.2~20231223/debian/patches/python3.12.diff	2024-01-25 16:06:27.0 +0100
@@ -0,0 +1,23 @@
+--- a/m4/python.m4
 b/m4/python.m4
+@@ -130,10 +130,7 @@ AC_DEFUN([INN_LIB_PYTHON],
+ print(" -L".join(sysconfig.get_config_vars("LIBDIR")))'`
+  py_ldlibrary=`$PYTHON -c 'import sysconfig; \
+ print(sysconfig.get_config_vars("LDLIBRARY")@<:@0@:>@)'`
+- py_linkage=`$PYTHON -c 'import sysconfig; \
+-print(" ".join(sysconfig.get_config_vars(  \
+-"LIBS", "LIBC", "LIBM", "LOCALMODLIBS", "BASEMODLIBS", \
+-"LINKFORSHARED", "LDFLAGS")))'`],
++ py_linkage=`${PYTHON}-config --embed --libs`],
+ [py_include=`$PYTHON -c 'import distutils.sysconfig; \
+ print(distutils.sysconfig.get_python_inc())'`
+  py_libdir=`$PYTHON -c 'import distutils.sysconfig; \
+@@ -142,7 +139,7 @@ AC_DEFUN([INN_LIB_PYTHON],
+ print(distutils.sysconfig.get_config_vars("LDLIBRARY")@<:@0@:>@)'`
+  py_linkage=`$PYTHON -c 'import distutils.sysconfig;   \
+ print(" ".join(distutils.sysconfig.get_config_vars(\
+-"LIBS", "LIBC", "LIBM", "LOCALMODLIBS", "BASEMODLIBS", \
++"LIBS", "LIBC", "LIBM", "MODLIBS", "BASEMODLIBS", \
+ "LINKFORSHARED", "LDFLAGS")))'`])
+  PYTHON_CPPFLAGS="-I$py_include"
+  py_libpython=`AS_ECHO(["$py_ldlibrary"]) \
diff -Nru inn2-2.7.2~20231223/debian/patches/series inn2-2.7.2~20231223/debian/patches/series
--- inn2-2.7.2~20231223/debian/patches/series	2023-09-06 21:47:32.0 +0200
+++ 

Bug#1061499: libgssglue: disable gsasl-dovecot-gssapi-heimdal autopkgtests on armhf, re-enable them on i386

[Emanuele Rocca]

Source: libgssglue
Version: 0.8-2
Severity: serious
User: debian-...@lists.debian.org
Usertags: 32bit-stackclash
Tags: patch

Dear Maintainer,

Two of the libgssglue valgrind autopkgtests, namely
gsasl-dovecot-gssapi-heimdal and gsasl-dovecot-gssapi-heimdal-root,
currently fail on armhf due to valgrind bug
https://bugs.debian.org/1061496:

 libgssglue   PASS
 bad-configs  PASS
 bad-configs-root PASS
 gsasl-dovecot-gssapi PASS
 gsasl-dovecot-gssapi-heimdal FAIL non-zero exit status 1
 gsasl-dovecot-gssapi-heimdal-root FAIL non-zero exit status 1

Please consider disabling them.

On the other hand, all tests can be re-enabled on i386 now that #1057693
has been taken care of.

Patch attached.

Thanks,
  Emanuele
diff -Nru libgssglue-0.8/debian/changelog libgssglue-0.8/debian/changelog
--- libgssglue-0.8/debian/changelog	2023-12-07 09:17:26.0 +0100
+++ libgssglue-0.8/debian/changelog	2024-01-25 12:29:55.0 +0100
@@ -1,3 +1,12 @@
+libgssglue (0.8-2.1) UNRELEASED; urgency=medium
+
+  * Disable autopkgtests gsasl-dovecot-gssapi-heimdal and
+gsasl-dovecot-gssapi-heimdal-root on armhf due to valgrind
+bug #1061496.
+  * Re-enable valgrind on i386 now that #1057693 is fixed.
+
+ -- Emanuele Rocca   Thu, 25 Jan 2024 12:29:55 +0100
+
 libgssglue (0.8-2) unstable; urgency=medium
 
   * Disable valgrind in i386 due to #1057693.
diff -Nru libgssglue-0.8/debian/tests/control libgssglue-0.8/debian/tests/control
--- libgssglue-0.8/debian/tests/control	2023-12-07 08:40:56.0 +0100
+++ libgssglue-0.8/debian/tests/control	2024-01-25 12:29:55.0 +0100
@@ -10,13 +10,13 @@
 Restrictions: allow-stderr, needs-root
 
 Tests: gsasl-dovecot-gssapi
-Depends: gsasl, dovecot-imapd, dovecot-gssapi, krb5-kdc, krb5-admin-server, valgrind-if-available [!i386]
+Depends: gsasl, dovecot-imapd, dovecot-gssapi, krb5-kdc, krb5-admin-server, valgrind-if-available
 Restrictions: allow-stderr
 
 Tests: gsasl-dovecot-gssapi-heimdal
-Depends: gsasl, dovecot-imapd, dovecot-gssapi, krb5-kdc, krb5-admin-server, valgrind-if-available [!i386], libgssapi3-heimdal
+Depends: gsasl, dovecot-imapd, dovecot-gssapi, krb5-kdc, krb5-admin-server, valgrind-if-available [!armhf], libgssapi3-heimdal
 Restrictions: allow-stderr
 
 Tests: gsasl-dovecot-gssapi-heimdal-root
-Depends: gsasl, dovecot-imapd, dovecot-gssapi, krb5-kdc, krb5-admin-server, valgrind-if-available [!i386], libgssapi3-heimdal
+Depends: gsasl, dovecot-imapd, dovecot-gssapi, krb5-kdc, krb5-admin-server, valgrind-if-available [!armhf], libgssapi3-heimdal
 Restrictions: allow-stderr needs-root

Processed: Re: Processed: severity of 926900 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 926900 normal
Bug #926900 [reportbug] sslv3 alert illegal parameter
Bug #988415 [reportbug] sslv3 alert illegal parameter
Bug #988416 [reportbug] sslv3 alert illegal parameter
Severity set to 'normal' from 'serious'
Severity set to 'normal' from 'serious'
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
926900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926900
988415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988415
988416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061438: marked as done (tpm2-tss: can't upgrade the tpm2-tss packages to 4.0.1-6; missing Conflicts?)

[Debian Bug Tracking System]

Your message dated Thu, 25 Jan 2024 14:57:23 +
with message-id 
and subject line Bug#1061438: fixed in tpm2-tss 4.0.1-7
has caused the Debian Bug report #1061438,
regarding tpm2-tss: can't upgrade the tpm2-tss packages to 4.0.1-6; missing 
Conflicts?
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 ow...@bugs.debian.org
immediately.)


-- 
1061438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tpm2-tss
Version: 4.0.1-6
Severity: serious

It is not possible to upgrade the tpm2-tss packages to 4.0.1-6 with
"apt upgrade" or with aptitude (command line or its TUI, without a
*manual* dependency resolution):

root@disset:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libtss2-esys-3.0.2-0 libtss2-sys1 libtss2-tcti-cmd0 libtss2-tcti-device0
  libtss2-tcti-mssim0 libtss2-tcti-swtpm0
[...]

This is apparently due to the rename of libtss2-mu0 to
libtss2-mu-4.0.1-0. This latter package has a Breaks+Replaces,
but is that sufficient? i.e. isn't Conflicts needed?

https://wiki.debian.org/RenamingPackages says "Conflicts should only
be used if two packages can never be unpacked at the same time",
which is the case for libtss2-mu0 and libtss2-mu-4.0.1-0.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
(500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.13-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: tpm2-tss
Source-Version: 4.0.1-7
Done: Ying-Chun Liu (PaulLiu) 

We believe that the bug you reported is fixed in the latest version of
tpm2-tss, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated tpm2-tss 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 25 Jan 2024 21:48:43 +0800
Source: tpm2-tss
Architecture: source
Version: 4.0.1-7
Distribution: unstable
Urgency: low
Maintainer: Mathieu Trudel-Lapierre 
Changed-By: Ying-Chun Liu (PaulLiu) 
Closes: 1061438
Changes:
 tpm2-tss (4.0.1-7) unstable; urgency=low
 .
   [ Jeremy Bícha ]
   * Add debian/salsa-ci.yml
 .
   [ Ying-Chun Liu (PaulLiu) ]
   * debian/control: libtss2-mu-4.0.1-0 conflicts libtss2-mu0 (Closes: #1061438)
Checksums-Sha1:
 37c9e865c1e088bbd3b17210b24b031c8cfb7d10 3219 tpm2-tss_4.0.1-7.dsc
 89b0e9fba336f91fa3b25f16342686d87462f603 18984 tpm2-tss_4.0.1-7.debian.tar.xz
 f4455e7fe1db92a0829ab080a13d65a328ab67a5 8348 tpm2-tss_4.0.1-7_source.buildinfo
Checksums-Sha256:
 9c9a94f148bbfbd328454084b4b61443ed36eaf65a515c34274d5b6e9f377d55 3219 
tpm2-tss_4.0.1-7.dsc
 06cd82b264bb83a5245537d04c2c0cf6fac6e4f77dc18e9bd51e5eebf7ad56de 18984 
tpm2-tss_4.0.1-7.debian.tar.xz
 f39cfc1d556ea29b1caeca3c8c79f4a55bea65fce44a4b04f653cecfc115f398 8348 
tpm2-tss_4.0.1-7_source.buildinfo
Files:
 d6d041bce1e549ca87353f69b84468dc 3219 libs optional tpm2-tss_4.0.1-7.dsc
 ab537f8e521c466fc1f21ba97f185f5a 18984 libs optional 
tpm2-tss_4.0.1-7.debian.tar.xz
 7506005ad3103f0bb17c7c4640063d29 8348 libs optional 
tpm2-tss_4.0.1-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmWybc4THHBhdWxsaXVA
ZGViaWFuLm9yZwAKCRBEFz+hPQWIiKTPEAChh1La28JtejPtxoWTWzxvP7V+WqAW
jtq3LFqMKT4ys6SsyG4yDTCzUd6M1qXcjSrDcmVyTehOJdSDKCa9RWtf32vXP1g5
5qCpZ5+q/zoKrQ/I3nNvei0vVaZUoh/V3PCGV1fYIVrerbZ9Mu12vNTH1DPkKPvT

Processed: Re: scribus ftbfs with Python 3.12 as default

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1061305 [src:scribus] scribus ftbfs with Python 3.12 as default
Added tag(s) patch.

-- 
1061305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061305: scribus ftbfs with Python 3.12 as default

[Matthias Klose]

Control: tags -1 + patch

this is fixed in the new upstream 1.6.1

Processed: Not reproducible

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1061032 [src:golang-github-go-kit-kit] golang-github-go-kit-kit: FTBFS: 
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
github.com/go-kit/kit/auth/basic github.com/go-kit/kit/auth/casbin [...] 
returned exit code 1
Severity set to 'normal' from 'serious'
> tags -1 unreproducible
Bug #1061032 [src:golang-github-go-kit-kit] golang-github-go-kit-kit: FTBFS: 
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
github.com/go-kit/kit/auth/basic github.com/go-kit/kit/auth/casbin [...] 
returned exit code 1
Added tag(s) unreproducible.

-- 
1061032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061032: Not reproducible

[Reinhard Tartler]

Control: severity -1 normal
Control: tags -1 unreproducible

Hey Lucas,

I've been unable to reproduce, please see my build log attached to this email.
Maybe some test is flaky?

I'm lowering severity as I am unconvinced that removing this package from
testing, along with all of its reverse dependencies is doing anyone a
service.

<#part type="text/plain" 
filename="/srv/scratch/packages/go-team/golang-github-go-kit-kit.autopkgtest.log/log"
 disposition=inline description="successful build log">
<#/part>

Processed: adding fixes, package still doesn't build

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1061316 [src:gringo] gringo ftbfs with Python 3.12 as the default
Added tag(s) patch.

-- 
1061316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: adding fixes, package still doesn't build

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1054688 [src:gringo] gringo: FTBFS: main.cc:2:10: fatal error: 
catch2/catch.hpp: No such file or directory
Added tag(s) patch.

-- 
1054688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1054688: adding fixes, package still doesn't build

[Matthias Klose]

Control: tags -1 + patch

adding patches, however the package still ftbfs with:

[...]
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/Scrt1.o: in 
function `_start':

(.text+0x1b): undefined reference to `main'
/usr/bin/ld: CMakeFiles/test_reify.dir/program.cc.o: in function 
`Reify::Test::CATCH2_INTERNAL_TEST_0()':
/usr/src/gringo-5.4.1-3.1ubuntu1/libreify/tests/program.cc:18:(.text+0x409): 
undefined reference to `Catch::StringRef::StringRef(char const*)'
/usr/bin/ld: 
/usr/src/gringo-5.4.1-3.1ubuntu1/libreify/tests/program.cc:18:(.text+0x448): 
undefined reference to `Catch::Section::Section(Catch::SourceLineInfo 
const&, Catch::StringRef, char const*)'
/usr/bin/ld: 
/usr/src/gringo-5.4.1-3.1ubuntu1/libreify/tests/program.cc:18:(.text+0x450): 
undefined reference to `Catch::Section::operator bool() const'

[...]
collect2: error: ld returned 1 exit status
make[4]: *** [libreify/tests/CMakeFiles/test_reify.dir/build.make:118: 
bin/test_reify] Error 1


plus made a try at the new upstream, although the tests still hang:

See
https://launchpad.net/~doko/+archive/ubuntu/ppa/+sourcepub/15720531/+listing-archive-extradiff -Nru gringo-5.4.1/debian/changelog gringo-5.4.1/debian/changelog
--- gringo-5.4.1/debian/changelog	2024-01-19 20:38:31.0 +0100
+++ gringo-5.4.1/debian/changelog	2024-01-25 12:22:34.0 +0100
@@ -1,3 +1,12 @@
+gringo (5.4.1-3.1ubuntu1) noble; urgency=medium
+
+  * Fix build with Python 3.12. Closes: #1061316.
+  * Fix build with new catch2 version. Closes: #1054688.
+  * Explicitly mention the build system.
+  * Add override_dh_auto_install target.
+
+ -- Matthias Klose   Thu, 25 Jan 2024 12:22:34 +0100
+
 gringo (5.4.1-3.1build1) noble; urgency=medium
 
   * No-change rebuild with Python 3.12 as default
diff -Nru gringo-5.4.1/debian/patches/python3.12.diff gringo-5.4.1/debian/patches/python3.12.diff
--- gringo-5.4.1/debian/patches/python3.12.diff	1970-01-01 01:00:00.0 +0100
+++ gringo-5.4.1/debian/patches/python3.12.diff	2024-01-25 12:22:01.0 +0100
@@ -0,0 +1,11 @@
+--- a/cmake/python-site.py
 b/cmake/python-site.py
+@@ -1,4 +1,7 @@
+-from distutils.sysconfig import get_python_lib, get_config_vars
++try:
++from setuptools.sysconfig import get_python_lib, get_config_vars
++except ImportError:
++from distutils.sysconfig import get_python_lib, get_config_vars
+ import sys
+ if sys.argv[1] == "prefix":
+ print(get_python_lib(True, False, sys.argv[2] if len(sys.argv) > 2 else None))
diff -Nru gringo-5.4.1/debian/patches/series gringo-5.4.1/debian/patches/series
--- gringo-5.4.1/debian/patches/series	2022-11-19 11:33:48.0 +0100
+++ gringo-5.4.1/debian/patches/series	2024-01-25 12:21:04.0 +0100
@@ -4,3 +4,4 @@
 bump-version-5.4.1.patch
 use-system-catch-for-glibc-2.34-compat.patch
 testsuite-python-open-rU.patch
+python3.12.diff
diff -Nru gringo-5.4.1/debian/patches/use-system-catch-for-glibc-2.34-compat.patch gringo-5.4.1/debian/patches/use-system-catch-for-glibc-2.34-compat.patch
--- gringo-5.4.1/debian/patches/use-system-catch-for-glibc-2.34-compat.patch	2022-11-19 11:33:48.0 +0100
+++ gringo-5.4.1/debian/patches/use-system-catch-for-glibc-2.34-compat.patch	2024-01-25 12:22:34.0 +0100
@@ -300,7 +300,7 @@
 
  #define CATCH_CONFIG_MAIN
 -#include "catch.hpp"
-+#include 
++#include 
 --- gringo-5.4.1.orig/libclingo/tests/tests.hh
 +++ gringo-5.4.1/libclingo/tests/tests.hh
 @@ -23,7 +23,7 @@
@@ -308,7 +308,7 @@
  
  #include "clingo.hh"
 -#include "catch.hpp"
-+#include 
++#include 
  
  namespace Clingo { namespace Test {
  
@@ -319,7 +319,7 @@
  // }}}
  #define CATCH_CONFIG_MAIN
 -#include "catch.hpp"
-+#include 
++#include 
 --- gringo-5.4.1.orig/libgringo/tests/tests.hh
 +++ gringo-5.4.1/libgringo/tests/tests.hh
 @@ -25,7 +25,7 @@
@@ -327,7 +327,7 @@
  #define _GRINGO_TEST_TESTS_HH
  
 -#include "catch.hpp"
-+#include 
++#include 
  #include "gringo/utility.hh"
  #include "gringo/logger.hh"
  #include "gringo/base.hh"
@@ -336,13 +336,13 @@
 @@ -1,2 +1,2 @@
  #define CATCH_CONFIG_MAIN
 -#include "catch.hpp"
-+#include 
++#include 
 
 --- gringo-5.4.1.orig/libreify/tests/program.cc
 +++ gringo-5.4.1/libreify/tests/program.cc
 @@ -1,4 +1,4 @@
 -#include "catch.hpp"
-+#include 
++#include 
  #include 
  #include 
  
diff -Nru gringo-5.4.1/debian/rules gringo-5.4.1/debian/rules
--- gringo-5.4.1/debian/rules	2022-11-19 11:33:48.0 +0100
+++ gringo-5.4.1/debian/rules	2024-01-25 12:22:34.0 +0100
@@ -28,7 +28,7 @@
 CXXFLAGS += $(CPPFLAGS)
 
 %:
-	dh $@ --with pkgkde_symbolshelper
+	dh $@ --buildsystem=cmake --with pkgkde_symbolshelper
 
 # configure with cmake
 override_dh_auto_configure:
@@ -38,6 +38,9 @@
 override_dh_auto_build:
 	dh_auto_build --builddirectory=$(TOPBUILDDIR)
 
+override_dh_auto_install:
+	dh_auto_install --builddirectory=$(TOPBUILDDIR)
+
 override_dh_auto_clean:
 	dh_auto_clean --builddirectory=$(TOPBUILDDIR)
 

Bug#1061481: bpftrace ftbfs on armhf

[Matthias Klose]

Package: src:bpftrace
Version: 0.20.0-1
Severity: serious
Tags: sid trixie ftbfs

bpftrace ftbfs on armhf:

/<>/src/attached_probe.cpp:836:35: warning: cast from 
‘const unsigned char*’ to ‘const bpf_insn*’ increases required alignment 
of target type [-Wcast-align]
  836 |   reinterpret_castbpf_insn *>(
  | 
^~

  837 |   insns.data()),
  |   ~
/<>/src/attached_probe.cpp: In member function ‘void 
bpftrace::AttachedProbe::attach_multi_uprobe(int)’:
/<>/src/attached_probe.cpp:1113:43: error: cannot convert 
‘long long unsigned int*’ to ‘const long unsigned int*’ in assignment

 1113 |   opts.uprobe_multi.offsets = offsets.data();
  |   ^~
  |   |
  |   long long unsigned int*



/<>/src/bpftrace.cpp: At global scope:
/<>/src/bpftrace.cpp:2034:13: error: no declaration matches 
‘std::string bpftrace::BPFtrace::resolve_uid(uint64_t) const’

 2034 | std::string BPFtrace::resolve_uid(uint64_t addr) const
  | ^~~~
In file included from /<>/src/bpftrace.cpp:34:
/<>/src/bpftrace.h:138:15: note: candidate is: ‘std::string 
bpftrace::BPFtrace::resolve_uid(uintptr_t) const’

  138 |   std::string resolve_uid(uintptr_t addr) const;
  |   ^~~
/<>/src/bpftrace.h:95:7: note: ‘class bpftrace::BPFtrace’ 
defined here

   95 | class BPFtrace
  |   ^~~~
/<>/src/bpftrace.cpp:2119:13: error: no declaration matches 
‘std::string bpftrace::BPFtrace::resolve_ksym(uint64_t, bool)’

 2119 | std::string BPFtrace::resolve_ksym(uint64_t addr, bool show_offset)
  | ^~~~
/<>/src/bpftrace.h:131:15: note: candidate is: ‘std::string 
bpftrace::BPFtrace::resolve_ksym(uintptr_t, bool)’

  131 |   std::string resolve_ksym(uintptr_t addr, bool show_offset=false);
  |   ^~~~
/<>/src/bpftrace.h:95:7: note: ‘class bpftrace::BPFtrace’ 
defined here

   95 | class BPFtrace
  |   ^~~~
/<>/src/bpftrace.cpp:2310:13: error: no declaration matches 
‘std::string bpftrace::BPFtrace::resolve_usym(uint64_t, int, int, bool, 
bool)’

 2310 | std::string BPFtrace::resolve_usym(uint64_t addr,
  | ^~~~
/<>/src/bpftrace.h:132:15: note: candidate is: ‘std::string 
bpftrace::BPFtrace::resolve_usym(uintptr_t, int, int, bool, bool)’

  132 |   std::string resolve_usym(uintptr_t addr,
  |   ^~~~
/<>/src/bpftrace.h:95:7: note: ‘class bpftrace::BPFtrace’ 
defined here

   95 | class BPFtrace
  |   ^~~~

Processed: Problem is caused by upgrade of python3-bibtexparser to 2.0.0b5 - issue filed upstream

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1060965 [src:qiime] q2cli: AttributeError: module 'bibtexparser' has no 
attribute 'bparser'
Bug #1060987 [src:qiime] q2cli: AttributeError: module 'bibtexparser' has no 
attribute 'bparser'
Added tag(s) upstream.
Added tag(s) upstream.
> forwarded -1 https://github.com/sciunto-org/python-bibtexparser/issues/451
Bug #1060965 [src:qiime] q2cli: AttributeError: module 'bibtexparser' has no 
attribute 'bparser'
Bug #1060987 [src:qiime] q2cli: AttributeError: module 'bibtexparser' has no 
attribute 'bparser'
Set Bug forwarded-to-address to 
'https://github.com/sciunto-org/python-bibtexparser/issues/451'.
Set Bug forwarded-to-address to 
'https://github.com/sciunto-org/python-bibtexparser/issues/451'.

-- 
1060965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060965
1060987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forwarded issue

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1061319 https://github.com/kpeeters/cadabra2/issues/291
Bug #1061319 [src:cadabra2] cadabra2 ftbfs with Python 3.12 as default
Set Bug forwarded-to-address to 
'https://github.com/kpeeters/cadabra2/issues/291'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1061319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061319
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1060965: Problem is caused by upgrade of python3-bibtexparser to 2.0.0b5 - issue filed upstream

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 
https://github.com/sciunto-org/python-bibtexparser/issues/451

It turns out that bibtexparser has changed its API.  I asked for some
documentation about this change to find a proper patch.

-- 
http://fam-tille.de

Processed: Re: Bug#1061015: pygame-sdl2: FTBFS: Cannot assign type 'Sint64 (SDL_RWops *) except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:renpy
Bug #1061015 [src:pygame-sdl2] pygame-sdl2: FTBFS: Cannot assign type 'Sint64 
(SDL_RWops *) except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'
Added indication that 1061015 affects src:renpy

-- 
1061015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061015: pygame-sdl2: FTBFS: Cannot assign type 'Sint64 (SDL_RWops *) except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'

[Simon McVittie]

Control: affects -1 + src:renpy

On Tue, 16 Jan 2024 at 20:43:34 +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> > src/pygame_sdl2/rwobject.pyx:336:22: Cannot assign type 'Sint64 (SDL_RWops 
> > *) except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'. Exception 
> > values are incompatible. Suggest adding 'noexcept' to type 'Sint64 
> > (SDL_RWops *) except? -1 nogil'.

This looks like probably a regression with cython 3.x, which has this
in its release notes:

Cython-implemented C functions now propagate exceptions by default,
rather than swallowing them in non-object returning function if the
user forgot to add an except declaration to the signature. This was
a long-standing source of bugs, but can require adding the noexcept
declaration to existing functions if exception propagation is really
undesired. (Github issue #4280)

...

To opt out of the new, safer exception handling behaviour, legacy
code can set the new directive legacy_implicit_noexcept=True for
a transition period to keep the previous, unsafe behaviour. This
directive will eventually be removed in a later release.

References: ,
.

The changelog for pygame-sdl2 8.1.3-1 says the new upstream release is
compatible with cython3, but that doesn't seem to be the case? But I
also don't understand where these new upstream releases are coming from,
because https://github.com/renpy/pygame_sdl2 only has tags for 8.1.0,
and there don't seem to be any recent commits that are relevant to
cython3 compatibility.

smcv

Processed: retitle 1061015 to pygame-sdl2: FTBFS: Cannot assign type 'Sint64 (SDL_RWops *) except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1061015 pygame-sdl2: FTBFS: Cannot assign type 'Sint64 (SDL_RWops *) 
> except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'
Bug #1061015 [src:pygame-sdl2] pygame-sdl2: FTBFS: make: *** [debian/rules:6: 
binary] Error 25
Changed Bug title to 'pygame-sdl2: FTBFS: Cannot assign type 'Sint64 (SDL_RWops 
*) except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'' from 'pygame-sdl2: 
FTBFS: make: *** [debian/rules:6: binary] Error 25'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1061015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: raising severity, 3.12 extensions are already built

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1061392 [src:swig] swig 4.2.0 needed for Python 3.12 compatibility
Severity set to 'serious' from 'important'

-- 
1061392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1061102

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1061102 + patch
Bug #1061102 [librust-tikv-jemalloc-sys-dev] librust-tikv-jemalloc-sys-dev: 
fails to compile without xsltproc
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1061102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061027: marked as done (moment-timezone.js: FTBFS: make[1]: *** [debian/rules:28: execute_before_dh_auto_configure] Error 1)

[Debian Bug Tracking System]

Your message dated Thu, 25 Jan 2024 09:06:26 +
with message-id 
and subject line Bug#1061027: fixed in moment-timezone.js 0.5.44+dfsg-1+2023d
has caused the Debian Bug report #1061027,
regarding moment-timezone.js: FTBFS: make[1]: *** [debian/rules:28: 
execute_before_dh_auto_configure] Error 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 ow...@bugs.debian.org
immediately.)


-- 
1061027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: moment-timezone.js
Version: 0.5.43+dfsg-1+2023c
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>debian/rules execute_before_dh_auto_configure
> make[1]: Entering directory '/<>'
> # Fail the build if the tzdata package does not match TZVER.
> grep -q '^# version 2023c$' /usr/share/zoneinfo/tzdata.zi
> make[1]: *** [debian/rules:28: execute_before_dh_auto_configure] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/moment-timezone.js_0.5.43+dfsg-1+2023c_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: moment-timezone.js
Source-Version: 0.5.44+dfsg-1+2023d
Done: Martina Ferrari 

We believe that the bug you reported is fixed in the latest version of
moment-timezone.js, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martina Ferrari  (supplier of updated moment-timezone.js 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 25 Jan 2024 07:46:05 +
Source: moment-timezone.js
Architecture: source
Version: 0.5.44+dfsg-1+2023d
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Martina Ferrari 
Closes: 1061027
Changes:
 moment-timezone.js (0.5.44+dfsg-1+2023d) unstable; urgency=medium
 .
   * New upstream version 0.5.44, supporting tzdata 2023d. Closes: #1061027.
   * tests/helpers/helpers.js: Add patch to only consider 4 decimal points when
 comparing UTC offsets, to avoid failing on rounding differences.
Checksums-Sha1:
 0e626f833e31aab60d7a849a4500753976d6cc17 2356 
moment-timezone.js_0.5.44+dfsg-1+2023d.dsc
 0abb1eb2f6c17c54c1fe5dc42667427a78d35f8b 1901720 
moment-timezone.js_0.5.44+dfsg.orig.tar.xz
 c2acbcea6eebf373a43ef15e753df8d4fbf96c9b 6320 
moment-timezone.js_0.5.44+dfsg-1+2023d.debian.tar.xz
 9ab55b2dd4cf528a0edb2bacbfea149ce8a4a43b 20305 
moment-timezone.js_0.5.44+dfsg-1+2023d_amd64.buildinfo
Checksums-Sha256:
 141d0c190e61d6459f93bd354cfc3b84d8464d1bab9fbd96e46ebef6f3c0de7a 2356 
moment-timezone.js_0.5.44+dfsg-1+2023d.dsc
 4f00509ae297e3c40a5c274ab754a5661846c7155d6538b4c23780e731409e79 1901720 
moment-timezone.js_0.5.44+dfsg.orig.tar.xz
 c76a0412c18a7c468e7029dd2fadef404f9ed7e07048aab40928b092431aa907 6320 
moment-timezone.js_0.5.44+dfsg-1+2023d.debian.tar.xz
 f401804438ab9c30f63c1ad2e329af0e7a3e0055c7fce665fac1472786c25bea 20305 
moment-timezone.js_0.5.44+dfsg-1+2023d_amd64.buildinfo
Files:
 923e9d3758422e74e226d2643b24a48f 2356 javascript optional 
moment-timezone.js_0.5.44+dfsg-1+2023d.dsc
 a4c8c41a513f810cd88ab5a1ff523cd3 1901720 javascript optional 
moment-timezone.js_0.5.44+dfsg.orig.tar.xz
 

Processed: reassign 1060895 to src:liblsl, found 1040544 in 3.3.3-1, severity of 1040544 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1060895 src:liblsl 1.16.2b1-1
Bug #1060895 [liblsl] liblsl: missing #include for uint32_t
Bug reassigned from package 'liblsl' to 'src:liblsl'.
No longer marked as found in versions 1.16.2b1-1.
Ignoring request to alter fixed versions of bug #1060895 to the same values 
previously set
Bug #1060895 [src:liblsl] liblsl: missing #include for uint32_t
Marked as found in versions liblsl/1.16.2b1-1.
> found 1040544 3.3.3-1
Bug #1040544 {Done: Jelmer Vernooij } [src:breezy] breezy: 
Unnecessary Build-Depends on cython3-dbg
Marked as found in versions breezy/3.3.3-1.
> severity 1040544 serious
Bug #1040544 {Done: Jelmer Vernooij } [src:breezy] breezy: 
Unnecessary Build-Depends on cython3-dbg
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1040544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040544
1060895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1060998: marked as done (cthreadpool: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Thu, 25 Jan 2024 08:34:35 +
with message-id 
and subject line Bug#1060998: fixed in cthreadpool 0.0+git20231218.4eb5a69-1
has caused the Debian Bug report #1060998,
regarding cthreadpool: FTBFS: E: Build killed with signal TERM after 150 
minutes of inactivity
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 ow...@bugs.debian.org
immediately.)


-- 
1060998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cthreadpool
Version: 0.0+git20201207.b259a6e-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> 1/10
> 2/10
> 3/10
> 4/10
> 5/10
> 6/10
> 7/10
> 8/10
> 9/10
> 10/10
> 
> Testing multiple threads creation and destruction in pool(threads=3 times=20)
> 1/20
> 2/20
> 3/20
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/cthreadpool_0.0+git20201207.b259a6e-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: cthreadpool
Source-Version: 0.0+git20231218.4eb5a69-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
cthreadpool, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1060...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated cthreadpool package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 25 Jan 2024 08:41:52 +0100
Source: cthreadpool
Architecture: source
Version: 0.0+git20231218.4eb5a69-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Andreas Tille 
Closes: 1060998
Changes:
 cthreadpool (0.0+git20231218.4eb5a69-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
 Closes: #1060998
   * Standards-Version: 4.6.2 (routine-update)
   * Set upstream metadata fields: Repository-Browse.
   * DEP3
Checksums-Sha1:
 f9b3d04a69afe09f175cd667b3542f0c24dc1780 2152 
cthreadpool_0.0+git20231218.4eb5a69-1.dsc
 372feba68b457934a9d1d818e5fb8523933db8a5 13076 
cthreadpool_0.0+git20231218.4eb5a69.orig.tar.xz
 8e69d5a8d75c9e8ede3eb7dddcb757bd1cfb2c5e 3756 
cthreadpool_0.0+git20231218.4eb5a69-1.debian.tar.xz
 98c2a1d3613cce615d0a59f3acdbd525b09eb89f 6877 
cthreadpool_0.0+git20231218.4eb5a69-1_amd64.buildinfo
Checksums-Sha256:
 a08292f617d253f5d5d50d679ceacb92580097123ba55d4def5fde2bdbb06bc2 2152 
cthreadpool_0.0+git20231218.4eb5a69-1.dsc
 7efd15ee6bfb3371c92e899d7282d4ed1abbc2e58bfbc699b5f4a9eaa984b33e 13076 
cthreadpool_0.0+git20231218.4eb5a69.orig.tar.xz
 f9b16049796a66db4d6b2a1641a27faf6e88348f9a4bfa5c701fd07ff4e33d3c 3756 
cthreadpool_0.0+git20231218.4eb5a69-1.debian.tar.xz
 33a5c2e472242d85aa0d83378e831bf7eda8fb31ebf0ebe2f50b5aaba41b78dc 6877 
cthreadpool_0.0+git20231218.4eb5a69-1_amd64.buildinfo
Files:
 a7df22ce343bf1806d93338a5d60acc0 2152 libs optional 
cthreadpool_0.0+git20231218.4eb5a69-1.dsc
 fec6c0b814ceba3f81c18e02c8cb1d58 13076 libs optional 
cthreadpool_0.0+git20231218.4eb5a69.orig.tar.xz
 94e04e3c81c50785361e66c7203d2370 3756 libs optional 
cthreadpool_0.0+git20231218.4eb5a69-1.debian.tar.xz
 80b51a7c3ec7291b51eb0c8b8acf50b0 6877 libs optional 
cthreadpool_0.0+git20231218.4eb5a69-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Processed: Bug#1061027 marked as pending in moment-timezone.js

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1061027 [src:moment-timezone.js] moment-timezone.js: FTBFS: make[1]: *** 
[debian/rules:28: execute_before_dh_auto_configure] Error 1
Added tag(s) pending.

-- 
1061027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1061027: marked as pending in moment-timezone.js

[Martina Ferrari]

Control: tag -1 pending

Hello,

Bug #1061027 in moment-timezone.js reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/moment-timezone.js/-/commit/b1b2b0107a538bd9e6c5d14b6a4c59d2c955e841


Add missing Closes: #1061027.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1061027