Bug#1022788: marked as done (cockpit: FTBFS on armel/mipsel/mips64el: dh_auto_test failures)

[Debian Bug Tracking System]

Your message dated Sat, 29 Oct 2022 05:51:01 +
with message-id 
and subject line Bug#1022788: fixed in cockpit 278-1
has caused the Debian Bug report #1022788,
regarding cockpit: FTBFS on armel/mipsel/mips64el: dh_auto_test failures
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.)


-- 
1022788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cockpit
Version: 276.1-1
Severity: serious

cockpit seems to fail its test suite on the aforementioned architectures

on armel:
~
(cockpit-bridge:13294): cockpit-bridge-WARNING **: 11:53:58.528: couldn't 
create runtime dir: /run/user/2952: Permission denied
cockpit-bridge-Message: 11:53:58.577: incompatible: package requires a later 
version of cockpit: 999.5 > 277
cockpit-bridge-Message: 11:53:58.577: requires: package has an unknown 
requirement: unknown
cockpit-bridge-Message: 11:53:58.582: couldn't get polkit authority: Error 
initializing authority: Could not connect: No such file or directory
# cockpit-protocol-DEBUG: cockpit-bridge: reading input 1
# cockpit-protocol-DEBUG: cockpit-bridge: received a 358 byte payload
# cockpit-ws-DEBUG: received init message
# cockpit-protocol-DEBUG: cockpit-bridge: queued 67 byte payload
# cockpit-protocol-DEBUG: cockpit-bridge: want more data
# cockpit-protocol-DEBUG: cockpit-bridge: queued 302 byte payload
# cockpit-protocol-DEBUG: cockpit-bridge: queued 35 byte payload
# cockpit-protocol-DEBUG: cockpit-bridge: queued 34 byte payload
# cockpit-protocol-DEBUG: cockpit-bridge: end of input
# cockpit-protocol-DEBUG: cockpit-bridge: pipe closing when output queue empty
# cockpit-protocol-DEBUG: cockpit-bridge: couldn't write: Broken pipe
# cockpit-protocol-DEBUG: cockpit-bridge: closing pipe: terminated
# cockpit-protocol-DEBUG: cockpit-bridge: killing child: 13294
Bail out! GLib-FATAL-WARNING: GChildWatchSource: Exit status of a child process 
was requested but ECHILD was received by waitpid(). See the documentation of 
g_child_watch_source_new() for possible causes.

(test-channelresponse:13227): GLib-WARNING **: 11:53:58.590: GChildWatchSource: 
Exit status of a child process was requested but ECHILD was received by 
waitpid(). See the documentation of g_child_watch_source_new() for possible 
causes.
**
cockpit-ws:ERROR:src/ws/test-channelresponse.c:526:test_resource_failure: Got 
unexpected message: GChildWatchSource: Exit status of a child process was 
requested but ECHILD was received by waitpid(). See the documentation of 
g_child_watch_source_new() for possible causes. instead of cockpit-ws-Message: 
*: external channel failed: *
Bail out! 
cockpit-ws:ERROR:src/ws/test-channelresponse.c:526:test_resource_failure: Got 
unexpected message: GChildWatchSource: Exit status of a child process was 
requested but ECHILD was received by waitpid(). See the documentation of 
g_child_watch_source_new() for possible causes. instead of cockpit-ws-Message: 
*: external channel failed: *
FAIL test-channelresponse (exit status: 134)


on mips* the test suite is killed after 150min of inactivity

This currently prevents testing migration, thus filing with RC severity.
--- End Message ---
--- Begin Message ---
Source: cockpit
Source-Version: 278-1
Done: Martin Pitt 

We believe that the bug you reported is fixed in the latest version of
cockpit, 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 1022...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Pitt  (supplier of updated cockpit 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: Sat, 29 Oct 2022 07:20:06 +0200
Source: cockpit
Architecture: source
Version: 278-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Martin Pitt 
Closes: 1022788
Changes:
 cockpit (278-1) unstable; urgency=medium
 .
   * New upstream release:
 - Metrics: Display individual disk read/write usage
 - test-channelresponse: use pidfd to watch for child exit
   (Closes: #1022788)
Checksums-Sha1:
 461e4a9dddf38f3a905d1dc642d04894094d1444 3019 cockpit_278-1.dsc
 ab8949dcda5c1dc80f

Processed: Re: Bug#1022788: cockpit: FTBFS on armel/mipsel/mips64el: dh_auto_test failures

[Debian Bug Tracking System]

Processing control commands:

> tag -1 fixed-upstream pending
Bug #1022788 [src:cockpit] cockpit: FTBFS on armel/mipsel/mips64el: 
dh_auto_test failures
Added tag(s) pending and fixed-upstream.

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

Bug#1022788: cockpit: FTBFS on armel/mipsel/mips64el: dh_auto_test failures

[Martin Pitt]

Control: tag -1 fixed-upstream pending

Hello again,

Martin Pitt [2022-10-26  6:04 +0200]:
> Argh, this keeps haunting us. We already tried to fix that in [1] and [2], but
> no way. Why must glib be so unpredictable? 😢

> [2] https://github.com/cockpit-project/cockpit/pull/17755

Nevermind.. [2] is part of release 278, and I just didn't package that yet 🙈
will do now!

Martin

Bug#1021810: Should firefox-esr be dropped on 32bit architectures in bookworm?

[Adrian Bunk]

On Thu, Oct 20, 2022 at 09:25:34AM +0200, Axel Beckert wrote:
>...
> P.S.: Due to making this bug report "release critical", automatic
> updates on stable with apt-listbugs stopped applying firefox-esr
> security updates. Otherwise I wouldn't have noticed it. :-P

The bug is tagged "bookworm, sid", which makes it clear that it does not 
apply to stable.

Looking at the BTS, apt-listbugs seems to have some problems with 
version tracking that should be fixed there.

>   Regards, Axel

cu
Adrian

Bug#1023009: golang-github-coredhcp-coredhcp: binary-all FTBFS

[Adrian Bunk]

Source: golang-github-coredhcp-coredhcp
Version: 0.0.0+git.2022.04.07.a2552c5c1b-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=golang-github-coredhcp-coredhcp&arch=all&ver=0.0.0%2Bgit.2022.04.07.a2552c5c1b-3&stamp=1666975743&raw=0

...
dh_install
rm -f 
/<>/debian/golang-github-coredhcp-coredhcp-dev/usr/share/gocode/src/github.com/coredhcp/coredhcp/.gitignore
mkdir -p /<>/debian/coredhcp-client/usr/bin
mv /<>/debian/coredhcp-server/usr/bin/client 
/<>/debian/coredhcp-client/usr/bin/coredhcp-client
mv: cannot stat '/<>/debian/coredhcp-server/usr/bin/client': No 
such file or directory
make[1]: *** [debian/rules:16: override_dh_install] Error 1

Bug#1023008: fdroidserver: autopkgtest regression with openjdk-11 11.0.17+8-2

[Adrian Bunk]

Source: fdroidserver
Version: 2.1.1-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/f/fdroidserver/27601295/log.gz

...
==
ERROR: test_verify_jar_signature_succeeds (__main__.CommonTest)
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.obx56lo0/downtmp/build.IwA/src/fdroidserver/common.py", 
line 3500, in verify_jar_signature
output = subprocess.check_output([config['jarsigner'], '-strict', 
'-verify', jar],
  File "/usr/lib/python3.10/subprocess.py", line 421, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.10/subprocess.py", line 526, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 
'['/usr/lib/jvm/default-java/bin/jarsigner', '-strict', '-verify', 
'/tmp/autopkgtest-lxc.obx56lo0/downtmp/build.IwA/src/tests/signindex/testy.jar']'
 returned non-zero exit status 16.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.obx56lo0/downtmp/build.IwA/src/tests/common.TestCase", 
line 503, in test_verify_jar_signature_succeeds
fdroidserver.common.verify_jar_signature(testfile)
  File 
"/tmp/autopkgtest-lxc.obx56lo0/downtmp/build.IwA/src/fdroidserver/common.py", 
line 3507, in verify_jar_signature
raise VerificationException(error + '\n' + e.output.decode('utf-8'))
fdroidserver.exception.VerificationException: JAR signature failed to verify: 
/tmp/autopkgtest-lxc.obx56lo0/downtmp/build.IwA/src/tests/signindex/testy.jar

The jar will be treated as unsigned, because it is signed with a weak algorithm 
that is now disabled.

Re-run jarsigner with the -verbose option for more details.


--
Ran 84 tests in 24.843s

FAILED (errors=1, skipped=3)
autopkgtest [12:14:14]: test command1: ---]
autopkgtest [12:14:14]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 1

Processed: mark relationship

[Debian Bug Tracking System]

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

> block 1021803 by 1017739
Bug #1021803 [src:gnuserv] "gnuserv seems to be affected badly by #1017739"
1021803 was not blocked by any bugs.
1021803 was blocking: 1020050
Added blocking bug(s) of 1021803: 1017739
> thanks
Stopping processing here.

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

Bug#1023006: tpm2-pkcs11: binary-any FTBFS

[Adrian Bunk]

Source: tpm2-pkcs11
Version: 1.8.0-0.1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Bastian Germann 

https://buildd.debian.org/status/logs.php?pkg=tpm2-pkcs11&ver=1.8.0-0.1

...
checking for module pyasn1_modules in python... configure: error: not found



This should be moved from Build-Depends-Indep to Build-Depends.

Bug#1017845: New upload should resolve native compilation fork bomb problem

[Axel Beckert]

Control: fixed -1 1:28.2+1-3

Hi Sean,

Sean Whitton wrote:
> Thank you for testing so promptly.  There's an additional patch that
> just made it to upstream master that tries to address the trampoline
> problem.  I've just uploaded that to sid.  Could you let me know whether
> it helps, please?

Yay, finally! This one fixed it! Thanks a lot!

Marking it as fixed in 1:28.2+1-3, but leaving up to you how to
actually close the bug report as there's another one merged with this
one.

The only thing which now happened is this:

In toplevel form:
cider.el:218:1: Error: Wrong number of arguments: (3 . 4), 2

[…]
ERROR: install script from elpa-cider package failed
dpkg: error processing package emacs-gtk (--configure):
 installed emacs-gtk package post-installation script subprocess returned error 
exit status 1

But this is https://bugs.debian.org/1017834 and I was able to solve it
by temporarily uninstalling elpa-cider.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: Re: Bug#1017845: New upload should resolve native compilation fork bomb problem

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1:28.2+1-3
Bug #1017817 [emacs-common] emacs: new release seems to have funny ideas about 
byte-compiling process
Bug #1017845 [emacs-common] emacs-common: Endless fork loop at installation and 
at run time: /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-_{scroll_other_window,delete_frame}_0-.el
Ignoring request to alter fixed versions of bug #1017817 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1017845 to the same values 
previously set

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

Processed: Re: Bug#1017845: New upload should resolve native compilation fork bomb problem

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1:28.2+1-3
Bug #1017845 [emacs-common] emacs-common: Endless fork loop at installation and 
at run time: /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-_{scroll_other_window,delete_frame}_0-.el
Bug #1017817 [emacs-common] emacs: new release seems to have funny ideas about 
byte-compiling process
Marked as fixed in versions emacs/1:28.2+1-3.
Marked as fixed in versions emacs/1:28.2+1-3.

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

Bug#922579: FTBFS against opencv 4.0.1 (exp)

[Bo YU]

Source: freeture
Version: 1.3.0-1
Followup-For: Bug #922579

Dear Maintainer,

I have tried to build it with switching to opencv4, but it fails.

The searon failed is not only opencv4's api incompatibility, but also
aravis need to upgrade from 0.6 to 0.8, this also leads to the api
incompatibility.

```
In file included from /usr/include/aravis-0.8/arv.h:31,
 from CameraGigeAravis.h:51,
 from CameraGigeAravis.cpp:38:
/usr/include/aravis-0.8/arvcamera.h:45:25: note: declared here
   45 | ARV_API ArvCamera * arv_camera_new  (const char 
*name, GError **error);
  | ^~
CameraGigeAravis.cpp: In member function ‘virtual bool 
CameraGigeAravis::setSize(int, int, int, int, bool)’:
CameraGigeAravis.cpp:169:34: error: too few arguments to function ‘void 
arv_camera_set_region(ArvCamera*, gint, gint, gint, gint, GError**)’
  169 | arv_camera_set_region(camera, startx, starty, width, 
height);
  | ~^~~
/usr/include/aravis-0.8/arvcamera.h:63:25: note: declared here
   63 | ARV_API voidarv_camera_set_region   
(ArvCamera *camera, gint x, gint y, gint width, gint height, GError **error);
  | ^
CameraGigeAravis.cpp:170:35: error: too few arguments to function ‘void 
arv_camera_get_region(ArvCamera*, gint*, gint*, gint*, gint*, GError**)’
  170 | arv_camera_get_region (camera, &mStartX, &mStartY, &mWidth, 
&mHeight);
  | 
~~^~~
/usr/include/aravis-0.8/arvcamera.h:64:25: note: declared here
   64 | ARV_API voidarv_camera_get_region   
(ArvCamera *camera, gint *x, gint *y, gint *width, gint *height, GError 
**error);
  | ^
CameraGigeAravis.cpp:183:39: error: too few arguments to function ‘void 
arv_camera_get_sensor_size(ArvCamera*, gint*, gint*, GError**)’
  183 | arv_camera_get_sensor_size(camera, &sensor_width, 
&sensor_height);
  | 
~~^~~
/usr/include/aravis-0.8/arvcamera.h:62:25: note: declared here
   62 | ARV_API voidarv_camera_get_sensor_size  
(ArvCamera *camera, gint *width, gint *height, GError **error);
  | ^~
CameraGigeAravis.cpp:186:34: error: too few arguments to function ‘void 
arv_camera_set_region(ArvCamera*, gint, gint, gint, gint, GError**)’
  186 | arv_camera_set_region(camera, 0, 
0,sensor_width,sensor_height);
  | 
~^
/usr/include/aravis-0.8/arvcamera.h:63:25: note: declared here
   63 | ARV_API voidarv_camera_set_region   
(ArvCamera *camera, gint x, gint y, gint width, gint height, GError **error);
  | ^
CameraGigeAravis.cpp:187:35: error: too few arguments to function ‘void 
arv_camera_get_region(ArvCamera*, gint*, gint*, gint*, gint*, GError**)’
  187 | arv_camera_get_region (camera, NULL, NULL, &mWidth, 
&mHeight);
  | 
~~^~~
/usr/include/aravis-0.8/arvcamera.h:64:25: note: declared here
   64 | ARV_API voidarv_camera_get_region   
(ArvCamera *camera, gint *x, gint *y, gint *width, gint *height, GError 
**error);
  | ^
CameraGigeAravis.cpp: In member function ‘virtual bool 
CameraGigeAravis::grabInitialization()’:
CameraGigeAravis.cpp:220:42: error: too few arguments to function ‘guint 
arv_camera_get_payload(ArvCamera*, GError**)’
  220 | payload = arv_camera_get_payload (camera);
  |   ~~~^~~~
/usr/include/aravis-0.8/arvcamera.h:152:25: note: declared here
  152 | ARV_API guint   arv_camera_get_payload  
(ArvCamera *camera, GError **error);
  | ^~
CameraGigeAravis.cpp:223:48: error: too few arguments to function 
‘ArvPixelFormat arv_camera_get_pixel_format(ArvCamera*, GError**)’
  223 | pixFormat = arv_camera_get_pixel_format(camera);
  | ~~~^~~~
/usr/include/aravis-0.8/arvcamera.h:84:25: note: declared here
   84 | ARV_API ArvPixelFormat  arv_camera_get_pixel_format 
(ArvCamera *camera, GError **error);
  | ^~~
CameraGigeAravis.cpp:225:45: error: too few arguments to function ‘void 
arv_camera_get_exposure_time_bounds(ArvCamera*, double*, double*, GError**)’
  225 | arv_camera_get_exposure_time_bounds (camera, &exposureMin, 
&exposureMax

Bug#1021109: marked as done (bash: non existent locale crashes bash)

[Debian Bug Tracking System]

Your message dated Sat, 29 Oct 2022 03:18:02 +0300
with message-id 
and subject line Fixed in 5.2-2
has caused the Debian Bug report #1021109,
regarding bash: non existent locale crashes bash
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.)


-- 
1021109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.35-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: kos...@debian.org

Dear maintainer,

After upgrading to libc6 2.35-1 (or 2.36-1 in experimental), nonexistent locale 
setting
starts to crash the system.

This is dangerous because a remote system might not always have the same locale 
installed.
An auto update will soft-brick the system unless the sysadmin knows to set 
their LC_ALL=POSIX
before attempting to ssh.

Steps to reproduce:

>From a clean installed Debian sid, upgrade to libc6 2.35-1.
Only install C locale and en_US.UTF-8.

$ LC_ALL=ja_JP.UTF-8 bash
bash: warning: setlocale: LC_ALL: cannot change locale (ja_JP.UTF-8)
Segmentation fault (core dumped)

$ LC_ALL=ja_JP.UTF-8 gdb bash

Fatal signal: Segmentation fault
- Backtrace -
0x55ed3e1e8dcf ???
0x55ed3e2df312 ???
0x55ed3e2df488 ???
0x7f0b4a39ba9f ???
0x7f0b4b412204 _rl_init_locale
0x7f0b4b4122f1 _rl_init_eightbit
0x7f0b4b3f10f2 rl_initialize
... snip ...

Downgrade to 2.34-8 seems also don't fix the issue, probably some locale
state was invalidated when upgrading.

Thanks,
Kan-Ru


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages libc6 depends on:
ii  libgcc-s1  12.2.0-3

Versions of packages libc6 recommends:
ii  libidn2-0  2.3.3-1+b1

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.79
pn  glibc-doc  
ii  libc-l10n  2.35-1
pn  libnss-nis 
pn  libnss-nisplus 
ii  locales2.35-1

-- debconf information:
  glibc/kernel-too-old:
  glibc/restart-failed:
  glibc/disable-screensaver:
  glibc/upgrade: true
* libraries/restart-without-asking: false
* glibc/restart-services: cron
  glibc/kernel-not-supported:
--- End Message ---
--- Begin Message ---
Version: 5.2-2

bash (5.2-2) unstable; urgency=medium

  * Apply upstream patches 001 - 002.
...
- Starting bash with an invalid locale specification for
  LC_ALL/LANG/LC_CTYPE can cause the shell to crash. Closes: #1021062.

 -- Matthias Klose   Mon, 24 Oct 2022 10:34:28 +0200--- End Message ---

Bug#1022934: closed by Adrian Bunk (Fixed in 0.8.58-1)

[Adrian Bunk]

On Fri, Oct 28, 2022 at 05:54:13PM +0200, Sebastian Ramacher wrote:
> On 2022-10-28 15:45:05 +, Debian Bug Tracking System wrote:
>...
> > Version: 0.8.58-1
> 
> That version does not exist in the archive
> 
> > libpappsomspp (0.8.58-1) bullseye; urgency=low
> 
> … and that's the reason why.

It's in [1], which is what matters for version tracking.

It's not that uncommon that versions where something got fixed only 
existed in experimental/NEW/nowhere and never in unstable, when I know
the exact version where it was fixed I use that since even an unreleased
version might be the last common ancestor of versions in unstable and
experimental (e.g. if that version was stuck in NEW for some time).

> Cheers

cu
Adrian

[1] 
https://tracker.debian.org/media/packages/libp/libpappsomspp/changelog-0.8.60-1

Processed: Mark as affecting gcc-12

[Debian Bug Tracking System]

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

> tags 1022991 ftbfs
Bug #1022991 [libc6] libc6: broken y2038 support in fstatat on mips64el
Added tag(s) ftbfs.
> affects 1022991 src:gcc-12
Bug #1022991 [libc6] libc6: broken y2038 support in fstatat on mips64el
Added indication that 1022991 affects src:gcc-12
> thanks
Stopping processing here.

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

Bug#1022300: marked as done (kleopatra: FTBFS: refreshcertificatecommand.cpp:22:10: fatal error: QGpgME/RefreshOpenPGPKeysJob: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 22:56:19 +
with message-id 
and subject line Bug#1022300: fixed in kleopatra 4:22.08.2-1
has caused the Debian Bug report #1022300,
regarding kleopatra: FTBFS: refreshcertificatecommand.cpp:22:10: fatal error: 
QGpgME/RefreshOpenPGPKeysJob: No such file or directory
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.)


-- 
1022300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kleopatra
Version: 4:22.08.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
> -DGPGMEPP_ERR_SOURCE_DEFAULT=GPG_ERR_SOURCE_KLEO 
> -DGPG_ERR_SOURCE_DEFAULT=GPG_ERR_SOURCE_KLEO -DKCOREADDONS_LIB 
> -DKF_DEPRECATED_WARNINGS_SINCE=0x6 
> -DKF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x56000 -DQT_CORE_LIB -DQT_DBUS_LIB 
> -DQT_DEPRECATED_WARNINGS_SINCE=0x6 -DQT_DISABLE_DEPRECATED_BEFORE=0x50e00 
> -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII 
> -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_EMIT 
> -DQT_NO_KEYWORDS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT 
> -DQT_NO_URL_CAST_FROM_STRING -DQT_PRINTSUPPORT_LIB -DQT_STRICT_ITERATORS 
> -DQT_WIDGETS_LIB -DQT_XML_LIB -D_ASSUAN_ONLY_GPG_ERRORS -D_GNU_SOURCE 
> -D_LARGEFILE64_SOURCE -I/<>/obj-x86_64-linux-gnu/src 
> -I/<>/src 
> -I/<>/obj-x86_64-linux-gnu/src/kleopatra_bin_autogen/include 
> -I/<>/obj-x86_64-linux-gnu -I/<> 
> -I/<>/obj-x86_64-linux-gnu/src/conf -I/<>/src/conf 
> -I/<>/obj-x86_64-linux-gnu/src/libkleopatraclient/gui 
> -I/<>/src/libkleopatraclient/gui 
> -I/<>/obj-x86_64-linux-gnu/src/libkleopatraclient/core 
> -I/<>/src/libkleopatraclient/core -isystem 
> /usr/include/KF5/Libkleo -isystem /usr/include/KF5 -isystem 
> /usr/include/gpgme++ -isystem /usr/include/qgpgme -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/KF5/KIconThemes -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/KF5/KI18n 
> -isystem /usr/include/KF5/KWidgetsAddons -isystem 
> /usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem 
> /usr/include/KF5/KConfig -isystem /usr/include/KF5/KConfigGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/KF5/KConfigCore 
> -isystem /usr/include/KF5/KAuthWidgets -isystem /usr/include/KF5/KAuthCore 
> -isystem /usr/include/KF5/KAuth -isystem /usr/include/KF5/KCoreAddons 
> -isystem /usr/include/KF5/KDBusAddons -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/KF5/KMime 
> -isystem /usr/include/KF5/KXmlGui -isystem /usr/include/KF5/KWindowSystem 
> -isystem /usr/include/KF5/KItemModels -isystem /usr/include/KF5/KCrash 
> -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-operator-names 
> -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
> -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
> -Werror=return-type -Werror=init-self -Wvla -Wdate-time -Wsuggest-override 
> -Wlogical-op -pedantic -Wzero-as-null-pointer-constant -Wmissing-include-dirs 
> -Wno-missing-braces -Wno-parentheses -Wno-ignored-qualifiers -fexceptions 
> -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++20 -MD -MT 
> src/CMakeFiles/kleopatra_bin.dir/commands/refreshopenpgpcertscommand.cpp.o 
> -MF CMakeFiles/kleopatra_bin.dir/commands/refreshopenpgpcertscommand.cpp.o.d 
> -o CMakeFiles/kleopatra_bin.dir/commands/refreshopenpgpcertscommand.cpp.o -c 
> /<>/src/commands/refreshopenpgpcertscommand.cpp
> /<>/src/commands/refreshcertificatecommand.cpp:22:10: fatal 
> error: QGpgME/RefreshOpenPGPKeysJob: No such file or directory
>22 | #include 
>   |  ^~
> compilation terminated.
> make[3]: *** [src/CMakeFiles/kleopatra_bin.dir/build.make:900: 
> src/CMakeFiles/kleopatra_bin.dir/commands/refreshcertificatecommand.cpp.o] 
> Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/kleopatra_22.08.0-2_unstable.log

All bugs f

Bug#1022848: linux: 6.0.5 fixes critical btrfs bug

[Christoph Anton Mitterer]

Hey Salvatore.

On Fri, 2022-10-28 at 06:49 +0200, Salvatore Bonaccorso wrote:
> I did decide to still do so, so we can have the CVE fix migrate
> finally to testing (which took some time as well given there was the
> perl transition ongoing).

Fine for me... I think it would be nice if there was a better mechanism
to have bugs shown in apt-listbugs out of the box, while still not
preventing migration to testing.


Oh and another off-topic thing:

Right now the kernel image meta-packages depend on the (secure boot)
signed version of that... and it seems that these take always longer to
be available than the unsigned ones.

However, if people want the nice service to have linux-image-amd64
installed and pull in just the current package, they need to wait for
the signed one to become available - even if they don't use secure boot
at all.

So question is,.. would it make sense to request that linux-image-amd64
depends on the signed | unsigned version?



> I did import already 6.0.5 and will upload next so we get the btrfs
> fix. And I have made the bug now as well again back RC severity.

Thanks as always for your continued efforts.


Cheers,
Chris.

Bug#1021524: marked as done (lomiri-system-settings is not installable)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 21:59:54 +
with message-id 
and subject line Bug#1021524: fixed in lomiri-system-settings 
1.0~git20221028.ca6da85-1
has caused the Debian Bug report #1021524,
regarding lomiri-system-settings is not installable
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.)


-- 
1021524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lomiri-system-settings
Version: 1.0~git20221004.572f3a9-1
Severity: serious

The following packages have unmet dependencies:
 lomiri-system-settings : Depends: lomiri-keyboard-data but it is not 
installable
  Depends: ubports-wallpapers but it is not installable
--- End Message ---
--- Begin Message ---
Source: lomiri-system-settings
Source-Version: 1.0~git20221028.ca6da85-1
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
lomiri-system-settings, 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 1021...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated lomiri-system-settings 
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: Fri, 28 Oct 2022 22:58:33 +0200
Source: lomiri-system-settings
Architecture: source
Version: 1.0~git20221028.ca6da85-1
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team 
Changed-By: Mike Gabriel 
Closes: 1021524
Changes:
 lomiri-system-settings (1.0~git20221028.ca6da85-1) unstable; urgency=medium
 .
   [ Mike Gabriel ]
   * New upstream Git snapshot.
   * debian/patches/:
 + Drop 0001_copyright-headers-Use-uniform-spelling-for-copyright.patch.
   Applied upstream.
   * debian/control:
 + Switch from ubports-wallpapers to lomiri-wallpapers (currently in
   Debian's NEW queue); comment out lomiri-keyboard-data (we don't
   build the language plugin for now). (Closes: #1021524).
   * debian/copyright:
 + Update copyright attributions.
 .
   [ Anton Gladky ]
   * Add debian/.gitlab-ci.yml
   * Let blhc fail
Checksums-Sha1:
 f4624b619aba54fdfed914ecf9071515207942b6 3772 
lomiri-system-settings_1.0~git20221028.ca6da85-1.dsc
 3f524ddbff947b933fbc0cebcbbdd8f720a2e44e 3578696 
lomiri-system-settings_1.0~git20221028.ca6da85.orig.tar.xz
 c87d9dba070dbd8039efa0aa6a4448d3016c8469 9328 
lomiri-system-settings_1.0~git20221028.ca6da85-1.debian.tar.xz
 dc3ad569711b9191668b44ecbcfc55240b371233 17707 
lomiri-system-settings_1.0~git20221028.ca6da85-1_source.buildinfo
Checksums-Sha256:
 124e7eb5de30cb43abc9804599dc53efcd49672e43dd4cedc48139207c6d59f2 3772 
lomiri-system-settings_1.0~git20221028.ca6da85-1.dsc
 f7e0a5461947bb9700fcbcbb6065779b0511091362c9ed7a876b8fdc2275ec8f 3578696 
lomiri-system-settings_1.0~git20221028.ca6da85.orig.tar.xz
 51fcf9baeacdc22d8d563a9fb7483154ed9746d5f626462d0835248a3daeb183 9328 
lomiri-system-settings_1.0~git20221028.ca6da85-1.debian.tar.xz
 cd5f803c90b987e48f6ae9d8eee7d78b1663d12ab1410876abccfa631be4dd29 17707 
lomiri-system-settings_1.0~git20221028.ca6da85-1_source.buildinfo
Files:
 cfde16c964a7d2bccc98b7e9c36fac97 3772 misc optional 
lomiri-system-settings_1.0~git20221028.ca6da85-1.dsc
 23ec48382ffed80316bc3139ee345be2 3578696 misc optional 
lomiri-system-settings_1.0~git20221028.ca6da85.orig.tar.xz
 04477a85c39db9f29395720df0452535 9328 misc optional 
lomiri-system-settings_1.0~git20221028.ca6da85-1.debian.tar.xz
 4cef0e1c0561d601e398205507a24746 17707 misc optional 
lomiri-system-settings_1.0~git20221028.ca6da85-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmNcRbQVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsx4bMQAKkXlpyOk4fVSt2tpVbPetWTKCSn
osV3LnlB/z0kx5O9j+4OhPwygFTxPLZ+opVAPmcFgNdhol36N9g7uBIgCkE/DOxa
5xG5YSobiusbiZze0LjI0IaKYDz5aKBzjq5CeKhJYs/gQ5Yim9DEfhajPw5PVbZk
W4Sgi8WmD/gPrGwWexCTRtQYNrYnoaK2/ZqAQT6yYT5Dpe9hpFz0gkZsHZeFF5fC
A7M8T7qhUOXagFTITXE79KLFPCAvHwAArZHLBvMWUbjaSMSe9m27benpTlxh/Ndw
MUODQ69MgAYdSp3J6TdGC3Lc9pXJdh5cSeSCHhl6jfQZSo17eg5JIT43mJJDQUWS
C2Qwmr5/g605JyX7csIwauP+SgIQ6OnTTfZEXNdUKORe10izPtQZHZhRfXvWj13W
1tb0j8rhmXHr7yHEazhn4xpulTQui

Bug#1023000: dpdk: flaky autopkgtest on amd64 and ppc64el: pdump_autotest time out

[Paul Gevers]

Source: dpdk
Version: 20.11.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails on amd64 and ppc64el. From a cursory look it 
seems to have started around August 2022. The error seems to be 
different between different failures.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/testing/ppc64el/d/dpdk/27590240/log.gz

54/57 DPDK:fast-tests / pdump_autotest   RUNNING
>>> DPDK_TEST=pdump_autotest MALLOC_PERTURB_=178 
/tmp/autopkgtest-lxc.wxrxh9zu/downtmp/build.zmC/src/build/app/test/dpdk-test 
--no-huge -m 2048 --file-prefix=pdump_autotest
― ✀ 
―

EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /tmp/tmp.k8x9WW5het/dpdk/pdump_autotest/mp_socket
EAL: Physical addresses are unavailable, selecting IOVA as VA mode.
EAL: Selected IOVA mode 'VA'
EAL: WARNING! Base virtual address hint (0x101865000 != 0x7fff1f58) 
not respected!

EAL:This may cause issues with mapping memory into secondary processes
EAL: Probe PCI driver: net_virtio (1af4:1000) device: :00:01.0 
(socket 0)

eth_virtio_pci_init(): Failed to init PCI device
EAL: Requested device :00:01.0 cannot be used
APP: HPET is not enabled, using TSC as default timer
RTE>>pdump_autotest
IN PRIMARY PROCESS
pdump_init success
Running binary with 
argv[]:'/tmp/autopkgtest-lxc.wxrxh9zu/downtmp/build.zmC/src/build/app/test/dpdk-test' 
'-c' '1' '--proc-type=secondary' '--file-prefix=pdump_autotest'

EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket 
/tmp/tmp.k8x9WW5het/dpdk/pdump_autotest/mp_socket_16805_20758caec7b059

EAL: Physical addresses are unavailable, selecting IOVA as VA mode.
EAL: Selected IOVA mode 'VA'
EAL: Failed to open shared memory!
EAL: FATAL: Cannot get hugepage information.
EAL: Cannot get hugepage information.
EAL: Cannot destroy local memory map
EAL: Could not release memory subsystem data
IN PRIMARY PROCESS
pdump_init success
pdump_uninit success
Test OK
RTE>>DPDK:fast-tests / pdump_autotest time out (After 30.0 seconds)
――
54/57 DPDK:fast-tests / pdump_autotest   TIMEOUT30.06s 
killed by signal 15 SIGTERM


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1017161: gringo: FTBFS: catch.hpp:6415:41: error: array bound is not an integer constant before ‘]’ token

[s3v]

Dear Maintainer,

[...]
> In file included from /<>/clasp/libpotassco/tests/main.cpp:19:
> /<>/clasp/libpotassco/tests/catch.hpp:6415:41: error: array 
> bound is not an integer constant before ‘]’ token
>  6415 | static char altStackMem[SIGSTKSZ];
>   | ^
> /<>/clasp/libpotassco/tests/catch.hpp: In constructor 
> ‘Catch::FatalConditionHandler::FatalConditionHandler()’:
> /<>/clasp/libpotassco/tests/catch.hpp:6434:30: error: 
> ‘altStackMem’ was not declared in this scope
>  6434 | sigStack.ss_sp = altStackMem;
>   |  ^~~
> /<>/clasp/libpotassco/tests/catch.hpp: At global scope:
> /<>/clasp/libpotassco/tests/catch.hpp:6466:53: error: array 
> bound is not an integer constant before ‘]’ token
>  6466 | char FatalConditionHandler::altStackMem[SIGSTKSZ] = {};
>   | ^
> [ 11%] Linking CXX executable ../../../bin/lpconvert
[...]

I guess the failure is a consequence of a bug in clasp that affects your 
package.
Please see [1] for reference.

Kind Regards

[1] https://github.com/potassco/libpotassco/issues/12

Processed: Re: Bug#1022991: libc6: broken y2038 support in fstatat on mips64el

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=29730
Bug #1022991 [libc6] libc6: broken y2038 support in fstatat on mips64el
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=29730'.

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

Bug#1022991: libc6: broken y2038 support in fstatat on mips64el

[Aurelien Jarno]

control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=29730

On 2022-10-28 20:35, Aurelien Jarno wrote:
> Package: libc6
> Version: 2.35-1
> Severity: critical
> Tags: upstream
> Justification: breaks unrelated software
> 
> On mips64el the fstat/fstatat/lstat functions return EOVERFLOW when they
> are called on files with a mtime, atime or ctime that can't be
> represented within a 32-bit time_t. This should not happen as time_t is
> 64-bit on mips64el. This is a regression from glibc 2.34 and can be
> reproduce with:
> 
> (sid_mips64el-dchroot)aurel32@eller:~$ touch -d 20390101 t
> (sid_mips64el-dchroot)aurel32@eller:~$ chmod +x t
> chmod: cannot access 't': Value too large for defined data type
> (sid_mips64el-dchroot)aurel32@eller:~$ 
> 
> This breaks unrelated software, for instance the build of gcc-12 on the
> build daemons:
> 
> https://buildd.debian.org/status/fetch.php?pkg=gcc-12&arch=mips64el&ver=12.2.0-7&stamp=1666806816&raw=0

I have identified the commit causing the issue, and forwarded the bug
upstream. See: https://sourceware.org/bugzilla/show_bug.cgi?id=29730

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#1020456: cypari2 FTBFS with PARI 2.15.0

[Tobias Hansen]

Thanks! I will apply the patch once the pari version with the other fixes is 
uploaded.

Best wishes,
Tobias

On 10/26/22 10:55, Bill Allombert wrote:
> Also I consider the error message change
> - PariError: call_python: forbidden multiplication t_VEC (1 elts) * t_VEC 
> (1 elts)
> + PariError: call_python: incorrect type in qfbcomp (t_VEC)
> to be a bug in PARI/GP that I will fix too.
>
> For the others, I join a patch.
>
> Cheers,

Bug#1021138: marked as done (php8.1: CVE-2022-31628 CVE-2022-31629)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 21:30:30 +0200
with message-id 
and subject line Re: Accepted php8.1 8.1.12-1 (source) into unstable
has caused the Debian Bug report #1021138,
regarding php8.1: CVE-2022-31628 CVE-2022-31629
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.)


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

Hi,

The following vulnerabilities were published for php8.1.

CVE-2022-31628[0]:
| In PHP versions before 7.4.31, 8.0.24 and 8.1.11, the phar
| uncompressor code would recursively uncompress "quines" gzip files,
| resulting in an infinite loop.

PHP Bug: https://bugs.php.net/bug.php?id=81726
https://github.com/php/php-src/commit/404e8bdb68350931176a5bdc86fc417b34fb583d
https://github.com/php/php-src/commit/432bf196d59bcb661fcf9cb7029cea9b43f490af

CVE-2022-31629[1]:
| In PHP versions before 7.4.31, 8.0.24 and 8.1.11, the vulnerability
| enables network and same-site attackers to set a standard insecure
| cookie in the victim's browser which is treated as a `__Host-` or
| `__Secure-` cookie by PHP applications.

PHP Bug: https://bugs.php.net/bug.php?id=81727
https://github.com/php/php-src/commit/0611be4e82887cee0de6c4cbae320d34eec946ca

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-2022-31628
https://www.cve.org/CVERecord?id=CVE-2022-31628
[1] https://security-tracker.debian.org/tracker/CVE-2022-31629
https://www.cve.org/CVERecord?id=CVE-2022-31629

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: php8.1
Source-Version: 8.1.12-1

On Fri, Oct 28, 2022 at 06:37:31PM +, Debian FTP Masters wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Fri, 28 Oct 2022 19:32:24 +0200
> Source: php8.1
> Architecture: source
> Version: 8.1.12-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian PHP Maintainers 
> Changed-By: Ondřej Surý 
> Changes:
>  php8.1 (8.1.12-1) unstable; urgency=medium
>  .
>* New upstream version 8.1.12
> + CVE-2022-31630: OOB read due to insufficient input validation in
>   imageloadfont()
> + CVE-2022-37454: buffer overflow in hash_update() on long parameter
> Checksums-Sha1:
>  e90232a73a5a2da9bfad5c326d8a90c658a4aa76 5694 php8.1_8.1.12-1.dsc
>  5edef81be360eba654ea015bdb3fa10654b8ff94 11747176 php8.1_8.1.12.orig.tar.xz
>  de98b50219ac62cffdc81ba67b2a55719a7ed055 833 php8.1_8.1.12.orig.tar.xz.asc
>  389af6a53f115e275da3c3592448cc7eb3c385c8 67180 php8.1_8.1.12-1.debian.tar.xz
>  6c6e020d1e8abd088a85dd7c428310a9ba77c6d6 32723 
> php8.1_8.1.12-1_amd64.buildinfo
> Checksums-Sha256:
>  90795e4d2e65d029aacd300ae90f374925c43ce689f2967e41a6808ce4e3df46 5694 
> php8.1_8.1.12-1.dsc
>  08243359e2204d842082269eedc15f08d2eca726d0e65b93fb11f4bfc51bbbab 11747176 
> php8.1_8.1.12.orig.tar.xz
>  3f1a4452a9cfed4c7a4872eef471e0cd18a43ebd5d8d695ffcd483d705d54a53 833 
> php8.1_8.1.12.orig.tar.xz.asc
>  168572ef036c1718280ddf3512cdf7990319eb261814f3f741a5de585352df9d 67180 
> php8.1_8.1.12-1.debian.tar.xz
>  7037afc052e4e915450b8a91349fe5f2f3b6ade052fb1ec2ae154567a66cb2ac 32723 
> php8.1_8.1.12-1_amd64.buildinfo
> Files:
>  3b1f8fd6cca9a906cf242f5e49bc34e2 5694 php optional php8.1_8.1.12-1.dsc
>  6a30e4eb25ff9a73dafe7582ae838c17 11747176 php optional 
> php8.1_8.1.12.orig.tar.xz
>  2fd0ab115a84fe8f3a38e4ea2218b467 833 php optional 
> php8.1_8.1.12.orig.tar.xz.asc
>  531ac3f146be4d26011bd74dae2f98a1 67180 php optional 
> php8.1_8.1.12-1.debian.tar.xz
>  38fec20b5efe2b21774da0b986330432 32723 php optional 
> php8.1_8.1.12-1_amd64.buildinfo
> 
> -BEGIN PGP SIGNATURE-
> 
> iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmNcHk5fFIAALgAo
> aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
> NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
> WcLHTw//dm0yY2ewj0kpC32mNo/1mijOM/kafe247ujZgmfX52vUA+WLOGn532eG
> RYBi6KmKpYxxK+3ThEGRNdGk7px8pmButGzaU+myeRhFSIciQB4IB0J+YtUXtuBp
> 8F946T8yKvoGT+WqPbA1BdE77F92tqbHdObzAoHEl4cRTaY2Wxp+zR8F0Vz/Wd0o
> TrJBzKMwm7skLJ44WLXcOJ0DSEerDHFO9lRpEzo/aYedv6OjtV7PvBbcDkAKvQAP
> CjO5AbKcT2McAMZL///KryJAksfkCvdUg3zOEAva8js1b03rzT9oKc6VrnM41WT3
> KFciwOCVuzcytGeaR0JC05xmxqD9vbeTRqdk0GsmpFgftkr2RvUhdLC/GsvUByk1
> df4EM2BdWEkCErx9fofeZOJZItMf7+7Cq7dXLMSE+js87GITAn7SpKhpHMp3

Bug#1016972: marked as done (php8.1: CVE-2022-31627)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 21:29:15 +0200
with message-id 
and subject line Re: Accepted php8.1 8.1.12-1 (source) into unstable
has caused the Debian Bug report #1016972,
regarding php8.1: CVE-2022-31627
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.)


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

Hi,

The following vulnerability was published for php8.1.

It's specific to 8.1.x

CVE-2022-31627[0]:
| In PHP versions 8.1.x below 8.1.8, when fileinfo functions, such as
| finfo_buffer, due to incorrect patch applied to the third party code
| from libmagic, incorrect function may be used to free allocated
| memory, which may lead to heap corruption.

PHP Bug: https://bugs.php.net/bug.php?id=81723
https://github.com/php/php-src/commit/ca6d511fa54b34d5b75bf120a86482a1b9e1e686


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-2022-31627
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31627

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: php8.1
Source-Version: 8.1.12-1

On Fri, Oct 28, 2022 at 06:37:31PM +, Debian FTP Masters wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Fri, 28 Oct 2022 19:32:24 +0200
> Source: php8.1
> Architecture: source
> Version: 8.1.12-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian PHP Maintainers 
> Changed-By: Ondřej Surý 
> Changes:
>  php8.1 (8.1.12-1) unstable; urgency=medium
>  .
>* New upstream version 8.1.12
> + CVE-2022-31630: OOB read due to insufficient input validation in
>   imageloadfont()
> + CVE-2022-37454: buffer overflow in hash_update() on long parameter
> Checksums-Sha1:
>  e90232a73a5a2da9bfad5c326d8a90c658a4aa76 5694 php8.1_8.1.12-1.dsc
>  5edef81be360eba654ea015bdb3fa10654b8ff94 11747176 php8.1_8.1.12.orig.tar.xz
>  de98b50219ac62cffdc81ba67b2a55719a7ed055 833 php8.1_8.1.12.orig.tar.xz.asc
>  389af6a53f115e275da3c3592448cc7eb3c385c8 67180 php8.1_8.1.12-1.debian.tar.xz
>  6c6e020d1e8abd088a85dd7c428310a9ba77c6d6 32723 
> php8.1_8.1.12-1_amd64.buildinfo
> Checksums-Sha256:
>  90795e4d2e65d029aacd300ae90f374925c43ce689f2967e41a6808ce4e3df46 5694 
> php8.1_8.1.12-1.dsc
>  08243359e2204d842082269eedc15f08d2eca726d0e65b93fb11f4bfc51bbbab 11747176 
> php8.1_8.1.12.orig.tar.xz
>  3f1a4452a9cfed4c7a4872eef471e0cd18a43ebd5d8d695ffcd483d705d54a53 833 
> php8.1_8.1.12.orig.tar.xz.asc
>  168572ef036c1718280ddf3512cdf7990319eb261814f3f741a5de585352df9d 67180 
> php8.1_8.1.12-1.debian.tar.xz
>  7037afc052e4e915450b8a91349fe5f2f3b6ade052fb1ec2ae154567a66cb2ac 32723 
> php8.1_8.1.12-1_amd64.buildinfo
> Files:
>  3b1f8fd6cca9a906cf242f5e49bc34e2 5694 php optional php8.1_8.1.12-1.dsc
>  6a30e4eb25ff9a73dafe7582ae838c17 11747176 php optional 
> php8.1_8.1.12.orig.tar.xz
>  2fd0ab115a84fe8f3a38e4ea2218b467 833 php optional 
> php8.1_8.1.12.orig.tar.xz.asc
>  531ac3f146be4d26011bd74dae2f98a1 67180 php optional 
> php8.1_8.1.12-1.debian.tar.xz
>  38fec20b5efe2b21774da0b986330432 32723 php optional 
> php8.1_8.1.12-1_amd64.buildinfo
> 
> -BEGIN PGP SIGNATURE-
> 
> iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmNcHk5fFIAALgAo
> aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
> NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
> WcLHTw//dm0yY2ewj0kpC32mNo/1mijOM/kafe247ujZgmfX52vUA+WLOGn532eG
> RYBi6KmKpYxxK+3ThEGRNdGk7px8pmButGzaU+myeRhFSIciQB4IB0J+YtUXtuBp
> 8F946T8yKvoGT+WqPbA1BdE77F92tqbHdObzAoHEl4cRTaY2Wxp+zR8F0Vz/Wd0o
> TrJBzKMwm7skLJ44WLXcOJ0DSEerDHFO9lRpEzo/aYedv6OjtV7PvBbcDkAKvQAP
> CjO5AbKcT2McAMZL///KryJAksfkCvdUg3zOEAva8js1b03rzT9oKc6VrnM41WT3
> KFciwOCVuzcytGeaR0JC05xmxqD9vbeTRqdk0GsmpFgftkr2RvUhdLC/GsvUByk1
> df4EM2BdWEkCErx9fofeZOJZItMf7+7Cq7dXLMSE+js87GITAn7SpKhpHMp3hU8Q
> dP4TixdhF6uZwwVWZI2aCJ18RmFl+BoyQSNOxU4pYKmtPD0w47ytJhAyuYKO7RpS
> ooLR8KI9Q8zT6IPaILUDnpE/mGBoKL8k9+YAmTWi13io1QTg5A1o4awCRd4MdtzG
> rmB2PDrmQrNZEogeqfYN878xwiagxK7ovYwwXP3NP2NFwu3HoeL+014geJB6RKGl
> i4ba0qavHtBfN0OX9JyUgS2ekfszGVn7tCsiZCoQ+fOXe54ouic=
> =LT9J
> -END PGP SIGNATURE-
> --- End Message ---

Processed: found 1016972 in 8.1.7-1

[Debian Bug Tracking System]

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

> found 1016972 8.1.7-1
Bug #1016972 [src:php8.1] php8.1: CVE-2022-31627
Marked as found in versions php8.1/8.1.7-1.
> thanks
Stopping processing here.

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

Bug#1017845: New upload should resolve native compilation fork bomb problem

[Axel Beckert]

Hi Sean,

Sean Whitton wrote:
> > Ok, someone gave back emacs:all and it built now.
> 
> Yeah, there's a flaky test.

I see.

> > Unfortunately the issue still shows up for me:
> 
> Thank you for testing so promptly.

You're welcome!

Actually I'm very keen on seeing a (working ;-) Emacs 28 in Debian
Unstable as one of my packages (elpa-ligature) only seems to work
properly with Emacs 28 (and occasionally crashes Emacs 27 due to a
missing fix there according to upstream)… Because then I can finally
move it from experimental to unstable, too. :-)

> There's an additional patch that just made it to upstream master
> that tries to address the trampoline problem. I've just uploaded
> that to sid. Could you let me know whether it helps, please?

Will do, once the packages are on incoming.d.o.

And thanks for your patience and pertinaciousness with this issue. :-)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#1022991: libc6: broken y2038 support in fstatat on mips64el

[Aurelien Jarno]

Package: libc6
Version: 2.35-1
Severity: critical
Tags: upstream
Justification: breaks unrelated software

On mips64el the fstat/fstatat/lstat functions return EOVERFLOW when they
are called on files with a mtime, atime or ctime that can't be
represented within a 32-bit time_t. This should not happen as time_t is
64-bit on mips64el. This is a regression from glibc 2.34 and can be
reproduce with:

(sid_mips64el-dchroot)aurel32@eller:~$ touch -d 20390101 t
(sid_mips64el-dchroot)aurel32@eller:~$ chmod +x t
chmod: cannot access 't': Value too large for defined data type
(sid_mips64el-dchroot)aurel32@eller:~$ 

This breaks unrelated software, for instance the build of gcc-12 on the
build daemons:

https://buildd.debian.org/status/fetch.php?pkg=gcc-12&arch=mips64el&ver=12.2.0-7&stamp=1666806816&raw=0

Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists

[Gert]

I suspect to have this same bug.

In case it's useful, I got kernel logs via serial console, see attachment.
Therein I have marked where VGA console output stops.
Serial console goes a bit further.
SysRq+B still works.

My system: MSI 785GM-E51 (AMD 785G+SB710) + Dell Radeon R5 240 OEM (Oland).
I use radeon.si_support=0 amdgpu.si_support=1 amdgpu.dc=0.
I put the drivers inside initramfs. Outside doesn't work either but 
hangs a bit later.

5.19.0-0.deb11.2-amd64 works fine at first glance.

Currently I have little time for "big" things like git-bisect, sorry.
But I'm happy to test smaller things.
Thanks, GertSerial console log, also visible on VGA console:

[0.00] Linux version 5.10.0-19-amd64 (debian-ker...@lists.debian.org) 
(gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 
2.35.2) #1 SMP Debian 5.10.149-2 (2022-10-21)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-5.10.0-19-amd64 
root=UUID=4594ae40-1c56-4123-b65a-bfad982b83b3 ro rootflags=subvol=debian 
nmi_watchdog=0 clocksource=hpet ipv6.disable=1 nokaiser nopti pti=off 
usbhid.quirks=0x2341:0x8037:0x040 usbhid.jspoll=1 console=tty0 
console=ttyS0,115200n8 text
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009f3ff] usable
[0.00] BIOS-e820: [mem 0x0009f400-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e6000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xcfe8] usable
[0.00] BIOS-e820: [mem 0xcfe9-0xcfe9dfff] ACPI data
[0.00] BIOS-e820: [mem 0xcfe9e000-0xcfed] ACPI NVS
[0.00] BIOS-e820: [mem 0xcfee-0xcfef] reserved
[0.00] BIOS-e820: [mem 0xfff0-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00022fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.5 present.
[0.00] DMI: MICRO-STAR INTERNATIONAL CO.,LTD MS-7596/785GM-E51 
(MS-7596), BIOS V2.12 02/18/2011
[0.00] tsc: Fast TSC calibration using PIT
[0.00] tsc: Detected 3599.944 MHz processor
[0.013438] AGP: No AGP bridge found
[0.013513] last_pfn = 0x23 max_arch_pfn = 0x4
[0.013756] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.013902] last_pfn = 0xcfe90 max_arch_pfn = 0x4
[0.017282] found SMP MP-table at [mem 0x000ff780-0x000ff78f]
[0.024303] Using GB pages for direct mapping
[0.024641] RAMDISK: [mem 0x33e2b000-0x35f0cfff]
[0.024647] ACPI: Early table checksum verification disabled
[0.024652] ACPI: RSDP 0x000FAD00 14 (v00 ACPIAM)
[0.024655] ACPI: RSDT 0xCFE9 40 (v01 7596MS A7596200 
20110218 MSFT 0097)
[0.024661] ACPI: FACP 0xCFE90200 84 (v01 7596MS A7596200 
20110218 MSFT 0097)
[0.024665] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has 
valid Length but zero Address: 0x/0x1 (20200925/tbfadt-615)
[0.024670] ACPI: DSDT 0xCFE905D0 0093B2 (v01 A7596  A7596200 
0200 INTL 20051117)
[0.024673] ACPI: FACS 0xCFE9E000 40
[0.024676] ACPI: APIC 0xCFE90390 7C (v01 7596MS A7596200 
20110218 MSFT 0097)
[0.024679] ACPI: MCFG 0xCFE90410 3C (v01 7596MS OEMMCFG  
20110218 MSFT 0097)
[0.024682] ACPI: OEMB 0xCFE9E040 72 (v01 7596MS A7596200 
20110218 MSFT 0097)
[0.024685] ACPI: SRAT 0xCFE9A5D0 C8 (v03 AMDFAM_F_10 
0002 AMD  0001)
[0.024688] ACPI: HPET 0xCFE9A6A0 38 (v01 7596MS OEMHPET  
20110218 MSFT 0097)
[0.024691] ACPI: SSDT 0xCFE9A6E0 000458 (v01 A M I  POWERNOW 
0001 AMD  0001)
[0.024694] ACPI: Reserving FACP table memory at [mem 0xcfe90200-0xcfe90283]
[0.024696] ACPI: Reserving DSDT table memory at [mem 0xcfe905d0-0xcfe99981]
[0.024697] ACPI: Reserving FACS table memory at [mem 0xcfe9e000-0xcfe9e03f]
[0.024698] ACPI: Reserving APIC table memory at [mem 0xcfe90390-0xcfe9040b]
[0.024699] ACPI: Reserving MCFG table memory at [mem 0xcfe90410-0xcfe9044b]
[0.024700] ACPI: Reserving OEMB table memory at [mem 0xcfe9e040-0xcfe9e0b1]
[0.024702] ACPI: Reserving SRAT table memory at [mem 0xcfe9a5d0-0xcfe9a697]
[0.024703] ACPI: Reserving HPET table memory at [mem 0xcfe9a6a0-0xcfe9a6d7]
[0.024704] ACPI: Reserving SSDT table memory at [mem 0xcfe9a6e0-0xcfe9ab37]
[0.024742] SRAT: PXM 0 -> APIC 0x00 -> Node 0
[0.024743] SRAT: PXM 0 -> APIC 0x01 -> Node 0
[0.024746] ACPI: SRAT: Node 0 PXM 0 [mem 0x-0x0009]
[0.024747] ACPI: SRAT: Node 0 PXM 0 [mem 0x0010-0xcfff]
[0.024748] ACPI: SRAT: Node 0 PXM 0 [mem 0x1-0x22fff]
[0.024751] NUMA: Node 0 [mem 0x-0x0009] + [mem 
0x0010

Bug#1017845: New upload should resolve native compilation fork bomb problem

[Sean Whitton]

Hello,

On Thu 27 Oct 2022 at 12:47AM +02, Axel Beckert wrote:

> Control: found -1 1:28.2+1-2
>
> Hi Sean,
>
> Axel Beckert wrote:
>> Sean Whitton wrote:
>> > Could you see if the upload I just made, 28.2+1-2, still shows the
>> > problem, please?  It includes a backported upstream fix.  Thanks.
>>
>> Would like to, but can't as "emacs-common (= 1:28.2+1-2)" is
>> unavailable due to a FTBFS:
>> https://buildd.debian.org/status/package.php?p=emacs
>
> Ok, someone gave back emacs:all and it built now.

Yeah, there's a flaky test.

> Unfortunately the issue still shows up for me:

Thank you for testing so promptly.  There's an additional patch that
just made it to upstream master that tries to address the trampoline
problem.  I've just uploaded that to sid.  Could you let me know whether
it helps, please?

Thanks.

-- 
Sean Whitton

Bug#1022854: debuerreotype: autopkgtest rebuilds with different toolchain and expects the same result

[Tianon Gravi]

On Fri, 28 Oct 2022 at 10:42, Luca Boccassi  wrote:
> (18:32:13) bluca: the debuerrotype maintainer explicitly asked not to,
> and instead to ask for a migration hint
> (18:32:46) elbrus: we'll not do that
> (18:32:58) elbrus: as the autopkgtest regression in testing is RC

Sorry, this was my miscommunication!  I'm totally fine with this bug
being RC if that allows debootstrap to transition and unblocks others
(I probably used the wrong terms in my previous email).  Thanks for
following up!

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#1022980: src:ruby-vcr: fails to migrate to testing for too long: ftbfs

[Paul Gevers]

Source: ruby-vcr
Version: 6.0.0+really5.0.0-2
Severity: serious
Control: close -1 6.0.0+really5.0.0-3
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1019674

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:ruby-vcr has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package failed to build from 
source.


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 bookworm, 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/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=ruby-vcr



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:ruby-vcr: fails to migrate to testing for too long: ftbfs

[Debian Bug Tracking System]

Processing control commands:

> close -1 6.0.0+really5.0.0-3
Bug #1022980 [src:ruby-vcr] src:ruby-vcr: fails to migrate to testing for too 
long: ftbfs
The source 'ruby-vcr' and version '6.0.0+really5.0.0-3' do not appear to match 
any binary packages
Marked as fixed in versions ruby-vcr/6.0.0+really5.0.0-3.
Bug #1022980 [src:ruby-vcr] src:ruby-vcr: fails to migrate to testing for too 
long: ftbfs
Marked Bug as done
> block -1 by 1019674
Bug #1022980 {Done: Paul Gevers } [src:ruby-vcr] 
src:ruby-vcr: fails to migrate to testing for too long: ftbfs
1022980 was not blocked by any bugs.
1022980 was not blocking any bugs.
Added blocking bug(s) of 1022980: 1019674

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

Processed: src:gnumach: fails to migrate to testing for too long: ftbfs on amd64

[Debian Bug Tracking System]

Processing control commands:

> close -1 2:1.8+git20220827-3
Bug #1022979 [src:gnumach] src:gnumach: fails to migrate to testing for too 
long: ftbfs on amd64
Marked as fixed in versions gnumach/2:1.8+git20220827-3.
Bug #1022979 [src:gnumach] src:gnumach: fails to migrate to testing for too 
long: ftbfs on amd64
Marked Bug as done

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

Bug#1022979: src:gnumach: fails to migrate to testing for too long: ftbfs on amd64

[Paul Gevers]

Source: gnumach
Version: 2:1.8+git20220218-3
Severity: serious
Control: close -1 2:1.8+git20220827-3
Tags: sid bookworm ftbfs
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 60 days as having a Release Critical bug in 
testing [1]. Your package src:gnumach has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package failed to build from 
source on amd64, where it built successfully in the past.


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 bookworm, 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/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=gnumach



OpenPGP_signature
Description: OpenPGP digital signature

Processed (with 1 error): Re: Bug#1022854: debuerreotype: autopkgtest rebuilds with different toolchain and expects the same result

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1022854 [debuerreotype] debuerreotype: autopkgtest rebuilds with different 
toolchain and expects the same result
Severity set to 'serious' from 'important'
> justification -1 breaks autopkgtest in testing
Unknown command or malformed arguments to command.


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

Processed: src:atlas-ecmwf: fails to migrate to testing for too long: ftbfs on mips64el and s390x

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.30.0-3
Bug #1022978 [src:atlas-ecmwf] src:atlas-ecmwf: fails to migrate to testing for 
too long: ftbfs on mips64el and s390x
Marked as fixed in versions atlas-ecmwf/0.30.0-3.
Bug #1022978 [src:atlas-ecmwf] src:atlas-ecmwf: fails to migrate to testing for 
too long: ftbfs on mips64el and s390x
Marked Bug as done

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

Bug#1022978: src:atlas-ecmwf: fails to migrate to testing for too long: ftbfs on mips64el and s390x

[Paul Gevers]

Source: atlas-ecmwf
Version: 0.29.0-2
Severity: serious
Control: close -1 0.30.0-3
Tags: sid bookworm ftbfs
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 60 days as having a Release Critical bug in 
testing [1]. Your package src:atlas-ecmwf has been trying to migrate for 
61 days [2]. Hence, I am filing this bug. Your package failed to build 
from source on mips64el and s390x where it built successfully in the past.


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 bookworm, 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/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=atlas-ecmwf



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1022975: Fails to build for 6.0.0: error: implicit declaration of function ‘__grab_cache_page’

[Ryan Kavanagh]

Package: openafs-modules-dkms
Version: 1.8.8.1-3
Severity: grave
Justification: Renders package unusable

The openafs DKMS module fails to build for kernel 6.0.0. Here are the
relevant bits from the end of the attached build log
/var/lib/dkms/openafs/1.8.8.1/build/make.log:

In file included from 
/var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-6.0.0-2-amd64-SP/rx_kmutex.c:24:
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_compat.h:143:1: error: 
conflicting types for ‘grab_cache_page_write_begin’; have ‘struct page *(struct 
address_space *, long unsigned int,  unsigned int)’
  143 | grab_cache_page_write_begin(struct address_space *mapping, pgoff_t 
index,
  | ^~~
In file included from 
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/sysincludes.h:127,
 from 
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_machdep.h:79,
 from /var/lib/dkms/openafs/1.8.8.1/build/src/afs/afs_osi.h:446,
 from 
/var/lib/dkms/openafs/1.8.8.1/build/src/rx/rx_kcommon.h:136,
 from 
/var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-6.0.0-2-amd64-SP/rx_kmutex.c:20:
/usr/src/linux-headers-6.0.0-2-common/include/linux/pagemap.h:734:14: note: 
previous declaration of ‘grab_cache_page_write_begin’ with type ‘struct page 
*(struct address_space *, long unsigned int)’
  734 | struct page *grab_cache_page_write_begin(struct address_space *mapping,
  |  ^~~
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_compat.h: In function 
‘grab_cache_page_write_begin’:
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_compat.h:145:12: error: 
implicit declaration of function ‘__grab_cache_page’; did you mean 
‘grab_cache_page’? [-Werror=implicit-function-declaration]
  145 | return __grab_cache_page(mapping, index);
  |^
  |grab_cache_page
/var/lib/dkms/openafs/1.8.8.1/build/src/afs/LINUX/osi_compat.h:145:12: warning: 
returning ‘int’ from a function with return type ‘struct page *’ makes pointer 
from integer without a cast [-Wint-conversion]
  145 | return __grab_cache_page(mapping, index);
  |^
cc1: some warnings being treated as errors
make[4]: *** [/usr/src/linux-headers-6.0.0-2-common/scripts/Makefile.build:254: 
/var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-6.0.0-2-amd64-SP/rx_kmutex.o]
 Error 1
make[3]: *** [/usr/src/linux-headers-6.0.0-2-common/Makefile:1876: 
/var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-6.0.0-2-amd64-SP] Error 2
make[3]: Leaving directory '/usr/src/linux-headers-6.0.0-2-amd64'
FAILURE: make exit code 2
make[2]: *** [Makefile.afs:280: openafs.ko] Error 1
make[2]: Leaving directory 
'/var/lib/dkms/openafs/1.8.8.1/build/src/libafs/MODLOAD-6.0.0-2-amd64-SP'
make[1]: *** [Makefile:187: linux_compdirs] Error 2
make[1]: Leaving directory '/var/lib/dkms/openafs/1.8.8.1/build/src/libafs'
make: *** [Makefile:15: all] Error 2

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openafs-modules-dkms depends on:
ii  dkms   3.0.6-4
ii  libc6-dev  2.35-4
ii  perl   5.36.0-4

Versions of packages openafs-modules-dkms recommends:
ii  openafs-client  1.8.8.1-3+b2

openafs-modules-dkms suggests no packages.

-- no debconf information

-- 
|)|/  Ryan Kavanagh  | 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac | BD95 8F7B F8FC 4A11 C97A
DKMS make.log for openafs-1.8.8.1 for kernel 6.0.0-2-amd64 (x86_64)
Thu 27 Oct 17:14:46 EDT 2022
checking for gcc... gcc-12
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc-12 accepts -g... yes
checking for gcc-12 option to enable C11 features... none needed
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for sys/time.h... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for grep that handles long lines and -e... /usr/bin/grep
checking for gcc-12 options needed to detect all undeclar

Bug#1020043: marked as done (pillow: FTBFS: ModuleNotFoundError: No module named 'PIL')

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 16:20:33 +
with message-id 
and subject line Bug#1020043: fixed in pillow 9.2.0-1.1
has caused the Debian Bug report #1020043,
regarding pillow: FTBFS: ModuleNotFoundError: No module named 'PIL'
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.)


-- 
1020043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pillow
Version: 9.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> python3 -c "import sphinx" > /dev/null 2>&1 || python3 -m pip install sphinx
> : # python3 -c "import furo" > /dev/null 2>&1 || python3 -m pip install furo
> make[2]: Leaving directory '/<>/docs'
> python3 -m sphinx.cmd.build -b html -W --keep-going -d _build/doctrees   . 
> _build/html
> Running Sphinx v4.5.0
> 
> Configuration error:
> There is a programmable error in your configuration file:
> 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/sphinx/config.py", line 332, in 
> eval_config_file
> exec(code, namespace)
>   File "/<>/docs/conf.py", line 19, in 
> import PIL
> ModuleNotFoundError: No module named 'PIL'
> 
> make[1]: *** [Makefile:50: html] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/pillow_9.2.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 marking 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: pillow
Source-Version: 9.2.0-1.1
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
pillow, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated pillow 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: Fri, 21 Oct 2022 15:53:14 +
Source: pillow
Architecture: source
Version: 9.2.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Nilesh Patra 
Closes: 1020043
Changes:
 pillow (9.2.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch to fix FTBFS (Closes: #1020043)
Checksums-Sha1:
 50df9cb60daf7d948918ff89072789212fb9a9f3 1663 pillow_9.2.0-1.1.dsc
 f3cf2b6740f14ba7d11c3ae2389cdf9578536c20 16352 pillow_9.2.0-1.1.debian.tar.xz
 6e5b2c993f049d15ea5e3bc17ae90ec9199cc4a7 11941 pillow_9.2.0-1.1_amd64.buildinfo
Checksums-Sha256:
 c5f79734d43812bbb1c995cd19fcfc286d49ef65f3a3b58aeab9346e7e8eed66 1663 
pillow_9.2.0-1.1.dsc
 c739c8ccdde6a03c02f91f16fee4c1cfc2698f81ba1b817c5bd1a5cf336a8a67 16352 
pillow_9.2.0-1.1.debian.tar.xz
 d1fb52fd456b9ec347c51f97fc2424e6978adf1966a75bf62d8597f22da42156 11941 
pillow_9.2.0-1.1_amd64.buildinfo
Files:
 49322ee50f368196c34fafc4e71be818 1663 python optional pillow_9.2.0-1.1.dsc
 395a143cb94a071680dd8cf198810d25 16352 python optional 
pillow_9.2.0-1.1.debian.tar.xz
 2795009f59a92f3030d46fee2512d2b0 11941 python optional 
pillow_9.2.0-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCY1v9bgAKCRAqJ5BL1yQ+
2oDbAP0eyTH+8rm/T60Y/V4jFlDrXrUCK05Kw7etjTf4wpAyiQEAkp2yASVdiR7e
Rw0nB2seGPlBm+LM1svmlNB6yWh3EAM=
=GODS
-E

Bug#1022934: closed by Adrian Bunk (Fixed in 0.8.58-1)

[Sebastian Ramacher]

On 2022-10-28 15:45:05 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:libpappsomspp package:
> 
> #1022934: libpappsomspp: FTBFS on i386
> 
> It has been closed by Adrian Bunk .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Adrian Bunk 
>  by
> replying to this email.
> 
> 
> -- 
> 1022934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022934
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Fri, 28 Oct 2022 18:41:51 +0300
> From: Adrian Bunk 
> To: 1022934-d...@bugs.debian.org
> Subject: Fixed in 0.8.58-1
> Message-ID: 
> 
> Version: 0.8.58-1

That version does not exist in the archive

> libpappsomspp (0.8.58-1) bullseye; urgency=low

… and that's the reason why.

Cheers

> ...
>   * d/rules: Fix by Adrian Bunk to work around the excess precision of the x87
> FPU that causes
> https://buildd.debian.org/status/logs.php?pkg=libpappsomspp&arch=i386.
> 
>  -- Filippo Rusconi   Thu, 27 Oct 2022 10:38:00 +0200

> Date: Fri, 28 Oct 2022 00:20:35 +0200
> From: Sebastian Ramacher 
> To: Debian Bug Tracking System 
> Subject: libpappsomspp: FTBFS on i386
> Message-ID: 
> 
> Source: libpappsomspp
> Version: 0.8.55-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
> 
> https://buildd.debian.org/status/fetch.php?pkg=libpappsomspp&arch=i386&ver=0.8.55-1%2Bb1&stamp=1666460310&raw=0
> 
> term_listb.size= 8
>  MOD:00397 mass=57.021463721083
>  MOD:00429 mass=28.031300128964
>  MOD:00382 mass=-20.026214748524
>  MOD:00234 mass=305.068156389475
>  MOD:00838 mass=3.018830236677
>  A 71.037113785565
>  R 156.10025652
>  C 103.009184959665
>  D 115.026943024685
>  E 129.042593089167
>  F 147.068413914529
>  G 57.021463721083
>  H 137.058911859647
>  I 113.084063979011
>  K 128.094963016052
>  L 113.084063979011
>  M 131.040485088629
>  N 114.042927442166
>  P 97.052763850047
>  Q 128.058577506648
>  R 156.10025652
>  S 87.032028405125
>  T 101.047678469607
>  V 99.068413914529
>  W 186.07931295157
>  Y 163.063328534089
>  U 168.964198469607
>  O 255.158291550141
> 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 
> 0% 
> 0% 10% 20% 
> 
> ..:: Test 1 OK ::..
> 
> ..:: second test, new calibration parameters ::..
> 
> ..:: Test 2 OK ::..
> ===
> test cases:  32 |  31 passed | 1 failed
> assertions: 345 | 343 passed | 2 failed
> 
> 
> 
> 94% tests passed, 1 tests failed out of 18
> 
> Total Test time (real) =   3.47 sec
> 
> The following tests FAILED:
> 1 - catch2-only-tests (Failed)
> Errors while running CTest
> make[2]: *** [Makefile:94: test] Error 8
> 
> Cheers
> -- 
> Sebastian Ramacher


-- 
Sebastian Ramacher

Bug#877015: marked as done (fizmo FTBFS with debhelper 10.9)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 15:48:24 +
with message-id 
and subject line Bug#1022757: Removed package(s) from unstable
has caused the Debian Bug report #877015,
regarding fizmo FTBFS with debhelper 10.9
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.)


-- 
877015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fizmo
Version: 0.7.10-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fizmo.html

...
dh_prep -pbuild-stamp
dh_prep: Requested unknown package build-stamp via -p/--package, expected one 
of: fizmo-common fizmo-ncursesw fizmo-console
dh_prep: unknown option or error during option parsing; aborting
debian/rules:31: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 25
--- End Message ---
--- Begin Message ---
Version: 0.7.10-2+rm

Dear submitter,

as the package fizmo has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1022757

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1022934: marked as done (libpappsomspp: FTBFS on i386)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 18:41:51 +0300
with message-id 
and subject line Fixed in 0.8.58-1
has caused the Debian Bug report #1022934,
regarding libpappsomspp: FTBFS on i386
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.)


-- 
1022934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpappsomspp
Version: 0.8.55-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=libpappsomspp&arch=i386&ver=0.8.55-1%2Bb1&stamp=1666460310&raw=0

term_listb.size= 8
 MOD:00397 mass=57.021463721083
 MOD:00429 mass=28.031300128964
 MOD:00382 mass=-20.026214748524
 MOD:00234 mass=305.068156389475
 MOD:00838 mass=3.018830236677
 A 71.037113785565
 R 156.10025652
 C 103.009184959665
 D 115.026943024685
 E 129.042593089167
 F 147.068413914529
 G 57.021463721083
 H 137.058911859647
 I 113.084063979011
 K 128.094963016052
 L 113.084063979011
 M 131.040485088629
 N 114.042927442166
 P 97.052763850047
 Q 128.058577506648
 R 156.10025652
 S 87.032028405125
 T 101.047678469607
 V 99.068413914529
 W 186.07931295157
 Y 163.063328534089
 U 168.964198469607
 O 255.158291550141
0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 
0% 
0% 10% 20% 

..:: Test 1 OK ::..

..:: second test, new calibration parameters ::..

..:: Test 2 OK ::..
===
test cases:  32 |  31 passed | 1 failed
assertions: 345 | 343 passed | 2 failed



94% tests passed, 1 tests failed out of 18

Total Test time (real) =   3.47 sec

The following tests FAILED:
  1 - catch2-only-tests (Failed)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 0.8.58-1

libpappsomspp (0.8.58-1) bullseye; urgency=low
...
  * d/rules: Fix by Adrian Bunk to work around the excess precision of the x87
FPU that causes
https://buildd.debian.org/status/logs.php?pkg=libpappsomspp&arch=i386.

 -- Filippo Rusconi   Thu, 27 Oct 2022 10:38:00 +0200--- End Message ---

Bug#1022795: marked as done (libghc-crypto-numbers-doc: depends on non-existing haddock-interface-35)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 15:27:30 +
with message-id 
and subject line Bug#1022878: Removed package(s) from unstable
has caused the Debian Bug report #1022795,
regarding libghc-crypto-numbers-doc: depends on non-existing 
haddock-interface-35
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.)


-- 
1022795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libghc-crypto-numbers-doc
Version: 0.2.7-10
Severity: serious

Hi,

libghc-crypto-numbers-doc depends on haddock-interface-35 but this
package does not exist in the archive.

-Ralf.
--- End Message ---
--- Begin Message ---
Version: 0.2.7-10+rm

Dear submitter,

as the package haskell-crypto-numbers has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1022878

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1021068: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 15:27:04 +
with message-id 
and subject line Bug#1022876: Removed package(s) from unstable
has caused the Debian Bug report #1021068,
regarding Removal notice: obsolete
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.)


-- 
1021068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-crypto-pubkey
Version: 0.2.8-10
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS
  * Deprecated in favor of cryptonite

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.2.8-10+rm

Dear submitter,

as the package haskell-crypto-pubkey has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1022876

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1021067: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 15:27:30 +
with message-id 
and subject line Bug#1022878: Removed package(s) from unstable
has caused the Debian Bug report #1021067,
regarding Removal notice: obsolete
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.)


-- 
1021067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-crypto-numbers
Version: 0.2.7-10
Severity: serious

I intend to remove this package:

  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.2.7-10+rm

Dear submitter,

as the package haskell-crypto-numbers has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1022878

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1015291: marked as done (haskell-crypto-numbers FTBFS: error: Variable not in scope)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 15:27:30 +
with message-id 
and subject line Bug#1022878: Removed package(s) from unstable
has caused the Debian Bug report #1015291,
regarding haskell-crypto-numbers FTBFS: error: Variable not in scope
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.)


-- 
1015291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-crypto-numbers
Version: 0.2.7-10
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=haskell-crypto-numbers&suite=sid

...
Crypto/Number/Prime.hs:82:6: error:
Variable not in scope: nextPrimeInteger :: Integer -> Integer
   |
82 | (nextPrimeInteger n, rng)
   |  

Crypto/Number/Prime.hs:92:10: error:
• Variable not in scope:
testPrimeInteger :: Integer -> Int# -> Int#
• Perhaps you meant ‘testBitInteger’ (imported from 
GHC.Integer.GMP.Internals)
   |
92 | case testPrimeInteger n tries of
   |  
 at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.

Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
 "haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131

Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup", 
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 709
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe() 
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Version: 0.2.7-10+rm

Dear submitter,

as the package haskell-crypto-numbers has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1022878

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1017201: marked as done (haskell-crypto-pubkey: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.13.0.0-2f220, libghc-bytestring-dev-0.10.10.1-c40ee, libghc-crypto-random-dev-0.0.9-1612d

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 15:27:04 +
with message-id 
and subject line Bug#1022876: Removed package(s) from unstable
has caused the Debian Bug report #1017201,
regarding haskell-crypto-pubkey: FTBFS: unsatisfiable build-dependencies: 
libghc-base-dev-4.13.0.0-2f220, libghc-bytestring-dev-0.10.10.1-c40ee, 
libghc-crypto-random-dev-0.0.9-1612d, libghc-ghc-prim-dev-0.5.3-49209, 
libghc-integer-gmp-dev-1.0.2.0-fa0ae, libghc-vector-dev-0.12.1.2-29734, 
haddock-interface-35, libghc-base-prof-4.13.0.0-2f220, 
libghc-bytestring-prof-0.10.10.1-c40ee, libghc-crypto-random-prof-0.0.9-1612d, 
libghc-ghc-prim-prof-0.5.3-49209, libghc-integer-gmp-prof-1.0.2.0-fa0ae, 
libghc-vector-prof-0.12.1.2-29734
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.)


-- 
1017201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-crypto-pubkey
Version: 0.2.8-10
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-byteable-dev, libghc-byteable-prof, 
> libghc-crypto-numbers-dev (>= 0.2.2), libghc-crypto-numbers-prof, 
> libghc-crypto-pubkey-types-dev (<< 0.5), libghc-crypto-pubkey-types-dev (>= 
> 0.4.1), libghc-crypto-pubkey-types-prof, libghc-crypto-random-dev (<< 0.1), 
> libghc-crypto-random-dev (>= 0.0), libghc-crypto-random-prof, 
> libghc-cryptohash-dev (>= 0.9.1), libghc-cryptohash-prof, build-essential, 
> fakeroot, ghc-doc, libghc-byteable-doc, libghc-crypto-numbers-doc, 
> libghc-crypto-pubkey-types-doc, libghc-crypto-random-doc, 
> libghc-cryptohash-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-byteable-dev, libghc-byteable-prof, 
> libghc-crypto-numbers-dev (>= 0.2.2), libghc-crypto-numbers-prof, 
> libghc-crypto-pubkey-types-dev (<< 0.5), libghc-crypto-pubkey-types-dev (>= 
> 0.4.1), libghc-crypto-pubkey-types-prof, libghc-crypto-random-dev (<< 0.1), 
> libghc-crypto-random-dev (>= 0.0), libghc-crypto-random-prof, 
> libghc-cryptohash-dev (>= 0.9.1), libghc-cryptohash-prof, build-essential, 
> fakeroot, ghc-doc, libghc-byteable-doc, libghc-crypto-numbers-doc, 
> libghc-crypto-pubkey-types-doc, libghc-crypto-random-doc, 
> libghc-cryptohash-doc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [529 B]
> Get:5 copy:/<>/apt_archive ./ Packages [605 B]
> Fetched 2097 B in 0s (172 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libghc-crypto-numbers-dev : Depends: libghc-base-dev-4.13.0.0-2f220 but it 
> is not installable
>  Depends: libghc-bytestring-dev-0.10.10.1-c40ee 
> but it is not installable
>  Depends: libghc-crypto-random-dev-0.0.9-1612d 
> but it is not installable
>  Depends: libghc-ghc-prim-dev-0.5.3-49209 but it 
> is not installable
>  Depends: libghc-integer-gmp-dev-1.0.2.0-fa0ae 
> but it is not installable
>  Depends: libghc-vector-dev-0.12.1.2-29734 but it 
> is not installable
>  libghc-crypto-numbers-doc : Depends: haddock-interface-35 but it is not 
> installable
>  libghc-crypto-numbers-prof : Depends: li

Bug#1019611: marked as done (ruby-asset-sync: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: @yml ||= ::YAML.load(::ERB.new(IO.read(yml_path)).result)[::Rails.env] || {})

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 15:20:24 +
with message-id 
and subject line Bug#1019611: fixed in ruby-asset-sync 2.11.0-1.1
has caused the Debian Bug report #1019611,
regarding ruby-asset-sync: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
   Failure/Error: @yml ||= 
::YAML.load(::ERB.new(IO.read(yml_path)).result)[::Rails.env] || {}
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.)


-- 
1019611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-asset-sync
Version: 2.11.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-asset-sync with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>   Failure/Error: @yml ||= 
> ::YAML.load(::ERB.new(IO.read(yml_path)).result)[::Rails.env] || {}
> 
>   Psych::BadAlias:
> Unknown alias: defaults
>   # ./lib/asset_sync/config.rb:165:in `yml'
>   # ./lib/asset_sync/config.rb:195:in `load_yml!'
>   # ./lib/asset_sync/config.rb:95:in `initialize'
>   # ./spec/unit/rackspace_spec.rb:63:in `new'
>   # ./spec/unit/rackspace_spec.rb:63:in `block (3 levels) in  (required)>'
> 
> Finished in 1 second (files took 0.56587 seconds to load)
> 133 examples, 27 failures, 3 pending
> 
> Failed examples:
> 
> rspec ./spec/unit/asset_sync_spec.rb:105 # AssetSync from yml should default 
> AssetSync to enabled
> rspec ./spec/unit/asset_sync_spec.rb:110 # AssetSync from yml should 
> configure run_on_precompile
> rspec ./spec/unit/asset_sync_spec.rb:114 # AssetSync from yml should 
> configure aws_access_key_id
> rspec ./spec/unit/asset_sync_spec.rb:118 # AssetSync from yml should 
> configure aws_secret_access_key
> rspec ./spec/unit/asset_sync_spec.rb:122 # AssetSync from yml should 
> configure fog_directory
> rspec ./spec/unit/asset_sync_spec.rb:126 # AssetSync from yml should 
> configure fog_region
> rspec ./spec/unit/asset_sync_spec.rb:130 # AssetSync from yml should 
> configure path_style
> rspec ./spec/unit/asset_sync_spec.rb:134 # AssetSync from yml should 
> configure existing_remote_files
> rspec ./spec/unit/asset_sync_spec.rb:138 # AssetSync from yml should default 
> gzip_compression to false
> rspec ./spec/unit/asset_sync_spec.rb:142 # AssetSync from yml should default 
> manifest to false
> rspec ./spec/unit/asset_sync_spec.rb:146 # AssetSync from yml should default 
> asset_regexps to match regexps
> rspec ./spec/unit/asset_sync_spec.rb:158 # AssetSync from yml, exporting to a 
> mobile hybrid development directory should be disabled
> rspec ./spec/unit/google_spec.rb:111 # AssetSync from yml when using S3 
> interop API should configure google_storage_access_key_id
> rspec ./spec/unit/google_spec.rb:115 # AssetSync from yml when using S3 
> interop API should configure google_storage_secret_access_key
> rspec ./spec/unit/google_spec.rb:119 # AssetSync from yml when using S3 
> interop API should not configure google_json_key_location
> rspec ./spec/unit/google_spec.rb:123 # AssetSync from yml when using S3 
> interop API should configure fog_directory
> rspec ./spec/unit/google_spec.rb:127 # AssetSync from yml when using S3 
> interop API should configure existing_remote_files
> rspec ./spec/unit/google_spec.rb:131 # AssetSync from yml when using S3 
> interop API should default gzip_compression to false
> rspec ./spec/unit/google_spec.rb:135 # AssetSync from yml when using S3 
> interop API should default manifest to false
> rspec ./spec/unit/google_spec.rb:146 # AssetSync from yml when using service 
> account API should configure google_json_key_location
> rspec ./spec/unit/google_spec.rb:150 # AssetSync from yml when using service 
> account API should not configure google_storage_secret_access_key
> rspec ./spec/unit/rackspace_spec.rb:66 # AssetSync using Rackspace from yml 
> should keep existing remote files
> rspec ./spec/unit/rackspace_spec.rb:70 # AssetSync using Rackspace from yml 
> should configure rackspace_username
> rspec ./spec/unit/rackspace_spec.rb:74 # AssetSync using Rackspace from yml 
> should configure rackspace_api_key
> rspec ./spec/unit/rackspace_spec.rb:78 # AssetSync using Rackspace from yml 
> should configure fog_directory
> rspec ./spec/unit/rackspace_spec.rb:82 # AssetSync using Rackspace from yml 
> should configure fog_region
> rspec ./spec/unit/rackspace_spec.rb:86 # AssetSync using Rackspace from yml 
> should co

Bug#1020093: marked as done (python-dlt: FTBFS: AssertionError: 1 != 0 : Stdout: dlt/dlt_broker_handlers.py:65:24: E275 missing whitespace after keyword)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 15:20:14 +
with message-id 
and subject line Bug#1020093: fixed in python-dlt 2.0-3.1
has caused the Debian Bug report #1020093,
regarding python-dlt: FTBFS: AssertionError: 1 != 0 : Stdout: 
dlt/dlt_broker_handlers.py:65:24: E275 missing whitespace after keyword
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.)


-- 
1020093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-dlt
Version: 2.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_dlt/build/dlt
> copying dlt/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_dlt/build/dlt
> copying dlt/dlt_broker_handlers.py -> 
> /<>/.pybuild/cpython3_3.10_dlt/build/dlt
> copying dlt/dlt_broker.py -> 
> /<>/.pybuild/cpython3_3.10_dlt/build/dlt
> copying dlt/helpers.py -> 
> /<>/.pybuild/cpython3_3.10_dlt/build/dlt
> copying dlt/py_dlt_receive.py -> 
> /<>/.pybuild/cpython3_3.10_dlt/build/dlt
> copying dlt/dlt.py -> /<>/.pybuild/cpython3_3.10_dlt/build/dlt
> creating /<>/.pybuild/cpython3_3.10_dlt/build/dlt/core
> copying dlt/core/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_dlt/build/dlt/core
> copying dlt/core/core_base.py -> 
> /<>/.pybuild/cpython3_3.10_dlt/build/dlt/core
> copying dlt/core/core_2185.py -> 
> /<>/.pybuild/cpython3_3.10_dlt/build/dlt/core
> copying dlt/core/core_2186.py -> 
> /<>/.pybuild/cpython3_3.10_dlt/build/dlt/core
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.10_dlt/build; 
> python3.10 -m nose -v tests
> tests.condition_tests.TestsLimitCondition.test_limit_decreasing ... ok
> tests.condition_tests.TestsLimitCondition.test_none ... ok
> tests.continuousness_helper_test.TestsContinuousness.test_ignore_control ... 
> ok
> tests.continuousness_helper_test.TestsContinuousness.test_simple ... ok
> tests.continuousness_helper_test.TestsContinuousness.test_simple_missing ... 
> ok
> tests.continuousness_helper_test.TestsContinuousness.test_simple_over ... ok
> tests.continuousness_helper_test.TestsContinuousness.test_simple_reset ... ok
> tests.continuousness_helper_test.TestsContinuousness.test_zeros_da1_dc1 ... ok
> tests.continuousness_helper_test.TestsContinuousness.test_zeros_non_da1_dc1 
> ... ok
> test_connect_with_timeout_failed (tests.dlt_client_unit_tests.TestDLTClient) 
> ... ok
> test_connect_with_timeout_success (tests.dlt_client_unit_tests.TestDLTClient) 
> ... ok
> test_init (tests.dlt_context_handler_unit_tests.TestDLTContextHandler) ... ok
> test_register_no_filter 
> (tests.dlt_context_handler_unit_tests.TestDLTContextHandler) ... ok
> test_register_similar_filters 
> (tests.dlt_context_handler_unit_tests.TestDLTContextHandler) ... ok
> test_register_single_filter 
> (tests.dlt_context_handler_unit_tests.TestDLTContextHandler) ... ok
> test_run_multiple_context_queue 
> (tests.dlt_context_handler_unit_tests.TestDLTContextHandler) ... ok
> test_run_no_messages 
> (tests.dlt_context_handler_unit_tests.TestDLTContextHandler) ... ok
> test_run_single_context_queue 
> (tests.dlt_context_handler_unit_tests.TestDLTContextHandler) ... ok
> test_run_unregister_with_unread_messages 
> (tests.dlt_context_handler_unit_tests.TestDLTContextHandler) ... ok
> test_unregister (tests.dlt_context_handler_unit_tests.TestDLTContextHandler) 
> ... ok
> test_sizeof (tests.dlt_core_unit_tests.TestCoreStructures) ... ok
> test_get_api_specific_file 
> (tests.dlt_core_unit_tests.TestImportSpecificVersion) ... ok
> test_get_api_specific_file_not_found 
> (tests.dlt_core_unit_tests.TestImportSpecificVersion) ... ok
> test_get_api_specific_file_truncate_minor_version 
> (tests.dlt_core_unit_tests.TestImportSpecificVersion) ... ok
> test_get_version (tests.dlt_core_unit_tests.TestImportSpecificVersion) ... ok
> tests.dlt_filter_unit_tests.TestDLTFilter.test_add0 ... ok
> tests.dlt_filter_unit_tests.TestDLTFilter.test_add1 ... ok
> tests.dlt_filter_unit_tes

Processed: bug 1019612 is forwarded to https://github.com/dmendel/bindata/issues/144

[Debian Bug Tracking System]

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

> forwarded 1019612 https://github.com/dmendel/bindata/issues/144
Bug #1019612 [src:ruby-bindata] ruby-bindata: FTBFS with ruby3.1: ERROR: Test 
"ruby3.1" failed.
Set Bug forwarded-to-address to 'https://github.com/dmendel/bindata/issues/144'.
> thanks
Stopping processing here.

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

Processed: Re: prometheus-openstack-exporter: FTBFS dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +pending
Bug #1021925 [src:prometheus-openstack-exporter] prometheus-openstack-exporter: 
FTBFS dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
exit code 13
Ignoring request to alter tags of bug #1021925 to the same tags previously set

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

Bug#1021925: prometheus-openstack-exporter: FTBFS dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned exit code 13

[Tobias Frost]

Source: prometheus-openstack-exporter
Followup-For: Bug #1021925
Control: tags -1 +pending

Dear maintainer,

I've uploaded Raúl's NMU to DELAYED/2.
Let me know if I should delay it any longer.

-- 
tobi


signature.asc
Description: PGP signature

Bug#1022957: nex: /usr/bin/nex is already provided by the nvi package

[Andreas Beckmann]

Package: nex
Version: 0.0.0+git.2021.03.30.1a3320dab9-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package nex.
  Preparing to unpack .../nex_0.0.0+git.2021.03.30.1a3320dab9-1_amd64.deb ...
  Unpacking nex (0.0.0+git.2021.03.30.1a3320dab9-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/nex_0.0.0+git.2021.03.30.1a3320dab9-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/nex', which is also in package nvi 1.81.6-17+b2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/nex_0.0.0+git.2021.03.30.1a3320dab9-1_amd64.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/bin/nex


Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html

Bug#949355: Removing simpleitk from Debian (Was: simpleitk FTBFS: test failures)

[Andreas Tille]

Hi Ghislain,

I tried to upgrade simpleitk to latest upstream in Git but failed.  IMHO
only the latest upstream which is supposed to be compatible to ITK5
makes sense to support inside Debian.  You are listed as Maintainer of
the package.  Do you think you are able to work on this package?
Otherwise I'd like to ask for removal from Debian.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#1022025: fixed in linux 5.10.149-2

[Jorge Barreiro]

Just wanted to report that version 5.10.149-2 fixed the issue for me. Using
"AMD Ryzen 5 PRO 4650G with Radeon Graphics" with its integraded graphics.

Bug#1020593: marked as done (mmdebstrap: debootstrap installing empty lsb-base package prevents autopkgtest from passing)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 14:31:30 +0200
with message-id <166696029071.179823.17637090374395556686@localhost>
and subject line Re: mmdebstrap: debootstrap installing empty lsb-base package 
prevents autopkgtest from passing
has caused the Debian Bug report #1020593,
regarding mmdebstrap: debootstrap installing empty lsb-base package prevents 
autopkgtest from passing
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.)


-- 
1020593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mmdebstrap
Version: 1.2.1-2
Severity: serious
X-Debbugs-Cc: jo...@debian.org

The functionality of lsb-base is in the Essential:yes set since
Bullseye. The package itself is now an empty transitional package
(because debootstrap doesn't understand the Provides relationship) which
depends on the new provider of the functionality, sysvinit-utils, which
is also in the Essential:yes set.

The problem is, that this empty package is only installed by debootstrap
because its resolver is not clever enough to realize that its
installation can be avoided. The resolver used by mmdebstrap (apt) does
not draw in the useless empty lsb-base package, thus resulting in a
difference between the chroots created by debootstrap and mmdebstrap
that makes the mmdebstrap test suite not succeed:

https://ci.debian.net/data/autopkgtest/unstable/amd64/m/mmdebstrap/26125615/log.gz

[...]
I: Retrieving logrotate 3.20.1-1
I: Validating logrotate 3.20.1-1
I: Retrieving lsb-base 11.4
W: Couldn't download package lsb-base (ver 11.4 arch all) at 
http://127.0.0.1/debian/pool/main/l/lsb/lsb-base_11.4_all.deb
I: Retrieving dmsetup 2:1.02.185-1
I: Validating dmsetup 2:1.02.185-1
[...]
I: Retrieving zlib1g 1:1.2.11.dfsg-4.1
I: Validating zlib1g 1:1.2.11.dfsg-4.1
E: Couldn't download packages: lsb-base

Instead of adding a hack to mmdebstrap, lets correct all packages in the
Priority:important set that still carry a useless dependency on
lsb-base:

https://salsa.debian.org/debian/cron/-/merge_requests/7
https://salsa.debian.org/debian/ifupdown/-/merge_requests/12
https://salsa.debian.org/md/kmod/-/merge_requests/9
https://salsa.debian.org/debian/procps/-/merge_requests/6

There is also a proposed lintian message deprecating the use of lsb-base
in dependencies:

https://salsa.debian.org/lintian/lintian/-/merge_requests/419

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
On Fri, 23 Sep 2022 23:22:58 +0200 Johannes Schauer Marin Rodrigues 
 wrote:
> Instead of adding a hack to mmdebstrap, lets correct all packages in the
> Priority:important set that still carry a useless dependency on
> lsb-base:
> 
> https://salsa.debian.org/debian/cron/-/merge_requests/7
> https://salsa.debian.org/debian/ifupdown/-/merge_requests/12
> https://salsa.debian.org/md/kmod/-/merge_requests/9
> https://salsa.debian.org/debian/procps/-/merge_requests/6

All done. Thus, closing.

signature.asc
Description: signature
--- End Message ---

Bug#1013157: Asking for removal from Debian (Was: nifti2dicom: vtk[6,7] removal)

[Andreas Tille]

Hi,

I've added to the upstream issue[1] that I will ask ftpmaster for
removal from Debian if there is no visible sign that there is any
interest to port the code to recent VTK.

Just to let readers of Debian Med know that this package is about
to be removed.

Kind regards

 Andreas.

[1] https://github.com/biolab-unige/nifti2dicom/issues/36

-- 
http://fam-tille.de

Bug#1022169: marked as done (llvm-toolchain-15: FTBFS on mips*el: static assertion failed: struct_kernel_stat_sz == sizeof(stat))

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 12:03:42 +
with message-id 
and subject line Bug#1022169: fixed in llvm-toolchain-15 1:15.0.3-2
has caused the Debian Bug report #1022169,
regarding llvm-toolchain-15: FTBFS on mips*el: static assertion failed: 
struct_kernel_stat_sz == sizeof(stat)
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.)


-- 
1022169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-15
Version: 1:15.0.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source, making mesa unbuildable
User: debian-m...@lists.debian.org
Usertags: mipsel mips64el
X-Debbugs-Cc: debian-m...@lists.debian.org, m...@packages.debian.org
Control: affects -1 + src:mesa

Quoting from mips64el buildd logs, but mipsel has a similar failure:

> /<>/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_linux.cpp:67:1:
>  error: static assertion failed due to requirement 'struct_kernel_stat_sz == 
> sizeof(stat)':
> COMPILER_CHECK(struct_kernel_stat_sz == sizeof(struct stat));

Strictly speaking this is not a regression because llvm-toolchain-15 was
never built successfully on mips*el, but I think it should be treated as
RC anyway, because older llvm-toolchain-* were buildable on mips*el (and
mesa is already using llvm-toolchain-15, making it a key package).

smcv

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 
'oldstable-debug'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-15
Source-Version: 1:15.0.3-2
Done: Sylvestre Ledru 

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-15, 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 1022...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-15 
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: Fri, 28 Oct 2022 10:25:45 +0200
Source: llvm-toolchain-15
Architecture: source
Version: 1:15.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 1022169
Changes:
 llvm-toolchain-15 (1:15.0.3-2) unstable; urgency=medium
 .
   * Cherry-pick upstream fix to unbreak mips (closes: #1022169)
 Thanks to YunQiang Su for the patch
 https://reviews.llvm.org/D135553
Checksums-Sha1:
 d69ac8a6a45fa5a2e2398f991598534e3980116b 7321 llvm-toolchain-15_15.0.3-2.dsc
 58a0a47ac265407203e919010da9c0a6bf613853 159980 
llvm-toolchain-15_15.0.3-2.debian.tar.xz
 040e36bf4138c75e24eb42e4c5b37059d5094a13 31853 
llvm-toolchain-15_15.0.3-2_amd64.buildinfo
Checksums-Sha256:
 c12a883ebd6f308a25c9be763954c53782c7ba9dcabfc11bd0f7756c25494d41 7321 
llvm-toolchain-15_15.0.3-2.dsc
 bbaab936b302b51a0da74c8dd4d4e5728bc1b311bdb2dd2da471128100215861 159980 
llvm-toolchain-15_15.0.3-2.debian.tar.xz
 5e0134f31929237b2ae241c62230327018d36fa865664ac92a383e8982843032 31853 
llvm-toolchain-15_15.0.3-2_amd64.buildinfo
Files:
 0ee14fe700fc2c9f3161c2716ba77551 7321 devel optional 
llvm-toolchain-15_15.0.3-2.dsc
 d1b2b7d0f8bda617e733483c55ec23b7 159980 devel optional 
llvm-toolchain-15_15.0.3-2.debian.tar.xz
 a2377fad479347452b2f475c1eb61efd 31853 devel optional 
llvm-toolchain-15_15.0.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmNbuwMACgkQfmUo2nUv
G+EX9Q/+IOyjJJn+EkyS6Za89q56V0VGj3TrNZ8oLccR0MUZdUjg1+fRIuXRKS4I
5R36ozl99qVMwPS6kAHtI8tSyKYlN9qivy6mYGLVDp3Xsvij+GzvDcPrFDlk9wvc
znNILL1M/GNz1zX0XUGdNMzvncS13Y0YzT

Bug#1022304: marked as done (lsp-mode: FTBFS: lsp-completion.el:166:8: Error: docstring wider than 80 characters)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 11:19:36 +
with message-id 
and subject line Bug#1022304: fixed in lsp-mode 8.0.0-5
has caused the Debian Bug report #1022304,
regarding lsp-mode: FTBFS: lsp-completion.el:166:8: Error:  docstring wider 
than 80 characters
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.)


-- 
1022304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lsp-mode
Version: 8.0.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> /bin/true
> make[1]: Leaving directory '/<>'
>dh_elpa_test
>   emacs -batch -Q -l package --eval "(setq native-comp-eln-load-path 
> '(\"/tmp/r3t8gwuiGB\"))" --eval "(add-to-list 'package-directory-list 
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f 
> package-initialize -L clients/ -L . -L test -l test/lsp-javascript-test.el -l 
> test/lsp-mode-test.el -l test/lsp-io-test.el -l test/lsp-methods-test.el -l 
> test/lsp-file-watch-test.el -l test/lsp-clangd-test.el -l 
> test/lsp-completion-test.el -l test/lsp-common-test.el -l 
> test/lsp-protocol-test.el -l test/lsp-integration-test.el -l 
> debian/ert-helper.el
> Loading /<>/test/test-helper.el (source)...
> Running 62 tests (2022-10-23 07:36:14+, selector ‘(not (or (tag org) (tag 
> no-win)))’)
>passed   1/62  lsp--boolean-property (0.000225 sec)
>passed   2/62  lsp--build-workspace-configuration-response-test (0.000191 
> sec)
>passed   3/62  lsp--custom-settings-test (0.000164 sec)
>passed   4/62  lsp--f-ancestor-of\? (0.000281 sec)
>passed   5/62  lsp--find-session-folder (0.000548 sec)
>passed   6/62  lsp--get-symbol-to-rename (0.000176 sec)
>passed   7/62  lsp--merge-results (0.000402 sec)
>passed   8/62  lsp--non-boolean-property (0.000159 sec)
>passed   9/62  lsp--non-related-content-on-stdout (0.652790 sec)
>passed  10/62  lsp--parser-read--ignored-messages (0.002724 sec)
>passed  11/62  lsp--parser-read--multibyte (0.042170 sec)
>passed  12/62  lsp--parser-read--multibyte-nospace (0.000827 sec)
>passed  13/62  lsp--parser-read--multibyte-received (0.000140 sec)
>passed  14/62  lsp--parser-read--multiple-chunks (0.000151 sec)
>passed  15/62  lsp--parser-read--multiple-messages (0.000180 sec)
>passed  16/62  lsp--parser-read--multiple-multibyte-chunks (0.000251 sec)
>passed  17/62  lsp--path-to-uri (0.000127 sec)
>passed  18/62  lsp--read-rename (0.270667 sec)
>passed  19/62  lsp--test-find-roots-for-workspace (0.000147 sec)
> LSP :: Applying 12 edits to ` *temp*-360212' ...
> Applying 12 edits to ` *temp*-360212' ... 
> Applying 12 edits to ` *temp*-360212' ...done
>passed  20/62  lsp--test-overlapping-updates (0.000830 sec)
>passed  21/62  lsp--uri-to-path--handle-utf8 (0.000148 sec)
> Testing file /<>/lsp-completion.el
> 
> In toplevel form:
> lsp-completion.el:166:8: Error:  docstring wider than 80 characters
> Test lsp-byte-compilation-test backtrace:
>   signal(ert-test-failed (((should (byte-compile-file (save-excursion 
> (find-library library) (buffer-file-name :form (byte-compile-file 
> "/<>/lsp-completi...") :value nil)))
>   ert-fail(((should (byte-compile-file (save-excursion (find-library library) 
> (buffer-file-name :form (byte-compile-file 
> "/<>/lsp-completi...") :value nil))
>   (if (unwind-protect (setq value-1004 (apply fn-1002 args-1003)) (setq 
> form-description-1006 (nconc (list '(should (byte-compile-file ...))) (list 
> :form (cons fn-1002 args-1003)) (if (eql value-1004 
> 'ert-form-evaluation-aborted-1005) nil (list :value value-1004)) (if (eql 
> value-1004 'ert-form-evaluation-aborted-1005) nil (let ((-explainer- ...)) 
> (if -explainer- (progn ...)) (ert--signal-should-execution 
> form-description-1006)) nil (ert-fail form-description-1006))
>   (let (form-description-1006) (if (unwind-protect (setq value-1004 (apply 
> fn-1002 args-1003)) (setq form-description-1006 (nconc (list '(should ...)) 
> (list :form (cons fn-1002 args-1003)) (if (eql value-1004 
> 'ert-form-evaluation-aborted-1005) nil (list :value value-1004)) (if (eql 
> value-1004 'ert-form-evaluation-aborted-1005) nil (let (...) (if -explainer- 
> ...) (ert--signal-should-execution form-description-1006)) ni

Processed: Bug#1016070 marked as pending in sbuild

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1016070 [src:sbuild] sbuild: autopkgtest fails with "No space left on 
device"
Added tag(s) pending.

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

Bug#1016070: marked as pending in sbuild

[Johannes Schauer Marin Rodrigues]

Control: tag -1 pending

Hello,

Bug #1016070 in sbuild 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/debian/sbuild/-/commit/002bb6fef7eda2cab7c5cc3e0bfa8baf14c8d6b3


debian/tests/unshare-qemuwrapper: bump disk size to 4G

Sometimes gcc temporarily includes debug symbols to track down ICEs from
build logs. This blows up the packages by several hundred megabytes
until debug symbols are removed again. Usually this happens when new gcc
versions are uploaded and gets reverted before a stable release.

Closes: #1016070


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1016070

Bug#1019765: wxsvg: Please transition to wxwidgets3.2

[Alec Leamas]

On Wed, 14 Sep 2022 15:42:16 -0400 s...@techie.net wrote:

Source: wxsvg
Severity: normal
Control: block 1019416 by -1

Hi,

Please transition wxsvg from wxwidgets3.0 to wxwidgets3.2.


wxsvg is basically a dependency of opencpn, I'm not aware of any other 
package depending on it. As such, the transition to using wxWidgets 3.2 
is handled in the opencpn context as discussed in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=101976; can we keep 
the discussion in that bug?


--alec

Bug#1020819: marked as done (subtitlecomposer: Cannot load any video: "Option refcounted_frames not found" error (removed from FFmpeg))

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 10:06:31 +
with message-id 
and subject line Bug#1020819: fixed in subtitlecomposer 0.7.1-4
has caused the Debian Bug report #1020819,
regarding subtitlecomposer: Cannot load any video: "Option refcounted_frames 
not found" error (removed from FFmpeg)
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.)


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

Package: subtitlecomposer
Version: 0.7.1-3
Severity: grave
Tags: fixed-upstream patch
Justification: renders package unusable
Forwarded: https://invent.kde.org/multimedia/subtitlecomposer/-/issues/68
Dear Maintainer,

I cannot load any video into Subtitle Composer. After I select a video 
from the "Open Video..." option, the video does not appear, and standard 
error shows this message:


Option refcounted_frames not found.
Last message repeated 1 times
Failed to open file '[path to video file]'

This has been fixed upstream in the following Git commit:
https://invent.kde.org/multimedia/subtitlecomposer/-/commit/d8f9797d9c0d45fa9f4402f79c539544b74d2cc7

There is no new upstream release with the fix yet, but the patch should 
be fairly simple to apply.


Thank you,
Philip Chung

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; 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

Versions of packages subtitlecomposer depends on:
ii  kio   5.98.0-1
ii  libavcodec59  7:5.1.1-2+b1
ii  libavformat59 7:5.1.1-2+b1
ii  libavutil57   7:5.1.1-2+b1
ii  libc6 2.34-8
ii  libicu71  71.1-3
ii  libkf5codecs5 5.98.0-1
ii  libkf5completion5 5.98.0-1
ii  libkf5configcore5 5.98.0-1
ii  libkf5configgui5  5.98.0-1
ii  libkf5configwidgets5  5.98.0-1
ii  libkf5coreaddons5 5.98.0-1
ii  libkf5i18n5   5.98.0-1
ii  libkf5kiocore55.98.0-1
ii  libkf5kiogui5 5.98.0-1
ii  libkf5kiowidgets5 5.98.0-1
ii  libkf5krosscore5  5.98.0-1
ii  libkf5sonnetcore5 5.98.0-1
ii  libkf5sonnetui5   5.98.0-1
ii  libkf5textwidgets55.98.0-1
ii  libkf5widgetsaddons5  5.98.0-1
ii  libkf5xmlgui5 5.98.0-1
ii  libopenal11:1.19.1-2
ii  libpocketsphinx3  0.8+5prealpha+1-14
ii  libqt5core5a [qtbase-abi-5-15-4]  5.15.4+dfsg-5
ii  libqt5gui55.15.4+dfsg-5
ii  libqt5widgets55.15.4+dfsg-5
ii  libsphinxbase30.8+5prealpha+1-13+b2
ii  libstdc++612.2.0-3
ii  libswresample47:5.1.1-2+b1

subtitlecomposer recommends no packages.

subtitlecomposer suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: subtitlecomposer
Source-Version: 0.7.1-4
Done: Pino Toscano 

We believe that the bug you reported is fixed in the latest version of
subtitlecomposer, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated subtitlecomposer 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, 28 Oct 2022 11:41:15 +0200
Source: subtitlecomposer
Architecture: source
Version: 0.7.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Pino Toscano 
Closes: 1020819
Changes:
 subtitlecomposer (0.7.1-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Diederik de Haas ]
   * Backport upstream commit d8f9797d9c0d45fa9f4402f79c539544b74d2cc7 to
 remove dep

Processed: tagging 1020056

[Debian Bug Tracking System]

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

> tags 1020056 + pending
Bug #1020056 [src:tango] tango: FTBFS: configure: error: Couldn't find a 
compatible zmq.hpp
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: found 1019782 in 1.0.1-3

[Debian Bug Tracking System]

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

> # Tell BTS that this RC bug doesn't affect stable
> found 1019782 1.0.1-3
Bug #1019782 {Done: Ole Streicher } [src:gnudatalanguage] 
gnudatalanguage: Please transition to wxwidgets3.2
Marked as found in versions gnudatalanguage/1.0.1-3.
> thanks
Stopping processing here.

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

Bug#1020895: marked as done (whatmaps: postinst fails in clean chroot/container)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 08:41:47 +
with message-id 
and subject line Bug#1020895: fixed in whatmaps 0.0.12-4
has caused the Debian Bug report #1020895,
regarding whatmaps: postinst fails in clean chroot/container
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.)


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

Package: whatmaps
Version: 0.0.12-3
Severity: serious

Dear whatmaps maintainer,

whatmaps' postinst maintscript fails when run in a newly created 
unstable system, as used by autopkgtest.


Setting up whatmaps (0.0.12-3) ...
sed: can't read /etc/apt/apt.conf.d/20services: No such file
or directory
dpkg: error processing package whatmaps (--configure):
 installed whatmaps package post-installation script
 subprocess returned error exit status 2

A full log can be found at .

As of 2022-09-28, this can be reproduced using autopkgtest and lxc:

$ sudo autopkgtest-build-lxc debian sid
$ autopkgtest . -- lxc --sudo autopkgtest-sid

Regards,

--
Gioele Barabucci
--- End Message ---
--- Begin Message ---
Source: whatmaps
Source-Version: 0.0.12-4
Done: Guido Günther 

We believe that the bug you reported is fixed in the latest version of
whatmaps, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated whatmaps 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: Fri, 28 Oct 2022 09:59:38 +0200
Source: whatmaps
Architecture: source
Version: 0.0.12-4
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Guido Günther 
Closes: 1020895
Changes:
 whatmaps (0.0.12-4) unstable; urgency=medium
 .
   * [3030430] d/postinst: Don't fail in container without apt
 (Closes: #1020895)
   * [dbd0843] Bump debhelper compat to 13
   * [b2b1e7b] d/control: Drop X-Python3-Version
   * [de2a09d] Bump standards version to 4.6.1.
 No changes needed
   * [b0f56a6] Drop unused pyversions.
 Thanks linitian
   * [75a2d0b] d/rules: Use dh_execute_after.
 This ensures that DEB_BUILD_OPTIONS=nocheck gets honored automatically
   * [6b68c87] d/control: Switch priority to optional.
 It's prefereed over `extra`
Checksums-Sha1:
 a8eb0c2f9ebfda9ec541278af6282c2d9ddcba10 1885 whatmaps_0.0.12-4.dsc
 5fa915bb5103d4085e4f926dfef1743926721172 11520 whatmaps_0.0.12-4.debian.tar.xz
 fa962a60726f2cc82d152eed138f7e8278af7e66 6891 whatmaps_0.0.12-4_amd64.buildinfo
Checksums-Sha256:
 2915e0b744e4e5f51f9e4d329218d36c1481b7a3c63b4b9e8e374799a07a588d 1885 
whatmaps_0.0.12-4.dsc
 92125a66640425a64af1ed140f8b48e8887bf9496ca29e0e63a46208d5731eb3 11520 
whatmaps_0.0.12-4.debian.tar.xz
 237201e38523becc74972243ba0a02c5147b4c4cab4b55f66b42e8f8ccc9cd44 6891 
whatmaps_0.0.12-4_amd64.buildinfo
Files:
 d313918929ac24fffa66c0a9205ba0d4 1885 admin optional whatmaps_0.0.12-4.dsc
 cd00096677981e92ac5d30a35aa06680 11520 admin optional 
whatmaps_0.0.12-4.debian.tar.xz
 a0d9c93f81c74d09579355cd918b0d3f 6891 admin optional 
whatmaps_0.0.12-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEY/bM35YinQkoayrDJb+GUkr8weMFAmNbjdQACgkQJb+GUkr8
wePcOQ/8DESd49WzFxMk0RStBFXjVmYQFDhlvvABRC7E/1oVOaZMrhtmp4xG55G5
PpG0WgIwTL1jC4tHvPM0Pvhy66lIOvCplfVhrX5zgr260iHuJT92z95hGQI6Eenz
+E+7tauVfloa0L6xxUPsv6vZkGTfOMP2dNXiMtLWyXkL8GRSzoS4v6QTgMvzB+0J
xYaVzvfxQgMfn9sFK+QuV6du4S2MihM57s6twPEuBNjy9mapnSc10X0Oa5Q6ple0
k1lbVFD5GW1DZ0QVx6xmtAUJaG0/wl2t6wOG68DZs4SB9jZkner/S0S4ao/LQd1S
+ETz2YRG85Tphw/w5hr1MnYJYNA1nuNBmJz55d5GSehgsigE9Lk/Th1bbxTvLr7/
uOl6g/axTWVd74rQ9lzG97K3KFObLNUmsl3y1tWIxEzJhH69JzHnuL3wL5lW/6yK
sXTuAhxLITQYzRvAPO9a2uZxCq6glcnIzxcEYVbigGGwu3VmCXpDvhHBoA3AYZV7
SEJCbGOMbrF13ySwIAHye6XJPcfcnw93FVWfI0RPkdkfqFfZ14cVcnlh/Su0UK4S
u8p+qyPWgZnsZ+uGmytpuoRui78319ZCKYxmdxC63TZ+V2VVMgFNQORphfrxFNE1
Zru9eDPswktTzQu8YbsjUJ5VmYEb/JbnWHBaZgrGTkuTxkFdpS4=
=pX38
-END PGP SIGNATURE End Message ---

Processed: affects 1022233

[Debian Bug Tracking System]

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

> affects 1022233 src:rust-isahc
Bug #1022233 [librust-tracing-subscriber-dev] librust-tracing-subscriber-dev: 
impossible to install
Added indication that 1022233 affects src:rust-isahc
> thanks
Stopping processing here.

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

Bug#1022297: marked as done (neomutt: FTBFS: ./obj-x86_64-linux-gnu/conftest__.c:3: undefined reference to `qsort_s')

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 09:18:42 +0200
with message-id 
and subject line Re: Bug#1022297: neomutt: FTBFS: 
./obj-x86_64-linux-gnu/conftest__.c:3: undefined reference to `qsort_s'
has caused the Debian Bug report #1022297,
regarding neomutt: FTBFS: ./obj-x86_64-linux-gnu/conftest__.c:3: undefined 
reference to `qsort_s'
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.)


-- 
1022297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: neomutt
Version: 20220429+dfsg1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: /tmp/ccw8HBtr.o: in function `main':
> ./obj-x86_64-linux-gnu/conftest__.c:3: undefined reference to `qsort_s'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/neomutt_20220429+dfsg1-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221023&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 marking 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 ---

fixed 1022297 20220429+dfsg1-2
thanks

On Sun, Oct 23, 2022 at 02:37:30PM +0200, Lucas Nussbaum wrote:
[...]
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 

This was fixed by 20220429+dfsg1-2, the problem was that libgpg-error-config
dependency was not detected appropriately starting from libgpg-error-dev 1.46.--- End Message ---

Processed: Re: Bug#1022297: neomutt: FTBFS: ./obj-x86_64-linux-gnu/conftest__.c:3: undefined reference to `qsort_s'

[Debian Bug Tracking System]

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

> fixed 1022297 20220429+dfsg1-2
Bug #1022297 [src:neomutt] neomutt: FTBFS: 
./obj-x86_64-linux-gnu/conftest__.c:3: undefined reference to `qsort_s'
Marked as fixed in versions neomutt/20220429+dfsg1-2.
> thanks
Stopping processing here.

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

Bug#1022848: marked as done (6.0.5 fixes critical btrfs bug in 6.0.3, affecting space cache v1 filesystems)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 07:11:50 +
with message-id 
and subject line Bug#1022848: fixed in linux 6.0.5-1
has caused the Debian Bug report #1022848,
regarding 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space cache v1 
filesystems
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.)


-- 
1022848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 5.19.6-1
Severity: critical
Justification: breaks the whole system


Hi.

6.0.3 introduced a commit that causes (permanent) CPU soft lockups
for some people with btrfs filesystems, effectively breaking the
system, e.g. when booting.

See e.g.
https://lore.kernel.org/linux-btrfs/2291416ef48d98059f9fdc5d865b0ff040148237.ca...@scientia.org/T/#u
https://lore.kernel.org/linux-btrfs/1c531dd5de7477c8b6ec15d4aebb8e42ae460925.ca...@scientia.org/T/#t
https://lore.kernel.org/linux-btrfs/Y1krzbq3zdYOSQYG@bulldog/T/#u
https://lore.kernel.org/all/10522366-5c17-c18f-523c-b97c14969...@net4u.de/
https://bugs.archlinux.org/task/76266



6.0.5 is ought to fix that, could you please upgrade sid ASAP? :-)

See:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.0.5&id=217fd7557896d990c3dd8beea83a6feeb504f235


Thanks,
Chris.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.0.5-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, 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 1022...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux 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, 28 Oct 2022 08:53:43 +0200
Source: linux
Architecture: source
Version: 6.0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1022544 1022848
Changes:
 linux (6.0.5-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.0.4
 - [x86] drm/i915/bios: Validate fp_timing terminator presence
 - [x86] drm/i915/bios: Use hardcoded fp_timing size for generating LFP data
   pointers
 - pinctrl: amd: change dev_warn to dev_dbg for additional feature support
 - [x86] thermal: intel_powerclamp: Use first online CPU as control_cpu
 - io_uring/net: fail zc send when unsupported by socket
 - HID: playstation: stop DualSense output work on remove.
 - HID: playstation: add initial DualSense Edge controller support
 - net: flag sockets supporting msghdr originated zerocopy
 - drm/amd/pm: fulfill SMU13.0.7 cstate control interface
 - drm/amd/pm: add SMU IP v13.0.4 IF version define to V7
 - drm/amd/pm: disable cstate feature for gpu reset scenario
 - drm/amd/pm: fulfill SMU13.0.0 cstate control interface
 - drm/amd/pm: update SMU IP v13.0.4 driver interface version
 - dm clone: Fix typo in block_device format specifier
 - efi: efivars: Fix variable writes without query_variable_store()
 - efi: ssdt: Don't free memory if ACPI table was loaded successfully
 - gcov: support GCC 12.1 and newer compilers
 - io-wq: Fix memory leak in worker creation
 - fbdev/core: Remove remove_conflicting_pci_framebuffers()
 - Revert "ALSA: hda: Fix page fault in snd_hda_codec_shutdown()"
   (Closes: #1022544)
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.0.5
 - [arm64,armhf] clk: tegra: Fix Tegra PWM parent clock
 - Revert "btrfs: call __btrfs_remove_free_space_cache_locked on cache load
   failure" (Closes: #1022848)
 .
   [ Salvatore Bonaccorso ]
   * [rt] Update to 6.0.5-rt14
   * Ignore ABI changes doe to removed check_var_size, 
check_var_size_nonblocking
 and remove_conflicting_pci_framebuffers
Checksums-Sha1:
 0a66fb0c24cee959b7509864d0f60cdf8d7cdf7d 249241 linux_6.0.5-1.dsc
 1d0b2c8761c915bd6be5ec6308d44508dfa2a806 136367304 linux_6.0.5.orig.tar.xz
 05f610bc22f3babf6e908716eff8223d031f9d82 4117412 linux_6.0.5-1.debian.tar.xz
 c00e