Bug#956074: ITP: golang-github-francoispqt-gojay -- JSON encoder/decoder with stream API

[Roger Shimizu]

control: unblock -1 by 958162 958164

Dear Alois,

I don't think this package depends on golang-github-viant-afs or
golang-github-josharian-intern

> I was working on toolbox with upstream to fix the wrong permissions issues
> without having to write a patch.
> Otherwise LGTME.

Thanks for your feedback!
uploaded to NEW.

You can upload again after upstream releases the fix.
Passing NEW queue takes some time, so it's better to upload as soon as
it gets ready.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#959505: release.debian.org: Is erlang autoremoval is necessary?

[Sergei Golovan]

Package: release.debian.org
Severity: normal

Hi release team!

Today, I've got an autoremoval mails for erlang and a whole bunch of related
packages because of #958841 (see [1] for details).

Is it really necessary to remove erlang and all its reverse dependencies,
while it's elixir-lang which is the culprit? As far as I can see, removal
of all erlang related packages (which includes elixir-lang) should lead to
moving them back except for elixir-lang which is now uninstallable.
On the other hand, just removing elixir-lang from testing achieves the same
outcome without removing/moving back many packages.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958841

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

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

Bug#957976: xdms: ftbfs with GCC-10

[John Paul Adrian Glaubitz]

Control: tags -1 +patch
Control: forwarded -1 https://gitlab.com/heikkiorsila/xdms/-/merge_requests/1

Hi!

On 4/17/20 1:13 PM, Matthias Klose wrote:
> The package fails to build in a test rebuild on at least amd64 with
> gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
> severity of this report will be raised before the bullseye release,
> so nothing has to be done for the buster release.

There is already a patch to address this issue which has been provided
by Jeff Law from GCC to upstream [1]. I'm attaching it to this bug
report.

I will update the package the next days and include the patch.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
diff --git a/src/u_deep.c b/src/u_deep.c
index e1e5dcaf6fb177ed8b58503225c6109105725b3a..095de2137a524c43a7da0874a9a8197fb4aa3906 100644
--- a/src/u_deep.c
+++ b/src/u_deep.c
@@ -17,9 +17,9 @@
 #include "getbits.h"
 
 
-INLINE USHORT DecodeChar(void);
-INLINE USHORT DecodePosition(void);
-INLINE void update(USHORT c);
+static INLINE USHORT DecodeChar(void);
+static INLINE USHORT DecodePosition(void);
+static INLINE void update(USHORT c);
 static void reconst(void);
 
 
@@ -98,7 +98,7 @@ USHORT Unpack_DEEP(UCHAR *in, UCHAR *out, USHORT origsize){
 
 
 
-INLINE USHORT DecodeChar(void){
+static INLINE USHORT DecodeChar(void){
 	USHORT c;
 
 	c = son[R];
@@ -117,7 +117,7 @@ INLINE USHORT DecodeChar(void){
 
 
 
-INLINE USHORT DecodePosition(void){
+static INLINE USHORT DecodePosition(void){
 	USHORT i, j, c;
 
 	i = GETBITS(8);  DROPBITS(8);
@@ -171,7 +171,7 @@ static void reconst(void){
 
 /* increment frequency of given code by one, and update tree */
 
-INLINE void update(USHORT c){
+static INLINE void update(USHORT c){
 	USHORT i, j, k, l;
 
 	if (freq[R] == MAX_FREQ) {
diff --git a/src/u_heavy.c b/src/u_heavy.c
index 3ec09c2cbdfd6af4bc126ef6c3f005692a02ce6e..6cacac593f7d19c02f09ffa0b0f61b2cd2d239ba 100644
--- a/src/u_heavy.c
+++ b/src/u_heavy.c
@@ -30,8 +30,8 @@ USHORT heavy_text_loc, heavy_lastlen;
 
 static USHORT read_tree_c(void);
 static USHORT read_tree_p(void);
-INLINE USHORT decode_c(void);
-INLINE USHORT decode_p(void);
+static INLINE USHORT decode_c(void);
+static INLINE USHORT decode_p(void);
 
 
 
@@ -74,7 +74,7 @@ USHORT Unpack_HEAVY(UCHAR *in, UCHAR *out, UCHAR flags, USHORT origsize){
 
 
 
-INLINE USHORT decode_c(void){
+static INLINE USHORT decode_c(void){
 	USHORT i, j, m;
 
 	j = c_table[GETBITS(12)];
@@ -96,7 +96,7 @@ INLINE USHORT decode_c(void){
 
 
 
-INLINE USHORT decode_p(void){
+static INLINE USHORT decode_p(void){
 	USHORT i, j, m;
 
 	j = pt_table[GETBITS(8)];

Bug#959481: alpine: does not connect with TLS to smtp/imap server

[Βασίλειος A . Ζοῦκος]

On Sat, 2 May 2020, Unit 193 wrote:


severity -1 normal
tags -1 + unreproducible
stop

Howdy,

When filing bugs, please at the very least take the time to fill out the the 
template additionally providing any details that may be used to assist with 
your problem.


I have been using this version of alpine for some time now (indeed, it fixes 
SNI issues) and have no problems connecting to TLS sources.  Perhaps take a 
minute to review your configuration and see if there's any oddities 
preventing you from connecting, and if at all possible provide any details 
that might further shed light on the problem.


~Unit 193
Unit193 @ freenode
Unit193 @ OFTC


To be more precise:
On the same machine with the same  debian distribution, I retain two
executable versions for alpine:
1. alpine ver. 2.20
2. alpine ver. 2.22
Using the same alpine configuration (for ver 2.20, 2.22):
1. I am able to connect via TLS to imap/smtp servers and perform all the
e-mail tasks using alpine ver. 2.20
2. I can't connect via TLS to the same imap/smtp servers using alpine 2.22.
Attached are parts of the pine-debug files produced by the command:
alpine_2_XX -d 9  (XX=20,22)

Many thanks,

19:40:26.561978
Debug output of the Alpine program (debug=9 debug_imap=4). Version 2.20 (DEB 67 
2015-01-07)
Thu Apr 30 19:40:26 2020


19:40:26.562098
Starting after the reading_pinerc calls, the data in this file should
be encoded as UTF-8. Before that it will be in the user's native charset.

19:40:26.562150
Debug file: /home/vzoukos/.pine-debug1 (level=9 imap=4)

19:40:26.562187
 
"/usr/bin/alpine_2_20" "-d" "9" (PID=1191)


19:40:26.562241
Setting home dir from $HOME: "/home/vzoukos"

19:40:26.571837

 -- init_pinerc --

>>+ Ommited section
<<- Ommited section

19:40:31.787358
start_after() created c0d37700: done

19:40:31.787475
pine_mail_open: opening 
"{imap.otenet.gr/IMAP/novalidate-cert/norsh/user=vzoukos}INBOX" (stream was 
NULL) openflags=0x500  SP_USERFLDR SP_USEPOOL (19:40:31.787475)

19:40:31.787587
sp_stream_get({imap.otenet.gr/IMAP/novalidate-cert/norsh/user=vzoukos}INBOX): 
SP_MATCH

19:40:31.787650
sp_stream_get: no match found

19:40:31.787709
sp_stream_get({imap.otenet.gr/IMAP/novalidate-cert/norsh/user=vzoukos}INBOX): 
SP_SAME SP_TEMPUSE

19:40:31.787770
sp_stream_get: no match found

19:40:31.787827
pine_mail_open: there is an empty slot to use

19:40:32.007878
IMAP 19:40:32 4/30 mm_log babble: Trying IP address [62.103.147.209]

19:40:32.061157
IMAP DEBUG 19:40:32.061157: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR 
LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN] OTENET ready

19:40:32.061298
imap_cmd({imap.otenet.gr/IMAP/novalidate-cert/norsh/user=vzoukos}INBOX, 
STARTTLS, 0x0)

19:40:32.061385
IMAP DEBUG 19:40:32.061385:  STARTTLS

19:40:32.082356
IMAP DEBUG 19:40:32.082356:  OK Begin TLS negotiation now.

19:40:32.149887
imap_cmd({imap.otenet.gr/IMAP/novalidate-cert/norsh/user=vzoukos}INBOX, 
CAPABILITY, 0x0)

19:40:32.150002
IMAP DEBUG 19:40:32.150002: 0001 CAPABILITY

19:40:32.170860
IMAP DEBUG 19:40:32.170860: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR 
LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN

19:40:32.170942
IMAP DEBUG 19:40:32.170942: 0001 OK Pre-login capabilities listed, 
post-login capabilities have more.

19:40:32.195544
IMAP DEBUG 19:40:32.195544: 0002 AUTHENTICATE PLAIN

19:40:32.218606
IMAP DEBUG 19:40:32.218606: + 

19:40:32.218719
mm_login_work trial=0 user=vzoukos service=imap

19:40:32.218790
mm_login: host=imap.otenet.gr

19:40:32.218850
imap_get_passwd: checking user=vzoukos alt=1 host=imap.otenet.gr

19:40:32.218911
imap_get_passwd: no match

19:40:32.218968
read_passfile

19:40:32.219027
Looking for passfile "/home/vzoukos/.pine-passfile"

19:40:32.219154
=== optionally_enter called ===

>>+ Ommited section
<<- Ommited section

19:40:03.172282
Debug output of the Alpine program (debug=9 debug_imap=4). Version 2.22 (DEB 
394 2020-01-19)
Thu Apr 30 19:40:03 2020


19:40:03.172405
Starting after the reading_pinerc calls, the data in this file should
be encoded as UTF-8. Before that it will be in the user's native charset.

19:40:03.172456
Debug file: /home/vzoukos/.pine-debug1 (level=9 imap=4)

19:40:03.172498
 
"/usr/bin/alpine" "-d" "9" (PID=1185)


19:40:03.172554
Setting home dir from $HOME: "/home/vzoukos"

19:40:03.181443

 -- init_pinerc --

>>+ Ommited section
<<- Ommited section

19:40:10.252281
start_after() created ba738700: done

19:40:10.252371
pine_mail_open: opening 
"{imap.otenet.gr/IMAP/novalidate-cert/norsh/user=vzoukos}INBOX" (stream was 
NULL) openflags=0x500  SP_USERFLDR SP_USEPOOL (19:40:10.252371)

19:40:10.252459
sp_stream_get({imap.otenet.gr/IMAP/novalidate-cert/norsh/user=vzoukos}INBOX): 
SP_MATCH

19:40:10.252522
sp_stream_get: no match found

19:40:10.252581
sp_stream_get({imap.otenet.gr/IMAP/novalidate-cert/norsh/user=vzoukos}INBOX): 
SP_SAME SP_TEMPUSE

19:40:10.252642
sp_stream_get: no match foun

Bug#959504: select2.js: run upstream tests

[merkys]

Source: select2.js
Severity: wishlist
Control: block -1 by 959411

Upstream uses grunt-contrib-qunit to run automated tests in headless Web
browser. These tests should be used in build time and autopkgtest to
ensure the integrity of the package.

Andrius

Bug#959503: salmon breaks trinityrnaseq autopkgtest: /usr/bin/ParaFly -c recursive_trinity.cmds -CPU 2 -v -shuffle died with ret 256

[Paul Gevers]

Source: salmon, trinityrnaseq
Control: found -1 salmon/1.2.1+ds1-1
Control: found -1 trinityrnaseq/2.6.6+dfsg-6
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of salmon the autopkgtest of trinityrnaseq fails in
testing when that autopkgtest is run with the binary packages of salmon
from unstable. It passes when run with only packages from testing. In
tabular form:

   passfail
salmon from testing1.2.1+ds1-1
trinityrnaseq  from testing2.6.6+dfsg-6
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of salmon to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=salmon

https://ci.debian.net/data/autopkgtest/testing/amd64/t/trinityrnaseq/5248098/log.gz


We are sorry, commands in file: [FailedCommands] failed.  :-(

Error, cmd: /usr/bin/ParaFly -c recursive_trinity.cmds -CPU 2 -v
-shuffle  died with ret 256 at ../../Trinity line 2589.
main::process_cmd("/usr/bin/ParaFly -c recursive_trinity.cmds -CPU 2 -v
-shuffle ") called at ../../Trinity line 3226
main::run_partitioned_cmds("recursive_trinity.cmds") called at
../../Trinity line 2247

main::run_recursive_trinity("/tmp/autopkgtest-lxc.v050vbja/downtmp/autopkgtest_tmp/trinity"...)
 called at ../../Trinity line 2009

main::run_chrysalis("/tmp/autopkgtest-lxc.v050vbja/downtmp/autopkgtest_tmp/trinity"...,
 "/tmp/autopkgtest-lxc.v050vbja/downtmp/autopkgtest_tmp/trinity"..., 200, 500, 
"RF", "/tmp/autopkgtest-lxc.v050vbja/downtmp/autopkgtest_tmp/trinity"..., 
"/tmp/autopkgtest-lxc.v050vbja/downtmp/autopkgtest_tmp/trinity"...) called at 
../../Trinity line 1672
main::run_Trinity() called at ../../Trinity line 1325
eval {...} called at ../../Trinity line 1324

Trinity run failed. Must investigate error above.
make[1]: *** [Makefile:7: test_all] Error 2
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.v050vbja/downtmp/autopkgtest_tmp/trinityrnaseq/sample_data/test_Trinity_Assembly'
make: *** [Makefile:6: test_trin_assembly] Error 2



signature.asc
Description: OpenPGP digital signature

Bug#959499: Enable riscv64 build

[Ryan Finnie]

Source: efivar
Version: 37-2

UEFI RISC-V support is coming to the Linux kernel soon[0].  Upstream
GRUB already has RISC-V support and Linux loader support will be added
along with kernel support[1].  To enable building grub2 on riscv64,
efibootmgr and efivar will need to be built.  No additional changes are
needed other than adding riscv64 to the package Architecture:s (see
attached debdiff).

Thank you!

[0] https://lkml.org/lkml/2020/4/20/1800
[1] https://lists.gnu.org/archive/html/grub-devel/2020-04/msg00203.html

diff -Nru efivar-37/debian/changelog efivar-37/debian/changelog
--- efivar-37/debian/changelog  2019-03-01 09:55:07.0 -0800
+++ efivar-37/debian/changelog  2020-05-02 19:02:36.0 -0700
@@ -1,3 +1,9 @@
+efivar (37-3) unstable; urgency=medium
+
+  * Enable riscv64 build
+
+ -- Ryan Finnie   Sat, 02 May 2020 19:02:36 -0700
+
 efivar (37-2) unstable; urgency=medium
 
   * Cherry-pick fix from upstream:
diff -Nru efivar-37/debian/control efivar-37/debian/control
--- efivar-37/debian/control2019-03-01 09:40:21.0 -0800
+++ efivar-37/debian/control2020-05-02 19:02:08.0 -0700
@@ -11,7 +11,7 @@
 
 Package: libefivar-dev
 Section: libdevel
-Architecture: amd64 i386 ia64 armhf arm64 armel x32
+Architecture: amd64 i386 ia64 armhf arm64 armel x32 riscv64
 Multi-Arch: same
 Depends: libefivar1 (= ${binary:Version}), ${misc:Depends}
 Description: Development headers for libefivar
@@ -19,7 +19,7 @@
 
 Package: libefiboot-dev
 Section: libdevel
-Architecture: amd64 i386 ia64 armhf arm64 armel x32
+Architecture: amd64 i386 ia64 armhf arm64 armel x32 riscv64
 Multi-Arch: same
 Depends: libefiboot1 (= ${binary:Version}), ${misc:Depends}
 Conflicts: libefivar-dev (<< 27-1)
@@ -29,14 +29,14 @@
 
 Package: efivar
 Section: admin
-Architecture: amd64 i386 ia64 armhf arm64 armel x32
+Architecture: amd64 i386 ia64 armhf arm64 armel x32 riscv64
 Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends}, libefivar1 (= ${binary:Version}), 
libefiboot1 (= ${binary:Version})
 Description: Tools to manage UEFI variables
  efivar provides a simple command line interface to the UEFI variable facility.
 
 Package: libefiboot1
-Architecture: amd64 i386 ia64 armhf arm64 armel x32
+Architecture: amd64 i386 ia64 armhf arm64 armel x32 riscv64
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -45,7 +45,7 @@
  Library to allow for the manipulation of UEFI variables related to booting.
 
 Package: libefivar1
-Architecture: amd64 i386 ia64 armhf arm64 armel x32
+Architecture: amd64 i386 ia64 armhf arm64 armel x32 riscv64
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}


signature.asc
Description: OpenPGP digital signature

Bug#959498: Enable riscv64 build

[Ryan Finnie]

Source: efibootmgr
Version: 17-1

UEFI RISC-V support is coming to the Linux kernel soon[0].  Upstream
GRUB already has RISC-V support and Linux loader support will be added
along with kernel support[1].  To enable building grub2 on riscv64,
efibootmgr and efivar will need to be built.  No additional changes are
needed other than adding riscv64 to the package Architecture:s (see
attached debdiff).

Thank you!

[0] https://lkml.org/lkml/2020/4/20/1800
[1] https://lists.gnu.org/archive/html/grub-devel/2020-04/msg00203.html
diff -Nru efibootmgr-17/debian/changelog efibootmgr-17/debian/changelog
--- efibootmgr-17/debian/changelog  2020-02-19 14:13:57.0 -0800
+++ efibootmgr-17/debian/changelog  2020-05-02 19:00:12.0 -0700
@@ -1,3 +1,9 @@
+efibootmgr (17-2) unstable; urgency=medium
+
+  * Enable riscv64 build
+
+ -- Ryan Finnie   Sat, 02 May 2020 19:00:12 -0700
+
 efibootmgr (17-1) unstable; urgency=medium
 
   [ Steve McIntyre ]
diff -Nru efibootmgr-17/debian/control efibootmgr-17/debian/control
--- efibootmgr-17/debian/control2020-02-19 14:13:57.0 -0800
+++ efibootmgr-17/debian/control2020-05-02 18:59:57.0 -0700
@@ -9,7 +9,7 @@
 Vcs-Browser: https://salsa.debian.org/efi-team/efibootmgr
 
 Package: efibootmgr
-Architecture: amd64 i386 ia64 armhf arm64 armel x32
+Architecture: amd64 i386 ia64 armhf arm64 armel x32 riscv64
 Multi-Arch: foreign
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}


signature.asc
Description: OpenPGP digital signature

Bug#959502: multitail: new version 6.5.0 available

[Kenyon Ralph]

Package: multitail
Version: 6.4.2-3+b1
Severity: normal

Dear Maintainer,

Version 6.5.0 of multitail has been released.
https://www.vanheusden.com/multitail/download.php

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

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

Versions of packages multitail depends on:
ii  libc6 2.28-10
ii  libncursesw6  6.1+20181013-2+deb10u2
ii  libtinfo6 6.1+20181013-2+deb10u2

multitail recommends no packages.

multitail suggests no packages.

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

-- no debconf information

Bug#657401: experiment to build packages out-of-tree

[Philipp Hahn]

This weekend I has a look at this issue and mostly got it working, but
at the end failed on two issues:

1. `dpkg-source --build $path` allows absolute paths. The `.orig.tar`
files must be placed in the directory from where `dpkg-source` is
invoked from.

2. Most packages nowadays use debhelper, so `dh_builddeb` is used to
invoke `dpkg-deb`. The former has the option `--destdir` but that one
clashes with the same option being used by `dh_auto_install`, so it MUST
NOT be passed through `$DH_OPTIONS`.

3. `dpkg-genbuildinfo` and `dpkg-genchanges` both have the option `-u`
to specify a different directory for the build artifacts.

4. The last missing part is the hard-coded path for the `.changes` file:
> 593 my $chg = "../$pva.changes";
`dpkg-buildpackage` has no option to change that.

This is my summary for now as of May 2020.
More details of my experiment at
.

Bug#959412: node-puppeteer: uses @types/node v10

[merkys]

Hello,

Packaging puppeteer at least seems doable. I have managed to get the
unit tests passing with Debian-provided chromium, of course with cutting
some edges by installing missing dependencies via 'npm i'. The most
troubling part seems to be the usage of @types/node v10 (Debian has
v13), and I have no idea how to resolve this.

I have pushed my packaging efforts to salsa [1] should anyone be interested.

[1] https://salsa.debian.org/js-team/node-puppeteer

Andrius

Bug#959465: spoa - fixes to move forward with Gcc 10

[Andreas Tille]

Control: tags -1 upstrean
Control: forwarded -1 https://github.com/rvaser/bioparser/pull/7

Hi Étienne,

thank you for your investigation.  If you add your suggested fix to
libbioparser-dev packaging git as a patch to fix bug #959465 I would
upload and we could fix those other bugs (if I understood correctly).

Kind regards

 Andreas.

On Sat, May 02, 2020 at 10:06:22PM +0200, Étienne Mollier wrote:
> Greetings Gentlemen,
> 
> Sorry, I believe I haven't mentionned that earlier, but I
> brought some changes in the package "spoa" as well, to move
> forward with #957836 (initially, it was to occupy the time
> during "praat" building, which took quite some time).  Actually,
> this is how I spotted the issue with the "libbioparser-dev", and
> documented it in #959465.
> 
> There are a few details I'm still uncomfortable with, such as
> how would an attempt to close the bug #957836 behave if #959465
> is still present to block the correction.  I'm under the
> impression I might have been a bit fast forward, but for your
> information.
> 
> Have a good week end,  :)
> -- 
> Étienne Mollier 
> Fingerprint:  5ab1 4edf 63bb ccff 8b54  2fa9 59da 56fe fff3 882d
> Help find cures against the Covid-19 !  Give CPU cycles:
>   * Rosetta@home: https://boinc.bakerlab.org/rosetta/
>   * Folding@home: https://foldingathome.org/



-- 
http://fam-tille.de

Bug#637348: +1 Vote for Icecat in Debian

[meraz]

"I'm shocked no one packaged Icecat after all these years. Icecat is
absolutely a package to have in Debian, and it's more in line with DFSG
than Firefox is. This is the browser Debian should have used all these
years instead of Iceweasel. Icecat's additional features over Firefox
are all opt-in, so anyone who don't want them will have no problem, and
there is no telemetry enabled by default. It's also worth noting that
adopting Icecat as the default browser in Debian would avoid any
conflict with Mozilla in the future (although they appear to be solved
now, no one can predict what will happen in the future) and will join
the efforts of the GNU team with the Debian team for a better free
browser that will get more attention in all the Debian-based distributions."

I didn't said that but I agree with him, iceCat has been there for a while and 
it's a good alternative if you like firefox, you're concern about privacy and 
all that stuff and you don't know much about compiling source code or patching 
firefox (That's my case), please if you can... Make installing IceCat in debian 
a thing...

Bug#959501: luabind: std::terminate called on luabind:error

[Andreas Grob]

Source: luabind
Version: 0.9.1+git20150823+dfsg-3
Severity: important
Tags: patch upstream

Dear Maintainer,

the upstream snapshot (76d4061) fixes some instances of std::terminate being 
called when luabind::error is thrown
in a destructor by utilizing a macro that evaluates to noexcept(false). 
Unfortunately, it seems one of those
instances has not been fixed.

In luabind/detail/call_member.hpp:233 LUABIND_MAY_THROW needs to be
attached to ~proxy_member_void_caller() to fix this bug.

I have also reported this issue to the upstream source:
https://github.com/ValyriaTear/luabind/pull/2

For your convenience I will attach a patch.


Kind regards,
Andreas Grob


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

Kernel: Linux 5.5.0-2-amd64 (SMP w/6 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
Author: Andreas Grob 
Description: Prevent std::terminate in ~proxy_member_void_caller()

If luabind::error is thrown in ~proxy_member_void_caller() std::terminate will 
be called, unless we set noexcept(false).

This should complement the fix made in upstream commit 94fedc6.

I have also suggested this fix in upstream at 
https://github.com/ValyriaTear/luabind/pull/2

Index: luabind-0.9.1+git20150823+dfsg/luabind/detail/call_member.hpp
===
--- luabind-0.9.1+git20150823+dfsg.orig/luabind/detail/call_member.hpp
+++ luabind-0.9.1+git20150823+dfsg/luabind/detail/call_member.hpp
@@ -230,7 +230,7 @@ namespace luabind
 rhs.m_called = true;
 }

-~proxy_member_void_caller()
+~proxy_member_void_caller() LUABIND_MAY_THROW
 {
 if (m_called) return;

Bug#959500: misleading 'You need to be root' when Linux is in Lockdown mode

[John Scott]

Package: flashrom
Version: 1.2-5
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

It seems this is because I use my system with Secure Boot, so Lockdown
mode is enabled by default, but in principle I think it could be enabled by
anyone (maybe it's used by SELinux users as well)

# flashrom -p internal -r woo
flashrom v1.2 on Linux 5.5.0-2-amd64 (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
ERROR: Could not get I/O privileges (Operation not permitted).
You need to be root.
Error: Programmer initialization failed.

# dmesg | tail -3
[38836.060931] Lockdown: flashrom: raw io port access is restricted; see 
https://wiki.debian.org/SecureBoot
[38851.136762] Lockdown: flashrom: raw io port access is restricted; see 
https://wiki.debian.org/SecureBoot
[38865.113982] Lockdown: flashrom: raw io port access is restricted; see 
https://wiki.debian.org/SecureBoot

flashrom should say the actual semantic of the problem, that it couldn't
access a device, instead of its best guess.

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

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

Versions of packages flashrom depends on:
ii  libc6 2.30-4
ii  libftdi1-21.4-2+b2
ii  libpci3   1:3.6.4-1
ii  libusb-1.0-0  2:1.0.23-2

flashrom recommends no packages.

flashrom suggests no packages.

- -- debconf-show failed

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQT287WtmxUhmhucNnhyvHFIwKstpwUCXq45lgAKCRByvHFIwKst
pxjXAQDidnYRdO0NEDDkPxcmxgT/+zsHnCovWtWTjGsbUS67XQEA9xFDpObphlMa
pb8aTi0E6hnwOqvk7p9qJDV9tf1IWg0=
=1538
-END PGP SIGNATURE-

Bug#956074: ITP: golang-github-francoispqt-gojay -- JSON encoder/decoder with stream API

[Aloïs Micard]

On Sun, 3 May 2020 03:12:17 +0900 Roger Shimizu  wrote:
> control: tags -1 +pending
> 
> Dear Alois,
> 
> Thank for your ITP!
> 
> Since it's also an indirect dependency for my another package, I used
> dh-make-golang to create the package.
> I already push to salsa:
> - https://salsa.debian.org/go-team/packages/golang-github-francoispqt-gojay
> 
> If you have anything to add, please go ahead.
> I can sponsor your upload. Please ping me by replying to this email.
> 
> Otherwise, I'll try to upload in a week or so. Thank you!
> 
> Cheers,
> -- 
> Roger Shimizu, GMT +9 Tokyo
> PGP/GPG: 4096R/6C6ACD6417B3ACB1
> 
> 

Hello there,

The package shouldn't build since many dependencies are missing 
(I'm working with upstream to fix errors in some of them before packaging them)

This will cause problem to the upload no? 
How did you build the package with the missing dependencies?

Regards
-- 
Aloïs Micard 

GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2



signature.asc
Description: OpenPGP digital signature

Bug#959497: dircolors from coreutils is missing glob pattern `TERM putty*`

[Tobias Wendorff]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: coreutils
Version: 8.30-3

`src/dircolors.hin` lists TERM entries, which can be glob patterns,
to match against the TERM environment variable to determine if it
is colorizable.

It also lists `TERM putty`, rather than the expected `TERM putty*`.
Right now, `TERM putty-256color` (from ncurses-term) gets ignored,
although it is capable of displaying colors and widely used by
Putty users.

I suggest to fix the glob pattern in `src/dircolors.hin`, also
in upstream.
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEPELrVvCcCbgs2v/SRcqbzr8zQfYFAl6uGxkACgkQRcqbzr8z
Qfb3VggAyzrsbCE/Ke6xA5a8hYTW/3AOoqGED3m/HgbkmkaBEbsYCW5pTAssomP5
yfiPZXsx8GlcwTNXlZyKKnpciXly2FAGkkJxJxCw2TJezEVzDeWZkaoxhpkHhsq0
+S7aMbTxnw9LF49jt30WmEIsMK8uQBQYxwVV8vkEb9PfrESd+aGAkxhWD0ytEtXI
y52z9IzSAf4F8GSAaEJMKL4B33S+YQ3OcHT3TnEuaoC1vmhQkGAOkgvrr32wHLcM
uwJ5INvu/oR8en12FRdrjlm6XGKFTJG5Tw5S8FWx/9D7HCOVtO1CM9x8BA3nutDm
MaWDSWN0nIpzkgSJ2mK4xWPYqWNaTg==
=EryE
-END PGP SIGNATURE-

Bug#956074: ITP: golang-github-francoispqt-gojay -- JSON encoder/decoder with stream API

[Aloïs Micard]

My bad, just noticed that you have packaged the missing dependencies too.

I was working on toolbox with upstream to fix the wrong permissions issues 
without having to write a patch.

Otherwise LGTME.

Thanks
-- 
Aloïs Micard 

GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2



signature.asc
Description: OpenPGP digital signature

Bug#959434: ITP: awf-gtk2 -- A widget factory is a theme preview application

[Paul Wise]

On Sat, 02 May 2020 12:47:42 +0200 luigifab wrote:

> This package include the gtk2 version.

Debian is attempting to remove GTK 2, so it would be best to not
introduce new packages that require GTK 2.

https://lists.debian.org/msgid-search/20200429093827.ga770...@espresso.pseudorandom.co.uk

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#959496: debian-changelog-line-too-long joins lines unnecessarily

[Jelmer Vernooij]

Package: lintian-brush
Version: 0.61
Severity: normal

In
https://salsa.debian.org/installer-team/cdebconf/-/merge_requests/3#note_159698,
lintian-brush tried to wrap some long lines but joined lines unnecessarily in
the process:

It changed:

- Sort translated choices when a select/multiselect template contains
  a line Listorder: lexicographic
  If some Choices items must not be sorted, they can be prepended 
with
  an exclamation mark.  Adding a comment is a good idea to let
  translators know why this sign has been put here:
_Choices: ${FOO}, !Other[ You only have to translate Other, 
remove the exclamation mark and this comment between brackets]
  Currently text, newt, slang and gtk frontends support this 
feature.


to:

- Sort translated choices when a select/multiselect template contains a line
  Listorder: lexicographic If some Choices items must not be 
sorted, they
  can be prepended with an exclamation mark.  Adding a comment is a 
good
  idea to let translators know why this sign has been put here:   
_Choices:
  ${FOO}, !Other[ You only have to translate Other, remove the 
exclamation
  mark and this comment between brackets] Currently text, newt, 
slang and
  gtk frontends support this feature.

(I hope that doesn't get mangled because it's in an email).

It should have broken the long line but not joined the other lines.

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

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

Versions of packages lintian-brush depends on:
ii  devscripts   2.20.3
ii  python3  3.8.2-3
ii  python3-breezy   3.0.2-5+b1
ii  python3-debian   0.1.37
ii  python3-distro-info  0.23
ii  python3-dulwich  0.19.15-1+b1
ii  python3-iniparse 0.4-3
ii  python3-levenshtein  0.12.0-5+b1
ii  python3-pkginfo  1.4.2-3
ii  python3-ruamel.yaml  0.15.89-3+b2

Versions of packages lintian-brush recommends:
ii  dos2unix   7.4.0-2
ii  gpg2.2.20-1
ii  libdebhelper-perl  13
ii  lintian2.69.0
ii  python3-asyncpg0.20.1-1+b1
ii  python3-pyinotify  0.9.6-1.3

Versions of packages lintian-brush suggests:
pn  gnome-pkg-tools
ii  postgresql-common  214

-- no debconf information

Bug#959484: grub-common: typos in /etc/grub.d/05_debian_theme

[Steve McIntyre]

On Sat, May 02, 2020 at 11:01:05PM +0200, Vincent Lefevre wrote:
>Package: grub-common
>Version: 2.04-7
>Severity: minor
>
>There are typos in "/etc/grub.d/05_debian_theme":
>
># For plymouth backward compatiblity. Can be removed
>
>should be "compatibility"
>
># If so, we can remove the cache file (if any). Otherwise the backgound
>  ^
>should be "background"

Thanks! Just fixed in git now...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Every time you use Tcl, God kills a kitten." -- Malcolm Ray

Bug#959495: ITP: dpaste -- Pastebin using OpenDHT distributed hash table

[Simon Désaulniers]

Package: wnpp
Severity: wishlist
Owner: Simon Désaulniers 

* Package name: dpaste
  Version : 0.3.3
  Upstream Author : Simon Désaulniers 
* URL : https://github.com/sim590/dpaste
* License : GPL
  Programming Lang: C++
  Description : Pastebin using OpenDHT distributed hash table

A distributed pastebin which requires no central server to paste your files (up
to a size of 64KiB).

This package would be useful for exchanging small files to be shared
momentarily, for e.g. on IRC or other sorts of group discussion platforms. The
program works using a distributed hash table, therefore it doesn't suffer from
limitations of centralized software like inaccessibility or censorship. The
usage of this program is also lightweight and therefore removes the need for a
central server to carry the burden of maintaining a service which is completely
achievable through light peer-to-peer software.

I have already created a package for this and I will close this bug soon.

-- 
Simon Désaulniers
sim.desaulni...@gmail.com


signature.asc
Description: PGP signature

Bug#959477: ITP: ckeditor3 -- Javascript rich text editor for embedding into websites (v3)

[Mike Gabriel]

Package: wnpp
Severity: wishlist
Owner: Mike Gabriel 

* Package name: ckeditor3
  Version : 3.6.6.1
  Upstream Author : Frederico Knabben
* URL : http://ckeditor.com/download
* License : GPL-2+
  Programming Lang: Javascript
  Description : Javascript rich text editor for embedding into websites (v3)

 I plan to re-upload ckeditor3 to Debian as part of my initiative to
 re-provide Horde in Debian.
 .
 Unfortunately, Horde upstream has still not moved on to ckeditor4, thus this
 old version of ckeditor is required for the interim.
 .
 Before Debian 11 gets released I plan to provide a patch to Horde Upstream
 that fixes this problem.

Bug#601023: Greetings From Miss Pamela Render Please I Need Your Urgent Reply!

[Miss Pamela Render]

Greetings From Miss Pamela Render Please I Need Your Urgent Reply!

I'm Pamela Render, from USA. I am a highly motivated and willing to learn, I'm 
also hard working lady, very relaible. I really want to establish mutual 
friendship with you, I will introduce myself better as soon as i receive your 
email response.

Kind regards
Miss Pamela Render

Bug#959493: cmake: ignores CXXFLAGS when building CMakeCXXCompilerABI.cpp, causes blhc error

[nicoo]

Package: src:cmake
Version: 3.16.3-2
Severity: important
Tags: upstream
Control: clone -1 -2
Control: reassign -2 debhelper
Control: retitle  -2 debhelper: Do not set CMAKE_AUTOGEN_VERBOSE=NO
Control: severity -2 normal
Control: found -2 12.10
Control: found -2 13
Control: affects -1 debhelper

Dear maintainers,


CMake compiles /usr/share/cmake-*/Modules/CMakeCXXCompilerABI.cpp during the
build of a C++ projects, several times, and ignoring the CXXFLAGS.
This behaviour is likely defined in
 
/usr/share/cmake-*/Modules/{CMakeTestCXXCompiler,Compiler/{Intel,GNU,QCC}}.cmake

In addition to being a (presumably benign?) correctness issue, this is about to
become a notable inconvenience for maintainers of C++ packages in Debian whose
buildsystem is CMake:
- starting in debhelper 12.10 (uploaded 2020-03-24), CMAKE_AUTOGEN_VERBOSE=ON
  is set by default for all packages that use CMake ;
- CMake then logs the compiler invocations for CMakeCXXCompilerABI.cpp;
- blhc (build log hardening checker) raises (correctly so) an error,
  as C++ code was built without the required flags.
- the blhc failure is surfaced to the maintainer in many places:
  Salsa CI, tracker.d.o, qa.d.o, ...

After discussion with nthykier, he suggested rolling back the change in dh
(commit 2f88a603001a32b596389b8b031489960e30a9e9) until this issue is fixed
in CMake.  As such I am leaving a copy of this bug report against dh.


Many thanks to Andreas Noteng, whose package scantailor-advanced (which I
am sponsoring) is where I first encountered the issue, and who bissected
the problem down to that specific commit in debhelper.


Best,

  nicoo

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

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

Versions of packages cmake depends on:
ii  cmake-data3.16.3-2
ii  libarchive13  3.4.0-2
ii  libc6 2.30-4
ii  libcurl4  7.68.0-1
ii  libexpat1 2.2.9-1
ii  libgcc-s1 10-20200418-1
ii  libjsoncpp1   1.7.4-3.1
ii  librhash0 1.3.9-1
ii  libstdc++610-20200418-1
ii  libuv11.35.0-2
ii  procps2:3.3.16-4
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages cmake recommends:
ii  gcc   4:9.2.1-3.1
ii  make  4.2.1-1.2

Versions of packages cmake suggests:
pn  cmake-doc
ii  ninja-build  1.10.0-1

-- no debconf information

Bug#959481: alpine: does not connect with TLS to smtp/imap server

[Unit 193]

severity -1 normal
tags -1 + unreproducible
stop

Howdy,

When filing bugs, please at the very least take the time to fill out the the 
template additionally providing any details that may be used to assist with your 
problem.


I have been using this version of alpine for some time now (indeed, it fixes SNI 
issues) and have no problems connecting to TLS sources.  Perhaps take a minute 
to review your configuration and see if there's any oddities preventing you from 
connecting, and if at all possible provide any details that might further shed 
light on the problem.


~Unit 193
Unit193 @ freenode
Unit193 @ OFTC

Bug#959491: RM: getlive -- RoQA; Upstream Dead; Not Working Anymore

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: rm
Control: clone -1 -2
Control: tags -2 = stretch
Control: usertags -2 rm

On Tue, 18 Feb 2020 15:56:18 -0500 Boyuan Yang 
wrote in #951617:
> Package: ftp.debian.org
> 
> Dear FTP Masters,
> 
> As described in https://bugs.debian.org/950452 , the upstream of package
> getlive no longer maintains it since 2014 due to hotmail live's contstantly
> breaking changes. As a result, package getlive has been broken since then. I
> believe we should have it removed from Debian archive since it is really
> useless now.

Let's follow sid and do the same in (old-)stable.

Andreas

Bug#959490: elinks cookie lost when path= equal to request path

[Ian Jackson]

Package: elinks
Version: 0.13.1-1
Tags: patch

I found that elinks was not able to work with my installation of a
(not in Debian) web service, disorder [1].  This is because disorder
sends a path= attribute in its Set-Cookie header which is precisely
equal to the path in all of its URLs.

After some debugging, and some source diving, I discovered that the
cause was that elinks mishandles this case.  Patch attached.

Thanks for your attention.

If you have a good relationship with upstream I would appreciate it if
you'd pass it on.  If you would prefer me to do that I can look up how
to do it.

The patch applies cleanly as far back as buster, at least.

Regards,
Ian.

[1] https://www.greenend.org.uk/rjk/disorder/

>From a36579b07058b6bfcb5f7472e404c354bfa2813d Mon Sep 17 00:00:00 2001
From: Ian Jackson 
Date: Sat, 2 May 2020 19:40:06 +0100
Subject: [PATCH] cookies: Properly handle cookie path= equal to request path

The code in cookies.c would arrange that c->path would always contain
a string ending in "/".  This may have been an attempt to make it
easier to do a proper subpath check in is_path_prefix.

Howver, the overall result is wrong in the case
   Set-Cookie: ;path=/some/thing
and then later
   http://site.example.com/some/thing

c->path gets set to "/some/thing/" which doesn't pass the test in
is_path_prefix.

The precise required algorithm is described in RFC6265 5.1.4.  The
existing code fails to implement the first of the three bulleted
conditions at the end of 5.1.4.

The trailing "/" is actually not so helpful for this.  It is more
convenient to change is_path_prefix to do subpath matching directly:
we change it to insist that the supposed path prefix is a textual
prefix of the request path, *and* that this happens at a path segment
boundary: ie at '/' or end of string.[1]

Accordingly, we no longer add "/" to the cookie path.  When we strip
the final path element we strip the "/" too.  We still insert a "/" if
the path was empty.

[1] It is not 100% clear to me what "path" (URI_PATH) is but I think
it does not include any query parameters.  If I am wrong about that
then '?' should be tolerated too.

CC: Mark Wooding 
Signed-off-by: Ian Jackson 
---
 src/cookies/cookies.c | 7 +++
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/src/cookies/cookies.c b/src/cookies/cookies.c
index 993437d..ce30159 100644
--- a/src/cookies/cookies.c
+++ b/src/cookies/cookies.c
@@ -356,8 +356,7 @@ set_cookie(struct uri *uri, unsigned char *str)
unsigned char *path_end;
 
case HEADER_PARAM_FOUND:
-   if (!path[0]
-   || path[strlen(path) - 1] != '/')
+   if (!path[0])
add_to_strn(&path, "/");
 
if (path[0] != '/') {
@@ -374,7 +373,7 @@ set_cookie(struct uri *uri, unsigned char *str)
 
path_end = strrchr((const char *)path, '/');
if (path_end)
-   path_end[1] = '\0';
+   path_end[0] = '\0';
break;
 
default: /* error */
@@ -615,7 +614,7 @@ is_path_prefix(unsigned char *d, unsigned char *s)
 
if (dl > strlen(s)) return 0;
 
-   return !memcmp(d, s, dl);
+   return !memcmp(d, s, dl) && (s[dl] == '\0' || s[dl] == '/');
 }
 
 
-- 
2.11.0


-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#959489: buster-pu: package pgcli/1.9.1-3+deb10u1

[Andreas Beckmann]

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

Let's add the missing dependency on python3-pkg-ressources, backported
from sid.
The package is already uploaded.

Andreas
diff -Nru pgcli-1.9.1/debian/changelog pgcli-1.9.1/debian/changelog
--- pgcli-1.9.1/debian/changelog2019-06-11 11:04:36.0 +0200
+++ pgcli-1.9.1/debian/changelog2020-05-03 00:22:41.0 +0200
@@ -1,3 +1,12 @@
+pgcli (1.9.1-3+deb10u1) buster; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Lennart Weller ]
+  * pkg-resources hard dependency for minimal systems (Closes: #944455)
+
+ -- Andreas Beckmann   Sun, 03 May 2020 00:22:41 +0200
+
 pgcli (1.9.1-3) unstable; urgency=medium
 
   * Fix Patch for pg11. Excluding new parameter (Closes: #930273)
diff -Nru pgcli-1.9.1/debian/control pgcli-1.9.1/debian/control
--- pgcli-1.9.1/debian/control  2019-06-11 11:04:36.0 +0200
+++ pgcli-1.9.1/debian/control  2020-05-03 00:18:24.0 +0200
@@ -19,6 +19,7 @@
 Depends: python3-click (>= 4.1),
  python3-configobj (>= 5.0.6),
  python3-humanize (>= 0.5.1),
+ python3-pkg-resources (>= 40),
  python3-prompt-toolkit (>= 1.0.10),
  python3-psycopg2 (>= 2.7.4),
  python3-pygments (>= 2.0),

Bug#955747: libgl1-mesa-dri: all GL programms crash on startup when

[Jean-Francois Pirus]

I have the same or very similar issue (see 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959400 )

And I can confirm that uninstalling the xserver-xorg-video-intel and
using the modesetting driver fixed the issue for me.

PS:
And removing  a custom config file that caused the any other driver
from failing to load.
ie:
/usr/share/X11/xorg.conf.d/BLAH.conf

Bug#959400: Acknowledgement (mesa: SIGSEGV in iris_dri.so using mpv or glxgears, Intel HD Graphics 620)

[Jean-Francois Pirus]

I can confirm that uninstalling the xserver-xorg-video-intel and using
the modesetting driverfixed the issue.

PS:
And removing  a custom config file that caused the any other driver
from failing to load.
ie:
/usr/share/X11/xorg.conf.d/BLAH.conf


On Sat, 2020-05-02 at 00:27 +, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
> 
> You can follow progress on this Bug here: 959400: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959400.
> 
> 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.
> 
> Your message has been sent to the package maintainer(s):
>  Debian X Strike Force 
> 
> If you wish to submit further information on this problem, please
> send it to 959...@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.
> 

Bug#959424: [Pkg-clamav-devel] Bug#959424: Error: VirusEvent: fork failed

[Sebastian Andrzej Siewior]

On 2020-05-02 11:05:08 [+0200], Bernd wrote:
> Package: clamav-daemon
> Version: 0.102.2+dfsg-0+deb10u1
> Severity: normal
> Tags: a11y
> 

Is it possible to provide more information than just the $Subject?

Sebastian

Bug#929450: caml-crush, build-dependencies unsatisfiable on armel

[Andreas Beckmann]

Control: found -1 1.0.8-1
Control: tag -1 = sid
Control: close -1

On Tue, 09 Jul 2019 13:56:40 +0200 Andreas Beckmann  wrote:
> The armel binaries have been removed from sid.
and buster, too.

Andreas

Bug#237772: mailman: Please separate architecture independent and dependent files.

[Jonas Smedegaard]

Quoting Tollef Fog Heen (2004-03-15 12:11:44)
> 
> severity 233410 wishlist
> severity 237772 wishlist
> merge 233410 237772
> thanks
> 
> * Jonas Smedegaard 
> 
> | The arch-dep mailman binary package is several megabytes big, but only a 
> small
> | portion of that is in reality arch-dep.
> |
> | Please split the package in arch-dependent and arch-independent files to 
> lessen
> | the load on mirrors.
> 
> It would be nice if you looked at bugs already filed before filing new
> ones.  Yes, I'm aware of the issue, and yes, it will be fixed.

...famous last words... :-P

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#959488: qbittorrent logo on the systemtray looks odd

[shirish शिरीष]

Package: qbittorrent
Version: 4.2.4-1
Severity: normal

Dear Maintainer,

The qbittorrent logo on the systray looks odd. It looks almost as if
it has been squeezed from both sides. I dunno if it's the logo which
has an issue or it's qt. This is on mate-desktop btw.


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

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

Versions of packages qbittorrent depends on:
ii  geoip-database  20191224-2
ii  libboost-system1.67.0   1.67.0-17+b1
ii  libc6   2.30-4
ii  libgcc-s1   10-20200418-1
ii  libqt5core5a5.12.5+dfsg-10
ii  libqt5dbus5 5.12.5+dfsg-10
ii  libqt5gui5  5.12.5+dfsg-10
ii  libqt5network5  5.12.5+dfsg-10
ii  libqt5widgets5  5.12.5+dfsg-10
ii  libqt5xml5  5.12.5+dfsg-10
ii  libssl1.1   1.1.1g-1
ii  libstdc++6  10-20200418-1
ii  libtorrent-rasterbar10  1.2.5-1+b1
ii  python3 3.8.2-3
ii  zlib1g  1:1.2.11.dfsg-2

qbittorrent recommends no packages.

Versions of packages qbittorrent suggests:
ii  qbittorrent-dbg  4.2.4-1

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

Bug#959469: buster-pu: package openssl/1.1.1g-1

[Adam D. Barratt]

On Sat, 2020-05-02 at 22:29 +0200, Sebastian Andrzej Siewior wrote:
> On 2020-05-02 20:32:01 [+0100], Adam D. Barratt wrote:
> > On Sat, 2020-05-02 at 18:36 +0200, Sebastian Andrzej Siewior wrote:
> > > I'm fairly late, I know.
> > 
> > Just a little. :-( Particularly as OpenSSL builds udebs.
> > 
> > CCing KiBi and -boot so they're aware of the discussion, but this
> > does
> > come quite late.
> 
> Yes, I know. I'm won't cry if this skips this pu, I just couldn't get
> earlier to it.

OK. To be honest, at this stage I would be happier looking at this for
10.5 than 10.4.

> > Do we have any feeling for how widespread such certificates might
> > be?
> > The fact that there have been two different upstream reports isn't
> > particularly comforting.
> 
> This is correct. I don't know if there is tooling that is generating
> broken certificates or just some individuals. I updated my two
> OpenVPN instances and I saw clients connecting again.

Thanks for the information.

Regards,

Adam

Bug#959487: libpng built without VSX support on ppc64le

[Timothy Pearson]

Package: libpng16-16:ppc64le
Version: 1.6.36-6

libpng is built without VSX support on POWER systems.  This breaks assumptions 
in other software, such as node optipng (log below).

I can work around it with this, but it is not ideal:
CFLAGS="-DPNG_POWERPC_VSX_OPT=0" npm install optipng-bin

npm install optipng-bin
npm WARN npm npm does not support Node.js v10.15.2
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 
8, 9.
npm WARN npm You can find the latest version at https:/nodejs.org/

> optipng-bin@6.0.0 postinstall 
> /home/develop/build/ONLYOFFICE/build_tools/node_modules/optipng-bin
> node lib/install.js

  ⚠ Command failed: 
/home/develop/build/ONLYOFFICE/build_tools/node_modules/optipng-bin/vendor/optipng
 --version
/home/develop/build/ONLYOFFICE/build_tools/node_modules/optipng-bin/vendor/optipng:
 1: 
/home/develop/build/ONLYOFFICE/build_tools/node_modules/optipng-bin/vendor/optipng:
 @@8�@@@�: not found
/home/develop/build/ONLYOFFICE/build_tools/node_modules/optipng-bin/vendor/optipng:
 2: 
/home/develop/build/ONLYOFFICE/build_tools/node_modules/optipng-bin/vendor/optipng:
 d: not found
/home/develop/build/ONLYOFFICE/build_tools/node_modules/optipng-bin/vendor/optipng:
 1: 
/home/develop/build/ONLYOFFICE/build_tools/node_modules/optipng-bin/vendor/optipng:
 ELF: not found
/home/develop/build/ONLYOFFICE/build_tools/node_modules/optipng-bin/vendor/optipng:
 1: 
/home/develop/build/ONLYOFFICE/build_tools/node_modules/optipng-bin/vendor/optipng:
 Syntax error: ";" unexpected


  ⚠ optipng pre-build test failed
  ℹ compiling from source
  ✖ Error: Command failed: /bin/sh -c make install
pngrtran.c:99:1: warning: ‘png_rtran_ok’ defined but not used 
[-Wunused-function]
 png_rtran_ok(png_structrp png_ptr, int need_IHDR)
 ^~~~
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
pngxmem.c: In function ‘pngx_malloc_rows_extended’:
pngxmem.c:38:34: warning: comparison is always false due to limited range of 
data type [-Wtype-limits]
(pngx_alloc_size_t)height > (pngx_alloc_size_t)(-1) / sizeof(png_bytep))
  ^
ar: `u' modifier ignored since `D' is the default (see `U')
/usr/bin/ld: ../libpng/libpng.a(pngrutil.o): in function `png_read_filter_row':
pngrutil.c:(.text+0x29c0): undefined reference to 
`png_init_filter_functions_vsx'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:100: optipng] Error 1
make: *** [Makefile:14: install] Error 2

cd src/optipng && \
make install && \
cd ../..
make[1]: Entering directory 
'/home/develop/build/ONLYOFFICE/build_tools/node_modules/optipng-bin/a4e0fea9-c020-4419-98f6-a1b3d4dfc863/src/optipng'
cd ../libpng && \
make -f Makefile PNGLIBCONF_H_PREBUILT=pnglibconf.h.optipng && \
cd ../optipng
make[2]: Entering directory 
'/home/develop/build/ONLYOFFICE/build_tools/node_modules/optipng-bin/a4e0fea9-c020-4419-98f6-a1b3d4dfc863/src/libpng'
cp pnglibconf.h.optipng pnglibconf.h
gcc -c -I../zlib  -O2 -Wall -Wextra -o png.o png.c
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngerror.o pngerror.c
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngget.o pngget.c
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngmem.o pngmem.c
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngpread.o pngpread.c
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngread.o pngread.c
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngrio.o pngrio.c
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngrtran.o pngrtran.c
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngrutil.o pngrutil.c
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngset.o pngset.c
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngtrans.o pngtrans.c
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngwio.o pngwio.c
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngwrite.o pngwrite.c
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngwtran.o pngwtran.c
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngwutil.o pngwutil.c
ar rcs libpng.a png.o pngerror.o pngget.o pngmem.o pngpread.o pngread.o 
pngrio.o pngrtran.o pngrutil.o pngset.o pngtrans.o pngwio.o pngwrite.o 
pngwtran.o pngwutil.o
ranlib libpng.a
gcc -c -I../zlib  -O2 -Wall -Wextra -o pngtest.o pngtest.c
gcc  -L../zlib -o pngtest pngtest.o libpng.a -lz -lm
make[2]: Leaving directory 
'/home/develop/build/ONLYOFFICE/build_tools/node_modules/optipng-bin/a4e0fea9-c020-4419-98f6-a1b3d4dfc863/src/libpng'
cd ../opngreduc && \
make -f Makefile libopngreduc.a && \
cd ../optipng
make[2]: Entering directory 
'/home/develop/build/ONLYOFFICE/build_tools/node_modules/optipng-bin/a4e0fea9-c020-4419-98f6-a1b3d4dfc863/src/opngreduc'
gcc -c  -O2 -Wall -Wextra  -I../libpng -o opngreduc.o opngreduc.c
ar cru libopngreduc.a opngreduc.o
ranlib libopngreduc.a
make[2]: Leaving directory 
'/ho

Bug#948191: nmu: vlc_3.0.8-0+deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2020-01-05 at 03:32 +0100, Andreas Beckmann wrote:
> nmu vlc_3.0.8-0+deb10u1 . ANY . buster . -m "Rebuild to tighten
> libmatroska6v5 dependency." --extra-depends "libmatroska6v5 (>=
> 1.4.9-1+deb10u1)"

That's no longer necessary as there's been a 3.0.10 upload.

> nmu mkvtoolnix_31.0.0-1 . ANY . buster . -m "Rebuild to tighten
> libmatroska6v5 dependency." --extra-depends "libmatroska6v5 (>=
> 1.4.9-1+deb10u1)"

Scheduled.

Regards,

Adam

Bug#959486: cloud-init - Enable fallback data source if nothing is detected in ds-identify

[Bastian Blank]

Package: cloud-init
Version: 20.1-2
Severity: wishlist

cloud-init does some basic tasks, like
- network config (currently completely shadowed by our own),
- ssh host keys.

I think the most sensible setup would always enable cloud-init, and if
it only runs with the fallback datasource.

Currently we are using ds-identify.  This tools does not have any way to
only enable the fallback data source.

Any ideas?

Bastian

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

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

Versions of packages cloud-init depends on:
pn  cloud-guest-utils   
ii  fdisk   2.34-0.1
ii  gdisk   1.0.5-1
ii  ifupdown0.8.35+b1
ii  locales 2.30-4
ii  lsb-base11.1.0
ii  lsb-release 11.1.0
ii  net-tools   1.60+git20180626.aebd88e-1
ii  procps  2:3.3.16-4
ii  python3 3.8.2-3
ii  python3-configobj   5.0.6-4
ii  python3-jinja2  2.10.1-2
pn  python3-jsonpatch   
pn  python3-jsonschema  
pn  python3-oauthlib
ii  python3-requests2.23.0+dfsg-2
ii  python3-six 1.14.0-3
ii  python3-yaml5.3.1-1+b1
ii  util-linux  2.34-0.1

Versions of packages cloud-init recommends:
pn  cloud-guest-utils  
ii  eatmydata  105-7
ii  sudo   1.8.31p1-1

Versions of packages cloud-init suggests:
ii  btrfs-progs  5.6-1
ii  e2fsprogs1.45.6-1
ii  xfsprogs 5.4.0-1+b1

Bug#959485: ITP: python-redisearch-py -- RediSearch client

[Michael Fladischer]

Package: wnpp
Severity: wishlist
Owner: Michael Fladischer 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: python-redisearch-py
  Version : 0.9.0
  Upstream Author : RedisLabs 
* URL : https://github.com/RediSearch/redisearch-py/
* License : BSD-2-clause
  Programming Lang: Python
  Description : RediSearch client

 This is a python search engine library that utilizes the RediSearch Redis
 Module API. RediSearch is an open-source, high performance search engine
 implemented as a Redis Module. It uses custom data types to allow fast, stable
 and feature rich full-text search inside redis.
 .
 This client is a wrapper around the RediSearch API protocol, that allows you to
 utilize its features easily.

I do intend to maintain this package as part of the DPMT.

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAl6t37wRHGZsYWRpQGRl
Ymlhbi5vcmcACgkQ/9PIi5l90WrHgQf/TSZlqzdrcMWJY1lUM20hzAPQk5ZBUdow
jFuTYJzteXSYCIh2JeBJG8VBrhd92L+8EWdLR/+JvIla3+jUZKE/QCA3BtWWUZB/
4qnl4eRqEhsaQmyX9eIrukreGWj4i/xjakZ+9aviVi68MZk1vEz0IkcZmlTef43p
wo4J1yOMVSwiLZVIHIaY0B7sFROHWRy0qFe+JcgVTuIzzFi5V+tjrAUgIpNT9qEz
2ExufWKJFGVdzJ+d+dvctqiAkLBpziVj6CWjlwEZLT7neWw4NyyTECbctwzSkiFs
jgQkpk8Vo1pCyPdGL50tjf/KssAJkUVnEdndwtLtMKOVTEeqXyeehg==
=z5hz
-END PGP SIGNATURE-

Bug#959484: grub-common: typos in /etc/grub.d/05_debian_theme

[Vincent Lefevre]

Package: grub-common
Version: 2.04-7
Severity: minor

There are typos in "/etc/grub.d/05_debian_theme":

# For plymouth backward compatiblity. Can be removed

should be "compatibility"

# If so, we can remove the cache file (if any). Otherwise the backgound
  ^
should be "background"

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/mapper/zira--vg-root / ext4 rw,relatime,errors=remount-ro 0 0
/dev/sda1 /boot ext2 rw,relatime,stripe=4 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="${saved_entry}"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  
7b3de7fd-236a-47f6-bb85-64831a06ca1f
else
  search --no-floppy --fs-uuid --set=root 7b3de7fd-236a-47f6-bb85-64831a06ca1f
fi
font="/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=1024x768 640x480
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=POSIX
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  
7b3de7fd-236a-47f6-bb85-64831a06ca1f
else
  search --no-floppy --fs-uuid --set=root 7b3de7fd-236a-47f6-bb85-64831a06ca1f
fi
insmod png
if background_image /grub/.background_cache.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=keep
export linux_gfx_mode
menuentry 'Debian GNU/Linux, with Linux 5.6.0-1-amd64' --class debian --class 
gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-5.6.0-1-amd64-advanced-30a1ad7d-49ca-4b60-91d5-58f6f63d1c8e' {
savedefault
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  
7b3de7fd-236a-47f6-bb85-64831a06ca1f
else
  search --no-floppy --fs-uuid --set=root 
7b3de7fd-236a-47f6-bb85-64831a06ca1f
fi
echo'Loading Linux 5.6.0-1-amd64 ...'
linux   /vmlinuz-5.6.0-1-amd64 root=/dev/mapper/zira--vg-root ro  quiet 
acpi_osi=linux acpi_backlight=vendor
echo'Loading initial ramdisk ...'
initrd  /initrd.img-5.6.0-1-amd64
}
menuentry 'Debian GNU/Linux, with Linux 5.6.0-1-amd64 (recovery mode)' --class 
debian --class gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-5.6.0-1-amd64-recovery-30a1ad7d-49ca-4b60-91d5-58f6f63d1c8e' {
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msd

Bug#959483: bluez: typo in /etc/default/bluetooth

[Vincent Lefevre]

Package: bluez
Version: 5.50-1.2
Severity: minor

A typo in /etc/default/bluetooth (or debian/bluez.bluetooth.default
in the source):

# This setting used to switch HID devices (e.g mouse/keyboad) to HCI mode, that
 ^^^
should be "keyboard"

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

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

Versions of packages bluez depends on:
ii  dbus  1.12.16-2
ii  kmod  27+20200310-2
ii  libasound21.2.2-2.1
ii  libc6 2.30-4
ii  libdbus-1-3   1.12.16-2
ii  libdw10.176-1.1
ii  libglib2.0-0  2.64.2-1
ii  libreadline8  8.0-4
ii  libudev1  245.5-2
ii  lsb-base  11.1.0
ii  udev  245.5-2

bluez recommends no packages.

Versions of packages bluez suggests:
pn  pulseaudio-module-bluetooth  

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#959482: nfs-ganesha linked with rados library

[Andras Elso]

Package: nfs-ganesha
Version: 2.7.1-2
Severity: normal

nfs-ganesha nfs server binary is linked with rados library despire of you 
disable it in debian/rules.

$ ldd /nfs-ganesha/debian/nfs-ganesha/usr/bin/ganesha.nfsd
...
librados.so.2 => /usr/lib/x86_64-linux-gnu/librados.so.2 
(0x7fcb3106c000)

You disable it with "NO", but i think this is wrong, sould be "OFF": 
USE_RADOS_RECOV is a goption macro
(https://github.com/nfs-ganesha/nfs-ganesha/blob/next/src/CMakeLists.txt#L370),
and goption use ON or OFF:
https://github.com/nfs-ganesha/nfs-ganesha/blob/next/src/cmake/goption.cmake#L9

Other options sould use ON/OFF too.


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

Kernel: Linux 3.13.0-153-generic (SMP w/24 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages nfs-ganesha depends on:
pn  daemon
pn  dbus  
ii  libacl1   2.2.53-4
ii  libblkid1 2.33.1-0.1
ii  libc6 2.28-10
ii  libcap2   1:2.25-2
ii  libcom-err2   1.44.5-1+deb10u3
ii  libdbus-1-3   1.12.16-1
ii  libgssapi-krb5-2  1.17-3
ii  libk5crypto3  1.17-3
ii  libkrb5-3 1.17-3
ii  libnfsidmap2  0.25-5.1
ii  libntirpc1.7  1.7.1-1
ii  librados2 12.2.11+dfsg1-2.1+b1
ii  liburcu6  0.10.2-1
ii  libuuid1  2.33.1-0.1
ii  libwbclient0  2:4.9.5+dfsg-5+deb10u1
pn  nfs-common
pn  rpcbind   

nfs-ganesha recommends no packages.

nfs-ganesha suggests no packages.

Bug#959469: buster-pu: package openssl/1.1.1g-1

[Sebastian Andrzej Siewior]

On 2020-05-02 20:32:01 [+0100], Adam D. Barratt wrote:
> On Sat, 2020-05-02 at 18:36 +0200, Sebastian Andrzej Siewior wrote:
> > I'm fairly late, I know.
> 
> Just a little. :-( Particularly as OpenSSL builds udebs.
> 
> CCing KiBi and -boot so they're aware of the discussion, but this does
> come quite late.

Yes, I know. I'm won't cry if this skips this pu, I just couldn't get
earlier to it.

> Do we have any feeling for how widespread such certificates might be?
> The fact that there have been two different upstream reports isn't
> particularly comforting.

This is correct. I don't know if there is tooling that is generating
broken certificates or just some individuals. I updated my two OpenVPN
instances and I saw clients connecting again.

> Regards,
> 
> Adam

Sebastian

Bug#934004: ITP: golang-starlark -- Interpreter for the Starlark configuration language

[Roger Shimizu]

control: tags -1 +pending

Dear Emanuel,

Thank for your ITP!

On Tue, Aug 6, 2019 at 6:51 AM Emanuel Krivoy  wrote:
>
> Package: wnpp
> Severity: wishlist
> Owner: Emanuel Krivoy 
>
> * Package name: golang-starlark
>   Version : 0.0~git20190717.fc7a7f4-1

uploaded with minor changes.
build verified on debomatic
- 
http://debomatic-amd64.debian.net/distribution#unstable/golang-starlark/0.0~git20190717.fc7a7f4-1/buildlog

all commits are on salsa now:
- https://salsa.debian.org/go-team/packages/golang-skylark

thanks for your patience, and contribution to debian!

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#959101: debian-security-support 2020.04.16~deb10u2 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 959101 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: debian-security-support
Version: 2020.04.16~deb10u2

Explanation: new upstream stable release; update status of several packages; 
use "runuser" rather than "su"

Bug#958053: schleuder 3.4.0-2+deb10u3 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 958053 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: schleuder
Version: 3.4.0-2+deb10u3

Explanation: improve patch to handle encoding errors introduced in the previous 
version; switch default encoding to UTF-8; let x-add-key handle mails with 
attached, quoted-printable encoded keys; fix x-attach-listkey with mails 
created by Thunderbird that include protected headers

Bug#959431: speech-dispatcher 0.9.0-5+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 959431 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: speech-dispatcher
Version: 0.9.0-5+deb10u1

Explanation: fix default pulseaudio latency which triggers scratchy output

Bug#959481: alpine: does not connect with TLS to smtp/imap server

[Βασίλειος A . Ζοῦκος]

Package: alpine
Version: 2.22+dfsg1-1~bpo10+1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?
  I expected to work properly as version 2.20 does
*** End of the template - remove these template lines ***


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

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

Versions of packages alpine depends on:
ii  libc6 2.28-10
ii  libgssapi-krb5-2  1.17-3
ii  libkrb5-3 1.17-3
ii  libldap-2.4-2 2.4.47+dfsg-3+deb10u1
ii  libssl1.1 1.1.1c-1
ii  libtinfo6 6.1+20181013-2+deb10u1
ii  mlock 8:2007f~dfsg-6

Versions of packages alpine recommends:
ii  alpine-doc  2.21+dfsg1-1.1
ii  sensible-utils  0.0.12

Versions of packages alpine suggests:
ii  aspell 0.60.7~20110707-6
ii  exim4-daemon-light [mail-transport-agent]  4.92-8+deb10u3

-- no debconf information

Bug#959480: FTBFS with Boost 1.71

[Giovanni Mascellani]

Package: frogatto
Version: 1.3.1+dfsg-4
Severity: wishlist
Tags: patch
User: team+bo...@tracker.debian.org
Usertags: boost1.71

Dear Maintainer,

your package fails to build with boost1.71. You can find a build log
attached. If you want to attempt the build yourself, an updated version
of boost-defaults which brings in boost1.71 dependencies can be found
adding this line to your sources.list file:

  deb https://people.debian.org/~gio/reprepro gio main

This bug has severity whishlist for the moment, but it will raised to RC
as soon as version 1.71 of Boost is promoted to default.

More specifically, your package fails building because it uses a retired
API from Boost.Asio. The attached patch should fix the bug.

Thanks and all the best, Giovanni.
-- 
Giovanni Mascellani 
Postdoc researcher - Université Libre de Bruxelles
Index: frogatto-1.3.1+dfsg/src/http_server.cpp
===
--- frogatto-1.3.1+dfsg.orig/src/http_server.cpp
+++ frogatto-1.3.1+dfsg/src/http_server.cpp
@@ -31,7 +31,7 @@ web_server::web_server(boost::asio::io_s
 
 void web_server::start_accept()
 {
-	socket_ptr socket(new tcp::socket(acceptor_.get_io_service()));
+	socket_ptr socket(new tcp::socket(acceptor_.get_executor()));
 	acceptor_.async_accept(*socket, boost::bind(&web_server::handle_accept, this, socket, boost::asio::placeholders::error));
 
 }


frogatto.log.gz
Description: application/gzip


signature.asc
Description: OpenPGP digital signature

Bug#959479: FTBFS with Boost 1.71

[Giovanni Mascellani]

Package: dogecoin
Version: 1.10.0-7.1
Severity: wishlist
User: team+bo...@tracker.debian.org
Usertags: boost1.71

Dear Maintainer,

your package fails to build with boost1.71. You can find a build log
attached. If you want to attempt the build yourself, an updated version
of boost-defaults which brings in boost1.71 dependencies can be found
adding this line to your sources.list file:

  deb https://people.debian.org/~gio/reprepro gio main

This bug has severity whishlist for the moment, but it will raised to RC
as soon as version 1.71 of Boost is promoted to default.

More specifically, your package fails building because it uses some
retired API from Boost.Asio. It appears, though, that upstream dogecoin
has since long stopped using Asio, switching to libevent2 as IO library
since commit 40b556d3742a1f65d67e2d4c760d0b13fe8be5b7 (dated Fri Jan 23
07:53:17 2015 +0100). I believe it would be more advisable to package an
updated version of dogecoin rather than patch it for Boost 1.71.

Thanks and all the best, Giovanni.
-- 
Giovanni Mascellani 
Postdoc researcher - Université Libre de Bruxelles


dogecoin.log.gz
Description: application/gzip


signature.asc
Description: OpenPGP digital signature

Bug#959469: buster-pu: package openssl/1.1.1g-1

[Adam D. Barratt]

On Sat, 2020-05-02 at 18:36 +0200, Sebastian Andrzej Siewior wrote:
> I'm fairly late, I know.

Just a little. :-( Particularly as OpenSSL builds udebs.

CCing KiBi and -boot so they're aware of the discussion, but this does
come quite late.

> The last update was addressed via DSA providing only a patch for the
> CVE with severity high. This pu updates Buster's OpenSSL version from
> `d' to current `g' fixing CVE-2019-1551 which was earlier skipped due
> to its low severity. 
> The "EOF" bug-fix-regression introduced in `e' is reverted again in
> `g'.
> OpenSSL now checks certificates more strictly. There should be no
> problems with "officially" issued certificats but some certificates
> contain an invalid (combination of) attributes which are now. The `g'
> version is since 25th April in testing and received no bug reports
> but OpenSSL upstream received [0], [1] for custom issued OpenVPN
> certificates.
> Please find attached a compressed debdiff since last security update.
> 
> [0] https://github.com/openssl/openssl/issues/11456
> [1] https://github.com/openssl/openssl/issues/11625

Do we have any feeling for how widespread such certificates might be?
The fact that there have been two different upstream reports isn't
particularly comforting.

Regards,

Adam

Bug#959478: bc is not included as a dependency for wireguard-dkms

[Carlos Fernandez]

Package: wireguard-dkms
Version: 1.0.20200429-1~bpo10+1

Trying to install wireguard

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  wireguard-dkms wireguard-tools
The following NEW packages will be installed:
  wireguard wireguard-dkms wireguard-tools
0 upgraded, 3 newly installed, 0 to remove and 18 not upgraded.
Need to get 354 kB of archives.
After this operation, 2,100 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ftp.debian.org/debian buster-backports/main amd64
wireguard-dkms all 1.0.20200429-1~bpo10+1 [260 kB]
Get:2 http://ftp.debian.org/debian buster-backports/main amd64
wireguard-tools amd64 1.0.20200319-1~bpo10+1 [86.5 kB]
Get:3 http://ftp.debian.org/debian buster-backports/main amd64
wireguard all 1.0.20200319-1~bpo10+1 [7,464 B]
Fetched 354 kB in 0s (4,843 kB/s)
Selecting previously unselected package wireguard-dkms.
(Reading database ... 112993 files and directories currently installed.)
Preparing to unpack .../wireguard-dkms_1.0.20200429-1~bpo10+1_all.deb ...
Unpacking wireguard-dkms (1.0.20200429-1~bpo10+1) ...
Selecting previously unselected package wireguard-tools.
Preparing to unpack .../wireguard-tools_1.0.20200319-1~bpo10+1_amd64.deb ...
Unpacking wireguard-tools (1.0.20200319-1~bpo10+1) ...
Selecting previously unselected package wireguard.
Preparing to unpack .../wireguard_1.0.20200319-1~bpo10+1_all.deb ...
Unpacking wireguard (1.0.20200319-1~bpo10+1) ...
Setting up wireguard-dkms (1.0.20200429-1~bpo10+1) ...
Loading new wireguard-1.0.20200429 DKMS files...
Building for 5.4.0-0.bpo.4-amd64
Building initial module for 5.4.0-0.bpo.4-amd64
Error! Bad return status for module build on kernel:
5.4.0-0.bpo.4-amd64 (x86_64)
Consult /var/lib/dkms/wireguard/1.0.20200429/build/make.log for more
information.
dpkg: error processing package wireguard-dkms (--configure):
 installed wireguard-dkms package post-installation script subprocess
returned error exit status 10
Setting up wireguard-tools (1.0.20200319-1~bpo10+1) ...
dpkg: dependency problems prevent configuration of wireguard:
 wireguard depends on wireguard-dkms (>= 0.0.20200121-2) |
wireguard-modules (>= 0.0.20191219); however:
  Package wireguard-dkms is not configured yet.
  Package wireguard-modules is not installed.

And the error is:
DKMS make.log for wireguard-1.0.20200429 for kernel 5.4.0-0.bpo.4-amd64 (x86_64)
Sat 02 May 2020 07:10:25 PM UTC
make: Entering directory '/usr/src/linux-headers-5.4.0-0.bpo.4-amd64'
/bin/sh: 1: bc: not found
/var/lib/dkms/wireguard/1.0.20200429/build/compat/Kbuild.include:58:
*** bc(1) is required for building.  Stop.
make[1]: *** [/usr/src/linux-headers-5.4.0-0.bpo.4-common/Makefile:1665:
/var/lib/dkms/wireguard/1.0.20200429/build] Error 2
make: *** [/usr/src/linux-headers-5.4.0-0.bpo.4-common/Makefile:179:
sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-5.4.0-0.bpo.4-amd64'

Manually installing the package "bc" solves the problem.

Bug#959476: wicd-daemon: spams the logs with "Throttling autoreconnect" messages

[Vincent Lefevre]

Package: wicd-daemon
Version: 1.7.4+tb2-6
Severity: important

wicd-daemon spams the logs with "Throttling autoreconnect" messages,
mostly during the same second:

zira% journalctl -b | wc -l
56765
zira% journalctl -b -u wicd | grep -c 'Throttling autoreconnect'   
41075
zira% journalctl -b -u wicd | grep 'Throttling autoreconnect' | uniq | wc -l 
260

In short, these messages take 72% of the logs, and each time they
appear, they appear 158 times the same second! If I did not have
these duplicates, the messages would take only 260 lines over the
15000+ other lines.

Note: My machine is usually connected by Ethernet (not managed by wicd),
and I still get these messages while there should be no connection
attempt from wicd.

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

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

Versions of packages wicd-daemon depends on:
ii  adduser   3.118
ii  dbus  1.12.16-2
ii  debconf   1.5.74
ii  iputils-ping  3:20190709-3
ii  isc-dhcp-client   4.4.1-2.1+b2
ii  lsb-base  11.1.0
ii  psmisc23.3-1
ii  python2.7.17-2
ii  python-dbus   1.2.16-2
ii  python-gobject-2  2.28.6-14+b1
ii  python-wicd   1.7.4+tb2-6
ii  wireless-tools30~pre9-13.1
ii  wpasupplicant 2:2.9.0-12

Versions of packages wicd-daemon recommends:
ii  rfkill 2.34-0.1
ii  wicd-curses [wicd-client]  1.7.4+tb2-6
ii  wicd-gtk [wicd-client] 1.7.4+tb2-6

Versions of packages wicd-daemon suggests:
pn  pm-utils  

Versions of packages wicd depends on:
ii  wicd-curses [wicd-client]  1.7.4+tb2-6
ii  wicd-gtk [wicd-client] 1.7.4+tb2-6

Versions of packages wicd-gtk depends on:
ii  python 2.7.17-2
ii  python-glade2  2.24.0-6
ii  python-gtk22.24.0-6

Versions of packages wicd-gtk recommends:
ii  menu   2.1.47+b1
ii  policykit-10.105-26
ii  python-notify  0.1.1-4+b2

Versions of packages wicd-curses depends on:
ii  python2.7.17-2
ii  python-urwid  2.0.1-2+b2

Versions of packages wicd-curses recommends:
ii  sudo  1.8.31p1-1

Versions of packages python-wicd depends on:
ii  net-tools  1.60+git20180626.aebd88e-1
ii  python 2.7.17-2

Versions of packages python-wicd suggests:
ii  ethtool   1:5.4-1
ii  iproute2  5.6.0-1

-- Configuration Files:
/etc/wicd/encryption/templates/active changed:
wpa
wpa-peap
wpa-peap-wo-domain
wpa-psk
wpa-psk-hex
wpa2-leap
wpa2-peap
wpa2-peap-wo-domain
wep-hex
wep-passphrase
wep-shared
leap
ttls
eap
peap
peap-eduroam
peap-tkip
eap-tls
psu


-- debconf information:
* wicd/users:

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#957704: [Git][med-team/praat][master] 7 commits: fix ftbfs with gcc 10

[Andreas Tille]

Control: tags -1 pending

Hi Rafael,

Étienne was pretty helpful for several Debian Med packages.  Do
you want to check and sponsor his changes since you usually are
uploading praat?  If not I can do so for sure.

Kind regards

 Andreas.


On Sat, May 02, 2020 at 03:01:46PM +, Étienne Mollier wrote:
> 
> 
> Étienne Mollier pushed to branch master at Debian Med / praat
> 
> 
> Commits:
> a543dab7 by Etienne Mollier at 2020-05-02T14:06:35+02:00
> fix ftbfs with gcc 10
> 
> - - - - -
> b7a2025a by Etienne Mollier at 2020-05-02T14:07:26+02:00
> routine-update: Add salsa-ci file
> 
> - - - - -
> 3dee22f2 by Etienne Mollier at 2020-05-02T14:07:34+02:00
> Use secure URI in Homepage field.
> 
> Fixes: lintian: homepage-field-uses-insecure-uri
> See-also: 
> https://lintian.debian.org/tags/homepage-field-uses-insecure-uri.html
> 
> - - - - -
> 71da8edd by Etienne Mollier at 2020-05-02T14:07:37+02:00
> Remove obsolete fields Contact, Name from debian/upstream/metadata (already 
> present in machine-readable debian/copyright).
> - - - - -
> 8c9a98a1 by Etienne Mollier at 2020-05-02T15:09:18+02:00
> put information about yahoo group to d/copyright
> 
> it looks like it is the place it is now intended to be since
> linters said that was redundant in d/u/metadata.
> 
> - - - - -
> aff4b733 by Etienne Mollier at 2020-05-02T15:18:01+02:00
> 6.1.13-2 ready for upload I guess
> 
> - - - - -
> 9301bb05 by Etienne Mollier at 2020-05-02T16:13:57+02:00
> remove -Wl,--as-needed linker flags
> 
> - - - - -
> 
> 
> 8 changed files:
> 
> - debian/changelog
> - debian/control
> - debian/copyright
> - + debian/patches/fix-ftbfs-gcc-10.patch
> - debian/patches/series
> - debian/rules
> - + debian/salsa-ci.yml
> - debian/upstream/metadata
> 
> 
> Changes:
> 
> =
> debian/changelog
> =
> @@ -1,3 +1,15 @@
> +praat (6.1.13-2) unstable; urgency=medium
> +
> +  * Team upload.
> +  * changed a call for isupper(3) to iswupper(3) (Closes: #957704)
> +  * Add salsa-ci file (routine-update)
> +  * Use secure URI in Homepage field.
> +  * Remove obsolete fields Contact, Name from debian/upstream/metadata
> +(already present in machine-readable debian/copyright).
> +  * Moved Contact information into debian/copyright.
> +
> + -- Etienne Mollier   Sat, 02 May 2020 14:07:38 
> +0200
> +
>  praat (6.1.13-1) unstable; urgency=medium
>  
>* New upstream version 6.1.13
> 
> 
> =
> debian/control
> =
> @@ -15,7 +15,7 @@ Build-Depends: debhelper-compat (= 12),
>  Standards-Version: 4.5.0
>  Vcs-Browser: https://salsa.debian.org/med-team/praat
>  Vcs-Git: https://salsa.debian.org/med-team/praat.git
> -Homepage: http://www.praat.org
> +Homepage: https://www.praat.org
>  Rules-Requires-Root: no
>  
>  Package: praat
> 
> 
> =
> debian/copyright
> =
> @@ -1,6 +1,7 @@
>  Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
>  Upstream-Name: Program for speech analysis and synthesis
>  Upstream-Contact: Paul Boersma 
> +  https://uk.groups.yahoo.com/neo/groups/praat-users/info
>  Source: http://www.fon.hum.uva.nl/praat/download_sources.html
>  
>  Files: *
> 
> 
> =
> debian/patches/fix-ftbfs-gcc-10.patch
> =
> @@ -0,0 +1,22 @@
> +Description: fix ftbfs with migration to gcc-10
> + Options are either to import ctypes.h or move to wide-char support for the
> + incriminated function call.  Given work advertised on Unicode support
> + (specifically UTF-16) on Praat home page, the second option has been chosen:
> + http://www.fon.hum.uva.nl/praat/manual/Unicode.html
> +Author: Étienne Mollier 
> +Bug-Debian: https://bugs.debian.org/957704
> +Forwarded: no
> +Last-Update: 2020-05-02
> +---
> +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
> +--- praat.orig/external/espeak/espeak_io.cpp
>  praat/external/espeak/espeak_io.cpp
> +@@ -190,7 +190,7 @@
> + // copy 4 bytes: version number
> + // copy 4 bytes: sample rate
> + while (fgets (line, sizeof (line), manifestf)) {
> +-if (! isupper (line [0])) continue;
> ++if (! iswupper (line [0])) continue;
> + unsigned int index;
> + sscanf(& line [2], "%x", & index);
> + fseek (phondataf, index, SEEK_SET);
> 
> 
> =
> debian/patches/series
> =
> @@ -1,3 +1,4 @@
>  use-ldflags.patch
>  remove-time-date-macros.patch
>  fix-procrustes-unit-test.patch
> +fix-ftbfs-gcc-10.patch
> 
> 
> =
> debian/rules
> =
> @@ -50,8 +50,7 @@ override_dh_auto_configure:
>   # Get rid of the
>   # dp

Bug#959469: buster-pu: package openssl/1.1.1g-1

[Sebastian Andrzej Siewior]

On 2020-05-02 18:36:42 [+0200], To sub...@bugs.debian.org wrote:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: pu
> Tags: buster
> Severity: normal
> 
> I'm fairly late, I know.
> The last update was addressed via DSA providing only a patch for the CVE
> with severity high. This pu updates Buster's OpenSSL version from `d' to
> current `g' fixing CVE-2019-1551 which was earlier skipped due to its
> low severity. 

Haven't seen it in the list archive as of now, so it in case it did not
pass due to its size, here is a note about it.

Sebastian

Bug#954259: innoextract: diff for NMU version 1.8-1.1

[Adrian Bunk]

Control: tags 954259 + patch

Dear maintainer,

I've prepared an NMU for innoextract (versioned as 1.8-1.1) and uploaded 
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru innoextract-1.8/debian/changelog innoextract-1.8/debian/changelog
--- innoextract-1.8/debian/changelog	2020-01-15 17:30:07.0 +0200
+++ innoextract-1.8/debian/changelog	2020-05-02 21:00:51.0 +0300
@@ -1,3 +1,11 @@
+innoextract (1.8-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Go back to debhelper-compat 11 to work around dwz issues on
+mipsel and mips64el. (see #956954) (Closes: #954259)
+
+ -- Adrian Bunk   Sat, 02 May 2020 21:00:51 +0300
+
 innoextract (1.8-1) unstable; urgency=medium
 
   * Move to new upstream version. Deprecating the last patch
diff -Nru innoextract-1.8/debian/control innoextract-1.8/debian/control
--- innoextract-1.8/debian/control	2020-01-15 17:30:07.0 +0200
+++ innoextract-1.8/debian/control	2020-05-02 21:00:35.0 +0300
@@ -8,8 +8,7 @@
 Vcs-git: https://salsa.debian.org/lhw-guest/innoextract.git
 Homepage: http://constexpr.org/innoextract/
 Build-Depends: cmake,
-   debhelper (>= 12),
-   debhelper-compat(= 12),
+   debhelper-compat(= 11),
dpkg-dev (>= 1.16.1~),
libboost-iostreams-dev,
libboost-filesystem-dev,

Bug#959475: screenkey: doesn't respect settings

[Tomas Janousek]

Package: screenkey
Version: 0.10-1
Severity: grave
Justification: renders package unusable

The python3 version seems almost entirely broken on my Debian testing system.
Almost all settings are ignored, regardless of whether I change them using
command-line switches or the settings GUI. Backspace shows as [⁰⁰₀₈] instead
of ⌫. No matter what font I choose, it uses some fixed one that apparently
lacks the symbol for backspace and many other keys. No matter what setting I
choose for --bak-mode, it shows the same broken backspace unicode replacement
instead of erasing the last char. --key-mode is ignored as well.

When changing settings through the setting GUI, the following exception is
printed:

  File "/usr/lib/python3/dist-packages/Screenkey/screenkey.py", line 340, 
in on_cbox_modes_changed
self.options.key_mode = KEY_MODES.keys()[index]
TypeError: 'dict_keys' object is not subscriptable

Downgrading to 0.9-2 from stable fixes all of this.

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

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

-- 
Tomáš Janoušek, a.k.a. Pivník, a.k.a. Liskni_si, http://work.lisk.in/

Bug#959423: [pkg-cryptsetup-devel] Bug#959423: cryptsetup-initramfs: MODULES=dep missed "ecb" since linux-5.6.0

[Guilhem Moulin]

Control: retitle -1 cryptsetup-initramfs: Can't open AES-XTS device from 
initrd.img-5.6.0-1-amd64 built with MODULES=dep on systems lacking AES-NI
Control: tag -1 pending

Hi,

On Sat, 02 May 2020 at 11:19:48 +0200, Adrien CLERC wrote:
> It seems that linux-5.6 changes a lot of things in crypto modules, and I
> started to add everything in /etc/initramfs-tools/modules from
> /lib/modules/5.6.0-1-amd64/kernel/crypto/.
> After bisecting the whole list, I figured out that I just need to add "ecb" in
> the list.

Thanks for the detailed report :-)  I believe this is the same issue as #883595
(and https://gitlab.com/cryptsetup/cryptsetup/issues/319 ) but it's
beyond me why the ‘xts’ doesn't depend on ‘ecb’ despite Milan's patch
being applied upstream:


https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/crypto/Kconfig?h=v5.6.7#n435
https://sources.debian.org/src/linux/5.6.7-1/crypto/Kconfig/#L435

But I think I now understand why no one else complained since >4.10
landed in sid.  On a minimal Buster VM running on CPUs without AES-NI
support I see:

$ grep -Fw -e{ecb,xts} /proc/modules
ecb 16384 4 - Live 0xc0395000
xts 16384 2 - Live 0xc038b000

initrd.img-4.19.0-8-amd64 built with MODULES=dep *does* include ‘ecb’.

$ lsinitramfs /boot/initrd.img-4.19.0-8-amd64 | grep -E 
"/kernel/crypto/(ecb|xts)"
usr/lib/modules/4.19.0-8-amd64/kernel/crypto/ecb.ko
usr/lib/modules/4.19.0-8-amd64/kernel/crypto/xts.ko

This is because the root FS is in ext4 format (like on your system, and
also the d-i default) and (unlike ‘xts’) the ‘ext4’ module… does depend
on ‘ecb’, at least for kernel versions between 4.10 and 4.19.  Sigh.

$ modprobe --all --set-version=4.19.0-8-amd64 \
--ignore-install --quiet --show-depends ext4
[…]
insmod /lib/modules/4.19.0-8-amd64/kernel/crypto/ecb.ko 
[…]
insmod /lib/modules/4.19.0-8-amd64/kernel/fs/ext4/ext4.ko 
$ modprobe --all --set-version=4.19.0-8-amd64 \
--ignore-install --quiet --show-depends xts
[…]
insmod /lib/modules/4.19.0-8-amd64/kernel/crypto/xts.ko

(It might be that initrd.img-4.19.0-8-amd64 built MODULES=dep won't
include ‘ecb’ either on other file system types.  ‘btrfs’ for instance
doesn't depend on ‘ecb’, and without AES-NI I can't open my btrfs root
FS from a initrd.img-4.19.0-8-amd64 built with MODULES=dep.)

Now, installing current Bullseye (5.5.0-2-amd64) and sid (5.6.0-1-amd64)
kernels on that box, I see that 5.5.0-2-amd64's ‘ecb’ and ‘xts’ are both
builtin for some reason.

$ modinfo -F filename -k 4.19.0-8-amd64 ecb xts
/lib/modules/4.19.0-8-amd64/kernel/crypto/ecb.ko
/lib/modules/4.19.0-8-amd64/kernel/crypto/xts.ko
$ modinfo -F filename -k 5.5.0-2-amd64 ecb xts
name:   ecb
(builtin)
name:   ecb
(builtin)
name:   xts
(builtin)
name:   xts
(builtin)
$ modinfo -F filename -k 5.6.0-1-amd64 ecb xts
/lib/modules/5.6.0-1-amd64/kernel/crypto/ecb.ko
/lib/modules/5.6.0-1-amd64/kernel/crypto/xts.ko
 
So while initrd.img-5.5.0-2-amd64 contains neither it's not an issue
since they're builtin.  On the other hand on 5.6.0-1-amd64 ‘ext4’ no
longer depends on ‘ecb’ so initrd.img-5.5.0-2-amd64 won't include it
unless it's explicitly included in /etc/initramfs-tools/modules.

$ lsinitramfs /boot/initrd.img-5.5.0-2-amd64 | grep -E 
"/kernel/crypto/(ecb|xts)"
$ lsinitramfs /boot/initrd.img-5.6.0-1-amd64 | grep -E 
"/kernel/crypto/(ecb|xts)"
usr/lib/modules/5.6.0-1-amd64/kernel/crypto/xts.ko

All in all: 1/ I don't understand why #883595 isn't fixed while the
patch seems applied upstream; and 2/ for now a workaround for us is to
unconditionally copy ‘ecb’ when the host CPU lacks AES-NI support.  This
also fixes the problem with non-EXT root FS on Buster kernels.

Tested in 8 different scenarios, each with initrd.img-5.6.0-1-amd64 and
MODULES=dep: with aes-xts-plain64 and serpent-xts-plain64; with ext4 and
btrfs root file systems; on CPUs with and without AES-NI support.

Cheers,
-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#959474: Issues with Chinese language (all variants) when building some pages in buster

[Laura Arjona Reina]

Package: www.debian.org
Severity: normal
User: www.debian@packages.debian.org
Usertags: scripts
X-Debbugs-CC: debian-l10n-chin...@lists.debian.org
X-Debbugs-CC: debian-i...@lists.debian.org

Hi all,

TL;DR

There are some issues with some Chinese pages when they are built in a
buster machine.
We need to fix those issues (at least the "Malformed UTF-8 character
[...] at ../../bin/tocn.pl [...]" ones) so DSA can upgrade the
www-master machine to buster. See the summary of the log at the bottom
to know which files produce this error.
I have no idea of how to fix the issues, so any help from the Chinese
team or web team mates is greatly appreciated..
Additional issues may arise (e.g. I still didn't test the release-notes
or doc-manual), any help testing is welcome too, please create bug
reports for each different issue or update the existing ones. Thanks!

LONG VERSION

I've done a test build of the /english and /chinese subdirs in a buster
machine, and I have noticed some warnings/errors related to the Chinese
pages (some, not all of them).

It would be desirable to upgrade www-master machine to buster as soon as
possible, so any help with this (from website  or Chinese team members)
is very appreciated.

Below you can find an extract of the build log, including only the the
files for which I got some error or warning message.

After the build, I have compared the problematic HTML files of a build
in stretch and a build in buster with a diff tool, to see if there were
significant changes in the html output due to these issues.

Here are my results:

* For the messages of the type ", [zh_TW]Invalid UTF8: " when building,
I couldn't note any difference between the output of a stretch build and
the output of a buster build.

I would say this is not a blocker for the buster upgrade of www-master.

* For the messages of the type "Malformed UTF-8 character [...] at
../../bin/tocn.pl [...]" I have seen important changes in the HTML diff,
I think the output in the stretch build is totally broken (fortunately,
there are not many files in that situation).

I would say this is a blocker for the buster upgrade of www-master, but
I would prefer somebody of the Chinese team to confirm (try to build
those files in a buster machine, and review the output).

Additional notes:

* I have only tested the wml build, not the rest of the cron scripts
that run on www-master. I will try to do it in the following days, but
if you already know any that works well (e.g. release-notes,
doc-manuals...) just tell so I can skip them.

* When I build files in my machines, there is something wrong in my
environment that I don't get the .po files integrated every time, so for
example the Chinese pages I build show the menus and footnote in
English. Therefore, if there is any issue with the encoding of the .po
files themselves, I guess I cannot detect it until I fix my particular
issue :/

* The local build that I make uses the SAMPLE_FILES that are needed in
some folders; so additional issues may arise when we use the actual
files that are generated at runtime in the often and lessoften cron jobs.

That's all for now, I think. Thanks for your patience reading and for
your help!

Kind regards,
-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona


--- extract of the build log file

/chinese

Processing
donations.wml:
[zh_CN]Invalid UTF8:
ïŒŒç‚¹å‡»â€œæ·»åŠ åˆ°èŽ­ç‰©èœŠâ€ïŒŒç„¶åŽå®Œæˆå‰©äœ™è¿‡çš‹ã€‚
, [zh_TW]Invalid UTF8:
ïŒŒç‚¹å‡»â€œæ·»åŠ åˆ°èŽ­ç‰©èœŠâ€ïŒŒç„¶åŽå®Œæˆå‰©äœ™è¿‡çš‹ã€‚
, [zh_HK]Invalid UTF8:
ïŒŒç‚¹å‡»â€œæ·»åŠ åˆ°èŽ­ç‰©èœŠâ€ïŒŒç„¶åŽå®Œæˆå‰©äœ™è¿‡çš‹ã€‚
.

make[1]: Entering directory '/webwml/chinese/Bugs'
Processing Reporting.wml: [zh_CN]Invalid UTF8:
°äž€æ¬¡ç€ºäŸ‹äŒšè¯çš„过皋。
, [zh_TW]Invalid UTF8: °äž€æ¬¡ç€ºäŸ‹äŒšè¯çš„过皋。
, [zh_HK]Invalid UTF8: °äž€æ¬¡ç€ºäŸ‹äŒšè¯çš„过皋。
.

make[2]: Entering directory '/webwml/chinese/News/2000'

Processing 2815.wml:
[zh_CN]Invalid UTF8: µ·å€–朋友的錎力協助包括
, [zh_TW]Invalid UTF8: µ·å€–朋友的錎力協助包括
, [zh_HK]Invalid UTF8: µ·å€–朋友的錎力協助包括
.

make[2]: Entering directory '/webwml/chinese/News/2009'
Processing 20090214.wml: [zh_CN]Invalid UTF8: šSun SPARC (sparc)、
, [zh_TW]Invalid UTF8: šSun SPARC (sparc)、
, [zh_HK]Invalid UTF8: šSun SPARC (sparc)、
.

make[2]: Entering directory '/webwml/chinese/News/weekly'

copying index.zh-cn.html to ../../../../www/News/weekly/./2002/48
Processing index.wml: [zh_CN]Malformed UTF-8 character (unexpected end
of string) in substitution (s///) at ../../bin/tocn.pl line 13, <> line 146.
Malformed UTF-8 character (unexpected end of string) in substitution
(s///) at ../../bin/tocn.pl line 15, <> line 146.
panic: do_trans_simple_utf8 line 362 at ../../bin/tocn.pl line 20, <>
line 146.
, [zh_TW]Invalid UTF8: å‘
, [zh_HK]Invalid UTF8: å‘
.
copying index.zh-cn.html to ../../../../www/News/weekly/./2002/49

copying index.zh-cn.html to ../../../../www/News/weekly/./

Bug#956877: release-notes: Upgrade from XFS removes mount option "barrier|nobarrier"

[Paul Gevers]

Dear Benedikt, all,

On 16-04-2020 10:44, Benedikt Tuchen wrote:
> While doing an upgrade from Stretch to Buster on a Laptop with XFS
> Filesystem in use. After the upgrade the laptop doesn't boot into
> the system because of the removed "barrier|nobarrier" mount option
> for XFS in version 4.19.
> 
> I think this issue should be mentioned in the "5. Issues to be aware
> of for buster" part of the release-notes in Buster.

What is exactly the problem? Does everybody with XFS run into this
issue? Do you have a solution for the problem that we can mention? Or,
phrased differently, what should the user do if they have an XFS
filesystem and want to upgrade to buster?

Paul



signature.asc
Description: OpenPGP digital signature

Bug#956074: ITP: golang-github-francoispqt-gojay -- JSON encoder/decoder with stream API

[Roger Shimizu]

control: tags -1 +pending

Dear Alois,

Thank for your ITP!

Since it's also an indirect dependency for my another package, I used
dh-make-golang to create the package.
I already push to salsa:
- https://salsa.debian.org/go-team/packages/golang-github-francoispqt-gojay

If you have anything to add, please go ahead.
I can sponsor your upload. Please ping me by replying to this email.

Otherwise, I'll try to upload in a week or so. Thank you!

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#959473: orthanc-dicomweb build-dependencies unsatisfiable on armel

[peter green]

Package: orthanc-dicomweb
Version: 1.1+dfsg-1
Severity: serious
x-debbugs-cc: node-axios

My self-contained buildability check script detected that armel binaries for 
orthanc-dicomweb were present in testing, but the build-dependencies for 
orthanc-dicomweb could not be satisified on armel. Specifically 
orthanc-dicomweb depends on the arch-all package node-axios which in turn 
depends on nodejs which is not available on armel.

What took me a while to figure out is how exactly things had got to this state.

It seems that orthanc-dicomweb gained the build-dependency on node-axios in 
version 1.0+dfsg-1 which got stuck in unstable for a while. A while later 
1.0+dfsg-2 was uploaded, a request was made to the ftpmasters to remove the old 
packages ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944732 ). The 
removal request was actioned and orthanc-dicomweb migrated to testing without 
armel support.

1.1+dfsg-1 was also uploaded and migrated to testing, initially without armel 
support.

Then a month or so later a buggy version of node-pegjs was uploaded that contained 
"Provides: libjs-pegjs, node-peg, nodejs, pegjs". The bug was fixed a week or 
so later, but not before it had allowed the buildds to build armel packages for 
orthanc-dicomweb 1.1+dfsg-1. The release teams build-dependency checks are not 
sophisticated enough to detect this either and so the armel binaries made it into testing 
(even though the package that had enabled them to build never did).

Since it seems that the orthanc-dicomweb build does not actually need nodejs 
(the armel build succeeded after-all) that would seem to leave two ways to get 
back to a consistent state.

1. Request again removal of the armel binaries. This is probablly the easiest option, but 
it's not really in keeping with "packages must be built on as many architectures as 
reasonably possible".
2. Restructure the "node-axios" package and it's dependencies to provide a 
"libjs-axios" package that can be installed without nodejs.

I am ccing the node-axios maintainers on this bug report so they can comment on 
the feasibility of providing a libjs-axios package that can be installed on 
architectures where nodejs is not available.

Bug#955680: birdfont: diff for NMU version 2.28.0-1.1

[Adrian Bunk]

Control: tags 955680 + patch
Control: tags 955680 + pending

Dear maintainer,

I've prepared an NMU for birdfont (versioned as 2.28.0-1.1) and uploaded 
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru birdfont-2.28.0/debian/changelog birdfont-2.28.0/debian/changelog
--- birdfont-2.28.0/debian/changelog	2019-10-11 18:42:17.0 +0300
+++ birdfont-2.28.0/debian/changelog	2020-05-02 20:40:39.0 +0300
@@ -1,3 +1,10 @@
+birdfont (2.28.0-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Link with libcairo-gobject. (Closes: #955680)
+
+ -- Adrian Bunk   Sat, 02 May 2020 20:40:39 +0300
+
 birdfont (2.28.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru birdfont-2.28.0/debian/patches/cairo-gobject.patch birdfont-2.28.0/debian/patches/cairo-gobject.patch
--- birdfont-2.28.0/debian/patches/cairo-gobject.patch	1970-01-01 02:00:00.0 +0200
+++ birdfont-2.28.0/debian/patches/cairo-gobject.patch	2020-05-02 20:40:39.0 +0300
@@ -0,0 +1,14 @@
+Description: Link with libcairo-gobject.
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/955680
+
+--- birdfont-2.28.0.orig/dodo.py
 birdfont-2.28.0/dodo.py
+@@ -335,6 +335,7 @@ def make_libbirdfont(target_binary, deps
+ $({pkg-config} --libs gio-2.0) \
+ $({pkg-config} --libs fontconfig) \
+ $({pkg-config} --libs cairo) \
++$({pkg-config} --libs cairo-gobject) \
+ $({pkg-config} --libs glib-2.0) \
+ $({pkg-config} --libs xmlbird) \
+ -L./build -L./build/bin -l birdgems \
diff -Nru birdfont-2.28.0/debian/patches/series birdfont-2.28.0/debian/patches/series
--- birdfont-2.28.0/debian/patches/series	2019-10-11 18:42:17.0 +0300
+++ birdfont-2.28.0/debian/patches/series	2020-05-02 20:40:39.0 +0300
@@ -1 +1,2 @@
 0001-Don-t-install-Roboto-Regular.ttf.patch
+cairo-gobject.patch

Bug#703388: davical: potential privacy issues as any user can list all other users/their details, etc.

[Klaus Maria Pfeiffer]

hi!

starting on Patrick Mulrooney's work in in 
https://sourceforge.net/p/davical/patches/5/ I've attached a set of 
patches (based on davical/stretch-backports,now 1.1.8-1+deb10u1~bpo9+1) 
to limit users view to own user and users of groups its member of.


gre3tings, Klaus
--- /usr/share/davical/inc/always.php.in.orig	2019-01-30 20:52:46.0 +0100
+++ /usr/share/davical/inc/always.php.in	2020-05-02 18:35:22.442020949 +0200
@@ -93,6 +93,7 @@
 $c->base_url = preg_replace('#/[^/]+\.php.*$#', '', $_SERVER['SCRIPT_NAME']);
 $c->base_directory = preg_replace('#/[^/]*$#', '', $_SERVER['DOCUMENT_ROOT']);
 $c->default_privileges = array('read-free-busy', 'schedule-deliver');
+$c->list_everyone = true;
 
 $c->enable_auto_schedule = true;
 
--- /usr/share/davical/htdocs/always.php.orig	2020-04-21 23:23:53.0 +0200
+++ /usr/share/davical/htdocs/always.php	2020-05-02 18:34:19.873738736 +0200
@@ -134,6 +134,7 @@
 $c->base_url = preg_replace('#/[^/]+\.php.*$#', '', $_SERVER['SCRIPT_NAME']);
 $c->base_directory = preg_replace('#/[^/]*$#', '', $_SERVER['DOCUMENT_ROOT']);
 $c->default_privileges = array('read-free-busy', 'schedule-deliver');
+$c->list_everyone = true;
 
 $c->enable_auto_schedule = true;
 
--- /usr/share/davical/inc/ui/collection-edit.php.orig	2020-04-21 23:23:53.0 +0200
+++ /usr/share/davical/inc/ui/collection-edit.php	2020-05-02 18:28:50.600242993 +0200
@@ -416,7 +416,13 @@
 
   $grantrow = new Editor("Grants", "grants");
   $grantrow->SetSubmitName( 'savegrantrow' );
-  $grantrow->SetLookup( 'to_principal', 'SELECT principal_id, displayname FROM dav_principal WHERE principal_id NOT IN (SELECT member_id FROM group_member WHERE group_id = '.$id.') ORDER BY displayname' );
+  $limit_grantrow = '';
+  if ( ! $c->list_everyone ) {
+if ( ! $session->AllowedTo( "Admin" ) ) {
+  $limit_grantrow = 'AND (principal_id = \''.$session->principal_id.'\' or principal_id in (select member_id from group_member where group_id in (select group_id from group_member where member_id = \''.$session->principal_id.'\')) or principal_id in (select group_id from group_member where member_id = \''.$session->principal_id.'\'))';
+}
+  }
+  $grantrow->SetLookup( 'to_principal', 'SELECT principal_id, displayname FROM dav_principal WHERE principal_id NOT IN (SELECT member_id FROM group_member WHERE group_id = '.$id.') '.$limit_grantrow.' ORDER BY displayname' );
   if ( $can_write_collection ) {
 if ( $grantrow->IsSubmit() ) {
   $_POST['by_collection'] = $id;
--- /etc/davical/config.php.orig	2020-04-21 23:23:53.0 +0200
+++ /etc/davical/config.php	2020-05-02 18:23:54.486873745 +0200
@@ -113,6 +113,14 @@
 // $c->local_styles = array();
 // $c->print_styles = array();
 
+/**
+* Allow users to see all accounts listed, or only their account and
+* the accounts they have a relationship to in the web interface. 
+* Admins will still be able to see all accounts.
+* Default: true
+*/
+// $c->list_everyone = false;
+
 
 /***
 *  *
--- /usr/share/davical/inc/ui/principal-browse.php.orig	2016-12-28 10:35:25.0 +0100
+++ /usr/share/davical/inc/ui/principal-browse.php	2020-05-02 17:23:27.106920933 +0200
@@ -35,6 +35,16 @@
   $browser->AndWhere( 'type_id = '.$principal_type );
 }
 
+if ( ! $c->list_everyone ) {
+  if ( ! $session->AllowedTo( "Admin" ) ) { 
+if ( isset($principal_type) && ( $principal_type == 1 || $principal_type == 2 ) ) {
+  $browser->AndWhere( '(principal_id = \''.$session->principal_id.'\' or principal_id in (select member_id from group_member where group_id in (select group_id from group_member where member_id = \''.$session->principal_id.'\')))' );
+}
+if ( isset($principal_type) && $principal_type == 3 ) {
+  $browser->AndWhere( '(principal_id = \''.$session->principal_id.'\' or principal_id in (select group_id from group_member where member_id = \''.$session->principal_id.'\'))' );
+}
+  }
+}
 
 $c->page_title = $browser->Title();
 
--- /usr/share/davical/inc/ui/principal-edit.php.orig	2020-04-21 23:23:53.0 +0200
+++ /usr/share/davical/inc/ui/principal-edit.php	2020-05-02 18:06:02.729799715 +0200
@@ -615,7 +615,7 @@
 
 
 function grant_row_editor() {
-  global $c, $id, $editor, $can_write_principal, $privilege_names;
+  global $c, $id, $editor, $can_write_principal, $privilege_names, $session;
 
   $grantrow = new Editor("Grants", "grants");
   $grantrow->SetSubmitName( 'savegrantrow' );
@@ -623,7 +623,13 @@
   if ( isset($_GET['edit_grant']) ) {
 $edit_grant_clause = ' AND to_principal != '.intval($_GET['edit_grant']);
   }
-  $grantrow->SetLookup( 'to_principal', 'SELECT principal_id, displayname FROM dav_principal WHERE user_active AND principal_id NOT IN (SELECT to_principal FROM grants WHERE by_principal = '.$id.$edit_grant_clause.') ORDER BY fullname' );
+  $limit_grantrow = '';
+  if 

Bug#959472: initramfs-tools (0.137): E: /usr/share/initramfs-tools/hooks/plymouth failed

[John David Anglin]

Package: initramfs-tools
Version: 0.137
Severity: normal

Dear Maintainer,

update-initramfs fails:

Processing triggers for initramfs-tools (0.137) ...
update-initramfs: Generating /boot/initrd.img-5.2.17+
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.2.17+ with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

Version 0.136 was okay.

Regards,
Dave Anglin

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 12M Apr 11  2015 /boot/initrd.img-3.12.40+
-rw-r--r-- 1 root root 11M Sep 27  2016 /boot/initrd.img-3.18.42+
-rw-r--r-- 1 root root 20M Apr 16 20:38 /boot/initrd.img-4.14.176+
-rw-r--r-- 1 root root 20M Apr 24 21:57 /boot/initrd.img-4.14.177+
-rw-r--r-- 1 root root 11M Aug 21  2016 /boot/initrd.img-4.4.19+
-rw-r--r-- 1 root root 12M Sep 22  2017 /boot/initrd.img-4.9.51+
-rw-r--r-- 1 root root 37M Aug 21  2019 /boot/initrd.img-5.2.0-2-parisc64
-rw-r--r-- 1 root root 20M Apr 24 19:43 /boot/initrd.img-5.2.17+
-rw-r--r-- 1 root root 20M Sep 17  2019 /boot/initrd.img-5.2.8+
-- /proc/cmdline
root=LABEL=ROOT2 console=ttyS0 HOME=/ rootfstype=xfs clocksource=jiffies 
TERM=xterm palo_kernel=2/vmlinuz

-- /proc/filesystems
cramfs
xfs
ext2
ext3
ext4

-- lsmod
Module  Size  Used by
binfmt_misc13075  1
ext4  693225  3
ext2  113644  1
crc16   1655  1 ext4
jbd2  122319  1 ext4
mbcache 9772  2 ext4,ext2
sg 53216  0
ipmi_watchdog  25830  0
ipmi_si72878  1
ipmi_poweroff  12981  0
ipmi_devintf   14622  0
ipmi_msghandler60860  4 ipmi_devintf,ipmi_si,ipmi_watchdog,ipmi_poweroff
nfsd  166379  11
ip_tables  26100  0
x_tables   35419  1 ip_tables
ipv6  587774  146
autofs446898  2
xfs  1118276  2
libcrc32c   1618  1 xfs
crc32c_generic  3086  7
raid10 80659  0
raid1  59399  0
raid0  13504  0
multipath  11251  0
linear  6392  0
md_mod222868  5 raid1,raid10,raid0,linear,multipath
ses12759  0
enclosure  13195  1 ses
scsi_transport_sas 46247  1 ses
sd_mod 59912  10
sr_mod 24407  0
cdrom  44396  1 sr_mod
uas24743  0
usb_storage76116  2 uas
ata_generic 5378  0
ohci_pci5280  0
tg3   257464  0
pata_cmd64x10355  0
ptp20391  1 tg3
ohci_hcd   43731  1 ohci_pci
ehci_pci5759  0
ehci_hcd   62336  1 ehci_pci
sym53c8xx 111720  6
pps_core   13769  1 ptp
libata282335  2 pata_cmd64x,ata_generic
scsi_transport_spi 38311  1 sym53c8xx
usbcore   270368  6 
ohci_hcd,ehci_pci,usb_storage,ehci_hcd,ohci_pci,uas
scsi_mod  247013  10 
ses,scsi_transport_sas,sd_mod,scsi_transport_spi,usb_storage,uas,sym53c8xx,libata,sg,sr_mod
usb_common  3118  1 usbcore

-- /etc/initramfs-tools/modules

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

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

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

-- /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid10] 
unused devices: 

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

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


-- System Information:
Debian Release: bullseye/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

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

Versions of packages initramfs-tools depends on:
ii  initramfs-tools-core  0.137
ii  linux-base4.6

initramfs-tools recommends no packages.

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

-- no debconf information

Bug#959471: base-files: Support for parametrized files

[Guillem Jover]

Source: base-files
Source-Version: 11
Severity: wishlist
Tags: patch

Hi!

This package requires both changes in Debian between freeze and
non-freeze times, and also is one of the first ones that need
modifications when creating a derivative.

To make handling both these cases, I've prepared the attached patch
which tries to parametrize everything that is changed in Debian during
the release cycle so that it's easier to maintain. And so that
derivatives can have an easier time deriving too.

The new workflow for Debian would require only touching three variables
in params/debian. For a derivative, it would require adding a new
params/ file and changing the params/default symlink to point
to that. This would massively reduce the amount of changes needed in
derivatives, as seen in .


I've tried to document all variables in params/debian so that they are
easy to understand. I've also switched from #SUBST# to @SUBST@ as that
works better within a Makefile.


Let me know what you think, and whether you'd like to see anything
changed?

(BTW, I guess you do not manage this package under a VCS?)

Thanks,
Guillem
From f3bc14192d80a40c7376bced5e7af27f23de099c Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Sun, 19 Jan 2020 01:10:40 +0100
Subject: [PATCH] Parametrize files

This should help both Debian and its derivatives, as now all these
should be able to do most of the work by just adding a new params/
file and updating the params/default symlink.

We switch from #SUBST# to @SUBST@ as that works better within a
Makefile.

The intention here is that the only things that would normally need
changing would be under params/. For a derivative a new params file
would need to be added under params/ and the params/default symlink
updated.
---
 debian/README   | 10 ++---
 debian/base-files.dirs  |  1 +
 debian/base-files.docs  |  2 -
 debian/base-files.links |  1 -
 debian/clean|  1 +
 debian/control  |  8 ++--
 debian/copyright.in |  6 +--
 debian/current-md5sums-obsolete |  4 +-
 debian/gen-vendor.mk| 14 +++
 debian/postinst.in  |  4 +-
 debian/rules| 72 -
 etc/debian_version  |  1 -
 etc/issue   |  2 +-
 etc/issue.net   |  2 +-
 etc/os-release  | 16 +---
 origins/debian  |  3 --
 params/debian   | 68 +++
 params/default  |  1 +
 share/dot.bashrc|  2 +-
 share/info.dir  |  2 +-
 share/motd  |  4 +-
 21 files changed, 180 insertions(+), 44 deletions(-)
 delete mode 100644 debian/base-files.docs
 create mode 100644 debian/gen-vendor.mk
 delete mode 100644 etc/debian_version
 delete mode 100644 origins/debian
 create mode 100644 params/debian
 create mode 12 params/default

diff --git a/debian/README b/debian/README
index 1618655..5a51013 100644
--- a/debian/README
+++ b/debian/README
@@ -4,10 +4,10 @@ Frequently Asked Questions about base-files
 * Questions about /etc/issue and /etc/debian_version:
 
 Q. I upgraded my system to the testing distribution and now my /etc/issue
-says "bullseye/sid". Should it not read "bullseye" or "testing"?
+says "@OSCODENAME_TESTING@/sid". Should it not read "@OSCODENAME_TESTING@" or "testing"?
 
 Q. I upgraded my system to the unstable distribution and now my /etc/issue
-says "bullseye/sid". Should it not read "sid" or "unstable"?
+says "@OSCODENAME_TESTING@/sid". Should it not read "sid" or "unstable"?
 
 A. That would be nice, but it is not possible because of the way the
 testing distribution works. Packages uploaded for unstable reach
@@ -17,9 +17,9 @@ testing. You should consider the testing and unstable distributions as
 two sides of the same coin. Since the base-files package in testing
 was initially uploaded for unstable, the only sensible /etc/issue to
 have is one that is both valid for testing and unstable, hence
-"bullseye/sid" (or whatever is appropriate).
+"@OSCODENAME_TESTING@/sid" (or whatever is appropriate).
 
-Q. Why "bullseye/sid" and not "testing/unstable" as it used to be?
+Q. Why "@OSCODENAME_TESTING@/sid" and not "testing/unstable" as it used to be?
 
 A. The codename is a little bit more informative, as the meaning of
 "testing" changes over time.
@@ -31,7 +31,7 @@ not a reliable way to know that anymore. Looking at the contents of
 your /etc/apt/sources.list file is probably a much better way.
 
 Q. There is a new point release and I've just upgraded my system.
-The /etc/debian_version file now says 10.x but /etc/issue still says 10.
+The /etc/debian_version file now says @OSVERSION_ID_STABLE@.x but /etc/issue still says @OSVERSION_ID_STABLE@.
 Is this ok?
 
 A. Yes. The release managers asked me not to touch /etc/issue, as that's
diff --git a/debian/

Bug#959470: base-files: Switch to use https

[Guillem Jover]

Source: base-files
Source-Version: 11
Severity: normal

Hi!

Attached a patch to switch URLs from http to https.

Thanks,
Guillem
From 731eafe5edad6e79a0d23c4fff60e38a3683cd92 Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Tue, 21 Apr 2020 14:35:19 +0200
Subject: [PATCH] Switch to use https where possible

We leave the license texts alone as these are not allowed to be changed.
---
 origins/debian  | 2 +-
 share/staff-group-for-usr-local | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/origins/debian b/origins/debian
index 91f6ed1..3b623d2 100644
--- a/origins/debian
+++ b/origins/debian
@@ -1,3 +1,3 @@
 Vendor: Debian
-Vendor-URL: http://www.debian.org/
+Vendor-URL: https://www.debian.org/
 Bugs: debbugs://bugs.debian.org
diff --git a/share/staff-group-for-usr-local b/share/staff-group-for-usr-local
index 4c7c8f2..0b5d526 100644
--- a/share/staff-group-for-usr-local
+++ b/share/staff-group-for-usr-local
@@ -13,4 +13,4 @@ This file is created by base-files on the initial install, and it's
 also created on upgrades from any base-files release before 6.10, which
 means it will be created on upgrades from squeeze to wheezy.
 
-See http://bugs.debian.org/299007 for details.
+See https://bugs.debian.org/299007 for details.
-- 
2.26.1.301.g55bc3eb7cb9

Bug#958702: bashtop

[Jonathan Carter]

Hi Dylan, I somehow missed your ITP when I first searched and continued
doing the packaging for bashtop (including the patch that fixes the
Makefile, I also sent a PR for this upstream). If you haven't yet
started, can I upload what I've done so far and then you take it from
there? Also happy to comaintain this if you want.

-Jonathan

Bug#958702: bashtop

[Dylan Aïssi]

Hi Jonathan,

The VCS fields on the ITP are wrong, the repo is there:
> https://salsa.debian.org/debian/bashtop

And bashtop (outdated) is in the NEW queue.
> https://ftp-master.debian.org/new/bashtop_0.8.5-1.html

Feel free to add yourself as comaintainer ;-)

Best,
Dylan

Bug#954093: Alternative fix

[daniel]

An alternative fix would be adding a plasma desktop theme and setting 
the default background there. That alternative doesn't require a custom 
script for setting the background image.


For example:
(using /usr/share/plasma/desktoptheme/default/metadata.desktop as a 
template)


$ cat /usr/share/plasma/desktoptheme/debian-theme/metadata.desktop
[Desktop Entry]
Name=DebianTheme
Comment=[...]

X-KDE-PluginInfo-Author=[...]
X-KDE-PluginInfo-Email=[...]
X-KDE-PluginInfo-Name=Debian Theme
X-KDE-PluginInfo-Version=1.0
X-KDE-PluginInfo-Website=[...]
X-KDE-PluginInfo-Category=
X-KDE-PluginInfo-Depends=
X-KDE-PluginInfo-License=[...]
X-KDE-PluginInfo-EnabledByDefault=true
X-Plasma-API=5.0

[Settings]
FallbackTheme=default

[Wallpaper]
defaultWallpaperTheme=DebianTheme
defaultFileSuffix=.png
defaultWidth=1920
defaultHeight=1080


---

And configure that theme as default:

$ cat /etc/xdg/plasmarc
[Theme]
name=DebianTheme

--
Daniel Ruiz de Alegría
drasite.com

Bug#959452:

[Meral Kuscu]

Bug#881788: patch is upstream

[Ralph Giles]

Just wanted to note that this patch has been merged upstream and should
be part of the 0.12 release.

  
https://gitlab.xiph.org/xiph/opusfile/-/commit/49578c103ac59e00538a73311a479c5456922016

 -r

Bug#959406: apt-get: Language and numeric formatting in the output do not match

[Julian Andres Klode]

Control: severity -1 wishlist moreinfo

On Sat, May 02, 2020 at 02:15:00AM +, Bjarni Ingi Gislason wrote:
> Package: apt
> Version: 2.0.2
> Severity: normal
> 
> Dear Maintainer,
> 
>   there is an inconsistency between used language (English) in the
> output and the used punctuation marks for numbers.
> 
> LC_LANG=is_IS, decimal_point="," thousands_sep="."
> 
> LC_LANG=C, decimal_point="." thousands_sep=""
> 
> LC_LANG=C.UTF-8, decimal_point="." thousands_sep=""
> 
> 
>   Example:
> 
> Fetched 1.289 kB in 4s (302 kB/s)
> 
> Fetched 42,4 MB in 7s (5.949 kB/s)

So, this looks alright to me, could you please explain what you think
is wrong here? You gave three languages above, but I fail to see how
that relates to the output.

This is formatted simply by calling printf() variants in C library, so
if you think there is something wrong, it's probably in there.

As said, I don't see anything wrong here. Also LC_LANG does that even
affect these things, aren't they in LC_NUMERIC?


> 
> 
>   Additionally, there should be a space between a number and its units,
> here "4s" should be "4 s", "7s" be "7 s".

The formatting as is has its benefits and it makes sense to keep it.

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

Bug#959468: Add a DEP-8 test

[Dylan Aïssi]

Package: jbig2dec
Severity: wishlist
Tags: patch

Hi,

Please find attached a patch that add a basic DEP-8 test for jbig2dec.

Best,
Dylan
From 7441b13d5a60db0f6c7564c57a1061fafa1a89ed Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dylan=20A=C3=AFssi?= 
Date: Sat, 2 May 2020 13:19:32 +0200
Subject: [PATCH] Add a DEP-8 test

---
 debian/tests/control   |  2 ++
 debian/tests/run-unit-test | 13 +
 2 files changed, 15 insertions(+)
 create mode 100644 debian/tests/control
 create mode 100644 debian/tests/run-unit-test

diff --git a/debian/tests/control b/debian/tests/control
new file mode 100644
index 000..7082497
--- /dev/null
+++ b/debian/tests/control
@@ -0,0 +1,2 @@
+Tests: run-unit-test
+Depends: @
diff --git a/debian/tests/run-unit-test b/debian/tests/run-unit-test
new file mode 100644
index 000..98a7f2a
--- /dev/null
+++ b/debian/tests/run-unit-test
@@ -0,0 +1,13 @@
+#!/bin/sh -e
+
+export LC_ALL=C.UTF-8
+
+if [ "$AUTOPKGTEST_TMP" = "" ] ; then
+AUTOPKGTEST_TMP=`mktemp -d /tmp/${debname}-test.XX`
+trap "rm -rf $AUTOPKGTEST_TMP" 0 INT QUIT ABRT PIPE TERM
+fi
+
+cp -a annex-h.jbig2 $AUTOPKGTEST_TMP
+cd $AUTOPKGTEST_TMP
+
+jbig2dec annex-h.jbig2 -o annex-h.png
-- 
2.20.1

Bug#956414: RFS: eudev/3.2.9-7+debian2: [ITP] /dev/ and hotplug management daemon

[Svante Signell]

Hi again,

I uploaded a new version, 3.2.9-7+debian2 which fixes many lintian
warnings:
  * binary-control-field-duplicates-source
  * out-of-date-standards-version
  * package-uses-old-debhelper-compat-version
  * xc-package-type-in-debian-control
  * rules-requires-root-missing
  * hardening-no-bindnow

Thank you for considering sponsoring this package.

Bug#959467: installation-reports: succesful installation on powermac G4 - powerpc

[Martin Hrebec]

Package: installation-reports
Severity: normal

Dear Maintainer,

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

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

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


-- Package-specific info:

Boot method: CD
Image version: 
https://cdimage.debian.org/cdimage/ports/2020-04-19/debian-10.0-powerpc-NETINST1.iso
Date: 2020-05-02

Machine: PowerBook G4, PowerBook5,8, A1138
Partitions: 
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs   1012380   0   1012380   0% /dev
tmpfs  tmpfs   206180 956205224   1% /run
/dev/sda4  ext4  60184256 4223440  52873876   8% /
tmpfs  tmpfs  1030888   0   1030888   0% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs  1030888   0   1030888   0% /sys/fs/cgroup
/dev/sda2  hfs 1249906676118314   6% /boot/grub
tmpfs  tmpfs   206176   0206176   0% /run/user/0
tmpfs  tmpfs   206176   8206168   1% /run/user/1000

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:



ALL ok
-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20200315"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux powerbook 5.5.0-2-powerpc #1 Debian 5.5.17-1 (2020-04-15) ppc 
GNU/Linux
lspci -knn: lspci: Unable to load libkmod resources: error -12
lspci -knn: :00:0b.0 Host bridge [0600]: Apple Inc. Intrepid2 AGP Bridge 
[106b:0066]
lspci -knn: Kernel driver in use: agpgart-uninorth
lspci -knn: :00:10.0 VGA compatible controller [0300]: Advanced Micro 
Devices, Inc. [AMD/ATI] RV350/M10 / RV360/M11 [Mobility Radeon 9600 (PRO) / 
9700] [1002:4e50]
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RV350/M10 / 
RV360/M11 [Mobility Radeon 9600 (PRO) / 9700] [1002:4e50]
lspci -knn: Kernel driver in use: radeonfb
lspci -knn: 0001:10:0b.0 Host bridge [0600]: Apple Inc. Intrepid2 PCI Bridge 
[106b:0067]
lspci -knn: 0001:10:11.0 Network controller [0280]: Broadcom Inc. and 
subsidiaries BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller 
[14e4:4318] (rev 02)
lspci -knn: Subsystem: Apple Inc. Device [106b:4318]
lspci -knn: Kernel driver in use: b43-pci-bridge
lspci -knn: 0001:10:14.0 CardBus bridge [0607]: Texas Instruments PCI1510 PC 
card Cardbus Controller [104c:ac56]
lspci -knn: Kernel driver in use: yenta_cardbus
lspci -knn: 0001:10:15.0 USB controller [0c03]: NEC Corporation OHCI USB 
Controller [1033:0035] (rev 43)
lspci -knn: Subsystem: NEC Corporation OHCI USB Controller [1033:0035]
lspci -knn: Kernel driver in use: ohci-pci
lspci -knn: 0001:10:15.1 USB controller [0c03]: NEC Corporation OHCI USB 
Controller [1033:0035] (rev 43)
lspci -knn: Subsystem: NEC Corporation OHCI USB Controller [1033:0035]
lspci -knn: Kernel driver in use: ohci-pci
lspci -knn: 0001:10:15.2 USB controller [0c03]: NEC Corporation uPD72010x USB 
2.0 Controller [1033:00e0] (rev 04)
lspci -knn: Subsystem: NEC Corporation uPD72010x USB 2.0 Controller 
[1033:00e0]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 0001:10:17.0 Unassigned class [ff00]: Apple Inc. KeyLargo/Intrepid 
Mac I/O [106b:003e]
lspci -knn: Kernel driver in use: macio
lspci -knn: 0002:24:0b.0 Host bridge [0600]: Apple Inc. Intrepid2 PCI Bridge 
[106b:0068]
lspci -knn: 0002:24:0d.0 Unassigned class [ff00]: Apple Inc. Intrepid2 ATA/100 
[106b:0069]
lspci -knn: Kernel driver in use: pata-pci-macio
lspci -knn: 0002:24:0e.0 FireWire (IEEE 1394) [0c00]: Apple Inc. Intrepid2 
Firewire [106b:006a]
lspci -knn: Subsystem: Apple Inc. Device [106b:5811]
lspci -knn: Kernel driver in use: firewire_ohci
lspci -knn: 0002:24:0f.0 Ethernet controller [0200]: Apple Inc. Intrepid2 GMAC

Bug#956075: ITP: golang-github-viant-toolbox -- Toolbox - go utility library

[Roger Shimizu]

control: tags -1 +pending

Dear Alois,

Thank for your ITP!

On Tue, Apr 7, 2020 at 7:27 AM Alois Micard  wrote:
>
> Package: wnpp
> Severity: wishlist
> Owner: Alois Micard 
>
> * Package name: golang-github-viant-toolbox
>Version : 0.31.0-1
>Upstream Author : Viant, Inc
> * URL : https://github.com/viant/toolbox
> * License : Apache-2.0
>Programming Lang: Go
>Description : Toolbox - go utility library
>
> This package is needed as indirect dependency for Syncthing.

Since it's also an indirect dependency for my another package, I used
dh-make-golang to create the package.
I already push to salsa:
- https://salsa.debian.org/go-team/packages/golang-github-viant-toolbox

If you have anything to add, please go ahead.
I can sponsor your upload. Please ping me by replying to this email.

Otherwise, I'll try to upload in a week or so. Thank you!

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#959466: RFP: mindustry -- A sandbox tower-defense game

[Giovanni Mascellani]

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

   Package name: mindustry
Version: 104.6
Upstream Author: Anton "Anuken" Kramskoi 
URL: https://github.com/Anuken/Mindustry
License: GPL-3.0
Description: A sandbox tower-defense game

Mindustry is a hybrid tower-defense sandbox factory game. Create
elaborate supply chains of conveyor belts to feed ammo into your
turrets, produce materials to use for building, and defend your
structures from waves of enemies. Features include a map editor, 24
built-in maps, cross-platform multiplayer and large-scale PvP unit battles.

The game is written in Java and built over libGDX.

Thanks, Giovanni.
-- 
Giovanni Mascellani 
Postdoc researcher - Université Libre de Bruxelles



signature.asc
Description: OpenPGP digital signature

Bug#959440: RFS: zope.configuration/4.4.0-1 [QA] -- Zope Configuration Markup Language (ZCML)

[Håvard Flaget Aasen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "zope.configuration"

 * Package name: zope.configuration
   Version : 4.4.0-1
   Upstream Author : Zope Foundation and Contributors 
 * URL : https://pypi.python.org/pypi/zope.configuration
 * License : Zope-2.1
 * Vcs : None
   Section : zope

It builds those binary packages:

  python3-zope.configuration - Zope Configuration Markup Language (ZCML)

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

  https://mentors.debian.net/package/zope.configuration

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

  dget -x
https://mentors.debian.net/debian/pool/main/z/zope.configuration/zope.configuration_4.4.0-1.dsc

Changes since the last upload:

   * QA upload.
   * New upstream release
   * Update Standards-Version to 4.5.0
   * Bump debhelper to 13
   * Set upstream metadata field: Bug-Submit

Regards,
Håvard

Bug#959465: libbioparser-dev: Causes several packages to FTBFS with Gcc 10

[Étienne Mollier]

Package: libbioparser-dev
Version: 2.0.1-1
Severity: normal

Dear Maintainers,

While investigating the reasons of failure to build from source
by several packages with Gcc 10, I observed a reoccurring
pattern at least on #957747 and #957748, and also while having a
look at #957836 (but it is hidden by the first build error in
that particular case):

/usr/include/bioparser/bioparser.hpp:867:24: error: ‘invalid_argument’ is not a 
member of ‘std’
  867 | throw std::invalid_argument("[bioparser::SamParser] error: "
  |^~~~
/usr/include/bioparser/bioparser.hpp: In member function ‘bool 
bioparser::SamParser::parse(std::vector >&, uint64_t, 
bool)’:
/usr/include/bioparser/bioparser.hpp:891:28: error: ‘invalid_argument’ is not a 
member of ‘std’
  891 | throw std::invalid_argument("[bioparser::SamParser] 
error: "
  |^~~~
In file included from /<>/src/main.cpp:8:
/usr/include/bioparser/bioparser.hpp: In function 
‘std::unique_ptr > bioparser::createParser(const string&)’:
/usr/include/bioparser/bioparser.hpp:189:20: error: ‘invalid_argument’ is not a 
member of ‘std’
  189 | throw std::invalid_argument("[bioparser::createParser] error: "
  |^~~~
/usr/include/bioparser/bioparser.hpp: In lambda function:
/usr/include/bioparser/bioparser.hpp:263:24: error: ‘invalid_argument’ is not a 
member of ‘std’
  263 | throw std::invalid_argument("[bioparser::FastaParser] 
error: "
  |^~~~
/usr/include/bioparser/bioparser.hpp: In member function ‘bool 
bioparser::FastaParser::parse(std::vector >&, uint64_t, 
bool)’:
/usr/include/bioparser/bioparser.hpp:287:28: error: ‘invalid_argument’ is not a 
member of ‘std’
  287 | throw std::invalid_argument("[bioparser::FastaParser] 
error: "
  |^~~~
/usr/include/bioparser/bioparser.hpp: In lambda function:
/usr/include/bioparser/bioparser.hpp:381:24: error: ‘invalid_argument’ is not a 
member of ‘std’
  381 | throw std::invalid_argument("[bioparser::FastqParser] 
error: "
  |^~~~
/usr/include/bioparser/bioparser.hpp: In member function ‘bool 
bioparser::FastqParser::parse(std::vector >&, uint64_t, 
bool)’:
/usr/include/bioparser/bioparser.hpp:407:28: error: ‘invalid_argument’ is not a 
member of ‘std’
  407 | throw std::invalid_argument("[bioparser::FastqParser] 
error: "
  |^~~~
/usr/include/bioparser/bioparser.hpp: In lambda function:
/usr/include/bioparser/bioparser.hpp:545:24: error: ‘invalid_argument’ is not a 
member of ‘std’
  545 | throw std::invalid_argument("[bioparser::MhapParser] error: 
"
  |^~~~
/usr/include/bioparser/bioparser.hpp: In member function ‘bool 
bioparser::MhapParser::parse(std::vector >&, uint64_t, 
bool)’:
/usr/include/bioparser/bioparser.hpp:567:28: error: ‘invalid_argument’ is not a 
member of ‘std’
  567 | throw std::invalid_argument("[bioparser::MhapParser] 
error: "
  |^~~~
/usr/include/bioparser/bioparser.hpp: In lambda function:
/usr/include/bioparser/bioparser.hpp:675:24: error: ‘invalid_argument’ is not a 
member of ‘std’
  675 | throw std::invalid_argument("[bioparser::PafParser] error: "
  |^~~~
/usr/include/bioparser/bioparser.hpp:691:24: error: ‘invalid_argument’ is not a 
member of ‘std’
  691 | throw std::invalid_argument("[bioparser::PafParser] error: "
  |^~~~
/usr/include/bioparser/bioparser.hpp: In member function ‘bool 
bioparser::PafParser::parse(std::vector >&, uint64_t, 
bool)’:
/usr/include/bioparser/bioparser.hpp:714:28: error: ‘invalid_argument’ is not a 
member of ‘std’
  714 | throw std::invalid_argument("[bioparser::PafParser] 
error: "
  |^~~~
/usr/include/bioparser/bioparser.hpp: In lambda function:
/usr/include/bioparser/bioparser.hpp:839:24: error: ‘invalid_argument’ is not a 
member of ‘std’
  839 | throw std::invalid_argument("[bioparser::SamParser] error: "
  |^~~~
/usr/include/bioparser/bioparser.hpp:867:24: error: ‘invalid_argument’ is not a 
member of ‘std’
  867 | throw std::invalid_argument("[bioparser::SamParser] error: "
  |^~~~
/usr/include/bioparser/bioparser.hpp: In member function ‘bool 
bioparser::SamParser::parse(std::vector >&, uint64_t, 
bool)’:
/usr/include/bioparser/bioparser.hpp:891:28: error: ‘invalid_argument’ is not a 
member of ‘std’
  891 | throw std::invalid_argument("[bioparser::SamParser] 
error: "
  |^

Bug#959419: Confirm

[Magnus Berg]

I have the same issue and message:

magnus@dev:~$ calibre
qt5ct: using qt5ct plugin
Traceback (most recent call last):
  File "/usr/bin/calibre", line 20, in 
sys.exit(calibre())
  File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre
main(args)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 543, in main
listener = create_listener()
  File "/usr/lib/calibre/calibre/gui2/main.py", line 514, in create_listener
return Listener(address=gui_socket_address())
  File "/usr/lib/calibre/calibre/utils/ipc/server.py", line 110, in __init__
self._listener._unlink.cancel()
AttributeError: 'NoneType' object has no attribute 'cancel'

Bug#959464: Update fails sometimes with: Device or resource busy (errno=16)

[Jörg Frings-Fürst]

Package: openvpn
Version: 2.4.9-2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,


updating to 2.4.9-2 fails sometimes with

[quote]
ovpn-ixion[232162]: ERROR: Cannot ioctl TUNSETIFF tun0: Device or resource busy
(errno=16)
ovpn-ixion[232162]: Exiting due to fatal error
[/quote]

This error is reproducible and occurs in about 50% of all computers.

CU
Jörg



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

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

Versions of packages openvpn depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  iproute2   5.6.0-1
ii  libc6  2.30-4
ii  liblz4-1   1.9.2-2
ii  liblzo2-2  2.10-2
ii  libpam0g   1.3.1-5
ii  libpkcs11-helper1  1.26-1+b1
ii  libssl1.1  1.1.1g-1
ii  libsystemd0245.5-2
ii  lsb-base   11.1.0

Versions of packages openvpn recommends:
ii  easy-rsa  3.0.6-1

Versions of packages openvpn suggests:
ii  openssl   1.1.1g-1
pn  openvpn-systemd-resolved  
pn  resolvconf

- -- Configuration Files:
/etc/default/openvpn changed:
AUTOSTART="all"
OPTARGS=""
OMIT_SENDSIGS=0


- -- debconf-show failed

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl6tkowACgkQCfifPIyh
0l3iaRAAueyYE/rY6WuyK2TXlr2IBBWFUq7HLKbW3S/LfG2GU0FBPPS2xUqrhFiK
nLNUJL1m47SkXixZxrsEX/W7LGKeVgCBMknDAbvzhvyG5zcj8i6ai3+NtJAEjT+M
UwQMIQqDpoLGajDoXJ304Ne/h5Pdxf8kuYDayceylFje/7xNhk2TbBOWdOOXucuH
FCNYrjTm7fpkAiC2DiYaAYQRHrCTVoFdDk2343BJM1ZQzYXLDws2D2VeCT/juWOo
UaksRKqe9Ivf/+jloND+Ae3p89+KwSUMRaxcfgUcg+eLQ3aBswiHeQWoKG+Z1y/U
U5iNAmduJacu94ypAQQ8ScBeTgZaHAfG/hGuldVhCxHGH1v9gcVv0dbhkJ4DlL6p
h4kJu6y8UyBZdixQbS5W08ZtJ+havOhn1AVQpeQU4qUxa2JHqzZA2G4u5GfBHlgC
WMOUbdahFPUnbKESMsa7W0QLprBg0cWW6rhAgG0hNL4dd+7plMNVuPSDj2BW0pbj
XoHcpcuHjIWfwHtq/lBpXq5kafkSM9mlfitMV4hZeCL48uKxB1vVTfrnYGgU00WT
WnPXX4HndmJYXIEDX0bNVab+JwRD5vt7JbKZ75wYmVhMBn3RTDLUXN152uVYB/VF
enGWg34uUX8ogbiYFHT0obYqGxvL3F6HMbOWuknkoSRqUtwsT9M=
=c1+o
-END PGP SIGNATURE-

Bug#956072: ITP: golang-github-viant-assertly -- Arbitraty datastructure validation

[Roger Shimizu]

control: tags -1 +pending

Dear Alois,

Thank for your ITP!

On Tue, Apr 7, 2020 at 7:18 AM Alois Micard  wrote:
>
> Package: wnpp
> Severity: wishlist
> Owner: Alois Micard 
>
> * Package name: golang-github-viant-assertly
>Version : 0.5.3-1
>Upstream Author : Viant, Inc
> * URL : https://github.com/viant/assertly
> * License : Apache-2.0
>Programming Lang: Go
>Description : Arbitraty datastructure validation
>
> This package is needed as indirect dependency for Syncthing.

Since it's also an indirect dependency for my another package, I used
dh-make-golang to create the package.
I already push to salsa:
- https://salsa.debian.org/go-team/packages/golang-github-viant-assertly

If you have anything to add, please go ahead.
I can sponsor your upload. Please ping me by replying to this email.

Otherwise, I'll try to upload in a week or so. Thank you!

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#959438: RFS: zope.proxy/4.3.5-1 [QA] -- Generic transparent proxies for Python

[Håvard Flaget Aasen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "zope.proxy"

 * Package name: zope.proxy
   Version : 4.3.5-1
   Upstream Author : Zope Foundation and Contributors 
 * URL : https://pypi.python.org/pypi/zope.proxy
 * License : Zope-2.1
 * Vcs : https://salsa.debian.org/python-team/modules/zope.proxy
   Section : zope

It builds those binary packages:

  python3-zope.proxy - Generic transparent proxies for Python

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

  https://mentors.debian.net/package/zope.proxy

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

  dget -x
https://mentors.debian.net/debian/pool/main/z/zope.proxy/zope.proxy_4.3.5-1.dsc

Changes since the last upload:

   * QA upload.
   * New upstream version 4.3.5
   * Update Standards-Version to 4.5.0
   * Bump debhelper to 13
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse
   * Implement upstream testsuite during build

Regards,
Håvard

Bug#916506: closed by Chris Hofstaedtler (Re: /usr/bin/logger: /usr/bin/logger allows anyone to write to /var/log/syslog)

[Frank Mori Hess]

Shouldn't this be reassigned to rsyslog rather than closed?  Or to whatever
is giving wide open permissions to the log socket?

On Sat, May 2, 2020, 10:06 Debian Bug Tracking System 
wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the bsdutils package:
>
> #916506: /usr/bin/logger: /usr/bin/logger allows anyone to write to
> /var/log/syslog
>
> It has been closed by Chris Hofstaedtler .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Chris Hofstaedtler <
> z...@debian.org> by
> replying to this email.
>
>
> --
> 916506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916506
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Chris Hofstaedtler 
> To: 916506-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 2 May 2020 15:56:40 +0200
> Subject: Re: /usr/bin/logger: /usr/bin/logger allows anyone to write to
> /var/log/syslog
> As explained by Andreas, this is not a bug in util-linux.
>
> Thanks,
> Chris
>
>
> -- Forwarded message --
> From: Frank Mori Hess 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Sat, 15 Dec 2018 02:38:07 -0500
> Subject: /usr/bin/logger: /usr/bin/logger allows anyone to write to
> /var/log/syslog
> Package: bsdutils
> Version: 1:2.29.2-1+deb9u1
> Severity: normal
> File: /usr/bin/logger
>
> Dear Maintainer,
>
> I was surprised to find that I can write anything I want to
> /var/log/syslog using the /usr/bin/logger program as a non-root user.
> My user account has no permissions on /var/log/syslog, it can't even
> read it.
>
> -- System Information:
> Debian Release: 9.6
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.9.0-8-amd64 (SMP w/6 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages bsdutils depends on:
> ii  libc62.24-11+deb9u3
> ii  libsystemd0  232-25+deb9u6
>
> Versions of packages bsdutils recommends:
> ii  bsdmainutils  9.0.12+nmu1
>
> bsdutils suggests no packages.
>
> -- no debconf information
>

Bug#959462: Provides undocumented virtual package linux-kernel-headers

[Ben Hutchings]

Package: linux-libc-dev
Version: 5.6.4-1~exp1
Severity: normal

This was removed in 5.6.7-1, but that change will have to be reverted
as there are still source packages that Build-Depend on it.

This is a tracking bug report that I will block with bug reports
against those source packages.

Ben.

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

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

-- no debconf information

Bug#959454: Acknowledgement (dvbtune: Build-Depends on obsolete package linux-kernel-headers)

[Ben Hutchings]

Actually, since linux-libc-dev is (transitively) build-essential, you
do not need to Build-Depend on it at all.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.




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

Bug#959452: Acknowledgement (array-info: Build-Depends on obsolete package linux-kernel-headers)

[Ben Hutchings]

Actually, since linux-libc-dev is (transitively) build-essential, you
do not need to Build-Depend on it at all.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.




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

Bug#959451: Acknowledgement (am-utils: Build-Depends on obsolete package linux-kernel-headers)

[Ben Hutchings]

Actually, since linux-libc-dev is (transitively) build-essential, you
do not need to Build-Depend on it at all.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.



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

Bug#959453: Acknowledgement (dvbstream: Build-Depends on obsolete package linux-kernel-headers)

[Ben Hutchings]

Actually, since linux-libc-dev is (transitively) build-essential, you
do not need to Build-Depend on it at all.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.




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

Bug#959459: netsend: Build-Depends on obsolete package linux-kernel-headers

[Ben Hutchings]

Package: src:netsend
Version: 0.0~svnr250-1.3
Severity: serious

linux-kernel-headers was removed from unstable in 2007 (I think).  It
is now effectively a virtual package provided by linux-libc-dev, but
it's not a documented virtual package name and I would like to stop
providing it.

linux-libc-dev is (transitively) build-essential, so you do not need to
Build-Depend on it at all.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.



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

Bug#959461: raidutils: Build-Depends on obsolete package linux-kernel-headers

[Ben Hutchings]

Package: src:raidutils
Version: 0.0.6-22
Severity: serious

linux-kernel-headers was removed from unstable in 2007 (I think).  It
is now effectively a virtual package provided by linux-libc-dev, but
it's not a documented virtual package name and I would like to stop
providing it.

linux-libc-dev is (transitively) build-essential, so you do not need to
Build-Depend on it at all.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.



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

Bug#959460: paxtest: Build-Depends on obsolete package linux-kernel-headers

[Ben Hutchings]

Package: src:paxtest
Version: 1:0.9.15-1
Severity: serious

linux-kernel-headers was removed from unstable in 2007 (I think).  It
is now effectively a virtual package provided by linux-libc-dev, but
it's not a documented virtual package name and I would like to stop
providing it.

linux-libc-dev is (transitively) build-essential, so you do not need to
Build-Depend on it at all.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.



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

Bug#959458: matchbox-panel: Build-Depends on obsolete package linux-kernel-headers

[Ben Hutchings]

Package: src:matchbox-panel
Version: 0.9.3-10
Severity: serious

linux-kernel-headers was removed from unstable in 2007 (I think).  It
is now effectively a virtual package provided by linux-libc-dev, but
it's not a documented virtual package name and I would like to stop
providing it.

linux-libc-dev is (transitively) build-essential, so you do not need to
Build-Depend on it at all.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.



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

Bug#944494: The same bug happen to me

[Davide Lombardo]

Every time I click on the Media icon the program crash after few seconds

$ uname -a

Linux PC0 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1+deb10u1 (2020-04-27) x86_64 
GNU/Linux uname -a

$ apt-cache show jami

Package: jami
Source: ring
Version: 20190215.1.f152c98~ds1-1
 ...

$ gnome.-ring 
** Message: 16:46:50.975: Jami GNOME client version: 
dd9a8fb6323e3b170664c77b2e7173a2d10dc00f
** Message: 16:46:50.975: git ref: unknown
Updating all accounts
Loading "6ed0e3315209a825"
QDBusMarshaller: type `VectorString' attempts to redefine basic D-BUS type 
'as' (QStringList) (Did you forget to call beginStructure() ?)
QDBusMarshaller: type `MapStringVectorString' produces invalid D-BUS signature 
`a{s}' (Did you forget to call beginStructure() ?)
QDBusMarshaller: type `QMap' produces invalid 
D-BUS signature `a{s}' (Did you forget to call beginStructure() ?)

(gnome-ring:9713): Gtk-CRITICAL **: 16:46:53.551: gtk_scrolled_window_add: 
assertion 'child_widget == NULL' failed
No profile selected or none exists
QDBusConnection: name 'cx.ring.Ring' had owner '' but we thought it was ':
1.208'
lookup name NOT FOUND: "" "6ed0e3315209a825"
lookup name NOT FOUND: "" "6ed0e3315209a825"
could not open shm area "" , shm_open failed: Invalid argument
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Video::ShmRenderer(0x7feb9000c4d0), parent's thread is 
QThread(0x5621ad469620), current thread is QThread(0x5621acd87b70)
Terminated

Bug#959225: libcap-ng FTBFS: Build-Depends: linux-kernel-headers is no longer provided

[Ben Hutchings]

On Fri, 1 May 2020 09:18:20 +0200 Helmut Grohne  wrote:
> Source: libcap-ng
> Version: 0.7.9-2.1
> Severity: serious
> Tags: ftbfs patch
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> libcap-ng fails to build from source, because linux-libc-dev no longer
> provides linux-kernel-headers, which is what libcap-ng Build-Depends on.
> Please transition your dependency to linux-libc-dev:
> 
> sed -i -e 's/linux-kernel-headers/linux-libc-dev/' debian/control

I will restore this Provides temporarily as I had failed to see that
there were still build-dependencies on it.  But please do remove linux-
kernel-headers, as it's not a documented virtual package.

linux-libc-dev is (transitively) build-essential, so there is no need
to explicitly Build-Depend on it.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.




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

Bug#959455: fakeroot-ng: Build-Depends on obsolete package linux-kernel-headers

[Ben Hutchings]

Package: src:fakeroot-ng
Version: 0.18-4
Severity: serious

linux-kernel-headers was removed from unstable in 2007 (I think).  It
is now effectively a virtual package provided by linux-libc-dev, but
it's not a documented virtual package name and I would like to stop
providing it.

linux-libc-dev is (transitively) build-essential, so you do not need to
Build-Depend on it at all.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.



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

Bug#959456: inotify-tools: Build-Depends on obsolete package linux-kernel-headers

[Ben Hutchings]

Package: src:inotify-tools
Version: 3.14-8
Severity: serious

linux-kernel-headers was removed from unstable in 2007 (I think).  It
is now effectively a virtual package provided by linux-libc-dev, but
it's not a documented virtual package name and I would like to stop
providing it.

linux-libc-dev is (transitively) build-essential, so you do not need to
Build-Depend on it at all.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.



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

Bug#959457: isakmpd: Build-Depends on obsolete package linux-kernel-headers

[Ben Hutchings]

Package: src:isakmpd
Version: 20041012-8
Severity: serious

linux-kernel-headers was removed from unstable in 2007 (I think).  It
is now effectively a virtual package provided by linux-libc-dev, but
it's not a documented virtual package name and I would like to stop
providing it.

linux-libc-dev is (transitively) build-essential, so you do not need to
Build-Depend on it at all.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.



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