Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

[Jochen Sprickerhof]

Hi Vagrant,

* Vagrant Cascadian  [2017-07-07 20:21]:
> Is this the only patch needed? Does it also need one of the patches
> mentioned earlier in this bug? This is a single patch, with a v4.12 and
> v4.11 variant, or two very similar looking patches?
> 
> I'd be happy to test on debian's 4.9 and 4.11 kernels, but it is a
> little unclear to me exactly which patches are meant for what.

Sorry for being unclear.

For v4.9 the only patch needed is:

https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=843448;filename=0001-usb-dwc3-core-setup-phy-before-trying-to-read-from-i.patch;msg=97

For v4.11 and v4.12 the only patch needed is:

https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=843448;filename=0001-v4.12-usb-dwc3-core-Setup-phy-before-trying-to-read-.patch;msg=117

For current Linux master you need:

https://patchwork.kernel.org/patch/9815981/
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=843448;filename=0001-usb-dwc3-core-Setup-phy-before-trying-to-read-from-i.patch;msg=117

I also forwarded this upstream here:

http://marc.info/?l=linux-usb=149945465112440=2

Test results welcome.

Cheers Jochen


signature.asc
Description: PGP signature

Bug#867641: gdbm: no fstat error checking and no large file support can crash on 32-bit systems

[Brad Spencer]

Source: gdbm
Version: 1.8.3-14
Severity: important
Tags: lfs patch upstream

Dear Maintainer,

After upgrading to stretch, man-db was crashing randomly during package
upgrades.  Sometimes it would instead report EOVERFLOW errors.  Since I was
running it on i386 with a very large XFS filesystem, I suspected large file
support issues, since I've seen them before in other packages.  It turns out
this was the case.

I built man-db from source and debugged it to confirm the issue was in gdbm.
I then build gdbm from source and was astonished to notice that the fstat()
calls it makes weren't even error-checked, which explained the random crashes
(it tries to allocate, read, etc. a random amount of data because the stat
structure contains garbage from the stack).  This concerns me a bit, since
gdbm programs like man-db run as root with pretty arbitrary input so there
might even be an attack vector here.

I confirmed the code is compiled without _FILE_OFFSET_BITS=64, recompiled it
with that flag, and confirmed that the fstat() calls were working.  Running
the man-db test suite with the fixed gdbm passed all tests (before it failed
on 4 tests on my system).

I've prepared a patch to gdbm that fixes the fstat() calls (this should
probably go upstream).  I hacked in the -D_FILE_OFFSET_BITS=64 (I'm not an
autoconf expert) into Makefile.in; perhaps there's a better way.

I will attach the patch after the report is submitted.

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
--- gdbm-1.8.3.orig/Makefile.in 2017-07-08 01:39:16.0 -0300
+++ gdbm-1.8.3/Makefile.in  2017-07-08 01:23:35.352509271 -0300
@@ -26,7 +26,7 @@
 # Where the system [n]dbm routines are...
 LIBS = @LIBS@ -lc
 
-CFLAGS = @CFLAGS@
+CFLAGS = @CFLAGS@ -D_FILE_OFFSET_BITS=64
 LDFLAGS = @LDFLAGS@
 
 # Common prefix for installation directories
--- gdbm-1.8.3.orig/gdbmopen.c  2017-07-08 01:39:16.0 -0300
+++ gdbm-1.8.3/gdbmopen.c   2017-07-08 01:50:27.809533680 -0300
@@ -152,7 +152,14 @@
 }
 
   /* Get the status of the file. */
-  fstat (dbf->desc, _stat);
+  if (fstat (dbf->desc, _stat) == -1)
+{
+  close (dbf->desc);
+  free (dbf->name);
+  free (dbf);
+  gdbm_errno = GDBM_FILE_OPEN_ERROR;
+  return NULL;
+}
 
   /* Lock the file in the approprate way. */
   if ((flags & GDBM_OPENMASK) == GDBM_READER)
@@ -195,8 +202,14 @@
  now time to truncate the file. */
   if (need_trunc && file_stat.st_size != 0)
 {
-  TRUNCATE (dbf);
-  fstat (dbf->desc, _stat);
+  if (TRUNCATE (dbf) == -1 || fstat (dbf->desc, _stat) == -1)
+{
+  close (dbf->desc);
+  free (dbf->name);
+  free (dbf);
+  gdbm_errno = GDBM_FILE_OPEN_ERROR;
+  return NULL;
+}
 }
 
   /* Decide if this is a new file or an old file. */
--- gdbm-1.8.3.orig/gdbmreorg.c 2002-10-07 15:38:26.0 -0300
+++ gdbm-1.8.3/gdbmreorg.c  2017-07-08 01:09:33.791888611 -0300
@@ -111,7 +111,12 @@
   new_name[len] = '#';
 
   /* Get the mode for the old file and open the new database. */
-  fstat (dbf->desc, );
+  if (fstat (dbf->desc, ) == -1)
+{
+  free (new_name);
+  gdbm_errno = GDBM_REORGANIZE_FAILED;
+  return -1;
+}
   new_dbf = gdbm_open (new_name, dbf->header->block_size, GDBM_WRCREAT,
   fileinfo.st_mode, dbf->fatal_err);
 
--- gdbm-1.8.3.orig/Makefile.in 2017-07-08 01:39:16.0 -0300
+++ gdbm-1.8.3/Makefile.in  2017-07-08 01:23:35.352509271 -0300
@@ -26,7 +26,7 @@
 # Where the system [n]dbm routines are...
 LIBS = @LIBS@ -lc
 
-CFLAGS = @CFLAGS@
+CFLAGS = @CFLAGS@ -D_FILE_OFFSET_BITS=64
 LDFLAGS = @LDFLAGS@
 
 # Common prefix for installation directories
--- gdbm-1.8.3.orig/gdbmopen.c  2017-07-08 01:39:16.0 -0300
+++ gdbm-1.8.3/gdbmopen.c   2017-07-08 01:50:27.809533680 -0300
@@ -152,7 +152,14 @@
 }
 
   /* Get the status of the file. */
-  fstat (dbf->desc, _stat);
+  if (fstat (dbf->desc, _stat) == -1)
+{
+  close (dbf->desc);
+  free (dbf->name);
+  free (dbf);
+  gdbm_errno = GDBM_FILE_OPEN_ERROR;
+  return NULL;
+}
 
   /* Lock the file in the approprate way. */
   if ((flags & GDBM_OPENMASK) == GDBM_READER)
@@ -195,8 +202,14 @@
  now time to truncate the file. */
   if (need_trunc && file_stat.st_size != 0)
 {
-  TRUNCATE (dbf);
-  fstat (dbf->desc, _stat);
+  if (TRUNCATE (dbf) == -1 || fstat (dbf->desc, _stat) == -1)
+{
+  close (dbf->desc);
+  free (dbf->name);
+  free (dbf);
+  gdbm_errno = GDBM_FILE_OPEN_ERROR;
+  return NULL;
+}
 }
 
   /* Decide if this is a new file or an old file. */
--- 

Bug#867333: Please withdraw this bug report

[Rob Johnson]

My apologies.  Upon further investigation, this seems to be the same
as the bug described here:

https://askubuntu.com/questions/792605/ubuntu-16-04-lts-too-slow-after-suspend-and-resume

Running "sudo wrmsr -a 0x19a 0x0" restored performance.

So please mark this bug resolved.

Best,
Rob

Bug#867640: mlocate upstream has moved

[Anthony DeRobertis]

Package: mlocate
Version: 0.26-2
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

With fedorahosted having shut down, upstream seems to have moved to
. It does not appear they've made any (real)
code changes, though they now use git.

The upstream homepage and watch files need updating at least.

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

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

Versions of packages mlocate depends on:
ii  adduser  3.115
ii  libc62.24-12

mlocate recommends no packages.

mlocate suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHMEARECADMWIQTlAc7j4DAtSNRJJ0z7P4jCVepZ/gUCWWBbUBUcYW50aG9ueUBk
ZXJvYmVydC5uZXQACgkQ+z+IwlXqWf7jewCff8r5K2UyZR6bxtSNkqmgomHa88IA
nR/gPl+PqpjDgD/9ntXIZgsH3k0E
=QINy
-END PGP SIGNATURE-

Bug#844376: caja-actions: Uses deprecated libunique3

[Jeremy Bicha]

I didn't see your response until today since I wasn't explicitly CC'd
on your reply.

Why did you change the severity of this bug without an explanation?

libunique3 is unsuitable for release in buster according to its
maintainers but it cannot be removed from testing as long as
caja-actions is in testing with this bug unfixed.

Please investigate whether filemanager-actions can replace caja-actions.

Thanks,
Jeremy Bicha

Bug#867639: browser is ASCII only

[積丹尼 Dan Jacobson]

Package: dillo
Version: 3.0.5-3

Please make dillo configured to read webpages with CJK characters in
them right out of the box. Users shouldn't need to edit a configuration file.

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

[Vagrant Cascadian]

On 2017-07-07, Jochen Sprickerhof wrote:
> I've created patches for v4.12 (applies to v4.11 as well) and git
> master and send them to the subsystem maintainers. Would be great to see
> them included in the Debian kernel as well.

Thanks!

Is this the only patch needed? Does it also need one of the patches
mentioned earlier in this bug? This is a single patch, with a v4.12 and
v4.11 variant, or two very similar looking patches?

I'd be happy to test on debian's 4.9 and 4.11 kernels, but it is a
little unclear to me exactly which patches are meant for what.

live well,
  vagrant

> From 7b12187f59ff43571e664b9f6987534ee622700f Mon Sep 17 00:00:00 2001
> From: Jochen Sprickerhof 
> Date: Fri, 7 Jul 2017 19:38:03 +0200
> Subject: [PATCH] v4.12: usb: dwc3: core: Setup phy before trying to read from
>  it
>
> Commit c499ff71ff2a ("usb: dwc3: core: re-factor init and exit paths")
> moved the call to dwc3_phy_setup() from dwc3_probe() to dwc3_core_init()
> and after the dwc3_readl() (now in dwc3_core_is_valid). This broke USB
> and Ethernet on Odroid XU4, because dwc3_readl() needs dwc3_phy_setup()
> to be run before.
>
> Fix this by moving the call to dwc3_phy_setup() before
> dwc3_core_is_valid().
>
> This fixes USB and Ethernet on Odroid XU4.
>
> Also see https://bugs.debian.org/843448
>
> Signed-off-by: Jochen Sprickerhof 
> Fixes: c499ff71ff2a ("usb: dwc3: core: re-factor init and exit paths")
> ---
>  drivers/usb/dwc3/core.c | 8 
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> index 455d89a1cd6d..2418979a883a 100644
> --- a/drivers/usb/dwc3/core.c
> +++ b/drivers/usb/dwc3/core.c
> @@ -732,6 +732,10 @@ static int dwc3_core_init(struct dwc3 *dwc)
>   u32 reg;
>   int ret;
>  
> + ret = dwc3_phy_setup(dwc);
> + if (ret)
> + goto err0;
> +
>   if (!dwc3_core_is_valid(dwc)) {
>   dev_err(dwc->dev, "this is not a DesignWare USB3 DRD Core\n");
>   ret = -ENODEV;
> @@ -755,10 +759,6 @@ static int dwc3_core_init(struct dwc3 *dwc)
>   if (ret)
>   goto err0;
>  
> - ret = dwc3_phy_setup(dwc);
> - if (ret)
> - goto err0;
> -
>   dwc3_core_setup_global_control(dwc);
>   dwc3_core_num_eps(dwc);
>  
> -- 
> 2.13.2
>
> From 6b7d33243a364c668530a5ae11ed5a57cecd42d9 Mon Sep 17 00:00:00 2001
> From: Jochen Sprickerhof 
> Date: Fri, 7 Jul 2017 19:38:03 +0200
> Subject: [PATCH] usb: dwc3: core: Setup phy before trying to read from it
>
> Commit c499ff71ff2a ("usb: dwc3: core: re-factor init and exit paths")
> moved the call to dwc3_phy_setup() from dwc3_probe() to dwc3_core_init()
> and after the dwc3_readl() (now in dwc3_core_is_valid). This broke USB
> and Ethernet on Odroid XU4, because dwc3_readl() needs dwc3_phy_setup()
> to be run before.
>
> Fix this by moving the call to dwc3_phy_setup() before
> dwc3_core_is_valid().
>
> This fixes USB and Ethernet on Odroid XU4.
>
> This needs and is supposed to be applied on top of
> https://patchwork.kernel.org/patch/9815981/
>
> Also see https://bugs.debian.org/843448
>
> Signed-off-by: Jochen Sprickerhof 
> Fixes: c499ff71ff2a ("usb: dwc3: core: re-factor init and exit paths")
> ---
>  drivers/usb/dwc3/core.c | 8 
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> index 03474d3575ab..3c6faddc1394 100644
> --- a/drivers/usb/dwc3/core.c
> +++ b/drivers/usb/dwc3/core.c
> @@ -747,6 +747,10 @@ static int dwc3_core_init(struct dwc3 *dwc)
>   u32 reg;
>   int ret;
>  
> + ret = dwc3_phy_setup(dwc);
> + if (ret)
> + goto err0;
> +
>   if (!dwc3_core_is_valid(dwc)) {
>   dev_err(dwc->dev, "this is not a DesignWare USB3 DRD Core\n");
>   ret = -ENODEV;
> @@ -774,10 +778,6 @@ static int dwc3_core_init(struct dwc3 *dwc)
>   if (ret)
>   goto err0;
>  
> - ret = dwc3_phy_setup(dwc);
> - if (ret)
> - goto err0;
> -
>   dwc3_core_setup_global_control(dwc);
>   dwc3_core_num_eps(dwc);
>  
> -- 
> 2.13.2


signature.asc
Description: PGP signature

Bug#866986: bugs.debian.org: broken links to PTS and package pages

[Andrew Donnellan]

The link to "xyz package page" is still broken as of 8 July.

-- 
Andrew Donnellan
http://andrew.donnellan.id.au and...@donnellan.id.au

Bug#867533: test failure when updating to 3.9.0

[Antonio Terceiro]

On Fri, Jul 07, 2017 at 10:32:53AM +0530, Pirate Praveen wrote:
> package: ruby-parser
> version: 3.8.2
> 
> When trying to update ruby-parser to latest upstream release (3.9.0),
> tests failed. Log below.

This seems wrong. If you get a failure after trying to update the
package to 3.9.0, by definition the bug cannot be against version 3.8.2
(which does not exist in Debian BTW, you missed the Debian revision
number).

IMO the BTS should be used for bugs that are not present in the Debian
archive.


signature.asc
Description: PGP signature

Bug#867599: gem2deb fails to install pure ruby part when a gem has both pure ruby and native libs

[Antonio Terceiro]

Control: tag -1 + moreinfo

On Fri, Jul 07, 2017 at 10:43:20PM +0530, Pirate Praveen wrote:
> package: gem2deb
> version: 0.34
> 
> gem2deb is not installing the pure ruby libraries of grpc (ruby-grpc is
> in alioth) and tests fail.

yes it is installing the pure ruby libraries

> ──┐
> │ Run tests for ruby2.3 from debian/ruby-tests.rake
>   │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-grpc/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0:.
> GEM_PATH=debian/ruby-grpc/usr/share/rubygems-integration/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
> ruby2.3 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern
> ./src/ruby/spec/\*\*/\*_spec.rb --format documentation
> /<>/src/ruby/lib/grpc/errors.rb:48:in `':
> uninitialized constant GRPC::Core (NameError)

if the pure ruby libraries were not being installed, you would get a
LoadError (i.e. a `require` statement failed), but that's not what is
happening here.

gem2deb does install the Ruby code even when there is a C extension, and
there are several automated tests for that. If it didn't, we wouldn't
be learning that this late in the game.

I don't think this is a bug in gem2deb, but you can convince me
otherwise.


signature.asc
Description: PGP signature

Bug#867638: debian-goodies: checkrestart wrongly reports that nginx needs to be restarted

[Joseph Muller]

Package: debian-goodies
Version: 0.63
Severity: important

Checkrestart still notes nginx and nginx-debug as needed to be restarted even 
after the services were restarted.

Please see the output of "checkrestart -v":

Found 3 processes using old versions of upgraded files
(2 distinct programs)
Process /sbin/agetty (PID: 1503)
List of deleted files in use:
/lib/x86_64-linux-gnu/libnss_files-2.19.so
/lib/x86_64-linux-gnu/libnss_nis-2.19.so
/lib/x86_64-linux-gnu/libnsl-2.19.so
/lib/x86_64-linux-gnu/libnss_compat-2.19.so
/lib/x86_64-linux-gnu/libc-2.19.so
/lib/x86_64-linux-gnu/ld-2.19.so
Process /sbin/agetty (PID: 1504)
List of deleted files in use:
/lib/x86_64-linux-gnu/libnss_files-2.19.so
/lib/x86_64-linux-gnu/libnss_nis-2.19.so
/lib/x86_64-linux-gnu/libnsl-2.19.so
/lib/x86_64-linux-gnu/libnss_compat-2.19.so
/lib/x86_64-linux-gnu/libc-2.19.so
/lib/x86_64-linux-gnu/ld-2.19.so
Process /usr/sbin/nginx (PID: 16676)
List of deleted files in use:
/[aio]
Running:['dpkg-query', '--search', '/usr/sbin/nginx', '/sbin/agetty']
Reading line: nginx: /usr/sbin/nginx

Reading line: util-linux: /sbin/agetty

(2 distinct packages)

Of these, 1 seem to contain init scripts which can be used to restart them:
The following packages seem to have init scripts that could be used
to restart them:
nginx:
16676   /usr/sbin/nginx

These are the init scripts:
service nginx restart
service nginx-debug restart

These processes do not seem to have an associated init script to restart them:


Please see the output of "lsof | egrep 'delete|DEL|path inode'":

getty  1503  root  DEL   REG  251,1 
1049081 /lib/x86_64-linux-gnu/libnss_files-2.19.so
getty  1503  root  DEL   REG  251,1 
1049083 /lib/x86_64-linux-gnu/libnss_nis-2.19.so
getty  1503  root  DEL   REG  251,1 
1049078 /lib/x86_64-linux-gnu/libnsl-2.19.so
getty  1503  root  DEL   REG  251,1 
1049079 /lib/x86_64-linux-gnu/libnss_compat-2.19.so
getty  1503  root  DEL   REG  251,1 
1049070 /lib/x86_64-linux-gnu/libc-2.19.so
getty  1503  root  DEL   REG  251,1 
1049010 /lib/x86_64-linux-gnu/ld-2.19.so
getty  1504  root  DEL   REG  251,1 
1049081 /lib/x86_64-linux-gnu/libnss_files-2.19.so
getty  1504  root  DEL   REG  251,1 
1049083 /lib/x86_64-linux-gnu/libnss_nis-2.19.so
getty  1504  root  DEL   REG  251,1 
1049078 /lib/x86_64-linux-gnu/libnsl-2.19.so
getty  1504  root  DEL   REG  251,1 
1049079 /lib/x86_64-linux-gnu/libnss_compat-2.19.so
getty  1504  root  DEL   REG  251,1 
1049070 /lib/x86_64-linux-gnu/libc-2.19.so
getty  1504  root  DEL   REG  251,1 
1049010 /lib/x86_64-linux-gnu/ld-2.19.so
zabbix_ag 13262zabbix  DEL   REG0,5 
  98304 /SYSV6c010716
zabbix_ag 13263zabbix  DEL   REG0,5 
  98304 /SYSV6c010716
zabbix_ag 13264zabbix  DEL   REG0,5 
  98304 /SYSV6c010716
zabbix_ag 13265zabbix  DEL   REG0,5 
  98304 /SYSV6c010716
zabbix_ag 13266zabbix  DEL   REG0,5 
  98304 /SYSV6c010716
zabbix_ag 13267zabbix  DEL   REG0,5 
  98304 /SYSV6c010716
php5-fpm  16169  root  DEL   REG0,5   
392843111 /dev/zero
php5-fpm  16169  root  DEL   REG0,5   
392843117 /dev/zero
php5-fpm  16169  root3u  REG  251,10
 393231 /tmp/.ZendSem.TGS39p (deleted)
php5-fpm  16171  www-data  DEL   REG0,5   
392843111 /dev/zero
php5-fpm  16171  www-data  DEL   REG0,5   
392843117 /dev/zero
php5-fpm  16171  www-data3u  REG  251,10
 393231 /tmp/.ZendSem.TGS39p (deleted)
php5-fpm  16172  www-data  DEL   REG0,5   
392843111 /dev/zero
php5-fpm  16172  www-data  DEL   REG0,5   
392843117 /dev/zero
php5-fpm  16172  www-data3u  REG  251,10
 393231 /tmp/.ZendSem.TGS39p (deleted)
sshd  16528  root  DEL   REG0,5   
392876958 /dev/zero
sshd  16528  root  DEL   REG0,5   
392876935 /dev/zero
nginx 16673  

Bug#867637: python-livereload: Please package latest upstream version

[Brian May]

Source: python-livereload
Version: 2.4.0-1
Severity: normal

The latest version of this package is required by the latest version of
python-mkdocs.

Thanks

-- System Information:
Debian Release: 9.0
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable'), (100, 
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#814570: debdiff: [PATCH 0/4] Correctly match filesystem entries for different options.

[James McCoy]

On Fri, Jul 07, 2017 at 12:39:01PM +1000, Ben Finney wrote:
> On 14-May-2016, Ben Finney wrote:
> > I will attempt fixing this.
> 
> This patch series alters the Bash command competion script for
> ‘debdiff(1)’, to allow matching filesystem entries and options as
> needed.

Seems good to me.  Thanks!

> Ben Finney (4):
>   Record the change being made in this branch.

Please leave out the munging of the changelog trailer.

Other than that, feel free to merge the series.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#867636: linux-image-4.9.0-3-amd64: Repeated ESATA softreset failed messages - even after replacing most components.

[Matthew Gillespie]

Package: src:linux
Version: 4.9.30-2+deb9u2
Severity: important

Dear Maintainer,

   * What led up to the situation?

On a hot day two drives in my eSATA connected Sandisk TowerRAID TR8M+B 
failed. After removing the drives I'm receiving repeated softreset messages - 
even with entirely new equipment (except for the se
rver itself)

This system worked without issue for almost a year. Previous 
incarnations (another server with same NAS) worked for even longer.

The messages received in dmesg (and across the screen)  are:


[  258.182103] ata3: link is slow to respond, please be patient (ready=0)
[  282.190796] ata3: softreset failed (device not ready)
[  282.190862] ata3: limiting SATA link speed to 1.5 Gbps
[  282.190864] ata3: hard resetting link
[  282.914095] ata3: SATA link down (SStatus 100 SControl 310)
[  282.914104] ata3: EH complete
[  282.915391] ata3: exception Emask 0x10 SAct 0x0 SErr 0x404 action 0xe 
frozen
[  282.915460] ata3: irq_stat 0x8040, connection status changed
[  282.915522] ata3: SError: { CommWake DevExch }
[  282.915579] ata3: hard resetting link
[  290.005120] device vlan35 entered promiscuous mode
[  290.005132] device eth0 entered promiscuous mode
[  292.932185] ata3: softreset failed (device not ready)
[  292.932251] ata3: hard resetting link
[  299.197731] ata3: failed to reset engine (errno=-5)
[  303.429384] ata3: softreset failed (1st FIS failed)
[  303.429452] ata3: hard resetting link
[  310.194426] ata3: failed to reset engine (errno=-5)
[  338.896868] ata3: softreset failed (1st FIS failed)
[  338.896943] ata3: limiting SATA link speed to 1.5 Gbps
[  338.896945] ata3: hard resetting link
[  340.119629] ata3: SATA link down (SStatus 100 SControl 310)
[  340.119640] ata3: EH complete
[  340.120968] ata3: exception Emask 0x10 SAct 0x0 SErr 0x404 action 0xe 
frozen
[  340.121048] ata3: irq_stat 0x8040, connection status changed
[  340.121114] ata3: SError: { CommWake DevExch }
[  340.121179] ata3: hard resetting link
[  350.137287] ata3: softreset failed (device not ready)
[  350.137359] ata3: hard resetting link
[  356.402847] ata3: failed to reset engine (errno=-5)
[  360.626520] ata3: softreset failed (1st FIS failed)
[  360.626587] ata3: hard resetting link
[  372.094712] ata3: link is slow to respond, please be patient (ready=0)
[  395.594524] ata3: softreset failed (device not ready)
[  395.594592] ata3: limiting SATA link speed to 1.5 Gbps
[  395.594594] ata3: hard resetting link
[  396.317785] ata3: SATA link down (SStatus 100 SControl 310)
[  396.317797] ata3: EH complete
[  396.319185] ata3: exception Emask 0x10 SAct 0x0 SErr 0x404 action 0xe 
frozen
[  396.319263] ata3: irq_stat 0x8040, connection status changed
[  396.319326] ata3: SError: { CommWake DevExch }
[  396.319389] ata3: hard resetting link
[  402.579341] ata3: failed to reset engine (errno=-5)
[  406.818948] ata3: softreset failed (1st FIS failed)
[  406.819017] ata3: hard resetting link
[  416.844648] ata3: softreset failed (device not ready)



   * What exactly did you do (or not do) that was effective (or
 ineffective)?
The following actions have been taken so far, none of which are 
successful:
- Upgraded Dell R210 II's BIOS
- Purchased an entirely new Sandisk TowerRAID TR8M+B
- Replaced the eSATA card - moving from SIL chipset to Marvell
- Replaced all hard drives with brand new 3TB drives.
- Upgraded OS from Debian Jessie to Debian Stretch
- Ensured BIOS was set for maximum performance and not power saving.
- Added noapic, acpi=off, and apm=off kernel parameter options.
- Performed a full on-board health check (part of the Dell on-board 
management abilities), finding no issues.
- Performed an extensive memory test, finding no issues.

   * What was the outcome of this action?
None of the above have helped fix or alter this issue.

   * What outcome did you expect instead?
The timeouts are preventing the external eSATA drives from functioning.


-- Package-specific info:
** Version:
Linux version 4.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-3-amd64 root=/dev/mapper/qub4rt-rootfs ro noapic 
acpi=off apm=off

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Dell Inc.
product_name: PowerEdge R210 II
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: 2.2.3
board_vendor: Dell Inc.
board_name: 03X6X0
board_version: A00

** Loaded modules:
nf_conntrack_ipv6
nf_defrag_ipv6
ip6table_filter
ip6_tables
ipt_MASQUERADE
nf_nat_masquerade_ipv4
xt_nat
iptable_nat
nf_nat_ipv4
nf_nat
xt_TCPMSS
nf_conntrack_ipv4
nf_defrag_ipv4
xt_mac
ipt_REJECT
nf_reject_ipv4
xfrm_user
xt_policy
xt_comment

Bug#864622: RFS: rich-minority/1.0.1-1 [ITP]

[Nicholas D Steeves]

Hi Sean,

On Tue, Jun 13, 2017 at 06:42:28PM +0100, Sean Whitton wrote:
> Hello Nicholas,
> 
> On Mon, Jun 12, 2017 at 07:33:12PM -0400, Nicholas D Steeves wrote:
> > Would it be better to ship README.org and file a bug against the
> > package myself?
> 
> Yes.  Why not ship README.org in the interim?

Let's discuss .org documentation at DebConf.  I've converted the
README to plaintext for now.

> > How many lines can I dedicate to this?  By my count I need to
> > summarise the following in five lines, and the most salient additions
> > are the mention of diminish.el, plus compare/contrast by adding what I
> > suspect are the two most salient points.
> >   * "/missing/...quick and simple replacement functionality"
> >   * the addition of "It accepts *regexps* instead of [individual 
> > specifications]".
> 
> Where are you getting this line limit from?

In the same way that lines must be hard-wrapped to fit a 80 column
terminal I inferred that long description should also fit in a 24 line
terminal, and that README should used for anything longer.  Maybe it's
not a hard rule, but this has always struck me as a sort of standard.
At any rate, I've updated the description.

> > These two points seem contradictory to me.  Do you know how
> > diminish.el is more quick and simple?  Also, can I use your answer for
> > a patch against the upstream description, because I might not be the
> > only one who's not confused about this.  Failing that, I can open an
> > upstream issue/request for clarified description.
> 
> diminish.el works like this:
> 
> (diminish 'auto-fill-function)
> 
> That's it.  Clearly simpler.

I think this is probably the simplest rich-minority-mode equivalent,
assuming that subsequent (diminish 'minor-mode-function) adds items
to-be-hidden:

(push " Fill" rm-blacklist)

I haven't investigated corner cases, but it would seem that
rich-minority-mode might also be simple :-)

All of your comments should be addressed by 419b8ca which I believe is
ready to upload.  I would be very appreciative if you would also grand
DM permissions for it :-)

Thank you,
Nicholas


signature.asc
Description: Digital signature

Bug#867635: mention --target-release will not work on packages already installed

[積丹尼 Dan Jacobson]

Package: aptitude
Version: 0.8.8-1
Severity: wishlist
File: /usr/share/man/man8/aptitude-curses.8.gz

We read
   -t , --target-release 
   Set the release from which packages should be installed. For
   instance, "aptitude -t experimental ..."  will install packages
   from the experimental distribution unless you specify otherwise.

   This will affect the default candidate version of packages
   according to the rules described in apt_preferences(5).

   This corresponds to the configuration item APT::Default-Release.

Mention
   If the packages to be installed are already installed, this
   cannot be used to change their versions! [BUG!]

# apt-cache policy libjavascriptcoregtk-4.0-18
libjavascriptcoregtk-4.0-18:
  Installed: 2.17.4-1
  Candidate: 2.17.4-1
  Version table:
 *** 2.17.4-1 990
990 http://free.nchc.org.tw/debian experimental/main i386 Packages
100 /var/lib/dpkg/status
 2.16.5-1 500
500 http://free.nchc.org.tw/debian unstable/main i386 Packages
# aptitude -t unstable install libjavascriptcoregtk-4.0-18
libjavascriptcoregtk-4.0-18 is already installed at the requested version 
(2.17.4-1)

The "requested version" is the "unstable" version, not what the output
above says, so... BUG! (else why did the user use -t?)

Bug#867634: linux-image-4.9.0-3-amd64: Repeated ESATA softreset failed messages - even after replacing most components.

[madsara]

Package: src:linux
Version: 4.9.30-2+deb9u2
Severity: normal

Dear Maintainer,

   * What led up to the situation?

On a hot day two drives in my eSATA connected Sandisk TowerRAID TR8M+B 
failed. After removing the drives I'm receiving repeated softreset messages - 
even with entirely new equipment (except for the server itself)

This system worked without issue for almost a year. Previous 
incarnations (another server with same NAS) worked for even longer.

The messages received in dmesg (and across the screen)  are:

[  258.182103] ata3: link is slow to respond, please be patient (ready=0)
[  282.190796] ata3: softreset failed (device not ready)
[  282.190862] ata3: limiting SATA link speed to 1.5 Gbps
[  282.190864] ata3: hard resetting link
[  282.914095] ata3: SATA link down (SStatus 100 SControl 310)
[  282.914104] ata3: EH complete
[  282.915391] ata3: exception Emask 0x10 SAct 0x0 SErr 0x404 action 0xe 
frozen
[  282.915460] ata3: irq_stat 0x8040, connection status changed
[  282.915522] ata3: SError: { CommWake DevExch }
[  282.915579] ata3: hard resetting link
[  290.005120] device vlan35 entered promiscuous mode
[  290.005132] device eth0 entered promiscuous mode
[  292.932185] ata3: softreset failed (device not ready)
[  292.932251] ata3: hard resetting link
[  299.197731] ata3: failed to reset engine (errno=-5)
[  303.429384] ata3: softreset failed (1st FIS failed)
[  303.429452] ata3: hard resetting link
[  310.194426] ata3: failed to reset engine (errno=-5)
[  338.896868] ata3: softreset failed (1st FIS failed)
[  338.896943] ata3: limiting SATA link speed to 1.5 Gbps
[  338.896945] ata3: hard resetting link
[  340.119629] ata3: SATA link down (SStatus 100 SControl 310)
[  340.119640] ata3: EH complete
[  340.120968] ata3: exception Emask 0x10 SAct 0x0 SErr 0x404 action 0xe 
frozen
[  340.121048] ata3: irq_stat 0x8040, connection status changed
[  340.121114] ata3: SError: { CommWake DevExch }
[  340.121179] ata3: hard resetting link
[  350.137287] ata3: softreset failed (device not ready)
[  350.137359] ata3: hard resetting link
[  356.402847] ata3: failed to reset engine (errno=-5)
[  360.626520] ata3: softreset failed (1st FIS failed)
[  360.626587] ata3: hard resetting link
[  372.094712] ata3: link is slow to respond, please be patient (ready=0)
[  395.594524] ata3: softreset failed (device not ready)
[  395.594592] ata3: limiting SATA link speed to 1.5 Gbps
[  395.594594] ata3: hard resetting link
[  396.317785] ata3: SATA link down (SStatus 100 SControl 310)
[  396.317797] ata3: EH complete
[  396.319185] ata3: exception Emask 0x10 SAct 0x0 SErr 0x404 action 0xe 
frozen
[  396.319263] ata3: irq_stat 0x8040, connection status changed
[  396.319326] ata3: SError: { CommWake DevExch }
[  396.319389] ata3: hard resetting link
[  402.579341] ata3: failed to reset engine (errno=-5)
[  406.818948] ata3: softreset failed (1st FIS failed)
[  406.819017] ata3: hard resetting link
[  416.844648] ata3: softreset failed (device not ready)



   * What exactly did you do (or not do) that was effective (or
 ineffective)?
The following actions have been taken so far, none of which are 
successful:
- Upgraded Dell R210 II's BIOS
- Purchased an entirely new Sandisk TowerRAID TR8M+B
- Replaced the eSATA card - moving from SIL chipset to Marvell
- Replaced all hard drives with brand new 3TB drives.
- Upgraded OS from Debian Jessie to Debian Stretch
- Ensured BIOS was set for maximum performance and not power saving.
- Added noapic, acpi=off, and apm=off kernel parameter options.
- Performed a full on-board health check (part of the Dell on-board 
management abilities), finding no issues.
- Performed an extensive memory test, finding no issues.

   * What was the outcome of this action?
None of the above have helped fix or alter this issue.

   * What outcome did you expect instead?
The timeouts are preventing the external eSATA drives from functioning.



-- Package-specific info:
** Version:
Linux version 4.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-3-amd64 root=/dev/mapper/qub4rt-rootfs ro noapic 
acpi=off apm=off

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Dell Inc.
product_name: PowerEdge R210 II
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: 2.2.3
board_vendor: Dell Inc.
board_name: 03X6X0
board_version: A00

** Loaded modules:
nf_conntrack_ipv6
nf_defrag_ipv6
ip6table_filter
ip6_tables
ipt_MASQUERADE
nf_nat_masquerade_ipv4
xt_nat
iptable_nat
nf_nat_ipv4
nf_nat
xt_TCPMSS
nf_conntrack_ipv4
nf_defrag_ipv4
xt_mac
ipt_REJECT
nf_reject_ipv4
xfrm_user
xt_policy
xt_comment

Bug#867633: python-confluent-kafka: missing build dependency on python3-all-dev

[Adrian Bunk]

Source: python-confluent-kafka
Version: 0.9.4-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-confluent-kafka.html

...
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-g -O2 -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python3.6m -c confluent_kafka/src/confluent_kafka.c -o 
build/temp.linux-amd64-3.6/confluent_kafka/src/confluent_kafka.o
In file included from confluent_kafka/src/confluent_kafka.c:17:0:
confluent_kafka/src/confluent_kafka.h:17:20: fatal error: Python.h: No such 
file or directory
 #include 
^
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:283: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.6 setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 3.6 3.5 returned exit code 
13
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 25

Bug#867632: python-oslo.rootwrap FTBFS with python 3.6 as supported version

[Adrian Bunk]

Source: python-oslo.rootwrap
Version: 5.1.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-oslo.rootwrap.html

...
==
FAIL: 
oslo_rootwrap.tests.test_rootwrap.DaemonCleanupTestCase.test_daemon_no_cleanup_for_uninitialized_server
oslo_rootwrap.tests.test_rootwrap.DaemonCleanupTestCase.test_daemon_no_cleanup_for_uninitialized_server
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
  File 
"/build/1st/python-oslo.rootwrap-5.1.0/oslo_rootwrap/tests/test_rootwrap.py", 
line 636, in test_daemon_no_cleanup_for_uninitialized_server
config=None, filters=None)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 422, in 
assertRaises
self.assertThat(our_callable, matcher)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 433, in 
assertThat
mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 483, in 
_matchHelper
mismatch = matcher.match(matchee)
  File "/usr/lib/python3/dist-packages/testtools/matchers/_exception.py", line 
108, in match
mismatch = self.exception_matcher.match(exc_info)
  File "/usr/lib/python3/dist-packages/testtools/matchers/_higherorder.py", 
line 62, in match
mismatch = matcher.match(matchee)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 414, in 
match
reraise(*matchee)
  File "/usr/lib/python3/dist-packages/testtools/_compat3x.py", line 16, in 
reraise
raise exc_obj.with_traceback(exc_tb)
  File "/usr/lib/python3/dist-packages/testtools/matchers/_exception.py", line 
101, in match
result = matchee()
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 969, in 
__call__
return self._callable_object(*self._args, **self._kwargs)
  File "/build/1st/python-oslo.rootwrap-5.1.0/oslo_rootwrap/daemon.py", line 
94, in daemon_start
socket_path = os.path.join(temp_dir, "rootwrap.sock")
  File "/usr/lib/python3.6/posixpath.py", line 78, in join
a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not MagicMock


--
Ran 57 tests in 2.630s

FAILED (failures=1, skipped=1)
debian/rules:18: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#867481: [Python-modules-team] Bug#867481: Bug#867481: celery FTBFS: test_recursive runs forever with python 3.6

[Scott Kitterman]

On July 7, 2017 8:16:01 PM EDT, Brian May  wrote:
>Adrian Bunk  writes:
>
>>> * sphinx_celery
>>
>> https://tracker.debian.org/pkg/sphinx-celery
>
>Looks like there is only a Python3 version of the package...

It's DPMT maintained, so you could add the python version.

Scott K

Bug#867631: python-nanomsg: missing build dependency on python3-all-dev

[Adrian Bunk]

Source: python-nanomsg
Version: 1.0-1
Severity: serious
Tags: buster sid

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

...
I: pybuild base:184: python3.6 setup.py test 
running test
running egg_info
writing nanomsg.egg-info/PKG-INFO
writing dependency_links to nanomsg.egg-info/dependency_links.txt
writing top-level names to nanomsg.egg-info/top_level.txt
reading manifest file 'nanomsg.egg-info/SOURCES.txt'
writing manifest file 'nanomsg.egg-info/SOURCES.txt'
running build_ext
building '_nanomsg_cpy' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.6m -c _nanomsg_cpy/wrapper.c 
-o build/temp.linux-amd64-3.6/_nanomsg_cpy/wrapper.o
_nanomsg_cpy/wrapper.c:1:20: fatal error: Python.h: No such file or directory
 #include 
^
compilation terminated.
test_pubsub (unittest.loader._FailedTest) ... ERROR
test_pair (unittest.loader._FailedTest) ... ERROR
test_general_socket_methods (unittest.loader._FailedTest) ... ERROR

==
ERROR: test_pubsub (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_pubsub
Traceback (most recent call last):
  File "/usr/lib/python3.6/unittest/loader.py", line 153, in loadTestsFromName
module = __import__(module_name)
  File "/build/1st/python-nanomsg-1.0/tests/test_pubsub.py", line 8, in 
from nanomsg import (
  File "/build/1st/python-nanomsg-1.0/nanomsg/__init__.py", line 7, in 
from . import wrapper
  File "/build/1st/python-nanomsg-1.0/nanomsg/wrapper.py", line 4, in 
_wrapper = _load_wrapper()
  File "/build/1st/python-nanomsg-1.0/nanomsg_wrappers/__init__.py", line 16, 
in load_wrapper
return importlib.import_module('_nanomsg_' + _choice)
  File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
ImportError: /build/1st/python-nanomsg-1.0/_nanomsg_cpy.so: undefined symbol: 
PyString_FromStringAndSize


==
ERROR: test_pair (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_pair
Traceback (most recent call last):
  File "/usr/lib/python3.6/unittest/loader.py", line 153, in loadTestsFromName
module = __import__(module_name)
  File "/build/1st/python-nanomsg-1.0/tests/test_pair.py", line 8, in 
from nanomsg import (
  File "/build/1st/python-nanomsg-1.0/nanomsg/__init__.py", line 7, in 
from . import wrapper
  File "/build/1st/python-nanomsg-1.0/nanomsg/wrapper.py", line 4, in 
_wrapper = _load_wrapper()
  File "/build/1st/python-nanomsg-1.0/nanomsg_wrappers/__init__.py", line 16, 
in load_wrapper
return importlib.import_module('_nanomsg_' + _choice)
  File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
ImportError: /build/1st/python-nanomsg-1.0/_nanomsg_cpy.so: undefined symbol: 
PyString_FromStringAndSize


==
ERROR: test_general_socket_methods (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_general_socket_methods
Traceback (most recent call last):
  File "/usr/lib/python3.6/unittest/loader.py", line 153, in loadTestsFromName
module = __import__(module_name)
  File "/build/1st/python-nanomsg-1.0/tests/test_general_socket_methods.py", 
line 8, in 
from nanomsg import (
  File "/build/1st/python-nanomsg-1.0/nanomsg/__init__.py", line 7, in 
from . import wrapper
  File "/build/1st/python-nanomsg-1.0/nanomsg/wrapper.py", line 4, in 
_wrapper = _load_wrapper()
  File "/build/1st/python-nanomsg-1.0/nanomsg_wrappers/__init__.py", line 16, 
in load_wrapper
return importlib.import_module('_nanomsg_' + _choice)
  File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
ImportError: /build/1st/python-nanomsg-1.0/_nanomsg_cpy.so: undefined symbol: 
PyString_FromStringAndSize


--
Ran 3 tests in 0.001s

FAILED (errors=3)
Test failed: 

===
WARNING : CPython API extension could not be built.

Exception was : CompileError(DistutilsExecError("command 'x86_64-linux-gnu-gcc' 
failed with exit status 1",),)

If you need the extensions (they may be faster than alternative on some
 platforms) check you have a compiler configured with all 

Bug#867481: [Python-modules-team] Bug#867481: celery FTBFS: test_recursive runs forever with python 3.6

[Brian May]

Adrian Bunk  writes:

>> * sphinx_celery
>
> https://tracker.debian.org/pkg/sphinx-celery

Looks like there is only a Python3 version of the package...
-- 
Brian May 

Bug#867630: python-oslo.service FTBFS with python 3.6 as supported version

[Adrian Bunk]

Source: python-oslo.service
Version: 1.16.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-oslo.service.html

...
===> Testing with python3.6 (python3)
...
==
FAIL: oslo_service.tests.test_service.ProcessLauncherTest.test_stop
oslo_service.tests.test_service.ProcessLauncherTest.test_stop
--
_StringException: Empty attachments:
  stderr
  stdout

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
  File 
"/build/1st/python-oslo.service-1.16.0/oslo_service/tests/test_service.py", 
line 459, in test_stop
mock_kill.mock_calls)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 350, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 435, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: !=:
reference = [call(222, 15), call(22, 15)]
actual= [call(22, ), call(222, )]


--
Ran 121 tests in 49.793s

FAILED (failures=1, skipped=1)
debian/rules:27: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#867629: python-proliantutils FTBFS with python 3.6 as supported version

[Adrian Bunk]

Source: python-proliantutils
Version: 2.1.11-2
Severity: serious
Tags: buster sid

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

...
==
FAIL: 
proliantutils.tests.ilo.test_firmware_controller.FirmwareImageExtractorTestCase.test_successive_calls_to_extract_method
proliantutils.tests.ilo.test_firmware_controller.FirmwareImageExtractorTestCase.test_successive_calls_to_extract_method
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
  File 
"/build/1st/python-proliantutils-2.1.11/proliantutils/tests/ilo/test_firmware_controller.py",
 line 473, in test_successive_calls_to_extract_method
raw_fw_file, is_extracted = fw_img_extractor.extract()
  File 
"/build/1st/python-proliantutils-2.1.11/proliantutils/ilo/firmware_controller.py",
 line 273, in extract
extract_path = os.path.join(temp_dir, self.fw_filename)
  File "/usr/lib/python3.6/posixpath.py", line 78, in join
a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not MagicMock


--
Ran 473 tests in 4.584s

FAILED (failures=1)
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#867628: python-muranoclient FTBFS with python 3.6 as supported version

[Adrian Bunk]

Source: python-muranoclient
Version: 0.11.1-1
Severity: serious
Tags: buster sid

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

...
==
FAIL: 
unittest2.loader._FailedTest.muranoclient.tests.unit.osc.v1.test_environment
unittest2.loader._FailedTest.muranoclient.tests.unit.osc.v1.test_environment
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
muranoclient.tests.unit.osc.v1.test_environment
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File 
"/build/1st/python-muranoclient-0.11.1/muranoclient/tests/unit/osc/v1/test_environment.py",
 line 19, in 
from muranoclient.osc.v1 import environment as osc_env
  File 
"/build/1st/python-muranoclient-0.11.1/muranoclient/osc/v1/environment.py", 
line 19, in 
import jsonpatch
  File "/usr/lib/python3/dist-packages/jsonpatch.py", line 114, in 
json.load = get_loadjson()
  File "/usr/lib/python3/dist-packages/jsonpatch.py", line 108, in get_loadjson
argspec = inspect.getargspec(json.load)
  File "/usr/lib/python3.6/inspect.py", line 1072, in getargspec
raise ValueError("Function has keyword-only parameters or annotations"
ValueError: Function has keyword-only parameters or annotations, use 
getfullargspec() API which can support them


==
FAIL: unittest2.loader._FailedTest.muranoclient.tests.unit.test_shell
unittest2.loader._FailedTest.muranoclient.tests.unit.test_shell
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: muranoclient.tests.unit.test_shell
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File 
"/build/1st/python-muranoclient-0.11.1/muranoclient/tests/unit/test_shell.py", 
line 42, in 
from muranoclient.v1 import shell as v1_shell
  File "/build/1st/python-muranoclient-0.11.1/muranoclient/v1/shell.py", line 
25, in 
import jsonpatch
  File "/usr/lib/python3/dist-packages/jsonpatch.py", line 114, in 
json.load = get_loadjson()
  File "/usr/lib/python3/dist-packages/jsonpatch.py", line 108, in get_loadjson
argspec = inspect.getargspec(json.load)
  File "/usr/lib/python3.6/inspect.py", line 1072, in getargspec
raise ValueError("Function has keyword-only parameters or annotations"
ValueError: Function has keyword-only parameters or annotations, use 
getfullargspec() API which can support them


--
Ran 117 tests in 3.432s

FAILED (failures=2)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#867540: instead: please, update the package to the latest upstream version

[Sam Protsenko]

On Fri, Jul 7, 2017 at 9:51 AM, Lev Lamberov  wrote:
> Source: instead
> Severity: wishlist
>
> Dear Maintainer,
>
> upstream recently released INSTEAD version 3.0.1. Please, consider
> updating to the latest version.
>

Hi,

Work is in progress. I have already managed to build the v3.0.1
package. Now it only takes some polishing. Hopefully it will be done
in a month or so. Upload date depends on my sponsor schedule.

Meanwhile you can track the progress in Gitter chat [1].

[1] https://gitter.im/instead-hub/instead

> Cheers!
> Lev Lamberov
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
> Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
> LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)

Bug#864565: chromium-shell: Couldn't mmap v8 natives data file, status code is 1

[bert schulze]

tag 864565 +patch
thanks

hi,

the chromium-shell binary is not supposed to be installed in /usr/bin
but rather /usr/lib/chromium. debian/chromium-shell.install pushes it
into /usr/bin at the moment.

The v8 natives file referred to is /usr/lib/chromium/natives_blob.bin,
other than that /usr/lib/chromium/snapshot_blob.bin is mandatory.

Moving the binary and running with strace shows:

open("/usr/lib/chromium/natives_blob.bin", O_RDONLY) = -1 ENOENT
open("/usr/lib/chromium/snapshot_blob.bin", O_RDONLY) = -1 ENOENT

Also the chromium package includes content_shell.pak which is not needed
for chromium itself and should be moved into the shell package itself.

open("/usr/lib/chromium/content_shell.pak", O_RDONLY) = -1 ENOENT

As the blobs are needed by both chromium and chromium-shell I'd suggest
to add a new chromium-blobs package and let chromium and chromium-shell
use Depends: chromium-blobs. That way we don't need to waste disk space
by installing chromium if only the shell is needed.


Further the chromium-shell binary wants to open a log within its path.

open("/usr/lib/chromium/content_shell.log", O_WRONLY|O_CREAT|O_APPEND, 0666) = 
-1

This will fail for unprivileged users but does not seem to be fatal.
I've got no idea if theres a build flag to move the logfile somewhere
else e.g. ~/.config/chromium.


build _and_ use-tested patch splitting the V8 blobs and fixing
chromium-shell attached.

bye
diff -Nrup a/debian/chromium-blobs.install b/debian/chromium-blobs.install
--- a/debian/chromium-blobs.install	1970-01-01 01:00:00.0 +0100
+++ b/debian/chromium-blobs.install	2017-07-08 00:25:15.117939830 +0200
@@ -0,0 +1 @@
+out/Release/*_blob.bin usr/lib/chromium
diff -Nrup a/debian/chromium.install b/debian/chromium.install
--- a/debian/chromium.install	2017-04-14 22:47:40.0 +0200
+++ b/debian/chromium.install	2017-07-08 00:25:15.117939830 +0200
@@ -1,8 +1,11 @@
 out/Release/chromium usr/lib/chromium
 out/Release/chrome-sandbox usr/lib/chromium
 
-out/Release/*.bin usr/lib/chromium
-out/Release/*.pak usr/lib/chromium
+out/Release/chrome_*.pak usr/lib/chromium
+out/Release/headless_*.pak usr/lib/chromium
+out/Release/mus_*.pak usr/lib/chromium
+out/Release/*resources.pak usr/lib/chromium
+out/Release/ui_*.pak
 
 out/Release/resources/en-US.pak usr/lib/chromium/locales
 
diff -Nrup a/debian/chromium-shell.install b/debian/chromium-shell.install
--- a/debian/chromium-shell.install	2017-01-02 03:14:00.0 +0100
+++ b/debian/chromium-shell.install	2017-07-08 00:25:15.117939830 +0200
@@ -1 +1,2 @@
-out/Release/chromium-shell usr/bin
+out/Release/chromium-shell usr/lib/chromium
+out/Release/content_shell.pak usr/lib/chromium
diff -Nrup a/debian/control b/debian/control
--- a/debian/control	2017-06-17 22:03:49.0 +0200
+++ b/debian/control	2017-07-08 00:25:15.118939830 +0200
@@ -87,12 +87,24 @@ Build-Depends:
  fonts-ipafont-mincho,
 Standards-Version: 3.9.8
 
+Package: chromium-blobs
+Architecture: i386 amd64 arm64 armhf
+Depends:
+ ${misc:Depends},
+ ${shlibs:Depends},
+Description: web browser - minimal shell
+ Web browser that aims to build a safer, faster, and more stable internet
+ browsing experience.
+ .
+ This package provides the V8 JavaScript engine natives/snapshot blobs.
+
 Package: chromium
 Architecture: i386 amd64 arm64 armhf
 Built-Using: ${Built-Using}
 Depends:
  ${misc:Depends},
  ${shlibs:Depends},
+ chromium-blobs (= ${binary:Version}),
  x11-utils,
  xdg-utils,
 Recommends:
@@ -135,6 +147,7 @@ Architecture: i386 amd64 arm64 armhf
 Depends:
  ${misc:Depends},
  ${shlibs:Depends},
+ chromium-blobs (= ${binary:Version}),
 Description: web browser - minimal shell
  Web browser that aims to build a safer, faster, and more stable internet
  browsing experience.
diff -Nrup a/debian/rules b/debian/rules
--- a/debian/rules	2017-06-17 22:03:49.0 +0200
+++ b/debian/rules	2017-07-08 00:49:11.628934350 +0200
@@ -118,6 +118,9 @@ override_dh_auto_install-arch:
 	mkdir -p $$dst; \
 	cp $$file $$dst/chromium.$$ext; \
 	done
+	# create chromium-shell symlink
+	mkdir -p debian/chromium-shell/usr/bin
+	ln -sf ../lib/chromium/chromium-shell debian/chromium-shell/usr/bin
 
 override_dh_fixperms:
 	dh_fixperms --exclude chrome-sandbox


signature.asc
Description: PGP signature

Bug#867627: python-mox3 FTBFS with python 3.6 as supported version

[Adrian Bunk]

Source: python-mox3
Version: 0.14.0-1
Severity: serious
Tags: buster sid

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

...
==
FAIL: mox3.tests.test_mox.RegexTest.testReprWithFlags
mox3.tests.test_mox.RegexTest.testReprWithFlags
--
_StringException: Traceback (most recent call last):
  File "/build/1st/python-mox3-0.14.0/mox3/tests/test_mox.py", line 319, in 
testReprWithFlags
self.assertTrue(repr(mox.Regex(r"a\s+b", flags=4)) ==
  File "/build/1st/python-mox3-0.14.0/mox3/mox.py", line 1530, in __init__
self.regex = re.compile(pattern, flags=flags)
  File "/usr/lib/python3.6/re.py", line 233, in compile
return _compile(pattern, flags)
  File "/usr/lib/python3.6/re.py", line 301, in _compile
p = sre_compile.compile(pattern, flags)
  File "/usr/lib/python3.6/sre_compile.py", line 562, in compile
p = sre_parse.parse(p, flags)
  File "/usr/lib/python3.6/sre_parse.py", line 865, in parse
p.pattern.flags = fix_flags(str, p.pattern.flags)
  File "/usr/lib/python3.6/sre_parse.py", line 832, in fix_flags
raise ValueError("cannot use LOCALE flag with a str pattern")
ValueError: cannot use LOCALE flag with a str pattern


--
Ran 222 tests in 1.289s

FAILED (failures=1)
debian/rules:26: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#867626: python-json-patch FTBFS with python 3.6 as supported version

[Adrian Bunk]

Source: python-json-patch
Version: 1.19-4
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-json-patch.html

...
set -e ; for pyvers in 2.7 3.6 3.5; do \
PYTHONPATH=/build/1st/python-json-patch-1.19 python$pyvers ./tests.py ; 
\
done
...
--
Ran 67 tests in 0.046s

OK
Traceback (most recent call last):
  File "./tests.py", line 9, in 
import jsonpatch
  File "/build/1st/python-json-patch-1.19/jsonpatch.py", line 114, in 
json.load = get_loadjson()
  File "/build/1st/python-json-patch-1.19/jsonpatch.py", line 108, in 
get_loadjson
argspec = inspect.getargspec(json.load)
  File "/usr/lib/python3.6/inspect.py", line 1072, in getargspec
raise ValueError("Function has keyword-only parameters or annotations"
ValueError: Function has keyword-only parameters or annotations, use 
getfullargspec() API which can support them
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#850965: freecad: GNOME Software catalog entry missing

[asciiwolf]

The issue is still present although the icons and desktop file seems to be
correct. Any ideas?

Bug#720672: gmrun should respect xdg directory base specification (~/.config/gmrun/config)

[Lukas Schwaighofer]

Control: severity -1 wishlist

Hi Thomas,

> it would be nice if gmrun would read its configuration file according
> to the xdg base directory specification and thus not clutter my $HOME:
> http://wiki.debian.org/XDGBaseDirectorySpecification

I agree that this would be desirable.  Unfortunately upstream is dead
and, according to the link you provided, "Debian packages should not be
patched for conformance to avoid unnecessary deviation from upstream
and other distributions."

I'm lowering the severity to wishlist.

Regards
Lukas

Bug#866950: fontconfig: upgrade radically changes font-rendering style with no warning or hint of how to revert

[Soeren D. Schulze]

Changing the value in debconf question in fontconfig also helped, correct?


In my case (fontconfig 2.12.3-0.2, libfreetype6 2.8-0.2), setting
FREETYPE_PROPERTIES was not enough. Only after I've also
dpkg-reconfigured fontconfig to 'Full' hinting style everything got back
to normal (pre 2.12 style).


I can confirm this.  You need both full hinting in debconf as well as 
having FREETYPE_PROPERTIES set.  Having only one of them does not do 
anything.

Bug#866710: Pending fixes for bugs in the golang-go.tools package

[pkg-go-maintainers]

tag 866710 + pending
thanks

Some bugs in the golang-go.tools package are closed in revision
13daba7747e5a45deebe473d73f4750ea702166f in branch 'master' by
Anthony Fok

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-go.tools.git/commit/?id=13daba7

Commit message:

Remove GOROOT hack (needed by gccgo-6 but not gccgo-7)

gccgo-7 no longer installs godoc into $GOROOT/bin like gccgo-6 did,
and the old GOROOT hack would actually cause FTBFS with gccgo-7.
(Closes: #866710)

Bug#507483: Re : Bug#507483 J’espén pouvait avoir une rencontre de plus près Lou

[louis zecchinel]

Bonsoir
Tu es italienne .je serai content de te rencontrer pour te parler in  italiano! 
 A presto .luigi

En date de : Ven 7.7.17, Lou Stamponi  a écrit :

 Objet: Bug#507483 J’espérais qu’on pouvait avoir une rencontre de plus près Lou
 À: sub...@bugs.debian.org
 Date: Vendredi 7 juillet 2017, 15h20
 
 
 
 
   
 

   
   
 Vas-tu me révéler ce que tu aimes? 

 http://bit.ly/2toTEjM
   
 

Bug#749275: PGObject::Util::PseudoCSV PREREQ_PM ?

[Robert J. Clay]

Chris,

On Fri, Jul 7, 2017 at 4:09 PM, Chris Travers 
wrote:

> will fix that in the Makefile.  Basically at present, trying to have
> everything in PGObject::Util be usable by the ecosystem but not depend on
> PGObject base classes or mappers.  The makefile.pl is in error and I will
> fix.
>

>>
OK, I'll make a note of that and keep an eye out for a new updated
version.   (Let me know if I should open an ticket for it.)



-- 
Robert J. Clay
rjc...@gmail.com

Bug#867308: debian-policy: please add "javascript" as a valid value for the Section field

[Josh Triplett]

On Wed, 05 Jul 2017 18:05:01 +0200 Johannes Schauer  wrote:
> Package: debian-policy
> Version: 3.9.8.0
> Severity: wishlist
> 
> According to https://packages.debian.org/unstable/ there exists the
> section "javascript" filled with 1050 packages. But the "javascript"
> section is missing from the list of valid section names in policy §2.4.
> Please add it.

The "rust" section was added at the same time; please add that one as
well.

Bug#507483: Re : Bug#507483 J’espén pouvait avoir une rencontre de plus près Lou

[louis zecchinel]

En date de : Ven 7.7.17, Lou Stamponi  a écrit :

 Objet: Bug#507483 J’espérais qu’on pouvait avoir une rencontre de plus près Lou
 À: sub...@bugs.debian.org
 Date: Vendredi 7 juillet 2017, 15h20
 
 
 
 
   
 

   
   
 Vas-tu me révéler ce que tu aimes? 

 http://bit.ly/2toTEjM
   
 

Bug#867202: Duplicate bug

[Francesco Poli]

Control: forcemerge 867203 867202

These two bug reports are duplicates: I am merging them...

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgps_V2pJgQCF.pgp
Description: PGP signature

Bug#867534: toolz: missing test dep on python3-all

[Diane Trout]

> As a follow-on to bug #867242, the toolz autopkgtests are still
> failing in
> Ubuntu because pyversions -r now returns python3.6 in addition to
> python3.5:

I added the test dependency and uploaded a new version to unstable.
Hope that works.

Diane

Bug#866950: fontconfig: upgrade radically changes font-rendering style with no warning or hint of how to revert

[Tomasz Nitecki]

On 07/07/17 23:06, Laurent Bigonville wrote:
> Le 07/07/17 à 22:52, Soeren D. Schulze a écrit :
>> Am 07.07.2017 um 08:51 schrieb Laurent Bigonville:
>>> Le 07/07/17 à 08:28, Laurent Bigonville a écrit :
 With the updated freefont and fontconfig could you please try to
 regenerate the fontconfig cache files with running (as root):
 "fc-cache -s -f -v" (before doing so maybe try to delete
 ~/.cache/fontconfig in your home) and test again?
>>>
>>> Could you also try to export
>>> FREETYPE_PROPERTIES="truetype:interpreter-version=35" when testing an
>>> application?
>>>
>>> Freetype has also changed his behavior in the last release the version
>>> 35 of the interpreter is the old one
>>
>> The first two suggestions (fc-cache and deleting ~/.cache/fontconfig)
>> do not help, but the last one does.

It worked exactly the same way for me.


> Changing the value in debconf question in fontconfig also helped, correct?

In my case (fontconfig 2.12.3-0.2, libfreetype6 2.8-0.2), setting
FREETYPE_PROPERTIES was not enough. Only after I've also
dpkg-reconfigured fontconfig to 'Full' hinting style everything got back
to normal (pre 2.12 style).


Regards,
T.




signature.asc
Description: OpenPGP digital signature

Bug#866950: fontconfig: upgrade radically changes font-rendering style with no warning or hint of how to revert

[Soeren D. Schulze]

Am 07.07.2017 um 23:06 schrieb Laurent Bigonville:

Changing the value in debconf question in fontconfig also helped, correct?

If it's the case I'll already upload that, for freetype I should maybe
add an entry in the NEWS file as well.


No -- with the new libfreetype6, the only thing that helps is 
FREETYPE_PROPERTIES="truetype:interpreter-version=35".  Neither the 
debconf setting nor local.conf has any effect.

Bug#867625: isc-dhcp: dhclient-script doesn't use configured metric for rfc3442 classless routes, launchpad bug #1664352

[Matthew Heller]

Package: isc-dhcp
Version: 4.3.3-5
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Dear Maintainer,

Please consider the included patch to fix the problem described below
and in Ubuntu bug report:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1664352

As things stand a routing metric configured in /etc/network/interfaces
is applied when the "option routers" value received from DHCP is used to
create a route but when "option classless-static-routes" values are
received the configured metric is ignored. If a system has more than one
network interface providing the same route, for example two interfaces
both providing a default route this 'metric' option (described in
interfaces(5)) is needed to configure a consistent behavior of
prioritizing the route of one interface over the other, otherwise it is a
race condition of last interface up wins.

Before https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592735
and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748272 were fixed,
enforcing rfc3442 complaint behavior of ignoring the 'routers' option
when a 'classless-static-routes' option is present, it was possible to
work around this limitation by omitting the default route from the
'classless-static-routes' list and using the 'routers' option to provide
the default route with metric if configured. Now you are stuck if you
need rfc3442 routes and need to prioritize conflicting routes.

This patch fixes the problem in my environment. The patch provides the
behavior I would expect from the 'metric' option, and I think it is the
correct behavior, since option is currently described in
the interfaces(5) man page dhcp method section as
"Metric for added routes (dhclient)" indicating its application should
not be limited to just cases where the 'routers' option alone is used.


*** /tmp/tmpqO9qiS/bug_body

  * Apply configured metric to rfc3442 routes. Fixes launchpad bug
#1664352


Thanks for considering the patch.

--Matt




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

Kernel: Linux 4.8.0-54-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru isc-dhcp-4.3.3/debian/control isc-dhcp-4.3.3/debian/control
--- isc-dhcp-4.3.3/debian/control	2016-10-21 12:46:20.0 -0400
+++ isc-dhcp-4.3.3/debian/control	2017-07-07 15:31:47.0 -0400
@@ -1,8 +1,7 @@
 Source: isc-dhcp
 Section: net
 Priority: important
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Debian ISC DHCP maintainers 
+Maintainer: Debian ISC DHCP maintainers 
 Uploaders: Andrew Pollock , Michael Gilbert 
 Vcs-Git: git://anonscm.debian.org/pkg-dhcp/isc-dhcp.git
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-dhcp/isc-dhcp.git;a=summary
diff -Nru isc-dhcp-4.3.3/debian/rfc3442-classless-routes.linux isc-dhcp-4.3.3/debian/rfc3442-classless-routes.linux
--- isc-dhcp-4.3.3/debian/rfc3442-classless-routes.linux	2016-10-21 12:46:20.0 -0400
+++ isc-dhcp-4.3.3/debian/rfc3442-classless-routes.linux	2017-07-07 15:31:39.0 -0400
@@ -12,6 +12,7 @@
 	if [ -n "$new_rfc3442_classless_static_routes" ]; then
 		if [ "$reason" = "BOUND" ] || [ "$reason" = "REBOOT" ]; then
 
+			if_metric="$IF_METRIC"
 			set -- $new_rfc3442_classless_static_routes
 
 			while [ $# -gt 0 ]; do
@@ -71,7 +72,8 @@
 
 # set route (ip detects host routes automatically)
 ip -4 route add "${net_address}/${net_length}" \
-	${via_arg} dev "${interface}" >/dev/null 2>&1
+	${via_arg} dev "${interface}" \
+	${if_metric:+metric $if_metric} >/dev/null 2>&1
 			done
 		fi
 	fi

Bug#867624: Debdiff

[Anton Gladky]

Debdiff is applied.

Anton


avogadro.debdiff
Description: Binary data

Bug#867624: stretch-pu: package avogadro/1.2.0-1+deb9u1

[Anton Gladky]

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

Dear release team,

avogadro_1.2.0-1 in stretch has a serious bug #865085 which makes
the package completely unusable.

The reason is the incompatibility with eigen3 >> 3.3 which
was not detected during the development phase. Upstream fixed
this problem [1], [2].

The proposed update fixes the bug. Basically both patches were
applied against the current source package.

Please consider to accept this update, though patches are big.
Otherwise the package should be completely removed from the
stretch not to scare users.

[1] 
https://github.com/cryos/avogadro/commit/43af3c117b0b3220b15c2fe2895b94bbd83d3a60.patch
[2] 
https://github.com/cryos/avogadro/commit/2d4be7ede177a8df7340fe3b209698d591ee8a04.patch


Thank you,

Anton

Bug#866950: fontconfig: upgrade radically changes font-rendering style with no warning or hint of how to revert

[Laurent Bigonville]

Le 07/07/17 à 22:52, Soeren D. Schulze a écrit :

Am 07.07.2017 um 08:51 schrieb Laurent Bigonville:

Le 07/07/17 à 08:28, Laurent Bigonville a écrit :

I'm a bit puzzled here.

With the updated freefont and fontconfig could you please try to
regenerate the fontconfig cache files with running (as root):
"fc-cache -s -f -v" (before doing so maybe try to delete
~/.cache/fontconfig in your home) and test again?


Could you also try to export
FREETYPE_PROPERTIES="truetype:interpreter-version=35" when testing an
application?

Freetype has also changed his behavior in the last release the version
35 of the interpreter is the old one


The first two suggestions (fc-cache and deleting ~/.cache/fontconfig) 
do not help, but the last one does.


Changing the value in debconf question in fontconfig also helped, correct?

If it's the case I'll already upload that, for freetype I should maybe 
add an entry in the NEWS file as well.

Bug#805488: [Patch] Fix (including for a lot of other failing tarballs)

[Lennart Sorensen]

On Fri, Jul 07, 2017 at 10:10:04PM +0200, Tomasz Buchert wrote:
> Wow, this is nice. Would you mind adding some tests to cover this?
> Ideally, we would have coverage for all rsyncable "dialects" we
> support.

I can try to add some test coverage.  I will have to check how to do that.

>Can you commit to collab-maint?

I highly doubt it.  I am not a DD or DM (I keep meaning to become one,
but never seem to get around to it).

-- 
Len Sorensen

Bug#866950: fontconfig: upgrade radically changes font-rendering style with no warning or hint of how to revert

[Soeren D. Schulze]

Am 07.07.2017 um 08:51 schrieb Laurent Bigonville:

Le 07/07/17 à 08:28, Laurent Bigonville a écrit :

I'm a bit puzzled here.

With the updated freefont and fontconfig could you please try to
regenerate the fontconfig cache files with running (as root):
"fc-cache -s -f -v" (before doing so maybe try to delete
~/.cache/fontconfig in your home) and test again?


Could you also try to export
FREETYPE_PROPERTIES="truetype:interpreter-version=35" when testing an
application?

Freetype has also changed his behavior in the last release the version
35 of the interpreter is the old one


The first two suggestions (fc-cache and deleting ~/.cache/fontconfig) do 
not help, but the last one does.



Sören

Bug#867623: heirloom-mailx is not an alternative for /usr/bin/mailx

[Norman Ramsey]

Package: heirloom-mailx
Version: 14.8.16-1
Severity: normal

Dear Maintainer,

I upgraded from jessie to stretch, and I expected to continue using
heirloom-mailx as my implementation of mailx.  But my system was
somehow switched to bsd-mailx.  Worse, update-alternatives is not
capable of changing back:

  nr@homedog ~/e/j/tufts> sudo update-alternatives --config mailx
  There are 2 choices for the alternative mailx (providing /usr/bin/mailx).

SelectionPathPriority   Status
  
  * 0/usr/bin/bsd-mailx   50auto mode
1/usr/bin/bsd-mailx   50manual mode
2/usr/bin/mh/mhmail   25manual mode

I expected /usr/bin/heirloom-mailx to be an alternative on this menu.

This is possibly the same bug as 858080, but I don't know enough
Debian jargon to know for sure.


Norman Ramsey


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

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

Versions of packages heirloom-mailx depends on:
ii  s-nail  14.8.16-1

heirloom-mailx recommends no packages.

heirloom-mailx suggests no packages.

-- no debconf information

Bug#867049: Intending to adopt plplot maintenance for Debian

[Ole Streicher]

Control: owner -1 !
Control: retitle -1 ITA: plplot -- Scientific plotting library

Hi,

since plplot is unmaintained for some time but is a dependency of a few
packages (also from astronomy), I am going to adopt it under the
debian-science umbrella.

I am however not too happy with the adoption, since it is a complex
package and quite a bit out of my own scope. So, if one wants to take
over, I am happy to step back. Co-maintenance and help is also very
welcome; especially for the several language bindings.

This is my plan for the package: Up to now, the debian packaging was
maintained seamlessly in the upstream SVN, which will not be continued,
and is already broken by the last NMUs that were required to keep plplot
in Debian Stretch. Therefore instead of converting this to git, I would
use gbp import-dscs to create a git repository from the Debian packages,
and put that into the Debian Science git. The next steps would be

- switch to gbp for packaging
- update to latest upstream
- modernize/simplify the build and the package structure
- fix the remaining bugs and glitches

This all will take some time, so don't hold breath.

Best regards

Ole

Bug#867609: python-dmidecode: stop linking with libxml2mod

[Adrian Bunk]

On Fri, Jul 07, 2017 at 03:25:29PM -0400, Sandro Tosi wrote:
> control: tags -1 -patch
> 
> On Fri, Jul 7, 2017 at 2:39 PM, Adrian Bunk  wrote:
> > The attached patch copies the two functions used from libxml2mod
> > instead of linking with libxml2mod.
> 
> this seems wrong.

Less wrong than before, which included a copy of prototypes for 
internal python-libxml functions in src/libxml_wrap.h

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#867545: Fails with confusing message when tarball target is a unresolved symlink

[Tomasz Buchert]

retitle 867545 Fails with cryptic message when given paths do not exist
thanks

On 07/07/17 09:57, Guido Günther wrote:
> Package: pristine-tar
> Version: 1.39
> Severity: minor
>
> pristine-tar fails when the target it want's to reproduce is a symlink
> that points nowhere. That by itself is o.k. but the error message is
> confusing:
>
> $ /usr/bin/pristine-tar checkout 
> /var/scratch/src/krb5-auth-dialog/krb5-auth-dialog_3.20.0.orig.tar.xz
> Use of uninitialized value $tarball in -e at /usr/bin/pristine-tar line 
> 454.
> Use of uninitialized value $_[0] in substitution (s///) at 
> /usr/share/perl/5.24/File/Basename.pm line 180.
> fileparse(): need a valid pathname at /usr/bin/pristine-tar line 469.
> pristine-tar: failed to generate tarball
>
> Steps to reproduce:
>
> ln -s /doesnotexist krb5-auth-dialog_3.20.0.orig.tar.xz
> gbp clone vcsgit:krb5-auth-dialog
> /usr/bin/pristine-tar checkout 
> /var/scratch/src/krb5-auth-dialog/krb5-auth-dialog_3.20.0.orig.tar.xz
>

Hey Guido,
thanks for this info, but I think the issue has nothing to do with the
symbolic link, but rather with the fact that the destination directory
does not exist (also in steps above you have to 'cd' into the cloned
repo).

I've committed a change [1] that will verify better what is given from
the command line to all pristine-tar commands.

Thanks,
Tomasz

[1] 
https://anonscm.debian.org/cgit/collab-maint/pristine-tar.git/commit/?id=9265d0c0eea1620370a7261e0a6ee20eb86426fd


signature.asc
Description: PGP signature

Bug#805488: [Patch] Fix (including for a lot of other failing tarballs)

[Tomasz Buchert]

On 07/07/17 10:34, Lennart Sorensen wrote:
> I managed to fix almost half the failures in knownproblems by making
> --gnu always be tried rather than only when GZIP_OS_UNIX is found.
> Doing the same for --rsyncable and --new-rsyncable probably makes sense
> too.
>
> The --new-rsyncable was written for gzip 1.4, while gzip 1.6 does things
> a bit different (it's a bit of a hybrid between the original rsyncable
> and the 1.4 rsyncable).  I have added a new --16-rsyncable option to
> zgz that matches the new behaviour, which fixes this bug.
>
> I have tested both gzip 1.4 and gzip 1.6 with --rsyncable and pristine-tar
> now handles both.
>
> --
> Len Sorensen

Wow, this is nice. Would you mind adding some tests to cover this?
Ideally, we would have coverage for all rsyncable "dialects" we
support.  Can you commit to collab-maint?

Thanks!
Tomasz


signature.asc
Description: PGP signature

Bug#749275: PGObject::Util::PseudoCSV PREREQ_PM ?

[Chris Travers]

will fix that in the Makefile.  Basically at present, trying to have
everything in PGObject::Util be usable by the ecosystem but not depend on
PGObject base classes or mappers.  The makefile.pl is in error and I will
fix.

On Fri, Jul 7, 2017 at 5:54 PM, Robert J. Clay  wrote:

> Chris,
>
> The new v2 of PGObject::Util::PseudoCSV does now build without errors but
> there's something I don't quite understand:  its changelog says "Removed
> dependency on PGObject" but it's still listed as a PREREQ_PM  in the
> Makefile.PL?
>
> Also; it looks like there is a word that is not spelled correctly;  the
> word "unecessary" at line 51 of PseudoCSV.pm.
>
>
>
> --
> Robert J. Clay
> rjc...@gmail.com
>



-- 
Best Wishes,
Chris Travers

Efficito:  Hosted Accounting and ERP.  Robust and Flexible.  No vendor
lock-in.
http://www.efficito.com/learn_more

Bug#867622: tor: after update unable to use/start tor

[shirish शिरीष]

Package: tor
Version: 0.3.0.9-1
Severity: normal

Dear Maintainer,
I used to start tor from an alias

/home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/start-tor-browser

I updated tor as it was out of date and nothing happened.

It seems that the path has been changed to -

/home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/start-tor-browser.desktop

Trying to run that either as an alias or via console I get the following -

┌─[shirish@debian] -
[~/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US] - [10018]
└─[$] ./start-tor-browser.desktop
Launching './Browser/start-tor-browser --detach'...
./Browser/execdesktop: line 14: ./Browser/start-tor-browser: No such
file or directory

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

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

Versions of packages tor depends on:
ii  adduser  3.115
ii  init-system-helpers  1.48
ii  libc62.24-12
ii  libevent-2.0-5   2.0.21-stable-3
ii  libseccomp2  2.3.1-2.1
ii  libssl1.11.1.0f-3
ii  libsystemd0  233-9
ii  lsb-base 9.20161125
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages tor recommends:
ii  logrotate3.11.0-0.1
ii  tor-geoipdb  0.3.0.9-1
ii  torsocks 2.2.0-1

Versions of packages tor suggests:
pn  apparmor-utils   
pn  mixmaster
ii  obfs4proxy   0.0.7-1+b2
ii  obfsproxy0.2.13-2
ii  socat1.7.3.1-2+b1
pn  tor-arm  
ii  torbrowser-launcher  0.2.7-2

-- no debconf information

Looking forward to the fix.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#867621: gnome-music: Gnome music cannot find album covers

[E. Allely]

Package: gnome-music
Version: 3.22.2-1
Severity: normal

Dear Maintainer,

Gnome music cannot find album covers, opening the program from the terminal it
outputs messages similar to the one below.

(gnome-music:1834): Grilo-WARNING **: [lua-library] grl-lua-library.c:504:
Can't fetch element 1 (URL:
https://api.spotify.com/v1/search?q=album:...Calling%20All%20Stations...+artist:Genesis=album=1):
'Authentication required: Unauthorized'
20:56:17 WARNINGcan't find artwork for album '...Calling All
Stations...' by Genesis

I tried to find an alternative way of getting the covers, like maybe using
last.fm, but I did not succeded. So far is just not working.




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

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

Versions of packages gnome-music depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gir1.2-glib-2.0  1.50.0-1+b1
ii  gir1.2-grilo-0.3 0.3.2-2
ii  gir1.2-gst-plugins-base-1.0  1.10.4-1
ii  gir1.2-gstreamer-1.0 1.10.4-1
ii  gir1.2-gtk-3.0   3.22.11-1
ii  gir1.2-mediaart-2.0  1.9.0-2
ii  gir1.2-notify-0.70.7.7-2
ii  gir1.2-totem-plparser-1.03.10.7-1+b1
ii  gir1.2-tracker-1.0   1.10.5-1
ii  gnome-settings-daemon3.22.2-2
ii  grilo-plugins-0.30.3.3-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u1
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgtk-3-0   3.22.11-1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  python3  3.5.3-1
ii  python3-gi   3.22.0-2
ii  python3-gi-cairo 3.22.0-2
ii  python3-requests 2.12.4-1
ii  tracker  1.10.5-1

gnome-music recommends no packages.

gnome-music suggests no packages.

-- no debconf information

Bug#867620: lightdm unlock screen randomly doesn't appear

[Albero87]

Package: lightdm
Version: 1.18.3-3
Severity: important

Dear Maintainer,

This bug is similar but different from other reports.
On startup lightdm work always for me.

When the screen locked, regardless of the cause,
and I move the mouse to resume,
randomly unlock screen doesn't appear.

I see the mouse pointer as a black X
and I can't do anything.

I change tty with CTRL+ALT+1
I enter with my credentials
I can write: "sudo systemctl restart lighdm"
and lightdm unlock screen appears


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

Kernel: Linux 4.9.0-3-amd64 (SMP w/2 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)

Versions of packages lightdm depends on:
ii  adduser3.115
ii  dbus   1.10.18-1
ii  debconf [debconf-2.0]  1.5.61
ii  libaudit1  1:2.7.7-1+b1
ii  libc6  2.24-12
ii  libgcrypt201.7.8-1
ii  libglib2.0-0   2.52.3-1
ii  libpam-systemd 233-9
ii  libpam0g   1.1.8-3.6
ii  libxcb11.12-1
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.2-1
ii  lsb-base   9.20161125

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+19

Versions of packages lightdm suggests:
pn  accountsservice  
ii  upower   0.99.4-4+b1
pn  xserver-xephyr   

-- Configuration Files:
/etc/lightdm/lightdm.conf changed:
[LightDM]
[Seat:*]
greeter-hide-users=false
[XDMCPServer]
[VNCServer]


-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm

Bug#867618: sqlite3: CVE-2017-10989

[Salvatore Bonaccorso]

Source: sqlite3
Version: 3.8.7.1-1
Severity: important
Tags: upstream security patch

Hi,

the following vulnerability was published for sqlite3.

CVE-2017-10989[0]:
| The getNodeSize function in ext/rtree/rtree.c in SQLite before 3.11.0,
| as used in GDAL and other products, mishandles undersized RTree blobs
| in a crafted database, leading to a heap-based buffer over-read or
| possibly unspecified other impact.

Even the above description mentions "before 3.11.0" (and actually would
be 3.17.0) the issue is still present in later versions, it's hidden, as
explained in [1]. There is a patch at [2]. So it might be as well be
applied to newer versions (and it's basically already queued upstream as
well, with the referenced commit).

, [ make test ]
| ...
| ! rtreeA-7.110 expected: [1 {undersize RTree blobs in "t1_node"}]
| ! rtreeA-7.110 got:  [1 {database disk image is malformed}]
| Time: rtreeA.test 56 ms
| ...
`

(unrelated, speaking of testsuite, would be great if #339368 could be
made working in Debian and maybe having autopkgtest smoke-tests running
the upstream testsuite, but not sure how feasible this is).

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-10989
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10989
[1] https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1700937/comments/7
[2] https://sqlite.org/src/info/66de6f4a

Regards,
Salvatore

Bug#867619: libpam-cgfs: failed creating cgroups

[benoit barthelet]

Package: libpam-cgfs
Version: 2.0.7-0ubuntu4
Severity: important

Dear Maintainer,

I couldn't start my unpriviledged containers anymore, seems like the
libpam-cgfs is the culprit, according to the discussion I had here :
https://discuss.linuxcontainers.org/t/failed-creating-cgroups/272/6l
Installing the ubuntu package solved my issue

Using the debian package 2.0.7-1 leads to this type of error while trying to 
start an unpriviledged container

  lxc-start 20170707164658.915 INFO lxc_cgroup - 
cgroups/cgroup.c:cgroup_init:68 - cgroup driver cgroupfs initing for modoboa
  lxc-start 20170707164658.915 ERRORlxc_cgfs - 
cgroups/cgfs.c:lxc_cgroupfs_create:909 - Could not set clone_children to 1 for 
cpuset hierarchy in parent cgroup.
  lxc-start 20170707164658.915 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: failed to 
delete /sys/fs/cgroup/blkio/user.slice
  lxc-start 20170707164658.915 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Read-only file system - cgroup_rmdir: failed 
to delete /sys/fs/cgroup/perf_event/
  lxc-start 20170707164658.915 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Read-only file system - cgroup_rmdir: failed 
to delete /sys/fs/cgroup/freezer/
  lxc-start 20170707164658.915 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: failed to 
delete /sys/fs/cgroup/pids/user.slice/user-1000.slice/session-138.scope
  lxc-start 20170707164658.915 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: failed to 
delete /sys/fs/cgroup/devices/user.slice
  lxc-start 20170707164658.915 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: failed to 
delete /sys/fs/cgroup/cpu,cpuacct/user.slice
  lxc-start 20170707164658.915 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Read-only file system - cgroup_rmdir: failed 
to delete /sys/fs/cgroup/net_cls,net_prio/
  lxc-start 20170707164658.915 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Read-only file system - cgroup_rmdir: failed 
to delete /sys/fs/cgroup/cpuset/
  lxc-start 20170707164658.915 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: failed to 
delete /sys/fs/cgroup/memory/user.slice
  lxc-start 20170707164658.915 ERRORlxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: failed to 
delete /sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-138.scope
  lxc-start 20170707164658.915 ERRORlxc_start - start.c:lxc_spawn:1119 - 
Failed creating cgroups.
  lxc-start 20170707164658.915 ERRORlxc_start - start.c:__lxc_start:1354 - 
Failed to spawn container "modoboa".
 

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

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

Versions of packages libpam-cgfs depends on:
ii  libc6   2.24-12
ii  libpam-runtime  1.1.8-3.6
ii  libpam0g1.1.8-3.6
ii  systemd 233-9

libpam-cgfs recommends no packages.

libpam-cgfs suggests no packages.

-- no debconf information

Bug#867616: src:python-dib-utils: Installs files in python*/dist-packages, but is not python

[Scott Kitterman]

Package: src:python-dib-utils
Version: 0.0.6-1
Severity: normal
Tags: patch

There's no python in this package, so it's a misfeature to install stuff in
the python dist-packages directory.  Please see the attached patch.  As far as
I can tell, it produces a functionally equivalent package.

Scott K
diff -Nru python-dib-utils-0.0.6/debian/control python-dib-utils-0.0.6/debian/control
--- python-dib-utils-0.0.6/debian/control	2014-09-07 14:34:05.0 +
+++ python-dib-utils-0.0.6/debian/control	2014-09-07 14:13:10.0 +
@@ -4,13 +4,6 @@
 Maintainer: PKG OpenStack 
 Uploaders: Thomas Goirand 
 Build-Depends: debhelper (>= 9),
-   openstack-pkg-tools,
-   python-all (>= 2.6.6-3~),
-   python-pbr,
-   python-setuptools,
-   python3-all,
-   python3-pbr,
-   python3-setuptools
 Standards-Version: 3.9.5
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=openstack/python-dib-utils.git
 Vcs-Git: git://anonscm.debian.org/openstack/python-dib-utils.git
@@ -19,7 +12,7 @@
 Package: python-dib-utils
 Architecture: all
 Pre-Depends: dpkg (>= 1.15.6~)
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}
 Description: Standalone tools related to diskimage-builder - Python 2.x
  These tools were originally part of the diskimage-builder project, but they
  have uses outside of that project as well. Because disk space is at a premium
@@ -33,7 +26,7 @@
 Package: python3-dib-utils
 Architecture: all
 Pre-Depends: dpkg (>= 1.15.6~)
-Depends: ${misc:Depends}, ${python3:Depends}
+Depends: ${misc:Depends}
 Description: Standalone tools related to diskimage-builder - Python 3.x
  These tools were originally part of the diskimage-builder project, but they
  have uses outside of that project as well. Because disk space is at a premium
diff -Nru python-dib-utils-0.0.6/debian/rules python-dib-utils-0.0.6/debian/rules
--- python-dib-utils-0.0.6/debian/rules	2014-09-07 14:34:05.0 +
+++ python-dib-utils-0.0.6/debian/rules	2014-09-07 14:13:10.0 +
@@ -1,32 +1,20 @@
 #!/usr/bin/make -f
 
-PYTHONS:=$(shell pyversions -vr)
-PYTHON3S:=$(shell py3versions -vr)
-
 UPSTREAM_GIT = git://github.com//dib-utils.git
-include /usr/share/openstack-pkg-tools/pkgos.make
-
-export OSLO_PACKAGE_VERSION=$(VERSION)
 
 %:
-	dh $@ --buildsystem=python_distutils --with python2,python3
-
-override_dh_install:
-	set -e && for pyvers in $(PYTHONS); do \
-		python$$pyvers setup.py install --install-layout=deb \
-			--root $(CURDIR)/debian/python-dib-utils; \
-	done
-	set -e && for pyvers in $(PYTHON3S); do \
-		python$$pyvers setup.py install --install-layout=deb \
-			--root $(CURDIR)/debian/python3-dib-utils; \
-	done
-	mv $(CURDIR)/debian/python-dib-utils/usr/bin/dib-run-parts $(CURDIR)/debian/python-dib-utils/usr/bin/python2-dib-run-parts
-	mv $(CURDIR)/debian/python3-dib-utils/usr/bin/dib-run-parts $(CURDIR)/debian/python3-dib-utils/usr/bin/python3-dib-run-parts
-	rm -rf $(CURDIR)/debian/python*-dib-utils/usr/lib/python*/dist-packages/*.pth
+	dh $@
 
-override_dh_clean:
-	dh_clean -O--buildsystem=python_distutils
-	rm -rf build
+override_dh_auto_build:
+override_dh_auto_install:
+	mkdir -p $(CURDIR)/debian/python-dib-utils/usr/bin
+	mkdir -p $(CURDIR)/debian/python3-dib-utils/usr/bin
+	cp $(CURDIR)/bin/dib-run-parts $(CURDIR)/debian/python-dib-utils/usr/bin/python2-dib-run-parts
+	cp $(CURDIR)/bin/dib-run-parts $(CURDIR)/debian/python3-dib-utils/usr/bin/python3-dib-run-parts
+
+override_dh_auto_clean:
+	rm -rf $(CURDIR)/debian/python-dib-utils
+	rm -rf $(CURDIR)/debian/python3-dib-utils
 
 # Commands not to run
 override_dh_installcatalogs:

Bug#867617: RFS/ITP: node-rollup-plugin-replace/1.1.1-1

[Julien Puydt]

Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "node-rollup-plugin-replace"

 * Package name: node-rollup-plugin-replace
   Version : 1.1.1-1
   Upstream Author : Rich Harris
 * URL : https://github.com/rollup/rollup-plugin-replace
 * License : Expat
   Section : web

  It builds those binary packages:

node-rollup-plugin-replace - Rollup plugin to make string
substitutions while bundling

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

  https://mentors.debian.net/package/node-rollup-plugin-replace


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

dget -x
https://mentors.debian.net/debian/pool/main/n/node-rollup-plugin-replace/node-rollup-plugin-replace_1.1.1-1.dsc

  It is packaged within the Debian JavaScript Maintainers team:

Vcs-Git:
https://anonscm.debian.org/git/pkg-javascript/node-rollup-plugin-replace.git
Vcs-Browser:
https://anonscm.debian.org/cgit/pkg-javascript/node-rollup-plugin-replace.git

 Thanks,

Snark on #debian-js

Bug#867614: zsh: endless loop when building under "apt-get source -b"

[Sven Joachim]

On 2017-07-07 21:33 +0200, Sven Joachim wrote:

> Source: zsh
> Version: 5.3.1-5
> Severity: normal
>
> Something strange is happening here.  When I try to build zsh with
> "apt-get source -b zsh" in an xterm, during the tests zsh rapidly prints
> the following messages over and over until it is killed:
>
> ,
> | (eval):4: write error: inappropriate ioctl for device
> | (eval):print:4: write error: broken pipe
> `

By piping the output through tee(1) I could capture the messages before
the endless loop and saw this test failure:

,
| Running test: Bug regression: piping to anonymous function; piping to 
backround function
| Pattern match failed:
| <\[<->\] <-> <->
| >[7] 10380 10381
| >[7]  + 10380 running( while :; do; print "This is a line"; done; ) | 
| >   10381 done   () { ... }
| Test ../../Test/A05execution.ztst failed: output differs from expected as 
shown above for:
|   { setopt MONITOR } 2>/dev/null
|   if [[ -o MONITOR ]]
|   then
|( while :; do print "This is a line"; done ) | () : &
|sleep 1
|jobs -l
|   else
|print -u $ZTST_fd "Skipping pipe leak test, requires MONITOR option"
|print "[0] 0 0"
|   fi
| Error output:
| (eval):print:4: write error: broken pipe
| (eval):4: write error: inappropriate ioctl for device
`

Cheers,
   Sven

Bug#867615: ITP: node-rollup-plugin-replace -- Rollup plugin to make string substitutions while bundling

[Julien Puydt]

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

* Package name: node-rollup-plugin-replace
  Version : 1.1.1
  Upstream Author : Rich Harris 
* URL : https://github.com/rollup/rollup-plugin-replace#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Rollup plugin to make string substitutions while
bundling
 This rollup plugin replaces strings in files during the bundling stage
; you
 should ensure it is run early in the bundling pipeline so other plugins can
 apply optimisations such as dead code removal.
 .
 Node.js is an event-based server-side JavaScript engine.


It is a depend of rollup, which I need to update some of my packages.

Snark on #debian-js

Bug#867614: zsh: endless loop when building under "apt-get source -b"

[Sven Joachim]

Source: zsh
Version: 5.3.1-5
Severity: normal

Something strange is happening here.  When I try to build zsh with
"apt-get source -b zsh" in an xterm, during the tests zsh rapidly prints
the following messages over and over until it is killed:

,
| (eval):4: write error: inappropriate ioctl for device
| (eval):print:4: write error: broken pipe
`

These are the final messages after I killed the runaway zsh process:

,
| (eval):4: write error: inappropriate ioctl for device
| (eval):print:4: write error: broken pipe
| Was testing: Bug regression: piping to anonymous function; piping to 
backround function
| ../../Test/A05execution.ztst: test failed.
| The following may (or may not) help identifying the cause:
|   This test checks for two different bugs, a parser segfault piping to an
|   anonymous function, and a descriptor leak when backgrounding a pipeline
| Makefile:187: recipe for target 'check' failed
| make[2]: *** [check] Interrupt
| Makefile:263: recipe for target 'test' failed
| make[1]: *** [test] Interrupt
| dh_auto_test: make -j2 test VERBOSE=1 died with signal 2
| debian/rules:52: recipe for target 'build-arch' failed
| make: *** [build-arch] Interrupt
| dpkg-buildpackage: error: debian/rules build died from signal 2
| E: Build command 'cd zsh-5.3.1 && dpkg-buildpackage -b -uc' failed.
`

Note that this problem does _not_ manifest itself when running
dpkg-buildpackage -b directly instead of under apt-get's control.


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

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

Bug#867609: python-dmidecode: stop linking with libxml2mod

[Sandro Tosi]

control: tags -1 -patch

On Fri, Jul 7, 2017 at 2:39 PM, Adrian Bunk  wrote:
> The attached patch copies the two functions used from libxml2mod
> instead of linking with libxml2mod.

this seems wrong.

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

Bug#867499: tiptop: Fix parallel bison FTBFS

[Tomasz Buchert]

On 07/07/17 00:56, Adrian Bunk wrote:
> [...]

This is amazing, thanks!
Just uploaded 2.3-3 with your fix.

Tomasz


signature.asc
Description: PGP signature

Bug#867613: ITP: gettext-maven-plugin -- plugin to integrate gettext tools into a Maven build

[Markus Koschany]

Package: wnpp
Severity: wishlist
Owner: Markus Koschany 

* Package name: gettext-maven-plugin
  Version : 1.2.9
  Upstream Author : Tammo van Lessen, Steffen Pingel, Felix Berger
* URL : https://github.com/rlf/maven-gettext-plugin
* License : Apache-2.0
  Programming Lang: Java
  Description : plugin to integrate gettext tools into a Maven build

The gettext-commons library combines the power of the unix-style
gettext tools with the widely used Java ResourceBundles. This makes it
possible to use the original text instead of arbitrary property keys,
which is less cumbersome and makes programs easier to read.

This package includes the Maven plugin.

Bug#867612: gdb: Assertion `frame_id_p (*this_id)' failed.

[Joshua Charles Campbell]

Package: gdb
Version: 7.12-6
Severity: normal

Dear Maintainer,

I am experiencing issues debugging the JVM with stock stretch GDB and openjdk.

Steps to reproduce:

1. cd /usr/lib/x86_64-linux-gnu
2. sudo ln -s libpython3.5m.a libpython3.5.a
3. sudo ln -s libpython3.5m.so libpython3.5.so
4. python3 -m virtualenv -p python3 venv3
5. source venv3/bin/activate
6. JCC_JDK=/usr/lib/jvm/java-8-openjdk-amd64
7. pip install jcc==3.0.0 --no-cache-dir
8. gdb --args python -m jcc --package java.lang
9. (gdb) b JNI_CreateJavaVM
10. (gdb) r
11. (gdb) step

Results obtained (GDB 7.12, stretch current latest):

/build/gdb-A87voC/gdb-7.12/gdb/inline-frame.c:167: internal-error: void
inline_frame_this_id(frame_info*, void**, frame_id*): Assertion `frame_id_p
(*this_id)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

Results expected:

I can continue to step through the JVM code.

With GDB 8.0 built from source, GDB does not fail.
With GDB 8.0-1 from experimental, GDB does not fail.




-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (990, 'stable'), (40, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages gdb depends on:
ii  libbabeltrace-ctf1  1.5.1-1
ii  libbabeltrace1  1.5.1-1
ii  libc6   2.24-11+deb9u1
ii  libexpat1   2.2.0-2+deb9u1
ii  liblzma55.2.2-1.2+b1
ii  libncurses5 6.0+20161126-1
ii  libpython3.53.5.3-1
ii  libreadline77.0-3
ii  libtinfo5   6.0+20161126-1
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages gdb recommends:
ii  libc6-dbg [libc-dbg]  2.24-11+deb9u1

Versions of packages gdb suggests:
ii  gdb-doc7.12-2
ii  gdbserver  7.12-6

-- no debconf information

Bug#867611: linux-image-4.9.0-3-arm64: snd-hda-intel.ko module missing

[Ard Biesheuvel]

Package: src:linux
Version: 4.9.30-2+deb9u2
Severity: normal

Dear Maintainer,

Please consider adding CONFIG_SND_HDA_INTEL=m to the arm64 kernel config.

-- Package-specific info:
** Version:
Linux version 4.9.0-3-arm64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-arm64 
root=UUID=f3b7c265-d79f-4dce-8c44-d6120d9111e7 ro earlycon

** Tainted: WI (2560)
 * Taint on warning.
 * Working around severe firmware bug.

** Kernel log:
[6.089313] systemd[1]: Listening on Journal Socket (/dev/log).
[6.109283] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[6.129535] systemd[1]: Created slice System Slice.
[6.145453] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[6.165443] systemd[1]: Created slice system-serial\x2dgetty.slice.
[6.185365] systemd[1]: Listening on Journal Audit Socket.
[6.435663] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
[6.744776] EFI Variables Facility v0.08 2004-May-17
[6.749803] efi_call_virt_check_flags: 268 callbacks suppressed
[6.755747] efi: [Firmware Bug]: IRQ flags corrupted 
(0x0140=>0x0100) by EFI get_next_variable
[6.765128] efi: [Firmware Bug]: IRQ flags corrupted 
(0x0140=>0x0100) by EFI get_next_variable
[6.768835] alg: No test for __ecb-aes-ce (__driver-ecb-aes-ce)
[6.768967] sd 4:0:0:0: Attached scsi generic sg0 type 0
[6.780236] alg: No test for __ecb-aes-ce (cryptd(__driver-ecb-aes-ce))
[6.784251] systemd-journald[214]: Received request to flush runtime journal 
from PID 1
[6.800167] [drm] Initialized
[6.803346] efi: [Firmware Bug]: IRQ flags corrupted 
(0x0140=>0x0100) by EFI get_next_variable
[6.803380] efi: [Firmware Bug]: IRQ flags corrupted 
(0x0140=>0x0100) by EFI get_next_variable
[6.803410] efi: [Firmware Bug]: IRQ flags corrupted 
(0x0140=>0x0100) by EFI get_next_variable
[6.803438] efi: [Firmware Bug]: IRQ flags corrupted 
(0x0140=>0x0100) by EFI get_next_variable
[6.803465] efi: [Firmware Bug]: IRQ flags corrupted 
(0x0140=>0x0100) by EFI get_next_variable
[6.803493] efi: [Firmware Bug]: IRQ flags corrupted 
(0x0140=>0x0100) by EFI get_next_variable
[6.803520] efi: [Firmware Bug]: IRQ flags corrupted 
(0x0140=>0x0100) by EFI get_next_variable
[6.803547] efi: [Firmware Bug]: IRQ flags corrupted 
(0x0140=>0x0100) by EFI get_next_variable
[6.813510] pstore: using zlib compression
[6.816906] pstore: Registered efi as persistent store backend
[6.926537] nouveau :01:00.0: NVIDIA GT218 (0a8280b1)
[7.038991] Adding 976892k swap on /dev/sda3.  Priority:-1 extents:1 
across:976892k SSFS
[7.166280] nouveau :01:00.0: bios: version 70.18.8a.00.06
[7.167145] ax88179_178a 2-1:1.0 eth0: register 'ax88179_178a' at 
usb-:02:00.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 50:3f:56:00:23:f5
[7.167203] usbcore: registered new interface driver ax88179_178a
[7.171345] ax88179_178a 2-1:1.0 enx503f560023f5: renamed from eth0
[7.254405] nouveau :01:00.0: fb: 1024 MiB DDR3
[7.280057] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: 
(null)
[7.834658] IPv6: ADDRCONF(NETDEV_UP): enx503f560023f5: link is not ready
[8.561510] [TTM] Zone  kernel: Available graphics memory: 8190650 kiB
[8.568041] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[8.574569] [TTM] Initializing pool allocator
[8.578937] [TTM] Initializing DMA pool allocator
[8.583669] nouveau :01:00.0: DRM: VRAM: 1024 MiB
[8.588719] nouveau :01:00.0: DRM: GART: 1048576 MiB
[8.594040] nouveau :01:00.0: DRM: TMDS table version 2.0
[8.599789] nouveau :01:00.0: DRM: DCB version 4.0
[8.604929] nouveau :01:00.0: DRM: DCB outp 00: 02000300 
[8.611370] nouveau :01:00.0: DRM: DCB outp 01: 01000302 00020030
[8.617811] nouveau :01:00.0: DRM: DCB outp 02: 02021362 00020010
[8.624253] nouveau :01:00.0: DRM: DCB outp 04: 01032310 
[8.630699] nouveau :01:00.0: DRM: DCB conn 00: 1030
[8.636358] nouveau :01:00.0: DRM: DCB conn 01: 2161
[8.642017] nouveau :01:00.0: DRM: DCB conn 02: 0200
[8.657437] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[8.664052] [drm] Driver supports precise vblank timestamp query.
[8.699486] nouveau :01:00.0: DRM: MM: using COPY for buffer copies
[8.729230] nouveau :01:00.0: No connectors reported connected with modes
[8.736366] [drm] Cannot find any crtc or sizes - going 1024x768
[8.746063] nouveau :01:00.0: DRM: allocated 1024x768 fb: 0x7, bo 
8c556ae7ec00
[8.754469] nouveau :01:00.0: fb0: nouveaufb frame buffer device
[8.777201] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on 
minor 0
[   

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

[Steinar H. Gunderson]

On Fri, Jul 07, 2017 at 08:42:08PM +0200, Jochen Sprickerhof wrote:
> I've created patches for v4.12 (applies to v4.11 as well) and git
> master and send them to the subsystem maintainers. Would be great to see
> them included in the Debian kernel as well.

Thanks for doing this :-) I'd love to see this in a stretch point release
so that we don't have to wait for buster to get XU4 support.

(Granted, I've never tried d-i, but at least then I can rebuild my XU4
images.)

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#865303: Java JNI crashes post CVE-2017-1000364 fixes post 4.9.30-2+deb9u2

[Joshua Campbell]

I am experiencing a related issue which is caused by calling the JNI
JVM init from python.

Steps to reproduce:

1. cd /usr/lib/x86_64-linux-gnu
2. sudo ln -s libpython3.5m.a libpython3.5.a
3. sudo ln -s libpython3.5m.so libpython3.5.so
4. python3 -m virtualenv -p python3 venv3
5. source venv3/bin/activate
6. JCC_JDK=/usr/lib/jvm/java-8-openjdk-amd64
7. pip install jcc --no-cache-dir
8. python -m jcc --package java.lang

Results obtained: SEGV

Results expected: command exits normally

Using 4.9.0-1 (pre-patch for CVE-2017-1000364): command exits normally.

It also works to run python under GDB, break before the JVM calls
os::pd_create_stack_guard_pages (os_linux.cpp:2985) and read enough
stack pages (using x/x) to force the kernel to move the stack guard
far enough for successful execution. This is similar behavior to
compiling C code with -fstack-check, which I assume Python is.

os::pd_create_stack_guard_pages calls mmap() to create the JVM's own
stack-guard pages (which are now unneeded?) which seems to cause linux
kernel to no longer be able to detect when the kernel's stack guard
pages need to be advanced down so the stack guard is then stuck in
place at whatever the largest size of the stack was when
os::pd_create_stack_guard_pages was called. The JVM isn't expecting a
(kernel-created) stack-guard page at this location so it grows the
stack (using alloca()), tries to write to it and SEGV.

Before os::pd_create_stack_guard_pages the linux kernel correctly
detects the page at the top of the stack as the stack page, as
reported by pmap(1) or (gdb) info proc maps. The stack pages are
marked by the kernel as [stack].

After os::pd_create_stack_guard_pages the linux kernel no longer
correctly detects the page the top of the stack as the stack page as
reported by pmap(1) or (gdb) info proc maps. The stack pages are NO
LONGER marked by the kernel as [stack]; and the kernel stack-guard
page is now frozen in place for the remainder of the process
execution.


-- 
Joshua Charles Campbell
Ph.D. Student and Research Assistant
Department of Computing Science
University of Alberta
josh...@ualberta.ca

Bug#867610: python3-libvhdi: Missing python3 interpreter depends

[Scott Kitterman]

Package: python3-libvhdi
Version: 20170223-1
Severity: serious
Tags: patch
Justification: Policy 3.5

python3-libvhdi requires a python3 interpreter to work, but does not have any
dependency on an interpreter due to an incorrect substitution variable.  Patch
attached.

As an added bonus, it would be nice if you could build python3-libvhdi for all
supported python3 versions and not just the default.  This eases python3
transitions considerably.

Please let me know if you do not want me to NMU the package.  I have no
immediate intent to do so, but if this is still open when we swith the default
python3 to python3.6, I will probably do it then.

Scott K
diff -Nru libvhdi-20170223/debian/changelog libvhdi-20170223/debian/changelog
--- libvhdi-20170223/debian/changelog	2017-02-25 04:59:34.0 -0500
+++ libvhdi-20170223/debian/changelog	2017-07-07 14:32:59.0 -0400
@@ -1,3 +1,10 @@
+libvhdi (20170223-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Correct python3-libvhdi depends
+
+ -- Scott Kitterman   Fri, 07 Jul 2017 14:32:37 -0400
+
 libvhdi (20170223-1) unstable; urgency=medium
 
   * New upstream version 20170223
diff -Nru libvhdi-20170223/debian/control libvhdi-20170223/debian/control
--- libvhdi-20170223/debian/control	2017-02-25 04:26:37.0 -0500
+++ libvhdi-20170223/debian/control	2017-07-07 14:33:23.0 -0400
@@ -68,7 +68,7 @@
 Package: python3-libvhdi
 Section: python
 Architecture: any
-Depends: libvhdi1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
+Depends: libvhdi1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
 Description: Virtual Hard Disk image format access library -- Python 3 bindings
  libvhdi is a library to access the Virtual Hard Disk (VHD) image format.
  .

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

[Jochen Sprickerhof]

Control: tags -1 patch

Hi,

I've created patches for v4.12 (applies to v4.11 as well) and git
master and send them to the subsystem maintainers. Would be great to see
them included in the Debian kernel as well.

Cheers Jochen
From 7b12187f59ff43571e664b9f6987534ee622700f Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof 
Date: Fri, 7 Jul 2017 19:38:03 +0200
Subject: [PATCH] v4.12: usb: dwc3: core: Setup phy before trying to read from
 it

Commit c499ff71ff2a ("usb: dwc3: core: re-factor init and exit paths")
moved the call to dwc3_phy_setup() from dwc3_probe() to dwc3_core_init()
and after the dwc3_readl() (now in dwc3_core_is_valid). This broke USB
and Ethernet on Odroid XU4, because dwc3_readl() needs dwc3_phy_setup()
to be run before.

Fix this by moving the call to dwc3_phy_setup() before
dwc3_core_is_valid().

This fixes USB and Ethernet on Odroid XU4.

Also see https://bugs.debian.org/843448

Signed-off-by: Jochen Sprickerhof 
Fixes: c499ff71ff2a ("usb: dwc3: core: re-factor init and exit paths")
---
 drivers/usb/dwc3/core.c | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
index 455d89a1cd6d..2418979a883a 100644
--- a/drivers/usb/dwc3/core.c
+++ b/drivers/usb/dwc3/core.c
@@ -732,6 +732,10 @@ static int dwc3_core_init(struct dwc3 *dwc)
 	u32			reg;
 	int			ret;
 
+	ret = dwc3_phy_setup(dwc);
+	if (ret)
+		goto err0;
+
 	if (!dwc3_core_is_valid(dwc)) {
 		dev_err(dwc->dev, "this is not a DesignWare USB3 DRD Core\n");
 		ret = -ENODEV;
@@ -755,10 +759,6 @@ static int dwc3_core_init(struct dwc3 *dwc)
 	if (ret)
 		goto err0;
 
-	ret = dwc3_phy_setup(dwc);
-	if (ret)
-		goto err0;
-
 	dwc3_core_setup_global_control(dwc);
 	dwc3_core_num_eps(dwc);
 
-- 
2.13.2

From 6b7d33243a364c668530a5ae11ed5a57cecd42d9 Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof 
Date: Fri, 7 Jul 2017 19:38:03 +0200
Subject: [PATCH] usb: dwc3: core: Setup phy before trying to read from it

Commit c499ff71ff2a ("usb: dwc3: core: re-factor init and exit paths")
moved the call to dwc3_phy_setup() from dwc3_probe() to dwc3_core_init()
and after the dwc3_readl() (now in dwc3_core_is_valid). This broke USB
and Ethernet on Odroid XU4, because dwc3_readl() needs dwc3_phy_setup()
to be run before.

Fix this by moving the call to dwc3_phy_setup() before
dwc3_core_is_valid().

This fixes USB and Ethernet on Odroid XU4.

This needs and is supposed to be applied on top of
https://patchwork.kernel.org/patch/9815981/

Also see https://bugs.debian.org/843448

Signed-off-by: Jochen Sprickerhof 
Fixes: c499ff71ff2a ("usb: dwc3: core: re-factor init and exit paths")
---
 drivers/usb/dwc3/core.c | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
index 03474d3575ab..3c6faddc1394 100644
--- a/drivers/usb/dwc3/core.c
+++ b/drivers/usb/dwc3/core.c
@@ -747,6 +747,10 @@ static int dwc3_core_init(struct dwc3 *dwc)
 	u32			reg;
 	int			ret;
 
+	ret = dwc3_phy_setup(dwc);
+	if (ret)
+		goto err0;
+
 	if (!dwc3_core_is_valid(dwc)) {
 		dev_err(dwc->dev, "this is not a DesignWare USB3 DRD Core\n");
 		ret = -ENODEV;
@@ -774,10 +778,6 @@ static int dwc3_core_init(struct dwc3 *dwc)
 	if (ret)
 		goto err0;
 
-	ret = dwc3_phy_setup(dwc);
-	if (ret)
-		goto err0;
-
 	dwc3_core_setup_global_control(dwc);
 	dwc3_core_num_eps(dwc);
 
-- 
2.13.2



signature.asc
Description: PGP signature

Bug#867609: python-dmidecode: stop linking with libxml2mod

[Adrian Bunk]

Package: python-dmidecode
Version: 3.12.2-3
Severity: serious
Tags: patch buster sid

python-libxml2 contains the following change:
-/usr/lib/python2.7/dist-packages/libxml2mod.so
+/usr/lib/python2.7/dist-packages/libxml2mod.x86_64-linux-gnu.so

This makes python-dmidecode FTBFS since it wants to link
dmidecodemod.x86_64-linux-gnu.so with libxml2mod:

x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-HVkOs2/python2.7-2.7.13=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
-std=gnu89 -Wdate-time -D_FORTIFY_SOURCE=2 
build/temp.linux-x86_64-2.7/src/dmidecodemodule.o 
build/temp.linux-x86_64-2.7/src/util.o build/temp.linux-x86_64-2.7/src/dmioem.o 
build/temp.linux-x86_64-2.7/src/dmidecode.o 
build/temp.linux-x86_64-2.7/src/dmixml.o 
build/temp.linux-x86_64-2.7/src/dmierror.o 
build/temp.linux-x86_64-2.7/src/dmilog.o 
build/temp.linux-x86_64-2.7/src/xmlpythonizer.o 
build/temp.linux-x86_64-2.7/src/efi.o build/temp.linux-x86_64-2.7/src/dmidump.o 
-L/usr/lib/python2.7/dist-packages -L/usr/lib/pymodules/python2.7 -lxml2 
-lxml2mod -o build/lib.linux-x86_64-2.7/dmidecodemod.so
/usr/bin/ld: cannot find -lxml2mod


The attached patch copies the two functions used from libxml2mod
instead of linking with libxml2mod.
Description: Stop linking with libxml2mod
 Copy the two funcions used instead of linking with libxml2mod.
Author: Adrian Bunk 

--- python-dmidecode-3.12.2.orig/src/dmidecodemodule.c
+++ python-dmidecode-3.12.2/src/dmidecodemodule.c
@@ -42,7 +42,6 @@
 #include 
 
 #include 
-#include "libxml_wrap.h"
 
 #include "dmidecodemodule.h"
 #include "dmixml.h"
@@ -64,6 +63,32 @@ char *PyUnicode_AsUTF8(PyObject *unicode
 }
 #endif
 
+static PyObject *
+libxml_xmlDocPtrWrap(xmlDocPtr doc)
+{
+PyObject *ret;
+
+if (doc == NULL) {
+Py_INCREF(Py_None);
+return (Py_None);
+}
+ret = PyCapsule_New((void *) doc, (char *) "xmlDocPtr", NULL);
+return (ret);
+}
+
+static PyObject *
+libxml_xmlNodePtrWrap(xmlNodePtr node)
+{
+PyObject *ret;
+
+if (node == NULL) {
+Py_INCREF(Py_None);
+return (Py_None);
+}
+ret = PyCapsule_New((void *) node, (char *) "xmlNodePtr", NULL);
+return (ret);
+}
+
 static void init(options *opt)
 {
 opt->devmem = DEFAULT_MEM_DEV;
--- python-dmidecode-3.12.2.orig/src/setup_common.py
+++ python-dmidecode-3.12.2/src/setup_common.py
@@ -68,9 +68,6 @@ def libxml2_lib(libdir, libs):
 elif l.find('-l') == 0:
 libs.append(l.replace("-l", "", 1))
 
-# this library is not reported and we need it anyway
-libs.append('xml2mod')
-
 
 
 # Get version from src/version.h

Bug#867608: python3-solv: Please build for all supported python3 versions

[Scott Kitterman]

Package: python3-solv
Version: 0.6.28-1
Severity: normal

It makes python3 transitions much easier if packages build for all python3
versions.  I'd offer a patch, but with CDBS I have no idea how to do it.

Scott K

Bug#867342: tor: /usr/bin/obfs4proxy fails to load under default combination of apparmor execution permission PUx and systemd NoNewPrivileges=Yes hardening

[Jason J. Ayala P.]

> Do you mean obfs4proxy (rather than obfsproxy) i.e.:

obfs4proxy, yes. 

> Do you have any AppArmor policy enabled for obfs4proxy? (use aa-status)

No aa profile for /usr/bin/obfs4proxy

With tor@default.service  NoNewPrivileges=yes

Editing abstractions/tor; reparsing with apparmor_parser -r; then restarting 
tor@default…

/usr/bin/obfs4proxy ...
Pux -> Fails
Pix -> Works
pix -> Works

Bug#715271: Preprocessor now handles _Pragma less badly

[Mark Wooding]

I've recently upgraded to stretch (from wheezy), and I thought I'd look
to see whether my compiler bugs have been fixed.  This one is half
fixed.  Specifically, the integrated preprocessor now seems to work the
same way as the separate one, so the second example program, which I
named `pragbug2.c', now seems to be handled correctly.

Alas, the first program is still handled wrongly: the `diagnostic
ignored' pragma somehow escapes the push/pop sandwich it's supposed to
be in.

[stratocaster /tmp/mdw]cat pragbug1.c
#include 

#define PRAGMA(x) _Pragma(#x)

#define WARNING(warn) PRAGMA(GCC diagnostic ignored warn)

#define SANDWICH(warns, filling)\
  _Pragma("GCC diagnostic push")\
  warns \
  filling   \
  _Pragma("GCC diagnostic pop")

#define CHECK(cond) __extension__ ({\
  SANDWICH(WARNING("-Waddress"), !!(cond); )\
})

#define WRAP(x) x

int main(void)
{
  int y = 0;
  if (CHECK()) puts("Hello, world!");
  return (0);
}
[stratocaster /tmp/mdw]gcc -E -o- pragbug1.c
...
# 19 "pragbug1.c"
int main(void)
{
  int y = 0;
  if (__extension__ ({
# 22 "pragbug1.c"
#pragma GCC diagnostic ignored "-Waddress"
# 22 "pragbug1.c"
 
# 22 "pragbug1.c"
#pragma GCC diagnostic push
# 22 "pragbug1.c"
  !!();
# 22 "pragbug1.c"
#pragma GCC diagnostic pop
# 22 "pragbug1.c"
  })) puts("Hello, world!");
  return (0);
}
[stratocaster /tmp/mdw]

-- [mdw]

Bug#867606: ITP: lxqt-themes -- Upstream Themes for LXQt

[Alf Gaida]

Package: wnpp
Severity: wishlist
Owner: Alf Gaida 

* Package name: lxqt-themes
  Version : 0.11.96
  Upstream Author : Alf Gaida 
* URL : http://github.com/lxde/lxqt-themes
* License : LGPL
  Programming Lang: n.A.
  Description : Upstream Themes for LXQt

Several upstream themes for LXQt, including
 - Ambiance
 - Dark
 - Frost
 - Light

This package is the successor of the obsoleted lxqt-commons. The common files
was merged in the matching packages, the themes will be a new package.

Bug#867607: botch: change in file layout in libjs-jquery-tablesorter requires adaptation

[Paul Gevers]

Source: botch
Version: 0.21-3
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Johannes,

I am about to upload jquery-tablesorter to unstable. It replaces jquery-goodies
as the source for libjs-jquery-tablesorter. In the process, I switch upstream
(more active) and build system. As a result, the files in the
libjs-jquery-tablesorter package and up in slightly different
locations. Notably, the theme files are distributed differently. I will in my
next upload include a backword compatibility softlink for the js file in
addons/pager, but all in all it would be better to adapt to the new file layout
(as currently in experimental).

Please let me know if I can do something in the package to lighten the burden.

Paul

- -- System Information:
Debian Release: 9.0
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable'), (200, 'stable'), (50, 
'stable')
Architecture: amd64 (x86_64)

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAllf0M4ACgkQnFyZ6wW9
dQpg7QgAyMv1dpvJ3CZTLbace2PmDbPsy75yaY1kLAUAfsFC2uO2QOw9IuNKSSIu
VYzxf2hAoOehfk2wR4XlDfex1WBdQGRWUzGb0MjyRguXNTPGYMEDMcRLlPtXhHQp
+A6hDE7QnXMLmw+vMKwE0U2O9dOec6rqNjzps40BBTjF3+kAht7P3GBGpmqjJE3x
OmbqS+/ukmQGaWkG3lg0U0ysMu4emh5h5PNDrqRsgIuc302okaNUrDfVofH5Tvt0
W30ov34YWeGS32r8oudShexwI//gGh4MyEAXS14BCrpVbokyR+2pbMYFRq5jc9Ye
t0TIlA2rXdwpXymFEHbEMH0HXmf7+g==
=dpkl
-END PGP SIGNATURE-

Bug#715262: Fixed while I wasn't looking

[Mark Wooding]

I've recently upgraded to stretch (directly from wheezy) and I thought
I'd see if my compiler bugs had been fixed.  And this one has been to my
satisfaction.  Feel free to mark this bug fixed in gcc 4:6.3.0-4.

-- [mdw]

Bug#866768: r-base: R does not set the default user directory.

[Dirk Eddelbuettel]

On Thu, Jul 06, 2017 at 03:37:10PM -0400, Russell Almond wrote:
> Let me add a resounding ME TOO.  This is a bug and I want it fixed.

I essentially stopped reading your mail here.  That tone gets you nowhere.

Dirk

-- 
Three out of two people have difficulties with fractions.

Bug#867586: Shouldn't "amongst" be included?

[Don Armstrong]

Control: severity -1 normal
Control: retitle -1 variants_2 not included (missing 'amongst' among others)
Control: tag -1 pending

On Fri, 07 Jul 2017, 積丹尼 Dan Jacobson wrote:
> Shouldn't "amongst" be included?

Yep; between 7.1 and this version, it seems that the numbering of the
variants was changed.

Fixed in https://git.donarmstrong.com/deb_pkgs/scowl.git/c/8ace845.

-- 
Don Armstrong  https://www.donarmstrong.com

Maybe I did steal your heart
and I am such a perfect criminal
that you never noticed
 -- a softer world #481
http://www.asofterworld.com/index.php?id=481

Bug#866662: Pending fixes for bugs in the golang-gopkg-mcuadros-go-syslog.v2 package

[pkg-go-maintainers]

tag 82 + pending
thanks

Some bugs in the golang-gopkg-mcuadros-go-syslog.v2 package are
closed in revision 3741227bd26e087f631a801f3774b48f461fc15a in branch
'master' by Dr. Tobias Quathamer

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-gopkg-mcuadros-go-syslog.v2.git/commit/?id=3741227

Commit message:

Update expected error string to fix FTBFS.

Closes: #82

Bug#867555: gnome-shell: Tries to drive monitor at unsupported refresh rate

[Simon McVittie]

On Fri, 07 Jul 2017 at 13:20:28 +0100, Mark Brown wrote:
> On Fri, Jul 07, 2017 at 12:44:46PM +0100, Simon McVittie wrote:
> 
> > My first question is, what graphics hardware and driver is this?
> 
> It's this:
> 
> 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc.  [AMD/ATI] 
> Cedar [Radeon HD 5000/6000/7350/8350 Series]
> 
> using whatever Debian drives it with by default.

That would be the radeon or possibly amdgpu kernel driver, together with
corresponding DRM, Mesa and X drivers in user-space, assuming you haven't
installed the proprietary fglrx driver and forgotten you did so.
I'm afraid I don't know the finer points of which driver gets used
for which hardware under which conditions. lsmod would probably tell you.

> > * Move your ~/.config/monitors.xml out of the way (don't delete it; if
> >   this works, it would be useful to see what's in it). This is where
> >   GNOME stores display settings. You could also compare it with
> >   ~/.config/monitors.xml~ which is the second-most-recent version.
> 
> Removing my monitors.xml appears to fix things, the difference appears
> to be that if I try to make any change to the default layout of the
> monitors monitor 1 goes blank.

Thanks. It seems that the mode in which GNOME Shell brings up your
displays when unconfigured is fine, but when you start reconfiguring
(for which I assume you're using gnome-control-center, aka "Settings"?),
some code that only runs during reconfiguration chooses an impossible
mode. Hopefully this will be enough for someone more knowledgeable than
me to narrow down which module has the problem.

> > * Look for mentions of EDID, DDC or mode in the Xorg log
> >   (could be /var/log/Xorg.*.log, ~/.cache/gdm/* or the systemd Journal
> >   depending how your X server was started)
> 
> I'm using a default Debian system with systemd, I don't know how
> specifically the X server is started. The X logs haven't been updated
> for a long time.  There's no obvious X logs in .cache/gdm and I've no
> idea how to get X logs from systemd.

Please check /var/log/syslog (as root or a member of group adm), assuming
you haven't removed rsyslogd. X logs go there via the systemd Journal;
the Journal is in-memory-only by default, because writing it to disk
is mostly redundant with having a syslogd.

> XWAYLAND0 connected 2560x1440+0+0 (0x26) normal (normal left inverted right x 
> axis y axis) 550mm x 310mm

That's XWayland, which uses a Wayland compositor as its "hardware",
and can't do mode switching (it reports that the current Wayland mode
is the only mode possible). When using Wayland, GNOME Shell does the
mode-switching without any X involvement.

If you didn't mean to be using Wayland, please try xrandr under an
X11 GNOME session or a non-GNOME X11 session.

If you are intentionally living in the future, someone who knows more
about the DRI/DRM stack than I do will have to tell you what the
Wayland equivalent of xrandr is. Rummaging in /sys/class/drm/card*/modes,
or using parse-edid < /sys/class/drm/cardwhatever/edid (parse-edid is
in the read-edid package), might be informative?

(GNOME in Debian is probably going to default to Wayland when we upgrade to
GNOME 3.24, but for the 3.22 versions currently in stretch and buster/sid,
using Wayland has too many papercuts to be the default.)

S

Bug#867605: src:sunpy: Binary content for python3-sunpy not built

[Scott Kitterman]

Package: src:sunpy
Version: 0.7.8-1
Severity: important

python3-sunpy is an arch:any package without any binary content.  As built it
can and should be changed to arch:all and the python3-all-dev build-dep
changed to python3-all.

Alternately, compile the binary extenstions for python3 as they are for
python.

As it is, sunpy shows up on the list of packages needing work for python3
transitions, but it doesn't.  Obviously compiling the binary extensions for
all python3 versions would be the best solution, but either of the above
would be an improvement over the current case.

Scott K

Bug#867581: libgnutls30: AES256-GCM emits all-zeros ciphertext on aarch64 with hardware acceleration (upstream bug report)

[Andreas Metzler]

Control: found -1 3.5.8-5
Control: severity -1 serious

On 2017-07-07 Catalin Marinas  wrote:
> Package: libgnutls30
> Version: 3.5.8-5+deb9u1
[...]
> Unrelated gnome-terminal or xfce4-terminal crashing when significant output
> (e.g. running 'yes'; apparently because of the corruption of the encrypted
> scrollback buffer).

> Issue noticed on a Cavium ThunderX running Debian Stretch.

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

> Patching libgnutls with
> https://gitlab.com/gnutls/gnutls/commit/228b18dfbf934d8924d3305dc24d7b0162352eba
> fixes the issue.

> This fix is available in gnutls 3.5.13 (and testing+unstable) but not in 3.5.8
> (stable). Please back-port the above patch to stable.

> Upstream bug report: https://gitlab.com/gnutls/gnutls/issues/204

> I marked it as 'critical' because it breaks unrelated packages, though I'm not
> sure that's the appropriate severity level.
[...]

Hello,

Thanks for the bugreport. I will try to get this fixed via a stable
update.

cu Andreas

PS: I am downgrading to serious. Afaiui this is not "unrelated"
software. Both gnome-terminal and xfce4-terminal link (indirectly)
against gnutls and the error happens when actual gnutls code is invoked.
(For encrypting the scrollback buffer?). The "unrelated software" clause
is about something like a package overwriting /bin/bash.
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#867604: src:grib-api: Please build for all supported python3 versions

[Scott Kitterman]

Package: src:grib-api
Version: 1.19.0-1
Severity: important
Tags: patch

grib-api only builds in python3 support in python3-grib-api for the
default python3 version, but build-depends on python3-all-dev.  Please update
the package to build for all supported python3 versions (currently
python3.5 and python3.6 in sid and buster).  Please see the attached patch. I
test built it and it passed all tests with both python3.6 and python3.6 on
amd64.

Supporting all versions is preferred as we use the build-depends to track what
packages need rebuilding in what stage of a python3 transition and with the
current situation it's possible this will fail to be rebuilt at the
appropriate time and end up RC buggy.

Scott K
diff -Nru grib-api-1.19.0/debian/changelog grib-api-1.19.0/debian/changelog
--- grib-api-1.19.0/debian/changelog	2016-11-28 15:43:29.0 +
+++ grib-api-1.19.0/debian/changelog	2017-07-03 12:44:24.0 +
@@ -1,3 +1,10 @@
+grib-api (1.19.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Build for all supported python3 versions
+
+ -- Scott Kitterman   Mon, 03 Jul 2017 08:44:24 -0400
+
 grib-api (1.19.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru grib-api-1.19.0/debian/rules grib-api-1.19.0/debian/rules
--- grib-api-1.19.0/debian/rules	2016-11-28 15:43:29.0 +
+++ grib-api-1.19.0/debian/rules	2017-07-03 12:44:24.0 +
@@ -14,7 +14,7 @@
 CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS) $(CPPFLAGS)
 LDFLAGS:=$(shell dpkg-buildflags --get LDFLAGS)
 
-PY3VERSM:=$(shell py3versions -d)m
+PY3VERSM:=$(shell py3versions -s)
 
 export LDFLAGS CFLAGS CXXFLAGS
 
@@ -44,33 +44,41 @@
 	dh $@ --buildsystem=cmake --with=python2,python3 --no-parallel
 
 override_dh_auto_configure:
-	F77=gfortran dh_auto_configure --builddirectory=debian/build-py3  -- \
-		-DPYTHON_EXECUTABLE=/usr/bin/python3 \
-		${BUILD_FLAGS} 
+	set -e && for i in $(PY3VERSM); do \
+	  F77=gfortran dh_auto_configure --builddirectory=debian/build-$$i  -- \
+		-DPYTHON_EXECUTABLE=/usr/bin/$$i \
+		${BUILD_FLAGS} ; \
+	  ( cd debian/build-$$i/data ; tar axpf $(CURDIR)/../grib-api_$(UPSTREAM_VERSION).orig-data.tar.xz ) ; \
+	done
 	F77=gfortran dh_auto_configure --builddirectory=debian/build-py2  -- \
 		-DPYTHON_EXECUTABLE=/usr/bin/python2 \
 		${BUILD_FLAGS}
-	( cd debian/build-py3/data ; tar axpf $(CURDIR)/../grib-api_$(UPSTREAM_VERSION).orig-data.tar.xz )
 	( cd debian/build-py2/data ; tar axpf $(CURDIR)/../grib-api_$(UPSTREAM_VERSION).orig-data.tar.xz )
 #	-DENABLE_MEMORY_MANAGEMENT=ON \
 
 
 override_dh_auto_build:
 	dh_auto_build  --builddirectory=debian/build-py2
-	dh_auto_build  --builddirectory=debian/build-py3 
+	set -e && for i in $(PY3VERSM); do \
+	  dh_auto_build  --builddirectory=debian/build-$$i ; \
+	done
 
 override_dh_auto_install:
 	dh_auto_install  --builddirectory=debian/build-py2
-	dh_auto_install  --builddirectory=debian/build-py3 
+	set -e && for i in $(PY3VERSM); do \
+	  dh_auto_install  --builddirectory=debian/build-$$i ; \
+	done
 
 override_dh_auto_test:
 	# We need python code properly installed in debian/tmp to separate python2, python3 extensions when testing
 	(cd debian/build-py2 && $(MAKE) install DESTDIR=$(CURDIR)/debian/tmp AM_UPDATE_INFO_DIR=no)
-	(cd debian/build-py3 && $(MAKE) install DESTDIR=$(CURDIR)/debian/tmp AM_UPDATE_INFO_DIR=no)
 	$(DO_TEST) && ( LD_LIBRARY_PATH=$(CURDIR)/debian/build-py2/lib ; PYTHONPATH=$(CURDIR)/debian/tmp/usr/lib/python2.7/site-packages \
 		dh_auto_test --builddirectory=debian/build-py2  ) || true
-	$(DO_TEST) && ( LD_LIBRARY_PATH=$(CURDIR)/debian/build-py3/lib ; PYTHONPATH=$(CURDIR)/debian/tmp/usr/lib/python3.5/site-packages \
-		dh_auto_test --builddirectory=debian/build-py3  ) || true
+	set -e && for i in $(PY3VERSM); do \
+	  (cd debian/build-$$i && $(MAKE) install DESTDIR=$(CURDIR)/debian/tmp AM_UPDATE_INFO_DIR=no) ; \
+	  $(DO_TEST) && ( LD_LIBRARY_PATH=$(CURDIR)/debian/build-$$i/lib ; PYTHONPATH=$(CURDIR)/debian/tmp/usr/lib/$$i/site-packages \
+		dh_auto_test --builddirectory=debian/build-$$i  ) || true ; \
+	done
 
 override_dh_install:
 	for d in libgrib_api_f77.so  libgrib_api_f90.so	libgrib_api.so ; do \

Bug#867548: playback to HDMI monitor stutters / pauses

[Felipe Sateler]

On Jul 7, 2017 13:06, "Daniel Pocock"  wrote:



On 07/07/17 18:07, Felipe Sateler wrote:
> Control: tags -1 moreinfo
>
> On Fri, Jul 7, 2017 at 4:53 AM, Daniel Pocock  > wrote:
>
> Package: pulseaudio
> Version: 10.0-1
> Severity: important
>
> When playing audio through the HDMI monitor, I've noticed it
> stutters/pauses every few seconds, very briefly, less than a second
each
> time.  It is very irritating to listen to.
>
> In the middle of playback, I can open the GNOME settings panel for
sound
> and switch the output to another device (e.g. my USB sound card
> connected to an amp with an optical cable) and it works fine.  As soon
> as I switch back to the HDMI output the problem comes back.
>
>
> Could you attach a verbose log please?
>
> https://wiki.ubuntu.com/PulseAudio/Log
>


After following those instructions, I don't hear any playback at all



Strange. Any errors in the logfile?


I notice the killall command doesn't actually kill every pulseaudio
process, there is a process running as user Debian-gdm.  Do I need to do
something to stop that too before logging will work?



No, that is not necessary.

Bug#867603: /usr/bin/dgit-badcommit-fixup: does not respect core.sharedrepository

[Sean Whitton]

Package: dgit
Version: 4.0
Severity: normal
File: /usr/bin/dgit-badcommit-fixup

It appears that dgit-badcommit-fixup can leave shared repositories
unpushable by users other than the one that ran dgit-badcommit-fixup.

In particular, .git/objects/foo dirs are left not group-writeable.

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (900, 'stable')
Architecture: i386 (i686)

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

Versions of packages dgit depends on:
ii  apt   1.4.6
ii  ca-certificates   20161130+nmu1
ii  coreutils 8.26-3
ii  curl  7.52.1-5
ii  devscripts2.17.6
ii  dpkg-dev  1.18.24
ii  dput-ng [dput]1.14
ii  git [git-core]1:2.11.0-3
ii  git-buildpackage  0.8.16
ii  libdpkg-perl  1.18.24
ii  libjson-perl  2.90-1
ii  liblist-moreutils-perl0.416-1+b1
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-3
ii  libtext-glob-perl 0.10-1
ii  libtext-iconv-perl1.7-5+b4
ii  libwww-perl   6.15-1
ii  perl  5.24.1-3

Versions of packages dgit recommends:
ii  openssh-client [ssh-client]  1:7.4p1-10

Versions of packages dgit suggests:
ii  sbuild  0.73.0-4

-- no debconf information

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#866564: bind9: CVE-2017-3142 CVE-2017-3143

[rogeriobastos]

We thank you for the great job!

-- 
Rogerio Bastos
PoP-BA/RNP

Bug#866908: updated patch

[Chris West]

Looks like the code that needs patching has been copy-pasted into
WorkArounds.java.

A patch like the following seems to work:

--- 
a/langtools/src/jdk.javadoc/share/classes/jdk/javadoc/internal/doclets/toolkit/WorkArounds.java
+++ 
b/langtools/src/jdk.javadoc/share/classes/jdk/javadoc/internal/doclets/toolkit/WorkArounds.java
@@ -125,7 +125,7 @@ public class WorkArounds {
 }
 
 if (!msgOptionSeen) {
-doclintOpts.add(DocLint.XMSGS_OPTION);
+return;
 }
 
 String sep = "";



Also, the VCS link for the openjdk-9 packaging on
https://tracker.debian.org/pkg/openjdk-9 is dead.

Chris.

Bug#867601: slim: should no longer run the Xorg server as root

[Salvatore Bonaccorso]

Source: slim
Version: 1.3.6-5.1
Severity: wishlist
Tags: security

Hi

Similarly as for lightdm, #809067, the Xorg server no longer needs to
be run as root. Cf. /usr/share/doc/xserver-xorg-core/NEWS.Debian.gz:

cut-cut-cut-cut-cut-cut-
xorg-server (2:1.17.3-1) unstable; urgency=medium

  The Xorg server is no longer setuid root by default.  This change reduces the
  risk of privilege escalation due to X server bugs, but has some side effects:

  * it relies on logind and libpam-systemd
  * it relies on a kernel video driver (so the userspace component doesn't
touch the hardware directly)
  * it needs X to run on the virtual console (VT) it was started from
  * it changes the location for storing the Xorg log from /var/log/ to
~/.local/share/xorg/

  On systems where those are not available, the new xserver-xorg-legacy package
  is needed to allow X to run with elevated privileges.  See the
  Xwrapper.config(5) manual page for configuration details.

 -- Julien Cristau   Tue, 27 Oct 2015 22:54:11 +
cut-cut-cut-cut-cut-cut-

Regards,
Salvatore

Bug#867602: xfce4-datetime-plugin: If attribute gravity set to "auto" xfce4 panel crashes

[Albero87]

Package: xfce4-datetime-plugin
Version: 0.7.0-1
Severity: normal

Dear Maintainer,

when I go to properties of clock > clock options > custom format
and I use attribute gravity in , if I set gravity="auto",
just I press 'o' of 'auto' xfce panel crashes and restart.

Other attributes work, for example, color attribute.
Gravity attribute doesn't work at all
and with "auto" it causes crash

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/2 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)

Versions of packages xfce4-datetime-plugin depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-12
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.52.3-1
ii  libgtk-3-0   3.22.16-1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libxfce4panel-2.0-4  4.12.1-2
ii  libxfce4ui-2-0   4.12.1-2
ii  libxfce4util74.12.1-3

xfce4-datetime-plugin recommends no packages.

xfce4-datetime-plugin suggests no packages.

-- no debconf information

Bug#867600: 0 bytes/s vs. ∞ bytes/s

[積丹尼 Dan Jacobson]

Package: git
Version: 1:2.13.2+next.20170630-1
Severity: minor

One sees
Receiving objects: 100% (1003/1003), 1.15 MiB | 0 bytes/s, done.
Receiving objects: 100% (1861/1861), 11.74 MiB | 4.58 MiB/s, done.
Receiving objects: 100% (474/474), 160.72 KiB | 0 bytes/s, done.
Receiving objects: 100% (7190/7190), 26.02 MiB | 6.53 MiB/s, done.

But if the connection is too fast to calculate, please say
∞ bytes/s or
inf bytes/s or
? bytes/s
Anything but 0 bytes/s, which means nothing (transmitted.)

[My mail to g...@vger.kernel.org never makes it. Hence filing with Debian.]

Bug#866564: bind9: CVE-2017-3142 CVE-2017-3143

[Salvatore Bonaccorso]

Hi

On Fri, Jul 07, 2017 at 09:42:05AM -0300, rogeriobas...@pop-ba.rnp.br wrote:
> Hi,
> 
> This bug is marked as fixed in versions bind9/1:9.9.5.dfsg-9+deb8u12, 
> bind9/1:9.10.3.dfsg.P4-12.3+deb9u1 but they are not available in security 
> repository.
> Is there anything holding it ?

The reason is, the update was prepared and uploaded to be released,
but did not contain the bug closer. So I did that manually. Due to
some technical reasons on the archive side we could not yet release
the fixed packages, but that should happen soonish now.

Apologies for the delay,

Regards,
Salvatore

Bug#818971: firefox-kwallet5 1.3 -please retest your issue

[Gregor Riepl]

> Which version of Firefox are you using? I cannot confirm this problem with
> 52.2.0 (64-Bit). I deleted and re-added a password. The entry is present in
> the KWallet Manager and in Firefox, and used at the next login.

Interesting.

I see the problem in firefox-esr (52.2) and firefox (54.0), but not in
thunderbird (52.2). I suspect it may have something to do with the new
password entry widget in FF50+?

Bug#867599: gem2deb fails to install pure ruby part when a gem has both pure ruby and native libs

[Pirate Praveen]

package: gem2deb
version: 0.34

gem2deb is not installing the pure ruby libraries of grpc (ruby-grpc is
in alioth) and tests fail.

──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rake
  │
└──┘

RUBYLIB=/<>/debian/ruby-grpc/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0:.
GEM_PATH=debian/ruby-grpc/usr/share/rubygems-integration/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
ruby2.3 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.3 /usr/bin/rspec --pattern
./src/ruby/spec/\*\*/\*_spec.rb --format documentation
/<>/src/ruby/lib/grpc/errors.rb:48:in `':
uninitialized constant GRPC::Core (NameError)
from /<>/src/ruby/lib/grpc/errors.rb:45:in `'
from /<>/src/ruby/lib/grpc/errors.rb:33:in `'
from /<>/src/ruby/lib/grpc.rb:32:in `require_relative'
from /<>/src/ruby/lib/grpc.rb:32:in `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from /<>/src/ruby/spec/call_credentials_spec.rb:30:in
`'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in 
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:100:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:86:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
from /usr/bin/rspec:4:in `'
/usr/bin/ruby2.3 /usr/bin/rspec --pattern
./src/ruby/spec/\*\*/\*_spec.rb --format documentation failed
ERROR: Test "ruby2.3" failed. Exiting.



signature.asc
Description: OpenPGP digital signature

Bug#867598: irssi: CVE-2017-10965 CVE-2017-10966

[Salvatore Bonaccorso]

Source: irssi
Version: 0.8.17-1
Severity: important
Tags: upstream patch security fixed-upstream

Hi,

the following vulnerabilities were published for irssi.

CVE-2017-10965[0]:
| An issue was discovered in Irssi before 1.0.4. When receiving messages
| with invalid time stamps, Irssi would try to dereference a NULL
| pointer.

CVE-2017-10966[1]:
| An issue was discovered in Irssi before 1.0.4. While updating the
| internal nick list, Irssi could incorrectly use the GHashTable
| interface and free the nick while updating it. This would then result
| in use-after-free conditions on each access of the hash table.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-10965
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10965
[1] https://security-tracker.debian.org/tracker/CVE-2017-10966
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10966
[2] https://irssi.org/security/irssi_sa_2017_07.txt
[3] 
https://github.com/irssi/irssi/commit/5e26325317c72a04c1610ad952974e206384d291

Regards,
Salvatore

Bug#867548: playback to HDMI monitor stutters / pauses

[Daniel Pocock]

On 07/07/17 18:07, Felipe Sateler wrote:
> Control: tags -1 moreinfo
> 
> On Fri, Jul 7, 2017 at 4:53 AM, Daniel Pocock  > wrote:
> 
> Package: pulseaudio
> Version: 10.0-1
> Severity: important
> 
> When playing audio through the HDMI monitor, I've noticed it
> stutters/pauses every few seconds, very briefly, less than a second each
> time.  It is very irritating to listen to.
> 
> In the middle of playback, I can open the GNOME settings panel for sound
> and switch the output to another device (e.g. my USB sound card
> connected to an amp with an optical cable) and it works fine.  As soon
> as I switch back to the HDMI output the problem comes back.
> 
> 
> Could you attach a verbose log please?
> 
> https://wiki.ubuntu.com/PulseAudio/Log
>  


After following those instructions, I don't hear any playback at all

I notice the killall command doesn't actually kill every pulseaudio
process, there is a process running as user Debian-gdm.  Do I need to do
something to stop that too before logging will work?

Regards,

Daniel

Bug#395295: This could probably be closed

[Dominique Brazziel]

ll /dev/nbd*
brw-rw 1 root disk 43,   0 Jul  6 08:31 /dev/nbd0
brw-rw 1 root disk 43,  16 Jul  6 08:31 /dev/nbd1
brw-rw 1 root disk 43, 160 Jul  6 08:31 /dev/nbd10
brw-rw 1 root disk 43, 176 Jul  6 08:31 /dev/nbd11
brw-rw 1 root disk 43, 192 Jul  6 08:31 /dev/nbd12
brw-rw 1 root disk 43, 208 Jul  6 08:31 /dev/nbd13
brw-rw 1 root disk 43, 224 Jul  6 08:31 /dev/nbd14
brw-rw 1 root disk 43, 240 Jul  6 08:31 /dev/nbd15
brw-rw 1 root disk 43,  32 Jul  6 08:31 /dev/nbd2
brw-rw 1 root disk 43,  48 Jul  6 08:31 /dev/nbd3
brw-rw 1 root disk 43,  64 Jul  6 08:31 /dev/nbd4
brw-rw 1 root disk 43,  80 Jul  6 08:31 /dev/nbd5
brw-rw 1 root disk 43,  96 Jul  6 08:31 /dev/nbd6
brw-rw 1 root disk 43, 112 Jul  6 08:31 /dev/nbd7
brw-rw 1 root disk 43, 128 Jul  6 08:31 /dev/nbd8
brw-rw 1 root disk 43, 144 Jul  6 08:31 /dev/nbd9

Bug#867597: stretch-pu: package retext/6.0.2-2+deb9u1

[Dmitry Shachnev]

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

Dear release team,

I would like to request a Stretch update for ReText.

The attached debdiff fixes two issues:

* RC bug #863640 — segfault in XSettings code.
* Syntax error in the appdata XML file.

Both these issues are fixed in current version in testing, 7.0.1-1.

-- 
Dmitry Shachnev
diff -Nru retext-6.0.2/debian/changelog retext-6.0.2/debian/changelog
--- retext-6.0.2/debian/changelog	2016-10-03 23:51:39.0 +0300
+++ retext-6.0.2/debian/changelog	2017-07-07 19:35:28.0 +0300
@@ -1,3 +1,10 @@
+retext (6.0.2-2+deb9u1) stretch; urgency=medium
+
+  * Backport upstream fix for crash in XSettings code (closes: #863640).
+  * Backport upstream patch to fix syntax in appdata XML file.
+
+ -- Dmitry Shachnev   Fri, 07 Jul 2017 19:35:28 +0300
+
 retext (6.0.2-2) unstable; urgency=medium
 
   * Do not remove testdata directory during clean.
diff -Nru retext-6.0.2/debian/patches/appdata_closing_tag.diff retext-6.0.2/debian/patches/appdata_closing_tag.diff
--- retext-6.0.2/debian/patches/appdata_closing_tag.diff	1970-01-01 03:00:00.0 +0300
+++ retext-6.0.2/debian/patches/appdata_closing_tag.diff	2017-07-07 19:35:28.0 +0300
@@ -0,0 +1,15 @@
+Description: fix closing tag in appdata XML file
+Origin: upstream, https://github.com/retext-project/retext/commit/49e4de2b11b24ab4
+Last-Update: 2017-07-07
+
+--- a/data/me.mitya57.ReText.appdata.xml
 b/data/me.mitya57.ReText.appdata.xml
+@@ -28,7 +28,7 @@
+ ReText is a text editor for plain text markup languages, such as Markdown and reStructuredText.
+ It supports tabs, live text preview, synchronized scrolling (for Markdown) and syntax highlighting.
+ ReText can export to HTML, ODT and PDF formats. It is also possible to write custom export extensions.
+-  
++  
+   https://github.com/retext-project/retext
+   CC0
+   GPL-2.0+
diff -Nru retext-6.0.2/debian/patches/fix_xsettings_segfault.diff retext-6.0.2/debian/patches/fix_xsettings_segfault.diff
--- retext-6.0.2/debian/patches/fix_xsettings_segfault.diff	1970-01-01 03:00:00.0 +0300
+++ retext-6.0.2/debian/patches/fix_xsettings_segfault.diff	2017-07-07 19:35:28.0 +0300
@@ -0,0 +1,15 @@
+Description: fix crash when freeing result of xcb_get_property_reply
+Origin: upstream, https://github.com/retext-project/retext/commit/fb5c5b8aae2ce904
+Last-Update: 2017-07-07
+
+--- a/ReText/xsettings.py
 b/ReText/xsettings.py
+@@ -64,6 +64,8 @@
+ 	c = ctypes.CDLL(c_library_name)
+ 
+ 	# set some args and return types
++	c.free.argtypes = [ctypes.c_void_p]
++	c.free.restype = None
+ 	xcb.xcb_connect.argtypes = [ctypes.c_char_p, ctypes.POINTER(ctypes.c_int)]
+ 	xcb.xcb_connect.restype = ctypes.c_void_p
+ 	xcb.xcb_connection_has_error.argtypes = [ctypes.c_void_p]
diff -Nru retext-6.0.2/debian/patches/series retext-6.0.2/debian/patches/series
--- retext-6.0.2/debian/patches/series	1970-01-01 03:00:00.0 +0300
+++ retext-6.0.2/debian/patches/series	2017-07-07 19:35:28.0 +0300
@@ -0,0 +1,2 @@
+fix_xsettings_segfault.diff
+appdata_closing_tag.diff


signature.asc
Description: PGP signature