Bug#1003702: marked as done (node-postcss: uses internet during build)

[Debian Bug Tracking System]

Your message dated Fri, 14 Jan 2022 06:03:37 +
with message-id 
and subject line Bug#1003702: fixed in node-postcss 8.4.5+~cs7.1.51-2
has caused the Debian Bug report #1003702,
regarding node-postcss: uses internet 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.)


-- 
1003702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-postcss
Version: 8.4.5+~cs7.1.51-1
Severity: serious

Hello, looks like the software is trying to reach github.com and habr.com 
during node test/integration.js

This can be seen in Ubuntu build logs
https://launchpad.net/ubuntu/+source/node-postcss/8.4.5+~cs7.1.51-1/+build/23052474


ln -s ../. node_modules/postcss
/bin/sh -ex debian/tests/pkg-js/test
+ node test/integration.js
- github.com
- github.com
- habr.com
- github.com
- habr.com
- bootstrap.css
Error: getaddrinfo ENOTFOUND github.com
Error: getaddrinfo ENOTFOUND habr.com
Error: getaddrinfo ENOTFOUND github.com
Error: getaddrinfo ENOTFOUND habr.com
Error: getaddrinfo ENOTFOUND github.com
Error: getaddrinfo ENOTFOUND stackpath.bootstrapcdn.com
Error: getaddrinfo ENOTFOUND habr.com

https://github.com/
 Request error  Error: getaddrinfo ENOTFOUND github.com
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
make: *** [debian/rules:5: binary] Error 25


This is forbidden by policy.

Thanks for having a look

Gianfranco
--- End Message ---
--- Begin Message ---
Source: node-postcss
Source-Version: 8.4.5+~cs7.1.51-2
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-postcss package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 14 Jan 2022 06:37:28 +0100
Source: node-postcss
Architecture: source
Version: 8.4.5+~cs7.1.51-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1003702
Changes:
 node-postcss (8.4.5+~cs7.1.51-2) unstable; urgency=medium
 .
   * Team upload
   * Don't launch upstream test, requires Internet (Closes: #1003702)
Checksums-Sha1: 
 397f4b1c7cd24b4835ca34dffa2549ec178ce86b 3516 
node-postcss_8.4.5+~cs7.1.51-2.dsc
 a1686c532e22de3bba0115644a31f0ca79247efd 18168 
node-postcss_8.4.5+~cs7.1.51-2.debian.tar.xz
Checksums-Sha256: 
 3da334a3a1d2e717c6c51b50f904c5f82612565f6d59715a6623fd4ad1dcfa8d 3516 
node-postcss_8.4.5+~cs7.1.51-2.dsc
 2066f3f1a9ea9dd07ff18e586c79e644aca4f84d2d6fbb8e1cbe0a6fe369af27 18168 
node-postcss_8.4.5+~cs7.1.51-2.debian.tar.xz
Files: 
 24f0acce63899072b8a9bbe006d885cd 3516 javascript optional 
node-postcss_8.4.5+~cs7.1.51-2.dsc
 d155ab4ec5ed9975d392acaae5392568 18168 javascript optional 
node-postcss_8.4.5+~cs7.1.51-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmHhDP4ACgkQ9tdMp8mZ
7um7eA/+M87gBmjTtgjKbe6nvxbDds2pZARwU1DkdxEiC8a4YHiwTtxleR8Pqel4
TWufCV5rMEiVZ0rG/oeuLIEkT1HKQswJwpH9Rj3BUxeQb0SkZGTO2pt2XHV+7bKk
FpGoOzBbl/L4PbcUYr6rfRy+m9TcNJ00+ol8811jItFh4ANogGcbWXgMY5Zeo70n
+Os5OZg07ScUVdcXSxIp6PxYLJ4rGvS0qkSCvENECYARmfWNIWk+/jGAyog/mcPg
auRDwKHec5F37m9cOIvJ8+tPAd0BvbQ06qBWFYcGGkq5X3x8zIcEOVSJ+3bh+asg
7qHFehu4dzgnwv3wcikNQmKFJ4ASpgbbpJLLmDkzI/k0drG6u5TZigLWTK+SK2kK
9jnE651O2kU4M/vVCJ9HF9JAAz9olddTLKgRjiPnOcBWFd+E6u+sfyDwjY5sJBSg
BeVaXU0awm32lJtfrUpljYJMCSeXqCczdBz//i+HzEH33vQfU/2UwuqIBcVErLCq
slpf7UCha9mVUuu6cJemXkB0+BWMQfO6V4WlWpkwtwQHzCvFFlfY6iJEFW2RNEEv
o0wY7uIfFE7PQxrEhU2iZUh3JeDMlLQZLU2szLaQYw0ocsB4GIChQ21AevPNiVCZ
W7XE9GYgazDAabORbobzmE94Ff7xsPmPi0y/oEekPY8uL08XQ0o=
=VS3I
-END PGP SIGNATURE End Message ---

Processed: Bug#1003702 marked as pending in node-postcss

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1003702 [src:node-postcss] node-postcss: uses internet during build
Added tag(s) pending.

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

Bug#1003702: marked as pending in node-postcss

[Yadd]

Control: tag -1 pending

Hello,

Bug #1003702 in node-postcss 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/js-team/node-postcss/-/commit/0cfc0673a99ba303e4a17415e0965d6d34d95405


Don't launch upstream test, requires Internet

Closes: #1003702


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1003702

Bug#1002166: sdrangelove: FTBFS: gnuradiothread.cpp:139:23: error: no matching function for call to ‘gr::top_block::connect(osmosdr::source::sptr&, int, gr_adaptor_sptr&, int)’

[tony mancill]

On Tue, Jan 11, 2022 at 12:55:16PM +0100, Christoph Berg wrote:
> Re: Lucas Nussbaum
> > Source: sdrangelove
> > Version: 0.0.1.20150707-5
> > 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.
> 
> sdrangelove hasn't really been touched upstream since 2015 (except 3
> more or less boring git commits), so I propose we remove it.

Sounds like a reasonable goal for bookworm.

> (... and I should finally get around to upload sdrangel.)

https://github.com/f4exb/sdrangel looks to be quite active.

Thank you for your packaging work,
tony

Bug#965829: sofia-sip: Removal of obsolete debhelper compat 5 and 6 in bookworm

[Jonas Smedegaard]

I have filed bug#1003706 to salvage sofia-sip.

@Evangelos: If that process is not canceled, I would be more than happy 
to have you as co-maintainer.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

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

signature.asc
Description: signature

Bug#1003687: marked as done (python-pip breaks python-virtualenv autopkgtest: invalid syntax)

[Debian Bug Tracking System]

Your message dated Fri, 14 Jan 2022 00:48:48 +
with message-id 
and subject line Bug#1003687: fixed in python-virtualenv 20.13.0+ds-1
has caused the Debian Bug report #1003687,
regarding python-pip breaks python-virtualenv autopkgtest: invalid syntax
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.)


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

Source: python-pip, python-virtualenv
Control: found -1 python-pip/21.3.1+dfsg-3
Control: found -1 python-virtualenv/20.12.1+ds-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
python-pip from testing21.3.1+dfsg-3
python-virtualenv  from testing20.12.1+ds-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 python-pip 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=python-pip

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

created virtual environment CPython2.7.18.final.0-64 in 446ms
  creator 
CPython2Posix(dest=/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/ve, 
clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, 
wheel=bundle, via=copy, 
app_data_dir=/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/home/.local/share/virtualenv)
added seed packages: pip==21.3.1, pkg_resources==0.0.0, 
setuptools==59.6.0, wheel==0.34.2
  activators 
BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

created virtual environment CPython2.7.18.final.0-64 in 185ms
  creator 
CPython2Posix(dest=/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/sysve, 
clear=False, no_vcs_ignore=False, global=True)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, 
wheel=bundle, via=copy, 
app_data_dir=/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/home/.local/share/virtualenv)
added seed packages: pip==21.3.1, pkg_resources==0.0.0, 
setuptools==59.6.0, wheel==0.34.2
  activators 
BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

testMPipHelp
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 163, in _run_module_as_main
mod_name, _Error)
  File "/usr/lib/python2.7/runpy.py", line 111, in _get_module_details
__import__(mod_name)  # Do not catch exceptions initializing package
  File 
"/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/ve/lib/python2.7/site-packages/pip/__init__.py", 
line 6

def main(args: Optional[List[str]] = None) -> int:
 ^
SyntaxError: invalid syntax
ASSERT:Execute bare pip
testSystemPackagesNotAvailable
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named six
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 163, in _run_module_as_main
mod_name, _Error)
  File "/usr/lib/python2.7/runpy.py", line 111, in _get_module_details
__import__(mod_name)  # Do not catch exceptions initializing package
  File 
"/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/ve/lib/python2.7/site-packages/pip/__init__.py", 
line 6

def main(args: Optional[List[str]] = None) -> int:
 ^
SyntaxError: invalid syntax
testSystemPackagesAvailable
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 163, in _run_module_as_main
mod_name, _Error)
  File "/usr/lib/python2.7/runpy.py", line 111, in _get_module_details
__import__(mod_name)  # Do not catch exceptions initializing package
  File 
"/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/sysve/lib/python2.7/site-packages/pip/__init__.py", 
line 6

def main(args: 

Processed: Bug#1003687 marked as pending in python-virtualenv

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1003687 [src:python-pip, src:python-virtualenv] python-pip breaks 
python-virtualenv autopkgtest: invalid syntax
Added tag(s) pending.

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

Bug#1003687: marked as pending in python-virtualenv

[Stefano Rivera]

Control: tag -1 pending

Hello,

Bug #1003687 in python-virtualenv 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/python-team/packages/python-virtualenv/-/commit/9eefd0c56067376f220ff615f68f9690146b9434


Mark pypy and python2.7 autopkgtests as skip-not-installable for now, as the 
binary packages are in NEW. (Closes: #1003687)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1003687

Bug#1002231: marked as done (golang-github-pkg-term: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/pkg/term github.com/pkg/term/termios returned exit code

[Debian Bug Tracking System]

Your message dated Fri, 14 Jan 2022 00:33:31 +
with message-id 
and subject line Bug#1002231: fixed in golang-github-pkg-term 1.1.0-4
has caused the Debian Bug report #1002231,
regarding golang-github-pkg-term: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/pkg/term 
github.com/pkg/term/termios returned exit code 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.)


-- 
1002231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-pkg-term
Version: 1.1.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/pkg/term github.com/pkg/term/termios
> internal/unsafeheader
> internal/goexperiment
> internal/abi
> internal/cpu
> runtime/internal/atomic
> runtime/internal/sys
> runtime/internal/math
> internal/itoa
> math/bits
> unicode/utf8
> internal/race
> sync/atomic
> internal/bytealg
> math
> unicode
> golang.org/x/sys/internal/unsafeheader
> runtime
> internal/reflectlite
> sync
> internal/testlog
> errors
> sort
> internal/oserror
> io
> strconv
> syscall
> path
> bytes
> strings
> reflect
> time
> internal/syscall/execenv
> internal/syscall/unix
> io/fs
> internal/poll
> encoding/binary
> internal/fmtsort
> os
> golang.org/x/sys/unix
> fmt
> github.com/pkg/term/termios
> github.com/pkg/term
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/pkg/term 
> github.com/pkg/term/termios
> === RUN   TestTermSetCbreak
> --- PASS: TestTermSetCbreak (0.00s)
> === RUN   TestTermSetRaw
> --- PASS: TestTermSetRaw (0.00s)
> === RUN   TestTermSetSpeed
> --- PASS: TestTermSetSpeed (0.00s)
> === RUN   TestTermSetReadTimeout
> --- PASS: TestTermSetReadTimeout (0.00s)
> === RUN   TestTermSetFlowControl
> --- PASS: TestTermSetFlowControl (0.00s)
> === RUN   TestTermRestore
> --- PASS: TestTermRestore (0.00s)
> PASS
> okgithub.com/pkg/term 0.002s
> === RUN   TestTcflush
> --- PASS: TestTcflush (0.00s)
> === RUN   TestTcgetattr
> --- PASS: TestTcgetattr (0.00s)
> === RUN   TestTcsetattr
> --- PASS: TestTcsetattr (0.00s)
> === RUN   TestTcsendbreak
> --- PASS: TestTcsendbreak (0.00s)
> === RUN   TestTcdrain
> --- PASS: TestTcdrain (0.00s)
> === RUN   TestTiocmget
> termios_test.go:65: inappropriate ioctl for device
> --- FAIL: TestTiocmget (0.00s)
> === RUN   TestTiocmset
> termios_test.go:76: inappropriate ioctl for device
> --- FAIL: TestTiocmset (0.00s)
> === RUN   TestTiocmbis
> termios_test.go:90: inappropriate ioctl for device
> --- FAIL: TestTiocmbis (0.00s)
> === RUN   TestTiocmbic
> termios_test.go:100: inappropriate ioctl for device
> --- FAIL: TestTiocmbic (0.00s)
> === RUN   TestTiocinq
> --- PASS: TestTiocinq (0.00s)
> === RUN   TestTiocoutq
> --- PASS: TestTiocoutq (0.00s)
> === RUN   TestCfgetispeed
> --- PASS: TestCfgetispeed (0.00s)
> === RUN   TestCfgetospeed
> --- PASS: TestCfgetospeed (0.00s)
> FAIL
> FAIL  github.com/pkg/term/termios 0.002s
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/pkg/term github.com/pkg/term/termios returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/golang-github-pkg-term_1.1.0-3_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: golang-github-pkg-term
Source-Version: 1.1.0-4
Done: Stephen Gelman 

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

A summary of the changes between this version and the 

Processed: tagging 1003674

[Debian Bug Tracking System]

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

> tags 1003674 + experimental
Bug #1003674 [src:php-sabre-vobject] php-sabre-vobject: (autopkgtest) needs 
update for php8.1: ValueError: Epoch doesn't fit in a PHP integer
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Bug#1003704: bugs.debian.org: error compiling kernel 5.16

[gdaniel1358]

Package: bugs.debian.org
Severity: grave
Justification: can not compile kernel 5.16
X-Debbugs-Cc: gdaniel1...@hotmail.com

Dear Maintainer,

Hi, tried to compile kernel 5.16.0 from kernel.org.
At linking point I get:

 CHK include/generated/compile.h
  LD  vmlinux.o
  MODPOST vmlinux.symvers
  MODINFO modules.builtin.modinfo
  GEN modules.builtin
  LD  .tmp_vmlinux.btf
ld: BFD (GNU Binutils for Debian) 2.35.2 internal error, aborting at 
../../bfd/merge.c:939 in _bfd_merged_section_offset

ld: Please report this bug.



thanks in advance. 

Bug#1003687: python-pip breaks python-virtualenv autopkgtest: invalid syntax

[stefanor]

Hi Paul (2022.01.13_18:00:41_+)

We have a transition in progress, although not coordinated with you guys.
See #1003573. Once that is done, all the python3 side will work again.

We need to get python2-pip through NEW to get 2.7 virtualenvs working
again. I'll probably mark those tests as skip-not-installable, for now.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1003702: node-postcss: uses internet during build

[Gianfranco Costamagna]

Source: node-postcss
Version: 8.4.5+~cs7.1.51-1
Severity: serious

Hello, looks like the software is trying to reach github.com and habr.com 
during node test/integration.js

This can be seen in Ubuntu build logs
https://launchpad.net/ubuntu/+source/node-postcss/8.4.5+~cs7.1.51-1/+build/23052474


ln -s ../. node_modules/postcss
/bin/sh -ex debian/tests/pkg-js/test
+ node test/integration.js
- github.com
- github.com
- habr.com
- github.com
- habr.com
- bootstrap.css
Error: getaddrinfo ENOTFOUND github.com
Error: getaddrinfo ENOTFOUND habr.com
Error: getaddrinfo ENOTFOUND github.com
Error: getaddrinfo ENOTFOUND habr.com
Error: getaddrinfo ENOTFOUND github.com
Error: getaddrinfo ENOTFOUND stackpath.bootstrapcdn.com
Error: getaddrinfo ENOTFOUND habr.com

https://github.com/
 Request error  Error: getaddrinfo ENOTFOUND github.com
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
make: *** [debian/rules:5: binary] Error 25


This is forbidden by policy.

Thanks for having a look

Gianfranco

Bug#1003627: marked as done (fpc: autopkgtest regression on ppc64el:)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 21:33:56 +
with message-id 
and subject line Bug#1003627: fixed in fpc 3.2.2+dfsg-6
has caused the Debian Bug report #1003627,
regarding fpc: autopkgtest regression on ppc64el:
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.)


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

Source: fpc
Version: 3.2.2+dfsg-5
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
fpcfrom testing3.2.2+dfsg-5
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=fpc

https://ci.debian.net/data/autopkgtest/testing/ppc64el/f/fpc/18260761/log.gz

Total = 7734 (55:7679)
Total number of compilations = 4753 (17:4736)
Successfully compiled = 3605
Successfully failed = 1131
Compilation failures = 14
Compilation that did not fail while they should = 3
Total number of runs = 2981 (38:2943)
Successful runs = 2943
Failed runs = 38
Number units compiled = 152
Number program that should not be run = 468
Number of skipped tests = 632
Number of skipped graph tests = 10
Number of skipped interactive tests = 31
Number of skipped known bug tests = 7
Number of skipped tests for other versions = 5
Number of skipped tests for other cpus = 397
Number of skipped tests for other targets = 182
make: Leaving directory 
'/tmp/autopkgtest-lxc.ims6woux/downtmp/build.IH3/src/fpcsrc/tests'

Let's save some of the output
Compare the new results with known results if we have them

Difference between expected failures and current failures:
--- debian/tests/ref_fail_powerpc64-linux	2021-12-30 13:48:26.0 
+
+++ fpcsrc/tests/output/powerpc64-linux/faillist	2022-01-12 
08:26:51.116689429 +

@@ -39,6 +39,7 @@
 webtbs/tw3157
 webtbs/tw36179
 webtbs/tw36863
+webtbs/tw36934a
 webtbs/tw3930
 webtbs/tw3964b
 webtbs/tw4809

Checking (and fail if so) for new failures:
Unexpected failures
autopkgtest [08:26:51]: test run-upstream-testsuite



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: fpc
Source-Version: 3.2.2+dfsg-6
Done: Abou Al Montacir 

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

Debian distribution maintenance software
pp.
Abou Al Montacir  (supplier of updated fpc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 13 Jan 2022 21:54:24 +0100
Source: fpc
Architecture: source
Version: 3.2.2+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Abou Al Montacir 
Closes: 1003627
Changes:
 fpc (3.2.2+dfsg-6) unstable; urgency=medium
 .
   * Revert "Updated timestamps for newly modified files."
   * Revert "Imported upstream patch to fix FPU related internal compiler 
error."
 (Closes: Bug#1003627)
Checksums-Sha1:
 29c8ef151a75e9d319b16e54019d9bfd3be7 3784 fpc_3.2.2+dfsg-6.dsc
 b2923c2b107bce306f47e2956de4890daaff954a 267932 fpc_3.2.2+dfsg-6.debian.tar.xz
 8baa418cc04502a2980b7af700de3de73b68a44f 17476 fpc_3.2.2+dfsg-6_amd64.buildinfo
Checksums-Sha256:
 71155f9210d00ff256b087837adacab60db8f3ee5bc8b4cd53125cc4ce4671ad 3784 
fpc_3.2.2+dfsg-6.dsc
 c0d2d5ad24ee06eef7cd52a26ba5607f2c6eb30027454448aad91e003a8a1040 267932 
fpc_3.2.2+dfsg-6.debian.tar.xz
 

Bug#998058: intel-compute-runtime: FTBFS due to 2 failing tests

[Yuri D'Elia]

Package: intel-opencl-icd
Followup-For: Bug #998058

Any news?

Bug#1003443: marked as done (libpam-ssh: Default profile "ssh-pwd" breaks common-auth configuration)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 20:37:21 +
with message-id 
and subject line Bug#1003617: fixed in libpam-ssh 2.3+ds-6
has caused the Debian Bug report #1003617,
regarding libpam-ssh: Default profile "ssh-pwd" breaks common-auth configuration
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.)


-- 
1003617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-ssh
Version: 2.3+ds-5
Severity: important
X-Debbugs-Cc: deb...@akurth.de

Dear maintainer,

after upgrading from 2.3+ds-3 to 2.3+ds-5 the default profile changed
to "ssh-pwd", which added the following line at the bottom of my
/etc/pam.d/common-auth:

  [success=0 default=ignore]pam_ssh.so use_first_pass

This leads to the following error:

  login[1089]: PAM pam_parse: expecting non-zero; [... default=ignore]

which in turn prohibits any login.

The former default profile "ssh" added the line:

  optional pam_ssh.so use_first_pass

Booting into rescue and changing the directive to "optional" fixed the
problem, as expected.

Cheers, Andreas.


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

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

Versions of packages libpam-ssh depends on:
ii  libc6   2.33-2
ii  libpam-runtime  1.4.0-11
ii  libpam0g1.4.0-11
ii  libssl1.1   1.1.1m-1

Versions of packages libpam-ssh recommends:
ii  libpam-tmpdir0.09+b2
ii  openssh-client [ssh-client]  1:8.7p1-4

libpam-ssh suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libpam-ssh
Source-Version: 2.3+ds-6
Done: Jerome Benoit 

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated libpam-ssh package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 13 Jan 2022 19:58:56 +
Source: libpam-ssh
Architecture: source
Version: 2.3+ds-6
Distribution: unstable
Urgency: medium
Maintainer: Jerome Benoit 
Changed-By: Jerome Benoit 
Closes: 1003617
Changes:
 libpam-ssh (2.3+ds-6) unstable; urgency=medium
 .
   * RC bug fix release (Closes: #1003617), correct d/pam-configs/ssh-*.
Checksums-Sha1:
 f41d9390efb42aa83703bd316b00b3e838019e6c 2651 libpam-ssh_2.3+ds-6.dsc
 3b0f1b7d2762999343c103a362f2bae4746a7191 17108 
libpam-ssh_2.3+ds-6.debian.tar.xz
 7bb39c90c488eaa8fc782b4d71bbc1cde8fa8895 6472 
libpam-ssh_2.3+ds-6_source.buildinfo
Checksums-Sha256:
 c804db7cdf4b2ce65f80b36f46ef4f3d21ac86aadb37ebf21bfdf4e7ea93a8b0 2651 
libpam-ssh_2.3+ds-6.dsc
 bf3e347f8bb43c542fcc154d41ddc0085a0c41cf8d97a18d68b1fc6ec43b5959 17108 
libpam-ssh_2.3+ds-6.debian.tar.xz
 4dc00f039ca9c209a1a3860f479791fa140e7272398b13fa57c92fb739a492fb 6472 
libpam-ssh_2.3+ds-6_source.buildinfo
Files:
 2e32618fb7722bc2757e126e8645003f 2651 admin optional libpam-ssh_2.3+ds-6.dsc
 5ae2389457495bdf83e0de683fe9b8ee 17108 admin optional 
libpam-ssh_2.3+ds-6.debian.tar.xz
 a6fa3160d5a6780540a6d12b448605d6 6472 admin optional 
libpam-ssh_2.3+ds-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAmHghjUVHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLSOsf/jKUKFt29wCCj+vf47qdvp4d5b1A
lZXTI4eV5FzUb9xyCnQtGAqv3ORzG/6Xuq9Fn+rF9KFKNpFdDVhp6vVvZPyJptB+
MtbSD4yUAiVdd5cNqZeGa6b5cgrvPx5INJ+Ko9eSKYNrHM56d1mXKmv16mZaRmH9
7oSt8Cve7rlzcn6g5t97h94MHInB9kM7axWcyDRxyJr2xNgTOvsTAtvi9lc4awef
Gd4+335hkKLAt+3OPExRBmy1oKnyZDtbebKdDk11V4ZYdyMyfDd3DcECP/Q6vV9K
tR+kTmCcPDF4chaoAuCrcdUaglJk+x3tjSvxEUpOUQhUDj4tXhbaeA2FT6cSO9st
wsp91ky8V02bR1nt5m/kFvyrMNqP1p4KKt2cdsvZDAvnFv9yFDnf12MBBavZMnXm
PFeL2lMR2B4Dp7tXd3j2op+KEK1q3Jb9fStn/t1lJu05BxAbiBBi0lhew06GxND4

Bug#1003617: marked as done (libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 20:37:21 +
with message-id 
and subject line Bug#1003617: fixed in libpam-ssh 2.3+ds-6
has caused the Debian Bug report #1003617,
regarding libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is 
broken
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.)


-- 
1003617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-runtime
Version: 1.4.0-11
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * Upgrade to the unstable version of libpam-runtime_1.14.0_11_all
   with 
   ```
   auth[success=0 default=ignore]  pam_ssh.so use_first_pass
   ```
   * Login then failed
   * I've modified "success=0" -> "success=1" to get back the login.



-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-debug'), (500, 
'oldstable-updates'), (500, 'oldstable-debug'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (500, 'oldstable'), (100, 'buster-fasttrack'), 
(100, 'buster-backports'), (100, 'bullseye-fasttrack'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libpam-runtime depends on:
ii  debconf [debconf-2.0]  1.5.79
ii  libpam-modules 1.4.0-11

libpam-runtime recommends no packages.

libpam-runtime suggests no packages.

-- debconf information:
  libpam-runtime/conflicts:
  libpam-runtime/override: false
* libpam-runtime/profiles: passwdqc, unix, ssh-pwd, tmpdir, systemd
  libpam-runtime/no_profiles_chosen:
  libpam-runtime/title:

-- 
Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net

Société Libre, Logiciel Libre http://www.april.org/adherer
Parinux, logiciel libre à Paris : http://www.parinux.org
--- End Message ---
--- Begin Message ---
Source: libpam-ssh
Source-Version: 2.3+ds-6
Done: Jerome Benoit 

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated libpam-ssh package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 13 Jan 2022 19:58:56 +
Source: libpam-ssh
Architecture: source
Version: 2.3+ds-6
Distribution: unstable
Urgency: medium
Maintainer: Jerome Benoit 
Changed-By: Jerome Benoit 
Closes: 1003617
Changes:
 libpam-ssh (2.3+ds-6) unstable; urgency=medium
 .
   * RC bug fix release (Closes: #1003617), correct d/pam-configs/ssh-*.
Checksums-Sha1:
 f41d9390efb42aa83703bd316b00b3e838019e6c 2651 libpam-ssh_2.3+ds-6.dsc
 3b0f1b7d2762999343c103a362f2bae4746a7191 17108 
libpam-ssh_2.3+ds-6.debian.tar.xz
 7bb39c90c488eaa8fc782b4d71bbc1cde8fa8895 6472 
libpam-ssh_2.3+ds-6_source.buildinfo
Checksums-Sha256:
 c804db7cdf4b2ce65f80b36f46ef4f3d21ac86aadb37ebf21bfdf4e7ea93a8b0 2651 
libpam-ssh_2.3+ds-6.dsc
 bf3e347f8bb43c542fcc154d41ddc0085a0c41cf8d97a18d68b1fc6ec43b5959 17108 
libpam-ssh_2.3+ds-6.debian.tar.xz
 4dc00f039ca9c209a1a3860f479791fa140e7272398b13fa57c92fb739a492fb 6472 
libpam-ssh_2.3+ds-6_source.buildinfo
Files:
 2e32618fb7722bc2757e126e8645003f 2651 admin optional libpam-ssh_2.3+ds-6.dsc
 5ae2389457495bdf83e0de683fe9b8ee 17108 admin optional 
libpam-ssh_2.3+ds-6.debian.tar.xz
 a6fa3160d5a6780540a6d12b448605d6 6472 admin optional 
libpam-ssh_2.3+ds-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAmHghjUVHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLSOsf/jKUKFt29wCCj+vf47qdvp4d5b1A
lZXTI4eV5FzUb9xyCnQtGAqv3ORzG/6Xuq9Fn+rF9KFKNpFdDVhp6vVvZPyJptB+
MtbSD4yUAiVdd5cNqZeGa6b5cgrvPx5INJ+Ko9eSKYNrHM56d1mXKmv16mZaRmH9
7oSt8Cve7rlzcn6g5t97h94MHInB9kM7axWcyDRxyJr2xNgTOvsTAtvi9lc4awef

Bug#1003696: prosody: CVE-2022-0217: Unauthenticated Remote Denial of Service Attack in the WebSocket interface

[Salvatore Bonaccorso]

Source: prosody
Version: 0.11.11-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for prosody.

CVE-2022-0217[0]:
| Unauthenticated Remote Denial of Service Attack in the WebSocket
| interface

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-0217
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0217
[1] https://prosody.im/security/advisory_20220113/
[2] https://www.openwall.com/lists/oss-security/2022/01/13/3

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

[Debian Bug Tracking System]

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

> affects 1003443 src:pam
Bug #1003443 [libpam-ssh] libpam-ssh: Default profile "ssh-pwd" breaks 
common-auth configuration
Added indication that 1003443 affects src:pam
> merge 1003443 1003617
Bug #1003443 [libpam-ssh] libpam-ssh: Default profile "ssh-pwd" breaks 
common-auth configuration
Bug #1003617 [libpam-ssh] libpam-runtime: When upgrading to 
libpam-runtime_1.4.0-11 pam_ssh is broken
Marked as found in versions libpam-ssh/2.3+ds-5.
Merged 1003443 1003617
> thanks
Stopping processing here.

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

Processed (with 1 error): libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

[Debian Bug Tracking System]

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

> severity 1003443 critical
Bug #1003443 [libpam-ssh] libpam-ssh: Default profile "ssh-pwd" breaks 
common-auth configuration
Severity set to 'critical' from 'important'
> merge 1003443 1003617
Bug #1003443 [libpam-ssh] libpam-ssh: Default profile "ssh-pwd" breaks 
common-auth configuration
Unable to merge bugs because:
affects of #1003617 is 'src:pam' not ''
Failed to merge 1003443: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#1003678: sqlite3 breaks crowdsec autopkgtest: invalid type \"INTEGER\" for column

[GCS]

Control: reassign -1 src:golang-github-facebook-ent
Control: found -1 0.5.4-2
Control: tags -1 +patch

Hi Paul,

On Thu, Jan 13, 2022 at 3:54 PM Paul Gevers  wrote:
> With a recent upload of sqlite3 the autopkgtest of crowdsec fails in
> testing when that autopkgtest is run with the binary packages of sqlite3
> from unstable.
[...]
> Currently this regression is blocking the migration of sqlite3 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?
 SQLite3 used to store column data types as text with the same case it
was created. So it could have been 'integer', 'INTEGER' or even
'IntEGEr'. But with 3.37.0 and onwards it's now stored as an
enumerated value [1] and always translated to uppercase column type
[2].
Then golang-github-facebook-ent only checks for lowercase [3] values.
Meaning it was wrong for previous SQLite3 versions even.
The attached patch fixes this.

Hope this helps,
Laszlo/GCS
[1] https://github.com/sqlite/sqlite/blob/version-3.37.0/src/global.c#L388
[2] https://github.com/sqlite/sqlite/blob/version-3.37.0/src/global.c#L396
[3] https://github.com/ent/ent/blob/v0.5.4/dialect/sql/schema/sqlite.go#L284
Description: SQLite3 3.37.0+ use uppercase column tupe names
 Starting with SQLite3 3.37.0 it stores column type names as a value and
 always displayed in uppercase letters.
 Previously it stored type names as text with the same case as it was given. 
 This breaks testing where the column type is defined in lowercase and
 expects it to be given back as-is.
 Fix this with using type names in uppercase.
Author: Laszlo Boszormenyi (GCS) 
Forwarded: no
Last-Update: 2022-01-13

---

--- golang-github-facebook-ent-0.5.4.orig/dialect/sql/schema/sqlite.go
+++ golang-github-facebook-ent-0.5.4/dialect/sql/schema/sqlite.go
@@ -281,7 +281,7 @@ func (d *SQLite) scanColumn(c *Column, r
 	if err != nil {
 		return err
 	}
-	switch parts[0] {
+	switch strings.ToLower(parts[0]) {
 	case "bool", "boolean":
 		c.Type = field.TypeBool
 	case "blob":

Processed: Re: Bug#1003678: sqlite3 breaks crowdsec autopkgtest: invalid type \"INTEGER\" for column

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:golang-github-facebook-ent
Bug #1003678 [src:sqlite3, src:crowdsec] sqlite3 breaks crowdsec autopkgtest: 
invalid type \"INTEGER\" for column
Bug reassigned from package 'src:sqlite3, src:crowdsec' to 
'src:golang-github-facebook-ent'.
No longer marked as found in versions sqlite3/3.37.2-1 and crowdsec/1.0.9-3.
Ignoring request to alter fixed versions of bug #1003678 to the same values 
previously set
> found -1 0.5.4-2
Bug #1003678 [src:golang-github-facebook-ent] sqlite3 breaks crowdsec 
autopkgtest: invalid type \"INTEGER\" for column
Marked as found in versions golang-github-facebook-ent/0.5.4-2.
> tags -1 +patch
Bug #1003678 [src:golang-github-facebook-ent] sqlite3 breaks crowdsec 
autopkgtest: invalid type \"INTEGER\" for column
Added tag(s) patch.

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

Bug#984400: marked as done (w1retap: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 19:02:31 +
with message-id 
and subject line Bug#984400: fixed in w1retap 1.4.6-1
has caused the Debian Bug report #984400,
regarding w1retap: ftbfs with GCC-11
to be marked as done.

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

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


-- 
984400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:w1retap
Version: 1.4.4-4
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/w1retap_1.4.4-4_unstable_gcc11.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.

[...]
/bin/bash ../../libtool  --tag=CC   --mode=link gcc  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall  -Wl,-z,relro -Wl,-z,now -Wl,--disable-new-dtags 
-Wl,--allow-multiple-definition -o libw1mongo.la -rpath 
/usr/lib/x86_64-linux-gnu/w1retap w1mongo.lo -lmongo-client -lxml2 -lrt -lm 
libtool: link: gcc -shared  -fPIC -DPIC  .libs/w1mongo.o   -lmongo-client 
-lxml2 -lrt -lm  -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z 
-Wl,now -Wl,--disable-new-dtags -Wl,--allow-multiple-definition   -Wl,-soname 
-Wl,libw1mongo.so.0 -o .libs/libw1mongo.so.0.0.0
libtool: link: (cd ".libs" && rm -f "libw1mongo.so.0" && ln -s 
"libw1mongo.so.0.0.0" "libw1mongo.so.0")
libtool: link: (cd ".libs" && rm -f "libw1mongo.so" && ln -s 
"libw1mongo.so.0.0.0" "libw1mongo.so")
libtool: link: ar cr .libs/libw1mongo.a  w1mongo.o
libtool: link: ranlib .libs/libw1mongo.a
libtool: link: ( cd ".libs" && rm -f "libw1mongo.la" && ln -s 
"../libw1mongo.la" "libw1mongo.la" )
make[5]: Leaving directory '/<>/src/mongo'
Making all in libusblinux300
make[5]: Entering directory '/<>/src/libusblinux300'
gcc -DHAVE_CONFIG_H -I. -I../..  -Wall -D_GNU_SOURCE=1 -I . -pthread 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  
-Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wno-unused-result  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -c -o w1find.o w1find.c
gcc -DHAVE_CONFIG_H -I. -I../..  -Wall -D_GNU_SOURCE=1 -I . -pthread 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  
-Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wno-unused-result  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -c -o findtype.o findtype.c
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..  -Wall -D_GNU_SOURCE=1 -I . -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -Wdate-time -D_FORTIFY_SOURCE=2 
-Werror -Wno-unused-result  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o owerr.lo 
owerr.c
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..  -Wall -D_GNU_SOURCE=1 -I . -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -Wdate-time -D_FORTIFY_SOURCE=2 
-Werror -Wno-unused-result  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o ioutil.lo 
ioutil.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wall 

Bug#1003686: marked as done (CVE-2021-4122: cryptsetup 2.x: decryption through LUKS2 reencryption crash recovery)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 18:50:05 +
with message-id 
and subject line Bug#1003686: fixed in cryptsetup 2:2.4.3-1
has caused the Debian Bug report #1003686,
regarding CVE-2021-4122: cryptsetup 2.x: decryption through LUKS2 reencryption 
crash recovery
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.)


-- 
1003686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cryptsetup
Severity: grave
Tags: security upstream
Justification: root security hole
Control: found -1 2:2.3.5-1
Control: found -1 2:2.4.2-1
X-Debbugs-Cc: Debian Security Team 

Quoting :

| CVE-2021-4122 describes a possible attack against data confidentiality
| through LUKS2 online reencryption extension crash recovery.
| 
| An attacker can modify on-disk metadata to simulate decryption in
| progress with crashed (unfinished) reencryption step and persistently
| decrypt part of the LUKS device.
| 
| This attack requires repeated physical access to the LUKS device but
| no knowledge of user passphrases.
| 
| The decryption step is performed after a valid user activates
| the device with a correct passphrase and modified metadata.
| There are no visible warnings for the user that such recovery happened
| (except using the luksDump command). The attack can also be reversed
| afterward (simulating crashed encryption from a plaintext) with
| possible modification of revealed plaintext.
| […]
| The issue was found by Milan Broz as cryptsetup maintainer.

Upstream fixes:

  2.3 branch: 
https://gitlab.com/cryptsetup/cryptsetup/-/commit/60addcffa6794c29dccf33d8db5347f24b75f2fc
  2.4 branch: 
https://gitlab.com/cryptsetup/cryptsetup/-/commit/de98f011418c62e7b825a8ce3256e8fcdc84756e

Buster and earlier are not affected since their respective
(lib)cryptsetup don't support LUKS2 online reencryption.  I'll provide a
debdiff for bullseye-security.

-- 
Guilhem.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:2.4.3-1
Done: Guilhem Moulin 

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

Debian distribution maintenance software
pp.
Guilhem Moulin  (supplier of updated cryptsetup package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 13 Jan 2022 19:07:05 +0100
Source: cryptsetup
Architecture: source
Version: 2:2.4.3-1
Distribution: unstable
Urgency: high
Maintainer: Debian Cryptsetup Team 

Changed-By: Guilhem Moulin 
Closes: 1001063 1003685 1003686
Changes:
 cryptsetup (2:2.4.3-1) unstable; urgency=high
 .
   [ Guilhem Moulin ]
   * New upstream security release 2.4.3, with fix for CVE-2021-4122:
 decryption through LUKS2 reencryption crash recovery. (Closes: #1003685,
 #1003686)
   * Remove cryptsetup-initramfs.preinst. (Closes: #1001063)
 .
   [ Christoph Anton Mitterer ]
   * d/rules: don't expand here-document.
Checksums-Sha1:
 7b0e47c9d6b2919d1fcfc531a0e9b82ab79e17ec 3008 cryptsetup_2.4.3-1.dsc
 a35acf0d69229888089f31ad9b56ad3ea96b902b 11434956 cryptsetup_2.4.3.orig.tar.gz
 f4eaf016918c644346cd9242818f57156d4d07e9 127364 
cryptsetup_2.4.3-1.debian.tar.xz
 2352fee4f22b11355ecbcfd33b8ed2aa8953 10383 
cryptsetup_2.4.3-1_amd64.buildinfo
Checksums-Sha256:
 cfaeab454ad8f8745ab9972a577363bf8e4c187e19135b24ab4719345989ce7e 3008 
cryptsetup_2.4.3-1.dsc
 95ee4ec84d59e582eba2409281d8a41a1cc3eff3b4df91fed6dbe1df65b0614f 11434956 
cryptsetup_2.4.3.orig.tar.gz
 e0ae663b539bf76b914ddee7b0b96a5d817b2e1db0655e6034955514075affc2 127364 
cryptsetup_2.4.3-1.debian.tar.xz
 37f442c3f15fd883dce8025568d0c96a6fe5b8ab925a753065b378a347afa97b 10383 
cryptsetup_2.4.3-1_amd64.buildinfo
Files:
 2d9ba9aca62e7b3ed88e713ff2326434 3008 admin optional cryptsetup_2.4.3-1.dsc
 d6f5b44b4a775980c7f57b029e878cfd 11434956 admin optional 
cryptsetup_2.4.3.orig.tar.gz
 a3bcb368c9ac84959c21a5212e461c40 127364 admin optional 
cryptsetup_2.4.3-1.debian.tar.xz
 8cf3f0e2c7e5ea789b2764b8421d125f 10383 

Bug#1003685: marked as done (cryptsetup: CVE-2021-4122)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 18:50:05 +
with message-id 
and subject line Bug#1003686: fixed in cryptsetup 2:2.4.3-1
has caused the Debian Bug report #1003686,
regarding cryptsetup: CVE-2021-4122
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.)


-- 
1003686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:2.4.2-1
Severity: critical
Tags: security upstream
Justification: root security hole


Hey.

You've probably seen it already... Milan found CVE-2021-4122, and
the package should be upgraded to 2.4.3 ASAP.

Thanks in advance,
Chris.
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:2.4.3-1
Done: Guilhem Moulin 

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

Debian distribution maintenance software
pp.
Guilhem Moulin  (supplier of updated cryptsetup package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 13 Jan 2022 19:07:05 +0100
Source: cryptsetup
Architecture: source
Version: 2:2.4.3-1
Distribution: unstable
Urgency: high
Maintainer: Debian Cryptsetup Team 

Changed-By: Guilhem Moulin 
Closes: 1001063 1003685 1003686
Changes:
 cryptsetup (2:2.4.3-1) unstable; urgency=high
 .
   [ Guilhem Moulin ]
   * New upstream security release 2.4.3, with fix for CVE-2021-4122:
 decryption through LUKS2 reencryption crash recovery. (Closes: #1003685,
 #1003686)
   * Remove cryptsetup-initramfs.preinst. (Closes: #1001063)
 .
   [ Christoph Anton Mitterer ]
   * d/rules: don't expand here-document.
Checksums-Sha1:
 7b0e47c9d6b2919d1fcfc531a0e9b82ab79e17ec 3008 cryptsetup_2.4.3-1.dsc
 a35acf0d69229888089f31ad9b56ad3ea96b902b 11434956 cryptsetup_2.4.3.orig.tar.gz
 f4eaf016918c644346cd9242818f57156d4d07e9 127364 
cryptsetup_2.4.3-1.debian.tar.xz
 2352fee4f22b11355ecbcfd33b8ed2aa8953 10383 
cryptsetup_2.4.3-1_amd64.buildinfo
Checksums-Sha256:
 cfaeab454ad8f8745ab9972a577363bf8e4c187e19135b24ab4719345989ce7e 3008 
cryptsetup_2.4.3-1.dsc
 95ee4ec84d59e582eba2409281d8a41a1cc3eff3b4df91fed6dbe1df65b0614f 11434956 
cryptsetup_2.4.3.orig.tar.gz
 e0ae663b539bf76b914ddee7b0b96a5d817b2e1db0655e6034955514075affc2 127364 
cryptsetup_2.4.3-1.debian.tar.xz
 37f442c3f15fd883dce8025568d0c96a6fe5b8ab925a753065b378a347afa97b 10383 
cryptsetup_2.4.3-1_amd64.buildinfo
Files:
 2d9ba9aca62e7b3ed88e713ff2326434 3008 admin optional cryptsetup_2.4.3-1.dsc
 d6f5b44b4a775980c7f57b029e878cfd 11434956 admin optional 
cryptsetup_2.4.3.orig.tar.gz
 a3bcb368c9ac84959c21a5212e461c40 127364 admin optional 
cryptsetup_2.4.3-1.debian.tar.xz
 8cf3f0e2c7e5ea789b2764b8421d125f 10383 admin optional 
cryptsetup_2.4.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAmHga7YACgkQ05pJnDwh
pVJUSA//RmdVk71zU1g2C5AuYhKh+MSk8kAzVKI3Vux0LNZ0yhkyUMRVtAvyFrf1
hw045l9oWfTSaeskSeyPKd5t6OWK7WOW52f1ZZtMJ7LGvFvEcm47tbBF1oPiEZUF
VHAvHouSDDiHggs3nR05Gda1dGxyoZx1gTYAOKiak9iYUr/qQmQkyvcya5KSarIl
etojCGya/8qvL26jX00Uv8v6t4+Ya0kJlcQw5i+ZRVIl17GMiE8YbGE56vOnf7uY
rEEGQ70/6NcxQocErA3xhTfkggGoAgqV+Ojb2LtLgrT5kWZVBnNnKehx/gVPQKoO
uZ3XopYUv2iLXtyjQp9oFuswTk03QOTSIebdIcAKqwHIgUqWT84bL/qodvjIUBld
31y9il+PMcIek4LyWbqhJFufrJSlOIVgnBOqGXhS4HvSVbF0L+8lTJzsQpi6hEuJ
F+03NC/NZ8W7vQGXg10sk7fmXFlXub6npgDCMM590eXIp1Ez23WZfc7MWsrV6QNq
RR4ejtdvToAALTB6MsqQFWfVnoZKPj1G9/+oKpbe9bcBLy/jXTFmnrSFegUaHenH
WFffPVJG2Pe8mzJa43rG6LvJEqqTVZMa2ilV7c1kqtZi2rbyBL5AO8X+lO9KOl86
caDyH8W+ToB5ceiNw2sS5U1c1H30guapmIv8Ngz2WtMU31h/4+0=
=O1tU
-END PGP SIGNATURE End Message ---

Bug#1003686: marked as done (CVE-2021-4122: cryptsetup 2.x: decryption through LUKS2 reencryption crash recovery)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 18:50:05 +
with message-id 
and subject line Bug#1003685: fixed in cryptsetup 2:2.4.3-1
has caused the Debian Bug report #1003685,
regarding CVE-2021-4122: cryptsetup 2.x: decryption through LUKS2 reencryption 
crash recovery
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.)


-- 
1003685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cryptsetup
Severity: grave
Tags: security upstream
Justification: root security hole
Control: found -1 2:2.3.5-1
Control: found -1 2:2.4.2-1
X-Debbugs-Cc: Debian Security Team 

Quoting :

| CVE-2021-4122 describes a possible attack against data confidentiality
| through LUKS2 online reencryption extension crash recovery.
| 
| An attacker can modify on-disk metadata to simulate decryption in
| progress with crashed (unfinished) reencryption step and persistently
| decrypt part of the LUKS device.
| 
| This attack requires repeated physical access to the LUKS device but
| no knowledge of user passphrases.
| 
| The decryption step is performed after a valid user activates
| the device with a correct passphrase and modified metadata.
| There are no visible warnings for the user that such recovery happened
| (except using the luksDump command). The attack can also be reversed
| afterward (simulating crashed encryption from a plaintext) with
| possible modification of revealed plaintext.
| […]
| The issue was found by Milan Broz as cryptsetup maintainer.

Upstream fixes:

  2.3 branch: 
https://gitlab.com/cryptsetup/cryptsetup/-/commit/60addcffa6794c29dccf33d8db5347f24b75f2fc
  2.4 branch: 
https://gitlab.com/cryptsetup/cryptsetup/-/commit/de98f011418c62e7b825a8ce3256e8fcdc84756e

Buster and earlier are not affected since their respective
(lib)cryptsetup don't support LUKS2 online reencryption.  I'll provide a
debdiff for bullseye-security.

-- 
Guilhem.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:2.4.3-1
Done: Guilhem Moulin 

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

Debian distribution maintenance software
pp.
Guilhem Moulin  (supplier of updated cryptsetup package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 13 Jan 2022 19:07:05 +0100
Source: cryptsetup
Architecture: source
Version: 2:2.4.3-1
Distribution: unstable
Urgency: high
Maintainer: Debian Cryptsetup Team 

Changed-By: Guilhem Moulin 
Closes: 1001063 1003685 1003686
Changes:
 cryptsetup (2:2.4.3-1) unstable; urgency=high
 .
   [ Guilhem Moulin ]
   * New upstream security release 2.4.3, with fix for CVE-2021-4122:
 decryption through LUKS2 reencryption crash recovery. (Closes: #1003685,
 #1003686)
   * Remove cryptsetup-initramfs.preinst. (Closes: #1001063)
 .
   [ Christoph Anton Mitterer ]
   * d/rules: don't expand here-document.
Checksums-Sha1:
 7b0e47c9d6b2919d1fcfc531a0e9b82ab79e17ec 3008 cryptsetup_2.4.3-1.dsc
 a35acf0d69229888089f31ad9b56ad3ea96b902b 11434956 cryptsetup_2.4.3.orig.tar.gz
 f4eaf016918c644346cd9242818f57156d4d07e9 127364 
cryptsetup_2.4.3-1.debian.tar.xz
 2352fee4f22b11355ecbcfd33b8ed2aa8953 10383 
cryptsetup_2.4.3-1_amd64.buildinfo
Checksums-Sha256:
 cfaeab454ad8f8745ab9972a577363bf8e4c187e19135b24ab4719345989ce7e 3008 
cryptsetup_2.4.3-1.dsc
 95ee4ec84d59e582eba2409281d8a41a1cc3eff3b4df91fed6dbe1df65b0614f 11434956 
cryptsetup_2.4.3.orig.tar.gz
 e0ae663b539bf76b914ddee7b0b96a5d817b2e1db0655e6034955514075affc2 127364 
cryptsetup_2.4.3-1.debian.tar.xz
 37f442c3f15fd883dce8025568d0c96a6fe5b8ab925a753065b378a347afa97b 10383 
cryptsetup_2.4.3-1_amd64.buildinfo
Files:
 2d9ba9aca62e7b3ed88e713ff2326434 3008 admin optional cryptsetup_2.4.3-1.dsc
 d6f5b44b4a775980c7f57b029e878cfd 11434956 admin optional 
cryptsetup_2.4.3.orig.tar.gz
 a3bcb368c9ac84959c21a5212e461c40 127364 admin optional 
cryptsetup_2.4.3-1.debian.tar.xz
 8cf3f0e2c7e5ea789b2764b8421d125f 10383 

Bug#1003685: marked as done (cryptsetup: CVE-2021-4122)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 18:50:05 +
with message-id 
and subject line Bug#1003685: fixed in cryptsetup 2:2.4.3-1
has caused the Debian Bug report #1003685,
regarding cryptsetup: CVE-2021-4122
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.)


-- 
1003685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:2.4.2-1
Severity: critical
Tags: security upstream
Justification: root security hole


Hey.

You've probably seen it already... Milan found CVE-2021-4122, and
the package should be upgraded to 2.4.3 ASAP.

Thanks in advance,
Chris.
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:2.4.3-1
Done: Guilhem Moulin 

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

Debian distribution maintenance software
pp.
Guilhem Moulin  (supplier of updated cryptsetup package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 13 Jan 2022 19:07:05 +0100
Source: cryptsetup
Architecture: source
Version: 2:2.4.3-1
Distribution: unstable
Urgency: high
Maintainer: Debian Cryptsetup Team 

Changed-By: Guilhem Moulin 
Closes: 1001063 1003685 1003686
Changes:
 cryptsetup (2:2.4.3-1) unstable; urgency=high
 .
   [ Guilhem Moulin ]
   * New upstream security release 2.4.3, with fix for CVE-2021-4122:
 decryption through LUKS2 reencryption crash recovery. (Closes: #1003685,
 #1003686)
   * Remove cryptsetup-initramfs.preinst. (Closes: #1001063)
 .
   [ Christoph Anton Mitterer ]
   * d/rules: don't expand here-document.
Checksums-Sha1:
 7b0e47c9d6b2919d1fcfc531a0e9b82ab79e17ec 3008 cryptsetup_2.4.3-1.dsc
 a35acf0d69229888089f31ad9b56ad3ea96b902b 11434956 cryptsetup_2.4.3.orig.tar.gz
 f4eaf016918c644346cd9242818f57156d4d07e9 127364 
cryptsetup_2.4.3-1.debian.tar.xz
 2352fee4f22b11355ecbcfd33b8ed2aa8953 10383 
cryptsetup_2.4.3-1_amd64.buildinfo
Checksums-Sha256:
 cfaeab454ad8f8745ab9972a577363bf8e4c187e19135b24ab4719345989ce7e 3008 
cryptsetup_2.4.3-1.dsc
 95ee4ec84d59e582eba2409281d8a41a1cc3eff3b4df91fed6dbe1df65b0614f 11434956 
cryptsetup_2.4.3.orig.tar.gz
 e0ae663b539bf76b914ddee7b0b96a5d817b2e1db0655e6034955514075affc2 127364 
cryptsetup_2.4.3-1.debian.tar.xz
 37f442c3f15fd883dce8025568d0c96a6fe5b8ab925a753065b378a347afa97b 10383 
cryptsetup_2.4.3-1_amd64.buildinfo
Files:
 2d9ba9aca62e7b3ed88e713ff2326434 3008 admin optional cryptsetup_2.4.3-1.dsc
 d6f5b44b4a775980c7f57b029e878cfd 11434956 admin optional 
cryptsetup_2.4.3.orig.tar.gz
 a3bcb368c9ac84959c21a5212e461c40 127364 admin optional 
cryptsetup_2.4.3-1.debian.tar.xz
 8cf3f0e2c7e5ea789b2764b8421d125f 10383 admin optional 
cryptsetup_2.4.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAmHga7YACgkQ05pJnDwh
pVJUSA//RmdVk71zU1g2C5AuYhKh+MSk8kAzVKI3Vux0LNZ0yhkyUMRVtAvyFrf1
hw045l9oWfTSaeskSeyPKd5t6OWK7WOW52f1ZZtMJ7LGvFvEcm47tbBF1oPiEZUF
VHAvHouSDDiHggs3nR05Gda1dGxyoZx1gTYAOKiak9iYUr/qQmQkyvcya5KSarIl
etojCGya/8qvL26jX00Uv8v6t4+Ya0kJlcQw5i+ZRVIl17GMiE8YbGE56vOnf7uY
rEEGQ70/6NcxQocErA3xhTfkggGoAgqV+Ojb2LtLgrT5kWZVBnNnKehx/gVPQKoO
uZ3XopYUv2iLXtyjQp9oFuswTk03QOTSIebdIcAKqwHIgUqWT84bL/qodvjIUBld
31y9il+PMcIek4LyWbqhJFufrJSlOIVgnBOqGXhS4HvSVbF0L+8lTJzsQpi6hEuJ
F+03NC/NZ8W7vQGXg10sk7fmXFlXub6npgDCMM590eXIp1Ez23WZfc7MWsrV6QNq
RR4ejtdvToAALTB6MsqQFWfVnoZKPj1G9/+oKpbe9bcBLy/jXTFmnrSFegUaHenH
WFffPVJG2Pe8mzJa43rG6LvJEqqTVZMa2ilV7c1kqtZi2rbyBL5AO8X+lO9KOl86
caDyH8W+ToB5ceiNw2sS5U1c1H30guapmIv8Ngz2WtMU31h/4+0=
=O1tU
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#1003685: Acknowledgement (cryptsetup: CVE-2021-4122)

[Debian Bug Tracking System]

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

> reassign 1003685 src:cryptsetup
Bug #1003685 [cryptsetup] cryptsetup: CVE-2021-4122
Bug reassigned from package 'cryptsetup' to 'src:cryptsetup'.
No longer marked as found in versions cryptsetup/2:2.4.2-1.
Ignoring request to alter fixed versions of bug #1003685 to the same values 
previously set
> forcemerge 1003686 1003685
Bug #1003686 [src:cryptsetup] CVE-2021-4122: cryptsetup 2.x: decryption through 
LUKS2 reencryption crash recovery
Bug #1003685 [src:cryptsetup] cryptsetup: CVE-2021-4122
Severity set to 'grave' from 'critical'
Marked as found in versions cryptsetup/2:2.3.5-1 and cryptsetup/2:2.4.2-1.
Merged 1003685 1003686
>
End of message, stopping processing here.

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

Processed (with 1 error): Re: Bug#1003685: Acknowledgement (cryptsetup: CVE-2021-4122)

[Debian Bug Tracking System]

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

> forcemerge 1003686 1003685
Bug #1003686 [src:cryptsetup] CVE-2021-4122: cryptsetup 2.x: decryption through 
LUKS2 reencryption crash recovery
Unable to merge bugs because:
package of #1003685 is 'cryptsetup' not 'src:cryptsetup'
Failed to forcibly merge 1003686: Did not alter merged bugs.

>
End of message, stopping processing here.

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

Processed: python-pip breaks python-virtualenv autopkgtest: invalid syntax

[Debian Bug Tracking System]

Processing control commands:

> found -1 python-pip/21.3.1+dfsg-3
Bug #1003687 [src:python-pip, src:python-virtualenv] python-pip breaks 
python-virtualenv autopkgtest: invalid syntax
Marked as found in versions python-pip/21.3.1+dfsg-3.
> found -1 python-virtualenv/20.12.1+ds-1
Bug #1003687 [src:python-pip, src:python-virtualenv] python-pip breaks 
python-virtualenv autopkgtest: invalid syntax
Marked as found in versions python-virtualenv/20.12.1+ds-1.

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

Bug#1003687: python-pip breaks python-virtualenv autopkgtest: invalid syntax

[Paul Gevers]

Source: python-pip, python-virtualenv
Control: found -1 python-pip/21.3.1+dfsg-3
Control: found -1 python-virtualenv/20.12.1+ds-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
python-pip from testing21.3.1+dfsg-3
python-virtualenv  from testing20.12.1+ds-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 python-pip 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=python-pip

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

created virtual environment CPython2.7.18.final.0-64 in 446ms
  creator 
CPython2Posix(dest=/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/ve, 
clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, 
wheel=bundle, via=copy, 
app_data_dir=/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/home/.local/share/virtualenv)
added seed packages: pip==21.3.1, pkg_resources==0.0.0, 
setuptools==59.6.0, wheel==0.34.2
  activators 
BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

created virtual environment CPython2.7.18.final.0-64 in 185ms
  creator 
CPython2Posix(dest=/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/sysve, 
clear=False, no_vcs_ignore=False, global=True)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, 
wheel=bundle, via=copy, 
app_data_dir=/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/home/.local/share/virtualenv)
added seed packages: pip==21.3.1, pkg_resources==0.0.0, 
setuptools==59.6.0, wheel==0.34.2
  activators 
BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

testMPipHelp
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 163, in _run_module_as_main
mod_name, _Error)
  File "/usr/lib/python2.7/runpy.py", line 111, in _get_module_details
__import__(mod_name)  # Do not catch exceptions initializing package
  File 
"/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/ve/lib/python2.7/site-packages/pip/__init__.py", 
line 6

def main(args: Optional[List[str]] = None) -> int:
 ^
SyntaxError: invalid syntax
ASSERT:Execute bare pip
testSystemPackagesNotAvailable
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named six
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 163, in _run_module_as_main
mod_name, _Error)
  File "/usr/lib/python2.7/runpy.py", line 111, in _get_module_details
__import__(mod_name)  # Do not catch exceptions initializing package
  File 
"/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/ve/lib/python2.7/site-packages/pip/__init__.py", 
line 6

def main(args: Optional[List[str]] = None) -> int:
 ^
SyntaxError: invalid syntax
testSystemPackagesAvailable
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 163, in _run_module_as_main
mod_name, _Error)
  File "/usr/lib/python2.7/runpy.py", line 111, in _get_module_details
__import__(mod_name)  # Do not catch exceptions initializing package
  File 
"/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/sysve/lib/python2.7/site-packages/pip/__init__.py", 
line 6

def main(args: Optional[List[str]] = None) -> int:
 ^
SyntaxError: invalid syntax
ASSERT:pip freeze lists system module from system-site-packages VE
testSetuptoolsAvailable
Traceback (most recent call last):
  File "", line 1, in 
  File 
"/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/ve/lib/python2.7/site-packages/setuptools/__init__.py", 
line 16, in 

import setuptools.version
  File 
"/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/ve/lib/python2.7/site-packages/setuptools/version.py", 
line 1, in 

import pkg_resources
  File 
"/tmp/autopkgtest-lxc.tsxq3czm/downtmp/autopkgtest_tmp/ve/lib/python2.7/site-packages/pkg_resources/__init__.py", 
line 117

f"{v} is an invalid version and will not be supported in "
 ^
SyntaxError: invalid syntax
ASSERT:Import 

Processed: CVE-2021-4122: cryptsetup 2.x: decryption through LUKS2 reencryption crash recovery

[Debian Bug Tracking System]

Processing control commands:

> found -1 2:2.3.5-1
Bug #1003686 [src:cryptsetup] CVE-2021-4122: cryptsetup 2.x: decryption through 
LUKS2 reencryption crash recovery
Marked as found in versions cryptsetup/2:2.3.5-1.
> found -1 2:2.4.2-1
Bug #1003686 [src:cryptsetup] CVE-2021-4122: cryptsetup 2.x: decryption through 
LUKS2 reencryption crash recovery
Marked as found in versions cryptsetup/2:2.4.2-1.

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

Bug#1003686: CVE-2021-4122: cryptsetup 2.x: decryption through LUKS2 reencryption crash recovery

[Guilhem Moulin]

Source: cryptsetup
Severity: grave
Tags: security upstream
Justification: root security hole
Control: found -1 2:2.3.5-1
Control: found -1 2:2.4.2-1
X-Debbugs-Cc: Debian Security Team 

Quoting :

| CVE-2021-4122 describes a possible attack against data confidentiality
| through LUKS2 online reencryption extension crash recovery.
| 
| An attacker can modify on-disk metadata to simulate decryption in
| progress with crashed (unfinished) reencryption step and persistently
| decrypt part of the LUKS device.
| 
| This attack requires repeated physical access to the LUKS device but
| no knowledge of user passphrases.
| 
| The decryption step is performed after a valid user activates
| the device with a correct passphrase and modified metadata.
| There are no visible warnings for the user that such recovery happened
| (except using the luksDump command). The attack can also be reversed
| afterward (simulating crashed encryption from a plaintext) with
| possible modification of revealed plaintext.
| […]
| The issue was found by Milan Broz as cryptsetup maintainer.

Upstream fixes:

  2.3 branch: 
https://gitlab.com/cryptsetup/cryptsetup/-/commit/60addcffa6794c29dccf33d8db5347f24b75f2fc
  2.4 branch: 
https://gitlab.com/cryptsetup/cryptsetup/-/commit/de98f011418c62e7b825a8ce3256e8fcdc84756e

Buster and earlier are not affected since their respective
(lib)cryptsetup don't support LUKS2 online reencryption.  I'll provide a
debdiff for bullseye-security.

-- 
Guilhem.


signature.asc
Description: PGP signature

Processed: Re: Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libpam-ssh
Bug #1003617 [libpam-runtime] libpam-runtime: When upgrading to 
libpam-runtime_1.4.0-11 pam_ssh is broken
Bug reassigned from package 'libpam-runtime' to 'libpam-ssh'.
No longer marked as found in versions pam/1.4.0-11.
Ignoring request to alter fixed versions of bug #1003617 to the same values 
previously set
> affects -1 src:pam
Bug #1003617 [libpam-ssh] libpam-runtime: When upgrading to 
libpam-runtime_1.4.0-11 pam_ssh is broken
Added indication that 1003617 affects src:pam
> tags -1 - moreinfo unreproducible
Bug #1003617 [libpam-ssh] libpam-runtime: When upgrading to 
libpam-runtime_1.4.0-11 pam_ssh is broken
Removed tag(s) unreproducible and moreinfo.

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

Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

[Steve Langasek]

Control: reassign -1 libpam-ssh
Control: affects -1 src:pam
Control: tags -1 - moreinfo unreproducible

On Thu, Jan 13, 2022 at 10:31:31AM +0100, Vincent-Xavier JUMEL wrote:
> The steps are :

> I've quickly reproduce the bug. You can follow these steps :
> 1. install debian stable in a vm
> 2. install libpam-ssh
> 3. upgrade it to debian sid

Ok, this is also reproducible by directly installing the unstable version of
the libpam-ssh package.  (I had attempted to do this before but missed that
my sources were out of date, so I was installing the stable version.)

/usr/share/pam-config/ssh-pwd declares an 'Additional' module and uses
'success=end'.  This is undefined behavior in pam-auth-update, which only
defines 'success=end' for 'Primary' module configs.

The pam package could potentially improve handling of this undefined
behavior, but in this case it's primarily a bug in libpam-ssh shipping a
broken config.

> Le 13 janv. à 10:06 Vincent-Xavier JUMEL a écrit
> > Hello,
> > 
> > I've quickly reproduce the bug. You can follow these steps :
> > 1. install debian stable in a vm
> > 2. upgrade it to debian sid
> > 
> > The mentionned line appears then in the /etc/pam.d/common-auth file
> > 
> > Le 13 janv. à 00:18 Steve Langasek a écrit
> > > Control: tags -1 moreinfo unreproducible
> > > 
> > > On Wed, Jan 12, 2022 at 06:28:45PM +0100, Vincent-Xavier JUMEL wrote:
> > > > Package: libpam-runtime
> > > > Version: 1.4.0-11
> > > > Severity: critical
> > > > Justification: breaks the whole system
> > > 
> > > > Dear Maintainer,
> > > > 
> > > >* Upgrade to the unstable version of libpam-runtime_1.14.0_11_all
> > > >with 
> > > >```
> > > >auth[success=0 default=ignore]  pam_ssh.so use_first_pass
> > > >```
> > > >* Login then failed
> > > >* I've modified "success=0" -> "success=1" to get back the login.
> > > 
> > > So where does this 'success=0' come from?  It doesn't come from
> > > /usr/share/pam-configs/ssh.  Installing libpam-ssh in unstable does not
> > > result in a config containing this line.  I'm not sure 'success=0' is 
> > > valid,
> > > and if it is, it means 'on success, process the next module' so your bug
> > > report, by slicing your config file to only show the single pam_ssh line,
> > > does not show what happens afterward that actually fails the stack.
> > > 
> > > -- 
> > > 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
> > 
> > 
> > 
> > -- 
> > Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net
> > 
> > Société Libre, Logiciel Libre http://www.april.org/adherer
> > Parinux, logiciel libre à Paris : http://www.parinux.org
> 
> -- 
> Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net
> 
> Société Libre, Logiciel Libre http://www.april.org/adherer
> Parinux, logiciel libre à Paris : http://www.parinux.org
> 

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


signature.asc
Description: PGP signature

Bug#1003685: cryptsetup: CVE-2021-4122

[Christoph Anton Mitterer]

Package: cryptsetup
Version: 2:2.4.2-1
Severity: critical
Tags: security upstream
Justification: root security hole


Hey.

You've probably seen it already... Milan found CVE-2021-4122, and
the package should be upgraded to 2.4.3 ASAP.

Thanks in advance,
Chris.

Bug#1003684: double-conversion: autopkgtest regression on i386: ./run_tests: terminated by signal 6

[Paul Gevers]

Source: double-conversion
Version: 3.1.7-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
double-conversion  from testing3.1.7-3
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=double-conversion

https://ci.debian.net/data/autopkgtest/testing/i386/d/double-conversion/1826/log.gz

CXX test/cctest/test-fixed-dtoa.cc
CXX test/cctest/test-conversions.cc
CXX test/cctest/test-diy-fp.cc
CXX test/cctest/cctest.cc
CXX test/cctest/gay-shortest-single.cc
CXX test/cctest/gay-precision.cc
CXX test/cctest/gay-shortest.cc
CXX test/cctest/test-ieee.cc
CXX test/cctest/test-fast-dtoa.cc
CXX test/cctest/gay-fixed.cc
CXX test/cctest/test-strtod.cc
CXX test/cctest/test-bignum.cc
CXX test/cctest/test-dtoa.cc
CXX test/cctest/test-bignum-dtoa.cc
LD run_tests
xargs: ./run_tests: terminated by signal 6
autopkgtest [11:10:53]: test unittest.sh



OpenPGP_signature
Description: OpenPGP digital signature

Processed: [bts-link] source package src:abyss

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:abyss
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1000577 (http://bugs.debian.org/1000577)
> # Bug title: abyss: autopkgtest regression on armhf and i386: Floating point 
> exception
> #  * https://github.com/bcgsc/abyss/issues/384
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1000577 + fixed-upstream
Bug #1000577 [src:abyss] abyss: autopkgtest regression on armhf and i386: 
Floating point exception
Added tag(s) fixed-upstream.
> usertags 1000577 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1000577 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#1002345: marked as done (python-mock: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 15:49:18 +
with message-id 
and subject line Bug#1002345: fixed in python-mock 4.0.3-3
has caused the Debian Bug report #1002345,
regarding python-mock: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p "3.10 3.9" returned exit code 13
to be marked as done.

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

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


-- 
1002345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mock
Version: 4.0.3-2
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):
>  debian/rules binary
> dh binary --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:237: python3.10 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'home-page' will not be supported in future versions. Please 
> use the underscore name 'home_page' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'author-email' will not be supported in future versions. 
> Please use the underscore name 'author_email' instead
>   warnings.warn(
> running config
> I: pybuild base:237: python3.9 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'home-page' will not be supported in future versions. Please 
> use the underscore name 'home_page' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'author-email' will not be supported in future versions. 
> Please use the underscore name 'author_email' instead
>   warnings.warn(
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:237: /usr/bin/python3.10 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'home-page' will not be supported in future versions. Please 
> use the underscore name 'home_page' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'author-email' will not be supported in future versions. 
> Please use the underscore name 'author_email' instead
>   warnings.warn(
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_mock/build/mock
> copying mock/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_mock/build/mock
> copying mock/mock.py -> 
> /<>/.pybuild/cpython3_3.10_mock/build/mock
> copying mock/backports.py -> 
> /<>/.pybuild/cpython3_3.10_mock/build/mock
> creating /<>/.pybuild/cpython3_3.10_mock/build/mock/tests
> copying mock/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_mock/build/mock/tests
> copying mock/tests/testasync.py -> 
> /<>/.pybuild/cpython3_3.10_mock/build/mock/tests
> copying mock/tests/testsealable.py -> 
> /<>/.pybuild/cpython3_3.10_mock/build/mock/tests
> copying mock/tests/testpatch.py -> 
> /<>/.pybuild/cpython3_3.10_mock/build/mock/tests
> copying mock/tests/testmagicmethods.py -> 
> /<>/.pybuild/cpython3_3.10_mock/build/mock/tests
> copying mock/tests/testsentinel.py -> 
> /<>/.pybuild/cpython3_3.10_mock/build/mock/tests
> copying mock/tests/testcallable.py -> 
> /<>/.pybuild/cpython3_3.10_mock/build/mock/tests
> copying mock/tests/testwith.py -> 
> /<>/.pybuild/cpython3_3.10_mock/build/mock/tests
> copying mock/tests/support.py -> 
> /<>/.pybuild/cpython3_3.10_mock/build/mock/tests
> copying mock/tests/testhelpers.py -> 
> /<>/.pybuild/cpython3_3.10_mock/build/mock/tests
> 

Bug#1001422: marked as done (python-mock: (autopkgtest) needs update for python3.10: InvalidSpecError)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 15:49:18 +
with message-id 
and subject line Bug#1001422: fixed in python-mock 4.0.3-3
has caused the Debian Bug report #1001422,
regarding python-mock: (autopkgtest) needs update for python3.10: 
InvalidSpecError
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.)


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

Source: python-mock
Version: 4.0.3-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of python-mock fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
python-mockfrom testing4.0.3-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 python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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

Paul

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

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

=== FAILURES 
===
_ MockTest.test_bool_not_called_when_passing_spec_arg 
__


self = testMethod=test_bool_not_called_when_passing_spec_arg>


def test_bool_not_called_when_passing_spec_arg(self):
class Something:
def __init__(self):
self.obj_with_bool_func = unittest.mock.MagicMock()
obj = Something()

  with unittest.mock.patch.object(obj, 'obj_with_bool_func', 
autospec=True): pass


/usr/lib/python3/dist-packages/mock/tests/testmock.py:2176: _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = 

def __enter__(self):
"""Perform the patch."""
new, spec, spec_set = self.new, self.spec, self.spec_set
autospec, kwargs = self.autospec, self.kwargs
new_callable = self.new_callable
self.target = self.getter()
# normalise False to None
if spec is False:
spec = None
if spec_set is False:
spec_set = None
if autospec is False:
autospec = None
if spec is not None and autospec is not None:
raise TypeError("Can't specify spec and autospec")
if ((spec is not None or autospec is not None) and
spec_set not in (True, None)):
raise TypeError("Can't provide explicit spec_set *and* spec 
or autospec")

original, local = self.get_original()
if new is DEFAULT and autospec is None:
inherit = False
if spec is True:
# set spec to the object we are replacing
spec = original
if spec_set is True:
spec_set = original
spec = None
elif spec is not None:
if spec_set is True:
spec_set = spec
spec = None
elif spec_set is True:
spec_set = original
if spec is not None or spec_set is not None:
if original is DEFAULT:
raise TypeError("Can't use 'spec' with create=True")
if isinstance(original, type):
# If we're patching out a class and there is a spec
inherit = True
if spec is None and _is_async_obj(original):
Klass = AsyncMock
else:
Klass = MagicMock
_kwargs = {}
if new_callable is not None:
Klass = new_callable
elif spec is not None or spec_set is not None:
this_spec = spec
if 

Processed: Bug#1002345 marked as pending in python-mock

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002345 [src:python-mock] python-mock: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) pending.

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

Bug#1001422: marked as pending in python-mock

[Michael Fladischer]

Control: tag -1 pending

Hello,

Bug #1001422 in python-mock 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/python-team/packages/python-mock/-/commit/ee2710e160b4d695156f558dfefb9a23a02801b2


Add upstream patch to fix tests that should test mock but were testing 
unittest.mock (Closes: #1001422, #1002345).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001422

Processed: Bug#1001422 marked as pending in python-mock

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1001422 [src:python-mock] python-mock: (autopkgtest) needs update for 
python3.10: InvalidSpecError
Added tag(s) pending.

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

Bug#1002345: marked as pending in python-mock

[Michael Fladischer]

Control: tag -1 pending

Hello,

Bug #1002345 in python-mock 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/python-team/packages/python-mock/-/commit/ee2710e160b4d695156f558dfefb9a23a02801b2


Add upstream patch to fix tests that should test mock but were testing 
unittest.mock (Closes: #1001422, #1002345).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002345

Bug#1003606: marked as done (python3-flask-httpauth: missing Breaks+Replaces: python-flask-httpauth-doc (<< 4))

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 15:35:06 +
with message-id 
and subject line Bug#1003606: fixed in python-flask-httpauth 4.5.0-3
has caused the Debian Bug report #1003606,
regarding python3-flask-httpauth: missing Breaks+Replaces: 
python-flask-httpauth-doc (<< 4)
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.)


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

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../python3-flask-httpauth_4.5.0-1_all.deb ...
  Unpacking python3-flask-httpauth (4.5.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-flask-httpauth_4.5.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/flask-httpauth.1.gz', which is also 
in package python-flask-httpauth-doc 3.2.4-3.1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-flask-httpauth_4.5.0-1_all.deb

Obviously the manpage was moved between the packages.


cheers,

Andreas


python-flask-httpauth-doc=3.2.4-3.1_python3-flask-httpauth=4.5.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-flask-httpauth
Source-Version: 4.5.0-3
Done: Martina Ferrari 

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

Debian distribution maintenance software
pp.
Martina Ferrari  (supplier of updated python-flask-httpauth 
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, 13 Jan 2022 15:09:34 +
Source: python-flask-httpauth
Architecture: source
Version: 4.5.0-3
Distribution: unstable
Urgency: medium
Maintainer: Martina Ferrari 
Changed-By: Martina Ferrari 
Closes: 1003606
Changes:
 python-flask-httpauth (4.5.0-3) unstable; urgency=medium
 .
   * Move manpage to section 3. Closes: #1003606
Checksums-Sha1:
 d4ea3e124dd6bfe529e49483fe45a258b706b219 2220 python-flask-httpauth_4.5.0-3.dsc
 86dcd872a5978b810ec051293615b90090f1c004 5228 
python-flask-httpauth_4.5.0-3.debian.tar.xz
 9aa907213bfd555dd8a99614a33b1b6b2e2a45b4 8444 
python-flask-httpauth_4.5.0-3_amd64.buildinfo
Checksums-Sha256:
 1d144c8ed3e3acf546b0fda821b2e5725b72482fb51c5f2e3839a77d2b83413e 2220 
python-flask-httpauth_4.5.0-3.dsc
 119e95d0f97214a76d6d7e734841971f52227cecdb68f0cdf9fd1f6c5e8e4828 5228 
python-flask-httpauth_4.5.0-3.debian.tar.xz
 2e336ed51f1afee9531f924984f8157c78b51ffa93adc5f362a0bd88fb1c3bf3 8444 
python-flask-httpauth_4.5.0-3_amd64.buildinfo
Files:
 3700395bffa29bae08c4d14f48a128cc 2220 python optional 
python-flask-httpauth_4.5.0-3.dsc
 311327f42e80c6b0235b3f4a002540b9 5228 python optional 
python-flask-httpauth_4.5.0-3.debian.tar.xz
 868803e3551863b4879f598edb3a927f 8444 python optional 
python-flask-httpauth_4.5.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE2qbv8cYn6hwmsaaSqiMPxF+MJ7EFAmHgQRAACgkQqiMPxF+M
J7Evvg/9EBJ9U6zz8Tz7dy1LGVqIjs4DrUXIl3rNmijblDYo2k0Z3cuM5tx2nfFT
iLV5+n/Tu1inZZiUskdlA4Zb2fyEUx8l1jc+4uidZNTAT7Qd+qyjHyuFdL3U5Eb5
rqcNGVTkRQ4LnE0nZ5ZCseJWn2d7+ZeZ1ZPcBCsAwhazuTkqFPIk3VyOmv+NBNd2
sso/juJGyQUUTrtaslrdF3wbI+eHZPHsh5cZtZnrzNUGmLMf5FXTd1Vs1kBW06L0
/r63Mg4VRHTNzuZ8+6+e0Q4uvAFJLWgygL3ggcdAozmkgfpv7kA52qp+04QkGKOv
Zmx3Uek1mj5xBmAFmDLrkHZkiqrGATPlkDkzMBzBN4HuCKs7kGPouCk3txJbF+EG
ZXIfZwEw29yThlI31GdSNgYF8TRWT+Ef5qsaplKVKFiApBYxsPc1eoeoc43Edp8/
74GhQ+8/j5VmjZ9RxbAGfIKKyqsP4VJZwiZd5Y90aX4sChiH9N6oGKCOvEbIt8qg
0BH1snTjUUku5SR+jwEE67+tItj9ABouwYs/y2hHSEOSUAegH1YrcheKbzTasBAm

Bug#999071: marked as done (docbook-simple: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 15:33:50 +
with message-id 
and subject line Bug#999071: fixed in docbook-simple 1.1-6
has caused the Debian Bug report #999071,
regarding docbook-simple: missing required debian/rules targets build-arch 
and/or build-indep
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.)


-- 
999071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: docbook-simple
Version: 1.1-5
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: docbook-simple
Source-Version: 1.1-6
Done: Mathieu Malaterre 

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated docbook-simple 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 13 Jan 2022 16:09:55 +0100
Source: docbook-simple
Architecture: source
Version: 1.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: Mathieu Malaterre 
Closes: 802367 999071
Changes:
 docbook-simple (1.1-6) unstable; urgency=medium
 .
   * d/watch Update to latest uscan version
   * d/rules: Migrate d/rules to newer style. Closes: #999071
   * d/control: Bump Std-Vers to 4.6.0 no changes needed
   * d/control: Migrate to team maintenance. Closes: #802367
Checksums-Sha1:
 d82dd55996ba93278fca31bd902eb2adf55d4ca8 2033 docbook-simple_1.1-6.dsc
 e14e104956f4bc26e154d08c4cfeb0dbe184706a 8056 
docbook-simple_1.1-6.debian.tar.xz
 9b23fe536610872f00b1efd03118b8880d246afd 6101 
docbook-simple_1.1-6_source.buildinfo
Checksums-Sha256:
 5820f01af8d1f80ea7913e823812c6ff71568bc99894e786a2b7355e13ce1a1e 2033 
docbook-simple_1.1-6.dsc
 11943e474b827366abb42191eaccdd1c52731616fa4edf7c13d97dc4b42b3784 8056 
docbook-simple_1.1-6.debian.tar.xz
 7ed0d7e997ca77ec9d2ff8d9148ac989598329e0e75e9cd25721d99e46cfaa5f 6101 
docbook-simple_1.1-6_source.buildinfo
Files:
 b3058e7cca9819c2adce513b196ca9df 2033 text optional docbook-simple_1.1-6.dsc
 7a2e72f8810e5b33467c3939ade97ca5 8056 text optional 
docbook-simple_1.1-6.debian.tar.xz
 a09a3943de7f43034ac452561d97758a 6101 text optional 
docbook-simple_1.1-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmHgQSkRHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0UrzBAAhOENC02Pk8AslE3/bNTxlWrfDzJmc8Yj
6mZhHCdoMwmhsthK3ZWMzQt218YpD3GZ5G3BCM+XCDR5Osa7NrMopbxYa9Zqk9Kj
5BRdfhOa8iMl+pOliy/XXjfN/m74OA9of3F0OlFIytBgocFQUQb2IGHu+EcPBUAd
PkOeeSfD/SXtrxcN0KdqSob4ckobeOfsVcy0do7cYTD8g0bF1MAFM4PqFs5ctxSn
dRoQXY9TivZ5mxTgMLuXfxxMHds8mqbjDc1rovR4QdPhX57MaycN8Nl8qvDGhFEZ
UtueCgqNHy6UujJCDPNaTpCGxtqfiVfCY5ph1z0q9UNc4Xx4eN077kAdrNCd6ytv
oc6KlVyMKYQ/MPzmRjZLFPjCc55a/lkY1xIQaG+hRSOBIaqmh52ivgLGG7Rvf73r
fCFRCkcRYfkhvzXWbfXX6+N5B/RtMTfxc90NK0ySGiUqYK1VPYhhkZHJlZ/Mt/92
9sd04A0xNoA1RnVvLszJVqrGIvetDRfuKHhzUbj+jt33oj5KAiejjOyJo1mL7MPp
8lra/vwzSF+00dVbL+MmqQ+uXqNjeYZZfvsjl596021Yn2Inw679EMuraEH51mb+
yT2bF2AjvWQj9sFOOdXiiYPV32FbELlvtHw47U8TGqbYUo0X8QMvg9ox+O23EEnT
9kc65Tp0CpI=
=A3Jy
-END PGP SIGNATURE End Message ---

Processed: closing 1003670

[Debian Bug Tracking System]

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

> close 1003670 1.4.4-3
Bug #1003670 [src:php-mockery] php-mockery: (autopkgtest) needs update for 
php8.1: Test directory 
"/tmp/autopkgtest-lxc.dt9l77z_/downtmp/build.5Ul/src/./tests/PHP80" not found
Marked as fixed in versions php-mockery/1.4.4-3.
Bug #1003670 [src:php-mockery] php-mockery: (autopkgtest) needs update for 
php8.1: Test directory 
"/tmp/autopkgtest-lxc.dt9l77z_/downtmp/build.5Ul/src/./tests/PHP80" not found
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1003670: closing 1003670

[David Prévot]

close 1003670 1.4.4-3
thanks

Bug#1003606: closed by Debian FTP Masters (reply to Martina Ferrari ) (Bug#1003606: fixed in python-flask-httpauth 4.5.0-2)

[Martina Ferrari]

Hi Andreas,

On 13/01/2022 12:51, Andreas Beckmann wrote:


you reinstated
   Breaks+Replaces: python-flask-httpauth (<< 3.2.4-1)
in the -doc package, which is actually no longer needed since the 
python2 package is gone.


OUCH, I guess I completely misread your report. Sorry, I hadn't slept 
well! :(


This B+R probably stems from the time when the man page was moved to 
-doc in oder to make the python2 and python3 packages co-installable and 
using alternatives (pure guess, many packages did it this way when 
adding python3 support).


Yes, AFAIR that was the reason.


As I said in the Subject, python3-flask-httpauth needs
   Breaks+Replaces: python-flask-httpauth-doc (<< 4)
So it's the other way around and in the python3 package this time for 
moving the man page back to the package containing /usr/bin/flask-httpauth.


WAIT, there is a flask-httpauth(1) manpage, but I cannot find the 
corresponding command anywhere. And the man page is actually not for a 
command, so it should not be in section 1. I'm not sure where it 
belongs, though (perhaps section 3 or 7).
So just move the manpage to the correct section and forget about 
Breaks+Replaces ;-)


Ah, good point. That man page is generated from the sphinx 
documentation. It was originally in the doc package, but I thought it 
made more sense in the main package. Will do the rename as you suggest, 
I think section 3 is the right place.


Thanks again.

--
Martina Ferrari (Tina)

Bug#1003679: cryfs: autopkgtest regression on armhf: Resource temporarily unavailable

[Paul Gevers]

Source: cryfs
Version: 0.11.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
cryfs  from testing0.11.1-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=cryfs

https://ci.debian.net/data/autopkgtest/testing/armhf/c/cryfs/18257610/log.gz


[--] 4 tests from QueueMapTest_MoveConstructor
[ RUN  ] QueueMapTest_MoveConstructor.PushingAndPopping_MoveIntoMap
[   OK ] QueueMapTest_MoveConstructor.PushingAndPopping_MoveIntoMap 
(0 ms)
[ RUN  ] 
QueueMapTest_MoveConstructor.PushingAndPoppingPerKey_MoveIntoMap
[   OK ] 
QueueMapTest_MoveConstructor.PushingAndPoppingPerKey_MoveIntoMap (0 ms)

[ RUN  ] QueueMapTest_MoveConstructor.PushingAndPopping_CopyIntoMap
[   OK ] QueueMapTest_MoveConstructor.PushingAndPopping_CopyIntoMap 
(0 ms)
[ RUN  ] 
QueueMapTest_MoveConstructor.PushingAndPoppingPerKey_CopyIntoMap
[   OK ] 
QueueMapTest_MoveConstructor.PushingAndPoppingPerKey_CopyIntoMap (0 ms)

[--] 4 tests from QueueMapTest_MoveConstructor (0 ms total)

[--] 12 tests from QueueMapTest_MemoryLeak
[ RUN  ] QueueMapTest_MemoryLeak.Empty
[   OK ] QueueMapTest_MemoryLeak.Empty (0 ms)
[ RUN  ] QueueMapTest_MemoryLeak.AfterPushingOne
[   OK ] QueueMapTest_MemoryLeak.AfterPushingOne (0 ms)
[ RUN  ] QueueMapTest_MemoryLeak.AfterPushingTwo
[   OK ] QueueMapTest_MemoryLeak.AfterPushingTwo (0 ms)
[ RUN  ] QueueMapTest_MemoryLeak.AfterPushingTwoAndPoppingOldest
[   OK ] QueueMapTest_MemoryLeak.AfterPushingTwoAndPoppingOldest (0 ms)
[ RUN  ] QueueMapTest_MemoryLeak.AfterPushingTwoAndPoppingFirst
[   OK ] QueueMapTest_MemoryLeak.AfterPushingTwoAndPoppingFirst (0 ms)
[ RUN  ] QueueMapTest_MemoryLeak.AfterPushingTwoAndPoppingLast
[   OK ] QueueMapTest_MemoryLeak.AfterPushingTwoAndPoppingLast (0 ms)
[ RUN  ] QueueMapTest_MemoryLeak.AfterPushingOnePoppingOne
[   OK ] QueueMapTest_MemoryLeak.AfterPushingOnePoppingOne (0 ms)
[ RUN  ] QueueMapTest_MemoryLeak.AfterPushingOnePoppingOnePerKey
[   OK ] QueueMapTest_MemoryLeak.AfterPushingOnePoppingOnePerKey (0 ms)
[ RUN  ] QueueMapTest_MemoryLeak.AfterPushingOnePoppingOnePushingOne
[   OK ] QueueMapTest_MemoryLeak.AfterPushingOnePoppingOnePushingOne 
(0 ms)
[ RUN  ] 
QueueMapTest_MemoryLeak.AfterPushingOnePoppingOnePerKeyPushingOne
[   OK ] 
QueueMapTest_MemoryLeak.AfterPushingOnePoppingOnePerKeyPushingOne (0 ms)

[ RUN  ] QueueMapTest_MemoryLeak.AfterPushingOnePoppingOnePushingSame
[   OK ] 
QueueMapTest_MemoryLeak.AfterPushingOnePoppingOnePushingSame (0 ms)
[ RUN  ] 
QueueMapTest_MemoryLeak.AfterPushingOnePoppingOnePerKeyPushingSame
[   OK ] 
QueueMapTest_MemoryLeak.AfterPushingOnePoppingOnePerKeyPushingSame (0 ms)

[--] 12 tests from QueueMapTest_MemoryLeak (1 ms total)

[--] 4 tests from CacheTest_RaceCondition
[ RUN  ] 
CacheTest_RaceCondition.PopBlocksWhileRequestedElementIsThrownOut_ByAge
[   OK ] 
CacheTest_RaceCondition.PopBlocksWhileRequestedElementIsThrownOut_ByAge 
(1543 ms)
[ RUN  ] 
CacheTest_RaceCondition.PopDoesntBlockWhileOtherElementIsThrownOut_ByAge

terminate called after throwing an instance of 'std::system_error'
  what():  Resource temporarily unavailable
Aborted
autopkgtest [06:35:46]: test blockstore



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003678: sqlite3 breaks crowdsec autopkgtest: invalid type \"INTEGER\" for column

[Paul Gevers]

Source: sqlite3, crowdsec
Control: found -1 sqlite3/3.37.2-1
Control: found -1 crowdsec/1.0.9-3
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
sqlite3from testing3.37.2-1
crowdsec   from testing1.0.9-3
versioned deps [0] from testingfrom unstable
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 sqlite3 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

[0] You can see what packages were added from the second line of the log 
file quoted below. The migration software adds source package from 
unstable to the list if they are needed to install packages from 
sqlite3/3.37.2-1. I.e. due to versioned dependencies or breaks/conflicts.

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

https://ci.debian.net/data/autopkgtest/testing/amd64/c/crowdsec/18271072/log.gz

=== RUN   TestSimulatedAlert
time="2022-01-12T20:11:40Z" level=info msg="Creating new API server"
 - [Wed, 12 Jan 2022 20:11:41 UTC] "POST /v1/watchers HTTP/1.1 201 
98.133294ms "crowdsec-test/" "
time="2022-01-12T20:11:41Z" level=fatal msg="unable to create new 
database client: failed creating schema resources: sql/schema: invalid 
type \"INTEGER\" for column \"events_count\""

FAILgithub.com/crowdsecurity/crowdsec/pkg/apiserver 0.130s
?   	github.com/crowdsecurity/crowdsec/pkg/apiserver/controllers	[no 
test files]
?   	github.com/crowdsecurity/crowdsec/pkg/apiserver/controllers/v1	[no 
test files]
?   	github.com/crowdsecurity/crowdsec/pkg/apiserver/middlewares/v1	[no 
test files]


OpenPGP_signature
Description: OpenPGP digital signature

Processed: sqlite3 breaks crowdsec autopkgtest: invalid type \"INTEGER\" for column

[Debian Bug Tracking System]

Processing control commands:

> found -1 sqlite3/3.37.2-1
Bug #1003678 [src:sqlite3, src:crowdsec] sqlite3 breaks crowdsec autopkgtest: 
invalid type \"INTEGER\" for column
Marked as found in versions sqlite3/3.37.2-1.
> found -1 crowdsec/1.0.9-3
Bug #1003678 [src:sqlite3, src:crowdsec] sqlite3 breaks crowdsec autopkgtest: 
invalid type \"INTEGER\" for column
Marked as found in versions crowdsec/1.0.9-3.

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

Bug#1003674: php-sabre-vobject: (autopkgtest) needs update for php8.1: ValueError: Epoch doesn't fit in a PHP integer

[Paul Gevers]

Source: php-sabre-vobject
Version: 2.1.7-6
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php7.4 with php8.1 [0]. With a 
recent upload of php-defaults the autopkgtest of php-sabre-vobject fails 
in testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable on armhf and i386 (both 32 bits 
architectures). It passes when run with only packages from testing. In 
tabular form:


   passfail
php-defaults   from testing92
php-sabre-vobject  from testing2.1.7-6
versioned deps from testingfrom unstable
all others from testingfrom testing

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

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


php-commom added a whole set of versioned Breaks to make sure the right 
packages from current unstable are pulled in during testing. If the 
issue is caused by a missing breaks, please reasign this bug to php-common.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/armhf/p/php-sabre-vobject/18255681/log.gz

PHPUnit 9.5.11 by Sebastian Bergmann and contributors.

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


...  63 / 
553 ( 11%)
... 126 / 
553 ( 22%)
...R... 189 / 
553 ( 34%)
.R..E.. 252 / 
553 ( 45%)
..RR..RR..R 315 / 
553 ( 56%)
RRR 378 / 
553 ( 68%)
RRR 441 / 
553 ( 79%)
RRR 504 / 
553 ( 91%)
RRR..   553 / 
553 (100%)


Time: 00:00.087, Memory: 12.00 MB

There was 1 error:

1) Sabre\VObject\RecurrenceIteratorTest::testYearly
ValueError: Epoch doesn't fit in a PHP integer

/usr/share/php/Sabre/VObject/RecurrenceIterator.php:687
/tmp/autopkgtest-lxc.20ggb02o/downtmp/build.CCT/src/tests/Sabre/VObject/RecurrenceIteratorTest.php:973


OpenPGP_signature
Description: OpenPGP digital signature

Processed: php-sabre-vobject: (autopkgtest) needs update for php8.1: ValueError: Epoch doesn't fit in a PHP integer

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:php-defaults
Bug #1003674 [src:php-sabre-vobject] php-sabre-vobject: (autopkgtest) needs 
update for php8.1: ValueError: Epoch doesn't fit in a PHP integer
Added indication that 1003674 affects src:php-defaults

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

Processed: php-mockery: (autopkgtest) needs update for php8.1: Test directory "/tmp/autopkgtest-lxc.dt9l77z_/downtmp/build.5Ul/src/./tests/PHP80" not found

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:php-defaults
Bug #1003670 [src:php-mockery] php-mockery: (autopkgtest) needs update for 
php8.1: Test directory 
"/tmp/autopkgtest-lxc.dt9l77z_/downtmp/build.5Ul/src/./tests/PHP80" not found
Added indication that 1003670 affects src:php-defaults

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

Bug#1003670: php-mockery: (autopkgtest) needs update for php8.1: Test directory "/tmp/autopkgtest-lxc.dt9l77z_/downtmp/build.5Ul/src/./tests/PHP80" not found

[Paul Gevers]

Source: php-mockery
Version: 1.4.2-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

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


   passfail
php-defaults   from testing92
php-mockeryfrom testing1.4.2-1
versioned deps from testingfrom unstable
all others from testingfrom testing

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

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


php-commom added a whole set of versioned Breaks to make sure the right 
packages from current unstable are pulled in during testing. If the 
issue is caused by a missing breaks, please reasign this bug to php-common.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-mockery/18254695/log.gz

phpab %development% - Copyright (C) 2009 - 2022 by Arne Blankerts and 
Contributors


Scanning directory tests

Autoload file vendor/autoload.php generated.

PHP Deprecated:  Return type of 
MockeryTest_ImplementsIteratorAggregate::getIterator() should either be 
compatible with IteratorAggregate::getIterator(): Traversable, or the 
#[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in 
/tmp/autopkgtest-lxc.dt9l77z_/downtmp/build.5Ul/src/tests/Mockery/ContainerTest.php 
on line 1759
PHP Deprecated:  Return type of 
MockeryTest_ImplementsIterator::current() should either be compatible 
with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] 
attribute should be used to temporarily suppress the notice in 
/tmp/autopkgtest-lxc.dt9l77z_/downtmp/build.5Ul/src/tests/Mockery/ContainerTest.php 
on line 1771
PHP Deprecated:  Return type of MockeryTest_ImplementsIterator::next() 
should either be compatible with Iterator::next(): void, or the 
#[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in 
/tmp/autopkgtest-lxc.dt9l77z_/downtmp/build.5Ul/src/tests/Mockery/ContainerTest.php 
on line 1779
PHP Deprecated:  Return type of MockeryTest_ImplementsIterator::key() 
should either be compatible with Iterator::key(): mixed, or the 
#[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in 
/tmp/autopkgtest-lxc.dt9l77z_/downtmp/build.5Ul/src/tests/Mockery/ContainerTest.php 
on line 1775
PHP Deprecated:  Return type of MockeryTest_ImplementsIterator::valid() 
should either be compatible with Iterator::valid(): bool, or the 
#[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in 
/tmp/autopkgtest-lxc.dt9l77z_/downtmp/build.5Ul/src/tests/Mockery/ContainerTest.php 
on line 1783
PHP Deprecated:  Return type of MockeryTest_ImplementsIterator::rewind() 
should either be compatible with Iterator::rewind(): void, or the 
#[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in 
/tmp/autopkgtest-lxc.dt9l77z_/downtmp/build.5Ul/src/tests/Mockery/ContainerTest.php 
on line 1767
PHP Deprecated:  MockeryTest_ClassThatImplementsSerializable implements 
the Serializable interface, which is deprecated. Implement __serialize() 
and __unserialize() instead (or in addition, if support for old PHP 
versions is necessary) in 
/tmp/autopkgtest-lxc.dt9l77z_/downtmp/build.5Ul/src/tests/Mockery/ContainerTest.php 
on line 1848

PHPUnit 9.5.11 by Sebastian Bergmann and contributors.

Test directory 
"/tmp/autopkgtest-lxc.dt9l77z_/downtmp/build.5Ul/src/./tests/PHP80" not 
found

autopkgtest [05:27:48]: test command1



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003669: php-imagick: (autopkgtest) needs update for php8.1: No PHPT expectation found in /usr/share/php/PHPUnit/Runner/PhptTestCase.php

[Paul Gevers]

Source: php-imagick
Version: 3.6.0-4
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

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


   passfail
php-defaults   from testing92
php-imagickfrom testing3.6.0-4
versioned deps from testingfrom unstable
all others from testingfrom testing

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

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


php-commom added a whole set of versioned Breaks to make sure the right 
packages from current unstable are pulled in during testing. If the 
issue is caused by a missing breaks, please reasign this bug to php-common.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-imagick/18254677/log.gz

PHPUnit 9.5.11 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.1.1

.SI..S.SS..  63 / 
312 ( 20%)
S.. 126 / 
312 ( 40%)
.S. 189 / 
312 ( 60%)
..S.S...S..SS.. 252 / 
312 ( 80%)
S.S.S.SS.S.S..S...S...E..S..312 / 
312 (100%)


Time: 01:15.958, Memory: 4.00 MB

There was 1 error:

1) 
/tmp/autopkgtest-lxc.0xaw1h0b/downtmp/build.pyA/src/imagick-3.6.0/tests/bug81235.phpt
PHPUnit\Runner\Exception: No PHPT expectation found in 
/usr/share/php/PHPUnit/Runner/PhptTestCase.php:375

Stack trace:
#0 /usr/share/php/PHPUnit/Runner/PhptTestCase.php(203): 
PHPUnit\Runner\PhptTestCase->assertPhptExpectation()
#1 /usr/share/php/PHPUnit/Framework/TestSuite.php(678): 
PHPUnit\Runner\PhptTestCase->run()
#2 /usr/share/php/PHPUnit/TextUI/TestRunner.php(670): 
PHPUnit\Framework\TestSuite->run()
#3 /usr/share/php/PHPUnit/TextUI/Command.php(143): 
PHPUnit\TextUI\TestRunner->run()
#4 /usr/share/php/PHPUnit/TextUI/Command.php(96): 
PHPUnit\TextUI\Command->run()

#5 /usr/bin/phpunit(73): PHPUnit\TextUI\Command::main()
#6 {main}
--

There was 1 incomplete test:

1) 
/tmp/autopkgtest-lxc.0xaw1h0b/downtmp/build.pyA/src/imagick-3.6.0/tests/031_Imagick_affineTransformImage_basic.phpt

XFAIL section but test passes



OpenPGP_signature
Description: OpenPGP digital signature

Processed: php-imagick: (autopkgtest) needs update for php8.1: No PHPT expectation found in /usr/share/php/PHPUnit/Runner/PhptTestCase.php

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:php-defaults
Bug #1003669 [src:php-imagick] php-imagick: (autopkgtest) needs update for 
php8.1: No PHPT expectation found in 
/usr/share/php/PHPUnit/Runner/PhptTestCase.php
Added indication that 1003669 affects src:php-defaults

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

Processed: Re: RFS: kic/2.4c-1 [QA] [RC] -- Enhanced KIC layout editor

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1003464 [sponsorship-requests] RFS: kic/2.4c-1 [QA] [RC] -- Enhanced KIC 
layout editor
Added tag(s) pending.
> tag 688189 pending
Bug #688189 [kic] kic: newer upstream release
Added tag(s) pending.
> tag 999088 pending
Bug #999088 [src:kic] kic: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) pending.

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

Processed: bug #1002367: forwarded to upstream fix

[Debian Bug Tracking System]

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

> # Please note that upstream homepage is unreachable
> # I'm started from https://www.pygal.org instead of http://pygal.org
> # Thanks.
> forwarded 1002367 https://github.com/Kozea/pygal/issues/500
Bug #1002367 [src:python-pygal] python-pygal: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit 
code 13
Set Bug forwarded-to-address to 'https://github.com/Kozea/pygal/issues/500'.
> --
Stopping processing here.

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

Bug#1003606: closed by Debian FTP Masters (reply to Martina Ferrari ) (Bug#1003606: fixed in python-flask-httpauth 4.5.0-2)

[Andreas Beckmann]

Control: found -1 4.5.0-2

Hi,

you reinstated
  Breaks+Replaces: python-flask-httpauth (<< 3.2.4-1)
in the -doc package, which is actually no longer needed since the 
python2 package is gone.
This B+R probably stems from the time when the man page was moved to 
-doc in oder to make the python2 and python3 packages co-installable and 
using alternatives (pure guess, many packages did it this way when 
adding python3 support).


As I said in the Subject, python3-flask-httpauth needs
  Breaks+Replaces: python-flask-httpauth-doc (<< 4)
So it's the other way around and in the python3 package this time for 
moving the man page back to the package containing /usr/bin/flask-httpauth.


WAIT, there is a flask-httpauth(1) manpage, but I cannot find the 
corresponding command anywhere. And the man page is actually not for a 
command, so it should not be in section 1. I'm not sure where it 
belongs, though (perhaps section 3 or 7).
So just move the manpage to the correct section and forget about 
Breaks+Replaces ;-)


Andreas

Processed: Re: Bug#1003606 closed by Debian FTP Masters (reply to Martina Ferrari ) (Bug#1003606: fixed in python-flask-httpauth 4.5.0-2)

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.5.0-2
Bug #1003606 {Done: Martina Ferrari } [python3-flask-httpauth] 
python3-flask-httpauth: missing Breaks+Replaces: python-flask-httpauth-doc (<< 
4)
Marked as found in versions python-flask-httpauth/4.5.0-2; no longer marked as 
fixed in versions python-flask-httpauth/4.5.0-2 and reopened.

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

Bug#1003667: php-horde-data: (autopkgtest) needs update for php8.1: deprecation warnings on stderr

[Paul Gevers]

Source: php-horde-data
Version: 2.1.5-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

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


   passfail
php-defaults   from testing92
php-horde-data from testing2.1.5-2
versioned deps from testingfrom unstable
all others from testingfrom testing

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

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


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


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

Paul

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

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

PHPUnit 9.5.11 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.1.1
Configuration: 
/tmp/autopkgtest-lxc.fs93bltp/downtmp/build.VnG/src/Horde_Data-2.1.5/test/Horde/Data/phpunit.xml


Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.fs93bltp/downtmp/build.VnG/src/Horde_Data-2.1.5/test/Horde/Data/CsvTest.php

   Class name was 'Horde_Data_CsvTest', expected 'CsvTest'
Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.fs93bltp/downtmp/build.VnG/src/Horde_Data-2.1.5/test/Horde/Data/GetCsvTest.php
   Class name was 'Horde_Data_GetCsvTest', expected 
'GetCsvTest'


PHP Deprecated:  Return type of Horde_Variables::offsetExists($field) 
should either be compatible with ArrayAccess::offsetExists(mixed 
$offset): bool, or the #[\ReturnTypeWillChange] attribute should be used 
to temporarily suppress the notice in /usr/share/php/Horde/Variables.php 
on line 137
PHP Deprecated:  Return type of Horde_Variables::offsetGet($field) 
should either be compatible with ArrayAccess::offsetGet(mixed $offset): 
mixed, or the #[\ReturnTypeWillChange] attribute should be used to 
temporarily suppress the notice in /usr/share/php/Horde/Variables.php on 
line 175
PHP Deprecated:  Return type of Horde_Variables::offsetSet($field, 
$value) should either be compatible with ArrayAccess::offsetSet(mixed 
$offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute 
should be used to temporarily suppress the notice in 
/usr/share/php/Horde/Variables.php on line 240
PHP Deprecated:  Return type of Horde_Variables::offsetUnset($field) 
should either be compatible with ArrayAccess::offsetUnset(mixed 
$offset): void, or the #[\ReturnTypeWillChange] attribute should be used 
to temporarily suppress the notice in /usr/share/php/Horde/Variables.php 
on line 287
PHP Deprecated:  Return type of Horde_Variables::count() should either 
be compatible with Countable::count(): int, or the 
#[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in /usr/share/php/Horde/Variables.php on line 391
PHP Deprecated:  Return type of Horde_Variables::getIterator() should 
either be compatible with IteratorAggregate::getIterator(): Traversable, 
or the #[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in /usr/share/php/Horde/Variables.php on line 398
PHP Deprecated:  auto_detect_line_endings is deprecated in 
/tmp/autopkgtest-lxc.fs93bltp/downtmp/build.VnG/src/Horde_Data-2.1.5/lib/Horde/Data/Csv.php 
on line 328
PHP Deprecated:  auto_detect_line_endings is deprecated in 
/tmp/autopkgtest-lxc.fs93bltp/downtmp/build.VnG/src/Horde_Data-2.1.5/lib/Horde/Data/Csv.php 
on line 328
PHP Deprecated:  auto_detect_line_endings is deprecated in 
/tmp/autopkgtest-lxc.fs93bltp/downtmp/build.VnG/src/Horde_Data-2.1.5/lib/Horde/Data/Csv.php 
on line 328
PHP Deprecated:  auto_detect_line_endings is deprecated in 
/tmp/autopkgtest-lxc.fs93bltp/downtmp/build.VnG/src/Horde_Data-2.1.5/lib/Horde/Data/Csv.php 
on line 328
PHP Deprecated:  

Processed: php-horde-data: (autopkgtest) needs update for php8.1: deprecation warnings on stderr

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:php-defaults
Bug #1003667 [src:php-horde-data] php-horde-data: (autopkgtest) needs update 
for php8.1: deprecation warnings on stderr
Added indication that 1003667 affects src:php-defaults

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

Processed: php-horde-crypt-blowfish: (autopkgtest) needs update for php8.1: deprecation warnings on stderr

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:php-defaults
Bug #1003666 [src:php-horde-crypt-blowfish] php-horde-crypt-blowfish: 
(autopkgtest) needs update for php8.1: deprecation warnings on stderr
Added indication that 1003666 affects src:php-defaults

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

Bug#1003666: php-horde-crypt-blowfish: (autopkgtest) needs update for php8.1: deprecation warnings on stderr

[Paul Gevers]

Source: php-horde-crypt-blowfish
Version: 1.1.3-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php7.4 with php8.1 [0]. With a 
recent upload of php-defaults the autopkgtest of 
php-horde-crypt-blowfish fails in testing when that autopkgtest is run 
with the binary packages of php-defaults from unstable on armhf and i386 
(both 32 bit architectures). It passes when run with only packages from 
testing. In tabular form:


 passfail
php-defaults from testing92
php-horde-crypt-blowfish from testing1.1.3-2
versioned deps   from testingfrom unstable
all others   from testingfrom testing

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

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


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/armhf/p/php-horde-crypt-blowfish/1823/log.gz

PHPUnit 9.5.11 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.1.1
Configuration: 
/tmp/autopkgtest-lxc.ojxdquu1/downtmp/build.tSW/src/Horde_Crypt_Blowfish-1.1.3/test/Horde/Crypt/Blowfish/phpunit.xml


Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.ojxdquu1/downtmp/build.tSW/src/Horde_Crypt_Blowfish-1.1.3/test/Horde/Crypt/Blowfish/CbcTest.php
   Class name was 'Horde_Crypt_Blowfish_CbcTest', expected 
'CbcTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.ojxdquu1/downtmp/build.tSW/src/Horde_Crypt_Blowfish-1.1.3/test/Horde/Crypt/Blowfish/EcbTest.php
   Class name was 'Horde_Crypt_Blowfish_EcbTest', expected 
'EcbTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.ojxdquu1/downtmp/build.tSW/src/Horde_Crypt_Blowfish-1.1.3/test/Horde/Crypt/Blowfish/Pbkdf2Test.php
   Class name was 'Horde_Crypt_Blowfish_Pbkdf2Test', 
expected 'Pbkdf2Test'


.PHP Deprecated:  Implicit conversion 
from float 2242054355 to int loses precision in 
/tmp/autopkgtest-lxc.ojxdquu1/downtmp/build.tSW/src/Horde_Crypt_Blowfish-1.1.3/lib/Horde/Crypt/Blowfish/Php/Base.php 
on line 334
PHP Deprecated:  Implicit conversion from float 2752067618 to int loses 
precision in 
/tmp/autopkgtest-lxc.ojxdquu1/downtmp/build.tSW/src/Horde_Crypt_Blowfish-1.1.3/lib/Horde/Crypt/Blowfish/Php/Base.php 
on line 334
PHP Deprecated:  Implicit conversion from float 3964562569 to int loses 
precision in 
/tmp/autopkgtest-lxc.ojxdquu1/downtmp/build.tSW/src/Horde_Crypt_Blowfish-1.1.3/lib/Horde/Crypt/Blowfish/Php/Base.php 
on line 334
PHP Deprecated:  Implicit conversion from float 3193202383 to int loses 
precision in 
/tmp/autopkgtest-lxc.ojxdquu1/downtmp/build.tSW/src/Horde_Crypt_Blowfish-1.1.3/lib/Horde/Crypt/Blowfish/Php/Base.php 
on line 334
PHP Deprecated:  Implicit conversion from float 3232508343 to int loses 
precision in 
/tmp/autopkgtest-lxc.ojxdquu1/downtmp/build.tSW/src/Horde_Crypt_Blowfish-1.1.3/lib/Horde/Crypt/Blowfish/Php/Base.php 
on line 334
PHP Deprecated:  Implicit conversion from float 3380367581 to int loses 
precision in 
/tmp/autopkgtest-lxc.ojxdquu1/downtmp/build.tSW/src/Horde_Crypt_Blowfish-1.1.3/lib/Horde/Crypt/Blowfish/Php/Base.php 
on line 334
PHP Deprecated:  Implicit conversion from float 3041331479 to int loses 
precision in 
/tmp/autopkgtest-lxc.ojxdquu1/downtmp/build.tSW/src/Horde_Crypt_Blowfish-1.1.3/lib/Horde/Crypt/Blowfish/Php/Base.php 
on line 334
PHP Deprecated:  Implicit conversion from float 2450970073 to int loses 
precision in 
/tmp/autopkgtest-lxc.ojxdquu1/downtmp/build.tSW/src/Horde_Crypt_Blowfish-1.1.3/lib/Horde/Crypt/Blowfish/Php/Base.php 
on line 334
PHP Deprecated:  Implicit conversion from float 2306472731 to int loses 
precision in 
/tmp/autopkgtest-lxc.ojxdquu1/downtmp/build.tSW/src/Horde_Crypt_Blowfish-1.1.3/lib/Horde/Crypt/Blowfish/Php/Base.php 
on line 

Bug#1003665: php-horde-core: (autopkgtest) needs update for php8.1: deprecation warnings on stderr

[Paul Gevers]

Source: php-horde-core
Version: 2.31.16+debian0-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

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


   passfail
php-defaults   from testing92
php-horde-core from testing2.31.16+debian0-2
versioned deps from testingfrom unstable
all others from testingfrom testing

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

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


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


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

Paul

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

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

Generating locales (this might take a while)...
  en_US.UTF-8... done
  en_US.UTF-8... done
Generation complete.
PHPUnit 9.5.11 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.1.1
Configuration: 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/phpunit.xml


Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/Factory/GroupTest.php
   Class name was 'Horde_Core_Factory_GroupTest', expected 
'GroupTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/Factory/KolabServerTest.php
   Class name was 'Horde_Core_Factory_KolabServerTest', 
expected 'KolabServerTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/Factory/KolabSessionTest.php
   Class name was 'Horde_Core_Factory_KolabSessionTest', 
expected 'KolabSessionTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/NlsconfigTest.php
   Class name was 'Horde_Core_NlsconfigTest', expected 
'NlsconfigTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/RegistryTest.php
   Class name was 'Horde_Core_RegistryTest', expected 
'RegistryTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/SmartmobileUrlTest.php
   Class name was 'Horde_Core_SmartmobileUrlTest', expected 
'SmartmobileUrlTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.75k7yr80/downtmp/build.7nj/src/Horde_Core-2.31.16/test/Horde/Core/UrlTest.php

   Class name was 'Horde_Core_UrlTest', expected 'UrlTest'

PHP Deprecated:  Method ReflectionParameter::getClass() is deprecated in 
/usr/share/php/Horde/Injector/DependencyFinder.php on line 61
PHP Deprecated:  Method ReflectionParameter::getClass() is deprecated in 
/usr/share/php/Horde/Injector/DependencyFinder.php on line 62
PHP Deprecated:  Return type of 
Horde_Support_Stub::offsetExists($offset) should either be compatible 
with ArrayAccess::offsetExists(mixed $offset): bool, or the 
#[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in /usr/share/php/Horde/Support/Stub.php on line 111
PHP Deprecated:  Return type of Horde_Support_Stub::offsetGet($offset) 
should either be compatible with ArrayAccess::offsetGet(mixed $offset): 
mixed, or the #[\ReturnTypeWillChange] attribute should be used to 
temporarily suppress the notice in 

Bug#1002986: libguestfs-tools: Depends on guestfs-tools that is not in the archive

[Paul Gevers]

Hi,

guestfs-tools was accepted in the archive, but it can't be (re)built 
anywhere because it requires:
libcamomile-ocaml-dev- that isn't provided by 
libcamomile-ocaml-dev. I have no idea how ocaml packages work, but this 
needs to be fixed.


Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: php-horde-core: (autopkgtest) needs update for php8.1: deprecation warnings on stderr

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:php-defaults
Bug #1003665 [src:php-horde-core] php-horde-core: (autopkgtest) needs update 
for php8.1: deprecation warnings on stderr
Added indication that 1003665 affects src:php-defaults

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

Bug#1003664: fwupd: Too loose dependency on libfwupdN

[Guillem Jover]

Package: fwupd
Version: 1.5.7-5
Severity: serious

Hi!

This package seems to use a too loose dependency on at least
libfwupdN, but I suspect the same applies to libfwupdpluginM (or even
libfwupdN from libfwupdpluginM).

These are encoded as >=, which causes them to be upgradable on new
upstream releases, and do break partial upgrades. Right now I've got
fwupd held due to the signed version not being yet available, and
libfwupdplugin1 is not upgraded as that bumped its SONAME, but libfwupd2
did, and now the daemon is segfaulting. This is not the first time
this has happened, but I guess I forgot to file the other time, which
means this seems to be consistent behavior as with requiring exact
versions of the library:

  fwupd[108906]: 21:12:16:0092 GLib-GIO g_file_new_for_path: 
assertion 'path != NULL' failed
  fwupd[108906]: 21:12:16:0092 GLib-GIO g_file_query_file_type: 
assertion 'G_IS_FILE(file)' failed
  fwupd[108906]: 21:12:16:0092 GLib-GIO g_file_monitor_file: 
assertion 'G_IS_FILE (file)' failed
  kernel: fwupd[108906]: segfault at 8 ip 559242c78109 sp 7ffe4df24910 
error 4 in fwupd[559242c73000+26000]
  kernel: Code: ff 85 c0 0f 85 97 02 00 00 48 8b 7c 24 30 e8 5e d5 ff ff e9 67 
01 00 00 48 8b 44 24 28 48 8d 3d dc 14 02 00 41 be 01 00 00 00 <48> 8b 70 08 31 
c0 e8 4c f4 ff ff 4d 85 e4 74 08 4c 89 e7 e8 5f db

So it looks like all the intra library dependencies should be changed
to «libfwup.* (= )».

Thanks,
Guillem

Processed: golang-github-containers-image: FTBFS: tests fail with 'key has been revoked'

[Debian Bug Tracking System]

Processing control commands:

> found -1 5.17.0-1
Bug #1003663 [src:golang-github-containers-image] 
golang-github-containers-image: FTBFS: tests fail with 'key has been revoked'
Marked as found in versions golang-github-containers-image/5.17.0-1.

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

Bug#1003663: golang-github-containers-image: FTBFS: tests fail with 'key has been revoked'

[Andreas Beckmann]

Source: golang-github-containers-image
Version: 5.16.0-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Control: found -1 5.17.0-1

Hi,

golang-github-containers-image recently started to FTBFS, some tests
report a key as revoked. This could also be caused by an updated
toolchain package or build-dependency.

=== RUN   TestSessionKeyring
keyring_test.go:23: key has been revoked
--- FAIL: TestSessionKeyring (0.00s)
=== RUN   TestUserKeyring
--- PASS: TestUserKeyring (0.00s)
=== RUN   TestLink
keyring_test.go:95: key has been revoked
--- FAIL: TestLink (0.00s)
=== RUN   TestUnlink
keyring_test.go:142: key has been revoked
--- FAIL: TestUnlink (0.00s)
=== RUN   TestReadKeyring
--- PASS: TestReadKeyring (0.00s)
=== RUN   TestDescribe
--- PASS: TestDescribe (0.00s)
FAIL
FAILgithub.com/containers/image/internal/pkg/keyctl 0.106s


Andreas


golang-github-containers-image.sid.build.gz
Description: application/gzip

Bug#999131: marked as done (uqm-russian: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 11:33:46 +
with message-id 
and subject line Bug#999131: fixed in uqm-russian 1.0.2-6
has caused the Debian Bug report #999131,
regarding uqm-russian: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uqm-russian
Version: 1.0.2-5
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: uqm-russian
Source-Version: 1.0.2-6
Done: Stephen Kitt 

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated uqm-russian package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 13 Jan 2022 12:03:28 +0100
Source: uqm-russian
Architecture: source
Version: 1.0.2-6
Distribution: unstable
Urgency: medium
Maintainer: Dmitry E. Oboukhov 
Changed-By: Stephen Kitt 
Closes: 999131
Changes:
 uqm-russian (1.0.2-6) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Matija Nalis ]
   * Update the VCS URIs to point to Salsa.
   * Switch to debhelper compatibility level 13, using dh.
 Closes: #999131.
Checksums-Sha1:
 180775ce7685d10ed6e0575cc760dfe5de0fa612 1963 uqm-russian_1.0.2-6.dsc
 cfe591b6f9337aa475aff078b46e77e55769bcbb 2476 uqm-russian_1.0.2-6.debian.tar.xz
 6354babfd08a488bedf16eaabc20c2c65f6f07ac 6371 
uqm-russian_1.0.2-6_source.buildinfo
Checksums-Sha256:
 e8f14025bb57e2017fa1302f0868f9a394607745d4c2dbbda2b412cef62ca8c3 1963 
uqm-russian_1.0.2-6.dsc
 9658b1c23e4fe238d4b95a03ebae36a0012c340ea181a691b3d2631d3dfb4a0b 2476 
uqm-russian_1.0.2-6.debian.tar.xz
 aba068e5d4ff8f4b108f001d74719afc332f8ab4ccf807b13cb4be3ff5fe7425 6371 
uqm-russian_1.0.2-6_source.buildinfo
Files:
 be1471f85e45c85247c072909ca2c1c1 1963 contrib/games optional 
uqm-russian_1.0.2-6.dsc
 6644d788452f010defcf54941be4e53e 2476 contrib/games optional 
uqm-russian_1.0.2-6.debian.tar.xz
 48921782735e96052a386d098ae45a6f 6371 contrib/games optional 
uqm-russian_1.0.2-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmHgCAgACgkQgNMC9Yht
g5x7Vw//VBAH3a/ebXq1zenUpxjOTfY8If52iISEnAVdNAcT/JFT2kN+NEgWxHEZ
ngO4Piuyn0Xeu+VYeKXJingZFO81YlRsLTW2Kql4waIjqW/8294jx1869i6Emb7k
CNCU4aURyv9w7gN+WIZDMzYOeVwl0G1o+Er8zoVG1sL7rx/jYCNVjSEnXjeLdidt
Elsf243SAb/t7Q2xnlVzRQY461VLQa2Zh0heUD/NonZpy7Hy2DfSeBf2WBRb6YiW
Vs3on3+V24Kjv634htTpK3l0RJnO0p3XsODNqapTalPFoanWSGGnpcM6WcxGMvK8
YeRStpQONzMyWcj5skcj/DHRiYGh7RJrUxS0W3Hfw8N02maxiF6FzNX7hI2oNqAM
agBkQW+S//wGsb4yxhZ45V02lDh9FFn6czCaG3DKyovuNBrG7EmFWxPf6OPzn8H8
dvDkdpIaq5KkPzmW5w8jOC2MacxXt7PsK8k8cusJKQ5c54EDqLIGWXqRM1c/JGjL
BU3ugOUW7/JoLrEvCGo1RZilZzqxO6/IacZrnRHZzcAoxHyWeWKLzhNG9QAywQeG
+2ExES69kPR/q20sXjYZx6xpiXtUmTEdDs69Vn3/1DMzqaHoFgdF90wrbDfb+ul/
O2y9FTMgN4yhAv1tw6yfHdo//dsQFapAgMrCD0fSpVaKmc3Y4VM=
=zvjg
-END PGP SIGNATURE End Message ---

Bug#1003661: img2pdf's autopkg tests fail with pillow 9.0.0

[Matthias Klose]

Package: src:img2pdf
Version: 0.4.2-1
Severity: serious
Tags: sid bookworm

img2pdf's autopkg tests fail with pillow 9.0.0, as seen at
https://tracker.debian.org/pkg/img2pdf

=== short test summary info 
FAILED src/img2pdf_test.py::test_general[animation.gif-internal] - AssertionE...
FAILED src/img2pdf_test.py::test_general[animation.gif-pikepdf] - AssertionEr...
ERROR src/img2pdf_test.py::test_gif_animation[internal] - TypeError: object i...
ERROR src/img2pdf_test.py::test_gif_animation[pikepdf] - TypeError: object is...

there is a new upstream version available.

Bug#1003655: marked as done (uqm: FTBFS on i386: Error: register value used as expression)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 11:20:14 +
with message-id 
and subject line Bug#1003655: fixed in uqm 0.6.2.dfsg-9.7
has caused the Debian Bug report #1003655,
regarding uqm: FTBFS on i386: Error: register value used as expression
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.)


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

Hi,

the recent uqm upload FTBFS on i386:

https://buildd.debian.org/status/fetch.php?pkg=uqm=i386=0.6.2.dfsg-9.6=1641935490=0

gcc -c  -o "obj/release/src/sc2code/libs/graphics/sdl/2xscalers_mmx.c.o" -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT 
-I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -O3 -DGFXMODULE_SDL 
-DHAVE_OPENGL  -DSOUNDMODULE_SDL   -DNETPLAY=NETPLAY_FULL -DHAVE_JOYSTICK 
-DHAVE_ZIP=1  -DUSE_PLATFORM_ACCEL -I "." -g -Wdate-time -D_FORTIFY_SOURCE=2 -I 
src -I src/sc2code -I src/sc2code/libs 
"src/sc2code/libs/graphics/sdl/2xscalers_mmx.c"
src/sc2code/libs/graphics/sdl/scalemmx.h: Assembler messages:
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used 

Bug#1003660: daq: FTBFS: undefined reference to `__wrap_stat'

[Andreas Beckmann]

Source: daq
Version: 3.0.0-alpha5-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

daq/experimental recently started to FTBFS, due to some updated
build-essential toolchain package or build dependency.
(My previous build attempt was on 2021-03-13 and successful.)

libtool: link: gcc -Wstrict-prototypes -Wmissing-prototypes 
-Wold-style-definition -Wnested-externs -I../api -g -O2 
-ffile-prefix-map=/build/daq-3.0.0-alpha5=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,--wrap -Wl,printf -Wl,--wrap -Wl,__printf_chk 
-Wl,--wrap -Wl,fprintf -Wl,--wrap -Wl,__fprintf_chk -Wl,--wrap -Wl,opendir 
-Wl,--wrap -Wl,readdir -Wl,--wrap -Wl,closedir -Wl,--wrap -Wl,stat -Wl,--wrap 
-Wl,__xstat -Wl,--wrap -Wl,dlopen -Wl,--wrap -Wl,dlsym -Wl,--wrap -Wl,dlclose 
-Wl,-z -Wl,relro -o api_base_test api_base_test-api_base_test.o 
api_base_test-daq_test_module.o api_base_test-mock_stdio.o  
../api/.libs/libdaq.a -ldl -lcmocka
/usr/bin/ld: ../api/.libs/libdaq.a(libdaq_la-daq_base.o): in function 
`daq_load_dynamic_module':
./api/daq_base.c:204: undefined reference to `__wrap_stat'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:640: api_base_test] Error 1

Andreas


daq_3.0.0-alpha5-1.log.gz
Description: application/gzip

Bug#1003655: uqm: FTBFS on i386: Error: register value used as expression

[Andreas Beckmann]

Source: uqm
Version: 0.6.2.dfsg-9.6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

the recent uqm upload FTBFS on i386:

https://buildd.debian.org/status/fetch.php?pkg=uqm=i386=0.6.2.dfsg-9.6=1641935490=0

gcc -c  -o "obj/release/src/sc2code/libs/graphics/sdl/2xscalers_mmx.c.o" -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT 
-I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -O3 -DGFXMODULE_SDL 
-DHAVE_OPENGL  -DSOUNDMODULE_SDL   -DNETPLAY=NETPLAY_FULL -DHAVE_JOYSTICK 
-DHAVE_ZIP=1  -DUSE_PLATFORM_ACCEL -I "." -g -Wdate-time -D_FORTIFY_SOURCE=2 -I 
src -I src/sc2code -I src/sc2code/libs 
"src/sc2code/libs/graphics/sdl/2xscalers_mmx.c"
src/sc2code/libs/graphics/sdl/scalemmx.h: Assembler messages:
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: junk `(%ebp)' after 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:640: Error: register value used as 
expression
src/sc2code/libs/graphics/sdl/scalemmx.h:638: Error: junk `(%ebp)' after 
expression

Bug#1003654: ptex-jtex: Removal of obsolete debhelper compat 5 and 6 in bookworm

[Andreas Beckmann]

Source: ptex-jtex
Version: 1.7+1-15
Severity: serious
Tags: ftbfs sid bookworm
User: nthyk...@master.debian.org
Usertags: compat-5-6-removal

Hi,

The package ptex-jtex uses debhelper with a compat level of 5 or 6,
which is no longer supported [1].

Please bump the debhelper compat at your earliest convenience

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


Thanks,
Andreas

[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

Bug#999074: marked as done (iec16022: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 10:03:52 +
with message-id 
and subject line Bug#999074: fixed in iec16022 0.2.4-1.3
has caused the Debian Bug report #999074,
regarding iec16022: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iec16022
Version: 0.2.4-1.2
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: iec16022
Source-Version: 0.2.4-1.3
Done: Jakob Haufe 

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

Debian distribution maintenance software
pp.
Jakob Haufe  (supplier of updated iec16022 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, 12 Jan 2022 20:44:57 +
Source: iec16022
Architecture: source
Version: 0.2.4-1.3
Distribution: unstable
Urgency: medium
Maintainer: Jan Lübbe 
Changed-By: Jakob Haufe 
Closes: 984436 999074
Changes:
 iec16022 (0.2.4-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Refresh packaging (Closes: #999074)
 - Switch to 3.0 (quilt)
 - Switch to dh sequencer
 - Switch to compat 13
   * Drop obsolete Vcs-* fields
   * Update project homepage, watchfile (Closes: #984436)
Checksums-Sha1:
 a4478751ebdf9123b0550240d4b141b588dc7f41 1875 iec16022_0.2.4-1.3.dsc
 495ddd4500db15b837dd3f632f0465f44fc827aa 3392 iec16022_0.2.4-1.3.debian.tar.xz
 a7ba8a4c0b468ea80afadda94d9aa06c9d073d91 6782 
iec16022_0.2.4-1.3_source.buildinfo
Checksums-Sha256:
 a4091f134c1463959afe5d23b8ca0cb705da387acd45b068a2ee6bc943e1ee49 1875 
iec16022_0.2.4-1.3.dsc
 22e7e41241398610b9d102acbc92c999864b0fde067cdd0e0fce4f8d4b3036ab 3392 
iec16022_0.2.4-1.3.debian.tar.xz
 d029f2231ae32ebdae38434330e1e000b41eaea1634124741a16e632a534c7ed 6782 
iec16022_0.2.4-1.3_source.buildinfo
Files:
 8ae2ee3fc394e8c1416c90cd4f50254e 1875 graphics optional iec16022_0.2.4-1.3.dsc
 d67d791576a4ff67fb9e04856cb51c77 3392 graphics optional 
iec16022_0.2.4-1.3.debian.tar.xz
 56f1259a2ff33015ce3e05be08939c74 6782 graphics optional 
iec16022_0.2.4-1.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEe/X2rDZDH11A3BN6TPKyGPVNrj0FAmHf8l8ACgkQTPKyGPVN
rj3TtQ//ZWbhU5RYff//gHL/B1hlKrWaxyc0miOfRbN/YS3d3xMuFQ/xUR3KsZ2U
EfIUpgLa+3tjIRBfFncPighhGcnyUzYXYiZKfaeIzMuuV4lbTgrNpBcaavsjO7jo
8uV7GohbkM4RJ7y5g/V6b9599c+gLcb2DjTgIx6mD2AN60dHirJnFP42aHfFy87A
qADQ5mXtSxM/TguRkUJUQ9pQYgQP5cC/rqHHtR/XNWnBWTQPYDg24psaN1t9AZwK
u4iGOqA6AufD+wgBMdjlF8pn0DDvkimjZFMlJAaFiK0ltq+PzoKvtWaRIZzthIGl
kPbhdqM4S1mVcvYEPIX+hEnyRSkn+9JahlQPTLgz9B2/VZ6tnLob+/fJ6ctKEnm5
F0k8gAeFpGEN5c8AGTztzpkNxYKKdVuxFxV6szsEpb/QQDx7ypt7YcdJkZyaqn4Z
384yTljlT9LeTVjuYzqVhGqjVBEuUD9jDG8/+OCC3tt6+eatYX4DXM8CA69xhfm/
4TFQHkTPtWxuyRAceuxqZpYHGY3wYo+cyNz4z3tXxEPI8cLrrC8qXAkjIIFsHzMM
g409GhlQSdNbxBZGPJSDY7dOROUBr3jUm/pT0huaP8Kp5RTNbDFpFyWQQgOpjnYn
AxpV03tCy+hDptO9K4u7ycIsZvyNeNLFZMoeWr5kNCbbImORUuw=
=LppP
-END PGP SIGNATURE End Message ---

Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

[Vincent-Xavier JUMEL]

Further investagations :
activating pam_ssh.so via pam-auth-update insert the success=0 line in the
/etc/pam.d/common-auth file

Configuration seems to be declared in /usr/share/pam-configs/ssh-pwd (and I
don't see any significative difference with ssh-server and ssh-client)

-- 
Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net

Société Libre, Logiciel Libre http://www.april.org/adherer
Parinux, logiciel libre à Paris : http://www.parinux.org

Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

[Vincent-Xavier JUMEL]

The steps are :

I've quickly reproduce the bug. You can follow these steps :
1. install debian stable in a vm
2. install libpam-ssh
3. upgrade it to debian sid

Le 13 janv. à 10:06 Vincent-Xavier JUMEL a écrit
> Hello,
> 
> I've quickly reproduce the bug. You can follow these steps :
> 1. install debian stable in a vm
> 2. upgrade it to debian sid
> 
> The mentionned line appears then in the /etc/pam.d/common-auth file
> 
> Le 13 janv. à 00:18 Steve Langasek a écrit
> > Control: tags -1 moreinfo unreproducible
> > 
> > On Wed, Jan 12, 2022 at 06:28:45PM +0100, Vincent-Xavier JUMEL wrote:
> > > Package: libpam-runtime
> > > Version: 1.4.0-11
> > > Severity: critical
> > > Justification: breaks the whole system
> > 
> > > Dear Maintainer,
> > > 
> > >* Upgrade to the unstable version of libpam-runtime_1.14.0_11_all
> > >with 
> > >```
> > >auth[success=0 default=ignore]  pam_ssh.so use_first_pass
> > >```
> > >* Login then failed
> > >* I've modified "success=0" -> "success=1" to get back the login.
> > 
> > So where does this 'success=0' come from?  It doesn't come from
> > /usr/share/pam-configs/ssh.  Installing libpam-ssh in unstable does not
> > result in a config containing this line.  I'm not sure 'success=0' is valid,
> > and if it is, it means 'on success, process the next module' so your bug
> > report, by slicing your config file to only show the single pam_ssh line,
> > does not show what happens afterward that actually fails the stack.
> > 
> > -- 
> > 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
> 
> 
> 
> -- 
> Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net
> 
> Société Libre, Logiciel Libre http://www.april.org/adherer
> Parinux, logiciel libre à Paris : http://www.parinux.org

-- 
Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net

Société Libre, Logiciel Libre http://www.april.org/adherer
Parinux, logiciel libre à Paris : http://www.parinux.org

Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

[Vincent-Xavier JUMEL]

Hello,

I've quickly reproduce the bug. You can follow these steps :
1. install debian stable in a vm
2. upgrade it to debian sid

The mentionned line appears then in the /etc/pam.d/common-auth file

Le 13 janv. à 00:18 Steve Langasek a écrit
> Control: tags -1 moreinfo unreproducible
> 
> On Wed, Jan 12, 2022 at 06:28:45PM +0100, Vincent-Xavier JUMEL wrote:
> > Package: libpam-runtime
> > Version: 1.4.0-11
> > Severity: critical
> > Justification: breaks the whole system
> 
> > Dear Maintainer,
> > 
> >* Upgrade to the unstable version of libpam-runtime_1.14.0_11_all
> >with 
> >```
> >auth[success=0 default=ignore]  pam_ssh.so use_first_pass
> >```
> >* Login then failed
> >* I've modified "success=0" -> "success=1" to get back the login.
> 
> So where does this 'success=0' come from?  It doesn't come from
> /usr/share/pam-configs/ssh.  Installing libpam-ssh in unstable does not
> result in a config containing this line.  I'm not sure 'success=0' is valid,
> and if it is, it means 'on success, process the next module' so your bug
> report, by slicing your config file to only show the single pam_ssh line,
> does not show what happens afterward that actually fails the stack.
> 
> -- 
> 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



-- 
Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net

Société Libre, Logiciel Libre http://www.april.org/adherer
Parinux, logiciel libre à Paris : http://www.parinux.org

Bug#1003627: [Pkg-pascal-devel] Bug#1003627: Bug#1003627: fpc: autopkgtest regression on ppc64el:

[Abou Al Montacir]

Hi,

On Thu, 2022-01-13 at 19:39 +1100, David Bannon wrote:
> 
> 
> I wonder if this relates to the hardening issue ?  Hardening on PPC63le
> with FPC is not currently working, it makes a non viable binary.
> 
> https://gitlab.com/freepascal.org/fpc/source/-/issues/39451
The issue is due to the patch proposed by upstream and adding this test.
I'll revert it.
-- 
Cheers,
Abou Al Montacir


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

Bug#991151: marked as done (procps: dropped the reload option from the init script, breaking corekeeper)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 09:18:56 +
with message-id 
and subject line Bug#991151: fixed in procps 2:3.3.17-6
has caused the Debian Bug report #991151,
regarding procps: dropped the reload option from the init script, breaking 
corekeeper
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.)


-- 
991151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: corekeeper
Version: 1.7
Severity: serious
Justification: does not uninstall
X-Debbugs-Cc: t...@mirbsd.de

Removing corekeeper:x32 (1.7) ...
Usage: /etc/init.d/procps {start|stop|status|restart|try-restart|force-reload}
invoke-rc.d: initscript procps, action "reload" failed.
dpkg: error processing package corekeeper:x32 (--remove):
 installed corekeeper:x32 package post-removal script subprocess returned error 
exit status 3
dpkg: too many errors, stopping
Errors were encountered while processing:
 corekeeper:x32



-- System Information:
Debian Release: 11.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), 
(100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: x32, i386

Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages corekeeper depends on:
ii  procps  2:3.3.17-5

corekeeper recommends no packages.

corekeeper suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: procps
Source-Version: 2:3.3.17-6
Done: Craig Small 

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated procps package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 13 Jan 2022 19:46:59 +1100
Source: procps
Architecture: source
Version: 2:3.3.17-6
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Closes: 987557 991151 1000908
Changes:
 procps (2:3.3.17-6) unstable; urgency=medium
 .
   * Add reload option for init script Closes: #991151
   * Follow naming convention for systemd files debian/procps!3 Closes:
 #1000908
   * Fix FBTFS on Hurd Closes: #987557
Checksums-Sha1:
 8084764fec838f0512f6fc9acf7b823b97f558f8 2136 procps_3.3.17-6.dsc
 fd24c4ff2a130fa690149bfd6b94aee73909ba47 28984 procps_3.3.17-6.debian.tar.xz
 423979e6c9be2f2612b0315bce7b72dd5c214730 7349 procps_3.3.17-6_amd64.buildinfo
Checksums-Sha256:
 4bb6b0f37eae3c31938354f8785faa756796a6232619a853af65341bbc080846 2136 
procps_3.3.17-6.dsc
 86577e3f70e388e3e5c4e53d79d9e85fc446a3a79b6b7ba67c216e24855ba9a2 28984 
procps_3.3.17-6.debian.tar.xz
 c4414504c2fa5f98c59dd4129df8739c15e70d6f49a082b000bdb0630aa677d7 7349 
procps_3.3.17-6_amd64.buildinfo
Files:
 c1fb79c7c721fa856bbd1549da16c765 2136 admin optional procps_3.3.17-6.dsc
 8964edfe1b1299a768ef4ba97549ab13 28984 admin optional 
procps_3.3.17-6.debian.tar.xz
 2063b784c826f93ee08d1de282601a35 7349 admin optional 
procps_3.3.17-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAmHf6FoACgkQAiFmwP88
hOMwRg/6An6TNBGf1eW12SRUbz/qbJjLUVfwb0ovKCaW8TViAg27D+Nx/yr0LpFR
Q0BMKGSaDUyPcVy1fETn7tZCaL/AJxNjkvPQQGlwIfiYSw8RM8WWGOKHe+u0gRvP
8/A1Ai0zbWVSUIQbBKB9E2GihqukYqbblXjIl52nIpX2J/Fh46o/tOmimb+INmpP
4qZn0dS9dy10P16U6drQoeNVeVVHXl0DxTqBOKlaOQRpjVLjtjyd8rIGepwJSVRx
8jWazCD0+conyMepUfnNY7kkIKRHNPpR0t4SrpmXgM7pS7rTOyIl+cfR4/kZcWuy
QbFcYsVaERLn7wfg5GqFor+BiGOpGh5f6kN6Kd4j5xRYioB4Ap6VdkRBRsCKTbOO
KGBLCRFh/5bLYWKKJjJo/VcNkZ9l2cpadMheLCKBq+zqzbt+nNVUHBOmBuz96MSM
oDYykN1wBLp7/AArmjegBpc4Nt8Hiry8g2SlQban/g9avJSGnQAxEXKp/lxAtWFC
reNYT97AgEG3NcBJ/phDNyA1SNkDzD9RIQVHrKpIci0lRnhKgOTtelIZE98NdJ8G
67r5tHYw7GhfUn0afUkg7AZYXDhwpKNKraTF7vsVCSsDoueI8Fo097PCsrMIKhsZ
Am7umRUcwM1/I1sUJs8lO7KUsg3+vscCH63+PV+CO7xuwuy2zuo=
=XcTa
-END PGP SIGNATURE End Message ---

Bug#1003652: php-horde-compress: (autopkgtest) needs update for php8.1: deprecation warnings on stderr

[Paul Gevers]

Source: php-horde-compress
Version: 2.2.4-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

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


   passfail
php-defaults   from testing92
php-horde-compress from testing2.2.4-1
versioned deps from testingfrom unstable
all others from testingfrom testing

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

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


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


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

Paul

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

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

PHPUnit 9.5.11 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.1.1
Configuration: 
/tmp/autopkgtest-lxc.tdea4k_c/downtmp/build.DSa/src/Horde_Compress-2.2.4/test/Horde/Compress/phpunit.xml


Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.tdea4k_c/downtmp/build.DSa/src/Horde_Compress-2.2.4/test/Horde/Compress/RarTest.php

   Class name was 'Horde_Compress_RarTest', expected 'RarTest'
Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.tdea4k_c/downtmp/build.DSa/src/Horde_Compress-2.2.4/test/Horde/Compress/TarTest.php

   Class name was 'Horde_Compress_TarTest', expected 'TarTest'
Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.tdea4k_c/downtmp/build.DSa/src/Horde_Compress-2.2.4/test/Horde/Compress/TnefTest.php
   Class name was 'Horde_Compress_TnefTest', expected 
'TnefTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.tdea4k_c/downtmp/build.DSa/src/Horde_Compress-2.2.4/test/Horde/Compress/ZipTest.php

   Class name was 'Horde_Compress_ZipTest', expected 'ZipTest'

PHP Deprecated:  Return type of 
Horde_Support_Stub::offsetExists($offset) should either be compatible 
with ArrayAccess::offsetExists(mixed $offset): bool, or the 
#[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in /usr/share/php/Horde/Support/Stub.php on line 111
PHP Deprecated:  Return type of Horde_Support_Stub::offsetGet($offset) 
should either be compatible with ArrayAccess::offsetGet(mixed $offset): 
mixed, or the #[\ReturnTypeWillChange] attribute should be used to 
temporarily suppress the notice in /usr/share/php/Horde/Support/Stub.php 
on line 98
PHP Deprecated:  Return type of Horde_Support_Stub::offsetSet($offset, 
$value) should either be compatible with ArrayAccess::offsetSet(mixed 
$offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute 
should be used to temporarily suppress the notice in 
/usr/share/php/Horde/Support/Stub.php on line 105
PHP Deprecated:  Return type of Horde_Support_Stub::offsetUnset($offset) 
should either be compatible with ArrayAccess::offsetUnset(mixed 
$offset): void, or the #[\ReturnTypeWillChange] attribute should be used 
to temporarily suppress the notice in 
/usr/share/php/Horde/Support/Stub.php on line 118
PHP Deprecated:  Return type of Horde_Support_Stub::count() should 
either be compatible with Countable::count(): int, or the 
#[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in /usr/share/php/Horde/Support/Stub.php on line 126
PHP Deprecated:  Return type of Horde_Support_Stub::getIterator() should 
either be compatible with IteratorAggregate::getIterator(): Traversable, 
or the #[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in /usr/share/php/Horde/Support/Stub.php on line 135
...SS..PHP Deprecated:  Return type of 

Processed: php-horde-auth: (autopkgtest) needs update for php8.1: deprecation warnings on stderr

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:php-defaults
Bug #1003651 [src:php-horde-auth] php-horde-auth: (autopkgtest) needs update 
for php8.1: deprecation warnings on stderr
Added indication that 1003651 affects src:php-defaults

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

Processed: php-horde-compress: (autopkgtest) needs update for php8.1: deprecation warnings on stderr

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:php-defaults
Bug #1003652 [src:php-horde-compress] php-horde-compress: (autopkgtest) needs 
update for php8.1: deprecation warnings on stderr
Added indication that 1003652 affects src:php-defaults

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

Bug#1003651: php-horde-auth: (autopkgtest) needs update for php8.1: deprecation warnings on stderr

[Paul Gevers]

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

Dear maintainer(s),

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


   passfail
php-defaults   from testing92
php-horde-auth from testing2.2.2-8
versioned deps from testingfrom unstable
all others from testingfrom testing

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

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


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


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

Paul

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

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

PHPUnit 9.5.11 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.1.1
Configuration: 
/tmp/autopkgtest-lxc.2fo4kd22/downtmp/build.jN3/src/Horde_Auth-2.2.2/test/Horde/Auth/phpunit.xml

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.2fo4kd22/downtmp/build.jN3/src/Horde_Auth-2.2.2/test/Horde/Auth/Unit/AuthTest.php
   Class name was 'Horde_Auth_Unit_AuthTest', expected 
'AuthTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.2fo4kd22/downtmp/build.jN3/src/Horde_Auth-2.2.2/test/Horde/Auth/Unit/KolabTest.php
   Class name was 'Horde_Auth_Unit_KolabTest', expected 
'KolabTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.2fo4kd22/downtmp/build.jN3/src/Horde_Auth-2.2.2/test/Horde/Auth/Unit/PasswdTest.php
   Class name was 'Horde_Auth_Unit_PasswdTest', expected 
'PasswdTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.2fo4kd22/downtmp/build.jN3/src/Horde_Auth-2.2.2/test/Horde/Auth/Unit/Sql/Pdo/SqliteLockTest.php
   Class name was 'Horde_Auth_Unit_Sql_Pdo_SqliteLockTest', 
expected 'SqliteLockTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.2fo4kd22/downtmp/build.jN3/src/Horde_Auth-2.2.2/test/Horde/Auth/Unit/Sql/Pdo/SqliteTest.php
   Class name was 'Horde_Auth_Unit_Sql_Pdo_SqliteTest', 
expected 'SqliteTest'


PHP Deprecated: 
Return type of Horde_Support_Stub::offsetExists($offset) should either 
be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or 
the #[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in /usr/share/php/Horde/Support/Stub.php on line 111
PHP Deprecated:  Return type of Horde_Support_Stub::offsetGet($offset) 
should either be compatible with ArrayAccess::offsetGet(mixed $offset): 
mixed, or the #[\ReturnTypeWillChange] attribute should be used to 
temporarily suppress the notice in /usr/share/php/Horde/Support/Stub.php 
on line 98
PHP Deprecated:  Return type of Horde_Support_Stub::offsetSet($offset, 
$value) should either be compatible with ArrayAccess::offsetSet(mixed 
$offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute 
should be used to temporarily suppress the notice in 
/usr/share/php/Horde/Support/Stub.php on line 105
PHP Deprecated:  Return type of Horde_Support_Stub::offsetUnset($offset) 
should either be compatible with ArrayAccess::offsetUnset(mixed 
$offset): void, or the #[\ReturnTypeWillChange] attribute should be used 
to temporarily suppress the notice in 
/usr/share/php/Horde/Support/Stub.php on line 118
PHP Deprecated:  Return type of Horde_Support_Stub::count() should 
either be compatible with Countable::count(): 

Bug#1003649: php-horde-argv: (autopkgtest) needs update for php8.1: deprecation warnings on stderr

[Paul Gevers]

Source: php-horde-argv
Version: 2.1.0-7
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

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


   passfail
php-defaults   from testing92
php-horde-argv from testing2.1.0-7
versioned deps from testingfrom unstable
all others from testingfrom testing

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

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


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


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

Paul

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

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

PHPUnit 9.5.11 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.1.1
Configuration: 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/phpunit.xml


Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/BoolTest.php

   Class name was 'Horde_Argv_BoolTest', expected 'BoolTest'
Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/CallbackCheckAbbrevTest.php
   Class name was 'Horde_Argv_CallbackCheckAbbrevTest', 
expected 'CallbackCheckAbbrevTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/CallbackExtraArgsTest.php
   Class name was 'Horde_Argv_CallbackExtraArgsTest', 
expected 'CallbackExtraArgsTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/CallbackManyArgsTest.php
   Class name was 'Horde_Argv_CallbackManyArgsTest', 
expected 'CallbackManyArgsTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/CallbackMeddleArgsTest.php
   Class name was 'Horde_Argv_CallbackMeddleArgsTest', 
expected 'CallbackMeddleArgsTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/CallbackTest.php
   Class name was 'Horde_Argv_CallbackTest', expected 
'CallbackTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/CallbackVarArgsTest.php
   Class name was 'Horde_Argv_CallbackVarArgsTest', 
expected 'CallbackVarArgsTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/ChoiceTest.php
   Class name was 'Horde_Argv_ChoiceTest', expected 
'ChoiceTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/ConflictOverrideTest.php
   Class name was 'Horde_Argv_ConflictOverrideTest', 
expected 'ConflictOverrideTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.nzksfk39/downtmp/build.1D2/src/Horde_Argv-2.1.0/test/Horde/Argv/ConflictResolveTest.php
   Class name was 'Horde_Argv_ConflictResolveTest', 
expected 'ConflictResolveTest'

Warning:   Test case class not matching filename is deprecated
   in 

Processed: php-horde-argv: (autopkgtest) needs update for php8.1: deprecation warnings on stderr

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:php-defaults
Bug #1003649 [src:php-horde-argv] php-horde-argv: (autopkgtest) needs update 
for php8.1: deprecation warnings on stderr
Added indication that 1003649 affects src:php-defaults

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

Bug#1003648: php-horde-ansel: (autopkgtest) needs update for php8.1: deprecation warnings on stderr

[Paul Gevers]

Source: php-horde-ansel
Version: 3.0.10+debian1-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

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


   passfail
php-defaults   from testing92
php-horde-anselfrom testing3.0.10+debian1-2
versioned deps from testingfrom unstable
all others from testingfrom testing

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

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


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


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

Paul

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

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

PHPUnit 9.5.11 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.1.1
Configuration: 
/tmp/autopkgtest-lxc.d6lnqxiq/downtmp/build.0rr/src/ansel-3.0.10/test/Ansel/phpunit.xml


Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.d6lnqxiq/downtmp/build.0rr/src/ansel-3.0.10/test/Ansel/Unit/ImageTest.php

   Class name was 'Ansel_Unit_ImageTest', expected 'ImageTest'

PHP Deprecated:  Return type of 
Horde_Support_Stub::offsetExists($offset) should either be compatible 
with ArrayAccess::offsetExists(mixed $offset): bool, or the 
#[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in /usr/share/php/Horde/Support/Stub.php on line 111
PHP Deprecated:  Return type of Horde_Support_Stub::offsetGet($offset) 
should either be compatible with ArrayAccess::offsetGet(mixed $offset): 
mixed, or the #[\ReturnTypeWillChange] attribute should be used to 
temporarily suppress the notice in /usr/share/php/Horde/Support/Stub.php 
on line 98
PHP Deprecated:  Return type of Horde_Support_Stub::offsetSet($offset, 
$value) should either be compatible with ArrayAccess::offsetSet(mixed 
$offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute 
should be used to temporarily suppress the notice in 
/usr/share/php/Horde/Support/Stub.php on line 105
PHP Deprecated:  Return type of Horde_Support_Stub::offsetUnset($offset) 
should either be compatible with ArrayAccess::offsetUnset(mixed 
$offset): void, or the #[\ReturnTypeWillChange] attribute should be used 
to temporarily suppress the notice in 
/usr/share/php/Horde/Support/Stub.php on line 118
PHP Deprecated:  Return type of Horde_Support_Stub::count() should 
either be compatible with Countable::count(): int, or the 
#[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in /usr/share/php/Horde/Support/Stub.php on line 126
PHP Deprecated:  Return type of Horde_Support_Stub::getIterator() should 
either be compatible with IteratorAggregate::getIterator(): Traversable, 
or the #[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in /usr/share/php/Horde/Support/Stub.php on line 135
PHP Deprecated:  Return type of Horde_Prefs::offsetExists($offset) 
should either be compatible with ArrayAccess::offsetExists(mixed 
$offset): bool, or the #[\ReturnTypeWillChange] attribute should be used 
to temporarily suppress the notice in /usr/share/php/Horde/Prefs.php on 
line 530
PHP Deprecated:  Return type of Horde_Prefs::offsetGet($offset) should 
either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, 
or the #[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in /usr/share/php/Horde/Prefs.php on line 535
PHP Deprecated:  Return type of Horde_Prefs::offsetSet($offset, $value) 
should either be compatible with ArrayAccess::offsetSet(mixed $offset, 
mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be 
used to temporarily suppress the notice in 
/usr/share/php/Horde/Prefs.php on line 540
PHP Deprecated:  Return 

Processed: php-horde-ansel: (autopkgtest) needs update for php8.1: deprecation warnings on stderr

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:php-defaults
Bug #1003648 [src:php-horde-ansel] php-horde-ansel: (autopkgtest) needs update 
for php8.1: deprecation warnings on stderr
Added indication that 1003648 affects src:php-defaults

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

Bug#1003627: [Pkg-pascal-devel] Bug#1003627: fpc: autopkgtest regression on ppc64el:

[David Bannon]

I wonder if this relates to the hardening issue ?  Hardening on PPC63le
with FPC is not currently working, it makes a non viable binary.

https://gitlab.com/freepascal.org/fpc/source/-/issues/39451

Davo





On Wed, 2022-01-12 at 21:14 +0100, Paul Gevers wrote:
> Source: fpc
> Version: 3.2.2+dfsg-5
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
> 
> Dear maintainer(s),
> 
> With a recent upload of fpc the autopkgtest of fpc fails in testing
> when 
> that autopkgtest is run with the binary packages of fpc from unstable
> on 
> ppc64el. It passes when run with only packages from testing. In
> tabular 
> form:
> 
> passfail
> fpcfrom testing3.2.2+dfsg-5
> 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=fpc
> 
> https://ci.debian.net/data/autopkgtest/testing/ppc64el/f/fpc/18260761/log.gz
> 
> Total = 7734 (55:7679)
> Total number of compilations = 4753 (17:4736)
> Successfully compiled = 3605
> Successfully failed = 1131
> Compilation failures = 14
> Compilation that did not fail while they should = 3
> Total number of runs = 2981 (38:2943)
> Successful runs = 2943
> Failed runs = 38
> Number units compiled = 152
> Number program that should not be run = 468
> Number of skipped tests = 632
> Number of skipped graph tests = 10
> Number of skipped interactive tests = 31
> Number of skipped known bug tests = 7
> Number of skipped tests for other versions = 5
> Number of skipped tests for other cpus = 397
> Number of skipped tests for other targets = 182
> make: Leaving directory 
> '/tmp/autopkgtest-lxc.ims6woux/downtmp/build.IH3/src/fpcsrc/tests'
> Let's save some of the output
> Compare the new results with known results if we have them
> 
> Difference between expected failures and current failures:
> --- debian/tests/ref_fail_powerpc64-linux 2021-12-30
> 13:48:26.0 
> +
> +++ fpcsrc/tests/output/powerpc64-linux/faillist  2022-01-12 
> 08:26:51.116689429 +
> @@ -39,6 +39,7 @@
>   webtbs/tw3157
>   webtbs/tw36179
>   webtbs/tw36863
> +webtbs/tw36934a
>   webtbs/tw3930
>   webtbs/tw3964b
>   webtbs/tw4809
> 
> Checking (and fail if so) for new failures:
> Unexpected failures
> autopkgtest [08:26:51]: test run-upstream-testsuite
> 
> ___
> Pkg-pascal-devel mailing list
> pkg-pascal-de...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-pascal-devel