Bug#851927: 851927

[Sébastien Delafond]

I see the same problem, even with -enable-rmeote-extensions (which seems
to be about *installing* remote extensions, not enabling
already-installed ones).

However, my local extensions are still present (see
~/.config/chromium/Default/Extensions/*), and downgading to the version
in stretch (55.0.2883.75-3) brings them back.

Cheers,

--Seb

Processed: notfound 851927 in 55.0.2883.75-3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 851927 55.0.2883.75-3
Bug #851927 [chromium] chromium: Update removed all (local) installed extensions
Ignoring request to alter found versions of bug #851927 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
851927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 851927 in 55.0.2883.75-4

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 851927 55.0.2883.75-4
Bug #851927 [chromium] chromium: Update removed all (local) installed extensions
Marked as found in versions chromium-browser/55.0.2883.75-4.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
851927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851733: marked as done (ocd data files are arch dependent)

[Debian Bug Tracking System]

Your message dated Fri, 20 Jan 2017 07:34:03 +
with message-id 
and subject line Bug#851733: fixed in opencc 1.0.4-5
has caused the Debian Bug report #851733,
regarding ocd data files are arch dependent
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opencc
Version: 1.0.4-4
Severity: important

Hi,

Opencc will abort unexpectedly on i386/armhf.

Steps to reproduce:

1. sh -c "opencc"

Stderr:

terminate called after throwing an instance of 'std::length_error'
  what():  basic_string::_M_replace_aux

Thanks.



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

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

Versions of packages opencc depends on:
ii  libc6   2.24-9
ii  libgcc1 1:6.3.0-2
ii  libopencc2  1.0.4-4
ii  libstdc++6  6.3.0-2

opencc recommends no packages.

opencc suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: opencc
Source-Version: 1.0.4-5

We believe that the bug you reported is fixed in the latest version of
opencc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated opencc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 20 Jan 2017 15:15:35 +0800
Source: opencc
Binary: opencc libopencc2 libopencc-dev libopencc2-data
Architecture: source amd64 all
Version: 1.0.4-5
Distribution: unstable
Urgency: medium
Maintainer: IME Packaging Team 
Changed-By: Aron Xu 
Description:
 libopencc-dev - simplified-traditional Chinese conversion library - development
 libopencc2 - simplified-traditional Chinese conversion library - runtime
 libopencc2-data - simplified-traditional Chinese conversion library - data 
files
 opencc - simplified-traditional Chinese conversion tool
Closes: 851733
Changes:
 opencc (1.0.4-5) unstable; urgency=medium
 .
   * Make ocd data files arch:any (Closes: #851733)
Checksums-Sha1:
 197bc31f29d0cb373bc58579ea467691b83a5bcd 1893 opencc_1.0.4-5.dsc
 e00623580ad085d5bccba53654ccba458822834a 5900 opencc_1.0.4-5.debian.tar.xz
 5d9b20d298cb2605ff9580136225044583b4f80d 15730 libopencc-dev_1.0.4-5_amd64.deb
 76a125bca63e4d3d34635287da717bd02e15cea3 117324 libopencc2-data_1.0.4-5_all.deb
 a67a43dfd8d240b9480fb8d08102c892e13f0ce4 1165106 
libopencc2-dbgsym_1.0.4-5_amd64.deb
 b058d145933b64d2c47f2bfd41386c9f1060dbe6 1204152 libopencc2_1.0.4-5_amd64.deb
 7ed3d925ae6e6252d367a183b359da801ab6ad98 756236 opencc-dbgsym_1.0.4-5_amd64.deb
 c03b5ec754d1223306871c1429969e2654bb9cb0 7123 opencc_1.0.4-5_amd64.buildinfo
 cca2cbb8eccb5832ece56352845633aaa744a334 87540 opencc_1.0.4-5_amd64.deb
Checksums-Sha256:
 cc66ffe1098a95e63be1e0a13594c5cf8ee277a5e2fb2d883f2207b775fb8a88 1893 
opencc_1.0.4-5.dsc
 ab9b5f468003acd646fca377b3124d7188273f58864428a12869f81cc74ac372 5900 
opencc_1.0.4-5.debian.tar.xz
 f1fdb9cf2a55eacae673e5cfafaee5a48273e1fc78707ec3f3e32016ab14e37a 15730 
libopencc-dev_1.0.4-5_amd64.deb
 e7fde273828f17f520fba97309c590c2887d948368ff7baa06ed6ba767229c90 117324 
libopencc2-data_1.0.4-5_all.deb
 3f2d48d73bd3d7c453fd04138328eeef38b1132a74765ae2c69beb525b0736d9 1165106 
libopencc2-dbgsym_1.0.4-5_amd64.deb
 c22c7327ac9a7eaecabc5e73c35c4625eb0d4f3ba05ddb73193fe52531f1ad48 1204152 
libopencc2_1.0.4-5_amd64.deb
 c2ab30ff71885b16d6df6edb0d5b8f674da6d7c0c15d45f9cf970bd08e390359 756236 
opencc-dbgsym_1.0.4-5_amd64.deb
 97301c321a958f1807aaa87997bfa40a023745c4f1c059766f1dade4cdf2d7d1 7123 
opencc_1.0.4-5_amd64.buildinfo
 6387dd935b34fa7007dc960f487a39cfb3c7912b6f55d0dec60cd3d12b3ab8a0 87540 
opencc_1.0.4-5_amd64.deb
Files:
 

Processed: Re: [Pkg-ime-devel] Bug#851733: opencc: SIGABRT on i386/armhf architecture

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 ocd data files are arch dependent
Bug #851733 [opencc] opencc: SIGABRT on i386/armhf architecture
Changed Bug title to 'ocd data files are arch dependent' from 'opencc: SIGABRT 
on i386/armhf architecture'.
> severity -1 serious
Bug #851733 [opencc] ocd data files are arch dependent
Severity set to 'serious' from 'important'

-- 
851733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 851161 to ruby2.1: CVE-2016-2337 CVE-2016-2339

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 851161 ruby2.1: CVE-2016-2337 CVE-2016-2339
Bug #851161 [ruby2.1] ruby2.3: CVE-2016-2337 CVE-2016-2339
Changed Bug title to 'ruby2.1: CVE-2016-2337 CVE-2016-2339' from 'ruby2.3: 
CVE-2016-2337 CVE-2016-2339'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
851161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851161: CVE-2016-2337 CVE-2016-2339

[Salvatore Bonaccorso]

On Fri, Jan 20, 2017 at 01:13:41AM +0100, Christian Hofstaedtler wrote:
> Control: reassign -1 ruby2.1
> Control: found -1 2.1.5-2+deb8u3
> 
> Hi,
> 
> * Moritz Muehlenhoff  [170120 00:05]:
> > this has been assigned CVE-2016-2339: 
> > http://www.talosintelligence.com/reports/TALOS-2016-0034/
> > 
> > Patch is here: 
> > https://github.com/ruby/ruby/commit/bcc2421b4938fc1d9f5f3fb6ef2320571b27af42
> 
> If I'm reading all those right, this is actually fixed since 2.3.0;
> this issue is likely open in 2.1.x. Reassigning.

Confirmed for 2.1.x, the POC in a jessie VM:

$ ruby CVE-2016-2339.rb 
Start
args array size : 1
increase size of array
New args array size is : 11
*** Error in `ruby': free(): invalid next size (fast): 0x00ea3590 ***
Aborted

It was confusing that TALOS report mentions that it was tested with 2.3.0 dev,
but this might then be right, the above commit is included ongoing from 2.3.0.

> For the TclTk issue, looks like this upstream patch:
> https://github.com/ruby/ruby/commit/a2b8925a94a672235ca6a16e584bf09026a957ab
> If this is the correct patch, 2.3.0 has this fixed, but 2.1.x needs
> a patch.

Thanks added the commit as well, and the fixed version to the tracker. I
*think*, although a problem in the source, this might not rally need an update
in jessie via a DSA, since the issue is incombination with cancel_eval which is
supported in Tcl/Tk8.6 or later, but we don't have that for jessie. So I would
tend to just mark that one as no-dsa at least. Or do I miss something?

Regards,
Salvatore

Bug#849756: [Pkg-sssd-devel] Bug#849756: sssd-ldap fails to connect to ldaps:// due to problem with non-blocking socket

[Timo Aaltonen]

On 18.01.2017 11:09, Tomas Forsman wrote:
> Hello.
> 
> Applying the patch from https://github.com/SSSD/sssd/pull/67 onto sssd
> 1.14.2-1 in stretch, will make both ldaps:// and ldap://+starttls work
> again. Applies cleanly, no regression found so far.
> 
> It would be quite unfortunate to have stretch without this fix, as I
> believe ldap(s) support is one of the primary uses for sssd.

I hope to get 1.15 in stretch.. they'd just need to release it first and
time is running short.


-- 
t

Bug#851934: date: regression in 8.26-1: conversion from one timezone to another TZ no longer works

[Paul Wise]

Package: coreutils
Version: 8.26-1
Severity: serious
User: coreut...@packages.debian.org
Usertags: date

There is a regression from jessie, it is no longer possible to choose
the TZ of the output date when providing a TZ for the input date, which
means I can no longer use date to convert between timezones easily.
I have tested that downgrading to coreutils 8.25-2+b1 fixes the issue.

On jessie:

$ TZ="Europe/London" date -d 'TZ="Australia/Perth" 2016-08-15 07:00'
Monday 15 August  00:00:00 BST 2016

On stretch:

$ TZ="Europe/London" date -d 'TZ="Australia/Perth" 2016-08-15 07:00'
Mon 15 Aug 07:00:00 AWST 2016

-- System Information:
Debian Release: 9.0
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages coreutils depends on:
ii  libacl1  2.2.52-3
ii  libattr1 1:2.4.47-2
ii  libc62.24-9
ii  libselinux1  2.6-3

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Processed: Re: libmutter-cogl.so: cannot open shared object file: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugzilla.gnome.org/777519
Bug #851925 [gnome-shell] libmutter-cogl.so: cannot open shared object file: No 
such file or directory
Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/777519'.

-- 
851925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851925: libmutter-cogl.so: cannot open shared object file: No such file or directory

[Jeremy Bicha]

Control: forwarded -1 https://bugzilla.gnome.org/777519

I opened a GNOME bug for this.

Thanks,
Jeremy Bicha

Bug#851828: marked as done (oclgrind FTBFS on armhf: test failures)

[Debian Bug Tracking System]

Your message dated Fri, 20 Jan 2017 03:10:27 +
with message-id 
and subject line Bug#851828: fixed in oclgrind 16.10-2
has caused the Debian Bug report #851828,
regarding oclgrind FTBFS on armhf: test failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: oclgrind
Version: 16.10-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=oclgrind=armhf=16.10-1=1484675768=0

...
  Start 75: uninitialized/uninitialized_local_array
  Start 76: uninitialized/uninitialized_local_ptr
73/86 Test #76: uninitialized/uninitialized_local_ptr 
.***Failed0.15 sec
Running test with optimisations
Test returned non-zero value (-7)
FAILED

74/86 Test #74: uninitialized/uninitialized_address ...   
Passed0.36 sec
  Start 77: uninitialized/uninitialized_local_variable
  Start 78: uninitialized/uninitialized_packed_struct_memcpy
75/86 Test #75: uninitialized/uninitialized_local_array 
...***Failed0.27 sec
Running test with optimisations
Test returned non-zero value (-7)
FAILED

  Start 79: uninitialized/uninitialized_padded_struct_memcpy
76/86 Test #77: uninitialized/uninitialized_local_variable    
Passed0.42 sec
77/86 Test #78: uninitialized/uninitialized_packed_struct_memcpy ..   
Passed0.41 sec
  Start 80: uninitialized/uninitialized_padded_nested_struct_memcpy
  Start 81: uninitialized/uninitialized_private_array
78/86 Test #79: uninitialized/uninitialized_padded_struct_memcpy ..   
Passed0.31 sec
79/86 Test #81: uninitialized/uninitialized_private_array 
.***Failed0.17 sec
Running test with optimisations
Test returned non-zero value (-7)
FAILED

  Start 82: wait_event/wait_event_chained
  Start 83: wait_event/wait_event_divergent
80/86 Test #80: uninitialized/uninitialized_padded_nested_struct_memcpy ...   
Passed0.28 sec
  Start 84: wait_event/wait_event_duplicates
81/86 Test #83: wait_event/wait_event_divergent ...   
Passed0.31 sec
82/86 Test #82: wait_event/wait_event_chained .   
Passed0.41 sec
  Start 85: wait_event/wait_event_invalid
  Start 86: rt_map_buffer
83/86 Test #84: wait_event/wait_event_duplicates ..   
Passed0.31 sec
84/86 Test #86: rt_map_buffer .   
Passed0.31 sec
85/86 Test #85: wait_event/wait_event_invalid .   
Passed0.31 sec
86/86 Test #32: bugs/many_alloca ..   
Passed   30.88 sec

97% tests passed, 3 tests failed out of 86

Total Test time (real) =  34.03 sec

The following tests FAILED:
 75 - uninitialized/uninitialized_local_array (Failed)
 76 - uninitialized/uninitialized_local_ptr (Failed)
 81 - uninitialized/uninitialized_private_array (Failed)
Errors while running CTest
Makefile:109: recipe for target 'test' failed
make[1]: *** [test] Error 8
--- End Message ---
--- Begin Message ---
Source: oclgrind
Source-Version: 16.10-2

We believe that the bug you reported is fixed in the latest version of
oclgrind, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James Price  (supplier of updated oclgrind package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 19 Jan 2017 13:05:47 +
Source: oclgrind
Binary: liboclgrind-16.10 liboclgrind-dev oclgrind
Architecture: source
Version: 16.10-2
Distribution: unstable
Urgency: low
Maintainer: Debian OpenCL Maintainers 
Changed-By: James Price 
Description:
 liboclgrind-16.10 - core library for Oclgrind
 liboclgrind-dev - development files for Oclgrind
 oclgrind   - OpenCL device simulator
Closes: 851828
Changes:
 oclgrind 

Processed: severity of 851927 is grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # causes data loss
> severity 851927 grave
Bug #851927 [chromium] chromium: Update removed all (local) installed extensions
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
851927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: mpgrafic bug should block against openmpi bug

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 851923 by 851918
Bug #851923 [mpgrafic] mpgrafic: MPI_Comm_dup error on s390x, ppc64, sparc64 
builds of mpgrafic
851923 was not blocked by any bugs.
851923 was not blocking any bugs.
Added blocking bug(s) of 851923: 851918
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
851923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851925: libmutter-cogl.so: cannot open shared object file: No such file or directory

[Simon McVittie]

Package: gnome-shell
Version: 3.22.2-2
Severity: grave
Justification: renders package unusable

While logging in to a new GNOME-on-X11 user session from gdm, via
"Switch User":

Jan 20 00:37:48 perpetual org.gnome.Shell.desktop[25051]: /usr/bin/gnome-shell: 
error while loadi
ng shared libraries: libmutter-cogl.so: cannot open shared object file: No such 
file or directory
Jan 20 00:37:48 perpetual gnome-session[24959]: gnome-session-binary[24959]: 
WARNING: App 'org.gn
ome.Shell.desktop' exited with code 127
Jan 20 00:37:48 perpetual gnome-session-binary[24959]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 127

Some weirdness appears if I try ldd:

$ ldd /usr/bin/gnome-shell|grep mutter
libmutter-cogl-pango.so => 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-pango.so (0x7f4ad4328000)
libmutter.so.0 => /usr/lib/x86_64-linux-gnu/libmutter.so.0 
(0x7f4ad3986000)
libmutter-clutter-1.0.so => 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.0.so (0x7f4ad2d16000)
libmutter-cogl.so => not found
libmutter-cogl.so => /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl.so 
(0x7f4acbfb2000)
libmutter-cogl-path.so => 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-path.so (0x7f4ac7966000)

(Note the double entry for libmutter-cogl.so, only one of which was found.)

objdump -Tx says /usr/bin/gnome-shell and all the private mutter-related
libraries correctly have a RUNPATH, except for libmutter-cogl.so itself
(which doesn't depend on any of the others). So does the public
/usr/lib/x86_64-linux-gnu/libmutter.so.0.

However, libgnome-shell-menu.so links to libmutter-clutter-1.0.so without
a RUNPATH, and libgnome-shell.so links to libmutter-clutter-1.0.so
and libmutter-cogl.so with RUNPATH=/usr/lib/gnome-shell.
I think libgnome-shell.so might be the culprit here - the upstream
build system passes -rpath when it builds executables, but not when
it builds private shared libraries. Perhaps it should?

This might be related to recently-fixed RC bug #844796 - I'm not sure
whether exporting LD_LIBRARY_PATH during build would actually be
necessary if the -rpath was done correctly.

S

Bug#851923: mpgrafic: MPI_Comm_dup error on s390x, ppc64, sparc64 builds of mpgrafic

[Boud Roukema]

Package: mpgrafic
Version: 0.3.7.6-2
Severity: serious
Justification: fails to build from source

In this debian automated build of mpgrafic-0.3.7.6-2 (debian
downstream version) on an s390x architecture, `make check' calls
`regression-test-0.3.7.sh', which gives this fatal error:

* lines 878-884 of the html source of
https://buildd.debian.org/status/fetch.php?pkg=mpgrafic=s390x=0.3.7.6-2=1484854191=0

   878  This looks like a debian openmpi system.
   879  [zandonai:4650] *** An error occurred in MPI_Comm_dup
   880  [zandonai:4650] *** reported by process [4180410369,0]
   881  [zandonai:4650] *** on communicator MPI_COMM_WORLD
   882  [zandonai:4650] *** MPI_ERR_COMM: invalid communicator
   883  [zandonai:4650] *** MPI_ERRORS_ARE_FATAL (processes in this 
communicator will now abort,
   884  [zandonai:4650] ***and potentially your MPI job)

Version 0.3.7.6-2 is presently set up so that the build is not blocked
by make check errors - I need the logs on different architectures in order
to understand portability problems. I will soon prepare an updated
version in which this will lead to a build failure. So strictly speaking,
the "Justification:" tag above is not correct for 0.3.7.6-2, but I expect
that it will be a build failure on s390x, ppc64 and sparc64
for the next version of mpgrafic, probably 0.3.7.7-1 , unless this
bug is sorted out before that.

Since mpgrafic does not call MPI_Comm_dup directly, 
I suspect that the error comes from openmpi or fftw2 - after discussing this

on #debian-mentors with James Clarke, I've put a block against
openmpi source bug #851918 = 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851918 .

Hope this is right in terms of bug dependencies - if not feel
free to make corrections.

Cheers
Boud

-- System Information:
Debian Release: sid
Architecture: s390x

Processed: Re: Bug#851161: CVE-2016-2339

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ruby2.1
Bug #851161 [src:ruby2.3] ruby2.3: CVE-2016-2337 CVE-2016-2339
Bug reassigned from package 'src:ruby2.3' to 'ruby2.1'.
Ignoring request to alter found versions of bug #851161 to the same values 
previously set
Ignoring request to alter fixed versions of bug #851161 to the same values 
previously set
> found -1 2.1.5-2+deb8u3
Bug #851161 [ruby2.1] ruby2.3: CVE-2016-2337 CVE-2016-2339
Marked as found in versions ruby2.1/2.1.5-2+deb8u3.

-- 
851161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851161: CVE-2016-2339

[Christian Hofstaedtler]

Control: reassign -1 ruby2.1
Control: found -1 2.1.5-2+deb8u3

Hi,

* Moritz Muehlenhoff  [170120 00:05]:
> this has been assigned CVE-2016-2339: 
> http://www.talosintelligence.com/reports/TALOS-2016-0034/
> 
> Patch is here: 
> https://github.com/ruby/ruby/commit/bcc2421b4938fc1d9f5f3fb6ef2320571b27af42

If I'm reading all those right, this is actually fixed since 2.3.0;
this issue is likely open in 2.1.x. Reassigning.

For the TclTk issue, looks like this upstream patch:
https://github.com/ruby/ruby/commit/a2b8925a94a672235ca6a16e584bf09026a957ab
If this is the correct patch, 2.3.0 has this fixed, but 2.1.x needs
a patch.

Would be good if somebody could crosscheck this.

Thanks,
-- 
christian hofstaedtler 

Bug#850762: marked as done (setserial: missing dependency on lsb-base)

[Debian Bug Tracking System]

Your message dated Fri, 20 Jan 2017 00:42:38 +0100
with message-id <20170119234237.ga15...@percival.namespace.at>
and subject line Re: Bug#850762: setserial: missing dependency on lsb-base
has caused the Debian Bug report #850762,
regarding setserial: missing dependency on lsb-base
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
850762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: setserial
Version: 2.17-49.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package setserial.
  (Reading database ... 
(Reading database ... 4394 files and directories currently installed.)
  Preparing to unpack .../setserial_2.17-49.1_amd64.deb ...
  Unpacking setserial (2.17-49.1) ...
  Setting up setserial (2.17-49.1) ...
  removing the old setserial entry in the rcn.d directories
  Update complete.
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  /etc/init.d/setserial: 35: .: Can't open /lib/lsb/init-functions
  dpkg: error processing package setserial (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   setserial


cheers,

Andreas


setserial_2.17-49.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Hi,

* Andreas Beckmann  [170119 23:40]:
>   Selecting previously unselected package setserial.
>   (Reading database ... 
> (Reading database ... 4394 files and directories currently installed.)
>   Preparing to unpack .../setserial_2.17-49.1_amd64.deb ...
>   Unpacking setserial (2.17-49.1) ...
>   Setting up setserial (2.17-49.1) ...
>   removing the old setserial entry in the rcn.d directories
>   Update complete.
>   update-rc.d: warning: start and stop actions are no longer supported; 
> falling back to defaults
>   update-rc.d: warning: start and stop actions are no longer supported; 
> falling back to defaults
>   update-rc.d: warning: start and stop actions are no longer supported; 
> falling back to defaults
>   update-rc.d: warning: start and stop actions are no longer supported; 
> falling back to defaults
>   /etc/init.d/setserial: 35: .: Can't open /lib/lsb/init-functions

It is believed that this is fixed with the newer
init-system-helpers - the invoke-rc.d call should now be ignored in
chroots that miss an init system.
(And, if sysvinit is present, the missing file is present, or if
systemd is present, setserial.service is used instead.)

Best,
-- 
christian hofstaedtler --- End Message ---

Bug#835940: Bug#851871: RM: remove gcc-5 from stretch

[Emilio Pozuelo Monfort]

On 19/01/17 21:17, Adrian Bunk wrote:
> On Thu, Jan 19, 2017 at 03:07:03PM +0100, Matthias Klose wrote:
>> Package: release.debian.org
>> Tags: stretch
>>
>> Please remove gcc-5, gcc-5-cross and gcc-5-cross-ports from testing.  Now 
>> that
>> the linux source is built using gcc-6, the list of packages also needing 
>> removal
>> are acoording to [1]:
>>
>>  - nvida-cuda-toolkit
>>  - starpu-contrib
>> ...
> 
> Their fix might actually be blocked by outdated information in #835940.
> 
> Quoting the relevant part from #835940:
> 
> On Mon, Nov 28, 2016 at 11:23:27AM +0100, Matthias Klose wrote:
>> On 28.11.2016 02:08, lumin wrote:
>>> Hello guys,
>>>
>>> I successfully compiled caffe with CUDA_8.0.44-2 and
>>> clang-3.8 (the current default clang). Maybe we can
>>> replace GCC-5 with Clang-3.8 to solve this problem.
>>>
>>> That means Stretch still has chance to ship CUDA8,
>>> and users are expected to compile with Clang/LLVM
>>> instead of GCC-6, as long as the CUDA rDepends
>>> compile with clang.
>>>
>>> I only tested caffe-contrib.
>>
>> My guess is that clang-3.8 will be gone for the release as well ...
> 
> 
> What is the final decision regarding LLVM versions in stretch?

We are shipping with 3.7 (for ghc), 3.8 and 3.9.

Emilio

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 851518 moreinfo
Bug #851518 [cinnamon] cinnamon won't start
Added tag(s) moreinfo.
> tags 851518 unreproducible
Bug #851518 [cinnamon] cinnamon won't start
Added tag(s) unreproducible.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
851518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#845905: marked as done (ruby-dataobjects-mysql: switch to build depend on the metapackage default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 23:06:36 +
with message-id 
and subject line Bug#845905: fixed in ruby-dataobjects-mysql 0.10.16-2
has caused the Debian Bug report #845905,
regarding ruby-dataobjects-mysql: switch to build depend on the metapackage 
default-libmysqlclient-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
845905: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-dataobjects-mysql
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Source: ruby-dataobjects-mysql
Source-Version: 0.10.16-2

We believe that the bug you reported is fixed in the latest version of
ruby-dataobjects-mysql, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 845...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Hofstaedtler  (supplier of updated 
ruby-dataobjects-mysql package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 19 Jan 2017 22:44:26 +
Source: ruby-dataobjects-mysql
Binary: ruby-dataobjects-mysql
Architecture: source
Version: 0.10.16-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Christian Hofstaedtler 
Description:
 ruby-dataobjects-mysql - MySQL adapter for ruby-dataobjects
Closes: 830082 841583 845905
Changes:
 ruby-dataobjects-mysql (0.10.16-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Cédric Boutillier ]
   * Remove version in the gem2deb build-dependency
   * Use https:// in Vcs-* fields
 .
   [ Christian Hofstaedtler ]
   * Switch to default-*mysql (Closes: #845905, #841583)
   * Add Testsuite: autopkgtest-pkg-ruby (Closes: #830082)
   * Bump Standards-Version to 3.9.8 and dh compat level to 10
Checksums-Sha1:
 95491bd9a9acbd1a8f6d40b0b036ea3b8450d88b 2354 
ruby-dataobjects-mysql_0.10.16-2.dsc
 07c51609489d6b58d15d829e1345735d7dafcec3 4956 
ruby-dataobjects-mysql_0.10.16-2.debian.tar.xz
Checksums-Sha256:
 1de639eaf4450011fd67605469dc4b804d349288e09f4bc46385c1949df74cf7 2354 
ruby-dataobjects-mysql_0.10.16-2.dsc
 380304deb29f4eb1bd5f48bbd297b3e5ed270833bd9947016e4dcfbc8a9d0950 4956 
ruby-dataobjects-mysql_0.10.16-2.debian.tar.xz
Files:
 70ec1f97c4dde110317f235a5b54f606 2354 ruby optional 
ruby-dataobjects-mysql_0.10.16-2.dsc
 9b97db5f9adce51e04ea58d035d9c5dc 4956 ruby optional 
ruby-dataobjects-mysql_0.10.16-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAliBQdYACgkQXBPW25MF
LgOT/g//e+DeqWSLyfaFVl86VW0NFRnRPIUfz8yB3Pq2ql1Bqr1Rf8hDQpTJdKdy
dvFd6x7v0nIrrjGpz7S2gsOaSeRt1k7+tRhiMacqZ8PyEFtzi7HMqImlDtp41gGX
nBYwowUenHwW02v5qE1TYd4APm3NGOQiJ28e93LU+ZDGykZx1YozkN7K1WsOiHWH
ECo05c2HgG2VxnEoLHft7IXBdSyvyrcXJGtEZW87BlXOeu7DBY4Z6PBDJS8x3Bot
izZn/PDvLFBmLqzKzIaIM/racxTW5ewJtmik0BCAzsZioyIhbpb3k8cn24a8a9pE
eoxZmiIAZz7Dw+eGnLzgaEKNpqE2Yda1YQEUR6ESNsCJ6tSXOhzotNV4ateNtD8q
CbpDAbDwSoD8QsGoL+GMP//h/Xi/oPn5iu8wraTuUmL7BCmJRQvXm5FFxxzIkNMV
WN1mvl0k4j/RLTqzoM7oN7Zf6bS6j7QiDdIPZlCNSe7J76ny1a0Y6ChAUxfwfq9z
+7v6VyMQmf2zu+IK8Al67oCXm5mBjBwT8wUxFCRn7Dj+ZUPD9r/HQUHidfHhxpNR
3z+P436KhOyYTi2GswLcmHdzRhjH/kHVsN3HD6Q2sH0JIH53894vYAT2cQ7ypcl7
lnIFEdARhiQDLDJYGGvlFlsMs9Trr59uOeGxLoCsfcl16AqXh2I=
=Crn+
-END PGP SIGNATURE End Message ---

Bug#841583: marked as done (ruby-dataobjects-mysql: FTBFS: mysql_install_db: [ERROR] unknown option '--force')

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 23:06:36 +
with message-id 
and subject line Bug#841583: fixed in ruby-dataobjects-mysql 0.10.16-2
has caused the Debian Bug report #841583,
regarding ruby-dataobjects-mysql: FTBFS: mysql_install_db: [ERROR] unknown 
option '--force'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-dataobjects-mysql
Version: 0.10.16-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules binary
> dh binary --buildsystem=ruby --with ruby
> dh: Compatibility levels before 9 are deprecated (level 7 in use)
>dh_testroot -O--buildsystem=ruby
>dh_prep -O--buildsystem=ruby
>debian/rules override_dh_auto_install
> make[1]: Entering directory '/<>'
> chmod +x debian/start_mysqld_and_auto_install.sh
> debian/start_mysqld_and_auto_install.sh
> mysql_install_db: [ERROR] unknown option '--force'
> 2016-10-21 01:17:03 [ERROR]   Unrecognized options
> debian/rules:19: recipe for target 'override_dh_auto_install' failed
> make[1]: *** [override_dh_auto_install] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   
http://aws-logs.debian.net/2016/10/21/ruby-dataobjects-mysql_0.10.16-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ruby-dataobjects-mysql
Source-Version: 0.10.16-2

We believe that the bug you reported is fixed in the latest version of
ruby-dataobjects-mysql, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Hofstaedtler  (supplier of updated 
ruby-dataobjects-mysql package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 19 Jan 2017 22:44:26 +
Source: ruby-dataobjects-mysql
Binary: ruby-dataobjects-mysql
Architecture: source
Version: 0.10.16-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Christian Hofstaedtler 
Description:
 ruby-dataobjects-mysql - MySQL adapter for ruby-dataobjects
Closes: 830082 841583 845905
Changes:
 ruby-dataobjects-mysql (0.10.16-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Cédric Boutillier ]
   * Remove version in the gem2deb build-dependency
   * Use https:// in Vcs-* fields
 .
   [ Christian Hofstaedtler ]
   * Switch to default-*mysql (Closes: #845905, #841583)
   * Add Testsuite: autopkgtest-pkg-ruby (Closes: #830082)
   * Bump Standards-Version to 3.9.8 and dh compat level to 10
Checksums-Sha1:
 95491bd9a9acbd1a8f6d40b0b036ea3b8450d88b 2354 
ruby-dataobjects-mysql_0.10.16-2.dsc
 07c51609489d6b58d15d829e1345735d7dafcec3 4956 
ruby-dataobjects-mysql_0.10.16-2.debian.tar.xz
Checksums-Sha256:
 1de639eaf4450011fd67605469dc4b804d349288e09f4bc46385c1949df74cf7 2354 
ruby-dataobjects-mysql_0.10.16-2.dsc
 380304deb29f4eb1bd5f48bbd297b3e5ed270833bd9947016e4dcfbc8a9d0950 4956 

Bug#851518: cinnamon won't start

[William L. DeRieux IV]

tags 851518 = moreinfo unreproducible

--

On Thu, 19 Jan 2017 16:14:08 -0500 "William L. DeRieux IV" wrote:
> On Tue, 17 Jan 2017 22:43:42 +0100 Carsten Kosthorstwrote:
>
> > Hi,
> >
> > I updated today and cinnamon is working again.
> >
> > Thanks,
> >
> > Carsten
> >
> >
> >
>
> Your version of cinnamon was 3.2.7-1 in the initial report.
>
> The latest version in unstable/sid is 3.2.7-1.
>
> What version was cinnamon updated to the second time?
>
> You can do this by using: *apt-cache policy cinnamon*
>
> The latest version in stretch/sid is 3.2.7-1, so I'm thinking this issue
> was temporary ?
>
>

I just updated to 3.2.7-1 and I cannot reproduce this issue.

So this does seem to be a one-off issue.

Bug#849260: marked as done (gav-themes: FTBFS in testing (no binary artifacts))

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 22:00:10 +
with message-id 
and subject line Bug#849260: fixed in gav-themes 0.7.3-2.2
has caused the Debian Bug report #849260,
regarding gav-themes: FTBFS in testing (no binary artifacts)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
849260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gav-themes
Version: 0.7.3-2.1
Severity: serious
Tags: patch

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 fakeroot debian/rules binary-indep
dh_testdir
dh_testroot
dh_clean -k
dh_clean: dh_clean -k is deprecated; use dh_prep instead
dh_installdirs
# Add here commands to install the package into debian/gav-themes.
#/usr/bin/make install DESTDIR=/<>/debian/gav-themes
dh_install
 dpkg-genbuildinfo --build=all
dpkg-genbuildinfo: error: binary build with no binary artifacts found; 
.buildinfo is meaningless
dpkg-buildpackage: error: dpkg-genbuildinfo --build=all gave error exit status 2


This usually happens when the binary-arch and binary-indep targets are swapped.

The patch below (untested) might help.

Please consider uploading in source-only form so that these kind of bugs
are discovered earlier.

Thanks.

--- a/debian/rules
+++ b/debian/rules
@@ -58,12 +58,12 @@ install: build
#$(MAKE) install DESTDIR=$(CURDIR)/debian/gav-themes
dh_install
 
-# Build architecture-independent files here.
-binary-indep: build install
-# We have nothing to do by default.
-
 # Build architecture-dependent files here.
 binary-arch: build install
+# We have nothing to do by default.
+
+# Build architecture-independent files here.
+binary-indep: build install
dh_testdir
dh_testroot
 #  dh_installdebconf   
--- End Message ---
--- Begin Message ---
Source: gav-themes
Source-Version: 0.7.3-2.2

We believe that the bug you reported is fixed in the latest version of
gav-themes, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 849...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated 
gav-themes package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Dec 2016 13:50:40 +0100
Source: gav-themes
Binary: gav-themes
Architecture: source all
Version: 0.7.3-2.2
Distribution: unstable
Urgency: medium
Maintainer: Ari Pollak 
Changed-By: Christoph Biedl 
Description:
 gav-themes - Extra themes for GPL Arcade Volleyball
Closes: 849260
Changes:
 gav-themes (0.7.3-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix another FTBFS, patch by Santiago Vila. Closes: #849260
Checksums-Sha1:
 73b63abe7b0cd86431a8a68657ef9f2b77960503 1661 gav-themes_0.7.3-2.2.dsc
 dae75da4e375f8364654448ad447a9b89c64fabb 1659 gav-themes_0.7.3-2.2.diff.gz
 d0250e7728339d733e537354a7b7d886597ea065 551858 gav-themes_0.7.3-2.2_all.deb
 2a2696dc9e496f3db34a3b63ec1aba2a10b54294 5111 
gav-themes_0.7.3-2.2_amd64.buildinfo
Checksums-Sha256:
 2c4915ce7834190c9db395ebbb52603b6012ee405cf2a325a8b30bc5206fa336 1661 
gav-themes_0.7.3-2.2.dsc
 79f2a64b7f874080a4a635e0ee71953b5fe68b100a4f9e9ede12bb70854ebb8c 1659 
gav-themes_0.7.3-2.2.diff.gz
 6c6284da8b5d8f9156c6daa5152671a54d0ae141ccef9fa8e477a12b50e8ba74 551858 
gav-themes_0.7.3-2.2_all.deb
 f1d866a8028b819771bb0fad67d85fa19dd26aad28091948099a95449def8d26 5111 
gav-themes_0.7.3-2.2_amd64.buildinfo
Files:
 8135bac48c79c56996ae4b37934e6f4a 1661 games extra gav-themes_0.7.3-2.2.dsc
 8c4367141e53d0ed90073923aa3b0d51 1659 games extra gav-themes_0.7.3-2.2.diff.gz
 5e1ea1d7b479d9e5da276f333f52918b 551858 games extra 
gav-themes_0.7.3-2.2_all.deb
 ca5fd686c6d69d158ef744281c5e9961 5111 games extra 
gav-themes_0.7.3-2.2_amd64.buildinfo

-BEGIN PGP 

Bug#849261: marked as done (webcamd: FTBFS in testing (no binary artifacts))

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 22:00:10 +
with message-id 
and subject line Bug#849261: fixed in webcamd 0.7.6-5.2
has caused the Debian Bug report #849261,
regarding webcamd: FTBFS in testing (no binary artifacts)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
849261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:webcamd
Version: 0.7.6-5.1
Severity: serious
Tags: patch

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 fakeroot debian/rules binary-indep
dh_testdir
dh_testroot
dh_clean -k
dh_clean: dh_clean -k is deprecated; use dh_prep instead
dh_installdirs
# Add here commands to install the package into debian/webcamd.
/usr/bin/make install DESTDIR=/<>/debian/webcamd
make[1]: Entering directory '/<>'
install -d -m 755 /<>/debian/webcamd/usr/bin
install -m 755 webcamd /<>/debian/webcamd/usr/bin
install -m 755 webcamd-setup /<>/debian/webcamd/usr/bin
make[1]: Leaving directory '/<>'
 dpkg-genbuildinfo --build=all
dpkg-genbuildinfo: error: binary build with no binary artifacts found; 
.buildinfo is meaningless
dpkg-buildpackage: error: dpkg-genbuildinfo --build=all gave error exit status 2


This usually happens when the binary-arch and binary-indep targets are swapped.

The patch below (untested) might help.

Please consider uploading in source-only form so that these kind of bugs
are discovered earlier.

Thanks.

--- a/debian/rules
+++ b/debian/rules
@@ -45,12 +45,12 @@ install: build
$(MAKE) install DESTDIR=$(CURDIR)/debian/webcamd
 
 
-# Build architecture-independent files here.
-binary-indep: build install
-# We have nothing to do by default.
-
 # Build architecture-dependent files here.
 binary-arch: build install
+# We have nothing to do by default.
+
+# Build architecture-independent files here.
+binary-indep: build install
dh_testdir
dh_testroot
dh_installdocs
--- End Message ---
--- Begin Message ---
Source: webcamd
Source-Version: 0.7.6-5.2

We believe that the bug you reported is fixed in the latest version of
webcamd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 849...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated webcamd 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Dec 2016 13:55:37 +0100
Source: webcamd
Binary: webcamd
Architecture: source all
Version: 0.7.6-5.2
Distribution: unstable
Urgency: medium
Maintainer: Julien Danjou 
Changed-By: Christoph Biedl 
Description:
 webcamd- Capture images from video devices
Closes: 849261
Changes:
 webcamd (0.7.6-5.2) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Fix another FTBFS, patch by Santiago Vila. Closes: #849261
Checksums-Sha1:
 34f94d57a84f43fc9727ac37597827cd919e16da 1392 webcamd_0.7.6-5.2.dsc
 3f770adedba5b68b4b33c6bc80359318a2aa6df9 10839 webcamd_0.7.6-5.2.tar.gz
 75e26bcce0b966b044388f5aae9f09a0e4bea8c3 10940 webcamd_0.7.6-5.2_all.deb
 dcc18b6dc8e25c4c14c41f1f95c322935fd44611 5084 webcamd_0.7.6-5.2_amd64.buildinfo
Checksums-Sha256:
 11b3b0d7a0e443cbca5e3271370baa94267cd34a00e877c9c504645636d4a455 1392 
webcamd_0.7.6-5.2.dsc
 81ff325312d665772b263c3f2814b0d218de94706adbaa73b93ebb7654dd3981 10839 
webcamd_0.7.6-5.2.tar.gz
 3b779b8106581834250a37c27dc2ea9fdd7b18bd790d6f16a4a9e8e499a18880 10940 
webcamd_0.7.6-5.2_all.deb
 1d6eb2edeefcd9e33b61ede40d400caf174bf754430fc02b2ddf935eb1edb19d 5084 
webcamd_0.7.6-5.2_amd64.buildinfo
Files:
 0a27b2217bed2e652ce1527c75ad77ed 1392 net optional webcamd_0.7.6-5.2.dsc
 78d0185b67e72119b1f231ef2c099ea2 10839 net optional webcamd_0.7.6-5.2.tar.gz
 d8e3b2c8831c885f27d75478af1531be 10940 net optional webcamd_0.7.6-5.2_all.deb
 

Bug#850998: [Pkg-leofs-devel] Bug#850998: erlang-ranch: FTBFS: a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl

[Nobuhiro Iwamatsu]

Hi!

Thanks for your work.
I just pushed my latest commits.

Best regards,
  Nobuhiro

2017-01-19 7:52 GMT+09:00 Bálint Réczey :
> Hi Nobuhiro,
>
> I have uploaded the fix but the packaging repo does not contain your
> latest upload.
> In case you have it offline please upload it or we can import the
> history from the .dsc
>
> Cheers,
> Balint
>
> 2017-01-11 20:07 GMT+01:00 Lucas Nussbaum :
>> Source: erlang-ranch
>> Version: 1.2.1-2
>> Severity: serious
>> Tags: stretch sid
>> User: debian...@lists.debian.org
>> Usertags: qa-ftbfs-20170111 qa-ftbfs
>> Justification: FTBFS on amd64
>>
>> Hi,
>>
>> During a rebuild of all packages in sid, your package failed to build on
>> amd64.
>>
>> Relevant part (hopefully):
>>> make[2]: Entering directory '/<>'
>>>  GENdistclean-asciidoc
>>> a2x -v -f pdf doc/src/guide/book.asciidoc && mv doc/src/guide/book.pdf 
>>> doc/guide.pdf
>>> a2x: ERROR: missing configuration file: 
>>> /etc/asciidoc/dblatex/asciidoc-dblatex.xsl
>>> a2x: args: ['--dblatex-opts', '-P latex.output.revhistory=0 -P 
>>> doc.publisher.show=0 -P index.numbered=0', '-d', 'book', '--attribute', 
>>> 'tabsize=4', '-v', '-f', 'pdf', 'doc/src/guide/book.asciidoc']
>>> a2x: resource files: []
>>> a2x: resource directories: ['/etc/asciidoc/images', 
>>> '/etc/asciidoc/stylesheets']
>>> a2x: executing: "/usr/bin/asciidoc" --backend docbook -a "a2x-format=pdf"  
>>> --doctype book --attribute "tabsize=4" --verbose  --out-file 
>>> "/<>/doc/src/guide/book.xml" 
>>> "/<>/doc/src/guide/book.asciidoc"
>>>
>>> asciidoc: reading: /etc/asciidoc/asciidoc.conf
>>> asciidoc: reading: /<>/doc/src/guide/book.asciidoc
>>> asciidoc: reading: /etc/asciidoc/docbook45.conf
>>> asciidoc: reading: /etc/asciidoc/filters/source/source-highlight-filter.conf
>>> asciidoc: reading: /etc/asciidoc/filters/graphviz/graphviz-filter.conf
>>> asciidoc: reading: /etc/asciidoc/filters/music/music-filter.conf
>>> asciidoc: reading: /etc/asciidoc/filters/latex/latex-filter.conf
>>> asciidoc: reading: /etc/asciidoc/filters/code/code-filter.conf
>>> asciidoc: reading: /etc/asciidoc/lang-en.conf
>>> asciidoc: writing: /<>/doc/src/guide/book.xml
>>> asciidoc: include: /<>/doc/src/guide/introduction.asciidoc
>>> asciidoc: book.asciidoc: line 6: reading: 
>>> /<>/doc/src/guide/introduction.asciidoc
>>> asciidoc: include: /<>/doc/src/guide/listeners.asciidoc
>>> asciidoc: book.asciidoc: line 8: reading: 
>>> /<>/doc/src/guide/listeners.asciidoc
>>> asciidoc: include: /<>/doc/src/guide/transports.asciidoc
>>> asciidoc: book.asciidoc: line 10: reading: 
>>> /<>/doc/src/guide/transports.asciidoc
>>> asciidoc: include: /<>/doc/src/guide/protocols.asciidoc
>>> asciidoc: book.asciidoc: line 12: reading: 
>>> /<>/doc/src/guide/protocols.asciidoc
>>> asciidoc: include: /<>/doc/src/guide/embedded.asciidoc
>>> asciidoc: book.asciidoc: line 14: reading: 
>>> /<>/doc/src/guide/embedded.asciidoc
>>> asciidoc: include: /<>/doc/src/guide/parsers.asciidoc
>>> asciidoc: book.asciidoc: line 16: reading: 
>>> /<>/doc/src/guide/parsers.asciidoc
>>> asciidoc: include: /<>/doc/src/guide/ssl_auth.asciidoc
>>> asciidoc: book.asciidoc: line 18: reading: 
>>> /<>/doc/src/guide/ssl_auth.asciidoc
>>> asciidoc: include: /<>/doc/src/guide/internals.asciidoc
>>> asciidoc: book.asciidoc: line 20: reading: 
>>> /<>/doc/src/guide/internals.asciidoc
>>>
>>> a2x: executing: "xmllint" --nonet --noout --valid 
>>> "/<>/doc/src/guide/book.xml"
>>>
>>>
>>> erlang.mk:5062: recipe for target 'asciidoc-guide' failed
>>> make[2]: *** [asciidoc-guide] Error 1
>>
>> The full build log is available from:
>>http://aws-logs.debian.net/2017/01/11/erlang-ranch_1.2.1-2_unstable.log
>>
>> A list of current common problems and possible solutions is available at
>> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>>
>> About the archive rebuild: The rebuild was done on EC2 VM instances from
>> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
>> failed build was retried once to eliminate random failures.
>>
>> ___
>> Pkg-leofs-devel mailing list
>> pkg-leofs-de...@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-leofs-devel



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#813067: marked as done (jspwiki: FTBFS: WikiJSPFilter.java:261: error: MyServletOutputStream is not abstract and does not override abstract method setWriteListener(WriteListener) in ServletOutputS

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:45:02 +
with message-id 
and subject line Bug#851853: Removed package(s) from unstable
has caused the Debian Bug report #813067,
regarding jspwiki: FTBFS: WikiJSPFilter.java:261: error: MyServletOutputStream 
is not abstract and does not override abstract method 
setWriteListener(WriteListener) in ServletOutputStream
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
813067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jspwiki
Version: 2.8.0-6
Severity: serious
Justification: fails to build from source

jspwiki FTBFS in current sid:

[...]
 debian/rules build
dh build
   dh_testdir
   dh_update_autotools_config
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/jspwiki-2.8.0'
dh_auto_build
ant
Buildfile: /build/jspwiki-2.8.0/build.xml

mkpropertyfile:
 [copy] Copying 1 file to /build/jspwiki-2.8.0/etc
 [copy] Copying 1 file to /build/jspwiki-2.8.0/tests/etc
 [copy] Copying 1 file to /build/jspwiki-2.8.0/tests/etc
 [copy] Copying 1 file to /build/jspwiki-2.8.0/tests/etc

init:
[mkdir] Created dir: /build/jspwiki-2.8.0/build
[mkdir] Created dir: /build/jspwiki-2.8.0/tests/build
[mkdir] Created dir: /build/jspwiki-2.8.0/tests/reports
[mkdir] Created dir: /tmp/testrepository

compile:
[javac] /build/jspwiki-2.8.0/build.xml:236: warning: 'includeantruntime' 
was not set, defaulting to build.sysclasspath=last; set to false for repeatable 
builds
[javac] Compiling 365 source files to /build/jspwiki-2.8.0/build
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.5
[javac] 
/build/jspwiki-2.8.0/src/com/ecyrd/jspwiki/ui/WikiJSPFilter.java:261: error: 
MyServletOutputStream is not abstract and does not override abstract method 
setWriteListener(WriteListener) in ServletOutputStream
[javac] static class MyServletOutputStream extends 
ServletOutputStream
[javac]^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 error
[javac] 1 warning

BUILD FAILED
/build/jspwiki-2.8.0/build.xml:236: Compile failed; see the compiler error 
output for details.

Total time: 7 seconds
dh_auto_build: ant returned exit code 1
debian/rules:9: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/jspwiki-2.8.0'
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2


Andreas
--- End Message ---
--- Begin Message ---
Version: 2.8.0-7+rm

Dear submitter,

as the package jspwiki has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/851853

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#767076: marked as done (gnuvd not able to search for words)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:46:25 +
with message-id 
and subject line Bug#851896: Removed package(s) from unstable
has caused the Debian Bug report #767076,
regarding gnuvd not able to search for words
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
767076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnuvd
Version: 1.0.12-1
Severity: normal

Dear Maintainer,
since a couple of weeks, gnuvd is not able to search for words ... :(

   * What led up to the situation?

Sorry, no idea ... :(

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

In the last couple of weeks, I tried to search for different Dutch words like
"geneuzel", but even more simple words like "blijven" with


gnuvd geneuzel


or


gnuvd blijven

..

   * What was the outcome of this action?
I only get the "error: Dictionary is currently unavailable" message so far ...
:(

   * What outcome did you expect instead?
An exact definition of this word in Dutch

Sorry for the inconvenience and have a nice day
Thomas.



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

Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnuvd depends on:
ii  libc6  2.19-11

gnuvd recommends no packages.

gnuvd suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.0.12-1+rm

Dear submitter,

as the package gnuvd has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/851896

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#692455: marked as done (jspwiki: modifies conffiles (policy 10.7.3): /etc/jspwiki/jspwiki.properties)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:45:02 +
with message-id 
and subject line Bug#851853: Removed package(s) from unstable
has caused the Debian Bug report #692455,
regarding jspwiki: modifies conffiles (policy 10.7.3): 
/etc/jspwiki/jspwiki.properties
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
692455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jspwiki
Version: 2.8.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files

10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."

Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).

Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"

If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also http://wiki.debian.org/DpkgConffileHandling

In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

 /etc/jspwiki/jspwiki.properties
  

cheers,

Andreas


jspwiki_2.8.0-5.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Version: 2.8.0-7+rm

Dear submitter,

as the package jspwiki has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/851853

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#788726: marked as done ([src:jspwiki] Some sources are not included in your package)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:45:02 +
with message-id 
and subject line Bug#851853: Removed package(s) from unstable
has caused the Debian Bug report #788726,
regarding [src:jspwiki] Some sources are not included in your package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
788726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jspwiki 
Version:  2.8.0-6
user: lintian-ma...@debian.org
usertags: source-is-missing
severity: serious
X-Debbugs-CC: ftpmas...@debian.org

Hi,

Your package includes some files that seem to lack sources
in prefered forms of modification:
src/webdocs/scripts/posteditor.js
src/webdocs/scripts/mootools.js

According to Debian Free Software Guidelines [1] (DFSG) #2:
 "The program must include source code, and must allow distribution 
  in source code as well as compiled form."

In some cases this could also constitute a license violation for some
copyleft licenses such as the GNU GPL. (While sometimes the licence
allows not to ship the source, the DFSG always mandates source code.)

In order to solve this problem, you could:
1.  add the source files to "debian/missing-sources" directory.
2. repack the origin tarball and add the missing source files to it.

Both way satisfy the requirement to ship all source code. The second option
might be preferable due to the following reasons [2]:
 - Upstream can do it too and you could even supply a patch to them, thus
   full filling our social contract [3], see particularly §2.
 - If source and non-source are in different locations, ftpmasters may
   miss the source and (needlessly) reject the package.
 - The source isn't duplicated in every .diff.gz/.debian.tar.* (though
   this only really matters for larger sources).

You could also ask debian...@lists.debian.org or #debian-qa for more
guidance.

[1] https://www.debian.org/social_contract.en.html#guidelines
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8
[3] https://www.debian.org/social_contract

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Version: 2.8.0-7+rm

Dear submitter,

as the package jspwiki has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/851853

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: forwarded 851014

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 851014 
> https://github.com/python-xmp-toolkit/python-xmp-toolkit/issues/67
Bug #851014 [src:python-xmp-toolkit] python-xmp-toolkit: FTBFS: dh_auto_test: 
pybuild --test -i python{version} -p 2.7 returned exit code 13
Set Bug forwarded-to-address to 
'https://github.com/python-xmp-toolkit/python-xmp-toolkit/issues/67'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
851014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#850987: marked as done (python-keystonemiddleware: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:35:53 +
with message-id 
and subject line Bug#851649: fixed in python-webob 1:1.6.2-2
has caused the Debian Bug report #851649,
regarding python-keystonemiddleware: FTBFS: Test failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-keystonemiddleware
Version: 4.9.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>   File "/<>/keystonemiddleware/auth_token/__init__.py", line 
> 320, in __call__
> response = self.process_request(req)
>   File "/<>/keystonemiddleware/auth_token/__init__.py", line 
> 582, in process_request
> content_type='application/json')
>   File "/usr/lib/python3/dist-packages/webob/exc.py", line 268, in __init__
> **kw)
>   File "/usr/lib/python3/dist-packages/webob/response.py", line 310, in 
> __init__
> "You cannot set the body to a text value without a "
> TypeError: You cannot set the body to a text value without a charset
> 
> 
> --
> Ran 347 tests in 13.902s
> 
> FAILED (failures=74, skipped=3)
> debian/rules:26: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2017/01/11/python-keystonemiddleware_4.9.0-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-webob
Source-Version: 1:1.6.2-2

We believe that the bug you reported is fixed in the latest version of
python-webob, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-webob package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Jan 2017 16:38:16 +0100
Source: python-webob
Binary: python-webob python3-webob python-webob-doc
Architecture: source
Version: 1:1.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python-webob - Python module providing WSGI request and response objects 
(Python
 python-webob-doc - Python module providing WSGI request and response objects 
(docume
 python3-webob - Python module providing WSGI request and response objects 
(Python
Closes: 849591 851649
Changes:
 python-webob (1:1.6.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Rollback to 1.6.2 upstream release (Closes: #849591, #851649)
 - pytest replaced with nose
Checksums-Sha1:
 3248b25e682af086484e391337485514726d6581 2411 python-webob_1.6.2-2.dsc
 4e59f44f5e295f0302281008afe95841c641de22 205228 python-webob_1.6.2.orig.tar.gz
 6cffc95aee902f5c0a4b534f6bbe317ffd9c99fb 5384 
python-webob_1.6.2-2.debian.tar.xz
Checksums-Sha256:
 fa3e68055794f36334a6108fb930704cf5f97b87455be6b8abe9b46cfbb867c3 2411 
python-webob_1.6.2-2.dsc
 e096c20ec672412f7d463fd5ed23f71b9176945c66b8adb8b781b8cda174de84 205228 
python-webob_1.6.2.orig.tar.gz
 856f531182f7a60cd3abb378852e9fc1de1d2477e929b85fee0e6d93d72a0672 5384 
python-webob_1.6.2-2.debian.tar.xz
Files:
 32ca4ec065c1b27f504014e363d94f44 2411 python optional python-webob_1.6.2-2.dsc
 cc88bf68d6bf879c2d2145c86b6f5010 205228 python optional 
python-webob_1.6.2.orig.tar.gz
 82414afc24806b5858d32274611b3cc6 5384 python optional 
python-webob_1.6.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#849591: marked as done (python-webob: FTBFS (The 'WebOb' distribution was not found))

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:35:53 +
with message-id 
and subject line Bug#849591: fixed in python-webob 1:1.6.2-2
has caused the Debian Bug report #849591,
regarding python-webob: FTBFS (The 'WebOb' distribution was not found)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
849591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-webob
Version: 1.7.0-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

copying webob/multidict.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/webob
copying webob/cookies.py -> /<>/.pybuild/pythonX.Y_3.5/build/webob
copying webob/etag.py -> /<>/.pybuild/pythonX.Y_3.5/build/webob
copying webob/util.py -> /<>/.pybuild/pythonX.Y_3.5/build/webob
copying webob/byterange.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/webob
copying webob/cachecontrol.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/webob
copying webob/response.py -> /<>/.pybuild/pythonX.Y_3.5/build/webob
copying webob/exc.py -> /<>/.pybuild/pythonX.Y_3.5/build/webob
copying webob/client.py -> /<>/.pybuild/pythonX.Y_3.5/build/webob
copying webob/request.py -> /<>/.pybuild/pythonX.Y_3.5/build/webob
copying webob/dec.py -> /<>/.pybuild/pythonX.Y_3.5/build/webob
copying webob/acceptparse.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/webob
copying webob/static.py -> /<>/.pybuild/pythonX.Y_3.5/build/webob
copying webob/__init__.py -> /<>/.pybuild/pythonX.Y_3.5/build/webob
copying webob/compat.py -> /<>/.pybuild/pythonX.Y_3.5/build/webob
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
# enable network, tests.test_in_wsgiref.test_request_reading needs it
http_proxy='' dh_auto_test
I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
python2.7 -m pytest tests
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/_pytest/config.py", line 362, in 
_importconftest
mod = conftestpath.pyimport()
  File "/usr/lib/python2.7/dist-packages/py/_path/local.py", line 662, in 
pyimport
__import__(modname)
  File "/usr/lib/python2.7/dist-packages/_pytest/assertion/rewrite.py", line 
216, in load_module
py.builtin.exec_(co, mod.__dict__)
  File "/usr/lib/python2.7/dist-packages/py/_builtin.py", line 221, in exec_
exec2(obj, globals, locals)
  File "", line 7, in exec2
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/conftest.py", line 
4, in 
pkg_resources.require('WebOb')
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 963, 
in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 849, 
in resolve
raise DistributionNotFound(req, requirers)
DistributionNotFound: The 'WebOb' distribution was not found and is required by 
the application
ERROR: could not load 
/<>/.pybuild/pythonX.Y_2.7/build/tests/conftest.py

E: pybuild pybuild:276: test: plugin distutils failed with: exit code=4: cd 
/<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
debian/rules:11: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Please consider uploading in source-only form (dpkg-buildpackage -S), so that
we get official build logs here:

https://buildd.debian.org/status/package.php?p=python-webob

Thanks.
--- End Message ---
--- Begin Message ---
Source: python-webob
Source-Version: 1:1.6.2-2

We believe that the bug you reported is fixed 

Bug#851045: marked as done (keystone: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:35:53 +
with message-id 
and subject line Bug#851649: fixed in python-webob 1:1.6.2-2
has caused the Debian Bug report #851649,
regarding keystone: FTBFS: Test failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: keystone
Version: 2:10.0.0-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> 
> Traceback (most recent call last):
>   File "keystone/tests/unit/test_wsgi.py", line 179, in 
> test_render_response_no_body
> self.assertEqual('0', resp.headers.get('Content-Length'))
>   File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 350, in 
> assertEqual
> self.assertThat(observed, matcher, message)
>   File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 435, in 
> assertThat
> raise mismatch_error
> testtools.matchers._impl.MismatchError: '0' != None
> 
> 
> --
> Ran 6957 tests in 70.646s
> 
> FAILED (failures=5, skipped=1724)
> debian/rules:20: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/01/11/keystone_10.0.0-5_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-webob
Source-Version: 1:1.6.2-2

We believe that the bug you reported is fixed in the latest version of
python-webob, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-webob package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Jan 2017 16:38:16 +0100
Source: python-webob
Binary: python-webob python3-webob python-webob-doc
Architecture: source
Version: 1:1.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python-webob - Python module providing WSGI request and response objects 
(Python
 python-webob-doc - Python module providing WSGI request and response objects 
(docume
 python3-webob - Python module providing WSGI request and response objects 
(Python
Closes: 849591 851649
Changes:
 python-webob (1:1.6.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Rollback to 1.6.2 upstream release (Closes: #849591, #851649)
 - pytest replaced with nose
Checksums-Sha1:
 3248b25e682af086484e391337485514726d6581 2411 python-webob_1.6.2-2.dsc
 4e59f44f5e295f0302281008afe95841c641de22 205228 python-webob_1.6.2.orig.tar.gz
 6cffc95aee902f5c0a4b534f6bbe317ffd9c99fb 5384 
python-webob_1.6.2-2.debian.tar.xz
Checksums-Sha256:
 fa3e68055794f36334a6108fb930704cf5f97b87455be6b8abe9b46cfbb867c3 2411 
python-webob_1.6.2-2.dsc
 e096c20ec672412f7d463fd5ed23f71b9176945c66b8adb8b781b8cda174de84 205228 
python-webob_1.6.2.orig.tar.gz
 856f531182f7a60cd3abb378852e9fc1de1d2477e929b85fee0e6d93d72a0672 5384 
python-webob_1.6.2-2.debian.tar.xz
Files:
 32ca4ec065c1b27f504014e363d94f44 2411 python optional python-webob_1.6.2-2.dsc
 cc88bf68d6bf879c2d2145c86b6f5010 205228 python optional 
python-webob_1.6.2.orig.tar.gz
 82414afc24806b5858d32274611b3cc6 5384 python optional 
python-webob_1.6.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAliBLLkACgkQNXMSVZ0e

Bug#851044: marked as done (glance: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:35:53 +
with message-id 
and subject line Bug#851649: fixed in python-webob 1:1.6.2-2
has caused the Debian Bug report #851649,
regarding glance: FTBFS: Test failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glance
Version: 2:13.0.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> --
> _StringException: Traceback (most recent call last):
>   File "glance/tests/unit/v1/test_api.py", line 2296, in 
> test_add_image_wrong_content_type
> self.assertEqual(400, res.status_int)
>   File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 350, in 
> assertEqual
> self.assertThat(observed, matcher, message)
>   File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 435, in 
> assertThat
> raise mismatch_error
> testtools.matchers._impl.MismatchError: 400 != 201
> 
> 
> --
> Ran 2175 tests in 19.365s
> 
> FAILED (failures=2, skipped=11)
> debian/rules:17: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/01/11/glance_13.0.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-webob
Source-Version: 1:1.6.2-2

We believe that the bug you reported is fixed in the latest version of
python-webob, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-webob package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Jan 2017 16:38:16 +0100
Source: python-webob
Binary: python-webob python3-webob python-webob-doc
Architecture: source
Version: 1:1.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python-webob - Python module providing WSGI request and response objects 
(Python
 python-webob-doc - Python module providing WSGI request and response objects 
(docume
 python3-webob - Python module providing WSGI request and response objects 
(Python
Closes: 849591 851649
Changes:
 python-webob (1:1.6.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Rollback to 1.6.2 upstream release (Closes: #849591, #851649)
 - pytest replaced with nose
Checksums-Sha1:
 3248b25e682af086484e391337485514726d6581 2411 python-webob_1.6.2-2.dsc
 4e59f44f5e295f0302281008afe95841c641de22 205228 python-webob_1.6.2.orig.tar.gz
 6cffc95aee902f5c0a4b534f6bbe317ffd9c99fb 5384 
python-webob_1.6.2-2.debian.tar.xz
Checksums-Sha256:
 fa3e68055794f36334a6108fb930704cf5f97b87455be6b8abe9b46cfbb867c3 2411 
python-webob_1.6.2-2.dsc
 e096c20ec672412f7d463fd5ed23f71b9176945c66b8adb8b781b8cda174de84 205228 
python-webob_1.6.2.orig.tar.gz
 856f531182f7a60cd3abb378852e9fc1de1d2477e929b85fee0e6d93d72a0672 5384 
python-webob_1.6.2-2.debian.tar.xz
Files:
 32ca4ec065c1b27f504014e363d94f44 2411 python optional python-webob_1.6.2-2.dsc
 cc88bf68d6bf879c2d2145c86b6f5010 205228 python optional 
python-webob_1.6.2.orig.tar.gz
 82414afc24806b5858d32274611b3cc6 5384 python optional 
python-webob_1.6.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#850990: marked as done (nova: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:35:53 +
with message-id 
and subject line Bug#851649: fixed in python-webob 1:1.6.2-2
has caused the Debian Bug report #851649,
regarding nova: FTBFS: Test failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nova
Version: 2:14.0.0-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>   File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
> return func(*args, **keywargs)
>   File "nova/tests/unit/api/openstack/compute/test_microversions.py", line 
> 291, in _test_microversions_inner_function
> self.assertEqual(200, res.status_int)
>   File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 350, in 
> assertEqual
> self.assertThat(observed, matcher, message)
>   File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 435, in 
> assertThat
> raise mismatch_error
> testtools.matchers._impl.MismatchError: 200 != 400
> 
> 
> --
> Ran 14287 tests in 124.274s
> 
> FAILED (failures=4, skipped=56)
> debian/rules:150: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/01/11/nova_14.0.0-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-webob
Source-Version: 1:1.6.2-2

We believe that the bug you reported is fixed in the latest version of
python-webob, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-webob package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Jan 2017 16:38:16 +0100
Source: python-webob
Binary: python-webob python3-webob python-webob-doc
Architecture: source
Version: 1:1.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python-webob - Python module providing WSGI request and response objects 
(Python
 python-webob-doc - Python module providing WSGI request and response objects 
(docume
 python3-webob - Python module providing WSGI request and response objects 
(Python
Closes: 849591 851649
Changes:
 python-webob (1:1.6.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Rollback to 1.6.2 upstream release (Closes: #849591, #851649)
 - pytest replaced with nose
Checksums-Sha1:
 3248b25e682af086484e391337485514726d6581 2411 python-webob_1.6.2-2.dsc
 4e59f44f5e295f0302281008afe95841c641de22 205228 python-webob_1.6.2.orig.tar.gz
 6cffc95aee902f5c0a4b534f6bbe317ffd9c99fb 5384 
python-webob_1.6.2-2.debian.tar.xz
Checksums-Sha256:
 fa3e68055794f36334a6108fb930704cf5f97b87455be6b8abe9b46cfbb867c3 2411 
python-webob_1.6.2-2.dsc
 e096c20ec672412f7d463fd5ed23f71b9176945c66b8adb8b781b8cda174de84 205228 
python-webob_1.6.2.orig.tar.gz
 856f531182f7a60cd3abb378852e9fc1de1d2477e929b85fee0e6d93d72a0672 5384 
python-webob_1.6.2-2.debian.tar.xz
Files:
 32ca4ec065c1b27f504014e363d94f44 2411 python optional python-webob_1.6.2-2.dsc
 cc88bf68d6bf879c2d2145c86b6f5010 205228 python optional 
python-webob_1.6.2.orig.tar.gz
 82414afc24806b5858d32274611b3cc6 5384 python optional 
python-webob_1.6.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#851027: marked as done (python-oslo.middleware: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:35:53 +
with message-id 
and subject line Bug#851649: fixed in python-webob 1:1.6.2-2
has caused the Debian Bug report #851649,
regarding python-oslo.middleware: FTBFS: Test failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-oslo.middleware
Version: 3.19.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> 
> Traceback (most recent call last):
>   File "oslo_middleware/tests/test_sizelimit.py", line 108, in 
> test_request_too_large_no_content_length
> self.assertEqual(413, response.status_int)
>   File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 350, in 
> assertEqual
> self.assertThat(observed, matcher, message)
>   File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 435, in 
> assertThat
> raise mismatch_error
> testtools.matchers._impl.MismatchError: 413 != 200
> 
> 
> --
> Ran 93 tests in 0.771s
> 
> FAILED (failures=1)
> debian/rules:14: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2017/01/11/python-oslo.middleware_3.19.0-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-webob
Source-Version: 1:1.6.2-2

We believe that the bug you reported is fixed in the latest version of
python-webob, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-webob package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Jan 2017 16:38:16 +0100
Source: python-webob
Binary: python-webob python3-webob python-webob-doc
Architecture: source
Version: 1:1.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python-webob - Python module providing WSGI request and response objects 
(Python
 python-webob-doc - Python module providing WSGI request and response objects 
(docume
 python3-webob - Python module providing WSGI request and response objects 
(Python
Closes: 849591 851649
Changes:
 python-webob (1:1.6.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Rollback to 1.6.2 upstream release (Closes: #849591, #851649)
 - pytest replaced with nose
Checksums-Sha1:
 3248b25e682af086484e391337485514726d6581 2411 python-webob_1.6.2-2.dsc
 4e59f44f5e295f0302281008afe95841c641de22 205228 python-webob_1.6.2.orig.tar.gz
 6cffc95aee902f5c0a4b534f6bbe317ffd9c99fb 5384 
python-webob_1.6.2-2.debian.tar.xz
Checksums-Sha256:
 fa3e68055794f36334a6108fb930704cf5f97b87455be6b8abe9b46cfbb867c3 2411 
python-webob_1.6.2-2.dsc
 e096c20ec672412f7d463fd5ed23f71b9176945c66b8adb8b781b8cda174de84 205228 
python-webob_1.6.2.orig.tar.gz
 856f531182f7a60cd3abb378852e9fc1de1d2477e929b85fee0e6d93d72a0672 5384 
python-webob_1.6.2-2.debian.tar.xz
Files:
 32ca4ec065c1b27f504014e363d94f44 2411 python optional python-webob_1.6.2-2.dsc
 cc88bf68d6bf879c2d2145c86b6f5010 205228 python optional 
python-webob_1.6.2.orig.tar.gz
 82414afc24806b5858d32274611b3cc6 5384 python optional 
python-webob_1.6.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAliBLLkACgkQNXMSVZ0e

Bug#851032: marked as done (gnocchi: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:35:53 +
with message-id 
and subject line Bug#851649: fixed in python-webob 1:1.6.2-2
has caused the Debian Bug report #851649,
regarding gnocchi: FTBFS: Test failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnocchi
Version: 3.0.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> self.assertThat(observed, matcher, message)
>   File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 435, in 
> assertThat
> raise mismatch_error
> testtools.matchers._impl.MismatchError: !=:
> reference = [(datetime.datetime(2014, 1, 1, 0, 0, tzinfo=), 
> 86400.0, 55.5),
>  (datetime.datetime(2014, 1, 1, 12, 0, tzinfo=), 3600.0, 55.5),
>  (datetime.datetime(2014, 1, 1, 12, 0, tzinfo=), 300.0, 69),
>  (datetime.datetime(2014, 1, 1, 12, 5, tzinfo=), 300.0, 42.0)]
> actual= []
> 
> 
> --
> Ran 304 tests in 46.735s
> 
> FAILED (failures=44, skipped=24)
> debian/rules:44: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/01/11/gnocchi_3.0.0-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-webob
Source-Version: 1:1.6.2-2

We believe that the bug you reported is fixed in the latest version of
python-webob, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-webob package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Jan 2017 16:38:16 +0100
Source: python-webob
Binary: python-webob python3-webob python-webob-doc
Architecture: source
Version: 1:1.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python-webob - Python module providing WSGI request and response objects 
(Python
 python-webob-doc - Python module providing WSGI request and response objects 
(docume
 python3-webob - Python module providing WSGI request and response objects 
(Python
Closes: 849591 851649
Changes:
 python-webob (1:1.6.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Rollback to 1.6.2 upstream release (Closes: #849591, #851649)
 - pytest replaced with nose
Checksums-Sha1:
 3248b25e682af086484e391337485514726d6581 2411 python-webob_1.6.2-2.dsc
 4e59f44f5e295f0302281008afe95841c641de22 205228 python-webob_1.6.2.orig.tar.gz
 6cffc95aee902f5c0a4b534f6bbe317ffd9c99fb 5384 
python-webob_1.6.2-2.debian.tar.xz
Checksums-Sha256:
 fa3e68055794f36334a6108fb930704cf5f97b87455be6b8abe9b46cfbb867c3 2411 
python-webob_1.6.2-2.dsc
 e096c20ec672412f7d463fd5ed23f71b9176945c66b8adb8b781b8cda174de84 205228 
python-webob_1.6.2.orig.tar.gz
 856f531182f7a60cd3abb378852e9fc1de1d2477e929b85fee0e6d93d72a0672 5384 
python-webob_1.6.2-2.debian.tar.xz
Files:
 32ca4ec065c1b27f504014e363d94f44 2411 python optional python-webob_1.6.2-2.dsc
 cc88bf68d6bf879c2d2145c86b6f5010 205228 python optional 
python-webob_1.6.2.orig.tar.gz
 82414afc24806b5858d32274611b3cc6 5384 python optional 
python-webob_1.6.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAliBLLkACgkQNXMSVZ0e
BkvXKA/5AWVueUUqy9eS9ae5E53Mvp9XRTXjXS1/Jiz3lXjEgd3kcARoNeGG072+

Bug#851649: marked as done (python-webob: This version causes FTBFS of six OpenStack packages due backwards incompatibility)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:35:53 +
with message-id 
and subject line Bug#851649: fixed in python-webob 1:1.6.2-2
has caused the Debian Bug report #851649,
regarding python-webob: This version causes FTBFS of six OpenStack packages due 
backwards incompatibility
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-webob
Version: 1.7.0-1
Severity: serious

Hi,
upgrading from 1.6.2-1 to 1.7.0-1 causes multiple FTBFS in OpenStack packages.

Resolving of OpenStack packages FTBFS issues is hard due to the approaching 
stretch freeze.
Additionally, python-webob 1.7.0-1 has its own FTBFS and it is uncertain 
whether he gets into testing.
It would be possible to remove 1.7.0-1 from unstable?
I prefer 1.6.2-1, which works fine with current OpenStack in Debian.

Regards,
Ondrej Koblizek

-- System Information:
Debian Release: stretch/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-34-generic (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: python-webob
Source-Version: 1:1.6.2-2

We believe that the bug you reported is fixed in the latest version of
python-webob, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-webob package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Jan 2017 16:38:16 +0100
Source: python-webob
Binary: python-webob python3-webob python-webob-doc
Architecture: source
Version: 1:1.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python-webob - Python module providing WSGI request and response objects 
(Python
 python-webob-doc - Python module providing WSGI request and response objects 
(docume
 python3-webob - Python module providing WSGI request and response objects 
(Python
Closes: 849591 851649
Changes:
 python-webob (1:1.6.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Rollback to 1.6.2 upstream release (Closes: #849591, #851649)
 - pytest replaced with nose
Checksums-Sha1:
 3248b25e682af086484e391337485514726d6581 2411 python-webob_1.6.2-2.dsc
 4e59f44f5e295f0302281008afe95841c641de22 205228 python-webob_1.6.2.orig.tar.gz
 6cffc95aee902f5c0a4b534f6bbe317ffd9c99fb 5384 
python-webob_1.6.2-2.debian.tar.xz
Checksums-Sha256:
 fa3e68055794f36334a6108fb930704cf5f97b87455be6b8abe9b46cfbb867c3 2411 
python-webob_1.6.2-2.dsc
 e096c20ec672412f7d463fd5ed23f71b9176945c66b8adb8b781b8cda174de84 205228 
python-webob_1.6.2.orig.tar.gz
 856f531182f7a60cd3abb378852e9fc1de1d2477e929b85fee0e6d93d72a0672 5384 
python-webob_1.6.2-2.debian.tar.xz
Files:
 32ca4ec065c1b27f504014e363d94f44 2411 python optional python-webob_1.6.2-2.dsc
 cc88bf68d6bf879c2d2145c86b6f5010 205228 python optional 
python-webob_1.6.2.orig.tar.gz
 82414afc24806b5858d32274611b3cc6 5384 python optional 
python-webob_1.6.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAliBLLkACgkQNXMSVZ0e
BkvXKA/5AWVueUUqy9eS9ae5E53Mvp9XRTXjXS1/Jiz3lXjEgd3kcARoNeGG072+
TL8bSVwKvtVrHsIrhixC/bN9tcJgmsHWLzwmKCfsr7fR40DsLqfk6F/bTgSYnZSl
+hJ/d17Gl+cHgJ0kNX4JtV8107wM88jAsxrJ3OJBj4H6a2JOQdhrxBFj7+At5h7A
+4XmJgFHfyLhKWXI0G39t6LJFjI78Bqr7mNpeBYMGZzKk5MIqoQUqdYGba32s4wr
H0oEl8npk2RDvzpKo6bTHPebJwsOThEaQy8XpyGMq50gcOVM80sZ7dDGOZIyMS1J
N0XriVvw4s9LXAQc6xGLxRvaaQM6MsRlWAZwmcdmvJR159PJvEFwx660Qt5jPuRq
YHFsr9njxGlSkIbrJp4cDBHq3ef5uowzOkc+R3jz3bE1OEDEbD/U/oGUAFbozM/i
8MpjHtsKvLCTH57Wn/IgoJikEe928CfxtNmE+pam3qQMpRP0M0GDpkmvLCI7LWmE
oans5ZYzX0/nkKcOZQiWKwd7so5Ty6mHMBx4pZ+B3vbd8KoVztE7HFVVPKxBy7GY
a/ML4ng/poj1rbIbj1FR6U5GdxDhEofw/itR5AaF/5jYRcktYi2rh7BHe5qgQarz

Bug#851814: marked as done (apt-build: Broken postinst by less permissive sed)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:33:39 +
with message-id 
and subject line Bug#851814: fixed in apt-build 0.12.46
has caused the Debian Bug report #851814,
regarding apt-build: Broken postinst by less permissive sed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-build
Version: 0.12.45
Severity: serious
Tags: patch

Dear QA Group:

Installing apt-build results in this error:

Setting up apt-build (0.12.45) ...
sed: character class syntax is [[:space:]], not [:space:]
dpkg: error processing package apt-build (--configure):
 subprocess installed post-installation script returned error exit
status 4
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
 apt-build

Discovered by Antonio Trujillo here:

https://lists.debian.org/msgid-search/dd7864af-d235-217c-74dc-bd1b5a086...@juntadeandalucia.es

I think the following trivial patch should fix it, but I'm not
confident enough to push it to git because version in Debian archives
does not exactly match HEAD in git.

Thanks.

--- a/debian/postinst
+++ b/debian/postinst
@@ -75,7 +75,7 @@ if [ "$1" = "configure" ] ; then
 if [ -e "$source" ] ; then
# comment in all sources lists if asked
if [ "$add_to_sourceslist" = "false" ] ; then
-sed -i -e "s|^[:space:]*$debline.*|#$debline|" "$source"
+sed -i -e "s|^[[:space:]]*$debline.*|#$debline|" "$source"
   
   # check if source entry is already enabled
   elif grep -Eq "^[[:space:]]*$debline" "$source" ; then
@@ -149,12 +149,12 @@ if [ "$1" = "configure" ] ; then
   test -z "make_options" || grep -Eq '^[[:space:]]*make_options =' $CONFFILE 
|| \
 echo "make_options =" >> $CONFFILE
   
-  sed -e "s|^[:space:]*build-dir =.*|build-dir = $build_dir|" \
-  -e "s|^[:space:]*repository-dir =.*|repository-dir = $repository_dir|" \
-  -e "s|^[:space:]*Olevel =.*|Olevel = $Olevel|" \
-  -e "s|^[:space:]*mtune =.*|mtune = $mtune|" \
-  -e "s|^[:space:]*options =.*|options = \" $options\"|" \
-  -e "s|^[:space:]*make_options =.*|make_options = \" $make_options\"|" \
+  sed -e "s|^[[:space:]]*build-dir =.*|build-dir = $build_dir|" \
+  -e "s|^[[:space:]]*repository-dir =.*|repository-dir = $repository_dir|" 
\
+  -e "s|^[[:space:]]*Olevel =.*|Olevel = $Olevel|" \
+  -e "s|^[[:space:]]*mtune =.*|mtune = $mtune|" \
+  -e "s|^[[:space:]]*options =.*|options = \" $options\"|" \
+  -e "s|^[[:space:]]*make_options =.*|make_options = \" $make_options\"|" \
   < $CONFFILE > $CONFFILE.tmp
   
   mv -f $CONFFILE.tmp $CONFFILE
--- End Message ---
--- Begin Message ---
Source: apt-build
Source-Version: 0.12.46

We believe that the bug you reported is fixed in the latest version of
apt-build, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated apt-build package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 19 Jan 2017 21:56:57 +0100
Source: apt-build
Binary: apt-build
Architecture: source amd64
Version: 0.12.46
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Axel Beckert 
Description:
 apt-build  - frontend to apt to build, optimize and install packages
Closes: 672183 757296 851814
Changes:
 apt-build (0.12.46) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Santiago Vila ]
   * Fix postinst compatibility with stricter sed syntax in more recent sed
 releases. (Closes: #851814)
 .
   [ Axel Beckert ]
   * Switch Vcs-Git headers from git:// to https://.
   * Make debian/control non-executable.
   * Enable all hardening build flags.
   * Declare compliance with Debian Policy 3.9.8.
   * Apply "wrap-and-sort -a".
   * Cherry-pick changes to several packaging files from commit 24b41459 by
 Dominique Lasserre from the never completed 0.13.1 release 

Processed: Merge bugs after rollback to python-webob/1:1.6.2-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 851044  src:python-webob
Bug #851044 [src:glance] glance: FTBFS: Test failures
Bug reassigned from package 'src:glance' to 'src:python-webob'.
No longer marked as found in versions glance/2:13.0.0-1.
Ignoring request to alter fixed versions of bug #851044 to the same values 
previously set
> reassign 851032  src:python-webob
Bug #851032 [src:gnocchi] gnocchi: FTBFS: Test failures
Bug reassigned from package 'src:gnocchi' to 'src:python-webob'.
No longer marked as found in versions gnocchi/3.0.0-2.
Ignoring request to alter fixed versions of bug #851032 to the same values 
previously set
> reassign 851045  src:python-webob
Bug #851045 [src:keystone] keystone: FTBFS: Test failures
Bug reassigned from package 'src:keystone' to 'src:python-webob'.
No longer marked as found in versions keystone/2:10.0.0-5.
Ignoring request to alter fixed versions of bug #851045 to the same values 
previously set
> reassign 850990  src:python-webob
Bug #850990 [src:nova] nova: FTBFS: Test failures
Bug reassigned from package 'src:nova' to 'src:python-webob'.
No longer marked as found in versions nova/2:14.0.0-3.
Ignoring request to alter fixed versions of bug #850990 to the same values 
previously set
> reassign 850987  src:python-webob
Bug #850987 [src:python-keystonemiddleware] python-keystonemiddleware: FTBFS: 
Test failures
Bug reassigned from package 'src:python-keystonemiddleware' to 
'src:python-webob'.
No longer marked as found in versions python-keystonemiddleware/4.9.0-2.
Ignoring request to alter fixed versions of bug #850987 to the same values 
previously set
> reassign 851027  src:python-webob
Bug #851027 [src:python-oslo.middleware] python-oslo.middleware: FTBFS: Test 
failures
Bug reassigned from package 'src:python-oslo.middleware' to 'src:python-webob'.
No longer marked as found in versions python-oslo.middleware/3.19.0-2.
Ignoring request to alter fixed versions of bug #851027 to the same values 
previously set
> forcemerge 851649 851044 851032 851045 850990 850987 851027
Bug #851649 [src:python-webob] python-webob: This version causes FTBFS of six 
OpenStack packages due backwards incompatibility
Bug #851649 [src:python-webob] python-webob: This version causes FTBFS of six 
OpenStack packages due backwards incompatibility
Added tag(s) sid and stretch.
Bug #851045 [src:python-webob] keystone: FTBFS: Test failures
Added indication that 851045 affects 
nova,gnocchi,keystone,python-keystonemiddleware,glance,python-oslo.middleware
Marked as found in versions python-webob/1.7.0-1.
Bug #850987 [src:python-webob] python-keystonemiddleware: FTBFS: Test failures
Added indication that 850987 affects 
nova,gnocchi,keystone,python-keystonemiddleware,glance,python-oslo.middleware
Marked as found in versions python-webob/1.7.0-1.
Bug #851044 [src:python-webob] glance: FTBFS: Test failures
Added indication that 851044 affects 
nova,gnocchi,keystone,python-keystonemiddleware,glance,python-oslo.middleware
Marked as found in versions python-webob/1.7.0-1.
Bug #850990 [src:python-webob] nova: FTBFS: Test failures
Added indication that 850990 affects 
nova,gnocchi,keystone,python-keystonemiddleware,glance,python-oslo.middleware
Marked as found in versions python-webob/1.7.0-1.
Bug #851032 [src:python-webob] gnocchi: FTBFS: Test failures
Added indication that 851032 affects 
nova,gnocchi,keystone,python-keystonemiddleware,glance,python-oslo.middleware
Marked as found in versions python-webob/1.7.0-1.
Bug #851027 [src:python-webob] python-oslo.middleware: FTBFS: Test failures
Added indication that 851027 affects 
nova,gnocchi,keystone,python-keystonemiddleware,glance,python-oslo.middleware
Marked as found in versions python-webob/1.7.0-1.
Merged 850987 850990 851027 851032 851044 851045 851649
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
850987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850987
850990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850990
851027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851027
851032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851032
851044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851044
851045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851045
851649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851792: palo ships binary in the sources

[Helge Deller]

On 18.01.2017 20:40, Adrian Bunk wrote:
> Package: palo
...
> If palo should continue to be available on non-hppa machines,
> a (binary-all) package that uses gcc-hppa-linux-gnu for building
> might be an option.

I'll check if it's possile. May take some time.

Helge

Bug#849675: marked as done (pytest-httpbin: ImportError pytest_httpbin/certs': missing __init__.py)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 22:15:04 +0100
with message-id <8f2286f8-6441-b8a2-97c7-b393a4f2f...@danielstender.com>
and subject line pytest-httpbin: ImportError pytest_httpbin/certs': missing 
__init__.py
has caused the Debian Bug report #849675,
regarding pytest-httpbin: ImportError pytest_httpbin/certs': missing __init__.py
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
849675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-httpbin
Version: 0.2.3-1
Severity: grave
Justification: renders package unusable

Pytest actually can't use the plugin:


/usr/lib/python2.7/dist-packages/pytest_httpbin/plugin.py:4: ImportWarning: Not 
importing directory '/usr/lib/python2.7/dist-packages/pytest_httpbin/certs': 
missing __init__.py
  from . import serve, certs


The same is true for the Python3 package:


/.
/usr
/usr/lib
/usr/lib/python3
/usr/lib/python3/dist-packages
/usr/lib/python3/dist-packages/pytest_httpbin
/usr/lib/python3/dist-packages/pytest_httpbin/__init__.py
/usr/lib/python3/dist-packages/pytest_httpbin/certs
/usr/lib/python3/dist-packages/pytest_httpbin/certs/cacert.pem
/usr/lib/python3/dist-packages/pytest_httpbin/certs/cert.pem
/usr/lib/python3/dist-packages/pytest_httpbin/certs/key.pem
/usr/lib/python3/dist-packages/pytest_httpbin/certs.py
/usr/lib/python3/dist-packages/pytest_httpbin/plugin.py
/usr/lib/python3/dist-packages/pytest_httpbin/serve.py
/usr/lib/python3/dist-packages/pytest_httpbin/version.py
/usr/lib/python3/dist-packages/pytest_httpbin-0.2.3.egg-info
/usr/lib/python3/dist-packages/pytest_httpbin-0.2.3.egg-info/PKG-INFO
/usr/lib/python3/dist-packages/pytest_httpbin-0.2.3.egg-info/dependency_links.txt
/usr/lib/python3/dist-packages/pytest_httpbin-0.2.3.egg-info/entry_points.txt
/usr/lib/python3/dist-packages/pytest_httpbin-0.2.3.egg-info/requires.txt
/usr/lib/python3/dist-packages/pytest_httpbin-0.2.3.egg-info/top_level.txt
/usr/share
/usr/share/doc
/usr/share/doc/python3-pytest-httpbin
/usr/share/doc/python3-pytest-httpbin/README.gz
/usr/share/doc/python3-pytest-httpbin/changelog.Debian.gz
/usr/share/doc/python3-pytest-httpbin/changelog.gz
/usr/share/doc/python3-pytest-httpbin/copyright


DS

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Control: tags -1 + unreproducible

No, the package actually is o.k., certs/ isn't actually a package. This import 
error
occured once, but it appears that this was non standard behavior. This hasn't 
been
reported somewhere else, so I'm closing this now.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#847750: marked as done (rmysql: FTBFS on mips64el)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:12:00 +
with message-id 
and subject line Bug#850142: fixed in mariadb-connector-c 2.3.2-1
has caused the Debian Bug report #850142,
regarding rmysql: FTBFS on mips64el
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
850142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rmysql
Version: 0.10.9-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=rmysql=mips64el=0.10.9-3=1480467978

 fakeroot debian/rules binary-arch
CDBS WARNING:simple-patchsys.mk is deprecated since 0.4.85 - please use 
source format 3.0 (quilt) instead
test -x debian/rules
dh_testroot
dh_prep 
dh_installdirs -A 
dh_installdirs: Compatibility levels before 9 are deprecated (level 7 in use)
mkdir -p "."
dh_installdirs  usr/lib/R/site-library
dh_installdirs: Compatibility levels before 9 are deprecated (level 7 in use)
echo "R:Depends=r-base-core (>= 3.3.2-1), r-api-3" >> 
debian/r-cran-rmysql.substvars
if test -f /usr/bin/xvfb-run; then  \
 xvfb-run -a\
R CMD INSTALL -l 
/«PKGBUILDDIR»/debian/r-cran-rmysql/usr/lib/R/site-library --clean \
 .  \
"--built-timestamp=\"Thu, 10 Nov 2016 06:12:59 
-0600\"" \
;   \
else\
 R CMD INSTALL -l 
/«PKGBUILDDIR»/debian/r-cran-rmysql/usr/lib/R/site-library\
--clean  .  \
"--built-timestamp=\"Thu, 10 Nov 2016 06:12:59 
-0600\"" \
;   \
fi
* installing *source* package 'RMySQL' ...
** package 'RMySQL' successfully unpacked and MD5 sums checked
./configure: line 21: warning: command substitution: ignored null byte in input
./configure: line 22: warning: command substitution: ignored null byte in input
Found mysql_config cflags and libs!
Using PKG_CFLAGS=-I/usr/include/mariadb -I/usr/include/mariadb/mysql -g -O2 
-fdebug-prefix-map=/build/mariadb-connector-c-dopxmU/mariadb-connector-c-2.3.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wunused -Wno-uninitialized
-I/usr/include/mariadb -I/usr/include/mariadb/mysql -g -O2 
-fdebug-prefix-map=/build/mariadb-connector-c-dopxmU/mariadb-connector-c-2.3.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wunused -Wno-uninitialized
Using PKG_LIBS=-L/usr/lib/mips64el-linux-gnuabi64 -lmariadb
-L/usr/lib/mips64el-linux-gnuabi64 -lmariadb
- ANTICONF ERROR ---
Configuration failed because libmysqlclient was not found. Try installing:
 * deb: libmariadb-client-lgpl-dev (Debian, Ubuntu 16.04)
libmariadbclient-dev (Ubuntu 14.04)
 * rpm: mariadb-devel | mysql-devel (Fedora, CentOS, RHEL)
 * csw: mysql56_dev (Solaris)
 * brew: mariadb-connector-c (OSX)
If libmysqlclient is already installed, check that 'pkg-config' is in your
PATH and PKG_CONFIG_PATH contains a libmysqlclient.pc file. If pkg-config
is unavailable you can set INCLUDE_DIR and LIB_DIR manually via:
R CMD INSTALL --configure-vars='INCLUDE_DIR=... LIB_DIR=...'

ERROR: configuration failed for package 'RMySQL'
* removing '/«PKGBUILDDIR»/debian/r-cran-rmysql/usr/lib/R/site-library/RMySQL'
/usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch' failed
make: *** [R_any_arch] Error 1


Andreas
--- End Message ---
--- Begin Message ---
Source: mariadb-connector-c
Source-Version: 2.3.2-1

We believe that the bug you reported is fixed in the latest version of
mariadb-connector-c, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Otto Kekäläinen  (supplier of updated mariadb-connector-c 
package)

(This message was generated automatically at 

Bug#851841: xonsh: jobs and backgrounding broken

[Gordon Ball]

Thanks for reporting.

I think I have to agree. I pushed the 0.5 series when it was released
thinking it would be a better base if patching was required in future,
but there do appear to be too many bugs which cannot be patched at the
moment.

I have upgraded the bug to severity:serious to prevent migration, so
stretch will get 0.4.7 and unstable will be updated when patches for 0.5
are available.

On 19/01/17 09:48, Frederic Peters wrote:
> Package: xonsh
> Version: 0.5.2+dfsg-1
> Severity: important
> 
> Hi,
> 
> This is about https://github.com/xonsh/xonsh/issues/2071
> 
> From a comment in there:
> 
>   I think there are two separate issues here (that I've noticed).  One is that
>   backgrounding doesn't seem to work (the big issue). The other is that while
>   the SIGSTOP is sent by Ctrl-Z, the prompt doesn't always return control to
>   the user.
> 
> This makes xonsh almost unusable, and this version shouldn't migrate to
> testing. (imo)
> 
> 
> Thanks,
> Frederic
> 
> -- System Information:
> Debian Release: 9.0
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages xonsh depends on:
> ii  python3-pkg-resources  32.3.1-1
> ii  python3-ply3.9-1
> ii  python3-venv   3.5.1-4
> pn  python3:any
> 
> Versions of packages xonsh recommends:
> ii  python3-prompt-toolkit  1.0.9-1
> ii  python3-pygments2.1.3+dfsg-1
> ii  python3-setproctitle1.1.10-1
> 
> Versions of packages xonsh suggests:
> ii  xonsh-doc  0.5.2+dfsg-1
> 
> -- no debconf information
> 

Bug#851518: cinnamon won't start

[William L. DeRieux IV]

tags 851518 - moreinfo-- 
On Tue, 17 Jan 2017 22:43:42 +0100 Carsten Kosthorstwrote:


> Hi,
>
> I updated today and cinnamon is working again.
>
> Thanks,
>
> Carsten
>
>
>

Your version of cinnamon was 3.2.7-1 in the initial report.

The latest version in unstable/sid is 3.2.7-1.

What version was cinnamon updated to the second time?

You can do this by using: *apt-cache policy cinnamon*

The latest version in stretch/sid is 3.2.7-1, so I'm thinking this issue 
was temporary ?

Bug#850142: marked as done (libmariadb-dev: mariadb_config emits trailing binary bullshit on mips64el)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 21:12:00 +
with message-id 
and subject line Bug#850142: fixed in mariadb-connector-c 2.3.2-1
has caused the Debian Bug report #850142,
regarding libmariadb-dev: mariadb_config emits trailing binary bullshit on 
mips64el
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
850142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmariadb-dev
Version: 2.3.1-1
Severity: important
Control: affects -1 + src:rmysql

(severity should be serious, will raise after the next britney run)

(sid_mips64el-dchroot)anbe@eller:~$ mariadb_config
Copyright 2011-2015 MariaDB Corporation AB
Get compiler flags for using the MariaDB Connector/C.
Usage: mariadb_config [OPTIONS]
  --cflags[-I/usr/include/mariadb -I/usr/include/mariadb/mysql -g -O2 
-fdebug-prefix-map=/build/mariadb-connector-c-dopxmU/mariadb-connector-c-2.3.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wunused -Wno-uninitialized]
  --include   [-I/usr/include/mariadb -I/usr/include/mariadb/mysql]
  --libs  [-L/usr/lib/mips64el-linux-gnuabi64 -lmariadb]
  --libs_r[-L/usr/lib/mips64el-linux-gnuabi64 -lmariadb]
  --version   [5.5.1]
  --socket[/var/run/mysqld/mysqld.sock]
  --port  [3306]
  --plugindir [/usr/lib/mips64el-linux-gnuabi64/mariadb/plugin]
  --plugindir [/usr/lib/mips64el-linux-gnuabi64/mariadb/plugin]
ql]
g -O2 
-fdebug-prefix-map=/build/mariadb-connector-c-dopxmU/mariadb-connector-c-2.3.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wunused -Wno-uninitialized]
�

Looks like some buffer is printed twice (starting at the second --plugindir)
and this includes all *bytes* from the buffer, ignoring zero termination.
Redirecting this to a file (or piping through hd) does not give the the 
duplicate
--plugindir setting, but a lot of \0 bytes (and three non-\0 bytes) at the end.
Running mariadb_config with some arguments emits similar trailing binary crap.


(sid_mips64el-dchroot)anbe@eller:~$ mariadb_config | hd | tail -n 20
0540  75 73 72 2f 6c 69 62 2f  6d 69 70 73 36 34 65 6c  |usr/lib/mips64el|
0550  2d 6c 69 6e 75 78 2d 67  6e 75 61 62 69 36 34 20  |-linux-gnuabi64 |
0560  2d 6c 6d 61 72 69 61 64  62 5d 0a 20 20 2d 2d 76  |-lmariadb].  --v|
0570  65 72 73 69 6f 6e 20 20  20 20 20 20 20 5b 35 2e  |ersion   [5.|
0580  35 2e 31 5d 0a 20 20 2d  2d 73 6f 63 6b 65 74 20  |5.1].  --socket |
0590  20 20 20 20 20 20 20 5b  2f 76 61 72 2f 72 75 6e  |   [/var/run|
05a0  2f 6d 79 73 71 6c 64 2f  6d 79 73 71 6c 64 2e 73  |/mysqld/mysqld.s|
05b0  6f 63 6b 5d 0a 20 20 2d  2d 70 6f 72 74 20 20 20  |ock].  --port   |
05c0  20 20 20 20 20 20 20 5b  33 33 30 36 5d 0a 20 20  |   [3306].  |
05d0  2d 2d 70 6c 75 67 69 6e  64 69 72 20 20 20 20 20  |--plugindir |
05e0  5b 2f 75 73 72 2f 6c 69  62 2f 6d 69 70 73 36 34  |[/usr/lib/mips64|
05f0  65 6c 2d 6c 69 6e 75 78  2d 67 6e 75 61 62 69 36  |el-linux-gnuabi6|
0600  34 2f 6d 61 72 69 61 64  62 2f 70 6c 75 67 69 6e  |4/mariadb/plugin|
0610  5d 0a 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |]...|
0620  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
*
1310  00 f1 0f 02 00 00 00 00  00 00 00 00 00 00 00 00  ||
1320  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
*
00022309


This breaks the rmysql configure script.


While you are it it, please filter out -fdebug-prefix-map=* from the cflags.


Andreas
--- End Message ---
--- Begin Message ---
Source: mariadb-connector-c
Source-Version: 2.3.2-1

We believe that the bug you reported is fixed in the latest version of
mariadb-connector-c, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Otto Kekäläinen  (supplier of updated mariadb-connector-c 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED 

Bug#851901: [Aptitude-devel] Bug#851901: aptitude: "E: Internal Error, No file name for apt-build:amd64" after failed reinstallation of apt-build, then endless loop "Can't find a source to download ve

[Axel Beckert]

Control: severity -1 important

Hi again,

Axel Beckert wrote:
> Axel Beckert wrote:
> > Will now try to get out of that mess. Will post it here, once I
> > found a way out of this state.
> 
> "aptitude keep apt-build" on the commandline at least got me out of
> the endless loop in the TUI.

Downgrading the severity to important after discussion on IRC since:

* There is no data loss.
* There is an easy way to solve the problem (Ctrl-C + "aptitude keep").
* The problem is likely to appear only seldom(*).

(*) Nevertheless #841506 looks similar, but neither has much details
nor any endless loop. (And is also only of severity important,
too.)

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


signature.asc
Description: Digital signature

Processed: Re: [Aptitude-devel] Bug#851901: aptitude: "E: Internal Error, No file name for apt-build:amd64" after failed reinstallation of apt-build, then endless loop "Can't find a source to download

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #851901 [aptitude] aptitude: "E: Internal Error, No file name for 
apt-build:amd64" after failed reinstallation of apt-build, then endless loop 
"Can't find a source to download version '0.12.46'" in TUI after installing a 
fixed apt-build with "dpkg -i"
Severity set to 'important' from 'serious'

-- 
851901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851893: The availability of update-grub does not imply that GRUB is used

[Aurélien COUDERC]

Hi Alexander.

Le 19 janvier 2017 17:47:18 GMT+01:00, Alexander Kurtz  a 
écrit :

>Hi!
>
>People who want to have the GRUB binaries installed (for example to
>create VM images with GRUB), but don't want to use GRUB as their
>bootloader will (in the case of classic PCs) have the grub-pc-bin [0]
>and grub2-common [1] packages installed, but not the grub-pc [2]
>package as this contains the scripts for the automatic installation.

[buggy script code…]

>Since update-grub is shipped by the grub2-common package (see [3]),
>this test is wrong. The fact that update-grub is available does not
>imply that the system uses GRUB to boot. Since update-grub will
>obviously fail to run if GRUB is not installed to /boot, this bug
>causes desktop-base's postinst to fail, making the package
>uninstallable on such systems.

Thank you for your detailed bug report and analysis.
This looks a lot like #843727 [0] to me, although not for the same use case.

Would you care to test 9.0.1, already in sid that should fix this problem ?
The following change was done :
208:update-grub || echo "Updating grub failed, report success anyway!"

I'll merge the 2 bugs after confirmation that it works for you.

If you know of a better and robust way to detect if grub is being used, advice 
is welcome.

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

Cheers,
--Aurélien

Processed: tagging 701814, tagging 648208, tagging 776275, tagging 698733

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 701814 + pending
Bug #701814 [os-prober] os-prober: damages XFS exported via iSCSI but not 
mounted locally; potential data loss
Added tag(s) pending.
> tags 648208 + pending
Bug #648208 [os-prober] os-prober: blockdev --setro affects running kvm 
instances
Bug #788062 [os-prober] os-prober corrupts LVs/partitions while being mounted 
inside a VM
Bug #794849 [os-prober] linux: custom linux-image packages fail to install
Bug #806273 [os-prober] os-prober: remove or disable-per default the non 
grub-mount based probing
Bug #810121 [os-prober] linux: KVM guests randomly get I/O errors on VirtIO 
based devices
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> tags 776275 + pending
Bug #776275 [os-prober] os-prober: use grub-mount-udeb on all linux/freebsd 
arches
Added tag(s) pending.
> tags 698733 + pending
Bug #698733 [os-prober] Fix detection of /usr/ partition as a GNU/Linux root 
partition when /lib* directories are moved to /usr/ completely (e.g. in Fedora 
17/18)
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
648208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648208
698733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698733
701814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701814
776275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776275
788062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788062
794849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794849
806273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806273
810121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 851841 serious
Bug #851841 [xonsh] xonsh: jobs and backgrounding broken
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
851841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851909: elog: most recent elog update included with Debian 8.7 no longer allows login (except for Admin)

[chad seys]

Package: elog
Version: 2.9.2+2014.05.11git44800a7-2+deb8u1
Severity: grave
Justification: renders package unusable

Hi,
  A day or so ago elog was updated with the Debian change from 8.6 to 8.7 .  

  Afterwards only users listed as "admin" in the elog.cfg file could log in. 
Everyone else
would receive the error message "Use has no access to this logbook".
  Upgrading to 3.1.2 in stretch allows login again.
  
  A guess is that the patch for CVE-2016-6342 was not quite correct. :)

Thanks for packaging!
C.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages elog depends on:
ii  adduser  3.113+nmu3
ii  libc62.19-18+deb8u7
ii  libkrb5-31.12.1+dfsg-19+deb8u2
ii  libssl1.0.0  1.0.1t-1+deb8u5
ii  net-tools1.60-26+b1

Versions of packages elog recommends:
ii  imagemagick  8:6.8.9.9-5+deb8u6

Versions of packages elog suggests:
pn  fckeditor  

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

-- no debconf information

Processed: limit source to nut, tagging 851015

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source nut
Limiting to bugs with field 'source' containing at least one of 'nut'
Limit currently set to 'source':'nut'

> tags 851015 + pending
Bug #851015 [src:nut] nut: FTBFS: a2x: ERROR: missing configuration file: 
/etc/asciidoc/dblatex/asciidoc-dblatex.xsl
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
851015: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#835940: Bug#851871: RM: remove gcc-5 from stretch

[Adrian Bunk]

On Thu, Jan 19, 2017 at 03:07:03PM +0100, Matthias Klose wrote:
> Package: release.debian.org
> Tags: stretch
> 
> Please remove gcc-5, gcc-5-cross and gcc-5-cross-ports from testing.  Now that
> the linux source is built using gcc-6, the list of packages also needing 
> removal
> are acoording to [1]:
> 
>  - nvida-cuda-toolkit
>  - starpu-contrib
>...

Their fix might actually be blocked by outdated information in #835940.

Quoting the relevant part from #835940:

On Mon, Nov 28, 2016 at 11:23:27AM +0100, Matthias Klose wrote:
> On 28.11.2016 02:08, lumin wrote:
> > Hello guys,
> >
> > I successfully compiled caffe with CUDA_8.0.44-2 and
> > clang-3.8 (the current default clang). Maybe we can
> > replace GCC-5 with Clang-3.8 to solve this problem.
> >
> > That means Stretch still has chance to ship CUDA8,
> > and users are expected to compile with Clang/LLVM
> > instead of GCC-6, as long as the CUDA rDepends
> > compile with clang.
> >
> > I only tested caffe-contrib.
>
> My guess is that clang-3.8 will be gone for the release as well ...


What is the final decision regarding LLVM versions in stretch?


> Matthias

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

Processed: found 842895 in 10.0.15-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 842895 10.0.15-1
Bug #842895 [src:mariadb-10.0] mariadb-10.0: CVE-2016-6664
Marked as found in versions mariadb-10.0/10.0.15-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
842895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851015: nut: FTBFS: a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl

[Laurent Bigonville]

Le 19/01/17 à 19:52, Michael Stapelberg a écrit :

[+aquette, bigon directly]

Are you aware of this issue? This RC bug transitively marked freeradius
for removal from testing. If you need help, please let me know — I have
some incentive to look into it in order to keep freeradius in stretch.

Apparently it lacks of asciidoc-dblatex build-dependency

I'll try do an upload tonight

Bug#851759: marked as done (mariadb-10.1: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 19:39:21 +
with message-id 
and subject line Bug#851759: fixed in mariadb-10.1 10.1.21-1
has caused the Debian Bug report #851759,
regarding mariadb-10.1: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 
CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 
CVE-2017-3317 CVE-2017-3318
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mariadb-10.1
Version: 10.1.20-3
Severity: grave
Tags: upstream security fixed-upstream
Justification: user security hole

Hi

The following CVEs were fixed with a new upstream version 10.1.21,
whereas CVE-2016-6664 has already a separate bug in the BTS:

CVE-2016-6664
CVE-2017-3238
CVE-2017-3243
CVE-2017-3244
CVE-2017-3257
CVE-2017-3258
CVE-2017-3265
CVE-2017-3291
CVE-2017-3312
CVE-2017-3317
CVE-2017-3318 

https://mariadb.com/kb/en/mariadb/mariadb-10121-release-notes/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mariadb-10.1
Source-Version: 10.1.21-1

We believe that the bug you reported is fixed in the latest version of
mariadb-10.1, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Otto Kekäläinen  (supplier of updated mariadb-10.1 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Jan 2017 11:33:01 +0200
Source: mariadb-10.1
Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat 
libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.1 
mariadb-client-10.1 mariadb-server-core-10.1 mariadb-server-10.1 mariadb-server 
mariadb-client mariadb-plugin-connect mariadb-plugin-oqgraph 
mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider 
mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client 
mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source amd64 all
Version: 10.1.21-1
Distribution: unstable
Urgency: low
Maintainer: Debian MySQL Maintainers 
Changed-By: Otto Kekäläinen 
Description:
 libmariadbclient-dev - MariaDB database development files
 libmariadbclient-dev-compat - MariaDB database development files 
(libmysqlclient compatibility)
 libmariadbclient18 - MariaDB database client library
 libmariadbd-dev - MariaDB embedded database, development files
 libmariadbd18 - MariaDB embedded database, shared library
 mariadb-client - MariaDB database client (metapackage depending on the latest 
vers
 mariadb-client-10.1 - MariaDB database client binaries
 mariadb-client-core-10.1 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-plugin-connect - Connect storage engine for MariaDB
 mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin 
for MariaDB
 mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client
 mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server
 mariadb-plugin-mroonga - Mroonga storage engine for MariaDB
 mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB
 mariadb-plugin-spider - Spider storage engine for MariaDB
 mariadb-plugin-tokudb - TokuDB storage engine for MariaDB
 mariadb-server - MariaDB database server (metapackage depending on the latest 
vers
 mariadb-server-10.1 - MariaDB database server binaries
 mariadb-server-core-10.1 - MariaDB database core server files
 mariadb-test - MariaDB database regression test suite
 mariadb-test-data - MariaDB database regression test suite - data files
Closes: 677223 850216 851131 851257 851759
Changes:
 mariadb-10.1 (10.1.21-1) unstable; urgency=low
 .
   [ Otto Kekäläinen ]
   * New upstream release 10.0.28. Includes fixes for the following
 security vulnerabilities (Closes: #851759, Closes: ##849435):
 - CVE-2017-3318
 - CVE-2017-3317
 - CVE-2017-3312
 - 

Bug#851257: marked as done (mariadb-server-10.1: fails to reinstall)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 19:39:21 +
with message-id 
and subject line Bug#851257: fixed in mariadb-10.1 10.1.21-1
has caused the Debian Bug report #851257,
regarding mariadb-server-10.1: fails to reinstall
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mariadb-server-10.1
Version: 10.1.20-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to reinstall
over an existing installation of the same version.

>From the attached log (scroll to the bottom...):

1m5.6s DEBUG: Starting command: ['chroot', 
'/srv/piuparts.debian.org/tmp/tmpSyjHYx', 'apt-get', '-y', 'install', 
'--reinstall', 'mariadb-server-10.1=10.1.20-3']
1m12.1s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  debconf: delaying package configuration, since apt-utils is not installed
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
  Need to get 0 B/5226 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 
(Reading database ... 9456 files and directories currently installed.)
  Preparing to unpack .../mariadb-server-10.1_10.1.20-3_amd64.deb ...
  invoke-rc.d: could not determine current runlevel
  Stopping MariaDB database server: mysqld.
  /var/lib/mysql: found previous version 10.1
  The file /var/lib/mysql/debian-10.1.flag indicates a
  version that cannot automatically be upgraded. Therefore the
  previous data directory will be renamed to /var/lib/mysql-10.1 and
  a new data directory will be initialized at /var/lib/mysql.
  Please manually export/import your data (e.g. with mysqldump) if needed.
  mv: cannot move '/var/lib/mysql' to '/var/lib/mysql-10.1/mysql': Directory 
not empty
  dpkg: error processing archive 
/var/cache/apt/archives/mariadb-server-10.1_10.1.20-3_amd64.deb (--unpack):
   subprocess new pre-installation script returned error exit status 1
  invoke-rc.d: could not determine current runlevel
  Stopping MariaDB database server: mysqld.
  invoke-rc.d: could not determine current runlevel
  Starting MariaDB database server: mysqld.
  Errors were encountered while processing:
   /var/cache/apt/archives/mariadb-server-10.1_10.1.20-3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
1m12.1s ERROR: Command failed (status=100): ['chroot', 
'/srv/piuparts.debian.org/tmp/tmpSyjHYx', 'apt-get', '-y', 'install', 
'--reinstall', 'mariadb-server-10.1=10.1.20-3']


cheers,

Andreas


mariadb-server-10.1_10.1.20-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: mariadb-10.1
Source-Version: 10.1.21-1

We believe that the bug you reported is fixed in the latest version of
mariadb-10.1, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Otto Kekäläinen  (supplier of updated mariadb-10.1 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Jan 2017 11:33:01 +0200
Source: mariadb-10.1
Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat 
libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.1 
mariadb-client-10.1 mariadb-server-core-10.1 mariadb-server-10.1 mariadb-server 
mariadb-client mariadb-plugin-connect mariadb-plugin-oqgraph 
mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider 
mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client 
mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source amd64 all
Version: 10.1.21-1
Distribution: unstable
Urgency: low
Maintainer: Debian MySQL Maintainers 
Changed-By: Otto Kekäläinen 
Description:
 libmariadbclient-dev - MariaDB database development files
 libmariadbclient-dev-compat - MariaDB database development files 

Bug#850216: marked as done (mysql-server-5.6: Listens on * by default after installation (related to use of alternatives))

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 19:39:21 +
with message-id 
and subject line Bug#850216: fixed in mariadb-10.1 10.1.21-1
has caused the Debian Bug report #850216,
regarding mysql-server-5.6: Listens on * by default after installation (related 
to use of alternatives)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
850216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mysql-5.6
Version: 5.6.30-1
Severity: grave
Tags: security
Justification: user security hole

Hi

When installing myssql-server-5.6 in stretch and sid, then mysqld is
started and listend not binding on localhost only, but listen on *.

tcpLISTEN 0  80 :::mysql:::*
 users:(("mysqld",pid=2810,fd=10))

This issue seems related to the switch to use the alternatives system for 
my.cnf, now mysql-5.6 as well picking the mariadb.cnf in auto mode.

That one includes

!includedir /etc/mysql/conf.d/
!includedir /etc/mysql/mariadb.conf.d/

and thus the installation ends without

bind-address= 127.0.0.1 

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mariadb-10.1
Source-Version: 10.1.21-1

We believe that the bug you reported is fixed in the latest version of
mariadb-10.1, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Otto Kekäläinen  (supplier of updated mariadb-10.1 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Jan 2017 11:33:01 +0200
Source: mariadb-10.1
Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat 
libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.1 
mariadb-client-10.1 mariadb-server-core-10.1 mariadb-server-10.1 mariadb-server 
mariadb-client mariadb-plugin-connect mariadb-plugin-oqgraph 
mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider 
mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client 
mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source amd64 all
Version: 10.1.21-1
Distribution: unstable
Urgency: low
Maintainer: Debian MySQL Maintainers 
Changed-By: Otto Kekäläinen 
Description:
 libmariadbclient-dev - MariaDB database development files
 libmariadbclient-dev-compat - MariaDB database development files 
(libmysqlclient compatibility)
 libmariadbclient18 - MariaDB database client library
 libmariadbd-dev - MariaDB embedded database, development files
 libmariadbd18 - MariaDB embedded database, shared library
 mariadb-client - MariaDB database client (metapackage depending on the latest 
vers
 mariadb-client-10.1 - MariaDB database client binaries
 mariadb-client-core-10.1 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-plugin-connect - Connect storage engine for MariaDB
 mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin 
for MariaDB
 mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client
 mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server
 mariadb-plugin-mroonga - Mroonga storage engine for MariaDB
 mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB
 mariadb-plugin-spider - Spider storage engine for MariaDB
 mariadb-plugin-tokudb - TokuDB storage engine for MariaDB
 mariadb-server - MariaDB database server (metapackage depending on the latest 
vers
 mariadb-server-10.1 - MariaDB database server binaries
 mariadb-server-core-10.1 - MariaDB database core server files
 mariadb-test - MariaDB database regression test suite
 mariadb-test-data - MariaDB database regression test suite - data files
Closes: 677223 850216 851131 851257 851759
Changes:
 mariadb-10.1 (10.1.21-1) unstable; urgency=low
 .
   [ Otto Kekäläinen ]
   * New upstream release 10.0.28. Includes fixes for the following
 security vulnerabilities (Closes: #851759, Closes: ##849435):
 - 

Bug#851015: nut: FTBFS: a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl

[Arnaud Quette]

Hi Michael,

No idea on the why and not much time to look at it before the week end.
Iirc, dblatex is listed for the manpages generation.

Feel free to upload a fix if you find one.

Thanks and cheers.
Arno

Le 19 janv. 2017 19:57, "Michael Stapelberg"  a
écrit :

> [+aquette, bigon directly]
>
> Are you aware of this issue? This RC bug transitively marked freeradius
> for removal from testing. If you need help, please let me know — I have
> some incentive to look into it in order to keep freeradius in stretch.
>
> Lucas Nussbaum  writes:
>
> > Source: nut
> > Version: 2.7.4-4
> > Severity: serious
> > Tags: stretch sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20170111 qa-ftbfs
> > Justification: FTBFS on amd64
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> >
> > Relevant part (hopefully):
> >> make[3]: Entering directory '/<>/docs'
> >> make[3]: Nothing to be done for 'all-am'.
> >> make[3]: Leaving directory '/<>/docs'
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=chunked_format --format=chunked --xsl-file=./chunked.xsl
> user-manual.txt
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=chunked_format --format=chunked --xsl-file=./chunked.xsl
> developer-guide.txt
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=chunked_format --format=chunked --xsl-file=./chunked.xsl
> packager-guide.txt
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=xhtml11_format --format=xhtml --xsl-file=./xhtml.xsl FAQ.txt
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=pdf_format --format=pdf -a docinfo1 user-manual.txt
> >> a2x: WARNING: --destination-dir option is only applicable to HTML based
> outputs
> >> a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/
> asciidoc-dblatex.xsl
> >> Makefile:825: recipe for target 'user-manual.pdf' failed
> >> make[2]: *** [user-manual.pdf] Error 1
> >
> > The full build log is available from:
> >http://aws-logs.debian.net/2017/01/11/nut_2.7.4-4_unstable.log
> >
> > A list of current common problems and possible solutions is available at
> > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to
> contribute!
> >
> > About the archive rebuild: The rebuild was done on EC2 VM instances from
> > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> > failed build was retried once to eliminate random failures.
> >
> >
>
> --
> Best regards,
> Michael
>

Bug#850716: XML External Entity attack

[Salvatore Bonaccorso]

Hi,

On Mon, Jan 09, 2017 at 04:28:40PM +0100, Thomas Goirand wrote:
> there was a security hole fixed in python-pysaml2, which allowed XML
> External Entity attacks:
> https://github.com/rohe/pysaml2/pull/379
> https://github.com/rohe/pysaml2/commit/6e09a25d9b4b7aa7a506853210a9a14100b8bc9b

Apparently there was some confusion. To be clear, the above commit now
after re-clarification from MITRE is CVE-2016-10149[1], which means
the initially assigned CVE for the XXE vulnerability in pysaml2 is
still unfixed. Will open another bug for it. See the comments in the
references oss-security post for details.

 [1] https://marc.info/?l=oss-security=148484731923389=2

Regards,
Salvatore

Bug#851015: nut: FTBFS: a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl

[Michael Stapelberg]

[+aquette, bigon directly]

Are you aware of this issue? This RC bug transitively marked freeradius
for removal from testing. If you need help, please let me know — I have
some incentive to look into it in order to keep freeradius in stretch.

Lucas Nussbaum  writes:

> Source: nut
> Version: 2.7.4-4
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170111 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
>> make[3]: Entering directory '/<>/docs'
>> make[3]: Nothing to be done for 'all-am'.
>> make[3]: Leaving directory '/<>/docs'
>> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet" --xsltproc-opts 
>> "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\"" --xsltproc-opts 
>> "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\"" --xsltproc-opts 
>> "--stringparam nut.nutversion \"2.7.4\"" --attribute iconsdir=./images 
>> --attribute=badges --attribute=external_title --attribute tree_version=2.7 
>> -a toc -a numbered --destination-dir=. --attribute=chunked_format 
>> --format=chunked --xsl-file=./chunked.xsl user-manual.txt
>> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet" --xsltproc-opts 
>> "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\"" --xsltproc-opts 
>> "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\"" --xsltproc-opts 
>> "--stringparam nut.nutversion \"2.7.4\"" --attribute iconsdir=./images 
>> --attribute=badges --attribute=external_title --attribute tree_version=2.7 
>> -a toc -a numbered --destination-dir=. --attribute=chunked_format 
>> --format=chunked --xsl-file=./chunked.xsl developer-guide.txt
>> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet" --xsltproc-opts 
>> "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\"" --xsltproc-opts 
>> "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\"" --xsltproc-opts 
>> "--stringparam nut.nutversion \"2.7.4\"" --attribute iconsdir=./images 
>> --attribute=badges --attribute=external_title --attribute tree_version=2.7 
>> -a toc -a numbered --destination-dir=. --attribute=chunked_format 
>> --format=chunked --xsl-file=./chunked.xsl packager-guide.txt
>> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet" --xsltproc-opts 
>> "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\"" --xsltproc-opts 
>> "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\"" --xsltproc-opts 
>> "--stringparam nut.nutversion \"2.7.4\"" --attribute iconsdir=./images 
>> --attribute=badges --attribute=external_title --attribute tree_version=2.7 
>> -a toc -a numbered --destination-dir=. --attribute=xhtml11_format 
>> --format=xhtml --xsl-file=./xhtml.xsl FAQ.txt
>> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet" --xsltproc-opts 
>> "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\"" --xsltproc-opts 
>> "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\"" --xsltproc-opts 
>> "--stringparam nut.nutversion \"2.7.4\"" --attribute iconsdir=./images 
>> --attribute=badges --attribute=external_title --attribute tree_version=2.7 
>> -a toc -a numbered --destination-dir=. --attribute=pdf_format --format=pdf 
>> -a docinfo1 user-manual.txt
>> a2x: WARNING: --destination-dir option is only applicable to HTML based 
>> outputs
>> a2x: ERROR: missing configuration file: 
>> /etc/asciidoc/dblatex/asciidoc-dblatex.xsl
>> Makefile:825: recipe for target 'user-manual.pdf' failed
>> make[2]: *** [user-manual.pdf] Error 1
>
> The full build log is available from:
>http://aws-logs.debian.net/2017/01/11/nut_2.7.4-4_unstable.log
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
>
>

-- 
Best regards,
Michael

Bug#848234: marked as done (txwinrm,winrm: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 18:34:45 +
with message-id 
and subject line Bug#848234: fixed in golang-github-masterzen-winrm 
0.0~git20160323.0752679-2
has caused the Debian Bug report #848234,
regarding txwinrm,winrm: error when trying to install together
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
848234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: txwinrm,winrm
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 0.0~git20160323.0752679-1
Control: found -1 1.1.28-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package winrm.
  Preparing to unpack .../winrm_0.0~git20160323.0752679-1_amd64.deb ...
  Unpacking winrm (0.0~git20160323.0752679-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/winrm_0.0~git20160323.0752679-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/winrm', which is also in package txwinrm 
1.1.28-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/winrm_0.0~git20160323.0752679-1_amd64.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/bin/winrm

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


txwinrm=1.1.28-1_winrm=0.0~git20160323.0752679-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: golang-github-masterzen-winrm
Source-Version: 0.0~git20160323.0752679-2

We believe that the bug you reported is fixed in the latest version of
golang-github-masterzen-winrm, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 848...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Stender  (supplier of updated 
golang-github-masterzen-winrm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Jan 2017 18:59:25 +0100
Source: golang-github-masterzen-winrm
Binary: golang-github-masterzen-winrm-dev winrm
Architecture: source all amd64
Version: 0.0~git20160323.0752679-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Daniel Stender 
Description:
 golang-github-masterzen-winrm-dev - Windows remote command execution library 
for Go
 winrm  - tool for remote command execution on Windows machines
Closes: 848234
Changes:
 golang-github-masterzen-winrm (0.0~git20160323.0752679-2) unstable; 
urgency=medium
 .
   * solve binaries-have-conflict with txwinrm (Closes: #848234):
 + rename /usr/bin/winrm via override for dh_install in deb/rules.
 + add debian/winrm.NEWS with info on that change.
 + updated manpage.
   * deb/control:
 + corrected description text.
 + bumped 

Processed: retitle 850716 to python-pysaml2: CVE-2016-10149

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 850716 python-pysaml2: CVE-2016-10149
Bug #850716 {Done: Thomas Goirand } [src:python-pysaml2] 
python-pysaml2: CVE-2016-10127: XML External Entity attack
Changed Bug title to 'python-pysaml2: CVE-2016-10149' from 'python-pysaml2: 
CVE-2016-10127: XML External Entity attack'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
850716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#830399: marked as done (python-jedi: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 18:36:15 +
with message-id 
and subject line Bug#830399: fixed in python-jedi 0.10.0~git1+f05c071-1
has caused the Debian Bug report #830399,
regarding python-jedi: FTBFS: dh_auto_test: pybuild --test -i python{version} 
-p 2.7 returned exit code 13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
830399: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-jedi
Version: 0.9.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi
> copying jedi/common.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi
> copying jedi/settings.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi
> copying jedi/refactoring.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi
> copying jedi/cache.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi
> copying jedi/utils.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi
> copying jedi/__init__.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi
> copying jedi/debug.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi
> copying jedi/_compatibility.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi
> copying jedi/__main__.py -> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/parser
> copying jedi/parser/__init__.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/parser
> copying jedi/parser/tree.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/parser
> copying jedi/parser/user_context.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/parser
> copying jedi/parser/fast.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/parser
> copying jedi/parser/token.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/parser
> copying jedi/parser/tokenize.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/parser
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/parser/pgen2
> copying jedi/parser/pgen2/grammar.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/parser/pgen2
> copying jedi/parser/pgen2/pgen.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/parser/pgen2
> copying jedi/parser/pgen2/__init__.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/parser/pgen2
> copying jedi/parser/pgen2/parse.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/parser/pgen2
> creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/evaluate
> copying jedi/evaluate/docstrings.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/evaluate
> copying jedi/evaluate/stdlib.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/evaluate
> copying jedi/evaluate/cache.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/evaluate
> copying jedi/evaluate/iterable.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/evaluate
> copying jedi/evaluate/recursion.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/evaluate
> copying jedi/evaluate/sys_path.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/evaluate
> copying jedi/evaluate/precedence.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/evaluate
> copying jedi/evaluate/dynamic.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/evaluate
> copying jedi/evaluate/__init__.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/evaluate
> copying jedi/evaluate/helpers.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/evaluate
> copying jedi/evaluate/imports.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/evaluate
> copying jedi/evaluate/param.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/evaluate
> copying jedi/evaluate/flow_analysis.py -> 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/jedi/evaluate
> copying 

Bug#848234: txwinrm,winrm: error when trying to install together

[Daniel Stender]

On Thu, 5 Jan 2017 21:40:12 + Christopher Hoskin 
 wrote:
> Dear Dan,
> 
> Thanks for getting in touch - sorry for not replying sooner. "winrm"
> is the name of a Microsoft Windows command, so users might expect a
> Linux command with the same name to perform a similar function. I'm
> not familiar with what the command in your package does, and it's a
> while since I did the original txwinrm packaging so I'm not sure off
> hand which of our commands is closer to the Windows winrm.
> 
> I'll try to find some time in the next week or so to refresh my memory
> of the details, and consider what an appropriate name for the command
> in my package would be.
> 
> Hope that's soon enough?
> 
> Thanks.
> 
> Christopher

... I've cleared that problem now by renaming the binary in my package.

Please add a Conflicts against winrm_0.0~git20160323.0752679-1.

DS

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/

Bug#851901: aptitude: "E: Internal Error, No file name for apt-build:amd64" after failed reinstallation of apt-build, then endless loop "Can't find a source to download version '0.12.46'" in TUI after

[Axel Beckert]

Hi,

Axel Beckert wrote:
> Will now try to get out of that mess. Will post it here, once I
> found a way out of this state.

"aptitude keep apt-build" on the commandline at least got me out of
the endless loop in the TUI.

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

Processed: limit source to gnome-shell, tagging 844796

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source gnome-shell
Limiting to bugs with field 'source' containing at least one of 'gnome-shell'
Limit currently set to 'source':'gnome-shell'

> tags 844796 + pending
Bug #844796 [src:gnome-shell] gnome-shell: FTBFS: 
/<>/src/tmp-introspect2qs0g0tu/.libs/ShellMenu-0.1: error while 
loading shared libraries: libmutter-clutter-1.0.so: cannot open shared object 
file: No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
844796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851892: To tight permissions on /dev/ptmx

[Thorsten Glaser]

James Clarke dixit:

>#817236 strikes again; the thread there has various workarounds.

Why is this still not fixed in debootstrap, anyway?

Thanks,
//mirabilos
-- 
> Wish I had pine to hand :-( I'll give lynx a try, thanks.

Michael Schmitz on nntp://news.gmane.org/gmane.linux.debian.ports.68k
a.k.a. {news.gmane.org/nntp}#news.gmane.linux.debian.ports.68k in pine

Bug#851612: marked as done (opus: CVE-2017-0381: Memory corruption during media file and data processing)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 17:49:05 +
with message-id 
and subject line Bug#851612: fixed in opus 1.2~alpha2-1
has caused the Debian Bug report #851612,
regarding opus: CVE-2017-0381: Memory corruption during media file and data 
processing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opus
Version: 1.1-2
Severity: grave
Tags: upstream security patch
Justification: user security hole

Hi,

the following vulnerability was published for opus.

CVE-2017-0381[0]:
Memory corruption during media file and data processing

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-0381
[1] https://github.com/xiph/opus/commit/79e8f527b0344b0897a65be35e77f7885bd99409

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: opus
Source-Version: 1.2~alpha2-1

We believe that the bug you reported is fixed in the latest version of
opus, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ron Lee  (supplier of updated opus package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 20 Jan 2017 02:48:31 +1030
Source: opus
Binary: libopus0 libopus-dev libopus-dbg libopus-doc
Architecture: source amd64 all
Version: 1.2~alpha2-1
Distribution: unstable
Urgency: medium
Maintainer: Ron Lee 
Changed-By: Ron Lee 
Description:
 libopus-dbg - debugging symbols for libopus
 libopus-dev - Opus codec library development files
 libopus-doc - libopus API documentation
 libopus0   - Opus codec runtime library
Closes: 851612
Changes:
 opus (1.2~alpha2-1) unstable; urgency=medium
 .
   * Run the tonality analysis at 24 kHz, which reduces complexity while giving
 better frequency resolution for the tonality estimate.
   * Speech quality improvements especially in the 12-20 kbit/s range.
   * Improved VBR encoding for hybrid mode.
   * More aggressive use of wider speech bandwidth, including fullband speech
 starting at 14 kbit/s.
   * Music quality improvements in the 32-48 kb/s range.
   * Generic and SSE CELT optimizations.
   * Support for directly encoding packets up to 120 ms.
   * DTX support for CELT mode.
   * SILK CBR improvements.
   * Ensure that NLSF cannot be negative when computing a min distance between
 them.  This was reported and fixed in July, and assessed as having only a
 relatively minor impact (garbage output, from the garbage input needed to
 trigger it), or at very worst, an assertion failure or simple crash from
 a slightly out of bounds read.  In December it was assigned CVE-2017-0381
 by someone other than the upstream developers, with claims of it being a
 'Critical' issue on Android, but we're yet to see any analysis to back
 that up.  Closes: #851612
Checksums-Sha1:
 943e4d3250ef57f3214a4f330eaf32067069d08d 1967 opus_1.2~alpha2-1.dsc
 ee80d7823dadea7036a7589d5a5faca182b9b87d 1021012 opus_1.2~alpha2.orig.tar.gz
 5b19cc0c72dba9508a18640fef677705ae6c1db4 7445 opus_1.2~alpha2-1.diff.gz
 5d751953518498d059cf26c1c40b2eb916251e80 350212 
libopus-dbg_1.2~alpha2-1_amd64.deb
 80c9564f2292584eae4ef0e669b7a57cf8d8548f 212298 
libopus-dev_1.2~alpha2-1_amd64.deb
 620237e051be6e3c6c4c687f0d76cbeb5b316c20 194618 
libopus-doc_1.2~alpha2-1_all.deb
 de3120acc49728d43140587bf16509fd394ed764 170836 libopus0_1.2~alpha2-1_amd64.deb
 d593e09d1960621eac80da3057132b64eccc4b5b 7385 opus_1.2~alpha2-1_amd64.buildinfo
Checksums-Sha256:
 1b281c14f23ff5336f2edfc07181ae9a6d358a72162598589fec609df83d9de6 1967 
opus_1.2~alpha2-1.dsc
 148d38cd0a19e0dde7f7e5491c19953025ff4e7e172e7b21fcf7ba3ff84fa06e 1021012 
opus_1.2~alpha2.orig.tar.gz
 0bc67d52b0d1de2836390e267240c4bd998c5985e34a71d03ba3f57d7668a219 7445 
opus_1.2~alpha2-1.diff.gz
 

Bug#851901: aptitude: "E: Internal Error, No file name for apt-build:amd64" after failed reinstallation of apt-build, then endless loop "Can't find a source to download version '0.12.46'" in TUI after

[Axel Beckert]

Package: aptitude
Version: 0.8.4-1
Severity: serious
Justification: Maintainer's opinion

Hi,

to reproduce https://bugs.debian.org/851814, I pressed L on apt-build in
aptitude's TUI. As expected the configuration of the reinstalled package
failed. So far no problem.

But afterwards, when I want to install or upgrade other packages with
aptitude, aptitude always aborts with "E: Internal Error, No file name
for apt-build:amd64", be it from TUI or CLI:

# aptitude install
The following packages will be REINSTALLED:
  apt-build 
The following packages will be REMOVED:
  liblircclient0{pu} libmediaart-2.0-0{pu} 
The following packages will be upgraded:
  cvsps docutils-common fbtv ftp-ssl gdb libllvm4.0 libtracker-sparql-1.0-0 pia 
python-docutils python3-docutils scantv tcsh ttv v4l-conf xawtv 
  xawtv-plugins 
The following packages are RECOMMENDED but will NOT be installed:
  docutils-doc 
16 packages upgraded, 0 newly installed, 1 reinstalled, 2 to remove and 1 not 
upgraded.
Need to get 0 B/17.9 MB of archives. After unpacking 13.3 kB will be used.
Do you want to continue? [Y/n/?] y
E: Internal Error, No file name for apt-build:amd64

So far this wouldn't go for "serious", just for "important".

But I then tried to fix this by installing apt-build 0.12.46 which fixes
#851814 and which I'm about to upload.

But then it got worse:

# aptitude install
The following packages will be REINSTALLED:
  apt-build 
The following packages will be REMOVED:
  liblircclient0{pu} libmediaart-2.0-0{pu} 
The following packages will be upgraded:
  cvsps docutils-common fbtv ftp-ssl gdb libllvm4.0 libtracker-sparql-1.0-0 pia 
python-docutils python3-docutils scantv tcsh ttv v4l-conf xawtv 
  xawtv-plugins 
The following packages are RECOMMENDED but will NOT be installed:
  docutils-doc 
16 packages upgraded, 0 newly installed, 1 reinstalled, 2 to remove and 1 not 
upgraded.
E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'
After unpacking 13.3 kB will be used.
Do you want to continue? [Y/n/?] y
E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'
E: Internal error: couldn't generate list of packages to download
E: Perhaps the package lists are out of date, please try 'aptitude update' (or 
equivalent) first

(The suggested "aptitude update" didn't help at all.)

That's ok-ish on the CLI, but on the TUI I got an endless loop (and 100%
CPU usage) directly after starting the TUI without hitting any key since
aptitude started:

┌─┐B
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   #│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│E: Can't find a source to download version '0.12.46' of 'apt-build:amd64'   ▒│ 
│   [ Ok ]│ 
└─┘ 

If I press Enter to acknowledge the messages, a new such dialog pops up
immediately and fills up again with the same messages. No chance to use
the TUI in this state. Only Ctrl-C helps.

How to probably reproduce:

Use a clean jessie chroot. Install apt-build (should get you
0.12.45). Use snapshot.debian.org to replace the jessie sources.list
entries with sources.list entries showing the state of the repository on
late 18th of January 2017 with sed 4.3-3, but still with 

Processed: Re: Bug#851892: To tight permissions on /dev/ptmx

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 debootstrap
Bug #851892 [cowbuilder] Too tight permissions on /dev/ptmx
Bug reassigned from package 'cowbuilder' to 'debootstrap'.
No longer marked as found in versions cowdancer/0.83.
Ignoring request to alter fixed versions of bug #851892 to the same values 
previously set
> forcemerge 817236 -1
Bug #817236 [debootstrap] schroot: no access to pseudo-terminals in new chroots
Bug #841935 [debootstrap] pbuilder: incorrect permissions on /dev/ptmx breaks 
openpty()
Bug #849168 [debootstrap] pbuilder: Expect programe reported "no more ptys" and 
failed in rebuilding gcc with normal (non-root) user
Bug #851892 [debootstrap] Too tight permissions on /dev/ptmx
Severity set to 'serious' from 'normal'
829299 was blocked by: 849168 817236 841935
829299 was not blocking any bugs.
Added blocking bug(s) of 829299: 851892
Outlook recorded from message bug 851892 message 
Added indication that 851892 affects pbuilder,sbuild,schroot
Marked as found in versions debootstrap/1.0.87 and debootstrap/1.0.85.
Added tag(s) patch.
Bug #841935 [debootstrap] pbuilder: incorrect permissions on /dev/ptmx breaks 
openpty()
Bug #849168 [debootstrap] pbuilder: Expect programe reported "no more ptys" and 
failed in rebuilding gcc with normal (non-root) user
Merged 817236 841935 849168 851892

-- 
817236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817236
829299: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829299
841935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841935
849168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849168
851892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851497: marked as done (hashcat builds with -march=native)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 17:18:29 +
with message-id 
and subject line Bug#851497: fixed in hashcat 3.30-1
has caused the Debian Bug report #851497,
regarding hashcat builds with -march=native
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hashcat
Version: 3.20-1
Severity: grave

src/Makefile sets -march=native

This means the code will only run on machines with a CPU
compatible with the one on the machine where the package
was built.

Building on a different buildd machine can also change
where the code can run - including breaking existing
setups in stable updates.

Please remove -march=native from src/Makefile
--- End Message ---
--- Begin Message ---
Source: hashcat
Source-Version: 3.30-1

We believe that the bug you reported is fixed in the latest version of
hashcat, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated hashcat package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Jan 2017 18:00:19 +0100
Source: hashcat
Binary: hashcat hashcat-data
Architecture: source
Version: 3.30-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools Packaging Team 

Changed-By: Raphaël Hertzog 
Description:
 hashcat- World's fastest and most advanced password recovery utility
 hashcat-data - Data files for hashcat advanced password recovery utility
Closes: 851497
Changes:
 hashcat (3.30-1) unstable; urgency=medium
 .
   [ Samuel Henrique ]
   * Team upload.
   * New upstream version 3.30.
   * wrap-and-sort -a.
   * d/rules: Remove trailing whitespace.
   * d/copyright: Update copyright.
   * d/patches:
 - add_kfreebsd_support.diff: Update and Refresh.
 - fix_makefile.patch: Refresh.
 .
   [ Lorenzo "Palinuro" Faletra ]
   * Include libhashcat.so in hashcat binary package.
 .
   [ Raphaël Hertzog ]
   * Install libhashcat.so in /usr/lib/hashcat. It's not clean enough
 to be supported as a public library.
   * Drop -march=native from the Makefile. Closes: #851497
Checksums-Sha1:
 54167c9afd85c9bfb00e565fb8167e21100afe45 1737 hashcat_3.30-1.dsc
 0ce33d20dbfd8a7c65939324e32f30cc23f686d1 3970278 hashcat_3.30.orig.tar.gz
 1daf5a60c3ac9057fa55b1193a80b0c57c2a25ff 10328 hashcat_3.30-1.debian.tar.xz
Checksums-Sha256:
 97f8075feee2ae3a927cc3d7ae6ff700700c52fbb4373ab302bcfe8b9647e34b 1737 
hashcat_3.30-1.dsc
 3acd1d783f13183c57383069403de0554534ac2b06a30e7e078544e524f940d2 3970278 
hashcat_3.30.orig.tar.gz
 c179a5417ff3df8792ed4caa0ad970fbac254b90ddc332f8401d47d2a8a82665 10328 
hashcat_3.30-1.debian.tar.xz
Files:
 328c2adc7ba5ccf95b97601e0234c260 1737 net optional hashcat_3.30-1.dsc
 7f5682ddad66bd46972d07e1f2c00fa0 3970278 net optional hashcat_3.30.orig.tar.gz
 91178d14e42152c6fae67a85d2e5b6c3 10328 net optional 
hashcat_3.30-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAliA8TUACgkQA4gdq+vC
mrmR5wgAhurWRT+A+nOZOb4pdq6fp2Tsmo00f9+AOaMnykhl8pia0jXLsckc9y3P
nVXgrX74NLdRlgYszfZ8y2kjR0i7Qo+ySCDsXkJOMASsBMg0VnrZzk8y02TQ5PL+
6mFinUb3sO1AAfDSM/g1UbVIsxsOQLsXYr+mSxVBh3xiF0YyZyg80GyifFS6i5br
etkdMwPMPXOJY/mj9cWa0ufemp3h2syjGcdX6TGA6fOSdoieeqKWnRQnxhJlMOlJ
2MkZH6lHFUysFNZkCZVx2P69YigwKnh9DyIUU0xl/4uNcRnIePoI7xsHpQWJzBlu
CO+gXirrvSNSp4sjbnpe3qnQbw1p0w==
=kDaQ
-END PGP SIGNATURE End Message ---

Processed: Bug#851497 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 851497 pending
Bug #851497 [src:hashcat] hashcat builds with -march=native
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
851497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851497: marked as pending

[Raphaël Hertzog]

tag 851497 pending
thanks

Hello,

Bug #851497 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-security/hashcat.git;a=commitdiff;h=599a01d

---
commit 599a01d1ad38c632f902e27a204c52d4e9f6584a
Author: Raphaël Hertzog 
Date:   Thu Jan 19 17:10:32 2017 +0100

Install libhashcat.so in /usr/lib/hashcat

It's not clean enough to be supported as a public library.

Also drop -march=native from the Makefile. Closes: #851497

diff --git a/debian/changelog b/debian/changelog
index a78fb0a..240ab0a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -13,6 +13,11 @@ hashcat (3.30-1) UNRELEASED; urgency=medium
   [ Lorenzo "Palinuro" Faletra ]
   * Include libhashcat.so in hashcat binary package.
 
+  [ Raphaël Hertzog ]
+  * Install libhashcat.so in /usr/lib/hashcat. It's not clean enough
+to be supported as a public library.
+  * Drop -march=native from the Makefile. Closes: #851497
+
  -- Samuel Henrique   Sat, 07 Jan 2017 14:55:20 -0200
 
 hashcat (3.20-1) unstable; urgency=medium

Bug#851046: marked as done (tcsh FTBFS: 122. lexical.at:551: testing Quoting of expansions in `...` ... FAILED)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 17:02:38 +
with message-id <20170119170238.626b2wdzvt4he...@perpetual.pseudorandom.co.uk>
and subject line Re: Bug#851046: tcsh: FTBFS: | ./conftest.c:20: undefined 
reference to `crypt'
has caused the Debian Bug report #851046,
regarding tcsh FTBFS: 122. lexical.at:551: testing Quoting of expansions in 
`...` ... FAILED
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tcsh
Version: 6.20.00-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> {\
>   echo '# Signature of the current package.';\
>   echo 'm4_define([AT_PACKAGE_NAME],  [tcsh])';  \
>   echo 'm4_define([AT_PACKAGE_TARNAME],   [tcsh])';   \
>   echo 'm4_define([AT_PACKAGE_VERSION],   [6.20.00])';   \
>   echo 'm4_define([AT_PACKAGE_STRING],[tcsh 6.20.00])';  \
>   echo 'm4_define([AT_PACKAGE_BUGREPORT], [http://bugs.gw.com/])'; \
> } >./tests/package.m4
> autom4te --language=autotest -I ./tests \
>   ./tests/testsuite.at -o tests/testsuite.tmp
> mv tests/testsuite.tmp tests/testsuite
> /bin/sh ./tests/testsuite
> ##  ##
> ## tcsh 6.20.00 test suite. ##
> ##  ##
>   1: beepcmd skipped (aliases.at:3)
>   2: cwdcmd  ok
>   3: jobcmd  skipped (aliases.at:19)
>   4: helpcommand skipped (aliases.at:20)
>   5: periodicskipped (aliases.at:21)
>   6: precmd  skipped (aliases.at:22)
>   7: postcmd ok
>   8: shell   ok
>   9: -b  ok
>  10: -c  ok
>  11: -d  skipped (arguments.at:34)
>  12: -e  ok
>  13: -f  skipped (arguments.at:46)
>  14: -i  ok
>  15: -l  skipped (arguments.at:61)
>  16: -m  skipped (arguments.at:65)
>  17: -q  skipped (arguments.at:71)
>  18: -s  ok
>  19: -t  ok
>  20: -v  ok
>  21: -x  ok
>  22: -V  skipped 
> (arguments.at:126)
>  23: -X  skipped 
> (arguments.at:127)
>  24: --help  skipped 
> (arguments.at:130)
>  25: --version   skipped 
> (arguments.at:131)
>  26: invalid option  ok
>  27: non-option argumentsok
>  28: %   skipped (commands.at:3)
>  29: :   ok
>  30: @   ok
>  31: alias   ok
>  32: alloc   skipped (commands.at:80)
>  33: bg  skipped (commands.at:81)
>  34: bindkey skipped (commands.at:82)
>  35: break   ok
>  36: builtinsskipped (commands.at:133)
>  37: bye skipped (commands.at:134)
>  38: cd  ok
>  39: completeok
>  40: continueok
>  41: dirsok
>  42: echook
>  43: echotc  skipped (commands.at:348)
>  

Processed: gnuvd defunct

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 767076 grave
Bug #767076 [gnuvd] gnuvd not able to search for words
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
767076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851046: marked as done (tcsh FTBFS: 122. lexical.at:551: testing Quoting of expansions in `...` ... FAILED)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 17:29:05 +0100
with message-id <22656.59729.116219.899...@paeffgen.informatik.uni-koeln.de>
and subject line Re: Bug#851046: tcsh: FTBFS: | ./conftest.c:20: undefined 
reference to `crypt'
has caused the Debian Bug report #851046,
regarding tcsh FTBFS: 122. lexical.at:551: testing Quoting of expansions in 
`...` ... FAILED
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tcsh
Version: 6.20.00-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> {\
>   echo '# Signature of the current package.';\
>   echo 'm4_define([AT_PACKAGE_NAME],  [tcsh])';  \
>   echo 'm4_define([AT_PACKAGE_TARNAME],   [tcsh])';   \
>   echo 'm4_define([AT_PACKAGE_VERSION],   [6.20.00])';   \
>   echo 'm4_define([AT_PACKAGE_STRING],[tcsh 6.20.00])';  \
>   echo 'm4_define([AT_PACKAGE_BUGREPORT], [http://bugs.gw.com/])'; \
> } >./tests/package.m4
> autom4te --language=autotest -I ./tests \
>   ./tests/testsuite.at -o tests/testsuite.tmp
> mv tests/testsuite.tmp tests/testsuite
> /bin/sh ./tests/testsuite
> ##  ##
> ## tcsh 6.20.00 test suite. ##
> ##  ##
>   1: beepcmd skipped (aliases.at:3)
>   2: cwdcmd  ok
>   3: jobcmd  skipped (aliases.at:19)
>   4: helpcommand skipped (aliases.at:20)
>   5: periodicskipped (aliases.at:21)
>   6: precmd  skipped (aliases.at:22)
>   7: postcmd ok
>   8: shell   ok
>   9: -b  ok
>  10: -c  ok
>  11: -d  skipped (arguments.at:34)
>  12: -e  ok
>  13: -f  skipped (arguments.at:46)
>  14: -i  ok
>  15: -l  skipped (arguments.at:61)
>  16: -m  skipped (arguments.at:65)
>  17: -q  skipped (arguments.at:71)
>  18: -s  ok
>  19: -t  ok
>  20: -v  ok
>  21: -x  ok
>  22: -V  skipped 
> (arguments.at:126)
>  23: -X  skipped 
> (arguments.at:127)
>  24: --help  skipped 
> (arguments.at:130)
>  25: --version   skipped 
> (arguments.at:131)
>  26: invalid option  ok
>  27: non-option argumentsok
>  28: %   skipped (commands.at:3)
>  29: :   ok
>  30: @   ok
>  31: alias   ok
>  32: alloc   skipped (commands.at:80)
>  33: bg  skipped (commands.at:81)
>  34: bindkey skipped (commands.at:82)
>  35: break   ok
>  36: builtinsskipped (commands.at:133)
>  37: bye skipped (commands.at:134)
>  38: cd  ok
>  39: completeok
>  40: continueok
>  41: dirsok
>  42: echook
>  43: echotc  skipped (commands.at:348)
>  44: 

Bug#851893: The availability of update-grub does not imply that GRUB is used

[Alexander Kurtz]

Package: desktop-base
Version: 9.0.0
Severity: serious
Justification: Package fails to install because of this

Hi!

People who want to have the GRUB binaries installed (for example to
create VM images with GRUB), but don't want to use GRUB as their
bootloader will (in the case of classic PCs) have the grub-pc-bin [0]
and grub2-common [1] packages installed, but not the grub-pc [2]
package as this contains the scripts for the automatic installation.

This works fine, but unfortunately, desktop-base's postinst contains
the following code:

   202  # Apply GRUB background update into /boot
   203  if which update-grub > /dev/null ; then
   204  # Ensure the background image file has actually been written to 
disc
   205  # before updating.
   206  sync
   207  update-grub
   208  fi

Since update-grub is shipped by the grub2-common package (see [3]),
this test is wrong. The fact that update-grub is available does not
imply that the system uses GRUB to boot. Since update-grub will
obviously fail to run if GRUB is not installed to /boot, this bug
causes desktop-base's postinst to fail, making the package
uninstallable on such systems.

Best regards

Alexander Kurtz

[0] https://packages.debian.org/sid/grub-pc-bin
[1] https://packages.debian.org/sid/grub2-common
[2] https://packages.debian.org/sid/grub-pc
[3] https://packages.debian.org/sid/amd64/grub2-common/filelist

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

Bug#851817: [pkg-go] Bug#851817: Vendoring libraries

[Martín Ferrari]

severity 851817 normal
thanks

Hi,

On 18/01/17 22:15, Haruki TSURUMOTO wrote:

> Dear maintainers,
> Prometheus depends on many libraries, including source codes located
> into vendor directory.
> Is this a violation for Debian Policy 4.13 ?
> "4.13 Convenience copies of code"
> https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles
> 
> Some libraries of vendor/*  had already packaged in Debian,
>  (ex: golang-github-hashicorp-go-cleanhttp-dev,
> golang-github-hashicorp-consul-dev)
> Can't we use these instead of vendoring method ?

When I packaged the prometheus ecosystem, most of the vendored
dependencies were not present in Debian. I packaged about 30 different
libraries to remove vendoring and left just a couple of them. There were
a couple of libs that were just too small and specific to justify
separate packages (not used directly by prometheus), and in the case of
the consul API because there is an API incompatibility with the package
present in Debian.

I will review this to see again if the vendoring can be removed. But I
disagree with the severity of this bug, the policy only marks this
requirement as a "should", so it is not serious.


-- 
Martín Ferrari (Tincho)

Processed: Re: [pkg-go] Bug#851817: Vendoring libraries

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 851817 normal
Bug #851817 [prometheus] Vendoring libraries
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
851817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#838665: /usr/lib/python3/dist-packages/speechd_config/config.py: runs argparse on Python module import

[Sebastian Humenda]

Hi

Adrian Bunk schrieb am 18.01.2017, 20:34 +0200:
>On Mon, Sep 26, 2016 at 02:16:45PM +0200, Sebastian Humenda wrote:
>> I'll provide a patch to upstream shortly and attach it here as well, so that 
>> it
>> is fixed both upstream and downstream.
>
>any news regarding that?
Well, I had intended to attach the patch to my previous email, but forgot it, so
the downstream patch is gone. Upstream told me two days ago, that the patch
wouldn't fully work. I'm awaiting details on this and then backport the patch
again.

Thanks
Sebastian


signature.asc
Description: PGP signature

Bug#851812: marked as done (seed-webkit2 autoreconf FTBFS)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 17:24:55 +0100
with message-id <7dfb33e9-545a-fba8-f9a5-de5b2e199...@collabora.co.uk>
and subject line Re: seed-webkit2 autoreconf FTBFS
has caused the Debian Bug report #851812,
regarding seed-webkit2 autoreconf FTBFS
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: seed-webkit2
Version: 4.0.0+20161014+6c77960+dfsg1-3
Severity: serious

https://buildd.debian.org/status/package.php?p=seed-webkit2=sid

...
set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
--copyright --deb-fmt --ignore 
'^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
/bin/sh: 1: /usr/bin/licensecheck: not found
0 combinations of copyright and licensing found.
diff: debian/copyright_hints: No such file or directory
No new copyright notices found - assuming no news is good news...
touch debian/stamp-copyright-check
touch debian/stamp-upstream-cruft
dh_autoreconf debian/rules -- autoreconf
make[1]: Entering directory 
'/«BUILDDIR»/seed-webkit2-4.0.0+20161014+6c77960+dfsg1'
CDBS WARNING:  copyright-check disabled - touch debian/copyright_hints to 
enable.
./autogen.sh
You need to install gnome-common from GNOME SVN and make
sure the gnome-autogen.sh script is in your $PATH.
debian/rules:15: recipe for target 'autoreconf' failed
make[1]: *** [autoreconf] Error 1
--- End Message ---
--- Begin Message ---
Control: fixed -1 4.0.0+20161014+6c77960+dfsg1-4

Fixed in the last upload.

-- 
Cheers,
  Andrew--- End Message ---

Bug#851649: [Python-modules-team] Bug#851649: python-webob: This version causes FTBFS of six OpenStack packages due backwards incompatibility

[Ondřej Kobližek]

forcemerge 851649 851044 851032 851045 850990 850987 851027 849591

thanks

Merge bugs after rollback to python-webob/1:1.6.2-1

Processed (with 1 error): Re: [Python-modules-team] Bug#851649: python-webob: This version causes FTBFS of six OpenStack packages due backwards incompatibility

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 851649 851044 851032 851045 850990 850987 851027 849591
Bug #851649 [src:python-webob] python-webob: This version causes FTBFS of six 
OpenStack packages due backwards incompatibility
Unable to merge bugs because:
package of #851044 is 'src:glance' not 'src:python-webob'
package of #851032 is 'src:gnocchi' not 'src:python-webob'
package of #850987 is 'src:python-keystonemiddleware' not 'src:python-webob'
package of #851027 is 'src:python-oslo.middleware' not 'src:python-webob'
package of #850990 is 'src:nova' not 'src:python-webob'
package of #851045 is 'src:keystone' not 'src:python-webob'
Failed to forcibly merge 851649: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
849591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849591
850987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850987
850990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850990
851027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851027
851032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851032
851044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851044
851045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851045
851649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Processed (with 1 error): Re: Bug#794466: (no subject)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 794466 - src:virtualbox-guest-additions-isothanks
Bug #794466 [src:virtualbox] Virtualbox might not be suitable for Stretch
Removed indication that 794466 affects src:virtualbox-guest-additions-isothanks
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
794466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): Re: Bug#794466: (no subject)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 794466 src:virtualbox-guest-additions-isothanks
Bug #794466 [src:virtualbox] Virtualbox might not be suitable for Stretch
Added indication that 794466 affects src:virtualbox-guest-additions-isothanks
> Il Giovedì 19 Gennaio 2017 17:00, Gianfranco Costamagna 
>  ha scritto:
Unknown command or malformed arguments to command.
> affects 794466 src:virtualbox-guest-additions-iso
Bug #794466 [src:virtualbox] Virtualbox might not be suitable for Stretch
Added indication that 794466 affects src:virtualbox-guest-additions-iso
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
794466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#794466: (no subject)

[Gianfranco Costamagna]

affects 794466 src:virtualbox-guest-additions-iso
thanks



signature.asc
Description: OpenPGP digital signature

Bug#850216: [debian-mysql] Bug#850216: Bug#850216: Bug#850216: mysql-server-5.6: Listens on * by default after installation (related to use of alternatives)

[Robie Basak]

Hi Otto,

On Sun, Jan 15, 2017 at 09:33:24PM +0200, Otto Kekäläinen wrote:
> 2017-01-13 13:18 GMT+02:00 Robie Basak :
> > So I think the configure-symlinks code needs to move from mariadb-common
> > to mariadb-server-10.1 in addition.
> 
> The MariaDB client programs might also have MariaDB specific
> configuration lines, which according to this new config scheme should
> be placed in /etc/mysql/mariadb.cnf.d/, and for them to be read,
> mariadb-common must control the configure-symlinks.

OK.

> Maybe we should mark both the client and server packages to conflict
> each other, and for mariadb-common to conflict on mysql-client and
> mysql-server?

I think your statement above means that this must happen. Anything that
requires a custom /etc/mysql/my.cnf (rather than the generic one
provided in src:mysql-defaults) necessarily *must* conflict with
anything else that requires a different custom /etc/mysql/my.cnf.

I wonder if we should have both mariadb-common and mysql-server-5.7 (ie.
everything that asks for a custom my.cnf symlink) declare a virtual
package? So add:

  Provides: mysql-my-cnf
  Conflicts: mysql-my-cnf

to both mariadb-common and to mysql-server-5.7.

To be clear, mysql-common would not change. It would continue to provide
the "default" symlink for my.cnf for packages that want them, and we
should continue to negotiate any changes needed to that.

The rule would be: any package that arranges a /etc/mysql/my.cnf
symlink, usually via /usr/share/mysql-common/configure-symlinks, MUST
Provide and Conflict mysql-my-cnf, with the exception of mysql-common.

Then we wouldn't have to track individual conflicts related to my.cnf. I
think apt should be able to figure things out then, right?

Robie


signature.asc
Description: PGP signature

Bug#851814: apt-build: Broken postinst by less permissive sed

[Axel Beckert]

Hi Santiago,

Santiago Vila wrote:
> Setting up apt-build (0.12.45) ...
> sed: character class syntax is [[:space:]], not [:space:]
> dpkg: error processing package apt-build (--configure):
>  subprocess installed post-installation script returned error exit
> status 4
> Processing triggers for man-db (2.7.6.1-2) ...
> Errors were encountered while processing:
>  apt-build
> 
> Discovered by Antonio Trujillo here:
> 
> https://lists.debian.org/msgid-search/dd7864af-d235-217c-74dc-bd1b5a086...@juntadeandalucia.es

Thanks for forwarding it. Such issues are not detected by just having
the package installed and using it occasionally. But triggering a
reinstallation showed it here, too.

> I think the following trivial patch should fix it,

Thanks for the patch. I'll do an QA upload soon.

> but I'm not confident enough to push it to git because version in
> Debian archives does not exactly match HEAD in git.

Yes, I understand. Point is that when I did the first QA upload there
were (seemingly dead) ITA-traces in the Git master brnach and I didn't
want to throw them away, so for the last RC-fix (back then for
Jessie), I branched off a branch named "jessie" based on the lasted
upload to Unstable. I now did the same for Stretch: Created a branch
"stretch" based on the branch "jessie". As soon as I've uploaded
apt-build, I'll merge back my changes into the "master" branch.

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

Processed: tagging 851814

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 851814 + confirmed pending
Bug #851814 [apt-build] apt-build: Broken postinst by less permissive sed
Added tag(s) pending and confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
851814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851876: slt: FTBFS (Test killed with quit: ran too long (10m0s))

[Santiago Vila]

Package: src:slt
Version: 0.0.git20140301-2
Severity: serious

Hello dkg.

I tried to build this package in stretch with "dpkg-buildpackage -B"
but it failed:


[...]
 debian/rules build-arch
dh build-arch --buildsystem=golang --with=golang
   dh_testdir -a -O--buildsystem=golang
   dh_update_autotools_config -a -O--buildsystem=golang
   dh_autoreconf -a -O--buildsystem=golang
   dh_auto_configure -a -O--buildsystem=golang
   dh_auto_build -a -O--buildsystem=golang
go install -v -p 1 github.com/inconshrevable/slt
github.com/inconshreveable/go-vhost
gopkg.in/yaml.v2
github.com/inconshrevable/slt
   dh_auto_test -a -O--buildsystem=golang
go test -v -p 1 github.com/inconshrevable/slt
=== RUN   TestSimple

[... snipped ...]


/<>/obj-x86_64-linux-gnu/src/github.com/inconshrevable/slt/server.go:117
 +0x332
created by github.com/inconshrevable/slt.TestSimple

/<>/obj-x86_64-linux-gnu/src/github.com/inconshrevable/slt/server_test.go:91
 +0x170

goroutine 7 [chan send]:
github.com/inconshreveable/go-vhost.(*VhostMuxer).run(0xc420016f50)

/<>/obj-x86_64-linux-gnu/src/github.com/inconshreveable/go-vhost/mux.go:99
 +0xee
created by github.com/inconshreveable/go-vhost.NewVhostMuxer

/<>/obj-x86_64-linux-gnu/src/github.com/inconshreveable/go-vhost/mux.go:56
 +0x146

goroutine 8 [chan receive]:
github.com/inconshreveable/go-vhost.(*Listener).Accept(0xc4200c7e20, 0x6e9c08, 
0xc420015bf0, 0x7fa285b6c2a0, 0xc420011ed0)

/<>/obj-x86_64-linux-gnu/src/github.com/inconshreveable/go-vhost/mux.go:279
 +0x5b
github.com/inconshrevable/slt.(*Server).runFrontend(0xc420015bf0, 0xc420011bf0, 
0x10, 0xc42001b0a0, 0x7e23e0, 0xc4200c7e20)

/<>/obj-x86_64-linux-gnu/src/github.com/inconshrevable/slt/server.go:132
 +0x1d6
created by github.com/inconshrevable/slt.(*Server).Run

/<>/obj-x86_64-linux-gnu/src/github.com/inconshrevable/slt/server.go:85
 +0x2cc

rax0xca
rbx0x7fd650
rcx0x45e7a3
rdx0x0
rdi0x7fe190
rsi0x0
rbp0x7ffd17d698f0
rsp0x7ffd17d698a8
r8 0x0
r9 0x0
r100x0
r110x286
r120x0
r130xf3
r140x8
r150x3
rip0x45e7a1
rflags 0x286
cs 0x33
fs 0x0
gs 0x0
*** Test killed with quit: ran too long (10m0s).
FAILgithub.com/inconshrevable/slt   600.011s
dh_auto_test: go test -v -p 1 github.com/inconshrevable/slt returned exit code 1
debian/rules:6: recipe for target 'build-arch' failed
make: *** [build-arch] Error 1
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


A similar failure happens here:

https://tests.reproducible-builds.org/debian/logs/testing/amd64/slt_0.0.git20140301-2.build2.log.gz

so this is most likely not related to the fact that I'm using sbuild or the fact
that I'm using single-CPU machines.

In either case, I've put several build logs here:

https://people.debian.org/~sanvila/build-logs/slt/

Thanks.

Bug#851775: marked as done (libgcj-bc shlibs creates dependency that cannot be fulfilled in unstable)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 13:49:27 +
with message-id 
and subject line Bug#851775: fixed in gcc-defaults 1.165
has caused the Debian Bug report #851775,
regarding libgcj-bc shlibs creates dependency that cannot be fulfilled in 
unstable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgcj-bc
Version: 6.2.1-1
Severity: grave
Control: affects -1 libecj-java-gcj ecj1 ecj-gcj ant-gcj ant-optional-gcj

$ cat /var/lib/dpkg/info/libgcj-bc\:amd64.shlibs 
libgcj_bc 1 libgcj-bc (>= 6.2.1-3~)
$ 


That seems to be the reason why several packages can currently
not be installed in unstable:

  libecj-java-gcj,libgcj-bc 6.2.1-3~
  ecj1,libgcj-bc 6.2.1-3~
  ecj-gcj,libgcj-bc 6.2.1-3~
  ant-gcj,libgcj-bc 6.2.1-3~
  ant-optional-gcj,libgcj-bc 6.2.1-3~
--- End Message ---
--- Begin Message ---
Source: gcc-defaults
Source-Version: 1.165

We believe that the bug you reported is fixed in the latest version of
gcc-defaults, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-defaults package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Jan 2017 17:11:46 +0100
Source: gcc-defaults
Binary: cpp gcc gcc-multilib g++ g++-multilib gobjc gobjc-multilib gobjc++ 
gobjc++-multilib gfortran gfortran-multilib gccgo gccgo-multilib libgcj-common 
libgcj-bc gcj-jdk gcj-jre-headless gcj-jre gdc gdc-multilib libgphobos-dev 
gcc-hppa64-linux-gnu cpp-s390x-linux-gnu gcc-s390x-linux-gnu 
g++-s390x-linux-gnu gobjc-s390x-linux-gnu gobjc++-s390x-linux-gnu 
gfortran-s390x-linux-gnu gccgo-s390x-linux-gnu gcj-s390x-linux-gnu 
gdc-s390x-linux-gnu gcc-multilib-s390x-linux-gnu g++-multilib-s390x-linux-gnu 
gobjc-multilib-s390x-linux-gnu gobjc++-multilib-s390x-linux-gnu 
gfortran-multilib-s390x-linux-gnu gccgo-multilib-s390x-linux-gnu 
gdc-multilib-s390x-linux-gnu cpp-powerpc64le-linux-gnu 
gcc-powerpc64le-linux-gnu g++-powerpc64le-linux-gnu gobjc-powerpc64le-linux-gnu 
gobjc++-powerpc64le-linux-gnu gfortran-powerpc64le-linux-gnu 
gccgo-powerpc64le-linux-gnu gcj-powerpc64le-linux-gnu gdc-powerpc64le-linux-gnu 
cpp-aarch64-linux-gnu gcc-aarch64-linux-gnu g++-aarch64-linux-gnu
 gobjc-aarch64-linux-gnu gobjc++-aarch64-linux-gnu gfortran-aarch64-linux-gnu 
gccgo-aarch64-linux-gnu gcj-aarch64-linux-gnu gdc-aarch64-linux-gnu 
cpp-arm-linux-gnueabihf gcc-arm-linux-gnueabihf g++-arm-linux-gnueabihf 
gobjc-arm-linux-gnueabihf gobjc++-arm-linux-gnueabihf 
gfortran-arm-linux-gnueabihf gccgo-arm-linux-gnueabihf gcj-arm-linux-gnueabihf 
gdc-arm-linux-gnueabihf cpp-arm-linux-gnueabi gcc-arm-linux-gnueabi 
g++-arm-linux-gnueabi gobjc-arm-linux-gnueabi gobjc++-arm-linux-gnueabi 
gfortran-arm-linux-gnueabi gccgo-arm-linux-gnueabi gcj-arm-linux-gnueabi 
gdc-arm-linux-gnueabi cpp-mips-linux-gnu gcc-mips-linux-gnu g++-mips-linux-gnu 
gobjc-mips-linux-gnu gobjc++-mips-linux-gnu gfortran-mips-linux-gnu 
gccgo-mips-linux-gnu gcj-mips-linux-gnu gdc-mips-linux-gnu 
gcc-multilib-mips-linux-gnu g++-multilib-mips-linux-gnu 
gobjc-multilib-mips-linux-gnu gobjc++-multilib-mips-linux-gnu 
gfortran-multilib-mips-linux-gnu gccgo-multilib-mips-linux-gnu 
gdc-multilib-mips-linux-gnu
 cpp-mipsel-linux-gnu gcc-mipsel-linux-gnu g++-mipsel-linux-gnu 
gobjc-mipsel-linux-gnu gobjc++-mipsel-linux-gnu gfortran-mipsel-linux-gnu 
gccgo-mipsel-linux-gnu gcj-mipsel-linux-gnu gdc-mipsel-linux-gnu 
gcc-multilib-mipsel-linux-gnu g++-multilib-mipsel-linux-gnu 
gobjc-multilib-mipsel-linux-gnu gobjc++-multilib-mipsel-linux-gnu 
gfortran-multilib-mipsel-linux-gnu gccgo-multilib-mipsel-linux-gnu 
gdc-multilib-mipsel-linux-gnu cpp-mips64el-linux-gnuabi64 
gcc-mips64el-linux-gnuabi64 g++-mips64el-linux-gnuabi64 
gobjc-mips64el-linux-gnuabi64 gobjc++-mips64el-linux-gnuabi64 
gfortran-mips64el-linux-gnuabi64 gccgo-mips64el-linux-gnuabi64 
gcj-mips64el-linux-gnuabi64 gdc-mips64el-linux-gnuabi64 

Bug#851513: Build fails with Linux kernel 4.9.0

[Holger Schröder]

works, thanks.

...

Bug#851254: marked as done (androidsdk-tools: please don't depend on android-tools-adb)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 13:18:44 +
with message-id 
and subject line Bug#851254: fixed in androidsdk-tools 
22.2+git20130830~92d25d6-4
has caused the Debian Bug report #851254,
regarding androidsdk-tools: please don't depend on android-tools-adb
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851254: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: androidsdk-tools
Version: 22.2+git20130830~92d25d6-3
Severity: serious

The adb binary seems to have migrated from the android-tools-adb package
to the adb package provided by the android-platform-system-core source
package.
The package libandroidsdk-ddmlib-java (which is part of
androidsdk-tools) still depends on android-tools-adb which makes it not
possible to decruft android-tools without breaking this package.
Please replace the depends line for libandroidsdk-ddmlib-java.

Sebastian
--- End Message ---
--- Begin Message ---
Source: androidsdk-tools
Source-Version: 22.2+git20130830~92d25d6-4

We believe that the bug you reported is fixed in the latest version of
androidsdk-tools, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated androidsdk-tools 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 19 Jan 2017 12:52:17 +0100
Source: androidsdk-tools
Binary: libandroidsdk-common-java libandroidsdk-sdklib-java 
libandroidsdk-sdkstats-java libandroidsdk-swtmenubar-java 
libandroidsdk-ddmlib-java libandroidsdk-ddmuilib-java androidsdk-ddms 
libandroidsdk-hierarchyviewerlib-java androidsdk-hierarchyviewer 
androidsdk-traceview androidsdk-uiautomatorviewer
Architecture: source all
Version: 22.2+git20130830~92d25d6-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 androidsdk-ddms - Graphical debugging tool for Android
 androidsdk-hierarchyviewer - Tool to debug and optimize Android user interface
 androidsdk-traceview - Tool to profile performance of Android applications
 androidsdk-uiautomatorviewer - Tool to scan and analyze the UI components of 
an Android applicat
 libandroidsdk-common-java - Android sdk tools common library
 libandroidsdk-ddmlib-java - Library for communicaton with connected Android 
devices
 libandroidsdk-ddmuilib-java - User interface library for ddmlib
 libandroidsdk-hierarchyviewerlib-java - Android Hierarchy Viewer library
 libandroidsdk-sdklib-java - Android SDKlib
 libandroidsdk-sdkstats-java - Sends Android SDK usage statistics to Google
 libandroidsdk-swtmenubar-java - Android SDK OS menubar hook library
Closes: 851254
Changes:
 androidsdk-tools (22.2+git20130830~92d25d6-4) unstable; urgency=medium
 .
   * Team upload.
   * Depend on adb instead of android-tools-adb (Closes: #851254)
   * Build depend on libswt-gtk-4-java instead of libswt-gtk-3-java
   * Standards-Version updated to 3.9.8
   * Switch to debhelper level 10
   * Use a secure Vcs-Git URL
Checksums-Sha1:
 9209d94351a17e82cef327f5e3496fcf0eeb7d58 3206 
androidsdk-tools_22.2+git20130830~92d25d6-4.dsc
 535e6ad72f18834660e8f5bf3193179e03b7a1c6 20536 
androidsdk-tools_22.2+git20130830~92d25d6-4.debian.tar.xz
 c21fff27f3abeceb4b3e2e829928f698e80599eb 142270 
androidsdk-ddms_22.2+git20130830~92d25d6-4_all.deb
 af8658a0d06b582807e0b80f0ebee827cf760e10 58118 
androidsdk-hierarchyviewer_22.2+git20130830~92d25d6-4_all.deb
 0c85963f27fd15ca8257aaf262d2e86cf3d5464f 14264 
androidsdk-tools_22.2+git20130830~92d25d6-4_amd64.buildinfo
 4d37c65bd141acd9e0a1d41dc4e688fd0464689a 136870 
androidsdk-traceview_22.2+git20130830~92d25d6-4_all.deb
 294ef7ec94bb1fefd96d7cdaacdc17f63211b08a 55084 
androidsdk-uiautomatorviewer_22.2+git20130830~92d25d6-4_all.deb
 8cda2f7d4d9179b49e519d649443c9b5011c9500 65670 
libandroidsdk-common-java_22.2+git20130830~92d25d6-4_all.deb
 bac949642ef5f6117911f71fcf7cd837024386c2 233700 

Bug#846758: Supporting H.323 Stack in Stretch?

[Joerg Dorchain]

On Thu, Jan 19, 2017 at 12:56:23PM +0100, Bernhard Schmidt wrote:
> 
> I have just come across
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766045 whichs says
> that
> 
> a) there is a fork at  https://github.com/PeteDavidson/t38modem
> b) t38modem (I guess only the old version) won't work with current opal
> http://sourceforge.net/p/opalvoip/mailman/message/32955378/ . 
> 
> I guess since it is too late for Stretch now and we will likely have to
> upgrade opal sooner or later I think the only way forward will be the
> fork.

After stretch, defintivly yes.
> 
> Would you be willing to maintain this? I haven't received or sent a fax
> in 5+ years, I cannot test this.

Well, I could give it a try.

However, I received ~5 faxes last year and sent 1, so I am not
the most active fax user ever. Besides, with more bandwidth and
less jitter, faxes even work with plain iaxmodem[0]

Nevertheless, when there is a newer opal version in debian and
t38modem then has a nother FTBS-bugs, I can proabably package the
version from github.

Bye,

Joerg

[0] An analog paper scanned, converted to sound signals, then
digitised again, send in small packet over the net, all by the
same CPU in realtime. Receiving end analog. Amazing[1]..
[1] Most people just send pdfs directly.


signature.asc
Description: PGP signature

Bug#851047: marked as done (gcc-6-cross-ports: FTBFS: 1 out of 1 hunk FAILED -- rejects in file src/libphobos/configure.ac)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 12:48:59 +
with message-id 
and subject line Bug#851047: fixed in gcc-6-cross-ports 12
has caused the Debian Bug report #851047,
regarding gcc-6-cross-ports: FTBFS: 1 out of 1 hunk FAILED -- rejects in file 
src/libphobos/configure.ac
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-6-cross-ports
Version: 11
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/gcc'
> : # unpack gcc tarball
> mkdir -p stamps
> if [ -d /<>/gcc/src ]; then \
>   echo >&2 "Source directory /<>/gcc/src exists. Delete by 
> hand"; \
>   false; \
> fi
> rm -rf gcc-6.3.0
> tar -x -f /usr/src/gcc-6/gcc-6.3.0-dfsg.tar.xz
> mv gcc-6.3.0 /<>/gcc/src
> ln -sf libsanitizer /<>/gcc/src/libasan
> rm -f /<>/gcc/src/gcc/doc/*.1
> rm -f /<>/gcc/src/gcc/doc/fsf-funding.7
> rm -f /<>/gcc/src/gcc/doc/*.info
> rm -f /<>/gcc/src/gcc/fortran/*.info
> rm -f /<>/gcc/src/libgomp/*.info
> rm -f /<>/gcc/src/gcc/java/*.1
> rm -f /<>/gcc/src/gcc/java/*.info
> for i in gcc/doc/avr-mmcu.texi gcc/doc/bugreport.texi gcc/doc/cfg.texi 
> gcc/doc/collect2.texi gcc/doc/compat.texi gcc/doc/configfiles.texi 
> gcc/doc/configterms.texi gcc/doc/contrib.texi gcc/doc/contribute.texi 
> gcc/doc/cpp.texi gcc/doc/cppenv.texi gcc/doc/cppinternals.texi 
> gcc/doc/cppopts.texi gcc/doc/extend.texi gcc/doc/fragments.texi 
> gcc/doc/frontends.texi gcc/doc/gccint.texi gcc/doc/gcov.texi 
> gcc/doc/gcov-tool.texi gcc/doc/generic.texi gcc/doc/gimple.texi 
> gcc/doc/gnu.texi gcc/doc/gty.texi gcc/doc/headerdirs.texi 
> gcc/doc/hostconfig.texi gcc/doc/implement-c.texi gcc/doc/implement-cxx.texi 
> gcc/doc/install-old.texi gcc/doc/install.texi gcc/doc/interface.texi 
> gcc/doc/invoke.texi gcc/doc/languages.texi gcc/doc/libgcc.texi 
> gcc/doc/loop.texi gcc/doc/lto.texi gcc/doc/makefile.texi 
> gcc/doc/match-and-simplify.texi gcc/doc/md.texi gcc/doc/objc.texi 
> gcc/doc/optinfo.texi gcc/doc/options.texi gcc/doc/passes.texi 
> gcc/doc/plugins.texi gcc/doc/portability.texi gcc/doc/rtl.texi 
> gcc/doc/service.texi gcc/doc/sourcebuild.texi gcc/doc/standards.texi 
> gcc/doc/tm.texi.in gcc/doc/tm.texi gcc/doc/tree-ssa.texi gcc/doc/trouble.texi 
> gcc/doc/include/gcc-common.texi gcc/doc/include/funding.texi 
> gcc/fortran/gfc-internals.texi gcc/fortran/invoke.texi 
> gcc/fortran/intrinsic.texi ; do \
>   if [ -f /<>/gcc/src/$i ]; then \
> cp debian/dummy.texi /<>/gcc/src/$i; \
>   else \
> cp debian/dummy.texi /<>/gcc/src/$i; \
> echo >&2 "$i does not exist, fix debian/rules.unpack"; \
>   fi; \
> done
> for i in gcc/doc/gcc.texi gcc/java/gcj.texi gcc/ada/gnat-style.texi 
> gcc/ada/gnat_rm.texi gcc/ada/gnat_ugn.texi gcc/fortran/gfortran.texi 
> gcc/go/gccgo.texi libgomp/libgomp.texi libquadmath/libquadmath.texi ; do \
>   n=$(basename $i .texi); \
>   if [ -f /<>/gcc/src/$i ]; then \
> sed "s/@name@/$n/g" debian/gcc-dummy.texi \
>   > /<>/gcc/src/$i; \
>   else \
> sed "s/@name@/$n/g" debian/gcc-dummy.texi \
>   > /<>/gcc/src/$i; \
> echo >&2 "$i does not exist, fix debian/rules.unpack"; \
>   fi; \
> done
> for i in gcc/doc/cpp.1 gcc/doc/g++.1 gcc/doc/gc-analyze.1 gcc/doc/gcc.1 
> gcc/doc/gccgo.1 gcc/doc/gcj.1 gcc/doc/gcj-dbtool.1 gcc/doc/gcjh.1 
> gcc/doc/gcov.1 gcc/doc/gcov-tool.1 gcc/doc/gfortran.1 gcc/doc/gij.1 
> gcc/doc/grmic.1 gcc/doc/grmiregistry.1 gcc/doc/jcf-dump.1 
> gcc/doc/jv-convert.1 gcc/doc/fsf-funding.7 ; do \
>   touch /<>/gcc/src/$i; \
> done
> rm -f /<>/gcc/src/INSTALL/*.html
> echo "gcc-6.3.0-dfsg.tar.xz unpacked." > 
> stamps/01-unpack-stamp-gcc-6.3.0-dfsg.tar.xz
> : # unpack gdc tarball
> mkdir -p stamps
> if [ -d /<>/gcc/src/gcc/d ]; then \
>   echo >&2 "Source directory /<>/gcc/src/gcc/d exists. Delete by 
> hand";\
>   false; \
> fi
> #rm -rf gdc-20161222
> rm -rf /<>/gcc/src/gcc/d
> rm -rf /<>/gcc/src/gcc/testsuite/gdc.test
> rm -f /<>/gcc/src/gcc/testsuite/lib/gdc*.exp
> rm -rf /<>/gcc/src/libphobos
> tar -x -C /<>/gcc/src --strip-components=1 -f 
> /usr/src/gcc-6/gdc-20161222.tar.xz
> echo "gdc-20161222.tar.xz unpacked." > 
> stamps/01-unpack-stamp-gdc-20161222.tar.xz
> echo -e "\nBuilt from Debian source package gcc-6-6.3.0-2" \
>   > pxxx
> echo -e "Integrated upstream packages in 

Bug#851038: marked as done (gcc-6-cross: FTBFS: 1 out of 1 hunk FAILED -- rejects in file src/libphobos/configure.ac)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 12:48:52 +
with message-id 
and subject line Bug#851038: fixed in gcc-6-cross 15
has caused the Debian Bug report #851038,
regarding gcc-6-cross: FTBFS: 1 out of 1 hunk FAILED -- rejects in file 
src/libphobos/configure.ac
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-6-cross
Version: 14
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/gcc'
> : # unpack gcc tarball
> mkdir -p stamps
> if [ -d /<>/gcc/src ]; then \
>   echo >&2 "Source directory /<>/gcc/src exists. Delete by 
> hand"; \
>   false; \
> fi
> rm -rf gcc-6.3.0
> tar -x -f /usr/src/gcc-6/gcc-6.3.0-dfsg.tar.xz
> mv gcc-6.3.0 /<>/gcc/src
> ln -sf libsanitizer /<>/gcc/src/libasan
> rm -f /<>/gcc/src/gcc/doc/*.1
> rm -f /<>/gcc/src/gcc/doc/fsf-funding.7
> rm -f /<>/gcc/src/gcc/doc/*.info
> rm -f /<>/gcc/src/gcc/fortran/*.info
> rm -f /<>/gcc/src/libgomp/*.info
> rm -f /<>/gcc/src/gcc/java/*.1
> rm -f /<>/gcc/src/gcc/java/*.info
> for i in gcc/doc/avr-mmcu.texi gcc/doc/bugreport.texi gcc/doc/cfg.texi 
> gcc/doc/collect2.texi gcc/doc/compat.texi gcc/doc/configfiles.texi 
> gcc/doc/configterms.texi gcc/doc/contrib.texi gcc/doc/contribute.texi 
> gcc/doc/cpp.texi gcc/doc/cppenv.texi gcc/doc/cppinternals.texi 
> gcc/doc/cppopts.texi gcc/doc/extend.texi gcc/doc/fragments.texi 
> gcc/doc/frontends.texi gcc/doc/gccint.texi gcc/doc/gcov.texi 
> gcc/doc/gcov-tool.texi gcc/doc/generic.texi gcc/doc/gimple.texi 
> gcc/doc/gnu.texi gcc/doc/gty.texi gcc/doc/headerdirs.texi 
> gcc/doc/hostconfig.texi gcc/doc/implement-c.texi gcc/doc/implement-cxx.texi 
> gcc/doc/install-old.texi gcc/doc/install.texi gcc/doc/interface.texi 
> gcc/doc/invoke.texi gcc/doc/languages.texi gcc/doc/libgcc.texi 
> gcc/doc/loop.texi gcc/doc/lto.texi gcc/doc/makefile.texi 
> gcc/doc/match-and-simplify.texi gcc/doc/md.texi gcc/doc/objc.texi 
> gcc/doc/optinfo.texi gcc/doc/options.texi gcc/doc/passes.texi 
> gcc/doc/plugins.texi gcc/doc/portability.texi gcc/doc/rtl.texi 
> gcc/doc/service.texi gcc/doc/sourcebuild.texi gcc/doc/standards.texi 
> gcc/doc/tm.texi.in gcc/doc/tm.texi gcc/doc/tree-ssa.texi gcc/doc/trouble.texi 
> gcc/doc/include/gcc-common.texi gcc/doc/include/funding.texi 
> gcc/fortran/gfc-internals.texi gcc/fortran/invoke.texi 
> gcc/fortran/intrinsic.texi ; do \
>   if [ -f /<>/gcc/src/$i ]; then \
> cp debian/dummy.texi /<>/gcc/src/$i; \
>   else \
> cp debian/dummy.texi /<>/gcc/src/$i; \
> echo >&2 "$i does not exist, fix debian/rules.unpack"; \
>   fi; \
> done
> for i in gcc/doc/gcc.texi gcc/java/gcj.texi gcc/ada/gnat-style.texi 
> gcc/ada/gnat_rm.texi gcc/ada/gnat_ugn.texi gcc/fortran/gfortran.texi 
> gcc/go/gccgo.texi libgomp/libgomp.texi libquadmath/libquadmath.texi ; do \
>   n=$(basename $i .texi); \
>   if [ -f /<>/gcc/src/$i ]; then \
> sed "s/@name@/$n/g" debian/gcc-dummy.texi \
>   > /<>/gcc/src/$i; \
>   else \
> sed "s/@name@/$n/g" debian/gcc-dummy.texi \
>   > /<>/gcc/src/$i; \
> echo >&2 "$i does not exist, fix debian/rules.unpack"; \
>   fi; \
> done
> for i in gcc/doc/cpp.1 gcc/doc/g++.1 gcc/doc/gc-analyze.1 gcc/doc/gcc.1 
> gcc/doc/gccgo.1 gcc/doc/gcj.1 gcc/doc/gcj-dbtool.1 gcc/doc/gcjh.1 
> gcc/doc/gcov.1 gcc/doc/gcov-tool.1 gcc/doc/gfortran.1 gcc/doc/gij.1 
> gcc/doc/grmic.1 gcc/doc/grmiregistry.1 gcc/doc/jcf-dump.1 
> gcc/doc/jv-convert.1 gcc/doc/fsf-funding.7 ; do \
>   touch /<>/gcc/src/$i; \
> done
> rm -f /<>/gcc/src/INSTALL/*.html
> echo "gcc-6.3.0-dfsg.tar.xz unpacked." > 
> stamps/01-unpack-stamp-gcc-6.3.0-dfsg.tar.xz
> : # unpack gdc tarball
> mkdir -p stamps
> if [ -d /<>/gcc/src/gcc/d ]; then \
>   echo >&2 "Source directory /<>/gcc/src/gcc/d exists. Delete by 
> hand";\
>   false; \
> fi
> #rm -rf gdc-20161222
> rm -rf /<>/gcc/src/gcc/d
> rm -rf /<>/gcc/src/gcc/testsuite/gdc.test
> rm -f /<>/gcc/src/gcc/testsuite/lib/gdc*.exp
> rm -rf /<>/gcc/src/libphobos
> tar -x -C /<>/gcc/src --strip-components=1 -f 
> /usr/src/gcc-6/gdc-20161222.tar.xz
> echo "gdc-20161222.tar.xz unpacked." > 
> stamps/01-unpack-stamp-gdc-20161222.tar.xz
> echo -e "\nBuilt from Debian source package gcc-6-6.3.0-2" \
>   > pxxx
> echo -e "Integrated upstream packages in this version:\n"