Bug#1073480: Fwd: zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd

[yokota]

Hello Debian Qt/KDE Maintainers,

I think Debian bug 1073480 is not a libzstd's bug but qt6-base's bug.

Please examine this bug report and my forwarded message below.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073480

--
YOKOTA Hiroshi

-- Forwarded message -
Subject: Re: zstdTargets.cmake: missing targets zstd::libzstd_shared,
zstd::libzstd_static, zstd::libzstd
To: <1073...@bugs.debian.org>

Hello,

I think this bug is not a libzstd's bug but qt6-base's bug.

Please check this QTBUG.
> [#QTBUG-119469] Targets not yet defined: zstd::libzstd_static
> https://bugreports.qt.io/browse/QTBUG-119469

The QTBUG said this bug was fixed in Qt 6.7.2, so update Qt to 6.7.2
will fixes the problem.

Or, back port QTBUG-119469 fix from git commits.
> https://code.qt.io/cgit/qt/qtbase.git/log/?qt=grep=QTBUG-119469

PS:
Arch Linux also have this bug.
> https://gitlab.archlinux.org/archlinux/packaging/packages/qt6-doc/-/issues/1
--
YOKOTA Hiroshi

Bug#1071314: marked as done (heartbeat: FTBFS: dh_install: warning: Cannot find (any matches for) "/heartbeat.service")

[Debian Bug Tracking System]

Your message dated Thu, 27 Jun 2024 03:34:11 +
with message-id 
and subject line Bug#1071314: fixed in heartbeat 1:3.0.6-14.2
has caused the Debian Bug report #1071314,
regarding heartbeat: FTBFS: dh_install: warning: Cannot find (any matches for) 
"/heartbeat.service"
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.)


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

Package: src:heartbeat
Version: 1:3.0.6-14.1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules build
dh_testdir
# Only bootstrap as neccessary
if test -e ./configure -a ! -x ./configure; then\
chmod u+x ./configure;  \
fi
if test -e ./py-compile -a ! -x ./py-compile; then  \
chmod u+x ./py-compile; \
fi
test ! -x ./configure || /bin/bash ./configure PING=/bin/ping 
IFCONFIG=/sbin/ifconfig IP2UTIL=/sbin/ip PYTHON=/usr/bin/python3 --prefix=/usr 
--sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/libexec 
--mandir=/usr/share/man --disable-crm --with-group-name=haclient 
--with-ccmuser-name=hacluster --enable-libc-malloc --disable-fatal-warnings;
test -x ./configure || /bin/bash ./bootstrap PING=/bin/ping 
IFCONFIG=/sbin/ifconfig IP2UTIL=/sbin/ip PYTHON=/usr/bin/python3 --prefix=/usr 
--sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/libexec 
--mandir=/usr/share/man --disable-crm --with-group-name=haclient 
--with-ccmuser-name=hacluster --enable-libc-malloc --disable-fatal-warnings
Autoconf package autoconf found.
Automake package automake found.
Libtool package libtoolize found.

[... snipped ...]

make[3]: Leaving directory '/<>/lib/apphb'
Making install in plugins
make[3]: Entering directory '/<>/lib/plugins'
Making install in HBauth
make[4]: Entering directory '/<>/lib/plugins/HBauth'
make[5]: Entering directory '/<>/lib/plugins/HBauth'
make[5]: Nothing to be done for 'install-exec-am'.
 /usr/bin/mkdir -p 
'/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth'
 /bin/bash ../../../libtool --tag=CC--mode=install /usr/bin/install -c   md5.la crc.la 
sha1.la '/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth'
libtool: install: /usr/bin/install -c .libs/md5.so 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/md5.so
libtool: install: /usr/bin/install -c .libs/md5.lai 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/md5.la
libtool: install: /usr/bin/install -c .libs/crc.so 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/crc.so
libtool: install: /usr/bin/install -c .libs/crc.lai 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/crc.la
libtool: install: /usr/bin/install -c .libs/sha1.so 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/sha1.so
libtool: install: /usr/bin/install -c .libs/sha1.lai 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/sha1.la
libtool: install: /usr/bin/install -c .libs/md5.a 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/md5.a
libtool: install: chmod 644 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/md5.a
libtool: install: ranlib 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/md5.a
libtool: install: /usr/bin/install -c .libs/crc.a 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/crc.a
libtool: install: chmod 644 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/crc.a
libtool: install: ranlib 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/crc.a
libtool: install: /usr/bin/install -c .libs/sha1.a 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/sha1.a
libtool: install: chmod 644 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/sha1.a
libtool: install: ranlib 
/<>/debian/tmp/usr/lib/heartbeat/plugins/HBauth/sha1.a
libtool: warning: remember to run 'libtool --finish 
/usr/lib/heartbeat/plugins/HBauth'
make[5]: Leaving directory '/<>/lib/plugins/HBauth'
make[4]: Leaving directory '/<>/lib/plugins/HBauth'
Making install in HBcomm
make[4]: Entering directory '/<>/lib/plugins/HBcomm'
make[5]: Entering directory '/<>/lib/plugins/HBcomm'
make[6]: Entering directory '/<>/lib/plugins/HBcomm'
make[6]: Nothing to be done for 'install-exec-am'.
 /usr/bin/mkdir -p 
'/<>/debian/tmp/usr/lib/heartbeat/plugins/HBcomm'
 /bin/bash ../../../libtool --tag=CC--mode=install /usr/bin/install -c   bcast.la 
mcast.la mcast6.la ucast.la ucast6.la serial.la ping.la ping6.la ping_group.la 
'/<>/debian/tmp/usr/lib/heartbeat/plugins/HBcomm'
libtool: install: 

Bug#1060553: marked as done (heartbeat: Please switch Build-Depends to systemd-dev)

[Debian Bug Tracking System]

Your message dated Thu, 27 Jun 2024 03:34:11 +
with message-id 
and subject line Bug#1060553: fixed in heartbeat 1:3.0.6-14.2
has caused the Debian Bug report #1060553,
regarding heartbeat: Please switch Build-Depends to systemd-dev
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.)


-- 
1060553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: heartbeat
Version: 1:3.0.6-14
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: systemd-dev

Hi,

your package heartbeat declares a Build-Depends on systemd and/or
udev.

In most cases, this build dependency is added to get the paths that
are defined in udev.pc or systemd.pc (via pkgconfig).

Since systemd_253-2 [1], these two pkgconfig files have been split
into a separate package named systemd-dev. This package is arch:all,
so even available on non-Linux architectures, which will simplify the
installation of upstream provided service files / udev rules.

To not make existing source packages FTBFS, the systemd and udev
package have a Depends: systemd-dev. This dependency will be removed
at some point though before trixie is released. Once this happens,
this issue will be bumped to RC.

Please update your build dependencies accordingly at your earliest
convenience.

If all you need is the systemd.pc or udev.pc pkgconfig file, please
replace any systemd or udev Build-Depends with systemd-dev. In most
cases that should be sufficient. If your package needs further
resources from systemd or udev to build successfully, it's fine to
keep those Build-Depends in addition to systemd-dev.

To ease stable backports, a version of systemd with those changes is
provided via bookworm-backports.

In case you have further questions, please contact the systemd team
at .

On behalf of the systemd team, Michael

[1]
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 
--- End Message ---
--- Begin Message ---
Source: heartbeat
Source-Version: 1:3.0.6-14.2
Done: Boyuan Yang 

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated heartbeat 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: Wed, 26 Jun 2024 23:19:53 -0400
Source: heartbeat
Architecture: source
Version: 1:3.0.6-14.2
Distribution: unstable
Urgency: high
Maintainer: Debian HA Maintainers 

Changed-By: Boyuan Yang 
Closes: 1060553 1071314
Changes:
 heartbeat (1:3.0.6-14.2) unstable; urgency=high
 .
   * Non-maintainer upload.
   * debian/control: Replace build-dependency on systemd with systemd-dev.
 (Closes: #1060553, #1071314)
   * Merge changes from Ubuntu:
   * debian/control: Allow using alternative dependency of
 resource-agents | resource-agents-base. This helps Ubuntu who made
 resource-agents to be a removed transitional package.
 .
   [ Matthias Klose ]
   * debian/libheartbeat2t64.symbols: Mark strl* symbols as optional. These
 were included in glibc 2.38.
Checksums-Sha1:
 b795b8f34eaa2c8eb0c3e34d05ed7058fccd1b4f 2711 heartbeat_3.0.6-14.2.dsc
 e1cd31efa0ab8e8454edae711e67fa5c50df1219 551953 heartbeat_3.0.6.orig.tar.bz2
 4681340bf2c35ec901ba03e10c5d1052516c816a 41856 
heartbeat_3.0.6-14.2.debian.tar.xz
 a453f57ba0e152bc0bf6b89cf2e6032afa420a04 12493 
heartbeat_3.0.6-14.2_amd64.buildinfo
Checksums-Sha256:
 a3d157e831d6213cd8611953952d6feb41f5d3768e19be350b88a814ab477248 2711 
heartbeat_3.0.6-14.2.dsc
 851d2add2c129fef9fede764fec80229e1f6e7295e0e979950d10258648b462c 551953 
heartbeat_3.0.6.orig.tar.bz2
 e244ffb458f628e1353c70846763f10ce1d5875ad4ac79741952bd2098fa9b5d 41856 
heartbeat_3.0.6-14.2.debian.tar.xz
 91df820a5bd9a572e233f69b03ac6e7ab8ff1b7eba06d7e27c51f6e14b9c897e 12493 
heartbeat_3.0.6-14.2_amd64.buildinfo
Files:
 f88ca7dd340a77e401e0b9213e05efc2 2711 admin optional heartbeat_3.0.6-14.2.dsc
 101c8f507b1f407468d5ef15ae6719da 551953 admin optional 
heartbeat_3.0.6.orig.tar.bz2
 c65b85a3268381bdb8a8345419767683 

Bug#1073480: zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd

[yokota]

Hello,

I think this bug is not a libzstd's bug but qt6-base's bug.

Please check this QTBUG.
> [#QTBUG-119469] Targets not yet defined: zstd::libzstd_static
> https://bugreports.qt.io/browse/QTBUG-119469

The QTBUG said this bug was fixed in Qt 6.7.2, so update Qt to 6.7.2
will fixes the problem.

Or, back port QTBUG-119469 fix from git commits.
https://code.qt.io/cgit/qt/qtbase.git/log/?qt=grep=QTBUG-119469

PS:
Arch Linux also have this bug.
> https://gitlab.archlinux.org/archlinux/packaging/packages/qt6-doc/-/issues/1
--
YOKOTA Hiroshi

Bug#1070840: marked as done (r-cran-ff: autopkgtest regression with r-base 4.4.0)

[Debian Bug Tracking System]

Your message dated Thu, 27 Jun 2024 08:58:21 +0900
with message-id 
and subject line Re: [R-pkg-team] Bug#1070840: r-cran-ff: autopkgtest 
regression with r-base 4.4.0
has caused the Debian Bug report #1070840,
regarding r-cran-ff: autopkgtest regression with r-base 4.4.0
to be marked as done.

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

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


-- 
1070840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-ff
Version: 4.0.12+ds-1
Severity: serious
X-Debbugs-Cc: Dirk Eddelbuettel 
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

r-cran-ff's autopkgtest regresses when tested with r-base 4.4.0 [1].
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-ff/testing/amd64/


42s ══ Failed tests

42s ── Failure ('test-zero_lengths.R:34:3'): file size is correct when
creating ff integer from scratch ──
42s file.exists(f1) is not TRUE
42s
42s `actual`: FALSE
42s `expected`: TRUE
42s
42s [ FAIL 1 | WARN 52 | SKIP 0 | PASS 965 ]
42s Error: Test failures
42s Execution halted
--- End Message ---
--- Begin Message ---
Hello everybody,

The CI tests of r-cran-ff are passing now, so I am closing this bug.

Have a nice day,

Charles

-- 
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team http://www.debian.org/devel/debian-med
Tooting from home  https://framapiaf.org/@charles_plessy
- You  do not have  my permission  to use  this email  to train  an AI  End Message ---

Bug#1071861: marked as done (plakativ: autopkgtest fails with python3-fitz 1.24.x)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 23:04:50 +
with message-id 
and subject line Bug#1071861: fixed in plakativ 0.5.2-2
has caused the Debian Bug report #1071861,
regarding plakativ: autopkgtest fails with python3-fitz 1.24.x
to be marked as done.

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

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


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

Source: plakativ

python3-fitz's exported module is going to be renamed from fitz to fitz_old with the next unstable revision (already in 
experimental). Please prepare for the rename.
--- End Message ---
--- Begin Message ---
Source: plakativ
Source-Version: 0.5.2-2
Done: Johannes Schauer Marin Rodrigues 

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

Debian distribution maintenance software
pp.
Johannes Schauer Marin Rodrigues  (supplier of updated 
plakativ 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, 27 Jun 2024 00:28:04 +0200
Source: plakativ
Architecture: source
Version: 0.5.2-2
Distribution: unstable
Urgency: medium
Maintainer: Johannes Schauer Marin Rodrigues 
Changed-By: Johannes Schauer Marin Rodrigues 
Closes: 1071861
Changes:
 plakativ (0.5.2-2) unstable; urgency=medium
 .
   * Deal with PyMuPDF installed as fitz_old (closes: #1071861)
Checksums-Sha1:
 257ab3f876db67f9127962e41f8e314e47096bc6 2198 plakativ_0.5.2-2.dsc
 3f73530e538c9c21bdf8dd14ac600a1bf443c925 11356 plakativ_0.5.2-2.debian.tar.xz
Checksums-Sha256:
 56fcbc859eda2668d4c14545d6f80ec4560bb9a81d0cf9aabecbbc37604f43be 2198 
plakativ_0.5.2-2.dsc
 5f269ac775bbc45233c9f451bdb83a21bbce5b83582f631766006e7648d43a86 11356 
plakativ_0.5.2-2.debian.tar.xz
Files:
 7bb5195153b19aede4782836c23ea9ac 2198 python optional plakativ_0.5.2-2.dsc
 24d1dbc4f0a40071b5a5cd28444b2a8b 11356 python optional 
plakativ_0.5.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmZ8nAkACgkQ8sulx4+9
g+HcIw/5AXvywzo4kv2m0cL+uoXrdpDLAwdHyWH0bNfwDTtgFc4LniDF7NN5Kjyz
KpNUQUfSSz9zf3uEgrkry7sq3xmhsPO4PvM+jqZ4gIvmzN8sqaa7/6YCqFcSvnTk
OFBCYh9oIX/YSbHWEXneg1LcVMWXLJ5nOMIxeSy27usB2BpA9zQL93JiFS74qcfj
SuGJNu5Yj5fnlhWM6ptKvCHZ45b8abuFDQux2+b1KnhCriw6yJYqwYWRvn/EF2o8
9OgnJquYTm0wuOoYbsedwWCx5sU2+GxaXUtqSneHO1+mG+ox9/wu6YqZv7y+lY+k
0wswkaNufI/cl5t8+/sRM61RJ5gPd0F4x+vhiNzPp2P9vjxRv4pyP6RPm2cZ+3g1
MTuPuZLb5tjawDSHgj/MJHsXeDy+AgIJYpdYExbLM1vI+m7ugVhgUhisffd7EUuC
1E6S9gpSlz7SCxWHq+NwDdLM+uumJhEfGIZ+o1BaBXlFpXQ9iyEl1EImbVuBMJ3w
iLaWSXoDIH5TQQXEbw/h3MgJQFOYp3pznZ/yPWMyMropIaF3PwUYgGGi3UwReY0i
+b4w0SMjGE27NxRid20yhqU0hVzG2adViXjNdVJ2IIvHbswHw1jjPQz8aMT4aaol
FyrO/M4b6GWTsiP4phqne8KQ4wn5Qh513FjbzzgI5BlrgSDtRRQ=
=R7QP
-END PGP SIGNATURE-



pgpLRYJmI4t1c.pgp
Description: PGP signature
--- End Message ---

Processed: Re: Bug#1073189: awscli: ImportError: cannot import name DEFAULT_CIPHERS from urllib3.util.ssl_

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + upstream
Bug #1073189 [src:awscli] awscli: ImportError: cannot import name 
DEFAULT_CIPHERS from urllib3.util.ssl_
Bug #1073178 [src:awscli] awscli: please update awsci and/or botocore to 
support urllib3 2.x
Bug #1073191 [src:awscli] awscli: ImportError: cannot import name 
DEFAULT_CIPHERS from urllib3.util.ssl_
Added tag(s) upstream.
Added tag(s) upstream.
Added tag(s) upstream.
> forwarded -1 https://github.com/aws/aws-cli/issues/8342
Bug #1073189 [src:awscli] awscli: ImportError: cannot import name 
DEFAULT_CIPHERS from urllib3.util.ssl_
Bug #1073178 [src:awscli] awscli: please update awsci and/or botocore to 
support urllib3 2.x
Bug #1073191 [src:awscli] awscli: ImportError: cannot import name 
DEFAULT_CIPHERS from urllib3.util.ssl_
Set Bug forwarded-to-address to 'https://github.com/aws/aws-cli/issues/8342'.
Set Bug forwarded-to-address to 'https://github.com/aws/aws-cli/issues/8342'.
Set Bug forwarded-to-address to 'https://github.com/aws/aws-cli/issues/8342'.

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

Bug#1073189: awscli: ImportError: cannot import name DEFAULT_CIPHERS from urllib3.util.ssl_

[Noah Meyerhans]

Control: tags -1 + upstream
Control: forwarded -1 https://github.com/aws/aws-cli/issues/8342

On Fri, Jun 14, 2024 at 12:13:10PM +0300, Andrey Chernomyrdin wrote:
> After install awscli I got error on any command:
> ImportError: cannot import name 'DEFAULT_CIPHERS' from 'urllib3.util.ssl_' 
> (/usr/lib/python3/dist-packages/urllib3/util/ssl_.py)
> 

This is an upstream issue being tracked along with python 3.12
compatibility at https://github.com/aws/aws-cli/issues/8342

The patches proposed in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064307#10 seem to fix
this, and we can consider an upload based on it if upstream does not
have a fix soon...

Bug#1074343: src:texlive-bin: fails to migrate to testing for too long: unresolved RC issue

[Preuße]

On 26.06.2024 22:25, Paul Gevers wrote:

Hi,

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:texlive-bin has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version has an RC bug 
filed that's not resolved yet: 1072056.




As you noticed this bug is just an Migration blocker bug, the only 
reason is to present the migration to testing for now. I can close it at 
any point in time, when I think the time is up. Same for #1072054 and I 
would have done this in one of the next days.


Hilmar
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069488: parsinsert: FTBFS on armhf: make[1]: *** [debian/rules:30: override_dh_auto_test] Error 1

[Étienne Mollier]

Control: tags -1 + confirmed

Hi,

parsinsert is making a lot of assumptions on certain compiler
optimisation behaviors, which have evolved in time.  This has
caused an increasing number of ftbfs bugs affecting a range of
CPU architectures, for which the resolution consisted in
dropping optimization levels, e.g. #964082.

I could reproduce the present bug on armhf.  This architecture
was already built with -O1 optimisation, so I attempted a drop
to -O0 which resolved the segmentation fault, but caused other
computation errors anyway.  parsinsert has not seen any newer
upstream version for about twelve years, so I think we don't
have much options but lookup on which CPU architectures build is
broken, request for removal on such targets, then reduce the bug
severity, and move on.

At least the package still seems to operate properly on amd64,
so we can still get away without a removal of the package.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/3, please excuse my verbosity
   `-on air: Genesis - .. In That Quiet Earth'


signature.asc
Description: PGP signature

Processed: Re: parsinsert: FTBFS on armhf: make[1]: *** [debian/rules:30: override_dh_auto_test] Error 1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #1069488 [src:parsinsert] parsinsert: FTBFS on armhf: make[1]: *** 
[debian/rules:30: override_dh_auto_test] Error 1
Added tag(s) confirmed.

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

Bug#1074321: createrepo-c FTBFS: error: implicit declaration of function ‘xmlCheckUTF8’

[Peter Pentchev]

control: tag -1 + confirmed pending

On Wed, Jun 26, 2024 at 05:56:08PM +0300, Adrian Bunk wrote:
> Source: createrepo-c
> Version: 0.17.3-4
> Severity: serious
> Tags: ftbfs patch
> Forwarded: https://github.com/rpm-software-management/createrepo_c/pull/402
> 
> https://buildd.debian.org/status/logs.php?pkg=createrepo-c=0.17.3-4%2Bb2
> 
> ...
> /<>/src/sqlite.c: In function ‘cr_sqlite3_bind_text’:
> /<>/src/sqlite.c:76:16: error: implicit declaration of function 
> ‘xmlCheckUTF8’ [-Werror=implicit-function-declaration]
>76 | } else if (xmlCheckUTF8((const unsigned char *) orig_content)
>   |^~~~
> ...

Already fixed earlier today in
  
https://salsa.debian.org/pkg-rpm-team/createrepo-c/-/commit/5e0f45b00e8565bc45e5b6104c9ccd0748444da2

Thanks for trying to make Debian better!

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org pe...@morpheusly.com
PGP key:https://www.ringlet.net/roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Processed: Re: Bug#1074321: createrepo-c FTBFS: error: implicit declaration of function ‘xmlCheckUTF8’

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed pending
Bug #1074321 [src:createrepo-c] createrepo-c FTBFS: error: implicit declaration 
of function ‘xmlCheckUTF8’
Added tag(s) pending and confirmed.

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

Processed: src:biber: fails to migrate to testing for too long: autopkgtest regression and unresolved RC issue

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.20-2
Bug #1074345 [src:biber] src:biber: fails to migrate to testing for too long: 
autopkgtest regression and unresolved RC issue
Marked as fixed in versions biber/2.20-2.
Bug #1074345 [src:biber] src:biber: fails to migrate to testing for too long: 
autopkgtest regression and unresolved RC issue
Marked Bug as done
> block -1 by 1072054
Bug #1074345 {Done: Paul Gevers } [src:biber] src:biber: 
fails to migrate to testing for too long: autopkgtest regression and unresolved 
RC issue
1074345 was not blocked by any bugs.
1074345 was not blocking any bugs.
Added blocking bug(s) of 1074345: 1072054

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

Bug#1074345: src:biber: fails to migrate to testing for too long: autopkgtest regression and unresolved RC issue

[Paul Gevers]

Source: biber
Version: 2.19-2
Severity: serious
Control: close -1 2.20-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1072054

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:biber has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable has an 
unresolved RC bug: 1072054.


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=biber



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:sqlalchemy: fails to migrate to testing for too long: triggers autopkgtest issues

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.0.30+ds1-3
Bug #1074344 [src:sqlalchemy] src:sqlalchemy: fails to migrate to testing for 
too long: triggers autopkgtest issues
Marked as fixed in versions sqlalchemy/2.0.30+ds1-3.
Bug #1074344 [src:sqlalchemy] src:sqlalchemy: fails to migrate to testing for 
too long: triggers autopkgtest issues
Marked Bug as done

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

Bug#1074344: src:sqlalchemy: fails to migrate to testing for too long: triggers autopkgtest issues

[Paul Gevers]

Source: sqlalchemy
Version: 1.4.50+ds1-1
Severity: serious
Control: close -1 2.0.30+ds1-3
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:sqlalchemy has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable causes 
autopkgtest failure in multiple reverse (test) dependencies.


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=sqlalchemy



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:texlive-bin: fails to migrate to testing for too long: unresolved RC issue

[Debian Bug Tracking System]

Processing control commands:

> close -1 2024.20240313.70630+ds-2
Bug #1074343 [src:texlive-bin] src:texlive-bin: fails to migrate to testing for 
too long: unresolved RC issue
Marked as fixed in versions texlive-bin/2024.20240313.70630+ds-2.
Bug #1074343 [src:texlive-bin] src:texlive-bin: fails to migrate to testing for 
too long: unresolved RC issue
Marked Bug as done
> block -1 by 1072056
Bug #1074343 {Done: Paul Gevers } [src:texlive-bin] 
src:texlive-bin: fails to migrate to testing for too long: unresolved RC issue
1074343 was not blocked by any bugs.
1074343 was not blocking any bugs.
Added blocking bug(s) of 1074343: 1072056

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

Bug#1074343: src:texlive-bin: fails to migrate to testing for too long: unresolved RC issue

[Paul Gevers]

Source: texlive-bin
Version: 2023.20230311.66589-9
Severity: serious
Control: close -1 2024.20240313.70630+ds-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1072056

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:texlive-bin has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version has an RC bug 
filed that's not resolved yet: 1072056.


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=texlive-bin



OpenPGP_signature.asc
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.9-1
Bug #1074342 [src:modernize] src:modernize: fails to migrate to testing for too 
long: autopkgtest regression
Marked as fixed in versions modernize/0.9-1.
Bug #1074342 [src:modernize] src:modernize: fails to migrate to testing for too 
long: autopkgtest regression
Marked Bug as done

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

Bug#1074342: src:modernize: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: modernize
Version: 0.7-3
Severity: serious
Control: close -1 0.9-1
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:modernize has been trying to migrate for 
32 days [2]. Hence, I am filing this bug. The version in unstable fails 
its own autopkgtest.


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=modernize



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1074341: src:rust-subtile: fails to migrate to testing for too long: autopkgtest regression on i386

[Paul Gevers]

Source: rust-subtile
Version: 0.1.4-2
Severity: serious
Control: close -1 0.1.8-1
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:rust-subtile has been trying to migrate 
for 32 days [2]. Hence, I am filing this bug. The version in unstable 
fails its own autopkgtest on i386.


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=rust-subtile



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:rust-subtile: fails to migrate to testing for too long: autopkgtest regression on i386

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.1.8-1
Bug #1074341 [src:rust-subtile] src:rust-subtile: fails to migrate to testing 
for too long: autopkgtest regression on i386
Marked as fixed in versions rust-subtile/0.1.8-1.
Bug #1074341 [src:rust-subtile] src:rust-subtile: fails to migrate to testing 
for too long: autopkgtest regression on i386
Marked Bug as done

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

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

[Debian Bug Tracking System]

Processing control commands:

> close -1 4.7.1-1.1
Bug #1074339 [src:sosreport] src:sosreport: fails to migrate to testing for too 
long: autopkgtest regression
Marked as fixed in versions sosreport/4.7.1-1.1.
Bug #1074339 [src:sosreport] src:sosreport: fails to migrate to testing for too 
long: autopkgtest regression
Marked Bug as done

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

Bug#1074339: src:sosreport: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: sosreport
Version: 4.0-2.1
Severity: serious
Control: close -1 4.7.1-1.1
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:sosreport has been trying to migrate for 
32 days [2]. Hence, I am filing this bug. The version in unstable fails 
its own autopkgtest.


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=sosreport



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:libxml2: fails to migrate to testing for too long: unresolved RC issue

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.12.7+dfsg-3
Bug #1074338 [src:libxml2] src:libxml2: fails to migrate to testing for too 
long: unresolved RC issue
Marked as fixed in versions libxml2/2.12.7+dfsg-3.
Bug #1074338 [src:libxml2] src:libxml2: fails to migrate to testing for too 
long: unresolved RC issue
Marked Bug as done
> block -1 by 1073508
Bug #1074338 {Done: Paul Gevers } [src:libxml2] src:libxml2: 
fails to migrate to testing for too long: unresolved RC issue
1074338 was not blocked by any bugs.
1074338 was not blocking any bugs.
Added blocking bug(s) of 1074338: 1073508

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

Bug#1074338: src:libxml2: fails to migrate to testing for too long: unresolved RC issue

[Paul Gevers]

Source: libxml2
Version: 2.9.14+dfsg-1.3
Severity: serious
Control: close -1 2.12.7+dfsg-3
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1073508

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:libxml2 has been trying to migrate for 32 
days [2]. Hence, I am filing this bug. The version in unstable broke ABI 
without a SONAME bump as reported in bug 1073508.


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=libxml2



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: libssh-gcrypt-dev: Drop gcrypt flavor

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1074268 986529 1074257
Bug #1074337 [libssh-gcrypt-dev] libssh-gcrypt-dev: Drop gcrypt flavor
1074337 was not blocked by any bugs.
1074337 was not blocking any bugs.
Added blocking bug(s) of 1074337: 986529, 1074257, and 1074268

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

Bug#1073050:

[Andreas Hasenack]

I believe this is because the hns provider is not built on architectures
which have no "COHERENT_DMA":

-- Performing Test HAVE_COHERENT_DMA
-- Performing Test HAVE_COHERENT_DMA - Failed
(...)
-- Missing Optional Items:
--  Architecture NOT able to do coherent DMA (check util/udma_barrier.h)
some providers disabled!


CMakeLists.txt:
# Providers
if (HAVE_COHERENT_DMA)
add_subdirectory(providers/bnxt_re)
(...)
add_subdirectory(providers/hns)
(...)

This was already the case in version 50.0, I'm still not sure what changed
in 52.0 other than the debian packaging now including libhns in some
d/*.install files. Maybe before they were just left there without
installing?

Bug#1071007: Sherlock bug update

[Paul Pfeister]

We are planning to bump to 0.15.0 to coordinate merges for all our
planned breaking changes at once

With this, the importable module's name will be changed, avoiding
conflict. I've proposed sherlock_project to match pypi and the egg, as
Thomas recommended.

We also plan to adopt proper tagged releases starting with this
version. This means that long date+commitish version tags like
0.14.4+git20240531.e5ad3c4-2 are theoretically no longer necessary for
downstream. Downstream packages should be able to (in theory) peg
themselves to a version tag for stable and add build numbers after for
later mid-lifecycle/unstable updates or patches (i.e. 0.15.0-1,
0.15.0-2).

Will update everyone soon.

Processed: tagging 1074112

[Debian Bug Tracking System]

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

> tags 1074112 + upstream
Bug #1074112 [src:binutils] [arm64] boot stops at 'Starting kernel ...' without 
any further output when kernel built with recent binutils
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: lintian-brush: Build-Depends: librust-breezyshim-dev (>= 0.1.101) not satisfiable

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:rust-breezyshim
Bug #1074330 [src:lintian-brush] lintian-brush: Build-Depends: 
librust-breezyshim-dev (>= 0.1.101) not satisfiable
Added indication that 1074330 affects src:rust-breezyshim

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

Bug#1074330: lintian-brush: Build-Depends: librust-breezyshim-dev (>= 0.1.101) not satisfiable

[Jeremy Bícha]

Source: lintian-brush
Version: 0.157
Severity: serious
Tags: ftbfs
X-Debbugs-CC: rust-breezys...@packages.debian.org
Control: affects -1 src:rust-breezyshim

lintian-brush has Build-Depends: librust-breezyshim-dev (>= 0.1.101)
but the version of rust-breezyshim in Debian is 0.1.92

Feel free to reassign this bug to rust-breezyshim if you end up simply
packaging a new version.

Thank you,
Jeremy Bícha

Processed: Re: plakativ: prepare for next python3-fitz version

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 plakativ: autopkgtest fails with python3-fitz 1.24.x
Bug #1071861 [src:plakativ] plakativ: prepare for next python3-fitz version
Changed Bug title to 'plakativ: autopkgtest fails with python3-fitz 1.24.x' 
from 'plakativ: prepare for next python3-fitz version'.
> severity -1 serious
Bug #1071861 [src:plakativ] plakativ: autopkgtest fails with python3-fitz 1.24.x
Severity set to 'serious' from 'normal'

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

Bug#1073321: marked as done (libsbml: FTBFS: LibXMLParser.cpp:427:46: error: invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to ‘xmlErrorPtr’ {aka ‘_xmlError*’} [-fpermissive])

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 17:29:27 +
with message-id 
and subject line Bug#1073321: fixed in libsbml 5.20.2+dfsg-8
has caused the Debian Bug report #1073321,
regarding libsbml: FTBFS: LibXMLParser.cpp:427:46: error: invalid conversion 
from ‘const xmlError*’ {aka ‘const _xmlError*’} to ‘xmlErrorPtr’ {aka 
‘_xmlError*’} [-fpermissive]
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.)


-- 
1073321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsbml
Version: 5.20.2+dfsg-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cd /<>/build/src && /usr/bin/c++ -DLIBSBML_COMPILED_IN_SRC 
> -DLINUX -DUSE_BZ2 -DUSE_COMP -DUSE_FBC=1 -DUSE_GROUPS -DUSE_L3V2EXTENDEDMATH 
> -DUSE_LAYOUT -DUSE_LIBXML -DUSE_QUAL -DUSE_RENDER -DUSE_ZLIB -Dsbml_EXPORTS 
> -I/<>/build/src/src/sbml -I/<>/build/src/src 
> -I/<>/build/src -I/<>/src 
> -I/<>/src/sbml -I/<>/src/sbml/packages/comp/common 
> -I/<>/src/sbml/packages/comp/extension 
> -I/<>/src/sbml/packages/comp/sbml 
> -I/<>/src/sbml/packages/comp/util 
> -I/<>/src/sbml/packages/comp/validator 
> -I/<>/src/sbml/packages/comp/validator/constraints 
> -I/<>/src/sbml/packages/fbc/common 
> -I/<>/src/sbml/packages/fbc/extension 
> -I/<>/src/sbml/packages/fbc/sbml 
> -I/<>/src/sbml/packages/fbc/util 
> -I/<>/src/sbml/packages/fbc/validator 
> -I/<>/src/sbml/packages/fbc/validator/constraints 
> -I/<>/src/sbml/packages/groups/common 
> -I/<>/src/sbml/packages/groups/extension 
> -I/<>/src/sbml/packages/groups/sbml 
> -I/<>/src/sbml/packages/groups/validator 
> -I/<>/src/sbml/packages/groups/validator/constraints 
> -I/<>/src/sbml/packages/l3v2extendedmath/common 
> -I/<>/src/sbml/packages/l3v2extendedmath/extension 
> -I/<>/src/sbml/packages/l3v2extendedmath/sbml 
> -I/<>/src/sbml/packages/l3v2extendedmath/validator 
> -I/<>/src/sbml/packages/l3v2extendedmath/validator/constraints 
> -I/<>/src/sbml/packages/qual/common 
> -I/<>/src/sbml/packages/qual/extension 
> -I/<>/src/sbml/packages/qual/sbml 
> -I/<>/src/sbml/packages/qual/validator 
> -I/<>/src/sbml/packages/qual/validator/constraints 
> -I/<>/src/sbml/packages/render/common 
> -I/<>/src/sbml/packages/render/extension 
> -I/<>/src/sbml/packages/render/sbml 
> -I/<>/src/sbml/packages/render/util 
> -I/<>/src/sbml/packages/render/validator 
> -I/<>/src/sbml/packages/render/validator/constraints -isystem 
> /usr/include/libxml2 -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 
> -fno-strict-aliasing -fPIC -fPIC   -Wall -MD -MT 
> src/CMakeFiles/sbml.dir/sbml/xml/LibXMLParser.cpp.o -MF 
> CMakeFiles/sbml.dir/sbml/xml/LibXMLParser.cpp.o.d -o 
> CMakeFiles/sbml.dir/sbml/xml/LibXMLParser.cpp.o -c 
> /<>/src/sbml/xml/LibXMLParser.cpp
> /<>/src/sbml/xml/LibXMLParser.cpp: In member function ‘virtual 
> bool LibXMLParser::parseNext()’:
> /<>/src/sbml/xml/LibXMLParser.cpp:427:46: error: invalid 
> conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to ‘xmlErrorPtr’ 
> {aka ‘_xmlError*’} [-fpermissive]
>   427 | xmlErrorPtr libxmlError = xmlGetLastError();
>   |   ~~~^~
>   |  |
>   |  const xmlError* {aka 
> const _xmlError*}
> make[3]: *** [src/CMakeFiles/sbml.dir/build.make:5623: 
> src/CMakeFiles/sbml.dir/sbml/xml/LibXMLParser.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/libsbml_5.20.2+dfsg-7_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: libsbml

Bug#1073321: marked as pending in libsbml

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/libsbml/-/commit/bc8cf1aefde2316f007c1e8a33536a944d15eaaf


Added patch from upstream to add libxml2 2.12.0 support. Closes: #1073321


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073321

Processed: Bug#1073321 marked as pending in libsbml

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073321 [src:libsbml] libsbml: FTBFS: LibXMLParser.cpp:427:46: error: 
invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to 
‘xmlErrorPtr’ {aka ‘_xmlError*’} [-fpermissive]
Added tag(s) pending.

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

Bug#1065186: marked as done (caml-crush: missing build-dep on libtirpc-dev (and also rpcsvc-proto))

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 16:04:08 +
with message-id 
and subject line Bug#1065186: fixed in caml-crush 1.0.12-1.2
has caused the Debian Bug report #1065186,
regarding caml-crush: missing build-dep on libtirpc-dev (and also rpcsvc-proto)
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.)


-- 
1065186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caml-crush
Version: 1.0.12-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

Starting with glibc 2.31, support for NIS (libnsl library) has been
moved to a separate libnsl2 package. In order to allow a smooth
transition, a libnsl-dev, which depends on libtirpc-dev, has been added
to the libc6-dev package.

The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1
NMU, as part of the 64-bit time_t transition. This causes caml-crush to
FTBFS in sid with:

| checking for gawk... no
| checking for mawk... mawk
| checking for camlidl... yes
| checking for spatch... yes
| Detected coccinelle version 1.1.1
| configure: Using default C based client and RPC
| checking for getnetname in -ltirpc... no
| configure: Using the glibc RPC implementation
| checking for rpc/rpc.h... no
| configure: error: Could not find C RPC headers.
| cd build-SERVER && tail -v -n \+0 config.log

This could be fixed by adding an explicit Build-Depends on libtirpc-dev.
The glibc change will likely be reverted in the short term, but given
its a change we want to do for Trixie, this will only lower the severity
of the bug.

I also noticed that caml-crush, uses rpcgen, provided by the
rpcsvc-proto during the build process. It is currently a dependency of
the libc6-dev package for the same reason as libnsl-dev, and will be
removed at some point. Therefore please also add an explicit
Build-Depends on rpcsvc-proto.

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: caml-crush
Source-Version: 1.0.12-1.2
Done: Aurelien Jarno 

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated caml-crush 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: Wed, 26 Jun 2024 17:42:56 +0200
Source: caml-crush
Architecture: source
Version: 1.0.12-1.2
Distribution: unstable
Urgency: medium
Maintainer: Thomas Calderon 
Changed-By: Aurelien Jarno 
Closes: 1065186
Changes:
 caml-crush (1.0.12-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build-dependency on libtirpc-dev and rpcsvc-proto (Closes: #1065186).
Checksums-Sha1:
 ac7945651976804b8ebbb111043f97dea437e9a3 2225 caml-crush_1.0.12-1.2.dsc
 7532de44d8f687d7df03366b0094b16fb9fe0cae 6684 
caml-crush_1.0.12-1.2.debian.tar.xz
 9a148e2b5316b8dfd8d5650a1e4ea004a20a3234 7696 
caml-crush_1.0.12-1.2_source.buildinfo
Checksums-Sha256:
 f0a60e651fe93a52ddc8f981a125bc61bbeb7987a910a560fe73be40cfde2b16 2225 
caml-crush_1.0.12-1.2.dsc
 ee0cca782ff921278b5674e46aeca4bec4ea8713eaa26b1f828b1e7d2c849ee1 6684 
caml-crush_1.0.12-1.2.debian.tar.xz
 c6ff9b20cb2765acb2fa608e1139df2a497864fcecd6e6e96ec6bd37225fac65 7696 
caml-crush_1.0.12-1.2_source.buildinfo
Files:
 972aaca39414be5b3bfe740ee23f9b0f 2225 net optional caml-crush_1.0.12-1.2.dsc
 8e0825dbf1facf1ff93d4fd3d0408262 6684 net optional 
caml-crush_1.0.12-1.2.debian.tar.xz
 895ff307a366da0fab30e30387be9754 7696 net optional 
caml-crush_1.0.12-1.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmZ8OL4ACgkQE4jA+Jno
M2ukTA/+Koa5gDUVX1eGmTmm2MjC7NeXY+Ez9eheIYEbPo824v3FQtm+C9FWrtEW
Ydi/JTKa4m4HUD/8TCrTiCCu8Q2MY6PhVIz/i8tD7Xoi+vHLR7/34eMxUqe9JJ++
p3PfK0FgEMNaJonANToesoj3Dpby3iNRJudQ19R9VkR6/Ps1ATm1Ob9CXtiNVBTW
E1rjWxuYmXITX11zhG5JG6CbJG7ADBG4hhCuhoQBkITQuU0/7AWNZ3iiUbMD66Kg
1C/jXgsA+rqvnpAKdJd6TKrqplNjaLLTd07dBJtkx+cwAgbV7mln/uDmEuAMB2nL
M1CwUMwiRHk4AqZcaXYqF4EB58k/xIALtwNR/7lMSnSoesP38XLUwXMyfQ5HW/6u

Bug#1065160: marked as done (slapi-nis: FTBFS: missing build-dep on libnsl-dev)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 15:51:09 +
with message-id 
and subject line Bug#1065160: fixed in slapi-nis 0.60.0-1.1
has caused the Debian Bug report #1065160,
regarding slapi-nis: FTBFS: missing build-dep on libnsl-dev
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.)


-- 
1065160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slapi-nis
Version: 0.60.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-gl...@lists.debian.org
Usertags: libnsl-dev

Dear maintainer,

Starting with glibc 2.31, support for NIS (libnsl library) has been
moved to a separate libnsl2 package. In order to allow a smooth
transition, a libnsl-dev has been added to the libc6-dev package.

This dependency has been temporarily dropped in the 2.37-15.1 NMU, as
part of the 64-bit time_t transition. This causes slapi-nis to FTBFS in
sid with:

| /bin/bash ../libtool  --tag=CC   --mode=link gcc  -I/usr/include/nss 
-I/usr/include/nspr  -I/usr/include/tirpc   -DDEFS_NIS_MAIN -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-module -avoid-version -export-symbols-regex '.*_plugin_init' -Wl,-z,relro -o 
nisserver-plugin-defs nisserver_plugin_defs-defs-nis.o  -lsss_nss_idmap
| libtool: link: gcc -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/tirpc -DPORTMAP_MAIN -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wl,-z -Wl,relro -o portmap 
portmap-portmap.o  -lnss3 -lnssutil3 -lsmime3 -lssl3 -lplds4 -lplc4 -lnspr4 
-ltirpc -lwrap -lnsl -lsss_nss_idmap
| /usr/bin/ld: cannot find -lnsl: No such file or directory
| collect2: error: ld returned 1 exit status
| make[3]: *** [Makefile:717: portmap] Error 1
| make[3]: *** Waiting for unfinished jobs
| libtool: link: gcc -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/tirpc -DDEFS_NIS_MAIN -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wl,-z -Wl,relro -o nisserver-plugin-defs nisserver_plugin_defs-defs-nis.o  
-lsss_nss_idmap
| make[3]: Leaving directory '/<>/src'
| make[2]: *** [Makefile:547: all] Error 2
| make[2]: Leaving directory '/<>/src'
| make[1]: *** [Makefile:481: all-recursive] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j3 returned exit code 2
| make: *** [debian/rules:8: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This could be fixed by adding an explicit Build-Depends on libnsl-dev.
The glibc change will likely be reverted in the short term, but given
its a change we want to do for Trixie, this will only lower the severity
of the bug.

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: slapi-nis
Source-Version: 0.60.0-1.1
Done: Aurelien Jarno 

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated slapi-nis 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: Wed, 26 Jun 2024 17:18:36 +0200
Source: slapi-nis
Architecture: source
Version: 0.60.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Aurelien Jarno 
Closes: 1065160
Changes:
 slapi-nis (0.60.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add libnsl-dev as build-dependency. Closes: #1065160.
Checksums-Sha1:
 05af2cefc6dd6843089f8c9fc80f10efbcb6cffb 2074 slapi-nis_0.60.0-1.1.dsc
 ffd751d76f2d6ff1f20dc9e4cdfde1e3d65a41e5 3612 
slapi-nis_0.60.0-1.1.debian.tar.xz
 033b025c36d5c5266119ba5a5d73757b951f053a 6801 
slapi-nis_0.60.0-1.1_source.buildinfo
Checksums-Sha256:
 81763b1ceecf4e9a2ef0656803512d97025b3d4ca772a9a25631dfc2f60f8383 2074 
slapi-nis_0.60.0-1.1.dsc
 

Bug#1065186: caml-crush: missing build-dep on libtirpc-dev (and also rpcsvc-proto)

[Aurelien Jarno]

Dear maintainer,

On 2024-03-01 16:55, Aurelien Jarno wrote:
> Source: caml-crush
> Version: 1.0.12-1.1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> 
> Dear maintainer,
> 
> Starting with glibc 2.31, support for NIS (libnsl library) has been
> moved to a separate libnsl2 package. In order to allow a smooth
> transition, a libnsl-dev, which depends on libtirpc-dev, has been added
> to the libc6-dev package.
> 
> The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1
> NMU, as part of the 64-bit time_t transition. This causes caml-crush to
> FTBFS in sid with:
> 
> | checking for gawk... no
> | checking for mawk... mawk
> | checking for camlidl... yes
> | checking for spatch... yes
> | Detected coccinelle version 1.1.1
> | configure: Using default C based client and RPC
> | checking for getnetname in -ltirpc... no
> | configure: Using the glibc RPC implementation
> | checking for rpc/rpc.h... no
> | configure: error: Could not find C RPC headers.
> | cd build-SERVER && tail -v -n \+0 config.log
> 
> This could be fixed by adding an explicit Build-Depends on libtirpc-dev.
> The glibc change will likely be reverted in the short term, but given
> its a change we want to do for Trixie, this will only lower the severity
> of the bug.
> 
> I also noticed that caml-crush, uses rpcgen, provided by the
> rpcsvc-proto during the build process. It is currently a dependency of
> the libc6-dev package for the same reason as libnsl-dev, and will be
> removed at some point. Therefore please also add an explicit
> Build-Depends on rpcsvc-proto.

I have just done a NMU to fix this issue. Please find the debdiff
attached.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net
diff -Nru caml-crush-1.0.12/debian/changelog caml-crush-1.0.12/debian/changelog
--- caml-crush-1.0.12/debian/changelog  2023-01-27 09:11:33.0 +0100
+++ caml-crush-1.0.12/debian/changelog  2024-06-26 17:42:56.0 +0200
@@ -1,3 +1,10 @@
+caml-crush (1.0.12-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add build-dependency on libtirpc-dev and rpcsvc-proto (Closes: #1065186).
+
+ -- Aurelien Jarno   Wed, 26 Jun 2024 17:42:56 +0200
+
 caml-crush (1.0.12-1.1) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru caml-crush-1.0.12/debian/control caml-crush-1.0.12/debian/control
--- caml-crush-1.0.12/debian/control2021-11-25 16:23:09.0 +0100
+++ caml-crush-1.0.12/debian/control2024-06-26 17:42:56.0 +0200
@@ -2,7 +2,7 @@
 Section: net
 Priority: optional
 Maintainer: Thomas Calderon 
-Build-Depends: debhelper (>= 12), debhelper-compat (= 13), 
ocaml-native-compilers, camlidl, coccinelle, libocamlnet-ocaml-dev (>= 3.5.1), 
libocamlnet-ssl-ocaml-dev (>= 3.5.1), libocamlnet-ocaml-bin (>= 3.5.1), 
libssl-dev, libgnutls28-dev, libconfig-file-ocaml-dev, camlp4, dh-exec
+Build-Depends: debhelper (>= 12), debhelper-compat (= 13), 
ocaml-native-compilers, camlidl, coccinelle, libocamlnet-ocaml-dev (>= 3.5.1), 
libocamlnet-ssl-ocaml-dev (>= 3.5.1), libocamlnet-ocaml-bin (>= 3.5.1), 
libssl-dev, libgnutls28-dev, libconfig-file-ocaml-dev, camlp4, dh-exec, 
libtirpc-dev, rpcsvc-proto
 Standards-Version: 4.6.0.1
 Homepage: https://github.com/caml-pkcs11/caml-crush
 Vcs-Git: https://github.com/caml-pkcs11/caml-crush.git

Processed: tagging 1074175, reassign 1069317 to src:vamp-plugin-sdk, fixed 1069317 in 2.10.0-5~exp ...

[Debian Bug Tracking System]

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

> tags 1074175 + sid trixie
Bug #1074175 [src:netkit-rwho] netkit-rwho: remove for trixie?
Added tag(s) trixie and sid.
> reassign 1069317 src:vamp-plugin-sdk 2.10.0-4
Bug #1069317 {Done: IOhannes m zmölnig (Debian/GNU) } 
[libvamp-hostsdk3v5] FTBFS: tests failed
Bug #1074226 {Done: IOhannes m zmölnig (Debian/GNU) } 
[libvamp-hostsdk3v5] sonic-visualiser: FTBFS on armel/armhf
Bug reassigned from package 'libvamp-hostsdk3v5' to 'src:vamp-plugin-sdk'.
Bug reassigned from package 'libvamp-hostsdk3v5' to 'src:vamp-plugin-sdk'.
Ignoring request to alter found versions of bug #1069317 to the same values 
previously set
Ignoring request to alter found versions of bug #1074226 to the same values 
previously set
No longer marked as fixed in versions vamp-plugin-sdk/2.10.0-5~exp and 
vamp-plugin-sdk/2.10.0-5.
No longer marked as fixed in versions vamp-plugin-sdk/2.10.0-5 and 
vamp-plugin-sdk/2.10.0-5~exp.
Bug #1069317 {Done: IOhannes m zmölnig (Debian/GNU) } 
[src:vamp-plugin-sdk] FTBFS: tests failed
Bug #1074226 {Done: IOhannes m zmölnig (Debian/GNU) } 
[src:vamp-plugin-sdk] sonic-visualiser: FTBFS on armel/armhf
Marked as found in versions vamp-plugin-sdk/2.10.0-4.
Marked as found in versions vamp-plugin-sdk/2.10.0-4.
> fixed 1069317 2.10.0-5~exp
Bug #1069317 {Done: IOhannes m zmölnig (Debian/GNU) } 
[src:vamp-plugin-sdk] FTBFS: tests failed
Bug #1074226 {Done: IOhannes m zmölnig (Debian/GNU) } 
[src:vamp-plugin-sdk] sonic-visualiser: FTBFS on armel/armhf
Marked as fixed in versions vamp-plugin-sdk/2.10.0-5~exp.
Marked as fixed in versions vamp-plugin-sdk/2.10.0-5~exp.
> fixed 1069317 2.10.0-5
Bug #1069317 {Done: IOhannes m zmölnig (Debian/GNU) } 
[src:vamp-plugin-sdk] FTBFS: tests failed
Bug #1074226 {Done: IOhannes m zmölnig (Debian/GNU) } 
[src:vamp-plugin-sdk] sonic-visualiser: FTBFS on armel/armhf
The source 'vamp-plugin-sdk' and version '2.10.0-5' do not appear to match any 
binary packages
Marked as fixed in versions vamp-plugin-sdk/2.10.0-5.
Marked as fixed in versions vamp-plugin-sdk/2.10.0-5.
> tags 1074250 + sid trixie
Bug #1074250 [ifupdown2] ifupdown2 not working with python3.12
Added tag(s) trixie and sid.
> found 1074241 1.5.8.1-1
Bug #1074241 [opensnitch] opensnitch can no longer be built on ppc64el.
Marked as found in versions opensnitch/1.5.8.1-1.
> tags 1074241 + sid trixie experimental
Bug #1074241 [opensnitch] opensnitch can no longer be built on ppc64el.
Added tag(s) sid, trixie, and experimental.
> thanks
Stopping processing here.

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

Bug#1065160: slapi-nis: FTBFS: missing build-dep on libnsl-dev

[Aurelien Jarno]

Dear maintainer,

On 2024-03-01 11:33, Aurelien Jarno wrote:
> Source: slapi-nis
> Version: 0.60.0-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> User: debian-gl...@lists.debian.org
> Usertags: libnsl-dev
> 
> Dear maintainer,
> 
> Starting with glibc 2.31, support for NIS (libnsl library) has been
> moved to a separate libnsl2 package. In order to allow a smooth
> transition, a libnsl-dev has been added to the libc6-dev package.
> 
> This dependency has been temporarily dropped in the 2.37-15.1 NMU, as
> part of the 64-bit time_t transition. This causes slapi-nis to FTBFS in
> sid with:
> 
> | /bin/bash ../libtool  --tag=CC   --mode=link gcc  -I/usr/include/nss 
> -I/usr/include/nspr  -I/usr/include/tirpc   -DDEFS_NIS_MAIN -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -module -avoid-version -export-symbols-regex '.*_plugin_init' -Wl,-z,relro -o 
> nisserver-plugin-defs nisserver_plugin_defs-defs-nis.o  -lsss_nss_idmap
> | libtool: link: gcc -I/usr/include/nss -I/usr/include/nspr 
> -I/usr/include/tirpc -DPORTMAP_MAIN -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wl,-z -Wl,relro -o portmap portmap-portmap.o  -lnss3 -lnssutil3 -lsmime3 
> -lssl3 -lplds4 -lplc4 -lnspr4 -ltirpc -lwrap -lnsl -lsss_nss_idmap
> | /usr/bin/ld: cannot find -lnsl: No such file or directory
> | collect2: error: ld returned 1 exit status
> | make[3]: *** [Makefile:717: portmap] Error 1
> | make[3]: *** Waiting for unfinished jobs
> | libtool: link: gcc -I/usr/include/nss -I/usr/include/nspr 
> -I/usr/include/tirpc -DDEFS_NIS_MAIN -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wl,-z -Wl,relro -o nisserver-plugin-defs nisserver_plugin_defs-defs-nis.o  
> -lsss_nss_idmap
> | make[3]: Leaving directory '/<>/src'
> | make[2]: *** [Makefile:547: all] Error 2
> | make[2]: Leaving directory '/<>/src'
> | make[1]: *** [Makefile:481: all-recursive] Error 1
> | make[1]: Leaving directory '/<>'
> | dh_auto_build: error: make -j3 returned exit code 2
> | make: *** [debian/rules:8: build] Error 25
> | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> status 2
> 
> This could be fixed by adding an explicit Build-Depends on libnsl-dev.
> The glibc change will likely be reverted in the short term, but given
> its a change we want to do for Trixie, this will only lower the severity
> of the bug.

I have just done a NMU to fix this issue. Please find the debdiff
attached.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net
diff -Nru slapi-nis-0.60.0/debian/changelog slapi-nis-0.60.0/debian/changelog
--- slapi-nis-0.60.0/debian/changelog   2022-11-21 10:38:23.0 +0100
+++ slapi-nis-0.60.0/debian/changelog   2024-06-26 17:18:36.0 +0200
@@ -1,3 +1,10 @@
+slapi-nis (0.60.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add libnsl-dev as build-dependency. Closes: #1065160.
+
+ -- Aurelien Jarno   Wed, 26 Jun 2024 17:18:36 +0200
+
 slapi-nis (0.60.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru slapi-nis-0.60.0/debian/control slapi-nis-0.60.0/debian/control
--- slapi-nis-0.60.0/debian/control 2022-11-21 10:16:32.0 +0100
+++ slapi-nis-0.60.0/debian/control 2024-06-26 17:18:36.0 +0200
@@ -13,6 +13,7 @@
  libsss-nss-idmap-dev,
  libtirpc-dev,
  libwrap0-dev,
+ libnsl-dev,
  pkg-config
 Standards-Version: 4.5.0
 Homepage: https://pagure.io/slapi-nis

Bug#1074258: marked as done (fontforge FTBFS with gettext 0.22.5-1)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 15:19:20 +
with message-id 
and subject line Bug#1074258: fixed in fontforge 1:20230101~dfsg-2
has caused the Debian Bug report #1074258,
regarding fontforge FTBFS with gettext 0.22.5-1
to be marked as done.

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

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


-- 
1074258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fontforge
Version: 1:20230101~dfsg-1.1
Severity: serious
Tags: ftbfs patch
Forwarded: https://github.com/fontforge/fontforge/pull/5330

https://buildd.debian.org/status/fetch.php?pkg=fontforge=s390x=1%3A20230101~dfsg-1.1%2Bb1=1719301120=0

...
FAILED: po/fr.mo /<>/build/nox/po/fr.mo 
cd "/<>/build/nox/po" && /usr/bin/msgfmt --check -o 
"/<>/build/nox/po/fr.mo" "/<>/po/fr.po"
/<>/po/fr.po:294: 'msgstr' is not a valid C format string, unlike 
'msgid'. Reason: In the directive number 3, the argument size specifier is 
invalid.
/<>/po/fr.po:305: 'msgstr' is not a valid C format string, unlike 
'msgid'. Reason: In the directive number 4, the argument size specifier is 
invalid.
/<>/po/fr.po:7435: 'msgstr' is not a valid C format string, unlike 
'msgid'. Reason: In the directive number 2, the argument size specifier is 
invalid.
/<>/po/fr.po:19927: 'msgstr' is not a valid C format string, 
unlike 'msgid'. Reason: In the directive number 2, the argument size specifier 
is invalid.
/<>/po/fr.po:19935: 'msgstr' is not a valid C format string, 
unlike 'msgid'. Reason: In the directive number 2, the argument size specifier 
is invalid.
/<>/po/fr.po:19970: 'msgstr' is not a valid C format string, 
unlike 'msgid'. Reason: In the directive number 2, the argument size specifier 
is invalid.
/<>/po/fr.po:19986: 'msgstr' is not a valid C format string, 
unlike 'msgid'. Reason: In the directive number 2, the argument size specifier 
is invalid.
/<>/po/fr.po:20459: 'msgstr' is not a valid C format string, 
unlike 'msgid'. Reason: In the directive number 2, the argument size specifier 
is invalid.
/<>/po/fr.po:21045: 'msgstr' is not a valid C format string, 
unlike 'msgid'. Reason: In the directive number 2, the argument size specifier 
is invalid.
/<>/po/fr.po:21443: 'msgstr' is not a valid C format string, 
unlike 'msgid'. Reason: In the directive number 2, the argument size specifier 
is invalid.
/<>/po/fr.po:21772: 'msgstr' is not a valid C format string, 
unlike 'msgid'. Reason: In the directive number 2, the argument size specifier 
is invalid.
/<>/po/fr.po:24553: 'msgstr' is not a valid C format string, 
unlike 'msgid'. Reason: In the directive number 2, the argument size specifier 
is invalid.
/<>/po/fr.po:24564: 'msgstr' is not a valid C format string, 
unlike 'msgid'. Reason: In the directive number 2, the argument size specifier 
is invalid.
/usr/bin/msgfmt: found 13 fatal errors
...
--- End Message ---
--- Begin Message ---
Source: fontforge
Source-Version: 1:20230101~dfsg-2
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated fontforge 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: Wed, 26 Jun 2024 10:37:51 -0400
Source: fontforge
Architecture: source
Version: 1:20230101~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Boyuan Yang 
Closes: 1035892 1074258
Changes:
 fontforge (1:20230101~dfsg-2) unstable; urgency=medium
 .
   * debian/control: Bump Standards-Version to 4.7.0.
   * debian/patches/:
 + 0006-Update-po-files-from-Croudin-sources-after-fixing-pr.patch:
   Cherry-pick upstream PR #5330 to refresh po/ directory and fix
   FTBFS with gettext 0.22.5. (Closes: #1074258)
 .
   [ David (Plasma) Paul ]
   * Fully support the nodoc build profile. (Closes: #1035892)
 - Don't build fontforge-doc in nodoc build profile.
 - Mark Build-Depend:python3-sphinx .
Checksums-Sha1:
 f4234bc44fab9de409476346be4e67c29f00455f 2936 fontforge_20230101~dfsg-2.dsc
 

Bug#1073229: marked as done (rust-temp-testdir: autopkgtest timeouts: test::should_not_leave_a_dangling_empty_directory hangs)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 14:55:19 +
with message-id 
and subject line Bug#1073229: fixed in rust-temp-testdir 0.2.3-2
has caused the Debian Bug report #1073229,
regarding rust-temp-testdir: autopkgtest timeouts: 
test::should_not_leave_a_dangling_empty_directory hangs
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.)


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

Source: rust-temp-testdir
Version: 0.2.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. What's worse, 
it fails because it seems to hang and eventually times out due to 
autopkgtest. Can you please investigate the situation and fix it? I 
copied some of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. Also tests that time out (while 
normally running in much less time) are bad for our infrastructure. I 
have added your package to our reject_list and will remove it once this 
bug is closed.


More information about this bug and the reason for filing it can be 
found on 
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

 26s test test::should_resolve_root_in_env ... FAILED
 26s test test::should_resolve_rstest_temp_dir_root_name_in_env ... FAILED
 26s test test::tempdir_permanent_should_do_not_remove_dir ... FAILED
 26s test test::two_temp_dir_should_have_different_path ... FAILED
 86s test test::should_not_leave_a_dangling_empty_directory has been 
running for over 60 seconds
10026s autopkgtest [09:37:55]: ERROR: timed out on command "su -s 
/bin/bash debci ...


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: rust-temp-testdir
Source-Version: 0.2.3-2
Done: Reinhard Tartler 

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated rust-temp-testdir 
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: Wed, 26 Jun 2024 09:18:39 -0400
Source: rust-temp-testdir
Architecture: source
Version: 0.2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Reinhard Tartler 
Closes: 1073229
Changes:
 rust-temp-testdir (0.2.3-2) unstable; urgency=medium
 .
   * Package temp_testdir 0.2.3 from crates.io using debcargo 2.6.1
   * Disable unit tests that randomly hang. Keep integration tests during
 package builds. Closes: #1073229
Checksums-Sha1:
 3efa45e0de421473bc60b8866f10e674487267e4 2238 rust-temp-testdir_0.2.3-2.dsc
 4b4f47e4e8757035f600f042953df6c75658ab1c 3260 
rust-temp-testdir_0.2.3-2.debian.tar.xz
 79469df5c797156a1cb208210e1827bf82baed37 8536 
rust-temp-testdir_0.2.3-2_source.buildinfo
Checksums-Sha256:
 3d1b0ae661e3369304176a7cdbdcbef3e86577beb1fa736e975aa13da2f28c51 2238 
rust-temp-testdir_0.2.3-2.dsc
 7eb78cbf0c3939ad14f5fe2903945ca4f8c82fbb11ea5d46955d8cb735d8300b 3260 
rust-temp-testdir_0.2.3-2.debian.tar.xz
 04e7be49c56def07a9031afb2e6d32f782130fb793c8c73f9e0aff6d0c4b3469 8536 
rust-temp-testdir_0.2.3-2_source.buildinfo
Files:
 936a894a79e4807a9fb97e0027592c56 2238 rust optional 
rust-temp-testdir_0.2.3-2.dsc
 07262987883498eea13853d71337abae 3260 rust optional 
rust-temp-testdir_0.2.3-2.debian.tar.xz
 928a12bdc51323f5d2fd2ca494b3ac77 8536 rust optional 
rust-temp-testdir_0.2.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmZ8FVQUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJsujjBAAms++69cZim+/MyrhvAvJL2yBUOWt
0wnZ0aTJq5Qt0UubqI7zYcGJ9tFZ8WiFk4tncDLXJKexylHQxjQIE6KUlNZ8MpyR
kYmpidt2qYi/ACKrJk+HgEZwteTK0O0qm7zl3WuvmmcNEPJVM3+VZRRAPMqh5DNL
+uzFX8zUoZuJIUwZ6HlHGEFGemqAIyGQajC3RK0QtzQKAvP6a77Oo3VCVcvzmbg+

Bug#1074226: marked as done (sonic-visualiser: FTBFS on armel/armhf)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 14:55:29 +
with message-id 
and subject line Bug#1069317: fixed in vamp-plugin-sdk 2.10.0-5
has caused the Debian Bug report #1069317,
regarding sonic-visualiser: FTBFS on armel/armhf
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.)


-- 
1069317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sonic-visualiser
Version: 4.5.2-2
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: delta...@debian.org

Dear Maintainer,

your package FTBFS on armel/armhf is therefore stuck on unsatisfiable
dependencies. See
https://buildd.debian.org/status/fetch.php?pkg=sonic-visualiser=armel=4.5.2-2%2Bb3=1713251413=0
and
https://buildd.debian.org/status/fetch.php?pkg=sonic-visualiser=armhf=4.5.2-2%2Bb3=1713249425=0


--
Regards

Patrick Franz
--- End Message ---
--- Begin Message ---
Source: vamp-plugin-sdk
Source-Version: 2.10.0-5
Done: IOhannes m zmölnig (Debian/GNU) 

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
vamp-plugin-sdk 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, 26 Jun 2024 15:51:23 +0200
Source: vamp-plugin-sdk
Architecture: source
Version: 2.10.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1069317
Changes:
 vamp-plugin-sdk (2.10.0-5) unstable; urgency=medium
 .
   * Team upload.
 .
   * Upload to unstable.
   * Add time64 compat hints
 .
 vamp-plugin-sdk (2.10.0-5~exp) experimental; urgency=medium
 .
   * Team upload.
 .
   * Rename libraries for 64-bit time_t transition. (Closes: #1069317)
   * B-D on 'pkgconf' rather than 'pkg-config'
   * Add autopkgtest
   * Streamlined copyright information
 + Add 'licensecheck' target
 + Generate d/copyright_hints
   * Apply 'wrap-and-sort -ast'
   * Bump standards version to 4.7.0
Checksums-Sha1:
 2df0215a14e3d5a73d6a9e732606136f1ad41e22 2635 vamp-plugin-sdk_2.10.0-5.dsc
 85989bc09f0beac10662d1e8afbb0edbea4483a9 12836 
vamp-plugin-sdk_2.10.0-5.debian.tar.xz
Checksums-Sha256:
 2313c3ad36c3433a25d81d609bbadd959526a02c814b389e0e984a016c449e1d 2635 
vamp-plugin-sdk_2.10.0-5.dsc
 de7f5cfc96d7fe72e247af5fa15cea0c037377801fbf760b6f5db8c7f848dd03 12836 
vamp-plugin-sdk_2.10.0-5.debian.tar.xz
Files:
 a5b1748a5ae7dcbf1085f0b5db0fd883 2635 libs optional 
vamp-plugin-sdk_2.10.0-5.dsc
 3aac92b45b529d6c4f1aa55ab56ca3ec 12836 libs optional 
vamp-plugin-sdk_2.10.0-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmZ8HXUWHGZvcnVtQHVt
bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+EoaD/wLsoTSD/XG7soPsOOF7CmRrkT+
qEawm2mdJJO8y9ccqEFdXhcofTo/TLOZGC99qaZPR0fST9qS0yGfR5X0KObEl5QX
Q4dThWXgPuyRParYibAU013hpuLKuVZUObc59+UduW62aUP4227w/r+ofTP7lGXc
UKl438lv1jxUv8BsDMN45WoM5hSMJl+g3NsguDNp0a8QZIYh+jgpMacIRddmXU5x
1gVe5A8Y9OM5+wrvgVzdUCCfoKtpiJOQbxkoMLN7SPYd9E3tIuNmi0xfDBl2dVJt
5M4X/iCL6pA0YAgfML87QAIaLdBL3WFBLTk9pM/iHM+qpP91qLmhx3yNllp/Vram
NYv2EZvG7HYDLtsXdEq+ZabP1+LNKw/Yxw0c3eCp8v4akqIHY3Do4Xr5G8hJg7z8
VkzILh6C+6Mhs/5c3lBT7vJu19TL3jqlQ/cyqvqxK6HO8Tht/OOOtdYj/ZHpuuzn
cjLXpjHDWGL7Y5mJe+KuNSFYH083ZDi1LeleTHkKmDRZ9Veji3/PfMaRaul2+ewR
OFO8it6cqIHV2IzsPNxOtYk8RTSKci0rkycGmJJdEAVD3R5zUPxANM6sJXLO6qaX
Olm8AjlFFOAyA2rqIXvFGjnhlpz2eWqDhq0lvpSg6DixqNRJbE2oC9+Tva8qzPx2
2fqMExXI73P3ohsegA==
=hxc4
-END PGP SIGNATURE-



pgpDOvbEYs26n.pgp
Description: PGP signature
--- End Message ---

Bug#1069317: marked as done (FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 14:55:29 +
with message-id 
and subject line Bug#1069317: fixed in vamp-plugin-sdk 2.10.0-5
has caused the Debian Bug report #1069317,
regarding FTBFS: tests failed
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.)


-- 
1069317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sonic-visualiser
Version: 4.5.2-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=sonic-
visualiser=armel=4.5.2-2%2Bb3=1713251413=0

FAIL!  : TestVampRealTime::fromTimeval() Compared values are not the same
   Loc: [test-svcore-base.p/../../svcore/base/test/TestVampRealTime.h(144)]



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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: vamp-plugin-sdk
Source-Version: 2.10.0-5
Done: IOhannes m zmölnig (Debian/GNU) 

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
vamp-plugin-sdk 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, 26 Jun 2024 15:51:23 +0200
Source: vamp-plugin-sdk
Architecture: source
Version: 2.10.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1069317
Changes:
 vamp-plugin-sdk (2.10.0-5) unstable; urgency=medium
 .
   * Team upload.
 .
   * Upload to unstable.
   * Add time64 compat hints
 .
 vamp-plugin-sdk (2.10.0-5~exp) experimental; urgency=medium
 .
   * Team upload.
 .
   * Rename libraries for 64-bit time_t transition. (Closes: #1069317)
   * B-D on 'pkgconf' rather than 'pkg-config'
   * Add autopkgtest
   * Streamlined copyright information
 + Add 'licensecheck' target
 + Generate d/copyright_hints
   * Apply 'wrap-and-sort -ast'
   * Bump standards version to 4.7.0
Checksums-Sha1:
 2df0215a14e3d5a73d6a9e732606136f1ad41e22 2635 vamp-plugin-sdk_2.10.0-5.dsc
 85989bc09f0beac10662d1e8afbb0edbea4483a9 12836 
vamp-plugin-sdk_2.10.0-5.debian.tar.xz
Checksums-Sha256:
 2313c3ad36c3433a25d81d609bbadd959526a02c814b389e0e984a016c449e1d 2635 
vamp-plugin-sdk_2.10.0-5.dsc
 de7f5cfc96d7fe72e247af5fa15cea0c037377801fbf760b6f5db8c7f848dd03 12836 
vamp-plugin-sdk_2.10.0-5.debian.tar.xz
Files:
 a5b1748a5ae7dcbf1085f0b5db0fd883 2635 libs optional 
vamp-plugin-sdk_2.10.0-5.dsc
 3aac92b45b529d6c4f1aa55ab56ca3ec 12836 libs optional 
vamp-plugin-sdk_2.10.0-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmZ8HXUWHGZvcnVtQHVt
bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+EoaD/wLsoTSD/XG7soPsOOF7CmRrkT+
qEawm2mdJJO8y9ccqEFdXhcofTo/TLOZGC99qaZPR0fST9qS0yGfR5X0KObEl5QX
Q4dThWXgPuyRParYibAU013hpuLKuVZUObc59+UduW62aUP4227w/r+ofTP7lGXc
UKl438lv1jxUv8BsDMN45WoM5hSMJl+g3NsguDNp0a8QZIYh+jgpMacIRddmXU5x
1gVe5A8Y9OM5+wrvgVzdUCCfoKtpiJOQbxkoMLN7SPYd9E3tIuNmi0xfDBl2dVJt
5M4X/iCL6pA0YAgfML87QAIaLdBL3WFBLTk9pM/iHM+qpP91qLmhx3yNllp/Vram
NYv2EZvG7HYDLtsXdEq+ZabP1+LNKw/Yxw0c3eCp8v4akqIHY3Do4Xr5G8hJg7z8
VkzILh6C+6Mhs/5c3lBT7vJu19TL3jqlQ/cyqvqxK6HO8Tht/OOOtdYj/ZHpuuzn
cjLXpjHDWGL7Y5mJe+KuNSFYH083ZDi1LeleTHkKmDRZ9Veji3/PfMaRaul2+ewR
OFO8it6cqIHV2IzsPNxOtYk8RTSKci0rkycGmJJdEAVD3R5zUPxANM6sJXLO6qaX
Olm8AjlFFOAyA2rqIXvFGjnhlpz2eWqDhq0lvpSg6DixqNRJbE2oC9+Tva8qzPx2
2fqMExXI73P3ohsegA==
=hxc4
-END PGP SIGNATURE-



pgpx3ar9d99dZ.pgp
Description: PGP signature
--- End Message ---

Bug#1074321: createrepo-c FTBFS: error: implicit declaration of function ‘xmlCheckUTF8’

[Adrian Bunk]

Source: createrepo-c
Version: 0.17.3-4
Severity: serious
Tags: ftbfs patch
Forwarded: https://github.com/rpm-software-management/createrepo_c/pull/402

https://buildd.debian.org/status/logs.php?pkg=createrepo-c=0.17.3-4%2Bb2

...
/<>/src/sqlite.c: In function ‘cr_sqlite3_bind_text’:
/<>/src/sqlite.c:76:16: error: implicit declaration of function 
‘xmlCheckUTF8’ [-Werror=implicit-function-declaration]
   76 | } else if (xmlCheckUTF8((const unsigned char *) orig_content)
  |^~~~
...

Bug#1071883: marked as done (q2-quality-control: FTBFS: unsatisfiable build-dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 16:26:36 +0200
with message-id 
and subject line Re: q2-quality-control: FTBFS: unsatisfiable build-dependencies
has caused the Debian Bug report #1071883,
regarding q2-quality-control: FTBFS: unsatisfiable build-dependencies
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.)


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

Package: src:q2-quality-control
Version: 2024.2.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
Install main build dependencies (apt-based resolver)


Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python3-ipywidgets : Depends: python3-widgetsnbextension but it is not 
installable
  Depends: jupyter-nbextension-jupyter-js-widgets but it is 
not installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.
E: Package installation failed
Not removing build depends: cloned chroot in use



The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202405/

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---

Version: 2024.5.0-1

thanks

I didn't see this bug prior to making the update



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: otpclient-cli usage disagrees with the man page

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1074260 {Done: Francisco Vilmar Cardoso Ruviaro } 
[otpclient-cli] otpclient-cli: does not output anything
Bug reopened
Ignoring request to alter fixed versions of bug #1074260 to the same values 
previously set
> retitle -1 otpclient-cli usage disagrees with the man page
Bug #1074260 [otpclient-cli] otpclient-cli: does not output anything
Changed Bug title to 'otpclient-cli usage disagrees with the man page' from 
'otpclient-cli: does not output anything'.
> severity -1 normal
Bug #1074260 [otpclient-cli] otpclient-cli usage disagrees with the man page
Severity set to 'normal' from 'grave'

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

Bug#1074260: otpclient-cli usage disagrees with the man page

[Vincent Lefevre]

Control: reopen -1
Control: retitle -1 otpclient-cli usage disagrees with the man page
Control: severity -1 normal

On 2024-06-26 13:03:06 +, Debian Bug Tracking System wrote:
> Hi Vincent,
> 
> On Tue, 25 Jun 2024 15:09:17 +0200 Vincent Lefevre  wrote:
> > 
> > "otpclient-cli show -a " or "otpclient-cli list" prompts
> > for the password, but does not output anything else.
> 
> The command is almost correct, but the hyphens are missing,
> try this:
> 
> $ otpclient-cli --show -a 
> 
> $ otpclient-cli --list

This is not what the otpclient-cli(1) man page says:

   Main Options:

  -v, --version
 Show program version.

  show   Show a token.

  list   List all pairs of account and issuer.

  export Export data.

I suspect that these were intended to be commands, thus without
hyphens. But perhaps that this is no longer the case.

So either the program or the man page needs to be changed.

The man page also gives

   Help Options:

  -h, --help
 Show this help.

  --help-show
 Show options.

  --help-export
 Export options.

The -h / --help option works and gives a different usage,
and --help-show and --help-export do not work.

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

Bug#1073380: marked as done (ansible-lint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 15:12:37 +0200
with message-id 
and subject line Re: ansible-lint: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
has caused the Debian Bug report #1073380,
regarding ansible-lint: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
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.)


-- 
1073380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ansible-lint
Version: 6.17.2-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
> module
> I: pybuild base:311: python3.12 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12  
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/ansiblelint
> copying src/ansiblelint/utils.py -> build/lib/ansiblelint
> copying src/ansiblelint/__init__.py -> build/lib/ansiblelint
> copying src/ansiblelint/runner.py -> build/lib/ansiblelint
> copying src/ansiblelint/file_utils.py -> build/lib/ansiblelint
> copying src/ansiblelint/stats.py -> build/lib/ansiblelint
> copying src/ansiblelint/generate_docs.py -> build/lib/ansiblelint
> copying src/ansiblelint/logger.py -> build/lib/ansiblelint
> copying src/ansiblelint/version.py -> build/lib/ansiblelint
> copying src/ansiblelint/_version.py -> build/lib/ansiblelint
> copying src/ansiblelint/yaml_utils.py -> build/lib/ansiblelint
> copying src/ansiblelint/color.py -> build/lib/ansiblelint
> copying src/ansiblelint/__main__.py -> build/lib/ansiblelint
> copying src/ansiblelint/constants.py -> build/lib/ansiblelint
> copying src/ansiblelint/text.py -> build/lib/ansiblelint
> copying src/ansiblelint/skip_utils.py -> build/lib/ansiblelint
> copying src/ansiblelint/errors.py -> build/lib/ansiblelint
> copying src/ansiblelint/transformer.py -> build/lib/ansiblelint
> copying src/ansiblelint/cli.py -> build/lib/ansiblelint
> copying src/ansiblelint/app.py -> build/lib/ansiblelint
> copying src/ansiblelint/config.py -> build/lib/ansiblelint
> copying src/ansiblelint/loaders.py -> build/lib/ansiblelint
> copying src/ansiblelint/_mockings.py -> build/lib/ansiblelint
> creating build/lib/ansiblelint/schemas
> copying src/ansiblelint/schemas/__init__.py -> build/lib/ansiblelint/schemas
> copying src/ansiblelint/schemas/main.py -> build/lib/ansiblelint/schemas
> copying src/ansiblelint/schemas/__main__.py -> build/lib/ansiblelint/schemas
> creating build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/no_same_owner.py -> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/avoid_implicit.py -> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/empty_string_compare.py -> 
> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/risky_file_permissions.py -> 
> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/__init__.py -> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/meta_no_tags.py -> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/command_instead_of_module.py -> 
> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/fqcn.py -> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/galaxy.py -> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/package_latest.py -> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/no_prompting.py -> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/key_order.py -> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/name.py -> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/syntax_check.py -> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/risky_octal.py -> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/partial_become.py -> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/only_builtins.py -> build/lib/ansiblelint/rules
> copying src/ansiblelint/rules/no_changed_when.py -> 
> 

Bug#1074260: marked as done (otpclient-cli: does not output anything)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 13:01:28 +
with message-id 
and subject line Re: otpclient-cli: does not output anything
has caused the Debian Bug report #1074260,
regarding otpclient-cli: does not output anything
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.)


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

"otpclient-cli show -a " or "otpclient-cli list" prompts
for the password, but does not output anything else.

No issues with the GUI version.

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

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

Versions of packages otpclient-cli depends on:
ii  libc62.38-13
ii  libcotp3 3.0.0-1+b1
ii  libgcrypt20  1.10.3-3
ii  libglib2.0-0t64  2.80.3-1
ii  libjansson4  2.14-2+b2
ii  libsecret-1-00.21.4-1+b1
ii  libuuid1 2.40.1-9

Versions of packages otpclient-cli recommends:
ii  otpclient  3.6.0-1

otpclient-cli suggests no packages.

-- no debconf information

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


On Tue, 25 Jun 2024 15:09:17 +0200 Vincent Lefevre  wrote:
> 
> "otpclient-cli show -a " or "otpclient-cli list" prompts
> for the password, but does not output anything else.

The command is almost correct, but the hyphens are missing,
try this:

$ otpclient-cli --show -a 

$ otpclient-cli --list


Cheers,
-- 
Francisco Vilmar Cardoso Ruviaro 
4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#1073414: marked as done (conda-package-streaming: FTBFS: unsatisfiable build-dependency: libzstd1 (< 1.5.6~) but 1.5.6+dfsg-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 14:51:15 +0200
with message-id 
and subject line Re: conda-package-streaming: FTBFS: unsatisfiable 
build-dependency: libzstd1 (< 1.5.6~) but 1.5.6+dfsg-1 is to be installed
has caused the Debian Bug report #1073414,
regarding conda-package-streaming: FTBFS: unsatisfiable build-dependency: 
libzstd1 (< 1.5.6~) but 1.5.6+dfsg-1 is to be installed
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.)


-- 
1073414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: conda-package-streaming
Version: 0.9.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-python, 
> pybuild-plugin-pyproject, python3-flit-scm, python3, python3-setuptools, 
> conda-package-handling, python3-pytest, python3-pytest-cov, 
> python3-pytest-mock, python3-boto3, python3-bottle, python3-zstandard, flit, 
> python3:any | python3-all:any | python3-dev:any | python3-all-dev:any | 
> dh-sequence-python3, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-python, 
> pybuild-plugin-pyproject, python3-flit-scm, python3, python3-setuptools, 
> conda-package-handling, python3-pytest, python3-pytest-cov, 
> python3-pytest-mock, python3-boto3, python3-bottle, python3-zstandard, flit, 
> python3:any, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [612 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1008 B]
> Get:5 copy:/<>/apt_archive ./ Packages [883 B]
> Fetched 2503 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  python3-zstandard : Depends: libzstd1 (< 1.5.6~) but 1.5.6+dfsg-1 is to be 
> installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/conda-package-streaming_0.9.0-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Forgot to close this bug in d/changelog thus closing it manually, Andreas.
-- 
https://fam-tille.de--- End Message ---

Bug#1073077: marked as done (krita: Fails to build with jpeg-xl 0.9)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 08:39:04 -0400
with message-id 

and subject line Re: krita: Fails to build with jpeg-xl 0.9
has caused the Debian Bug report #1073077,
regarding krita: Fails to build with jpeg-xl 0.9
to be marked as done.

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

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


-- 
1073077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: krita
Version: 1:5.2.2+dfsg-3
Severity: important
Tags: ftbfs
X-Debbugs-CC: jpeg...@packages.debian.org

krita fails to build with jpeg-xl 0.9 available in Debian Experimental.

I tried cherry-picking 2 patches which I thought might fix the issue
but the build still fails for me.

https://invent.kde.org/graphics/krita/-/commit/6ddb599
https://invent.kde.org/graphics/krita/-/commit/546765d

Build logs

https://launchpad.net/ubuntu/+source/krita/1:5.2.2+dfsg-3build3
https://launchpad.net/~jbicha/+archive/ubuntu/arch2/+sourcepub/16216044/+listing-archive-extra

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Version: 1:5.2.3+dfsg-1

Thank you,
Jeremy Bícha--- End Message ---

Bug#1074137: org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code (CVE-2024-39331)

[Max Nikulin]

On Wed, 26 Jun 2024 17:24:25 +0700 Max Nikulin wrote:

On Sun, 23 Jun 2024 18:16:27 +0200 Salvatore Bonaccorso wrote:
> 
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f4cc61636947b5c2f0afc67174dd369fe3277aa8

Will the fix be backported to bookworm emacs-28 package?


Sorry, I have missed fix for CVE-2024-39331
https://tracker.debian.org/news/1539939/accepted-emacs-12821-15deb12u3-source-into-stable-security/
"Accepted emacs 1:28.2+1-15+deb12u3 (source) into stable-security"


I am surprised by a conclusion for
https://security-tracker.debian.org/tracker/CVE-2024-30202
> [bookworm] - emacs  (Minor issue, will be fixed via point release)


that includes fixes
https://tracker.debian.org/news/1537392/accepted-emacs-12821-15deb12u2-source-into-proposed-updates/
"Accepted emacs 1:28.2+1-15+deb12u2 (source) into proposed-updates"

CVE-2024-30202, CVE-2024-30203, CVE-2024-30204 & CVE-2024-30205

Thank you for this work.

Processed: Re: Bug#1073788: gimp: whole-system froze when adjusting threshold

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1073788 [sway] sway: whole system froze when adjusting threshold in gimp
Severity set to 'normal' from 'critical'

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

Bug#1073788: gimp: whole-system froze when adjusting threshold

[Jochen Sprickerhof]

Control: severity -1 normal

Hi,

* Manny  [2024-06-18 13:13]:

Opened “Colors » Threshold…”. Some images have an interesting graph to
help determine where to move the slider and some just have an empty
graph. This may not be related but I noticed that both times spaz’d
out it was when an image had an empty graph (or nearly empty).

As soon as the slider is moved, *both* screens on a dual headed
machine go black for ~1½ seconds then pop back on. GIMP is only ever
present one of the two displays, never spread out. On one occassion,
the system froze for a few seconds before the cursor could move
again. On another occasion, the keyboard and mouse were permanently
frozen. I walked away from the machine for ~5 minutes or so to give it
time to unfreeze, but it never unfroze. I was ultimately forced to
physically force a power down of the whole system. It would have been
catastrophic if I had unsaved work in any application.


I was not able to reproduce this in a debvm, thus lowering severity.

What I tried:

$ debvm-create -r stable -- --hook-dir=/usr/share/mmdebstrap/hooks/useradd \
  
--include=linux-image-generic,greetd,sway,sway-backgrounds,suckless-tools,xwayland,gimp
 \
  --customize-hook='echo \'[initial_session]\ncommand = "sway"\nuser = "user"\n[terminal]\nvt = 
1\n[default_session]\ncommand = "/usr/sbin/agreety -c sway"\nuser = "user"\' > 
"$1/etc/greetd/config.toml"'
$ debvm-run -g -- -vga qxl

That gives me a logged in sway where I can hit Ctrl-D to execute gimp 
(you can use Ctrl-Alt-G to let qemu grab the key in case it is mapped on 
your host system.)


Then in gimp I created a new image by taking a screenshot and played 
with the sliders in the Threshold window.


To me this bug sounds a lot like a out of memory problem (maybe even out 
of video memory). Can you have a log at the system log at the time of 
the crash? Try:


sudo journalctl -S 2024-06-18

for that. Also, can you reproduce the bug?

Cheers Jochen


signature.asc
Description: PGP signature

Bug#1074222: pycorrfit FTBFS with Python 3.12 as default

[Adrian Bunk]

On Wed, Jun 26, 2024 at 06:18:35PM +0800, Bo YU wrote:
> Hi,
> On Mon, Jun 24, 2024 at 09:40:02PM +0300, Adrian Bunk wrote:
> > Source: pycorrfit
> > Version: 1.1.7+dfsg-2
> > Severity: serious
> > Tags: ftbfs trixie sid
> > 
> >self.run_command('egg_info')
> >  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 
> > 318, in run_command
> >self.distribution.run_command(command)
> >  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in 
> > run_command
> >super().run_command(command)
> >  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> > 987, in run_command
> >cmd_obj.ensure_finalized()
> >  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 
> > 111, in ensure_finalized
> >self.finalize_options()
> >  File "/usr/lib/python3/dist-packages/setuptools/command/egg_info.py", line 
> > 225, in finalize_options
> >parsed_version = packaging.version.Version(self.egg_version)
> > ^^^
> >  File 
> > "/usr/lib/python3/dist-packages/setuptools/_vendor/packaging/version.py", 
> > line 198, in __init__
> >raise InvalidVersion(f"Invalid version: '{version}'")
> > setuptools.extern.packaging.version.InvalidVersion: Invalid version: 
> > 'unknown'
> > E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1: 
> > /usr/bin/python3 setup.py build
> > dh_auto_build: error: pybuild --build -i python{version} -p 3.12 returned 
> > exit code 13
> > make[1]: *** [debian/rules:49: override_dh_auto_build] Error 25
> 
> I can not reproduce it now locally:
>...
> So could we rebuild it again?

Still fails on the buildd:
https://buildd.debian.org/status/fetch.php?pkg=pycorrfit=amd64=1.1.7%2Bdfsg-2%2Bb2=1719400031=0

Based on the error message, I wouldn't be surprised if the +b2 from the 
binNMU version would be part of the problem.

> Regards,

cu
Adrian

Bug#1070988: src:q2-feature-table: fails to migrate to testing for too long: autopkgtest regression

[Michael R. Crusoe]

Bump to give us more time


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1074137: org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code (CVE-2024-39331)

[Max Nikulin]

On Sun, 23 Jun 2024 18:16:27 +0200 Salvatore Bonaccorso wrote:

https://www.openwall.com/lists/oss-security/2024/06/23/1

Upstream fix (in org-mode);

https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f4cc61636947b5c2f0afc67174dd369fe3277aa8


Will the fix be backported to bookworm emacs-28 package? The change is
local, so risk of unexpected consequences due to the patch should be low.

Severity of the vulnerability should not be lower than for
https://nvd.nist.gov/vuln/detail/CVE-2023-28617


Base Score:  7.8 HIGH
Vector:  CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H


However to exploit that vulnerability a user must invoke an inherently
insecure action. In the case of CVE-2024-39331 it is enough to open a
crafted file or a mail message.

I am surprised by a conclusion for
https://security-tracker.debian.org/tracker/CVE-2024-30202

[bookworm] - emacs  (Minor issue, will be fixed via point release)

that is arbitrary code execution on opening a file or a mail message as
well.

A file may have an almost arbitrary suffix, e.g. a valid python code, so 
activation of Org mode may be unexpected for a user opening some file:


cve-2024-39331.py
 8< 
#!/usr/bin/env python3
# -*- mode: org; -*-
#+link: vuln %(shell-command)
"[[vuln:emacs -Q]]"
#+begin_src python
if __name__ == '__main__':
print("Hello, Org!")
#+end_src
 >8 

It should launch another emacs instance.

I expect that this message is enough to demonstrate the issue since
Gnus calls Org mode preview for any "#+keyword:" and next line in a
text/plain message.

#+link: vuln %(shell-command)
[[vuln:emacs -Q]]

Bug#1074299: marked as done (samba-vfs-ceph and samba-vfs-glusterfs have an undeclared file conflict)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 10:16:17 +
with message-id 
and subject line Bug#1074299: fixed in samba 2:4.20.2+dfsg-4
has caused the Debian Bug report #1074299,
regarding samba-vfs-ceph and samba-vfs-glusterfs have an undeclared file 
conflict
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.)


-- 
1074299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba-vfs-glusterfs,samba-vfs-ceph
Version: 2:4.20.2+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + samba-vfs-modules

samba-vfs-ceph and samba-vfs-glusterfs have an undeclared file conflict.
This may result in an unpack error from dpkg.

The files
 * /usr/lib/x86_64-linux-gnu/samba/vfs/ceph.so
 * /usr/lib/x86_64-linux-gnu/samba/vfs/ceph_snapshots.so
are contained in the packages
 * samba-vfs-ceph/2:4.20.2+dfsg-3 as present in unstable
 * samba-vfs-modules
   * 2:4.13.13+dfsg-1~deb11u5 as present in bullseye
   * 2:4.13.13+dfsg-1~deb11u6 as present in 
bullseye-proposed-updates|bullseye-security
   * 2:4.17.12+dfsg-0+deb12u1 as present in bookworm|bookworm-security
   * 2:4.17.12+dfsg-0+deb12u1~bpo11+1 as present in bullseye-backports
   * 2:4.17.9+dfsg-0+deb12u3 as present in bookworm-updates
   * 2:4.20.2+dfsg-2 as present in trixie
   * 2:4.20.2+dfsg-2~bpo12+2 as present in bookworm-backports

The files
 * /usr/lib/x86_64-linux-gnu/samba/vfs/glusterfs.so
 * /usr/lib/x86_64-linux-gnu/samba/vfs/glusterfs_fuse.so
are contained in the packages
 * samba-vfs-glusterfs/2:4.20.2+dfsg-3 as present in unstable
 * samba-vfs-modules
   * 2:4.13.13+dfsg-1~deb11u5 as present in bullseye
   * 2:4.13.13+dfsg-1~deb11u6 as present in 
bullseye-proposed-updates|bullseye-security
   * 2:4.17.12+dfsg-0+deb12u1 as present in bookworm|bookworm-security
   * 2:4.17.12+dfsg-0+deb12u1~bpo11+1 as present in bullseye-backports
   * 2:4.17.9+dfsg-0+deb12u3 as present in bookworm-updates
   * 2:4.20.2+dfsg-2 as present in trixie
   * 2:4.20.2+dfsg-2~bpo12+2 as present in bookworm-backports

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.20.2+dfsg-4
Done: Michael Tokarev 

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated samba 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: Wed, 26 Jun 2024 12:20:08 +0300
Source: samba
Architecture: source
Version: 2:4.20.2+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Samba Maintainers 
Changed-By: Michael Tokarev 
Closes: 1074299
Changes:
 samba (2:4.20.2+dfsg-4) unstable; urgency=medium
 .
   * d/control: add the forgotten epoch for Breaks/Replaces
 of samba-vfs-ceph & samba-vfs-glusterfs (Closes: #1074299)
Checksums-Sha1:
 2a4457b530397d45cf577a9a6a8f925552e851b5 4818 samba_4.20.2+dfsg-4.dsc
 cdd9bc00c2d178c395ac9667e52d3d0360d7121c 177704 
samba_4.20.2+dfsg-4.debian.tar.xz
 9da424359fd706805198bb9e025fd4eda884ed7c 6367 
samba_4.20.2+dfsg-4_source.buildinfo
Checksums-Sha256:
 0f8db30e9e1ceaff1e93fe807bb5105cc6f4e4838ef17d2ec0383f75df262ded 4818 
samba_4.20.2+dfsg-4.dsc
 79fe1d72826dec9832db6d1cb5a19cf572fd52b60d268b264cdd2f9efa0e57b7 177704 
samba_4.20.2+dfsg-4.debian.tar.xz
 b5d8fd52d517ee5e4dc65537497d2b7f8eb9bd5516c530909a3bdf4bb7328bb9 6367 
samba_4.20.2+dfsg-4_source.buildinfo
Files:
 f1d805bd1c53a90d0fa74b3a8fe7ccf0 4818 net optional 

Bug#1074222: pycorrfit FTBFS with Python 3.12 as default

[Bo YU]

Hi,
On Mon, Jun 24, 2024 at 09:40:02PM +0300, Adrian Bunk wrote:

Source: pycorrfit
Version: 1.1.7+dfsg-2
Severity: serious
Tags: ftbfs trixie sid

   self.run_command('egg_info')
 File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 318, 
in run_command
   self.distribution.run_command(command)
 File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in 
run_command
   super().run_command(command)
 File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 987, 
in run_command
   cmd_obj.ensure_finalized()
 File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 111, 
in ensure_finalized
   self.finalize_options()
 File "/usr/lib/python3/dist-packages/setuptools/command/egg_info.py", line 
225, in finalize_options
   parsed_version = packaging.version.Version(self.egg_version)
^^^
 File "/usr/lib/python3/dist-packages/setuptools/_vendor/packaging/version.py", 
line 198, in __init__
   raise InvalidVersion(f"Invalid version: '{version}'")
setuptools.extern.packaging.version.InvalidVersion: Invalid version: 'unknown'
E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p 3.12 returned exit 
code 13
make[1]: *** [debian/rules:49: override_dh_auto_build] Error 25


I can not reproduce it now locally:

```
...
Build Architecture: amd64
Build Type: binary
Build-Space: 10680
Build-Time: 1960
Distribution: unstable
Host Architecture: amd64
Install-Time: 273
Job: /home/vimer/build/rfs/pycorrfit/new/pycorrfit_1.1.7+dfsg-2.dsc
Lintian: warn
Machine Architecture: amd64
Package: pycorrfit
Package-Time: 2267
Source-Version: 1.1.7+dfsg-2
Space: 10680
Status: successful
Version: 1.1.7+dfsg-2

Finished at 2024-06-26T07:10:35Z
Build needed 00:37:47, 10680k disk space
```

So could we rebuild it again?


--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Processed: Forwarded

[Debian Bug Tracking System]

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

> forwarded 1073436 https://github.com/sissaschool/xmlschema/issues/405
Bug #1073436 [src:python-xmlschema] python-xmlschema: FTBFS: AssertionError: 
'file:/filer01/MY_HOME/dev/XMLSCHEMA/test.xsd' != 
'file:filer01/MY_HOME/dev/XMLSCHEMA/test.xsd'
Set Bug forwarded-to-address to 
'https://github.com/sissaschool/xmlschema/issues/405'.
>
End of message, stopping processing here.

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

Bug#1071774: marked as done (orange3: FTBFS: Orange/classification/_simple_tree.c:63:9: error: implicit declaration of function ‘qsort_r’)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 09:30:16 +
with message-id 
and subject line Bug#1071774: fixed in orange3 3.37.0-1
has caused the Debian Bug report #1071774,
regarding orange3: FTBFS: Orange/classification/_simple_tree.c:63:9: error: 
implicit declaration of function ‘qsort_r’
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.)


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

Package: src:orange3
Version: 3.35.0+ds1-5
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules build
dh build --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
module
I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.12_orange3
* Building wheel...
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-cpython-312

[... snipped ...]

creating build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/tests
copying Orange/widgets/data/utils/tests/test_tableview.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/tests
copying Orange/widgets/data/utils/tests/__init__.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/tests
creating 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/test_rectangular_selection.py 
-> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/base.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/test_bracket_highlighter.py 
-> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/test_draw_whitespace.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/test_api.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/test_edit.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/test_indent.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/test_vim.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/run_all.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/__init__.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
creating 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests/test_indenter
copying Orange/widgets/data/utils/pythoneditor/tests/test_indenter/test_python.py 
-> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests/test_indenter
copying Orange/widgets/data/utils/pythoneditor/tests/test_indenter/indenttest.py 
-> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests/test_indenter
copying Orange/widgets/data/utils/pythoneditor/tests/test_indenter/__init__.py 
-> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests/test_indenter
creating build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owdistancefile.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owpca.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owlouvain.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owsavedistances.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying 

Processed: severity of 1072678 is important

[Debian Bug Tracking System]

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

> severity 1072678 important
Bug #1072678 [src:nextpnr] : FTBFS on armel, armhf ( error: 
‘QOpenGLFunctions_3_2_Core’ does not name a type;)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1068961: llvm-toolchain-18: block migration to testing: to many llvm-toolchain versions in testing

[Drew Parsons]

On 2024-06-26 11:05, sylvestre...@ledru.info wrote:
I am sorry but I don't think it is reasonable to keep/maintains all the 
versions of LLVM for a single package.


Keep in mind it's not a single package exactly.  It's llvmlite, but also 
numba, and then every package that uses numba (critical for a bunch of 
Frederic-Emmanuel Picca's packages, for instance, and optionally used by 
several of mine)

Bug#1073436: python-xmlschema: FTBFS: AssertionError: 'file://///filer01/MY_HOME/dev/XMLSCHEMA/test.xsd' != 'file:////filer01/MY_HOME/dev/XMLSCHEMA/test.xsd'

[Christian Kastner]

On 2024-06-16 15:10, Lucas Nussbaum wrote:
> Source: python-xmlschema
> Version: 3.3.1-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240615 ftbfs-trixie
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

>> ==
>> FAIL: test_normalize_url_slashes 
>> (tests.test_locations.TestLocations.test_normalize_url_slashes)
>> --
>> Traceback (most recent call last):
>>   File 
>> "/<>/.pybuild/cpython3_3.12_xmlschema/build/tests/test_locations.py",
>>  line 314, in test_normalize_url_slashes
>> self.assertRegex(normalize_url('root/dir1/schema.xsd'),
>> AssertionError: Regex didn't match: 'file:root/dir1/schema.xsd' not 
>> found in 'file://root/dir1/schema.xsd'
>>
>> ==
>> FAIL: test_normalize_url_with_base_unc_path 
>> (tests.test_locations.TestLocations.test_normalize_url_with_base_unc_path)
>> --
>> Traceback (most recent call last):
>>   File 
>> "/<>/.pybuild/cpython3_3.12_xmlschema/build/tests/test_locations.py",
>>  line 283, in test_normalize_url_with_base_unc_path
>> self.assertEqual(url, 'file:filer01/MY_HOME/dev/XMLSCHEMA/test.xsd')
>> AssertionError: 'file:/filer01/MY_HOME/dev/XMLSCHEMA/test.xsd' != 
>> 'file:filer01/MY_HOME/dev/XMLSCHEMA/test.xsd'
>> - file:/filer01/MY_HOME/dev/XMLSCHEMA/test.xsd
>> ?  -
>> + file:filer01/MY_HOME/dev/XMLSCHEMA/test.xsd

This only occurs with Python 3.12. I'll look into it.

Bug#1068961: llvm-toolchain-18: block migration to testing: to many llvm-toolchain versions in testing

[sylvestredeb]

Le mercredi 26 juin 2024 à 10:51, Drew Parsons  a écrit :

> 
> 
> > If possible, it would be sensible in principle for debian to drop
> 
> > llvm-toolchain-15 and llvm-toolchain-16.
> > i.e. only keep llvm-toolchain-14 (for llvmlite/numba)
> > and the latest llvm-toolchain
> 
> 
> It belatedly occurs to me that it could be dangerous to drop the interim
> versions of llvm, since at some point llvmlite will upgrade its llvm
> support, and won't necessarily jump directly to the most recent llvm.

I am sorry but I don't think it is reasonable to keep/maintains all the 
versions of LLVM for a single package.

Cheers
Sylvestre

Processed: firebird-utils has an undeclared file conflict

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + firebird3.0-server
Bug #1074298 [firebird-utils] firebird-utils has an undeclared file conflict
Added indication that 1074298 affects firebird3.0-server

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

Bug#1074299: samba-vfs-ceph and samba-vfs-glusterfs have an undeclared file conflict

[Helmut Grohne]

Package: samba-vfs-glusterfs,samba-vfs-ceph
Version: 2:4.20.2+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + samba-vfs-modules

samba-vfs-ceph and samba-vfs-glusterfs have an undeclared file conflict.
This may result in an unpack error from dpkg.

The files
 * /usr/lib/x86_64-linux-gnu/samba/vfs/ceph.so
 * /usr/lib/x86_64-linux-gnu/samba/vfs/ceph_snapshots.so
are contained in the packages
 * samba-vfs-ceph/2:4.20.2+dfsg-3 as present in unstable
 * samba-vfs-modules
   * 2:4.13.13+dfsg-1~deb11u5 as present in bullseye
   * 2:4.13.13+dfsg-1~deb11u6 as present in 
bullseye-proposed-updates|bullseye-security
   * 2:4.17.12+dfsg-0+deb12u1 as present in bookworm|bookworm-security
   * 2:4.17.12+dfsg-0+deb12u1~bpo11+1 as present in bullseye-backports
   * 2:4.17.9+dfsg-0+deb12u3 as present in bookworm-updates
   * 2:4.20.2+dfsg-2 as present in trixie
   * 2:4.20.2+dfsg-2~bpo12+2 as present in bookworm-backports

The files
 * /usr/lib/x86_64-linux-gnu/samba/vfs/glusterfs.so
 * /usr/lib/x86_64-linux-gnu/samba/vfs/glusterfs_fuse.so
are contained in the packages
 * samba-vfs-glusterfs/2:4.20.2+dfsg-3 as present in unstable
 * samba-vfs-modules
   * 2:4.13.13+dfsg-1~deb11u5 as present in bullseye
   * 2:4.13.13+dfsg-1~deb11u6 as present in 
bullseye-proposed-updates|bullseye-security
   * 2:4.17.12+dfsg-0+deb12u1 as present in bookworm|bookworm-security
   * 2:4.17.12+dfsg-0+deb12u1~bpo11+1 as present in bullseye-backports
   * 2:4.17.9+dfsg-0+deb12u3 as present in bookworm-updates
   * 2:4.20.2+dfsg-2 as present in trixie
   * 2:4.20.2+dfsg-2~bpo12+2 as present in bookworm-backports

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

Processed: samba-vfs-ceph and samba-vfs-glusterfs have an undeclared file conflict

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + samba-vfs-modules
Bug #1074299 [samba-vfs-glusterfs,samba-vfs-ceph] samba-vfs-ceph and 
samba-vfs-glusterfs have an undeclared file conflict
Added indication that 1074299 affects samba-vfs-modules

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

Bug#1074298: firebird-utils has an undeclared file conflict

[Helmut Grohne]

Package: firebird-utils
Version: 4.0.4.3010.ds6-4
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + firebird3.0-server

firebird-utils has an undeclared file conflict. This may result in an
unpack error from dpkg.

The files
 * /usr/bin/fb_lock_print
 * /usr/bin/fbtracemgr
 * /usr/sbin/fbguard
 * /usr/sbin/firebird
are contained in the packages
 * firebird-utils/4.0.4.3010.ds6-4 as present in experimental
 * firebird3.0-server/3.0.11.33703.ds4-4 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

Bug#1068961: llvm-toolchain-18: block migration to testing: to many llvm-toolchain versions in testing

[Drew Parsons]

If possible, it would be sensible in principle for debian to drop
llvm-toolchain-15 and llvm-toolchain-16.
i.e. only keep llvm-toolchain-14 (for llvmlite/numba)
and the latest llvm-toolchain


It belatedly occurs to me that it could be dangerous to drop the interim 
versions of llvm, since at some point llvmlite will upgrade its llvm 
support, and won't necessarily jump directly to the most recent llvm.


The latest llvmlite (released two weeks ago) now builds against 
llvm-toolchain-15,

https://llvmlite.readthedocs.io/en/latest/release-notes.html

More discussion on the Debian Science mailing list at
https://lists.debian.org/debian-science/2024/06/msg00024.html

Bug#1073145: marked as done (rust-bcrypt: unsatisfiable dependency librust-getrandom-0.2+js-dev)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 08:43:56 +
with message-id 
and subject line Bug#1073145: fixed in rust-bcrypt 0.15.1-2
has caused the Debian Bug report #1073145,
regarding rust-bcrypt: unsatisfiable dependency librust-getrandom-0.2+js-dev
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.)


-- 
1073145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-bcrypt
Version: 0.15.1-1
Severity: serious
Control: affects -1 src:rust-getrandom
X-Debbugs-CC: b...@debian.org

librust-bcrypt-dev is uninstallable because it has Depends:
librust-getrandom-0.2+js-dev

While rust-getrandom 0.2 is packaged in Debian,
librust-getrandom-0.2+js-dev is not.

This issue is preventing rust-bcrypt from reaching Testing.

https://tracker.debian.org/pkg/rust-bcrypt
https://release.debian.org/transitions/html/rust.html
https://piuparts.debian.org/sid/state-dependency-does-not-exist.html#librust-bcrypt-dev

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: rust-bcrypt
Source-Version: 0.15.1-2
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated rust-bcrypt 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: Wed, 26 Jun 2024 09:41:20 +0200
Source: rust-bcrypt
Architecture: source
Version: 0.15.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Bastian Germann 
Closes: 1073145
Changes:
 rust-bcrypt (0.15.1-2) unstable; urgency=medium
 .
   * Package bcrypt 0.15.1 from crates.io using debcargo 2.6.1
   * Disable getrandom feature js. Closes: #1073145
Checksums-Sha1:
 f467ecd70bf53b9d2528e63b675a1a8ff27eb6ac 2347 rust-bcrypt_0.15.1-2.dsc
 46893728c7dd3327ecad18796082d83835662d11 3024 
rust-bcrypt_0.15.1-2.debian.tar.xz
 15cc34287b3046554b690f85e2780dbf2c4b81de 6747 
rust-bcrypt_0.15.1-2_source.buildinfo
Checksums-Sha256:
 93286430bc17b93601e0dc36b46fe277b8af0d6ef626c3aed80f6d70e0946715 2347 
rust-bcrypt_0.15.1-2.dsc
 7a9e3608fd5aecfc1a65be2acef48feef0044a05a3448c62556f25ce2c87805b 3024 
rust-bcrypt_0.15.1-2.debian.tar.xz
 d604907f9a2ecd320ff266d54a74e7d0eb937f13f2a6106dd5f0cb173c49e551 6747 
rust-bcrypt_0.15.1-2_source.buildinfo
Files:
 3de97970b7d4f444e6329e1486d90ba9 2347 rust optional rust-bcrypt_0.15.1-2.dsc
 617c985a029bf78efc923005c221052c 3024 rust optional 
rust-bcrypt_0.15.1-2.debian.tar.xz
 428a07a508f249ac2796b6bbe3c04d8e 6747 rust optional 
rust-bcrypt_0.15.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmZ7xqUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFGuzC/0VIFJxaVJqZSJxEHhesXJeP5FinAi7DBf7
cDr5/6R+xX8CISE/SKQTo2TicBsVoJcqdnLmfgt+dutdzPHLZrVQOLqVnwoXtG7C
7yvzsppAGTh5YOJiE4iqcKhMZ7Gb47EQhl66JuBODaZM8TfTpE1/ATfkwow9n2yy
fEgETM64wLbNcoq5kNNIYuGo8zox6gZbxAKj6Ggu9Kanvt4wb/t4NjGlmuORoncL
y029PZ/Yx53WuVle3Occ5d7tcSbx6eZA9PPtbuP7nOk1nrKgOfLNXxd1EgnW6kp3
Y6t/omE0LEvuJyROLsSCzAa3aNSgePTD0rM+cRKzkOiCu9cDo9m4z+scH7hoMq1S
JoWveE3Uw9VKJZd2frF4NbrJOYjE1qlph+EEuWcB1PTNP3KFcy08hU9o5+qE/t07
yMFgtotXNb1+Sx6OXpq/QQotdgGRNNMyvp0FICMFUY/j8PK8pVOPlENZQc1XUfu4
k0CmqtbpVJQsiq0o+S7GVgszCKZf+0I=
=MNC+
-END PGP SIGNATURE-



pgp9FwE6dff9Q.pgp
Description: PGP signature
--- End Message ---

Processed: bug 1073077 is forwarded to https://bugs.kde.org/show_bug.cgi?id=478987

[Debian Bug Tracking System]

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

> forwarded 1073077 https://bugs.kde.org/show_bug.cgi?id=478987
Bug #1073077 {Done: Pino Toscano } [src:krita] krita: Fails to 
build with jpeg-xl 0.9
Changed Bug forwarded-to-address to 
'https://bugs.kde.org/show_bug.cgi?id=478987' from 
'https://salsa.debian.org/qt-kde-team/extras/krita/-/merge_requests/3'.
> thanks
Stopping processing here.

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

Bug#1069871: marked as done (netplan.io: flaky autopkgtest: eth42 interface already exists)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 08:39:42 +
with message-id 
and subject line Bug#1069871: fixed in netplan.io 1.0-6
has caused the Debian Bug report #1069871,
regarding netplan.io: flaky autopkgtest: eth42 interface already exists
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.)


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

Source: netplan.io
Version: 0.107.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails on s390x (and maybe on armel/armhf, but that's 
hard to tell because of the time_t fall-out).


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

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

Paul

e.g.
https://ci.debian.net/packages/n/netplan.io/testing/s390x/45071647/

272s ==
272s ERROR: test_rename_interfaces 
(__main__.TestNetworkd.test_rename_interfaces)

272s --
272s Traceback (most recent call last):
272s   File 
"/tmp/autopkgtest-lxc.ndthudlr/downtmp/build.hjS/src/tests/integration/base.py", 
line 177, in setUp

272s self.create_devices()
272s   File 
"/tmp/autopkgtest-lxc.ndthudlr/downtmp/build.hjS/src/tests/integration/base.py", 
line 120, in create_devices

272s raise SystemError('eth42 interface already exists')
272s SystemError: eth42 interface already exists


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: netplan.io
Source-Version: 1.0-6
Done: Lukas Märdian 

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

Debian distribution maintenance software
pp.
Lukas Märdian  (supplier of updated netplan.io 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: Wed, 26 Jun 2024 10:01:15 +0200
Source: netplan.io
Built-For-Profiles: noudeb
Architecture: source
Version: 1.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Netplan Maintainers 
Changed-By: Lukas Märdian 
Closes: 1069871
Changes:
 netplan.io (1.0-6) unstable; urgency=medium
 .
   * More fixes for flaky 'ethernets' autopkgtest (Closes: #1069871)
 .
 netplan.io (1.0-5) unstable; urgency=medium
 .
   * d/p/0004: Improve 'ethernets' autopkgtest flakyness (Closes: #1069871)
   * Declare compatibility with Standards-Version 4.7.0
 .
 netplan.io (1.0-4) unstable; urgency=medium
 .
   * d/p/0002: Add 'Forwarded:' patch header
   * d/p/0004: Try to improve autopkgtest flakyness (C:1069871)
Checksums-Sha1:
 6ad77c3ca82c2f3798ad0675633e62aad6779d04 2998 netplan.io_1.0-6.dsc
 fde5a0e89a8deffaee38a22c39cdbad96d73be11 19448 netplan.io_1.0-6.debian.tar.xz
 be8d7a74dc979149dc3696d76cd8d230b0ded7cb 12187 
netplan.io_1.0-6_source.buildinfo
Checksums-Sha256:
 542b56070be0f89a153e242070ca16c9e1d71273e4bd44c28bc36375e76b42e6 2998 
netplan.io_1.0-6.dsc
 60beeac1abab7d2d9fc90ca789c6d7b1f304fbfc1188217f6c35f26cb992a207 19448 
netplan.io_1.0-6.debian.tar.xz
 84b6387fc3691098194338f5c40325b70b7cc90f372acfc41236875f7100a11b 12187 
netplan.io_1.0-6_source.buildinfo
Files:
 a680417f1674806491c868388a6d3628 2998 net optional netplan.io_1.0-6.dsc
 1ed43a4cd414d7aaae2661a4f46dcc20 19448 net optional 
netplan.io_1.0-6.debian.tar.xz
 bcf0898f20e46b4feecd0fc1b610f89d 12187 net optional 
netplan.io_1.0-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE496GmCL5m2y8NfJ5v322IrMDrIsFAmZ7ztwACgkQv322IrMD
rIvZvQ//aH9E/kxZmSzenRGA+r9dsM+Xe7ZDvWjUFkEhEZwH9giujX7TGOqhhIUo
DkKMr8GTA/oi924grFbUa2LsExChqtjHs6MSKou4/WI/s9S+JG9cEJBtFJwY97EW

Processed: closing 1073077

[Debian Bug Tracking System]

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

> close 1073077
Bug #1073077 [src:krita] krita: Fails to build with jpeg-xl 0.9
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1073374: getfem: FTBFS: ImportError: cannot import name 'rand' from 'scipy' (/usr/lib/python3/dist-packages/scipy/__init__.py)

[Bo YU]

Hi,

On Sun, Jun 16, 2024 at 03:02:37PM +0200, Lucas Nussbaum wrote:

Source: getfem
Version: 5.4.2+dfsg1-3.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie


I have sent one RFS to debian science mail list:
https://lists.debian.org/debian-science/2024/06/msg00023.html

This should fix the issue.

BR,
Bo


signature.asc
Description: PGP signature

Bug#1074290: marked as done (rustfmt: error while loading shared libraries: librustc_driver-c7caf62295e72a17.so: cannot open shared object file: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jun 2024 07:15:43 +
with message-id 
and subject line Bug#1074290: fixed in rustc 1.79.0+dfsg1-1
has caused the Debian Bug report #1074290,
regarding rustfmt: error while loading shared libraries: 
librustc_driver-c7caf62295e72a17.so: cannot open shared object file: No such 
file or directory
to be marked as done.

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

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


-- 
1074290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rustfmt
Version: 1.78.0+dfsg1-2
Severity: serious
Control: found -1 1.79.0+dfsg1-1~exp1
User: debian...@lists.debian.org
Usertags: undefined-symbol adequate

rustfmt is missing a dependency on libstd-rust-1.78 and it does not
run if that is not installed. I get a symbol error in a minimal chroot
and piuparts/adequate detect the issue too, but do not fail the test:

https://piuparts.debian.org/sid/pass/rustfmt_1.78.0+dfsg1-2.log

   $ sudo apt install rustfmt
   Installing: 
 rustfmt
   
   Recommended packages:
 cargo
   
   Summary:
 Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 0
 Download size: 0 B / 2032 kB
 Space needed: 7746 kB / 32.6 GB available
   
   Selecting previously unselected package rustfmt.
   (Reading database ... 14772 files and directories currently installed.)
   Preparing to unpack .../rustfmt_1.78.0+dfsg1-2_amd64.deb ...
   Unpacking rustfmt (1.78.0+dfsg1-2) ...
   Setting up rustfmt (1.78.0+dfsg1-2) ...
   
   $ rustfmt --version
   rustfmt: error while loading shared libraries: 
librustc_driver-c7caf62295e72a17.so: cannot open shared object file: No such 
file or directory
   
   $ sudo apt install libstd-rust-1.78
   Installing: 
 libstd-rust-1.78
   
   Installing dependencies:
 libedit2  libicu72  libllvm17t64  libxml2  libz3-4
   
   Summary:
 Upgrading: 0, Installing: 6, Removing: 0, Not Upgrading: 0
 Download size: 0 B / 60.5 MB
 Space needed: 271 MB / 32.5 GB available
   
   Continue? [Y/n] 
   Selecting previously unselected package libedit2:amd64.
   (Reading database ... 16679 files and directories currently installed.)
   Preparing to unpack .../0-libedit2_3.1-20240517-1_amd64.deb ...
   Unpacking libedit2:amd64 (3.1-20240517-1) ...
   Selecting previously unselected package libicu72:amd64.
   Preparing to unpack .../1-libicu72_72.1-4+b1_amd64.deb ...
   Unpacking libicu72:amd64 (72.1-4+b1) ...
   Selecting previously unselected package libxml2:amd64.
   Preparing to unpack .../2-libxml2_2.12.7+dfsg-3_amd64.deb ...
   Unpacking libxml2:amd64 (2.12.7+dfsg-3) ...
   Selecting previously unselected package libz3-4:amd64.
   Preparing to unpack .../3-libz3-4_4.8.12-3.1+b2_amd64.deb ...
   Unpacking libz3-4:amd64 (4.8.12-3.1+b2) ...
   Selecting previously unselected package libllvm17t64:amd64.
   Preparing to unpack .../4-libllvm17t64_1%3a17.0.6-12_amd64.deb ...
   Unpacking libllvm17t64:amd64 (1:17.0.6-12) ...
   Selecting previously unselected package libstd-rust-1.78:amd64.
   Preparing to unpack .../5-libstd-rust-1.78_1.78.0+dfsg1-2_amd64.deb ...
   Unpacking libstd-rust-1.78:amd64 (1.78.0+dfsg1-2) ...
   Setting up libicu72:amd64 (72.1-4+b1) ...
   Setting up libedit2:amd64 (3.1-20240517-1) ...
   Setting up libz3-4:amd64 (4.8.12-3.1+b2) ...
   Setting up libxml2:amd64 (2.12.7+dfsg-3) ...
   Setting up libllvm17t64:amd64 (1:17.0.6-12) ...
   Setting up libstd-rust-1.78:amd64 (1.78.0+dfsg1-2) ...
   Processing triggers for libc-bin (2.38-13) ...
   
   $ rustfmt --version
   rustfmt 1.7.0-stable ( )
   
-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.8.12-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages rustfmt depends on:
ii  libc6  2.38-13
ii  libgcc-s1  14.1.0-2

Versions of packages rustfmt recommends:
pn  cargo  

rustfmt suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: rustc
Source-Version: 1.79.0+dfsg1-1
Done: Fabian Grünbichler 

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

A summary of the changes between this version and the previous