Bug#1029329: closing 1029329

[Salvatore Bonaccorso]

close 1029329 2.9.7-1
thanks

Processed: closing 1029329

[Debian Bug Tracking System]

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

> close 1029329 2.9.7-1
Bug #1029329 [src:modsecurity-apache] src:modsecurity-apache: CVE-2023-24021 In 
ModSecurity before 2.9.7, FILES_TMP_CONTENT sometimes lacked the complete 
content.
Marked as fixed in versions modsecurity-apache/2.9.7-1.
Bug #1029329 [src:modsecurity-apache] src:modsecurity-apache: CVE-2023-24021 In 
ModSecurity before 2.9.7, FILES_TMP_CONTENT sometimes lacked the complete 
content.
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> found 1029534 2:7.4.4-4
Bug #1029534 [libreoffice-common] libreoffice-common: breaks libreoffice-core 
from the same version
There is no source info for the package 'libreoffice-common' at version 
'2:7.4.4-4' with architecture ''
Unable to make a source version for version '2:7.4.4-4'
Marked as found in versions 2:7.4.4-4.
> found 1029534 2:7.5.0~rc2-4
Bug #1029534 [libreoffice-common] libreoffice-common: breaks libreoffice-core 
from the same version
Marked as found in versions libreoffice/2:7.5.0~rc2-4.
> --
Stopping processing here.

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

Bug#1029534: libreoffice-common: breaks libreoffice-core from the same version

[Rene Engelhard]

Hi,

Am 23.01.23 um 23:04 schrieb Sven Joachim:

The Breaks in libreoffice-common need to be adjusted for the recent
epoch bumps.  Among others, libreoffice-common Breaks
libreoffice-core (>= 1:7.5~), making libreoffice-core 4:7.4.4-7
not installable.

Yeah, that one I noticed yesterday already.

Good luck figuring out what other relationships need to be changed, and
take your time.


Thanks :) Just doing a build and we will see... :)


Regards,


Rene

Bug#1029481: fixed with version 3.1.0-2

[Paul Wise]

On Mon, 2023-01-23 at 11:21 +0100, Christoph Martin wrote:

> The other lines reported with
> 
> dgrep -A5 'auto-generated' debmake
> 
> are false-positives since they are files from the debmake package and
> not from yq.

That was just an illustration of where the yq package description that
was containing "auto-generated" was copied from, not a demonstration of
the problematic parts of the yq package, which was the first command.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1028986: marked as done (Multiple integer overflow and buffer overflow issues in game loading)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2023 04:23:17 +
with message-id 
and subject line Bug#1028986: fixed in sgt-puzzles 20230122.806ae71-1
has caused the Debian Bug report #1028986,
regarding Multiple integer overflow and buffer overflow issues in game loading
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.)


-- 
1028986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sgt-puzzles
Version: 20220801.89391ba-1
Severity: serious
Tags: security
X-Debbugs-Cc: Debian Security Team 

Ben Harris found multiple issues in sgt-puzzles where a malformed game
description or save file can lead to integer overflow or buffer
overflow.  These were fixed upstream today, and I'll upload the
changes to unstable shortly.

The Debian package doesn't register any media type handler for save
files, so I think this can only be exploited by social-engineering a
user into loading such a file or description.

Ben.

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

Kernel: Linux 6.0.0-6-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 sgt-puzzles depends on:
ii  libc62.36-6
ii  libcairo21.16.0-7
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1
ii  libglib2.0-0 2.74.3-1
ii  libgtk-3-0   3.24.35-3
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1

Versions of packages sgt-puzzles recommends:
ii  chromium [www-browser]  108.0.5359.124-1
ii  firefox [www-browser]   108.0-2
ii  lynx [www-browser]  2.9.0dev.10-1+b1
ii  xdg-utils   1.1.3-4.1

sgt-puzzles suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: sgt-puzzles
Source-Version: 20230122.806ae71-1
Done: Ben Hutchings 

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated sgt-puzzles 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: Tue, 24 Jan 2023 03:09:26 +0100
Source: sgt-puzzles
Architecture: source
Version: 20230122.806ae71-1
Distribution: unstable
Urgency: medium
Maintainer: Ben Hutchings 
Changed-By: Ben Hutchings 
Closes: 887982 1018235 1028986
Changes:
 sgt-puzzles (20230122.806ae71-1) unstable; urgency=medium
 .
   * New upstream version:
 - Multiple fixes for integer overflow and buffer overflow issues in game
   loading (Closes: #1028986)
   * Install 96x96 application icons (Closes: #887982)
   * Use po4a-updatepo instead of po4a-gettextize
   * Update German translation.
 Thanks to Helge Kreutzmann (Closes: #1018235)
Checksums-Sha1:
 496cab5514610def4f674ef6727fb87d11ff3b3b 2044 
sgt-puzzles_20230122.806ae71-1.dsc
 ef06980e22fc2451ed0bb41229f8c4433595c44b 855568 
sgt-puzzles_20230122.806ae71.orig.tar.xz
 d224aa5af7e0e33afcd54a6072438c55c37a9034 99720 
sgt-puzzles_20230122.806ae71-1.debian.tar.xz
 2128c2374268487fa9442b58ded091d9c036d329 15203 
sgt-puzzles_20230122.806ae71-1_amd64.buildinfo
Checksums-Sha256:
 42bb06da4a26fa4f24ef6589c041ffb3c390cf18005b742c88d998b2ea0c1076 2044 
sgt-puzzles_20230122.806ae71-1.dsc
 6e236301b0ef756b9f421c8cdb50edc5510a6e5f6f7f1d3b8384dfd3d5204a99 855568 
sgt-puzzles_20230122.806ae71.orig.tar.xz
 e8b69cda40b0809753e72da15a562fcedb091f6178baf37bbe4109815dac8113 99720 
sgt-puzzles_20230122.806ae71-1.debian.tar.xz
 92b51591cd5eacc2fddad2161ad2ed0a14539f023c46e1b412977c7b67c16bbf 15203 
sgt-puzzles_20230122.806ae71-1_amd64.buildinfo
Files:
 297706194e6b8bc3cdee71ccbd2b7578 2044 games optional 
sgt-puzzles_20230122.806ae71-1.dsc
 27245fbbbafea8da85ea94b2035a34c8 855568 games opti

Bug#1004940: marked as done (gr-iio seems to be integrated into gnuradio now)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2023 03:47:00 +
with message-id 
and subject line Bug#1029540: Removed package(s) from unstable
has caused the Debian Bug report #1004940,
regarding gr-iio seems to be integrated into gnuradio now
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.)


-- 
1004940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gr-iio
Version: 0.3-9
Severity: serious
Tags: bookworm sid

https://www.gnuradio.org/news/2022-01-17-gnuradio-v3.10.0.0-release/

- New in-tree module gr-iio
--- End Message ---
--- Begin Message ---
Version: 0.3-9+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Paul Richards Tagliamonte (the ftpmaster behind the curtain)--- End Message ---

Bug#1002119: marked as done (gr-fcdproplus: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create')

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2023 03:47:33 +
with message-id 
and subject line Bug#1029539: Removed package(s) from unstable
has caused the Debian Bug report #1002119,
regarding gr-fcdproplus: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to 
`pthread_create'
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.)


-- 
1002119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gr-fcdproplus
Version: 3.8~20190817-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/cmTC_d6505.dir/src.c.o: in function `main':
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to 
> `pthread_create'
> /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12: undefined 
> reference to `pthread_detach'
> /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13: undefined 
> reference to `pthread_cancel'
> /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:14: undefined 
> reference to `pthread_join'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/gr-fcdproplus_3.8~20190817-3_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 3.8~20190817-3+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Paul Richards Tagliamonte (the ftpmaster behind the curtain)--- End Message ---

Bug#1002091: marked as done (gr-iio: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create')

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2023 03:47:00 +
with message-id 
and subject line Bug#1029540: Removed package(s) from unstable
has caused the Debian Bug report #1002091,
regarding gr-iio: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: 
undefined reference to `pthread_create'
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.)


-- 
1002091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gr-iio
Version: 0.3-9
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/cmTC_c5a48.dir/src.c.o: in function `main':
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to 
> `pthread_create'
> /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12: undefined 
> reference to `pthread_detach'
> /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13: undefined 
> reference to `pthread_cancel'
> /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:14: undefined 
> reference to `pthread_join'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/gr-iio_0.3-9_unstable.log

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

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

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

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Paul Richards Tagliamonte (the ftpmaster behind the curtain)--- End Message ---

Bug#1029417: marked as done (gammu: FTBFS in bookworm (undeclared build-dependency on tzdata))

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2023 03:20:23 +
with message-id 
and subject line Bug#1029417: fixed in gammu 1.42.0-6
has caused the Debian Bug report #1029417,
regarding gammu: FTBFS in bookworm (undeclared build-dependency on tzdata)
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.)


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

Package: src:gammu
Version: 1.42.0-5
Severity: serious
Tags: ftbfs patch

Dear maintainer:

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


[...]
 debian/rules binary-arch
dh binary-arch --with sphinxdoc --buildsystem=cmake
   dh_update_autotools_config -a -O--buildsystem=cmake
   dh_autoreconf -a -O--buildsystem=cmake
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
-DINSTALL_LIBDATA_DIR=/usr/lib/x86_64-linux-gnu \
-DSYSTEMD_SERVICES_INSTALL_DIR=/usr/lib/systemd/system \
-DINSTALL_LSB_INIT=ON \
-DSYSTEMD_FOUND=ON \
-DWITH_SYSTEMD=ON
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON 
-DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix 
Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DINSTALL_LIBDATA_DIR=/usr/lib/x86_64-linux-gnu 
-DSYSTEMD_SERVICES_INSTALL_DIR=/usr/lib/systemd/system -DINSTALL_LSB_INIT=ON -DSYSTEMD_FOUND=ON 
-DWITH_SYSTEMD=ON ..

[...]

test 468
Start 468: test_sql_time

468: Test command: 
/<>/obj-x86_64-linux-gnu/tests/atgen/test_sql_time
468: Working Directory: /<>/obj-x86_64-linux-gnu/tests/atgen
468: Test timeout computed to be: 1500
468: Test "tm.tm_hour == 13" failed!
468: test_fill_time_t_gmt
468: test_fill_time_t_dst
468/880 Test #468: test_sql_time 
...***Failed
0.01 sec
Test "tm.tm_hour == 13" failed!
test_fill_time_t_gmt
test_fill_time_t_dst

[...]

The following tests FAILED:
468 - test_sql_time (Failed)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=--verbose 
ARGS\+=-j1 returned exit code 2
make[1]: *** [debian/rules:21: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:12: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

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 ---
Source: gammu
Source-Version: 1.42.0-6
Done: Boian Bonev 

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

Debian distribution maintenance software
pp.
Boian Bonev  (supplier of updated gammu 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: Tue, 24 Jan 2023 00:44:14 +
Source: gam

Bug#1027943: regina-normal FTBFS with Python 3.11 as default version

[Simon Quigley]

Hi Benjamin, thanks for responding so quickly.

I will cancel the upload in Debian, but it's worth noting that I did upload this to Ubuntu already. (Your version will 
automatically sync over once you upload it.)


Best wishes,
--
Simon Quigley
si...@tsimonq2.net
tsimonq2 on LiberaChat and OFTC
@tsimonq2:linuxdelta.com on Matrix
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1028830: marked as done (python-hypothesis: FTBFS: InputError: [Errno 2] No such file or directory: 'hypothesis-python/RELEASE.rst'.)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2023 00:17:36 +
with message-id 
and subject line Bug#1028830: fixed in python-hypothesis 6.64.0-1
has caused the Debian Bug report #1028830,
regarding python-hypothesis: FTBFS: InputError: [Errno 2] No such file or 
directory: 'hypothesis-python/RELEASE.rst'.
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=hypothesis-python/src \
> http_proxy='127.0.0.1:9' \
> https_proxy='127.0.0.1:9' \
> python3 -m sphinx -N -b html hypothesis-python/docs/ 
> /<>/.pybuild/docs/html/
> Running Sphinx v5.3.0
> making output directory... done
> /<>/hypothesis-python/src/hypothesis/extra/array_api.py:925: 
> HypothesisWarning: Could not determine whether module mock is an Array API 
> library
>   warn(
> loading intersphinx inventory from https://docs.python.org/3/objects.inv...
> loading intersphinx inventory from https://numpy.org/doc/stable/objects.inv...
> loading intersphinx inventory from 
> https://pandas.pydata.org/pandas-docs/stable/objects.inv...
> loading intersphinx inventory from 
> https://docs.pytest.org/en/stable/objects.inv...
> loading intersphinx inventory from 
> https://django.readthedocs.io/en/stable/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable 
> due to : 
> HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded 
> with url: /3/objects.inv (Caused by ProxyError('Cannot connect to proxy.', 
> NewConnectionError(' 0x7f0d19e951d0>: Failed to establish a new connection: [Errno 111] Connection 
> refused')))
> loading intersphinx inventory from 
> https://dateutil.readthedocs.io/en/stable/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://dateutil.readthedocs.io/en/stable/objects.inv' 
> not fetchable due to : 
> HTTPSConnectionPool(host='dateutil.readthedocs.io', port=443): Max retries 
> exceeded with url: /en/stable/objects.inv (Caused by ProxyError('Cannot 
> connect to proxy.', NewConnectionError(' object at 0x7f0d19e9cfd0>: Failed to establish a new connection: [Errno 111] 
> Connection refused')))
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://numpy.org/doc/stable/objects.inv' not 
> fetchable due to : 
> HTTPSConnectionPool(host='numpy.org', port=443): Max retries exceeded with 
> url: /doc/stable/objects.inv (Caused by ProxyError('Cannot connect to 
> proxy.', NewConnectionError(' 0x7f0d19e9d350>: Failed to establish a new connection: [Errno 111] Connection 
> refused')))
> loading intersphinx inventory from 
> https://redis-py.readthedocs.io/en/stable/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://django.readthedocs.io/en/stable/objects.inv' 
> not fetchable due to : 
> HTTPSConnectionPool(host='django.readthedocs.io', port=443): Max retries 
> exceeded with url: /en/stable/objects.inv (Caused by ProxyError('Cannot 
> connect to proxy.', NewConnectionError(' object at 0x7f0d19e96f50>: Failed to establish a new connection: [Errno 111] 
> Connection refused')))
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 
> 'https://pandas.pydata.org/pandas-docs/stable/objects.inv' not fetchable due 
> to : 
> HTTPSConnectionPool(host='pandas.pydata.org', port=443): Max retries exceeded 
> with url: /pandas-docs/stable/objects.inv (Caused by ProxyError('Cannot 
> connect to proxy.', NewConnectionError(' object at 0x7f0d19e9fc90>: Failed to establish a new connection: [Errno 111] 
> Connection refused')))
> loading intersphinx inventory from 
> https://www.attrs.org/en/stable/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://redis-py.readthedocs.io/en/stable/objects.inv' 
> not fetchable due to : 
> HTTPSConnectionPool(host='redis-py.readthedocs.io', port=443): Max retries 
> exceeded with url: /en/stable/objects.inv (Caused

Bug#1029255: marked as done (rbac-client-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.eclipse.jetty:jetty-jmx:jar:debian has not been download

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2023 00:18:13 +
with message-id 
and subject line Bug#1029255: fixed in rbac-client-clojure 1.1.4-1
has caused the Debian Bug report #1029255,
regarding rbac-client-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
org.eclipse.jetty:jetty-jmx:jar:debian has not been downloaded from it before.
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.)


-- 
1029255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rbac-client-clojure
Version: 0.9.4-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230120 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> lein pom debian/pom.xml
> Wrote /<>/debian/pom.xml
> lein i18n make
> Running 'make i18n'
> lein jar
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.clojure:tools.namespace:jar:debian has not been downloaded 
> from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.clojure:tools.namespace:jar:debian has not been downloaded from 
> it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact compojure:compojure:jar:debian has not been downloaded from it 
> before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact compojure:compojure:jar:debian has not been downloaded from it 
> before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-server:jar:debian has not been 
> downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-server:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-servlet:jar:debian has not been 
> downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-servlet:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-servlets:jar:debian has not been 
> downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-servlets:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-webapp:jar:debian has not been 
> downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-webapp:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-proxy:jar:debian has not been downloaded 
> from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-proxy:jar:debian has not been downloaded 
> from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.eclipse.jetty:jetty-jmx:jar:debian has not been downloaded 
> from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.eclipse.jetty:jetty-jmx:jar:debian has not been downloaded from 
> it before.
> This could be due to a typo in :dependencies, file system permissions, or 
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/01/20/rbac-client-clojure_0.9.4-2_unstable.log

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

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.o

Bug#1019790: marked as done (eviacam: Please transition to wxwidgets3.2)

[Debian Bug Tracking System]

Your message dated Tue, 24 Jan 2023 00:05:37 +
with message-id 
and subject line Bug#1019790: fixed in eviacam 2.1.4-2.1
has caused the Debian Bug report #1019790,
regarding eviacam: Please transition to wxwidgets3.2
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.)


-- 
1019790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eviacam
Severity: normal
Control: block 1019416 by -1

Hi,

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

wxWidgets 3.2 (a new API/ABI stable release) has been released a few
months ago and is now packaged in unstable as wxwidgets3.2. Upstream
has stopped supporting wxWidgets 3.0, so the Debian wx team would
like to migrate all wx package users to wxwidgets3.2 for bullseye,
with the plan to remove wxwidgets3.0 before release.

For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).

Thanks, Scott 
--- End Message ---
--- Begin Message ---
Source: eviacam
Source-Version: 2.1.4-2.1
Done: Olly Betts 

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

Debian distribution maintenance software
pp.
Olly Betts  (supplier of updated eviacam 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, 09 Nov 2022 10:14:08 +1300
Source: eviacam
Architecture: source
Version: 2.1.4-2.1
Distribution: unstable
Urgency: medium
Maintainer: Cesar Mauri 
Changed-By: Olly Betts 
Closes: 1019790
Changes:
 eviacam (2.1.4-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Update to build with wxwidgets-3.2 (new patch
 wx3.2-compat.patch) (Closes: #1019790)
Checksums-Sha1:
 649caaa756a2f0b3d7aa3f68bd1270957882406f 1659 eviacam_2.1.4-2.1.dsc
 9fd9c41a3d5c25f5d1ce03ff4c38ae61957dc35e 14756 eviacam_2.1.4-2.1.debian.tar.xz
 2e56c7dbab048091c3716250700d2463df4cf7f5 21384 
eviacam_2.1.4-2.1_source.buildinfo
Checksums-Sha256:
 0ea5aac977243645c44f2ae7b7c3c37df0171e501f78dfcec325459407d26be2 1659 
eviacam_2.1.4-2.1.dsc
 d154528db9a07d85159dcb63fedc9f8309ceb4585ff65b165520e806b9660e92 14756 
eviacam_2.1.4-2.1.debian.tar.xz
 ce0e5552b10c210d9af00dea6573aad35c22503c47db2bc1bca61ceab2c5391c 21384 
eviacam_2.1.4-2.1_source.buildinfo
Files:
 bea78e0ec37b7bc8b547a51fc9b93f08 1659 x11 optional eviacam_2.1.4-2.1.dsc
 f663fca5fa4d0205e4ef60088900334b 14756 x11 optional 
eviacam_2.1.4-2.1.debian.tar.xz
 633ae3f49efb348c1a541969047dddfb 21384 x11 optional 
eviacam_2.1.4-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmPB43YQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFPGIDADrRye6kMS9SVDknwBk6nvQ4DNvy5KJsP/V
A0TpNwps12U3Kce+dDzcb4DG52oxuvW/895WillxmuQDGW9M5RQ/+omc+xFHH44U
sDWK77TLGbtKHs5jBgHXEjYinRiKBMNXsBd7JToY8Ry9ywqwOV81q0t3Rdq2Inht
P1Hx3PI5iXo5oj+8QS2JfSHQMQgcxsUC5PXN13aGFLAZLr74GmC7hQ5NiZ71QB+e
cHi5xlhjElmoWIdvHn4CyB5knFZhFUZZ4l7aRT5oXtgk9MkVcHBP5brg8NjR331v
ALOPGotWEq9tkB598sF0onFPl9VCNUFd5a4ZTtIgxTJC0arIztkYLVueSPuG/qSh
ftQZGttAbCwP2LKZdbq/SO9ZS/RqFWTe5mcWFuqptCaS2aD0tYXrCKBGjLw8ML+p
nm8zB7TIow5bw1HsVYs2wuoDoMMY1z3vjLZ6tA6F6X/9dAciQ6chVSDhazTGp/XQ
cg33yDIdSXdQbu41BA8acS1PotSSpjI=
=b/Hh
-END PGP SIGNATURE End Message ---

Bug#1028946: php-horde-support: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

[Mike Gabriel]

Control: close -1
Control: fixed -1 2.2.2-2

On  So 15 Jan 2023 07:27:03 CET, Paul Gevers wrote:


Source: php-horde-support
Version: 2.2.2-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a  
recent upload of php-defaults the autopkgtest of php-horde-support  
fails in testing when that autopkgtest is run with the binary  
packages of php-defaults from unstable. It passes when run with only  
packages from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-support  from testing2.2.2-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of php-defaults  
to testing [1]. https://www.php.net/ChangeLog-8.php lists the  
changes since 7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of  
deprecation warnings on stderr. Output on stderr makes autopkgtest  
fail by default, unless `allow-stderr` is added to the set of  
restrictions. As a flood of deprecation warnings in server logs may  
be very unwanted, I'm not saying that adding the restriction to  
autopkgtest is the right answer to this issue, but because of the  
php transition, it needs to be resolved one way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-support/30356868/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration:  
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/test/Horde/Support/phpunit.xml


PHP  
Deprecated: Creation of dynamic property  
Horde_Support_Inflector::$_uncountables_keys is deprecated in  
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/lib/Horde/Support/Inflector.php on line  
128
PHP Deprecated:  Creation of dynamic property  
Horde_Support_InflectorTest::$inflector is deprecated in  
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/test/Horde/Support/InflectorTest.php on line  
42
.PHP Deprecated:  Creation of dynamic property  
Horde_Support_Inflector::$_uncountables_keys is deprecated in  
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/lib/Horde/Support/Inflector.php on line  
128
PHP Deprecated:  Creation of dynamic property  
Horde_Support_InflectorTest::$inflector is deprecated in  
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/test/Horde/Support/InflectorTest.php on line  
42
.PHP Deprecated:  Creation of dynamic property  
Horde_Support_Inflector::$_uncountables_keys is deprecated in  
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/lib/Horde/Support/Inflector.php on line  
128
PHP Deprecated:  Creation of dynamic property  
Horde_Support_InflectorTest::$inflector is deprecated in  
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/test/Horde/Support/InflectorTest.php on line  
42
.PHP Deprecated:  Creation of dynamic property  
Horde_Support_Inflector::$_uncountables_keys is deprecated in  
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/lib/Horde/Support/Inflector.php on line  
128
PHP Deprecated:  Creation of dynamic property  
Horde_Support_InflectorTest::$inflector is deprecated in  
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/test/Horde/Support/InflectorTest.php on line  
42
IPHP Deprecated:  Creation of dynamic property  
Horde_Support_Inflector::$_uncountables_keys is deprecated in  
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/lib/Horde/Support/Inflector.php on line  
128
PHP Deprecated:  Creation of dynamic property  
Horde_Support_InflectorTest::$inflector is deprecated in  
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/test/Horde/Support/InflectorTest.php on line  
42
.PHP Deprecated:  Creation of dynamic property  
Horde_Support_Inflector::$_uncountables_keys is deprecated in  
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/lib/Horde/Support/Inflector.php on line  
128
PHP Deprecated:  Creation of dynamic property  
Horde_Support_InflectorTest::$inflector is deprecated in  
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/test/Horde/Support/InflectorTest.php on line  
42
PHP Deprecated:  Creation of dynamic property  
Horde_Support_Inflector::$_uncountables_keys is deprecated in  

Processed: Re: Bug#1028946: php-horde-support: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #1028946 [src:php-horde-support] php-horde-support: (autopkgtest) needs 
update for php8.2: deprecation warnings on stderr
Marked Bug as done
> fixed -1 2.2.2-2
Bug #1028946 {Done: Mike Gabriel } 
[src:php-horde-support] php-horde-support: (autopkgtest) needs update for 
php8.2: deprecation warnings on stderr
The source 'php-horde-support' and version '2.2.2-2' do not appear to match any 
binary packages
Marked as fixed in versions php-horde-support/2.2.2-2.

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

Bug#1029508: marked as done (pnc: missing Breaks+Replaces: pn)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 23:08:17 +
with message-id 
and subject line Bug#1029508: fixed in pnc 0.9.4-3
has caused the Debian Bug report #1029508,
regarding pnc: missing Breaks+Replaces: pn
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.)


-- 
1029508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pnc
Version: 0.9.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../archives/pnc_0.9.4-1_amd64.deb ...
  Unpacking pnc (0.9.4-1) ...
  dpkg: error processing archive /var/cache/apt/archives/pnc_0.9.4-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/gawk/gawkpn.so', which is 
also in package pn 0.9.0-1+b3
  Errors were encountered while processing:
   /var/cache/apt/archives/pnc_0.9.4-1_amd64.deb

Since pnc is taking over pn, the Breaks+Replaces can be unversioned.

Please also file a RM bug for src:pn


cheers,

Andreas


pn=0.9.0-1+b3_pnc=0.9.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pnc
Source-Version: 0.9.4-3
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated pnc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Jan 2023 23:46:28 +0100
Source: pnc
Architecture: source
Version: 0.9.4-3
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Jochen Sprickerhof 
Closes: 1029508
Changes:
 pnc (0.9.4-3) unstable; urgency=medium
 .
   * Add Breaks+Replaces: pn.
 Thanks to Andreas Beckmann (Closes: #1029508)
Checksums-Sha1:
 3d50ff3006bb79008e74fca09769d417029b6b1d 1988 pnc_0.9.4-3.dsc
 d52b088357cf2262e732ef5df7e4789155580fbb 2052 pnc_0.9.4-3.debian.tar.xz
 0472de10424c373d2b600c76f4e887f997e5bd1c 6742 pnc_0.9.4-3_source.buildinfo
Checksums-Sha256:
 6a771e66afb9dd99faea97125e804f05425be832bf4e17349863ac4837dcce13 1988 
pnc_0.9.4-3.dsc
 58c32d63a75f0409277c1065e45f0690bc3af7f21024d3d1c572298d37a3f17c 2052 
pnc_0.9.4-3.debian.tar.xz
 ccc403bfe1ca94d7e1ea713dd2a95fa17578b62ae561c9562c82a7c50e3a32c8 6742 
pnc_0.9.4-3_source.buildinfo
Files:
 dffdce3d535390e83ad7069eba649640 1988 x11 optional pnc_0.9.4-3.dsc
 c583e701eef5fee4fc252b92a45e266b 2052 x11 optional pnc_0.9.4-3.debian.tar.xz
 77b477303483843c756152dc12d7788b 6742 x11 optional pnc_0.9.4-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmPPDk8ACgkQW//cwljm
lDMnlRAAoqBRUXIyEBEYOi9ER++UgZx/Jx3a5hJd/zgdlOA7gLLCTkj/aaol+pfK
NoPp1zwD+UB1XrdOQq3PMcmR+5vlDZMAIdlpAkgD5L+Vv7B6v5ihX617+fsrcOqN
3MhRahYebhSVzPRDqqZgDG9fwap7rBCM4puYC7vAP0a/JsWFVcCNXpOqCyJlCBCp
dujZQ+8YZjBkOAToS/q04MNmF28ZA99QQI3bUXKqdu48o1qxlj9/+4igAHv6w21z
ua+7OKMApttuozQP27yoY9MK+IAjHP0wR7yyVskTU4C/f3/Cba+QWIJmqZgAq03S
1pDNygzBSxqkH6vUdHzW7u9mdNgZHvKtIDCknTKqmbHdMMV8S5c/UwgS2M73IT8t
TsO87K+rbh8YCsDJh9YoGIdPRkMiZx8gBLS8ZuorjRAVARw6m/csOO15aUi6VfSK
/0wT/kI05SK//6yS6J57+RkvUHqufOfyVL6lzo2mGT/8xjk+te6ykpk5/1Bi+N+w
gOLkuCFm+xxgKc/ew/uDPDXWMsSAR4nMJ32pHQitLHE9KS2r073nUHsxSsRoCHFT
7xgw6dJqyht8rc+h7FXN8a2CirxhXpd6TVFWCicx6vdwU96Js8q9ImOx3ihLAOEq
6EMOdCTfS9iLyyfdLIR4JyJ6FDfmSXXgOF/JqFEZqZIXFHUG4ik=
=w51e
-END PGP SIGNATURE End Message ---

Bug#1029178: marked as done (vtk-dicom: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 22:54:51 +
with message-id 
and subject line Bug#1029178: fixed in vtk-dicom 0.8.14-3.1
has caused the Debian Bug report #1029178,
regarding vtk-dicom: autopkgtest failure
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.)


-- 
1029178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vtk-dicom
Version: 0.8.14-3
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/v/vtk-dicom/30492694/log.gz

autopkgtest [23:14:01]: test autodep8-python3: set -e ; for py in $(py3versions 
-d 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c 
"import vtkdicom; print(vtkdicom)" ; done
autopkgtest [23:14:01]: test autodep8-python3: [---
Testing with python3.10:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/vtkdicom/__init__.py", line 1, in 

from .vtkDICOM import *
ModuleNotFoundError: No module named 'vtkdicom.vtkDICOM'

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: vtk-dicom
Source-Version: 0.8.14-3.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated vtk-dicom 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 21 Jan 2023 22:41:32 +0100
Source: vtk-dicom
Architecture: source
Version: 0.8.14-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sebastian Ramacher 
Closes: 1029178
Changes:
 vtk-dicom (0.8.14-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * debian/control: Use ${python3:Depends} (Closes: #1029178)
Checksums-Sha1:
 ebdfeddaf8bb463cf9606b3ee4a656879d9e305a 2289 vtk-dicom_0.8.14-3.1.dsc
 ef04c1883639a79a843a4297de02831c3b948ae1 6852 
vtk-dicom_0.8.14-3.1.debian.tar.xz
Checksums-Sha256:
 92391a9311d4f3e5dcb47e88f5cdb8fb5ce5d97bbe68b74f418778b98e69bbdb 2289 
vtk-dicom_0.8.14-3.1.dsc
 fa6a27d5aa43fd058145622a19de07ac4a0d15b5ae69eed431664bd005014f55 6852 
vtk-dicom_0.8.14-3.1.debian.tar.xz
Files:
 7f501f142de912f50ceed32c2bf3455b 2289 graphics optional 
vtk-dicom_0.8.14-3.1.dsc
 8f6412764f8244434be50f0e0890177c 6852 graphics optional 
vtk-dicom_0.8.14-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmPMXu0ACgkQafL8UW6n
GZPLkg//aB7NeSxArEk03WhraPl1BN091PZkbo10BxeuNokEkeDWXCOwLOLYgSe5
dMVUxIx5b5FcBqQ5oD2Qx5vDyQAlQEUILU3eOwupAoD9o4B4+zHJLTAm2J1AkHq/
gxo+dX2bFkUeXMMcyfp6KVhxsYfkgW/rrjMlJTseXWaIs0zEplJV3ULEmK0MEFFk
5KG4K3IuQWF3MAATi84lm/+sNXvp9vFrHvwOmpGl6kZhOEvWIWELsvZQLRQ1Hz8J
XYbz6J4pl6DJNBVKRWroQYcW75yYBq5dSiQDkzD6zTYLeJhERxgJKztRV3WtOIiq
V/6Ih9OSfIYP3vRcV9jIW7sINk1HZXTkZhuhfZZc0WuNYLL+X8RXyYOjuwMniTKa
Csq72gdLf1dOhaELVOx+k20l5Bays4LNElehFmI9sicEsWXzUNoGYTWSfDaDHU/I
ZB0ntMdo/FN5VpHTcxa+TH7a3NHX5T3TaCbaJZmkZ9gp+6ww9is1e3CDaxJzEJT3
pdYvG1O+6KUo2zd3iP1/kXj2cvm/WZ1/l1ZT1JqL8bhMvGvM4ZOi7Udr+8m3oGzE
DgUsLmt2x5Dxx1XMYcyGNnPN/VCKluNb3swpsQ7eR9iPWN+a+k7vm6z8SiZ70HBj
LJ3euF4fxAdVjfMHbvHyzNcUCrdkWXja0mKgusZ7UEAbA2dMc9k=
=jJbD
-END PGP SIGNATURE End Message ---

Bug#1028795: marked as done (trinity: FTBFS: net/proto-decnet.c:5:10: fatal error: linux/dn.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 22:54:24 +
with message-id 
and subject line Bug#1028795: fixed in trinity 1.9+git20230109.87f1530-1
has caused the Debian Bug report #1028795,
regarding trinity: FTBFS: net/proto-decnet.c:5:10: fatal error: linux/dn.h: 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.)


-- 
1028795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trinity
Version: 1.9+git20220923.e63e484-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wextra -I. -Iinclude/ -include 
> config.h -Wimplicit -D_GNU_SOURCE -D__linux__ -std=gnu11 -Wformat=2 
> -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef 
> -Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes 
> -Wmissing-prototypes -fsigned-char -Wno-missing-field-initializers 
> -Wlogical-op -Wstrict-aliasing=3 -o net/proto-decnet.o -c net/proto-decnet.c
> net/proto-decnet.c:5:10: fatal error: linux/dn.h: No such file or directory
> 5 | #include 
>   |  ^~~~
> compilation terminated.
> cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wextra -I. -Iinclude/ -include 
> config.h -Wimplicit -D_GNU_SOURCE -D__linux__ -std=gnu11 -Wformat=2 
> -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef 
> -Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes 
> -Wmissing-prototypes -fsigned-char -Wno-missing-field-initializers 
> -Wlogical-op -Wstrict-aliasing=3 -o net/proto-econet.o -c net/proto-econet.c
> make[2]: *** [Makefile:113: net/proto-decnet.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/trinity_1.9+git20220923.e63e484-1_unstable.log

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

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

If you reassign this bug to another package, please 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: trinity
Source-Version: 1.9+git20230109.87f1530-1
Done: gustavo panizzo 

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

Debian distribution maintenance software
pp.
gustavo panizzo  (supplier of updated trinity package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Jan 2023 22:08:07 +0100
Source: trinity
Architecture: source
Version: 1.9+git20230109.87f1530-1
Distribution: unstable
Urgency: medium
Maintainer: gustavo panizzo 
Changed-By: gustavo panizzo 
Closes: 1028795
Changes:
 trinity (1.9+git20230109.87f1530-1) unstable; urgency=medium
 .
   * Package an upstream snapshot (Closes: #1028795)
   * [1214da] Update copyright years
   * [398f7c] Bump standards version to 4.6.2, no changes were needed
Checksums-Sha1:
 b9b328b1a9ca3fd6163c64d7315f8d69008fd800 1425 
trinity_1.9+git20230109.87f1530-1.dsc
 88c0da1149e8e7f3ed983f46a6d5253f9e73bf0a 279011 
trinity_1.9+git20230109.87f1530.orig.tar.gz
 c86cf0e6fd65b261f0de2f1f0516c45bf36bf4e8 4968 
trinity_1.9+git20230109.87f1530-1.debian.tar.xz
 2ab991491f3c53a3e73d102fdb588f0863ac46c8 5725 
trinity_1.9+git2

Bug#1019790: eviacam: diff for NMU version 2.1.4-2.1

[Olly Betts]

On Sat, Jan 14, 2023 at 12:07:21AM +0100, Bastian Germann wrote:
> I have just tested the patch and uploaded it as-is as NMU to DELAYED/10.

Thanks for the testing.

I'm not super happy that you've uploaded an NMU that appears to have
been done by me though:

https://ftp-master.debian.org/deferred/eviacam_2.1.4-2.1_source.changes

I did provide a candidate patch, but I'm not able to provide follow up
support for your NMU because eviacam doesn't even start up with the
webcam I have access to.  All I can do is forward any follow up I get
about it to you, which just seems to be creating an unnecessary job for
me.

Cheers,
Olly

Bug#1028879: marked as done (moment-timezone.js: FTBFS: make[1]: *** [debian/rules:12: data/meta/2022f.json] Error 1)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 22:46:20 +
with message-id 
and subject line Bug#1028879: fixed in moment-timezone.js 0.5.40+dfsg-1+2022g
has caused the Debian Bug report #1028879,
regarding moment-timezone.js: FTBFS: make[1]: *** [debian/rules:12: 
data/meta/2022f.json] Error 1
to be marked as done.

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

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


-- 
1028879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: moment-timezone.js
Version: 0.5.38+dfsg-1+2022f
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link ./node_modules/moment -> /usr/share/nodejs/moment
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> # Fail the build if the tzdata package does not match TZVER.
> grep -q '^# version 2022f$' /usr/share/zoneinfo/tzdata.zi
> make[1]: *** [debian/rules:12: data/meta/2022f.json] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/moment-timezone.js_0.5.38+dfsg-1+2022f_unstable.log

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

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

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

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

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Jan 2023 21:37:52 +
Source: moment-timezone.js
Architecture: source
Version: 0.5.40+dfsg-1+2022g
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Martina Ferrari 
Closes: 1028879
Changes:
 moment-timezone.js (0.5.40+dfsg-1+2022g) unstable; urgency=medium
 .
   * New upstream version 0.5.40. Closes: #1028879.
   * Remove unneeded patch.
   * debian/rules: Improve dependency graph.
Checksums-Sha1:
 0e31459daf8f6dad698859e6733fa0e94c3e8fe5 2349 
moment-timezone.js_0.5.40+dfsg-1+2022g.dsc
 4c4b0e43dc9c8c5fd86b49766d4c72a451e00740 1297500 
moment-timezone.js_0.5.40+dfsg.orig.tar.xz
 77681410abf7f1bdfdf014dee2f5da61397bf6ee 5644 
moment-timezone.js_0.5.40+dfsg-1+2022g.debian.tar.xz
 b6bf16728ae7e830c636e31b39d3f89946d4ad9e 20339 
moment-timezone.js_0.5.40+dfsg-1+2022g_amd64.buildinfo
Checksums-Sha256:
 42003d2dd38d915d1330a48d892a9b86975cb16a4e493fff9816f99a06b7df36 2349 
moment-timezone.js_0.5.40+dfsg-1+2022g.dsc
 6705ef04be0d913f6b925ed9707c8d999cc24405bb784dcbd21c1a323e1ac075 1297500 
moment-timezone.js_0.5.40+dfsg.orig.tar.xz
 37fb1afca62439e3588ca7842cd2a5f785854432b5d2e3317d2cd4420e3bc6c0 5644 
moment-timezone.js_0.5.40+dfsg-1+2022g.debian.tar.xz
 425f2d5123cf672ac454e155f943596d606c354b923b9bd8dd93822b81c1fc90 20339 
moment-timezone.js_0.5.40+dfsg-1+2022g_amd64.buildinfo
Files:
 727e971d5a87adc8880f3a1bc46d324d 2349 javascript optional 
moment-timezone.js_0.5.40+dfsg-1+2022g.dsc
 924a4d74bf4e94f796998053f728f62b 1297500 javascrip

Bug#1027943: regina-normal FTBFS with Python 3.11 as default version

[Benjamin Burton]

Hi Simon, Graham,

Thanks both of you for looking into this (and Graham: the upstream patch you 
found is indeed the right one for this issue).

As it happens I have a fix tested and ready to upload but waiting for me to 
come back from travels (since I didn’t take my private key with me). If it’s 
okay I might just upload that since I’ve already gone through the usual manual 
testing (e.g., the GUI, desktop integration, etc.) that I do for these packages.

Having said that, thanks again both of you.

- Ben.

--

Prof. Benjamin Burton
Computational Geometry & Topology Group
School of Mathematics and Physics
The University of Queensland, Australia

UQ ALLY   ::   Supporting and celebrating the diversity of sexuality, gender 
and sex at UQ.   Pronouns: He, him, his

Bug#1029534: libreoffice-common: breaks libreoffice-core from the same version

[Sven Joachim]

Package: libreoffice-common
Version: 4:7.4.4-7
Severity: serious

The Breaks in libreoffice-common need to be adjusted for the recent
epoch bumps.  Among others, libreoffice-common Breaks
libreoffice-core (>= 1:7.5~), making libreoffice-core 4:7.4.4-7
not installable.

Good luck figuring out what other relationships need to be changed, and
take your time.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Bug#1028996: marked as done (python-configshell-fb: (autopkgtest) needs update for Python 3.11)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 21:58:33 +
with message-id 
and subject line Bug#1028996: fixed in python-configshell-fb 1:1.1.28-2.1
has caused the Debian Bug report #1028996,
regarding python-configshell-fb: (autopkgtest) needs update for Python 3.11
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.)


-- 
1028996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-configshell-fb
Version: 1:1.1.28-2
Severity: serious
Tag: bookworm sid
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Hi Maintainer

The autopkgtests of python-configshell-fb fail with Python 3.11 as the
default version (and Python 3.10 still supported) [1].  I've copied
what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/p/python-configshell-fb/testing/amd64/


Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.xyuu059i/downtmp/build.k7y/src/examples/myshell",
line 173, in 
main()
  File "/tmp/autopkgtest-lxc.xyuu059i/downtmp/build.k7y/src/examples/myshell",
line 170, in main
shell.run_interactive()
  File "/usr/lib/python3/dist-packages/configshell_fb/shell.py", line
900, in run_interactive
self._cli_loop()
  File "/usr/lib/python3/dist-packages/configshell_fb/shell.py", line
729, in _cli_loop
self.run_cmdline(cmdline)
  File "/usr/lib/python3/dist-packages/configshell_fb/shell.py", line
843, in run_cmdline
self._execute_command(path, command, pparams, kparams)
  File "/usr/lib/python3/dist-packages/configshell_fb/shell.py", line
818, in _execute_command
result = target.execute_command(command, pparams, kparams)
 ^
  File "/usr/lib/python3/dist-packages/configshell_fb/node.py", line
1405, in execute_command
self.assert_params(method, pparams, kparams)
  File "/usr/lib/python3/dist-packages/configshell_fb/node.py", line
1420, in assert_params
spec = inspect.getargspec(method)
   ^^
AttributeError: module 'inspect' has no attribute 'getargspec'. Did
you mean: 'getargs'?
--- End Message ---
--- Begin Message ---
Source: python-configshell-fb
Source-Version: 1:1.1.28-2.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated 
python-configshell-fb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 21 Jan 2023 21:29:09 +0100
Source: python-configshell-fb
Architecture: source
Version: 1:1.1.28-2.1
Distribution: unstable
Urgency: medium
Maintainer: Linux Block Storage Team 
Changed-By: Sebastian Ramacher 
Closes: 1028996
Changes:
 python-configshell-fb (1:1.1.28-2.1) unstable; urgency=medium
 .
   [ Bas Couwenberg ]
   * Non-maintainer upload.
   * Add upstream patches to fix test failure with python3.11.
 (Closes: #1028996)
Checksums-Sha1:
 9139bd89299cd380650e81be59444e9b56d22a56 2276 
python-configshell-fb_1.1.28-2.1.dsc
 62c7d50b508963787719507ae43fcec2ca74a8e5 5024 
python-configshell-fb_1.1.28-2.1.debian.tar.xz
Checksums-Sha256:
 d343cd388243d1ac234a5f9887d739689036fab2b15733b4333077621d8cb18b 2276 
python-configshell-fb_1.1.28-2.1.dsc
 aeafc1a7a07628611fd0984a55bfb107aa7ac2970ab7e1d4155d6ed74e089cfa 5024 
python-configshell-fb_1.1.28-2.1.debian.tar.xz
Files:
 ddcb795f9fd2d8263d40d40881e63203 2276 python optional 
python-configshell-fb_1.1.28-2.1.dsc
 1763399795ba5c7abdcff5acff20c9d3 5024 python optional 
python-configshell-fb_1.1.28-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmPMS3YACgkQafL8UW6n
GZMhMhAAqRt/BxhtpBuKIENHNeWP4E0IgY9+aVJQq3Ndy09S+mpaA1n3axjdTa2l
5LuLOexmqjy7W6z7aaAX99H/Q2YY3g2Izc3pmVxEE7zaWGK2M7MCH64DF7rrmauk
z+PC50XThCKbREf8TE6SJlkPCZszIKYdnI7FDQbXa40lELWscFtT5sOAm14q4bf3
hvPSA2pkpfMcw7RWV9apvO/vuk

Processed: Re: python-xarray autopkgtest fail on i386

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1004869 {Done: Jochen Sprickerhof } 
[src:python-xarray] python-xarray: autopkgtest regression on i386
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-xarray/2022.12.0-2.
> found -1 2023.01.0-1
Bug #1004869 [src:python-xarray] python-xarray: autopkgtest regression on i386
Marked as found in versions python-xarray/2023.01.0-1.

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

Bug#1004869: python-xarray autopkgtest fail on i386

[Rebecca N. Palmer]

Control: reopen -1
Control: found -1 2023.01.0-1

This patch was dropped in the next upload (probably by accident), and 
hence this bug has reappeared.


It is currently listed as blocking pandas from testing, though I'm not 
sure why (it isn't obvious why pandas and xarray would have to go together).

Bug#1029348: marked as done (php8.1: keep out of testing)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 21:30:40 +
with message-id 
and subject line Bug#1029489: Removed package(s) from unstable
has caused the Debian Bug report #1029348,
regarding php8.1: keep out of testing
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.)


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

This is a placeholder RC bug so that php8.1 is kept out of testing.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 8.1.12-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#878983: marked as done (cduce FTBFS with OCaml 4.05.0)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 21:23:37 +
with message-id 
and subject line Bug#1028324: Removed package(s) from unstable
has caused the Debian Bug report #878983,
regarding cduce FTBFS with OCaml 4.05.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.)


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

https://buildd.debian.org/status/package.php?p=cduce&suite=sid

...
Build types/atoms.cmx
Build types/normal.cmi
Build types/normal.cmx
File "types/normal.ml", line 1:
Error: The implementation types/normal.ml
   does not match the interface types/normal.cmi:
   ...
   At position module Make(X1)(X2) : 
   Values do not match:
 val pi1 : (X1.t * '_a) list -> X1.t
   is not included in
 val pi1 : t -> X1.t
   File "types/normal.ml", line 80, characters 6-9: Actual declaration
Makefile.distrib:317: recipe for target 'types/normal.cmx' failed
make[2]: *** [types/normal.cmx] Error 2
--- End Message ---
--- Begin Message ---
Version: 0.6.0-5+rm

Dear submitter,

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

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

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

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

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

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

Bug#1028324: marked as done (RM: cduce -- RoQA, unmaintained, FTBFS, zero popcon)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 21:23:33 +
with message-id 
and subject line Bug#1028324: Removed package(s) from unstable
has caused the Debian Bug report #1028324,
regarding RM: cduce -- RoQA, unmaintained, FTBFS, zero popcon
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.)


-- 
1028324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cduce
Severity: normal
User: tobi-rm-proposals@d.o
Usertags: rm-proposal

Dear Maintainer,

- the package has currently 1 RC (FTBFS) bug on all architectures:

#878983 [S|⛺|  ] [src:cduce] cduce FTBFS with OCaml 4.05.0

- It is even not installable in sid:

The following packages have unmet dependencies:
 cduce : Depends: libcamlp4-ocaml-dev-p9wj7
 Depends: libcurl-ocaml-dev-34fm5
 Depends: libexpat-ocaml-dev-18y95
 Depends: libocamlnet-ocaml-dev-zpic0 but it is not installable
 Depends: libpcre-ocaml-dev-54x46
 Depends: ocaml-nox-4.02.3
 Depends: ocaml-ulex-68rw6
E: Unable to correct problems, you have held broken packages.


- The last upload was 2015.

- popcon is "0".

- There are no r-depends on the package.


This makes me wonder if we should retire this package.

If you don't think so, please fix your package.

If you also think that it shoulw be removed, just reassign it to the
ftp.debian.org pseudo package.

If there is no answer, I will reassing the bug for removal in exactly 3 months.

Thanks!
--
tobi




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

Kernel: Linux 6.0.0-6-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 cduce |0.6.0-5 | source
 cduce | 0.6.0-5+b6 | mips64el, mipsel, ppc64el, s390x
 cduce | 0.6.0-5+b7 | amd64, arm64, armel, armhf, i386

--- Reason ---
RoQA, unmaintained, FTBFS, zero popcon
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1028...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1028324

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

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

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

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 21:22:41 +
with message-id 
and subject line Bug#1029346: Removed package(s) from unstable
has caused the Debian Bug report #1022914,
regarding Removal notice: obsolete
to be marked as done.

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

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


-- 
1022914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-test-framework-th
Version: 0.2.4-12
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * Seems unmaintained; Last upload more than 10 years ago
  * It's not part of the latest Stackage LTS
  * Depends on deprecated software (see #1022040)

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

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.2.4-12+rm

Dear submitter,

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

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

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

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

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

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

Processed: Re: Bug#1028826: herbstluftwm: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:python-xlib
Bug #1028826 [src:herbstluftwm] herbstluftwm: FTBFS: E: Build killed with 
signal TERM after 150 minutes of inactivity
Bug reassigned from package 'src:herbstluftwm' to 'src:python-xlib'.
No longer marked as found in versions herbstluftwm/0.9.5-3.
Ignoring request to alter fixed versions of bug #1028826 to the same values 
previously set
> affects -1 src:herbstluftwm
Bug #1028826 [src:python-xlib] herbstluftwm: FTBFS: E: Build killed with signal 
TERM after 150 minutes of inactivity
Added indication that 1028826 affects src:herbstluftwm
> forwarded -1 https://github.com/python-xlib/python-xlib/issues/241
Bug #1028826 [src:python-xlib] herbstluftwm: FTBFS: E: Build killed with signal 
TERM after 150 minutes of inactivity
Set Bug forwarded-to-address to 
'https://github.com/python-xlib/python-xlib/issues/241'.

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

Bug#1028826: herbstluftwm: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Christoph Egger]

Control: reassign -1 src:python-xlib
Control: affects -1 src:herbstluftwm
Control: forwarded -1 https://github.com/python-xlib/python-xlib/issues/241

Indeed, upstream also confirms this issue affects their CI setup

Thanks!

Christoph

On Sonntag, 15. Januar 2023 09:10:37 CET you wrote:
> Dear Maintainer,
> 
> Please see below the output of this command:
> > cd obj-x86_64-linux-gnu
> > PYTHONPATH=../python python3 -m pytest -x --pdb ../tests/test_rules.py
> 
> [...]
> 
> This failure leads to [1][2]. After applying upstream commit, your package
> builds fine and all tests pass again.
> I think this bug should be reassigned to src:python-xlib.
> 
> Kind Regards
> 
> [1] https://github.com/python-xlib/python-xlib/issues/241
> [2] https://github.com/python-xlib/python-xlib/pull/242

Bug#1001653: marked as done (aribas: autopkgtest fails with glibc >= 2.33: stack smashing detected)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 20:55:19 +
with message-id 
and subject line Bug#1001653: fixed in aribas 1.65-1
has caused the Debian Bug report #1001653,
regarding aribas: autopkgtest fails with glibc >= 2.33: stack smashing detected
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.)


-- 
1001653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aribas
Version: 1.64-6
Severity: serious
Tags: patch upstream

Dear maintainer,

The aribas autopkgtests fails when run on an i386 system with glibc 2.33
installed. Here is the relevant part of the tests: 

| Preparing to unpack .../aribas_1.64-6_i386.deb ...
| Unpacking aribas (1.64-6) ...
| Setting up aribas (1.64-6) ...
| Setting up autopkgtest-satdep (0) ...
| (Reading database ... 13148 files and directories currently installed.)
| Removing autopkgtest-satdep (0) ...
| autopkgtest [21:14:39]: test upstream: [---
| *** stack smashing detected ***: terminated
| Aborted
| autopkgtest [21:14:40]: test upstream: ---]
| autopkgtest [21:14:40]: test upstream:  - - - - - - - - - - results - -
| - - - - - - - -
| upstream FAIL non-zero exit status 1
| autopkgtest [21:14:40]: test upstream:  - - - - - - - - - - stderr - - -
| - - - - - - -
| *** stack smashing detected ***: terminated
| Aborted
| autopkgtest [21:14:40]:  summary
| upstream FAIL non-zero exit status 1

The full autopkgtest log is available there:
https://ci.debian.net/data/autopkgtest/testing/i386/a/aribas/17524130/log.gz

After investigation it appears that aribas contains i386 assembly code
which doesn't follow the calling convention with regard to the direction
flag. The divarr and modarr function modifies it to the "backward"
direction with the STD instruction, but fails to modify it back to the
"forward" direction upon exit as required in the System V ABI [1]:

| EFLAGS  
|
| The flags register contains the system flags, such as the direction
| flag and the carry flag. The direction flag must be set to the
| "forward" (that is, zero) direction before entry and upon exit from
| a function. Other user flags have no specified role in the standard
| calling sequence and are not preserved.

The patch below fixes that, and is enough to get the autopkgtest
working.

Regards,
Aurelien


[1] http://www.sco.com/developers/devspecs/abi386-4.pdf


--- aribas-1.64.orig/src/LINUX/arito386.S
+++ aribas-1.64/src/LINUX/arito386.S
@@ -211,6 +211,7 @@ divarr:
popl%edi
popl%ebx
popl%ebp
+   cld
ret
 
 /*-*/
@@ -266,5 +267,6 @@ mod4arr:
popl%esi
popl%ebx
popl%ebp
+   cld
ret
 /*-*/
--- End Message ---
--- Begin Message ---
Source: aribas
Source-Version: 1.65-1
Done: Ralf Treinen 

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

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated aribas package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Jan 2023 20:12:10 +0100
Source: aribas
Architecture: source
Version: 1.65-1
Distribution: unstable
Urgency: medium
Maintainer: Ralf Treinen 
Changed-By: Ralf Treinen 
Closes: 991782 1001653
Changes:
 aribas (1.65-1) unstable; urgency=medium
 .
   [ Ralf Treinen ]
   * update debian/watch file
   * add src/aribas to the filter in gbp.conf since upstream distributes a
 pre-compiled binary with the sources.
   * new upstream version,
 - drop patch no_strip as it is not useful
 - drop patch casting_pointers which has been integrated upstream
 - add patch fix-make-clean to make "make clean" idempotent
 - add patch compile-with-debug-symbols to use the -g flag to gcc
   * upstream has dropped the i386 assembly code (closes: #1001653), remove
 the special case for i386 in debian/rules 

Processed: Re: Bug#1029447: unmuting audio breaks video playing in browsers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1029447 [wireplumber] unmuting audio breaks video playing in browsers
Severity set to 'normal' from 'grave'

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

Bug#1029447: unmuting audio breaks video playing in browsers

[Dylan Aïssi]

Control: severity -1 normal

Le dim. 22 janv. 2023 à 18:15, Marco d'Itri  a écrit :
>
> If I replace pipewire-media-session with wireplumber then playing video
> in browsers (e.g. Youtube and other similar sites, or even just embedded
>  tags) stutters and stops. Just pressing the mute button in the
> video player makes video work as usual, 100% reproducibile.
> I have reproduced this both with Firefox and Chrome.
>
> Installing again pipewire-media-session and rebooting fixed this.
>

Not reproducible here.

With wireplumber installed and after a reboot what is the output of
"pactl info"?
And what audio backend uses firefox (in "about:support" then in the
"Audio section" )?
Do you have both  wireplumber.service and pipewire-pulse.service running?

Thanks,
Dylan

Bug#1027943: regina-normal FTBFS with Python 3.11 as default version

[Simon Quigley]

Hello,

I've uploaded this fix to DELAYED/2, please let me know if you would like it 
cancelled/delayed further/not uploaded.

Thanks,
--
Simon Quigley
si...@tsimonq2.net
tsimonq2 on LiberaChat and OFTC
@tsimonq2:linuxdelta.com on Matrix
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1022843: ifupdown: network down after systemctl restart

[Amy Kos]

Hi,

boot online:
 No delay.

boot offline:
 60 seconds boot delay (dhcp tiemout) per defined interface.

Please abort or do the timeout in background like ifupdown 0.8.39 used 
to,

instead of delaying boot.

Didn't expect this bug to be reopened, opened another one yesterday.
Please feel free to close or merge it.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029449

Cheers,
Amy

Bug#1029248: marked as done (binoculars: FTBFS: AttributeError: module 'numpy' has no attribute 'bool'. Unable to parse configuration option 'maskmatrix'. The error can quite likely be solved by modif

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 19:49:49 +
with message-id 
and subject line Bug#1027192: fixed in binoculars 0.0.12-1.1
has caused the Debian Bug report #1027192,
regarding binoculars: FTBFS: AttributeError: module 'numpy' has no attribute 
'bool'. Unable to parse configuration option 'maskmatrix'. The error can quite 
likely be solved by modifying the option in the configuration file.
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args='{interpreter} -m unittest 
> discover -s tests -t {dir} -v'
>   pybuild --test -i python{version} -p 3.11 --system=custom 
> "--test-args={interpreter} -m unittest discover -s tests -t {dir} -v"
> I: pybuild base:240: python3.11 -m unittest discover -s tests -t 
> /<> -v
> test_IO (tests.test_cfg.TestCase.test_IO) ... ok
> test_IO (tests.test_id03.TestCase.test_IO) ... 
> /<>/binoculars/backends/id03.py:1177: FutureWarning: In the 
> future `np.bool` will be defined as the corresponding NumPy scalar.  (This 
> may have returned Python scalars in past versions.
>   return numpy.array(numpy.load(filename), dtype=numpy.bool)
> ERROR
> test_IO (tests.test_metadata.MetaDataTestCase.test_IO) ... expected failure
> 
> ==
> ERROR: test_IO (tests.test_id03.TestCase.test_IO)
> --
> Traceback (most recent call last):
>   File "/<>/tests/test_id03.py", line 24, in setUp
> self.id03input = id03.EH2(cfg_unparsed)
>  ^^
>   File "/<>/binoculars/util.py", line 744, in __init__
> self.parse_config(config)
>   File "/<>/binoculars/backends/id03.py", line 909, in 
> parse_config
> super(EH2, self).parse_config(config)
>   File "/<>/binoculars/backends/id03.py", line 478, in 
> parse_config
> self.config.maskmatrix = load_matrix(
>  
>   File "/<>/binoculars/backends/id03.py", line 1177, in 
> load_matrix
> return numpy.array(numpy.load(filename), dtype=numpy.bool)
>^^
>   File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 284, in 
> __getattr__
> raise AttributeError("module {!r} has no attribute "
> AttributeError: module 'numpy' has no attribute 'bool'. Unable to parse 
> configuration option 'maskmatrix'. The error can quite likely be solved by 
> modifying the option in the configuration file.
> 
> --
> Ran 3 tests in 0.065s
> 
> FAILED (errors=1, expected failures=1)
> ConfigFile{
>   [dispatcher]
> destination = b'demo_{first}-{last}.hdf5'
> overwrite = b'true'
> type = b'local'
>   [projection]
> resolution = b'0.002, 0.002, 1'
> type = b'id03:hklprojection'
>   [input]
> centralpixel = b'40, 255'
> imagefolder = b'/path/to/data/images/{rUCCD[0]}/'
> pixelsize = b'0.055, 0.055'
> sdd = b'1050'
> specfile = b'/path/to/data/file.spec'
> target_weight = b'4000'
> type = b'id03:eh1'
> xmask = b'50-235'
> ymask = b'185-253,262-400'
> }
> origin = test.hdf5
> command = 
> MetaBase{
>   [first]
> string = string
> numpy.array = [0 1 2 3 4 5 6 7 8 9]
> list = range(0, 10)
> tuple = (0, 1, 2, 3, 4, 5, 6, 7, 8, 9)
> }
> 
> Space (3 dimensions, 1331 points, 20.8 kB) {
> Axis h (min=0.0, max=10.0, res=1.0, count=11)
> Axis k (min=0.0, max=10.0, res=1.0, count=11)
> Axis l (min=0.0, max=10.0, res=1.0, count=11)
> }
> E: pybuild pybuild:388: test: plugin custom failed with: exit code=1: 
> python3.11 -m unittest discover -s tests -t /<> -v
>   rm -fr -- /tmp/dh-xdg-rundir-D4gM_IpQ
> dh_auto_test: error: pybuild --test -i python{version} -p 3.11 
> --system=custom "--test-args={interpreter} -m unittest discover -s tests -t 
> {dir} -v" returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2023/01/20/binoculars_0.0.12-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.or

Bug#1027192: marked as done (binoculars: autopkgtest fail with numpy/1.24.1)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 19:49:49 +
with message-id 
and subject line Bug#1027192: fixed in binoculars 0.0.12-1.1
has caused the Debian Bug report #1027192,
regarding binoculars: autopkgtest fail with numpy/1.24.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.)


-- 
1027192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: binoculars
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro
--- End Message ---
--- Begin Message ---
Source: binoculars
Source-Version: 0.0.12-1.1
Done: Bas Couwenberg 

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

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

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated binoculars 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, 11 Jan 2023 17:48:13 +0100
Source: binoculars
Built-For-Profiles: noudeb
Architecture: source
Version: 0.0.12-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian PaN Maintainers 

Changed-By: Bas Couwenberg 
Closes: 1027192
Changes:
 binoculars (0.0.12-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch to fix test failure with Numpy 1.24.
 (closes: #1027192)
Checksums-Sha1:
 230b9d6ea6b96a9e8e0c3277fd2778946655df77 2409 binoculars_0.0.12-1.1.dsc
 6f93614b62e0b383d5abbbef23e5f1e09990a53f 4968 
binoculars_0.0.12-1.1.debian.tar.xz
 c2c0cb22aaa6985b81027f7609f5482c445ba4ba 8751 
binoculars_0.0.12-1.1_source.buildinfo
Checksums-Sha256:
 e6bb4e4d3858e7d7f9251b43c1bb1687b929acc540d3f4600082fadc43bbc713 2409 
binoculars_0.0.12-1.1.dsc
 bc26e12ff30bd2bed2152ebfeed3491125e423ea82eb0ca08cea779f9f078e47 4968 
binoculars_0.0.12-1.1.debian.tar.xz
 49c908dfa2ce604fc61bfbff5d00f73514381f47344ac6bf5f273ee497a2f072 8751 
binoculars_0.0.12-1.1_source.buildinfo
Files:
 39e579e3daa162b9b01780a38f121976 2409 science optional 
binoculars_0.0.12-1.1.dsc
 b9a759b29e4c2cdf0613e8053a6afe92 4968 science optional 
binoculars_0.0.12-1.1.debian.tar.xz
 cd7401a711e6d2dd8a80027e6e26b851 8751 science optional 
binoculars_0.0.12-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXHq+og+GMEWcyMi14n8s+EWML6QFAmPO4CoACgkQ4n8s+EWM
L6TAnQ/9ENZi0YVOGLND8avcxd6peH537v3VebsHQbZ/G7kC9CHftxGbEsGjkwUz
JJWHuey/plPUKNG/RQNBfSRfgSSTJ3vGpy2p1ZZsbgoX9PfBOeWps/ebI4z4OKlA
FK5x9C+58pOMASmS/Jv28ie9WGs+vFnnGbvCIwGO/w2EFfogis0hIXpZj4kqTLMz
brUqs6HrJDEaPB9+jRnizGYb/OV/cQsMsDHGSf09j1UV0aZ33yLLDfp5e8qC6XOw
8I2Ots+sO/eT9IC/D4VXBSP+NnsZifNNsppa8MPHbN5PAZymduQG0goSNjw4kzuv
U78YRkvKe5xjhbvTnRrQUAcTBYael2Oqz8+K0yv3ezPbq6zaGVX/zIvsS0JjOpx3
yJF1ABq60125xcqZ5YV5NCWjA3JIJZmXLAWEbUxMgQiHdZIvykhhofGdvhKd7RKc
UsIIJO2CDXSDq0ZwnupwG4Cf+6Hv0Iax6NaCLKURDc37Pbd5iBQYQKvNCMBiiI2r
6hKT2uryy4/KXatqSkFMrPKf/SYwZL0mAHAkoDi2eiCTZmTuveqnC1Ef/L9gQcu8
HZSmWQQoE2cNNcl6x

Bug#1029310: [Help] Re: Bug#1029310: src:r-cran-bayesplot: fails to migrate to testing for too long: autopkgtest regression

[Andreas Tille]

Hi Nilesh,

Am Mon, Jan 23, 2023 at 03:49:29PM +0530 schrieb Nilesh Patra:
> >I admit I'm running out of ideas but for the moment my last resort
> >is to skip the 8 affected test, let the packages migrate to testing
> >and revert skipping the tests afterwards.
> 
> I did find an issue[3] which states ggplot2 breaks bayesplot 1.9.0 and spews 
> the exact same errors we observe in debci.
> There's also an upstream issue with bayesplot installation (similar stuff 
> again) where it works for some people but not for others, see[4].
> But then I'm not sure as to why it works for me, you and salsa CI. For now 
> I'll have to dismiss it by calling it black magic.
> 
> Your approach sounds fair. Maybe you should do what you wrote (disable tests, 
> let it migrate, enable tests again)

I did so just to learn that there are new errors now[5].  I admit I've
lost my nerves and uploaded by really forcing acceptance of all errors[6].
I'll revert this after testing migration as well as the patch I tried
before.

Kind regards
Andreas.
 
> >[1] https://ci.debian.net/packages/r/r-cran-bayesplot/testing/amd64/
> >[2] 
> >https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-bayesplot/28139180/log.gz
> [3]: 
> https://github.com/tidyverse/ggplot2/blob/main/revdep/problems.md#bayesplot
> [4]: 
> https://github.com/stan-dev/bayesplot/issues/297

[5] 
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-bayesplot/30633104/log.gz
 
[6] 
https://salsa.debian.org/r-pkg-team/r-cran-bayesplot/-/blob/master/debian/tests/run-unit-test#L15

-- 
http://fam-tille.de

Processed: Re: Bug#1029513: xss-lock: crashes with core dump on activation

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1029513 [xss-lock] xss-lock: crashes with core dump on activation
Severity set to 'important' from 'grave'
> tags -1 +help
Bug #1029513 [xss-lock] xss-lock: crashes with core dump on activation
Added tag(s) help.

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

Bug#1029513: xss-lock: crashes with core dump on activation

[Ian Campbell]

Control: severity -1 important
Control: tags -1 +help

On Mon, 2023-01-23 at 11:04 -0500, Stuart Freeman wrote:
> Calling `xdg-screensaver activate` causes xss-lock to dump core.

Thank you for your report.

>From the logs it looks like xss-lock is actually hitting an assertion
which manifests in a core dump:

>     Jan 23 09:52:48 gamera xss-lock[8434]: Error getting session: 
> GDBus.Error:org.freedesktop.login1.NoSessionForPID: Caller does not belong to 
> any known session.
>     Jan 23 09:53:05 gamera xss-lock[8434]: xss-lock: ./src/xss-lock.c:469: 
> logind_session_set_locked_hint: Assertion `logind_session' failed.

I've tried to repro but unfortunately I can't.

It seems like xss-lock is failing to talk to logind on your system. I'm
not sure why this would be, is it possible that logind on your system
is not running or is otherwise misconfigured? 

I launch xss-lock from .i3/config rather than the system unit which you
seem to be using, it's possible that's related? Perhaps the unit needs
to depend (requires?) on some other services for ordering (e.g. logind
or maybe dbus session which is used to talk to logind)? Some sort of
`Requires=dbus.service` type thing maybe?

Since I don't use this configuration and I'm not especially familiar
with system user units I have no good advice on how to do this, or how
to go about debugging, sorry.

Since it does not appear to be generally broken for everyone I have
downgraded the severity to important.

Thanks again,
Ian.

Bug#1027355: src:libapreq2: Should not migrate to testing.

[Salvatore Bonaccorso]

Hi,

On Fri, Dec 30, 2022 at 05:32:49PM +0100, Tobias Frost wrote:
> Source: libapreq2
> Severity: serious
> Justification: possibly not suitable for a stable release
> X-Debbugs-Cc: Debian Security Team , Salvatore 
> Bonaccorso 
> Control: affects -1 lua-apr
> Control: affects -1 rapache
> Control: affects -1 libapache2-authcassimple-perl
> Control: affects -1 libapache2-sitecontrol-perl
> 
> The package should probably be removed for bookworm,
> at least without clarification from upstream about the security issue.
> (see for details #1018191)

FTR, let's not close this bug and migrate libapreq2 further for
bookworm (even the open known CVEs are addressed) as long it does not
get an active maintainer interested supporting potential updates
needed for the bookworm release.

libapreq2 including the affected rdepds are now out of bookworm.

Regards,
Salvatore

Bug#1028333: marked as done (puppetserver: find an upgrade path from puppet-master)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 19:29:18 +
with message-id 
and subject line Bug#1028333: fixed in puppetserver 7.9.3-3
has caused the Debian Bug report #1028333,
regarding puppetserver: find an upgrade path from puppet-master
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.)


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

Package: puppetserver
Severity: grave

At the moment, this package doesn't acknowledge the existence of the 
puppet-master package at all. As such, if the two packages are installed 
on the same machines, important breakage is likely.


A proper upgrade path should be found, to make the transition from 
puppet-master to puppetserver seamless.


--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_0xE1E5457C8BAD4113.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: puppetserver
Source-Version: 7.9.3-3
Done: Jérôme Charaoui 

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

Debian distribution maintenance software
pp.
Jérôme Charaoui  (supplier of updated puppetserver package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Jan 2023 12:50:03 -0500
Source: puppetserver
Architecture: source
Version: 7.9.3-3
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 

Changed-By: Jérôme Charaoui 
Closes: 1028333
Changes:
 puppetserver (7.9.3-3) unstable; urgency=medium
 .
   * d/control: build transitional packages (Closes: #1028333)
   * d/control: change section from java to admin
   * d/rules: do not enable service upon installation
   * sync systemd service unit status with internal state
   * fix puppetserver subcommands
   * add missing cli subcommands
   * add jruby lib path to java arguments
   * add appropriate lintian overrides
   * improve autopkgtests using ruby-serverspec
Checksums-Sha1:
 8557b847f167ff710b3bc0640e259ea58c4143c7 3574 puppetserver_7.9.3-3.dsc
 17b401a6bce0857b1ce7613c2b813ca180c11955 21652 
puppetserver_7.9.3-3.debian.tar.xz
 fbb98913cb34e6fb3c7da8ca766d2f438277f8da 18446 
puppetserver_7.9.3-3_amd64.buildinfo
Checksums-Sha256:
 633843aaf4b211c537bbb0d22280a727f5a6c7622a70d7108a24c9b08d82d720 3574 
puppetserver_7.9.3-3.dsc
 8cf329d24a186e7d0ce222608c6f12c89748c4377d1892546e310cd1d1b13877 21652 
puppetserver_7.9.3-3.debian.tar.xz
 be14d5cf130266abc32fd0f3f7bf2ae6cafcbcababe6000ee578cdb506fecb8d 18446 
puppetserver_7.9.3-3_amd64.buildinfo
Files:
 aca9f255c67c3f9f2b44d2b7a8ffe769 3574 admin optional puppetserver_7.9.3-3.dsc
 c1ed83adf600467d610bf103ed6be0cd 21652 admin optional 
puppetserver_7.9.3-3.debian.tar.xz
 50f92b91e0caf5597cab045c554feb47 18446 admin optional 
puppetserver_7.9.3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQTAq04Rv2xblqv/eu5pxS9ljpiFQgUCY87WBgAKCRBpxS9ljpiF
QhJgAQCV/JEoMimqQBhiw8rSTBkOUfGQ7qnhg5WH9X2StSIg5AD/TIkkCl9D0EkT
qDOzK/kSYAnUSIVcMWFLSVcthYuMNgU=
=vSbp
-END PGP SIGNATURE End Message ---

Bug#1022843: Bug#1029352: Bug#1022843: ifupdown: network down after systemctl restart

[Cyril Brulebois]

Hi Oleg,

Oleg A. Arkhangelsky  (2023-01-23):
> I tried this *.deb (Pascal approach). It doesn't change behaviour
> introduced after this patch [1]. Yes, restart for "allow-hotplug"
> interfaces work but I got the same system boot lag in Jeff configuration.

Right, I mostly tested that an available “allow-hotplug” and an available
“auto” interfaces in my VM work fine when I tested Pascal's approach, I
didn't try to disable any of them in my hypervisor.

> Cyril's latest solution seems to work. I just added "-" to /bin/sh to
> deal with cases when we have a device that is really hotplug and
> absent: […]

Right, thanks for implementing and testing the part: as I mentioned, I
wasn't sure what to do about possible errors, and didn't investigate; your
approach seems reasonable given hotpluggable interfaces may or may not be
present.

> I got fast boot (as without bad patch) and working restart. One minute
> long blocking during `systemctl restart networking` when DHCP is not
> respoding (as in Jeff config) is expected.
> 
> Thanks to all!

Thanks to both Jeff and you for your tests!


I do note that taking precautions, maintaining the status quo for working
use cases, while addressing other use cases… is sometimes not that bad;
even if that seems “needlessly convoluted”!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1029523: there is a new upstream major version that relaxes ruby requirement

[Pirate Praveen]

so updating to 4.0.1 could fix this
https://github.com/drbrain/net-http-persistent/blob/75574f2546a08aa2663b06a2e005bcf2ee304f13/Rakefile#L16

Bug#1029523: ruby-net-http-persistent want Ruby (~> 2.1)

[Pirate Praveen]

Package: ruby-net-http-persistent
Severity: grave
Justification: unable to install gitlab or use with bundler

Just add this to Gemfile.
gem "telesign"

and run,
bundle install --local
Don't run Bundler as root. Bundler can ask for sudo if it is needed, 
and installing your bundle as root will

break this application for all non-root users on this machine.
[DEPRECATED] This Gemfile does not include an explicit global source. 
Not using an explicit global source may result in a different lockfile 
being generated depending on the gems you have installed locally before 
bundler is run. Instead, define a global source in your Gemfile like 
this: source "https://rubygems.org";.

Resolving dependencies...
Bundler found conflicting requirements for the Ruby version:
 In Gemfile:
   Ruby

   telesign was resolved to 2.2.3, which depends on
 net-http-persistent (~> 3.0, >= 3.0.0) was resolved to 3.1.0, 
which depends on

   Ruby (~> 2.1)


This comes from the gemspec
https://salsa.debian.org/ruby-team/ruby-net-http-persistent/-/blob/master/net-http-persistent.gemspec#L23

Processed: raise severity (policy violation)

[Debian Bug Tracking System]

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

> severity 1029260 serious
Bug #1029260 [src:vice] vice: missing font license in d/copyright
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Bug#1022843: Bug#1029352: Bug#1022843: ifupdown: network down after systemctl restart

[Jeff King]

On Mon, Jan 23, 2023 at 03:55:50PM +0100, Santiago Ruano Rincón wrote:

> > That seems needlessly convoluted. What about this:
> > 
> > [Service]
> > Type=oneshot
> > EnvironmentFile=-/etc/default/networking
> > ExecStart=/sbin/ifup -a --read-environment
> > ExecStart=-/sbin/ifup -a --read-environment --allow=hotplug
> > ExecStop=/sbin/ifdown -a --read-environment --exclude=lo
> > RemainAfterExit=true
> > TimeoutStartSec=5min
> > 
> > "start" and "restart" configure all existing "auto" and "allow-hotplug"
> > interfaces.
> > Missing "allow-hotplug" interfaces do not be marked as configured (so that
> > they can be configured by udev) and do not make "start" or "restart" fail.
> 
> Thanks everybody for the inputs. I've applied Paul's solution, and the
> generated .deb can be downloaded from here:
> 
> https://salsa.debian.org/debian/ifupdown/-/jobs/3841392/artifacts/raw/debian/output/ifupdown_0.8.41~1.gbp3a6fae+salsaci+20230123+42_amd64.deb
> 
> Would it be possible for you (Oleg, Paul, Jeff, kibi et al.) to give it
> a try?

I tried it, and it still results in a 10-second pause during startup
while broadcasting dhcp over eth0. Which is not too surprising. You
can't get around that if you run "ifup --allow=hotplug", and it's
reasonable for systemd to wait for the process to finish, even if the
exit code doesn't affect success.

That may be an acceptable casualty for fixing the other problems, but I
suspect it's something that many laptop users will encounter (they have
wifi that is normally used and an ethernet port that is not; d-i sets
only the wifi as "auto").

I didn't test it, but I believe Cyril's approach to avoid trying to
bring up hotplug interfaces at all (unless during restart) would fix
that.

-Peff

Bug#1022843: Bug#1029352: Bug#1022843: ifupdown: network down after systemctl restart

[Oleg A. Arkhangelsky]

On Mon Jan 23, 2023 at 2:55 PM UTC, Santiago Ruano Rincón wrote:

> Thanks everybody for the inputs. I've applied Paul's solution, and the
> generated .deb can be downloaded from here:
>
> https://salsa.debian.org/debian/ifupdown/-/jobs/3841392/artifacts/raw/debian/output/ifupdown_0.8.41~1.gbp3a6fae+salsaci+20230123+42_amd64.deb
>
> Would it be possible for you (Oleg, Paul, Jeff, kibi et al.) to give it
> a try?

I tried this *.deb (Pascal approach). It doesn't change behaviour
introduced after this patch [1]. Yes, restart for "allow-hotplug"
interfaces work but I got the same system boot lag in Jeff configuration.

Cyril's latest solution seems to work. I just added "-" to /bin/sh to
deal with cases when we have a device that is really hotplug and absent:

[Service]
Type=oneshot
EnvironmentFile=-/etc/default/networking
ExecStart=/sbin/ifup -a --read-environment
ExecStart=-/bin/sh -c 'if [ -f /run/network/restart-hotplug ]; then 
/sbin/ifup -a --read-environment --allow=hotplug; fi'
ExecStop=/sbin/ifdown -a --read-environment --exclude=lo
ExecStopPost=/usr/bin/touch /run/network/restart-hotplug
RemainAfterExit=true
TimeoutStartSec=5min

I got fast boot (as without bad patch) and working restart. One minute
long blocking during `systemctl restart networking` when DHCP is not
respoding (as in Jeff config) is expected.

Thanks to all!

[1] https://salsa.debian.org/debian/ifupdown/-/merge_requests/17

>
> Cheers,
>
>  -- S

Processed: Found 3.23-1

[Debian Bug Tracking System]

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

> found 973990 3.23-1
Bug #973990 [xtables-addons] shorewall: Fails to start with "Couldn't load 
match `iface':No such file or directory"
There is no source info for the package 'xtables-addons' at version '3.23-1' 
with architecture ''
Unable to make a source version for version '3.23-1'
Marked as found in versions 3.23-1.
>
End of message, stopping processing here.

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

Bug#1028837: python-zstandard 0.19.0-1 possibly no more compatible with python3.10

[s3v]

On Mon, 23 Jan 2023 19:06:01 +0100 s3v  wrote:

>
> exceptiongroup module has been packaged in Debian [1]

Sorry for the mess, there is the link:

https://tracker.debian.org/pkg/python-exceptiongroup

Processed: Re: Fixed in 3.11-1

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #973990 {Done: Jeremy Sowden } [xtables-addons-common] 
shorewall: Fails to start with "Couldn't load match `iface':No such file or 
directory"
Bug reopened
Ignoring request to alter fixed versions of bug #973990 to the same values 
previously set
> reassign -1 xtables-addons
Bug #973990 [xtables-addons-common] shorewall: Fails to start with "Couldn't 
load match `iface':No such file or directory"
Bug reassigned from package 'xtables-addons-common' to 'xtables-addons'.
No longer marked as found in versions xtables-addons/3.23-1.
Ignoring request to alter fixed versions of bug #973990 to the same values 
previously set
> severity -1 critical
Bug #973990 [xtables-addons] shorewall: Fails to start with "Couldn't load 
match `iface':No such file or directory"
Severity set to 'critical' from 'normal'

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

Bug#1028837: python-zstandard 0.19.0-1 possibly no more compatible with python3.10

[s3v]

Hi,

On Sat, 21 Jan 2023 17:49:33 +0100 =?utf-8?Q?=C3=89tienne?= Mollier 
 wrote:
> Hello from Debian Med Sprint, I had a look at this bug because
> it flagged at least augur for autoremoval.
>
> The module caught by this exception looks to be only supported
> in python3.11:
> >> ModuleNotFoundError: No module named 'exceptiongroup'
>
> When searching for this module, there seems to be a backport
> available for older python3 versions[1], but it does not seem to
> be available in Debian yet. Easier fix might be to build only
> for the default python3 for the time being. I tried limiting
> the build dependencies to python3-dev and it "fixed" the test
> failure for me. I'm considering doing a team upload in hope
> this helps.
>
> [1]: https://pypi.org/project/exceptiongroup/
>
> Have a nice day, :)
> --
> Étienne Mollier 
> Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
> Sent from my alarm clock.

exceptiongroup module has been packaged in Debian [1]
This missing leads rdeps tests to fail for Python 3.10, I guess.

Thanks for your work.

Kind Regards.

[1] https://tracker.debian.org/pkg/python-zstandard

Bug#1029459: hp-plugin crashes when trying to download plugin with error NameError: name 'get_distro_std_name' is not defined. Did you mean: 'get_distro_name'?

[Pirate Praveen]

Control: severity -1 important

On Mon, Jan 23 2023 at 04:57:16 PM +00:00:00 +00:00:00, Brian Potkin 
 wrote:

On Mon 23 Jan 2023 at 01:39:46 +0530, Pirate Praveen wrote:


 Package: hplip
 Version: 3.22.10+dfsg0-1
 Severity: grave
 Justification: makes it unusable

 $ hp-plugin

 HP Linux Imaging and Printing System (ver. 3.22.10)
 Plugin Download and Install Utility ver. 2.1

 Copyright (c) 2001-18 HP Development Company, LP
 This software comes with ABSOLUTELY NO WARRANTY.
 This is free software, and you are welcome to distribute it
 under certain conditions. See COPYING file for more details.


 HP Linux Imaging and Printing System (ver. 3.22.10)
 Plugin Download and Install Utility ver. 2.1

 Copyright (c) 2001-18 HP Development Company, LP
 This software comes with ABSOLUTELY NO WARRANTY.
 This is free software, and you are welcome to distribute it
 under certain conditions. See COPYING file for more details.

 QSocketNotifier: Can only be used with threads started with QThread
 Checking for network connection...
 Downloading plug-in from:
 Traceback (most recent call last):
   File "/usr/share/hplip/ui5/plugindialog.py", line 248, in
 NextButton_clicked
 status, download_plugin_file, error_str =
 
self.pluginObj.download(self.plugin_path,self.plugin_download_callback)


 
^^^
   File "/usr/share/hplip/installer/pluginhandler.py", line 257, in 
download

 core = core_install.CoreInstall()
^^
   File "/usr/share/hplip/installer/core_install.py", line 240, in 
__init__

 self.passwordObj = password.Password(ui_mode)
^^
   File "/usr/share/hplip/base/password.py", line 94, in __init__
 self.__readAuthType()  # self.__authType
 ^
   File "/usr/share/hplip/base/password.py", line 119, in 
__readAuthType

 distro_name = get_distro_std_name(os_name)
   ^^^
 NameError: name 'get_distro_std_name' is not defined. Did you mean:
 'get_distro_name'?
 Aborted


Thank you for you report, Pirate Praveen.

My attempt with

  sh -i hplip-3.22.10-plugin.run

failed over an ssh link. This is an upstream issue.
get_distro_std_name is not used in hplip-3.22.6.
Please report at

  https://bugs.launchpad.net/hplip/+bugs



If you are already familiar with launchpad, can you file it?


I would query the severity of grave rather than
imortant. Plugin files can be installed with

  sh hplip--plugin.run --tar vxf
  python3 installPlugin.py



Lowered severity to important. Though we probably have to document it 
somewhere more visible until this is fixed.



Regards,

Brian.

Processed: Re: Bug#1029459: hp-plugin crashes when trying to download plugin with error NameError: name 'get_distro_std_name' is not defined. Did you mean: 'get_distro_name'?

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1029459 [hplip] hp-plugin crashes when trying to download plugin with 
error NameError: name 'get_distro_std_name' is not defined. Did you mean: 
'get_distro_name'?
Severity set to 'important' from 'grave'

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

Bug#1029459: hp-plugin crashes when trying to download plugin with error NameError: name 'get_distro_std_name' is not defined. Did you mean: 'get_distro_name'?

[Brian Potkin]

On Mon 23 Jan 2023 at 01:39:46 +0530, Pirate Praveen wrote:

> Package: hplip
> Version: 3.22.10+dfsg0-1
> Severity: grave
> Justification: makes it unusable
> 
> $ hp-plugin
> 
> HP Linux Imaging and Printing System (ver. 3.22.10)
> Plugin Download and Install Utility ver. 2.1
> 
> Copyright (c) 2001-18 HP Development Company, LP
> This software comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to distribute it
> under certain conditions. See COPYING file for more details.
> 
> 
> HP Linux Imaging and Printing System (ver. 3.22.10)
> Plugin Download and Install Utility ver. 2.1
> 
> Copyright (c) 2001-18 HP Development Company, LP
> This software comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to distribute it
> under certain conditions. See COPYING file for more details.
> 
> QSocketNotifier: Can only be used with threads started with QThread
> Checking for network connection...
> Downloading plug-in from:
> Traceback (most recent call last):
>   File "/usr/share/hplip/ui5/plugindialog.py", line 248, in
> NextButton_clicked
> status, download_plugin_file, error_str =
> self.pluginObj.download(self.plugin_path,self.plugin_download_callback)
> 
> ^^^
>   File "/usr/share/hplip/installer/pluginhandler.py", line 257, in download
> core = core_install.CoreInstall()
>^^
>   File "/usr/share/hplip/installer/core_install.py", line 240, in __init__
> self.passwordObj = password.Password(ui_mode)
>^^
>   File "/usr/share/hplip/base/password.py", line 94, in __init__
> self.__readAuthType()  # self.__authType
> ^
>   File "/usr/share/hplip/base/password.py", line 119, in __readAuthType
> distro_name = get_distro_std_name(os_name)
>   ^^^
> NameError: name 'get_distro_std_name' is not defined. Did you mean:
> 'get_distro_name'?
> Aborted

Thank you for you report, Pirate Praveen.

My attempt with

  sh -i hplip-3.22.10-plugin.run

failed over an ssh link. This is an upstream issue.
get_distro_std_name is not used in hplip-3.22.6.
Please report at

  https://bugs.launchpad.net/hplip/+bugs

I would query the severity of grave rather than
imortant. Plugin files can be installed with

  sh hplip--plugin.run --tar vxf
  python3 installPlugin.py

Regards,

Brian.

  
 

Processed: Re: Bug#1029352: netcfg: broken ifupdown support for wireless interfaces

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1029352 [netcfg] netcfg: broken ifupdown support for wireless interfaces
Added tag(s) pending.

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

Bug#1029352: netcfg: broken ifupdown support for wireless interfaces

[Cyril Brulebois]

Control: tag -1 pending

Cyril Brulebois  (2023-01-21):
> I've pushed three commits in the pu/ifupdown+wireless branch:
>   
> https://salsa.debian.org/installer-team/netcfg/-/commits/pu/ifupdown+wireless

Updated branch:
  
https://salsa.debian.org/installer-team/netcfg/-/commits/pu/ifupdown+wireless-v2

> Commit links:
>  1. 
> https://salsa.debian.org/installer-team/netcfg/-/commit/9494d7ec02b32538db842d88c105db1ab2a6201b
>  2. 
> https://salsa.debian.org/installer-team/netcfg/-/commit/247056dbb22e6eacbea6348c5c9a6951eab948bd
>  3. 
> https://salsa.debian.org/installer-team/netcfg/-/commit/5ca665c6c26346e3c9c37c2df6366e8e5d718238

Updated commits, with changelog entries this time (no code change):
 1. 
https://salsa.debian.org/installer-team/netcfg/-/commit/aa62245f2960363f8b16f1f30d666936cc88bc83
 2. 
https://salsa.debian.org/installer-team/netcfg/-/commit/815cdfccaa5567fdf53594d47545d97c235de68e

Please note the third commit got moved to another branch:
  
https://salsa.debian.org/installer-team/netcfg/-/tree/pu/disable-hotplug-detection
  
https://salsa.debian.org/installer-team/netcfg/-/commit/9000be355b5e35134958c2655ec35bc75ba1b7e7

I suppose we can postpone wondering what to do about hotplug support
(netcfg currently believes everything is hotpluggable…) to a later time
(after bookworkm) given the broken “allow-hotplug” support at boot-up
(third issue) was an ifupdown regression in the end: #1022843.


My current plan includes more work on hw-detect; I'll upload netcfg with
commits from the ifupdown+wireless-v2 branch once I'm done (probably in
a few hours). Feedback regarding the netcfg commits is still very much
welcome (even after the upload, we can still tweak things before the
release).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#986070: closing 986070

[Emmanuel Bourg]

close 986070 
thanks

Green light for Kotlin and its dependencies in testing

Bug#1029509: marked as done (yq: /usr/bin/xq is already shipped by the xq package)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 16:55:48 +
with message-id 
and subject line Bug#1029509: fixed in yq 3.1.0-3
has caused the Debian Bug report #1029509,
regarding yq: /usr/bin/xq is already shipped by the xq package
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.)


-- 
1029509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yq
Version: 3.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package yq.
  Preparing to unpack .../13-yq_3.1.0-1_all.deb ...
  Unpacking yq (3.1.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-SyyrYV/13-yq_3.1.0-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/xq', which is also in package xq 1.0.0-2+b1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-SyyrYV/13-yq_3.1.0-1_all.deb


cheers,

Andreas


xq=1.0.0-2+b1_yq=3.1.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: yq
Source-Version: 3.1.0-3
Done: Christoph Martin 

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

Debian distribution maintenance software
pp.
Christoph Martin  (supplier of updated yq package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Jan 2023 17:28:55 +0100
Source: yq
Architecture: source
Version: 3.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Christoph Martin 
Closes: 1029509
Changes:
 yq (3.1.0-3) unstable; urgency=medium
 .
   * rename xq to xq-python (closes: #1029509)
Checksums-Sha1:
 61ac037e35aef2e8f1d64da8c4292a2af1be2d23 1949 yq_3.1.0-3.dsc
 2a75c87990b323df3ef00c730c5c8ae447d12c96 24948 yq_3.1.0.orig.tar.gz
 347e5ae458a0c5387f35844be00c77d0825a2793 2020 yq_3.1.0-3.debian.tar.xz
 22511255ec345170ad764b22b24141eb7156616b 8111 yq_3.1.0-3_amd64.buildinfo
Checksums-Sha256:
 ad6155813e10f605ef79edb636c48df59953c147fb49cb27d8774eaeb7f92abc 1949 
yq_3.1.0-3.dsc
 d34e9a34494ee248d9c6234dce631624892b4268da12f83b6aac19d84d001d29 24948 
yq_3.1.0.orig.tar.gz
 94c9116b8e2338b8f1f537fdc1e4ed5317c0afc9f98fa15e3aea2fb0517e8e14 2020 
yq_3.1.0-3.debian.tar.xz
 55511a152ad448a6e5fe6fb816a5ad51701dfd3892dc98aa83d1dc348de74331 8111 
yq_3.1.0-3_amd64.buildinfo
Files:
 e0501703e87d6826cc7b65207165bd1c 1949 utils optional yq_3.1.0-3.dsc
 046b38e860f8b2a888ef08f3e946ea91 24948 utils optional yq_3.1.0.orig.tar.gz
 e5db15d7fd3beb1fc14051c38024774e 2020 utils optional yq_3.1.0-3.debian.tar.xz
 caa9da8e90d155f84613503d41e49ff3 8111 utils optional yq_3.1.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEt1cFkfJ3DVbrq4cu7mlEXgxb5BcFAmPOtw0ACgkQ7mlEXgxb
5Bc8AQ//dRcnoEUKIiFh6KB3b1uBVsUgX7Kt0p6o1OUsg2qS3Md4Bqji1R+oBqGD
bJBFFcXTeYDJ2BoXD+bVijKxGghgvF3F94MeiPR/PxsptyUIqZ9UUr35WikJUISo
GV8KKcyfKqj+HIAjFXBhx7EJ2VVHw7Z41PmR5o2Xl+uNY2ha9rG7kzZKVetG9etj
6KtHv4BU/9JqZQAtlDmUnhpwJEfG5cpIWrEgEpmkitU67W8m6ja5ggDZooGTdSCo
EkZDhAz5tTE87jS01HghXEPs1P+tddFOHH5oFLeYjVW1Al7hfJoLNCJSBJ4ZQEwZ
MWAomUygmJlJotS6lnJBDYRYyurqjlT3wP5hDkIvxrlFVfTGDtIpa75t/r+P02GZ
y8/wkR6f7t77eS2FhO9QtBCvMti543sL6geQGMWH4TdznlD6t76iWAR/oZ5V8IOB
AJU+9WvNuzd9NUy8XnCuo1FfbOqJgoI4h5EjC6jjD5/pER87RxLXo3gXpiQ/cNJx
26a2ovEE/M0/gTbpUpGUIoUXKea0wuAVdjbWEkdNVKsRaEXzcZyHMBPDD/dERkAd
OUu0/fPCWTdDjlmLDOgukDmhJ/hxD4Z+UPcvrKYbYx/79Np+ZsmPKoGjmsDs4ci+
3hq4E4Xo18v9sun4zX1Dvdh8jEzCsvK2uS3fgLkcFGhxUpqHkwI=
=nTPI
-END PGP SIGNATURE End Message ---

Processed: closing 986070

[Debian Bug Tracking System]

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

> close 986070
Bug #986070 [protobuf2] protobuf2: unsuitable for release
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1020195: marked as done (elisp-bug-hunter: FTBFS: make: *** [debian/rules:4: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 16:20:13 +
with message-id 
and subject line Bug#1020195: fixed in elisp-bug-hunter 1.3.1+repack-6
has caused the Debian Bug report #1020195,
regarding elisp-bug-hunter: FTBFS: make: *** [debian/rules:4: binary] Error 25
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.)


-- 
1020195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: elisp-bug-hunter
Version: 1.3.1+repack-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with elpa
>dh_update_autotools_config
>dh_autoreconf
>dh_elpa_test
>   emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list 
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f 
> package-initialize -L . -l bug-hunter-test.el --eval 
> \(ert-run-tests-batch-and-exit\)
> Package cl is deprecated
> Running 6 tests (2022-09-17 20:04:00+, selector ‘t’)
> Doing some initial tests...
> Initial tests done. Hunting for the cause...
> Testing: 1/5
> Testing: 2/5
> Testing: 3/5
> Testing: 4/5
> Testing: 5/5
> nil, line 12 pos 90:
>   The following error was signaled here:
> (void-variable not-defined)
>   Caused by the following expression:
> not-defined
> 
> 
> Doing some initial tests...
> Initial tests done. Hunting for the cause...
> Testing: 1/5
> Testing: 2/5
> Testing: 3/5
> Testing: 4/5
> Testing: 5/5
> nil, line 12 pos 90:
>   The following error was signaled here:
> (void-variable not-defined)
>   Caused by the following expression:
> not-defined
> 
> 
> Doing some initial tests...
> Initial tests done. Hunting for the cause...
> Testing: 1/5
> Testing: 2/5
> Testing: 3/5
> Testing: 4/5
> Testing: 5/5
> nil, line 12 pos 90:
>   The following error was signaled here:
> (void-variable not-defined)
>   Caused by the following expression:
> not-defined
> 
> 
> Doing some initial tests...
> Initial tests done. Hunting for the cause...
> Testing: 1/5
> Testing: 2/5
> Testing: 3/5
> Testing: 4/5
> Testing: 5/5
> nil, line 12 pos 90:
>   The following error was signaled here:
> (void-variable not-defined)
>   Caused by the following expression:
> not-defined
> 
> 
> Doing some initial tests...
> Initial tests done. Hunting for the cause...
> Testing: 1/5
> Testing: 2/5
> Testing: 3/5
> Testing: 4/5
> Testing: 5/5
> nil, line 12 pos 90:
>   The following error was signaled here:
> (void-variable not-defined)
>   Caused by the following expression:
> not-defined
> 
> 
> Doing some initial tests...
> Initial tests done. Hunting for the cause...
> Testing: 1/5
> Testing: 2/5
> Testing: 3/5
> Testing: 4/5
> Testing: 5/5
> nil, line 12 pos 90:
>   The following error was signaled here:
> (void-variable not-defined)
>   Caused by the following expression:
> not-defined
> 
> 
> Doing some initial tests...
> Initial tests done. Hunting for the cause...
> Testing: 1/5
> Testing: 2/5
> Testing: 3/5
> Testing: 4/5
> Testing: 5/5
> nil, line 12 pos 90:
>   The following error was signaled here:
> (void-variable not-defined)
>   Caused by the following expression:
> not-defined
> 
> 
> Doing some initial tests...
> Initial tests done. Hunting for the cause...
> Testing: 1/5
> Testing: 2/5
> Testing: 3/5
> Testing: 4/5
> Testing: 5/5
> nil, line 12 pos 90:
>   The following error was signaled here:
> (void-variable not-defined)
>   Caused by the following expression:
> not-defined
> 
> 
> Doing some initial tests...
> Initial tests done. Hunting for the cause...
> Testing: 1/5
> Testing: 2/5
> Testing: 3/5
> Testing: 4/5
> Testing: 5/5
> nil, line 12 pos 90:
>   The following error was signaled here:
> (void-variable not-defined)
>   Caused by the following expression:
> not-defined
> 
> 
> Doing some initial tests...
> Initial tests done. Hunting for the cause...
> Testing: 1/5
> Testing: 2/5
> Testing: 3/5
> Testing: 4/5
> Testing: 5/5
> nil, line 12 pos 90:
>   The following error was signaled here:
> (void-variable not-defined)
>   Caused by the following expression:
> not-defined
> 
> 
> Doing some initial tests...
> Initial tests done. Hunting for the cause...
> Testing: 1/5
> Testing: 2/5
> Testing: 3/5
> Testing: 4/5
> Testing: 5/5
> nil, line 12 pos 90:
> 

Bug#1029031: marked as done (dcap: includes non-free source)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 16:20:01 +
with message-id 
and subject line Bug#1029031: fixed in dcap 2.47.13-1
has caused the Debian Bug report #1029031,
regarding dcap: includes non-free source
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.)


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

Source: dcap
Severity: serious
Version: 2.47.12-4

plugins/gssapi/gssIoTunnel.c has the following comment:

 *   Copyright (c) 2000,2001,2002 DESY Hamburg DMG-Division
 *   All rights reserved.
 *
 *   THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF
 * DESY Hamburg DMG-Division
 *
 * Copyright (c) 1997 - 2002 Kungliga Tekniska H�gskolan (Royal Institute of
 * Technology, Stockholm, Sweden). All rights reserved.

Please repack the source package to get rid of the file.
--- End Message ---
--- Begin Message ---
Source: dcap
Source-Version: 2.47.13-1
Done: Mattias Ellert 

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

Debian distribution maintenance software
pp.
Mattias Ellert  (supplier of updated dcap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Jan 2023 16:20:55 +0100
Source: dcap
Architecture: source
Version: 2.47.13-1
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert 
Changed-By: Mattias Ellert 
Closes: 1029031
Changes:
 dcap (2.47.13-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1029031)
   * Drop patches accepted upstream
   * Remove override_dh_strip rule (completed debug symbol migration)
Checksums-Sha1:
 15877e545daae0c861b0915f1803c6c4f46ab2d3 2232 dcap_2.47.13-1.dsc
 79b8bd156c81a5c5c6a177221203622d4f6dd754 193098 dcap_2.47.13.orig.tar.gz
 f636173a9163c408ce9cb4b048043d2f36750870 3924 dcap_2.47.13-1.debian.tar.xz
 23a88e932877fecd15e4896c7103d05b91eaec1d 10287 dcap_2.47.13-1_amd64.buildinfo
Checksums-Sha256:
 9ad874cce6267b69a5b51d37c1eef0fc0471dbcc3710f3e8fc74f882bfb2e6fc 2232 
dcap_2.47.13-1.dsc
 ae4a3845b7dd6bc32dc8ba445105e3ce72c1a25aa11da640404f63c89378876b 193098 
dcap_2.47.13.orig.tar.gz
 7ac376fec377d2bc749632ef4cf2948891c27a4883fa1e257fa4ee2365fc0bd2 3924 
dcap_2.47.13-1.debian.tar.xz
 6b7f6143ee14f039cf5f89461d7af73ad8e4d8621609e14dba0584920c5fafae 10287 
dcap_2.47.13-1_amd64.buildinfo
Files:
 f34a1939e5b41708ce44b7a9dadee822 2232 libs optional dcap_2.47.13-1.dsc
 2ea98fd14b956e20f176635d19be1c16 193098 libs optional dcap_2.47.13.orig.tar.gz
 3e603fb5a189427184af000c1697a41b 3924 libs optional 
dcap_2.47.13-1.debian.tar.xz
 1da62dcf1ead785a68f59c319dd7003c 10287 libs optional 
dcap_2.47.13-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6hgwr99NQxrZ4RRS6K7C/zvhqUsFAmPOrXcACgkQ6K7C/zvh
qUtoCRAAiIgsVgOXlQTz/bmUN8U+UPqTs1cuUDZG3Vk1Go+VxGRKABb3gS+hBVD5
nRtgFLrOTriPKwuFiRN9+Kx/DvQ6EP1Fo4E5Z88wIJZJ/jyjOdy90KNf3uLatyDr
BXPCwl41Al/PFH8rq79oF0JYs/PNugBOiYyAqN+yZ56WW8crcnuCLP4gm8wbM+CN
t9BMfffgavdwPwvPvo/IFh50bjwFCeg1DnuNGAP+dZ0HuSeQo/s5D4JTrzGlzeBq
RAAEhIbUg8yBMRZhSSatEWR+wh8GnDF3d7LRvvDtNm+HVhCgmSlV5ZmlWRmRPlTo
HEIsIIQP9f/ObjxT/kVmwccOwoUT51Gw1/hZFx8vYn0urb8/WELgVHd+FSi8l+GC
1m3YR04o4WwQSVHn4J78r/325WVvENAJgc/h5Lzz/f6PNx1f5AQSB4EEntk8DJps
oQNDDYkMAvGqLQBvVAtBcHEKcNx901b4P6U9X3o9IPp2zN41ruNLfi+YzU7Zvk08
j+uy5cy9J+4Ye7MZJjdCXBHaiGwDghLRHP6sVPMB3/c45XFfS7uVbi7DRvbZZU9i
SA0wu8G8bvieWIwSMVy52PcmyFFZxRFv2BUYGYo9RSsZKwiK/9fieB/QgnfG4OmD
6hV7n7AFeNNkLQ5MphoLuYNHo0MYAa91dknuBmgraatdDNiJbl8=
=ohA6
-END PGP SIGNATURE End Message ---

Bug#1029513: xss-lock: crashes with core dump on activation

[Stuart Freeman]

Package: xss-lock
Version: 0.3.0+git20220214.adafe4-2
Severity: grave
Justification: renders package unusable

Calling `xdg-screensaver activate` causes xss-lock to dump core.

Output of `systemctl --user status xss-lock:

× xss-lock.service - X Session Lock
 Loaded: loaded (/home/stuart/.config/systemd/user/xss-lock.service; 
enabled; preset: enabled)
 Active: failed (Result: core-dump) since Mon 2023-01-23 09:53:05 EST; 
3min 55s ago
   Duration: 17.084s
Process: 8434 ExecStart=xss-lock -s ${XDG_SESSION_ID} -n 
/usr/libexec/xsecurelock/dimmer -l -- xsecurelock (code=dumped, signal=ABRT)
   Main PID: 8434 (code=dumped, signal=ABRT)
CPU: 114ms

Jan 23 09:52:48 gamera systemd[1481]: Started X Session Lock.
Jan 23 09:52:48 gamera xss-lock[8434]: Error getting session: 
GDBus.Error:org.freedesktop.login1.NoSessionForPID: Caller does not belong to 
any known session.
Jan 23 09:53:05 gamera xss-lock[8434]: xss-lock: ./src/xss-lock.c:469: 
logind_session_set_locked_hint: Assertion `logind_session' failed.
Jan 23 09:53:05 gamera systemd-coredump[8576]: [🡕] Process 8434 (xss-lock) 
of user 1000 dumped core.

   Stack trace of thread 8434:
   #0  0x7f615a9d5ccc 
__pthread_kill_implementation (libc.so.6 + 0x8accc)
   #1  0x7f615a986ef2 
__GI_raise (libc.so.6 + 0x3bef2)
   #2  0x7f615a971472 
__GI_abort (libc.so.6 + 0x26472)
   #3  0x7f615a971395 
__assert_fail_base (libc.so.6 + 0x26395)
   #4  0x7f615a97fdf2 
__GI___assert_fail (libc.so.6 + 0x34df2)
   #5  0x55967f985ff7 n/a 
(xss-lock + 0x3ff7)
   #6  0x55967f9866cc n/a 
(xss-lock + 0x46cc)
   #7  0x55967f9868ee n/a 
(xss-lock + 0x48ee)
   #8  0x7f615abc767f 
g_main_context_dispatch (libglib-2.0.so.0 + 0x5467f)
   #9  0x7f615abc7a38 n/a 
(libglib-2.0.so.0 + 0x54a38)
   #10 0x7f615abc7cef 
g_main_loop_run (libglib-2.0.so.0 + 0x54cef)
   #11 0x55967f9857e2 main 
(xss-lock + 0x37e2)
   #12 0x7f615a97218a 
__libc_start_call_main (libc.so.6 + 0x2718a)
   #13 0x7f615a972245 
__libc_start_main_impl (libc.so.6 + 0x27245)
   #14 0x55967f985af1 
_start (xss-lock + 0x3af1)

   Stack trace of thread 8438:
   #0  0x7f615aa470af 
__GI___poll (libc.so.6 + 0xfc0af)
   #1  0x7f615abc79ae n/a 
(libglib-2.0.so.0 + 0x549ae)
   #2  0x7f615abc7acc 
g_main_context_iteration (libglib-2.0.so.0 + 0x54acc)
   #3  0x7f615abc7b11 n/a 
(libglib-2.0.so.0 + 0x54b11)
   #4  0x7f615abf1cfd n/a 
(libglib-2.0.so.0 + 0x7ecfd)
   #5  0x7f615a9d3fd4 
start_thread (libc.so.6 + 0x88fd4)
   #6  0x7f615aa5466c 
__clone3 (libc.so.6 + 0x10966c)
 Warning: The unit file, source configuration file 
or drop-ins of xss-lock.service changed on disk. Run 'systemctl --user 
daemon-reload' to reload units.

   Stack trace of thread 8440:
   #0  0x7f615aa470af 
__GI___poll (libc.so.6 + 0xfc0af)
   #1  0x7f615abc79ae n/a 
(libglib-2.0.so.0 + 0x549ae)
   #2  0x7f615abc7cef 
g_main_loop_run (libglib-2.0.so.0 + 0x54cef)
   #3  0x7f615ae23996 n/a 
(libgio-2.0.so.0 + 0x118996)
   #4  0x7f615abf1cfd n/a 
(libglib-2.0.so.0 + 0x7ecfd)
   #5  0x7f615a9d3fd4 
start_thread (libc.so.6 + 0x88fd4)
   #6  0x7f615aa5466c 
__clone3 (libc.so.6 + 0x10966c)
   ELF object binary 
architecture: AMD x86-64
Jan 23 09:53:05 gamera systemd[1481]: xss-lock.service: Main process 
exited

Processed: Re: Bug#1029507: linux-image-6.1.0-1-amd64 isn't installable

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 dkms
Bug #1029507 [src:linux] linux-image-6.1.0-1-amd64 isn't installable
Bug reassigned from package 'src:linux' to 'dkms'.
No longer marked as found in versions linux/6.1.4-1.
Ignoring request to alter fixed versions of bug #1029507 to the same values 
previously set
> forcemerge 1029063 -1
Bug #1029063 [dkms] dkms: linux-image-* remains unconfigured after dkms module 
build failure
Bug #1029388 [dkms] linux-image-6.1.0-2-amd64: system does not boot up when 
swap partion is a file
Bug #1029507 [dkms] linux-image-6.1.0-1-amd64 isn't installable
Severity set to 'grave' from 'normal'
Bug #1029388 [dkms] linux-image-6.1.0-2-amd64: system does not boot up when 
swap partion is a file
Merged 1029063 1029388 1029507

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

Bug#1022843: Bug#1029352: Bug#1022843: ifupdown: network down after systemctl restart

[Cyril Brulebois]

Hi Santiago,

Santiago Ruano Rincón  (2023-01-23):
> Thanks everybody for the inputs. I've applied Paul's solution, and the
> generated .deb can be downloaded from here:
> 
> https://salsa.debian.org/debian/ifupdown/-/jobs/3841392/artifacts/raw/debian/output/ifupdown_0.8.41~1.gbp3a6fae+salsaci+20230123+42_amd64.deb
> 
> Would it be possible for you (Oleg, Paul, Jeff, kibi et al.) to give it
> a try?

(Reading your mail with s/Paul/Pascal/g in mind.)

Tests yesterday seem to indicate successful results, but again I've only
tested a few combinations in a VM (to keep the feedback loop short).

From the installer team point of view, I'd welcome a swift upload with
this patch, possibly with urgency=high so that the fix reaches testing
soon. This will another blocker out of the way for the next D-I release!

Thanks!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1022843: Bug#1029352: Bug#1022843: ifupdown: network down after systemctl restart

[Santiago Ruano Rincón]

El 23/01/23 a las 00:24, Pascal Hambourg escribió:
> Oleg A. Arkhangelsky wrote:
> > Note that we have to use '--ignore-errors'. Otherwise if we have real
> > hotplug interface that is not present at the moment of restart, `ifup`
> > returns non-zero and systemd unit fail.
> 
> "--ignore-errors" marks missing interfaces as configured, so ifup will not
> configure them when invoked by udev. In order to not fail the systemd unit
> start on ifup error, you can prefix the command with "-".
> 
> On 22/01/2023 at 20:58, Cyril Brulebois wrote:
> > 
> > with an extra ens3 declared as auto, the following seems to work fine
> > for boot-up, stop and start, and restart:
> > 
> >  [Service]
> >  Type=oneshot
> >  EnvironmentFile=-/etc/default/networking
> >  ExecStart=/sbin/ifup -a --read-environment
> >  ExecStart=/bin/sh -c 'if [ -f /run/network/restart-hotplug ]; then 
> > /sbin/ifup -a --read-environment --allow=hotplug; fi'
> >  ExecStop=/sbin/ifdown -a --read-environment --exclude=lo
> >  ExecStopPost=/usr/bin/touch /run/network/restart-hotplug
> >  RemainAfterExit=true
> >  TimeoutStartSec=5min
> 
> That seems needlessly convoluted. What about this:
> 
> [Service]
> Type=oneshot
> EnvironmentFile=-/etc/default/networking
> ExecStart=/sbin/ifup -a --read-environment
> ExecStart=-/sbin/ifup -a --read-environment --allow=hotplug
> ExecStop=/sbin/ifdown -a --read-environment --exclude=lo
> RemainAfterExit=true
> TimeoutStartSec=5min
> 
> "start" and "restart" configure all existing "auto" and "allow-hotplug"
> interfaces.
> Missing "allow-hotplug" interfaces do not be marked as configured (so that
> they can be configured by udev) and do not make "start" or "restart" fail.

Thanks everybody for the inputs. I've applied Paul's solution, and the
generated .deb can be downloaded from here:

https://salsa.debian.org/debian/ifupdown/-/jobs/3841392/artifacts/raw/debian/output/ifupdown_0.8.41~1.gbp3a6fae+salsaci+20230123+42_amd64.deb

Would it be possible for you (Oleg, Paul, Jeff, kibi et al.) to give it
a try?

Cheers,

 -- S


signature.asc
Description: PGP signature

Bug#1029509: yq: /usr/bin/xq is already shipped by the xq package

[Andreas Beckmann]

Package: yq
Version: 3.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package yq.
  Preparing to unpack .../13-yq_3.1.0-1_all.deb ...
  Unpacking yq (3.1.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-SyyrYV/13-yq_3.1.0-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/xq', which is also in package xq 1.0.0-2+b1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-SyyrYV/13-yq_3.1.0-1_all.deb


cheers,

Andreas


xq=1.0.0-2+b1_yq=3.1.0-1.log.gz
Description: application/gzip

Bug#1029508: pnc: missing Breaks+Replaces: pn

[Andreas Beckmann]

Package: pnc
Version: 0.9.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../archives/pnc_0.9.4-1_amd64.deb ...
  Unpacking pnc (0.9.4-1) ...
  dpkg: error processing archive /var/cache/apt/archives/pnc_0.9.4-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/gawk/gawkpn.so', which is 
also in package pn 0.9.0-1+b3
  Errors were encountered while processing:
   /var/cache/apt/archives/pnc_0.9.4-1_amd64.deb

Since pnc is taking over pn, the Breaks+Replaces can be unversioned.

Please also file a RM bug for src:pn


cheers,

Andreas


pn=0.9.0-1+b3_pnc=0.9.4-1.log.gz
Description: application/gzip

Bug#1029503: spirv-cross: new upstream release breaks API

[Timo Röhling]

Source: spirv-cross
Version: 2021.01.15+1.3.236.0-1
Severity: serious
Tags: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear co-maintainers,

the recent upload of spirv-cross 2021.01.15+1.3.236.0-1 has incompatible
API changes which break reverse dependencies, notably src:filament.

This type of change is no longer appropriate since the 2023-01-12 transition 
freeze.
Please keep this bug at a RC-critical severity to prevent migration to
testing.


Relevant excerpt from a filament rebuild:

[...]
[ 50%] Built target test_utils
/<>/libs/filamat/src/GLSLPostProcessor.cpp:349:75: error: too few 
arguments to function call, expected 3, have 2
glslCompiler.remap_ext_framebuffer_fetch(i.first, i.second);
  ^
/usr/include/spirv_cross/spirv_glsl.hpp:203:7: note: 
'remap_ext_framebuffer_fetch' declared here
void remap_ext_framebuffer_fetch(uint32_t input_attachment_index, 
uint32_t color_location, bool coherent);
 ^
1 error generated.
make[3]: *** [libs/filamat/CMakeFiles/filamat.dir/build.make:331: 
libs/filamat/CMakeFiles/filamat.dir/src/GLSLPostProcessor.cpp.o] Error 1
[...]


Cheers
Timo


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmPOhI8ACgkQ+C8H+466
LVmO/QwAnyuW2b78PW1dGWP/S0uOn10R4Khg1vtayd6dG+d4DItcDYtiXQcB4p4a
1f9zJwnkB3PT2nvpXT29frqvOO9rz4JQ/fT68bEpjluRL3255MNRTjseTSiZRIFA
rBkmyflC1+5agaJhuQSH4FR7PkuSpnCKA4uTAuvQf4gYQEmeUGb8Exca2YKXVeK1
8iPTIDyvd8LUVJBhnp0O7d8j1XJXibzewuyEzivGoTGbNJ+PVoeBLSxx1BzOKT5C
2QEpy6Ji9tG9UIzm7AjqNdTwnQOejSXKWthQsyFx4QAgoIOv+ppv2PpZiQWSzgFY
CVy8ngQdS2k1uwCokAFperRS9XuoUT0EaR43jALpZ1ryfmSzmZrkGDMyZXaUFV9l
ubYMQpp/JBe9YfMV6M02kV45ihbXqHSUdK9QrwVnWGLZIwnoeLJbs+K0Jm/jpfY+
Qq7pVAtEt2Kr+LU0xkssuskKbyMeFvkLJcAXFJ3vI55/e8XgaiHMUJuwzzbnH9aj
NOfNqANT
=/4Kr
-END PGP SIGNATURE-

Processed: affects 1029503

[Debian Bug Tracking System]

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

> affects 1029503 src:filament
Bug #1029503 [src:spirv-cross] spirv-cross: new upstream release breaks API
Added indication that 1029503 affects src:filament
> thanks
Stopping processing here.

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

Bug#1029504: bat: /usr/bin/bat vs. /usr/sbin/bat in bacula-console-qt

[Andreas Beckmann]

Package: bat
Version: 0.22.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Undoing the bat/batcat rename was not a good idea: while src:bacula no
longer ships the (transitional) /usr/bin/bat -> /usr/sbin/bat symlink in
bacula-console-qt, it still has the /usr/sbin/bat binary (and its
bat.1.gz manpage which is now causing a file conflict) and thus src:bat
may not use the /usr/bin/bat filename.

(bacula-console-qt should probably better move the manpage to section 8
if the binary resides in sbin, but that is not the point here.)


Andreas

Bug#1008468: marked as done (ruby-jquery-atwho-rails: FTBFS: installing symlink 'lib/assets/javascripts/jquery.atwho/jquery.atwho.js' pointing to parent path /usr/share/javascript/jquery-atwho/jquery.

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 12:24:31 +
with message-id 
and subject line Bug#1008468: fixed in ruby-jquery-atwho-rails 1.5.4+dfsg-3
has caused the Debian Bug report #1008468,
regarding ruby-jquery-atwho-rails: FTBFS: installing symlink 
'lib/assets/javascripts/jquery.atwho/jquery.atwho.js' pointing to parent path 
/usr/share/javascript/jquery-atwho/jquery.atwho.js of 
/<>/debian/ruby-jquery-atwho-rails/usr/share/rubygems-integration/all/gems/jquery-atwho-rails-1.5.4
 is not allowed
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.)


-- 
1008468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-jquery-atwho-rails
Version: 1.5.4+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ln -sf /usr/share/javascript/jquery-atwho/jquery.atwho.js 
> /<>/lib/assets/javascripts/jquery.atwho/jquery.atwho.js
> ln -sf /usr/share/javascript/caret.js/jquery.caret.js 
> /<>/lib/assets/javascripts/jquery.atwho/jquery.caret.js
> dh_auto_configure
>   dh_ruby --configure
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=ruby
>   dh_ruby --build
>dh_ruby --build
>dh_auto_test -O--buildsystem=ruby
>   dh_ruby --test
>create-stamp debian/debhelper-build-stamp
>dh_testroot -O--buildsystem=ruby
>dh_prep -O--buildsystem=ruby
>dh_auto_install --destdir=debian/ruby-jquery-atwho-rails/ 
> -O--buildsystem=ruby
>   dh_ruby --install 
> /<>/ruby-jquery-atwho-rails-1.5.4\+dfsg/debian/ruby-jquery-atwho-rails
>dh_ruby --install
> /usr/bin/ruby3.0 -S gem build --config-file /dev/null --verbose 
> /tmp/d20220326-487327-2brvg7/gemspec
> Failed to load /dev/null because it doesn't contain valid YAML hash
> WARNING:  licenses is empty, but is recommended.  Use a license identifier 
> from
> http://spdx.org/licenses or 'Nonstandard' for a nonstandard license.
> WARNING:  lib/assets/javascripts/jquery.atwho/jquery.atwho.js is a symlink, 
> which is not supported on all platforms
> WARNING:  lib/assets/javascripts/jquery.atwho/jquery.caret.js is a symlink, 
> which is not supported on all platforms
> WARNING:  open-ended dependency on rspec (>= 0, development) is not 
> recommended
>   use a bounded requirement, such as '~> x.y'
> WARNING:  open-ended dependency on generator_spec (>= 0, development) is not 
> recommended
>   use a bounded requirement, such as '~> x.y'
> WARNING:  See https://guides.rubygems.org/specification-reference/ for help
>   Successfully built RubyGem
>   Name: jquery-atwho-rails
>   Version: 1.5.4
>   File: jquery-atwho-rails-1.5.4.gem
> /usr/bin/ruby3.0 -S gem install --config-file /dev/null --verbose --local 
> --verbose --no-document --ignore-dependencies --install-dir 
> debian/ruby-jquery-atwho-rails/usr/share/rubygems-integration/all 
> /tmp/d20220326-487327-2brvg7/jquery-atwho-rails-1.5.4.gem
> Failed to load /dev/null because it doesn't contain valid YAML hash
> ERROR:  While executing gem ... (Gem::Package::SymlinkError)
> installing symlink 'lib/assets/javascripts/jquery.atwho/jquery.atwho.js' 
> pointing to parent path /usr/share/javascript/jquery-atwho/jquery.atwho.js of 
> /<>/debian/ruby-jquery-atwho-rails/usr/share/rubygems-integration/all/gems/jquery-atwho-rails-1.5.4
>  is not allowed
> /<>/debian/ruby-jquery-atwho-rails/usr/share/rubygems-integration/all/gems/jquery-atwho-rails-1.5.4/lib/assets/javascripts/jquery.atwho/index.js
> /usr/lib/ruby/vendor_ruby/gem2deb.rb:54:in `run': /usr/bin/ruby3.0 -S gem 
> install --config-file /dev/null --verbose --local --verbose --no-document 
> --ignore-dependencies --install-dir 
> debian/ruby-jquery-atwho-rails/usr/share/rubygems-integration/all 
> /tmp/d20220326-487327-2brvg7/jquery-atwho-rails-1.5.4.gem 
> (Gem2Deb::CommandFailed)
>   from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:212:in `run_gem'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:120:in `block 
> in install_files_and_build_extensions'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:68:in `each'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:68:in 
> `install_files_and_build_extensions'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:28:in `install'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:86:in `block in 
> install'
>   

Bug#1027939: marked as done (clang-14 lost its (indirect) dependency on libclang-rt-14-dev)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 12:50:07 +
with message-id 
and subject line Bug#1027939: fixed in halide 14.0.0-3
has caused the Debian Bug report #1027939,
regarding clang-14 lost its (indirect) dependency on libclang-rt-14-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.)


-- 
1027939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clang-14
Version: 1:14.0.6-10~exp4
Severity: serious
Tags: ftbfs
Control: affects -1 src:halide

https://buildd.debian.org/status/fetch.php?pkg=halide&arch=amd64&ver=14.0.0-2%2Bb1&stamp=1672837458&raw=0

...
-- Check for working C compiler: /usr/bin/clang-14
-- Check for working C compiler: /usr/bin/clang-14 - broken
CMake Error at /usr/share/cmake-3.25/Modules/CMakeTestCCompiler.cmake:70 
(message):
  The C compiler

"/usr/bin/clang-14"

  is not able to compile a simple test program.

  It fails with the following output:

Change Dir: 
/<>/build/stage-0/halide/CMakeFiles/CMakeScratch/TryCompile-MA4jQl

Run Build Command(s):/usr/bin/ninja cmTC_6af5a && [1/2] Building C object 
CMakeFiles/cmTC_6af5a.dir/testCCompiler.c.o
clang: warning: -Wl,--build-id=sha1: 'linker' input unused 
[-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-fuse-ld=lld-14' 
[-Wunused-command-line-argument]
[2/2] Linking C executable cmTC_6af5a
FAILED: cmTC_6af5a 
: && /usr/bin/clang-14 -g -fdebug-default-version=4 -fprofile-generate 
-Xclang -mllvm -Xclang -vp-counters-per-site=10.0 -fuse-ld=lld-14 
-Wl,--build-id=sha1 -Wl,-z,relro CMakeFiles/cmTC_6af5a.dir/testCCompiler.c.o -o 
cmTC_6af5a   && :
ld.lld-14: error: cannot open 
/usr/lib/llvm-14/lib/clang/14.0.6/lib/linux/libclang_rt.profile-x86_64.a: No 
such file or directory
clang: error: linker command failed with exit code 1 (use -v to see 
invocation)
ninja: build stopped: subcommand failed.



  

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:2 (project)


-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: halide
Source-Version: 14.0.0-3
Done: Gianfranco Costamagna 

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

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

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated halide 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Jan 2023 13:19:16 +0100
Source: halide
Built-For-Profiles: noudeb
Architecture: source
Version: 14.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Roman Lebedev 
Changed-By: Gianfranco Costamagna 
Closes: 1027939
Changes:
 halide (14.0.0-3) unstable; urgency=medium
 .
   [ Gianfranco Costamagna ]
   * Team upload
 .
   [ James Addison ]
   * Add libclang-rt-14-dev build dependency (Closes: #1027939)
Checksums-Sha1:
 168b3de05b4d793b5478d6d86a26e9db31f8c30c 2664 halide_14.0.0-3.dsc
 47989289caaa2fe1992e6513ad293ad303131600 292784 halide_14.0.0-3.debian.tar.xz
 e69ce115df0e2139ce68c49264a18fdf25e0e53b 11636 halide_14.0.0-3_source.buildinfo
Checksums-Sha256:
 2e59fef78cbbe614ef51bdff2075d05c2fbde24fc05b907631e2f7d61e8e7630 2664 
halide_14.0.0-3.dsc
 2f6daf8b957dfa215128e2db1009dca1fd24b3ba771aa433ec249710e13755eb 292784 
halide_14.0.0-3.debian.tar.xz
 225faef33211cdb6edee04cba3f10e8fe6fe1e9e45d9c5a180caa9b56bf53f47 11636 
halide_14.0.0-3_source.buildinfo
Files:
 3411e83c3027aad173c51d6d1ced29db 2664 devel optional halide_14.0.0-3.dsc
 2d98e3969df47ffd73fae7373b0527f5 292784 devel optional 
halide_14.0.0-3.debian.tar.xz
 ed2ffa372fa85d1af940989c1b2aa032 11636 devel optional 
halide_14.0.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmPOe4wACgkQ808JdE6f
XdmA8w/9GmncCvae12CR0mj+DxTSjW2Wf/XnF9RmARv/LGupScy3hr5oCXSFRXBi
GgLIEGlqoFx0WXYYpRI5DeHZXkTLTu/bD8QdYsz1q7zncNZ9S60ZXYXHVm+5fuv3
1xL8FvXx063p2SUkh8UFjJ1Q7Oi7WubV99GM57TCvyb4AT8yjEQJDGF6VEZtO1gz
agDgFbDAK87JPRsR

Processed: Re: Bug#1028324: RM: cduce -- RoQA, unmaintained, FTBFS, zero popcon

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #1028324 [src:cduce] RM: cduce -- RoQA, unmaintained, FTBFS, zero popcon
Bug reassigned from package 'src:cduce' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #1028324 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1028324 to the same values 
previously set

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

Bug#1028324: RM: cduce -- RoQA, unmaintained, FTBFS, zero popcon

[Stéphane Glondu]

Control: reassign -1 ftp.debian.org

Le 09/01/2023 à 16:37, Tobias Frost a écrit :

This makes me wonder if we should retire this package.


Yes, absolutely.


If you also think that it shoulw be removed, just reassign it to the
ftp.debian.org pseudo package.



Cheers,

--
Stéphane

Bug#1028869: marked as done (pyml: FTBFS: make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 12:01:02 +
with message-id 
and subject line Bug#1028869: fixed in pyml 20220905-1
has caused the Debian Bug report #1028869,
regarding pyml: FTBFS: make[1]: *** [debian/rules:22: override_dh_auto_test] 
Error 1
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dune runtest -p pyml
>  numpy_tests alias runtest
> Environment variables:
> PATH=/<>/_build/install/default/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> PYTHONHOME not set
> DYLD_LIBRARY_PATH not set
> DYLD_FALLBACK_LIBRARY_PATH not set
> Initializing library...
> Temporary set 
> PYTHONPATH=":/usr/lib/python311.zip:/usr/lib/python3.11:/usr/lib/python3.11/lib-dynload:/usr/local/lib/python3.11/dist-packages:/usr/lib/python3/dist-packages".
> Trying to load "/usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0".
> Library "/usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0" has been loaded.
> platform: linux
> build info: main, Dec 31 2022, 10:23:59
> Not a debug build.
> Starting tests...
> Test 'of_bigarray' ... disabled: numpy is not available
> Test 'of_bigarray2' ... disabled: numpy is not available
> Test 'to_bigarray' ... disabled: numpy is not available
> Test 'to_bigarray2' ... disabled: numpy is not available
> Test 'to_bigarray invalid type' ... disabled: numpy is not available
>   pyml_tests alias runtest (got signal SEGV)
> (cd _build/default && ./pyml_tests.exe)
> Environment variables:
> PATH=/<>/_build/install/default/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> PYTHONHOME not set
> DYLD_LIBRARY_PATH not set
> DYLD_FALLBACK_LIBRARY_PATH not set
> Initializing library...
> Temporary set 
> PYTHONPATH=":/usr/lib/python311.zip:/usr/lib/python3.11:/usr/lib/python3.11/lib-dynload:/usr/local/lib/python3.11/dist-packages:/usr/lib/python3/dist-packages".
> Trying to load "/usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0".
> Library "/usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0" has been loaded.
> platform: linux
> build info: main, Dec 31 2022, 10:23:59
> Not a debug build.
> Starting tests...
> Test 'version' ... Python version 3.11.1 (main, Dec 31 2022, 10:23:59) [GCC 
> 12.2.0]
> passed
> Test 'library version' ... Python library version 3.11.1 (main, Dec 31 2022, 
> 10:23:59) [GCC 12.2.0]
> passed
> Test 'hello world' ... passed
> Test 'class' ... passed
> Test 'empty tuple' ... passed
> Test 'make tuple' ... passed
> Test 'module get/set/remove' ... passed
> Test 'capsule' ... passed
> Test 'capsule-conversion-error' ... passed
> Test 'exception' ... passed
> Test 'ocaml exception' ... passed
> Test 'ocaml exception with traceback' ... passed
> Test 'restore with null' ... passed
> Test 'ocaml other exception' ... passed
> Test 'run file with filename' ... passed
> Test 'run file with channel' ... passed
> Test 'boolean' ... 
> make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/pyml_20220325-1_unstable.log

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

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

If you reassign this bug to another package, please 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: pyml
Source-Version: 20220905-1
Done: Stéphane Glondu 

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

Bug#964607: Massive update necessary

[Pirate Praveen]

On Thu, 25 Nov 2021 18:54:24 +0100 Daniel Leidert  
wrote:
> This gem is out-of-date. Upstream is at 3.2.2, which requires 
packaging for
> google-cloud-translate-v2 and google-cloud-translate-v3 and updating 
google-

> cloud-core to >= 1.6. The tests require packageing google-style.

This is a leaf package, likely packaged for loomio. I think we can 
ignore this for bookworm. May be we should use a usertag to mark such 
packages which can ignore rc bugs for bookworm (it could be useful in 
future if loomio packaging is revived, since upstream is still active, 
we can probably keep it in unstable).

Processed: Bug#1008468 marked as pending in ruby-jquery-atwho-rails

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008468 [src:ruby-jquery-atwho-rails] ruby-jquery-atwho-rails: FTBFS: 
installing symlink 'lib/assets/javascripts/jquery.atwho/jquery.atwho.js' 
pointing to parent path /usr/share/javascript/jquery-atwho/jquery.atwho.js of 
/<>/debian/ruby-jquery-atwho-rails/usr/share/rubygems-integration/all/gems/jquery-atwho-rails-1.5.4
 is not allowed
Added tag(s) pending.

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

Bug#1008468: marked as pending in ruby-jquery-atwho-rails

[Praveen Arimbrathodiyil]

Control: tag -1 pending

Hello,

Bug #1008468 in ruby-jquery-atwho-rails 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/ruby-team/ruby-jquery-atwho-rails/-/commit/d5a92ae76665588545aee0af4a93850431af8c91


Copy assets during build instead of symlink (Closes: #1008468)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008468

Processed: Re: Bug#1025985: glosstext: FTBFS: LaTeX Error: File `pdftexcmds.sty' not found.

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:glosstex
Bug #1025985 [texlive-latex-base] hypdoc.sty requires pdftexcmds.sty that is in 
texlive-latex-extra
Added indication that 1025985 affects src:glosstex

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

Bug#1025985: glosstext: FTBFS: LaTeX Error: File `pdftexcmds.sty' not found.

[Hilmar Preuße]

Control: affects -1 src:glosstex

Bug#1028868: marked as done (yara: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 10:54:21 +
with message-id 
and subject line Bug#1028868: fixed in yara 4.2.3-4
has caused the Debian Bug report #1028868,
regarding yara: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 
--verbose" VERBOSE=1 returned exit code 2
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.)


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

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>'
> PASS: test-alignment
> PASS: test-arena
> PASS: test-version
> PASS: test-atoms
> PASS: test-bitmask
> PASS: test-stack
> PASS: test-re-split
> PASS: test-async
> PASS: test-elf
> PASS: test-math
> FAIL: test-magic
> PASS: test-dotnet
> PASS: test-dex
> PASS: test-macho
> PASS: test-pe
> PASS: test-api
> PASS: test-exception
> PASS: test-rules
> ==
>yara 4.2.3: ./test-suite.log
> ==
> 
> # TOTAL: 18
> # PASS:  17
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: test-magic
> 
> 
> tests/test-magic.c:24: rule does not match (but should)
> FAIL test-magic (exit status: 1)
> 
> 
> Testsuite summary for yara 4.2.3
> 
> # TOTAL: 18
> # PASS:  17
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See ./test-suite.log
> Please report to vmalva...@virustotal.com
> 
> make[4]: *** [Makefile:1316: test-suite.log] Error 1
> make[4]: Leaving directory '/<>'
> make[3]: *** [Makefile:1424: check-TESTS] Error 2
> make[3]: Leaving directory '/<>'
> make[2]: *** [Makefile:1787: check-am] Error 2
> make[2]: Leaving directory '/<>'
> make[1]: *** [Makefile:1201: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 
> returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/yara_4.2.3-3_unstable.log

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

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

If you reassign this bug to another package, please 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: yara
Source-Version: 4.2.3-4
Done: Hilko Bengen 

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated yara package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Jan 2023 09:28:13 +0100
Source: yara
Architecture: source
Version: 4.2.3-4
Distribution: unstable
Urgency: high
Maintainer: Debian Security Tools 
Changed-By: Hilko Bengen 
Closes: 1028868
Changes:
 yara (4.2.3-4) unstable; urgency=high
 .
   * Fix debian/watch
   * Fix test-magic patch (Closes: #1028868)
Checksums-Sha1:
 1487b6476a4f2107e4aab2c

Bug#1026103: marked as done (aflplusplus: FTBFS on s390x)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 10:49:23 +
with message-id 
and subject line Bug#1026103: fixed in aflplusplus 4.04c-3
has caused the Debian Bug report #1026103,
regarding aflplusplus: FTBFS on s390x
to be marked as done.

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

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


-- 
1026103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aflplusplus
Version: 4.04c-2
Severity: serious

Hi,

Your package is failing to build on s390x:
[*] Compiling afl++ for OS Linux on ARCH s390x
./test/unittests/unit_maybe_alloc
[==] Running 6 test(s).
[ RUN  ] test_pow2
[   OK ] test_pow2
[ RUN  ] test_null_allocs
[   OK ] test_null_allocs
[ RUN  ] test_nonpow2_size
[   OK ] test_nonpow2_size
[ RUN  ] test_zero_size
[   OK ] test_zero_size
[ RUN  ] test_unchanged_size
[   OK ] test_unchanged_size
[ RUN  ] test_grow_multiple
[   OK ] test_grow_multiple
[==] 6 test(s) run.
[  PASSED  ] 6 test(s).
./test/unittests/unit_preallocable
[==] Running 2 test(s).
[ RUN  ] test_alloc_free
[   OK ] test_alloc_free
[ RUN  ] test_prealloc_overflow
[   OK ] test_prealloc_overflow
[==] 2 test(s) run.
[  PASSED  ] 2 test(s).
./test/unittests/unit_list
[==] Running 3 test(s).
[ RUN  ] test_contains
[   OK ] test_contains
[ RUN  ] test_foreach
[   OK ] test_foreach
[ RUN  ] test_long_list
[   OK ] test_long_list
[==] 3 test(s) run.
[  PASSED  ] 3 test(s).
./test/unittests/unit_rand
[==] Running 2 test(s).
[ RUN  ] test_rand_0
[   OK ] test_rand_0
[ RUN  ] test_rand_below
[   OK ] test_rand_below
[==] 2 test(s) run.
[  PASSED  ] 2 test(s).
./test/unittests/unit_hash
[==] Running 1 test(s).
[ RUN  ] test_hash
[   OK ] test_hash
[==] 1 test(s) run.
[  PASSED  ] 1 test(s).
make[3]: Leaving directory '/<>'
␛[1;90m[*] 10 test cases completed.␛[0m
␛[1;93m[-] not all test cases were executed
␛[0;31m[!] failure in tests :-(␛[0m
make[2]: *** [GNUmakefile:343: tests] Error 1

It's not at all clear why it says: "failure in tests". All the test seem
to pass. Other architectures also have the "not all test cases were
executed" message.

I've tried to build it again on the buildds, but it failed the same way.


Kurt
--- End Message ---
--- Begin Message ---
Source: aflplusplus
Source-Version: 4.04c-3
Done: Sophie Brun 

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

Debian distribution maintenance software
pp.
Sophie Brun  (supplier of updated aflplusplus 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Jan 2023 10:58:26 +0100
Source: aflplusplus
Architecture: source
Version: 4.04c-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Sophie Brun 
Closes: 1026103
Changes:
 aflplusplus (4.04c-3) unstable; urgency=medium
 .
   * Disable lld support on s390x for now (Closes: #1026103). Thanks to
 Gianfranco Costamagna
Checksums-Sha1:
 0f154385d5721c8db617c7b4e0c61e5b94b1caaa 2496 aflplusplus_4.04c-3.dsc
 85ebc17b9a144620cd675c67535bac0f1dfe5230 10412 
aflplusplus_4.04c-3.debian.tar.xz
 a227f70c7ed3c0e7bd091a90cae76e9e3269b955 8813 
aflplusplus_4.04c-3_source.buildinfo
Checksums-Sha256:
 488a91291b25032b301202b1f2943e7f6181bfe4fb7b14e47a24d18d1c6acf48 2496 
aflplusplus_4.04c-3.dsc
 2f9f367209728e4c09e97120a7b169a5877ac3e55d4d7b7fe187522966e08dac 10412 
aflplusplus_4.04c-3.debian.tar.xz
 4a2c82c1ea2cc9b227607e0d4bfdf1dbcc0dad97f42281df5313ffad118cfbbe 8813 
aflplusplus_4.04c-3_source.buildinfo
Files:
 b3bcdf2961f07b9db84d5c402b7c6b02 2496 devel optional aflplusplus_4.04c-3.dsc
 3988e16e31f1aec9c589cc5c29c6e3a2 10412 devel optional 
aflplusplus_4.04c-3.debian.tar.xz
 cfd9b0643fea6b2c1ba2f5b08a2f00fc 8813 devel optional 
aflplusplus_4.04c-3_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Sophie Brun

iQIzBAEBCgAdFiEEOyG45orlwW+H9TItV5J4OyBv7jAFAmPOXTYACgkQV5J4OyBv
7

Bug#1029310: marked as done (src:r-cran-bayesplot: fails to migrate to testing for too long: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 10:52:21 +
with message-id 
and subject line Bug#1029310: fixed in r-cran-bayesplot 1.10.0-3
has caused the Debian Bug report #1029310,
regarding src:r-cran-bayesplot: fails to migrate to testing for too long: 
autopkgtest regression
to be marked as done.

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

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


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

Source: r-cran-bayesplot
Version: 1.9.0-1
Severity: serious
Control: close -1 1.10.0-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:r-cran-bayesplot has been trying to 
migrate for 61 days [2]. Hence, I am filing this bug. Your package fails 
its own autopkgtest if the package from unstable is installed in 
testing. A very quick glance suggests that it's just a missing 
*versioned* (test) dependency as I see it pass in unstable on armel (I 
scheduled the other archs too just now).


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


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


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


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=r-cran-bayesplot



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-bayesplot
Source-Version: 1.10.0-3
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-bayesplot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Jan 2023 11:02:49 +0100
Source: r-cran-bayesplot
Architecture: source
Version: 1.10.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1029310
Changes:
 r-cran-bayesplot (1.10.0-3) unstable; urgency=medium
 .
   * Skip 8 tests failing in connection with ggplot2
 Closes: #1029310
Checksums-Sha1:
 32cb4d8fbc0173224ec2e20bc2db66f784283457 2521 r-cran-bayesplot_1.10.0-3.dsc
 4bfc65ffed851b98a50661c7f2fe885130c07b31 4228 
r-cran-bayesplot_1.10.0-3.debian.tar.xz
 f780eaf268d408d473a8b171e75b33fab9ef04ef 11922 
r-cran-bayesplot_1.10.0-3_amd64.buildinfo
Checksums-Sha256:
 be41c8012255000a11655f72ec460afebafe5b8fecf8e131cbb33959e478698e 2521 
r-cran-bayesplot_1.10.0-3.dsc
 dd7488c9c0d1b314d3a024c3c8960e0e2930f3efa4d607470ceaa7f89dc122d0 4228 
r-cran-bayesplot_1.10.0-3.debian.tar.xz
 a5b26c690143172114e27e23a47cbc5e3b32ba6fadbe3918a1cdc56d7c291507 11922 
r-cran-bayesplot_1.10.0-3_amd64.buildinfo
Files:
 d9d6af649a742d720dbe15e424bbc2ea 2521 gnu-r optional 
r-cran-bayesplot_1.10.0-3.dsc
 333784e26165aa07386b97cf9f2b797e 4228 gnu-r optional 
r-cran-bayesplot_1.10.0-3.debian.tar.xz
 46600ba9166f6552d9d9003d7cbebc42 11922 gnu-r optional 
r-cran-bayesplot_1.10.0-3_amd64.buildinfo

-BEGIN

Bug#1028181: marked as done (runit-init makes the system unbootable)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 10:52:56 +
with message-id 
and subject line Bug#1028181: fixed in runit 2.1.2-53
has caused the Debian Bug report #1028181,
regarding runit-init makes the system unbootable
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.)


-- 
1028181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: runit-init
Version: 2.1.2-52
Severity: grave
Justification: makes the system unbootable

Hi,

in order to investigate runit-init as a possible init alternative, I
tried booting a minimal Debian system containing runit-init and a linux
kernel image. This is what I got:

| Begin: Running /scripts/local-bottom ... done.
| Begin: Running /scripts/init-bottom ... done.
| [1.518637] Not activating Mandatory Access Control as /sbin/tomoyo-init 
does not exist.
| - runit: $Id: 25da3b86f7bed4038b8a039d2f8e8c9bbcf0822b $: booting.
| - runit: enter stage: /etc/runit/1
| /etc/rcS.d/S01mountkernfs.sh: 280: mount: not found
| /etc/rcS.d/S01mountkernfs.sh: 280: mount: not found
| /etc/rcS.d/S01mountkernfs.sh: 280: mount: not found
| Starting hotplug events dispatcher: systemd-udevd.
| Synthesizing the initial hotplug events (subsystems)...done.
| Synthesizing the initial hotplug events (devices)...[1.752098] input: 
Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
| done.
| Waiting for /dev to be fully populated...[1.763554] sr 1:0:0:0: Attached 
scsi generic sg0 type 5
| [1.766920] ACPI: button: Power Button [PWRF]
| [2.180257] RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 
10737418240 ms ovfl timer
| [2.196663] cryptd: max_cpu_qlen set to 1000
| [2.284932] AVX2 version of gcm_enc/dec engaged.
| [2.286968] AES CTR mode by8 optimization enabled
| done.
| /etc/rcS.d/S03mountdevsubfs.sh: 280: mount: not found
| Activating swap...failed.
| /etc/rcS.d/S04checkroot.sh: 210: mount: not found
| Cannot check root file system because it is not mounted read-only. ... failed!
| /etc/rcS.d/S04checkroot.sh: 316: mount: not found
| Creating compatibility symlink from /etc/mtab to /proc/mounts. ... (warning).
| /etc/init.d/mountkernfs.sh: 289: mount: not found
| /etc/init.d/mountkernfs.sh: 289: mount: not found
| /etc/init.d/mountkernfs.sh: 289: mount: not found
| /etc/init.d/mountdevsubfs.sh: 289: mount: not found
| Checking file systems...fsck: cannot check /dev/vda: fsck.ext4 not found
| done.
| Cleaning up temporary files... /tmp.
| Mounting local filesystems.../etc/rcS.d/S07mountall.sh: 35: mount: not found
| failed.
| Activating swapfile swap, if any...done.
| /etc/rcS.d/S07mountall.sh: 280: mount: not found
| /etc/rcS.d/S07mountall.sh: 280: mount: not found
| Cleaning up temporary files
| Cleaning up temporary files
| - runit: leave stage: /etc/runit/1
| - runit: enter stage: /etc/runit/2
| /etc/runit/2: 8: mount: not found
| runsvchdir: default: current.

The biggest problem here is the lack of mount. mount is not essential
and nothing depends on it, so it goes missing. Something in the runit
ecosystem should definitely depend on mount.

Then after boot, no getty is spawned and there is no way to log in.

I retried with mount installed and got something different:

| Begin: Running /scripts/local-bottom ... done.
| Begin: Running /scripts/init-bottom ... done.
| [1.554225] Not activating Mandatory Access Control as /sbin/tomoyo-init 
does not exist.
| - runit: $Id: 25da3b86f7bed4038b8a039d2f8e8c9bbcf0822b $: booting.
| - runit: enter stage: /etc/runit/1
| Starting hotplug events dispatcher: systemd-udevd.
| Synthesizing the initial hotplug events (subsystems)...done.
| Synthesizing the initial hotplug events (devices)...done.
| Waiting for /dev to be fully populated...[1.770569] input: Power Button 
as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
| [1.783674] sr 1:0:0:0: Attached scsi generic sg0 type 5
| [1.796417] ACPI: button: Power Button [PWRF]
| [2.151984] RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 
10737418240 ms ovfl timer
| [2.155414] cryptd: max_cpu_qlen set to 1000
| [2.287889] AVX2 version of gcm_enc/dec engaged.
| [2.290906] AES CTR mode by8 optimization enabled
| done.
| Activating swap...done.
| [3.003917] EXT4-fs (vda): re-mounted. Quota mode: none.
| Checking root file system...fsck: error 2 (No such file or directory) while 
executing fsck.ext4 for /dev/vda
| fsck exited with status code 8
| failed (code 8).
| An automatic file system check (fsck) of the root filesystem failed.
| A manual fsck must be pe

Bug#1021969: marked as done (ospd-openvas: Cannot fulfill the build dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 10:32:23 +
with message-id 
and subject line Bug#1021969: fixed in ospd-openvas 22.4.2-1
has caused the Debian Bug report #1021969,
regarding ospd-openvas: Cannot fulfill the 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.)


-- 
1021969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ospd-openvas
Version: 21.4.4-1.1
Severity: serious
Tags: ftbfs

The following packages have unmet dependencies:
 builddeps:ospd-openvas : Depends: python3-ospd (>= 21.4.1)


Source: ospd-openvas
Build-Depends: python3-ospd (>= 21.4.1)

Package: ospd-openvas
Provides: python3-ospd

It does not seem to be intentional that the package build depends
on itself, and even less that this build dependency cannot be
fulfilled due to the non-versioned Provides.
--- End Message ---
--- Begin Message ---
Source: ospd-openvas
Source-Version: 22.4.2-1
Done: Sophie Brun 

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

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

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

Debian distribution maintenance software
pp.
Sophie Brun  (supplier of updated ospd-openvas 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Jan 2023 10:34:13 +0100
Source: ospd-openvas
Architecture: source
Version: 22.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Sophie Brun 
Closes: 1021969
Changes:
 ospd-openvas (22.4.2-1) unstable; urgency=medium
 .
   * New upstream version 22.4.0
   * Update debian/copyright
   * Refresh patch
   * Bump Standards-Version to 4.6.1 (no change)
   * Add missing depends python3-gnupg and python3-paho-mqtt
   * Remove python3-ospd from build-dep (Closes: #1021969)
   * Add missing build-dep python3-defusedxml and python3-lxml
   * Remove copy of license
   * Update minimal required version of openvas-scanner
   * New upstream version 22.4.2
Checksums-Sha1:
 1e100b740e69e5709f889801ac9935e8ad0a6675 2304 ospd-openvas_22.4.2-1.dsc
 08b61cf093a6597a5d8d91f0eb1371f657106514 246856 ospd-openvas_22.4.2.orig.tar.gz
 9028f62c14d28ac8af75f65eea91666d85edac00 14844 
ospd-openvas_22.4.2-1.debian.tar.xz
 b0371f6851b67da1ab2bebf81e376e01c48622c8 7837 
ospd-openvas_22.4.2-1_source.buildinfo
Checksums-Sha256:
 4c4f1b04ed72c4f4ee762bb95dead86b05dcd2c4fba34c8a2a0a597281f06ad1 2304 
ospd-openvas_22.4.2-1.dsc
 0ccd170cf9053311903173fe2b22d317725baf8d24439337afa849423e2a97d8 246856 
ospd-openvas_22.4.2.orig.tar.gz
 ef643bb72246bffead19a8f20506b1f56b70d448ef073582208c965cbaaa6fbd 14844 
ospd-openvas_22.4.2-1.debian.tar.xz
 149ef88b3f69789c083d9516dbf52b72ca557ab2298255bec0c7107168303bb3 7837 
ospd-openvas_22.4.2-1_source.buildinfo
Files:
 d4d287b92e72a9a36238c52d0f66dc55 2304 admin optional ospd-openvas_22.4.2-1.dsc
 3d140c25cca7ff6c2bbff1098be4ab0b 246856 admin optional 
ospd-openvas_22.4.2.orig.tar.gz
 3aa1d377253a23b30e7c8b20b67a77c6 14844 admin optional 
ospd-openvas_22.4.2-1.debian.tar.xz
 a97624e4e05219c6fbc4dd0bcf2319e5 7837 admin optional 
ospd-openvas_22.4.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Sophie Brun

iQIzBAEBCgAdFiEEOyG45orlwW+H9TItV5J4OyBv7jAFAmPOVTEACgkQV5J4OyBv
7jBqOg/+JFm3NhDo92HCxbOYY5imlORt+UCVm5Vf2f2LyPK+3uYWGkV7UmjjwCqN
4Iy86zeaTvwQbh5530U4zb/Jo9YcLlzvcY3rMOQLXioEfO+yf2AmkTxVkp/VpTlr
L4fPU34hFnYqOpZa1WfXxZBQzj0BWBHEDsSO4jB/xT20Dn7/FU4PdH03R3rgGQh1
Iysj2+OhnI9N1wZ+/cz3r80bIWIsJRHDR8Nh5Ynop7uPrVjYBGkvt0hWS+eVJ9NK
C0xyLAIvmKw3qlEjkrXnJY5qbacd/K64G9HACVdZ9LFKb83ppPvqV46LfpWoHHPq
XS7dB5N2L5NhnZITHpOiPToc3e870fTB8V6c5FBC4O/Eq9/juYqPnuU0UeM8Ojnm
/UE0kmk08H8zRR4UHeye+pZvEP3j3kzxiIhmq8xbSnKCFFvH+YQGdYEOsDW1Nt41
kY5dIQDu07un6Ihs5PmHsSNkhLSY2+udM/tt+qKWXPYTkIhENaCLseH5ZAYFcAsJ
s+38RWEk144OBYF4ifUeFcXJOZgiVJj0ZHjA569KZgfPuUbwLEmpy/lFsC9FBkwC
hy1mxn813gAIaUnV0KuTOHL/5GnJi3hLSDk0yZo1ObzHLn0zN6joEY3IeSvQTveb
LP+aob6v9K7fsetUXqjvLusBXj8/qVf9+3NV4yUvL6KQVnlU5yI=
=Qfev
-END PGP SIGNATURE End Message ---

Bug#1029481: marked as done (yq: unmodified incorrect package description from debmake template)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 11:21:50 +0100
with message-id 
and subject line fixed with version 3.1.0-2
has caused the Debian Bug report #1029481,
regarding yq: unmodified incorrect package description from debmake template
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.)


-- 
1029481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yq
Version: 3.1.0-1
Severity: serious

The current description of the yq package is rather bogus.
It appears that the debmake template was not modified.

   $ apt-cache show yq | grep-dctrl -s Description-en .
   Description-en: auto-generated package by debmake
This Debian binary package was auto-generated by the
debmake(1) command provided by the debmake package.

   $ chronic apt source -qq yq
   $ head -n1 yq*/README*
   yq: Command-line YAML/XML/TOML processor - jq wrapper for YAML, XML, TOML 
documents
   
   $ dgrep -A5 'auto-generated' debmake
   /usr/lib/python3/dist-packages/debmake/control.py:desc = 
"auto-generated package by debmake"
   /usr/lib/python3/dist-packages/debmake/control.py-#
   /usr/lib/python3/dist-packages/debmake/control.py-if 
para["desc_long"].rstrip():
   /usr/lib/python3/dist-packages/debmake/control.py-desc_long = 
para["desc_long"].rstrip()
   /usr/lib/python3/dist-packages/debmake/control.py-elif 
para["desc"].strip():
   /usr/lib/python3/dist-packages/debmake/control.py-desc_long = " " + 
para["desc"].strip()
   --
   /usr/lib/python3/dist-packages/debmake/para.py:help="pedantically 
check auto-generated files",
   /usr/lib/python3/dist-packages/debmake/para.py-)
   /usr/lib/python3/dist-packages/debmake/para.py-p.add_argument(
   /usr/lib/python3/dist-packages/debmake/para.py-"-T",
   /usr/lib/python3/dist-packages/debmake/para.py-"--tutorial",
   /usr/lib/python3/dist-packages/debmake/para.py-action="store_true",
   --
   /usr/share/debmake/extra0desc_long/_long: This Debian binary package was 
auto-generated by the
   /usr/share/debmake/extra0desc_long/_long- debmake(1) command provided by the 
debmake package.
   --
   /usr/share/debmake/extra0desc_long/_long_tutorial: This Debian binary 
package was auto-generated by the
   /usr/share/debmake/extra0desc_long/_long_tutorial- debmake(1) command 
provided by the debmake package.
   /usr/share/debmake/extra0desc_long/_long_tutorial- .
   /usr/share/debmake/extra0desc_long/_long_tutorial- = This comes from the 
unmodified template file =
   /usr/share/debmake/extra0desc_long/_long_tutorial- .
   /usr/share/debmake/extra0desc_long/_long_tutorial- Please edit this template 
file (debian/control) and other package files

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---

Version: 3.1.0-2

the bug is fixed in version 3.1.0-2 with fixing the description in 
debian/control.


The other lines reported with

dgrep -A5 'auto-generated' debmake

are false-positives since they are files from the debmake package and 
not from yq.


Christoph


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

Bug#1029310: [Help] Re: Bug#1029310: src:r-cran-bayesplot: fails to migrate to testing for too long: autopkgtest regression

[Nilesh Patra]

On 23 January 2023 3:06:58 pm IST, Andreas Tille  wrote:
>Am Sat, Jan 21, 2023 at 10:17:06PM +0530 schrieb Nilesh Patra:
>> On 1/21/23 21:59, Andreas Tille wrote:
>> > Am Sat, Jan 21, 2023 at 09:46:07PM +0530 schrieb Nilesh Patra:
>> > > On 1/21/23 16:56, Andreas Tille wrote:
>> > > > as per DebCI there are 15 autopkgtest failures which seem to be
>> > > > connected to ggplot2 API somehow.[1]  Interestingly Salsa CI[2] does 
>> > > > not
>> > > > show this autopkgtest error neither can I reproduce the problem on my 
>> > > > local
>> > > > pbuilder.
>> > > > 
>> > > > Has anyone some idea what might be wrong?  If not I might ask bug 
>> > > > reporter
>> > > > for more info.
>> > > 
>> > > I can't repro it either.
>> > 
>> > Relieving to know that I did not missed any basic thing here. ;-)
>> > 
>> > > But the log you point to is a fresh failure (today).
>> > > Did not dig deeper, but did you take a look at the `diff` between log 
>> > > that passes and the one
>> > > which does not?
>> > 
>> > Not yet.  Where can I find those old logs?
>> 
>> You can take a diff betweek ci log you pointed to and the log on salsa 
>> CI/local system.
>> The debci runs with package versions in testing, so there might be a bump in 
>> some dependency.
>
>I did a diff between the r-cran-* packages in the failing log and the
>successful log: 
> [...]
>
>to me those diffs are locking not really spectacular regarding to
>the actual issue.

Right.

>I admit I'm running out of ideas but for the moment my last resort
>is to skip the 8 affected test, let the packages migrate to testing
>and revert skipping the tests afterwards.

I did find an issue[3] which states ggplot2 breaks bayesplot 1.9.0 and spews 
the exact same errors we observe in debci.
There's also an upstream issue with bayesplot installation (similar stuff 
again) where it works for some people but not for others, see[4].
But then I'm not sure as to why it works for me, you and salsa CI. For now I'll 
have to dismiss it by calling it black magic.

Your approach sounds fair. Maybe you should do what you wrote (disable tests, 
let it migrate, enable tests again)

>[1] https://ci.debian.net/packages/r/r-cran-bayesplot/testing/amd64/
>[2] 
>https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-bayesplot/28139180/log.gz
[3]: https://github.com/tidyverse/ggplot2/blob/main/revdep/problems.md#bayesplot
[4]: 
https://github.com/stan-dev/bayesplot/issues/297
--
Best,
Nilesh

Bug#1028638: Gajim crashes. Upstream denies responsability and bans users.

[bert]

Niccolo,

I usually don't engage with stuff like this, but your behaviour is what 
makes open source development harder and often not fun.


I hope you know that all posts in the Gajim MUC are public:
https://conference.gajim.org:5281/muc_log/gajim/2023-01-19

You barged in there requesting help because you're "loosing money", and 
Gajim devs + other people immediately tried to help you.
They very clearly explained that this is a libproxy bug and told you 
that downgrading libproxy works as a temporary workaround, which you 
don't want to do because of "dependency issues", which is your choice.
The devs and maintainers in the MUC then very clearly explained to you 
why the Gajim devs can't do anything about this problem.
You then continue to mix up "upstream", "Debian developers" and "Gajim 
developers" and finally (because you have nothing more to add and out 
of frustration) you start lamenting about Gajim being a resource hog 
because it's written in Python.


They (understandably imho) ban you from their MUC and you end up here 
writing things like


> That's speak volumes about the Gajim team. They not only suppress 
freedom
> of choice but thay are also recurring to low level methods in order 
to hide
> Gajim issues and bugs. I felt compelled to report this incident 
downstream.


which is absolutely ridiculous and unjustified.

Also:
> I'm running Debian testing.

Well, yeah.

Bug#1029436: marked as done (open-infrastructure-service-tools fails to install)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 09:46:57 +
with message-id 
and subject line Bug#1029436: fixed in open-infrastructure-service-tools 
20221122-3
has caused the Debian Bug report #1029436,
regarding open-infrastructure-service-tools fails to install
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.)


-- 
1029436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: open-infrastructure-service-tools
Version: 20221122-2
Severity: serious

https://piuparts.debian.org/sid/fail/open-infrastructure-service-tools_20221122-2.log

...
  Setting up open-infrastructure-service-tools (20221122-2) ...
  update-alternatives: error: alternative path /usr/share/apache2/icons doesn't 
exist
  dpkg: error processing package open-infrastructure-service-tools 
(--configure):
   installed open-infrastructure-service-tools package post-installation script 
subprocess returned error exit status 2
  Processing triggers for libc-bin (2.36-8) ...
  Errors were encountered while processing:
   open-infrastructure-service-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)
--- End Message ---
--- Begin Message ---
Source: open-infrastructure-service-tools
Source-Version: 20221122-3
Done: Daniel Baumann 

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

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated 
open-infrastructure-service-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Jan 2023 09:37:07 +0100
Source: open-infrastructure-service-tools
Architecture: source
Version: 20221122-3
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 1029436
Changes:
 open-infrastructure-service-tools (20221122-3) sid; urgency=medium
 .
   * Uploading to sid.
   * Reverting downgrade of apache2 depends to suggests (Closes: #1029436).
   * Using codename instead of suitename in changelog.
Checksums-Sha1:
 e1a0835d678c182e02ff8a2b3a0b11cc19c6a141 2378 
open-infrastructure-service-tools_20221122-3.dsc
 a50fb1a0466460a67ee9f185e7f74fbf31c0af19 12616 
open-infrastructure-service-tools_20221122-3.debian.tar.xz
 0fb249dd94c5d2a0a62253c8d3304f4e84de050e 9753 
open-infrastructure-service-tools_20221122-3_amd64.buildinfo
Checksums-Sha256:
 f7f246ddf61c1abbd74477f7442fc08d53738481ce44107adf83ff2cc1327d76 2378 
open-infrastructure-service-tools_20221122-3.dsc
 43060d9493f426e3834d1f4953a1e96814814ece06f12495d28c5db031dfd4cb 12616 
open-infrastructure-service-tools_20221122-3.debian.tar.xz
 23a2461ad0e717e3883a6589a3477086942b2199a9f521f8ad45da139cda949d 9753 
open-infrastructure-service-tools_20221122-3_amd64.buildinfo
Files:
 c65f1145f2cda778f3a7bf500b7405cd 2378 admin optional 
open-infrastructure-service-tools_20221122-3.dsc
 d81d2fe8a32d1c0b1aee97e217420382 12616 admin optional 
open-infrastructure-service-tools_20221122-3.debian.tar.xz
 5aabc296875bc430bc34fae3994002a0 9753 admin optional 
open-infrastructure-service-tools_20221122-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmPOSAkACgkQVc8b+Yar
ucd75hAAylBFx+9i2Rk6pcznGWJy0bG1kN8AQLN0w76qTcr+fD6REYuPdTd4iK+y
dHG4IO1kx9P3/3vBLVK5s3tEwnNNvvEp1PkuHhExm2UbFaj+U3AKKW8G045Zp+HG
Kwe5IJAmqgIBIdkPvzGXEYEJBMMTbA/IE8mPAa1TKQ0bKNBWmOHlqxFaWLN7NHwl
dpNoc7RzLMsRU5v9geDIW11c2ikolA+R/aZcHcywyEa7FAR1vvyLud5qpY8sz6wl
/QemV5v3DChr0q8nfmR4TfjUKgmlrkGJU6wsk4G3rwexhNJQiyjLokn03CAqVl9Q
UVzOWS8FzU3BfzPbvqfHYkmwsoR/3JJ7/yROR3trZcxau+FfSDP6s+bH3UWlfnN6
mIEkKLqsetl7oY73XJADYq2iR2qSqNWzNFi3j/JyNOLF5afAZ8C8DI3MqefzzkmD
9g5GJ/PA6zF7eTzIpOltmq7xTT85cXqT/5PQUkdRdl3Rg4LjXi2i+1tIYhreitqb
WLwAyl6F/3N29FL2M6aqdJkHBoAlht0VBqBc6mM7xHNTEF73bqHfcPt0qi8+DPO9
RvzKWzoT7x6cK9I+q6IsL8g5csmPGQW+ZwdEUbv3oMB/vhEABPIWL5vsVRBXz9Qj
1qJEwj/H344NuQe9caPQ37kIKiTZYnVLbnHvPrzTbEfueEIeTII=
=w3AV
-END PGP SIGNATURE End Message ---

Bug#1029287: marked as done (progress-linux-desktop: Depends: webext-ublock-origin but it is not installable)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 09:47:39 +
with message-id 
and subject line Bug#1029287: fixed in progress-linux-metapackages 20221002-4
has caused the Debian Bug report #1029287,
regarding progress-linux-desktop: Depends: webext-ublock-origin but it is not 
installable
to be marked as done.

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

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


-- 
1029287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: progress-linux-desktop
Version: 20221002-3
Severity: serious

The following packages have unmet dependencies:
 progress-linux-desktop : Depends: webext-ublock-origin but it is not 
installable


The transitional package webext-ublock-origin that depended on both
webext-ublock-origin-firefox and webext-ublock-origin-chromium was
removed.
--- End Message ---
--- Begin Message ---
Source: progress-linux-metapackages
Source-Version: 20221002-4
Done: Daniel Baumann 

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

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated 
progress-linux-metapackages package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Jan 2023 09:31:50 +0100
Source: progress-linux-metapackages
Architecture: source
Version: 20221002-4
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 1029287
Changes:
 progress-linux-metapackages (20221002-4) sid; urgency=medium
 .
   * Uploading to sid.
   * Removing obsolete webext-https-everywhere from progress-linux-desktop.
   * Updating ublock-origin depends (Closes: #1029287).
Checksums-Sha1:
 8b4ca44505979e61684073258059dcaade4c541f 2768 
progress-linux-metapackages_20221002-4.dsc
 eff432ad50bc34a07163e7ae096de743480d201b 6868 
progress-linux-metapackages_20221002-4.debian.tar.xz
 3cf596c3ecd117b4e10808367ff2ed57ce4274db 9051 
progress-linux-metapackages_20221002-4_amd64.buildinfo
Checksums-Sha256:
 40c6da8d9c0227851e8c1e69a4e8a364942044d70d0d2a3c00c33d44520e4a18 2768 
progress-linux-metapackages_20221002-4.dsc
 f10cacf736111ec8e02c6096d82994d2993f0b5bfb80d0798802cdfe88da85f4 6868 
progress-linux-metapackages_20221002-4.debian.tar.xz
 1ec3aec7d0dd766c62f37a28a80a92d4523fca1c5281970b859e0be2e970904d 9051 
progress-linux-metapackages_20221002-4_amd64.buildinfo
Files:
 13153a7e84be06123ba2f8b40545e894 2768 metapackages optional 
progress-linux-metapackages_20221002-4.dsc
 fef5a8c3954499a961e8d9e97e5c6a48 6868 metapackages optional 
progress-linux-metapackages_20221002-4.debian.tar.xz
 cdf2f4c71bbac17996f022b1a5066ab8 9051 metapackages optional 
progress-linux-metapackages_20221002-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmPORigACgkQVc8b+Yar
uccQ/A//YAuK/Xarl99JyWNEEKWfFRAIG7dHtOGetX0quf/I4icnVY28zJEIKrAd
LAwbMURkhcc8PkJf/iceic6OVeCYqwl5BpOsY07122uwa6g3rtkzlQawoaTuRePw
MKnxaDP3lc5yEf4Un+uctc3Poz33AvmdR1denEXkqGoVklkwTZtU8ouwEC/YgFmJ
dgXv3MWPqpOFfv7uy1C3P8675fGFmr5c1phsGoJiwSk/ENsoMGd+msWTtcLyUiCz
yp0S/pc2YcWnJWL+2qwm2aiBQGRKI7UHNU48IOkcHYV+BjCzOTJtp2DM7Jfak5Ri
tOip2QVx2nVue2yq6M6IoJVec6UlPTr6ku2cVkPZciZivTiZ7ved7b5cyRgRxRrK
7fTNY80UhAOTlUVWTlxr996p/Q6IDtQL2YuoQ+NcgGFCokUiEDw/BMhv6QTE2b9r
WJBF+1uoEhJajH3FjfNvcQhzlj/4IyxxRvkz9E92J3EZ4dx1KIcE20HC2UJ+1ScI
mSOs8ljqkLSwSQP55twtWrfADIGQ4KM4LWDCuPHNDEKRUgQYN1NyjjHZlOEKhHBP
C5WYiqT32cqhfWBgvmpUk3X1WS9ZZlwWtQu1LeO4mp9iNLjBMtgcVP4zTfVDAqMV
ZRzcqFeIMmjaGI5+IhVOK20aYvZMM0X3qgStLJ8RqpuO0dSQ8PA=
=fKU7
-END PGP SIGNATURE End Message ---

Bug#1029310: [Help] Re: Bug#1029310: src:r-cran-bayesplot: fails to migrate to testing for too long: autopkgtest regression

[Andreas Tille]

Am Sat, Jan 21, 2023 at 10:17:06PM +0530 schrieb Nilesh Patra:
> On 1/21/23 21:59, Andreas Tille wrote:
> > Am Sat, Jan 21, 2023 at 09:46:07PM +0530 schrieb Nilesh Patra:
> > > On 1/21/23 16:56, Andreas Tille wrote:
> > > > as per DebCI there are 15 autopkgtest failures which seem to be
> > > > connected to ggplot2 API somehow.[1]  Interestingly Salsa CI[2] does not
> > > > show this autopkgtest error neither can I reproduce the problem on my 
> > > > local
> > > > pbuilder.
> > > > 
> > > > Has anyone some idea what might be wrong?  If not I might ask bug 
> > > > reporter
> > > > for more info.
> > > 
> > > I can't repro it either.
> > 
> > Relieving to know that I did not missed any basic thing here. ;-)
> > 
> > > But the log you point to is a fresh failure (today).
> > > Did not dig deeper, but did you take a look at the `diff` between log 
> > > that passes and the one
> > > which does not?
> > 
> > Not yet.  Where can I find those old logs?
> 
> You can take a diff betweek ci log you pointed to and the log on salsa 
> CI/local system.
> The debci runs with package versions in testing, so there might be a bump in 
> some dependency.

I did a diff between the r-cran-* packages in the failing log and the
successful log: 


--- debci (with dependencies from testing which fails 
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-bayesplot/30584842/log.gz
+++ salsa (with dependencies from unstable which works)
@@ -2,8 +2,8 @@
@@ -153,12 +153,13 @@

-r-base-core_4.2.2.20221110-1+b1_amd64.deb
+r-base-core_4.2.2.20221110-1_amd64.deb

-r-cran-bayesplot_1.9.0-1_all.deb
+r-cran-bayesplot.deb

-r-cran-cli_3.6.0-1_amd64.deb
+r-cran-cli_3.5.0-1_amd64.deb

-r-cran-ggplot2_3.4.0+dfsg-2_all.deb
+r-cran-ggplot2_3.4.0+dfsg-1_all.deb

-r-cran-htmlwidgets_1.6.1+dfsg-1_all.deb
-r-cran-httpuv_1.6.8+dfsg-1_amd64.deb
+r-cran-htmlwidgets_1.6.0+dfsg-1_all.deb
+r-cran-httpuv_1.6.7+dfsg-1_amd64.deb

-r-cran-purrr_0.3.5-1_amd64.deb
+r-cran-purrr_1.0.0-1_amd64.deb

-r-cran-rcppparallel_5.1.6+dfsg-1_amd64.deb
+r-cran-rcppparallel_5.1.5+dfsg-3_amd64.deb

-r-cran-statmod_1.5.0-1_amd64.deb
-r-cran-stringi_1.7.12-1_amd64.deb
-r-cran-stringr_1.4.1-1_all.deb
+r-cran-statmod_1.4.37-1_amd64.deb
+r-cran-stringi_1.7.8-1+b1_amd64.deb
+r-cran-stringr_1.5.0-1_all.deb

-r-cran-xts_0.12.1-1_amd64.deb
+r-cran-xts_0.12.2-1_amd64.deb


to me those diffs are locking not really spectacular regarding to
the actual issue.  I also checked the debci history[1] where the
first failure of this kind is

1.9.0-1 2022-11-11 23:59:45 UTC 
r-cran-ggplot2/3.4.0+dfsg-1 diffoscop...
src:r-cran-ggplot2 from unstable
src:diffoscope from unstable
src:r-base from unstable
src:r-cran-vctrs from unstable 

where I can find inside the test log[2]

This might correlate to

r-cran-ggplot2 (3.4.0+dfsg-1) unstable; urgency=medium

  * New upstream version
...
 -- Andreas Tille   Fri, 11 Nov 2022 08:24:21 +0100



I admit I'm running out of ideas but for the moment my last resort
is to skip the 8 affected test, let the packages migrate to testing
and revert skipping the tests afterwards.

Kind regards
Andreas.



[1] https://ci.debian.net/packages/r/r-cran-bayesplot/testing/amd64/
[2] 
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-bayesplot/28139180/log.gz

-- 
http://fam-tille.de

Bug#1029286: marked as done (bfh-desktop: Depends: webext-ublock-origin but it is not installable)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 09:36:21 +
with message-id 
and subject line Bug#1029286: fixed in bfh-metapackages 20211009-15
has caused the Debian Bug report #1029286,
regarding bfh-desktop: Depends: webext-ublock-origin but it is not installable
to be marked as done.

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

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


-- 
1029286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bfh-desktop
Version: 20211009-14
Severity: serious

The following packages have unmet dependencies:
 bfh-desktop : Depends: webext-ublock-origin but it is not installable


The transitional package webext-ublock-origin that depended on both
webext-ublock-origin-firefox and webext-ublock-origin-chromium was
removed.
--- End Message ---
--- Begin Message ---
Source: bfh-metapackages
Source-Version: 20211009-15
Done: Daniel Baumann 

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

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated 
bfh-metapackages package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Jan 2023 09:29:46 +0100
Source: bfh-metapackages
Architecture: source
Version: 20211009-15
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 1029286
Changes:
 bfh-metapackages (20211009-15) sid; urgency=medium
 .
   * Uploading to sid.
   * Removing obsolete webext-https-everywhere from bfh-desktop.
   * Updating ublock-origin depends (Closes: #1029286).
Checksums-Sha1:
 0bcd01e8b8ba5717d79e5f7a1154526275b5adb1 2421 bfh-metapackages_20211009-15.dsc
 67410ab5a2ea18863fec5f38a49e207defb49fb9 5288 
bfh-metapackages_20211009-15.debian.tar.xz
 3e7fc33394782d4a46448701fc0207b7c12497d6 8391 
bfh-metapackages_20211009-15_amd64.buildinfo
Checksums-Sha256:
 30b7721836fbc31180f62e8101ec449460bf4cbd85bae9e8cbc3352e2c81bac0 2421 
bfh-metapackages_20211009-15.dsc
 797ad24f499b2223fad4c173f2d9464bd94620d0b475a450ad4a9239f28faa39 5288 
bfh-metapackages_20211009-15.debian.tar.xz
 6be31a8688421a3511bee8b90ae83df89a5830e871401ecb4ecf185a8b1b6eca 8391 
bfh-metapackages_20211009-15_amd64.buildinfo
Files:
 9ff76be7842565d3cbfbc2bdec3d0f69 2421 metapackages optional 
bfh-metapackages_20211009-15.dsc
 00d7d008bc09252220dbc0943a8a0b24 5288 metapackages optional 
bfh-metapackages_20211009-15.debian.tar.xz
 be27af76b6669c2fd7994cc427090938 8391 metapackages optional 
bfh-metapackages_20211009-15_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmPORcEACgkQVc8b+Yar
ucfQKRAAkhUJIxVcxnZJb04jgdpBDEGenvENuDHBYYdDpAYZAjEczWi1djlQCFgD
BIMrUpgKMLE3BHQ1iEqHNmXFPPFAmZXCOVOw45+PVYUUPBw/xm2pVYetMLb94S5h
qje8h628tXHlWlhIdCjGJbjh+SCnYRDns3pqR5qUt1C5NejTLqgbEV9w8wW3bjh3
G8nbFNCatuUPC6pvNFram+JwJBHyZT8NJC2bBGpBtYf7nC1yrW8JpIjJliD6ix2G
lnPNajbvGagDoN29NxUlBfYVt8NyBoD/m3AElp5ZtGsqSuu93Ja9PGaNCoX83G0W
/idaJ9grI32q+jCnIzEI81FATW2T/vlQqlCLj/KduCYgGucz1JP4mE6CG7w8ue2d
OMnCZP2n89RMB+rYUxxDXQZllqGr8JmUiY1RBEs/plYjzZY3PtcVIHgfMJaPONbi
fuza7yolZYSJXmjmawdMeuBZMO7BUa6uLIyxGdnNQwa4oHCPWbCy259OCsBoUbP7
R4FE9Alu3x1+EKp8VOJwCBqSaOad25hUT9XLjFeWZ4TyH34pC9Hhn7HvsQDbxYBW
A+8/FEm4dQUP0Pw6gJLpTALytuuPvtAXebYKpikdQ6Niv/TV5YT/WHRTuehscZzB
bnRke+M4oLMEsqIr7iJrs/eqt60ucAdpbJhSMbJQWnWnLeaAGgs=
=XW4l
-END PGP SIGNATURE End Message ---

Bug#1029182: marked as done (pgcli: Dependency needs updating python3-psycopg3 -> python3-psycopg)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 09:01:02 +
with message-id 
and subject line Bug#1029182: fixed in pgcli 3.5.0-5
has caused the Debian Bug report #1029182,
regarding pgcli: Dependency needs updating python3-psycopg3 -> python3-psycopg
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.)


-- 
1029182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pgcli
Version: 3.5.0-3
Severity: serious

python3-psycopg3 does not exist anymore, see #1016031.
--- End Message ---
--- Begin Message ---
Source: pgcli
Source-Version: 3.5.0-5
Done: Daniel Baumann 

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

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated pgcli 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Jan 2023 09:26:07 +0100
Source: pgcli
Architecture: source
Version: 3.5.0-5
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 1029182
Changes:
 pgcli (3.5.0-5) sid; urgency=medium
 .
   * Uploading to sid.
   * Building with fixed psycopg3 (Closes: #1029182).
Checksums-Sha1:
 9248b3bfd6bc44a11a93faef2edb01795a658fab 2015 pgcli_3.5.0-5.dsc
 fe34e2cafb7fad67f29be3ab74882800ce656984 4348 pgcli_3.5.0-5.debian.tar.xz
 bc4c9096981b5d5d4832edf65a8bee0b25ec0309 7011 pgcli_3.5.0-5_amd64.buildinfo
Checksums-Sha256:
 20348e422c601bcc3a484ab6404118c01c0481765353e9fb01b54364da1dd28b 2015 
pgcli_3.5.0-5.dsc
 3955febb3cadb23b0d2d6a3ada0ce9bd4d99194a118c27d7b099d9cac4ab14ba 4348 
pgcli_3.5.0-5.debian.tar.xz
 fd1e6dde2d9ae4badbd59b663119685c8bdfecebae97274ad50d47b184c94a54 7011 
pgcli_3.5.0-5_amd64.buildinfo
Files:
 560069eb190b8ad9b4d6924475263d52 2015 database optional pgcli_3.5.0-5.dsc
 95d06e1a716fa7037c03cf07cce0d452 4348 database optional 
pgcli_3.5.0-5.debian.tar.xz
 8368d9b267b23cb14ace53a0a111ae78 7011 database optional 
pgcli_3.5.0-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmPORREACgkQVc8b+Yar
ucd+qhAApW3Hv+UAlTJ5RsKeTyvVQazN5NJI/8i29vofqGJCbEvgY0YVyR2rdqVH
m/kq7witu5PDnSe+652mdrbIcuCXkAsiC8sq/4EykLpTDzUgI1IsYQDK3/WqyA2R
6cVsHklq/yIYC10z71TRonM+oUXRBoriRX19bMI5risWTIIczOSIXm3LOfPAX/lc
z9eR1MZ56OnWwHycbs96NSIU9puDD0web/fALOkLMsrI4QZc8GE7KHQgiX/tds/W
PJ4AtUI1myBiqxeUYFrnwnQVGc87MP/2x9z4S5GeEhk5lnRluCFlsu+G8a6ogaNg
P3BhPztx7XkxkvhkGd9zZr8FpRMay3iol/qZFE1cIXryP3yaVCR8uFReQFkrq0TR
j7qAmVKDeS7G4kyB5bZr5iAEhchiMpEvy7w/nTr9xXCK1tzC2FhQa/SKmMgGp7bF
D89mz0MLipnu3lTT/+xBykap71UjwTtqALUMIqyQ4QnxmztHLhQ8LVbTf12PTOhO
0M0BBdMada3gNW5dg1nzow9dS4gY9aBsK+ugKriuDD7Yw/C7zIW3dxiY/0AgqSQM
92G0yFKeYdAmGmhidRqxZuoEejH7dML8h1VxgSUUl4u1HCiytCpCr/Fy75tH2c+k
wr3jYvacBd34Q889DPDfIcBaCzfG/Vmbm0VpOx4NxPT+ao9XuDU=
=ZJ35
-END PGP SIGNATURE End Message ---

Bug#1029428: marked as done (pyephem: FTBFS in bookworm (undeclared build-dependency on tzdata))

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2023 09:01:21 +
with message-id 
and subject line Bug#1029428: fixed in pyephem 4.1.4-2
has caused the Debian Bug report #1029428,
regarding pyephem: FTBFS in bookworm (undeclared build-dependency on tzdata)
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.)


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

Package: src:pyephem
Version: 4.1.3-1
Severity: serious
Tags: ftbfs patch

Dear maintainer:

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


[...]
 debian/rules binary-arch
dh binary-arch --with python3 --buildsystem=pybuild
   dh_update_autotools_config -a -O--buildsystem=pybuild
   dh_autoreconf -a -O--buildsystem=pybuild
   dh_auto_configure -a -O--buildsystem=pybuild
I: pybuild base:240: python3.10 setup.py config
/<>/setup.py:3: DeprecationWarning: The distutils package is 
deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for 
potential alternatives
  from distutils.core import setup, Extension
running config
   dh_auto_build -a -O--buildsystem=pybuild
I: pybuild base:240: /usr/bin/python3 setup.py build
/<>/setup.py:3: DeprecationWarning: The distutils package is 
deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for 
potential alternatives
  from distutils.core import setup, Extension
running build
running build_py
creating /<>/.pybuild/cpython3_3.10_ephem/build/ephem
copying ephem/stars.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem
copying ephem/__init__.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem
copying ephem/cities.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem
creating /<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_usno.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_launchpad_236872.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_github_issues.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_angles.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_stars.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_launchpad_244811.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/__init__.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_cities.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_bodies.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_constants.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_satellite.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_dates.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_usno_equinoxes.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_rst.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_rise_set.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_locales.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_observers.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
copying ephem/tests/test_jpl.py -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/tests
creating /<>/.pybuild/cpython3_3.10_ephem/build/ephem/doc
copying ephem/doc/rise-set.rst -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/doc
copying ephem/doc/tutorial.rst -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/doc
copying ephem/doc/CHANGELOG.rst -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/doc
copying ephem/doc/index.rst -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/doc
copying ephem/doc/date.rst -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/doc
copying ephem/doc/examples.rst -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/doc
copying ephem/doc/toc.rst -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/doc
copying ephem/doc/radec.rst -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/doc
copying ephem/doc/quick.rst -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/doc
copying ephem/doc/newton.rst -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/doc
copying ephem/doc/catalogs.rst -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/doc
copying ephem/doc/angle.rst -> 
/<>/.pybuild/cpython3_3.10_ephem/build/ephem/doc
copying ephem/doc/co