Bug#926832: di-netboot-assistant: di-netboot-assitant Version 0.62 shows Version 0.60 when calling di-netboot-assistant -V

[Ralf Moll]

Package: di-netboot-assistant
Version: 0.62
Severity: minor

Dear Maintainer,

just wanted to re-check my last bug-report

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926795

and noticed this:

dpkg --list di-netboot-assistant 
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version  Architecture Description
+++----==
ii  di-netboot-assistant 0.62 all  Debian-Installer
netboot assistant

but:

# di-netboot-assistant -V
di-netboot-assistant 0.60


Checked VCS für Buster 0.62:
https://salsa.debian.org/installer-team/netboot-assistant/blob/buster/di-netboot-assistant
equal to
https://salsa.debian.org/installer-team/netboot-assistant/blob/0.62/di-netboot-assistant

# -- Declare the constants --- #
PACKAGE_NAME=di-netboot-assistant 
PACKAGE_VERSION=0.60

Best regards,

Ralf

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

Kernel: Linux 4.19.0-4-amd64 (SMP w/2 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#920759: amdgpu+linux-images 4.9 & 4.19 crash randomly & always after X started

[franckr]

With kernel driver amdgpu & [AMD/ATI] Baffin [Polaris11] (radeon RX560).
Unfortunately new releases of kernel images crash too.
=> 4.19 is not anymore the solution vs 4.9.

linux-images 4.9 & 4.19 often (not systematically) crash randomly & always 
after X started (but I am seldomly a few minutes in console mode).
Usually within a few minutes after login.

I wonder why a version works, then a newer crashes, even with very different 
patch application dates, ex: 4.9.135 of 20-Oct-2018 works & 4.19.16 of 
16-Jan-2019 works, whereas in between 4.9.144-1 of 08-Dec-2018 crashes.

CrashZ (T>10, T>C)= (B) + linux-image-4.19.0-0.bpo.4-amd64-unsigned 
4.19.28-2~bpo9+1 = upstream 10-Mar-2019
Work   (T>>10)  = (B) + linux-image-4.19.0-0.bpo.2-amd64-unsigned 
4.19.16-1~bpo9+1 = upstream 16-Jan-2019
CrashM (T=C=1)  = (B) + linux-image-4.9.0-9-amd64 4.9.161-1 
= upstream 27-Feb-2019
Crash   = (A) + linux-image-4.9.0-8-amd64 4.9.144-1 
= upstream 08-Dec-2018 
Work= (A) + linux-image-4.9.0-8-amd64 4.9.135-1 
= upstream 20-Oct-2018

CrashZ = hard crashes: Keyboard do not respond anymore & Magic SysRq key do not 
work.
CrashM = Magic SysRq keys work (and allow a safe reboot).
T=number of tests
C=number of crashes

(B) = (firmware-amd-graphics   20190114-1) + (1920x1200 59.95Hz 8bit per RGB = 
nothing special)
(A) = (firmware-amd-graphics   20161130-4)

Graphic card:
  PowerColor Red Dragon Radeon™ RX 560 16CU 2GB GDDR5 OC
  RADEON RX 560
  AXRX 560 2GBD5-DHV2/OC
  https://www.powercolor.com/product?id=1496308686
  'AMDGPU(0): Chipset: "POLARIS11" (ChipID = 0x67ff)'

Kind Regards,
Franck

Bug#926831: unblock: u-boot/2019.01+dfsg-4

[Vagrant Cascadian]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal
X-Debbugs-Cc: debian-b...@lists.debian.org

Please unblock package u-boot

This upload enables support for four additional boards, and should
have a very low risc of regressions for existing boards, as no code
was changed.

Unfortunately debian-installer appears to be blocked from migrating to
testing due to u-boot.


diff -Nru u-boot-2019.01+dfsg/debian/changelog 
u-boot-2019.01+dfsg/debian/changelog
--- u-boot-2019.01+dfsg/debian/changelog2019-02-28 20:42:31.0 
-0800
+++ u-boot-2019.01+dfsg/debian/changelog2019-04-08 19:47:02.0 
-0700
@@ -1,3 +1,13 @@
+u-boot (2019.01+dfsg-4) unstable; urgency=medium
+
+  [ Martyn Welch ]
+  * [armhf] u-boot-imx: Enable build for NXP SABRE Lite.
+
+  [ Neil Armstrong ]
+  * [arm64] u-boot-amlogic: Enable nanopi-k2 and khadas-vim/vim2.
+
+ -- Vagrant Cascadian   Mon, 08 Apr 2019 19:47:02 -0700
+
 u-boot (2019.01+dfsg-3) unstable; urgency=medium
 
   [ Romain Perier ]
diff -Nru u-boot-2019.01+dfsg/debian/targets u-boot-2019.01+dfsg/debian/targets
--- u-boot-2019.01+dfsg/debian/targets  2019-02-28 20:38:15.0 -0800
+++ u-boot-2019.01+dfsg/debian/targets  2019-04-08 14:01:19.0 -0700
@@ -37,6 +37,9 @@
 # Rick Thomas , Cubox-i4x4, Cubox-i4PRO
 armhf  imx mx6cuboxi   u-boot.img SPL
 
+# Martyn Welch 
+armhf  imx mx6qsabrelite   u-boot.imx
+
 # Hector Oron 
 armhf  imx nitrogen6q  u-boot.imx
 
@@ -165,9 +168,16 @@
 # Ian Campbell 
 armhf  tegra   jetson-tk1  u-boot-tegra.bin
 
+# Neil Armstrong 
+arm64  amlogic khadas-vim  u-boot.bin
+arm64  amlogic khadas-vim2 u-boot.bin
+
 # Frederic Danis 
 arm64  amlogic libretech-ccu-boot.bin
 
+# Neil Armstrong 
+arm64  amlogic nanopi-k2   u-boot.bin
+
 # Vagrant Cascadian 
 arm64  amlogic odroid-c2   u-boot.bin
 
diff -Nru u-boot-2019.01+dfsg/debian/u-boot-amlogic.install 
u-boot-2019.01+dfsg/debian/u-boot-amlogic.install
--- u-boot-2019.01+dfsg/debian/u-boot-amlogic.install   2019-02-28 
20:38:15.0 -0800
+++ u-boot-2019.01+dfsg/debian/u-boot-amlogic.install   2019-04-08 
14:01:19.0 -0700
@@ -1,2 +1,2 @@
 #!/bin/sh
-debian/bin/u-boot-install-targets amlogic 
"board/amlogic/odroid-c2/README.odroid-c2 
board/amlogic/p212/README.libretech-cc"
+debian/bin/u-boot-install-targets amlogic 
"board/amlogic/odroid-c2/README.odroid-c2 
board/amlogic/odroid-c2/README.nanopi-k2 board/amlogic/p212/README.khadas-vim 
board/amlogic/p212/README.libretech-cc board/amlogic/q200/README.khadas-vim2"


unblock u-boot/2019.01+dfsg-4


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#926431: [Pkg-samba-maint] Bug#926431: cifs-utils: Password containing special character "$" (dollar) only works with prepended backslash

[Mathieu Parent]

Le ven. 5 avr. 2019 à 03:21, Lars Kruse  a écrit :
>
> Package: cifs-utils
> Version: 2:6.8-2
> Severity: normal
>
> Dear Maintainer,
>
> recently I changed my LDAP password to a new one, that contains a "$" 
> character.
> Afterwards I failed to mount shares with this new password.
>
> I tried the following approaches:
> * interactive mount (e.g. "mount -t cifs -o user=foo //example/share /mnt")
> * credential file
>   (e.g. "mount -t cifs -o user=foo,credentials=bar //example/share /mnt")
> * indirect mount via "pam_mount"
>
> In the first two cases I succeed to mount the share, if I prepend the
> special character ("$") with a backslash. Thus "pass\$word" works, while
> the real password is "pass$word".
> The last case ("pam_mount") was obviously impossible to test this way.
>
> I observed the same behaviour with a client on jessie (2:6.4-1) and on
> stretch (2:6.7-1).

Thanks for your report. Reading the source of cifs-utils and linux, I
don't find where the dollar sign is unescaped.

As a workaround for pma_mount, you may use a  wrapper command.

See https://manpages.debian.org/testing/libpam-mount/pam_mount.conf.5.en.html

Regards

-- 
Mathieu Parent

Bug#922996: Bug#923176: stretch-pu: package ca-certificates-java/20170929~deb9u1

[tony mancill]

On Wed, Apr 10, 2019 at 06:25:42AM -0700, tony mancill wrote:
> On Wed, Apr 10, 2019 at 09:49:02AM +0200, Andreas Beckmann wrote:
> > Hi Tony,
> > 
> > do we have another error in the script?
> > 
> > Setting up ca-certificates-java (20170929~deb9u2) ...
> > /var/lib/dpkg/info/ca-certificates-java.postinst: line 55: printf: -d: 
> > invalid option
> > printf: usage: printf [-v var] format [arguments]
> > Adding debian:TrustCor_RootCert_CA-2.pem
> > Adding debian:TrustCor_RootCert_CA-1.pem
> > ...
> > 
> > (noticed while looking for something different ..)
> 
> Hello Andreas,
> 
> Yes, and the error is due to this hunk in my patch:
> 
> > --- ca-certificates-java-20170929~deb9u1/debian/postinst.in 2019-02-11 
> > 04:14:23.0 -0800
> > +++ ca-certificates-java-20170929~deb9u2/debian/postinst.in 2019-02-24 
> > 09:55:04.0 -0800
> > @@ -52,7 +52,7 @@
> >  
> >  # Forcibly remove diginotar cert (LP: #920758)
> >  if [ -n "$FIXOLD" ]; then
> > -echo -e "-diginotar_root_ca\n-diginotar_root_ca_pem" | \
> > +printf "-diginotar_root_ca\n-diginotar_root_ca_pem\n" | \
> >  java -Xmx64m -jar $JAR -storepass "$storepass"
> >  fi
> 
> I didn't realize that the behavior of printf varied between the shells.
> 
> - printf "-dfoo" fails in dash and ash, but not in bash or zsh, etc.
> - printf '-dfoo' fails in dash and ash as well.
> - printf -- "-dfoo" works as expected.

Bah! - please ignore my comments above.  The `printf "-dfoo" fails in
other shells too.  And even more frustrating is that there wasn't any
point in trying to address the "echo -e" bashism in the postinst in the
first place, since it uses /bin/bash shebang anyway (unlike jks-keystore,
which runs under /bin/sh).

> Sorry for the hassle and thank you for noticing this.
>
> I will prepare another upload.

Since Andreas fixed another bashism in the postinst with his proposed
debdiff [1], I propose that we move forward with the fixed printf syntax
(debdiff attached), since it matches other uses of printf in the
postinst.

I have tested locally in a chroot, including forcing the execution path
to flow through the $FIXOLD path and believe it's fixed now.

Andreas, please let me know if this looks okay to you and I'll file the
stretch-pu bug. 

Thank you,
tony

[1] 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=922996;filename=ca-certificates-java_20170929~deb9u2.dsc.diff.gz;msg=5
diff -Nru ca-certificates-java-20170929~deb9u2/debian/changelog ca-certificates-java-20170929~deb9u3/debian/changelog
--- ca-certificates-java-20170929~deb9u2/debian/changelog	2019-02-24 09:55:04.0 -0800
+++ ca-certificates-java-20170929~deb9u3/debian/changelog	2019-04-10 19:59:01.0 -0700
@@ -1,3 +1,10 @@
+ca-certificates-java (20170929~deb9u3) stretch; urgency=medium
+
+  * Team upload.
+  * Fix printf syntax problem introduced in 20170929~deb9u2
+
+ -- tony mancill   Wed, 10 Apr 2019 19:59:01 -0700
+
 ca-certificates-java (20170929~deb9u2) stretch; urgency=medium
 
   * Team upload.
diff -Nru ca-certificates-java-20170929~deb9u2/debian/postinst.in ca-certificates-java-20170929~deb9u3/debian/postinst.in
--- ca-certificates-java-20170929~deb9u2/debian/postinst.in	2019-02-24 09:55:04.0 -0800
+++ ca-certificates-java-20170929~deb9u3/debian/postinst.in	2019-04-10 19:59:01.0 -0700
@@ -52,7 +52,7 @@
 
 # Forcibly remove diginotar cert (LP: #920758)
 if [ -n "$FIXOLD" ]; then
-printf "-diginotar_root_ca\n-diginotar_root_ca_pem\n" | \
+printf -- "-diginotar_root_ca\n-diginotar_root_ca_pem\n" | \
 java -Xmx64m -jar $JAR -storepass "$storepass"
 fi
 


signature.asc
Description: PGP signature

Bug#926830: unblock: uhubctl/2.0.0-5

[gustavo panizzo]

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

Please unblock package uhubctl

Hello release team

Recently I've updated the uhubctl package in experimental to fix its
autopkgtests which were failing.

The upload to experimental which fixed the issue was imported into
Ubuntu where it works fine [1]

I'd like to have that fix in buster if possible, a debdiff is attached

thanks!

[1] http://autopkgtest.ubuntu.com/packages/u/uhubctl/disco/amd64

unblock uhubctl/2.0.0-5

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 4.19.0-2-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
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 (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
diff -Nru uhubctl-2.0.0/debian/changelog uhubctl-2.0.0/debian/changelog
--- uhubctl-2.0.0/debian/changelog  2018-09-24 17:25:02.0 +0800
+++ uhubctl-2.0.0/debian/changelog  2019-04-10 16:30:47.0 +0800
@@ -1,3 +1,19 @@
+uhubctl (2.0.0-5) unstable; urgency=medium
+
+  * Upload to unstable.
+
+ -- gustavo panizzo   Wed, 10 Apr 2019 16:30:47 +0800
+
+uhubctl (2.0.0-4) experimental; urgency=medium
+
+  [ Ondřej Nový ]
+  * d/control: Add Vcs-* field
+
+  [ gustavo panizzo ]
+  * [fc94ec] Fix autopkgtest
+
+ -- gustavo panizzo   Wed, 03 Apr 2019 09:34:35 +0800
+
 uhubctl (2.0.0-3) unstable; urgency=medium
 
   * [f88227] Fix autopkgtests
diff -Nru uhubctl-2.0.0/debian/control uhubctl-2.0.0/debian/control
--- uhubctl-2.0.0/debian/control2018-09-24 17:25:02.0 +0800
+++ uhubctl-2.0.0/debian/control2019-04-01 10:14:07.0 +0800
@@ -5,6 +5,8 @@
 Build-Depends: debhelper (>= 11.0.0), libusb-1.0-0-dev, autopkgtest
 Standards-Version: 4.2.1
 Homepage: https://github.com/mvp/uhubctl
+Vcs-Browser: https://salsa.debian.org/debian/uhubctl
+Vcs-Git: https://salsa.debian.org/debian/uhubctl.git
 
 Package: uhubctl
 Architecture: any
diff -Nru uhubctl-2.0.0/debian/tests/control uhubctl-2.0.0/debian/tests/control
--- uhubctl-2.0.0/debian/tests/control  2018-09-24 17:25:02.0 +0800
+++ uhubctl-2.0.0/debian/tests/control  2019-04-02 17:06:31.0 +0800
@@ -1 +1,2 @@
 Tests: run-uhubctl-v
+Depends: @
diff -Nru uhubctl-2.0.0/debian/tests/run-uhubctl-v 
uhubctl-2.0.0/debian/tests/run-uhubctl-v
--- uhubctl-2.0.0/debian/tests/run-uhubctl-v2018-09-24 17:25:02.0 
+0800
+++ uhubctl-2.0.0/debian/tests/run-uhubctl-v2019-04-03 00:46:36.0 
+0800
@@ -4,4 +4,4 @@
 
 set -e
 
-./uhubctl -v
+uhubctl -v

Bug#926813: unblock: python-scipy/1.1.0-5

[Drew Parsons]

On 2019-04-11 04:38, Paul Gevers wrote:

Hi Drew,

On 10-04-2019 21:22, Paul Gevers wrote:
Thanks. I want to run a couple of tests, to see if it now appears 
stable

(the first two passed).

I'll unblock when I don't find any failure.


The score isn't great (and not all results are in): 3/14 failure (2 in
unstable, 1 in testing so far). Can you please have a look?



Apparently the same test failure does occur in python3 tests, but only 
some of the time not all of the time.  Weird.


I've uploaded 1.1.0-6 now to skip the same 2 tests in python3.


$ debdiff python-scipy_1.1.0-4.dsc python-scipy_1.1.0-6.dsc
diff -Nru python-scipy-1.1.0/debian/changelog 
python-scipy-1.1.0/debian/changelog
--- python-scipy-1.1.0/debian/changelog	2019-03-14 14:12:00.0 
+0800
+++ python-scipy-1.1.0/debian/changelog	2019-04-11 09:38:17.0 
+0800

@@ -1,3 +1,18 @@
+python-scipy (1.1.0-6) unstable; urgency=medium
+
+  * Team upload.
+  * skip sparsetools.TestInt32Overflow matvec tests on python3 also.
+
+ -- Drew Parsons   Thu, 11 Apr 2019 09:38:17 +0800
+
+python-scipy (1.1.0-5) unstable; urgency=medium
+
+  * Team upload.
+  * Skip sparsetools.TestInt32Overflow matvec tests on python2
+(MemoryError). Closes: #919929.
+
+ -- Drew Parsons   Wed, 10 Apr 2019 16:41:47 +0800
+
 python-scipy (1.1.0-4) unstable; urgency=medium

   * Team upload.
diff -Nru python-scipy-1.1.0/debian/tests/python2 
python-scipy-1.1.0/debian/tests/python2
--- python-scipy-1.1.0/debian/tests/python2	2019-03-14 
14:12:00.0 +0800
+++ python-scipy-1.1.0/debian/tests/python2	2019-04-11 
09:38:17.0 +0800

@@ -27,6 +27,9 @@
 
"sparse.tests.test_sparsetools.TestInt32Overflow.test_bsr_n_block[matmat]",
 
"sparse.tests.test_sparsetools.TestInt32Overflow.test_bsr_n_block[matvecs]",
 
"sparse.tests.test_sparsetools.TestInt32Overflow.test_bsr_n_block[transpose]",

+# postscriptum on Bug#919929
+"sparse.tests.test_sparsetools.TestInt32Overflow.test_matvecs",
+"sparse.tests.test_sparsetools.TestInt32Overflow.test_dia_matvec",
 ]

 junit = "$TMPDIR/junit.xml"
diff -Nru python-scipy-1.1.0/debian/tests/python3 
python-scipy-1.1.0/debian/tests/python3
--- python-scipy-1.1.0/debian/tests/python3	2019-03-14 
14:12:00.0 +0800
+++ python-scipy-1.1.0/debian/tests/python3	2019-04-11 
09:38:17.0 +0800

@@ -19,6 +19,9 @@
 "linalg.tests.test_solvers.test_solve_generalized_discrete_are",
 # fails with atlas
 "linalg.tests.test_solvers.test_solve_discrete_are",
+# postscriptum on Bug#919929
+"sparse.tests.test_sparsetools.TestInt32Overflow.test_matvecs",
+"sparse.tests.test_sparsetools.TestInt32Overflow.test_dia_matvec",
 ]

 junit = "$TMPDIR/junit.xml"

Bug#925890: Acknowledgement (xrdp: session doesn't start correctly after sesman got SIGUP)

[Koichiro Iwao]

I think you'll need some more information. v0.9.7, v0.9.8, v0.9.9 have
this bug. The upcoming v0.9.10 includes this fix. I know Debian hardly
apply version update except unstable so I want you to consider applying
this fix to the branches such as stable-bpo. The original issue #1315 is
reported by a Debian user. At least a Debian user is annoyed because of
our bug.

This issue is a kind of availability. New sessions cannot be started
after xrdp-sesman caught SIGUP unless DefaultWindowManager in sesman.ini
is specified in full path. Same with ReconnectScript. It won't be
executed unless it is specified in full path.

I'm not sure Debian rotates xrdp log, the major scenario that
xrdp-sesman catch SIGUP is log rotation.

-- 
meta 

Bug#926787: ghostscript: "filter failed"

[James Van Zandt]

Yes, this is the same as #926576.  You may merge them.

Bug#926297: duplicity: azure dependency broken?

[dean]

It seems that this works as you suggest:

pip install azure-storage==0.20.0

At least its a problem understood upstream. It has some chance of being 
resolved



On Fri, 05 Apr 2019 12:43:47 +1000 Alexander Zangerl  
wrote:


> tags 926297 + upstream
> forwarded 926297 https://bugs.launchpad.net/duplicity/+bug/1694770
> thanks
>
> On Wed, 03 Apr 2019 14:27:31 +1100, Dean Hamstead writes:
> >Similarly, if i do a 'pip install azure' i get the same error.
>
> that's an api incompatibility problem known to upstream
> (see the launchpad tracker link above). a comment on that bug report
> indicates that forcing the installation of
> an older azure api version with
>
> pip install azure-storage==0.20.0
>
> should provide a workaround for now (you may also have to ditch the
> python-azure-storage debian package).
>
> regards
> az
>
>
> --
> Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/
> AA - American Association Against Acronym Abuse Anonymous.



Psst! It's possible that this email contains information that is on the super secret side 
of confidential. So if you received it accidentally, let the sender know straight away and 
delete it (and the email you sent them). Also, we should let you know that any emails that 
come and go through Winc might be scanned, stored or read by Winc at 
its discretion. If you've got a question, please give us a buzz on +61 2 9335 0555 
(Australia) or +64 9 271 7600 (NZ). Oh, and Winc does its best to avoid errors 
on emails it sends, but we can't promise that it will be error free. So, please don't hold 
it against us.

Bug#926825: faudio: FTBFS (Missing build-dependency on cmake)

[Hillel Lubman]

This also prevents i386 version from being built, which in turn blocks using 
newer 32-bit Wine which now depends on faudio.

Please re-upload the package with build-depends for cmake, and you can as well 
use the newest version:  19.04.

Regards,
Hillel Lubman.

Bug#818366: Synaptic on Buster/SID

[Marshall Neill]

I see that Synaptic cannot be opened.
I believe the correct way is

synaptic-pkexec

Regards

Bug#923878: bash-completion: unrar completion doesn't suggest *.rar files immedietly, but requires options first (uneeded)

[Gabriel F. T. Gomes]

On Wed, Apr 10 2019, Witold Baryluk wrote:
> 
> I am using a free version of unrar, in package unrar-free in main repo of 
> Debian:
> 
> [...]
> 
> $ unrar-free --version
> unrar 0.0.1
> $ unrar --version
> unrar 0.0.1

Oh, I see.  Thanks for the explanation.

> Note that OPTION part is optional, i.e. -x / --extract is default.

I guess you are right.  I'll work on it.

Bug#926829: voctomix-outcasts: usb audio needs gstreamer1.0-alsa

[Carl Karsten]

Package: voctomix-outcasts
Version: package needs gstreamer1.0-alsa added to recommends
Severity: important

Dear Maintainer,

A show said "oh, no audio"  so I'm hooking a usb mic to the Opsis
slave, which needs gstreamer1.0-alsa.

this fixed it:
apt install gstreamer1.0-alsa

please package v0.8.0 waiting in git and add gstreamer1.0-alsa


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

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

-- 
Carl K

Bug#926828: voctomix-outcasts: EOS errors

[Carl Karsten]

Package: voctomix-outcasts
Version: v0.7.0
Severity: important

Dear Maintainer,

Hi!

I wanted 5 seconds of test pattern, but limiting the stream to 5 seccodns
does exit(1) and things abort.  so I fixed it.  go me.

please package v0.8.0 waiting in git

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

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


-- 
Carl K

Bug#926823: executable-not-elf-or-script should consider PE binaries

[Michael Biebl]

Am 11.04.19 um 01:22 schrieb Felix Lechner:
> It's just that the lintian tag is not
> triggered when the bit is off.

That much I figured :-)


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#926823: executable-not-elf-or-script should consider PE binaries

[Felix Lechner]

On Wed, Apr 10, 2019 at 4:16 PM Michael Biebl  wrote:
>
> Those bits are set by ld respectively objcopy when the binaries are
> generated. Are you implying that ld/objcopy should not do that?

No, you may well need it. It's just that the lintian tag is not
triggered when the bit is off.

Bug#926823: executable-not-elf-or-script should consider PE binaries

[Michael Biebl]

Am 10.04.19 um 23:46 schrieb Felix Lechner:
> On Wed, Apr 10, 2019 at 2:33 PM Michael Biebl  wrote:
>>
>> systemd ships EFI binaries which are PE executables.
>>
>> usr/lib/systemd/boot/efi/linuxia32.efi.stub [amd64, i386]
>> usr/lib/systemd/boot/efi/linuxx64.efi.stub [amd64, i386]
>> usr/lib/systemd/boot/efi/systemd-bootia32.efi [amd64, i386]
>> usr/lib/systemd/boot/efi/systemd-bootx64.efi [amd64, i386]
>>
>> I wonder whether executable-not-elf-or-script should be made aware of PE
>> executables and not warn about them.
> 
> Does systemd-boot require the executable bits to be set on these files?

Those bits are set by ld respectively objcopy when the binaries are
generated. Are you implying that ld/objcopy should not do that?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#926826: ruby-guard: FTBFS (failing tests)

[Santiago Vila]

Package: src:ruby-guard
Version: 2.15.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby

[... snipped ...]

returns multiple plugin scopes
returns a group scope

Guard::Deprecated::Watcher
  .match_guardfile?
matches against current guardfile
displays a deprecation warning to the user

Guard::Guardfile::Generator
  has a valid Guardfile template
  #initialize_template
with an installed Guard implementation
  initializes the Guard
with a user defined template
  copies the Guardfile template and initializes the Guard
when the passed guard can't be found
  notifies the user about the problem
  #initialize_all_templates
calls Guard.initialize_template on all installed plugins
  #create_guardfile
with an existing Guardfile
  aborts
  displays an error message
  does not display information
  does not copy the Guardfile template or notify the user
without an existing Guardfile
  copies the Guardfile template and notifies the user
  does not display any kind of error or abort

Guard::CLI
  #show
stub me: ENV[GEM_REQUIREMENT_IO-CONSOLE]!

Finished in 9.46 seconds (files took 1.48 seconds to load)
217 examples, 0 failures

Randomized with seed 39874

/usr/bin/ruby2.5 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb -I 
spec -r spec_helper --no-fail-fast failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-guard returned 
exit code 1
make[1]: *** [debian/rules:9: override_dh_auto_install] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#926827: ruby-vcr: FTBFS (failing tests)

[Santiago Vila]

Package: src:ruby-vcr
Version: 4.0.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby

[... snipped ...]

 #   An HTTP request has been made that VCR does not know how to handle:
 # GET http://localhost:34979/search?q=thread
 #   
 #   VCR are currently using the following cassettes:
 # - /<>/tmp/cassette_library_dir/search.yml
 #   - :record => :once
 #   - :match_requests_on => [:method, :uri]
 # - /<>/tmp/cassette_library_dir/foo.yml
 #   - :record => :once
 #   - :match_requests_on => [:method, :uri]
 #   
 #   Under the current configuration VCR can not find a suitable HTTP 
interaction
 #   to replay and is prevented from recording new requests. There are a 
few ways
 #   you can deal with this:
 #   
 # * If you're surprised VCR is raising this error
 #   and want insight about how VCR attempted to handle the request,
 #   you can use the debug_logger configuration option to log more 
details [1].
 # * You can use the :new_episodes record mode to allow VCR to
 #   record this new request to the existing cassette [2].
 # * If you want VCR to ignore this request (and others like it), you 
can
 #   set an `ignore_request` callback [3].
 # * The current record mode (:once) does not allow new requests to be 
recorded
 #   to a previously recorded cassette. You can delete the cassette 
file and re-run
 #   your tests to allow the cassette to be recorded with this request 
[4].
 #   
 #   [1] 
https://www.relishapp.com/vcr/vcr/v/4-0-0/docs/configuration/debug-logging
 #   [2] 
https://www.relishapp.com/vcr/vcr/v/4-0-0/docs/record-modes/new-episodes
 #   [3] 
https://www.relishapp.com/vcr/vcr/v/4-0-0/docs/configuration/ignore-request
 #   [4] https://www.relishapp.com/vcr/vcr/v/4-0-0/docs/record-modes/once
 #   

 #   ./lib/vcr/request_handler.rb:97:in `on_unhandled_request'

Finished in 26.5 seconds (files took 2.79 seconds to load)
1725 examples, 1 failure

Failed examples:

rspec ./spec/acceptance/concurrency_spec.rb:15 # VCR when used in a 
multithreaded environment with an around_http_request can use a cassette in an 
#around_http_request hook

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-vcr returned 
exit code 1
make: *** [debian/rules:6: binary-indep] Error 1
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here at least in the arm64 architecture:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#922251: live-build: support syslinux-efi as (additional) bootloader

[adrian15]

El 08/04/19 a las 21:29, Matthijs Kooijman escribió:
> Hi Luca & others,
> 
> I've been working on syslinux-efi support in the past weeks and just
> submitted a MR with a working implementation, along with some small
> bootloader-related cleanups and refactors:
> 
>   https://salsa.debian.org/live-team/live-build/merge_requests/19
Commenting below.
> 
> In the end, I opted to implement syslinux-efi rather than make grub-efi
> work on hdd images, since that seemed easier and allows preserving the
> existing bootloader config files in our project. Getting grub-efi to
> work on hdd images might still be an interesting project that could be
> implemented alongside syslinux-efi support, though I do not have any
> specific purpose for it as of yet.
I implemented multi bootloader support back in the day and maybe
grub-efi, not sure about that last one.

I didn't implement the hdd part because I didn't know what was the
purpose of an hdd image and how I was supposed to test it.

I might take a look into your notes to implement grub-efi + secure boot
in hdd img but... this might be in 2021 XD . Too busy at the moment.

What's your use case? What do you need to build live-build based hdd
imgs? I'm curious.

> As predicted by others in this bug report, my work does not enable
> secure boot (which syslinux simply does not support), nor enable
> syslinux-efi support in iso/isohybrid images (since syslinux-efi does
> not support this, or at least it apparently does not work).

Nice. What you need to make sure is that you cannot choose syslinux-efi
when trying to build iso/isohybrid images.

> Gr.
> 
> Matthijs

> 0) backward incompatible change
In the pull request there is a mention about a backward incompatible
change. Can you please describe in what that change consists?

> 1) Refactor some bootloader scripts (969cdf4e)

1.1) Nice idea the Get_Bootloader_Config_Dir function.
Have you made sure that $BOOTLOADER variable is not used anywhere else
in the code?
Maybe you should make that variable local.

1.2) The function Install_Bootloader_Files does not seem to be right.
If you are not going to reuse that function in more than one place (I'll
check your other commits later) you might consider not having that
function in the first place.

Even if the Install_Bootloader_Files function was a good idea it's not
well implemented commit-wise. You are performing two changes. One about
moving the functionality to a function. Another one is chaning the
comment about "two steps" to "three steps". It's hard to notice if you
changed something other than that comment on that commit.

I mean... this part should be splitted in two commits.

> 2) Reduce config duplication in syslinux variants (bccd127b)

I know it's better the way you merge files there but I think the
original idea was about having independent configuration files for each
different media.

I mean there were not meant to be merged together in the first place.

> 3) Remove ldlinux.c32 for extlinux and syslinux (6fc68c1d)

3.1) Nice. I didn't know about those new syslinux architecture dependent
files. As per the wiki you link (
https://wiki.syslinux.org/wiki/index.php?title=Library_modules#All_Syslinux_variants_need_an_additional_ldlinux_module
) in the commit description I guess that even ldlinux.c32 wouldn't be
used but ldlinux.e64 instead.

3.2) BTW Do you support both EFI IA32 and EFI X64 or only EFI X64 ?

> 4) Move syslinux modules into subdirectories (53901001)

Shouldn't those c32 modules be moved to a folder named c32-modules (or
c32mods for short name) instead?

Let's see how you name the UEFI modules folder later.

In "Add syslinux-efi bootloader support (a271f8f9)" you use modules32
folder name for some c32. Shouldn't you use modules32 as a folder name
in this "Remove ldlinux.c32 for extlinux and syslinux (6fc68c1d)" commit
in the first place?

I'm not sure about this one I might be missing something.

>  5) Add syslinux-efi bootloader support (a271f8f9)
5.1) You have got a nice bug on that code XD . Just after the Echo_error
statements about syslinux-efi not being supported there should be an
exit 1 statement.

Else you are just echoing a warning but not stopping the build.

5.2) Anyway I don't think I like this code at all. I mean... you are
supposed to create a new file named:
scripts/build/binary_syslinux-efi
and not hack around the existant one: binary_syslinux
.

I know it's difficult to work on a new binary file because of the way
binary_syslinux handles kernel images and renames them.
But I was able to handle that on the loopback.cfg binary file.

Probably the common code for generating cfg files should be on a common
binary file which it's only triggered if either binary_syslinux or
binary_syslinux-efi is being used as a bootloader.

5.3) I see you add a lot of c32 and efi as symbolic links to paths on
the system.
I'm not sure this is the right way of doing this.
Are other equivalent files already implemented like you are doing?
Or is it me 

Bug#926825: faudio: FTBFS (Missing build-dependency on cmake)

[Santiago Vila]

Package: src:faudio
Version: 19.02-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules binary-arch
dh binary-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
install -d obj-x86_64-linux-gnu
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
Can't exec "cmake": No such file or directory at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 475.
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. failed to execute: No child 
processes
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. returned exit code 2
make: *** [debian/rules:13: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


Seems like a missing build-depends on cmake.

Thanks.

Bug#926823: executable-not-elf-or-script should consider PE binaries

[Felix Lechner]

On Wed, Apr 10, 2019 at 2:33 PM Michael Biebl  wrote:
>
> systemd ships EFI binaries which are PE executables.
>
> usr/lib/systemd/boot/efi/linuxia32.efi.stub [amd64, i386]
> usr/lib/systemd/boot/efi/linuxx64.efi.stub [amd64, i386]
> usr/lib/systemd/boot/efi/systemd-bootia32.efi [amd64, i386]
> usr/lib/systemd/boot/efi/systemd-bootx64.efi [amd64, i386]
>
> I wonder whether executable-not-elf-or-script should be made aware of PE
> executables and not warn about them.

Does systemd-boot require the executable bits to be set on these files?

Bug#926824: go-md2man: Produced manpages contain many warnings "manpage-has-bad-whatis-entry" lintian warnings

[Reinhard Tartler]

Source: go-md2man
Severity: normal

I'm using this tool in the golang-github-containers-storage. At the end
of the package build, I see lots of warnings like this:

,
| W: containers-storage: manpage-has-bad-whatis-entry 
usr/share/man/man1/containers-storage-mounted.1.gz
| W: containers-storage: manpage-has-bad-whatis-entry 
usr/share/man/man1/containers-storage-set-container-data.1.gz
| W: containers-storage: manpage-has-bad-whatis-entry 
usr/share/man/man1/containers-storage-set-image-data.1.gz
| W: containers-storage: manpage-has-bad-whatis-entry 
usr/share/man/man1/containers-storage-set-metadata.1.gz
| W: containers-storage: manpage-has-bad-whatis-entry 
usr/share/man/man1/containers-storage-set-names.1.gz
| W: containers-storage: manpage-has-bad-whatis-entry 
usr/share/man/man1/containers-storage-shutdown.1.gz
| W: containers-storage: manpage-has-bad-whatis-entry 
usr/share/man/man1/containers-storage-status.1.gz
| W: containers-storage: manpage-has-bad-whatis-entry 
usr/share/man/man1/containers-storage-unmount.1.gz
| W: containers-storage: manpage-has-bad-whatis-entry 
usr/share/man/man1/containers-storage-version.1.gz
| W: containers-storage: manpage-has-bad-whatis-entry 
usr/share/man/man1/containers-storage-wipe.1.gz
`


The description of the lintian warning reads:

,[ lintian-info -t manpage-has-bad-whatis-entry
| W: manpage-has-bad-whatis-entry
| N:
| N:   Each manual page should start with a "NAME" section, which lists the
| N:   name and a brief description of the page separated by "\-". The "NAME"
| N:   section is parsed by lexgrog and used to generate a database that's
| N:   queried by commands like apropos and whatis. This tag indicates that
| N:   lexgrog was unable to parse the NAME section of this manual page.
| N:   
| N:   For manual pages that document multiple programs, functions, files, or
| N:   other things, the part before "\-" should list each separated by a
| N:   comma and a space. Each thing listed must not contain spaces; a man
| N:   page for a two-part command like "fs listacl" must use something like
| N:   "fs_listacl" in the "NAME" section so that it can be parsed by
| N:   lexgrog.
| N:   
| N:   Refer to the lexgrog(1) manual page, the groff_man(7) manual page, and
| N:   the groff_mdoc(7) manual page for details.
| N:   
| N:   Severity: normal, Certainty: certain
| N:   
| N:   Check: manpages, Type: binary
| N:
`

The .md files have headers that look like this:

,
| ## containers-storage-add-names "August 2016"
| 
| ## NAME
| containers-storage add-names - Add names to a layer/image/container
| [...]
`

AFAIUI the generated manpage should produce '\-' instead of '-' to have a 
functional
whatis database and unbreak lexgrog.

Best,
-rt

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

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

Bug#926306: RFS: socklog/2.1.0-9

[Mathieu Mirmont]

On Wed, Apr 10, 2019 at 08:20:30AM +, Dmitry Bogatov wrote:
> You can repack it as new upstream version. New version would be
> something like `2.1.0+repack-1'. Do not forget add clarification into
> Debian.source.

I've updated the package and uploaded to mentors:

https://mentors.debian.net/package/socklog
https://mentors.debian.net/debian/pool/main/s/socklog/socklog_2.1.0+repack-1.dsc

-- 
Mathieu Mirmont 


signature.asc
Description: PGP signature

Bug#921949: golang-github-containers-storage_1.5-1_amd64.changes REJECTED

[Reinhard Tartler]

Hi Thorsten,

thank you for looking at the package.

On 4/10/19 3:00 PM, Thorsten Alteholz wrote: 
> I don't think that it is ok to add all contributors to your debian/copyright
> although the LICENSE says that Docker, Inc claims the copyright (and they
> are missing).

I don't think this is accurate either. Most if of not all upstream maintainers 
are actually RedHat employees. This may not be obvious from looking at the 
source code.

Would it be acceptable to state "(C) 2013-2019 github.com/containers/storage 
maintainers"?

If neither that rather vague specification (which is used in packages such as 
docker, cf. 
https://tracker.debian.org/media/packages/d/docker.io/copyright-18.09.1dfsg1-5 
and Linux, cf. 
https://tracker.debian.org/media/packages/l/linux/copyright-5.0.2-1exp1, as 
well), nor the authors listed in the AUTHORS file is acceptable, what would you 
recommend me to do?

> While you are at it, please also mention pkg/mflag in your debian/copyright.

Thanks for the hint. In fact, I've already started working on a new upstream 
release and have clarified the pkg/mflag license.

Cheers,
-rt

Bug#926823: executable-not-elf-or-script should consider PE binaries

[Michael Biebl]

Package: lintian
Version: 2.12.0
Severity: normal

Hi,

systemd ships EFI binaries which are PE executables.
This triggers lintian:
executable-not-elf-or-script

usr/lib/systemd/boot/efi/linuxia32.efi.stub [amd64, i386]
usr/lib/systemd/boot/efi/linuxx64.efi.stub [amd64, i386]
usr/lib/systemd/boot/efi/systemd-bootia32.efi [amd64, i386]
usr/lib/systemd/boot/efi/systemd-bootx64.efi [amd64, i386]

Some packages seem to override that, like in
https://salsa.debian.org/efi-team/fwupd/blob/debian/debian/lintian/fwupd#L8

I wonder whether executable-not-elf-or-script should be made aware of PE
executables and not warn about them.

Regards,
Michael

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

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

Versions of packages lintian depends on:
ii  binutils   2.31.1-16
ii  bzip2  1.0.6-9
ii  diffstat   1.62-1
ii  dpkg   1.19.6
ii  dpkg-dev   1.19.6
ii  file   1:5.35-4
ii  gettext0.19.8.1-9
ii  gpg2.2.13-1
ii  intltool-debian0.35.0+20060710.5
ii  libapt-pkg-perl0.1.34+b1
ii  libarchive-zip-perl1.64-1
ii  libcapture-tiny-perl   0.48-1
ii  libcgi-pm-perl 4.40-1
ii  libclass-accessor-perl 0.51-1
ii  libclone-perl  0.41-1+b1
ii  libdigest-sha-perl 6.02-1+b1
ii  libdpkg-perl   1.19.6
ii  libemail-valid-perl1.202-1
ii  libfile-basedir-perl   0.08-1
ii  libio-async-perl   0.72-1
ii  libipc-run-perl20180523.0-1
ii  liblist-moreutils-perl 0.416-1+b4
ii  libparse-debianchangelog-perl  1.2.0-13
ii  libpath-tiny-perl  0.108-1
ii  libtext-levenshtein-perl   0.13-1
ii  libtimedate-perl   2.3000-2
ii  libtry-tiny-perl   0.30-1
ii  liburi-perl1.76-1
ii  libxml-simple-perl 2.25-1
ii  libyaml-libyaml-perl   0.76+repack-1
ii  man-db 2.8.5-2
ii  patchutils 0.3.4-2
ii  perl   5.28.1-6
ii  t1utils1.41-3
ii  xz-utils   5.2.4-1

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b5

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  libhtml-parser-perl3.72-3+b3
ii  libtext-template-perl  1.55-1

-- no debconf information

Bug#926822: gimp: clean target is missing some files

[Faheem Mitha]

Package: gimp
Version: 2.10.8-2
Severity: normal

Dear Maintainer,

When trying to backport 2.10.8 from unstable to stable, I keep seeing

dpkg-source: info: local changes detected, the modified files are:
 gimp-2.10.8/app/tests/gimpdir/pluginrc
 gimp-2.10.8/app/tests/gimpdir/profilerc
 gimp-2.10.8/app/tests/gimpdir/themerc
dpkg-source: error: aborting due to unexpected upstream changes, see 
/tmp/gimp_2.10.8-2.diff.eL_rzG
dpkg-source: info: you can integrate the local changes with dpkg-source --commit
dpkg-buildpackage: error: dpkg-source -b gimp-2.10.8 gave error exit status 2
debuild: fatal error at line 1116:
dpkg-buildpackage -rfakeroot -us -uc failed

I'm using `debuild -uc -us` to build.

Either the Gimp is generating different files when building on stable,
or your cleanup is missing some files.

I'm not sure where your clean target is, or I would send a patch.

More details available if required, but I'm not sure what would be
relevant right now.

Since 2.10.8-2 isn't actually installed on my system when this bug
template was generated, the Gimp package information refers to the
Gimp in staxble.

Regards, Faheem Mitha

-- System Information:
Debian Release: 9.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (50, 'unstable'), (1, 
'experimental')
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=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gimp depends on:
ii  gimp-data2.8.18-1+deb9u1
ii  libaa1   1.4p5-44+b1
ii  libatk1.0-0  2.22.0-1
ii  libbabl-0.1-00.1.62-1
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.24-11+deb9u4
ii  libcairo21.14.8-1
ii  libdbus-1-3  1.10.26-0+deb9u1
ii  libdbus-glib-1-2 0.108-2
ii  libexif120.6.21-2+b2
ii  libexpat12.2.0-2+deb9u1
ii  libfontconfig1   2.12.6-0.1
ii  libfreetype6 2.6.3-3.2
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libgegl-0.3-00.3.8-4
ii  libgimp2.0   2.8.18-1+deb9u1
ii  libglib2.0-0 2.60.0-1
ii  libgs9   9.26a~dfsg-0+deb9u1
ii  libgtk2.0-0  2.24.31-2
ii  libgudev-1.0-0   230-3
ii  libice6  2:1.0.9-2
ii  libjpeg62-turbo  1:1.5.1-2
ii  libjson-glib-1.0-0   1.2.6-1
ii  liblcms2-2   2.9-3
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  libpng16-16  1.6.28-1
ii  libpoppler-glib8 0.48.0-2+deb9u2
ii  librsvg2-2   2.40.16-1+b1
ii  libsm6   2:1.2.2-1+b3
ii  libtiff5 4.0.8-2+deb9u4
ii  libwmf0.2-7  0.2.8.4-10.6
ii  libx11-6 2:1.6.4-3+deb9u1
ii  libxcursor1  1:1.1.14-1+deb9u2
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2
ii  libxpm4  1:3.5.12-1
ii  libxt6   1:1.1.5-1
ii  python   2.7.13-2
ii  python-gtk2  2.24.0-5.1
ii  python2.72.7.13-2+deb9u3
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages gimp recommends:
ii  ghostscript  9.26a~dfsg-0+deb9u1

Versions of packages gimp suggests:
pn  gimp-data-extras  
ii  gimp-help-en [gimp-help]  2.8.2-0.1
ii  gvfs-backends 1.30.4-1
ii  libasound21.1.3-5

-- debconf-show failed

Bug#914517: linux-image-4.19.0-4-amd64: System freezes with nomodeset set and boots in a loop without

[Robert Pommrich]

Am 10.04.19 um 22:32 schrieb Ben Hutchings:
> On Wed, 2019-04-10 at 17:26 +0200, Robert Pommrich wrote:
>> Hi,
>>
>> I really don't understand why the severity of this bug was lowered.
>> Plus, this was the only action taken on this bug beside my actions.
> [...]
>
> The phrase "renders package unusable" means that the package is
> unusable in general, or on a large proportion of Debian systems.
>
> I don't believe that that is the case for this bug.

Okay, what would be the right phrase for a system, that doesn't start?

>
> Ben.
>

Robert

Bug#926821: unblock: feersum/1.406-2

[Xavier Guimard]

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

Please unblock package feersum

Hi all,

due to libhttp-tiny-perl bug, feersum build fails when only one CPU is
available or on very poor configuration. I patched it to:
 * ignore errors on t/63-plack-apps.t test
 * don't test t/{13-pre-fork.t,60-plack.t,61-plack-suite.t} if nproc==1

See https://bugs.debian.org/909480 for the full discussion.

Feersum has no reverse dependencies.

Since this patch affects only tests, I think it is not risky to unblock
this new version. This fixes no bug but workaround #909480, severity
"normal" and avoid FTBFS.

Cheers,
Xavier

unblock feersum/1.406-2

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

Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/changelog b/debian/changelog
index a4832a2..153cbb3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+feersum (1.406-2) unstable; urgency=medium
+
+  * Declare compliance with policy 4.3.0
+  * Add patch to workaround libhttp-tiny-perl bug in tests and disable 3 other
+tests when only 1 CPU is available (#909480)
+
+ -- Xavier Guimard   Wed, 10 Apr 2019 21:24:03 +0200
+
 feersum (1.406-1) unstable; urgency=medium
 
   * debian/rules: fix Perl path in example files
diff --git a/debian/control b/debian/control
index 081e2ba..e995ca7 100644
--- a/debian/control
+++ b/debian/control
@@ -15,7 +15,7 @@ Build-Depends: debhelper (>= 10),
libtest-leaktrace-perl,
libtest-tcp-perl,
perl
-Standards-Version: 4.2.1
+Standards-Version: 4.3.0
 Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/feersum
 Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/feersum.git
 Homepage: https://metacpan.org/release/Feersum
diff --git a/debian/patches/series b/debian/patches/series
index aba7ccb..2bcab6e 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 autopkgtest.patch
+workaround-for-909480.diff
diff --git a/debian/patches/workaround-for-909480.diff 
b/debian/patches/workaround-for-909480.diff
new file mode 100644
index 000..7c22ffb
--- /dev/null
+++ b/debian/patches/workaround-for-909480.diff
@@ -0,0 +1,30 @@
+Description: Workaround for #909480
+ Feersum sometimes FTBFS due to libhttp-tiny-perl
+ bug (https://bugs.debian.org/909480
+ .
+ This workaround adds a "TODO" loop to not fail on build even if HTTP::Tiny
+ tries to reuse closed connections.
+Author: Xavier Guimard 
+Bug-Debian: https://bugs.debian.org/909480
+Forwarded: not-needed
+Last-Update: 2019-04-10
+
+--- a/t/63-plack-apps.t
 b/t/63-plack-apps.t
+@@ -22,6 +22,8 @@
+ use Plack::Request;
+ use Test::TCP;
+ 
++TODO: {
++local $TODO = 'Failure ignored to workaround #909480';
+ via_map: test_psgi(
+ app => builder {
+ mount '/' => Plack::App::File->new(root => 't');
+@@ -85,6 +87,7 @@
+ like $res->content, qr/^\Q$s\E$/m, "found static line (cascade)";
+ }
+ );
++}
+ 
+ __END__
+ # IS THIS FILE STATICALLY SERVED?
diff --git a/debian/rules b/debian/rules
index d1559c8..2f5ed39 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,6 +4,7 @@ PACKAGE = $(shell dh_listpackages)
 TMP = $(CURDIR)/debian/$(PACKAGE)
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+TEST_FILES_1_CPU=$(filter-out t/13-pre-fork.t t/60-plack.t 
t/61-plack-suite.t,$(shell echo t/*.t)); \
 
 %:
dh $@
@@ -15,3 +16,12 @@ override_dh_installexamples:
 override_dh_auto_install:
dh_auto_install
sed -i '1s|^#!.*perl|#!/usr/bin/perl|' $(TMP)/usr/*bin/*
+
+override_dh_auto_test:
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS) $(DEB_BUILD_PROFILES)))
+   if [ `nproc` -gt 1 ]; then \
+   dh_auto_test; \
+   else \
+   make -j5 test TEST_VERBOSE=1 TEST_FILES="$(TEST_FILES_1_CPU)"; \
+   fi
+endif

Bug#926820: RM: esperanza -- RoM; Affected by Qt4 Removal; Upstream dead;

[Boyuan Yang]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove

Dear FTP Masters,

As indicated in https://bugs.debian.org/926727, we agreed to remove esperanza
from Debian. This package is currently affected by Qt4 Removal and hasn't seen
any upstream activity for 10 years.

--
Regards,
Boyuan Yang


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

Bug#926819: RM: xtensor [experimental] -- ROM; NPOASR; FTBFS; orphaned

[ghisvail]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-scie...@lists.debian.org
Control: affects -1 xtensor

Please remove source package xtensor from experimental.

This package was removed from unstable in #926027 earlier.

Best regards,
Ghislain

Bug#926813: unblock: python-scipy/1.1.0-5

[Paul Gevers]

Hi Drew,

On 10-04-2019 21:22, Paul Gevers wrote:
> Thanks. I want to run a couple of tests, to see if it now appears stable
> (the first two passed).
> 
> I'll unblock when I don't find any failure.

The score isn't great (and not all results are in): 3/14 failure (2 in
unstable, 1 in testing so far). Can you please have a look?

Paul



signature.asc
Description: OpenPGP digital signature

Bug#926798: RFP: elpa-magit-forge -- Work with Git forges from the comfort of Magit

[Matteo F. Vescovi]

Hi!

Il mer 10 apr 2019, 16:54 Antoine Beaupre  ha scritto:

> Package: wnpp
> Severity: wishlist
>
> * Package name: elpa-magit-forge
>   Version : 0.1.0
>   Upstream Author : Jonas Bernoulli 
> * URL : https://github.com/magit/forge
> * License : GPL-3
>   Programming Lang: Elisp
>   Description : Work with Git forges from the comfort of Magit
>

This is really nice.
I'll try to give a look at it and hopefully package it.

Stay tuned. ;-)

mfv

Bug#914517: linux-image-4.19.0-4-amd64: System freezes with nomodeset set and boots in a loop without

[Ben Hutchings]

On Wed, 2019-04-10 at 17:26 +0200, Robert Pommrich wrote:
> Hi,
> 
> I really don't understand why the severity of this bug was lowered.
> Plus, this was the only action taken on this bug beside my actions.
[...]

The phrase "renders package unusable" means that the package is
unusable in general, or on a large proportion of Debian systems.

I don't believe that that is the case for this bug.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained
by stupidity.




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

Bug#925194: unblock: [pre-approval] qutebrowser/1.6.1-1 or qutebrowser/1.6.0-2?

[Axel Beckert]

Hi Paul,

Paul Gevers wrote:
> Please upload the 1.6.1-1 version in experimental to unstable an removed
> the moreinfo tag when it is build (I couldn't find logs on buildd.d.o,
> please do a source-only upload).

Will do. Thanks for the review!

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#926634: Delays opening dialogs, possibly related to defunct fc-list process

[Jeff]

Please apply these two patches, which should fix the UTF-8 characters in
the font names, and prevent the zombie process, and let me know if the
problem with the delay still occurs.

Regards

Jeff
diff --git a/lib/Gscan2pdf/Dialog/Save.pm b/lib/Gscan2pdf/Dialog/Save.pm
index 04fac57b..e4ee5def 100644
--- a/lib/Gscan2pdf/Dialog/Save.pm
+++ b/lib/Gscan2pdf/Dialog/Save.pm
@@ -11,6 +11,7 @@ use Gscan2pdf::EntryCompletion;
 use Gscan2pdf::Translation '__';# easier to extract strings with xgettext
 use Date::Calc qw(Today Today_and_Now);
 no if $] >= 5.018, warnings => 'experimental::smartmatch';
+use Encode;
 use Readonly;
 Readonly my $ENTRY_WIDTH_DATE => 10;
 Readonly my $ENTRY_WIDTH_DATETIME => 19;
@@ -809,6 +810,7 @@ sub add_pdf_options {
 my @fonts;
 my ( undef, $stdout ) =
   Gscan2pdf::Document::exec_command( ['fc-list : family style file'] );
+$stdout = Encode::decode_utf8($stdout);
 
 my $font = $self->get('pdf-font');
 for ( split /\n/sm, $stdout ) {
-- 
2.17.1

diff --git a/lib/Gscan2pdf/Document.pm b/lib/Gscan2pdf/Document.pm
index cc77f491..3e3e76ae 100644
--- a/lib/Gscan2pdf/Document.pm
+++ b/lib/Gscan2pdf/Document.pm
@@ -1980,7 +1980,9 @@ sub exec_command {
 close $fh or return $PROCESS_FAILED;
 }
 
-waitpid $ALL_PENDING_ZOMBIE_PROCESSES, WNOHANG;
+# Using 0 for flags, rather than WNOHANG to ensure that we wait for the
+# process to finish and not leave a zombie
+waitpid $ALL_PENDING_ZOMBIE_PROCESSES, 0;
 my $child_exit_status = $CHILD_ERROR >> $BITS_PER_BYTE;
 return $child_exit_status, slurp($reader), slurp($err);
 }
-- 
2.17.1



signature.asc
Description: OpenPGP digital signature

Bug#925934: RM: golang-gopkg-data-dog-go-sqlmock.v1/1.3.0-1

[Paul Gevers]

Hi rajudev,

On Sat, 30 Mar 2019 16:55:26 +0100 Paul Gevers  wrote:
> On 28-03-2019 21:36, rajudev wrote:
> > Shengjing pointed it out that golang-github-data-dog-go-sqlmock-dev can be
> > used for package which imports gopkg.in/DATA-DOG/go-sqlmock.v1
> > 
> > Hence I want this package to be removed.
> 
> Do you want it removed from Debian, or *only* from testing? In the
> former case, please clone this bug to the ftp.debian.org pseudo package.
> 
> However, it can't be removed yet, as there are multiple packages (build)
> depending on it, which need to be fixed first (see below). Did you
> coordinate this removal request with the maintainers of those packages?

Ping...

Paul

Bug#926798: RFP: elpa-magit-forge -- Work with Git forges from the comfort of Magit

[Vincent Bernat]

 ❦ 10 avril 2019 10:50 -04, Antoine Beaupre :

> I keep on coming back to this package. I think it's installable
> through MELPA but because of the poor connexion here, I'm having
> trouble testing it.

From my understanding, it doesn't work with the current version of
magit. See: .
-- 
Use the fundamental control flow constructs.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#909480: Feersum FTBFS

[Xavier]

Le 10/04/2019 à 20:55, Santiago Vila a écrit :
>> could you add my ssh-key and give me the server name?
> 
> Done. Please try:
> 
> ssh xavier@xxx
> sbuild -d buster feersum
> 
> [ You can also try "taskset --cpu-list 0 dpkg-buildpackage" in your
>   own machine, as I have the feeling that the failure is particularly
>   easy to reproduce on single-CPU machines ].
>   
> Thanks a lot.

Hello,

I can patch t/63-plack-apps.t (with a TODO block), then it succeeds on
your machine. But with a single CPU machine, 2 other tests fail and
can't be easily patched. I don't like the idea to disable them. Do you
think it's enough for now? Build is OK in debci machines.

Cheers,
Xavier

Bug#926818: s3ql: autopkgtest regression

[Paul Gevers]

Source: s3ql
Version: 3.1+dfsg-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of s3ql the autopkgtest of s3ql fails in testing
when that autopkgtest is run with the binary packages of s3ql from
unstable. It passes when run with only packages from testing. In tabular
form:
   passfail
s3ql   from testing3.1+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Without
further checking, it seems you are missing a (test) dependency.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? If needed, please
change the bug's severity.

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=s3ql

https://ci.debian.net/data/autopkgtest/testing/amd64/s/s3ql/2224241/log.gz
=== FAILURES
===
_ AdmTests.test_clear
__
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.ew3nmq2e/downtmp/build.SHF/src/tests/t4_adm.py",
line 85, in test_clear
self.mkfs()
  File
"/tmp/autopkgtest-lxc.ew3nmq2e/downtmp/build.SHF/src/tests/t4_adm.py",
line 54, in mkfs
self.assertEqual(proc.wait(), 0)
  File "/usr/lib/python3.7/unittest/case.py", line 839, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python3.7/unittest/case.py", line 832, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 1 != 0
- Captured stderr call
-
Traceback (most recent call last):
  File "/usr/bin/mkfs.s3ql", line 6, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3191, in 
@_call_aside
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3175, in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3204, in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
583, in _build_master
ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
900, in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
786, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'google-auth-oauthlib'
distribution was not found and is required by s3ql
=== 1 failed, 287 passed, 5 skipped in 59.15 seconds
===




signature.asc
Description: OpenPGP digital signature

Bug#926727: esperanza: Consider removing this software from Debian?

[Benjamin Drung]

Am Dienstag, den 09.04.2019, 12:32 -0400 schrieb Boyuan Yang:
> Package: esperanza
> Severity: important
> Version: 0.4.0+git20091017-5
> X-Debbugs-CC: bdr...@debian.org
> 
> Hi,
> 
> It looks like esperanza has no upstream activity for 10 years and that
> it is
> currently affected by Qt4 Removal in Debian [1]. Its popcon data is
> also
> declining. Is it okay if we remove it from Debian?

Yes. Feel free to go ahead to remove it. I am not using it any more.

If someone else still likes esperanza and has time, please go ahead and
port it to Qt5 and take over the Debian maintenance.

-- 
Benjamin Drung
Debian & Ubuntu Developer

Bug#922526: remove_stale.pl not removing old html files

[Holger Wansing]

Hi,

Laura Arjona Reina  wrote:
> The files related to DLA that were in subfolders under /english/security
> were recently moved to /english/lts/security. However, in
> www-master.debian.org, the previous generated html files are still present.
> 
> I believe those html files should have been removed by remove_stale.pl
> script which is run in the 8maintenance task in every often cron job:
> 
> https://salsa.debian.org/webmaster-team/webwml/blob/master/remove_stale.pl

I just noticed another occurrence of this problem:
https://www.debian.org/consultants/blunix.en.html (and its translations) are
still existing on the www servers, although that consultant has been removed
from the list in
https://salsa.debian.org/webmaster-team/webwml/commit/45314c40f2a57f17400d3cdc48487ffdca9e2ab2


@Laura:
could you remove the above pages from the servers, maybe?
(of course, feel free to leave them at their place, if you think they
could be useful for debugging purposes).


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#926817: unblock: publicsuffix/20190329.0756-1

[Daniel Kahn Gillmor]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Control: affects -1 src:publicsuffix

Please unblock package publicsuffix

The publicsuffix package contains up-to-date descriptions of the network
environment.  In addition to capturing the most recent state of the
DNS's public cutpoints, this update marks the correct level of debian
policy compliance (4.3.0) and moves to debhelper compat level 12 (no
changes to the generated tarball resulted from this shift in dh compat
level).

Buster should start off with an accurate state of the public network.

The debdiff is attached.

unblock publicsuffix/20190329.0756-1

Thanks for your work on Buster!

--dkg

diff --git publicsuffix-20190221.0923-1/debian/changelog publicsuffix-20190329.0756-1/debian/changelog
index 818926d..6a336fc 100644
--- publicsuffix-20190221.0923-1/debian/changelog
+++ publicsuffix-20190329.0756-1/debian/changelog
@@ -1,3 +1,9 @@
+publicsuffix (20190329.0756-1) unstable; urgency=medium
+
+  * new upstream version
+
+ -- Daniel Kahn Gillmor   Wed, 03 Apr 2019 22:49:31 -0400
+
 publicsuffix (20190221.0923-1) unstable; urgency=medium
 
   * new upstream version
diff --git publicsuffix-20190221.0923-1/debian/compat publicsuffix-20190329.0756-1/debian/compat
deleted file mode 100644
index b4de394..000
--- publicsuffix-20190221.0923-1/debian/compat
+++ /dev/null
@@ -1 +0,0 @@
-11
diff --git publicsuffix-20190221.0923-1/debian/control publicsuffix-20190329.0756-1/debian/control
index 683edff..f9f9dbe 100644
--- publicsuffix-20190221.0923-1/debian/control
+++ publicsuffix-20190329.0756-1/debian/control
@@ -3,10 +3,10 @@ Section: net
 Priority: optional
 Maintainer: Daniel Kahn Gillmor 
 Build-Depends:
- debhelper (>= 11~),
+ debhelper-compat (= 12),
  psl-make-dafsa,
  python3-minimal,
-Standards-Version: 4.2.1
+Standards-Version: 4.3.0
 Homepage: https://publicsuffix.org
 Vcs-Browser: https://salsa.debian.org/debian/publicsuffix
 Vcs-Git: https://salsa.debian.org/debian/publicsuffix.git
diff --git publicsuffix-20190221.0923-1/debian/upstream-changes.txt publicsuffix-20190329.0756-1/debian/upstream-changes.txt
index f575c27..b85f949 100644
--- publicsuffix-20190221.0923-1/debian/upstream-changes.txt
+++ publicsuffix-20190329.0756-1/debian/upstream-changes.txt
@@ -1,3 +1,102 @@
+commit 826d762a078ae21cd8bb95fa8f38ae84bb3948e7
+Author: Rishabh 
+Date:   Fri Mar 29 00:56:08 2019 -0700
+
+Add discourse.group for Civilized Discourse Construction Kit, Inc. (#768)
+
+At Discourse (Civilized Discourse Construction Kit, Inc.), we host free
+discussion forums for open source organizations under the `discourse.group` domain.
+https://blog.discourse.org/2018/11/free-hosting-for-open-source-v2/
+
+Therefore, each subdomain of discourse.group should be treated as a distinct domain.
+Website: https://www.discourse.org/
+
+As we host multiple forums under the discourse.group domain we'd like to add it to the PSL to:
+
+1. Ensure that each subdomain of discourse.group is treated as a distinct domain.
+2. Adding cookie security.
+
+commit 1def5910a0c1db384691adf55f769de191b4f2b7
+Author: Vincent Fiduccia 
+Date:   Fri Mar 29 00:53:18 2019 -0700
+
+Add on-rancher.cloud and on-rio.io (#779)
+
+We are adding a feature to automatically provide each user cluster with a ..on-rancher.cloud (and on-rio.io) DNS entry, so each user-id is a mutually untrusting third-party that should not be able to set cookies readable by each other. We also plan to provide Let's Encrypt wildcard certs for each user-id.
+
+commit 2b92a7f2c9c91f1141faea73d3ec2d429da18698
+Author: Boris Rybalkin 
+Date:   Fri Mar 29 07:49:12 2019 +
+
+Syncloud dynamic dns service (#727)
+
+Syncloud DDNS server (syncloud.it) hosts user's DNS records and also has its own site at syncloud.it.
+So In practice allthesebelong todifferent people:
+user1.syncloud.it
+user2.syncloud.it
+www.syncloud.it
+
+Also any incorrectly set cookie sharing across all three is not safe as different users can run anything under *.[user].syncloud.it
+
+commit e2e4e03ff8cba26140f973a8b64a24891d1789b9
+Author: Jennifer Herting 
+Date:   Thu Mar 28 13:38:33 2019 -0400
+
+Add git-pages.rit.edu (#690)
+
+Proper handling of the namespace by browsers.
+Prevention of cookie based attacks among others. Sites hosted under this namespace will be controlled by any number of students, staff, faculty, etc.
+
+commit a4ebab27463e90f80d3ab99220af90211299d7e1
+Author: Jake Riesterer 
+Date:   Thu Mar 28 12:36:52 2019 -0500
+
+Add workers.dev (#772)
+
+Cloudflare customers will given a subdomain of workers.dev to which they can deploy their serverless applications. Because subdomains are each controlled by different customers, they should be treated as separate domains for cookie purposes.
+
+commit f2f5143bc727d695f41195fe0300ff2133a79953
+Author: 

Bug#926813: unblock: python-scipy/1.1.0-5

[Paul Gevers]

Control: tags -1 moreinfo

On 10-04-2019 20:04, Drew Parsons wrote:
> debci tests were intermittently failing (Bug#919929), evidently due to
> running out of memory in the test system because of an excessive
> number of deprecation warnings emitted during the tests.
> 
> 1.1.0-4 applied a patch which eliminated the largest contribution to
> the warnings (warnings about the matrix API from numpy 1.16).
> 
> But the remaining warnings were sufficient to continue to trigger
> MemoryError failure in 2 tests, only in python2.  Tests in python3 all
> pass with scipy 1.1.0-4.
> 
> scipy 1.1.0-5 simply skips those 2 python2 tests. With that, 1.1.0-5
> now passes debci tests in testing and in unstable.

Thanks. I want to run a couple of tests, to see if it now appears stable
(the first two passed).

I'll unblock when I don't find any failure.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#926816: yubikey-manager FTBFS in some common situations

[Alex Chernyakhovsky]

Package: yubikey-manager
Version: 2.1.0

Dear maintainer,

The package yubikey-manager currently appears to fail to build, using
a stretch host with an sbuild chroot for sid-amd64:

yubikey-manager-2.1.0$ lsb_release  -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 9.8 (stretch)
Release:9.8
Codename:   stretch
yubikey-manager-2.1.0$ sbuild -A -c sid-amd64
dh clean --with python3 --buildsystem=pybuild
dh: Compatibility levels before 5 are no longer supported (level 1 requested)
debian/rules:6: recipe for target 'clean' failed
make: *** [clean] Error 25

If I then `echo 10 > debian/compat`, sbuild is able to proceed. The
package builds normally against a sid schroot.  If I try to use
debuild normally, the package FTBFS with
help2man -o debian/ykman.1 \
--no-info --version-string=2.1.0 \
--name 'YubiKey Manager' -- /tmp/tmp.3fY41n5LsH/bin/ykman
help2man: can't get `--help' info from /tmp/tmp.3fY41n5LsH/bin/ykman
Try `--no-discard-stderr' if option outputs to stderr
debian/rules:15: recipe for target 'override_dh_installman' failed

Interestingly enough, I cannot reproduce with a buster schroot; the
behavior seems to be dependent on debuild vs sbuild. Some further
investigation with with --no-discard-stderr shows a Python stacktrace
in python3-click, complaining about the locale. If we pass
--locale=C.UTF-8 to help2man, then everything builds properly, even
with debuild in this situation.

I've attached a debdiff that makes this package build more reliably.

Sincerely,
-Alex


yubikey-manager.debdiff
Description: Binary data

Bug#914470: gdc-8: ICE in gdc on call to defaulted alias template parameter that is a delegate literal

[Iain Buclaw]

On Wed, 10 Apr 2019 at 19:06, Witold Baryluk  wrote:
>
> Package: gdc-8
> Version: 8.3.0-6
> Followup-For: Bug #914470
>
> Still broken in 8.3.0-6
>

Looks like another example of PR d/89041, which was fixed in r269533
in gcc trunk.

-- 
Iain

Bug#926815: dh_auto_configure --buildsystem=cmake: emits wrong CMAKE_SYSTEM_PROCESSOR for mips64el during cross

[Helmut Grohne]

Source: debhelper
Version: 12.1.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:aom

aom fails to cross build from source for mips64el, because it does not
recognize the passed CMAKE_SYSTEM_PROCESSOR value. It turns out that on
mips64el, the CMAKE_SYSTEM_PROCESSOR should be "mips64" rather than
"mips64el". The attached patch extends the relevant mapping.

Helmut
diff --minimal -Nru debhelper-12.1.1/debian/changelog 
debhelper-12.1.1+nmu1/debian/changelog
--- debhelper-12.1.1/debian/changelog   2019-02-23 14:24:47.0 +0100
+++ debhelper-12.1.1+nmu1/debian/changelog  2019-04-10 14:33:59.0 
+0200
@@ -1,3 +1,11 @@
+debhelper (12.1.1+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Buildsystem/cmake: Fix CMAKE_SYSTEM_PROCESSOR for mips64el.
+(Closes: #-1)
+
+ -- Helmut Grohne   Wed, 10 Apr 2019 14:33:59 +0200
+
 debhelper (12.1.1) unstable; urgency=medium
 
   * dh_installinitramfs: Install hooks as executable rather than
diff --minimal -Nru debhelper-12.1.1/lib/Debian/Debhelper/Buildsystem/cmake.pm 
debhelper-12.1.1+nmu1/lib/Debian/Debhelper/Buildsystem/cmake.pm
--- debhelper-12.1.1/lib/Debian/Debhelper/Buildsystem/cmake.pm  2018-12-18 
20:49:57.0 +0100
+++ debhelper-12.1.1+nmu1/lib/Debian/Debhelper/Buildsystem/cmake.pm 
2019-04-10 14:33:56.0 +0200
@@ -27,6 +27,7 @@
 );
 
 my %GNU_CPU2SYSTEM_PROCESSOR = (
+   'mips64el'=> 'mips64',
'powerpc64le' => 'ppc64le',
 );
 

Bug#926814: deal.ii: Upgrade build dependency from liboce to libocct

[Kurt Kremitzki]

Source: deal.ii
Severity: normal

Dear Maintainer,

Currently deal.ii builds against liboce, OpenCASCADE Community Edition,
which is based on OpenCASCADE 6.9. Recently the mainline version of
OpenCASCADE, libocct (OpenCASCADE Technology) was reintroduced to
Debian. The current libocct version is 7.3, which contains many
significant improvements over 6.9.

I have created a PR on Salsa for this change:
https://salsa.debian.org/science-team/deal.ii/merge_requests/2


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

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

Bug#925194: unblock: [pre-approval] qutebrowser/1.6.1-1 or qutebrowser/1.6.0-2?

[Paul Gevers]

Control: tags -1 confirmed moreinfo
Control: retitle -1 unblock: qutebrowser/1.6.1-2

On Thu, 21 Mar 2019 03:54:36 +0100 Axel Beckert  wrote:



Please upload the 1.6.1-1 version in experimental to unstable an removed
the moreinfo tag when it is build (I couldn't find logs on buildd.d.o,
please do a source-only upload).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#916513: AVX/AVX2 added to inxi -Cx default short flag list

[contact smxi]

I talked to damentz of the Liquorix kernel project, who was able to supply a reason why AVX/AVX2 
should be included in the short -Cx output. Supplying a clear explanation of why something is being 
requested is generally a much better strategy than saying you want it because it's missing and 
should be included.


In general, when requesting a new feature, please do not bother the Debian maintainers with 
something that is not a bug.


I've also created a new cpu-flags.txt documentation on the inxi-perl branch (where all docs live) of 
the github inxi project pages.


This new document explains, more or less, why certain flags are used for the -Cx list vs the -f full 
flags list, as well as having links to cpu flag explations, source files, and a fairly current copy 
of a fairly full list.


This change will not enter Debian for a long time due to the recent freeze for next stable, so don't 
hold your breath. But it is in the pinxi version of inxi, from inxi-perl, and will be in next master 
inxi (which will be 3.0.34), whenever that comes out.


thanks, Harald

Bug#926700: cacti: CVE-2019-11025:

[Paul Gevers]

Hi Chris,

On 10-04-2019 16:51, Chris Lamb wrote:
> I've attached a patch that I intend to upload to jessie LTS. May I
> also prepare an update for stretch based on this?

I guess it doesn't matter for stable, but you have my blessing.

Paul

PS: I uploaded to sid yesterday, but I fear my key on the Debian keyring
was still marked as expired and the package was dropped.



signature.asc
Description: OpenPGP digital signature

Bug#926813: unblock: python-scipy/1.1.0-5

[Drew Parsons]

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

Please unblock package python-scipy

debci tests were intermittently failing (Bug#919929), evidently due to
running out of memory in the test system because of an excessive
number of deprecation warnings emitted during the tests.

1.1.0-4 applied a patch which eliminated the largest contribution to
the warnings (warnings about the matrix API from numpy 1.16).

But the remaining warnings were sufficient to continue to trigger
MemoryError failure in 2 tests, only in python2.  Tests in python3 all
pass with scipy 1.1.0-4.

scipy 1.1.0-5 simply skips those 2 python2 tests. With that, 1.1.0-5
now passes debci tests in testing and in unstable.

debdiff is:

$ debdiff python-scipy_1.1.0-4.dsc python-scipy_1.1.0-5.dsc
diff -Nru python-scipy-1.1.0/debian/changelog 
python-scipy-1.1.0/debian/changelog
--- python-scipy-1.1.0/debian/changelog 2019-03-14 14:12:00.0 +0800
+++ python-scipy-1.1.0/debian/changelog 2019-04-10 16:41:47.0 +0800
@@ -1,3 +1,11 @@
+python-scipy (1.1.0-5) unstable; urgency=medium
+
+  * Team upload.
+  * Skip sparsetools.TestInt32Overflow matvec tests on python2
+(MemoryError). Closes: #919929.
+
+ -- Drew Parsons   Wed, 10 Apr 2019 16:41:47 +0800
+
 python-scipy (1.1.0-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru python-scipy-1.1.0/debian/tests/python2 
python-scipy-1.1.0/debian/tests/python2
--- python-scipy-1.1.0/debian/tests/python2 2019-03-14 14:12:00.0 
+0800
+++ python-scipy-1.1.0/debian/tests/python2 2019-04-10 16:41:47.0 
+0800
@@ -27,6 +27,9 @@
 "sparse.tests.test_sparsetools.TestInt32Overflow.test_bsr_n_block[matmat]",
 "sparse.tests.test_sparsetools.TestInt32Overflow.test_bsr_n_block[matvecs]",
 "sparse.tests.test_sparsetools.TestInt32Overflow.test_bsr_n_block[transpose]",
+# postscriptum on Bug#919929
+"sparse.tests.test_sparsetools.TestInt32Overflow.test_matvecs",
+"sparse.tests.test_sparsetools.TestInt32Overflow.test_dia_matvec",
 ]
 
 junit = "$TMPDIR/junit.xml"


unblock python-scipy/1.1.0-5

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

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

Bug#902997: pulseaudio: every other time sound card does not get loaded

[Sergey]

Problem still presisit. pulseaudio version 12.2.

Bug#926812: curl: Doesn't support link local addresses in URL

[Witold Baryluk]

Package: curl
Version: 7.64.0-1
Severity: normal
Tags: ipv6

Dear Maintainer,


user@debian:~$ curl -v 'http://[fe80::da11:11ff:fe00:1234%25enp66s0]:80/'
* Expire in 0 ms for 6 (transfer 0x55732247e350)
* Closing connection -1
curl: (3) URL using bad/illegal format or missing URL
user@debian:~$ curl -v 'http://[fe80::da11:11ff:fe00:1234%enp66s0]:80/'
* Expire in 0 ms for 6 (transfer 0x55b1f6cf9350)
* Closing connection -1
curl: (3) URL using bad/illegal format or missing URL
user@debian:~$ 

Please see, https://tools.ietf.org/html/rfc6874 for details. This is a
short document.



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

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

Versions of packages curl depends on:
ii  libc6 2.28-8
ii  libcurl4  7.64.0-1
ii  zlib1g1:1.2.11.dfsg-1

curl recommends no packages.

curl suggests no packages.

-- no debconf information

Bug#926811: retroarch-assets: Missing icons when used with the retroarch 1.7.3 XMB interface

[Kraig Limbird]

Package: retroarch-assets
Version: 1.3.6+git20160731+dfsg1-2
Severity: minor

Dear Maintainer,

   * What led up to the situation?
Installing retroarch
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I had a previous retroarch configuration. So I removed
~/.config/retroarch and tried to launch retroarch again, but the missing icons
persisted.
   * What was the outcome of this action?
In retroarch's default XMB interface the top level icons for the
"Favorites" and "Netplay Rooms" menus are missing, only displaying black boxes.
   * What outcome did you expect instead?
All icons to be present in the XMB interface



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

Kernel: Linux 4.19.0-2-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages retroarch-assets depends on:
ii  fonts-roboto-hinted  2:0~20170802-3

retroarch-assets recommends no packages.

retroarch-assets suggests no packages.

-- no debconf information

Bug#916513: inxi -C -xxx doesn't show information about AVX, AVX2, etc

[contact smxi]

As I indicated, this is not a bug, it's a feature/enhancement request, and should be filed on inxi 
github page, not here. Further, nothing in the initial issue report indicated what you said in your 
last post here, in other words, it failed to really explain what why or how.


Bugs should be reserved for actual bugs, this is not a bug, and the issue 
should be closed.

It could well be that we can talk about a review of the defaults for -Cxx but this is not the place 
to do it.


Once you file the appropriate issue on inxi github, I'll take a look at it. Please include a full 
explanation of why a certain flag should or should not be listed in the default short list. But do 
not do that here, it's not the place to discuss specific enhancements or changes that are NOT bugs.


The default flag list comes from a long time ago, and if some should be added or dropped, that's 
just an ongoing update.


Please close this non bug since it is not a bug, just a desire to show something that may or may not 
be a good idea to show as default.


Thanks, Harald

Bug#926810: bugs.debian.org: Can't see both archived and unarchived bugs from web interface

[Witold Baryluk]

Package: bugs.debian.org
Severity: normal

For example:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;submitter=witold.baryluk%40gmail.com

after about a second or so, server returns a response:

curl -v output:

> GET /cgi-bin/pkgreport.cgi?archive=both;submitter=witold.baryluk%40gmail.com 
> HTTP/1.1
> Host: bugs.debian.org
> User-Agent: curl/7.64.0
> Accept: */*
> 
< HTTP/1.1 500 Internal Server Error
< Date: Wed, 10 Apr 2019 17:56:23 GMT
< Server: Apache
< X-Content-Type-Options: nosniff
< X-Frame-Options: sameorigin
< Referrer-Policy: no-referrer
< X-Xss-Protection: 1
< Strict-Transport-Security: max-age=15552000
< Public-Key-Pins: pin-sha256="efCzyZNcRDygSZ2Uw7twt3QmMgc3Fos/LAwZ+pgtx/M="; 
pin-sha256="ruqQmR+uAkOrIm05oGOSA0Y0jo3rBd/xQ/ieZ0sfI5g="; max-age=5184000
< Content-Length: 600
< Connection: close
< Content-Type: text/html; charset=iso-8859-1
< 


500 Internal Server Error

...



The value 'both' comes from the form on the website:


Unarchived
Archived
Archived and Unarchived


Thanks,
Witold






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

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

Bug#921266: linphone: Segfault and crash with "error 4 in libc-2.28.so" on password entry

[Bernhard Übelacker]

Control: reassign 921266 libbellesip0 1.6.3-4
Control: affects 921266 linphone
Control: tags 921266 + upstream patch


Hello Alf,

> Hope this helps you to locate the root cause.

I had a quick look at this line and found that upstream has
changed these lines already in their repository,
these commits [1] seem related.

There is also still an upstream issue [2] that might be
this problem, and even if at least changed in source,
is still open.
The links in [3] look like other reports on the
linphone-dev mailing list.
And further it looks like github is just a mirror - the
real upstream is maybe in [4] which leads to a bug that
is unfortunately not publicly visible.


But, without me having enough knowledge about libbellesip,
further suggestions would be needed from the package
maintainers, therefore reassigning to libbellesip0

Kind regards,
Bernhard


[1]

https://github.com/BelledonneCommunications/belle-sip/commit/7dd8397f0fd24bc3ddf04986488241b1acaf5a94

https://github.com/BelledonneCommunications/belle-sip/commit/3a6a6d677d4dce38f2498be4e10320d8106d76bf

https://github.com/BelledonneCommunications/belle-sip/commit/7191ee1df84707107a7fe4f89d33ebe075a0cb35

[2] https://github.com/BelledonneCommunications/linphone-desktop/issues/250

[3]
https://lists.gnu.org/archive/html/linphone-developers/2018-01/msg00018.html
https://lists.gnu.org/archive/html/linphone-developers/2018-02/msg4.html

[4]
https://gitlab.linphone.org/BC/public/belle-sip/merge_requests/14
https://bugs.linphone.org/view.php?id=5536


(gdb) list provider.c:1032,1050
1032
1033static void 
authorization_context_fill_from_auth(authorization_context_t* 
auth_context,belle_sip_header_www_authenticate_t* authenticate,belle_sip_uri_t 
*from_uri) {
1034
authorization_context_set_realm(auth_context,belle_sip_header_www_authenticate_get_realm(authenticate));
1035 >  if (auth_context->nonce && 
strcmp(belle_sip_header_www_authenticate_get_nonce(authenticate),auth_context->nonce)!=0)
 {
1036/*new nonce, resetting nounce_count*/
1037auth_context->nonce_count=0;
1038}

Bug#926809: strace: Allow dumping full detail of fstat and getdents/getdents64 syscalls

[Witold Baryluk]

Package: strace
Version: 4.26-0.2
Severity: normal

...
fstat(3, {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
getdents64(3, /* 35 entries */, 32768)  = 1104
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0x7), ...}) = 0
...


I tried fidling with -X verbose, -e verbose=%desc, and others, and it
still hides some details behind ... and in /* 35 entries */.


AFAIK, for things like select/poll/epoll_wait, that also return complex
variable length structures, strace shows them fully and reasonably nicely
(not sure if they do work with -y option, maybe...).

I want to be able to see detail of all getdents64 entries, including
entry order as they are returned by kernel, d_type, and the exact filename 
string
positions in memory, and the d_reclen, d_off values. 




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

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

Versions of packages strace depends on:
ii  libc6   2.28-8
ii  libunwind8  1.2.1-8

strace recommends no packages.

strace suggests no packages.

-- no debconf information

Bug#926795: di-netboot-assistant: Unable to install Debian Buster amd64 from d-i n-a at 2019-04-10 generated boot-file

[Andreas B. Mundt]

Control: reassign -1 debian-installer
Control: forcemerge 749991 -1


Hi Ralf,

many thanks for your report!

On Wed, Apr 10, 2019 at 04:06:43PM +0200, Ralf Moll wrote:

[…]
> the "Debian testing (amd64) image 20190410", generated by
> 
> di-netboot-assistant install stable testing
> 
> shows after answering a few installer querstions the following dialog:
> 
> "[!!] Download installer components
> 
> No kernel modules were found. This probably is due to a mismatch between
> the kernel used by this version of the Installer and the kernel version
> available in the archive.
> 
>[…]
>
> No matter what I select, the installer will fail.
> 
> Seems kernel and mirror are out of sycn...

Yes, exactly.  The issue is well-known, reported and discussed in bug
#749991 [1].  There is nothing di-netboot-assistant can do about it.

I recommend to try the daily image, for me that worked a few days ago
(201904040, but that seems not always to be the case [2]) or to wait
for an updated debian installer release.

Best regards,

  Andi



[1] https://bugs.debian.org/749991 
[2] https://bugs.debian.org/749991#181

Bug#926784: firehol: Please document usage of iptables-legacy

[Libor Klepáč]

Hi,
usage of -legacy variant can be patched in during build time.

Included patch tested by manual running (i don't have disk space to install 
tex) of: 
./autogen.sh && ./configure && make 

and checking generated ./sbin/install.config


Libor
Description: compatibility with iptables-legacy
Author: libor.kle...@bcom.cz
Origin: other
Last-Update: 2019-04-10
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
Index: firehol-3.1.6+ds/configure.ac
===
--- firehol-3.1.6+ds.orig/configure.ac
+++ firehol-3.1.6+ds/configure.ac
@@ -189,7 +189,7 @@ if test x"$enable_firehol_wizard" = xyes
 AX_NEED_PROG([IP], [ip], [])
 fi
 if test x"$enable_ipv6" = xyes; then
-AX_CHECK_PROG([IP6TABLES], [ip6tables], [])
+AX_CHECK_PROG([IP6TABLES], [ip6tables-legacy], [])
 fi
 if test x"$enable_ipv6" = xyes; then
 AX_CHECK_PROG([IP6TABLES_RESTORE], [ip6tables-restore], [])
@@ -200,7 +200,7 @@ fi
 AX_CHECK_PROG([IPRANGE], [iprange], [])
 AX_CHECK_PROG([IPSET], [ipset], [])
 if test x"$enable_ipv4" = xyes; then
-AX_CHECK_PROG([IPTABLES], [iptables], [])
+AX_CHECK_PROG([IPTABLES], [iptables-legacy], [])
 fi
 if test x"$enable_ipv4" = xyes; then
 AX_CHECK_PROG([IPTABLES_RESTORE], [iptables-restore], [])
debianization.patch
debianization-usrmerge-transition.patch
iptables-legacy.patch

Bug#924888: some links now removed

[Thomas Lange]

In commit
https://salsa.debian.org/webmaster-team/webwml/commit/00ee01a963076d499ecc72b4197a38bf69001e36
I removed some of the items in /misc
-- 
regards Thomas

Bug#923878: bash-completion: unrar completion doesn't suggest *.rar files immedietly, but requires options first (uneeded)

[Witold Baryluk]

Package: bash-completion
Version: 1:2.8-5
Followup-For: Bug #923878

Hi Gabriel,

I am using a free version of unrar, in package unrar-free in main repo of 
Debian:

unrar --help
Usage: unrar [OPTION...] ARCHIVE [FILE...] [DESTINATION]
Extract files from rar archives.

  -x, --extract  Extract files from archive (default)
  -t, --list List files in archive
  -f, --forceOverwrite files when extracting
  --extract-newerOnly extract newer files from the archive
  --extract-no-paths Don't create directories while extracting
  -p, --password Decrypt archive using a password
  -?, --help Give this help list
  --usageGive a short usage message
  -V, --version  Print program version

Report bugs to .
$

Note that OPTION part is optional, i.e. -x / --extract is default.



$ unrar-free --version
unrar 0.0.1
$ unrar --version
unrar 0.0.1
$ 

$ dpkg -l unrar-free
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description
+++-==-=--=
ii  unrar-free 1:0.0.1+cvs20140707-4 amd64Unarchiver for .rar files

$ dpkg -L unrar-free
/.
/usr
/usr/bin
/usr/bin/unrar-free
/usr/share
/usr/share/doc
/usr/share/doc/unrar-free
/usr/share/doc/unrar-free/README.Debian
/usr/share/doc/unrar-free/changelog.Debian.gz
/usr/share/doc/unrar-free/changelog.gz
/usr/share/doc/unrar-free/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/unrar-free
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/unrar-free.1.gz
/usr/share/unrar-free
/usr/share/unrar-free/misc
/usr/share/unrar-free/misc/tarar.pike


$ apt-cache show unrar-free
Package: unrar-free
Version: 1:0.0.1+cvs20140707-4
Installed-Size: 72
Maintainer: Ying-Chun Liu (PaulLiu) 
Architecture: amd64
Depends: libc6 (>= 2.15)
Recommends: unar
Suggests: pike8.0 | pike7.8 | pike7.6 | pike
Conflicts: unrar-nonfree (<< 1:3.7.8-1)
Description-en: Unarchiver for .rar files
 Unrar can extract files from .rar archives. Can't handle some archives in
 the RAR 3.0 format natively. Package "unar" can be used to extract those
 archives if installed.
Description-md5: ec1032a402cf223268dffa022fd9536b
Homepage: https://gna.org/projects/unrar/
Tag: implemented-in::c, interface::commandline, role::program,
 scope::utility, use::compressing, works-with::archive
Section: utils
Priority: optional
Filename: pool/main/u/unrar-free/unrar-free_0.0.1+cvs20140707-4_amd64.deb
Size: 25132
MD5sum: 9d31bb0d4d714a8e2fb25bc01fd25f6f
SHA256: 8b2113d348e065ce71cffab1e15d86102d242efd082d692a9818914d9f8ca36b

$

It always served me well, and does support solid and multi file archives,
and essentially never failed me.

The one you tested is from non-free repo AFAIK.




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

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

-- no debconf information

Bug#926707: cups: please do not generate files under /etc but use /var/lib for that (etckeeper woes)

[Thorsten Glaser]

# mention etckeeper in the title (easier found thus)
retitle 549673 cups: constantly modify configuration files in /etc (bad for 
etckeeper)
retitle 926707 cups-browsed: generates PPDs in /etc, not /var/lib (bad for 
etckeeper)
# merging, as these are effectively the same issue
unblock 926707 by 549673
tags 549673 - fixed-upstream
severity 926707 minor
forwarded 926707 https://github.com/apple/cups/issues/3067
forcemerge 926707 549673
thanks

Hi OdyX,

>While I agree that the whole /etc/cups directory _COULD_ be moved to
>/var/lib/cups , this is not done easily, brings only little benefit, and woudl
>break a lot of assumptions in various parts of the stack. See as mere example
>the search for /etc/cups/ppd ; 290 occurences:

thanks for this explanation.

>I really have not changed my mind about this: diverging away from upstream
>CUPS and their 20+ years of existance is really not worth the costs.
>
>Hereby marking this as upstream, and wontfix; sorry.

I agree; thanks for leaving this open, so it can be found easier
by others encountering the same problem.

Maybe this is something that can be fixed on the etckeeper side
(ignoring those generated PPDs and the .O (IIRC?) files).

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#888500: libnss-lwres: Recommends lwresd, yet this package do not exist (it is virtual). Maybe recommend (or depend) on bind9?

[Witold Baryluk]

Package: libnss-lwres
Followup-For: Bug #888500

ping?

this is still an issue with libnss-lwres 0.93-7+b4

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

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

Versions of packages libnss-lwres depends on:
ii  libc62.28-8
ii  liblwres161  1:9.11.5.P1+dfsg-1

Versions of packages libnss-lwres recommends:
pn  lwresd  

libnss-lwres suggests no packages.

Bug#916513: inxi -C -xxx doesn't show information about AVX, AVX2, etc

[Witold Baryluk]

Package: inxi
Version: 3.0.32-1-1
Followup-For: Bug #916513

I am fully aware of -f to show all flags.

The point of my bug report was to put AVX and AVX2 specifically to be
printed by default just like few other flags are whitelisted to be shown
when using -C. My request wasnt about putting all flags, just the major
ones that are similar to SSEx ones.

Cheers,
Witold


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

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

Versions of packages inxi depends on:
ii  pciutils  1:3.5.2-1
ii  perl  5.28.1-4
ii  procps2:3.3.15-2

Versions of packages inxi recommends:
ii  dmidecode  3.2-1
ii  dnsutils   1:9.11.5.P1+dfsg-1
ii  file   1:5.35-2
ii  hddtemp0.3-beta15-53
ii  iproute2   4.20.0-2
ii  kmod   25-2
ii  lm-sensors 1:3.5.0-3
ii  mesa-utils 8.4.0-1+b1
ii  net-tools  1.60+git20180626.aebd88e-1
ii  sudo   1.8.27-1
ii  tree   1.8.0-1
ii  usbutils   1:010-2
ii  x11-utils  7.7+4
ii  x11-xserver-utils  7.7+8

Versions of packages inxi suggests:
ii  curl7.64.0-1
ii  libcpanel-json-xs-perl  4.08-1
ii  libjson-xs-perl 3.040-1+b1
ii  libxml-dumper-perl  0.81-1.2
ii  wget1.20.1-1

-- no debconf information

Bug#914470: gdc-8: ICE in gdc on call to defaulted alias template parameter that is a delegate literal

[Witold Baryluk]

Package: gdc-8
Version: 8.3.0-6
Followup-For: Bug #914470

Still broken in 8.3.0-6



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

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

Versions of packages gdc-8 depends on:
ii  g++-8 8.3.0-6
ii  gcc-8-base8.3.0-6
ii  libc6 2.28-8
ii  libgmp10  2:6.1.2+dfsg-4
ii  libgphobos-8-dev  8.3.0-6
ii  libisl19  0.20-2
ii  libmpc3   1.1.0-1
ii  libmpfr6  4.0.2-1
ii  zlib1g1:1.2.11.dfsg-1

gdc-8 recommends no packages.

gdc-8 suggests no packages.

-- no debconf information

Bug#926808: fping: --timestamp should show missing responses too per host and line

[Witold Baryluk]

Package: fping
Version: 4.2-1
Severity: wishlist

In --loop or --count modes for example:

# fping --timestamp  -6 -A -d --count 10 2a00:1450:400a:802::3

2a00:1450:400a:802::3 (2a00:1450:400a:802::3) : xmt/rcv/%loss = 10/0/100%
#

Adding -u or -a doesn't help. Adding -u -a (both), is not supported.

I would expect something more useful, i.e.:

# fping --timestamp  -6 -A -d --count 10 2a00:1450:400a:802::3
[1554914998.643838] 2a00:1450:400a:802::3 (2a00:1450:400a:802::3) : [0], 64 
bytes, timeout, 1000ms (nan avg, 100% loss)
[1554914999.645784] 2a00:1450:400a:802::3 (2a00:1450:400a:802::3) : [1], 64 
bytes, timeout, 1000ms (nan avg, 100% loss)
[1554915000.646059] 2a00:1450:400a:802::3 (2a00:1450:400a:802::3) : [2], 64 
bytes, timeout, 1000ms (nan avg, 100% loss)
[1554915001.647150] 2a00:1450:400a:802::3 (2a00:1450:400a:802::3) : [3], 64 
bytes, timeout, 1000ms (nan avg, 100% loss)
[1554915002.647459] 2a00:1450:400a:802::3 (2a00:1450:400a:802::3) : [4], 64 
bytes, timeout, 1000ms (nan avg, 100% loss)
[1554915003.648428] 2a00:1450:400a:802::3 (2a00:1450:400a:802::3) : [5], 64 
bytes, timeout, 1000ms (nan avg, 100% loss)
[1554915004.649674] 2a00:1450:400a:802::3 (2a00:1450:400a:802::3) : [6], 64 
bytes, timeout, 1000ms (nan avg, 100% loss)
[1554915005.650596] 2a00:1450:400a:802::3 (2a00:1450:400a:802::3) : [7], 64 
bytes, timeout, 1000ms (nan avg, 100% loss)
[1554915006.651561] 2a00:1450:400a:802::3 (2a00:1450:400a:802::3) : [8], 64 
bytes, timeout, 1000ms (nan avg, 100% loss)
[1554915007.652256] 2a00:1450:400a:802::3 (2a00:1450:400a:802::3) : [9], 64 
bytes, timeout, 1000ms (nan avg, 100% loss)

2a00:1450:400a:802::3 (2a00:1450:400a:802::3) : xmt/rcv/%loss = 10/0/100%
#

or something like this.

The main benefit is when the packet loss is interminent, as the output is
then easier to be ingested into external monitoring systems.

Cheers,
Witold



-- Package-specific info:
-rwxr-xr-x 1 root root 48032 Feb 19 22:27 /usr/bin/fping
lrwxrwxrwx 1 root root 5 Feb 19 22:27 /usr/bin/fping6 -> fping

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

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

Versions of packages fping depends on:
ii  libc62.28-8
ii  libcap2-bin  1:2.25-2
ii  netbase  5.5

fping recommends no packages.

fping suggests no packages.

-- no debconf information

Bug#926807: RFP: signal-cli -- A command-line and D-BUS interface for Signal Messenger

[Jacob Adams]

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

* Package name: signal-cli
  Version : 0.6.2
  Upstream Author : AsamK
* URL : https://github.com/AsamK/signal-cli
* License : GPL-3
  Programming Lang: Java
  Description : A command-line and D-BUS interface for Signal Messenger

signal-cli is a command-line interface for libsignal-service-java.
It supports registering, verifying, sending and receiving messages.
For registering you need a phone number where you can receive SMS or incoming 
calls.
signal-cli is primarily intended to be used on servers to notify admins
of important events.
For this use-case, it has a D-BUS interface, that can be used to send messages
from any programming language that has D-BUS bindings.



Packaging this would also require:
 * Updating libbcprov-java to 1.61
 * Updating libargparse4j-java to 0.8.1
 * Packaging https://github.com/Turasa/libsignal-service-java/

The last item may be controversial, as it is a fork, but it appears to
be kept up to date and it allows signal-cli to be a slave device, which
is quite a useful feature.

That would require:
 * Packaging libphonenumber8-java:
https://github.com/googlei18n/libphonenumber/
 * Packaging https://github.com/signalapp/libsignal-metadata-java
 (Technically also requires threetenbp, but with Java SE 8 and newer it
can be replaced with data and time support from Java)

I may change this to an ITP later if I have time, but for the
foreseeable future I do not.



signature.asc
Description: OpenPGP digital signature

Bug#926806: fping: Typoe in fping manpage, -s, --src should be -s, --stats

[Witold Baryluk]

Package: fping
Version: 4.2-1
Severity: minor


   -s, --src
Print cumulative statistics upon exit.

   -S, --src=addr
Set source address.


first one should be -s, --src, to be in order with --help :

Output options:
...
   -s, --statsprint final stats
...


Cheers,
Witold


-- Package-specific info:
-rwxr-xr-x 1 root root 48032 Feb 19 22:27 /usr/bin/fping
lrwxrwxrwx 1 root root 5 Feb 19 22:27 /usr/bin/fping6 -> fping

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

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

Versions of packages fping depends on:
ii  libc62.28-8
ii  libcap2-bin  1:2.25-2
ii  netbase  5.5

fping recommends no packages.

fping suggests no packages.

-- no debconf information

Bug#926805: inetutils-ping: Add option to print timestamp of send and receive packets on each line of output

[Witold Baryluk]

Package: inetutils-ping
Version: 2:1.9.4-7
Severity: wishlist

It would be amazing useful, especially for plotting data and ingesting
into various monitoring systems to have an option (--time? --log?
--verbose?) that makes each "response/lack of response" lines have some
timestamp available, in machine readable form. Sticking to Unix timestamp
(microsecond resolution), or using LC_TIME or strftime format argument to
--time:

I.e.

# ping6 --numeric --interval=1000 --count=3 --time google.com
PING google.com (2a00:1450:400a:802::200e): 56 data bytes
64 bytes from 2a00:1450:400a:802::200e: icmp_seq=0 ttl=55 time=1.230 ms 
sent=1554913612.123456 received=1554913612.124676
64 bytes from 2a00:1450:400a:802::200e: icmp_seq=1 ttl=55 time=1.294 ms 
sent=1554913613.13 received=1554913613.131294
64 bytes from 2a00:1450:400a:802::200e: icmp_seq=2 ttl=55 time=1.639 ms 
sent=1554913614.141000 received=1554913614.142639
--- google.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.230/1.388/1.639/0.180 ms
#

timestamps could be seconds, or miliseconds to be consistent with time
and --interval options, as well with ICMP_TIMESTAMP feature (which is
orthogonal to this wishlist).

(using comma vs dot, depending on LC_ALL etc is optional, but would be
consistent with its use in time= and in round-trip min/avg/max/... stats)

The main reasoning is, that on Linux, doing pings using ICMP requires
super user to open raw socket, so if integreating into various systems,
one either need to install setuid binaries (which is a bit fragile and
possibly less secure) or use existing ping/ping6 tool installed.

>From normal user:

...
socket(AF_INET, SOCK_RAW, IPPROTO_ICMP) = -1 EPERM (Operation not permitted)
socket(AF_INET, SOCK_DGRAM, IPPROTO_ICMP) = -1 EACCES (Permission denied)
write(2, "ping: Lacking privilege for icmp"..., 41ping: Lacking privilege for 
icmp socket.
...

On Linux, it mighte be possible to access functionality using
CAP_NET_RAW, but 1) it again requires a setup, 2) allows too much than
only required functionality. On other kernels it could be even worse.

Adding timestamps would help a lot of this problem, as one could have
ping running continously for various targets, and just ingest its output
using pipes, named fifo or simply files for example. This alone would for
example help with constantly starting processes (currently the method
would be to send ~5 packets ever 100ms and then quit the ping), to have
approximate time and required stats. However this will lead to a lot of
forks, other overheads, and inprecise timeing.

Currently ping also do not report missing responses, even with --timeout
set manually, which is also unfortunate.

fping kind of provides similar functionality, i.e.

# fping --timestamp --loop -6 -A -d google.com
[1554914467.234919] zrh04s14-in-x0e.1e100.net (2a00:1450:400a:802::200e) : [0], 
64 bytes, 1.17 ms (1.17 avg, 0% loss)
[1554914468.235169] zrh04s14-in-x0e.1e100.net (2a00:1450:400a:802::200e) : [1], 
64 bytes, 1.35 ms (1.26 avg, 0% loss)
[1554914469.236207] zrh04s14-in-x0e.1e100.net (2a00:1450:400a:802::200e) : [2], 
64 bytes, 1.38 ms (1.30 avg, 0% loss)
[1554914470.237207] zrh04s14-in-x0e.1e100.net (2a00:1450:400a:802::200e) : [3], 
64 bytes, 1.35 ms (1.31 avg, 0% loss)

zrh04s14-in-x0e.1e100.net (2a00:1450:400a:802::200e) : xmt/rcv/%loss = 4/4/0%, 
min/avg/max = 1.17/1.31/1.38
#

but for non-root users persepective, ping is almost always installed, and
fping isn't. fping doesn't print missing responses either:

# fping --timestamp  -6 -A -d --count 10 2a00:1450:400a:802::3

2a00:1450:400a:802::3 (2a00:1450:400a:802::3) : xmt/rcv/%loss = 10/0/100%
#



Cheers,
Witold

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

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

Versions of packages inetutils-ping depends on:
ii  libc6 2.28-8
ii  libidn11  1.33-2.2
ii  netbase   5.5

inetutils-ping recommends no packages.

inetutils-ping suggests no packages.

-- no debconf information

Bug#923980: claws-mail-gdata-plugin: gdata plugin crashes after update to 3.17.3-1

[Christian Beier]

Hi Ricardo,

I just upgraded to 3.17.3-2, but unfortunately still get the segfault:

---
Thread 1 "claws-mail" received signal SIGSEGV, Segmentation fault.
__strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120
120 ../sysdeps/x86_64/multiarch/../strlen.S: Datei oder Verzeichnis nicht 
gefunden.
(gdb) bt
#0  0x76018436 in __strlen_sse2 () at 
../sysdeps/x86_64/multiarch/../strlen.S:120
#1  0x75fd1bef in _IO_vfprintf_internal (s=s@entry=0x7fffb9e0, 
format=format@entry=0x7155050f "GData-Plugin: Erneuern der Autorisierung 
erfolgreich: %s\n", ap=ap@entry=0x7fffbba8)
at vfprintf.c:1638
#2  0x760885a9 in ___vsnprintf_chk
(s=0x7fffbbcb "GData-Plugin: Erneuern der Autorisierung erfolgreich: 
\024\221", maxlen=, flags=1, slen=, 
format=0x7155050f "GData-Plugin: Erneuern der Autorisierung erfolgreich: 
%s\n", args=0x7fffbba8) at vsnprintf_chk.c:63
#3  0x005fe2c4 in log_message ()
#4  0x7fffee549025 in  () at 
/usr/lib/x86_64-linux-gnu/claws-mail/plugins/gdata.so
#5  0x76d49719 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x76d49759 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#7  0x76b5bdd8 in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x76b5c1c8 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x76b5c4c2 in g_main_loop_run () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x77c788e7 in gtk_main () at 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#11 0x00449cc8 in main ()
(gdb) q
A debugging session is active.

Inferior 1 [process 11179] will be killed.
---

I checked with 3.17.3-2's source package and there is a de.gmo file in there 
which still contains the %s. Might this be the reason?


Cheers,
-- 
Christian Beier, CTO.

W   https://shoutrlabs.com
E   c...@shoutrlabs.com
L   https://www.linkedin.com/in/christianbeier
P   +49 (0)30-555794563
T   https://twitter.com/shoutrlabs

what is, is; what is not is possible.

shoutr labs UG (haftungsbeschränkt), 
Wolfener Straße 32-34, Haus K, CleanTech Innovation Center, 12681 Berlin
HRB 154532 B, AG Charlottenburg
Managing directors: Christian Beier, Sebastian Winkler



pgpU7IBQjf1CC.pgp
Description: Digitale Signatur von OpenPGP

Bug#926804: ITP: golang-github-x86kernel-htmlcolor -- HTML syntax highlighter for Go

[Dawid Dziurla]

Package: wnpp
Severity: wishlist
Owner: Dawid Dziurla 

* Package name: golang-github-x86kernel-htmlcolor
  Version : 0.0~git20170417.cf1d377-1
  Upstream Author : JaeYoung Mun
* URL : https://github.com/x86kernel/htmlcolor
* License : Not specified
  Programming Lang: Go
  Description : HTML syntax highlighter for Go

 Pretty print HTML source code with syntax highlighting in Go.

This package is an additional dependency of newer version of package "wuzz".

Bug#926803: libfm-qt will not react to file changes in filesystems with no monitoring

[Alf Gaida]

Package: libfm-qt6
Version: 0.14.2~16-g2fc359a-2
Severity: important
Tags: upstream

This is esp. painful for smb and similar - not refreshing remote file systems
after file operations in pcmanfm-qt and other dependend applications make a
normal workflow impossible.

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

Kernel: Linux 5.0.7-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libfm-qt6 depends on:
ii  libc6 2.28-8
ii  libexif12 0.6.21-5.1
ii  libglib2.0-0  2.58.3-1
ii  libglib2.0-bin2.58.3-1
ii  libmenu-cache31.1.1~2-g583c190-1
ii  libqt5core5a [qtbase-abi-5-11-3]  5.11.3+dfsg1-1
ii  libqt5gui55.11.3+dfsg1-1
ii  libqt5widgets55.11.3+dfsg1-1
ii  libqt5x11extras5  5.11.3-2
ii  libstdc++68.3.0-6
ii  libxcb1   1.13.1-2
ii  shared-mime-info  1.10-1

Versions of packages libfm-qt6 recommends:
ii  libfm-qt-l10n  0.14.2~16-g2fc359a-2

libfm-qt6 suggests no packages.

-- no debconf information

Bug#909480: Feersum FTBFS

[Xavier]

Le 10/04/2019 à 15:38, Santiago Vila a écrit :
> affects 909480 src:feersum
> thanks
> 
> Hello Xavier.
> 
> I almost report this again because we forgot to add the affects. Fixed that 
> now.
> 
> The failure rate in my autobuilders for feersum is still extremely high.
> 
> I could understand that you don't want to add a workaround in feersum
> if the package to blame is another one, but OTOH if a package A makes
> package B to FTBFS, then package A should have a serious bug.
> 
> Therefore I don't think it is ok that both A) This bug is still "normal"
> and B) Test suite in feersum keeps failing a lot.
> 
> (I already have your public ssh key, please tell me if you still need
> a test machine).
> 
> Thanks.

Hello,

thanks, I'll test this evening (and will give you the relevant ssh key
when back at home).

Cheers,
Xavier

Bug#856393: lxcfs: error message from the kernel: cgroup: new mount options do not match the existing superblock, will be ignored

[Laurent Bonnaud]

On 12/9/18 10:08 PM, Pierre-Elliott Bécue wrote:

> I'm sorry nobody gave you any feedback on your bug.

No problem, and sorry to answer after such a long time :>.

> I've made an upload of lxc 3 in unstable. Could you run some tests with it
> and tell me if you get the same issue?

Yes.  With this package version:

Package: lxcfs
Version: 3.0.3-2

the kernel still outputs:

[2008277.482552] new mount options do not match the existing superblock, will 
be ignored

Thanks,

-- 
Laurent.

Bug#926801: src:wpa: multiples vulnerabilities in SAE and EAP-pwd code in wpa

[Yves-Alexis Perez]

Package: src:wpa
Severity: grave
Tags: security
Justification: user security hole

Hi,

multiple vulnerabilities were discovered in wpa:

CVE-2019-9494 [cache attack against SAE]
CVE-2019-9495 [cache attack against EAP-pwd]
CVE-2019-9496 [SAE confirm missing state validation in hostapd/AP]
CVE-2019-9497 [EAP-pwd server not checking for reflection attack]
CVE-2019-9498 [EAP-pwd server missing commit validation for scalar/element]
CVE-2019-9499 [EAP-pwd peer missing commit validation for scalar/element]

When you fix them, please include references to those CVE in the
changelog.

Regards,
-- 
Yves-Alexis


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

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

Bug#926802: ipywidgets: FTBFS (TypeError: path.scope.getBindings(...).hasOwnProperty is not a function)

[Santiago Vila]

Package: src:ipywidgets
Version: 6.0.0-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.7 setup.py config 
running config
dh_auto_configure -- -d ./widgetsnbextension
I: pybuild base:217: python2.7 setup.py config 
INFO:root:setup.py entered
INFO:root:$PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
running config
I: pybuild base:217: python3.7 setup.py config 
INFO:root:setup.py entered
INFO:root:$PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
running config
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make -C debian -f fakewebpack.mk all
make[2]: Entering directory '/<>/debian'
/usr/bin/make -f "fakewebpack-prep-unpacked.mk" all
make[3]: Entering directory '/<>/debian'
cd "fakewebpack-unpacked/phosphor/" && tsc --moduleResolution Classic --project 
src
mkdir -p "fakewebpack-unpacked/phosphor/styles/" && NODE_PATH=../.. 
fakewebpack-helpers/css-loader-pack.py < 
"fakewebpack-unpacked/phosphor/styles/base.css.real" > 
"fakewebpack-unpacked/phosphor/styles/base.css"
mkdir -p "fakewebpack-unpacked/phosphor/styles/" && m4 -DNODE_PATH=../.. 
-DCSS_INPUT=./base.css "fakewebpack-helpers/style-loader.js.m4" > 
"fakewebpack-unpacked/phosphor/styles/base.css?f74d"
printf "module.exports = $(cat 
"fakewebpack-unpacked/jupyter-js-widgets/package.json.real");" > 
"fakewebpack-unpacked/jupyter-js-widgets/package.json"
cd "fakewebpack-unpacked/jupyter-js-widgets/" && tsc --moduleResolution Classic 
--project src
mkdir -p "fakewebpack-unpacked/jupyter-js-widgets/css/"
cd ../jupyter-js-widgets/css && cat widgets.css | \
sed -e '/@import ".\/labvariables.css"/{r ./labvariables.css'"${NLD}"'}' \
-e '/@import ".\/widgets-base.css"/{r ./widgets-base.css'"${NLD}"'}' | \
sed -e '/@import ".\/materialcolors.css"/{r ./materialcolors.css'"${NLD}"'}' > 
/<>/debian/"fakewebpack-unpacked/jupyter-js-widgets/css/widgets.css.real"
mkdir -p "fakewebpack-unpacked/jupyter-js-widgets/css/" && NODE_PATH=../.. 
fakewebpack-helpers/css-loader-pack.py < 
"fakewebpack-unpacked/jupyter-js-widgets/css/widgets.css.real" > 
"fakewebpack-unpacked/jupyter-js-widgets/css/widgets.css"
mkdir -p "fakewebpack-unpacked/jupyter-js-widgets/css/" && m4 -DNODE_PATH=../.. 
-DCSS_INPUT=./widgets.css "fakewebpack-helpers/style-loader.js.m4" > 
"fakewebpack-unpacked/jupyter-js-widgets/css/widgets.css?7dc3"
mkdir -p "fakewebpack-unpacked/widgetsnbextension/webpack/ ./" && m4 
-DWEBPACK_PUBLIC_PATH= "fakewebpack-helpers/webpack-bootstrap.js.m4" > 
"fakewebpack-unpacked/widgetsnbextension/webpack/bootstrap e65abc6196a7e23c9fcf"
mkdir -p "fakewebpack-unpacked/widgetsnbextension/css/" && 
NODE_PATH=../node_modules fakewebpack-helpers/css-loader-pack.py < 
"fakewebpack-unpacked/widgetsnbextension/css/outputarea.css.real" > 
"fakewebpack-unpacked/widgetsnbextension/css/outputarea.css"
mkdir -p "fakewebpack-unpacked/widgetsnbextension/css/" && m4 
-DNODE_PATH=../node_modules -DCSS_INPUT=./outputarea.css 
"fakewebpack-helpers/style-loader.js.m4" > 
"fakewebpack-unpacked/widgetsnbextension/css/outputarea.css?73c5"
printf "module.exports = $(cat 
"fakewebpack-unpacked/widgetsnbextension/package.json.real");" > 
"fakewebpack-unpacked/widgetsnbextension/package.json"
mkdir -p fakewebpack
touch "fakewebpack/prep.stamp"
make[3]: Leaving directory '/<>/debian'
touch fakewebpack/widgetsnbextension-unpacked.stamp
rm -rf "fakewebpack/widgetsnbextension" && mkdir -p 
"fakewebpack/widgetsnbextension" && ./fakewebpack-generate.py 
fakewebpack-meta/widgetsnbextension.files 
fakewebpack-meta/widgetsnbextension.modules 
fakewebpack-unpacked/widgetsnbextension/ True > 
"fakewebpack/widgetsnbextension/extension.js" && touch 
"fakewebpack/widgetsnbextension.stamp"
/<>/debian/fakewebpack-postprocess.js:130
if (!path.scope.getBindings().hasOwnProperty(path.node.name)) {
  ^

TypeError: path.scope.getBindings(...).hasOwnProperty is not a function
at Context.visitIdentifier 
(/<>/debian/fakewebpack-postprocess.js:130:47)
at Context.invokeVisitorMethod 
(/usr/lib/nodejs/ast-types/lib/path-visitor.js:344:49)
at Visitor.PVp.visitWithoutReset 
(/usr/lib/nodejs/ast-types/lib/path-visitor.js:196:32)
at visitChildren (/usr/lib/nodejs/ast-types/lib/path-visitor.js:246:25)
at Visitor.PVp.visitWithoutReset 
(/usr/lib/nodejs/ast-types/lib/path-visitor.js:204:20)
at 

Bug#884128: libical: don't release with buster

[Sandro Knauß]

Hey,

> That's basically kdepimlibs, as cyrus-imapd is not in testing and kmymoney 
is already fixed in experimental and just needs an upload to sid.
 
> kdepimlibs may not be easy though as disabling libical will probably disable 
some libs that may be used by rdeps. Someone needs to look at that. I have 
just opened a bug for it and made it block this one.

kdepimlibs has migrated to Buster the Transitions' view looks like nothing is 
blocking us anymore from removing libical:
https://release.debian.org/transitions/html/libical.html

hefee 



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

Bug#926707: cups: please do not generate files under /etc but use /var/lib for that (etckeeper woes)

[Didier 'OdyX' Raboud]

Control: block -1 549673
Control: tags -1 +upstream +wontfix
Control: retitle -1 cups-browsed: generates PPDs in /etc, not /var/lib

Le mardi, 9 avril 2019, 13.32:27 h CEST Thorsten Glaser a écrit :
> With etckeeper on a laptop that often is taken around to different networks,
> I see lines like these on apt-get --purge dist-upgrade all the time:
> 
> [master 48dee15] saving uncommitted changes in /etc prior to apt run
> […]
>  create mode 100644
> cups/ppd/pr_bn_1og_Brother_HL_L8250CDN_Laser_Colour_Duplex_172_2.ppd […]
> 
> So, these files are autogenerated and not created then changed by the
> local admin. (They are also automatically deleted). There’s a place for
> such files in the filesystem standard, and it’s /var/lib not /etc.
> 
> Please move this stuff out of /etc, TYVM.

Unfortunately, this is a long-running issue with CUPS and the CUPS stack, and 
is tracked by https://bugs.debian.org/549673 and https://github.com/apple/
cups/issues/3067

While I agree that the whole /etc/cups directory _COULD_ be moved to
/var/lib/cups , this is not done easily, brings only little benefit, and woudl 
break a lot of assumptions in various parts of the stack. See as mere example 
the search for /etc/cups/ppd ; 290 occurences:

https://codesearch.debian.net/search?q=%2Fetc%2Fcups%2Fppd

I really have not changed my mind about this: diverging away from upstream 
CUPS and their 20+ years of existance is really not worth the costs.

Hereby marking this as upstream, and wontfix; sorry.

Cheers,
OdyX

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

Bug#914517: linux-image-4.19.0-4-amd64: System freezes with nomodeset set and boots in a loop without

[Robert Pommrich]

Hi,

I really don't understand why the severity of this bug was lowered.
Plus, this was the only action taken on this bug beside my actions.

The system doesn't start completely, instead it is caught in a boot
loop, which renders the system unusable.

I tried every new kernel that hit backports and the problem existed on
and on. Even worse, booting with nomodeset freezes the system.

Please, take a further look on this bug. I suggest raising the severity
as the only workaround doesn't work anymore.

Thank you.
Robert

Bug#926800: unblock: cups-filters/1.21.6-5

[Didier 'OdyX' Raboud]

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

Please unblock package cups-filters 1.21.6-5

It fixes a severity: important bug (#926576) in cups-filters; which is a
regression in the ghostscript support triggered by the version of Ghostscript
that will be shipped in Buster (9.27), quoting the upstream developer
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926576#20):

> The old call used the undocumented internal "pdfdict" of Ghostscript 
> which from Ghostscript 9.27 on is not accessible any more for security 
> reasons. Now I use the call suggested in the Arch Linux bug report using
> "runpdfbegin".

The full (noisy) debdiff is attached, but here comes the real source diff:

--- a/filter/foomatic-rip/pdf.c
+++ b/filter/foomatic-rip/pdf.c
@@ -47,9 +47,8 @@ static int pdf_count_pages(const char *filename)
 size_t bytes;
 
 snprintf(gscommand, CMDLINE_MAX, "%s -dNODISPLAY -q -c "
-"'/pdffile (%s) (r) file def pdfdict begin pdffile pdfopen begin "
-"(PageCount: ) print pdfpagecount == flush currentdict pdfclose "
-"end end quit'",
+"'/pdffile (%s) (r) file runpdfbegin (PageCount: ) print "
+"pdfpagecount = quit'",
 gspath, filename);
 
 FILE *pd = popen(gscommand, "r");


This patch was uploaded to experimental as 1.22.5-1 and to unstable as 1.21.6-5
today.

unblock cups-filters/1.21.6-5

Cheers, and thanks for your time;
OdyX
diff -Nru cups-filters-1.21.6/debian/changelog 
cups-filters-1.21.6/debian/changelog
--- cups-filters-1.21.6/debian/changelog2019-02-16 14:31:17.0 
+0100
+++ cups-filters-1.21.6/debian/changelog2019-04-10 17:13:22.0 
+0200
@@ -1,3 +1,11 @@
+cups-filters (1.21.6-5) unstable; urgency=medium
+
+  * Backport upstream patch:
+ - foomatic-rip: Changed Ghostscript call to count pages in a PDF file so
+   that it works with GS 9.27 (Closes: #926576)
+
+ -- Didier Raboud   Wed, 10 Apr 2019 17:13:22 +0200
+
 cups-filters (1.21.6-4) unstable; urgency=medium
 
   * Backport upstream patch:
diff -Nru cups-filters-1.21.6/debian/.git-dpm 
cups-filters-1.21.6/debian/.git-dpm
--- cups-filters-1.21.6/debian/.git-dpm 2019-02-16 14:31:17.0 +0100
+++ cups-filters-1.21.6/debian/.git-dpm 2019-04-10 17:13:22.0 +0200
@@ -1,6 +1,6 @@
 # see git-dpm(1) from git-dpm package
-c1ec6e6233f90f7944e796732bcb68b546e75512
-c1ec6e6233f90f7944e796732bcb68b546e75512
+ac421831bde36d391900eba263cb6215eacb4927
+ac421831bde36d391900eba263cb6215eacb4927
 ec41f03b4dc5def5a6d53ea1dbb856f4b1bba169
 ec41f03b4dc5def5a6d53ea1dbb856f4b1bba169
 cups-filters_1.21.6.orig.tar.xz
diff -Nru 
cups-filters-1.21.6/debian/patches/0005-foomatic-rip-Changed-Ghostscript-call-to-count-pages.patch
 
cups-filters-1.21.6/debian/patches/0005-foomatic-rip-Changed-Ghostscript-call-to-count-pages.patch
--- 
cups-filters-1.21.6/debian/patches/0005-foomatic-rip-Changed-Ghostscript-call-to-count-pages.patch
  1970-01-01 01:00:00.0 +0100
+++ 
cups-filters-1.21.6/debian/patches/0005-foomatic-rip-Changed-Ghostscript-call-to-count-pages.patch
  2019-04-10 17:13:22.0 +0200
@@ -0,0 +1,26 @@
+From ac421831bde36d391900eba263cb6215eacb4927 Mon Sep 17 00:00:00 2001
+From: Till Kamppeter 
+Date: Sun, 7 Apr 2019 16:34:16 +0200
+Subject: foomatic-rip: Changed Ghostscript call to count pages in a PDF file
+ so that it works with GS 9.27.
+
+---
+ filter/foomatic-rip/pdf.c | 5 ++---
+ 1 file changed, 2 insertions(+), 3 deletions(-)
+
+diff --git a/filter/foomatic-rip/pdf.c b/filter/foomatic-rip/pdf.c
+index 9c3979bb2..bc739bd80 100644
+--- a/filter/foomatic-rip/pdf.c
 b/filter/foomatic-rip/pdf.c
+@@ -47,9 +47,8 @@ static int pdf_count_pages(const char *filename)
+ size_t bytes;
+ 
+ snprintf(gscommand, CMDLINE_MAX, "%s -dNODISPLAY -q -c "
+-   "'/pdffile (%s) (r) file def pdfdict begin pdffile pdfopen begin "
+-   "(PageCount: ) print pdfpagecount == flush currentdict pdfclose "
+-   "end end quit'",
++   "'/pdffile (%s) (r) file runpdfbegin (PageCount: ) print "
++   "pdfpagecount = quit'",
+gspath, filename);
+ 
+ FILE *pd = popen(gscommand, "r");
diff -Nru cups-filters-1.21.6/debian/patches/auto-gitignore 
cups-filters-1.21.6/debian/patches/auto-gitignore
--- cups-filters-1.21.6/debian/patches/auto-gitignore   2019-02-16 
14:31:17.0 +0100
+++ cups-filters-1.21.6/debian/patches/auto-gitignore   2019-04-10 
17:13:22.0 +0200
@@ -4,7 +4,7 @@
 .gitignore file(s).  This patch is autogenerated, to provide these
 updates to users of the official Debian archive view of the package.
 
-[dgit (8.3) update-gitignore]
+[dgit (8.4) update-gitignore]
 ---
 diff --git a/.gitignore b/.gitignore
 new file mode 100644
diff -Nru cups-filters-1.21.6/debian/patches/series 
cups-filters-1.21.6/debian/patches/series
--- cups-filters-1.21.6/debian/patches/series   2019-02-16 

Bug#924291: closed by Markus Koschany (Bug#924291: fixed in netrek-client-cow 3.3.1-3)

[Helmut Grohne]

Hi Stephen,

I looked into why it runs mkkey and couldn't figure out much. Let me
write down what I know:
 * It generates an RSA public/private key pair.
 * The public key is installed to /usr/share/doc.
 * The private key is used in some other way during the build (the
   comments talk about obfuscation).

Thus I think that removing the public key should be possible, but it
doesn't help, because the private key gets embedded elsewhere and I
don't understand what it is being used for.

On Wed, Apr 10, 2019 at 04:03:14PM +0200, Stephen Kitt wrote:
> I have a patch which builds mkkey using the build CC, which makes the build
> fail earlier because we don't have libgmp, so that would fix the endless
> build ;-). Helmut, do we have any way of specifying native build-deps? IIRC
> we don't yet, is that still the case?

Thank you for working on this. Indeed making it fail earlier would help
a lot. This is the only package that breaks the crossqa.d.n
infrastructure.

The annotation you are looking for is :native. It can only be used in
Build-* relations and never in binary package relations. In this case,
you likely want to depend on libgmp-dev twice, because other parts need
it for the host architecture:

Build-Depends: libgmp-dev, libgmp-dev:native

This might look odd, but it actually works (as libgmp-dev is Multi-Arch:
same) and for native builds these dependencies are identical.

I'd appreciate if you could go ahead with your changes (with or without
libgmp-dev:native, just make it fail reliably rather than loop).

Helmut

Bug#926789: ghostscript: unrecoverable error -> cups: no print, return "Filter failed"

[Jonas Smedegaard]

Quoting Antonio (2019-04-10 14:06:37)
> the version *9.27~dfsg-1* of ghostscript packages returns an error and
> cups can no longer print documents.

Thanks for reporting this issue!

Please check if this is the already reported bug 
https://bugs.debian.org/926576

 - 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#926799: lintian: hangs when dpkg-source fails

[Lucas Nussbaum]

Package: lintian
Version: 2.12.0~bpo9+1
Severity: normal

Hi,

While processing old packages, I noticed that lintian hangs on some of
them when dpkg-source fails to extract them.

Example, using:
http://snapshot.debian.org/archive/debian/20130509T215232Z/pool/main/u/usbredir/usbredir_0.6-2.dsc


$ lintian usbredir_0.6-2.dsc 
dpkg-source: error: expected ^--- in line 3 of diff 
'/tmp/temp-lintian-lab-vcUvBQH1iD/pool/u/usbredir/usbredir_0.6-2_source/unpacked/debian/patches/update-usbredirserver-whatis-entry.diff'
internal error: dpkg-source -x failed with status  2 at 
/usr/share/perl5/Lintian/Util.pm line 1177.
Lintian::Util::internal_error("dpkg-source -x failed with status ", 2) 
called at /usr/share/lintian/collection/unpacked line 74
Lintian::coll::unpacked::collect("usbredir", "source", 
"/tmp/temp-lintian-lab-vcUvBQH1iD/pool/u/usbredir/usbredir_0.6"...) called at 
/usr/share/perl5/Lintian/CollScript.pm line 242
Lintian::CollScript::collect(Lintian::CollScript=HASH(0x55d35d11c150), 
"usbredir", "source", 
"/tmp/temp-lintian-lab-vcUvBQH1iD/pool/u/usbredir/usbredir_0.6"...) called at 
/usr/share/perl5/Lintian/Unpacker.pm line 412
eval {...} called at /usr/share/perl5/Lintian/Unpacker.pm line 412
Lintian::Unpacker::__ANON__() called at 
/usr/share/perl5/IO/Async/Loop.pm line 1943
eval {...} called at /usr/share/perl5/IO/Async/Loop.pm line 1943
IO::Async::Loop::fork(IO::Async::Loop::Poll=HASH(0x55d35cb387b0), 
"code", CODE(0x55d35e922518), "on_exit", CODE(0x55d35e926f20)) called at 
/usr/share/perl5/Lintian/Unpacker.pm line 461
eval {...} called at /usr/share/perl5/Lintian/Unpacker.pm line 385
Lintian::Unpacker::__ANON__("unpacked-source:usbredir/0.6-2", 
Lintian::CollScript=HASH(0x55d35d11c150), 
Lintian::Lab::Entry=HASH(0x55d35c8280b0), 
Lintian::DepMap::Properties=HASH(0x55d35e8e05d8)) called at 
/usr/share/perl5/Lintian/Unpacker.pm line 476

Lintian::Unpacker::process_tasks(Lintian::Unpacker=HASH(0x55d35d1108d8), 
HASH(0x55d35c4e18b0)) called at /usr/share/lintian/commands/lintian.pm line 957
main::unpack_group("usbredir/0.6-2", 
Lintian::ProcessableGroup=HASH(0x55d35c827f48)) called at 
/usr/share/lintian/commands/lintian.pm line 730
main::__ANON__() called at /usr/share/lintian/commands/lintian.pm line 
1658
main::timed_task(CODE(0x55d35e9003b0)) called at 
/usr/share/lintian/commands/lintian.pm line 733
main::__ANON__() called at /usr/share/lintian/commands/lintian.pm line 
1658
main::timed_task(CODE(0x55d35e8f3fe8)) called at 
/usr/share/lintian/commands/lintian.pm line 762
main::main() called at /usr/bin/lintian line 46
eval {...} called at /usr/bin/lintian line 46
main::__ANON__("/usr/share/lintian/commands/lintian.pm") called at 
/usr/bin/lintian line 114
dplint::run_tool("/usr/bin/lintian", "lintian") called at 
/usr/bin/lintian line 290
dplint::main() called at /usr/bin/lintian line 359
warning: collect info unpacked about package usbredir failed (512)
warning: skipping check of source package usbredir


I would expect lintian to exit with an error instead.

A list of packages for which it hang:

acpica-unix_20140424-1
cb2bib_1.4.4-3
cnews_cr.g7-37
cnews_cr.g7-38
cnews_cr.g7-39
cnews_cr.g7-40
cnews_cr.g7-40.1
cnews_cr.g7-40.2
cnews_cr.g7-40.4
dwm_6.0-3
dwm_6.0-5
dynare_4.2.1-2
flite_1.4-release-8
foremost_1.5.7-4
fslint_2.16-1
getfem++_4.1.1-10
getfem++_4.1.1-9
getfem++_4.1.1+dfsg1-11
getfem++_4.2+dfsg1-1
grpn_1.1.2-3.1
herculesstudio_1.3.0-2
hfsutils_3.2.6-12
icedove_3.0.11-2
katoob_0.5.9.1-3
katoob_0.5.9.1-4
katoob_0.5.9.1-4.1
kvpm_0.8.6-2
kvpm_0.8.6-3
lazarus_1.2~rc2+dfsg-1
lldpad_0.9.43+git20111215.c0498b-1
lldpad_0.9.44-1
lldpad_0.9.46-1
lldpad_0.9.46-2
lurker_2.3-4
lurker_2.3-4.1
lutefisk_1.0.7+dfsg-1
moodle_1.9.9.dfsg2-4
moodle_1.9.9.dfsg2-5
ncmpcpp_0.5.5-1
nsnake_1.5-1
ompl_0.13.0+git20130920.01d0ca4-1
ompl_0.14.1-1
opencryptoki_2.3.1+dfsg-1
openms_1.9.0-4
openms_1.9.0-4.1
openoffice-python_1:0.1+20110129-1
piwigo_2.3.1-1
puppet_2.7.17-1
python-virtualenv_1.7-1
python-webob_1.2.3-4
qemu_1.7.0+dfsg-5
ruby-saml_1.0.0-1
ruby-saml_1.1.2-1
ruby-saml_1.3.0-1
ruby-saml_1.4.1-1
ruby-saml_1.7.2-1
rust-roxmltree_0.4.1-2
samba_2:3.6.16-1
samba_2:3.6.6-2
samba_2:3.6.6-3
samba_2:3.6.6-5
spice_0.12.4-0nocelt1
spice_0.12.4-0nocelt2
spice-vdagent_0.14.0-1
spice-vdagent_0.15.0-1
tac-plus_F4.0.4.alpha-12
tac-plus_F4.0.4.alpha-12.1
u-boot_2014.04+dfsg1-1
u-boot_2014.07+dfsg1-2
u-boot_2014.10+dfsg1-2.1
usbredir_0.4.3-2
usbredir_0.6-2
widelands_build10-1
widelands_build9-6
widelands_build9-7
widelands_build9half-1
widelands_build9half-10
widelands_build9half-9

- Lucas


-- System Information:
Debian Release: 9.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (400, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/8 CPU cores)
Locale: 

Bug#926798: Acknowledgement (RFP: elpa-magit-forge -- Work with Git forges from the comfort of Magit)

[Antoine Beaupré]

Well that was quick. I tried to install forge on stretch with ELPA, and
it fails to load. I don't have the details on hand, but at first it
failed because the stretch version of magit was out of date, but even
after restarting emacs with the newer magit version, it would still fail
with:

Symbol’s value as variable is void: cl-struct-magit-section-tags

So I'm not sure this is going to be easy to package after all...

a.

-- 
La nature n'a créé ni maîtres ni esclaves
Je ne veux ni donner ni recevoir de lois.
- Denis Diderot

Bug#890343: The Debian kernel could use the fq_codel network queuing algorithm by default

[Laurent Bonnaud]

Hi,

this "bug" still exists in the latest 4.19 kernel in Debian:

# uname -a
Linux irancy 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64 
GNU/Linux

# ip addr
[...]
2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000

-- 
Laurent.

Bug#926700: cacti: CVE-2019-11025:

[Chris Lamb]

retitle 926700 cacti: CVE-2019-11025 - XSS in utilities.php
thanks

Hi all,

I've attached a patch that I intend to upload to jessie LTS. May I
also prepare an update for stretch based on this?


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-Backport from https://github.com/Cacti/cacti/commit/c373e66a6a224e221a1db037164144ce59b20736

--- cacti-0.8.8b+dfsg.orig/utilities.php
+++ cacti-0.8.8b+dfsg/utilities.php
@@ -1164,7 +1164,7 @@ function utilities_view_snmp_cache() {
 			}
 			if (sizeof($hosts) > 0) {
 			foreach ($hosts as $host) {
-print "" . $host["description"] . "\n";
+print "" . htmlspecialchars($host["description"]) . "\n";
 			}
 			}
 			?>
@@ -1305,7 +1305,7 @@ function utilities_view_snmp_cache() {
 		form_alternate_row_color($colors["form_alternate1"],$colors["form_alternate2"],$i);
 		?>
 		
-			Host: \\1", $item["description"])) : $item["description"]);?>
+			Host: \\1", htmlspecialchars($item["description"]))) : htmlspecialchars($item["description"]));?>
 			, SNMP Query: \\1", $item["name"])) : $item["name"]);?>
 		
 		
@@ -1313,7 +1313,7 @@ function utilities_view_snmp_cache() {
 		form_alternate_row_color($colors["form_alternate1"],$colors["form_alternate2"],$i);
 		?>
 		
-			Index: 
+			Index: 
 			, Field Name: \\1", $item["field_name"])) : $item["field_name"]);?>
 			, Field Value: \\1", $item["field_value"])) : $item["field_value"]);?>
 		
@@ -1559,12 +1559,12 @@ function utilities_view_poller_cache() {
 if ($item["snmp_version"] != 3) {
 	$details =
 		"SNMP Version: " . $item["snmp_version"] . ", " .
-		"Community: " . $item["snmp_community"] . ", " .
+		"Community: " . htmlspecialchars($item["snmp_community"]) . ", " .
 		"OID: " . (strlen(get_request_var_request("filter")) ? (preg_replace("/(" . preg_quote(get_request_var_request("filter"), "/") . ")/i", "\\1", $item["arg1"])) : $item["arg1"]);
 }else{
 	$details =
 		"SNMP Version: " . $item["snmp_version"] . ", " .
-		"User: " . $item["snmp_username"] . ", OID: " . $item["arg1"];
+		"User: " . htmlspecialchars($item["snmp_username"]) . ", OID: " . $item["arg1"];
 }
 			}elseif ($item["action"] == 1) {
 	$details = "Script: " . (strlen(get_request_var_request("filter")) ? (preg_replace("/(" . preg_quote(get_request_var_request("filter"), "/") . ")/i", "\\1", $item["arg1"])) : $item["arg1"]);
@@ -1583,7 +1583,7 @@ function utilities_view_poller_cache() {
 			
 			
 			
-RRD: 
+RRD: 
 			
 		
 		

Bug#926798: RFP: elpa-magit-forge -- Work with Git forges from the comfort of Magit

[Antoine Beaupre]

Package: wnpp
Severity: wishlist

* Package name: elpa-magit-forge
  Version : 0.1.0
  Upstream Author : Jonas Bernoulli 
* URL : https://github.com/magit/forge
* License : GPL-3
  Programming Lang: Elisp
  Description : Work with Git forges from the comfort of Magit

Forge allows you to work with Git forges, such as Github and Gitlab,
from the comfort of Magit and the rest of Emacs.

Forge fetches issues, pull-requests and other data using the forge’s
API and stores that in a local database. Additionally it fetches the
pull-request references using Git. Forge implements various features
that use this data but the database and pull-request refs can also be
used by third-party packages.

Forge currently supports the following forges in one way or the other:

 * Github
 * Gitlab
 * Gitweb
 * Cgit
 * Stgit
 * Srht

There are also plans to support Gitea and Gogs and possibly
Bitbucket.



I keep on coming back to this package. I think it's installable
through MELPA but because of the poor connexion here, I'm having
trouble testing it.

Since we already have magit in the archive, it would seem natural to
package this extremely useful tool.

There's a similar tool in Debian packaged as elpa-magithub but that
only works for github, while magit-forge supports other forges as
well, like gitlab, gitea and so on.

Bug#924291: closed by Markus Koschany (Bug#924291: fixed in netrek-client-cow 3.3.1-3)

[Stephen Kitt]

Hi Helmut,

Le 10/04/2019 13:59, Markus Koschany a écrit :

Am 10.04.19 um 06:33 schrieb Helmut Grohne:
On Sun, Mar 24, 2019 at 01:09:06PM +, Debian Bug Tracking System 
wrote:

   * Fix infinite loop patch. Really (Closes: #924291)


As much as I hate to say this, it still loops. You can see failing
(cross) builds at http://crossqa.debian.net/src/netrek-client-cow. All
of them were terminated by manual intervention.

Remember: I'm not asking for netrek-client-cow to cross build. I'm
asking for it to fail sanely.

The current version loops like this:

| /bin/sh: 1: ./mkkey: Exec format error
| /bin/sh: 1: attempts: not found
| /bin/sh: 1: test: -le: unexpected operator


I don't know why this happens now and on what system but I thought the
last update of the possible-infinite-loop.patch was correct.


The problem is that the execution fails too early, effectively, so the 
countdown of attempts never works.


I have a patch which builds mkkey using the build CC, which makes the 
build fail earlier because we don't have libgmp, so that would fix the 
endless build ;-). Helmut, do we have any way of specifying native 
build-deps? IIRC we don't yet, is that still the case?


Regards,

Stephen

Bug#926716: lsof: FTBFS on linux in tests

[Mathieu Trudel-Lapierre]

On Tue, Apr 9, 2019 at 1:25 PM Andres Salomon  wrote:
>
> On Tue, 09 Apr 2019 10:57:47 -0400
> Mathieu Trudel-Lapierre  wrote:
>
> > Package: lsof
> > Version: 4.91+dfsg-1
> > Severity: normal
> > Tags: patch
> > User: ubuntu-de...@lists.ubuntu.com
> > Usertags: origin-ubuntu disco ubuntu-patch
> >
> > Dear Maintainer,
> >
> > lsof FTBFS on linux in tests rebuilds; due to the changes in
> > major()/minor() macros.
> >
> > In Ubuntu, the attached patch was applied to achieve the following:
> >
> >   * debian/patches/majorminor: Fix ftbfs due to missing major/minor
> > macros in tests; by including sysmacros.h where appropriate.
> >
> >
>
> Thanks! Is this due to a change in libc6 2.29?

This was a change in glibc 2.28 [1]; though deprecation started in 2.25.

[1] 
https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commit;h=e16deca62e16f645213dffd4ecd1153c37765f17

Kind regards,

Mathieu Trudel-Lapierre 
Freenode: cyphermox, Jabber: mathieu...@gmail.com
4096R/65B58DA1 818A D123 0992 275B 23C2  CF89 C67B B4D6 65B5 8DA1

Bug#923711:

[Pacho Ramos]

Please take into account that upstream is completely against applying
that patch:
https://github.com/plougher/squashfs-tools/issues/60

Bug#926797: gimp: with KDE plasma 5.14 ( buster) menus are in mode transparency, so they are unreadable

[bruno volpi]

Package: gimp
Version: 2.10.8-2
Severity: important

Dear Maintainer,


I use KDE plasma 5.14
Global menu in title bar doesn't work, it's not a big deal because i don't like
it very much.
So i use the normal Menu bar.
the bar by itself appear ok, but i i try to go on the sub menu they are totaly
transparent and completly unreadable.
Is there as workaround or do i have to go back to gnome ?

system info
Debian 'Buster'
KDE plasma 5.14.5
kernel 4.19.0-4-amd64



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

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

Versions of packages gimp depends on:
ii  gimp-data2.10.8-2
ii  libaa1   1.4p5-46
ii  libbabl-0.1-00.1.62-1
ii  libbz2-1.0   1.0.6-9
ii  libc62.28-8
ii  libcairo21.16.0-4
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3
ii  libgcc1  1:8.3.0-5
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libgegl-0.4-00.4.12-2
ii  libgexiv2-2  0.10.9-1
ii  libgimp2.0   2.10.8-2
ii  libglib2.0-0 2.58.3-1
ii  libgs9   9.26a~dfsg-2
ii  libgtk2.0-0  2.24.32-3
ii  libgudev-1.0-0   232-2
ii  libharfbuzz0b2.3.1-1
ii  libheif1 1.3.2-1+b1
ii  libilmbase23 2.2.1-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3
ii  liblzma5 5.2.4-1
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.3-0 1.3.0-2.1
ii  libopenexr23 2.2.1-4.1
ii  libopenjp2-7 2.3.0-2
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpangoft2-1.0-01.42.4-6
ii  libpng16-16  1.6.36-5
ii  libpoppler-glib8 0.71.0-3
ii  librsvg2-2   2.44.10-1
ii  libstdc++6   8.3.0-5
ii  libtiff5 4.0.10-4
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libwmf0.2-7  0.2.8.4-14
ii  libx11-6 2:1.6.7-1
ii  libxcursor1  1:1.1.15-2
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2+b3
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages gimp recommends:
ii  ghostscript  9.26a~dfsg-2

Versions of packages gimp suggests:
pn  gimp-data-extras  
pn  gimp-help-en | gimp-help  
pn  gimp-python   
pn  gvfs-backends 
ii  libasound21.1.8-1

-- no debconf information

Bug#926796: bochs recommends the package createdisk which isn't available

[Daniele Forsi]

Source: bochs
Severity: minor

Dear Maintainer,

bochs recommends bximage | createdisk but createdisk was removed from Debian
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314669

thank you,
Daniele

Bug#926795: di-netboot-assistant: Unable to install Debian Buster amd64 from d-i n-a at 2019-04-10 generated boot-file

[Ralf Moll]

Package: di-netboot-assistant
Version: 0.60
Severity: normal

Dear Maintainer,

the "Debian testing (amd64) image 20190410", generated by

di-netboot-assistant install stable testing

shows after answering a few installer querstions the following dialog:

"[!!] Download installer components

No kernel modules were found. This probably is due to a mismatch between
the kernel used by this version of the Installer and the kernel version
available in the archive.

If you 're Installing from a mirror, you can work around this problem
by choosing to Install a different version of Debian. The Install will
probably fail to work if you continue without kernel modules.

Continue the Install without loading kernel modules?

  "

No matter what I select, the installer will fail.

Seems kernel and mirror are out of sycn...

Thanks for any hint

Ralf


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

Kernel: Linux 4.19.0-4-amd64 (SMP w/2 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#926793: chown xyz. doesn't complete.

[積丹尼 Dan Jacobson]

Package: bash-completion
Version: 1:2.8-6
Severity: minor
File: /usr/share/bash-completion/completions/chown

# chown jidanni. doesn't complete.
It should complete the possible groups.

Bug#926794: linux-image-4.19.0.0-bpo.4-amd64: Please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel config

[Frantisek Novak]

Package: linux-image-4.19.0.0-bpo.4-amd64
Version: linux-image-4.19.0-0-bpo.4-amd64
Severity: wishlist

Dear Maintainer,

please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel configuration to 
prevent clearing of the framebuffer when the console starts during the boot.

Thanks
Frantisek

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

Kernel: Linux 4.19.0-0.bpo.4-amd64 (SMP w/3 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#909480: Feersum FTBFS

[Santiago Vila]

affects 909480 src:feersum
thanks

Hello Xavier.

I almost report this again because we forgot to add the affects. Fixed that now.

The failure rate in my autobuilders for feersum is still extremely high.

I could understand that you don't want to add a workaround in feersum
if the package to blame is another one, but OTOH if a package A makes
package B to FTBFS, then package A should have a serious bug.

Therefore I don't think it is ok that both A) This bug is still "normal"
and B) Test suite in feersum keeps failing a lot.

(I already have your public ssh key, please tell me if you still need
a test machine).

Thanks.

Bug#926792: [cppreference-doc] Please update to last upstream version

[Giovanni Mascellani]

Package: cppreference-doc
Version: 20170409-1
Severity: wishlist

Dear maintainer,

this package seems to be a few years out of date. Considering how
quickly the C++ landscape is evolving nowadays, I believe that it could
be useful to update cppreference-doc to the last released version, which
is currently 20181028.

If you are not currently having time to work on this I can prepare the
next upload, and if you are ok I can also take co-mantainership.

Please let me know and all the best!

Thanks for your work, Giovanni.


--- System information. ---
Architecture: Kernel:   Linux 4.19.0-4-amd64

Debian Release: buster/sid
  500 xenial  updates.signal.org   500 unstable-debug
debug.mirrors.debian.org   500 unstableftp.be.debian.org   500
testing ftp.be.debian.org   500 stable  repo.skype.com
 500 stable  dl.google.com 1 experimentalftp.be.debian.org
--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.
-- 
Giovanni Mascellani 
Postdoc researcher - Université Libre de Bruxelles



signature.asc
Description: OpenPGP digital signature