Bug#929165: How to use rm_conffile to remove files that contain empty " ", comma "," and wildcard "*"?

[Andreas Metzler]

On 2021-03-07 Hideki Yamane  wrote:
> X-debbugs-CC: debian-de...@lists.debian.org
>  I've tried to remove files that was accidentally containts empty " ",
>  comma "," and wildcard "*" via rm_conffile from dpkg-maintscript-helper.

>  However, it returns an error like below.

> > dh_installdeb: error: The current conffile path for rm_conffile must be 
> > present and absolute, got 
> > '/etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg,

>  I've specified it like below.

> > # cat debian/ubuntu-dbgsym-keyring.maintscript
> > rm_conffile '/etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg, *'
[...]
>  How to use rm_conffile to remove such files that contains empty, comma
>  and * in its filenames?

Hello,

I think that might be a dh_installdeb error, it seems to check whether
the first character is a '/', and does not account for possible quoting
characters.

This might work around this
rm_conffile /etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg,\ \*

BTW you should really specify [prior-version and [package].

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#846950: Merge request for nfs-utils to fix bugs #846950, #849942, #849608

[Salvatore Bonaccorso]

Hi Felix,

On Sat, Mar 06, 2021 at 11:26:36PM -0800, Felix Lechner wrote:
> Hi Salvatore,
> 
> On Sat, Mar 6, 2021 at 2:15 AM Joachim Falk  wrote:
> >
> > I have a merge request open on nfs-utils.
> 
> I would like to second this request, please. I filed (or patched) some
> of these bugs, but someone downgraded them from the RC level. They are
> on my list of open items for bullseye: I plan to potentially upgrade
> the severities again, after consulting with the release team. Your
> input would be much appreciated. Thanks!
> 
> Thank you, Joachim, for advancing these grave issues in a helpful way!

Can you check which ones the release team accepts as potentially to be
be fixed at this stage of the release, and then we really can aim to
take those.

nfs-utils is very in a bad shape in Debian, and the aim is now to
quickly after the bullseye release try to catch up finally with
upstream (once this is done the task is more easy, but the amount of
divergence now made it impossible to fnish up
https://salsa.debian.org/kernel-team/nfs-utils/-/merge_requests/3).
And the more Debian specific changes we apply the harder it becomes.

The latter really needs to be done, we have already too much breakage,
but it is not possibe for bullseye.

As it is maintainer under Debian kernel-team maintenance I really
would like to see that happen.

Salvatore

Bug#973927: please close as duplicate of #947425

[Schplurtz le déboulonné]

Hi,

This bug is a duplicate of bug #947425 and should be closed.

By the way Willi Mann's diff solved this issue.

Bug#849608: Bug#846950: Merge request for nfs-utils to fix bugs #846950, #849942, #849608

[Felix Lechner]

Hi Salvatore,

On Sat, Mar 6, 2021 at 2:15 AM Joachim Falk  wrote:
>
> I have a merge request open on nfs-utils.

I would like to second this request, please. I filed (or patched) some
of these bugs, but someone downgraded them from the RC level. They are
on my list of open items for bullseye: I plan to potentially upgrade
the severities again, after consulting with the release team. Your
input would be much appreciated. Thanks!

Thank you, Joachim, for advancing these grave issues in a helpful way!

Kind regards
Felix Lechner

Bug#984560: NIS binary maps could be broken after upgrades, due to GDBM oddities

[McIntyre, Vincent (CASS, Marsfield)]

On Fri, Mar 05, 2021 at 09:51:34AM +0100, Francesco P. Lovergine wrote:

Thank you for the quick reply.
I agree with all your points and that there's little to be done but
document the issue. I'm happy for this to be closed.
If both buster & bullseye link with libgdbm6 then I agree
it's unlikely this issue will arise during upgrades.

I plan to send a wishlist patch for the nis.debian.howto,
or a new README.Debian file - hopefully that will be useful.
Do you prefer bugs+patches or PRs?

Kind regards
Vince

Bug#984689: ruby-vcr: DFSG violation (Hippocratic license)

[TANIGUCHI Takaki]

Package: ruby-vcr
Version: 6.0.0-2
Severity: serious

Dear Maintainer,

ruby-vcr license has been changed to The Hippocaratic License since
versoin 5.1. I think it is not DFSG compliant.

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

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

-- no debconf information

Bug#589913: dput: Support Ubuntu-style “host argument” parameter

[Paul Wise]

On Wed, 28 Dec 2016 23:22:12 +1100 Ben Finney wrote:

> Support for a specific non-Debian archive structure should not be a
> part of Debian's ‘dput’.

dput is a package used by folks from many different distros, including
Debian, Ubuntu, many other derivatives and probably some private
archives for specific companies. The audience for it is much wider than
just members of the Debian Project, so it seems reasonable for it to
meet the needs of the entire audience instead of just Debian folks.

> While I can understand the desire for this, it is not compelling
> enough to add functionality to a Debian-native tool for archives that
> are not standard to Debian.

There has been talk of adding secondary archives to Debian too (aka
bikesheds), so probably this argument mechanism will be useful for
Debian itself at some point.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#984688: folder.c: add "folder.h" for prototypes

[Bjarni Ingi Gislason]

Source: nn
Version: 6.7.3-14
Severity: normal
Tags: patch

Dear Maintainer,

>From 150bf8643922f310cb945f0e1b3d2350a6dcac75 Mon Sep 17 00:00:00 2001
>From: Bjarni Ingi Gislason 
>Date: Sun, 7 Mar 2021 05:14:17 +
>Subject: [PATCH] folder.c: add "folder.h" for prototypes

  Add "folder.h" for missing prototypes.

  Comment out prototype for "getpwnam()" as it is included in ".

Signed-off-by: Bjarni Ingi Gislason 
---
 folder.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/folder.c b/folder.c
index a50be28..1a095be 100644
--- a/folder.c
+++ b/folder.c
@@ -16,6 +16,7 @@
 #include "db.h"
 #include "digest.h"
 #include "dir.h"
+#include "folder.h"
 #include "match.h"
 #include "menu.h"
 #include "pack_date.h"
@@ -53,7 +54,7 @@ int ignore_fancy_select = 0;  /* turn off 
select features
 extern int  fmt_linenum;
 extern char*header_lines;
 
-extern struct passwd *getpwnam(const char *); /*  */
+/* extern struct passwd *getpwnam(const char *); */ /*  */
 
 /*
  * expand ~[user][/...] form
-- 
2.30.1



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

Kernel: Linux 5.10.9-1 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- debconf information excluded

-- 
Bjarni I. Gislason

Bug#984682: kodi: Kodi 19.0+dfsg1 PVR Recordings from vdr vnsi plugin all show the same recording date.

[Selaron]

Package: kodi
Version: 2:19.0+dfsg1-1
Severity: important
X-Debbugs-Cc: sela...@dismail.de

Dear Maintainer,



   * What led up to the situation?

Updating from kodi 17 to 19.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I updated from debian buster to bullseye.
Afterwards using kodi 19 all PVR recordings received via VNSI plugin from VDR
are shown with the same recording date and thus cannot be sorted by date.
Additionaly kodi does not remember the time to resume playback of recordings
when kodi is restarted.

Building kodi from source (apt source kodi) after reverting these patches helps
me in getting the correct recording times back:
debian/patches/cdatetime-std-chrono/0001-Replace-Kodi-date-time-implementation-
with-std-c.patch
debian/patches/cdatetime-std-chrono/0002-Use-Debian-tzdata.patch


But kodi does still not remember PVR recording playback position beyond
restarts.



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

Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 kodi depends on:
ii  kodi-bin   2:19.0+dfsg1-1
ii  kodi-data  2:19.0+dfsg1-1

Versions of packages kodi recommends:
ii  kodi-repository-kodi [kodi-repository]  2:19.0+dfsg1-1
ii  kodi-visualization-spectrum 3.4.0+ds1-2

kodi suggests no packages.

Additional packages:

ii  kodi-pvr-vdr-vnsi:amd64 8.2.2+ds1-1
amd64Kodi PVR Addon VDR VNSI
ii  vdr-plugin-vnsiserver   1:1.8.0-3
amd64VDR plugin to provide PVR backend services for Kodi
ii  vdr 2.4.1-4.1
amd64Video Disk Recorder for DVB cards

Bug#984620: fltk1.1: Please add a Wayland driver

[Aaron M. Ucko]

Guillem Jover  writes:

> Given that the X.Org server is apparently pretty much dead, that other
> distributions are also switching to Wayland and that most mainstream
> desktop environments now support this natively. It would be nice to
> have fltk support this too.

Hi, Guillem.

That's a fair request, but alas doesn't have a good formal home in
Debian at the moment -- I've been using a separate source package for
each upstream release series, and per the upstream report's feedback,
Wayland support won't be happening for the 1.3 branch (fltk1.3 source
package), let alone 1.1 (long dead upstream, to be belatedly retired
from Debian post-buster).  I expect it would be non-trivial to backport
even to 1.3.

I suppose I could construe this report as an RFP for fltk1.4, but that
code base hasn't yet either had an official upstream release or gained
Wayland support.

How would you like to proceed?

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

Bug#984472: e2fsprogs: resize2fs on inconsistent filesystem (in a way that e2fsck doesn't detect) completely corrupts MMP data (in a way e2fsck can't recover from)

[Theodore Ts'o]

On Fri, Mar 05, 2021 at 09:48:50PM -0500, Theodore Ts'o wrote:
> I can't reproduce the problem given your file system image.  Given
> your description, this is almost certainly operator error.

OK, I was finally able to reproduce the problem, but not using your
reproduction instructions.  I reproduced it via:

1.  e2image -r rbd13.e2i.qcow2 /tmp/rbd13
2.  truncate -s 10T /tmp/rbd13
3.  e2fsck -fy /tmp/rbd13
4.  resize2fs /tmp/rbd13
5.  e2fsck -fy /tmp/rbd13
  

The bug report was also incorrect by saying that resizing the file
system to 4T was sufficient; that is not true.  It can only be
reproduced by when a file system is resized sufficiently large that
there is no longer enough room to grow the block group descriptors
without moving the allocation bitmaps and/or inode table out of the
way in order to create room for the block group descriptors.  (As in
the above reproduction recipe.)

% e2image -r rbd13.e2i.qcow2 /tmp/rbd13
e2image 1.46.2 (28-Feb-2021)
% truncate -s 4T /tmp/rbd13
% resize2fs  /tmp/rbd13
resize2fs 1.46.2 (28-Feb-2021)
Please run 'e2fsck -f /tmp/rbd13' first.
% e2fsck -f /tmp/rbd13
e2fsck 1.46.2 (28-Feb-2021)
e2fsck: MMP: e2fsck being run while checking MMP block
MMP check failed: If you are sure the filesystem is not in use on any node, run:
'tune2fs -f -E clear_mmp /tmp/rbd13'
MMP_block:
mmp_magic: 0x4d4d50
mmp_check_interval: 10
mmp_sequence: e24d4d50
mmp_update_date: Sat Mar  6 22:47:25 2021
mmp_update_time: 1615088845
mmp_node_name: cwcc
mmp_device_name: /tmp/rbd13

/tmp/rbd13: ** WARNING: Filesystem still has errors **

This is a separate bug.  The issue here is that resize2fs is exiting
after printing the "Please run 'e2fsck -f /tmp/rbd13' first." without
cleanly stopping (resetting) the MMP protection.  And this doesn't
lead to file system corruption, as we can see here:

% tune2fs -f -E clear_mmp /tmp/rbd13
tune2fs 1.46.2 (28-Feb-2021)
% e2fsck -fy /tmp/rbd13
e2fsck 1.46.2 (28-Feb-2021)
Clearing orphaned inode 45617124 (uid=107, gid=115, mode=0100600, size=16777216)
Clearing orphaned inode 15073744 (uid=0, gid=0, mode=0100644, size=593696)
Clearing orphaned inode 15073743 (uid=0, gid=0, mode=0100644, size=3031904)
Clearing orphaned inode 50331709 (uid=0, gid=0, mode=0100644, size=149704)
Clearing orphaned inode 50332495 (uid=0, gid=0, mode=0100755, size=231560)
Clearing orphaned inode 50332319 (uid=0, gid=0, mode=0100644, size=2670992)
Clearing orphaned inode 50332271 (uid=0, gid=0, mode=0100644, size=651472)
Clearing orphaned inode 50332251 (uid=0, gid=0, mode=0100644, size=282752)
Clearing orphaned inode 13 (uid=0, gid=0, mode=0100600, size=0)
Pass 1: Checking inodes, blocks, and sizes
Inode 46530577 extent tree (at level 1) could be shorter.  Optimize? yes

Inode 46530714 extent tree (at level 1) could be shorter.  Optimize? yes

Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/tmp/rbd13: * FILE SYSTEM WAS MODIFIED *
/tmp/rbd13: 225913/67108864 files (8.6% non-contiguous), 185961407/268435456 
blocks


The workaround to the first bug is to clear the MMP feature, do the
offline resize, and then enable the MMP feature again.  Of course,
while the MMP feature you won't be protected by another node trying to
modify the file system.  But it will allow you to grow the file system.

Another workaround is to simply do an online resize (that is, on the
node where the file system is mounted, run resize2fs on the mounted
file system).  However, depending on the kernel version, it won't
allow you to resize past the limits of the reserved block group
descriptors reserved by the resize inode.

- Ted

Bug#929165: How to use rm_conffile to remove files that contain empty " ", comma "," and wildcard "*"?

[Hideki Yamane]

X-debbugs-CC: debian-de...@lists.debian.org

Hi,

 I've tried to remove files that was accidentally containts empty " ",
 comma "," and wildcard "*" via rm_conffile from dpkg-maintscript-helper.

 However, it returns an error like below.

> dh_installdeb: error: The current conffile path for rm_conffile must be 
> present and absolute, got 
> '/etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg,

 I've specified it like below.

> # cat debian/ubuntu-dbgsym-keyring.maintscript
> rm_conffile '/etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg, *'
> rm_conffile '/etc/apt/trusted.gpg.d/ubuntu-dbgsym-removed-keys.gpg, *'



 How to use rm_conffile to remove such files that contains empty, comma
 and * in its filenames?


-- 
Regards,

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

Bug#984687: menu.h: change prototype of "*menu" to "menu".

[Bjarni Ingi Gislason]

Source: nn
Version: 6.7.3-14
Severity: normal
Tags: patch

Dear Maintainer,

>From 68e8b0288efbc2af55740b196510b19aa06d0c83 Mon Sep 17 00:00:00 2001
>From: Bjarni Ingi Gislason 
>Date: Sun, 7 Mar 2021 03:19:46 +
>Subject: [PATCH] menu.h: change prototype of "*menu" to "menu".

Signed-off-by: Bjarni Ingi Gislason 
---
 menu.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/menu.h b/menu.h
index 7d3636d..69c5e34 100644
--- a/menu.h
+++ b/menu.h
@@ -62,7 +62,7 @@
 #define AC_UNCHANGED   6   /* no display changes */
 
 char   *pct(long, long, long, long);
-int*menu(fct_type_void);
+int menu(fct_type_void);
 article_header *get_menu_article(void);
 int alt_command(void);
 int prt_replies(int);
-- 
2.30.1



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

Kernel: Linux 5.10.9-1 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- debconf information excluded

-- 
Bjarni I. Gislason

Bug#984686: newlisp: Recommends multiple no more existing packages due to hardcoded ABI versions in library package names

[Axel Beckert]

Package: newlisp
Version: 10.7.5-1+b2
Severity: normal

Hi,

newlisp recommends libcrypto++6 and libmysqlclient18 which are both no
more available in Debian Unstable.

libcrypto++6 has been superseeded by libcrypto++8 and libmysqlclient18
by libmysqlclient21.

Please don't hardcode libraries with ABI versions as part of the package
name in debian/control so that they're automatically updated upon
rebuilds. Use e.g. dpkg-shlibdeps/dh_shlibdeps for that. See option -d
in dpkg-shlibdeps(1) for a hint on how to do that.

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

Kernel: Linux 5.10.0-4-amd64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages newlisp depends on:
ii  libc6 2.31-9
ii  libffi7   3.3-6
ii  libreadline8  8.1-1

Versions of packages newlisp recommends:
ii  libcrypto++6  5.6.4-10
pn  libmysqlclient18  
ii  libpq513.2-1
ii  libsqlite3-0  3.34.1-3
ii  sensible-utils0.0.14
ii  zlib1g1:1.2.11.dfsg-2

newlisp suggests no packages.

-- no debconf information

Bug#984682: kodi: Kodi 19.0+dfsg1 PVR Recordings from vdr vnsi plugin all show the same recording date.

[Vasyl Gello]

Hi Selaron!

Thanks for the report!

>
>   * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
>I updated from debian buster to bullseye.
>Afterwards using kodi 19 all PVR recordings received via VNSI plugin from VDR
>are shown with the same recording date and thus cannot be sorted by date.
>Additionaly kodi does not remember the time to resume playback of recordings
>when kodi is restarted.
>
>Building kodi from source (apt source kodi) after reverting these patches helps
>me in getting the correct recording times back:
>debian/patches/cdatetime-std-chrono/0001-Replace-Kodi-date-time-implementation-
>with-std-c.patch
>debian/patches/cdatetime-std-chrono/0002-Use-Debian-tzdata.patch
>
>
>But kodi does still not remember PVR recording playback position beyond
>restarts.
>

I see two separate issues here:

* the same recording date displayed by PVR recording functionality, likely 
introduced by my backport of cdatetime topic,
* the PVR recording playback position forgotten, likely an upstream one.

I recall I had to fix PVRRecording within the cdatetime patchset to make PVR 
recordings not crash on display,
but what is the date displayed with cdatetime patch applied? Is that something 
like 12-31-1969 or similar?

Also I will try reproducing your setup with virtual DVB card because I am using 
IPTV Simple as my daily driver.

-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com

Skype: vasek.gello
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

Bug#984685: ITP: quicknav -- Quicknav is a command line tool that allows you to easily jump to specific locations in your filesystem from a simple command. Quicknav is built for terminal navigation on

[MrDogeBro]

Package: wnpp
Severity: wishlist
Owner: MrDogeBro 

* Package name: quicknav
  Version : 0.1.0
  Upstream Author : MrDogeBro 
* URL : https://github.com/MrDogeBro/quicknav
* License : MIT
  Programming Lang: Rust
  Description : A way to quickly navigate your filesystem from the command 
line.

Quicknav is a command line tool that allows you to easily jump to
specific locations in your filesystem from a simple command. Quicknav is
built for terminal navigation on Unix operating systems.

 - why is this package useful/relevant?
- The package is a useful way to navigation to common locations
from your terminal while not having tons of aliases in your
shell config which can get messy quick. This is a tool I use in
my daily workflow and it is very helpful for me to quickly get
to common locations.
 - how do you plan to maintain it? 
- I plan to keep updating the tool and adding new features and
fixing bugs. I think this tool is very useful to anyone who uses
a terminal and doesn't like their config files getting cluttered
like me.
- do you need a sponsor?
- From what I understand from reading the debian docs, I will need
a sponsor since you cannot upload a package to the debian repos
without a sponsor unless you are a debian developer.

Bug#984665: [Pkg-rust-maintainers] Bug#984665: CVE-2021-25900

[plugwash-urgent]

I started looking into this bug and trying to gauge it's impact.
In particular what if-any applications in Debian actually use the broken 
code.


First I tried to use codesearch to search for insert_many but I got way 
too many
false-positives. So I tried a different approach. I did however notice 
some embedded

code copies of smallvec during this search, more on that later.

I used zcat 
/srv/ftp.debian.org/mirror/dists/sid/main/binary-amd64/Packages.gz | 
grep-dctrl rust-smallvec -sPackage to identify what applications use 
(directly or indirectly) rust-smallvec, I came up with the following 
list.


bat
cargo-lock
cargo-outdated (build-depends uninstallable, not in testing)
debcargo
git-absorb
grcov
sq-keyring-linter
sqop
sq
sqv
spotify-tui (not in testing)

I installed the build-dependencies for all of these packages except 
cargo-outdated
and did "grep -r insert_many /usr/share/cargo/registry/" the only calls 
were in the

tests and benchmarks of smallvec itself.

I then downloaded and extracted the source packages for the apps 
themselves
into a directory and issued "grep -r insert_many *" in that directory, 
there

were no matches

I tried to repeat the process for buster, unfortunately it seems the 
version

of the tooling used to build many of the rust packages in buster did not
add built-using: or x-cargo-built-using:, It's possible there are also 
some
rust applications in bullseye that have not been touched for a long time 
and
hence suffer from the same isue. Anyway one application was found in 
buster that

had an X-Cargo-Built-Using for rust-smallvec.

ripgrep
I found the following packages that appeard to have embedded copies of
smallvec, it's very possible there were others as I did not do an 
exhaustive

search.
I repeated the build-dependency and source package contents tests 
described
above in buster, using the list of packages from both stable and 
unstable

(where the package existed in stable), again I found now results.

Going back to the original codesearch I noticed the following packages
in the list, that seemed (based mainly on my memory of what uses rust)
like they might be rust-related and investigated them further. I did not
investigate every package in the list for rust dependencies.

firefox
firefox-esr
rust-lexical-core
librsvg
thunderbird

firefox, firefox-esr, librsvg and thunderbird seem to have embedded
copies of rust-smallvec, but don't appear to call insert_many

rust-lexical-core seems to be completely unrelated to arrayvec
(it does not build-depend directly or indirectly on it and it
does not appear to have an embedded copy of it)

This search has not been perfect and I may try and assemble tooling to
do a better one, but my tentative conclusion is that the insert_many
operation in rust-arrayvec does not seem to actually be used.

Bug#984684: z80dasm: add support z180

[Ben Hildred]

Package: z80dasm
Version: 1.1.5-1
Severity: wishlist
Tags: patch upstream

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

we grabbed old parts off the shelf

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

patched z80dasm to add support for z180 extended instructions needed to 
disassemble project rom

   * What was the outcome of this action?

a complete diassembly in less than a day and mild astonishment

   * What outcome did you expect instead?

much more work

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 10.8
  APT prefers stable
  APT policy: (500, 'stable'), (100, 'buster-fasttrack')
Architecture: amd64 (x86_64)

Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled


-- no debconf information
diff --git a/src/dz80.c b/src/dz80.c
index 78c9bb3..a1155ee 100644
--- a/src/dz80.c
+++ b/src/dz80.c
@@ -247,7 +247,13 @@ else 
if((a>=0x70)&&(a<0x80)&&(ed70[a-0x70][0]!='0'))FP(fx,"%s",ed70[a-0x70]);
 else if((a>=0xa0)&&(a<0xb0)&&(eda0[a-0xa0][0]!='0'))FP(fx,"%s",eda0[a-0xa0]);
 else if((a>=0xb0)&&(a<0xc0)&&(edb0[a-0xb0][0]!='0'))FP(fx,"%s",edb0[a-0xb0]);
 */
-   if((a>=0x40)&&(a<0x50)&&(ed40[a-0x40][0]!='0')) i=0;
+   if((a & 0xc6)==0){ /* 0 0 g g g 0 0 x ino, outo */
+   i=6;
+   //}
+   //else if((a & 0xcF)==0x6c){ /* 0 1 w w 1 1 0 0 mlt */
+   //  i=7;
+   }
+   else if((a>=0x40)&&(a<0x50)&&(ed40[a-0x40][0]!='0')) i=0;
else if((a>=0x50)&&(a<0x60)&&(ed50[a-0x50][0]!='0')) i=1;
else if((a>=0x60)&&(a<0x70)&&(ed60[a-0x60][0]!='0')) i=2;
else if((a>=0x70)&&(a<0x80)&&(ed70[a-0x70][0]!='0')) i=3;
@@ -275,10 +281,20 @@ else 
if((a>=0xb0)&&(a<0xc0)&&(edb0[a-0xb0][0]!='0'))FP(fx,"%s",edb0[a-0xb0]);
break;
case 5: strcpy(rstr,edb0[a-0xb0]);
break;
+   case 6: //before_undoc(3);
+   strcpy(rstr,edio[a&1]);
+   break;
+   //case 7: //before_undoc(2);
+   //  break;
}
 
 /*if arg not in prog range it is a constant*/
-   if(a == 0x43)
+   if(i==6)
+   {
+   r=(a & 0x38) >>3;
+   strcpy(stro,regf[r]);
+   }
+   else if(a == 0x43)
{
strcpy(stro,"%s),bc");
}
@@ -298,7 +314,14 @@ else 
if((a>=0xb0)&&(a<0xc0)&&(edb0[a-0xb0][0]!='0'))FP(fx,"%s",edb0[a-0xb0]);
stro[0] = 0;
}
 
-   if(stro[0] == 0) {
+   if(i==6){
+   if (a&1){
+   FP(fx,rstr,t[2],stro);
+   }else{
+   FP(fx,rstr,stro,t[2]);
+   }
+   return(3);
+   } else if(stro[0] == 0) {
FP(fx,"%s",rstr);
return(2);
} else {
diff --git a/src/dz80.h b/src/dz80.h
index 0c365a7..3bcf8f8 100644
--- a/src/dz80.h
+++ b/src/dz80.h
@@ -36,6 +36,8 @@ int msg(int level, const char *format, ...);
 /* from dz80dat.c */
 extern const char *rarg[];
 extern const struct comm comtab[];
+extern const char *regf[];
+extern const char *edio[];
 extern const char *ed40[];
 extern const char *ed50[];
 extern const char *ed60[];
diff --git a/src/dz80dat.c b/src/dz80dat.c
index 4c496fa..6870bf3 100644
--- a/src/dz80dat.c
+++ b/src/dz80dat.c
@@ -264,6 +264,20 @@ const struct comm comtab[]={
 /*ff*/{"rst 38h","vv",1,0,0},
};
 
+const char *regf[]={
+/*0*/"b",
+/*1*/"c",
+/*2*/"d",
+/*3*/"e",
+/*4*/"h",
+/*5*/"l",
+/*6*/""/* invalid */,
+/*7*/"a",
+   };
+const char *edio[]={
+/*38*/"ino %s, (0x%02llx)",
+/*39*/"outo (0x%02llx), %s",
+};
 const char *ed40[]={
 /*40*/"in b,(c)",
 /*41*/"out (c),b",
@@ -277,7 +291,7 @@ const char *ed40[]={
 /*49*/"out (c),c",
 /*4a*/"adc hl,bc",
 /*4b*/"ld bc,(",
-/*4c*/"00",
+/*4c*/"mlt bc",
 /*4d*/"reti",
 /*4e*/"00",
 /*4f*/"ld r,a",
@@ -296,7 +310,7 @@ const char *ed50[]={
 /*59*/"out (c),e",
 /*5a*/"adc hl,de",
 /*5b*/"ld de,(",
-/*5c*/"00",
+/*5c*/"mlt de",
 /*5d*/"00",
 /*5e*/"im 2",
 /*5f*/"ld a,r",
@@ -307,7 +321,7 @@ const char *ed60[]={
 /*61*/"out (c),h",
 /*62*/"sbc hl,hl",
 /*63*/"00",
-/*64*/"00",
+/*64*/"tst m",
 /*65*/"00",
 /*66*/"00",
 /*67*/"rrd",
@@ -315,7 +329,7 @@ const char *ed60[]={
 /*69*/"out (c),l",
 /*6a*/"adc hl,hl",
 /*6b*/"00",
-/*6c*/"00",
+/*6c*/"mlt hl",
 /*6d*/"00",
 /*6e*/"00",
 /*6f*/"rld",
@@ -326,7 +340,7 @@ const char *ed70[]={
 /*71*/"out (c),0",
 /*72*/"sbc hl,sp",
 /*73*/"ld (",
-/*74*/"00",
+/*74*/"0tstio (", // incomplete
 /*75*/"00",
 /*76*/"00",
 /*77*/"00",
@@ -334,7 +348,7 @@ const char *ed70[]={
 /*79*/"out (c),a",
 /*7a*/"adc hl,sp",
 /*7b*/"ld sp,(",
-/*7c*/"00",
+/*7c*/"mlt sp",
 /*7d*/"00",
 /*7e*/"00",
 /*7f*/"00",

Bug#984683: RM: libwww-freshmeat-perl -- ROM; obsolete

[gregor herrmann]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: debian-p...@lists.debian.org,982...@bugs.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please remove libwww-freshmeat-perl from the archive.

It's a perl module which interacts with freshmeat.net. Which doesn't
exist anymore since, well, many years.

Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmBELhBfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZvixAAgzPGmZ0dkoU5BQRUxVVg37tpXn1imQsLc5Y62dM3M+T5+WVJwojM1imx
c6m7bniIqi50hgy44CcIRLxlzbdfoiJyZniIbJSmPKvOLq3Ufvzo1U6Md1+WkS3L
ajTAIhJthVUGm03DqkjI08HfPES95D08W1qMCEPtEeesIigdXGxa+Ddcndryl5l0
oiNmNUhLj+lQO8iEz6HD2gqadtiBnPrtnTAbStlO5/rYHSgd1xYfovAacphbHMuK
vdaOgElEWKTxjO+aKqeuTVpQGUgkcffM9cmmzhhuoP8o1+z0kbGYgVt6jbzaCXwQ
XKuSk/hLi81LO7nXSaefFdFzQBdeiHgOoA7FNO/SJ0GytZRUPz2ECVJm7ApTT9Tf
od2jUfz8xbxtM2eFHN6Cbx2cGCXvfa+EU0zZjuob19lWna+7IRz5EKkg9iUReyJ4
lHPpbTE8D7AwuZeAoC3EpXIVFrpDcooMwRj/salJyvYp3YhOPFfb02NnQlZdqbKo
++cXJaNgxEOnxcRfM4cfnkEzZ0mUchhZHxGw6EJKcPoAPOqfkY32318ul/IEVl9N
0lBMORqLjy0CMNGFxN2WEXWmeuF8Jj+/szyqY5/0mbvoJjum6/sk8Ms+Rim6Mfd0
fKXT7rVUkPAXQtZN8JyUfb7kTze2TwCQ42ueAsBAVbE3ZvWpgL4=
=jbHD
-END PGP SIGNATURE-

Bug#979631: They just keep filling up

[積丹尼 Dan Jacobson]

Help. The kernels just don't go away:
$  apt-show-versions -r -p '^linux-image-[0-9]+\.'
linux-image-5.10.0-1-amd64:amd64 5.10.5-1 installed: No available version in 
archive
linux-image-5.10.0-2-amd64:amd64 5.10.9-1 installed: No available version in 
archive
linux-image-5.10.0-3-amd64:amd64 5.10.13-1 installed: No available version in 
archive
linux-image-5.10.0-4-amd64:amd64/unstable 5.10.19-1 uptodate
linux-image-5.9.0-2-amd64:amd64 5.9.6-1 installed: No available version in 
archive
linux-image-5.9.0-4-amd64:amd64 5.9.11-1 installed: No available version in 
archive
linux-image-5.9.0-5-amd64:amd64 5.9.15-1 installed: No available version in 
archive

Bug#668945: xpdf can not display ToC in UTF-8

[Adam Sampson]

This bug is related to #946270 ("xpdf: can't search for various Unicode
characters") -- traditional xpdf doesn't enable Motif's localisation
support, so it can only disable ISO-8859-1 characters in the UI.

I've got some patches now for xpopple that enable localisation and fix
searching and outline display. They're in the "unicode" branch in
xpopple Git at the moment, and I'll push them to master once they've had
a bit more testing.

Screenshot: http://stuff.offog.org/xpdf-ru.png

Thanks,

-- 
Adam Sampson  

Bug#977694: 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd

[João Ricardo Sares Teles de Matos]

I ran into this issue while trying to migrate the root filesystem into a 
btrfs subvolume on an USB hard drive.

I'm also using a Raspberry Pi 4B.

I followed Ryutaroh's advice of loading the reset_raspberrypi module, as 
follows:


> echo reset_raspberrypi >/etc/initramfs-tools/modules
> update-initramfs -uk all

And now I can boot from USB.


Note that this issue also causes any other USB devices to be missing 
while in initramfs, including USB keyboards, which might be useful in a 
rescue shell.


Sidenote: the rescue shell only seems to be spawned on the serial 
terminal currently, so having a USB keyboard is still useless in that 
regard, but that's another issue.



I feel inclined to agree with the idea of adding the file

> /usr/share/initramfs-tools/modules.d/raspi-firmware.conf

with the contents

> reset_raspberrypi

to the package raspi-firmware, provided that it doesn't interfere with 
the rest of the Raspberry Pi family.


Best regards, João Matos

Bug#984681: menu.h: correct prototype for "menu()"

[Bjarni Ingi Gislason]

Source: nn
Version: 6.7.3-14
Severity: normal
Tags: patch

Dear Maintainer,

>From 3d3b4182a08234c50de0841eccd7101225ff2cb0 Mon Sep 17 00:00:00 2001
>From: Bjarni Ingi Gislason 
>Date: Sat, 6 Mar 2021 23:10:53 +
>Subject: [PATCH] menu.h: correct prototype for "*menu()"

  Change from "menu(int (*)(void))" to "menu(fct_type_void)".

Signed-off-by: Bjarni Ingi Gislason 
---
 menu.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/menu.h b/menu.h
index e43ca02..69c5e34 100644
--- a/menu.h
+++ b/menu.h
@@ -62,7 +62,7 @@
 #define AC_UNCHANGED   6   /* no display changes */
 
 char   *pct(long, long, long, long);
-int menu(int (*)(void));
+int menu(fct_type_void);
 article_header *get_menu_article(void);
 int alt_command(void);
 int prt_replies(int);
-- 
2.30.1



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

Kernel: Linux 5.10.9-1 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- debconf information excluded

-- 
Bjarni I. Gislason

Bug#984679: unblock elfutils/0.183-2

[Sergio Durigan Junior]

Control: retitle -1 pre-approval: unblock elfutils/0.183-2

On Saturday, March 06 2021, I wrote:

> Hi,
>
> Please unblock elfutils/0.183-2.
>
> I have just uploaded this version to address
> , which is
> about enabling the use of https://debuginfod.debian.net by default if
> the user chooses to do so when presented with a new debconf question.
>
> This is not an upload of a new upstream version, but it adds a new
> binary package (libdebuginfod-common) which holds the debconf
> template for the new question.  The package is currently in NEW.
>
> In all fairness, I am not entirely sure whether this requires an unblock
> bug, but I decided to be safe and file one.

Here's the debdiff.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

diff -Nru elfutils-0.183/debian/changelog elfutils-0.183/debian/changelog
--- elfutils-0.183/debian/changelog	2021-02-08 03:56:24.0 -0500
+++ elfutils-0.183/debian/changelog	2021-02-28 21:07:16.0 -0500
@@ -1,3 +1,33 @@
+elfutils (0.183-2) unstable; urgency=medium
+
+  * d/control:
+- B-D on lsb-release.
+- B-D on po-debconf.
+- Create new libdebuginfod-common package.
+- Add myself to Uploaders.
+  * d/rules:
+- Use https://debuginfod.debian.net as our default service.
+  Also, revamp the code responsible for determining libdebuginfod
+  configuration flags.
+- Invoke dh_installdebconf.
+  * d/libdebuginfod-common.templates: Create a debconf template.
+Also, create d/po/POTFILES.in and d/po/templates.pot.
+This template is for the question of whether the user accepts GDB or
+another debuginfo consumer program to connect to Debian's debuginfod
+server.
+  * d/libdebuginfod-common.config: Ask if the user accepts to use Debian's
+debuginfod.
+  * d/libdebuginfod-common.postinst: Act upon the user's answer to the
+debconf question.
+If the user has accepted to use Debian's debuginfod, then the script
+confirms the value of the DEBUGINFOD_URLS environment variable present
+in the shell excerpts under /etc/profile.d.  Otherwise, the script
+will set the variable to an empty value, disabling the remote
+connection to the debuginfod server. (Closes: #983434)
+  * d/libdebuginfod-common.install: Install the profile.d snippets.
+
+ -- Sergio Durigan Junior   Sun, 28 Feb 2021 21:07:16 -0500
+
 elfutils (0.183-1) unstable; urgency=medium
 
   * New upstream release. Changes compared to the snapshot:
diff -Nru elfutils-0.183/debian/control elfutils-0.183/debian/control
--- elfutils-0.183/debian/control	2021-02-08 03:56:24.0 -0500
+++ elfutils-0.183/debian/control	2021-02-28 21:07:16.0 -0500
@@ -2,11 +2,12 @@
 Priority: optional
 Maintainer: Debian Elfutils Maintainers 
 Uploaders: Kurt Roeckx ,
-  Matthias Klose 
+  Matthias Klose ,
+  Sergio Durigan Junior ,
 Build-Depends: debhelper (>= 11),
-  autoconf, automake,
+  autoconf, automake, lsb-release,
   bzip2, zlib1g-dev, zlib1g-dev:native, libbz2-dev, liblzma-dev,
-  m4, gettext,
+  m4, gettext, po-debconf,
   gawk, dpkg-dev (>= 1.16.1~),
   gcc-multilib [any-amd64 sparc64] ,
   libc6-dbg [powerpc powerpcspe ppc64 ppc64el armel armhf arm64 sparc64 riscv64],
@@ -113,7 +114,8 @@
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends},
-  libelf1 (= ${binary:Version}), libdw1 (= ${binary:Version})
+  libelf1 (= ${binary:Version}), libdw1 (= ${binary:Version}),
+  libdebuginfod-common (= ${source:Version})
 Pre-Depends: ${misc:Pre-Depends}
 Description: library to interact with debuginfod (development files)
  The libdebuginfo1 package provides a library with an interface to interact
@@ -142,3 +144,15 @@
  Server, client tool and library to index and fetch ELF/DWARF files
  addressed by build-id through HTTP.
 
+Package: libdebuginfod-common
+Build-Profiles: 
+Section: devel
+Architecture: all
+Multi-Arch: foreign
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Pre-Depends: ${misc:Pre-Depends}, debconf
+Description: library to interact with debuginfod (common files)
+ The libdebuginfo1 package provides a library with an interface to interact
+ with debuginfod.
+ .
+ This package contains the common files for libdebuginfod.
diff -Nru elfutils-0.183/debian/libdebuginfod-common.config elfutils-0.183/debian/libdebuginfod-common.config
--- elfutils-0.183/debian/libdebuginfod-common.config	1969-12-31 19:00:00.0 -0500
+++ elfutils-0.183/debian/libdebuginfod-common.config	2021-02-28 21:07:16.0 -0500
@@ -0,0 +1,18 @@
+#!/bin/sh
+
+set -e
+
+. /usr/share/debconf/confmodule
+
+db_version 2.0
+db_capb
+
+# Ask whether the user is OK with using Debian's debuginfod.  We just
+# bother with the question if there is actually a debuginfod profile.d
+# script available.
+if [ -f /etc/profile.d/debuginfod.sh ]; then
+if grep -qFx "ID=debian" /etc/os-release; 

Bug#927454: ITP: towncrier -- compiler for project news file

[Sergio Durigan Junior]

On Saturday, March 06 2021, Ben Finney wrote:

> On 05-Mar-2021, Sergio Durigan Junior wrote:
>
>> How are you?
>
> Thanks for asking. I'm not great, but it's all relative; pretty much
> everyone has had a bad 12 months more more. Hope you're well.

Ouch, sorry to read that :-(.  I hope you take good care of yourself,
and please don't feel pressured to work on this package just because of
my message.

>> I have a friend (who is also my namesake) who is interested in
>> having towncrier in the archive. Maybe you can give us/him some
>> pointers on the current status of the package so that he can help
>> you with it?
>
> Thank you for the prompt. I will get back onto this and bring it up to
> date.

Thanks, I really appreciate it, but as I said, please don't feel like
you need to do that.  Sérgio Cipriano is interested in helping with the
package (he is still learning, but I can attest that he's good and picks
things up really fast), so if you want to give us the lay of the land we
can take it from here, no problems.

Otherwise, if you feel like finishing the package, please know that you
can ping us if you need any help!

Thank you very much.  Take care!

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#984680: aegisub: Aegisub often freezes when it encounters non-ASCII characters in some situations

[Kristof Csillag]

Package: aegisub
Version: 3.2.2+dfsg-6+b1
Severity: important
Tags: l10n

When copying data from the clipboard, if it has any non-ASCII character, I get 
this on the console:

../src/common/string.cpp(1185): assert "c < 0x80" failed in FromAscii(): 
Non-ASCII value passed to FromAscii().

... and the app freezes completely.

I don't know how to recover from this, except by killing the app.

Sometimes the same thing also happens when it encounters accented characters in 
filenames...
... or even just by opening the menu, if it remembers some accented file names 
from recent history,
and tries to diplay those options in the menu.

This is very annoying, because the behavious is unpredictable; ie. the thing 
crashes randomly.

It would be great if this could be fixed somehow.

Thanks.


-- System Information:
Debian Release: 10.8
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (500, 
'oldstable')
Architecture: amd64 (x86_64)

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

Versions of packages aegisub depends on:
ii  libasound2 1.2.4-1.1
ii  libass91:0.14.0-2
ii  libboost-chrono1.74.0  1.74.0-8
ii  libboost-filesystem1.74.0  1.74.0-8
ii  libboost-locale1.74.0  1.74.0-8
ii  libboost-regex1.74.0 [libboost-regex1.74.0-icu67]  1.74.0-8
ii  libboost-thread1.74.0  1.74.0-8
ii  libc6  2.31-9
ii  libffms2-4 2.23-4
ii  libfftw3-double3   3.3.8-2
ii  libfontconfig1 2.13.1-4.2
ii  libgcc-s1  10.2.1-6
ii  libgl1 1.3.2-1
ii  libhunspell-1.7-0  1.7.0-3
ii  libicu67   67.1-6
ii  libluajit-5.1-22.1.0~beta3+dfsg-5.1
ii  libpulse0  14.2-2
ii  libstdc++6 10.2.1-6
ii  libwxbase3.0-0v5   3.0.5.1+dfsg-2
ii  libwxgtk3.0-gtk3-0v5   3.0.5.1+dfsg-2
ii  zlib1g 1:1.2.11.dfsg-2

aegisub recommends no packages.

Versions of packages aegisub suggests:
pn  aegisub-l10n  

-- debconf-show failed

Bug#927454: ITP: towncrier -- compiler for project news file

[Ben Finney]

On 05-Mar-2021, Sergio Durigan Junior wrote:

> How are you?

Thanks for asking. I'm not great, but it's all relative; pretty much
everyone has had a bad 12 months more more. Hope you're well.

> I'm writing to check on the status of the towncrier package. I
> noticed that you have an apparently complete package on
> https://salsa.debian.org/bignose/pkg-towncrier, but it hasn't been
> uploaded and I can't find why.

One of many things that slipped aside in 2020.

> I have a friend (who is also my namesake) who is interested in
> having towncrier in the archive. Maybe you can give us/him some
> pointers on the current status of the package so that he can help
> you with it?

Thank you for the prompt. I will get back onto this and bring it up to
date.

-- 
 \ “I was stopped by the police for speeding; they said ‘Don't you |
  `\   know the speed limit is 55 miles an hour?’ I said ‘Yeah I know, |
_o__) but I wasn't going to be out that long.’” —Steven Wright |
Ben Finney 


signature.asc
Description: PGP signature

Bug#984679: unblock elfutils/0.183-2

[Sergio Durigan Junior]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Hi,

Please unblock elfutils/0.183-2.

I have just uploaded this version to address
, which is
about enabling the use of https://debuginfod.debian.net by default if
the user chooses to do so when presented with a new debconf question.

This is not an upload of a new upstream version, but it adds a new
binary package (libdebuginfod-common) which holds the debconf
template for the new question.  The package is currently in NEW.

In all fairness, I am not entirely sure whether this requires an unblock
bug, but I decided to be safe and file one.

Thanks in advance,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#984678: Please add check for tmpfiles similar to systemd-service-file-pidfile-refers-to-var-run

[Michael Biebl]

Package: lintian
Version: 2.104.0
Severity: wishlist

Hi,

we already have a check for .service files using
/var/run in PIDFile systemd-service-file-pidfile-refers-to-var-run

A similar check should be added for tmpfiles (i.e. files matching
/usr/lib/tmpfiles.d/*.conf) to prevent tmpfiles from using /var/run.
I think restricting it to directories should be a good start, i.e.
trigger the warning if the tmpfile contains something like
'^d\s+/var/run', like in
https://codesearch.debian.net/search?q=%5Ed%5Cs%2B%2Fvar%2Frun=0

A tmpfile using /var/run currently triggers this warning in systemd-tmpfiles:

# echo "d /var/run/bad 0755 root root" > /etc/tmpfiles.d/test.conf
# systemd-tmpfiles --create /etc/tmpfiles.d/test.conf
/etc/tmpfiles.d/test.conf:1: Line references path below legacy directory 
/var/run/, updating /var/run/bad → /run/bad; please update the tmpfiles.d/ 
drop-in file accordingly.

Obviously, the service requiring this runtime directory should be
updated accordingly to write its runtime files directly to /run,
i.e. it's not sufficient to only change the tmpfile to /run when the
service is still configured/built to write to /var/run.

Regards,
Michael

-- 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.0-4-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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 lintian depends on:
ii  binutils2.35.2-2
ii  bzip2   1.0.8-4
ii  diffstat1.64-1
ii  dpkg1.20.7.1
ii  dpkg-dev1.20.7.1
ii  file1:5.39-3
ii  gettext 0.21-4
ii  gpg 2.2.27-1
ii  intltool-debian 0.35.0+20060710.5
ii  libapt-pkg-perl 0.1.40
ii  libarchive-zip-perl 1.68-1
ii  libcapture-tiny-perl0.48-1
ii  libclass-xsaccessor-perl1.19-3+b7
ii  libclone-perl   0.45-1+b1
ii  libconfig-tiny-perl 2.26-1
ii  libcpanel-json-xs-perl  4.25-1+b1
ii  libdata-dpath-perl  0.58-1
ii  libdata-validate-domain-perl0.10-1.1
ii  libdevel-size-perl  0.83-1+b2
ii  libdigest-sha-perl  6.02-1+b3
ii  libdpkg-perl1.20.7.1
ii  libemail-address-xs-perl1.04-1+b3
ii  libfile-basedir-perl0.08-1
ii  libfile-find-rule-perl  0.34-1
ii  libfont-ttf-perl1.06-1.1
ii  libhtml-html5-entities-perl 0.004-1.1
ii  libipc-run3-perl0.048-2
ii  libjson-maybexs-perl1.004003-1
ii  liblist-compare-perl0.55-1
ii  liblist-moreutils-perl  0.430-2
ii  liblist-utilsby-perl0.11-1
ii  libmoo-perl 2.004004-1
ii  libmoox-aliases-perl0.001006-1.1
ii  libnamespace-clean-perl 0.27-1
ii  libpath-tiny-perl   0.118-1
ii  libperlio-gzip-perl 0.19-1+b7
ii  libproc-processtable-perl   0.59-2+b1
ii  libsereal-decoder-perl  4.018+ds-1+b1
ii  libsereal-encoder-perl  4.018+ds-1+b1
ii  libtext-glob-perl   0.11-1
ii  libtext-levenshteinxs-perl  0.03-4+b8
ii  libtext-markdown-discount-perl  0.12-1+b1
ii  libtext-xslate-perl 3.5.8-1+b1
ii  libtime-duration-perl   1.21-1
ii  libtime-moment-perl 0.44-1+b3
ii  libtimedate-perl2.3300-2
ii  libtry-tiny-perl0.30-1
ii  libtype-tiny-perl   1.012001-2
ii  libunicode-utf8-perl0.62-1+b2
ii  liburi-perl 5.08-1
ii  libxml-libxml-perl  2.0134+dfsg-2+b1
ii  libyaml-libyaml-perl0.82+repack-1+b1
ii  lzip1.22-3
ii  lzop1.04-2
ii  man-db  2.9.4-2
ii  patchutils  0.4.2-1
ii  perl [libdigest-sha-perl]   5.32.1-3
ii  t1utils 1.41-4
ii  unzip   6.0-26
ii  xz-utils5.2.5-1.0

lintian recommends no packages.

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  libtext-template-perl  1.59-1

-- no debconf information

Bug#650234: More information

[Ralph Ronnquist]

Package: fakechroot
Version: 2.19-3.2

Commenting out the lines mentioning fakechroot_chroot_paths_ldsoconf
in /usr/sbin/chroot.fakechroot, and the resulting spurious "fi",
avoids this problem.

Ralph.

Bug#984635: unblock: tqdm/4.57.0-2

[Sandro Tosi]

> > i'm open to suggestions on how to address it, but i would prefer to
> > avoid frankenstein monsters of x.y.zreallym.n.o or giant patches
> > against an old version of tqdm that could be addressed by a new
> > upstream release.
>
> Me too, but tqdm is a key package

apologies, i did not realized tqdm reached the "key package" status,
otherwise it'd have been more careful with the recent uploads :(

> and we really want to avoid
> unnecessary changes at much as possible at this stage. How much smaller
> is the diff between 4.51.0-1 and 4.56.2-1 compared to the current diff?

i let salsa do the diff, as i believe it's a bit easier to navigate
than pure debdiff (at least for upstream changes):

https://salsa.debian.org/python-team/packages/tqdm/-/compare/upstream%2F4.55.1...upstream%2F4.56.2

and this is the upstream diff between 4.56.2 and the latest upstream
release in unstable, 4.57.0:

https://salsa.debian.org/python-team/packages/tqdm/-/compare/upstream%2F4.56.2...upstream%2F4.57.0

which i believe is relatively tiny and mostly contains minor changes

> And what's in the additional delta?

sorry, delta between what specifically? 4.56.2-1 and 4.57.0-2?
https://salsa.debian.org/python-team/packages/tqdm/-/compare/debian%2F4.56.2-1...debian%2F4.57.0-2
the changes in the packaging files are just what's required by the
upstream code changes.

Let me know if some of these answer are not clear or satisfactory

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

Bug#983031: konqueror segfaults on starting

[Aurélien COUDERC]

Le samedi 6 mars 2021, 17:43:11 CET J Rowan a écrit :
> On Sat, 6 Mar 2021 14:04:38 +0100

Dear Joe,

thanks for taking the time to report the bug and investigate.
What the stack tells us is that the crash is in the R300 OpenGL graphics 
driver, as called by Qt Web Engine that Konqueror uses for the HTML rendering.

I cannot reproduce the crash myself on various more recent pieces of hardware, 
and neither did the team get similar bug reports.

So I can see 3 possible causes and (im)possible fixes from the most probable 
to the least :
1/ The OpenGL driver has a broken code path that is triggered here and should 
be fixed.
2/ Qt Web Engine calls the OpenGL stack incorrectly in this case and could be 
fixed. Alternatively it could be made to work around that particular OpenGL 
driver bug even if we’re in case 1/.
3/ That piece of graphics hardware is (now) broken and the code path makes it 
visible, nothing we can do about it. If that was the case I would expect the 
crash not to be reproducible 100% of the time, and here it looks like you can 
reproduce it so maybe not.

Looking the hardware support for that driver you must have a graphics card 
from the Radeon 9500-9800 series, X300-X600 series or X1050/X1150 from the 
2003-2005 era.
This driver is in maintenance mode to say the least so I wouldn’t get my hopes 
too high about a possible fix.

However if you want to help diagnose the issue further you could install the 
dbgsym packages [1] for at least libgl1-mesa-dri, libglx-mesa0, 
libqt5webenginecore5 and konqueror packages, and rerun the same gdb call so we 
get the crash stack with the function names and line numbers.

If you can confirm whether you get crashes with other programs using 3D 
rendering besides konqueror, that would be a useful data point.

Then we can decide if we want to forward the bug to mesa or Qt.

Again be ready to face refusals from both upstreams to work on an issue for 
such an old piece of hardware. Most opensource projects are understaffed and I 
have the feeling that reproducing let alone fixing this issue is not going to 
be an easy task.
Also I seem to remember that the R300 driver was made out of reverse 
engineering or with documentation provided to selected developers under NDA, 
which is not going to help either…

If you don’t have the time or motivation to do the above and dig further I’d 
still appreciate that you say so, and I’ll just mark this bug as « won’t 
fix ».


[1] https://wiki.debian.org/AutomaticDebugPackages?highlight=%28dbgsym%29


Thanks & happy hacking !
--
Aurélien


> Bernhard Übelacker  wrote:
> > gdb -q -ex 'set pagination off' -ex 'run' -ex 'bt' -ex 'detach' -ex
> > 'quit' --args konqueror
> 
> Reading symbols from konqueror...
> Reading symbols from
> /usr/lib/debug/.build-id/e4/6ba37330371215b40e01c7c01397ce28f6aa3c.debug...
> Starting program: /usr/bin/konqueror
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [New Thread 0x70faf700 (LWP 8878)]
> [New Thread 0x7fffe42c3700 (LWP 8885)]
> [New Thread 0x7fffe3981700 (LWP 8886)]
> [New Thread 0x7fffe3180700 (LWP 8887)]
> [New Thread 0x7fffe297f700 (LWP )]
> [New Thread 0x7fffe217e700 (LWP 8889)]
> [New Thread 0x7fffe197d700 (LWP 8890)]
> 
> Thread 1 "konqueror" received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> #0  0x in  ()
> #1  0x7fffeafcf23f in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
> #2  0x7fffeaaeb704 in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
> #3  0x7fffeaaeca94 in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
> #4  0x7fffeaace95e in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
> #5  0x7fffeafcd903 in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
> #6  0x707175af in  () at /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
> #7  0x70705e49 in  () at /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
> #8  0x715db1b5 in  () at
> /usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integra
> tion.so #9  0x763fa4fb in QOpenGLContext::destroy() () at
> /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #10 0x763fa7a7 in
> QOpenGLContext::~QOpenGLContext() () at
> /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x715dd2bf in  () at
> /usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integra
> tion.so #12 0x715dd909 in  () at
> /usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integra
> tion.so #13 0x7fffbd4d9845 in  () at
> /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #14 0x7fffd210
> in  ()
> #15 0x7fffbd4ddec1 in  () at
> /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #16 0x7fffd610
> in  ()
> #17 0x7fffbd4dc4e5 in  () at
> /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #18 0x7fffd230
> in  ()
> #19 0x0005 in  ()
> #20 0x7fffd530 in  ()
> #21 0x7fffd540 in  ()
> 

Bug#984677: ngspice: Please mark symbols optimized away with -O3 as optional

[Logan Rosen]

Package: ngspice
Version: 34+ds-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch

Hi,

ngspice 34+ds-1 failed to build on ppc64el in Ubuntu [1] because we use -O3
by default on that architecture, and two symbols are optimized away at
that level.

In Ubuntu, the attached patch was applied to achieve the following:

  * d/libngspice0.symbols: Mark a couple of symbols as optional that are
optimized away with -O3 on ppc64el.

Thanks for considering the patch.

Logan

[1] https://launchpad.net/ubuntu/+source/ngspice/34+ds-1
diff -Nru ngspice-34+ds/debian/libngspice0.symbols 
ngspice-34+ds/debian/libngspice0.symbols
--- ngspice-34+ds/debian/libngspice0.symbols2021-01-31 06:43:20.0 
-0500
+++ ngspice-34+ds/debian/libngspice0.symbols2021-03-05 22:53:34.0 
-0500
@@ -16,8 +16,8 @@
  _Z6HICFCTdN5duals4dualIdEEPS1_S2_@Base 34+ds
  _Z6QJMODFN5duals4dualIdEES1_S1_dS1_S1_PS1_S2_@Base 34+ds
  _Z7TMPHICJN5duals4dualIdEEdS1_S1_dddPS1_S2_S2_@Base 34+ds
- _ZNSt14_Function_baseD1Ev@Base 34+ds
- _ZNSt14_Function_baseD2Ev@Base 34+ds
+ (optional=templinst)_ZNSt14_Function_baseD1Ev@Base 34+ds
+ (optional=templinst)_ZNSt14_Function_baseD2Ev@Base 34+ds
  hicum_thermal_update@Base 34+ds
 # added in 28
  ngGet_Evt_NodeInfo@Base 28

Bug#984676: rt5-db-sqlite: package description refers to version 4 instead of 5

[Daniele Forsi]

Package: rt5-db-sqlite
Severity: minor

Dear Maintainer,

package description says: "This package provides the 4 series of RT." but it 
provides version 5.

thanks,
Daniele

Bug#984675: group.c: fix some warnings issued by the compiler and add other changes.

[Bjarni Ingi Gislason]

Source: nn
Version: 6.7.3-14
Severity: normal
Tags: patch

Dear Maintainer,

>From a54bc2423dd39d33a8c5e3cacc8a41e5874516ea Mon Sep 17 00:00:00 2001
>From: Bjarni Ingi Gislason 
>Date: Sat, 6 Mar 2021 21:28:54 +
>Subject: [PATCH] group.c: fix some warnings issued by the compiler and add
> other changes.

  Include header file "group.h" for prototypes.

  Change the name of the variable "NDELAYED_MSG" to lower case
"ndelayed_msg".

  Fix the declaration of the last parameter of the function
"group_menu()" from "fct_type menu" to "int (* menu) (fct_type_void)".

  Use "snprintf()" instead of "sprintf()".

Signed-off-by: Bjarni Ingi Gislason 
---
 group.c | 12 
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/group.c b/group.c
index 8819d52..44fd67f 100644
--- a/group.c
+++ b/group.c
@@ -14,6 +14,7 @@
 #include "articles.h"
 #include "db.h"
 #include "folder.h"
+#include "group.h"
 #include "macro.h"
 #include "match.h"
 #include "menu.h"
@@ -52,7 +53,7 @@ extern int  killed_articles;
 extern int  seq_cross_filtering;
 extern char*default_save_file, *folder_save_file;
 
-extern const size_t NDELAYED_MSG;
+extern const size_t ndelayed_msg;
 extern char delayed_msg[];
 extern int32db_read_counter;
 
@@ -210,7 +211,10 @@ print_header(void)
  */
 
 int
-group_menu(register group_header * gh, article_number first_art, register 
flag_type access_mode, char *mask, fct_type menu)
+group_menu(register group_header * gh, article_number first_art,
+   register flag_type access_mode, char *mask,
+  int (* menu) (fct_type_void) )
+
 {
 register group_header *mg_head;
 article_number  was_unread;
@@ -763,7 +767,7 @@ get_group_name:
if (!get_from_macro) {
prompt("\1Number of extra articles\1 max %ld: ",
   gh->current_first - gh->first_db_article);
-   sprintf(buffer, "%c", ans1);
+   snprintf(buffer, FILENAME, "%c", ans1);
answer = get_s(NONE, buffer, NONE, NULL_FCT);
if (answer == NULL || *answer == NUL)
goto_return(ME_NO_REDRAW);
@@ -1160,7 +1164,7 @@ merge_and_read(flag_type access_mode, char *mask)
 current_group = _group;
 
 kb = (kb + 1023) >> 10;
-snprintf(delayed_msg, NDELAYED_MSG, "Read %ld articles in %ld seconds (%ld 
kbyte/s)",
+snprintf(delayed_msg, ndelayed_msg, "Read %ld articles in %ld seconds (%ld 
kbyte/s)",
(long) db_read_counter, (long) t2, t2 > 0 ? kb / t2 : kb);
 
 menu(merged_header);
-- 
2.30.1



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

Kernel: Linux 5.10.9-1 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- debconf information excluded

-- 
Bjarni I. Gislason

Bug#984674: ccache: clang links missing in /usr/lib/ccache

[Joachim Wuttke]

Package: ccache
Version: 4.2-1

Dear Joel or other maintainers:

Package ccache installs a number of symbolic links to /usr/lib/ccache,
among them clang-11 and clang++-11, but not clang and clang++.
May I kindly suggest you add these two?

Thank you for your work on ccache, Joachim



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#982966: python3-pygame: Using pygame 1.9.6 crashes Wayland (hard) and X

[Bernhard Übelacker]

Hello Richard,
thanks for the fast response.
I failed to tell you the -b0 means the current boot,
therefore if you rebooted with -b-1 might the boot that
contains the crash.

But maybe you could improve the output of coredumpctl
quite a bit.
Could you please add the debug symbol package repository
like in [1] and install these packages?

gdb libglib2.0-0-dbgsym gnome-shell-dbgsym libgjs0g-dbgsym 
libmozjs-78-0-dbgsym libmutter-7-0-dbgsym

Then you could again invoke 'coredumpctl gdb 18825',
that should print mostly the same information but give
you a "(gdb)" prompt, where you could issue the command
'bt full' and forward this output again?

Kind regards,
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

Bug#984673: solarwolf: Thread object has no attribute isAlive

[Markus Koschany]

Package: solarwolf
Version: 1.5+dfsg1-2
Severity: grave
X-Debbugs-Cc: a...@debian.org

solarwolf fails to start because of an AttributeError: Thread object
has no attribute isAlive. The funtion was removed in Python 3.9. The
new one appears to be is_alive(). I try to prepare a patch for
solarwolf but wouldn't mind if someone else beats me to it.

Markus


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

Kernel: Linux 4.19.0-14-amd64 (SMP w/4 CPU threads)
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: unable to detect

Versions of packages solarwolf depends on:
ii  python3 3.9.1-1
pn  python3-pygame  

solarwolf recommends no packages.

solarwolf suggests no packages.

Bug#984490: test-archive.t fails in the autopkg tests

[Logan Rosen]

Control: tags -1 patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/python-3.9.2.patch: Use "&" instead of ";" as query string separator
in test-archive.t to fix FTBFS with Python 3.9.2, which changed its
urllib.parse.parse_qsl() behavior to only accept "&" as a separator by
default.

Thanks for considering the patch.

Logan
diff -Nru mercurial-5.6.1/debian/patches/python-3.9.2.patch 
mercurial-5.6.1/debian/patches/python-3.9.2.patch
--- mercurial-5.6.1/debian/patches/python-3.9.2.patch   1969-12-31 
19:00:00.0 -0500
+++ mercurial-5.6.1/debian/patches/python-3.9.2.patch   2021-03-02 
23:00:32.0 -0500
@@ -0,0 +1,15 @@
+--- a/tests/test-archive.t
 b/tests/test-archive.t
+@@ -334,10 +334,10 @@
+   > pass
+   > if len(sys.argv) <= 3:
+   > node, archive = sys.argv[1:]
+-  > requeststr = 'cmd=archive;node=%s;type=%s' % (node, archive)
++  > requeststr = 'cmd=archive=%s=%s' % (node, archive)
+   > else:
+   > node, archive, file = sys.argv[1:]
+-  > requeststr = 'cmd=archive;node=%s;type=%s;file=%s' % (node, archive, 
file)
++  > requeststr = 'cmd=archive=%s=%s=%s' % (node, archive, 
file)
+   > try:
+   > stdout = sys.stdout.buffer
+   > except AttributeError:
diff -Nru mercurial-5.6.1/debian/patches/series 
mercurial-5.6.1/debian/patches/series
--- mercurial-5.6.1/debian/patches/series   2021-02-01 11:46:24.0 
-0500
+++ mercurial-5.6.1/debian/patches/series   2021-03-02 23:00:01.0 
-0500
@@ -4,3 +4,4 @@
 deb_specific__optional-dependencies
 deb_specific__disable_libdir_replacement.patch
 0005-Tolerate-SIGINT-getting-the-kill-in-test-stdio.py.patch
+python-3.9.2.patch

Bug#984671: unblock: dbconfig-common/2.0.19

[Paul Gevers]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Please unblock package dbconfig-common

[ Reason ]
Changes in dbconfig-common made during the bullseye release cycle
introduced a regression handling database names containing hyphens,
which made dbconfig-common fail in postinst when creating a database
user for a database containing a hyphen.

Escape the database name again to reestablish old behaviour.

[ Impact ]
Users that install packages that use dbconfig-common to handle the
database processing can see installation failures if databases are
involved that contain a hyphen.

[ Tests ]
dbconfig-common comes with an extensive test suite that's also run as
autopkgtest. I ran it manually and it passes, after I updated the
references to accommodate for the change.

[ Risks ]
The risk is small as the exact same quoting is present in buster too.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
https://salsa.debian.org/debian/dbconfig-common/-/merge_requests/6

unblock dbconfig-common/2.0.19

Paul
diff -Nru dbconfig-common-2.0.18/debian/changelog 
dbconfig-common-2.0.19/debian/changelog
--- dbconfig-common-2.0.18/debian/changelog 2021-01-29 21:34:31.0 
+0100
+++ dbconfig-common-2.0.19/debian/changelog 2021-03-06 20:56:28.0 
+0100
@@ -1,3 +1,10 @@
+dbconfig-common (2.0.19) unstable; urgency=medium
+
+  [ Simon Hollenbach ]
+  * Fix mysql grant for db names containing hyphens
+
+ -- Paul Gevers   Sat, 06 Mar 2021 20:56:28 +0100
+
 dbconfig-common (2.0.18) unstable; urgency=medium
 
   [ Chris Halls ]
diff -Nru dbconfig-common-2.0.18/internal/mysql 
dbconfig-common-2.0.19/internal/mysql
--- dbconfig-common-2.0.18/internal/mysql   2021-01-29 21:34:31.0 
+0100
+++ dbconfig-common-2.0.19/internal/mysql   2021-03-06 20:56:28.0 
+0100
@@ -326,7 +326,7 @@
 fi
 cat << EOF >> "$l_sqlfile"
 ALTER USER '$dbc_dbuser'@'$dbc_dballow' IDENTIFIED BY '$(dbc_mysql_escape_str 
"$dbc_dbpass")';
-GRANT ALL PRIVILEGES ON $dbc_dbname.* TO '$dbc_dbuser'@'$dbc_dballow';
+GRANT ALL PRIVILEGES ON \`$dbc_dbname\`.* TO '$dbc_dbuser'@'$dbc_dballow';
 FLUSH PRIVILEGES;
 EOF
 l_dbname=$dbc_dbname
diff -Nru dbconfig-common-2.0.18/test/data/dbc_mysql_createuser.nohost.sql.txt 
dbconfig-common-2.0.19/test/data/dbc_mysql_createuser.nohost.sql.txt
--- dbconfig-common-2.0.18/test/data/dbc_mysql_createuser.nohost.sql.txt
2021-01-29 21:34:31.0 +0100
+++ dbconfig-common-2.0.19/test/data/dbc_mysql_createuser.nohost.sql.txt
2021-03-06 20:56:28.0 +0100
@@ -1,4 +1,4 @@
 CREATE USER IF NOT EXISTS 'testdbuser'@'localhost';
 ALTER USER 'testdbuser'@'localhost' IDENTIFIED BY 'testdbpass';
-GRANT ALL PRIVILEGES ON testdbname.* TO 'testdbuser'@'localhost';
+GRANT ALL PRIVILEGES ON `testdbname`.* TO 'testdbuser'@'localhost';
 FLUSH PRIVILEGES;
diff -Nru dbconfig-common-2.0.18/test/data/dbc_mysql_createuser.remote.sql.txt 
dbconfig-common-2.0.19/test/data/dbc_mysql_createuser.remote.sql.txt
--- dbconfig-common-2.0.18/test/data/dbc_mysql_createuser.remote.sql.txt
2021-01-29 21:34:31.0 +0100
+++ dbconfig-common-2.0.19/test/data/dbc_mysql_createuser.remote.sql.txt
2021-03-06 20:56:28.0 +0100
@@ -1,4 +1,4 @@
 CREATE USER IF NOT EXISTS 'testdbuser'@'host2';
 ALTER USER 'testdbuser'@'host2' IDENTIFIED BY 'testdbpass';
-GRANT ALL PRIVILEGES ON testdbname.* TO 'testdbuser'@'host2';
+GRANT ALL PRIVILEGES ON `testdbname`.* TO 'testdbuser'@'host2';
 FLUSH PRIVILEGES;


OpenPGP_signature
Description: OpenPGP digital signature

Bug#984672: oneisenough: AttributeError: module 'time' has no attribute 'clock'

[Markus Koschany]

Package: oneisenough
Version: 0.40-5
Severity: grave
X-Debbugs-Cc: a...@debian.org

oneisenough fails to start because the function time.clock() has been
removed in Python 3.8. I believe time.process_time() is the new
equivalent but I have not tested the patch yet.

Markus



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

Kernel: Linux 4.19.0-14-amd64 (SMP w/4 CPU threads)
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: unable to detect

Versions of packages oneisenough depends on:
ii  fonts-dejavu-core  2.37-2
ii  python33.9.1-1
pn  python3-pygame 

oneisenough recommends no packages.

oneisenough suggests no packages.

Bug#984617: unblock: lowmem/1.49

[Cyril Brulebois]

Hi,

Paul Gevers  (2021-03-06):
> As this relates to d-i, I've explicitly put kibi in CC to give his ACK.

Yes, that's fine; thanks.


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


signature.asc
Description: PGP signature

Bug#983567: Subject: systemd-nspawn: can not run any command related changing the timestamp of files in the i386 bullseye chroot

[Michael Biebl]

Control: fixed -1 247.3-1

On Fri, 26 Feb 2021 11:13:52 +  wrote:
> Package: systemd-container
> Version: 241-7~deb10u4
> Severity: normal
> 
> Dear Maintainer,
> 
> I enter to the bullseye chroot with i386 architecture by systemd-
nspawn command,
> and i can't run any command related changing the timestamp of files
as below:
> debian-buster:~$ mkdir chroot-bullseye-i386
> debian-buster:~$ sudo debootstrap --arch=i386 bullseye chroot-
bullseye-i386 http://deb.debian.org/debian/
> debian-buster:~$ sudo systemd-nspawn -q --resolv-conf=off --
timezone=off -D chroot-bullseye-i386
> root@chroot-bullseye-i386:~# touch /usr/bin/bootctl
> touch: setting times of '/usr/bin/bootctl': Operation not permitted
> root@chroot-bullseye-i386:~# date
> Thu Jan 1 00:00:01 UTC 1970
> 

I can't reproduce that problem with v247.3-1 from testing, so marking
as fixed accordingly.
If this is indeed the same issue as #981007, using systemd from buster-
backports is probably your best option.

Regards,
Michael



signature.asc
Description: This is a digitally signed message part

Bug#984669: xfce4-goodies: xfce4-weather-plugin is broken and is unmaintained upstream

[Derric Atzrott]

Package: xfce4-goodies
Version: 4.12.6
Severity: normal
Tags: upstream

Dear Maintainer,

The xfce4-weather-plugin is broken after an API change at the National
Weather Service. This API change was noted with a deprecation message that
showed up in the program for several years before it finally broke maybe
6 months ago.

The issue has been reported upstream several times by others. There have been
no updates to the plugin upstream for 6 years now, so I believe it to be
unmaintained and abandoned.  I am requesting that the xfce4-weather-plugin
be removed or disabled for the time being.

Thank you


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

Kernel: Linux 4.19.0-11-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfce4-goodies depends on:
ii  mousepad0.4.1-2
ii  notification-daemon 3.20.0-4
ii  plasma-workspace [notification-daemon]  4:5.14.5.1-1
ii  ristretto   0.8.3-1
ii  thunar-archive-plugin   0.4.0-2
ii  thunar-media-tags-plugin0.3.0-2
ii  xfburn  0.5.5-2
ii  xfce4-battery-plugin1.1.2-1
ii  xfce4-clipman-plugin2:1.4.3-1
ii  xfce4-cpufreq-plugin1.2.1-1
ii  xfce4-cpugraph-plugin   1.0.5-2
ii  xfce4-datetime-plugin   0.7.0-2
ii  xfce4-dict  0.8.2-1
ii  xfce4-diskperf-plugin   2.6.1-2
ii  xfce4-fsguard-plugin1.1.0-2
ii  xfce4-genmon-plugin 4.0.1-2
ii  xfce4-mailwatch-plugin  1.2.0-3
ii  xfce4-netload-plugin1.3.1-2
ii  xfce4-notes-plugin  1.8.1-2
ii  xfce4-notifyd [notification-daemon] 0.4.3-1
ii  xfce4-places-plugin 1.7.0-4
ii  xfce4-screenshooter 1.9.3-1
ii  xfce4-sensors-plugin1.3.0-2+b1
ii  xfce4-smartbookmark-plugin  0.5.0-1
ii  xfce4-systemload-plugin 1.2.2-1
ii  xfce4-taskmanager   1.2.2-1
ii  xfce4-terminal  0.8.7.4-2
ii  xfce4-timer-plugin  1.7.0-1
ii  xfce4-verve-plugin  2.0.0-1
ii  xfce4-wavelan-plugin0.6.0-2
ii  xfce4-weather-plugin0.8.10-1
ii  xfce4-whiskermenu-plugin2.3.1-1
ii  xfce4-xkb-plugin1:0.8.1-2

Versions of packages xfce4-goodies recommends:
ii  xfce4-power-manager  1.6.1-1

Versions of packages xfce4-goodies suggests:
pn  gigolo  
ii  parole  1.0.1-1
pn  xfce4-indicator-plugin  
pn  xfce4-mpc-plugin
pn  xfce4-radio-plugin  

-- no debconf information

Bug#984615: xterm: bug in CVE-2021-27135 patch in at least stretch

[Thomas Dickey]

On Sat, Mar 06, 2021 at 06:46:25PM +0100, Sven Joachim wrote:
...
> Run xterm under valgrind and select some text.  Valgrind will be very
> unhappy with xterm 327-2+deb9u1 but should not show up any errors in

valgrind usually has something to say, but (noting that I'm only
interested in what it says when I configure --with-valgrind(*)),
I get a report of ~5000 lines using these options

OPTS="-v \
--num-callers=10 \
--error-limit=no \
--show-reachable=yes \
--leak-resolution=high \
--track-origins=yes \
--leak-check=yes \
--show-reachable=yes"

...and almost all of that is stuff that I can't fix without adding
interfaces in X11, Xt and Xaw.

(*) asan2 also has things to say, but most of that is not useful
without a complete set of debug-libraries (again, X11/Xt/Xaw).

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature

Bug#984617: unblock: lowmem/1.49

[Paul Gevers]

Control: tags -1 confirmed d-i

Hi Samuel,

On 05-03-2021 22:45, Samuel Thibault wrote:
> unblock lowmem/1.49

As this relates to d-i, I've explicitly put kibi in CC to give his ACK.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#984668: python-markdown2: CVE-2021-26813

[Salvatore Bonaccorso]

Source: python-markdown2
Version: 2.3.10-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/trentm/python-markdown2/pull/387
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for python-markdown2.

CVE-2021-26813[0]:
| markdown2 =1.0.1.18, fixed in 2.4.0, is affected by a regular
| expression denial of service vulnerability. If an attacker provides a
| malicious string, it can make markdown2 processing difficult or
| delayed for an extended period of time.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-26813
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-26813

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#984571: apt: Broken python-empy:amd64 Depends on python:any:any

[Julian Andres Klode]

On Sat, Mar 06, 2021 at 08:36:40PM +0100, Guillem Jover wrote:
> Control: reassign -1 apt
> Control: retitle -1 apt: Broken python-empy:amd64 Depends on python:any:any
> 
> Hi!
> 
> On Fri, 2021-03-05 at 11:34:26 +0100, Andreas Beckmann wrote:
> > Package: dpkg
> > Version: 1.19.7
> > Severity: normal
> 
> > I just saw something curious in dpkg's debug output:
> > 
> >   Investigating (0) python-empy:amd64 < 3.3.2-2 @ii mK Ib >
> >   Broken python-empy:amd64 Depends on python:any:any < none @un H > (< 2.8)
> > Considering python:amd64 1 as a solution to python-empy:amd64 -1
> > Removing python-empy:amd64 rather than change python:any:any
> > 
> > What is python:any:any ? Seems to come from dpkg and is probably only
> > cosmetic.

It's what the name says: A package called python:any on the any
architecture. APT creates FOO:any virtual packages for any foo package
that is Multi-Arch: same in order to implement those constraints
correctly.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#984667: CVE-2021-3377

[Moritz Muehlenhoff]

Package: node-ansi-up
Severity: important
Tags: security
X-Debbugs-Cc: Debian Security Team 

This was assigned CVE-2021-3377:
https://doyensec.com/resources/Doyensec_Advisory_ansi_up4_XSS.pdf
https://github.com/drudru/ansi_up/commit/c8c726ed1db979bae4f257b7fa41775155ba2e27

Cheers,
Moritz
  

Bug#984635: unblock: tqdm/4.57.0-2

[Paul Gevers]

Hi Sandro,

On 06-03-2021 19:50, Sandro Tosi wrote:
> to properly fix 980680 tqdm/4.56.2-1 is required, which is a newer
> upstream release than bullseye anyway (since it has 4.51.0-1).
> 
> i'm open to suggestions on how to address it, but i would prefer to
> avoid frankenstein monsters of x.y.zreallym.n.o or giant patches
> against an old version of tqdm that could be addressed by a new
> upstream release.

Me too, but tqdm is a key package and we really want to avoid
unnecessary changes at much as possible at this stage. How much smaller
is the diff between 4.51.0-1 and 4.56.2-1 compared to the current diff?
And what's in the additional delta?

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#984666: CVE-2020-9489

[Moritz Muehlenhoff]

Source: tika
Severity: important
Tags: security
X-Debbugs-Cc: Debian Security Team 

This was assigned CVE-2020-9489:
https://www.openwall.com/lists/oss-security/2020/04/24/1

Cheers,
Moritz

Bug#984665: CVE-2021-25900

[Moritz Muehlenhoff]

Source: rust-smallvec
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

https://rustsec.org/advisories/RUSTSEC-2021-0003.html
https://github.com/servo/rust-smallvec/issues/252

Cheers,
Moritz

Bug#824223: dehydrated: Example cron script

[Reuben Thomas]

Package: dehydrated
Version: 0.6.5-1
Followup-For: Bug #824223

An example cron job script is provided by the hosting company Mythic Beasts
at: https://www.mythic-beasts.com/support/domains/letsencrypt_dns_01

/etc/cron.daily/dehydrated:
#!/bin/sh
exec /usr/bin/dehydrated -c >>/var/log/dehydrated-cron.log 2>&1

/etc/logrotate.d/dehydrated:
/var/log/dehydrated-cron.log
{
rotate 12
monthly
missingok
notifempty
delaycompress
compress
}

It would be great to see this functionality added to the Debian package!

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(100, 'focal-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-44-generic (SMP w/16 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dehydrated depends on:
ii  ca-certificates  20210119~20.04.1
ii  curl 7.68.0-1ubuntu2.4
ii  openssl  1.1.1f-1ubuntu2.2

dehydrated recommends no packages.

dehydrated suggests no packages.

-- no debconf information

Bug#982737: gnome-autoar: CVE-2020-36241

[Salvatore Bonaccorso]

Hi,

On Wed, Mar 03, 2021 at 03:06:26PM +0100, Salvatore Bonaccorso wrote:
> Hi Michael,
> 
> On Mon, Mar 01, 2021 at 11:24:19AM +0100, Michael Biebl wrote:
> > Hi  Salvatore
> > 
> > Am 01.03.21 um 10:57 schrieb Salvatore Bonaccorso:
> > > Hi,
> > > 
> > > On Sat, Feb 13, 2021 at 07:33:00PM +0100, Salvatore Bonaccorso wrote:
> > > > Source: gnome-autoar
> > > > Version: 0.2.4-2
> > > > Severity: important
> > > > Tags: security upstream
> > > > Forwarded: https://gitlab.gnome.org/GNOME/gnome-autoar/-/issues/7
> > > > X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> > > > 
> > > > Control: found -1 0.2.3-2
> > > > 
> > > > Hi,
> > > > 
> > > > The following vulnerability was published for gnome-autoar.
> > > > 
> > > > CVE-2020-36241[0]:
> > > > | autoar-extractor.c in GNOME gnome-autoar through 0.2.4, as used by
> > > > | GNOME Shell, Nautilus, and other software, allows Directory Traversal
> > > > | during extraction because it lacks a check of whether a file's parent
> > > > | is a symlink to a directory outside of the intended extraction
> > > > | location.
> > > > 
> > > > If possible this ideally should be fixed in bullseye in time.
> > > 
> > > Would it be possible to cherry-pick the fix so we have the fix
> > > included in bullseye?
> > 
> > 
> > Seems reasonable. That said, I haven't really done any GNOME related uploads
> > for quite a while.
> 
> Jupp thanks for the reply! (I just pinged explicitly the last couple of
> uploaders). Anyone else from the team who could handle that?

Probably as well on your radar already, but there is as well a
regression fix needed for it as per

https://gitlab.gnome.org/GNOME/gnome-autoar/-/commit/cc4e8b7ccc973ac69d75a7423fbe1bcdc51e2cb3

Regards,
Salvatore

Bug#984615: xterm: bug in CVE-2021-27135 patch in at least stretch

[Thomas Dickey]

On Sat, Mar 06, 2021 at 06:07:43PM +, Thorsten Glaser wrote:
> Sven Joachim dixit:
> 
> >I see that this might be a problem (albeit unlikely to happen in
> >practice), however I have trouble understanding exactly where a
> >use-after-realloc bug comes into play.  Maybe Thorsten can help me fix
> >my blindness?
> 
> The next time something is selected, the code a little further
> up will check if the allocated size is sufficient, and, if so,
> use screen->selection_data which was the pre-realloc address of
> line.
> 
> >> I am glad and surprised that sid is okay and there doesn't seem to be
> 
> The code in sid completely differs (structures, variable names, etc).

The renaming (selection_size) comes from patch #338,
which looks like this item:

Patch #338 - 2018/12/09
 * amend  solution  for  Debian  #758633  to  ensure that replies for
   bracketed  paste  are  not  sent  while processing a selection for
   exec-formatted (Debian #913237).
 
> >suggestion you could also apply the patches to the SaltTextAway()
> >function from xterm 365e.
> 
> If 365e is like 366 (currently in sid), you’ll have lots of fun due
> to the renamed everything.

366 is current.  I have some changes for 367 which I'll put out after
seeing what I can do to improve performance with fwvm active-icon.
 
> I’d rather Tom changed xterm upstream to address the realloc-failure
> difference. I know he reads Debian bugreports ;-) and he’s really
> busy so probably takes longer to respond.

it used to be the case that downstream would ask my opinion on patches
like this -- it's been a while since anyone did

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature

Bug#984664: pygments: CVE-2021-20270

[Salvatore Bonaccorso]

Source: pygments
Version: 2.7.1+dfsg-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/pygments/pygments/issues/1625
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for pygments.

CVE-2021-20270[0].

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-20270
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-20270
[1] https://github.com/pygments/pygments/issues/1625
[2] 
https://github.com/pygments/pygments/commit/f91804ff4772e3ab41f46e28d370f57898700333

Can you please try to make the fix land in bullseye?

Regards,
Salvatore

Bug#984571: apt: Broken python-empy:amd64 Depends on python:any:any

[Guillem Jover]

Control: reassign -1 apt
Control: retitle -1 apt: Broken python-empy:amd64 Depends on python:any:any

Hi!

On Fri, 2021-03-05 at 11:34:26 +0100, Andreas Beckmann wrote:
> Package: dpkg
> Version: 1.19.7
> Severity: normal

> I just saw something curious in dpkg's debug output:
> 
>   Investigating (0) python-empy:amd64 < 3.3.2-2 @ii mK Ib >
>   Broken python-empy:amd64 Depends on python:any:any < none @un H > (< 2.8)
> Considering python:amd64 1 as a solution to python-empy:amd64 -1
> Removing python-empy:amd64 rather than change python:any:any
> 
> What is python:any:any ? Seems to come from dpkg and is probably only
> cosmetic.
> 
> Package: python-empy
> Source: empy
> Version: 3.3.2-2
> Installed-Size: 289
> Maintainer: Jose Luis Rivero 
> Architecture: all
> Provides: python2.7-empy
> Depends: python:any (<< 2.8), python:any (>= 2.7~)
> Conflicts: python3-empy (<= 3.3-8)
> 
> Full piuparts log attached in case you are interested.

This output is coming from apt, thus reassigning.

Thanks,
Guillem

Bug#926276: Should guacamole-client be removed?

[Salvatore Bonaccorso]

Hi,

On Wed, Apr 03, 2019 at 12:27:25PM +, Mike Gabriel wrote:
> Hi Moritz,
> 
> On  Di 02 Apr 2019 22:04:34 CEST, Moritz Muehlenhoff wrote:
> 
> > Source: guacamole-client
> > Severity: serious
> > 
> > Should guacamole-client be removed?
> > 
> > guacamole-client hasn't been updated since 2016, is removed from testing
> > since 1.5 years and has four RC bugs at this point
> > 
> > Cheers,
> > Moritz
> 
> My suggestion to 'Nik was to drop FreeRDP support for a while and fix the
> other issues and keep that in unstable.
> 
> However, it's the maintainers call at the end.

Almost 2 years later: Should maybe now guacamole-client be removed
from the archive alltogether? The version currently in sid lacks quite
behind the current upstream version, has security-bugs open (and at
least one quite hard to backport fixes to the version in sid).

As such I think it would be better to remove the package as well in
unstable?

Regards,
Salvatore

Bug#984663: more.c: remove redeclaration of arrays "pr_fmt[]" and "send_date[]"

[Bjarni Ingi Gislason]

Source: nn
Version: 6.7.3-14
Severity: normal
Tags: patch

Dear Maintainer,

>From 1cafd43f0c34f4397170537530396020725fe74f Mon Sep 17 00:00:00 2001
>From: Bjarni Ingi Gislason 
>Date: Sat, 6 Mar 2021 19:24:04 +
>Subject: [PATCH] more.c: remove redeclaration of arrays "pr_fmt[]" and
> "send_date[]"

Signed-off-by: Bjarni Ingi Gislason 
---
 more.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/more.c b/more.c
index 08ce974..843ead0 100644
--- a/more.c
+++ b/more.c
@@ -391,7 +391,6 @@ more(article_header * ah, int mode, int screen_offset)
 char   *fname, *hdrline;
 #defineNPR_FMT  200
 charpr_fmt[NPR_FMT], send_date[40];
-charpr_fmt[200], send_date[40];
 int match_expr, shade_overlap, shade_line;
 int*key_map;
 key_typecur_key;
-- 
2.30.1



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

Kernel: Linux 5.10.9-1 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- debconf information excluded

-- 
Bjarni I. Gislason

Bug#984662: ntp: Please integrate ntp-wait with systemd's time-sync.target

[nandhp]

Package: ntp
Version: 1:4.2.8p12+dfsg-4
Severity: normal

Dear Maintainer,

Many embedded systems have no hardware real-time clock. Debian
provides the fake-hwclock package to maintain reasonable time across
reboots. However, this means that there will be a noticeable time skip
after system startup, when NTP synchronizes the clock. This time skip
may be very large if the system has been turned off for a long time.

Systemd provides time-sync.target, which units like timers depend on
to avoid being affected by such time skips. The ntp package provides
an ntp-wait program that waits until NTP has synchronized the system
clock. However, the ntp package does not install a systemd service to
block the time-sync.target from starting until ntp-wait succeeds.

Please install a service similar to these ones shipped by other NTP
distributors:
https://github.com/ntpsec/ntpsec/blob/master/etc/ntp-wait.service
https://src.fedoraproject.org/rpms/ntp/blob/f25/f/ntp-wait.service
https://build.opensuse.org/package/view_file/openSUSE:Factory/ntp/conf.ntp-wait.service

Thanks.
-nandhp

Bug#984661: ITP: ruby-pg-query -- PostgreSQL query parsing and normalization library

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 

Packaging of https://rubygems.org/gems/pg_query

This will replace ruby-gitlab-pg-query (which is a fork). Dependency of 
gitlab 13.8.x

Bug#983595: linux-image-5.10.0-3-amd64: [regression] Kernel panic on resume from sleep

[Zbynek Michl]

So really it was a bug in the alx driver - there was a wrong call order on
resume.

Jakub Kicinski has fixed it in the vanilla kernel:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=a4dcfbc4ee2218abd567d81d795082d8d4afcdf6

More details are available in the kernel mailing list:
https://lore.kernel.org/netdev/CAJH0kmw00RHaKXqxRFi-7aSj2waYaMBYpp3v1fnC-=237be...@mail.gmail.com/T/#t

This bug report can be closed now.

Thanks
Zbynek

Bug#981878: ruby-gitlab-pg-query downloads from the internet during the build

[Pirate Praveen]

On Thu, 04 Feb 2021 20:49:39 +0200 Adrian Bunk  wrote:
> /usr/lib/ruby/2.7.0/net/http.rb:960:in `initialize': Failed to open 
TCP connection to codeload.github.com:443 (Network is unreachable - 
connect(2) for "codeload.github.com" port 443) (Errno::ENETUNREACH)

>from /usr/lib/ruby/2.7.0/net/http.rb:960:in `open'
>from /usr/lib/ruby/2.7.0/net/http.rb:960:in `block in connect'
>from /usr/lib/ruby/2.7.0/timeout.rb:95:in `block in timeout'
>from /usr/lib/ruby/2.7.0/timeout.rb:105:in `timeout'
>from /usr/lib/ruby/2.7.0/net/http.rb:958:in `connect'
>from /usr/lib/ruby/2.7.0/net/http.rb:943:in `do_start'
>from /usr/lib/ruby/2.7.0/net/http.rb:932:in `start'
>from /usr/lib/ruby/2.7.0/open-uri.rb:346:in `open_http'
>from /usr/lib/ruby/2.7.0/open-uri.rb:764:in `buffer_open'
>from /usr/lib/ruby/2.7.0/open-uri.rb:235:in `block in open_loop'
>from /usr/lib/ruby/2.7.0/open-uri.rb:233:in `catch'
>from /usr/lib/ruby/2.7.0/open-uri.rb:233:in `open_loop'
>from /usr/lib/ruby/2.7.0/open-uri.rb:174:in `open_uri'
>from /usr/lib/ruby/2.7.0/open-uri.rb:744:in `open'
>from /usr/lib/ruby/2.7.0/open-uri.rb:50:in `open'
>from extconf.rb:19:in `block in '
>from extconf.rb:18:in `open'
>from extconf.rb:18:in `'
> /usr/lib/ruby/2.7.0/net/http.rb:960:in `initialize': Network is 
unreachable - connect(2) for "codeload.github.com" port 443 
(Errno::ENETUNREACH)

>from /usr/lib/ruby/2.7.0/net/http.rb:960:in `open'
>from /usr/lib/ruby/2.7.0/net/http.rb:960:in `block in connect'

This gem (gitlab-pg_query) is a fork of pg_query. gitlab is now using 
pg_query directly instead of ther fork. I'm uploading pg_query gem as 
ruby-pg-query with a fix for this issue. Once ruby-pg-query is accepted 
and its reverse dependencies switch to the new package, I will request 
removal of this package.

Bug#984660: more.c: some changes

[Bjarni Ingi Gislason]

Source: nn
Version: 6.7.3-14
Severity: normal
Tags: patch

Dear Maintainer,

>From 68d6969f3f7b03fbd308a87cfa50f4ffba48dad5 Mon Sep 17 00:00:00 2001
>From: Bjarni Ingi Gislason 
>Date: Sat, 6 Mar 2021 19:11:15 +
>Subject: [PATCH] more.c: some changes

  Use 8bit data, change "data_bits" from 7 to 8.

  Add a declaration for "ndelayed_msg", that is the size of array
"delayed_msg[]".

  Use "snprintf()" instead of "sprintf()".

  Correct the value for "attr" from "NULL_FCT" to "NULL_FCT_INT".

  Add a constant "NPR_FMT" for the number of elements in "pr_fmt[]".

Signed-off-by: Bjarni Ingi Gislason 
---
 more.c | 17 ++---
 1 file changed, 10 insertions(+), 7 deletions(-)

diff --git a/more.c b/more.c
index 0cebb20..08ce974 100644
--- a/more.c
+++ b/more.c
@@ -49,7 +49,7 @@ char   *header_lines = NULL;
 
 int min_pv_window = 7;
 int wrap_headers = 6;
-int data_bits = 7;
+int data_bits = 8;
 int scroll_clear_page = 1;
 int expired_msg_delay = 1;
 char   *trusted_escapes = NULL;
@@ -74,6 +74,7 @@ extern int  mouse_state;
 extern int  alt_cmd_key, in_menu_mode, any_message;
 extern long n_selected;
 
+extern const size_t ndelayed_msg; /* size of array "delayed_msg[]" */
 extern char delayed_msg[];
 
 static int  rot13_must_init = 1;
@@ -157,7 +158,7 @@ get_header_field(char code, char **namep, char **valp, 
register article_header *
/* FALLTHROUGH */
case 'G':
if (ah->a_number > 0) {
-   sprintf(special, "%s/%ld",
+   snprintf(special, FILENAME, "%s/%ld",
current_group->group_name, (long) ah->a_number);
lp = special;
} else
@@ -182,7 +183,7 @@ get_header_field(char code, char **namep, char **valp, 
register article_header *
break;
 
case 'i':
-   sprintf(special, "#%ld fl=%ld re=%d li=%d hp=%ld fp=%ld lp=%ld 
ts=%ld",
+   snprintf(special, FILENAME, "#%ld fl=%ld re=%d li=%d hp=%ld fp=%ld 
lp=%ld ts=%ld",
(long) ah->a_number, (long) ah->flag, (int) ah->replies,
ah->lines, ah->hpos, ah->fpos, (long) ah->lpos,
(long) ah->t_stamp);
@@ -213,7 +214,7 @@ next_header_field(char **namep, char **valp, fct_type_int * 
attrp)
 fct_type_intattr;
 
 while (*scan_codes) {
-   attr = NULL_FCT;
+   attr = NULL_FCT_INT;
*namep = NULL;
 
switch (*scan_codes) {
@@ -388,6 +389,8 @@ more(article_header * ah, int mode, int screen_offset)
 flag_type   in_digest = ah->flag & A_DIGEST;
 article_header  digestah;
 char   *fname, *hdrline;
+#defineNPR_FMT  200
+charpr_fmt[NPR_FMT], send_date[40];
 charpr_fmt[200], send_date[40];
 int match_expr, shade_overlap, shade_line;
 int*key_map;
@@ -511,7 +514,7 @@ more(article_header * ah, int mode, int screen_offset)
group_name += len - maxl;
}
if (mode & (MM_PREVIEW | MM_DIGEST) || n_selected == 0)
-   sprintf(pr_fmt,
+   snprintf(pr_fmt, NPR_FMT,
"\1\2--%s-- %s%s %s--%%s--%%s\1",
group_name,
(mode & MM_DIGEST) ? "DIGEST" :
@@ -519,14 +522,14 @@ more(article_header * ah, int mode, int screen_offset)
(ah->flag & A_NEXT_SAME) ? "+next" : "",
novice ? "--help:?" : "");
else
-   sprintf(pr_fmt,
+   snprintf(pr_fmt, NPR_FMT,
"\1\2--%s-- %ld MORE%s %s--%%s--%%s\1",
group_name,
n_selected,
(ah->flag & A_NEXT_SAME) ? "+next" : "",
novice ? "--help:?" : "");
 } else
-   sprintf(pr_fmt,
+   snprintf(pr_fmt, NPR_FMT,
"\1\2-- %s%s %s-%%s%s-%%s\1",
(mode & MM_PREVIEW) ? "PREVIEW " : "",
(mode & MM_DIGEST) ? "FULL DIGEST" :
-- 
2.30.1



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

Kernel: Linux 5.10.9-1 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- debconf information excluded

-- 
Bjarni I. Gislason

Bug#976462: tech-ctte: Should dbgsym files be compressed via objcopy --compress-debug-section or not?

[Jakub Wilk]

* Elana Hashman , 2021-02-17, 11:06:
Would you be able to research some representative slice of popular 
packages that would be affected by the policy change (at least 10) and 
share the on-disk sizes with compression vs. without?


Not exactly what you asked Niels for, but...

A few months ago I recompressed whole buster/main/amd64 to see what the 
effect of ditching --compress-debug-sections would be.

Raw data for this experiment is available here:
https://github.com/jwilk/lets-shrink-dbgsym/releases/download/20200708/buster-main-amd64-20200708.tsv.xz
The columns are:
* file name
* original .deb size
* recompressed .deb size
* original installed size
* recompressed installed size

Note that some of the .deb size savings might be caused by the fix for 
#868674 (for packages that haven't been rebuilt since the fix).


--
Jakub Wilk

Bug#984647: forensics-extra's autopkg tests always fail on 32bit archs

[Eriberto]

Hi Matthias,

Thanks a lot for your report. This issue was identificated in 2.28
version by me. I wrote in file list-of-packages-extra:

-stegosuite FED
+stegosuite FGR # FIXME, dependencies not available for i386 in autopkgtest

In other words, I moved stegosuite from Depends (in forensics-extra)
to Recommends (in forensics-extra-gui). However, because of a mistake
of mine, a new debian/control file wasn't generated by gen-control.sh
command. I will release the revision 2.29 to fix it. Thanks again.

Eriberto

Bug#984635: unblock: tqdm/4.57.0-2

[Sandro Tosi]

> What matters here is the delta between testing and unstable:
>  88 files changed, 2803 insertions(+), 1897 deletions(-)

that's right: the 4.56.2-1 upload fixed 980680 while this unblock
request is for 4.57.0-2 which fixes #983007, but you're right i didnt
diff testing..unstable

> Please review your own request taking into account all uploads since the
> package currently in testing. I would prefer a revert of the upstream
> version and just a fix for the FTBFS (#980680) in bullseye, is fixing
> that an option without the new upstream release?

to properly fix 980680 tqdm/4.56.2-1 is required, which is a newer
upstream release than bullseye anyway (since it has 4.51.0-1).

i'm open to suggestions on how to address it, but i would prefer to
avoid frankenstein monsters of x.y.zreallym.n.o or giant patches
against an old version of tqdm that could be addressed by a new
upstream release.

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

Bug#980516: Bug:980516: mate-power-manager: Crashes soon after startup

[Bernhard Übelacker]

Dear Maintainer,
I tried to get some more information from the kernel message.

This led me to this line:
  at 0x5556ee99: file gpm-engine.c, line 540.

There the array is dereferenced unconditionally:
  
https://sources.debian.org/src/mate-power-manager/1.24.2-1/src/gpm-engine.c/#L540
  539   array = up_client_get_devices2 (engine->priv->client);
  540   for (i=0;ilen;i++) {

Therefore the assertion message just before the segfault
seems related:
  up_client_get_devices2: assertion 'UP_IS_CLIENT (client)' failed

That points to this line in upower:
  https://cgit.freedesktop.org/upower/tree/libupower-glib/up-client.c#n117
  117   g_return_val_if_fail (UP_IS_CLIENT (client), NULL);

And therefore the "array" seems to have received the NULL pointer.

Therefore the value given to function up_client_get_devices2
seems already suspicious.


Unfortunately I have not found any related
entry in upstream bug trackers.
Details in attached file.

Kind regards,
Bernhard

# Bullseye/testing amd64 qemu VM 2021-03-06


apt update
apt dist-upgrade


systemd-coredump mate xserver-xorg lightdm gdb mate-power-manager-dbgsym


reboot




https://wiki.debian.org/InterpretingKernelOutputAtProcessCrash

From submitter:
[  349.205142] mate-power-mana[3580]: segfault at 8 ip 5641ef93ae99 sp 
7ffcb468bf60 error 4 in mate-power-manager[5641ef928000+1a000]
[  349.205154] Code: 00 49 8b 44 24 18 31 db 48 8b 78 20 e8 b0 01 ff ff 4c 89 
e7 e8 68 f5 ff ff 49 8b 44 24 18 48 8b 78 08 e8 fa e3 fe ff 48 89 c5 <8b> 40 08 
85 c0 74 1a 48 8b 45 00 89 da 4c 89 e7 83 c3 01 48 8b 34

error 4 == 0b0100:
- 0: no page found
- 0: read access
- 0: kernel-mode access

echo -n "find /b ..., ..., 0x" && \
echo "00 49 8b 44 24 18 31 db 48 8b 78 20 e8 b0 01 ff ff 4c 89 e7 e8 68 f5 ff 
ff 49 8b 44 24 18 48 8b 78 08 e8 fa e3 fe ff 48 89 c5 <8b> 40 08 85 c0 74 1a 48 
8b 45 00 89 da 4c 89 e7 83 c3 01 48 8b 34" \
 | sed 's/[<>]//g' | sed 's/ /, 0x/g'

find /b ..., ..., 0x00, 0x49, 0x8b, 0x44, 0x24, 0x18, 0x31, 0xdb, 0x48, 0x8b, 
0x78, 0x20, 0xe8, 0xb0, 0x01, 0xff, 0xff, 0x4c, 0x89, 0xe7, 0xe8, 0x68, 0xf5, 
0xff, 0xff, 0x49, 0x8b, 0x44, 0x24, 0x18, 0x48, 0x8b, 0x78, 0x08, 0xe8, 0xfa, 
0xe3, 0xfe, 0xff, 0x48, 0x89, 0xc5, 0x8b, 0x40, 0x08, 0x85, 0xc0, 0x74, 0x1a, 
0x48, 0x8b, 0x45, 0x00, 0x89, 0xda, 0x4c, 0x89, 0xe7, 0x83, 0xc3, 0x01, 0x48, 
0x8b, 0x34




gdb -q
set width 0
set pagination off
file /usr/bin/mate-power-manager
tb main
run

info target
...
0xd760 - 0x55575a11 is .text
...


find /b 0xd760, 0x55575a11, 0x00, 0x49, 0x8b, 0x44, 0x24, 
0x18, 0x31, 0xdb, 0x48, 0x8b, 0x78, 0x20, 0xe8, 0xb0, 0x01, 0xff, 0xff, 0x4c, 
0x89, 0xe7, 0xe8, 0x68, 0xf5, 0xff, 0xff, 0x49, 0x8b, 0x44, 0x24, 0x18, 0x48, 
0x8b, 0x78, 0x08, 0xe8, 0xfa, 0xe3, 0xfe, 0xff, 0x48, 0x89, 0xc5, 0x8b, 0x40, 
0x08, 0x85, 0xc0, 0x74, 0x1a, 0x48, 0x8b, 0x45, 0x00, 0x89, 0xda, 0x4c, 0x89, 
0xe7, 0x83, 0xc3, 0x01, 0x48, 0x8b, 0x34
0x5556ee6f 
1 pattern found.

b * (0x5556ee6f + 42)
Breakpoint 2 at 0x5556ee99: file gpm-engine.c, line 540.

info b
Num Type   Disp Enb AddressWhat
2   breakpoint keep y   0x5556ee99 in 
gpm_engine_coldplug_idle_cb at gpm-engine.c:540

disassemble /r 0x5556ee6f, 0x5556ee6f + 62
Dump of assembler code from 0x5556ee6f to 0x5556eead:
   0x5556ee6f : 00 49 8badd 
   %cl,-0x75(%rcx)
   0x5556ee72 : 44 24 18
rex.R and $0x18,%al
   0x5556ee75 : 31 db   xor 
   %ebx,%ebx
   0x5556ee77 : 48 8b 78 20 mov 
   0x20(%rax),%rdi
   0x5556ee7b : e8 b0 01 ff ff  
call   0xf030 
   0x5556ee80 : 4c 89 e7mov 
   %r12,%rdi
   0x5556ee83 : e8 68 f5 ff ff  
call   0x5556e3f0 
   0x5556ee88 :49 8b 44 24 18  mov 
   0x18(%r12),%rax
   0x5556ee8d :48 8b 78 08 mov 
   0x8(%rax),%rdi
   0x5556ee91 :e8 fa e3 fe ff  
call   0xd290 
   0x5556ee96 :48 89 c5mov 
   %rax,%rbp
***0x5556ee99 :8b 40 08mov 
   0x8(%rax),%eax
   0x5556ee9c :85 c0   
test   %eax,%eax
   0x5556ee9e :74 1a   je  
   0x5556eeba 
   0x5556eea0 :48 8b 45 00 mov 
   0x0(%rbp),%rax
   0x5556eea4 :89 da   mov 
   %ebx,%edx
   0x5556eea6 :4c 89 e7mov 
   %r12,%rdi
   0x5556eea9 :83 c3 01add 
   $0x1,%ebx
   0x5556eeac :48 8b 34 d0 mov 
   (%rax,%rdx,8),%rsi
End of assembler dump.




mate-power-manager-dbgsym_1.24.2-1_amd64.deb
https://sources.debian.org/src/mate-power-manager/1.24.2-1/src/gpm-engine.c/#L540
for (i=0;ilen;i++) {

https://git.mate-desktop.org/mate-power-manager/tree/src/gpm-engine.c#n538

https://cgit.freedesktop.org/upower/tree/libupower-glib/up-client.c#n117


(gdb) ptype /o GPtrArray
type = struct _GPtrArray {
/*0  | 

Bug#984641: ifmail: Status files for non-default domains are created in directories without domain hex number suffix

[Marco d'Itri]

On Mar 06, Björn Wiberg  wrote:

> Perhaps this is something that can be reported upstream?
Come on, there has not been an upstream maintainer in 20 years.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#984659: more.c: fix warnings issued by the compiler

[Bjarni Ingi Gislason]

Source: nn
Version: 6.7.3-14
Severity: normal
Tags: patch

Dear Maintainer,

>From 1122632ccd762a88c941c54140e258d7017c3cce Mon Sep 17 00:00:00 2001
>From: Bjarni Ingi Gislason 
>Date: Sat, 6 Mar 2021 18:31:25 +
>Subject: [PATCH] more.c: fix warnings issued by the compiler

more.c: In function 'next_header_field':
more.c:213:5: error: unknown type name 'fct_type'
  213 | fct_typeattr;
  | ^~~~

more.c: In function 'more':
more.c:1492:6: warning: "/*" within comment [-Wcomment]
 1492 |  /* XXX: fall here? */
  |

###

  Change the type of "attr" from "fct_type" to "fct_type_int".

  Change the '*(' to '*/' to finish a comment.

Signed-off-by: Bjarni Ingi Gislason 
---
 more.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/more.c b/more.c
index 1da0317..0cebb20 100644
--- a/more.c
+++ b/more.c
@@ -210,7 +210,7 @@ scan_header_fields(char *fields, article_header * ah)
 int
 next_header_field(char **namep, char **valp, fct_type_int * attrp)
 {
-fct_typeattr;
+fct_type_intattr;
 
 while (*scan_codes) {
attr = NULL_FCT;
@@ -1488,7 +1488,7 @@ alt_key:
regular_expr = regcomp(fname);
match_lines = 0;
}
-   /* FALLTHROUGH *(
+   /* FALLTHROUGH */
/* XXX: fall here? */
case K_NEXT_MATCH:
if (regular_expr == NULL) {
-- 
2.30.1



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

Kernel: Linux 5.10.9-1 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- debconf information excluded

-- 
Bjarni I. Gislason

Bug#984635: unblock: tqdm/4.57.0-2

[Paul Gevers]

Control: tags -1 moreinfo

Hi Sandro,

On 06-03-2021 05:42, Sandro Tosi wrote:
> the last upload of tqdm fixes a RC bug

Thanks.

> [ Risks ]
> trivial fix

What matters here is the delta between testing and unstable:
 88 files changed, 2803 insertions(+), 1897 deletions(-)

That's not "trivial fix".

> [ Checklist ]
>   [x] all changes are documented in the d/changelog
>   [x] I reviewed all changes and I approve them
>   [x] attach debdiff against the package in testing

Please review your own request taking into account all uploads since the
package currently in testing. I would prefer a revert of the upstream
version and just a fix for the FTBFS (#980680) in bullseye, is fixing
that an option without the new upstream release?

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#981347: [debian-mysql] Bug#981347: Bug#981347: mariadb-10.5 FTBFS on kfreebsd

[Otto Kekäläinen]

The freebsd build still fails, now on some files that are not built:

>From 
>https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.5=kfreebsd-amd64=1%3A10.5.9-1=1614977404=0
*
dh_install: warning: Cannot find (any matches for)
"lib/systemd/system/mariadb@bootstrap.service.d/use_galera_new_cluster.conf"
(tried in ., debian/tmp)
dh_install: warning: mariadb-server-10.5 missing files:
lib/systemd/system/mariadb@bootstrap.service.d/use_galera_new_cluster.conf
dh_install: warning: Cannot find (any matches for)
"lib/systemd/system/mysql.service" (tried in ., debian/tmp)
dh_install: warning: mariadb-server-10.5 missing files:
lib/systemd/system/mysql.service
dh_install: warning: Cannot find (any matches for)
"lib/systemd/system/mysqld.service" (tried in ., debian/tmp)
dh_install: warning: mariadb-server-10.5 missing files:
lib/systemd/system/mysqld.service
dh_install: warning: Cannot find (any matches for)
"usr/bin/galera_new_cluster" (tried in ., debian/tmp)
dh_install: warning: mariadb-server-10.5 missing files:
usr/bin/galera_new_cluster
dh_install: warning: Cannot find (any matches for)
"usr/bin/galera_recovery" (tried in ., debian/tmp)
dh_install: warning: mariadb-server-10.5 missing files: usr/bin/galera_recovery
dh_install: warning: Cannot find (any matches for)
"usr/bin/mariadb-service-convert" (tried in ., debian/tmp)
dh_install: warning: mariadb-server-10.5 missing files:
usr/bin/mariadb-service-convert
dh_install: warning: Cannot find (any matches for)
"usr/lib/mysql/plugin/disks.so" (tried in ., debian/tmp)
dh_install: warning: mariadb-server-10.5 missing files:
usr/lib/mysql/plugin/disks.so
*

These are various files referenced from the
mariadb-server-10.5.install file. All have a direct relation to
systemd, apart from maybe disks.so (I don't know what it does at all).

I suspect that these files are missing as the debian/control defines
"libsystemd-dev [linux-any]" as the package is not available for
kfreebsd (https://packages.debian.org/sid/libsystemd-dev).

Feel free to open a new merge request if you figure out a sensible
solution to this.

Bug#984615: xterm: bug in CVE-2021-27135 patch in at least stretch

[Thorsten Glaser]

Sven Joachim dixit:

>I see that this might be a problem (albeit unlikely to happen in
>practice), however I have trouble understanding exactly where a
>use-after-realloc bug comes into play.  Maybe Thorsten can help me fix
>my blindness?

The next time something is selected, the code a little further
up will check if the allocated size is sufficient, and, if so,
use screen->selection_data which was the pre-realloc address of
line.

>> I am glad and surprised that sid is okay and there doesn't seem to be

The code in sid completely differs (structures, variable names, etc).

>suggestion you could also apply the patches to the SaltTextAway()
>function from xterm 365e.

If 365e is like 366 (currently in sid), you’ll have lots of fun due
to the renamed everything.

I’d rather Tom changed xterm upstream to address the realloc-failure
difference. I know he reads Debian bugreports ;-) and he’s really
busy so probably takes longer to respond.

bye,
//mirabilos
-- 
>> Why don't you use JavaScript? I also don't like enabling JavaScript in
> Because I use lynx as browser.
+1
-- Octavio Alvarez, me and ⡍⠁⠗⠊⠕ (Mario Lang) on debian-devel

Bug#984658: more.c: fix warnings issued by the compiler

[Bjarni Ingi Gislason]

Source: nn
Version: 6.7.3-14
Severity: normal
Tags: patch

Dear Maintainer,

>From 303ca6f90afa8d27274f8bfeef0fd46bb634358a Mon Sep 17 00:00:00 2001
>From: Bjarni Ingi Gislason 
>Date: Sat, 6 Mar 2021 17:59:17 +
>Subject: [PATCH] more.c: fix warnings issued by the compiler

  Add header file "more.h".

  Comment out declaration of "STANDOUT", is declared in "nn_term.h".

  Fix type of parameter "attrp" in "next_header_field()".

  Fix the type of "hdrattr", it is "fct_type_int", not just "fct_type".

  Add several /* FALLTHROUGH */ to avoid warnings from the compiler.

Signed-off-by: Bjarni Ingi Gislason 
---
 more.c | 11 ---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/more.c b/more.c
index 99280e0..1da0317 100644
--- a/more.c
+++ b/more.c
@@ -22,6 +22,7 @@
 #include "macro.h"
 #include "match.h"
 #include "menu.h"
+#include "more.h"
 #include "news.h"
 #include "regexp.h"
 #include "save.h"
@@ -69,7 +70,7 @@ extern char*folder_save_file, *default_save_file;
 extern int  show_art_next_invalid;
 extern int  mouse_y;
 extern int  mouse_state;
-extern int  STANDOUT;
+/* extern int  STANDOUT; */ /* declared in "nn_term.h" */
 extern int  alt_cmd_key, in_menu_mode, any_message;
 extern long n_selected;
 
@@ -207,7 +208,7 @@ scan_header_fields(char *fields, article_header * ah)
 }
 
 int
-next_header_field(char **namep, char **valp, fct_type * attrp)
+next_header_field(char **namep, char **valp, fct_type_int * attrp)
 {
 fct_typeattr;
 
@@ -391,7 +392,7 @@ more(article_header * ah, int mode, int screen_offset)
 int match_expr, shade_overlap, shade_line;
 int*key_map;
 key_typecur_key;
-fct_typehdrattr;
+fct_type_inthdrattr;
 char   *match_start, *match_end = NULL;
 int open_modes, o_mode;
 
@@ -1116,6 +1117,7 @@ alt_key:
STATE(K_CONTINUE);
}
}
+   /* FALLTHROUGH */
/* fall through??? */
 
case K_NEXT_PAGE:
@@ -1204,6 +1206,7 @@ alt_key:
c = alt_cmd_key;
goto alt_key;
}
+   /* FALLTHROUGH */
/* XXX: fall-thru? */
case K_QUIT:
ah->attr = A_LEAVE_NEXT;
@@ -1485,6 +1488,7 @@ alt_key:
regular_expr = regcomp(fname);
match_lines = 0;
}
+   /* FALLTHROUGH *(
/* XXX: fall here? */
case K_NEXT_MATCH:
if (regular_expr == NULL) {
@@ -1597,6 +1601,7 @@ alt_key:
if (mode & MM_PREVIEW)
more_return(MC_PREVIEW_OTHER);
 
+   /* FALLTHROUGH */
/* fall thru to "default" */
 
default:
-- 
2.30.1



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

Kernel: Linux 5.10.9-1 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- debconf information excluded

-- 
Bjarni I. Gislason

Bug#662024: http://ftp-master.debian.org/new.822: invalid e-mail addresses

[Jakub Wilk]

Control: reopen -1

This is happening again:

  $ wget -q -O- http://ftp-master.debian.org/new.822 | grep 'Sponsored.*@.*@'
  Sponsored-By: buildd_all-x86-csail...@buildd.debian.org@debian.org
  Sponsored-By: buildd_arm64-arm-conova...@buildd.debian.org@debian.org
  Sponsored-By: buildd_arm64-arm-conova...@buildd.debian.org@debian.org
  ...

--
Jakub Wilk

Bug#982966: python3-pygame: Using pygame 1.9.6 crashes Wayland (hard) and X

[Bernhard Übelacker]

Hello Richard,
I tried the steps below [1] but it did not trigger
a crash inside a gnome/wayland test VM.

Maybe you could install the package systemd-coredump, trigger
the crash once more and retrieve the logging from the current
boot by 'journalctl -b0 > journalctl.txt' and forward the
lines related to the crash to this bug?

More informations on retrieving a backtrace could be found in [2].

Kind regards,
Bernhard


[2] https://wiki.debian.org/HowToGetABacktrace

[1] apt install systemd-coredump gnome python3-pygame git

mkdir flappybird
cd flappybird
git clone https://github.com/clear-code-projects/FlappyBird_Python
cd FlappyBird_Python
sed -i 's/04B_19.ttf/04B_19.TTF/g' flappy_update.py
python3 flappy_update.py

Bug#984615: xterm: bug in CVE-2021-27135 patch in at least stretch

[Sven Joachim]

On 2021-03-06 02:49 +0530, Utkarsh Gupta wrote:

> Hi Thorsten
>
> On Sat, Mar 6, 2021 at 2:25 AM Thorsten Glaser  wrote:
>> debian/patches/CVE-2021-27135.patch changes button.c line (after
>> patching) 3747 to:
>>
>>line = realloc(line, screen->selection_size);
>>
>> But “line” is a local variable, the address of the buffer must
>> be stored in the one handed out, too, so please change this to:
>>
>> if ((have * 2) < (size_t) j) {
>> Char *next = realloc(line, have + 1);
>> if (next) {
>> screen->selection_data = line = next;
>> screen->selection_size = have + 1;
>> }
>> }
>>
>> This also deals properly with realloc failures (since we’re
>> shrinking, ignore them and just keep the older, larger area).

I see that this might be a problem (albeit unlikely to happen in
practice), however I have trouble understanding exactly where a
use-after-realloc bug comes into play.  Maybe Thorsten can help me fix
my blindness?

> Thanks for the very comprehensive bug report and for the patch as well!
>
>> I’ve not looked at jessie-ELTS or buster-security whether they
>> are affected as well; sid is clean (and where I got the realloc
>> failure check necessity from, although sid’s free()s the buffer
>> if realloc fails; this isn’t needed @Tom).
>
> If this seems to be happening in stretch, I assume there's a problem
> with jessie-ELTS as well. That said, buster is good because a DSA
> wasn't issued and this will be fixed via a point release.

I had already prepared an update for buster, but fortunately it did not
happen yet, because that one also has the same bug as yours.

> I am glad and surprised that sid is okay and there doesn't seem to be
> a problem.  Just to cross-check and ensure I get it right (for stretch
> and jessie), can you send me the reproducer as well? I'd like to be
> able to reproduce this before and after your patch (just to be one the
> safer side) and do the same for jessie as well!

Run xterm under valgrind and select some text.  Valgrind will be very
unhappy with xterm 327-2+deb9u1 but should not show up any errors in
that regard with a correctly patched version.  Instead of Thorsten's
suggestion you could also apply the patches to the SaltTextAway()
function from xterm 365e.

Cheers,
   Sven

Bug#984657: nss: Please package most recent version 3.62

[Carsten Schoenert]

Source: nss
Severity: wishlist

Dear Maintainer,

while trying to package the current beta version of Thunderbird (87.0b2)
the configure step is failing due not available version >= 3.62 of
libnss3-dev.

Please consider to package this new version.

Thanks!

Carsten

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

Kernel: Linux 5.10.0-3-amd64 (SMP w/6 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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

Bug#984469: guitarix: debian/copyright is inaccurate

[Hermann Meyer]

Hi

guitarix upstream maintainer here.

Please downgrade the severity of this bug.

The files in question don't be part of the distributed package, so there
is no serious reason to mark guitarix "unfit for release".

Even if the [debian/copyright] file may be wrong for those files, that
haven't any relation to the distributed package, as they are only part
of the source, and be in no relation to the distributed binary.

If it helps, I could mark the files in question as CC-BY-1.0 so that the
copyright file is correct.

However, this is by far not a serious bug, so please, handle it.

Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x

[Dirk Eddelbuettel]

Hi Graham and Martin,

Thanks for coming back to this, I had also meant to write to Martin this 
weekend.

On 6 March 2021 at 19:16, Graham Inggs wrote:
| Is there a bug opened for this issue with Matrix upstream?

Per field Bug-Reports in DESCRIPTION, the repo (and bug tracker) are (still)
at R-Forge:

   https://r-forge.r-project.org/tracker/?atid=294_id=61=browse

| I may have some useful feedback from TMB upstream to add.

You may need an account there :-/


To Martin: As I can run some simple tests on s390x, is this something you
could possible schedule to make some time for?


Best, Dirk

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#983031: konqueror segfaults on starting

[J Rowan]

On Sat, 6 Mar 2021 14:04:38 +0100
Bernhard Übelacker  wrote:

> gdb -q -ex 'set pagination off' -ex 'run' -ex 'bt' -ex 'detach' -ex
> 'quit' --args konqueror


Reading symbols from konqueror...
Reading symbols from 
/usr/lib/debug/.build-id/e4/6ba37330371215b40e01c7c01397ce28f6aa3c.debug...
Starting program: /usr/bin/konqueror 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x70faf700 (LWP 8878)]
[New Thread 0x7fffe42c3700 (LWP 8885)]
[New Thread 0x7fffe3981700 (LWP 8886)]
[New Thread 0x7fffe3180700 (LWP 8887)]
[New Thread 0x7fffe297f700 (LWP )]
[New Thread 0x7fffe217e700 (LWP 8889)]
[New Thread 0x7fffe197d700 (LWP 8890)]

Thread 1 "konqueror" received signal SIGSEGV, Segmentation fault.
0x in ?? ()
#0  0x in  ()
#1  0x7fffeafcf23f in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
#2  0x7fffeaaeb704 in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
#3  0x7fffeaaeca94 in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
#4  0x7fffeaace95e in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
#5  0x7fffeafcd903 in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
#6  0x707175af in  () at /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
#7  0x70705e49 in  () at /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
#8  0x715db1b5 in  () at 
/usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so
#9  0x763fa4fb in QOpenGLContext::destroy() () at 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#10 0x763fa7a7 in QOpenGLContext::~QOpenGLContext() () at 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#11 0x715dd2bf in  () at 
/usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so
#12 0x715dd909 in  () at 
/usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so
#13 0x7fffbd4d9845 in  () at 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#14 0x7fffd210 in  ()
#15 0x7fffbd4ddec1 in  () at 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#16 0x7fffd610 in  ()
#17 0x7fffbd4dc4e5 in  () at 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#18 0x7fffd230 in  ()
#19 0x0005 in  ()
#20 0x7fffd530 in  ()
#21 0x7fffd540 in  ()
#22 0x7fffd590 in  ()
#23 0x7fffd380 in  ()
#24 0x7fffd360 in  ()
#25 0x7fffd2a8 in  ()
#26 0x7fffd5a0 in  ()
#27 0x in  ()
Detaching from program: /usr/bin/konqueror, process 8873
[Inferior 1 (process 8873) detached]

-- 
Joe

Bug#984655: news.h: fix a warning about a missing declaration in a prototype

[Bjarni Ingi Gislason]

Source: nn
Version: 6.7.3-14
Severity: normal
Tags: patch

Dear Maintainer,

>From 34b4cf72fdb07ce1b37550e10d9064a2406828a1 Mon Sep 17 00:00:00 2001
>From: Bjarni Ingi Gislason 
>Date: Sat, 6 Mar 2021 17:11:00 +
>Subject: [PATCH] news.h: fix a warning about a missing declaration in a
> prototype

In file included from more.c:25:
news.h:76:1: warning: function declaration isn't a prototype 
[-Wstrict-prototypes]
   76 | char   *parse_header(FILE *, char **(*) (), int, 
news_header_buffer);
  | ^~~~

Signed-off-by: Bjarni Ingi Gislason 
---
 news.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/news.h b/news.h
index b23c841..6a6127b 100644
--- a/news.h
+++ b/news.h
@@ -73,7 +73,7 @@ extern struct digest_header digest;
 
 typedef charnews_header_buffer[NEWS_HEADER_BUFFER];
 
-char   *parse_header(FILE *, char **(*) (), int, news_header_buffer);
+char   *parse_header(FILE *, char **(*) (char *, int), int, 
news_header_buffer);
 int is_header_line(char *);
 FILE   *open_news_article(article_header *, int, news_header_buffer, 
news_header_buffer);
 
-- 
2.30.1



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

Kernel: Linux 5.10.9-1 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- debconf information excluded

-- 
Bjarni I. Gislason

Bug#984656: pam: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Adriano Rafael Gomes]

Package: pam
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x

[Graham Inggs]

Hi Dirk

Is there a bug opened for this issue with Matrix upstream?

I may have some useful feedback from TMB upstream to add.

Regards
Graham

Bug#983031: konqueror segfaults on starting

[Bernhard Übelacker]

Hello Joe,
this information might not be sufficient for the maintainer.

Could you try following to collect some more informations?

- install packages:
gdb psmisc konqueror-dbgsym

- stop all running instances of konqueror:
killall konqueror

- then start konqueror inside a debugger:
gdb -q -ex 'set pagination off' -ex 'run' -ex 'bt' -ex 'detach' -ex 'quit' 
--args konqueror


When the crash happens, a backtrace should be printed.
Please forward this output to this bug.

More debugging hints can be found here [1].

Kind regards,
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace

Bug#984654: alsa-ucm-conf: please add support for pinephone,pinetab,librem5 hardware

[Nicolas Boulenguez]

Package: alsa-ucm-conf
Version: 1.2.4-2
Severity: wishlist
Tags: patch upstream
X-Debbugs-Cc: Arnaud Ferraris 

Hello.

Please apply the attached changes by Arnaud Ferraris.  They have been
applied and tested by the Mobian distribution for a few months.

The Pinephone part is forwarded to ALSA upstream (though currently
waiting for approval, so no Forwarded: URL yet).

The PineTab part is not forwarded. Upstream requires the output of
alsa-info executed on the actual hardware.

The Librem5 part is incomplete but useful nevertheless.

Thanks.
>From 997a22545f3df75c3c1b6cae49f0a4cccbb5d266 Mon Sep 17 00:00:00 2001
From: Arnaud Ferraris 
Date: Tue, 12 May 2020 09:43:51 +0200
Subject: [PATCH 1/2] ucm2: add PinePhone configuration

---
 ucm2/PinePhone/HiFi.conf  | 139 +
 ucm2/PinePhone/PinePhone.conf |  11 +++
 ucm2/PinePhone/VoiceCall.conf | 142 ++
 3 files changed, 292 insertions(+)
 create mode 100644 ucm2/PinePhone/HiFi.conf
 create mode 100644 ucm2/PinePhone/PinePhone.conf
 create mode 100644 ucm2/PinePhone/VoiceCall.conf

diff --git a/ucm2/PinePhone/HiFi.conf b/ucm2/PinePhone/HiFi.conf
new file mode 100644
index 000..a6a1cf8
--- /dev/null
+++ b/ucm2/PinePhone/HiFi.conf
@@ -0,0 +1,137 @@
+SectionVerb {
+	EnableSequence [
+		cset "name='Headphone Playback Switch' off"
+		cset "name='Headphone Source Playback Route' DAC"
+		cset "name='Line In Playback Switch' off"
+		cset "name='Line Out Playback Switch' off"
+		cset "name='Line Out Source Playback Route' Mono Differential"
+		cset "name='Mic1 Playback Switch' off"
+		cset "name='Mic2 Playback Switch' off"
+		cset "name='AIF1 DA0 Playback Volume' 160"
+		cset "name='AIF3 ADC Source Capture Route' None"
+		cset "name='AIF2 DAC Source Playback Route' AIF2"
+		cset "name='DAC Playback Switch' on"
+		cset "name='DAC Playback Volume' 160"
+		cset "name='ADC Digital DAC Playback Switch' off"
+		cset "name='AIF1 Slot 0 Digital DAC Playback Switch' on"
+		cset "name='AIF2 Digital DAC Playback Switch' off"
+		cset "name='DAC Reversed Playback Switch' off"
+		cset "name='Earpiece Playback Switch' off"
+		cset "name='Earpiece Source Playback Route' DACL"
+
+		cset "name='Line In Capture Switch' off"
+		cset "name='Mic1 Capture Switch' off"
+		cset "name='Mic2 Capture Switch' off"
+		cset "name='Mixer Capture Switch' off"
+		cset "name='Mixer Reversed Capture Switch' off"
+		cset "name='ADC Capture Volume' 160"
+		cset "name='AIF1 AD0 Capture Volume' 160"
+		cset "name='AIF1 Data Digital ADC Capture Switch' on"
+		cset "name='AIF2 ADC Mixer ADC Capture Switch' off"
+		cset "name='AIF2 ADC Mixer AIF1 DA0 Capture Switch' off"
+		cset "name='AIF2 ADC Mixer AIF2 DAC Rev Capture Switch' off"
+		cset "name='AIF2 ADC Mixer AIF1 DA0 Capture Switch' off"
+		cset "name='AIF2 ADC Mixer AIF1 DA0 Capture Switch' off"
+	]
+	DisableSequence [
+	]
+	Value {
+	}
+}
+
+SectionDevice."Speaker" {
+	Comment "Internal speaker"
+	EnableSequence [
+		cset "name='AIF1 DA0 Stereo Playback Route' Mix Mono"
+		cset "name='Line Out Playback Switch' on"
+		cset "name='Line Out Playback Volume' 100%"
+	]
+
+	DisableSequence [
+		cset "name='Line Out Playback Switch' off"
+	]
+
+	Value {
+		PlaybackVolume "Line Out Playback Volume"
+		PlaybackSwitch "Line Out Playback Switch"
+		PlaybackChannels "2"
+		PlaybackPriority 300
+		PlaybackPCM "hw:${CardId},0"
+	}
+}
+SectionDevice."Earpiece" {
+	Comment "Internal Earpiece"
+	EnableSequence [
+		cset "name='AIF1 DA0 Stereo Playback Route' Mix Mono"
+		cset "name='Earpiece Playback Switch' on"
+		cset "name='Earpiece Playback Volume' 100%"
+	]
+
+	DisableSequence [
+		cset "name='Earpiece Playback Switch' off"
+	]
+
+	Value {
+		PlaybackVolume "Earpiece Playback Volume"
+		PlaybackSwitch "Earpiece Playback Switch"
+		PlaybackChannels "2"
+		PlaybackPriority 100
+		PlaybackPCM "hw:${CardId},0"
+	}
+}
+SectionDevice."DigitalMic" {
+	Comment "Internal Microphone"
+	ConflictingDevice [
+		"HeadsetMic"
+	]
+	EnableSequence [
+		cset "name='Mic1 Capture Switch' on"
+	]
+	DisableSequence [
+		cset "name='Mic1 Capture Switch' off"
+	]
+	Value {
+		CapturePriority 100
+		CapturePCM "hw:${CardId},0"
+		CaptureChannels "2"
+	}
+}
+SectionDevice."HeadsetMic" {
+	Comment "Headset Microphone"
+	ConflictingDevice [
+		"DigitalMic"
+	]
+	EnableSequence [
+		cset "name='Mic2 Capture Switch' on"
+	]
+	DisableSequence [
+		cset "name='Mic2 Capture Switch' off"
+	]
+	Value {
+		CapturePriority 200
+		CapturePCM "hw:${CardId},0"
+		CaptureChannels "2"
+		JackControl "Headset Microphone Jack"
+	}
+}
+SectionDevice."Headphone" {
+	Comment "Headphones"
+	EnableSequence [
+		cset "name='AIF1 DA0 Stereo Playback Route' Stereo"
+		cset "name='Headphone Playback Switch' on"
+		cset "name='Headphone Playback Volume' 100%"
+	]
+
+	DisableSequence [
+		cset "name='Headphone Playback Switch' off"
+	]
+
+	Value {
+		PlaybackVolume "Headphone Playback Volume"
+		PlaybackSwitch "Headphone Playback Switch"
+		

Bug#984653: please rate limit messages sent to logged-in users

[Michael Biebl]

Am 06.03.2021 um 17:22 schrieb Marc Haber:

If this cannot be done with run-time configuration at the moment, I will
be happy to take this issue upstream. Please let me know.


ttbomk, this omusrmg can not be rate limited independently.

It would probably need something like imuxsock
https://www.rsyslog.com/doc/v8-stable/configuration/modules/imuxsock.html#syssock-ratelimit-interval

Would be great if you can raise this upstream at
https://github.com/rsyslog/rsyslog/issues/new

Bug#984650: update-initramfs fails when /etc/systemd/network/99-default.link is symlink to /dev/null

[Frederik Lindenaar]

Hi Cyril,

Thank you for the quick reply

As Ben also pointed out, I probably have indeed mixed up /dev/zero and 
/dev/null and had already fixed that by using an empty file. Nevertheless the 
result was pretty odd (the disk filling up rapidly) and very confusing so might 
still be useful to prevent this (if possible).

Why not use a cp -aLt  {} instead to prevent this?

regards,

Frederik


> On 6 Mar 2021, at 16:27, Cyril Brulebois  wrote:
> 
> Hello Frederik,
> 
> It seems there's some confusion around special character devices. Your
> subject mentions /dev/null…
> 
> Frederik Lindenaar  (2021-03-06):
>> When one disables the "Predicatble Network InterfaceNames" 
>> by making /lib/systemd/network/99-default.link a symlink to /dev/zero then
> 
> … but this is about /dev/zero (not the same thing! — see `man 4 null`).
> 
>> update-initramfs will fail as the copy of this symlink will fill-up all space
>> available in /var/tmp and makes it impossible to install any kernel image
>> 
>> the culprit is the following command executed by update-initramfs:
>> 
>>  find /etc/systemd/network -name *.link -execdir cp -pt /var/tmp/ {} +
>> 
>> As it (and should) dereference de symlink, it reads zero bytes from
>> /dev/null until the disk is full.
> 
> … and here you write /dev/null but what you describe happens with
> /dev/zero instead.
> 
>> Changing the symlink to a zero byte file resolved the issue for me but
>> as this approach is one of the recommended approaches to disable
>> predicatble network interface names (see [1]) others may also bump
>> into this.
>> 
>> [1] https://wiki.debian.org/NetworkInterfaceNames#How_to_get_it_back
> 
> This correctly describes a symlink to /dev/null, and not /dev/zero which
> appears to be what you're trying to use.
> 
> Fix your symlink, and you should be good to go?
> 
> 
> Cheers,
> -- 
> Cyril Brulebois (k...@debian.org)
> D-I release manager -- Release team member -- Freelance Consultant

Bug#984650: update-initramfs fails when /etc/systemd/network/99-default.link is symlink to /dev/null

[Frederik Lindenaar]

Hi Ben,

Thanks for the quick reply. I am not sure how I could have mixed these two up 
but did a quick test with cp just now and the problem indeed looks like mixing 
up /dev/zero and /dev/null (I have no way to check that anymore though).

Nevertheless the result was very confusing (a full disk) so might still be good 
to check somehow

regards,

Frederik

> On 6 Mar 2021, at 16:38, Ben Hutchings  wrote:
> 
> Control: tag -1 moreinfo
> 
> On Sat, 2021-03-06 at 14:57 +0100, Frederik Lindenaar wrote:
>> Package: initramfs-tools
>> Version: 0.133+deb10u1
>> Severity: important
>> 
>> When one disables the "Predicatble Network InterfaceNames" 
>> by making /lib/systemd/network/99-default.link a symlink to /dev/zero then
>> update-initramfs will fail as the copy of this symlink will fill-up all space
>> available in /var/tmp and makes it impossible to install any kernel image
>> 
>> the culprit is the following command executed by update-initramfs:
>> 
>> find /etc/systemd/network -name *.link -execdir cp -pt /var/tmp/ {} +
>> 
>> As it (and should) dereference de symlink, it reads zero bytes from
>> /dev/null until the disk is full.
> [...]
> 
> It looks like you have mixed up /dev/null and /dev/zero (as a Dutch
> learner, I can see how that would happen).  /dev/null is always empty
> and would be copied as an empty file.  This is the correct target for
> symlinks when you want to disable a systemd unit.  /dev/zero is an
> infinite stream of binary zeroes and would result in the behaviour you
> saw.
> 
> Ben.
> 
> 
> -- 
> Ben Hutchings
> Knowledge is power.  France is bacon.

Bug#984653: please rate limit messages sent to logged-in users

[Marc Haber]

Package: rsyslog
Version: 8.2102.0-2
Severity: important

Hi,

rsyslog's default configuration comes with a catch-all clause that sends
all messages with the "emergency" severity to everybody logged in:

*.emerg :omusrmsg:*

I today had the situation where a daemon running wild sent tens of
thousands of those messages per second to rsyslog. Of course, it became
totally impossible to log in to the machine to kill the misbehaving
daemon or rsyslog. To make things worse, since the serial console was
also spammed with the messages, Magic SysRq didn't work.

This was the first time in years I had to actually go to the machine
room to pull the power cable from a running system.

I would appreciate if it would be possible to have rsyslog rate-limit
emergency messages sent to the console of a logged-in user (maybe even
as severely as to one per minute?), or at least not print tens of
thousands of identical messages to consoles. Maybe the omusrmsg target
can be configured with a rate limit in the default config file?

If this cannot be done with run-time configuration at the moment, I will
be happy to take this issue upstream. Please let me know.

Thanks in advance!

Greetings
Marc


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

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

Versions of packages rsyslog depends on:
ii  init-system-helpers  1.60
ii  libc62.31-9
ii  libestr0 0.1.10-2.1+b1
ii  libfastjson4 0.99.9-1
ii  liblognorm5  2.0.5-1.1
ii  libsystemd0  247.3-1
ii  libuuid1 2.36.1-7
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages rsyslog recommends:
ii  logrotate  3.18.0-2

Versions of packages rsyslog suggests:
pn  rsyslog-doc   
pn  rsyslog-gssapi
pn  rsyslog-mongodb   
pn  rsyslog-mysql | rsyslog-pgsql 
pn  rsyslog-openssl | rsyslog-gnutls  
pn  rsyslog-relp  

-- Configuration Files:
/etc/logrotate.d/rsyslog changed [not included]

-- no debconf information

Bug#984652: alsa-ucm-conf: please check upstream GPG signature

[Nicolas Boulenguez]

Package: alsa-ucm-conf
Severity: minor
Tags: patch

Hello.

Please use the attached commit and let uscan check the signature of
new upstream versions.
The upstream fingerprint F04D F507 37AC 1A88 4C4B 3D71 8380 596D A6E5 9C91
is taken from https://alsa-project.org/wiki/Download.

A second commit contains a cosmetic suggestion that does not deserve a
bug on its own.
Thanks for reviewing both.
>From 38f0b697d0bd26ab39f2cd03c2e2350af04e0045 Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Sat, 6 Mar 2021 17:12:43 +0100
Subject: [PATCH 2/3] Let uscan check upstream signature

---
 debian/upstream/signing-key.asc | 29 +
 debian/watch|  3 ++-
 2 files changed, 31 insertions(+), 1 deletion(-)
 create mode 100644 debian/upstream/signing-key.asc

diff --git a/debian/upstream/signing-key.asc b/debian/upstream/signing-key.asc
new file mode 100644
index 000..6f245fc
--- /dev/null
+++ b/debian/upstream/signing-key.asc
@@ -0,0 +1,29 @@
+-BEGIN PGP PUBLIC KEY BLOCK-
+
+mQINBF+PBUIBEACQ0eLhY6zJkZCztI3Zj7GiEkGyDYXFr10wMn2BmAxXEOhvGs5C
+XtZYokNnYnojU2ehb14pdQiIYVm7YwjNjPhFmc6DnSJ74tlDtzI0ZfZYgU8B3/AU
+hHCIe7NeH+uqaS4hQ4gQF3HB19GNQ21keQPtm/cZzNvkAwWQ6wxiIas/odQGt6sg
+TULub4gXQw42iCW0jNeliNgeOc/4/2qtznN+Ss5G+Hs+EBh0kFCG4+5RcpgtKmYO
+LEy+8qI/UmlgOeT+47eTXm4LjxHfRuKcbvSExfICUB5XLD2ZmeZbFyP48jkDvB7w
+A4jNfImtlRfTvoviNlOl08Pk3aJoPR8IZIGw+EQCf3ChXTziadqOg37SAy4yGJ14
+BjirKgBNO4zB+lkLOAknsVKJOKRt3w54MevCuj0GGbfSyErZAeHvliXrfBa1ACLu
+c2ynRDR/5j0FA3vPzRsHyOGFC4F34W5BhkXCuJBG2o2VDv/zANzjg/hw+0IbmH3G
+kYn73EDIaz5giKJolE32WaWkz39DwuuoUaLLyfxyiN+c0p2/XQFCrOSqHNUMfI5z
+Ll62nL1XruF6u9ApLKRv/uDJN7tLgds83rteYJP7/5/JSYCPB8PcUkmhB8OoVdpr
+tYI8C/6Y6KREm3Jk4AdkySIFnPXZQCkiOR2qOmAuaQPeesjsrSkUtJYZcwARAQAB
+tEVBTFNBIFJlbGVhc2UgVGVhbSAoUGFja2FnZSBTaWduaW5nIEtleSB2MSkgPHJl
+bGVhc2VAYWxzYS1wcm9qZWN0Lm9yZz6JAk4EEwEIADgWIQTwTfUHN6waiExLPXGD
+gFltpuWckQUCX48FQgIbAwULCQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRCDgFlt
+puWckRhVD/45DNoD79lHBJEu0Wv93OSlPZDUKR+BnkkdEDgDEhTvk+Bin/EWdb3g
+Unc+rEczgAqjqblLH7ndBtFZPNGiQ2nu8eAdN0TrOFQx7bFg4Do7KXNUUqdPUETC
+AgkozF3ucsgOcBbv6LwwDfdQDFjkg7CuNGy8CRcLSO5dLK7domq3RxF5mKl1dkOv
+4brfw6ssn+pja/jkgM9BKt80ycIDiJtVRuXMBJD19ZB8EzQO9OQBdAPERSG8BwLX
+LemTLAZqNd0mixVbn50qCQil64UOkOd5DHVBBokxgtlJEcDujqWaCUYSygSiP2ke
+44ArDr7hRwG5KhhbFOigXo3nBYnKyiuWs0jpnrTQD9+uTxcetyBpJ6BW/i/Fy2a9
+NBFNhbDI07rCMXM25cLP8qbI5i6nTSDlkpLP40At9yUVYt8gIO6ZpGpO04/lAhT1
+NxtbZkKMo1nphMHU/MDSusoHyLxUXpppdbXTdMgsuFrXae3gcFDowQbLZqb6ZAJ5
+opX4sDBIdoHDBsI6wCGTV7AAWB8RXWW0RTYMkyIxqixiiB2N2jaau4yHfqv9QWOY
+oPcx6ySKqGN0HV50PeRis5eeq7kHIdRrVIOBd0tPIqCKIvyJZk1QXReKvvE84Km2
+dYPusBlhhF7/4WVovlE6HFwyLSOyb32m4qf5dV35op07ew8i4DHpkQ==
+=n4lM
+-END PGP PUBLIC KEY BLOCK-
diff --git a/debian/watch b/debian/watch
index c5253dd..db4c35f 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,2 +1,3 @@
 version=4
-ftp://ftp.alsa-project.org/pub/lib/alsa-ucm-conf-(.+)\.tar\.bz2
+opts=pgpmode=auto \
+ftp://ftp.alsa-project.org/pub/lib/@PACKAGE@@ANY_VERSION@@ARCHIVE_EXT@
-- 
2.30.1

>From a1f16b7822d1fc41e714e9517d2e7462929ea23c Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Sat, 6 Mar 2021 17:13:13 +0100
Subject: [PATCH 3/3] Cosmetic improvement in readability of debian/rules

---
 debian/rules | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/debian/rules b/debian/rules
index 2f5a068..ae075b3 100755
--- a/debian/rules
+++ b/debian/rules
@@ -3,6 +3,5 @@
 %:
 	dh $@
 
-override_dh_install:
-	dh_install
-	chmod -x $(CURDIR)/debian/alsa-ucm-conf/usr/share/alsa/ucm2/kblrt5660/*
+execute_after_dh_fixperms:
+	chmod -x debian/alsa-ucm-conf/usr/share/alsa/ucm2/kblrt5660/*
-- 
2.30.1

Bug#984650: update-initramfs fails when /etc/systemd/network/99-default.link is symlink to /dev/null

[Ben Hutchings]

Control: tag -1 moreinfo

On Sat, 2021-03-06 at 14:57 +0100, Frederik Lindenaar wrote:
> Package: initramfs-tools
> Version: 0.133+deb10u1
> Severity: important
> 
> When one disables the "Predicatble Network InterfaceNames" 
> by making /lib/systemd/network/99-default.link a symlink to /dev/zero then
> update-initramfs will fail as the copy of this symlink will fill-up all space
> available in /var/tmp and makes it impossible to install any kernel image
> 
> the culprit is the following command executed by update-initramfs:
> 
> find /etc/systemd/network -name *.link -execdir cp -pt /var/tmp/ {} +
>
> As it (and should) dereference de symlink, it reads zero bytes from
> /dev/null until the disk is full.
[...]

It looks like you have mixed up /dev/null and /dev/zero (as a Dutch
learner, I can see how that would happen).  /dev/null is always empty
and would be copied as an empty file.  This is the correct target for
symlinks when you want to disable a systemd unit.  /dev/zero is an
infinite stream of binary zeroes and would result in the behaviour you
saw.

Ben.


-- 
Ben Hutchings
Knowledge is power.  France is bacon.


signature.asc
Description: This is a digitally signed message part

Bug#984650: update-initramfs fails when /etc/systemd/network/99-default.link is symlink to /dev/null

[Cyril Brulebois]

Hello Frederik,

It seems there's some confusion around special character devices. Your
subject mentions /dev/null…

Frederik Lindenaar  (2021-03-06):
> When one disables the "Predicatble Network InterfaceNames" 
> by making /lib/systemd/network/99-default.link a symlink to /dev/zero then

… but this is about /dev/zero (not the same thing! — see `man 4 null`).

> update-initramfs will fail as the copy of this symlink will fill-up all space
> available in /var/tmp and makes it impossible to install any kernel image
> 
> the culprit is the following command executed by update-initramfs:
> 
>   find /etc/systemd/network -name *.link -execdir cp -pt /var/tmp/ {} +
> 
> As it (and should) dereference de symlink, it reads zero bytes from
> /dev/null until the disk is full.

… and here you write /dev/null but what you describe happens with
/dev/zero instead.

> Changing the symlink to a zero byte file resolved the issue for me but
> as this approach is one of the recommended approaches to disable
> predicatble network interface names (see [1]) others may also bump
> into this.
> 
> [1] https://wiki.debian.org/NetworkInterfaceNames#How_to_get_it_back

This correctly describes a symlink to /dev/null, and not /dev/zero which
appears to be what you're trying to use.

Fix your symlink, and you should be good to go?


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


signature.asc
Description: PGP signature

Bug#984651: unblock: freedict/2021.01.05-3

[Sebastian Humenda]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package freedict

The previous version ran the build in parallel and consumed vast amounts of
memory. The fix is simplistic: just build sequentially. I therefore would like
to request to unblock the package, since it will not affect the stability of
the upcoming release. It was blocked by #982730.

Debdiff:

```
gpgv: Signature made Tue Feb 16 22:48:52 2021 CET
gpgv:using RSA key A8574EA4228468D0463BEB0C731F86C6AC61798D
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on 
/tmp/freedict_2021.01.05-2.dsc
gpgv: Signature made Sat Mar  6 14:05:06 2021 CET
gpgv:using RSA key 0DD2BC30C6C7326B3FFACD24DBF124790B30ECA5
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on 
/mnt/sdb6/streicher/quellen/debian/freedict/freedict_2021.01.05-3.dsc
diff -Nru freedict-2021.01.05/debian/changelog 
freedict-2021.01.05/debian/changelog
--- freedict-2021.01.05/debian/changelog2021-02-16 22:45:56.0 
+0100
+++ freedict-2021.01.05/debian/changelog2021-03-03 18:26:24.0 
+0100
@@ -1,3 +1,9 @@
+freedict (2021.01.05-3) unstable; urgency=medium
+
+  * properly disable parallel builds (Closes: #982730)
+
+ -- Sebastian Humenda   Wed, 03 Mar 2021 18:26:24 +0100
+
 freedict (2021.01.05-2) unstable; urgency=medium

   * rules: Decrease --max-parallel to 1 (Closes: #982730)
diff -Nru freedict-2021.01.05/debian/control freedict-2021.01.05/debian/control
--- freedict-2021.01.05/debian/control  2021-02-16 22:45:03.0 +0100
+++ freedict-2021.01.05/debian/control  2021-03-03 18:26:24.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Sebastian Humenda 
 Build-Depends: debhelper-compat (= 13), freedict-tools (>= 0.5.0)
-Standards-Version: 4.5.0
+Standards-Version: 4.5.1
 Rules-Requires-Root: no
 Homepage: https://freedict.org/
 Vcs-Browser: https://salsa.debian.org/freedict-team/dictionaries
diff -Nru freedict-2021.01.05/debian/control.HEAD 
freedict-2021.01.05/debian/control.HEAD
--- freedict-2021.01.05/debian/control.HEAD 2021-02-16 22:45:03.0 
+0100
+++ freedict-2021.01.05/debian/control.HEAD 2021-03-03 18:26:24.0 
+0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Sebastian Humenda 
 Build-Depends: debhelper-compat (= 13), freedict-tools (>= 0.5.0)
-Standards-Version: 4.5.0
+Standards-Version: 4.5.1
 Rules-Requires-Root: no
 Homepage: https://freedict.org/
 Vcs-Browser: https://salsa.debian.org/freedict-team/dictionaries
diff -Nru freedict-2021.01.05/debian/rules freedict-2021.01.05/debian/rules
--- freedict-2021.01.05/debian/rules2021-02-16 22:45:46.0 +0100
+++ freedict-2021.01.05/debian/rules2021-03-03 15:14:00.0 +0100
@@ -11,10 +11,10 @@
 BUILD_MODE ?= normal

 # pass parallelisation through from debhelper
-ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
-NUMJOBS = $(patsubst parallel=%,%,$(filter 
parallel=%,$(DEB_BUILD_OPTIONS)))
-MAKEFLAGS += -j$(NUMJOBS)
-endif
+#ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
+#NUMJOBS = $(patsubst parallel=%,%,$(filter 
parallel=%,$(DEB_BUILD_OPTIONS)))
+#MAKEFLAGS += -j$(NUMJOBS)
+#endif

 %:
dh $@ --max-parallel=1
```

Note that due to hardware failure, I cannot access my private key at the
moment, but that shouldn't make the debdiff less useful.


unblock freedict/2021.01.05-3

-- System Information:
Debian Release: 10.8
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: i386 (i686)

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

Bug#984646: omniorb-nameserver: omniNames does not start any longer

[fwxx]

Package: omniorb-nameserver
Version: 4.2.2-0.9+b1
Severity: grave
Tags: d-i
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
starting omniorb4-nameserver a second time.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 rm -f /var/lib/omniorb/omninames*
 starting/stopping omniorb4-nameserver 2 times:
 systemctl start omniorb-nameserver
 => service runs
 systemctl stop omniorb-nameserver
 => in /var/lib/omniorb/:
omninames-*.bak
omninames-*.dat
exists
 systemctl start omniorb-nameserver

   * What was the outcome of this action?
 => omniorb4-nameserver service does not run (systemctl status
omniorb4-nameserver)
 => in /var/lib/omniorb/:
omninames-*.bak
omninames-*.dat
omninames-*.log
exists

   * What outcome did you expect instead?
 - omniNames nameserver service runs.
 - omninames-*.log
   does not exist in /var/lib/omniorb/

   * I think the problem is in
 /etc/init.d/omniorb4-nameserver
 which copies omninames-*.bak file to .log
 According to http://omniorb.sourceforge.net/omni42/omniNames.html
 ".log" is replaced by ".dat". I think this is just a matter of
 filename extensions.

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

Kernel: Linux 4.19.0-14-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages omniorb-nameserver depends on:
ii  libc6   2.28-10
ii  libgcc1 1:8.3.0-6
ii  libomniorb4-2   4.2.2-0.9+b1
ii  libomnithread4  4.2.2-0.9+b1
ii  libstdc++6  8.3.0-6
ii  lsb-base10.2019051400

omniorb-nameserver recommends no packages.

omniorb-nameserver suggests no packages.

Bug#984487: nmu: libzstd1 rdeps relying on 1.3.8

[Stephen Kitt]

On Fri, 5 Mar 2021 10:34:06 +0100, Sebastian Ramacher 
wrote:
> On 2021-03-04 07:06:05, Stephen Kitt wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: binnmu
> > 
> > Dear release team,
> > 
> > libzstd1 used to provide an over-enthusiastic symbols file, which has
> > resulted in dependencies which are too relaxed. The library API isn’t
> > determined by its exported symbols, unfortunately, but by one of its
> > headers. See https://bugs.debian.org/969597 and
> > https://github.com/facebook/zstd/pull/2501 for details.
> > 
> > As a result, a (small) number of packages have picked up a dependency
> > on “libzstd1 (>= 1.3.8)” when it should be “(>= 1.4.0)” — they were
> > built with one of the 1.4 packages, but the symbols file declared some
> > of the 1.4 functions as available in 1.3.8 (which they were,
> > technically, but with a different API in some cases).  
> 
> Please explain. If they were available with a different API prior to
> 1.4, that sounds like an ABI break to me. In that case, the binNMUs
> would just hide the problem.

They weren’t intended to be available as part of the library API. libzstd
distinguishes two sets of functions: one intended for use by programs linked
with the dynamic library, another intended for use by programs linked
statically. Programs built in Debian abide by this rule and don’t use any
symbols they shouldn’t.

Unfortunately, the way the library is built means that “static-only” symbols
are still exported by the dynamic library (even though no dynamically-linked
program uses them). The symbols file appears to have been generated
mechanically, and as a result it includes symbols starting from the point
where they appeared in the library, and not when they officially became part
of the library’s API. The result is that programs built against libzstd 1.4.0
or later, using symbols added in 1.4.0, end up with a dependency on libzstd
1.3.8 or later, even though libzstd 1.3.8 doesn’t support the API they use.

The point of the binNMUs is to fix the latter, by ensuring that packages
depending on libzstd 1.4.0 or later really get an appropriate version of
libzstd. Without this, users can end up with broken packages if they only
partially upgrade their system.

I’m working on a longer-term fix with upstream, see
https://github.com/facebook/zstd/pull/2501 for details. I’ve already
substantially reduced the number of exported symbols (which were never part
of the external API and aren’t used by external users) in 1.4.9 upstream.

Arguably this is a soname breakage, but the case can also be made that it
isn’t: libzstd1 *is* backwards-compatible with all programs built against
older versions, even though some of its exported symbols changed their API
(they weren’t used in the incompatible versions). The invalid dependency
declaration is a consequence of Debian packaging only, IMO. The shlibs file
in the current package in unstable follows upstream’s instructions.

Regards,

Stephen


pgpdF_I1IqQwk.pgp
Description: OpenPGP digital signature

Bug#955540: chromium: Using ozone

[Guillem Jover]

Hi!

On Thu, 2021-01-21 at 16:31:29 +0100, Michel Le Bihan wrote:
> I built Chromium with ozone, but I'm not sure if it's ready for Debian
> yet. It will need testing. You can test it, if you want:
> https://lebihan.pl/chromium/chromium_88.0.4324.96-ozone.tar
> Currently, I only built for amd64.

Could you provide the patch needed to build with Ozone enabled? Even
if it's trivial (which I assume it might be), it might make it easier
for the maintainers to simply apply it?

Missing Ozone support means Chromium currently has bogus behavior with
its tab handling, and it shows artifacts when watching videos in
fullscreen mode in Wayland, so it would be nice to get this support
uploaded, even if into experimental. I was having the same exact
artifacts with Firefox using Xwayland, and enabling its Wayland support,
made these disappear.

Thanks,
Guillem

Bug#984645: unblock: refpolicy/2:2.20210203-4

[Russell Coker]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package refpolicy

[ Reason ]
This new version has lots of changes that will make the experience more
pleasant for users.  It specifically allows some of the recent features
in systemd, chromium/chrome, and KDE.  It allows gpg with pinentry to be
run from user_t (the confined user).  It allows some extra access that
mailman3 requires.  It also allows newaliases to run with Postfix.

[ Impact ]
If this isn't in Bullseye then the SE Linux experience for users will be
a little more annoying.  Things won't work out of the box as expected
without it and local customisations to resolve the issues won't be of as
high quality as the ones I developed.  Also without this version there
will be audit messages that will be confusing and annoying.

[ Tests ]
For the programs subject to the policy in question, they were run
repeatedly with the new policy, VMs running them were rebooted, and the
results were inspected to see if they operated correctly and didn't give
unwanted audit messages.

[ Risks ]
Most changes are granting new access, not access that is unexpected given
the context, and not access that is likely to be part of a vulnerability
chain.  These have low possibility of causing any problem.

The change for the newaliases command is more complex, but being unable
to run newaliases is a serious issue so it's worth doing.  The worst
case might be some domain being unable to send mail from a script.  But
in all the test cases it worked.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing


unblock refpolicy/2:2.20210203-4

diff -Nru refpolicy-2.20210203/debian/changelog 
refpolicy-2.20210203/debian/changelog
--- refpolicy-2.20210203/debian/changelog   2021-02-23 16:57:40.0 
+1100
+++ refpolicy-2.20210203/debian/changelog   2021-03-05 21:11:58.0 
+1100
@@ -1,3 +1,35 @@
+refpolicy (2:2.20210203-4) unstable; urgency=medium
+
+  * Allow ntpd_t to get the status of generic systemd units
+  * Allow kernel_t self:perf_event cpu.
+  * Allow chromium to watch network manager runtime dirs (for resolv.conf)
+Allow chromium to run naclhelper with nnp_transition
+Allow chromium to watch root dirs
+Allow chromium to read/write unix sockets from the calling domain
+  * Make Postgresql use postgresql_tmpfs_t for tmpfs files and make 
+mon_local_test_t and systemd_logind_t not have getattr access to tmpfs
+files audited.
+  * Allow systemd_user_runtime_dir_t to unlink device nodes of type
+user_tmp_t, they probably should not exist, so it's in the hacks patch.
+  * Allow the acngtool to read random and urandom devices and search fs sysctls
+  * Add wm_write_xdg_data tunable to allow user_wm_t etc to write xdg data.
+  * Allow chromium to watch gnome_xdg_config_t dirs
+  * Label pinentry programs as gpg_agent_exec_t and allow gpg_agent_t to exec
+them
+  * Create new admin_mail_t domain so that newaliases can work with Postfix
+  * Added a transition rule so that vipw/vigr gives the right context for
+/etc/passwd and /etc/group
+  * Allow acngtool_t to read /proc/sys/kernel/random/uuid
+  * Allow unconfined domains lockdown confidentiality and integrity access
+  * Allow netutils_t netlink_generic_socket access for tcpdump
+  * Allow smbcontrol to create a sock_file in a samba run dir
+  * Allow mailman_queue_t to bind to all unreserved TCP ports
+  * Allow systemd_coredump_t to mmap all executables and to have cap_userns
+sys_ptrace access. dontaudit systemd_coredump_t capability net_admin
+  * Allow mailman_queue_t to connect to port 443
+
+ -- Russell Coker   Fri, 05 Mar 2021 21:11:58 +1100
+
 refpolicy (2:2.20210203-3) unstable; urgency=medium
 
   * Add policy for blkmapd which is part of nfs service (included in upstream)
diff -Nru refpolicy-2.20210203/debian/patches/0002-strict 
refpolicy-2.20210203/debian/patches/0002-strict
--- refpolicy-2.20210203/debian/patches/0002-strict 2021-02-17 
13:40:42.0 +1100
+++ refpolicy-2.20210203/debian/patches/0002-strict 2021-02-25 
11:47:38.0 +1100
@@ -245,3 +245,15 @@
  
  tunable_policy(`pulseaudio_execmem',`
allow pulseaudio_t self:process execmem;
+Index: refpolicy-2.20210203/policy/modules/services/ntp.te
+===
+--- refpolicy-2.20210203.orig/policy/modules/services/ntp.te
 refpolicy-2.20210203/policy/modules/services/ntp.te
+@@ -130,6 +130,7 @@ term_use_ptmx(ntpd_t)
+ auth_use_nsswitch(ntpd_t)
+ 
+ init_exec_script_files(ntpd_t)
++init_get_generic_units_status(ntpd_t)
+ 
+ logging_send_syslog_msg(ntpd_t)
+ 
diff -Nru refpolicy-2.20210203/debian/patches/0025-systemd 
refpolicy-2.20210203/debian/patches/0025-systemd
--- refpolicy-2.20210203/debian/patches/0025-systemd2021-02-17 

Bug#984642: unblock: policycoreutils/3.1-3

[Russell Coker]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package policycoreutils

(Please provide enough (but not too much) information to help
the release team to judge the request efficiently. E.g. by
filling in the sections below.)

[ Reason ]
This version fixes bug #983447 which is grave and risks kicking the package
out of Bullseye.  It also closes bug #922448 and avoids trying to relabel
non-persistent filesystems on reboot.

[ Impact ]
All SE Linux packages get removed from Debian I guess, catastrophic for all
SE Linux users in Debian.

[ Tests ]
Manual test is to create an empty file /.autorelabel and reboot the system
and verify that it causes a relabel, then create a file /.autorelabel with
the contents "-F" and verify that it works.

[ Risks ]
The changed code is pretty simple, and in day to day usage it isn't even
used.  It's only used for corner cases of an initial installation.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

[ Other info ]
(Anything else the release team should know.)

unblock policycoreutils/3.1-3

Here is the debdiff:

diff -Nru policycoreutils-3.1/debian/changelog 
policycoreutils-3.1/debian/changelog
--- policycoreutils-3.1/debian/changelog2021-02-11 02:46:48.0 
+1100
+++ policycoreutils-3.1/debian/changelog2021-03-05 20:45:24.0 
+1100
@@ -1,3 +1,16 @@
+policycoreutils (3.1-3) unstable; urgency=medium
+
+  * Remove needless quotes around $FORCE variable in
+/lib/systemd/selinux-autorelabel to avoid shell error on empty file
+Closes: #983447
+  * Add check for noautorelabel command line option to prevent relabeling
+Closes: #922448
+  * Make fixfiles avoid trying to relabel tmpfs and other non-permanent
+filesystems
+Closes: #984567
+
+ -- Russell Coker   Fri, 05 Mar 2021 20:45:24 +1100
+
 policycoreutils (3.1-2) unstable; urgency=medium
 
   [ Laurent Bigonville ]
diff -Nru policycoreutils-3.1/debian/local/selinux-autorelabel 
policycoreutils-3.1/debian/local/selinux-autorelabel
--- policycoreutils-3.1/debian/local/selinux-autorelabel2021-02-11 
02:46:48.0 +1100
+++ policycoreutils-3.1/debian/local/selinux-autorelabel2021-03-05 
20:32:47.0 +1100
@@ -29,7 +29,7 @@
 
FORCE=$(cat /.autorelabel)
[ -x "/sbin/quotaoff" ] && /sbin/quotaoff -aug
-   /sbin/fixfiles "$FORCE" restore
+   /sbin/fixfiles $FORCE restore
 fi
 rm -f  /.autorelabel
 [ -x /usr/lib/dracut/dracut-initramfs-restore ] && 
/usr/lib/dracut/dracut-initramfs-restore
diff -Nru policycoreutils-3.1/debian/local/selinux-autorelabel-generator.sh 
policycoreutils-3.1/debian/local/selinux-autorelabel-generator.sh
--- policycoreutils-3.1/debian/local/selinux-autorelabel-generator.sh   
2021-02-11 02:46:48.0 +1100
+++ policycoreutils-3.1/debian/local/selinux-autorelabel-generator.sh   
2021-03-05 20:05:29.0 +1100
@@ -21,6 +21,9 @@
 }
 
 if selinuxenabled; then
+if grep -sqE "\bnoautorelabel\b" /proc/cmdline; then
+exit 0
+fi
 if test -f /.autorelabel; then
 set_target
 elif grep -sqE "\bautorelabel\b" /proc/cmdline; then
diff -Nru policycoreutils-3.1/debian/patches/fixfiles-remove-extras 
policycoreutils-3.1/debian/patches/fixfiles-remove-extras
--- policycoreutils-3.1/debian/patches/fixfiles-remove-extras   1970-01-01 
10:00:00.0 +1000
+++ policycoreutils-3.1/debian/patches/fixfiles-remove-extras   2021-03-05 
20:37:08.0 +1100
@@ -0,0 +1,13 @@
+Index: policycoreutils-3.1/scripts/fixfiles
+===
+--- policycoreutils-3.1.orig/scripts/fixfiles
 policycoreutils-3.1/scripts/fixfiles
+@@ -45,7 +45,7 @@ FS="`cat /proc/self/mounts | sort | uniq
+ for i in $FS; do
+   if [ `useseclabel` -ge 0 ]
+   then
+-  grep " $i " /proc/self/mounts | awk '{print $4}' | egrep 
--silent '(^|,)seclabel(,|$)' && echo $i
++  grep " $i " /proc/self/mounts | egrep -v "(tmpfs)|( 
/sys)|(^devpts)|(^hugetlbfs)|(^mqueue)" | awk '{print $4}' | egrep --silent 
'(^|,)seclabel(,|$)' && echo $i
+   else
+   grep " $i " /proc/self/mounts | grep -v "context=" | egrep 
--silent '(ext[234]| ext4dev | gfs2 | xfs | jfs | btrfs )' && echo $i
+   fi
diff -Nru policycoreutils-3.1/debian/patches/series 
policycoreutils-3.1/debian/patches/series
--- policycoreutils-3.1/debian/patches/series   2021-02-11 02:46:48.0 
+1100
+++ policycoreutils-3.1/debian/patches/series   2021-03-05 20:33:22.0 
+1100
@@ -1 +1,2 @@
 fixfiles-correctly-restore-context-of-mountpoints.patch
+fixfiles-remove-extras

Bug#984650: update-initramfs fails when /etc/systemd/network/99-default.link is symlink to /dev/null

[Frederik Lindenaar]

Package: initramfs-tools
Version: 0.133+deb10u1
Severity: important

When one disables the "Predicatble Network InterfaceNames" 
by making /lib/systemd/network/99-default.link a symlink to /dev/zero then
update-initramfs will fail as the copy of this symlink will fill-up all space
available in /var/tmp and makes it impossible to install any kernel image

the culprit is the following command executed by update-initramfs:

find /etc/systemd/network -name *.link -execdir cp -pt /var/tmp/ {} +

As it (and should) dereference de symlink, it reads zero bytes from /dev/null 
until the disk is full.

Changing the symlink to a zero byte file resolved the issue for me but as this
approach is one of the recommended approaches to disable predicatble network
interface names (see [1]) others may also bump into this.

[1] https://wiki.debian.org/NetworkInterfaceNames#How_to_get_it_back

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 6.9M Mar  6 14:31 /boot/initrd.img-4.19.0-13-amd64
-rw-r--r-- 1 root root 6.9M Mar  6 14:32 /boot/initrd.img-4.19.0-14-amd64
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.19.0-14-amd64 
root=UUID=8d33b150-7c84-4dd0-8893-06eab0e7b9d7 ro quiet

-- resume
RESUME=UUID=2db37a4d-80dd-46b3-aa4d-ff57862589ba
-- /proc/filesystems
ext3
ext2
ext4

-- lsmod
Module  Size  Used by
vmw_vsock_vmci_transport32768  1
vsock  40960  2 vmw_vsock_vmci_transport
ata_generic16384  0
crct10dif_pclmul   16384  0
crc32_pclmul   16384  0
vmwgfx331776  1
ttm   126976  1 vmwgfx
ghash_clmulni_intel16384  0
vmw_balloon20480  0
drm_kms_helper208896  1 vmwgfx
intel_rapl_perf16384  0
joydev 24576  0
pcspkr 16384  0
drm   495616  4 vmwgfx,drm_kms_helper,ttm
ahci   40960  0
vmxnet369632  0
ata_piix   36864  0
libahci40960  1 ahci
sg 36864  0
libata270336  4 ata_piix,libahci,ahci,ata_generic
vmw_vmci   81920  2 vmw_balloon,vmw_vsock_vmci_transport
i2c_piix4  24576  0
ac 16384  0
button 20480  0
ip_tables  28672  0
x_tables   45056  1 ip_tables
autofs449152  2
ext4  745472  1
crc16  16384  1 ext4
mbcache16384  1 ext4
jbd2  122880  1 ext4
crc32c_generic 16384  0
fscrypto   32768  1 ext4
ecb16384  0
crc32c_intel   24576  2
sd_mod 61440  3
aesni_intel   200704  0
psmouse   172032  0
aes_x86_64 20480  1 aesni_intel
crypto_simd16384  1 aesni_intel
cryptd 28672  3 crypto_simd,ghash_clmulni_intel,aesni_intel
glue_helper16384  1 aesni_intel
evdev  28672  2
serio_raw  16384  0
vmw_pvscsi 28672  2
scsi_mod  249856  4 vmw_pvscsi,sd_mod,libata,sg

-- /etc/initramfs-tools/modules

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=auto
KEYMAP=n
COMPRESS=gzip
DEVICE=
NFSROOT=auto
RUNSIZE=10%

-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no

-- /sys/block
sda

-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:

/usr/share/initramfs-tools/hooks:
dmsetup
fsck
fuse
keymap
klibc-utils
kmod
resume
thermal
udev
zz-busybox


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

Kernel: Linux 4.19.0-14-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.utf8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.utf8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages initramfs-tools depends on:
ii  initramfs-tools-core  0.133+deb10u1
ii  linux-base4.6

initramfs-tools recommends no packages.

Versions of packages initramfs-tools suggests:
ii  bash-completion  1:2.8-6

-- no debconf information