Bug#990436: librust-cargo-dev: please use a versioned dependency for librust-flate2-1+{default,zlib}-dev

[Andreas Beckmann]

Package: librust-cargo-dev
Version: 0.43.1-3
Severity: serious
Tags: patch

librust-cargo-dev depends on librust-flate2-1+default-dev and
librust-flate2-1+zlib-dev which are (versioned) virtual packages
provided by librust-flate2+zlib-dev in buster and by
librust-flate2+rust-backend-dev and librust-flate2+libz-sys-dev
in bullseye. apt-get has problems exchanging these two packages during an
upgrade from buster to bullseye and prefers to keep the already installed
provider installed. This can be fixed by making the dependency versioned
s.t. the old provider from buster is no longer considered as a valid
solution.


Andreas
diff -Nru rust-cargo-0.43.1/debian/changelog rust-cargo-0.43.1/debian/changelog
--- rust-cargo-0.43.1/debian/changelog  2020-12-07 06:19:36.0 +0100
+++ rust-cargo-0.43.1/debian/changelog  2021-06-28 14:13:18.0 +0200
@@ -1,3 +1,14 @@
+rust-cargo (0.43.1-4) UNRELEASED; urgency=medium
+
+  * librust-cargo-dev: Bump the dependency version on the virtual packages
+librust-flate2-1+default-dev and librust-flate2-1+zlib-dev for smoother
+upgrades from buster which need to switch the provider from
+librust-flate2+zlib-dev to librust-flate2+rust-backend-dev and
+librust-flate2+libz-sys-dev.  (Closes: #-1)
+  * Bump the version in the Build-Depends for consistency.
+
+ -- Andreas Beckmann   Mon, 28 Jun 2021 14:13:18 +0200
+
 rust-cargo (0.43.1-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru rust-cargo-0.43.1/debian/control rust-cargo-0.43.1/debian/control
--- rust-cargo-0.43.1/debian/control2020-12-07 06:19:36.0 +0100
+++ rust-cargo-0.43.1/debian/control2021-06-28 14:13:12.0 +0200
@@ -21,8 +21,8 @@
  librust-curl-sys-0.4+default-dev (>= 0.4.22-~~) ,
  librust-env-logger-0.7+default-dev ,
  librust-filetime-0.2+default-dev ,
- librust-flate2-1+default-dev (>= 1.0.3-~~) ,
- librust-flate2-1+zlib-dev (>= 1.0.3-~~) ,
+ librust-flate2-1+default-dev (>= 1.0.13-~~) ,
+ librust-flate2-1+zlib-dev (>= 1.0.13-~~) ,
  librust-fs2-0.4+default-dev ,
  librust-fwdansi-1+default-dev ,
  librust-git2-0.13+default-dev (>= 0.13.11-~~) ,
@@ -109,8 +109,8 @@
  librust-curl-sys-0.4+default-dev (>= 0.4.22-~~),
  librust-env-logger-0.7+default-dev,
  librust-filetime-0.2+default-dev,
- librust-flate2-1+default-dev (>= 1.0.3-~~),
- librust-flate2-1+zlib-dev (>= 1.0.3-~~),
+ librust-flate2-1+default-dev (>= 1.0.13-~~),
+ librust-flate2-1+zlib-dev (>= 1.0.13-~~),
  librust-fs2-0.4+default-dev,
  librust-fwdansi-1+default-dev,
  librust-git2-0.13+default-dev (>= 0.13.11-~~),

Processed: tagging 951647

[Debian Bug Tracking System]

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

> tags 951647 - pending
Bug #951647 [libmstch-dev] libmstch-dev: Library configuration is misplaced
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#987936: libstorj: fails to build from the source

[Adrian Bunk]

On Sat, May 15, 2021 at 05:05:26AM +0100, Philip Wyett wrote:
>...
> --- libstorj-1.0.3/debian/libstorj0.symbols   2018-12-30 17:48:58.0 
> +
> +++ libstorj-1.0.3/debian/libstorj0.symbols   2021-05-15 04:38:45.0 
> +0100
> @@ -28,7 +28,6 @@
>   mnemonic_generate_indexes@Base 1.0.2
>   mnemonic_to_seed@Base 1.0.2
>   mnemonic_wordlist@Base 1.0.2
> - pbkdf2_hmac_sha512@Base 1.0.2
>   print_int_array@Base 1.0.2
>   put_shard@Base 1.0.2
>   random_buffer@Base 1.0.2
>...

This is an ABI break from the version in buster.

Correct would be instead something like (untested):

Removal from the header is fine, but libstorj-dev should get a runtime 
dependency on new enough nettle-dev (not the one in buster).

In src/crypto.c, instead of
  #ifndef pbkdf2_hmac_sha512
do an
  #undef pbkdf2_hmac_sha512
This would still build the function into the library for legacy users 
compiled against the buster version of the library.

cu
Adrian

Bug#988717: marked as done (lxml: triggers lintian autoreject tag 'license-problem-md5sum-non-free-file')

[Debian Bug Tracking System]

Your message dated Mon, 28 Jun 2021 20:33:30 +
with message-id 
and subject line Bug#988717: fixed in lxml 4.6.3+dfsg-0.1
has caused the Debian Bug report #988717,
regarding lxml: triggers lintian autoreject tag 
'license-problem-md5sum-non-free-file'
to be marked as done.

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

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


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

Hi,

your package triggers a non-overridable lintian autoreject tag, i.e.
if the package would be reuploaded today without changes, it would be
automatically rejected by ftp-master.

https://lintian.debian.org/tags/license-problem-md5sum-non-free-file
https://lintian.debian.org/sources/lxml

E license-problem-md5sum-non-free-file doc/html/flattr-badge-large.png usual 
name is badge-93x20.png. Could not be modified (variant from 
https://github.com/balupton/flattr-buttons.git) See also 
http://developers.flattr.net/api/policy/.


Andreas
--- End Message ---
--- Begin Message ---
Source: lxml
Source-Version: 4.6.3+dfsg-0.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated lxml 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, 26 Jun 2021 19:40:37 +0200
Source: lxml
Architecture: source
Version: 4.6.3+dfsg-0.1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Paul Gevers 
Closes: 799334 988717
Changes:
 lxml (4.6.3+dfsg-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Repack upstream to drop non-free and unused file (Closes: #988717)
   * Build and ship documentation (Closes: #799334)
Checksums-Sha1:
 b749909d96c76a1642a5f1a67366dce0443bb762 1839 lxml_4.6.3+dfsg-0.1.dsc
 32b81a3d8546521bc6d209a8028bf9f5d927411e 940222 lxml_4.6.3+dfsg.orig.tar.gz
 ad62e174806e9abb5df4287867af5b4928eb5ffa 7692 lxml_4.6.3+dfsg-0.1.debian.tar.xz
Checksums-Sha256:
 9fc2b8c9f6f360d170572c85b03e14e341e6350c3e1cb9225db3cda6a93be551 1839 
lxml_4.6.3+dfsg-0.1.dsc
 aa386ddf45ccc40975f33d29e285b6656273254ed797dd87d6283090f5d62036 940222 
lxml_4.6.3+dfsg.orig.tar.gz
 b2d0c2b73e8749ace7519111a1ec9c82788293facb7ed79bb5b64ada4f6fd52e 7692 
lxml_4.6.3+dfsg-0.1.debian.tar.xz
Files:
 f80c6371a720d8c9d308ce63b749fcef 1839 python optional lxml_4.6.3+dfsg-0.1.dsc
 6c55a1d15abe4da09a9f97f8abf5e908 940222 python optional 
lxml_4.6.3+dfsg.orig.tar.gz
 3866e7b83f0096043e429367c87caedd 7692 python optional 
lxml_4.6.3+dfsg-0.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmDXgSIACgkQnFyZ6wW9
dQrR9Af/eBwUEXlcqLeMAakrP/69f2mspYRpMYMLf8jZ/fnrZ+CiHN0I4Hf6TXgu
O6dmEKNXk8SOps9NhJse8F6JyEDEFQ4uWUoUDHVFKTYPHbuNvR9b7ZnF02Pg4hv9
J4bK9GlEHt8A7nCPTFkUqNPqO99avF6aGlxAZyLJk8ss2nrKIRJfE4rulPTf06E5
95nBNewa1H65FqwW76TEnzf9RX+JxSD+WKh8Kf6kowH2c7az8ZRwIRqlvELM4GBT
U2j0Ar1lDGTsPyLanGKtT8gT8O9jRVN4tDMFMsIFeS2GK97dgzUt+Vu1j4QcK/Yx
buS2XVBdTUu5uxSy9XqSjWgo7NGdrA==
=M7t6
-END PGP SIGNATURE End Message ---

Bug#990340: glances: contains prebuilt javascript without source

[Pirate Praveen]

On Sat, 26 Jun 2021 07:51:18 +0200 Johannes Schauer Marin Rodrigues 
 wrote:
> Package: glances
> Version: 3.1.5-1
> Severity: serious
> Justification: Policy 2.2.1
> 
> Hi,
> 
> the source package contains:
> 
> glances/outputs/static/public/glances.js
> glances/outputs/static/public/glances.map.js
> 
> these files are copied into the binary package as:
> 
> /usr/lib/python3/dist-packages/glances/outputs/static/public/glances.js
> /usr/lib/python3/dist-packages/glances/outputs/static/public/glances.map.js
> 
> they trigger the following lintian errors:
> 
> E source-is-missing glances/outputs/static/public/glances.js line 52292 is 
> 44264 characters long (>512)
> E source-is-missing glances/outputs/static/public/glances.map.js line 2 is 
> 2631202 characters long (>512)
> 
> Don't distribute those files or build them from source.

It uses webpack to build.

https://github.com/nicolargo/glances/blob/develop/glances/outputs/static/package.json#L28

cd glances/outputs/static && webpack 

in debian/rules with required build dependencies added should work. Most build 
dependencies are already packaged.
-- 
Sent from my p≡p for Android.

Processed: tagging 981997

[Debian Bug Tracking System]

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

> tags 981997 + bookworm sid
Bug #981997 [gudev-sharp-1.0] Conflicting monodoc-gudev-manual binary built 
also by Package: gudev-sharp-3.0
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Processed: tagging 990419

[Debian Bug Tracking System]

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

> tags 990419 + upstream
Bug #990419 [puppetdb] CVE-2021-27021
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#990419: CVE-2021-27021

[Moritz Muehlenhoff]

Package: puppetdb
Version: 6.2.0-5
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

See https://puppet.com/security/cve/cve-2021-27021/

Fixed by 
https://github.com/puppetlabs/puppetdb/commit/c146e624d230f7410fb648d58ae28c0e3cd457a2
https://github.com/puppetlabs/puppetdb/commit/f8dc81678cf347739838e42cc1c426d96406c266
https://github.com/puppetlabs/puppetdb/commit/72bd137511487643a3a6236ad9e72a5dd4a6fadb

Cheers,
 Moritz

Bug#990417: openjdk-11-jre-headless: running java in qemu s390 gives a SIGILL at C [linux-vdso64.so.1+0x6f8] __kernel_getcpu+0x8

[Arne Plöse]

Package: openjdk-11-jre-headless
Version: 11.0.11+9-1~deb10u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I tried tu run java in an qemu emulated s390 debian VM.
The bug accects also unstabel and te openjdk versions 15, 16 and 17, but not 
version 1.8

The outcome is a hs_err_pid632.log.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGILL (0x4) at pc=0x03ff88c7e6f4, pid=587, tid=588
#
# JRE version:  (11.0.11+9) (build )
# Java VM: OpenJDK 64-Bit Server VM (11.0.11+9-post-Debian-1deb10u1, mixed 
mode, sharing, tiered, compressed oops, g1 gc, linux-s390x)
# Problematic frame:
# C  [linux-vdso64.so.1+0x6f8]  __kernel_getcpu+0x8
#
# No core dump will be written. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
#
#

---  S U M M A R Y 

Command Line: 

Host: 2964, 2 cores, 1G, Debian GNU/Linux 10 (buster)
Time: Mon Jun 28 19:13:29 2021 CEST elapsed time: 0.099756 seconds (0d 0h 0m 0s)

---  T H R E A D  ---

Current thread is native thread

Stack: [0x03ff8748,0x03ff8758],  sp=0x03ff8757e940,  free 
space=1018k
Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, 
Vv=VM code, C=native code)
C  [linux-vdso64.so.1+0x6f8]  __kernel_getcpu+0x8


siginfo: si_signo: 4 (SIGILL), si_code: 5 (ILL_PRVOPC), si_addr: 
0x03ff88c7e6f4



-- System Information:
Debian Release: 10.10
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: s390x

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

Versions of packages openjdk-11-jre-headless depends on:
ii  ca-certificates-java  20190405
ii  java-common   0.71
ii  libasound21.1.8-1
ii  libc6 2.28-10
ii  libcups2  2.2.10-6+deb10u4
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3+deb10u2
ii  libgcc1   1:8.3.0-6
ii  libharfbuzz0b 2.3.1-1
ii  libjpeg62-turbo   1:1.5.2-2+deb10u1
ii  liblcms2-22.9-3
ii  libnss3   2:3.42.1-1+deb10u3
ii  libpcsclite1  1.8.24-1
ii  libstdc++68.3.0-6
ii  util-linux2.33.1-0.1
ii  zlib1g1:1.2.11.dfsg-1

openjdk-11-jre-headless recommends no packages.

Versions of packages openjdk-11-jre-headless suggests:
pn  fonts-dejavu-extra 
pn  fonts-indic
pn  fonts-ipafont-gothic   
pn  fonts-ipafont-mincho   
pn  fonts-wqy-microhei | fonts-wqy-zenhei  
pn  libnss-mdns

-- no debconf information

Bug#986709: dirvish is unmaintained since 2005, but still available in bullseye

[Dirk Heinrichs]

Hi,

given that dirvish is still available in bullseye, although it's
unmaintained for more than 16(!) years now, it really makes me wonder
why rsnapshot has been removed. Please add it back, it's removal doesn't
make any sense.

Bye...

    Dirk

-- 
Dirk Heinrichs 
GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de




OpenPGP_signature
Description: OpenPGP digital signature

Bug#990263: podman sets oom_score_adj to -1000 for processes inside the

[Hideki Yamane]

 container so the system breaks in OOM situations
Message-Id: <20210629000848.a3125fe89a9984a780074...@iijmio-mail.jp>
In-Reply-To: <502056d5848360369973f2c96882ff37ad42bb4f.ca...@doo.shop>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi,

On Thu, 24 Jun 2021 11:37:35 +0200 Max Bruckner  wrote:
> How to reproduce:
> 
> ```
> # podman run -it --rm debian sh
> # cat /proc/$$/oom_score_adj
> -1000
> ```

 Well, I've tested it too with bullseye on KVM and reproduced it, however,
 it's only under root privilege. Just run "$ podman run -it --rm debian sh"
 via normal user and it returns 0.

 And also tested with my daily driver unstable system I cannot reproduce it.
 (But sid on KVM can reproduce it, hmm...)


 It may be better to downgrade as important if it's only root privilege, IMO.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#990412: pam: PAM doesn't appear to be reading /lib/security

[Sam Hartman]

> "Rowan" == Rowan Wookey  writes:

Rowan> Fair enough, I couldn't find any docs on the policy of
Rowan> /lib/security or any news on it not being scanned in
Rowan> Bullseye, is there something about that somewhere?

I don't know.
I had mostly been not paying attention to PAM but it looked like Steve
was getting a bit behind and he accepted an offer of help.
So, I was not tracking when this change got made.
It may well be we should document this is release notes.

Bug#990412: pam: PAM doesn't appear to be reading /lib/security

[Rowan Wookey]

Fair enough, I couldn't find any docs on the policy of /lib/security or
any news on it not being scanned in Bullseye, is there something about
that somewhere?

On 28/06/2021 14:48, Sam Hartman wrote:
> control: reassign -1 libpam-yubico
> control: severity -1 grave
> control: retitle -1 pam_yubico fails to install module in multiarch path
> control: found -1 2.23-1
> 
>> "Rowan" == Rowan Wookey  writes:
> 
> Rowan> It appears that in Bullseye pam isn't checking /lib/security.
>   
>   
> Rowan> The libpam-yubico package installes a module in /lib/security
> Rowan> which when configured without an absolute path pam errors
> Rowan> with:
> 
> I think that's a bug in the other package.
> The issue is that /lib/security is not a multiarch path.
> And so I cannot have both an i386 and amd64 version of the module
> installed at the same time.
> By this point, we really ought to be supporting multiarch.
> 
> I'm happy to add breaks relationships in pam on broken modules that
> don't provide multiarch paths,
> but I'd consider this a grave bug on a module that only installs in
> /lib/security at this point.
> 

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 989603 2.8.1+dfsg1-1
Bug #989603 {Done: Hideki Yamane } 
[ocsinventory-server] ocsinventory-server: Does not start after install
Marked as fixed in versions ocsinventory-server/2.8.1+dfsg1-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#990412: pam: PAM doesn't appear to be reading /lib/security

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libpam-yubico
Bug #990412 [libpam-yubico] pam_yubico fails to install module in multiarch path
Ignoring request to reassign bug #990412 to the same package
> severity -1 grave
Bug #990412 [libpam-yubico] pam_yubico fails to install module in multiarch path
Ignoring request to change severity of Bug 990412 to the same value.
> retitle -1 pam_yubico fails to install module in multiarch path
Bug #990412 [libpam-yubico] pam_yubico fails to install module in multiarch path
Ignoring request to change the title of bug#990412 to the same title
> found -1 2.23-1
Bug #990412 [libpam-yubico] pam_yubico fails to install module in multiarch path
Ignoring request to alter found versions of bug #990412 to the same values 
previously set

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

Bug#990412: pam: PAM doesn't appear to be reading /lib/security

[Sam Hartman]

control: reassign -1 libpam-yubico
control: severity -1 grave
control: retitle -1 pam_yubico fails to install module in multiarch path
control: found -1 2.23-1

> "Rowan" == Rowan Wookey  writes:

Rowan> It appears that in Bullseye pam isn't checking /lib/security.


Rowan> The libpam-yubico package installes a module in /lib/security
Rowan> which when configured without an absolute path pam errors
Rowan> with:

I think that's a bug in the other package.
The issue is that /lib/security is not a multiarch path.
And so I cannot have both an i386 and amd64 version of the module
installed at the same time.
By this point, we really ought to be supporting multiarch.

I'm happy to add breaks relationships in pam on broken modules that
don't provide multiarch paths,
but I'd consider this a grave bug on a module that only installs in
/lib/security at this point.


signature.asc
Description: PGP signature

Processed: Re: Bug#990412: pam: PAM doesn't appear to be reading /lib/security

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libpam-yubico
Bug #990412 [src:pam] pam: PAM doesn't appear to be reading /lib/security
Bug reassigned from package 'src:pam' to 'libpam-yubico'.
No longer marked as found in versions pam/1.4.0-7.
Ignoring request to alter fixed versions of bug #990412 to the same values 
previously set
> severity -1 grave
Bug #990412 [libpam-yubico] pam: PAM doesn't appear to be reading /lib/security
Severity set to 'grave' from 'important'
> retitle -1 pam_yubico fails to install module in multiarch path
Bug #990412 [libpam-yubico] pam: PAM doesn't appear to be reading /lib/security
Changed Bug title to 'pam_yubico fails to install module in multiarch path' 
from 'pam: PAM doesn't appear to be reading /lib/security'.
> found -1 2.23-1
Bug #990412 [libpam-yubico] pam_yubico fails to install module in multiarch path
Marked as found in versions yubico-pam/2.23-1.

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

Bug#982794: firefox-esr: illegal instruction in libxul.so on armhf

[Hideki Yamane]

Hi,

On Sun, 14 Feb 2021 14:12:17 + Vincent Arkesteijn  
wrote:
> Firefox is killed with SIGILL shortly after startup:
> $ firefox-esr -safe-mode
> Illegal instruction

 Can you reproduce it on freshly installed bullseye sytem?

> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: armhf (armv7l)

 However,

> Kernel: Linux 3.5.7-14-ARCH (PREEMPT)

 It seems that is not the kernel bullseye provides.


 And it maybe help to provide its hardware information, too.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#934713: os-prober: missing dependency on mount

[Hideki Yamane]

control: tags -1 +patch

On Thu, 15 Aug 2019 16:49:46 +0200 Johannes Schauer  wrote:
> > > https://lists.debian.org/20170726081846.ga22...@fatal.se
> > 
> > Well, debian-devel@ isn't where one files bug reports against packages that
> > suddenly need a dependency?
> 
> I was not trying to justify or excuse the omission of the src:util-linux
> maintainers. I can only imagine that os-prober somehow slipped through the
> cracks when the src:util-linux maintainers filed bugs against all packages 
> that
> need the mount utilities during the buster release cycle.
> 
> I agree that the situation now is unfortunate but I only reported this problem
> once I stumbled across it. I was not involved in the decision two years ago.

 Anyway, here's a tiny MR
 https://salsa.debian.org/installer-team/os-prober/-/merge_requests/9


 If it would be a wrong way to deal with this bug, then close above MR
 and remove Tags: patch, please. If not - just merge it and push the package :D


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Processed: Re: Bug#934713: os-prober: missing dependency on mount

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #934713 [os-prober] os-prober: missing dependency on mount
Added tag(s) patch.

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

Bug#883194: marked as done (please convert mountstats and nfsiostat scripts to Python3)

[Debian Bug Tracking System]

Your message dated Mon, 28 Jun 2021 12:48:22 +
with message-id 
and subject line Bug#883194: fixed in nfs-utils 1:1.3.4-6
has caused the Debian Bug report #883194,
regarding please convert mountstats and nfsiostat scripts to Python3
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.)


-- 
883194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-utils
Version: 1:1.3.4-2.1
User: debian-pyt...@lists.debian.org
Usertags: py2-removal

the changelog reads:

- nfs-common: Add Recommends python for mountstats and nfsiostat

Please convert these scripts to python3, and recommend Python3 instead.
--- End Message ---
--- Begin Message ---
Source: nfs-utils
Source-Version: 1:1.3.4-6
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated nfs-utils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 28 Jun 2021 09:15:06 +0200
Source: nfs-utils
Architecture: source
Version: 1:1.3.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team 
Changed-By: Salvatore Bonaccorso 
Closes: 513284 883194
Changes:
 nfs-utils (1:1.3.4-6) unstable; urgency=medium
 .
   * mountstats:  Remove a shebang
   * Convert remaining python scripts to python3 (Closes: #883194)
   * debian/control: Switch Recommends from python to python3
   * Removed a resource leak from mountd/fsloc.c (Closes: #513284)
Checksums-Sha1: 
 8759ddc36fdd19b506bf41a25e4935048542ec14 2448 nfs-utils_1.3.4-6.dsc
 394ed54e18da92b693e3a1e260d68657d8883f33 52140 nfs-utils_1.3.4-6.debian.tar.xz
Checksums-Sha256: 
 7ccd4817343cf069bef73f38e9f487db278c6c27ad5ff9538cccf967ad0ea06f 2448 
nfs-utils_1.3.4-6.dsc
 015bd80fbe41497d1db8b021085f23ba3f7b49a0d47d168861e387221624196b 52140 
nfs-utils_1.3.4-6.debian.tar.xz
Files: 
 27713db4ec307476975d93f7d7ad2996 2448 net optional nfs-utils_1.3.4-6.dsc
 06302be9388b60cd77536c77e4e57a33 52140 net optional 
nfs-utils_1.3.4-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmDZwUBfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EoVMQAKFSs/+RaqpNb49UIc8Y5QqjKRlCN9VD
R9RZLgbFPSOCFbUqViIqyTtmrj9HK1k0yO2tDr1yowY9WXSgIgrpUnHQE9vuSYum
RdL1hDGOcgZai4TqI07HLp0vnUAN1aUpYPSOsiSb6uG/Ve4zaKxrxrJ7Q3Bsw6Dr
BtnKNebdFV1Rrj8xx4Q0C3jMJL4Zq8JHA4/yHf8Hpq68Sg2ndiU68nZo3tZQ/MVI
fv4ups7I9IDB0Dbza7Zzx5Y/Df1c4wumV76q+n6+9e5J8RWA3WRQkqG94SwKDVyV
dX5XLehMvJHTQnqfhDdIfc9nrDL4U5nEHXXy0sdBn7OH77tr0v3aI/rQBSRvjfLU
PeVfRWiScu1wZppCq5f6/WlGXPP3HL8NCqJfkmEZyz6Sd6VPibKh3UToy/Fc3d9I
HOGTAZcbDUDjsDXm720XAvklFIw6Ge6WvYcU6+UWq8s+5J399ZEyzMkkxymKDwlm
f9paELM9N+mfnqBFXAWGhJgbvpRN8MzPYlwIl3bLhqA4MvkTMvQuhfGmXe2CIu+W
na+C9LDu6MjtD2sFUhxSmBlyA4Qhs8PWxNT+3o1aGCFL+sSSuG8f4uEstQS45+2a
6LsgbXZ0qkReHwAuyqlAVm9PJCBFblWbZA7zUnggKOZk+hlPjrcIa0AGlfGZfK4a
gPXCiIZ3owRk
=iB9t
-END PGP SIGNATURE End Message ---

Bug#990409: ca-cacert: should this package be removed?

[Timo Röhling]

Package: ca-cacert
Version: 2019.0411-2
Severity: serious
User: debian...@lists.debian.org
Usertags: proposed-removal

Hi,

CAcert is pretty much made obsolete by LetsEncrypt, and unlike
LetsEncrypt, it has never been part of the Mozilla truststore.
Furthermore, the ca-cacert package has become virtually useless with
the expiry of the shipped intermediate certificate [1], and not even
CAcert seems to bother enough to link the newly generated
certificate from their official website [2].

Therefore, I believe it is time to acknowledge the facts and remove
the package from Debian altogether.

Cheers
Timo


[1] https://bugs.debian.org/988512
[2] http://www.cacert.org/index.php?id=3


--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

Bug#988358: marked as done (bucardo: please use versioned Depends: libpod-parser-perl (>= 1.63))

[Debian Bug Tracking System]

Your message dated Mon, 28 Jun 2021 11:33:26 +
with message-id 
and subject line Bug#988358: fixed in bucardo 5.6.0-3
has caused the Debian Bug report #988358,
regarding bucardo: please use versioned Depends: libpod-parser-perl (>= 1.63)
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.)


-- 
988358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bucardo
Version: 5.6.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: clone -1 -2 -3
Control: reassign -2 latexml 0.8.5-2
Control: retitle -2 latexml: please use versioned Depends: libpod-parser-perl 
(>= 1.63)
Control: reassign -3 pod2pdf 0.42-5.1
Control: retitle -3 pod2pdf: please use versioned Depends: libpod-parser-perl 
(>= 1.63)

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster' if perl-modules-5.24 from stretch is still installed.

perl-modules-5.24 provided an unversioned virtual libpod-parser-perl
and apt tries to use the installed package (instead of installing a new
package) to satisfy the new dependency of bucardo, while
perl-modules-5.24 needs to get removed due to Breaks in new perl.
(The versioned virtual libpod-parser-perl (= 1.63) in perl/buster is
probably not considered a candidate since perl with its high score was
decided for being upgraded earlier.)

Making the dependency versioned excludes the unversioned virtual package
from being considered a candidate. I tested this with bucardo, and assume
that it will work the same way for the other two packages showing the
same problem.

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

  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) perl:amd64 < 5.28.1-6+deb10u1 -> 5.32.1-4 @ii umU Ib >
  Broken perl:amd64 Breaks on perl-modules-5.24:amd64 < 5.24.1-3+deb9u7 @ii mK >
Considering perl-modules-5.24:amd64 -2 as a solution to perl:amd64 16
Added perl-modules-5.24:amd64 to the remove list
Fixing perl:amd64 via remove of perl-modules-5.24:amd64
  Investigating (0) bucardo:amd64 < 5.5.0-1 -> 5.6.0-2 @ii umU Ib >
  Broken bucardo:amd64 Depends on libpod-parser-perl:amd64 < none | 1.63-2 @un 
uH >
Considering libpod-parser-perl:amd64 1 as a solution to bucardo:amd64 0
Holding Back bucardo:amd64 rather than change libpod-parser-perl:amd64
  Investigating (0) libperl5.24:amd64 < 5.24.1-3+deb9u7 @ii gK Ib >
  Broken libperl5.24:amd64 Depends on perl-modules-5.24:amd64 < 5.24.1-3+deb9u7 
@ii mR > (>= 5.24.1-3+deb9u7)
Considering perl-modules-5.24:amd64 -2 as a solution to libperl5.24:amd64 -2
Removing libperl5.24:amd64 rather than change perl-modules-5.24:amd64
  Investigating (1) perl-base:amd64 < 5.28.1-6+deb10u1 -> 5.32.1-4 @ii umU Ib >
  Broken perl-base:amd64 Breaks on bucardo:amd64 < 5.5.0-1 | 5.6.0-2 @ii umH > 
(< 5.5.0-1.1)
Considering bucardo:amd64 0 as a solution to perl-base:amd64 5238
Upgrading bucardo:amd64 due to Breaks field in perl-base:amd64
  Investigating (1) bucardo:amd64 < 5.5.0-1 -> 5.6.0-2 @ii umU Ib >
  Broken bucardo:amd64 Depends on libpod-parser-perl:amd64 < none | 1.63-2 @un 
uH >
Considering libpod-parser-perl:amd64 1 as a solution to bucardo:amd64 0
Holding Back bucardo:amd64 rather than change libpod-parser-perl:amd64
  Investigating (2) perl-base:amd64 < 5.28.1-6+deb10u1 -> 5.32.1-4 @ii umU Ib >
  Broken perl-base:amd64 Breaks on bucardo:amd64 < 5.5.0-1 | 5.6.0-2 @ii umH > 
(< 5.5.0-1.1)
Considering bucardo:amd64 0 as a solution to perl-base:amd64 5238
Upgrading bucardo:amd64 due to Breaks field in perl-base:amd64
  Investigating (2) bucardo:amd64 < 5.5.0-1 -> 5.6.0-2 @ii umU Ib >
  Broken bucardo:amd64 Depends on libpod-parser-perl:amd64 < none | 1.63-2 @un 
uH >
Considering libpod-parser-perl:amd64 1 as a solution to bucardo:amd64 0
Holding Back bucardo:amd64 rather than change libpod-parser-perl:amd64
  Investigating (3) perl-base:amd64 < 5.28.1-6+deb10u1 -> 5.32.1-4 @ii umU Ib >
  Broken perl-base:amd64 Breaks on bucardo:amd64 < 5.5.0-1 | 5.6.0-2 @ii umH > 
(< 5.5.0-1.1)
Considering bucardo:amd64 0 as a solution to perl-base:amd64 5238
qUpgrading bucardo:amd64 due to Breaks field in perl-base:amd64
  Investigating (3) bucardo:amd64 < 5.5.0-1 -> 5.6.0-2 @ii umU Ib >
  Broken bucardo:amd64 Depends on libpod-parser-perl:amd64 < none | 1.63-2 @un 
uH >
Considering libpod-parser-perl:amd64 1 as a solution to bucardo:amd64 0
Holding Back bucardo:amd64 rather than change libpod-parser-perl:amd64
  Investigating (4) perl-base:amd64 < 

Processed: Bug#988358 marked as pending in bucardo

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #988358 [bucardo] bucardo: please use versioned Depends: libpod-parser-perl 
(>= 1.63)
Ignoring request to alter tags of bug #988358 to the same tags previously set

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

Processed: Bug#988358 marked as pending in bucardo

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #988358 [bucardo] bucardo: please use versioned Depends: libpod-parser-perl 
(>= 1.63)
Added tag(s) pending.

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

Bug#988358: marked as pending in bucardo

[Michael Meskes]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/postgresql/bucardo/-/commit/50a1a28940ec521f5b2c5d26485bee1badd04b80


Merge branch 'master' into 'master'

Fix upgrade failure with perl-modules-5.24 from stretch is still installed 
(Closes: #988358)

See merge request postgresql/bucardo!2


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/988358

Bug#988358: marked as pending in bucardo

[Michael Meskes]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/postgresql/bucardo/-/commit/8a7159e2870231d238d20188cfb920ce3ca032ef


Fix upgrade failure with perl-modules-5.24 from stretch is still installed 
(Closes: #988358)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/988358

Bug#985932: openstack-trove should not be included in Bullseye

[Michal Arbet]

Hi,

Totally agree with your opinion.

Cheers
Michal Arbet
Openstack Engineer

Ultimum Technologies a.s.
Na Poříčí 1047/26, 11000 Praha 1
Czech Republic

+420 604 228 897
michal.ar...@ultimum.io
*https://ultimum.io *

LinkedIn  | Twitter
 | Facebook



pá 26. 3. 2021 v 12:15 odesílatel Thomas Goirand  napsal:

> Package: openstack-trove
> Version: 1:13.0.0-1
> Severity: serious
>
> Hi,
>
> I never really tried Trove myself, and therefore, I would prefer if it was
> not
> part of Bullseye. It will still be available from the unofficial repository
> of OpenStack (osbpo.debian.net, accessible with extrepo).
>
> Cheers,
>
> Thomas Goirand (zigo)
>
>