Bug#984581: pst-utils: Fails to extract email addresses for emails having ARC headers from PST file

[Paul Wise]

On Mon, 2021-04-05 at 06:04 +, Surla, Sai Kalyan wrote:

> Is there any update on the issues.

I discussed the issues with upstream.

Upstream doesn't have time to work on the issues.

Upstream confirmed my suggested solutions sound OK.

I haven't yet had time to work on the solutions.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#986395: sympa: Update `apache2/conf-available/sympa{,-soap}.conf`

[Paul Menzel]

Package: sympa
Version: 6.2.60~dfsg-4
Severity: normal


Dear Debian folks,


The shipped Apache HTTPD drop-in still uses the removed FCGI wrappers.

```
$ dpkg -S apache2/conf-available/sympa
sympa: /etc/apache2/conf-available/sympa-soap.conf
sympa: /etc/apache2/conf-available/sympa.conf
```

```
diff --git a/apache2/conf-available/sympa-soap.conf 
b/apache2/conf-available/sympa-soap.conf

index 57e5f6b..16168a9 100644
--- a/apache2/conf-available/sympa-soap.conf
+++ b/apache2/conf-available/sympa-soap.conf
@@ -3,7 +3,7 @@
 #

 
-ScriptAlias /sympasoap 
/usr/lib/cgi-bin/sympa/sympa_soap_server-wrapper.fcgi

+ScriptAlias /sympasoap /usr/lib/cgi-bin/sympa/sympa_soap_server.fcgi
 
 Require all granted
 
diff --git a/apache2/conf-available/sympa.conf 
b/apache2/conf-available/sympa.conf

index e266eca..9795e52 100644
--- a/apache2/conf-available/sympa.conf
+++ b/apache2/conf-available/sympa.conf
@@ -18,7 +18,7 @@
 Require all granted
 

-ScriptAlias /wws /usr/lib/cgi-bin/sympa/wwsympa-wrapper.fcgi
+ScriptAlias /wws /usr/lib/cgi-bin/sympa/wwsympa.fcgi
 
 Require all granted
 
```


Kind regards,

Paul

Bug#984581: pst-utils: Fails to extract email addresses for emails having ARC headers from PST file

[Surla, Sai Kalyan]

Hi Paul,

Hope you are doing good.
Is there any update on the issues.

Thank you
Sai Kalyan

From: Paul Wise 
Sent: 22 March 2021 12:56 PM
To: Surla, Sai Kalyan ; 984...@bugs.debian.org
Subject: Re: Bug#984581: pst-utils: Fails to extract email addresses for emails 
having ARC headers from PST file

On Mon, 2021-03-22 at 05:41 +, Surla, Sai Kalyan wrote:

> In this case can we still go with the temporary change that you
> suggested as the issue is little different with this PST?

The temporary change will not work for the second PST, since it only
works around the header detection issue, but the second PST doesn't
have the full MIME headers, only the predefined PST To/CC/BCC fields.

There isn't any easy workaround for the issue with the second PST.

--
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#986008: libpdfbox2-java: CVE-2021-27906

[tony mancill]

On Sat, Mar 27, 2021 at 07:54:11PM +0100, Salvatore Bonaccorso wrote:
> Source: libpdfbox2-java
> Version: 2.0.22-1
> Severity: important
> Tags: security upstream
> Forwarded: https://issues.apache.org/jira/browse/PDFBOX-5112
> X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> 

Hi,

I took a look at this and I think the best thing to do for our users is
to upload 2.0.23 instead of trying pick backport just the CVE changes
from this set of commits [1].

The 2.0.23 package builds without any other changes and doesn't
introduce any API changes [2].  This will address both CVE-2021-27807
and CVE-2021-27906.

I have an upload ready (using DEP-14 branches, so it won't change
master).  I originally considered uploading 2.0.23 to experimental due
to the freeze, but I think it should go to unstable and then we can
discuss what we do for bullseye.

Concerns?

Thanks,
tony

[1] https://github.com/apache/pdfbox/compare/2.0.22...2.0.23
[2] japi-compliance-checker against resulting JARs:

$ japi-compliance-checker 2.0.22/usr/share/java/pdfbox2-2.0.22.jar 
2.0.23/usr/share/java/pdfbox2-2.0.23.jar 
Preparing, please wait ...
Using Java 15.0.2
Reading classes 2.0.22 ...
Reading classes 2.0.23 ...
Comparing classes ...
Creating compatibility report ...
Binary compatibility: 100%
Source compatibility: 100%
Total binary compatibility problems: 0, warnings: 0
Total source compatibility problems: 0, warnings: 0
Report: compat_reports/pdfbox2-/2.0.22_to_2.0.23/compat_report.html

$ japi-compliance-checker 2.0.22/usr/share/java/pdfbox2-tools-2.0.22.jar 
2.0.23/usr/share/java/pdfbox2-tools-2.0.23.jar
Preparing, please wait ...
Using Java 15.0.2
Reading classes 2.0.22 ...
Reading classes 2.0.23 ...
Comparing classes ...
Creating compatibility report ...
Binary compatibility: 100%
Source compatibility: 100%
Total binary compatibility problems: 0, warnings: 0
Total source compatibility problems: 0, warnings: 0
Report: compat_reports/pdfbox2-tools/2.0.22_to_2.0.23/compat_report.html


signature.asc
Description: PGP signature

Bug#908204: git-buildpackage: cannot use gbp push without tagging a release

[Norbert Preining]

Took some time, but ..

On Thu, 17 Dec 2020, Guido Günther wrote:
> Would 'gbp push' getting a '--tips' option to just pushes the tips of
> upstream, debian and pristine-tar branch help?

I guess that is what I would normally use ... so yes, that would help.

Thanks

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu + IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#986359: RFS: libubootenv/0.3-1.1 [NMU] [RC] -- Library to access U-Boot environment

[Nobuhiro Iwamatsu]

Hi Bastian,

2021年4月5日(月) 9:09 Bastian Germann :
>
> Am 05.04.21 um 01:35 schrieb Nobuhiro Iwamatsu:
> > And If we put this package in bullseye "Added symbols for
> > libubootenv0.1 (Closes: # 969216)"
> > we need to remove the fix, I think.
>
> Why? The interface does not change. No symbols are added but a symbols FILE 
> is added.

Sorry, I had the wrong understanding about Hard Freeze.
I will upload with #969216.

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#986393: dnss: Recent update overwrote modified configuration files - broke DNS

[se]

Package: dnss
Version: 0.0~git20200927.0.6aad832e-2
Severity: important
X-Debbugs-Cc: b...@mbse.ca

Dear Maintainer,

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

   * What led up to the situation?
- running "apt upgrade"

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
- had to restore all 3 confuration files from backup:
   /etc/default/dnss
   /lib/systemd/system/dnss.socket
   /lib/systemd/system/dnss.service

   * What was the outcome of this action?
- restoring from backup and re-enabling and re-starting dnss restored function

   * What outcome did you expect instead?
- asking about modified configuratiuon files before overwriting them.
- not breaking DNS resolution.

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


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

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

Versions of packages dnss depends on:
ii  libc6  2.31-11

dnss recommends no packages.

dnss suggests no packages.

-- Configuration Files:
/etc/default/dnss changed [not included]

-- no debconf information

Bug#985252: vorta: clicking on the notification bar icon doesnt open the application

[Nicholas D Steeves]

Hi Sandro!

Sandro Tosi  writes:

>> It introduces an additional factor (appletlib); however, if
>> weather-applet with appletlib functions correctly on gnome-flashback
>
> it does "work": it cant find any weather data, but when i left click
> one it "tries" to show "No data available", see attachment, but at
> least it does something.
>

Thank you for testing.  Yes, exactly, we both don't care about the
weather data for the purposes of this bug :-)

>> then I think it will be reasonable to suppose that appletlib has a more
>> correct system-tray implementation than Vorta; Then we can forward both
>> this bug and a link to the GPL3+ appletlib library to Manu, as a PyQt5
>> tray reference implementation--given that appletlib and this bug exist,
>> I suspect system-tray support might not be as straight-forward to
>> implement as the PyQt5 docs indicate.
>
> i think this is a bug in vorta
>

Agreed!  Also, thank you for forwarding this bug.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#986332: lsattr on certiain files in /dev results in "stack smashing detected"

[Bernhard Übelacker]

Hello Chris,


Am 04.04.21 um 22:33 schrieb Chris Hofstaedtler:

Hello Bernhard, Marc,



Some more questions:
1) which kernel version is this?


My test was just inside a temporary VM with current testing.
But I can still reproduce this with current testing kernel at the host too:
Linux rechner 5.10.0-5-amd64 #1 SMP Debian 5.10.24-1 (2021-03-19) x86_64 
GNU/Linux



2) /dev/dri is on tmpfs?


bernhard@rechner:~$ mount
udev on /dev type devtmpfs 
(rw,nosuid,noexec,relatime,size=8075552k,nr_inodes=201,mode=755)
...


Kind regards,
Bernhard

Bug#985825: virtual rms considered mostly harmless

[Holger Levsen]

control: severity -1 important
thanks

So my plan is to replace src:vrms with src:check-dfsg-status and to provide
a nice upgrade path and I might try to get this done for bullseye (caugh), 
(if) with the support of the release team, or maybe not. Then this would be
my plan for bookworm.

In any case this will be staged in experimental soon.

However the outcome of this plan, I do think a virtual rms package in bullseye
(after having that for the last X years) is ok, it's virtual after all - and 
having such a tool is also very worthwhile and enjoyed by many.


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁   holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
 ⠈⠳⣄

Society: Be Yourself!
Society: No, not like that.


signature.asc
Description: PGP signature

Bug#986392: skyview fails to start

[gpe92]

Package: skyview
Version: 3.5.5+repack-1
Severity: normal

Dear Maintainer,

Skyviews fails to start with the following errors:

skyview 
Unable to find settings. Continuing with defaults.
SkyView version is -1.0
Error reading usage file:java.lang.NullPointerException
Unable to instantiate dynamic class null in package skyview.survey:
  null
java.lang.NullPointerException
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:315)
at skyview.util.Utilities.newInstance(Utilities.java:474)
at skyview.executive.Imager.usage(Imager.java:405)
at skyview.executive.Imager.main(Imager.java:268)
Error creating SurveyFinder: null

BR

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

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

Versions of packages skyview depends on:
ii  default-jre-headless  2:1.11-72
ii  jarwrapper0.78
ii  skyview-java  3.5.5+repack-1

skyview recommends no packages.

skyview suggests no packages.

-- no debconf information

Bug#986359: RFS: libubootenv/0.3-1.1 [NMU] [RC] -- Library to access U-Boot environment

[Bastian Germann]

Am 05.04.21 um 01:35 schrieb Nobuhiro Iwamatsu:

And If we put this package in bullseye "Added symbols for
libubootenv0.1 (Closes: # 969216)"
we need to remove the fix, I think.


Why? The interface does not change. No symbols are added but a symbols FILE is 
added.

Bug#986351: (no subject)

[slow_speed]

sudo lpadmin -p PRINTQ -v 
usb://HP/Photosmart%20C3100%20series?serial=CN668B721G04KV&interface=1 
-E -m PPD

[1] 26162
bash: -E: command not found

Bug#986390: RFS: golang-code.rocketnine-tslocum-cbind/0.1.5-1 [ITP] -- Key event handling Golang library for tcell

[Micheal Waltz]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package 
"golang-code.rocketnine-tslocum-cbind":

 * Package name: golang-code.rocketnine-tslocum-cbind
   Version : 0.1.5-1
   Upstream Author : Trevor Slocum 
 * URL : https://code.rocketnine.space/tslocum/cbind
 * License : Expat
 * Vcs : 
https://salsa.debian.org/go-team/packages/golang-code.rocketnine-tslocum-cbind
   Section : devel

It builds those binary packages:

  golang-code.rocketnine-tslocum-cbind-dev - Key event handling Golang library 
for tcell

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

  https://mentors.debian.net/package/golang-code.rocketnine-tslocum-cbind/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/golang-code.rocketnine-tslocum-cbind/golang-code.rocketnine-tslocum-cbind_0.1.5-1.dsc

Changes for the initial release:

 golang-code.rocketnine-tslocum-cbind (0.1.5-1) unstable; urgency=medium
 .
   * Initial release (Closes: #985180)

-- 
Micheal Waltz
https://keybase.io/ecliptik
GPG Fingerprint: 5F70 F2AC BD58 F580 DF15  3D1F 4FA2 70F5 CD36 71F9


signature.asc
Description: PGP signature

Bug#943747: RFA: python-expiringdict -- Python3 caching library

[danieltorres]

Hi Daniel, 

I want to contribute with my help by adopting the package. 

I appreciate if you or someone could point me to the next step in the process.

Kind regards
Daniel Torres

Bug#985182: ITP: golang-code.rocketnine-tslocum-cview -- Terminal-based user interface toolkit for Golang

[Micheal Waltz]

Re-titling to match new source code repository since upstream was moved
to a new git repository.
See: https://lists.debian.org/debian-go/2021/04/msg2.html

* Package name: golang-code.rocketnine-tslocum-cview
  Version : 1.5.4-1
  Upstream Author : Trevor Slocum , Oliver Kuederle
* URL : https://code.rocketnine.space/tslocum/cview
* License : Expat
  Programming Lang: Go
  Description : Terminal-based user interface toolkit for Golang

 cview is a fork of tview (https://github.com/rivo/tview),
 which provides commonly needed components for terminal
 based user interfaces in Go.

-- 
Micheal Waltz
https://keybase.io/ecliptik
GPG Fingerprint: 5F70 F2AC BD58 F580 DF15  3D1F 4FA2 70F5 CD36 71F9


signature.asc
Description: PGP signature

Bug#985180: ITP: golang-code.rocketnine-tslocum-cbind -- Key event handling Golang library for tcell

[Micheal Waltz]

Re-titling to match new source code repository since upstream was moved
to a new git repository.
See: https://lists.debian.org/debian-go/2021/04/msg2.html

* Package name: golang-code.rocketnine-tslocum-cbind
  Version : 0.1.5-1
  Upstream Author : Trevor Slocum 
* URL : https://gitlab.com/tslocum/cbind
* License : Expat
  Programming Lang: Go
  Description : Key event handling Golang library for tcell

 cbind Golang library provides tcell key event encoding,
 decoding and handling.

-- 
Micheal Waltz
https://keybase.io/ecliptik
GPG Fingerprint: 5F70 F2AC BD58 F580 DF15  3D1F 4FA2 70F5 CD36 71F9


signature.asc
Description: PGP signature

Bug#986389: bfh-server: please add Breaks: exim4-config

[Andreas Beckmann]

Package: bfh-server
Version: 20210101-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a similar issue like #985658 in progress-linux-server exists in
bfh-server, too.
I'd assume the same solution will work here, too, but I haven't
tried it.

[partially quoting from #985658]
during a test with piuparts I noticed your package failed to install
with --install-recommends enabled. (It installed fine with
--install-recommends disabled.) Apt does not find a proper dependency
solution due to exim vs. postfix, but adding a Breaks: exim4-config
to progress-linux-server makes the install succeed because possible
solutions that include installing exim (because some dependency of
progress-linux-server (transitively) recommends some MTA) are discarded
early and postfix wins.

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

0m12.5s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmp9dNz5P', 
'apt-get', '-y', 'install', 'bfh-server=20210101-1']
0m13.1s DUMP: 
  Reading package lists...
  Building dependency tree...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   exim4-config : Conflicts: postfix but 3.5.6-1 is to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.
0m13.1s ERROR: Command failed (status=100): ['chroot', 
'/srv/piuparts/tmp/tmp9dNz5P', 'apt-get', '-y', 'install', 
'bfh-server=20210101-1']

cheers,

Andreas


bfh-server_20210101-1.log.gz
Description: application/gzip

Bug#978334: php-finder-facade: FTBFS: Call to undefined method SebastianBergmann\Timer\Timer::resourceUsage()

[Logan Rosen]

Control: tags -1 patch

Hi,

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

  * d/p/0009-Compatibility-with-php-timer-4.0.patch: Cherrypick upstream
commit to fix compatibility with php-timer >= 4.0.

Thanks for considering the patch.

Logan
diff -Nru 
phpdox-0.12.0/debian/patches/0009-Compatibility-with-php-timer-4.0.patch 
phpdox-0.12.0/debian/patches/0009-Compatibility-with-php-timer-4.0.patch
--- phpdox-0.12.0/debian/patches/0009-Compatibility-with-php-timer-4.0.patch
1969-12-31 19:00:00.0 -0500
+++ phpdox-0.12.0/debian/patches/0009-Compatibility-with-php-timer-4.0.patch
2021-04-04 18:35:45.0 -0400
@@ -0,0 +1,54 @@
+From a71dfe4ffce072eb8402e5fd5303e6b3076ee0e7 Mon Sep 17 00:00:00 2001
+From: homerjsimpson000 
+Date: Mon, 14 Dec 2020 09:13:14 +0100
+Subject: [PATCH] Update ShellProgressLogger.php
+
+Use ResourceUsageFormatter instead of Timer::resourceUsage to enable updating 
to use both Timer ^2.0 and Timer 5.0.*
+---
+ src/logger/ShellProgressLogger.php | 26 +-
+ 1 file changed, 25 insertions(+), 1 deletion(-)
+
+diff --git a/src/logger/ShellProgressLogger.php 
b/src/logger/ShellProgressLogger.php
+index 1017dda1..d76fdfd4 100644
+--- a/src/logger/ShellProgressLogger.php
 b/src/logger/ShellProgressLogger.php
+@@ -1,6 +1,7 @@
+ resourceUsage();
+ print "\n\n";
+ }
++
++/**
++ * @return string
++ */
++private function resourceUsage(): string {
++$result = '';
++
++if(
++class_exists(ResourceUsageFormatter::class) &&
++method_exists(ResourceUsageFormatter::class, 
'resourceUsageSinceStartOfRequest')
++) {
++/** @var ResourceUsageFormatter $resource */
++$resource = new ResourceUsageFormatter();
++$result = $resource->resourceUsageSinceStartOfRequest();
++} else if(
++class_exists(Timer::class) &&
++method_exists(Timer::class, 'resourceUsage')
++) {
++$result = Timer::resourceUsage();
++}
++
++return $result;
++}
+ }
diff -Nru phpdox-0.12.0/debian/patches/series 
phpdox-0.12.0/debian/patches/series
--- phpdox-0.12.0/debian/patches/series 2020-12-21 07:03:11.0 -0500
+++ phpdox-0.12.0/debian/patches/series 2021-04-04 18:35:45.0 -0400
@@ -6,3 +6,4 @@
 0006-Compatibility-with-recent-PHPUnit-8.patch
 0007-Drop-versioned-dependency-that-can-t-be-satisfied.patch
 0008-Adapt-to-recent-version-of-PHPUnit-9.patch
+0009-Compatibility-with-php-timer-4.0.patch

Bug#986351: (no subject)

[Brian Potkin]

> usb://HP/Photosmart%20C3100%20series?serial=CN668B721G04KV&interface=1
> hp:/usb/Photosmart_C3100_series?serial=CN668B721G04KV

These are URIs. Either is valid, but the second is advised when easy
access to the scanner is wanted. Substitute a URI in the lpadmin
command below.

The PPD for your device is

  drv:///hpcups.drv/hp-photosmart_c3100_series.ppd

This gets substituted for PPD in the lpadnin command below.

Set up a print queue with

  lpadmin -p PRINTQ -v URI -E -m PPD

Test printing with

  lp -d PRINTQ /etc/nsswitch.conf

PRINTQ can be anything you choose, such as c3100.



I will also copy and post this and subsequent mails via a Gmail
account.

The mail should also be viewable at

  https://lists.debian.org/debian-printing/2021/04/threads.html



Regards,

Brian.


On Sun, 4 Apr 2021 at 22:45,  wrote:
>
> file cups-brf:/
> network http
> network socket
> network beh
> network ipp
> network https
> network lpd
> network ipps
> serial serial:/dev/ttyS0?baud=115200
> direct
> usb://HP/Photosmart%20C3100%20series?serial=CN668B721G04KV&interface=1
> direct hp:/usb/Photosmart_C3100_series?serial=CN668B721G04KV
> direct hpfax
> network smb
>

Bug#986351: hplip: Printing Places All Jobs On Hold

[Brian Potkin]

On Sun 04 Apr 2021 at 17:43:41 -0400, slow_sp...@att.net wrote:

> usb://HP/Photosmart%20C3100%20series?serial=CN668B721G04KV&interface=1
> hp:/usb/Photosmart_C3100_series?serial=CN668B721G04KV

These are URIs. Either is valid, but the second is advised when easy
access to the scanner is wanted. Substitute a URI in the lpadmin
command below.

The PPD for your device is

  drv:///hpcups.drv/hp-photosmart_c3100_series.ppd

This gets substituted for PPD in the lpadnin command below.

Set up a print queue with

  lpadmin -p PRINTQ -v URI -E -m PPD

Test printing with

  lp -d PRINTQ /etc/nsswitch.conf

PRINTQ can be anything you choose, such as c3100.



I will also copy and post this and subsequent mails via a Gmail account.

The mail should also be viewable at

  https://lists.debian.org/debian-printing/2021/04/threads.html



Regards,

Brian.

Bug#986332: lsattr on certiain files in /dev results in "stack smashing detected"

[Chris Hofstaedtler]

Hi Marc,

thanks for the followup.

* Marc Haber  [210404 22:03]:
> On Sun, Apr 04, 2021 at 10:33:46PM +0200, Chris Hofstaedtler wrote:
> > * Bernhard Übelacker  [210404 20:32]:
> > > Dear Maintainer,
> > > tried to locate the exact smashing.
> > > It looks like the ioctl(EXT2_IOC_GETFLAGS) takes an int* parameter,
> > > but writes 8 bytes instead of just sizeof(int) to the given address.
> > 
> > Some more questions:
> > 1) which kernel version is this?
> > 2) /dev/dri is on tmpfs?
> 
> 1 [2/4021]mh@testsid85:~ $ sudo lsattr /dev/dri/card0 
> [sudo] password for mh: 
> *** stack smashing detected ***: terminated
> Aborted
> 134 [3/4022]mh@testsid85:~ $ uname -a
> Linux testsid85 5.10.0-5-amd64 #1 SMP Debian 5.10.26-1 (2021-03-27) x86_64 
> GNU/Linux
> [4/4023]mh@testsid85:~ $ stat -f /dev/dri
>   File: "/dev/dri"
> ID: 0Namelen: 255 Type: tmpfs
> Block size: 4096   Fundamental block size: 4096
> Blocks: Total: 40336  Free: 40336  Available: 40336
> Inodes: Total: 40336  Free: 39600
> [5/4024]mh@testsid85:~ $ 
> 
> Other /dev device nods can be lsattr'd without error.

I was wondering about changes since buster, and indeed:

Upstream commit 40ea4628 [1] removes the lstat call which shielded
the ioctl call later on. On buster, lsattr /dev/dri/card0 just
gives:
  lsattr: Operation not supported While reading flags on /dev/dri/card0

(Even with Linux 5.10.0-0.bpo.3-amd64.)


Now, for the actual issue:

AFAICT, for /dev/dri/card0 the ioctl ends up in the kernel's
drm_ioctl [2], which will blindly call copy_to_user assuming the
output size is the same as the input size (8 bytes). This is wrong
for FS_IOC_GETFLAGS, at least for normal files.

Maybe the best thing is to put the lstat check back in?
Or maybe lsattr should expect that the kernel might actually use the
8 bytes? I have checked various fs ioctl functions, and they all
seem to return 4 bytes, except for orangefs [3] ... 

Chris

[1] 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/lib/e2p/fgetflags.c?id=40ea4628ba1b55f8eba311f12399d039698dbeeb
[2] 
https://elixir.bootlin.com/linux/v5.10.27/source/drivers/gpu/drm/drm_ioctl.c#L888
[3] https://elixir.bootlin.com/linux/v5.10.27/source/fs/orangefs/file.c#L378

Bug#986387: cdrom: Unsuccessful installation on Windows10-Dell-Latitude-Ultrabook. No grub.

[enno]

Package: cdrom
Severity: important

Dear Maintainer,

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

Jigdone a debian-10.9.0-amd64-xfce-CD1 USB-Stick.  Booted a Dell Latitude
Ultrabook with preinstalled Windows 10 from aforesaid USB-Stick.  Performed
full installation including resizing the NTFS partition and including
installation of grub(2).  Rebooted.  No bootable media found.
On reboot via F12 I could select Windows Boot Manager to boot successfully into
Windows10.  But Grub or Linux are not available.

Windows10 recognises the resize of the NTFS partition, the
additional partitions sda4 (root) and sda5 (swap) are recognised as well.

UEFI booting presents a "normal" Windows 10.
Legacy booting says, no bootable media found.
Booting via UEFI-->Windows Bootmanager boots Windows 10.
Legacy AND UEFI booting Installation-USB-Stick work up to the point to
register the disk(s), and there it stops, it doesn't seem to recognise the
partition table, that the installer has written and is also reported by
Windows10.

It just presents an unformatted disk of MAX units to go on with.  But Windows
DatentrÀgerverwaltung does indeed see the created partitions.

I'm at a loss.

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (x86_64)

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT@euro, LC_CTYPE=de_AT@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#986388: sympa: Migrate lines with backticks

[Paul Menzel]

Package: sympa
Version: 6.2.60~dfsg-4
Severity: normal


Dear Debian folks,


Sympa fails to start, if `sympa.conf` has lines with backticks in it. 
It’d be great, if these could be migrated automatically, or the 
`NEWS.Debian` would list the change, so users reading the NEWS files 
before upgrading can prepare for that change.


In my case, I did:

-#syslog `cat /etc/sympa/facility`
+#syslog LOCAL1


Kind regards,

Paul

Bug#983389: closed by Debian FTP Masters (reply to Yangfl ) (Bug#983389: fixed in finit 4.0~rc3-1)

[Adrian Bunk]

On Sat, Mar 20, 2021 at 08:27:07PM +, Debian Bug Tracking System wrote:
>...
>  finit (4.0~rc3-1) unstable; urgency=medium
>  .
>* New upstream release
>* Enable some services by default (Closes: #983389)
>...

If finit should be in bullseye, this bug needs a more targeted fix
that fixes only the bug and does not include a new upstream version.

cu
Adrian

Bug#986351: (no subject)

[slow_speed]

Also, closed the toolbox and it is no where to be found even though 
installed.

Bug#986358: hardening-runtime: Restrictions on /etc/pam.d/ break X screensavers

[Topi Miettinen]

On 4.4.2021 16.23, Andrew Savchenko wrote:

Hello Yves-Alexis,

Sunday, April 4, 2021, 7:35:46 PM, you wrote:


statoverride in hardening-runtime were added by Topi Miettinen so I'm adding
him in the loop for comments.


For the screensavers specifically, I have narrowed it down to /etc/pam.d only.
chmod'ing it to the default 0755 fixes the issue.


Very strange, I actually also have 0755. I think this line should be 
removed.



There might be more dragons though as this is somewhat similar to openSUSE:
https://github.com/openSUSE/permissions/blob/master/profiles/permissions.paranoid


I didn't see any reference to pam.d here though.

-Topi

Bug#986351: (no subject)

[slow_speed]

Always.  Unless I reboot the computer and turn on the printer first.  At 
least that is what I discovered so far.  Can't guaranty that however.

Bug#986382: DPL Jonathan Carter's passport number is *******

[Jean-Philippe MENGUAL]

Hi guys,

Please stop replying. That is a troll, will be banned quickly, dont 
maintain it alive. Just ignore, listmaster and bts will do what is 
needed. Keep power for other more interesting things.


Regards

Le 04/04/2021 à 23:18, crazy.mo...@lavache.com a écrit :



If you don't want these ego-maniacs to use your name in their vendettas 
you can resign from Debian.  This is the choice.  How many people will 
resign if Debian votes to attack Stallman?  Please tell us before the 
vote finishes so we call can know this now.


No matter the outcome of this vote.  Having the vote at all suggests 
that people are expendable.  Volunteers can be hung over the side of the 
ship while people have an email argument about what to do next.


Why don't you understand how toxic this is?

There are so many years of defamation in Debian now.  Delete it all 
now.  Delete the negative options from the vote now.  Please stop or we 
stop you.





From: Stephan Lachnit 
To: crazy.mo...@lavache.com
Subject: Re: Bug#986382: DPL Jonathan Carter's passport number is ***
Date: 04/04/2021 22:38:20 Europe/Paris
Cc: 986...@bugs.debian.org;
   debian-de...@lists.debian.org

> Why does the toxic woman want to destroy reputations?

If you refer to Jonathan Carter, that isn't even the person that
started the vote, nor an original author of the open letter. Do your
research, tbh to me it seems like you are a complete outsider.

> Destroy nobody - Or destroy everybody! You can't have it both ways.

First of all, nobody wants to "destroy" RMS. Calling someone to resign
isn't destroying them, especially if they were just (secretly)
elected.

Secondly, why are you so toxic and want to "destroy" everybody? There
is really no point, all you do is make the FLOSS community weaker and
more divided. And since you seem to care about RMS and his ideas, I
don't think that is something you would like.

> If Debian is a vehicle for defamation, every one of you faces full 
consequences.


Debian is a democracy. Assume one person votes in favor of RMS (which
as you can see some people will do), why do you want them to face your
alleged consequences? That doesn't make sense. They have no power to
do the things you ask for. In fact, nobody in Debian has. Again, I
don't think you understand the Debian project at all.

> Your jobs are the targets. Your families are targets.

I can understand that you are angry even if I don't agree with your
views, but I don't think anyone here wants to harm RMS. Everyone here
just wants the best for the FLOSS community. Why do you want to harm
them so badly?

Opinions on how what's the best for the community may differ, but
that's fine. Discussions are healthy, as long as they stay friendly
(btw your mails aren't). I have learned a lot from discussions, and
yes sometimes people (me included) get unfriendly or say things that
turn out to be false. But as long as we apologize for mistakes, we can
grow from it.

> No volunteer should have to suffer you toxic people

Don't you think, just maybe, that we shouldn't suffer from your
toxicity as well? Especially since we will suffer much more than you
can ever suffer from this. I mean, what's the worst that can happen
from your point of view? RMS resigns again? Then everything would be
just like a month ago.

Regards,
Stephan

Bug#986351: (no subject)

[slow_speed]

file cups-brf:/
network http
network socket
network beh
network ipp
network https
network lpd
network ipps
serial serial:/dev/ttyS0?baud=115200
direct 
usb://HP/Photosmart%20C3100%20series?serial=CN668B721G04KV&interface=1

direct hp:/usb/Photosmart_C3100_series?serial=CN668B721G04KV
direct hpfax
network smb

Bug#986382: DPL Jonathan Carter's passport number is ****909

[Pierre-Elliott Bécue]

Le dimanche 04 avril 2021 à 21:22:16+0200, crazy.mo...@lavache.com a écrit :
> Package: wnpp
> Severity: wishlist
> X-Debbugs-CC: 
> debian-proj...@lists.debian.org,debian-v...@lists.debian.org,debian-de...@lists.debian.org
> 
> 
> We are contributors to Debian
> 
> The contribution of every one of us makes the name Debian respectable
> 
> We can't allow a crazy woman who slept with a past project leader to hijack 
> the name of the project and use it to scar volunteers.  This happened to many 
> times.  It stops now.
> 
> Please stop!  Delete all fascism and defamation about any volunteer that has 
> been instigated from Debian in any form whatsoever.  Delete it from the vote, 
> web pages, search engines.
> 
> Please stop!  Delete all negative options from the RMS vote.  We only want 
> positive options or nothing.  We will not tolerate any outcome that is 
> negative for a volunteer
> 
> If the mob does not respect our request, we are making a data dump of all the 
> DebConf personal data.  DPL Jonathan Carter's passport number is 909.
> 
> Privacy for everybody or privacy for nobody

Go to sleep, Dan, you're drunk.

-- 
Pierre-Elliott Bécue

Bug#986379: utfout: [INTL:nb] Norwegian Bokmål initial translation

[David Schledewitz]

Package: utfout
Version: 0.0.1
Severity: wishlist
Tags: l10n patch


Hi,

The initial Norwegian Bokmål translation for utfout is attached.
# Copyright (C) 2021 Free Software Foundation, Inc.
# This file is distributed under the same license as the utfout package.
#
# David Schledewitz , 2021.
msgid ""
msgstr ""
"Project-Id-Version: utfout 0.0.1\n"
"Report-Msgid-Bugs-To: james.h...@ubuntu.com\n"
"POT-Creation-Date: 2012-09-19 20:23+0100\n"
"PO-Revision-Date: 2021-04-04 08:54+0200\n"
"Last-Translator: David Schledewitz \n"
"Language-Team: Norwegian Bokmål <>\n"
"Language: nb\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Lokalize 19.12.3\n"

#: src/utfout.c:1370
msgid "version"
msgstr "versjon"

#: src/utfout.c:1371
msgid "License"
msgstr "Lisens"

#: src/utfout.c:1372
msgid "Written by"
msgstr "Skrevet av"

Bug#986385: sympa: Package `wwsympa.service`

[Paul Menzel]

Package: sympa
Version: 6.2.60~dfsg-4
Severity: normal


Dear Debian folks,


Thank you for maintaining the package *sympa*.

It’d be great, if you packaged the systemd service unit 
`wwsympa.service` so the template [1] does not need to be adapted.


```
[Unit]
Description=WWSympa - Web interface for Sympa mailing list manager
After=syslog.target sympa.service

[Service]
Type=forking
PIDFile=--piddir--/wwsympa.pid
ExecStart=/usr/bin/spawn-fcgi -F $FCGI_CHILDREN \
-P --piddir--/wwsympa.pid \
-s --piddir--/wwsympa.socket \
-u $FCGI_USER -g $FCGI_GROUP $FCGI_OPTS -- \
--execcgidir--/wwsympa.fcgi
Environment="FCGI_CHILDREN=5"
Environment="FCGI_USER=--USER--"
Environment="FCGI_GROUP=--GROUP--"
Environment="FCGI_OPTS=-M 0600 -U nginx"
EnvironmentFile=-/etc/sysconfig/sympa
Restart=always

[Install]
WantedBy=multi-user.target
```


Kind regards,

Paul


[1]: 
https://github.com/sympa-community/sympa/blob/3f44b653a3c174a29920768e5bab530e76d245f4/src/etc/script/wwsympa.servicein

Bug#986386: ITP: r-cran-performanceanalytics -- GNU R Econometric Tools for Performance and Risk Analysis

[Shayan Doust]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: he...@shayandoust.me

Subject: ITP: r-cran-performanceanalytics -- GNU R Econometric Tools for 
Performance and Risk Analysis
Package: wnpp
Owner: Shayan Doust 
Severity: wishlist

* Package name: r-cran-performanceanalytics
  Version : 2.0.4
  Upstream Author : Brian G. Peterson,
* URL : https://cran.r-project.org/package=PerformanceAnalytics
* License : GPL-2
  Programming Lang: GNU R
  Description : GNU R Econometric Tools for Performance and Risk Analysis
 Collection of econometric functions for performance and risk
 analysis. In addition to standard risk and performance metrics, this
 package aims to aid practitioners and researchers in utilizing the latest
 research in analysis of non-normal return streams.  In general, it is most
 tested on return (rather than price) data on a regular scale, but most
 functions will work with irregular return data as well, and increasing
 numbers of functions will work with P&L or price data where possible.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-performanceanalytics

Bug#986384: [Courier-imap] courier and maildrop it seems does not work as xpected

[PICCORO McKAY Lenz]

Source: courier
Severity: grave
Justification: causes non-serious data loss

I setup both : real system users and virtual ones, both servers have mixed
users nature (system ones and virtuals)

The specific build removal of the courier-maildrop package breaks the
courier MTA utilizing the virtual accounts tools, noted that some variables
are imported that normal build of maildrop does not! (I compared the rules
files of both), those are HOME, SHELL, LOGNAME and MAILDIRQUOTA while the
standalone version won't.

MArkus.. i revised and checked related bugs in debian and it seems that
standar "maildrop" package is a piece of crap respect of this..  for
working i must get back the older courier-maildrop and builds my own
package from courier sources, can you get back the build of
courier-maildrop i remember that i previously send a request about this!

SAM: but,i cannot understand pretty well .. we need to clarify this cos i
try to reproduce and i dont know if this was the problem, i do not set any
sticky bit in home users.. but my home users are under a subdirectory..
maybe this can be misinterpreted?

i found this problem randomly in newer versions of debian packages (i try
to compile from sources and i do not have such problem) and  in one
particular scenery ALWAYS are reproducible:

a) server are in a migration of ip and upgrading of programs
b) there's some dynamic deliveries pending
c) mail queue has almost 200 thousands of pending mails

When I changed the DNS to the new server with exact configuration, but
another ip, mails are delivered in log and courier system, but if you use
lasted maildrop debian shit it does not work! all the new mails are
delivered and dissapears (are in queue only but log as delivered)

El dom, 4 de abr. de 2021 a la(s) 12:04, Sam Varshavchik (
mr...@courier-mta.com) escribió:

> PICCORO McKAY Lenz writes:
>
> > I have installed maildrop (no longer courier-maildrop) and I am
> surprised to
> > find that the mails are not arriving at Maildir user place, even
> > at /var/mail/spool/$USER file! . that's i ask here to you guys cos i
> dont
> > know if the problem is dropmail debian package (build separately puff)
> or
> > courier..
>
> It's a long-standing problem with the debian package.
>
> > I define correctly the maildellivery in imap etc etc but I notice that
> the
> > mail is in /var/spool/mail instead of in the user's home... and I
> already
> > defined in /etc/maildroprc the DEFAULT
>
> Except that the standalone maildrop build is not going to know what the
> DEFAULT is, without the appropriate -d option.
>
> I do not remember any more details, this problem comes up every once in a
> while.
>
> ___
> Courier-imap mailing list
> courier-i...@lists.sourceforge.net
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
>

Bug#986382: DPL Jonathan Carter's passport number is *******

[crazy . molly]

If you don't want these ego-maniacs to use your name in their vendettas you can 
resign from Debian.  This is the choice.  How many people will resign if Debian 
votes to attack Stallman?  Please tell us before the vote finishes so we call 
can know this now.



No matter the outcome of this vote.  Having the vote at all suggests that 
people are expendable.  Volunteers can be hung over the side of the ship while 
people have an email argument about what to do next.



Why don't you understand how toxic this is?



There are so many years of defamation in Debian now.  Delete it all now.  
Delete the negative options from the vote now.  Please stop or we stop you.






From: Stephan Lachnit 
To: crazy.mo...@lavache.com
Subject: Re: Bug#986382: DPL Jonathan Carter's passport number is ***
Date: 04/04/2021 22:38:20 Europe/Paris
Cc: 986...@bugs.debian.org;
   debian-de...@lists.debian.org

> Why does the toxic woman want to destroy reputations?

If you refer to Jonathan Carter, that isn't even the person that
started the vote, nor an original author of the open letter. Do your
research, tbh to me it seems like you are a complete outsider.

> Destroy nobody - Or destroy everybody! You can't have it both ways.

First of all, nobody wants to "destroy" RMS. Calling someone to resign
isn't destroying them, especially if they were just (secretly)
elected.

Secondly, why are you so toxic and want to "destroy" everybody? There
is really no point, all you do is make the FLOSS community weaker and
more divided. And since you seem to care about RMS and his ideas, I
don't think that is something you would like.

> If Debian is a vehicle for defamation, every one of you faces full 
> consequences.

Debian is a democracy. Assume one person votes in favor of RMS (which
as you can see some people will do), why do you want them to face your
alleged consequences? That doesn't make sense. They have no power to
do the things you ask for. In fact, nobody in Debian has. Again, I
don't think you understand the Debian project at all.

> Your jobs are the targets. Your families are targets.

I can understand that you are angry even if I don't agree with your
views, but I don't think anyone here wants to harm RMS. Everyone here
just wants the best for the FLOSS community. Why do you want to harm
them so badly?

Opinions on how what's the best for the community may differ, but
that's fine. Discussions are healthy, as long as they stay friendly
(btw your mails aren't). I have learned a lot from discussions, and
yes sometimes people (me included) get unfriendly or say things that
turn out to be false. But as long as we apologize for mistakes, we can
grow from it.

> No volunteer should have to suffer you toxic people

Don't you think, just maybe, that we shouldn't suffer from your
toxicity as well? Especially since we will suffer much more than you
can ever suffer from this. I mean, what's the worst that can happen
from your point of view? RMS resigns again? Then everything would be
just like a month ago.

Regards,
Stephan

Bug#986374: zfs-zed: broken purge detection in postrm script

[Chris Hofstaedtler]

* наб  [210404 20:54]:
> /var/lib/dpkg/info/zfs-zed.postrm: 7: [: upgrade: unexpected operator

Apparently introduced in the fix for #983401.

Chris

Bug#986332: lsattr on certiain files in /dev results in "stack smashing detected"

[Marc Haber]

Hi Chris,

On Sun, Apr 04, 2021 at 10:33:46PM +0200, Chris Hofstaedtler wrote:
> * Bernhard Übelacker  [210404 20:32]:
> > Dear Maintainer,
> > tried to locate the exact smashing.
> > It looks like the ioctl(EXT2_IOC_GETFLAGS) takes an int* parameter,
> > but writes 8 bytes instead of just sizeof(int) to the given address.
> 
> Some more questions:
> 1) which kernel version is this?
> 2) /dev/dri is on tmpfs?

1 [2/4021]mh@testsid85:~ $ sudo lsattr /dev/dri/card0 
[sudo] password for mh: 
*** stack smashing detected ***: terminated
Aborted
134 [3/4022]mh@testsid85:~ $ uname -a
Linux testsid85 5.10.0-5-amd64 #1 SMP Debian 5.10.26-1 (2021-03-27) x86_64 
GNU/Linux
[4/4023]mh@testsid85:~ $ stat -f /dev/dri
  File: "/dev/dri"
ID: 0Namelen: 255 Type: tmpfs
Block size: 4096   Fundamental block size: 4096
Blocks: Total: 40336  Free: 40336  Available: 40336
Inodes: Total: 40336  Free: 39600
[5/4024]mh@testsid85:~ $ 

Other /dev device nods can be lsattr'd without error.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#986382: DPL Jonathan Carter's passport number is *******

[Stephan Lachnit]

> Why does the toxic woman want to destroy reputations?

If you refer to Jonathan Carter, that isn't even the person that
started the vote, nor an original author of the open letter. Do your
research, tbh to me it seems like you are a complete outsider.

> Destroy nobody - Or destroy everybody!  You can't have it both ways.

First of all, nobody wants to "destroy" RMS. Calling someone to resign
isn't destroying them, especially if they were just (secretly)
elected.

Secondly, why are you so toxic and want to "destroy" everybody? There
is really no point, all you do is make the FLOSS community weaker and
more divided. And since you seem to care about RMS and his ideas, I
don't think that is something you would like.

> If Debian is a vehicle for defamation, every one of you faces full 
> consequences.

Debian is a democracy. Assume one person votes in favor of RMS (which
as you can see some people will do), why do you want them to face your
alleged consequences? That doesn't make sense. They have no power to
do the things you ask for. In fact, nobody in Debian has. Again, I
don't think you understand the Debian project at all.

> Your jobs are the targets.  Your families are targets.

I can understand that you are angry even if I don't agree with your
views, but I don't think anyone here wants to harm RMS. Everyone here
just wants the best for the FLOSS community. Why do you want to harm
them so badly?

Opinions on how what's the best for the community may differ, but
that's fine. Discussions are healthy, as long as they stay friendly
(btw your mails aren't). I have learned a lot from discussions, and
yes sometimes people (me included) get unfriendly or say things that
turn out to be false. But as long as we apologize for mistakes, we can
grow from it.

> No volunteer should have to suffer you toxic people

Don't you think, just maybe, that we shouldn't suffer from your
toxicity as well? Especially since we will suffer much more than you
can ever suffer from this. I mean, what's the worst that can happen
from your point of view? RMS resigns again? Then everything would be
just like a month ago.

Regards,
Stephan

Bug#986332: lsattr on certiain files in /dev results in "stack smashing detected"

[Chris Hofstaedtler]

Hello Bernhard, Marc,

* Bernhard Übelacker  [210404 20:32]:
> Dear Maintainer,
> tried to locate the exact smashing.
> It looks like the ioctl(EXT2_IOC_GETFLAGS) takes an int* parameter,
> but writes 8 bytes instead of just sizeof(int) to the given address.

Some more questions:
1) which kernel version is this?
2) /dev/dri is on tmpfs?

Chris

Bug#754809: Debian bug-tracking system still generating bouncing emails that violate DMARC

[Jonathan Kamens]

This bug, first opened almost 7 years ago, originally concerned the fast
that emails sent through lists.dmarc.org were violating DMARC, causing
bounces, and in general causing mayhem for domains with p=reject DMARC
policies and users whose mail providers enforce DMARC.

Since then it appears that lists.dmarc.org was fixed, bug
bugs.debian.org is still broken. I reported a couple of bugs to
bugs.debian.org recently for the first time in a while, and I see from
my incoming DMARC aggregate reports that I've received hundreds of
notifications about invalid notification emails sent as a result by
bugs.debian.org.

My domain has a p=reject DMARC policy, which means that users whose
email providers enforce DMARC (pretty much all the major email providers
nowadays) simply aren't going to see the emails about the bugs I report.
This is going to be true for a lot of people, and it significantly
hampers the effectiveness of the bug-tracking system.

I don't even know if the maintainers of the packages I report bugs about
see my bugs. They may have no idea they were filed, because their email
providers bounced the notifications or put them into their Spam folders.

The last activity recorded for this bug was nearly two years ago.

FYI Ubuntu fixed this issue in Launchpad something like a year ago.

It sure would be nice if Debian fixed it.

  jik

Bug#986382: DPL Jonathan Carter's passport number is *******

[crazy . molly]

> If you were, why do you try to destroy it with this attempt?


Why does the toxic woman want to destroy reputations?

Destroy nobody - Or destroy everybody!  You can't have it both ways.

If Debian is a vehicle for defamation, every one of you faces full consequences.

Your jobs are the targets.  Your families are targets.

No volunteer should have to suffer you toxic people

Molly is the toxic icing on the toxic cake

Bug#986383: unblock: nageru/2.0.0-3

[Steinar H. Gunderson]

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

Please unblock package nageru

Hi Release Team and Hats,

Would it be possible to unblock nageru 2.0.1-3, which I just uploaded?
The changes are:

  1. Reenable build-dep on srt (I was asked to remove it, since srt was
 RC-buggy, but it turned out to stay in testing after all).
  2. A critical one-line bugfix (from upstream git) that prevents correct
 transcoding.

diff -Nru nageru-2.0.1/debian/changelog nageru-2.0.1/debian/changelog
--- nageru-2.0.1/debian/changelog   2021-01-10 13:39:12.0 +0100
+++ nageru-2.0.1/debian/changelog   2021-04-04 21:26:11.0 +0200
@@ -1,3 +1,11 @@
+nageru (2.0.1-3) unstable; urgency=medium
+
+  * Reenable the SRT support, as the srt package was fixed again. 
+  * fix-ffmpeg-height-calculation.diff: New patch from upstream git,
+fixes resolution calculation in kaeru due to a typo.
+
+ -- Steinar H. Gunderson   Sun, 04 Apr 2021 21:26:11 +0200
+
 nageru (2.0.1-2) unstable; urgency=medium
 
   * Build without SRT support (remove the build-dependency on
diff -Nru nageru-2.0.1/debian/control nageru-2.0.1/debian/control
--- nageru-2.0.1/debian/control 2021-01-10 13:39:08.0 +0100
+++ nageru-2.0.1/debian/control 2021-04-04 21:26:11.0 +0200
@@ -5,7 +5,7 @@
 # lld is strictly optional, but depending on it means the build is more 
reproducible;
 # the result doesn't depend on whether the package was installed or not.
 # However, there's a bug on i386 where it doesn't link properly.
-Build-Depends: debhelper (>= 13), qtbase5-dev, libqt5opengl5-dev, pkg-config, 
libusb-1.0-0-dev, libmovit-dev (>= 1.5.2), libmicrohttpd-dev, libx264-dev, 
libavcodec-dev, libavformat-dev (>= 7:3.1), libswscale-dev, libva-dev, 
libavresample-dev, libegl1-mesa-dev, libasound2-dev, libzita-resampler-dev, 
libluajit-5.1-dev, libbmusb-dev (>= 0.7.4), protobuf-compiler, libprotobuf-dev, 
libqcustomplot-dev, meson (>= 0.47), libjpeg-dev, libsqlite3-dev, libdrm-dev, 
lld [!i386]
+Build-Depends: debhelper (>= 13), qtbase5-dev, libqt5opengl5-dev, pkg-config, 
libusb-1.0-0-dev, libmovit-dev (>= 1.5.2), libmicrohttpd-dev, libx264-dev, 
libavcodec-dev, libavformat-dev (>= 7:3.1), libswscale-dev, libva-dev, 
libavresample-dev, libegl1-mesa-dev, libasound2-dev, libzita-resampler-dev, 
libluajit-5.1-dev, libbmusb-dev (>= 0.7.4), protobuf-compiler, libprotobuf-dev, 
libqcustomplot-dev, meson (>= 0.47), libjpeg-dev, libsqlite3-dev, libdrm-dev, 
lld [!i386], libsrt-gnutls-dev
 Build-Conflicts: lld [i386]
 Standards-Version: 4.5.0
 Homepage: https://nageru.sesse.net/
diff -Nru nageru-2.0.1/debian/patches/fix-ffmpeg-height-calculation.diff 
nageru-2.0.1/debian/patches/fix-ffmpeg-height-calculation.diff
--- nageru-2.0.1/debian/patches/fix-ffmpeg-height-calculation.diff  
1970-01-01 01:00:00.0 +0100
+++ nageru-2.0.1/debian/patches/fix-ffmpeg-height-calculation.diff  
2021-04-04 21:26:11.0 +0200
@@ -0,0 +1,13 @@
+Index: nageru-2.0.1/nageru/ffmpeg_capture.cpp
+===
+--- nageru-2.0.1.orig/nageru/ffmpeg_capture.cpp
 nageru-2.0.1/nageru/ffmpeg_capture.cpp
+@@ -1109,7 +1109,7 @@ unsigned FFmpegCapture::frame_height(con
+   if (height == 0) {
+   return frame->height;
+   } else {
+-  return width;
++  return height;
+   }
+ }
+ 
diff -Nru nageru-2.0.1/debian/patches/series nageru-2.0.1/debian/patches/series
--- nageru-2.0.1/debian/patches/series  2019-04-19 09:24:23.0 +0200
+++ nageru-2.0.1/debian/patches/series  2021-04-04 21:26:11.0 +0200
@@ -0,0 +1 @@
+fix-ffmpeg-height-calculation.diff

unblock nageru/2.0.0-3

-- System Information:
Debian Release: 10.9
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'proposed-updates'), (500, 
'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.11.0 (SMP w/40 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NO:en_US:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#978450: fixed upstream

[Łukasz Stelmach]

Control: fixed -1 0.19~pre1+git20201123.8d73c8f0+dfsg1-1

The bug has been fixed somewhere between upstream commits 3fcbf71fb5
(last failing) and 435815ccc8 (first working). Alas, the commits between
are large and don't build and I was unable to spot the exact fix.

-- 
Miłego dnia,
Łukasz Stelmach


signature.asc
Description: PGP signature

Bug#986382: DPL Jonathan Carter's passport number is *******

[Stephan Lachnit]

> We are contributors to Debian
>
> The contribution of every one of us makes the name Debian respectable

If you were, why do you try to destroy it with this attempt?

> Please stop!  Delete all fascism and defamation about any volunteer that has 
> been instigated from Debian in any form whatsoever.  Delete it from the vote, 
> web pages, search engines.
>
> Please stop!  Delete all negative options from the RMS vote.  We only want 
> positive options or nothing.  We will not tolerate any outcome that is 
> negative for a volunteer
>
> If the mob does not respect our request, we are making a data dump of all the 
> DebConf personal data.

Wtf please relax. The vote isn't even finished. And let's assume the
project would vote against it, why do you want everything to be
deleted? That's just stupid.

Also, let's suppose you are a contributor to Debian (which I doubt),
why do you contribute to a project which rules you don't respect? Why
do you try to hurt everyone, even those who might vote in favor of
supporting RMS?

Regards,
Stephan

PS: if you reply to this, please don't share the alleged last digits
to the passport number.

Bug#799476: libc6: strftime should allow extended-format timezone (ISO 8601)

[Thorsten Glaser]

Package: libc6
Version: 2.31-10
Followup-For: Bug #799476
X-Debbugs-Cc: t...@mirbsd.de
Control: tags 799476 + upstream

Incidentally, I came here to report precisely this (strftime(3) and date(1)
not consistent wrt. GNU extensions). I’ve since added %-d and %:z to MirBSD
libc’s strftime(3) — whose date(1) uses that.

I’ve noticed that trying to use %:z in a locale category fails, but passing
it directly to date(1) works:

$ LC_TIME=de_DE.UTF-8 date +"$(LC_TIME=de_DE.UTF-8@iso8601 locale d_t_fmt)"
2021-04-04T21:34:31+02:00 (CEST), 2021-W13-7 (So)
$ LC_TIME=de_DE.UTF-8@iso8601 date +%c
2021-04-04T21:34:35%:z (CEST), 2021-W13-7 (So)

I thought I could get by with using "%Y-%m-%dT%H:%M:%S%z (%Z), %G-W%V-%u (%a)"
but the OP makes a good point that mixing basic and extended formats is not
permitted either.

Please forward this upstream so it’ll be implemented. Thanks!

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

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

Versions of packages libc6 depends on:
ii  libcrypt1  1:4.4.18-2
ii  libgcc-s1  10.2.1-6

Versions of packages libc6 recommends:
ii  libidn2-0   2.3.0-5
ii  libnss-nis  3.1-4
ii  libnss-nisplus  1.3-4

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.76
ii  glibc-doc  2.31-10
ii  libc-l10n  2.31-10
ii  locales2.31-10

-- debconf information:
  glibc/kernel-too-old:
  glibc/restart-services:
* glibc/upgrade: true
  glibc/disable-screensaver:
  glibc/kernel-not-supported:
* libraries/restart-without-asking: true
  glibc/restart-failed:

Bug#986371: qemu-system-x86: /proc/stat on host does not show guest cpu usage

[Thomas Scholz]

Package: qemu-system-x86
Version: 1:5.2+dfsg-9
Severity: normal

Dear Maintainer,

  * What led up to the situation?
I have two hosts, running several KVM/qemu guests. The first host runs on 
Ubuntu 20.10 and shows 
under /proc/stat in the 9th column the values for the CPU-usage of the guests.

The other host (=this host) under Debian testing does not show these values, 
rather the guest's
CPU-usage is included in the system-stat (3rd column).

  * What exactly did you do (or not do) that was effective (or
ineffective)?
I googled an searched a lot to find out, if there is some kind of configuration 
regarding this, 
or known differences because of different kernel/qemu versions.

  * What was the outcome of this action?
Unfortunately I didn’t find anything regarding this issue.

  * What outcome did you expect instead?
I would expect the guest CPU-usage being reported to the host as 'guest' time 
-> 9th value in
/proc/stat just as it does on my Ubuntu 20.10 box. 

Of course between those two boxes are lots of differences (kernel, qemu, 
libraries, etc.), but
I did not find any clue on where to start searching, nor any hint that it could 
be a configuration
issue. I suspect that it might be an issue related to the debian's version of 
qemu and/or kernel
module.


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

Kernel: Linux 5.10.0-5-amd64 (SMP w/8 CPU threads)
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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qemu-system-x86 depends on:
ii  ipxe-qemu 1.0.0+git-20190125.36a4c85-5.1
ii  libaio1   0.3.112-9
ii  libasound21.2.4-1.1
ii  libbrlapi0.8  6.3+dfsg-1
ii  libc6 2.31-10
ii  libcacard01:2.8.0-3
ii  libcapstone4  4.0.2-3
ii  libepoxy0 1.5.5-1
ii  libfdt1   1.6.0-1
ii  libgbm1   20.3.4-1
ii  libgcc-s1 10.2.1-6
ii  libglib2.0-0  2.66.8-1
ii  libgnutls30   3.7.1-1
ii  libibverbs1   33.1-1
ii  libjpeg62-turbo   1:2.0.6-4
ii  libncursesw6  6.2+20201114-2
ii  libnettle83.7-2.1
ii  libnuma1  2.0.12-1+b1
ii  libpixman-1-0 0.40.0-1
ii  libpmem1  1.10-1
ii  libpng16-16   1.6.37-3
ii  librdmacm133.1-1
ii  libsasl2-22.1.27+dfsg-2.1
ii  libseccomp2   2.5.1-1
ii  libslirp0 4.4.0-1
ii  libspice-server1  0.14.3-2.1
ii  libtinfo6 6.2+20201114-2
ii  libudev1  247.3-3
ii  liburing1 0.7-3
ii  libusb-1.0-0  2:1.0.24-2
ii  libusbredirparser10.8.0-1+b1
ii  libvdeplug2   4.0.1-2
ii  libvirglrenderer1 0.8.2-5
ii  libxendevicemodel14.14.1+11-gb0b734a8b3-1
ii  libxenevtchn1 4.14.1+11-gb0b734a8b3-1
ii  libxenforeignmemory1  4.14.1+11-gb0b734a8b3-1
ii  libxengnttab1 4.14.1+11-gb0b734a8b3-1
ii  libxenmisc4.144.14.1+11-gb0b734a8b3-1
ii  libxenstore3.04.14.1+11-gb0b734a8b3-1
ii  libxentoolcore1   4.14.1+11-gb0b734a8b3-1
ii  qemu-system-common1:5.2+dfsg-9
ii  qemu-system-data  1:5.2+dfsg-9
ii  seabios   1.14.0-2
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages qemu-system-x86 recommends:
ii  ovmf 2020.11-2
pn  qemu-system-gui  
ii  qemu-utils   1:5.2+dfsg-9

Versions of packages qemu-system-x86 suggests:
pn  qemu-block-extra
ii  qemu-system-data [sgabios]  1:5.2+dfsg-9
ii  samba   2:4.13.5+dfsg-1
pn  vde2

-- no debconf information

Bug#986382: DPL Jonathan Carter's passport number is ****909

[crazy . molly]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: 
debian-proj...@lists.debian.org,debian-v...@lists.debian.org,debian-de...@lists.debian.org


We are contributors to Debian

The contribution of every one of us makes the name Debian respectable

We can't allow a crazy woman who slept with a past project leader to hijack the 
name of the project and use it to scar volunteers.  This happened to many 
times.  It stops now.

Please stop!  Delete all fascism and defamation about any volunteer that has 
been instigated from Debian in any form whatsoever.  Delete it from the vote, 
web pages, search engines.

Please stop!  Delete all negative options from the RMS vote.  We only want 
positive options or nothing.  We will not tolerate any outcome that is negative 
for a volunteer

If the mob does not respect our request, we are making a data dump of all the 
DebConf personal data.  DPL Jonathan Carter's passport number is 909.

Privacy for everybody or privacy for nobody

Bug#871446: jemalloc: FTBFS on hurd-i386: aligned_alloc test hangs

[Faidon Liambotis]

On Sun, Apr 04, 2021 at 02:26:16AM +0200, Samuel Thibault wrote:
> So basically libpthread is trying to initialize itself, calls malloc,
> which initializes jemalloc, which calls pthread_self, which is not happy
> that libpthread is not initialized yet, thus calls assert, which tries
> to malloc as well, which tries (again!) to initialize jemalloc, and
> gets stuck on mutex_lock. And since this is all happening at very early
> initialization of libc, interaction with ps etc. is not possible yet.
> 
> [...]
>
> I'm wondering how this kind of bootstrap issue is solved on Linux? The
> _dl_allocate_tls code is exactly the same.

Thanks for looking into this! I'm really out of my depth here. Don't
assume that the platform settings in configure.ac are the right ones
either -- I just guesstimated them, and may just as well be something
there.

I'd suggest reaching out to upstream directly on either a GitHub issue,
or their Gitter channel (they're responsive in my experience). Note that
I haven't sent them debian/patches/hurd.patch as it hasn't been
functional so far, so it may be worth prefacing your communication with
the configure.ac settings that we've chosen.

If you succeed into figuring out the root cause and making jemalloc
build, happy to prepare a PR to upstream this.

Regards,
Faidon

Bug#986381: polymake: VISUAL with threejs fails

[Joachim Zobel]

Package: polymake
Version: 4.3-3
Severity: normal

Dear Maintainer,

Doing cube(3)->VISUAL; starts the default browser (Gnome Web), which only
displays the three bars. The bars don't open a menu on click and no graphics
are displayed.

F12 displays a warning

"THREE.OrbitControls: As part of the transition to ES6 Modules, the files in
'examples/js' were deprecated in May 2020 (r117) and will be deleted in
December 2020 (r124). You can find more information about developing using ES6
Modules in https://threejs.org/docs/index.html#manual/en/introduction/Import-
via-modules."

and 2 times an error

"ReferenceError: Can't find variable: THREE"

Sincerely,
Joachim

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

Kernel: Linux 5.10.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
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 polymake depends on:
ii  libbliss2   0.73-5
ii  libc6   2.31-10
ii  libcdd0d094l-2
ii  libeantic0  0.1.8+ds-1
ii  libflint-2.6.3  2.6.3-3
ii  libgcc-s1   10.2.1-6
ii  libgmp102:6.2.1+dfsg-1
ii  libgomp110.2.1-6
ii  libmpfr64.1.0-3
ii  libnormaliz33.8.9+ds-0.1
ii  libpolymake-dev-common  4.3-3
ii  libppl141:1.2-8.1
ii  libstdc++6  10.2.1-6
ii  ninja-build 1.10.1-1
ii  polymake-common 4.3-3

Versions of packages polymake recommends:
ii  chromium   89.0.4389.90-1
ii  gfan   0.6.2-4
ii  graphviz   2.42.2-4+b2
ii  xdg-utils  1.1.3-4

Versions of packages polymake suggests:
pn  povray   
ii  texlive-latex-extra  2020.20210202-3
ii  texlive-pictures 2020.20210202-3

Bug#986299: closed by Debian FTP Masters (reply to Mo Zhou ) (Bug#986299: fixed in zfs-linux 2.0.3-5)

[наб]

Hi!

It appears that my reading of the manpage was wrong (and you didn't
check the built package) ‒ dh_installdocs -A only installs the *named*
files for all packages, so zfsutils-linux still doesn't have the README;
turning the
  dh_installdocs -A
into
  dh_installdocs -A debian/README.Debian
should work (but please verify this before uploading!).

Best,
наб


signature.asc
Description: PGP signature

Bug#986377: [Pkg-phototools-devel] Bug#986377: segfault on startup

[David Bremner]

Antoine Beaupre  writes:

> Package: darktable
> Version: 3.2.1-3~bpo10+1
> Severity: important

probably someone (TM) should upgrade the backport to 3.4.1 before
spending much more effort on this.

d

Bug#974616: nomacs: "charset=Ascii" appears before the comment of the image

[Antoine Beaupré]

On 2020-12-14 23:45:06, Vincent Lefevre wrote:
> Control: retitle -1 nomacs uses internal libexiv2 functions to get the user 
> comment
> Control: severity -1 serious
> Control: tags -1 - patch
>
> On 2020-12-12 21:59:38 +0100, Vincent Lefevre wrote:
>> I'm attaching the patch I've written. There was already a function
>> that removes substrings of the form 'charset="ASCII"' case
>> insensitively. So I do the same thing with 'charset=ASCII'
>> (i.e. without the double-quotes) and 'charset=Unicode', which
>> appears when the string has non-ASCII characters.
>> 
>> Note that this function is a hack: it will remove real occurrences
>> of such strings, not just those added by libexiv2. However, there
>> is very little probability that such strings really appear in the
>> comment. And one cannot do much better to fix the issue.
>
> This is just a workaround that seems to work with the current
> libexiv2 version, but according to the upstream libexiv2 maintainer,
> nomacs uses some internal libexiv2 function, which means that an
> update of libexiv2 can break it at any time, potentially introducing
> security issues.
>
> Note that a change of behavior could have already been seen with the
> upgrade of libexiv2-27 to 0.27.3 with the appearance of spurious data
> before the comment.
>
> The correct way to get the comment with the public API is
>
>   std::string comment = Exiv2::CommentValue(value().toString()).comment());
>
> Note: The upstream nomacs version comes with a bundled libexiv2,
> meaning that this may not be an issue to use internal libexiv2
> features. Debian chose to use the shared library, thus it needs
> to replace these internals by calls to the public API.

Is this fixed upstream, in the latest 3.16 release?

I mean I understand that it *still* bundles exiv2 and friends:

https://github.com/nomacs/nomacs/tree/master/3rd-party

... but maybe their usage of the library improved?

There is #974617 for upgrading to 3.16...

a.

-- 
By now the computer has moved out of the den and into the rest of your
life. It will consume all of your spare time, and even your vacation,
if you let it. It will empty your wallet and tie up your thoughts. It
will drive away your family. Your friends will start to think of you
as a bore. And what for?
   - The True Computerist by Tom Pittman

Bug#986354: Re[2]: Bug#986354: hardening-runtime breaks upowerd which affects default installation

[Andrew Savchenko]

Hello Yves-Alexis,

Sunday, April 4, 2021, 6:09:22 PM, you wrote:

> Hi, could you detail which permissions and from where? I'm aware of the issue
> with user namespaces but not from the permissions.

Indeed, user namespaces were to blame.

> There's already a small warning in the package long description, do you have
> something specific in mind? Could you propose a wording?

```
WARNING!

This package sets restrictive permissions on a number of directories.

While this is beneficial to the system security, it might lead to situation
where an application is unable to access a certain path.

Please use `reportbug` shall you encounter any.
``` 


-- 
Regards,
A

Bug#986358: Re[2]: Bug#986358: hardening-runtime: Restrictions on /etc/pam.d/ break X screensavers

[Andrew Savchenko]

Hello Yves-Alexis,

Sunday, April 4, 2021, 7:35:46 PM, you wrote:

> statoverride in hardening-runtime were added by Topi Miettinen so I'm adding
> him in the loop for comments.

For the screensavers specifically, I have narrowed it down to /etc/pam.d only.
chmod'ing it to the default 0755 fixes the issue.

There might be more dragons though as this is somewhat similar to openSUSE:
https://github.com/openSUSE/permissions/blob/master/profiles/permissions.paranoid


-- 
Regards,
A

Bug#771117: etckeeper: stores passwd- backup files

[Thorsten Glaser]

Package: etckeeper
Version: 1.18.10-1
Followup-For: Bug #771117

etckeeper should add *~, *-, *.dpkg* and *.ucf* to its
default ignore list (to avoid this and similar issues).

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

Kernel: Linux 4.19.0-14-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages etckeeper depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  git1:2.20.1-2+deb10u3
ii  python 2.7.16-1

Versions of packages etckeeper recommends:
ii  cron [cron-daemon]  3.0pl1-134+deb10u1

Versions of packages etckeeper suggests:
ii  sudo  1.8.27-1+deb10u3

-- debconf information:
  etckeeper/purge: true

Bug#986377: Acknowledgement (segfault on startup)

[Antoine Beaupré]

On 2021-04-04 12:56:54, Antoine Beaupré wrote:
> Extra information: moving .config/darktable out of the way works around
> the problem. Moving the .config/darktable/*.db files back in triggers
> the bug again, so presumably something is broken with the database. :(

And I reran that upgrade (by restoring the -pre-3.2.1 files) and it
crashed again, with those extra messages on top:

anarcat@angela:darktable(main)$ darktable
[lighttable_init_presets] updating 'metadata' preset 'anarcat-CC-BY-SA' from 
version 1 to version 3
[lighttable_init_presets] updating 'metadata' preset 'nouveau pré-réglage' from 
version 1 to version 3
[lighttable_init_presets] updating 'export' preset 'private-sigal' from version 
6 to version 7
[lighttable_init_presets] updating 'export' preset 'marcos-paste' from version 
6 to version 7
[lighttable_init_presets] updating 'export' preset 'sigal-local' from version 6 
to version 7
[lighttable_init_presets] updating 'export' preset 'calendes-local' from 
version 6 to version 7
[lighttable_init_presets] updating 'export' preset 'calendes-print' from 
version 6 to version 7
[lighttable_init_presets] updating 'export' preset 'quick-render-1080p' from 
version 6 to version 7
[lighttable_init_presets] updating 'export' preset 'calendes-letter' from 
version 6 to version 7
[lighttable_init_presets] updating 'collect' preset 'calendes' from version 1 
to version 3
[lighttable_init_presets] updating 'collect' preset '2018' from version 1 to 
version 3


-- 
The good news about computers is that they do what you tell them to
do. The bad news is that they do what you tell them to do.
- Ted Nelson

Bug#986332: lsattr on certiain files in /dev results in "stack smashing detected"

[Bernhard Übelacker]

Dear Maintainer,
tried to locate the exact smashing.
It looks like the ioctl(EXT2_IOC_GETFLAGS) takes an int* parameter,
but writes 8 bytes instead of just sizeof(int) to the given address.

Kind regards,
Bernhard


Old value = (void *) 0xf759b62c03711000
New value = (void *) 0xf759b62c
0x77ec0cc7 in ioctl () at ../sysdeps/unix/syscall-template.S:120
120 ../sysdeps/unix/syscall-template.S: Datei oder Verzeichnis nicht 
gefunden.
1: x/i $pc
=> 0x77ec0cc7 :cmp$0xf001,%rax
(gdb) bt
#0  0x77ec0cc7 in ioctl () at ../sysdeps/unix/syscall-template.S:120
#1  0x77fbcb17 in fgetflags (name=name@entry=0x7fffe83f 
"/dev/dri/card0", flags=flags@entry=0x7fffe3e0) at 
../../../../lib/e2p/fgetflags.c:90
#2  0x54d5 in list_attributes (name=name@entry=0x7fffe83f 
"/dev/dri/card0") at ../../../misc/lsattr.c:85
#3  0x56c9 in lsattr_args (name=0x7fffe83f 
"/dev/dri/card0") at ../../../misc/lsattr.c:134
#4  0x5369 in main (argc=, argv=) 
at ../../../misc/lsattr.c:221

https://sources.debian.org/src/e2fsprogs/1.46.2-1/lib/e2p/fgetflags.c/#L90
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/tree/lib/e2p/fgetflags.c#n90

# single-use Bullseye/testing amd64 qemu VM 2021-04-04

echo "set enable-bracketed-paste off" >> /etc/inputrc; bash

apt update

# to speedup testing
mv /etc/manpath.config /etc/manpath.config.renamed
apt install libeatmydata1
export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libeatmydata.so

apt dist-upgrade
apt install systemd-coredump gdb valgrind \
e2fsprogs-dbgsym libext2fs2-dbgsym
.










benutzer@debian:~$ lsattr /dev/dri/card0
*** stack smashing detected ***: terminated
Abgebrochen (Speicherabzug geschrieben)

root@debian:~# coredumpctl list
TIMEPID   UID   GID SIG COREFILE  EXE
Sun 2021-04-04 14:22:59 CEST   1921  1000  1000   6 present   /usr/bin/lsattr

root@debian:~# coredumpctl gdb 1921
   PID: 1921 (lsattr)
   UID: 1000 (benutzer)
   GID: 1000 (benutzer)
Signal: 6 (ABRT)
 Timestamp: Sun 2021-04-04 14:22:59 CEST (50s ago)
  Command Line: lsattr /dev/dri/card0
Executable: /usr/bin/lsattr
 Control Group: /user.slice/user-1000.slice/session-3.scope
  Unit: session-3.scope
 Slice: user-1000.slice
   Session: 3
 Owner UID: 1000 (benutzer)
   Boot ID: de580d9e15564f17b195ec068c7129dc
Machine ID: 33f18f39d2a9438eb75b0ed52848afcd
  Hostname: debian
   Storage: 
/var/lib/systemd/coredump/core.lsattr.1000.de580d9e15564f17b195ec068c7129dc.1921.161753897900.zst
   Message: Process 1921 (lsattr) of user 1000 dumped core.

Stack trace of thread 1921:
#0  0x7f7ea4286ce1 __GI_raise (libc.so.6 + 0x3bce1)
#1  0x7f7ea4270537 __GI_abort (libc.so.6 + 0x25537)
#2  0x7f7ea42c9768 __libc_message (libc.so.6 + 0x7e768)
#3  0x7f7ea4358652 __GI___fortify_fail (libc.so.6 + 
0x10d652)
#4  0x7f7ea4358630 __stack_chk_fail (libc.so.6 + 0x10d630)
#5  0x7f7ea443bbd6 fgetflags (libe2p.so.2 + 0x3bd6)
#6  0x557d54ea24d5 n/a (lsattr + 0x14d5)
#7  0x557d54ea26c9 n/a (lsattr + 0x16c9)
#8  0x557d54ea2369 n/a (lsattr + 0x1369)
#9  0x7f7ea4271d0a __libc_start_main (libc.so.6 + 0x26d0a)
#10 0x557d54ea23ea n/a (lsattr + 0x13ea)


...
Core was generated by `lsattr /dev/dri/card0'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht 
gefunden.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x7f7ea4270537 in __GI_abort () at abort.c:79
#2  0x7f7ea42c9768 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x7f7ea43d7c24 "*** %s ***: terminated\n") at 
../sysdeps/posix/libc_fatal.c:155
#3  0x7f7ea4358652 in __GI___fortify_fail (msg=msg@entry=0x7f7ea43d7c0c 
"stack smashing detected") at fortify_fail.c:26
#4  0x7f7ea4358630 in __stack_chk_fail () at stack_chk_fail.c:24
#5  0x7f7ea443bbd6 in fgetflags () from /lib/x86_64-linux-gnu/libe2p.so.2
#6  0x557d54ea24d5 in ?? ()
#7  0x557d54ea26c9 in ?? ()
#8  0x557d54ea2369 in ?? ()
#9  0x7f7ea4271d0a in __libc_start_main (main=0x557d54ea21d0, argc=2, 
argv=0x7ffda1e5c978, init=, fini=, 
rtld_fini=, stack_end=0x7ffda1e5c968) at ../csu/libc-start.c:308
#10 0x557d54ea23ea in ?? ()

(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x7f7ea4270537 in __GI_abort () at abort.c:79
#2  0x7f7ea42c9768 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x7f7ea43d7c24 "*** %s ***: terminated\n") at 
../

Bug#986377: Acknowledgement (segfault on startup)

[Antoine Beaupré]

Extra information: moving .config/darktable out of the way works around
the problem. Moving the .config/darktable/*.db files back in triggers
the bug again, so presumably something is broken with the database. :(

Bug#986378: linux-image-5.10.0-5-amd64: please enable CONFIG_TLS

[Steinar H. Gunderson]

Package: src:linux
Version: 5.10.26-1
Severity: wishlist

Hi,

Please enable CONFIG_TLS=y (kTLS), so that we can get kernel-accelerated TLS
for compatible software (e.g. cubemap). It's been supported since 4.17,
so should be pretty mature by now.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#986377: segfault on startup

[Antoine Beaupre]

Package: darktable
Version: 3.2.1-3~bpo10+1
Severity: important

I haven't started Darktable in months! Finally, I find the time to
look at it again, and it (understandably) prompts me to upgrade the
database (which i do), and then just disappeared. I couldn't quite
figure out what happened, so I start it on the commandline, and it
crashes on __GI___waitpid(), somewhere inside legacy_params()...

Darktable is just unusable here.

Here's the full backtrace:

anarcat@angela:~(main)$ darktable
[New LWP 3398]
[New LWP 3399]
[New LWP 3400]
[New LWP 3401]
[New LWP 3402]
[New LWP 3403]
[New LWP 3404]
[New LWP 3405]
[New LWP 3407]
[New LWP 3411]
[New LWP 3412]
[New LWP 3413]
[New LWP 3414]
[New LWP 3415]
[New LWP 3417]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7ff619b8446a in __GI___waitpid (pid=3425, stat_loc=0x0, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:30
30  ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
warning: Currently logging to /tmp/darktable_bt_8XV500.txt.  Turn the logging 
off and on to make the new setting effective.
#0  0x7ff619b8446a in __GI___waitpid (pid=3425, stat_loc=0x0, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:30
#1  0x7ff619df8b60 in  () at 
/usr/bin/../lib/x86_64-linux-gnu/darktable/libdarktable.so
#2  0x7ff619af5840 in  () at 
/lib/x86_64-linux-gnu/libc.so.6
#3  0x7ff5fc19a0cc in legacy_params () at 
/usr/lib/x86_64-linux-gnu/darktable/plugins/lighttable/libcollect.so
#4  0x7ff619f1d6e9 in dt_lib_init_presets () at 
/usr/bin/../lib/x86_64-linux-gnu/darktable/libdarktable.so
#5  0x7ff619f1dd29 in  () at 
/usr/bin/../lib/x86_64-linux-gnu/darktable/libdarktable.so
#6  0x7ff619dda1a7 in dt_module_load_modules () at 
/usr/bin/../lib/x86_64-linux-gnu/darktable/libdarktable.so
#7  0x7ff619f1e731 in dt_lib_init () at 
/usr/bin/../lib/x86_64-linux-gnu/darktable/libdarktable.so
#8  0x7ff619d69952 in dt_init () at 
/usr/bin/../lib/x86_64-linux-gnu/darktable/libdarktable.so
#9  0x562256ed0086 in  ()
#10 0x7ff619ae209b in __libc_start_main (main=0x562256ed0070, argc=1, 
argv=0x7fffd1b164a8, init=, fini=, 
rtld_fini=, stack_end=0x7fffd1b16498) at ../csu/libc-start.c:308
#11 0x562256ed00da in  ()

=

  Id   Target Id   Frame 
* 1Thread 0x7ff6114efe80 (LWP 3397) "darktable"0x7ff619b8446a in 
__GI___waitpid (pid=3425, stat_loc=0x0, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:30
  2Thread 0x7ff611213700 (LWP 3398) "gmain"0x7ff619bac819 in 
__GI___poll (fds=0x562258c65be0, nfds=1, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  3Thread 0x7ff6109c2700 (LWP 3399) "pool" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7ff60bfff700 (LWP 3400) "gdbus"0x7ff619bac819 in 
__GI___poll (fds=0x562258c39070, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  5Thread 0x7ff60b7fe700 (LWP 3401) "worker 0" futex_wait_cancelable 
(private=0, expected=0, futex_word=0x562258c61900) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
  6Thread 0x7ff60affd700 (LWP 3402) "worker 1" futex_wait_cancelable 
(private=0, expected=0, futex_word=0x562258c61900) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
  7Thread 0x7ff60a7fc700 (LWP 3403) "worker 2" futex_wait_cancelable 
(private=0, expected=0, futex_word=0x562258c61900) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
  8Thread 0x7ff609ffb700 (LWP 3404) "worker 3" futex_wait_cancelable 
(private=0, expected=0, futex_word=0x562258c61900) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
  9Thread 0x7ff6097fa700 (LWP 3405) "worker 4" futex_wait_cancelable 
(private=0, expected=0, futex_word=0x562258c61900) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
  10   Thread 0x7ff608ff9700 (LWP 3407) "worker 5" futex_wait_cancelable 
(private=0, expected=0, futex_word=0x562258c61900) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
  11   Thread 0x7ff5f700 (LWP 3411) "worker 6" futex_wait_cancelable 
(private=0, expected=0, futex_word=0x562258c61900) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
  12   Thread 0x7ff5ff7fe700 (LWP 3412) "worker 7" futex_wait_cancelable 
(private=0, expected=0, futex_word=0x562258c61900) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
  13   Thread 0x7ff5feffd700 (LWP 3413) "kicker"   0x7ff619b84720 in 
__GI___nanosleep (requested_time=0x7ff5fefee760, remaining=0x7ff5fefee760) at 
../sysdeps/unix/sysv/linux/nanosleep.c:28
  14   Thread 0x7ff5fe7fc700 (LWP 3414) "worker res 0" futex_wait_cancelable 
(private=0, expected=0, futex_word=0x562258c61900) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
  15   Thread 0x7ff5fdffb700 (LWP 3415) "worker res 1" futex_wait_cancelable 
(private=0, expected=0, futex_word=0x562258c61900) at 
../sysdeps/unix/sysv/linux

Bug#986375: elfutils: elutils 0.183-6 cannot be installed because libdebuginfod-common 0.183-6 is not available

[Eric Valette]

Package: elfutils
Version: 0.183-6
Severity: important

apt-get -t experimental install elfutils libdebuginfod1 libdebuginfod-common
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libdebuginfod-common is already the newest version (0.183-4).
libdebuginfod-common set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libdebuginfod1 : Depends: libdebuginfod-common (= 0.183-6) but 0.183-4 is to 
be installed



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

Kernel: Linux 5.10.27 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages elfutils depends on:
ii  libasm1 0.183-4
ii  libc6   2.31-11
ii  libdw1  0.183-4
ii  libelf1 0.183-4
ii  libstdc++6  10.2.1-6

elfutils recommends no packages.

elfutils suggests no packages.

-- no debconf information

Bug#986376: Please Update HASH values for vcrun2019

[Bernhard]

Package: winetricks
Version: 0.0+20210206-1

Dear maintainer,

The Hash-values for vcrun2019 were changed.
Installation of vcrun2019 is no more possible.

The Hash-values were fixed upstream.
Please have a look at Github:

https://github.com/Winetricks/winetricks/commit/f503916c7df23d128c534248d91abdfbf331b93d

Please backport this change in Debian package.
And, if possible, please backport this change also in Debian 11.

Thank you in advance.

Best regards
Bernhard



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

Bug#986373: dpkg: please preserve unchanged content on upgrades

[Aaron M. Ucko]

Package: dpkg
Version: 1.20.7.1
Severity: wishlist

When upgrading a package, it is by no means unheard of for many of its
files to preserve their contents (though not necessarily their
metadata).  This phenomenon is particularly common for minor upgrades,
as with stable updates or many upgrades within development suites
(testing, unstable, and experimental).  In this era of reproducible
builds, it commonly even extends to compiled binaries such as shared
libraries, whose upgrades currently always trip needrestart.

It would be great if dpkg could handle this scenario with less formal
disruption.  At minimum, instead of unconditionally renaming .dpkg-new
files into place, perhaps it could compare them with the files they
are to replace (after confirming that they are in fact regular files)
and in the case of an exact match simply resync metadata and remove
corresponding .dpkg-new files.

A more elaborate approach could reduce peak disk usage in many cases:
immediately after creating a .dpkg-new file, compare it with the file
it is to replace, and in the case of an exact match discard the
.dpkg-new file in favor of an empty file with an extension of (say)
.dpkg-newmeta and the desired permissions and ownership.  The rename
phase would then check for such .dpkg-newmeta files and proceed
accordingly.

Thanks in advance for considering this suggestion!

-- Package-specific info:

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

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

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.8-4
ii  libc62.31-11
ii  liblzma5 5.2.5-2
ii  libselinux1  3.1-3
ii  tar  1.34+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-2

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt2.2.2
pn  debsig-verify  

-- no debconf information

Bug#986372: aptitude: Hide implicit dependencies/provides in `show`

[Julian Andres Klode]

Package: aptitude
Severity: minor
X-Debbugs-Cc: j...@debian.org

aptitude renders implicit Provides, as can be seen by versioned
kernel packages getting Provides: $kernel (= $binary:Version)
or rustc having a Provides: rustc:any (= $binary:Version), when
shown by aptitude show.

Please hide them by looking calling IsMultiArchImplicit() on the
PrvIterator or DepIterator. I think the latter also has an IsImplicit()
that handles more cases and might be better suited.


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

Bug#986370: espeakup: Copy over the speakup parameters into the installed system

[Samuel Thibault]

Package: espeakup
Version: 1:0.80-21
Severity: normal

During installation, the user can tune the behavior of speakup to
his/her liking. But at reboot into the installed system, the
configuration is lost. Notably, the volume setting is lost, which may
make the speech significantly low (see Bug#985666). It would be useful
to copy over the speakup parameters, so that at reboot into the
installed system the behavior is the same as during installation.

Samuel

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

Kernel: Linux 5.11.0 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

-- 
Samuel
 bon comment on fait de l'investigation pour savoir qui est le vilain ?
 on débranche le routeur et on regarde qui s'affole
 -+- #ens-mim administre -+-

Bug#986358: hardening-runtime: Restrictions on /etc/pam.d/ break X screensavers

[Andrew Savchenko]

Package: hardening-runtime
Version: 2
Severity: important
X-Debbugs-Cc: and...@savchenko.net

Dear Maintainer,

Restricting permissions on /etc/pam.d to 0700 while the folder is owned
by `root:root` leads to xscreensaver, mate-screensaver and others being
unable to authenticate a user.

Perhaps worth adding a warning or making this optional?


Thank you.

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

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

Bug#986369: lintian.d.o: out-of-date reports

[Samuel Thibault]

Package: lintian
Version: 2.104.0
Severity: normal

Hello,

It seems the lintian.d.o pages are not up to date, for instance:
https://lintian.debian.org/sources/orca.html
version 3.38.0-1 was replaced by version 3.38.0-2 since novembre 1st.
As a consequence, the lintian columns of the QA page is little useful.

With best regards,
Samuel

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

Kernel: Linux 5.11.0 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 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.39
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  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-2

lintian recommends no packages.

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

-- no debconf information

-- 
Samuel
 je déteste import
 parce que lorsque tu fais du python et que tu oublies le #!/bin/env python 
et que tu mets le fichier exécutable
 import est exécuté
 -+- #ens-mim - pourquoi mon script python change le curseur de la souris ?! -+-

Bug#986368: mutt: Add support for client certificate without AUTH in smtp

[Adam Majer]

Package: mutt
Version: 2.0.5-4
Severity: minor
Tags: patch

Hi,

Current implementation of mutt always seems to ask for SMTP username
even if one is not set in the config (smtp_url) and AUTH is not
an allowed option of submit server. This then results in an email
send failure

  SMTP server does not support authentication

The patch that fixes this issue is at and also attached.

https://gitlab.com/muttmua/mutt/-/commit/191b0513b43d5e603f99292faa5f8ebcc1be3823.patch

I've tested this patch in the tagged version and the problem is solved.
Please consider adding it to mutt for next upload.

Thanks,
- Adam


>From 191b0513b43d5e603f99292faa5f8ebcc1be3823 Mon Sep 17 00:00:00 2001
From: Kevin McCarthy 
Date: Fri, 5 Mar 2021 18:52:48 -0800
Subject: [PATCH] Fix $ssl_client_cert usage with SMTP.

The ssl and gnutls client-cert setup code was calling
mutt_account_getuser().  This caused two problems.  First, it's not
necessarily the case that there will be a username.  Second,
populating the user would cause smtp_open() to check for AUTH
capabilities and call smtp_auth - even if the user is already
authenticated by the cert.  The server won't advertize AUTH if they
already authenticated, causing a connection abort.

Remove prompt for mutt_account_getuser() in the ssl and gnutls client
certificate connection code.  The SASL code has callbacks, so I don't
understand why it would need this.  Let's take it out and see if
anyone screams 8-P.  If necessary, we can add a mutt_account_getuser()
call to the very beginning of imap_auth_sasl().

Revamp the openssl ssl_passwd_cb() prompt.  From the man pages, it
appears to be used for the cert decryption.  There's no need to call
mutt_account_getuser() and use the generic mutt_account_getpass() just
to read a password in.  Instead create a callback function version to
customize the prompt for a client cert with just the host.

Change the SMTP authentication test to check if the AUTH capabilities
are set, instead of if the user field is set before calling
smtp_auth().
---
 account.c | 25 -
 account.h |  2 ++
 mutt_ssl.c| 32 +++-
 mutt_ssl_gnutls.c | 20 ++--
 smtp.c| 11 +--
 5 files changed, 68 insertions(+), 22 deletions(-)

diff --git a/account.c b/account.c
index 28c0749b..09bf24d3 100644
--- a/account.c
+++ b/account.c
@@ -198,8 +198,19 @@ int mutt_account_getlogin (ACCOUNT* account)
   return 0;
 }
 
-/* mutt_account_getpass: fetch password into ACCOUNT, if necessary */
-int mutt_account_getpass (ACCOUNT* account)
+static void getpass_prompt (char *prompt, size_t prompt_size, ACCOUNT *account)
+{
+  /* L10N:
+ Prompt for an account password when connecting.
+ %s@%s is user@host
+  */
+  snprintf (prompt, prompt_size, _("Password for %s@%s: "),
+account->flags & MUTT_ACCT_LOGIN ? account->login : account->user,
+account->host);
+}
+
+int _mutt_account_getpass (ACCOUNT* account,
+   void (*prompt_func) (char *, size_t, ACCOUNT *))
 {
   char prompt[SHORT_STRING];
 
@@ -221,9 +232,7 @@ int mutt_account_getpass (ACCOUNT* account)
 return -1;
   else
   {
-snprintf (prompt, sizeof (prompt), _("Password for %s@%s: "),
-  account->flags & MUTT_ACCT_LOGIN ? account->login : account->user,
-  account->host);
+prompt_func (prompt, sizeof(prompt), account);
 account->pass[0] = '\0';
 if (mutt_get_password (prompt, account->pass, sizeof (account->pass)))
   return -1;
@@ -234,6 +243,12 @@ int mutt_account_getpass (ACCOUNT* account)
   return 0;
 }
 
+/* mutt_account_getpass: fetch password into ACCOUNT, if necessary */
+int mutt_account_getpass (ACCOUNT *account)
+{
+  return _mutt_account_getpass (account, getpass_prompt);
+}
+
 void mutt_account_unsetpass (ACCOUNT* account)
 {
   account->flags &= ~MUTT_ACCT_PASS;
diff --git a/account.h b/account.h
index 2eccb7f4..9f485cfd 100644
--- a/account.h
+++ b/account.h
@@ -55,6 +55,8 @@ int mutt_account_fromurl (ACCOUNT* account, ciss_url_t* url);
 void mutt_account_tourl (ACCOUNT* account, ciss_url_t* url);
 int mutt_account_getuser (ACCOUNT* account);
 int mutt_account_getlogin (ACCOUNT* account);
+int _mutt_account_getpass (ACCOUNT* account,
+   void (*prompt_func) (char *, size_t, ACCOUNT *));
 int mutt_account_getpass (ACCOUNT* account);
 void mutt_account_unsetpass (ACCOUNT* account);
 int mutt_account_getoauthbearer (ACCOUNT* account, BUFFER *authbearer, int xoauth2);
diff --git a/mutt_ssl.c b/mutt_ssl.c
index dd76cded..91507948 100644
--- a/mutt_ssl.c
+++ b/mutt_ssl.c
@@ -1399,22 +1399,44 @@ static void ssl_get_client_cert(sslsockdata *ssldata, CONNECTION *conn)
 SSL_CTX_use_certificate_file(ssldata->ctx, SslClientCert, SSL_FILETYPE_PEM);
 SSL_CTX_use_PrivateKey_file(ssldata->ctx, SslClientCert, SSL_FILETYPE_PEM);
 
+#if 0
+/* This interferes with SMTP client-cert authentication that do

Bug#986367: unblock: espeakup/1:0.80-20

[Samuel Thibault]

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

Hello,

I have uploaded the attach changes of espeakup to unstable, proposed for
inclusion for bullseye.

The complete discussion is on
https://lists.debian.org/debian-accessibility/2021/03/msg00019.html
which started with Bug#985666, currently assigned to pulseaudio.

[ Reason ]
During installation with speech synthesis enabled, users have the
capslock-1 / 2 keyboard shortcuts to change the volume of the sound card
used for synthesis. In the debian-installer context, these shortcuts not
only make espeakup change the synthesis volume for itself, but also the
global alsa mixer, to be sure to allow for the maximum volume that the
hardware can achieve. This level of control is however disabled in the
installed system, to avoid espeakup overriding users' fine-tuning in
amixer / alsamixer.

A user however reported that he didn't have sound in the installed
system, and we found out that this was because the sound level was too
low for him to hear, and the speakup shortcuts where not enough to get
it audible, precisely because in the installed system espeakup does not
change the global volume, which was too low.

The base problem is that the alsa-utils package sets volumes in the
installed system by default to 80%, which is considered not too high to
avoid breaking the user's ears, but apparently depending on the hardware
it can be too low for the user to be able to use the computer with a
speech synthesis and to even be able to raise the volume to make it
usable.

The proposed changes thus make espeakup running inside the installer
replicate the mixer settings into the installed system, so that the
volume levels that were reached through espeakup inside the installer
are pre-set for the reboot into the installed system to have them just
like during installation.

[ Impact ]
Without the change, depending on some hardware, users may see their
first reboot into the installed system with an inaudible speech
synthesis, making the installed system unusable.

[ Tests ]
I tested it by hand, and the user who reported the issue also tested it.

[ Risks ]
The code is basically 4 lines, and they are essentially either harmless
or their failing would be just ignored.

[ 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 espeakup/1:0.80-20

Thanks!
Samuel
diff -Nru espeakup-0.80/debian/changelog espeakup-0.80/debian/changelog
--- espeakup-0.80/debian/changelog  2020-11-09 20:39:46.0 +0100
+++ espeakup-0.80/debian/changelog  2021-04-04 14:33:26.0 +0200
@@ -1,3 +1,10 @@
+espeakup (1:0.80-20) unstable; urgency=medium
+
+  * espeakup-udeb.finish-install: Carry over the alsa mixer levels into the
+installed system.
+
+ -- Samuel Thibault   Sun, 04 Apr 2021 14:33:26 +0200
+
 espeakup (1:0.80-19) unstable; urgency=medium
 
   * patches/range: Really enable patch.
diff -Nru espeakup-0.80/debian/espeakup-udeb.finish-install 
espeakup-0.80/debian/espeakup-udeb.finish-install
--- espeakup-0.80/debian/espeakup-udeb.finish-install   2020-04-29 
02:48:49.0 +0200
+++ espeakup-0.80/debian/espeakup-udeb.finish-install   2021-04-04 
14:33:26.0 +0200
@@ -10,6 +10,13 @@
 
 apt-install espeakup alsa-utils || true
 
+mkdir -p /var/lock
+mkdir -p /var/lib/alsa
+if alsactl store
+then
+   cp /var/lib/alsa/asound.state /target/var/lib/alsa/ || true
+fi
+
 cp /usr/share/espeakup-udeb/espeakup.default /target/etc/default/espeakup
 sed -i -e "s/^VOICE=.*/VOICE=$VOICE/" /target/etc/default/espeakup
 [ -z "$ALSA_CARD" ] || sed -i -e "s/^# ALSA_CARD=.*/ALSA_CARD=\"$ALSA_CARD\"/" 
/target/etc/default/espeakup

Bug#986365: gnome-packagekit: gpk-update-viewer shows a critical error and closes immediately

[Amr Ibrahim]

Package: gnome-packagekit
Version: 3.32.0-2
Severity: important
X-Debbugs-Cc: amribrahim1...@hotmail.com

Dear Maintainer,

gpk-update-viewer shows a critical error and closes immediately. It renders the 
application unusable.

Run gpk-update-viewer in a terminal:

$ gpk-update-viewer

(gpk-update-viewer:11610): Gtk-CRITICAL **: 14:48:44.318: gtk_widget_hide: 
assertion 'GTK_IS_WIDGET (widget)' failed



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

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

Versions of packages gnome-packagekit depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-2
ii  gnome-packagekit-data3.32.0-2
ii  libc62.31-11
ii  libglib2.0-0 2.66.8-1
ii  libgtk-3-0   3.24.24-3
ii  libpackagekit-glib2-18   1.2.2-2
ii  libpolkit-gobject-1-00.105-30
ii  packagekit   1.2.2-2

Versions of packages gnome-packagekit recommends:
ii  software-properties-gtk  0.96.20.2-2.1

gnome-packagekit suggests no packages.

-- no debconf information

Bug#986366: unblock: ruby-kramdown/2.3.0-5

[Antonio Terceiro]

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

Please unblock package ruby-kramdown

[ Reason ]
Fixes a CVE and RC bug #985569

[ Tests ]
all autopkgtests of reverse dependencies passed.

[ Risks ]
The change should not cause regressions on non-malicious code.

[ 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 ruby-kramdown/2.3.0-5
commit b80244870c477d90090305f569eea39f7bd2b3f5
Author: Antonio Terceiro 
Date:   Sat Apr 3 10:40:54 2021 -0300

Add upstream patch to fix arbitrary code execution vulnerability

This is CVE-2021-28834

Closes: #985569

diff --git a/debian/changelog b/debian/changelog
index 088c244..012d553 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+ruby-kramdown (2.3.0-5) unstable; urgency=medium
+
+  * Team upload.
+  * Add upstream patch to fix arbitrary code execution vulnerability
+[CVE-2021-28834] (Closes: #985569)
+
+ -- Antonio Terceiro   Sat, 03 Apr 2021 10:39:28 -0300
+
 ruby-kramdown (2.3.0-4) unstable; urgency=medium
 
   * Recommend ruby-rouge, for out-of-the-box syntax highlighting
diff --git a/debian/patches/0002-Restrict-Rouge-formatters-to-Rouge-Formatters-namesp.patch b/debian/patches/0002-Restrict-Rouge-formatters-to-Rouge-Formatters-namesp.patch
new file mode 100644
index 000..68457a6
--- /dev/null
+++ b/debian/patches/0002-Restrict-Rouge-formatters-to-Rouge-Formatters-namesp.patch
@@ -0,0 +1,69 @@
+From: Stan Hu 
+Date: Sun, 14 Mar 2021 11:21:00 -0700
+Subject: Restrict Rouge formatters to Rouge::Formatters namespace
+
+ff0218a added support for specifying custom Rouge formatters with the
+constraint that the formatter be in theRouge::Formatters namespace, but
+it did not actually enforce this constraint. For example, this is valid:
+
+```ruby
+Rouge::Formatters.const_get('CSV')
+=> CSV
+```
+
+Adding the `false` parameter to `const_get` prevents this:
+
+```ruby
+Rouge::Formatters.const_get('CSV', false)
+NameError: uninitialized constant Rouge::Formatters::CSV
+```
+---
+ lib/kramdown/converter/syntax_highlighter/rouge.rb |  2 +-
+ test/test_files.rb | 18 +++---
+ 2 files changed, 12 insertions(+), 8 deletions(-)
+
+diff --git a/lib/kramdown/converter/syntax_highlighter/rouge.rb b/lib/kramdown/converter/syntax_highlighter/rouge.rb
+index c799526..ed6a4f8 100644
+--- a/lib/kramdown/converter/syntax_highlighter/rouge.rb
 b/lib/kramdown/converter/syntax_highlighter/rouge.rb
+@@ -70,7 +70,7 @@ module Kramdown::Converter::SyntaxHighlighter
+   when Class
+ formatter
+   when /\A[[:upper:]][[:alnum:]_]*\z/
+-::Rouge::Formatters.const_get(formatter)
++::Rouge::Formatters.const_get(formatter, false)
+   else
+ # Available in Rouge 2.0 or later
+ ::Rouge::Formatters::HTMLLegacy
+diff --git a/test/test_files.rb b/test/test_files.rb
+index 82ff6b0..3517e55 100644
+--- a/test/test_files.rb
 b/test/test_files.rb
+@@ -21,16 +21,20 @@ begin
+   end
+ 
+   # custom formatter for tests
+-  class RougeHTMLFormatters < Kramdown::Converter::SyntaxHighlighter::Rouge.formatter_class
++  module Rouge
++module Formatters
++  class RougeHTMLFormatters < Kramdown::Converter::SyntaxHighlighter::Rouge.formatter_class
+ 
+-tag 'rouge_html_formatters'
++tag 'rouge_html_formatters'
+ 
+-def stream(tokens, &b)
+-  yield %()
+-  super
+-  yield %()
+-end
++def stream(tokens, &b)
++  yield %()
++  super
++  yield %()
++end
+ 
++  end
++end
+   end
+ rescue LoadError, SyntaxError, NameError
+ end
diff --git a/debian/patches/series b/debian/patches/series
index 7d4b5b1..f8d5d26 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 fix_manpage_warnings.patch
+0002-Restrict-Rouge-formatters-to-Rouge-Formatters-namesp.patch


signature.asc
Description: PGP signature

Bug#986364: cupt: Should Recommends

[Nelson A. de Oliveira]

Package: cupt
Version: 2.10.4+nmu1+b1
Severity: wishlist

Hi!

cupt should probably
Recommends: libcupt4-2-downloadmethod-curl | libcupt4-2-downloadmethod-wget

This info is already explained in the package's description:

 Cupt has built-in support for APT repositories using the file:// or copy://
 URL schemas. For access to remote repositories using HTTP or FTP, install a
 download method such as libcupt4-2-downloadmethod-curl.

Downloading from FTP/HTTP(S) is probably what most of the users need or
will use and recommending libcupt4-2-downloadmethod-* seems to make
sense.

Thank you!

Best regards,
Nelson

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

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

Versions of packages cupt depends on:
ii  libboost-program-options1.74.0  1.74.0-9
ii  libc6   2.31-11
ii  libcupt4-2  2.10.4+nmu1+b1
ii  libgcc-s1   10.2.1-6
ii  libstdc++6  10.2.1-6

cupt recommends no packages.

Versions of packages cupt suggests:
pn  libreadline7
ii  sensible-utils  0.0.14

-- no debconf information

Bug#986351: hplip: Printing Places All Jobs On Hold

[Brian Potkin]

On Sun 04 Apr 2021 at 12:50:46 +0100, Brian Potkin wrote:

[...]

> Thank you for your report, Roger. Please give the output of
>
>   lpinfo -v
>
> Do you mean "often" or "always"?
>
> Regards,
>
> Brian.

---

 This message was created automatically by mail delivery software.

 A message that you sent could not be delivered to one or more of its
 recipients. This is a permanent error. The following address(es) failed:

  slow_sp...@att.net
host al-ip4-mx-vip2.prodigy.net [144.160.235.144]
SMTP error from remote mail server after MAIL 
FROM::
553 5.3.0 alph736 DNSBL:ATTRBL 521< 77.44.3.143 >_is_blocked.For assistance 
forward this error to
+abuse_...@abuse-att.net

 [ -- Attachment #2 --]
 [-- Type: message/delivery-status, Encoding: 7bit, Size: 0.3K --]

 Reporting-MTA: dns; copernicus.org.uk

---

I really do not fancy fighting AT&T. Thinking.

-- 
Brian.

Bug#986363: O: guile-lib -- Library of useful Guile modules

[Göran Weinholt]

Package: wnpp
Severity: normal
Control: affects -1 src:guile-lib

I intend to orphan the guile-lib package.

The package description is:
 A set of various-purpose library modules for Guile. Covered areas include:
 .
  * Unit testing framework ala JUnit
  * Logging system
  * String routines (wrapping, completion, soundex algorithm)
  * OS process chains (think "shell pipes in scheme")
  * ANSI escape sequence text coloring
  * A thread-safe message queue
  * Routines to perform topological sorts
  * Neil Van Dyke's permissive ("pragmatic") HTML parser
  * Nifty and concise regular expression routines
  * Classic search functions

Bug#986362: software-properties-gtk: The Updates and Developer Options tabs enable trixie instead of bullseye

[Amr Ibrahim]

Package: software-properties-gtk
Version: 0.96.20.2-2.1
Severity: important
X-Debbugs-Cc: amribrahim1...@hotmail.com

Dear Maintainer,

The Updates and Developer Options tabs enable trixie-updates, trixie-security 
and trixie-proposed-updates in the sources.list.

That should not happen because trixie does not exist. It should enable bullseye 
instead.


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

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

Versions of packages software-properties-gtk depends on:
ii  gir1.2-gtk-3.0   3.24.24-3
ii  python3  3.9.2-2
ii  python3-gi   3.38.0-2
ii  python3-software-properties  0.96.20.2-2.1
ii  software-properties-common   0.96.20.2-2.1

software-properties-gtk recommends no packages.

Versions of packages software-properties-gtk suggests:
pn  gnome-software  

-- no debconf information

Bug#986351: hplip: Printing Places All Jobs On Hold

[Brian Potkin]

severity 986351 important
thanks


On Sat 03 Apr 2021 at 21:17:00 -0400, Roger wrote:

[...]

> This issue happens often.  The system is Debian 10, with Xfce 4.12 and
> an HP Photosmart C3100 Series All-in-One printer running on USB
> connection.  All updates have been applied as notified by the OS
> system.
> 
> In trying to install it:
> hplip is already the newest version (3.18.12+dfsg0-2).
> 
> 
> cups runs fine, but it cannot release the files, even when attempting
> to do so directly.

Thank you for your report, Roger. Please give the output of

  lpinfo -v

Do you mean "often" or "always"?

Regards,

Brian.

Bug#986361: libubootenv-tool: Add missing manpages

[Bastian Germann]

Package: libubootenv-tool
Severity: normal

Please add manpages for fw_printenv and fw_setenv. You can base them on the former u-boot-tools' 
manpages:


https://manpages.debian.org/buster/u-boot-tools/fw_printenv.8.en.gz
https://manpages.debian.org/buster/u-boot-tools/fw_setenv.8.en.gz

Bug#986360: RFS: awf-gtk4/2.3.0-1 [ITP] -- A widget factory is a theme preview, application for GTK

[cont...@luigifab.fr]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "awf-gtk4"

 * Package name: awf-gtk4
   Version : 2.3.0-1
   Upstream Author : Fabrice Creuzot 
 * URL : https://github.com/luigifab/awf-extended
 * License : GPL-3+
 * Vcs : https://github.com/luigifab/awf-extended
   Section : x11

A widget factory is a theme preview application for GTK. It displays the
various widget types provided by GTK in a single window allowing to see
the visual effect of the applied theme.

It builds those binary packages:

  awf-gtk4 - A widget factory is a theme preview application for GTK

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

  https://mentors.debian.net/package/awf-gtk4

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

  dget -x
https://mentors.debian.net/debian/pool/main/a/awf-gtk4/awf-gtk4_2.3.0-1.dsc

Changes since the last upload:

   * Initial debian package release (Closes: #959433)

Regards,
Thank you

Bug#986355: xabacus: [INTL:nb] Norwegian Bokmål initial translation

[David S.]

Package: xabacus
Version: 8.2.2
Severity: wishlist
Tags: l10n patch

Hi,

The inital Norwegian Bokmål translation for xabacus is attached.
# ABACUS TEACH
# Copyright (C) 2017 - 2019
# This file is distributed under the same license as the xabacus package.
#
# David Bagley , 2019.
# David Schledewitz , 2021.
msgid ""
msgstr ""
"Project-Id-Version: xabacus-8.2.2\n"
"Report-Msgid-Bugs-To: \n"
"Last-Translator: David Schledewitz \n"
"Language-Team: Norwegian Bokmål <>\n"
"Language: nb\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2021-04-04 08:19+0200\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Lokalize 19.12.3\n"

#, c-format
msgid "Final answer:"
msgstr "Sist svar"

msgid "Current answer:"
msgstr "Aktuelt svar"

Bug#986354: hardening-runtime breaks upowerd which affects default installation

[Andrew Savchenko]

Package: hardening-runtime
Version: 2
Severity: important
X-Debbugs-Cc: and...@lists.savchenko.net

Dear Maintainer,

Installing this package leads to dpkg-overrides setting permissions in a
way that upowerd is unable to start under a non-root account.

This breaks default installation where DE is using UPower service: Gnome,
Mate and potentially some others.

Please consider adding a conditional or a warning prior to installation.
Tested on fully-updated Bullseye.


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

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

Bug#986359: RFS: libubootenv/0.3-1.1 [NMU] [RC] -- Library to access U-Boot environment

[Bastian Germann]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for the package "libubootenv":

 * Package name: libubootenv
   Version : 0.3-1.1
 * URL : https://github.com/sbabic/libubootenv
 * License : LGPL-2.1+
 * Vcs : https://salsa.debian.org/debian/libubootenv
   Section : utils

It builds those binary packages:

  libubootenv-doc - Library to access U-Boot environment - document
  libubootenv-tool - Library to access U-Boot environment - tool
  libubootenv0.1 - Library to access U-Boot environment - runtime
  libubootenv-dev - Library to access U-Boot environment - development files

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

  https://mentors.debian.net/package/libubootenv/
  https://salsa.debian.org/debian/libubootenv/-/merge_requests/2

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

  dget -x 
https://mentors.debian.net/debian/pool/main/libu/libubootenv/libubootenv_0.3-1.1.dsc

Changes since the last upload:

 libubootenv (0.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Dave Jones ]
   * Added symbols for libubootenv0.1 (Closes: #969216)
 .
   [ Bastian Germann ]
   * Compile with NDEBUG set (Closes: #985948)
   * Let libubootenv-dev depend on zlib1g-dev (Closes: #969026)

Regards,
Bastian

Bug#986358: hardening-runtime: Restrictions on /etc/pam.d/ break X screensavers

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, 2021-04-04 at 19:22 +0930, Andrew Savchenko wrote:
> Package: hardening-runtime
> Version: 2
> Severity: important
> X-Debbugs-Cc: and...@savchenko.net
> 
> Dear Maintainer,
> 
> Restricting permissions on /etc/pam.d to 0700 while the folder is owned
> by `root:root` leads to xscreensaver, mate-screensaver and others being
> unable to authenticate a user.
> 
> Perhaps worth adding a warning or making this optional?

Hi Andrew,

statoverride in hardening-runtime were added by Topi Miettinen so I'm adding
him in the loop for comments.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmBpj3oACgkQ3rYcyPpX
RFuRNAf6AvjtfiX9RY0IGyTOMI5k3VxU77akVRDPF2g8p5xGMVsiO9ZCPyW7no3R
X7kmkUd0E+CGCv0qS9FrAGYP5vEAqsI8jNlrqyl9qj5SWlegZ8/yybidm2GvywgY
aZ9OIusyCY8TdrOnJwZz1vqNhTIs3ymHIERbt/PV2oX/jJXHTDS1yuSbHWDc/A09
JS/rspSYlm8gqQcyxU3HpYCQc9UZskx9mYg+IFNR07zZJQO7/Ebi2j/hvK91HDwP
4i562mL79TK5L8XtTSxI1cu1B1G9zjyxWGS7VjANS7fdJSacNGGOEWJ3vGznxGsk
PYu02fdIziwad8G3YXx0hadvjjKgwQ==
=kpuW
-END PGP SIGNATURE-

Bug#947217: shorewall-masq superseded by shorewall-snat

[Jeremy Sowden]

shorewall-masq was superseded by shorewall-snat and its man-page
deleted in 5.2.0.

J.


signature.asc
Description: PGP signature

Bug#985850: RFS: filezilla/3.53.1-1 [Team] -- Full-featured graphical FTP/FTPS/SFTP client

[Gianfranco Costamagna]

control: close -1

done thanks

G.

Bug#985977: unblock: dlt-viewer/2.21.2+dfsg-1

[Gianfranco Costamagna]

On Thu, 1 Apr 2021 22:06:35 +0200 Paul Gevers  wrote:
> Hi Gianfranco,
> 
> On Mon, 29 Mar 2021 10:49:38 +0200 Sebastian Ramacher
>  wrote:
> > Seems fine without the compat bump.
> 
> Please revert.
> 
> https://release.debian.org/bullseye/FAQ.html (last section).
> 
> Paul
> 
> 
> 

done thanks!

G.

Bug#986029: [Virtualsquare] Bug#986029: fuse-umfuse-fat: newer upstream version available?

[Junichi Uekawa]

Thanks for the info, looking forward to the new version!

On Sun, 28 Mar 2021 19:14:16 +0900,
Renzo Davoli wrote:
> 
> Hi Junichi,
> 
> Virtualsquare's FAT module for fuse (compatible with umfuse and vufuse) has 
> been rewritten.
> [1] is the new source code based on the FAT file system module for embedded 
> systems fatfs by ChaN.
> The virtualsquare team is working to package this new implementation as a 
> Debian package as
> soon as possible. It is in the queue, maybe we'll work on it just after 
> bullseye's release.
> ChaN's module is mode stable and complete than our former libfat.
> 
> The source code of the current fuse-umfuse-fat package can be found here 
> (it is a subdir of the view-os source tree):
> [2] [3]
> 
> [1] https://github.com/virtualsquare/fusefatfs
> [2] https://github.com/virtualsquare/view-os/tree/master/fuse-modules/fat
> [3] https://sourceforge.net/projects/view-os/
> 
> * wishes,
> 
>   renzo
> 
> On Sun, Mar 28, 2021 at 05:07:59PM +0900, Junichi Uekawa wrote:
> > Source: fuse-umfuse-fat
> > Version: 0.1a-1.2
> > Severity: wishlist
> > 
> > Dear Maintainer,
> > 
> > I was looking at some issues with fusefat and noticed that the
> > upstream wiki page [1] links to github repository [2].  Is this a new
> > upstream release?
> > 
> > One thing that confuses me is that history file [3] seems to suggest
> > that the release would have been 0.06 by June 2008, so not sure if
> > this was the project that was packaged in Debian.
> > 
> > [1] http://wiki.virtualsquare.org/#!repos.md
> > [2] https://github.com/virtualsquare/fusefatfs
> > [3] 
> > https://github.com/virtualsquare/fusefatfs/blob/master/fatfs/source/00history.txt
> > 
> > -- System Information:
> > Debian Release: 10.8
> >   APT prefers stable
> >   APT policy: (500, 'stable')
> > Architecture: amd64 (x86_64)
> > 
> > Kernel: Linux 5.4.88-12224-gf05236dbdecf (SMP w/8 CPU cores; PREEMPT)
> > Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
> > to ja_JP.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
> > ja_JP.UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> 

Bug#986354: hardening-runtime breaks upowerd which affects default installation

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, 2021-04-04 at 15:48 +0930, Andrew Savchenko wrote:
> Installing this package leads to dpkg-overrides setting permissions in a
> way that upowerd is unable to start under a non-root account.

Hi, could you detail which permissions and from where? I'm aware of the issue
with user namespaces but not from the permissions.
> 
> This breaks default installation where DE is using UPower service: Gnome,
> Mate and potentially some others.
> 
> Please consider adding a conditional or a warning prior to installation.
> Tested on fully-updated Bullseye.

There's already a small warning in the package long description, do you have
something specific in mind? Could you propose a wording?

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmBpezoACgkQ3rYcyPpX
RFsXsgf9GWN6YoeASS9++pFyg9IR3hdIRf4xDc4yx03YG37QB1+C13DoZ52xNHB6
kMs44+/HaBFON2q6xpzyMP/h1R2GsCvQIpny8g3vd0ZytT2VHUM8p29rZJQKpvrx
qV687/zFw9lhY+HZlFCalYUCyv+e3u4LGbw9sRfHA07cGUaptijhziEIeXhQMjTs
yx6v0thChAEWg+uspulIB+rS34T9rtgj3KGARuCyMFIQ+8VHVzXGTLPkN0toDpnU
P5Pp8tfvSTZABT9pgT+h6ExykCGUzRD2No/ry/xi9294G/ujHXk7QAyckTIVSQ6G
YwLcsvHjz2Gqa5Z9pPlDwiDUQYb3WQ==
=rLoG
-END PGP SIGNATURE-

Bug#986357: Please improve package description

[Enrico Zini]

Package: sq
Version: 0.25.0-1
Severity: normal

Hello,

thanks for packaging Sequoia.

The package contains a user-facing tool, and the package description
contains mostly redundant technical details about how the package is
generated.

Could you please update the description so that it explains what the sq
command is supposed to do, so that one could use the description to see
if it's a package that might do some of what they need?


Enrico

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

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

Bug#986356: cached package is truncated

[Osamu Aoki]

Package: apt-cacher-ng
Version: 3.6.3-1
Severity: normal

I think apt-cacher-ng doesn't close downloaded file properly under heavy
stress and leaves truncated damaged package file in its cache.  Its size
is smaller than the size listed in *.head file.  So apt-cacher-ng knows
it is truncated or under download.

Let me describe situation with some screen grubs.

I experience problem when many package files are downloaded during the
KVM guest system to install GUI tasks (GNOME and KDE).

Host side is started to use this cache but don't see this problem so
far.

The virt-manager's message from guest's APT seem to indicate hash is
broken but file size is OK.

As I checked cached packages on the host system, one by the
apt-cacher-ng and another by manual download, situation apears to be a
bit different.  Basically, apt-cacher-ng is truncating downloaded file
in its cache.  Clearly package in apt-cache-ng's cache is much shorter.
APT error message was deceptive.  I did vimdiff of the hexdump to see it
was really truncation at one point.

Of course setting --fix-missing will allow me to move on but that's on
broken package data.

I am on a fairly nice optical_to_room + wifi_to_pc fast connection.  So
such frequent and almost predictable data loss is unthinkable.  My WS
uses fast nvme SSD and all data are on btrfs.

I will attach 3 screen captures and log in the follow up

-- Package-specific info:

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

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

Versions of packages apt-cacher-ng depends on:
ii  adduser  3.118
ii  debconf [debconf-2.0]1.5.75
ii  dpkg 1.20.7.1
ii  libbz2-1.0   1.0.8-4
ii  libc62.31-11
ii  libevent-2.1-7   2.1.12-stable-1
ii  libevent-pthreads-2.1-7  2.1.12-stable-1
ii  libgcc-s110.2.1-6
ii  liblzma5 5.2.5-2
ii  libssl1.11.1.1k-1
ii  libstdc++6   10.2.1-6
ii  libsystemd0  247.3-3
ii  libwrap0 7.6.q-31
ii  lsb-base 11.1.0
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages apt-cacher-ng recommends:
ii  ca-certificates  20210119

Versions of packages apt-cacher-ng suggests:
ii  avahi-daemon  0.8-5
ii  doc-base  0.11.1
ii  libfuse2  2.9.9-5

-- Configuration Files:
/etc/apt-cacher-ng/security.conf [Errno 13] Permission denied: 
'/etc/apt-cacher-ng/security.conf'

-- debconf information:
* apt-cacher-ng/cachedir: keep
* apt-cacher-ng/bindaddress: keep
* apt-cacher-ng/gentargetmode: No automated setup
* apt-cacher-ng/proxy: keep
* apt-cacher-ng/tunnelenable: true
* apt-cacher-ng/port: keep

Bug#985197: gdb bt

[Silvério Santos]

coredumpctl gdb 1920
   PID: 1920 (kwin_wayland)
   UID: 1000 (myname)
   GID: 1000 (myname)
Signal: 11 (SEGV)
 Timestamp: Sun 2021-04-04 09:10:40 CEST (7min ago)
  Command Line: /usr/bin/kwin_wayland --xwayland --exit-with-session=/usr/lib/
x86_64-linux-gnu/libexec/startplasma-waylandsession
Executable: /usr/bin/kwin_wayland
 Control Group: /user.slice/user-1000.slice/session-3.scope
  Unit: session-3.scope
 Slice: user-1000.slice
   Session: 3
 Owner UID: 1000 (myname)
   Boot ID: 0ae3171f524a465e9acb992a202f814b
Machine ID: f72ae64cabdcedd770963755524c666b
  Hostname: systemname
   Storage: /var/lib/systemd/coredump/core.kwin_wayland.
1000.0ae3171f524a465e9acb992a202f814b.1920.161752024000.zst (truncated)
   Message: Process 1920 (kwin_wayland) of user 1000 dumped core.

Stack trace of thread 1920:
#0  0x7f65188b9268 n/a (n/a + 0x0)

GNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/kwin_wayland...
(No debugging symbols found in /usr/bin/kwin_wayland)
BFD: warning: /tmp/user/1000/coredump-ySV5m6 is truncated: expected core file
size >= 2365169664, found: 2147483648

warning: Can't open file /memfd:wayland-cursor (deleted) during file-backed
mapping note processing

warning: Can't open file /memfd:wayland-shm (deleted) during file-backed mapping
note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file /tmp/#730 (deleted) during file-backed mapping note
processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file /tmp/#164 (deleted) during file-backed mapping note
processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file /run/user/1000/xwayland-shared-P4Yrw8 (delete