Bug#991800: altos FTBFS with the bookworm gcc-arm-none-eabi

2021-08-01 Thread Adrian Bunk 
Source: altos
Version: 1.9.6-1
Severity: serious
Tags: ftbfs bookworm sid

altos FTBFS with the bookworm gcc-arm-none-eabi
that is already in unstable:

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

...
  CC  telegps-v0.3-1.9.7.elf
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_boot_chain.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: 
multiple definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_product.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: multiple 
definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_romconfig.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: 
multiple definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_cmd.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: multiple 
definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_config.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: multiple 
definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_task.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: multiple 
definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_stdio.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: multiple 
definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_panic.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: multiple 
definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_timer_lpc.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: 
multiple definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_mutex.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: multiple 
definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_freq.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: multiple 
definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_spi_lpc.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: multiple 
definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_usb_lpc.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: multiple 
definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_exti_lpc.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: 
multiple definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_serial_lpc.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: 
multiple definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_gps_ublox.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: 
multiple definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_gps_show.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: 
multiple definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: first 
defined here
/usr/lib/gcc/arm-none-eabi/10.2.1/../../../arm-none-eabi/bin/ld: 
ao_cc115l.o:/build/1st/altos-1.9.7/src/telegps-v0.3/../lpc/lpc.h:871: multiple 
definition of `lpc_usb'; 
ao_interrupt.o:/build/1st/altos-1.9.7/src/t

Bug#991648: marked as done (python-a38: FTBFS: AssertionError: "routines:CMS_verify:content verify error" does not match "b'Verification failure\n140224232826176:error:2E099064:CMS routines:cms_signer

2021-08-01 Thread Debian Bug Tracking System 
Your message dated Mon, 02 Aug 2021 06:03:25 +
with message-id 
and subject line Bug#991648: fixed in python-a38 0.1.3-2
has caused the Debian Bug report #991648,
regarding python-a38: FTBFS: AssertionError: "routines:CMS_verify:content 
verify error" does not match "b'Verification 
failure\n140224232826176:error:2E099064:CMS 
routines:cms_signerinfo_verify_cert:certificate verify 
error:../crypto/cms/cms_smime.c:252:Verify error:certificate has expired\n'"
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.)


-- 
991648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-a38
Version: 0.1.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210728 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> nose2-3
> sEF..
> ==
> ERROR: test_verify (test_p7m.TestAnagrafica)
> --
> Traceback (most recent call last):
>   File "/<>/tests/test_p7m.py", line 63, in test_verify
> p7m.verify_signature(capath)
>   File "/<>/a38/crypto.py", line 102, in verify_signature
> raise InvalidSignatureError(res.stderr)
> a38.crypto.InvalidSignatureError: b'Verification 
> failure\n140292464510272:error:2E099064:CMS 
> routines:cms_signerinfo_verify_cert:certificate verify 
> error:../crypto/cms/cms_smime.c:252:Verify error:certificate has expired\n'
> 
> ==
> FAIL: test_verify_corrupted_payload (test_p7m.TestAnagrafica)
> --
> a38.crypto.InvalidSignatureError: b'Verification 
> failure\n140224232826176:error:2E099064:CMS 
> routines:cms_signerinfo_verify_cert:certificate verify 
> error:../crypto/cms/cms_smime.c:252:Verify error:certificate has expired\n'
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>   File "/<>/tests/test_p7m.py", line 81, in 
> test_verify_corrupted_payload
> p7m.verify_signature(capath)
> AssertionError: "routines:CMS_verify:content verify error" does not match 
> "b'Verification failure\n140224232826176:error:2E099064:CMS 
> routines:cms_signerinfo_verify_cert:certificate verify 
> error:../crypto/cms/cms_smime.c:252:Verify error:certificate has expired\n'"
> 
> --
> Ran 145 tests in 0.155s
> 
> FAILED (failures=1, errors=1, skipped=1)
> make[1]: *** [debian/rules:15: override_dh_auto_test] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/07/28/python-a38_0.1.3-1_testing.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.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-a38
Source-Version: 0.1.3-2
Done: Elena Grandi 

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

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

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

Debian distribution maintenance software
pp.
Elena Grandi  (supplier of updated python-a38 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
Da

Bug#991788: xfce4-settings: black screen after suspend when laptop lid is closed and re-opened

2021-08-01 Thread truetechie 
Package: xfce4-settings
Version: 4.16.0-1
Severity: critical

On Debian and, by extension, Ubuntu, when suspending a laptop via closing the 
lid on XFCE, the screen stays black after resuming from suspend. The only way 
to "fix" the system is to blindly type "xrandr --auto" into a terminal or 
switch to a TTY and restart X.

This issue can be easily fixed by disabling Upower support when the package is 
compiled. However, despite being set as default in 4.16, Debian seems to have 
it re-enabled. Removing "--enable-upower-glib" from the configure flags in the 
package instantly solves this issue.

Bug#991739: marked as done (GPSD time will jump back 1024 weeks at after week=2180 (23-October-2021))

2021-08-01 Thread Debian Bug Tracking System 
Your message dated Sun, 01 Aug 2021 20:18:21 +
with message-id 
and subject line Bug#991739: fixed in gpsd 3.22-4
has caused the Debian Bug report #991739,
regarding GPSD time will jump back 1024 weeks at after week=2180 
(23-October-2021)
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.)


-- 
991739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpsd
Version: 3.20-12~bpo10+1

Effects 3.20 to 3.22. Corrected in 3.23. Debian buster-backports has 3.20 and 
bullseye has 3.22.

Email description from the gpsd-users mailing list.

From:Gary E. Miller
Subject: GPSD time will jump back 1024 weeks at after week=2180 
(23-October-2021)
Date:     Mon, 26 Jul 2021 14:32:10 -0700

Yo All!

Fair warning.  Issue 144: https://gitlab.com/gpsd/gpsd/-/issues/144

"GPSD time will jump back 1024 weeks at after week=2180 (23-October-2021)"

The offending commit was after 3.19, so only 3.20, 3.21 and 3.22 are affected:

    commit cb7367496f6dd5f90c6b067c031b327921a857b2
    Author: Gary E. Miller 
    Date:   Tue Oct 8 17:04:54 2019 -0700

The commit 7f30d88d fixes the problem for those that want to try to back port 
the fix. You'll just be without all the other bug fixes..

This is a real good reason to get 3.23 out very soon.  Please test!
--- End Message ---
--- Begin Message ---
Source: gpsd
Source-Version: 3.22-4
Done: Bernd Zeimetz 

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

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

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

Debian distribution maintenance software
pp.
Bernd Zeimetz  (supplier of updated gpsd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 01 Aug 2021 21:58:54 +0200
Source: gpsd
Architecture: source
Version: 3.22-4
Distribution: unstable
Urgency: high
Maintainer: Bernd Zeimetz 
Changed-By: Bernd Zeimetz 
Closes: 991739
Changes:
 gpsd (3.22-4) unstable; urgency=high
 .
   * [2df40c76] Fix: GPSD time will jump back 1024 weeks at after week=2180
 (Closes: #991739)
   * [c6af361a] Fix patch
Checksums-Sha1:
 8c8fa139675420470f19ba10fd701b4229678e29 2841 gpsd_3.22-4.dsc
 a207980c7ccf0268fb710e25a798fe5e00e1a0fe 54296 gpsd_3.22-4.debian.tar.xz
 9ab7b837478065f000fb2c5dfb62d76d48b301cd 16001 gpsd_3.22-4_source.buildinfo
Checksums-Sha256:
 02d4b503a3d84ecd56ea2eecdfff5dfc324e925cf140e6bd2af51bdfc66b096e 2841 
gpsd_3.22-4.dsc
 3d56a83e37f9321a6e80cb910780192fb9ecefa078392fc01250b9be64d96094 54296 
gpsd_3.22-4.debian.tar.xz
 3b9291c39b2eaf9278d80119769e4ad256c2dbcef10d455b0c43698dae212b99 16001 
gpsd_3.22-4_source.buildinfo
Files:
 56f98680de717208cab685ecd8bec0c2 2841 misc optional gpsd_3.22-4.dsc
 d47eb9dda1b349054b6cba40505fc05c 54296 misc optional gpsd_3.22-4.debian.tar.xz
 55fc0e121bb0b69fd065ae914e70ef65 16001 misc optional 
gpsd_3.22-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAmEG/aUACgkQ6zYXGm/5
Q1+0GA/+JSpKSsGLGriD0kv0U0AhEXr6q1EgltHQnt4vObjKabG3feLUUhFiLnnH
uog2CEKCalC2TDyHBXU5e4YBetKGW5i36XuN35T7Bfw80rteCOS02Llgy/G35252
L+V8EYrFei1Y70XT8MarJehDrklE/UZziwvQJHOv2cfb1PY1TqdncxjE9u6NTMsS
dQBuxSeaNMWIp5H9WeyHAzW1wcDgCmbUDzltEY0KfzlD4Y/ZA/HvL0d1OdYSeZaU
eKYPEOKWuaNT+NgxqUV10nP+loNOUEEN1AvJzSsxfT+e8Dr/iVOpMDE+YGGGfUav
kkA5Ie1q9DgNVGyjbZVxsSsYWQOHWu+p9JWdGNpMFY0i1Wwr0efUrt5IxxhJIt+Y
orX7kIzHw0tpLHcuejJAx272dZwebXqN2YxcryQo/Zdu4fxXwST2ySew2cmG3IPu
F8WwpbpOM1YcQAqUW4+z00/nYecOBZxY0Y/2Pk65/qdbZFX6MGPihKT6xlageE1N
RmvVa40LlzYabDUsVNpvIRAha5FmNr1oKCdGL5yxdDWfu9TrgLSiPfMqXP40ODzj
rpHplCMjmUzPIGLZ8JOhwJ4a0U17pKZXAYXvso5svB8leGZjbsnpBQY05XbIhUWK
puGF25FFpyuNEqUSUH1VE/3Klut3DgN5wWunEtw/uJYtWAaGZK4=
=HvEU
-END PGP SIGNATURE End Message ---

Bug#987441: s390x installation bugs

2021-08-01 Thread Valentin Vidic 
On Sun, Aug 01, 2021 at 05:10:07PM +0200, Cyril Brulebois wrote:
> Valentin Vidic  (2021-08-01):
> > No problem, I was not able to reproduce this reliably or get a core
> > dump for this crash. It could just be an emulation problem with qemu
> > or some timing issue for the first installer step. If there is no
> > update on this problem I think we can even close it for now.
> 
> Speaking of the first step, did anyone mention #987368 before, now fixed
> in udpkg?

Thanks, that does sound similar to what I was getting there. I will try
to see if it still happens with the latest installer. And since it
crashes on start I had no way to access the logs or dmesg of the
machine. Perhaps there is some installer option to help debug this kind
of thing?

-- 
Valentin

Processed: tagging 988707

2021-08-01 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 988707 + bookworm sid
Bug #988707 {Done: A. Maitland Bottoms } 
[src:qthid-fcd-controller] qthid-fcd-controller: triggers lintian autoreject 
tag 'bogus-mail-host'
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Processed: found 989792 in 1.8.0-1

2021-08-01 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> found 989792 1.8.0-1
Bug #989792 [src:dqlite] dqlite assumes a kernel configured with 4kB page size
Marked as found in versions dqlite/1.8.0-1.
> thanks
Stopping processing here.

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

Processed: unarchiving 707803, found 707803 in 5.0.2-2.2+squeeze1, unarchiving 698631 ...

2021-08-01 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> unarchive 707803
Bug #707803 {Done: Ivo De Decker } [bacula] bacula: 
copyright file missing after upgrade (policy 12.5)
Unarchived Bug 707803
> found 707803 5.0.2-2.2+squeeze1
Bug #707803 {Done: Ivo De Decker } [bacula] bacula: 
copyright file missing after upgrade (policy 12.5)
Marked as found in versions bacula/5.0.2-2.2+squeeze1.
> unarchive 698631
Bug #698631 {Done: gregor herrmann } [typo3] typo3: 
copyright file missing after upgrade (policy 12.5)
Warning: Unknown package 'typo3'
Unarchived Bug 698631
Warning: Unknown package 'typo3'
> found 698631 4.3.9+dfsg1-1+squeeze9
Bug #698631 {Done: gregor herrmann } [typo3] typo3: 
copyright file missing after upgrade (policy 12.5)
Warning: Unknown package 'typo3'
Marked as found in versions typo3-src/4.3.9+dfsg1-1+squeeze9.
Warning: Unknown package 'typo3'
> thanks
Stopping processing here.

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

Processed: bullseye-ignore

2021-08-01 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> # We're getting very close to the bullseye release. Although we'd
> # (still) love to have these bugs fixed, let's focus on what absolutely
> # needs fixing.
> # I'm considering adding a release-notes section about some/most of
> # these bugs
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was elb...@debian.org).
> tag 984714 bullseye-ignore
Bug #984714 [gparted] gparted should suggest exfatprogs and backport the commit 
that rejects exfat-utils
Bug #990393 [gparted] gparted should suggest exfatprogs and backport the commit 
that rejects exfat-utils
Added tag(s) bullseye-ignore.
Added tag(s) bullseye-ignore.
> usertag 984714 bullseye-release-notes
There were no usertags set.
Usertags are now: bullseye-release-notes.
> tag 991082 bullseye-ignore
Bug #991082 [gir1.2-gtd-1.0] gir1.2-gtd-1.0 has empty Depends
Added tag(s) bullseye-ignore.
> usertag 991082 bullseye-release-notes
There were no usertags set.
Usertags are now: bullseye-release-notes.
> tag 991449 bullseye-ignore
Bug #991449 [fail2ban] fix for CVE-2021-32749 breaks systems with mail from 
bsd-mailx
Added tag(s) bullseye-ignore.
> usertag 991449 bullseye-release-notes
There were no usertags set.
Usertags are now: bullseye-release-notes.
> tag 984760 bullseye-ignore
Bug #984760 [grub-efi-amd64] grub-efi-amd64: upgrade works, boot fails (error: 
symbol `grub_is_lockdown` not found)
Added tag(s) bullseye-ignore.
> usertag 984760 bullseye-release-notes
There were no usertags set.
Usertags are now: bullseye-release-notes.
> retitle 991588 tpm2-abrmd should not use Requires=systemd-udev-settle.service 
> in its unit
Bug #991588 [tpm2-abrmd] systemd: Buster to Bullseye: boot stalls at network 
loading on normal boot
Changed Bug title to 'tpm2-abrmd should not use 
Requires=systemd-udev-settle.service in its unit' from 'systemd: Buster to 
Bullseye: boot stalls at network loading on normal boot'.
> tag 991588 bullseye-ignore
Bug #991588 [tpm2-abrmd] tpm2-abrmd should not use 
Requires=systemd-udev-settle.service in its unit
Added tag(s) bullseye-ignore.
> usertag 991588 bullseye-release-notes
There were no usertags set.
Usertags are now: bullseye-release-notes.
> thanks
Stopping processing here.

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

Processed: Re: Processed (with 1 error): document fail2ban brokenness in release-notes

2021-08-01 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> retitle 991781 fail2ban is broken with mail from bsd-mailx
Bug #991781 [release-notes] fix for CVE-2021-32749 breaks systems with mail 
from bsd-mailx
Changed Bug title to 'fail2ban is broken with mail from bsd-mailx' from 'fix 
for CVE-2021-32749 breaks systems with mail from bsd-mailx'.
> thanks
Stopping processing here.

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

Processed (with 1 error): document fail2ban brokenness in release-notes

2021-08-01 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> clone 991449 -1
Bug #991449 [fail2ban] fix for CVE-2021-32749 breaks systems with mail from 
bsd-mailx
Bug 991449 cloned as bug 991781
> reassign -1 release-notes
Bug #991781 [fail2ban] fix for CVE-2021-32749 breaks systems with mail from 
bsd-mailx
Bug reassigned from package 'fail2ban' to 'release-notes'.
No longer marked as found in versions fail2ban/0.11.2-2.
Ignoring request to alter fixed versions of bug #991781 to the same values 
previously set
> retitle fail2ban is broken with mail from bsd-mailx
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Processed: tagging 991739

2021-08-01 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 991739 - bullseye-ignore
Bug #991739 [gpsd] GPSD time will jump back 1024 weeks at after week=2180 
(23-October-2021)
Removed tag(s) bullseye-ignore.
> thanks
Stopping processing here.

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

Bug#991778: dlint: Dlint fails to find version number of dig

2021-08-01 Thread Patrik Schindler 
Package: dlint
Version: 1.4.0-8
Severity: grave
Tags: patch
Justification: renders package unusable

On my Debian Buster system, dig fails to work with

;; This program requires DiG version 2.1 or newer, which I cannot find.

Checking on this, I saw that the "ver" call in line 109 doesn't output a
version number anymore. So I changed that to dig -v.

Next, sed was unable to extract a meaningful version number from what dig -v
provided, so I changed the sed statement in the same line accordingly.

The following replacement for line 109 works for me.

ver=`dig -v 2>&1 | grep DiG | head -1 | sed -e 's/^DiG \([0-9.]\+\).*$/\1/'`

My changes might introduce non-backwards compatible changes, though.

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

Kernel: Linux 4.19.0-17-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages dlint depends on:
ii  dnsutils  1:9.11.5.P4+dfsg-5.1+deb10u5
ii  perl  5.28.1-6+deb10u1

dlint recommends no packages.

dlint suggests no packages.

-- no debconf information

Bug#987441: s390x installation bugs

2021-08-01 Thread Cyril Brulebois 
Valentin Vidic  (2021-08-01):
> No problem, I was not able to reproduce this reliably or get a core
> dump for this crash. It could just be an emulation problem with qemu
> or some timing issue for the first installer step. If there is no
> update on this problem I think we can even close it for now.

Speaking of the first step, did anyone mention #987368 before, now fixed
in udpkg?

(The BTS seems to be sad right now, and I'd like to avoid diving into
bug mail.)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#987441: marked as done (debian-installer: D-I must get ready for Bullseye)

2021-08-01 Thread Debian Bug Tracking System 
Your message dated Sun, 1 Aug 2021 16:35:48 +0200
with message-id <20210801143548.d7km2yzgm5qcf...@mraw.org>
and subject line Re: Bug#987441: s390x installation bugs
has caused the Debian Bug report #987441,
regarding debian-installer: D-I must get ready for Bullseye
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.)


-- 
987441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debian-installer
Version: 20210415
Severity: serious
Justification: meh.

Let's keep track of things that need to be looked at before D-I is
considered ready for the initial Bullseye release (11.0).

Carried over from D-I Bullseye RC 1 errata:
 - amdgpu firmware
 - broken rescue mode

Bugs reported against various packages or installation reports will
block this bug report until they are either fixed or ruled out as not
being actual blockers for the release.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Hi Valentin,

Valentin Vidic  (2021-05-02):
> Probably not critical, but maybe these installation bugs on s390x
> could be fixed for the release?
> 
> rootskel: steal-ctty no longer works on at least sparc64
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926539

I'm sorry I haven't been able to follow up to your updated MR that was
adjusted according to my wishes (making the new code s390x-specific)…
Thanks anyway, your efforts don't go unnoticed!

In the meanwhile the discrepancy was addressed upstream, and I've been
in contact with Salvatore to get the change in time for 11.0 (in the
linux 5.10.46-3 upload):
  
https://tracker.debian.org/news/1245083/accepted-linux-51046-3-source-into-unstable/

Let's try and get the rootskel change in early in the next release cycle
(possibly not limited to this architecture since we wouldn't be so close
to 11.0…)?

> debian-installer: qemu-system-s390x installation fails due to segfault in 
> main-menu
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987788

There doesn't seem to be any patches around for this one, so it looks
like this will need to get fixed during the next release cycle, and
we'll see whether we can backport the fix via bullseye-proposed-updates.

With #989863, that was the only remaining blocker I documented via this
meta bug report, so I'll close it and consider our work for Bullseye
done (provided the to-be-published D-I Bullseye RC 3 doesn't explode).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature
--- End Message ---

Processed: bullseye-ignore

2021-08-01 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> # We're getting very close to the bullseye release. Although we'd
> # (still) love to have these bugs fixed, let's focus on what absolutely
> # needs fixing.
> # I'm considering adding a release-notes section about some/most of
> # these bugs
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was elb...@debian.org).
> tag 987602 bullseye-ignore
Bug #987602 [src:ca-certificates] 
ca-certificates-java,default-jre-headless,openjdk-11-jre-headless: get rid of 
the circular dependency
Added tag(s) bullseye-ignore.
> tag 929685 bullseye-ignore
Bug #929685 [ca-certificates-java,default-jre-headless,openjdk-11-jre-headless] 
ca-certificates-java,default-jre-headless,openjdk-11-jre-headless: get rid of 
the circular dependency
Added tag(s) bullseye-ignore.
> tag 991110 bullseye-ignore
Bug #991110 [src:python3.9] python3.9: Please exclude test_concurrent_futures 
also on armhf and alpha
Added tag(s) bullseye-ignore.
> tag 932501 bullseye-ignore
Bug #932501 [src:squid-deb-proxy] squid-deb-proxy: daemon does not start due to 
the conf file not being allowed by apparmor
Added tag(s) bullseye-ignore.
> tag 932501 - patch
Bug #932501 [src:squid-deb-proxy] squid-deb-proxy: daemon does not start due to 
the conf file not being allowed by apparmor
Removed tag(s) patch.
> usertag 932501 bullseye-release-notes
There were no usertags set.
Usertags are now: bullseye-release-notes.
> tag 989545 bullseye-ignore
Bug #989545 [src:llvm-toolchain-11] libgl1-mesa-dri: si_texture.c:1727 
si_texture_transfer_map - failed to create temporary texture to hold untiled 
copy
Added tag(s) bullseye-ignore.
> usertag 989545 bullseye-release-notes
There were no usertags set.
Usertags are now: bullseye-release-notes.
> tag 990318 bullseye-ignore
Bug #990318 [python-pkg-resources] python-pkg-resources: please add Breaks 
against the unversioned python packages
Added tag(s) bullseye-ignore.
> usertag 990318 bullseye-release-notes
There were no usertags set.
Usertags are now: bullseye-release-notes.
> tag 922981 bullseye-ignore
Bug #922981 [ca-certificates-java] ca-certificates-java: 
/etc/ca-certificates/update.d/jks-keystore doesn't update 
/etc/ssl/certs/java/cacerts
Added tag(s) bullseye-ignore.
> usertag 922981 bullseye-release-notes
There were no usertags set.
Usertags are now: bullseye-release-notes.
> tag 988477 bullseye-ignore
Bug #988477 [src:xen] xen-hypervisor-4.14-amd64: xen dmesg shows (XEN) AMD-Vi: 
IO_PAGE_FAULT on sata pci device
Added tag(s) bullseye-ignore.
> usertag 988477 bullseye-release-notes
There were no usertags set.
Usertags are now: bullseye-release-notes.
> tag 990417 bullseye-ignore
Bug #990417 [src:qemu] openjdk-11-jre-headless: running java in qemu s390 gives 
a SIGILL at C  [linux-vdso64.so.1+0x6f8]  __kernel_getcpu+0x8
Added tag(s) bullseye-ignore.
> tag 990026 bullseye-ignore
Bug #990026 [cron] cron: Reduced charset in MAILTO causes breakage
Added tag(s) bullseye-ignore.
> usertag 990026 bullseye-release-notes
There were no usertags set.
Usertags are now: bullseye-release-notes.
> tag 981054 bullseye-ignore
Bug #981054 [openipmi] openipmi: Missing dependency on kmod
Added tag(s) bullseye-ignore.
> usertag 981054 bullseye-release-notes
There were no usertags set.
Usertags are now: bullseye-release-notes.
> tag 991478 bullseye-ignore
Bug #991478 [shim-signed] [shim-signed] RFE: do not brick users' systems in the 
stable distribution
Added tag(s) bullseye-ignore.
> tag 991610 bullseye-ignore
Bug #991610 [postfix] postfix: TLS_LICENSE is not included in 
/usr/share/doc/postfix/copyright
Added tag(s) bullseye-ignore.
> tag 991739 bullseye-ignore
Bug #991739 [gpsd] GPSD time will jump back 1024 weeks at after week=2180 
(23-October-2021)
Added tag(s) bullseye-ignore.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
922981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922981
929685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929685
932501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932501
981054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981054
987602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987602
988477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988477
989545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989545
990026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990026
990318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990318
990417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990417
991110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991110
991478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991478
991610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991610
991739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forcibly merging 991344 991770

2021-08-01 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> forcemerge 991344 991770
Bug #991344 [src:umatrix] umatrix: CVE-2021-36773: Denial of Service
Bug #991770 [src:umatrix] umatrix: new upstream release (1.4.4) fixes security 
issue
Severity set to 'grave' from 'wishlist'
Added tag(s) upstream.
Merged 991344 991770
> thanks
Stopping processing here.

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

Bug#991006: marked as done (openjdk-11-jre-dcevm: autopkgtest broken by openjdk-11 in unstable)

2021-08-01 Thread Debian Bug Tracking System 
Your message dated Sun, 01 Aug 2021 13:48:52 +
with message-id 
and subject line Bug#991006: fixed in openjdk-11-jre-dcevm 11.0.12+7-1
has caused the Debian Bug report #991006,
regarding openjdk-11-jre-dcevm: autopkgtest broken by openjdk-11 in unstable
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.)


-- 
991006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-11-jre-dcevm
Version: 1.0.11+9-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/o/openjdk-11-jre-dcevm/13559634/log.gz

...
autopkgtest [12:12:28]: test java-version: java -dcevm -version
autopkgtest [12:12:28]: test java-version: [---
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (classLoader.cpp:1217), pid=3385, tid=3390
#  guarantee(JImageResourcePath != NULL) failed: function JIMAGE_ResourcePath 
not found
#
# JRE version:  (11.0.12+6) (build )
# Java VM: Dynamic Code Evolution 64-Bit Server VM 
(11.0.11-internal+0-adhoc.buildd.openjdk-11-jre-dcevm-11.0.119, mixed mode, 
sharing, tiered, unknown gc, linux-amd64)
# No core dump will be written. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /tmp/autopkgtest-lxc.xdpuhkvl/downtmp/build.zk5/src/hs_err_pid3385.log
#
#
bash: line 1:  3385 Aborted bash -ec 'java -dcevm -version' 2> 
>(tee -a /tmp/autopkgtest-lxc.xdpuhkvl/downtmp/java-version-stderr >&2) > >(tee 
-a /tmp/autopkgtest-lxc.xdpuhkvl/downtmp/java-version-stdout)
autopkgtest [12:12:30]: test java-version: ---]
autopkgtest [12:12:30]: test java-version:  - - - - - - - - - - results - - - - 
- - - - - -
java-version FAIL non-zero exit status 134
--- End Message ---
--- Begin Message ---
Source: openjdk-11-jre-dcevm
Source-Version: 11.0.12+7-1
Done: Emmanuel Bourg 

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated openjdk-11-jre-dcevm 
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: Sun, 01 Aug 2021 15:26:13 +0200
Source: openjdk-11-jre-dcevm
Architecture: source
Version: 11.0.12+7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 991006
Changes:
 openjdk-11-jre-dcevm (11.0.12+7-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #991006)
Checksums-Sha1:
 c47ce753bddad4b4ec597c3547a25d33f0e2546e 2361 
openjdk-11-jre-dcevm_11.0.12+7-1.dsc
 5b9328ba882460951d82d7597fa6de19a49b1de2 17356016 
openjdk-11-jre-dcevm_11.0.12+7.orig.tar.xz
 e6f6b376203c7fc26359f66319457bc1d4f2b38e 5984 
openjdk-11-jre-dcevm_11.0.12+7-1.debian.tar.xz
 79788c87a2537f0accc4a2068a55ae0916698808 9644 
openjdk-11-jre-dcevm_11.0.12+7-1_source.buildinfo
Checksums-Sha256:
 31bd88fa2622a16d9fe6b5ccc1fe5100398f327a6c5381cbba7c50d495f08bce 2361 
openjdk-11-jre-dcevm_11.0.12+7-1.dsc
 0ccfab8ceebb353edd6329a5503fd23f6281a19947f1ae2566dfc94b9635ae83 17356016 
openjdk-11-jre-dcevm_11.0.12+7.orig.tar.xz
 c019a9838a84c9d45a5281f34b7ebf19cecc37344f64ed30bd1dc975ab181c1a 5984 
openjdk-11-jre-dcevm_11.0.12+7-1.debian.tar.xz
 714239c8300a7668fa5721ba2f3b617d812879f58846abcd48289566cd87f040 9644 
openjdk-11-jre-dcevm_11.0.12+7-1_source.buildinfo
Files:
 9b9debe8ed18016fc9cc86b30fbd644a 2361 java optional 
openjdk-11-jre-dcevm_11.0.12+7-1.dsc
 1efaa6957dc812e2dd4c17b92aa75213 17356016 java optional 
openjdk-11-jre-dcevm_11.0.12+7.orig.tar.xz
 8617da508e3ad1ba63c20d6d2839e272 5984 java optional 
openjdk-11-jre-dcevm_11.0.12+7-1.debian.tar.xz
 6c2595e278f343d1db4ef5f41297396f 9644 java optional 
openjdk-11-jre-dcevm_11.0.12+7-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmEGoR8SHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsolIP/3ydZN7473BND/JAwX2PleIc1PP/hIY/

Bug#991006: marked as pending in openjdk-11-jre-dcevm

2021-08-01 Thread Emmanuel Bourg 
Control: tag -1 pending

Hello,

Bug #991006 in openjdk-11-jre-dcevm reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/java-team/openjdk-11-jre-dcevm/-/commit/9ccd8295c4e900c467dd8ec48bad0b678705c886


New upstream release (Closes: #991006)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/991006

Processed: Bug#991006 marked as pending in openjdk-11-jre-dcevm

2021-08-01 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #991006 [src:openjdk-11-jre-dcevm] openjdk-11-jre-dcevm: autopkgtest broken 
by openjdk-11 in unstable
Added tag(s) pending.

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

Bug#989296: marked as done (missing dependencies and wrong path in the .cmake file)

2021-08-01 Thread Debian Bug Tracking System 
Your message dated Sun, 01 Aug 2021 13:03:27 +
with message-id 
and subject line Bug#989296: fixed in gdcm 3.0.8-2
has caused the Debian Bug report #989296,
regarding missing dependencies and wrong path in the .cmake file
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.)


-- 
989296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvtkgdcm-dev
Severity: important
X-Debbugs-Cc: pi...@debian.org


Hello,

I try to build a package but it end up with this error message

-- The imported target "vtkgdcm" references the file
   "/usr/lib/x86_64-linux-gnu/libvtkgdcm.so.3.0.8"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake"
but not all the files it references.

-- The imported target "vtkgdcmsharpglue" references the file
   "/usr/lib/x86_64-linux-gnu/libvtkgdcmsharpglue.so"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake"
but not all the files it references.

-- The imported target "vtkgdcmJava" references the file
   "/usr/lib/x86_64-linux-gnu/jni/libvtkgdcmJava.so"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake"
but not all the files it references.

-- The imported target "vtkgdcmPython" references the file
   "/usr/lib/python/dist-packages/vtkgdcmPython.so"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake"
but not all the files it references.

-- The imported target "vtkgdcmPythonD" references the file
   "/usr/lib/x86_64-linux-gnu/libvtkgdcmPythonD.so.3.0.8"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake"
but not all the files it references.

-- The imported target "gdcmdump" references the file
   "/usr/bin/gdcmdump"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake"
but not all the files it references.

-- The imported target "gdcmdiff" references the file
   "/usr/bin/gdcmdiff"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake"
but not all the files it references.

-- The imported target "gdcmraw" references the file
   "/usr/bin/gdcmraw"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake"
but not all the files it references.

-- The imported target "gdcmscanner" references the file
   "/usr/bin/gdcmscanner"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake"
but not all the files it references.

-- The imported target "gdcmanon" references the file
   "/usr/bin/gdcmanon"
but this file does not exist.  Possible reasons include:
* The file was

Bug#989289: marked as done (libpmix-dev: Should depend on libevent-dev)

2021-08-01 Thread Debian Bug Tracking System 
Your message dated Sun, 01 Aug 2021 09:48:23 +
with message-id 
and subject line Bug#989289: fixed in pmix 4.0.0-4.1
has caused the Debian Bug report #989289,
regarding libpmix-dev: Should depend on libevent-dev
to be marked as done.

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

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


-- 
989289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpmix-dev
Version: 4.0.0-4
Severity: important

Dear Maintainer,

The package libpmix-dev comes with a pkg-config file to get compilation
flags. When I first installed the package, I got the following when
trying to get the flags:

% pkg-config --libs pmix
Package libevent was not found in the pkg-config search path.
Perhaps you should add the directory containing `libevent.pc'
to the PKG_CONFIG_PATH environment variable

The file libevent.pc is in libevent-dev package. I installed it,
and now:

% pkg-config --libs pmix
-lpmix -lhwloc -levent -lz

which is the expected result.

Thanks!


-- System Information:
Debian Release: 11.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'oldoldstable'), (500, 'unstable'), (500, 
'testing'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-5-amd64 (SMP w/16 CPU threads)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libpmix-dev depends on:
ii  libpmix2  4.0.0-4

libpmix-dev recommends no packages.

libpmix-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pmix
Source-Version: 4.0.0-4.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated pmix 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: Sun, 01 Aug 2021 11:20:07 +0200
Source: pmix
Architecture: source
Version: 4.0.0-4.1
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Sebastian Ramacher 
Closes: 989289
Changes:
 pmix (4.0.0-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Nobuhiro Iwamatsu ]
   * Add libevent-dev, libhwloc-dev and zlib1g-dev to libpmix-dev's Depends
 (Closes: #989289)
Checksums-Sha1:
 b8e7f968d2ead331742643fd2d5a74acf25ca738 2227 pmix_4.0.0-4.1.dsc
 709551eb0bc4ed08bbb52b313e310785ef76e9b4 9112 pmix_4.0.0-4.1.debian.tar.xz
Checksums-Sha256:
 e877c7ecabbf5e1ae624920e55054e8cfd332c325abdd0b99a876c4db5fb67d0 2227 
pmix_4.0.0-4.1.dsc
 f84ec4b50b3b60fb8347bfb168be325c69b46f916ba40b4fa6f2b67c98401219 9112 
pmix_4.0.0-4.1.debian.tar.xz
Files:
 58b3f832f8521d64ff1c5314acf888b0 2227 net optional pmix_4.0.0-4.1.dsc
 4d125b0c05f0796a40079ed8cf31ba15 9112 net optional pmix_4.0.0-4.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmEGaloACgkQafL8UW6n
GZN+7A//cfospeedmTjkoVmw7tQZxCrrryfw/kb5Jl/+WgSNnEIWp51cffHXd7Uu
GbOcXpWcNbJImFO73iBJcmHg+4qsEMv9Lg7hnOQaPSYqmrYj/23Uwg2nOFM7JzvN
kE63O2DkZ/EtKXPqaDHK1kF6V0t+xjmpK2M1V3xYZ6n9DRGXobEFHnotnQ9nSSQd
/oT1XDRKZ4pPXp+c+MCjrFGxkQolQZOHqrsu5W648ZXJB4ISZEOXGIGsztGZeGVU
8AIXCzoPHPKW1e1bnjZLRFLRz1Y/MYp5u0iIRxLWjdd4LpNOX4TsiibPrk2Cuu5O
UEUonvUxGZx534X/S9kShcVOZigIbIVVt2oscBgzM3jOtWEcVe1ERQRFtu1oYgpx
lqZ2W/uIp1wv5QNgbqGZzhV7fbQL7dr8Rtm3LWApoBHKNohQOv2zguHkoGm4Hqg8
LjraiJxoy3W2zuKvKEN868E8yv69Fw82O9it8TvOphcIMZmjJtN6aoi9ou2A89dy
ZgRp29fO+boihXJkpHm0DPNnlprQ7vIXn3Q/qiLT+vhfEaCe7rhbH0Krp+6Pmgtd
z/sEGva+A4omZolU955c5gTM42MsNERHegs0OjSngMOL1Z01CZAXxEHVzF3lpQF5
+dQaSwHRJfBow0lebdla59CCZtpdrmmcFNYWYB2h6EzpaJYlTK0=
=n2nV
-END PGP SIGNATURE End Message ---

Bug#989289: pmix: diff for NMU version 4.0.0-4.1

2021-08-01 Thread Sebastian Ramacher 
Dear maintainer,

I've prepared an NMU for pmix (versioned as 4.0.0-4.1). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru pmix-4.0.0/debian/changelog pmix-4.0.0/debian/changelog
--- pmix-4.0.0/debian/changelog	2021-01-20 18:30:05.0 +0100
+++ pmix-4.0.0/debian/changelog	2021-08-01 11:20:07.0 +0200
@@ -1,3 +1,13 @@
+pmix (4.0.0-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Nobuhiro Iwamatsu ]
+  * Add libevent-dev, libhwloc-dev and zlib1g-dev to libpmix-dev's Depends
+(Closes: #989289)
+
+ -- Sebastian Ramacher   Sun, 01 Aug 2021 11:20:07 +0200
+
 pmix (4.0.0-4) unstable; urgency=medium
 
   * Add Breaks: libopenmpi3 (<< 4.1.0-3) to libpmix2 to get necessary
diff -Nru pmix-4.0.0/debian/control pmix-4.0.0/debian/control
--- pmix-4.0.0/debian/control	2021-01-20 18:30:05.0 +0100
+++ pmix-4.0.0/debian/control	2021-08-01 11:19:00.0 +0200
@@ -26,7 +26,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: ${shlibs:Depends}, ${misc:Depends}, libpmix2 (= ${binary:Version}),
+Depends: ${shlibs:Depends}, ${misc:Depends}, libpmix2 (= ${binary:Version}), libevent-dev, libhwloc-dev, zlib1g-dev
 Description: Development files for the PMI Exascale library  
  This is the OpenMPI implementation of the Process Management Interface (PMI)
  Exascale API. PMIx aims to retain transparent compatibility with the existing


signature.asc
Description: PGP signature

Processed: tagging 990345

2021-08-01 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> # secrity issues that can be fixed later via a DSA
> tags 990345 + bullseye-ignore
Bug #990345 [src:zookeeper] zookeeper: various security issues
Added tag(s) bullseye-ignore.
> thanks
Stopping processing here.

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