Bug#906803: RM: cipux,cipux-dog,cipux-object,cipux-passwd,cipux-rbac,cipux-rbac-simple,cipux-rpc,cipux-rpc-client,cipux-storage,cipux-task,module-build-cipux -- ROM; unused, dead upstream

[Jonas Smedegaard]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi ftpmasters,

Please remove all CipUX packages from unstable: The project is dead
upstream for several years, and not unsed anywhere in Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlt7xs4ACgkQLHwxRsGg
ASExjQ/+Nx6ko14c5C3JS0vZuhccle+JbDIuxxv8ex2S0RxNgGqrPBjZmUtSG4+r
oHug83rR/g3WsRzPHwjYvgCSItQ6BaocEGnn0qb9PB8fbiJqXvM/53qKVHm86gq4
5/PY/Te1NwpWVoKjsyfqDsJb/QiV7O49XaqHwnkOeWIbhQQUmyrieI7AM/EZmmXO
guUavcX/hGHjY2a0GD8h1gsk9LCtGQDf8OVY/GASYq7yeWp5WYLVVZCvUWoPvon2
tOXS7txirFOGmxEqDLUI421Hd0tskg2dDV/XKRe3vQJJke5krcV0V50rzwSi89jn
Nb51NUtPI3za8OyDlQF8VsN/T3UQJmOsTIOnmmjeN37Pm5/zN98+lk3nLW37tmYX
w+xBd0l/qkKQwM2+ghn1+6qxfecQFdAW86vLlvbbKun029jDlV5CMVNG/wNfySJM
0RJywL52txdXY89tmrbjHjkEJWESSgyWeCTZ4/1PrUSHG5vz8qCaOFpvSlq/YlxM
QJtWJRUASzCYf5n/5Oz5NX99/eRuOdiVVsVst5sSReGqJ00eAzAJB0BXRzx7gRUM
L4gmUBUEuDrEB51h0VptgBCnZF06gxL731TQH3LiOwUrB01WTzkkNhPsCNL2qFFk
Q+WgZddRyNIOOoiVkmy9OKiGOKysK2pPOXXqff1dtBnxzYTgI3s=
=GKjc
-END PGP SIGNATURE-

Bug#906714: paraview: FTBFS in Sid

[Juhani Numminen]

Control: tags -1 + fixed-upstream patch

Dear maintainer,

To sum up, this FTBFS is resolved by applying these upstream commits:

https://gitlab.kitware.com/paraview/paraview/commit/931c779dde8460fe32aa8a3d19956b175b96e4f9
https://gitlab.kitware.com/paraview/paraview/commit/f9c7e4b01341f45aec55f452b583c544e2557ca4

The package was successfully built on amd64 sid (cowbuilder) as well as
on Ubuntu, https://launchpad.net/ubuntu/+source/paraview/.

--
Juhani

Bug#906236: openssh: CVE-2018-15473: delay bailout for invalid authenticating user until after the packet

[Chris Lamb]

Hi Sébastien,

> Sorry, missed your email about this. I'm actually done with the patch on
> my end.

No problem. Just to clarify that:

 a) You will take the lead on stable/DSA.

 b) I'll carry on with LTS, etc.

Let me know if this is incorrect.


Regards,

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

Bug#906799: gnome-control-center: crashes or shows blank window when started outside GNOME

[Simon McVittie]

Control: retitle -1 gnome-control-center: crashes or shows blank window when 
started outside GNOME
Control: severity -1 normal
Control: found -1 1:3.28.2-1

On Tue, 21 Aug 2018 at 08:16:25 +0100, Simon McVittie wrote:
> While trying to reproduce #906750 I found that gnome-control-center from
> experimental doesn't start in a qemu VM

This is because I was starting it from outside a GNOME session (to try
to reproduce a crash that happens when Recommends were not installed, I
launched it in openbox or from a ssh session), and it respects OnlyShowIn
when deciding which panels to show. If the desktop environment is neither
GNOME nor Unity, then it doesn't show any, but then (in the experimental
version) manipulating the visibility of the wifi panel assumes that panel
is available and causes a crash.

The version in unstable doesn't crash, but it also doesn't show any
panels.

Mitigation: the menu entry for gnome-control-center itself won't show
in a non-GNOME session either (due to its use of OnlyShowIn), so this
is not something that is really supported or meant to work.

A possible workaround would be: if any panels would be shown on the
current desktop environment, proceed with that subset of panels, but if
no panels would be shown, show all of them (or those that would show in
a GNOME session) instead.

smcv

Bug#906769: arm kernels fail to boot

[Vincas Dargis]

On Mon, 20 Aug 2018 15:16:52 -0700 Vagrant Cascadian  wrote:

One "armmp-lpae" system appears to have successfully booted, but gets
many kernel messages along these lines:

[   78.638348] INFO: rcu_sched detected stalls on CPUs/tasks:
[   78.642433]  0-...: (0 ticks this GP) idle=29c/0/0 softirq=1396/1396 fqs=0
[   78.649321]  (detected by 2, t=4204 jiffies, g=283, c=282, q=41917)
[   78.655567] Task dump for CPU 0:
[   78.658770] swapper/0   R  running task0 0  0 0x
[   78.665844] rcu_sched kthread starved for 4207 jiffies! g283 c282 f0x0 
RCU_GP_WAIT_FQS(3) ->state=0x1
[   78.674972] rcu_sched   S0 7  2 0x
[   78.680506] [] (__schedule) from [] (schedule+0x50/0xa8)
[   78.687501] [] (schedule) from [] 
(schedule_timeout+0x1e0/0x464)
[   78.695231] [] (schedule_timeout) from [] 
(rcu_gp_kthread+0x574/0x908)
[   78.703447] [] (rcu_gp_kthread) from [] 
(kthread+0x118/0x130)
[   78.710894] [] (kthread) from [] 
(ret_from_fork+0x14/0x34)


I have the same case - OdroidHC1 ARM device ( armmp-lpae ) booted, but some applications kept 
hanging. Took forever to make it reboot into older kernel.

Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts

[Nuno Oliveira]

* Michael Biebl  [2018-08-20 20:01]:

On 8/20/18 14:40, Nuno Oliveira wrote:

Hi Bertrand,

I got a similar behaviour. This is probably due to dropped
NetworkManager support in the last package version by Michael Biebl.
Presently I cannot
run sucessfully a plain

/usr/sbin/ypbind

in a startup script, not even in /etc/rc.local. If this is a run after
system startup, then nis starts normally, though.



Does ypbind need the network to be up before it can start?
If so, how do you configure your network (details please, including
configuration files.)

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



Hi Michael,

Here's some more details on this:

Both the client and NIS server are on buster. The client has the latest 
package that you've uploaded (3.17.1-2), and the server still has the previous 
version (3.17.1-1+b2).


With 3.17.1-1+b2 the client had no problems with NIS, and the 
configuration has not changed. The server has other clients with 
both versions on the NIS packages, and this behaviour is reproducible. 
Presently with the latest package on the client, ypbind cannot be included 
in a startup script, but runs ok manually on an interactive shell.


I've tried to run an extra ypbind on /etc/rc.local, with a wait period 
so that the networking effects are stabilized for sure. During this 
period I'm able to login remotely into the client, so the networking is 
definitely ok. Here's the test /etc/rc.local:


#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

sleep 90
/usr/sbin/service rpcbind restart
strace /usr/sbin/ypbind 2> /tmp/strace-ypbind-rc.local
/usr/sbin/service nis restart
/bin/mount -a

# Log task date:
/bin/date > /tmp/rclocal.date
exit 0


The network is set statically:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug enp3s0
auto enp3s0
iface enp3s0 inet static
   address 10.1.214.129
   netmask 255.255.255.128
   network 10.1.214.128
   broadcast 10.1.214.255
   gateway 10.1.214.254
   # dns-* options are implemented by the resolvconf package, if
   # installed
   dns-nameservers 10.1.214.254 10.1.214.30
   dns-search eq.uc.pt


and we avoid using NetworkManager:

host:/etc/NetworkManager# more NetworkManager.conf
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false


I've attached the strace files for ypbind both for the rc script and the 
interactive shell, but I see no big differences between these cases.


My guess is that this problem related to:

nis (3.17.1-1) unstable; urgency=medium

 * ypbind 1.38, reenable Network Manager support to fix systemd
   breakage killing ypbind after it daemonizes (closes: #834298).

-- Mark Brown   Tue, 16 Aug 2016 11:22:19 +0100

Apparently Network Manager support in NIS was introduced to avoid ypbind 
from being killed by systemd. In fact, after system startup I see no 
ypbind process running in the client. With the previous package version, 
I see a


/usr/sbin/ypbind -no-dbus

process running, which is required for NIS to work properly. In fact, 
with the new client, I cannot even run ypbind with this option:


host:~# /usr/sbin/ypbind -no-dbus
Usage:
   ypbind [-broadcast | -ypset | -ypsetme] [-f configfile]
 [-no-ping] [-broken-server] [-local-only] [-i ping-interval]
 [-r rebind-interval] [-debug] [-verbose] [-n | -foreground]
   ypbind -c [-f configfile]
   ypbind --version


ypbind with no arguments runs fine though. Any suggestion on how to fix 
this messy situation?


Thanks,

Nuno.
execve("/usr/sbin/ypbind", ["/usr/sbin/ypbind"], 0x7ffefbe146e0 /* 7 vars */) = 0
brk(NULL)   = 0x55ef94786000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=211744, ...}) = 0
mmap(NULL, 211744, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7ffa50efa000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libsystemd.so.0", O_RDONLY|O_CLOEXEC) = 
3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\365\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=569456, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7ffa50ef8000
mmap(NULL, 574040, PROT_READ, 

Bug#906775: hamlib: FTBFS in buster/sid (makeinfo: command not found)

[Ervin Hegedüs]

Hi Santiago,

On Mon, Aug 20, 2018 at 10:50:13PM +, Santiago Vila wrote:
> Package: src:hamlib
> Version: 3.1-8
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> I tried to build this package in buster but it failed:
> 
> 
> [...]
>  debian/rules build-indep
> dh_testdir
> dh_autoreconf
> aclocal: overwriting 'macros/libtool.m4' with '/usr/share/aclocal/libtool.m4'
> aclocal: overwriting 'macros/ltoptions.m4' with 
> '/usr/share/aclocal/ltoptions.m4'
> 
> [... snipped ...]

[...]
 
> /<>/build-aux/missing: line 81: makeinfo: command not found
> WARNING: 'makeinfo' is missing on your system.
>  You should only need it if you modified a '.texi' file, or

this is a known problem - we don't know the reason exactly
(perhaps the texinfo package changed - but the problem came to
SID/Buster after an upgrade).

https://lists.debian.org/debian-hams/2018/07/msg1.html

The workaround is just install the texinfo package manually.

We're working on Hamlib 3.2, hope that it will released soon (see
the mail thread above).



73, Ervin
HA2OS

Bug#885740: gnomekiss: Port to GTK+ 3

[Yavor Doganov]

Yavor Doganov wrote:
> Please find attached a patch that ports the program to GTK+ 3.

I wasn't careful enough; my patch introduces memory leaks.  Please
find attached an updated version (compressed); please use it instead.
Thanks.


gtk3-port.patch.xz
Description: Binary data

Bug#906796: [Debian-science-sagemath] Bug#906796: sagemath: Sage crashes at startup (segfault in pari modules)

[Doug Torrance]

On 08/21/2018 04:13 AM, Tobias Hansen wrote:

Control: block -1 by 905434 905300

This is expected after a major pari update. sagemath 8.3 is almost ready to be 
uploaded, major things we have to do:

- fix build failures in fpylll and gfan
- fix at least the 24 failing sagemath doctests in 
sage/repl/ipython_kernel/install.py [1]

If gfan 0.6.2 can't be fixed we could still use version 0.5...


I forwarded the gfan build failure upstream a few weeks ago but haven't 
gotten a response yet.  I've tried debugging it on my own but haven't 
figured anything out yet.


The build failure is from a test failing on 32-bit architectures.  We 
could always just skip that test on those architectures for a short-term 
fix.  I can work on that later.


Doug

Bug#906715: ITP: lloconv -- command line document converter using libreofficekit

[Félix Sipma]

OK, thanks for taking time to answer this!


signature.asc
Description: PGP signature

Bug#906804: reprepro: Homepage URL is invalid

[Fabien Givors (Debian)]

Package: reprepro
Version: 5.1.1-1
Severity: minor

Dear maintainer,

According to the control file, the homepage url is
http://mirrorer.alioth.debian.org/

However, this page doesn't exist anymore, and I don't know where/if it has
moved.

BTW, this broken link can be found here: 
https://wiki.debian.org/DebianRepository/SetupWithReprepro (and in many 
other places all arround the internet)


Cheers,

--
fabien

Bug#906805: lxc-start is affected by CVE-2018-10892

[Reco]

Package: lxc
Version: 1:2.0.7-2+deb9u2
Severity: normal

Dear Maintainer,

both current stable and unstable versions of LXC are affected by issue
similar to CVE-2018-10892 - arbitrary modification of /proc/acpi
contents from inside the container.

Suggested mitigation of this issue would be including:

deny /proc/acpi/* rwx,

to all Apparmor profiles that are provided by lxc package.

And, since this can be considered a security issue, feel free to tag the
bug as 'serious'.

Sincerely yours, Reco

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

Kernel: Linux 4.16.0-0.bpo.2-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)

Versions of packages lxc depends on:
ii  init-system-helpers  1.48
ii  libapparmor1 2.11.0-3+deb9u2
ii  libc62.24-11+deb9u3
ii  libcap2  1:2.25-1
ii  libgnutls30  3.5.8-5+deb9u3
ii  liblxc1  1:2.0.7-2+deb9u2
ii  libseccomp2  2.3.1-2.1
ii  libselinux1  2.6-3+b3
ii  lsb-base 9.20161125
ii  python3  3.5.3-1
ii  python3-lxc  1:2.0.7-2+deb9u2

Versions of packages lxc recommends:
pn  bridge-utils  
pn  debootstrap   
pn  dirmngr   
pn  dnsmasq-base  
ii  gnupg 2.1.18-8~deb9u2
ii  iptables  1.6.0+snapshot20161117-6
pn  libpam-cgfs   
pn  lxcfs 
ii  openssl   1.1.0f-3+deb9u2
ii  rsync 3.1.2-1+deb9u1
pn  uidmap

Versions of packages lxc suggests:
ii  apparmor 2.11.0-3+deb9u2
pn  btrfs-tools  
ii  lvm2 2.02.168-2

-- Configuration Files:
/etc/apparmor.d/lxc/lxc-default changed [not included]
/etc/apparmor.d/lxc/lxc-default-cgns changed [not included]
/etc/apparmor.d/lxc/lxc-default-with-mounting changed [not included]
/etc/apparmor.d/lxc/lxc-default-with-nesting changed [not included]

-- debconf-show failed

Bug#906807: Can't send reply to encrypted message

[Jeffrey Ratcliffe]

Package: claws-mail
Version: 3.16.0-2
Severity: normal

When replying to an encrypted message, on hitting "send", I get the error:
"Could not queue message for sending. Couldn't get recipient encryption key"

However, Privacy System=None  is selected in Options.

On selecting a different privacy system, I can send the message.



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

Kernel: Linux 4.17.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (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 claws-mail depends on:
ii  libatk1.0-0  2.28.1-1
ii  libc62.27-5
ii  libcairo21.15.10-3
ii  libcompfaceg11:1.5.2-5+b2
ii  libcurl3-gnutls  7.61.0-1
ii  libdb5.3 5.3.28-13.1+b1
ii  libenchant1c2a   1.6.0-11.1
ii  libetpan20   1.8.0-1
ii  libexpat12.2.6-1
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libfribidi0  1.0.5-1
ii  libgdk-pixbuf2.0-0   2.36.12-1
ii  libglib2.0-0 2.56.1-2
ii  libgnutls30  3.5.19-1
ii  libgtk2.0-0  2.24.32-2
ii  libice6  2:1.0.9-2
ii  libldap-2.4-22.4.46+dfsg-5
ii  liblockfile1 1.14-1.1
ii  libpango-1.0-0   1.42.1-2
ii  libpangocairo-1.0-0  1.42.1-2
ii  libpangoft2-1.0-01.42.1-2
ii  librsvg2-2   2.40.20-2
ii  libsasl2-2   2.1.27~101-g0780600+dfsg-3.1
ii  libsm6   2:1.2.2-1+b3
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages claws-mail recommends:
ii  aspell-en [aspell-dictionary]  2017.08.24-0-0.1
ii  claws-mail-i18n3.16.0-2
ii  xfonts-100dpi  1:1.0.4+nmu1
ii  xfonts-75dpi   1:1.0.4+nmu1

Versions of packages claws-mail suggests:
pn  claws-mail-doc 
ii  claws-mail-tools   3.16.0-2
ii  firefox-esr [www-browser]  52.9.0esr-1
pn  gedit | kwrite | mousepad | nedit  
ii  w3m [www-browser]  0.5.3-36+b1

-- no debconf information

Bug#906796: sagemath: Sage crashes at startup (segfault in pari modules)

[Giovanni Mascellani]

Package: sagemath
Version: 8.2-5
Severity: important

Dear Maintainer,

when I start sage, it immediately crashes with the attached crash
report. Before running sage I removed the directories .ipython, .sage
and .local/lib/python* (which I discovered contained some Python modules
that were executed by sage upon startup).

The end of the crash report seems to mention a segmentation fault in
some pari module, but I am not able to extract more information from it.

Thanks, Giovanni.


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

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

Versions of packages sagemath depends on:
ii  cysignals-tools  1.6.7+ds-4
ii  cython   0.28.4-1
ii  ecl  16.1.2-4+b1
ii  eclib-tools  20171002-1+b3
ii  f2c  20160102-1
ii  fflas-ffpack 2.3.2-2
ii  flintqs  1:1.0-3
ii  gap-core 4r8p8-3
ii  gfan 0.5+dfsg-6
ii  gmp-ecm  7.0.4+ds-3
ii  ipython  5.5.0-1
ii  iso-codes3.79-1
ii  jmol 14.6.4+2016.11.05+dfsg1-3.1
ii  lcalc1.23+dfsg-7
ii  less 487-0.1+b1
ii  libatlas3-base [liblapack.so.3]  3.10.3-7+b1
ii  libblas3 [libblas.so.3]  3.8.0-1+b1
ii  libbrial-groebner3   1.2.0-2
ii  libbrial31.2.0-2
ii  libc62.27-5
ii  libcdd-tools 094h-1+b1
ii  libcliquer1  1.21-2
ii  libec3   20171002-1+b3
ii  libecm1  7.0.4+ds-3
ii  libflint-2.5.2   2.5.2-18
ii  libflint-arb21:2.12.0-3
ii  libgap-sage-44.8.8+3+20160327g69a66f0+dsx-1
ii  libgcc1  1:8.2.0-4
ii  libgd3   2.2.5-4
ii  libgivaro9   4.0.4-2
ii  libglpk404.65-2
ii  libgmp10 2:6.1.2+dfsg-3
ii  libgmpxx4ldbl2:6.1.2+dfsg-3
ii  libgsl23 2.5+dfsg-4
ii  libgslcblas0 2.5+dfsg-4
ii  libiml0  1.0.4-1+b2
ii  libjs-mathjax2.7.4+dfsg-1
ii  libjs-three  80+dfsg2-2
ii  liblapack3 [liblapack.so.3]  3.8.0-1+b1
ii  liblfunction01.23+dfsg-7
ii  liblinbox-1.5.2-01.5.2-2
ii  liblinboxsage-1.5.2-01.5.2-2
ii  liblrcalc1   1.2-2+b1
ii  libm4ri-0.0.20140914 20140914-2+b1
ii  libm4rie-0.0.2015090820150908-2
ii  libmpc3  1.1.0-1
ii  libmpfi0 1.5.3+ds-2
ii  libmpfr6 4.0.1-1
ii  libntl35 10.5.0-2
ii  libopenblas-base [liblapack.so.3]0.3.2+ds-1
ii  libpari-gmp-tls5 2.9.5-1
ii  libplanarity03.0.0.5-3
ii  libpng16-16  1.6.34-2
ii  libppl14 1:1.2-3
ii  libpynac17   0.7.19-2
ii  libratpoints-2.1.3   1:2.1.3-1+b2
ii  libreadline7 7.0-5
ii  librw0   0.8+ds-1
ii  libsingular4 1:4.1.0-p3+ds-2+b3
ii  libstdc++6   8.2.0-4
ii  libsymmetrica2   2.0+ds-5
ii  libzn-poly-0.9   0.9-3+b2
ii  maxima-sage  5.39.0+ds-3
ii  maxima-sage-doc  5.39.0+ds-3
ii  maxima-sage-share5.39.0+ds-3
ii  nauty2.6r10+ds-1
ii  octave

Bug#906750: gnome-control-center: Does not start. Missing dependency avahi-daemon

[Simon McVittie]

Control: tags -1 + moreinfo unreproducible

On Mon, 20 Aug 2018 at 18:14:49 +0200, k0r155ov...@mailbox.org wrote:
> foo@bar:~$ gnome-control-center -v
> 17:47:38.0368  sharing-cc-panel:DEBUG: Error calling 
> GetHostNameFqdn: DBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The 
> name org.freedesktop.Avahi was not provided by any .service files
> Speicherzugriffsfehler

Please try to repeat this crash (remove avahi-daemon) with an English
locale (LC_ALL=C.UTF-8), and get a backtrace:
https://wiki.debian.org/HowToGetABacktrace

I couldn't reproduce this crash myself on a minimal virtual machine,
because I get a different crash instead, which is not fixed by installing
avahi-daemon (I've opened a separate bug). On my (non-minimal) laptop,
I couldn't trigger this crash by removing avahi-daemon.

It might also help to set the environment variable G_MESSAGES_DEBUG=all
before running gnome-control-center: this would result in more messages
being printed.

smcv

Bug#816733: PTS doesn't understand RFS bugs

[Raphael Hertzog]

Control: retitle -1 tracker.debian.org: RFS entries are hidden by other WNPP 
entries

On Tue, 21 Aug 2018, Paul Wise wrote:
> > I think this bug does not apply to tracker.debian.org.
> 
> Actually, it does (although the summary message is less severe):

Hum, before doing this I checked a few packages listed on
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=sponsorship-requests;dist=unstable

For example https://tracker.debian.org/pkg/raphael or
https://tracker.debian.org/pkg/cplay

So it seems that the ITA or O entry is taking precedence and is hiding the
RFS one. Just confirmed this in the source code:

package_name, wnpp_type, bug_id = line.split('|')[0].split()

We only take into account the first entry of each line
in https://qa.debian.org/data/bts/wnpp_rm

So there are actually two issues here. I just fixed the fact that RFS is unknown
but the other issue is still pending.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#906801: RM: libbitcoin -- ROM; unused

[Jonas Smedegaard]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi ftpmasters,

Please remove libbitcoin from unstable: It is unused in Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlt7xG8ACgkQLHwxRsGg
ASEW4w/7BwFsfCyty78So/okSRmN4O+xbv6pV5VBRNWWEn2XWDTLOw9LITqDBADS
I9EOmEm8odHHkimGu/fQywJDVFDC7m/qrTnMWDKsQd77yEr4GN+Q3vzyq0L2JXCe
aa4jeU3YeYwEAOS2uTM7oAnqIRvlTjQDBZ+J/5gtz01A4OjV8Q7v4PyrXQ2qqLpH
QmJMV8//EVveUBlHY+aBwRSTdQnmRY04tkKIAqejhdez8dQo84qt+KTSX7nmzf47
M8QxtJh5CXmTKHwKw9jgR9CqElg+GG5/IlMjDYQzS6bZJ+6eXf66sXYd4+NGWnLc
TMil0xcwSKWmoCTlv2BXaBTK8jG0ByKt0GUBjpTPo2g+AMzOWLR2G6IRHP8tpbad
9LjDHtWUrwZyWs6Ewd/kv9B5O/JclmIYhmThhTv0RTjzLmyPIp2L/vgzsAUpniqu
Qi6GL5C0dOSa3z/3mlrbLmQekfKP6NXKue/MgZws7xYSw2aRHUaSROaazzD3XF7A
E08umVLbH+at//7wTOUJ4gE4sM7d3ndJ6LIJK0iiO/dF7oa/v9THe7F/osvxZagn
v/l9A/1o7BykaYTGSD1H90CVYwufpzP7SAq7pledM/Xv/VcCcKuXlmNRTrtruPeK
M5dAAjPWY68LPtAQdodJjUa/aDGVHp+x9HaJXUSzC6fAKVmQAMY=
=jI8c
-END PGP SIGNATURE-

Bug#905396: CVE-2018-12482 fixed upstream

[Xavier Guimard]

According to
https://github.com/OCSInventory-NG/OCSInventory-Server/issues/129,
CVE-2018-12482 has been fixed upstream (2.5)




signature.asc
Description: OpenPGP digital signature

Bug#905396: Version 2.5 is still vulnerable

[Xavier Guimard]

Looking at ocsinventory-server upstream changes, no commits deals with
CVEs and at least CVE-2018-12483 is still in 2.5 (no change on this file)



signature.asc
Description: OpenPGP digital signature

Bug#906797: Better reporting when deps are unsatisfiable

[Julien Puydt]

Package: autopkgtest
Version: 5.5
Severity: wishlist

Hi,

when a tested package has unsatisfiable deps, autopkgtest reports only 
that the package had such a problem -- no information about what is 
actually triggering the problem is given, which makes it harder to debug 
than should be.


In the log, I had first:

Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) autopkgtest-satdep:amd64 < 0 @iU mK Nb Ib >
Broken autopkgtest-satdep:amd64 Depends on node-nanomatch:amd64 < none | 
1.2.13-1 @un uH >
  Considering node-nanomatch:amd64 1 as a solution to 
autopkgtest-satdep:amd64 -2

  Removing autopkgtest-satdep:amd64 rather than change node-nanomatch:amd64
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done

then later:

autopkgtest: WARNING: package node-nanomatch is not installed though it 
should be

require  FAIL badpkg
blame: node-nanomatch_1.2.13-1.dsc
badpkg: Test dependencies are unsatisfiable. A common reason is that 
your testbed is out of date with respect to the archive, and you need to 
use a current testbed or run apt-get update or use -U.


The common reason given wasn't applicable.

jpuydt on irc.debian.org

Bug#906799: gnome-control-center/experimental: crashes on a qemu VM: cc_shell_model_set_panel_visibility: assertion failed: (valid)

[Simon McVittie]

Package: gnome-control-center
Version: 1:3.29.90-1
Severity: important

While trying to reproduce #906750 I found that gnome-control-center from
experimental doesn't start in a qemu VM, possibly because the VM does not
have any wifi devices:

user@host:~$ DISPLAY=:0 gdb gnome-control-center
...
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)

Thread 1 "gnome-control-c" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x71a622f1 in __GI_abort () at abort.c:79
#2  0x77729fa5 in g_assertion_message () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7772a00a in g_assertion_message_expr () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x556a2af1 in cc_shell_model_set_panel_visibility 
(self=0x55efbd60,
id=id@entry=0x556c6ba5 "wifi", 
visibility=visibility@entry=CC_PANEL_VISIBLE_IN_SEARCH)
at ../shell/cc-shell-model.c:458
#5  0x55666254 in update_panel_visibility (client=) at 
../panels/network/cc-wifi-panel.c:112
#6  0x55666ebe in cc_wifi_panel_static_init_func () at 
../panels/network/cc-wifi-panel.c:141
#7  0x555abbb3 in cc_panel_loader_fill_model (model=0x55efbd60) at 
../shell/cc-panel-loader.c:214
#8  0x555afcc8 in setup_model (shell=0x560e23b0) at 
../shell/cc-shell-model.h:31
#9  cc_window_constructed (object=0x560e23b0) at ../shell/cc-window.c:767
#10 0x779e2760 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x779e4420 in g_object_new_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x779e4799 in g_object_new () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x555b036c in cc_window_new (application=0x55a6e320, 
model=model@entry=0x55efbd60)
at ../shell/cc-window.c:885
#14 0x555aa62a in cc_application_startup (application=0x55a6e320) 
at ../shell/cc-application.c:265
#15 0x779dcf6d in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x779efe0e in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x779f83f5 in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x779f8e0f in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x77cc30a2 in g_application_register () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#20 0x77cc38b7 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#21 0x77cc3c46 in g_application_run () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#22 0x555a9c51 in main (argc=, argv=) at 
../shell/main.c:57

The failing assertion is:

  /* If we don't find any panel with the given id, we'll iterate until
   * valid == FALSE, so we can use this variable to determine if the
   * panel was found or not. It is a programming error to try to set
   * the visibility of a non-existant panel.
   */
  g_assert (valid);

but perhaps the wifi panel doesn't always appear?

This does not seem to be the same crash as #906750 - installing
avahi-daemon, or installing gnome-core and all of gnome-control-center's
Recommends, does not fix it.

smcv

Bug#906800: RM: sugar-toolkit -- ROM; obsolete

[Jonas Smedegaard]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi ftpmasters,

Please remove sugar-toolkit from unstable.

It is stabke code not expected to evolve, but unfortunately dependencies
is getting removed from debian now (see bug#790158, #888960).


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlt7whsACgkQLHwxRsGg
ASHgPw//ZODgJlMdjEMFMAhvUfkgi+c4Qz4s4xNq6g9jFJbiJzd54EZxcAusKeu9
ksB5oOQpueOsDR/bDXT60wIMdF1IgmOVYs36x/olFjWA0nNlHkL7n4CR88usSydV
M94eUYrq9Uk5/8GbDnKtz/pDceQ+6FmRGjsFursEs0ZEbtPI8S2kjVFGzsWpZCXs
JgcMVsUaPHv+PKrgo4PCm1IgWZzBRaBTffSdefL+xSNOi45jptyKXESpEY8IIZFl
Jj7syIZulkh9OLDzQymO1Gg5TdCUWPxRS2CXZy2qjv3ScfJLFK1YZuLJ0YYzo5c1
g3dbce3EZ22ErAnL7eD5VfRmkwlGzvo4csxXbm7o76YLRkZnPMur4u0wVU+Xubsj
30xHxxlABs55IyyZS+2Lf4zf1cMuUUN7eYVEB7wY9cTcChqgpkMX+3lAgqTZYOGH
FrKla1/4hFktk530C6g4yVRdFXkSX5QgduAhgyUZksMWC3dZvdjiZgkV692Wdxnl
3xN5EPjHe2CNnYXRjM7UJd8IAwESOS4newJCLOOaS8p/cohO20Ii6ulij7lAuwh5
aYMgymEbBFJaT7YE/XodFfltbFiUW3S1Wtu6oxr/pGq5unjYonqi8YKJ+TKZNWtH
hjHXaqbs2pOUwy08JUzzx+FF4il/UBE2QbYJMb/AEOcxZbfHE6s=
=peez
-END PGP SIGNATURE-

Bug#906800: RM: sugar-toolkit -- ROM; obsolete

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2018-08-21 09:41:18)
> Please remove sugar-toolkit from unstable.

Please also remove the following reverse dependencies:

sugar-irc-activity
sugar-jigsawpuzzle-activity
sugar-physics-activity
sugar-poll-activity

Those are all fringe packages having received no love in Debian for a 
long time - they can be reintroduced later if modernized upstream.


 - Jonas

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

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


signature.asc
Description: signature

Bug#906708: Bug#906753: Acknowledgement (GCC's -O2 optimization breaks floating point precision or something else)

[Matthias Klose]

Control: tags -1 important
Control: forwarded -1 https://gcc.gnu.org/PR87036

On 20.08.2018 21:53, Lumin wrote:
> This is the minimal code for repro #906753:
> 
> OK with -O0, FAIL with -O2 on i386, ppc64el, ...

that always failed on i386 and ppc64el with -O2, so not a regression. You talked
about other architectures, but don't name these with the reduced test case.

> 
> masssq1 and masssq2 are computed from the same vector [1.1, 2.2, 3.3, 4.4],
> but the results are different!
> 
> ==
> 
> #include 
> #include   // for swap
> #include 
> 
> namespace HepMC {
> class FourVector {
> public:
>   double m_x, m_y, m_z, m_t;
>   FourVector( double xin, double yin, double zin, double tin=0) : m_x(xin), 
> m_y(yin), m_z(zin), m_t(tin) {}
>   inline double m2() const {
> return m_t*m_t - (m_x*m_x + m_y*m_y + m_z*m_z);
>   }
>   inline double m() const {
> double mm = m2();
> return mm < 0.0 ? -std::sqrt(-mm) : std::sqrt(mm);
>   }
> };
> } // HepMC
> 
> int main()
> {
>   double eps = 1.e-15; // allowed differnce between doubles
> 
>   // FourVector
>   HepMC::FourVector vector(1.1,2.2,3.3,4.4);
>   HepMC::FourVector v4(1.1,2.2,3.3,4.4);
> 
>   //vector = v4;
> 
>   double masssq1 = v4.m2();
>   double mass1 = v4.m();
>   double masssq2 = vector.m2();
>   double mass2 = vector.m();
> 
>   if( fabs( masssq1 - masssq2 ) > eps ) {
>  std::cout << "different mass sq values: " << masssq1 << " " << masssq2 
> << std::endl;
>  std::cout << "difference is : " << ( masssq1 - masssq2 ) << std::endl;
>   }
> 
>   return 0;
> }
> 

Bug#906802: RM: sipwitch -- ROM; unused, possibly dead upstream

[Jonas Smedegaard]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi ftpmasters,

Please remove sipwitch from unstable: It has received no love, neither
in Debian nor upstream, for several years.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlt7xRQACgkQLHwxRsGg
ASEs5g//dFoIwHwL+rm5itqQEWhikmuKneLnrx34aWwhAVXhB0qIBh96r0rzPQ6y
4fE28fwMHI3cGcOwULDZ+kn3agvcxwb0QV7DfyxZn+//8bcHSRLgkmIlgCAI75vW
tB/HTXq7r46mNEyootO9/Aaywtvr2Rpqh5kCQpgduPtFsOgYQFZyc5ZU+ogdyeIM
/NiUdJiW5LC2xiA/RCknmJM50YD1Rn/cxC4xfBaON7QuJLFOzVGtEOPMbm4wysLf
8BUfM/PicGRx93ozA04yE7ZPDibgd75gl350UdPoKve17huF2REQ4seMVflGywM4
JNkBRT5+LMnW87Hg8lwExVdKAQjEP1hAK5do94kpdkzMMU13vMCgGAEjVPpgCR/y
yHJG+xm6Jqyikgxjfph+j6USsVLBQA8MsC9H+RY1Ih3FShCHOYAXx3xAwt1IplGr
mq0wKP25a1QMZj9rv2zsHHF7BTiEiRJbj8zypapRAt87ln7ukY58z75fiaXxv4kn
yQEU/HtQpFvOecP11LE2E8dmWsN1+36cWHgA1fPTi9fMZ2NG7b/6kgfNGSJvkszD
t93pt6flPrkd9oD52CrXiUDzrtmEKavqVQhaz4Lw1PhnH5MRhBBUtwzQmT05RhS6
eXKOuifF1NuzAfgrDpOMBMK7jsZ4i2DZAYPRasgcbmlcX8gKrNg=
=4aM8
-END PGP SIGNATURE-

Bug#906236: openssh: CVE-2018-15473: delay bailout for invalid authenticating user until after the packet

[Chris Lamb]

Chris Lamb wrote:

> > openssh: CVE-2018-15473: delay bailout for invalid authenticating
> > user until after the packet
> 
> I've started on a patch for wheezy (WIP attached).
> 
> Would the security team be interested in one for stretch? If so, I can
> return with a proposed debdiff.

Gentle ping on this?


Regards,

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

Bug#906744: dico: FTBFS in buster/sid (makeinfo: command not found)

[أحمد المحمودي]

reassign 906744 automake
quit

  geda-gaf and dico FTBFS on Debian after automake got updated to 1.16, 
  as the following happens during build[2]:

 Making all in scheme-api
 make[4]: Entering directory '/<>/docs/scheme-api'
 Updating ./version.texi
 make[4]: Leaving directory '/<>/docs/scheme-api'

  which later triggers rebuild of info files during 'make check':

> Making check in doc
> make[3]: Entering directory '/<>/doc'
> restore=: && backupdir=".am$$" && \
> am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
> rm -rf $backupdir && mkdir $backupdir && \
> if (/bin/bash /<>/build-aux/missing makeinfo --version) 
> >/dev/null 2>&1; then \
>   for f in dico.info dico.info-[0-9] dico.info-[0-9][0-9] dico.i[0-9] 
> dico.i[0-9][0-9]; do \
> if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
>   done; \
> else :; fi && \
> cd "$am__cwd"; \
> if /bin/bash /<>/build-aux/missing makeinfo -I ../imprimatur -D 
> DISTRIB  -I . \
>  -o dico.info dico.texi; \
> then \
>   rc=0; \
>   CDPATH="${ZSH_VERSION+.}:" && cd .; \
> else \
>   rc=$?; \
>   CDPATH="${ZSH_VERSION+.}:" && cd . && \
>   $restore $backupdir/* `echo "./dico.info" | sed 's|[^/]*$||'`; \
> fi; \
> rm -rf $backupdir; exit $rc
> /<>/build-aux/missing: line 81: makeinfo: command not found
> WARNING: 'makeinfo' is missing on your system.
>  You should only need it if you modified a '.texi' file, or
>  any other file indirectly affecting the aspect of the manual.
>  You might want to install the Texinfo package:
>  
>  The spurious makeinfo call might also be the consequence of
>  using a buggy 'make' (AIX, DU, IRIX), in which case you might
>  want to install GNU make:
>  
> make[3]: *** [Makefile:1263: dico.info] Error 127

  Adding texinfo to build-dep would get around the FTBFS, but I 
  am not convinced with it. Could you advise me us as whether this is a 
  problem in automake 1.16 or something needs to be fixed in dico & 
  geda-gaf build scripts, or if adding texinfo to build-deps is actually 
  the proper way to go ?

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#878442: rmstar change

[Matus UHLAR - fantomas]

Hello,

it's apparently the change in tcsh changelog that created this problem:

41. V6.19.00 - 20150521
40. V6.18.05 - 20150510
...
 9. make rmstar interruptible on linux
...
following commit.

https://github.com/tcsh-org/tcsh/commit/b3933b3364549c0ea451b918e0d20185444ef297

I have reported this on github:

https://github.com/tcsh-org/tcsh/issues/5

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
2B|!2B, that's a question!

Bug#906806: Show artwork authorship in bits.debian.org posts

[Laura Arjona Reina]

Package: press
Severity: normal
X-Debbugs-CC: debian-public...@lists.debian.org

We need to find a way to show authorship of the artwork that is present/inserted
in the bits.debian.org posts.

Pasting here an extract of conversation in IRC #debian-publicity, so it does not
get lost:

Currently attribution is in the image alt text (but that is only shown when the
image is not shown in some browsers) and full name + license in git.

Simply adding the person as one more author is not good because the authors get
links automatically but the string is taken as one author (see
https://bits.debian.org/author/ ).

Ideally it should be something that goes in the metadata of the post, and then
automatically written in the post.

Another approach is to add a few fields for every image/multimedia content in
every post and then a pelican plugin reads this like in the translations and
inserts the proper HTML when building the blog; it would need at least: author,
license, and caption: yes/no (not every image needs a caption with the author)

To take into account: a post can have more than one image, we might want the
plugin to do the translations automatically adding the "Image by" in all the
languages we usually translate but it also can default to English in a very
first initial version.

Cheers
-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

Bug#666189: sshfs unable to handle hardlinks properly

[Vincent Lefevre]

Control: tags -1 - moreinfo + upstream
Control: forwarded -1 https://github.com/libfuse/sshfs/issues/109

On 2016-08-25 16:31:26 +0200, Louis-David Mitterrand wrote:
> In order to save an attachement on a sshfs mount with mutt I have to
> use "sshfs -odisable_hardlink"

Concerning Mutt, the problem will probably be avoided soon:

  https://gitlab.com/muttmua/mutt/issues/61

In short, the check of the stat structures (which contain the inode
number, in particular, which leads to the error) is probably useless.

But personally, I think that "sshfs -odisable_hardlink" is a safer
solution in general, until hard links are properly implemented in
sshfs.

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

Bug#906371: Changes in alter-sequence-alignment break build of jmodeltest (Was: Bug#906371: jmodeltest: FTBFS in buster/sid)

[Andreas Tille]

Hi,

On Mon, Aug 20, 2018 at 12:39:21AM +0200, Emmanuel Bourg wrote:
> > do you have any hint how to deal with this issue?
> 
> The actual error is:
> 
> [javac]
> /build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:28:
> error: package parser does not exist
> [javac] import parser.ParseException;
> [javac]  ^
> [javac]
> /build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:29:
> error: package converter does not exist
> [javac] import converter.Converter;
> [javac] ^
> [javac]
> /build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:30:
> error: package converter does not exist
> [javac] import converter.DefaultFactory;
> [javac] ^
> [javac]
> /build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:31:
> error: package converter does not exist
> [javac] import converter.Factory;
> [javac] ^
> 
> There is an issue with a dependency (alter-sequence-alignment maybe?),
> the Java version isn't to blame here.

Good catch.  The latest upstream version of alter-sequence-alignment has
split these to an additional alter-lib.jar and the time of the build
failure of jmodeltest correlates with the upload of
alter-sequence-alignment 1.3.4-1.  But now the question is:  How to
teach the jmodeltest build system to use alter-lib.jar.  I think adding
it to debian/manifest[1] is needed to *run* jmodeltest but it surely
does not help at build time.  I have not found any place where the
build system specifies the needed jars. :-(

Any hint?

Kind regards

  Andreas.


[1]

-- 
http://fam-tille.de

Bug#906798: sphde ftbfs at least on s390x (where it built before)

[Matthias Klose]

Package: src:sphde
Version: 1.4.0-1
Severity: serious
Tags: sid buster

according to the s390x build logs:

bin/bash ../libtool  --tag=CXX --silent  --mode=compile g++ -DHAVE_CONFIG_H -I.
-I..   -Wdate-time -D_FORTIFY_SOURCE=2 -D__SASSIM__ -Wall -Werror
-Wwrite-strings -Woverloaded-virtual -pthread -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -mhtm -c -o libsphde_la-sphmultipcqueue.lo `test -f
'sphmultipcqueue.cpp' || echo './'`sphmultipcqueue.cpp
sphmultipcqueue.cpp: In function 'void* SPHMPMCQInitInternal(void*, sas_type_t,
block_size_t, unsigned int, unsigned int)':
sphmultipcqueue.cpp:81:16: error: 'PPC_FEATURE2_HAS_HTM' was not declared in
this scope
  if ((hwcap2 & PPC_FEATURE2_HAS_HTM) == 0) {
^~~~
sphmultipcqueue.cpp: In function 'void* 
SPHMPMCQAllocStrideDirectHTM(SPHMPMCQ_t)':
sphmultipcqueue.cpp:348:3: error: 'TM_buff_type' was not declared in this scope
   TM_buff_type TM_buff;
   ^~~~
sphmultipcqueue.cpp:358:19: error: 'TM_buff' was not declared in this scope
   if (__TM_begin (TM_buff) == _HTM_TBEGIN_STARTED) {
   ^~~
sphmultipcqueue.cpp: In function 'void*
SPHMPMCQGetNextCompleteDirectHTM(SPHMPMCQ_t)':
sphmultipcqueue.cpp:429:3: error: 'TM_buff_type' was not declared in this scope
   TM_buff_type TM_buff;
   ^~~~
sphmultipcqueue.cpp:430:19: error: 'TM_buff' was not declared in this scope
   if (__TM_begin (TM_buff) == _HTM_TBEGIN_STARTED) {
   ^~~
make[3]: *** [Makefile:1555: libsphde_la-sphmultipcqueue.lo] Error 1
make[3]: *** Waiting for unfinished jobs
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile:544: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:413: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j2 returned exit code 2
make: *** [debian/rules:11: build-arch] Error 2

Bug#906796: sagemath: Sage crashes at startup (segfault in pari modules)

[Tobias Hansen]

Control: block -1 by 905434 905300

This is expected after a major pari update. sagemath 8.3 is almost ready to be 
uploaded, major things we have to do:

- fix build failures in fpylll and gfan
- fix at least the 24 failing sagemath doctests in 
sage/repl/ipython_kernel/install.py [1]

If gfan 0.6.2 can't be fixed we could still use version 0.5...


[1] https://people.debian.org/~thansen/sage-test-status-experimental.html

On 08/21/2018 09:00 AM, Giovanni Mascellani wrote:
> Package: sagemath
> Version: 8.2-5
> Severity: important
>
> Dear Maintainer,
>
> when I start sage, it immediately crashes with the attached crash
> report. Before running sage I removed the directories .ipython, .sage
> and .local/lib/python* (which I discovered contained some Python modules
> that were executed by sage upon startup).
>
> The end of the crash report seems to mention a segmentation fault in
> some pari module, but I am not able to extract more information from it.
>
> Thanks, Giovanni.
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
> (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), 
> LANGUAGE=it_IT.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages sagemath depends on:
> ii  cysignals-tools  1.6.7+ds-4
> ii  cython   0.28.4-1
> ii  ecl  16.1.2-4+b1
> ii  eclib-tools  20171002-1+b3
> ii  f2c  20160102-1
> ii  fflas-ffpack 2.3.2-2
> ii  flintqs  1:1.0-3
> ii  gap-core 4r8p8-3
> ii  gfan 0.5+dfsg-6
> ii  gmp-ecm  7.0.4+ds-3
> ii  ipython  5.5.0-1
> ii  iso-codes3.79-1
> ii  jmol 14.6.4+2016.11.05+dfsg1-3.1
> ii  lcalc1.23+dfsg-7
> ii  less 487-0.1+b1
> ii  libatlas3-base [liblapack.so.3]  3.10.3-7+b1
> ii  libblas3 [libblas.so.3]  3.8.0-1+b1
> ii  libbrial-groebner3   1.2.0-2
> ii  libbrial31.2.0-2
> ii  libc62.27-5
> ii  libcdd-tools 094h-1+b1
> ii  libcliquer1  1.21-2
> ii  libec3   20171002-1+b3
> ii  libecm1  7.0.4+ds-3
> ii  libflint-2.5.2   2.5.2-18
> ii  libflint-arb21:2.12.0-3
> ii  libgap-sage-4
> 4.8.8+3+20160327g69a66f0+dsx-1
> ii  libgcc1  1:8.2.0-4
> ii  libgd3   2.2.5-4
> ii  libgivaro9   4.0.4-2
> ii  libglpk404.65-2
> ii  libgmp10 2:6.1.2+dfsg-3
> ii  libgmpxx4ldbl2:6.1.2+dfsg-3
> ii  libgsl23 2.5+dfsg-4
> ii  libgslcblas0 2.5+dfsg-4
> ii  libiml0  1.0.4-1+b2
> ii  libjs-mathjax2.7.4+dfsg-1
> ii  libjs-three  80+dfsg2-2
> ii  liblapack3 [liblapack.so.3]  3.8.0-1+b1
> ii  liblfunction01.23+dfsg-7
> ii  liblinbox-1.5.2-01.5.2-2
> ii  liblinboxsage-1.5.2-01.5.2-2
> ii  liblrcalc1   1.2-2+b1
> ii  libm4ri-0.0.20140914 20140914-2+b1
> ii  libm4rie-0.0.2015090820150908-2
> ii  libmpc3  1.1.0-1
> ii  libmpfi0 1.5.3+ds-2
> ii  libmpfr6 4.0.1-1
> ii  libntl35 10.5.0-2
> ii  libopenblas-base [liblapack.so.3]0.3.2+ds-1
> ii  libpari-gmp-tls5 2.9.5-1
> ii  libplanarity03.0.0.5-3
> ii  libpng16-16  1.6.34-2
> ii  libppl14 1:1.2-3
> ii  libpynac17   0.7.19-2
> ii  libratpoints-2.1.3   

Bug#906720: leiningen-clojure: please make the build reproducible

[Chris Lamb]

Elana,

> However, Clojure itself does not actually produce reproducible
> bytecode[*] most of the time, so I don't think turning this off will
> actually fix the reproducibility of the package.

Sorry but I don't quite follow your reasoning here.

We should always do as much as possible to make a build reproducible,
at the very least to see what is left to do. This is justification
enough to remove this override line given that #877418 is resolved.

(In other words, working on a "it's not 100% reproducible so let's not
bother at all" is actually counter-productive and actually somewhat
demotivating.)

Saying that, according to my tests when I filed this bug, the problem
is simply a umask one, not a bytecode one so removing your override
will make the package reproducible.

I therefore entreat you to revert this change.


Best wishes,

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

Bug#906236: openssh: CVE-2018-15473: delay bailout for invalid authenticating user until after the packet

[Sébastien Delafond]

On Aug/19, Chris Lamb wrote:
> Would the security team be interested in one for stretch? If so, I can
> return with a proposed debdiff.

Sorry, missed your email about this. I'm actually done with the patch on
my end.

Cheers,

--Seb

Bug#906236: openssh: CVE-2018-15473: delay bailout for invalid authenticating user until after the packet

[Sébastien Delafond]

On Aug/21, Chris Lamb wrote:
>  a) You will take the lead on stable/DSA.
>  b) I'll carry on with LTS, etc.

Yes.

--Seb

Bug#906732: Acknowledgement (intel-mkl: [INTL:fr] French translation)

[jean-pierre giraud]

Hi,
Le 20/08/2018 à 12:54, Debian Bug Tracking System a écrit :
> Thank you for filing a new Bug report with Debian.
> 
> You can follow progress on this Bug here: 906732: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906732.
> 
> 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 Science Maintainers 
> 
> 
> If you wish to submit further information on this problem, please
> send it to 906...@bugs.debian.org.
The forgotten file... Sorry,
Best,
Jean-Pierre Giraud


fr.po.gz
Description: application/gzip

Bug#906794: quassel-core: postinst script fails on Debian testing

[Joseph Nuthalapati]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: quassel-core
Version: 1:0.12.5-2
Severity: important

Dear maintainer,

Installation of quassel-core fails on Debian testing. When "dpkg
- --configure -a" is run, the following error is shown.

root@computer:~# dpkg --configure -a
Setting up quassel-core (1:0.12.5-2) ...
Creating quassel group ...
Creating quasselcore user ...
Generating SSL certificate as /var/lib/quassel/quasselCert.pem
... su: Permission denied dpkg: error processing package
quassel-core (--configure):
 installed quassel-core package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 quassel-core

Package installation is successful on Debian unstable for the
same version of the package. #819483 might be related.

- -- 
Regards,
Joseph Nuthalapati

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE4rQIdbX3Xc6j+BCYU5jwCi+kPDUFAlt7rfgACgkQU5jwCi+k
PDXanw//VCraJimfzYtQsIvQU72twt6ECD0Y96c3dgB4Y8w8Bq2SxEF7laAKKpoW
IMCPhMrc03h4zeV5mNQbBRFMELTm4WhpcBj+C2xKSR2B13/2W7CHHzLfU6Dz68Rk
+RNbwMSQ0kMnRdF41YOXUPS5DiTF5KMNO7y+mWScufl48Ai9kiE0To1A9mgMcmgn
UMqChJnAfuWnD4fGZRCL38fAUZ1jdpuE3LyYCnolaYRoE5qt09X6CKgkv/dWvefL
zVI/YG1KmFzvFauoeN/NFJjbM5rRpx8Y2SKye5dNR4JTBUXc7RHWTYl7LtYZ4ASr
3Gldn2BlglBGptZUPgl2+Sv/uylacVMZ9KWW69joZ9Ivcqspum1LqR0qDCwCK0vG
SdWeqgWVlaW7UHZBKgC+tMb4vbHjTDiG8mkC0no8g+fU8j59CLo9+X9lEex+q/Z3
i83MrZGVmBVJUy+t9WbFBCWX4iCw0ZxPbdMGPHZookvVZeqRn5h9xaQap4qH9Etn
EbkIRlPQpFibmMyuhLoh2Ym2wn85zn8DZSdR1DDRivDBIYfjqIZVcWvn46YMgotN
gAA4GQxaKffwOOxXhKuUJ/UplkACAW27Cu1n1xe7z7YuY8nyxvHZFSPh+6Uo2cGS
YtvA4+C+6l5sUdDj6kFo8wdjF7KdcOBPJ8IPqjhk3/39CYqd+tA=
=evvP
-END PGP SIGNATURE-

Bug#906795: x2goserver 4.1.0.2-1 owncloud client won't start (TESTING)

[klak]

Package:x2goserver
Version:4.1.0.2-1


Dear Maintainer,

after updating the x2goserver to 4.1.0.2-1 the owncloud client won't
start.

Greets klak

==>> kkadmin@debt30:~$ owncloud
==>> Gdk-Message: 08:03:03.399: owncloud: Fatal IO error 2 (Datei oder
Verzeichnis nicht gefunden) on X server :50.


The server is a Debian Testing KVM-VM with MATE.

ii x2goserver   4.1.0.2-1  
ii owncloud-client  2.4.1+dfsg-1.1
ii mate-desktop-environment 1.20.0+5


The client is Debian Testing with MATE.

ii  x2goclient  4.1.2.1-2
ii  mate-desktop-environment1.20.0+5   

Bug#906698: anbox-session-manager segmentation fault

[Javier Barroso]

Hello,
On Tue, Aug 21, 2018 at 7:08 AM Shengjing Zhu  wrote:
>
> On Tue, Aug 21, 2018 at 5:45 AM Javier Barroso  wrote:
> > $ anbox system-info
> > version: 0.0~git20180709-1-Debian
> [...]
>
> Can't find evidence yet. But I find an upstream issue which looks same,
> https://github.com/anbox/anbox/issues/829
>
> Upstream suggests the reporter to use software rendering, however this
> is not available in Debian package.
> Meanwhile the reporter got it worked after disabling Nvidia graphics.
> Do you have Nvidia graphics?

I have not Nvidia graphics. Maybe I have some package if Debian
install any ( I have not access to the laptop now)

If you want I can continue with the report at github. Maybe a good
idea to mark this bug as forward to the upstream ?

Thank you !
>
> --
> Best regards,
> Shengjing Zhu

Bug#898060: Stall NFS clients: RPC request reserved 84 but used 272

[Christof Koehler]

Hello everybody,

in the thread on the ubuntu tracker someone else pointed out that this
was also observed on fedora 26, see comment 14 in
https://bugzilla.redhat.com/show_bug.cgi?id=1552037

Apparently it was suggested there (comment 14) that forcing NFS vers=4.0
for the mount appears to fix this as far as it can be reliably
reproduced. Note that debian 9 and ubuntu 18.04 apparently default to
vers=4.2.

I will try that next.

Best Regards

Christof

Bug#906317: dgit: consider demoting git-buildpackage to recommends

[Ian Jackson]

Héctor Orón Martínez writes ("Bug#906317: dgit: consider demoting 
git-buildpackage to recommends"):
> Package: dgit
> Version: 6.6
> Severity: wishlist
> User: debian-ad...@lists.debian.org
> Usertags: needed-by-DSA-Team
...
>   Please, consider demoting `git-buildpackage` to a recommends, since `dgit` 
> does not "seem" to depend on it.

As well as the obvious gbp-build operations, dgit does depend on
gbp pq for importing `3.0 (quilt)' format source packages.

That would be needed during during dgit push if the last upload wasn't
done with dgit, which would be not uncommon.  Also, without gbp pq,
dgit clone of most packages would fail.

So I'm inclined to think that the subset of dgit's functionality which
is useable without gbp pq is too small for your use case (and too
small to make it sensible to demote this depends).  But I'm happy to
talk about it some more.

> For some background, I would like to enable Debian porterbox users
> to be able to run `dgit push`,

Running dgit push directly on a porterbox would involve making the pgp
key availabe to the porterbox.  That doesn't seem wise.  I guess you
mean `dgit rpush', which would be well suited to this use case ?

(Since dgit rpush does most of the work on the `remote' machine, in
this case the porterbox, I don't think that has any implications for
the gbp pq dependency.)

>   At the moment `dgit` is installed in porterboxes,

Thank you.

> however it drags in `git-buildpackage` which is very much a concern
> to have it installed there.

What is the concern with git-buildpackage ?  I understand that it's a
big piece of software but it contains many important tools for
managing many styles of Debian packaging git branch.  I wasn't aware
that it had significant functionality of a kind that would be
undesirable on a porterbox.

For example, if a porter chose to deal with a gbp pq patches-unapplied
tree from salsa, rather than a dsc import from dgit, they would find
that they would anyway need gbp pq to manipulate the patch stack and
to build the package on the porterbox.

> Could you please consider demoting such
> dependency to a recommends? Or alternatively provide a separated
> binary package providing `dgit push` functionality? (Since
> porterboxes run on stable and you agree with the report, consider
> making available such feature via stable-backports)

For the reasons I have given, I'm not sure that this would help.
Perhaps in the future gbp pq could be its own .deb, but I doubt we
would want to do that in stable.

Ian.

-- 
Ian JacksonThese opinions are my own.

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

Bug#868050: RFS: golang-github-shibukawa-configdir -- Configuration directories handling for Go

[Paride Legovini]

X-Debbugs-CC: debian...@lists.debian.org

Dear debian-go,

I think this very simple package is ready to be reviewed and eventually
sponsored. The packaging repository is:

https://salsa.debian.org/go-team/packages/golang-github-shibukawa-configdir

The package is a dependency of browsh (ITP #904132).

Cheers,

Paride

Bug#893713: debootstrap-udeb: containts too many scripts files (most of them are symlink but...)

[Raphael Hertzog]

Hi,

On Fri, 23 Mar 2018, Hideki Yamane wrote:
>  It's not a problem, but we can improve it, IMO (so severity is low).

So you tried to fix a non-problem... and while doing so you introduced
a real problem.

While cleaning up the list of scripts to keep, you decided to drop the
scripts for all derivatives making it impossible to use the udeb built
for Debian on any derivative (Kali bug report here:
https://bugs.kali.org/view.php?id=4921)

So you saved a few kilobytes and made the life harder for others.
IMO it was the wrong decision.

The other bug that you fixed at the same time asked to add more scripts,
it did not ask to remove any.

If you really want to do anything at this level, you should just have
a list of obsolete release and automatically drop the corresponding
scripts. But IMO this is not worth the effort. We should just keep all
scripts.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#906491: mediawiki2latex: FTBFS in buster/sid (File name does not match module name)

[Dirk Hünniger]

Hi Georges,

I just published mediawiki2atex version 7.30. I think this solves this bug.

Yours Dirk


On 18.08.2018 17:38, Georges Khaznadar wrote:

Dear Dirk,

I created a git repository to manage debian packaging at salsa.debian.org,
and then modified slightly one debain patch to take your proposition in
account.

Unfortunately, the package still FTNFS.

Maybe you would like to create an account at https://salsa.debian.org
and either fork and request some pulls or become a direct maintainer of
https://salsa.debian.org/georgesk/mediawiki2latex

Please find attached the build log for my last build attempt, which is
synchronized with the current state of the repository mentioned above.

Best regards,   Georges.

Dirk Hünniger a écrit :

Hi Georges,

Hi Santiago,

to me it looks that the line "Font" in the section "Other-Modules:" in the
file "mediawiki2latex.cabal" needs to be removed to fix the issue. @Georges
is it easy for you to create a patch to fix that, or should I better release
a new version?

Yours Dirk


On 17.08.2018 21:22, Santiago Vila wrote:

Package: src:mediawiki2latex
Version: 7.29-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
   debian/rules build-arch
dh build-arch
 dh_update_autotools_config -a
 debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
ghc /<>/Setup.lhs
[1 of 1] Compiling Main ( /<>/Setup.lhs, 
/<>/Setup.o )
Linking /<>/Setup ...
/<>/Setup configure
Configuring mediawiki2latex-7.29...
make[1]: Leaving directory '/<>'
 debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/<>/Setup build
Preprocessing executable 'mediawiki2latex' for mediawiki2latex-7.29..
Building executable 'mediawiki2latex' for mediawiki2latex-7.29..

src/Font.hs:1:1: error:
  File name does not match module name:
  Saw: `Main'
  Expected: `Font'
|
1 | import Data.Tuple
| ^
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:14: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

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

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

Thanks.

Bug#906698: anbox-session-manager segmentation fault

[Shengjing Zhu]

Control: forwarded -1 https://github.com/anbox/anbox/issues/829

On Tue, Aug 21, 2018 at 2:40 PM Javier Barroso  wrote:
>
> If you want I can continue with the report at github. Maybe a good
> idea to mark this bug as forward to the upstream ?
>

Sure, you can provide more debug info at github. But please remember
upstream only supports snap :(
I see morphis has recognized it as a bug, let's wait to see what will happen.

-- 
Best regards,
Shengjing Zhu

Bug#904544: to smcv -- Cannot run Gimp

[Martin Kovařík]

Hi,

my problem was solved by new version of Gimp (version 2.10.2-1)
uploaded in testing And as well by removing "libopenblas-base"  as
refers link: 

 From: Adrian Bunk 
To: Dean Chia , 906...@bugs.debian.org
Subject: Re: Bug#906244: gimp: Cannot Run GIMP
Date: Thu, 16 Aug 2018 02:56:16 +0300


martin@starec:~$ uname -a
Linux starec 4.17.0-1-amd64 #1 SMP Debian 4.17.8-1 (2018-07-20) x86_64
GNU/Linux

martin@starec:~$ lscpu
Architektura:  x86_64
Operační režim(y) CPU: 32-bit, 64-bit
Pořadí bajtů:  Little Endian
Počet CPU: 4
Seznam zapnutých CPU:  0-3
Vláken na jádro:   1
Jader na patici:   4
Patic: 1
Uzly NUMA: 1
ID výrobce:GenuineIntel
Rodina CPU:6
Model: 44
Název modelu:  Intel(R) Xeon(R) CPU   E5606  @ 2.13GHz
Stepping:  2
CPU MHz:   1202.737
CPU max. MHz:  2133,
CPU min. MHz:  1200,
BogoMIPS:  4276.29
Virtualizace:  VT-x
L1d keš:   32K
L1i keš:   32K
L2 keš:256K
L3 keš:8192K
CPU NUMA uzlu 0:   0-3
Příznaky:  fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts
rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca
sse4_1 sse4_2 popcnt aes lahf_lm pti tpr_shadow vnmi flexpriority ept
vpid dtherm arat

with regards Martin Kovařík

Bug#904870: fixed in autopkgtest 5.4.2?

[Nicholas D Steeves]

Control: reopen -1

On Sun, Jul 29, 2018 at 04:06:05PM +, Debian Bug Tracking System wrote:
>
> Closes: 903975 904870
> Changes:
>  autopkgtest (5.4.2) unstable; urgency=medium
>  .
>[ Martin Pitt ]
>* doc: Document "test-name" feature
>* doc/README.package-tests.rst: Fix formatting of previous commit
>  .
>[ Niko Tyni ]
>* Fix versioned provides test dependency handling
>* Refactor _synthesize_deps() parameters
>* Properly handle virtual packages in alternative test dependencies
>  (Closes: #903975)
>* Add test cases for alternative test dependencies improvements
>  .
>[ Antonio Terceiro ]
>* Always pass a non-empty user string to `su` (Closes: #904870)
[...]
> Package: autopkgtest
> Version: 5.4.1
> Severity: grave
> Justification: renders package unusable
> 
> Dear autopkgtest Maintainers,
> 
> In various situations autopkgtest calls /bin/su with an empty string for
> the username. The old su (from login) ignored this, but newer su
> versions (from util-linux 2.32-0.2) do not accept this, and abort.
> Personally I think autopkgtest got lucky that this worked before, but
> this probably was not a valid thing to do.
> 
> One of the affected lines:
>https://sources.debian.org/src/autopkgtest/5.4.1/lib/adt_testbed.py/#L1096
> 
> Example output from autopkgtest:
> 
>autopkgtest [15:52:36]: test supported-algos: [---
>su: user  does not exist
>autopkgtest [15:52:36]: test supported-algos: ---]
>Unexpected error:
>Traceback (most recent call last):
>  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 717, in mainloop
>command()
>  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 646, in command
>r = f(c, ce)
>  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 584, in cmd_copyup
>copyupdown(c, ce, True)
>  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 469, in copyupdown
>copyupdown_internal(ce[0], c[1:], upp)
>  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 494, in 
> copyupdown_internal
>copyup_shareddir(sd[0], sd[1], dirsp, downtmp_host)
>  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 408, in 
> copyup_shareddir
>shutil.copy(tb, host)
>  File "/usr/lib/python3.6/shutil.py", line 241, in copy
>copyfile(src, dst, follow_symlinks=follow_symlinks)
>  File "/usr/lib/python3.6/shutil.py", line 120, in copyfile
>with open(src, 'rb') as fsrc:
>FileNotFoundError: [Errno 2] No such file or directory: 
> '/tmp/autopkgtest.zwqy11/supported-algos-stdout'
>autopkgtest [15:52:36]: ERROR: testbed failure: cannot send to testbed: 
> [Errno 32] Broken pipe
>autopkgtest [15:52:36]: Binaries: resetting testbed apt configuration
> 
> Note that tests that say "Restrictions: needs-root" do not appear to hit
> those code paths.
> 
> I might try to come up with a patch if no one beats me to it.
> 
> Chris

I ran into this just now with autopkgtest 5.5 (inside LXC, or schroot)
when the host system is using either 4.4 or 5.4.1~bpo9+2.

autopkgtest [07:45:34]: test command1: dh_elpa_test --autopkgtest
autopkgtest [07:45:34]: test command1: [--- 
su: user  does not exist
autopkgtest [07:45:34]: test command1: ---]
Unexpected error:
Traceback (most recent call last):
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 717, in mainloop
command()
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 646, in command
r = f(c, ce)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 584, in cmd_copyup
copyupdown(c, ce, True)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 469, in copyupdown
copyupdown_internal(ce[0], c[1:], upp)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 494, in 
copyupdown_internal
copyup_shareddir(sd[0], sd[1], dirsp, downtmp_host)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 408, in 
copyup_shareddir
shutil.copy(tb, host)
  File "/usr/lib/python3.5/shutil.py", line 241, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.5/shutil.py", line 120, in copyfile
with open(src, 'rb') as fsrc:
FileNotFoundError: [Errno 2] No such file or directory: 
'/tmp/autopkgtest-lxc.rg28o5cn/downtmp/command1-stdout'
autopkgtest [07:45:35]: ERROR: testbed failure: cannot send to testbed: [Errno 
32] Broken pipe

Will this be solved if 5.5 is backported?  As a consequence, does this
also mean all stretch systems with sid autopkgtest chroots must switch
to using backported autopkgtests?

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#906809: gimp: Gimp crashes on statrtup

[Mykola Korobko]

Package: gimp
Version: 2.10.2-1
Severity: normal
Tags: upstream

Dear Maintainer,

GIMP is unusable after I updated a system
GIMP crashes on startup: I see startup logo, progress bar and then a stacktrace
window.

the stacktrace:
GNU Image Manipulation Program version 2.10.2
git-describe: GIMP_2_10_0-292-gbe7f9b433a
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian
7.3.0-19' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-
languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-
major-version-only --program-suffix=-7 --program-prefix=x86_64-linux-gnu-
--enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-
included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-
sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-
time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-
vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-
system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-
list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-
targets=nvptx-none --without-cuda-driver --enable-checking=release
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 7.3.0 (Debian 7.3.0-19)

using GEGL version 0.4.6 (compiled against version 0.4.2)
using GLib version 2.56.1 (compiled against version 2.56.1)
using GdkPixbuf version 2.36.12 (compiled against version 2.36.11)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.1 (compiled against version 1.42.1)
using Fontconfig version 2.13.0 (compiled against version 2.13.0)
using Cairo version 1.15.10 (compiled against version 1.15.10)

> fatal error: Помилка адресування

Stack trace:
/usr/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x468)[0x7f38289e52a8]
gimp-2.10(+0xcfa04)[0x5622f8a17a04]
gimp-2.10(+0xcfff8)[0x5622f8a17ff8]
gimp-2.10(+0xd0707)[0x5622f8a18707]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x128e0)[0x7f38265828e0]
gimp-2.10(gimp_device_info_save_tool+0x67)[0x5622f8b77d07]
gimp-2.10(+0x233139)[0x5622f8b7b139]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f3826a4af6d]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x22d3e)[0x7f3826a5dd3e]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xa75)[0x7f3826a663f5]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f3826a66e0f]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_object_setv+0x23e)[0x7f3826a52a0e]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_object_set_property+0x1e)[0x7f3826a5399e]
/usr/lib/libgimpconfig-2.0.so.0(gimp_config_deserialize_property+0x1ea)[0x7f3829432a6a]
/usr/lib/libgimpconfig-2.0.so.0(gimp_config_deserialize_properties+0x256)[0x7f3829432e06]
gimp-2.10(+0x3a3729)[0x5622f8ceb729]
/usr/lib/libgimpconfig-2.0.so.0(gimp_config_deserialize_gfile+0x131)[0x7f3829430f81]
gimp-2.10(gimp_contexts_load+0x108)[0x5622f8cc5478]
gimp-2.10(gimp_tools_restore+0x184)[0x5622f8a769e4]
gimp-2.10(+0xd24b3)[0x5622f8a1a4b3]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f3826a4af6d]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x22d3e)[0x7f3826a5dd3e]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xa75)[0x7f3826a663f5]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f3826a66e0f]
gimp-2.10(gimp_restore+0x111)[0x5622f8cc3631]
gimp-2.10(app_run+0x486)[0x5622f8a174f6]
gimp-2.10(main+0x34c)[0x5622f8a16c9c]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f38263d5b17]
gimp-2.10(_start+0x2a)[0x5622f8a16e3a]

Running gimp from the console is not informative - same result.

I've deleted the GIMP, reinstalled it. Made sure it came from debian repo

gimp:
  Встановлено: 2.10.2-1
  Кандидат:2.10.2-1
  Таблиця версій:
 *** 2.10.2-1 1000
   1000 http://ftp.ua.debian.org/debian testing/main amd64 Packages
  2 http://ftp.us.debian.org/debian sid/main amd64 Packages
100 /var/lib/dpkg/status

Nothing changed.



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

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

Versions of packages gimp depends on:
ii  gimp-data2.10.2-1
ii  libaa1   1.4p5-44+b2
ii  

Bug#906810: dpkg: error: 2 expected programs not found in PATH or not executable

[Thom Thom]

Package: dpkg
Version: 1.19.0.5+b1

After updating from stable to testing I receive the following error messages 
when I use aptitude to install packages:

# aptitude safe-upgrade;
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /usr/bin/dpkg returned an error code (2)
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin

Exporting the PATH before running the same command fix the issue: export 
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

The same happens for full-upgrade, install, etc ...

Bug#790093: No TOFU for git server host key

[Ian Jackson]

Héctor Orón Martínez writes ("Bug#906317: dgit: consider demoting 
git-buildpackage to recommends"):
> For some background, I would like to enable Debian porterbox users
> to be able to run `dgit push`, however some of my colleagues on the
> Debian sysadmin team, consider installing `dgit` a concern, since
> they prefer users to push sources into porterboxes rather than pull
> them (being `apt source` the only exception). At the moment `dgit`
> is installed in porterboxes,

It is great that dgit is installed in porterboxes, thanks.

During conversations at DC18, I was asked about dgit's approach to the
integrity of the sources it fetches.  I mentioned this bug:
  #790093   dgit is subvertable by X.509 CA cabal

This is not as bad on porterboxes (which AIUI trust only Let's
Encrypt) as it is on general user machines, but it is still
suboptimal.  And we should improve this for user machines too.

I think now would be a good time to look at #790093 again.  Would
anyone from the DSA team with the requisite TLS knowledge be available
to get together with me to sketch out a solution ?

The basic problem statement is as follows:


dgit needs to use the ftpmaster api service for a lot of its
functions.  (It is not really practical to replace this with
reliance on apt; I can expand on the reasons if need be.)

The ftpmaster api service is currently provided over HTTP over TLS,
based on with a standard X.509 web PKI cert from Let's Encrypt.

We want, instead, those API queries to be secured by a public key
shipped in a Debian packge.

dgit currently uses the system-provided curl with no special TLS
options (but could pass such options if we knew what they should be).


The description in the head message in #790093 about EE certificates
is no longer right (if it ever was).  AIUI nowadays the EE certificate
is from LE and is updated frequently - too frequently for a Debian
package.

Maybe that means that the ftpmaster api service needs to be provided
via another HTTP-over-TLS endpoint with a different TLS setup.

NB that although I am a security expert and have a background
incryptography, I don't really know much about the details of TLS and
X.509.  So some of what I say above about TLS and X.509 may be wrong.

Thanks,
Ian.

Bug#898998: [clementine] Cannot resume via Plasma media player widget

[Alexander Kernozhitsky]

Control: tags -1 patch

Seems that I got this fixed. Attaching the patch.

The bug was that Plasma Media widget asked CanPlay() only on Clementine 
startup (when an empty playlist was active). According to MPRIS2 docs about 
CanPlay [1],

> When this property changes, the 
org.freedesktop.DBus.Properties.PropertiesChanged signal is emitted with the 
new value. 

But this signal wasn't emitted. So I've added some calls to notify about 
CanPlay/CanPause change. This fixes the issue.

[1] https://specifications.freedesktop.org/mpris-spec/latest/
Player_Interface.html#Property:CanPlay

-- 
Alexander KernozhitskyDescription: Emitting notification on CanPlay/CanPause changed
 If Clementine starts with first playlist empty, CanPlay initially returns False
 (because of empty playlist). Plasma Media Player asks for CanPlay only once,
 because Clementine doesn't say it is changed via DBus. This patch notifies
 about CanPlay/CanPause change every time the engine state or current track
 changes.
Author: Alexander Kernozhitsky 
Bug-Debian: https://bugs.debian.org/898998
Last-Update: 2018-08-21

--- clementine-1.3.1+git565-gd20c2244a+dfsg.orig/src/core/mpris2.cpp
+++ clementine-1.3.1+git565-gd20c2244a+dfsg/src/core/mpris2.cpp
@@ -131,6 +131,8 @@ void Mpris2::EngineStateChanged(Engine::
 EmitNotification("Metadata");
   }
 
+  EmitNotification("CanPlay");
+  EmitNotification("CanPause");
   EmitNotification("PlaybackStatus", PlaybackStatus(newState));
   if (newState == Engine::Playing)
 EmitNotification("CanSeek", CanSeek(newState));
@@ -181,6 +183,10 @@ void Mpris2::EmitNotification(const QStr
 value = CanGoPrevious();
   else if (name == "CanSeek")
 value = CanSeek();
+  else if (name == "CanPlay")
+value = CanPlay();
+  else if (name == "CanPause")
+value = CanPause();
 
   if (value.isValid()) EmitNotification(name, value);
 }
@@ -328,6 +334,8 @@ QString Mpris2::current_track_id() const
 // changing song starts...
 void Mpris2::CurrentSongChanged(const Song& song) {
   ArtLoaded(song, "");
+  EmitNotification("CanPlay");
+  EmitNotification("CanPause");
   EmitNotification("CanGoNext", CanGoNext());
   EmitNotification("CanGoPrevious", CanGoPrevious());
   EmitNotification("CanSeek", CanSeek());

Bug#887142: ITP: node-nock -- It is an HTTP mocking and expectations library for Node.js

[Pirate Praveen]

On Sun, 14 Jan 2018 18:16:44 +0530 Manas Kashyap
 wrote:>   Description : Nock is an HTTP
mocking and expectations library for
>  Node.js

node-pre-gyp tests need this package.



signature.asc
Description: OpenPGP digital signature

Bug#906318: www.debian.org: Language Stats page completely broken

[Rhonda D'Vine]

Hey Helge,

* Helge Kreutzmann  [2018-08-17 08:11:58 CEST]:
> Until yesterday (at least to my knowledge) the langauge stats page was
> outdated, but (hopefully) complete:
> https://www.debian.org/international/l10n/po-debconf/de

 while I can't comment on what's going on there (haven't digged into it
yet), one thing confused me:

> It would be great if this could be fixed ASAP as the freeze comes
> close and this page is a very valuable ressource to determine where
> work is still needed.

 What freeze is coming close?  Did I miss some release team update?
Last I've heard about the freeze was in april and it stated:

 * 2019-01-12 - Transition freeze

 To the best of my knowledge this hasn't changed since?  Or do you mean
that this is already a close timeframe?  Just to be sure we are speaking
of the same freeze times. :)

 Enjoy,
Rhonda
-- 
Fühlst du dich mutlos, fass endlich Mut, los  |
Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden
Fühlst du dich machtlos, geh raus und mach, los   | 23.55: Alles auf Anfang
Fühlst du dich haltlos, such Halt und lass los|

Bug#846006: debian-cd: please provide flavor/spin netinst image for Debian Edu

[Steve McIntyre]

On Tue, Aug 21, 2018 at 12:13:09AM +0200, Wolfgang Schweer wrote:
>On Sun, Jul 29, 2018 at 01:20:47PM +0100, Steve McIntyre wrote:
>> On Sun, Jul 29, 2018 at 11:55:45AM +, Holger Levsen wrote:
>> >I think we should still keep this bug open though, to finish the last
>> >remaining bit: the offline USB image...
>
>Thanks for providing the USB image! Just checked the one built today. 
>The ISO image seems to contain all packages needed, but one thing is 
>still missing for this image to be usable in offline mode:
>
>[BD ISO image]/.disk/disk_type says 'not_complete'; the content should 
>be 'bluray' for the image to be usable offline, because otherwise 
>apt-setup (and some Debian Edu code as well) would try to connect to the 
>network and fail.
>
>I figure setting 'export DISKTYPE=BD' in the related CONF.sh file would 
>do it right (the default is DISKTYPE=CD).
>
>Steve, would it be possible to try this change?

Hey Wolfgang,

It was already being set in the "testingcds" script, but there was a
stray "COMPLETE=0" that had been copied from the netinst image
config. I've just removed that now.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Further comment on how I feel about IBM will appear once I've worked out
 whether they're being malicious or incompetent. Capital letters are forecast."
 Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html

Bug#906808: libbuild-helper-maven-plugin-java: Provide debian version for maven artefact

[Adrian]

Package: libbuild-helper-maven-plugin-java
Severity: normal

Hi,

It would be very helpful to provide a debian version for the maven
artefact »build-helper-maven-plugin«. This is especially helpful for
building packages depending on this artefact on debian jessie, stretch
*and* buster.

Thanks, Adrian

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

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

Versions of packages libbuild-helper-maven-plugin-java depends on:
pn  libbsh-java 
pn  libmaven-plugin-tools-java  
pn  libmaven2-core-java 
pn  libplexus-utils-java

libbuild-helper-maven-plugin-java recommends no packages.

Versions of packages libbuild-helper-maven-plugin-java suggests:
pn  libbuild-helper-maven-plugin-java-doc  

Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts

[Michael Biebl]

Am 21.08.2018 um 11:07 schrieb Nuno Oliveira:

> Apparently Network Manager support in NIS was introduced to avoid ypbind
> from being killed by systemd.

That sounds like non-sense and definitely not the root cause of the issue.



signature.asc
Description: OpenPGP digital signature

Bug#906795: x2goserver 4.1.0.2-1 owncloud client won't start (TESTING)

[Mike Gabriel]

Hi,

On  Di 21 Aug 2018 08:15:26 CEST, klak wrote:


Package:x2goserver
Version:4.1.0.2-1


Dear Maintainer,

after updating the x2goserver to 4.1.0.2-1 the owncloud client won't
start.

Greets klak


Can you test owncloud client locally outside of X2Go on that very  
machine? My guess is that the error you observe is not related to  
X2Go. So, please test locally (or via VNC or ssh -X).


Thanks,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpcxqtykL7s4.pgp
Description: Digitale PGP-Signatur

Bug#824074: gimp: Crashes (apparently) when Caps Lock key is pressed

[Simon McVittie]

Version: 2.24.31-1

On Wed, 11 May 2016 at 23:23:22 +0200, Guillermo wrote:
> While on a normal usage of Gimp sometimes it crashes losing all unsaved
> progress. Apparently this happens after pressing the Caps Lock key,
> but not always.

This is believed to have been fixed upstream in gtk+2.0 version 2.24.31,
available in Debian 9 'stretch' and later.

smcv

Bug#906811: FTBFS: libconfig.h: No such file or directory

[Gilles Filippini]

Source: blasr
Version: 5.3+0-2
Severity: serious
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

When recompiling blasr for unstable it FTBFS with:

make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build   
make[1]: Entering directory '/<>'
dh_auto_build 
make -j1 "INSTALL=install --strip-program=true"
make[2]: Entering directory '/<>'
make[2]: git: Command not found
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/pbseq -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -O3 -g -DSHA1_7=\"\" -std=c++0x -pedantic -Wall -We
xtra -Wno-div-by-zero -Wno-overloaded-virtual -MMD -MP -fno-builtin-malloc 
-fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free 
-fno-omit-frame-pointer  -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/pbseq
/alignment -I/usr/include/pbseq/hdf -I/usr/include/pbseq/pbdata -I/usr/include 
-I/usr/include/hdf5/serial -I/usr/include/htslib -I/usr/include/boost  -c -o 
Blasr.o Blasr.cpp
In file included from iblasr/BlasrMiscs.hpp:4,
 from Blasr.cpp:3:  
iblasr/BlasrHeaders.h:24:10: fatal error: libconfig.h: No such file or directory
 #include
  ^
compilation terminated.
make[2]: *** [: Blasr.o] Error 1

Full log attached.

Thanks,

_g.

- -- System Information:
Distributor ID: PureOS
Description:PureOS GNU/Linux 8
Release:8
Codename:   green
Architecture: x86_64

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

Versions of packages blasr depends on:
ii  libc62.27-5
ii  libgcc1  1:8.2.0-3
ii  libhdf5-100  1.10.0-patch1+docs-4+b2
ii  libhdf5-cpp-100  1.10.0-patch1+docs-4+b2
pn  libhts2  
pn  libpbbam 
pn  libpbseq 
ii  libstdc++6   8.2.0-3
ii  zlib1g   1:1.2.11.dfsg-1

blasr recommends no packages.

blasr suggests no packages.

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlt8Cu8ACgkQ7+hsbH/+
z4OhTQf/bZPsdSP7SzdhPH4n7kRghAx0aH+hiRpMbwIV+KbBKrFglcVV4G6X9LJM
eAI2ovx0mk27VKLPjKFA7eYkin5j3JxEvKDrSiqwu4xk7YAtHf/4rfMIJfLs1za2
oXqaWkc7GlKhX834A+0B2kxCOnmOLLETOXAoPzJl0+TFt3Ec5uJbXQSd6QLF0iJO
LTm4zx8kl/3KXxQPZUHkQibC/B6G5vDHl2KoXNnAqQHqyDjFrFE5wglu4mUV/u0X
2kVaNezD7+o1HGqLEOTKXFT9rLH13EWoL79/Tcblr66jjJdgn36tFqHggVc74d5v
42+SK5GWyaR5yXNPH27mj1NS/RSF7g==
=0mhM
-END PGP SIGNATURE-


blasr_5.3+0-2_amd64-2018-08-21T11:40:43Z.build.gz
Description: application/gzip

Bug#906236: openssh: CVE-2018-15473: delay bailout for invalid authenticating user until after the packet

[Colin Watson]

On Sun, Aug 19, 2018 at 09:32:57AM +0100, Chris Lamb wrote:
> Hi,
> 
> > openssh: CVE-2018-15473: delay bailout for invalid authenticating
> > user until after the packet
> 
> I've started on a patch for wheezy (WIP attached).
> 
> Would the security team be interested in one for stretch? If so, I can
> return with a proposed debdiff.

Your WIP mostly looks good, except:

> --- openssh-6.7p1.orig/auth2-pubkey.c
> +++ openssh-6.7p1/auth2-pubkey.c
> @@ -76,15 +76,11 @@ userauth_pubkey(Authctxt *authctxt)
>   Buffer b;
>   Key *key = NULL;
>   char *pkalg, *userstyle;
> - u_char *pkblob, *sig;
> + u_char *pkblob, *sig = NULL;
>   u_int alen, blen, slen;
>   int have_sig, pktype;
>   int authenticated = 0;
>  
> - if (!authctxt->valid) {
> - debug2("userauth_pubkey: disabled because of invalid user");
> - return 0;
> - }
>   have_sig = packet_get_char();
>   if (datafellows & SSH_BUG_PKAUTH) {
>   debug2("userauth_pubkey: SSH_BUG_PKAUTH");
> @@ -131,6 +127,11 @@ userauth_pubkey(Authctxt *authctxt)
>   } else {
>   buffer_put_string(, session_id2, session_id2_len);
>   }
> + if (!authctxt->valid || authctxt->user == NULL) {
> + debug2("%s: disabled because of invalid user",
> + __func__);
> + goto done;
> + }
>   /* reconstruct packet */
>   buffer_put_char(, SSH2_MSG_USERAUTH_REQUEST);
>   xasprintf(, "%s%s%s", authctxt->user,
> @@ -162,11 +163,14 @@ userauth_pubkey(Authctxt *authctxt)
>   buffer_len())) == 1)
>   authenticated = 1;
>   buffer_free();
> - free(sig);
>   } else {
>   debug("test whether pkalg/pkblob are acceptable");
>   packet_check_eom();
> -
> + if (!authctxt->valid || authctxt->user == NULL) {
> + debug2("%s: disabled because of invalid user",
> + __func__);
> + goto done;
> + }
>   /* XXX fake reply and always send PK_OK ? */
>   /*
>* XXX this allows testing whether a user is allowed
> @@ -192,6 +196,7 @@ done:
>   key_free(key);
>   free(pkalg);
>   free(pkblob);
> + free(sig);
>   return authenticated;
>  }
>  

This bit has the same memory leak problem that I noticed in Sébastien's
backport for stretch: https://bugzilla.mindrot.org/show_bug.cgi?id=2898,
but the backported fix needs to be different because we're working with
a buffer on the stack rather than a pointer to the buffer on the heap.
My suggestion to Sébastien was to add "buffer_free();" before the new
"goto done;" in (only) the have_sig branch; this is a bit clunky, but
seems like the easiest solution.

-- 
Colin Watson   [cjwat...@debian.org]

Bug#884697: logrotate package

[Andreas Henriksson]

Hello Christian,

On Sun, Aug 19, 2018 at 11:05:49AM +0200, Christian Göttsche wrote:
[...]
> > Please tell me if you want me to go ahead with further testing and
> > uploading of the package, or if you already have someone else in mind
> > for this task.
> 
> Yes, I'd like to go ahead.
[...]

There doesn't seem to be any (signed) debian/3.14.0-1 tag in the
logrotate repository at
https://salsa.debian.org/debian/logrotate/tags

Please push one, or if you'd rather finish up the changes in master
and release them then please push a (signed) debian/3.14.0-2 tag.
Also you might also want to add a debian/gbp.conf explicitly
specifying which options should be used with this repo,
like 'pristine-tar = True' etc.
cf. https://salsa.debian.org/debian/iwd/blob/debian/master/debian/gbp.conf

Poke me again once tagged and I'll look at uploading it.

(I can probably guess that --git-debian-tag=a919cd247cfe5 is right, but
I'd rather not guess and let you be explicit about what to use.)

Regards,
Andreas Henriksson

PS. If you skip including debian/changelog entries in your commits
and instead generate them from commit message using 'gbp dch --auto'
it'll be easier to revert/cherry-pick/merge if needed later.

Bug#906769: arm kernels fail to boot

[Domenico Andreoli]

On Mon, Aug 20, 2018 at 03:16:52PM -0700, Vagrant Cascadian wrote:
> I can confirm this on several machines in the reproducible builds zoo,
> running linux-image-4.9.0-8-armmp-lpae version 4.9.110-3+deb9u3.
> 
> What I've noticed is that machines running the "armmp" variant appear to
> be unaffected, all of the systems that failed were running the
> "armmp-lpae" variant.

Two A20-OLinuXino-LIME2 with 4.9.0-8-armmp here, both cannot boot.

I don't see any big crash but there are some 'Illegal instruction' towards the 
end.

Thanks.
Domenico

[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.9.0-8-armmp (debian-ker...@lists.debian.org) 
(gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 
4.9.110-3+deb9u3 (2018-08-19)
[0.00] CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), cr=10c5387d
[0.00] CPU: div instructions available: patching division code
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
instruction cache
[0.00] OF: fdt:Machine model: Olimex A20-OLinuXino-LIME2
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] cma: Reserved 16 MiB at 0x7f00
[0.00] Memory policy: Data cache writealloc
[0.00] psci: probing for conduit method from DT.
[0.00] psci: Using PSCI v0.1 Function IDs from DT
[0.00] percpu: Embedded 14 pages/cpu @ef6c1000 s27596 r8192 d21556 
u57344
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 260416
[0.00] Kernel command line: console=ttyS0,115200
[0.00] PID hash table entries: 4096 (order: 2, 16384 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.00] Memory: 993148K/1048576K available (7168K kernel code, 1008K 
rwdata, 2216K rodata, 1024K init, 335K bss, 39044K reserved, 16384K 
cma-reserved, 245760K highmem)
[0.00] Virtual kernel memory layout:
[0.00] vector  : 0x - 0x1000   (   4 kB)
[0.00] fixmap  : 0xffc0 - 0xfff0   (3072 kB)
[0.00] vmalloc : 0xf080 - 0xff80   ( 240 MB)
[0.00] lowmem  : 0xc000 - 0xf000   ( 768 MB)
[0.00] pkmap   : 0xbfe0 - 0xc000   (   2 MB)
[0.00] modules : 0xbf00 - 0xbfe0   (  14 MB)
[0.00]   .text : 0xc0008000 - 0xc080   (8160 kB)
[0.00]   .init : 0xc0b0 - 0xc0c0   (1024 kB)
[0.00]   .data : 0xc0c0 - 0xc0cfc19c   (1009 kB)
[0.00].bss : 0xc0cfe000 - 0xc0d51c4c   ( 336 kB)
[0.00] Hierarchical RCU implementation.
[0.00]  Build-time adjustment of leaf fanout to 32.
[0.00]  RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
[0.00] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
[0.00] NR_IRQS:16 nr_irqs:16 16
[0.00] arm_arch_timer: Architected cp15 timer(s) running at 24.00MHz 
(phys).
[0.00] clocksource: arch_sys_counter: mask: 0xff 
max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[0.09] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 
4398046511097ns
[0.24] Switching to timer-based delay loop, resolution 41ns
[0.002745] clocksource: timer: mask: 0x max_cycles: 0x, 
max_idle_ns: 79635851949 ns
[0.003653] clocksource: hstimer: mask: 0x max_cycles: 0x, 
max_idle_ns: 12741736309 ns
[0.004387] Console: colour dummy device 80x30
[0.004434] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 48.00 BogoMIPS (lpj=12)
[0.004452] pid_max: default: 32768 minimum: 301
[0.004732] Security Framework initialized
[0.004747] Yama: disabled by default; enable with sysctl kernel.yama.*
[0.004790] AppArmor: AppArmor disabled by boot time parameter
[0.004877] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.004890] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.006102] CPU: Testing write buffer coherency: ok
[0.006173] ftrace: allocating 26775 entries in 79 pages
[0.068075] /cpus/cpu@0 missing clock-frequency property
[0.068116] /cpus/cpu@1 missing clock-frequency property
[0.068130] CPU0: thread -1, cpu 0, socket 0, mpidr 8000
[0.068185] Setting up static identity map for 0x4010 - 0x40100098
[0.073874] EFI services will not be available.
[0.085503] CPU1: thread -1, cpu 1, socket 0, mpidr 8001
[0.085732] Brought up 2 CPUs
[0.085756] SMP: Total of 2 processors activated (96.00 BogoMIPS).
[0.085763] CPU: All CPU(s) started in HYP mode.
[0.085769] CPU: Virtualization extensions available.
[0.086836] devtmpfs: initialized
[0.098345] VFP support v0.3: implementor 41 architecture 2 part 30 variant 
7 rev 4
[0.098846] 

Bug#906785: version warping patch is overly aggressive

[Markus Koschany]

Hi Bdale,

we all assumed that OpenJDK 11 will remove support for source/target
1.6. After a discussion on the OpenJDK mailing list they decided to
postpone this change for OpenJDK 12. [1]

The current patch simplifies our packaging work because we don't have to
manually fix packages that still target older Java releases. Since we
don't support and ship Java 6 in Debian anymore, there is no downside
for our users because all packages work for them with OpenJDK8 or
OpenJDK 11. Frankly we have never supported your MacOS use case.
Security support for OpenJDK 6 has ended a long time ago.

> Frankly, I'm not sure having this patch in the Debian package at all is a 
> good idea.  Isn't it better to let javac itself emit an error message if/when
> a version actually becomes supported, and let the developer learn about
> versions and how to update their ancient assertions when needed rather than
> hide this problem?

I think the patch could be removed for OpenJDK 11 but should be applied
for OpenJDK 12 again. All build tools already emit a deprecation warning
for source/target 1.6, so developers and users should be aware of it,
and it is certain now that OpenJDK 11 will be the last JDK that supports
1.6.

Regards,

Markus

[1] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-May/001190.html



signature.asc
Description: OpenPGP digital signature

Bug#906775: hamlib: FTBFS in buster/sid (makeinfo: command not found)

[Enrico Rossi]

tags 906775 + fixed pending confirmed
stop

Hi,

I confirm that hamlib 3.2 is ready and soon will be uploaded, also this
bug is triggered by missing texinfo build-dep in the package.

Thanks for reporting.
Bye
E.

On Tue, Aug 21, 2018 at 11:07:49AM +0200, Ervin Hegedüs wrote:
> 
> The workaround is just install the texinfo package manually.

-- 
GPG key: 4096R/5E0195FAF2133176 2010-10-19 Enrico Rossi 

Bug#905385: stretch-pu: package weboob/1.2-1

[Jonathan Dowland]

On Wed, Aug 15, 2018 at 04:43:41PM +0900, Marc Dequènes wrote:
I finally found some spoons to upload a fixed package with insults 
removed and a warning in the description. I found an extra insult 
which is not in upstream master, so I added an extra patch; this might 
be needed for backporting too but better check with grep to avoid 
missing some around.


Thanks!

Jonathan, if you still feel like giving a hand, then feel free to 
branch on the original repo with all the insult-removal patch needed, 
and please add the warning message as well.


Yes I do still want to help. So to be clear, I will rework the branches
in my Salsa fork for stable and oldstable to backport the patch
committed to sid, and do an additional grep-check for anything missing,
then I'll ping you.


Best wishes

--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄

Bug#906711: appstream glib error - not fixed in 0.12.2-2

[Matthias Klumpp]

2018-08-20 17:48 GMT+02:00 william l-k :
> [...]

Hmm, I still can't reproduce the issue - but:

2018-08-20 3:41 GMT+02:00 william l-k :
> [...]
> Versions of packages appstream depends on:
> ii  libappstream4  0.12.2-1
> ii  libc6  2.27-5
> ii  libglib2.0-0   2.56.1-2
> [...]

Can you please ensure libappstream4 is up to date as well? The fix for
the previous issue actually is in the library, and if the library
isn't updated, you will obviously still have the older issue.
(I am quite tempted now to pass the -V flag to dh_shlibdeps...)

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#906539: magic-wormhole: Please provide python-magic-wormhole library its needed by new version of tahoe-lafs

[Antoine Beaupré]

I'm happy to accept patches to ship a Python2 debian package of the
wormhole library, but I do not have time to make the change myself. NMU,
patches welcome.

I would also strongly recommend pushing tahoe-lafs to port to Py3
already. Python 2 will be unsupported by the time our next Debian
release is published and its future is uncertain, at best.

A.

-- 
A patriot must always be ready to defend his country
against his government.
- Edward Abbey

Bug#906814: stretch-pu: package libxml-structured-perl/1.01-2+deb9u1

[Mike Gabriel]

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

I just uploaded libxml-structured-perl 1.01-2+deb9u1 fixing RC bug
#896502 for stretch.

The uploaded package version adds a missing build and runtime dependency
on libxml-parser-perl.

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

Kernel: Linux 4.9.0-6-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)
diff -Nru libxml-structured-perl-1.01/debian/changelog 
libxml-structured-perl-1.01/debian/changelog
--- libxml-structured-perl-1.01/debian/changelog2017-01-23 
12:50:28.0 +0100
+++ libxml-structured-perl-1.01/debian/changelog2018-08-21 
16:20:42.0 +0200
@@ -1,3 +1,11 @@
+libxml-structured-perl (1.01-2+deb9u1) stretch; urgency=medium
+
+  [ gregor herrmann ]
+  * Add missing build and runtime dependency on libxml-parser-perl.
+(Closes: #896502)
+
+ -- Mike Gabriel   Tue, 21 Aug 2018 16:20:42 +0200
+
 libxml-structured-perl (1.01-2) unstable; urgency=medium
 
   [ Salvatore Bonaccorso ]
diff -Nru libxml-structured-perl-1.01/debian/control 
libxml-structured-perl-1.01/debian/control
--- libxml-structured-perl-1.01/debian/control  2017-01-23 12:49:29.0 
+0100
+++ libxml-structured-perl-1.01/debian/control  2018-08-21 16:20:13.0 
+0200
@@ -5,7 +5,8 @@
 Uploaders:
  Mike Gabriel ,
 Build-Depends: debhelper (>= 9)
-Build-Depends-Indep: perl
+Build-Depends-Indep: perl,
+ libxml-parser-perl
 Standards-Version: 3.9.8
 Homepage: https://metacpan.org/release/XML-Structured
 Vcs-Git: 
https://anonscm.debian.org/git/pkg-perl/packages/libxml-structured-perl.git
@@ -16,6 +17,7 @@
 Depends:
  ${misc:Depends},
  ${perl:Depends},
+ libxml-parser-perl
 Description: Convert XML data into a predefined Perl data structure and back
  The XML::Structured module provides a way to convert XML data into a
  predefined Perl data structure and back to XML. Unlike with modules like

Bug#906815: arbtt: "index too large" when running arbtt-stats

[Chris Lamb]

Source: arbtt
Version: 0.10.0.2-1
Severity: important

Hi,

Not sure if this is similar to #751279 (which appears to be more of a
wishlist request), but I am getting a fatal:

  $ ls -l capture.log
  -rw --- 1 lamby lamby 20,638,562 2018-08-21 15:23 capture.log

  $ arbtt-stats  
  Processing data []   1%
  arbtt-stats: Prelude.!!: index too large


Best wishes,

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

Bug#884697: logrotate package

[Christian Göttsche]

Hello Andreas,

> There doesn't seem to be any (signed) debian/3.14.0-1 tag in the
> logrotate repository at
> https://salsa.debian.org/debian/logrotate/tags
>
> Please push one, or if you'd rather finish up the changes in master
> and release them then please push a (signed) debian/3.14.0-2 tag.
> Also you might also want to add a debian/gbp.conf explicitly
> specifying which options should be used with this repo,
> like 'pristine-tar = True' etc.
> cf. https://salsa.debian.org/debian/iwd/blob/debian/master/debian/gbp.conf
>
> Poke me again once tagged and I'll look at uploading it.

Here I am; I made a new release (3.14.0-2) and pushed a (hopefully) signed tag.
Btw. how do i see on https://salsa.debian.org/debian/logrotate/tags if
a tag is signed?

> PS. If you skip including debian/changelog entries in your commits
> and instead generate them from commit message using 'gbp dch --auto'
> it'll be easier to revert/cherry-pick/merge if needed later.

Makes sense (I adopted my former workflow from another package).

Best regards,
  Christian Göttsche

Bug#906816: thunderbird: Does not start

[Elmar Haneke]

Package: thunderbird
Version: 1:60.0-1
Severity: important

Dear Maintainer,

thunderbird does fail to start, yust these errors are printed to console:

ExceptionHandler::GenerateDump cloned child 23947
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...


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

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

Versions of packages thunderbird depends on:
ii  debianutils   4.8.6
ii  fontconfig2.13.0-5
ii  libatk1.0-0   2.28.1-1
ii  libc6 2.27-5
ii  libcairo-gobject2 1.15.10-3
ii  libcairo2 1.15.10-3
ii  libdbus-1-3   1.12.10-1
ii  libdbus-glib-1-2  0.110-3
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-8
ii  libfontconfig12.13.0-5
ii  libfreetype6  2.8.1-2
ii  libgcc1   1:8.2.0-4
ii  libgdk-pixbuf2.0-02.36.12-1
ii  libglib2.0-0  2.56.1-2
ii  libgtk-3-03.22.30-2
ii  libgtk2.0-0   2.24.32-2
ii  libhunspell-1.6-0 1.6.2-1+b1
ii  libicu60  60.2-6
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.19-3
ii  libnss3   2:3.38-1
ii  libpango-1.0-01.42.4-1
ii  libpangocairo-1.0-0   1.42.4-1
ii  libpangoft2-1.0-0 1.42.4-1
ii  libsqlite3-0  3.24.0-1
ii  libstartup-notification0  0.12-5
ii  libstdc++68.2.0-4
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.5-1
ii  libx11-xcb1   2:1.6.5-1
ii  libxcb-shm0   1.13-2
ii  libxcb1   1.13-2
ii  libxext6  2:1.3.3-1+b2
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc23.1-1+b1
ii  x11-utils 7.7+4
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages thunderbird recommends:
ii  hunspell-de-de [hunspell-dictionary]  20161207-5
ii  hunspell-en-us [hunspell-dictionary]  1:2018.04.16-1
pn  lightning 

Versions of packages thunderbird suggests:
ii  apparmor  2.13-8
ii  fonts-lyx 2.3.0-2
ii  libgssapi-krb5-2  1.16-2

-- no debconf information

Bug#906318: www.debian.org: Language Stats page completely broken

[Laura Arjona Reina]

Hi
I think this is related to this bug:

Debian#887107: [debian-i18n] https://i18n.debian.org/material/data/unstable.gz 
not updated since 2017-11-23 - https://bugs.debian.org/887107


There is a merge request for that bug, that needs review and test but I 
couldn't find the time to setup a test environment or finish reviewing the 
code... help welcome.

Cheers


El 21 de agosto de 2018 15:10:26 CEST, Rhonda D'Vine  escribió:
>Hey Helge,
>
>* Helge Kreutzmann  [2018-08-17 08:11:58 CEST]:
>> Until yesterday (at least to my knowledge) the langauge stats page
>was
>> outdated, but (hopefully) complete:
>> https://www.debian.org/international/l10n/po-debconf/de
>
> while I can't comment on what's going on there (haven't digged into it
>yet), one thing confused me:
>
>> It would be great if this could be fixed ASAP as the freeze comes
>> close and this page is a very valuable ressource to determine where
>> work is still needed.
>
> What freeze is coming close?  Did I miss some release team update?
>Last I've heard about the freeze was in april and it stated:
>
> * 2019-01-12 - Transition freeze
>
> To the best of my knowledge this hasn't changed since?  Or do you mean
>that this is already a close timeframe?  Just to be sure we are
>speaking
>of the same freeze times. :)
>
> Enjoy,
>Rhonda

-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
Sent with K-9 mail

Bug#906436: nis debugging

[Thomas Lange]

I've tested nis nis_3.17.1-1 and nis_3.17.1-2 on a nis client running
buster.
nis_3.17.1-1 works without problems. After a reboot, nis is running.

With nis_3.17.1-2, after a reboot nis is not working. If I log in via
the console and do a systemctl restart nis, ypbind is not
started. But when I just call ypbind, it gets started and nis is
working. So the problem is not in the nis package itself. ypbind is
not started if systemd is trying to start it.

How can we debug this in more detail?
-- 
regards Thomas

Bug#906812: edb: is this still maintained in Debian?

[Nicholas D Steeves]

Package: edb
Version: 1.31-3
Severity: important

Hi,

I noticed that this package hasn't seen an upload since 2013, and it's had an 
RC bug for over a year (#840748).  It also causes problems for other packages 
(#875430).  Last year I attempted to update the package and ultimately gave up 
(#871041), and it's not a package that I'd like to salvage or maintain.  
Finally, it has a low popcon of 18 
(https://qa.debian.org/popcon.php?package=edb).

At this point edb is open to salvaging:
  https://debconf18.debconf.org/talks/149-lets-start-salvaging-packages/
  https://pad.riseup.net/p/debian-salvaging-packages-keep
  https://wiki.debian.org/PackageSalvaging

Alternatively I wonder if edb should be requested for removal...

Sincerely,
Nicholas

Bug#870815: Upstream 1.9.3 release

[Michael Gratton]

Just FYI the new upstream 1.9.3 release fixes all known CVE in 
libytnef: https://github.com/Yeraze/ytnef/releases/tag/v1.9.3



--
⊨ Michael Gratton, Percept Wrangler.
⚙ 

Bug#906813: stretch-pu: package ganeti-os-noop/0.2-1+deb9u1

[Mike Gabriel]

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


Dear release team,

please pre-upload ack/deny my proposal for stretch-pu of ganeti-os-noop
(closing RC bug #895602).

In the .debdiff I cherry-picked in three more changes to debian/control.

  1. Update of Vcs-*: fields. (Mostly because of this issue [1].

  2. Priorty: optional (merely cosmetic, it allowed simple cherry-picking
  of the next commit.

  3. Maintainer: change due to Alioth mailing list death.

Thanks for your time.

Mike

[1] https://lists.debian.org/debian-www/2018/07/msg00023.html

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

Kernel: Linux 4.9.0-6-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)
diff -Nru ganeti-os-noop-0.2/debian/changelog 
ganeti-os-noop-0.2/debian/changelog
--- ganeti-os-noop-0.2/debian/changelog 2016-04-11 22:31:50.0 +0200
+++ ganeti-os-noop-0.2/debian/changelog 2018-08-21 16:00:41.0 +0200
@@ -1,3 +1,17 @@
+ganeti-os-noop (0.2-1+deb9u1) stretch; urgency=medium
+
+  * debian/control:
++ Update Vcs-*: fields. VCS repo has been migrated to salsa.debian.org.
++ Priority extra -> optional.
++ Update Maintainer: field to 'Debian Ganeti Team
+  '
+  * debian/patches:
++ Add 1001_fix-export-script-for-non-block-devices.patch. Fix size
+  detection for non-block devices. Thanks to Bastian Blank for
+  providing the patch. (Closes: #895602).
+
+ -- Mike Gabriel   Tue, 21 Aug 2018 16:00:41 +0200
+
 ganeti-os-noop (0.2-1) unstable; urgency=medium
 
   * Initial release. (Closes: #794482).
diff -Nru ganeti-os-noop-0.2/debian/control ganeti-os-noop-0.2/debian/control
--- ganeti-os-noop-0.2/debian/control   2016-04-12 09:02:37.0 +0200
+++ ganeti-os-noop-0.2/debian/control   2018-08-21 16:00:41.0 +0200
@@ -1,7 +1,7 @@
 Source: ganeti-os-noop
 Section: admin
-Priority: extra
-Maintainer: Debian Ganeti Team 
+Priority: optional
+Maintainer: Debian Ganeti Team 
 Uploaders:
  Apollon Oikonomopoulos ,
  Mike Gabriel ,
@@ -10,8 +10,8 @@
  debhelper (>= 9)
 Standards-Version: 3.9.7
 Homepage: https://github.com/grnet/ganeti-os-noop
-Vcs-Browser: https://anonscm.debian.org/git/pkg-ganeti/ganeti-os-noop.git
-Vcs-Git: https://anonscm.debian.org/git/pkg-ganeti/ganeti-os-noop.git
+Vcs-Browser: https://salsa.debian.org/ganeti-team/ganeti-os-noop
+Vcs-Git: https://salsa.debian.org/ganeti-team/ganeti-os-noop
 
 Package: ganeti-os-noop
 Architecture: all
diff -Nru 
ganeti-os-noop-0.2/debian/patches/1001_fix-export-script-for-non-block-devices.patch
 
ganeti-os-noop-0.2/debian/patches/1001_fix-export-script-for-non-block-devices.patch
--- 
ganeti-os-noop-0.2/debian/patches/1001_fix-export-script-for-non-block-devices.patch
1970-01-01 01:00:00.0 +0100
+++ 
ganeti-os-noop-0.2/debian/patches/1001_fix-export-script-for-non-block-devices.patch
2018-08-21 16:00:22.0 +0200
@@ -0,0 +1,18 @@
+Description: Fix size detection for non-block devices
+Author: Bastian Blank 
+
+--- a/ganeti/os/noop/export
 b/ganeti/os/noop/export
+@@ -28,7 +28,11 @@
+ # https://bugs.launchpad.net/ubuntu/+source/dash/+bug/249620
+ 
+ if test -n "$EXP_SIZE_FD"; then
+-  blockdev --getsize64 "$EXPORT_DEVICE" >&"$EXP_SIZE_FD"
++  if [ -f "$EXPORT_DEVICE" ]; then
++stat -c '%s' "$EXPORT_DEVICE" >&"$EXP_SIZE_FD"
++  else
++blockdev --getsize64 "$EXPORT_DEVICE" >&"$EXP_SIZE_FD"
++  fi
+ fi
+ 
+ dd if="$EXPORT_DEVICE" bs=1048576
diff -Nru ganeti-os-noop-0.2/debian/patches/README 
ganeti-os-noop-0.2/debian/patches/README
--- ganeti-os-noop-0.2/debian/patches/README1970-01-01 01:00:00.0 
+0100
+++ ganeti-os-noop-0.2/debian/patches/README2018-08-21 16:00:22.0 
+0200
@@ -0,0 +1,3 @@
+0xxx: Grabbed from upstream development.
+1xxx: Possibly relevant for upstream adoption.
+2xxx: Only relevant for official Debian release.
diff -Nru ganeti-os-noop-0.2/debian/patches/series 
ganeti-os-noop-0.2/debian/patches/series
--- ganeti-os-noop-0.2/debian/patches/series1970-01-01 01:00:00.0 
+0100
+++ ganeti-os-noop-0.2/debian/patches/series2018-08-21 16:00:22.0 
+0200
@@ -0,0 +1 @@
+1001_fix-export-script-for-non-block-devices.patch

Bug#906000: etckeeper: missing dependency on python

[Adrian Bunk]

On Tue, Aug 21, 2018 at 09:50:58AM -0400, Antoine Beaupré wrote:
> On 2018-08-13 01:29:41, Adrian Bunk wrote:
> > Package: etckeeper
> > Version: 1.18.7-1
> > Severity: serious
> >
> > etckeeper installs a Python module but no longer
> > has a python dependency.
> 
> I guess this is another of my "failed to use python variable expansion"
> again. :(
> 
> Commit acc10f9, to fix #883145, is what might have triggered this. I
> wonder if I was just dumb and ${python3:depends} is not a thing?

${python3:depends} is a thing, but /usr/lib/python2.7/dist-packages/
is not Python 3.

> A.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#906809: gimp: Gimp crashes on statrtup

[Simon McVittie]

On Tue, 21 Aug 2018 at 15:45:43 +0300, Mykola Korobko wrote:
> I've deleted the GIMP, reinstalled it. Made sure it came from debian repo

However, some of the libraries that it uses did not:

> Versions of packages gimp depends on:
> ii  libbabl-0.1-01:0.1.56-dmo1
> ii  libgegl-0.4-01:0.4.6-dmo1
> ii  libmypaint-1.3-0 1:1.3.0-dmo6

These appear to be from deb-multimedia.org. We cannot provide support for
applications using these libraries. Please use libraries from Debian to
provide the dependencies of applications from Debian.

smcv

Bug#905536: closed by Matthias Klose (Bug#905536: fixed in python3.7 3.7.0-5)

[Jason Duerstock]

The patch appears to not have actually been applied in 3.7.0-5.  Can you
double check this please?

Thanks,

Jason

On Mon, Aug 20, 2018 at 3:51 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the src:python3.7 package:
>
> #905536: python3.7: disable -O3 on ia64 due to compiler bug
>
> It has been closed by Matthias Klose .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Matthias Klose <
> d...@debian.org> by
> replying to this email.
>
>
> --
> 905536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905536
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Matthias Klose 
> To: 905536-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 20 Aug 2018 19:49:55 +
> Subject: Bug#905536: fixed in python3.7 3.7.0-5
> Source: python3.7
> Source-Version: 3.7.0-5
>
> We believe that the bug you reported is fixed in the latest version of
> python3.7, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 905...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Matthias Klose  (supplier of updated python3.7 package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Format: 1.8
> Date: Mon, 20 Aug 2018 19:52:20 +0200
> Source: python3.7
> Binary: python3.7 python3.7-venv libpython3.7-stdlib python3.7-minimal
> libpython3.7-minimal libpython3.7 python3.7-examples python3.7-dev
> libpython3.7-dev libpython3.7-testsuite idle-python3.7 python3.7-doc
> python3.7-dbg libpython3.7-dbg
> Architecture: source
> Version: 3.7.0-5
> Distribution: unstable
> Urgency: medium
> Maintainer: Matthias Klose 
> Changed-By: Matthias Klose 
> Description:
>  idle-python3.7 - IDE for Python (v3.7) using Tkinter
>  libpython3.7 - Shared Python runtime library (version 3.7)
>  libpython3.7-dbg - Debug Build of the Python Interpreter (version 3.7)
>  libpython3.7-dev - Header files and a static library for Python (v3.7)
>  libpython3.7-minimal - Minimal subset of the Python language (version 3.7)
>  libpython3.7-stdlib - Interactive high-level object-oriented language
> (standard library
>  libpython3.7-testsuite - Testsuite for the Python standard library (v3.7)
>  python3.7  - Interactive high-level object-oriented language (version 3.7)
>  python3.7-dbg - Debug Build of the Python Interpreter (version 3.7)
>  python3.7-dev - Header files and a static library for Python (v3.7)
>  python3.7-doc - Documentation for the high-level object-oriented language
> Python
>  python3.7-examples - Examples for the Python language (v3.7)
>  python3.7-minimal - Minimal subset of the Python language (version 3.7)
>  python3.7-venv - Interactive high-level object-oriented language (pyvenv
> binary, v
> Closes: 902788 905536
> Changes:
>  python3.7 (3.7.0-5) unstable; urgency=medium
>  .
>* Update to 20180820 from the 3.7 branch.
>* Avoid usage of distutils in the platform module. See issue #26544.
>* Fix some issues on architectures from the computer museum (Jason
> Duerstock).
>  Closes: #905536.
>  - Disable -O3 on ia64 (see PR rtl-optimization/85412).
>  - Remove the -O2 override on m68k (see Debian #326903).
>  - Remove the -mieee and -O2 overrides for DEC Alpha (see Debian
> #212912).
>* Add more breaks for packages not compatible with Python 3.7:
>  - python3-aiomeasures. See #906159.
>  - python3-motor (updated). See #903527.
>* Again close the RC issue about the syntax errors triggered by Python
> 3.7.
>  Closes: #902788.
>* Update symbols files.
> Checksums-Sha1:
>  c1b685de02b97c3540a94b97bd0f8d1dff89e30f 3424 python3.7_3.7.0-5.dsc
>  8da303b6e87587d4d7e234436f5f8e0c36eada0b 370660
> python3.7_3.7.0-5.debian.tar.xz
>  3b45fb308d1fffa315e84f88fdc4822a5f55a005 9404
> python3.7_3.7.0-5_source.buildinfo
> Checksums-Sha256:
>  90eff7180a5d8c71023bd10d9d429a96da6b3fdcf30146e769f49341c88e63b0 3424
> python3.7_3.7.0-5.dsc
>  88f392b0125187c29d51cc86dc212c20266dbd872d5e8af9b029694479c51b84 370660
> python3.7_3.7.0-5.debian.tar.xz
>  b7582768f6a967c4d68738f1737cdf45892eb9e639187f2305248fdcc04eeedc 9404
> python3.7_3.7.0-5_source.buildinfo
> Files:
>  03f89ab2b59cc261f2c3b6b57fbab391 3424 python optional
> python3.7_3.7.0-5.dsc
>  9d753aa4b00257fc64c5957cb0aa4c71 370660 python optional
> 

Bug#906817: mate-screensaver: Screensaver has stopped working.

[Frank McCormick]

Package: mate-screensaver
Version: 1.20.1-1
Severity: important

Using mate-screensaver with the glslideshow module. Pictures are in  the
Pictures directory in home. Screen blanks after a while but slideshow never
shows. Tried other modules they don't work either.



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

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

Versions of packages mate-screensaver depends on:
ii  dbus-x11  1.12.10-1
ii  libatk1.0-0   2.28.1-1
ii  libc6 2.27-5
ii  libcairo-gobject2 1.15.10-3
ii  libcairo2 1.15.10-3
ii  libdbus-1-3   1.12.10-1
ii  libdbus-glib-1-2  0.110-3
ii  libgdk-pixbuf2.0-02.36.12-1
ii  libgl11.1.0-1
ii  libglib2.0-0  2.56.1-2
ii  libgtk-3-03.22.30-2
ii  libice6   2:1.0.9-2
ii  libmate-desktop-2-17  1.20.3-2
ii  libmate-menu2 1.20.1-1
ii  libmatekbd4   1.20.2-1
ii  libnotify40.7.7-3
ii  libpam0g  1.1.8-3.8
ii  libpango-1.0-01.42.4-1
ii  libpangocairo-1.0-0   1.42.4-1
ii  libsm62:1.2.2-1+b3
ii  libstartup-notification0  0.12-5
ii  libsystemd0   239-7
ii  libx11-6  2:1.6.5-1
ii  libxext6  2:1.3.3-1+b2
ii  libxklavier16 5.4-3
ii  libxss1   1:1.2.2-1+b2
ii  libxxf86vm1   1:1.1.4-1+b2
ii  mate-desktop-common   1.20.3-2
ii  mate-screensaver-common   1.20.1-1
ii  mate-session-manager  1.20.1-2

Versions of packages mate-screensaver recommends:
ii  mate-power-manager  1.20.2-1

Versions of packages mate-screensaver suggests:
pn  rss-glx
ii  xscreensaver-data  5.36-1

-- no debconf information

Bug#868217: qemu-user-static.postinst script not executed in LXC/Docker containers

[bruno binet]

It seems that on debian, binfmt is not managed by systemd unit
systemd-binfmt.service but by binfmt-support.service instead, so the
"ConditionDirectoryNotEmpty was not met" sounds ok to me.

And binfmt-support.service expect to find binfmt conf files at
/var/lib/binfmts/*, which should be generated by the postinst script
/var/lib/dpkg/info/qemu-user-static.postinst as Ian explained.

The issue we have here is that there is a special check to prevent
execution on this postinst script on container platform like docker or lxc
(See line `grep -zqs ^container= /proc/1/environ && exit 0` in below
postinst script:)

```
$ head /var/lib/dpkg/info/qemu-user-static.postinst
#!/bin/sh
set -e
# check if we're running inside an (lxc) container
# (we may copy or move this to the postinst script too, to skip installing
it)
grep -zqs ^container= /proc/1/environ && exit 0

# == binfmt registration/deregistration ==
if command -v update-binfmts > /dev/null ; then

fmts="aarch64 alpha arm armeb cris i386 m68k microblaze mips mipsel mipsn32
mipsn32el mips64 mips64el ppc ppc64 ppc64abi32 ppc64le s390x sh4 sh4eb
sparc sparc32plus sparc64 x86_64"
```

So what is the reasoning behind this container check? and can we remove
this check or at least disable it for docker?
I guess if we install qemu-user-static in a docker container, we could
expect qemu binfmts to be correctly registered, right?

Thanks.
Bruno

Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts

[Nuno Oliveira]

Hi again,

The ypbind binary in the current package does not recognize the -no-dbus 
option:


host:~> ypbind -no-dbus
Usage:
   ypbind [-broadcast | -ypset | -ypsetme] [-f configfile]
 [-no-ping] [-broken-server] [-local-only] [-i ping-interval]
 [-r rebind-interval] [-debug] [-verbose] [-n | -foreground]
   ypbind -c [-f configfile]
   ypbind --version
Exit 1


Michael, please update the /etc/default/nis in your package accordingly:

host:~> diff /etc/default/nis /etc/default/nis.orig
28,29c28
< #YPBINDARGS=-no-dbus
< YPBINDARGS=
---

YPBINDARGS=-no-dbus



For me this solves the problem with the client. I will update the server 
later and report any problems.


Thanks,

Nuno.

Bug#906816: thunderbird: Does not start

[Carsten Schoenert]

Hi,

On Tue, Aug 21, 2018 at 04:17:12PM +0200, Elmar Haneke wrote:
> thunderbird does fail to start, yust these errors are printed to console:
> 
> ExceptionHandler::GenerateDump cloned child 23947
> ExceptionHandler::SendContinueSignalToChild sent continue signal to child
> ExceptionHandler::WaitForContinueSignal waiting for continue signal...
... 
> Versions of packages thunderbird suggests:
> ii  apparmor  2.13-8

you have installed apparmor, is the apparmor profile for Thunderbird
also active?

Please have a look at /usr/share/doc/thunderbird/README.apparmor

Regards
Carsten

Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts

[Thomas Lange]

> On Tue, 21 Aug 2018 15:50:33 +0100, Nuno Oliveira  said:

> host:~> diff /etc/default/nis /etc/default/nis.orig
> 28,29c28
> < #YPBINDARGS=-no-dbus
> < YPBINDARGS=
> ---
>> YPBINDARGS=-no-dbus
> 
I can confirm that this fix also works for me.
Thanks for helping.
-- 
regards Thomas

Bug#906818: java-package: Cannot package Java 10.

[Erwan David]

Package: java-package
Version: 0.62
Severity: important

Dear Maintainer,

Trying to package a java 10 jdk from orace, I get following errors :
make-jpkg jdk-10.0.2_linux-x64_bin.tar.gz 
Creating temporary directory: /tmp/make-jpkg.nAUkc2vNJY
Loading plugins: /usr/share/java-package/common.sh 
/usr/share/java-package/javase.sh /usr/share/java-package/jdk-doc.sh 
/usr/share/java-package/oracle-jdk-doc.sh /usr/share/java-package/oracle-jdk.sh 
/usr/share/java-package/oracle-jre.sh 
/usr/share/java-package/oracle-server-jre.sh

Detected Debian build architecture: amd64
Detected Debian GNU type: x86_64-linux-gnu

No matching packaging method was found for jdk-10.0.2_linux-x64_bin.tar.gz.
Please make sure you are using a tar.gz or a self-extracting archive
Removing temporary directory: done



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

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

Versions of packages java-package depends on:
ii  build-essential  12.5
ii  debhelper11.3.5
ii  dpkg-dev 1.19.0.5
ii  fakeroot 1.23-1
ii  libasound2   1.1.6-1
ii  libfontconfig1   2.13.0-5
ii  libgl1-mesa-glx  18.1.6-1
ii  libgtk2.0-0  2.24.32-2
ii  libx11-6 2:1.6.5-1
ii  libxslt1.1   1.1.32-2
ii  libxtst6 2:1.2.3-1
ii  libxxf86vm1  1:1.1.4-1+b2
ii  unzip6.0-21

java-package recommends no packages.

Versions of packages java-package suggests:
pn  openjdk-7-jre  

-- no debconf information

Bug#906820: octave-statistics: autopkgtest failure on i386

[Graham Inggs]

Source: octave-statistics
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: issue

Hi Maintainer

Octave-statistics fails its autopkgtests on i386 with the following error:

[inst/ttest.m]
> /tmp/autopkgtest.iYGNCe/build.raS/src/inst/ttest.m
* test
 x = 8:0.1:12;
 [h, pval, ci] = ttest (x, 10);
 assert (h, 0)
 assert (pval, 1, 10*eps)
 assert (ci, [9.6219 10.3781], 1E-5)
 [h, pval, ci0] = ttest (x, 0);
 assert (h, 1)
 assert (pval, 0)
 assert (ci0, ci)
 [h, pval, ci] = ttest (x, 10, "tail", "right", "dim", 2, "alpha", 0.05);
 assert (h, 0)
 assert (pval, 0.5, 10*eps)
 assert (ci, [9.68498 Inf], 1E-5)
! test failed
ASSERT errors for:  assert (ci0,ci)

  Location  |  Observed  |  Expected  |  Reason
(2)10.3781  10.3781  Abs err 1.7764e-15 exceeds tol 
0 by 2e-15

1 test, 0 passed, 0 known failure, 0 skipped

As far as I can tell, this is not a new failure, and increasing the 
error tolerance may be the solution here.


Regards
Graham

Bug#906819: php-memcached: incomplete default memcached.ini configuration file

[Julien Boulen]

Package: php-memcached
Version: 3.0.1+2.2.0-1
Severity: minor

Dear Maintainer,

Default memcached.ini configuration file should use this file (such as is done 
with php-memcache) :

https://github.com/php-memcached-dev/php-memcached/blob/master/memcached.ini

Regards,

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

Kernel: Linux 3.16.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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php-memcached depends on:
ii  libapache2-mod-php7.0 [phpapi-20151012]  7.0.30-0+deb9u1
ii  libc62.24-11+deb9u3
ii  libmemcached11   1.0.18-4.1
ii  libmemcachedutil21.0.18-4.1
ii  libsasl2-2   2.1.27~101-g0780600+dfsg-3
ii  php-common   1:49
ii  php-igbinary 2.0.1-1
ii  php-msgpack  2.0.2+0.5.7-1
ii  php7.0-cli [phpapi-20151012] 7.0.30-0+deb9u1
ii  php7.0-fpm [phpapi-20151012] 7.0.30-0+deb9u1
ii  ucf  3.0036
ii  zlib1g   1:1.2.8.dfsg-5

php-memcached recommends no packages.

php-memcached suggests no packages.

-- no debconf information

Bug#906821: arctica-greeter build depends on the renamed libayatana-ido3-0.4-dev

[Adrian Bunk]

Source: arctica-greeter
Version: 0.99.1.0-1
Severity: serious
Tags: ftbfs

The following packages have unmet dependencies:
 builddeps:arctica-greeter : Depends: libayatana-ido3-0.4-dev (>= 0.4.0~)

The provides in libayatana-ido3-dev is not versioned.

Bug#906836: xul-ext-self-destructing-cookies no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-self-destructing-cookies
Version: 0.4.11-1
Severity: serious

XUL addons are no longer supported.

Bug#906834: xul-ext-form-history-control no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-password-editor
Version: 2.10.3-1
Severity: serious

XUL addons are no longer supported.

Bug#906835: xul-ext-pdf.js no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-pdf.js
Version: 1.5.188+dfsg-1
Severity: serious

XUL addons are no longer supported.

Bug#906156: Python-skbio not compatible with latest pandas

[Andreas Tille]

Control: forwarded -1 https://github.com/biocore/scikit-bio/issues/1585

- Forwarded message from Yoshiki Vázquez Baeza  
-

Date: Tue, 21 Aug 2018 09:25:21 -0700
From: Yoshiki Vázquez Baeza 
To: biocore/scikit-bio 
Cc: Andreas Tille , Mention 
Subject: Re: [biocore/scikit-bio] Test suite fails with Python 3.7 (#1595)

You are correct, skbio currently does not work with the latest version 
of Pandas. That being said, we do plan to support the newest version of 
Pandas. We have an issue for that here: 
https://github.com/biocore/scikit-bio/issues/1585

On (Aug-21-18| 1:44), Andreas Tille wrote:
>Hi,
>On Mon, Aug 20, 2018 at 02:15:06PM -0700, Yoshiki Vázquez Baeza wrote:
>> If you check with `pandas >= 0.19.2, < 0.23.0`, tests should pass.
>Ahh, this means skbio is not yet adapted to latest pandas version?  For the 
>Debian package I do not have an option to pick some specific pandas version 
>since only one version is supported as Debian package and I need to build 
>against a packaged version.  Do you intend to support latest pandas in the 
>near future?
>Kind regards, Andreas.
>
>
>-- 
>You are receiving this because you commented.
>Reply to this email directly or view it on GitHub:
>https://github.com/biocore/scikit-bio/issues/1595#issuecomment-414598824


-- 
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/biocore/scikit-bio/issues/1595#issuecomment-414735605

- End forwarded message -

-- 
http://fam-tille.de

Bug#906816: thunderbird: Does not start

[Elmar Haneke]

The problem still remains after explicitely disabling apparmor


aa-status  --pretty-json | jq .profiles.thunderbird

results in "null"



Am 21.08.2018 um 18:09 schrieb Carsten Schoenert:
> On Tue, Aug 21, 2018 at 05:11:47PM +0200, Elmar Haneke wrote:
>>> you have installed apparmor, is the apparmor profile for Thunderbird
>>> also active?
>>>
>>> Please have a look at /usr/share/doc/thunderbird/README.apparmor
>> None of these instructions does help clearing that Problem.
> Now I still don't know if the AppArmor profile for Thunderbird is
> active.
>
> You give only poor information how this behaviour could be reproduced.
> Without this it's impossible to solve the issue on your side. Please
> help me to understand what your are doing and what is happen on your
> side.
>
> Putting your small log information into the search engine of my choice
> brings me to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887645
>
> So I would bet you have an active AA profile.
>
> Next would be to see what AppArmor is blocking. For this the mentioned
> Readme file is intended for.
>
> Regards
> Carsten
>

-- 
Mit freundlichen Grüßen

Elmar Haneke

===
|Dr. Elmar Haneke   Tel: +49-2241-39749-0 |
|   Fax: +49-2241-39749-30|
|Haneke SoftwareWWW: www.haneke.de|
|Dr. Elmar und Hubertus Haneke  Mail: el...@haneke.de |
|Johannesstraße 41|
|53721 Siegburg USt-IdNr. DE 123387209|
===

Bug#906000: etckeeper: missing dependency on python

[Antoine Beaupré]

On 2018-08-21 17:22:52, Adrian Bunk wrote:
> On Tue, Aug 21, 2018 at 09:50:58AM -0400, Antoine Beaupré wrote:
>> On 2018-08-13 01:29:41, Adrian Bunk wrote:
>> > Package: etckeeper
>> > Version: 1.18.7-1
>> > Severity: serious
>> >
>> > etckeeper installs a Python module but no longer
>> > has a python dependency.
>> 
>> I guess this is another of my "failed to use python variable expansion"
>> again. :(
>> 
>> Commit acc10f9, to fix #883145, is what might have triggered this. I
>> wonder if I was just dumb and ${python3:depends} is not a thing?
>
> ${python3:depends} is a thing, but /usr/lib/python2.7/dist-packages/
> is not Python 3.

Sigh. I have, indeed, completely missed the mark on that port. After
meddling with dh_auto_install -- PYTHON=python3, I have finally figured
out a port is impossible without first porting bzrlib, which is
currently python2 only (#883146).

So I have reverted the py3 port for now and reopened the original bug,
and made it dependent on that other bug.

Thanks!

A.

-- 
The class which has the power to rob upon a large scale has also the
power to control the government and legalize their robbery.
- Eugene V. Debs

Bug#906838: xul-ext-y-u-no-validate no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-y-u-no-validate
Version: 2013052407-3
Severity: serious

XUL addons are no longer supported.

Bug#906837: xul-ext-ublock-origin no longer works with firefox-esr 60

[Adrian Bunk]

Package: xul-ext-ublock-origin
Version: 1.10.4+dfsg-1
Severity: serious
Control: fixed -1 1.16.6+dfsg-1
Control: close -1

XUL addons are no longer supported.

This is already fixed in unstable.

Bug#906839: RFP: package-update-indicator -- Notify about available software updates

[Guido Berhoerster]

Package: wnpp
Severity: wishlist

* Package name: package-update-indicator
  Version : 1
  Upstream Author : Guido Berhoerster 
* URL : 
https://code.guido-berhoerster.org/projects/package-update-indicator/
* License : MIT
  Programming Lang: C
  Description : Notify about available software updates

The package-update-indicator utility regularly checks for software
updates and notifies the user about available updates using desktop
notifications and either a status notifier icon or a system tray
icon.

This is a much-improved replacement for the pk-update-icon package
which is no longer under development and depends on an obsolete
software stack (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885812 ).

Bug#906816: thunderbird: Does not start

[Carsten Schoenert]

Control: tags -1 moreinfo

On Tue, Aug 21, 2018 at 06:33:17PM +0200, Elmar Haneke wrote:
> The problem still remains after explicitely disabling apparmor

I still don't know what the problem really is.

> aa-status  --pretty-json | jq .profiles.thunderbird
> 
> results in "null"

Come on, ... think about about a bit.

https://wiki.debian.org/Thunderbird#Bug_Reporting_.2F_Issues

Bug#906769: arm kernels fail to boot

[Vagrant Cascadian]

On 2018-08-20, Vagrant Cascadian wrote:
> I can confirm this on several machines in the reproducible builds zoo,
> running linux-image-4.9.0-8-armmp-lpae version 4.9.110-3+deb9u3.
>
> What I've noticed is that machines running the "armmp" variant appear to
> be unaffected, all of the systems that failed were running the
> "armmp-lpae" variant.

If it matters, three imx6 and one exynos4 system running "armmp" seem to
work without problems.

The systems running "armmp-lpae" that are broken include exynos5,
rk3288, allwinner A20, and tegra124.

> Switching to linux-image-4.9.0-8-armmp kernel variant on an affected
> system appears to workaround the issue, or downgrading to
> linux-image-4.9.0-7-armmp-lpae.

Downgrading to the "armmp" variant didn't fully solve the issue; it
allowed the systems to boot, but they tended to eventually hang, just
much slower than when running an "armmp-lpae" variant.


live well,
  vagrant


signature.asc
Description: PGP signature