Bug#1038152: supertuxkart: Supertuxkart does not start - missing NotoColorEmoji.ttf

[Federico]

Package: supertuxkart
Version: 1.4+dfsg-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: matta2...@gmail.com

Dear Maintainer,

after clean apt install, STK does not start.

[info   ] SharedGPUObjects: Hardware Skinning enabled, method: TBO, max bones:
1024
[info   ] ShaderFilesManager: Compiling shader:
/usr/share/games/supertuxkart/data/shaders/screenquad.vert
[info   ] ShaderFilesManager: Compiling shader:
/usr/share/games/supertuxkart/data/shaders/motion_blur.frag
[info   ] ShaderFilesManager: Compiling shader:
/usr/share/games/supertuxkart/data/shaders/lightning.frag
[info   ] ShaderFilesManager: Compiling shader:
/usr/share/games/supertuxkart/data/shaders/primitive2dlist.vert
[info   ] ShaderFilesManager: Compiling shader:
/usr/share/games/supertuxkart/data/shaders/transparent.frag
[info   ] ShaderFilesManager: Compiling shader:
/usr/share/games/supertuxkart/data/shaders/texturedquad.vert
[info   ] ShaderFilesManager: Compiling shader:
/usr/share/games/supertuxkart/data/shaders/uniformcolortexturedquad.frag
[info   ] ShaderFilesManager: Compiling shader:
/usr/share/games/supertuxkart/data/shaders/texturedquad.frag
[info   ] ShaderFilesManager: Compiling shader:
/usr/share/games/supertuxkart/data/shaders/coloredquad.vert
[info   ] ShaderFilesManager: Compiling shader:
/usr/share/games/supertuxkart/data/shaders/coloredquad.frag
[info   ] ShaderFilesManager: Compiling shader:
/usr/share/games/supertuxkart/data/shaders/colortexturedquad.vert
[info   ] ShaderFilesManager: Compiling shader:
/usr/share/games/supertuxkart/data/shaders/colortexturedquad.frag
[info   ] irr_driver: GLSL supported.
[info   ] GUI: Loading skin data from file:
/usr/share/games/supertuxkart/data/skins/peach/stkskin.xml
[fatal  ] [FileManager]: Can not find file 'NotoColorEmoji.ttf' in
'/usr/share/games/supertuxkart/data/ttf/'

Can not find file 'NotoColorEmoji.ttf   ' in
'/usr/share/games/supertuxkart/data/ttf/'


/usr/share/games/supertuxkart/data/ttf> ls -la
total 4588
drwxr-xr-x  2 root root4096 May 29 11:15 .
drwxr-xr-x 20 root root4096 May 29 11:15 ..
lrwxrwxrwx  1 root root  58 Feb 28 23:00 Cantarell-Regular.otf ->
../../../../fonts/opentype/cantarell/Cantarell-Regular.otf
lrwxrwxrwx  1 root root  50 Feb 28 23:00 NotoColorEmoji.ttf ->
../../../../fonts/truetype/noto/NotoColorEmoji.ttf
lrwxrwxrwx  1 root root  61 Feb 28 23:00 NotoNaskhArabicUI-Regular.ttf ->
../../../../fonts/truetype/noto/NotoNaskhArabicUI-Regular.ttf
lrwxrwxrwx  1 root root  58 Feb 28 23:00 NotoSansHebrew-Regular.ttf ->
../../../../fonts/truetype/noto/NotoSansHebrew-Regular.ttf
lrwxrwxrwx  1 root root  61 Feb 28 23:00 NotoSansMalayalam-Regular.ttf ->
../../../../fonts/truetype/noto/NotoSansMalayalam-Regular.ttf
lrwxrwxrwx  1 root root  56 Feb 28 23:00 NotoSansThai-Regular.ttf ->
../../../../fonts/truetype/noto/NotoSansThai-Regular.ttf
-rw-r--r--  1 root root   50384 Oct 31  2022 SigmarOne.otf
-rw-r--r--  1 root root 4626376 Oct 31  2022 wqy-microhei.ttf

/usr/share/games/supertuxkart/data/ttf> ls -la

../../../../fonts/truetype/noto/NotoColorEmoji.ttf
bash: ../../../../fonts/truetype/noto/NotoColorEmoji.ttf: No such file or
directory

Maybe there is a dependency issue, missing a noto package to install
NotoColorEmoji.ttf

Do you mind checking it?

Thanks,


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

Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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 supertuxkart depends on:
ii  libbluetooth3  5.66-1
ii  libc6  2.36-9
ii  libcurl3-gnutls7.88.1-10
ii  libfreetype6   2.12.1+dfsg-5
ii  libgcc-s1  12.2.0-14
ii  libharfbuzz0b  6.0.0+dfsg-3
ii  libjpeg62-turbo1:2.1.5-2
ii  libmbedcrypto7 2.28.3-1
ii  libmcpp0   2.7.2-5
ii  libopenal1 1:1.19.1-2
ii  libpng16-161.6.39-2
ii  libsdl2-2.0-0  2.26.5+dfsg-1
ii  libsqlite3-0   3.40.1-2
ii  libsquish0 1.15-3
ii  libstdc++6 12.2.0-14
ii  libvorbisfile3 1.3.7-1
ii  supertuxkart-data  1.4+dfsg-2
ii  zlib1g 1:1.2.13.dfsg-1

supertuxkart recommends no packages.

supertuxkart suggests no packages.

-- no debconf information

Bug#1037995: marked as done (digimend-dkms: module fails to build for Linux 6.3: error: implicit declaration of function 'hid_is_using_ll_driver')

[Debian Bug Tracking System]

Your message dated Fri, 16 Jun 2023 05:04:27 +
with message-id 
and subject line Bug#1037995: fixed in digimend-dkms 11-3
has caused the Debian Bug report #1037995,
regarding digimend-dkms: module fails to build for Linux 6.3: error: implicit 
declaration of function 'hid_is_using_ll_driver'
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.)


-- 
1037995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digimend-dkms
Version: 11-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts

DKMS make.log for digimend-11 for kernel 6.3.0-1-amd64 (x86_64)
Thu Jun 15 09:51:43 UTC 2023
make -C /lib/modules/6.3.0-1-amd64/build M=/var/lib/dkms/digimend/11/build 
modules
make[1]: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
  CC [M]  /var/lib/dkms/digimend/11/build/hid-kye.o
  CC [M]  /var/lib/dkms/digimend/11/build/hid-uclogic-core.o
  CC [M]  /var/lib/dkms/digimend/11/build/hid-uclogic-rdesc.o
  CC [M]  /var/lib/dkms/digimend/11/build/hid-uclogic-params.o
  CC [M]  /var/lib/dkms/digimend/11/build/hid-polostar.o
  CC [M]  /var/lib/dkms/digimend/11/build/hid-viewsonic.o
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c: In function 
'uclogic_params_init':
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1227:17: error: implicit 
declaration of function 'hid_is_using_ll_driver' 
[-Werror=implicit-function-declaration]
 1227 | || !hid_is_using_ll_driver(hdev, _hid_driver)
  | ^~
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1227:47: error: 
'usb_hid_driver' undeclared (first use in this function); did you mean 
'to_hid_driver'?
 1227 | || !hid_is_using_ll_driver(hdev, _hid_driver)
  |   ^~
  |   to_hid_driver
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1227:47: note: each 
undeclared identifier is reported only once for each function it appears in
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1349:20: warning: this 
statement may fall through [-Wimplicit-fallthrough=]
 1349 | if (bNumInterfaces != 3) {
  |^
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1367:9: note: here
 1367 | case VID_PID(USB_VENDOR_ID_HUION,
  | ^~~~
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.build:257: 
/var/lib/dkms/digimend/11/build/hid-uclogic-params.o] Error 1
make[2]: *** Waiting for unfinished jobs
make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2050: 
/var/lib/dkms/digimend/11/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.3.0-1-amd64'
make: *** [Makefile:25: modules] Error 2


Andreas
--- End Message ---
--- Begin Message ---
Source: digimend-dkms
Source-Version: 11-3
Done: Kentaro Hayashi 

We believe that the bug you reported is fixed in the latest version of
digimend-dkms, 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.
Kentaro Hayashi  (supplier of updated digimend-dkms package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 16 Jun 2023 12:52:28 +0900
Source: digimend-dkms
Architecture: source
Version: 11-3
Distribution: unstable
Urgency: medium
Maintainer: Kentaro Hayashi 
Changed-By: Kentaro Hayashi 
Closes: 1037995
Changes:
 digimend-dkms (11-3) unstable; urgency=medium
 .
   * debian/control
 - Bump standards-version to 4.6.2. No changes are required.
   * debian/patches/support-kernel-6.3.patch
 * Fix FTBFS error with kernel 6.3 or later. (Closes: #1037995)
Checksums-Sha1:
 a610c50347085c50b8be2cf9fd49eec536fec619 2138 digimend-dkms_11-3.dsc
 185abfe01a9bdb1854252f9c3172629db2142ba9 3880 digimend-dkms_11-3.debian.tar.xz
 33841b37448e6c950cb59a465cb6ac23852877f6 5815 
digimend-dkms_11-3_amd64.buildinfo
Checksums-Sha256:
 0530f1f31b3733b05055da084de5fe444859968843934ed2fd0b4971100442cd 

Bug#1037064: maven-verifier depends on downloading sources at build time

[tony mancill]

On Sat, Jun 03, 2023 at 12:58:17PM +0200, gregor herrmann wrote:
> On Fri, 02 Jun 2023 21:40:10 -0700, Steve Langasek wrote:
> 
> > While this is not a build failure, it does mean building the package has a
> > dependency on software outside of main, which I believe is a serious policy
> > violation.
> 
> The network access during build is a policy violation in itself:
> 
> 4.9
> …
> For packages in the main archive, required targets must not
> attempt network access, except, via the loopback interface, to
> services on the build host that have been started by the build.

For posterity, I tested locally using network namespaces and described
here [1].  Specifically:

# create a chroot including the build-deps
# (maybe there's an easier way?)

sudo sbuild-createchroot --no-deb-src --chroot-mode=schroot \
   --chroot-prefix=1037064 \
   
--include=debhelper,default-jdk,junit4,libeclipse-sisu-maven-plugin-java,libmaven-parent-java,libmaven-resolver-transport-http-java,libmaven-shared-utils-java,libmodello-maven-plugin-java,maven-debian-helper
 \
   unstable /data/chroot/1037064-amd64-sbuild http://localhost:3142/debian

# create the namespace
sudo ip netns add no-net

# build
sudo ip netns exec no-net sbuild --no-apt-update --no-apt-upgrade \
--no-apt-distupgrade --no-run-lintian --chroot=1037064-amd64-sbuild

# clean up
/usr/sbin/sbuild-destroychroot 1037064-amd64-sbuild

[1] 
https://wiki.debian.org/sbuild#Disabling_network_access_for_dpkg-buildpackage

Bug#1037064: marked as done (maven-verifier depends on downloading sources at build time)

[Debian Bug Tracking System]

Your message dated Fri, 16 Jun 2023 04:22:00 +
with message-id 
and subject line Bug#1037064: fixed in maven-verifier 1.8.0-2
has caused the Debian Bug report #1037064,
regarding maven-verifier depends on downloading sources at build time
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.)


-- 
1037064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maven-verifier
Version: 1.8.0-1
Severity: serious
Justification: package in main has dependency on external software
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic

Dear maintainers,

maven-verifier 1.8.0-1 has been failing to build in Ubuntu, because its
build-time tests depend on downloading software from the Internet:

[...]
[ERROR] testWithMavenHome(org.apache.maven.it.Embedded3xLauncherTest)  Time 
elapsed: 0.581 s  <<< FAILURE!
java.lang.AssertionError: 
exit code unexpected, build log: 
[INFO] Scanning for projects...
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-shared-components/18/maven-shared-components-18.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for 
org.apache.maven.shared:maven-verifier:1.4-SNAPSHOT: Could not transfer 
artifact org.apache.maven.shared:maven-shared-components:pom:18 from/to central 
(https://repo.maven.apache.org/maven2): transfer failed for 
https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-shared-components/18/maven-shared-components-18.pom
 and 'parent.relativePath' points at wrong local POM @ line 23, column 11
 @ 
[...]

  (https://launchpad.net/ubuntu/+source/maven-verifier/1.8.0-1/+build/26010073)

This fails because Launchpad does not allow network access during package
builds, unlike Debian buildds which usually have network access.

While this is not a build failure, it does mean building the package has a
dependency on software outside of main, which I believe is a serious policy
violation.

libmaven-parent-java ships maven-shared-components-35.pom and maven-verifier
build-depends on libmaven-parent-java.  So perhaps src/test/resources/pom.xml
simply needs updated to point at the current version instead of version 18?

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: maven-verifier
Source-Version: 1.8.0-2
Done: tony mancill 

We believe that the bug you reported is fixed in the latest version of
maven-verifier, 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.
tony mancill  (supplier of updated maven-verifier 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, 15 Jun 2023 20:13:15 -0700
Source: maven-verifier
Architecture: source
Version: 1.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 1037064
Changes:
 maven-verifier (1.8.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Rework tests patch to disable network access (Closes: #1037064)
   * Freshen years in debian/copyright
   * Set Rules-Requires-Root: no in debian/control
Checksums-Sha1:
 2bea4f4d360a67b33526cb25bec54f0c51d8ee44 2244 maven-verifier_1.8.0-2.dsc
 f4fa6106900dd0ec326c13bf0eeaf4ec99d2a05b 4148 
maven-verifier_1.8.0-2.debian.tar.xz
 7eb163709fdd64b128235e18661da9feab9db0d4 13732 
maven-verifier_1.8.0-2_amd64.buildinfo
Checksums-Sha256:
 f1f5a06273f401273b045d22a61a8c815cbed6bfdbb1ee944f5672a8a729076e 2244 
maven-verifier_1.8.0-2.dsc
 617e7096c8031d7ffefb9fa6a512f5905700284d82eace4166751534ed071f56 4148 
maven-verifier_1.8.0-2.debian.tar.xz
 b6c0afd8e9242f0eecba2b67f4233a23a38742fa817286aa10ae0b1422fb2603 13732 
maven-verifier_1.8.0-2_amd64.buildinfo
Files:
 

Processed: change severity

[Debian Bug Tracking System]

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

> severity 172 critical
Bug #172 [src:libapache2-mod-qos] libapache2-mod-qos: depends on obsolete 
pcre3 library
Severity set to 'critical' from 'important'
> thanks
Stopping processing here.

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

Processed: Bug#1037064 marked as pending in maven-verifier

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1037064 [src:maven-verifier] maven-verifier depends on downloading sources 
at build time
Added tag(s) pending.

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

Bug#1037064: marked as pending in maven-verifier

[Tony Mancill]

Control: tag -1 pending

Hello,

Bug #1037064 in maven-verifier 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/java-team/maven-verifier/-/commit/c761ab42ddbdd883306e9d72a27096a2123d0752


Disable tests requiring network access (Closes: #1037064)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1037064

Bug#982685: marked as done (sl-modem: Depends on removed package execstack)

[Debian Bug Tracking System]

Your message dated Fri, 16 Jun 2023 02:59:26 +
with message-id 
and subject line Bug#982685: fixed in sl-modem 2.9.11~20110321-17
has caused the Debian Bug report #982685,
regarding sl-modem: Depends on removed package execstack
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.)


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

Package: sl-modem
Severity: serious

Dear Maintainer,

the prelink, and with it the execstack, package got removed. You do have 
a build-dependency on exec-stack.


Your package is in non-free, so its not as serious as in main, but still 
nice to fix.
Please either drop the b-d or, if you really need it, reintroduce 
execstack (as an own package without the broken prelink part) to use it.


--
bye, Joerg
--- End Message ---
--- Begin Message ---
Source: sl-modem
Source-Version: 2.9.11~20110321-17
Done: أحمد المحمودي (Ahmed El-Mahmoudy) 

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

Debian distribution maintenance software
pp.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated sl-modem package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 16 Jun 2023 03:53:11 +0200
Source: sl-modem
Architecture: source
Version: 2.9.11~20110321-17
Distribution: unstable
Urgency: low
Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy) 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Closes: 982685 1027887
Changes:
 sl-modem (2.9.11~20110321-17) unstable; urgency=low
 .
   [ Debian Janitor ]
   * Set debhelper-compat version in Build-Depends.
   * Fix day-of-week for changelog entries 2.9.11~20080817-2, 2.9.11~20080817-1,
 2.7.10-1.
 .
   [ أحمد المحمودي (Ahmed El-Mahmoudy) ]
   * Update standards version to 4.6.2
   * d/control:
 + Bump to debhelper 13
 + Switch to dh-sequence-dkms in build deps. (Closes: #1027887)
 + Add Testsuite: autopkgtest-pkg-dkms
   Thanks to Andreas Beckmann 
 + Drop execstack from build deps (Closes: #982685)
 + Add Rules-Requires-Root: no
   * d/rules:
 + Drop --with dkms
   Thanks to Andreas Beckmann 
 + Use DEB_HOST_ARCH in debian/rules instead of the incorrect
   DEB_BUILD_ARCH.
   Thanks to Steve Langasek 
 + Use objcopy instead of execstack to set the no-executable-stack state on
   the daemon's closed-source binary on i386.
   Thanks to Steve Langasek 
 + Make the package cross-buildable.
   Thanks to Steve Langasek 
 * d/sl-modem-dkms.dkms: Fix "dkms: line 80: cd: too many arguments"
   New dkms appends CC= variable to the MAKE[0] command, which this package
   treats like an arbitrary shell command. .
   Thanks to Dimitri John Ledkov 
   * Add d/sl-modem-dkms.lintian-overrides
   * Add d/s/lintian-overrides for missing sources of dsplibs.o & amrlibs.o
Checksums-Sha1:
 dcd8ffbd79dbd5041c42bbc042ab719e2d66e1f6 1972 sl-modem_2.9.11~20110321-17.dsc
 0c746b0d763940bd0f6bb3d0d957cc5fe9ff9df9 36860 
sl-modem_2.9.11~20110321-17.debian.tar.xz
 1770b08edc3f75f35187a337b40374d30de1a467 6413 
sl-modem_2.9.11~20110321-17_source.buildinfo
Checksums-Sha256:
 9e5517916357f8f5e7eaa844fb2b66acc0489a1a391f8ea0828523cfbd143dfc 1972 
sl-modem_2.9.11~20110321-17.dsc
 0341d04cf3c772275ddb8dc1795485f00196fc507aa73cd62650ec0ccaaaf594 36860 
sl-modem_2.9.11~20110321-17.debian.tar.xz
 f7ce04d252b630b83fd1a7c555fb8bbd1ccddc6dabdcaa9764b5a810f0b14434 6413 
sl-modem_2.9.11~20110321-17_source.buildinfo
Files:
 2700bf4f90faa6332e47edba8d0b10e5 1972 non-free/misc optional 
sl-modem_2.9.11~20110321-17.dsc
 c4cb369193b256f6c4dd3b97468df289 36860 non-free/misc optional 
sl-modem_2.9.11~20110321-17.debian.tar.xz
 2dd06b4aada85da46793ce176547f812 6413 non-free/misc optional 
sl-modem_2.9.11~20110321-17_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFWBAEBCgBAFiEEggahliCEfm0N+LF2vBlqlO3dobcFAmSLwRQiHGFlbG1haG1v
dWR5QHVzZXJzLnNvdXJjZWZvcmdlLm5ldAAKCRC8GWqU7d2ht4quB/0Uu/cPsy2Y
rM9EJ6hNa8L5lDEQz7Gj6+7l0P8jKQiDM19zEWhKg86aT4NswvRmfEMsUXWco99L

Bug#1027887: marked as done (sl-modem: please switch to B-D: dh-sequence-dkms (or dh-dkms))

[Debian Bug Tracking System]

Your message dated Fri, 16 Jun 2023 02:59:26 +
with message-id 
and subject line Bug#1027887: fixed in sl-modem 2.9.11~20110321-17
has caused the Debian Bug report #1027887,
regarding sl-modem: please switch to B-D: dh-sequence-dkms (or dh-dkms)
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.)


-- 
1027887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sl-modem
Version: 2.9.11~20110321-16
Severity: serious

Hi,

please switch the Build-Depends of your package from `dkms` to `dh-dkms`
or (preferrably) `dh-sequence-dkms`.
With the latter you can also drop the `--with dkms` argument to `dh`.

Please consider adding
  Testsuite: autopkgtest-pkg-dkms
to the source stanza in debian/control s.t. the module gets build-tested
against any new kernel version in the archive and breakage is noticed
quickly.

If you have questions or need help for disabling the module build on
unsupported architectures/configurations (that may be exposed when
enabling the autopkgtest), don't hesitate to contact me.


Thanks

Andreas
--- End Message ---
--- Begin Message ---
Source: sl-modem
Source-Version: 2.9.11~20110321-17
Done: أحمد المحمودي (Ahmed El-Mahmoudy) 

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

Debian distribution maintenance software
pp.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated sl-modem package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 16 Jun 2023 03:53:11 +0200
Source: sl-modem
Architecture: source
Version: 2.9.11~20110321-17
Distribution: unstable
Urgency: low
Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy) 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Closes: 982685 1027887
Changes:
 sl-modem (2.9.11~20110321-17) unstable; urgency=low
 .
   [ Debian Janitor ]
   * Set debhelper-compat version in Build-Depends.
   * Fix day-of-week for changelog entries 2.9.11~20080817-2, 2.9.11~20080817-1,
 2.7.10-1.
 .
   [ أحمد المحمودي (Ahmed El-Mahmoudy) ]
   * Update standards version to 4.6.2
   * d/control:
 + Bump to debhelper 13
 + Switch to dh-sequence-dkms in build deps. (Closes: #1027887)
 + Add Testsuite: autopkgtest-pkg-dkms
   Thanks to Andreas Beckmann 
 + Drop execstack from build deps (Closes: #982685)
 + Add Rules-Requires-Root: no
   * d/rules:
 + Drop --with dkms
   Thanks to Andreas Beckmann 
 + Use DEB_HOST_ARCH in debian/rules instead of the incorrect
   DEB_BUILD_ARCH.
   Thanks to Steve Langasek 
 + Use objcopy instead of execstack to set the no-executable-stack state on
   the daemon's closed-source binary on i386.
   Thanks to Steve Langasek 
 + Make the package cross-buildable.
   Thanks to Steve Langasek 
 * d/sl-modem-dkms.dkms: Fix "dkms: line 80: cd: too many arguments"
   New dkms appends CC= variable to the MAKE[0] command, which this package
   treats like an arbitrary shell command. .
   Thanks to Dimitri John Ledkov 
   * Add d/sl-modem-dkms.lintian-overrides
   * Add d/s/lintian-overrides for missing sources of dsplibs.o & amrlibs.o
Checksums-Sha1:
 dcd8ffbd79dbd5041c42bbc042ab719e2d66e1f6 1972 sl-modem_2.9.11~20110321-17.dsc
 0c746b0d763940bd0f6bb3d0d957cc5fe9ff9df9 36860 
sl-modem_2.9.11~20110321-17.debian.tar.xz
 1770b08edc3f75f35187a337b40374d30de1a467 6413 
sl-modem_2.9.11~20110321-17_source.buildinfo
Checksums-Sha256:
 9e5517916357f8f5e7eaa844fb2b66acc0489a1a391f8ea0828523cfbd143dfc 1972 
sl-modem_2.9.11~20110321-17.dsc
 0341d04cf3c772275ddb8dc1795485f00196fc507aa73cd62650ec0ccaaaf594 36860 
sl-modem_2.9.11~20110321-17.debian.tar.xz
 f7ce04d252b630b83fd1a7c555fb8bbd1ccddc6dabdcaa9764b5a810f0b14434 6413 
sl-modem_2.9.11~20110321-17_source.buildinfo
Files:
 2700bf4f90faa6332e47edba8d0b10e5 1972 non-free/misc optional 
sl-modem_2.9.11~20110321-17.dsc
 c4cb369193b256f6c4dd3b97468df289 36860 non-free/misc optional 
sl-modem_2.9.11~20110321-17.debian.tar.xz
 2dd06b4aada85da46793ce176547f812 6413 non-free/misc optional 

Bug#1037351: marked as done (hippotat: ftbfs with rust-base64 0.21)

[Debian Bug Tracking System]

Your message dated Fri, 16 Jun 2023 00:47:48 +
with message-id 
and subject line Bug#1037351: fixed in hippotat 1.1.8
has caused the Debian Bug report #1037351,
regarding hippotat: ftbfs with rust-base64 0.21
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.)


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

Package: hippotat
Version: 1.1.7
Tags: trixie, sid, ftbfs, patch

hippotat FTBFS with the new version of rust-base64.

I attach a patch which makes the package build.
I have not tested it beyond that (and the build said it was
skipping tests due to lack of unshare).

Also your clean target is horriblly broken, I filtered the
debdiff to get rid of a huge volume of junk.

I may or may not NMU this later.
diff -Nru hippotat-1.1.7/debian/cargo_home/config 
hippotat-1.1.7+nmu1/debian/cargo_home/config
--- hippotat-1.1.7/debian/cargo_home/config 1970-01-01 00:00:00.0 
+
+++ hippotat-1.1.7+nmu1/debian/cargo_home/config2023-06-11 
19:36:38.0 +
@@ -0,0 +1,8 @@
+[source.crates-io]
+replace-with = "dh-cargo-registry"
+
+[source.dh-cargo-registry]
+directory = "/usr/share/cargo/registry"
+
+[build]
+rustflags = ['-C', 'debuginfo=2', '--cap-lints', 'warn', '-C', 
'linker=x86_64-linux-gnu-gcc', '-C', 'link-arg=-Wl,-z,relro']
diff -Nru hippotat-1.1.7/debian/changelog hippotat-1.1.7+nmu1/debian/changelog
--- hippotat-1.1.7/debian/changelog 2023-01-12 18:50:36.0 +
+++ hippotat-1.1.7+nmu1/debian/changelog2023-06-11 19:36:38.0 
+
@@ -1,3 +1,11 @@
+hippotat (1.1.7+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Bump base64 dependency to 0.21 and fix code to build with it.
+  * Make debian dependency on base64 match the versioing in Cargo.toml.
+
+ -- Peter Michael Green   Sun, 11 Jun 2023 19:36:38 +
+
 hippotat (1.1.7) unstable; urgency=medium
 
   Build system:
diff -Nru hippotat-1.1.7/debian/control hippotat-1.1.7+nmu1/debian/control
--- hippotat-1.1.7/debian/control   2023-01-12 18:50:36.0 +
+++ hippotat-1.1.7+nmu1/debian/control  2023-06-11 19:36:29.0 +
@@ -9,7 +9,7 @@
moreutils, libssl-dev (>= 1.1), pkg-config,
 # debian/update-build-deps manages these:
 librust-backtrace-dev ,
-librust-base64-dev ,
+librust-base64-0.21-dev ,
 librust-clap-3+derive-dev ,
 librust-easy-ext-dev ,
 librust-educe-dev ,
--- End Message ---
--- Begin Message ---
Source: hippotat
Source-Version: 1.1.8
Done: Ian Jackson 

We believe that the bug you reported is fixed in the latest version of
hippotat, 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.
Ian Jackson  (supplier of updated hippotat 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Jun 2023 22:16:53 +0100
Source: hippotat
Architecture: source
Version: 1.1.8
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson 
Changed-By: Ian Jackson 
Closes: 1037351
Changes:
 hippotat (1.1.8) unstable; urgency=medium
 .
   Dependencies:
   * base64: update to 0.21 and fix code to build with it
 [Peter Green, Ian Jackson]  Closes: #1037351.
 We are now incompatible with Debian bookworm, and targeting trixie.
   * clap: update to clap 4 and fix code to build and run with it.
 .
   Packaging:
   * Make version minima in Cargo.toml accurate (and tested).
   * Tidying-up of Cargo.toml.
   * Update the provided Cargo.lock.
 .
   Debian packaging:
   * Add version specifiers for all Rust build-dependencies.
 (Extracted from the Cargo.toml's minima, which are now correct.)
   * debian/update-build-deps: Add --check mode
   * debian/update-build-deps: Use a real TOML parser
   * debian/update-build-deps: Scan macros/ too
 .
   Tests:
   * test/capture-log: Make it possible to disable capturing
   * Add many gitlab (sal) CI tests of both upstream and Debian builds,
 cargo audit, metadata consistency, etc.
 Sadly no end-to-end client/server tests due to lack of a
 

Bug#1038122: cp: cannot stat '/tmp/odbcinst.ini.bak'

[Hugh McMaster]

Hi Simon and Alan,

On Fri, 16 Jun 2023 at 09:24, Simon McVittie wrote:
>
> Control: severity -1 serious
> Control: block 1038041 by -1
>
> On Fri, 16 Jun 2023 at 03:49:12 +0930, Arthur Marsh wrote:
> > Attempting to upgrade odbc related packages from 2.3.11-2 to 2.3.11-3
>
> > Setting up unixodbc-common (2.3.11-3) ...
> > cp: cannot stat '/tmp/odbcinst.ini.bak': No such file or directory
> > dpkg: error processing package unixodbc-common (--configure):
> >  installed unixodbc-common package post-installation script subprocess 
> > returned error exit status 1
>
> Here's a repeatable reproducer for this bug:
>
> $ podman run --rm -it debian:sid # not sid-slim to avoid #1038067
> # apt update
> # apt upgrade
> # apt install unixodbc-common
> # rm /etc/odbcinst.ini
> # apt install --reinstall unixodbc-common
> ...
> Unpacking unixodbc-common (2.3.11-3) over (2.3.11-3) ...
> Setting up unixodbc-common (2.3.11-3) ...
> cp: cannot stat '/tmp/odbcinst.ini.bak': No such file or directory
>
> I don't actively use this package (it's installed as a dependency) so
> I haven't *intentionally* modified or deleted /etc/odbcinst.ini, but it
> wasn't present on my laptop for whatever reason, causing this failure
> mode during upgrades. Deleting configuration files is usually treated
> as an intentional sysadmin change that should be preserved.

/etc/odbcinst.ini should definitely be created during postinst if not
already present.

In this case, the log should show an error on preinst as well.

> I think the regression of failing to upgrade is a considerably worse
> bug than the old conffile record still being present in dpkg's database
> (#1009152). Is there a user-visible impact of #1009152 that makes it worth
> having this extra complexity? I'm not at all sure that
> https://bugs.debian.org/1009152#15 is the
> right thing to be doing here.

I tested multiple new install and upgrade scenarios, although it seems
likely I didn't test this particular scenario.

There is no user impact, other than a slightly non-clean system.

rm_conffile renames the conffile to conffile.dpkg-bak, which is only
deleted during package purge.

I'm now thinking a much better approach is to test for the presence of
the backup file during postinst and copy it back as /etc/odbcinst.ini.

That would greatly simplify things and avoid any breakage that we are
seeing now. I'll test this thoroughly, of course.

> Not *directly* related to the failure to upgrade, but I'm also
> concerned by this package using a fixed filename in /tmp to save and
> restore a root-owned configuration file. /tmp is world-writeable, so
> the worst-case assumption needs to be that a malicious local user has
> created /tmp/odbcinst.ini.bak with crafted contents (maybe as a directory,
> or a symlink to a location of their choice, or as a hard link). If so,
> then I'm worried that there might be something they can do to cause a
> denial of service, or worse, overwrite something (/etc/odbcinst.ini or
> otherwise) with attacker-controlled contents. If this tricky save/restore
> transaction is needed, it would be safer to use a root-owned location
> in /etc or /var that is namespaced appropriately for the package, for
> example perhaps "/etc/odbcinst.ini.maintscript-temp" analogous to dpkg's
> .dpkg-old and so on.

Yes, mktemp or tempdir would be more appropriate, although retrieving
the path in a different script is not so easy.

Processed: Re: Bug#1038122: cp: cannot stat '/tmp/odbcinst.ini.bak'

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1038122 [unixodbc-common] cp: cannot stat '/tmp/odbcinst.ini.bak'
Severity set to 'serious' from 'important'
> block 1038041 by -1
Bug #1038041 [release.debian.org] bookworm-pu: package unixodbc/2.3.11-2+deb12u1
1038041 was not blocked by any bugs.
1038041 was not blocking any bugs.
Added blocking bug(s) of 1038041: 1038122

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

Processed: affects 1030129

[Debian Bug Tracking System]

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

> affects 1030129 src:cvc5
Bug #1030129 [ca-certificates-java] ca-certificates-java - Fails to install: 
Error loading java.security file
Added indication that 1030129 affects src:cvc5
> thanks
Stopping processing here.

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

Bug#1038148: aardvark-dns: FTBFS with new rust-async-broadcast.

[Peter Green]

Package: aardvark-dns
Version: 1.4.0-3
Severity: serious

rust-async-broadcast was recently updated to 0.5, the Debian dependencies
of aardvark-dns allow the new version but the cargo dependencies do not.
So the package FTBFS

When I removed the upper limit from the Cargo dependency the package built
successfully.

Debdiff attatched, I may or may not NMU this later.diff -Nru aardvark-dns-1.4.0/debian/changelog 
aardvark-dns-1.4.0/debian/changelog
--- aardvark-dns-1.4.0/debian/changelog 2023-01-15 07:05:56.0 +
+++ aardvark-dns-1.4.0/debian/changelog 2023-06-15 17:16:42.0 +
@@ -1,3 +1,10 @@
+aardvark-dns (1.4.0-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove upper limit from cargo dependency on async-broadcast.
+
+ -- Peter Michael Green   Thu, 15 Jun 2023 17:16:42 +
+
 aardvark-dns (1.4.0-3) unstable; urgency=medium
 
   [ Peter Green ]
diff -Nru aardvark-dns-1.4.0/debian/patches/update-dependencies.patch 
aardvark-dns-1.4.0/debian/patches/update-dependencies.patch
--- aardvark-dns-1.4.0/debian/patches/update-dependencies.patch 2023-01-15 
07:05:56.0 +
+++ aardvark-dns-1.4.0/debian/patches/update-dependencies.patch 2023-06-15 
17:16:38.0 +
@@ -1,7 +1,7 @@
-Index: aardvark-dns/Cargo.toml
+Index: aardvark-dns-1.4.0/Cargo.toml
 ===
 aardvark-dns.orig/Cargo.toml
-+++ aardvark-dns/Cargo.toml
+--- aardvark-dns-1.4.0.orig/Cargo.toml
 aardvark-dns-1.4.0/Cargo.toml
 @@ -14,19 +14,19 @@ exclude = ["/.cirrus.yml", "/.github/*"]
  # See more keys and their definitions at 
https://doc.rust-lang.org/cargo/reference/manifest.html
  
@@ -21,7 +21,8 @@
 +futures-util = { version = "0.3", default-features = false }
  signal-hook = "0.3.13"
  tokio = { version = "1.21.2", features = ["macros", "rt-multi-thread", "net"] 
}
- async-broadcast = "0.4.1"
+-async-broadcast = "0.4.1"
++async-broadcast = ">= 0.4.1"
  resolv-conf = "0.7.0"
 -nix = "0.25.0"
 +nix = "0.26"

Bug#1038145: cgreen: FTBFS on s390x

[Steve Langasek]

Source: cgreen
Version: 1.5.1-1
Severity: serious
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic

Dear maintainers,

cgreen > 1.4.1-1 fails to build from source on s390x:

[...]
Total Test time (real) =   3.57 sec

The following tests FAILED:
  3 - runner_test_cgreen_c (Failed)
  6 - runner_test_cgreen_cpp (Failed)
Errors while running CTest
Output from these tests are in: 
/<>/build/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
make[2]: *** [Makefile:33: test] Error 8
[...]

  
(https://buildd.debian.org/status/fetch.php?pkg=cgreen=s390x=1.5.1-1=1681718579=0)

This is a regression in architecture coverage, so will block the package
from testing until fixed or you get the ftp team to remove the old binaries.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1037453: libmail-dmarc-perl: FTBFS with test failures when there's no network

[Noah Meyerhans]

Control: tags -1 + pending


On 6/12/2023 8:58 PM, Steve Langasek wrote:

I've applied the attached (very dirty) patch to libmail-dmarc-perl in
Ubuntu, which is sufficient to let the package build in Launchpad.  Having
looked at some of the surrounding tests, I'm not sure this would let the
package build in a completely offline environment - I think Launchpad
provides name resolution of a limited subset of domains, so some tests which
pass in Launchpad may also fail when offline.


Thanks. It seems to build in a completely disconnected environment with 
your patch applied, so let's start with it.

Processed: Re: Bug#1037453: libmail-dmarc-perl: FTBFS with test failures when there's no network

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1037453 [libmail-dmarc-perl] libmail-dmarc-perl: FTBFS with test failures 
when there's no network
Added tag(s) pending.

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

Bug#1038139: debci-worker: Process leaks authentication data via amqp-tools

[Christian Kastner]

Package: debci
Version: 3.6
Severity: serious
Tags: security
X-Debbugs-Cc: Debian Security Team 

Hi,

When using authentication in AMQP connections, the username and password
supplied in the --url option to amqp-consume resp. amqp-publish are
exposed in the proces list, see #1037322:

  $ pgrep -a ampq-consume
  62287 amqp-consume --url amqp://user:pass@192.168.0.1 --queue=myqueue

A patch has been accepted upstream to read the username and password
from a file. I assume this will make its way into ampq-tools soon.

Unless I'm mistaken, debci will need to be updated for this, e.g. by
adding a debci_amqp_pwfile config option + NEWS entry suggesting that
people migrate to this new option. I'd be happy to file an MR for this,
once ampq-tools has been fixed.

Best,
Christian


-- System Information:
Debian Release: 11.7
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'),
(500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-0.deb11.7-amd64 (SMP w/24 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 debci depends on:
ii  adduser 3.118
pn  amqp-tools  
ii  curl7.88.1-7~bpo11+2
ii  dctrl-tools 2.24-3+b1
ii  debian-archive-keyring  2021.1.1+deb11u1
ii  debootstrap 1.0.128+nmu2~bpo11+1
ii  devscripts  2.22.2~bpo11+1
pn  distro-info 
ii  fonts-font-awesome  5.0.10+really4.7.0~dfsg-4.1
ii  jq  1.6-2.1
ii  libjs-bootstrap 3.4.1+dfsg-2
ii  libjs-jquery3.5.1+dfsg+~3.5.5-7
pn  libjs-jquery-flot   
pn  moreutils   
ii  netcat-openbsd  1.217-3
pn  parallel
ii  patchutils  0.4.2-1
pn  retry   
ii  rsync   3.2.7-1~bpo11+1
ii  ruby1:2.7+2
pn  ruby-activerecord   
pn  ruby-bunny  
pn  ruby-erubi  
pn  ruby-kaminari-activerecord  
pn  ruby-pg 
pn  ruby-sinatra
pn  ruby-sinatra-contrib
pn  ruby-sqlite3
pn  ruby-thor   
pn  sudo

Versions of packages debci recommends:
ii  systemd-timesyncd [time-daemon]  252.5-2~bpo11+1

Versions of packages debci suggests:
pn  apt-cacher-ng  

Bug#1038138: rust-diesel: FTBFS in unstable

[Steve Langasek]

Source: rust-diesel
Version: 2.0.3-1
Severity: serious
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic

Dear maintainers,

In trying to rebuild rust-diesel with the fix for bug #1038135, I've
discovered the package now fails to build from source in both Debian
unstable and Ubuntu mantic:

[...]
error[E0277]: the trait bound `FieldAttr: ToTokens` is not satisfied
   --> 
/<>/debian/cargo_registry/diesel_derives-2.0.1/src/attrs.rs:143:6
|
143 | impl Spanned for FieldAttr {
|  ^^^ the trait `ToTokens` is not implemented for `FieldAttr`
|
= help: the following other types implement trait `ToTokens`:
  &'a T
  &'a mut T
  Abi
  Abstract
  AndAnd
  AndEq
  AngleBracketedGenericArguments
  As
and 243 others
= note: required for `FieldAttr` to implement 
`quote::spanned::private::Sealed`
note: required by a bound in `quote::spanned::Spanned`
   --> /<>/debian/cargo_registry/quote-1.0.27/src/spanned.rs:6:20
|
6   | pub trait Spanned: private::Sealed {
|^^^ required by this bound in 
`quote::spanned::Spanned`

error[E0277]: the trait bound `StructAttr: ToTokens` is not satisfied
   --> 
/<>/debian/cargo_registry/diesel_derives-2.0.1/src/attrs.rs:242:6
|
242 | impl Spanned for StructAttr {
|  ^^^ the trait `ToTokens` is not implemented for `StructAttr`
|
= help: the following other types implement trait `ToTokens`:
  &'a T
  &'a mut T
  Abi
  Abstract
  AndAnd
  AndEq
  AngleBracketedGenericArguments
  As
and 243 others
= note: required for `StructAttr` to implement 
`quote::spanned::private::Sealed`
note: required by a bound in `quote::spanned::Spanned`
   --> /<>/debian/cargo_registry/quote-1.0.27/src/spanned.rs:6:20
|
6   | pub trait Spanned: private::Sealed {
|^^^ required by this bound in 
`quote::spanned::Spanned`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `diesel_derives` due to 2 previous errors
[...]

  
(https://launchpad.net/ubuntu/+source/rust-diesel/2.0.3-1ubuntu1/+build/26310394)

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1038135: rust-diesel: librust-diesel-dev uninstallable on 32-bit archs

[Steve Langasek]

Package: rust-diesel
Version: 2.0.3-1
Severity: serious
Tags: patch
Justification: uninstallable
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch

Dear maintainers,

rust-diesel is not migrating to Debian testing because it depends on
librust-pq-sys-dev and librust-mysqlclient-sys-dev, neither of which is
buildable on 32-bit archs; but it does not build-depend on these packages,
so librust-diesel-dev builds uninstallable binary packages.

Either rust-diesel should build-depend on these packages so that binaries
are not built on architectures where they're unavailable, or the
dependencies should be relaxed so that the packages are installable.

For the moment, I've opted for the first of these in Ubuntu.  See attached
patch.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru rust-diesel-2.0.3/debian/control rust-diesel-2.0.3/debian/control
--- rust-diesel-2.0.3/debian/control2023-02-10 03:05:35.0 -0800
+++ rust-diesel-2.0.3/debian/control2023-06-15 13:22:18.0 -0700
@@ -8,7 +8,9 @@
  libstd-rust-dev ,
  librust-diesel-derives-2.0+32-column-tables-dev ,
  librust-diesel-derives-2.0+default-dev ,
- librust-diesel-derives-2.0+with-deprecated-dev 
+ librust-diesel-derives-2.0+with-deprecated-dev ,
+ librust-pq-sys-dev,
+ librust-mysqlclient-sys-dev
 Maintainer: Debian Rust Maintainers 

 Uploaders:
  kpcyrd ,

Bug#1037974: ddcci-dkms: code fails to build and package fails to install with Linux 6.3 headers

[Stephen Kitt]

Hi Paul,

On Thu, 15 Jun 2023 10:32:56 +0800, Paul Wise  wrote:
> When I try to install ddcci-dkms with the Linux 6.3 headers installed,
> the build of the code fails and then the install of the package fails.
> 
> I think there are two problems here:
> 
>  * The code needs to be adapted to the latest Linux kernel version.

I’ve applied candidate patches from the upstream repo to handle up to 6.4.

>  * The package should not fail to install when the module build fails.
>    This might be a problem in dkms itself, or in ddcci's integration.

This is the more interesting issue, but see #1029063. Admittedly the absence
of a ddcci module is unlikely to ever prevent a system from booting, so
perhaps we could have a way of telling dkms that build failures in a given
module shouldn’t be treated as errors. Andreas, what do you think?

Regards,

Stephen


pgpdvmAJgP37_.pgp
Description: OpenPGP digital signature

Bug#1038131: Duplicate of 1037828

[Sebastian Ramacher]

On 2023-06-15 12:32:05 -0700, Soren Stoutner wrote:
> This looks like a duplicate of
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037828[1]
> 
> Which relates to the transition from GCC 12 to GCC 13 causing a FTBFS.

The failure happened with GCC 12, though.

Cheers
-- 
Sebastian Ramacher

Processed: limit source to hippotat, tagging 1037351

[Debian Bug Tracking System]

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

> limit source hippotat
Limiting to bugs with field 'source' containing at least one of 'hippotat'
Limit currently set to 'source':'hippotat'

> tags 1037351 + pending
Bug #1037351 [hippotat] hippotat: ftbfs with rust-base64 0.21
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1037510: texlive-lang-japanese: dangling symlinks due to missing dependencies

[Vincent Lefevre]

Hi,

On 2023-06-15 20:40:36 +0200, Preuße, Hilmar wrote:
> Currently we just suggest these 4 packages. I propose to promote the suggest
> to recommend. Do you think that would be sufficient?

Since Recommends are installed by default, I think that this would be
sufficient (this should also probably be documented). Alternatively,
the symbolic links could be provided by the packages that contain the
files, if this makes sense.

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

Bug#1038133: libx11: CVE-2023-3138

[Salvatore Bonaccorso]

Source: libx11
Version: 2:1.8.4-2
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for libx11.

CVE-2023-3138[0]:
| Buffer overflows in InitExt.c in libX11

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-3138
https://www.cve.org/CVERecord?id=CVE-2023-3138
[1] 
https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/304a654a0d57bf0f00d8998185f0360332cfa36c
[2] https://www.openwall.com/lists/oss-security/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1038132: qtwebengine-opensource-src: FTBFS: ../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: operand type mismatch for `shr'

[Sebastian Ramacher]

Source: qtwebengine-opensource-src
Version: 5.15.13+dfsg-1~deb12u1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src=amd64=5.15.13%2Bdfsg-1%7Edeb12u1%2Bb1=1686790387=0

FAILED: obj/third_party/ffmpeg/ffmpeg_internal/autorename_libavcodec_flacdec.o 
/usr/bin/gcc -MMD -MF 
obj/third_party/ffmpeg/ffmpeg_internal/autorename_libavcodec_flacdec.o.d 
-DHAVE_AV_CONFIG_H -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC 
-DFFMPEG_CONFIGURATION=NULL -DCHROMIUM_NO_LOGGING -D_ISOC99_SOURCE 
-D_LARGEFILE_SOURCE -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 
-DOFFICIAL_BUILD -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES -DNDEBUG -DNVALGRIND 
-DDYNAMIC_ANNOTATIONS_ENABLED=0 
-I../../3rdparty/chromium/third_party/ffmpeg/chromium/config/Chrome/linux/x64 
-I../../3rdparty/chromium/third_party/ffmpeg 
-I../../3rdparty/chromium/third_party/ffmpeg/compat/atomics/gcc -Igen 
-I../../3rdparty/chromium -Igen -fPIC -Wno-deprecated-declarations 
-fomit-frame-pointer -w -std=c99 -pthread -fno-math-errno -fno-signed-zeros 
-fno-tree-vectorize -fno-strict-aliasing --param=ssp-buffer-size=4 
-fstack-protector -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC 
-pipe -pthread -m64 -g0 -fvisibility=hidden -Wno-unused-local-typedefs 
-Wno-maybe-uninitialized -Wno-deprecated-declarations 
-fno-delete-null-pointer-checks -Wno-comments -Wno-packed-not-aligned 
-Wno-dangling-else -Wno-missing-field-initializers -Wno-unused-parameter -O2 
-fno-ident -fdata-sections -ffunction-sections -I/usr/include/opus -std=gnu11 
-c 
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/autorename_libavcodec_flacdec.c
 -o obj/third_party/ffmpeg/ffmpeg_internal/autorename_libavcodec_flacdec.o
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h: Assembler 
messages:
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:116: Error: 
operand type mismatch for `sar'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: 
operand type mismatch for `shr'
[3608/33093] /usr/bin/gcc -MMD -MF 
obj/third_party/ffmpeg/ffmpeg_internal/autorename_libavcodec_flacdsp.o.d 
-DHAVE_AV_CONFIG_H -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC 
-DFFMPEG_CONFIGURATION=NULL -DCHROMIUM_NO_LOGGING -D_ISOC99_SOURCE 
-D_LARGEFILE_SOURCE -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 
-DOFFICIAL_BUILD -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES -DNDEBUG -DNVALGRIND 
-DDYNAMIC_ANNOTATIONS_ENABLED=0 
-I../../3rdparty/chromium/third_party/ffmpeg/chromium/config/Chrome/linux/x64 
-I../../3rdparty/chromium/third_party/ffmpeg 
-I../../3rdparty/chromium/third_party/ffmpeg/compat/atomics/gcc -Igen 
-I../../3rdparty/chromium -Igen -fPIC -Wno-deprecated-declarations 
-fomit-frame-pointer -w -std=c99 -pthread -fno-math-errno -fno-signed-zeros 
-fno-tree-vectorize -fno-strict-aliasing --param=ssp-buffer-size=4 
-fstack-protector -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC 
-pipe -pthread -m64 -g0 -fvisibility=hidden -Wno-unused-local-typedefs 
-Wno-maybe-uninitialized 

Bug#1038131: qt6-webengine: FTBFS: ../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: operand type mismatch for `shr'

[Sebastian Ramacher]

Source: qt6-webengine
Version: 6.4.2-final+dfsg-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=qt6-webengine=amd64=6.4.2-final%2Bdfsg-1%2Bb1=1686789322=0

FAILED: obj/third_party/ffmpeg/ffmpeg_internal/flacdec.o 
/usr/bin/cc -MMD -MF obj/third_party/ffmpeg/ffmpeg_internal/flacdec.o.d 
-DHAVE_AV_CONFIG_H -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC 
-DFFMPEG_CONFIGURATION=NULL -DCHROMIUM_NO_LOGGING -D_ISOC99_SOURCE 
-D_LARGEFILE_SOURCE -DUSE_UDEV -DUSE_AURA=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD 
-DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES 
-DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-I../../../../../src/3rdparty/chromium/third_party/ffmpeg/chromium/config/Chrome/linux/x64
 -I../../../../../src/3rdparty/chromium/third_party/ffmpeg -Igen 
-I../../../../../src/3rdparty/chromium -fPIC -Wno-deprecated-declarations 
-fomit-frame-pointer -w -std=c99 -pthread -fno-math-errno -fno-signed-zeros 
-fno-tree-vectorize -fno-ident -fno-strict-aliasing --param=ssp-buffer-size=4 
-fstack-protector -Wno-unknown-pragmas -Wno-parentheses -Wno-sign-compare 
-Wno-stringop-overflow -Wno-stringop-overread -Wno-psabi -Wno-multichar 
-Wno-format-zero-length -fno-unwind-tables -fno-asynchronous-unwind-tables 
-fPIC -pipe -pthread -m64 -msse3 -gdwarf-4 -g1 -fvisibility=hidden 
-Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments 
-Wno-packed-not-aligned -Wno-dangling-else -Wno-missing-field-initializers 
-Wno-unused-parameter -O2 -fdata-sections -ffunction-sections 
-I/usr/include/opus -std=gnu11 -c 
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/flacdec.c -o 
obj/third_party/ffmpeg/ffmpeg_internal/flacdec.o
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:
 Assembler messages:
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:116:
 Error: operand type mismatch for `sar'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
../../../../../src/3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125:
 Error: operand type mismatch for `shr'
ninja: build stopped: subcommand failed.
FAILED: src/core/None/x86_64/QtWebEngineCore.stamp 
src/core/None/x86_64/QtWebEngineCore 
/<>/obj-x86_64-linux-gnu/src/core/None/x86_64/QtWebEngineCore.stamp
 /<>/obj-x86_64-linux-gnu/src/core/None/x86_64/QtWebEngineCore 
cd /<>/obj-x86_64-linux-gnu/src/core && /usr/bin/ninja -C 
/<>/obj-x86_64-linux-gnu/src/core/None/x86_64 QtWebEngineCore
ninja: build stopped: subcommand failed.
dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v 
returned exit code 1
make: *** [debian/rules:31: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher

Processed: Re: minidlna: CVE-2023-33476

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.3.0+dfsg-2.2
Bug #1037052 [src:minidlna] minidlna: CVE-2023-33476
Marked as found in versions minidlna/1.3.0+dfsg-2.2.

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

Bug#1037052: minidlna: CVE-2023-33476

[Paul Gevers]

control: found -1 1.3.0+dfsg-2.2

Hi,

On Fri, 02 Jun 2023 23:25:09 +0200 Salvatore Bonaccorso 
 wrote:

| ReadyMedia (MiniDLNA) versions from 1.1.15 up to 1.3.2 is vulnerable
| to Buffer Overflow.


Which means the version in testing (and stable) is also affected.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1038127: src:mail-expire: fails to migrate to testing for too long: uploader built binaries

[Paul Gevers]

Source: mail-expire
Version: 0.9.1
Severity: serious
Control: close -1 0.9.2
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:mail-expire: fails to migrate to testing for too long: uploader built binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.9.2
Bug #1038127 [src:mail-expire] src:mail-expire: fails to migrate to testing for 
too long: uploader built binaries
Marked as fixed in versions mail-expire/0.9.2.
Bug #1038127 [src:mail-expire] src:mail-expire: fails to migrate to testing for 
too long: uploader built binaries
Marked Bug as done

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

Bug#1038125: src:eln: fails to migrate to testing for too long: new build dependencies not available

[Paul Gevers]

Source: eln
Version: 1.4.6-1
Severity: serious
Control: close -1 1.5.0-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:eln has been trying to migrate for 81 days 
[2] (yes, partially because of the freeze). Hence, I am filing this bug. 
Your package started to build depend on packages not available on all 
release architectures. You probably need to request removal of your 
binaries on those architectures, or fix the problem someway else.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:python-pyo: fails to migrate to testing for too long: FTBFS on i386

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.0.5-2
Bug #1038126 [src:python-pyo] src:python-pyo: fails to migrate to testing for 
too long: FTBFS on i386
Marked as fixed in versions python-pyo/1.0.5-2.
Bug #1038126 [src:python-pyo] src:python-pyo: fails to migrate to testing for 
too long: FTBFS on i386
Marked Bug as done

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

Bug#1038126: src:python-pyo: fails to migrate to testing for too long: FTBFS on i386

[Paul Gevers]

Source: python-pyo
Version: 1.0.4-1
Severity: serious
Control: close -1 1.0.5-2
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:python-pyo has been trying to migrate for 
80 days [2]. Hence, I am filing this bug. Your package failed to build 
from source on i386, while it built there successfully in the past.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:eln: fails to migrate to testing for too long: new build dependencies not available

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.5.0-2
Bug #1038125 [src:eln] src:eln: fails to migrate to testing for too long: new 
build dependencies not available
Marked as fixed in versions eln/1.5.0-2.
Bug #1038125 [src:eln] src:eln: fails to migrate to testing for too long: new 
build dependencies not available
Marked Bug as done

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

Processed: src:geoalchemy2: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.13.3-1
Bug #1038124 [src:geoalchemy2] src:geoalchemy2: fails to migrate to testing for 
too long: autopkgtest regression
Marked as fixed in versions geoalchemy2/0.13.3-1.
Bug #1038124 [src:geoalchemy2] src:geoalchemy2: fails to migrate to testing for 
too long: autopkgtest regression
Marked Bug as done
> block -1 by 1034304
Bug #1038124 {Done: Paul Gevers } [src:geoalchemy2] 
src:geoalchemy2: fails to migrate to testing for too long: autopkgtest 
regression
1038124 was not blocked by any bugs.
1038124 was not blocking any bugs.
Added blocking bug(s) of 1038124: 1034304

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

Bug#1038124: src:geoalchemy2: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: geoalchemy2
Version: 0.12.5-1
Severity: serious
Control: close -1 0.13.3-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1034304

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:geoalchemy2 has been trying to migrate for 
89 days [2] (yes, partially due to the freeze, but that's over now). 
Hence, I am filing this bug. Your package has an autopkgtest regression, 
I filed a bug for that in 1034304.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1037510: texlive-lang-japanese: dangling symlinks due to missing dependencies

[Preuße]

On 13.06.2023 18:00, Vincent Lefevre wrote:

Hi Vincent,


There is a dangling symlink on my machine:
/usr/share/texlive/texmf-dist/fonts/truetype/public/ipaex/ipaexm.ttf -> 
../../../../../../fonts/opentype/ipaexfont-mincho/ipaexm.ttf

This seems to be due to a missing dependency on fonts-ipaexfont-mincho.


Thanks for the report!

Currently we just suggest these 4 packages. I propose to promote the 
suggest to recommend. Do you think that would be sufficient?
Mhhh: these 4 packages have a (installed) size of 40MB. Maybe the is 
neglect-able given the size of texlive-lang-japanese (300MB).


Let me know what you think.

H.
--
sigfault



OpenPGP_0x0C871C4C653C1F59.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1037985: marked as done (godot: FTBFS om s390 (missing #include ))

[Debian Bug Tracking System]

Your message dated Thu, 15 Jun 2023 17:53:32 +
with message-id 
and subject line Bug#1037985: fixed in godot 3.5.2-stable-1
has caused the Debian Bug report #1037985,
regarding godot: FTBFS om s390 (missing #include )
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.)


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

Package: src:godot
Version: 3.5.1-stable-2
Severity: serious

The latest source fail to build on s390x.  This is the build error from
https://buildd.debian.org/status/fetch.php?pkg=godot=s390x=3.5.1-stable-2=1686780159=0
 >:

  Compiling ==> thirdparty/embree/common/sys/sysinfo.cpp
  In file included from thirdparty/embree/common/sys/sysinfo.cpp:5:
  thirdparty/embree/common/sys/intrinsics.h:15:10: fatal error: immintrin.h: No 
such file or directory
 15 | #include 
|  ^
  compilation terminated.
  scons: *** [thirdparty/embree/common/sys/sysinfo.x11.opt.tools.64.o] Error 1
  scons: building terminated because of errors.
  [Time elapsed: 00:04:55.241]
  make[1]: *** [debian/rules:83: override_dh_auto_build] Error 2

A similar build error occured with version 3.5.1-stable-1 reported as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031132 > with
the build log in
https://buildd.debian.org/status/fetch.php?pkg=godot=s390x=3.5.1-stable-1=1675605014=0
 >:

  Compiling ==> thirdparty/oidn/core/api.cpp
  In file included from thirdparty/oidn/core/common.h:19,
   from thirdparty/oidn/core/device.h:19,
   from thirdparty/oidn/core/api.cpp:48:
  thirdparty/oidn/common/platform.h:27:10: fatal error: xmmintrin.h: No such 
file or directory
 27 | #include 
|  ^
  compilation terminated.
  scons: *** [thirdparty/oidn/core/api.x11.opt.tools.64.o] Error 1
  scons: building terminated because of errors.
  [Time elapsed: 00:01:47.982]
  make[1]: *** [debian/rules:66: override_dh_auto_build] Error 2

The "solution" then was to disable the module that failed to build on
any non x86 and arm platform.  Perhaps some other module need to be
disabled on s390x?

Setting severity serious as this build problem will block the package
from entering testing.

-- 
Happy hacking
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Source: godot
Source-Version: 3.5.2-stable-1
Done: Petter Reinholdtsen 

We believe that the bug you reported is fixed in the latest version of
godot, 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.
Petter Reinholdtsen  (supplier of updated godot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Jun 2023 18:51:07 +0200
Source: godot
Architecture: source
Version: 3.5.2-stable-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Petter Reinholdtsen 
Closes: 1037985
Changes:
 godot (3.5.2-stable-1) unstable; urgency=medium
 .
   * Team upload.
 .
   * Added d/gbp.conf to enforce use of pristine-tar.
   * New upstream version 3.5.2-stable.
   * Disable modules raycast and lightmapper_cpu on s390x (Closes: #1037985).
Checksums-Sha1:
 6ddd493e276858a02da6ba245658e11c24d948e0 2589 godot_3.5.2-stable-1.dsc
 3194a175654608e19c20d378cd9457b1fcf7a6d8 56483598 
godot_3.5.2-stable.orig.tar.gz
 948014d5d33f3d0beed5a9a52e372b9154d32b6f 17736 
godot_3.5.2-stable-1.debian.tar.xz
 fc23ad404bb6af79871666373c46aa3eb7c69dc8 12286 
godot_3.5.2-stable-1_source.buildinfo
Checksums-Sha256:
 41f2c07e29987c310f988a90f905045c0d0a8a20cc88a0d4b6e253734187b2c5 2589 
godot_3.5.2-stable-1.dsc
 f40652a1343d060d5e3f53957c27205f39c2bfe54b7701d1b6c133c0a90f1f34 56483598 
godot_3.5.2-stable.orig.tar.gz
 5c629fe9ef1d0a541665ecc655f48bb1a32da05b7ad8a70c550ea2c825465a26 17736 
godot_3.5.2-stable-1.debian.tar.xz
 7292ce0918fc7aed511bed3b3e7125862ac61f920ad28faa3ddde70d4ff0 12286 
godot_3.5.2-stable-1_source.buildinfo
Files:
 0c8d482771d1c68a11fb516028f4282f 2589 devel optional godot_3.5.2-stable-1.dsc
 1534d7712f9ef02e68d556893505d061 56483598 devel optional 

Bug#1037982: marked as done (libnet-route-perl needs dependency net-tools for system route command.)

[Debian Bug Tracking System]

Your message dated Thu, 15 Jun 2023 15:21:50 +
with message-id 
and subject line Bug#1037982: fixed in libnet-route-perl 0.02-4
has caused the Debian Bug report #1037982,
regarding libnet-route-perl needs dependency net-tools for system route command.
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.)


-- 
1037982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnet-route-perl
Version: 0.02-3
Severity: serious
X-Debbugs-CC: Craig Manley 

As reported by Craig:

On Wed, Jun 14, 2023 at 12:33:44PM +0200, Craig Manley wrote:
> Hello,
> 
> Our builds were failing because libnet-route-perl called the missing system
> command /sbin/route which is provided by net-tools. That package isn't
> listed in the Depends list.
> 
> -Craig Manley

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libnet-route-perl
Source-Version: 0.02-4
Done: gregor herrmann 

We believe that the bug you reported is fixed in the latest version of
libnet-route-perl, 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.
gregor herrmann  (supplier of updated libnet-route-perl 
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, 15 Jun 2023 16:38:16 +0200
Source: libnet-route-perl
Architecture: source
Version: 0.02-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 1037982
Changes:
 libnet-route-perl (0.02-4) unstable; urgency=medium
 .
   * Team upload.
   * Add net-tools to Depends. It is needed at runtime as well.
 Thanks to Craig Manley for the bug report. (Closes: #1037982)
   * Declare compliance with Debian Policy 4.6.2.
   * Set Rules-Requires-Root: no.
   * Annotate test-only build dependencies with .
   * Move net-tools from Build-Depends to Build-Depends-Indep.
 Only needed for tests, not for the actual build.
Checksums-Sha1:
 d542d95a9c85f9110e0ce4652bb1f0eebe84fd59 2587 libnet-route-perl_0.02-4.dsc
 d4f38d678d019bb94b224f57b067085ac78436cb 2976 
libnet-route-perl_0.02-4.debian.tar.xz
Checksums-Sha256:
 d5a42d9c791d1edf9f18953042538a1262c8ec146fcd49c8c45bf7ae4d518d64 2587 
libnet-route-perl_0.02-4.dsc
 a0b310b67ad7c98bf2070bd7c4310419886178e3e1e6a1a7c61a5fbfb88626af 2976 
libnet-route-perl_0.02-4.debian.tar.xz
Files:
 0981bcd513de16dc4219c9b09ec8422f 2587 perl optional 
libnet-route-perl_0.02-4.dsc
 9488f1270891a0a8d49ce84a5a83dd70 2976 perl optional 
libnet-route-perl_0.02-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmSLI+9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbFzw/8DoberCGTCvjDsNB3UTqYNPXSYIr9zmLfTkHdPMcRORZ3MmsfYee6LzPZ
IUcZqjw4p2Qw1/Xt90kp4hL87O7CRG4InDCkq1DcK9psML7VQ/O4PVrNYdvUz3jo
KZxw1hXbboRVbV290S6RJ9U7/YE4NHrfCX5En+Ggzqu3ol+z+Bn+Tg0xVNXVfE/m
6kAFvUL9bqDaNOIEtIn/V68meZYeW/UJQP/vJm3Cni/SIBe7NqD/8W16i1EK9fWl
cTIbTB5Uk9aDf+rLV7kJH/hMlCtvaMAHFSGsLsP/RkiuOFt+t5xRHtmrh8N4jFLa
W3En2dDxwEx9k3RYPZmRO+oLFnJNmC+u74qSXTOgbkqOQGr0CK0QYtN71x6cs7i4
O11+1FWJbGzB0BFhYjigMb+LLHVRzJ7f3ZnfhyeWjgm1VUXBB0PvOU27NuO2iA5z
6BrNwN5uO2Q/+QZhHzD2wJdnReR5tush66ftmHG3npU56DukOY8m5JrwDbCkK315
m2e2B0vYt5QXQ+HuvbqPGQCu3NH4PNMygfEtSkva7sLIlmWvyppNo3IWymlpWR5G
Hp9AH9Kb19ST7Vu8jamU0ozk6U+LXBT5WmneXwfccYwczPi0O3eNfbkixNinM/O1
o93yXBAyNJSLdiEDisrf3bZWAK00FJIRuy51EEa23/Y1NOghEyA=
=Zb1m
-END PGP SIGNATURE End Message ---

Processed: transition: gdal

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:gdal
Bug #1038115 [release.debian.org] transition: gdal
Added indication that 1038115 affects src:gdal
> forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html
Bug #1038115 [release.debian.org] transition: gdal
Set Bug forwarded-to-address to 
'https://release.debian.org/transitions/html/auto-gdal.html'.
> block -1 by 1030129 998833 1037920 984398 1037976
Bug #1038115 [release.debian.org] transition: gdal
1038115 was not blocked by any bugs.
1038115 was not blocking any bugs.
Added blocking bug(s) of 1038115: 1037976, 1030129, 998833, 1037920, and 984398

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

Processed: tagging 1030129

[Debian Bug Tracking System]

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

> tags 1030129 + ftbfs
Bug #1030129 [ca-certificates-java] ca-certificates-java - Fails to install: 
Error loading java.security file
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1037982: libnet-route-perl needs dependency net-tools voor system route command.

[gregor herrmann]

On Thu, 15 Jun 2023 09:28:55 +0200, Craig Manley wrote:

> Yes it's a runtime dependency.-Craig

Alright; I didn't interpret "Our builds were failing" as a missing
runtime dependency but I understand now.

I'm uploading a fixed package shortly.

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1038111: haproxy-log-analysis: current version not usable, new upstream release available

[Daniel Scharon]

Package: haproxy-log-analysis
Version: 2.0~b0-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

directly after installation of haproxy-log-analysis the postinst script throws
errors:

Selecting previously unselected package python3-haproxy-log-analysis.
Preparing to unpack .../python3-haproxy-log-analysis_2.0~b0-4_all.deb ...
Unpacking python3-haproxy-log-analysis (2.0~b0-4) ...
Selecting previously unselected package haproxy-log-analysis.
Preparing to unpack .../haproxy-log-analysis_2.0~b0-4_all.deb ...
Unpacking haproxy-log-analysis (2.0~b0-4) ...
Setting up python3-pkg-resources (66.1.1-1) ...
Setting up python3-haproxy-log-analysis (2.0~b0-4) ...
/usr/lib/python3/dist-packages/haproxy/filters.py:122: SyntaxWarning: "is not"
with a literal. Did you mea
n "!="?
  if start_value is not '':
/usr/lib/python3/dist-packages/haproxy/filters.py:125: SyntaxWarning: "is not"
with a literal. Did you mea
n "!="?
  if delta_value is not '':
/usr/lib/python3/dist-packages/haproxy/filters.py:128: SyntaxWarning: "is not"
with a literal. Did you mea
n "!="?
  if start_value is not '' and delta_value is not '':
/usr/lib/python3/dist-packages/haproxy/filters.py:128: SyntaxWarning: "is not"
with a literal. Did you mea
n "!="?
  if start_value is not '' and delta_value is not '':
/usr/lib/python3/dist-packages/haproxy/filters.py:132: SyntaxWarning: "is" with
a literal. Did you mean "=
="?
  if start_value is '':
Setting up haproxy-log-analysis (2.0~b0-4) ...


Also executing haproxy-log-analysis throws an error which makes it basically
unusable:

Traceback (most recent call last):
  File "/usr/bin/haproxy_log_analysis", line 33, in 
sys.exit(load_entry_point('haproxy-log-analysis==2.0b0', 'console_scripts',
'haproxy_log_analysis')())

  File "/usr/lib/python3/dist-packages/haproxy/main.py", line 289, in
console_script
main(arguments)
  File "/usr/lib/python3/dist-packages/haproxy/main.py", line 274, in main
for command in args['commands']:
TypeError: 'NoneType' object is not iterable


The currently in Debian available version of haproxy-log-analysis is 7 years
old. There have been several releases by upstream since then. The latest was
version 5.1.0 released on December 3rd, 2022.

Please update haproxy-log-analysis so that we have a working version in Debian
again.

Thank you and kind regards,
Daniel




-- System Information:


Versions of packages haproxy-log-analysis depends on:
ii  python3   3.9.2-3
pn  python3-haproxy-log-analysis  

haproxy-log-analysis recommends no packages.

Bug#1038004: confirmed + some reference

[Ivan Sergio Borgonovo]

I've the same problem here and I've found

https://forums.developer.nvidia.com/t/driver-470-182-03-fails-to-compile-with-linux-6-3-1/251992/2

that lead me to:

https://gist.github.com/vejeta/9078219f082d2bfd62b08b6eada780e6

https://gist.github.com/joanbm/d10e9c8e245b6e7e27b2db338faf

thanks

--
Ivan Sergio Borgonovo
https://www.webthatworks.it https://www.borgonovo.net

Bug#1037171: closed by Debian FTP Masters (reply to Marc Haber ) (Bug#1037171: fixed in aide 0.18.3-2)

[TMC]

Hi there Aide maintainers

I think the proposed solution to this issue will also fix bug #1032381
<1032...@bugs.debian.org>, if my reading of the report is correct.

Tomasz

On Thu, 15 Jun 2023 at 01:21, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the aide package:
>
> #1037171: aide: fresh aide package install fails to add the requried _aide
> user to system
>
> It has been closed by Debian FTP Masters 
> (reply to Marc Haber ).
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters <
> ftpmas...@ftp-master.debian.org> (reply to Marc Haber <
> mh+debian-packa...@zugschlus.de>) by
> replying to this email.
>
>
> --
> 1037171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037171
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Debian FTP Masters 
> To: 1037171-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Wed, 14 Jun 2023 15:18:54 +
> Subject: Bug#1037171: fixed in aide 0.18.3-2
> Source: aide
> Source-Version: 0.18.3-2
> Done: Marc Haber 
>
> We believe that the bug you reported is fixed in the latest version of
> aide, 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.
> Marc Haber  (supplier of updated aide
> package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Format: 1.8
> Date: Wed, 14 Jun 2023 16:48:04 +0200
> Source: aide
> Architecture: source
> Version: 0.18.3-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Aide Maintainers 
> Changed-By: Marc Haber 
> Closes: 1037171 1037436
> Changes:
>  aide (0.18.3-2) unstable; urgency=medium
>  .
>* improve 31_aide_atop rule
>* call dh_installsysusers manually in debian/rules
>  Thanks to Tomasz Ciolek (Closes: #1037171)
>* Fix handling of extended attributes on symlinks. (Closes: #1037436)
> Checksums-Sha1:
>  6a5314b58033d46a94d1797753dc529d992b73d3 2579 aide_0.18.3-2.dsc
>  b0dfda1f3917973dae9e750939c06b00b398f004 108084
> aide_0.18.3-2.debian.tar.xz
>  7ba41950401bad0de82867c43d601d6b4afb452e 6597
> aide_0.18.3-2_source.buildinfo
> Checksums-Sha256:
>  570d2ad75dc06a04e0d6b116cb7569b8dfed083765a07e2ee4556e331c55184c 2579
> aide_0.18.3-2.dsc
>  86401bcbed3d641d796d6b82e9a4e832e52fd5ffe67d0f4882e2a44934f356dc 108084
> aide_0.18.3-2.debian.tar.xz
>  f4b81d3a9d8b5a0953d78c1f7dd7c82303cb1fcbae8b5604fad13632378dd994 6597
> aide_0.18.3-2_source.buildinfo
> Files:
>  3fdbd356c0d39f386a7b81e6ba9e1ccd 2579 admin optional aide_0.18.3-2.dsc
>  daf26d959ea0d8959b7baa0503afde1c 108084 admin optional
> aide_0.18.3-2.debian.tar.xz
>  11e957852ae8f61b674f7309ab02b8b6 6597 admin optional
> aide_0.18.3-2_source.buildinfo
>
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCAAdFiEE6QL5UJ/L0pcuNEbjj3cgEwEyBEIFAmSJ1aoACgkQj3cgEwEy
> BEJEog//XkGntXQvUVZ5mjAlF+Nl5C+thgQnH5SJeiUeI5RYc1sjWkS2slePIqHH
> pQpaq4bgAQgtDNie7wzNYW/KksonYBQrWwSjfMzbtYg6FUYWU3qY9aS398KiJe4V
> hZ5KdOwOzmmBYRI6Ewgfy+0ktnCWarXWdiPB5vuMZkzWf15oCCj+sBsgCMRcKYy5
> oMLgmiKdBegTvNkplD39kth0jvA6c+I1T38zWwWjrqmxBfp4ddaC8ai2m/ZO5E/x
> S9UfRzGNP3djqKspk6WjbfH1YjGA6ReiEaEgNNfACAtB9a1md45M7ztfZAns3d6f
> fJSi8DdTD4BHBSxsbwqtqi+inKY0ai8JxR1UCuiUsG6JHtqypL8GuVG1vgT7gqNr
> quxWg27xPf0PBKwVUU8NIL4gO+kQOaqwIf1hG4T2dsTsracox9/Pgj2QXuK/rghE
> cwIz5Frwi8ZmSqsk4G62NUShlBfY6dDGo3yNwM3+UR9IXpveZhUW/6npzPyG/dzV
> eEVvYYtXAbn/hlZy11GlUjDTr+KNffWqzmXN/wNDet/NnR+saqDKh2UrIrXIF9a3
> zqw2aCtWnA3b9IQQHDbvPPBhJdUskCzP4my96fAXGGlTxWX/1yUXDJLo1tDillFE
> i+2dnDm32o5mzvdTg9sjro98/Y6VqmaOJQ+8zcdA3OHYP1ERGSg=
> =D2zD
> -END PGP SIGNATURE-
>
>
> -- Forwarded message --
> From: Tomasz Ciolek 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Wed, 07 Jun 2023 08:41:49 +1000
> Subject: aide: fresh aide package install fails to add the requried _aide
> user to system
> Package: aide
> Version: 0.18.3-1
> Severity: serious
> Justification: 5.d
>
> Dear Maintainer,
>
> A fresh aide package install on debina buster fails to add the requried
> _aide user to system. This block the ability to run 'aideinit' script.
>
> While this is mentioned in /usr/share/doc/aide-common/README.Debian.gz
> there are no clear instrucntions as to whar range of UID/GID to give the
> _aide user when cerating them manually.
>

Bug#1038067: dash: fails to upgrade from -2 in debian:sid-slim image due to --path-exclude=/usr/share/man

[Helmut Grohne]

Package: dash
Version: 0.5.12-4
Severity: serious

Hi,

if you --path-exclude=/usr/share/man, dash fails to upgrade from -2.
Reproducer:

mmdebstrap trixie /dev/null --dpkgopt='path-exclude=/usr/share/man/*' 
--chrooted-customize-hook='sed -i -e s/trixie/sid/ /etc/apt/sources.list; 
apt-get update; apt-get -y install dash'

Unfortunately, this breaks upgrading docker images debian:sid-slim to
unstable at the moment and that breaks lots of CI jobs.

I guess it is the readlink that silently fails on the non-existent
manual page link. Probably, when that link doesn't exist and it is
diverted by dash, we should assume that it is ok-ish:

actualtarget=$(readlink "$dfile") || actualtarget=$ltarget

What do you think?

Helmut

Bug#1037974: marked as done (ddcci-dkms: code fails to build and package fails to install with Linux 6.3 headers)

[Debian Bug Tracking System]

Your message dated Thu, 15 Jun 2023 12:20:11 +
with message-id 
and subject line Bug#1037974: fixed in ddcci-driver-linux 0.4.3-2
has caused the Debian Bug report #1037974,
regarding ddcci-dkms: code fails to build and package fails to install with 
Linux 6.3 headers
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.)


-- 
1037974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ddcci-dkms
Version: 0.4.2-4
Severity: serious

When I try to install ddcci-dkms with the Linux 6.3 headers installed,
the build of the code fails and then the install of the package fails.

I think there are two problems here:

 * The code needs to be adapted to the latest Linux kernel version.
 * The package should not fail to install when the module build fails.
   This might be a problem in dkms itself, or in ddcci's integration.

I note that the combination of these issues also will break
installation of Linux 6.3 when ddcci-dkms is installed.

   $ sudo apt install ddcci-dkms 
   Reading package lists... Done
   Building dependency tree... Done
   Reading state information... Done
   The following NEW packages will be installed:
 ddcci-dkms
   0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
   Need to get 21.7 kB of archives.
   After this operation, 95.2 kB of additional disk space will be used.
   Get:1 https://deb.debian.org/debian testing/main amd64 ddcci-dkms all 
0.4.2-4 [21.7 kB]
   Fetched 21.7 kB in 1s (17.0 kB/s) 
   Retrieving bug reports... Done
   Parsing Found/Fixed information... Done
   Selecting previously unselected package ddcci-dkms.
   (Reading database ... 730615 files and directories currently installed.)
   Preparing to unpack .../ddcci-dkms_0.4.2-4_all.deb ...
   Unpacking ddcci-dkms (0.4.2-4) ...
   Setting up ddcci-dkms (0.4.2-4) ...
   Loading new ddcci-0.4.2 DKMS files...
   Building for 6.3.0-1-amd64
   Building initial module for 6.3.0-1-amd64
   Error! Bad return status for module build on kernel: 6.3.0-1-amd64 (x86_64)
   Consult /var/lib/dkms/ddcci/0.4.2/build/make.log for more information.
   dpkg: error processing package ddcci-dkms (--configure):
    installed ddcci-dkms package post-installation script subprocess returned 
error exit status 10
   Errors were encountered while processing:
    ddcci-dkms
   E: Sub-process /usr/bin/dpkg returned an error code (1)
   
   $ cat /var/lib/dkms/ddcci/0.4.2/build/make.log
   DKMS make.log for ddcci-0.4.2 for kernel 6.3.0-1-amd64 (x86_64)
   Thu 15 Jun 2023 10:23:01 AWST
   make: Entering directory '/var/lib/dkms/ddcci/0.4.2/build'
   make -C "ddcci"
   make[1]: Entering directory '/var/lib/dkms/ddcci/0.4.2/build/ddcci'
   make -C "/lib/modules/6.3.0-1-amd64/build" 
M="/var/lib/dkms/ddcci/0.4.2/build/ddcci" modules
   make[2]: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
 CC [M]  /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.o
   /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1053:27: error: initialization 
of ‘int (*)(const struct device *, struct kobj_uevent_env *)’ from incompatible 
pointer type ‘int (*)(struct device *, struct kobj_uevent_env *)’ 
[-Werror=incompatible-pointer-types]
    1053 | .uevent = ddcci_device_uevent,
 |   ^~~
   /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1053:27: note: (near 
initialization for ‘ddcci_device_type.uevent’)
   /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1056:27: error: initialization 
of ‘char * (*)(const struct device *, umode_t *, kuid_t *, kgid_t *)’ {aka 
‘char * (*)(const struct device *, short unsigned int *, kuid_t *, kgid_t *)’} 
from incompatible pointer type ‘char * (*)(struct device *, umode_t *, kuid_t 
*, kgid_t *)’ {aka ‘char * (*)(struct device *, short unsigned int *, kuid_t *, 
kgid_t *)’} [-Werror=incompatible-pointer-types]
    1056 | .devnode    = ddcci_devnode
 |   ^
   /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1056:27: note: (near 
initialization for ‘ddcci_device_type.devnode’)
   /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1062:27: error: initialization 
of ‘int (*)(const struct device *, struct kobj_uevent_env *)’ from incompatible 
pointer type ‘int (*)(struct device *, struct kobj_uevent_env *)’ 
[-Werror=incompatible-pointer-types]
    1062 | .uevent = ddcci_device_uevent,
 |   ^~~
   /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1062:27: note: (near 
initialization 

Bug#1038031: python3-migrate: python 3.11 compatiblity

[neonknight]

Package: python3-migrate
Version: 0.13.0-3
Severity: grave
Tags: patch
Justification: renders package unusable
X-Debbugs-Cc: debian-b...@neonknight.ch

Dear Maintainer,

When executing migrate on python 3.11 the following error is produced due to 
the deprecation of inspect.getargspec

  File 
"/nix/store/7a8iky58c7smv24ybgw4x592c9hn7rny-python3.11-sqlalchemy-migrate-0.13.0/lib/python3.11/site-packages/migrate/versioning/shell.py",
 line 111, in main
 f_args, f_varargs, f_kwargs, f_defaults = inspect.getargspec(command_func)
   ^^
AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean: 
'getargs'?


the fix is as simple as replacing line 111 of shell.py by:

f_args, f_varargs, f_kwargs, f_defaults, _, _, _ = 
inspect.getfullargspec(command_func)

Also see upstream project bug:
https://bugs.launchpad.net/sqlalchemy-migrate/+bug/2003619


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

Kernel: Linux 6.1.0-7-arm64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-migrate depends on:
ii  python3 3.11.2-1+b1
ii  python3-decorator   5.1.1-3
ii  python3-pbr 5.10.0-2
ii  python3-six 1.16.0-4
ii  python3-sqlalchemy  1.4.46+ds1-1
ii  python3-sqlparse0.4.2-1
ii  python3-tempita 0.5.2-7

python3-migrate recommends no packages.

Versions of packages python3-migrate suggests:
pn  python-migrate-doc  

-- no debconf information

Bug#1037977: marked as done (rust-ureq - update for base64 0.21)

[Debian Bug Tracking System]

Your message dated Thu, 15 Jun 2023 11:31:00 +
with message-id 
and subject line Bug#1037977: fixed in rust-ureq 2.7.0-1
has caused the Debian Bug report #1037977,
regarding rust-ureq - update for base64 0.21
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.)


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

Package: rust-ureq
Version: 2.6.2-3
Severity: serious
Tags: trixie, sid, patch, ftbfs

rust-base64 was recently updated to 0.21 making rust-ureq unbuildable and 
uninstallable.

Upstream already has a fix, I grabbed it and added it to the Debian package and 
it
built and passed autopkgtests fine.

Debdiff attached, I may or may not NMU this later.diff -Nru rust-ureq-2.6.2/debian/changelog rust-ureq-2.6.2/debian/changelog
--- rust-ureq-2.6.2/debian/changelog2023-02-12 16:16:54.0 +
+++ rust-ureq-2.6.2/debian/changelog2023-06-15 02:17:59.0 +
@@ -1,3 +1,10 @@
+rust-ureq (2.6.2-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply upstream patch for base64 0.21.
+
+ -- Peter Michael Green   Thu, 15 Jun 2023 02:17:59 +
+
 rust-ureq (2.6.2-3) unstable; urgency=medium
 
   * avoid initial dash in autopkgtest test name;
diff -Nru rust-ureq-2.6.2/debian/control rust-ureq-2.6.2/debian/control
--- rust-ureq-2.6.2/debian/control  2023-01-26 16:13:56.0 +
+++ rust-ureq-2.6.2/debian/control  2023-06-15 02:17:57.0 +
@@ -4,7 +4,7 @@
 Build-Depends:
  debhelper-compat (= 13),
  dh-cargo (>= 25),
- librust-base64-0.13+default-dev ,
+ librust-base64-0.21+default-dev ,
  librust-brotli-decompressor-2+default-dev ,
  librust-chunked-transfer-1+default-dev ,
  librust-cookie-0.16-dev ,
@@ -37,7 +37,7 @@
 Architecture: all
 Multi-Arch: foreign
 Depends:
- librust-base64-0.13+default-dev,
+ librust-base64-0.21+default-dev,
  librust-brotli-decompressor-2+default-dev,
  librust-chunked-transfer-1+default-dev,
  librust-cookie-0.16-dev,
diff -Nru rust-ureq-2.6.2/debian/patches/0001_base64.patch 
rust-ureq-2.6.2/debian/patches/0001_base64.patch
--- rust-ureq-2.6.2/debian/patches/0001_base64.patch1970-01-01 
00:00:00.0 +
+++ rust-ureq-2.6.2/debian/patches/0001_base64.patch2023-06-15 
02:16:54.0 +
@@ -0,0 +1,59 @@
+commit abda74c4d8d1235c6eddccafd3c4bd690dc10ea7
+Author: Martin Algesten 
+Date:   Mon Jan 30 23:39:55 2023 +0100
+
+Upgrade deps
+
+diff --git a/Cargo.toml b/Cargo.toml
+index 00dc9f0ea..418ae582b 100644
+--- a/Cargo.toml
 b/Cargo.toml
+@@ -26,7 +26,7 @@ gzip = ["flate2"]
+ brotli = ["brotli-decompressor"]
+ 
+ [dependencies]
+-base64 = "0.13"
++base64 = "0.21"
+ cookie = { version = "0.16", default-features = false, optional = true}
+ once_cell = "1"
+ url = "2"
+diff --git a/src/proxy.rs b/src/proxy.rs
+index ff9413917..0148904a1 100644
+--- a/src/proxy.rs
 b/src/proxy.rs
+@@ -1,3 +1,5 @@
++use base64::{prelude::BASE64_STANDARD, Engine};
++
+ use crate::error::{Error, ErrorKind};
+ 
+ /// Proxy protocol
+@@ -131,7 +133,7 @@ impl Proxy {
+ 
+ pub(crate) fn connect>(, host: S, port: u16) -> String 
{
+ let authorization = if self.use_authorization() {
+-let creds = base64::encode(format!(
++let creds = BASE64_STANDARD.encode(format!(
+ "{}:{}",
+ self.user.clone().unwrap_or_default(),
+ self.password.clone().unwrap_or_default()
+diff --git a/src/unit.rs b/src/unit.rs
+index 895067ff0..2011bb673 100644
+--- a/src/unit.rs
 b/src/unit.rs
+@@ -3,6 +3,7 @@ use std::io::{self, Write};
+ use std::ops::Range;
+ use std::time;
+ 
++use base64::{prelude::BASE64_STANDARD, Engine};
+ use log::debug;
+ use url::Url;
+ 
+@@ -87,7 +88,7 @@ impl Unit {
+ if (!username.is_empty() || !password.is_empty())
+ && get_header(, "authorization").is_none()
+ {
+-let encoded = base64::encode(format!("{}:{}", username, 
password));
++let encoded = BASE64_STANDARD.encode(format!("{}:{}", 
username, password));
+ extra.push(Header::new("Authorization", !("Basic {}", 
encoded)));
+ }
+ 
diff -Nru rust-ureq-2.6.2/debian/patches/series 
rust-ureq-2.6.2/debian/patches/series
--- rust-ureq-2.6.2/debian/patches/series   2023-01-26 16:08:45.0 
+
+++ rust-ureq-2.6.2/debian/patches/series   2023-06-15 02:17:14.0 
+
@@ -1,3 +1,4 @@
+0001_base64.patch
 2001_native_certs.patch
 2002_env_logger.patch
 2003_cookie-store.patch
--- 

Processed: user debian...@lists.debian.org, usertagging 1037974, tagging 1037974, found 1037974 in 0.4.3-1 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 1037974 piuparts
There were no usertags set.
Usertags are now: piuparts.
> tags 1037974 + sid trixie
Bug #1037974 [ddcci-dkms] ddcci-dkms: code fails to build and package fails to 
install with Linux 6.3 headers
Added tag(s) trixie and sid.
> found 1037974 0.4.3-1
Bug #1037974 [ddcci-dkms] ddcci-dkms: code fails to build and package fails to 
install with Linux 6.3 headers
Marked as found in versions ddcci-driver-linux/0.4.3-1.
> severity 1034881 serious
Bug #1034881 [falcosecurity-scap-dkms] falcosecurity-scap-dkms: Cannot compile 
linux kernel 6.2.12 due to failure with scap dkms
Severity set to 'serious' from 'important'
> usertags 1034881 piuparts
There were no usertags set.
Usertags are now: piuparts.
> tags 1034881 + sid trixie
Bug #1034881 [falcosecurity-scap-dkms] falcosecurity-scap-dkms: Cannot compile 
linux kernel 6.2.12 due to failure with scap dkms
Added tag(s) sid and trixie.
> tags 1038004 + sid trixie
Bug #1038004 [nvidia-tesla-470-kernel-dkms] nvidia-tesla-470-kernel-dkms: fails 
to build with kernel 6.3.0-1-amd64
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Bug#1038009: zfs-dkms: module fails to build for Linux 6.3

[Andreas Beckmann]

Package: zfs-dkms
Version: 2.1.11-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts

Running the pre_build script:
checking for gawk... gawk
checking metadata... META file
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether make supports nested variables... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking whether make sets $(MAKE)... yes
checking how to print strings... printf
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc-12
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc-12 accepts -g... yes
checking for gcc-12 option to enable C11 features... none needed
checking whether gcc-12 understands -c and -o together... yes
checking dependency style of gcc-12... none
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc-12... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for file... file
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc-12 object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc-12 supports -fno-rtti -fno-exceptions... no
checking for gcc-12 option to produce PIC... -fPIC -DPIC
checking if gcc-12 PIC flag -fPIC -DPIC works... yes
checking if gcc-12 static flag -static works... yes
checking if gcc-12 supports -c -o file.o... yes
checking if gcc-12 supports -c -o file.o... (cached) yes
checking whether the gcc-12 linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for gcc... (cached) gcc-12
checking whether the compiler supports GNU C... (cached) yes
checking whether gcc-12 accepts -g... (cached) yes
checking for gcc-12 option to enable C11 features... (cached) none needed
checking whether gcc-12 understands -c and -o together... (cached) yes
checking dependency style of gcc-12... (cached) none
checking whether ln -s works... yes
checking for pkg-config... no
checking dependency style of gcc-12... none
checking whether to build with code coverage support... no
checking how to create a pax tar archive... gnutar
checking zfs author... OpenZFS
checking zfs license... CDDL
checking whether NLS is requested... yes
checking for msgfmt... no
checking for gmsgfmt... :
checking for xgettext... no
checking for msgmerge... no
checking for ld... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking for shared library run path origin... done
checking 32-bit host C ABI... no
checking for the common suffixes of directories in the library search path... 
lib,lib
checking zfs config... kernel
checking the 

Bug#1038005: vpoll-dkms: module fails to build for Linux 6.3

[Andreas Beckmann]

Package: vpoll-dkms
Version: 0.1-3
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts


DKMS make.log for vpoll-0.1 for kernel 6.3.0-1-amd64 (x86_64)
Thu Jun 15 10:27:14 UTC 2023
make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
  CC [M]  /var/lib/dkms/vpoll/0.1/build/vpoll.o
/var/lib/dkms/vpoll/0.1/build/vpoll.c: In function 'myinit':
/var/lib/dkms/vpoll/0.1/build/vpoll.c:117:38: error: assignment to 'char * 
(*)(const struct device *, umode_t *)' {aka 'char * (*)(const struct device *, 
short unsigned int *)'} from incompatible pointer type 'char * (*)(struct 
device *, umode_t *)' {aka 'char * (*)(struct device *, short unsigned int *)'} 
[-Werror=incompatible-pointer-types]
  117 | vpoll_class->devnode = vpoll_devnode;
  |  ^
cc1: some warnings being treated as errors
make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.build:257: 
/var/lib/dkms/vpoll/0.1/build/vpoll.o] Error 1
make: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2050: 
/var/lib/dkms/vpoll/0.1/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.3.0-1-amd64'


Andreas

Bug#1038003: xtrx-dkms: module fails to build for Linux 6.3: error: assignment of read-only member 'vm_flags'

[Andreas Beckmann]

Package: xtrx-dkms
Version: 0.0.1+git20190320.5ae3a3e-3.2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts

related to this kernel change: bc292ab00f6c ("mm: introduce vma->vm_flags 
wrapper functions")

DKMS make.log for xtrx-0.0.1+git20190320.5ae3a3e-3.2 for kernel 6.3.0-1-amd64 
(x86_64)
Thu Jun 15 10:23:22 UTC 2023
make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
  CC [M]  /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.o
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c: In function 
'xtrxfd_mmap':
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c:1075:31: error: 
assignment of read-only member 'vm_flags'
 1075 | vma->vm_flags |= VM_LOCKED;
  |   ^~
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c:1090:31: error: 
assignment of read-only member 'vm_flags'
 1090 | vma->vm_flags |= VM_IO;
  |   ^~
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c:1115:31: error: 
assignment of read-only member 'vm_flags'
 1115 | vma->vm_flags |= VM_LOCKED;
  |   ^~
make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.build:257: 
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.o] Error 1
make: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2050: 
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.3.0-1-amd64'


Andreas

Bug#1038002: openafs-modules-dkms: module fails to build for Linux 6.3: error: invalid use of undefined type 'struct file_lock'

[Andreas Beckmann]

Package: openafs-modules-dkms
Version: 1.8.9-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts


DKMS make.log for openafs-1.8.9 for kernel 6.3.0-1-amd64 (x86_64)
Thu Jun 15 10:14:08 UTC 2023
checking for gcc... gcc-12
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc-12 accepts -g... yes
checking for gcc-12 option to enable C11 features... none needed
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc-12 options needed to detect all undeclared functions... none 
needed
checking how to run the C preprocessor... gcc-12 -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for pkg-config... no
checking for libxslt... no
checking for saxon... no
checking for xalan-j... no
checking for xsltproc... no
checking for fop... no
checking for dblatex... no
checking for docbook2pdf... no
configure: WARNING: Docbook stylesheets not found; some documentation can't be 
built
checking for kindlegen... no
checking for doxygen... no
checking for dot... no
checking for library containing strerror... none required
checking for pid_t... yes
checking for size_t... yes
checking whether ln -s works... yes
checking for ranlib... ranlib
checking for bison... no
checking for byacc... no
checking for flex... no
checking for lex... no
checking if lex is flex... yes
checking whether byte order is known at compile time... yes
checking whether byte ordering is bigendian... no
checking whether printf understands the %z length modifier... yes
checking your OS... linux
checking for ranlib... (cached) ranlib
checking for as... as
checking for mv... mv
checking for rm... rm
checking for ld... ld
checking for cp... cp
checking for gencat... gencat
checking whether C compiler accepts -fno-strict-aliasing... yes
checking whether C compiler accepts -fno-strength-reduce... yes
checking whether C compiler accepts -fno-common... yes
checking whether C compiler accepts -pipe... yes
checking if linux kbuild requires EXTRA_CFLAGS... no
checking if linux kernel module build works... yes
checking operation follow_link in inode_operations... no
checking operation put_link in inode_operations... no
checking operation rename in inode_operations... no
checking operation create in inode_operations... no
checking for linux/cred.h... yes
checking for linux/config.h... no
checking for linux/exportfs.h... yes
checking for linux/freezer.h... yes
checking for linux/key-type.h... yes
checking for linux/semaphore.h... yes
checking for linux/seq_file.h... yes
checking for linux/sched/signal.h... yes
checking for linux/uaccess.h... yes
checking for linux/stdarg.h... yes
checking for struct vfs_path... no
checking for kuid_t... yes
checking for struct proc_ops... yes
checking for time_t... no
checking for backing_dev_info in struct address_space... no
checking for write_begin in struct address_space_operations... yes
checking for dirty_folio in struct address_space_operations... yes
checking for readahead in struct address_space_operations... yes
checking for read_folio in struct address_space_operations... yes
checking for name in struct backing_dev_info... no
checking for session_keyring in struct cred... yes
checking for ctl_name in struct ctl_table... no
checking for d_u.d_alias in struct dentry... yes
checking for d_automount in struct dentry_operations... yes
checking for gid in struct group_info... yes
checking for i_alloc_sem in struct inode... no
checking for i_blkbits in struct inode... yes
checking for i_blksize in struct inode... no
checking for i_mutex in struct inode... no
checking for i_security in struct inode... yes
checking for f_path in struct file... yes
checking for flock in struct file_operations... yes
checking for iterate in struct file_operations... yes
checking for read_iter in struct file_operations... yes
checking for sendfile in struct file_operations... no
checking for mount in struct file_system_type... yes
checking for truncate in struct inode_operations... no
checking for get_link in struct inode_operations... yes
checking for payload.value in struct key... no
checking for instantiate_prep in struct key_type... no
checking for match_preparse in struct key_type... yes
checking for preparse in struct key_type... yes
checking for msg_iter in struct msghdr... yes
checking for path in struct nameidata... no

Bug#1038001: librem-ec-acpi-dkms: module fails to build for Linux 6.3

[Andreas Beckmann]

Package: librem-ec-acpi-dkms
Version: 0.9.1-4
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts


DKMS make.log for librem_ec_acpi-0.9.1 for kernel 6.3.0-1-amd64 (x86_64)
Thu Jun 15 10:09:49 UTC 2023
make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
  CC [M]  /var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.o
/var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:276:24: error: 
initialization of 'int (*)(struct power_supply *, struct acpi_battery_hook *)' 
from incompatible pointer type 'int (*)(struct power_supply *)' 
[-Werror=incompatible-pointer-types]
  276 | .add_battery = librem_ec_battery_add,
  |^
/var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:276:24: note: (near 
initialization for 'librem_ec_battery_hook.add_battery')
/var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:277:27: error: 
initialization of 'int (*)(struct power_supply *, struct acpi_battery_hook *)' 
from incompatible pointer type 'int (*)(struct power_supply *)' 
[-Werror=incompatible-pointer-types]
  277 | .remove_battery = librem_ec_battery_remove,
  |   ^~~~
/var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:277:27: note: (near 
initialization for 'librem_ec_battery_hook.remove_battery')
/var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:773:27: error: 
initialization of 'void (*)(struct acpi_device *)' from incompatible pointer 
type 'int (*)(struct acpi_device *)' [-Werror=incompatible-pointer-types]
  773 | .remove = librem_ec_remove,
  |   ^~~~
/var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:773:27: note: (near 
initialization for 'librem_ec_driver.ops.remove')
cc1: some warnings being treated as errors
make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.build:257: 
/var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.o] Error 1
make: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2050: 
/var/lib/dkms/librem_ec_acpi/0.9.1/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.3.0-1-amd64'


Andreas

Bug#1037999: jool-dkms: module fails to build for Linux 6.3

[Andreas Beckmann]

Package: jool-dkms
Version: 4.1.9-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts


DKMS make.log for jool-dkms-4.1.9 for kernel 6.3.0-1-amd64 (x86_64)
Thu Jun 15 10:07:23 UTC 2023
make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc7915/4to6.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc7915/6to4.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc7915/common.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/address_xlat.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc7915/core.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/dev.o
  CC [M]  
/var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/kernel_hook_netfilter.o
  CC [M]  
/var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/kernel_hook_iptables.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/log.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/address.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/atomic_config.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/icmp_wrapper.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/init.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/ipv6_hdr_iterator.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/joold.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/packet.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc6052.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rtrie.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/stats.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/types.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/translation_state.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/route_out.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/skbuff.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/core.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/error_pool.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/timer.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/trace.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/wkmalloc.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/wrapper-config.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/wrapper-global.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/wrapper-types.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/xlator.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/steps/send_packet.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/address.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/atomic_config.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/attribute.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_handler.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_core.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/bib.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/denylist4.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/eam.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/global.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/instance.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/joold.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_common.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/pool4.o
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/session.o
/var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_handler.c:205:21: 
error: initialization of 'int (*)(const struct genl_split_ops *, struct sk_buff 
*, struct genl_info *)' from incompatible pointer type 'int (*)(const struct 
genl_ops *, struct sk_buff *, struct genl_info *)' 
[-Werror=incompatible-pointer-types]
  205 | .pre_doit = pre_handle_request,
  | ^~
/var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_handler.c:205:21: 
note: (near initialization for 'jool_family.pre_doit')
/var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_handler.c:206:22: 
error: initialization of 'void (*)(const struct genl_split_ops *, struct 
sk_buff *, struct genl_info *)' from incompatible pointer type 'void (*)(const 
struct genl_ops *, struct sk_buff *, struct genl_info *)' 
[-Werror=incompatible-pointer-types]
  206 | .post_doit = post_handle_request,
  |  ^~~
/var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_handler.c:206:22: 
note: (near initialization for 'jool_family.post_doit')
  CC [M]  /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/stats.o
cc1: some warnings being treated as errors
make[1]: *** 

Bug#1037998: gost-crypto-dkms: module fails to build for Linux 6.3: error: implicit declaration of function 'crypto_tfm_ctx'

[Andreas Beckmann]

Package: gost-crypto-dkms
Version: 0.3.4-4
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts


DKMS make.log for gost-crypto-0.3.4 for kernel 6.3.0-1-amd64 (x86_64)
Thu Jun 15 10:04:49 UTC 2023
make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
  CC [M]  /var/lib/dkms/gost-crypto/0.3.4/build/gost28147_basic.o
  CC [M]  /var/lib/dkms/gost-crypto/0.3.4/build/gost28147_modes.o
  CC [M]  /var/lib/dkms/gost-crypto/0.3.4/build/gosthash94_generic.o
  CC [M]  /var/lib/dkms/gost-crypto/0.3.4/build/kuznyechik_generic.o
  CC [M]  /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.o
  CC [M]  /var/lib/dkms/gost-crypto/0.3.4/build/streebog_generic.o
  CC [M]  /var/lib/dkms/gost-crypto/0.3.4/build/testmgr.o
  CC [M]  /var/lib/dkms/gost-crypto/0.3.4/build/gost-test-main.o
/var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c: In function 
'magma_set_key':
/var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c:25:40: error: implicit 
declaration of function 'crypto_tfm_ctx' [-Werror=implicit-function-declaration]
   25 | struct crypto_magma_ctx *ctx = crypto_tfm_ctx(tfm);
  |^~
/var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c:25:40: warning: 
initialization of 'struct crypto_magma_ctx *' from 'int' makes pointer from 
integer without a cast [-Wint-conversion]
/var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c: In function 
'magma_encrypt':
/var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c:39:46: warning: 
initialization of 'const struct crypto_magma_ctx *' from 'int' makes pointer 
from integer without a cast [-Wint-conversion]
   39 | const struct crypto_magma_ctx *ctx = crypto_tfm_ctx(tfm);
  |  ^~
/var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c: In function 
'magma_decrypt':
/var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c:52:46: warning: 
initialization of 'const struct crypto_magma_ctx *' from 'int' makes pointer 
from integer without a cast [-Wint-conversion]
   52 | const struct crypto_magma_ctx *ctx = crypto_tfm_ctx(tfm);
  |  ^~
cc1: some warnings being treated as errors
make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.build:257: 
/var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.o] Error 1
make[1]: *** Waiting for unfinished jobs
make: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2050: 
/var/lib/dkms/gost-crypto/0.3.4/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.3.0-1-amd64'


Andreas

Bug#1037997: evdi-dkms: module fails to build for Linux 6.3: error: implicit declaration of function 'drm_encoder_cleanup'

[Andreas Beckmann]

Package: evdi-dkms
Version: 1.12.0+dfsg-0.3
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts


DKMS make.log for evdi-1.12.0+dfsg for kernel 6.3.0-1-amd64 (x86_64)
Thu Jun 15 09:56:32 UTC 2023
make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_drv.o
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_dev.o
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_sysfs.o
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_modeset.o
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_connector.o
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.o
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.o
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_fb.o
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_gem.o
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_painter.o
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_params.o
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_cursor.o
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_debug.o
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o
  CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_ioc32.o
In file included from /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_connector.c:19:
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.h:196:72: warning: 'struct 
i2c_msg' declared inside parameter list will not be visible outside of this 
definition or declaration
  196 | bool evdi_painter_i2c_data_notify(struct evdi_painter *painter, struct 
i2c_msg *msg);
  |
^~~
In file included from /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:21:
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.h:196:72: warning: 'struct 
i2c_msg' declared inside parameter list will not be visible outside of this 
definition or declaration
  196 | bool evdi_painter_i2c_data_notify(struct evdi_painter *painter, struct 
i2c_msg *msg);
  |
^~~
In file included from 
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_dev.c:30:
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.h:196:72: warning: 'struct 
i2c_msg' declared inside parameter list will not be visible outside of this 
definition or declaration
  196 | bool evdi_painter_i2c_data_notify(struct evdi_painter *painter, struct 
i2c_msg *msg);
  |
^~~
In file included from /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_gem.c:24:
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.h:196:72: warning: 'struct 
i2c_msg' declared inside parameter list will not be visible outside of this 
definition or declaration
  196 | bool evdi_painter_i2c_data_notify(struct evdi_painter *painter, struct 
i2c_msg *msg);
  |
^~~
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c: In function 
'evdi_enc_destroy':
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:26:9: error: implicit 
declaration of function 'drm_encoder_cleanup'; did you mean 'drm_crtc_cleanup'? 
[-Werror=implicit-function-declaration]
   26 | drm_encoder_cleanup(encoder);
  | ^~~
  | drm_crtc_cleanup
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c: At top level:
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:38:21: error: variable 
'evdi_enc_helper_funcs' has initializer but incomplete type
   38 | static const struct drm_encoder_helper_funcs evdi_enc_helper_funcs = {
  | ^~~~
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:39:10: error: 'const struct 
drm_encoder_helper_funcs' has no member named 'enable'
   39 | .enable = evdi_encoder_enable,
  |  ^~
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:39:19: warning: excess 
elements in struct initializer
   39 | .enable = evdi_encoder_enable,
  |   ^~~
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:39:19: note: (near 
initialization for 'evdi_enc_helper_funcs')
In file included from /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_cursor.c:33:
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.h:196:72: warning: 'struct 
i2c_msg' declared inside parameter list will not be visible outside of this 
definition or declaration
  196 | bool evdi_painter_i2c_data_notify(struct evdi_painter *painter, struct 
i2c_msg *msg);
  |
^~~
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:40:10: error: 'const struct 
drm_encoder_helper_funcs' has no member named 'disable'
   40 | .disable = evdi_encoder_disable
  |  ^~~
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:40:20: warning: excess 
elements in struct 

Bug#1037995: digimend-dkms: module fails to build for Linux 6.3: error: implicit declaration of function 'hid_is_using_ll_driver'

[Andreas Beckmann]

Package: digimend-dkms
Version: 11-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts

DKMS make.log for digimend-11 for kernel 6.3.0-1-amd64 (x86_64)
Thu Jun 15 09:51:43 UTC 2023
make -C /lib/modules/6.3.0-1-amd64/build M=/var/lib/dkms/digimend/11/build 
modules
make[1]: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
  CC [M]  /var/lib/dkms/digimend/11/build/hid-kye.o
  CC [M]  /var/lib/dkms/digimend/11/build/hid-uclogic-core.o
  CC [M]  /var/lib/dkms/digimend/11/build/hid-uclogic-rdesc.o
  CC [M]  /var/lib/dkms/digimend/11/build/hid-uclogic-params.o
  CC [M]  /var/lib/dkms/digimend/11/build/hid-polostar.o
  CC [M]  /var/lib/dkms/digimend/11/build/hid-viewsonic.o
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c: In function 
'uclogic_params_init':
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1227:17: error: implicit 
declaration of function 'hid_is_using_ll_driver' 
[-Werror=implicit-function-declaration]
 1227 | || !hid_is_using_ll_driver(hdev, _hid_driver)
  | ^~
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1227:47: error: 
'usb_hid_driver' undeclared (first use in this function); did you mean 
'to_hid_driver'?
 1227 | || !hid_is_using_ll_driver(hdev, _hid_driver)
  |   ^~
  |   to_hid_driver
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1227:47: note: each 
undeclared identifier is reported only once for each function it appears in
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1349:20: warning: this 
statement may fall through [-Wimplicit-fallthrough=]
 1349 | if (bNumInterfaces != 3) {
  |^
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1367:9: note: here
 1367 | case VID_PID(USB_VENDOR_ID_HUION,
  | ^~~~
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.build:257: 
/var/lib/dkms/digimend/11/build/hid-uclogic-params.o] Error 1
make[2]: *** Waiting for unfinished jobs
make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2050: 
/var/lib/dkms/digimend/11/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.3.0-1-amd64'
make: *** [Makefile:25: modules] Error 2


Andreas

Bug#1037993: dahdi-dkms: module fails to build for Linux 6.3

[Andreas Beckmann]

Package: dahdi-dkms
Version: 1:2.11.1.0.20170917~dfsg-8.4
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts


DKMS make.log for dahdi-2.11.1.0.20170917 for kernel 6.3.0-1-amd64 (x86_64)
Thu Jun 15 09:40:51 UTC 2023
make -C /lib/modules/6.3.0-1-amd64/build 
KBUILD_EXTMOD=/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi 
DAHDI_INCLUDE=/var/lib/dkms/dahdi/2.11.1.0.20170917/build/include 
DAHDI_MODULES_EXTRA="dahdi_dummy.o dahdi_echocan_oslec.o " HOTPLUG_FIRMWARE=yes 
modules DAHDI_BUILD_ALL=m
make[1]: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_adpcm_chan.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_channel.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_open.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_stats.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_conf_bridge.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_debug.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_events.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_interrupts.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_memory.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_miscellaneous.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_mixer.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_phasing_tsst.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_playout_buf.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_remote_debug.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tlv.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tone_detection.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tsi_cnct.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tsst.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/apilib/bt/octapi_bt0.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/apilib/largmath/octapi_largmath.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/apilib/llman/octapi_llman.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/oct612x-user.o
  LD [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/oct612x.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wct4xxp/base.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wct4xxp/vpm450m.o
  LD [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wct4xxp/wct4xxp.o
  CC [M]  
/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wctc4xxp/base.o
In file included from 
/usr/src/linux-headers-6.3.0-1-common/include/linux/string.h:254,
 from 
/usr/src/linux-headers-6.3.0-1-common/include/linux/bitmap.h:11,
 from 
/usr/src/linux-headers-6.3.0-1-common/include/linux/cpumask.h:12,
 from 
/usr/src/linux-headers-6.3.0-1-common/arch/x86/include/asm/paravirt.h:17,
 from 
/usr/src/linux-headers-6.3.0-1-common/arch/x86/include/asm/cpuid.h:62,
 from 
/usr/src/linux-headers-6.3.0-1-common/arch/x86/include/asm/processor.h:19,
 from 
/usr/src/linux-headers-6.3.0-1-common/arch/x86/include/asm/timex.h:5,
 from 
/usr/src/linux-headers-6.3.0-1-common/include/linux/timex.h:67,
 from 
/usr/src/linux-headers-6.3.0-1-common/include/linux/time32.h:13,
 from 
/usr/src/linux-headers-6.3.0-1-common/include/linux/time.h:60,
 from 
/usr/src/linux-headers-6.3.0-1-common/include/linux/stat.h:19,
 from 
/usr/src/linux-headers-6.3.0-1-common/include/linux/module.h:13,
 from 

Processed: tagging 1037322

[Debian Bug Tracking System]

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

> tags 1037322 + upstream
Bug #1037322 [amqp-tools] amqp-tools: Process leaks authentication data
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1037172: marked as done (unixodbc-common,odbcinst: missing Breaks+Replaces: odbcinst1debian1)

[Debian Bug Tracking System]

Your message dated Thu, 15 Jun 2023 08:39:05 +
with message-id 
and subject line Bug#1037172: fixed in unixodbc 2.3.11-3
has caused the Debian Bug report #1037172,
regarding unixodbc-common,odbcinst: missing Breaks+Replaces: odbcinst1debian1
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.)


-- 
1037172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unixodbc-common,odbcinst
Version: 2.3.11-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libsqliteodbc

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'lenny' to 'squeeze' to 'wheezy' to 'jessie' to 'stretch' to 'buster' to
'bullseye' to 'bookworm'.
It installed fine in 'lenny', and upgraded to 'squeeze', 'wheezy',
'jessie', 'stretch', 'buster', and 'bullseye' successfully,
but then the upgrade to 'bookworm' failed.

In case the package was not part of an intermediate stable release,
the version from the preceding stable release was kept installed.

>From the attached log (scroll to the bottom...):

...
  Selecting previously unselected package unixodbc-common.
  Preparing to unpack .../22-unixodbc-common_2.3.11-2_all.deb ...
  Unpacking unixodbc-common (2.3.11-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-JsWDst/22-unixodbc-common_2.3.11-2_all.deb (--unpack):
   trying to overwrite '/etc/odbc.ini', which is also in package 
odbcinst1debian1 2.2.11-16
...
  Selecting previously unselected package odbcinst.
  Preparing to unpack .../25-odbcinst_2.3.11-2_amd64.deb ...
  Unpacking odbcinst (2.3.11-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-JsWDst/25-odbcinst_2.3.11-2_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/odbcinst', which is also in package 
odbcinst1debian1 2.2.11-16
...
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-JsWDst/22-unixodbc-common_2.3.11-2_all.deb
   /tmp/apt-dpkg-install-JsWDst/25-odbcinst_2.3.11-2_amd64.deb

The mentioned Breaks+Replaces may have been there in the past,
but on some upgrade paths originating in lenny the obsolete packages may
have survived without being affected by B+R so far.

(In the concrete case, libsqliteodbc/lenny had a dependency on
odbcinst1debian1, libsqliteodbc/bookworm has a dependency on odbcinst
while in all releases inbetween there was no pdenedency on an *odbc*
package at all.)


cheers,

Andreas


libsqliteodbc_0.9998-3+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: unixodbc
Source-Version: 2.3.11-3
Done: Hugh McMaster 

We believe that the bug you reported is fixed in the latest version of
unixodbc, 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.
Hugh McMaster  (supplier of updated unixodbc 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, 15 Jun 2023 18:00:48 +1000
Source: unixodbc
Architecture: source
Version: 2.3.11-3
Distribution: unstable
Urgency: medium
Maintainer: Hugh McMaster 
Changed-By: Hugh McMaster 
Closes: 1009152 1037172
Changes:
 unixodbc (2.3.11-3) unstable; urgency=medium
 .
   * debian/control:
 + Update Maintainer email address.
 + Raise Standards-Version to 4.6.2 (no changes needed).
 + Update Homepage field.
 + Drop transitional packages (libodbc1, odbcinst1debian2).
 + unixodbc-common, odbcinst: Add Breaks+Replaces against odbcinst1debian1
   (Closes: #1037172).
   * debian/copyright: Update Source field and update for 2023.
   * unixodbc-common: Remove obsolete conffile (Closes: #1009152).
   * debian/upstream/metadata: Update Documentation field.
Checksums-Sha1:
 704755f52ecc502fa0bc116bab1b7ee126bad217 2228 unixodbc_2.3.11-3.dsc
 9f703ab86c2bd2881a3c814a689e3c1421bea9aa 16804 unixodbc_2.3.11-3.debian.tar.xz
 f82bf3d8be44524ab5d9f376ffaa75f9a57566ae 9127 unixodbc_2.3.11-3_amd64.buildinfo
Checksums-Sha256:
 f4d8e7d83a0779c9d57d147b7590a3584a279d7d3acb30b7e1bcf93bff58cac9 2228 
unixodbc_2.3.11-3.dsc
 

Bug#1037985: godot: FTBFS om s390 (missing #include )

[Petter Reinholdtsen]

Package: src:godot
Version: 3.5.1-stable-2
Severity: serious

The latest source fail to build on s390x.  This is the build error from
https://buildd.debian.org/status/fetch.php?pkg=godot=s390x=3.5.1-stable-2=1686780159=0
 >:

  Compiling ==> thirdparty/embree/common/sys/sysinfo.cpp
  In file included from thirdparty/embree/common/sys/sysinfo.cpp:5:
  thirdparty/embree/common/sys/intrinsics.h:15:10: fatal error: immintrin.h: No 
such file or directory
 15 | #include 
|  ^
  compilation terminated.
  scons: *** [thirdparty/embree/common/sys/sysinfo.x11.opt.tools.64.o] Error 1
  scons: building terminated because of errors.
  [Time elapsed: 00:04:55.241]
  make[1]: *** [debian/rules:83: override_dh_auto_build] Error 2

A similar build error occured with version 3.5.1-stable-1 reported as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031132 > with
the build log in
https://buildd.debian.org/status/fetch.php?pkg=godot=s390x=3.5.1-stable-1=1675605014=0
 >:

  Compiling ==> thirdparty/oidn/core/api.cpp
  In file included from thirdparty/oidn/core/common.h:19,
   from thirdparty/oidn/core/device.h:19,
   from thirdparty/oidn/core/api.cpp:48:
  thirdparty/oidn/common/platform.h:27:10: fatal error: xmmintrin.h: No such 
file or directory
 27 | #include 
|  ^
  compilation terminated.
  scons: *** [thirdparty/oidn/core/api.x11.opt.tools.64.o] Error 1
  scons: building terminated because of errors.
  [Time elapsed: 00:01:47.982]
  make[1]: *** [debian/rules:66: override_dh_auto_build] Error 2

The "solution" then was to disable the module that failed to build on
any non x86 and arm platform.  Perhaps some other module need to be
disabled on s390x?

Setting severity serious as this build problem will block the package
from entering testing.

-- 
Happy hacking
Petter Reinholdtsen

Bug#1037977: rust-ureq - update for base64 0.21

[Jonas Smedegaard]

Quoting Peter Green (2023-06-15 06:35:02)
> rust-base64 was recently updated to 0.21 making rust-ureq unbuildable and 
> uninstallable.
> 
> Upstream already has a fix, I grabbed it and added it to the Debian package 
> and it
> built and passed autopkgtests fine.
> 
> Debdiff attached, I may or may not NMU this later.

Thanks for the report.

Instead of using the provided patch, I have prepared an upgrade to
newest upstream release which includes this change.

Unfortunately I am not yet able to build that, due to base64 upgrade
also affecting rust-rustls-pemfile and rust-cookie - which you already
know and have dealt with earlier today.

In future, I recommend to more cautiously release backwards-incompatible
package upgrades: First release to experimental as a NEW package, then
when approved by ftpmasters re-release to unstable, then when no longer
wanting to maintain the older branch) file RC bugs against all reverse
dependencies of the older package, and when none of those are in testing
(which happens automatically after some time for packages with RC bugs)
request removal from testing of the old package, and then later from
unstable as well.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Processed: Re: amqp-tools: Process leaks authentication data

[Debian Bug Tracking System]

Processing control commands:

> tag -1 fixed-upstream
Bug #1037322 [amqp-tools] amqp-tools: Process leaks authentication data
Added tag(s) fixed-upstream.

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

Bug#1037322: amqp-tools: Process leaks authentication data

[Christian Kastner]

Control: tag -1 fixed-upstream

On 2023-06-11 12:28, Christian Kastner wrote:
> Package: amqp-tools
> Version: 0.11.0-1
> Severity: grave
> Tags: security
> Forwarded: https://github.com/alanxz/rabbitmq-c/issues/575
> 
> When passing authentication data with either --password or --url, the
> data is exposed in the process list, where it can be seen by any user.
> 
> Example:
>   $ pgrep -a ampq-consume
>   62287 amqp-consume --url amqp://user:pass@192.168.0.1 --queue=myqueue
> 
> This is an upstream issue. I've filed a pull request upstream that adds
> an option --authfile with which authentication data can be read from a file.

A patch for this has been merged upstream:

https://github.com/alanxz/rabbitmq-c/commit/463054383fbeef889b409a7f843df5365288e2a0

Best,
Christian

Processed: found

[Debian Bug Tracking System]

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

> found 1037322 0.9.0-0.2
Bug #1037322 [amqp-tools] amqp-tools: Process leaks authentication data
Marked as found in versions librabbitmq/0.9.0-0.2.
>
End of message, stopping processing here.

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

Bug#1037982: libnet-route-perl needs dependency net-tools for system route command.

[Salvatore Bonaccorso]

Package: libnet-route-perl
Version: 0.02-3
Severity: serious
X-Debbugs-CC: Craig Manley 

As reported by Craig:

On Wed, Jun 14, 2023 at 12:33:44PM +0200, Craig Manley wrote:
> Hello,
> 
> Our builds were failing because libnet-route-perl called the missing system
> command /sbin/route which is provided by net-tools. That package isn't
> listed in the Depends list.
> 
> -Craig Manley

Regards,
Salvatore

Bug#1037974: ddcci-dkms: code fails to build and package fails to install with Linux 6.3 headers

[Tomas Jura]

Hi

I successfully applied patch from 
https://aur.archlinux.org/packages/ddcci-driver-linux-dkms and compiled 
without error.


Tomas