Bug#1004408: marked as done (odpic: binary-any FTBFS)

[Debian Bug Tracking System]

Your message dated Thu, 27 Jan 2022 03:37:33 +
with message-id 
and subject line Bug#1004408: fixed in odpic 4.3.0-2
has caused the Debian Bug report #1004408,
regarding odpic: binary-any FTBFS
to be marked as done.

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

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


-- 
1004408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: odpic
Version: 4.3.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=odpic=4.3.0-1

...
 debian/rules clean
dh clean --with sphinxdoc
dh: error: unable to load addon sphinxdoc: Can't locate 
Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: /etc/perl 
/usr/local/lib/aarch64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 
/usr/lib/aarch64-linux-gnu/perl5/5.32 /usr/share/perl5 
/usr/lib/aarch64-linux-gnu/perl-base /usr/lib/aarch64-linux-gnu/perl/5.32 
/usr/share/perl/5.32 /usr/local/lib/site_perl) at (eval 12) line 1.
BEGIN failed--compilation aborted at (eval 12) line 1.

make: *** [debian/rules:14: clean] Error 25
--- End Message ---
--- Begin Message ---
Source: odpic
Source-Version: 4.3.0-2
Done: Joseph Nahmias 

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

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

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

Debian distribution maintenance software
pp.
Joseph Nahmias  (supplier of updated odpic package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jan 2022 22:09:04 -0500
Source: odpic
Architecture: source
Version: 4.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Joseph Nahmias 
Changed-By: Joseph Nahmias 
Closes: 1004408
Changes:
 odpic (4.3.0-2) unstable; urgency=medium
 .
   * [eb2e04a] update homepage URL
   * [2cfc490] add dep on libaio1 needed by Oracle Instant Client
   * [d9a5e64] move python3-sphinx to Build-Deps (Closes: 1004408)
Checksums-Sha1:
 7432bc836704407dc1b6278e68ca6c0cb6820259 1944 odpic_4.3.0-2.dsc
 5ece4356eebfc767b6d0aa3edc2e45145f8fde89 8172 odpic_4.3.0-2.debian.tar.xz
 7b758350f34c0c21ace367915e0202b4c27119f1 8028 odpic_4.3.0-2_amd64.buildinfo
Checksums-Sha256:
 e52b5122179f24ea38fb829b23dfa057ee0d4c6c1cb9f26082a006a744fb8d01 1944 
odpic_4.3.0-2.dsc
 0822a37fbf4674f946f09c84a3239df5598e8091a029d4c1b9d620c03352c258 8172 
odpic_4.3.0-2.debian.tar.xz
 e799628f1bf65b2e31db5dc6f08e4ec1454346389d17db4f8e00ae2e2539c08c 8028 
odpic_4.3.0-2_amd64.buildinfo
Files:
 b5400c4d8385a686b7f4f43daf7f9391 1944 contrib/libs optional odpic_4.3.0-2.dsc
 e770786661d5e62b866ecf5d336a38e2 8172 contrib/libs optional 
odpic_4.3.0-2.debian.tar.xz
 d95ceeb146cecfac60778b425181e891 8028 contrib/libs optional 
odpic_4.3.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEcxc7CTsDz7hRCK0UsRvZGQeaO5gFAmHyD0sACgkQsRvZGQea
O5hF9g//cc7kubYmPc4QYHTkdO9Y9+3YbLNTEpNRSinco876j0y/hhIvNxbXM6t7
l4jIGaQIbLJ7aSG2COeqFohyJZSVA/4AQHJB1WxczZs5J/FcWZqaHT3aCuBXBWUS
eCJim/WRxC6e9lmqhsYVza4Eh7ldF5KkR5y3EoLvy7I0qqfF4RbwD3ebR9aZTH0/
E3eVNpWiS1VnB7WHugynusx7NwNh3x09fTjoOinkh595yTmEJf7A2UWdg/eiyp0/
6aDVYby/8n/rO0IoKzEvGPYeu7QbIrXJtwP/Rhoh7Pno1r5Tj1IUW7qxfhakvCSm
QjZMLRrf/DRbjtbJ/pjvhI1JHf+4BB3dLt/37rahh7vRngLaTfNgg+JewRIkffMd
c5csxTrdMHyAy5cEN2x7sMAXZvErp+LfVHxYSOQqeyeEsxoOeQc6JS9aZCszLSxx
hpQYpcUKtU/AZZo5EDF1LYB9EcFQJgzZYcUkzHcHy6JqgmVpP1nUsVN82ZXI49sY
iKiSh+wol2GSDhrZ6iDvug85g6t6CPaKIFnXGg8F6K0EoFQfiU42iUeqKZGCcdFG
zVK5nuMxSJT/NShanPfruPTT8YgKUzqmAE4z8DL+zFNpMx+P1q0tWehOj8znwwZ+
FJ0+ev7alN/mCkmbWYDl3K6urfo+wtqvm6jAeoJCuMObdOf2qMo=
=xeZn
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Thu, 27 Jan 2022 02:38:38 +
with message-id 
and subject line Bug#965743: fixed in mysqmail 0.4.9-10.3
has caused the Debian Bug report #965743,
regarding mysqmail: 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.)


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

Hi,

The package mysqmail 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: mysqmail
Source-Version: 0.4.9-10.3
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
mysqmail, 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.
Andreas Beckmann  (supplier of updated mysqmail package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Jan 2022 02:08:05 +0100
Source: mysqmail
Architecture: source
Version: 0.4.9-10.3
Distribution: unstable
Urgency: medium
Maintainer: Thomas Goirand 
Changed-By: Andreas Beckmann 
Closes: 965743
Changes:
 mysqmail (0.4.9-10.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch to debhelper-compat (= 13).  (Closes: #965743)
   * Switch Priority to optional.
   * Add Pre-Depends: ${misc:Pre-Depends}.
   * Set Rules-Requires-Root: no.
Checksums-Sha1:
 10bee52e5160e601d2075f8ddf230a3eeb867029 2236 mysqmail_0.4.9-10.3.dsc
 118734a18bd8edaaba83c74b3322eeeb5ae0141e 14696 
mysqmail_0.4.9-10.3.debian.tar.xz
 d5fe5bbcc1500237b54064cd5027f8a3da2f43d6 5770 
mysqmail_0.4.9-10.3_source.buildinfo
Checksums-Sha256:
 aacef3f62490b19b235cb8f85d5ce9e965b8207f505239272399050818741692 2236 
mysqmail_0.4.9-10.3.dsc
 ab384b443e4977f9903fafdb5fd7ad54a02760176e012500d265428107d02795 14696 
mysqmail_0.4.9-10.3.debian.tar.xz
 ca716d3294c880edde48c3b7c0c44f21ad8f7cc79945afad0c5b3babcd731a3e 5770 
mysqmail_0.4.9-10.3_source.buildinfo
Files:
 98e320386657c6202881d4bf957adad1 2236 mail optional mysqmail_0.4.9-10.3.dsc
 7ce2743e3b5183b3299f35f4d3d28c37 14696 mail optional 
mysqmail_0.4.9-10.3.debian.tar.xz
 0d4faab735c00e56e657145560b66a8f 5770 mail optional 
mysqmail_0.4.9-10.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmHkwbYQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCGHbEACGVJI5YRuvffMS5/ktXJClWFOYLo3uQeeT
OOTEFzB4Ha79Le7XRsgp1GeJHhYqO2IdT4hna1lpD+LMeRTvtqSE0htY29U5rnpS
evhTS/QjlKo++Ex1SqxNWdttkXW157lrtHZBLbDVjq6rgqdTG1SMdkGqKZUs+6hV
omj9bKWluAeJWzFVaA4JQPFq9lsPgH9KJSWW1Y0tI6g7lw4/TEOGXoAroDxxuqGW
8XPye7UXPG7ud9WNpBxKJhk9CuZn0YA8hEUt/K0wPqSmM6ivKixGcDKswCvvGeKi
i9w11jcRyI/0afC8Ajbv20lh6Uyw8ILkJ/pB1SiouAI4FF2riqSAcaqeuCBCIzaT
9ZGuyZ5P0UwJJjFBXMf0kCafNmO0CsmY2COKo/pMnpm4cqeq1MLK2X4df+4PY1if
po8XSWCYgErlYYAmqkc7FEwYEhr2Y0gb2sbqHO7sf0HE5U2Zkesjvh/iT2iOE99J
Woo5o4AgGmGwubTmRRnt5DJHlRfCe6nZc9UEmQVrCnB1iteW+Fs5Kz4t6NLuHlpv
W2J+Lw9RMhTLVl4fAPF+Mgy31rrD59lEiFMgaZ6ryqT1u5vgN+T/mg0f6Rk9Z2yY

Bug#1004413: breezy: autopkgtest regression

[Adrian Bunk]

Source: breezy
Version: 3.2.1+bzr7581-1
Severity: serious

https://ci.debian.net/packages/b/breezy/testing/amd64/

...
==
ERROR: 
breezy.tests.per_workingtree.test_get_file_mtime.TestGetFileMTime.test_get_file_mtime_nested(GitWorkingTreeFormat)
--
testtools.testresult.real._StringException: log: {{{
709.353  preparing to commit
INFO  Committing to: 
/tmp/testbzr-l60a69ix.tmp/breezy.tests.per_workingtree.test_get_file_mtime.TestGetFileMTime.test_get_file_mtime_nested(GitWorkingTreeFormat)/work/tree/sub/
709.355  Selecting files for commit with filter None
INFO  added one
INFO  Committed revision 1.
709.359  Committed revid b'git-v1:224ad6defd64ea12b377b19bbd479da34028b846' as 
revno 1.
709.361  preparing to commit
INFO  Committing to: 
/tmp/testbzr-l60a69ix.tmp/breezy.tests.per_workingtree.test_get_file_mtime.TestGetFileMTime.test_get_file_mtime_nested(GitWorkingTreeFormat)/work/tree/
709.364  Selecting files for commit with filter None
INFO  added one
709.370  preparing to commit
INFO  Committing to: 
/tmp/testbzr-l60a69ix.tmp/breezy.tests.per_workingtree.test_get_file_mtime.TestGetFileMTime.test_get_file_mtime_nested(GitWorkingTreeFormat)/work/tree/sub/
709.375  Selecting files for commit with filter None
INFO  Committed revision 2.
709.379  Committed revid b'git-v1:71d4b60ca022a684e8ad5d9e29895f3c8e1daed4' as 
revno 2.
INFO  added sub
INFO  Committed revision 1.
709.384  Committed revid b'git-v1:6f1968cb6ccb852225ca9469735e1a1428d554c5' as 
revno 1.
}}}

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/breezy/git/tree.py", line 380, in 
get_file_mtime
(store, unused_path, commit_id) = change_scanner.find_last_change_revision(
  File "/usr/lib/python3/dist-packages/breezy/git/filegraph.py", line 57, in 
find_last_change_revision
target_mode, target_sha = tree_lookup_path(
  File "/usr/lib/python3/dist-packages/dulwich/object_store.py", line 1175, in 
tree_lookup_path
return tree.lookup_path(lookup_obj, path)
  File "/usr/lib/python3/dist-packages/dulwich/objects.py", line 1188, in 
lookup_path
obj = lookup_obj(sha)
  File "/usr/lib/python3/dist-packages/dulwich/object_store.py", line 138, in 
__getitem__
type_num, uncomp = self.get_raw(sha)
  File "/usr/lib/python3/dist-packages/dulwich/object_store.py", line 584, in 
get_raw
raise KeyError(hexsha)
KeyError: b'71d4b60ca022a684e8ad5d9e29895f3c8e1daed4'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/breezy/tests/per_workingtree/test_get_file_mtime.py",
 line 57, in test_get_file_mtime_nested
tree.basis_tree().get_file_mtime('sub/one'),
  File "/usr/lib/python3/dist-packages/breezy/git/tree.py", line 383, in 
get_file_mtime
raise errors.NoSuchFile(path)
breezy.errors.NoSuchFile: No such file: 'sub/one'

--
Ran 32863 tests in 916.376s

FAILED (errors=1, known_failure_count=46)
4780 tests skipped
autopkgtest [09:25:42]: test testsuite3: ---]
autopkgtest [09:25:42]: test testsuite3:  - - - - - - - - - - results - - - - - 
- - - - -
testsuite3   FAIL non-zero exit status 1

Bug#1003490: marked as done (u-boot: FTBFS on arch:all with qemu-ppce500 target)

[Debian Bug Tracking System]

Your message dated Thu, 27 Jan 2022 00:35:51 +
with message-id 
and subject line Bug#1003490: fixed in u-boot 2022.01+dfsg-2
has caused the Debian Bug report #1003490,
regarding u-boot: FTBFS on arch:all with qemu-ppce500 target
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.)


-- 
1003490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: u-boot
Version: 2022.01+dfsg1-1
Severity: serious
X-Debbugs-Cc: debian-powe...@lists.debian.org, q...@packages.debian.org, 
binut...@packages.debian.org

Something in the toolchain recently changed which causes u-boot arch:all
build to FTBFS... I suspect binutils, as building in "bookworm" still
works fine where binutils hasn't yet migrated.

On arch:all builds the qemu-ppce500 target is cross-compiled.

Full log:

  
https://buildd.debian.org/status/fetch.php?pkg=u-boot=all=2022.01%2Bdfsg-1=1641860624=0

The hopefully relevent lines from the build log:

  powerpc-linux-gnu-gcc -Wp,-MD,arch/powerpc/cpu/mpc85xx/.tlb.o.d -nostdinc 
-isystem /usr/lib/gcc-cross/powerpc-linux-gnu/11/include -Iinclude  
-I/<>/include  -I/<>/arch/powerpc/include -include 
/<>/include/linux/kconfig.h  
-I/<>/arch/powerpc/cpu/mpc85xx -Iarch/powerpc/cpu/mpc85xx 
-D__KERNEL__ -D__UBOOT__ -Wall -Wstrict-prototypes -Wno-format-security 
-fno-builtin -ffreestanding -std=gnu11 -fshort-wchar -fno-strict-aliasing 
-fno-PIE -Os -fno-stack-protector -fno-delete-null-pointer-checks 
-Wno-pointer-sign -Wno-stringop-truncation -Wno-zero-length-bounds 
-Wno-array-bounds -Wno-stringop-overflow -Wno-maybe-uninitialized 
-fmacro-prefix-map=/<>/= -g -fstack-usage -Wno-format-nonliteral 
-Wno-address-of-packed-member -Wno-unused-but-set-variable -Werror=date-time 
-Wno-packed-not-aligned -D__powerpc__ -ffixed-r2 -m32 -fno-ira-hoist-pressure 
-Wa,-me500 -msoft-float -mno-string -fpic -mrelocatable -ffunction-sections 
-fdata-sections -mcall-linux -msingle-pic-base -fno-jump-tables -pipe
-DKBUILD_BASENAME='"tlb"'  -DKBUILD_MODNAME='"tlb"' -c -o 
arch/powerpc/cpu/mpc85xx/tlb.o /<>/arch/powerpc/cpu/mpc85xx/tlb.c
...
{standard input}: Assembler messages:
{standard input}:127: Error: unrecognized opcode: `tlbre'
{standard input}:418: Error: unrecognized opcode: `tlbre'
{standard input}:821: Error: unrecognized opcode: `msync'
{standard input}:821: Error: unrecognized opcode: `tlbwe'
{standard input}:884: Error: unrecognized opcode: `tlbsx'
make[4]: *** [/<>/scripts/Makefile.build:253: 
arch/powerpc/cpu/mpc85xx/tlb.o] Error 1
make[3]: *** [/<>/Makefile:1810: arch/powerpc/cpu/mpc85xx] Error 2
make[3]: *** Waiting for unfinished jobs
  powerpc-linux-gnu-gcc -Wp,-MD,arch/powerpc/lib/.traps.o.d -nost


If anyone has thoughts what might be the issue, please chime in!


I could remove qemu-ppce500 from the build targets(all other targets
build fine); I am not sure if it is used by qemu or if qemu builds all
it's own firmwares.


live well,
  vagrant


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: u-boot
Source-Version: 2022.01+dfsg-2
Done: Vagrant Cascadian 

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

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

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

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated u-boot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 26 Jan 2022 11:58:27 -0800
Source: u-boot
Architecture: source
Version: 2022.01+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Vagrant Cascadian 
Changed-By: Vagrant Cascadian 
Closes: 1003490
Changes:
 u-boot (2022.01+dfsg-2) unstable; urgency=medium
 .
   * debian/patches: Fix building qemu-ppce500 target with binutils
 2.38. Thanks to Aurelien Jarno! (Closes: #1003490)
   * debian/patches: Update to newer riscv64 default ISA spec.
 Thanks to Aurelien Jarno! (Closes: #1003490)
   * debian/control: Add versioned Build-Depends on binutils.
   * debian/control: Update versioned Build-Depends on opensbi.
Checksums-Sha1:
 

Bug#1003490: marked as pending in u-boot

[Vagrant Cascadian]

Control: tag -1 pending

Hello,

Bug #1003490 in u-boot 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/u-boot/-/commit/3461e257b9709fd32422792b759ed5037cd1055d


debian/patches: Fix building qemu-ppce500 target with binutils 2.38.
Thanks to Aurelien Jarno! (Closes: #1003490)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1003490

Bug#1003490: marked as pending in u-boot

[Vagrant Cascadian]

Control: tag -1 pending

Hello,

Bug #1003490 in u-boot 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/u-boot/-/commit/395014db8971964a55103b8b9b242fea188f1c03


debian/patches: Update to newer riscv64 default ISA spec.
Thanks to Aurelien Jarno! (Closes: #1003490)

Fixes FTBFS with newer GCC and binutils.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1003490

Processed: Bug#1003490 marked as pending in u-boot

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1003490 [u-boot] u-boot: FTBFS on arch:all with qemu-ppce500 target
Added tag(s) pending.

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

Processed: Bug#1003490 marked as pending in u-boot

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1003490 [u-boot] u-boot: FTBFS on arch:all with qemu-ppce500 target
Ignoring request to alter tags of bug #1003490 to the same tags previously set

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

Processed: retitle 1004411 to asl FTBFS with vtk 9.1

[Debian Bug Tracking System]

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

> retitle 1004411 asl FTBFS with vtk 9.1
Bug #1004411 [src:asl] asl FTBFA with vtk 9.1
Changed Bug title to 'asl FTBFS with vtk 9.1' from 'asl FTBFA with vtk 9.1'.
> thanks
Stopping processing here.

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

Bug#1004411: asl FTBFA with vtk 9.1

[Adrian Bunk]

Source: asl
Version: 0.1.7-3
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/AvtechScientific/ASL/issues/48

https://buildd.debian.org/status/logs.php?pkg=asl=0.1.7-3%2Bb1

...
   debian/rules override_dh_auto_configure-arch
make[1]: Entering directory '/<>'
dh_auto_configure -- -DBUILD_SHARED_LIBS=ON 
-DCMAKE_LIBRARY_ARCHITECTURE="x86_64-linux-gnu" -DWITH_EXAMPLES=OFF 
-DWITH_MATIO=ON -DWITH_TESTS=OFF -DWITH_API_DOC=OFF
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DBUILD_SHARED_LIBS=ON -DCMAKE_LIBRARY_ARCHITECTURE=x86_64-linux-gnu 
-DWITH_EXAMPLES=OFF -DWITH_MATIO=ON -DWITH_TESTS=OFF -DWITH_API_DOC=OFF ..
-- The C compiler identification is GNU 11.2.0
-- The CXX compiler identification is GNU 11.2.0
-- 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
-- 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
-- Looking for CL_VERSION_2_0
-- Looking for CL_VERSION_2_0 - found
-- Found OpenCL: /usr/lib/x86_64-linux-gnu/libOpenCL.so (found suitable version 
"2.0", minimum required is "1.1") 
-- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake  
found components: program_options filesystem system 
CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/vtk-9.1/vtkDetectLibraryType.cmake:23 (message):
  The `PATH` argument is required.
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/vtk-9.1/patches/99/FindHDF5.cmake:1066 
(vtk_detect_library_type)
  
/usr/lib/x86_64-linux-gnu/cmake/vtk-9.1/VTK-vtk-module-find-packages.cmake:444 
(find_package)
  /usr/lib/x86_64-linux-gnu/cmake/vtk-9.1/vtk-config.cmake:150 (include)
  CMakeLists.txt:56 (find_package)


-- Configuring incomplete, errors occurred!

Bug#1004409: libslurm-dev: slurm/slurm_version.h is missing

[Adrian Bunk]

Package: libslurm-dev
Version: 21.08.5-1.1
Severity: serious
Tags: ftbfs
Control: affects -1 src:mpich

$ cat test.c
#include 
$ gcc -c test.c
In file included from test.c:1:
/usr/include/slurm/slurm.h:55:10: fatal error: slurm/slurm_version.h: No such 
file or directory
   55 | #include 
  |  ^~~
compilation terminated.
$

Processed: libslurm-dev: slurm/slurm_version.h is missing

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:mpich
Bug #1004409 [libslurm-dev] libslurm-dev: slurm/slurm_version.h is missing
Added indication that 1004409 affects src:mpich

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

Bug#1004408: odpic: binary-any FTBFS

[Adrian Bunk]

Source: odpic
Version: 4.3.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=odpic=4.3.0-1

...
 debian/rules clean
dh clean --with sphinxdoc
dh: error: unable to load addon sphinxdoc: Can't locate 
Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: /etc/perl 
/usr/local/lib/aarch64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 
/usr/lib/aarch64-linux-gnu/perl5/5.32 /usr/share/perl5 
/usr/lib/aarch64-linux-gnu/perl-base /usr/lib/aarch64-linux-gnu/perl/5.32 
/usr/share/perl/5.32 /usr/local/lib/site_perl) at (eval 12) line 1.
BEGIN failed--compilation aborted at (eval 12) line 1.

make: *** [debian/rules:14: clean] Error 25

Processed: block 1002778 with 1004046

[Debian Bug Tracking System]

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

> block 1002778 with 1004046
Bug #1002778 {Done: Sergio Durigan Junior } 
[src:python-aioamqp] python-aioamqp: FTBFS: ModuleNotFoundError: No module 
named 'pamqp.specification'
1002778 was not blocked by any bugs.
1002778 was not blocking any bugs.
Added blocking bug(s) of 1002778: 1004046
> thanks
Stopping processing here.

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

Bug#1004403: marked as done (src:carbon-c-relay: fails to migrate to testing for too long: FTBFS on mips*el)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 22:19:11 +
with message-id 
and subject line Bug#1004403: fixed in carbon-c-relay 3.7.3-2
has caused the Debian Bug report #1004403,
regarding src:carbon-c-relay: fails to migrate to testing for too long: FTBFS 
on mips*el
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.)


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

Source: carbon-c-relay
Version: 3.7.2-1
Severity: serious
Control: close -1 3.7.3-1
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:carbon-c-relay has been trying to migrate 
for 61 days [2]. Hence, I am filing this bug. Your package fails to 
build from source on mipsel and mips64el while it built there in the past.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: carbon-c-relay
Source-Version: 3.7.3-2
Done: Bernd Zeimetz 

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

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

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

Debian distribution maintenance software
pp.
Bernd Zeimetz  (supplier of updated carbon-c-relay package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jan 2022 22:59:39 +0100
Source: carbon-c-relay
Architecture: source
Version: 3.7.3-2
Distribution: unstable
Urgency: medium
Maintainer: Bernd Zeimetz 
Changed-By: Bernd Zeimetz 
Closes: 1004403
Changes:
 carbon-c-relay (3.7.3-2) unstable; urgency=medium
 .
   * [e3a05ae] Disable tests for now.
 We have segfaults/timeouts on buildds I was not able to reproduce yet.
 (Closes: #1004403)
Checksums-Sha1:
 1692aa8c21160bac9c683e79b619d7e8385adfb7 1939 carbon-c-relay_3.7.3-2.dsc
 6ae7c2b9556524443e2660ffd9eae6c01dd6e89d 7348 
carbon-c-relay_3.7.3-2.debian.tar.xz
 5d68b1a8188e9d57f90cd0e591b9a8957d3593fa 7007 
carbon-c-relay_3.7.3-2_source.buildinfo
Checksums-Sha256:
 5b1b0839de46cb3083413e0587a0c6fc61a05499d2787b20d2871e9d9bf4c052 1939 
carbon-c-relay_3.7.3-2.dsc
 9f8f28b5db20238bb00641d21e51ab964303fe62040b41a6c521b5fd0276c27b 7348 
carbon-c-relay_3.7.3-2.debian.tar.xz
 125dadfa6f3ddf5cc78defb0af9ffcfb5e50055ec27b414ef6eb367ec64d7a9c 7007 
carbon-c-relay_3.7.3-2_source.buildinfo
Files:
 51b12f4764119407a48d1e0c25a5ed6b 1939 net optional carbon-c-relay_3.7.3-2.dsc
 5c8a72ab0f72580ab942e83a2c5e84e3 7348 net optional 
carbon-c-relay_3.7.3-2.debian.tar.xz
 5d7a07e9b9657a515422c9b2ee5c1ec1 7007 net optional 
carbon-c-relay_3.7.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAmHxxHQACgkQ6zYXGm/5
Q1/92A//dJMEILfMb5nbhyC/xIAO8t+6iR+6zCXUf1zM6RvrndwPshU1D/CdUd8j

Processed: src:carbon-c-relay: fails to migrate to testing for too long: FTBFS on mips*el

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.7.3-1
Bug #1004403 [src:carbon-c-relay] src:carbon-c-relay: fails to migrate to 
testing for too long: FTBFS on mips*el
Marked as fixed in versions carbon-c-relay/3.7.3-1.
Bug #1004403 [src:carbon-c-relay] src:carbon-c-relay: fails to migrate to 
testing for too long: FTBFS on mips*el
Marked Bug as done

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

Bug#1004403: src:carbon-c-relay: fails to migrate to testing for too long: FTBFS on mips*el

[Paul Gevers]

Source: carbon-c-relay
Version: 3.7.2-1
Severity: serious
Control: close -1 3.7.3-1
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:carbon-c-relay has been trying to migrate 
for 61 days [2]. Hence, I am filing this bug. Your package fails to 
build from source on mipsel and mips64el while it built there in the past.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!

[Paul Gevers]

Hi all,

On 04-12-2021 22:44, Paul Gevers wrote:

On Thu, 02 Dec 2021 13:44:15 +0100 Paul Gevers  wrote:

The last couple of days, two of the ci.debian.net arm64 workers became
unresponsive. The systems were rebooted and I found the message in
the journal pasted below.


Of course the absence of these failures doesn't prove the bug is gone, 
but since upgrading our systems to 5.10.84-1 (on 20 December 2021), I 
have not seen this failure again. Maybe it's about time we close this 
bug and assume it's fixed in version 5.10.84-1?


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: bug 1004376 is forwarded to https://github.com/ADOdb/ADOdb/issues/793

[Debian Bug Tracking System]

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

> forwarded 1004376 https://github.com/ADOdb/ADOdb/issues/793
Bug #1004376 [src:libphp-adodb] libphp-adodb: CVE-2021-3850 - Authentication 
Bypass in PostgreSQL connections
Set Bug forwarded-to-address to 'https://github.com/ADOdb/ADOdb/issues/793'.
> thanks
Stopping processing here.

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

Bug#1002370: marked as done (python-pint: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar')

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 20:51:15 +
with message-id 
and subject line Bug#1002370: fixed in python-pint 0.18-1
has caused the Debian Bug report #1002370,
regarding python-pint: FTBFS: AttributeError: module 'mistune' has no attribute 
'BlockGrammar'
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=. python3 -m sphinx -b html docs 
> debian/python-pint-doc/usr/share/doc/python-pint-doc/html
> Running Sphinx v4.3.2
> Matplotlib created a temporary config/cache directory at 
> /tmp/matplotlib-6xl3kqhf because the default path 
> (/sbuild-nonexistent/.config/matplotlib) is not a writable directory; it is 
> highly recommended to set the MPLCONFIGDIR environment variable to a writable 
> directory, in particular to speed up the import of Matplotlib and to better 
> support multiprocessing.
> 
> Exception occurred:
>   File 
> "/usr/lib/python3/dist-packages/nbconvert/filters/markdown_mistune.py", line 
> 31, in 
> class MathBlockGrammar(mistune.BlockGrammar):
> AttributeError: module 'mistune' has no attribute 'BlockGrammar'
> The full traceback has been saved in /tmp/sphinx-err-vjjnom6g.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[1]: *** [debian/rules:13: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/python-pint_0.16.1-1_unstable.log

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-pint package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jan 2022 20:52:41 +0100
Source: python-pint
Architecture: source
Version: 0.18-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andreas Tille 
Closes: 1002370
Changes:
 python-pint (0.18-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Apply multi-arch hints.
 + python-pint-doc: Add Multi-Arch: foreign.
   * Remove obsolete field Name from debian/upstream/metadata (already present 
in
 machine-readable debian/copyright).
 .
   [ Andreas Tille ]
   * New upstream version
 Closes: #1002370
   * Standards-Version: 4.6.0 (routine-update)
   * Add salsa-ci file (routine-update)
   * Build-Depends: python3-pytest-subtests 
Checksums-Sha1:
 8da0a369e7dd1737f1e43d0761467034776a65bf 2385 python-pint_0.18-1.dsc
 7cd4ba6da2b4206685336969c62d5f3b4072ebf4 270007 python-pint_0.18.orig.tar.gz
 ffdd0a202161508130de97f4c1bca0b89dcc29ce 6020 python-pint_0.18-1.debian.tar.xz
 e2bab34f0db5f2bca3cf6a018d9edfa7f7a7b641 11477 
python-pint_0.18-1_amd64.buildinfo
Checksums-Sha256:
 2fa4db5d57d7354935b87dd143b1481fa634bd2c647185ae538f84bcd1b778fa 2385 
python-pint_0.18-1.dsc
 8416df5ecd678fe82777523a6b8613236c89ea67e76116c343a7ee6147499132 270007 

Bug#999575: marked as done (elan: error: failed to select a version for the requirement `itertools = "^0.9.0"`)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 20:35:03 +
with message-id 
and subject line Bug#999575: fixed in elan 1.3.1-1
has caused the Debian Bug report #999575,
regarding elan: error: failed to select a version for the requirement 
`itertools = "^0.9.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.)


-- 
999575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: elan
Version: 1.0.6-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org

| debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', '-j4', 
'--target', 'x86_64-unknown-linux-gnu'],) {}
| error: failed to select a version for the requirement `itertools = "^0.9.0"`
| candidate versions found which didn't match: 0.10.1
| location searched: directory source `/<>/debian/cargo_registry` 
(which is replacing registry `crates-io`)
| required by package `elan v1.0.6 (/<>)`
| perhaps a crate was updated and forgotten to be re-vendored?
| dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
| make: *** [debian/rules:19: binary-arch] Error 25

https://buildd.debian.org/status/fetch.php?pkg=elan=amd64=1.0.6-1%2Bb1=1636717403=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: elan
Source-Version: 1.3.1-1
Done: Christopher Hoskin 

We believe that the bug you reported is fixed in the latest version of
elan, 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.
Christopher Hoskin  (supplier of updated elan package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 26 Jan 2022 20:16:00 +
Source: elan
Architecture: source
Version: 1.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Christopher Hoskin 
Changed-By: Christopher Hoskin 
Closes: 999575
Changes:
 elan (1.3.1-1) unstable; urgency=medium
 .
   [ Peter Michael Green ]
   * Non-maintainer upload.
   * Relax cargo dependencies on itertools and rand ( Closes: 999575 ).
   * Remove cargo dependency on the "vendored" feature of the openssl crate,
 it has been removed in current Debian packaging of that crate (and was a
 no-op before that)
   * Change Debian dependency to depend on librust-semver-0.9-dev
 instead of librust-semver-dev.
 .
   [ Christopher Hoskin ]
   * Add debian/gbp.conf
   * Import new upstream version (1.3.1)
   * Update patches
   * Switch to gbp pq
   * Revert support for zst archives
   * Depend on librust-zip+time-dev
   * Complete update of dependency patch
Checksums-Sha1:
 fb0d7cb671f870e8aa1a63164be1b075fb05fecb 2561 elan_1.3.1-1.dsc
 ba8d925dbc16927efaa80bc4d2619fa61e1d6a32 95935 elan_1.3.1.orig.tar.gz
 5f1b93ebe0f7403efa0fdd0bf178593b78054ba3 7104 elan_1.3.1-1.debian.tar.xz
 c4c9c3b103f687611099927b6879a591f5bf3107 14725 elan_1.3.1-1_amd64.buildinfo
Checksums-Sha256:
 f9fa836a82b0b6c2db52c39633d97b1c0a0aad8b5b7f4c83e084314b67fbf33a 2561 
elan_1.3.1-1.dsc
 8e1380a1cb20cec54f07e30519ad7bc0179d9e3d68d33c02d0476248322b5015 95935 
elan_1.3.1.orig.tar.gz
 803d99b13b7d723f70161f558adab18669c41fe7e2441cebc8d9e2c4382fc02e 7104 
elan_1.3.1-1.debian.tar.xz
 7e748dc250547ee58ce312bac76be5709487588aef020a7f71dcf6100b562b72 14725 
elan_1.3.1-1_amd64.buildinfo
Files:
 1ca4eb56c219fc53ab3bb7a9bd03403d 2561 math optional elan_1.3.1-1.dsc
 2ca7f6af1bdd6b53dda2bf23678bf9d9 95935 math optional elan_1.3.1.orig.tar.gz
 a04829775b818c226eeb5b3c741ffbef 7104 math optional elan_1.3.1-1.debian.tar.xz
 61bf797e98c730b30598f24d9171e8d7 14725 math optional 
elan_1.3.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEbctJ5K6JlvFsvhGhf6qUsnUUSpoFAmHxrTUACgkQf6qUsnUU
Spp3mBAAgiRq6wzBrgvHpr0E9uPdtjlhSHaIVG3j62Y9SfPO0oxp8WAmHFM0VG53
unmt0+6q9SbpS14+sKrUCVo1pCl10uMwrx4URgua3xlCq8HcCpymAgYXT29pkpe9
chIxwnzq9Gf+HWLqP8bsUxguwmLUvW6oH1NFKqbLxzUj0zfMAbnm6Rp/0tGevMdo
IvuqSIeShvI87DvTTsY+C9Lw9RD2tARLmHQda7uwNFetRy+82TrxEdDwV4nJGUZY

Bug#995356: python-parameterized: autopkgtest regression: AssertionError in tearDownModule

[Paul Gevers]

Hi Sandro,

On 26-01-2022 05:24, Sandro Tosi wrote:

If nobody is going to fix this issue, I am going to upload the package
removing the autopkgtest soon.


I took your NMU diff and made it a team upload, thanks!


I regret my bold action a bit, so I'll try to figure out a proper patch 
if I find time the next days.



This issue is blocking migration to
testing for too long. The package can't be easily removed because it's a
key package.


is there a publicly available list of key packages?


Yes: https://udd.debian.org/cgi-bin/key_packages.yaml.cgi

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1004397: ilorest: Fails to upgrade: Git merge conflict markers in /usr/lib/python3/dist-packages/ilorest/rdmc.py causing Python syntax error during postinst

[Axel Beckert]

Package: ilorest
Version: 3.3.0.0+ds1-1
Severity: serious

Upgrading ilorest to 3.3.0.0+ds1-1 fails for me as follows:

Setting up ilorest (3.3.0.0+ds1-1) ...
  File "/usr/lib/python3/dist-packages/ilorest/rdmc.py", line 995
<<< HEAD:ilorest/rdmc.py
^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/ilorest/rdmc.py", line 995
<<< HEAD:ilorest/rdmc.py
^^
SyntaxError: invalid syntax
dpkg: error processing package ilorest (--configure):
 installed ilorest package post-installation script subprocess returned error 
exit status 1

The offending lines are:

995 <<< HEAD:ilorest/rdmc.py
996 def ilorestcommand():
997 ===
998 
999 if __name__ == '__main__':
   1000 >>> v3.3.0.0:src/rdmc.py

And later on also:

   1034 <<< HEAD:ilorest/rdmc.py
   1035 return RDMC.retcode
   1036 
   1037 if __name__ == '__main__':
   1038 # Return code
   1039 sys.exit(ilorestcommand())
   1040 ===
   1041 # Return code
   1042 sys.exit(RDMC.retcode)
   1043 >>> v3.3.0.0:src/rdmc.py

Oh, and btw.,
https://salsa.debian.org/openstack-team/third-party/python-redfish-utility
(as mentioned in the Vcs-Browse header) gives a "404 Not Found".

-- 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')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
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

Versions of packages ilorest depends on:
ii  libjs-sphinxdoc 4.3.2-1
ii  python3 3.9.8-1
ii  python3-certifi 2020.6.20-1
ii  python3-colorama0.4.4-1
ii  python3-decorator   4.4.2-2
ii  python3-ilorest 3.3.0.0+ds-1
ii  python3-json-pointer2.1-3
ii  python3-jsondiff1.1.1-4
ii  python3-jsonpatch   1.32-2
ii  python3-jsonpath-rw 1.4.0-4
ii  python3-pbr 5.6.0-2
ii  python3-ply 3.11-5
ii  python3-prompt-toolkit  3.0.24-1
ii  python3-pyaes   1.6.1-4
ii  python3-pyudev  0.22.0-2
ii  python3-setproctitle1.2.2-2+b1
ii  python3-setuptools  59.6.0-1.2
ii  python3-six 1.16.0-3
ii  python3-tabulate0.8.9-1
ii  python3-urllib3 1.26.5-1~exp1
ii  python3-validictory 1.1.2-2
ii  python3-wcwidth 0.1.9+dfsg1-2

ilorest recommends no packages.

ilorest suggests no packages.

-- no debconf information

Bug#1004380: marked as done (libfilament-tools: /usr/bin/resgen is already provided by mono-devel)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 17:34:15 +
with message-id 
and subject line Bug#1004380: fixed in filament 1.9.25+dfsg-3
has caused the Debian Bug report #1004380,
regarding libfilament-tools: /usr/bin/resgen is already provided by mono-devel
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.)


-- 
1004380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfilament-tools
Version: 1.9.25+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

/usr/bin/resgen (and the corresponding manpage) are already shipped by
mono-devel. Please rename that executable and its manpage.


Andreas


mono-devel=6.8.0.105+dfsg-3.2_libfilament-tools=1.9.25+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: filament
Source-Version: 1.9.25+dfsg-3
Done: Timo Röhling 

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

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

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

Debian distribution maintenance software
pp.
Timo Röhling  (supplier of updated filament package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 26 Jan 2022 18:23:13 +0100
Source: filament
Architecture: source
Version: 1.9.25+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Timo Röhling 
Changed-By: Timo Röhling 
Closes: 1004380
Changes:
 filament (1.9.25+dfsg-3) unstable; urgency=medium
 .
   * Rename resgen executable to avoid conflict with mono-devel
 (Closes: #1004380)
   * Replace BlueGL with GLEW
Checksums-Sha1:
 8565afe0ac2cd78f0111e9c6e3452e2569704153 2202 filament_1.9.25+dfsg-3.dsc
 824f02d1d318f7b4ddbba55f7c5f35f7eab86595 26832 
filament_1.9.25+dfsg-3.debian.tar.xz
 c7f635593eddadf28907e5b20eab19f57a320270 13700 
filament_1.9.25+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 20bba1ef201689b4239b48319f267851504a107de414b1d3539b56c98a600fe0 2202 
filament_1.9.25+dfsg-3.dsc
 cb103eadd8640b9b86951ee2d53945e7069f86c1e189cc961e5efc0cb12108db 26832 
filament_1.9.25+dfsg-3.debian.tar.xz
 011ea9beeaddd6f245a839d41b703326b3cb9d86c522435e735136904fd571fe 13700 
filament_1.9.25+dfsg-3_amd64.buildinfo
Files:
 2350ad8a51d4bc0482917417f1faf13f 2202 libs optional filament_1.9.25+dfsg-3.dsc
 7fd08cbaa027b23f51738e6099afd66d 26832 libs optional 
filament_1.9.25+dfsg-3.debian.tar.xz
 82794b9ad39d9054412674db2df4a11c 13700 libs optional 
filament_1.9.25+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQHIBAEBCgAyFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmHxhAkUHHJvZWhsaW5n
QGRlYmlhbi5vcmcACgkQ+C8H+466LVkaLwv+I1fNR/3+mz0tkCVpHbbv+3O3gYA0
Ps44ALJ5aDMfXaV/9mjFDjKc91Q8Wv/1uL3EGivaMnMNwZSH4pzGEOt55sXALOXM
K4qQskknPr9pX7D2qFnk4nbfdpE3H1obWz0kVmGr6sP2kJR8luPGSjBdt+GDSHy7
MiL60S4xeHKUtzwNxlb6M7Wphh4EmmLy4wi6TD+9cixotugfFyn3amQxumv65G5a
5rzaG6747xC0YwU0mA0p9Z2g2qwy0odbGwnYG6Aoe23FKgYC/IQv3JVpFyazH/al
QVZUtiQ6bX7ISvpcw93KmKCItI/PytC1kw8JofhtPqrlaPhC6CLqwsZSYiAbjQFE
+68zcB4l64KKYUxLfoLeIhfZnqky4GWRkoeD4xlRSK0V9TeuIoAE5ryZqV/w0Ya/
JDa2WvhwTCrJwy2rK3itlWq4JFU/Rscg511dCqidpO4AEg7b2TEvUEx3ZOJ9kpXE
XfQZA2quSQS8cNiLIPBfa2rOjH/SDjRXII67
=TFc3
-END PGP SIGNATURE End Message ---

Bug#1002241: marked as done (chatty: FTBFS: dh_auto_test: error: cd _build && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 17:18:43 +
with message-id 
and subject line Bug#1002241: fixed in chatty 0.6.0-1
has caused the Debian Bug report #1002241,
regarding chatty: FTBFS: dh_auto_test: error: cd _build && LC_ALL=C.UTF-8 
MESON_TESTTHREADS=4 meson test returned exit code 1
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> xvfb-run dh_auto_test
>   cd _build && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test
> ninja: Entering directory `/<>/_build'
> [1/53] Generating src/version.h with a custom command
>  1/12 Validate desktop file   OK   0.01s
>  2/12 Validate schema fileOK   0.01s
>  3/12 Validate appstream file OK   0.01s
>  4/12 settingsOK   0.01s
>  5/12 utils   OK   0.04s
>  6/12 matrix-api  OK   0.04s
>  7/12 matrix-enc  FAIL 0.04s   killed by signal 6 
> SIGABRT
> >>> G_TEST_SRCDIR=/<>/tests MALLOC_PERTURB_=220 
> >>> G_TEST_BUILDDIR=/<>/_build/tests MALLOC_CHECK_=2 
> >>> GSETTINGS_SCHEMA_DIR=/<>/_build/data 
> >>> /<>/_build/tests/matrix-enc
> 
>  8/12 matrix-utilsOK   0.03s
>  9/12 mm-account  OK   0.04s
> 10/12 matrix-db   OK   0.18s
> 11/12 account OK   0.24s
> 12/12 history OK   2.03s
> 
> 
> Ok: 11  
> Expected Fail:  0   
> Fail:   1   
> Unexpected Pass:0   
> Skipped:0   
> Timeout:0   
> 
> Full log written to /<>/_build/meson-logs/testlog.txt
>   cd _build && tail -v -n \+0 meson-logs/testlog.txt
> ==> meson-logs/testlog.txt <==
> Log of Meson test suite run on 2021-12-20T18:58:08.688019
> 
> Inherited environment: DEB_HOST_GNU_SYSTEM=linux-gnu DFLAGS=-frelease 
> DEB_BUILD_ARCH_BITS=64 DEB_TARGET_GNU_CPU=x86_64 DEB_HOST_ARCH_OS=linux 
> USER=user42 CXXFLAGS='-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security' 
> DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_TARGET_MULTIARCH=x86_64-linux-gnu 
> OBJCFLAGS='-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security' 
> DH_INTERNAL_OPTIONS=-O--builddirectory=_build DEB_BUILD_ARCH_CPU=amd64 
> DEB_HOST_ARCH_LIBC=gnu DEB_HOST_ARCH_ABI=base 
> HOME=/<>/debian/.debhelper/generated/_source/home 
> APT_CONFIG=/var/lib/sbuild/apt.conf SCHROOT_CHROOT_NAME=sid-amd64-sbuild 
> DEB_BUILD_ARCH_ENDIAN=little LDFLAGS='-Wl,-z,relro -Wl,-z,now' 
> DEB_TARGET_ARCH_BITS=64 DEB_BUILD_GNU_SYSTEM=linux-gnu MAKEFLAGS=w 
> SCHROOT_UID=1001 DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_TYPE=x86_64-linux-gnu 
> DEB_TARGET_ARCH_CPU=amd64 LOGNAME=user42 DEB_BUILD_ARCH_LIBC=gnu 
> DEB_BUILD_ARCH_ABI=base DEB_HOST_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little 
> DH_INTERNAL_OVERRIDE=dh_auto_test DEB_HOST_GNU_CPU=x86_64 LC_COLLATE=C.UTF-8 
> DEB_TARGET_GNU_SYSTEM=linux-gnu 
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games 
> DEB_TARGET_ARCH_OS=linux CFLAGS='-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security' MAKELEVEL=2 
> DEB_HOST_MULTIARCH=x86_64-linux-gnu SOURCE_DATE_EPOCH=1631518591 FCFLAGS='-g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong' 
> SCHROOT_SESSION_ID=sid-amd64-sbuild-f0830dbf-bf2b-44b2-be1e-775411aca1cc 
> SCHROOT_COMMAND='dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -sa' 
> DISPLAY=:99 OBJCXXFLAGS='-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security' LANG=C.UTF-8 
> SCHROOT_ALIAS_NAME=unstable DEB_TARGET_ARCH_LIBC=gnu DEB_TARGET_ARCH_ABI=base 
> XAUTHORITY=/tmp/xvfb-run.GWDwks/Xauthority DEB_BUILD_OPTIONS=parallel=4 
> SCHROOT_GROUP=user42 SCHROOT_USER=user42 CPPFLAGS='-Wdate-time 
> -D_FORTIFY_SOURCE=2' DH_INTERNAL_BUILDFLAGS=1 SHELL=/bin/sh 
> DEB_HOST_ARCH_BITS=64 DEB_BUILD_ARCH=amd64 
> DEB_BUILD_MAINT_OPTIONS=hardening=+all DEB_BUILD_GNU_CPU=x86_64 ASFLAGS='' 
> DEB_HOST_GNU_TYPE=x86_64-linux-gnu LC_ALL=C.UTF-8 DEB_HOST_ARCH_CPU=amd64 
> DEB_RULES_REQUIRES_ROOT=no PWD=/<> 

Bug#1004392: marked as done (systemd: Incorrect location of configuration files)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 17:36:03 +0100
with message-id <9d1acdcb30fbc80a975eba2e799ae551f39a63dd.ca...@43-1.org>
and subject line Re: Bug#1004392: systemd: Incorrect location of configuration 
files
has caused the Debian Bug report #1004392,
regarding systemd: Incorrect location of configuration files
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.)


-- 
1004392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 247.3-6
Severity: serious
Justification: Policy 10.7

Dear Maintainer,

/usr/lib/tmpfiles.d/x11.conf should be a configuration file. Entries in it must 
be disabled in order to run containers with accelerated X11 and DRI access. 

As it is under lib, changes to it are overwritten on every systemd update 
breaking all containers which run X apps with direct access to local X-server.

1. There is no way to disable it permanently.
2. There is no way to override it in a way which disables the defaults 

Actually, most of that directory does not belong in /usr - it should be under 
/etc as per Debian policy for configuration files and should be handled as 
config on
system upgrades and updates.

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser3.118
ii  libacl12.2.53-10
ii  libapparmor1   2.13.6-10
ii  libaudit1  1:3.0-2
ii  libblkid1  2.36.1-8
ii  libc6  2.31-13+deb11u2
ii  libcap21:2.44-1
ii  libcrypt1  1:4.4.18-4
ii  libcryptsetup122:2.3.5-1
ii  libgcrypt201.8.7-6
ii  libgnutls303.7.1-5
ii  libgpg-error0  1.38-2
ii  libip4tc2  1.8.7-1
ii  libkmod2   28-1
ii  liblz4-1   1.9.3-2
ii  liblzma5   5.2.5-2
ii  libmount1  2.36.1-8
ii  libpam0g   1.4.0-9+deb11u1
ii  libseccomp22.5.1-1+deb11u1
ii  libselinux13.1-3
ii  libsystemd0247.3-6
ii  libzstd1   1.4.8+dfsg-2.1
ii  mount  2.36.1-8
ii  ntp [time-daemon]  1:4.2.8p15+dfsg-1
ii  util-linux 2.36.1-8

Versions of packages systemd recommends:
ii  dbus  1.12.20-2

Versions of packages systemd suggests:
ii  policykit-10.105-31
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.140
ii  libnss-systemd   247.3-6
ii  libpam-systemd   247.3-6
ii  udev 247.3-6

-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
KillUserProcesses=yes
KillExcludeUsers=root


-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, 2022-01-26 at 15:41 +, Anton Ivanov wrote:
> /usr/lib/tmpfiles.d/x11.conf should be a configuration file. Entries
> in it must be disabled in order to run containers with accelerated
> X11 and DRI access. 
> 
> As it is under lib, changes to it are overwritten on every systemd
> update breaking all containers which run X apps with direct access to
> local X-server.
> 
> 1. There is no way to disable it permanently.
> 2. There is no way to override it in a way which disables the
> defaults 

The files in /usr can be overriden with files in /etc.  See the section
"CONFIGURATION DIRECTORIES AND PRECEDENCE" in man:tmpfiles.d(5).
(It works the same for most of systemd.)

Ansgar--- End Message ---

Bug#1004392: systemd: Incorrect location of configuration files

[Anton Ivanov]

Package: systemd
Version: 247.3-6
Severity: serious
Justification: Policy 10.7

Dear Maintainer,

/usr/lib/tmpfiles.d/x11.conf should be a configuration file. Entries in it must 
be disabled in order to run containers with accelerated X11 and DRI access. 

As it is under lib, changes to it are overwritten on every systemd update 
breaking all containers which run X apps with direct access to local X-server.

1. There is no way to disable it permanently.
2. There is no way to override it in a way which disables the defaults 

Actually, most of that directory does not belong in /usr - it should be under 
/etc as per Debian policy for configuration files and should be handled as 
config on
system upgrades and updates.

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser3.118
ii  libacl12.2.53-10
ii  libapparmor1   2.13.6-10
ii  libaudit1  1:3.0-2
ii  libblkid1  2.36.1-8
ii  libc6  2.31-13+deb11u2
ii  libcap21:2.44-1
ii  libcrypt1  1:4.4.18-4
ii  libcryptsetup122:2.3.5-1
ii  libgcrypt201.8.7-6
ii  libgnutls303.7.1-5
ii  libgpg-error0  1.38-2
ii  libip4tc2  1.8.7-1
ii  libkmod2   28-1
ii  liblz4-1   1.9.3-2
ii  liblzma5   5.2.5-2
ii  libmount1  2.36.1-8
ii  libpam0g   1.4.0-9+deb11u1
ii  libseccomp22.5.1-1+deb11u1
ii  libselinux13.1-3
ii  libsystemd0247.3-6
ii  libzstd1   1.4.8+dfsg-2.1
ii  mount  2.36.1-8
ii  ntp [time-daemon]  1:4.2.8p15+dfsg-1
ii  util-linux 2.36.1-8

Versions of packages systemd recommends:
ii  dbus  1.12.20-2

Versions of packages systemd suggests:
ii  policykit-10.105-31
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.140
ii  libnss-systemd   247.3-6
ii  libpam-systemd   247.3-6
ii  udev 247.3-6

-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
KillUserProcesses=yes
KillExcludeUsers=root


-- no debconf information

Processed: forcibly merging 1003345 1003305

[Debian Bug Tracking System]

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

> forcemerge 1003345 1003305
Bug #1003345 {Done: Cédric Boutillier } [src:ruby-sqlite3] 
ruby-sqlite3: FTBFS with SQLite3 3.37.0+
Bug #1003305 [src:ruby-sqlite3] ruby-sqlite3: FTBFS against sqlite3 3.37 or 
newer
Set Bug forwarded-to-address to 
'https://github.com/sparklemotion/sqlite3-ruby/pull/309'.
Severity set to 'serious' from 'normal'
Marked Bug as done
Marked as fixed in versions ruby-sqlite3/1.4.2-4.
Marked as found in versions ruby-sqlite3/1.4.2-3.
Added tag(s) sid, bookworm, and patch.
Merged 1003305 1003345
> thanks
Stopping processing here.

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

Bug#1004119: marked as done (fricas: libc6 2.33 bug causes assert; patch is upstream)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 16:04:21 +
with message-id 
and subject line Bug#1004119: fixed in fricas 1.3.7-4
has caused the Debian Bug report #1004119,
regarding fricas: libc6 2.33 bug causes assert; patch is upstream
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.)


-- 
1004119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fricas
Version: 1.3.7-3
Severity: grave

Since recent update to libc6 2.33 in testing it broke fricas,
please use the patch upstream in this bug:
https://savannah.gnu.org/bugs/index.php?60161
https://git.savannah.gnu.org/cgit/gcl.git/commit/?id=26a7a50d3d2ac4bc27d082f7321d16dba2b920cf

Maxima should be also affected.

P.S. Looks like https://sources.debian.org/patches/gcl/2.6.12-117/
should be compiled into fricas?

Please note that I was able to see assert on WSLv1 but somehow
it just fails in real machine. Another bug in glibc?

Thanks.
--- End Message ---
--- Begin Message ---
Source: fricas
Source-Version: 1.3.7-4
Done: Camm Maguire 

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

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

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

Debian distribution maintenance software
pp.
Camm Maguire  (supplier of updated fricas package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jan 2022 10:38:35 -0500
Source: fricas
Architecture: source
Version: 1.3.7-4
Distribution: unstable
Urgency: medium
Maintainer: Camm Maguire 
Changed-By: Camm Maguire 
Closes: 1004119
Changes:
 fricas (1.3.7-4) unstable; urgency=medium
 .
   * rebuild against latest gcl
   * Bug fix: "libc6 2.33 bug causes assert; patch is upstream", thanks to
 Валерий Заподовников (Closes: #1004119).
Checksums-Sha1:
 b98d4b450686210e38e918e8c34f1d4ec126b891 2351 fricas_1.3.7-4.dsc
 cc8dac8be6203a5fafd5324eee20048baa916f11 65004 fricas_1.3.7-4.debian.tar.xz
 00fb8eed5ae108b188d802fa68ab7f160bb57f08 7328 fricas_1.3.7-4_source.buildinfo
Checksums-Sha256:
 0e54c30c1b3416a2972df14dc40a5c90af2cff940adbe5fb5d1f71a9a823214a 2351 
fricas_1.3.7-4.dsc
 355aab4d24612eca892719b525d6196717890d4549eb8e991df642ee1d45367a 65004 
fricas_1.3.7-4.debian.tar.xz
 3067261e009921f59dcb6706bd74cad1b9e96c830379b29d694f2d03496b2c72 7328 
fricas_1.3.7-4_source.buildinfo
Files:
 7cab87cdcbb2f57ce8682eb6d327751d 2351 math optional fricas_1.3.7-4.dsc
 477ba5fc6fc938567bba969ec867e739 65004 math optional 
fricas_1.3.7-4.debian.tar.xz
 9e8e7bd80d3bebb6f934bae1abff3b5e 7328 math optional 
fricas_1.3.7-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/iFPNjaXdzJC6BbsuEXOUQ+bcU0FAmHxbI8ACgkQuEXOUQ+b
cU3q1A/9Ef1o2UVqigkehheEu3vQO7rjsAlbtefWzmcVnm3rrDCah+esAF42KqF6
ooiIOB94UPD1uxySUA/+UxR2BS2zm2Y0v82QZA5r7c+Gke6wnKegEz+VhIXLnH1H
AIC1W98bnoC1JfXxhi9irvmfGiQuMJIbWdYb64bDuS8dGzHTZyaoVTusqw3YY0Hc
vEMXQx+VU51U0RTEMPGiu1RkeR2zIP5WBoCmMhPENLMpAkn26pzE/8BqfcTToW7y
UL3jl9bKcdk8SV2af5nc0QxuscdGOdCfSTS9em6FrbigqjTJ9lnPc8rSggyn0DX4
8C1iAw8GE8cwCG+XyqQF6jc5tmzTDHDB3YAmI0nmd52ecm2zEUoQ2TRygSROPyx1
E5bCOHmaihuK2QNpJSZMJbLzw/Xvfypoo9AL0tBH1om8EoUWgPSF7XLhtqIhhEp+
KOMBhdP6st8Fzcpsv+wVEWVK5cwuPy3iameT/waFZw1vxAH008twsIVyNT88FIzI
HkOm7ZHA3a0MitB+g/3tym9Colr9Sds52gWc8whhjqMlZuOpJMpx5g2IL4cVyHWG
apa6hfXbmhjWjUm/w0UgcS72xLSTp69UThSzuTGatc69677NwxVAP5TCq12Dkui2
AX0DvzdrPeI/XzV5aGAk6ANTMJg9Tf9GWACPKZJsZ2Y5KwjNeB8=
=mxV9
-END PGP SIGNATURE End Message ---

Processed (with 1 error): forcibly merging 1003345 1003305

[Debian Bug Tracking System]

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

> forcemerge 1003345 1003305
Bug #1003345 {Done: Cédric Boutillier } [src:ruby-sqlite3] 
ruby-sqlite3: FTBFS with SQLite3 3.37.0+
Unable to merge bugs because:
package of #1003305 is 'ruby-sqlite3' not 'src:ruby-sqlite3'
Failed to forcibly merge 1003345: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#1002105: marked as done (ruby-icalendar: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: local_start.to_datetime.strftime '%Y%m%dT%H%M%S')

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 15:37:28 +
with message-id 
and subject line Bug#1002105: fixed in ruby-icalendar 2.7.1-1
has caused the Debian Bug report #1002105,
regarding ruby-icalendar: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: 
local_start.to_datetime.strftime '%Y%m%dT%H%M%S'
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.)


-- 
1002105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-icalendar
Version: 2.4.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>   Failure/Error: local_start.to_datetime.strftime '%Y%m%dT%H%M%S'
> 
>   NameError:
> undefined local variable or method `local_start' for 
> #
> Did you mean?  local_start_at
>   # ./lib/icalendar/tzinfo.rb:79:in `dtstart'
>   # ./lib/icalendar/tzinfo.rb:173:in `block in build_timezone'
>   # ./lib/icalendar/tzinfo.rb:169:in `tap'
>   # ./lib/icalendar/tzinfo.rb:169:in `build_timezone'
>   # ./lib/icalendar/tzinfo.rb:137:in `daylight'
>   # ./lib/icalendar/tzinfo.rb:103:in `ical_timezone'
>   # ./spec/tzinfo_spec.rb:8:in `block (2 levels) in '
>   # ./spec/tzinfo_spec.rb:25:in `block (3 levels) in '
> 
> Finished in 0.14041 seconds (files took 0.21245 seconds to load)
> 186 examples, 13 failures, 3 pending
> 
> Failed examples:
> 
> rspec ./spec/tzinfo_spec.rb:32 # TZInfo::Timezone no end transition only 
> creates a standard component
> rspec ./spec/tzinfo_spec.rb:21 # TZInfo::Timezone daylight recurrence rule 
> rspec ./spec/tzinfo_spec.rb:12 # TZInfo::Timezone daylight offset 
> rspec ./spec/tzinfo_spec.rb:11 # TZInfo::Timezone daylight offset 
> rspec ./spec/tzinfo_spec.rb:75 # TZInfo::Timezone dst transition is expected 
> not to raise Exception
> rspec ./spec/tzinfo_spec.rb:74 # TZInfo::Timezone dst transition is expected 
> not to raise Exception
> rspec ./spec/tzinfo_spec.rb:84 # TZInfo::Timezone dst transition 
> TZInfo::Timezone.default_dst = true is expected not to raise Exception
> rspec ./spec/tzinfo_spec.rb:89 # TZInfo::Timezone dst transition 
> TZInfo::Timezone.default_dst = false is expected not to raise Exception
> rspec ./spec/tzinfo_spec.rb:101 # TZInfo::Timezone tzname for offset 
> #daylight 
> rspec ./spec/tzinfo_spec.rb:106 # TZInfo::Timezone tzname for offset 
> #standard 
> rspec ./spec/tzinfo_spec.rb:16 # TZInfo::Timezone standard offset 
> rspec ./spec/tzinfo_spec.rb:17 # TZInfo::Timezone standard offset 
> rspec ./spec/tzinfo_spec.rb:25 # TZInfo::Timezone standard recurrence rule 
> 
> Randomized with seed 38963
> 
> Coverage report generated for RSpec to /<>/coverage. 928 / 993 
> LOC (93.45%) covered.
> Stopped processing SimpleCov as a previous error not related to SimpleCov has 
> been detected
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby2.7" failed: 


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/ruby-icalendar_2.4.1-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ruby-icalendar
Source-Version: 2.7.1-1
Done: Cédric Boutillier 

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

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

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-icalendar 
package)

(This message was generated automatically at their request; 

Bug#1004387: Filed RFP #1004388

[Enrico Zini]

Hello,

I filed the RFP at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004388


Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini 

Bug#1004387: Upstream seems abandoned

[Enrico Zini]

Package: python3-pyinotify
Version: 0.9.6-1.3
Severity: serious

Hello,

thank you for maintaining python3-pyinotify.

Looking at https://github.com/dsoprea/PyInotify it says:

   This project is unrelated to the *PyInotify* project that existed
   prior to this one (this project began in 2015). That project is
   defunct and no longer available.

and indeed, https://github.com/seb-m/pyinotify which is listed as
upstream of python3-pyinotify seems to be stuck in 2015.

To the best that I could see, https://github.com/dsoprea/PyInotify is
not packaged in Debian.

If I understand correctly, the only way to access inotify functionality
in Python with libraries in Debian at the moment is via the old
pyinotify, and at least gunicorn is requiring the newer one for
inotify-based reloading to work:

   https://docs.gunicorn.org/en/stable/settings.html#reload
   "In order to use the inotify reloader, you must have the inotify
   package installed."

I guess my next step could be filing an RFP for
https://github.com/dsoprea/PyInotify ?


Enrico

-- System Information:
Debian Release: 11.2
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages python3-pyinotify depends on:
ii  python3  3.9.2-3

python3-pyinotify recommends no packages.

Versions of packages python3-pyinotify suggests:
pn  python-pyinotify-doc  

-- no debconf information

Processed: bug 1002115 is forwarded to https://github.com/gettalong/kramdown/issues/744

[Debian Bug Tracking System]

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

> forwarded 1002115 https://github.com/gettalong/kramdown/issues/744
Bug #1002115 [src:ruby-kramdown] ruby-kramdown: FTBFS: ERROR: Test "ruby2.7" 
failed: ArgumentError: invalid byte sequence in UTF-8
Set Bug forwarded-to-address to 
'https://github.com/gettalong/kramdown/issues/744'.
> thanks
Stopping processing here.

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

Bug#1002115: bug in texlive?

[Cédric Boutillier]

I suspect this is caused by a change in texlive.
Here is the diff for the list of packages used in tests in ci.debian.net
between the last green and the (almost) first red:

--- kramdown-ok 2022-01-26 14:35:12.162946913 +0100
+++ kramdown-nok2022-01-26 14:35:21.802998157 +0100
@@ -1,7 +1,7 @@
 fontconfig-config  2.13.1-4.2
 fonts-dejavu-core  2.37-2
 fonts-lmodern  2.004.5-6.1
-gem2deb-test-runner1.7
+gem2deb-test-runner1.8
 kramdown   2.3.1-3
 libapache-pom-java 18-1
 libbrotli1 1.0.9-2+b3
@@ -11,7 +11,7 @@
 libfontbox-java1:1.8.16-2
 libfontconfig1 2.13.1-4.2
 libfreetype6   2.11.0+dfsg-1
-libglib2.0-0   2.70.1-1
+libglib2.0-0   2.70.2-1
 libgraphite2-3 1.3.14-1
 libharfbuzz0b  2.7.4-1
 libice62:1.0.10-1
@@ -70,13 +70,13 @@
 rubygems-integration   1.18
 t1utils1.41-4
 tex-common 6.17
-texlive-base   2021.20210921-1
+texlive-base   2021.20211127-1
 texlive-binaries   2021.20210626.59705-1
-texlive-fonts-recommended  2021.20210921-1
-texlive-latex-base 2021.20210921-1
-texlive-latex-extra2021.20210921-1
-texlive-latex-recommended  2021.20210921-1
-texlive-pictures   2021.20210921-1
+texlive-fonts-recommended  2021.20211127-1
+texlive-latex-base 2021.20211127-1
+texlive-latex-extra2021.20211127-1
+texlive-latex-recommended  2021.20211127-1
+texlive-pictures   2021.20211127-1
 tidy   2:5.6.0-11
 x11-common 1:7.7+23
 xdg-utils  1.1.3-4.1

 The test failure comes from the filtering of the latex output. Removing
 the 'scan and join' part works around the issue.

diff --git a/test/test_files.rb b/test/test_files.rb
index 7e2ccad..bc5523a 100644
--- a/test/test_files.rb
+++ b/test/test_files.rb
@@ -150,7 +150,7 @@ class TestFiles < Minitest::Test
 io.close_write
 io.read
   end
-  assert($?.exitstatus == 0, result.scan(/^!(.*\n.*)/).join("\n"))
+  assert($?.exitstatus == 0, result)
 end
   end
 end


signature.asc
Description: PGP signature

Bug#1002418: [Pkg-privacy-maintainers] Bug#1002418: marked as done (mat2: FTBFS: AssertionError: 'TransparentColor' not found in {})

[Georg Faerber]

Hi Utkarsh,
 
Thanks for your upload.
 
Could you please push the changes you did to the git repo?
 
Thanks,
cheers,
Georg

Bug#997756: marked as done (python-meshplex: FTBFS: sed: no input files)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 12:49:02 +
with message-id 
and subject line Bug#997756: fixed in python-meshplex 0.17.0-1
has caused the Debian Bug report #997756,
regarding python-meshplex: FTBFS: sed: no input files
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.)


-- 
997756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-meshplex
Version: 0.15.13-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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_sphinxdoc -i
> grep "https://cdnjs.cloudflare.com/ajax/libs/mathjax/.*/latest.js; 
> debian/python-meshplex-doc/usr/share/doc/python-meshplex-doc/* -r 
> --files-with-matches | xargs sed 
> "s|src=\"https://cdnjs.cloudflare.com/ajax/libs/mathjax/.*/latest.js|src=\"file://usr/share/javascript/mathjax/unpacked/latest.js|g"
>  -i
> sed: no input files
> make[1]: *** [debian/rules:24: override_dh_sphinxdoc-indep] Error 123


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

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated python-meshplex package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jan 2022 13:18:57 +0100
Source: python-meshplex
Architecture: source
Version: 0.17.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 997756 998577
Changes:
 python-meshplex (0.17.0-1) unstable; urgency=medium
 .
   * New upstream release.
 - deprecates debian patch test_no_exdown.patch
 - test dir updated to "tests"
 - Build-Depends: python3-npx, python3-numpy (>= 1.20.0~)
 - bumps upper Build-Depends: python3-meshio (<< 6).
   Closes: #998577.
   * update debian/README.source
 - upstream tags no longer prefixed with v
   * don't patch mathjax references if there aren't any.
 Remove forkme*.png privacy handling in docs.
 Closes: #997756.
   * Standards-Version: 4.6.0
   * use default python build for docs
   * don't link meshes for dh_auto_test (test/meshes already copied)
   * drop debian patch test_io_dmsh_not_meshzoo.patch
 - Build-Depends: python3-meshzoo. Also debian/test Depends.
 - drop Build-Depends: python3-dmsh. Also for debian/test.
   * add debian patch test_relax_tolerance.patch to relax tolerances in
 test_mesh_tri.py
   * clean autogenerated src/meshplex.egg-info
   * build docs after dh_auto_build-indep instead of override_
   * debian patch docs_local_mathjax.patch uses local libjs-mathjax
 for docs. Closes: #997756.
   * Build-Depends: pybuild-plugin-pyproject, flit
 - drop debian patch setup_python.patch
Checksums-Sha1:
 c27087c3db2059b8ac09b0b3ac87cdc80b04d3fd 2503 python-meshplex_0.17.0-1.dsc
 db800f5edb7771b24c0cfe0314cdfbdb329beee5 124473 
python-meshplex_0.17.0.orig.tar.gz
 477db46ac96d3b75276f306bce5ecda1c3d03118 4712 
python-meshplex_0.17.0-1.debian.tar.xz
Checksums-Sha256:
 2c8155021ff2daffd5e81219d4b7f5e2928f7c49ba9216b3a04c77151de2d52b 2503 
python-meshplex_0.17.0-1.dsc
 6bce3a3c22ce00f379ba3c221e651e7b68f6c0733928663ae454e3d77110547b 124473 

Bug#998577: marked as done (python-dmsh: FTBFS: build-dependency not installable: python3-meshio (< 5))

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 12:49:02 +
with message-id 
and subject line Bug#998577: fixed in python-meshplex 0.17.0-1
has caused the Debian Bug report #998577,
regarding python-dmsh: FTBFS: build-dependency not installable: python3-meshio 
(< 5)
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.)


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

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-python, python3-all, 
> python3-importlib-metadata, python3-matplotlib, python3-meshplex (>= 0.15.8), 
> python3-meshplex (<< 0.16), python3-numpy, python3-scipy, python3-setuptools, 
> python3-wheel, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-python, python3-all, 
> python3-importlib-metadata, python3-matplotlib, python3-meshplex (>= 0.15.8), 
> python3-meshplex (<< 0.16), python3-numpy, python3-scipy, python3-setuptools, 
> python3-wheel, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [450 B]
> Get:5 copy:/<>/apt_archive ./ Packages [534 B]
> Fetched 1941 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  python3-meshplex : Depends: python3-meshio (< 5) but it is not going to be 
> installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2021/11/04/python-dmsh_0.2.11-3_unstable.log

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

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

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

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated python-meshplex package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 26 Jan 2022 13:18:57 +0100
Source: python-meshplex
Architecture: source
Version: 0.17.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 997756 998577
Changes:
 python-meshplex (0.17.0-1) unstable; urgency=medium
 .
   * New upstream release.
 - deprecates 

Bug#1004272: marked as done (binutils: missing RELRO header)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 13:42:02 +0100
with message-id <0231dfec-3de7-f5b1-0ce0-3238e0b55...@debian.org>
and subject line Re: binutils: missing RELRO header
has caused the Debian Bug report #1004272,
regarding binutils: missing RELRO header
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.)


-- 
1004272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: binutils
Version: 2.37.50.20220121-1
Severity: serious

Control: affects -1 vnstat

Building vnstat (version 2.8 or 2.9) with version 2.37.50.20220121-1
results in 2 of 3 binaries not having a RELRO section, despite
`-Wl,-z,relro` being passed and blhc being happy.
Building with version 2.37.50.20220106-2 successfully adds a RELRO
section to all binaries as expected.
Sample failed salsa pipelines:
  rebuild of current sid version 2.8:
https://salsa.debian.org/debian/vnstat/-/pipelines/340548
  prepared 2.9 release:
https://salsa.debian.org/debian/vnstat/-/pipelines/340535
--- End Message ---
--- Begin Message ---
Version: 2.37.90.20220123-2

Fixed.--- End Message ---

Bug#1004272: binutils: missing RELRO header

[Matthias Klose]

Version: 2.37.90.20220123-2

Fixed.

Bug#965917: marked as done (yorick-z: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 11:51:09 +
with message-id 
and subject line Bug#965917: fixed in yorick-z 1.2.0+cvs20080115-5.1
has caused the Debian Bug report #965917,
regarding yorick-z: 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.)


-- 
965917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yorick-z
Version: 1.2.0+cvs20080115-5
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package yorick-z 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: yorick-z
Source-Version: 1.2.0+cvs20080115-5.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
yorick-z, 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.
Adrian Bunk  (supplier of updated yorick-z package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 12:59:55 +0200
Source: yorick-z
Architecture: source
Version: 1.2.0+cvs20080115-5.1
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers 

Changed-By: Adrian Bunk 
Closes: 965917
Changes:
 yorick-z (1.2.0+cvs20080115-5.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965917)
Checksums-Sha1:
 48367fc3e8cbf87257a35dd5095735f7f103f2c7 2130 
yorick-z_1.2.0+cvs20080115-5.1.dsc
 ecbe14f1f519459565ab6e733e8cd1af2204abb3 5960 
yorick-z_1.2.0+cvs20080115-5.1.debian.tar.xz
Checksums-Sha256:
 600854d44347877132c168495b2b38f7a90859d46632ee87fea6d7a29e3d0007 2130 
yorick-z_1.2.0+cvs20080115-5.1.dsc
 ff0435d5b56a4717522dd3a16feeed6943ab746b04b5712584719e30be8dc39e 5960 
yorick-z_1.2.0+cvs20080115-5.1.debian.tar.xz
Files:
 b25aad36493d27ba07455c4c78d0f2fd 2130 science extra 
yorick-z_1.2.0+cvs20080115-5.1.dsc
 b9b12670ce2fc11c536cf76c01582950 5960 science extra 
yorick-z_1.2.0+cvs20080115-5.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHn778ACgkQiNJCh6LY
mLFE5xAAoI3JO11R+2JsX+lNQ0J7x9yScDwj/5U0Fd5m6XnCAgonGG7+faaaLH+T
NmJCpHUfnWuUog6G6ad37kxhqZYQNVqMuD4mj/HjIWezEapehJ4Yt0URv1O+PB9M
rFzIzJIttIDAX5hEHFasN2zPTY64x07LDY7y8dakBHM/Um0L1NiNm7e+ou6XcjF3
yfQ+jN5SKPLxQIesH593rSguRWTI4gOUUolILH0upKjEQ91RNiTd1JSC5B4i7qhY
JTLGG2ZcglTPG+cJKblS2ZuZiEDZFB8aD18B3xqDMd9f/GK8IRjCJL3SZVfwC05f
ijfE8yWzA7xIp2nyw6qOf3lY2JrAAIyM8wTRjnHCExbWCp5EUur8JFzAnKS9npnt
KFgOFHdrATuqduVQCoIpYnoozACjFuhhMhUsK5nJMSBmEC7/u52r2dzxRRAKbFKu
MeZ4ew3z9CM/ktKbpD3/buqP+781NDJOFsVe1KP/9egg0cPLruPhMADD1AZSuTz5
MPIxJgAconfcsHapR7uh3W+6JEBpvrSRhcWs6FFM7y8AMT5vAOFcYcKddIrYGkon
o0DXlBt1fKt8wL5nY98/NRGKFfrQXoSui+p+cPUhBgVNS8yuXM4o9XksWB1pf62Q
C1KVPVHZ6zhlTnKo0mHQbfC33nlr5QLwJKCRWZZK1VbhqCjHH1E=
=TNY5
-END PGP SIGNATURE End Message ---

Bug#1004311: marked as done (pahole segfaults during kernel build)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 11:49:04 +
with message-id 
and subject line Bug#1004311: fixed in dwarves 1.22-4
has caused the Debian Bug report #1004311,
regarding pahole segfaults during kernel build
to be marked as done.

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

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


-- 
1004311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pahole
Version: 1.22-2
Severity: normal

Dear Maintainer,

Building an upstream kernel reliably segfaults in pahole, starting with
1.22-2. I just downgraded to 1.22-1 (from snapshot.do) and that does *not*
have this problem. I don't immediately see a changelog entry that could
explain this problem.

Greetings,

Andres

Backtrace from core file:

#0  type__compare_members (b=0x55a9260432b0, a=0x55a925f8ce70) at ./pahole.c:216
216 ./pahole.c: No such file or directory.
(gdb) bt
#0  type__compare_members (b=0x55a9260432b0, a=0x55a925f8ce70) at ./pahole.c:216
#1  type__compare (cu_a=, cu_b=0x55a925f4b880, b=0x55a9260432b0, 
a=0x55a925f8ce70) at ./pahole.c:310
#2  __structures__add (class=class@entry=0x55a9260432b0, 
cu=cu@entry=0x55a925f4b880, id=id@entry=26, 
existing_entry=existing_entry@entry=0x7ffce1053090)
at ./pahole.c:326
#3  0x55a9258f4491 in structures__add (existing_entry=0x7ffce1053090, 
id=26, cu=0x55a925f4b880, class=0x55a9260432b0) at ./pahole.c:357
#4  print_classes (cu=) at ./pahole.c:524
#5  pahole_stealer (cu=0x55a925f4b880, conf_load=) at 
./pahole.c:2859
#6  0x55a925901613 in cu__finalize (conf=0x55a925914100 , 
cu=0x55a925f4b880) at ./dwarf_loader.c:2477
#7  cus__finalize (cus=0x55a925f47610, cu=cu@entry=0x55a925f4b880, 
conf=0x55a925914100 ) at ./dwarf_loader.c:2484
#8  0x55a925903ba7 in dwarf_cus__create_and_process_cu 
(dcus=dcus@entry=0x7ffce10532a0, cu_die=0x7ffce1053250, pointer_size=)
at ./dwarf_loader.c:2675
#9  0x55a92590462c in __dwarf_cus__process_cus (dcus=) at 
./dwarf_loader.c:2764
#10 dwarf_cus__process_cus (dcus=0x7ffce10532a0) at ./dwarf_loader.c:2778
#11 cus__load_module (cus=cus@entry=0x55a925f47610, conf=, 
mod=mod@entry=0x55a925f49f00, dw=, elf=elf@entry=0x55a925f476f0,
filename=0x7ffce1054a6e ".tmp_vmlinux.btf") at ./dwarf_loader.c:2913
#12 0x55a9259048b1 in cus__process_dwflmod (dwflmod=0x55a925f49f00, 
userdata=, name=, base=,
arg=0x7ffce1053400) at ./dwarf_loader.c:2957
#13 0x7fdc64fe3471 in dwfl_getmodules () from 
/lib/x86_64-linux-gnu/libdw.so.1
#14 0x55a925900880 in cus__process_file (filename=0x7ffce1054a6e 
".tmp_vmlinux.btf", fd=5, conf=0x55a925914100 , cus=0x55a925f47610)
at ./dwarf_loader.c:3023
#15 dwarf__load_file (cus=0x55a925f47610, conf=0x55a925914100 , 
filename=0x7ffce1054a6e ".tmp_vmlinux.btf") at ./dwarf_loader.c:3058
#16 0x55a9258f905f in cus__load_file (cus=cus@entry=0x55a925f47610, 
conf=conf@entry=0x55a925914100 ,
filename=0x7ffce1054a6e ".tmp_vmlinux.btf") at ./dwarves.c:2043
#17 0x55a9258f92d8 in cus__load_files (cus=cus@entry=0x55a925f47610, 
conf=conf@entry=0x55a925914100 , 
filenames=filenames@entry=0x7ffce10537c0)
at ./dwarves.c:2396
#18 0x55a9258f0ba9 in main (argc=4, argv=0x7ffce10537a8) at ./pahole.c:3224
(gdb)

Using a pahole built from source I do not see this.


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

Kernel: Linux 5.16.0-rc5-andres-00225-g5e9874628080 (SMP w/40 CPU threads; 
PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pahole depends on:
ii  libbpf0  1:0.5.0-1
ii  libc62.33-3
ii  libdw1   0.186-1
ii  libelf1  0.186-1
ii  zlib1g   1:1.2.11.dfsg-2

pahole recommends no packages.

pahole suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dwarves
Source-Version: 1.22-4
Done: Domenico Andreoli 

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

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

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

Debian distribution maintenance software
pp.
Domenico Andreoli  

Bug#965916: marked as done (yorick-cubeview: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 11:51:05 +
with message-id 
and subject line Bug#965916: fixed in yorick-cubeview 2.2-2.2
has caused the Debian Bug report #965916,
regarding yorick-cubeview: 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.)


-- 
965916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yorick-cubeview
Version: 2.2-2
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package yorick-cubeview 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: yorick-cubeview
Source-Version: 2.2-2.2
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
yorick-cubeview, 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.
Adrian Bunk  (supplier of updated yorick-cubeview package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 13:03:55 +0200
Source: yorick-cubeview
Architecture: source
Version: 2.2-2.2
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers 

Changed-By: Adrian Bunk 
Closes: 965916
Changes:
 yorick-cubeview (2.2-2.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965916)
Checksums-Sha1:
 8e2332b9c5bf10e49a32e9c198a7ca37a4160a17 2071 yorick-cubeview_2.2-2.2.dsc
 698c55ec18bc5eebb191e7aab718c61b34e21495 4344 
yorick-cubeview_2.2-2.2.debian.tar.xz
Checksums-Sha256:
 557f8e280952aafcd63adebd7d6b4825b2c568a95160e47bd9c413cc3f8d9e66 2071 
yorick-cubeview_2.2-2.2.dsc
 a15a45cdb534cf026ea9eec244c2dbeb03b3348e8af584d24dea96adaeb5b358 4344 
yorick-cubeview_2.2-2.2.debian.tar.xz
Files:
 77078dbd49deab6edf9578b1259f8173 2071 science extra yorick-cubeview_2.2-2.2.dsc
 4fdab05b581d550baf2336b06fd56aa5 4344 science extra 
yorick-cubeview_2.2-2.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHn8GsACgkQiNJCh6LY
mLFY0A//XgzL8wAuJgZkP01psa+BATxiEg7f/vZJHeHAa3el/aKbMRfySYv1RrWo
3bVEGw+IS9SbKPeA8OUltLOa9bS1FxTwAIHnazkMfPCEFuQuKO7wEj2CbBEj5VaV
/daxP2RrAFtKXMNgTj/JzN1pZmG5i+aqFruZBJc2m/+jZ7KmXrsMdLKOTD+lxEt1
IjpaGFmzG0WG3k2z4zyOpyRzLuQzYNqtO72YViyhcBD2juOxR6s4anZq/CIkR+A2
DikyJJEKxW/W4vsZjFA5XTTOStcW17s1n7Ieiz1CoreBm1KnqzH+OPs8BY1+ZenT
utVDx2UErQnhpAiKBWlqbPBe2/vbZoSKD7ehDhav3vmZir3qw0njd51a4VELfr/e
J/JUJ4AVheJ8HOLIsUZASXFRh3rRqGoo26urG+++GHG07wfBAqJa1qzc/YZ7QvEr
qEae0Ddc/7LWWqyY9xJ1isFsQFscTbQrsbt9iF5lUBjR4yHFSm6I1hmojm1/V07F
UvjRKu6ogn7A9nsxkdD4BAL41avGQ//cabImsW5PD//gMDf8kk1d5eZ0GMznh3zq
CixlVVm/16FG3blV6yjLfiJpekRg0JxIdtucloRI1OjXN/gMcv97gMknXcsS4J1A
yXW3GLKFkTpimM11OvOvXDahcnx/qKYJ1OtAHYf5Q0ItvEVoiLM=
=TCnW
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 11:18:43 +
with message-id 
and subject line Bug#965900: fixed in xfsdump 3.1.9+0+nmu2
has caused the Debian Bug report #965900,
regarding xfsdump: 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.)


-- 
965900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfsdump
Version: 3.1.9+0
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package xfsdump 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: xfsdump
Source-Version: 3.1.9+0+nmu2
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
xfsdump, 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.
Adrian Bunk  (supplier of updated xfsdump package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jan 2022 12:22:32 +0200
Source: xfsdump
Architecture: source
Version: 3.1.9+0+nmu2
Distribution: unstable
Urgency: low
Maintainer: Nathan Scott 
Changed-By: Adrian Bunk 
Closes: 965900
Changes:
 xfsdump (3.1.9+0+nmu2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965900)
Checksums-Sha1:
 ed378a34b862a10f48c13c074ef66e49fdbec846 1626 xfsdump_3.1.9+0+nmu2.dsc
 ae0bf767be42a59d88f68ac9e78fa65b0a2ffa7d 885795 xfsdump_3.1.9+0+nmu2.tar.gz
Checksums-Sha256:
 6624dfd11d0829d9b720f58f155d6180e263e154a8117f78784ea6629bff70cf 1626 
xfsdump_3.1.9+0+nmu2.dsc
 4d56cfb751e0cd350ebfbe93c28e1eacc8b93d61cadb4764b50fd7907e41ceb9 885795 
xfsdump_3.1.9+0+nmu2.tar.gz
Files:
 1734c2c5ee5e9f4474147414534bdf9e 1626 admin optional xfsdump_3.1.9+0+nmu2.dsc
 de3b9e835b6516b2e17364546f7e9393 885795 admin optional 
xfsdump_3.1.9+0+nmu2.tar.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHn6vUACgkQiNJCh6LY
mLFedhAApzV40yX0Fdy82CejWqrCeHRsJZ6aFsTFcJbe9+FPqr0SymcdMSeIGYT+
o22LUyI2TmFVt/Xjn0n/cpTdtFnER1rouy2pegRb8svie2QaB2I2n+Cu1Bk2GPEZ
batHgGepLydrPbFW+5RH0rmxmJ0MjrhYP711oPvIhUbp3f1tXF/THBgBIbHUzfGF
kAH4D/isHqwmKpLbJqiF5bZGaybaQnINTJEREu9knSvvUYIPTK/GibjrIV4OXc6q
dpZol/ZWFo+l4QPGAuQy6S08IjZB69A/6gXzvReNoPS2W5PM+DCy/M588cqwJjP6
cXUNhtaxreaxCzcU0K1yrIWZkHSRyNzyO0BlltfCvJqA6nq5Ld3loqAUabE0vNyU
R5Phc0xIY81cu9M+5S57Oahz01KA9dx9xUAWPuTAUtjbPl+FU8kL3q6U/cT6LV38
Q4dKUoc91qGLBuf5DaMorBcbZa57KidlHR+PeYIczLGpou3Hg3s0U98836hYP4vY
UH4f5yhMAzTbKZW/TvS3fBNvd4DZkIt8rrkqF15VbxXQ3mL2LsH06IpVolc0sRK5
ya9tD/DU+QCoCy8cngKyunWf5J6E8oYXVnvKXIgUC8O+4Xl0akewe9pq8CROZ8OW
Ip++vUmrGjJ+2zft5Iaci82zKX+To561BtQGpYXLKoDAzwLerQY=
=+kHQ
-END PGP SIGNATURE End Message ---

Bug#1003933: w3c-sgml-lib: catalogs for MathML 2.0 are incomplete

[Mathieu Malaterre]

Control: forwarded -1 https://github.com/w3c/markup-validator/issues/66
Control: tags -1 upstream

As discussed in upstream bug tracker there is something wrong with the
namespace "TR"...

Processed: w3c-sgml-lib: catalogs for MathML 2.0 are incomplete

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/w3c/markup-validator/issues/66
Bug #1003933 [w3c-sgml-lib] w3c-sgml-lib: catalogs for MathML 2.0 are incomplete
Set Bug forwarded-to-address to 
'https://github.com/w3c/markup-validator/issues/66'.
> tags -1 upstream
Bug #1003933 [w3c-sgml-lib] w3c-sgml-lib: catalogs for MathML 2.0 are incomplete
Added tag(s) upstream.

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

Bug#1004380: libfilament-tools: /usr/bin/resgen is already provided by mono-devel

[Andreas Beckmann]

Package: libfilament-tools
Version: 1.9.25+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

/usr/bin/resgen (and the corresponding manpage) are already shipped by
mono-devel. Please rename that executable and its manpage.


Andreas


mono-devel=6.8.0.105+dfsg-3.2_libfilament-tools=1.9.25+dfsg-2.log.gz
Description: application/gzip

Bug#1004311: [PATCH] add_cmake_libbpf_enabled_option.patch: Only check the macro HAVE_BPF

[Salvatore Bonaccorso]

Hi,

On Wed, Jan 26, 2022 at 01:47:42AM +0100, Ben Hutchings wrote:
> Control: tag -1 patch
> 
> The patch add_cmake_libbpf_enabled_option.patch is indeed the problem,
> because it doesn't consistently use the same macro name.  The fix is
> below.
> 
> If you're not able to upload with this today, can I please NMU to
> unblock linux?
> 
> Ben.
> 
> --- a/debian/patches/add_cmake_libbpf_enabled_option.patch
> +++ b/debian/patches/add_cmake_libbpf_enabled_option.patch
> @@ -5,6 +5,8 @@ Non-linux systems also can make good use of these tools. This 
> patch
>  adds option LIBBPF_ENABLED (default: on) so to opt-out BPF when needed.
>  
>  Signed-off-by: Domenico Andreoli 
> +[bwh: Only check the macro HAVE_BPF, not HAVE_BTF]
> +Signed-off-by: Ben Hutchings 
>  ---
>   CMakeLists.txt |   61 
> +
>   dwarves.c  |2 ++
> @@ -193,7 +195,7 @@ Index: b/pahole.c
>   cu__fprintf_ptr_table_stats_csv(cu, stderr);
>   }
>   
> -+#ifdef HAVE_BTF
> ++#ifdef HAVE_BPF
>   if (btf_encode) {
>   static pthread_mutex_t btf_lock = PTHREAD_MUTEX_INITIALIZER;
>   
> @@ -241,7 +243,7 @@ Index: b/pahole.c
>   type_instance__delete(header);
>   header = NULL;
>   
> -+#ifdef HAVE_BTF
> ++#ifdef HAVE_BPF
>   if (btf_encode) {
>   err = btf_encoder__encode(btf_encoder);
>   if (err) {
> @@ -257,7 +259,7 @@ Index: b/pahole.c
>   #ifdef DEBUG_CHECK_LEAKS
>   cus__delete(cus);
>   structures__delete();
> -+#ifdef HAVE_BTF
> ++#ifdef HAVE_BPF
>   btf__free(conf_load.base_btf);
>   conf_load.base_btf = NULL;
>   #endif

Tested against our current master (5.16.2-1~exp1) and fixes the issue.

Tested-by: Salvatore Bonaccorso   

Regards,
Salvatore

Bug#999265: marked as done (libjavascript-rpc-perl: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 09:18:55 +
with message-id 
and subject line Bug#999265: fixed in libjavascript-rpc-perl 0.10-2
has caused the Debian Bug report #999265,
regarding libjavascript-rpc-perl: 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.)


-- 
999265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjavascript-rpc-perl
Version: 0.10-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: libjavascript-rpc-perl
Source-Version: 0.10-2
Done: Christoph Biedl 

We believe that the bug you reported is fixed in the latest version of
libjavascript-rpc-perl, 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.
Christoph Biedl  (supplier of updated 
libjavascript-rpc-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Jan 2022 18:51:57 +0100
Source: libjavascript-rpc-perl
Architecture: source
Version: 0.10-2
Distribution: unstable
Urgency: medium
Maintainer: Christoph Biedl 
Changed-By: Christoph Biedl 
Closes: 999265 1001975
Changes:
 libjavascript-rpc-perl (0.10-2) unstable; urgency=medium
 .
   * Salvaging upload
   * Take maintainership. Closes: #1001975
   * Packaging cleanup. Closes: #999265
Checksums-Sha1:
 7fa720f4b6375ce67bed3796927a83d243dc06bd 1931 libjavascript-rpc-perl_0.10-2.dsc
 2f8bbd33fac4ca71a2833045905673872ec4b398 2216 
libjavascript-rpc-perl_0.10-2.debian.tar.xz
 417a127bc74dba60e0472b6ca1fc622e9c0a328a 6093 
libjavascript-rpc-perl_0.10-2_powerpc.buildinfo
Checksums-Sha256:
 cb0eba19a81b516e8bafb50794496e0d0fd90271b689ec9c310fee0a9a8e0116 1931 
libjavascript-rpc-perl_0.10-2.dsc
 8cd2a45d706ede01bfdfa7f63699255f7f2ea894caf8c647c45a759d9fc5c76c 2216 
libjavascript-rpc-perl_0.10-2.debian.tar.xz
 62ac54c972f5babcbffb53af04a1d557dfc2de8820d7110d55d4c40edd2b0dfc 6093 
libjavascript-rpc-perl_0.10-2_powerpc.buildinfo
Files:
 bdd20ab3be59f9b97d083d415d4ce1fe 1931 perl optional 
libjavascript-rpc-perl_0.10-2.dsc
 342486178fff4cf0b0faadce6d87e3ad 2216 perl optional 
libjavascript-rpc-perl_0.10-2.debian.tar.xz
 a3b376b080a5412fbb04b4483ee124c9 6093 perl optional 
libjavascript-rpc-perl_0.10-2_powerpc.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAmHekl8ACgkQxCxY61kU
kv0hHw//bIj/j61jmkzCtZgezFsEqGXvLislUA5/TJKvDUZm/XJNYKbibYwgXCSl
yoipungrgCR1pQFRKzhEOf9yi2JE4QDwip6UV3MluFSFtz2aQT29lxGjxVlTsBHs
q0hFF+9O2VL9ybsH8/cbIVTli9N5+ek6FL1wkGTljniY1qYvngIsB9Y7rqIzGxjL
xqv5IxmKHcGFgZfEqByKe7BSMam1hiSIOV9XBRuoi1Id1zzDKyzue+s9cQOpoxkE
0+GcwEm/MeI9GCozFKvCLFSJRHpvIiDwPPd+VAflfuRmkAb7EN2vrv6RaAA4LSCg
xtgjxX31IN7aa8fA9lwAGS4fpt/6DJ1DzpjASrYLgxv5Z5+MCVL/5RP73AtWhtym
nWU7Oz4RDbUrrzBoALvP0PwyPyKh9atPo+4e0PTzc7KKPpuJ/6+uwHljZNFDSKEF
Bm8xfpKR4Vho+YuMwq8RF3ihVu7drWVsxFz06wxZNuCFTbJSx5RUHxBDL6xV9WXo
wsLJAUhQn+nHc0P78HEUwyfwF52l4TWZyPQet0JmsNxQSJ3NIy8cNGB/ixuxu/0B
NLh/GFKfUs7CnABLomtVIBhmLaiChudUcNHURs8mx/+r9r3ZWcBqWWNLF8aTua2d
BRuoLyzUWk12jeYaCIg5WYYdUnUFt+woTkyOKF0dzlN9m/LMuus=
=qkq7
-END PGP SIGNATURE End Message ---

Bug#999223: marked as done (libcgi-ssi-parser-perl: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 09:18:44 +
with message-id 
and subject line Bug#999223: fixed in libcgi-ssi-parser-perl 0.01-2
has caused the Debian Bug report #999223,
regarding libcgi-ssi-parser-perl: 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.)


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: libcgi-ssi-parser-perl
Source-Version: 0.01-2
Done: Christoph Biedl 

We believe that the bug you reported is fixed in the latest version of
libcgi-ssi-parser-perl, 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.
Christoph Biedl  (supplier of updated 
libcgi-ssi-parser-perl 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, 08 Jan 2022 12:48:43 +0100
Source: libcgi-ssi-parser-perl
Architecture: source
Version: 0.01-2
Distribution: unstable
Urgency: medium
Maintainer: Christoph Biedl 
Changed-By: Christoph Biedl 
Closes: 466397 999223 1001973
Changes:
 libcgi-ssi-parser-perl (0.01-2) unstable; urgency=medium
 .
   * Salvaging upload
   * Take maintainership. Closes: #1001973
   * Packaging cleanup. Closes: #466397, #999223
Checksums-Sha1:
 ffe78427c0edf8387d08bbdf769950c3a6b89e7e 1878 libcgi-ssi-parser-perl_0.01-2.dsc
 2c6e575796d9aec727078765cc06fcb1bb2dc40c 1836 
libcgi-ssi-parser-perl_0.01-2.debian.tar.xz
 16fb34aa926462b873adb9057db94fbdbc672a7a 5730 
libcgi-ssi-parser-perl_0.01-2_powerpc.buildinfo
Checksums-Sha256:
 c7935ae712dfa78fe984bf839e8cb55e606f74b6e08f82530fd93896eb25faeb 1878 
libcgi-ssi-parser-perl_0.01-2.dsc
 3a4cf5d41939a928c2a78859ba4ec8c5e114734b4ef381bd294bb079743f4de2 1836 
libcgi-ssi-parser-perl_0.01-2.debian.tar.xz
 ea793af71f095b8b5d19444d92155296eca514ee36e31d44c4cfc81a457b71ae 5730 
libcgi-ssi-parser-perl_0.01-2_powerpc.buildinfo
Files:
 08248483febfc76850b3b33e78a0cc8a 1878 web optional 
libcgi-ssi-parser-perl_0.01-2.dsc
 2136e42e3d29b1f9274c6500e8972dcf 1836 web optional 
libcgi-ssi-parser-perl_0.01-2.debian.tar.xz
 a3b15753af7fe0dfdf63e9317149b31f 5730 web optional 
libcgi-ssi-parser-perl_0.01-2_powerpc.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAmHeklUACgkQxCxY61kU
kv2XRA/+Lfb7Xs7kOGFyfzfFMbNHvxX4LxEvSIyT7QN4ntVTbpsD3SMfrf067nxh
YXdtKkeSyNMDAab6XLsKV/BEj6kuL31ylO/65Ng+1zi35xO6Ycw7/sV6TgdDQ/pP
uLOXkTuUHQq15U+IbWbSS6YLQA4i8BYuKJHO2iy/Y19KvzQjPEAiBU/HJ8nsFyUM
ZLGNfXW8bqoWduPzUMXEncMtSQWYY5cHPk8yAw0O/rGBz3tro0fQj3AtXqKrqpfw
EsyF+hUyfjAbwtsuqTh8OxGR452S/FU/NIIivd81OoyeBYzpYX91SB19tb6yLtYN
KZ7gsIPbxrfuy17HhCUof/OKfKnanHhqZ7NzCPJwoJZlwVxkdYjq5MynmwNSnXri
XRa5oMurQJCa/Tpo6yTAe3vCYjXdXYqYH0A76vl1njxOQCC3LfOyLnOsZj/RdwAH
w71HrX3wgMU62LEW9zSTPmpM1dQow/J7kvo5Q+vKCuEvfETPRKVJVL6RIalMkQ3W
TnCr0YVT1K4vjdneQB3FxkwNFsIwe5LZ/uJgwZqksvBiJC6CU6qJEd5RDLeANJ0s
sFdrCh2a5FXxSKZfSrXS6UzF863/1rAp5gPKXAjv7a2W4xtB2vziRPNFyw2NEx5Y
BxFvB2Ao8q9E1h40PzQ0neI8TNVh3r+Wfu0ZI3PI5Z8ldtsXk3Y=
=Fm4m
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 09:19:00 +
with message-id 
and subject line Bug#998954: fixed in libppd 2:0.10-8
has caused the Debian Bug report #998954,
regarding libppd: 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.)


-- 
998954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libppd
Version: 2:0.10-7.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: libppd
Source-Version: 2:0.10-8
Done: Christoph Biedl 

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

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated libppd 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Jan 2022 20:37:21 +0100
Source: libppd
Architecture: source
Version: 2:0.10-8
Distribution: unstable
Urgency: medium
Maintainer: Christoph Biedl 
Changed-By: Christoph Biedl 
Closes: 912689 998954 1001976
Changes:
 libppd (2:0.10-8) unstable; urgency=medium
 .
   * Take maintainership. Closes: #1001976
   * Packaging cleanup. Closes: #998954, #912689
Checksums-Sha1:
 bece6e89eb7bde6b07c89795abfe768b5344b557 1865 libppd_0.10-8.dsc
 c676404267390f0bb7833059f8ac05903527234d 9196 libppd_0.10-8.debian.tar.xz
 4394ef2f09c4e6b9cc5c6613c71c7116a4ab43d9 7790 libppd_0.10-8_powerpc.buildinfo
Checksums-Sha256:
 599931aea32c6c312d7fa785194a2aa96b4b64a58d2a4cc83fb73f6458064908 1865 
libppd_0.10-8.dsc
 6e86d4eb0dcd386811c59ea02d8ae02ce3c3eae638686d9161f7a972f56cc39e 9196 
libppd_0.10-8.debian.tar.xz
 6dd005299b0c259780da4fd7b011ea3c0638fda9419d6afa784f1528510c8c0e 7790 
libppd_0.10-8_powerpc.buildinfo
Files:
 7483f9cae9b4e597ee5c02024c0f9260 1865 libs optional libppd_0.10-8.dsc
 dcbe218ecf02a476453e3630214681f3 9196 libs optional libppd_0.10-8.debian.tar.xz
 4bc0e8a778b2aad69aed7b0f1ea1b4d2 7790 libs optional 
libppd_0.10-8_powerpc.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAmHekmUACgkQxCxY61kU
kv0Xwg/+POSuxWAhwh22jsRat/z47qLED6DrbSF9bhU8mKbxVmoO0g6uJLV/FK+r
2lzS0X2prSFONJXmOEAfxDvvV5NGtmsh9icyOVyRKhNQpEUQwUxZJpHzLdjqGvxt
Z4vjqYiPrEh7sDd1FceY8Y9AJMwAwQZm5nJs4+aZYJN1ukwF1664wAblve7akQb9
qagO36N3V34PYEU4NjXnpR/6DFWgM8U4I0F/nSTPQv/v4oijc9vrecmWIiBQ3vWW
lm9p82NdteJPnxLBLqBho4Hyrn8FJXuOU0oYjT+CZN8YQpX0OxmD1m2eVeIKt4Sp
hUVSyPUg68p91Dt/0rgTvXHacqSzjLt4pEMYCqCfsy5O/3xNbJMG1qa2JZ8bTGT9
16VNuNtrXcCpm6Rx57xjn7e/WKnI52P6ogxffI3htH25KBKd0AL5j9RxffnV1RJK
iJwr6Agfo0wdnCFZh9qpSAZaR8vcouP0q5t+6dh+AkY1FVf17buNgcziOXTAz4RL
XpFP/IMHmg6XVYEdpZlIuaRpKpCR7e3zds8+uSuOhxDrCYGAnVWkR39xyICgkNKH
q07Wv0h8URqis1mk5IK/B/GPSz+K4AymPNW965EC/t3y0qqZFwxgfNMbbwojdoB8
pL5kVfivZYczfWR0OfdVQQWC8wmQf786ck/0XHq9CtPYQF48658=
=Beh7
-END PGP SIGNATURE End Message ---

Bug#998918: marked as done (libdebian-package-html-perl: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jan 2022 09:18:50 +
with message-id 
and subject line Bug#998918: fixed in libdebian-package-html-perl 0.1-3
has caused the Debian Bug report #998918,
regarding libdebian-package-html-perl: 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.)


-- 
998918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdebian-package-html-perl
Version: 0.1-2.1
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: libdebian-package-html-perl
Source-Version: 0.1-3
Done: Christoph Biedl 

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

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated 
libdebian-package-html-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Jan 2022 23:20:53 +0100
Source: libdebian-package-html-perl
Architecture: source
Version: 0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Christoph Biedl 
Changed-By: Christoph Biedl 
Closes: 610178 998918 1001974
Changes:
 libdebian-package-html-perl (0.1-3) unstable; urgency=medium
 .
   * Salvaging upload
   * Take maintainership. Closes: #1001974
   * Packaging cleanup. Closes: #998918
   * Remove external example reference from documentation.
 Closes: #610178
Checksums-Sha1:
 067be792604a3dd0978b00d6ca6cec224ca9fd47 1945 
libdebian-package-html-perl_0.1-3.dsc
 3ae52a88e02e57e98169d636d2d9f8820e10111c 2512 
libdebian-package-html-perl_0.1-3.debian.tar.xz
 12944e3b24a6d5785d13b4332fdd592b6d1296eb 5928 
libdebian-package-html-perl_0.1-3_powerpc.buildinfo
Checksums-Sha256:
 5f97cb0f9f023033e25f8c441237cd72319ee1b3e79f478c82fdb982408ac8d4 1945 
libdebian-package-html-perl_0.1-3.dsc
 938d32a8a0c44f72868c9d2b78cdbf4ba5979c4424c0fbb9ee71fd2865eb8209 2512 
libdebian-package-html-perl_0.1-3.debian.tar.xz
 c99f46416c4e0127cd96e23fd15f549e686e848ba54746053de5e9679270a0d7 5928 
libdebian-package-html-perl_0.1-3_powerpc.buildinfo
Files:
 58a3f1ad312f103d27c5161c22710fdf 1945 perl optional 
libdebian-package-html-perl_0.1-3.dsc
 1895f49a1c9f737a69b6ea49de2d2ea4 2512 perl optional 
libdebian-package-html-perl_0.1-3.debian.tar.xz
 db2b879004b0aff932bf920b900f15ad 5928 perl optional 
libdebian-package-html-perl_0.1-3_powerpc.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAmHekloACgkQxCxY61kU
kv0ttxAAjZFhPN9Cx4VbNbyO1iY1MZR/uqsfZKxaS+rs/SzGUb/y69kQEtPObjVd
SxHw53AiEAz1iwTuBi/agci8dcDWKLyIy1KmJs/vxaSbwBjWuYjo5ZIJH1htH0S9
QzDIn1JCgsKCDKqLZIYEMKYvGP9/5k3J33SJkM2u6o98SIsVsVaR89j10S00NEuc
aHEnPUBbN+JuD0NnsR1jRAkwOqmuHWyMcxYbvmSRv5ibX7tw6tN6zvT1CLy6AhC5
ETdnOQPrclDVPLPIZWZtURE5FEISvgfWtBGdQJszqXK8bZvh8s/lx9u7oL9o/qQ7
DPNabDNTJMEWCM99cpIUufXADhx9Yuu0LzwRowlOCVg998jgCcqfqTrBJywLJLxg
z6ZhdG0C3sd2q9bmqfb7xh0nFSBWtOwiM8Z237P+pe+u/s/Lqqg+BaFeRScuccur
ly2Wd8363dgf0ppTmZNmUVu46raWBYdh2BmmALZFErBj/30Pt79lhpqAmr0I7xwZ
qrzLOka1hymtXHl4xipsuX5gtscxmE1kCHorm0/fI4KY2Pl/O7CMlad/Fegctg3N
mGydC2ITfcMHldWdgf0FEHe1WuGMThEiYcJJ9AbBlsMnJnPuPlgOG8Bm4/R0+Wy7
6fxPAaC7VOlFk4rXQ4oePinMCFqXGhL56mQnkfsNNhNB/6bKEl8=
=coZC
-END PGP SIGNATURE End Message ---

Bug#1004376: libphp-adodb: CVE-2021-3850 - Authentication Bypass in PostgreSQL connections

[Neil Williams]

Source: libphp-adodb
Version: 5.20.19-1
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: codeh...@debian.org, Debian Security Team 


Hi,

The following vulnerability was published for libphp-adodb.

CVE-2021-3850[0]:
| Authentication Bypass by Primary Weakness in GitHub repository
| adodb/adodb prior to 5.20.21.


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-2021-3850
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3850

Please adjust the affected versions in the BTS as needed.

The upstream issue describes the problem as:
"a critical security issue - anyone relying on ADOdb < 5.20.21 and <
5.21.4 to connect to a PostgreSQL database is strongly advised to
upgrade as soon as possible."

The affected line shows up in the current package in unstable:
https://sources.debian.org/src/libphp-adodb/5.20.19-1/drivers/adodb-postgres64.inc.php/?hl=50#L54
(Same version is in bullseye).
https://sources.debian.org/src/libphp-adodb/5.20.14-1/drivers/adodb-postgres64.inc.php/#L54
(buster)

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

Kernel: Linux 5.15.0-3-amd64 (SMP w/16 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Processed: forwarded binutils issue

[Debian Bug Tracking System]

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

> forwarded 1004272 https://sourceware.org/bugzilla/show_bug.cgi?id=28819
Bug #1004272 [src:binutils] binutils: missing RELRO header
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=28819'.
> thanks
Stopping processing here.

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

Processed: zeitgeist: FTBFS: where-clause.vala:219.35-219.63: error: The name `pdata' does not exist in the context of `GLib.PtrArray*'

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 
> https://gitlab.freedesktop.org/zeitgeist/zeitgeist/-/commit/64ac3a6
Bug #997287 [src:zeitgeist] zeitgeist: FTBFS: where-clause.vala:219.35-219.63: 
error: The name `pdata' does not exist in the context of `GLib.PtrArray*'
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/zeitgeist/zeitgeist/-/commit/64ac3a6'.

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