Bug#925951: "zsnes" does not support symlinks.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: zsnes
Version: 1.510+bz2-8+b3

Steps to reproduce:
1. Start ZSNES and save settings.
2. It creates a "$HOME/.zsnes/" folder for the configuration.
3. Symlink that folder to elsewhere, e. g. "$HOME/.config/zsnes/" (the folder 
is already created).
4. Start ZSNES again and found that the settings are not applied.
5. Change settings and save them again. This time it directly put them in 
"$HOME/".

Not related, but I hope you to follow XDG and move your config in a sane folder 
like "$HOME/.config/zsnes/".
-
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcnbBvAAoJENi1YDlFXXQfWNwH/AxEhkWM8m/IMQT5M7N7
IggXNvccxJywg4lcYk7lR4JSiCSqlHQA0gHApHX4TuSWW1J6mztydArm7PCV
ZGOSQEgWIYuzrcFlPBb2K7LN9G7hShRwo9aaDuy0IvEVc2JVbfEYJgvqWGDZ
nWeUKINc5/VmHZ3eqVcxmTnOtN09kwv+/R9u9itdwlCb8XaJjnvEFbVHhb4k
WX5e1CrwrjiRWPWBfs4zG94QIj/dXZ9V4zS78Mv+eGqCqBvWqo1V5C5TAhMH
O5SiM5E3+PAmOJHRM+iJbXdwxSoAnjhhCm4BuROAvw/yvBTzrhD4fH2sTEcu
ERLXEFLP0lx+Bqu+IFlSRxg=
=C0kg
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#925950: patches no longer apply for gcc-8 and gcc-9

[Helmut Grohne]

Package: cross-gcc-dev
Version: 226
Severity: serious
Tags: patch

The patches for gcc-8 and gcc-9 no longer apply to unstable. Around two
weeks ago that used to work. Apparently, Matthias fixed a typo in
debian/control.m4 and that happens to break the hunk context of one
patch. The following sed expression fixes the patches:


sed -i -e 's/\(`TARGET\))/\1/' patches/gcc-[89]/*-now-depend-on-cpp-*

Helmut

Bug#919929: python-scipy: autopkgtest fails intermittently

[Drew Parsons]

Package: python-scipy
Followup-For: Bug #919929

debci tests are consistently passing with python-scipy/1.1.0-4

I think we can consider this bug resolved now.

Drew



-- 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_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

Versions of packages python-scipy depends on:
ii  libatlas3-base [liblapack.so.3]3.10.3-8
ii  libblas3 [libblas.so.3]3.8.0-2
ii  libc6  2.28-8
ii  libgcc11:8.3.0-4
ii  libgfortran5   8.3.0-4
ii  liblapack3 [liblapack.so.3]3.8.0-2
ii  libopenblas-base [liblapack.so.3]  0.3.5+ds-3
ii  libquadmath0   8.3.0-4
ii  libstdc++6 8.3.0-4
ii  python 2.7.16-1
ii  python-decorator   4.3.0-1.1
ii  python-numpy [python-numpy-abi9]   1:1.16.2-1

Versions of packages python-scipy recommends:
ii  g++   4:8.3.0-1
ii  g++-7 [c++-compiler]  7.4.0-8
ii  g++-8 [c++-compiler]  8.3.0-4
ii  python-dev2.7.16-1
ii  python-pil5.4.1-1

Versions of packages python-scipy suggests:
ii  python-scipy-doc  1.1.0-4

-- no debconf information

Bug#925932: logtop FTCBFS: does not pass cross tools to make

[Helmut Grohne]

On Thu, Mar 28, 2019 at 10:14:42PM +, Julien Palard wrote:
> I do not feel like re-reading the whole maintainer guide tonight to play the 
> "find the 7 difference" game between "level 7" and the "current level". But 
> don't hesitate to tell me if there's some (simple) steps missing for this 
> cross build to pass.

Take your time. The bug at hand is not release-critical and Debian is
currently frozen. You shouldn't be uploading this to unstable anyway
before buster is released.

The debhelper warning is quite harmless and my patch is sufficient for
making logtop cross build. It is informing you that you are using old
interfaces and should be upgrading eventually, but not necessarily now.
man 7 debhelper has an upgrading checklist for your convenience.

Helmut

Bug#864827: Whither Zotero 5?

[Borden Rhodes]

On Sun, 24 Mar 2019 17:47:38 +0100 =?ISO-8859-1?Q?S=E9bastien?=
Villemot  wrote:
> The main reason is lack of manpower (a lot of work in the Javascript
> packages need to happen first).

Thank you for the explanation. Is there a to-do list or some
elaboration on the work that needs to be done?

Bug#925949: RFP: node-evacuated-wide-align -- Wide-character aware text alignment function

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: node-evacuated-wide-align
  Version : 1.1.3
  Upstream Author : Rebecca Turner  
* URL : 
https://salsa.debian.org/themusicgod1-guest/evacuated-wide-align
* License : ISC
  Programming Lang: javascript
  Description : Wide-character aware text alignment function

Fork of node-wide-align with a different upstream.

At version 1.1.3 rather than 1.1.0 (which is where node-wide-align is 
currently),
which is required by task Meteor 
( https://wiki.debian.org/Javascript/Nodejs/Tasks/Meteor / #842425 ).

Bug#925948: xfce4-power-manager: Display power management blanking cannot unblank

[Ed Peguillan III]

Package: xfce4-power-manager
Version: 1.6.1-1
Severity: grave
Tags: a11y
Justification: causes non-serious data loss

Running Debian testing on Lenovo ThinkPad X1 Extreme, xfce4 desktop
environment.

I wished to have power manager blank my monitor after 1 minute of inactivity if
running on battery. Power manager does successfully blank monitor, but
cannot unblank. Moving the mouse or pressing any keys does not unblank
the monitor. Only way to fix is to hold power button to force a
shutdown.

EDIT: A workaround is to use CTRL + ALT + F<2,3,4,etc> to switch to a
new tty temporarily. Then CTRL + ALT + F1 switches back to xfce, which
will display the unlock screen.

Steps to reproduce:

1. Allow XFCE4 Power Manager to manage display power
2. Set 'Blank after' to One minute.
3. Wait 1 minute. Display blanks, cannot unblank.

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

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

Versions of packages xfce4-power-manager depends on:
ii  libc6 2.28-8
ii  libcairo2 1.16.0-4
ii  libgdk-pixbuf2.0-02.38.1+dfsg-1
ii  libglib2.0-0  2.58.3-1
ii  libgtk-3-03.24.5-1
ii  libnotify40.7.7-4
ii  libpango-1.0-01.42.4-6
ii  libpangocairo-1.0-0   1.42.4-6
ii  libupower-glib3   0.99.10-1
ii  libx11-6  2:1.6.7-1
ii  libxext6  2:1.3.3-1+b2
ii  libxfce4ui-2-04.12.1-3
ii  libxfce4util7 4.12.1-3
ii  libxfconf-0-2 4.12.1-1
ii  libxrandr22:1.5.1-1
ii  upower0.99.10-1
ii  xfce4-power-manager-data  1.6.1-1

Versions of packages xfce4-power-manager recommends:
ii  libpam-systemd   241-1
ii  xfce4-power-manager-plugins  1.6.1-1

xfce4-power-manager suggests no packages.

-- no debconf information

Bug#925887: Users fooled by Busybox boilerplate

[積丹尼 Dan Jacobson]

Maybe just have a message: "press TAB to see all available commands."
That would show both built-ins and non builtins. (Hope TAB works.)

Bug#925160: request for performance test in your environment

[Aaron M. Ucko]

Osamu Aoki  writes:

> IM_CONFIG_WAYLAND=disable

===> multitime results
1: -q /usr/lib/systemd/user-environment-generators/70-im-config
MeanStd.Dev.Min Median  Max
real0.001   0.000   0.001   0.001   0.002   
user0.001   0.000   0.000   0.001   0.001   
sys 0.000   0.001   0.000   0.000   0.001   

> IM_CONFIG_WAYLAND=enable

===> multitime results
1: -q /usr/lib/systemd/user-environment-generators/70-im-config
MeanStd.Dev.Min Median  Max
real0.004   0.000   0.003   0.004   0.004   
user0.003   0.001   0.001   0.003   0.005   
sys 0.001   0.001   0.000   0.002   0.004   

... so quite fast either way.

> Is these better way to get the primary multiarch path name?

Not to my knowledge. :-/

> (I can't do it during the build since this is arch ALL package)

I suppose you could formally make it architecture: any for this purpose;
the package is small enough that the resulting duplication would be no
big deal.

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

Bug#902893: x11vnc: Error in `x11vnc': corrupted size vs. prev_size: 0x000055f181552530

[Bernhard Übelacker]

Control: fixed 902893 0.9.13-6


Dear Maintainer,
just tried to make a more readable stack out of these
backtraces.

This one points to function snapshot_stack_list,
and this one saw also a fix some time ago.

Therefore marking as fixed.

Kind regards,
Bernhard


https://github.com/LibVNC/x11vnc/pull/25
https://github.com/LibVNC/x11vnc/pull/25/commits/c93aa29ae76a2fbb3e8c8e55a68de5544bd863b5



*** Error in `x11vnc': corrupted size vs. prev_size: 0x55f181552530 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7fa6d0bcdbfb]
/lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7fa6d0bd3fc6]
/lib/x86_64-linux-gnu/libc.so.6(+0x780a4)[0x7fa6d0bd50a4]
/usr/lib/x86_64-linux-gnu/libX11.so.6(XFree+0x9)[0x7fa6d1c19699]
src/XlibInt.c, line 1553: callq  0x760c5600 
x11vnc(+0xaceb4)[0x55f17f5b9eb4]
win_utils.c, line 304: callq  0x55610da0 
x11vnc(+0x41887)[0x55f17f54e887]
pointer.c, line 552: callq  0x55600c70 
x11vnc(+0x42846)[0x55f17f54f846]
pointer.c, line 931: callq  0x55595540 
/usr/lib/x86_64-linux-gnu/libvncserver.so.1(rfbProcessClientMessage+0x7d6)[0x7fa6d36aaa56]
  rfbserver.c, line 2447: callq  *%rbx
/usr/lib/x86_64-linux-gnu/libvncserver.so.1(rfbCheckFds+0x3a8)[0x7fa6d36b09e8]  
sockets.c, line 464: callq  0x77b7fb70 

/usr/lib/x86_64-linux-gnu/libvncserver.so.1(rfbProcessEvents+0x1e)[0x7fa6d36a793e]
  main.c, line 1109: callq  0x77b7f130 
x11vnc(+0xaa721)[0x55f17f5b7721]
util.c, line 581: callq  0xd520 
x11vnc(+0xa27e5)[0x55f17f5af7e5]
userinput.c, line 5212: callq  0x555fe590 
x11vnc(+0x6a77c)[0x55f17f5c]
screen.c, line 4561: callq  0x555f5e90 
x11vnc(+0x13ae4)[0x55f17f520ae4]
x11vnc.c, line 5990: callq  0x555bdd10 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fa6d0b7d2e1]
x11vnc(+0x1cd7a)[0x55f17f529d7a]


# Stretch amd64 qemu VM 2019-03-29

apt update
apt dist-upgrade



approx:
debian-10-buster-snapshot.debian.org  
https://snapshot.debian.org/archive/debian/20180703T00Z/


sources.list
deb [check-valid-until=no] 
http://192.168.178.25:/debian-10-buster-snapshot.debian.org/ buster main


echo 'Acquire::Languages "none";' > /etc/apt/apt.conf.d/99disable-translations
echo 'Acquire::Check-Valid-Until "no";' > 
/etc/apt/apt.conf.d/99disable-check-valid-until


apt update
apt dist-upgrade


apt install dpkg-dev devscripts x11vnc gdb mc



wget 
https://snapshot.debian.org/archive/debian-debug/20180508T213823Z/pool/main/x/x11vnc/x11vnc-dbgsym_0.9.13-6_amd64.deb
dpkg -i x11vnc-dbgsym_0.9.13-6_amd64.deb


wget 
https://snapshot.debian.org/archive/debian/20161222T033154Z/pool/main/x/x11vnc/x11vnc_0.9.13-2_amd64.deb
wget 
https://snapshot.debian.org/archive/debian/20161222T033154Z/pool/main/x/x11vnc/x11vnc-data_0.9.13-2_all.deb
wget 
https://snapshot.debian.org/archive/debian-debug/20161222T030857Z/pool/main/x/x11vnc/x11vnc-dbgsym_0.9.13-2_amd64.deb
dpkg -i *0.9.13-2*deb

wget 
https://snapshot.debian.org/archive/debian-security/20180608T202807Z/pool/updates/main/libv/libvncserver/libvncserver1_0.9.11%2Bdfsg-1%2Bdeb9u1_amd64.deb
wget 
https://snapshot.debian.org/archive/debian-security/20180608T202807Z/pool/updates/main/libv/libvncserver/libvncserver1-dbg_0.9.11%2Bdfsg-1%2Bdeb9u1_amd64.deb
dpkg -i *0.9.11+dfsg-1+deb9u1*deb

wget 
https://snapshot.debian.org/archive/debian/20170128T033044Z/pool/main/libx/libx11/libx11-6_1.6.4-3_amd64.deb
wget 
https://snapshot.debian.org/archive/debian-debug/20170128T030650Z/pool/main/libx/libx11/libx11-6-dbgsym_1.6.4-3_amd64.deb
dpkg -i *1.6.4-3*deb



mkdir /home/benutzer/source/x11vnc/orig -p
cd/home/benutzer/source/x11vnc/orig
dget 
https://snapshot.debian.org/archive/debian-debug/20161222T030857Z/pool/main/x/x11vnc/x11vnc_0.9.13-2.dsc


gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'set backtrace past-main 
on' -ex 'directory /home/benutzer/source/x11vnc/orig/x11vnc-0.9.13/x11vnc' -ex 
'b main' -ex 'run' --args x11vnc


script -c "gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'set backtrace 
past-main on' -ex 'directory 
/home/benutzer/source/x11vnc/orig/x11vnc-0.9.13/x11vnc' -ex 'b main' -ex 'run' 
--args x11vnc" -a x11vnc-gdb_$(date +%Y-%m-%d_%H-%M-%S).log






*** Error in `x11vnc': corrupted size vs. prev_size: 0x55f181552530 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7fa6d0bcdbfb]
/lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7fa6d0bd3fc6]
/lib/x86_64-linux-gnu/libc.so.6(+0x780a4)[0x7fa6d0bd50a4]

Bug#925947: apt-listchanges: warns on postinst: -V is ignored in pypycompile

[Julian Gilbey]

Package: apt-listchanges
Version: 3.19
Severity: normal

On installing, I noticed the following warning:

Setting up apt-listchanges (3.19) ...
-V is ignored in pypycompile

Best wishes,

   Julian

Bug#925946: python3-apt: warns on postinst: -V is ignored in pypycompile

[Julian Gilbey]

Package: python3-apt
Version: 1.8.4
Severity: normal

On installing, I spotted this message:

Setting up python3-apt (1.8.4) ...
-V is ignored in pypycompile

Best wishes,

   Julian

Bug#857498: x11vnc: X11vnc crash during a connection with Remmina

[Bernhard Übelacker]

Control: fixed 857498 0.9.13-6


Dear Maintainer,
just tried to make a more readable stack out of these
backtraces.

So that one points to function "record_CW" and a buffer
overflow in that function got fixed in [1],
like mentioned in last message.

Therefore marking as fixed.

Kind regards,
Bernhard


[1] https://github.com/LibVNC/x11vnc/pull/25

https://github.com/LibVNC/x11vnc/pull/25/commits/a3a34ca49c60738cc958096ebb06dc7dbff4660a




*** stack smashing detected ***: x11vnc terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x7f016a945bcb]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f016a9ce0b7]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f016a9ce080]
x11vnc(+0xb8887)[0x55babf222887]
xrecord.c, line 1347: callq  0xe3b0 <__stack_chk_fail@plt>
x11vnc(+0xb8d3b)[0x55babf222d3b]
xrecord.c, line 1387: callq  0x5560bc80 
/usr/lib/x86_64-linux-gnu/libXtst.so.6(+0x19d8)[0x7f016c6b59d8] 
src/XRecord.c, line 856: callq  *%rax
/usr/lib/x86_64-linux-gnu/libXtst.so.6(+0x1f55)[0x7f016c6b5f55] 
src/XRecord.c, line 987: callq  0x76e1a910 
/usr/lib/x86_64-linux-gnu/libX11.so.6(+0x421dd)[0x7f016b98d1dd] 
src/xcb_io.c, line 305: callq  *0x8(%rax)
/usr/lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x55)[0x7f016b98db15]  
src/xcb_io.c, line 350: callq  0x760f2190 
/usr/lib/x86_64-linux-gnu/libX11.so.6(XPending+0x57)[0x7f016b97f7e7]
src/Pending.c, line 55: callq  0x760cc2c0 <_XEventsQueued@plt>
x11vnc(+0x97060)[0x55babf201060]
userinput.c, line 2988: callq  0xe490  -> 
jmpq   0x76e1a2e0 
x11vnc(+0xa1f95)[0x55babf20bf95]
userinput.c, line 5712: callq  0x555eab00 
x11vnc(+0x6a77c)[0x55babf1d477c]
screen.c, line 4561: callq  0x555f5e90 
x11vnc(+0x13ae4)[0x55babf17dae4]
x11vnc.c, line 5990: callq  0x555bdd10 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f016a8f52b1]
x11vnc(+0x1cd7a)[0x55babf186d7a]

# Jessie amd64 qemu VM 2019-03-28

apt update
apt dist-upgrade



approx:
debian-9-stretch-snapshot.debian.org
https://snapshot.debian.org/archive/debian/20170311T00Z/

sources.list:
deb [check-valid-until=no] 
http://192.168.178.25:/debian-9-stretch-snapshot.debian.org/ stretch main
deb-src [check-valid-until=no] 
http://192.168.178.25:/debian-9-stretch-snapshot.debian.org/ stretch main


echo 'Acquire::Languages "none";' > /etc/apt/apt.conf.d/99disable-translations
echo 'Acquire::Check-Valid-Until "no";' > 
/etc/apt/apt.conf.d/99disable-check-valid-until


apt update
apt dist-upgrade


apt install dpkg-dev devscripts x11vnc gdb


wget 
https://snapshot.debian.org/archive/debian-debug/20161222T030857Z/pool/main/x/x11vnc/x11vnc-dbgsym_0.9.13-2_amd64.deb
dpkg -i x11vnc-dbgsym_0.9.13-2_amd64.deb
wget 
https://snapshot.debian.org/archive/debian-debug/20170128T030650Z/pool/main/libx/libx11/libx11-6-dbgsym_1.6.4-3_amd64.deb
dpkg -i libx11-6-dbgsym_1.6.4-3_amd64.deb
wget 
https://snapshot.debian.org/archive/debian-debug/20161206T030437Z/pool/main/libx/libxtst/libxtst6-dbgsym_1.2.3-1_amd64.deb
dpkg -i libxtst6-dbgsym_1.2.3-1_amd64.deb


mkdir /home/benutzer/source/x11vnc/orig -p
cd/home/benutzer/source/x11vnc/orig
apt source x11vnc




gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'set backtrace past-main 
on' -ex 'directory /home/benutzer/source/x11vnc/orig/x11vnc-0.9.13/x11vnc' -ex 
'b main' -ex 'run' --args x11vnc

script -c "gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'set backtrace 
past-main on' -ex 'directory 
/home/benutzer/source/x11vnc/orig/x11vnc-0.9.13/x11vnc' -ex 'b main' -ex 'run' 
--args x11vnc" -a x11vnc-gdb_$(date +%Y-%m-%d_%H-%M-%S).log
disassemble main

benutzer@debian:~$ grep "ae4 " x11vnc-gdb_2019-03-29_01-45-59.log -B1
   0x55567adf <+19871>: callq  0x555bdd10 
   0x55567ae4 <+19876>: xor%eax,%eax



   
*** stack smashing detected ***: x11vnc terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x7f016a945bcb]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f016a9ce0b7]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f016a9ce080]
x11vnc(+0xb8887)[0x55babf222887]
xrecord.c, line 1347: callq  0xe3b0 <__stack_chk_fail@plt>
x11vnc(+0xb8d3b)[0x55babf222d3b]
xrecord.c, line 1387: callq  0x5560bc80 
/usr/lib/x86_64-linux-gnu/libXtst.so.6(+0x19d8)[0x7f016c6b59d8] 
src/XRecord.c, line 856: callq  *%rax
/usr/lib/x86_64-linux-gnu/libXtst.so.6(+0x1f55)[0x7f016c6b5f55] 
src/XRecord.c, line 987: callq  0x76e1a910 

Bug#925476: unblock: dwww/1.13.4+nmu3

[Osamu Aoki]

Hi,

On Wed, Mar 27, 2019 at 09:07:12PM +, Jonathan Wiltshire wrote:
> On Tue, Mar 26, 2019 at 01:03:16AM +0900, Osamu Aoki wrote:
> > I took no response from my reply is NOT GOOD.  So I reverted
> > undocumented changes here.  No more dependency changes.
> 
> Well, you waited less than 48 hours before deciding that and you hadn't
> removed the moreinfo tag from your original request, so it wasn't back on
> our radar. That isn't very long with the amount of work we currently have
> piling up.

Yes, you are right.  Let me correct my tone of message.

> The dependency changes weren't necessarily a problem, the just needed to be
> understood (particularly with no explanation in the changelog and no
> corresponding bug report, as far as I can see).

As you see in my original reply, I wasn't convinced that these are
absolutely required changes for the package.  Your question was my wake
up call. Given that this isn't my package and this upload was a
salvaging/hijacking kind NMU, I thought it is best to minimize changes
to the extent clearly documented in changelog.

> Unblocked, anyway.

Thanks

I think I need to ask unblock for im-config with many changes to correct
degradation happened in buster testing updates.  I hope we can finish it
before the release.  11 second wait for ssh login is really bad

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925160
  (Current unstable package is not good enough)

Small performance bug get accumulated ... 

Osamu
 

Bug#925615: kernel-package: make-kpkg fails to build latest kernel

[Matteo Croce]

Hi all,

It seems that we have a workaround upstream:

https://git.kernel.org/linus/2b50f7ab6368

Regards,
-- 
Matteo Croce
per aspera ad upstream

Bug#925945: elpa-zzz-to-char: Prompts for text to zap to/up to then gives an Unexpected Style error

[Damon Thomas]

Package: elpa-zzz-to-char
Version: 0.1.3-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation? Normal usage of the package.
   * What exactly did you do (or not do) that was effective (or
 ineffective)? I tried to use both zzz-to-char and zzz-up-to-char and both 
gave the same error.  I could reproduce the error with:

1. emacs -q
2. M-x load-file 
/usr/share/emacs/site-lisp/elpa/zzz-to-char-0.1.3/zzz-to-char.el 
3. M-x zzz-to-char -> Enter Character
4. Unexpected Style X (X being a changing number)
   * What was the outcome of this action?  Unexpected Style Error
   * What outcome did you expect instead?  For text to be "zapped"

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


-- 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/4 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 elpa-zzz-to-char depends on:
ii  elpa-avy0.4.0+git20180322.2d613eb0-1
ii  emacsen-common  3.0.4

Versions of packages elpa-zzz-to-char recommends:
ii  emacs  1:26.1+1-3.2
ii  emacs-gtk [emacs]  1:26.1+1-3.2

elpa-zzz-to-char suggests no packages.

-- no debconf information

Bug#925944: laptop-mode-tools: laptop-mode interferes with NetworkManager

[Soeren D. Schulze]

Package: laptop-mode-tools
Version: 1.72-3
Severity: normal
Tags: ipv6

By default, laptop-mode is configured to control eth0.  However, this
seems to cause eth0 to become active prematurely before NetworkManager
can take control of it.

Excerpt from journalctl:
[...]
Mar 29 00:24:53 ritchie laptop-mode[7040]: enabled, not active
Mar 29 00:24:53 ritchie kernel: r8169 :03:00.0 eth0: Link is Up -
1Gbps/Full - flow control rx/tx
Mar 29 00:24:53 ritchie kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0:
link becomes ready
[...]
Mar 29 00:24:58 ritchie avahi-daemon[597]: Joining mDNS multicast group
on interface eth0.IPv6 with address [...].
Mar 29 00:24:58 ritchie avahi-daemon[597]: New relevant interface
eth0.IPv6 for mDNS.
Mar 29 00:24:58 ritchie avahi-daemon[597]: Network interface enumeration
completed.
Mar 29 00:24:58 ritchie avahi-daemon[597]: Registering new address
record for [...] on eth0.*.
[...]

After that, the device appears managed to NetworkManager, such that it
does not do any IPv4 configuration for it and does not set up
/etc/resolv.conf, either.  As a workaround, I need to either reconnect
eth0 from the NetworkManager GUI after each start-up or remove eth0 from
the devices controlled by laptop-mode.  The role of avahi-daemon in this
scenario is not entirely clear to me.

In newer configurations, this bug will likely not show up due to the new
naming scheme of networking interfaces, but then the primary network
device will not be controlled by laptop-mode, either.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'stable-updates'), (500, 'proposed-updates'), (500, 'testing'), (500,
'stable'), (400, 'unstable')
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 laptop-mode-tools depends on:
ii  lsb-base10.2019031300
ii  psmisc  23.2-1
ii  util-linux  2.33.1-0.1

Versions of packages laptop-mode-tools recommends:
ii  ethtool 1:4.19-1
ii  hdparm  9.58+ds-1
ii  net-tools   1.60+git20180626.aebd88e-1
ii  python3-pyqt5   5.11.3+dfsg-1+b3
ii  rfkill  2.33.1-0.1
ii  sdparm  1.10-1
ii  udev241-1
ii  wireless-tools  30~pre9-13

Versions of packages laptop-mode-tools suggests:
ii  acpid  1:2.0.31-1

-- Configuration Files:
/etc/laptop-mode/conf.d/usb-autosuspend.conf changed [not included]

-- no debconf information

Bug#923347: No sensible security support due to Oracle's policies

[Sandro Tosi]

Hello Moritz,
could you please reply to the points made below? thanks!

On Wed, Feb 27, 2019 at 12:23 AM Sandro Tosi  wrote:

> Hello Moritz,
> i'm not sure what kind of input you're expecting from (if at all, and
> this RC is mostly for the RT), but i'll reply
>
> > mysql-connector-python is affected by Oracle's policy of not disclosing
> > what security fixes they fix.
> >
> > CVE-2019-2435 is labeled with a CVSS 8.1/10 score and only fixed in
> > 8.x, while the version in stretch (2.1.x) is marked as vulnerable,
> > but no 2.1.9 release is available, i.e. we cannot effectively provide
> > a fix within stable only 20 months after stretch was released.
> >
> > This renders mysql-connector-python unsuitable for inclusion in a stable
> > release with security support.
>
> what kind of security support do Debian provide to the mysql server
> packages?
>
> > This leaves us with the following options for buster:
> > - There are no reverse dependencies in buster, remove it from testing
> >   and hope that someone less hostile to the FLOSS community creates a
> >   fork
>
> from a quick look (on unstable):
>
> $ apt-cache rdepends python-mysql.connector
> python-mysql.connector
> Reverse Depends:
>  mysql-utilities
>  mysql-workbench
> $ apt-cache rdepends python3-mysql.connector
> python3-mysql.connector
> Reverse Depends:
>  openlp
>  python3-sql
>
> so some packages, not many, didnt verity if they are in buster atm
>
> > - Aside from the packaged software and given that this is the only Python
> >   binding for mysql/mariadb, there's most definitely a sizable number of
> >   inhouse code using that module. Update src:debian-security-support to
> >   mark mysql-connector-python as unsupported and add a
> README.Debian.security
> >   which also documents this status within the package itself.
>
> i think this is up to the security team to decide, no?
>
> --
> Sandro "morph" Tosi
> My website: http://sandrotosi.me/
> Me at Debian: http://wiki.debian.org/SandroTosi
> G+: https://plus.google.com/u/0/+SandroTosi
>


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#899067: Fixed by patching def loop to def sr_loop

[Roland Hieber]

Control: tag -1 + patch

Thank you, that one helps! Although there are still a lot of
deprecation warnings, but it's working, so I'll ignore that for now :)

 - Roland

On Tue, 12 Mar 2019 14:34:47 +0100 Christian Schiffler 
 wrote:
> Apparently there is now a collision with some other GEM.
> 
> Patched the internal def "loop" to "sr_loop".
> 
> diff attached.
> 
> Hope this helps
> Chris
> 
> 

Bug#925943: nfs-common: nfsiostat crashes due to using reserved word 'list' as variable name

[Matthew Ruffell]

Package: nfs-utils
Version: 1:1.3.4-2.3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch

Dear Maintainer,

nfsiostat, in nfs-common-1.3.4-2, is broken in bionic, cosmic and disco.

When you run the command nfsiostat, either as root or a regular user, the 
following traceback is printed:

$ nfsiostat
Traceback (most recent call last):
  File "/usr/sbin/nfsiostat", line 640, in 
iostat_command(prog)
  File "/usr/sbin/nfsiostat", line 593, in iostat_command
devices = list_nfs_mounts(origdevices, mountstats)
  File "/usr/sbin/nfsiostat", line 495, in list_nfs_mounts
for device, descr in list(mountstats.items()):
TypeError: 'list' object is not callable

This is caused by the 'list' reserved word being used as a variable name in 
list_nfs_mounts(), 
and is explained here: 
https://askubuntu.com/questions/1123319/nfsiostat-failing-on-18-04/1123336#1123336?s=a1e9150fbf284e849efe6fe084e7c7b8

I have sent a patch upstream to fix this, and it was commited in:
http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=c4c14011b70375050d7bba7c57e2eaf4c715dc7c

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

  * nfsiostat-replace-list-reserved-word.patch: fix nfsiostat crash due to
using 'list' as a variable name. (LP: #1821261)

Please land this patch in debian to aid with the SRU process.

Thanks for considering the patch.

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

Kernel: Linux 4.18.0-16-generic (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru nfs-utils-1.3.4/debian/control nfs-utils-1.3.4/debian/control
--- nfs-utils-1.3.4/debian/control  2019-03-26 01:24:29.0 +1300
+++ nfs-utils-1.3.4/debian/control  2019-03-29 11:09:15.0 +1300
@@ -1,8 +1,7 @@
 Source: nfs-utils
 Priority: standard
 Section: net
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Debian kernel team 
+Maintainer: Debian kernel team 
 Uploaders: Anibal Monsalve Salazar , Ben Hutchings 
, Steve Langasek , Daniel Pocock 

 Build-Depends: debhelper (>= 9.20160709), libwrap0-dev, libevent-dev, 
libnfsidmap-dev (>= 0.24), libkrb5-dev, libblkid-dev, libkeyutils-dev, 
pkg-config, libldap2-dev, libcap-dev, libtirpc-dev (>= 1.0.2), 
libdevmapper-dev, dh-autoreconf, libmount-dev, libsqlite3-dev
 Standards-Version: 4.2.1
diff -Nru 
nfs-utils-1.3.4/debian/patches/nfsiostat-replace-list-reserved-word.patch 
nfs-utils-1.3.4/debian/patches/nfsiostat-replace-list-reserved-word.patch
--- nfs-utils-1.3.4/debian/patches/nfsiostat-replace-list-reserved-word.patch   
1970-01-01 12:00:00.0 +1200
+++ nfs-utils-1.3.4/debian/patches/nfsiostat-replace-list-reserved-word.patch   
2019-03-29 11:08:23.0 +1300
@@ -0,0 +1,45 @@
+From c4c14011b70375050d7bba7c57e2eaf4c715dc7c Mon Sep 17 00:00:00 2001
+From: Matthew Ruffell 
+Date: Thu, 28 Mar 2019 15:43:21 -0400
+Subject: [PATCH] nfsiostat: replace 'list' reserved word
+
+list is a reserved word in python and should not be used as a variable
+name. Changing list to devicelist for list_nfs_mounts()
+
+Fixes: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1821261
+
+Signed-off-by: Matthew Ruffell 
+Signed-off-by: Steve Dickson 
+---
+ tools/nfs-iostat/nfs-iostat.py | 8 
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+Index: nfs-utils-1.3.4/tools/nfs-iostat/nfs-iostat.py
+===
+--- nfs-utils-1.3.4.orig/tools/nfs-iostat/nfs-iostat.py
 nfs-utils-1.3.4/tools/nfs-iostat/nfs-iostat.py
+@@ -484,20 +484,20 @@ def list_nfs_mounts(givenlist, mountstat
+return a full list if the given list is empty -
+may return an empty list if none found
+ """
+-list = []
++devicelist = []
+ if len(givenlist) > 0:
+ for device in givenlist:
+ stats = DeviceData()
+ stats.parse_stats(mountstats[device])
+ if stats.is_nfs_mountpoint():
+-list += [device]
++devicelist += [device]
+ else:
+ for device, descr in list(mountstats.items()):
+ stats = DeviceData()
+ stats.parse_stats(descr)
+ if stats.is_nfs_mountpoint():
+-list += [device]
+-return list
++devicelist += [device]
++return devicelist
+ 
+ def iostat_command(name):
+ """iostat-like command for NFS mount points
diff -Nru nfs-utils-1.3.4/debian/patches/series 
nfs-utils-1.3.4/debian/patches/series
--- nfs-utils-1.3.4/debian/patches/series   2019-03-26 01:24:29.0 
+1300
+++ 

Bug#925942: ITP: python-os-ken -- component-based software defined networking framework for OpenStack

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: python-os-ken
  Version : 0.3.1
  Upstream Author : OpenStack Foundation 
* URL : https://github.com/openstack/os-ken
* License : Apache-2.0
  Programming Lang: Python
  Description : component-based software defined networking framework for 
OpenStack

 A component-based software defined networking framework in OpenStack.
 .
 This is a fork of the Ryu library tailored for OpenStack Neutron.

Note: This replaces the Ryu dependency.

Note 2: Somebody upstream must have played too much to Street Fighter in their
childhood. :)

Bug#925932: logtop FTCBFS: does not pass cross tools to make

[Julien Palard]

Hi! Thanks a lot for reporting and providing a patch, appreciated!

Did not touched this packet since 2012, sorry I'm a bit "rusty" about Debian 
packaging...

Found I did not even versionned my debian/ directory, but I found it on my 
server, so I created a branch for this:

https://github.com/JulienPalard/logtop/tree/debian/sid

I applied your patch, but looks like there's still work to do, 
dpkg-buildpackage whines a lot about "dh: Compatibility levels before 9 are 
deprecated (level 7 in use)", looks like time flies!

I do not feel like re-reading the whole maintainer guide tonight to play the 
"find the 7 difference" game between "level 7" and the "current level". But 
don't hesitate to tell me if there's some (simple) steps missing for this cross 
build to pass.

Bests,
-- 
Julien Palard
https://mdk.fr

Bug#925941: nvenc not in ffmpeg

[miltonshane256]

Package: FFMPEG
Version: 4.1.1-1 and others

When running command ffmpeg -codecs nvenc is not showing in h264  or
nvenc_hevc.  This is supported in Debian 9 but not Buster/Testing.

I suggest enabling this duing build as it is a widly used feature along
with vaapi

I am using Debian Linux Buster/Testing with nvidia driver stack in
Testing.

Bug#925940: open-vm-tools 10.3.10 released

[Oliver Kurth]

Package: open-vm-tools
Version: 2:10.3.5-8

We have released open-vm-tools 10.3.10.

open-vm-tools 10.3.10 is available for download from GitHub:

https://github.com/vmware/open-vm-tools/tree/stable-10.3.10

For more details and changes, please refer to the release notes at

https://github.com/vmware/open-vm-tools/blob/stable-10.3.10/ReleaseNotes.md

or the ChangeLog at:

https://github.com/vmware/open-vm-tools/blob/stable-10.3.10/open-vm-tools/ChangeLog

Oliver

Bug#925909: pbgenomicconsensus: autopkgtest regression

[Andreas Tille]

Control: tags -1 pending

Hi,

I commited some changes to Git which are not sufficient yet but
I think I have a clue I can implement in the next 2-3 days.

Thanks for spotting this issue

  Andreas.

-- 
http://fam-tille.de

Bug#925939: jupyter-notebook: CVE-2019-10255: open redirect vulnerability

[Salvatore Bonaccorso]

Source: jupyter-notebook
Version: 5.7.4-2
Severity: important
Tags: patch security upstream

Hi,

The following vulnerability was published for jupyter-notebook.

CVE-2019-10255[0]:
| An Open Redirect vulnerability for all browsers in Jupyter Notebook
| before 5.7.7 and some browsers (Chrome, Firefox) in JupyterHub before
| 0.9.5 allows crafted links to the login page, which will redirect to a
| malicious site after successful login. Servers running on a base_url
| prefix are not affected.


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

For further information see:

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

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#878069: Acknowledgement (lightdm: xdmcp broken)

[Anton Ivanov]

I can no longer observe it for up-to-date stretch clients vs stretch 
server and buster clients versus stretch server.


Both sides are amd64

(the original reported crash was with a 32 bit client which I no longer 
have so cannot re-test).


A.

On 09/10/2017 14:06, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 878069: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878069.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
  Debian Xfce Maintainers 

If you wish to submit further information on this problem, please
send it to 878...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.


--
Anton R. Ivanov
https://www.kot-begemot.co.uk/

Bug#884658: Библии да! Конституции нет! / Bible Yes, Constitution No.

[Afonso Henrique]

ПОКОЛЕНИЕ ИИСУСА ХРИСТА

ПОКОЛЕНИЕ МУЧЕНИЦА
учить умирать
за Иисуса Христа

 
ЭТО МИНИСТЕРСТВО ГОЛОСА ВОССТАНОВЛЕНИЯ, ТОЛЬКО ДВЕРЬ ДЛЯ РАПТУРЫ ЦЕРКВИ:
http://bit.ly/thelastelijah-ru
 
PR. ТУПИРАНИ, ПОСЛЕДНИЙ ЭЛИЯ.
БИБЛИЯ ДА! КОНСТИТУЦИЯ НЕ!
2070: ИИСУС ВОЗВРАЩАЕТСЯ.
МЫ НЕ МАСОНОВ!
 
“Вот, Я пошлю к вам Илию пророка пред наступлением дня Господня, великого и 
страшного." (Малахия 4:5)
 
“Иисус сказал им в ответ: правда, Илия должен придти прежде и устроить всё;" 
(Матфея 17:11)

Bug#864017: release-notes: Assumes /etc/apt/sources.list is used (and not /etc/apt/sources.list.d/*.list or deb822) [general]

[Paul Gevers]

Hi Justin,

Looks good to me, minus one missing ";".

On 28-03-2019 01:16, Justin B Rye wrote:
> +The upgrade process described in this chapter has been designed for
> +pure Debian stable systems. If your APT
configuration mentions
> +additional sources besides , or if you have
installed packages
 ^ there.

If nobody has further comments, I'll commit this version.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#925938: ITP: node-psl -- Domain name parser based on the Public Suffix List

[Utkarsh Gupta]

Package: wnpp
Severity: wishlist
Owner: Utkarsh Gupta 

* Package name : node-psl
  Version  : 1.1.29
  Upstream Author  : Lupo Montero
* URL  : https://github.com/wrangr/psl/
* License  : Expat
  Programming Lang : JavaScript
  Description  : Domain name parser based on the Public Suffix List

 psl is a JavaScript domain name parser based on the Public Suffix List
 (https://publicsuffix.org/). This implementation is tested against the test
 data hosted by Mozilla and kindly provided by Comodo.
 .
 The Public Suffix List is a cross-vendor initiative to provide an accurate
 list of domain name suffixes. A "public suffix" is one under which Internet
 users can directly register names. Some examples of public suffixes are
 ".com", ".co.uk" and "pvt.k12.wy.us". The Public Suffix List is a list of
all
 known public suffixes.


Best,
Utkarsh

Bug#924891: glibc: FTBFS: /<>/build-tree/amd64-libc/conform/UNIX98/ndbm.h/scratch/ndbm.h-test.c:1:10: fatal error: ndbm.h: No such file or directory

[Aurelien Jarno]

Hi Florian,

On 2019-03-27 23:59, Florian Weimer wrote:
> retitle 924891 glibc: misc/tst-pkey fails due to cleared PKRU register after 
> signal in amd64 32-bit compat mode 
> thanks
> 
> * Lucas Nussbaum:
> 
> > On 27/03/19 at 08:48 +0100, Florian Weimer wrote:
> >> > If that's useful, I can easily provide access to an AWS VM to debug this
> >> > issue.
> >> 
> >> Oh, that would be quite helpful indeed.
> >
> > Can you send your SSH key? (I thought there was a way to get the SSH key
> > for a DD, but I cannot find it anymore)
> >
> > Then you will be able to ssh to root@18.184.55.40.
> > There's sbuild and schroot setup on the VM.
> >
> > When you are done, please 'poweroff' the machine, which will terminate
> > it.
> 
> The issue reproduces outside the chroot, with the stretch userland.
> 
> What happens is that once we get out of the SIGUSR1 signal handler,
> the PKRU register has value zero.  This happens around this code in
> the test:
> 
>   /* Check that in a signal handler, there is no access.  */
>   xsignal (SIGUSR1, _handler);
>   xraise (SIGUSR1);
>   xsignal (SIGUSR1, SIG_DFL);
>   TEST_COMPARE (sigusr1_handler_ran, 1);
> 
> I checked the following (via a breakpoint in pkey_get; I don't think
> GDB can read the PKRU register directly): Inside the SIGUSR1 signal
> handler, PKRU has value 0x5554, as expected for this kernel, but
> after the return, we get zero.  This is the first time a signal is
> delivered on the main thread, so it's consistent with fairly broken
> signal handling as far as the PKRU register is concerned.  I guess
> clearing PKRU in this way might even constitute a minor security bug
> (because the zero value means no restrictions).

Thanks a lot for investigating and for all the details.

> This commit looks highly relevant:
> 
> commit a4455082dc6f0b5d51a23523f77600e8ede47c79
> Author: Dave Hansen 
> Date:   Wed Jun 8 10:25:33 2016 -0700
> 
> x86/signals: Add missing signal_compat code for x86 features
> 
> The 32-bit siginfo is a different binary format than the 64-bit
> one.  So, when running 32-bit binaries on 64-bit kernels, we have
> to convert the kernel's 64-bit version to a 32-bit version that
> userspace can grok.
> 
> If the siginfo_t layout is incorrect (with regards to what the
> hardware writes), I expect that we might end up copying back the wrong
> PKRU value.

This commit is actually already in the 4.9 kernel.

> I'm not sure what to do here.  This really looks like a kernel bug.
> Maybe we should just verify that this is fixed in the buster kernel
> and move on?

I agree. I have been able to find a machine where I can temporarily run
a VM. I have found that the problem has been solved between kernel
4.10-rc6 and 4.10, more precisely between the following debian packages:
- linux-image-4.10.0-rc6-amd64-unsigned version 4.10~rc6-1~exp1
- linux-image-4.10.0-trunk-amd64-unsigned version 4.10-1~exp1

I gave a quick look at the commit logs, and I haven't identified a
commit. I'll look again and try to identify the commit fixing the issue
so that it can be backported in the stretch kernel. I'll then reassign
the bug there.

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#925929: tomcat9: /var/log/tomcat9 is owned by tomcat:tomcat instead of tomcat:adm

[Thorsten Glaser]

Emmanuel Bourg dixit:

>It's different from tomcat8, why do you think it is wrong?

Because it’s customary, on Debian, that a user who is member
of the group adm can read logs.

(I’ve not checked whether this is an actual policy or where.)

bye,
//mirabilos
-- 
“ah that reminds me, thanks for the stellar entertainment that you and certain
other people provide on the Debian mailing lists │ sole reason I subscribed to
them (I'm not using Debian anywhere) is the entertainment factor │ Debian does
not strike me as a place for good humour, much less German admin-style humour”

Bug#925928: tomcat9: Error occurred during initialization of VM: Option -XX:+UseG1GC not supported

[Thorsten Glaser]

Emmanuel Bourg dixit:

>I can't reproduce this issue. What JRE did you use? G1 has been
>available since Java 7.

11. Apparently, the option is not available in the Zero VM,
only in Hotspot (didn’t check DCE, JamVM, etc).

But the manpage says that a suitable GC is nowadays picked
automatically anyway, so we don’t lose if we drop this.

Do any release architectures _not_ have Hotspot available?
(mips comes to mind.) If so, this is RC; if not, this can
very well wait until after the release (as you expressed
a desire to not change the config files at the moment).

bye,
//mirabilos
-- 
[...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but
what about xfs, and if only i had waited until reiser4 was ready... in the be-
ginning, there was ffs, and in the middle, there was ffs, and at the end, there
was still ffs, and the sys admins knew it was good. :)  -- Ted Unangst über *fs

Bug#924627: unblock: node-formidable/1.2.1-2

[Xavier]

Please unblock package node-formidable

> node-formidable hasn't been updated for years. Testing version isn't
> compatible with our nodejs but this was not seen since there was no
> real tests (see https://bugs.debian.org/924589).
>
> I upgraded it and added full tests (build and autopkgtest).
>
> node-formidable reverse dependencies:
>  - node-superagent:
>+- node-supertest (no reverse dependencies)
>
> node-formidable bug does not affect these packages since the failing
> functions are not used in it, that's why I decrease bug severity to
> important. I tested the 2 reverse dependencies with both old and new
> node-formidable with success (sbuild and autopkgtest).
>
> debdiff is big since I embedded some node modules (only for tests,
> they are not installed). Upstream changes are not so big. I updated
> also debian/* files and added examples (and tests of course).
>
> I think it's low risky to update node-formidable. However I leave you
> appreciate if it is opportune.


Hi all,

when enabling upstream test in 1.2.1-1, it fails only under debci LXC
environment. After many tries, I fixed this in 1.2.1-2 (was a test loop:
test/run.js tried to test itself). So all tests are OK now. If you think
it is opportune to unblock node-formidable, please unblock version 1.2.1-2

Cheers,
Xavier

Bug#925937: light-locker: makes debian/xfce unusable as server in thin client/X11 environment

[Anton Ivanov]

Package: light-locker
Version: 1.7.0-3
Severity: important

Dear Maintainer,

If the client is non-local (f.e. xterm via xdmcp/lightdm) a lock via
light-locker is "fatal" - there is no means of unlocking besides ssh-ing in
and killing the light-locker.

Suggested - should not run if the DISPLAY has a non-null host part. I ended
up having to wrap it as follows:

#!/bin/sh

TEST=`echo $DISPLAY | sed -e 's/:.*//g'`

if [ -n "$TEST" ] ; then
exit 0
fi

exec /usr/bin/light-locker.real


-- 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-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages light-locker depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
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  libglib2.0-0 2.50.3-2
ii  libgtk-3-0   3.22.11-1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libsystemd0  232-25+deb9u9
ii  libx11-6 2:1.6.4-3+deb9u1
ii  libxext6 2:1.3.3-1+b2
ii  libxss1  1:1.2.2-1
ii  lightdm  1.18.3-1

light-locker recommends no packages.

light-locker suggests no packages.

-- no debconf information

Bug#925935: light-locker: should not run concurrently with xscreensaver

[Anton Ivanov]

Package: light-locker
Version: 1.7.0-3
Severity: important

Dear Maintainer,

At present light-locker is allowed to coexist with xscreensaver at least
in xfce. The results are mostly harmless on a normal machine, but fatal
in a xterm environment. While xscreensaver functions correclty for xterms
light-locker does not. 

These two should not be allowed to coexist, it should be either one or
the other

-- 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-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages light-locker depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
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  libglib2.0-0 2.50.3-2
ii  libgtk-3-0   3.22.11-1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libsystemd0  232-25+deb9u9
ii  libx11-6 2:1.6.4-3+deb9u1
ii  libxext6 2:1.3.3-1+b2
ii  libxss1  1:1.2.2-1
ii  lightdm  1.18.3-1

light-locker recommends no packages.

light-locker suggests no packages.

-- no debconf information

Bug#924892: smartmontools: fails on nvme/Optane: NVMe Status 0x4002

[Christian Franke]

> Read NVMe SMART/Health Information failed: NVMe Status 0x4002

Which device name did you use for smartctl 6.6 ?
If it was '/dev/nvme0n1', please retry with '/dev/nvme0' or 
'/dev/nvme0n1,0x'.


Smartctl 6.6 uses selected namespace to read SMART/Health and Error logs.
Smartctl 7.0 always uses broadcast namespace.

Christian
smartmontools.org

Bug#924876: Fixed

[Xavier]

Hello,

I succeed to fix LXC network problem when following
file.MAINTAINERS.html documentation.
Default LXC configuration file contains:

  lxc.apparmor.profile = generated
  lxc.apparmor.allow_nesting = 1

When removing these 2 lines, all is OK. Could you update
https://ci.debian.net/doc/file.MAINTAINERS.html to explain this ?

Cheers,
Xavier

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

[rajudev]

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

This was a dependency of golang-github-lucasb-eyer-go-colorful as estimated by
dh-make-golang.
https://salsa.debian.org/libregeekingkid-guest/micro/wikis/Dependency-Tree-of-Micro

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.

Bug#901193: Bug#901003: There is no standard way of removing transitional / dummy packages

[Paul Gevers]

Control: tags -1 pending

On 28-03-2019 01:22, vincent.mcint...@csiro.au wrote:
> Works for me.

And for me. So I have locally committed the attached changes which I
will push if no comments appear in the next two days.

Paul
From 6eb5bd59864b26b9b56b1e3b591e9e77cffef374 Mon Sep 17 00:00:00 2001
From: Paul Gevers 
Date: Thu, 28 Mar 2019 21:19:44 +0100
Subject: [PATCH] upgrading.dbk: improve wording around transitional dummy
 packages

Closes: #901193
---
 en/upgrading.dbk | 35 ++-
 1 file changed, 18 insertions(+), 17 deletions(-)

diff --git a/en/upgrading.dbk b/en/upgrading.dbk
index a22924f3..742b2d68 100644
--- a/en/upgrading.dbk
+++ b/en/upgrading.dbk
@@ -1311,24 +1311,25 @@ $ aptitude purge '~c'
   
 
   
-Dummy packages
-
-  Some packages from  have been split into several packages in , often
-  to improve system maintainability.  To ease the upgrade path in such cases,
-   often provides dummy packages: empty packages that have the same name as
-  the old package in  with dependencies that cause the new packages to be
-  installed.  These dummy packages are considered redundant after the
-  upgrade and can be safely removed.
-
-
-  Most (but not all) dummy packages' descriptions indicate their purpose.
-  Package descriptions for dummy packages are not uniform, however, so you might
-  also find deborphan with the
+Transitional dummy packages
+
+  Some packages from  may have been replaced in 
+  by transitional dummy packages, which are empty placeholders designed to
+  simplify upgrades. If for instance an application that was formerly a single
+  package has been split into several, a transitional package may be provided
+  with the same name as the old package and with appropriate dependencies to
+  cause the new ones to be installed. After this has happened the redundant
+  dummy package can be safely removed.
+
+
+  The package descriptions for transitional dummy packages usually indicate
+  their purpose. However, they are not uniform; in particular, some
+  dummy packages are designed to be kept installed, in order
+  to pull in a full software suite, or track the current latest version of
+  some program. You might also find deborphan with the
   --guess-* options (e.g.
-  --guess-dummy) useful to detect them in your system.  Note
-  that some dummy packages are not intended to be removed after an upgrade but
-  are, instead, used to keep track of the current available version of a program
-  over time.
+  --guess-dummy) useful to detect transitional dummy
+  packages on your system.
 
   
 
-- 
2.20.1



signature.asc
Description: OpenPGP digital signature

Bug#798097: Restarting logind kills Xserver

[Michael Biebl]

On Thu, 21 Mar 2019 17:59:26 +0100 Michael Biebl  wrote:
> Hi Julien
> 
> On Thu, 5 Oct 2017 09:39:11 +0200 Julien Cristau 
> wrote:
> > On Sun, Aug 27, 2017 at 13:16:48 +0200, Michael Biebl wrote:
> > 
> > > On Sun, 11 Oct 2015 16:22:24 +0200 Michael Biebl  wrote:
> > > 
> > > > We dropped the logind restart in systemd_226-4 for now and the
> > > > xserver-xorg-core package gained a  Breaks against older systemd 
> > > > versions.
> > > > 
> > > > This is not a real fix yet, but it should be sufficient to not be RC.
> > > > 
> > > > Thus downgrading to important. We still should change both logind and
> > > > Xorg so logind can be restarted safely without wreaking havoc.
> > > 
> > > Upstream logind/systemd has been fixed so it can be restarted safely
> > > now, see https://github.com/systemd/systemd/pull/5600
> > > 
> > > This change is in systemd v234.
> > > I suggest that we ship a patch that reverts [1] and xserver-xorg bumps
> > > the breaks against systemd to << 234.
> > > 
> > I don't want to ship a debian-specific patch for this.  Is there a way
> > for Xorg to detect logind has that bug fix?
> > 
> 
> This patch was merged upstream. See
> https://gitlab.freedesktop.org/xorg/xserver/merge_requests/150
> 
> Would be great if this patch could be applied for buster. This would
> mean I could add the logind to systemd's postinst in buster+1.
> If we don't get this Xorg fix into buster, we'd have to wait another
> full release cycle.
> 
> Julien, in case you are busy, I could offer to NMU.
> WDYT?


Bringing Timo and Andreas into the loop here as well.

Would welcome your thoughts on how to proceed here.

Regards,
Michael

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

Bug#919825: systemd: local filesystems other than '/' and '/usr' not checked and mounted -- emergency mode

[Michael Biebl]

On Wed, 13 Mar 2019 01:10:09 -0500 Bob Tracy  wrote:
> On Tue, Mar 12, 2019 at 12:37:27PM +0100, Michael Biebl wrote:
> > I can't really trawl through the complete config file.
> > What I noticed from the journal are errors like this
> > 
> > Feb 14 04:12:20 smirkin systemd-udevd[435]: sr0: Failed to apply ACL:
> > Operation not supported
> > Feb 14 04:12:31 smirkin systemd-udevd[440]: sg1: Failed to apply ACL:
> > Operation not supported
> > ...
> > 
> > You probably want to enable
> >   CONFIG_TMPFS_XATTR
> >   CONFIG_{TMPFS,EXT4_FS,XFS,BTRFS_FS,...}_POSIX_ACL
> > 
> > If that makes a difference, I dunno.
> 
> Those kernel config parameters are currently designated "optional" in
> the systemd README file, and I'd be really annoyed to find out they
> aren't.  I have no use for the extended attribute and ACL support in a
> non-SELINUX context, but it would not surprise me in the least to find
> out that systemd has some kind of dependency on it.  I'll enable those
> options for my next build.
> 
> > You could try running udev in debug mode (see /etc/udev/udev.conf) and
> > check if you can spot any errors.
> 
> Worth a try.

Any news here, Bob?
Did you have a chance to try a Debian kernel / run udev in debug mode?

-- 
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#925933: mixxx: menu bar goes black after making the software full screen

[Salman Mohammadi]

Package: mixxx
Version: 2.2.0~dfsg-1
Severity: normal

Dear Maintainer,

After making the software full screen, the menu bar goes black and it is
barely visible. Even
after reverting the size, the color does not change to its initial state.


Steps to reproduce:

---
- Press *F11* or click on *View > Full Screen*


-- 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/4 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)
LSM: AppArmor: enabled

Versions of packages mixxx depends on:
ii libc6 2.28-8
ii libchromaprint1 1.4.3-3
ii libebur128-1 1.2.4-2
ii libflac8 1.3.2-3
ii libgcc1 1:8.3.0-2
ii libgl1 1.1.0-1
ii libglib2.0-0 2.58.3-1
ii libhidapi-libusb0 0.8.0~rc1+git20140818.d17db57+dfsg-2
ii libid3tag0 0.15.1b-14
ii liblilv-0-0 0.24.2~dfsg0-2
ii libmad0 0.15.1b-10
ii libogg0 1.3.2-1+b1
ii libopusfile0 0.9+20170913-1
ii libportaudio2 19.6.0-1
ii libportmidi0 1:217-6
ii libprotobuf-lite17 3.6.1.3-1
ii libqt5concurrent5 5.11.3+dfsg1-1
ii libqt5core5a 5.11.3+dfsg1-1
ii libqt5dbus5 5.11.3+dfsg1-1
ii libqt5gui5 5.11.3+dfsg1-1
ii libqt5network5 5.11.3+dfsg1-1
ii libqt5opengl5 5.11.3+dfsg1-1
ii libqt5script5 5.11.3+dfsg-3
ii libqt5scripttools5 5.11.3+dfsg-3
ii libqt5sql5 5.11.3+dfsg1-1
ii libqt5sql5-sqlite 5.11.3+dfsg1-1
ii libqt5svg5 5.11.3-2
ii libqt5widgets5 5.11.3+dfsg1-1
ii libqt5x11extras5 5.11.3-2
ii libqt5xml5 5.11.3+dfsg1-1
ii librubberband2 1.8.1-7
ii libshout3 2.4.1-2
ii libsndfile1 1.0.28-6
ii libsoundtouch1 2.1.2+ds1-1
ii libsqlite3-0 3.27.2-1
ii libstdc++6 8.3.0-2
ii libtag1v5 1.11.1+dfsg.1-0.3
ii libupower-glib3 0.99.10-1
ii libusb-1.0-0 2:1.0.22-2
ii libvorbis0a 1.3.6-2
ii libvorbisenc2 1.3.6-2
ii libvorbisfile3 1.3.6-2
ii libx11-6 2:1.6.7-1
ii mixxx-data 2.2.0~dfsg-1

mixxx recommends no packages.

Versions of packages mixxx suggests:
ii evince [pdf-viewer] 3.30.2-3

-- no debconf information

Bug#925596: irssi-plugin-xmpp: ABI mismatch with irssi 1.2.0-2

[debian]

Hello,

with

echo deb-src http://deb.debian.org/debian buster main 
>/etc/apt/sources.list.d/src-buster.list
sudo apt-get build-dep irssi-plugin-xmpp
mkdir irssi-plugin-xmpp-pkg
cd irssi-plugin-xmpp-pkg
apt-get source irssi-plugin-xmpp
cd irssi-plugin-xmpp-0.54
dpkg-buildpackage -us -uc
sudo dpkg -i ../irssi-plugin-xmpp_0.54-2.1_amd64.deb

you can fix your issue.



Please rebuild package for buster.

Best Regards,
Juri Grabowski


signature.asc
Description: PGP signature

Bug#900397: Possible regression

[Heitor R. Alves de Siqueira]

Hi,

Just FYI, there's a bug in Ubuntu that prevents iscsid to restart
properly due to the ExecStop directive in iscsid.service. This only
happens if iscsid.socket is being used, so making iscsid socket
activated might introduce this bug in Debian.
The fix is to remove ExecStop from the iscsid service and let systemd
handle termination. For more details, refer to LP 1821255 [0].

Thanks,
Heitor

[0] https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1821255

Bug#920545: [Debian-med-packaging] Bug#920545: python-intervaltree breaks python-intervaltree-bio autopkgtest

[Graham Inggs]

Hi Olivier

Paul says a targeted fix for the autopkgtest will be eligible for an unblock.

Regards
Graham

Bug#925553: audacity: segfault in NumericTextCtrl::ValueToControls() ()

[Bernhard Übelacker]

Control: retitle 925553 audacity: with ssh X-forwarding: 
PaAlsaStreamComponent_BeginPolling: Assertion `ret == self->nfds' failed.



Hello Jeff Cliff,
I looked at this backtrace without deeper knowledge of
audacity and the problem might not be a segfault in
mentioned funciton, instead a SIGABRT from pulseaudio.

Instead I guess it is in the first backtrace of yours,
showing in libportaudio.so.2.

By the way, installing the debug symbols [1] would be helpful
for the maintainers to get an idea of where the problem is.
In this case package libportaudio2-dbgsym.

Having audacity running in gdb with an active breakpoint
at PaAlsaStreamComponent_BeginPolling and just continuing
a few times leads to such a backtrace.
(But my "network" connection was just into a VM on the same host.)

Did you also debug audacity or did you let it run freely?
Is your ssh connection over a slow network link?

Should this bug be reassigned to pulseaudio?

Kind regards,
Bernhard


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


(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x73661535 in __GI_abort () at abort.c:79
#2  0x7366140f in __assert_fail_base (fmt=0x7fffe92021d2 "%s%s%s:%u: 
%s%sZusicherung »%s« nicht erfüllt.\n%n", assertion=0x77d7a66e "ret == 
self->nfds", file=0x77d74038 "src/hostapi/alsa/pa_linux_alsa.c", line=3641, 
function=) at assert.c:92
#3  0x7366f0f2 in __GI___assert_fail 
(assertion=assertion@entry=0x77d7a66e "ret == self->nfds", 
file=file@entry=0x77d74038 "src/hostapi/alsa/pa_linux_alsa.c", 
line=line@entry=3641, function=function@entry=0x77d7abe0 
<__PRETTY_FUNCTION__.12102> "PaAlsaStreamComponent_BeginPolling") at 
assert.c:101
#4  0x77d5c1c3 in PaAlsaStreamComponent_BeginPolling (pfds=, self=) at src/hostapi/alsa/pa_linux_alsa.c:3641
#5  0x77d69e85 in PaAlsaStreamComponent_BeginPolling (pfds=, self=) at src/hostapi/alsa/pa_linux_alsa.c:3931
#6  PaAlsaStream_WaitForFrames (self=self@entry=0x56867c00, 
framesAvail=framesAvail@entry=0x7fffe8007720, 
xrunOccurred=xrunOccurred@entry=0x7fffe800771c) at 
src/hostapi/alsa/pa_linux_alsa.c:3802
#7  0x77d6a63e in CallbackThreadFunc (userData=0x56867c00) at 
src/hostapi/alsa/pa_linux_alsa.c:4274
#8  0x73b34fa3 in start_thread (arg=) at 
pthread_create.c:486
#9  0x7373882f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

# Buster amd64 qemu VM 2019-03-28

apt update
apt dist-upgrade





apt install dpkg-dev devscripts systemd-coredump alsa-utils audacity pulseaudio 
libportaudio2-dbgsym gdb elfutils elfutils-dbgsym libelf1-dbgsym strace 
binutils mc


$ ssh -X -p benutzer@$LOCALIP
benutzer@debian:~$ audacity
-> record -> no crash -> cursor is moving as usual


##


cp -a /usr/lib/x86_64-linux-gnu/libportaudio.so.2.0.0 /tmp/libportaudio.so.2.0.0
cp -a /usr/lib/debug/.build-id/4d/7ecbcc022ad848e4da5356dfeaf76b5230731d.debug 
/tmp/7ecbcc022ad848e4da5356dfeaf76b5230731d.debug
LANG=C eu-unstrip --force /tmp/libportaudio.so.2.0.0 
/tmp/7ecbcc022ad848e4da5356dfeaf76b5230731d.debug
eu-unstrip: cannot write output file: invalid section alignment
# Doh!

mkdir /home/benutzer/source/elfutils/orig -p
cd/home/benutzer/source/elfutils/orig
apt source elfutils
cd

mkdir /home/benutzer/source/libc6/orig -p
cd/home/benutzer/source/libc6/orig
apt source libc6
cd

grep "invalid section alignment" . -rn

grep "ELF_E_INVALID_SHENTSIZE_IDX" . -rn

grep "ELF_E_INVALID_SHENTSIZE" . -rn

gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'directory 
/home/benutzer/source/elfutils/orig/elfutils-0.176/libelf' -ex 'b 
elf32_updatenull.c:399' -ex 'run' --args eu-unstrip --force 
/tmp/libportaudio.so.2.0.0 /tmp/7ecbcc022ad848e4da5356dfeaf76b5230731d.debug

(gdb) bt
#0  __libelf_seterrno (value=value@entry=36) at elf_error.c:336
#1  0x77fb3f7a in __elf64_updatenull_wrlock 
(elf=elf@entry=0x55564f30, change_bop=change_bop@entry=0x7fffd2ec, 
shnum=shnum@entry=35) at elf32_updatenull.c:215
#2  0x77fb2fb0 in elf_update (elf=0x55564f30, cmd=ELF_C_WRITE) at 
elf_update.c:209
#3  0xbb67 in copy_elided_sections (unstripped=, 
stripped=, stripped_ehdr=, bias=) 
at unstrip.c:2070
#4  0xc1a3 in handle_file (output_file=0x0, create_dirs=, stripped=0x55563900, stripped_ehdr=0x7fffe200, 
unstripped=0x55564f30) at unstrip.c:2132
#5  0xc3b9 in handle_explicit_files (output_file=0x0, 
create_dirs=, force=) at unstrip.c:2223
#6  0x6c81 in main (argc=, argv=0x7fffe558) at 
unstrip.c:2558

1: x/i $pc
=> 0x77faa520 <__libelf_seterrno>:  push   %rbx


##




mkdir /home/benutzer/source/libportaudio2/orig -p
cd/home/benutzer/source/libportaudio2/orig
apt source libportaudio2
cd




script -c "gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'b main' -ex 
'run' --args audacity" -a gdb-dissassemble_$(date 

Bug#925932: logtop FTCBFS: does not pass cross tools to make

[Helmut Grohne]

Source: logtop
Version: 0.4.3-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

logtop fails to cross build from source, because it does not pass cross
tools to make. The easiest way of fixing that - using dh_auto_build -
makes logtop cross buildable. Please consider applying the attached
patch.

Helmut
diff --minimal -Nru logtop-0.4.3/debian/changelog logtop-0.4.3/debian/changelog
--- logtop-0.4.3/debian/changelog   2012-06-05 22:39:38.0 +0200
+++ logtop-0.4.3/debian/changelog   2019-03-28 19:22:57.0 +0100
@@ -1,3 +1,10 @@
+logtop (0.4.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 28 Mar 2019 19:22:57 +0100
+
 logtop (0.4.3-1) unstable; urgency=low
 
   * New Support LDFLAGS in Makefile
diff --minimal -Nru logtop-0.4.3/debian/rules logtop-0.4.3/debian/rules
--- logtop-0.4.3/debian/rules   2012-05-28 13:26:36.0 +0200
+++ logtop-0.4.3/debian/rules   2019-03-28 19:22:56.0 +0100
@@ -5,7 +5,7 @@
 include /usr/share/dpkg/buildflags.mk
 
 override_dh_auto_build:
-   $(MAKE) CFLAGS="$(CFLAGS) -D_FORTIFY_SOURCE=2" LDFLAGS="$(LDFLAGS)"
+   dh_auto_build -- CFLAGS="$(CFLAGS) -D_FORTIFY_SOURCE=2" 
LDFLAGS="$(LDFLAGS)"
 
 %:
dh $@

Bug#925701: gnutls28: ftbfs with GCC-9

[Andreas Metzler]

On 2019-03-27 Matthias Klose  wrote:
> Package: src:gnutls28
> Version: 3.6.6-3
> Severity: normal
> Tags: sid bullseye
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-9
[...]
> GCC 9 also passes the linker option --as-needed by default; typical
> build issues are passing libraries before object files to the linker,
> or underlinking of convenience libraries built from the same source.
[...]
> /usr/bin/ld: cipher-openssl-compat.o: in function `doit':
> ./b4deb/tests/slow/../../../tests/slow/cipher-openssl-compat.c:194: undefined 
> reference to `OPENSSL_init_crypto'

Seems to be fixed by 
---
--- gnutls28-3.6.7.orig/tests/slow/Makefile.am
+++ gnutls28-3.6.7/tests/slow/Makefile.am
@@ -53,7 +53,7 @@ check_PROGRAMS = $(ctests) cipher-test c
 TESTS = $(ctests) test-ciphers.sh override-ciphers test-hash-large.sh crypto 
test-ciphers-api.sh
 
 if HAVE_LIBCRYPTO
-cipher_openssl_compat_LDFLAGS = $(LDADD) $(LIBCRYPTO)
+cipher_openssl_compat_LDADD = $(LDADD) $(LIBCRYPTO)
 
 dist_check_SCRIPTS += test-ciphers-openssl.sh
 check_PROGRAMS += cipher-openssl-compat
---
cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#925931: ITP: q2-types -- QIIME 2 plugin defining types for microbiome analysis

[Liubov Chuprikova]

Package: wnpp
Owner: Liubov Chuprikova 
Severity: wishlist

* Package name: q2-types
  Version : 2019.1.0
  Upstream Author : QIIME 2 development team
* URL : https://qiime2.org/
* License : BSD-3-clause
  Programming Lang: Python
  Description : QIIME 2 plugin defining types for microbiome analysis
 QIIME 2 is a powerful, extensible, and decentralized microbiome analysis
 package with a focus on data and analysis transparency. QIIME 2 enables
 researchers to start an analysis with raw DNA sequence data and finish with
 publication-quality figures and statistical results.
 Key features:
  * Integrated and automatic tracking of data provenance
  * Semantic type system
  * Plugin system for extending microbiome analysis functionality
  * Support for multiple types of user interfaces (e.g. API, command line,
 graphical)
 .
 QIIME 2 is a complete redesign and rewrite of the QIIME 1 microbiome
analysis
 pipeline. QIIME 2 will address many of the limitations of QIIME 1, while
 retaining the features that makes QIIME 1 a powerful and widely-used
analysis
 pipeline.
 .
 QIIME 2 currently supports an initial end-to-end microbiome analysis
pipeline.
 New functionality will regularly become available through QIIME 2 plugins.
You
 can view a list of plugins that are currently available on the QIIME 2
plugin
 availability page. The future plugins page lists plugins that are being
 developed.

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/q2-types

Bug#925930: fprintd: Elan fingerprint reader is not detected

[Lorenzo Ancora]

Package: fprintd
Version: 0.8.1-1
Severity: important

The fprintd daemon is running and the PAM subsystem is configured with its 
authentication module, but the dongle of Elan Microelectronics Corp. with ID 
04f3: 0c28 is not detected, with the consequence that the enrollment of the 
digital crests is impossible.
Even loading PAM fprintd with "auth sufficient pam_fprintd.so" before PAM UNIX 
fingerprint authentication has no effect, as if the dongle was not connected. 
The system acts as if it had no drivers but the dongle is working when 
compiling libfprint manually: this dongle is supported on GNU/Linux systems via 
libfprint and natively allows 360° finger authentication, I've tested it in a 
separate subdirectory with the included sample programs (it produces valid 
images of the digital crests and recognizes the saved crests).

Could you make the dongle be recognized?

Thank you,
Lorenzo

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

Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fprintd depends on:
ii  dbus   1.10.26-0+deb9u1
ii  libc6  2.27-3
ii  libdbus-1-31.10.26-0+deb9u1
ii  libdbus-glib-1-2   0.108-2
ii  libfprint0 1:0.8.2-3
ii  libglib2.0-0   2.50.3-2
ii  libpolkit-gobject-1-0  0.105-18+deb9u1
ii  policykit-10.105-18+deb9u1

fprintd recommends no packages.

fprintd suggests no packages.

-- no debconf information

Bug#925524: init-system-helpers: Please provide a stretch backport for debhelper 12~

[Niels Thykier]

wf...@niif.hu:
> Niels Thykier  writes:
> 
>> I don't think I have much to add to it really beyond what is covered in
>> https://nthykier.wordpress.com/2019/01/04/debhelper-compat-12-is-now-released/
> 
> Thanks for the good writeup, I missed it.
> 

:)

>> Sure it would be great to have one less caveat for upgrating to compat
>> 12.  But mostly release compat 12 before buster was to ensure people
>> could assume compat 12 was present in buster (and less about stretch).
> 
> I see.  I was forced to compat 12 by #887904 for shibboleth-sp back in
> August, and now we try to backport it to stretch.  Working around
> #887904 on compat 11 does not seem a simple exercise for me, that's why
> I decided to pursue an init-system-helpers backport.  Please correct me
> if I overlook something.
> 

Right.  I aimed for making compat 12 in buster painless.  Possibly
compat 11 should be deprecated aggressively because it is "broken" for
services (asking people to choose compat 10 or 12 instead as appropriate).

>> Related note (with my RT hat on): Please defer debhelper compat bumps
>> for anything targeting buster as it is not considered a "minimal change".
> 
> I didn't even think of such things. :)  However, now that you reminded
> me, I've got a tricky minimal change for your RT hat, let me put that
> forward as well...
> 

:)

Thanks,
~Niels

Bug#925524: init-system-helpers: Please provide a stretch backport for debhelper 12~

[Niels Thykier]

Etienne Dysli Metref:
> On 27/03/2019 21.12, Niels Thykier wrote:
>> I don't think I have much to add to it really beyond what is 
>> covered in https://nthykier.wordpress.com/2019/01/04/ 
>> debhelper-compat-12-is-now-released/
> 
> 
> Hi Niels,
> 
> Thank you for your explanation. One point, however, isn't completely
> clear to me: does that
> 
>> Caveat for stretch-backports support: Due to the above, we need a 
>> versioned Pre-Depends on init-system-helpers.  That version is 
>> unfortunately not available in stretch nor stretch-backports and 
>> therefore packages relying on this cannot be safely backported to 
>> stretch (but they will be backportable to buster).
> 
> mean init-system-helpers 1.56 should not be backported to stretch?
> 
> Cheers,
>   Etienne
> 

I made no assertions abot whether init-system-helpers should or should
be backported to stretch.  If someone does it, great - it is easier for
people that want to use backports.  If no-one does backports
init-system-helpers, then we remain at the status quo (e.g. mentioned in
my blog post).

Thanks,
~Niels

Bug#925928: tomcat9: Error occurred during initialization of VM: Option -XX:+UseG1GC not supported

[Emmanuel Bourg]

Le 28/03/2019 à 18:31, Thorsten Glaser a écrit :

> tomcat9 does not start at all:
> 
> […]
> NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
> Error occurred during initialization of VM
> Option -XX:+UseG1GC not supported

I can't reproduce this issue. What JRE did you use? G1 has been
available since Java 7.

Emmanuel Bourg

Bug#925524: init-system-helpers: Please provide a stretch backport for debhelper 12~

[Michael Biebl]

Am 28.03.19 um 11:08 schrieb wf...@niif.hu:
> Felipe Sateler  writes:
> 
>> I'm not opposed to a backport, and I don't think there are many
>> problems with attempting it. However, I do not have time to prepare
>> and test such a backport. Help welcome.
> 
> I can do the busy-work of backporting, but I lack the perspective to
> tell whether it's feasible now or in the long run.  Looking at the
> changelog it feels safe to install 1.56 on a stretch system, and this
> close to the release I wouldn't expect anything to come up before
> stretch-backports closes, though...
> 

Personally I prefer to revert the compat bumps when doing backports for
stretch (like in [1]) as I like to to keep the impact on the stable
system as minimal as possible. Pulling in a newer i-s-h is a rather
significant change. Thankfully not as significant as we had between
jessie → stretch. So a backport of i-s-h might indeed be feasible on a
cursory glance.

Regards,
Michael


[1]
https://salsa.debian.org/debian/rsyslog/commit/6bd5a7915e826650750e5864e035edb1f4d2e31a
-- 
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#925919: linux-image-amd64: linux-image-3.16.0-8-amd64 - unpredictable reboots / kernel panics?

[Emanuel Kocher]

Hi Werner

Same problem here. It looks like a combination of Debian 8 with Kernel 
3.16.0-8. We have around 25 servers having had this combo and at least 9 
servers failing randomly today with:
- kernel panic
- XFS filesystem corruption (Metadata corruption detected / Corrruption 
of in-memory data detected. Shutting down filesystem)

Unfortunately I cannot provide a nice text as the crash is not logged

We also downgraded all servers and are hoping for a fast fix as we put 
those packages on hold.

Kind regards
Emanuel

Bug#925817: rawtherapee: ftbfs with GCC-9

[Philip Rinn]

Control: tags -1 fixed-upstream

Hi,

thanks for pointing this out.
It's already fixed upstream: https://github.com/Beep6581/RawTherapee/issues/5177

I'll upload a fixed version after buster is released.

Best,
Philip




signature.asc
Description: OpenPGP digital signature

Bug#925929: tomcat9: /var/log/tomcat9 is owned by tomcat:tomcat instead of tomcat:adm

[Emmanuel Bourg]

Le 28/03/2019 à 18:37, Thorsten Glaser a écrit :

> commit aeff1188eaab8dbe99bb1fec62472d9c2ff1d876 changed the way
> the log directory was created, and (probably a pasto) uses the
> wrong ownership.

It's different from tomcat8, why do you think it is wrong?

Emmanuel Bourg

Bug#684134: Mensagem do administrador

[Atendimento IEL]

Prezado usuário de email,

Sua caixa de correio excedeu seu limite de armazenamento.
CLIQUE AQUI PARA DESBLOQUEAR,
Preencha e clique em ENVIAR para mais espaço ou você não poderá enviar e-mails.

Bug#925929: tomcat9: /var/log/tomcat9 is owned by tomcat:tomcat instead of tomcat:adm and not setgid

[Thorsten Glaser]

retitle 925929 tomcat9: /var/log/tomcat9 is owned by tomcat:tomcat instead of 
tomcat:adm and not setgid
thanks

On Thu, 28 Mar 2019, Thorsten Glaser wrote:

> commit aeff1188eaab8dbe99bb1fec62472d9c2ff1d876 changed the way
> the log directory was created, and (probably a pasto) uses the
> wrong ownership.

Furthermore, /var/log/tomcat9 should be chmod 2750 not 750
so that the logfiles are accessible by the adm group, as
Debian commonplace.

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

*

**!!! NEU !!!** Mit der **tarent Academy** bieten wir ab sofort auch Trainings
und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und
Zukunftstechnologien an. Besuchen Sie uns
auf [www.tarent.de/academy](http://www.tarent.de/academy). Wir freuen uns auf
Ihren Kontakt.

*

Bug#925929: tomcat9: /var/log/tomcat9 is owned by tomcat:tomcat instead of tomcat:adm

[Thorsten Glaser]

Package: tomcat9
Version: 9.0.16-3
Severity: important

commit aeff1188eaab8dbe99bb1fec62472d9c2ff1d876 changed the way
the log directory was created, and (probably a pasto) uses the
wrong ownership.

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

Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages tomcat9 depends on:
ii  adduser 3.118
ii  lsb-base10.2019031300
ii  tomcat9-common  9.0.16-4
ii  ucf 3.0038+nmu1

Versions of packages tomcat9 recommends:
ii  libtcnative-1  1.2.21-1

Versions of packages tomcat9 suggests:
pn  tomcat9-admin 
pn  tomcat9-docs  
pn  tomcat9-examples  
pn  tomcat9-user  

-- Configuration Files:
/etc/tomcat9/policy.d/01system.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/01system.policy'
/etc/tomcat9/policy.d/02debian.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/02debian.policy'
/etc/tomcat9/policy.d/03catalina.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/03catalina.policy'
/etc/tomcat9/policy.d/04webapps.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/04webapps.policy'
/etc/tomcat9/policy.d/50local.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/50local.policy'

-- no debconf information

Bug#925927: libgmp10:amd64: failure with Clang's memory sanitizer: use-of-uninitialized-value

[Vincent Lefevre]

Control: tags -1 upstream
Control: forwarded -1 
https://gmplib.org/list-archives/gmp-bugs/2019-March/004525.html

I also reported the bug upstream.

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

Bug#925928: tomcat9: Error occurred during initialization of VM: Option -XX:+UseG1GC not supported

[Thorsten Glaser]

Package: tomcat9
Version: 9.0.16-3
Severity: important

tomcat9 does not start at all:

[…]
NOTE: Picked up JDK_JAVA_OPTIONS:  --add-opens=java.base/java.lang=ALL-UNNAMED 
--add-opens=java.base/java.io=ALL-UNNAMED 
--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
Error occurred during initialization of VM
Option -XX:+UseG1GC not supported

This is because of this:

tglase@tglase:~/tomcat9 $ git grep UseG1GC
debian/default.template:# options will be: -Djava.awt.headless=true -XX:+UseG1GC
debian/default.template:JAVA_OPTS="-Djava.awt.headless=true -XX:+UseG1GC"
debian/setenv.sh:   JAVA_OPTS="-Djava.awt.headless=true -XX:+UseG1GC"


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

Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages tomcat9 depends on:
ii  adduser 3.118
ii  lsb-base10.2019031300
ii  tomcat9-common  9.0.16-4
ii  ucf 3.0038+nmu1

Versions of packages tomcat9 recommends:
ii  libtcnative-1  1.2.21-1

Versions of packages tomcat9 suggests:
pn  tomcat9-admin 
pn  tomcat9-docs  
pn  tomcat9-examples  
pn  tomcat9-user  

-- Configuration Files:
/etc/tomcat9/policy.d/01system.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/01system.policy'
/etc/tomcat9/policy.d/02debian.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/02debian.policy'
/etc/tomcat9/policy.d/03catalina.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/03catalina.policy'
/etc/tomcat9/policy.d/04webapps.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/04webapps.policy'
/etc/tomcat9/policy.d/50local.policy [Errno 13] Permission denied: 
'/etc/tomcat9/policy.d/50local.policy'

-- no debconf information

Bug#925927: libgmp10:amd64: failure with Clang's memory sanitizer: use-of-uninitialized-value

[Vincent Lefevre]

Package: libgmp10
Version: 2:6.1.2+dfsg-4
Severity: important

The following program

#include 

int main (void)
{
  mpz_t z;

  mpz_init (z);
  mpz_set_ui (z, 1);
  mpz_dump (z);
  mpz_clear (z);

  return 0;
}

compiled with: clang-7 -fsanitize=memory -o tst tst.c -lgmp

gives the following error:

cventin:~> ./tst
Uninitialized bytes in __interceptor_puts at offset 1 inside [0x70100010, 2)
==17647==WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0x7fbf03e6fe6a in __gmpz_dump 
(/usr/lib/x86_64-linux-gnu/libgmp.so.10+0x18e6a)
#1 0x49518a in main (/home/vlefevre/tst+0x49518a)
#2 0x7fbf03aeb09a in __libc_start_main 
(/lib/x86_64-linux-gnu/libc.so.6+0x2409a)
#3 0x41e2b9 in _start (/home/vlefevre/tst+0x41e2b9)

SUMMARY: MemorySanitizer: use-of-uninitialized-value 
(/usr/lib/x86_64-linux-gnu/libgmp.so.10+0x18e6a) in __gmpz_dump
Exiting
zsh: exit 77./tst

In particular, this failure prevents one from using -fsanitize=memory
with software that uses GMP.

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

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

Versions of packages libgmp10:amd64 depends on:
ii  libc6  2.28-8

libgmp10:amd64 recommends no packages.

libgmp10:amd64 suggests no packages.

-- no debconf information

Bug#925914: libzmq5: GSSAPI support not available anymore

[GCS]

Hi Luca,

On Thu, Mar 28, 2019 at 12:51 PM Luca Boccassi  wrote:
> GSSAPI support is no longer built in in the version in buster/sid.
>
> This is due to my mistake upstream when refactoring the autoconf file -
> the correct autoconf variable does not get set when using pkg-config to
> find the gssapi library.
[...]
> The fix is simple, is already merged upstream and is also attached.
 Applied to the package and upload is pending. Thanks for the detailed
analysis and the fix.

> Given this is a regression since stretch, it would be great if we could
> get this uploaded and approved for buster.
>
> I'm more than happy to deal with the paperwork and file a request with
> the Release Team myself, given it was my mistake.
 Well, I can ask for the unblock, but probably will reference you in it.

Cheers,
Laszlo/GCS

Bug#925353: [Pkg-linaro-lava-devel] Bug#925353: lava-server: logrotate complains about "parent directory has insecure permissions"

[Andreas Beckmann]

On 2019-03-28 17:31, Steve McIntyre wrote:
> I'm a little bit at a loss to see what's causing it... :-/

I tried to normalize the logs (remove timestamps, tmpdir and everything
before the dist-upgrade to buster) and then diff them to find this:

@@ -6631,10 +6227,9 @@
  INFO: Package lava-server contains logrotate file: 
/etc/logrotate.d/lava-master-log
  INFO: Package lava-server contains logrotate file: 
/etc/logrotate.d/lava-publisher-log
  INFO: Package lava-server contains logrotate file: 
/etc/logrotate.d/lava-server-gunicorn-log
- INFO: Package lava-server contains logrotate file: 
/etc/logrotate.d/lava-server-uwsgi-log
  DEBUG: Starting command: ['chroot', '<>', 'dpkg-query', '-W', '-f', 
'${Status}\\t${binary:Package}\\t${Package}\\t${Version}\\n']

and further up:

@@ -5953,11 +5600,6 @@
  DEBUG: Command ok: ['adequate', '--root', '<>', 'lava-server']
  ERROR: WARN: Inadequate results from running adequate!
   lava-server: broken-symlink /usr/share/lava-server/static/docs -> 
../../doc/lava-server-doc/html
-  lava-server: obsolete-conffile /etc/logrotate.d/lava-server-uwsgi-log
-  lava-server: obsolete-conffile /etc/lava-server/lava-server.wsgi
-  lava-server: obsolete-conffile /etc/lava-server/debug.wsgi
-  lava-server: obsolete-conffile /etc/lava-server/uwsgi.ini
-  lava-server: obsolete-conffile /etc/lava-server/uwsgi.reload
   lava-server: obsolete-conffile /etc/logrotate.d/lava-scheduler-log
   lava-server: obsolete-conffile /etc/lava-server/lava-server-gunicorn.service
   lava-server: obsolete-conffile 
/etc/lava-server/dispatcher-config/device-types/nxp-k64f.jinja2
@@ -5975,11 +5617,6 @@
  DEBUG: Command ok: ['chroot', '<>', 
'tmp/scripts/pre_remove_40_find_missing_md5sums']
  DEBUG: Starting command: ['chroot', '<>', 
'tmp/scripts/pre_remove_40_find_obsolete_conffiles']
  DUMP:
-  OBSOLETE CONFFILE /etc/logrotate.d/lava-server-uwsgi-log REGISTERED BY 
lava-server
-  OBSOLETE CONFFILE /etc/lava-server/lava-server.wsgi REGISTERED BY lava-server
-  OBSOLETE CONFFILE /etc/lava-server/debug.wsgi REGISTERED BY lava-server
-  OBSOLETE CONFFILE /etc/lava-server/uwsgi.ini REGISTERED BY lava-server
-  OBSOLETE CONFFILE /etc/lava-server/uwsgi.reload REGISTERED BY lava-server
   OBSOLETE CONFFILE /etc/logrotate.d/lava-scheduler-log REGISTERED BY 
lava-server (MISSING)
   OBSOLETE CONFFILE /etc/lava-server/lava-server-gunicorn.service REGISTERED 
BY lava-server
   OBSOLETE CONFFILE 
/etc/lava-server/dispatcher-config/device-types/nxp-k64f.jinja2 REGISTERED BY 
lava-server

So you have a lot of conffile cruft stemming from both jessie and stretch ...
debian/lava-server.maintscript will be your friend :-)

We have the data already:
https://piuparts.debian.org/stretch2buster/obsolete_conffiles_issue.html
Someone needs to start filing bugs ... obsolete conffiles will bite you in the 
future :-)

Andreas

Bug#925924: unblock: dovecot/2.3.4.1-3

[Apollon Oikonomopoulos]

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

Please unblock package dovecot.

2.3.4.1-3, which was uploaded to unstable today, fixes two cases of 
buffer overflows (collectively known as CVE-2019-7524). Please allow it 
to migrate to testing as soon as possible. Full source debdiff against 
testing attached.

Thanks,
Apollon

unblock dovecot/2.3.4.1-3
diff -Nru dovecot-2.3.4.1/debian/changelog dovecot-2.3.4.1/debian/changelog
--- dovecot-2.3.4.1/debian/changelog2019-03-14 11:02:39.0 +0200
+++ dovecot-2.3.4.1/debian/changelog2019-03-25 23:06:01.0 +0200
@@ -1,3 +1,10 @@
+dovecot (1:2.3.4.1-3) unstable; urgency=high
+
+  * [07c9212] Fix two buffer overflows when reading oversized FTS headers
+and/or oversized POP3-UIDL headers (CVE-2019-7524).
+
+ -- Apollon Oikonomopoulos   Mon, 25 Mar 2019 23:06:01 
+0200
+
 dovecot (1:2.3.4.1-2) unstable; urgency=medium
 
   [ Laurent Bigonville ]
diff -Nru dovecot-2.3.4.1/debian/patches/CVE-2019-7524 
dovecot-2.3.4.1/debian/patches/CVE-2019-7524
--- dovecot-2.3.4.1/debian/patches/CVE-2019-75241970-01-01 
02:00:00.0 +0200
+++ dovecot-2.3.4.1/debian/patches/CVE-2019-75242019-03-25 
23:06:01.0 +0200
@@ -0,0 +1,59 @@
+From 2d31f0e08a80217c039be4aaae8de25bed0251f4 Mon Sep 17 00:00:00 2001
+From: Apollon Oikonomopoulos 
+Date: Mon, 25 Mar 2019 23:04:44 +0200
+Subject: [PATCH] Fix CVE-2019-7524
+
+commit ad1350ff036965c33f0aae20432ec73ca84f7819
+Author: Timo Sirainen 
+Date:   Mon Feb 4 19:25:13 2019 -0800
+
+fts: Fix buffer overflow when reading oversized fts header
+
+commit 89e05f17de80e19078544ef887d83d160491214e
+Author: Timo Sirainen 
+Date:   Mon Feb 4 19:23:02 2019 -0800
+
+lib-storage: Fix buffer overflow when reading oversized hdr-pop3-uidl 
header
+---
+ src/lib-storage/index/index-pop3-uidl.c | 4 ++--
+ src/plugins/fts/fts-api.c   | 2 +-
+ 2 files changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/src/lib-storage/index/index-pop3-uidl.c 
b/src/lib-storage/index/index-pop3-uidl.c
+index 13b7363ef..e537e9ff5 100644
+--- a/src/lib-storage/index/index-pop3-uidl.c
 b/src/lib-storage/index/index-pop3-uidl.c
+@@ -37,7 +37,7 @@ bool index_pop3_uidl_can_exist(struct mail *mail)
+   /* this header isn't set yet */
+   return TRUE;
+   }
+-  memcpy(, data, size);
++  memcpy(, data, sizeof(uidl));
+   return mail->uid <= uidl.max_uid_with_pop3_uidl;
+ }
+ 
+@@ -95,7 +95,7 @@ void index_pop3_uidl_update_exists_finish(struct 
mailbox_transaction_context *tr
+ 
+   /* check if we have already the same header */
+   if (size >= sizeof(uidl)) {
+-  memcpy(, data, size);
++  memcpy(, data, sizeof(uidl));
+   if (trans->highest_pop3_uidl_uid == uidl.max_uid_with_pop3_uidl)
+   return;
+   }
+diff --git a/src/plugins/fts/fts-api.c b/src/plugins/fts/fts-api.c
+index 5a5b2a919..4f8a1c125 100644
+--- a/src/plugins/fts/fts-api.c
 b/src/plugins/fts/fts-api.c
+@@ -425,7 +425,7 @@ bool fts_index_get_header(struct mailbox *box, struct 
fts_index_header *hdr_r)
+   i_zero(hdr_r);
+   ret = FALSE;
+   } else {
+-  memcpy(hdr_r, data, data_size);
++  memcpy(hdr_r, data, sizeof(*hdr_r));
+   ret = TRUE;
+   }
+   mail_index_view_close();
+-- 
+2.20.1
+
diff -Nru dovecot-2.3.4.1/debian/patches/series 
dovecot-2.3.4.1/debian/patches/series
--- dovecot-2.3.4.1/debian/patches/series   2019-03-14 11:02:39.0 
+0200
+++ dovecot-2.3.4.1/debian/patches/series   2019-03-25 23:06:01.0 
+0200
@@ -9,4 +9,5 @@
 ssl-dh-params-location.patch
 lib-master-test-event-stats-Use-PRIu64-format.patch
 avoid-double-closing-mysql.patch
+CVE-2019-7524
 debian-changes

Bug#750731: FastAC license issue (Was: laszip)

[Sebastiaan Couwenberg]

Control: owner -1 !

On Tue, 26 Mar 2019 15:19:51 +0100 Gürkan Myczko wrote:
> I have a working package as in, you can build this from debian source 
> package:
> http://phd-sid.ethz.ch/debian/laszip/

The team maintained packaging is available on Salsa:

 https://salsa.debian.org/debian-gis-team/laszip

Regarding the FastAC license issue, to quote the upstream issue [0]:

"
 Thanks for Tom "spot" Callaway of RedHat for Fedora Legal, the FastAC
 authors have agreed to relicense their code under the BSD-2-Clause
 license, see the attachments in the Bugzilla issue:

  LASzip contains FastAC code which does not allow modification
  https://bugzilla.redhat.com/show_bug.cgi?id=1674537

 Direct links:

  * BSD_Relicense_of_FastAC_code.pdf
https://bugzilla.redhat.com/attachment.cgi?id=1549115
Contains the email thread between Tom Callaway, Amir Said &
William (Bill) Pearlman
  * new-fastac-header.txt
https://bugzilla.redhat.com/attachment.cgi?id=1549116)
The updated license header for the FastAC code

 There is no new release of the FastAC code yet, once that's available
 the license issue preventing distributions from distributing LASzip
 should be resolved.
"

[0] https://github.com/LASzip/LASzip/issues/55

Kind Regards,

Bas

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

Bug#925320: [Android-tools-devel] Bug#925320: Acknowledgement (android-platform-tools-apksig: apksigner fails to run on OpenJDK 8 due to UnsupportedClassVersionError)

[Tiago Daitx]

On Thu, Mar 28, 2019 at 7:24 AM Hans-Christoph Steiner  wrote:
>
>
> The "--release 8" fix seems fine, my only concern is that someone needs
> to test this, since it is different than what upstream does.  I suppose
> that the autopkgtest is complete enough to test this.  I'm not really
> aware of whether there are security concerns of compiling with different
> source/target/release versions.  Do you know?
>
> .hc

I am also not aware of any security issues related to providing
backwards compatibility for compiled java classes. The --release flag
(and the -source/-target pair) is and has been used on other packages
for quite some time so there are no known drawbacks of using it, on
the contrary, they are required so we can provide java 8 bytecode when
compiling with a java 9+ compiler.

Regards,
Tiago

Bug#925353: [Pkg-linaro-lava-devel] Bug#925353: lava-server: logrotate complains about "parent directory has insecure permissions"

[Steve McIntyre]

On Wed, Mar 27, 2019 at 01:30:22AM +0100, Andreas Beckmann wrote:
>On 2019-03-26 16:56, Steve McIntyre wrote:
>> That sounds like a weird way to fix what's claimed to be a permissions
>> problem in the log. Or is this just a bad error message from logrotate?
>> 
>> And checking - the logrotate file in question already has 'missingok'
>> spceified.
>
>That is the first time I encountered this strange error. The missing 
>'missingok' was just the most popular (i.e. only) cause for logrotate 
>failures so far.

ACK...

>>> 6m50.2s ERROR: Command failed (status=1): ['chroot', 
>>> '/srv/piuparts/tmp/tmpML5ulV', '/usr/sbin/logrotate', 
>>> '/etc/logrotate.d/lava-server-uwsgi-log']
>>>  error: skipping "/var/log/lava-server/lava-uwsgi.log" because parent 
>>> directory has insecure permissions (It's world writable or writable by 
>>> group which is not "root") Set "su" directive in config file to tell 
>>> logrotate which user/group should be used for rotation.
>> 
>> I appreciate that you won't have this session around now to be able to
>> look directly, but for future reports it would be very helpful if
>> piuparts could show the logfiles and directories look like at this point.
>
>I can quite easily rerun failing tests and get a shell in the chroot to 
>collect additional information ...
>
>This is after the failure in a jessie -> stretch -> buster upgrade:
>
># ls -la /var/log/lava-server/
>total 0
>drwxrwsr-x 2 lavaserver adm   80 Mar 26 17:41 .
>drwxr-xr-x 8 root   root 320 Mar 26 17:47 ..
>-rw-rw-r-- 1 lavaserver adm0 Mar 26 17:46 django.log
>-rw-r--r-- 1 root   adm0 Mar 26 17:43 lava-scheduler.log
>
>OK, that looks like bad permission, lets look where they come from:
>I added some scripts that do 'ls -la /var/log/lava-server/' before
>and after each distupgrade, full log attached.
>The problem happens during the upgrade to buster:
>
>27m28.9s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmpgfr9HI', 
>'tmp/scripts/pre_distupgrade_zzz_debug-lava-server']
>27m28.9s DUMP: 
>  + ls -la /var/log/lava-server
>  total 0
>  drwsr-sr-x 2 root   root  80 Mar 26 23:02 .
>  drwxr-xr-x 9 root   root 340 Mar 26 23:07 ..
>  -rw-r--r-- 1 lavaserver adm0 Mar 26 23:09 django.log
>  -rw-r--r-- 1 root   adm0 Mar 26 23:07 lava-scheduler.log
>27m28.9s DEBUG: Command ok: ['chroot', '/srv/piuparts/tmp/tmpgfr9HI', 
>'tmp/scripts/pre_distupgrade_zzz_debug-lava-server']
>27m28.9s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmpgfr9HI', 
>'apt-get', 'update']
>27m37.0s DUMP: 
>  Hit:1 http://ftp.de.debian.org/debian buster InRelease
>  Reading package lists...
>27m37.0s DEBUG: Command ok: ['chroot', '/srv/piuparts/tmp/tmpgfr9HI', 
>'apt-get', 'update']
>27m37.0s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmpgfr9HI', 
>'apt-get', '-yf', 'dist-upgrade']
>[...]
>44m48.3s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmpgfr9HI', 
>'tmp/scripts/post_distupgrade_000_debug-lava-server']
>44m48.3s DUMP: 
>  + ls -la /var/log/lava-server
>  total 0
>  drwxrwsr-x 2 lavaserver adm   80 Mar 26 23:02 .
>  drwxr-xr-x 9 root   root 340 Mar 26 23:07 ..
>  -rw-rw-r-- 1 lavaserver adm0 Mar 26 23:26 django.log
>  -rw-r--r-- 1 root   adm0 Mar 26 23:07 lava-scheduler.log
>44m48.3s DEBUG: Command ok: ['chroot', '/srv/piuparts/tmp/tmpgfr9HI', 
>'tmp/scripts/post_distupgrade_000_debug-lava-server']
>
>
>and now doing the same with starting in stretch (not jessie) and upgrading to 
>buster
>
>24m14.0s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmpS7TOc2', 
>'tmp/scripts/pre_distupgrade_zzz_debug-lava-server']
>24m14.1s DUMP:
>  + ls -la /var/log/lava-server
>  total 0
>  drwsr-sr-x 2 root   root  80 Mar 26 23:49 .
>  drwxr-xr-x 8 root   root 300 Mar 26 23:46 ..
>  -rw-r--r-- 1 lavaserver adm0 Mar 26 23:59 django.log
>  -rw-r--r-- 1 root   adm0 Mar 26 23:49 lava-scheduler.log
>24m14.1s DEBUG: Command ok: ['chroot', '/srv/piuparts/tmp/tmpS7TOc2', 
>'tmp/scripts/pre_distupgrade_zzz_debug-lava-server']
>24m14.1s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmpS7TOc2', 
>'apt-get', 'update']
>24m35.1s DUMP:
>  Hit:1 http://ftp.de.debian.org/debian buster InRelease
>  Reading package lists...
>24m35.1s DEBUG: Command ok: ['chroot', '/srv/piuparts/tmp/tmpS7TOc2', 
>'apt-get', 'update']
>24m35.1s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmpS7TOc2', 
>'apt-get', '-yf', 'dist-upgrade']
>[...]
>33m44.0s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmpS7TOc2', 
>'tmp/scripts/post_distupgrade_000_debug-lava-server']
>33m44.0s DUMP: 
>  + ls -la /var/log/lava-server
>  total 0
>  drwxrwsr-x 2 lavaserver adm   80 Mar 26 23:49 .
>  drwxr-xr-x 8 root   root 300 Mar 26 23:46 ..
>  -rw-rw-r-- 1 lavaserver adm0 Mar 27 00:15 django.log
>  -rw-r--r-- 1 root   adm0 Mar 26 23:49 lava-scheduler.log
>33m44.0s DEBUG: Command ok: ['chroot', '/srv/piuparts/tmp/tmpS7TOc2', 

Bug#925922: attr: [INTL:nl] Dutch po file for the attr package

[Frans Spiesschaert]

 
 
Package: attr 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the Dutch po file for the attr package. 
It has been submitted for review to the debian-l10n-dutch mailing
list. 
Please add it to your next package revision. 
It should be put as "po/nl.po" in your package build tree. 
 

-- 
Met vriendelijke groet,
Frans Spiesschaert


nl.po.gz
Description: application/gzip

Bug#925923: unblock: ruby2.5/2.5.5-1

[Antonio Terceiro]

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

Please unblock package ruby2.5. This is a maintainance-only new upstream
release that includes fixes for important bugs, and 6 security bugs.

Changelog:

 ruby2.5 (2.5.5-1) unstable; urgency=medium
 .
   * New upstream version 2.5.5. Includes a series of bug fixes, most notably
 for 6 security bugs discovered in Rubygems:
 - CVE-2019-8320: Delete directory using symlink when decompressing tar
 - CVE-2019-8321: Escape sequence injection vulnerability in verbose
 - CVE-2019-8322: Escape sequence injection vulnerability in gem owner
 - CVE-2019-8323: Escape sequence injection vulnerability in API response
   handling
 - CVE-2019-8324: Installing a malicious gem may lead to arbitrary code
   execution
 - CVE-2019-8325: Escape sequence injection vulnerability in errors
   * Rebase patches. The following patches were applied upstream and dropped
 from the Debian package:
 - 0011-Update-for-tzdata-2018f.patch
 - 0012-test-update-test-certificate.patch

The full diff against the version in testing is attached. It's a bit
big, but I have reviewed the changes and there is nothing worrysome from
my POV. You will notice that a few functions are renamed, but they are
not part of the API or the ABI since they are not exported in the -dev
header files. Having this version in buster will make the maintainance
in stable a lot easier.

unblock ruby2.5/2.5.5-1

-- 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)

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


signature.asc
Description: PGP signature

Bug#925918: linux-image-amd64: linux-image-3.16.0-8-amd64 - unpredictable reboots / kernel panics?

[Daniel Lewart]

Debian Kernel Team,

WD> So for me, linux-image-3.16.0-8-amd64 smells fishy and i was wondering
WD> if there are other users which have problems?

Yes!  My Jessie MySQL database server updated to linux-image-3.16.0-8-amd64,
rebooted, and crashed within 47 minutes.  Below are the syslog messages.

Please change Severity to "Critical" and merge Bugs #925918 and #925919.

Thank you and good luck!
Dan
---
Mar 28 07:13:11 bd kernel: [ 2836.042567] mysqld: Corrupted page table
at address 7fae5da486ac
Mar 28 07:13:11 bd kernel: [ 2836.042601] PGD 80042bf68067 PUD
42be4a067 PMD 42c78a067 PTE 61662d796e616d2d
Mar 28 07:13:11 bd kernel: [ 2836.042628] Bad pagetable: 000d [#1] SMP
Mar 28 07:13:11 bd kernel: [ 2836.042655] Modules linked in: xt_recent
iptable_nat nf_nat_ipv4 xt_comment ipt_REJECT xt_addrtype xt_mark
iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ipt_ULOG xt_NFLOG
nfnetlink_log xt_LOG nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp
nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323
nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_nat
nf_conntrack_sane nf_conntrack_tftp nf_conntrac
##

Bug#924070: [pre-approval] unblock: nvidia-cuda-toolkit/10.1.105-1

[Graham Inggs]

The CUDA 10.1 transition was completed in Ubuntu yesterday, and I'll be 
watching for bug reports.

Bug#925921: RFP: nuspell -- Nuspell is a free and open source spell checker that is written in modern C++.

[Pander]

Package: wnpp
Severity: wishlist

* Package name: nuspell
  Version : 2.2.0
  Upstream Author : Pander 
* URL : https://github.com/nuspell/nuspell
* License : LGPL
  Programming Lang: C++
  Description : spell checker
  
Nuspell is a free and open source spell checker that is written in modern C++.
It extensively supports character encodings, compounding, affixing and complex
morphology. It has backwards compatability with MySpell and Hunspell
dictionaries and affix files, a.k.a. language support. Nuspell offers also
suggestions and personal dictionaries.

Debian source package is available at
https://github.com/nuspell/misc-nuspell/tree/master/packaging

Bug#925590: fai-client: remove "libfile-lchown-perl" dependency from fcopy

[Thomas Lange]

lchown is only needed if a symlink needs to be changed.
One option would be to add some code which does only loads this perl
module if we have a symlink.

This conditional loading of a Perl package can be done using
eval "require File::lchown"

If this fails, we cannot load the package, but the script itself does
not fail.
-- 
regards Thomas

Bug#884632: missing from backports

[Josue Ortega]

On Wed, Mar 27, 2019 at 12:40:08PM -0700, blathersc...@secmail.pro wrote:
> > I will upload the upstream version 1.19 to stretch-backports by now.
> 
> This command should work:
> 
> $ aptitude -t stretch-backports install rtv
> 
> But the backports version is still 1.14.1.

Hi

I have uploaded the fix to the Stretch backports:
https://ftp-master.debian.org/new/rtv_1.25.1+dfsg-1~bpo9+1.html

Currently it is in an approval queue, should be accepted in the next days.

Sorry for the inconvenience


signature.asc
Description: PGP signature

Bug#924891: glibc: FTBFS: /<>/build-tree/amd64-libc/conform/UNIX98/ndbm.h/scratch/ndbm.h-test.c:1:10: fatal error: ndbm.h: No such file or directory

[Lucas Nussbaum]

On 27/03/19 at 23:59 +0100, Florian Weimer wrote:
> retitle 924891 glibc: misc/tst-pkey fails due to cleared PKRU register after 
> signal in amd64 32-bit compat mode 
> thanks
> 
> * Lucas Nussbaum:
> 
> > On 27/03/19 at 08:48 +0100, Florian Weimer wrote:
> >> > If that's useful, I can easily provide access to an AWS VM to debug this
> >> > issue.
> >> 
> >> Oh, that would be quite helpful indeed.
> >
> > Can you send your SSH key? (I thought there was a way to get the SSH key
> > for a DD, but I cannot find it anymore)
> >
> > Then you will be able to ssh to root@18.184.55.40.
> > There's sbuild and schroot setup on the VM.
> >
> > When you are done, please 'poweroff' the machine, which will terminate
> > it.
> 
> The issue reproduces outside the chroot, with the stretch userland.
> 
> What happens is that once we get out of the SIGUSR1 signal handler,
> the PKRU register has value zero.  This happens around this code in
> the test:
> 
>   /* Check that in a signal handler, there is no access.  */
>   xsignal (SIGUSR1, _handler);
>   xraise (SIGUSR1);
>   xsignal (SIGUSR1, SIG_DFL);
>   TEST_COMPARE (sigusr1_handler_ran, 1);
> 
> I checked the following (via a breakpoint in pkey_get; I don't think
> GDB can read the PKRU register directly): Inside the SIGUSR1 signal
> handler, PKRU has value 0x5554, as expected for this kernel, but
> after the return, we get zero.  This is the first time a signal is
> delivered on the main thread, so it's consistent with fairly broken
> signal handling as far as the PKRU register is concerned.  I guess
> clearing PKRU in this way might even constitute a minor security bug
> (because the zero value means no restrictions).
> 
> This commit looks highly relevant:
> 
> commit a4455082dc6f0b5d51a23523f77600e8ede47c79
> Author: Dave Hansen 
> Date:   Wed Jun 8 10:25:33 2016 -0700
> 
> x86/signals: Add missing signal_compat code for x86 features
> 
> The 32-bit siginfo is a different binary format than the 64-bit
> one.  So, when running 32-bit binaries on 64-bit kernels, we have
> to convert the kernel's 64-bit version to a 32-bit version that
> userspace can grok.
> 
> If the siginfo_t layout is incorrect (with regards to what the
> hardware writes), I expect that we might end up copying back the wrong
> PKRU value.
> 
> I'm not sure what to do here.  This really looks like a kernel bug.
> Maybe we should just verify that this is fixed in the buster kernel
> and move on?
> 
> Lucas, can you run your rebuild tests on newer kernels?

Indeed. I upgraded the kernel to the stretch-backports one, and glibc
builds fine.

Lucas

Bug#925920: golang-github-jlaffaye-ftp: Please update to fix GitHu:#114

[Christoph Egger]

Package: golang-github-jlaffaye-ftp
Version: 0.0~git20170707.0.a05056b-1
Severity: normal

Hi!

seems there was a bug in the protocol implementation (see upstream bug
#114) that prevents rclone (via this library) to access my ftp
space. Please consider updateing to address this issue

Thanks!

  Christoph

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

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

Bug#924854: mmdebstrap: flaky autopkgtest

[Pollet Obuya]

unsubscribe

On Sun, Mar 17, 2019 at 9:54 PM Paul Gevers  wrote:

> Source: mmdebstrap
> Version: 0.4.1-1
> Severity: important
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: flaky
>
> Dear maintainers,
>
> Since the end of February the autopkgtest of mmdebstrap sometimes fails
> in unstable and testing, while a retry not much later succeeds. Because
> the unstable-to-testing migration software now blocks on regressions in
> testing, flaky tests, i.e. tests that flip between passing and failing
> without changes to the list of installed packages, are wasting peoples
> time. Please either fix the test to be more robust, or mark this
> particular test as "flaky".
>
> I copied some of the output at the bottom of this report. Unfortunately,
> the failure doesn't always seem to be on the same place.
>
> More information about this bug and the reason for filing it can be found
> on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
>
> Paul
>
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/m/mmdebstrap/2123560/log.gz
>
>
> --
> (27/88) mode=root,variant=apt: test --include=libc6:armhf
> time left: 00:14:28
>
> --
> + set -eu
> + export LC_ALL=C.UTF-8
> + mmdebstrap --mode=root --variant=apt --architectures=amd64,armhf
> --include=gcc-8-base:armhf unstable /tmp/debian-unstable
> http://127.0.0.1/debian
> I: chroot architecture amd64 is equal to the host's architecture
> I: Reading sources.list from standard input...
> I: running apt-get update...
> I: downloading packages with apt...
> I: extracting archives...
> I: installing packages...
> I: installing remaining packages inside the chroot...
> Reading package lists...
> Building dependency tree...
> The following packages will be REMOVED:
>   adduser apt base-files base-passwd bash bsdutils coreutils dash debconf
>   debianutils diffutils dpkg fdisk findutils gcc-8-base gpgv grep gzip
>   hostname init-system-helpers libacl1 libapt-pkg5.0 libattr1 libaudit1
>   libblkid1 libbz2-1.0 libc-bin libc6 libcap-ng0 libdb5.3 libdebconfclient0
>   libfdisk1 libffi6 libgcc1 libgcrypt20 libgmp10 libgnutls30 libgpg-error0
>   libhogweed4 libidn2-0 liblz4-1 liblzma5 libmount1 libncursesw6 libnettle6
>   libp11-kit0 libpam-modules libpam-modules-bin libpam-runtime libpam0g
>   libpcre3 libseccomp2 libselinux1 libsemanage1 libsepol1 libsmartcols1
>   libstdc++6 libsystemd0 libtasn1-6 libtinfo6 libudev1 libunistring2
> libuuid1
>   libzstd1 login mawk ncurses-bin passwd perl-base sed sysvinit-utils tar
>   util-linux zlib1g
> The following NEW packages will be installed:
>   gcc-8-base:armhf
> WARNING: The following essential packages will be removed.
> This should NOT be done unless you know exactly what you are doing!
>   apt adduser (due to apt) gpgv (due to apt) libapt-pkg5.0 (due to apt)
>   libc6 (due to apt) libgcc1 (due to apt) libgnutls30 (due to apt)
>   libseccomp2 (due to apt) libstdc++6 (due to apt) base-files base-passwd
>   libdebconfclient0 (due to base-passwd) bash libtinfo6 (due to bash)
>   debianutils (due to bash) bsdutils libsystemd0 (due to bsdutils)
> coreutils
>   libacl1 (due to coreutils) libattr1 (due to coreutils)
>   libselinux1 (due to coreutils) dash dpkg (due to dash) debconf (due to
> dash)
>   diffutils libbz2-1.0 (due to dpkg) liblzma5 (due to dpkg)
>   zlib1g (due to dpkg) tar (due to dpkg) fdisk libfdisk1 (due to fdisk)
>   libmount1 (due to fdisk) libncursesw6 (due to fdisk)
>   libsmartcols1 (due to fdisk) findutils grep libpcre3 (due to grep) gzip
>   hostname init-system-helpers perl-base (due to init-system-helpers)
> libc-bin
>   login libaudit1 (due to login) libpam0g (due to login)
>   libpam-runtime (due to login) libpam-modules (due to login)
> ncurses-bin sed
>   sysvinit-utils util-linux (due to sysvinit-utils)
>   libblkid1 (due to util-linux) libcap-ng0 (due to util-linux)
>   libudev1 (due to util-linux) libuuid1 (due to util-linux)
> 0 upgraded, 1 newly installed, 74 to remove and 0 not upgraded.
> E: Essential packages were removed and -y was used without
> --allow-remove-essential.
> E: run_chroot failed: E: /usr/sbin/chroot /tmp/debian-unstable env
> --unset=APT_CONFIG --unset=TMPDIR apt-get --yes install
> -oAPT::Status-Fd=<$fd> -oDpkg::Use-Pty=false gcc-8-base:armhf failed
> test.sh failed
> + kill 1482
>
>
>

Bug#920545: python-intervaltree breaks python-intervaltree-bio autopkgtest

[Graham Inggs]

Hi Olivier

On 2019/03/09 17:56, olivier sallou wrote:

I have pushed a fix to get autopkgtests done in python-intervaltree-bio
I have not uploaded package, as we are in freeze transition, so patch is in
git only
Commit: 4f67ea8b607fa47520b553ce8776a37cf62a1713
Link:
https://salsa.debian.org/med-team/python-intervaltree-bio/commit/4f67ea8b607fa47520b553ce8776a37cf62a1713


I've just uploaded python-intervaltree-bio including this patch to 
Ubuntu and confirm that it fixes the autopkgtest there.


python-intervaltree should get "Breaks: python-intervaltree-bio (<< 
1.0.1-4)" or similar added.


Regards
Graham

Bug#925781: mozjs52: ftbfs with GCC-9

[Simon McVittie]

On Wed, 27 Mar 2019 at 19:47:11 +, Matthias Klose wrote:
> The last lines of the build log

... don't look particularly relevant. The error seems to be:

/<>/js/src/jsapi-tests/testPrintf.cpp: In member function 'virtual 
bool cls_testPrintf::run(JS::HandleObject)':
/<>/js/src/jsapi-tests/testPrintf.cpp:58:20: error: '%s' directive 
argument is null [-Werror=format-overflow=]
   58 | CHECK(print_one("(null)", "%s", zero()));

smcv

Bug#925919: linux-image-amd64: linux-image-3.16.0-8-amd64 - unpredictable reboots / kernel panics?

[Werner D.]

Package: linux-image-amd64
Version: linux-image-3.16.0-8-amd64
Severity: important

Dear Maintainer,

here we go again, i hope this time we get a bug nummer for this report :) 

after upgrading to the latest linux-image-adm64 on jessie we're experiencing 
several issues which led us 
to downgrade to linux-image-3.16.0-7-amd64 again and deinstall 
linux-image-3.16.0-8-amd64. It's happened
until now on a COROSYNC/DRBD Cluster where standby node has been upgraded and 
after the upgrade the system
froze, see [1]. 

On another MySQL-Slave where we applied this kernel - the system - after 
running some time rebooted due to
a kernel panic. I wasn't fast enough to catch the kernel panic on the screen as 
VMware HA-features instantly 
rebooted the system. Both systems run in a VMware HA-Cluster on different ESXi 
runhosts.

So for me, linux-image-3.16.0-8-amd64 smells fishy and i was wondering if there 
are other users which have
problems? 

Cheers,
Werner



[1]
Mar 28 13:35:38 nfs02 kernel: [  191.925130] block drbd0: helper command: 
/sbin/drbdadm after-resync-target minor-0
Mar 28 13:35:38 nfs02 kernel: [  191.927389] block drbd0: helper command: 
/sbin/drbdadm after-resync-target minor-0 exit code 0 (0x0)
Mar 28 13:35:40 nfs02 kernel: [  194.306334] drbd r0: Wrong magic value 
0x in protocol version 101
Mar 28 13:35:40 nfs02 kernel: [  194.306407] drbd r0: peer( Primary -> Unknown 
) conn( Connected -> ProtocolError ) pdsk( UpToDate -> DUnknown ) 
Mar 28 13:35:40 nfs02 kernel: [  194.306432] drbd r0: asender terminated
Mar 28 13:35:40 nfs02 kernel: [  194.306436] drbd r0: Terminating drbd_a_r0
Mar 28 13:35:40 nfs02 kernel: [  194.306828] drbd r0: Connection closed
Mar 28 13:35:40 nfs02 kernel: [  194.306845] drbd r0: conn( ProtocolError -> 
Unconnected ) 
Mar 28 13:35:40 nfs02 kernel: [  194.306847] drbd r0: receiver terminated
Mar 28 13:35:40 nfs02 kernel: [  194.306848] drbd r0: Restarting receiver thread
Mar 28 13:35:40 nfs02 kernel: [  194.306850] drbd r0: receiver (re)started
Mar 28 13:35:40 nfs02 kernel: [  194.306860] drbd r0: conn( Unconnected -> 
WFConnection ) 
Mar 28 13:35:41 nfs02 kernel: [  194.805238] drbd r0: Handshake successful: 
Agreed network protocol version 101
Mar 28 13:35:41 nfs02 kernel: [  194.805243] drbd r0: Agreed to support TRIM on 
protocol level
Mar 28 13:35:41 nfs02 kernel: [  194.805274] drbd r0: conn( WFConnection -> 
WFReportParams ) 
Mar 28 13:35:41 nfs02 kernel: [  194.805277] drbd r0: Starting asender thread 
(from drbd_r_r0 [1367])
Mar 28 13:35:41 nfs02 kernel: [  194.869215] block drbd0: drbd_sync_handshake:
Mar 28 13:35:41 nfs02 kernel: [  194.869221] block drbd0: self 
E2641EEB9E133204::0DD839919AA45372:0DD739919AA45373 bits:0 
flags:0
Mar 28 13:35:41 nfs02 kernel: [  194.869225] block drbd0: peer 
14F96DC2D3D2E20D:E2641EEB9E133205:0DD839919AA45373:0DD739919AA45373 bits:23 
flags:0
Mar 28 13:35:41 nfs02 kernel: [  194.869228] block drbd0: uuid_compare()=-1 by 
rule 50
Mar 28 13:35:41 nfs02 kernel: [  194.869236] block drbd0: peer( Unknown -> 
Primary ) conn( WFReportParams -> WFBitMapT ) disk( UpToDate -> Outdated ) 
pdsk( DUnknown -> UpToDate ) 
Mar 28 13:35:41 nfs02 kernel: [  194.876039] block drbd0: receive bitmap stats 
[Bytes(packets)]: plain 0(0), RLE 39(1), total 39; compression: 100.0%
Mar 28 13:35:41 nfs02 kernel: [  194.882431] block drbd0: send bitmap stats 
[Bytes(packets)]: plain 0(0), RLE 39(1), total 39; compression: 100.0%
Mar 28 13:35:41 nfs02 kernel: [  194.882445] block drbd0: conn( WFBitMapT -> 
WFSyncUUID ) 
Mar 28 13:35:41 nfs02 kernel: [  194.887016] block drbd0: updated sync uuid 
E2651EEB9E133204::0DD839919AA45372:0DD739919AA45373
Mar 28 13:35:41 nfs02 kernel: [  194.887489] block drbd0: helper command: 
/sbin/drbdadm before-resync-target minor-0
Mar 28 13:35:41 nfs02 kernel: [  194.889641] block drbd0: helper command: 
/sbin/drbdadm before-resync-target minor-0 exit code 0 (0x0)
Mar 28 13:35:41 nfs02 kernel: [  194.889656] block drbd0: conn( WFSyncUUID -> 
SyncTarget ) disk( Outdated -> Inconsistent ) 
Mar 28 13:35:41 nfs02 kernel: [  194.889666] block drbd0: Began resync as 
SyncTarget (will sync 92 KB [23 bits set]).
Mar 28 13:35:41 nfs02 kernel: [  194.900324] drbd r0: Wrong magic value 
0x84a1785a in protocol version 101
Mar 28 13:35:41 nfs02 kernel: [  194.900381] drbd r0: peer( Primary -> Unknown 
) conn( SyncTarget -> ProtocolError ) pdsk( UpToDate -> DUnknown ) 
Mar 28 13:35:41 nfs02 kernel: [  194.900392] drbd r0: asender terminated
Mar 28 13:35:41 nfs02 kernel: [  194.900394] drbd r0: Terminating drbd_a_r0
Mar 28 13:35:41 nfs02 kernel: [  194.911438] drbd r0: Connection closed
Mar 28 13:35:41 nfs02 kernel: [  194.911456] drbd r0: conn( ProtocolError -> 
Unconnected ) 
Mar 28 13:35:41 nfs02 kernel: [  194.911458] drbd r0: receiver terminated
Mar 28 13:35:41 nfs02 kernel: [  194.911460] drbd r0: Restarting receiver thread
Mar 28 13:35:41 nfs02 kernel: [  194.911461] drbd r0: receiver 

Bug#925915: cjk: Failed to analyze the VCS repository

[韓達耐]

Hahaha! Thanks for pointing that out, Hilmar.

I wanted to bring it over to the new GIT repository but it escaped my
attention.
I am now abroad due to unforeseen circumstances, and will return home in
the second week of April.
I will migrate everything to the new repo.

Cheers

-- 
Danai

On Thu, 28 Mar 2019, 14:04 Hilmar Preuße,  wrote:

> Source: cjk
> Version: 4.8.4+git20170127-2
> Severity: normal
>
> Dear Maintainer,
>
>* What led up to the situation?
>
> On the way to have a look at the current Debian cjk repository I had
> to notice that the package still lists a svn repository on Debian
> Alioth. I hope this is not correct any more. ;-)
>
> Please fix the URL.
>
> Thanks!
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: i386 (i686)
>
> Kernel: Linux 4.19.0-4-686-pae (SMP w/1 CPU core)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored:
> LC_ALL set to en_GB.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored:
> LC_ALL set to en_GB.UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
>

Bug#925918: linux-image-amd64: linux-image-3.16.0-8-amd64 - unpredictable reboots / kernel panics?

[Werner D.]

Package: linux-image-amd64
Version: linux-image-3.16.0-8-amd64
Severity: important

Dear Maintainer,

after upgrading to the latest linux-image-adm64 on jessie we're experiencing 
several issues which led us 
to downgrade to linux-image-3.16.0-7-amd64 again and deinstall 
linux-image-3.16.0-8-amd64. It's happened
until now on a COROSYNC/DRBD Cluster where standby node has been upgraded and 
after the upgrade the system
froze, see [1]. 

On another MySQL-Slave where we applied this kernel - the system - after 
running some time rebooted due to
a kernel panic. I wasn't fast enough to catch the kernel panic on the screen as 
VMware HA-features instantly 
rebooted the system. Both systems run in a VMware HA-Cluster on different ESXi 
runhosts.

So for me, linux-image-3.16.0-8-amd64 smells fishy and i was wondering if there 
are other users which have
problems? 

Cheers,
Werner



[1]
Mar 28 13:35:38 nfs02 kernel: [  191.925130] block drbd0: helper command: 
/sbin/drbdadm after-resync-target minor-0
Mar 28 13:35:38 nfs02 kernel: [  191.927389] block drbd0: helper command: 
/sbin/drbdadm after-resync-target minor-0 exit code 0 (0x0)
Mar 28 13:35:40 nfs02 kernel: [  194.306334] drbd r0: Wrong magic value 
0x in protocol version 101
Mar 28 13:35:40 nfs02 kernel: [  194.306407] drbd r0: peer( Primary -> Unknown 
) conn( Connected -> ProtocolError ) pdsk( UpToDate -> DUnknown ) 
Mar 28 13:35:40 nfs02 kernel: [  194.306432] drbd r0: asender terminated
Mar 28 13:35:40 nfs02 kernel: [  194.306436] drbd r0: Terminating drbd_a_r0
Mar 28 13:35:40 nfs02 kernel: [  194.306828] drbd r0: Connection closed
Mar 28 13:35:40 nfs02 kernel: [  194.306845] drbd r0: conn( ProtocolError -> 
Unconnected ) 
Mar 28 13:35:40 nfs02 kernel: [  194.306847] drbd r0: receiver terminated
Mar 28 13:35:40 nfs02 kernel: [  194.306848] drbd r0: Restarting receiver thread
Mar 28 13:35:40 nfs02 kernel: [  194.306850] drbd r0: receiver (re)started
Mar 28 13:35:40 nfs02 kernel: [  194.306860] drbd r0: conn( Unconnected -> 
WFConnection ) 
Mar 28 13:35:41 nfs02 kernel: [  194.805238] drbd r0: Handshake successful: 
Agreed network protocol version 101
Mar 28 13:35:41 nfs02 kernel: [  194.805243] drbd r0: Agreed to support TRIM on 
protocol level
Mar 28 13:35:41 nfs02 kernel: [  194.805274] drbd r0: conn( WFConnection -> 
WFReportParams ) 
Mar 28 13:35:41 nfs02 kernel: [  194.805277] drbd r0: Starting asender thread 
(from drbd_r_r0 [1367])
Mar 28 13:35:41 nfs02 kernel: [  194.869215] block drbd0: drbd_sync_handshake:
Mar 28 13:35:41 nfs02 kernel: [  194.869221] block drbd0: self 
E2641EEB9E133204::0DD839919AA45372:0DD739919AA45373 bits:0 
flags:0
Mar 28 13:35:41 nfs02 kernel: [  194.869225] block drbd0: peer 
14F96DC2D3D2E20D:E2641EEB9E133205:0DD839919AA45373:0DD739919AA45373 bits:23 
flags:0
Mar 28 13:35:41 nfs02 kernel: [  194.869228] block drbd0: uuid_compare()=-1 by 
rule 50
Mar 28 13:35:41 nfs02 kernel: [  194.869236] block drbd0: peer( Unknown -> 
Primary ) conn( WFReportParams -> WFBitMapT ) disk( UpToDate -> Outdated ) 
pdsk( DUnknown -> UpToDate ) 
Mar 28 13:35:41 nfs02 kernel: [  194.876039] block drbd0: receive bitmap stats 
[Bytes(packets)]: plain 0(0), RLE 39(1), total 39; compression: 100.0%
Mar 28 13:35:41 nfs02 kernel: [  194.882431] block drbd0: send bitmap stats 
[Bytes(packets)]: plain 0(0), RLE 39(1), total 39; compression: 100.0%
Mar 28 13:35:41 nfs02 kernel: [  194.882445] block drbd0: conn( WFBitMapT -> 
WFSyncUUID ) 
Mar 28 13:35:41 nfs02 kernel: [  194.887016] block drbd0: updated sync uuid 
E2651EEB9E133204::0DD839919AA45372:0DD739919AA45373
Mar 28 13:35:41 nfs02 kernel: [  194.887489] block drbd0: helper command: 
/sbin/drbdadm before-resync-target minor-0
Mar 28 13:35:41 nfs02 kernel: [  194.889641] block drbd0: helper command: 
/sbin/drbdadm before-resync-target minor-0 exit code 0 (0x0)
Mar 28 13:35:41 nfs02 kernel: [  194.889656] block drbd0: conn( WFSyncUUID -> 
SyncTarget ) disk( Outdated -> Inconsistent ) 
Mar 28 13:35:41 nfs02 kernel: [  194.889666] block drbd0: Began resync as 
SyncTarget (will sync 92 KB [23 bits set]).
Mar 28 13:35:41 nfs02 kernel: [  194.900324] drbd r0: Wrong magic value 
0x84a1785a in protocol version 101
Mar 28 13:35:41 nfs02 kernel: [  194.900381] drbd r0: peer( Primary -> Unknown 
) conn( SyncTarget -> ProtocolError ) pdsk( UpToDate -> DUnknown ) 
Mar 28 13:35:41 nfs02 kernel: [  194.900392] drbd r0: asender terminated
Mar 28 13:35:41 nfs02 kernel: [  194.900394] drbd r0: Terminating drbd_a_r0
Mar 28 13:35:41 nfs02 kernel: [  194.911438] drbd r0: Connection closed
Mar 28 13:35:41 nfs02 kernel: [  194.911456] drbd r0: conn( ProtocolError -> 
Unconnected ) 
Mar 28 13:35:41 nfs02 kernel: [  194.911458] drbd r0: receiver terminated
Mar 28 13:35:41 nfs02 kernel: [  194.911460] drbd r0: Restarting receiver thread
Mar 28 13:35:41 nfs02 kernel: [  194.911461] drbd r0: receiver (re)started
Mar 28 13:35:41 nfs02 kernel: [  194.911471] drbd r0: conn( Unconnected -> 

Bug#900573: qreator: Proposed patch to fix the crash

[Chow Loong Jin]

On Wed, Mar 27, 2019 at 10:31:35PM +0100, Andreas Boll wrote:
> Control: severity -1 serious
> Control: tags -1 + patch
> 
> Dear maintainer,
> 
> I've prepared a patch to fix this issue.
> Also currently the package qreator isn't useful at all with this issue
> because it crashes on startup. Thus bumping severity to serious
> because this package shouldn't end up in Debian Buster without a fix
> for this issue.
> 
> Please let me know if I should upload this fix as NMU or if you like
> to upload it yourself.

Please go ahead and upload this fix. Thanks.

-- 
Kind regards,
Loong Jin


signature.asc
Description: PGP signature

Bug#917296: emacs-gtk: Emacs GNUS can no longer use movemail

[Oleg Kostyuchenko]

This update to Emacs 26.1 broke my movemail setup (Buster) in exactly the same 
way.

The bad thing here is, I don't even have mailutils installed as this package is 
pretty much bloated.
But for some reason I had a movemail executable in 
/usr/bin/emacs/v25.2/x86_64-linux-gnu and had no problems with mail retrieval 
from a (file) spool. (Apt-file somewhy doesn't show me the owner of this 
executable).

After upgrade to 26.1, there is no movemail executable in 
/usr/bin/emacs/v25.2/x86_64-linux-gnu anymore and I cannot retrieve mail from a 
local spool, observing the "searching for program" error.

One  hack is to retrieve the old movemail executable from a backup or deb 
package, and reinstate it in /usr/bin/emacs/v26.1/x86_64-linux-gnu.

Thanks
Oleg

Bug#925917: openvassd reports error release_connection_fd: close() : Bad file descriptor

[Jason Ede]

Package: openvas
Version: 9.0.3
Severity: important
Tags: a11y

Dear Maintainer,

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

   * What led up to the situation?
 
Installed openvas and tried to run a scan. In 
/var/log/openvassd.messages the following is then logged for some hosts and the 
scan never completes

[Thu Mar 28 13:35:17 2019][24429] [24429] release_connection_fd: 
close() : Bad file descriptor

[Thu Mar 28 13:35:17 2019][24429] Severe bug! Unhandled transport layer -1 
(fd=100)

[Thu Mar 28 13:35:17 2019][24429] Severe bug! Unhandled transport layer -1 
(fd=100)

[Thu Mar 28 13:35:17 2019][24429] [24429] release_connection_fd: close() : Bad 
file descriptor


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

I found errors in /var/log/syslog
Mar 28 13:17:38 openvas9 gsad[528]: xsltFreeStackElem: Unexpected RVT flag (nil)
Mar 28 13:17:38 openvas9 gsad[528]: xsltFreeStackElem: Unexpected RVT flag (nil)
Mar 28 13:17:38 openvas9 gsad[528]: xsltFreeStackElem: Unexpected RVT flag (nil)
Mar 28 13:17:38 openvas9 gsad[528]: xsltFreeStackElem: Unexpected RVT flag (nil)
Mar 28 13:17:38 openvas9 gsad[528]: xsltFreeStackElem: Unexpected RVT flag (nil)
Mar 28 13:17:38 openvas9 gsad[528]: xsltFreeStackElem: Unexpected RVT flag (nil)
 that referenced libxslt1.1 and found indications that this might have issues. 
Tried the 1.1.29 version and the errors from the syslog disappeared, but the 
errors in openvassd.messages remained


   * What was the outcome of this action?
Did not resolve the problem
   * What outcome did you expect instead?

Expected scan to complete, but it's stuck in a non-complete state for 
some hosts and never finishes.

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


-- 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/6 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openvas depends on:
ii  greenbone-security-assistant  7.0.3+dfsg.1-1
ii  openvas-cli   1.4.5-2
ii  openvas-manager   7.0.3-1
ii  openvas-scanner   5.1.3-2

Versions of packages openvas recommends:
ii  rsync 3.1.3-6
ii  sqlite3   3.27.2-1
ii  xsltproc  1.1.32-2

openvas suggests no packages.

-- no debconf information

Bug#925577: shairport-sync: Crashes with "free(): double free detected in tcache 2" with instance name changed

[Bernhard Übelacker]

Control: tags 925577 + upstream patch


Dear Maintainer,
I tried to have a look at this crash and
could reproduce the issue.

It seems a pointer to the name-parameter value is queried
from libconfig9 and some lines later this pointer gets freed.

Unfortunately libconfig9 tries to free the pointer later too.

A valgrind run shows this quite nicely.

Attached patch makes a copy of the queried value that
could be safely freed later.
A package build with that patch does not crash.

Could not find a related issue in the upstream bug tracker.

Kind regards,
Bernhard


benutzer@debian:~$ valgrind shairport-sync 
==8612== Memcheck, a memory error detector
==8612== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==8612== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
==8612== Command: shairport-sync
==8612== 
fatal error: Could not establish a service on port 5000 -- program terminating. 
Is another instance of Shairport Sync running on this device?
==8612== Invalid free() / delete / delete[] / realloc()
==8612==at 0x48369AB: free (vg_replace_malloc.c:530)
==8612==by 0x4F910C8: __config_setting_destroy (libconfig.c:472)
==8612==by 0x4F91070: __config_list_destroy (libconfig.c:502)
==8612==by 0x4F91070: __config_setting_destroy (libconfig.c:479)
==8612==by 0x4F91070: __config_list_destroy (libconfig.c:502)
==8612==by 0x4F91070: __config_setting_destroy (libconfig.c:479)
==8612==by 0x4F914E2: config_destroy (libconfig.c:743)
==8612==by 0x1114F4: exit_function (shairport.c:1067)
==8612==by 0x5736E9B: __run_exit_handlers (exit.c:108)
==8612==by 0x5736FC9: exit (exit.c:139)
==8612==by 0x119118: die (common.c:124)
==8612==by 0x117C71: rtsp_listen_loop (rtsp.c:2099)
==8612==by 0x110CD3: main (shairport.c:1512)
==8612==  Address 0x71c00b0 is 0 bytes inside a block of size 7 free'd
==8612==at 0x48369AB: free (vg_replace_malloc.c:530)
==8612==by 0x11253D: parse_options (shairport.c:967)
==8612==by 0x110D62: main (shairport.c:1221)
==8612==  Block was alloc'd at
==8612==at 0x483577F: malloc (vg_replace_malloc.c:299)
==8612==by 0x5784FF9: strdup (strdup.c:42)
==8612==by 0x4F91C8A: config_setting_set_string (libconfig.c:1161)
==8612==by 0x4F95637: libconfig_yyparse (grammar.y:346)
==8612==by 0x4F9169C: __config_read (libconfig.c:597)
==8612==by 0x4F91847: config_read_file (libconfig.c:712)
==8612==by 0x11231C: parse_options (shairport.c:372)
==8612==by 0x110D62: main (shairport.c:1221)
>From a620d40987108349beae29f44fac0710e3643993 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bernhard=20=C3=9Cbelacker?= 
Date: Thu, 28 Mar 2019 14:06:26 +0100
Subject: [PATCH] Avoid double free by making a copy of the value received from
 libconfig9.

https://bugs.debian.org/925577
---
 shairport.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/shairport.c b/shairport.c
index 301838c..56a766b 100644
--- a/shairport.c
+++ b/shairport.c
@@ -374,7 +374,7 @@ int parse_options(int argc, char **argv) {
   config.cfg = _file_stuff;
   /* Get the Service Name. */
   if (config_lookup_string(config.cfg, "general.name", )) {
-raw_service_name = (char *)str;
+raw_service_name = strdup(str);
   }
   int daemonisewithout = 0;
   int daemonisewith = 0;
-- 
2.20.1


# Buster amd64 qemu VM 2019-03-28

apt update
apt dist-upgrade


apt install systemd-coredump xserver-xorg lightdm openbox shairport-sync gdb 
shairport-sync-dbgsym libconfig9-dbgsym valgrind devscripts dpkg-dev net-tools
apt build-dep shairport-sync

systemctl start lightdm

sed -i 's@//.*name = "%H";@   name = "Arcade";\n//  name = "%H"@g' 
/etc/shairport-sync.conf



mkdir /home/benutzer/source/shairport-sync/orig -p
cd/home/benutzer/source/shairport-sync/orig
apt source shairport-sync
cd


mkdir /home/benutzer/source/libconfig9/orig -p
cd/home/benutzer/source/libconfig9/orig
apt source libconfig9
cd


###


benutzer@debian:~$ shairport-sync 
fatal error: Could not establish a service on port 5000 -- program terminating. 
Is another instance of Shairport Sync running on this device?
free(): double free detected in tcache 2
Abgebrochen (Speicherabzug geschrieben)


root@debian:~# coredumpctl list
TIMEPID   UID   GID SIG COREFILE  EXE
Thu 2019-03-28 13:24:22 CET8268  1000  1000   6 present   
/usr/bin/shairport-sync


root@debian:~# coredumpctl gdb 8268
   PID: 8268 (shairport-sync)
   UID: 1000 (benutzer)
   GID: 1000 (benutzer)
Signal: 6 (ABRT)
 Timestamp: Thu 2019-03-28 13:24:22 CET (1min 22s ago)
  Command Line: shairport-sync
Executable: /usr/bin/shairport-sync
 Control Group: /user.slice/user-1000.slice/session-5.scope
  Unit: session-5.scope
 Slice: user-1000.slice
   Session: 5
 Owner UID: 1000 (benutzer)
   Boot ID: df1b25a2714f48f2bad5fbd1c7b68abd
Machine ID: 

Bug#925602: unblock: ruby-globalid/0.4.2-1

[Utkarsh Gupta]

Hey,

On Thu, Mar 28, 2019 at 2:16 AM Paul Gevers  wrote:

> Control: tags -1 moreinfo
>
> Hi Utkarsh,
>
> On 27-03-2019 14:30, Utkarsh Gupta wrote:
> > Please unblock package ruby-globalid.
> >
> > Recently, there was a bug (#925178) reported against the package with
> > severity: important.
>
> Did you see my last note in that bug?
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925178#21


Apologies. I didn't see it earlier :(
Answering below.

Care to answer it here?
> '''
> On 24-03-2019 07:21, Debian Bug Tracking System wrote:
> >  ruby-globalid (0.4.2-1) unstable; urgency=medium
> >  .
> >* Team upload
> >* New upstream version 0.4.2
> >* Add patch to fix regression (Closes: #925178)
> >* Drop patches that are merged in upstream
> >* Bump debhelper compatibility level to 11
> >* Bump Standards-Version to 4.3.0 (no changes needed)
> >* Fix insecure URL
>
> Thanks for the quick fix for this issue. However, due to the new
> upstream version and the debhelper compatibility bump this version is
> not eligible [1] for an unblock for buster.
>
> Did rails 2:5.2.2.1+dfsg-1 break ruby-globalid or did it only break the
> autopkgtest of it? I'm asking because this version of rails is fixing a
> CVE's which we want in buster, but the autopkgtest failure (and the
> freeze) is blocking it.
>

It was breaking just the autopkgtest, thus the regression.
Everything else was fine.

Paul
>
> [1] https://release.debian.org/buster/freeze_policy.html
> '''
>
> > The package was in testing and the bug was reported on 20th March and
> > was resolved in the latest upload, which was on 24th March.
> > This also causes regression in the migration of rails' latest update.
> >
> > Hence, request you to:
> >
> > unblock ruby-globalid/0.4.2-1
>
> Not likely in the current state.
>

ruby-activejob from rails is the only reverse dependency of ruby-globalid.
Since the package is in good shape now, perhaps could be given an exception?
And it won't be risky either since ruby-activejob is the only rev-dep :)
Also, it was an RC bug at the last moment (though I understand the scenario
here) :(

Paul
>


Best,
Utkarsh

Bug#925916: /usr/lib/x86_64-linux-gnu/pkgconfig/librtlsdr.pc file broken?

[Gürkan Myczko]

Package: librtlsdr-dev
Version: 0.6-1
Severity: wishlist

I think the file in Subject: is broken, see
https://github.com/merbanan/rtl_433/issues/952

Yours,

Bug#925915: cjk: Failed to analyze the VCS repository

[Hilmar Preuße]

Source: cjk
Version: 4.8.4+git20170127-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?

On the way to have a look at the current Debian cjk repository I had
to notice that the package still lists a svn repository on Debian
Alioth. I hope this is not correct any more. ;-)

Please fix the URL.

Thanks!

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

Kernel: Linux 4.19.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#923926: proftpd has memory leaks, allows Denial-Of-Service attack

[Markus Koschany]

Hello Francesco,

I intend to upgrade proftpd in Jessie to fix the memory leaks and
another unrelated issue. I think it would be best to backport the
version in testing. If you agree, I could also update proftpd in stable.
Please let me know if I can proceed.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#859063: weston: running 'weston --fullscreen' inside of weston causes bad RAM access

[Hector Oron]

On Thu, Mar 30, 2017 at 01:00:15AM +0200, mviereck wrote:
> Package: weston
> Version: 1.12.0-3
> Severity: normal
> 
> Dear Maintainer,
> 
> Steps to reproduce:
> Start weston from console:
>   weston
> Inside of weston, open terminal and run
>   weston --fullscreen

This works fine for me on weston 5.0.0.


signature.asc
Description: PGP signature

Bug#925914: libzmq5: GSSAPI support not available anymore

[Luca Boccassi]

Package: libzmq5
Version: 4.3.1-3
Severity: important
Justification: regression from Stretch

Dear Maintainer,

GSSAPI support is no longer built in in the version in buster/sid.

This is due to my mistake upstream when refactoring the autoconf file -
the correct autoconf variable does not get set when using pkg-config to
find the gssapi library.

This can be noted in the dpkg-buildpackage log, that correctly detects
that there's a linkage against the library but gssapi symbols are not
used:

dpkg-shlibdeps: warning: package could avoid a useless dependency if 
debian/libzmq5/usr/lib/x86_64-linux-gnu/libzmq.so.5.2.1 was not linked against 
libgssapi_krb5.so.2 (it uses none of the library's symbols)

https://buildd.debian.org/status/fetch.php?pkg=zeromq3=amd64=4.3.1-3=1548515257=0

$ objdump -T /usr/lib/x86_64-linux-gnu/libzmq.so.5.2.1 | grep gssapi | wc -l
0

The fix is simple, is already merged upstream and is also attached.
After the fix:

$ objdump -T src/.libs/libzmq.so.5.2.1 | grep gssapi | wc -l
13

Given this is a regression since stretch, it would be great if we could
get this uploaded and approved for buster.

I'm more than happy to deal with the paperwork and file a request with
the Release Team myself, given it was my mistake.

Thank you!

-- 
Kind regards,
Luca Boccassi
Author: Luca Boccassi 
Description: gssapi pkg-config check in configure.ac does not work
 correctly enable the definition in platform.hpp so that the
 gssapi support is actually built in if requested and available.
Origin: https://github.com/zeromq/libzmq/pull/3361
--- a/configure.ac
+++ b/configure.ac
@@ -472,16 +472,20 @@
 # conditionally require libgssapi_krb5
 if test "x$require_libgssapi_krb5_ext" != "xno"; then
 PKG_CHECK_MODULES([gssapi_krb5], [krb5-gssapi], [
+have_gssapi_library="yes"
 PKGCFG_NAMES_PRIVATE="$PKGCFG_NAMES_PRIVATE krb5-gssapi"
 ], [
 AC_CHECK_HEADERS(gssapi/gssapi_generic.h)
 AC_SEARCH_LIBS([gss_init_sec_context], [gssapi_krb5 gssapi],
-AC_DEFINE(HAVE_LIBGSSAPI_KRB5, [1], [Enabled GSSAPI security]),
+have_gssapi_library="yes",
 AC_MSG_ERROR(libgssapi_krb5 is needed for GSSAPI security))
 PKGCFG_LIBS_PRIVATE="$PKGCFG_LIBS_PRIVATE -lgssapi_krb5"
 ])
 fi
-AM_CONDITIONAL(BUILD_GSSAPI, test "x$require_libgssapi_krb5_ext" != "xno")
+if test "x$have_gssapi_library" = "xyes"; then
+AC_DEFINE(HAVE_LIBGSSAPI_KRB5, [1], [Enabled GSSAPI security])
+fi
+AM_CONDITIONAL(BUILD_GSSAPI, test "x$have_gssapi_library" = "xyes")
 
 # Select curve encryption library, defaults to tweetnacl
 # To use libsodium instead, use --with-libsodium (must be installed)


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

Bug#925586: FTBFS: Could not find xml-apis:xml-apis:debian

[Jongmin Kim]

Control: retitle -1 android-sdk-helper FTBFS with libgradle-core-java
Control: severity -1 important
Control: tag -1 - ftbfs

-- 
Jongmin Kim

OpenPGP key located at
https://jmkim-pgp.github.io/keys/pubkey.D39D8D29BAF36DF8.Jongmin_Kim.asc
OpenPGP fingerprint: 012E 4A06 79E1 4EFC DAAE  9472 D39D 8D29 BAF3 6DF8


signature.asc
Description: PGP signature

Bug#925898: [t-p-u, pre-approval] unblock: highwayhash/0~git20181002.c5ee50b-4

[Paul Gevers]

Control: tags -1 moreinfo

Hi Mo,

On 28-03-2019 06:06, Mo Zhou wrote:
> Please unblock package highwayhash
> 
> (explain the reason for the unblock here)
> 
> The C++ symbols changed somehow since the -3 upload, which
> renders dpkg-gensymbols failure.

I am sure there are people on the release team that are more
knowledgeable about C++ symbols, but it really helps the whole team if
you would explain why you believe, or what you did to investigate if, it
is harmless to remove this symbol.

> However, the newer snapshot
> in sid FTBFS on arm* so it would not migrate even if I fixed
> the symbol lists. That means, well unfortunately, I have to
> go through testing-proposed-updates.

"have to" is a bit strong. You could nearly always go with a "+really"
version an revert the new snapshot. (Not saying you have to do that, but
it is an option and going through unstable is a lot better for QA and
the team.)

> Does it worth the effort to save the package for Buster?
> src:highwayhash's popcon is quite low (~ 10), and it has
> no reverse dependency in the archive except src:tensorflow.
> 
> If RT doesn't bother dealing with such a t-p-u case,
> please feel free to close this bug and I'm totally fine
> with that.
> 
> (include/attach the debdiff against the package in testing)
> 
> The difference will be merely some C++ symbol updates.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924840

Paul



signature.asc
Description: OpenPGP digital signature

Bug#925913: uhubctl: autopkgtest always fails

[Graham Inggs]

Source: uhubctl
Version: 2.0.0-3
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: fails-always

Hi Maintainer

It seems uhubctl's autopkgtests have always failed on ci.debian.net [1].

Weirdly, a previous version passes in Ubuntu [2] and prevents migration 
of 2.0.0-3 there.


Regards
Graham


[1] https://ci.debian.net/packages/u/uhubctl/testing/amd64/
[2] http://autopkgtest.ubuntu.com/packages/uhubctl/disco/amd64

Bug#925594: unblock: lib3mf/1.8.1+ds-3

[John Paul Adrian Glaubitz]

Hi!

On 3/27/19 10:03 PM, Niels Thykier wrote:
> Unblocked on the assumption that the #MISSING is intentional (given it
> is the only real change). Honestly, I thought you would have to mark the
> symbol as optional ...

Good point. I will have another discussion with Torsten regarding this
to make sure the symbols file is correct.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#925586: [Android-tools-devel] Bug#925586: FTBFS: Could not find xml-apis:xml-apis:debian

[Jongmin Kim]

Control: reassign -1 src:gradle

Related links:
 - https://salsa.debian.org/java-team/gradle/merge_requests/2
 - https://salsa.debian.org/java-team/gradle/merge_requests/3

Thank you!

-- 
Jongmin Kim

OpenPGP key located at
https://jmkim-pgp.github.io/keys/pubkey.D39D8D29BAF36DF8.Jongmin_Kim.asc
OpenPGP fingerprint: 012E 4A06 79E1 4EFC DAAE  9472 D39D 8D29 BAF3 6DF8


signature.asc
Description: PGP signature