Processed: Bug#1027369 marked as pending in golang-github-mohae-deepcopy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1027369 [src:golang-github-mohae-deepcopy] golang-github-mohae-deepcopy: 
FTBFS in bullseye (missing build-depends on tzdata)
Added tag(s) pending.

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

Bug#1027369: marked as pending in golang-github-mohae-deepcopy

[Shengjing Zhu]

Control: tag -1 pending

Hello,

Bug #1027369 in golang-github-mohae-deepcopy 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/go-team/packages/golang-github-mohae-deepcopy/-/commit/c9bcf3e13e79fa51c6c4eef1837b63e4030e6d81


Add tzdata to Build-Depends (Closes: #1027369)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1027369

Bug#1023972: Python 3.11 for bookworm?

[Andrius Merkys]

Hello,

On 2023-01-07 10:05, Andreas Tille wrote:

Am Thu, Jan 05, 2023 at 01:57:43PM +0100 schrieb Thomas Goirand:

Please share it in this list!


#1023965 [src:pandas] pandas FTBFS with Python 3.11 as supported version
#1024031 [src:numba] numba FTBFS with Python 3.11 as supported version


If I may, I would as well be grateful if someone could give a look at:

#1023972 [src:python-ase] FTBFS with Python 3.11 due to 
pathlib.Path.__enter__() deprecation


I have no idea how to fix this and the upstream is silent.

Best,
Andrius

Processed: Re: python3-dateutil: python_dateutil get_zonefile_instance functionality is broken (no zoneinfo found)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #1003044 [python3-dateutil] python3-dateutil: python_dateutil 
get_zonefile_instance functionality is broken (no zoneinfo found)
Severity set to 'grave' from 'normal'

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

Bug#1027369: marked as done (golang-github-mohae-deepcopy: FTBFS in bullseye (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 09:08:18 +
with message-id 
and subject line Bug#1027369: fixed in golang-github-mohae-deepcopy 
0.0~git20170929.c48cc78-4
has caused the Debian Bug report #1027369,
regarding golang-github-mohae-deepcopy: FTBFS in bullseye (missing 
build-depends on tzdata)
to be marked as done.

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

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


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

Package: src:golang-github-mohae-deepcopy
Version: 0.0~git20170929.c48cc78-2
Severity: serious
Tags: ftbfs patch

Dear maintainer:

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


[...]
 debian/rules binary-indep
dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--builddirectory=_build 
-O--buildsystem=golang
   dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang
   dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang
   dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang
cd _build && go install -trimpath -v -p 2 github.com/mohae/deepcopy
internal/unsafeheader
math/bits
internal/cpu
runtime/internal/atomic
math
internal/bytealg
runtime/internal/sys
runtime/internal/math
runtime
unicode/utf8
internal/race
sync/atomic
unicode
internal/reflectlite
sync
errors
strconv
internal/oserror
syscall
reflect
time
github.com/mohae/deepcopy
   dh_auto_test -i -O--builddirectory=_build -O--buildsystem=golang
cd _build && go test -vet=off -v -p 2 github.com/mohae/deepcopy
=== RUN   TestSimple
--- PASS: TestSimple (0.00s)
=== RUN   TestMostTypes
--- PASS: TestMostTypes (0.00s)
=== RUN   TestComplexSlices
--- PASS: TestComplexSlices (0.00s)
=== RUN   TestStructA
--- PASS: TestStructA (0.00s)
=== RUN   TestUnexportedFields
--- PASS: TestUnexportedFields (0.00s)
=== RUN   TestTimeCopy
deepcopy_test.go:876: 0: unexpected error: unknown time zone 
America/New_York
deepcopy_test.go:876: 2: unexpected error: unknown time zone Europe/Prague
--- FAIL: TestTimeCopy (0.00s)
=== RUN   TestPointerToStruct
--- PASS: TestPointerToStruct (0.00s)
=== RUN   TestIssue9
--- PASS: TestIssue9 (0.00s)
=== RUN   TestInterface
--- PASS: TestInterface (0.00s)
FAIL
FAILgithub.com/mohae/deepcopy   0.004s
FAIL
dh_auto_test: error: cd _build && go test -vet=off -v -p 2 
github.com/mohae/deepcopy returned exit code 1
make: *** [debian/rules:4: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


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

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

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

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

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: golang-github-mohae-deepcopy
Source-Version: 0.0~git20170929.c48cc78-4
Done: Shengjing Zhu 

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

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

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

Debian distribution maintenance software
pp.
Shengjing Zhu  (supplier of updated 
golang-github-mohae-deepcopy 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: Sat, 07 Jan 2023 16:00:35 +0800
Source: golang-github-mohae-deepcopy
Architecture: source
Version: 0.0~git20170929.c48cc78-4
Distribution: unstable
Urge

Bug#1010244: marked as done (does not work with PHP 8.1)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 09:12:55 +
with message-id 
and subject line Bug#1010244: fixed in phpsysinfo 3.4.2-1
has caused the Debian Bug report #1010244,
regarding does not work with PHP 8.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.)


-- 
1010244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpsysinfo
Version: 3.2.5-3
Severity: grave
Tags: upstream

phpsysinfo fails with:

Fatal error: __autoload() is no longer supported, use spl_autoload_register() 
instead in /usr/share/phpsysinfo/includes/autoloader.inc.php on line 25

This has been fixed in a more recent upstream release.

-- 
ciao,
Marco


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: phpsysinfo
Source-Version: 3.4.2-1
Done: William Desportes 

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

Debian distribution maintenance software
pp.
William Desportes  (supplier of updated phpsysinfo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Jan 2023 11:08:27 +0400
Source: phpsysinfo
Built-For-Profiles: noudeb
Architecture: source
Version: 3.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: William Desportes 
Changed-By: William Desportes 
Closes: 632638 965776 1001949 1010244
Changes:
 phpsysinfo (3.4.2-1) unstable; urgency=medium
 .
   * New upstream version 3.4.2 (Closes: #632638, Closes: #1010244)
   * Add gbp.conf
   * Add GitLab Salsa CI config
   * Bump debhelper from old 5 to 13 (Closes: #965776)
   * Refresh d/rules and depend on pkg-php-tools
   * Refresh d/watch
   * Enable pristine-tar
   * Add Vcs-* and Rules-Requires-Root to d/control
   * Set myself as a Maintainer and PHP PEAR team as Uploaders
   * Remove Suggests hddtemp (Closes: #1001949)
   * Replace old cdbs d/rules override to use override_dh_fixperms
   * Re-work the Depends section
   * Fix d/conffile to /etc/phpsysinfo/phpsysinfo.ini
   * Drop not used depends on libjs-jquery (Ref: #1021030)
   * Remove link for /usr/share/phpsysinfo/phpsysinfo.ini
   * Add a patch to change the config path
   * Add autopkgtests
Checksums-Sha1:
 1778209fcf855757f7a9082ffa961eb6f5496e9f 2088 phpsysinfo_3.4.2-1.dsc
 925ce889e3dcbfce39754177dee188d83780809b 1018093 phpsysinfo_3.4.2.orig.tar.gz
 4092217ebebae4b3e0984e7e82d637c248f1d107 24220 phpsysinfo_3.4.2-1.debian.tar.xz
 ae7de5f968c849d33e0391522f661f43feb2f3d4 50976 
phpsysinfo_3.4.2-1_source.buildinfo
Checksums-Sha256:
 a30a630a5c8a47acc0b899ce6b1359d62432ed7105b5e07c4231c86f7904af6d 2088 
phpsysinfo_3.4.2-1.dsc
 133d4591688abbb93272d0858b8833379ada1eb9b8ffd9878a7b82448cf3f0ed 1018093 
phpsysinfo_3.4.2.orig.tar.gz
 1d73b254d63963cef1b4db27babe73eff3901fbb30c3ba1945c96462193f960b 24220 
phpsysinfo_3.4.2-1.debian.tar.xz
 4b23a1789ebd1c300e27c89d03c96fb478d868b36703a6e3d1ade19c5730bf03 50976 
phpsysinfo_3.4.2-1_source.buildinfo
Files:
 9b572907c5874d264a144b497c8dcc03 2088 web optional phpsysinfo_3.4.2-1.dsc
 05f0c1a60ce4c85287c77d7b54f4c3f4 1018093 web optional 
phpsysinfo_3.4.2.orig.tar.gz
 b4e7140dcf7f9be1f6a8c65e96a8b90e 24220 web optional 
phpsysinfo_3.4.2-1.debian.tar.xz
 23a5af3a6c41724b461c55b8d73a6b91 50976 web optional 
phpsysinfo_3.4.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEExNkf3872tKPGU/14kKDvG4JRqIkFAmO5IHQACgkQkKDvG4JR
qIlzEQ//R6b9MrPx40fc+zzsJ3E2XBd3HNogHEsNyQtjyCRt26SBonXnTiB1qsm1
WzZ6boKlMQ+/dmyuwXGAQyAG3UBL2hRyfIgW3iWOQwmsKSkQBwhkR8pk7IOnQOQX
JKk+AteIjlHIr0IgsRZdiRWKKIW1S/KDLSrIDpoVUezqeNUgjPg5nTu2VccNxTdH
GiLFITkt9Y9WceffqLpc0sXP/Tu++/XO/L2Tah+z13CZ1pcw3nfrsKoH2hKSRcCB
0Z7pVs6iDYSByz+8fo3zHCmKuWKKl0SdfVXyPfYg0siMsRb42QArdvvKP4barjB7
FLnHfG42JPQ8dEhSS7QgU8G5IKirEqtZ6pAmsgLyf0vKyqWHuMua3CIHeG4trdcx
TAmp2xANsBrGUz9VkhzhHeIiqO0TGi2aBpB849PUxeoQFCI34Netwnmvbw9ZSMl9
08KRA8m6UZtS1kHWGLi5IIxPj+Np7TU5ISNw/F3vBEYGML2YMczVZ+oZLhWH7/TZ
E3M0QRqkNPy/M+SJd4f+LMS+AUNDR1V3aMfaOUf2qMI5wuxMVzBTDFnQ45RmRzdX
NhBkHyGlP/jt6q7LtEc7YW2sNTVDeEQUyfIT89d3XL+jp+tiuxJ69Y/m+ei0rniG
oE59lu

Bug#965776: marked as done (phpsysinfo: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 09:12:55 +
with message-id 
and subject line Bug#965776: fixed in phpsysinfo 3.4.2-1
has caused the Debian Bug report #965776,
regarding phpsysinfo: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: phpsysinfo
Version: 3.2.5-3
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package phpsysinfo uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

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

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


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

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: phpsysinfo
Source-Version: 3.4.2-1
Done: William Desportes 

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

Debian distribution maintenance software
pp.
William Desportes  (supplier of updated phpsysinfo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Jan 2023 11:08:27 +0400
Source: phpsysinfo
Built-For-Profiles: noudeb
Architecture: source
Version: 3.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: William Desportes 
Changed-By: William Desportes 
Closes: 632638 965776 1001949 1010244
Changes:
 phpsysinfo (3.4.2-1) unstable; urgency=medium
 .
   * New upstream version 3.4.2 (Closes: #632638, Closes: #1010244)
   * Add gbp.conf
   * Add GitLab Salsa CI config
   * Bump debhelper from old 5 to 13 (Closes: #965776)
   * Refresh d/rules and depend on pkg-php-tools
   * Refresh d/watch
   * Enable pristine-tar
   * Add Vcs-* and Rules-Requires-Root to d/control
   * Set myself as a Maintainer and PHP PEAR team as Uploaders
   * Remove Suggests hddtemp (Closes: #1001949)
   * Replace old cdbs d/rules override to use override_dh_fixperms
   * Re-work the Depends section
   * Fix d/conffile to /etc/phpsysinfo/phpsysinfo.ini
   * Drop not used depends on libjs-jquery (Ref: #1021030)
   * Remove link for /usr/share/phpsysinfo/phpsysinfo.ini
   * Add a patch to change the config path
   * Add autopkgtests
Checksums-Sha1:
 1778209fcf855757f7a9082ffa961eb6f5496e9f 2088 phpsysinfo_3.4.2-1.dsc
 925ce889e3dcbfce39754177dee188d83780809b 1018093 phpsysinfo_3.4.2.orig.tar.gz
 4092217ebebae4b3e0984e7e82d637c248f1d107 24220 phpsysinfo_3.4.2-1.debian.tar.xz
 ae7de5f968c849d33e0391522f661f43feb2f3d4 50976 
phpsysinfo_3.4.2-1_source.buildinfo
Checksums-Sha256:
 a30a630a5c8a47acc0b899ce6b1359d62432ed7105b5e07c4231c86f7904af6d 2088 
phpsysinfo_3.4.2-1.dsc
 133d4591688abbb93272d0858b8833379ada1eb9b8ffd9878a7b82448cf3f0ed 1018093 
phpsysinfo_3.4.2.orig.tar.gz
 1d73b254d63963cef1b4db27babe73eff3901fbb30c3ba1945c96462193f960b 24220 
phpsysinfo_3.4.2-1.debian.tar.xz
 4b23a1789ebd1c300e27c89d03c96fb478d868b36703a6e3d1ade19c5730bf03 50976 
phpsysinfo_3.4.2-1_source.buildinfo
Files:
 9b572907c5874d264a144b497c8dcc03 2088 web optional phpsysinfo_3.4.2-1.dsc
 05f0c1a60ce4c85287c77d7b54f4c3f4 1018093 web optional 
phpsysinfo_3.4.2.orig.tar.gz
 b4e7140dcf7f9be1f6a8c65e96a8b90e 24220 web optional 
phpsysinfo_3.4.2-1.debian.

Bug#1026643: marked as pending in astunparse

[Carsten Schoenert]

Control: tag -1 pending

Hello,

Bug #1026643 in astunparse 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/astunparse/-/commit/c1b04ef5a7908b68288915d75a4d733c61843bc7


Rebuild patch queue from patch-queue branch

Added patch:
tests-Skip-test_files-on-on-Python-3.10.patch

Closes: #1026643


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026643

Processed: Bug#1026643 marked as pending in astunparse

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026643 {Done: Carsten Schoenert } 
[src:astunparse] astunparse: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
Added tag(s) pending.

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

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

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 09:34:32 +
with message-id 
and subject line Bug#1026643: fixed in astunparse 1.6.3-2
has caused the Debian Bug report #1026643,
regarding astunparse: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p "3.11 3.10" 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.)


-- 
1026643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astunparse
Version: 1.6.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 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 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> running config
> I: pybuild base:240: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_astunparse/build/astunparse
> copying lib/astunparse/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_astunparse/build/astunparse
> copying lib/astunparse/unparser.py -> 
> /<>/.pybuild/cpython3_3.11_astunparse/build/astunparse
> copying lib/astunparse/__main__.py -> 
> /<>/.pybuild/cpython3_3.11_astunparse/build/astunparse
> copying lib/astunparse/printer.py -> 
> /<>/.pybuild/cpython3_3.11_astunparse/build/astunparse
> running egg_info
> creating lib/astunparse.egg-info
> writing lib/astunparse.egg-info/PKG-INFO
> writing dependency_links to lib/astunparse.egg-info/dependency_links.txt
> writing requirements to lib/astunparse.egg-info/requires.txt
> writing top-level names to lib/astunparse.egg-info/top_level.txt
> writing manifest file 'lib/astunparse.egg-info/SOURCES.txt'
> reading manifest file 'lib/astunparse.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> adding license file 'AUTHORS.rst'
> writing manifest file 'lib/astunparse.egg-info/SOURCES.txt'
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_astunparse/build/astunparse
> copying lib/astunparse/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_astunparse/build/astunparse
> copying lib/astunparse/unparser.py -> 
> /<>/.pybuild/cpython3_3.10_astunparse/build/astunparse
> copying lib/astunparse/__main__.py -> 
> /<>/.pybuild/cpython3_3.10_astunparse/build/astunparse
> copying lib/astunparse/printer.py -> 
> /<>/.pybuild/cpython3_3.10_astunparse/build/astunparse
> running egg_info
> writing lib/astunparse.egg-info/PKG-INFO
> writing dependency_links to lib/astunparse.egg-info/dependency_links.txt
> writing requirements to lib/astunparse.egg-info/requires.txt
> writing top-level names to lib/astunparse.egg-info/top_level.txt
> reading manifest file 'lib/astunparse.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> adding license file 'AUTHORS.rst'
> writing manifest file 'lib/astunparse.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd 
> /<>/.pybuild/cpython3_3.11_astunparse/build; python3.11 -m 
> pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
> rootdir: /<>
> collected 94 items
> 
> tests/test_dump.py s.s.s..s...   [ 
> 50%]
> tests/test_unparse.py .F..s.s.s..s...
> [100%]
> 
> === FAILURES 
> ===
> __ UnparseTestCase.test_files 
> __
> 
> self = 
> 
> def test_files(self):
> names = []
> for test_dir in self.test_directories:
> for n in os.listdir(test_dir):
> if n.endswith('.py') and not n.startswith('bad'):
> names.append(os.path.join(test_dir, n))
> 
> for filename in names:
> print('Testing %s' % filename)
> source = read_pyfile(filename)
> >   self.check_roundtrip(source)
> 
> tests/common.py:192: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Bug#1026665: marked as pending in doxia-sitetools

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/doxia-sitetools/-/commit/a55fc0f4a22c90cfaa4d5084dc40a44213ee47ae


Explicit dependency on libeclipse-sisu-maven-plugin-java (Closes: #1026665)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026665

Processed: Bug#1026665 marked as pending in doxia-sitetools

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026665 [src:doxia-sitetools] doxia-sitetools: FTBFS: make: *** 
[debian/rules:4: build] Error 25
Added tag(s) pending.

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

Bug#1026665: marked as done (doxia-sitetools: FTBFS: make: *** [debian/rules:4: build] Error 25)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 10:05:04 +
with message-id 
and subject line Bug#1026665: fixed in doxia-sitetools 1.11.1-1
has caused the Debian Bug report #1026665,
regarding doxia-sitetools: FTBFS: make: *** [debian/rules:4: build] Error 25
to be marked as done.

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

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


-- 
1026665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: doxia-sitetools
Version: 1.7.5-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibdoxia-sitetools-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Doxia Sitetools
> [pom]
> [INFO] Doxia Sitetools :: Decoration Model
> [jar]
> [INFO] Doxia Sitetools :: Skin Model  
> [jar]
> [INFO] Doxia Sitetools :: Integration Tools   
> [jar]
> [INFO] Doxia Sitetools :: Site Renderer   
> [jar]
> [INFO] Doxia Sitetools :: Document Renderer   
> [jar]
> [INFO] 
> 
> [INFO] Reactor Summary for Doxia Sitetools 1.7.5:
> [INFO] 
> [INFO] Doxia Sitetools  SKIPPED
> [INFO] Doxia Sitetools :: Decoration Model  SKIPPED
> [INFO] Doxia Sitetools :: Skin Model .. SKIPPED
> [INFO] Doxia Sitetools :: Integration Tools ... SKIPPED
> [INFO] Doxia Sitetools :: Site Renderer ... SKIPPED
> [INFO] Doxia Sitetools :: Document Renderer ... SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  0.182 s
> [INFO] Finished at: 2022-12-20T09:39:05Z
> [INFO] 
> 
> [ERROR] Error resolving version for plugin 
> 'org.eclipse.sisu:sisu-maven-plugin' from the repositories [local 
> (/<>/debian/maven-repo), central 
> (https://repo.maven.apache.org/maven2)]: Plugin not found in any plugin 
> repository -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginVersionResolutionException
> dh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify 
> -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US 
> returned exit code 1
> make: *** [debian/rules:4: build] Error 25


The full build log is available from:
http://q

Bug#1027377: marked as done (miller: FTBFS in bullseye (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 10:23:15 +
with message-id 
and subject line Bug#1027377: fixed in miller 6.6.0-2
has caused the Debian Bug report #1027377,
regarding miller: FTBFS in bullseye (missing build-depends on tzdata)
to be marked as done.

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

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


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

Package: src:miller
Version: 5.10.0-1
Severity: serious
Tags: ftbfs patch

Dear maintainer:

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


[...]
 debian/rules binary-arch
dh binary-arch
   dh_update_autotools_config -a
   dh_autoreconf -a

[...]


Differences between ./expected/out and 
/<>/c/reg_test/output-regtest/out:
*** ./expected/out  2020-11-29 20:56:56.0 +
--- /<>/c/reg_test/output-regtest/out  2022-07-15 
11:48:14.641689838 +
***
*** 24879,24942 
  
  DSL LOCAL DATE/TIME FUNCTIONS
  
  mlr --opprint put $b=localtime2sec($a); $c=sec2localtime($b); $d=sec2localdate($b)

  a   b c   d
! 2017-02-18 23:00:00 1487469600.00 2017-02-18 23:00:00 2017-02-18
! 2017-02-18 23:59:59 1487473199.00 2017-02-18 23:59:59 2017-02-18
! 2017-02-19 00:00:00 1487473200.00 2017-02-19 00:00:00 2017-02-19
! 2017-02-19 00:30:00 1487475000.00 2017-02-19 00:30:00 2017-02-19
! 2017-02-19 01:00:00 1487476800.00 2017-02-19 01:00:00 2017-02-19
! 2017-10-14 23:00:00 1508032800.00 2017-10-14 23:00:00 2017-10-14
! 2017-10-14 23:59:59 1508036399.00 2017-10-14 23:59:59 2017-10-14
! 2017-10-15 00:00:00 1508036400.00 2017-10-15 01:00:00 2017-10-15
! 2017-10-15 00:30:00 1508038200.00 2017-10-15 01:30:00 2017-10-15
! 2017-10-15 01:00:00 150804.00 2017-10-15 02:00:00 2017-10-15
  
  mlr --opprint put $b=localtime2sec($a); $c=sec2localtime($b); $d=sec2localdate($b)

  a   b c   d
! 2017-02-14 00:00:00 1487041200.00 2017-02-14 01:00:00 2017-02-14
! 2017-02-15 00:00:00 1487127600.00 2017-02-15 01:00:00 2017-02-15
! 2017-02-16 00:00:00 1487214000.00 2017-02-16 01:00:00 2017-02-16
! 2017-02-17 00:00:00 1487300400.00 2017-02-17 01:00:00 2017-02-17
! 2017-02-18 00:00:00 1487386800.00 2017-02-18 01:00:00 2017-02-18
! 2017-02-19 00:00:00 1487473200.00 2017-02-19 00:00:00 2017-02-19
! 2017-02-20 00:00:00 1487559600.00 2017-02-20 00:00:00 2017-02-20
! 2017-10-12 00:00:00 150200.00 2017-10-12 00:00:00 2017-10-12
! 2017-10-13 00:00:00 1507863600.00 2017-10-13 00:00:00 2017-10-13
! 2017-10-14 00:00:00 150795.00 2017-10-14 00:00:00 2017-10-14
! 2017-10-15 00:00:00 1508036400.00 2017-10-15 01:00:00 2017-10-15
! 2017-10-16 00:00:00 1508122800.00 2017-10-16 01:00:00 2017-10-16
! 2017-10-17 00:00:00 1508209200.00 2017-10-17 01:00:00 2017-10-17
! 2017-10-18 00:00:00 1508295600.00 2017-10-18 01:00:00 2017-10-18
! 2017-10-19 00:00:00 1508382000.00 2017-10-19 01:00:00 2017-10-19
  
  mlr --opprint put $b=strptime_local($a, "%Y-%m-%d %H:%M:%S"); $c=strftime_local($b, "%Y-%m-%d %H:%M:%S")

  a   b c
! 2017-02-18 23:00:00 1487469600.00 2017-02-18 23:00:00
! 2017-02-18 23:59:59 1487473199.00 2017-02-18 23:59:59
! 2017-02-19 00:00:00 1487473200.00 2017-02-19 00:00:00
! 2017-02-19 00:30:00 1487475000.00 2017-02-19 00:30:00
! 2017-02-19 01:00:00 1487476800.00 2017-02-19 01:00:00
! 2017-10-14 23:00:00 1508032800.00 2017-10-14 23:00:00
! 2017-10-14 23:59:59 1508036399.00 2017-10-14 23:59:59
! 2017-10-15 00:00:00 1508036400.00 2017-10-15 01:00:00
! 2017-10-15 00:30:00 1508038200.00 2017-10-15 01:30:00
! 2017-10-15 01:00:00 150804.00 2017-10-15 02:00:00
  
  mlr --opprint put $b=strptime_local($a, "%Y-%m-%d %H:%M:%S"); $c=strftime_local($b, "%Y-%m-%d %H:%M:%S")

  a   b c
! 2017-02-18 23:00:00 1487469600.00 2017-02-18 23:00:00
! 2017-02-18 23:59:59 1487473199.00 2017-02-18 23:59:59
! 2017-02-19 00:00:00 1487473200.00 2017-02-19 00:00:00
! 2017-02-19 00:30:00 1487475000.00 2017-02-19 00:30:00
! 2017-02-19 01:00:00 1487476800.00 2017-02-19 01:00:00
! 2017-10-14 23:00:00 1508032800.00 2017-10-14 23:00:00
! 2017-10-14 23:59:59 1508036399.00 2017-10-14 23:59:

Bug#1028122: sortmerna: FTBFS on i386

[Sebastian Ramacher]

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

https://buildd.debian.org/status/fetch.php?pkg=sortmerna&arch=i386&ver=4.3.6-1&stamp=1673038926&raw=0

cd /<>/obj-i686-linux-gnu/src/sortmerna && /usr/bin/cc  
-I/<>/include -I/<>/3rdparty/cmph 
-I/<>/3rdparty/concurrentqueue -I/<>/3rdparty/alp -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT 
src/sortmerna/CMakeFiles/smr_objs.dir/ssw.c.o -MF 
CMakeFiles/smr_objs.dir/ssw.c.o.d -o CMakeFiles/smr_objs.dir/ssw.c.o -c 
/<>/src/sortmerna/ssw.c
/<>/src/sortmerna/ssw.c: In function ‘sw_sse2_byte’:
/<>/src/sortmerna/ssw.c:177:17: warning: SSE vector return without 
SSE enabled changes the ABI [-Wpsabi]
  177 | __m128i vZero = _mm_set1_epi32(0);
  | ^
In file included from /<>/src/sortmerna/ssw.c:49:
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:654:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_set1_epi8’: target specific option 
mismatch
  654 | _mm_set1_epi8 (char __A)
  | ^
/<>/src/sortmerna/ssw.c:192:25: note: called from here
  192 | __m128i vBias = _mm_set1_epi8(bias);
  | ^~~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:654:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_set1_epi8’: target specific option 
mismatch
  654 | _mm_set1_epi8 (char __A)
  | ^
/<>/src/sortmerna/ssw.c:189:25: note: called from here
  189 | __m128i vGapE = _mm_set1_epi8(weight_gapE);
  | ^~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:654:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_set1_epi8’: target specific option 
mismatch
  654 | _mm_set1_epi8 (char __A)
  | ^
/<>/src/sortmerna/ssw.c:186:25: note: called from here
  186 | __m128i vGapO = _mm_set1_epi8(weight_gapO);
  | ^~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:642:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_set1_epi32’: target specific option 
mismatch
  642 | _mm_set1_epi32 (int __A)
  | ^~
/<>/src/sortmerna/ssw.c:177:25: note: called from here
  177 | __m128i vZero = _mm_set1_epi32(0);
  | ^
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:1227:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_slli_si128’: target specific option 
mismatch
 1227 | _mm_slli_si128 (__m128i __A, const int __N)
  | ^~
/<>/src/sortmerna/ssw.c:217:22: note: called from here
  217 | vH = _mm_slli_si128(vH, 1); /* Shift the 128-bit value 
in vH left by 1 byte. */
  |  ^
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:695:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_load_si128’: target specific option 
mismatch
  695 | _mm_load_si128 (__m128i const *__P)
  | ^~
/<>/src/sortmerna/ssw.c:259:30: note: called from here
  259 | vH = _mm_load_si128(pvHLoad + j);
  |  ^~~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:1413:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_max_epu8’: target specific option 
mismatch
 1413 | _mm_max_epu8 (__m128i __A, __m128i __B)
  | ^~~~
/<>/src/sortmerna/ssw.c:256:30: note: called from here
  256 | vF = _mm_max_epu8(vF, vH);
  |  ^~~~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:1136:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_subs_epu8’: target specific option 
mismatch
 1136 | _mm_subs_epu8 (__m128i __A, __m128i __B)
  | ^
/<>/src/sortmerna/ssw.c:255:30: note: called from here
  255 | vF = _mm_subs_epu8(vF, vGapE);
  |  ^~~~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:731:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_store_si128’: target specific option 
mismatch
  731 | _mm_store_si128 (__m128i *__P, __m128i __B)
  | ^~~
/<>/src/sortmerna/ssw.c:252:25: note: called from here
  252 | _mm_store_si128(pvE + j, e);
  | ^~~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:1413:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_max_epu8’: target specific option 
mismatch
 1413 | _mm_max_epu8 (__m128i __A, __m128i __B)
  | ^~~~
/<>/src/sortmerna/ssw.c:251:29: note: called from here
  251 | e = _mm_max_epu8(e, vH);
  | ^~~
/usr/lib/gcc/i686-linux-gnu/12/includ

Bug#1028108: marked as pending in python-cooler

[Étienne Mollier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/python-cooler/-/commit/92995f567ee4f2ce40f70885a88519e4ac3c68f3


d/rules: build tests.tar.xz only on arch=all builds.

Also ventilate a bit the scripting to build that archive to make the
whole rule a bit easier to read.

Closes: #1028108


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028108

Processed: Bug#1028108 marked as pending in python-cooler

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028108 [src:python-cooler] python-cooler: binary-any FTBFS
Added tag(s) pending.

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

Bug#1023972: Python 3.11 for bookworm?

[Simon McVittie]

On Sat, 07 Jan 2023 at 10:23:19 +0200, Andrius Merkys wrote:
> If I may, I would as well be grateful if someone could give a look at:
> 
> #1023972 [src:python-ase] FTBFS with Python 3.11 due to
> pathlib.Path.__enter__() deprecation
> 
> I have no idea how to fix this and the upstream is silent.

My first thought on seeing this was: why were Path objects a context
manager in the first place? What would that mean?

Looking at the code in python3.10 and python3.11 pathlib, it seems the
reason this is deprecated is indeed that it didn't make sense:

def __enter__(self):
# In previous versions of pathlib, __exit__() marked this path as
# closed; subsequent attempts to perform I/O would raise an IOError.
# This functionality was never documented, and had the effect of
# making Path objects mutable, contrary to PEP 428.
# In Python 3.9 __exit__() was made a no-op.
# In Python 3.11 __enter__() began emitting DeprecationWarning.
# In Python 3.13 __enter__() and __exit__() should be removed.
warnings.warn("pathlib.Path.__enter__() is deprecated and scheduled "
  "for removal in Python 3.13; Path objects as a context "
  "manager is a no-op",
  DeprecationWarning, stacklevel=2)
return self

def __exit__(self, t, v, tb):
pass

So the solution seems to be that if your package contains this:

with some_path_object:
do_stuff(some_path_object)

replace it with:

do_stuff(some_path_object)

and if it contains:

with Path(...) as my_path:
do_stuff(my_path)

replace with:

my_path = Path(...)
do_stuff(my_path)

I hope that should be a relatively straightforward change.

smcv

Processed: limit source to secnet, tagging 1028102

[Debian Bug Tracking System]

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

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

> tags 1028102 + pending
Bug #1028102 [src:secnet] secnet FTBFS: eax-aes-test failure
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1026719: [Pkg-pascal-devel] Bug#1026719: Bug#1026719: vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory

[Abou Al Montacir]

control: reassign -1
control: reopen 967348

On Fri, 2023-01-06 at 13:59 +0100, Abou Al Montacir wrote:
> I do agree.
> I'll revert it.
Done
--
Cheers,
Abou Al Montacir



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

Bug#1026719: [Pkg-pascal-devel] Bug#1026719: Bug#1026719: vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory

[Abou Al Montacir]

control: reassign -1 fpc
control: reopen 967348

On Fri, 2023-01-06 at 13:59 +0100, Abou Al Montacir wrote:
> I do agree.
> I'll revert it.
> Done
--
Cheers,
Abou Al Montacir


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

Processed (with 1 error): Re: [Pkg-pascal-devel] Bug#1026719: Bug#1026719: vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 fpc
Bug #1026719 [lazarus] vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No 
such file or directory
Bug reassigned from package 'lazarus' to 'fpc'.
Ignoring request to alter found versions of bug #1026719 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1026719 to the same values 
previously set
> reopen 967348
Failed to reopen 967348: Not altering archived bugs; see unarchive.


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

Bug#1004154: Fwd: Bug#1004154: xserver-xorg-video-qxl: XOrg frequently crashes when using qxl driver: qxl(0): error doing QXL_ALLOC

[Bernhard Übelacker]

Forwarding, as the email from TJ possibly did not reach Felix.


On Fri, 21 Oct 2022 11:43:07 +0100 TJ  wrote:

On Sat, 12 Feb 2022 08:21:55 + Felix Leimbach  wrote:
> I noticed that vgamem_mb was still low (32 MB).
> So I changed to this (slightly wasteful) command-line and am now running the 
latest kernel (5.15.0-3-amd64):
> 
> -vga none -device qxl-vga,ram_size_mb=256,vgamem_mb=256,vram_size_mb=256,vram64_size_mb=256,max_outputs=1
> 
> Will report back if that helps.


Did the vgamem_mb change fix the issue?

This bug is currently keeping the package out of bookworm and, if it was 
a user-specific issue, ought to be closed and the package reintroduced 
to bookworm.


I'm currently doing a full-upgrade bullseye to bookworm and this removal 
is a blocker for VMs.

Bug#1026719: marked as done (vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 13:28:32 +
with message-id 
and subject line Bug#1026719: fixed in fpc 3.2.2+dfsg-18
has caused the Debian Bug report #1026719,
regarding vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or 
directory
to be marked as done.

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

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


-- 
1026719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vmg
Version: 3.7.1-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> /usr/bin/i686-w64-mingw32-windres fpcmagnifier.rc fpcmagnifier.res
> /usr/bin/i686-w64-mingw32-windres magnifier.rc magnifier.res
> lazres startform.lrs startform.lfm
> startform.lfm ResourceName='TvStartWindow' Type='FORMDATA'
> fpc -S2cgi -O1 -gl -vewnhi -l \
>   -Fu/usr/lib/lazarus/default/lcl/units/x86_64-linux/ \
>   -Fu/usr/lib/lazarus/default/lcl/units/x86_64-linux/gtk2/ \
>   -Fu/usr/lib/lazarus/default/packager/units/x86_64-linux/ \
>   -Fu/usr/lib/lazarus/default/components/lazutils/lib/x86_64-linux/ \
>   -Fu. -o./vmg -dLCL -dLCLgtk2 magnifier.dpr
> Hint: Start of reading config file /etc/fpc.cfg
> Hint: End of reading config file /etc/fpc.cfg
> Free Pascal Compiler version 3.2.2+dfsg-17 [2022/11/27] for x86_64
> Copyright (c) 1993-2021 by Florian Klaempfl and others
> Target OS: Linux for x86-64
> Compiling magnifier.dpr
> Compiling glass.pas
> Compiling constants.pas
> Compiling appsettings.pas
> Compiling translationsvmg.pas
> appsettings.pas(70,28) Hint: Parameter "Sender" not used
> appsettings.pas(71,20) Hint: Parameter "Sender" not used
> appsettings.pas(248,3) Note: Local variable "APath" not used
> appsettings.pas(249,3) Note: Local variable "LocalConfigFile" not used
> appsettings.pas(250,3) Note: Local variable "attrs" not used
> glass.pas(205,3) Note: Local variable "buffer" not used
> glass.pas(206,3) Note: Local variable "memstream" not used
> glass.pas(483,3) Note: Local variable "c" not used
> glass.pas(484,3) Note: Local variable "srcRect" not used
> glass.pas(484,12) Note: Local variable "destRect" not used
> glass.pas(486,3) Note: Local variable "lCurWindow" not used
> glass.pas(486,15) Note: Local variable "lVMGWindow" not used
> glass.pas(487,3) Note: Local variable "lCurWindowText" not used
> glass.pas(488,3) Note: Local variable "i" not used
> glass.pas(490,3) Note: Local variable "bmpRetinaDisplay" not used
> glass.pas(93,33) Hint: Parameter "DestCanvas" not used
> glass.pas(658,3) Note: Local variable "dwROP" is assigned but never used
> glass.pas(770,3) Note: Local variable "i" not used
> glass.pas(770,6) Note: Local variable "MinWidth" not used
> glass.pas(770,16) Note: Local variable "MinHeight" not used
> glass.pas(775,9) Note: Local variable "stepMinor" is assigned but never used
> glass.pas(775,20) Note: Local variable "tickSize" is assigned but never used
> glass.pas(775,30) Note: Local variable "tickCount" not used
> glass.pas(916,3) Note: Local variable "I" not used
> glass.pas(986,47) Hint: Local variable "DrawInfo" does not seem to be 
> initialized
> glass.pas(112,31) Hint: Parameter "DC" not used
> Compiling app.pas
> Compiling plugins.pas
> Compiling plugininfo.pas
> app.pas(113,15) Warning: An inherited method is hidden by "ShowHelp(TObject);"
> Compiling about.pas
> about.pas(63,24) Hint: Parameter "Sender" not used
> Compiling configdlg.pas
> configdlg.pas(62,24) Hint: Parameter "Sender" not used
> configdlg.pas(63,25) Hint: Parameter "Sender" not used
> configdlg.pas(63,46) Hint: Parameter "Action" not used
> configdlg.pas(35,54) Hint: Unit "constants" not used in configdlg
> configdlg.pas(77,3) Hint: Unit "glass" not used in configdlg
> app.pas(106,26) Hint: Parameter "Sender" not used
> app.pas(94,27) Hint: Parameter "Sender" not used
> app.pas(184,3) Note: Local variable "lResult" not used
> app.pas(521,3) Note: Local variable "OSVersion" not used
> app.pas(123,38) Hint: Parameter "Sender" not used
> app.pas(124,32) Hint: Parameter "AID" not used
> app.pas(108,25) Hint: Parameter "Sender" not used
> app.pas(108,42) Hint: Parameter "Shift" not used
> app.pas(108,62) Hint: Parameter "X" not used
> app.pas(108,65) Hint: Parameter "Y" not used
> app.pas(109,30) Hint: Parameter "uID" not used
> app.pas(114,28) Hint: Parameter "Sender" not used
> app.pas(115,36) Hint: Parameter "Sender" not used
> app.pas(107,24) Hint: P

Bug#997152: marked as done (gom: FTBFS: gom_iface_t.c:118:9: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 13:31:31 +
with message-id 
and subject line Bug#997152: fixed in gom 0.30.4-1
has caused the Debian Bug report #997152,
regarding gom: FTBFS: gom_iface_t.c:118:9: error: format not a string literal 
and no format arguments [-Werror=format-security]
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.)


-- 
997152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gom
Version: 0.30.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o gom.o gom.c
> gom_iface_t.c: In function ‘gom_iface_t_cntrprintw’:
> gom_iface_t.c:118:9: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   118 | mvprintw(line, (COLS - strlen(str)) / 2, str);
>   | ^~~~
> gom_iface_t.c: In function ‘gom_iface_t_info’:
> gom_iface_t.c:160:52: warning: zero-length gnu_printf format string 
> [-Wformat-zero-length]
>   160 | mvprintw(gom_iface_t_info_line, 0, "");
>   |^~
> gom_iface_t.c:166:52: warning: zero-length gnu_printf format string 
> [-Wformat-zero-length]
>   166 | mvprintw(GOM_IFACE_T_INFO_LINE, 0, "");
>   |^~
> gom_iface_t.c:168:9: warning: ‘vwprintw’ is deprecated 
> [-Wdeprecated-declarations]
>   168 | vwprintw(stdscr, fmt, vargs);
>   | ^~~~
> In file included from gom_iface_t.c:30:
> /usr/include/curses.h:812:28: note: declared here
>   812 | extern NCURSES_EXPORT(int) vwprintw (WINDOW *, const char *, va_list) 
> GCC_DEPRECATED(use vw_printw) /* implemented */
>   |^~~~
> gom_iface_t.c: In function ‘gom_iface_t_get_option_arg’:
> gom_iface_t.c:191:17: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   191 | mvprintw(GOM_IFACE_T_INFO_LINE, 0, prompt);
>   | ^~~~
> gom_iface_t.c: In function ‘gom_iface_t_draw_sline’:
> gom_iface_t.c:285:24: warning: too many arguments for format 
> [-Wformat-extra-args]
>   285 | printw("   |", gom_driver_c_c_len(c) >= 2 ? 
> gom_mixer_c_l(c) ? '+' : '-' : 'x');
>   |^~
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:490: gom_iface_t.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/gom_0.30.3-1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: gom
Source-Version: 0.30.4-1
Done: Stephan Sürken 

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

Debian distribution maintenance software
pp.
Stephan Sürken  (supplier of updated gom package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Jan 2023 12:41:35 +0100
Source: gom
Architecture: source
Version: 0.30.4-1
Distribution: unstable
Urgency: medium
Maintainer: Stephan Sürken 
Changed-By: Stephan Sürken 
Closes: 997152
Changes:
 gom (0.30.4-1) unstable; urgency=medium
 .
   * [81228ae] New upstream version 0.30.4 (Bug fix: "FTBFS:
 gom_iface_t.c:118:9: error: format not a string literal and no format
 arguments [-Werror=format-security]", thanks to Lucas

Bug#1028108: marked as done (python-cooler: binary-any FTBFS)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 13:49:02 +
with message-id 
and subject line Bug#1028108: fixed in python-cooler 0.8.11-6
has caused the Debian Bug report #1028108,
regarding python-cooler: binary-any FTBFS
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.)


-- 
1028108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cooler
Version: 0.8.11-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-cooler&ver=0.8.11-5

...
   debian/rules override_dh_installexamples
make[1]: Entering directory '/<>'
dh_installexamples
cd debian/python3-cooler-examples/usr/share/doc/python3-cooler && tar --create 
--owner=0 --group=0 --numeric-owner --sort=name --mtime="@1672342132" 
--mode=u=wrX,og=rX --file tests.tar.xz tests && rm -rf tests
/bin/sh: 1: cd: can't cd to 
debian/python3-cooler-examples/usr/share/doc/python3-cooler
make[1]: *** [debian/rules:12: override_dh_installexamples] Error 2
--- End Message ---
--- Begin Message ---
Source: python-cooler
Source-Version: 0.8.11-6
Done: Étienne Mollier 

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

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

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated python-cooler 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Jan 2023 12:09:31 +0100
Source: python-cooler
Architecture: source
Version: 0.8.11-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1028108
Changes:
 python-cooler (0.8.11-6) unstable; urgency=medium
 .
   * Team upload.
   * d/rules: build tests.tar.xz only on arch=all builds. (Closes: #1028108)
   * d/rules: fix broken .xz archive.
   * skip-http-connection.patch: add; skip tests needing Internet.
   * d/copyright: update copyright year.
   * d/t/control: only test on supported architectures.
Checksums-Sha1:
 5aca504acd2e41763b3e07ac8a5987b98227e34c 2716 python-cooler_0.8.11-6.dsc
 da16ff029f1b63df744ef8bff5669d9a1325b527 6788 
python-cooler_0.8.11-6.debian.tar.xz
Checksums-Sha256:
 59b7e98681d827d5ccb612411bdf804ae7056490d8f1a4ff1b8970c1b322ad00 2716 
python-cooler_0.8.11-6.dsc
 8e3aac2bd9d8ad42ee41f4828dacfeaa182939c14b43f5c80a7bc1f06f68e8ba 6788 
python-cooler_0.8.11-6.debian.tar.xz
Files:
 d3a911e0adb9fbdf56860e4f441d9e17 2716 science optional 
python-cooler_0.8.11-6.dsc
 17aab2f61dbee1c94eadcb6a2ca525ac 6788 science optional 
python-cooler_0.8.11-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmO5XrgUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdrjng//dakGjSCISuB5latHym6/VlhPuftB
07Xswmut7DiO9SS+ckUuSwM3KDxMd4zb7L1kZlmUNRUPaG4DMPCqHjeRxQSMlsxv
52Ttq6+IRhvtiODIXEikZmHtnkW/evfKrB1AVZzTjs6cSLoA6oOlOmY+0asWUUL/
NhfX8UlVx/mQ7epbpn87UlcLadxdrKjGngmFm8JnhpzO3UKmxDLznvaz8dGyq5Rg
c7+4FswI6qOXPY6wIDtntjPSkKC7MbA5+FPDiuCmfjljYmdf03nhnRFyKrc0uqzN
TN9Tq4QbkKl8nXmMS8XbnMbhYXDfibUCxTRyVX1JTxxV3NiMZ/cdrbCI2ajeC2XQ
/EMbV4pqf5DLoP600lZPDtREv1eE5yk2jB6gqU6iZAD1PPm2c9rw5JV/w2/mdAUV
Fgds1z4ayXYoAtueV+gkcHRKguz7xEIcQqBTHsmDbx5/CJHMjHwtaB2AoVTxEGKu
0RhRQQeItPk6XT5E3IUXRAWoVzhpMWpDk8vHrLZcgS9ms8kAWRIq38udX1zNBxB8
uRCXMRyyONA2mKwlB/LNPV6rVPTRSOOH+kQLWfx58yJRAueB7+VKhuuKTzFHuz02
UwlJlCPtdpW1S3UmFc/jb4Hw44WXxI0n5JrGEZhkVbxI12I8HCBgZZKchzTJ1ARy
KhMN2qGUY5h+k0Y=
=RbNG
-END PGP SIGNATURE End Message ---

Bug#1027707: patroni: autopkgtest fails with etcd 3.4 (v2 not enabled by default)

[Shengjing Zhu]

Hi,

On Mon, Jan 2, 2023 at 6:35 PM Shengjing Zhu  wrote:
>
> Source: patroni
> Version: 2.1.5-1
> Severity: serious
>
> Hi,
>
> I've uploaded etcd 3.4 to unstable. Your package's autopkgtest fails.
> I believe it's because etcd 3.4 doesn't enable v2 API by default.
> Please adjust your autopkgtest with ETCD_ENABLE_V2=true env, or --enable-v2
> option.

I noticed you uploaded 2.1.6 which has  --enable-v2. But the
autopkgtest failure still exists.

I tried to reproduce it locally with the 2.1.6 version.

First I run autopkgtest with the schroot backend, and I can't
reproduce the error.
The I tried the lxd backend. Now I indeed found the error.

# autopkgtest -B -s --test-name=acceptance-etcd-basic
patroni_2.1.6-1.dsc -- lxd autopkgtest/debian/unstable/amd64

root@autopkgtest-lxd-jzdcwl:/tmp/autopkgtest.VeGcZ8/build.2LX/src# cat
features/output/etcd.log
2023-01-07 14:04:06.932041 W | pkg/flags: unrecognized environment
variable ETCD_UNSUPPORTED_ARCH=
[WARNING] Deprecated '--logger=capnslog' flag is set; use
'--logger=zap' flag instead
2023-01-07 14:04:06.932117 I | etcdmain: etcd Version: 3.4.23
2023-01-07 14:04:06.932125 I | etcdmain: Git SHA: Not provided (use
./build instead of go build)
2023-01-07 14:04:06.932132 I | etcdmain: Go Version: go1.19.4
2023-01-07 14:04:06.932139 I | etcdmain: Go OS/Arch: linux/amd64
2023-01-07 14:04:06.932146 I | etcdmain: setting maximum number of
CPUs to 4, total number of available CPUs is 4
[WARNING] Deprecated '--logger=capnslog' flag is set; use
'--logger=zap' flag instead
2023-01-07 14:04:06.932839 C | etcdmain: listen tcp 127.0.0.1:2380:
bind: address already in use

root@autopkgtest-lxd-jzdcwl:/tmp/autopkgtest.VeGcZ8/build.2LX/src#
systemctl status etcd
● etcd.service - etcd - highly-available key value store
Loaded: loaded (/lib/systemd/system/etcd.service; enabled; preset: enabled)
   Drop-In: /run/systemd/system/service.d
└─zzz-lxc-service.conf
Active: active (running) since Sat 2023-01-07 14:03:46 UTC; 44s ago
  Docs: https://etcd.io/docs
man:etcd
  Main PID: 1677 (etcd)
 Tasks: 10 (limit: 9324)
Memory: 31.1M
   CPU: 568ms
CGroup: /system.slice/etcd.service
└─1677 /usr/bin/etcd

There is an etcd instance running. So you test can't start a new one.
I'm not sure why etcd 3.4 behaviors differently with 3.3. But it
doesn't seem wrong for etcd.

So could you mask or kill etcd instances before running tests?

I can run the test successfully with following command:

autopkgtest --setup-commands="systemctl mask etcd" -U -B -s
--test-name=acceptance-etcd-basic patroni_2.1.6-1.dsc -- lxd
autopkgtest/debian/unstable/amd64

--
Shengjing Zhu

Bug#1020915: FTBFS

[matthias . geiger1024]

 Hi,

I just did a quick rebuild of 0.13.5. To me it looks like the bug is fixed as I 
can't reproduce it. 

Cheers

Matthias

Processed: tagging 1027733

[Debian Bug Tracking System]

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

> tags 1027733 + pending
Bug #1027733 [screen] GNU Screen does not support Unicode 14
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1028129: securestring FTBFS: fatal error: Python.h: No such file or directory

[Adrian Bunk]

Source: securestring
Version: 0.2-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=securestring&ver=0.2-1

...
creating build/temp.linux-x86_64-3.10
x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 
-Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv 
-O2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python3.10 -c pysecstr.c -o 
build/temp.linux-x86_64-3.10/pysecstr.o
pysecstr.c:3:10: fatal error: Python.h: No such file or directory
3 | #include 
  |  ^~
compilation terminated.
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:388: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.10 setup.py build

Bug#1026719: preventing lazpaint package removal

[Juliette DAMON-ELSASS]

Hello,

I am the maintainer of lazpaint. I would like to thank you all for having a 
look a this issue.

I received the following some time ago:
> lazpaint 7.2.2-1 is marked for autoremoval from testing on 2023-01-18
> 
> It is affected by these RC bugs:
> 1026718: lazpaint: FTBFS: /usr/bin/ld.bfd: cannot find -lpangocairo-1.0: No 
> such file or directory
>  https://bugs.debian.org/1026718
> 
> It (build-)depends on packages with these RC bugs:
> 1026719: lazarus: vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such 
> file or directory
>  https://bugs.debian.org/1026719

So there is still a bug report associated with the package. Though I suppose it 
is related.

Is it possible to avoid the removal of my package? Or the removal will be 
automatically canceled? Which version of Debian will be affected?

Regards,

  Juliette DAMON-ELSASS

Bug#1004154: Fwd: Bug#1004154: xserver-xorg-video-qxl: XOrg frequently crashes when using qxl driver: qxl(0): error doing QXL_ALLOC

[Felix Leimbach]

Thanks for forwarding Bernhard.

TJ, the problem is gone for me. It was either due to upgrading the RAM size or 
a subsequent kernel update.
Haven't had the problem in months and I'm currently running 
linux-image-5.19.0-2-amd64.
I think you can close this issue.

Bug#1028122: marked as pending in sortmerna

[Étienne Mollier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/sortmerna/-/commit/4e03438b79addfd07198fb70c1baac7d93231b0c


d/rules: build for i386 with -msse2

The package depends on sse2-support for that architecture, so this is
not a baseline violation in this particular case.

Closes: #1028122


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028122

Processed: Bug#1028122 marked as pending in sortmerna

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028122 [src:sortmerna] sortmerna: FTBFS on i386
Added tag(s) pending.

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

Bug#1004154: marked as done (xserver-xorg-video-qxl: XOrg frequently crashes when using qxl driver: qxl(0): error doing QXL_ALLOC)

[Debian Bug Tracking System]

Your message dated Sat, 7 Jan 2023 17:10:57 +0100
with message-id 
and subject line Re: Fwd: Bug#1004154: xserver-xorg-video-qxl: XOrg frequently 
crashes when using qxl driver: qxl(0): error doing QXL_ALLOC
has caused the Debian Bug report #1004154,
regarding xserver-xorg-video-qxl: XOrg frequently crashes when using qxl 
driver: qxl(0): error doing QXL_ALLOC
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.)


-- 
1004154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-video-qxl
Version: 0.1.5+git20200331-1
Severity: grave
Justification: Xorg randomly crashes (all unsaved work lost)

Kernel:
---
Happens with latest 5.15.5-2
Testing older versions right now, will report if they solve the issue

Contents of Xorg X server log file after a crash:
-
[74.435]
X.Org X Server 1.20.14
X Protocol Version 11, Revision 0
[74.435] Build Operating System: linux Debian
[74.435] Current Operating System: Linux fllin 5.15.0-2-amd64 #1 SMP Debian
5.15.5-2 (2021-12-18) x86_64
[74.435] Kernel command line: BOOT_IMAGE=/vmlinuz-5.15.0-2-amd64
root=/dev/mapper/fllin--vg-root ro quiet
[74.435] Build Date: 11 January 2022  02:21:08PM
[74.435] xorg-server 2:1.20.14-1 (https://www.debian.org/support)
[74.435] Current version of pixman: 0.40.0
[74.435]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[74.435] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[74.435] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 21 02:33:59
2022
[74.437] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[74.440] (==) No Layout section.  Using the first Screen section.
[74.440] (==) No screen section available. Using defaults.
[74.440] (**) |-->Screen "Default Screen Section" (0)
[74.440] (**) |   |-->Monitor ""
[74.440] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[74.440] (==) Automatically adding devices
[74.440] (==) Automatically enabling devices
[74.440] (==) Automatically adding GPU devices
[74.440] (==) Max clients allowed: 256, resource mask: 0x1f
[74.443] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[74.443]Entry deleted from font path.
[74.445] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[74.445] (==) ModulePath set to "/usr/lib/xorg/modules"
[74.445] (II) The server relies on udev to provide the list of input
devices.
If no devices become available, reconfigure udev or disable
AutoAddDevices.
[74.445] (II) Loader magic: 0x5576e43e1e40
[74.445] (II) Module ABI versions:
[74.445]X.Org ANSI C Emulation: 0.4
[74.445]X.Org Video Driver: 24.1
[74.445]X.Org XInput driver : 24.1
[74.445]X.Org Server Extension : 10.0
[74.446] (++) using VT number 7

[74.446] (II) systemd-logind: logind integration requires -keeptty and
-keeptty was not provided, disabling logind integration
[74.446] (II) xfree86: Adding drm device (/dev/dri/card0)
[74.449] (--) PCI:*(0@0:2:0) 1b36:0100:1af4:1100 rev 5, Mem @
0xe800/134217728, 0xf000/134217728, 0xf8054000/8192,
0xd000/268435456, I/O @ 0xc160/32, BIOS @ 0x/131072
[74.449] (II) LoadModule: "glx"
[74.450] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[74.457] (II) Module glx: vendor="X.Org Foundation"
[74.457]compiled for 1.20.14, module version = 1.0.0
[74.457]ABI class: X.Org Server Extension, version 10.0
[74.457] (==) Matched qxl as autoconfigured driver 0
[74.457] (==) Matched modesetting as autoconfigured driver 1
[74.457] (==) Matched fbdev as autoconfigured driver 2
[74.457] (==) Matched vesa as autoconfigured driver 3
[74.457] (==) Assigned the driver to the xf86ConfigLayout
[74.457] (II) LoadModule: "qxl"
[74.458] (II) Loading /usr/lib/xorg/modules/drivers/qxl_drv.so
[74.459] (II) Module qxl: vendor="X.Org Foundation"
[74.459]compiled for 1.20.8, module v

Bug#1025778: marked as done (libnewuoa breaks libpdb-redo autopkgtest: pdb-redo-example (Failed))

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 16:38:34 +
with message-id 
and subject line Bug#1025778: fixed in libpdb-redo 3.0.4-3
has caused the Debian Bug report #1025778,
regarding libnewuoa breaks libpdb-redo autopkgtest: pdb-redo-example (Failed)
to be marked as done.

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

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


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

Source: libnewuoa, libpdb-redo
Control: found -1 libnewuoa/0.1.2-1
Control: found -1 libpdb-redo/2.0.3-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
libnewuoa  from testing0.1.2-1
libpdb-redofrom testing2.0.3-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 libnewuoa 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=libnewuoa

https://ci.debian.net/data/autopkgtest/testing/amd64/libp/libpdb-redo/29137519/log.gz

-- The CXX compiler identification is GNU 12.2.0
-- The C compiler identification is GNU 12.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Looking for ccp4/ccp4_general.h - /usr/include
-- Found CCP4: /usr/lib/x86_64-linux-gnu/libccp4c.so  -- Performing Test 
CMAKE_HAVE_LIBC_PTHREAD

-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE  -- Looking for clipper/clipper.h - /usr/include
-- Found CCP4: /usr/lib/x86_64-linux-gnu/libclipper-core.so  -- FFTW2 
libraries - /usr/lib/libsfftw.so

-- - /usr/lib/libsrfftw.so
-- FFTW2 header directory - /usr/include
-- Performing Test _LINKING_WITH_CLIPPER_CORE
-- Performing Test _LINKING_WITH_CLIPPER_CORE - Success
-- Looking for clipper/clipper-ccp4.h - /usr/include
-- Found CCP4: /usr/lib/x86_64-linux-gnu/libclipper-ccp4.so  -- Looking 
for clipper/clipper-contrib.h - /usr/include
-- Found CCP4: /usr/lib/x86_64-linux-gnu/libclipper-contrib.so  -- CCP4 
include directory: /usr/include
-- Found Boost: 
/usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake (found 
suitable version "1.74.0", minimum required is "1.70.0") found 
components: system iostreams regex -- Found Boost: 
/usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake (found 
suitable version "1.74.0", minimum required is "1.70.0") found 
components: system date_time regex -- Looking for ccp4/ccp4_general.h - 
/usr/include
-- Found CCP4: /usr/lib/x86_64-linux-gnu/libccp4c.so  -- Looking for 
clipper/clipper.h - /usr/include
-- Found CCP4: /usr/lib/x86_64-linux-gnu/libclipper-core.so  -- FFTW2 
libraries - /usr/lib/libsfftw.so

-- - /usr/lib/libsrfftw.so
-- FFTW2 header directory - /usr/include
-- Looking for clipper/clipper-ccp4.h - /usr/include
-- Found CCP4: /usr/lib/x86_64-linux-gnu/libclipper-ccp4.so  -- Looking 
for clipper/clipper-contrib.h - /usr/include
-- Found CCP4: /usr/lib/x86_64-linux-gnu/libclipper-contrib.so  -- CCP4 
include directory: /usr/include

-- Configuring done
-- Generating done
-- Build files have been written to: 
/tmp/autopkgtest-lxc.qdh1lkps/downtmp/autopkgtest_tmp/build

[ 50%] Building CXX object CMakeFiles/pdb-redo-example.dir/example.cpp.o
[100%] Linking CXX executable pdb-redo-example
/usr/bin/ld: warning: libnewuoa.so.0, needed by 
/usr/lib/x86_64-linux-gnu/libpdb-redo.so.2.0.3, not found (try using 
-rpath or -rpath-link)

[100%] Built target pdb-redo-example
Test project /tmp/autopkgtest-lxc.qdh1lkps/downtmp/autopkgtest_tmp/build
Start 1: pdb-redo-example
1/1 Test #1

Processed: affects 1028084

[Debian Bug Tracking System]

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

> affects 1028084 src:guiqwt
Bug #1028084 [src:guidata] guidata FTBFS with Python 3.11 as default version
Added indication that 1028084 affects src:guiqwt
> thanks
Stopping processing here.

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

Bug#1027950: marked as done (pyside2 FTBFS with Python 3.11 as default version)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 16:58:34 +
with message-id 
and subject line Bug#1027950: fixed in pyside2 5.15.8-1
has caused the Debian Bug report #1027950,
regarding pyside2 FTBFS with Python 3.11 as default version
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.)


-- 
1027950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyside2
Version: 5.15.2-2.3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=pyside2&arch=amd64&ver=5.15.2-2.3%2Bb4&stamp=1672846001&raw=0

...
 debian/rules clean
dh clean --with python3,sphinxdoc --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:240: python3.11 setup.py clean 
Unsupported python version detected. Only these python versions are supported: 
[(2, 7), (3, 5), (3, 6), (3, 7), (3, 8), (3, 9), (3, 10)]
E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1: 
python3.11 setup.py clean 
dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned exit 
code 13
make: *** [debian/rules:30: clean] Error 25
--- End Message ---
--- Begin Message ---
Source: pyside2
Source-Version: 5.15.8-1
Done: Dmitry Shachnev 

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

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

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated pyside2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Jan 2023 17:38:12 +0400
Source: pyside2
Architecture: source
Version: 5.15.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Dmitry Shachnev 
Closes: 1027950
Changes:
 pyside2 (5.15.8-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
   * Drop patches, included in the new release:
 - fix-reuse-build.patch
 - qApp-fix-flag-handling.patch
 - py3.10-prep-reset-the-type-cache-after-feature-switching.patch
 - py3.10-prep-Fix-parser.py-for-changed-typing-module.patch
 - py3.10-prep-Finally-support-Python-3.10.patch
 - py3.10-prep-Fix-a-very-old-refcounting-error-in-time_test.patch
 - shiboken6-Adapt-to-LLVM-12.01.patch
   * Refresh debian/patches/blacklist-failing-tests.patch.
   * Backport 7 upstream patches to support Python 3.11 (closes: #1027950).
   * Remove dh-exec (debhelper now supports substitutions natively).
   * Revert a change from 5.15.8 which broke build without limited API.
   * Add a patch to fix AttributeError in signature_bootstrap.py.
   * Fix redundant-globbing-patterns Lintian warning.
   * Bump Standards-Version to 4.6.2, no changes needed.
Checksums-Sha1:
 030327d0d0bf1090a6f2a85964f15c90db629edb 7786 pyside2_5.15.8-1.dsc
 e01d1ae36249e639f1f631c6ad70666a1dd5fef6 3582256 pyside2_5.15.8.orig.tar.xz
 43b7fa78d222f9a50d0c09b662d83f5ebcd1d798 19584 pyside2_5.15.8-1.debian.tar.xz
 852a6c1086ae1e4b629d4ff1317264a00dd167dc 20658 
pyside2_5.15.8-1_source.buildinfo
Checksums-Sha256:
 3188d4f2c2d190564c5dc9c57eecef2c6c999de80cc49332129095f8585c06e6 7786 
pyside2_5.15.8-1.dsc
 23436302c8deb5b4cbc769b205d09604e38ba83b40708efccb7bd8c9af6f6b5d 3582256 
pyside2_5.15.8.orig.tar.xz
 6d5b338600025102a250c27937debc4abe17e2d8a42f6877214c779bbde54ea3 19584 
pyside2_5.15.8-1.debian.tar.xz
 f8979d2660d4fa51346bd48851e375415e6749328ffdecf6390abbbf21bb72a9 20658 
pyside2_5.15.8-1_source.buildinfo
Files:
 850ac662494a8ceb795f056af3e820b7 7786 python optional pyside2_5.15.8-1.dsc
 0152004ac8c2f2012999a93aed5d8a6e 3582256 python optional 
pyside2_5.15.8.orig.tar.xz
 0b681e15ecbd29b6bc235fdff51b43ed 19584 python optional 
pyside2_5.15.8-1.debian.tar.xz
 5a16214467aed7bae062c01de14d16d7 20658 python optional 
pyside2_5.15.8-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAmO5dsYTHG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDy0x3D/9JAHK8IavQOCC97MYYO9/+QtJIcicc
poREVXn+MuDYDCzvBRFQq7GwgdNJ1nlmI54EK2YCeRzHHQAak5GzTeQVCK/GvbXJ
ZVhIdJGLJt0MxpZ7hqWOsPOqQnL10O/vuKiMQKxrc2uhAu1QDxYYyGYrSmzVJrBX
ugH7EHm

Bug#1028138: arandr: no longer starts: module 'inspect' has no attribute 'getargspec'

[Reiner Herrmann]

Package: arandr
Version: 0.1.10-1.1
Severity: serious

Dear maintainer,

since I updated some Python packages recently, arandr is no longer starting:

> $ arandr
> Traceback (most recent call last):
>   File "/usr/bin/arandr", line 41, in 
> from screenlayout.gui import main
>   File "/usr/lib/python3/dist-packages/screenlayout/gui.py", line 76, in 
> 
> class Application:
>   File "/usr/lib/python3/dist-packages/screenlayout/gui.py", line 185, in 
> Application
> @actioncallback
>  ^^
>   File "/usr/lib/python3/dist-packages/screenlayout/gui.py", line 48, in 
> actioncallback
> argnames = inspect.getargspec(function)[0]
>^^
> AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean: 
> 'getargs'?

Kind regards,
  Reiner

Bug#1020915: marked as done (rust-xmlparser: FTBFS: cdata_err_01 test fails)

[Debian Bug Tracking System]

Your message dated Sat, 7 Jan 2023 17:21:58 +
with message-id 
and subject line RE: FTBFS
has caused the Debian Bug report #1020915,
regarding rust-xmlparser: FTBFS: cdata_err_01 test fails
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.)


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

Hi,

rust-xmlparser/experimental (but not the version in sid) recently
started to FTBFS (previous rebuilds in February and May succeeded):

...
 Running 
`/build/rust-xmlparser-0.13.3/target/x86_64-unknown-linux-gnu/debug/deps/cdata-4167abb68ff53f68`

running 10 tests
test cdata_05 ... ok
test cdata_08 ... ok
test cdata_01 ... ok
test cdata_02 ... ok
test cdata_03 ... ok
test cdata_04 ... ok
test cdata_09 ... ok
test cdata_06 ... ok
test cdata_07 ... ok
test cdata_err_01 ... FAILED

failures:

 cdata_err_01 stdout 
thread 'cdata_err_01' panicked at 'assertion failed: `(left == right)`
  left: `Error("invalid CDATA at 1:4 cause a non-XML character '\\0' found at 
1:13")`,
 right: `Error("invalid CDATA at 1:4 cause a non-XML character '\\u{0}' found 
at 1:13")`', tests/cdata.rs:72:1
stack backtrace:
   0: rust_begin_unwind
 at /usr/src/rustc-1.61.0/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
 at /usr/src/rustc-1.61.0/library/core/src/panicking.rs:143:14
   2: core::panicking::assert_failed_inner
   3: core::panicking::assert_failed
 at /usr/src/rustc-1.61.0/library/core/src/panicking.rs:182:5
   4: cdata::cdata_err_01
 at /usr/share/cargo/registry/xmlparser-0.13.3/tests/token.rs:49:17
   5: cdata::cdata_err_01::{{closure}}
 at /usr/share/cargo/registry/xmlparser-0.13.3/tests/token.rs:45:9
   6: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.61.0/library/core/src/ops/function.rs:227:5
   7: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.61.0/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.


failures:
cdata_err_01

test result: FAILED. 9 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.01s

error: test failed, to rerun pass '--test cdata'
dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 
101
make[1]: *** [debian/rules:6: override_dh_auto_test] Error 25


Andreas


rust-xmlparser_0.13.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---


I just did a quick rebuild of 0.13.5. To me it looks like the bug is fixed


Agreed, 0.13.5-1 built on all release architectures when it was uploaded to
unstable (some time after this bug was filed) and also looks fine on
reproducible builds. So i'm going to close this bug.--- End Message ---

Processed: Sphinx 5 is now in unstable

[Debian Bug Tracking System]

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

> severity 1013383 serious
Bug #1013383 [src:ruby-github-markup] ruby-github-markup: FTBFS with Sphinx 
5.0, docutils 0.18: ERROR: Test "ruby3.0" failed.
Severity set to 'serious' from 'important'
> severity 1013395 serious
Bug #1013395 [src:mpdecimal] mpdecimal: FTBFS with Sphinx 5.0, docutils 0.18: 
make[1]: *** [debian/rules:60: override_dh_sphinxdoc] Error 255
Ignoring request to change severity of Bug 1013395 to the same value.
> close 1013405 1.11.1-1
Bug #1013405 [src:sympy] sympy: FTBFS with Sphinx 5.0, docutils 0.18: 
AttributeError: 'Text' object has no attribute 'rawsource'
Marked as fixed in versions sympy/1.11.1-1.
Bug #1013405 [src:sympy] sympy: FTBFS with Sphinx 5.0, docutils 0.18: 
AttributeError: 'Text' object has no attribute 'rawsource'
Marked Bug as done
> close 1013402
Bug #1013402 [src:python-openstacksdk] python-openstacksdk: FTBFS with Sphinx 
5.0, docutils 0.18: FAIL: 
openstack.tests.unit.identity.v2.test_role.TestRole.test_make_it
Marked Bug as done
> close 1013408
Bug #1013408 [src:macsyfinder] macsyfinder: FTBFS with Sphinx 5.0, docutils 
0.18: dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned 
exit code 13
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1028139: q-text-as-data FTBFS: FAILED test/test_suite.py::FormattingTests::test_universal_newlines_parsing_flag

[Adrian Bunk]

Source: q-text-as-data
Version: 3.1.6-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/q-text-as-data.html

...
=== FAILURES ===
_ FormattingTests.test_universal_newlines_parsing_flag _

self = 

def test_universal_newlines_parsing_flag(self):
def list_as_byte_list(l):
return list(map(lambda x:six.b(x),l))

expected_output = list(map(lambda x:list_as_byte_list(x),[['lifelock', 
'LifeLock', '', 'web', 'Tempe', 'AZ', '1-May-07', '685', 'USD', 'b'],
   ['lifelock', 'LifeLock', '', 'web', 'Tempe', 'AZ', 
'1-Oct-06', '600', 'USD', 'a'],
   ['lifelock', 'LifeLock', '', 'web', 'Tempe', 'AZ', 
'1-Jan-08', '2500', 'USD', 'c'],
   ['mycityfaces', 'MyCityFaces', '7', 'web', 
'Scottsdale', 'AZ', '1-Jan-08', '5', 'USD', 'seed'],
   ['flypaper', 'Flypaper', '', 'web', 'Phoenix', 'AZ', 
'1-Feb-08', '300', 'USD', 'a'],
   ['infusionsoft', 'Infusionsoft', '105', 'software', 
'Gilbert', 'AZ', '1-Oct-07', '900', 'USD', 'a']]))

data = 
six.b('permalink,company,numEmps,category,city,state,fundedDate,raisedAmt,raisedCurrency,round\rlifelock,LifeLock,,web,Tempe,AZ,1-May-07,685,USD,b\rlifelock,LifeLock,,web,Tempe,AZ,1-Oct-06,600,USD,a\rlifelock,LifeLock,,web,Tempe,AZ,1-Jan-08,2500,USD,c\rmycityfaces,MyCityFaces,7,web,Scottsdale,AZ,1-Jan-08,5,USD,seed\rflypaper,Flypaper,,web,Phoenix,AZ,1-Feb-08,300,USD,a\rinfusionsoft,Infusionsoft,105,software,Gilbert,AZ,1-Oct-07,900,USD,a')
tmp_data_file = self.create_file_with_data(data)

cmd = Q_EXECUTABLE + ' -d , -H -U "select 
permalink,company,numEmps,category,city,state,fundedDate,raisedAmt,raisedCurrency,round
 from %s"' % tmp_data_file.name
retcode, o, e = run_command(cmd)

>   self.assertEqual(retcode,0)
E   AssertionError: 59 != 0

test/test_suite.py:4851: AssertionError
- Captured stdout call -
CMD: /build/1st/q-text-as-data-3.1.6/bin/q.py -d , -H -U "select 
permalink,company,numEmps,category,city,state,fundedDate,raisedAmt,raisedCurrency,round
 from /tmp/tmps51xoyjb"
RESULT:(59, [], [b"Could not parse the input. Please make sure to set the 
proper -w input-wrapping parameter for your input, and that you use the proper 
input encoding (-e). Error: invalid mode: 'rU'"])
=== short test summary info 
FAILED test/test_suite.py::FormattingTests::test_universal_newlines_parsing_flag
 1 failed, 223 passed, 3 deselected in 61.17s (0:01:01) 
make[1]: *** [debian/rules:27: override_dh_auto_test] Error 1

Bug#1014548: marked as done (tiledarray build-depends on non-existent libbtas-dev)

[Debian Bug Tracking System]

Your message dated Sat, 7 Jan 2023 18:44:30 +0100
with message-id <63b9af7f.050a0220.dfccb.2...@mx.google.com>
and subject line Re: [Debichem-devel] Bug#1014548: tiledarray build-depends on 
non-existent libbtas-dev
has caused the Debian Bug report #1014548,
regarding tiledarray build-depends on non-existent libbtas-dev
to be marked as done.

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

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


-- 
1014548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tiledarray
Version: 1.0.0-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic

Hi Michael,

tiledarray in unstable has added a build-dependency on libbtas-dev. 
However, this package does not exist anywhere in Debian and there is no sign
of it in the NEW queue, therefore tiledarray is not built on any
architectures.

Please upload libbtas to Debian, or drop the build-dependency on the
non-existent package.

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi Steve,

On Thu, Jul 07, 2022 at 10:15:46AM -0700, Steve Langasek wrote:
> Source: tiledarray
> Version: 1.0.0-1
> Severity: serious
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu kinetic
> 
> Hi Michael,
> 
> tiledarray in unstable has added a build-dependency on libbtas-dev. 
> However, this package does not exist anywhere in Debian and there is no sign
> of it in the NEW queue, therefore tiledarray is not built on any
> architectures.

I think it was rejected, and I forgot about that when I uploaded
tiledarrey.
 
> Please upload libbtas to Debian, or drop the build-dependency on the
> non-existent package.

In the meantime, libbtas-dev has entered the archive, so this bug is
resolved.


Michael--- End Message ---

Bug#1028142: dlocate: cannot find recent files - obsolete database?

[Vincent Lefevre]

Package: dlocate
Version: 1.12
Severity: grave
Justification: renders package unusable

dlocate cannot find recent files, so it is mostly useless.

I suspect that since the upgrade to dlocate 1.12 on 2022-11-25,
its database is no longer updated:

zira:~> ll /var/lib/dlocate
total 109172
-rw-r--r-- 1 root root 55750318 2022-11-25 00:27:44 dlocatedb
-rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old
-rw-r--r-- 1 root root   105318 2022-11-25 00:27:44 dlocatedb.stamps
-rw-r--r-- 1 root root   299199 2022-11-25 00:27:44 dpkg-list

The changelog doesn't mention any change:

dlocate (1.12) unstable; urgency=medium

  * QA upload.
  * Convert to 3.0 source format. Closes: #1007667

 -- Bastian Germann   Thu, 24 Nov 2022 00:10:50 +0100

The cron file /etc/cron.daily/dlocate is there, though:

#!/bin/sh

# update databases for both files and packages.
if [ -x /usr/sbin/update-dlocatedb ] ; then
  /usr/sbin/update-dlocatedb -b
fi

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

Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dlocate depends on:
ii  dctrl-tools [grep-dctrl]  2.24-3+b1
ii  dpkg  1.21.17
ii  perl  5.36.0-6

Versions of packages dlocate recommends:
ii  supercat  0.5.7-1

dlocate suggests no packages.

-- no debconf information

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

Bug#1027025: [Debichem-devel] Bug#1027025: psi4: FTBFS with Python 3.11 as default version

[Michael Banck]

Hi James,

On Thu, Jan 05, 2023 at 04:14:24PM +, James Addison wrote:
> Source: psi4
> Version: 1:1.3.2+dfsg-3
> Followup-For: Bug #1027025
> 
> I've opened a merge request[1] to address what I thought was a
> cmake-related build failure cause on Python 3.11, described in my
> previous message.. however it looks like the package has built
> successfully since then - so I might have been on the wrong track
> there (apologies).

Thanks, I've merged it.

I think it always built fine, but psi4 was broken at runtime so all the
tests failed, but that did not lead to a build failure. With your patch,
most of the tests pass and I'll have to investigate the remaining
numerical issues.


Michael

Bug#1028142: dlocate: cannot find recent files - obsolete database?

[Sven Joachim]

On 2023-01-07 18:53 +0100, Vincent Lefevre wrote:

> Package: dlocate
> Version: 1.12
> Severity: grave
> Justification: renders package unusable
>
> dlocate cannot find recent files, so it is mostly useless.
>
> I suspect that since the upgrade to dlocate 1.12 on 2022-11-25,
> its database is no longer updated:
>
> zira:~> ll /var/lib/dlocate
> total 109172
> -rw-r--r-- 1 root root 55750318 2022-11-25 00:27:44 dlocatedb
> -rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old
> -rw-r--r-- 1 root root   105318 2022-11-25 00:27:44 dlocatedb.stamps
> -rw-r--r-- 1 root root   299199 2022-11-25 00:27:44 dpkg-list

That could have been the case for much longer actually.  At installation
time, the postinst script runs "update-dlocatedb -b" which seems to have
been successful.

> The cron file /etc/cron.daily/dlocate is there, though:
>
> #!/bin/sh
>
> # update databases for both files and packages.
> if [ -x /usr/sbin/update-dlocatedb ] ; then
>   /usr/sbin/update-dlocatedb -b
> fi

But apparently it is never executed.  Are any other cron jobs being run
on your system?  If not, you may have been bitten by bug #1019554 in
anacron which needs manual restore as mentioned in
https://lists.debian.org/debian-devel-announce/2022/11/msg1.html.

Cheers,
   Sven

Bug#965624: marked as done (libapache2-mod-lisp: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 18:19:02 +
with message-id 
and subject line Bug#965624: fixed in libapache2-mod-lisp 1.3.1-2
has caused the Debian Bug report #965624,
regarding libapache2-mod-lisp: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
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.)


-- 
965624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libapache2-mod-lisp
Version: 1.3.1-1.3
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package libapache2-mod-lisp uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

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

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


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

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: libapache2-mod-lisp
Source-Version: 1.3.1-2
Done: Marcos Talau 

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

Debian distribution maintenance software
pp.
Marcos Talau  (supplier of updated libapache2-mod-lisp 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Jan 2023 13:50:33 -0300
Source: libapache2-mod-lisp
Architecture: source
Version: 1.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Marcos Talau 
Closes: 965624 999213
Changes:
 libapache2-mod-lisp (1.3.1-2) unstable; urgency=medium
 .
   * QA upload.
   * Convert package to source format 3.0 (quilt). Consequently:
 - debian/source/format: New.
 - debian/patches/:
   ~ apache2.4-fixes.patch: Rename to "02_apache2.4-fixes.patch".
   ~ 01_APR_FTBS.patch: New. Patch extracted from "diff.gz"
   ~ 03_create_makefile.patch: New. Patch extracted from "diff.gz".
   ~ 04_create_modulesmk.patch: New. Patch extracted from "diff.gz".
   * Set maintainer to Debian QA Group . (see: #829682)
   * Using new DH level format. Consequently:
 - debian/compat: Remove.
 - debian/control: Change from 'debhelper' to 'debhelper-compat' in
   Build-Depends field and bump level to 13.
 - Closes: #965624.
   * debian/control:
 - Add Vcs-* fields.
 - Change Section from devel to httpd.
   * debian/libapache2-mod-lisp.debhelper.log: Remove. No longer need.
   * debian/libapache2-mod-lisp.preinst: Remove. No longer need.
   * debian/rules: Completely rewritten (Closes: #999213).
   * debian/salsa-ci.yml: Add to provide CI tests for Salsa.
   * debian/tests/*: Create autopkgtest.
Checksums-Sha1:
 6df3d4b862aef32bd03caa24580afc2397b9af15 1993 libapache2-mod-lisp_1.3.1-2.dsc
 84b006a73f6e2be5fad24e939f2294fc620c5509 5232 
libapache2-mod-lisp_1.3.1-2.debian.tar.xz
 31b54aa0851ffd48a78bda380ceba40b4e7841fa 7597 
libapache2-mod-lisp_1.3.1-2_source.buildinfo
Checksums-Sha256:
 044eaaa7dadf1c5d3828ec2f24b985e86b3d242fd5f4e0d5c0d291e6e2ea2d04 1993 
libapache2-mod-lisp_1.3.1-2.dsc
 6f9632236c208aeb8c8283089950156e05bfea53522745aa35fb6c9dd6e1a6fa 5232 
libapache2-mod-lisp_1.3.1-2.debian.tar.xz
 18a0af0d50ec5316b8a97edd488d2302f15a73512e7ce828c1c2f8719dd779ad 7597 
libapache2-mod-lisp_1.3.1-2_source.buildinfo
Files:
 cf649ee9f0cc5a15de706df95ed3dd4b

Bug#999213: marked as done (libapache2-mod-lisp: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 18:19:02 +
with message-id 
and subject line Bug#999213: fixed in libapache2-mod-lisp 1.3.1-2
has caused the Debian Bug report #999213,
regarding libapache2-mod-lisp: 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.)


-- 
999213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libapache2-mod-lisp
Version: 1.3.1-1.3
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: libapache2-mod-lisp
Source-Version: 1.3.1-2
Done: Marcos Talau 

We believe that the bug you reported is fixed in the latest version of
libapache2-mod-lisp, 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.
Marcos Talau  (supplier of updated libapache2-mod-lisp 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Jan 2023 13:50:33 -0300
Source: libapache2-mod-lisp
Architecture: source
Version: 1.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Marcos Talau 
Closes: 965624 999213
Changes:
 libapache2-mod-lisp (1.3.1-2) unstable; urgency=medium
 .
   * QA upload.
   * Convert package to source format 3.0 (quilt). Consequently:
 - debian/source/format: New.
 - debian/patches/:
   ~ apache2.4-fixes.patch: Rename to "02_apache2.4-fixes.patch".
   ~ 01_APR_FTBS.patch: New. Patch extracted from "diff.gz"
   ~ 03_create_makefile.patch: New. Patch extracted from "diff.gz".
   ~ 04_create_modulesmk.patch: New. Patch extracted from "diff.gz".
   * Set maintainer to Debian QA Group . (see: #829682)
   * Using new DH level format. Consequently:
 - debian/compat: Remove.
 - debian/control: Change from 'debhelper' to 'debhelper-compat' in
   Build-Depends field and bump level to 13.
 - Closes: #965624.
   * debian/control:
 - Add Vcs-* fields.
 - Change Section from devel to httpd.
   * debian/libapache2-mod-lisp.debhelper.log: Remove. No longer need.
   * debian/libapache2-mod-lisp.preinst: Remove. No longer need.
   * debian/rules: Completely rewritten (Closes: #999213).
   * debian/salsa-ci.yml: Add to provide CI tests for Salsa.
   * debian/tests/*: Create autopkgtest.
Checksums-Sha1:
 6df3d4b862aef32bd03caa24580afc2397b9af15 1993 libapache2-mod-lisp_1.3.1-2.dsc
 84b006a73f6e2be5fad24e939f2294fc620c5509 5232 
libapache2-mod-lisp_1.3.1-2.debian.tar.xz
 31b54aa0851ffd48a78bda380ceba40b4e7841fa 7597 
libapache2-mod-lisp_1.3.1-2_source.buildinfo
Checksums-Sha256:
 044eaaa7dadf1c5d3828ec2f24b985e86b3d242fd5f4e0d5c0d291e6e2ea2d04 1993 
libapache2-mod-lisp_1.3.1-2.dsc
 6f9632236c208aeb8c8283089950156e05bfea53522745aa35fb6c9dd6e1a6fa 5232 
libapache2-mod-lisp_1.3.1-2.debian.tar.xz
 18a0af0d50ec5316b8a97edd488d2302f15a73512e7ce828c1c2f8719dd779ad 7597 
libapache2-mod-lisp_1.3.1-2_source.buildinfo
Files:
 cf649ee9f0cc5a15de706df95ed3dd4b 1993 httpd optional 
libapache2-mod-lisp_1.3.1-2.dsc
 2f455a0cd9cfc02c6799f6e8b820490d 5232 httpd optional 
libapache2-mod-lisp_1.3.1-2.debian.tar.xz
 247966ede4abcd4780694d3c7904aba9 7597 httpd optional 
libapache2-mod-lisp_1.3.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmO5o64ACgkQ9LqqgNso
ukwUtg//TyWEJZ

Processed: Re: Bug#996234: ruby-github-markup: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #996234 [src:ruby-github-markup] ruby-github-markup: FTBFS with ruby3.0: 
ERROR: Test "ruby3.0" failed.
Severity set to 'serious' from 'important'
> tags -1 - moreinfo unreproducible
Bug #996234 [src:ruby-github-markup] ruby-github-markup: FTBFS with ruby3.0: 
ERROR: Test "ruby3.0" failed.
Removed tag(s) moreinfo and unreproducible.

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

Bug#1027163: marked as done (python-git: CVE-2022-24439)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 18:40:07 +
with message-id 
and subject line Bug#1027163: fixed in python-git 3.1.30-1
has caused the Debian Bug report #1027163,
regarding python-git: CVE-2022-24439
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.)


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

Hi,

The following vulnerability was published for python-git.

CVE-2022-24439[0]:
| All versions of package gitpython are vulnerable to Remote Code
| Execution (RCE) due to improper user input validation, which makes it
| possible to inject a maliciously crafted remote URL into the clone
| command. Exploiting this vulnerability is possible because the library
| makes external calls to git without sufficient sanitization of input
| arguments.

https://security.snyk.io/vuln/SNYK-PYTHON-GITPYTHON-3113858
https://github.com/gitpython-developers/GitPython/issues/1515
https://github.com/gitpython-developers/GitPython/pull/1521

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-24439
https://www.cve.org/CVERecord?id=CVE-2022-24439

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: python-git
Source-Version: 3.1.30-1
Done: Jochen Sprickerhof 

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

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

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated python-git 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Jan 2023 15:36:58 +0100
Source: python-git
Architecture: source
Version: 3.1.30-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Jochen Sprickerhof 
Closes: 1018503 1027163
Changes:
 python-git (3.1.30-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Team upload.
   * Update standards version to 4.6.1, no changes needed.
 .
   [ Jochen Sprickerhof ]
   * Switch d/watch to Github
   * New upstream version 3.1.30 (Closes: #1027163)
 - CVE-2022-24439: Remote Code Execution
   * Minimize d/rules
   * Update (build) dependencies (Closes: #1018503)
   * Add autopkgtest
   * Drop salsa-ci.yml
   * Bump policy version (no changes)
   * Move package description to source package
   * Add R³
Checksums-Sha1:
 47be56d2419f5b9b88c56c04c6bc142f86ec188c 2742 python-git_3.1.30-1.dsc
 182e33029e675dc700d90006c6508e31a2579b10 477652 python-git_3.1.30.orig.tar.gz
 f43bd6d90ebf49287b367c73fed35cc9f2448abf 6864 python-git_3.1.30-1.debian.tar.xz
 c56e518f0076cb997d310fd4e7f609f976b071a7 7471 
python-git_3.1.30-1_source.buildinfo
Checksums-Sha256:
 902263de7b2dae1a27293582ee79c46d0157f20ad80fbd1947a58ab42835820b 2742 
python-git_3.1.30-1.dsc
 faa4b66b0b75f172358fbb75243c9d2a70b26623232eef365739fc96e9ecffc8 477652 
python-git_3.1.30.orig.tar.gz
 bb5c80a375b1ebac16a400565e458696c5c2acc9e3eb159b7fb00b3b45380b19 6864 
python-git_3.1.30-1.debian.tar.xz
 537fe7ae5c9430fabae5ed3c41c3dba2845df6886ea8bf6da8aeae3f39690df2 7471 
python-git_3.1.30-1_source.buildinfo
Files:
 cf803b9b3173100a59151b4b3c7dc49a 2742 python optional python-git_3.1.30-1.dsc
 50bee4876f7e4ac3a67111c0aa602d0d 477652 python optional 
python-git_3.1.30.orig.tar.gz
 ff7e9a14718b141d0c39e03c7bdc1d66 6864 python optional 
python-git_3.1.30-1.debian.tar.xz
 2bbcbcaa974dceba4e20c75ea679720f 7471 python optional 
python-git_3.1.30-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmO5iEkACgkQW//cwljm
lDMC1hAAjYgSmM+2Ew8k4SiMUe+aQOp38v9K4duGX4STtvgO2tqojqnXOT2Bwy27
kKq691cnZIeOpOmjFWa6QbxmQGrs4gJABcKiDIHexR3yYOLmmoamWj5nXJWF8Xms
XXKlAnL/FA64wnGSdWXBUjZBiKZ1lHc8tyP610joswpfyNkeqFVn8JyKj3gHyUIn
QMVjDFjVR7YtmMTnvRCcy3hYHXhBEqsVVK3e+B3GvovQySyx8Ye+BuesaMDllOjJ
bpUj73Ai

Processed: affects 1026520

[Debian Bug Tracking System]

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

> affects 1026520 + reprotest
Bug #1026520 [src:python-rstr] reprotest: FTBFS: AttributeError: module 're' 
has no attribute 'sre_parse'
Bug #1026569 [src:python-rstr] python-rstr: FTBFS: AttributeError: module 're' 
has no attribute 'sre_parse'
Added indication that 1026520 affects reprotest
Added indication that 1026569 affects reprotest
> thanks
Stopping processing here.

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

Bug#1028142: dlocate: cannot find recent files - obsolete database?

[Vincent Lefevre]

On 2023-01-07 19:20:56 +0100, Sven Joachim wrote:
> On 2023-01-07 18:53 +0100, Vincent Lefevre wrote:
> > zira:~> ll /var/lib/dlocate
> > total 109172
> > -rw-r--r-- 1 root root 55750318 2022-11-25 00:27:44 dlocatedb
> > -rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old
> > -rw-r--r-- 1 root root   105318 2022-11-25 00:27:44 dlocatedb.stamps
> > -rw-r--r-- 1 root root   299199 2022-11-25 00:27:44 dpkg-list

Same issue my other machine.

> That could have been the case for much longer actually.  At installation
> time, the postinst script runs "update-dlocatedb -b" which seems to have
> been successful.

I suppose that explains the

> > -rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old

> > The cron file /etc/cron.daily/dlocate is there, though:
> >
> > #!/bin/sh
> >
> > # update databases for both files and packages.
> > if [ -x /usr/sbin/update-dlocatedb ] ; then
> >   /usr/sbin/update-dlocatedb -b
> > fi
> 
> But apparently it is never executed.  Are any other cron jobs being run
> on your system?

In the logs I can see for today:

Jan 07 06:25:01 zira CRON[1843444]: (root) CMD (test -x /usr/sbin/anacron || { 
cd / && run-parts --report /etc/cron.daily; })

and

Jan 07 14:38:01 zira CRON[1857920]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)

So it seems to be OK, though I don't know what leads to the logging
of popularity-contest only.

> If not, you may have been bitten by bug #1019554 in
> anacron which needs manual restore as mentioned in
> https://lists.debian.org/debian-devel-announce/2022/11/msg1.html.

2022-07-14 20:57:59 upgrade anacron:amd64 2.3-32 2.3-33
2022-07-14 20:57:59 status half-configured anacron:amd64 2.3-32
2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-32
2022-07-14 20:57:59 status half-installed anacron:amd64 2.3-32
2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-33

but I get mail from failing cron scripts.

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

Bug#1028122: marked as done (sortmerna: FTBFS on i386)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 18:48:55 +
with message-id 
and subject line Bug#1028122: fixed in sortmerna 4.3.6-2
has caused the Debian Bug report #1028122,
regarding sortmerna: FTBFS on i386
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=sortmerna&arch=i386&ver=4.3.6-1&stamp=1673038926&raw=0

cd /<>/obj-i686-linux-gnu/src/sortmerna && /usr/bin/cc  
-I/<>/include -I/<>/3rdparty/cmph 
-I/<>/3rdparty/concurrentqueue -I/<>/3rdparty/alp -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT 
src/sortmerna/CMakeFiles/smr_objs.dir/ssw.c.o -MF 
CMakeFiles/smr_objs.dir/ssw.c.o.d -o CMakeFiles/smr_objs.dir/ssw.c.o -c 
/<>/src/sortmerna/ssw.c
/<>/src/sortmerna/ssw.c: In function ‘sw_sse2_byte’:
/<>/src/sortmerna/ssw.c:177:17: warning: SSE vector return without 
SSE enabled changes the ABI [-Wpsabi]
  177 | __m128i vZero = _mm_set1_epi32(0);
  | ^
In file included from /<>/src/sortmerna/ssw.c:49:
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:654:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_set1_epi8’: target specific option 
mismatch
  654 | _mm_set1_epi8 (char __A)
  | ^
/<>/src/sortmerna/ssw.c:192:25: note: called from here
  192 | __m128i vBias = _mm_set1_epi8(bias);
  | ^~~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:654:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_set1_epi8’: target specific option 
mismatch
  654 | _mm_set1_epi8 (char __A)
  | ^
/<>/src/sortmerna/ssw.c:189:25: note: called from here
  189 | __m128i vGapE = _mm_set1_epi8(weight_gapE);
  | ^~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:654:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_set1_epi8’: target specific option 
mismatch
  654 | _mm_set1_epi8 (char __A)
  | ^
/<>/src/sortmerna/ssw.c:186:25: note: called from here
  186 | __m128i vGapO = _mm_set1_epi8(weight_gapO);
  | ^~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:642:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_set1_epi32’: target specific option 
mismatch
  642 | _mm_set1_epi32 (int __A)
  | ^~
/<>/src/sortmerna/ssw.c:177:25: note: called from here
  177 | __m128i vZero = _mm_set1_epi32(0);
  | ^
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:1227:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_slli_si128’: target specific option 
mismatch
 1227 | _mm_slli_si128 (__m128i __A, const int __N)
  | ^~
/<>/src/sortmerna/ssw.c:217:22: note: called from here
  217 | vH = _mm_slli_si128(vH, 1); /* Shift the 128-bit value 
in vH left by 1 byte. */
  |  ^
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:695:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_load_si128’: target specific option 
mismatch
  695 | _mm_load_si128 (__m128i const *__P)
  | ^~
/<>/src/sortmerna/ssw.c:259:30: note: called from here
  259 | vH = _mm_load_si128(pvHLoad + j);
  |  ^~~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:1413:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_max_epu8’: target specific option 
mismatch
 1413 | _mm_max_epu8 (__m128i __A, __m128i __B)
  | ^~~~
/<>/src/sortmerna/ssw.c:256:30: note: called from here
  256 | vF = _mm_max_epu8(vF, vH);
  |  ^~~~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:1136:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_subs_epu8’: target specific option 
mismatch
 1136 | _mm_subs_epu8 (__m128i __A, __m128i __B)
  | ^
/<>/src/sortmerna/ssw.c:255:30: note: called from here
  255 | vF = _mm_subs_epu8(vF, vGapE);
  |  ^~~~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:

Bug#1028142: dlocate: cannot find recent files - obsolete database?

[Vincent Lefevre]

On 2023-01-07 19:48:17 +0100, Vincent Lefevre wrote:
> In the logs I can see for today:
> 
> Jan 07 06:25:01 zira CRON[1843444]: (root) CMD (test -x /usr/sbin/anacron || 
> { cd / && run-parts --report /etc/cron.daily; })
> 
> and
> 
> Jan 07 14:38:01 zira CRON[1857920]: (root) CMD (   test -x 
> /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
> --crond)
> 
> So it seems to be OK, though I don't know what leads to the logging
> of popularity-contest only.

This is actually because of /etc/cron.d.

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

Bug#1028142: dlocate: cannot find recent files - obsolete database?

[Sven Joachim]

On 2023-01-07 19:48 +0100, Vincent Lefevre wrote:

> On 2023-01-07 19:20:56 +0100, Sven Joachim wrote:
>> On 2023-01-07 18:53 +0100, Vincent Lefevre wrote:
>> > zira:~> ll /var/lib/dlocate
>> > total 109172
>> > -rw-r--r-- 1 root root 55750318 2022-11-25 00:27:44 dlocatedb
>> > -rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old
>> > -rw-r--r-- 1 root root   105318 2022-11-25 00:27:44 dlocatedb.stamps
>> > -rw-r--r-- 1 root root   299199 2022-11-25 00:27:44 dpkg-list
>
> Same issue my other machine.
>
>> That could have been the case for much longer actually.  At installation
>> time, the postinst script runs "update-dlocatedb -b" which seems to have
>> been successful.
>
> I suppose that explains the
>
>> > -rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old
>
>> > The cron file /etc/cron.daily/dlocate is there, though:
>> >
>> > #!/bin/sh
>> >
>> > # update databases for both files and packages.
>> > if [ -x /usr/sbin/update-dlocatedb ] ; then
>> >   /usr/sbin/update-dlocatedb -b
>> > fi
>>
>> But apparently it is never executed.  Are any other cron jobs being run
>> on your system?
>
> In the logs I can see for today:
>
> Jan 07 06:25:01 zira CRON[1843444]: (root) CMD (test -x
> /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.daily; })
>
> and
>
> Jan 07 14:38:01 zira CRON[1857920]: (root) CMD ( test -x
> /etc/cron.daily/popularity-contest &&
> /etc/cron.daily/popularity-contest --crond)
>
> So it seems to be OK, though I don't know what leads to the logging
> of popularity-contest only.

Most likely the script /etc/cron.d/popularity-contest, I get the same
messages.

>> If not, you may have been bitten by bug #1019554 in
>> anacron which needs manual restore as mentioned in
>> https://lists.debian.org/debian-devel-announce/2022/11/msg1.html.
>
> 2022-07-14 20:57:59 upgrade anacron:amd64 2.3-32 2.3-33
> 2022-07-14 20:57:59 status half-configured anacron:amd64 2.3-32
> 2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-32
> 2022-07-14 20:57:59 status half-installed anacron:amd64 2.3-32
> 2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-33

Note that the anacron bug only makes itself apparent after the upgrade
to a later version, since that would run the faulty postrm from 2.3-33.

> but I get mail from failing cron scripts.

What does "systemctl status anacron.service" print?

Cheers,
   Sven

Bug#1028146: collectd FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: collectd
Version: 5.12.0-11
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/collectd.html

...
In file included from src/python.c:36:
src/cpython.h:29:10: fatal error: longintrepr.h: No such file or directory
   29 | #include 
  |  ^~~
compilation terminated.
make[2]: *** [Makefile:8457: src/python_la-python.lo] Error 1

Bug#984211: marked as done (libwibble: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 19:29:23 +
with message-id 
and subject line Bug#984211: fixed in libwibble 1.1-3
has caused the Debian Bug report #984211,
regarding libwibble: 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.)


-- 
984211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libwibble
Version: 1.1-2
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/libwibble_1.1-2_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.

[...]
make  -f wibble/CMakeFiles/wibble.dir/build.make 
wibble/CMakeFiles/wibble.dir/build
make[4]: Entering directory '/<>/debian/build'
[  1%] Building CXX object wibble/CMakeFiles/wibble.dir/exception.o
[  2%] Building CXX object wibble/CMakeFiles/wibble.dir/string.o
[  3%] Building CXX object wibble/CMakeFiles/wibble.dir/regexp.o
cd /<>/debian/build/wibble && /usr/bin/c++ -DHAVE_CONFIG_H -DPOSIX 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I/<>/wibble/.. 
-I/<>/debian/build/wibble/.. -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o 
CMakeFiles/wibble.dir/exception.o -c /<>/wibble/exception.cpp
cd /<>/debian/build/wibble && /usr/bin/c++ -DHAVE_CONFIG_H -DPOSIX 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I/<>/wibble/.. 
-I/<>/debian/build/wibble/.. -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o 
CMakeFiles/wibble.dir/string.o -c /<>/wibble/string.cpp
cd /<>/debian/build/wibble && /usr/bin/c++ -DHAVE_CONFIG_H -DPOSIX 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I/<>/wibble/.. 
-I/<>/debian/build/wibble/.. -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o 
CMakeFiles/wibble.dir/regexp.o -c /<>/wibble/regexp.cpp
[  4%] Building CXX object wibble/CMakeFiles/wibble.dir/test.o
cd /<>/debian/build/wibble && /usr/bin/c++ -DHAVE_CONFIG_H -DPOSIX 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I/<>/wibble/.. 
-I/<>/debian/build/wibble/.. -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o 
CMakeFiles/wibble.dir/test.o -c /<>/wibble/test.cpp
In file included from /<>/wibble/regexp.cpp:21:
/<>/wibble/../wibble/regexp.h:66:77: error: ISO C++17 does not 
allow dynamic exception specifications
   66 | Regexp(const std::string& expr, int match_count = 0, int flags 
= 0) throw (wibble::exception::Regexp);
  | 
^
/<>/wibble/../wibble/regexp.h:69:59: error: ISO C++17 does not 
allow dynamic exception specifications
   69 | bool match(const std::string& str, int flags = 0) throw 
(wibble::exception::Regexp);
  |   ^
/<>/wibble/../wibble/regexp.h:75:41: error: ISO C++17 does not 
allow dynamic exception specifications
   75 | std::string operator[](int idx) throw 
(wibble::except

Bug#1028148: celery FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: celery
Version: 5.2.6-4
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/celery.html

...
   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/1st/celery-5.2.6'
PYTHONPATH=. python3 -m sphinx -b html -d docs/.build/.doctrees -N docs 
/build/1st/celery-5.2.6/debian/python-celery-doc/usr/share/doc/python-celery-doc/html
Running Sphinx v5.3.0

Extension error:
Could not import extension celery.contrib.sphinx (exception: cannot import name 
'formatargspec' from 'inspect' (/usr/lib/python3.11/inspect.py))
make[1]: *** [debian/rules:21: override_dh_sphinxdoc] Error 2

Bug#1013894: findutils: d/copyright: Missing licenses

[Bastian Germann]

Hi Andreas,

Any news on this? The freeze is nearing.

Thanks,
Bastian

Bug#1027025: marked as done (psi4: FTBFS with Python 3.11 as default version)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 19:40:55 +
with message-id 
and subject line Bug#1027025: fixed in psi4 1:1.3.2+dfsg-4
has caused the Debian Bug report #1027025,
regarding psi4: FTBFS with Python 3.11 as default version
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.)


-- 
1027025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: psi4
Version: 1:1.3.2+dfsg-3
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.11

Hi Maintainer

Psi4 fails its build-time tests with Python 3.11 as the default
version, although the build doesn't fail outright, probably because of
the following in debian/rules:

override_dh_auto_test:
mkdir -p $(CURDIR)/builddir/tmp-scratch
-(cd builddir/tests; CTEST_OUTPUT_ON_FAILURE=TRUE ctest -L quicktests)

I've copied what I hope is the relevant part of the log below.

Regards
Graham


Traceback (most recent call last):
  File "/<>/builddir/stage/bin/psi4", line 177, in 
import psi4
  File "/<>/builddir/stage/lib/x86_64-linux-gnu/psi4/__init__.py",
line 60, in 
raise ImportError("{0}".format(err))
ImportError: cannot import name 'core' from partially initialized
module 'psi4' (most likely due to a circular import)
(/<>/builddir/stage/lib/x86_64-linux-gnu/psi4/__init__.py)
Exit Status: infile ( 1 ); autotest ( None ); sowreap ( None ); overall ( 1 )


0% tests passed, 143 tests failed out of 143
--- End Message ---
--- Begin Message ---
Source: psi4
Source-Version: 1:1.3.2+dfsg-4
Done: Michael Banck 

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

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

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

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated psi4 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: Sat, 07 Jan 2023 19:13:25 +0100
Source: psi4
Architecture: source
Version: 1:1.3.2+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Michael Banck 
Closes: 1027025
Changes:
 psi4 (1:1.3.2+dfsg-4) unstable; urgency=medium
 .
   [ James Addison ]
   * debian/patches/cmake_pymodulesuffix.patch: New patch, fixes runtime errors
 with Python 3.11 (Closes: #1027025).
 .
   [ Michael Banck ]
   * debian/watch: Updated.
Checksums-Sha1:
 35c81d7cafc354f700caf3330dcbd866ec529c21 2367 psi4_1.3.2+dfsg-4.dsc
 fc57dbe423278ae59284cbaba8eab44ae4b5b203 16216 psi4_1.3.2+dfsg-4.debian.tar.xz
 04f52d5686f960031c8aa43e15bc5c98a76769ae 9003 
psi4_1.3.2+dfsg-4_source.buildinfo
Checksums-Sha256:
 6d4d20a2bc00ebe1223ef0a20584879c80365432b69aa094d1360f85074f37bb 2367 
psi4_1.3.2+dfsg-4.dsc
 47917d9a64c568e6457b497bc37b3e7feba3ed9d9e47007489264d164bfd3bc8 16216 
psi4_1.3.2+dfsg-4.debian.tar.xz
 1ece928ff7a9d2396eff9e0bdd7bded96084f81e8ae30b08fabd3d98a946a678 9003 
psi4_1.3.2+dfsg-4_source.buildinfo
Files:
 2781e64f3a8138a138c40119a64c760c 2367 science optional psi4_1.3.2+dfsg-4.dsc
 8a9dc83d33a485a023baa22a29ffecad 16216 science optional 
psi4_1.3.2+dfsg-4.debian.tar.xz
 d9e55ff48b05784099ee91775cedf4de 9003 science optional 
psi4_1.3.2+dfsg-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEnKh3dJ+rLk+paGLs3GhqJ7Q0gbAFAmO5tlUACgkQ3GhqJ7Q0
gbCjyw/9H3THATwCApNFI/1R95KpHWCRt2Qgb4HAnH9SdBVtqDyzB/SZ/BGYpUZW
3BO/piK+Ax3Nc99y2ZnmUz3fXKqazkxyNNQgoWgxui2dma/GB618EszRcwr2MCn2
QkZOymwbreAyzX4W9P+9ajXY2Q9A6mhX7fc9MxOtWhuyVRtKPWq9JOz9qGcufMUD
kYFxVaSRrweIGThcJh8a2zCnSSW3nYFTwg8OF2GKMNAImK0/XUrk8/yDCxN3DCyW
WRLuFAOGCaRUuj8kHDJlEFWwuIEq1I4jkggSyBMbXFhVXwJLcGhJCc4z1OH6SmFH
ogCZy8/YiEzXOnWkBU+CKgV7YGJShcYwL8uzyzbAJ25QkmWwOwqRbei/lDyc/viy
jXqW548hICPcQ+Bkl7ACooKXrvEn52mvWtTglTK3zxw64UNrbcE6YVH+h4wFDokp
QYAow7d81348qObkuhwLObuuoBgk0fxZ50c+2rrW5FwUyj/Hrm4s+7sFlxHg1sq+
vkkKsah/SsOj5XnxM3qI0IaRv3vX7OaNlQ1boBvIzJ0BuHVqqwPSVFfLGMykHrIm
G0UpslQJbGFS5FEXIo99WgT/xSj991pwBEsyg4FzHUURUjl+eNMGk7MPPspUD+j0
jfRYgtKz8/cvyKHidND8l+XG7fDXkZYibh1PXdFTEUTPnDtFFzA=
=hh7o
-END PGP SIGNATURE End Message ---

Processed: Bug#1026647 marked as pending in trapperkeeper-metrics-clojure

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026647 [src:trapperkeeper-metrics-clojure] trapperkeeper-metrics-clojure: 
FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1
Added tag(s) pending.

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

Bug#1026647: marked as pending in trapperkeeper-metrics-clojure

[Louis-Philippe Véronneau]

Control: tag -1 pending

Hello,

Bug #1026647 in trapperkeeper-metrics-clojure 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/clojure-team/trapperkeeper-metrics-clojure/-/commit/c5cdb37f1844117c009bb8e3cfe44bd7ca3f0c4a


d/patches/0001: remove Java version restriction. (Closes: #1026647)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026647

Bug#1028110: marked as pending in php-horde-lz4

[Anton Gladky]

Control: tag -1 pending

Hello,

Bug #1028110 in php-horde-lz4 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/horde-team/php-horde-lz4/-/commit/4e5ab4940daf5cfd1dd92529ad02f634b4e3234a


d/t/control: add php-dom. (Closes: #1028110)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028110

Processed: Bug#1028110 marked as pending in php-horde-lz4

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028110 [src:php-horde-lz4] php-horde-lz4: autopkgtest failure
Added tag(s) pending.

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

Bug#1028152: golang-github-likexian-gokit FTBFS: chown tmp: operation not permitted

[Adrian Bunk]

Source: golang-github-likexian-gokit
Version: 0.25.6-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=golang-github-likexian-gokit&arch=all

...
FAILgithub.com/likexian/gokit/xdaemon   0.012s
...
assert.go:197: 
/<>/obj-x86_64-linux-gnu/src/github.com/likexian/gokit/xfile/xfile_test.go:155
assert.go:170: ! unexpected error: "chown tmp: operation not permitted"
...

Bug#1026527: marked as done (hiro: FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec')

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 21:09:43 +
with message-id 
and subject line Bug#1026527: fixed in hiro 0.5.1-2
has caused the Debian Bug report #1026527,
regarding hiro: FTBFS: AttributeError: module 'inspect' has no attribute 
'getargspec'
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3.11 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_hiro/build/hiro
> copying hiro/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_hiro/build/hiro
> copying hiro/core.py -> 
> /<>/.pybuild/cpython3_3.11_hiro/build/hiro
> copying hiro/errors.py -> 
> /<>/.pybuild/cpython3_3.11_hiro/build/hiro
> copying hiro/version.py -> 
> /<>/.pybuild/cpython3_3.11_hiro/build/hiro
> copying hiro/patches.py -> 
> /<>/.pybuild/cpython3_3.11_hiro/build/hiro
> copying hiro/utils.py -> 
> /<>/.pybuild/cpython3_3.11_hiro/build/hiro
> running egg_info
> creating hiro.egg-info
> writing hiro.egg-info/PKG-INFO
> writing dependency_links to hiro.egg-info/dependency_links.txt
> writing requirements to hiro.egg-info/requires.txt
> writing top-level names to hiro.egg-info/top_level.txt
> writing manifest file 'hiro.egg-info/SOURCES.txt'
> reading manifest file 'hiro.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'hiro.egg-info/SOURCES.txt'
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_hiro/build/hiro
> copying hiro/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_hiro/build/hiro
> copying hiro/core.py -> 
> /<>/.pybuild/cpython3_3.10_hiro/build/hiro
> copying hiro/errors.py -> 
> /<>/.pybuild/cpython3_3.10_hiro/build/hiro
> copying hiro/version.py -> 
> /<>/.pybuild/cpython3_3.10_hiro/build/hiro
> copying hiro/patches.py -> 
> /<>/.pybuild/cpython3_3.10_hiro/build/hiro
> copying hiro/utils.py -> 
> /<>/.pybuild/cpython3_3.10_hiro/build/hiro
> running egg_info
> writing hiro.egg-info/PKG-INFO
> writing dependency_links to hiro.egg-info/dependency_links.txt
> writing requirements to hiro.egg-info/requires.txt
> writing top-level names to hiro.egg-info/top_level.txt
> reading manifest file 'hiro.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'hiro.egg-info/SOURCES.txt'
> PYTHONPATH=. http_proxy='127.0.0.1:9' python3 -m sphinx -N -bhtml doc/source 
> build/html
> Running Sphinx v5.3.0
> making output directory... done
> WARNING: html_static_path entry '_static' does not exist
> loading intersphinx inventory from http://docs.python.org/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'http://docs.python.org/objects.inv' not fetchable due 
> to : 
> HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url: 
> http://docs.python.org/objects.inv (Caused by ProxyError('Cannot connect to 
> proxy.', NewConnectionError(' 0x7f291a76fee0>: Failed to establish a new connection: [Errno 111] Connection 
> refused')))
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 4 source files that are out of date
> updating environment: [new config] 4 added, 0 changed, 0 removed
> reading sources... [ 25%] api
> reading sources... [ 50%] index
> reading sources... [ 75%] intro
> reading sources... [100%] project
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 25%] api
> writing output... [ 50%] index
> writing output... [ 75%] intro
> writing output... [100%] project
> 
> generating indices... genindex done
> highlighting module code... [100%] hiro.core
> 
> writing additional pages... search done
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 2 warnings.
> 
> The HTML pages are in build/html.
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pyb

Bug#984163: marked as done (guessnet: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 21:09:35 +
with message-id 
and subject line Bug#984163: fixed in guessnet 0.58
has caused the Debian Bug report #984163,
regarding guessnet: 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.)


-- 
984163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:guessnet
Version: 0.56
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/guessnet_0.56_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.

[...]
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for unistd.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking whether byte ordering is bigendian... no
checking whether gcc and cc understand -c and -o together... yes
checking for ranlib... ranlib
checking for flex... no
checking for lex... no
checking for bison... no
checking for byacc... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for LIBWIBBLE... yes
checking for libnet-config... /usr/bin/libnet-config
checking for libnet libraries... found
checking pcap.h usability... yes
checking pcap.h presence... yes
checking for pcap.h... yes
checking for pcap_open_live in -lpcap... yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking for pthread_create in -lpthread... yes
checking for iw_scan in -liw... yes
checking for sh... /bin/sh
checking for ifconfig... /sbin/ifconfig
checking for grep... (cached) /bin/grep
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating scripts/Makefile
config.status: creating tests/Makefile
config.status: creating config.h
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-maintainer-mode, 
--disable-silent-rules
touch debian/stamp-autotools
/usr/bin/make -C . 
make[1]: Entering directory '/<>'
/usr/bin/make  all-recursive
make[2]: Entering directory '/<>'
Making all in src
make[3]: Entering directory '/<>/src'
g++ -DHAVE_CONFIG_H -I. -I.. -D_BSD_SOURCE -D__BSD_SOURCE -D__FAVOR_BSD 
-DHAVE_NET_ETHERNET_H  -DSCRIPTDIR=\"/usr/share/guessnet/test\"  -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o nettypes.o 
nettypes.cc
In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
 from /usr/include/string.h:26,
 from nettypes.h:29,
 from nettypes.cc:23:
/usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
_DEFAULT_SOURCE"
  |   ^~~
In file included from nettypes.cc:23:
nettypes.h:95:43: error: ISO C++17 does not allow dynamic exception 
specifications
   95 | IPAddress(const std::string& st

Bug#1026527: marked as pending in hiro

[Carsten Schoenert]

Control: tag -1 pending

Hello,

Bug #1026527 in hiro 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/hiro/-/commit/14fdc0fcea382bda265cbbcdb9a5e5f191723896


Rebuild patche queue from patch-queue branch

Added patches:
docs-Use-local-inventory-for-intersphinx.patch
h-core.py-Use-getfullargspec-instead-of-getargspec.patch

Closes: #1026527

Renamed patches:
0001-Remove-useless-sphinx-extensions.patch
 -> docs-Remove-not-exsting-sphinx-extensions.patch
0002-Remove-external-links-from-project-docs.patch
 -> docs-Remove-external-badge-linking-from-documentation.patch


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026527

Processed: Bug#1026527 marked as pending in hiro

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026527 {Done: Carsten Schoenert } [src:hiro] 
hiro: FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec'
Added tag(s) pending.

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

Bug#1026718: [Pkg-pascal-devel] Bug#1026719: preventing lazpaint package removal

[Abou Al Montacir]

control: reassign -1 fpc
control: forcemerge -1 1026718

On Sat, 2023-01-07 at 15:31 +, Peter B wrote:
> I notice the fpc upload is closing 1026719, but not 1026718.
> 
> Maybe 1026718 needs closing manually?
I'm merging them.
-- 
Cheers,
Abou Al Montacir



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

Processed: Re: [Pkg-pascal-devel] Bug#1026719: preventing lazpaint package removal

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 fpc
Bug #1026718 [src:lazpaint] lazpaint: FTBFS: /usr/bin/ld.bfd: cannot find 
-lpangocairo-1.0: No such file or directory
Bug reassigned from package 'src:lazpaint' to 'fpc'.
No longer marked as found in versions lazpaint/7.2.2-1.
Ignoring request to alter fixed versions of bug #1026718 to the same values 
previously set
> forcemerge -1 1026718
Bug #1026718 [fpc] lazpaint: FTBFS: /usr/bin/ld.bfd: cannot find 
-lpangocairo-1.0: No such file or directory
Merged 1026718

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

Bug#1021541: marked as done (lomiri-terminal-app: ships a copy of qml-module-qmltermwidget)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 21:16:23 +
with message-id 
and subject line Bug#1021541: fixed in lomiri-terminal-app 
1.0.3~git20230107.278767e-1
has caused the Debian Bug report #1021541,
regarding lomiri-terminal-app: ships a copy of qml-module-qmltermwidget
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.)


-- 
1021541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lomiri-terminal-app
Version: 1.0.3~git20221008.b07f08a-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package lomiri-terminal-app.
  Preparing to unpack 
.../43-lomiri-terminal-app_1.0.3~git20221008.b07f08a-1_amd64.deb ...
  Unpacking lomiri-terminal-app (1.0.3~git20221008.b07f08a-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-gCsdoo/43-lomiri-terminal-app_1.0.3~git20221008.b07f08a-1_amd64.deb
 (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/QMLTermScrollbar.qml', which 
is also in package qml-module-qmltermwidget 1.2.0+ds-7
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-gCsdoo/43-lomiri-terminal-app_1.0.3~git20221008.b07f08a-1_amd64.deb

The conflicting files are

usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/QMLTermScrollbar.qml
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/BlackOnRandomLight.colorscheme
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/DarkPastels.colorscheme
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/GreenOnBlack.colorscheme
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/Linux.colorscheme
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/Ubuntu.colorscheme
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/BlackOnLightColor.schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/DarkPicture.schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/Example.Schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/GreenOnBlack.schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/GreenTint.schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/GreenTint_MC.schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/LightPicture.schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/Linux.schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/README.Schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/README.default.Schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/Transparent.schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/Transparent_MC.schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/Transparent_darkbg.schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/Transparent_lightbg.schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/XTerm.schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/syscolor.schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/color-schemes/historic/vim.schema
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/kb-layouts/default.keytab
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/kb-layouts/historic/vt100.keytab
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/kb-layouts/historic/x11r5.keytab
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/kb-layouts/linux.keytab
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/kb-layouts/macbook.keytab
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/kb-layouts/solaris.keytab
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/kb-layouts/vt420pc.keytab
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/libqmltermwidget.so
usr/lib/x86_64-linux-gnu/qt5/qml/QMLTermWidget/qmldir

Please (build-?)depend on and use the packaged copy in
qml-module-qmltermwidget instead.


cheers,

Andreas


qml-module-qmltermwidget=1.2.0+ds-7_lomiri-terminal-app=1.0.3~git20221008.b07f08a-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lomiri-terminal-app
Source-Version: 1.0.3~git20230107.278767e-1
Done: Marius Gripsgard 

We believe that the bug you reported is fixed in the l

Processed: python3-sphinxcontrib-pecanwsme: error with Python 3.11

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:aodh
Bug #1028154 [python3-sphinxcontrib-pecanwsme] python3-sphinxcontrib-pecanwsme: 
error with Python 3.11
Added indication that 1028154 affects src:aodh

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

Bug#1028154: python3-sphinxcontrib-pecanwsme: error with Python 3.11

[Adrian Bunk]

Package: python3-sphinxcontrib-pecanwsme
Version: 0.10.0-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:aodh

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/aodh.html

...
Exception occurred:
  File "/usr/lib/python3/dist-packages/sphinxcontrib/pecanwsme/rest.py", line 
133, in make_rst_for_controller
argspec = inspect.getargspec(controller.__init__)
  ^^
AttributeError: module 'inspect' has no attribute 'getargspec'
...

Bug#1026718: [Pkg-pascal-devel] Bug#1026719: preventing lazpaint package removal

[Abou Al Montacir]

control: forcemerge 1026719 -1
-- 
Cheers,
Abou Al Montacir



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

Processed: Re: [Pkg-pascal-devel] Bug#1026719: preventing lazpaint package removal

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 1026719 -1
Bug #1026719 {Done: Abou Al Montacir } [fpc] vmg: 
FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory
Bug #1026718 [fpc] lazpaint: FTBFS: /usr/bin/ld.bfd: cannot find 
-lpangocairo-1.0: No such file or directory
Marked Bug as done
Added indication that 1026718 affects vmg
Marked as fixed in versions fpc/3.2.2+dfsg-18.
Merged 1026718 1026719

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

Bug#1026647: marked as done (trapperkeeper-metrics-clojure: FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 21:28:20 +
with message-id 
and subject line Bug#1026647: fixed in trapperkeeper-metrics-clojure 1.5.0-2
has caused the Debian Bug report #1026647,
regarding trapperkeeper-metrics-clojure: FTBFS: make[1]: *** [debian/rules:17: 
override_dh_auto_build] Error 1
to be marked as done.

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

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


-- 
1026647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trapperkeeper-metrics-clojure
Version: 1.5.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> lein pom debian/pom.xml
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> java.lang.Exception: Error loading /<>/project.clj
>  at leiningen.core.project$read_raw$fn__7638.invoke (project.clj:1046)
> leiningen.core.project$read_raw.invokeStatic (project.clj:1040)
> leiningen.core.project$read_raw.invoke (project.clj:1036)
> leiningen.core.project$read.invokeStatic (project.clj:1057)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.project$read.invokeStatic (project.clj:1058)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.main$_main$fn__7024.invoke (main.clj:447)
> leiningen.core.main$_main.invokeStatic (main.clj:442)
> leiningen.core.main$_main.doInvoke (main.clj:439)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.core$apply.invokeStatic (core.clj:667)
> clojure.main$main_opt.invokeStatic (main.clj:514)
> clojure.main$main_opt.invoke (main.clj:510)
> clojure.main$main.invokeStatic (main.clj:664)
> clojure.main$main.doInvoke (main.clj:616)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.main.main (main.java:40)
> Caused by: clojure.lang.Compiler$CompilerException: Syntax error compiling at 
> (/<>/project.clj:1:1).
> #:clojure.error{:phase :compile-syntax-check, :line 1, :column 1, :source 
> "/<>/project.clj"}
>  at clojure.lang.Compiler.load (Compiler.java:7652)
> clojure.lang.Compiler.loadFile (Compiler.java:7578)
> clojure.lang.RT$3.invoke (RT.java:327)
> leiningen.core.project$read_raw$fn__7638.invoke (project.clj:1044)
> leiningen.core.project$read_raw.invokeStatic (project.clj:1040)
> leiningen.core.project$read_raw.invoke (project.clj:1036)
> leiningen.core.project$read.invokeStatic (project.clj:1057)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.project$read.invokeStatic (project.clj:1058)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.main$_main$fn__7024.invoke (main.clj:447)
> leiningen.core.main$_main.invokeStatic (main.clj:442)
> leiningen.core.main$_main.doInvoke (main.clj:439)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.core$apply.invokeStatic (core.clj:667)
> clojure.main$main_opt.invokeStatic (main.clj:514)
> clojure.main$main_opt.invoke (main.clj:510)
> clojure.main$main.invokeStatic (main.clj:664)
> clojure.main$main.doInvoke (main.clj:616)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.main.main (main.java:40)
> Caused by: clojure.lang.ExceptionInfo: Unsupported major Java version. 
> Expects 8 or 11.
> {:major "17", :minor nil}
>  at leiningen.core.project$eval657.invokeStatic (project.clj:65)
> leiningen.core.project$eval657.invoke (project.clj:1)
> clojure.lang.Compiler.eval (Compiler.java:7181)
> clojure.lang.Compiler.load (Compiler.java:7640)
> clojure.lang.Compiler.loadFile (Compiler.java:7578)
> clojure.lang.RT$3.invoke (RT.java:327)
> leiningen.core.project$read_raw$fn__7638.invoke (project.clj:1044)
> leiningen.core.project$read_raw.invokeStatic (project.clj:1040)
> leiningen.core.project$read_raw.invoke (project.clj:1036)
> leiningen.core.project$read.invokeStatic (project.clj:1057)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.project$read.invokeStatic (project.clj:1058)
> leiningen.core.project$read.invoke (project.clj:1054)
>  

Bug#1026649: marked as done (ssl-utils-clojure: FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 21:27:55 +
with message-id 
and subject line Bug#1026649: fixed in ssl-utils-clojure 3.3.0-2
has caused the Debian Bug report #1026649,
regarding ssl-utils-clojure: FTBFS: make[1]: *** [debian/rules:17: 
override_dh_auto_build] Error 1
to be marked as done.

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

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


-- 
1026649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ssl-utils-clojure
Version: 3.3.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> lein pom debian/pom.xml
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> java.lang.Exception: Error loading /<>/project.clj
>  at leiningen.core.project$read_raw$fn__7638.invoke (project.clj:1046)
> leiningen.core.project$read_raw.invokeStatic (project.clj:1040)
> leiningen.core.project$read_raw.invoke (project.clj:1036)
> leiningen.core.project$read.invokeStatic (project.clj:1057)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.project$read.invokeStatic (project.clj:1058)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.main$_main$fn__7024.invoke (main.clj:447)
> leiningen.core.main$_main.invokeStatic (main.clj:442)
> leiningen.core.main$_main.doInvoke (main.clj:439)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.core$apply.invokeStatic (core.clj:667)
> clojure.main$main_opt.invokeStatic (main.clj:514)
> clojure.main$main_opt.invoke (main.clj:510)
> clojure.main$main.invokeStatic (main.clj:664)
> clojure.main$main.doInvoke (main.clj:616)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.main.main (main.java:40)
> Caused by: clojure.lang.Compiler$CompilerException: Syntax error compiling at 
> (/<>/project.clj:8:1).
> #:clojure.error{:phase :compile-syntax-check, :line 8, :column 1, :source 
> "/<>/project.clj"}
>  at clojure.lang.Compiler.load (Compiler.java:7652)
> clojure.lang.Compiler.loadFile (Compiler.java:7578)
> clojure.lang.RT$3.invoke (RT.java:327)
> leiningen.core.project$read_raw$fn__7638.invoke (project.clj:1044)
> leiningen.core.project$read_raw.invokeStatic (project.clj:1040)
> leiningen.core.project$read_raw.invoke (project.clj:1036)
> leiningen.core.project$read.invokeStatic (project.clj:1057)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.project$read.invokeStatic (project.clj:1058)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.main$_main$fn__7024.invoke (main.clj:447)
> leiningen.core.main$_main.invokeStatic (main.clj:442)
> leiningen.core.main$_main.doInvoke (main.clj:439)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.core$apply.invokeStatic (core.clj:667)
> clojure.main$main_opt.invokeStatic (main.clj:514)
> clojure.main$main_opt.invoke (main.clj:510)
> clojure.main$main.invokeStatic (main.clj:664)
> clojure.main$main.doInvoke (main.clj:616)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.main.main (main.java:40)
> Caused by: clojure.lang.ExceptionInfo: Unsupported major Java version. 
> Expects 8 or 11.
> {:major "17", :minor nil}
>  at leiningen.core.project$eval658.invokeStatic (project.clj:59)
> leiningen.core.project$eval658.invoke (project.clj:8)
> clojure.lang.Compiler.eval (Compiler.java:7181)
> clojure.lang.Compiler.load (Compiler.java:7640)
> clojure.lang.Compiler.loadFile (Compiler.java:7578)
> clojure.lang.RT$3.invoke (RT.java:327)
> leiningen.core.project$read_raw$fn__7638.invoke (project.clj:1044)
> leiningen.core.project$read_raw.invokeStatic (project.clj:1040)
> leiningen.core.project$read_raw.invoke (project.clj:1036)
> leiningen.core.project$read.invokeStatic (project.clj:1057)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.project$read.invokeStatic (project.clj:1058)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.main$_main$fn__702

Bug#1028122: marked as done (sortmerna: FTBFS on i386)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 21:26:39 +
with message-id 
and subject line Bug#1028122: fixed in rnahybrid 2.1.2-7
has caused the Debian Bug report #1028122,
regarding sortmerna: FTBFS on i386
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=sortmerna&arch=i386&ver=4.3.6-1&stamp=1673038926&raw=0

cd /<>/obj-i686-linux-gnu/src/sortmerna && /usr/bin/cc  
-I/<>/include -I/<>/3rdparty/cmph 
-I/<>/3rdparty/concurrentqueue -I/<>/3rdparty/alp -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT 
src/sortmerna/CMakeFiles/smr_objs.dir/ssw.c.o -MF 
CMakeFiles/smr_objs.dir/ssw.c.o.d -o CMakeFiles/smr_objs.dir/ssw.c.o -c 
/<>/src/sortmerna/ssw.c
/<>/src/sortmerna/ssw.c: In function ‘sw_sse2_byte’:
/<>/src/sortmerna/ssw.c:177:17: warning: SSE vector return without 
SSE enabled changes the ABI [-Wpsabi]
  177 | __m128i vZero = _mm_set1_epi32(0);
  | ^
In file included from /<>/src/sortmerna/ssw.c:49:
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:654:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_set1_epi8’: target specific option 
mismatch
  654 | _mm_set1_epi8 (char __A)
  | ^
/<>/src/sortmerna/ssw.c:192:25: note: called from here
  192 | __m128i vBias = _mm_set1_epi8(bias);
  | ^~~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:654:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_set1_epi8’: target specific option 
mismatch
  654 | _mm_set1_epi8 (char __A)
  | ^
/<>/src/sortmerna/ssw.c:189:25: note: called from here
  189 | __m128i vGapE = _mm_set1_epi8(weight_gapE);
  | ^~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:654:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_set1_epi8’: target specific option 
mismatch
  654 | _mm_set1_epi8 (char __A)
  | ^
/<>/src/sortmerna/ssw.c:186:25: note: called from here
  186 | __m128i vGapO = _mm_set1_epi8(weight_gapO);
  | ^~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:642:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_set1_epi32’: target specific option 
mismatch
  642 | _mm_set1_epi32 (int __A)
  | ^~
/<>/src/sortmerna/ssw.c:177:25: note: called from here
  177 | __m128i vZero = _mm_set1_epi32(0);
  | ^
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:1227:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_slli_si128’: target specific option 
mismatch
 1227 | _mm_slli_si128 (__m128i __A, const int __N)
  | ^~
/<>/src/sortmerna/ssw.c:217:22: note: called from here
  217 | vH = _mm_slli_si128(vH, 1); /* Shift the 128-bit value 
in vH left by 1 byte. */
  |  ^
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:695:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_load_si128’: target specific option 
mismatch
  695 | _mm_load_si128 (__m128i const *__P)
  | ^~
/<>/src/sortmerna/ssw.c:259:30: note: called from here
  259 | vH = _mm_load_si128(pvHLoad + j);
  |  ^~~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:1413:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_max_epu8’: target specific option 
mismatch
 1413 | _mm_max_epu8 (__m128i __A, __m128i __B)
  | ^~~~
/<>/src/sortmerna/ssw.c:256:30: note: called from here
  256 | vF = _mm_max_epu8(vF, vH);
  |  ^~~~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:1136:1: error: inlining 
failed in call to ‘always_inline’ ‘_mm_subs_epu8’: target specific option 
mismatch
 1136 | _mm_subs_epu8 (__m128i __A, __m128i __B)
  | ^
/<>/src/sortmerna/ssw.c:255:30: note: called from here
  255 | vF = _mm_subs_epu8(vF, vGapE);
  |  ^~~~
/usr/lib/gcc/i686-linux-gnu/12/include/emmintrin.h:

Bug#1004784: aiscm: FTBFS with ffmpeg 5.0

[Jan Wedekind]

Not sure how to orphan it. I read that I need to change the package 
maintainer to Debian QA Group but I can't create a new release any more 
since it won't build on Debian unstable because of FFPMEG 5.0 changes.


On Wed, 14 Dec 2022, Bastian Germann wrote:


Am 14.12.22 um 16:51 schrieb Jan Wedekind:

No, I didn't manage to fix it. Is it possible to remove the package?


Yes. But if you do not want to maintain it anymore, orphaning would usually 
the step that maintainers take.

Bug#1028110: marked as done (php-horde-lz4: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 21:54:00 +
with message-id 
and subject line Bug#1028110: fixed in php-horde-lz4 1.0.10-10
has caused the Debian Bug report #1028110,
regarding php-horde-lz4: autopkgtest failure
to be marked as done.

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

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


-- 
1028110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-horde-lz4
Version: 1.0.10-9
Severity: serious

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

...
autopkgtest [03:59:01]: test phpunit: [---
PHPUnit requires the "dom" extension.
autopkgtest [03:59:02]: test phpunit: ---]
autopkgtest [03:59:02]: test phpunit:  - - - - - - - - - - results - - - - - - 
- - - -
phpunit  FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: php-horde-lz4
Source-Version: 1.0.10-10
Done: Anton Gladky 

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated php-horde-lz4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Jan 2023 22:01:37 +0100
Source: php-horde-lz4
Architecture: source
Version: 1.0.10-10
Distribution: unstable
Urgency: medium
Maintainer: Horde Maintainers 
Changed-By: Anton Gladky 
Closes: 1028110
Changes:
 php-horde-lz4 (1.0.10-10) unstable; urgency=medium
 .
   * Team upload.
   * d/t/control: add php-dom. (Closes: #1028110)
Checksums-Sha1:
 186e751a63e998bc122095a4fdc0abbe64a83aa3 2125 php-horde-lz4_1.0.10-10.dsc
 b55d823930878e14a24460d62fe46c77c79ef8d8 5756 
php-horde-lz4_1.0.10-10.debian.tar.xz
 1092c94827d18465fdbad956945507eb639b64b0 7194 
php-horde-lz4_1.0.10-10_source.buildinfo
Checksums-Sha256:
 53644971522ebc574309d0246a90d4109abbd8260d0709cd8f8624f2c2eb33d9 2125 
php-horde-lz4_1.0.10-10.dsc
 83a35812d1ec0c0f80dab32a771aaa6378a4681e992e80da0d6cef8aa0f9207c 5756 
php-horde-lz4_1.0.10-10.debian.tar.xz
 b6d9f06062adc5c01381fc2ee97b2ed14dc7140ac071f876ff2a1daadaa5326f 7194 
php-horde-lz4_1.0.10-10_source.buildinfo
Files:
 5d4018e8c618cb5876012cbdc0fced65 2125 php optional php-horde-lz4_1.0.10-10.dsc
 f45b35ac4ae082bfffe4db23c76947db 5756 php optional 
php-horde-lz4_1.0.10-10.debian.tar.xz
 8b9cb6d5ab059644c7cdfc80c9f67759 7194 php optional 
php-horde-lz4_1.0.10-10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmO53tUACgkQ0+Fzg8+n
/wZDDw//QujYdg1dye3xWHJNyUVPEkKOg7h7Q7xBEfYcR6qDja29T8L3TsNbzXvt
YYUK0QIMrP8nsu3kVgjaeTwkWuPKHZWuT99hMGsnCqFWCPOV0BVmN8DRiXY6h2M/
WkDTdsqFwBT0uvOvNrawVHYaFOULfGRG2pESDaa7wuWYre5kfqZfG6n19Ee/HW8X
ZT4STyvmRznDtDGTo+2YnbtlBpPStobyldmuczQxfb+fGc6a4WVEtPD4l0cYJsEQ
phwnGP8JXtwZofoHfUa09Q8j3YZpYzPEiIcUJzxeJACihlqyei8CBQkOlT08gs5+
s+BVqOllvKhT3s6rxVBaGXaBjZ4rqlaR9zwXez/J9dzA21Z1Eji5R17QRP6TNgKL
AOp7QQ023b5xF2Lwqs2zLlkcAdvRTH193dTJreR57+6AiiYZnd31Td2bLy6E1Ho8
f/P5JhhmTlutBY1OA8rn4uHpha5BDCkcn7vAeDYv/BU40ARsJVfz+2VVK4MJAfUr
EaKgSAwAWkb8eoh83rIBnjX8jHT3V4T3moCMfy9H2EL/ZK18/ofo+imoA/9Z7beM
vYuryAOdR/8Mcsm4LiywXL4fdkG8xDNn/mG0kJ+YODRZRNFzvpIawWqwZRxPZsMY
DjQQBrBQ79s0bc6PgeK563U8uFWDJXkW4ZJxYdVUlim55jwVa5A=
=o+us
-END PGP SIGNATURE End Message ---

Bug#1027952: pcre2 causes crashes in link-grammar

[Matthew Vernon]

Hi,

I'm struggling a bit here; I wanted to try and bisect pcre2 upstream 
commits to see where this bug might have been introduced (or get to the 
bottom of what link-grammar's test is doing wrong, I see they've been 
troublesome in the past cf #975696).


I took unstable's link-grammar source, and built it thus:

./autogen.sh
#the python test fails for some reason
./configure --disable-python-bindings --disable-java-bindings
make
make check

I then cloned pcre2 upstream, checked out pcre2-10.42
./autogen.sh
./configure --prefix=/home/matthew/junk/pcre2bug/install
make
make install

Then I go back to my link-grammar tree and do
cd tests
LD_LIBRARY_PATH=/home/matthew/junk/pcre2bug/install/lib make check

which works

similarly
LD_LIBRARY_PATH=/home/matthew/junk/pcre2bug/install/lib ./multi-thread

works

With a slightly horrible hack:
lsof -p $(ps waux | grep multi-thread | grep pcre | cut -f 4 -d ' ')

I can confirm the running multi-thread test is definitely running my 
locally-built (and thus 10.42) pcre2 library.


...so I'm not currently able to reproduce this in any way that might 
help me track down what if anything in pcre2 changed. And I'm not sure 
upstream would be very happy with "this test suite from another package 
now fails in Debian CI" as a bug report...


Regards,

Matthew

Bug#1027913: marked as pending in howardhinnant-date

[Andrea Pappacoda]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/howardhinnant-date/-/commit/b8e4338b25d9ac5ace44ed6797cbd1bf77cbf51d


d/control: depend on tzdata

Closes: #1027913


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1027913

Processed: Bug#1027913 marked as pending in howardhinnant-date

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1027913 [howardhinnant-date] howardhinnant-date must runtime-depend on 
tzdata
Added tag(s) pending.

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

Bug#1028163: sshfs-fuse: FTBFS in bullseye (tries to use the ssh service from the host machine)

[Santiago Vila]

Package: src:sshfs-fuse
Version: 3.7.1+repack-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary-arch
dh binary-arch --buildsystem=meson
   dh_update_autotools_config -a -O--buildsystem=meson
   dh_autoreconf -a -O--buildsystem=meson
   dh_auto_configure -a -O--buildsystem=meson
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu
The Meson build system
Version: 0.56.2
Source dir: /<>
Build dir: /<>/obj-x86_64-linux-gnu
Build type: native build
Project name: sshfs
Project version: 3.7.1
Using 'CFLAGS' from environment with value: '-g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security'
Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now'
Using 'CPPFLAGS' from environment with value: '-Wdate-time -D_FORTIFY_SOURCE=2'
C compiler for the host machine: cc (gcc 10.2.1 "cc (Debian 10.2.1-6) 10.2.1 
20210110")
C linker for the host machine: cc ld.bfd 2.35.2
Using 'CFLAGS' from environment with value: '-g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security'
Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now'
Using 'CPPFLAGS' from environment with value: '-Wdate-time -D_FORTIFY_SOURCE=2'
Host machine cpu family: x86_64
Host machine cpu: x86_64
../meson.build:8: WARNING: Consider using the built-in warning_level option instead of 
using "-Wall".
../meson.build:8: WARNING: Consider using the built-in warning_level option instead of 
using "-Wextra".
Message: Compiler warns about unused result even when casting to void
Program rst2man found: YES (/usr/bin/rst2man)
Configuring config.h using configuration
Found pkg-config: /usr/bin/pkg-config (0.29.2)
Run-time dependency fuse3 found: YES 3.10.3
Run-time dependency glib-2.0 found: YES 2.66.8
Run-time dependency gthread-2.0 found: YES 2.66.8
Program utils/install_helper.sh found: YES 
(/<>/utils/install_helper.sh)
Build targets in project: 4

Option buildtype is: plain [default: debugoptimized]
Found ninja-1.10.1 at /usr/bin/ninja
   dh_auto_build -a -O--buildsystem=meson
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 -v
[1/7] cc -Isshfs.p -I. -I.. -I/usr/include/fuse3 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -D_REENTRANT -DHAVE_CONFIG_H -Wall -Wextra 
-Wno-sign-compare -Wmissing-declarations -Wwrite-strings -Wno-unused-result -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DFUSE_USE_VERSION=31 -MD 
-MQ sshfs.p/sshfs.c.o -MF sshfs.p/sshfs.c.o.d -o sshfs.p/sshfs.c.o -c ../sshfs.c
[2/7] cc -Isshfs.p -I. -I.. -I/usr/include/fuse3 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -D_REENTRANT -DHAVE_CONFIG_H -Wall -Wextra 
-Wno-sign-compare -Wmissing-declarations -Wwrite-strings -Wno-unused-result -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DFUSE_USE_VERSION=31 -MD 
-MQ sshfs.p/cache.c.o -MF sshfs.p/cache.c.o.d -o sshfs.p/cache.c.o -c ../cache.c
[3/7] cc  -o sshfs sshfs.p/sshfs.c.o sshfs.p/cache.c.o -Wl,--as-needed -Wl,--no-undefined 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,--start-group 
/usr/lib/x86_64-linux-gnu/libfuse3.so -lpthread /usr/lib/x86_64-linux-gnu/libglib-2.0.so 
/usr/lib/x86_64-linux-gnu/libgthread-2.0.so -Wl,--end-group -pthread
[4/7] /usr/bin/rst2man ../sshfs.rst sshfs.1
[5/7] cp -fPp ../test/conftest.py ../test/pytest.ini ../test/test_sshfs.py ../test/util.py 
/<>/obj-x86_64-linux-gnu/test
[6/7] cc -Itest/wrong_command.p -Itest -I../test -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -D_REENTRANT -DHAVE_CONFIG_H -Wall -Wextra 
-Wno-sign-compare -Wmissing-declarations -Wwrite-strings -Wno-unused-result -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ 
test/wrong_command.p/wrong_command.c.o -MF test/wrong_command.p/wrong_command.c.o.d -o 
test/wrong_command.p/wrong_command.c.o -c ../test/wrong_command.c
[7/7] cc  -o test/wrong_command test/wrong_command.p/wrong_command.c.o -Wl,--as-needed 
-Wl,--no-undefined -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
python3 -m pytest test/
= test session starts 

Bug#1028104: libboost-dev: Boost with C++20 uses unavailable std functions

[Andreas Beckmann]

Followup-For: Bug #1028104
Control: tag -1 sid bookworm experimental
Control: close -1 1.81.0.1~exp1

This happens with g++-12 but not with g++-11.
It is fixed in the boost version in experimental.


Andreas

Processed: Re: libboost-dev: Boost with C++20 uses unavailable std functions

[Debian Bug Tracking System]

Processing control commands:

> tag -1 sid bookworm experimental
Bug #1028104 [libboost-dev] libboost-dev: Boost with C++20 uses unavailable std 
functions
Added tag(s) experimental, sid, and bookworm.
> close -1 1.81.0.1~exp1
Bug #1028104 [libboost-dev] libboost-dev: Boost with C++20 uses unavailable std 
functions
Marked as fixed in versions boost-defaults/1.81.0.1~exp1.
Bug #1028104 [libboost-dev] libboost-dev: Boost with C++20 uses unavailable std 
functions
Marked Bug as done

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

Bug#1027506: Status of mozillavpn in Debian

[Richard B. Kreckel]

Could we just upgrade to version 1.12.0 for sid/bookworm, please?

Right now, the mozillavpn package is slated for removal from bookworm. I 
would be very happy if we could avoid this.


After some tinkering, I got v1.12.0 to work on sid/bookworm. Here's what 
it takes:


1) Create mozillavpn_2.12.0.orig.tar.gz
   a) download 
https://github.com/mozilla-mobile/mozilla-vpn-client/archive/refs/tags/v2.12.0.tar.gz
   b) unpack it (and discover that directories under 3rdparty/ subdir 
are empty)
   c) drop the contents of 
https://github.com/mozilla/glean/archive/refs/tags/v52.0.0.tar.gz into 
3rdparty/glean/
   d) drop the contents of 
https://github.com/WireGuard/wireguard-tools/archive/refs/heads/master.zip 
into 3rdparty/wireguard-tools/


2) Based on mozillavpn_2.9.0-1.debian.tar.xz, apply some changes to 
debian/ directory:
   a) -DBUILD_TESTING=OFF to dh_auto_configure argument in debian/rules 
(without it it FTBFS trying to run some tests and that is also in 
upstream's rules file)
   d) change rm -rf debian/mozillavpn/etc/opt/chrome to rm -rf 
debian/mozillavpn/etc/opt in debian/rules so purge won't remove 
/etc/opt/ since there's nothing in there anyway
   c) Add packages python3-click and python3-jinja2 to Build-Depnds in 
debian/control (without these, it FTBFS)
   d) remove libqt6* and qt6-qpa-plugins dependencies in debian/control 
(see #1026957).


This builds for me on amd64.

An alternative to step 1) above is of course to clone from 
https://github.com/mozilla-mobile/mozilla-vpn-client.git and then git 
submodule update --init. That only adds some stuff not needed for Debian 
into the orig.tar.gz.


For the record, I've placed copies of the files at 
https://in.terlu.de/~kreckel/mozillavpn/.


Also, debian-release should be contacted because of the build failure on 
mipsel and mpis64el. It makes little sense to insist on these 
architectures if upstream doesn't care.


Please decide how to proceed and let me know if I can help in any way.

  -richard.
--
   .''`.  Richard B. Kreckel
  : :' :  
  `. `'   
`-

Bug#631280: marked as done (libphp-jpgraph: uses deprecated PHP functions)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 23:50:51 +
with message-id 
and subject line Bug#1027783: Removed package(s) from unstable
has caused the Debian Bug report #631280,
regarding libphp-jpgraph: uses deprecated PHP functions
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.)


-- 
631280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libphp-jpgraph
Version: 1.5.2-12
Severity: important

Hi,

jpgraph uses functions that have been deprecated in recent PHP releases,
like split() (see [1]). Even worse, it sets 'ERR_DEPRECATED' to true in
jpgraph.php. This is fine for development environments but should not be
done in production environments (i.e., Debian packages).

TIA,
Sebastian

[1] 

-- 
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin



signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1.5.2-13.1+rm

Dear submitter,

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

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

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

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

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

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

Bug#965677: marked as done (libphp-jpgraph: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 23:50:51 +
with message-id 
and subject line Bug#1027783: Removed package(s) from unstable
has caused the Debian Bug report #965677,
regarding libphp-jpgraph: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
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.)


-- 
965677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libphp-jpgraph
Version: 1.5.2-13
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package libphp-jpgraph uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

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

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


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

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Version: 1.5.2-13.1+rm

Dear submitter,

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

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

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

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

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

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

Bug#1027506: Status of mozillavpn in Debian

[Sylvestre Ledru]

Hello

Could you please submit a MR here ? 
https://salsa.debian.org/sylvestre/mozillavpn


I will be happy to upload it then

many thanks

Cheers

Sylvestre


Le 08/01/2023 à 00:46, Richard B. Kreckel a écrit :

Could we just upgrade to version 1.12.0 for sid/bookworm, please?

Right now, the mozillavpn package is slated for removal from bookworm. 
I would be very happy if we could avoid this.


After some tinkering, I got v1.12.0 to work on sid/bookworm. Here's 
what it takes:


1) Create mozillavpn_2.12.0.orig.tar.gz
   a) download 
https://github.com/mozilla-mobile/mozilla-vpn-client/archive/refs/tags/v2.12.0.tar.gz
   b) unpack it (and discover that directories under 3rdparty/ subdir 
are empty)
   c) drop the contents of 
https://github.com/mozilla/glean/archive/refs/tags/v52.0.0.tar.gz into 
3rdparty/glean/
   d) drop the contents of 
https://github.com/WireGuard/wireguard-tools/archive/refs/heads/master.zip 
into 3rdparty/wireguard-tools/


2) Based on mozillavpn_2.9.0-1.debian.tar.xz, apply some changes to 
debian/ directory:
   a) -DBUILD_TESTING=OFF to dh_auto_configure argument in 
debian/rules (without it it FTBFS trying to run some tests and that is 
also in upstream's rules file)
   d) change rm -rf debian/mozillavpn/etc/opt/chrome to rm -rf 
debian/mozillavpn/etc/opt in debian/rules so purge won't remove 
/etc/opt/ since there's nothing in there anyway
   c) Add packages python3-click and python3-jinja2 to Build-Depnds in 
debian/control (without these, it FTBFS)
   d) remove libqt6* and qt6-qpa-plugins dependencies in 
debian/control (see #1026957).


This builds for me on amd64.

An alternative to step 1) above is of course to clone from 
https://github.com/mozilla-mobile/mozilla-vpn-client.git and then git 
submodule update --init. That only adds some stuff not needed for 
Debian into the orig.tar.gz.


For the record, I've placed copies of the files at 
https://in.terlu.de/~kreckel/mozillavpn/.


Also, debian-release should be contacted because of the build failure 
on mipsel and mpis64el. It makes little sense to insist on these 
architectures if upstream doesn't care.


Please decide how to proceed and let me know if I can help in any way.

  -richard.

Bug#1028066: marked as done (sleekxmpp: contains non-free fonts)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 23:55:35 +
with message-id 
and subject line Bug#1028067: Removed package(s) from unstable
has caused the Debian Bug report #1028066,
regarding sleekxmpp: contains non-free fonts
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.)


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

Source: sleekxmpp
Version: 1.3.3-9
Severity: serious

sleekxmpp contains two versions of the non-free Museo Slab font: 
https://www.exljbris.com/museoslab.html
Please replace to get rid of them.
--- End Message ---
--- Begin Message ---
Version: 1.3.3-9+rm

Dear submitter,

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

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

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

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

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

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

Bug#952299: marked as done (golang-go-dbus: FTBFS: failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: mkdir /sbuild-nonexistent: permission denied)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 23:55:04 +
with message-id 
and subject line Bug#1028065: Removed package(s) from unstable
has caused the Debian Bug report #952299,
regarding golang-go-dbus: FTBFS: failed to initialize build cache at 
/sbuild-nonexistent/.cache/go-build: mkdir /sbuild-nonexistent: permission 
denied
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.)


-- 
952299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-go-dbus
Version: 1~bzr20150122-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd build/src/launchpad.net/go-dbus/v1
> for t in 'S.Test.*coder.*' 'S.TestAuthenticate' 'S.TestMatch.*' \
>   'S.TestNew.*' 'S.TestNonceTcpTransportDial' 'S.TestReadMessage' \
>   'S.TestSigna.*' 'S.TestTcpTransportDial' 'S.TestUnixTransportDial' \
>   'S.TestWriteMessage'; do \
>   GOPATH=/<>/build go test -gocheck.v -gocheck.f $t; \
> done
> failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: 
> mkdir /sbuild-nonexistent: permission denied
> failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: 
> mkdir /sbuild-nonexistent: permission denied
> failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: 
> mkdir /sbuild-nonexistent: permission denied
> failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: 
> mkdir /sbuild-nonexistent: permission denied
> failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: 
> mkdir /sbuild-nonexistent: permission denied
> failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: 
> mkdir /sbuild-nonexistent: permission denied
> failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: 
> mkdir /sbuild-nonexistent: permission denied
> failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: 
> mkdir /sbuild-nonexistent: permission denied
> failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: 
> mkdir /sbuild-nonexistent: permission denied
> failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: 
> mkdir /sbuild-nonexistent: permission denied
> make[1]: *** [debian/rules:15: override_dh_auto_test] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/02/22/golang-go-dbus_1~bzr20150122-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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 1~bzr20150122-3+rm

Dear submitter,

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

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

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

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

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

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

Bug#783420: marked as done (php-mime-type: Needs an update for PHP 7.0)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 23:57:47 +
with message-id 
and subject line Bug#1028126: Removed package(s) from unstable
has caused the Debian Bug report #783420,
regarding php-mime-type: Needs an update for PHP 7.0
to be marked as done.

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

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


-- 
783420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-mime-type
Version: 1.3.1-1
Severity: serious

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

php-mime-type is only used by extplorer (removed from testing over a
year ago), and is not maintained upstream anymore (the version in Debian
even predates the latest upstream version).

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1.3.1-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#823683: marked as done (PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 23:58:37 +
with message-id 
and subject line Bug#1028127: Removed package(s) from unstable
has caused the Debian Bug report #823683,
regarding PHP 7.0 Transition
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.)


-- 
823683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-services-json
Version: 1.0.3-1
Severity: serious
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

Hi,

As shown by php7cc, php-services-json contains deprecated PHP 4
constructors. As outlined in #783422, upstream has not been active in
years, so unless that changes, this package should probably not be
shipped in the next Debian stable release.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.0.3-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#1028165: libfltk1.3-dev: Missing dependency on fluid?

[Adrian Bunk]

Package: libfltk1.3-dev
Version: 1.3.8-5
Severity: serious
Tags: ftbfs
Control: affects -1 src:giada

https://buildd.debian.org/status/fetch.php?pkg=giada&arch=amd64&ver=0.22.0-1%2Bb1&stamp=1672996393&raw=0

...
CMake Error at /usr/lib/fltk/FLTK-Targets.cmake:145 (message):
  The imported target "fluid" references the file

 "/usr/bin/fluid"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/fltk/FLTK-Targets.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/fltk/FLTKConfig.cmake:31 (include)
  CMakeLists.txt:330 (find_package)


-- Configuring incomplete, errors occurred!



This was likely broken by 1.3.8-5, the fix for #1017271 did
touch the cmake files:
https://tests.reproducible-builds.org/debian/history/giada.html

Processed: libfltk1.3-dev: Missing dependency on fluid?

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:giada
Bug #1028165 [libfltk1.3-dev] libfltk1.3-dev: Missing dependency on fluid?
Added indication that 1028165 affects src:giada

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

Bug#1028167: golang-github-gopacket-gopacket FTBFS: FAIL: TestBPFInstruction

[Adrian Bunk]

Source: golang-github-gopacket-gopacket
Version: 0.1.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=golang-github-gopacket-gopacket&arch=all&ver=0.1.0-1&stamp=1673131542&raw=0

...
--- FAIL: TestBPFInstruction (0.00s)
FAIL
FAILgithub.com/gopacket/gopacket/pcap   0.046s
ngread_dsb_test.go:51: Decryption Secrets Block found, index block: 0
ngread_dsb_test.go:44: ReadPacketData returned EOF
ngread_dsb_test.go:60: bigEndian false
ngread_dsb_test.go:61: Reading packet data into memory: 276 packets in 
1.498864ms, 5.43µs per packet
ngread_dsb_test.go:63: decryptionSecrets: 1
ngread_dsb_test.go:66: SecretType:544C534B, Length:176, Data:CLIENT_RANDOM 
75db01ecd858f0066c5b75884de569b7370101ee0cd6a21f900333d501ffc2a4 
05edde5321c8a8fe04517c3b7e0e443075c0d6bdae4bffe44a72f9c11e734c6124be4ab5bd932e7d52573e08026b6a35
...

Bug#1028168: commons-configuration2: Build-depends on NBS package, about to FTBFS

[Scott Kitterman]

Source: commons-configuration2
Version: 2.8.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

* source package commons-vfs version 2.1-4 no longer builds
  binary package(s): libcommons-vfs-java-doc
  on all
  - broken Build-Depends:
commons-configuration2: libcommons-vfs-java-doc

Once libcommons-vfs-java-doc is decrufted, this package will not longer
build.

Scott K

Bug#1028166: commons-configuration: Build-depends on NBS package about to FTBFS

[Scott Kitterman]

Source: commons-configuration
Version: 1.10-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source


* source package commons-vfs version 2.1-4 no longer builds
  binary package(s): libcommons-vfs-java-doc
  on all
  - broken Build-Depends:
commons-configuration: libcommons-vfs-java-doc

Once libcommons-vfs-java-doc is decrufted, this package will not longer
build.

Scott K