Bug#950123: virtualenvwrapper: Autocomplete not loaded in default install

[David da Silva Polverari]

Hi,

I can confirm that despite what is stated on
/usr/share/doc/virtualenvwrapper/README.Debian,
virtualenvwrapper_4.8.4-4, doesn't install
/etc/bash_completion.d/virtualenvwrapper, as it was the case in the
version found on Buster (4.3.1-2).

Regards,

David Polverari.

Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel

[Hamish Moffatt]

On 29/8/20 1:01 pm, Noah Meyerhans wrote:

On Sat, Aug 29, 2020 at 11:43:21AM +1000, Hamish Moffatt wrote:

Could you please enable CONFIG_F2FS_FS in the cloud kernel?

[...]

What makes you think f2fs will be commonly used in cloud deployments?


I don't know that it will be, but as it supports encryption and compression
and benchmarks shows it performs at least as well as ext4, I don't see why
it couldn't be a good choice for virtual machines. It seems at least as
useful in a cloud deployment as minix and hpfs which are included in this
flavour.

This sounds like a good argument for turning off minix and hpfs to me.
;)

I thought you might say that :)


Is F2FS usable as a Debian root filesystem?  Does it support all the
features (file capabilities and POSIX ACLs, for example) that are
commonly used on Debian systems?

The cloud team, for what it's worth, does not have any plans to switch
from ext4 in the forseeable future.  (We probably would not do so unless
Debian made the change distro-wide.)  That doesn't mean we shouldn't
consider enabling it, but I'd like to see a clearer use case.  My small
amount of research into it (mostly reading wikipedia and a couple of the
reference sources) suggests that it's most popular on phones and similar
devices, not cloud instances.  Do you see use cases involving
manipulating filesystems for those type of devices in cloud VMs?  Or
something else?

How are crypto keys handled for its encryption functionality?

The cloud kernel is not expected to be useful for 100% of people, even
in cloud environments.  In cases where specific functionality is needed
that isn't available in the cloud kernel, the generic kernel is
available and I'd probably recommend that.



I envisage using f2fs on cloud instances for their own storage, with the 
benefit of encryption and compression (without the performance penalty 
of eg ZFS).


f2fs appears to be available in Clear Linux as the root file system 
since March (https://github.com/clearlinux/distribution/issues/1522, 
https://www.phoronix.com/scan.php?page=news_item=Clear-Linux-F2FS-Root-Option 
). Debian is working on this too according to 
https://www.phoronix.com/scan.php?page=news_item=Debian-F2FS-Root-File-System 
.


Crypto setup is handled with fscrypt just as per ext4.


thanks
Hamish

Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel

[Ben Hutchings]

On Fri, 2020-08-28 at 20:01 -0700, Noah Meyerhans wrote:
> On Sat, Aug 29, 2020 at 11:43:21AM +1000, Hamish Moffatt wrote:
> > > > Could you please enable CONFIG_F2FS_FS in the cloud kernel?
> > > [...]
> > > 
> > > What makes you think f2fs will be commonly used in cloud deployments?
> > > 
> > I don't know that it will be, but as it supports encryption and compression
> > and benchmarks shows it performs at least as well as ext4, I don't see why
> > it couldn't be a good choice for virtual machines. It seems at least as
> > useful in a cloud deployment as minix and hpfs which are included in this
> > flavour.
> 
> This sounds like a good argument for turning off minix and hpfs to me.
> ;)
[...]

I agree with that; I didn't realise they were enabled.

Ben.

-- 
Ben Hutchings
Experience is what causes a person to make new mistakes
instead of old ones.




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

Bug#969194: linuxptp: LinuxPTP version 3.0 available

[Jon Nistor]

Package: linuxptp
Version: 1.9.2
Severity: normal

Dear Maintainer,

LinuxPTP is shipping verion 3.0 as of July 2020.  Please consider updating the 
package system to reflect version 3.

Release notes are as follows since 1.9.2:

Version 3.0 - July 2020
This release offers substantial new functionality. Users are encouraged to 
upgrade. The most notable changes are as follows.

* Improves system time synchronization via the PTP_SYS_OFFSET_PRECISE and 
PTP_SYS_OFFSET_EXTENDED ioctls.
* Supports implementing a PTP GM clock by using a GPS radio or other PPS time 
source.
* Provides per-port statistics via the management interface.
* Implements IEEE 1588 v2.1 slave event monitoring.
* Adds Automotive Profile support.


Version 2.0 - August 2018
This release represents a major new milestone, and it includes substantial new 
features. Users are encouraged to upgrade. The most notable changes are as 
follows.

* Peer-to-Peer Transparent Clock support
* End-to-End Transparent Clock support
* Unicast support
* Support for all three Telecom Profiles
- T-REC-G.8265.1-201407
- T-REC-G.8275.1-201606
- T-REC-G.8275.2-201708





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

Kernel: Linux 4.9.0-12-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linuxptp depends on:
ii  init-system-helpers  1.48
ii  libc62.24-11+deb9u4

linuxptp recommends no packages.

linuxptp suggests no packages.

Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel

[Noah Meyerhans]

On Sat, Aug 29, 2020 at 11:43:21AM +1000, Hamish Moffatt wrote:
> > > Could you please enable CONFIG_F2FS_FS in the cloud kernel?
> > [...]
> > 
> > What makes you think f2fs will be commonly used in cloud deployments?
> > 
> I don't know that it will be, but as it supports encryption and compression
> and benchmarks shows it performs at least as well as ext4, I don't see why
> it couldn't be a good choice for virtual machines. It seems at least as
> useful in a cloud deployment as minix and hpfs which are included in this
> flavour.

This sounds like a good argument for turning off minix and hpfs to me.
;)

Is F2FS usable as a Debian root filesystem?  Does it support all the
features (file capabilities and POSIX ACLs, for example) that are
commonly used on Debian systems?

The cloud team, for what it's worth, does not have any plans to switch
from ext4 in the forseeable future.  (We probably would not do so unless
Debian made the change distro-wide.)  That doesn't mean we shouldn't
consider enabling it, but I'd like to see a clearer use case.  My small
amount of research into it (mostly reading wikipedia and a couple of the
reference sources) suggests that it's most popular on phones and similar
devices, not cloud instances.  Do you see use cases involving
manipulating filesystems for those type of devices in cloud VMs?  Or
something else?

How are crypto keys handled for its encryption functionality?

The cloud kernel is not expected to be useful for 100% of people, even
in cloud environments.  In cases where specific functionality is needed
that isn't available in the cloud kernel, the generic kernel is
available and I'd probably recommend that.

noah

Bug#969193: xscreensaver-data-extra: line break corrupts config file

[Francesco Potortì]

Package: xscreensaver-data-extra
Version: 5.42+dfsg1-1+b1
Severity: normal
X-Debbugs-Cc: none, Francesco Potortì 
File: /usr/share/applications/screensavers/glitchpeg.desktop

Aug 26 07:00:12 tucano tracker-extract[2555695]: Could not load desktop file 
'file:///usr/share/applications/screensavers/glitchpeg.desktop': Key file 
contains line “several times a second.  After a while, finds a new image to 
corrupt. Written by Jamie Zawinski; 2018.” which is not a key-value pair, 
group, or comment

This is caused by a newline in the comment line.  The patch is trivial:
just remove the newline

-- 
Francesco Potortì (ricercatore)Voice:  +39.050.621.3058
ISTI - Area della ricerca CNR  Mobile: +39.348.8283.107
via G. Moruzzi 1, I-56124 Pisa Skype:  wnlabisti
(gate 20, 1st floor, room C71) Web:http://fly.isti.cnr.it


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

Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=it_IT.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 xscreensaver-data-extra depends on:
ii  dictionaries-common  1.28.2
ii  libc62.31-3
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libglib2.0-0 2.64.4-1
ii  libjpeg-turbo-progs  1:2.0.5-1.1
ii  libx11-6 2:1.6.10-3
ii  libxext6 2:1.3.3-1+b2
ii  libxft2  2.3.2-2
ii  libxmu6  2:1.1.2-2+b3
ii  libxt6   1:1.2.0-1
ii  netpbm   2:10.0-15.3+b2
ii  xscreensaver-data5.42+dfsg1-1+b1

xscreensaver-data-extra recommends no packages.

xscreensaver-data-extra suggests no packages.

-- no debconf information

Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel

[Hamish Moffatt]

On 29/8/20 7:41 am, Ben Hutchings wrote:

Control: tag -1 moreinfo

On Fri, 2020-08-28 at 14:43 +0800, Hamish Moffatt wrote:

Package: src:linux
Version: 5.7.10-1~bpo10+1
Severity: wishlist

Hi,
Could you please enable CONFIG_F2FS_FS in the cloud kernel?

[...]

What makes you think f2fs will be commonly used in cloud deployments?


I don't know that it will be, but as it supports encryption and 
compression and benchmarks shows it performs at least as well as ext4, I 
don't see why it couldn't be a good choice for virtual machines. It 
seems at least as useful in a cloud deployment as minix and hpfs which 
are included in this flavour.


thanks
Hamish

Bug#969123: webext-ublock-origin: FF80 broke ublock again

[Markus Koschany]

Hello ftp team,

ublock origin is in the NEW queue again. [1] The binary packages have
not changed since the last review. I had uploaded a newer version to
unstable and when you finally approved the version I had uploaded to
experimental it got automatically removed from Debian because the
version was lower than in unstable.

Please fast-track the review of ublock-origin because nothing has
changed in reality and the package is currently unusable due to a new
Firefox version.

Thank you

Markus

[1] https://ftp-master.debian.org/new/ublock-origin_1.29.0+dfsg-1.html



signature.asc
Description: OpenPGP digital signature

Bug#969123: webext-ublock-origin: FF80 broke ublock again

[Christoph Anton Mitterer]

On Sat, 2020-08-29 at 01:32 +0200, Markus Koschany wrote:
> Thanks for reporting. I believe this is fixed in 1.29.0+dfsg.
> Unfortunately the package has to go through NEW again which is
> unfortunate. I hope I can convince the ftp-team to fast-track
> reviewing
> uBo (again).

Interestingly it seems other (all) add-ons are broken too, at least for
me... but not when I create fresh profiles.


Thanks,
Chris.

Bug#969123: webext-ublock-origin: FF80 broke ublock again

[Markus Koschany]

Control: tags -1 pending

On Thu, 27 Aug 2020 23:13:45 +0200 Christoph Anton Mitterer
 wrote:
[...]
> It seems stupid *zilla broke ublock origina again with the new Firefox.

Thanks for reporting. I believe this is fixed in 1.29.0+dfsg.
Unfortunately the package has to go through NEW again which is
unfortunate. I hope I can convince the ftp-team to fast-track reviewing
uBo (again).


Markus



signature.asc
Description: OpenPGP digital signature

Bug#969192: O: memtest86 -- thorough real-mode memory tester

[Yann Dirson]

Package: wnpp
Severity: normal

I intend to orphan the memtest86 package.

There will likely be no more DGSF-compliant version of this package.
memtest86+ probably supercedes it completely nowadays.  I'm orphaning
this one at the same time as memtest86+, as it makes sense either to
have the same people maintaining them, or to drop old memtest86.


The package description is:
 Memtest86 scans your RAM for errors.
 .
 This tester runs independently of any OS - it is run at computer
 boot-up, so that it can test *all* of your memory.  You may want to
 look at `memtester', which allows testing your memory within Linux,
 but this one won't be able to test your whole RAM.
 .
 It can output a list of bad RAM regions usable by the BadRAM kernel
 patch, so that you can still use you old RAM with one or two bad bits.
 .
 This is the last DFSG-compliant version of this software, upstream
 has opted for a proprietary development model starting with 5.0.  You
 may want to consider using memtest86+, which has been forked from an
 earlier version of memtest86, and provides a different set of
 features.  It is available in the memtest86+ package.
 .
 A convenience script is also provided to make a grub-legacy-based
 floppy or image.
 Memtest86 scans your RAM for errors.
 .
 This tester runs independently of any OS - it is run at computer
 boot-up, so that it can test *all* of your memory.  You may want to
 look at `memtester', which allows testing your memory within Linux,
 but this one won't be able to test your whole RAM.
 .
 It can output a list of bad RAM regions usable by the BadRAM kernel
 patch, so that you can still use you old RAM with one or two bad bits.
 .
 This is the last DFSG-compliant version of this software, upstream
 has opted for a proprietary development model starting with 5.0.  You
 may want to consider using memtest86+, which has been forked from an
 earlier version of memtest86, and provides a different set of
 features.  It is available in the memtest86+ package.
 .
 A convenience script is also provided to make a grub-legacy-based
 floppy or image.

Bug#969191: O: memtest86+ -- thorough real-mode memory tester

[Yann Dirson]

Package: wnpp
Severity: normal

I intend to orphan the memtest86+ package.

After much time a new beta is out, but it still does not include the
multiboot support.  I don't have enough interest in this to dedicate
the time it requires to do things right.

The current unreleased state of the package is at
https://salsa.debian.org/debian/memtest86plus on branch "wip".


The package description is:
 Memtest86+ scans your RAM for errors.
 .
 This tester runs independently of any OS - it is run at computer
 boot-up, so that it can test *all* of your memory.  You may want to
 look at `memtester', which allows to test your memory within Linux,
 but this one won't be able to test your whole RAM.
 .
 It can output a list of bad RAM regions usable by the BadRAM kernel
 patch, so that you can still use your old RAM with one or two bad bits.
 .
 Memtest86+ is based on memtest86 3.0, and adds support for recent
 hardware, as well as a number of general-purpose improvements,
 including many patches to memtest86 available from various sources.
 .
 Both memtest86 and memtest86+ are being worked on in parallel.
 Memtest86+ scans your RAM for errors.
 .
 This tester runs independently of any OS - it is run at computer
 boot-up, so that it can test *all* of your memory.  You may want to
 look at `memtester', which allows to test your memory within Linux,
 but this one won't be able to test your whole RAM.
 .
 It can output a list of bad RAM regions usable by the BadRAM kernel
 patch, so that you can still use your old RAM with one or two bad bits.
 .
 Memtest86+ is based on memtest86 3.0, and adds support for recent
 hardware, as well as a number of general-purpose improvements,
 including many patches to memtest86 available from various sources.
 .
 Both memtest86 and memtest86+ are being worked on in parallel.

Bug#969187: librtmidi-dev: content differs vastly between architectures

[Thorsten Glaser]

Sebastian Ramacher dixit:

>That looks like the expected difference between the amd64 and arm64
>packages. So what issues are you seeing?

Oh, interesting. I was using p.d.o to search for RtMidi.h
and found this divergence in the file lists on p.d.o…

>> https://packages.debian.org/sid/amd64/librtmidi-dev/filelist
>> https://packages.debian.org/sid/arm64/librtmidi-dev/filelist

I admit I didn’t download the packages and look for myself,
trusting the p.d.o data to be, if possibly up to 36 hours out
of date, at least accurate.

bye,
//mirabilos
-- 
[16:04:33] bkix: "veni vidi violini"
[16:04:45] bkix: "ich kam, sah und vergeigte"...

Bug#969189: Acknowledgement (ITP: hydrapaper -- Utility that sets background independently for each monitor)

[Francisco M Neto]

submitter 969189 !

On Fri, 2020-08-28 at 21:39 +, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
> 
> You can follow progress on this Bug here: 969189: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969189.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due
> course.
> 
> As you requested using X-Debbugs-CC, your message was also forwarded
> to
>   fmn...@gmail.com
> (after having been given a Bug report number, if it did not have
> one).
> 
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
> 
> If you wish to submit further information on this problem, please
> send it to 969...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 


-- 
[]'s,

Francisco M Neto 

GPG: 4096R/D692FBF0


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

Bug#969190: buster-pu: package libvncserver/0.9.11+dfsg-1.3+deb10u3

[Mike Gabriel]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu


Dear release team,

several (minor) CVE issues have been resolved in buster's libvncserver:

+  * CVE-2019-20839: libvncclient: bail out if unix socket name would overflow.
+  * CVE-2020-14397: libvncserver: add missing NULL pointer checks.
+  * CVE-2020-14399: libvncclient: fix pointer aliasing/alignment issue.
+  * CVE-2020-14400: libvncserver: fix pointer aliasing/alignment issue.
+  * CVE-2020-14401: libvncserver: scale: cast to 64 bit before shifting.
+  * CVE-2020-14402, CVE-2020-14403, CVE-2020-14404: libvncserver: encodings:
+prevent OOB accesses.
+  * CVE-2020-14405: libvncclient/rfbproto: limit max textchat size.

The changes have already been dput as +deb10u4. Thanks for reviewing.

Greets,
Mike


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

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

Bug#969091: pdns-backend-mysql: Queries calling stored procedures broken with recent MariaDB/MySQL

[Xan Charbonnet]

Hi Chris,

On the pdns mailing list, it's been requested I file an issue in the 
GitHub repository.  I've done so:

https://github.com/PowerDNS/pdns/issues/9421

It includes detailed steps to reproduce.  It really just boils down to 
setting one of the queries to use a stored procedure, eg:


gmysql-basic-query=CALL basic_query(?, ?)

Do the Debian tests include stored procedures?  Or just regular SQL queries?

-Xan

Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel

[Ben Hutchings]

Control: tag -1 moreinfo

On Fri, 2020-08-28 at 14:43 +0800, Hamish Moffatt wrote:
> Package: src:linux
> Version: 5.7.10-1~bpo10+1
> Severity: wishlist
> 
> Hi,
> Could you please enable CONFIG_F2FS_FS in the cloud kernel?
[...]

What makes you think f2fs will be commonly used in cloud deployments?

Ben.

-- 
Ben Hutchings
It is impossible to make anything foolproof
because fools are so ingenious.




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

Bug#969189: ITP: hydrapaper -- Utility that sets background independently for each monitor

[Francisco M Neto]

Package: wnpp
Severity: wishlist
Owner: Francisco M Neto 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: hydrapaper
  Version : 1.4.2
  Upstream Author : Gabriele Musco 
* URL : https://gitlab.com/gabmus/HydraPaper
* License : GPLv3
  Programming Lang: Python
  Description : Utility that sets background independently for each monitor

HydraPaper is a GTK-based utility that sets background images for multiple
monitor desktops independently. It works by merging multiple wallpaper images
into one and setting the result as wallpaper with the "Spanned" option. It is
based on the GNOME 3 Desktop but officially supports  MATE and Budgie as well,
 and should work on any GNOME-based desktop like Pantheon.

This package offers the functionality of setting different wallpapers on
different monitors, something that GNOME doesn't offer, and similar tools (e.g.
variety) don't support either. It is not a dependency on any other packages.

I plan to maintain it on my own. It is a reasonably small package, it is
fairly simple and its build system is straightforward.

Bug#969112: flashplugin-nonfree: Re: RM: flashplugin-nonfree -- RoQA, unmainained, several RC bugs, techology deprecated

[Tobias Frost]

Package: flashplugin-nonfree
Version: 1:3.7
Followup-For: Bug #969112
Control: reassign -1 ftp.debian.org
Control: severity -1 normal

Reassigning bug after receiving heads-up to decide myself from the maintainer.

-- 
tobi

Bug#969187: librtmidi-dev: content differs vastly between architectures

[Sebastian Ramacher]

Control: tags -1 + moreinfo

On 2020-08-28 22:53:57 +0200, Thorsten Glaser wrote:
> Package: librtmidi-dev
> Version: 3.0.0~ds1-2+b1
> Severity: important
> X-Debbugs-Cc: t...@mirbsd.de
> 
> The amd64 package…
> 
> https://packages.debian.org/sid/amd64/librtmidi-dev/filelist
> 
> /usr/include/rtmidi/RtMidi.h
> /usr/include/rtmidi/rtmidi_c.h
> /usr/lib/x86_64-linux-gnu/librtmidi.so
> /usr/lib/x86_64-linux-gnu/pkgconfig/rtmidi.pc
> /usr/share/doc/librtmidi-dev/README.md
> /usr/share/doc/librtmidi-dev/changelog.Debian.amd64.gz
> /usr/share/doc/librtmidi-dev/changelog.Debian.gz
> /usr/share/doc/librtmidi-dev/changelog.gz
> /usr/share/doc/librtmidi-dev/copyright
> 
> … and the arm64 package…
> 
> https://packages.debian.org/sid/arm64/librtmidi-dev/filelist
> 
> /usr/include/RtMidi.h
> /usr/include/rtmidi/RtMidi.h
> /usr/include/rtmidi/rtmidi_c.h
> /usr/lib/aarch64-linux-gnu/librtmidi.so
> /usr/lib/aarch64-linux-gnu/librtmidi.so
> /usr/lib/aarch64-linux-gnu/pkgconfig/rtmidi.pc
> /usr/lib/aarch64-linux-gnu/pkgconfig/rtmidi.pc
> /usr/share/doc/librtmidi-dev/README.md
> /usr/share/doc/librtmidi-dev/changelog.Debian.arm64.gz
> /usr/share/doc/librtmidi-dev/changelog.Debian.gz
> /usr/share/doc/librtmidi-dev/changelog.Debian.gz
> /usr/share/doc/librtmidi-dev/changelog.gz
> /usr/share/doc/librtmidi-dev/copyright
> /usr/share/doc/librtmidi-dev/copyright
> /usr/share/doc/librtmidi-dev/readme
> /usr/share/doc/librtmidi-dev/release.txt.gz
> 
> … differ *vastly* in content. Something in the build system must
> be wrong. This can lead to architecture-specific FTBFSes in pak‐
> kages depending on librtmidi-dev.

$ debdiff librtmidi-dev_3.0.0\~ds1-2+b1_amd64.deb 
librtmidi-dev_3.0.0\~ds1-2+b1_arm64.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in second .deb but not in first
-
-rw-r--r--  root/root   /usr/lib/aarch64-linux-gnu/pkgconfig/rtmidi.pc
-rw-r--r--  root/root   /usr/share/doc/librtmidi-dev/changelog.Debian.arm64.gz
lrwxrwxrwx  root/root   /usr/lib/aarch64-linux-gnu/librtmidi.so -> 
librtmidi.so.4.0.0

Files in first .deb but not in second
-
-rw-r--r--  root/root   /usr/lib/x86_64-linux-gnu/pkgconfig/rtmidi.pc
-rw-r--r--  root/root   /usr/share/doc/librtmidi-dev/changelog.Debian.amd64.gz
lrwxrwxrwx  root/root   /usr/lib/x86_64-linux-gnu/librtmidi.so -> 
librtmidi.so.4.0.0

Control files: lines which differ (wdiff format)

Architecture: [-amd64-] {+arm64+}

That looks like the expected difference between the amd64 and arm64
packages. So what issues are you seeing?

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#969188: RFP: duplicati -- user-friendly remote, encrypted, incremental backups; capable GUI via built-in local server

[Boris BARBOUR]

Package: wnpp
Severity: wishlist

* Package name: duplicati
  Version : 2.0
  Upstream Author : Kenneth Skovhede , Rene Stach

* URL : http://www.duplicati.com/
* License : LGPL-2.1
  Programming Lang: C#
  Description : user-friendly remote, encrypted, incremental
backups; capable GUI via built-in local server

I have looked at most of the backup packages in Debian and duplicati has
a better combination ot features and ease-of-use, at least for personal
use. It can perform remote, encrypted, incremental backups over several
transports. It has a very capable GUI with well-designed configuration
options. It makes a pragmatic, simplifying default choice of largely
trusting the user's machine but not the remote host.

The built-in web server for configuration and administration is very
convenient (and excellent for remote administration using port forwarding).

A debian package exists and requires little more than automated
installation of systemd configuration.

Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles

[Mike Hommey]

On Fri, Aug 28, 2020 at 05:18:44PM +0200, Christoph Anton Mitterer wrote:
> Package: firefox
> Version: 80.0-1
> Severity: normal
> 
> 
> Hi.
> 
> It seems that with FF80 all addons are broken in existing profiles. They're 
> shown
> in the add-ons list, but e.g. their icons aren’t in the menu.
> 
> E.g. ublock origin, noscript also don't seem to work... so it's not just a 
> display
> issue.

It works for me...

Mike

Bug#904664: msgconvert mbox output issues

[Olly Betts]

On Thu, Jul 26, 2018 at 01:30:56PM +0200, Matus UHLAR - fantomas wrote:
> 1. the "From " line contains full "From: " header, while it's supposed to
> contain only the address, without < and > brackets, with one space
> separating address and date (two spaces are used now).

I've fixed this in Debian and submitted the patch upstream.

> 2. output lines are end with CR-LF characters. CR's should be stripped, at
> leasst on unix systems.
> 
> I have compared output with and without --mbox and the only differences are
> - From line
> - mime boundaries
> - new lines.
> 
> Since the 2nd problem seems to come from Email::Sender::Transport::Mbox, I
> believe that package could be avoided, and mbox files can be written to
> single file starting each mail with "From address RFC822-date" and ending
> with empty line.

This same issue had also been reported upstream, but upstream believes
the current behaviour is correct so I think you need to take it up with
them if you disagree:

https://github.com/mvz/email-outlook-message-perl/issues/13#issuecomment-616044853

Writing mbox isn't quite as simple as you suggest - e.g. extra care is
needed for lines starting "From " in the message body.  If this really
is wrong then it would be better to get it fixed in
Email::Sender::Transport::Mbox (as upstream suggests above) - that would
benefit other users of it.

Cheers,
Olly

Bug#487380: [Pkg-utopia-maintainers] Processed: severity of 487380 is serious

[Michael Biebl]

Control: severity -1 normal

Am 28.08.20 um 21:33 schrieb Debian Bug Tracking System:
> Processing commands for cont...@bugs.debian.org:
> 
>> # Modifying a config file is a policy violation
>> severity 487380 serious
> Bug #487380 [libnss-mdns] libnss-mdns: Unasked changes in nsswitch.conf 
> breaks the whole system
> Severity set to 'serious' from 'minor'
>> thanks
> Stopping processing here.
> 
> Please contact me if you need assistance.
> 

/etc/nsswitch.conf is not a conffile.
Policy allows modification of a configuration file from maintainer scripts.



signature.asc
Description: OpenPGP digital signature

Bug#913542: teckit: Fails to build on Ubuntu's ppc64el (symbols)

[Hilmar Preuße]

Am 21.11.2018 um 10:49 teilte Matthias Klose mit:

Hi,

> Control: tags -1 + patch
> 
> proposed patch at
> https://patches.ubuntu.com/t/teckit/teckit_2.5.8+ds2-5ubuntu1.patch
> 
New URL:

https://patches.ubuntu.com/t/teckit/teckit_2.5.8+ds2-5ubuntu2.patch

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#964862: RFS: git-revise/0.6.0-1 -- handy git tool for doing efficient in-memory commit rebases & fixups

[Nicolas Schier]

On Fri, Aug 28, 2020 at 01:28:00PM +0300, Adrian Bunk wrote:
> Control: tags -1 moreinfo
> 
> On Sat, Jul 11, 2020 at 02:02:43PM +0200, Nicolas Schier wrote:
> >...
> > Changes since the last upload:
> >...
> >* Enable autopkgtest by using upstream tests (Closes: #944957)
> 
> This likely worked when you posted the sponsorship request,
> but new pylint makes it fail:
> 
> ...
> lint run-test: commands[0] | pylint gitrevise
> * Module gitrevise.merge
> gitrevise/merge.py:207:12: W0707: Consider explicitly re-raising using the 
> 'from' keyword (raise-missing-from)
> gitrevise/merge.py:225:12: W0707: Consider explicitly re-raising using the 
> 'from' keyword (raise-missing-from)
> * Module gitrevise.utils
> gitrevise/utils.py:73:8: W0707: Consider explicitly re-raising using the 
> 'from' keyword (raise-missing-from)
> gitrevise/utils.py:89:12: W0707: Consider explicitly re-raising using the 
> 'from' keyword (raise-missing-from)
> 
> --
> Your code has been rated at 9.96/10 (previous run: 9.96/10, +0.00)
> 
> ERROR: InvocationError for command 
> /tmp/autopkgtest.SDfHIM/tree/.tox/lint/bin/pylint gitrevise (exited with code 
> 4)
> ...

thanks for the pointer!  I am going to look at it and re-upload in a few
days.

Kind regards,
Nicolas

-- 
epost: nico...@fjasle.eu   irc://oftc.net/nsc
↳ gpg: 18ed 52db e34f 860e e9fb  c82b 7d97 0932 55a0 ce7f
 -- frykten for herren er opphav til kunnskap --

Bug#969187: librtmidi-dev: content differs vastly between architectures

[Thorsten Glaser]

Package: librtmidi-dev
Version: 3.0.0~ds1-2+b1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de

The amd64 package…

https://packages.debian.org/sid/amd64/librtmidi-dev/filelist

/usr/include/rtmidi/RtMidi.h
/usr/include/rtmidi/rtmidi_c.h
/usr/lib/x86_64-linux-gnu/librtmidi.so
/usr/lib/x86_64-linux-gnu/pkgconfig/rtmidi.pc
/usr/share/doc/librtmidi-dev/README.md
/usr/share/doc/librtmidi-dev/changelog.Debian.amd64.gz
/usr/share/doc/librtmidi-dev/changelog.Debian.gz
/usr/share/doc/librtmidi-dev/changelog.gz
/usr/share/doc/librtmidi-dev/copyright

… and the arm64 package…

https://packages.debian.org/sid/arm64/librtmidi-dev/filelist

/usr/include/RtMidi.h
/usr/include/rtmidi/RtMidi.h
/usr/include/rtmidi/rtmidi_c.h
/usr/lib/aarch64-linux-gnu/librtmidi.so
/usr/lib/aarch64-linux-gnu/librtmidi.so
/usr/lib/aarch64-linux-gnu/pkgconfig/rtmidi.pc
/usr/lib/aarch64-linux-gnu/pkgconfig/rtmidi.pc
/usr/share/doc/librtmidi-dev/README.md
/usr/share/doc/librtmidi-dev/changelog.Debian.arm64.gz
/usr/share/doc/librtmidi-dev/changelog.Debian.gz
/usr/share/doc/librtmidi-dev/changelog.Debian.gz
/usr/share/doc/librtmidi-dev/changelog.gz
/usr/share/doc/librtmidi-dev/copyright
/usr/share/doc/librtmidi-dev/copyright
/usr/share/doc/librtmidi-dev/readme
/usr/share/doc/librtmidi-dev/release.txt.gz

… differ *vastly* in content. Something in the build system must
be wrong. This can lead to architecture-specific FTBFSes in pak‐
kages depending on librtmidi-dev.

-- 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.7.0-2-amd64 (SMP w/2 CPU threads)
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 librtmidi-dev depends on:
pn  libasound2-dev  
pn  libjack-dev 
pn  librtaudio-dev  
pn  librtmidi3  
ii  librtmidi4  3.0.0~ds1-2+b1
pn  librtmidi5  

librtmidi-dev recommends no packages.

Versions of packages librtmidi-dev suggests:
pn  librtmidi-doc  

Bug#969186: ITP: libreflections-java -- Java runtime metadata analysis library

[Pierre Gruet]

Package: wnpp
Severity: wishlist
Owner: Debian Java team 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-j...@lists.debian.org

* Package name: libreflections-java
  Version : 0.9.12
  Upstream Author : ronmamo
* URL : https://github.com/ronmamo/reflections
* License : WTFPL
  Programming Lang: Java
  Description : Java runtime metadata analysis library

Reflections scans a classpath, indexes the metadata, allows one to query it on
runtime and may save and collect that information for many modules within a
project.

Using Reflections one can query metadata such as:
 - get all subtypes of some type;
 - get all types/members annotated with some annotation;
 - get all resources matching a regular expression;
 - get all methods with specific signature including parameters, parameter
 annotations and return type.

This package is needed as a predependency of igv, which the Debian med team
would like to package out of non-free. I am personnally aiming at this.
The package will be maintained in the Debian Java team.

Bug#969184: Upgrade fails when interface name has changed

[Thomas Goirand]

On 8/28/20 9:35 PM, dann frazier wrote:
> Package: minissdpd
> Version: 1.5.20190824-1
> Severity: normal
> 
> I changed out docks for my laptop several months ago, which means my
> built-in NIC has a different MAC address, and therefore a different
> interface name. minissdpd has stored the old address in the debconf
> database. Now when I try to upgrade, it fails (see below). Even correcting
> the interface name in /etc/default/minissdpd doesn't fix things, as
> the postinst will just overwrite my change. And I can't just
> dpkg-reconfigure things to update the interface name, as the package is now
> in a broken state. Seems like this situation could be detected and
> a less severe failure mode implemented.

Hi Dann,

If you look into the minissdpd configuration script (ie:
/var/lib/dpkg/info/minissdpd.config) it does read what's in the
/etc/default/minissdpd configuration file before attempting to configure
the package. Maybe there's a problem in it, and you could try debugging
it by adding a set -x in there? It would help a lot of you could show
the output like that, so we can figure out where the problem is.

Cheers,

Thomas Goirand (zigo)

Bug#969185: src:tiddit: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: tiddit
Version: 2.12.0+dfsg-1
Severity: serious
Control: close -1 2.12.0+dfsg-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 964101

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:tiddit in its
current version in unstable has been trying to migrate for 60 days [2].
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=tiddit




signature.asc
Description: OpenPGP digital signature

Bug#885846: Recurring Atheros Driver Crash

[Leandro Cunha]

Hi, how are you?

Have you tested the firmware-ath9k-htc? And with this firmware it is quite
possible that the problem you reported does not occur and I use and in
stable version work fine and this one here is open source. I use TP Link
board also and it is interesting to report this, although firmware is not a
driver.

Log here

[   18.124396] usb 1-1.4: ath9k_htc: Firmware ath9k_htc/htc_9271-1.dev.0.fw
requested
[   18.124508] usbcore: registered new interface driver ath9k_htc
[   18.326598] usb 1-1.4: firmware: direct-loading firmware
ath9k_htc/htc_9271-1.dev.0.fw
[   18.614208] usb 1-1.4: ath9k_htc: Transferred FW:
ath9k_htc/htc_9271-1.dev.0.fw, size: 51008
[   18.865805] ath9k_htc 1-1.4:1.0: ath9k_htc: HTC initialized with 33
credits
[   19.117742] ath9k_htc 1-1.4:1.0: ath9k_htc: FW Version: 1.4
[   19.117746] ath9k_htc 1-1.4:1.0: FW RMW support: On
[   19.480962] ath9k_htc 1-1.4:1.0 wlxe894f6285298: renamed from wlan0
[ 6074.286308] Modules linked in: ctr ccm aufs(OE) devlink overlay uvcvideo
arc4 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common
videodev ath9k_htc ath9k_common snd_hda_codec_hdmi ath9k_hw
snd_hda_codec_realtek ath mac80211 snd_hda_codec_generic cfg80211 media
snd_hda_intel rfkill snd_hda_codec snd_hda_core snd_hwdep snd_pcm
intel_powerclamp snd_timer coretemp snd intel_ips kvm_intel soundcore
wmi_bmof mei_me iTCO_wdt kvm mei sg irqbypass iTCO_vendor_support
intel_cstate intel_uncore joydev serio_raw evdev pcspkr pcc_cpufreq
nf_log_ipv6 battery ac acpi_cpufreq ip6t_REJECT nf_reject_ipv6 xt_hl
ip6_tables ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4
xt_LOG squashfs nft_limit xt_limit xt_addrtype xt_tcpudp loop xt_conntrack
nft_compat nft_counter nf_conntrack_netbios_ns
[ 6074.287109] Modules linked in: ctr ccm aufs(OE) devlink overlay uvcvideo
arc4 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common
videodev ath9k_htc ath9k_common snd_hda_codec_hdmi ath9k_hw
snd_hda_codec_realtek ath mac80211 snd_hda_codec_generic cfg80211 media
snd_hda_intel rfkill snd_hda_codec snd_hda_core snd_hwdep snd_pcm
intel_powerclamp snd_timer coretemp snd intel_ips kvm_intel soundcore
wmi_bmof mei_me iTCO_wdt kvm mei sg irqbypass iTCO_vendor_support
intel_cstate intel_uncore joydev serio_raw evdev pcspkr pcc_cpufreq
nf_log_ipv6 battery ac acpi_cpufreq ip6t_REJECT nf_reject_ipv6 xt_hl
ip6_tables ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4
xt_LOG squashfs nft_limit xt_limit xt_addrtype xt_tcpudp loop xt_conntrack
nft_compat nft_counter nf_conntrack_netbios_ns
[ 6078.718836] Modules linked in: ctr ccm aufs(OE) devlink overlay uvcvideo
arc4 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common
videodev ath9k_htc ath9k_common snd_hda_codec_hdmi ath9k_hw
snd_hda_codec_realtek ath mac80211 snd_hda_codec_generic cfg80211 media
snd_hda_intel rfkill snd_hda_codec snd_hda_core snd_hwdep snd_pcm
intel_powerclamp snd_timer coretemp snd intel_ips kvm_intel soundcore
wmi_bmof mei_me iTCO_wdt kvm mei sg irqbypass iTCO_vendor_support
intel_cstate intel_uncore joydev serio_raw evdev pcspkr pcc_cpufreq
nf_log_ipv6 battery ac acpi_cpufreq ip6t_REJECT nf_reject_ipv6 xt_hl
ip6_tables ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4
xt_LOG squashfs nft_limit xt_limit xt_addrtype xt_tcpudp loop xt_conntrack
nft_compat nft_counter nf_conntrack_netbios_ns
[10482.893784] Modules linked in: ctr ccm aufs(OE) devlink overlay uvcvideo
arc4 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common
videodev ath9k_htc ath9k_common snd_hda_codec_hdmi ath9k_hw
snd_hda_codec_realtek ath mac80211 snd_hda_codec_generic cfg80211 media
snd_hda_intel rfkill snd_hda_codec snd_hda_core snd_hwdep snd_pcm
intel_powerclamp snd_timer coretemp snd intel_ips kvm_intel soundcore
wmi_bmof mei_me iTCO_wdt kvm mei sg irqbypass iTCO_vendor_support
intel_cstate intel_uncore joydev serio_raw evdev pcspkr pcc_cpufreq
nf_log_ipv6 battery ac acpi_cpufreq ip6t_REJECT nf_reject_ipv6 xt_hl
ip6_tables ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4
xt_LOG squashfs nft_limit xt_limit xt_addrtype xt_tcpudp loop xt_conntrack
nft_compat nft_counter nf_conntrack_netbios_ns
[11277.515444] Modules linked in: ctr ccm aufs(OE) devlink overlay uvcvideo
arc4 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common
videodev ath9k_htc ath9k_common snd_hda_codec_hdmi ath9k_hw
snd_hda_codec_realtek ath mac80211 snd_hda_codec_generic cfg80211 media
snd_hda_intel rfkill snd_hda_codec snd_hda_core snd_hwdep snd_pcm
intel_powerclamp snd_timer coretemp snd intel_ips kvm_intel soundcore
wmi_bmof mei_me iTCO_wdt kvm mei sg irqbypass iTCO_vendor_support
intel_cstate intel_uncore joydev serio_raw evdev pcspkr pcc_cpufreq
nf_log_ipv6 battery ac acpi_cpufreq ip6t_REJECT nf_reject_ipv6 xt_hl
ip6_tables ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4
xt_LOG squashfs nft_limit xt_limit xt_addrtype xt_tcpudp loop xt_conntrack
nft_compat nft_counter nf_conntrack_netbios_ns

Bug#969184: Upgrade fails when interface name has changed

[dann frazier]

Package: minissdpd
Version: 1.5.20190824-1
Severity: normal

I changed out docks for my laptop several months ago, which means my
built-in NIC has a different MAC address, and therefore a different
interface name. minissdpd has stored the old address in the debconf
database. Now when I try to upgrade, it fails (see below). Even correcting
the interface name in /etc/default/minissdpd doesn't fix things, as
the postinst will just overwrite my change. And I can't just
dpkg-reconfigure things to update the interface name, as the package is now
in a broken state. Seems like this situation could be detected and
a less severe failure mode implemented.


Setting up minissdpd (1.5.20190824-1) ...
Job for minissdpd.service failed because the control process exited with error c
ode.
See "systemctl status minissdpd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript minissdpd, action "restart" failed.
● minissdpd.service - keep memory of all UPnP devices that announced themselves
 Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled; vendor pres
et: enabled)
 Active: failed (Result: exit-code) since Fri 2020-08-28 13:15:11 MDT; 5ms a
go
   Docs: man:minissdpd(1)
Process: 77838 ExecCondition=/usr/lib/minissdpd/minissdpd-systemd-wrapper -t
 ${MiniSSDPd_INTERFACE_ADDRESS} (code=exited, status=0/SUCCESS)
Process: 77839 ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper ${Mini
SSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS (code=exited, status=1/FAILURE
)

Aug 28 13:15:11 xps13 minissdpd-systemd-wrapper[77839]: Error parsing address/ma
sk (or interface name) : enx*REDACTED*
Aug 28 13:15:11 xps13 minissdpd-systemd-wrapper[77839]: can't parse 
"enx*REDACTED*
4b8e" as a valid address or interface name
Aug 28 13:15:11 xps13 minissdpd-systemd-wrapper[77839]: Usage: /usr/sbin/minissd
pd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f device] -i  [-i ] ...
Aug 28 13:15:11 xps13 minissdpd-systemd-wrapper[77839]:is either 
an IPv4 address with mask such as
Aug 28 13:15:11 xps13 minissdpd-systemd-wrapper[77839]:   192.168.1.42/255.255.2
55.0, or an interface name such as eth0.
Aug 28 13:15:11 xps13 minissdpd-systemd-wrapper[77839]:   By default, socket wil
l be open as /var/run/minissdpd.sock
Aug 28 13:15:11 xps13 minissdpd-systemd-wrapper[77839]:   and pid written to fil
e /var/run/minissdpd.pid
Aug 28 13:15:11 xps13 systemd[1]: minissdpd.service: Control process exited, cod
e=exited, status=1/FAILURE
Aug 28 13:15:11 xps13 systemd[1]: minissdpd.service: Failed with result 'exit-co
de'.
Aug 28 13:15:11 xps13 systemd[1]: Failed to start keep memory of all UPnP device
s that announced themselves.
dpkg: error processing package minissdpd (--configure):
 installed minissdpd package post-installation script subprocess returned error 
exit status 1
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for systemd (246.2-1) ...
Errors were encountered while processing:
 minissdpd
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Kernel: Linux 5.7.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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 minissdpd depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  init-system-helpers1.58
ii  libc6  2.31-3
ii  libnfnetlink0  1.0.1-3+b1
ii  lsb-base   11.1.0

minissdpd recommends no packages.

minissdpd suggests no packages.

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

-- debconf information excluded

Bug#969091: pdns-backend-mysql: Queries calling stored procedures broken with recent MariaDB/MySQL

[Chris Hofstaedtler]

Hi Xan,

* Xan Charbonnet  [200827 17:42]:
> PowerDNS supports using stored procedures for its backend MySQL queries.  
> However, it seems
> that when the database is MariaDB >= 10.2 (or MySQL >= 5.7), stored 
> procedures fail to work.
> 
> I have tested this on Stretch, using three different PowerDNS versions: 4.0.3 
> (from Stretch),
> 4.1.6 (from Buster), and 4.3.0 (from Bullseye), all compiled on Stretch.  
> They all have the
> same behavior: on MariaDB 10.1, stored procedures work great.  On MariaDB 
> 10.2, calls to
> procedures which return any rows give the error "Could not bind parameters to 
> mysql
> statement".  The various versions of MariaDB came from the MariaDB Debian 
> repositories.
> 
> I have also tried this on a clean Bullseye test system, using the versions of 
> PowerDNS and
> MariaDB which are native to Bullseye.  Same problem.  This is the system 
> where I'm running
> reportbug.

I'm a bit puzzled by this. Debian has an autopkgtest that sets up
MariaDB and pdns-server + pdns-backend-mysql. This (simple) test
appears to work fine:

  https://ci.debian.net/packages/p/pdns/unstable/amd64/

As you can see in this list, even MariaDB 10.4 from experimental
appears to work properly.

There might be some additional info that we are missing here.

Chris

Bug#969183: nvme-cli: bring debhelper compat to 13 and fix build deps

[Dan Streetman]

Package: nvme-cli
Version: 1.12-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy ubuntu-patch

Dear Maintainer,

This patch brings the debhelper-compat version up to 13, since it is currently 
still set to 9 which is deprecated and generates warnings during build.

This also does a 'wrap-and-sort -ast'.

This removes some build deps that are no longer needed:
libudev-dev
python3-nose (technically the tests use python3-nose2, but they aren't run 
during build anyway, because they require nvme hardware)

This adds some build deps there were missing:
pkg-config
uuid-dev

Thanks!
diff -Nru nvme-cli-1.12/debian/compat nvme-cli-1.12/debian/compat
--- nvme-cli-1.12/debian/compat 2016-01-07 12:34:55.0 -0500
+++ nvme-cli-1.12/debian/compat 1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-9
diff -Nru nvme-cli-1.12/debian/control nvme-cli-1.12/debian/control
--- nvme-cli-1.12/debian/control2019-11-23 08:40:09.0 -0500
+++ nvme-cli-1.12/debian/control2020-08-28 12:24:46.0 -0400
@@ -3,12 +3,19 @@
 Section: admin
 Priority: optional
 Standards-Version: 4.1.1
-Build-Depends: debhelper (>= 9), libudev-dev, python3-nose, pci.ids, 
uuid-runtime
+Build-Depends:
+ debhelper-compat (= 13),
+ pci.ids,
+ pkg-config,
+ uuid-dev,
+ uuid-runtime,
 Homepage: https://github.com/linux-nvme/nvme-cli
 
 Package: nvme-cli
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends:
+ ${misc:Depends},
+ ${shlibs:Depends},
 Description: userspace tooling to control NVMe drives
  NVMe is a fast, scalable, direct attached storage interface, accessing
  solid state drives through PCIe.

Bug#885846: Recurring Atheros Driver Crash

[M. Halverson]

Package: firmware-atheros
Version: 20190114-2
Followup-For: Bug #885846

Dear Maintainer,

I am seeing a similar crash as reported in bug 885846, using wireless driver
ATH9k with a TP-Link TL-WN851ND. The system freezes during moderate to high
wifi activity, such as streaming or running speedtest utilities, and is very
repeatable. At best, the system requires a hard reset. At worst, the crash
corrupts the BIOS, forcing BIOS reconfiguration. This issue affects distros
that use kernels common to Ubuntu 20.04, Mint 20/LMDE, etc. It does not occur
with older distros (e.g. Mint 17, Ubuntu 18.04 and its derivatives), or with
Windows.

Using modprobe I attempted to replace the ATH driver package provided with Mint
LMDE/Ubuntu 20 with that from Mint 17, however the older driver package is
apparently incompatible with the new kernel(s) and failed to load. I also
attempted to replace the ATH9k driver with ndiswrapper and the 64 bit driver
provided in Windows XP, but modprobe would hang when attempting to load
ndiswrapper. I also disabled wireless N in both the adapter settings, and the
router itself, to slow the data rate (i.e. I ran the adapter in "Legacy" mode).
The system still crashes; it just takes a while longer. Likewise, the crash
occurs whether security is enabled or disabled, and does not appear related to
any other hardware conflicts (the crash occurs whether using Nouveau or Nvidia
drivers, plus the wireless adapter is only device installed in a PCI slot).



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

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

firmware-atheros depends on no packages.

firmware-atheros recommends no packages.

Versions of packages firmware-atheros suggests:
ii  initramfs-tools  0.133+deb10u1

-- no debconf information

*** /mnt/Storage/common files/ath9k/ath9k wireless driver crashing Mint 20 et
al.txt
Problem:
The ath9k wireless adapter driver appears to be "broken". Affects Mint 20
Cinnamon & LMDE, Ubuntu & Xubuntu 20.04.0 &.1 (I believe they all use the
latest kernels). It is NOT "broken" when using Mint 17.3 or Windows 7. (Adapter
make and model: TP-Link TL-WN851nd)

The symptoms:
When running speedtest utils (speedtest.net, xfinityspeedtest.org, etc) OR
streaming audio OR video (YouTubeTV) in Chrome OR Firefox while connected to
wifi, the mouse and keyboard will freeze, plus an audible static ("white
noise") will often come from the speakers. Sometimes speedtest or whatever was
being streamed at the time will continue to run for several seconds, even
though the keyboard and mouse are frozen. Othertimes, everything freezes at the
same time. At best it is necessary to perform a hard shutdown and reboot. At
worst, the crash corrupts the BIOS (about 50% of the time...) and I have to
reconfigure the BIOS before I can use the PC, and/or the OS/boot configuration
will be corrupted and I have to use "Boot Repair" and/or restore a previously
saved backup image before the PC can be used. This problem has been 100%
repeatable.

What I have tried:
1) Updated the firmware-atheros to the newest version (20200619-1). The
wireless still froze.

2) Using "Network Settings" I disabled wireless N on the adapter PLUS I
disabled wireless N on my ASUS RT-AC66U_B1 router (i.e. I used 802.11b or
802.11g Legacy mode only), and re-ran speedtest, but the system still crashed.
The only difference was that it took longer; I presume due to the slower
download and upload speeds.

3) Booting from a live USB (both Mint 20 and LMDE), I connected to wifi and ran
speedtest. The system still crashed. (Booting the live USB in UEFI or Legacy
BIOS mode made no difference.)

4) I attempted to replace the ath9k driver that comes with Mint 20 with the
ath9k driver in Mint 17.3, but it appears that the drivers are signed in some
fashion, preventing older drivers from being used with the newer kernels.

5) Tweeking the wifi, proxy, IPv4, and IPv6 settings from their defaults made
no difference.

6) The system does not crash when both wired and wifi connections are enabled.
I presume this is because the wired connection is preferred (has "priority").

7) The output from "lspci -b -vvv" shows that mint 17.3 is using the same
driver name (ath9k) and interrupt as mint 20.04.

8) Although I have tested this issue many times, only once was a crash log
generated, and it was lost after a subsequent crash. Sorry...

9) Thinking the crash may be related to downloads only, I ran "testmy.net
/upload" to skip the download part of the speedtest, and the system still
crashed. (The problem ***may be*** related to 

Bug#959387: [Re] paraview-dev: missing cmake vtk modules in the dev package, cannot use

[Anton Gladky]

Hello Jakob,

thanks for work on this huge and difficult packages! Just to let you know,
i am
going to start to work on recently released VTK9. We can coordinate our work
and to try to solve this problem, if it is possible.

Best regards

Anton


Am Fr., 28. Aug. 2020 um 12:09 Uhr schrieb Jakob Meng :

> PPPS:
>
> ParaView installs its Python modules as well as all the VTK Python
> modules as part of its CMake install process. If python3-vtk8 [1] ever
> enters Debian this might cause file collisions, as both python3-paraview
> and python3-vtk8 install files to the same locations and hence cannot be
> co-installed. So either we skip installing VTK Python modules during
> ParaView install or we install those ParaView's VTK Python modules to a
> different location by setting e.g. VTK_PYTHON_SITE_PACKAGES_SUFFIX. When
> skipping VTK Python module install, then we have to make sure that all
> VTK-related files in ParaView and VTK packages do match exactly and have
> the same patches applied. Else Python, ParaView or its Python modules
> might crash or even worse cause silent data and memory corruption bugs.
>
> Just calling 'rm -fr debian/tmp/usr/lib/python3*/dist-packages/vtk*' in
> ParaView's debian/rules is not a proper workaround. ParaView 5.7 from
> Debian Sid uses a development version of VTK8 (not far from VTK9
> release?) [4], while Debian's dedicated VTK8 package [1] is at 8.2, so
> both VTK versions have many differences.
>
> ParaView has CMake flags to build with an external VTK install [6], but
> this is not supported at least in ParaView 5.7.0 [7].
>
> BTW, these incompatibilities affect older Debian releases as well. For
> example, install both packages 'paraview-python' [2] and 'python3-vtk7'
> [3] on Debian 10 (Buster), run pvpython and enter 'import vtk'. ParaView
> Python will crash. So always remember to enter 'import paraview.vtk' on
> Debian and Ubuntu [5].
>
> To avoid these bugs, my reworked ParaView package does not allow
> parallel installs of python3-vtk7 or python3-vtk8 [8]. Both paraview-dev
> and python3-paraview install a lot (all?) of VTK's headers, libraries
> and Python modules anyway.
>
> Ref.:
> [1] https://salsa.debian.org/science-team/vtk8/
> [2] https://packages.debian.org/buster/paraview-python
> [3] https://packages.debian.org/buster/python3-vtk7
> [4]
>
> https://salsa.debian.org/science-team/paraview/-/blob/master/VTK/CMake/vtkVersion.cmake
> [5] https://blog.kitware.com/import-vtk-or-import-paraview-vtk/
> [6] https://github.com/Kitware/ParaView/blob/v5.8.1/CMakeLists.txt#L218
> [7] https://github.com/Kitware/ParaView/blob/v5.7.0/CMakeLists.txt#L290
> [8]
>
> https://git.inf.h-brs.de/jmeng2m/debian-package-paraview/-/blob/debian/5.7.0+ds.1-3/debian/control#L172
>
>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#829444: Accepting / adopting DEP-14

[Guido Günther]

Hi,
On Tue, Aug 25, 2020 at 05:52:47PM +0300, Otto Kekäläinen wrote:
> Hello!
> 
> Finalizing and publishing DEP-14 would be nice.
> 
> I have been using git-buildpackage for all of my packages for many years
> already, and thus been automatically following these guidelines as they are
> followed by git-buildpackage.
> 
> There are only two diversions I've noted:
> - in git-buildpackage default master is 'master', not DEP-14 'debian/master'
> - git-buildpackage in my use has the branch 'pristine-tar' which DEP-14
> does not cover

Thanks for the reminder. Defaulting to `debian/master` should
certainly be flipped for bullseye (and that one is easy where switching
from upstream to upsteam/latest is harder) since if the branch exists it
can't easily become a directory).
Cheers,
 -- Guido

Bug#969182: debhelper: compat 11 adds install --strip-program=true which generates annoying warnings during build

[Dan Streetman]

Package: debhelper
Version: 12.10ubuntu1
Severity: minor

Dear Maintainer,

The debhelper compat level 11 adds the --strip-program=true parameter to calls 
to install,
to prevent install-time stripping (debian bug 844077).

However, if the upstream Makefile is calling install without -s, the addition 
of --strip-program=true
causes annoying/confusing warning messages to be printed many times during 
build, e.g.:

install: WARNING: ignoring --strip-program option as -s option was not specified

Bug#969137: [Pkg-phototools-devel] Bug#969137: darktable: Histogram not shown

[David Bremner]

Control: severity -1 wishlist
Control: retitle -1 darktable: use default values for empty config settings

Fabián Inostroza  writes:

> I found the issue (with the help of reddit), it was related to the
> configuration file. The height of the histogram entry was empty on the
> darktablerc file, like this:
> plugins/darkroom/histogram/height=
>
> I put some value (200), opened darktable and the histogram was shown.
> Then I tried renaming the darktablerc file and letting darktable
> recreate it but it also had the empty histogram height.

The only way I can reproduce that is if darktable is open while renaming
the file.

> Anyway, maybe darktable should use a good default values for empty
> entries, at least for the height of the histogram.

OK, I've retitled the bug accordingly. 

> I was using a previous version of darktable, the one that was on the
> repositories, maybe that confused some settings.

I'm not sure what you mean here. Are you upgrading from a previous
version in Debian, or something else? If so, what version.

Bug#969058: iptables in buster-backports requires netbase >= 6.0 which is not present in archive

[Johan Fleury]

>> this bug utterly hosed the systems i am working on (fortunately a dev 

>> network)
>>
> If in a rush, one could simply install netbase from testing. It should be a
> simple operation.

Or install a previous version that may still be in apt cache.

> This costs thousand of €€€ (EURs) in engineering time. Would you volunteer to 
> do
> all the work you are suggesting should be done? Or fund with money for other
> folks to do so?
>
> Please, be mindful, Debian is a community project. People do work here mostly 
> on
> a volunteer capacity. While I may understand your frustration, this kind of
> yelling you are doing might destroy people's motivation in communities.

Totally agree, and I wanted to thank you for the work you’re doing on 
backporting iptables, it’s appreciated and really helpful (for instance, 
without this I wouldn’t be able to run Kubernetes on Buster).

>> This makes `iptables` un-upgradable on my system, and even worse, it
>> lead to it being removed an I cannot install it anymore:
>>
> this is because the apt pin config you have for the package... The config 
> tells
> apt to only install the package from buster-bpo, but that package is
> uninstallable, therefore the deadlock.

Am I doing something wrong here? I really need iptables to be installed from 
backports and this is the only way I found to do so (appart from running `apt 
install -t buster-backports iptables` by hand)

--
Johan Fleury



signature.asc
Description: OpenPGP digital signature

Bug#969180: RFS: facerec/1.0 [ITP] -- A Face Authentication system for ubuntu

[Rushabh Vasani]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: facerec
* Version: 1.0
* Upstream Author: Rushabh Vasani 
* URL: https://github.com/rushabh-v/linux_face_unlock
* License : GPL-3.0 License

* Vcs: https://github.com/rushabh-v/linux_face_unlock
* Section: devel (Python)

It builds those binary packages:
Facerec - Linux face unlock

Facerec - Face authentication system for Ubuntu Linux that works while
logging in, running "sudo" commands, etc. It is having a user-friendly CLI
and it is highly optimized and secure.

To access further information about this package, please visit the
following URL:
https://github.com/rushabh-v/linux_face_unlock

Alternatively, one can download and install the deb package with the
following steps:

   1. *Install prerequisites:*

sudo apt-get install python3-pip \
python3-opencv \
python3-setuptools \
python-execnet \
cmake \
libatlas-base-dev \
build-essential


   1. *Download the deb package:*

wget https://rushabh-v.github.io/facerec_1.0_all.deb


   1. *Install facerec:*

sudo dpkg -i facerec_1.0_all.deb

Command Line Interface
CommandDescription
facerec new Add a new root face.
facerec enable Enable facerec (Enable back after disabling)
facerec disable Temporarily disable facerec, preserving the setup.
facerec remove Completely remove facerec and with all the root faces.
facerec --help help for Facerec-CLI
changelog:
  facerec (1.0); urgency=normal
* Initial release.

Best Regards,
Rushabh Vasani

Bug#969179: iwlwifi: firmware error results in extremely poor connection until reboot

[Josh Triplett]

Source: linux
Version: 5.7.17-1
Severity: normal
X-Debbugs-Cc: j...@joshtriplett.org

I get errors like the following regularly, particularly when on video
calls; as soon as the error happens, most or all packets stop going
through, and the connection becomes extremely unreliable.

Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: Queue 11 is active on fifo 1 
and stuck for 1 ms. SW [126, 95] HW [126, 95] FH TRB=0x0c010b08d
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: Microcode SW error detected.  
Restarting 0x200.
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: Start IWL Error Log Dump:
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: Status: 0x0040, count: 6
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: Loaded firmware version: 
36.79ff3ccf.0 8265-36.ucode
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0084 | 
NMI_INTERRUPT_UNKNOWN   
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x22E0 | trm_hw_status0
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | trm_hw_status1
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x000248FC | branchlink2
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0003A872 | interruptlink1
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x083E | interruptlink2
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | data1
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0080 | data2
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0783 | data3
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x2D800D81 | beacon time
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0xA808AA7D | tsf low
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0078 | tsf hi
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | time gp1
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x346CA182 | time gp2
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0001 | uCode revision type
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0024 | uCode version major
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x79FF3CCF | uCode version minor
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0230 | hw version
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x00C89000 | board version
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0A15001C | hcmd
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x000A | isr0
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0080 | isr1
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0800180A | isr2
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x00401480 | isr3
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | isr4
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0B7E001C | last cmd Id
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | wait_event
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0xCF5A | l2p_control
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x8020 | l2p_duration
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x0003 | l2p_mhvalid
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x00F7 | l2p_addr_match
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x000D | lmpm_pmg_sel
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x02052035 | timestamp
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x00341828 | flow_handler
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | ADVANCED_SYSASSERT
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac branchlink1
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac branchlink2
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac interruptlink1
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac interruptlink2
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac data1
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac data2
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac data3
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac major
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | umac minor
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | frame pointer
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | stack pointer
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | last host cmd
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x | isr status reg
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: Fseq Registers:
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x22BC1126 | FSEQ_ERROR_CODE
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x9E626500 | 
FSEQ_TOP_INIT_VERSION
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x118C2230 | 
FSEQ_CNVIO_INIT_VERSION
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0xA10B | FSEQ_OTP_VERSION
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0x57DD1850 | 
FSEQ_TOP_CONTENT_VERSION
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0xC66901A4 | FSEQ_ALIVE_TOKEN
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0xEAC96D6C | FSEQ_CNVI_ID
Aug 28 09:31:38 s kernel: iwlwifi :04:00.0: 0xE4E57887 | 

Bug#969181: RFP: yubikey-agent -- yubikey-agent is a seamless ssh-agent for YubiKeys.

[Andrew Dorney]

Package: wnpp
Severity: wishlist

yubikey-agent is a seamless ssh-agent for YubiKeys.

   - *Easy to use.* A one-command setup, one environment variable, and it
   just runs in the background.
   - *Indestructible.* Tolerates unplugging, sleep, and suspend. Never
   needs restarting.
   - *Compatible.* Provides a public key that works with all services and
   servers.
   - *Secure.* The key is generated on the YubiKey and can't be extracted.
   Every session requires the PIN, every login requires a touch. Setup takes
   care of PUK and management key.

Written in pure Go, it's based on github.com/go-piv/piv-go and
golang.org/x/crypto/ssh.

Source code at: https://github.com/FiloSottile/yubikey-agent

License: BSD 3-Clause see
https://github.com/FiloSottile/yubikey-agent/blob/master/LICENSE

Copyright: Copyright 2020 Google LLC

Bug#957803: sjeng: diff for NMU version 11.2-8.1

[Sudip Mukherjee]

Control: tags 957803 + patch
Control: tags 957803 + pending

Dear maintainer,

I've prepared an NMU for sjeng (versioned as 11.2-8.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -u sjeng-11.2/debian/changelog sjeng-11.2/debian/changelog
--- sjeng-11.2/debian/changelog
+++ sjeng-11.2/debian/changelog
@@ -1,3 +1,10 @@
+sjeng (11.2-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957803)
+
+ -- Sudip Mukherjee   Fri, 28 Aug 2020 17:28:50 
+0100
+
 sjeng (11.2-8) unstable; urgency=low
 
   * Apply a patch to satisfy the xboard protocol related to SAN
diff -u sjeng-11.2/debian/patches/series sjeng-11.2/debian/patches/series
--- sjeng-11.2/debian/patches/series
+++ sjeng-11.2/debian/patches/series
@@ -20,0 +21 @@
+gcc-10.patch
only in patch2:
unchanged:
--- sjeng-11.2.orig/debian/patches/gcc-10.patch
+++ sjeng-11.2/debian/patches/gcc-10.patch
@@ -0,0 +1,28 @@
+--- a/extvars.h
 b/extvars.h
+@@ -129,10 +129,10 @@ extern int numb_moves;
+ 
+ extern int phase;
+ 
+-FILE *lrn_standard;
+-FILE *lrn_zh;
+-FILE *lrn_suicide;
+-FILE *lrn_losers;
++extern FILE *lrn_standard;
++extern FILE *lrn_zh;
++extern FILE *lrn_suicide;
++extern FILE *lrn_losers;
+ extern int bestmovenum;
+ 
+ extern int ugly_ep_hack;
+--- a/proof.c
 b/proof.c
+@@ -48,7 +48,7 @@ long frees;
+ int iters;
+ int forwards;
+ int maxply;
+-int ply;
++extern int ply;
+ int pn_time;
+ move_s pn_move;
+ move_s pn_saver;

Bug#969149: possible fix

[Paolo Greppi]

Please note that a similar problem has been fixed by the fcml maintainer:
https://bugs.debian.org/969148

Paolo

Bug#969148: fcml: FTBFS with doxygen 1.8.19

[Paolo Greppi]

Hi Stephen, 

Il 28/08/20 12:22, Stephen Kitt ha scritto:
> Hi Paolo,
> 
>> ...
> 
> After building the package with doxygen from experimental, I get
> 
> $ find . -name doxygen.\*
> ./docs/doxygen/doxygen.stamp
> ./docs/doxygen/html/doxygen.css
> ./docs/doxygen/html/doxygen.svg
> ./docs/doxygen/latex/doxygen.sty
> ./debian/libfcml-doc/usr/share/doc/libfcml-doc/html/doxygen.css
> ./debian/tmp/usr/share/doc/fcml/html/doxygen.css
> ./debian/tmp/usr/share/doc/fcml/html/doxygen.svg
> 
> dh_doxygen is invoked with -plibfcml-doc so this happens because the SVG file
> isn’t installed there. Fixing that allows the build to complete.
> 
> Regards,
> 
> Stephen

Thanks for the research and quick fix. This will be helpful to bug 969149 which 
I'll notify.

Paolo

Bug#969169: cups: Driverless printing not working

[Brian Potkin]

On Fri 28 Aug 2020 at 18:16:41 +0200, Kurt Roeckx wrote:

> On Fri, Aug 28, 2020 at 04:55:56PM +0100, Brian Potkin wrote:
> > 
> > ipp:/... is another URI for the printer. Execute
> > 
> >   lpadmin -p  -v  -E -m everywhere
> 
> # lpadmin -p Brother_HL_L2370DN_series -v 
> ipp://BRN3C2AF4B40D45.local:631/ipp/print -E -m everywhere
> lpadmin: Unable to connect to "BRN3C2AF4B40D45.local:631": Name or service 
> not known
> # ping BRN3C2AF4B40D45.local
> ping: BRN3C2AF4B40D45.local: Name or service not known
> 
> I do not have nss-mdns installed, nor set up. But avahi-browse
> clearly knows that correct IP address.

You have a network issue, not a printing issue. Try

  ipp://192.168.0.154/ipp/print

as the URI.

I have libnss-mdns installed

Cheers,

Brian.

Bug#969169: cups: Driverless printing not working

[Kurt Roeckx]

On Fri, Aug 28, 2020 at 06:16:41PM +0200, Kurt Roeckx wrote:
> On Fri, Aug 28, 2020 at 04:55:56PM +0100, Brian Potkin wrote:
> > 
> > ipp:/... is another URI for the printer. Execute
> > 
> >   lpadmin -p  -v  -E -m everywhere
> 
> # lpadmin -p Brother_HL_L2370DN_series -v 
> ipp://BRN3C2AF4B40D45.local:631/ipp/print -E -m everywhere
> lpadmin: Unable to connect to "BRN3C2AF4B40D45.local:631": Name or service 
> not known
> # ping BRN3C2AF4B40D45.local
> ping: BRN3C2AF4B40D45.local: Name or service not known
> 
> I do not have nss-mdns installed, nor set up. But avahi-browse
> clearly knows that correct IP address.

If I strace it, I only see an attemp to resolve it using DNS,
while something like avahi-resolve-host-name actually seems to
talk to the avahi daemon.

lpadmin is linked to avahi-client, so I expect it to try to use
it. It clearly knows how to use it to locate the printer.


Kurt

Bug#969178: override: uucpsend:news/optional

[Baptiste BEAUPLAT]

Package: ftp.debian.org
Severity: normal

Hi,

To comply with the policy 2.5 Priorities, I've changed uucpsend priority
from "extra" to "optional".

Please update accordingly.

Thanks,
-- 
Baptiste BEAUPLAT - lyknode



signature.asc
Description: OpenPGP digital signature

Bug#962651: Version 0.98 released

[Rob Allen]

Upstream has now released version 0.98 of rst2pdf which removes the pdfrw 
dependency.

* https://github.com/rst2pdf/rst2pdf/releases/tag/0.98 

* https://pypi.org/project/rst2pdf/0.98/ 


Regards,

Rob
-- 
Rob Allen
rst2pdf Project Lead
https://rst2pdf.org 

Bug#969169: cups: Driverless printing not working

[Kurt Roeckx]

On Fri, Aug 28, 2020 at 04:55:56PM +0100, Brian Potkin wrote:
> 
> ipp:/... is another URI for the printer. Execute
> 
>   lpadmin -p  -v  -E -m everywhere

# lpadmin -p Brother_HL_L2370DN_series -v 
ipp://BRN3C2AF4B40D45.local:631/ipp/print -E -m everywhere
lpadmin: Unable to connect to "BRN3C2AF4B40D45.local:631": Name or service not 
known
# ping BRN3C2AF4B40D45.local
ping: BRN3C2AF4B40D45.local: Name or service not known

I do not have nss-mdns installed, nor set up. But avahi-browse
clearly knows that correct IP address.


Kurt

Bug#969177: debmake: cannot create deb for nodejs modeule

[Pirate Praveen]

package: debmake
version: 4.3.2-1
severity: grave

Using pretty-ms node module as example. debmake 4.3.2-1 worked.

(debian-sid)pravi@ilvala2:~/packaging/node-pretty-ms-7.0.0$ debmake
I: set parameters
I: sanity check of parameters
I: pkg="node-pretty-ms", ver="7.0.0", rev="1"
I: *** start packaging in "node-pretty-ms-7.0.0". ***
I: provide node-pretty-ms_7.0.0.orig.tar.gz for non-native Debian 
package

I: pwd = "/home/pravi/packaging"
I: Use existing "node-pretty-ms_7.0.0.orig.tar.gz" as upstream tarball
I: pwd = "/home/pravi/packaging/node-pretty-ms-7.0.0"
I: parse binary package settings:
I: binary package=node-pretty-ms Type=nodejs / Arch=all M-A=foreign
I: analyze the source tree
I: build_type = nodejs
I: scan source for copyright+license text and file extensions
I: 17 %, ext = javascript
I: 17 %, ext = yml
I: 17 %, ext = ts
I: 8 %, ext = gitattributes
I: 8 %, ext = md
I: 8 %, ext = npmrc
I: 8 %, ext = json
I: 8 %, ext = gitignore
I: 8 %, ext = editorconfig
I: check_all_licenses
I: .
I: check_all_licenses completed for 13 files.
I: bunch_all_licenses
I: format_all_licenses
I: make debian/* template files
I: single binary package
I: debmake -x "1" ...
Traceback (most recent call last):
 File "/usr/bin/debmake", line 28, in 
   debmake.main()
 File "/usr/lib/python3/dist-packages/debmake/__init__.py", line 271, 
in main

   debmake.debian.debian(para)
 File "/usr/lib/python3/dist-packages/debmake/debian.py", line 159, in 
debian
   "debian/control", debmake.control.control(para), 
tutorial=para["tutorial"]
 File "/usr/lib/python3/dist-packages/debmake/control.py", line 60, in 
control

   desc_long_type = debmake.read.read(
 File "/usr/lib/python3/dist-packages/debmake/read.py", line 30, in 
read

   with open(file, mode="r", encoding="utf-8") as f:
FileNotFoundError: [Errno 2] No such file or directory: 
'/usr/share/debmake/extra0desc_long/nodejs'

Bug#969169: cups: Driverless printing not working

[Brian Potkin]

On Fri 28 Aug 2020 at 17:12:21 +0200, Kurt Roeckx wrote:

> On Fri, Aug 28, 2020 at 03:23:23PM +0100, Brian Potkin wrote:
> > Thank you for your report, Kurt. Please provide the outputs of
> > 
> 
> =   eth0 IPv4 Brother HL-L2370DN series Internet Printer  
>local
>hostname = [BRN3C2AF4B40D45.local]
>address = [192.168.0.154]
>port = [631]
>txt = ["mopria-certified=1.3" "print_wfds=T" 
> "UUID=e3248000-80ce-11db-8000-3c2af4b40d45" "PaperMax=legal-A4" 
> "kind=document,envelope,label,postcard" 
> "URF=W8,CP1,IS4-1,MT1-3-4-5-8,OB10,PQ3-4-5,RS300-600-1200,V1.4,DM1" "TBCP=F" 
> "Transparent=T" "Binary=T" "PaperCustom=T" "Scan=F" "Fax=F" "Duplex=T" 
> "Copies=T" "Color=F" "usb_CMD=PJL,PCL,PCLXL,URF" "usb_MDL=HL-L2370DN series" 
> "usb_MFG=Brother" "priority=25" 
> "adminurl=http://BRN3C2AF4B40D45.local./net/net/airprint.html; 
> "product=(Brother HL-L2370DN series)" "ty=Brother HL-L2370DN series" "note=" 
> "rp=ipp/print" "pdl=application/octet-stream,image/urf,image/pwg-raster" 
> "qtotal=1" "txtvers=1"]

The URF= key indicates an AirPrint printer. The pdl= key has image/urf
in it. The printing system can easily handle printing to the HL-L2370DN
if it is an IPP device.

> intrepid:~#   ippfind -T 5
> ipp://BRN3C2AF4B40D45.local:631/ipp/print

The HL-L2370DN is an IPP device. The second line is a URI for it.

> intrepid:~#   lpstat -l -e
> Brother_HL_L2370DN_series network none 
> ipp://Brother%20HL-L2370DN%20series._ipp._tcp.local/

Brother_HL_L2370DN_series is the destination used with a CUPS temporary
queue. See

   https://wiki.debian.org/CUPSDriverlessPrinting#tempq

> intrepid:~#   lpinfo -v
> network ipp://Brother%20HL-L2370DN%20series._ipp._tcp.local/

ipp:/... is another URI for the printer. Execute

  lpadmin -p  -v  -E -m everywhere

and test printing with

  lp -d  /etc/nsswitch.conf 

> For the Epson printer, I now see 3 in a print dialog, while there is
> only 1 in the cups admin, and at least one of them doesn't work.

Probably the final bullet point in the above link and nothing to do with
the CUPS printing system.

Cheers,

Brian.

Bug#969176: ITP: libdsiutils-java -- Java library of statistical and text data handling tools

[Pierre Gruet]

Package: wnpp
Severity: wishlist
Owner: Debian Java team 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-j...@lists.debian.org

* Package name: libdsiutils-java
  Version : 2.6.6
  Upstream Author : Sebastiano Vigna
* URL : http://dsiutils.di.unimi.it
* License : LGPL-3
  Programming Lang: Java
  Description : Java library of statistical and text data handling tools

The library contains:
  - Implementations of pseudorandom number generators;
  - BitVector and its implementations -- a high-performance but flexible set of
  bit vector classes;
  - A it.unimi.dsi.compression package containing codecs for several types of
  encodings;
  - ProgressLogger, a flexible logger with statistics marking the progress of
  the classes that are used and that require hours of computation;
  - ObjectParser, a class making it easy to specify complex objects on the
  command line;
  - MutableString, an alternative to the immutable Java String class;
  - The I/O package, containing fast version of several classes existing in
  java.io, many useful classes to read easily text data
  (e.g., FileLinesCollection), bit streams, classes providing large-size memory
  mapping such as ByteBufferInputStream, and OfflineIterable -- the easy & fast
  way to store large sequences of objects on disk and iterate on them;
  - The it.unimi.dsi.util package, containing pseudorandom number generators,
  tries, immutable prefix maps, Bloom filters, a very comfortable Properties
  class and more;
  - The it.unimi.dsi.stat package, containing a lightweight class for computing
  basic statistics and an arbitrary-precision implementation of the Jackknife
  method;
  - Lots of utility methods in Util;
  - Big versions of I/O and utility classes in it.unimi.dsi.big.io and
  it.unimi.dsi.big.util;
  - The BulletParser, used to parse HTML and XML.

This package is needed as a predependency of igv, which the Debian med team
would like to package out of non-free. I am personnally aiming at this.
The package will be maintained in the Debian Java team.

Bug#969137: [Pkg-phototools-devel] Bug#969137: darktable: Histogram not shown

[Fabián Inostroza]

Hi,

I found the issue (with the help of reddit), it was related to the
configuration file. The height of the histogram entry was empty on the
darktablerc file, like this:
plugins/darkroom/histogram/height=

I put some value (200), opened darktable and the histogram was shown.
Then I tried renaming the darktablerc file and letting darktable
recreate it but it also had the empty histogram height.
Tried renaming the whole config folder and the darktablerc file was
recreated correctly. The weird thing is that after restoring
the old configuration folder darktable recreates correctly the darktablerc file.

Anyway, maybe darktable should use a good default values for empty
entries, at least for the height of the histogram.
I was using a previous version of darktable, the one that was on the
repositories, maybe that confused some settings.

Regards.

El vie., 28 ago. 2020 a las 6:40, David Bremner () escribió:
>
> Control: tag -1 unreproducible
>
> Fabian Inostroza  writes:
>
> > Package: darktable
> > Version: 3.2.1-2+b1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > When working on a image in darktable the histogram is not shown, a user 
> > suggested
> > I try Ctrl+Shift+H and the only change I see is a very thin dark line in 
> > the place
> > where the histogram should be.
> >
>
> Hi Fabian;
>
> Sorry I can't reproduce that. Ctrl-shift-h does indeed toggle it for me,
> and the histogram is displayed at startup
>
> 1. Does it happen on all images, or just certain ones?
> 2. As you might know, the histogram is only displayed in darkroom mode.
> 3. One thing to try is to move your darktable configuration out of the way
>(in ~/.config/darktable)
>

Bug#882145: asterisk: pjsip show history causes segmentation fault

[Bernhard Schmidt]

Control: forward -1 https://issues.asterisk.org/jira/browse/ASTERISK-28854

Am 14.08.20 um 09:47 schrieb Benoit Panizzon:

Hi,

>> Benoit, are you using IPv6? If yes,
>> https://issues.asterisk.org/jira/browse/ASTERISK-28854 could be the
>> culprit.
> 
> Well, why should I use that old legacy phased out ipv4 protocol? :-)

I agree :-)

I have verified the patch and it works fine. Stable upload fixing this
bug has been requested.

Bernhard

Bug#963689: Acknowledgement (linux-image-5.6.0-2-powerpc: stuck at 'pmac32_cpufreq' when booting)

[Giuseppe Sacco]

Hello,
it seems I found the problem as explained in the upstream bug I
opened[1]. Waiting for a fix, a possibile workaround proposed by kernel
developers is to unset CONFIG_VMAP_STACK.

Is it possible to change this configuration option for powerpc (32bit)
architecture?

Thank you,
Giuseppe

[1]https://github.com/linuxppc/issues/issues/326

Bug#969169: cups: Driverless printing not working

[Kurt Roeckx]

On Fri, Aug 28, 2020 at 03:23:23PM +0100, Brian Potkin wrote:
> Thank you for your report, Kurt. Please provide the outputs of
> 

intrepid:~#   avahi-browse -rt _ipp._tcp
+   eth0 IPv6 EPSON WF-7515 Series @ intrepid   Internet Printer
 local
+   eth0 IPv6 Brother HL-L2370DN series Internet Printer
 local
+   eth0 IPv4 EPSON WF-7515 Series @ intrepid   Internet Printer
 local
+   eth0 IPv4 Brother HL-L2370DN series Internet Printer
 local
+   eth0 IPv4 EPSON WF-7515 Series  Internet Printer
 local
+ lo IPv4 EPSON WF-7515 Series @ intrepid   Internet Printer
 local
=   eth0 IPv6 EPSON WF-7515 Series @ intrepid   Internet Printer
 local
   hostname = [intrepid.local]
   address = [:::::::]
   port = [631]
   txt = ["printer-type=0xB00E" "printer-state=3" "Color=T" "TLS=1.2" 
"UUID=65e68070-4dc2-3d2b-40aa-5f840c51c6d8" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
 "product=(EPSON WF-7510 Series)" "priority=0" "note=Kurt" 
"adminurl=https://intrepid.local.:631/printers/EPSON_WF-7515; "ty=Epson WF-7515 
Series - epson-inkjet-printer 1.0.0-1lsb3.2 (Seiko Epson Corporation LSB 3.2)" 
"rp=printers/EPSON_WF-7515" "qtotal=1" "txtvers=1"]
= lo IPv4 EPSON WF-7515 Series @ intrepid   Internet Printer
 local
   hostname = [intrepid.local]
   address = [127.0.0.1]
   port = [631]
   txt = ["printer-type=0xB00E" "printer-state=3" "Color=T" "TLS=1.2" 
"UUID=65e68070-4dc2-3d2b-40aa-5f840c51c6d8" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
 "product=(EPSON WF-7510 Series)" "priority=0" "note=Kurt" 
"adminurl=https://intrepid.local.:631/printers/EPSON_WF-7515; "ty=Epson WF-7515 
Series - epson-inkjet-printer 1.0.0-1lsb3.2 (Seiko Epson Corporation LSB 3.2)" 
"rp=printers/EPSON_WF-7515" "qtotal=1" "txtvers=1"]
=   eth0 IPv4 EPSON WF-7515 Series @ intrepid   Internet Printer
 local
   hostname = [intrepid.local]
   address = [192.168.0.2]
   port = [631]
   txt = ["printer-type=0xB00E" "printer-state=3" "Color=T" "TLS=1.2" 
"UUID=65e68070-4dc2-3d2b-40aa-5f840c51c6d8" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
 "product=(EPSON WF-7510 Series)" "priority=0" "note=Kurt" 
"adminurl=https://intrepid.local.:631/printers/EPSON_WF-7515; "ty=Epson WF-7515 
Series - epson-inkjet-printer 1.0.0-1lsb3.2 (Seiko Epson Corporation LSB 3.2)" 
"rp=printers/EPSON_WF-7515" "qtotal=1" "txtvers=1"]
=   eth0 IPv4 Brother HL-L2370DN series Internet Printer
 local
   hostname = [BRN3C2AF4B40D45.local]
   address = [192.168.0.154]
   port = [631]
   txt = ["mopria-certified=1.3" "print_wfds=T" 
"UUID=e3248000-80ce-11db-8000-3c2af4b40d45" "PaperMax=legal-A4" 
"kind=document,envelope,label,postcard" 
"URF=W8,CP1,IS4-1,MT1-3-4-5-8,OB10,PQ3-4-5,RS300-600-1200,V1.4,DM1" "TBCP=F" 
"Transparent=T" "Binary=T" "PaperCustom=T" "Scan=F" "Fax=F" "Duplex=T" 
"Copies=T" "Color=F" "usb_CMD=PJL,PCL,PCLXL,URF" "usb_MDL=HL-L2370DN series" 
"usb_MFG=Brother" "priority=25" 
"adminurl=http://BRN3C2AF4B40D45.local./net/net/airprint.html; 
"product=(Brother HL-L2370DN series)" "ty=Brother HL-L2370DN series" "note=" 
"rp=ipp/print" "pdl=application/octet-stream,image/urf,image/pwg-raster" 
"qtotal=1" "txtvers=1"]
=   eth0 IPv6 Brother HL-L2370DN series Internet Printer
 local
   hostname = [BRN3C2AF4B40D45.local]
   address = [192.168.0.154]
   port = [631]
   txt = ["mopria-certified=1.3" "print_wfds=T" 
"UUID=e3248000-80ce-11db-8000-3c2af4b40d45" "PaperMax=legal-A4" 
"kind=document,envelope,label,postcard" 
"URF=W8,CP1,IS4-1,MT1-3-4-5-8,OB10,PQ3-4-5,RS300-600-1200,V1.4,DM1" "TBCP=F" 
"Transparent=T" "Binary=T" "PaperCustom=T" "Scan=F" "Fax=F" "Duplex=T" 
"Copies=T" "Color=F" "usb_CMD=PJL,PCL,PCLXL,URF" "usb_MDL=HL-L2370DN series" 
"usb_MFG=Brother" "priority=25" 
"adminurl=http://BRN3C2AF4B40D45.local./net/net/airprint.html; 
"product=(Brother HL-L2370DN series)" "ty=Brother HL-L2370DN series" "note=" 
"rp=ipp/print" "pdl=application/octet-stream,image/urf,image/pwg-raster" 
"qtotal=1" "txtvers=1"]
=   eth0 IPv4 EPSON WF-7515 Series  Internet Printer
 local
   hostname = [EPSONFB3FA2.local]
   address = [192.168.0.4]
   port = [631]
   txt = ["UUID=cfe92100-67c4-11d4-a45f-a4ee57fb3fa2" 
"URF=CP1,MT1-3-8-11-12,PQ4-5,OB9,OFU0,RS360-720,SRGB24,W8,IS1" "Scan=T" 
"Duplex=F" "Color=T" "note=" 
"adminurl=http://EPSONFB3FA2.local.:80/PRESENTATION/BONJOUR; "qtotal=1" 
"rp=Epson_IPP_Printer" "pdl=application/octet-stream,image/urf,image/jpeg" 
"product=(EPSON WF-7515 Series)" "usb_MDL=WF-7515 Series" "usb_MFG=EPSON" 
"ty=EPSON WF-7515 Series" 

Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles

[Christoph Anton Mitterer]

Package: firefox
Version: 80.0-1
Severity: normal


Hi.

It seems that with FF80 all addons are broken in existing profiles. They're 
shown
in the add-ons list, but e.g. their icons aren’t in the menu.

E.g. ublock origin, noscript also don't seem to work... so it's not just a 
display
issue.

Cheers,
Chris

Bug#969173: RM: openvas openvas-libraries openvas-cli openvas-manager -- ROM; replaced by gvm

[Raphaël Hertzog]

Package: ftp.debian.org
Severity: normal
User: de...@kali.org
Usertags: origin-kali
X-Debbugs-Cc: debian-security-to...@lists.debian.org

Hello,

GVM is replacing OpenVAS and a bunch of source packages have been
renamed or are obsolete.

Please remove the following source packages from unstable:
* openvas(replaced by gvm)
* openvas-libraries  (replaced by gvm-libs)
* openvas-cli(obsolete)
* openvas-manager(replaced by gvmd)

Thank you!

Bug#969172: buster-pu: package asterisk/1:16.2.1~dfsg-1+deb10u2

[Bernhard Schmidt]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Hi,

I would like to make a stable-update for asterisk.

It fixes three minor CVEs (marked no-dsa)

#940060   CVE-2019-15297: AST-2019-004: Crash when negotiating for T.38 with a 
declined stream
#947377   CVE-2019-18610: AST-2019-007: AMI user could execute system commands
#947381   CVE-2019-18790: AST-2019-006: SIP request can change address of a SIP 
peer

It fixes one segmentation fault due to a wrong datatype when IPv6 is
in use

#882145   asterisk: pjsip show history causes segmentation fault

and one use-after-free that causes a misleading error message to
appear

#966334   ast_json_vpack: Error building JSON ... Invalid UTF-8 string.

All of them have been fixed by backporting the corressponding upstream
fixes that are already in sid/bullseye.

Debdiff attached.

Bernhard
diffstat for asterisk-16.2.1~dfsg asterisk-16.2.1~dfsg

 changelog   |   13 ++
 patches/AST-2019-004.patch  |  171 
 patches/AST-2019-006.patch  |   73 +
 patches/AST-2019-007.patch  |   46 
 patches/fix-error-building-json.patch   |   30 +
 patches/fix-sigsegv-pjsip-history.patch |   30 +
 patches/series  |9 +
 7 files changed, 372 insertions(+)

diff -Nru asterisk-16.2.1~dfsg/debian/changelog 
asterisk-16.2.1~dfsg/debian/changelog
--- asterisk-16.2.1~dfsg/debian/changelog   2019-08-20 22:31:33.0 
+0200
+++ asterisk-16.2.1~dfsg/debian/changelog   2020-08-27 00:53:40.0 
+0200
@@ -1,3 +1,16 @@
+asterisk (1:16.2.1~dfsg-1+deb10u2) buster; urgency=medium
+
+  * CVE-2019-15297: AST-2019-004
+Crash when negotiating for T.38 with a declined stream (Closes: #940060)
+  * CVE-2019-18790: AST-2019-006
+SIP request can change address of a SIP peer (Closes: #947381)
+  * CVE-2019-18610: AST-2019-007
+AMI user could execute system commands (Closes: #947377)
+  * Fix use-after-free with TEST_FRAMEWORK enabled (Closes: #966334)
+  * Fix segfault in pjsip show history with IPv6 peers (Closes: #882145)
+
+ -- Bernhard Schmidt   Thu, 27 Aug 2020 00:53:40 +0200
+
 asterisk (1:16.2.1~dfsg-1+deb10u1) buster; urgency=medium
 
   * AST-2019-002 / CVE-2019-12827
diff -Nru asterisk-16.2.1~dfsg/debian/patches/AST-2019-004.patch 
asterisk-16.2.1~dfsg/debian/patches/AST-2019-004.patch
--- asterisk-16.2.1~dfsg/debian/patches/AST-2019-004.patch  1970-01-01 
01:00:00.0 +0100
+++ asterisk-16.2.1~dfsg/debian/patches/AST-2019-004.patch  2020-08-27 
00:53:40.0 +0200
@@ -0,0 +1,171 @@
+From 965df3c228d49bcde3503e0482f3c831dcbf6c77 Mon Sep 17 00:00:00 2001
+From: Kevin Harwell 
+Date: Tue, 20 Aug 2019 15:05:45 -0500
+Subject: [PATCH] AST-2019-004 - res_pjsip_t38.c: Add NULL checks before using 
session media
+
+After receiving a 200 OK with a declined stream in response to a T.38
+initiated re-invite Asterisk would crash when attempting to dereference
+a NULL session media object.
+
+This patch checks to make sure the session media object is not NULL before
+attempting to use it.
+
+ASTERISK-28495
+patches:
+  ast-2019-004.patch submitted by Alexei Gradinari (license 5691)
+
+Change-Id: I168f45f4da29cfe739acf87e597baa2aae7aa572
+---
+
+diff --git a/res/res_pjsip_t38.c b/res/res_pjsip_t38.c
+index 11804e2..e5c6090 100644
+--- a/res/res_pjsip_t38.c
 b/res/res_pjsip_t38.c
+@@ -203,7 +203,6 @@
+ {
+   RAII_VAR(struct ast_sip_session *, session, obj, ao2_cleanup);
+   RAII_VAR(struct ast_datastore *, datastore, 
ast_sip_session_get_datastore(session, "t38"), ao2_cleanup);
+-  struct ast_sip_session_media *session_media;
+ 
+   if (!datastore) {
+   return 0;
+@@ -212,8 +211,7 @@
+   ast_debug(2, "Automatically rejecting T.38 request on channel '%s'\n",
+   session->channel ? ast_channel_name(session->channel) : 
"");
+ 
+-  session_media = 
session->pending_media_state->default_session[AST_MEDIA_TYPE_IMAGE];
+-  t38_change_state(session, session_media, datastore->data, T38_REJECTED);
++  t38_change_state(session, NULL, datastore->data, T38_REJECTED);
+   ast_sip_session_resume_reinvite(session);
+ 
+   return 0;
+@@ -322,28 +320,37 @@
+   int index;
+ 
+   session_media = 
session->active_media_state->default_session[AST_MEDIA_TYPE_IMAGE];
+-  t38_change_state(session, session_media, state, T38_ENABLED);
++  if (!session_media) {
++  ast_log(LOG_WARNING, "Received %d response to T.38 
re-invite on '%s' but no active session media\n",
++  status.code, session->channel ? 
ast_channel_name(session->channel) : "unknown channel");
++  } else {
++  t38_change_state(session, session_media, state, 
T38_ENABLED);
+ 
+-  /* Stop all the streams 

Bug#969171: akonadi-server expects akonadi-backend-mysql allthough any sql backend should work

[Eric Valette]

Package: akonadi-server
Version: 4:20.04.1-2+b1
Severity: grave
Justification: renders package unusable

akonadi server support any backend from package dependency point of view.
However trying to start it via 

akonadictl start you get:

org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl:done.
Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
valette@tri-yann4:~$ org.kde.pim.akonadiserver: Starting up the Akonadi 
Server...
org.kde.pim.akonadiserver: Did not find MySQL server default configuration 
(mysql-global.conf)
org.kde.pim.akonadiserver: Failed to remove runtime connection config file
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited 
normally...

However the file

/etc/xdg/akonadi/mysql-global.conf  comes only with package
akonadi-backend-mysql and manually adding an empty file the error disappers but 
then it
barks again later with mysql not running.



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

Kernel: Linux 5.4.61 (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 akonadi-server depends on:
ii  akonadi-backend-sqlite   4:20.04.1-2+b1
ii  libc62.31-3
ii  libgcc-s110.2.0-5
ii  libkf5akonadiprivate5abi2 [libkf5akonadiprivate5-20.04]  4:20.04.1-2+b1
ii  libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.04]  4:20.04.1-2+b1
ii  libkf5configcore55.70.0-1
ii  libkf5coreaddons55.70.0-2
ii  libkf5crash5 5.70.0-1
ii  libkf5i18n5  5.70.0-1
ii  libqt5core5a 5.14.2+dfsg-6
ii  libqt5dbus5  5.14.2+dfsg-6
ii  libqt5gui5   5.14.2+dfsg-6
ii  libqt5network5   5.14.2+dfsg-6
ii  libqt5sql5   5.14.2+dfsg-6
ii  libqt5widgets5   5.14.2+dfsg-6
ii  libqt5xml5   5.14.2+dfsg-6
ii  libstdc++6   10.2.0-5

akonadi-server recommends no packages.

Versions of packages akonadi-server suggests:
pn  akonadi-backend-mysql   
pn  akonadi-backend-postgresql  
ii  akonadi-backend-sqlite  4:20.04.1-2+b1

-- no debconf information



Subject: akonadi-server: xxx
Package: akonadi-server
Version: 4:20.04.1-2+b1
Severity: normal



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

Kernel: Linux 5.4.61 (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 akonadi-server depends on:
ii  akonadi-backend-sqlite   4:20.04.1-2+b1
ii  libc62.31-3
ii  libgcc-s110.2.0-5
ii  libkf5akonadiprivate5abi2 [libkf5akonadiprivate5-20.04]  4:20.04.1-2+b1
ii  libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.04]  4:20.04.1-2+b1
ii  libkf5configcore55.70.0-1
ii  libkf5coreaddons55.70.0-2
ii  libkf5crash5 5.70.0-1
ii  libkf5i18n5  5.70.0-1
ii  libqt5core5a 5.14.2+dfsg-6
ii  libqt5dbus5  5.14.2+dfsg-6
ii  libqt5gui5   5.14.2+dfsg-6
ii  libqt5network5   5.14.2+dfsg-6
ii  libqt5sql5   5.14.2+dfsg-6
ii  libqt5widgets5   5.14.2+dfsg-6
ii  libqt5xml5   5.14.2+dfsg-6
ii  libstdc++6   10.2.0-5

akonadi-server recommends no packages.

Versions of packages akonadi-server suggests:
pn  akonadi-backend-mysql   
pn  akonadi-backend-postgresql  
ii  akonadi-backend-sqlite  

Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load

[Salvatore Bonaccorso]

hi Dirk,

On Wed, Aug 12, 2020 at 05:53:57PM +0200, Dirk Kostrewa wrote:
> Hi Salvatore,
> 
> I just found out, that if none of the two USB ports is connected, there are
> two kworker processes with permanently high CPU load, if one USB port is
> connected and the other not, there is one such kworker process, and if both
> USB ports are connected, there is no kworker process with high CPU load.
> I think, this supports your suspicion that these kworker processes are
> connected with the overcurrent condition for both USB ports that I also see
> in the dmesg output.
> What puzzles me, is that I've observed these oddly behaving kworker
> processes also with the 5.6 kernel that I've tried from the Buster Backports
> repository.

The kernel parameter variant did not work correctly as there are no
dynamic debug output afaics (the double quotes seem to placed in the
wrong place), please just try the setting at runtime instead:

# echo 'file drivers/usb/* +p;' > /sys/kernel/debug/dynamic_debug/control

What I was meaning is (and this is confirmed if you see the issue
issue as well with the more recent kernels), that the specified commit
actually uncovers the issue present possibly with the HW.

Similarly to you someone else, where in known case with faulty HW,
reported the following issue upstream:

https://lore.kernel.org/lkml/20200720083956.ga4...@dhcp22.suse.cz/

I would like to see if we can collect as much information as possible
and possibly crosscheck with upstream.

If build the kernel with the attached patch (that is with the commit
wich is supsected to uncover the issue), does then the issue goes
away?

You can folllow the quide in
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
for the "simple patching and building" and quickly chekcing a patch.

Regards,
Salvatore
>From 61ca5460d93d1a60a9aee0e46d51ae126593fda2 Mon Sep 17 00:00:00 2001
From: Salvatore Bonaccorso 
Date: Fri, 28 Aug 2020 16:31:04 +0200
Subject: [PATCH] Revert "xhci: prevent bus suspend if a roothub port detected
 a over-current condition"

This reverts commit d3ee95dedd88ed3fcd4647e4a8e265acaf27b2f0.
---
 drivers/usb/host/xhci-hub.c | 9 -
 1 file changed, 9 deletions(-)

diff --git a/drivers/usb/host/xhci-hub.c b/drivers/usb/host/xhci-hub.c
index a58ef53e4ae1..eb4284696f25 100644
--- a/drivers/usb/host/xhci-hub.c
+++ b/drivers/usb/host/xhci-hub.c
@@ -1481,8 +1481,6 @@ int xhci_hub_status_data(struct usb_hcd *hcd, char *buf)
 		}
 		if ((temp & PORT_RC))
 			reset_change = true;
-		if (temp & PORT_OC)
-			status = 1;
 	}
 	if (!status && !reset_change) {
 		xhci_dbg(xhci, "%s: stopping port polling.\n", __func__);
@@ -1548,13 +1546,6 @@ int xhci_bus_suspend(struct usb_hcd *hcd)
  port_index);
 			goto retry;
 		}
-		/* bail out if port detected a over-current condition */
-		if (t1 & PORT_OC) {
-			bus_state->bus_suspended = 0;
-			spin_unlock_irqrestore(>lock, flags);
-			xhci_dbg(xhci, "Bus suspend bailout, port over-current detected\n");
-			return -EBUSY;
-		}
 		/* suspend ports in U0, or bail out for new connect changes */
 		if ((t1 & PORT_PE) && (t1 & PORT_PLS_MASK) == XDEV_U0) {
 			if ((t1 & PORT_CSC) && wake_enabled) {
-- 
2.28.0

Bug#969169: cups: Driverless printing not working

[Brian Potkin]

On Fri 28 Aug 2020 at 15:04:41 +0200, Kurt Roeckx wrote:

> Package: cups
> Version: 2.3.3-2
> 
> Hi,
> 
> I've been trying to get printing on a Brother HL-L2370DN to work,
> but all attempts failed so far.
> 
> I first attempted this the old way by adding a printer using the
> adminstration page, where it finds it 3 times:
> Brother HL-L2370DN series (Brother HL-L2370DN series)
> Brother HL-L2370DN series (Brother HL-L2370DN series)
> Brother HL-L2370DN series (fully driverless) (Brother HL-L2370DN series)
> 
> It's at least very confusing why it would show me that same
> printer 3 times. But it seems the first one is using dnssd, the
> 2nd ldp, and the 3rd ipp.
> 
> If you then try to install it, you need to select a driver
> where there are 2 options for the dnssd and ipp: ipp everywhere,
> or driverless, and just one for ldp: driverless
> 
> If you use the ipp everywhere driver, and then try to print
> something, it will not find the printer, the job just stays in the
> queue. (I think I tried this for the 3 types.)
> 
> If you try to use the "driverless" driver it will just say
> "unable to copy PPD file".
> 
> Looking at the wiki and other places on internet, I decided to
> remove the printer in cups, and install cups-browsed. I think I've
> changed the config to:
> CreateIPPPrinterQueues Driverless
> 
> (It would be really nice if the documentation says what the
> default is, and that is has a good default.)
> 
> Even though the cups admin page doesn't show a printer, when I try
> to print something it's showing me a "Brother-HL-L2370DN-series"
> printer. However, when I tried to print using that, only page
> after page of garbage comes out of the printer.

Thank you for your report, Kurt. Please provide the outputs of

  avahi-browse -rt _ipp._tcp
  ippfind -T 5
  lpstat -l -e
  lpstat -t
  lpinfo -v

Thanks,

Brian.

Bug#950455: Bug#969170: lintian: fpos for override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS

[Chris Lamb]

forcemerge 950455 969170
thanks

Mattia Rizzolo wrote:

> When using debhelper compat 13 there is no need to explicitly check
> DEB_BUILD_OPTIONS=nocheck, so this tag
> override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS
> should not be emitted in dh compat 13.

Indeed.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#969156: rumur FTBFS on armel/armhf/mipsel/mips64el: test failures

[Matthew Fernandez]

Thanks for reporting this, Adrian. I noticed this some time after upload and 
fixed it upstream: 
https://github.com/Smattr/rumur/commit/68683c4742b380421936a703c4b9262dac1e68dc 


I hadn’t uploaded a fixed version to Debian because Rumur’s release cadence is 
so frequent I expected to release a new upstream version before the fix could 
get into Debian unstable. I hope this is an acceptable strategy.

By the way, is there any way to run the buildd tests prior to upload? I don’t 
have, e.g. armhf, hardware and bringing up a usable armhf qemu environment 
seems non-trivial. The buildd tests only seem to run after an upload is 
accepted, so I end up only being able to run this cross-platform testing once 
per release and only after the fact.

Bug#969170: lintian: fpos for override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS

[Mattia Rizzolo]

Package: lintian
Version: 2.91.0

Hi,

When using debhelper compat 13 there is no need to explicitly check
DEB_BUILD_OPTIONS=nocheck, so this tag
override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS
should not be emitted in dh compat 13.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#805445: ifupdown: Static IPv6 Default Route is not configured when exists RA and interface is not up

[Jose M Calhariz]

Package: ifupdown
Version: 0.8.35
Followup-For: Bug #805445

In our server VLAN there are IPv6 RA.  Every method we tried to disable autconf 
and 
RA on the clients are not working in buster, being kernel parameter autoconf=0, 
by 
sysctl.conf or by options in network/interfaces.  This bug is important to us.

-- Package-specific info:
--- /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#allow-hotplug ens3
auto ens3
iface ens3 inet static
  address XXX.YYY.ZZZ.251/25
  gateway XXX.YYY.ZZZ.254
  dns-nameserver  XXX.YYY.ZZZ.81 XXX.YYY.ZZZ.82

# This is an autoconfigured IPv6 interface
iface ens3 inet6 static
  address :::1::81/64
  gateway :::1::1
  accept_ra 0
  pre-up echo accept_ra
  pre-up cat /proc/sys/net/ipv6/conf/*/accept_ra
  autoconf 0
  pre-up echo autoconf
  pre-up cat /proc/sys/net/ipv6/conf/*/autoconf
  #pre-up echo use_tempaddr
  #pre-up cat /proc/sys/net/ipv6/conf/*/use_tempaddr
  pre-up ip a
  pre-up ip -6 r


--- /etc/network/interfaces.d/*:
cat: '/etc/network/interfaces.d/*': No such file or directory

--- up and down scripts installed:
/etc/network/if-down.d:
total 0

/etc/network/if-post-down.d:
total 0

/etc/network/if-pre-up.d:
total 0

/etc/network/if-up.d:
total 0


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

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

Versions of packages ifupdown depends on:
ii  adduser   3.118
ii  iproute2  4.20.0-2
ii  libc6 2.28-10
ii  lsb-base  10.2019051400

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.4.1-2

Versions of packages ifupdown suggests:
pn  ppp 
pn  rdnssd  

-- no debconf information

Bug#969169: cups: Driverless printing not working

[Kurt Roeckx]

Package: cups
Version: 2.3.3-2

Hi,

I've been trying to get printing on a Brother HL-L2370DN to work,
but all attempts failed so far.

I first attempted this the old way by adding a printer using the
adminstration page, where it finds it 3 times:
Brother HL-L2370DN series (Brother HL-L2370DN series)
Brother HL-L2370DN series (Brother HL-L2370DN series)
Brother HL-L2370DN series (fully driverless) (Brother HL-L2370DN series)

It's at least very confusing why it would show me that same
printer 3 times. But it seems the first one is using dnssd, the
2nd ldp, and the 3rd ipp.

If you then try to install it, you need to select a driver
where there are 2 options for the dnssd and ipp: ipp everywhere,
or driverless, and just one for ldp: driverless

If you use the ipp everywhere driver, and then try to print
something, it will not find the printer, the job just stays in the
queue. (I think I tried this for the 3 types.)

If you try to use the "driverless" driver it will just say
"unable to copy PPD file".

Looking at the wiki and other places on internet, I decided to
remove the printer in cups, and install cups-browsed. I think I've
changed the config to:
CreateIPPPrinterQueues Driverless

(It would be really nice if the documentation says what the
default is, and that is has a good default.)

Even though the cups admin page doesn't show a printer, when I try
to print something it's showing me a "Brother-HL-L2370DN-series"
printer. However, when I tried to print using that, only page
after page of garbage comes out of the printer.


Kurt

Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327]

[Markus Koschany]

Hello Kevin,

Am 28.08.20 um 11:53 schrieb SerNet Support Kevin Ivory:
[...]
> is there any way to extract only the data you need?
> 
> All cases in my debug log (46 GB) seem to be of a POST
> that is logged in access.log as
> 2020-08-27 11:29:24   1243 172.16.100.3 TAG_NONE/500 3640 POST
> http://srv1.first-businesspost.com/viper? - HIER_NONE/- text/html
> The debug cache.log does contain SenderID= and Secret=
[...]
>>> The cache.log shows
>>> 2020/08/18 07:24:04 kid1| suspending ICAP service for too many failures
>>> 2020/08/18 07:24:04 kid1| essential ICAP service is suspended:
>>> icap://127.0.0.1:1344/service_scanner-reqmod [down,susp,fail11]

In order to debug the problem I need to understand how the failing ICAP
service is related to your POST messages with internal server error 500.
With debug_options ALL,9 there should be a line with error: or Error:
before the ICAP service is suspended or something else that causes the
ICAP service to fail.

Some internet search also suggests that TAG_NONE/500 errors could be
completely unrelated to ICAP and indicate different issues like firewall
problems etc.

I would clone the customer's squid configuration and try to reproduce
the bug on your debug vm or try to find out what all those 500 errors
have in common.

Just to make sure that we are looking in the right direction, when you
unapply CVE-2019-12523.patch now, is everything working normal again?
I'm asking because there was another bug in CVE-2019-12529.patch that
prevented in some cases the authentication of clients when the kerberos
option was turned on. Rebuilding the squid package without those patches
may help to narrow down the problem.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#969168: RM: ruby-has-scope/0.7.2-2 ruby-inherited-resources/1.11.0-4

[Pirate Praveen]

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

FTBFS with rails 6 (#969166) and blocking testing migration of rails 6.
It has a leaf package as reverse dependency: 
ruby-inherited-resources/1.11.0-4

So please remove both packages to allow migration of rails 6 to testing.

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

Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Bug#969167: borgmatic: Shouldn't binary pkg Architecture be arch:all?

[Alexandre Rossi]

Package: borgmatic
Version: 1.5.1-1
Severity: normal
Tags: patch

Dear Maintainer,

I noticed that your package is arch:any and has a binary package for each
architecture supported in Debian. However, from a quick inspection of the
source and the build logs, it seems to be a pure python application.

Am I wrong in thinking the binary package should be Architecture: all ?

Thanks,

Alex

Bug#969028: ganeti: migration_caps break migration

[Sascha Lucas]

On Wed, 26 Aug 2020 11:55:49 +0200 Joerg Jaspert  wrote:

> using Ganeti 2.16 and qemu 1:5.0-14~bpo10+1 I tried setting 
> migration_caps for the cluster. But no matter which value i use it 
> breaks migration.
> 
> Migration then "goes"
>  - Setup disks and prepare target node
>  - starting memore transfer
>  - "Migration failed, aborting"
>  - Closing disks
> 
> That is entirely independent on which value I put into the caps.
> 
> Unsetting migration_caps and retrying the migration - it fails again.

I have tested Ganeti-3.0 from master on Buster with Qemu-5.0 from
backports. The HV-code should be the same for Ganeti-2.16.

First migration works on freshly started instances (empty
migration_caps). I've also tested the following migration capabilities
with success (2 times of migrations): auto-converge, zero-blocks,
xbzrle. The only known one that is broken is postcopy-ram[1].

So I assume Joerg is/was using postcopy-ram? If an instance was
previously migrated with postcopy-ram, the current qemu-process
"remembers" this "setting". If migration_caps is unset (empty), running
instances must be unset as well. On the instance's node run:

echo "migrate_set_capability postcopy-ram off" | socat STDIO 
UNIX-CONNECT:/var/run/ganeti/kvm-hypervisor/ctrl/X.monitor

> Looking more in detail it appears that its setting the caps on the 
> source side. But possibly forgets to set them on the target side so qemu 
> hates doing migration?!

That is true for postcopy-ram. It worked before Qemu-2.11, but is now
broken (should also be broken with qemu-3.1/default buster version). 

> And when it breaks, it forgets to unset the capabilities, so next 
> migrations break too. One has to manually connect to the monitor and 
> unset them, before migration works again.

Sounds exactly what I described.

[1] https://github.com/ganeti/ganeti/issues/950#issuecomment-506266808


pgptEUu87UQFb.pgp
Description: PGP signature

Bug#969166: ruby-has-scope: FTBFS with rails 6 - ArgumentError: unknown keywords: :only_tall, :id

[Pirate Praveen]

Package: ruby-has-scope
Version: 0.7.2-2
Severity: serious
User: pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: rails6-transition

This package FTBFS with rails 6.

30) Error:
HasScopeTest#test_scope_is_called_only_on_index:
ArgumentError: unknown keywords: :only_tall, :id
   
/usr/share/rubygems-integration/all/gems/actionpack-6.0.3.1/lib/action_controller/test_case.rb:460:in 
`process'
   
/usr/share/rubygems-integration/all/gems/actionpack-6.0.3.1/lib/action_controller/test_case.rb:395:in 
`get'
   /<>/test/has_scope_test.rb:120:in 
`test_scope_is_called_only_on_index'
   /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) 
in run'
   /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in 
`capture_exceptions'
   /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) 
in run'

   /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it'
   /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run'
   /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
   /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in 
`with_info_handler'

   /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run'
   /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method'
   /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method'
   /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in 
run'

   /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each'
   /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run'
   /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
   /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler'
   /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run'
   /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run'
   /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map'
   /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run'
   /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run'
   /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun'

32 runs, 3 assertions, 0 failures, 30 errors, 0 skips

Full log 
https://people.debian.org/~praveen/rails6-meta-build/buildlogs/ruby-has-scope.log

Bug#969165: Please add libzstd-dev to enable zstd in zlib_plugin.

[Sven Hartge]

Source: dovecot
Version: 1:2.3.11.3+dfsg1-2
Severity: wishlist

Hi!

The subject says it all: Please add libzstd-dev to enable zstd in
zlib_plugin.

Grüße,
Sven.

Bug#969164: ITP: libtrapperkeeper-filesystem-watcher-clojure -- Trapperkeeper filesystem watcher service

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: libtrapperkeeper-filesystem-watcher-clojure
  Version : 1.2.2
  Upstream Author : Puppet Labs Inc 
* URL : 
https://github.com/puppetlabs/trapperkeeper-filesystem-watcher
* License : Apache-2.0
  Programming Lang: Clojure
  Description : Trapperkeeper filesystem watcher service

 This library includes a Trapperkeeper service which provides an API for
 watching paths on the filesystem for changes and doing something when they
 change.

Note: This is a dependency for Puppet 6.

Bug#930919: dovecot: dsync broken for sieve filters

[Raphaël Walther]

On Wed, 26 Aug 2020 11:25:50 -0700, Noah Meyerhans wrote:
…
> I suspect we'll also want the next commit on that file, 
> https://github.com/dovecot/pigeonhole/commit/382b1eacdf587cd7d20a260e19a29a4d958bf98e

Indeed, I also think these two commits should be included:

commit 382b1eacdf587cd7d20a260e19a29a4d958bf98e
Author: Timo Sirainen 
Date:   Wed Jul 17 12:33:09 2019 +0300

doveadm-sieve: Shared attribute iteration shouldn't list Sieve scripts

Trying to get them as shared instead of as private resulted in failure.

commit 0e91911d22d43621c820d7f5b28be671050fd290
Author: Aki Tuomi 
Date:   Mon May 27 09:43:25 2019 +0300

doveadm-sieve: Fix script synchronization

When dsyncing, this codepath is always called with prefix "".
There is no point checking the prefix at all.

Broken in 479c5e57046dec76078597df844daccbfc0eb75f


I rebuilded the packages on my side. That would be nice to see this bug fixed
in buster release.

-- 
infomaniak
Raphaël Walther | Administrateur système
Rue Eugène-Marziano 25, 1227 Genève
Swiss Made| ISO 27001 14001 50001



signature.asc
Description: PGP signature

Bug#969163: buster-pu: package npm/5.8.0+ds6-4+deb10u2

[Xavier Guimard]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Hi,

[ Reason ]
npm is vulnerable to CVE-2020-15095: password in URL are stored in logs.
This fixes import upstream commit to fix it.

[ Impact ]
(What is the impact for the user if the update isn't approved?)
Little CVE: URL containing password (https://user:pwd@xxx) are stored in
logs

[ Tests ]
autopkgtest tested, no specific test for this CVE

[ Risks ]
(Discussion of the risks involved. E.g. code is trivial or
complex, alternatives available.)
Low risk: minor change in logs only

[ 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 (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]
(Explain *all* the changes)
Log strings are parsed by a new "lib/utils/replace-info.js" to delete
password in URLs before logging

[ Other info ]
None
diff --git a/debian/changelog b/debian/changelog
index d7b986f..a567e2e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+npm (5.8.0+ds6-4+deb10u2) buster; urgency=medium
+
+  * Team upload
+  * Don't show password in logs (Closes: CVE-2020-15095)
+
+ -- Xavier Guimard   Fri, 28 Aug 2020 13:36:33 +0200
+
 npm (5.8.0+ds6-4+deb10u1) buster; urgency=medium
 
   * Add patches to fix arbitrary path access
diff --git a/debian/patches/CVE-2020-15095.diff 
b/debian/patches/CVE-2020-15095.diff
new file mode 100644
index 000..9188249
--- /dev/null
+++ b/debian/patches/CVE-2020-15095.diff
@@ -0,0 +1,133 @@
+Description: chore: remove auth info from logs
+Author: claudiahdz 
+Origin: upstream, https://github.com/npm/cli/commit/a9857b8f
+Bug: https://github.com/npm/cli/security/advisories/GHSA-93f3-23rq-pjfp
+Forwarded: not-needed
+Reviewed-By: Xavier Guimard 
+Last-Update: 2020-08-28
+
+--- a/bin/npm-cli.js
 b/bin/npm-cli.js
+@@ -35,6 +35,7 @@
+   var npm = require('../lib/npm.js')
+   var npmconf = require('../lib/config/core.js')
+   var errorHandler = require('../lib/utils/error-handler.js')
++  var replaceInfo = require('../lib/utils/replace-info.js')
+   var output = require('../lib/utils/output.js')
+ 
+   var configDefs = npmconf.defs
+@@ -48,7 +49,8 @@
+ process.argv.splice(1, 1, 'npm', '-g')
+   }
+ 
+-  log.verbose('cli', process.argv)
++  var args = replaceInfo(process.argv)
++  log.verbose('cli', args)
+ 
+   var conf = nopt(types, shorthands)
+   npm.argv = conf.argv.remain
+--- a/lib/fetch-package-metadata.js
 b/lib/fetch-package-metadata.js
+@@ -3,6 +3,7 @@
+ const deprCheck = require('./utils/depr-check')
+ const path = require('path')
+ const log = require('npmlog')
++const pacote = require('pacote')
+ const readPackageTree = require('read-package-tree')
+ const rimraf = require('rimraf')
+ const validate = require('aproba')
+@@ -10,8 +11,8 @@
+ const npm = require('./npm')
+ const npmlog = require('npmlog')
+ const limit = require('call-limit')
+-const tempFilename = require('./utils/temp-filename')
+-const pacote = require('pacote')
++const tempFilename = require('./utils/temp-filename.js')
++const replaceInfo = require('./utils/replace-info.js')
+ let pacoteOpts
+ const isWindows = require('./utils/is-windows.js')
+ 
+@@ -19,7 +20,9 @@
+   validate('SOF|SZF|OOF|OZF', [spec, tracker, done])
+   return (er, pkg) => {
+ if (er) {
+-  log.silly('fetchPackageMetaData', 'error for ' + String(spec), 
er.message)
++  er.message = replaceInfo(er.message)
++  var spc = replaceInfo(String(spec))
++  log.silly('fetchPackageMetaData', 'error for ' + spc, er.message)
+   if (tracker) tracker.finish()
+ }
+ return done(er, pkg)
+--- a/lib/utils/error-handler.js
 b/lib/utils/error-handler.js
+@@ -13,6 +13,7 @@
+ var chain = require('slide').chain
+ var writeFileAtomic = require('write-file-atomic')
+ var errorMessage = require('./error-message.js')
++var replaceInfo = require('./replace-info.js')
+ var stopMetrics = require('./metrics.js').stop
+ var mkdirp = require('mkdirp')
+ var fs = require('graceful-fs')
+@@ -176,14 +177,16 @@
+   ].forEach(function (k) {
+ var v = er[k]
+ if (!v) return
++v = replaceInfo(v)
+ log.verbose(k, v)
+   })
+ 
+   log.verbose('cwd', process.cwd())
+ 
+   var os = require('os')
++  var args = replaceInfo(process.argv)
+   log.verbose('', os.type() + ' ' + os.release())
+-  log.verbose('argv', process.argv.map(JSON.stringify).join(' '))
++  log.verbose('argv', args.map(JSON.stringify).join(' '))
+   log.verbose('node', process.version)
+   log.verbose('npm ', 'v' + npm.version)
+ 
+--- a/lib/utils/error-message.js
 b/lib/utils/error-message.js
+@@ -2,12 +2,17 @@
+ var npm = require('../npm.js')
+ var util = require('util')
+ var nameValidator = require('validate-npm-package-name')
++var replaceInfo = require('./replace-info.js')
+ 
+ module.exports = errorMessage
+ 
+ function errorMessage (er) {
+   var short = []
+  

Bug#969162: checkit_tiff: new upstream available, changed main repository

[Andreas Romeyke]

Package: checkit_tiff
Version: 0.5.4
Severity: normal
Tags: upstream

Dear Maintainer,

the main repository of the tool is changed to
https://art1pirat.spdns.org/art1/checkit_tiff

the latest release is 0.6.0,see
https://art1pirat.spdns.org/art1/checkit_tiff/releases for details.

The former repository is outdated.

With best regards

Andreas



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

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

Versions of packages checkit_tiff depends on:
ii  libc6 2.28-10
ii  libpcre3  2:8.39-12

checkit_tiff recommends no packages.

checkit_tiff suggests no packages.

-- no debconf information

Bug#896016: strace: please make the build reproducible

[Chris Lamb]

> Would you consider applying this patch and uploading?

A quick glance suggests like this was fixed upstream in Apr 2018:

  https://github.com/strace/strace/pull/68#ref-commit-fc8294c

Can you confirm? Unfortunately, your package FTBFS in our
infrastructure (something to do with libfaketime, as yet
uninvestigated).

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

Click the "rbuild" link on the left hand side for the build log;
apologies for the weird UI/UX here.


Best wishes,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#969161: RM: ruby-diaspora-federation-rails/0.2.6-1

[Pirate Praveen]

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

This package is not yet compatible with rails 6 (#969157) and is 
blocking

migration of rails 6 to testing.

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

Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Bug#969144: systemd: serial-getty@.service should support 57600 baud

[Michael Biebl]

Control: tags -1 + upstream

Thanks for the patch. Since that is not a Debian integration issue,
please consider submitting that upstream as pull request
https://github.com/systemd/systemd/pulls

Regards,
Michael

Am 28.08.20 um 09:55 schrieb Bjørn Mork:
> Package: systemd
> Version: 241-7~deb10u4
> Severity: normal
>
> Dear Maintainer,
> 
> My BIOS provides pre-boot access to the system over serial, and sets
> the port up for 57600.  So I have configured the client (conserver)
> to use that speed.  This has happened to work by accident with the
> systemd serial-getty@.service because of the  --keep-baud
> parameter to agetty.
> 
> But today I ended up changing the speed of the port while temporarily
> testing another client.  And was surprised to learn that it is
> impossible to switch back to 57600 with the default serial-getty@.service 
> 
> 
> I see no reason why this standard baud rate should be excluded from
> the list of rates.  Please fix
> 
> --- a/lib/systemd/system/serial-getty@.service   2020-04-27 
> 19:02:57.0 +0200
> +++ b/etc/systemd/system/serial-getty@.service   2020-08-28 
> 09:45:03.0 +0200
> @@ -31,7 +31,7 @@
>  # The '-o' option value tells agetty to replace 'login' arguments with an
>  # option to preserve environment (-p), followed by '--' for safety, and then
>  # the entered username.
> -ExecStart=-/sbin/agetty -o '-p -- \\u' --keep-baud 115200,38400,9600 %I $TERM
> +ExecStart=-/sbin/agetty -o '-p -- \\u' --keep-baud 115200,57600,38400,9600 
> %I $TERM
>  Type=idle
>  Restart=always
>  UtmpIdentifier=%I
> 




signature.asc
Description: OpenPGP digital signature

Bug#969160: linux-image-5.7.0-2-amd64: amdgpu_dm_atomic_commit_tail issue freezes X

[Ma Wo]

Package: src:linux
Version: 5.7.10-1
Severity: important

amdgpu crashes leaving X unressponsible. This seems to be a race condition and 
is already fixed upstream for kernels 5.8.0, 5.7.13, 5.4.56
https://bugzilla.kernel.org/show_bug.cgi?id=207383

It is quite often reproducible by waking up the monitors after they have been 
switched off by the screensaver.

I'm using a multi monitor setup with a
0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 
10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c4)

-- Package-specific info:
** Version:
Linux version 5.7.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-16), GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 
5.7.10-1 (2020-07-26)

** Command line:
BOOT_IMAGE=/vmlinuz-5.7.0-2-amd64 
root=UUID=70f13b00-5a54-4309-887a-333da8417dd7 ro acpi_enforce_resources=lax 
splash

** Tainted: W (512)
 * kernel issued warning

** Kernel log:
Aug 26 17:26:38 localhost kernel: [12803.982534] show_signal_msg: 17 callbacks 
suppressed
Aug 26 17:26:38 localhost kernel: [12803.982537] kscreenlocker_g[27883]: 
segfault at 58 ip 7fddb372a9e9 sp 7ffc4b806000 error 4 in 
libQt5Core.so.5.14.2[7fddb34e8000+2ef000]
Aug 26 17:26:38 localhost kernel: [12803.982545] Code: 58 48 39 d0 0f 85 57 02 
00 00 b8 01 00 00 00 e9 34 fd ff ff 48 8b 74 24 38 48 8b 46 08 48 85 c0 74 0d 
48 8b 46 08 8b 74 24 40 <3b> 70 08 7c 32 48 8d 7c 24 60 e8 48 71 00 00 48 8b 7c 
24 08 b8 01
Aug 26 17:26:39 localhost kernel: [12804.947817] [ cut here 
]
Aug 26 17:26:39 localhost kernel: [12804.947921] WARNING: CPU: 4 PID: 29465 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hwseq.c:109 
dcn20_setup_gsl_group_as_lock+0x7f/0x200 [amdgpu]
Aug 26 17:26:39 localhost kernel: [12804.947923] Modules linked in: fuse 
xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
nft_compat nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nf_tables nfnetlink tun bridge stp llc binfmt_misc 
snd_hda_codec_realtek snd_hda_codec_generic amd64_edac_mod edac_mce_amd 
ledtrig_audio kvm_amd snd_hda_codec_hdmi kvm eeepc_wmi snd_hda_intel 
ax88179_178a asus_wmi snd_intel_dspcfg usbnet battery sparse_keymap irqbypass 
sg mii joydev snd_hda_codec rfkill snd_hda_core video pcspkr wmi_bmof snd_hwdep 
sp5100_tco snd_pcm k10temp watchdog snd_timer ccp snd rng_core soundcore evdev 
acpi_cpufreq ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi nct6775 hwmon_vid r8169 realtek 
libphy parport_pc ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 
mbcache jbd2 dm_crypt dm_mod raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid0 
multipath
Aug 26 17:26:39 localhost kernel: [12804.947953]  linear radeon raid1 md_mod 
sr_mod cdrom hid_generic usbhid hid sd_mod amdgpu gpu_sched i2c_algo_bit ttm 
crc32_pclmul crc32c_intel drm_kms_helper ghash_clmulni_intel cec xhci_pci drm 
xhci_hcd ahci aesni_intel libahci libata libaes crypto_simd cryptd glue_helper 
usbcore nvme scsi_mod nvme_core i2c_piix4 t10_pi crc_t10dif crct10dif_generic 
mfd_core crct10dif_pclmul usb_common crct10dif_common wmi button
Aug 26 17:26:39 localhost kernel: [12804.947972] CPU: 4 PID: 29465 Comm: 
kworker/u64:5 Not tainted 5.7.0-2-amd64 #1 Debian 5.7.10-1
Aug 26 17:26:39 localhost kernel: [12804.947974] Hardware name: System 
manufacturer System Product Name/TUF GAMING X570-PLUS, BIOS 1407 04/01/2020
Aug 26 17:26:39 localhost kernel: [12804.947984] Workqueue: events_unbound 
commit_work [drm_kms_helper]
Aug 26 17:26:39 localhost kernel: [12804.948076] RIP: 
0010:dcn20_setup_gsl_group_as_lock+0x7f/0x200 [amdgpu]
Aug 26 17:26:39 localhost kernel: [12804.948078] Code: 84 d2 74 47 84 c0 75 26 
48 8b 87 30 03 00 00 0f b6 80 70 02 00 00 a8 01 0f 84 dc 00 00 00 a8 02 74 55 
a8 04 0f 84 f7 00 00 00 <0f> 0b 0f 0b 48 8b 44 24 28 65 48 33 04 25 28 00 00 00 
0f 85 59 01
Aug 26 17:26:39 localhost kernel: [12804.948079] RSP: 0018:a67a4828fa48 
EFLAGS: 00010202
Aug 26 17:26:39 localhost kernel: [12804.948081] RAX: 0007 RBX: 
964871ce0b08 RCX: 
Aug 26 17:26:39 localhost kernel: [12804.948082] RDX: 0001 RSI: 
964871ce0b08 RDI: 9649a8d7
Aug 26 17:26:39 localhost kernel: [12804.948083] RBP: 0001 R08: 
a67a4828fa44 R09: 
Aug 26 17:26:39 localhost kernel: [12804.948084] R10:  R11: 
a67a4828fab4 R12: 0001
Aug 26 17:26:39 localhost kernel: [12804.948085] R13: 9649a8d7 R14: 
9648b798 R15: 964927614400
Aug 26 17:26:39 localhost kernel: [12804.948087] FS:  () 
GS:9649beb0() knlGS:
Aug 26 17:26:39 localhost kernel: [12804.948088] CS:  0010 DS:  ES:  
CR0: 80050033
Aug 26 17:26:39 localhost kernel: [12804.948089] CR2: 7fa2dc0289e0 CR3: 

Bug#734592: Listing Makefile Targets

[Barak A. Pearlmutter]

This seems a bit safer:

make -f debian/rules -rp | egrep -i '^[.a-z0-9_-]*:$'

although it does include "foo:" if there's an "include foo:" even if
there's no rule for "foo".

Bug#969159: darktable: embeds photoswipe

[David Bremner]

Package: darktable
Version: 3.2.1-2+b1
Severity: important
Tags: security
X-Debbugs-Cc: pkg-javascript-de...@lists.alioth.debian.org, Debian Security 
Team 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Darktable embeds the photoswipe JavaScript library 
(https://github.com/dimsemenov/PhotoSwipe)
and uses it in exported web galleries). It seems to be an old version
:(. 

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

Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 darktable depends on:
ii  libc62.31-3
ii  libcairo21.16.0-4
ii  libcolord-gtk1   0.1.26-2
ii  libcolord2   1.4.4-2
ii  libcups2 2.3.3-2
ii  libcurl3-gnutls  7.68.0-1+b1
ii  libexiv2-27  0.27.3-3
ii  libgcc-s110.2.0-5
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libglib2.0-0 2.64.4-1
ii  libgomp1 10.2.0-5
ii  libgphoto2-6 2.5.25-3
ii  libgphoto2-port122.5.25-3
ii  libgraphicsmagick-q16-3  1.4+really1.3.35+hg16297-1
ii  libgtk-3-0   3.24.22-1
ii  libilmbase25 2.5.3-2
ii  libjpeg62-turbo  1:2.0.5-1.1
ii  libjs-prototype  1.7.1-3
ii  libjs-scriptaculous  1.9.0-2
ii  libjson-glib-1.0-0   1.4.4-2
ii  liblcms2-2   2.9-4+b1
ii  liblensfun1  0.3.2-5
ii  liblua5.3-0  5.3.3-1.1+b1
ii  libopenexr25 2.5.3-2
ii  libopenjp2-7 2.3.1-1
ii  libosmgpsmap-1.0-1   1.1.0-7
ii  libpango-1.0-0   1.46.0-2
ii  libpangocairo-1.0-0  1.46.0-2
ii  libpng16-16  1.6.37-2
ii  libpugixml1v51.10-1
ii  librsvg2-2   2.48.7-1
ii  libsecret-1-00.20.3-1
ii  libsoup2.4-1 2.70.0-1
ii  libsqlite3-0 3.33.0-1
ii  libstdc++6   10.2.0-5
ii  libtiff5 4.1.0+git191117-2
ii  libwebp6 0.6.1-2+b1
ii  libx11-6 2:1.6.10-3
ii  libxml2  2.9.10+dfsg-5+b1
ii  libxrandr2   2:1.5.1-1
ii  zlib1g   1:1.2.11.dfsg-2

darktable recommends no packages.

darktable suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl9I5Q4ACgkQA0U5G1Wq
FSFhQw//YPA8EuJFCuMA5FHxTGodkmDGSgzZ/p5KK48oj56BXT2fp6czhb1cy3mT
aR44kpSKtfL2tF4q6Qqkr4Foo1tiGpAdDn7fYI/tjIBtxtPeO1mIMEnwHQKbg5Ck
VZGdzgclt0xvWi4b3mdm7lEk8ukgVf/qzoi1V6G701NNqVacgFDEG8EDCSTJqWzW
me0+Lr3iLnPkPVxtKiMhg25AVXVmBosxa6wv5fL87SlFUBtd+N2pWR+3UOZbkn0C
KiLIpmvIKB7JEGhIR4EWWKirNiuZAVbxWhlqITZUjhQPZKN7VNU5112cHuuG4CvS
3GegMO671tHA+E6vBnKlcTxr0DBFSDIjitbYwuzN2B3TOlckVg4AHgqdx7e1y9l8
wQz/abseVX5/g/JsH0doLT9cn93KumM2sw5FH7tJNsAibRq3LMvySNw5ZRvWkkXl
xrKhNPSM9zTBcY6OnZu/TqtHbA5VyY9Hvp5DJuFLJnEfZGT7FK818BEVfVwSiOmz
2PkXDoVzOKqRpUZp1eqlkrqVrsI0YRPA2q1ajshWZgVIU+3SitkUfe2ozBHw1wWF
t01IX8Uq0LnpZpwpi7+M/BDmSGhqA9QIrCyHNiEQW5rcRxYcLTBC7urBHY69dHgQ
vg8S2dh6OvpoafKPpZ91F2Krfv8A6nV58dK4t0vBshVjN/LlTtA=
=2wVa
-END PGP SIGNATURE-

Bug#935127: bash: please make the build reproducible

[Chris Lamb]

Chris Lamb wrote:

> A patch is attached that makes the Bash interpreter build
> reproducibly for me in unstable.

Gentle ping on this?

Bash is one of the few remaining packages in the 'Essential' package
set that remains unreproducible, and this patch has been in the BTS
for over a year now.


Regards,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#969137: [Pkg-phototools-devel] Bug#969137: darktable: Histogram not shown

[David Bremner]

Control: tag -1 unreproducible

Fabian Inostroza  writes:

> Package: darktable
> Version: 3.2.1-2+b1
> Severity: normal
>
> Dear Maintainer,
>
> When working on a image in darktable the histogram is not shown, a user 
> suggested
> I try Ctrl+Shift+H and the only change I see is a very thin dark line in the 
> place
> where the histogram should be.
>

Hi Fabian;

Sorry I can't reproduce that. Ctrl-shift-h does indeed toggle it for me,
and the histogram is displayed at startup

1. Does it happen on all images, or just certain ones?
2. As you might know, the histogram is only displayed in darkroom mode. 
3. One thing to try is to move your darktable configuration out of the way
   (in ~/.config/darktable)

Bug#579531: cscope: to support file name with space character

[Alberto Garcia]

On Wed, Apr 28, 2010 at 07:46:06PM +0800, Astone Lin wrote:
> I do not have any idea about whatever reason cscope not to support file
> name with whitespace,
> but I really need this feature in emacs environment with xcscope.el.
> I had some workaround to make it happened, as following patch.

Hi, I hit this problem recently and cooked a patch for xcscope-el.
This fixes the index generation for files with special names and adds
partial support for white spaces.

In order to support files with white spaces correctly it seems that
cscope itself needs to be fixed. I didn't do that, although my patch
seems to be enough for partial support (cscope-find-global-definition
does not seem to work but cscope-find-this-symbol does work).

Here's the patch and proposed pull request for reference. Any feedback
will be appreciated:

https://github.com/dkogan/xcscope.el/pull/23

Berto

Bug#969155: [Pkg-nagios-devel] Bug#969155: RFP: icinga database -- database for icinga 2

[Sebastiaan Couwenberg]

On 8/28/20 11:44 AM, Kunz David wrote:
> icinga database is a new database backend
> for icinga 2

Since the PostgreSQL backend works fine for me, and Icinga DB only seems
to support MySQL, I do not intend to package it.

Would you be willing to maintain the icingadb package for Debian within
the Nagios team?

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#969158: expeyes: maybe a false positive generated by mail_autoremovals.pl?

[Georges Khaznadar]

Package: release.debian.org
Severity: normal

Dear members of the release team,

The package expeyes which I maintain is affected repeatedly by announcements
telling that "expeyes is marked for autoremoval from testing", ... on
2020-09-16,
due to the fact that it is supposed to (build-)depend on binutils-avr, which
FTBFS.

I presume that it might be some false positive detection.
Here is the list of its build-dependencies:

 debhelper-compat (=12),
 python3-all,
 dh-python,
 python3-docutils,
 pkg-config,
 wxglade,
 x11proto-randr-dev (>= 1.5.0),
 pyqt5-dev-tools,
 qttools5-dev-tools,
 qt5-qmake

as far as I know, none of them is related with binutils-avr.

The source package expeyes generates one binary package, microhope, which
declares a dependency on avr-libc; should I downgrade this dependency down to
a recommendation? The binary package microhope does not need  binutils-avr
as it is mainly an editor for small C or assembly language snippets. It needs
binutils-avr only when the end user will try to compile and link one one the
edited snippets.

Thank you in advance for any feedback.

Best regards, Georges.




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

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

Bug#969157: ruby-diaspora-federation-rails: FTBFS with rails 6 - Could not find 'actionpack' (< 6, >= 4.2) - did find: [actionpack-6.0.3.1]

[Pirate Praveen]

Package: ruby-diaspora-federation-rails
Version: 0.2.6-1
Severity: serious
User: pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: rails6-transition

This package fails to build from source with rails 6.

┌──┐
│ Checking Rubygems dependency resolution on ruby2.7 │
└──┘

GEM_PATH=/<>/debian/ruby-diaspora-federation-rails/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 
ruby2.7 -e gem\ \"diaspora_federation-rails\"
/usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not 
find 'actionpack' (< 6, >= 4.2) - did find: [actionpack-6.0.3.1] 
(Gem::MissingSpecVersionError)
Checked in 
'GEM_PATH=/<>/debian/ruby-diaspora-federation-rails/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0', 
execute `gem env` for more information
from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1402:in `block in 
activate_dependencies'

from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in `each'
from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in 
`activate_dependencies'

from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:in `activate'
from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
in gem'
from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in 
`synchronize'

from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `gem'
from -e:1:in `'

Full log is 
https://people.debian.org/~praveen/rails6-meta-build/buildlogs/ruby-diaspora-federation-rails.log

Bug#964862: RFS: git-revise/0.6.0-1 -- handy git tool for doing efficient in-memory commit rebases & fixups

[Adrian Bunk]

Control: tags -1 moreinfo

On Sat, Jul 11, 2020 at 02:02:43PM +0200, Nicolas Schier wrote:
>...
> Changes since the last upload:
>...
>* Enable autopkgtest by using upstream tests (Closes: #944957)

This likely worked when you posted the sponsorship request,
but new pylint makes it fail:

...
lint run-test: commands[0] | pylint gitrevise
* Module gitrevise.merge
gitrevise/merge.py:207:12: W0707: Consider explicitly re-raising using the 
'from' keyword (raise-missing-from)
gitrevise/merge.py:225:12: W0707: Consider explicitly re-raising using the 
'from' keyword (raise-missing-from)
* Module gitrevise.utils
gitrevise/utils.py:73:8: W0707: Consider explicitly re-raising using the 'from' 
keyword (raise-missing-from)
gitrevise/utils.py:89:12: W0707: Consider explicitly re-raising using the 
'from' keyword (raise-missing-from)

--
Your code has been rated at 9.96/10 (previous run: 9.96/10, +0.00)

ERROR: InvocationError for command 
/tmp/autopkgtest.SDfHIM/tree/.tox/lint/bin/pylint gitrevise (exited with code 4)
...

> Kind regards,
> Nicolas

cu
Adrian

Bug#954823: Ταμείο κληρονομιάς

[Barrister Sayyad Zahed]

Χαίρετε,

Σας έστειλα ένα email πριν σχετικά με μια κληρονομιά χωρίς να σας ακούσω.
Επιτρέψτε μου να επαναφέρω ξανά το email μου και να απαντήσω αμέσως.
Το όνομά μου είναι ο κύριος Sayyad Zahed, κύριος δικηγόρος στο Sayyad &
Partner Associate Law Office με έδρα το Ντουμπάι. Σε επικοινωνώ μαζί μου
λόγω του αποθανόντος πελάτη μου που πέθανε αφήνοντας κάποια χρήματα σε
τράπεζα στο Ντουμπάι στο ποσό των 11.735.000,00 ευρώ. Θέλω να σας
ανακοινώσω ως κληρονόμο / δικαιούχο του ταμείου.

Δεν χρειάζεται να ανησυχείτε, αυτή η συναλλαγή θα γίνει νόμιμα χωρίς κανένα
πρόβλημα. Εάν ενδιαφέρεστε, μπορώ να σας δώσω περισσότερες πληροφορίες
σχετικά με την πρότασή μου μόλις λάβω την απάντησή σας.


Τις καλύτερες ευχές,
Κ. Sayyad Zahed.

Bug#969156: rumur FTBFS on armel/armhf/mipsel/mips64el: test failures

[Adrian Bunk]

Source: rumur
Version: 2020.05.27-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=rumur=sid

...
FAIL   basic-sandbox.m
Unexpected checker exit status -31:
FAILX  basic-sandbox.m
Unexpected checker exit status -31:
FAIL   M   basic-sandbox.m
Unexpected checker exit status -31:
FAIL   MX  basic-sandbox.m
Unexpected checker exit status -31:
FAIL  Obasic-sandbox.m
Unexpected checker exit status -31:
FAIL  O X  basic-sandbox.m
Unexpected checker exit status -31:
FAIL  OM   basic-sandbox.m
Unexpected checker exit status -31:
FAIL  OMX  basic-sandbox.m
Unexpected checker exit status -31:
FAIL D basic-sandbox.m
Unexpected checker exit status -31:
FAIL D M   basic-sandbox.m
Unexpected checker exit status -31:
FAIL DObasic-sandbox.m
Unexpected checker exit status -31:
FAIL DOM   basic-sandbox.m
Unexpected checker exit status -31:
...
FAIL - exec strace-sandbox.sh
...
--- SIGSYS {si_signo=SIGSYS, si_code=SYS_SECCOMP, si_call_addr=0xb6e84bf8, 
si_syscall=__NR_clock_gettime64, si_arch=AUDIT_ARCH_ARM} ---
+++ killed by SIGSYS +++
/<>/tests/strace-sandbox.sh: line 69: 10391 Bad system call
 strace ./model.exe
...
2794 passed, 1918 skipped, 13 failed out of 4725 total tests
make[4]: *** [CMakeFiles/check.dir/build.make:60: CMakeFiles/check] Error 1


The version in testing also started failing:
https://tests.reproducible-builds.org/debian/history/armhf/rumur.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/rumur.html

Bug#969148: fcml: FTBFS with doxygen 1.8.19

[Stephen Kitt]

Hi Paolo,

On Fri, 28 Aug 2020 10:05:33 +0200, Paolo Greppi 
wrote:
> while rebuilding the build dependencies of doxygen with the upcoming
> doxygen 1.8.19
> (https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.8.19-1_amd64-partial)
> this package FTBFS.
> 
> This is the error:
> 
> dh_doxygen: error: Doxygen documentation not found
> make[1]: *** [debian/rules:31: override_dh_installdocs-indep] Error 25
> 
> This requires further investigation; I thought I had fixed dh_doxygen with
> this commit:
> https://salsa.debian.org/debian/doxygen/-/commit/6e3577327a78d060268c7e32adac1d9b1051bf0f
> 
> But this seems to fail on your package.
> Can you find the doxygen.css, doxygen.svg and index.html files in the
> doxygen-built doc dir after the doxygen command is run by the build script ?

After building the package with doxygen from experimental, I get

$ find . -name doxygen.\*
./docs/doxygen/doxygen.stamp
./docs/doxygen/html/doxygen.css
./docs/doxygen/html/doxygen.svg
./docs/doxygen/latex/doxygen.sty
./debian/libfcml-doc/usr/share/doc/libfcml-doc/html/doxygen.css
./debian/tmp/usr/share/doc/fcml/html/doxygen.css
./debian/tmp/usr/share/doc/fcml/html/doxygen.svg

dh_doxygen is invoked with -plibfcml-doc so this happens because the SVG file
isn’t installed there. Fixing that allows the build to complete.

Regards,

Stephen


pgpOrwvcfpbSt.pgp
Description: OpenPGP digital signature

Bug#959387: [Re] paraview-dev: missing cmake vtk modules in the dev package, cannot use

[Jakob Meng]

PPPS:

ParaView installs its Python modules as well as all the VTK Python
modules as part of its CMake install process. If python3-vtk8 [1] ever
enters Debian this might cause file collisions, as both python3-paraview
and python3-vtk8 install files to the same locations and hence cannot be
co-installed. So either we skip installing VTK Python modules during
ParaView install or we install those ParaView's VTK Python modules to a
different location by setting e.g. VTK_PYTHON_SITE_PACKAGES_SUFFIX. When
skipping VTK Python module install, then we have to make sure that all
VTK-related files in ParaView and VTK packages do match exactly and have
the same patches applied. Else Python, ParaView or its Python modules
might crash or even worse cause silent data and memory corruption bugs.

Just calling 'rm -fr debian/tmp/usr/lib/python3*/dist-packages/vtk*' in
ParaView's debian/rules is not a proper workaround. ParaView 5.7 from
Debian Sid uses a development version of VTK8 (not far from VTK9
release?) [4], while Debian's dedicated VTK8 package [1] is at 8.2, so
both VTK versions have many differences.

ParaView has CMake flags to build with an external VTK install [6], but
this is not supported at least in ParaView 5.7.0 [7].

BTW, these incompatibilities affect older Debian releases as well. For
example, install both packages 'paraview-python' [2] and 'python3-vtk7'
[3] on Debian 10 (Buster), run pvpython and enter 'import vtk'. ParaView
Python will crash. So always remember to enter 'import paraview.vtk' on
Debian and Ubuntu [5].

To avoid these bugs, my reworked ParaView package does not allow
parallel installs of python3-vtk7 or python3-vtk8 [8]. Both paraview-dev
and python3-paraview install a lot (all?) of VTK's headers, libraries
and Python modules anyway.

Ref.:
[1] https://salsa.debian.org/science-team/vtk8/
[2] https://packages.debian.org/buster/paraview-python
[3] https://packages.debian.org/buster/python3-vtk7
[4]
https://salsa.debian.org/science-team/paraview/-/blob/master/VTK/CMake/vtkVersion.cmake
[5] https://blog.kitware.com/import-vtk-or-import-paraview-vtk/
[6] https://github.com/Kitware/ParaView/blob/v5.8.1/CMakeLists.txt#L218
[7] https://github.com/Kitware/ParaView/blob/v5.7.0/CMakeLists.txt#L290
[8]
https://git.inf.h-brs.de/jmeng2m/debian-package-paraview/-/blob/debian/5.7.0+ds.1-3/debian/control#L172




signature.asc
Description: OpenPGP digital signature

Bug#969058: iptables in buster-backports requires netbase >= 6.0 which is not present in archive

[Arturo Borrero Gonzalez]

On Fri, 28 Aug 2020 07:54:38 +0100 r...@synca.io wrote:
> Hi
> 
> > I just uploaded netbase 6.1~bpo10+1 to buster-backports.
> 
> it still doesnt appear to be there.

As of this writing, the package is waiting in the NEW queue before entering the
archive:

https://ftp-master.debian.org/new/netbase_6.1~bpo10+1.html

> 
> this bug utterly hosed the systems i am working on (fortunately a dev 
> network)

If in a rush, one could simply install netbase from testing. It should be a
simple operation.

> 
> imho this bug needs to be triaged as grave/critical and some kind of 
> post-mortem should happen
> 
> im actually speechless that you can release a package in an official 
> debian repository with a failing dependency like this, without any kind 
> of ci stopping you.
> 

This costs thousand of €€€ (EURs) in engineering time. Would you volunteer to do
all the work you are suggesting should be done? Or fund with money for other
folks to do so?

Please, be mindful, Debian is a community project. People do work here mostly on
a volunteer capacity. While I may understand your frustration, this kind of
yelling you are doing might destroy people's motivation in communities.

Ping me offline if you are willing to contribute with your time or money to the
project, I will gladly give you a few pointers :-)

Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327]

[SerNet Support Kevin Ivory]

Hello Markus,

we are having problems extracting a test case with debug data.
The problem arises sporadically on our customer systems with
HTTP POST or PUT, rarely with GET, sometimes with out HTTP
monitoring, sometimes with Debian updates.
Since I haven't been able to create a test case on our debug
vm system, I have created a debug file on a customer system.
Since the POST data might be critical to the customer,
is there any way to extract only the data you need?

All cases in my debug log (46 GB) seem to be of a POST
that is logged in access.log as
2020-08-27 11:29:24   1243 172.16.100.3 TAG_NONE/500 3640 POST 
http://srv1.first-businesspost.com/viper? - HIER_NONE/- text/html
The debug cache.log does contain SenderID= and Secret=

Am 18.08.20 um 21:38 schrieb Markus Koschany:

On Tue, 18 Aug 2020 13:37:30 +0200 SerNet Support Kevin Ivory
 wrote:

Hi Markus,

On Thu, 13 Aug 2020 21:56:14 +0200 Markus Koschany  wrote:

Version: 3.5.23-5+deb9u3


thanks for the work on the patches. We have two different ICAP dependent
packages. After installing squid 3.5.23-5+deb9u3, ICAP worked for
Avira ICAP, but it did not work for our squid-redirector package for
BPjM index file.

The cache.log shows
2020/08/18 07:24:04 kid1| suspending ICAP service for too many failures
2020/08/18 07:24:04 kid1| essential ICAP service is suspended: 
icap://127.0.0.1:1344/service_scanner-reqmod [down,susp,fail11]

I guess its time for me to set up a test machine for debugging output.


The default debug level shows not enough information to reproduce or
understand the problem. Please set debug_options to ALL,9 and send me
your cache.log and squid.conf file via private email.



Regards
Kevin Ivory (SerNet Support)
--
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: 0551-37-0, mailto:kont...@sernet.de
Gesch.F.: Dr. Johannes Loxen und Reinhild Jung
AG Göttingen: HR-B 2816 - http://www.sernet.de

Bug#969155: RFP: icinga database -- database for icinga 2

[Kunz David]

Package: icinga 2
Upstream Author: Icinga Development Team
License: GPLv2+
Homepage: icinga.com

icinga database is a new database backend
for icinga 2

Bug#969154: basex: Should look for Saxon-HE.jar

[Alexander Holupirek]

Hi Harri,

this is a good suggestion.
I'll have a look, when upgrading the package to the latest version.

Thanks,
Alex

> On 28. Aug 2020, at 11:26, Harri Kiiskinen  wrote:
> 
> Package: basex
> Version: 9.0.1+ds-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I would suggest that the jar Saxon-HE.jar should be added 
> to the list of jar-files looked for in all four files /usr/bin/basex*
> 
> BaseX uses Saxon in xslt-transforms, if available, and since 
> Debian includes the libsaxonhe-java package, it would be easy 
> to integrate the advanced XSLT support of Saxon 9.9 by adding 
> the corresponding jar library to the list of jars searched for.
> 
> This line seems to do the trick:
> 
> find_jars /usr/share/java/Saxon-HE.jar
> 
> Best,
> 
> Harri K.
> 
> -- System Information:
> Debian Release: 10.5
>  APT prefers stable-updates
>  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
> 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.19.0-10-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), 
> LANGUAGE=fi_FI.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages basex depends on:
> ii  default-jre [java8-runtime] 2:1.11-71
> ii  java-wrappers   0.3
> ii  openjdk-11-jre [java8-runtime]  11.0.8+10-1~deb10u1
> ii  openjdk-8-jre [java8-runtime]   8u212-b03-2~deb9u1
> 
> Versions of packages basex recommends:
> ii  libjline2-java  2.14.6-3
> 
> Versions of packages basex suggests:
> pn  libjing-java 
> ii  libtagsoup-java  1.2.1+-1
> ii  libxml-commons-resolver1.1-java  1.2-9
> 
> -- no debconf information