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

[Sven Joachim]

On 2023-01-08 02:56 +0100, Vincent Lefevre wrote:

> On 2023-01-07 20:05:59 +0100, Sven Joachim wrote:
>> >> 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.
>
> I track the diffs in etc, and it seems that 2.3-33 and later did
> nothing wrong.

This assumption is incorrect, see #1019554 and siblings.

> Dangling symlinks were removed after the upgrade
> to anacron 2.3-34, but these were *dangling* symlinks, so that
> this should have no effect. See the bug I reported:
>
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993348
>
> Dangling symlinks are bad as they can break other tools
> (e.g. checkrestart, which was the reason I reported this bug).

I do not like dangling symlinks either, however systemd works fine with
them.  Even if the unit is below /usr/lib/systemd/system and the symlink
in /etc points to a file below /lib/systemd/system, systemd still
activates the unit to accommodate system without a merged /usr.

>> What does "systemctl status anacron.service" print?
>
> ○ anacron.service - Run anacron jobs
>  Loaded: loaded (/lib/systemd/system/anacron.service; disabled; preset: 
> enabled)
>  Active: inactive (dead)
>Docs: man:anacron
>  man:anacrontab
>
> And anacron is no longer in the timers (systemctl list-timers).

That is your problem, you need to reenable and restart these units.

# systemctl enable anacron.service anacron.timer
# systemctl start anacron.service anacron.timer

See the d-d-a link I gave in my first reply,
https://lists.debian.org/debian-devel-announce/2022/11/msg1.html.

Cheers,
   Sven

Bug#1028186: cluster3: needs rebuild for Python 3.11 as default

[Graham Inggs]

Source: cluster3
Version: 1.59+ds-4
Severity: serious

Hi Maintainer

cluster3 is non-free and is not auto-buildable, so requires a manual
rebuild for the Python 3.11 transition.  Please upload a build with
Python 3.11 as default, including binaries.

Regards
Graham

Bug#1027951: marked as done (python-dev-is-python3: Uninstallable as it depends on python-is-python3 which "Breaks: python-dev-is-python3 (<< 12)")

[Debian Bug Tracking System]

Your message dated Sun, 08 Jan 2023 07:41:38 +
with message-id 
and subject line Bug#1027951: fixed in what-is-python 13
has caused the Debian Bug report #1027951,
regarding python-dev-is-python3: Uninstallable as it depends on 
python-is-python3 which "Breaks: python-dev-is-python3 (<< 12)"
to be marked as done.

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

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


-- 
1027951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-dev-is-python3
Version: 3.11.1-2
Severity: serious

Hi,

python-dev-is-python3 is uninstallable because of these never
satisfiable package relations:

Package: python-dev-is-python3
Source: what-is-python (12)
Version: 3.11.1-2
Depends: python-is-python3 (= 3.11.1-2), […]
^^

Package: python-is-python3
Source: what-is-python (12)
Version: 3.11.1-2
Installed-Size: 15
Maintainer: Matthias Klose  
Architecture: all
Replaces: […], python-dev-is-python3 (<< 12), […]
Breaks:   […], python-dev-is-python3 (<< 12), […]
  ^^

See also
https://qa.debian.org/dose/debcheck/unstable_main/latest/packages/python-dev-is-python3.html#ff0c7854f66c25b67d96e10ba73b0ca9
https://piuparts.debian.org/sid/fail/python-dev-is-python3_3.11.1-2.log

Reason is probably that for the << relation in Breaks and Replaces of
python-is-python3 the source package version is used despite the
(different) binary package version should have been used.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: what-is-python
Source-Version: 13
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
what-is-python, 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.
Matthias Klose  (supplier of updated what-is-python 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: Sun, 08 Jan 2023 08:19:39 +0100
Source: what-is-python
Architecture: source
Version: 13
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose  
Changed-By: Matthias Klose 
Closes: 1027951
Changes:
 what-is-python (13) unstable; urgency=medium
 .
   * Fix versioned breaks/replaces: Closes: #1027951.
Checksums-Sha1:
 c3bb218e77f2eb8c0c8af8b709614962a710887c 1577 what-is-python_13.dsc
 494decc3d5f9a74ecf39aff6b89ff92ce3c3fbf4 2520 what-is-python_13.tar.xz
 7cbd7384cb6f3dd93bb8387095b4e15940dac316 6125 
what-is-python_13_source.buildinfo
Checksums-Sha256:
 762c26f880096fdf0695a472876fa1a920cc12627c7a059399d3578ec4abdb50 1577 
what-is-python_13.dsc
 57589e40ef3356d4e6e87fe7c57b0245763b34e6674a8757bcb3f8d4c6930fde 2520 
what-is-python_13.tar.xz
 02f110bed29e86b4d8049f6705b1f6492bbf21bee449d7fc4593e03b2b06d693 6125 
what-is-python_13_source.buildinfo
Files:
 1aa4155675ed41987949b82aa22cc2eb 1577 python optional what-is-python_13.dsc
 6fc8df4fe0b5601e65bed247b02e1f14 2520 python optional what-is-python_13.tar.xz
 9b84b957f588d8400878f25a78bba433 6125 python optional 
what-is-python_13_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmO6b4YQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9XviEADNpO91rQ40YST8mmaxFmwPzFTbteyUvRPq
KvQycDlLc6+2hrXfHY9qa9BgFgSpwbu5/iOiGwpaigluEcGZ43bozv/0Kv+8zC9l
Mcy7P2y9hf9Vd5Z6DDH2kAhq7TZpcOQ+AoL7odPMS+uYzw3NOy5JHWIK0uI3EYyE
ig/DAoVjdRotbXHS3WY/vplzvadTaD2XihY2p7m0WKGCIRHc9a8fxAOXJseU22fT
5jDbW23yfqQAK0msRVzIELT//uXgPdp+3rU2YStKrwR3u0ofPvCF8XusnIFIxWlH
Q4PEWSJMH1slEbG8/A5zct7d0USXUE0UjJ1ooBV+Cf8rcOtbry190JtIY9UKX7hs

Bug#1025119: marked as done (python-ratelimiter: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine')

[Debian Bug Tracking System]

Your message dated Sun, 08 Jan 2023 07:16:04 +
with message-id 
and subject line Bug#1025119: fixed in python-ratelimiter 1.2.0.post0-4
has caused the Debian Bug report #1025119,
regarding python-ratelimiter: (autopkgtest) needs update for python3.11: module 
'asyncio' has no attribute 'coroutine'
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.)


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

Source: python-ratelimiter
Version: 1.2.0.post0-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.10.6-3
python-ratelimiter from testing1.2.0.post0-3
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


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

Paul

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

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

Testing with python3.11:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/ratelimiter.py", line 36, in 


class RateLimiter(object):
  File "/usr/lib/python3/dist-packages/ratelimiter.py", line 127, in 
RateLimiter

__aexit__ = asyncio.coroutine(__exit__)
^
AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you 
mean: 'coroutines'?

autopkgtest [23:15:36]: test autodep8-python3



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-ratelimiter
Source-Version: 1.2.0.post0-4
Done: Diane Trout 

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

Debian distribution maintenance software
pp.
Diane Trout  (supplier of updated python-ratelimiter 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:26:05 -0800
Source: python-ratelimiter
Architecture: source
Version: 1.2.0.post0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Diane Trout 
Closes: 1025119 1028175
Changes:
 python-ratelimiter (1.2.0.post0-4) unstable; urgency=medium
 .
   * Add debian/patches/use-async-keyword.patch
 - Makes package compatible with Python 3.11 Closes: #1025119
   Closes: #1028175
Checksums-Sha1:
 ec0025feab03bf8fa5f7f7e1e0539a1c52f697ac 2162 
python-ratelimiter_1.2.0.post0-4.dsc
 fe57af82a377f27b6d0111c2a7e505e3b3bf85c0 3704 
python-ratelimiter_1.2.0.post0-4.debian.tar.xz
 f1610e08d399c518898d76ec1bd1c66c575da7f3 6838 
python-ratelimiter_1.2.0.post0-4_amd64.buildinfo
Checksums-Sha256:
 804915fcb2872a8f1715f1942c469f90f8027c1bbcd138cc763652867ca97ef4 2162 
python-ratelimiter_1.2.0.post0-4.dsc
 110b977168b544855b03844c93d5933b0889abed78a3d954063b9ee0c6ce84d4 3704 
python-ratelimiter_1.2.0.post0-4.debian.tar.xz
 895563f47dbea1a5fe6944391ee044c99ccdd551aa97f3b9b6d2fc8f80efd670 6838 
python-ratelimiter_1.2.0.post0-4_amd64.buildinfo
Files:
 700a2e243a8d5733cdf13467a0d3b246 2162 python optional 
python-ratelimiter_1.2.0.post0-4.dsc
 

Bug#1028175: marked as done (snakemake rulename failes with asyncio has no attribute coroutine with python3.11)

[Debian Bug Tracking System]

Your message dated Sun, 08 Jan 2023 07:16:04 +
with message-id 
and subject line Bug#1028175: fixed in python-ratelimiter 1.2.0.post0-4
has caused the Debian Bug report #1028175,
regarding snakemake rulename failes with asyncio has no attribute coroutine 
with python3.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.)


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

Dear Maintainer,

I noticed that snakemake-modes tests were failing while I was trying to build
the package.

Eventually I found that running the snakemake executable was failing with
python 3.11, but worked with 3.10.

Using the test Snakefile from snakemake-mode for the tests I ran the command
with both python3.11 and python3.10. The results are below.

I should probably go try to package the throttle library and upload it to NEW.

Snakemake's upstream patched snakemake to use a different library throttle in
https://github.com/snakemake/snakemake/issues/1952

$ python3.11 /usr/bin/snakemake --dryrun aa.out
Building DAG of jobs...
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/snakemake/__init__.py", line 730, in
snakemake
success = workflow.execute(
  ^
  File "/usr/lib/python3/dist-packages/snakemake/workflow.py", line 942, in
execute
self.scheduler = JobScheduler(
 ^
  File "/usr/lib/python3/dist-packages/snakemake/scheduler.py", line 105, in
__init__
from ratelimiter import RateLimiter
  File "/usr/lib/python3/dist-packages/ratelimiter.py", line 36, in 
class RateLimiter(object):
  File "/usr/lib/python3/dist-packages/ratelimiter.py", line 127, in
RateLimiter
__aexit__ = asyncio.coroutine(__exit__)
^
AttributeError: module 'asyncio' has no attribute 'coroutine'

$ python3.10 -Wd /usr/bin/snakemake --dryrun aa.out
Building DAG of jobs...
/usr/lib/python3/dist-packages/ratelimiter.py:127: DeprecationWarning:
"@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
  __aexit__ = asyncio.coroutine(__exit__)
Job stats:
job  countmin threadsmax threads
-  ---  -  -
aa   1  1  1
total1  1  1


[Sat Jan  7 19:56:59 2023]
rule aa:
output: aa.out
jobid: 0
reason: Missing output files: aa.out
resources: tmpdir=/tmp

Job stats:
job  countmin threadsmax threads
-  ---  -  -
aa   1  1  1
total1  1  1

Reasons:
(check individual jobs above for details)
missing output files:
aa

This was a dry-run (flag -n). The order of jobs does not reflect the order of
execution.
/usr/lib/python3.10/tempfile.py:999: ResourceWarning: Implicitly cleaning up

  _warnings.warn(warn_message, ResourceWarning)


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 
'oldstable-debug'), (500, 'testing'), (500, 'stable'), (110, 'unstable'), (100, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages snakemake depends on:
ii  ca-certificates  20211016
ii  libjs-bootstrap  3.4.1+dfsg-3
ii  libjs-jquery 3.6.1+dfsg+~3.5.14-1
ii  python3  3.10.6-3+b1
ii  python3-appdirs  1.4.4-3
ii  python3-configargparse   1.5.3-1
ii  python3-connection-pool  0.0.3-2
ii  python3-datrie   0.8.2-4
ii  python3-docutils 0.17.1+dfsg-3
ii  python3-git  3.1.27-1
ii  python3-jinja2   3.0.3-2
ii  python3-jsonschema   4.9.1-3
ii  python3-nbformat 5.5.0-1
ii  python3-pkg-resources65.5.0-1.1
ii  python3-psutil   5.9.4-1
ii  python3-pulp 2.6.0+dfsg-1
ii  python3-ratelimiter  1.2.0.post0-3
ii  python3-requests 2.28.1+dfsg-1
ii  python3-smart-open   5.2.1-5
ii  python3-stopit   1.1.2-2
ii  python3-tabulate 0.8.9-1
ii  python3-toposort 1.7-1
ii  python3-wrapt1.14.1-2+b1
ii  python3-yaml 6.0-3+b1

Bug#1027371: marked as done (golang-github-tealeg-xlsx: FTBFS in bullseye (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Sun, 08 Jan 2023 06:36:29 +
with message-id 
and subject line Bug#1027371: fixed in golang-github-tealeg-xlsx 
1.0.3+git20181024.dbf71b6-2
has caused the Debian Bug report #1027371,
regarding golang-github-tealeg-xlsx: 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.)


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

Package: src:golang-github-tealeg-xlsx
Version: 1.0.3+git20181024.dbf71b6-1.1
Severity: serious
Tags: ftbfs patch

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install -trimpath -v -p 2 
github.com/tealeg/xlsx
internal/unsafeheader
internal/cpu
runtime/internal/atomic
internal/bytealg
runtime/internal/sys
runtime/internal/math
internal/race
sync/atomic
unicode
runtime
unicode/utf8
math/bits
math
internal/testlog
encoding
image/color
internal/reflectlite
sync
errors
sort
io
strconv
bytes
strings
reflect
bufio
internal/oserror
syscall
internal/syscall/unix
time
internal/fmtsort
internal/syscall/execenv
encoding/binary
hash
hash/crc32
internal/poll
path
os
fmt
path/filepath
io/ioutil
compress/flate
encoding/xml
archive/zip
github.com/tealeg/xlsx
   dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 
github.com/tealeg/xlsx
=== RUN   Test

--
FAIL: cell_test.go:740: CellSuite.TestSetDateWithOptions

cell_test.go:754:
c.Assert(err, IsNil)
... value *errors.errorString = {s:"unknown time zone 
America/New_York"} ("unknown time zone America/New_York")

OOPS: 173 passed, 1 FAILED
--- FAIL: Test (1.36s)
=== RUN   TestFuzzCrashers
--- PASS: TestFuzzCrashers (0.00s)
FAIL
FAILgithub.com/tealeg/xlsx  1.362s
FAIL
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 
github.com/tealeg/xlsx returned exit code 1
make: *** [debian/rules:4: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-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-tealeg-xlsx
Source-Version: 1.0.3+git20181024.dbf71b6-2
Done: Nobuhiro Iwamatsu 

We believe that the bug you reported is fixed in the latest version of
golang-github-tealeg-xlsx, 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.
Nobuhiro Iwamatsu  (supplier of updated 
golang-github-tealeg-xlsx 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: Sun, 08 Jan 2023 14:21:37 +0900
Source: golang-github-tealeg-xlsx
Architecture: source
Version: 1.0.3+git20181024.dbf71b6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Nobuhiro Iwamatsu 
Closes: 1027371
Changes:
 golang-github-tealeg-xlsx 

Bug#1028181: runit-init makes the system unbootable

[Helmut Grohne]

Package: runit-init
Version: 2.1.2-52
Severity: grave
Justification: makes the system unbootable

Hi,

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

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

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

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

I retried with mount installed and got something different:

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

It seems like runit requires checking the filesystem, but e2fsprogs is
not essential anymore and it fails hard. Nowadays, checking ext4
filesystems is optional and systemd skips doing it in the absence of
e2fsprogs.

So I went on to retry with e2fsprogs added and this is what I got:

| Begin: Running /scripts/local-bottom ... done.
| Begin: Running /scripts/init-bottom ... done.
| [1.484294] Not activating Mandatory Access Control as /sbin/tomoyo-init 
does not exist.
| - runit: $Id: 25da3b86f7bed4038b8a039d2f8e8c9bbcf0822b $: booting.
| - runit: enter stage: /etc/runit/1
| Starting hotplug events dispatcher: systemd-udevd.
| Synthesizing the initial hotplug events (subsystems)...done.
| 

Processed: Bug#1027371 marked as pending in golang-github-tealeg-xlsx

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#1027371: marked as pending in golang-github-tealeg-xlsx

[Nobuhiro Iwamatsu]

Control: tag -1 pending

Hello,

Bug #1027371 in golang-github-tealeg-xlsx 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-tealeg-xlsx/-/commit/6581e7195ee529954126feba4dd1fe60a10d2e38


d/control: Add tzdata to B-D (Closes: #1027371)

Signed-off-by: Nobuhiro Iwamatsu 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1027371

Processed: affects 1027947

[Debian Bug Tracking System]

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

> affects 1027947 src:gftools
Bug #1027947 [python3-setuptools-scm] python3-setuptools-scm: needs depend on 
python3-tomli during Python 3.11 transition
Added indication that 1027947 affects src:gftools
> thanks
Stopping processing here.

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

Bug#1028180: python-falcon FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: python-falcon
Version: 3.1.0-3
Severity: serious
Tags: ftbfs

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

...
 ERROR collecting tests/asgi/test_ws.py 
ImportError while importing test module 
'/build/1st/python-falcon-3.1.0/tests/asgi/test_ws.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/asgi/test_ws.py:11: in 
from falcon.asgi import App
falcon/asgi/__init__.py:35: in 
from .app import App
falcon/asgi/app.py:46: in 
from .response import Response
falcon/asgi/response.py:17: in 
from asyncio.coroutines import CoroWrapper  # type: ignore
E   ImportError: cannot import name 'CoroWrapper' from 'asyncio.coroutines' 
(/usr/lib/python3.11/asyncio/coroutines.py)
=== warnings summary ===
falcon/media/multipart.py:17
  /build/1st/python-falcon-3.1.0/falcon/media/multipart.py:17: 
DeprecationWarning: 'cgi' is deprecated and slated for removal in Python 3.13
import cgi

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=== short test summary info 
ERROR tests/asgi/test_asgi_conductor.py
ERROR tests/asgi/test_asgi_helpers.py
ERROR tests/asgi/test_asgi_servers.py
ERROR tests/asgi/test_boundedstream_asgi.py
ERROR tests/asgi/test_buffered_reader.py
ERROR tests/asgi/test_example_asgi.py
ERROR tests/asgi/test_hello_asgi.py
ERROR tests/asgi/test_lifespan_handlers.py
ERROR tests/asgi/test_request_body_asgi.py
ERROR tests/asgi/test_request_context_asgi.py
ERROR tests/asgi/test_response_media_asgi.py
ERROR tests/asgi/test_scheduled_callbacks.py
ERROR tests/asgi/test_scope.py
ERROR tests/asgi/test_sse.py
ERROR tests/asgi/test_sync.py
ERROR tests/asgi/test_testing_asgi.py
ERROR tests/asgi/test_ws.py
!!! Interrupted: 17 errors during collection !!!
 1 warning, 17 errors in 16.98s 
make[1]: *** [debian/rules:25: override_dh_auto_install] Error 2

Bug#1027380: safeclib: FTBFS in bullseye (missing build-depends on tzdata)

[Adam Borowski]

Control: severity -1 wishlist
Control: tags -1 +wontfix

On Sun, Jan 01, 2023 at 11:49:26PM +0100, Santiago Vila wrote:
> [ Thanks for fixing the bug in unstable so fast ]

... too fast, in fact.  Per the discussion on debian-policy, it's not a bug,
and this way I have a redundant dependency which actually is a bug (for a
good reason: it makes it harder to reorganize unrelated packages).

I've thus reverted the change -- in git, not worth a separate upload.

> > I'm all for fixing bugs in stable that:
> >   * are obviously bugs (rather than a point of debate)
> 
> You are the only one debating this, but it should really not be a point of 
> debate.

Per debian-policy, indeed.  Good that the debate has been resolved.

[...]
> [ In fact, I wonder why you bothered to add the missing B-D if you really 
> believe it
> is not a bug.

Because I considered doing so to be less effort than arguing.  Which has
proven to be premature.

[...]

> I think it is important to honor the promises we made to the users. We
> promised a stable release without FTBFS bugs, and we are almost delivering
> it, but not completely.
> 
> In the end, it boils down to where do we draw the line. You think having
> a reduced number of packages which FTBFS according to Policy is ok. I think
> the only acceptable number of FTBFS bugs to have in a stable release is zero,
> and I am working towards such goal.

Here I agree, but inventing new bugs where there's no FTBFS is not helpful.

"FTBFS" means the package actually fails to build from source, using
any of build machinery present in the archive, on a realistic
hardware/kernel/setup, for a distribution the given bug is marked as
affecting.

Thus, for example: a FTBFS with a future version of gcc or with buildflags
that are not enabled yet is not a RC bug, becoming serious only once such a
compiler/configuration is actually uploaded to unstable.  Likewise, a change
to the build environment where tzdata is no longer available, would be RC
only in unstable but not in bullseye.
 
> So the only thing I ask is that you do not insist that this is not a bug
> when I reopen it for bullseye. Since I will be the one doing the work,
> I think I should be allowed to use the BTS to track those bugs.

Okay, I'm not closing the bug for bullseye.  I did though reduce the
severity to wishlist as it's (per the debian-policy discussion) neither
RC nor even contravening bullseye's nor current unstable's policy,
and the change is opposed by a number of people.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Bestest pickup line:
⢿⡄⠘⠷⠚⠋⠀ "Cutie, your name must be Suicide, cuz I think of you every day."
⠈⠳⣄

Processed: Re: Bug#1027380: safeclib: FTBFS in bullseye (missing build-depends on tzdata)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #1027380 {Done: Adam Borowski } [src:safeclib] 
safeclib: FTBFS in bullseye (missing build-depends on tzdata)
Severity set to 'wishlist' from 'serious'
> tags -1 +wontfix
Bug #1027380 {Done: Adam Borowski } [src:safeclib] 
safeclib: FTBFS in bullseye (missing build-depends on tzdata)
Added tag(s) wontfix.

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

Bug#1004441: unblocking chromium?

[Andres Salomon]

On Fri, Jan 6 2023 at 11:36:02 AM +0200, Adrian Bunk  
wrote:

On Fri, Jan 06, 2023 at 10:18:16AM +0100, Moritz Muehlenhoff wrote:

...
 We might consider to set some expectation for oldstable-security, 
though e.g state that
 oldstable-security updates stop three months after the release of 
stable or so.





Yeah, I like that idea. I think I could comfortably handle about 6 
months of dual security support (stable+oldstable), personally.





 Chromium is very fast-paced in toolchain changes (e.g. in the past 
new C++ features
 become incompatible with GCC and we might see something similar 
with LLVM (which

 is used these days) as well.


New LLVM versions are already added annually to *stable for Firefox,
even in LTS (which got LLVM 13 last autumn in addition to 6, 7 and 
11).



The LLVM updates have been very helpful for chromium bullseye support.

Bug#1028168: marked as done (commons-configuration2: Build-depends on NBS package, about to FTBFS)

[Debian Bug Tracking System]

Your message dated Sun, 08 Jan 2023 05:20:06 +
with message-id 
and subject line Bug#1028168: fixed in commons-configuration2 2.8.0-2
has caused the Debian Bug report #1028168,
regarding commons-configuration2: Build-depends on NBS package, about to 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.)


-- 
1028168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: commons-configuration2
Source-Version: 2.8.0-2
Done: tony mancill 

We believe that the bug you reported is fixed in the latest version of
commons-configuration2, 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.
tony mancill  (supplier of updated commons-configuration2 
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:56:51 -0800
Source: commons-configuration2
Architecture: source
Version: 2.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 1028168
Changes:
 commons-configuration2 (2.8.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Drop libcommons-configuration2-java-doc (Closes: #1028168)
   * Freshen years in debian/copyright
   * Bump Standards-Version to 4.6.2
   * Add liblog4j1.2-java build-dep and adjust maven.ignoreRules.
Checksums-Sha1:
 f63ccf15b630d16977ab088ffbd96bbe5f00b7b4 2644 
commons-configuration2_2.8.0-2.dsc
 d6d520870f02a4a3daa9869cbcb9eb8c41b911b3 4924 
commons-configuration2_2.8.0-2.debian.tar.xz
 2a80f00971d9224be26ae86e24726d16545562cd 17253 
commons-configuration2_2.8.0-2_amd64.buildinfo
Checksums-Sha256:
 e215c28f03194ad2fc777fe9afd3783b3de98f023fa06b751e8aeaae4473ee60 2644 
commons-configuration2_2.8.0-2.dsc
 b120dcc1e201b12d9c6ca1360e30c2c77ed2e9e9b2f467b7882a85b4475acff1 4924 
commons-configuration2_2.8.0-2.debian.tar.xz
 c70b90b5491ac29887dcf792e91a7504848a108a335d1ad4fa598c4e18ed4dca 17253 
commons-configuration2_2.8.0-2_amd64.buildinfo
Files:
 31ea089dcfd7d10e63424652f1357d91 2644 java optional 
commons-configuration2_2.8.0-2.dsc
 f2a465db31e4e012607618abf565cbba 4924 java optional 
commons-configuration2_2.8.0-2.debian.tar.xz
 7a4bdf7ddf505c6007acacc457c7894f 17253 java optional 
commons-configuration2_2.8.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmO6RdMUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpY1FBAAlTi8EEnOFrQxGDkZabvj2mu2j12H
E6KCIq+I8rXddzCuT49yYn3vNDLXOTkXaZcVPZaux8nGv/99CgOIf/aWjiktDcpM
NDODD6Bd+dDA6eXRnfoXFZAUsVdrMsmnz6ZQWWhl1W+/NfV/Bu3Yn37fF8eVYrvm
IX68u+cG/R+fpP35mybqtjMCMEStdqvWgdaLIa78w5Cmb82oKU78zx30TKjLIDG4
jlg/uNLG5VnPjhd46Pjj3mJ3T608MmAOENwTdWov014QjBlpGumslRo7pUzNEdKz
xPf+6+xCQ8Gltl37f6/YUSHIoSinrP/Z8AgQcz2AWAlzzVUc5LS2j9Xedo0HUI8z
e8bOcwkg/CjcvDr3vWLVR0OdKSODTHXUOVV5ggpDSzQpp6Ff/j/SeKFkzUcMbeuC
6B/LIYhC3qGGCj7dIOqNYbTZkWz9Iyvi9ELgVjHfLcQRbwKXmaaHGMQRYfmkbkSt
gDwBbTtBl3Z9U0ag+ATafkqsw/IwYp0AGdx3taN5tntHQ2pzm5OQ3uAuXQeV1LQw
/0y/EromZuYfveP1CdxVaOfcv695KPKcsW+wIJ8Mmr2awWuPKrWVPlUUfkDtn/YP
1LZYHKJXufaqUePz7vlS7SIBS53YoUqs7M/I79X6zEQLVnNJj+CXVYYnvpKPj8se
Ez2UCqHdMmhXCgU=
=5itv
-END PGP SIGNATURE End Message ---

Bug#1028179: 0ad FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: 0ad
Version: 0.0.26-2
Severity: serious
Tags: ftbfs

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

...
Creating Python 3 environment
/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/third_party/python/virtualenv/virtualenv.py:24:
 DeprecationWarning: The distutils package is deprecated and slated for removal 
in Python 3.12. Use setuptools or check PEP 632 for potential alternatives
  import distutils.spawn
/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/third_party/python/virtualenv/virtualenv.py:25:
 DeprecationWarning: The distutils.sysconfig module is deprecated, use 
sysconfig instead
  import distutils.sysconfig
Using base prefix '/usr'
New python executable in 
/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/_virtualenvs/init_py3/bin/python3
Also creating executable in 
/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/_virtualenvs/init_py3/bin/python
ERROR: The executable 
/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/_virtualenvs/init_py3/bin/python3
 is not functioning
ERROR: It thinks sys.prefix is '/usr' (should be 
'/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/_virtualenvs/init_py3')
ERROR: virtualenv is not compatible with this system or executable
Traceback (most recent call last):
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/../js/src/../../configure.py",
 line 181, in 
sys.exit(main(sys.argv))
 ^^
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/../js/src/../../configure.py",
 line 52, in main
sandbox.run(os.path.join(os.path.dirname(__file__), 'moz.configure'))
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/python/mozbuild/mozbuild/configure/__init__.py",
 line 445, in run
self.include_file(path)
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/python/mozbuild/mozbuild/configure/__init__.py",
 line 436, in include_file
exec_(code, self)
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/python/mozbuild/mozbuild/util.py",
 line 53, in exec_
exec(object, globals, locals)
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/moz.configure",
 line 7, in 
include('build/moz.configure/init.configure')
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/python/mozbuild/mozbuild/configure/__init__.py",
 line 773, in include_impl
self.include_file(what)
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/python/mozbuild/mozbuild/configure/__init__.py",
 line 436, in include_file
exec_(code, self)
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/python/mozbuild/mozbuild/util.py",
 line 53, in exec_
exec(object, globals, locals)
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/build/moz.configure/init.configure",
 line 242, in 
@depends('PYTHON3', check_build_environment, mozconfig, '--help')
 
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/python/mozbuild/mozbuild/configure/__init__.py",
 line 756, in decorator
depends = DependsFunction(self, func, dependencies, when=when)
  
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/python/mozbuild/mozbuild/configure/__init__.py",
 line 129, in __init__
sandbox._value_for(self)
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/python/mozbuild/mozbuild/configure/__init__.py",
 line 542, in _value_for
return self._value_for_depends(obj)
   
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/python/mozbuild/mozbuild/util.py",
 line 1018, in method_call
cache[args] = self.func(instance, *args)
  ^^
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/python/mozbuild/mozbuild/configure/__init__.py",
 line 551, in _value_for_depends
value = obj.result()

  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/python/mozbuild/mozbuild/util.py",
 line 1018, in method_call
cache[args] = self.func(instance, *args)
  ^^
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/python/mozbuild/mozbuild/configure/__init__.py",
 line 155, in result
return self._func(*resolved_args)
   ^^
  File 
"/build/1st/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/python/mozbuild/mozbuild/configure/__init__.py",
 line 1161, in wrapped
return new_func(*args, **kwargs)
   

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

[tony mancill]

On Sat, Jan 07, 2023 at 05:24:30PM -0800, tony mancill wrote:
> $ reverse-depends -b -l libcommons-vfs-java
> commons-configuration
> commons-configuration2
> ivy
> mondrian
> sbt-ivy

Bah, this should have been:

$ reverse-depends -l -b libcommons-vfs-java-doc
commons-configuration
commons-configuration2

So even less to fix-up than I initially thought.

Bug#1028178: aubio FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: aubio
Version: 0.4.9-4.2
Severity: serious
Tags: ftbfs

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

...
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/1st/aubio-0.4.9'
python3 ./waf configure --verbose --destdir=debian/tmp --prefix=/usr 
--enable-fftw3f --libdir=/usr/lib/x86_64-linux-gnu
Waf: The wscript in '/build/1st/aubio-0.4.9' is unreadable
Traceback (most recent call last):
  File "/build/1st/aubio-0.4.9/waflib/Scripting.py", line 102, in 
waf_entry_point
set_main_module(wscript)
  File "/build/1st/aubio-0.4.9/waflib/Scripting.py", line 142, in 
set_main_module
Context.g_module=Context.load_module(file_path)
 ^^
  File "/build/1st/aubio-0.4.9/waflib/Context.py", line 349, in load_module
code=Utils.readf(path,m='rU',encoding=encoding)
 ^^
  File "/build/1st/aubio-0.4.9/waflib/Utils.py", line 146, in readf
with open(fname,m)as f:
 ^
ValueError: invalid mode: 'rUb'
make[1]: *** [debian/rules:45: override_dh_auto_configure] Error 2

Bug#1028177: 389-ds-base FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: 389-ds-base
Version: 2.0.15-1.1
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/389ds/389-ds-base/issues/5333

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/389-ds-base.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/389-ds-base-2.0.15'
(cd src/lib389 && python3 setup.py build)
running build
running build_py
running build_manpages
generating man/dsconf.8
Traceback (most recent call last):
  File "/build/1st/389-ds-base-2.0.15/src/lib389/setup.py", line 33, in 
setup(
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
setup
return distutils.core.setup(**attrs)
   ^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
185, in setup
return run_commands(dist)
   ^^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
201, in run_commands
dist.run_commands()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
969, in run_commands
self.run_command(cmd)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1208, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", 
line 132, in run
self.run_command(cmd_name)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 318, 
in run_command
self.distribution.run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1208, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/build_manpages/build_manpages.py", line 
85, in run
self.run_command(DEFAULT_CMD_NAME)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 318, 
in run_command
self.distribution.run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1208, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/build_manpages/build_manpages.py", line 
74, in run
parser = get_parser(data['import_type'], data['import_from'], 
data['objname'], data['objtype'])
 
^^
  File "/usr/lib/python3/dist-packages/build_manpages/build_manpage.py", line 
43, in get_parser
return get_parser_from_file(import_from, objname, objtype)
   ^^^
  File "/usr/lib/python3/dist-packages/build_manpages/build_manpage.py", line 
37, in get_parser_from_file
filedict = run_path(filename)
   ^^
  File "", line 291, in run_path
  File "", line 98, in _run_module_code
  File "", line 88, in _run_code
  File "cli/dsconf", line 83, in 
cli_plugin.create_parser(subparsers)
  File "/build/1st/389-ds-base-2.0.15/src/lib389/lib389/cli_conf/plugin.py", 
line 115, in create_parser
cli_passthroughauth.create_parser(subcommands)
  File 
"/build/1st/389-ds-base-2.0.15/src/lib389/lib389/cli_conf/plugins/passthroughauth.py",
 line 241, in create_parser
enable = subcommands.add_parser('enable', help='Enable the pass through 
authentication plugins')
 
^^^
  File "/usr/lib/python3.11/argparse.py", line 1197, in add_parser
raise ArgumentError(self, _('conflicting subparser: %s') % name)
argparse.ArgumentError: argument {show,enable,disable,status}: conflicting 
subparser: enable
make[1]: *** [debian/rules:42: override_dh_auto_build] Error 1

Bug#1028176: cmake-format FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: cmake-format
Version: 0.6.13-2
Severity: serious
Tags: ftbfs

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

...
==
ERROR: test_nested_include 
(cmakelang.test.config_include_test.TestConfigInclude.test_nested_include)
--
Traceback (most recent call last):
  File 
"/build/1st/cmake-format-0.6.13/.pybuild/cpython3_3.11/build/cmakelang/test/config_include_test.py",
 line 53, in tearDown
if self._test_passed():
   ^^^
  File 
"/build/1st/cmake-format-0.6.13/.pybuild/cpython3_3.11/build/cmakelang/test/config_include_test.py",
 line 32, in _test_passed
self._feedErrorsToResult(result, self._outcome.errors)

AttributeError: 'TestConfigInclude' object has no attribute 
'_feedErrorsToResult'

==
ERROR: test_relative_path 
(cmakelang.test.config_include_test.TestConfigInclude.test_relative_path)
--
Traceback (most recent call last):
  File 
"/build/1st/cmake-format-0.6.13/.pybuild/cpython3_3.11/build/cmakelang/test/config_include_test.py",
 line 53, in tearDown
if self._test_passed():
   ^^^
  File 
"/build/1st/cmake-format-0.6.13/.pybuild/cpython3_3.11/build/cmakelang/test/config_include_test.py",
 line 32, in _test_passed
self._feedErrorsToResult(result, self._outcome.errors)

AttributeError: 'TestConfigInclude' object has no attribute 
'_feedErrorsToResult'

==
ERROR: test_single_include 
(cmakelang.test.config_include_test.TestConfigInclude.test_single_include)
--
Traceback (most recent call last):
  File 
"/build/1st/cmake-format-0.6.13/.pybuild/cpython3_3.11/build/cmakelang/test/config_include_test.py",
 line 53, in tearDown
if self._test_passed():
   ^^^
  File 
"/build/1st/cmake-format-0.6.13/.pybuild/cpython3_3.11/build/cmakelang/test/config_include_test.py",
 line 32, in _test_passed
self._feedErrorsToResult(result, self._outcome.errors)

AttributeError: 'TestConfigInclude' object has no attribute 
'_feedErrorsToResult'

--
Ran 357 tests in 86.672s

FAILED (errors=3)
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd 
/build/1st/cmake-format-0.6.13/.pybuild/cpython3_3.11/build; python3.11 -m 
unittest discover -v 
dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit 
code 13
make[1]: *** [debian/rules:24: override_dh_auto_test] Error 25

Bug#1028168: marked as pending in commons-configuration2

[Tony Mancill]

Control: tag -1 pending

Hello,

Bug #1028168 in commons-configuration2 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/commons-configuration2/-/commit/3f994132b1204a09b608a6be582bae13f58772a1


Drop libcommons-configuration2-java-doc (Closes: #1028168)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028168

Processed: Bug#1028168 marked as pending in commons-configuration2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028168 [src:commons-configuration2] commons-configuration2: Build-depends 
on NBS package, about to FTBFS
Added tag(s) pending.

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

Bug#1028175: snakemake rulename failes with asyncio has no attribute coroutine with python3.11

[Diane Trout]

Package: snakemake
Version: 7.12.1-1
Severity: serious

Dear Maintainer,

I noticed that snakemake-modes tests were failing while I was trying to build
the package.

Eventually I found that running the snakemake executable was failing with
python 3.11, but worked with 3.10.

Using the test Snakefile from snakemake-mode for the tests I ran the command
with both python3.11 and python3.10. The results are below.

I should probably go try to package the throttle library and upload it to NEW.

Snakemake's upstream patched snakemake to use a different library throttle in
https://github.com/snakemake/snakemake/issues/1952

$ python3.11 /usr/bin/snakemake --dryrun aa.out
Building DAG of jobs...
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/snakemake/__init__.py", line 730, in
snakemake
success = workflow.execute(
  ^
  File "/usr/lib/python3/dist-packages/snakemake/workflow.py", line 942, in
execute
self.scheduler = JobScheduler(
 ^
  File "/usr/lib/python3/dist-packages/snakemake/scheduler.py", line 105, in
__init__
from ratelimiter import RateLimiter
  File "/usr/lib/python3/dist-packages/ratelimiter.py", line 36, in 
class RateLimiter(object):
  File "/usr/lib/python3/dist-packages/ratelimiter.py", line 127, in
RateLimiter
__aexit__ = asyncio.coroutine(__exit__)
^
AttributeError: module 'asyncio' has no attribute 'coroutine'

$ python3.10 -Wd /usr/bin/snakemake --dryrun aa.out
Building DAG of jobs...
/usr/lib/python3/dist-packages/ratelimiter.py:127: DeprecationWarning:
"@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
  __aexit__ = asyncio.coroutine(__exit__)
Job stats:
job  countmin threadsmax threads
-  ---  -  -
aa   1  1  1
total1  1  1


[Sat Jan  7 19:56:59 2023]
rule aa:
output: aa.out
jobid: 0
reason: Missing output files: aa.out
resources: tmpdir=/tmp

Job stats:
job  countmin threadsmax threads
-  ---  -  -
aa   1  1  1
total1  1  1

Reasons:
(check individual jobs above for details)
missing output files:
aa

This was a dry-run (flag -n). The order of jobs does not reflect the order of
execution.
/usr/lib/python3.10/tempfile.py:999: ResourceWarning: Implicitly cleaning up

  _warnings.warn(warn_message, ResourceWarning)


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 
'oldstable-debug'), (500, 'testing'), (500, 'stable'), (110, 'unstable'), (100, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages snakemake depends on:
ii  ca-certificates  20211016
ii  libjs-bootstrap  3.4.1+dfsg-3
ii  libjs-jquery 3.6.1+dfsg+~3.5.14-1
ii  python3  3.10.6-3+b1
ii  python3-appdirs  1.4.4-3
ii  python3-configargparse   1.5.3-1
ii  python3-connection-pool  0.0.3-2
ii  python3-datrie   0.8.2-4
ii  python3-docutils 0.17.1+dfsg-3
ii  python3-git  3.1.27-1
ii  python3-jinja2   3.0.3-2
ii  python3-jsonschema   4.9.1-3
ii  python3-nbformat 5.5.0-1
ii  python3-pkg-resources65.5.0-1.1
ii  python3-psutil   5.9.4-1
ii  python3-pulp 2.6.0+dfsg-1
ii  python3-ratelimiter  1.2.0.post0-3
ii  python3-requests 2.28.1+dfsg-1
ii  python3-smart-open   5.2.1-5
ii  python3-stopit   1.1.2-2
ii  python3-tabulate 0.8.9-1
ii  python3-toposort 1.7-1
ii  python3-wrapt1.14.1-2+b1
ii  python3-yaml 6.0-3+b1

Versions of packages snakemake recommends:
ii  cwltool  3.1.20221201130942-1
ii  imagemagick  8:6.9.11.60+dfsg-1.3+b4
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.3+b4
ii  python3-azure-storage20221101+git-2
ii  python3-biopython1.80+dfsg-1
ii  python3-boto31.26.27+dfsg-1
ii  python3-botocore 1.29.27+repack-1
ii  python3-dropbox  11.34.0-1
ii  python3-flask2.2.2-2
ii  python3-ftputil  5.0.4-1
ii  python3-irodsclient  0.8.1-3
ii  python3-kubernetes   22.6.0-2
ii  python3-pygments 2.13.0+dfsg-1
ii  python3-tz   2022.7-1
ii  python3-urllib3  1.26.12-1
ii  python3-yappi1.4.0-1

Versions of packages 

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

[Aaron M. Ucko]

Hi, Adrian.

In principle, the existing Recommends relationship should suffice, even
when using FLTK's CMake integration; reverse dependencies should either
explicitly build-depend on fluid or explicitly define FLTK_SKIP_FLUID as
appropriate.  That said, I see that giada already does the latter, so
I'll take a closer look when I get a chance.

> This was likely broken by 1.3.8-5, the fix for #1017271 did
> touch the cmake files:

It merely accounted for a change in where CMake placed them, but it's
plausible that some other recent change to CMake's behavior broke the
logic to honor FLTK_SKIP_FLUID (which I've confirmed remains present).

Thanks for the report (reminiscent of [1], FWIW), and sorry for the
trouble!

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855040

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#1028174: zfs-linux FTBFS due to python3-packaging

[Antonio Russo]

Package: src:zfs-linux
Version: 2.1.7-1
X-Debbugs-Cc: aeru...@aerusso.net
Severity: grave
Tags: patch

The recent upgrade of python3-packaging from 21.3-1.1 to 22.0-2 breaks
packaging.version.LegacyVersion (specifically, it removed it).  The configure
script will fail because it tries to use the unavailable class.

Matthew Ahrens has fixed this with upstream commit b72efb751 [1].

Best,
Antonio Russo


[1] 
https://github.com/openzfs/zfs/commit/b72efb751147ab57afd1588a15910f547cb22600

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

[Vincent Lefevre]

On 2023-01-07 20:05:59 +0100, Sven Joachim wrote:
> >> 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.

I track the diffs in etc, and it seems that 2.3-33 and later did
nothing wrong. Dangling symlinks were removed after the upgrade
to anacron 2.3-34, but these were *dangling* symlinks, so that
this should have no effect. See the bug I reported:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993348

Dangling symlinks are bad as they can break other tools
(e.g. checkrestart, which was the reason I reported this bug).

> > but I get mail from failing cron scripts.
> 
> What does "systemctl status anacron.service" print?

○ anacron.service - Run anacron jobs
 Loaded: loaded (/lib/systemd/system/anacron.service; disabled; preset: 
enabled)
 Active: inactive (dead)
   Docs: man:anacron
 man:anacrontab

And anacron is no longer in the timers (systemctl list-timers).

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

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

[tony mancill]

Hi Scott,

On Sat, Jan 07, 2023 at 07:08:10PM -0500, Scott Kitterman wrote:
> 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.

Thank you for filing these bugs.  I will take care of them, as this is
some left-over work from my upload of commons-vfs in response to its
FTBFS when libcommons-net-java-doc was dropped.

Assuming I've caught them all (below), the transitive dependency graph
doesn't have too many nodes, and we should be able to remove these Java
-doc packages fairly quickly.

For context, cleaning up these -doc packages is something that members
of the Java Team have proposed in the past.  Now is the time...

Thanks,
tony


$ reverse-depends -b -l libcommons-vfs-java
commons-configuration
commons-configuration2
ivy
mondrian
sbt-ivy

$ reverse-depends -b -l libcommons-configuration-java-doc
doxia
libowasp-esapi-java

$ reverse-depends -b -l libcommons-configuration2-java-doc
(null)

$ reverse-depends -b -l ivy-doc   
(null)

$ reverse-depends -b -l libowasp-esapi-java-doc
(null)

There is no libmondrian-java-doc package.

And on the doxia side:

$ reverse-depends -b -l libdoxia-java-doc
doxia-sitetools
maven-doxia-tools
maven-reporting-impl

$ reverse-depends -b -l libdoxia-sitetools-java-doc
(null)

$ reverse-depends -b -l libmaven-doxia-tools-java-doc
(null)

$ reverse-depends -b -l libmaven-reporting-impl-java-doc
(null)


signature.asc
Description: PGP signature

Bug#1028172: tiledarray: FTBFS in unstable

[Steve Langasek]

Source: tiledarray
Version: 1.0.0-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar

Hi Michael,

tiledarray's build-dependencies are now satisfied in unstable (bug
#1014548), but it fails to build from source :)

[...]
CMake Error at /usr/share/cmake-3.25/Modules/CMakeTestCXXCompiler.cmake:63 
(message):
  The C++ compiler

"/usr/bin/c++"

  is not able to compile a simple test program.

  It fails with the following output:

Change Dir: 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98

Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_d2ec9/fast && 
gmake[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98'
/usr/bin/gmake  -f CMakeFiles/cmTC_d2ec9.dir/build.make 
CMakeFiles/cmTC_d2ec9.dir/build
gmake[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98'
Building CXX object CMakeFiles/cmTC_d2ec9.dir/testCXXCompiler.cxx.o
/usr/bin/c++   -I/usr/include/x86_64-linux-gnu/mpich  -o 
CMakeFiles/cmTC_d2ec9.dir/testCXXCompiler.cxx.o -c 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98/testCXXCompiler.cxx
Linking CXX executable cmTC_d2ec9
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_d2ec9.dir/link.txt 
--verbose=1
/usr/bin/c++ -I/usr/include/x86_64-linux-gnu/mpich  -lmpich -lpthread 
-lhwloc -lucp -lucs -lrt  CMakeFiles/cmTC_d2ec9.dir/testCXXCompiler.cxx.o -o 
cmTC_d2ec9 
/usr/bin/ld: cannot find -lhwloc: No such file or directory
/usr/bin/ld: cannot find -lucp: No such file or directory
/usr/bin/ld: cannot find -lucs: No such file or directory
collect2: error: ld returned 1 exit status
gmake[3]: *** [CMakeFiles/cmTC_d2ec9.dir/build.make:99: cmTC_d2ec9] Error 1
gmake[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98'
gmake[2]: *** [Makefile:127: cmTC_d2ec9/fast] Error 2
gmake[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98'
[...]

  
(https://buildd.debian.org/status/fetch.php?pkg=tiledarray=amd64=1.0.0-1=1673126398=0)


Possibly an issue in a build-dependency, I see that these library options
come from the output of `pkg-config --libs-only-l mpi` but libmpich-dev
apparently doesn't depend on the packages providing the libs in its output.

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


signature.asc
Description: PGP signature

Bug#1028171: freecad FTBFS with Python 3.11 as default version

[Adrian Bunk]

Source: freecad
Version: 0.20.1+dfsg1-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=freecad=amd64=0.20.1%2Bdfsg1-2%2Bb2=1673131196=0

...
/<>/src/Base/ConsoleObserver.cpp: In member function 
‘std::stringstream& Base::LogLevel::prefix(std::stringstream&, const char*, 
int)’:
/<>/src/Base/ConsoleObserver.cpp:269:41: error: invalid use of 
incomplete type ‘PyFrameObject’ {aka ‘struct _frame’}
  269 | src = PyUnicode_AsUTF8(frame->f_code->co_filename);
  | ^~
In file included from /usr/include/python3.11/Python.h:42,
 from /<>/src/Base/ConsoleObserver.cpp:31:
/usr/include/python3.11/pytypedefs.h:22:16: note: forward declaration of 
‘PyFrameObject’ {aka ‘struct _frame’}
   22 | typedef struct _frame PyFrameObject;
  |^~
make[4]: *** [src/Base/CMakeFiles/FreeCADBase.dir/build.make:388: 
src/Base/CMakeFiles/FreeCADBase.dir/ConsoleObserver.cpp.o] Error 1

Bug#1028170: maven-doxia-tools: Build-depends on NBS package, will FTBFS soon

[Scott Kitterman]

Source: maven-doxia-tools
Version: 1.4-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source

* source package doxia version 1.11.1-1 no longer builds
  binary package(s): libdoxia-java-doc
  - broken Build-Depends:
maven-doxia-tools: libdoxia-java-doc

Once libdoxia-java-doc is decrufted, then this package will FTBFS.

Scott K

Bug#1028169: maven-reporting-impl: Build-depends on NBS package, will soon FTBS

[Scott Kitterman]

Source: maven-reporting-impl
Version: 3.0.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

* source package doxia version 1.11.1-1 no longer builds
  binary package(s): libdoxia-java-doc
  - broken Build-Depends:
maven-reporting-impl: libdoxia-java-doc

Once libdoxia-java-doc is decrufted, this package will start to FTBFS.

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

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#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=all=0.1.0-1=1673131542=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
...

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#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=amd64=0.22.0-1%2Bb1=1672996393=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

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#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#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#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#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#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#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#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
  : :' :  
  `. `'   
`-

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#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

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#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#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#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#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#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=i386=4.3.6-1=1673038926=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: 

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)
> 

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)
>  

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#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

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'
...

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#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 

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#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: 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#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

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& 

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 

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=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"
...

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#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

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

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#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 ---

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

[Bastian Germann]

Hi Andreas,

Any news on this? The freeze is nearing.

Thanks,
Bastian

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#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 

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#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#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#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=i386=4.3.6-1=1673038926=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: 

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#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

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#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

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:
 

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#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?

[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#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#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

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#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 ---

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#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=amd64=5.15.2-2.3%2Bb4=1672846001=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

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#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 

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 

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: 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