Bug#1040771: openjdk-22 should not be in stable releases

[Matthias Klose]

Control: severity -1 important

not being available for stable releases doesn't mean it can't be available in 
testing.

Processed: Re: openjdk-22 should not be in stable releases

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1040771 [src:openjdk-22] openjdk-22 should not be in stable releases
Severity set to 'important' from 'serious'

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

Bug#1040686: marked as done (libpdfbox-java: Missing build dependency on lcdf-typetool OR extraneous other relation in debian/)

[Debian Bug Tracking System]

Your message dated Tue, 11 Jul 2023 05:22:52 +
with message-id 
and subject line Bug#1040686: fixed in libpdfbox-java 1:1.8.16-3
has caused the Debian Bug report #1040686,
regarding libpdfbox-java: Missing build dependency on lcdf-typetool OR 
extraneous other relation in debian/
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.)


-- 
1040686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpdfbox-java
Version: 1:1.8.16-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: kerd...@gmail.com

Dear Maintainer,

This package fails to build when lcdf-typetool is not installed, but
only during packaging. It appears not to be used during the build.
Maybe it's supposed to be a build dependency. If it isn't supposed to
be a build dependency, then the build should succeed without its presence.

Salutations,
Ted

-- System Information:
Debian Release: 12.0
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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
--- End Message ---
--- Begin Message ---
Source: libpdfbox-java
Source-Version: 1:1.8.16-3
Done: tony mancill 

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated libpdfbox-java 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: Mon, 10 Jul 2023 21:45:30 -0700
Source: libpdfbox-java
Architecture: source
Version: 1:1.8.16-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 1040686
Changes:
 libpdfbox-java (1:1.8.16-3) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * Remove myself from Uploaders.
   * debian/control: move javahelper from Build-Depends-Indep
 to Build-Depends.
 It is used during clean via the javahelper debhelper addon.
   * debian/rules: use version of aglfn instead of lcdf-typetools.
 This change was missing in 40c228a. (Closes: #1040686)
   * debian/rules: rename override_dh_auto_{configure,build} to -indep.
 We are not building any architecture dependent packages.
 .
   [ tony mancill ]
   * Set Rules-Requires-Root: no in debian/control
   * Use debhelper-compat 13
   * Bump Standards-Version to 4.6.2
   * No longer build or distribute javadoc packages:
 libpdfbox-java-doc, libjempbox-java-doc, libfontbox-java-doc
   * Drop build-dep on libmaven-javadoc-plugin-java
   * Add missing Apache NOTICE file
Checksums-Sha1:
 fe027d97529a7799cc093b546563e19a590304e6 2415 libpdfbox-java_1.8.16-3.dsc
 392ca686f4cf0257e080ea42a34fb73475a6a9c1 11528 
libpdfbox-java_1.8.16-3.debian.tar.xz
 2ad06e76cbae4604ed9a23444a1a342da9919c7b 16894 
libpdfbox-java_1.8.16-3_amd64.buildinfo
Checksums-Sha256:
 9463fccf49650118ba714800ef26e2cdd720d101d2d3119d742ea0f0c4256396 2415 
libpdfbox-java_1.8.16-3.dsc
 8282a8905b99aa4fcaf18cfb91fa1f96f26c6704e1d7bcfb9031d1892b8e8e02 11528 
libpdfbox-java_1.8.16-3.debian.tar.xz
 c25cd950743b3b2dbe1ff46d1352fa364ca160f6575825ec901a8e4d4517bf1a 16894 
libpdfbox-java_1.8.16-3_amd64.buildinfo
Files:
 e3d195829946360bfb9251e09450e03a 2415 java optional libpdfbox-java_1.8.16-3.dsc
 3fc23e1f38fd7c589a62df235b2647fd 11528 java optional 
libpdfbox-java_1.8.16-3.debian.tar.xz
 fc019671203ee9e215325e02421e5789 16894 java optional 
libpdfbox-java_1.8.16-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmSs4agUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpaeeA/+PL7Ug5UdkWBNCPanOxpK10inDeSq
+GVNDo1s/dvWxpC+26BQle/5ArihArTWihxQDtqSEWSaBb0+dLr7HLhMoP5T56ci
EyPsdARtf45XsRa28dCP+3XvbMqIjHiJMDKroJjpdwuB+nzuUZ+SiJ4ygtfqiI/9
DySfvTcPPUxJdkyc621z0l7SKJM6D2RjChZTdZHkPA9A+G49R0ZG9uU4Iub+OOVb

Processed: block 1039030 with 1040800

[Debian Bug Tracking System]

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

> block 1039030 with 1040800
Bug #1039030 [release.debian.org] transition: qtbase-abi-5-15-10
1039030 was blocked by: 1038402 1038737
1039030 was not blocking any bugs.
Added blocking bug(s) of 1039030: 1040800
> thanks
Stopping processing here.

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

Processed: owner 1040686

[Debian Bug Tracking System]

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

> owner 1040686 !
Bug #1040686 [src:libpdfbox-java] libpdfbox-java: Missing build dependency on 
lcdf-typetool OR extraneous other relation in debian/
Owner recorded as tony mancill .
> thanks
Stopping processing here.

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

Processed: Re: mkchromecast: please change dependency from youtube-dl to yt-dlp

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1024216 [src:mkchromecast] mkchromecast: please change dependency from 
youtube-dl to yt-dlp
Severity set to 'serious' from 'normal'

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

Bug#1040815: golang-gitlab-gitlab-org-labkit build-depends unsatisfiable due to version restriction.

[Peter Green]

Package: golang-gitlab-gitlab-org-labkit
Version: 1.17.0-2
Tags: trixie, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable

golang-gitlab-gitlab-org-labkit build-depends on golang-google-grpc-dev:amd64 
(< 1.38~)
however the version of golang-google-grpc-dev in testing/unstable is now
1.38.0+really1.33.3-1

Bug#1040814: coq-quickchick build-depends on dropped transitional package.

[Peter Green]

Package: coq-quickchick
Version: 2.0-1
Tags: trixie, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable

coq-quickchick build-depends on dune, in bullseye this was a transitional 
package
built by the ocaml-dune source package and depending on the ocaml-dune
binary package. However in ocaml-dune 3.8.2-1 the transitional package
was dropped. It is still present in unstable as a cruft package but
is completely gone from testing.

Presumablly you need to update your build-dependency to build-depend on
dune instead of ocaml-dune.

Bug#1040813: ocaml-unix-errno build-depends on dropped transitional package.

[Peter Green]

Package: ocaml-unix-errno
Version: 0.6.1-2
Tags: trixie, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable

ocaml-pprint build-depends on dune, in bullseye this was a transitional package
built by the ocaml-dune source package and depending on the ocaml-dune
binary package. However in ocaml-dune 3.8.2-1 the transitional package
was dropped. It is still present in unstable as a cruft package but
is completely gone from testing.

Presumablly you need to update your build-dependency to build-depend on
dune instead of ocaml-dune.

Bug#1040812: ocaml-pprint build-depends on dropped transitional package.

[Peter Green]

Package: ocaml-pprint
Version: 20220103-1
Tags: trixie, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable

ocaml-pprint build-depends on dune, in bullseye this was a transitional package
built by the ocaml-dune source package and depending on the ocaml-dune
binary package. However in ocaml-dune 3.8.2-1 the transitional package
was dropped. It is still present in unstable as a cruft package but
is completely gone from testing.

Presumablly you need to update your build-dependency to build-depend on
dune instead of ocaml-dune.

Bug#1040811: ocaml-mm build-depends on dropped transitional package.

[Peter Green]

Package: ocaml-mm
Version: 0.8.1-1
Tags: trixie, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable

ocaml-mm build-depends on dune, in bullseye this was a transitional package
built by the ocaml-dune source package and depending on the ocaml-dune
binary package. However in ocaml-dune 3.8.2-1 the transitional package
was dropped. It is still present in unstable as a cruft package but
is completely gone from testing.

Presumablly you need to update your build-dependency to build-depend on
dune instead of ocaml-dune.

Bug#858337: apt-show-versions: wrong output when version of an installed package is missing from the Packages files

[Vincent Lefevre]

Hi Christoph,

On 2023-07-10 16:36:56 +0200, Christoph Martin wrote:
> Am 05.07.23 um 12:13 schrieb Vincent Lefevre:
> > Control: retitle -1 apt-show-versions gives unreliable information
> > Control: severity -1 grave
> 
> I still can not reproduce your problem.
> 
> Please try to find out, which value is missing in a Packages file, which
> triggers this error, so that I can reproduce the problem.

/var/lib/apt/lists/ftp.debian.org_debian_dists_unstable_main_binary-amd64_Packages
contains

Package: libreoffice-common
Source: libreoffice
Version: 4:7.5.4-4
Installed-Size: 57718
Maintainer: Debian LibreOffice Maintainers 
Architecture: all
[...]

So this appears to be correct.

Only the "Architecture: all" packages seem to be affected:

cventin:~> apt-show-versions -u | grep manually
fonts-opensymbol:all/experimental *manually* upgradeable from 
4:102.12+LibO7.5.4-4 to 4:102.12+LibO7.5.5~rc1-2
liblibreoffice-java:all/experimental *manually* upgradeable from 4:7.5.4-4 to 
4:7.5.5~rc1-2
libreoffice-common:all/experimental *manually* upgradeable from 4:7.5.4-4 to 
4:7.5.5~rc1-2
libreoffice-java-common:all/experimental *manually* upgradeable from 4:7.5.4-4 
to 4:7.5.5~rc1-2
libreoffice-nlpsolver:all/experimental *manually* upgradeable from 
4:0.9+LibO7.5.4-4 to 4:0.9+LibO7.5.5~rc1-2
libreoffice-report-builder:all/experimental *manually* upgradeable from 
4:7.5.4-4 to 4:7.5.5~rc1-2
libreoffice-script-provider-bsh:all/experimental *manually* upgradeable from 
4:7.5.4-4 to 4:7.5.5~rc1-2
libreoffice-script-provider-js:all/experimental *manually* upgradeable from 
4:7.5.4-4 to 4:7.5.5~rc1-2
libreoffice-script-provider-python:all/experimental *manually* upgradeable from 
4:7.5.4-4 to 4:7.5.5~rc1-2
libreoffice-style-colibre:all/experimental *manually* upgradeable from 
4:7.5.4-4 to 4:7.5.5~rc1-2
libreoffice-style-elementary:all/experimental *manually* upgradeable from 
4:7.5.4-4 to 4:7.5.5~rc1-2
libreoffice-wiki-publisher:all/experimental *manually* upgradeable from 
4:1.2.0+LibO7.5.4-4 to 4:1.2.0+LibO7.5.5~rc1-2
libunoloader-java:all/experimental *manually* upgradeable from 4:7.5.4-4 to 
4:7.5.5~rc1-2

FYI, the output for an "Architecture: all" package vs the output
of an arch-dependent package:

cventin:~> apt-show-versions -a libreoffice-common
libreoffice-common:all 4:7.5.4-4 install ok installed
libreoffice-common:all 4:7.4.5-3 stable   ftp.debian.org
No stable-updates version
libreoffice-common:all 4:7.4.5-3 testing  ftp.debian.org
libreoffice-common:all 4:7.4.5-3 unstable ftp.debian.org
libreoffice-common:all 4:7.5.5~rc1-2 experimental ftp.debian.org
libreoffice-common:all/experimental *manually* upgradeable from 4:7.5.4-4 to 
4:7.5.5~rc1-2

cventin:~> apt-show-versions -a libreoffice
libreoffice:amd64 4:7.5.4-4 install ok installed
libreoffice:amd64 4:7.4.5-3 stable   ftp.debian.org
No stable-updates version
libreoffice:amd64 4:7.4.5-3 testing  ftp.debian.org
libreoffice:amd64 4:7.5.4-4 unstable ftp.debian.org
libreoffice:amd64 4:7.5.5~rc1-2 experimental ftp.debian.org
libreoffice:amd64/unstable 4:7.5.4-4 uptodate
libreoffice:i386 4:7.4.5-3 stable   ftp.debian.org
No stable-updates version
libreoffice:i386 4:7.4.5-3 testing  ftp.debian.org
libreoffice:i386 4:7.4.5-3 unstable ftp.debian.org
libreoffice:i386 4:7.5.5~rc1-2 experimental ftp.debian.org
libreoffice:i386 not installed

Note that for the foreign architecture:

/var/lib/apt/lists/ftp.debian.org_debian_dists_unstable_main_binary-i386_Packages
contains

Package: libreoffice-common
Source: libreoffice
Version: 4:7.4.5-3
Installed-Size: 58639
Maintainer: Debian LibreOffice Maintainers 
Architecture: all
[...]

because of a build failure for 4:7.5.4-4 on i386:

https://buildd.debian.org/status/package.php?p=libreoffice

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1030385: marked as done (flite: FTBFS with TeXInfo 7.0.x)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jul 2023 22:48:54 +
with message-id 
and subject line Bug#1030385: fixed in flite 2.2-6
has caused the Debian Bug report #1030385,
regarding flite: FTBFS with TeXInfo 7.0.x
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.)


-- 
1030385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flite
Version: 2.2-5
Severity: important
Tags: ftbfs patch
Usertags: texinfo70

the package fails to build from source when using TeX Info 7.0.x. This
happens due to this change:

,
| 7.0 (7 November 2022)
| * texi2any
|  . HTML output:
|  . use manual_name_html as output directory for split HTML instead of
|manual_name or manual_name.html
`

The easiest solution is probably to add option "--output=flite" to
the "texi2any" call in doc/Makefile. A proposed patch is attached,
please make sure it does not break compatibility to TeXInfo 6.8.

For now TeXInfo 7.0 is available in experimental. This bug is not RC
for now, but after bookworm we'll upload TeXInfo 7.0 to unstable and
the bug will become RC.

Hilmar

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

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

-- 
sigmentation fault
--- flite-2.2.orig/doc/Makefile
+++ flite-2.2/doc/Makefile
@@ -50,7 +50,7 @@
 flite.html: flite.texi
@ if [ ! -d html ] ; \
   then mkdir -p html ; fi
-   (cd html; texi2any --set-customization-variable TEXI2HTML=1  
--split=chapter ../flite.texi)
+   (cd html; texi2any --set-customization-variable TEXI2HTML=1 
--output=flite --split=chapter ../flite.texi)
@ if [ -d html/flite ] ; \
  then mv html/flite/*.html html ; \
rmdir html/flite; fi


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: flite
Source-Version: 2.2-6
Done: Samuel Thibault 

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated flite 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: Mon, 10 Jul 2023 23:32:27 +0200
Source: flite
Architecture: source
Version: 2.2-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Closes: 1030385
Changes:
 flite (2.2-6) unstable; urgency=medium
 .
   [ Hilmar Preusse ]
   * patches/texinfo70: Fix build against TexInfo 7.0.x (Closes: Bug#1030385)
Checksums-Sha1:
 f32080c391bb5d3c0e112ea4f693b42cbded0be2 2130 flite_2.2-6.dsc
 3211198db443c743791af1eedd3303b65e5ccd9e 48772 flite_2.2-6.debian.tar.xz
 1ef8f0a8910ac3c819824b395350f32e9822100a 8789 flite_2.2-6_amd64.buildinfo
Checksums-Sha256:
 ba8db07046e16fc510e7df268d416685f55514fee4fbb14ebb5b4e611f0eca0a 2130 
flite_2.2-6.dsc
 44f77d55f26192ce82f097af2daa41712797aa1cded20cc2c9a10e5a5de779a4 48772 
flite_2.2-6.debian.tar.xz
 a97ac6045452afc870c242805ee43a5b1d8c1d0f0838290efcbc8db5e5066a31 8789 
flite_2.2-6_amd64.buildinfo
Files:
 cc015d94972bb92cee9368e50942f404 2130 sound optional flite_2.2-6.dsc
 94e3e80d37e4e4fcc259459a545a5ab2 48772 sound optional flite_2.2-6.debian.tar.xz
 df75f4f6279022a484015453c2ca7ee3 8789 sound optional 
flite_2.2-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi6MnFvk67auaclLJ5pG0tXV4H2IFAmSsiWoACgkQ5pG0tXV4
H2JG+g/+KQHOqg6OewK9XDPUGlBeufdGraH4xjQiQyDFG2r5W0uyjEZU7gnYBgXE
ousb0ezfEYBsh3rEWVXkHEZizRhKkz7eOLBLfrII7DmfcSP5L+JW+GcngIpuuEwZ
BjgB/tD9+Jqt0NIooywCyf46fV5ZkKKwQF2KlDChwNFsuKFAf7LN9uxX9l1a7fBC
Ud2AZ4gG5s08YRvpyE0Ta0FeU7baf9AkG2yeXlzsKyrmnBY+Hx2avJFGEp+WVg9z
nQVTCJ3pHkS15iF/QbDC73Q4+pg9Uoeg3j1kSez6is08JuXe6YQvXESKybOu+d6S

Bug#1040793: marked as done (udisks2 crashes when libblockdev plugins are missing)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jul 2023 21:51:18 +
with message-id 
and subject line Bug#1040793: fixed in udisks2 2.10.0-3
has caused the Debian Bug report #1040793,
regarding udisks2 crashes when libblockdev plugins are missing
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.)


-- 
1040793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udisks2
Version: 2.10.0-2
Severity: normal

Dear Maintainer,

In a daily upgrade basis of a sid system with some extra rc-buggy packages
(GNOME 44 relatives mainly),
the recent upload of udisks2 introduced the following issue:

  PID: 4640 (udisksd)
   UID: 0 (root)
   GID: 0 (root)
Signal: 5 (TRAP)
 Timestamp: Mon 2023-07-10 19:27:28 CEST (2min 12s ago)
  Command Line: /usr/libexec/udisks2/udisksd
Executable: /usr/libexec/udisks2/udisksd
 Control Group: /system.slice/udisks2.service
  Unit: udisks2.service
 Slice: system.slice
   Boot ID: a278c0ac4f4542c1aac6ab19b860f94a
Machine ID: be351e757dc049ffa300ddbaf0f4856a
  Hostname: X
   Storage:
/var/lib/systemd/coredump/core.udisksd.0.a278c0ac4f4542c1aac6ab19b860f94a.4640.168901004800.zst
(present)
  Size on Disk: 340.8K
   Message: Process 4640 (udisksd) of user 0 dumped core.

Module libudev.so.1 from deb systemd-253.5-1.amd64
Module libsystemd.so.0 from deb systemd-253.5-1.amd64
Stack trace of thread 4640:
#0  0x7faa5ad3c1e7 g_log_writer_default (libglib-2.0.so.0 +
0x641e7)
#1  0x7faa5ad39b61 g_log_structured_array (libglib-2.0.so.0
+ 0x61b61)
#2  0x7faa5ad39ecb g_log_structured (libglib-2.0.so.0 +
0x61ecb)
#3  0x556c3f1aed34 udisks_log (udisksd + 0x53d34)
#4  0x556c3f17a303 n/a (udisksd + 0x1f303)
#5  0x7faa5ae37fe6 n/a (libgobject-2.0.so.0 + 0x1bfe6)
#6  0x7faa5ae39bc3 g_object_new_valist (libgobject-2.0.so.0
+ 0x1dbc3)
#7  0x7faa5ae3a219 g_object_new (libgobject-2.0.so.0 +
0x1e219)
#8  0x556c3f17aaac udisks_daemon_new (udisksd + 0x1faac)
#9  0x556c3f1796f2 n/a (udisksd + 0x1e6f2)
#10 0x7faa5af92421 n/a (libgio-2.0.so.0 + 0x116421)
#11 0x7faa5af2d5e3 n/a (libgio-2.0.so.0 + 0xb15e3)
#12 0x7faa5af2e1d3 n/a (libgio-2.0.so.0 + 0xb21d3)
#13 0x7faa5af82e32 n/a (libgio-2.0.so.0 + 0x106e32)
#14 0x7faa5af2d5e3 n/a (libgio-2.0.so.0 + 0xb15e3)
#15 0x7faa5af2d619 n/a (libgio-2.0.so.0 + 0xb1619)
#16 0x7faa5ad31e2f g_main_context_dispatch
(libglib-2.0.so.0 + 0x59e2f)
#17 0x7faa5ad32208 n/a (libglib-2.0.so.0 + 0x5a208)
#18 0x7faa5ad324bf g_main_loop_run (libglib-2.0.so.0 +
0x5a4bf)
#19 0x556c3f17942e main (udisksd + 0x1e42e)
#20 0x7faa5ab1d6ca __libc_start_call_main (libc.so.6 +
0x276ca)
#21 0x7faa5ab1d785 __libc_start_main_impl (libc.so.6 +
0x27785)
#22 0x556c3f179551 _start (udisksd + 0x1e551)

Stack trace of thread 4643:
#0  0x7faa5abf6eb9 syscall (libc.so.6 + 0x100eb9)
#1  0x7faa5ad8bb4c g_cond_wait_until (libglib-2.0.so.0 +
0xb3b4c)
#2  0x7faa5acfbfc1 n/a (libglib-2.0.so.0 + 0x23fc1)
#3  0x7faa5ad5efe2 n/a (libglib-2.0.so.0 + 0x86fe2)
#4  0x7faa5ad5e63d n/a (libglib-2.0.so.0 + 0x8663d)
#5  0x7faa5ab7e3ec start_thread (libc.so.6 + 0x883ec)
#6  0x7faa5abfea1c __clone3 (libc.so.6 + 0x108a1c)

Stack trace of thread 4642:
#0  0x7faa5abf6eb9 syscall (libc.so.6 + 0x100eb9)
#1  0x7faa5ad8b9a0 g_cond_wait (libglib-2.0.so.0 + 0xb39a0)
#2  0x7faa5acfbfeb n/a (libglib-2.0.so.0 + 0x23feb)
#3  0x7faa5ad5ec82 n/a (libglib-2.0.so.0 + 0x86c82)
#4  0x7faa5ad5e63d n/a (libglib-2.0.so.0 + 0x8663d)
#5  0x7faa5ab7e3ec start_thread (libc.so.6 + 0x883ec)
#6  0x7faa5abfea1c __clone3 (libc.so.6 + 0x108a1c)

Stack trace of thread 4644:
#0  0x7faa5abf19ef __GI___poll (libc.so.6 + 0xfb9ef)
#1  0x7faa5ad3217e n/a 

Processed: tagging 1030385

[Debian Bug Tracking System]

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

> tags 1030385 + pending
Bug #1030385 [src:flite] flite: FTBFS with TeXInfo 7.0.x
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: flite: FTBFS with TeXInfo 7.0.x

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1030385 [src:flite] flite: FTBFS with TeXInfo 7.0.x
Severity set to 'serious' from 'important'

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

Processed: Re: proofgeneral: FTBFS with TeXInfo 7.0.x

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1030375 [src:proofgeneral] proofgeneral: FTBFS with TeXInfo 7.0.x
Severity set to 'serious' from 'important'

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

Bug#1040776: marked as done (python-biopython: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jul 2023 21:06:03 +
with message-id 
and subject line Bug#1040776: fixed in python-biopython 1.80+dfsg-6
has caused the Debian Bug report #1040776,
regarding python-biopython: autopkgtest regression
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.)


-- 
1040776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-biopython
Version: 1.80+dfsg-5
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-biopython/35614880/log.gz

...
580s ==
580s ERROR: test_diagram_via_methods_pdf 
(test_GenomeDiagram.DiagramTest.test_diagram_via_methods_pdf)
580s Construct and draw PDF using method approach.
580s --
580s Traceback (most recent call last):
580s   File 
"/tmp/autopkgtest-lxc.aeaunhwi/downtmp/autopkgtest_tmp/Tests/test_GenomeDiagram.py",
 line 1001, in test_diagram_via_methods_pdf
580s gdd.write(output_filename, "PDF")
580s   File 
"/usr/lib/python3/dist-packages/Bio/Graphics/GenomeDiagram/_Diagram.py", line 
244, in write
580s return _write(self.drawing, filename, output, dpi=dpi)
580s^^^
580s   File "/usr/lib/python3/dist-packages/Bio/Graphics/__init__.py", line 46, 
in _write
580s from reportlab.graphics import renderPS, renderPDF, renderSVG
580s   File "/usr/lib/python3/dist-packages/reportlab/graphics/renderSVG.py", 
line 22, in 
580s from .renderPM import _getImage
580s   File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", 
line 20, in 
580s from .utils import setFont as _setFont, RenderPMError
580s   File "/usr/lib/python3/dist-packages/reportlab/graphics/utils.py", line 
9, in 
580s from . _renderPM import makeT1Font
580s ModuleNotFoundError: No module named 'reportlab.graphics._renderPM'
...
582s autopkgtest [22:48:48]: test full_suite:  - - - - - - - - - - results - - 
- - - - - - - -
582s autopkgtest [22:48:48]:  summary
582s dependencies FAIL non-zero exit status 1
582s full_suite   FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: python-biopython
Source-Version: 1.80+dfsg-6
Done: Étienne Mollier 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated python-biopython 
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: Mon, 10 Jul 2023 22:27:12 +0200
Source: python-biopython
Architecture: source
Version: 1.80+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1040776
Changes:
 python-biopython (1.80+dfsg-6) unstable; urgency=medium
 .
   * d/control: depend on python3-reportlab (>= 4.0.4-1~). (Closes: #1040776)
Checksums-Sha1:
 e7f3b4f259891522e5f62cab399e4d36feae024c 3367 python-biopython_1.80+dfsg-6.dsc
 54c1d4f3367265208587b724e7685791bcf37a94 20956 
python-biopython_1.80+dfsg-6.debian.tar.xz
Checksums-Sha256:
 a2cb3cfb82f80bb17c33f2f1f2373b9b8446670683af1267ef470df01529b31e 3367 
python-biopython_1.80+dfsg-6.dsc
 e4d76715eaf0a3f67803de17a4bfa113c6caf3178d4bc36f7d684f6fbdd71564 20956 
python-biopython_1.80+dfsg-6.debian.tar.xz
Files:
 7f0812fce18297867df76caf29597c15 3367 python optional 
python-biopython_1.80+dfsg-6.dsc
 1330cc440ea57225d750a0d75718ff37 20956 python optional 
python-biopython_1.80+dfsg-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmSsbm4UHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdpouhAArtF2j5HhQmLqgQrqBDc8lgrz15IE
eYgMxusxcU5rTRXjZaHUFmriI67Vkvjtwu9ZoX2NP7pxA3R+h+3/lk0Jv/NtKfXP
NfYoMebN6i9xd53tDAr77XHprThNZau3d3HLy3FmLyYIWdGU8QqAlNnoG3N6zUVf
Y0odNoen+S3laGwH1pq1XN9kRJReJhov1lZH1/t78oItzQ30Raab1F6PMF/4KgD3
7dwFSDiHyayvlRIkulvWkJvD6LAO8tUYHYWAM1a95318N7C1H/U8GX0kbcqX2/LF

Bug#1039626: marked as done (sl-modem-dkms: module fails to build for Linux 6.3)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jul 2023 21:06:29 +
with message-id 
and subject line Bug#1039626: fixed in sl-modem 2.9.11~20110321-19
has caused the Debian Bug report #1039626,
regarding sl-modem-dkms: module fails to build for Linux 6.3
to be marked as done.

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

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


-- 
1039626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sl-modem-dkms
Version: 2.9.11~20110321-17
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts


1.) There is an autopkgtest regression with the -cloud kernel,
preventing migration to testing (therefore severity serious):

https://ci.debian.net/data/autopkgtest/testing/amd64/s/sl-modem/34615715/log.gz

DKMS make.log for sl-modem-2.9.11~20110321 for kernel 6.1.0-9-cloud-amd64 
(x86_64)
Mon Jun 19 06:58:35 UTC 2023
make: Entering directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
obj-m= slusb.o 
slamr-objs=amrmo_init.o sysdep_amr.o amrlibs.o
make modules -C /lib/modules/6.1.0-9-cloud-amd64/build 
M=/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers
make[1]: Entering directory '/usr/src/linux-headers-6.1.0-9-cloud-amd64'
  CC [M]  /var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/st7554.o
  LD [M]  /var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/slusb.o
  MODPOST /var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/Module.symvers
ERROR: modpost: "usb_alloc_urb" 
[/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/slusb.ko] undefined!
ERROR: modpost: "usb_free_urb" 
[/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/slusb.ko] undefined!
ERROR: modpost: "usb_register_driver" 
[/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/slusb.ko] undefined!
ERROR: modpost: "usb_clear_halt" 
[/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/slusb.ko] undefined!
ERROR: modpost: "usb_submit_urb" 
[/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/slusb.ko] undefined!
ERROR: modpost: "usb_control_msg" 
[/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/slusb.ko] undefined!
ERROR: modpost: "usb_set_interface" 
[/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/slusb.ko] undefined!
ERROR: modpost: "usb_deregister" 
[/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/slusb.ko] undefined!
ERROR: modpost: "usb_unlink_urb" 
[/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/slusb.ko] undefined!
make[2]: *** 
[/usr/src/linux-headers-6.1.0-9-common/scripts/Makefile.modpost:126: 
/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/Module.symvers] Error 1
make[1]: *** [/usr/src/linux-headers-6.1.0-9-common/Makefile:1989: modpost] 
Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-9-cloud-amd64'
make: *** [Makefile:138: all] Error 2
make: Leaving directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
make: Entering directory 
'/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem'
make modules -C /lib/modules/6.1.0-9-cloud-amd64/build 
M=/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem
make[1]: Entering directory '/usr/src/linux-headers-6.1.0-9-cloud-amd64'
  CC [M]  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.o
  MODPOST 
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/Module.symvers
  CC [M]  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.mod.o
  LD [M]  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.ko
  BTF [M] 
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.ko
Skipping BTF generation for 
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.ko 
due to unavailability of vmlinux
make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-9-cloud-amd64'
make: Leaving directory 
'/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem'

You probably need to add this line to your dkms.conf:

BUILD_EXCLUSIVE_CONFIG="CONFIG_USB"

in order to skip building the module for kernels without CONFIG_USB.



2.) the module fails to build for Linux 6.4

DKMS make.log for sl-modem-2.9.11~20110321 for kernel 6.4.0-0-amd64 (x86_64)
Tue Jun 27 10:00:31 UTC 2023
make: Entering directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
obj-m= slusb.o
slamr-objs=amrmo_init.o sysdep_amr.o amrlibs.o
make modules -C /lib/modules/6.4.0-0-amd64/build 
M=/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers
make[1]: Entering directory 

Processed: Re: festival: FTBFS with TeXInfo 7.0.x

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1030367 [src:festival] festival: FTBFS with TeXInfo 7.0.x
Severity set to 'serious' from 'important'

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

Processed: Re: elpa-transient: FTBFS with TeXInfo 7.0.x

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1030346 [src:elpa-transient] elpa-transient: FTBFS with TeXInfo 7.0.x
Severity set to 'serious' from 'important'

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

Processed: Re: fweb: FTBFS with TeXInfo 7.0.x

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1030350 [src:fweb] fweb: FTBFS with TeXInfo 7.0.x
Severity set to 'serious' from 'important'

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

Processed: Re: [Pkg-utopia-maintainers] Bug#1040793: udisks2: last sid upload introduced a crash

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1040793 [udisks2] udisks2: last sid upload introduced a crash
Severity set to 'serious' from 'normal'
> retitle -1 udisks2 crashes when libblockdev plugins are missing
Bug #1040793 [udisks2] udisks2: last sid upload introduced a crash
Changed Bug title to 'udisks2 crashes when libblockdev plugins are missing' 
from 'udisks2: last sid upload introduced a crash'.

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

Processed: Re: quelcom: FTBFS with TeXInfo 7.0.x

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1030328 [src:quelcom] quelcom: FTBFS with TeXInfo 7.0.x
Severity set to 'serious' from 'important'

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

Bug#1040776: marked as pending in python-biopython

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #1040776 in python-biopython 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/med-team/python-biopython/-/commit/f74f80414639e5c3204bf6db8848e2f2c70b9685


d/control: depend on python3-reportlab (>= 4.0.4-1~).

Closes: #1040776


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040776

Processed: Bug#1040776 marked as pending in python-biopython

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040776 [src:python-biopython] python-biopython: autopkgtest regression
Ignoring request to alter tags of bug #1040776 to the same tags previously set

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

Bug#414092: airport-utils 2-8

[Ricky Ricardo]

Hello. I have the same problem as reported on message #5 of this bug report.
I am using a Raspberry Pi Model 4B with Raspberry Pi OS (most recent
version, 32-bit).

I installed the airport-utils 2-8 from the repository.
Installation was okay, but when running airport-config from the terminal
nothing happened.

Would like these utilities to work so that I can re-configure an old Apple
Airport Express (or Extreme?) unit.

Thanks,
Rick

Processed: Re: gnushogi: FTBFS with TeXInfo 7.0.x

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1030322 [src:gnushogi] gnushogi: FTBFS with TeXInfo 7.0.x
Added tag(s) patch.
> severity -1 serious
Bug #1030322 [src:gnushogi] gnushogi: FTBFS with TeXInfo 7.0.x
Severity set to 'serious' from 'important'

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

Bug#1040776: marked as pending in python-biopython

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #1040776 in python-biopython 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/med-team/python-biopython/-/commit/f74f80414639e5c3204bf6db8848e2f2c70b9685


d/control: depend on python3-reportlab (>= 4.0.4-1~).

Closes: #1040776


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040776

Processed: Bug#1040776 marked as pending in python-biopython

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040776 [src:python-biopython] python-biopython: autopkgtest regression
Added tag(s) pending.

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

Bug#1040056: [Pkg-opencl-devel] Bug#1040056: spirv-tools breaks spirv-llvm-translator-15 autopkgtest: exactly one input file must be specified.

[Paul Gevers]

Hi,

On 10-07-2023 11:30, Andreas Beckmann wrote:

Does this issue affect spirv-llvm-translator-16, too?
I tried to trigger the corresponding tests (which succeeded), but I'm 
not sure if it really tested the correct setup.


https://release.debian.org/britney/excuses.yaml.gz tells me that -16 was 
tested too and that it didn't fail (NEUTRAL; link to the log is in the 
excuses.yaml).


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1040802: xkb-data: Breaks altgr in Norwegian layout

[Tollef Fog Heen]

Package: xkb-data
Version: 2.38-2
Severity: serious
Justification: makes a subset of systems effectively unusable
X-Debbugs-Cc: none, Tollef Fog Heen 

With commit 0fb34101788d84e9a1d98b3730cc7b9295e0f19b in
xkeyboard-config, `group(alts_toggle)` changed behaviour in a way such
that the right alt no longer generates altgr.  This is very problematic
with keyboard layouts such as Norwegian where that is required to type @
(altgr-2) or $ (altgr-4).

setxkmap no -print on my system outputs:

xkb_keymap {
xkb_keycodes  { include "evdev+aliases(qwerty)" };
xkb_types { include "complete"  };
xkb_compat{ include "complete"  };
xkb_symbols   { include 
"pc+no+inet(evdev)+level3(ralt_switch)+compose(caps)+group(alts_toggle)"
};
xkb_geometry  { include "pc(pc105)" };
};

which includes the problematic toggle.  I don't know if the right fix is
to revert the relevant commit (reintroducing the problem in
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/316)
or something else, but the current way it works is not great.

Happy to help debug this further, let me know what I can provide.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Bug#1040801: mcomix: pillow 10.0.0 not recognized as higher than 6.0.0

[Sebastien KALT]

Package: mcomix
Version: 2.1.0-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since python3-pil:amd64 upgrade from 9.5.0-1 to 10.0.0-1, it's impossible to
launch mcomix :

$ mcomix
22:02:01 [MainThread] ERROR: You don't have the required version of the Python
Imaging Library Fork (Pillow) installed.
22:02:01 [MainThread] ERROR: Installed Pillow version is: 10.0.0
22:02:01 [MainThread] ERROR: Required Pillow version is: 6.0.0 or higher

Downgrading python3-pil to 9.5.0-1 solves the problem, but it removes other
packages I use (qgis, matplotlib).

Regards,

Sébastien


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (980, 'unstable'), (970, 'testing'), (960, 'stable'), (500, 
'testing-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 mcomix depends on:
ii  gir1.2-gtk-3.03.24.37-2
ii  python3   3.11.4-5
ii  python3-cairo 1.24.0-1
ii  python3-gi3.42.2-3+b1
ii  python3-gi-cairo  3.42.2-3+b1
ii  python3-pil   10.0.0-1

Versions of packages mcomix recommends:
ii  python3-chardet  5.1.0+dfsg-2

Versions of packages mcomix suggests:
pn  lhasa
ii  mupdf-tools  1.22.2+ds1-1
ii  p7zip16.02+dfsg-8
ii  unrar1:6.2.8-1
ii  unzip6.0-28

-- no debconf information

Bug#1040800: lomiri-ui-toolkit: FTBFS on i386: file:///<>/qml/Lomiri/Metrics/qmldir:2:1: plugin cannot be loaded for module "Lomiri.Metrics": Cannot protect module Lomiri.Metrics 0 as it

[Sebastian Ramacher]

Source: lomiri-ui-toolkit
Version: 1.3.5010+dfsg-1
Severity: serious
Tags: ftbfs sid trixie
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=lomiri-ui-toolkit=i386=1.3.5010%2Bdfsg-1%2Bb1=1688977672=0

import Lomiri.Metrics 0.1 as ALomiri_Metrics_0_1
QtObject { }

file:///<>/qml/Lomiri/Metrics/qmldir:2:1: plugin cannot be loaded 
for module "Lomiri.Metrics": Cannot protect module Lomiri.Metrics 0 as it was 
never registered
make[3]: *** [Makefile:743: check] Error 1
make[2]: *** [Makefile:476: test] Error 2
dh_auto_test: error: make -j1 test returned exit code 2
Tail of xvfb-run output:
Creating QML component for Lomiri.Metrics
Failed to load Lomiri.Metrics
import QtQuick 2.0
import Lomiri.Metrics 0.1 as ALomiri_Metrics_0_1
QtObject { }

file:///<>/qml/Lomiri/Metrics/qmldir:2:1: plugin cannot be loaded 
for module "Lomiri.Metrics": Cannot protect module Lomiri.Metrics 0 as it was 
never registered
make[3]: *** [Makefile:743: check] Error 1
make[2]: *** [Makefile:476: test] Error 2

Cheers
-- 
Sebastian Ramacher

Bug#1040776: [Debian-med-packaging] Bug#1040776: python-biopython: autopkgtest regression

[Étienne Mollier]

Hi Adrian,

Adrian Bunk, on 2023-07-10:
> 580s ModuleNotFoundError: No module named 'reportlab.graphics._renderPM'

Thanks for your report, migrations of biopython and reportlab
seem to have gone entangled.  I'll bump the version requirement
of python3-reportlab to unlock the situation.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-on air: Scale The Summit - Whales


signature.asc
Description: PGP signature

Processed: RM: ruby-derailed-benchmarks -- ROM; rc-buggy, no longer needed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:ruby-derailed-benchmarks
Bug #1040798 [ftp.debian.org] RM: ruby-derailed-benchmarks -- ROM; rc-buggy, no 
longer needed
Added indication that 1040798 affects src:ruby-derailed-benchmarks
> block 1039916 by -1
Bug #1039916 [src:ruby-derailed-benchmarks] ruby-derailed-benchmarks: 
autopkgtest needs update for new version of ruby-memory-profiler: Could not 
find 'memory_profiler' (~> 0)
1039916 was not blocked by any bugs.
1039916 was not blocking any bugs.
Added blocking bug(s) of 1039916: 1040798

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

Bug#1031797: marked as done (libsemanage: Inaccurate copyright file)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jul 2023 19:04:40 +
with message-id 
and subject line Bug#1031797: fixed in libsemanage 3.5-1
has caused the Debian Bug report #1031797,
regarding libsemanage: Inaccurate copyright file
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.)


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

Source: libsemanage
Version: 3.4-1
Severity: serious
Control: tags -1 patch

The d/copyright file points to a 404 URL as source.
Also, it does not present all copyright information that is contained in the 
source.
I have a fix for these Policy violations attached in the machine-readable 
format.Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Comment: This is the Debian package for libsemanage.
Source: https://github.com/SELinuxProject/selinux/wiki/Releases

Files: *
Copyright: (C) 2004-2007, 2009 Tresys Technology, LLC
   (C) 2005 Red Hat, Inc.
   (C) 2005-2021 Red Hat, Inc.
   (C) 2017 Mellanox Technologies Inc.
License: LGPL-2.1+
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
 .
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
Lesser General Public License for more details.
 .
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1
Comment:
 On Debian GNU/Linux systems, the complete text of the Lesser GNU General
 Public License version 2.1 can be found in 
`/usr/share/common-licenses/LGPL-2.1'.

Files: debian/*
Copyright: © 2005-2009, Manoj Srivastava 
License: GPL-2
The Debian specific changes are distributed under the terms of the
GNU General Public License, version 2.
 .
A copy of the GNU General Public License is also available at
http://www.gnu.org/copyleft/gpl.html>.  You may also obtain
it by writing to the Free Software Foundation, Inc., 51 Franklin
St, Fifth Floor, Boston, MA 02110-1301, USA.
Comment:
 On Debian GNU/Linux systems, the complete text of the GNU General
 Public License version 2 can be found in `/usr/share/common-licenses/GPL-2'.
--- End Message ---
--- Begin Message ---
Source: libsemanage
Source-Version: 3.5-1
Done: Laurent Bigonville 

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated libsemanage 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: Mon, 10 Jul 2023 20:43:07 +0200
Source: libsemanage
Architecture: source
Version: 3.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian SELinux maintainers 
Changed-By: Laurent Bigonville 
Closes: 1022967 1031797
Changes:
 libsemanage (3.5-1) unstable; urgency=medium
 .
   [ Laurent Bigonville ]
   * New upstream release
 - debian/rules: Properly set the install layout for the python module
 - debian/control: Bump {build-}dependencies to match new release
   * debian/upstream/signing-key.asc: Add public key of Jason Zaman
   * debian/control: Bump Standards-Version to 4.6.2 (no further changes)
   * debian/control: Drop ancient Breaks/Replaces
   * debian/control: Drop dependency against ruby | ruby-interpreter, to please
 lintian
 .
   [ Helmut Grohne ]
   * Fix FTCBFS: Support cross building python and ruby extensions.
 (Closes: #1022967)
 .
   [ Bastian Germann ]
   * Fix "Inaccurate copyright file" (Closes: #1031797)
Checksums-Sha1:
 2d0be1004a502018e96adec9d6ae1a78c92eff5b 2644 libsemanage_3.5-1.dsc
 7dfb7935f03d08640a3afc5107d8e29405909a91 

Bug#1040790: installation-reports: ID in /etc/machine-id and /var/lib/dbus/machine-id mismatch on fresh debian 12 installation

[Luca Boccassi]

On Mon, 10 Jul 2023 17:14:48 +0100 Steve McIntyre 
wrote:
> Hi, and thanks for your bug report!
> 
> On Mon, Jul 10, 2023 at 05:27:50PM +0200, yogg wrote:
> >Package: installation-reports
> >Severity: serious
> >Tags: d-i
> >Justification: https://wiki.debian.org/MachineId
> >
> 
> ...
> 
> >After installation was finished and the system has been restarted
the
> >files "/etc/machine-id" and "/var/lib/dbus/machine-id" are not
linked
> >in any way (no soft or hardlink) and the ID inside the files differ
> >from each other.
> 
> I've confirmed this bug just now, doing a clean installation from the
> 12.0.0 amd64 netinst.

As a wild guess, maybe the split of src:dbus into multiple packages
affected the order in which the postinsts run, and now systemd's runs
first and creates /etc/machine-id, and then dbus-daemon's runs and
creates /var/lib/dbus/machine-id.

There is a tmpfiles.d shipped by dbus-daemon that creates
/var/lib/dbus/machine-id as a symlink to /etc/machine-id if it exists,
but this snippet runs _after_ the dbus-uuidgen so effectively it is
always a no-op on package install:

$ cat /var/lib/dpkg/info/dbus-daemon.postinst 
#!/bin/sh

set -e

if [ "$1" = configure ]; then
# This is idempotent, so it's OK to do every time. The system bus' init
# script does this anyway, but you also have to do this before a session
# bus will work on non-systemd systems, so we do this here for the
# benefit of people starting a temporary session bus in a chroot.
mkdir -p "${DPKG_ROOT:-/}var/lib/dbus"
dbus-uuidgen --ensure="${DPKG_ROOT:-/}var/lib/dbus/machine-id"
fi

# Automatically added by dh_installtmpfiles/13.11.4
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -x "$(command -v systemd-tmpfiles)" ]; then
systemd-tmpfiles ${DPKG_ROOT:+--root="$DPKG_ROOT"} --create 
dbus.conf >/dev/null || true
fi
fi
# End automatically added section

It seems to me a safe way to fix this and do the right thing is to swap
the #DEBHELPER# token and the manual dbus-uuidgen block in dbus-
daemon's postinst. Then on systemd systems the tmpfiles will win and on
other systems dbus-uuidgen will do its job.

-- 
Kind regards,
Luca Boccassi


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

Bug#1040257: schleuder-cli does not work with Ruby >= 3.0.0

[Georg Faerber]

Hi,

Thanks for your report.

On 23-07-03 23:50:03, s3lph wrote:
> [...]
>
> Upstream has fixed the issue on the main branch, but has not yet
> created a new release containing the fix.  The fix is quite small,
> only two lines diff:
> 
> https://0xacab.org/schleuder/schleuder-cli/-/commit/68754cf94cc2d9b2a400ff19d2e48a7ffa2ec1f2
> 
> With this patch applied manually, schleuder-cli works as expected:
>
> [...]

Indeed, I forgot to pull this into Debian, apologies for that. That's
fixed now via 0.1.0-5.

bookworm-pu is tracked via #1040791.

Cheers,
Georg

Bug#1040714: dhcpcd: Missing epoch from souce package version

[Martin-Éric Racine]

On Mon, Jul 10, 2023 at 7:05 PM Salvatore Bonaccorso  wrote:
> On Sun, Jul 09, 2023 at 10:39:59PM +0300, Martin-Éric Racine wrote:
> > On Sun, Jul 9, 2023 at 10:33 PM Salvatore Bonaccorso  
> > wrote:
> > > On Sun, Jul 09, 2023 at 09:25:33PM +0200, Salvatore Bonaccorso wrote:
> > > > Source: dhcpcd
> > > > Version: 10.0.1-1
> > > > Severity: serious
> > > > Justification: Debian version goes backwards from previous released 
> > > > versions
> > > > X-Debbugs-Cc: car...@debian.org
> > > >
> > > > Hi
> > > >
> > > > The new src:dhcpcd has a lower version of any previous released
> > > > src:dhcpd version, which had an epoch:
> > >
> > > Apologies for the typo, should be src:dhcpcd in both cases obviously
> > > :(
> >
> > Which is a slightly different issue than what Andtreas reported at
> > #1037190.  Sorry.
>
> No problem, just reopenng while we discuss it.

Agreed.

> > Unless I'm mistaken, we're basically looking at 2 separate issues:
> >
> > 1) bin:dhcpcd from Wheezy has a higher epoch that the one in Bookworm.
> > This is easily fixed as explained in #1037190 for Bookworm.
> >
> > 2) Since transiting the source from src:dhcpcd5 to src:dhcpcd we're
> > missing an epoch for everything. This requires reverting the above fix
> > and simply introducing an epoch for the whole src and binaries.
>
> Yes correct, this is maninly as well what I was referring to. But that
> would solve as well at same time the former issue right, if we drop
> all special casing for epoch on the binary packages, is this correct?

In Trixie, for the version, it would. Just insert the epoch for the
whole source (which would apply to the binaries generated too) and
we're done.

However, we still need that preinst script to clean up possible Wheezy
leftovers.

In Bookworm, we'll still need the version mingle just for one binary
target. debdiff for stable-proposed-updates are on #1037190 and the
upload is ready on Mentors.

> So if we add the epoch to the whole src;dhcpcd version, and to the
> produced binaries I think all the issues should be resolved.
>
> My background is here:
> https://security-tracker.debian.org/tracker/source-package/dhcpcd
> e.g. https://security-tracker.debian.org/tracker/CVE-2002-1403 will be
> considered not yet fixed, because for dpkg:
>
> $ dpkg --compare-versions 1:1.3.22pl2-2 lt 10.0.1-1
> $ echo $?
> 1

I was actually wondering how to close those old CVE against the old fork.

> > Or have I misunderstood the issue?
>
> No, I think we are on the same page in my understnding!

Excellent.

Martin-Éric

Bug#1040257: marked as done (schleuder-cli does not work with Ruby >= 3.0.0)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jul 2023 16:27:38 +
with message-id 
and subject line Bug#1040257: fixed in schleuder-cli 0.1.0-5
has caused the Debian Bug report #1040257,
regarding schleuder-cli does not work with Ruby >= 3.0.0
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.)


-- 
1040257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: schleuder-cli
Version: 0.1.0-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

schleuder-cli 0.1.0 was designed for Ruby 2.7 in mind; Ruby 3.0
comes with a breaking change that breaks schleuder-cli.  As bookworm
comes with Ruby 3.1, schleuder-cli crashes when used due to this
breaking change:

  root@localhost:/# schleuder-cli lists new t...@schleuder.example.org 
ad...@example.org /tmp/ad...@example.org.asc
  ::1 - - [03/Jul/2023:20:56:58 +] "POST /lists.json HTTP/1.1" 200 1102 
1.5971
  List t...@schleuder.example.org successfully created! Don't forget to hook it 
into your MTA.
  /usr/lib/ruby/vendor_ruby/schleuder-cli/helper.rb:22:in `block in url': 
undefined method `escape' for URI:Module (NoMethodError)

  "#{URI.escape(k.to_s)}=#{URI.escape(v.to_s)}"
^^^
from /usr/lib/ruby/vendor_ruby/schleuder-cli/helper.rb:21:in `each'
from /usr/lib/ruby/vendor_ruby/schleuder-cli/helper.rb:21:in `map'
from /usr/lib/ruby/vendor_ruby/schleuder-cli/helper.rb:21:in `url'
from /usr/lib/ruby/vendor_ruby/schleuder-cli/helper.rb:191:in 
`import_key'
from /usr/lib/ruby/vendor_ruby/schleuder-cli/helper.rb:170:in 
`import_key_and_find_fingerprint'
from /usr/lib/ruby/vendor_ruby/schleuder-cli/lists.rb:30:in `new'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor/command.rb:27:in 
`run'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor/invocation.rb:127:in
 `invoke_command'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor.rb:392:in 
`dispatch'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor/invocation.rb:116:in
 `invoke'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor.rb:243:in `block 
in subcommand'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor/command.rb:27:in 
`run'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor/invocation.rb:127:in
 `invoke_command'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor.rb:392:in 
`dispatch'
from 
/usr/share/rubygems-integration/all/gems/thor-1.2.1/lib/thor/base.rb:485:in 
`start'
from /usr/bin/schleuder-cli:7:in `'


Upstream has fixed the issue on the main branch, but has not yet
created a new release containing the fix.  The fix is quite small,
only two lines diff:

https://0xacab.org/schleuder/schleuder-cli/-/commit/68754cf94cc2d9b2a400ff19d2e48a7ffa2ec1f2

With this patch applied manually, schleuder-cli works as expected:

  root@localhost:/# schleuder-cli lists new t...@schleuder.example.org 
ad...@example.org /tmp/ad...@example.org.asc
  ::1 - - [03/Jul/2023:21:33:04 +] "POST /lists.json HTTP/1.1" 200 1108 
4.6595
  List t...@schleuder.example.org successfully created! Don't forget to hook it 
into your MTA.
  ::1 - - [03/Jul/2023:21:33:04 +] "POST 
/keys.json?list_id=test%40schleuder.example.org HTTP/1.1" 200 327 0.0120
  Key 48F817C6EF39DE78AEEF5D0AD6A09061E4E11475: imported
  ::1 - - [03/Jul/2023:21:33:04 +] "POST 
/subscriptions.json?list_id=test%40schleuder.example.org HTTP/1.1" 201 - 0.1797


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

Kernel: Linux 6.1.0-9-amd64 (SMP w/2 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 schleuder-cli depends on:
ii  ruby   1:3.1
ii  ruby-thor  1.2.1-2

schleuder-cli recommends no packages.

schleuder-cli suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: schleuder-cli
Source-Version: 0.1.0-5
Done: Georg Faerber 

We believe that the bug you reported is fixed in the latest version of
schleuder-cli, 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 

Bug#1040763: marked as done (boswars: binary-any FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jul 2023 16:19:15 +
with message-id 
and subject line Bug#1040763: fixed in boswars 2.8-2
has caused the Debian Bug report #1040763,
regarding boswars: binary-any FTBFS
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.)


-- 
1040763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boswars
Version: 2.8-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=boswars=2.8-1

...
   dh_install -a
   debian/rules execute_after_dh_install-arch
make[1]: Entering directory '/<>'
# Copy (and rename) an icon to be used as desktop file
mkdir -p debian/boswars/usr/share/pixmaps/
cp units/tank/ico_tank.png debian/boswars/usr/share/pixmaps/boswars.png
rm -f debian/boswars/usr/share/doc/boswars/html/README-SDL.txt
rm -f debian/boswars/usr/share/doc/boswars/html/*copyright*
rm -f debian/boswars/usr/share/doc/boswars/html/gpl3.txt
iconv -f ISO-8859-1 -t UTF-8 units/corpses/unit-corpses.lua -o 
debian/boswars-data/usr/share/games/boswars/units/corpses/unit-corpses.lua
iconv: cannot open output file: No such file or directory
make[1]: *** [debian/rules:26: execute_after_dh_install-arch] Error 1
--- End Message ---
--- Begin Message ---
Source: boswars
Source-Version: 2.8-2
Done: Alexandre Detiste 

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

Debian distribution maintenance software
pp.
Alexandre Detiste  (supplier of updated boswars 
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: Sun, 09 Jul 2023 21:49:11 +0200
Source: boswars
Architecture: source
Version: 2.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Alexandre Detiste 
Closes: 1040763
Changes:
 boswars (2.8-2) unstable; urgency=medium
 .
   * FTBFS: redo split -arch vs -any,
 add an explicit dependency on python3:any (Closes: #1040763)
Checksums-Sha1:
 7d4438c5e57aca3f8e66f325a06dcb326741a9ac 2098 boswars_2.8-2.dsc
 aefc5c900ab596fb413faaf5e342bd25f4f114dd 11648 boswars_2.8-2.debian.tar.xz
 0ed5b245c07c79b1e4424b99d28ec22f75ae6faa 5604 boswars_2.8-2_all.buildinfo
Checksums-Sha256:
 6964c216172539fc21bb9f7bf20b9c6c36c7e79da70ed5ed24217e4dfe605d43 2098 
boswars_2.8-2.dsc
 e769cf83f231ff5d3d648365ca69f10f9aa24c148fb9e337036f1cc3ca4d0e8b 11648 
boswars_2.8-2.debian.tar.xz
 084b7e7db3beb5cd435ddf096763416fb8c0bef0d1089c8704ffa3304dec303f 5604 
boswars_2.8-2_all.buildinfo
Files:
 b7255c815a236e7bb89a64b54d0a608e 2098 games optional boswars_2.8-2.dsc
 3a98cb1d673737d5b2cad7647651c84e 11648 games optional 
boswars_2.8-2.debian.tar.xz
 1d28efc4b86385b605a2d35cf4729455 5604 games optional 
boswars_2.8-2_all.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmSsKLIACgkQkWT6HRe9
XTZX+w/9FgJ2ZXMoPA/Or2tvlPwV7gsUFTQO3wQpV4dEDxvM3gyQWA95CrdbdWnw
7hnUfaZ1j3JO8QzlpMPqvsJFzc5uWMkqZ3PBibQHbTnWu2P3qUZHf1tmQ9BESayF
56hZOSYbPBq2EASdPUwbIPIueO8+UaUmjoJlSysiqzFkbv2RM5noOWMZtrHcBwkX
B54coyFt8W2roNoZISucFbYYO9cJ40JWduWZh4Fx6LST1NZ+ulgOioJZTO0hHRFQ
gjKQOGx+zQ3IoR0y+qdvVV3X8bP9G2tHkE0dlWu38RLqNrTd9NBD1ws6D2UhKxU3
/GigtvkgIA+OwZsrW728BD/zytsPLLIGEWG65/GO9/1LNOf1065e4QBd8GFNfib/
xrMmMUZPRJoyvSM4A7CYdFTv0f3Rab5oaq/OJXOfGQzQy9vGkpQWhwm10JVNe1Jk
hZMEEx+/ns816ZolXIO7kl+dy2WBBkTMar/YrdG5AfW6lsxpfJX6Y1HPpt8WQo6a
P2+oS8Sy8F7WifQwT++rRTjfQUCtNMSmFrYFxexRctg1MVklTvmsWEpqp99zu8sA
9J/3nLZm/5H1bGLZ2TgNdkq5+BkvY/y51+fqJQ1Hu9aDvq7nm4zUVBbq0Q+nLSrT
i6p40hmarTNtfiDQVqhEznDLj8CiFNyZPx6/g42PrjjoAT4885E=
=m086
-END PGP SIGNATURE End Message ---

Bug#1040790: installation-reports: ID in /etc/machine-id and /var/lib/dbus/machine-id mismatch on fresh debian 12 installation

[Steve McIntyre]

Hi, and thanks for your bug report!

On Mon, Jul 10, 2023 at 05:27:50PM +0200, yogg wrote:
>Package: installation-reports
>Severity: serious
>Tags: d-i
>Justification: https://wiki.debian.org/MachineId
>

...

>After installation was finished and the system has been restarted the
>files "/etc/machine-id" and "/var/lib/dbus/machine-id" are not linked
>in any way (no soft or hardlink) and the ID inside the files differ
>from each other.

I've confirmed this bug just now, doing a clean installation from the
12.0.0 amd64 netinst.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Managing a volunteer open source project is a lot like herding
 kittens, except the kittens randomly appear and disappear because they
 have day jobs." -- Matt Mackall

Processed: Re: Bug#1040714: dhcpcd: Missing epoch from souce package version

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1040714 {Done: Martin-Éric Racine } 
[src:dhcpcd] dhcpcd: Missing epoch from souce package version
Bug reopened
Ignoring request to alter fixed versions of bug #1040714 to the same values 
previously set

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

Bug#1040714: dhcpcd: Missing epoch from souce package version

[Salvatore Bonaccorso]

Control: reopen -1 

Hi Martin-Eric,

On Sun, Jul 09, 2023 at 10:39:59PM +0300, Martin-Éric Racine wrote:
> On Sun, Jul 9, 2023 at 10:33 PM Salvatore Bonaccorso  
> wrote:
> > On Sun, Jul 09, 2023 at 09:25:33PM +0200, Salvatore Bonaccorso wrote:
> > > Source: dhcpcd
> > > Version: 10.0.1-1
> > > Severity: serious
> > > Justification: Debian version goes backwards from previous released 
> > > versions
> > > X-Debbugs-Cc: car...@debian.org
> > >
> > > Hi
> > >
> > > The new src:dhcpcd has a lower version of any previous released
> > > src:dhcpd version, which had an epoch:
> >
> > Apologies for the typo, should be src:dhcpcd in both cases obviously
> > :(
> 
> Which is a slightly different issue than what Andtreas reported at
> #1037190.  Sorry.

No problem, just reopenng while we discuss it.

> Unless I'm mistaken, we're basically looking at 2 separate issues:
> 
> 1) bin:dhcpcd from Wheezy has a higher epoch that the one in Bookworm.
> This is easily fixed as explained in #1037190 for Bookworm.
> 
> 2) Since transiting the source from src:dhcpcd5 to src:dhcpcd we're
> missing an epoch for everything. This requires reverting the above fix
> and simply introducing an epoch for the whole src and binaries.

Yes correct, this is maninly as well what I was referring to. But that
would solve as well at same time the former issue right, if we drop
all special casing for epoch on the binary packages, is this correct?

So if we add the epoch to the whole src;dhcpcd version, and to the
produced binaries I think all the issues should be resolved.

My background is here:
https://security-tracker.debian.org/tracker/source-package/dhcpcd
e.g. https://security-tracker.debian.org/tracker/CVE-2002-1403 will be
considered not yet fixed, because for dpkg:

$ dpkg --compare-versions 1:1.3.22pl2-2 lt 10.0.1-1
$ echo $?
1

> Or have I misunderstood the issue?

No, I tink we are on the same page in my understnding!

Thank you for looking into this issue.

Regards,
Salvatore

Bug#1040521: tpm2-tss: FTBFS (test failures)

[Ying-Chun Liu (PaulLiu)]

Hi all,

The patch for fixing 32-bit platforms is as attachment.
Build log on armhf is also attached as a reference.

I think I can upload a fix after the upstream fixes the problem on s390x.

Yours,
Paul


Description: Fix test failed on 32-bit platforms.
 We should avoid converting pointers to integers on 32-bit platforms.
Bug-Debian: http://bugs.debian.org/1040521
Author: Ying-Chun Liu (PaulLiu) 
Last-Update: 2023-07-10
Index: tpm2-tss-4.0.1/test/unit/tcti-libtpms.c
===
--- tpm2-tss-4.0.1.orig/test/unit/tcti-libtpms.c
+++ tpm2-tss-4.0.1/test/unit/tcti-libtpms.c
@@ -1094,7 +1094,7 @@ tcti_libtpms_remap_state_posix_fallocate
 unsigned char cmd[] = {0x80, 0x01, 0x00, 0x00, 0x00, 0x0c, 0x00, 0x00, 0x01, 0x44, 0x00, 0x00};
 unsigned char rsp[] = {0x80, 0x01, 0x00, 0x00, 0x00, 0x0a, 0x00, 0x00, 0x00, 0x00};
 
-expect_value(TPMLIB_Process, cmd, cmd);
+expect_memory(TPMLIB_Process, cmd, cmd, sizeof(cmd));
 expect_value(TPMLIB_Process, cmd_len, sizeof(cmd));
 expect_value(TPMLIB_Process, locality, 0);
 will_return(TPMLIB_Process, rsp);


tpm2-tss_4.0.1-1_armhf.build.xz
Description: application/xz


OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Processed: tagging 1040257

[Debian Bug Tracking System]

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

> tags 1040257 + confirmed fixed-upstream patch
Bug #1040257 [schleuder-cli] schleuder-cli does not work with Ruby >= 3.0.0
Added tag(s) fixed-upstream and confirmed.
> thanks
Stopping processing here.

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

Bug#1040630: gavodachs autopkg tests fail with pillow 10.0.0

[Matthias Klose]

reported upstream: https://github.com/python-pillow/Pillow/issues/7275

Bug#1040790: installation-reports: ID in /etc/machine-id and /var/lib/dbus/machine-id mismatch on fresh debian 12 installation

[yogg]

Package: installation-reports
Severity: serious
Tags: d-i
Justification: https://wiki.debian.org/MachineId

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: CD/network
Image version: http://ftp.debian.org/debian/dists/bookworm/main/installer-amd64/
Date: 2023-07-10

Machine: Virtual-Maschine
Partitions:
Disk /dev/vda: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xcf0c07c3

Device Boot   Start  End  Sectors  Size Id Type
/dev/vda1  2048  2000895  1998848  976M 82 Linux swap / Solaris
/dev/vda2  *2000896 20969471 189685769G 83 Linux



Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]?

Comments/Problems:

After installation was finished and the system has been restarted the files 
"/etc/machine-id" and "/var/lib/dbus/machine-id" are not linked in any way (no 
soft or hardlink) and the ID inside the files differ from each other.

Expected:
"cat /etc/machine-id /var/lib/dbus/machine-id" should return the same ID two 
times

Workaround:
rm /etc/machine-id /var/lib/dbus/machine-id && dbus-uuidgen 
--ensure=/etc/machine-id && dbus-uuidgen --ensure


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230607"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux debian-test 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
6.1.27-1 (2023-05-08) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE 
[Natoma/Triton II] [8086:7010]
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: Kernel modules: ata_piix, ata_generic
lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 
[1013:00b8]
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: Kernel driver in use: cirrus
lspci -knn: Kernel modules: cirrus
lspci -knn: 00:03.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network 
device [1af4:1000]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0001]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:04.0 Communication controller [0780]: Red Hat, Inc. Virtio 
console [1af4:1003]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0003]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:05.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio block 
device [1af4:1001]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0002]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:06.0 Unclassified device [00ff]: Red Hat, Inc. Virtio memory 
balloon [1af4:1002]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0005]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:07.0 Unclassified device [00ff]: Red Hat, Inc. Virtio RNG 
[1af4:1005]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0004]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lsmod: Module  Size  Used by
lsmod: fuse  176128  0
lsmod: battery28672  0
lsmod: dm_mod184320  0
lsmod: md_mod192512  0
lsmod: xfs  1945600  0
lsmod: jfs   221184  0
lsmod: btrfs1777664  0
lsmod: xor24576  1 btrfs
lsmod: 

Bug#1040630: gavodachs autopkg tests fail with pillow 10.0.0

[Markus Demleitner]

On Sat, Jul 08, 2023 at 09:23:21AM +0200, Matthias Klose wrote:
> 110s From it/q:
> 110s  ERROR SCS has a valid response
> 110s  ERROR TAP query with pgsphere yields plausible result

Interesting -- this fails because the server that's being tested
does not come up because:

  module 'PIL.Image' has no attribute 'ANTIALIAS'

And indeed, it does not:

  >>> from PIL import Image
  >>> Image.ANTIALIAS
  Traceback (most recent call last):
File "", line 1, in 
  AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'

Now... this seems to be a fairly breaking change (or at least I
suspect there's a lot of code with Image.ANTIALIAS out there).
However, when looking for resize or ANTIALIAS in the upstream
changelog, I don't see it mentioned:
https://github.com/python-pillow/Pillow/blob/main/CHANGES.rst

That made me curious; ANTIALIAS as an alias of LANCZOS was dropped in
upstream commit f8e4e9c2dd94c6f4789639dd891b8a6d5fb16e14 with the
terse commit message "Added enums", where there's this:

  ...
  -LANCZOS = ANTIALIAS = 1

  -_filters_support = {BOX: 0.5, BILINEAR: 1.0, HAMMING: 1.0, BICUBIC: 2.0, 
LANCZOS: 3.0}
  +# resampling filters (also defined in Imaging.h)
  +class Resampling(IntEnum):
  +NEAREST = 0
  +BOX = 4
  +BILINEAR = 2
  +HAMMING = 5
  +BICUBIC = 3
  +LANCZOS = 1

Whether dropping the widely-documented ANTIALIAS alias was done
deliberately or not I can't say.  And hence I'll not decide whether or
not that's worth an upstream bug.  Instead, I'lljust move to LANCZOS
in DaCHS.

DaCHS users: if you urgently need the package on unstable, please use
our beta repo (https://soft.g-vo.org/repo) for the time being.
Release 2.8 wasn't our best one anyway.  Release 2.9 ought to come
around October-ish anyhow, at which time I'll close this bug (or
should be reminded to close it).

Processed: Re: ca-certificates-java: incorrect "Breaks:" versions about ubuntu

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1040675 [ca-certificates-java] ca-certificates-java: incorrect "Breaks:" 
versions about ubuntu
Severity set to 'important' from 'serious'

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

Bug#1040521: tpm2-tss: FTBFS (test failures)

[Ying-Chun Liu (PaulLiu)]

Hi Bastian,

Thanks for adding more information here.

I've looked into the problem. The s390x should be the endian problem.
While the rest (i386, armel, armhf) is due to it is 32-bits.

According to the build log:
https://buildd.debian.org/status/fetch.php?pkg=tpm2-tss=armhf=4.0.1-1=1688685120=0

The test failed at Test: tcti_libtpms_remap_state_posix_fallocate_fail_test

We can look into the code.
First.
At test/unit/tcti-libtpms.c:1097, expect_value(TPMLIB_Process, cmd, cmd);
And cmd is an array.
unsigned char cmd[] = {0x80, 0x01, 0x00, 0x00, 0x00, 0x0c, 0x00, 0x00, 0x01
, 0x44, 0x00, 0x00};

At test/unit/tcti-libtpms.c:136, check_expected_ptr(cmd);

So the problem is actually at test/unit/tcti-libtpms.c:1097.
Because it tries to convert a pointer to integer.
The expect_value() of CMocka is expect_value(#func, #para, LargestIntegralType 
val)
So that cmd is converted to Integral Type.
I think we might want to use expect_memory() instead?
expect_memory(#func, #para, void* mem, size_t size)
So that cmd is pointer rather than converted to int.

Yours,
Paul



OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1040675: ca-certificates-java: incorrect "Breaks:" versions about ubuntu

[Matthias Klose]

Control: severity -1 important

openjdk-18 has been removed from testing in November 2022, and I now filed a bug 
report to remove it from unstable (#1040789). It is unmaintained upstream, and 
superseded by newer OpenJDK releases.


The versions used in these breaks work both for Debian and Ubuntu. If there are 
mistakes made, please tell them. Shouting "this is Debian" doesn't help.


I'll close this issue once openjdk-18 is also removed from unstable.

Bug#1040785: marked as done (reportbug: ID in /etc/machine-id and /var/lib/dbus/machine-id mismatch on fresh debian 12 installation)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jul 2023 10:57:03 -0400
with message-id 

and subject line Re: Bug#1040785: reportbug: ID in /etc/machine-id and 
/var/lib/dbus/machine-id mismatch on fresh debian 12 installation
has caused the Debian Bug report #1040785,
regarding reportbug: ID in /etc/machine-id and /var/lib/dbus/machine-id 
mismatch on fresh debian 12 installation
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.)


-- 
1040785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 12.0.0
Severity: serious
Tags: d-i
Justification: https://wiki.debian.org/MachineId

Dear Maintainer,

   * What led up to the situation?
 - Installing debian 12 via the installer

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 - Normal install (also preseed install)

   * What was the outcome of this action?
 - After installation was finished and the system has been restarted the 
files "/etc/machine-id" and "/var/lib/dbus/machine-id" are not linked in any 
way (no soft or hardlink) and the ID inside the files differ from each other.

   * What outcome did you expect instead?
 - "cat /etc/machine-id /var/lib/dbus/machine-id" should return the same ID 
two times

   * Workaround
 - rm /etc/machine-id /var/lib/dbus/machine-id && dbus-uuidgen 
--ensure=/etc/machine-id && dbus-uuidgen --ensure


-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /root/.reportbugrc:
reportbug_version "12.0.0"
mode standard
ui text
realname "yogg"
email "deb...@x-net.at"
no-check-uid
smtphost "x-zimbra03.x"

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

Kernel: Linux 6.1.0-10-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 reportbug depends on:
ii  apt2.6.1
ii  python33.11.2-1+b1
ii  python3-reportbug  12.0.0
ii  sensible-utils 0.0.17+nmu1

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail
ii  debconf   1.5.82
pn  debsums   
pn  default-mta | postfix | exim4 | mail-transport-agent  
pn  dlocate   
pn  emacs-bin-common  
ii  file  1:5.44-3
pn  gnupg | pgp   
pn  python3-urwid 
pn  reportbug-gtk 
pn  xdg-utils 

Versions of packages python3-reportbug depends on:
ii  apt2.6.1
ii  file   1:5.44-3
ii  python33.11.2-1+b1
ii  python3-apt2.6.0
ii  python3-debian 0.1.49
ii  python3-debianbts  4.0.1
ii  python3-requests   2.28.1+dfsg-1
ii  sensible-utils 0.0.17+nmu1

python3-reportbug suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Jul 10, 2023 at 10:09 AM yogg  wrote:
>
> Package: reportbug
> Version: 12.0.0
> Severity: serious
> Tags: d-i
> Justification: https://wiki.debian.org/MachineId
>
> Dear Maintainer,
>
>* What led up to the situation?
>  - Installing debian 12 via the installer
>
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>  - Normal install (also preseed install)
>
>* What was the outcome of this action?
>  - After installation was finished and the system has been restarted the 
> files "/etc/machine-id" and "/var/lib/dbus/machine-id" are not linked in any 
> way (no soft or hardlink) and the ID inside the files differ from each other.
>
>* What outcome did you expect instead?
>  - "cat /etc/machine-id /var/lib/dbus/machine-id" should return the same 
> ID two times
>
>* Workaround
>  - rm /etc/machine-id /var/lib/dbus/machine-id && dbus-uuidgen 
> --ensure=/etc/machine-id && dbus-uuidgen --ensure


this is not the right package nor i'm sure which one to assign it to,
please seek help via https://www.debian.org/support

closing

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: 

Bug#1039684: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2023-25515, CVE-2023-25516)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jul 2023 14:46:26 +
with message-id 
and subject line Bug#1039684: fixed in nvidia-graphics-drivers-tesla-470 
470.199.02-1
has caused the Debian Bug report #1039684,
regarding nvidia-graphics-drivers-tesla-470: CVE-2023-25515, CVE-2023-25516
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.)


-- 
1039684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team 
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-25515, 
CVE-2023-25516
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-25515, 
CVE-2023-25516
Control: tag -3 + wontfix
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-25515, 
CVE-2023-25516
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-25515, 
CVE-2023-25516
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-25515, 
CVE-2023-25516
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-25515, 
CVE-2023-25516
Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2023-25515, 
CVE-2023-25516
Control: found -8 515.48.07-1
Control: found -8 525.60.13-1
Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1
Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2023-25515, 
CVE-2023-25516
Control: found -9 520.56.06-1
Control: found -9 525.85.12-1
Control: found -9 530.30.02-1
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1
Control: found -1 520.56.06-1
Control: found -1 525.53-1
Control: found -1 530.30.02-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5468

CVE-2023-25515  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability where unexpected untrusted data is parsed, which may
lead to code execution, denial of service, escalation of privileges,
data tampering, or information disclosure.

CVE-2023-25516  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where an unprivileged user can
cause an integer overflow, which may lead to information disclosure and
denial of service.

Linux Driver Branch CVE IDs Addressed
R535, R525, R470, R450  CVE-2023-25515, CVE-2023-25516

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R535All driver versions prior to 535.54.03  535.54.03
R525All driver versions prior to 525.125.06 525.125.06
R470All driver versions prior to 470.199.02 470.199.02
R450All driver versions prior to 450.248.02 450.248.02

Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-470
Source-Version: 470.199.02-1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla-470 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: Mon, 10 Jul 2023 15:06:22 +0200
Source: nvidia-graphics-drivers-tesla-470
Architecture: source
Version: 470.199.02-1

Processed: Re: Bug#858337: apt-show-versions: wrong output when version of an installed package is missing from the Packages files

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #858337 [apt-show-versions] apt-show-versions gives unreliable information
Added tag(s) moreinfo.

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

Bug#858337: apt-show-versions: wrong output when version of an installed package is missing from the Packages files

[Christoph Martin]

Control: tags -1 + moreinfo

Hi Vincent,

Am 05.07.23 um 12:13 schrieb Vincent Lefevre:

Control: retitle -1 apt-show-versions gives unreliable information
Control: severity -1 grave



I still can not reproduce your problem.

Please try to find out, which value is missing in a Packages file, which 
triggers this error, so that I can reproduce the problem.


Regards
Christoph


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1040785: reportbug: ID in /etc/machine-id and /var/lib/dbus/machine-id mismatch on fresh debian 12 installation

[yogg]

Package: reportbug
Version: 12.0.0
Severity: serious
Tags: d-i
Justification: https://wiki.debian.org/MachineId

Dear Maintainer,

   * What led up to the situation?
 - Installing debian 12 via the installer

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 - Normal install (also preseed install)

   * What was the outcome of this action?
 - After installation was finished and the system has been restarted the 
files "/etc/machine-id" and "/var/lib/dbus/machine-id" are not linked in any 
way (no soft or hardlink) and the ID inside the files differ from each other.

   * What outcome did you expect instead?
 - "cat /etc/machine-id /var/lib/dbus/machine-id" should return the same ID 
two times

   * Workaround
 - rm /etc/machine-id /var/lib/dbus/machine-id && dbus-uuidgen 
--ensure=/etc/machine-id && dbus-uuidgen --ensure


-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /root/.reportbugrc:
reportbug_version "12.0.0"
mode standard
ui text
realname "yogg"
email "deb...@x-net.at"
no-check-uid
smtphost "x-zimbra03.x"

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

Kernel: Linux 6.1.0-10-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 reportbug depends on:
ii  apt2.6.1
ii  python33.11.2-1+b1
ii  python3-reportbug  12.0.0
ii  sensible-utils 0.0.17+nmu1

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail
ii  debconf   1.5.82
pn  debsums   
pn  default-mta | postfix | exim4 | mail-transport-agent  
pn  dlocate   
pn  emacs-bin-common  
ii  file  1:5.44-3
pn  gnupg | pgp   
pn  python3-urwid 
pn  reportbug-gtk 
pn  xdg-utils 

Versions of packages python3-reportbug depends on:
ii  apt2.6.1
ii  file   1:5.44-3
ii  python33.11.2-1+b1
ii  python3-apt2.6.0
ii  python3-debian 0.1.49
ii  python3-debianbts  4.0.1
ii  python3-requests   2.28.1+dfsg-1
ii  sensible-utils 0.0.17+nmu1

python3-reportbug suggests no packages.

-- no debconf information

Bug#1040521: tpm2-tss: FTBFS (test failures)

[Bastian Germann]

Control: forwarded -1 https://github.com/tpm2-software/tpm2-tss/issues/2531

The big endian problem on s390 is already reported upstream.
This is new code in v4.

Processed: Re: tpm2-tss: FTBFS (test failures)

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/tpm2-software/tpm2-tss/issues/2531
Bug #1040521 [src:tpm2-tss] tpm2-tss: FTBFS (test failures)
Set Bug forwarded-to-address to 
'https://github.com/tpm2-software/tpm2-tss/issues/2531'.

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

Bug#1040521: tpm2-tss: FTBFS (test failures)

[Bastian Germann]

I have just noticed that the build dependency libtpms-dev was added in 4.0.1-1.
When I install it on bookworm, the build fails as well.

So to work around just revert
https://salsa.debian.org/debian/tpm2-tss/-/commit/4c88e0a46685632751e7501a91d9ba66a042e3e2

Bug#1040777: libcrypt-xxhash-perl: Baseline violation on x86 and FTBFS everywhere else

[Adrian Bunk]

Source: libcrypt-xxhash-perl
Version: 0.06-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=libcrypt-xxhash-perl=0.06-1

...
   dh_auto_build -a
/usr/bin/perl Build
Building Crypt-xxHash
c++ -I. -Isrc -Iext/xxHash -I. -Isrc 
-I/usr/lib/powerpc64le-linux-gnu/perl/5.36/CORE -fPIC -D_REENTRANT 
-D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -msse2 -msse4.2 -DCPP=1 
-std=c++17 -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing 
-pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -o ./ext/xxHash/xxh_x86dispatch.o 
./ext/xxHash/xxh_x86dispatch.c
c++: error: unrecognized command-line option ‘-msse2’
c++: error: unrecognized command-line option ‘-msse4.2’
error building ./ext/xxHash/xxh_x86dispatch.o from 
'./ext/xxHash/xxh_x86dispatch.c' at 
/usr/share/perl/5.36/ExtUtils/CBuilder/Base.pm line 185.
dh_auto_build: error: /usr/bin/perl Build returned exit code 2
make: *** [debian/rules:6: binary-arch] Error 25


Please remove the -msse parameters from Build.PL.

Bug#1040776: python-biopython: autopkgtest regression

[Adrian Bunk]

Source: python-biopython
Version: 1.80+dfsg-5
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-biopython/35614880/log.gz

...
580s ==
580s ERROR: test_diagram_via_methods_pdf 
(test_GenomeDiagram.DiagramTest.test_diagram_via_methods_pdf)
580s Construct and draw PDF using method approach.
580s --
580s Traceback (most recent call last):
580s   File 
"/tmp/autopkgtest-lxc.aeaunhwi/downtmp/autopkgtest_tmp/Tests/test_GenomeDiagram.py",
 line 1001, in test_diagram_via_methods_pdf
580s gdd.write(output_filename, "PDF")
580s   File 
"/usr/lib/python3/dist-packages/Bio/Graphics/GenomeDiagram/_Diagram.py", line 
244, in write
580s return _write(self.drawing, filename, output, dpi=dpi)
580s^^^
580s   File "/usr/lib/python3/dist-packages/Bio/Graphics/__init__.py", line 46, 
in _write
580s from reportlab.graphics import renderPS, renderPDF, renderSVG
580s   File "/usr/lib/python3/dist-packages/reportlab/graphics/renderSVG.py", 
line 22, in 
580s from .renderPM import _getImage
580s   File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", 
line 20, in 
580s from .utils import setFont as _setFont, RenderPMError
580s   File "/usr/lib/python3/dist-packages/reportlab/graphics/utils.py", line 
9, in 
580s from . _renderPM import makeT1Font
580s ModuleNotFoundError: No module named 'reportlab.graphics._renderPM'
...
582s autopkgtest [22:48:48]: test full_suite:  - - - - - - - - - - results - - 
- - - - - - - -
582s autopkgtest [22:48:48]:  summary
582s dependencies FAIL non-zero exit status 1
582s full_suite   FAIL non-zero exit status 1

Bug#1040774: msolve FTBFS on 32bit: test failure and hang

[Adrian Bunk]

Source: msolve
Version: 0.5.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=msolve=0.5.0-1

...
make  check-TESTS
make[3]: Entering directory '/<>'
make[4]: Entering directory '/<>'
PASS: fglm_build_matrixn_radical_shape-31
PASS: neogb_io
PASS: fglm_build_matrixn_nonradical_shape-31
PASS: fglm_build_matrixn_nonradical_radicalshape-31
FAIL: test/diff/diff_elim-qq.sh
PASS: test/diff/diff_elim-31.sh
PASS: test/diff/diff_F4SAT-31.sh
FAIL: test/diff/diff_kat6-31.sh
FAIL: test/diff/diff_eco11-31.sh
E: Build killed with signal TERM after 150 minutes of inactivity

Processed: tagging 1038402, found 1040675 in 20230707, tagging 1037467, tagging 1040746, fixed 1040746 in 44.0-2

[Debian Bug Tracking System]

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

> tags 1038402 + sid trixie
Bug #1038402 [src:openorienteering-mapper] openorienteering-mapper: FTBFS with 
Qt ≥ 5.15.9: QPainterTest failures
Added tag(s) trixie and sid.
> found 1040675 20230707
Bug #1040675 [ca-certificates-java] ca-certificates-java: incorrect "Breaks:" 
versions about ubuntu
Marked as found in versions ca-certificates-java/20230707.
> tags 1037467 + sid trixie
Bug #1037467 {Done: Debian FTP Masters } 
[src:ruby-gollum-lib] ruby-gollum-lib not compatible with ruby-rouge 4.1
Bug #1040405 {Done: Debian FTP Masters } 
[src:ruby-gollum-lib] ruby-gollum-lib: incompatible with newer ruby-rouge
Added tag(s) trixie and sid.
Added tag(s) sid and trixie.
> tags 1040746 + sid trixie
Bug #1040746 [src:gnome-photos] ftbfs in gnome-photos with recent babl
Added tag(s) sid and trixie.
> fixed 1040746 44.0-2
Bug #1040746 [src:gnome-photos] ftbfs in gnome-photos with recent babl
Marked as fixed in versions gnome-photos/44.0-2.
> thanks
Stopping processing here.

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

Bug#1040521: tpm2-tss: FTBFS (test failures)

[Bastian Germann]

It is obviously a signedness issue on 32 bit systems.

3.2.1-3 has the same issue on sid. So this has to be caused by a post-bookworm update of a different 
component.

Bug#1040773: indi-pentax needs new binaries uploaded for the libraw transition

[Adrian Bunk]

Source: indi-pentax
Version: 1.0+20221221102411-1
Severity: serious
Tags: ftbfs trixie sid

https://buildd.debian.org/status/package.php?p=indi-pentax

One option would be a new source upload (with binaries).

Processed: RM: golang-gitaly-proto -- ROM; rc-buggy, no longer needed for gitlab-shell

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:golang-gitaly-proto
Bug #1040772 [ftp.debian.org] RM: golang-gitaly-proto -- ROM; rc-buggy, no 
longer needed for gitlab-shell
Added indication that 1040772 affects src:golang-gitaly-proto
> affects -1 + src:golang-gitaly-proto
Bug #1040772 [ftp.debian.org] RM: golang-gitaly-proto -- ROM; rc-buggy, no 
longer needed for gitlab-shell
Ignoring request to set affects of bug 1040772 to the same value previously set
> block 1033705 by -1
Bug #1033705 [src:golang-gitaly-proto] golang-gitaly-proto: autopkgtest 
regression: test dependency ruby-gitaly-proto doesn't exist
1033705 was not blocked by any bugs.
1033705 was not blocking any bugs.
Added blocking bug(s) of 1033705: 1040772

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

Bug#1040771: openjdk-22 should not be in stable releases

[Adrian Bunk]

Source: openjdk-22
Version: 22~3ea-1
Severity: serious

openjdk-22 should not be in stable releases,
this bug should keep it out of testing.

Processed: closing 1039945

[Debian Bug Tracking System]

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

> close 1039945 4.0.4-6
Bug #1039945 [src:python-reportlab] python-reportlab: binary-any FTBFS
Marked as fixed in versions python-reportlab/4.0.4-6.
Bug #1039945 [src:python-reportlab] python-reportlab: binary-any FTBFS
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1040056: spirv-tools breaks spirv-llvm-translator-15 autopkgtest: exactly one input file must be specified.

[Sebastien Bacher]

Hey Michel,

Sorry you are right there, unsure how I went to that conclusion but 
indeed what I wrote before was wrong


Cheers,
Sébastien

Le 10/07/2023 à 12:21, Michel Dänzer a écrit :

On 7/10/23 10:36, Sebastien Bacher wrote:

The issue needs to be fixed in piglit and there is a patch upstream, I've 
reported that as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039592

The spirv-llvm-translator build doesn't use piglit though, does it?



https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/821

However, 'spirv-as -h' still says:

'If no file is specified, [...] then the assembly text is read from standard 
input.'

So this does seem like a spirv-tools bug, and my piglit change is a workaround.

Bug#1040056: spirv-tools breaks spirv-llvm-translator-15 autopkgtest: exactly one input file must be specified.

[Michel Dänzer]

On 7/10/23 10:36, Sebastien Bacher wrote:
> The issue needs to be fixed in piglit and there is a patch upstream, I've 
> reported that as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039592

The spirv-llvm-translator build doesn't use piglit though, does it?


> https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/821

However, 'spirv-as -h' still says:

'If no file is specified, [...] then the assembly text is read from standard 
input.'

So this does seem like a spirv-tools bug, and my piglit change is a workaround.


-- 
Earthling Michel Dänzer|  https://redhat.com
Libre software enthusiast  | Mesa and Xwayland developer

Bug#1040056: [Pkg-opencl-devel] Bug#1040056: spirv-tools breaks spirv-llvm-translator-15 autopkgtest: exactly one input file must be specified.

[Andreas Beckmann]

Does this issue affect spirv-llvm-translator-16, too?
I tried to trigger the corresponding tests (which succeeded), but I'm 
not sure if it really tested the correct setup.


Andreas

Bug#1040635: marked as done (python-wordcloud autopkg tests fail with pillow 10.0.0)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jul 2023 09:21:17 +
with message-id 
and subject line Bug#1040635: fixed in python-wordcloud 1.9.2+dfsg-1
has caused the Debian Bug report #1040635,
regarding python-wordcloud autopkg tests fail with pillow 10.0.0
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.)


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

Package: src:python-wordcloud
Version: 1.8.2.2+dfsg-1
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-wordcloud/35498779/log.gz

[...]
101s autopkgtest [17:25:06]: test run-unit-test: [---
102s Traceback (most recent call last):
102s   File "/tmp/autopkgtest-lxc.0c3pi9b6/downtmp/autopkgtest_tmp/foo.py", line 
14, in 

102s wc.generate(text)
102s   File "/usr/lib/python3/dist-packages/wordcloud/wordcloud.py", line 639, 
in generate

102s return self.generate_from_text(text)
102s^
102s   File "/usr/lib/python3/dist-packages/wordcloud/wordcloud.py", line 621, 
in generate_from_text

102s self.generate_from_frequencies(words)
102s   File "/usr/lib/python3/dist-packages/wordcloud/wordcloud.py", line 508, 
in generate_from_frequencies

102s box_size = draw.textsize(word, font=transposed_font)
102s^
102s AttributeError: 'ImageDraw' object has no attribute 'textsize'
103s autopkgtest [17:25:08]: test run-unit-test: ---]
--- End Message ---
--- Begin Message ---
Source: python-wordcloud
Source-Version: 1.9.2+dfsg-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-wordcloud 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: Mon, 10 Jul 2023 10:58:08 +0200
Source: python-wordcloud
Architecture: source
Version: 1.9.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andreas Tille 
Closes: 1040635
Changes:
 python-wordcloud (1.9.2+dfsg-1) unstable; urgency=medium
 .
   * New upstream version
 Closes: #1040635
   * Fix filename of download tarball
Checksums-Sha1:
 2c3950dc783f738b4f4ce9ba01ee139d8df16746 2327 python-wordcloud_1.9.2+dfsg-1.dsc
 6bc1fa4071c0edfffb2bff1a404d65208f3f3d63 38588 
python-wordcloud_1.9.2+dfsg.orig.tar.xz
 d9458572b9f212bdde78b9f2aebae811bb9cc9f3 5144 
python-wordcloud_1.9.2+dfsg-1.debian.tar.xz
 ee1f944035a9de8f97b76df2ee739566b2545345 9755 
python-wordcloud_1.9.2+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 f3fb3a521303b8996585f1c8658098a42fa9b8f3f221ec954874de056b44e515 2327 
python-wordcloud_1.9.2+dfsg-1.dsc
 4d342583e0f6c8aa4dce72a7b5c54ab75b76587e779b2f940c6d688c10cc5e6f 38588 
python-wordcloud_1.9.2+dfsg.orig.tar.xz
 5c0ef554283a047f86184945c4bfedd0f46aa86b3b54ae27ea3f02ab01f5b737 5144 
python-wordcloud_1.9.2+dfsg-1.debian.tar.xz
 030260c8e8e4fd6d6b20d9a33675112b5abfc1b92047d57b44cdc6c2c513168d 9755 
python-wordcloud_1.9.2+dfsg-1_amd64.buildinfo
Files:
 a3cc2d8a2910b3e9027fefddd018af67 2327 python optional 
python-wordcloud_1.9.2+dfsg-1.dsc
 106c42091583db81b85060e9907d0376 38588 python optional 
python-wordcloud_1.9.2+dfsg.orig.tar.xz
 8803d93aaef6b0cf39a3914842c887b5 5144 python optional 
python-wordcloud_1.9.2+dfsg-1.debian.tar.xz
 8e90fbf74248d9383f086540dace0288 9755 python optional 
python-wordcloud_1.9.2+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSrytoRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHgPQ//Z0W0h4j0oTdfpJRqiTD2W5Zd8z0c5a0r
iON00f+d1r2TdQvWEJa9Ieb0wM8CeOmbxs5E7qBpd15n1cm6I2JITNNgh5VNSNp8
NDzubaC1KyKlXuUQYimitQKMcbBzvTLCYI8uZc2dVSPGLnANaINICvQCtjV7S04o
de502HDqDQDrE5Euns2/U6Yw/ER+RwI+L5wTwaq9ksOtceO+NdCA7CJdryK1Jm95
nLiKv8OMyxYFT52g8h0NIryJj8cG0gkJHeKbtns8Xv1lyv5o+2zZ10FaNzMFRGfG
SF6uGFTulV3RtIMAB2DF9bDUkXx8h4dCIequJDLF5cHAIWs+4dJuAkLC/9bJP+07

Bug#1040702: marked as done (impossible to install: depends on missing packages)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jul 2023 09:21:24 +
with message-id 
and subject line Bug#1040702: fixed in rust-log 0.4.19-2
has caused the Debian Bug report #1040702,
regarding impossible to install: depends on missing packages
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.)


-- 
1040702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-log-dev
Version: 0.4.19-1
Severity: grave

depends on several unavailable packages.

 - Jonas
--- End Message ---
--- Begin Message ---
Source: rust-log
Source-Version: 0.4.19-2
Done: Sylvestre Ledru 

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated rust-log 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: Mon, 10 Jul 2023 10:34:22 +0200
Source: rust-log
Architecture: source
Version: 0.4.19-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Sylvestre Ledru 
Closes: 1040702
Changes:
 rust-log (0.4.19-2) unstable; urgency=medium
 .
   * Package log 0.4.19 from crates.io using debcargo 2.6.0
   * Unbreak the package by disable sval & value-bag until the new packages
 have been accepted (they are in NEW)
 (Closes: #1040702)
Checksums-Sha1:
 f2ea188f65ee7c9ff2a02f125f73553ecb32af86 2196 rust-log_0.4.19-2.dsc
 1891a9b2ca8d3e03c0c429a20f8b1b872f1e5403 4384 rust-log_0.4.19-2.debian.tar.xz
 dcf68e3406cf17cb828abe96056a125226507f2d 9757 
rust-log_0.4.19-2_source.buildinfo
Checksums-Sha256:
 927f42f3d498d9c2375a77449b32792d61ff76c6f91442f28c328192ff4246e7 2196 
rust-log_0.4.19-2.dsc
 185227455e6b8faa77de056d7ffec012344d8df0769e8fda3b82906adb491356 4384 
rust-log_0.4.19-2.debian.tar.xz
 84bfe12a0d4244bc7e7959145e4472c2cee7a6c42a91460027bd5954a4ee2384 9757 
rust-log_0.4.19-2_source.buildinfo
Files:
 c9f24d6f291f7aa330cec7d73be8a10b 2196 rust optional rust-log_0.4.19-2.dsc
 3330302ac48238b0a44cd6204e6e2bd1 4384 rust optional 
rust-log_0.4.19-2.debian.tar.xz
 562c6b18f5b4a288de750aa7b303faad 9757 rust optional 
rust-log_0.4.19-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmSrwpcACgkQfmUo2nUv
G+GHqA//eYz1T8tusT1+c1LlTXENT4Gsq4uKKdeTpmGX2Dch6f3uppjxbWw+KuDm
R9qhuAVpovN+wCdvptplgg++8f3XUWeQj0KMm/Qb7x5Tioxgce77J8CvO4+7F16C
MwG4GDKuKP/A4D8uzcnL35XbQNReVL9Z0Wa8cDARhuAbiM6aFS3s+Lg7q+d9G0fF
qtL9NeTwyeiwtKABrczISl8B2H7kF6K9yEmY/0J2dPSjE84CH/ycA7YNFqKx4ru3
blQQymK0qTkKlGkN9GeEFehBpvc4JylN9j6KuYFgs4PKy4hJSgav55Ws+yUIMNsB
WNtB0NjlHnIZBbu+JijXOFbVbj8MwaBRS5CY9hGUyFvbpV5CF7+QVHhA4D7B1Cv/
Dk0pVzTqdFh66IMoHsyZ0MOH+PMQjaFq/Tv2yNLXvTmR1+jUzDlQifuL6G07+8HQ
MY9ZeU+cHchDQjIc7rzXnMZWZZjpzwPzrTobCFs8QmF0Y4Vy/caDbXQmVRJrtC8C
rAU1peip5MTngk8Bs1Qep3J23zYYpdepSqSYZxyskAKWGHSpd2q3BPqQnf6/XACN
0kXsdsOmDPKFX5uHmALUVbVgtp/8QczJ/0JUNS5N40id0VQ7Db4rrJCdctbyGa96
0qGZq5tFjvxgx9m4RTXhM/R1r2akWDxGuAtw/lUy4V+15w0ccFU=
=9x1k
-END PGP SIGNATURE End Message ---

Processed: bug 999957 is forwarded to https://github.com/dlundquist/sniproxy/issues/392

[Debian Bug Tracking System]

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

> forwarded 57 https://github.com/dlundquist/sniproxy/issues/392
Bug #57 [src:sniproxy] sniproxy: depends on obsolete pcre3 library
Set Bug forwarded-to-address to 
'https://github.com/dlundquist/sniproxy/issues/392'.
> thanks
Stopping processing here.

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

Bug#1040056: spirv-tools breaks spirv-llvm-translator-15 autopkgtest: exactly one input file must be specified.

[Sebastien Bacher]

The issue needs to be fixed in piglit and there is a patch upstream, 
I've reported that as 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039592


https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/821

Bug#1024499: marked as done (pybdsf: FTBFS with Python 3.11 as a supported version)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jul 2023 07:38:59 +
with message-id 
and subject line Bug#1024499: fixed in pybdsf 1.10.3-1
has caused the Debian Bug report #1024499,
regarding pybdsf: FTBFS with Python 3.11 as a supported version
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.)


-- 
1024499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pybdsf
Version: 1.10.1-1
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.11

Hi Maintainer

pybdsf FTBFS during the recent rebuild adding Python 3.11 as a
supported version [1].  I've copied what I hope is the relevant part
of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=pybdsf


==
ERROR: bdsf (unittest.loader._FailedTest.bdsf)
--
ImportError: Failed to import test module: bdsf
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 440, in _find_test_path
package = self._get_module_from_name(name)
  
  File "/usr/lib/python3.11/unittest/loader.py", line 350, in
_get_module_from_name
__import__(name)
  File "/<>/.pybuild/cpython3_3.11/build/bdsf/__init__.py",
line 21, in 
from .collapse import Op_collapse
  File "/<>/.pybuild/cpython3_3.11/build/bdsf/collapse.py",
line 11, in 
from . import _cbdsm
SystemError: initialization of _cbdsm raised unreported exception
--- End Message ---
--- Begin Message ---
Source: pybdsf
Source-Version: 1.10.3-1
Done: Ole Streicher 

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated pybdsf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 22 Jun 2023 20:57:54 +0200
Source: pybdsf
Architecture: source
Version: 1.10.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Maintainers 

Changed-By: Ole Streicher 
Closes: 1024499
Changes:
 pybdsf (1.10.3-1) unstable; urgency=medium
 .
   [Bastian Germann]
   * New upstream version 1.10.3
   * Rediff patches
 .
   [ Ole Streicher ]
   * Call dh_numpy
   * Update d/watch
   * Fix build issue with Python 3.11 (Closes: #1024499)
   * Push Standards-Version to 4.6.2. No changes needed
Checksums-Sha1:
 bf2bff527c039bf3fb895799a8376880e6b3b553 2075 pybdsf_1.10.3-1.dsc
 50ea906381d65c4840527661f080b03606139a22 7809862 pybdsf_1.10.3.orig.tar.gz
 499b602e7e2b13ff7d672ce8d9ed49bbf80f3229 5148 pybdsf_1.10.3-1.debian.tar.xz
Checksums-Sha256:
 51f3244697f7dca36b43cee1ee3a64c530a736ad68d56c5dc12f2723e622d7a5 2075 
pybdsf_1.10.3-1.dsc
 cb0eea6349c30365503cca58f2e5e7f255725488b99188bc0859a1f9ee7264b2 7809862 
pybdsf_1.10.3.orig.tar.gz
 26b6c92141f7ecf9b60ce292628bcd980f7bbffa795e19c97e552c2c100f0872 5148 
pybdsf_1.10.3-1.debian.tar.xz
Files:
 cf5fd2508b9093466ade7fce2f249b62 2075 python optional pybdsf_1.10.3-1.dsc
 76549eb3fb1f9a9a095696ab1b3e5fe2 7809862 python optional 
pybdsf_1.10.3.orig.tar.gz
 f66366054bbecd4a3fd42e4087c6e258 5148 python optional 
pybdsf_1.10.3-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmSrrvsACgkQcRWv0HcQ
3PeOQQ/+PhrrJW12B+fXwg/CjWR6an6whX+fFYc/qo8T/pCWUFLwFzIl1WjKwoUV
VqqwKuE9j18tFp5RLxG9wO+2E8143kt3qwdJxKxyphsWveLogt8skq9eMj2AF7Ra
b6J81YRrpROIcV69EpcgRH6q3l6n3YTO52Gln0/nwE7nmj/aHYfkSvO9jjTSwL+8
UyNjewigshC6B7NAgM2tR8XiviXgt33FgkhvGNF1xvw/yJb2kx82/m256KyzLwjd
dZXapozZCa8U7zbxgFI9CaYEVYpzErcHmI/Iy7J/FqyDvahK5fkalHMawp0XMmHK
9uj3MFNZhV/6tKX+hiUxCGrlGFxxGMSrw4FDsq9mSrz0rFYNTtOkmkiO2xU32DKK
sO4nQylgxIKVJAEPPFMzQaG6pGajmu8dH677rcGbZe/TebdO4F4nKZCyqM7tEN+x
9n5w0/03NUS3eYUdhjMZbO4IMnJYVfgmujKaqlHd/BjF5E3M0GrBVcuW4L5AP5kP
76zkdm7IMHfcD0INlXkXWQUzqn2qLL3AdI5Szt3IUHJ4XQH0ehr1lAt6rJUaZGvV
HeXwyfBAEVTHoa2U4XoBitpAd+RUUlSO8yaxYucE11sXlIip9aqToFeZkb88LIJv

Bug#1037296: marked as done (manderlbot: reproducible-builds: Different path to erl in /usr/bin/manderlbot)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jul 2023 07:38:23 +
with message-id 
and subject line Bug#1037296: fixed in manderlbot 0.9.3-2
has caused the Debian Bug report #1037296,
regarding manderlbot: reproducible-builds: Different path to erl in 
/usr/bin/manderlbot
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.)


-- 
1037296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: manderlbot
Severity: serious
Justification: TC resolution #994388
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: usrmerge
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The path to erl is embedded differently in /usr/bin/manderlbot depending
on if it was built on a usrmerge vs. non-usrmerge system:

  
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/manderlbot.html

  ERL=/usr/bin/erl
  vs.
  ERL=/bin/erl

The attached patch fixes this by passing the path to ERL in a
debian/rules dh_auto_configure override. The path in /usr/bin is
compatible with both usrmerge and non-usrmerge systems.

According to my local tests, with this patch applied manderlbot should
build reproducibly on tests.reproducible-builds.org once it migrates to
testing! Unfortunately, there are other issues with build paths which
are only tested in unstable and experimental.

Thanks for maintaining manderlbot!

live well,
  vagrant
From 1d8e42b99a87810397cd1c50c36c79d545192575 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sat, 10 Jun 2023 07:10:24 -0700
Subject: [PATCH] debian/rules: Specify path to "erl" binary in
 dh_auto_configure override.

Otherwise, the path to "erl" may be hardcoded to a path that only
works on a usrmerge system when built on a usrmerge system.

https://tests.reproducible-builds.org/debian/issues/unstable/paths_vary_due_to_usrmerge_issue.html
---
 debian/rules | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/debian/rules b/debian/rules
index ba8c906..b7c845a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -27,5 +27,8 @@ override_dh_gencontrol:
 	erlang-depends
 	dh_gencontrol
 
+override_dh_auto_configure:
+	dh_auto_configure -- ERL=/usr/bin/erl
+
 .PHONY: override_dh_auto_build override_dh_auto_install \
 	override_dh_gencontrol
-- 
2.39.2



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: manderlbot
Source-Version: 0.9.3-2
Done: Sergei Golovan 

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

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated manderlbot 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: Mon, 10 Jul 2023 09:18:50 +0300
Source: manderlbot
Architecture: source
Version: 0.9.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Erlang Packagers 
Changed-By: Sergei Golovan 
Closes: 1037296
Changes:
 manderlbot (0.9.3-2) unstable; urgency=medium
 .
   * Incorporate the NMU by Holger Levsen.
   * Fix the debian/watch uscan control file.
   * Add patch by Vagrant Cascadian which fixes erl path for usrmerge systems
 (closes: #1037296).
   * Bump debhelper compatibility level to 13.
   * Bump standards version to 4.6.2.
Checksums-Sha1:
 badd2add7cef7b1abcb22efd1ea88bf11ead46d1 1983 manderlbot_0.9.3-2.dsc
 04ef146b74d0a3e2ec0ddd0ee47d9abc684d3cad 10112 manderlbot_0.9.3-2.debian.tar.xz
 2a121813c32b8aa0fafdb7411b442fce98a898ac 9067 
manderlbot_0.9.3-2_amd64.buildinfo
Checksums-Sha256:
 4a1de20d6eba6f1c3039116235973c62bc26a79c000ff8537f241a9a96d3742e 1983 
manderlbot_0.9.3-2.dsc
 246c119b34c2301f9059ae7ae24f175026f9b0e3aa9db245495f87ff0f1e6f94 10112 
manderlbot_0.9.3-2.debian.tar.xz
 f82b03050fda37c30fa9fdf25c0d558c8b253f22fdbd0e96b3ce4fbdb0081e79 9067 
manderlbot_0.9.3-2_amd64.buildinfo
Files:
 4d23785c5a41478b97a4c886e85f6ba8 1983 net optional manderlbot_0.9.3-2.dsc
 6cc442e7d42f1b7231acc24e21c40c16 10112 net optional 
manderlbot_0.9.3-2.debian.tar.xz
 687723483d0c71a8fcc2fce9216f161b 9067 net optional 

Bug#1040763: boswars: binary-any FTBFS

[Adrian Bunk]

Source: boswars
Version: 2.8-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=boswars=2.8-1

...
   dh_install -a
   debian/rules execute_after_dh_install-arch
make[1]: Entering directory '/<>'
# Copy (and rename) an icon to be used as desktop file
mkdir -p debian/boswars/usr/share/pixmaps/
cp units/tank/ico_tank.png debian/boswars/usr/share/pixmaps/boswars.png
rm -f debian/boswars/usr/share/doc/boswars/html/README-SDL.txt
rm -f debian/boswars/usr/share/doc/boswars/html/*copyright*
rm -f debian/boswars/usr/share/doc/boswars/html/gpl3.txt
iconv -f ISO-8859-1 -t UTF-8 units/corpses/unit-corpses.lua -o 
debian/boswars-data/usr/share/games/boswars/units/corpses/unit-corpses.lua
iconv: cannot open output file: No such file or directory
make[1]: *** [debian/rules:26: execute_after_dh_install-arch] Error 1