Processed: your mail

[Debian Bug Tracking System]

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

> close 982361 2.4.0-3
Bug #982361 [openjpeg2] Excludes the wrong binary on Ubuntu i386
There is no source info for the package 'openjpeg2' at version '2.4.0-3' with 
architecture ''
Unable to make a source version for version '2.4.0-3'
Marked as fixed in versions 2.4.0-3.
Bug #982361 [openjpeg2] Excludes the wrong binary on Ubuntu i386
Marked Bug as done
>
End of message, stopping processing here.

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

Processed: RFS: snd/21.1-1 -- Sound file editor

[Debian Bug Tracking System]

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

> close 982411
Bug #982411 [sponsorship-requests] RFS: snd/21.1-1 -- Sound file editor
Marked Bug as done
> stop
Stopping processing here.

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

Bug#962844: marked as done (mdadm: Assembling RAID using IMSM in initrd fails due to lack of module efivarfs)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 05:03:32 +
with message-id 
and subject line Bug#962844: fixed in mdadm 4.1-11
has caused the Debian Bug report #962844,
regarding mdadm: Assembling RAID using IMSM in initrd fails due to lack of  
module efivarfs
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.)


-- 
962844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mdadm
Version: 4.1-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

I created a RAID 5 volume over 4 disks using the BIOS support for Intel
RST. Install proceeded correctly, however after a reboot in to the
installed system, the root device was not found. Investigation in the
init shell found that the mdamd device had not been assembled correctly

The following error was encountered when looking for imsm capabilies on
the controller. 

mdadm --detail-platform
mdadm: imsm capabilities not found for controller: 
/sys/devices/pci:00/:00:1f.2 (type SATA)

I found that this occurred when mdadm could not read from 
/sys/firmware/efi/efivars/ due to it not being mounted. The efivarfs module was 
not found in the initrd

To resolve this, I booted in to a rescue CD and added efivarfs and
efivars to /etc/initramfs.conf/modules and ran an update-initramfs

This allowed the system to boot correctly

I suggest that mdadm ensures that these modules are added to the initrd
when the RAID array is using IMSM.


-- Package-specific info:
--- mdadm.conf
ARRAY metadata=imsm UUID=56bed0cd:2b07c313:c4651474:3a6b990c
ARRAY /dev/md/Volume0 container=56bed0cd:2b07c313:c4651474:3a6b990c member=0 
UUID=d0f942e0:fb69f9d0:bca65978:774a6c88
MAILADDR root

--- /etc/default/mdadm
AUTOCHECK=true
START_DAEMON=true
DAEMON_OPTIONS="--syslog"
VERBOSE=false

--- /proc/mdstat:
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] 
[raid10] 
md126 : active raid5 sda[3] sdb[2] sdc[1] sdd[0]
  5567516672 blocks super external:/md127/0 level 5, 64k chunk, algorithm 0 
[4/4] []
  
md127 : inactive sdb[3](S) sdd[2](S) sdc[1](S) sda[0](S)
  20804 blocks super external:imsm
   
unused devices: 

--- /proc/partitions:
major minor  #blocks  name

   8   48 1953514584 sdd
   8   32 1953514584 sdc
   8   16 1953514584 sdb
   80 1953514584 sda
   9  126 5567516672 md126
 2590 525391 md126p1
 2591 5533714844 md126p2
 2592   33276403 md126p3

--- LVM physical volumes:
LVM does not seem to be used.
--- mount output
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=16317648k,nr_inodes=4079412,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=3266568k,mode=755)
/dev/md126p2 on / type ext4 (rw,relatime,errors=remount-ro,stripe=48)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev

Bug#982418: marked as done (RFS: csound/1:6.15.0~dfsg-1 -- powerful and versatile sound synthesis software)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 05:55:42 +0100
with message-id 
and subject line Re: RFS: csound/1:6.15.0~dfsg-1 -- powerful and versatile 
sound synthesis software
has caused the Debian Bug report #982418,
regarding RFS: csound/1:6.15.0~dfsg-1 -- powerful and versatile sound synthesis 
software
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.)


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

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "csound":

 * Package name    : csound
   Version : 1:6.15.0~dfsg-1
   Upstream Author : csound-...@listserv.heanet.ie
 * URL : https://csound.github.io/
 * License : LGPL-2+, other-hrtf-data, other-sdif, 
other-random, public-domain, LGPL-2.1+

 * Vcs : https://salsa.debian.org/multimedia-team/csound
   Section : sound

It builds those binary packages:

  libcsound64-doc - Csound API documentation
  liblua5.1-luacsnd - Lua bindings for the Csound API
  libcsnd6-6.0v5 - C++ bindings for the Csound API
  python3-csound - Python bindings for Csound
  libcsnd-dev - development files for Csound -- C++ API
  libcsound64-dev - development files for Csound
  libcsnd6-java - Java bindings for the Csound API
  libcsound64-6.0 - main library for Csound
  csound-utils - miscellaneous utilities for the Csound system
  csound-soundfont - GM soundfont2 bank from csound
  csound-data - data files used by the csound library
  csound - powerful and versatile sound synthesis software

To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/csound/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/c/csound/csound_6.15.0~dfsg-1.dsc


Changes since the last upload:

 csound (1:6.15.0~dfsg-1) unstable; urgency=medium
 .
   * New upstream version 6.15.0~dfsg
   * Refresh patchset, drop patches applied by upstream
   * Fix build with lame header
   * Fix spelling errors
   * Provide the new package csound-soundfont with the sf2 soundbank
   * Update d/libcsound64-6.0.symbols
   * Build with libfltk1.3-dev (Closes: #974627)
   * Add libmp3lame-dev to B-Ds
   * Add me as uploader
   * Bump dh-compat to 13
 + d/rules: Remove obsolete override_dh_missing
   * Bump S-V to 4.5.1
   * Sort B-Ds
   * Mark libcsound64-doc as M-A: foreign
   * d/copyright: Add myself to the d/section
   * Use d/csound-data.install to install *.dat files and not d/rules
   * Update *.lintian-overrides
   * Remove trailing whitespaces from debian files
   * Mark python3-csound test as superficial (Closes: #974448)

Best Regards,
Dennis



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On Tue, Feb 09, 2021 at 11:33:12PM +0100, Dennis Braun wrote:
>  * Package name    : csound
>    Version : 1:6.15.0~dfsg-1

>    * Provide the new package csound-soundfont with the sf2 soundbank
   ^^^

Uploaded, in bin-NEW.

There'll be a need of a source upload afterwards.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ .--[ Makefile ]
⣾⠁⢠⠒⠀⣿⡁ # beware of races
⢿⡄⠘⠷⠚⠋⠀ all: pillage burn
⠈⠳⣄ `--- End Message ---

Processed: RFS: csound-manual/1:6.15.0~dfsg-1 -- documentation for csound

[Debian Bug Tracking System]

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

> close 982419
Bug #982419 [sponsorship-requests] RFS: csound-manual/1:6.15.0~dfsg-1 -- 
documentation for csound
Marked Bug as done
> stop
Stopping processing here.

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

Processed: RFS: csoundqt/0.9.8.1~dfsg0-1 -- frontend for the csound sound processor

[Debian Bug Tracking System]

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

> close 982420
Bug #982420 [sponsorship-requests] RFS: csoundqt/0.9.8.1~dfsg0-1 -- frontend 
for the csound sound processor
Marked Bug as done
> stop
Stopping processing here.

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

Processed: RFS: fluidsynth/2.1.7-1 -- Real-time MIDI software synthesizer

[Debian Bug Tracking System]

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

> close 982410
Bug #982410 [sponsorship-requests] RFS: fluidsynth/2.1.7-1 -- Real-time MIDI 
software synthesizer
Marked Bug as done
> stop
Stopping processing here.

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

Processed: RFS: sndfile-tools/1.5-1 -- Collection of programs for operating on sound files

[Debian Bug Tracking System]

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

> close 982412
Bug #982412 [sponsorship-requests] RFS: sndfile-tools/1.5-1 -- Collection of 
programs for operating on sound files
Marked Bug as done
> stop
Stopping processing here.

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

Bug#974812: marked as done (aspectc++: Please upgrade to llvm-toolchain-11)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 04:03:24 +
with message-id 
and subject line Bug#974812: fixed in aspectc++ 1:2.2+git20210209-1
has caused the Debian Bug report #974812,
regarding aspectc++: Please upgrade to llvm-toolchain-11
to be marked as done.

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

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


-- 
974812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aspectc++
Severity: normal

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the
archive, please upgrade to -11.

Thanks,
Sylvestre
--- End Message ---
--- Begin Message ---
Source: aspectc++
Source-Version: 1:2.2+git20210209-1
Done: Reinhard Tartler 

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated aspectc++ 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: Tue, 09 Feb 2021 22:37:09 -0500
Source: aspectc++
Architecture: source
Version: 1:2.2+git20210209-1
Distribution: unstable
Urgency: high
Maintainer: Reinhard Tartler 
Changed-By: Reinhard Tartler 
Closes: 974796 974812
Changes:
 aspectc++ (1:2.2+git20210209-1) unstable; urgency=high
 .
   * New upstream version 2.2+git20210209
   * Build against Clang 11, closes: #974796, #974812
Checksums-Sha1:
 b3f47aba614f781299a4f6fda341a73b5fadb204 2329 aspectc++_2.2+git20210209-1.dsc
 277501947004ec71ea08cdf07a74733b83e02dac 4488429 
aspectc++_2.2+git20210209.orig.tar.bz2
 54c515e174eae60d5e15dd1f33bf91f19da78101 15608 
aspectc++_2.2+git20210209-1.debian.tar.xz
Checksums-Sha256:
 407e61e24c0bc3a71c047e190e51c72f15b4a59c8aea1ca538a85a28245112c4 2329 
aspectc++_2.2+git20210209-1.dsc
 d5b01c92ce2315f4ac190b4c3803e20d6957ad1041b874674bc6067387af4e08 4488429 
aspectc++_2.2+git20210209.orig.tar.bz2
 21832ca76745874891cb0d502662638c3e04143458a5ed901ff7ee680a9ae09c 15608 
aspectc++_2.2+git20210209-1.debian.tar.xz
Files:
 fe91f0effd52b1ec0d8be713a02edb35 2329 devel optional 
aspectc++_2.2+git20210209-1.dsc
 c32e97ac892aa111ca5578467dd27cc4 4488429 devel optional 
aspectc++_2.2+git20210209.orig.tar.bz2
 5244b5772150b15bc854b257a0fc69bf 15608 devel optional 
aspectc++_2.2+git20210209-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmAjVa0UHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJsvMThAAhhPmx1BUPvDYsF/1CsNFgkOQXEUE
Rx4SAf43RRSzV6y84GMWikLX8F75SD4ylGbNE1kv7OLTZPByegCME3DAowePSEfk
OmMUHbj+lfMbxh/tJNzoDi+FIgQHPOyQLwtYOZtTv9NFXSOLIqZgBNpmal+zmrIi
Ca3W6Gvyk6ptbXUvp1Xw2BEmFJzUfYHKTw0dD24G9QZUwEbxzUIMDK1a0jlj3RWu
ZvJcTFhYhoSwsPalaVAt112yjw4kRG8NuCOjCz2rcbHDWxPEcnnqqXHnvE/ipjGA
uTbNCOKtBH2mlJ5A9Gk4Vc4+IMdidbf4nMeLWS/ml8/FXQkU2+NfIszMDu7TNJ09
AUjAJBA+aYxzusKEGN/okC0Pu8qqB3qfeZ/aOIAZNa3zrrqOLInS/P7DDXbJL1dC
qSvQRht5JIrFRaULepFCieLZvNUKj6/53HKKTUJ6Er7Jk247pTn7mRJrfj+ta4Qc
p7B3/zUHuEWQlnkwJXnZqsbnbYnZWdKcRFXfVQU6HGkfUujej5s9/xMZTUBDm2z1
nMc0xc+z+3OhZ8BH7tXoN2aJQmfURjQ+vhkoIrmr3g68boTegmrCjszpKG8Uhn+5
CUy7hDUtIRBKgnKMMkUm9etCfRF5Q5rnKpv9I7hxzNah0hVg0BB/wVPmCq+8PLUf
5a0XPBXVnqYJJ98=
=dAL4
-END PGP SIGNATURE End Message ---

Bug#974796: marked as done (aspectc++: Please upgrade to llvm-toolchain-11)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 04:03:24 +
with message-id 
and subject line Bug#974796: fixed in aspectc++ 1:2.2+git20210209-1
has caused the Debian Bug report #974796,
regarding aspectc++: Please upgrade to llvm-toolchain-11
to be marked as done.

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

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


-- 
974796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aspectc++
Severity: normal

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the 
archive, please upgrade to -11.

Thanks,
Sylvestre
--- End Message ---
--- Begin Message ---
Source: aspectc++
Source-Version: 1:2.2+git20210209-1
Done: Reinhard Tartler 

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated aspectc++ 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: Tue, 09 Feb 2021 22:37:09 -0500
Source: aspectc++
Architecture: source
Version: 1:2.2+git20210209-1
Distribution: unstable
Urgency: high
Maintainer: Reinhard Tartler 
Changed-By: Reinhard Tartler 
Closes: 974796 974812
Changes:
 aspectc++ (1:2.2+git20210209-1) unstable; urgency=high
 .
   * New upstream version 2.2+git20210209
   * Build against Clang 11, closes: #974796, #974812
Checksums-Sha1:
 b3f47aba614f781299a4f6fda341a73b5fadb204 2329 aspectc++_2.2+git20210209-1.dsc
 277501947004ec71ea08cdf07a74733b83e02dac 4488429 
aspectc++_2.2+git20210209.orig.tar.bz2
 54c515e174eae60d5e15dd1f33bf91f19da78101 15608 
aspectc++_2.2+git20210209-1.debian.tar.xz
Checksums-Sha256:
 407e61e24c0bc3a71c047e190e51c72f15b4a59c8aea1ca538a85a28245112c4 2329 
aspectc++_2.2+git20210209-1.dsc
 d5b01c92ce2315f4ac190b4c3803e20d6957ad1041b874674bc6067387af4e08 4488429 
aspectc++_2.2+git20210209.orig.tar.bz2
 21832ca76745874891cb0d502662638c3e04143458a5ed901ff7ee680a9ae09c 15608 
aspectc++_2.2+git20210209-1.debian.tar.xz
Files:
 fe91f0effd52b1ec0d8be713a02edb35 2329 devel optional 
aspectc++_2.2+git20210209-1.dsc
 c32e97ac892aa111ca5578467dd27cc4 4488429 devel optional 
aspectc++_2.2+git20210209.orig.tar.bz2
 5244b5772150b15bc854b257a0fc69bf 15608 devel optional 
aspectc++_2.2+git20210209-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmAjVa0UHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJsvMThAAhhPmx1BUPvDYsF/1CsNFgkOQXEUE
Rx4SAf43RRSzV6y84GMWikLX8F75SD4ylGbNE1kv7OLTZPByegCME3DAowePSEfk
OmMUHbj+lfMbxh/tJNzoDi+FIgQHPOyQLwtYOZtTv9NFXSOLIqZgBNpmal+zmrIi
Ca3W6Gvyk6ptbXUvp1Xw2BEmFJzUfYHKTw0dD24G9QZUwEbxzUIMDK1a0jlj3RWu
ZvJcTFhYhoSwsPalaVAt112yjw4kRG8NuCOjCz2rcbHDWxPEcnnqqXHnvE/ipjGA
uTbNCOKtBH2mlJ5A9Gk4Vc4+IMdidbf4nMeLWS/ml8/FXQkU2+NfIszMDu7TNJ09
AUjAJBA+aYxzusKEGN/okC0Pu8qqB3qfeZ/aOIAZNa3zrrqOLInS/P7DDXbJL1dC
qSvQRht5JIrFRaULepFCieLZvNUKj6/53HKKTUJ6Er7Jk247pTn7mRJrfj+ta4Qc
p7B3/zUHuEWQlnkwJXnZqsbnbYnZWdKcRFXfVQU6HGkfUujej5s9/xMZTUBDm2z1
nMc0xc+z+3OhZ8BH7tXoN2aJQmfURjQ+vhkoIrmr3g68boTegmrCjszpKG8Uhn+5
CUy7hDUtIRBKgnKMMkUm9etCfRF5Q5rnKpv9I7hxzNah0hVg0BB/wVPmCq+8PLUf
5a0XPBXVnqYJJ98=
=dAL4
-END PGP SIGNATURE End Message ---

Processed: RFS: mp3fs/1.1-1 -- FUSE filesystem for transcoding FLAC to MP3 on the fly

[Debian Bug Tracking System]

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

> close 982415
Bug #982415 [sponsorship-requests] RFS: mp3fs/1.1-1 -- FUSE filesystem for 
transcoding FLAC to MP3 on the fly
Marked Bug as done
> stop
Stopping processing here.

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

Bug#971014: marked as done (Reproducible bug in inline_data handling with ACL)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 03:33:37 +
with message-id 
and subject line Bug#971014: fixed in e2fsprogs 1.46.1-1
has caused the Debian Bug report #971014,
regarding Reproducible bug in inline_data handling with ACL
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.)


-- 
971014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: e2fsprogs
Version: 1.46~WIP.2019.10.03-1
Severity: normal
File: /sbin/mke2fs
X-Debbugs-Cc: j...@joshtriplett.org

This bug exists in both 1.45.6-1 (sid) and 1.46~WIP.2019.10.03-1
(experimental).

In the course of creating some filesystems containing Debian
installations using `mke2fs -d`, I managed to find a bug in the
`inline_data` handling, which seems to apply to files containing ACLs.
On a default Debian installation, /var/log/journal triggered this
problem.

I managed to create a minimal test case. To reproduce:

mkdir -p target/testdir
setfacl --restore=- <
Last mounted on:  
Filesystem UUID:  931e3151-83db-4c33-be5f-655c9323fab4
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  ext_attr resize_inode dir_index sparse_super2 
filetype inline_data sparse_super large_file
Filesystem flags: signed_directory_hash 
Default mount options:user_xattr acl
Filesystem state: clean
Errors behavior:  Continue
Filesystem OS type:   Linux
Inode count:  2048
Block count:  2048
Reserved block count: 102
Free blocks:  1911
Free inodes:  2036
First block:  0
Block size:   4096
Fragment size:4096
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 2048
Inode blocks per group:   128
Filesystem created:   Sat Sep 26 00:50:53 2020
Last mount time:  n/a
Last write time:  Sat Sep 26 00:50:53 2020
Mount count:  0
Maximum mount count:  -1
Last checked: Sat Sep 26 00:50:53 2020
Check interval:   0 ()
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:   256
Required extra isize: 32
Desired extra isize:  32
Default directory hash:   half_md4
Directory Hash Seed:  df46d104-ed26-4cea-ac61-0feff2a54622


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

Kernel: Linux 5.8.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: systemd (via /run/systemd/system)

Versions of packages e2fsprogs depends on:
ii  libblkid12.36-3+b1
ii  libc62.31-3
ii  libcom-err2  1.45.6-1
ii  libext2fs2   1.46~WIP.2019.10.03-1
ii  libss2   1.45.6-1
ii  libuuid1 2.36-3+b1
ii  logsave  1.45.6-1

Versions of packages e2fsprogs recommends:
pn  e2fsprogs-l10n  

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  
pn  fuse2fs
pn  gpart  
ii  parted 3.3-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: e2fsprogs
Source-Version: 1.46.1-1
Done: Theodore Y. Ts'o 

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

Debian distribution maintenance software
pp.
Theodore Y. Ts'o  (supplier of updated e2fsprogs 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: Tue, 09 Feb 2021 17:36:02 -0500
Source: e2fsprogs
Architecture: source
Version: 1.46.1-1
Distribution: unstable
Urgency: medium
Maintainer: Theodore Y. Ts'o 
Changed-By: Theodore Y. Ts'o 
Closes: 966686 971014
Changes:
 e2fsprogs (1.46.1-1) unstable; urgency=medium
 .
   * Drop transitional packages libcomerr2, e2fslibs, and e2fslibs-dev
   * Fix a bug in libext2fs and debugfs when trying to set an extended
 attribute wil

Bug#966686: marked as done (please add build profiles noudeb and pkg.e2fsprogs.no-static to e2fsprogs)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 03:33:37 +
with message-id 
and subject line Bug#966686: fixed in e2fsprogs 1.46.1-1
has caused the Debian Bug report #966686,
regarding please add build profiles noudeb and pkg.e2fsprogs.no-static to 
e2fsprogs
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.)


-- 
966686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: e2fsprogs
Version: 1.45.6-1
Severity: wishlist
Tags: patch

Hi Ted,

can I ask you to add more build profiles to e2fsprogs?

In the light of #966330, it would help a lot to have a
pkg.e2fsprogs.no-static profile as a workaround until the situation with
util-linux is sorted out. The profile would be useful beyond as it'd cut
down in build time.

I also suggest adding support for the standard noudeb profile. A number
of other packages already support it. Doing so here adds consistency to
the archive and again allows cutting down in build time.

The savings in build time are small. But if you build e2fsprogs ten
times a day (as we do on jenkins), that cost accumulates. It's a drop in
the bucket, but a relatively simple one.

Do you think that these features are worth their maintenance cost?

If you deem the cost inappropriate, please close the bug after tagging
it wontfix. There is no use in having it stick around.

In any case, I'm attaching a patch for your convenience.

Helmut
diff --minimal -Nru e2fsprogs-1.45.6/debian/changelog 
e2fsprogs-1.45.6/debian/changelog
--- e2fsprogs-1.45.6/debian/changelog   2020-03-21 04:49:33.0 +0100
+++ e2fsprogs-1.45.6/debian/changelog   2020-08-01 11:04:08.0 +0200
@@ -1,3 +1,10 @@
+e2fsprogs (1.45.6-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add support for build profiles pkg.e2fsprogs.no-static and noudeb.
+
+ -- Helmut Grohne   Sat, 01 Aug 2020 11:04:08 +0200
+
 e2fsprogs (1.45.6-1) unstable; urgency=medium
 
   * New upstream release
diff --minimal -Nru e2fsprogs-1.45.6/debian/control 
e2fsprogs-1.45.6/debian/control
--- e2fsprogs-1.45.6/debian/control 2020-03-21 04:49:33.0 +0100
+++ e2fsprogs-1.45.6/debian/control 2020-08-01 10:59:29.0 +0200
@@ -33,6 +33,7 @@
  of the output will also be written to standard output.
 
 Package: e2fsck-static
+Build-Profiles: 
 Priority: optional
 Depends: ${misc:Depends}
 Recommends: sash | bash-static | zsh-static | busybox-static
@@ -132,6 +133,7 @@
  This package contains the development environment for the ss library.
 
 Package: e2fsprogs-udeb
+Build-Profiles: 
 Package-Type: udeb
 Section: debian-installer
 Priority: optional
diff --minimal -Nru e2fsprogs-1.45.6/debian/rules e2fsprogs-1.45.6/debian/rules
--- e2fsprogs-1.45.6/debian/rules   2020-03-21 04:49:33.0 +0100
+++ e2fsprogs-1.45.6/debian/rules   2020-08-01 11:04:08.0 +0200
@@ -68,7 +68,9 @@
 
 override_dh_auto_build:
$(MAKE) -C ${stdbuilddir} V=1 all
+ifeq (,$(filter pkg.e2fsprogs.no-static,$(DEB_BUILD_PROFILES)))
$(MAKE) -C ${stdbuilddir}/e2fsck V=1 e2fsck.static
+endif
if ! test -d debian/orig-gmo ; then \
mkdir debian/orig-gmo ; \
mv po/*.gmo po/*.po debian/orig-gmo ; \
@@ -96,9 +98,11 @@
   # static libs and .h files
$(MAKE) -C ${stdbuilddir} V=1 install-libs DESTDIR=${tmpdir} 
LDCONFIG=true
 
+ifeq (,$(filter pkg.e2fsprogs.no-static,$(DEB_BUILD_PROFILES)))
   # statically-linked fsck
${INSTALL_PROGRAM} ${stdbuilddir}/e2fsck/e2fsck.static ${tmpdir}/sbin
(cd debian/tmp/usr/share/man/man8 ; cp e2fsck.8 e2fsck.static.8)
+endif
 
 ifeq ($(DEB_HOST_ARCH_OS), hurd)
${INSTALL} -m 0644 misc/mke2fs-hurd.conf ${tmpdir}/etc/mke2fs.conf
@@ -110,10 +114,12 @@
dh_install
dh_missing --fail-missing
 
+ifeq (,$(filter noudeb,$(DEB_BUILD_PROFILES)))
 override_dh_lintian:
dh_lintian
$(INSTALL) -D -p -m644 debian/e2fsprogs-udeb.lintian-overrides \
debian/e2fsprogs-udeb/usr/share/lintian/overrides/e2fsprogs-udeb
+endif
 
 override_dh_installinfo:
   # HTML docs
@@ -151,13 +157,15 @@
patch debian/$$i.symbols < debian/$$i.tmp-patch; \
/bin/rm debian/$$i.tmp-patch; \
done
-   dh_makeshlibs --add-udeb=e2fsprogs-udeb
+   dh_makeshlibs $(if $(filter 
noudeb,$(DEB_BUILD_PROFILES)),,--add-udeb=e2fsprogs-udeb)
 
 override_dh_shlibdeps:
dh_shlibdeps -pe2fsprogs -l${stdbuilddir}/lib \
-- -Ldebian/e2fsprogs.shlibs.local
+ifeq (,$(filter noudeb,$(DEB_BUILD_PROFILES)))
dh_shli

Bug#976217: marked as done (golang-github-containers-storage: Please add missing build-dependency on golang-github-moby-sys-dev)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 03:18:37 +
with message-id 
and subject line Bug#976217: fixed in golang-github-containers-storage 
1.25.0+dfsg1-1
has caused the Debian Bug report #976217,
regarding golang-github-containers-storage: Please add missing build-dependency 
on golang-github-moby-sys-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.)


-- 
976217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-containers-storage
Version: 1.23.9+dfsg1-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch

Dear maintainers,

In Ubuntu, golang-github-containers-storage was failing to build because of
a missing build-dependency:

[...]
cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
github.com/containers/storage 
github.com/containers/storage/cmd/containers-storage 
github.com/containers/storage/drivers 
github.com/containers/storage/drivers/aufs 
github.com/containers/storage/drivers/btrfs 
github.com/containers/storage/drivers/copy 
github.com/containers/storage/drivers/devmapper 
github.com/containers/storage/drivers/graphtest 
github.com/containers/storage/drivers/overlay 
github.com/containers/storage/drivers/overlayutils 
github.com/containers/storage/drivers/quota 
github.com/containers/storage/drivers/register 
github.com/containers/storage/drivers/vfs 
github.com/containers/storage/drivers/zfs 
github.com/containers/storage/internal/opts 
github.com/containers/storage/pkg/archive 
github.com/containers/storage/pkg/chrootarchive 
github.com/containers/storage/pkg/config 
github.com/containers/storage/pkg/devicemapper 
github.com/containers/storage/pkg/directory 
github.com/containers/storage/pkg/dmesg 
github.com/containers/storage/pkg/fileutils 
github.com/containers/storage/pkg/fsutils 
github.com/containers/storage/pkg/homedir 
github.com/containers/storage/pkg/idtools 
github.com/containers/storage/pkg/ioutils 
github.com/containers/storage/pkg/locker 
github.com/containers/storage/pkg/lockfile 
github.com/containers/storage/pkg/longpath 
github.com/containers/storage/pkg/loopback 
github.com/containers/storage/pkg/mflag 
github.com/containers/storage/pkg/mflag/example 
github.com/containers/storage/pkg/mount 
github.com/containers/storage/pkg/parsers 
github.com/containers/storage/pkg/parsers/kernel 
github.com/containers/storage/pkg/parsers/operatingsystem 
github.com/containers/storage/pkg/pools 
github.com/containers/storage/pkg/promise 
github.com/containers/storage/pkg/reexec 
github.com/containers/storage/pkg/stringid 
github.com/containers/storage/pkg/stringutils 
github.com/containers/storage/pkg/system 
github.com/containers/storage/pkg/tarlog 
github.com/containers/storage/pkg/truncindex 
github.com/containers/storage/pkg/unshare
src/github.com/containers/storage/pkg/mount/mountinfo.go:4:2: cannot find 
package "github.com/moby/sys/mountinfo" in any of:
/usr/lib/go-1.15/src/github.com/moby/sys/mountinfo (from $GOROOT)

/<>/golang-github-containers-storage-1.23.9+dfsg1/obj-x86_64-linux-gnu/src/github.com/moby/sys/mountinfo
 (from $GOPATH)
dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
github.com/containers/storage 
github.com/containers/storage/cmd/containers-storage 
[...]

  
(https://launchpad.net/ubuntu/+source/golang-github-containers-storage/1.23.9+dfsg1-1/+build/20330377)

Presumably this hasn't failed in Debian because some other build-dependency
is pulling this package in there.  But the package shouldn't rely on this,
since it is directly required by golang-github-containers-storage.

Please see the attached trivial patch to add golang-github-moby-sys-dev to
build-dependencies.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru golang-github-containers-storage-1.23.9+dfsg1/debian/control 
golang-github-containers-storage-1.23.9+dfsg1/debian/control
--- golang-github-containers-storage-1.23.9+dfsg1/debian/control
2020-11-23 14:05:11.0 -0800
+++ golang-github-containers-storage-1.23.9+dfsg1/debian/control
2020-12-01 09:03:25.0 -0800
@@ -16,6 +16,7 @@
golang-github-hashicorp-go-multierror-dev,
golang-github-klauspost-pgzip-dev,
  

Bug#981770: marked as done (erfs: Missing dependency on openssl)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 02:21:52 +
with message-id 
and subject line Bug#981770: fixed in erfs 1.4-1
has caused the Debian Bug report #981770,
regarding erfs: Missing dependency on openssl
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.)


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

https://ci.debian.net/data/autopkgtest/testing/amd64/e/erfs/10222343/log.gz

...
autopkgtest [02:03:35]: test upstream-tests: [---
/usr/bin/erfs: line 146: openssl: command not found
/usr/bin/erfs: line 146: openssl: command not found
/usr/bin/erfs: line 147: openssl: command not found
/usr/bin/erfs: line 147: openssl: command not found
/usr/bin/erfs: line 148: openssl: command not found
/usr/bin/erfs: line 148: openssl: command not found
/usr/bin/erfs: line 149: openssl: command not found
/usr/bin/erfs: line 149: openssl: command not found
fuse: device not found, try 'modprobe fuse' first
ERROR: sshfs failed.
1. The volume is already mounted.
2. Wrong SHARE-SECRET.
3. The server can not be reached.
autopkgtest [02:03:36]: test upstream-tests: ---]
autopkgtest [02:03:36]: test upstream-tests:  - - - - - - - - - - results - - - 
- - - - - - -
upstream-tests   FAIL non-zero exit status 1
autopkgtest [02:03:36]: test upstream-tests:  - - - - - - - - - - stderr - - - 
- - - - - - -
/usr/bin/erfs: line 146: openssl: command not found
/usr/bin/erfs: line 146: openssl: command not found
/usr/bin/erfs: line 147: openssl: command not found
/usr/bin/erfs: line 147: openssl: command not found
/usr/bin/erfs: line 148: openssl: command not found
/usr/bin/erfs: line 148: openssl: command not found
/usr/bin/erfs: line 149: openssl: command not found
/usr/bin/erfs: line 149: openssl: command not found
fuse: device not found, try 'modprobe fuse' first
autopkgtest [02:03:36]:  summary
upstream-tests   FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: erfs
Source-Version: 1.4-1
Done: Daniel Echeverri 

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

Debian distribution maintenance software
pp.
Daniel Echeverri  (supplier of updated erfs 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: Tue, 09 Feb 2021 19:25:36 -0500
Source: erfs
Architecture: source
Version: 1.4-1
Distribution: unstable
Urgency: medium
Maintainer: skyper 
Changed-By: Daniel Echeverri 
Closes: 981770
Changes:
 erfs (1.4-1) unstable; urgency=medium
 .
   * New upstream release.
   * debian/control
 + Add myself as Uploader.
 + Add openssl in Depends. (Closes: #981770)
 + Bump Standars-Version 4.5.1.
   * debian/tests/control
 + Add "isolation-machine" autopkgtest restriction,
   this test does not work in schroot environment.
Checksums-Sha1:
 a80a5b1f5eba904a94f64de2336eb8d9b3fbf42c 1785 erfs_1.4-1.dsc
 d2bba27757ece50bd0fb5ea20644bf8883d17ef9 42742 erfs_1.4.orig.tar.gz
 034748e17e47af5e8026a616da36aff1b0871a4d 2264 erfs_1.4-1.debian.tar.xz
 af7e984a0d7be9853647b9263b70474a6366a5fb 5647 erfs_1.4-1_amd64.buildinfo
Checksums-Sha256:
 fc3ae3d8852f35f33d5e5e639ebf479682e14a5015d4a2dc918c8399f0fa7b1f 1785 
erfs_1.4-1.dsc
 061159a0988c2456c85ceff1738c253e7628208147dfacd9ecbff8cedf5918ac 42742 
erfs_1.4.orig.tar.gz
 83b83e8e635c2fe43da27d5b1d373023cc482c46a1399b565bfde738e145651b 2264 
erfs_1.4-1.debian.tar.xz
 1e68a4df80f96b21499bf36c48a016d341afc038d9f090bb09a41a548bc81798 5647 
erfs_1.4-1_amd64.buildinfo
Files:
 aba0160bec20bec4bcfb40213f61ff07 1785 net optional erfs_1.4-1.dsc
 0190c42a588b4f5f4d5a65304cea6617 42742 net optional erfs_1.4.orig.tar.gz
 4497a9e91943d6f14029f031508dceae 2264 net optional erfs_1.4-1.debian.tar.xz
 96d183a343c859ca0c9d9b2f210ce4ba 5647 net optional erfs_1.4-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE0NCFsWnDv9lASFj6IfwpUEtSMNsFAmAjOGsTHGVwc2lsb25A
ZGViaWFuLm9yZwAKCRAh/ClQS1Iw25HrEACbn

Bug#982402: marked as done (Firmware needs prober)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 04:45:47 +0300
with message-id <1436711612921...@mail.yandex.ru>
and subject line Re: Firmware needs prober
has caused the Debian Bug report #982402,
regarding Firmware needs prober
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.)


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

Sure, one can install
all the firmware-*
packages in Debian, and thus be sure one has all the firmware one needs.

However that is a big waste. Many megabytes of wasted updates for who
knows what, some IBM printer from 1967, who knows?

Therefore there should be a package, that probes the system, to see
exactly what firmware packages one really needs.

Yes, it needs to be a highly specialized script that knows what kinds of
places to probe for what. (like lshw.)

And in its man page it needs to say "turn on / plug in all your devices
for best results."

Sure, a lot of firmware needs just cannot be probed, and one must wait
for problems to occur before one starts searching Google with the
symptoms, finally finding the answer, hopefully.

Yes, it would be nice if each hardware that needed firmware could be
probed in a standard way so that it would respond saying what firmware
it needed. Etc.
--- End Message ---
--- Begin Message ---
Hi,

This part of BTS is devoted to packaging of already existing software.

If there is software which may be used as you described, then you may
open correct RFP bug report for packaging it.

If there is no such software you may discuss your ideas in
debian-de...@lists.debian.org mailing list. And maybe someone will be
interested enough to implement them in code.

[1] https://lists.debian.org/debian-devel/2021/02/maillist.html

Best wishes,
Boris--- End Message ---

Bug#981814: marked as done (lilypond-doc: Unable to upgrade)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 01:48:29 +
with message-id 
and subject line Bug#981814: fixed in lilypond 2.22.0-9
has caused the Debian Bug report #981814,
regarding lilypond-doc: Unable to upgrade
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.)


-- 
981814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lilypond-doc
Version: 2.22.0-5
Severity: normal

Dear Maintainer,

I can’t upgrade lilypond-doc because of a file conflict.

dpkg-maintscript-helper: error: file '/usr/share/info/lilypond/user' not owned
by package 'lilypond-doc:all'
dpkg-maintscript-helper: error: directory '/usr/share/info/lilypond' contains
files not owned by package lilypond-doc
:all, cannot switch to symlink
dpkg: erreur de traitement de l'archive /tmp/user/0/apt-dpkg-
install-8VsaYi/33-lilypond-doc_2.22.0-8_all.deb (--unpac
k) :

Yours,
n.



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 5.7.0-1-686-pae (SMP w/3 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr:en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lilypond-doc depends on:
ii  install-info  6.7.0.dfsg.2-6

Versions of packages lilypond-doc recommends:
ii  lilypond-doc-html  2.22.0-8
ii  lilypond-doc-pdf   2.22.0-8

Versions of packages lilypond-doc suggests:
pn  lilypond  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lilypond
Source-Version: 2.22.0-9
Done: Anthony Fok 

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

Debian distribution maintenance software
pp.
Anthony Fok  (supplier of updated lilypond 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: Tue, 09 Feb 2021 18:18:33 -0700
Source: lilypond
Architecture: source
Version: 2.22.0-9
Distribution: unstable
Urgency: medium
Maintainer: Anthony Fok 
Changed-By: Anthony Fok 
Closes: 981814
Changes:
 lilypond (2.22.0-9) unstable; urgency=medium
 .
   * lilypond-doc: Remove stray symlink /usr/share/info/lilypond/user
 which would otherwise block the /usr/share/info/lilypond dir_to_symlink
 conversion since 2.22.0-6 and prevent lilypond-doc from upgrading.
 Thanks to Nicolas Patrois and Gabriele Stilli for reporting the bug.
 (Closes: #981814)
Checksums-Sha1:
 86afbee734e13647b1818a19dd31f9c8e6251747 4500 lilypond_2.22.0-9.dsc
 a8b00ff3c9c9124254c0a263ec0e22038eb1e6bf 82712 lilypond_2.22.0-9.debian.tar.xz
 15334831fe703fc7054ef949a11a49354b0dcf0c 13808 
lilypond_2.22.0-9_source.buildinfo
Checksums-Sha256:
 24e54a126eff8a750cae3e0f5fc80adf3f047cb49641e53c5a092203fcafb765 4500 
lilypond_2.22.0-9.dsc
 f7ddf3c99d628f1c4a62204458e6a1c8382bc6d71f31368d24d54c8fd781b080 82712 
lilypond_2.22.0-9.debian.tar.xz
 6b6d6be2e5d70415e60526ac9e0d5cad9359ae6d82f557738b40cb011581c6dc 13808 
lilypond_2.22.0-9_source.buildinfo
Files:
 dc82be5c348a10b534534e9a4ca837d5 4500 tex optional lilypond_2.22.0-9.dsc
 3fab7289978eef1a21cda01f88cd34f2 82712 tex optional 
lilypond_2.22.0-9.debian.tar.xz
 e5d9d4ab854d7b81500231cee8d847ea 13808 tex optional 
lilypond_2.22.0-9_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAmAjNKYQHGZva2FAZGVi
aWFuLm9yZwAKCRDqJQC0EsWaz0OgD/4ouhBjo0s0cg/KFY2ELJMiX3ifzOLThdlK
iuE9t7OcKVzUEULWJpGMvAHqE+snUPEwbQsY4YzYhrl6e0/zBynxUdmQkTEjZ10o
3l6KtHZfkmU/ooeQWdOTe/zEwgZz7gYXh9Uu4nukaaUb6bAaCEKtHVDJ1hFg1HkW
lGMeuowSjs6O8BJN1h1lwT9inkArI2In/kOevqyvVjMhPkAl9SVFvAZheJXjTPrP
1bjg7J6IAQDYKiy54w8LcEVg8xw9NrErlhWNrUmDWo8xVL/xvbSBHYkaM6wkHvo6
glBdKhbq86hHXR1GjZwE7U0MaDF0TIhGe3KiO0AeNPQey/nnAATMis8JlZGagre6
x2hVDOhE2+/GthIvZahYjuVEoELoovHb4P4kmI2qs6/e5ue1vTX0OM3EeCz4iGOu
NXFoKmwe3B+xZRPfROWyaSvu1CTXz8Xnn7KaPribe9NzTZX84AqwH7hHJGlpkPZn
lueN2lm90lfkyVTIcgczr84/zHXWSdJq2jF

Bug#981810: marked as done (python-fabio: regression in autopkgtest tests)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 01:03:46 +
with message-id 
and subject line Bug#981810: fixed in python-fabio 0.11.0+dfsg-2
has caused the Debian Bug report #981810,
regarding python-fabio: regression in autopkgtest tests
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.)


-- 
981810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-fabio
Version: 0.11.0+dfsg-1
Severity: serious

Hello,
autopkgtests are failing, please check the logs at:

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

The same tests are not executed during build time, and that's why the package
builds fine (i verify that just now) but then autopkgtests fail.

Regards,
Sandro

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

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: python-fabio
Source-Version: 0.11.0+dfsg-2
Done: Picca Frédéric-Emmanuel 

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated python-fabio 
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, 10 Feb 2021 01:32:43 +0100
Source: python-fabio
Architecture: source
Version: 0.11.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Closes: 981810
Changes:
 python-fabio (0.11.0+dfsg-2) unstable; urgency=medium
 .
   * fixed build option name nodocs -> nodoc
   * d/t/control: do not run test with python3-dbg (Closes: #981810).
Checksums-Sha1:
 53856b680343187ea609f6c4d64df5957e76bc3d 2956 python-fabio_0.11.0+dfsg-2.dsc
 17263d135a0c60ad55084477e75a7735a1f0 8548 
python-fabio_0.11.0+dfsg-2.debian.tar.xz
Checksums-Sha256:
 ae670200816fde2f2761d5148101c91a8acda684d4882f6a62796c5cc61e5d90 2956 
python-fabio_0.11.0+dfsg-2.dsc
 adcd4d35127855f9d4fc90e0ffb4255bf61845c1cbade70b4bbaa6faee8e670e 8548 
python-fabio_0.11.0+dfsg-2.debian.tar.xz
Files:
 2b1c787f55dd51566c2e07f767b05abb 2956 science optional 
python-fabio_0.11.0+dfsg-2.dsc
 0fa24324e65e84a65b9c287f4f9a4c46 8548 science optional 
python-fabio_0.11.0+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAmAjKjkRHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALvuuhAAgDnJuXSaSZQx4TsgMObSuV+dikiAWA9n
SFDlxd7lNsyDzngXWuZO4McLK9jWgkY3ZsTSAW/j/xPT4Hoy9aX7/cnAE03utPqS
LLbE4+xt6pVvuu3+yICCqZy9hGLsFEjX7X1DXir1nuNQT+I/jU66OF7rlb7dP5aE
KxCP/HauzZRpcVuma+cz1vvur22svx7f82J5C2nhMF5hm5oVXjKfQV6sv2r4CVx4
Rab2jYk3LtK4g8QGvqB4Sdt9JuAq3ffpfvNp4pE0fCPs5PaOxVFI200Yk0+a4Rfc
fvg1+q/bcA77vTORcmEHwzA6SPEHUsHls0sOFMxNpIt5UA14rWuKonmrWXfDM0b+
2tVKQ2Q+r7nYvJwFsW6tvyX25XUwsztLC1MdSrrTxkEUmdGauHXEwe+Up8CCrdQ/
J4FoTqJ3wDJZMcjP4bqel/NY1bwOrCsJgaOShkoT8510nPsSLrUx3vfNrwjPDKwp
cNkbhTlaoeGB8a2m3I1IGBs/5OV8opOQUvBNkw16rJReew/4c4KL4OJEu2Zn+wWi
Fjo0ljGZLbrklL7eyamD6GWG1GpfeorVexMgBuUkAPWhBXOoixoHDK1jINR/EiXh
poUP/NIzLiPYn21FtaqTzOk5ttA0A5973KtQzaLC9GN0z9tpvvgHBT4mrJbXugcG
9ZA5UNtfjhw=
=LYSD
-END PGP SIGNATURE End Message ---

Bug#928970: marked as done (RFP: jj -- FIFO-based jabber client)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 03:16:39 +0300
with message-id <102201612916...@mail.yandex.ru>
and subject line Close bug
has caused the Debian Bug report #928970,
regarding RFP: jj -- FIFO-based jabber client
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.)


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

Package: wnpp
Severity: wishlist

Homepage: https://23.fi/jj

jj is simple FIFO and filsystem-based Jabber client. It was inspired by
"ii" IRC client.


pgpoT74vMLApg.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Dead link to the project + too basic name of project for searching.--- End Message ---

Bug#740741: marked as done (RFP: xmpp-client -- console XMPP client written in pure Go.)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 03:05:12 +0300
with message-id <31361612915...@mail.yandex.ru>
and subject line Close bug
has caused the Debian Bug report #740741,
regarding RFP: xmpp-client -- console XMPP client written in pure Go.
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.)


-- 
740741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Jacob Appelbaum 

* Package name: xmpp-client
  Version : 0.1~20140304-1
  Upstream Author : Adam Langley 
* URL : http://www.github.com/agl/xmpp
* License : BSD
  Programming Lang: Golang
  Description : console XMPP client written in pure Go.
  xmpp-client is a minimal console instant messaging client for the
XMPP protocol.
  It supports Off-The-Record encryption natively and may optionally use Tor or
  connect to XMPP servers hosted as Tor Hidden Services.
  .
--- End Message ---
--- Begin Message ---
Project does not exist anymore.--- End Message ---

Bug#892384: marked as done (RFP: jabbercat -- modern XMPP client)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 02:55:34 +0300
with message-id <1416331612914...@mail.yandex.ru>
and subject line Close bug
has caused the Debian Bug report #892384,
regarding RFP: jabbercat -- modern XMPP client
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.)


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

Package: wnpp
Severity: wishlist

Package name: jabbercat
Version : git snapshot 2018-03-08
Upstream Author : Jonas Wielicki 
URL : https://jabbercat.org/
License : GPL3
Programming Lang: Python (with Qt5)
Description : modern XMPP client

"If you are intrigued by the User Experience provided by
modern, non-XMPP and/or non-free chat applications, this
is for you. We aim to provide Conversations-like chat
experience based on XMPP on the Desktop!"

This is pretty much a work in progress and should be
packaged only for experimental for now.
--- End Message ---
--- Begin Message ---
Project looks dead:
https://github.com/jabbercat/jabbercat/commits/devel
https://github.com/jabbercat/jabbercat/network--- End Message ---

Bug#977642: marked as done (5.10 kernel needs disable_fw_kms_setup=1)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2021 08:54:50 +0900 (JST)
with message-id <20210210.085450.585536173526168658.ryuta...@ict.e.titech.ac.jp>
and subject line Re: 5.10 kernel needs disable_fw_kms_setup=1
has caused the Debian Bug report #977642,
regarding 5.10 kernel needs disable_fw_kms_setup=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.)


-- 
977642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: raspi-firmware
Version: 1.20201022-1
Severity: normal
X-Debbugs-CC: lu...@debian.org

Dear Debian raspi-firmware maintainers,

Linux 5.10 kernel's vc4.ko starts partial support of RPi 2/3/4 VideoCore 4 GPU,
and it enables 4K HDMI output, which is very welcome.

But in some situation, screen output is garbled as reported at
http://lists.infradead.org/pipermail/linux-rpi-kernel/2020-November/007894.html

The above symptom can be fixed by adding disable_fw_kms_setup=1 as
reported at
http://lists.infradead.org/pipermail/linux-rpi-kernel/2020-November/007900.html

I do not think this is a bug in raspi-firmware, but config.txt is handled by
raspi-firmware, please consider to add disable_fw_kms_setup=1.

Best regards, Ryutaroh Matsumoto
--- End Message ---
--- Begin Message ---
The underlying kernel bug was fixed by Debian kernel 5.10.13.
The workaround disable_fw_kms_setup=1 becomes unnecessary.
Ryutaroh--- End Message ---

Processed: RFS: paho.mqtt.cpp/1.2.0-1 [ITP] -- Eclipse Paho MQTT C++ Client Library - development files

[Debian Bug Tracking System]

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

> close 978673
Bug #978673 [sponsorship-requests] RFS: paho.mqtt.cpp/1.2.0-1 [ITP] -- Eclipse 
Paho MQTT C++ Client Library - development files
Marked Bug as done
> stop
Stopping processing here.

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

Processed: Fix titles

[Debian Bug Tracking System]

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

> retitle 974678 RFP: openh264 -- H.264 encoding and decoding
Bug #974678 [wnpp] RFP: openh264 - H.264 encoding and decoding
Changed Bug title to 'RFP: openh264 -- H.264 encoding and decoding' from 'RFP: 
openh264 - H.264 encoding and decoding'.
> retitle 700412 O: kst -- A KDE application used for displaying scientific data
Bug #700412 [wnpp] O: kst -- A KDE application used for displaying
Changed Bug title to 'O: kst -- A KDE application used for displaying 
scientific data' from 'O: kst -- A KDE application used for displaying'.
> retitle 808074 O: fbreader -- e-book reader
Bug #808074 [wnpp] RFA: fbreader -- e-book reader
Changed Bug title to 'O: fbreader -- e-book reader' from 'RFA: fbreader -- 
e-book reader'.
> retitle 980433 ITP: buf -- Better way to work with Protocol Buffers
Bug #980433 [wnpp] ITP: buf -- 
Changed Bug title to 'ITP: buf -- Better way to work with Protocol Buffers' 
from 'ITP: buf -- '.
> retitle 944878 O: palabos -- CFD solver based on the lattice Boltzmann method
Bug #944878 [wnpp] O: palabos
Changed Bug title to 'O: palabos -- CFD solver based on the lattice Boltzmann 
method' from 'O: palabos'.
> retitle 881910 ITA: libcdio-paranoia -- library to read and control digital 
> audio CDs
Bug #881910 [wnpp] ITA: libcdio-paranoia
Changed Bug title to 'ITA: libcdio-paranoia -- library to read and control 
digital audio CDs' from 'ITA: libcdio-paranoia'.
> retitle 914035 RFA: influxdb -- Scalable datastore for metrics, events, and 
> real-time analytics
Bug #914035 [wnpp] RFA: influxdb
Changed Bug title to 'RFA: influxdb -- Scalable datastore for metrics, events, 
and real-time analytics' from 'RFA: influxdb'.
> retitle 969001 O: python-asynctest -- unittest extension for testing asyncio 
> libraries
Bug #969001 [wnpp] O: python-asynctest
Changed Bug title to 'O: python-asynctest -- unittest extension for testing 
asyncio libraries' from 'O: python-asynctest'.
> retitle 970377 ITA: python-libtrace -- Python bindings for the libtrace API
Bug #970377 [wnpp] ITA: python-libtrace
Changed Bug title to 'ITA: python-libtrace -- Python bindings for the libtrace 
API' from 'ITA: python-libtrace'.
> retitle 974914 ITA: cdrkit -- collection of computer programs for CD and DVD 
> authoring
Bug #974914 [wnpp] ITA: cdrkit
Changed Bug title to 'ITA: cdrkit -- collection of computer programs for CD and 
DVD authoring' from 'ITA: cdrkit'.
> retitle 975985 ITA: geda-gaf -- Electronics design software
Bug #975985 [wnpp] ITA: geda-gaf
Changed Bug title to 'ITA: geda-gaf -- Electronics design software' from 'ITA: 
geda-gaf'.
> retitle 976707 O: kopanocore -- Complete and feature rich groupware solution
Bug #976707 [wnpp] O: kopanocore - Complete and feature rich groupware solution
Changed Bug title to 'O: kopanocore -- Complete and feature rich groupware 
solution' from 'O: kopanocore - Complete and feature rich groupware solution'.
> retitle 976708 O: kopano-webapp -- WebApp for the Kopano Collaboration 
> Platform
Bug #976708 [wnpp] O: kopano-webapp - WebApp for the Kopano Collaboration 
Platform
Changed Bug title to 'O: kopano-webapp -- WebApp for the Kopano Collaboration 
Platform' from 'O: kopano-webapp - WebApp for the Kopano Collaboration 
Platform'.
> retitle 976709 O: kopano-webapp-plugins-files -- Kopano WebApp plugin for 
> managing attachments
Bug #976709 [wnpp] O: kopano-webapp-plugins-files - Kopano WebApp plugin for 
managing attachments
Changed Bug title to 'O: kopano-webapp-plugins-files -- Kopano WebApp plugin 
for managing attachments' from 'O: kopano-webapp-plugins-files - Kopano WebApp 
plugin for managing attachments'.
> retitle 976710 O: z-push -- open source implementation of the ActiveSync 
> protocol
Bug #976710 [wnpp] O: z-push - open source implementation of the ActiveSync 
protocol
Changed Bug title to 'O: z-push -- open source implementation of the ActiveSync 
protocol' from 'O: z-push - open source implementation of the ActiveSync 
protocol'.
> retitle 977266 O: python-bsddb3 -- Python interface for Berkeley DB
Bug #977266 [wnpp] O: python-bsddb3 - Python interface for Berkeley DB
Changed Bug title to 'O: python-bsddb3 -- Python interface for Berkeley DB' 
from 'O: python-bsddb3 - Python interface for Berkeley DB'.
> retitle 975732 ITP: xmppc -- command line xmpp client
Bug #975732 {Done: Stefan Kropp } [wnpp] ITP: xmppc - 
command line xmpp client
Changed Bug title to 'ITP: xmppc -- command line xmpp client' from 'ITP: xmppc 
- command line xmpp client'.
> retitle 720456 ITP: solarized -- solarized colorscheme for Vim
Bug #720456 {Done: Marco Villegas } [wnpp] ITP: solarized 
colorscheme for Vim
Changed Bug title to 'ITP: solarized -- solarized colorscheme for Vim' from 
'ITP: solarized colorscheme for Vim'.
> retitle 981140 ITP: xbanish -- banish the mouse cursor when typing, show it 
> again when the mouse moves
Bug #981140 {Done: Scupake } [wnpp] ITP: xbanish: banish 
the mouse cursor when typing, show it again when the m

Bug#981804: marked as done (yubioath-desktop: fails to read yubikey)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 23:33:50 +
with message-id 
and subject line Bug#981804: fixed in yubioath-desktop 5.0.4+post1-1
has caused the Debian Bug report #981804,
regarding yubioath-desktop: fails to read yubikey
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.)


-- 
981804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yubioath-desktop
Version: 5.0.4-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: norb...@preining.info

Hi all,

A flush of updates came in, besides that some yubi package updates,
and this morning the yubioath desktop application does not recognize my
yubikey (4, USB) anymore. No reaction. Yesterday it was still working.

[~] ykls
Reader:  Yubico Yubikey NEO OTP+U2F+CCID 00 00
Version: 0.1.3


Thanks

Norbert



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

Kernel: Linux 5.10.13 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages yubioath-desktop depends on:
ii  libc6  2.31-9
ii  libgcc-s1  10.2.1-6
ii  libqt5core5a   5.15.2+dfsg-4
ii  libqt5gui5 5.15.2+dfsg-4
ii  libqt5qml5 5.15.2+dfsg-3
ii  libqt5quick5   5.15.2+dfsg-3
ii  libqt5quickcontrols2-5 5.15.2+dfsg-2
ii  libqt5widgets5 5.15.2+dfsg-4
ii  libstdc++6 10.2.1-6
ii  pcscd  1.9.0-1
ii  python3-yubikey-manager4.0.0~a1-1
ii  qml-module-io-thp-pyotherside  1.5.9-2+b3
ii  qml-module-qt-labs-platform5.15.2+dfsg-2
ii  qml-module-qt-labs-settings5.15.2+dfsg-3
ii  qml-module-qtquick-controls5.15.2-2
ii  qml-module-qtquick-controls2   5.15.2+dfsg-2
ii  qml-module-qtquick-dialogs 5.15.2-2

yubioath-desktop recommends no packages.

yubioath-desktop suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: yubioath-desktop
Source-Version: 5.0.4+post1-1
Done: Taowa Rosetwig 

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

Debian distribution maintenance software
pp.
Taowa Rosetwig  (supplier of updated yubioath-desktop 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: Tue, 09 Feb 2021 16:06:45 -0500
Source: yubioath-desktop
Architecture: source
Version: 5.0.4+post1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Authentication Maintainers 

Changed-By: Taowa Rosetwig 
Closes: 981804
Changes:
 yubioath-desktop (5.0.4+post1-1) unstable; urgency=medium
 .
   * New upstream version 5.0.4+post1 (Closes: #981804)
Checksums-Sha1:
 7fed30bf1cb288b096bffd6a6f5167d36e1bb97f 2376 
yubioath-desktop_5.0.4+post1-1.dsc
 a87c54c0d04532f570a1801b329bdbc526410213 5658957 
yubioath-desktop_5.0.4+post1.orig.tar.gz
 73b6018b0060316b86c6eba22c5c208a06357775 5956 
yubioath-desktop_5.0.4+post1-1.debian.tar.xz
 5e853ab5d321c8ef8f91aa2005aa4b476c68d086 11843 
yubioath-desktop_5.0.4+post1-1_amd64.buildinfo
Checksums-Sha256:
 1f8927c371521f2318173c8ee493e116b0dd2c3be08c2e974d456201fbb240e4 2376 
yubioath-desktop_5.0.4+post1-1.dsc
 aff09fc044344704613fefe6550bd1d3023984ea1c33c25f8db5cb0c9fe66a60 5658957 
yubioath-desktop_5.0.4+post1.orig.tar.gz
 f6f7dba055a25613688f2c406bff4090ec69dd5e5a38c9a461c498992268a13f 5956 
yubioath-desktop_5.0.4+post1-1.debian.tar.xz
 c3e40467de910047871cf4ba5f8ebb90fc7e4e6ce9925161b915e566ea4fee04 11843 
yubioath-desktop_5.0.4+post1-1_amd64.buildinfo
Files:
 54d1c1df67b5418fce5ede5d9a71895e 2376 utils optional 
yubioath-desktop_5.0.4+post1-1.dsc
 be55401f076405639393a53a2b6a7bc6 5658957 utils optional 
yubioath-desktop_5.0.4+post1.orig.tar.gz
 484a4606d5c4f84

Bug#957384: marked as done (jabber-muc: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 22:33:31 +
with message-id 
and subject line Bug#957384: fixed in jabber-muc 0.8-8
has caused the Debian Bug report #957384,
regarding jabber-muc: ftbfs with GCC-10
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.)


-- 
957384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jabber-muc
Version: 0.8-7
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/jabber-muc_0.8-7_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
  |   ^~~
In file included from /usr/include/glib-2.0/glib.h:110,
 from ../../include/jcomp.h:35,
 from jcr_main_stream_error.c:23:
/usr/include/glib-2.0/glib/deprecated/gthread.h:100:10: note: declared here
  100 | GThread *g_thread_create   (GThreadFunc   func,
  |  ^~~
jcr_base_connect.c: In function ‘jcr_send_start_stream’:
jcr_base_connect.c:87:48: warning: format ‘%d’ expects argument of type ‘int’, 
but argument 3 has type ‘gsize’ {aka ‘long unsigned int’} [-Wformat=]
   87 | log_debug(JDBG, "Opening XML stream: sent %d bytes", bytes);
  |   ~^ ~
  || |
  |int   gsize {aka 
long unsigned int}
  |   %ld
a - jcr_xdb.o
a - jcr_log.o
a - jcr_deliver.o
a - jcr_elements.o
a - jcr_main_stream_error.o
a - jcr_shutdown.o
a - jcr_compatibility.o
a - jcr_base_connect.o
make[3]: Leaving directory '/<>/src/jcomp'
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I../../lib -I../include `pkg-config --cflags 
glib-2.0` -D_JCOMP -D_REENTRANT -DLIBIDN  -o mu-conference libjcomp.a 
conference.o conference_room.o conference_user.o utils.o xdata.o admin.o 
roles.o xdb.o hash.o iq.o main.o mysql.o  -Wl,-z,relro -Wl,-z,now -L.  -ljcomp 
-lm `pkg-config --libs glib-2.0` `pkg-config --libs gthread-2.0` -lexpat -lidn
/usr/bin/ld: conference_room.o:./src/../include/jcomp-compat.h:69: multiple 
definition of `deliver__flag'; conference.o:./src/../include/jcomp-compat.h:69: 
first defined here
/usr/bin/ld: conference_room.o:./src/../include/jcomp.h:101: multiple 
definition of `jcr'; conference.o:./src/../include/jcomp.h:101: first defined 
here
/usr/bin/ld: conference_user.o:./src/../include/jcomp-compat.h:69: multiple 
definition of `deliver__flag'; conference.o:./src/../include/jcomp-compat.h:69: 
first defined here
/usr/bin/ld: conference_user.o:./src/../include/jcomp.h:101: multiple 
definition of `jcr'; conference.o:./src/../include/jcomp.h:101: first defined 
here
/usr/bin/ld: utils.o:./src/../include/jcomp.h:101: multiple definition of 
`jcr'; conference.o:./src/../include/jcomp.h:101: first defined here
/usr/bin/ld: utils.o:./src/../include/jcomp-compat.h:69: multiple definition of 
`deliver__flag'; conference.o:./src/../include/jcomp-compat.h:69: first defined 
here
/usr/bin/ld: xdata.o:./src/../include/jcomp.h:101: multiple definition of 
`jcr'; conference.o:./src/../include/jcomp.h:101: first defined here
/usr/bin/ld: xdata.o:./src/../include/jcomp-compat.h:69: multiple definition of 
`deliver__flag'; conference.o:./src/../include/jcomp-compat.h:69: first defined 
here
/usr/bin/ld: admin.o:./src/../include/jcomp.h:101: multiple definitio

Bug#982367: marked as done (RM: sisu-maven-plugin -- ROM; No longer used, replaced by sisu-mojos)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 22:01:37 +
with message-id 
and subject line Bug#982367: Removed package(s) from unstable
has caused the Debian Bug report #982367,
regarding RM: sisu-maven-plugin -- ROM; No longer used, replaced by sisu-mojos
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.)


-- 
982367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: debian-j...@lists.debian.org

Hi,

Please remove the sisu-maven-plugin package, it has been replaced
by sisu-mojos and is no longer used.

Thank you,

Emmanuel Bourg
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libsisu-maven-plugin-java |  1.4-1 | all
sisu-maven-plugin |  1.4-1 | source

--- Reason ---
ROM; No longer used, replaced by sisu-mojos
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 982...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/982367

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#982393: marked as done (RM: r-cran-vim [armel] -- ROM; Needs to be removed on armel due to missing Build-Depends)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 22:01:53 +
with message-id 
and subject line Bug#982393: Removed package(s) from unstable
has caused the Debian Bug report #982393,
regarding RM: r-cran-vim [armel] -- ROM; Needs to be removed on armel due to 
missing Build-Depends
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.)


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

Hi,

it turned out that the Build-Depends node-highlight.js is missing on
armel and thus r-cran-vim does not build on this architecture.  Please
remove the package there to enable testing migration.

Kind regards

  Andreas.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

r-cran-vim | 6.0.0+dfsg-2 | armel

--- Reason ---
ROM; Needs to be removed on armel due to missing Build-Depends
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 982...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/982393

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

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---

Bug#981554: marked as done (samba-common: samba-common/dhcp PRIORITY=high results in prompt during d-i task-kde-desktop install)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 21:50:44 +
with message-id 
and subject line Bug#981554: fixed in samba 2:4.13.4+dfsg-1
has caused the Debian Bug report #981554,
regarding samba-common: samba-common/dhcp PRIORITY=high results in prompt 
during d-i task-kde-desktop install
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.)


-- 
981554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba-common
Version: 2:2:4.13.3+dfsg-1
Severity: normal

Dear Maintainer,

Selecting KDE as the desktop during instalation from this daily D-I test ISO:

   
https://cdimage.debian.org/cdimage/daily-builds/daily/20210131-1/amd64/iso-cd/debian-testing-amd64-netinst.iso

results in samba-common being installed, which then presents the user with the
debconf question samba-common/dhcp, which regards whether to edit smb.conf in
order to take DHCP into account (see: 
https://openqa.debian.net/tests/10143#step/grub/36 )

This would seem to be because this question is set to PRIORITY=high here:

   
https://sources.debian.org/src/samba/2:4.13.3+dfsg-1/debian/samba-common.config/#L69

This seems like a question that should not be asked at install time, since the
user is quite likely to have no idea what smb.conf, DHCP, WINS or IP are, and
may be concerned that they are doing something wrong by not installing
dhcp-client, or worried that they don't understand how they should go about 
doing so.

Perhaps the KDE task should not be pulling samba-common in at this point, or
perhaps the priority is set too high, but it seems clear that we should not be
bothering our new users with this question.

Cheers, Phil.
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.13.4+dfsg-1
Done: Mathieu Parent 

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

Debian distribution maintenance software
pp.
Mathieu Parent  (supplier of updated samba 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: Tue, 09 Feb 2021 22:26:43 +0100
Source: samba
Architecture: source
Version: 2:4.13.4+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Samba Maintainers 
Changed-By: Mathieu Parent 
Closes: 981554
Changes:
 samba (2:4.13.4+dfsg-1) unstable; urgency=medium
 .
   * New upstream version
 - GPG signature has changed
 - Update samba-libs.install
 - Update symbols
   * Never use priority high when asking for DHCP integration (Closes: #981554)
   * Sync CTDB patches with Ubuntu:
 - Add "ctdb-config: enable syslog by default"
 - Update "fix nfs related service names"
   * d/rules: Ubuntu specifics
 - No Ceph on i386
 - Disable some i386 packages
 - No GlusterFS
Checksums-Sha1:
 207323fa785369508252d0097be559b7a261d110 4349 samba_4.13.4+dfsg-1.dsc
 3853c72c189a990233f85333c4dfb34f2481c1ba 11682980 samba_4.13.4+dfsg.orig.tar.xz
 626675f15f7ec73a7b66aa2c01d0567920a1dc8d 247336 
samba_4.13.4+dfsg-1.debian.tar.xz
 063a4fe22f60f15d0068003c6f6fa5dc6872d10c 7145 
samba_4.13.4+dfsg-1_source.buildinfo
Checksums-Sha256:
 d6e7010d5d36e17ef8e3dd0370efa92a4478cbfb3f2d19773949fc72ef14816e 4349 
samba_4.13.4+dfsg-1.dsc
 e08a3612bac58855891fe447393b8b613c95a6a2dc1481e5ec89f3d8f6c1d980 11682980 
samba_4.13.4+dfsg.orig.tar.xz
 e98f11c0119c4e64da75a02843640c9ecf1d898fc4346acbce0c1ed61c32734d 247336 
samba_4.13.4+dfsg-1.debian.tar.xz
 6a659cd823486cd2776d402feef9c55bfc1a8141f9895b7cef56cca6b09e402d 7145 
samba_4.13.4+dfsg-1_source.buildinfo
Files:
 7aa2a764b6198f6995d10b84ac9d1bbd 4349 net optional samba_4.13.4+dfsg-1.dsc
 b9b4513d05ed4abf5369be86e6c061c4 11682980 net optional 
samba_4.13.4+dfsg.orig.tar.xz
 9df33381829605a2d59d157ce1e42536 247336 net optional 
samba_4.13.4+dfsg-1.debian.tar.xz
 18383fcf595c4b0eec8f46e4c423df86 7145 net optional 
samba_4.13.4+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEqqWLhC6ILPQU4Lqxp8cqHHgrjD8FAmAi/o8THHNhdGhpZXVA
ZGViaWFuLm9yZwAKCRCnxyoceCuMP5aCEACa49zlUQm2Uvazvt6YppXW0RdhDZ7D
lfxlU8Cx7/HomZZfidlRgR

Bug#947662: marked as done (repsnapper: depends on deprecated libpangox-1.0-0)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 21:50:36 +
with message-id 
and subject line Bug#947662: fixed in repsnapper 2.5a5-3
has caused the Debian Bug report #947662,
regarding repsnapper: depends on deprecated libpangox-1.0-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.)


-- 
947662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: repsnapper
Version: 2.5a5-2
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pangox
Control: block 947649 by -1

This package has a runtime dependency on libpangox-1.0-0, the Core X
backend for Pango, which has been deprecated since at least 2012, is
unmaintained upstream and is essentially unmaintained in Debian.

Using a general-purpose graphical toolkit such as GTK or Qt, or a
non-deprecated Pango backend with (such as Xft or Cairo), is recommended.

The severity of this bug might be increased in future if there is an
effort to remove libpangox-1.0-0 from Debian, but for the moment it's
normal-severity.

This dependency is likely to be as a result of using libgtkglext1-dev
(see #702010). It might be possible to avoid the direct dependency by
linking with -Wl,--as-needed.

smcv
--- End Message ---
--- Begin Message ---
Source: repsnapper
Source-Version: 2.5a5-3
Done: Ying-Chun Liu (PaulLiu) 

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

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated repsnapper 
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, 10 Feb 2021 05:06:34 +0800
Source: repsnapper
Architecture: source
Version: 2.5a5-3
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Closes: 947662
Changes:
 repsnapper (2.5a5-3) unstable; urgency=low
 .
   * Bump Standards-Version to 4.5.0: nothing needs to be changed
   * Bump dh compat to 13.
 - Use debhelper-compat and remove debian/compat
 - Rebuild with -Wl,--as-needed (Closes: #947662)
Checksums-Sha1:
 864a55ccb6976eacca8987bd4e284238405b0718 2023 repsnapper_2.5a5-3.dsc
 ec3ea891c7ea5f6b393e287290423f02551a2ff7 10036 repsnapper_2.5a5-3.debian.tar.xz
 f5e8c20c5faf1fc715d3f9d046b2b5ac572480d7 14808 
repsnapper_2.5a5-3_source.buildinfo
Checksums-Sha256:
 9918ef326ffae197c9fc6567ad0a72edd736103b900b2f38bce9acb33daa0d6d 2023 
repsnapper_2.5a5-3.dsc
 42faf6369b307fae55668fb2ac2ddb877cfdd600c6cb89c136b584d6e4d2b058 10036 
repsnapper_2.5a5-3.debian.tar.xz
 53c0864edb63a587a57f4173990c49c0a289627b1e79d631a3abe515dbba7372 14808 
repsnapper_2.5a5-3_source.buildinfo
Files:
 4df2270edd5e06e5f73bc5a8ec958d7f 2023 utils optional repsnapper_2.5a5-3.dsc
 9396febb8ac56b666dbed95a7180d2ba 10036 utils optional 
repsnapper_2.5a5-3.debian.tar.xz
 beccf6bb9d209e9fd752235126eb3dc8 14808 utils optional 
repsnapper_2.5a5-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmAi/UsTHHBhdWxsaXVA
ZGViaWFuLm9yZwAKCRBEFz+hPQWIiDB9D/0ST2yFef/w+KtYgbSNuZNU0IlE9Ha3
Zm0rVHxGhgGMIsLSaDdSrdmq6gGGpLLv74Yu7ez+NOQ2OX3EW6iB8rqBZfoEcokx
sQikq8njNMOrEcEb1Mxk7mlbeYo8tI3pg/QWAM0d7dF34FeiLfQlGGgJe7z9G4CK
FYB5BehUM8Lb0ylGBJ0byBLuGuYfkuBle9dz3g+0VZLyzqU270X833tOnd9HbRwP
r6ZfY72cf/PUsTfIMTjf71XIXJCP5OJYGrVFyR2faXZbRN9Jc8SZguJRl3+3Wez/
ylKWdXZMcuIp2zP7ieFxXJbvDf5BQ60wFWUXicJQiQIopqyDT53Jw+2MTHMR2+u4
9opz1wdfS2MKxJKbZqDossvCEh3+uVuXT6qJXgg7rnF4nTjfdpFvYmUjTYrW2qGe
sLxFT+QtgwUi/aRtcVqYLZzgIm7XdqH++uWb9ZqcLuVA7Uq9HzMqD/0YCynGbgRR
4sdybMurOP/fnaSHEuVRFFx+GLOJ70qnLbXUqin+MRR12ZbrkQ3Ee29ZSevtYbDr
gdxDNqiR2BmhqEr2VduZGu+jbewQmFx3A078B/UzA4G54fnXJQeZ2DjEdB8fZJW2
gcX/5JKItcnivj63BR8ZSQ0m7yCldXX7l2X3zfSuD8Q21yB5rXK72tApRxO/dHFp
EpfYXlsT3BQ3Tg==
=VP+t
-END PGP SIGNATURE End Message ---

Bug#982403: marked as done (istack-commons: FTBFS with OpenJDK 17 due to wrong -ea version parsing)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 21:34:27 +
with message-id 
and subject line Bug#982403: fixed in istack-commons 3.0.6-5
has caused the Debian Bug report #982403,
regarding istack-commons: FTBFS with OpenJDK 17 due to wrong -ea version parsing
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.)


-- 
982403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: istack-commons
Severity: important
Tags: ftbfs sid bookworm
User: debian-j...@lists.debian.org
Usertags: default-java17

istack-commons fails to build with OpenJDK 17 because the tests don't parse 
properly the version string:


  [INFO] ---
  [INFO]  T E S T S
  [INFO] ---
  [INFO] Running TestSuite
  findClass
  [ERROR] Tests run: 7, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.29 
s <<< FAILURE! - in TestSuite
  [ERROR] testFindResource(com.sun.istack.tools.ParallelWorldClassLoaderTest)  
Time elapsed: 0.004 s  <<< FAILURE!
  java.lang.NumberFormatException: For input string: "17-ea"
  at 
com.sun.istack.tools@3.0.6/com.sun.istack.tools.ParallelWorldClassLoaderTest.isJDK9(ParallelWorldClassLoaderTest.java:148)
  at 
com.sun.istack.tools@3.0.6/com.sun.istack.tools.ParallelWorldClassLoaderTest.testFindResource(ParallelWorldClassLoaderTest.java:115)

  [ERROR] testFindResources(com.sun.istack.tools.ParallelWorldClassLoaderTest)  
Time elapsed: 0 s  <<< FAILURE!
  java.lang.NumberFormatException: For input string: "17-ea"
  at 
com.sun.istack.tools@3.0.6/com.sun.istack.tools.ParallelWorldClassLoaderTest.isJDK9(ParallelWorldClassLoaderTest.java:148)
  at 
com.sun.istack.tools@3.0.6/com.sun.istack.tools.ParallelWorldClassLoaderTest.testFindResources(ParallelWorldClassLoaderTest.java:128)
--- End Message ---
--- Begin Message ---
Source: istack-commons
Source-Version: 3.0.6-5
Done: Emmanuel Bourg 

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated istack-commons 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: Tue, 09 Feb 2021 22:14:55 +0100
Source: istack-commons
Architecture: source
Version: 3.0.6-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 982403
Changes:
 istack-commons (3.0.6-5) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure with OpenJDK 17 (Closes: #982403)
   * Removed the unused dependency on sisu-inject-plexus
   * Standards-Version updated to 4.5.1
   * Switch to debhelper level 13
Checksums-Sha1:
 16197f989db812f9f85d07ad7b9606b8e8040684 2498 istack-commons_3.0.6-5.dsc
 ec018a342a5cc8f39d4dfc998ef35400979b4e22 10544 
istack-commons_3.0.6-5.debian.tar.xz
 14c71381ec94a9368a8e47b97f4e7dca6dd79d46 16766 
istack-commons_3.0.6-5_source.buildinfo
Checksums-Sha256:
 c5b8e22c229afd402989355bc91239693d1bd0decd2a5dc9d5e577ac5cc9e5a2 2498 
istack-commons_3.0.6-5.dsc
 390ef95ae4d788794cc115c88685bec21a900b06480d999cb60dee62ec3e8013 10544 
istack-commons_3.0.6-5.debian.tar.xz
 46c2d72160e08803658853f4f9a3b60e6649dd2de7ed99fafe0ed243cf31d012 16766 
istack-commons_3.0.6-5_source.buildinfo
Files:
 392a6d30076e30aa8d7282804a44f126 2498 java optional istack-commons_3.0.6-5.dsc
 64829f6e16385e18fc6ce29b375a2330 10544 java optional 
istack-commons_3.0.6-5.debian.tar.xz
 a27b52e44cf503a911d1d961363cdcc3 16766 java optional 
istack-commons_3.0.6-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmAi+2YSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsmy8QAIiGBG4F6//dFl9XFcXHYLwsO9Ne/QTS
GY0R6wlr+BMLQvj3GDf6bSpjnqLjtULiWgETP54eop/P+kZEaRIZnbMIVtVeetWx
/Cx1Qz9AaHbHX4w5wfdwqMwkLEY2nj70KAhxEY2/ISGkPEFnDqvoumSuuYVQlPVm
L7Yb2Axfrn9JErwltBEUDSD8dFBt6+GNMECo6Qaogbx1tlSte/+vT5GbyWj+kDei
NXmBgO5KDn3MH3Y+ma8KmRF7SJhYFrG7hMtcGg2v4Wn+6NLcc62I6g1roJy70aaf
dF1rpt

Bug#982352: marked as done (drop-seq-tools: Excessive dependendies)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 20:33:37 +
with message-id 
and subject line Bug#982352: fixed in drop-seq 2.4.0+dfsg-5
has caused the Debian Bug report #982352,
regarding drop-seq-tools: Excessive dependendies
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.)


-- 
982352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drop-seq-tools
Severity: normal

drop-seq-tools has many unnecessary Java dependencies, it looks like the build
dependencies are all added to the package dependencies by javahelper.
--- End Message ---
--- Begin Message ---
Source: drop-seq
Source-Version: 2.4.0+dfsg-5
Done: Emmanuel Bourg 

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated drop-seq 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: Tue, 09 Feb 2021 13:03:43 +0100
Source: drop-seq
Architecture: source
Version: 2.4.0+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Emmanuel Bourg 
Closes: 982352
Changes:
 drop-seq (2.4.0+dfsg-5) unstable; urgency=medium
 .
   * Team upload.
   * Reduce the dependencies of drop-seq-tools (Closes: #982352)
Checksums-Sha1:
 a459f6bfa8cacfe08b15a219c585bd5501b03644 2357 drop-seq_2.4.0+dfsg-5.dsc
 f8a1e6039bb100327c5f3d5c976654274735876c 60960 
drop-seq_2.4.0+dfsg-5.debian.tar.xz
 f23df645c385f47a5522503edd7465c0b494427e 15452 
drop-seq_2.4.0+dfsg-5_source.buildinfo
Checksums-Sha256:
 0669715a7b5db0e18d60847e18f427eb274660a12b315bef33decace4df9cf67 2357 
drop-seq_2.4.0+dfsg-5.dsc
 4b4697ad841bf76cf28bca1d48ddbf2df9af470fc1f58c9e9b91403554153686 60960 
drop-seq_2.4.0+dfsg-5.debian.tar.xz
 075a5185be304e3bb4d0753dd96faa402fce187dcfc7c9e26dc6f923df6ba952 15452 
drop-seq_2.4.0+dfsg-5_source.buildinfo
Files:
 d8a68d986ef973d49ec8191e1f051978 2357 science optional 
drop-seq_2.4.0+dfsg-5.dsc
 528047ea3b69b4280d694f7a29b53b0f 60960 science optional 
drop-seq_2.4.0+dfsg-5.debian.tar.xz
 907700fb4a6dd07e22672fc9e924a0ca 15452 science optional 
drop-seq_2.4.0+dfsg-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmAi7yASHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCs2bcQALP+KEhJbDEaI8wAb7exMuuINrR9c3NO
gsDu/nM4PSQ8s8ifNx9EV18X2pYiXg1v0JCWvNxEwT6uvtNs/W2pfArjYnf/2jza
mf8jY9e0s8hHOG0HVxySRsCd7dgLwkAH8EziB1QeaEVmk5Gg9prABCP7j0kXqB54
kyu0US9OWkhFW4fhtu4RUWxd/3G8k/s2qNxUiuiW4BoMDh3KqdwEkIwDUlzpbAp3
9Mp7uMgoDNVy23jvL4czJZOCuW0yJxXvz5hVNP1758hyGkuwkxE+k0tec5ZDfR9b
19t8Vd+IgJxyuO0Fld+8IgLqEUq9nYHop6qqQXQYxtykA0eZFRDQsY3Ew9sO01H5
NNfuhnxY1w4mt05++qZtKsuTqrvrUmPavnJ5TZ/GqQEOXoz09WPrrZnsFKThL/Rl
ujFnaxxRkAjpaoVKAXnMDeZzhl7xNVwT5FPlMlL6eiOjiEca+Mc9CFj33cbgcMbl
zvIT279k4AW3Va53lYxGksaHFTU2wCvRcoXlbCqVShFTWmWEHxxRnyAgIHzfw8AA
cFE8JUwPxnv5qebrQ4PEJNT0qe2iNPf/70q36Hc1LyYHndyJRFFKzcSEiH1qzx5A
X5rvCi+Q7EQRaQg1fp3JvppA3wesnKDULeuS8GPyzIez4ukB+/WC+tagXFEQ1FGj
GvJwDPYoNV/6
=lKGY
-END PGP SIGNATURE End Message ---

Bug#924570: marked as done (freeipmi: ftbfs in env with systemd installed)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 20:34:01 +
with message-id 
and subject line Bug#924570: fixed in freeipmi 1.6.6-3
has caused the Debian Bug report #924570,
regarding freeipmi: ftbfs in env with systemd installed
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.)


-- 
924570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:freeipmi
Version: 1.6.3-1.1

When systemd is installed, there will be no
 debian/tmp/etc/init.d/*
installed, while
 debian/tmp/lib/systemd/system/*.service
file exists.

In debian/rules, we delete only init.d files and without -f option.

So please either build-conficts with systemd, or just remove the
.service file, too.

-- 
YunQiang Su
--- End Message ---
--- Begin Message ---
Source: freeipmi
Source-Version: 1.6.6-3
Done: Fabio Fantoni 

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

Debian distribution maintenance software
pp.
Fabio Fantoni  (supplier of updated freeipmi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 06 Feb 2021 19:46:06 +0100
Source: freeipmi
Architecture: source
Version: 1.6.6-3
Distribution: unstable
Urgency: medium
Maintainer: Fabio Fantoni 
Changed-By: Fabio Fantoni 
Closes: 924570
Changes:
 freeipmi (1.6.6-3) unstable; urgency=medium
 .
   * remove sysvinit-utils dependency as not needed anymore
   * disable initd scripts in configure instead remove them with rm
   * remove maintscript entries related to very old versions
   * update ipmidetectd service, /etc/default/ipmidetectd was removed
   * use upstream systemd service files and add pkg-config, systemd
 and libsystemd-dev to build-depends (Closes: #924570)
   * wrap and sort
   * fix libipmiconsole.pc path
   * fix systemd service files permission
   * specify that rules require root
   * Bump Standards-Version to 4.5.1
   * add repository to upstream metadata
Checksums-Sha1:
 cb49131808f557f522b2c562dd651f381c973f7a 3062 freeipmi_1.6.6-3.dsc
 8d62b4764306203c3a068eac328bbe02eedb804d 23668 freeipmi_1.6.6-3.debian.tar.xz
 10d0e53a9decd716e1d7f0d2b9a0934dba024973 7256 freeipmi_1.6.6-3_source.buildinfo
Checksums-Sha256:
 de63edddc7db855de21c19d760c9bb0ab18c8f923649c880f07d83eaa01af018 3062 
freeipmi_1.6.6-3.dsc
 be0cd231921725b842180a6c998ed36886c932576dea33e82f292c54eff7a68e 23668 
freeipmi_1.6.6-3.debian.tar.xz
 31d3da2b01a6ba3857126ca2e5ce6e1108e8d8a8083b3f1c131a90ede0cbdb64 7256 
freeipmi_1.6.6-3_source.buildinfo
Files:
 5b2466e3a1f22e163581f7a70e8a1f8e 3062 admin optional freeipmi_1.6.6-3.dsc
 dcfe4b9db34610ed82833a5d321f830f 23668 admin optional 
freeipmi_1.6.6-3.debian.tar.xz
 b9ddb109f95af95aa8b9c577e433be30 7256 admin optional 
freeipmi_1.6.6-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAmAi7XIACgkQ6zYXGm/5
Q19wtg/+PrFtTxXm6FT7uHtwrTH9zzqeb7aidVKlkpwTrOLiQ9/D/0FB4cRqigmW
xATktJTeEgzFhYxNOi4y8aXNFqWMOlHdmO7IxFCFlx0a0MwBrBlgrgmI/NZlB4S7
HVf5T770THU2JxEWn4KJaVFKNOosdLeMZ2l1AqkTGvxymQThmMnQPKaHOIW32I9K
t1gAZQ+86eLNYuBmNXtORpVCe2EQEMXxBkSLY9S6NpUVb5ePT7XptUuBiyC7vokk
s+i1Zt2Onck+XaYRk3SKyg44ul1EGjs1uT4OGdzhlzKRiDNgBBWCOKuuv8A4GjIp
1xuuFfCPo55dLwjiseI2NKr4Lav4ZbjcUwRq2YiqeKjF1yUj8JmQD4zF20Q/TTq5
7QVgPQ+OwnXClvLucV25JnncxntH1Qcxc/qx9Ce9HhlzBhVj2qDPZHKytg7OTZmD
RbpJIXh9EK92i2/j5iZygz2OSJHAMMFVDKWcRZKk7BYO5VPoX8aAzQq6Msc+6URp
JepdB9usJdVw4CH2Nmj+x2F5ryBb6TYKFbgNh41uhDHJtGEv6uXpX3xBcgoKxLG3
5Zo/IYxyH6G865Wh1cIfZ+WSvnzjMaKwFcj5Rz68GrMPVgF1wq6w4yf79oNmf0M3
2Oc0qjt/S5O7HUU02rgt7zj88okAo8vRSRxb6DRH6iRawpgg9/A=
=DnVH
-END PGP SIGNATURE End Message ---

Bug#982306: marked as done (meschach FTCBFS: debian/rules forces the build architecture compiler as a make default)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 19:50:34 +
with message-id 
and subject line Bug#982306: fixed in meschach 1.2b-15
has caused the Debian Bug report #982306,
regarding meschach FTCBFS: debian/rules forces the build architecture compiler 
as a make default
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.)


-- 
982306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: meschach
Version: 1.2b-14
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

meschach fails to cross build from source, because debian/rules uses
$(CC) without initializing it to cross tools. The easiest way of doing
so - using dpkg's buildtools.mk - makes meschach cross buildable. Please
consider applying the attached patch.

Helmut
diff --minimal -Nru meschach-1.2b/debian/changelog 
meschach-1.2b/debian/changelog
--- meschach-1.2b/debian/changelog  2017-07-09 11:04:21.0 +0200
+++ meschach-1.2b/debian/changelog  2021-02-08 16:16:09.0 +0100
@@ -1,3 +1,10 @@
+meschach (1.2b-14.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dpkg's buildtools.mk initialize CC. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 08 Feb 2021 16:16:09 +0100
+
 meschach (1.2b-14) unstable; urgency=medium
 
   * Debian source format 3.0 (quilt)
diff --minimal -Nru meschach-1.2b/debian/rules meschach-1.2b/debian/rules
--- meschach-1.2b/debian/rules  2017-07-09 11:00:46.0 +0200
+++ meschach-1.2b/debian/rules  2021-02-08 16:16:07.0 +0100
@@ -5,6 +5,7 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
+-include /usr/share/dpkg/buildtools.mk
 DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
 
 headers = err.h machine.h   matrix.hmeminfo.h   sparse.hzmatrix.h \
--- End Message ---
--- Begin Message ---
Source: meschach
Source-Version: 1.2b-15
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated meschach 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: Tue, 09 Feb 2021 20:15:03 +0100
Source: meschach
Architecture: source
Version: 1.2b-15
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Drew Parsons 
Closes: 982306
Changes:
 meschach (1.2b-15) unstable; urgency=medium
 .
   * Standards-Version: 4.5.1
   * debhelper compatibility level 13
 - Build-Depends: debhelper-compat (= 13)
   * drop Build-Depends: dh-exec.
   * mark libmeschach1.2 as Multi-Arch: same
   * Fix FTCBFS: Let dpkg's buildtools.mk initialize CC.
 Thanks Helmut Grohne. Closes: #982306.
   * transfer maintenance to Debian Science Team
   * update debian/control
 - Homepage: 
https://maths.anu.edu.au/research/cma-proceedings/meschach-matrix-computations-c
 - salsa repo:  https://salsa.debian.org/science-team/meschach
   * update debian/rules to use dh
 - fix version at 1.2 (otherwise soname is incorrect when built
   from source dir named meschach rather than meschach-1.2b)
 - use package build scripts debian/*.install for clarity
   (no longer needs executable script or dh-exec)
 - skip dh_autoreconf: meschach is not maintained upstream,
   and configure.in no longer functions
 - build with standard dpkg-buildflags
   (provides debug symbols and hardening flags)
   * add debian/tests (autopkgtest), running torture tests
 installed as examples with libmeschach-dev.
 debian/test/makefile adapted from upstream makefile
 - tests executed with "set +e" to ignore error codes, since most
   tests end with mem_info(), which invokes fnprint (returns number
   of characters printed)
 - handle ./torture separately since it writes to stderr.
Checksums-Sha1:
 ae3070bfec6b4413615dbc1b31eb8a4df50a8232 2064 meschach_1.2b-15.dsc
 8f18b81928c4f4679970eedc98b3c2e7da02bffc 41352 meschach_1.2b-15.debian.tar.xz
Checksums-Sha256:
 ea083549670

Bug#963675: marked as done (r-bioc-rhdf5: h5read fails to read any dataset)

[Debian Bug Tracking System]

Your message dated Tue, 9 Feb 2021 19:34:49 +
with message-id <4e4549c1-d4ce-4ba5-7251-c98c95b03...@shayandoust.me>
and subject line Re: Bug#963675: Info received (Further details)
has caused the Debian Bug report #963675,
regarding r-bioc-rhdf5: h5read fails to read any dataset
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.)


-- 
963675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-bioc-rhdf5
Version: 2.32.0+dfsg-1
Severity: important

Dear Maintainer,

I have been using rhdf5 to load data generated by other programs so that I can 
plot these data using R.

With the current version of rhdf5, I cannot load any dataset from HDF5 files 
that previously worked fine.

I run the following commands in an R session:

library(rhdf5)
data_file <- 'path_to_data_file.hdf5'
h5ls(data_file)
df <- h5read(data_file, '/dataset/path')

I expect that h5ls() will list all of the groups and datasets in the HDF5 file, 
and that h5read() will return a dataframe.

The outcome is that h5ls() does list all of the groups and datasets, but 
h5read() fails with the following error message:

Error in H5Dread(h5dataset = h5dataset, h5spaceFile = h5spaceFile, 
h5spaceMem = h5spaceMem,  : 
  HDF5. Dataset. Read failed.

Running the same R commands on the same HDF5 file works on a second computer, 
which is running Debian Stable.

I am unable to determine whether or not this failure coincides with the 
transition to R 4.0.

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

Sincerely,
Rob

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages r-bioc-rhdf5 depends on:
ii  libc6  2.30-8
ii  libgcc-s1  10.1.0-3
ii  libhdf5-103-1  1.10.6+repack-2
ii  libstdc++6 10.1.0-3
ii  r-base-core [r-api-4.0]4.0.1-1
ii  r-bioc-biocgenerics [r-api-bioc-3.11]  0.34.0-1
ii  r-bioc-rhdf5lib1.10.0+dfsg1-1

Versions of packages r-bioc-rhdf5 recommends:
pn  r-cran-bit64 
ii  r-cran-testthat  2.3.2-2+b1

Versions of packages r-bioc-rhdf5 suggests:
ii  r-cran-dplyr  0.8.5-1+b1
ii  r-cran-ggplot23.3.1+dfsg-1
ii  r-cran-knitr  1.28+dfsg-2
ii  r-cran-rmarkdown  2.2+dfsg-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Dear Rob Moss,

Thank you for the initial report. It seems like this bug has indeed been fixed,
to which you've also verified.

Kind regards,
Shayan Doust--- End Message ---

Bug#981764: marked as done (autopkg tests should neither use easy_install nor pip)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 19:33:24 +
with message-id 
and subject line Bug#981764: fixed in black 20.8b1-4
has caused the Debian Bug report #981764,
regarding autopkg tests should neither use easy_install nor pip
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.)


-- 
981764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:black
Version: 20.8b1-3
Severity: important
Tags: sid bullseye

The tests should neither use easy_install nor pip to run:

it was:

if [ "$DEB_HOST_ARCH" == "amd64" ]; then
PYTHONPATH=/usr/lib/python3/dist-packages/ python3 setup.py test
else
echo "Skip the test execution on $DEB_HOST_ARCH"
fi
WARNING: The pip package is not available, falling back to EasyInstall for
handling setup_requires/test_requires; this is deprecated and will be removed in
a future version.
running test
WARNING: Testing via this command is deprecated and will be removed in a future
version. Users looking for a generic test entry point independent of test runner
are encouraged to use tox.
running egg_info


it is now with setuptools 52 (removing easy_install):


if [ "$DEB_HOST_ARCH" == "amd64" ]; then
PYTHONPATH=/usr/lib/python3/dist-packages/ python3 setup.py test
else
echo "Skip the test execution on $DEB_HOST_ARCH"
fi
WARNING: The wheel package is not available.
/usr/bin/python3: No module named pip
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 75, in
fetch_build_egg
subprocess.check_call(cmd)
  File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3', '-m', 'pip',
'--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmplyxhvuig',
'--quiet', 'setuptools_scm']' returned non-zero exit status 1.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.g4gjazay/downtmp/build.QhW/src/setup.py", line 49,
in 
setup(
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 152, in 
setup
_install_setup_requires(attrs)
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 147, in
_install_setup_requires
dist.fetch_build_eggs(dist.setup_requires)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 686, in
fetch_build_eggs
resolved_dists = pkg_resources.working_set.resolve(
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 766, in
resolve
dist = best[req.key] = env.best_match(
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1051, in
best_match
return self.obtain(req, installer)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1063, in
obtain
return installer(requirement)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 745, in
fetch_build_egg
return fetch_build_egg(self, req)
  File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 77, in
fetch_build_egg
raise DistutilsError(str(e)) from e
distutils.errors.DistutilsError: Command '['/usr/bin/python3', '-m', 'pip',
'--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmplyxhvuig',
'--quiet', 'setuptools_scm']' returned non-zero exit status 1.
--- End Message ---
--- Begin Message ---
Source: black
Source-Version: 20.8b1-4
Done: Diane Trout 

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

Debian distribution maintenance software
pp.
Diane Trout  (supplier of updated black 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: Tue, 09 Feb 2021 11:09:40 -0800
Source: black
Architecture: source
Version: 20.8b1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Diane Trout 
Closes: 981764
Changes:
 black (20.8b1-4) unstable; urgency=medium
 .
   * Modify autopkgtests to not use setup.py (Closes: #981764)
 - several

Bug#970633: marked as done (tt-rss: CVE-2020-25787 CVE-2020-25788 CVE-2020-25789)

[Debian Bug Tracking System]

Your message dated Tue, 9 Feb 2021 21:20:31 +0200
with message-id <20210209192031.GA31839@localhost>
and subject line Fixed in 20~git20201216.e48beee+dfsg-1
has caused the Debian Bug report #970633,
regarding tt-rss: CVE-2020-25787 CVE-2020-25788 CVE-2020-25789
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.)


-- 
970633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tt-rss
Version: 19.8+dfsg-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for tt-rss.

CVE-2020-25787[0]:
| An issue was discovered in Tiny Tiny RSS (aka tt-rss) before
| 2020-09-16. It does not validate all URLs before requesting them.


CVE-2020-25788[1]:
| An issue was discovered in Tiny Tiny RSS (aka tt-rss) before
| 2020-09-16. imgproxy in plugins/af_proxy_http/init.php mishandles
| $_REQUEST["url"] in an error message.


CVE-2020-25789[2]:
| An issue was discovered in Tiny Tiny RSS (aka tt-rss) before
| 2020-09-16. The cached_url feature mishandles JavaScript inside an SVG
| document.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-25787
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25787
[1] https://security-tracker.debian.org/tracker/CVE-2020-25788
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25788
[2] https://security-tracker.debian.org/tracker/CVE-2020-25789
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25789

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 20~git20201216.e48beee+dfsg-1

tt-rss (20~git20201216.e48beee+dfsg-1) unstable; urgency=high

  * new upstream snapshot (Closes: #970633)
   - Fixes: CVE-2020-25787, CVE-2020-25788, CVE-2020-25789
...
 -- Sebastian Reichel   Thu, 17 Dec 2020 10:42:00 +0100--- End Message ---

Bug#982152: marked as done (hunspell-sk: incorrect affix rule)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 19:19:35 +
with message-id 
and subject line Bug#982152: fixed in libreoffice-dictionaries 1:7.1.0~rc3-2
has caused the Debian Bug report #982152,
regarding hunspell-sk: incorrect affix rule
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.)


-- 
982152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hunspell-sk
Version: 1:7.1.0~rc3-1
Severity: normal
Tags: upstream
Forwarded: https://github.com/sk-spell/hunspell-sk/issues/32

Dear Maintainer,

The dictionary ships an incorrect affix rule:

SFX D   ň   niam   eňa is:dative is:plural

This can be vefiried by trying to use it with aspell:

Error: sk_SK.aff:387: The condition "eňa" does not guarantee that "ň" can 
always be stripped.

I don’t know much about the format or what exactly the author of the
patch intended to do with this to fix it, so I cannot provide a patch.

-- 
Cheers,
  Andrej
--- End Message ---
--- Begin Message ---
Source: libreoffice-dictionaries
Source-Version: 1:7.1.0~rc3-2
Done: Mattia Rizzolo 

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated 
libreoffice-dictionaries 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: Tue, 09 Feb 2021 19:46:14 +0100
Source: libreoffice-dictionaries
Architecture: source
Version: 1:7.1.0~rc3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Mattia Rizzolo 
Closes: 982152
Changes:
 libreoffice-dictionaries (1:7.1.0~rc3-2) unstable; urgency=medium
 .
   * Add patch from upstream's upstream to fix an incorrect rule
 in the sk_SK hunspell dict.  Closes: #982152
Checksums-Sha1:
 22a0e4c5c683d0ffe8c9fb6033449ff30fc1a32d 8019 
libreoffice-dictionaries_7.1.0~rc3-2.dsc
 533ba6226ff09b005d93b90ce87e47f44edb6dad 65160 
libreoffice-dictionaries_7.1.0~rc3-2.debian.tar.xz
 8070cc91d48cf523ef9b0a6392b331ae01e645f0 34177 
libreoffice-dictionaries_7.1.0~rc3-2_amd64.buildinfo
Checksums-Sha256:
 8a9da3edf1c6eca7011189274e50663bfbb9d1fa87e998891fe7e1a28639b5c0 8019 
libreoffice-dictionaries_7.1.0~rc3-2.dsc
 e321741e7b3c8e67813dfa4fcff74ddacb18d3bb24c24c5c2384fc76326db217 65160 
libreoffice-dictionaries_7.1.0~rc3-2.debian.tar.xz
 3ad99e75e2e5b6bcbff3d22eeabcd7e2266a9c306e4a13ca420d8db629559eaf 34177 
libreoffice-dictionaries_7.1.0~rc3-2_amd64.buildinfo
Files:
 96dd865ea9cbb3bfc00b058b0cb12f79 8019 text optional 
libreoffice-dictionaries_7.1.0~rc3-2.dsc
 fe1323a28c7409524f071fb089dd2a1b 65160 text optional 
libreoffice-dictionaries_7.1.0~rc3-2.debian.tar.xz
 6ce9faf824030d26340bfe3e753bd466 34177 text optional 
libreoffice-dictionaries_7.1.0~rc3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmAi2ysACgkQCBa54Yx2
K60wHA/+MTwK5dmfWqpHeFMhJK3CQUE0mWx4Nsd2ozsA8OwMR7s1O8Lkfdnhq8Ag
ogYReja6vNUJf3GenyVnG+mPboCxEEHw5/WHqypdUJXvXN2MVbIiY7USsvszUd1z
VABUXi4y/Wsl/OJKupOY19guP36lVhG6m8CWeBd3u39QeuFlYJumSLRrnPlZutFw
AY9zJo5h7ynMH/ZNxg7WL0+MuHs76FT7PxoL2p74BwRIcuqn9LjCeklVtbiH5dX+
Q27H/FDzw3QhUePYQ2JqHTOf9P+Rj8n26pcYJ2OxJRqbR1MmZlHk7vJ0ath/dZZb
IOwNyX1G//c23euogXzXdfbJWIZya1ZP+Obaa48l3BjMGCiTjwaKvcOp4YILLkje
yfuyrE684lrwbK6C4ZnKiZs8Z0OQzY97sHyJXH7B5+9AgMVCApNNwJ4dHV/XT56B
RkvVPkSM5NLgKvIDiNqaKZcg8Gykw67DqIrA63sQgibaad6F2AdSAtAih8qjgg21
nhF67DqjhjfOEDNJa5pR9dW/Vcwbj8EReK1km4k+x/Ad1/uQNhr87I3V40enoOSk
zXfiRDICFr3xxO8bRAt3dKbqh8DsjI5lH1jn1aMO/h3d7YSGc/Uv7t5k/i65BdwX
UnsSXEN6yxNIXFPnui8IJN/WIyBjnz27Q/r7IUMYo3YT9dPOhgs=
=c15i
-END PGP SIGNATURE End Message ---

Bug#982116: marked as done (vdjtools: autopkgtest fails due to slightly differing result on !x86)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 19:20:04 +
with message-id 
and subject line Bug#982116: fixed in vdjtools 1.2.1+git20190311-5
has caused the Debian Bug report #982116,
regarding vdjtools: autopkgtest fails due to slightly differing result on !x86
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.)


-- 
982116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdjtools
Version: 1.2.1+git20190311-4
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/arm64/v/vdjtools/10262633/log.gz

...
2c2
< vdjtools  .   11878   22574.4306601683650267E-4   
1.7544368655334885E-4   161 0.03897962619969673542.83482067688163   
0.0 0.0 1.0148381294964028
---
> vdjtools  .   11878   22574.4306601683650267E-4   
> 1.7544368655334882E-4   161 0.03897962619969673542.83482067688163 
>   0.0 0.0 1.0148381294964028
autopkgtest [20:30:38]: test run-unit-test: ---]
autopkgtest [20:30:38]: test run-unit-test:  - - - - - - - - - - results - - - 
- - - - - - -
run-unit-testFAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: vdjtools
Source-Version: 1.2.1+git20190311-5
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated vdjtools 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: Tue, 09 Feb 2021 19:57:29 +0100
Source: vdjtools
Binary: libvdjtools-java vdjtools
Architecture: source all
Version: 1.2.1+git20190311-5
Distribution: unstable
Urgency: high
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libvdjtools-java - Java library of vdjtools
 vdjtools   - framework for post-analysis of B/T cell repertoires
Closes: 982116
Changes:
 vdjtools (1.2.1+git20190311-5) unstable; urgency=high
 .
   * Team upload
   * Reduce precision of test result to work on all architectures
 Closes: #982116
Checksums-Sha1:
 a9e15fb9d28fabce7af1d93c136790da60625024 2503 vdjtools_1.2.1+git20190311-5.dsc
 6b913f7cce75a4b7be6d6fde3b0db3ad76adf5c2 6372 
vdjtools_1.2.1+git20190311-5.debian.tar.xz
 7a79799dad5bae949f7e8b9a8f288dad62c7ea7b 14542280 
libvdjtools-java_1.2.1+git20190311-5_all.deb
 eca1647995a845a959cad21f3a456adac518fdc3 42732 
vdjtools_1.2.1+git20190311-5_all.deb
 a4d968d860c5921cf645709e92d053ccc06e6af8 13784 
vdjtools_1.2.1+git20190311-5_amd64.buildinfo
Checksums-Sha256:
 02b50d21b931f145266ca86a24a977bdc117c7b15d1445913c16159d598c 2503 
vdjtools_1.2.1+git20190311-5.dsc
 73d6508d3234aeebcb20a4a66204f318d6ec05f96d70ba3d4c7c8f60e254073f 6372 
vdjtools_1.2.1+git20190311-5.debian.tar.xz
 867bf7cae459ed924c18322e5e048c90393317066b311073e07674191e319ee0 14542280 
libvdjtools-java_1.2.1+git20190311-5_all.deb
 719c5aa2de3d6a4e6f3f06e01c7251fc16dbc27a011a49071e13434be661d12b 42732 
vdjtools_1.2.1+git20190311-5_all.deb
 2cca7702a74021e0b7abd3021ecf5d8b400fee6b76fd0653fc15cc38fb432d78 13784 
vdjtools_1.2.1+git20190311-5_amd64.buildinfo
Files:
 c6795955d56d3c51d5aa73647f59ff38 2503 non-free/science optional 
vdjtools_1.2.1+git20190311-5.dsc
 f0fd70817298290330f07d8545170143 6372 non-free/science optional 
vdjtools_1.2.1+git20190311-5.debian.tar.xz
 211b5a2e8ce1a5fe273e066bdf75c8cc 14542280 non-free/science optional 
libvdjtools-java_1.2.1+git20190311-5_all.deb
 bcb88223ee1e707a1ea361b4a2ce0571 42732 non-free/science optional 
vdjtools_1.2.1+git20190311-5_all.deb
 b5238e205d3462f15958ff9bc500ea41 13784 non-free/science optional 
vdjtools_1.2.1+git20190311-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmAi3LERHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGAiA//bpsNPH6NRsXPBSD0Jts9CmFxEKD1LPFB
wLmR/hX3OCyEbHAJFmSuhwtrvOH/5du2u3HuNvF45nyhdnWcnkwWZ1wvBeNMXuHH
v4Q+zx42+eBvZDH9ZfvQ2IURYcoUyi+xV27VICQ/xOlAupapU0mbP2x92YlLvhGB
Lj6DfZdBgPOZV7/mJjXkEouq6tE0uFqQs0faPQqBWCdym0i9IMNPmqmhcn2RO+JF
UCWMv0fhQV1B19f

Bug#972573: marked as done (RFP: crowdsec -- lightweight and collaborative security engine)

[Debian Bug Tracking System]

Your message dated Tue, 9 Feb 2021 21:12:09 +0200
with message-id <20210209191209.GA31529@localhost>
and subject line crowdsec is now in unstable
has caused the Debian Bug report #972573,
regarding RFP: crowdsec -- lightweight and collaborative security engine
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.)


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

* Package name: crowdsec
  Version : 0.3.5
  Upstream Author : Crowd Security
* URL : https://crowdsec.net/
* License : MIT/Expat?
  Programming Lang: Golang
  Description : lightweight agent to detect and respond to bad behaviours

Crowdsec is an open-source, lightweight software, detecting peers with
aggressive behaviors to prevent them from accessing your systems. Its
user friendly design and assistance offers a low technical barrier of
entry and nevertheless a high security gain.

Processing is done in 5 steps:

 1. Read Data sources (log files, streams, trails, messages ...),
normalize and enrich signals
 
 2. Matching those signals to behavior patterns, aka scenarios (*)
 
 3. If an unwanted behavior is detected, deal with it through a
bouncer : a software component integrated into your applicative
stack that supports various remediations such as block, return
403, and soon captcha, 2FA, etc.

 4. (ONLY) The aggressive IP, the scenario name triggered and a
timestamp is then sent to our curation platform (to avoid
poisoning & false positives)

 5. If verified, this IP is then integrated to the block list
continuously distributed to all CrowdSec clients (which is used as
an enrichment source in step 1)

By detecting, blocking and sharing the threat they faced, all clients
are reinforcing each-others (hence the name Crowd-Security). Crowdsec
is designed for modern infrastructures, with its "Detect Here, Remedy
There" approach, letting you analyse logs coming from several sources
in one place and block threats at various levels (applicative, system,
infrastructural) of your stack.

(*) CrowdSec ships by default with scenario (brute force, port scan,
web scan, etc.) adapted for most context, but you can easily extend it
by picking more of them from the hub. It is also very easy to adapt an
existing one or create one yourself.



This is similar to fail2ban and sshguard, but with the extra touch
that it allows for federation and distribution of blocklists. It also
integrates with Prometheus, also packaged in Debian.

I haven't tested it. I guess it could be maintained by the Go team?

Source code is available here: https://github.com/crowdsecurity/crowdsec

The software is free (MIT), but to get access to the crowd-sourced
reputation data, you must also share it. The server-side of things is
also non-free.
--- End Message ---
--- Begin Message ---
crowdsec is now in unstable:
https://tracker.debian.org/pkg/crowdsec

cu
Adrian--- End Message ---

Bug#982400: marked as done (Request for Package also should mention software that hasn't been born yet)

[Debian Bug Tracking System]

Your message dated Tue, 9 Feb 2021 13:59:15 -0500
with message-id 

and subject line Re: Bug#982400: Request for Package also should mention 
software that hasn't been born yet
has caused the Debian Bug report #982400,
regarding Request for Package also should mention software that hasn't been 
born yet
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.)


-- 
982400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 7.10.0
Severity: wishlist

wnpp choice asks:

1 ITP  This is an `Intent To Package'. Please submit a package description 
along with copyright and URL in such a report.
2 OThe package has been `Orphaned'. It needs a new maintainer as soon as 
possible.
3 RFA  This is a `Request for Adoption'. Due to lack of time, resources, 
interest or something similar, the current maintainer is asking for someone 
else to maintain this package. They will maintain it in the
   meantime, but perhaps not in the best possible way. In short: the 
package needs a new maintainer.
4 RFH  This is a `Request For Help'. The current maintainer wants to continue 
to maintain this package, but they need some help to do this because their time 
is limited or the package is quite big and needs
   several maintainers.
5 RFP  This is a `Request For Package'. You have found an interesting piece of 
software and would like someone else to maintain it for Debian. Please submit a 
package description along with copyright and URL in
^^
   such a report.


OK, but if the user has not actually found it yet, please give him a sixth
choice.

E.g., "You wish somebody would write it for Debian."

Else brilliant package idea will be lost.

In fact such software might be very Debian specific.
--- End Message ---
--- Begin Message ---
> OK, but if the user has not actually found it yet, please give him a sixth
> choice.
>
> E.g., "You wish somebody would write it for Debian."
>
> Else brilliant package idea will be lost.
>
> In fact such software might be very Debian specific.

no.

this would not be something covered by wnpp then (since `packages`
woudnt exist yet). either write an email to debian-users, debian-devel
or any other relevant mailing list. reportbug is not a one stop shop
for all your needs, Dan.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi--- End Message ---

Bug#982395: marked as done (pcmanfm: FTBFS cannot compile package from source)

[Debian Bug Tracking System]

Your message dated Tue, 9 Feb 2021 20:01:04 +0100
with message-id <4ebb85b3-e9cd-44d6-9941-cb1dedc12...@users.sf.net>
and subject line Re: Bug#982395: pcmanfm: FTBFS cannot compile package from 
source
has caused the Debian Bug report #982395,
regarding pcmanfm: FTBFS cannot compile package from source
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.)


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

Hi,

I noticed that the icons in the toolbar (with tooltips "View as thumbnails", 
"View as icons", "View as small icons") are not visible whereas "Create new 
folder" is. Trying to analyse the missing package dependency I tried to build 
the package from source but failed in a stable buster system (build dependency 
are installed):

pcmanfm-1.3.1 $ dpkg-buildpackage
...
gcc -DHAVE_CONFIG_H -I. -I..  -DPACKAGE_DATA_DIR=\""/usr/share/pcmanfm"\" 
-DPACKAGE_UI_DIR=\""/usr/share/pcmanfm/ui"\" 
-DPACKAGE_MODULES_DIR=\""/usr/lib/aarch64-linux-gnu/pcmanfm"\" 
-DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -Wdate-time -D_FORTIFY_SOURCE=2 
-D_LARGEFILE_SOURCE -D_REENTRANT -D_FILE_OFFSET_BITS=64 -DG_DISABLE_ASSERT 
-DG_DISABLE_CHECKS  -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/aarch64-linux-gnu/gtk-2.0/include -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gio-unix-2.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/uuid 
-I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include 
-DG_DISABLE_CAST_CHECKS -Wall -Werror-implicit-function-declaration  -g -O2 
-fdebug-prefix-map=/home/jens/tmp/pcmanfm/pcmanfm-1.3.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
pcmanfm-desktop.o `test -f 'desktop.c' || echo './'`desktop.c
desktop.c: In function ‘fm_desktop_item_accessible_idle_do_action’:
desktop.c:939:21: note: #pragma message: FmFolderView*) (()
 #pragma message STR(FM_FOLDER_VIEW())
 ^~~
desktop.c:940:13: error: too few arguments to function 
‘fm_folder_view_item_clicked’
 fm_folder_view_item_clicked(FM_FOLDER_VIEW(item->widget), tp,
 ^~~
In file included from /usr/include/libfm/fm-gtk.h:40,
 from desktop.h:28,
 from desktop.c:27:
/usr/include/libfm/fm-folder-view.h:209:17: note: declared here
 voidfm_folder_view_item_clicked(FmFolderView* fv, GtkTreePath* 
path,
 ^~~

(The pragma was added by me to see whether the macro FM_FOLDER_VIEW is wrongly 
defined.)

/usr/include/libfm/fm-folder-view.h comes from package

ii  libfm-dev:arm64 1.3.1-1+rpt18 arm64file management support (core 
development files)

and I found no further fm_folder_view_item_clicked() declaration in 
/usr/include.

The source and the system header clearly do not match:

/pcmanfm-1.3.1 $ grep -r -C1 fm_folder_view_item_clicked . /usr/include/
./src/desktop.c-#pragma message STR(FM_FOLDER_VIEW())
./src/desktop.c:
fm_folder_view_item_clicked(FM_FOLDER_VIEW(item->widget), tp,
./src/desktop.c-item->action_type == 0 
? FM_FV_ACTIVATED : FM_FV_CONTEXT_MENU);
--
./src/desktop.c-if (widget)
./src/desktop.c:fm_folder_view_item_clicked(FM_FOLDER_VIEW(widget), 
NULL, FM_FV_CONTEXT_MENU);
./src/desktop.c-return FALSE;
--
./src/desktop.c-tp = 
gtk_tree_model_get_path(GTK_TREE_MODEL(self->model), &it);
./src/desktop.c:fm_folder_view_item_clicked(FM_FOLDER_VIEW(self), tp, 
clicked);
./src/desktop.c-if(tp)
--
./src/desktop.c-tp = gtk_tree_model_get_path(model, &it);
./src/desktop.c:
fm_folder_view_item_clicked(FM_FOLDER_VIEW(desktop), tp, FM_FV_ACTIVATED);
./src/desktop.c-if(tp)
--
./src/desktop.c-tp = gtk_tree_model_get_path(model, &it);
./src/desktop.c:
fm_folder_view_item_clicked(FM_FOLDER_VIEW(desktop), tp, FM_FV_ACTIVATED);
./src/desktop.c-if(tp)
--
/usr/include/libfm-1.0/fm-folder-view.h-/* emit signals; for interface 
implementations only */
/usr/include/libfm-1.0/fm-folder-view.h:void
fm_folder_view_item_clicked(FmFolderView* f

Bug#982390: marked as done (nmu: pbdagcon_0.3+git20180411.c14c422+dfsg-1)

[Debian Bug Tracking System]

Your message dated Tue, 9 Feb 2021 20:38:41 +0200
with message-id 

and subject line Re: Bug#982390: nmu: pbdagcon_pbdagcon
has caused the Debian Bug report #982390,
regarding nmu: pbdagcon_0.3+git20180411.c14c422+dfsg-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.)


-- 
982390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu pbdagcon_0.3+git20180411.c14c422+dfsg-1 . ANY . unstable . -m "rebuild 
against libblasr5.3.4"
--- End Message ---
--- Begin Message ---
Hi Adrian

On Tue, 9 Feb 2021 at 18:39, Adrian Bunk  wrote:
> nmu pbdagcon_0.3+git20180411.c14c422+dfsg-1 . ANY . unstable . -m "rebuild 
> against libblasr5.3.4"

Scheduled, thanks.

Regards
Graham--- End Message ---

Bug#982387: marked as done (RM: kfreebsd-11/experimental -- RoQA; end-of-life)

[Debian Bug Tracking System]

Your message dated Tue, 9 Feb 2021 17:30:20 +
with message-id <187d7929-33b7-4ca2-b8aa-9890ba3cb...@debian.org>
and subject line Bogus RM bugs
has caused the Debian Bug report #982387,
regarding RM: kfreebsd-11/experimental -- RoQA; end-of-life
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.)


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

Please remove package kfreebsd-11.  It is EOL since February 28, 2015.
The whole 11 series will be EOL on September 30, 2021.
--- End Message ---
--- Begin Message ---
I was not consulted about these bugs and as a debian-bsd member (the
primary active one) I do not agree. These packages should not be
removed.

Jess--- End Message ---

Bug#982385: marked as done (RM: ctfutils -- RoQA; end-of-life, unused)

[Debian Bug Tracking System]

Your message dated Tue, 9 Feb 2021 17:30:20 +
with message-id <187d7929-33b7-4ca2-b8aa-9890ba3cb...@debian.org>
and subject line Bogus RM bugs
has caused the Debian Bug report #982385,
regarding RM: ctfutils -- RoQA; end-of-life, unused
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.)


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

Please remove package ctfutils.  It comes from an EOL branch of freebsd.
It is unused as of now.
--- End Message ---
--- Begin Message ---
I was not consulted about these bugs and as a debian-bsd member (the
primary active one) I do not agree. These packages should not be
removed.

Jess--- End Message ---

Bug#982386: marked as done (RM: kfreebsd-10 -- RoQA; end-of-life)

[Debian Bug Tracking System]

Your message dated Tue, 9 Feb 2021 17:30:20 +
with message-id <187d7929-33b7-4ca2-b8aa-9890ba3cb...@debian.org>
and subject line Bogus RM bugs
has caused the Debian Bug report #982386,
regarding RM: kfreebsd-10 -- RoQA; end-of-life
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.)


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

Please remove the package kfreebsd-10.  It is EOL since April 30, 2018
and the whole 10 series is EOL since October 31, 2018.

Bastian
--- End Message ---
--- Begin Message ---
I was not consulted about these bugs and as a debian-bsd member (the
primary active one) I do not agree. These packages should not be
removed.

Jess--- End Message ---

Bug#982111: marked as done (r-cran-rcdk: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 17:05:15 +
with message-id 
and subject line Bug#982111: fixed in r-cran-rcdk 3.5.0+dfsg-3
has caused the Debian Bug report #982111,
regarding r-cran-rcdk: autopkgtest failure
to be marked as done.

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

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


-- 
982111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-rcdk
Version: 3.5.0+dfsg-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-rcdk/10267024/log.gz

...
autopkgtest [17:35:11]: test pkg-r-autopkgtest: 
/usr/share/dh-r/pkg-r-autopkgtest
autopkgtest [17:35:11]: test pkg-r-autopkgtest: [---
Test: Try to load the R library rcdk

R version 4.0.3 (2020-10-10) -- "Bunny-Wunnies Freak Out"
Copyright (C) 2020 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> library('rcdk')
Loading required package: rcdklibs
Loading required package: rJava
Error: package or namespace load failed for ‘rcdk’:
 .onLoad failed in loadNamespace() for 'rcdk', details:
  call: .jnew("org/openscience/cdk/formula/rules/NitrogenRule")
  error: java.lang.ClassNotFoundException
Execution halted
autopkgtest [17:35:14]: test pkg-r-autopkgtest: ---]
autopkgtest [17:35:14]: test pkg-r-autopkgtest:  - - - - - - - - - - results - 
- - - - - - - - -
pkg-r-autopkgtestFAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: r-cran-rcdk
Source-Version: 3.5.0+dfsg-3
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-rcdk 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: Tue, 09 Feb 2021 17:48:03 +0100
Source: r-cran-rcdk
Architecture: source
Version: 3.5.0+dfsg-3
Distribution: unstable
Urgency: high
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 982111
Changes:
 r-cran-rcdk (3.5.0+dfsg-3) unstable; urgency=high
 .
   * Depends: libcdkr-java
 Closes: #982111
   * Ignore one failing test
Checksums-Sha1:
 44b0b84c808fd47cfd6fdeba9e49fdd41a594f2b 2208 r-cran-rcdk_3.5.0+dfsg-3.dsc
 835d664f7492d218eebbb178c78421d710d22bd9 3116 
r-cran-rcdk_3.5.0+dfsg-3.debian.tar.xz
 86b05e9308c4b4e6a525296bc599715367c7c931 16003 
r-cran-rcdk_3.5.0+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 9420e96d34830be639650e7f715f547eb087395c46b513307e2cbe6f6775380c 2208 
r-cran-rcdk_3.5.0+dfsg-3.dsc
 d8479fd077cb0d04db05266390c11f04a904a9e48e5d62ccb3d279579745f142 3116 
r-cran-rcdk_3.5.0+dfsg-3.debian.tar.xz
 cbec7b746d021248b0c2f46d9231ac3e6c7dbf82511948aae3b80d56e3404da8 16003 
r-cran-rcdk_3.5.0+dfsg-3_amd64.buildinfo
Files:
 115ae1f73354d6ea07f7b70a55d1d80a 2208 gnu-r optional 
r-cran-rcdk_3.5.0+dfsg-3.dsc
 ef4b62c36b8e6a98be4571130747c88f 3116 gnu-r optional 
r-cran-rcdk_3.5.0+dfsg-3.debian.tar.xz
 71814451a5288667442204c8fd2cb10e 16003 gnu-r optional 
r-cran-rcdk_3.5.0+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmAivakRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFe2RAAjTy6yWdX1Pr4dR8/3OUBsg/8a+4Zn9cb
I+PBmWYn6ncdnfCfhndkhMYDWalRSOYUrNesPDTeG4bQe7R/35aFapZWk06L+op0
UrJiNZSWzOBQwUzPrPhCFlBYZlpfLcFlWEVnxAiLTPfC98t3P5Mjg29D03zZR+IO
tE3jJVHCHN1xr0/5+VCJJqyPZM3gshDNjq4btnxQ2HtVA/AfykOVkFxhatxr4EsC
kPdqyOw+guDeJsiyLrf2o+rLlXaZ+E6EJLOG7Tjanc5cV+g8fkEN/Tq11F288QIe
U55XSDvya7UEbYCj4C1vGYNc71onQiur/EtkSm5L82P4sMPBo69wz2QIGE3VWu0w
unYzwQcAj3TRvGKsTwkwZehPH+qO6c+tvQlE2cN

Bug#979231: marked as done (the new mailcap entry breaks mutt)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 16:48:23 +
with message-id 
and subject line Bug#979231: fixed in a2ps 1:4.14-7
has caused the Debian Bug report #979231,
regarding the new mailcap entry breaks mutt
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.)


-- 
979231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: a2ps
Version: 1:4.14-6
Severity: critical
Tags: newcomer
X-Debbugs-Cc: vagr...@debian.org

The recent NMU of a2ps converted the package to dh, and this enabled 
dh_installmime which was present in debian/rules but commented.

The installed file adds to mailcap an entry for "text/plain", which
breaks mutt and probably other software in fun ways.

Solution: override dh_installmime to stop installing the file until 
somebody will figure out a better plan.

It may be worth considering removing a2ps from the archive since its 
last upstream release and non-NMU uploads were from 2008 and I am being 
told that it does not support UTF-8.
paps has been mentioned as a replacement.

-- 
ciao,
Marco


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: a2ps
Source-Version: 1:4.14-7
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated a2ps 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: Tue, 09 Feb 2021 17:52:04 +0200
Source: a2ps
Architecture: source
Version: 1:4.14-7
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 979231
Changes:
 a2ps (1:4.14-7) unstable; urgency=high
 .
   * QA upload.
   * Done't install a mime entry for text/plain. (Closes: #979231)
Checksums-Sha1:
 d85c06534d13d098f490422e65ad643b18010729 1993 a2ps_4.14-7.dsc
 7fb5bd89f1f4fedc934329ee6ee21c877c932cad 28068 a2ps_4.14-7.debian.tar.xz
Checksums-Sha256:
 725b426e3c63e4a1210d7adc039af830a3312883d2f71ac5cb58d7d40825c281 1993 
a2ps_4.14-7.dsc
 384c4a384dbd884d8c93442cd08383d0264a7cff5564049d264781c96e07fa61 28068 
a2ps_4.14-7.debian.tar.xz
Files:
 ca76c6b13fb10cdc0f20a96594de84d1 1993 text optional a2ps_4.14-7.dsc
 582b9e1cc7a0828cd1401a10eae620b4 28068 text optional a2ps_4.14-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmAiuXMACgkQiNJCh6LY
mLHB3hAAokXRVfLmZaHJpCu1Jf1+8sEGZElnfc24VQYxX2nv2EUI/ngSBCpfu6WV
61xrANVtGfQLDmFmkXwFTinBTqzOO0cXL2qYqK870Dr2XcDzB46BEuAaqLt2Ms/A
QzzHTgCebAb90epcZkC7m0ycZGeNQvOQoOTVtopGaXrimrsxAKcAJRMQB6IDo/uW
35cxYctLOnKN1OSEO8pmj2OnsOJavbJsJJd2GV83iaGRrxCSMQvsYSh84TRhA9TR
4b206JhFWF/RIX+F7uz9XuJ/BKMpWKjj31qSAwjLeVQNJGQSU9cVxJqMB70JniXK
+B85S3s2QMd20bRDSjz/Fu2bA8+fyR9ZBHfxj3MHABYQ6j3sJrCUbvHK8Kw7mgyR
bfB4MICF4XyxqrOnkIq3eAfM/SuDnYy0LO6KiLnhoFG6506ACgSwqqwJ3BuC1WXx
aukZnaq+gOL2w3Wcw6xn/SFcJJZ2uyp8RPYhIGxV9LVy/EqMoX1GOSGS2wz/jmgq
u33Sc+paPUbeRnpa4YRLdHa2Rk2O7K7xHS8sPksodlU4miBCRc2fsGHyWgWY6A5A
K4bR6dsBppEp/ydL7q8gysGb9a0xQu22lhUoMUjDbrkrUWwJCXakwoSVPXiKkupg
KiwZwTZv1yhhMYqae7zrFX1Fa6+OcG5H3jqZ87as8jgHR9D+L+E=
=GUP+
-END PGP SIGNATURE End Message ---

Bug#981574: marked as done (Wrong screen resolution selected in gnome-control-center)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 16:18:35 +
with message-id 
and subject line Bug#981574: fixed in libhandy-1 1.0.3-2
has caused the Debian Bug report #981574,
regarding Wrong screen resolution selected in gnome-control-center
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.)


-- 
981574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libhandy-1
Version: 1.0.3-1

Would it be possible to backport this upstream fix?
https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/706

Thanks,
--- End Message ---
--- Begin Message ---
Source: libhandy-1
Source-Version: 1.0.3-2
Done: Arnaud Ferraris 

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

Debian distribution maintenance software
pp.
Arnaud Ferraris  (supplier of updated libhandy-1 
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: Tue, 09 Feb 2021 16:54:26 +0100
Source: libhandy-1
Architecture: source
Version: 1.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Arnaud Ferraris 
Closes: 981574
Changes:
 libhandy-1 (1.0.3-2) unstable; urgency=medium
 .
   [ Guido Günther ]
   * Backport combo-row checkmark fixes (Closes: #981574)
Checksums-Sha1:
 9dffa28095973c496b076e7595b2d553928435df 2578 libhandy-1_1.0.3-2.dsc
 ad02ff69d50ea54a16d3bbc2841b795eee323240 487829 libhandy-1_1.0.3.orig.tar.gz
 a42bbd980461dd449102b8f6221931b617430ff1 8988 libhandy-1_1.0.3-2.debian.tar.xz
 f1656b320eb1ac967c8e1e48e67de9bfd9167053 15751 
libhandy-1_1.0.3-2_source.buildinfo
Checksums-Sha256:
 db4af3819e1c8b793a107f59b348ff72c197513d52da5acdfab3970add02c544 2578 
libhandy-1_1.0.3-2.dsc
 b35adca6f13e52f9b9201f9859bf6aeb63cccf48a8b8f5070bf84afed0896297 487829 
libhandy-1_1.0.3.orig.tar.gz
 5cd11556eabef607b0861210cdc3f0a526c59e4b810580366a4988540aa03d16 8988 
libhandy-1_1.0.3-2.debian.tar.xz
 774b2e0e83aa98aa1093e8323360f044575cc34394211bc56c87bd1a8384ab23 15751 
libhandy-1_1.0.3-2_source.buildinfo
Files:
 03126791f1588c15ca15891f635b3f0a 2578 libs optional libhandy-1_1.0.3-2.dsc
 86aa0b0158233c8a327c90935828f56a 487829 libs optional 
libhandy-1_1.0.3.orig.tar.gz
 925e5de438b64825b47e1a455c7a6d51 8988 libs optional 
libhandy-1_1.0.3-2.debian.tar.xz
 6f6779c72c2e5b2553199a18ddc57644 15751 libs optional 
libhandy-1_1.0.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJOBAEBCAA4FiEEeW2zk9w/9AIituoi0+u1lmu5kZYFAmAisp0aHGFybmF1ZC5m
ZXJyYXJpc0BnbWFpbC5jb20ACgkQ0+u1lmu5kZYUYRAAodLwpofthGAYFFuF3xW+
jjgqgeOfE8Z45/nTv2QoT1LosHEgBQvDyNgkN+mn5GS7v8kpFNLNlSOm7HmE4qGG
ipPz9stRRmGI9BX95MUDQFQl/dsGvFznziybOO4X8aii90F+dgYAdZzGRi2oBCq2
30Db9RF2wpFKk//U7yFM7yECg1Efu3oBqd61r0wgp/HXjNIEkTwTLQpl15xRqp+F
198tsN5uZZUMFNvge1BXKmLxkB6+EpOefqNGzTaDRVKAVHOzYMSpBekGLBo43wcN
fvnMT+lWOEHEN/6KKmlMQ9pFBauB0Y6xUNGJaE5mmKb9WBxz55AwaVBMMhkrBXiF
QHaQWnbWxSShhCJRb0pSWe2mHkL5NgbEKp/CQWEUL9oQ+g/qMyOPocrqPumbIE6w
uWL6MtVoia6MCfZ44PXBT7FKPm1WdHptcJJtAS17WHYNhqze6B9Ag3XG7PAXgznR
aXbDbeNMf55u4vhdXE2kAkgM0+2Ayxaj+k7sqNedxUBXPUNXaSRNuc6hsPHXxB6P
eGd2gonwpEtdhrbiDsv78wpsoxZwn32xsB05K+0oqZb2lQOKXMq/rxgMery4WXpu
zUxT4B7kEFjC9py85YQyYyTPtkuuLqKiXupEC20kKHK1qVbMDfdCggHwEa1ObF6Y
A3+gMRQHaX1NL8IjZqANKsw=
=R1bP
-END PGP SIGNATURE End Message ---

Bug#982376: marked as done (netdata: Please include Prometheus Remote Write support)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 16:18:43 +
with message-id 
and subject line Bug#982376: fixed in netdata 1.29.1-2
has caused the Debian Bug report #982376,
regarding netdata: Please include Prometheus Remote Write support
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.)


-- 
982376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: netdata
Version: 1.29.0-2
Severity: wishlist

https://learn.netdata.cloud/docs/agent/backends/prometheus/remote_write
https://learn.netdata.cloud/docs/agent/exporting

Prometheus write backend is a compressed, binary protocol used by dozens of 
time series backends (I'm using victoria-metrics for example). 
It is right now not compiled in:
2021-02-09 15:34:07: netdata ERROR : EXPORTING : Prometheus Remote Write 
support isn't compiled

Would it be possible to include it?
(It requires libprotobuf-dev and libsnappy-dev at compile time.)

Thanks!
--- End Message ---
--- Begin Message ---
Source: netdata
Source-Version: 1.29.1-2
Done: Daniel Baumann 

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

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated netdata 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: Tue, 09 Feb 2021 16:53:37 +0100
Source: netdata
Architecture: source
Version: 1.29.1-2
Distribution: unstable
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 982376
Changes:
 netdata (1.29.1-2) unstable; urgency=medium
 .
   * Enabling cups support.
   * Enabling prometheus support, thanks to Peter Gervai  for the
 suggestion (Closes: #982376).
   * Updating TODO file.
Checksums-Sha1:
 f31a1729945b2cb307f8396cd432a2165e3d7937 2616 netdata_1.29.1-2.dsc
 9c1fe1b2ae8e0b6d07f3613a530837786a45aa81 670628 netdata_1.29.1-2.debian.tar.xz
 eb3c46017984b198a9bc7bac7e6f254727afe892 10166 netdata_1.29.1-2_amd64.buildinfo
Checksums-Sha256:
 9cc2a35489defb83df6bd023b0480dd9cc266bbbe61798277ad2a1f575385fa5 2616 
netdata_1.29.1-2.dsc
 10f035cf85ff4344f161c14f8ed3d02190f7cdaf64f0d91f244c3af49c18eefa 670628 
netdata_1.29.1-2.debian.tar.xz
 358ac4141ae5f9595c90bd689c18c58e5aa5e3f57611a6def33f9c3058427cb3 10166 
netdata_1.29.1-2_amd64.buildinfo
Files:
 b5d2867dbb748e36a60ffcef2f7dcf7d 2616 net optional netdata_1.29.1-2.dsc
 5a4c4f778df60ba3808040bd2ae57bd7 670628 net optional 
netdata_1.29.1-2.debian.tar.xz
 1fcbeb022134e8fa0382faa136bcaa03 10166 net optional 
netdata_1.29.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmAisYwACgkQVc8b+Yar
ucek4BAA2BxM8nVh7bTM7X+NZByTyrh+RnkMLL+aCyM9rbDyroUfJBGJdF3ampJT
w/xsQWCZrivEr6LSqn7ITZAKQNvi61yHU8vj7weVFLi7eRETCSkES8I21KA2z/CK
Lm/xiHa3e66mHTpdG8dOy92morBFe2WNPEpOuaUKNEiv8rjJzDmEs/I3ggOsHEsE
MRZbBWs2WJrl/izWyzNiG10gseSpu47yjOf4rDbdQAI/V9Lz+cg06Bco6bLoOHd1
Q3CJhyZvhPo7U3SNlpWA5kQ3TI9xvwiA9pTTYuqWmVaKBjjJ1b5bg/Xsfl2ieGc3
XgapE4x35l115TV/aqYC6WBRJpJU/BI+np7CTeRxxDVTZo0FhGaSOluwhiHZ/Xc4
Af921QisOKNoL93kN3DVHjZGidFUkwyYXkRAA7WiS28ld3cKOLrnpXnjUhyPNPKe
L6OyQI/O2VE+T7Ip1XbD5d3jzGyvxm6YEdKkRsFpNTz0eGEiJKfxj2i8TzAlaUhs
93kev4L20cDDJwpVuB8xnA9tprtsuQg8sJN18AeyPutZ7Yz5/km+0jNEncvL7cXX
Lso8nlBr+r3wIInUAB2O78rPiO7ZkBM9I6mf7yk9AEzsq+cq8Et23oscUTquORe0
xwTZQkYlmiw3oWJJhPR6Kyi43JWjrYaLAxab84Y7UyFTrdvCv7Q=
=JcdK
-END PGP SIGNATURE End Message ---

Bug#982287: marked as done (wsjtx fails to start without en_US.UTF-8 locale)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 15:34:50 +
with message-id 
and subject line Bug#982287: fixed in wsjtx 2.3.0+repack-2
has caused the Debian Bug report #982287,
regarding wsjtx fails to start without en_US.UTF-8 locale
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.)


-- 
982287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wsjtx
Version: 2.3.0+repack-1
Severity: important
X-Debbugs-Cc: hilary.sna...@zoho.com

Dear Maintainer,

On launch, the program immediately exits:

$ wsjtx
Error: locale::facet::_S_create_c_locale name not valid
$

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages wsjtx depends on:
ii  hamradio-files 20210127
ii  libboost-filesystem1.74.0  1.74.0-8
ii  libboost-log1.74.0 1.74.0-8
ii  libboost-thread1.74.0  1.74.0-8
ii  libc6  2.31-9
ii  libfftw3-single3   3.3.8-2
ii  libgcc-s1  10.2.1-6
ii  libgfortran5   10.2.1-6
ii  libgomp1   10.2.1-6
ii  libhamlib-utils4.0-4
ii  libhamlib4 4.0-4
ii  libqcustomplot2.0  2.0.1+dfsg1-4
ii  libqt5core5a   5.15.2+dfsg-2
ii  libqt5gui5 5.15.2+dfsg-2
ii  libqt5multimedia5  5.15.2-2
ii  libqt5multimedia5-plugins  5.15.2-2
ii  libqt5network5 5.15.2+dfsg-2
ii  libqt5serialport5  5.15.2-2
ii  libqt5sql5 5.15.2+dfsg-2
ii  libqt5widgets5 5.15.2+dfsg-2
ii  libstdc++6 10.2.1-6
ii  wsjtx-data 2.3.0+repack-1

Versions of packages wsjtx recommends:
ii  wsjtx-doc  2.3.0+repack-1

wsjtx suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: wsjtx
Source-Version: 2.3.0+repack-2
Done: Christoph Berg 

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated wsjtx 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: Tue, 09 Feb 2021 12:30:21 +0100
Source: wsjtx
Architecture: source
Version: 2.3.0+repack-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Closes: 982287
Changes:
 wsjtx (2.3.0+repack-2) unstable; urgency=medium
 .
   * Provide a debian/uupdate.sh script to extract the upstream tarball
 and use it in debian/watch.
   * Patch logging to require C.UTF-8 instead of en_US.UTF-8. (Closes: #982287)
   * Add dependency on libqt5sql5-sqlite.
Checksums-Sha1:
 cbe2baee85cfc37d854428c10083501f99537121 2424 wsjtx_2.3.0+repack-2.dsc
 caa7a5d65b81032b1dac2be58a2d655acdd0 16640 
wsjtx_2.3.0+repack-2.debian.tar.xz
Checksums-Sha256:
 ede3df8d0aae2ca704395bacfc3a7b1c0df9c98f3f1a0a896c2433161f1b3362 2424 
wsjtx_2.3.0+repack-2.dsc
 b9e01b56bd66d103136adc176a8111fa1d95120e60a6f9f87c7e148c735def79 16640 
wsjtx_2.3.0+repack-2.debian.tar.xz
Files:
 0fd48264da61080f747146512cece8af 2424 hamradio optional 
wsjtx_2.3.0+repack-2.dsc
 a1945b64fff3928eb0f6f9cdf1e982e2 16640 hamradio optional 
wsjtx_2.3.0+repack-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmAip1QACgkQTFprqxLS
p64RCA//QC159bpkLM04fVI7rT2BjgUmH0V5e1kChLnVKnXxvRafSm1b4n/kIikI
Pyhk7jqh7qPEqAdUXDoXNuElC8xi1j3XdoZLNFGkmQrbG8mPxKkD/NsaLzUpOmJU
DI/roqktePMWxRUYSt+xRsM3EzJFpka+ZbMHbhCE82Sdud9EMvF0bpoBHCfdr7SG
WZAe5wyQbAaBVsRWBaMy3Z+Je6YlbIXppQF40ZlXhiKDzyxbg6sL9J697sZbLLZH
UiU9pkXWJ8rLjopMWSPTTt+cqyTeb5XnuU5vNEmlWKCxsV8l89+dBo0WnBctw5IS
AVSTW4arYLwCAGQWa9SbOhq/ymvQ1ncst5NlrbhqxP8m81qcIFzdlcSzu7vUAEoy
MfcoDBEE9YsfFj0J0co3toluQ8OaHb7EkJL

Bug#981791: marked as done (wireshark: CVE-2021-22173 CVE-2021-22174)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 15:34:44 +
with message-id 
and subject line Bug#981791: fixed in wireshark 3.4.3-1
has caused the Debian Bug report #981791,
regarding wireshark: CVE-2021-22173 CVE-2021-22174
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.)


-- 
981791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wireshark
Version: 3.4.2-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for wireshark.

CVE-2021-22173[0]:
| USB HID dissector memory leak

CVE-2021-22174[1]:
| USB HID dissector could crash

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-22173
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22173
https://www.wireshark.org/security/wnpa-sec-2021-01.html
[1] https://security-tracker.debian.org/tracker/CVE-2021-22174
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22174
https://www.wireshark.org/security/wnpa-sec-2021-02.html

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: wireshark
Source-Version: 3.4.3-1
Done: Balint Reczey 

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

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated wireshark package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 29 Jan 2021 23:24:08 +0100
Source: wireshark
Architecture: source
Version: 3.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Balint Reczey 
Changed-By: Balint Reczey 
Closes: 981791
Changes:
 wireshark (3.4.3-1) unstable; urgency=medium
 .
   * New upstream version 3.4.3
 - security fixes (Closes: #981791):
   - USB HID dissector memory leak (CVE-2021-22173)
   - USB HID dissector crash (CVE-2021-22174)
Checksums-Sha1:
 d7a355304c062459ba5b46171132257af342660b 3509 wireshark_3.4.3-1.dsc
 ce54ca7e780c4610bd6a2e09fafe182d63c0cb79 32251372 wireshark_3.4.3.orig.tar.xz
 c65576098121439d599eadb861e10248df53ab81 74388 wireshark_3.4.3-1.debian.tar.xz
 64550876973eb63edf109e82bdf45201c3d54815 19449 
wireshark_3.4.3-1_source.buildinfo
Checksums-Sha256:
 73ab68929bf40d610a8c26d4ca36226baaac886f3b557b87dd258e92439009d5 3509 
wireshark_3.4.3-1.dsc
 abfd2779d736bec2f140a6d365ce75a8cb057f5efd1ac741d5e08b7a45f63460 32251372 
wireshark_3.4.3.orig.tar.xz
 b51d845fd96aa93024f7171aa659f6b07d6935fb1d4b8a147ee9bd163336e1e5 74388 
wireshark_3.4.3-1.debian.tar.xz
 efeeeb6121b13f420f1088c19e9ba564e105cda10cfda952eeb86c59e4b229ce 19449 
wireshark_3.4.3-1_source.buildinfo
Files:
 c3d4cb801a7979bc829c758abe871c80 3509 net optional wireshark_3.4.3-1.dsc
 3f9406a524af2cae7e1a6a5038ab2356 32251372 net optional 
wireshark_3.4.3.orig.tar.xz
 6e6af48f12d5e81a6bd5693ec333ef74 74388 net optional 
wireshark_3.4.3-1.debian.tar.xz
 70fb783bdab1173a67131f38698d356f 19449 net optional 
wireshark_3.4.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEI/PvTgXX55rLQUfDg6KBkWslS0UFAmAipw4ACgkQg6KBkWsl
S0XUMRAA0X2FsCSc5VvfmgAmpIGEHFmVgKEtaZkMRIyB4kn36FVgE+WJzCsyjj3Y
PuUaA/xgqROYKwXHfjBfZ6EJq3SLusGHf+DjPI5B5zWN5vmHxKuDcQSpjtVlxtnb
PQcRcUIWTdLloJNTXlkhQlk9XmsawBllZ7nhRXtzcMkfO2QPnSVP2wLhKnUpLeLf
ay+fEjd68AQzdKLJ6qlCPVcSZ6P8yk8En+IayIWcEW61MvembCJm73ddqxnzahpv
5FBIhd0Q4roVjTgc/OPatZH/RTeHWIOcRu0WsJFF4aX+8nLjEShgcLLnqvXEsosV
Ow9nQcci2s5QB33FKgJZdz1h/LedYDwP5Ijcic4q1PFH2jueonhLYDRI19p/p5UL
Hat9Q2StQCvGVNHa4FvBFwbJueXEHXfpodumHyfOPJmVVHpT9Ry/BiRKBW8zGEuk
T8xJrZRU154kobXckOQohUHfSvi5xF9A7ssS4QrFFRcMISUWyPkdwTO4QZxqtd/T
JKpD0NmKHxeZszN0Gzq3Kpr2op3HhSVZ/8U4tdBFdnhCgQOJR47nf3cCpsx13Zov
yCSV9YFgu1P+b4sNziK22GEHeIyaHO1uPmcaaKJ65jjnSBBwOtwb3m6UUh0km65C
D0mMkvuvhr2OSZphrUibgyG18SzDanTftJ9CYI3NHkOby75LF4g=
=6CKz
-END PGP SIGNATURE End Message ---

Bug#982205: marked as done (chromium: Update to version 88.0.4324.150 (security-fix))

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 15:04:15 +
with message-id 
and subject line Bug#982205: fixed in chromium 88.0.4324.150-1
has caused the Debian Bug report #982205,
regarding chromium: Update to version 88.0.4324.150 (security-fix)
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.)


-- 
982205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 88.0.4324.146-1
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

Chrome version 88.0.4324.150 contains CVE-2021-21148.
For details please see the link in [1].

Can you please provide a new version?

Thanks.

Regards,
- Sedat Dilek -

[1] 
https://chromereleases.googleblog.com/2021/02/stable-channel-update-for-desktop_4.html

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 
'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages chromium depends on:
ii  chromium-common  88.0.4324.146-1
ii  libasound2   1.2.4-1.1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libatomic1   10.2.1-6
ii  libatspi2.0-02.38.0-2
ii  libavcodec58 7:4.3.1-8
ii  libavformat587:4.3.1-8
ii  libavutil56  7:4.3.1-8
ii  libc62.31-9
ii  libcairo21.16.0-5
ii  libcups2 2.3.3op2-2
ii  libdbus-1-3  1.12.20-1
ii  libdrm2  2.4.104-1
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat12.2.10-1
ii  libflac8 1.3.3-2
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgbm1  20.3.4-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.6-1
ii  libgtk-3-0   3.24.24-1
ii  libharfbuzz0b2.7.4-1
ii  libicu67 67.1-6
ii  libjpeg62-turbo  1:2.0.5-2
ii  libjsoncpp24 1.9.4-4
ii  liblcms2-2   2.12~rc1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.60-1
ii  libopenjp2-7 2.4.0-1
ii  libopus0 1.3.1-0.1
ii  libpango-1.0-0   1.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpulse014.2-1
ii  libre2-9 20210201+dfsg-1
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.1-6
ii  libvpx6  1.9.0-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.7.0-2
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  libxrandr2   2:1.5.1-1
ii  libxslt1.1   1.1.34-4
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  88.0.4324.146-1

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n88.0.4324.146-1
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.31-9
ii  libstdc++6  10.2.1-6
ii  libx11-62:1.7.0-2
ii  libxext62:1.3.3-1.1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox88.0.4324.146-1
ii  fonts-liberation1:1.07.4-11
ii  gnome-shell [notification-daemon]   3.38.3-2
ii  libgl1-mesa-dri 20.3.4-1
ii  libu2f-udev 1.1.10-3
ii  notification-daemon 3.20.0-4
ii  plasma-workspace [notification-daemon]  4:5.20.5-3
ii  system-config-printer   1.5.14-1
ii  upower  0.99.11-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.31-9

-- Configuration Files:
/etc/chromium.d/default-flags changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: chromium
Source-Version: 88.0.4324.150-1
Done: Michel Le Bihan 

We believe that the bug you reported is fixed in the latest version of
chromium, which

Processed: your mail

[Debian Bug Tracking System]

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

> close 825339 2.4.0-2
Bug #825339 [libopenjp2-7-dev] Need public function to tell kernel type used 
(5x3 vs 9x7)
Ignoring request to alter fixed versions of bug #825339 to the same values 
previously set
Bug #825339 [libopenjp2-7-dev] Need public function to tell kernel type used 
(5x3 vs 9x7)
Marked Bug as done
>
End of message, stopping processing here.

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

Bug#973061: marked as done (nototools: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 14:51:05 +
with message-id 
and subject line Bug#973061: fixed in nototools 0.2.13-2
has caused the Debian Bug report #973061,
regarding nototools: FTBFS: dpkg-buildpackage: error: dpkg-source -b . 
subprocess returned exit status 2
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:217: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_nototools/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:217: python3.8 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.8_nototools/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
> rm -rf nototools.egg-info
> make[1]: Leaving directory '/<>'
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building nototools using existing 
> ./nototools_0.2.13.orig.tar.xz
> dpkg-source: info: local changes detected, the modified files are:
>  nototools-0.2.13/nototools/_version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/nototools_0.2.13-1.diff.EHwupO
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2020-10-27T12:29:37Z

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/nototools_0.2.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!

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: nototools
Source-Version: 0.2.13-2
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated nototools 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: Tue, 09 Feb 2021 09:29:39 -0500
Source: nototools
Architecture: source
Version: 0.2.13-2
Distribution: unstable
Urgency: high
Maintainer: Debian Fonts Task Force 
Changed-By: Boyuan Yang 
Closes: 973061
Changes:
 nototools (0.2.13-2) unstable; urgency=high
 .
   * Team upload.
   * Bump Standards-Version to 4.5.1.
   * Bump debhelper compat to v13.
   * debian/rules: Use dh13 syntax.
   * debian/rules: Remove modified nototools/_version.py to avoid
 FTBFS. (Closes: #973061)
Checksums-Sha1:
 99966161a87e77e28c9fca7149cc88590bd01c8c 2123 nototools_0.2.13-2.dsc
 ddc92fa056cbe2c72b3465ce2569e834dfb276fd 1100324 nototools_0.2.13.orig.tar.xz
 ce5d1fe44ecf0cf71fcf9c6d8641a442cb8283b0 3320 nototools_0.2.13-2.debian.tar.xz
 7b4a23d1ba5b31abb3dfb3ec6c257c30d3ff26bc 6853 
nototools_0.2.13-2_amd64.buildinfo
Checksums-Sha256:
 6ead0f1ab8149e549caa7f736f4df7cf1c4d4af4ebb0455d81fd302a733ccc7e 2123 
nototools_0.2.13-2.dsc
 d2ac7d03321d1a5b8232a9eb291bab3466b0156f2f39b45c2ff587c299c6eca2 1100324 
nototools_0.2.13.orig.tar.xz
 ec348474e95084d828688a1bf7dab17b0d9ab680e3bbbc0e9f027fed92651232 3320 
nototools_0.2

Bug#950474: marked as done (python-cogent FTBFS on armel and i386: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 14:34:38 +
with message-id 
and subject line Bug#950474: fixed in python-cogent 2020.12.21a+dfsg-4
has caused the Debian Bug report #950474,
regarding python-cogent FTBFS on armel and i386: test failures
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.)


-- 
950474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cogent
Version: 2019.12.6a+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=python-cogent&arch=armel&ver=2019.12.6a%2Bdfsg-1&stamp=1579377813&raw=0

...
==
FAIL: test_col_uncertainty (tests.test_maths.test_util.ArrayMathTests)
column_uncertainty: should handle pos/neg/zero/empty arrays
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.8_cogent3/build/tests/test_maths/test_util.py",
 line 137, in test_col_uncertainty
column_uncertainty(array([[-2]]))
AssertionError: FloatingPointError not raised
...


https://buildd.debian.org/status/fetch.php?pkg=python-cogent&arch=i386&ver=2019.12.6a%2Bdfsg-1&stamp=1579375248&raw=0

...
==
FAIL: test_jsm (tests.test_maths.test_measure.TestJensenShannon)
case1 is testing if the jsm between two identical distributions is 0.0
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.8_cogent3/build/tests/test_maths/test_measure.py",
 line 242, in test_jsm
assert_allclose(
  File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 
1514, in assert_allclose
assert_array_compare(compare, actual, desired, err_msg=str(err_msg),
  File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 
841, in assert_array_compare
raise AssertionError(msg)
AssertionError: 
Not equal to tolerance rtol=1e-07, atol=0
Testing case4 for jsm failed
Mismatch: 100%
Max absolute difference: 2.10734243e-08
Max relative difference: inf
 x: array(2.107342e-08)
 y: array(0.)
...


The armel port has no FPU in the baseline,
and the math emulation does not handle all corner cases correctly.

The i386 port uses the 387 FPU that has excess precision.

Since this package likely has no users on armel or i386,
I'd suggest to file an RM bug for the old binaries and
then lower the severity of this bug.
--- End Message ---
--- Begin Message ---
Source: python-cogent
Source-Version: 2020.12.21a+dfsg-4
Done: Michael R. Crusoe 

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated python-cogent 
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: Tue, 09 Feb 2021 14:42:13 +0100
Source: python-cogent
Architecture: source
Version: 2020.12.21a+dfsg-4
Distribution: unstable
Urgency: high
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 950474
Changes:
 python-cogent (2020.12.21a+dfsg-4) unstable; urgency=high
 .
   * Team upload.
   * debian/rules: Don't build docs package on armel/mipsel
 Closes: #950474
   * Skip tests on s390x, mips64el, mipsel, and armel
Checksums-Sha1:
 c3db74a7aabf04a938b89d6979b98a01a95f754e 2584 
python-cogent_2020.12.21a+dfsg-4.dsc
 1d2c6784d831c36ce5c20150031207f56dc1fd0e 11636 
python-cogent_2020.12.21a+dfsg-4.debian.tar.xz
 819ef6485f9c77c49a5636cccfe795d38bbc41c2 8794 
python-cogent_2020.12.21a+dfsg-4_source.buildinfo
Checksums-Sha256:
 ad8cb3431c50579562e156485beb1982f13a085096f3cb706d5ab2af44603da8 2584 
python-cogent_2020.12.21a+dfsg-4.dsc
 9510b671289f1328048e275e33f2d2ddfb4281f23ab63c9f95f0b9cc837c687a 11636 
python-cogent_2020.12.21a+dfsg-4.debian.tar.xz
 7e972090c1f1a86aa7e4071c5f50b65127d8f663df298c24691ef7394632eef0 8794 
python-cogent_2020.12.21a+dfsg-4_source.buildinfo

Bug#978388: marked as done (malcontent: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 14:33:37 +
with message-id 
and subject line Bug#978388: fixed in malcontent 0.10.0-2
has caused the Debian Bug report #978388,
regarding malcontent: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- -Dprivileged_group=sudo 
> -Dpamlibdir=/lib/x86_64-linux-gnu/security -Dui=enabled
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dprivileged_group=sudo 
> -Dpamlibdir=/lib/x86_64-linux-gnu/security -Dui=enabled
> The Meson build system
> Version: 0.56.0
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: malcontent
> Project version: 0.10.0
> Using 'CFLAGS' from environment with value: '-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security'
> Using 'LDFLAGS' from environment with value: '-Wl,-z,relro'
> Using 'CPPFLAGS' from environment with value: '-Wdate-time 
> -D_FORTIFY_SOURCE=2'
> C compiler for the host machine: cc (gcc 10.2.1 "cc (Debian 10.2.1-3) 10.2.1 
> 20201224")
> C linker for the host machine: cc ld.bfd 2.35.1
> Using 'CFLAGS' from environment with value: '-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security'
> Using 'LDFLAGS' from environment with value: '-Wl,-z,relro'
> Using 'CPPFLAGS' from environment with value: '-Wdate-time 
> -D_FORTIFY_SOURCE=2'
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency dbus-1 found: YES 1.12.20
> Run-time dependency polkit-gobject-1 found: YES 0.105
> Configuring config.h using configuration
> Compiler for C supports arguments -fno-strict-aliasing: YES 
> Compiler for C supports arguments -fstack-protector-strong: YES 
> Compiler for C supports arguments -Waggregate-return: YES 
> Compiler for C supports arguments -Wall: YES 
> Compiler for C supports arguments -Wunused: YES 
> Compiler for C supports arguments -Warray-bounds: YES 
> Compiler for C supports arguments -Wcast-align: YES 
> Compiler for C supports arguments -Wclobbered: YES 
> Compiler for C supports arguments -Wno-declaration-after-statement: YES 
> Compiler for C supports arguments -Wdiscarded-qualifiers: YES 
> Compiler for C supports arguments -Wduplicated-branches: YES 
> Compiler for C supports arguments -Wduplicated-cond: YES 
> Compiler for C supports arguments -Wempty-body: YES 
> Compiler for C supports arguments -Wformat=2: YES 
> Compiler for C supports arguments -Wformat-nonliteral: YES 
> Compiler for C supports arguments -Wformat-security: YES 
> Compiler for C supports arguments -Wformat-signedness: YES 
> Compiler for C supports arguments -Wignored-qualifiers: YES 
> Compiler for C supports arguments -Wimplicit-function-declaration: YES 
> Compiler for C supports arguments -Wincompatible-pointer-types: YES 
> Compiler for C supports arguments 
> -Wincompatible-pointer-types-discards-qualifiers: NO 
> Compiler for C supports arguments -Winit-self: YES 
> Compiler for C supports arguments -Wint-conversion: YES 
> Compiler for C supports arguments -Wlogical-op: YES 
> Compiler for C supports arguments -Wmisleading-indentation: YES 
> Compiler for C supports arguments -Wmissing-declarations: YES 
> Compiler for C supports arguments -Wmissing-format-attribute: YES 
> Compiler for C supports arguments -Wmissing-include-dirs: YES 
> Compiler for C supports arguments -Wmissing-noreturn: YES 
> Compiler for C supports arguments -Wmissing-parameter-type: YES 
> Compiler for C supports arguments -Wmissing-prototypes: YES 
> Compiler for C supports arguments -Wnested-externs: YES 
> Compiler for C supports arguments -Wno-error=cpp: YES 
> Compiler for C supports arguments -Wmissing-field-initializers: YES 
> Compiler for C supports arguments -Wno-suggest-attribute=format: YES 
> Compiler for C supports arguments -Wno-unused-parameter: YES 
> Compi

Processed: closing 922224

[Debian Bug Tracking System]

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

> close 94
Bug #94 [atop] atop interferes with package acct's logging
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#981331: marked as done (mirrors: [20210129] ftp.ntou.edu.tw: sync-frequency)

[Debian Bug Tracking System]

Your message dated Tue, 9 Feb 2021 14:31:36 +0100
with message-id 
and subject line Re: Bug#981331: mirrors: [20210129] ftp.ntou.edu.tw: 
sync-frequency
has caused the Debian Bug report #981331,
regarding mirrors: [20210129] ftp.ntou.edu.tw: sync-frequency
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.)


-- 
981331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mirrors
Severity: normal
X-Debbugs-Cc: m...@lxde.org
User: mirr...@packages.debian.org
Usertags: mirror-problem

Hi,

I was checking some things in the Debian mirror universe and noticed
a problem with your mirror:

o It seems your mirror is not up to date, having last updated on Thu, 28 Jan 
2021 19:36:23 +
o The latest ftpsync versions come with a wrapper script called
  ftpsync-cron, which is intended to be run out of cron every hour or so
  (at a randomish offset).  The script monitors your upstream mirror,
  and if there was an update triggers a full sync using ftpsync.
  You might want to give it a try.

  NOTE: This requires having your upstream mirror name set correctly to
  a specific mirror which is also correctly configured (and thus has a
  tracefile in /debian/project/trace with its name).

Note that the debian archive updates every 6 hours, we expect mirrors
listed in our mirror list to follow that rhythm.

Cheers,
Julien
--- End Message ---
--- Begin Message ---
Closing, thanks.

Cheers,
Julien

On Fri, Jan 29, 2021 at 09:15:23PM +0800, Yao Wei wrote:
> Package: mirrors
> Followup-For: Bug #981331
> 
> I updated ftpsync and it should now be using ftpsync-cron.
> 
> Previously the sync frequency was once per day just in case that push
> mirroring doesn't work as intended, without realizing that the push is
> not triggered for a long while.  I am going to adjust the frequency to 3
> times per day.
> 
> Let's see whether it is working, and if it is okay, please close this
> ticket on your own.--- End Message ---

Processed: bts

[Debian Bug Tracking System]

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

> close 982200
Bug #982200 [wnpp] ITP: athenacli -- CLI client for AWS Athena
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#921047: marked as done (create read-only user for mariadb-server)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 13:18:46 +
with message-id 
and subject line Bug#921047: fixed in netdata 1.29.0-3
has caused the Debian Bug report #921047,
regarding create read-only user for mariadb-server
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.)


-- 
921047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: netdata
Version: 1.11.1+dfsg-5
Severity: normal

Out of the box, the mysql plugin does not work on debian.

The /usr/lib/netdata/conf.d/python.d/mysql.conf debiancfg entry requires
/etc/mysql/debian.cnf to be readable by user or group netdata, and the
error log does not indicate this is the case, it silently fails.

Preferably, though, there should be a post-install script which installs a
mysql netdata user using debian-sys-maint credentials and which has limited
permissions.

This would be safer, as giving netdata debian-sys-maint privs to mysql is
probably a bad idea.

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

Kernel: Linux 4.18.16-x86_64-linode118 (SMP w/4 CPU cores; PREEMPT)
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/dash
Init: systemd (via /run/systemd/system)

Versions of packages netdata depends on:
ii  netdata-core  1.11.1+dfsg-5
ii  netdata-plugins-bash  1.11.1+dfsg-5
ii  netdata-web   1.11.1+dfsg-5

Versions of packages netdata recommends:
ii  netdata-plugins-nodejs  1.11.1+dfsg-5
ii  netdata-plugins-python  1.11.1+dfsg-5

netdata suggests no packages.

-- debconf information:
  netdata/title:
  netdata/send_email: YES
--- End Message ---
--- Begin Message ---
Source: netdata
Source-Version: 1.29.0-3
Done: Daniel Baumann 

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

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated netdata 
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: Tue, 09 Feb 2021 13:53:18 +0100
Source: netdata
Architecture: source
Version: 1.29.0-3
Distribution: unstable
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 921047
Changes:
 netdata (1.29.0-3) unstable; urgency=medium
 .
   * Updating TODO file.
   * Explicitly disabling netdata cloud support as it requires some weird
 special/forked/patched libraries.
   * Moving myself to maintainer, thanks Lennart.
   * Adding README.Debian for netdata, explaining mysql/mariadb tplugin things
 (Closes: #921047).
Checksums-Sha1:
 a437bcede9455b59b42eedefaef80f7f6f6a12a4 2551 netdata_1.29.0-3.dsc
 fca9f177086900875c8ec4a33ed45c51be9a3845 670472 netdata_1.29.0-3.debian.tar.xz
 ea0fa496dc20b6c09009f65e1a4806e3eac2ba60 9333 netdata_1.29.0-3_amd64.buildinfo
Checksums-Sha256:
 e5b1dee52c8cf189ad6d453cff217cb014a6a4d25a4b701df4ae070752bbb119 2551 
netdata_1.29.0-3.dsc
 17ed37b3a3d91791271a053fd5ab0db5e762b0f28d0f5c250e4ef0047a4018b8 670472 
netdata_1.29.0-3.debian.tar.xz
 a7b317657615cd7fd1cb40b3fe4b388dc948f7bb4ec37d60c988b5636e3cda72 9333 
netdata_1.29.0-3_amd64.buildinfo
Files:
 9e93efa0bb4b8dcaff1c0114b4c79ae0 2551 net optional netdata_1.29.0-3.dsc
 2812d550e11bfd57219696779489cfef 670472 net optional 
netdata_1.29.0-3.debian.tar.xz
 5e54c14b1d9e2d8a398a9bdd196d2b1d 9333 net optional 
netdata_1.29.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmAihtAACgkQVc8b+Yar
uccr7RAAyYdMpy6ucBayn2/io2RUBzUqa2L2N6J4GyV49pgqKAcpHxEvgLtaiLyX
U8/qeTAS4gSrMrOuQXiofrgUDEcgIBPB3OAA95eduWJG+mXGWVPxKfQmqlAGtJ+e
CIVu9q6s5FIhKafVaM8HvQVrV7h5gsXDtq8z2i7M0HWz/kyQoklj6e3HpMTIzY6j
Yv4Mjb8pXR67tHXwrsn4I7IYOG4O0ly8+T6uTI2B9vhitquEqYUEvP+N3d0irz1V
ybKgDj71S1o/54SWflnCviEVtx4+mhPs271ZVIYf0w7QEt/Shngv4S+fyUT5FpLY
k8WSqS4EB/p45xzw9iDbYJ3R6uwcYNik1gejLOh6nsX6mvJPsjwmUg9vLsUybfZu
haCpijE1FA+wb82s4NUUi9gpfd1waBC6sBTBHk9/ZSQWEqJHRoKd5QmIxFqGCOSK
NEwHCS/2Rw

Processed: Re: conf.d in /etc skipped

[Debian Bug Tracking System]

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

> close 930506 1.29.0-1
Bug #930506 [netdata] conf.d in /etc skipped
Marked as fixed in versions netdata/1.29.0-1.
Bug #930506 [netdata] conf.d in /etc skipped
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#981771: marked as done (ndpi FTBFS on i386: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 12:18:56 +
with message-id 
and subject line Bug#981771: fixed in ndpi 3.4-3
has caused the Debian Bug report #981771,
regarding ndpi FTBFS on i386: test failures
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.)


-- 
981771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ndpi
Version: 3.4-1
Severity: important
Tags: patch ftbfs

https://buildd.debian.org/status/fetch.php?pkg=ndpi&arch=i386&ver=3.4-2&stamp=1610990009&raw=0

...
zoom.pcap   ERROR
../example/ndpiReader -p ../example/protos.txt -c ../example/categories.txt -q 
-t -i pcap/zoom.pcap -w /tmp/reader.out -v 2 [old vs new]
31c31
<   13  TCP 192.168.1.117:53867 <-> 104.199.65.42:80 [proto: 
7.126/HTTP.Google][cat: Web/5][4 pkts/710 bytes <-> 2 pkts/242 bytes][Goodput 
ratio: 63/45][0.09 sec][bytes ratio: 0.492 (Upload)][IAT c2s/s2c 
min/avg/max/stddev: 30/64 31/64 32/64 1/0][Pkt Len c2s/s2c min/avg/max/stddev: 
66/121 178/121 329/121 115/0][Plen Bins: 
0,50,0,0,0,25,0,0,25,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
---
>   13  TCP 192.168.1.117:53867 <-> 104.199.65.42:80 [proto: 
> 7.126/HTTP.Google][cat: Web/5][4 pkts/710 bytes <-> 2 pkts/242 bytes][Goodput 
> ratio: 63/45][0.10 sec][bytes ratio: 0.492 (Upload)][IAT c2s/s2c 
> min/avg/max/stddev: 30/64 31/64 32/64 1/0][Pkt Len c2s/s2c 
> min/avg/max/stddev: 66/121 178/121 329/121 115/0][Plen Bins: 
> 0,50,0,0,0,25,0,0,25,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
make[1]: *** [debian/rules:29: override_dh_auto_test] Error 1



If exact results are required, the following patch mitigates
the x87 excess precision:

--- debian/rules.old2021-02-01 06:50:37.795280557 +
+++ debian/rules2021-02-01 06:51:08.671237643 +
@@ -5,6 +5,10 @@
 include /usr/share/dpkg/buildflags.mk
 include /usr/share/dpkg/pkg-info.mk
 
+ifneq (,$(filter $(DEB_HOST_ARCH), i386))
+export DEB_CFLAGS_MAINT_APPEND += -ffloat-store
+endif
+
 # Used by debian/libndpi-wireshark.{install,links}. Evaluated when referenced.
 WIRESHARK_PLUGINDIR = $(shell pkg-config --variable=plugindir wireshark)
 export WIRESHARK_PLUGINDIR
--- End Message ---
--- Begin Message ---
Source: ndpi
Source-Version: 3.4-3
Done: Raphaël Hertzog 

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated ndpi 
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: Tue, 09 Feb 2021 12:14:08 +0100
Source: ndpi
Architecture: source
Version: 3.4-3
Distribution: unstable
Urgency: high
Maintainer: Ludovico Cavedon 
Changed-By: Raphaël Hertzog 
Closes: 981771
Changes:
 ndpi (3.4-3) unstable; urgency=high
 .
   * Team upload.
   * Fix i386 build by changing the precision of the calculations.
 Thanks to Adrian Bunk  (Closes: #981771)
Checksums-Sha1:
 cac385599302193cb26a65f7edadb5476ca57ce4 1780 ndpi_3.4-3.dsc
 05c7c74c39493368acdf4f6cebf562c675dd094d 14068 ndpi_3.4-3.debian.tar.xz
 48241f0f9b6573840ecd83aee10f930b2dd95666 5939 ndpi_3.4-3_source.buildinfo
Checksums-Sha256:
 35a326b638be35353234e08af6a83b441ca5a9e9faebf7b0b5a08216a4af04e5 1780 
ndpi_3.4-3.dsc
 b194170806c1fd89077b228c9a04a8637758b816a1b56f8fa61fb42cfb3eff9f 14068 
ndpi_3.4-3.debian.tar.xz
 fe80864f5255d21eb627f2817b9ed136bbeb24ce9aff5ec63f063d011fe33cde 5939 
ndpi_3.4-3_source.buildinfo
Files:
 7aee4c2e817668ad5e37263b1c5adab6 1780 libs optional ndpi_3.4-3.dsc
 8277920b59627832b7e3e697d8e066f8 14068 libs optional ndpi_3.4-3.debian.tar.xz
 d2a92bcc6edcb21a57ddecc4f53328f6 5939 libs optional ndpi_3.4-3_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAmAierUACgkQA4gdq+vC
mrlwawf+McZ0jyHUptVcCbagEFnZg/YzLHyk2SKz9XKOL5UwqH2uq1RnUVQ0yFdq
3Omo1WPQdZA6lnykAx0g34iPkESTAn4MbcyNZO041VKGKfVdWRU5Se/HJ86te+oC
btyuYq41QqkQoyyGIt8iP0+DFdPZs7b/

Bug#951550: marked as done (procps: document /usr/lib/sysctl.d/)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 11:03:51 +
with message-id 
and subject line Bug#951550: fixed in procps 2:3.3.17-1
has caused the Debian Bug report #951550,
regarding procps: document /usr/lib/sysctl.d/
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.)


-- 
951550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: procps
Version: 2:3.3.16-1+b1
Severity: normal


Hi.

It seems that /usr/lib/sysctl.d/ is docuemnted nowhere, or did I miss that?

I think it should be mentioned in:
- the manpage
- /etc/sysctl.conf
- /etc/sysctl.d/README.sysctl

Maybe also with information in which order these files are parsed.

Thanks,
Chris.
--- End Message ---
--- Begin Message ---
Source: procps
Source-Version: 2:3.3.17-1
Done: Craig Small 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 09 Feb 2021 21:50:10 +1100
Source: procps
Architecture: source
Version: 2:3.3.17-1
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Closes: 950788 951335 951550
Changes:
 procps (2:3.3.17-1) unstable; urgency=medium
 .
   * New upstream source
 - sysctl: Match systemd directory order Closes: #950788
 - sysctl: Document directory order Closes: #951550
 - top: ensure config file backward compatibility Closes: #951335
Checksums-Sha1:
 efdf89f894a8007630b4cf23cf692a5aa89e2d09 2130 procps_3.3.17-1.dsc
 a52952e8bc6aaab812176c00d25adc4d4e1552e2 1008428 procps_3.3.17.orig.tar.xz
 c169f4476fb8f5a851bc2ac3c0419fcf0c83b036 28680 procps_3.3.17-1.debian.tar.xz
 62347cea3917a1afb2b0254a6fd7f142f0aabf2d 7302 procps_3.3.17-1_amd64.buildinfo
Checksums-Sha256:
 59bec91b0e9266a76ffa45d8a68d15f65cf9b244ab24235c0bfcd7415c57b1fe 2130 
procps_3.3.17-1.dsc
 4518b3e7aafd34ec07d0063d250fd474999b20b200218c3ae56f5d2113f141b4 1008428 
procps_3.3.17.orig.tar.xz
 040c2460ead45593467b3c128d2390f1f6483181583fb25c49f6ed76b8aa26f2 28680 
procps_3.3.17-1.debian.tar.xz
 d9581892667063fcfd4d0f9f4dc536ec59925625c619ea1bb91dd20a42b8fefb 7302 
procps_3.3.17-1_amd64.buildinfo
Files:
 832ca3dcf8173f27f1634a37c067568f 2130 admin optional procps_3.3.17-1.dsc
 d60613e88c2f442ebd462b5a75313d56 1008428 admin optional 
procps_3.3.17.orig.tar.xz
 d856954900821452dc64a054b147d165 28680 admin optional 
procps_3.3.17-1.debian.tar.xz
 b9f8c70d43510a742f547a8daea4a39b 7302 admin optional 
procps_3.3.17-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAmAiaV4ACgkQAiFmwP88
hOP+Ig//dJff/53JrY4LxiyICLKPQiDfkJoZbBg8FtPnolhRQpKk/gW1mmc84imH
RIN4jPXR8z539dz0BQr9GPav60eIsTwDtxWu4ZJC4hGCYMoIy1fgoQBPGOMbjrpx
4GVh0rtturTLctOgxmlfOzqoUL5k5/5gCcs0rRfXu8WQx5qJq2uAsveNxXnHFQiy
yPUkZTzuMsyShGYb62IKyBo95tCX9TF79Dq1dewziiiXVrT7Osc/WvBID2Ze98DQ
e54Jqgbe/tRxDOCyMOd4HYI8m97rmn5oZ8+w6XrN5SDIZ0y2m6ongxsn2v8QLS7W
y1Zi1iiZvCkXR+OL5tjfVmqM0XALiyN/rB3ayu073qHQGqpTqVtxDk1SS1x93NRF
gQCxWm/rOcVfS7SPVs734S6Aqmz6nynHfiuKYDhEl0NhluNf1lMyRus8XGem5LbB
1AGbVJEb/3aFWHx8EUTgPuGH8HMsmxU4W5fkQKcNlxBpyb5RGEbRID43p5wDBDad
CGMTy5riSYmV7C+ecVwpYIE7U7zaPx8YEQkIuJLtfsVoAvywy9QPQRaq/mQH7KvK
zQ4d3Xku9PtR1dkyvUzxZ6YwkZDk6VpUNHh1Ix+39+aJjZZQdRyPxZll3+kYfwNF
WUXaFIb7u8E6Fs9o7tFQpykAqxlcxxdvCxsK1SNo1X73tjsXcwE=
=eUDR
-END PGP SIGNATURE End Message ---

Bug#950788: marked as done (/usr/share/man/man5/sysctl.d.5.gz: sysctl.d.5 man page has confusing directory order)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 11:03:51 +
with message-id 
and subject line Bug#950788: fixed in procps 2:3.3.17-1
has caused the Debian Bug report #950788,
regarding /usr/share/man/man5/sysctl.d.5.gz: sysctl.d.5 man page has confusing 
directory order
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.)


-- 
950788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 244-3
Severity: minor
File: /usr/share/man/man5/sysctl.d.5.gz

The sysctl.d.5 man page says this:

  Configuration files are read from directories in /etc/, /run/, 
/usr/local/lib/, and /lib/, in order of precedence. Each configuration file in 
these configuration directories shall be named in the
  style of filename.conf. Files in /etc/ override files with the same name 
in /run/, /usr/local/lib/, and /lib/. Files in /run/ override files with the 
same name under /usr/.

OK, so we have 4 directories.
Anything in /etc overrides anything in the other 3.

But files in /run? They override.. /usr?
Is this supposed to mean /usr/local/lib?
Does that mean /run does NOT override files in /lib ?

I think the man page used to say /usr/local/lib and /usr/lib and it was
(badly) saying both directories under /usr

Maybe.. I'm not really sure what way to interpret this.

 - Craig

-- Package-specific info:

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-5
ii  libapparmor1 2.13.3-7
ii  libaudit11:2.8.5-2+b1
ii  libblkid12.34-0.1
ii  libc62.29-6
ii  libcap2  1:2.27-1
ii  libcryptsetup12  2:2.2.2-1
ii  libgcrypt20  1.8.5-3
ii  libgnutls30  3.6.11.1-2
ii  libgpg-error01.36-7
ii  libidn2-02.2.0-2
ii  libip4tc21.8.4-1
ii  libkmod2 26-3
ii  liblz4-1 1.9.2-2
ii  liblzma5 5.2.4-1+b1
ii  libmount12.34-0.1
ii  libpam0g 1.3.1-5
ii  libpcre2-8-0 10.34-7
ii  libseccomp2  2.4.2-2
ii  libselinux1  3.0-1
ii  libsystemd0  244-3
ii  mount2.34-0.1
ii  util-linux   2.34-0.1

Versions of packages systemd recommends:
ii  dbus  1.12.16-2

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

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.135
ii  udev 244-3

-- Configuration Files:
/etc/systemd/logind.conf changed [not included]

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

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 09 Feb 2021 21:50:10 +1100
Source: procps
Architecture: source
Version: 2:3.3.17-1
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Closes: 950788 951335 951550
Changes:
 procps (2:3.3.17-1) unstable; urgency=medium
 .
   * New upstream source
 - sysctl: Match systemd directory order Closes: #950788
 - sysctl: Document directory order Closes: #951550
 - top: ensure config file backward compatibility Closes: #951335
Checksums-Sha1:
 efdf89f894a8007630b4cf23cf692a5aa89e2d09 2130 procps_3.3.17-1.dsc
 a52952e8bc6aaab812176c00d25adc4d4e1552e2 1008428 procps_3.3.17.orig.tar.xz
 c169f4476fb8f5a851bc2ac3c0419fcf0c83b036 28680 procps_3.3.17-1.debian.tar.xz
 62347cea3917a1afb2b0254a6fd7f142f0aabf2d 73

Bug#981885: marked as done (apt: [INTL:nl] Dutch po file for the apt package)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 10:48:25 +
with message-id 
and subject line Bug#981885: fixed in apt 2.1.19
has caused the Debian Bug report #981885,
regarding apt: [INTL:nl] Dutch po file for the apt package
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.)


-- 
981885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
 
 
Package: apt 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch po file for the apt package. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as "po/nl.po" in your package build tree. 
 

-- 
Met vriendelijke groet,
Frans Spiesschaert



nl.po.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: apt
Source-Version: 2.1.19
Done: Julian Andres Klode 

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

Debian distribution maintenance software
pp.
Julian Andres Klode  (supplier of updated apt 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: Tue, 09 Feb 2021 10:41:53 +0100
Source: apt
Architecture: source
Version: 2.1.19
Distribution: unstable
Urgency: medium
Maintainer: APT Development Team 
Changed-By: Julian Andres Klode 
Closes: 979848 981883 981885
Changes:
 apt (2.1.19) unstable; urgency=medium
 .
   [ Helge Kreutzmann ]
   * German program translation update (Closes: #979848)
 .
   [ Youfu Zhang ]
   * dpkg: fix passing readonly /dev/null fd as stdout/stderr
 .
   [ Diederik de Haas ]
   * Fix apt-acquire-additional-files entity's location.
 .
   [ Wolfgang Schweer ]
   * vendor: Adjust Debian -security codename
 .
   [ Julian Andres Klode ]
   * Include all translations when building the cache (LP: #1907850)
 .
   [ David Kalnischkies ]
   * Various patches uplifted from unfinished fuzzer branches
 - Use 500 MB memory limit for xz/lzma decoding
 - Guess compressor only if no AR nember with exact name exists
 - Free XXH3 state to avoid leak in cache hashing
 - Fail ConfigDir reading if directory listing failed
 - Retire and deprecate _strtabexpand
 - Fix incorrect base64 encoding due to int promotion
 - Don't parse \x and \0 past the end in DeEscapeString
 - Remove Word size limit from ParseQuote and CWord
 - Forbid negative values in unsigned StrToNum explicitly
 - Avoid overstepping bounds in config file parsing
 - Show 'Done' always for 'Building dependency tree'
 - Avoid undefined pointer arithmetic while growing mmap
 - Use error reporting instead of assert in rred patching
 - Replace PrintStatus with SendMessage usage
 - Ensure HTTP status code text has sensible content
 - Limit on first patch size only for server-merged patches
 - Use size of the old cache as APT::Cache-Start default
 - Remove spurious periods on progress strings in po/de.po
 .
   [ Frans Spiesschaert ]
   * Dutch program translation update (Closes: #981885)
   * Dutch manpages translation update (Closes: #981883)
Checksums-Sha1:
 0439520ecd0bc26c8b304e38240cb90b9c10f94e 2784 apt_2.1.19.dsc
 308b29cff37efeb1b6e15106854913dc1028fe84 2194760 apt_2.1.19.tar.xz
 cbfef8f62a970e802ee49d91379f19530c411016 7494 apt_2.1.19_source.buildinfo
Checksums-Sha256:
 688e02c69354bc9cf660c099d3e2d8a578239de1956aaec757159d6ed0043aa9 2784 
apt_2.1.19.dsc
 eb796de8343d0b0a61815a39716256504717cd1e56213e076e2b39dd49d65378 2194760 
apt_2.1.19.tar.xz
 641739248b88445cdded63047bafd267f0d940243e9ce9f52df303edfb8e61f0 7494 
apt_2.1.19_source.buildinfo
Files:
 9d8fba59cec356796ace5e6c5f44d1a1 2784 admin important apt_2.1.19.dsc
 ce15450f7b7a212f9d781bab09c2ea22 2194760 admin important apt_2.1.19.tar.xz
 2ea9c8f98de2fe6c8fea525cf5ca47a6 7494 admin important 
apt_2.1.19_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEET7WIqEwt3nmnTHeHb6RY3R2wP3EFAmAiWfsPHGpha0BkZWJp
YW4ub3JnAAoJEG+kWN0dsD9xqBEP/RUU0Etc/m3ilhTpM/+yVy91NZneb9PIRjZx
8RFl2a

Bug#969606: marked as done (bilibop: lockfs autopkgtest is not portable, consistently fails in Ubuntu)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 10:18:17 +
with message-id 
and subject line Bug#969606: fixed in bilibop 0.6.3
has caused the Debian Bug report #969606,
regarding bilibop: lockfs autopkgtest is not portable, consistently fails in 
Ubuntu
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.)


-- 
969606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bilibop
Version: 0.6.1
Severity: important
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy

Hi Yann,

In your latest upload, you introduced a 'lockfs' autopkgtest.  This test is
skipped on Debian autopkgtest infrastructure because it has an
'isolation-machine' restriction.  But in Ubuntu, the test is run, and
fails on all architectures:

[...]
# df --output=source,fstype,target
Filesystem Type Mounted on
udev   devtmpfs /dev
tmpfs  tmpfs/run
tmpfs  tmpfs/aufs/rw
/dev/vda1  ext4 /aufs/ro
aufs   aufs /
tmpfs  tmpfs/dev/shm
tmpfs  tmpfs/run/lock
tmpfs  tmpfs/sys/fs/cgroup
tmpfs  tmpfs/aufs/rw/boot/efi
/dev/vda15 vfat /aufs/ro/boot/efi
aufs   aufs /boot/efi
tmpfs  tmpfs/run/user/1000

STAGE 1: unexpected error
autopkgtest [08:43:15]: test lockfs: ---]
autopkgtest [08:43:16]: test lockfs:  - - - - - - - - - - results - - - - - - - 
- - -
lockfs   FAIL non-zero exit status 91
[...]

(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/b/bilibop/20200501_084325_e3c5c@/log.gz)

I have not attempted to debug this; but it seems the test is not
particularly useful at present, since it is not run in Debian and fails in
Ubuntu.

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: bilibop
Source-Version: 0.6.3
Done: Yann Amar 

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

Debian distribution maintenance software
pp.
Yann Amar  (supplier of updated bilibop 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: Tue,  9 Feb 2021 11:02:05 CET
Source: bilibop
Binary: 
Architecture: source
Version: 0.6.3
Distribution: unstable
Urgency: high
Maintainer: Yann Amar 
Changed-By: Yann Amar 
Description: 
Closes: 955504 956344 958870 962411 969606
Changes:
 bilibop (0.6.3) unstable; urgency=high
 .
   * Fix missing support for aufs in autopkgtest test (lockfs).
 Closes: #969606
 .
   * Move executable files from /usr/lib/bilibop to /usr/libexec/bilibop
 according to FHS 3.0, Debian Policy and lintian (pedantic).
 .
   * Update translations for debconf
 - nl: thanks to Frans Spiesschaert. Closes: #955504
 - de: thanks to Chris Leick. Closes: #956344
 - es: thanks to Camaleón. Closes: #958870
 - pt: thanks to Américo Monteiro. Closes: #962411
 .
   * debian/control:
 - Bump debhelper-compat version to 13.
 - Bump Standards-Version to 4.5.1: no changes needed.
   * debian/substvars: move to debian/description to avoid lintian warning
 (source-contains-debian-substvars).
   * debian/rules: update dh_gencontrol override accordingly (+fix syntax).
   * debian/copyright: update GPL license URL to https.
Checksums-Sha256: 
 bde24635c171c79e74723e4080c2f841647d204fd77617c468b389e4687b4479 1819 
bilibop_0.6.3.dsc
 33a24672c6d896a47f14d9a47e2b8688e1655c8d358b838b9d8351cc58de3640 128400 
bilibop_0.6.3.tar.xz
 740b612eb1ff6a66fd60386be30b2327dd0e34873185888e052ad1f12b7bf918 7094 
bilibop_0.6.3_sourceonly.buildinfo
Checksums-Sha1: 
 6a69668dc442e9008a223bcdbb24acc905ea48f3 1819 bilibop_0.6.3.dsc
 fd9f19858a5b8

Bug#962411: marked as done (bilibop: [INTL:pt] Updated Portuguese translation - debconf messages)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 10:18:17 +
with message-id 
and subject line Bug#962411: fixed in bilibop 0.6.3
has caused the Debian Bug report #962411,
regarding bilibop: [INTL:pt] Updated Portuguese translation - debconf messages
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.)


-- 
962411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bilibop
Version: 0.6.1
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for bilibop's debconf messages
Translator: Américo Monteiro 
Feel free to use it.

For translation updates please contact 'Last Translator' 

-- 
Melhores cumprimentos/Best regards,

Américo Monteiro

-


bilibop_0.6.1_pt.po.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bilibop
Source-Version: 0.6.3
Done: Yann Amar 

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

Debian distribution maintenance software
pp.
Yann Amar  (supplier of updated bilibop 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: Tue,  9 Feb 2021 11:02:05 CET
Source: bilibop
Binary: 
Architecture: source
Version: 0.6.3
Distribution: unstable
Urgency: high
Maintainer: Yann Amar 
Changed-By: Yann Amar 
Description: 
Closes: 955504 956344 958870 962411 969606
Changes:
 bilibop (0.6.3) unstable; urgency=high
 .
   * Fix missing support for aufs in autopkgtest test (lockfs).
 Closes: #969606
 .
   * Move executable files from /usr/lib/bilibop to /usr/libexec/bilibop
 according to FHS 3.0, Debian Policy and lintian (pedantic).
 .
   * Update translations for debconf
 - nl: thanks to Frans Spiesschaert. Closes: #955504
 - de: thanks to Chris Leick. Closes: #956344
 - es: thanks to Camaleón. Closes: #958870
 - pt: thanks to Américo Monteiro. Closes: #962411
 .
   * debian/control:
 - Bump debhelper-compat version to 13.
 - Bump Standards-Version to 4.5.1: no changes needed.
   * debian/substvars: move to debian/description to avoid lintian warning
 (source-contains-debian-substvars).
   * debian/rules: update dh_gencontrol override accordingly (+fix syntax).
   * debian/copyright: update GPL license URL to https.
Checksums-Sha256: 
 bde24635c171c79e74723e4080c2f841647d204fd77617c468b389e4687b4479 1819 
bilibop_0.6.3.dsc
 33a24672c6d896a47f14d9a47e2b8688e1655c8d358b838b9d8351cc58de3640 128400 
bilibop_0.6.3.tar.xz
 740b612eb1ff6a66fd60386be30b2327dd0e34873185888e052ad1f12b7bf918 7094 
bilibop_0.6.3_sourceonly.buildinfo
Checksums-Sha1: 
 6a69668dc442e9008a223bcdbb24acc905ea48f3 1819 bilibop_0.6.3.dsc
 fd9f19858a5b84ca26fe01de4fee29c3b108d10d 128400 bilibop_0.6.3.tar.xz
 ec4b3e4f7ed688ebff2344707c0855c63822ba81 7094 
bilibop_0.6.3_sourceonly.buildinfo
Files: 
 655a3f0c71a6870ab4d2d2f4a9f56415 1819 admin optional bilibop_0.6.3.dsc
 3f8e939d3127fc1160082368c39b1109 128400 admin optional bilibop_0.6.3.tar.xz
 b6186fc72c02615b9814a429d5e18828 7094 - - bilibop_0.6.3_sourceonly.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEboF7OBIOe73fYj9R2KOaUw8NzMsFAmAiXbQACgkQ2KOaUw8N
zMs5tQ/+M7zpmJSG7unU11AXn8obI0FSbf+qyMzsJThOMZltxSo8qxQ+t8s59vy5
aAJI7ne9JmLE01DfOuXyV+BdGifh0D0WY4vGsLfDRy/VHTiLVgtpH+JuhL8jjOUk
FXf1ea6rFDwvkhvB864eh8Hv7Y1Jqoc1cv58lYj1Rj1UmwRWjAflGY3PcCWQ4RLf
fm/jh04+v8428NdIE7BzAFrLpsUN/+ZVKlKqce9jaDlofUEGMH4ygIFqPza/aogt
1lImsW8vV4sqA7J5j4t+HmxH/rkSuQ/p4gK+QrvnPkClqSo58U5quR6iyS76pUbh
38RaZtLcQF+0qzsPK84/Ixi27JPmzjqQkHka8jO6rjVqRm9BbfnyLf4RQ8emb44R
qmdIl5P3MGMXEJW74eQ2XfJ+tgzoTwN3tH3j5NL16p8UK/Lqf0sgNPRcbEj4WhOM
9uODb/xigv2eaXrADoJ81kOWNWnKs8yd1DhRJZVI5pDbZ70p0OmQAjSJQReD8zan
I+GPCnZAFzv0CIIr2sqoBhFSnq1n61nFhpBoUjfpvN3kmgD63LSa7SxHfwkMcoJS
2CULfZvUMnyyCNZrR9op4ISEhKv5Xvgkjjmw3grvuxwo9pKPgrHqgutMXIDHXVIC
doFehMWo6XFMfRCEg9cA8VUdvCVEbYehJ0naCpBWQlTA0FKWgbM=
=wn94
-END PGP SIGNATURE End Message ---

Bug#958870: marked as done ([INTL:es] Spanish translation of the debconf template)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 10:18:17 +
with message-id 
and subject line Bug#958870: fixed in bilibop 0.6.3
has caused the Debian Bug report #958870,
regarding [INTL:es] Spanish translation of the debconf template
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.)


-- 
958870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bilibop
Severity: wishlist
Tags: patch l10n

Hello,

You can find enclosed the Spanish translation template to be uploaded
with the latest package build.

Greetings,

-- 
Camaleón 
# bilibop po-debconf translation to Spanish
# Copyright (C) 2013 Software in the Public Interest
# This file is distributed under the same license as the bilibop package.
# Changes:
# - Initial translation
# Camaleón , 2010, 2013.
# - Updates
# Traductores, si no conocen el formato PO, merece la pena leer la
# documentación de gettext, especialmente las secciones dedicadas a este
# formato, por ejemplo ejecutando:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
# Equipo de traducción al español, por favor lean antes de traducir
# los siguientes documentos:
# - El proyecto de traducción de Debian al español
# http://www.debian.org/intl/spanish/
# especialmente las notas y normas de traducción en
# http://www.debian.org/intl/spanish/notas
# - La guía de traducción de po's de debconf:
# /usr/share/doc/po-debconf/README-trans
# o http://www.debian.org/intl/l10n/po-debconf/README-trans
msgid ""
msgstr ""
"Project-Id-Version: bilibop 0.4.20\n"
"Report-Msgid-Bugs-To: bili...@packages.debian.org\n"
"POT-Creation-Date: 2020-02-08 18:15+\n"
"PO-Revision-Date: 2020-04-14 13:58+\n"
"Last-Translator: Camaleón \n"
"Language-Team: Debian Spanish \n"
"Language: es\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../bilibop-rules.templates:1001
msgid "Do you intend to install bilibop-rules on a Live System ?"
msgstr "¿Va a instalar bilibop-rules en un sistema «Live»?"

#. Type: boolean
#. Description
#: ../bilibop-rules.templates:1001
msgid ""
"Some bilibop-rules settings can be useful on non-volatile Operating Systems, "
"when running from a removable and writable media (USB sticks, external HDD "
"or SD cards); but they are currently useless or even harmful for LiveCD or "
"LiveUSB systems."
msgstr ""
"Algunos de los ajustes de bilibop-rules pueden resultar útiles en sistemas "
"operativos persistentes cuando se ejecutan desde un dispositivo removible y "
"grabable (llaves USB, discos duros externos o tarjetas SD) pero resultan "
"completamente inútiles o incluso perjudiciales en sistemas LiveCD o LiveUSB."

#. Type: boolean
#. Description
#: ../bilibop-rules.templates:1001
msgid ""
"If you choose this option, no other question will be asked; bilibop udev "
"rules will be applied but nothing else will be modified on your system. Note "
"that in that case, this package is overkill and you should probably replace "
"it by the lighter but as much as efficient bilibop-udev package."
msgstr ""
"Si elige esta opción no se le harán más preguntas, se aplicarán las reglas "
"udev de bilibop pero no se modificará nada más en su sistema. Tenga en "
"cuenta que en este caso este paquete resulta excesivo y probablemente "
"debería reemplazarlo por otro más ligero pero igual de eficiente como el "
"paquete bilibop-udev."

#. Type: boolean
#. Description
#: ../bilibop-rules.templates:2001
msgid "Do you want to use custom bilibop rules and build them now ?"
msgstr "¿Desea utilizar reglas bilibop personalizadas y construirlas ahora?"

#. Type: boolean
#. Description
#: ../bilibop-rules.templates:2001
msgid ""
"If tens of removable media are plugged on the computer your system boots "
"from, bilibop udev rules can significantly increase boot time. This can be "
"avoided by using custom udev rules, which are specific to the device your "
"system is installed on."
msgstr ""
"Si tiene conectados varios dispositivos removibles en el equipo desde donde "
"inicia el sistema, las reglas udev de bilibop pueden incrementar "
"significativamente el tiempo de inicio. Para evitar esto puede utilizar "
"reglas udev personalizadas que son específicas para el dispositivo donde se "
"encuentra instalado el sistema."

#. Type: boolean
#. Description
#: ../bilibop-rules.templates:2001
msgid ""
"That said, if this device can boot from different hardware port types (as "
"USB/Firewire, USB/eSATA, USB/MMC/SD, etc.), you should check the resulting "
"rules by 

Bug#956344: marked as done (bilibop: [INTL:de] Updated German debconf translation)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 10:18:17 +
with message-id 
and subject line Bug#956344: fixed in bilibop 0.6.3
has caused the Debian Bug report #956344,
regarding bilibop: [INTL:de] Updated German debconf translation
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.)


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

Package: bilibop
Version: 0.6.1
Severity: wishlist
Tags: l10n patch



Hi,

please find attached the newest German debconf translation.

Kind regards,
Chris


de.po.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bilibop
Source-Version: 0.6.3
Done: Yann Amar 

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

Debian distribution maintenance software
pp.
Yann Amar  (supplier of updated bilibop 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: Tue,  9 Feb 2021 11:02:05 CET
Source: bilibop
Binary: 
Architecture: source
Version: 0.6.3
Distribution: unstable
Urgency: high
Maintainer: Yann Amar 
Changed-By: Yann Amar 
Description: 
Closes: 955504 956344 958870 962411 969606
Changes:
 bilibop (0.6.3) unstable; urgency=high
 .
   * Fix missing support for aufs in autopkgtest test (lockfs).
 Closes: #969606
 .
   * Move executable files from /usr/lib/bilibop to /usr/libexec/bilibop
 according to FHS 3.0, Debian Policy and lintian (pedantic).
 .
   * Update translations for debconf
 - nl: thanks to Frans Spiesschaert. Closes: #955504
 - de: thanks to Chris Leick. Closes: #956344
 - es: thanks to Camaleón. Closes: #958870
 - pt: thanks to Américo Monteiro. Closes: #962411
 .
   * debian/control:
 - Bump debhelper-compat version to 13.
 - Bump Standards-Version to 4.5.1: no changes needed.
   * debian/substvars: move to debian/description to avoid lintian warning
 (source-contains-debian-substvars).
   * debian/rules: update dh_gencontrol override accordingly (+fix syntax).
   * debian/copyright: update GPL license URL to https.
Checksums-Sha256: 
 bde24635c171c79e74723e4080c2f841647d204fd77617c468b389e4687b4479 1819 
bilibop_0.6.3.dsc
 33a24672c6d896a47f14d9a47e2b8688e1655c8d358b838b9d8351cc58de3640 128400 
bilibop_0.6.3.tar.xz
 740b612eb1ff6a66fd60386be30b2327dd0e34873185888e052ad1f12b7bf918 7094 
bilibop_0.6.3_sourceonly.buildinfo
Checksums-Sha1: 
 6a69668dc442e9008a223bcdbb24acc905ea48f3 1819 bilibop_0.6.3.dsc
 fd9f19858a5b84ca26fe01de4fee29c3b108d10d 128400 bilibop_0.6.3.tar.xz
 ec4b3e4f7ed688ebff2344707c0855c63822ba81 7094 
bilibop_0.6.3_sourceonly.buildinfo
Files: 
 655a3f0c71a6870ab4d2d2f4a9f56415 1819 admin optional bilibop_0.6.3.dsc
 3f8e939d3127fc1160082368c39b1109 128400 admin optional bilibop_0.6.3.tar.xz
 b6186fc72c02615b9814a429d5e18828 7094 - - bilibop_0.6.3_sourceonly.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEboF7OBIOe73fYj9R2KOaUw8NzMsFAmAiXbQACgkQ2KOaUw8N
zMs5tQ/+M7zpmJSG7unU11AXn8obI0FSbf+qyMzsJThOMZltxSo8qxQ+t8s59vy5
aAJI7ne9JmLE01DfOuXyV+BdGifh0D0WY4vGsLfDRy/VHTiLVgtpH+JuhL8jjOUk
FXf1ea6rFDwvkhvB864eh8Hv7Y1Jqoc1cv58lYj1Rj1UmwRWjAflGY3PcCWQ4RLf
fm/jh04+v8428NdIE7BzAFrLpsUN/+ZVKlKqce9jaDlofUEGMH4ygIFqPza/aogt
1lImsW8vV4sqA7J5j4t+HmxH/rkSuQ/p4gK+QrvnPkClqSo58U5quR6iyS76pUbh
38RaZtLcQF+0qzsPK84/Ixi27JPmzjqQkHka8jO6rjVqRm9BbfnyLf4RQ8emb44R
qmdIl5P3MGMXEJW74eQ2XfJ+tgzoTwN3tH3j5NL16p8UK/Lqf0sgNPRcbEj4WhOM
9uODb/xigv2eaXrADoJ81kOWNWnKs8yd1DhRJZVI5pDbZ70p0OmQAjSJQReD8zan
I+GPCnZAFzv0CIIr2sqoBhFSnq1n61nFhpBoUjfpvN3kmgD63LSa7SxHfwkMcoJS
2CULfZvUMnyyCNZrR9op4ISEhKv5Xvgkjjmw3grvuxwo9pKPgrHqgutMXIDHXVIC
doFehMWo6XFMfRCEg9cA8VUdvCVEbYehJ0naCpBWQlTA0FKWgbM=
=wn94
-END PGP SIGNATURE End Message ---

Bug#955504: marked as done (bilibop: [INTL:nl] Dutch translation of debconf messages)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 10:18:17 +
with message-id 
and subject line Bug#955504: fixed in bilibop 0.6.3
has caused the Debian Bug report #955504,
regarding bilibop: [INTL:nl] Dutch translation of debconf messages
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.)


-- 
955504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
 
 
Package: bilibop 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch translation of bilibop debconf
messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
 

-- 
Met vriendelijke groet,
Frans Spiesschaert



nl.po.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bilibop
Source-Version: 0.6.3
Done: Yann Amar 

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

Debian distribution maintenance software
pp.
Yann Amar  (supplier of updated bilibop 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: Tue,  9 Feb 2021 11:02:05 CET
Source: bilibop
Binary: 
Architecture: source
Version: 0.6.3
Distribution: unstable
Urgency: high
Maintainer: Yann Amar 
Changed-By: Yann Amar 
Description: 
Closes: 955504 956344 958870 962411 969606
Changes:
 bilibop (0.6.3) unstable; urgency=high
 .
   * Fix missing support for aufs in autopkgtest test (lockfs).
 Closes: #969606
 .
   * Move executable files from /usr/lib/bilibop to /usr/libexec/bilibop
 according to FHS 3.0, Debian Policy and lintian (pedantic).
 .
   * Update translations for debconf
 - nl: thanks to Frans Spiesschaert. Closes: #955504
 - de: thanks to Chris Leick. Closes: #956344
 - es: thanks to Camaleón. Closes: #958870
 - pt: thanks to Américo Monteiro. Closes: #962411
 .
   * debian/control:
 - Bump debhelper-compat version to 13.
 - Bump Standards-Version to 4.5.1: no changes needed.
   * debian/substvars: move to debian/description to avoid lintian warning
 (source-contains-debian-substvars).
   * debian/rules: update dh_gencontrol override accordingly (+fix syntax).
   * debian/copyright: update GPL license URL to https.
Checksums-Sha256: 
 bde24635c171c79e74723e4080c2f841647d204fd77617c468b389e4687b4479 1819 
bilibop_0.6.3.dsc
 33a24672c6d896a47f14d9a47e2b8688e1655c8d358b838b9d8351cc58de3640 128400 
bilibop_0.6.3.tar.xz
 740b612eb1ff6a66fd60386be30b2327dd0e34873185888e052ad1f12b7bf918 7094 
bilibop_0.6.3_sourceonly.buildinfo
Checksums-Sha1: 
 6a69668dc442e9008a223bcdbb24acc905ea48f3 1819 bilibop_0.6.3.dsc
 fd9f19858a5b84ca26fe01de4fee29c3b108d10d 128400 bilibop_0.6.3.tar.xz
 ec4b3e4f7ed688ebff2344707c0855c63822ba81 7094 
bilibop_0.6.3_sourceonly.buildinfo
Files: 
 655a3f0c71a6870ab4d2d2f4a9f56415 1819 admin optional bilibop_0.6.3.dsc
 3f8e939d3127fc1160082368c39b1109 128400 admin optional bilibop_0.6.3.tar.xz
 b6186fc72c02615b9814a429d5e18828 7094 - - bilibop_0.6.3_sourceonly.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEboF7OBIOe73fYj9R2KOaUw8NzMsFAmAiXbQACgkQ2KOaUw8N
zMs5tQ/+M7zpmJSG7unU11AXn8obI0FSbf+qyMzsJThOMZltxSo8qxQ+t8s59vy5
aAJI7ne9JmLE01DfOuXyV+BdGifh0D0WY4vGsLfDRy/VHTiLVgtpH+JuhL8jjOUk
FXf1ea6rFDwvkhvB864eh8Hv7Y1Jqoc1cv58lYj1Rj1UmwRWjAflGY3PcCWQ4RLf
fm/jh04+v8428NdIE7BzAFrLpsUN/+ZVKlKqce9jaDlofUEGMH4ygIFqPza/aogt
1lImsW8vV4sqA7J5j4t+HmxH/rkSuQ/p4gK+QrvnPkClqSo58U5quR6iyS76pUbh
38RaZtLcQF+0qzsPK84/Ixi27JPmzjqQkHka8jO6rjVqRm9BbfnyLf4RQ8emb44R
qmdIl5P3MGMXEJW74eQ2XfJ+tgzoTwN3tH3j5NL16p8UK/Lqf0sgNPRcbEj4WhOM
9uODb/xigv2eaXrADoJ81kOWNWnKs8yd1DhRJZVI5pDbZ70p0OmQAjSJQReD8zan
I+GPCnZAFzv0CIIr2sqoBhFSnq1n61nFhpBoUjfpvN3kmgD63LSa7SxHfwkMcoJS
2CULfZvUMnyyCNZrR9op4ISEhKv5Xvgkjjmw3grvuxwo9pKPgrHqgutMXIDHXVIC
doFehMWo6XFMfRCEg9cA8VUdvCVEbYehJ0naCpBWQlTA0FKWgbM=
=wn94
-END PGP SIGNATURE End Message ---

Bug#979970: marked as done (libselinux1: dependency to newer libc6 ignored by/missing for aptitude)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 10:03:18 +
with message-id 
and subject line Bug#979970: fixed in libselinux 3.1-3
has caused the Debian Bug report #979970,
regarding libselinux1: dependency to newer libc6 ignored by/missing for aptitude
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.)


-- 
979970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libselinux1
Version: 2.8-1+b1
Severity: grave

Right now, an update from buster to bullseye on amd64 completely
bricks the system because libselinux1 is requiring a libc6 which is
not yet installed on the system:

Preparing to unpack .../0-libselinux1_3.1-2+b2_amd64.deb ...
De-configuring libselinux1:i386 (2.8-1+b1) ...
Unpacking libselinux1:amd64 (3.1-2+b2) over (2.8-1+b1) ...
tar: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.30' not
found (required by /lib/x86_64-linux-gnu/libselinux.so.1)
dpkg-deb: error: tar subprocess returned error exit status 1

It is then not possible anymore to recover the system because dpkg
(mv, ...) is no longer working.

There is most likely some kind dependency missing to let aptitude
known that it must first update libc6 before it can update
libselinux1. At least on this system, the installed version of libc6
for amd64 and i386 was still 2.28-10 when this happened
--- End Message ---
--- Begin Message ---
Source: libselinux
Source-Version: 3.1-3
Done: Laurent Bigonville 

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated libselinux 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: Tue, 09 Feb 2021 10:19:50 +0100
Source: libselinux
Architecture: source
Version: 3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian SELinux maintainers 
Changed-By: Laurent Bigonville 
Closes: 979970
Changes:
 libselinux (3.1-3) unstable; urgency=medium
 .
   [ Christian Göttsche ]
   * d/gitlab-ci.yml: Use Debian recipe
   * d/README: Drop note about ancient SELinux mount point
   * d/control: Bump debhelper compat to level 13
   * d/control: Bump Standards-Version to 4.5.1 (no further changes)
   * d/control: Update homepage
   * d/rules: Enable -Wall and -Werror
   * d/rules: Enable build hardening
   * d/control: Drop cute fields
 .
   [ Laurent Bigonville ]
   * Do not use gettid() for Bullseye and use syscall() instead (Closes: 
#979970)
Checksums-Sha1:
 7b4281e68745ba1ec71147098f6cd68a5128d264 2300 libselinux_3.1-3.dsc
 9a409aeb6eae48fdf720aff83dad97eaf766be82 24176 libselinux_3.1-3.debian.tar.xz
 7dde60bdb758b96d050e0f058bc65196cc43078b 12344 
libselinux_3.1-3_source.buildinfo
Checksums-Sha256:
 42810484f3776af09a2e0ab726e3be877fc8a54d6bf51702e46c22f945ab5177 2300 
libselinux_3.1-3.dsc
 7170ab6914f0d2e93de169da312df961f799f5d58cc0a4c552e3f8a7882f3c81 24176 
libselinux_3.1-3.debian.tar.xz
 09b13fd1b342662e62994df391a7b9eba01f26de4c40707e52a23678da998c80 12344 
libselinux_3.1-3_source.buildinfo
Files:
 c6c5f358742e281e27045e7589d685c8 2300 libs optional libselinux_3.1-3.dsc
 963bf4bb91c9abfa0684f497e32d2983 24176 libs optional 
libselinux_3.1-3.debian.tar.xz
 f58ef684a1da99a80e433971d2011a46 12344 libs optional 
libselinux_3.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAmAiVlQRHGJpZ29uQGRl
Ymlhbi5vcmcACgkQH8WJHrqwQ9UkdQgAmEbylqb6JtS7CwahGBPYwpxORsNoxkk9
IVGnj+dTa6x27t9xEh1VHyBh437dO8+RkjhBNDgasZRRctqS1CBd8XN6/pgJsvN5
O3VOQ+DlziEqfnY7ceW6izQW7JHMkSf6KoLv8Dda1E/dRM6Q96otEsL/pKqwNBMC
SyYP8bH75V64BeF4HwUKsm1vmkVvuU05pe0TjAcoVOiCXkFl6jd9tfAydNSaiips
6wsTbiyBa/tFYQULmgC0VuIuq7VjJmcH9FGcSQSG6kbHfpS0nES4YjS95WfeURXc
zRIT9V7Axm7udXWsmnw7M23MDDjjjVaIUgUp/le6K4uuO6ANIKe5mg==
=J9Ku
-END PGP SIGNATURE End Message ---

Bug#982350: marked as done (plexus-cipher: FTBFS with OpenJDK 17: module java.base does not "opens java.lang" to unnamed module)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 10:03:30 +
with message-id 
and subject line Bug#982350: fixed in plexus-cipher 1.8-1
has caused the Debian Bug report #982350,
regarding plexus-cipher: FTBFS with OpenJDK 17: module java.base does not 
"opens java.lang" to unnamed module
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.)


-- 
982350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plexus-cipher
Severity: important
Tags: ftbfs sid bookworm
User: debian-j...@lists.debian.org
Usertags: default-java17

plexus-cipher fails to build with OpenJDK 17, the tests fail with the following 
error:


  [INFO] ---
  [INFO]  T E S T S
  [INFO] ---
  [INFO] Running org.sonatype.plexus.components.cipher.PBECipherTest
  [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.205 
s <<< FAILURE! - in org.sonatype.plexus.components.cipher.PBECipherTest
  [ERROR] testEncrypt(org.sonatype.plexus.components.cipher.PBECipherTest)  
Time elapsed: 0.192 s  <<< ERROR!
  com.google.common.util.concurrent.UncheckedExecutionException: 
com.google.common.util.concurrent.UncheckedExecutionException: 
com.google.common.util.concurrent.UncheckedExecutionException: 
java.lang.IllegalStateException: Unable to load cache item
  at 
com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2051)
  at com.google.common.cache.LocalCache.get(LocalCache.java:3951)
  at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3974)
  at 
com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4958)
  at 
com.google.common.cache.LocalCache$LocalLoadingCache.getUnchecked(LocalCache.java:4964)
  at com.google.inject.internal.FailableCache.get(FailableCache.java:51)
  at 
com.google.inject.internal.MembersInjectorStore.get(MembersInjectorStore.java:65)
  at 
com.google.inject.internal.Initializer$InjectableReference.validate(Initializer.java:184)
  at 
com.google.inject.internal.Initializer.validateOustandingInjections(Initializer.java:124)
  at 
com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:139)
  at 
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
  at com.google.inject.Guice.createInjector(Guice.java:87)
  at com.google.inject.Guice.createInjector(Guice.java:69)
  at com.google.inject.Guice.createInjector(Guice.java:59)
  at 
org.sonatype.guice.bean.containers.InjectedTestCase.setUp(InjectedTestCase.java:62)
  at 
org.sonatype.plexus.components.cipher.PBECipherTest.setUp(PBECipherTest.java:45)
  at junit.framework.TestCase.runBare(TestCase.java:128)
  at junit.framework.TestResult$1.protect(TestResult.java:106)
  at junit.framework.TestResult.runProtected(TestResult.java:124)
  at junit.framework.TestResult.run(TestResult.java:109)
  at junit.framework.TestCase.run(TestCase.java:120)
  at junit.framework.TestSuite.runTest(TestSuite.java:230)
  at junit.framework.TestSuite.run(TestSuite.java:225)
  at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
  at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.base/java.lang.reflect.Method.invoke(Method.java:566)
  at 
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:100)
  at 
org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:140)
  at 
org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:113)
  at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
  at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
  at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
  at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
  Caused by: com.google.common.util.concurrent.UncheckedExecutionException: 
com.google.common.util.concurrent.UncheckedExecutionException: 
java.lang.IllegalStateException: Unable to load cache item

Bug#898781: marked as done (python-ipywidgets-doc: HTML documentation appears to be missing (All 'Format' sections are invalid))

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 09:33:19 +
with message-id 
and subject line Bug#898781: fixed in ipywidgets 6.0.0-8
has caused the Debian Bug report #898781,
regarding python-ipywidgets-doc: HTML documentation appears to be missing (All 
'Format' sections are invalid)
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.)


-- 
898781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-ipywidgets-doc
Version: 6.0.0-2
Severity: important

Dear Maintainer,

While installing python-ipywidgets-doc dpkg reported the following error.

  Processing 1 added doc-base file...
  Error in `/usr/share/doc-base/python-ipywidgets-doc', line 11: all `Format'
sections are invalid.
  Note: `install-docs --verbose --check file_name' may give more details about
the above error.

I ran --verbose --check:

  Warning in `/usr/share/doc-base/python-ipywidgets-doc', line 11: file
`/usr/share/doc/python-ipywidgets-doc/html/  index.html' does not exist.
  Error in `/usr/share/doc-base/python-ipywidgets-doc', line 11: all `Format'
sections are invalid.

There doesn't appear to be any HTML files in the .deb

  dpkg --listfiles python-ipywidgets-doc
  /.
  /usr
  /usr/share
  /usr/share/doc
  /usr/share/doc/python-ipywidgets-doc
  /usr/share/doc/python-ipywidgets-doc/changelog.Debian.gz
  /usr/share/doc/python-ipywidgets-doc/copyright
  /usr/share/doc/python-ipywidgets-doc/html
  /usr/share/doc/python-ipywidgets-doc/html/_static
  /usr/share/doc-base
  /usr/share/doc-base/python-ipywidgets-doc
  /usr/share/lintian
  /usr/share/lintian/overrides
  /usr/share/lintian/overrides/python-ipywidgets-doc
  /usr/share/doc/python-ipywidgets-doc/html/_static/mathjax




-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'stable-debug'), (500, 'testing'), 
(500, 'stable'), (110, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages python-ipywidgets-doc depends on:
ii  jupyter-sphinx-theme-common  0.0.6+ds1-3
ii  libjs-mathjax2.7.3+dfsg-1

python-ipywidgets-doc recommends no packages.

python-ipywidgets-doc suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ipywidgets
Source-Version: 6.0.0-8
Done: Gordon Ball 

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

Debian distribution maintenance software
pp.
Gordon Ball  (supplier of updated ipywidgets 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: Tue, 09 Feb 2021 09:00:09 +
Source: ipywidgets
Architecture: source
Version: 6.0.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Gordon Ball 
Closes: 898781
Changes:
 ipywidgets (6.0.0-8) unstable; urgency=medium
 .
   * Upload to unstable
   * Missing bug close from the previous version: Closes: #898781
   * Add a hint to "Widget Javascript not detected" warnings.
Checksums-Sha1:
 e3de10135a083dcc7c2967549c13c007b37f5621 2964 ipywidgets_6.0.0-8.dsc
 9ace935bdfd75457fcc13d4d807107a423bda646 136372 
ipywidgets_6.0.0-8.debian.tar.xz
 2e95ff6af3853691e9a75fb6e7322faf30d5ca81 16775 
ipywidgets_6.0.0-8_source.buildinfo
Checksums-Sha256:
 c0e0073aa9f1aeedcd2cbe79cafa46c6a13afdd354f725ef25171bb629b74d61 2964 
ipywidgets_6.0.0-8.dsc
 82ab92cd23e3354234a1433222be7e5edf374171ed93f2d829e1bfd3cb44ac19 136372 
ipywidgets_6.0.0-8.debian.tar.xz
 2b2bf0d4f114354161604a27defe4f5202c6b6353bfd962cfa2b3d45326e1e6e 16775 
ipywidgets_6.0.0-8_source.buildinfo
Files:
 d295c544c14dad10a3c72dba9cd21c5d 2964 python optional ipywidgets_6.0.0-8.dsc
 6614950736526c075fee16ef448c892b 136372 python optional 
ipywidgets_6.0.0-8.debian.tar.xz
 f74d37082b4e8a1123fce75bf

Bug#977051: marked as done (meson: package missing dependency on dpkg-dev)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 09:33:26 +
with message-id 
and subject line Bug#977051: fixed in meson 0.57.0~rc1-1
has caused the Debian Bug report #977051,
regarding meson: package missing dependency on dpkg-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.)


-- 
977051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: meson
Version: 0.56.0-1.1
Severity: normal

Meson's debian package currently does not depend on dpkg-dev.

However, default_libdir() tries to run dpkg-architecture:
https://github.com/mesonbuild/meson/blob/0.56.0/mesonbuild/mesonlib.py#L743

Consequence: meson will install libraries to $PREFIX/lib64 instead of expected 
path $PREFIX/lib/x86_64-linux-gnu

Reproduce:

$ docker run --rm -it debian:sid-slim
$ apt-get update && apt-get install meson
$ dpkg-architecture -qDEB_HOST_MULTIARCH prints
bash: dpkg-architecture: command not found

Expected:

$ apt-get update && apt-get install meson
$ dpkg-architecture -qDEB_HOST_MULTIARCH
x86_64-linux-gnu

Suggested fix:
Add dpkg-dev to "Recommends:" header of meson's debian packge.

Bug previously reported upstream:
https://github.com/mesonbuild/meson/issues/7270

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

Kernel: Linux 5.4.0-56-generic (SMP w/8 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: meson
Source-Version: 0.57.0~rc1-1
Done: Jussi Pakkanen 

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

Debian distribution maintenance software
pp.
Jussi Pakkanen  (supplier of updated meson 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: Tue, 09 Feb 2021 01:21:53 +0200
Source: meson
Architecture: source
Version: 0.57.0~rc1-1
Distribution: experimental
Urgency: medium
Maintainer: Jussi Pakkanen 
Changed-By: Jussi Pakkanen 
Closes: 977051
Changes:
 meson (0.57.0~rc1-1) experimental; urgency=medium
 .
   * New upstream release.
   * Add recommends to dpkg-dev. Closes: #977051.
Checksums-Sha1:
 b03ab45f6a3c96df9460bacabdee4187cece4467 3457 meson_0.57.0~rc1-1.dsc
 dbd23ec7efc5b6b4a2aa1309ac4d94d64a66c34a 1844193 meson_0.57.0~rc1.orig.tar.gz
 aeadeee3659ffd4978dab75d8166a319a3b5a851 14188 meson_0.57.0~rc1-1.debian.tar.xz
 ec7e77d309cb72add363dcca91732781b36e8f91 6301 
meson_0.57.0~rc1-1_source.buildinfo
Checksums-Sha256:
 94a3f15ab5e8b90f754c8b81ccbf9781c105bec281b44fc5fb56505f3affd4c0 3457 
meson_0.57.0~rc1-1.dsc
 60b8494446a6d47572aff52617273bca3b449991cfe5eda46e500fe24c9f5012 1844193 
meson_0.57.0~rc1.orig.tar.gz
 282e3e67fecdc8e23a0b091c964bc2bbf821f15b44a13d83e69250510be6b6d2 14188 
meson_0.57.0~rc1-1.debian.tar.xz
 fbdfbaa67545ac6ce23ded24f9a3cbea91d1122a2b54c428ea3103134a9b07cd 6301 
meson_0.57.0~rc1-1_source.buildinfo
Files:
 7ceb0c519817a4b6aab49e5ae1b39816 3457 devel optional meson_0.57.0~rc1-1.dsc
 3db7b64627d4745d4a65e273b60216d7 1844193 devel optional 
meson_0.57.0~rc1.orig.tar.gz
 edb829c02917560be9c08652ecb3007a 14188 devel optional 
meson_0.57.0~rc1-1.debian.tar.xz
 42a1a1a5a32d460905468a1e61857325 6301 devel optional 
meson_0.57.0~rc1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPbRrVe+lnUDmIyFI0U7xXa/hE0cFAmAiU9cACgkQ0U7xXa/h
E0d1mBAAxDSKLSAA/7xqGGUH58sdfx4FgUoQ99BuxDpm8aiiNVkKNm7jdw3j75NC
/TZNEG3+wNECKvffqMrszrFdgF2D8tyo+VtpEmgeshss3T6DOqmI+CVrEELfmc7E
kvYSatI1xSUZrnOroiy0u5waqiLQ7IlCXqikKDbDmOzZ0CXSVqRX3XX/4hDjuVil
n204HChIIKZQO7gf6RuP2/I8UT44jWFxh7bkIe2XihL9FFb5QYZ0ZFDQCVaxIPzw
KrwhuAxBR7y+6yDnjbwvrJoP7/a0wWA1UKOCxhy+/XSoPpRPVGda5NmLjSpBsJob
mFdydYoMkCYe9dWxbM2dE15h6T57ehXuhkAsuj2y5Ai4/RrwkfR0MRQxO3Xrs2xs
UqpxLJ4U4UA7IOj035MjUxUQPbK3XikmXmi2xBI5ueZsAk2HcWdQ69mlAtq6fHdu
S30/ikACppD27rzLoekpumMb+lIbibm7znIv2nDssd/MQNWsQPFw2cwyTMj1P/D3
ub4Somu9B6pOoITIrKcIj

Bug#982288: marked as done (rootless podman fails with very long uids)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 08:52:28 +
with message-id 
and subject line Re: Bug#982288: podman: Can't run caontainers - failed to 
connect to container's attach socket - fixed!
has caused the Debian Bug report #982288,
regarding rootless podman fails with very long uids
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.)


-- 
982288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: podman
Version: 3.0.0~rc2+dfsg1-2+b1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: s...@robots.org.uk

After upgrading to podman 3, I can't run any containers any more.

$ podman run --rm -it docker.io/library/debian:10 
Error: failed to connect to container's attach socket: 
/run/user/876099160/libpod/tmp/socket/3178d20b8a3a42642dc6a7f32884df47019bc4a2a82af94fe4928b00ed3293c9/attach:
 no such file or directory

The directory /run/user/876099160/libpod/tmp/socket is empty.

According to unix(7), socket paths are limited to 108 bytes, but the
path in the error message is slightly longer than that:

$ echo -n 
/run/user/876099160/libpod/tmp/socket/18654637587d169f834095dce40d4812378e0056936974c9b7073ba1ae767bfa/attach
 | wc -c
109

Podman had a similar sounding bug a couple of years ago,
, but that was
fixed in podman 0.11.1.

Full debug output:

INFO[] podman filtering at log level debug  
DEBU[] Called run.PersistentPreRunE(podman --log-level=debug run --rm 
-it docker.io/library/debian:10) 
DEBU[] Reading configuration file 
"/usr/share/containers/containers.conf" 
DEBU[] Merged system config "/usr/share/containers/containers.conf": 
&{Containers:{Devices:[] Volumes:[] ApparmorProfile:containers-default-0.33.1 
Annotations:[] CgroupNS:private Cgroups:enabled DefaultCapabilities:[CHOWN 
DAC_OVERRIDE FOWNER FSETID KILL NET_BIND_SERVICE SETFCAP SETGID SETPCAP SETUID 
SYS_CHROOT] DefaultSysctls:[net.ipv4.ping_group_range=0 0] DefaultUlimits:[] 
DefaultMountsFile: DNSServers:[] DNSOptions:[] DNSSearches:[] 
EnableKeyring:true EnableLabeling:true 
Env:[PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 
TERM=xterm] EnvHost:false HTTPProxy:true Init:false InitPath: IPCNS:private 
LogDriver:k8s-file LogSizeMax:-1 NetNS:slirp4netns NoHosts:false PidsLimit:2048 
PidNS:private SeccompProfile:/usr/share/containers/seccomp.json ShmSize:65536k 
TZ: Umask:0022 UTSNS:private UserNS:host UserNSSize:65536} 
Engine:{ImageBuildFormat:oci CgroupCheck:false CgroupManager:systemd 
ConmonEnvVars:[PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin]
 ConmonPath:[/usr/libexec/podman/conmon /usr/local/libexec/podman/conmon 
/usr/local/lib/podman/conmon /usr/bin/conmon /usr/sbin/conmon 
/usr/local/bin/conmon /usr/local/sbin/conmon /run/current-system/sw/bin/conmon] 
DetachKeys:ctrl-p,ctrl-q EnablePortReservation:true Env:[] 
EventsLogFilePath:/run/user/876099160/libpod/tmp/events/events.log 
EventsLogger:journald HooksDir:[/usr/share/containers/oci/hooks.d] 
ImageDefaultTransport:docker:// InfraCommand: InfraImage:k8s.gcr.io/pause:3.2 
InitPath:/usr/libexec/podman/catatonit LockType:shm MultiImageArchive:false 
Namespace: NetworkCmdPath: NetworkCmdOptions:[] NoPivotRoot:false NumLocks:2048 
OCIRuntime:crun OCIRuntimes:map[crun:[/usr/bin/crun /usr/sbin/crun 
/usr/local/bin/crun /usr/local/sbin/crun /sbin/crun /bin/crun 
/run/current-system/sw/bin/crun] kata:[/usr/bin/kata-runtime 
/usr/sbin/kata-runtime /usr/local/bin/kata-runtime /usr/local/sbin/kata-runtime 
/sbin/kata-runtime /bin/kata-runtime /usr/bin/kata-qemu /usr/bin/kata-fc] 
runc:[/usr/bin/runc /usr/sbin/runc /usr/local/bin/runc /usr/local/sbin/runc 
/sbin/runc /bin/runc /usr/lib/cri-o-runc/sbin/runc 
/run/current-system/sw/bin/runc]] PullPolicy:missing Remote:false RemoteURI: 
RemoteIdentity: ActiveService: ServiceDestinations:map[] RuntimePath:[] 
RuntimeSupportsJSON:[crun runc] RuntimeSupportsNoCgroups:[crun] 
RuntimeSupportsKVM:[kata kata-runtime kata-qemu kata-fc] 
SetOptions:{StorageConfigRunRootSet:false StorageConfigGraphRootSet:false 
StorageConfigGraphDriverNameSet:false StaticDirSet:false VolumePathSet:false 
TmpDirSet:false} SignaturePolicyPath:/etc/containers/policy.json SDNotify:false 
StateType:3 
StaticDir:/home/ipa.example.com/sam.morris/.local/share/containers/storage/libpod
 StopTimeout:10 TmpDir:/run/user/876099160/libpod/tmp 
VolumePath:/home/ipa.example.com/sam.morris/.local/share/containers/storage/volumes
 VolumePlugins:map[]}

Bug#954907: marked as done (python3-dateparser: Warning with autopkgtest when python3.8 is default)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 08:33:32 +
with message-id 
and subject line Bug#954907: fixed in dateparser 1.0.0-1
has caused the Debian Bug report #954907,
regarding python3-dateparser: Warning with autopkgtest when python3.8 is default
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.)


-- 
954907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-dateparser
Version: 0.7.2-1
Severity: normal

While investigatin a resolution for #954147, I noticed the following
warning being emitted.  Presumably this will turn to an error in the
future and should, at some point, be addressed:

tmp/autopkgtest.ced6Wo/build.9qW/real-tree/dateparser/date.py:142: 
FutureWarning: Date formats should be list, tuple or set of strings
  warn(_DateLocaleParser.DATE_FORMATS_ERROR_MESSAGE, FutureWarning)

Scott K
--- End Message ---
--- Begin Message ---
Source: dateparser
Source-Version: 1.0.0-1
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated dateparser 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: Tue, 09 Feb 2021 00:17:09 -0800
Source: dateparser
Architecture: source
Version: 1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Stefano Rivera 
Closes: 954907
Changes:
 dateparser (1.0.0-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Antoine Beaupré ]
   * new upstream release (Closes: #954907)
   * remove patch disabling convertdate support in tests, convertdate is in
 Debian now. all Debian-specific patches gone.
 .
   [ Stefano Rivera ]
   * Patch: Skip hijri tests, the converter isn't in Debian yet.
   * Patch: Don't git clone unicode CLDR data.
   * Run autopkgtests with pytest, following upstream.
   * Run autopkgtests in $AUTOPKGTEST_TMP to be sure we're testing the
 installed module.
   * Don't install dateparser_scripts into the binary package, these are used
 at build time only.
   * Declare Rules-Requires-Root: no.
   * Bump watch file format to 4.
   * Bump Standards-Version to 4.5.1, no changes needed.
Checksums-Sha1:
 aba82ff24876e7f9de2262df93c5ed43585d4b6c 1880 dateparser_1.0.0-1.dsc
 2f0a087c6dbbe86d6236766c6d78cbf1eef2a3e0 471943 dateparser_1.0.0.orig.tar.gz
 119400a81f8fec046a080e67b7f23988b66afef6 4676 dateparser_1.0.0-1.debian.tar.xz
 4c78fed0abfa17cb97cafe342b1bce11a98daad9 5700 
dateparser_1.0.0-1_source.buildinfo
Checksums-Sha256:
 9bd9d61cbd9db8016d7b3098f8a96699e3230e4c04388743be0f601826f8bc5c 1880 
dateparser_1.0.0-1.dsc
 aeaa2025f8b66d32757dfde5b988ce57e3addaaae8d56b99f69c14f6fdf996ee 471943 
dateparser_1.0.0.orig.tar.gz
 5b60a689b5fbcfabf5f9eb0f9b855aa063df67478f50bb3d1d0a73c0d9f796f9 4676 
dateparser_1.0.0-1.debian.tar.xz
 6004e3edc0d7716deafbdb96a2dffc5c032bb12b7217137abb01ff398b343616 5700 
dateparser_1.0.0-1_source.buildinfo
Files:
 225605624c93d980a6ec7ef75d5c50d3 1880 python optional dateparser_1.0.0-1.dsc
 e02d7a1b33d02ab06f9f791e05d8663d 471943 python optional 
dateparser_1.0.0.orig.tar.gz
 032477fee1a8759658aee7222aa11482 4676 python optional 
dateparser_1.0.0-1.debian.tar.xz
 f43b30b78790cb84157a47ebcc743c7d 5700 python optional 
dateparser_1.0.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYCJFtgAKCRBHew2wJjpU
2DEXAP0V+8xlFX3ItD7fSmBaYddg1/l1W5tegB3+JGXBc+zKEgEAnElddM/2CEGT
22R+iSCGuXYgQ6NU1IxqmMgcMwtylQI=
=TZkU
-END PGP SIGNATURE End Message ---

Bug#978032: marked as done (python-cobra: autopkgtest regression in testing)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2021 08:22:12 +
with message-id 
and subject line Bug#978032: fixed in python-cobra 0.21.0-1
has caused the Debian Bug report #978032,
regarding python-cobra: autopkgtest regression in testing
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.)


-- 
978032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cobra
Version: 0.19.0-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

The autopkgtests of python-cobra recently started to fail in testing [1].
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/p/python-cobra/testing/amd64/


 ERRORS 
__ ERROR at setup of TestManipulation.test_escape_ids __

filename = '/usr/lib/python3/dist-packages/cobra/test/data/textbook.xml.gz'
number = 
f_replace = {'F_GENE': ,
'F_GENE_REV': , 'F_GROUP':
, 'F_GROUP_REV': , ...}
kwargs = {}
doc =  >
cobra_error = CobraSBMLError('Something went wrong reading the SBML
model. Most likely the SBML model is not valid. Please check
tha...ame)`\nIf the model is valid and cannot be read please open an
issue at https://github.com/opencobra/cobrapy/issues .')
--- End Message ---
--- Begin Message ---
Source: python-cobra
Source-Version: 0.21.0-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-cobra 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: Tue, 09 Feb 2021 08:43:16 +0100
Source: python-cobra
Architecture: source
Version: 0.21.0-1
Distribution: unstable
Urgency: high
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 978032
Changes:
 python-cobra (0.21.0-1) unstable; urgency=high
 .
   * Team upload.
   * New upstream version
 Closes: #978032
   * Standards-Version: 4.5.1 (routine-update)
   * No tab in license text (routine-update)
   * watch file standard 4 (routine-update)
   * Build-Depends: python3-appdirs, python3-httpx, python3-pydantic,
 python3-rich
   * Versioned Build-Depends: python3-swiglpk (>= 4.65.1)
Checksums-Sha1:
 a2de878a4f4a5669140dbaebffdb8586b383e5ce 3071 python-cobra_0.21.0-1.dsc
 fec54b33c1b20d8555fea158b8b82ac3034a655e 2572526 
python-cobra_0.21.0.orig.tar.gz
 03c8ab7e324f8f0849a7a837674090e26574eff1 8964 
python-cobra_0.21.0-1.debian.tar.xz
 c093a1b245b2f2935ce308f908cc6ddfe58299da 10236 
python-cobra_0.21.0-1_amd64.buildinfo
Checksums-Sha256:
 c4868e13282b203337e944a80137c3d50b567195e56dcbda0d32201b5ff2b330 3071 
python-cobra_0.21.0-1.dsc
 fa67f720f2c15b99869b75d5344e6754631ed28b6337b0b11da3e5fa9a9c65ae 2572526 
python-cobra_0.21.0.orig.tar.gz
 24c0e447bf5e758f0c482f793544fdff97d712aa21f79c907e7fa20665d3ba65 8964 
python-cobra_0.21.0-1.debian.tar.xz
 89f985b422509934c3912c39d0ae8d90f0678dbe6c02855150a91b3027f0b62b 10236 
python-cobra_0.21.0-1_amd64.buildinfo
Files:
 5d23eae9ae68fc039890bcc87c1ab4b5 3071 python optional python-cobra_0.21.0-1.dsc
 d5b048d09fbd42a58d6b05f617b33021 2572526 python optional 
python-cobra_0.21.0.orig.tar.gz
 ed5755d5d78308a980adb37778cae69b 8964 python optional 
python-cobra_0.21.0-1.debian.tar.xz
 8ebfe6b85f466ea917d4bc9b825b1704 10236 python optional 
python-cobra_0.21.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmAiQt8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFtsg/9GvHCXuZptKN9eWZ0ZLpJ4E+deG9aRHNc
ElqBu8eueIH1/PDiydYSyxBzmt3Wv/XG6Yuap+37Nt263hlSi3/sVqu3Nfs150HW
UIO2WzIZZmLlAeUk3+rN8QIjACFYEnsAnmkYaWjLmkatrpej264B3/OGLFEzpKPB
ZoHEGne1bXnIZDNRx4jqz64N8SBcBTY3Gn4RGSxxaZ9Lljf+gWec4uv6ld9dFkcd
jCdjMy7cdU1JsvtgHYmZF8moWusheROtpLp0CAUb+GpNWnps1Rt6MsnnB8H34ztR
CB202ecfJAQuSE7M07SJBmqcLau04Bt2qYZXip7FdiblW7lYbxNVfS7BmJF+QnD1
MXOGbEEvRiHQSPR3v