Bug#1020104: marked as done (libiio: FTBFS: dh_install: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2022 05:23:09 +
with message-id 
and subject line Bug#1020104: fixed in libiio 0.24-2
has caused the Debian Bug report #1020104,
regarding libiio: FTBFS: dh_install: error: missing files, aborting
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.)


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

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/build'
> make[3]: Nothing to be done for 'preinstall'.
> make[3]: Leaving directory '/<>/build'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "None"
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/libiio.pc
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libiio.so.0.24
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libiio.so.0
> -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libiio.so
> -- Installing: /<>/debian/tmp/usr/include/iio.h
> -- Installing: /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/py-modindex.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/objects.inv
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/searchindex.js
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_modules
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_modules/index.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_modules/iio_readdev.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_modules/iio_info.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_modules/iio_attr.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_modules/iio_writedev.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_modules/iio.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/.buildinfo
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/search.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_sources
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_sources/index.rst.txt
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_sources/context.rst.txt
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_sources/channel.rst.txt
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_sources/device.rst.txt
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_sources/iio_readdev.rst.txt
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_sources/buffer.rst.txt
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_sources/examples.rst.txt
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_sources/iio_attr.rst.txt
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_sources/iio_writedev.rst.txt
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_sources/trigger.rst.txt
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_sources/iio_info.rst.txt
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/genindex.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/context.html
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_static
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_static/pygments.css
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_static/basic.css
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_static/file.png
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_static/css
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_static/css/badge_only.css
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.24/python/_static/css/theme.css
> -- Installing: 
> 

Bug#1002113: marked as done (gr-gsm: FTBFS: Unknown CMake command "GR_SWIG_MAKE")

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2022 05:21:32 +
with message-id 
and subject line Bug#1002113: fixed in gr-gsm 1.0.0~20220727-1
has caused the Debian Bug report #1002113,
regarding gr-gsm: FTBFS: Unknown CMake command "GR_SWIG_MAKE"
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.)


-- 
1002113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gr-gsm
Version: 0.42.2.20200214-1
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_af046.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-gsm_0.42.2.20200214-1_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 ---
Source: gr-gsm
Source-Version: 1.0.0~20220727-1
Done: A. Maitland Bottoms 

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gr-gsm 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, 21 Sep 2022 23:27:12 -0400
Source: gr-gsm
Architecture: source
Version: 1.0.0~20220727-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: A. Maitland Bottoms 
Closes: 1002113
Changes:
 gr-gsm (1.0.0~20220727-1) unstable; urgency=medium
 .
   * New upstream branch to build with gnuradio 3.10 (Closes: #1002113)
 https://github.com/bkerler/gr-gsm/tree/maint-3.10_with_multiarfcn
   * Bump Standards-Version to 4.6.1 (no changes)
Checksums-Sha1:
 86c63b036795321817832fb2670e299dce455f4c 2198 gr-gsm_1.0.0~20220727-1.dsc
 3ddc96c301b2a440af88ec7de19cd23f36e27b9a 230976 
gr-gsm_1.0.0~20220727.orig.tar.xz
 8b6b116531e15ff1c57b1be1248a26a106cc05ca 4984 
gr-gsm_1.0.0~20220727-1.debian.tar.xz
 6658821fb750f73ca0d28bc0bd6a9343a66e9cfb 20644 
gr-gsm_1.0.0~20220727-1_amd64.buildinfo
Checksums-Sha256:
 679f4146754344c177ca52ccd38945bab7f92f21e6eeedc8ad6f94ba43ad38c9 2198 
gr-gsm_1.0.0~20220727-1.dsc
 968f262dd7090b1d5951a5c743296c8ba063cc71127667dacb18aa4bcdb22153 230976 
gr-gsm_1.0.0~20220727.orig.tar.xz
 0ae3495424ec7aeac03f4d8c23e1340bfdb81802614920951d449085919c2251 4984 
gr-gsm_1.0.0~20220727-1.debian.tar.xz
 627aa6b1cf6b9a96c18305bacddc3fe714f70eae8e4b140a9ea41dd13bc2d9c7 20644 
gr-gsm_1.0.0~20220727-1_amd64.buildinfo
Files:
 b65363e92fbc46084d9f3ed4d17414c0 2198 libdevel optional 
gr-gsm_1.0.0~20220727-1.dsc
 f9c8ab8d1774d7a04ca1dcfe69a2d937 230976 libdevel optional 
gr-gsm_1.0.0~20220727.orig.tar.xz
 915587361ed0700e927b3e70a4fa4919 4984 libdevel optional 
gr-gsm_1.0.0~20220727-1.debian.tar.xz
 a247652efacf75fdc3a78da01de52e89 20644 libdevel optional 
gr-gsm_1.0.0~20220727-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmMr6cIACgkQUEHxiR9E
4JC1LRAAzhAsHJiGeFIcILLJsLqrVUuVydvIEbbS9izuywNRl92oQIS2Uu77raoK

Bug#922214: marked as done (libpng12-0: libpng12.so.0 can not be installed, file or directory not found)

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2022 07:04:04 +0200
with message-id <6cea7794d317f5cb4ec49581888af07020d2646e.ca...@sviech.de>
and subject line Re: libpng12-0: libpng12.so.0 can not be installed, file or 
directory not found
has caused the Debian Bug report #922214,
regarding libpng12-0: libpng12.so.0 can not be installed, file or directory not 
found
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.)


-- 
922214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpng12-0
Version: 1.2.50-2+deb8u3
Severity: grave
Tags: a11y d-i
Justification: renders package unusable

dpkg says while trying to install:
file /usr/lib/x86_64-gnu-linux/libpng12-0.so.0 can not be installed, file or 
directory not found
and the installation is aborted
unpacking the deb-archiv is possible and in the package is that file in 
question as a symlink to /lib/x86_64-gnu-linux/libpng12.so.0,
which is a symlink to /lib/x86_64-gnu-linux/libpng12.so.0.50.0



-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (700, 'stable-updates'), (700, 'unstable'), (700, 'testing'), 
(700, 'stable'), (700, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/20 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpng12-0 depends on:
ii  libc6  2.28-7
ii  multiarch-support  2.28-7
ii  zlib1g 1:1.2.11.dfsg-1

libpng12-0 recommends no packages.

libpng12-0 suggests no packages.
--- End Message ---
--- Begin Message ---
Control: tags -1 wontfix

libpng 1.2 has been removed from Debian a long time ago, and now also oldstable 
(buster) is EOL, 
so closign this bug as wontfix--- End Message ---

Processed: Re: Bug#1020049: r-cran-hdf5r: FTBFS: datatype_export.c:1903:19: error: storage size of ‘myenum’ isn’t known

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1020049 [src:r-cran-hdf5r] r-cran-hdf5r: FTBFS: datatype_export.c:1903:19: 
error: storage size of ‘myenum’ isn’t known
Ignoring request to alter tags of bug #1020049 to the same tags previously set
> forwarded -1 https://github.com/hhoeflin/hdf5r/issues/192
Bug #1020049 [src:r-cran-hdf5r] r-cran-hdf5r: FTBFS: datatype_export.c:1903:19: 
error: storage size of ‘myenum’ isn’t known
Ignoring request to change the forwarded-to-address of bug#1020049 to the same 
value

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

Processed: Re: Bug#1020049: r-cran-hdf5r: FTBFS: datatype_export.c:1903:19: error: storage size of ‘myenum’ isn’t known

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1020049 [src:r-cran-hdf5r] r-cran-hdf5r: FTBFS: datatype_export.c:1903:19: 
error: storage size of ‘myenum’ isn’t known
Added tag(s) upstream.
> forwarded -1 https://github.com/hhoeflin/hdf5r/issues/192
Bug #1020049 [src:r-cran-hdf5r] r-cran-hdf5r: FTBFS: datatype_export.c:1903:19: 
error: storage size of ‘myenum’ isn’t known
Set Bug forwarded-to-address to 'https://github.com/hhoeflin/hdf5r/issues/192'.

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

Bug#1020049: r-cran-hdf5r: FTBFS: datatype_export.c:1903:19: error: storage size of ‘myenum’ isn’t known

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/hhoeflin/hdf5r/issues/192

Am Sun, Sep 18, 2022 at 08:21:55AM +0200 schrieb Lucas Nussbaum:
> > gcc -I"/usr/share/R/include" -DNDEBUG -I/usr/include/hdf5/serial
> > -D__USE_MINGW_ANSI_STDIO   -fpic  -g -O2 
> > -ffile-prefix-map=/build/r-base-J8F88F/r-base-4.2.1=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> > -D_FORTIFY_SOURCE=2  -c datatype_export.c -o datatype_export.o
> > datatype_export.c: In function ‘create_DT_H5R_type_t’:
> > datatype_export.c:1903:19: error: storage size of ‘myenum’ isn’t known
> >  1903 |   enum H5R_type_t myenum;
> >   |   ^~
> > datatype_export.c:1904:41: error: invalid application of ‘sizeof’ to 
> > incomplete type ‘enum H5R_type_t’
> >  1904 |   hid_t base_type = get_h5_equiv(sizeof(enum H5R_type_t), 
> > issigned(enum H5R_type_t));
> >   | ^~~~
> > In file included from datatype_export.c:20:
> > datatype_export.c:1904:73: error: conversion to incomplete type
> >  1904 |   hid_t base_type = get_h5_equiv(sizeof(enum H5R_type_t), 
> > issigned(enum H5R_type_t));
> >   | 
> > ^~
> > datatype_export.h:29:24: note: in definition of macro ‘issigned’
> >29 | #define issigned(t) (((t)(-1)) < 0)
> >   |^
> > make[1]: *** [/usr/lib/R/etc/Makeconf:168: datatype_export.o] Error 1

I have forwarded this upstream.

Kind regards

Andreas.

-- 
http://fam-tille.de

Processed: Bug#1002113 marked as pending in gr-gsm

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002113 [src:gr-gsm] gr-gsm: FTBFS: Unknown CMake command "GR_SWIG_MAKE"
Added tag(s) pending.

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

Bug#1002113: marked as pending in gr-gsm

[Maitland Bottoms]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-hamradio-team/gr-gsm/-/commit/b264b0dd01970f309a74b21123edb3a197b7f23c


Import Debian changes 1.0.0~20220727-1

gr-gsm (1.0.0~20220727-1) unstable; urgency=medium
.
  * New upstream branch to build with gnuradio 3.10 (Closes: #1002113)
https://github.com/bkerler/gr-gsm/tree/maint-3.10_with_multiarfcn
  * Bump Standards-Version to 4.6.1 (no changes)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002113

Bug#1020407: librust-tracing-futures-dev: impossible to install

[matthias . geiger1024]

Thanks for noticing that, I am working on it. Give me some time to resolve this.

Cheers

Matthias Geiger (werdahias)

Bug#1019519: marked as done (opencv: downloads blobs from Github during build)

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2022 01:43:18 +
with message-id 
and subject line Bug#1019519: fixed in opencv 4.6.0+dfsg-7
has caused the Debian Bug report #1019519,
regarding opencv: downloads blobs from Github during build
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.)


-- 
1019519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opencv
Version: 4.6.0+dfsg-6
Severity: serious
Tags: patch
Justification: Policy 4.9

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

During the build process, OpenCV module wechat_qrcode downloads four blobs from 
Github:
- -- wechat_qrcode: Downloading detect.caffemodel from 
https://raw.githubusercontent.com/WeChatCV/opencv_3rdparty/a8b69ccc738421293254aec5ddb38bd523503252/detect.caffemodel
- -- wechat_qrcode: Downloading detect.prototxt from 
https://raw.githubusercontent.com/WeChatCV/opencv_3rdparty/a8b69ccc738421293254aec5ddb38bd523503252/detect.prototxt
- -- wechat_qrcode: Downloading sr.caffemodel from 
https://raw.githubusercontent.com/WeChatCV/opencv_3rdparty/a8b69ccc738421293254aec5ddb38bd523503252/sr.caffemodel
- -- wechat_qrcode: Downloading sr.prototxt from 
https://raw.githubusercontent.com/WeChatCV/opencv_3rdparty/a8b69ccc738421293254aec5ddb38bd523503252/sr.prototxt

"For packages in the main archive, required targets must not attempt network 
access [...]", according to Debian Policy 4.9.

I have prepared a patch in a fork of the Salsa repository and have started a 
merge request.

Regards,


Victor Westerhuis


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

Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_NL.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en_US:en:nl_NL:nl
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEE6OxII3T+o0Ujs6ECQz2Rq5dHQPsFAmMdENITHHZpY3RvckB3
ZXN0ZXJodS5pcwAKCRBDPZGrl0dA+8tJD/9opFU7fVCyUbMDSqmdWzN8zqaOGw/3
8FzeLW07m8/UrjIIvULXkNqSUCgPfyKNQ0ZFp8dEaVrUCLAZSPdTq27I+r+7I9BT
QFF5B3kV0WzJmxw6u96DoYtNZQGEHLjL5ugJd+jYOTuEOwkfApTvS5CvMSI5Uuol
hdw+KP0z0fNBPKB8J5lgkh1Dth1iqYQTveHuUxhf4nv6ANdTnJCmRwgyWisQpdhf
d11NxpNqm4GM9TrVMG5cT/wBhriZ9PIRgswmVpq2adGCE+Pe1Qgit7VnXl2g1hU8
Nm2B4Yefq80IhSbNBpgg9LSXr+NaNY0YppUqlLZFPv7AJAyGpnJvmLmjOC9AFuTr
PirsyOyO3nE+caMfJp8zZGPNjRwvGEXnuL+YOjjdoz2+rCas0Jb5c/bujHeN6hYT
mt/3w7keXJikKxrmMJibXIz7gRy6Oyu1ZoGXXOkMgZezUi1s1/AUJwM7QOalpO+H
5s+btTZ8tZu7I8O748plYkekFd6UFRBnrV0xXNADpEX6jgsqcLCM+XN88z4jgidF
jnIJePmz6ffJE9kjQs5illj/FtkRdSWsRabn1+0nU+RVrj9gUYgmT8dC0Cfanyrp
eOQNyKK1qBcn2x3Vvfzocr0dUW1KDM+bcOCBMc/JCPlFxYeeMR/X8KCYvNzLFVGI
lIc2JzYOkoIAEA==
=fzKE
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: opencv
Source-Version: 4.6.0+dfsg-7
Done: Mo Zhou 

We believe that the bug you reported is fixed in the latest version of
opencv, 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.
Mo Zhou  (supplier of updated opencv 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, 21 Sep 2022 20:51:42 -0400
Source: opencv
Architecture: source
Version: 4.6.0+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Mo Zhou 
Closes: 958028 1019519 1019863
Changes:
 opencv (4.6.0+dfsg-7) unstable; urgency=medium
 .
   [ Victor Westerhuis ]
   * Do not try to download any files while building (Closes: 1019519)
   * Support building by directly calling d/rules
   * Fix Java architecture test in d/build
   * Do not build unused statically linked apps and Java bindings
   * Delete useless Build-Depends on libswresample
   * Fix building with LAPACK
   * Build highgui module with QT support (Closes: 958028)
 .
   [ Mo Zhou ]
   * Fix broken symlink for .jar file. (Closes: #1019863)
Checksums-Sha1:
 e2e15eab9ef0e831b69f2928be06f9b6bf95328e 6895 opencv_4.6.0+dfsg-7.dsc
 

Bug#1017311: marked as done (zfs-fuse: FTBFS: malloc.c:447:13: error: '__malloc_hook' undeclared (first use in this function); did you mean 'umem_malloc_hook'?)

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2022 00:48:04 +
with message-id 
and subject line Bug#1017311: fixed in zfs-fuse 0.7.0-23
has caused the Debian Bug report #1017311,
regarding zfs-fuse: FTBFS: malloc.c:447:13: error: '__malloc_hook' undeclared 
(first use in this function); did you mean 'umem_malloc_hook'?
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.)


-- 
1017311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zfs-fuse
Version: 0.7.0-22
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT malloc.lo -MD -MP -MF 
> .deps/malloc.Tpo -c malloc.c  -fPIC -DPIC -o .libs/malloc.o
> malloc.c: In function 'umem_malloc_init_hook':
> malloc.c:447:13: error: '__malloc_hook' undeclared (first use in this 
> function); did you mean 'umem_malloc_hook'?
>   447 | if (__malloc_hook != umem_malloc_hook) {
>   | ^
>   | umem_malloc_hook
> malloc.c:447:13: note: each undeclared identifier is reported only once for 
> each function it appears in
> malloc.c:448:17: warning: implicit declaration of function 'umem_startup' 
> [-Wimplicit-function-declaration]
>   448 | umem_startup(NULL, 0, 0, NULL, NULL);
>   | ^~~~
> malloc.c:450:17: error: '__free_hook' undeclared (first use in this 
> function); did you mean 'umem_free_hook'?
>   450 | __free_hook = umem_free_hook;
>   | ^~~
>   | umem_free_hook
> malloc.c:451:17: error: '__realloc_hook' undeclared (first use in this 
> function); did you mean 'umem_realloc_hook'?
>   451 | __realloc_hook = umem_realloc_hook;
>   | ^~
>   | umem_realloc_hook
> malloc.c:452:17: error: '__memalign_hook' undeclared (first use in this 
> function); did you mean 'umem_memalign_hook'?
>   452 | __memalign_hook = umem_memalign_hook;
>   | ^~~
>   | umem_memalign_hook
> make[1]: *** [Makefile:375: malloc.lo] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/zfs-fuse_0.7.0-22_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated zfs-fuse package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 22 Sep 2022 01:32:45 +0200
Source: zfs-fuse
Architecture: source
Version: 0.7.0-23
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Hilko Bengen 
Closes: 1017162 1017311
Changes:
 zfs-fuse (0.7.0-23) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Hilko Bengen ]
   * Add patch to FTBFS with glibc >= 2..34 (Closes: #1017162, #1017311)
Checksums-Sha1:
 891e69cff599c98b64e45ef28d49c3d7bc16039c 2054 zfs-fuse_0.7.0-23.dsc
 4f123e4f7ed599626940c3120981243c5071ee4c 29052 

Bug#1017162: marked as done (zfs-fuse: FTBFS: malloc.c:447:13: error: '__malloc_hook' undeclared (first use in this function); did you mean 'umem_malloc_hook'?)

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2022 00:48:04 +
with message-id 
and subject line Bug#1017162: fixed in zfs-fuse 0.7.0-23
has caused the Debian Bug report #1017162,
regarding zfs-fuse: FTBFS: malloc.c:447:13: error: '__malloc_hook' undeclared 
(first use in this function); did you mean 'umem_malloc_hook'?
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.)


-- 
1017162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zfs-fuse
Version: 0.7.0-22
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT malloc.lo -MD -MP -MF 
> .deps/malloc.Tpo -c malloc.c  -fPIC -DPIC -o .libs/malloc.o
> malloc.c: In function 'umem_malloc_init_hook':
> malloc.c:447:13: error: '__malloc_hook' undeclared (first use in this 
> function); did you mean 'umem_malloc_hook'?
>   447 | if (__malloc_hook != umem_malloc_hook) {
>   | ^
>   | umem_malloc_hook
> malloc.c:447:13: note: each undeclared identifier is reported only once for 
> each function it appears in
> malloc.c:448:17: warning: implicit declaration of function 'umem_startup' 
> [-Wimplicit-function-declaration]
>   448 | umem_startup(NULL, 0, 0, NULL, NULL);
>   | ^~~~
> malloc.c:450:17: error: '__free_hook' undeclared (first use in this 
> function); did you mean 'umem_free_hook'?
>   450 | __free_hook = umem_free_hook;
>   | ^~~
>   | umem_free_hook
> malloc.c:451:17: error: '__realloc_hook' undeclared (first use in this 
> function); did you mean 'umem_realloc_hook'?
>   451 | __realloc_hook = umem_realloc_hook;
>   | ^~
>   | umem_realloc_hook
> malloc.c:452:17: error: '__memalign_hook' undeclared (first use in this 
> function); did you mean 'umem_memalign_hook'?
>   452 | __memalign_hook = umem_memalign_hook;
>   | ^~~
>   | umem_memalign_hook
> make[1]: *** [Makefile:375: malloc.lo] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/zfs-fuse_0.7.0-22_unstable.log

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

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

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

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


--- End Message ---
--- Begin Message ---
Source: zfs-fuse
Source-Version: 0.7.0-23
Done: Hilko Bengen 

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated zfs-fuse package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 22 Sep 2022 01:32:45 +0200
Source: zfs-fuse
Architecture: source
Version: 0.7.0-23
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Hilko Bengen 
Closes: 1017162 1017311
Changes:
 zfs-fuse (0.7.0-23) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Hilko Bengen ]
   * Add patch to FTBFS with glibc >= 2..34 (Closes: #1017162, #1017311)
Checksums-Sha1:
 891e69cff599c98b64e45ef28d49c3d7bc16039c 2054 zfs-fuse_0.7.0-23.dsc
 4f123e4f7ed599626940c3120981243c5071ee4c 29052 

Bug#996063: marked as done (gnome-shell-extension-hijra: Please update for gnome-shell 43)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 23:30:57 +
with message-id 
and subject line Bug#996063: fixed in hijra 1.0-2
has caused the Debian Bug report #996063,
regarding gnome-shell-extension-hijra: Please update for gnome-shell 43
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.)


-- 
996063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-hijra
Version: 1.0-1
Severity: normal
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-41

The metadata.json for this extension doesn't declare compatibility with
GNOME 41. I don't know whether the actual code will need changes or not:
the conservative assumption is that it probably will (so please test).
gnome-shell 41 should be available in experimental soon.

In versions of GNOME Shell up to 3.38, metadata.json didn't matter much,
because validation of extensions' metadata against the installed Shell
version was disabled by default; but since GNOME 40 the default has changed
back to enabling the version check by default, in an effort to avoid
issues caused by outdated extensions remaining enabled. As a result,
GNOME Shell extensions in bookworm should probably have a dependency like:

Depends: gnome-shell (>= x), gnome-shell (<< y~)

where x and y are set according to metadata.json.
gnome-shell-extension-caffeine is a good example of this technique.

When we do the GNOME Shell 41 transition, hopefully soon, we will have
to either update this extension or remove it from testing. It would be
useful to get a fixed version into experimental.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: hijra
Source-Version: 1.0-2
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated hijra 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, 21 Sep 2022 15:26:08 -0400
Source: hijra
Built-For-Profiles: noudeb
Architecture: source
Version: 1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Islamic Maintainers 

Changed-By: Jeremy Bicha 
Closes: 996063
Changes:
 hijra (1.0-2) unstable; urgency=medium
 .
   * Drop obsolete GNOME Shell extension.
 It used the ancient Status Tray. The recommended replacement is to
 install hijra-applet and enable gnome-shell-extension-appindicator
 (Closes: #996063)
   * Drop obsolete Breaks/Replaces
   * Add minimal debian/gbp.conf
   * debian/control: Set XS-Autobuild: yes
Checksums-Sha1:
 19c5c6c9ed9c7742e08c339b74dd1e16eaae36f5 2116 hijra_1.0-2.dsc
 65b92d52e1ab56826c0a589cf9d38ee5cebd1db9 12624 hijra_1.0-2.debian.tar.xz
 cc9780cf4ca0df5160ea46a947ca856d35b494f7 7293 hijra_1.0-2_source.buildinfo
Checksums-Sha256:
 cf06f259dcf030deb70d90d610d85f17191fb36e901c9635a6f78139f8536025 2116 
hijra_1.0-2.dsc
 1dd8e2c57ea9d7ef1baa733d02257b1671705bb5c424ac4f2ec212125f6b100b 12624 
hijra_1.0-2.debian.tar.xz
 1f68a49ad51654651360073277964a63dcff98ab3db92c79662e97c70238bc8c 7293 
hijra_1.0-2_source.buildinfo
Files:
 cc4bb4f5386cc0ab2c72cf0f88781afe 2116 non-free/misc optional hijra_1.0-2.dsc
 df697490192c8b9e5b3e23a0b853dd4f 12624 non-free/misc optional 
hijra_1.0-2.debian.tar.xz
 952d0187b70c6433f11172ab11d46e6e 7293 non-free/misc optional 
hijra_1.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmMrZXEACgkQ5mx3Wuv+
bH3HjxAA1/4BJZlLIZzjx3xAkQUHOxdM0SiWzvmvuANhkBda/c3PFOBQ5PVtL0oM
X3UOXAM3Pdis44T4UuC2lA9Yu59b4dXs1u1p4l38ZNJA47h7zdXjWuuAZYOw9sW7
Tqsrq7umIgAO04kTnjFMnayOSePOUnll2kYTeKCS5IpU3PJhZm6cEFvnUGTe9dmj
pO2ZkcxhqQVa/zVW8Hk75HA+6UM70IcsPMMeGrtk3gVuHRKAz875iPgZQs5GgeHq
TQsorVxUL+aLuedNo8EbfLzfPuQioaVVqwdkXyg/co4bQNEY48CY1hofCJvvq1/b
/TMSy+PjPhMoyAslP5ucoBVOH4ftFRT94SCeCFpd5MgvNwWvzhbfYrTtyN30WHKr
WQQ5aKpKHkbutg5/P+2lstvx5dh6WbO4kK+o60Dry99HYVy3wlmeZCrafZm5X8Ix
kQdqwIx8F6JXWtEutaPZBQft3vzSgLyzJ/r7JazZxIHXYup4eRSCiLUMwmfjt9R6

Bug#1012912: marked as done (diagnostics: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 23:24:32 +
with message-id 
and subject line Bug#1012912: fixed in diagnostics 0.3.3-12.3
has caused the Debian Bug report #1012912,
regarding diagnostics: ftbfs with GCC-12
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.)


-- 
1012912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:diagnostics
Version: 0.3.3-12.2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/diagnostics_0.3.3-12.2_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I../.. 
-DDEBUG__LEVEL__=2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -pedantic -Wno-unused-function -MT 
test_data.lo -MD -MP -MF .deps/test_data.Tpo -c test_data.cpp -o test_data.o 
>/dev/null 2>&1
mv -f .deps/test_data.Tpo .deps/test_data.Plo
/bin/bash ../../libtool  --tag=CXX   --mode=compile x86_64-linux-gnu-g++ 
-DHAVE_CONFIG_H   -I../.. -DDEBUG__LEVEL__=2 -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -pedantic -Wno-unused-function -MT 
test_exception.lo -MD -MP -MF .deps/test_exception.Tpo -c -o test_exception.lo 
test_exception.cpp
libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I../.. 
-DDEBUG__LEVEL__=2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -pedantic -Wno-unused-function -MT 
test_exception.lo -MD -MP -MF .deps/test_exception.Tpo -c test_exception.cpp  
-fPIC -DPIC -o .libs/test_exception.o
libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I../.. 
-DDEBUG__LEVEL__=2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -pedantic -Wno-unused-function -MT 
test_exception.lo -MD -MP -MF .deps/test_exception.Tpo -c test_exception.cpp -o 
test_exception.o >/dev/null 2>&1
mv -f .deps/test_exception.Tpo .deps/test_exception.Plo
/bin/bash ../../libtool  --tag=CXX   --mode=compile x86_64-linux-gnu-g++ 
-DHAVE_CONFIG_H   -I../.. -DDEBUG__LEVEL__=2 -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -pedantic -Wno-unused-function -MT 
test_suite.lo -MD -MP -MF .deps/test_suite.Tpo -c -o test_suite.lo 
test_suite.cpp
libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I../.. 
-DDEBUG__LEVEL__=2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -pedantic -Wno-unused-function -MT 
test_suite.lo -MD -MP -MF .deps/test_suite.Tpo -c test_suite.cpp  -fPIC -DPIC 
-o .libs/test_suite.o
libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I../.. 
-DDEBUG__LEVEL__=2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -pedantic -Wno-unused-function -MT 
test_suite.lo -MD -MP -MF .deps/test_suite.Tpo -c 

Bug#1020389: marked as done (init-system-helpers: block migration waiting for #926699 #1020312 #1019985 #1019506)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 23:33:03 +0100
with message-id <0c8281692cf995e083d8a1f612a31686b360017e.ca...@debian.org>
and subject line Re: init-system-helpers: block migration waiting for #926699 
#1020312 #1019985 #1019506
has caused the Debian Bug report #1020389,
regarding init-system-helpers: block migration waiting for #926699 #1020312 
#1019985 #1019506
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.)


-- 
1020389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: init-system-helpers
Version: 1.65
Severity: grave
Justification: waiting for usrmerge fixes to migrate

Temporarily block migration until the following fixes have migrated to
testing:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020312
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926699
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019985
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019506

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
i-s-h has already migrated, and usrmerge will migrate now, so closing.

-- 
Kind regards,
Luca Boccassi


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

Bug#1020441: linux: autopkgtest needs update for new version of gcc-11

[Salvatore Bonaccorso]

Hi,

On Wed, Sep 21, 2022 at 09:23:59PM +0200, Paul Gevers wrote:
> Source: linux
> Version: 5.19.6-1
> Severity: serious
> X-Debbugs-CC: gcc...@packages.debian.org
> Tags: sid bookworm
> User: debian...@lists.debian.org
> Usertags: needs-update
> Control: affects -1 src:gcc-11
> 
> Dear maintainer(s),
> 
> With a recent upload of gcc-11 the autopkgtest of linux fails in testing
> when that autopkgtest is run with the binary packages of gcc-11 from
> unstable. It passes when run with only packages from testing (it also fails
> in testing). In tabular form:
> 
>passfail
> gcc-11 from testing11.3.0-6
> linux  from testing5.19.6-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 gcc-11 to testing
> [1]. Of course, gcc-11 shouldn't just break your autopkgtest (or even worse,
> your package), but it seems to me that the test "only" fails on "Unexpected
> warning" and your package needs to update to the new situation.
> 
> If this is a real problem in your package (and not only in your
> autopkgtest), the right binary package(s) from gcc-11 should really add a
> versioned Breaks on the unfixed version of (one of your) package(s). Note:
> the Breaks is nice even if the issue is only in the autopkgtest as it helps
> the migration software to figure out the right versions to combine in the
> tests.
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul
> 
> [1] https://qa.debian.org/excuses.php?package=gcc-11
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/l/linux/26272813/log.gz
> 
> I: Found quick flavour cloud-amd64
> I: Build for 5.19.0-1-cloud-amd64
> make: Entering directory '/usr/src/linux-headers-5.19.0-1-cloud-amd64'
> test -e include/generated/autoconf.h -a -e include/config/auto.conf || (  
> \
> echo >&2; \
> echo >&2 "  ERROR: Kernel configuration is invalid."; \
> echo >&2 " include/generated/autoconf.h or include/config/auto.conf
> are missing.";\
> echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix
> it."; \
> echo >&2 ;\
> /bin/false)
> warning: the compiler differs from the one used to build the kernel
>   The kernel was built by: gcc-11 (Debian 11.3.0-5) 11.3.0
>   You are using:   gcc-11 (Debian 11.3.0-6) 11.3.0
> make -f /usr/src/linux-headers-5.19.0-1-common/scripts/Makefile.build
> obj=/tmp/autopkgtest-lxc.8_h2xh0q/downtmp/autopkgtest_tmp/foo \
> single-build= \
> need-builtin=1 need-modorder=1
>gcc-11
> -Wp,-MMD,/tmp/autopkgtest-lxc.8_h2xh0q/downtmp/autopkgtest_tmp/foo/.foo.o.d
> -nostdinc -I/usr/src/linux-headers-5.19.0-1-common/arch/x86/include
> -I./arch/x86/include/generated
> -I/usr/src/linux-headers-5.19.0-1-common/include -I./include
> -I/usr/src/linux-headers-5.19.0-1-common/arch/x86/include/uapi
> -I./arch/x86/include/generated/uapi
> -I/usr/src/linux-headers-5.19.0-1-common/include/uapi
> -I./include/generated/uapi -include
> /usr/src/linux-headers-5.19.0-1-common/include/linux/compiler-version.h
> -include /usr/src/linux-headers-5.19.0-1-common/include/linux/kconfig.h
> -include
> /usr/src/linux-headers-5.19.0-1-common/include/linux/compiler_types.h
> -D__KERNEL__ -fmacro-prefix-map=/usr/src/linux-headers-5.19.0-1-common/=
> -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing
> -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration
> -Werror=implicit-int -Werror=return-type -Wno-format-security -std=gnu11
> -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64
> -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387
> -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone
> -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables
> -mindirect-branch=thunk-extern -mindirect-branch-register
> -mindirect-branch-cs-prefix -mfunction-return=thunk-extern -fno-jump-tables
> -mharden-sls=all -fno-delete-null-pointer-checks -Wno-frame-address
> -Wno-format-truncation -Wno-format-overflow -Wno-address-of-packed-member
> -O2 -fno-allow-store-data-races -Wframe-larger-than=2048
> -fstack-protector-strong -Wimplicit-fallthrough=5 -Wno-main
> -Wno-unused-but-set-variable -Wno-unused-const-variable
> -fno-stack-clash-protection -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY
> -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wcast-function-type
> -Wno-stringop-truncation -Wno-stringop-overflow -Wno-restrict
> -Wno-maybe-uninitialized -Wno-alloc-size-larger-than -fno-strict-overflow
> -fno-stack-check -fconserve-stack -Werror=date-time
> -Werror=incompatible-pointer-types -Werror=designated-init
> 

Processed: forcibly merging 1020441 1019749

[Debian Bug Tracking System]

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

> # merging the previous reported one into 1020441 and perserving all 
> release-team needed usertags
> forcemerge 1020441 1019749
Bug #1020441 [src:linux] linux: autopkgtest needs update for new version of 
gcc-11
Bug #1019749 [src:linux] linux autopkg tests fail with stderr output, blocking 
gcc-11
Added indication that 1019749 affects src:gcc-11
Merged 1019749 1020441
> thanks
Stopping processing here.

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

Bug#1020456: cypari2 FTBFS with PARI 2.15.0

[Adrian Bunk]

Source: cypari2
Version: 2.1.2-2
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/logs.php?pkg=cypari2=2.1.2-2%2Bb3

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
python3 tests/rundoctest.py
  ***   user warning: test
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 197450664 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 241740752 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 248010168 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 252956360 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 258607552 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 209447264 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 215847936 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 190613912 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 178484864 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",
/usr/lib/python3.10/doctest.py:1350: RuntimeWarning: cypari2 leaked 180449432 
bytes on the PARI stack
  exec(compile(example.source, filename, "single",

Testing cypari2.closure
**
File 
"/<>/.pybuild/cpython3_3.10_cypari2/build/cypari2/closure.cpython-310-x86_64-linux-gnu.so",
 line ?, in cypari2.closure.__test__.objtoclosure (line 145)
Failed example:
mul([1], [2])
Differences (ndiff with -expected +actual):
  Traceback (most recent call last):
- ...
- PariError: call_python: forbidden multiplication t_VEC (1 elts) * t_VEC 
(1 elts)
+   File "/usr/lib/python3.10/doctest.py", line 1350, in __run
+ exec(compile(example.source, filename, "single",
+   File "", 
line 1, in 
+ mul([1], [2])
+   File "cypari2/gen.pyx", line 4107, in cypari2.gen.Gen.__call__
+ sig_on()
+   File "cypari2/handle_error.pyx", line 213, in 
cypari2.handle_error._pari_err_handle
+ raise PariError(errnum, pari_error_string, clone_gen_noclear(E))
+ PariError: call_python: incorrect type in qfbcomp (t_VEC)
**
File 
"/<>/.pybuild/cpython3_3.10_cypari2/build/cypari2/closure.cpython-310-x86_64-linux-gnu.so",
 line ?, in cypari2.closure.objtoclosure
Failed example:
mul([1], [2])
Differences (ndiff with -expected +actual):
  Traceback (most recent call last):
- ...
- PariError: call_python: forbidden multiplication t_VEC (1 elts) * t_VEC 
(1 elts)
+   File "/usr/lib/python3.10/doctest.py", line 1350, in __run
+ exec(compile(example.source, filename, "single",
+   File "", line 1, in 
+ mul([1], [2])
+   File "cypari2/gen.pyx", line 4107, in cypari2.gen.Gen.__call__
+ sig_on()
+   File "cypari2/handle_error.pyx", line 213, in 
cypari2.handle_error._pari_err_handle
+ raise PariError(errnum, pari_error_string, clone_gen_noclear(E))
+ PariError: call_python: incorrect type in qfbcomp (t_VEC)
**
2 items had failures:
   1 of  19 in cypari2.closure.__test__.objtoclosure (line 145)
   1 of  19 in cypari2.closure.objtoclosure
***Test Failed*** 2 failures.

Testing cypari2.convert

Testing cypari2.gen
**
File 
"/<>/.pybuild/cpython3_3.10_cypari2/build/cypari2/gen.cpython-310-x86_64-linux-gnu.so",
 line ?, in cypari2.gen.Gen.__complex__
Failed example:
complex(g)
Differences (ndiff with -expected +actual):
- (2.2847006554165614+0j)
+ (1.118033988749895+0j)
**
File 
"/<>/.pybuild/cpython3_3.10_cypari2/build/cypari2/gen.cpython-310-x86_64-linux-gnu.so",
 line ?, in cypari2.gen.__test__.Gen.__complex__ (line 2006)
Failed example:
complex(g)
Differences (ndiff with -expected +actual):
- (2.2847006554165614+0j)
+ (1.118033988749895+0j)

Processed: tagging 983982

[Debian Bug Tracking System]

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

> tags 983982 + pending
Bug #983982 [src:bazel-bootstrap] bazel-bootstrap: ftbfs with GCC-11
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1016976: marked as done (connman: CVE-2022-32292 CVE-2022-32293)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 20:04:18 +
with message-id 
and subject line Bug#1016976: fixed in connman 1.36-2.2+deb11u1
has caused the Debian Bug report #1016976,
regarding connman: CVE-2022-32292 CVE-2022-32293
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.)


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

Hi,

The following vulnerabilities were published for connman.

CVE-2022-32292[0]:
| In ConnMan through 1.41, remote attackers able to send HTTP requests
| to the gweb component are able to exploit a heap-based buffer overflow
| in received_data to execute code.

https://lore.kernel.org/connman/20220801080043.4861-5-w...@monom.org/
https://bugzilla.suse.com/show_bug.cgi?id=1200189

CVE-2022-32293[1]:
| In ConnMan through 1.41, a man-in-the-middle attack against a WISPR
| HTTP query could be used to trigger a use-after-free in WISPR
| handling, leading to crashes or code execution.

https://lore.kernel.org/connman/20220801080043.4861-1-w...@monom.org/
https://lore.kernel.org/connman/20220801080043.4861-3-w...@monom.org/
https://bugzilla.suse.com/show_bug.cgi?id=1200190

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-32292
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32292
[1] https://security-tracker.debian.org/tracker/CVE-2022-32293
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32293

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: connman
Source-Version: 1.36-2.2+deb11u1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated connman 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, 03 Sep 2022 20:04:37 +0200
Source: connman
Architecture: source
Version: 1.36-2.2+deb11u1
Distribution: bullseye-security
Urgency: high
Maintainer: Alexander Sack 
Changed-By: Salvatore Bonaccorso 
Closes: 1004935 1016976
Changes:
 connman (1.36-2.2+deb11u1) bullseye-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * dnsproxy: Simplify udp_server_event()
   * dnsproxy: Validate input data before using them (CVE-2022-23096,
 CVE-2022-23097) (Closes: #1004935)
   * dnsproxy: Avoid 100 % busy loop in TCP server case (CVE-2022-23098)
 (Closes: #1004935)
   * dnsproxy: Keep timeout in TCP case even after connection is established
 (CVE-2022-23098) (Closes: #1004935)
   * gweb: Fix OOB write in received_data() (CVE-2022-32292) (Closes: #1016976)
   * wispr: Add reference counter to portal context (CVE-2022-32293)
 (Closes: #1016976)
   * wispr: Update portal context references (CVE-2022-32293)
 (Closes: #1016976)
Checksums-Sha1:
 4b415ca30b4a554a59b566236f7e62e99716ad49 2377 connman_1.36-2.2+deb11u1.dsc
 8f29df34231c214c06ee6eca9ed7c233212b8d12 692616 connman_1.36.orig.tar.xz
 880a95660f928bc9c4b494d8860ad01271775f5a 20920 
connman_1.36-2.2+deb11u1.debian.tar.xz
 677d1311322b008494b45a76390516109a5668db 7331 
connman_1.36-2.2+deb11u1_source.buildinfo
Checksums-Sha256:
 bcd701c51507610529ac58e12199209e3c01a009cf74411def6f9e9f719c7f27 2377 
connman_1.36-2.2+deb11u1.dsc
 c789db41cc443fa41e661217ea321492ad59a004bebcd1aa013f3bc10a6e0074 692616 
connman_1.36.orig.tar.xz
 0e9e188c7e29c002c0957d664200cdd90bfaff2e4cc155909ecc54709fb5ba55 20920 
connman_1.36-2.2+deb11u1.debian.tar.xz
 27296ea458caf034d6963883d0bf9b6b1a769f447e002bf1f63c9f351b9ba054 7331 
connman_1.36-2.2+deb11u1_source.buildinfo
Files:
 bc75d63ae61dd5bddf2e4c5eaab02e8f 2377 net optional connman_1.36-2.2+deb11u1.dsc
 dae77d9c904d2c223ae849e32079d57e 692616 net optional 

Bug#1004935: marked as done (connman: CVE-2022-23096 CVE-2022-23097 CVE-2022-23098)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 20:04:18 +
with message-id 
and subject line Bug#1004935: fixed in connman 1.36-2.2+deb11u1
has caused the Debian Bug report #1004935,
regarding connman: CVE-2022-23096 CVE-2022-23097 CVE-2022-23098
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.)


-- 
1004935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: connman
Version: 1.36-2.3
Severity: grave
Tags: security upstream
Forwarded: https://lore.kernel.org/connman/20220125090026.5108-1-w...@monom.org/
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1.36-2.2
Control: found -1 1.36-2.1~deb10u1
Control: found -1 1.36-2.1~deb10u2

Hi,

The following vulnerabilities were published for connman.

CVE-2022-23096[0]:
| An issue was discovered in the DNS proxy in Connman through 1.40. The
| TCP server reply implementation lacks a check for the presence of
| sufficient Header Data, leading to an out-of-bounds read.


CVE-2022-23097[1]:
| An issue was discovered in the DNS proxy in Connman through 1.40.
| forward_dns_reply mishandles a strnlen call, leading to an out-of-
| bounds read.


CVE-2022-23098[2]:
| An issue was discovered in the DNS proxy in Connman through 1.40. The
| TCP server reply implementation has an infinite loop if no data is
| received.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-23096
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23096
[1] https://security-tracker.debian.org/tracker/CVE-2022-23097
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23097
[2] https://security-tracker.debian.org/tracker/CVE-2022-23098
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23098

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: connman
Source-Version: 1.36-2.2+deb11u1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated connman 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, 03 Sep 2022 20:04:37 +0200
Source: connman
Architecture: source
Version: 1.36-2.2+deb11u1
Distribution: bullseye-security
Urgency: high
Maintainer: Alexander Sack 
Changed-By: Salvatore Bonaccorso 
Closes: 1004935 1016976
Changes:
 connman (1.36-2.2+deb11u1) bullseye-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * dnsproxy: Simplify udp_server_event()
   * dnsproxy: Validate input data before using them (CVE-2022-23096,
 CVE-2022-23097) (Closes: #1004935)
   * dnsproxy: Avoid 100 % busy loop in TCP server case (CVE-2022-23098)
 (Closes: #1004935)
   * dnsproxy: Keep timeout in TCP case even after connection is established
 (CVE-2022-23098) (Closes: #1004935)
   * gweb: Fix OOB write in received_data() (CVE-2022-32292) (Closes: #1016976)
   * wispr: Add reference counter to portal context (CVE-2022-32293)
 (Closes: #1016976)
   * wispr: Update portal context references (CVE-2022-32293)
 (Closes: #1016976)
Checksums-Sha1:
 4b415ca30b4a554a59b566236f7e62e99716ad49 2377 connman_1.36-2.2+deb11u1.dsc
 8f29df34231c214c06ee6eca9ed7c233212b8d12 692616 connman_1.36.orig.tar.xz
 880a95660f928bc9c4b494d8860ad01271775f5a 20920 
connman_1.36-2.2+deb11u1.debian.tar.xz
 677d1311322b008494b45a76390516109a5668db 7331 
connman_1.36-2.2+deb11u1_source.buildinfo
Checksums-Sha256:
 bcd701c51507610529ac58e12199209e3c01a009cf74411def6f9e9f719c7f27 2377 
connman_1.36-2.2+deb11u1.dsc
 c789db41cc443fa41e661217ea321492ad59a004bebcd1aa013f3bc10a6e0074 692616 
connman_1.36.orig.tar.xz
 0e9e188c7e29c002c0957d664200cdd90bfaff2e4cc155909ecc54709fb5ba55 20920 
connman_1.36-2.2+deb11u1.debian.tar.xz
 27296ea458caf034d6963883d0bf9b6b1a769f447e002bf1f63c9f351b9ba054 7331 

Bug#1020447: src:aircrack-ng: fails to migrate to testing for too long: not build on s390x

[Paul Gevers]

Source: aircrack-ng
Version: 1:1.6+git20210130.91820bc-2
Severity: serious
Control: close -1 1:1.7-3
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:aircrack-ng has been trying to migrate for 
69 days [2]. Hence, I am filing this bug. Your package stopped building 
on s390x, because it FTBFS there, but the binaries are still lingering 
around. The s390x situation needs to be resolved somehow.


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=aircrack-ng



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:aircrack-ng: fails to migrate to testing for too long: not build on s390x

[Debian Bug Tracking System]

Processing control commands:

> close -1 1:1.7-3
Bug #1020447 [src:aircrack-ng] src:aircrack-ng: fails to migrate to testing for 
too long: not build on s390x
Marked as fixed in versions aircrack-ng/1:1.7-3.
Bug #1020447 [src:aircrack-ng] src:aircrack-ng: fails to migrate to testing for 
too long: not build on s390x
Marked Bug as done

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

Bug#1020445: numba: autopkgtest regression on ppc64el: inf != 0.625

[Paul Gevers]

Source: numba
Version: 0.52.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it recently started
to fail in testing on ppc64el. It also has never passed on armel, armhf 
and s390x. I'm not sure what to make of all the recent migration run 
failures on amd64, arm64 and i386, but the test *appears* to be flaky.


Paul

https://ci.debian.net/data/autopkgtest/testing/ppc64el/n/numba/26229968/log.gz

==
FAIL: test_ldexp (numba.tests.test_mathlib.TestMathLib)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/numba/tests/test_mathlib.py", 
line 648, in test_ldexp

self.assertPreciseEqual(cfunc(*args), pyfunc(*args))
  File "/usr/lib/python3/dist-packages/numba/tests/support.py", line 
378, in assertPreciseEqual
self.fail("when comparing %s and %s: %s" % (first, second, 
failure_msg))

AssertionError: when comparing inf and 0.625: inf != 0.625

==
FAIL: test_ldexp_npm (numba.tests.test_mathlib.TestMathLib)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/numba/tests/test_mathlib.py", 
line 651, in test_ldexp_npm

self.test_ldexp(flags=no_pyobj_flags)
  File "/usr/lib/python3/dist-packages/numba/tests/test_mathlib.py", 
line 648, in test_ldexp

self.assertPreciseEqual(cfunc(*args), pyfunc(*args))
  File "/usr/lib/python3/dist-packages/numba/tests/support.py", line 
378, in assertPreciseEqual
self.fail("when comparing %s and %s: %s" % (first, second, 
failure_msg))

AssertionError: when comparing inf and 0.625: inf != 0.625



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1020090: marked as done (python-unicodedata2: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_build] Error 1)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 19:36:47 +
with message-id 
and subject line Bug#1020090: fixed in python-unicodedata2 14.0.0+ds2-1
has caused the Debian Bug report #1020090,
regarding python-unicodedata2: FTBFS: make[1]: *** [debian/rules:16: 
override_dh_auto_build] 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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Generate unicode data headers
> mkdir -p data
> unicode_ver=`dpkg -s unicode-data | grep '^Version: ' | sed 's/^Version: 
> \(.*\)-.*$/\1/'`; \
> for i in `ls /usr/share/unicode/*.txt | xargs -n1 basename`; do \
>   ln -s "/usr/share/unicode/${i}" "data/${i%.txt}-${unicode_ver}.txt" ; \
> done
> bunzip2 -ckd /usr/share/unicode/Unihan_NumericValues.txt.bz2 > 
> data/Unihan_NumericValues.txt
> python3 makeunicodedata.py
> --- Reading UnicodeData.txt ...
> Traceback (most recent call last):
>   File "/<>/makeunicodedata.py", line 1349, in 
> maketables(1)
>   File "/<>/makeunicodedata.py", line 117, in maketables
> unicode = UnicodeData(UNIDATA_VERSION)
>   File "/<>/makeunicodedata.py", line 997, in __init__
> for s in UcdFile(UNICODE_DATA, version):
>   File "/<>/makeunicodedata.py", line 927, in records
> with open_data(self.template, self.version) as file:
>   File "/<>/makeunicodedata.py", line 891, in open_data
> raise Exception(f'file not found: {local}')
> Exception: file not found: data/UnicodeData-14.0.0.txt
> make[1]: *** [debian/rules:16: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/python-unicodedata2_14.0.0+ds-8_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-unicodedata2
Source-Version: 14.0.0+ds2-1
Done: Boyuan Yang 

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated python-unicodedata2 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, 21 Sep 2022 13:34:24 -0400
Source: python-unicodedata2
Architecture: source
Version: 14.0.0+ds2-1
Distribution: unstable
Urgency: high
Maintainer: Debian Fonts Task Force 
Changed-By: Boyuan Yang 
Closes: 1020090
Changes:
 python-unicodedata2 (14.0.0+ds2-1) unstable; urgency=high
 .
   * Team upload.
   * New upstream snapshot 2022-09-15.
 + Fix FTBFS with unicode-data 15.0.0-1. (Closes: #1020090)
   * debian/control: Hardcode rebuild with unicode-data/15.0.0-1.
   * debian/control: Add build-test-dependency pytest and coverage.
   * debian/patches: Refresh patches.
   * debian/rules: Use dh13 syntax.
Checksums-Sha1:
 19f1836c092aea5079fef9cd198c6e56ab6cb35c 2328 
python-unicodedata2_14.0.0+ds2-1.dsc
 1ae1f3cca9e0a2ede77d31d1efdc0caf98e2f41c 32584 
python-unicodedata2_14.0.0+ds2.orig.tar.xz
 fa4a2dd6e03ba55431e70215c778a49e25a64b11 6032 
python-unicodedata2_14.0.0+ds2-1.debian.tar.xz
 

Processed: heimdal breaks openldap autopkgtest: test smbk5pwd

[Debian Bug Tracking System]

Processing control commands:

> found -1 heimdal/7.7.0+dfsg-6
Bug #1020442 [src:heimdal, src:openldap] heimdal breaks openldap autopkgtest: 
test smbk5pwd
Marked as found in versions heimdal/7.7.0+dfsg-6.
> found -1 openldap/2.5.12+dfsg-2
Bug #1020442 [src:heimdal, src:openldap] heimdal breaks openldap autopkgtest: 
test smbk5pwd
Marked as found in versions openldap/2.5.12+dfsg-2.

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

Bug#1020442: heimdal breaks openldap autopkgtest: test smbk5pwd

[Paul Gevers]

Source: heimdal, openldap
Control: found -1 heimdal/7.7.0+dfsg-6
Control: found -1 openldap/2.5.12+dfsg-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of heimdal the autopkgtest of openldap fails in 
testing when that autopkgtest is run with the binary packages of heimdal 
from unstable. It passes when run with only packages from testing (I 
note that the test in  unstable with the new version of openldap is also 
broken with seemingly the same output). In tabular form:


   passfail
heimdalfrom testing7.7.0+dfsg-6
openldap   from testing2.5.12+dfsg-2
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 heimdal to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

Paul

[1] https://qa.debian.org/excuses.php?package=heimdal

https://ci.debian.net/data/autopkgtest/testing/amd64/o/openldap/26275057/log.gz

SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "cn=samba,cn=schema,cn=config"

SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "cn=hdb,cn=schema,cn=config"

SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
ldap_add: Other (e.g., implementation specific) error (80)
additional info:  handler exited with 1
modifying entry "cn=module{0},cn=config"

adding new entry "olcOverlay=smbk5pwd,olcDatabase={1}mdb,cn=config"

autopkgtest [00:24:46]: test smbk5pwd



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1020441: linux: autopkgtest needs update for new version of gcc-11

[Paul Gevers]

Source: linux
Version: 5.19.6-1
Severity: serious
X-Debbugs-CC: gcc...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gcc-11

Dear maintainer(s),

With a recent upload of gcc-11 the autopkgtest of linux fails in testing 
when that autopkgtest is run with the binary packages of gcc-11 from 
unstable. It passes when run with only packages from testing (it also 
fails in testing). In tabular form:


   passfail
gcc-11 from testing11.3.0-6
linux  from testing5.19.6-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 gcc-11 to testing 
[1]. Of course, gcc-11 shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the test "only" fails on 
"Unexpected warning" and your package needs to update to the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from gcc-11 should really add 
a versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


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

Paul

[1] https://qa.debian.org/excuses.php?package=gcc-11

https://ci.debian.net/data/autopkgtest/testing/amd64/l/linux/26272813/log.gz

I: Found quick flavour cloud-amd64
I: Build for 5.19.0-1-cloud-amd64
make: Entering directory '/usr/src/linux-headers-5.19.0-1-cloud-amd64'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo >&2;\
echo >&2 "  ERROR: Kernel configuration is invalid.";  \
echo >&2 " include/generated/autoconf.h or 
include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to 
fix it.";	\

echo >&2 ;   \
/bin/false)
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc-11 (Debian 11.3.0-5) 11.3.0
  You are using:   gcc-11 (Debian 11.3.0-6) 11.3.0
make -f /usr/src/linux-headers-5.19.0-1-common/scripts/Makefile.build 
obj=/tmp/autopkgtest-lxc.8_h2xh0q/downtmp/autopkgtest_tmp/foo \

single-build= \
need-builtin=1 need-modorder=1
   gcc-11 
-Wp,-MMD,/tmp/autopkgtest-lxc.8_h2xh0q/downtmp/autopkgtest_tmp/foo/.foo.o.d 
-nostdinc -I/usr/src/linux-headers-5.19.0-1-common/arch/x86/include 
-I./arch/x86/include/generated 
-I/usr/src/linux-headers-5.19.0-1-common/include -I./include 
-I/usr/src/linux-headers-5.19.0-1-common/arch/x86/include/uapi 
-I./arch/x86/include/generated/uapi 
-I/usr/src/linux-headers-5.19.0-1-common/include/uapi 
-I./include/generated/uapi -include 
/usr/src/linux-headers-5.19.0-1-common/include/linux/compiler-version.h 
-include /usr/src/linux-headers-5.19.0-1-common/include/linux/kconfig.h 
-include 
/usr/src/linux-headers-5.19.0-1-common/include/linux/compiler_types.h 
-D__KERNEL__ -fmacro-prefix-map=/usr/src/linux-headers-5.19.0-1-common/= 
-Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs 
-fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE 
-Werror=implicit-function-declaration -Werror=implicit-int 
-Werror=return-type -Wno-format-security -std=gnu11 -mno-sse -mno-mmx 
-mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64 -falign-jumps=1 
-falign-loops=1 -mno-80387 -mno-fp-ret-in-387 
-mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic 
-mno-red-zone -mcmodel=kernel -Wno-sign-compare 
-fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern 
-mindirect-branch-register -mindirect-branch-cs-prefix 
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all 
-fno-delete-null-pointer-checks -Wno-frame-address 
-Wno-format-truncation -Wno-format-overflow 
-Wno-address-of-packed-member -O2 -fno-allow-store-data-races 
-Wframe-larger-than=2048 -fstack-protector-strong 
-Wimplicit-fallthrough=5 -Wno-main -Wno-unused-but-set-variable 
-Wno-unused-const-variable -fno-stack-clash-protection -pg 
-mrecord-mcount -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement 
-Wvla -Wno-pointer-sign -Wcast-function-type -Wno-stringop-truncation 
-Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized 
-Wno-alloc-size-larger-than -fno-strict-overflow -fno-stack-check 
-fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types 
-Werror=designated-init -Wno-packed-not-aligned -g  -DMODULE 
-DKBUILD_BASENAME='"foo"' -DKBUILD_MODNAME='"foo"' 
-D__KBUILD_MODNAME=kmod_foo -c -o 
/tmp/autopkgtest-lxc.8_h2xh0q/downtmp/autopkgtest_tmp/foo/foo.o 

Processed: linux: autopkgtest needs update for new version of gcc-11

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:gcc-11
Bug #1020441 [src:linux] linux: autopkgtest needs update for new version of 
gcc-11
Added indication that 1020441 affects src:gcc-11

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

Bug#1020404: luakit: aborts at start

[Markus Demleitner]

On Wed, Sep 21, 2022 at 11:36:08AM +0200, Arne Wichmann wrote:
> Bail out! ERROR:common/util.c:67:strip_ansi_escapes: assertion failed (err == 
> NULL): Error while compiling regular expression 
> ?[\u001b\u009b][[()#;?]*(?:[0-9]{1,4}(?:;[0-9]{0,4})*)?[0-9A-ORZcf-nqry=><]? 
> at char 3: unrecognised character following \ (g-regex-error-quark, 103)

Argl.  That's quite certainly the upstream bug
https://github.com/luakit/luakit/issues/1005

I've not commented on this because I was not really sure what
encoding the gchar *in would be -- if it's UCS-2, then the
complicated \u escapes make sense.  If it's UTF-8, a simple \x1b
would do the job.

Even more importantly, looking at where this code is being used (when
formatting tracebacks, and when writing via va_log when things are
going to a file), I'm now convinced that this is a lot less critical
than I first thought.  In particular, javascript console.log is *not*
sanitised at all, let alone by this code; to see that, run

  luakit http://www.tfiu.de/log-escape.html |& cat

(if you still have a running luakit somewhere) -- you'll see that the
colored messages are now b/w, but the escape sequence from javascript
is not filtered (which would feel like a good idea), so you end up
with a terminal writing in reverse video.

I hence felt it's ok to just experiment, and it seems we're talking
about UTF-8 strings here.

Can you build from https://salsa.debian.org/debian/luakit.git and see
whether the thing (a) builds and (b) whether luakit's log messages
are b/w when filtered through cat as above?

Thanks,

   Markus

Processed: tagging 1016939

[Debian Bug Tracking System]

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

> tags 1016939 + pending
Bug #1016939 [src:padthv1] : flaky autopkgtest: padthv1_jack: no process found
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: src:xmonad-contrib: fails to migrate to testing for too long: part of unfinshed ghc transition?

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.17.0-1
Bug #1020440 [src:xmonad-contrib] src:xmonad-contrib: fails to migrate to 
testing for too long: part of unfinshed ghc transition?
Marked as fixed in versions xmonad-contrib/0.17.0-1.
Bug #1020440 [src:xmonad-contrib] src:xmonad-contrib: fails to migrate to 
testing for too long: part of unfinshed ghc transition?
Marked Bug as done

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

Bug#1020440: src:xmonad-contrib: fails to migrate to testing for too long: part of unfinshed ghc transition?

[Paul Gevers]

Source: xmonad-contrib
Version: 0.16-1
Severity: serious
Control: close -1 0.17.0-1
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:xmonad-contrib has been trying to migrate 
for 61 days [2]. Hence, I am filing this bug. Your package is part of 
the unfinished ghc transition.


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=xmonad-contrib



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1020439: src:xmonad: fails to migrate to testing for too long: part of unfinshed ghc transition?

[Paul Gevers]

Source: xmonad
Version: 0.15-4
Severity: serious
Control: close -1 0.17.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:xmonad has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package is part of the 
unfinished ghc transition.


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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:xmonad: fails to migrate to testing for too long: part of unfinshed ghc transition?

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.17.0-2
Bug #1020439 [src:xmonad] src:xmonad: fails to migrate to testing for too long: 
part of unfinshed ghc transition?
Marked as fixed in versions xmonad/0.17.0-2.
Bug #1020439 [src:xmonad] src:xmonad: fails to migrate to testing for too long: 
part of unfinshed ghc transition?
Marked Bug as done

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

Bug#1020257: marked as done (libuhd4.3.0-dpdk-tests: ships files in /usr/lib/uhd/tests/4.2.0/)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 18:43:46 +
with message-id 
and subject line Bug#1020257: fixed in uhd 4.3.0.0+ds1-2
has caused the Debian Bug report #1020257,
regarding libuhd4.3.0-dpdk-tests: ships files in /usr/lib/uhd/tests/4.2.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.)


-- 
1020257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libuhd4.3.0-dpdk-tests
Version: 4.3.0.0+ds1-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 libuhd4.3.0-dpdk-tests.
  Preparing to unpack .../libuhd4.3.0-dpdk-tests_4.3.0.0+ds1-1_amd64.deb ...
  Unpacking libuhd4.3.0-dpdk-tests (4.3.0.0+ds1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libuhd4.3.0-dpdk-tests_4.3.0.0+ds1-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/uhd/tests/4.2.0/dpdk_port_test', which is also 
in package libuhd4.2.0-dpdk-tests 4.2.0.1+ds1-1+b1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libuhd4.3.0-dpdk-tests_4.3.0.0+ds1-1_amd64.deb

I don't think it was intended to ship files in the "old" location.


cheers,

Andreas


libuhd4.2.0-dpdk-tests=4.2.0.1+ds1-1+b1_libuhd4.3.0-dpdk-tests=4.3.0.0+ds1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: uhd
Source-Version: 4.3.0.0+ds1-2
Done: A. Maitland Bottoms 

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

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

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated uhd 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, 21 Sep 2022 06:26:19 -0400
Source: uhd
Architecture: source
Version: 4.3.0.0+ds1-2
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Closes: 1020257
Changes:
 uhd (4.3.0.0+ds1-2) unstable; urgency=medium
 .
   * Remove .dir file with old paths (Closes: #1020257)
Checksums-Sha1:
 1900b84c6a75f9116ec63d96b6865ddc6bf7c949 2840 uhd_4.3.0.0+ds1-2.dsc
 2229c3e792d657c60749826ed09785c4e3e06e7b 54052 uhd_4.3.0.0+ds1-2.debian.tar.xz
 00802a9ce5cab43165576c166d9a8fb047e4db0d 24771 
uhd_4.3.0.0+ds1-2_amd64.buildinfo
Checksums-Sha256:
 38fa70c7f9165a8c82f58de4e432e927f540b74f1aed418c5287a1f31612f209 2840 
uhd_4.3.0.0+ds1-2.dsc
 27e2e3241244f7d976e937e900aa33059d8d1e6668570b9e986c50608211e5f9 54052 
uhd_4.3.0.0+ds1-2.debian.tar.xz
 cd4b6e219c492a007dce4fceb378776c7dd02de73aa9efdc81e5ee01c91bf19d 24771 
uhd_4.3.0.0+ds1-2_amd64.buildinfo
Files:
 2b5c9b39766682e45ebda1cdfd5e9cbf 2840 science optional uhd_4.3.0.0+ds1-2.dsc
 1b10a547b688bcbf06232235a72b0873 54052 science optional 
uhd_4.3.0.0+ds1-2.debian.tar.xz
 4632d0a4fff96afd99f4de9a74bd4f5d 24771 science optional 
uhd_4.3.0.0+ds1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmMrKf0ACgkQUEHxiR9E
4JDQzBAAzGQdGm8wfrUTcMlxhqfnCEI2QcM6s7UFFrzWBXM+6/RGhZBRis670Le5
ospZteUFhwGMTQOKdYxUL4yegugg7UZ23CRY+Js9jTzkDySTdziGPCwxZAHQ64H2
GuucyyGSrs9lF56matlSo12Y6qmyH8Lt2ddqOdjMSDQpVO9sfwlfpfEY4Qbx5/hD
UtWHPoJbd2n4Fbf0gKs+Hr+YbIZrYYYVBGWE1YSGJ7Qbg65yJSaj+OpdMkJsd0j0
s+hNwKnqRSg1Y8FadpVzUp7qJVLflFTRV6sYBRCY4b9ea0ytA5vE86PMxH72YLCq
60slrLePpfObqgQ4wtoyU380gu6vriQHpI80GLNG0+Aw9tFAKvLUiAEyjwZvaNe3
mqVb3V1tPzAgfIQduPvllYJnnXkG0HXiAkJAoUBPUf7UQeqhEOPXx6QxoUZwsJGa
ITSXGN0gYDLOTDAjC4+xn4cNLa5v01uuGEH3fnNfwCBVwHWCLiu0p+VN/9NibHgQ
VJ1+loCwZ84HMfTlg6Tf+3vZRTUegYOpZbbXAulJlw/5zq9MS4tWy7KSILol/p6o
gZylfl8OjUIkDaDDqP6JwVbQbqCW3ImtCSF26ibMakYiIJvhg1jjsYx8zCNlnqx/
LGE0l5iLTouWK5Mo/bdrpsz4yyjWPjDK4s+Fbrnzl0eRx+QR4Z0=
=QTgH
-END PGP SIGNATURE End Message ---

Bug#1019923: marked as done (utf8proc: build-depends on unicode-data (< 14.1) but Unstable has 15.0.0-1)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 18:43:54 +
with message-id 
and subject line Bug#1019923: fixed in utf8proc 2.7.0-4
has caused the Debian Bug report #1019923,
regarding utf8proc: build-depends on unicode-data (< 14.1) but Unstable has 
15.0.0-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.)


-- 
1019923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: utf8proc
Version: 2.7.0-3
Severity: serious
Tags: ftbfs upstream bookworm sid

This week, there is a new Unicode 15 release. In Debian, unicode-data
has been updated to 15.0.0. utf8proc needs to be updated to building
against the current unicode-data in Debian.

This issue was detected by failing autopkgtests triggered by the new
unicode-data release.

Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: utf8proc
Source-Version: 2.7.0-4
Done: Mo Zhou 

We believe that the bug you reported is fixed in the latest version of
utf8proc, 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.
Mo Zhou  (supplier of updated utf8proc 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, 21 Sep 2022 10:22:38 -0400
Source: utf8proc
Architecture: source
Version: 2.7.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Julia Team 
Changed-By: Mo Zhou 
Closes: 1019923
Changes:
 utf8proc (2.7.0-4) unstable; urgency=medium
 .
   * Bump B-D to Unicode-data 15.0
   * Add patches to support Unicode-data 15.0.0 (Closes: #1019923)
Checksums-Sha1:
 9308c683767fd16a646454994c91eb04992d6040 2190 utf8proc_2.7.0-4.dsc
 8d778e0bd35ec5a69fc4b66c2c12e91a2c187405 36064 utf8proc_2.7.0-4.debian.tar.xz
 896064eb652558ec8d01cb168b5d0e07abecf20d 6231 utf8proc_2.7.0-4_source.buildinfo
Checksums-Sha256:
 106cc4f0cca6e27aa350d1c64fbd306e09aecd8ab9f6df6332cb363ac42b7bab 2190 
utf8proc_2.7.0-4.dsc
 47a48ec961ac56c38617bcf2e475aec3c64993eed3e1166d4dfa5dbdb5143095 36064 
utf8proc_2.7.0-4.debian.tar.xz
 bbf7d55de1a2d04e40aa1e9cd2bb7137871baaa7ef73e5d1c38d85077256a0d3 6231 
utf8proc_2.7.0-4_source.buildinfo
Files:
 79d4c347f85b2975f1dd077338aaac6f 2190 libs optional utf8proc_2.7.0-4.dsc
 06e7f31ffd6f82b7a87dd7723d8dba3c 36064 libs optional 
utf8proc_2.7.0-4.debian.tar.xz
 46eddffd926701e02d5c54ec759f7626 6231 libs optional 
utf8proc_2.7.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAmMrHtsRHGx1bWluQGRl
Ymlhbi5vcmcACgkQYmRes19oaoo/fw/+N4Ow2i9ykIroCh+4RR7lyxt40ah6+7MO
OraE5vo96aHMihkVvqUJqw3DHMihru6yj86iebK+gfr2qwMEag1HqrPcP6QoGz9q
Zt+vCGoc/myFPvGr/tok/796xZaPrcbEw82P/tHi1lEcWqYJCujCmTkhOzdIIGGK
jBoJngIGMtgy5yBDH5QCc6xJMnQSC65tPxMvOC8RfhTxqfSw1byljGSphVoSyMJm
Lf/mH2zWNcdE+bjaAKfrN4GDjMxUfZJz1q22mPiOvi9Y5wicPvDQQ74ux0k1+7fU
rZ/Tv2Kol8yYJcadyjFYUcEE3mb2OvtTYxeYI1CXDiFHxvIkV1EVbEQZJ8PWJajg
9yLxv+VuK4OxEpDv3KLd7MjPgQEq0ik8D2TR6UDf+OCGJK7Ez/cpViTtP5niEw61
59O1Kcc0WUa1Z0CtQ28ONiUf9FJ7WLPQzWeDU/eAy/XhRkXZT1nfHDgxYsS9eUYU
NKgGPueiIFaB1vC7IiB67xSaekSwPyp8TSF/WlaGEh67UR6CDh5Nsy8ChXt18q6j
VkLlS7oBlTbRq/Wk+4up2yKB8FMu/rgvQD8/8sScvfam448W+ei0fSeTOSwDfWlS
sIffoujME9ZoLsb+4Pk8tlnwo8B6AQhAakB8wVVB/MiNYY0kWxVizniKpgb28KVS
AHT7qVP/exQ=
=nhnH
-END PGP SIGNATURE End Message ---

Bug#1020437: clisp FTBFS with PARI 2.15.0

[Adrian Bunk]

Source: clisp
Version: 1:2.49.20210628.gitde01f0f-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=clisp=1%3A2.49.20210628.gitde01f0f-2%2Bb1

...
make[2]: Entering directory '/<>/debian/build/pari'
/<>/debian/build/clisp -K base  -E UTF-8 -Emisc 1:1 -Epathname 1:1 
-norc -q -c /<>/modules/pari/desc2lisp.lisp -o ./
;; Compiling file /<>/modules/pari/desc2lisp.lisp ...
;; Wrote file /<>/debian/build/pari/desc2lisp.fas
0 errors, 0 warnings
/<>/debian/build/clisp -K base  -E UTF-8 -Emisc 1:1 -Epathname 1:1 
-norc -q -i desc2lisp -c /<>/modules/pari/pari.lisp -o ./ 
/usr/share/pari
;; Loading file /<>/debian/build/pari/desc2lisp.fas ...
;; Loaded file /<>/debian/build/pari/desc2lisp.fas
;; Compiling file /<>/modules/pari/pari.lisp ...
Reading "/usr/share/pari/pari.desc" (1,704,497 bytes)
WARNING: Existing name: "arg" (arg :INTERNAL)
WARNING: Existing name: "arity" (arity :INTERNAL)
WARNING: Existing name: "default" (default :INTERNAL)
WARNING: Existing name: "digits" (digits :INTERNAL)
*** - lines-to-desc: unknown field:
  "\\item $8192 = \\kbd{no_MinMax}$: do not print the boundary numbers (in 
both directions)."
The following functions were used but not defined:
 PARI::%I PARI::%component
0 errors, 4 warnings
make[2]: *** [Makefile:35: pari.c] Error 1

Bug#1016600: marked as done (siconos: vtk[6,7] removal)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 18:10:18 +
with message-id 
and subject line Bug#1016600: fixed in siconos 4.4.0+dfsg-1
has caused the Debian Bug report #1016600,
regarding siconos: vtk[6,7] removal
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.)


-- 
1016600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: siconos
Version: 4.3.1+dfsg-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm
Control: block 1016597 by -1
User: gl...@debian.org
Usertags: vtk6_vtk7_removal

Based on #1013156 and similar bugs:

Dear maintainer,

Debian archive has now three major versions of the VTK (The
Visualization Toolkit) package: vtk6, vtk7 and vtk9. Old vesions
(vtk6 and vtk7) are not supported by upstream and the package itself
is not easy for the mainance.

We aim to drop old and deprecated version vtk6 and vtk7 packages before
the freeze of the Debian 12 Bookworm. Your package depends on vtk6 or
vtk7. Thus we ask you to migrate it to the latest vtk9 package.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: siconos
Source-Version: 4.4.0+dfsg-1
Done: Stephen Sinclair 

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

Debian distribution maintenance software
pp.
Stephen Sinclair  (supplier of updated siconos package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Sep 2022 10:43:48 +
Source: siconos
Binary: libsiconos-control-dev libsiconos-control7 libsiconos-control7-dbgsym 
libsiconos-io-dev libsiconos-io7 libsiconos-io7-dbgsym libsiconos-kernel-dev 
libsiconos-kernel7 libsiconos-kernel7-dbgsym libsiconos-mechanics-dev 
libsiconos-mechanics7 libsiconos-mechanics7-dbgsym libsiconos-numerics-dev 
libsiconos-numerics7 libsiconos-numerics7-dbgsym python3-siconos 
python3-siconos-dbgsym siconos siconos-mechanics-tools
Architecture: source amd64 all
Version: 4.4.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Stephen Sinclair 
Description:
 libsiconos-control-dev - modeling and simulation of nonsmooth dynamical 
systems (control d
 libsiconos-control7 - modeling and simulation of nonsmooth dynamical systems 
(control l
 libsiconos-io-dev - modeling and simulation of nonsmooth dynamical systems (io 
dev)
 libsiconos-io7 - modeling and simulation of nonsmooth dynamical systems (io 
lib)
 libsiconos-kernel-dev - modeling and simulation of nonsmooth dynamical systems 
(kernel de
 libsiconos-kernel7 - modeling and simulation of nonsmooth dynamical systems 
(kernel li
 libsiconos-mechanics-dev - modeling and simulation of nonsmooth dynamical 
systems (mechanics
 libsiconos-mechanics7 - modeling and simulation of nonsmooth dynamical systems 
(mechanics
 libsiconos-numerics-dev - modeling and simulation of nonsmooth dynamical 
systems (numerics
 libsiconos-numerics7 - modeling and simulation of nonsmooth dynamical systems 
(numerics
 python3-siconos - modeling and simulation of nonsmooth dynamical systems 
(python3)
 siconos- modeling and simulation of nonsmooth dynamical systems (simulatio
 siconos-mechanics-tools - modeling and simulation of nonsmooth dynamical 
systems (mechanics
Closes: 1016600
Changes:
 siconos (4.4.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream release.
   * Update patches.
   * Disable integration with fclib.
   * Fix CMake target patch to not be sensitive to version number.
   * Include a SONAME increment commit that was added after release.
   * Update symbols for libsiconos_externals.so and libsiconos_numerics.so.
   * Add usage of dh_numpy3.
   * Update policy version 4.6.1.
   * Update python3-vtk7 dependency to python3-vtk9.  (Closes: #1016600)
   * Add upstream fix for siconos_vview necessary for VTK 9.
   * Update kernel-dev test according to changes in new release.
   * Set DESTDIR during cmake configure.
   * Include upstream patch to fix crash in QPConvex test, fixes autopkgtest
 failure.
   * Fix library 

Bug#1020436: giac FTBFS with PARI 2.15.0

[Adrian Bunk]

Source: giac
Version: 1.9.0.19+dfsg2-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=giac=1.9.0.19%2Bdfsg2-1%2Bb1

...
pari.cc: At global scope:
pari.cc:752:17: error: typedef ‘giac::PFGEN’ is initialized (use ‘decltype’ 
instead)
  752 |   typedef GEN (*PFGEN)(ANYARG);
  | ^
pari.cc:752:24: error: ‘ANYARG’ was not declared in this scope
  752 |   typedef GEN (*PFGEN)(ANYARG);
  |^~
pari.cc: In function ‘giac::gen giac::in_pari(const gen&, const context*)’:
pari.cc:829:26: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
  829 |   argvec[k]= (GEN) v[j].val;
  |  ^~
pari.cc:847:33: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
  847 |   argvec[k]=(long int*)(pos -1);
  | ^~~
pari.cc:855:31: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
  855 | argvec[k]=(long int*) v[j].val;
  |   ^~~~
pari.cc:883:23: error: ‘PFGEN’ was not declared in this scope; did you mean 
‘GEN’?
  883 |   res = ((PFGEN)call)(_ARGS_);
  |   ^
  |   GEN
pari.cc:883:29: error: expected ‘)’ before ‘call’
  883 |   res = ((PFGEN)call)(_ARGS_);
  | ~   ^~~~
  | )
pari.cc:887:27: error: expected primary-expression before ‘int’
  887 |   m = (long)((int (*)(ANYARG))call)(_ARGS_);
  |   ^~~
pari.cc:887:27: error: expected ‘)’ before ‘int’
  887 |   m = (long)((int (*)(ANYARG))call)(_ARGS_);
  |  ~^~~
  |   )
pari.cc:887:56: error: expected ‘)’ before ‘;’ token
  887 |   m = (long)((int (*)(ANYARG))call)(_ARGS_);
  | ~  ^
  |)
pari.cc:891:21: error: expected primary-expression before ‘long’
  891 |   m = ((long (*)(ANYARG))call)(_ARGS_);
  | ^~~~
pari.cc:891:21: error: expected ‘)’ before ‘long’
  891 |   m = ((long (*)(ANYARG))call)(_ARGS_);
  |~^~~~
  | )
pari.cc:891:51: error: expected ‘)’ before ‘;’ token
  891 |   m = ((long (*)(ANYARG))call)(_ARGS_);
  |   ~   ^
  |   )
pari.cc:895:17: error: expected primary-expression before ‘void’
  895 |   ((void (*)(ANYARG))call)(_ARGS_);
  | ^~~~
pari.cc:895:17: error: expected ‘)’ before ‘void’
  895 |   ((void (*)(ANYARG))call)(_ARGS_);
  |~^~~~
  | )
pari.cc:895:47: error: expected ‘)’ before ‘;’ token
  895 |   ((void (*)(ANYARG))call)(_ARGS_);
  |   ~   ^
  |   )
make[3]: *** [Makefile:993: pari.lo] Error 1

Bug#1020435: ruby-prof: FTBFS on ppc64el

[Sebastian Ramacher]

Source: ruby-prof
Version: 1.4.3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=ruby-prof=ppc64el=1.4.3-1%2Bb1=1663720013=0

  1) Failure:
PrinterGraphTest#test_graph_results_sorting 
[/<>/test/printer_graph_test.rb:37]:
Array [0.171, 0.171, 0.167, 0.167, 0.166, 0.164, 0.004, 0.004, 0.002, 0.0, 0.0, 
0.0, 0.0, 0.17, 0.17, 0.0, 0.0, 0.169, 0.169, 0.0, 0.0] is not sorted.
--- expected
+++ actual
@@ -1 +1 @@
-[0.171, 0.171, 0.167, 0.167, 0.166, 0.164, 0.004, 0.004, 0.002, 0.0, 0.0, 0.0, 
0.0, 0.17, 0.17, 0.0, 0.0, 0.169, 0.169, 0.0, 0.0]
+[0.171, 0.171, 0.17, 0.17, 0.169, 0.169, 0.167, 0.167, 0.166, 0.164, 0.004, 
0.004, 0.002, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]


51 runs, 687 assertions, 1 failures, 0 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w -I"test" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb
 "test/abstract_printer_test.rb" "test/alias_test.rb" "test/basic_test.rb" 
"test/call_tree_visitor_test.rb" "test/call_trees_test.rb" 
"test/duplicate_names_test.rb" "test/enumerable_test.rb" 
"test/exceptions_test.rb" "test/exclude_methods_test.rb" 
"test/exclude_threads_test.rb" "test/fiber_test.rb" "test/gc_test.rb" 
"test/line_number_test.rb" "test/marshal_test.rb" "test/multi_printer_test.rb" 
"test/no_method_class_test.rb" "test/printer_call_stack_test.rb" 
"test/printer_call_tree_test.rb" "test/printer_flat_test.rb" 
"test/printer_graph_html_test.rb" "test/printer_graph_test.rb" 
"test/printing_recursive_graph_test.rb" "test/profile_test.rb" 
"test/rack_test.rb" "test/singleton_test.rb" -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.

Cheers
-- 
Sebastian Ramacher

Bug#1020434: ruby-liquid-c: FTBFS on ppc64el

[Sebastian Ramacher]

Source: ruby-liquid-c
Version: 4.1.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=ruby-liquid-c=ppc64el=4.1.0-1=1663761020=0

┌──┐
│ Run tests for ruby3.0 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=. 
GEM_PATH=/<>/debian/ruby-liquid-c/usr/lib/powerpc64le-linux-gnu/rubygems-integration/3.0.0:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/powerpc64le-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/powerpc64le-linux-gnu/rubygems-integration/3.0.0
 ruby3.0 debian/ruby-tests.rb
ruby3.0 -w -Itest 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb
 test/unit/block_test.rb test/unit/context_test.rb test/unit/expression_test.rb 
test/unit/gc_stress_test.rb test/unit/raw_test.rb 
test/unit/resource_limits_test.rb test/unit/tokenizer_test.rb 
test/unit/variable_test.rb -v
/<>/debian/ruby-liquid-c/usr/lib/powerpc64le-linux-gnu/rubygems-integration/3.0.0/gems/liquid-c-4.0.0/lib/liquid/c.rb:87:
 warning: method redefined; discarding old parse_expression
/usr/share/rubygems-integration/all/gems/liquid-5.4.0/lib/liquid/parse_context.rb:30:
 warning: previous definition of parse_expression was here
:231:in `verify_compaction_references': Compaction isn't available 
on this platform (NotImplementedError)
from /<>/test/test_helper.rb:11:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/unit/block_test.rb:3:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<>/debian/ruby-liquid-c 
returned exit code 1
make: *** [debian/rules:7: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher

Bug#1004634: openscenegraph: FTBFS with ffmpeg 5.0

[Alberto Luaces]

Hi PaulLi,

this is highly appreciated.  Thanks a lot for your effort!

I have stored the patch in the repo for reference:

https://salsa.debian.org/openscenegraph-team/openscenegraph-3.2/-/commit/d5babb29f1233a9b111be88fd1037aebb5211c54

Regards,

Alberto

On 20/9/22 19:56, Ying-Chun Liu (PaulLiu) wrote:

Hi all,

I've patched the audio part. But not completed. The video part needs 
more changes. But I don't have enough time now.


Just attach the partial patch I made so that when someone has time or I 
have time then we can continue it.


Yours,
Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: your mail

[Debian Bug Tracking System]

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

> severity 1020423 normal
Bug #1020423 [src:llvm-toolchain-15] [15 Regression] libc++abi.so.1.0 not 
linked against libgcc_s
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1011716: libbluray: continue to FTBFS and VLC crash in stable

[Christian Barcenas]

On Wed, Sep 21, 2022 at 10:21 AM Sebastian Ramacher
 wrote:
> Yes, that's all correct. But as you can see from the version graph at
> the top of the bug report at https://bugs.debian.org/1011716, the
> version in stable is not marked as fixed. There is no need to reopen
> this bug report because it is still open in stable.

Each day is an opportunity to learn something new. :-)

Looking forward to seeing the fix in the stable. Cheers.

Bug#1017982: Still working on this

[Martina Ferrari]

I am sending this message in hopes that it delays the testing 
autoremoval for a few days, as I have not been able to fix this bug in 
time, and because of it Prometheus is about to be removed from testing 
(a few days before than consul for some reason!).


FYI: I am hoping to upload a new version of consul that fixes all the 
outstanding CVEs, or failing that, to remove consul support from prometheus.


--
Martina Ferrari (Tina)

Bug#1011716: libbluray: continue to FTBFS and VLC crash in stable

[Sebastian Ramacher]

Hi

On 2022-09-21 10:13:42 -0500, Christian Barcenas wrote:
> Hi.
> 
> I am not an expert on Debian policy, so the following may be incorrect,
> but this was my reasoning for re-opening the bug:
> 
> On Wed, Sep 21, 2022 at 2:21 AM Sebastian Ramacher  
> wrote:
> > Please don't reopen it. We have version tracking to track this kind of
> > thinks. For the bullseye version, the bug was still open. Reclosing.
> 
> As far as I can see, this issue is fixed in bookworm because 1:1.3.2-1
> has an upstream fix, there is no fix at all to this issue in
> stable 1:1.2.1-4+deb11u1.
> 
> Aren't FTBFS, and other critical software bugs that prevent runtime
> use of the library entirely, considered a serious Debian policy violation
> that should be fixed with an upload to stable-proposed-updates?

Yes, that's all correct. But as you can see from the version graph at
the top of the bug report at https://bugs.debian.org/1011716, the
version in stable is not marked as fixed. There is no need to reopen
this bug report because it is still open in stable.

Cheers
-- 
Sebastian Ramacher

Bug#1011716: libbluray: continue to FTBFS and VLC crash in stable

[Christian Barcenas]

Hi.

I am not an expert on Debian policy, so the following may be incorrect,
but this was my reasoning for re-opening the bug:

On Wed, Sep 21, 2022 at 2:21 AM Sebastian Ramacher  wrote:
> Please don't reopen it. We have version tracking to track this kind of
> thinks. For the bullseye version, the bug was still open. Reclosing.

As far as I can see, this issue is fixed in bookworm because 1:1.3.2-1
has an upstream fix, there is no fix at all to this issue in
stable 1:1.2.1-4+deb11u1.

Aren't FTBFS, and other critical software bugs that prevent runtime
use of the library entirely, considered a serious Debian policy violation
that should be fixed with an upload to stable-proposed-updates?

Specifically, I am suggesting a new package 1:1.2.1-4+deb11u2 for inclusion
in the next bullseye point release. This keeps the existing upstream version
and packaging used for bullseye, with just one additional patch that fixes
the FTBFS and runtime issue.

>From experimentation the FTBFS and the runtime crash occur with Java 11
(i.e. stable's default-jdk) and Java 17. But not under Java 8. So it may be
difficult to observe the FTFBS if one builds the package in a non-isolated
environment using Java 8.

Thanks,
Christian

Bug#1020327: filezilla - fails to build from source (but built successfully in the past) - Forwarded upstream

[Philip Wyett]

On Wed, 21 Sep 2022 13:36:26 +0200 Bastian Blank  wrote:
> On Wed, Sep 21, 2022 at 11:43:07AM +0100, Philip Wyett wrote:
> > Upstream believes this to be an issue with GCC.
> > See comment and reproducer code: 
> > https://trac.filezilla-project.org/ticket/12777#comment:1
> > Needs to be reallocated to GCC.
> 
> Sorry, no, this is a bug in filezilla.  The given include is guarded by
> | #ifdef __SSE2__
> 
> SSE2 is not supported by the Debian i386 port.
> 
> Bastian
> 
> -- 
> Vulcans do not approve of violence.
>   -- Spock, "Journey to Babel", stardate 3842.4
> 
> 

Below is from upstream developer.

Changes (by Tim Kosse):

 * status:  new => moreinfo

Comment:

 The compiler does support SSE2 if you enable it, e.g. with the #pragma in
 the snippet.

 Also, why does the same snippet of code work fine in older versions of
 Debian with older versions of gcc?

 This very much looks like either a wrong #ifdef in the GCC headers, or
 enabling SSE2 via the #pragma (as opposed to -msse2) doesn't actually
 enable the functionality that SSE2 brings.

 See https://gcc.gnu.org/onlinedocs/gcc/x86-Function-Attributes.html#index-
 target_0028_0022sse2_0022_0029-function-attribute_002c-x86 and
 https://gcc.gnu.org/onlinedocs/gcc/Half-Precision.html

 I also found an interesting comment about a deeper underlying issue here:
 https://patchwork.ozlabs.org/project/gcc/patch/f3b2de01-c5c9-19dd-96bc-
 1cdd81240...@suse.com/
-- 
Ticket URL: 
FileZilla 
The free FTP solution


-- 
*** Playing the game for the games own sake. ***


Associations:

* Debian Maintainer (DM)
* Fedora/EPEL Maintainer.
* Contributor member of the AlmaLinux foundation.

WWW: https://kathenas.org

Buy Me a Coffee: https://www.buymeacoffee.com/kathenasorg

Twitter: @kathenasorg

Instagram: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Processed: block 1008016 with 1020407

[Debian Bug Tracking System]

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

> block 1008016 with 1020407
Bug #1008016 [wnpp] ITP: safe-network -- network routing and service daemon for 
the Safe Network
1008016 was blocked by: 1013139 1013117 1013106 1010275 1010212 1013142 1013108 
984864 1013144 1009888 1019090 1010099 1010083 1013137 1013109 1013136 974118 
1013115 1010075 1016409 1017918 1013138 1019044
1008016 was not blocking any bugs.
Added blocking bug(s) of 1008016: 1020407
> thanks
Stopping processing here.

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

Bug#1020423: [15 Regression] libc++abi.so.1.0 not linked against libgcc_s

[Matthias Klose]

Package: src:llvm-toolchain-15
Version: 1:15.0.1-1~exp2
Severity: serious
Tags: sid bookworm

Installing libc++abi1-15 instead of libc++abi1-14 (making LLVM 15 the default) 
breaks existing binaries, like


/usr/lib/android-sdk/extras/google/auto/desktop-head-unit: symbol lookup error: 
/usr/lib/android-sdk/extras/google/auto/desktop-head-unit: undefined symbol: 
__udivmodti4


found in the google-android-installers package.  The reason is that libc++abi.so 
isn't linked anymore against libgcc_s, and just rebuilding the package using 
LLVM 15 also doesn't link the binary against libgcc_s.



$ ldd /usr/lib/llvm-14/lib/libc++abi.so.1.0

linux-vdso.so.1 (0x7fff0233d000)

libunwind.so.1 => /lib/x86_64-linux-gnu/libunwind.so.1 
(0x7f4c18f64000)

libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f4c18d5f000)

libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f4c18c76000)

libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f4c18c56000)

/lib64/ld-linux-x86-64.so.2 (0x7f4c18fb2000)


$ ldd /usr/lib/llvm-15/lib/libc++abi.so.1.0

linux-vdso.so.1 (0x7ffe8acaf000)

libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f7ecdd09000)

libunwind.so.1 => /lib/x86_64-linux-gnu/libunwind.so.1 
(0x7f7ecdcfb000)

libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f7ecdc12000)

/lib64/ld-linux-x86-64.so.2 (0x7f7ecdf51000)

Processed: Re: Bug#1020290: init-system-helpers depends on usrmerge | usr-is-merged

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1020290 {Done: Ansgar } [init-system-helpers] 
init-system-helpers depends on usrmerge | usr-is-merged
Severity set to 'normal' from 'critical'
> tags -1 + moreinfo unreproducible
Bug #1020290 {Done: Ansgar } [init-system-helpers] 
init-system-helpers depends on usrmerge | usr-is-merged
Added tag(s) moreinfo and unreproducible.
> retitle -1 apt incorrectly prefer usr-is-merged
Bug #1020290 {Done: Ansgar } [init-system-helpers] 
init-system-helpers depends on usrmerge | usr-is-merged
Changed Bug title to 'apt incorrectly prefer usr-is-merged' from 
'init-system-helpers depends on usrmerge | usr-is-merged'.

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

Bug#1020290: init-system-helpers depends on usrmerge | usr-is-merged

[Michael Biebl]

control: severity -1 normal
control: tags -1 + moreinfo unreproducible
control: retitle -1 apt incorrectly prefer usr-is-merged

Am 21.09.22 um 15:12 schrieb Craig Sanders:

reopen 1020290
severity 1020290 critical
stop

There's no need to repeat (again!) what i've already said.



Unfortunately it is not possible to address the issue you are seeing 
without further information or having a way to reproduce the issue.


Maybe you can provide a minimal reproducer (based on a minimal chroot).

Bug#1020290: marked as done (init-system-helpers depends on usrmerge | usr-is-merged)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 15:25:28 +0200
with message-id 
and subject line Re: Bug#1020290: init-system-helpers depends on usrmerge | 
usr-is-merged
has caused the Debian Bug report #1020290,
regarding init-system-helpers depends on usrmerge | usr-is-merged
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.)


-- 
1020290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: init-system-helpers
Version: 1.65.2

dist-upgrade was broken on four systems tonight due to:

Depends: usrmerge | usr-is-merged

This effectively makes these packages Essential by stealth.  Debian's usrmerge
FAQ says:

* Is it mandatory to install this package?
No.


All four systems (3 running systemd, one running sysvinit - because systemd
is incapable of booting this machine) gave the following error message and
aborted the upgrade:

Selecting previously unselected package usr-is-merged.
Preparing to unpack .../01-usr-is-merged_30+nmu1_all.deb ...



**
*
* The usr-is-merged package cannot be installed because this system does
* not have a merged /usr.
*
* Please install the usrmerge package to convert this system to merged-/usr.
*
* For more information please read https://wiki.debian.org/UsrMerge.
*

**


dpkg: error processing archive 
/tmp/user/0/apt-dpkg-install-zRN5ON/01-usr-is-merged_30+nmu1_all.deb (--unpack):
 new usr-is-merged package pre-installation script subprocess returned 
error exit status 1
.
.
.
Errors were encountered while processing:
 /tmp/user/0/apt-dpkg-install-zRN5ON/01-usr-is-merged_30+nmu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This could only be fixed by reverting back to 1.64 and purging usr-is-merged,
followed by 'apt-mark hold init-system-helpers' of course.


This is an essential package.  Why is it forcing this usr merge idiocy on me,
even on systems that don't run systemd? what actual benefit does it provide?

And WTF does forcing usrmerge have to do with init-system-helpers' purpose?
How does forcing usrmerge qualify as a helper tool for switching between "all"
init systems?


Description-en: helper tools for all init systems
 This package contains helper tools that are necessary for switching
 between the various init systems that Debian contains (e. g. sysvinit
 or systemd). An example is deb-systemd-helper, a script that enables
 systemd unit files without depending on a running systemd.
 .
 It also includes the "service", "invoke-rc.d", and "update-rc.d"
 scripts which provide an abstraction for enabling, disabling,
 starting, and stopping services for all supported Debian init systems
 as specified by the policy.
 .
 While this package is maintained by pkg-systemd-maintainers, it is
 NOT specific to systemd at all. Maintainers of other init systems are
 welcome to include their helpers in this package.


craig

ps: I'm annoyed enough that this tried to install usr-is-merged and failed.
I would have been furious if it had successfully installed usrmerge and
irreversibly fucked with my filesystems without warning and especially without
my CONSENT.
--- End Message ---
--- Begin Message ---
Hi Craig,

On Wed, 2022-09-21 at 23:12 +1000, Craig Sanders wrote:
> There's no need to repeat (again!) what i've already said.
> 
> fix the bug before closing this report.

I recommend checking at https://www.debian.org/consultants/ to find
someone who can give you professional support with your likely
misconfiguration.

As several people already said multiple times: please leave the bug
tracker alone. I understand you might not have much experience with the
Debian community, but some minimal standards should be followed.

Ansgar--- End Message ---

Bug#1020290: init-system-helpers depends on usrmerge | usr-is-merged

[Craig Sanders]

reopen 1020290
severity 1020290 critical
stop

There's no need to repeat (again!) what i've already said.

fix the bug before closing this report.

Processed: Re: Bug#1020290: init-system-helpers depends on usrmerge | usr-is-merged

[Debian Bug Tracking System]

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

> reopen 1020290
Bug #1020290 {Done: Ansgar } [init-system-helpers] 
init-system-helpers depends on usrmerge | usr-is-merged
Bug reopened
Ignoring request to alter fixed versions of bug #1020290 to the same values 
previously set
> severity 1020290 critical
Bug #1020290 [init-system-helpers] init-system-helpers depends on usrmerge | 
usr-is-merged
Ignoring request to change severity of Bug 1020290 to the same value.
> stop
Stopping processing here.

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

Bug#1014496: marked as done (sphde: FTBFS on armhf et al)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 11:54:42 +
with message-id 
and subject line Bug#1014496: fixed in sphde 1.4.0-4
has caused the Debian Bug report #1014496,
regarding sphde: FTBFS on armhf et al
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.)


-- 
1014496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sphde
Version: 1.4.0-3
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch

Hi Frédéric,

sphde 1.4.0-3 has been stuck in unstable for 230 days because it fails to
build on several architectures.  The same problem affects Ubuntu, so I've
had a look at resolving the build failure.

It appears that of all the patches you added in this version, only the first
patch is actually required to fix the build failure with current gcc (at
least per my tests in Ubuntu); and the third of these patches is the one
that introduces the test hang on armhf.  Removing this patch is sufficient
to let the package build on all archs in Ubuntu, and hopefully this is true
for Debian as well.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru 
sphde-1.4.0/debian/patches/0009-Suppress-bogus-array-bounds-warning-with-GCC-12.patch
 
sphde-1.4.0/debian/patches/0009-Suppress-bogus-array-bounds-warning-with-GCC-12.patch
--- 
sphde-1.4.0/debian/patches/0009-Suppress-bogus-array-bounds-warning-with-GCC-12.patch
   2021-11-18 08:15:46.0 -0800
+++ 
sphde-1.4.0/debian/patches/0009-Suppress-bogus-array-bounds-warning-with-GCC-12.patch
   2022-07-06 17:18:10.0 -0700
@@ -23,13 +23,13 @@
  src/sassim.cpp | 17 +
  1 file changed, 17 insertions(+)
 
-diff --git a/src/sassim.cpp b/src/sassim.cpp
-index 53bda2a..1410919 100644
 a/src/sassim.cpp
-+++ b/src/sassim.cpp
-@@ -36,6 +36,10 @@
+Index: sphde-1.4.0/src/sassim.cpp
+===
+--- sphde-1.4.0.orig/src/sassim.cpp
 sphde-1.4.0/src/sassim.cpp
+@@ -35,6 +35,10 @@
+ #include 
  #include 
- #include 
  
 +#if __GNUC__
 +#include 
@@ -38,7 +38,7 @@
  #include "sasio.h"
  #include "freenode.h"
  #include "sasanchr.h"
-@@ -688,6 +692,15 @@ destroySASSem (SASAnchor_t * anchor)
+@@ -484,6 +488,15 @@
  #endif
  }
  
@@ -54,7 +54,7 @@
  static void
  initRegion ()
  {
-@@ -769,6 +782,10 @@ initRegion ()
+@@ -565,6 +578,10 @@
initSASSem (anchor);
  }
  
diff -Nru sphde-1.4.0/debian/patches/0010-Fixes-for-build-test-failure-61.patch 
sphde-1.4.0/debian/patches/0010-Fixes-for-build-test-failure-61.patch
--- sphde-1.4.0/debian/patches/0010-Fixes-for-build-test-failure-61.patch   
2021-11-18 08:15:46.0 -0800
+++ sphde-1.4.0/debian/patches/0010-Fixes-for-build-test-failure-61.patch   
2022-07-06 16:13:17.0 -0700
@@ -27,15 +27,14 @@
  src/tests/sassim_t.c  |  3 +--
  4 files changed, 54 insertions(+), 4 deletions(-)
 
-diff --git a/src/sasshm.c b/src/sasshm.c
-index 402e7e0..4a1e01a 100644
 a/src/sasshm.c
-+++ b/src/sasshm.c
-@@ -106,6 +106,56 @@ SASAllocateShmID (key_t key_id, void *addr, long size)
-   return (shm_id);
+Index: sphde-1.4.0/src/sasshm.c
+===
+--- sphde-1.4.0.orig/src/sasshm.c
 sphde-1.4.0/src/sasshm.c
+@@ -107,6 +107,56 @@
  }
  
-+int
+ int
 +SASAllocateShmID_clear (key_t key_id, void *addr, long size)
 +{
 +  int shm_id;
@@ -85,14 +84,15 @@
 +  return (shm_id);
 +}
 +
- int
++int
  SASAllocateShmName (char *key_name, void *addr, long size)
  {
-diff --git a/src/sasshm.h b/src/sasshm.h
-index e45f28e..40599ff 100644
 a/src/sasshm.h
-+++ b/src/sasshm.h
-@@ -36,6 +36,8 @@ extern __C__ int SASAllocateShm( void* addr, long size );
+   key_t shm_key;
+Index: sphde-1.4.0/src/sasshm.h
+===
+--- sphde-1.4.0.orig/src/sasshm.h
 sphde-1.4.0/src/sasshm.h
+@@ -36,6 +36,8 @@
  
  extern __C__ int SASAllocateShmID(key_t key_id, void* addr, long size );
  
@@ -101,11 +101,11 @@
  extern __C__ int SASAllocateShmName(char *key_name, void* addr, long size );
  
  extern __C__ int SASAllocateShmNameProj( char* key_name, char proj,
-diff --git a/src/tests/sascompoundheap_t.c 

Bug#1020327: filezilla - fails to build from source (but built successfully in the past) - Forwarded upstream

[Bastian Blank]

On Wed, Sep 21, 2022 at 11:43:07AM +0100, Philip Wyett wrote:
> Upstream believes this to be an issue with GCC.
> See comment and reproducer code: 
> https://trac.filezilla-project.org/ticket/12777#comment:1
> Needs to be reallocated to GCC.

Sorry, no, this is a bug in filezilla.  The given include is guarded by
| #ifdef __SSE2__

SSE2 is not supported by the Debian i386 port.

Bastian

-- 
Vulcans do not approve of violence.
-- Spock, "Journey to Babel", stardate 3842.4

Processed: block 996464 with 1020407

[Debian Bug Tracking System]

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

> block 996464 with 1020407
Bug #996464 [wnpp] ITP: atomic-data-rust -- graph database server to share 
Atomic Data on the web
996464 was blocked by: 1013106 1013108 1019144 969609 1013098 951683 1013100 
1019349 1019044 1019090 1013099 1013107 1010212 1013104 1013109 984622 1010256 
1013103
996464 was not blocking any bugs.
Added blocking bug(s) of 996464: 1020407
> thanks
Stopping processing here.

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

Processed: block 1001084 with 1020407

[Debian Bug Tracking System]

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

> block 1001084 with 1020407
Bug #1001084 [wnpp] ITP: meli -- terminal mail client
1001084 was not blocked by any bugs.
1001084 was not blocking any bugs.
Added blocking bug(s) of 1001084: 1020407
> thanks
Stopping processing here.

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

Bug#1020327: filezilla - fails to build from source (but built successfully in the past) - Forwarded upstream

[Philip Wyett]

Upstream believes this to be an issue with GCC.

See comment and reproducer code: 
https://trac.filezilla-project.org/ticket/12777#comment:1

Needs to be reallocated to GCC.

Regards

Phil

-- 
*** Playing the game for the games own sake. ***


Associations:

* Debian Maintainer (DM)
* Fedora/EPEL Maintainer.
* Contributor member of the AlmaLinux foundation.

WWW: https://kathenas.org

Buy Me a Coffee: https://www.buymeacoffee.com/kathenasorg

Twitter: @kathenasorg

Instagram: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Bug#1020327: filezilla - fails to build from source (but built successfully in the past)

[Philip Wyett]

Reproducer at: https://trac.filezilla-project.org/ticket/12777#comment:1

Regards

Phil

-- 
*** Playing the game for the games own sake. ***


Associations:

* Debian Maintainer (DM)
* Fedora/EPEL Maintainer.
* Contributor member of the AlmaLinux foundation.

WWW: https://kathenas.org

Buy Me a Coffee: https://www.buymeacoffee.com/kathenasorg

Twitter: @kathenasorg

Instagram: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Bug#1020407: librust-tracing-futures-dev: impossible to install: depends on missing librust-tokio-executor-0.1+default-dev

[Jonas Smedegaard]

Package: librust-tracing-futures-dev
Version: 0.2.5-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

s subjet says: package is totally broken. Please fix!

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmMq7okACgkQLHwxRsGg
ASFLUBAAmbKTHFnRsNBwX9V3l5YCt4dvoQH8lu5lpYXLzVhZlRpUX/rlhhoLHChB
1zIXVhC4GTioz0vVbFe46rce4LZsaXgCXehPpzJlWxcVUSZ5yIZSYTyo/4eGcLSR
WsBm+2wRtRPxg6oBA42CrHZWj2m8myG0y2DkdzrDyrWnG+++WvDoAKyO5MPPCHju
N/kJft0WOI+/GaPg26ikl/7yFdyCLP35Fb9ovmIfaH0pg7cc20HMHJ2DYUq62C7Z
2n3TheF6nKwBmDOqu0SiR/T+QJaM4Ym8N0+axjbbaDS20KNulcbaaIMgBOXZOQrH
Q8NGQdkyjpI65dJPk7WbYEsmHtj/SB6bSQx8NSrK63KfKKsLO2b3F0qUVmVcPTy4
ik5Bwnll1RTUT+p9ByN0gu1W9sS5+SZHwLIyBarnRm50FgSwwOZvjQoDiuZWirP4
Xz/yheSkdw1z8WAT3W8u4wCCWH5/XZZJKHmQQTr8JvV3LYB7Xme6pRqo1Fcm5P8r
jnbU5S8/kB7MXRZS/Cx8s6MrAuHh+7wp/w9XEOYWx5sYBb4ejCynF0VzakXhsWXB
zG7DZQXcntf9tDmGxg/lZGl2WABMXkbqPOYk3KGXjUP1FjC6nLv340tUDqmFAzHz
fGG0Q1Z3xdSTEiEWcW9zjg2IWQD8OkfD0PYp/hdYi5Pid8hC290=
=GHp3
-END PGP SIGNATURE-

Processed: Re: filezilla - fails to build from source (but built successfully in the past) - Forwarded upstream

[Debian Bug Tracking System]

Processing control commands:

> reassign 1020327 gcc 12
Bug #1020327 [src:filezilla] filezilla: FTBFS on i386
Bug reassigned from package 'src:filezilla' to 'gcc'.
No longer marked as found in versions filezilla/3.60.2-1.
Ignoring request to alter fixed versions of bug #1020327 to the same values 
previously set
Bug #1020327 [gcc] filezilla: FTBFS on i386
There is no source info for the package 'gcc' at version '12' with architecture 
''
Unable to make a source version for version '12'
Marked as found in versions 12.

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

Bug#1020327: filezilla - fails to build from source (but built successfully in the past) - Forwarded upstream

[Philip Wyett]

Control: reassign 1020327 gcc 12

Regards

Phil

-- 
*** Playing the game for the games own sake. ***


Associations:

* Debian Maintainer (DM)
* Fedora/EPEL Maintainer.
* Contributor member of the AlmaLinux foundation.

WWW: https://kathenas.org

Buy Me a Coffee: https://www.buymeacoffee.com/kathenasorg

Twitter: @kathenasorg

Instagram: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Bug#1020406: redmine: downgrade

[wim]

Package: redmine
Version: 4.0.7-1~bpo10+1
Followup-For: Bug #1020406

Hello,

the patch described on 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019238#15
does not work for this problem (confirmation?),
moreover the patch there needs be changed of reverted to the original files

downgrading solves the issue for now,
the same downgrade as described on:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019238#10

hth,
Wim


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

Kernel: Linux 4.19.0-21-amd64 (SMP w/8 CPU cores)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to nl_BE.utf8), LANGUAGE=nl_BE:nl (charmap=UTF-8) (ignored: LC_ALL set to 
nl_BE.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages redmine depends on:
ii  dbconfig-common 2.0.11+deb10u1
ii  debconf [debconf-2.0]   1.5.71+deb10u1
ii  libjs-chart.js  2.7.3+dfsg-5
ii  libjs-jquery3.3.1~dfsg-3+deb10u1
ii  libjs-jquery-ui 1.12.1+dfsg-5
ii  libjs-raphael   2.1.0-1
ii  redmine-pgsql   4.0.7-1~bpo10+1
ii  ruby1:2.5.1
ii  ruby-actionpack-action-caching  1.2.0-2
ii  ruby-actionpack-xml-parser  2.0.1-3
ii  ruby-bundler1.17.3-3+deb10u1
ii  ruby-coderay1.1.2-2
ii  ruby-csv3.0.2-1
ii  ruby-i18n   1.5.3-1+deb10u1
ii  ruby-jquery-rails   4.3.3-1
ii  ruby-mail   2.7.1+dfsg1-1
ii  ruby-mime-types 3.2.2-1
ii  ruby-mimemagic  0.3.2+dfsg-1
ii  ruby-mini-mime  1.0.1-1
ii  ruby-net-ldap   0.16.1-1
ii  ruby-nokogiri   1.10.0+dfsg1-2
ii  ruby-rack   2.0.6-3+deb10u1
ii  ruby-rack-test  0.7.0-1
ii  ruby-rails  2:5.2.2.1+dfsg-1+deb10u3
ii  ruby-rails-dom-testing  2.0.3-3
ii  ruby-rails-observers0.1.5-1
ii  ruby-rbpdf  1.19.5+ds.1-1
ii  ruby-redcarpet  3.4.0-4+deb10u1
ii  ruby-request-store  1.3.0-1
ii  ruby-rmagick2.16.0-6
ii  ruby-roadie 3.2.2-1
ii  ruby-roadie-rails   1.3.0-1
ii  ruby-rouge  3.21.0-1~bpo10+1
ii  ruby2.1 [ruby-interpreter]  2.1.5-2+deb8u3

Versions of packages redmine recommends:
ii  passenger  5.0.30-1.1

Versions of packages redmine suggests:
pn  bzr 
ii  cvs 2:1.12.13+real-27
pn  darcs   
ii  git 1:2.20.1-2+deb10u3
pn  mercurial   
ii  ruby-fcgi   0.9.2.1-2+b3
ii  subversion  1.10.4-1+deb10u3

-- debconf information:
  redmine/instances/default/remote/port:
  redmine/instances/default/dbconfig-remove:
  redmine/instances/default/mysql/method: Unix socket
  redmine/current-instances: default
  redmine/instances/default/db/app-user: redmine_default@localhost
  redmine/instances/default/internal/skip-preseed: false
  redmine/instances/default/purge: false
  redmine/instances/default/pgsql/method: TCP/IP
* redmine/instances/default/dbconfig-install: false
  redmine/instances/default/remote/newhost:
  redmine/instances/default/db/dbname: redmine_default
  redmine/instances/default/upgrade-backup: true
  redmine/instances/default/pgsql/authmethod-admin: ident
  redmine/instances/default/default-language: en
  redmine/instances/default/install-error: abort
  redmine/instances/default/pgsql/no-empty-passwords:
  redmine/instances/default/pgsql/manualconf:
  redmine/instances/default/upgrade-error: abort
  redmine/instances/default/internal/reconfiguring: false
  redmine/instances/default/passwords-do-not-match:
  redmine/instances/default/pgsql/admin-user: postgres
  redmine/instances/default/dbconfig-upgrade: true
  redmine/instances/default/db/basepath:
  redmine/notify-migration:
  redmine/missing-redmine-package:
  redmine/instances/default/remote/host: localhost
  redmine/instances/default/missing-db-package-error: abort
  redmine/instances/default/pgsql/authmethod-user: password
  redmine/instances/default/remove-error: abort
  redmine/instances/default/mysql/admin-user:
  redmine/instances/default/dbconfig-reinstall: false
  redmine/instances/default/pgsql/changeconf: false
  redmine/instances/default/database-type:
  redmine/old-instances:
  redmine/default-language: en

Bug#1020406: redmine: Could not spawn process for application: rubygems-integration, redmine, tsort, passenger

[wim]

Package: redmine
Version: 4.0.7-1~bpo10+1
Severity: grave
Justification: renders package unusable

Hello,

after the following upgrade, redmine (rendering) stopped working:

upgraded packages:
bzip2:amd64 1.0.6-9.2~deb10u1
bzip2:amd64 1.0.6-9.2~deb10u2
libbz2-1.0:amd64 1.0.6-9.2~deb10u1
libbz2-1.0:amd64 1.0.6-9.2~deb10u2
libc-bin:amd64 2.28-10+deb10u1
libglib2.0-0:amd64 2.58.3-2+deb10u3
libglib2.0-0:amd64 2.58.3-2+deb10u4
libglib2.0-data:all 2.58.3-2+deb10u3
libglib2.0-data:all 2.58.3-2+deb10u4
libmariadb3:amd64 1:10.3.34-0+deb10u1
libmariadb3:amd64 1:10.3.36-0+deb10u1
libsqlite3-0:amd64 3.27.2-3+deb10u1
libsqlite3-0:amd64 3.27.2-3+deb10u2
man-db:amd64 2.8.5-2
mariadb-common:all 1:10.3.34-0+deb10u1
mariadb-common:all 1:10.3.36-0+deb10u1
rails:all 2:5.2.2.1+dfsg-1+deb10u4
rails:all 2:5.2.2.1+dfsg-1+deb10u5
redmine:all 4.0.7-1~bpo10+1
ruby-actioncable:all 2:5.2.2.1+dfsg-1+deb10u4
ruby-actioncable:all 2:5.2.2.1+dfsg-1+deb10u5
ruby-actionmailer:all 2:5.2.2.1+dfsg-1+deb10u4
ruby-actionmailer:all 2:5.2.2.1+dfsg-1+deb10u5
ruby-actionpack:all 2:5.2.2.1+dfsg-1+deb10u4
ruby-actionpack:all 2:5.2.2.1+dfsg-1+deb10u5
ruby-actionview:all 2:5.2.2.1+dfsg-1+deb10u4
ruby-actionview:all 2:5.2.2.1+dfsg-1+deb10u5
ruby-activejob:all 2:5.2.2.1+dfsg-1+deb10u4
ruby-activejob:all 2:5.2.2.1+dfsg-1+deb10u5
ruby-activemodel:all 2:5.2.2.1+dfsg-1+deb10u4
ruby-activemodel:all 2:5.2.2.1+dfsg-1+deb10u5
ruby-activerecord:all 2:5.2.2.1+dfsg-1+deb10u4
ruby-activerecord:all 2:5.2.2.1+dfsg-1+deb10u5
ruby-activestorage:all 2:5.2.2.1+dfsg-1+deb10u4
ruby-activestorage:all 2:5.2.2.1+dfsg-1+deb10u5
ruby-activesupport:all 2:5.2.2.1+dfsg-1+deb10u4
ruby-activesupport:all 2:5.2.2.1+dfsg-1+deb10u5
ruby-rails:all 2:5.2.2.1+dfsg-1+deb10u4
ruby-rails:all 2:5.2.2.1+dfsg-1+deb10u5
ruby-railties:all 2:5.2.2.1+dfsg-1+deb10u4
ruby-railties:all 2:5.2.2.1+dfsg-1+deb10u5
sqlite3:amd64 3.27.2-3+deb10u1
sqlite3:amd64 3.27.2-3+deb10u2
zlib1g:amd64 1:1.2.11.dfsg-1+deb10u1
zlib1g:amd64 1:1.2.11.dfsg-1+deb10u2


apache error log:

[ 2022-09-21 00:00:01.9707 38239/7f305f260980 age/Wat/WatchdogMain.cpp:1291 ]: 
Starting Passenger watchdog...
[ 2022-09-21 00:00:01.9832 38245/7fa04b947980 age/Cor/CoreMain.cpp:982 ]: 
Starting Passenger core...
[ 2022-09-21 00:00:01.9833 38245/7fa04b947980 age/Cor/CoreMain.cpp:235 ]: 
Passenger core running in multi-application mode.
[ 2022-09-21 00:00:02.0157 38245/7fa04b947980 age/Cor/CoreMain.cpp:732 ]: 
Passenger core online, PID 38245
[ 2022-09-21 00:00:02.0269 38259/7faace70c980 age/Ust/UstRouterMain.cpp:529 ]: 
Starting Passenger UstRouter...
[ 2022-09-21 00:00:02.0281 38259/7faace70c980 age/Ust/UstRouterMain.cpp:342 ]: 
Passenger UstRouter online, PID 38259
[Wed Sep 21 00:00:02.095337 2022] [mpm_event:notice] [pid 12013:tid 
140622914925696] AH00489: Apache/2.4.38 (Debian) SVN/1.10.4 
Phusion_Passenger/5.0.30 OpenSSL/1.1.1n mod_perl/2.0.10 Perl/v5.28.1 configured 
-- resuming normal operations
[Wed Sep 21 00:00:02.095371 2022] [core:notice] [pid 12013:tid 140622914925696] 
AH00094: Command line: '/usr/sbin/apache2'
App 38351 stdout: 
App 38351 stdout: 
[ 2022-09-21 00:00:33.1058 38245/7fa0481c4700 
age/Cor/App/Implementation.cpp:304 ]: Could not spawn process for application 
/usr/share/redmine: An error occurred while starting up the preloader.
  Error ID: b3b55a33
  Error details saved to: /tmp/passenger-error-qM9kqT.html
  Message from application: undefined method `yaml_column_permitted_classes=' 
for ActiveRecord::Base:Class (NoMethodError)
  
/usr/share/rubygems-integration/all/gems/activerecord-5.2.2.1/lib/active_record/dynamic_matchers.rb:22:in
 `method_missing'
  
/usr/share/rubygems-integration/all/gems/activerecord-5.2.2.1/lib/active_record/railtie.rb:124:in
 `block (3 levels) in '
  
/usr/share/rubygems-integration/all/gems/activerecord-5.2.2.1/lib/active_record/railtie.rb:123:in
 `each'
  
/usr/share/rubygems-integration/all/gems/activerecord-5.2.2.1/lib/active_record/railtie.rb:123:in
 `block (2 levels) in '
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2.1/lib/active_support/lazy_load_hooks.rb:71:in
 `instance_eval'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2.1/lib/active_support/lazy_load_hooks.rb:71:in
 `block in execute_hook'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2.1/lib/active_support/lazy_load_hooks.rb:62:in
 `with_execution_control'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2.1/lib/active_support/lazy_load_hooks.rb:67:in
 `execute_hook'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2.1/lib/active_support/lazy_load_hooks.rb:52:in
 `block in run_load_hooks'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2.1/lib/active_support/lazy_load_hooks.rb:51:in
 `each'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2.1/lib/active_support/lazy_load_hooks.rb:51:in
 `run_load_hooks'
  
/usr/share/rubygems-integration/all/gems/activerecord-5.2.2.1/lib/active_record/base.rb:328:in
 `'
  

Bug#1020404: luakit: aborts at start

[Arne Wichmann]

Package: luakit
Version: 1:2.2.1-1
Severity: grave
Justification: renders package unusable

Luakit aborts saying:

Bail out! ERROR:common/util.c:67:strip_ansi_escapes: assertion failed (err == 
NULL): Error while compiling regular expression 
?[\u001b\u009b][[()#;?]*(?:[0-9]{1,4}(?:;[0-9]{0,4})*)?[0-9A-ORZcf-nqry=><]? at 
char 3: unrecognised character following \ (g-regex-error-quark, 103)

-- System Information:
Debian Release: 11.1
  APT prefers testing
  APT policy: (90, 'testing'), (90, 'stable'), (50, 'unstable'), (40, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.16 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.iso885915, LC_CTYPE=en_GB.iso885915 (charmap=ISO-8859-15), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages luakit depends on:
ii  libc6   2.34-7
ii  libcairo2   1.16.0-5
ii  libgdk-pixbuf2.0-0  2.40.2-2
ii  libglib2.0-02.73.3-3
ii  libgtk-3-0  3.24.24-4+deb11u2
ii  libjavascriptcoregtk-4.0-18 2.36.7-1~deb11u1
ii  libluajit-5.1-2 2.1.0~beta3+dfsg-5.3
ii  libpango-1.0-0  1.50.9+ds-1
ii  libsoup2.4-12.74.2-3
ii  libsqlite3-03.34.1-3
ii  libwebkit2gtk-4.0-372.36.7-1~deb11u1
ii  lua-filesystem [lua5.1-filesystem]  1.8.0-1

luakit recommends no packages.

luakit suggests no packages.

-- no debconf information

Bug#1009242: marked as done (zfs-dkms: PPC get_user workaround breaks boot on ZFS root)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 17:09:10 +0800
with message-id 

and subject line fixed in zfs-linux/2.1.5-1
has caused the Debian Bug report #1009242,
regarding zfs-dkms: PPC get_user workaround breaks boot on ZFS root
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.)


-- 
1009242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zfs-dkms
Version: 2.1.2-1~bpo11+1
Severity: critical
Tags: patch
Justification: breaks the whole system
X-Debbugs-Cc: nwfila...@gmail.com

Dear Maintainer,

Presently (and since 16 Nov 2021), the Debian ZFS repo has been carrying Colin
Ian King's
https://salsa.debian.org/zfsonlinux-team/zfs/-/blob/master/debian/patches/4900-ppc-get-user-workaround.patch
to work around a build failure on PPC machines whose kernels post-date
7613f5a66becfd0e43a0f34de8518695888f5458 ("powerpc/64s/kuap: Use
mmu_has_feature()").  5.13 is the first release to contain that patch
(amusingly, someone noticed pretty quickly: https://lwn.net/Articles/856312/).

Unfortunately, while this does fix the compilation error, in a rather
heavy-handed way, it results in the system hanging at boot, well before reaching
the multi-user target.  The EFAULT returned to userspace simply triggers a
retry, and so we spin.  As I am on a Debian kernel after 5.13, I am unable to
upgrade my ZFS pacakges and keep a working system without rolling back to an
older kernel, which I cannot readily do, due to another bug in pre-5.15 PPC
kernel packages: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990279 .

I reached out to the original author of mmu_feature_keys, and he has agreed to
change the EXPORT_SYMBOL status of this symbol.  His one-line patch to do so,
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20220329085709.4132729-1-haoke...@gmail.com/
has yet to be picked up by
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/ , but, I
think, could be safely included in Debian's kernel patch set until it does.

Can I ask that the ZFS and linux package maintainers coordinate picking up Kevin
Hao's patch into the kernel package and dropping Colin Ian King's workaround
from the ZFS package?

I do not know if I should also raise a bug against the linux package; please
advise.

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (991, 'stable-updates'), (990, 'stable'), (500, 
'unstable-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (300, 'unstable')
Architecture: ppc64el (ppc64le)

Kernel: Linux 5.15.0-0.bpo.2-powerpc64le (SMP w/176 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages zfs-dkms depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  dkms   2.8.4-3
ii  file   1:5.39-3
ii  libc6-dev [libc-dev]   2.31-13+deb11u3
ii  libpython3-stdlib  3.9.2-3
ii  lsb-release11.1.0
ii  perl   5.32.1-4+deb11u2
ii  python3-distutils  3.9.2-1

Versions of packages zfs-dkms recommends:
ii  linux-libc-dev  5.16.12-1~bpo11+1
ii  zfs-zed 2.1.2-1~bpo11+1
ii  zfsutils-linux  2.1.2-1~bpo11+1

Versions of packages zfs-dkms suggests:
ii  debhelper  13.3.4

-- debconf information:
  zfs-dkms/stop-build-for-unknown-kernel: true
* zfs-dkms/note-incompatible-licenses:
  zfs-dkms/stop-build-for-32bit-kernel: true
--- End Message ---
--- Begin Message ---
Source: zfs-linux
Source-Version: 2.1.5-1

This has been fixed in zfs-linux/2.1.5-1, hence closing the report.

Regards,
Aron--- End Message ---

Bug#1020290: marked as done (init-system-helpers depends on usrmerge | usr-is-merged)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 09:58:37 +0200
with message-id <7100d24d3e309e7284c1436f96a64e5efb33a544.ca...@43-1.org>
and subject line Re: Bug#1020290: closed by Ansgar  (Re: 
Bug#1020290: init-system-helpers depends on usrmerge | usr-is-merged)
has caused the Debian Bug report #1020290,
regarding init-system-helpers depends on usrmerge | usr-is-merged
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.)


-- 
1020290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: init-system-helpers
Version: 1.65.2

dist-upgrade was broken on four systems tonight due to:

Depends: usrmerge | usr-is-merged

This effectively makes these packages Essential by stealth.  Debian's usrmerge
FAQ says:

* Is it mandatory to install this package?
No.


All four systems (3 running systemd, one running sysvinit - because systemd
is incapable of booting this machine) gave the following error message and
aborted the upgrade:

Selecting previously unselected package usr-is-merged.
Preparing to unpack .../01-usr-is-merged_30+nmu1_all.deb ...



**
*
* The usr-is-merged package cannot be installed because this system does
* not have a merged /usr.
*
* Please install the usrmerge package to convert this system to merged-/usr.
*
* For more information please read https://wiki.debian.org/UsrMerge.
*

**


dpkg: error processing archive 
/tmp/user/0/apt-dpkg-install-zRN5ON/01-usr-is-merged_30+nmu1_all.deb (--unpack):
 new usr-is-merged package pre-installation script subprocess returned 
error exit status 1
.
.
.
Errors were encountered while processing:
 /tmp/user/0/apt-dpkg-install-zRN5ON/01-usr-is-merged_30+nmu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This could only be fixed by reverting back to 1.64 and purging usr-is-merged,
followed by 'apt-mark hold init-system-helpers' of course.


This is an essential package.  Why is it forcing this usr merge idiocy on me,
even on systems that don't run systemd? what actual benefit does it provide?

And WTF does forcing usrmerge have to do with init-system-helpers' purpose?
How does forcing usrmerge qualify as a helper tool for switching between "all"
init systems?


Description-en: helper tools for all init systems
 This package contains helper tools that are necessary for switching
 between the various init systems that Debian contains (e. g. sysvinit
 or systemd). An example is deb-systemd-helper, a script that enables
 systemd unit files without depending on a running systemd.
 .
 It also includes the "service", "invoke-rc.d", and "update-rc.d"
 scripts which provide an abstraction for enabling, disabling,
 starting, and stopping services for all supported Debian init systems
 as specified by the policy.
 .
 While this package is maintained by pkg-systemd-maintainers, it is
 NOT specific to systemd at all. Maintainers of other init systems are
 welcome to include their helpers in this package.


craig

ps: I'm annoyed enough that this tried to install usr-is-merged and failed.
I would have been furious if it had successfully installed usrmerge and
irreversibly fucked with my filesystems without warning and especially without
my CONSENT.
--- End Message ---
--- Begin Message ---
Hi owner@,

please stop Craig from further abusing the bug tracking system.

Thanks,
Ansgar

On Wed, 2022-09-21 at 17:50 +1000, Craig Sanders wrote:
> reopen 1020290
> severity 1020290 critical
> stop
> 
> > Please stop playing BTS ping-pong.
> 
> STOP CLOSING BUG REPORTS WITHOUT FIXING THE PROBLEM.
> 
> > Either way it looks like you misconfigured you apt sources as you
> > said earlier:
> 
> NO. I DID NOT MISCONFIGURE MY SYSTEM.

I think you did. Even your caps key seems to not work correctly.--- End Message ---

Processed: Re: Bug#1020290 closed by Ansgar (Re: Bug#1020290: init-system-helpers depends on usrmerge | usr-is-merged)

[Debian Bug Tracking System]

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

> reopen 1020290
Bug #1020290 {Done: Ansgar } [init-system-helpers] 
init-system-helpers depends on usrmerge | usr-is-merged
Bug reopened
Ignoring request to alter fixed versions of bug #1020290 to the same values 
previously set
> severity 1020290 critical
Bug #1020290 [init-system-helpers] init-system-helpers depends on usrmerge | 
usr-is-merged
Ignoring request to change severity of Bug 1020290 to the same value.
> stop
Stopping processing here.

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

Bug#1020290: closed by Ansgar (Re: Bug#1020290: init-system-helpers depends on usrmerge | usr-is-merged)

[Craig Sanders]

reopen 1020290
severity 1020290 critical
stop

> Please stop playing BTS ping-pong.

STOP CLOSING BUG REPORTS WITHOUT FIXING THE PROBLEM.

> Either way it looks like you misconfigured you apt sources as you said
> earlier:

NO. I DID NOT MISCONFIGURE MY SYSTEM.

IT DOESN'T MATTER HOW MANY TIMES YOU CLAIM IT HAS BEEN MISCONFIGURED, IT IS
NOT.  READ THE BUG REPORT.  PAY ATTENTION TO WHAT HAS BEEN STATED SEVERAL
TIMES NOW.  AT THE VERY LEAST DO YOUR OWN TESTS TO CONFIRM OR DISPROVE IT,
NOT JUST DISMISS IT WITH UNSUPPORTED STATEMENTS OF OPINION.

> # apt-get -d -u install usrmerge
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Package usrmerge is not available, but is referred to by another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
>
> That is obviously not a bug in the package. So find out why usrmerge is
> not available and then install it. It will probably also be picked up
> then.

THE SAME PROBLEM OCCURRED ON FIVE DIFFERENT SYSTEMS.

THE COPY-PASTE ABOVE IS FROM A BOG STANDARD SID VM, TOTALLY UNFUCKED WITH.

And, as I noted in a previous msg, the usrmerge package IS available,
"apt-cache show" finds it without a problem, but apt wants to install
usr-is-merged.

> But usrmerge does exist, it is available, there is an installation 
candidate:
>
># apt-cache show usrmerge
>Package: usrmerge
>Version: 30+nmu1
>Installed-Size: 39
>Maintainer: Marco d'Itri 
>Architecture: all
>Provides: usr-is-merged
>Depends: perl:any, libfile-find-rule-perl

It's not my responsibility to figure out what broken interactions your broken
package has with usrmerge, usr-is-merged, and apt itself.  IT'S YOUR PACKAGE,
YOUR RESPONSIBILTY.

craig

--
craig sanders 

Bug#1020290: init-system-helpers depends on usrmerge | usr-is-merged

[Craig Sanders]

On Wed, Sep 21, 2022 at 08:32:53AM +0200, Helmut Grohne wrote:
> On Wed, Sep 21, 2022 at 10:41:18AM +1000, Craig Sanders wrote:
> > Stop closing this bug without fixing it.
>
> The change you are objecting to was planned and presented to various
> teams in Debian including the technical committee and the release team.

This bug report is ABOUT A BROKEN PACKAGE that causes apt upgrade and
apt dist-upgrade etc to fail.

IT IS NOT ABOUT THE USR MERGE DECISION.  THAT IS ANOTHER ISSUE
ENTIRELY - IT HAPPENS TO BE THE ULTIMATE CAUSE OF THE BUG BEING
CREATED BUT THE BUG IS SEPARATE AND CAN BE FIXED WITHOUT REVISITING
ANY DECISIONS.

I'M NOT EXPECTING ANYONE TO REVERSE THE DECISION.

JUST FIX THE FUCKING PACKAGE SO IT DOESN'T BREAK APT.

> The change is implementing a technical committee decision and has been
> agreed to by the technical committee and the release team. You should be
> able to find the rationale in the relevant technical committee bug
> reports. If you want to change this, please file your objection with the
> technical committee or start a GR instead of reopening this bug over and
> over again.

The technical committee decision does not mandate an incompetent
implementation that breaks apt.

No matter how fucked up and stupid the decision was, it is possible to
implement it without breaking apt.

> > It is breaking upgrades and dist-upgrades etc.
>
> As others have pointed out, this is breaking on your side, because

These "others" you mention are making shit up because they don't want to even
investigate the problem, let alone fix it.

As I have pointed out several times now, THIS IS **NOT** SOMETHING JUST
HAPPENING ON MY SIDE DUE TO SOME ODDITY WITH MY SYSTEMS' CONFIGURATIONS.  MY
SYSTEMS ARE NOT MISCONFIGURED.  THE BUG OCCURS ON STANDARD DEBIAN SID VMS.

IF YOU THINK I AM WRONG, THEN DO SOME TESTING TO CONFIRM OR DISPROVE IT
YOURSELF.

> usrmerge is somehow prevented from being installable. Please figure out
> why that happens. I suppose the most likely cause would be use of
> dpkg-fsys-usrunmess. Refer to the new faq entry at
> https://wiki.debian.org/UsrMerge on how to revert that.

I have never run anything like that, so there is nothing to revert.  I was
barely even aware of this usr merge bullshit happening because it is not
important to me.

The ONLY reason I'm aware of it now is because, during a routing dist-upgrade,
init-system-helpers 1.65.2 broke upgrades on several of my systems, breakage
which was only fixable by reverting to 1.64.  AS WAS DESCRIBED IN MY INITIAL
BUG REPORT.

craig

--
craig sanders 

Bug#1011716: marked as done (libbluray: FTBFS: [javac] /<>/src/libbluray/bdj/java-j2se/java/io/BDFileSystemImpl.java:21: error: BDFileSystemImpl is not abstract and does not override

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 09:21:01 +0200
with message-id 
and subject line Re: Bug#1011716: libbluray: continue to FTBFS and VLC crash in 
stable
has caused the Debian Bug report #1011716,
regarding libbluray: FTBFS: [javac] 
/<>/src/libbluray/bdj/java-j2se/java/io/BDFileSystemImpl.java:21: 
error: BDFileSystemImpl is not abstract and does not override abstract method 
isInvalid(File) in FileSystem
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.)


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> rm -rf doc/doxygen
> SRCDIR='.' PROJECT='libbluray' DOCDIR='doc/doxygen' VERSION='1.3.1' 
> PERL_PATH='/usr/bin/perl' HAVE_DOT='NO' GENERATE_MAN='NO' GENERATE_RTF='NO' 
> GENERATE_XML='NO' GENERATE_HTMLHELP='NO' GENERATE_CHI='NO' 
> GENERATE_HTML='YES' GENERATE_LATEX='NO' /usr/bin/doxygen ./doc/doxygen-config
> warning: Tag 'TCL_SUBST' at line 237 of file './doc/doxygen-config' has 
> become obsolete.
>  To avoid this warning please remove this line from your 
> configuration file or upgrade it using "doxygen -u"
> warning: Tag 'COLS_IN_ALPHA_INDEX' at line 1055 of file 
> './doc/doxygen-config' has become obsolete.
>  To avoid this warning please remove this line from your 
> configuration file or upgrade it using "doxygen -u"
> warning: Tag 'PERL_PATH' at line 2120 of file './doc/doxygen-config' has 
> become obsolete.
>  To avoid this warning please remove this line from your 
> configuration file or upgrade it using "doxygen -u"
> warning: Tag 'MSCGEN_PATH' at line 2142 of file './doc/doxygen-config' has 
> become obsolete.
>  To avoid this warning please remove this line from your 
> configuration file or upgrade it using "doxygen -u"
> warning: doxygen no longer ships with the FreeSans font.
> You may want to clear or change DOT_FONTNAME.
> Otherwise you run the risk that the wrong font is being used for dot 
> generated graphs.
> /<>/src/libbluray/bluray.h:810: warning: Compound BD_EVENT is 
> not documented.
> /<>/src/libbluray/bluray.h:69: warning: Compound 
> BLURAY_DISC_INFO is not documented.
> /<>/src/libbluray/bluray.h:59: warning: Compound BLURAY_TITLE is 
> not documented.
> /<>/src/libbluray/bluray.h:258: warning: Compound bd_chapter is 
> not documented.
> /<>/src/libbluray/bluray.h:235: warning: Compound bd_clip is not 
> documented.
> /<>/src/libbluray/bluray.h:266: warning: Compound bd_mark is not 
> documented.
> /<>/src/libbluray/bluray.h:294: warning: Compound 
> bd_sound_effect is not documented.
> /<>/src/libbluray/bluray.h:224: warning: Compound bd_stream_info 
> is not documented.
> /<>/src/libbluray/bluray.h:275: warning: Compound bd_title_info 
> is not documented.
> /<>/src/libbluray/bluray.h:51: warning: Member 
> BD_AACS_CORRUPTED_DISC (macro definition) of file bluray.h is not documented.
> /<>/src/libbluray/bluray.h:52: warning: Member BD_AACS_NO_CONFIG 
> (macro definition) of file bluray.h is not documented.
> /<>/src/libbluray/bluray.h:53: warning: Member BD_AACS_NO_PK 
> (macro definition) of file bluray.h is not documented.
> /<>/src/libbluray/bluray.h:54: warning: Member BD_AACS_NO_CERT 
> (macro definition) of file bluray.h is not documented.
> /<>/src/libbluray/bluray.h:55: warning: Member 
> BD_AACS_CERT_REVOKED (macro definition) of file bluray.h is not documented.
> /<>/src/libbluray/bluray.h:56: warning: Member 
> BD_AACS_MMC_FAILED (macro definition) of file bluray.h is not documented.
> /<>/src/libbluray/bluray.h:601: warning: Member 
> BLURAY_PG_TEXTST_STREAM (macro definition) of file bluray.h is not documented.
> /<>/src/libbluray/bluray.h:816: warning: Member BD_ERROR_HDMV 
> (macro definition) of file bluray.h is not documented.
> /<>/src/libbluray/bluray.h:817: warning: Member BD_ERROR_BDJ 
> (macro definition) of file bluray.h is not documented.
> /<>/src/libbluray/bluray.h:820: warning: Member BD_ERROR_AACS 
> (macro definition) of file bluray.h is not documented.
> /<>/src/libbluray/bluray.h:821: warning: Member BD_ERROR_BDPLUS 
> (macro definition) of file bluray.h is not documented.
> /<>/src/libbluray/bluray.h:824: warning: Member 
> BLURAY_TITLE_FIRST_PLAY (macro definition) of file bluray.h is not documented.
> 

Bug#1020290: init-system-helpers depends on usrmerge | usr-is-merged

[Helmut Grohne]

Hi Craig,

Speaking with a CTTE hat.

On Wed, Sep 21, 2022 at 10:41:18AM +1000, Craig Sanders wrote:
> Stop closing this bug without fixing it.

The change you are objecting to was planned and presented to various
teams in Debian including the technical committee and the release team.
The change is implementing a technical committee decision and has been
agreed to by the technical committee and the release team. You should be
able to find the rationale in the relevant technical committee bug
reports. If you want to change this, please file your objection with the
technical committee or start a GR instead of reopening this bug over and
over again.

> It is breaking upgrades and dist-upgrades etc.

As others have pointed out, this is breaking on your side, because
usrmerge is somehow prevented from being installable. Please figure out
why that happens. I suppose the most likely cause would be use of
dpkg-fsys-usrunmess. Refer to the new faq entry at
https://wiki.debian.org/UsrMerge on how to revert that.

Helmut

Processed: your mail

[Debian Bug Tracking System]

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

> tags 1016600 + pending
Bug #1016600 [src:siconos] siconos: vtk[6,7] removal
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1013163: marked as done (solvespace: autopkgtest regression on s390x: The model does not contain any surfaces to export.)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 06:11:06 +
with message-id 
and subject line Bug#1013163: fixed in solvespace 3.1+ds1-2
has caused the Debian Bug report #1013163,
regarding solvespace: autopkgtest regression on s390x: The model does not 
contain any surfaces to export.
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.)


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

Source: solvespace
Version: 3.1~rc1+ds1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of solvespace the autopkgtest of solvespace fails 
in testing when that autopkgtest is run with the binary packages of 
solvespace from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
solvespace from testing3.1~rc1+ds1-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 to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul
[1] https://qa.debian.org/excuses.php?package=solvespace

https://ci.debian.net/data/autopkgtest/testing/s390x/s/solvespace/22632206/log.gz

+ . debian/tests/common
+ logname=/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/surfaces.txt
+ get_files_with_surfaces
+ grep -E -v (constraint)|(request)|(link)|(contour_area)
+ get_all_files
+ find -name *.slvs
+ tee /tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/surfaces.txt
+ read fn
+ echo ./test/group/translate_nd/normal.slvs
./test/group/translate_nd/normal.slvs
+ dirname ./test/group/translate_nd/normal.slvs
+ mkdir -p 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_nd
+ solvespace-cli export-surfaces --output 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/%_surfaces.step 
./test/group/translate_nd/normal.slvs

Missing (absent) translation for group-name'#references'
Missing (absent) translation for group-name'sketch-in-plane'
Generate::ALL took 43 ms
Written 
'/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_nd/normal_surfaces.step'.

+ read fn
+ echo ./test/group/translate_nd/normal_v22.slvs
./test/group/translate_nd/normal_v22.slvs
+ dirname ./test/group/translate_nd/normal_v22.slvs
+ mkdir -p 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_nd
+ solvespace-cli export-surfaces --output 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/%_surfaces.step 
./test/group/translate_nd/normal_v22.slvs

Missing (absent) translation for group-name'#references'
Missing (absent) translation for group-name'sketch-in-plane'
Generate::ALL took 44 ms
Error: The model does not contain any surfaces to export.
Written 
'/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_nd/normal_v22_surfaces.step'.

+ read fn
+ echo ./test/group/translate_asy/normal.slvs
./test/group/translate_asy/normal.slvs
+ dirname ./test/group/translate_asy/normal.slvs
+ mkdir -p 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_asy
+ solvespace-cli export-surfaces --output 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/%_surfaces.step 
./test/group/translate_asy/normal.slvs

Missing (absent) translation for group-name'#references'
Missing (absent) translation for group-name'sketch-in-plane'
Written 
'/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_asy/normal_surfaces.step'.

+ read fn
+ echo ./test/group/translate_asy/normal_v22.slvs
./test/group/translate_asy/normal_v22.slvs
+ dirname ./test/group/translate_asy/normal_v22.slvs
+ mkdir -p 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_asy
+ solvespace-cli export-surfaces --output 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/%_surfaces.step 
./test/group/translate_asy/normal_v22.slvs

Missing (absent) translation for group-name'#references'
Missing (absent) translation for group-name'sketch-in-plane'
Error: The model does not contain any surfaces to export.
Written 
'/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/./test/group/translate_asy/normal_v22_surfaces.step'.

+ read fn
+ grep Error 
/tmp/autopkgtest-lxc.qokm0ro_/downtmp/autopkgtest_tmp/surfaces.txt

Error: The model does not contain any surfaces 

Bug#1020290: marked as done (init-system-helpers depends on usrmerge | usr-is-merged)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 08:01:09 +0200
with message-id <0787beea07ce3a533a2c083f264e953c2ef85226.ca...@43-1.org>
and subject line Re: Bug#1020290: init-system-helpers depends on usrmerge | 
usr-is-merged
has caused the Debian Bug report #1020290,
regarding init-system-helpers depends on usrmerge | usr-is-merged
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.)


-- 
1020290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: init-system-helpers
Version: 1.65.2

dist-upgrade was broken on four systems tonight due to:

Depends: usrmerge | usr-is-merged

This effectively makes these packages Essential by stealth.  Debian's usrmerge
FAQ says:

* Is it mandatory to install this package?
No.


All four systems (3 running systemd, one running sysvinit - because systemd
is incapable of booting this machine) gave the following error message and
aborted the upgrade:

Selecting previously unselected package usr-is-merged.
Preparing to unpack .../01-usr-is-merged_30+nmu1_all.deb ...



**
*
* The usr-is-merged package cannot be installed because this system does
* not have a merged /usr.
*
* Please install the usrmerge package to convert this system to merged-/usr.
*
* For more information please read https://wiki.debian.org/UsrMerge.
*

**


dpkg: error processing archive 
/tmp/user/0/apt-dpkg-install-zRN5ON/01-usr-is-merged_30+nmu1_all.deb (--unpack):
 new usr-is-merged package pre-installation script subprocess returned 
error exit status 1
.
.
.
Errors were encountered while processing:
 /tmp/user/0/apt-dpkg-install-zRN5ON/01-usr-is-merged_30+nmu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This could only be fixed by reverting back to 1.64 and purging usr-is-merged,
followed by 'apt-mark hold init-system-helpers' of course.


This is an essential package.  Why is it forcing this usr merge idiocy on me,
even on systems that don't run systemd? what actual benefit does it provide?

And WTF does forcing usrmerge have to do with init-system-helpers' purpose?
How does forcing usrmerge qualify as a helper tool for switching between "all"
init systems?


Description-en: helper tools for all init systems
 This package contains helper tools that are necessary for switching
 between the various init systems that Debian contains (e. g. sysvinit
 or systemd). An example is deb-systemd-helper, a script that enables
 systemd unit files without depending on a running systemd.
 .
 It also includes the "service", "invoke-rc.d", and "update-rc.d"
 scripts which provide an abstraction for enabling, disabling,
 starting, and stopping services for all supported Debian init systems
 as specified by the policy.
 .
 While this package is maintained by pkg-systemd-maintainers, it is
 NOT specific to systemd at all. Maintainers of other init systems are
 welcome to include their helpers in this package.


craig

ps: I'm annoyed enough that this tried to install usr-is-merged and failed.
I would have been furious if it had successfully installed usrmerge and
irreversibly fucked with my filesystems without warning and especially without
my CONSENT.
--- End Message ---
--- Begin Message ---
On Wed, 2022-09-21 at 10:41 +1000, Craig Sanders wrote:
> reopen 1020290
> severity 1020290 critical
> stop

Please stop playing BTS ping-pong.

Either way it looks like you misconfigured you apt sources as you said
earlier:

# apt-get -d -u install usrmerge
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package usrmerge is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

That is obviously not a bug in the package. So find out why usrmerge is
not available and then install it. It will probably also be picked up
then.

Ansgar--- End Message ---

Bug#1020020: marked as done (libopenshot: FTBFS: ZmqLogger.h:43:10: fatal error: zmq.hpp: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2022 05:58:16 +
with message-id 
and subject line Bug#1020020: fixed in libopenshot 0.2.7+dfsg1-4
has caused the Debian Bug report #1020020,
regarding libopenshot: FTBFS: ZmqLogger.h:43:10: fatal error: zmq.hpp: 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.)


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

Hi,

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


Relevant part (hopefully):
> cd /<>/debian/build/src && /usr/bin/c++ -DHAVE_ISFINITE=1 
> -DLINUX -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 
> -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DUSE_HW_ACCEL=1 
> -DUSE_IMAGEMAGICK=1 -Dopenshot_EXPORTS 
> -I/<>/debian/build/src/openshot_autogen/include 
> -I/<>/src -I/<>/debian/build/src 
> -I/usr/include/ImageMagick-6 -I/usr/include/x86_64-linux-gnu/ImageMagick-6 
> -isystem /usr/include/libopenshot-audio -isystem /usr/include/jsoncpp 
> -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fPIC -fopenmp 
> -std=c++14 -MD -MT src/CMakeFiles/openshot.dir/CacheDisk.cpp.o -MF 
> CMakeFiles/openshot.dir/CacheDisk.cpp.o.d -o 
> CMakeFiles/openshot.dir/CacheDisk.cpp.o -c /<>/src/CacheDisk.cpp
> In file included from /<>/src/Frame.h:50,
>  from /<>/src/CacheBase.h:36,
>  from /<>/src/CacheMemory.h:37,
>  from /<>/src/CacheMemory.cpp:31:
> /<>/src/ZmqLogger.h:43:10: fatal error: zmq.hpp: No such file or 
> directory
>43 | #include 
>   |  ^
> compilation terminated.
> make[3]: *** [src/CMakeFiles/openshot.dir/build.make:163: 
> src/CMakeFiles/openshot.dir/CacheMemory.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/libopenshot_0.2.7+dfsg1-3_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: libopenshot
Source-Version: 0.2.7+dfsg1-4
Done: Anton Gladky 

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated libopenshot 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, 21 Sep 2022 06:54:10 +0200
Source: libopenshot
Architecture: source
Version: 0.2.7+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Anton Gladky 
Closes: 1020020
Changes:
 libopenshot (0.2.7+dfsg1-4) unstable; urgency=medium
 .
   [ Stephan Lachnit ]
   * [82bb3f0] zmq.hpp now in cppzmq-dev. Update dependency. (Closes: #1020020)
 .
   [ Anton Gladky ]
   * [425ba77] Update watch file format version to 4.
Checksums-Sha1:
 4a05e00bd52396a498a9d34009ed06757d89fd79 2591 libopenshot_0.2.7+dfsg1-4.dsc