Bug#824827: mixmaster: hold on..

2017-11-30 Thread Anonymous
Package: mixmaster
Version: 3.0.0-8.1
Followup-For: Bug #824827

> I know that. What you fail to realise is that the mixmaster
> *specification* makes no mention of 4k keys!

Then why would you claim it's not a bug for mixmaster to write packets
for out-of-spec hosts?  If a host doesn't conform to mixmaster specs,
then it's not a mixmaster node, thus mixmaster shouldn't be talking to
it.  You might as well design it to create messages for FTP servers
(which are also non-compliant but equally functional as the current
state).



Processed: Pending fixes for bugs in the golang-google-grpc package

2017-11-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 882554 + pending
Bug #882554 [src:golang-google-grpc] golang-google-grpc FTBFS: stringer: 
checking package: code_string.go:5:8: could not import fmt (can't find import: )
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#882554: Pending fixes for bugs in the golang-google-grpc package

2017-11-30 Thread pkg-go-maintainers
tag 882554 + pending
thanks

Some bugs in the golang-google-grpc package are closed in revision
ee9c570738a545c8db1f485851ddbf7ad8902bd1 in branch 'master' by
Shengjing Zhu

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

Commit message:

remove codes/code_string.go before running go generate (Closes: #882554).

codes/code_string.go is also generated file. running go generate on
file codes/codes.go will cause stringer to process all files in
dir codes, including this generated file.

Signed-off-by: Shengjing Zhu 



Processed: limit source to twig, tagging 882941

2017-11-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

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

> tags 882941 + pending
Bug #882941 [src:twig] twig FTBFS with phpunit 6.4.4-2
Added tag(s) pending.
> thanks
Stopping processing here.

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



Processed: Re: Bug#874295: Not a bug

2017-11-30 Thread Debian Bug Tracking System
Processing control commands:

> notfound -1 clementine/1.3.1+git276-g3485bbe43+dfsg-1
Bug #874295 {Done: Thomas Pierson } [clementine] 
clementine: installs non-free plugin at runtime
No longer marked as found in versions clementine/1.3.1+git276-g3485bbe43+dfsg-1.

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



Bug#874295: Not a bug

2017-11-30 Thread Ben Finney
Control: notfound -1 clementine/1.3.1+git276-g3485bbe43+dfsg-1

On 30-Nov-2017, Ben Finney wrote:
> Thomas Pierson  writes:
> > So unless someone point me a clear justification I will close this
> > bug as invalid for now.
> 
> I agree that, despite the problems remarked on of downloading and
> executing unpackaged code to execute on the user's computer, this is
> not a dependency for the program performing its normal function. So
> this does not appear to be a Policy §2.2.1 violation.

I'm recording the effects of this resolution on the metadata of this
report.

-- 
 \“If you continue running Windows, your system may become |
  `\unstable.” —Microsoft, Windows 95 bluescreen error message |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature


Processed: clementine: Third-party plug-ins should be packaged for Debian

2017-11-30 Thread Debian Bug Tracking System
Processing control commands:

> clone -1 -2
Bug #874295 {Done: Thomas Pierson } [clementine] 
clementine: installs non-free plugin at runtime
Bug 874295 cloned as bug 883225
> retitle -2 clementine: Third-party plug-ins should be packaged for Debian
Bug #883225 {Done: Thomas Pierson } [clementine] 
clementine: installs non-free plugin at runtime
Changed Bug title to 'clementine: Third-party plug-ins should be packaged for 
Debian' from 'clementine: installs non-free plugin at runtime'.
> found -2 clementine/1.3.1+git276-g3485bbe43+dfsg-1
Bug #883225 {Done: Thomas Pierson } [clementine] 
clementine: Third-party plug-ins should be packaged for Debian
Did not alter found versions and reopened.
> severity -2 minor
Bug #883225 [clementine] clementine: Third-party plug-ins should be packaged 
for Debian
Severity set to 'minor' from 'serious'
> tags -2 - upstream
Bug #883225 [clementine] clementine: Third-party plug-ins should be packaged 
for Debian
Removed tag(s) upstream.

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



Bug#874295: clementine: Third-party plug-ins should be packaged for Debian

2017-11-30 Thread Ben Finney
Control: clone -1 -2
Control: retitle -2 clementine: Third-party plug-ins should be packaged for 
Debian
Control: found -2 clementine/1.3.1+git276-g3485bbe43+dfsg-1
Control: severity -2 minor
Control: tags -2 - upstream

On 04-Sep-2017, Jonas Smedegaard wrote:

> One of several functions of Clementine is to stream audio from cloud
> service Spotify. Initially selecting that function triggers a
> routine where Clementine (asks for concent and then) downloads and
> installs a non-free binary driver.

As discussed in bug#874295, I think there is a separate bug to be
resolved here: the program should not download code for execution from
a third-party website, when that code can instead be packaged for
Debian and installed using the OS package manager.

On 30-Nov-2017, Ben Finney wrote:
> Thomas Pierson  writes:
> > It's only if a user want to connect to a particular external
> > service that a plugin file is downloaded and used.
> 
> That is still a problem, IMO. It would be best if the program did
> not do that, and instead prompted the user to install the non-free
> package providing that plug-in.

This (new) bug report requests that the program in Debian should not
have the behaviour Jonas describes above.

Instead, if there are third-party plug-ins to enable Clementine
features, those plug-ins should be packaged separately for Debian, and
only enabled by installing the Debian package.

The license conditions of those third-party packages will determine
whether they are in Debian, or in some other archive area. This bug
report does not relate to that issue.

Instead, this bug report requests the download and execution of
third-party code should not happen preferring to have the third-party
code packaged and managed by the Debian package manager.

-- 
 \  “… a Microsoft Certified System Engineer is to information |
  `\ technology as a McDonalds Certified Food Specialist is to the |
_o__)   culinary arts.” —Michael Bacarella |
Ben Finney 


signature.asc
Description: PGP signature


Bug#880072: marked as done (node-mapnik doesn't appear to be linking correctly, making it unusable)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Fri, 1 Dec 2017 00:39:17 +0100
with message-id <54c5b5b9-c1fd-1517-ae0a-6fe3fcf4b...@xs4all.nl>
and subject line Re: [Pkg-javascript-devel] Bug#880072: Bug#880072: node-mapnik 
doesn't appear to be linking correctly, making it unusable
has caused the Debian Bug report #880072,
regarding node-mapnik doesn't appear to be linking correctly, making it unusable
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.)


-- 
880072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-mapnik
Version: 3.6.2+dfsg-1
Severity: grave
Justification: renders package unusable

On both Debian and Ubuntu, executing the simple autopkgtest command for
node-mapnik (nodejs -e "require('mapnik');") leads to an error resolving
symbols:

Debian:
---
Error: /usr/lib/nodejs/mapnik/lib/binding/mapnik.node: undefined symbol: 
_ZN6mapnik15freetype_engine10face_namesEv
at Error (native)
at Object.Module._extensions..node (module.js:597:18)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/usr/lib/nodejs/mapnik/lib/mapnik.js:31:15)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)

Ubuntu:
---
Error: /usr/lib/nodejs/mapnik/lib/binding/mapnik.node: undefined symbol: 
_ZN6mapnik14save_to_stringINS_5imageINS_7rgba8_tESsRKT_RKSsRKNS_12rgba_paletteE
at Error (native)
at Object.Module._extensions..node (module.js:597:18)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/usr/lib/nodejs/mapnik/lib/mapnik.js:31:15)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)

This pretty clearly makes the package entirely unusable (unless there's
some other way to use it correctly, and the autopkgtest is incorrect?)

... Adam

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

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

Versions of packages node-mapnik depends on:
ii  libc6  2.26-0ubuntu2
ii  libgcc11:7.2.0-12ubuntu1
pn  libmapnik3.0   
ii  libstdc++6 7.2.0-12ubuntu1
pn  mapnik-utils   
pn  node-pre-gyp   
pn  nodejs 
pn  nodejs-abi-48  
pn  nodejs-dev 

Versions of packages node-mapnik recommends:
pn  node-carto
pn  node-srs  
pn  node-zipfile  

node-mapnik suggests no packages.
--- End Message ---
--- Begin Message ---
fixed 880072 node-mapnik/3.6.2+dfsg-2
thanks

On 10/29/2017 12:54 PM, Sebastiaan Couwenberg wrote:
> On 10/29/2017 11:03 AM, Adam Conrad wrote:
>> On both Debian and Ubuntu, executing the simple autopkgtest command for
>> node-mapnik (nodejs -e "require('mapnik');") leads to an error resolving
>> symbols:
> 
> This is a known issue. And not one I'm willing to spend time on, since
> there are no known users of the node-mapnik package.

The mapnik::freetype_engine issue seems to have been fixed with Mapnik
3.0.17 and the latest changes from the node-mapnik upstream git repository.

node-mapnik (3.6.2+dfsg-2) passes the CI tests again in Debian.

> The Mapnik ecosystem is quite fragile, with an upstream who relies on
> mason builds (often from development branches), making packaging quite a
> chore.
> 
> I think the node-mapnik package and its node-tilelive-* rdeps should be
> removed from Debian (and by extension Ubuntu), and we should give up on
> ever packaging kosmtik (#805308).

I still think that we should remove node-mapnik and its reverse
dependencies from Debian, but since I'm not the maintainer of the
package at least Jérémy will need to consent to it.

Kind Regards,

Bas

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


Processed: Re: [Pkg-javascript-devel] Bug#880072: Bug#880072: node-mapnik doesn't appear to be linking correctly, making it unusable

2017-11-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 880072 node-mapnik/3.6.2+dfsg-2
Bug #880072 [node-mapnik] node-mapnik doesn't appear to be linking correctly, 
making it unusable
Marked as fixed in versions node-mapnik/3.6.2+dfsg-2.
> thanks
Stopping processing here.

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



Bug#861027: Can Confirm

2017-11-30 Thread Barak A. Pearlmutter
This bit me today too. In a lecture hall full of students.
Luckily I had SWI Prolog installed as well, or it would have been a serious
disaster.

--Barak.

$ cat mortal.pl

man(aristotle).
mortal(X) :- man(X).% for all X


$ gprolog
GNU Prolog 1.4.5 (64 bits)
Compiled Feb  5 2017, 10:30:08 with gcc
By Daniel Diaz
Copyright (C) 1999-2016 Daniel Diaz
| ?- ['mortal.pl'].
compiling /home/barak/tmp/mortal.pl for byte code...
/home/barak/tmp/mortal.pl compiled, 4 lines read - 356 bytes written, 6 ms

yes
| ?- mortal(barak).
uncaught exception: error(existence_error(procedure,man/0),mortal/0)
| ?- mortal(aristotle).
uncaught exception: error(existence_error(procedure,man/0),mortal/0)
| ?- man(barak).

no
| ?- man(aristotle).

yes
| ?- man(X).

X = aristotle

yes
| ?-


Bug#878794: marked as done (golang-github-nbutton23-zxcvbn-go-dev 0.0~git20170830.0.f4cd9f5-2 causes FTBFS in golang-github-chzyer-readline)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 23:38:05 +0100
with message-id 
and subject line Fixed FTBFS
has caused the Debian Bug report #878794,
regarding golang-github-nbutton23-zxcvbn-go-dev 0.0~git20170830.0.f4cd9f5-2 
causes FTBFS in golang-github-chzyer-readline
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.)


-- 
878794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-chzyer-readline
Version: 1.4-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-chzyer-readline.html

...
  dh_auto_build -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/build/1st/golang-github-chzyer-readline-1.4/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/build/1st/golang-github-chzyer-readline-1.4/obj-x86_64-linux-gnu/src\"
 -v -p 15 github.com/chzyer/readline 
github.com/chzyer/readline/example/readline-demo 
github.com/chzyer/readline/example/readline-im 
github.com/chzyer/readline/example/readline-multiline 
github.com/chzyer/readline/example/readline-pass-strength 
github.com/chzyer/readline/example/readline-remote/readline-remote-client 
github.com/chzyer/readline/example/readline-remote/readline-remote-server 
github.com/chzyer/readline/runes
github.com/chzyer/readline
github.com/nbutton23/zxcvbn-go
github.com/chzyer/readline/runes
github.com/chzyer/readline/example/readline-demo
github.com/chzyer/readline/example/readline-im
github.com/chzyer/readline/example/readline-multiline
github.com/chzyer/readline/example/readline-remote/readline-remote-client
github.com/chzyer/readline/example/readline-remote/readline-remote-server
github.com/chzyer/readline/example/readline-pass-strength
# github.com/chzyer/readline/example/readline-pass-strength
src/github.com/chzyer/readline/example/readline-pass-strength/readline-pass-strength.go:53:14:
 undefined: pam.PasswordStrength
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/build/1st/golang-github-chzyer-readline-1.4/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/build/1st/golang-github-chzyer-readline-1.4/obj-x86_64-linux-gnu/src\"
 -v -p 15 github.com/chzyer/readline 
github.com/chzyer/readline/example/readline-demo 
github.com/chzyer/readline/example/readline-im 
github.com/chzyer/readline/example/readline-multiline 
github.com/chzyer/readline/example/readline-pass-strength 
github.com/chzyer/readline/example/readline-remote/readline-remote-client 
github.com/chzyer/readline/example/readline-remote/readline-remote-server 
github.com/chzyer/readline/runes returned exit code 2
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
--- End Message ---
--- Begin Message ---
Package: golang-github-nbutton23-zxcvbn-go-dev
Version: 0.1-2

Hi,

the FTBFS bug in golang-github-chzyer-readline has been caused by
golang-github-nbutton23-zxcvbn-go and should be fixed now. I did not
include the bug in the changelog of the latest upload, so I'm closing
the bug by mail.

Regards,
Tobias



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


Processed: golang-github-chzyer-readline: The FTBFS bug is caused in another package

2017-11-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 878794 golang-github-nbutton23-zxcvbn-go-dev 
> 0.0~git20170830.0.f4cd9f5-2
Bug #878794 [src:golang-github-chzyer-readline] golang-github-chzyer-readline 
FTBFS: readline-pass-strength.go:53:14: undefined: pam.PasswordStrength
Bug reassigned from package 'src:golang-github-chzyer-readline' to 
'golang-github-nbutton23-zxcvbn-go-dev'.
No longer marked as found in versions golang-github-chzyer-readline/1.4-1.
Ignoring request to alter fixed versions of bug #878794 to the same values 
previously set
Bug #878794 [golang-github-nbutton23-zxcvbn-go-dev] 
golang-github-chzyer-readline FTBFS: readline-pass-strength.go:53:14: 
undefined: pam.PasswordStrength
Marked as found in versions 
golang-github-nbutton23-zxcvbn-go/0.0~git20170830.0.f4cd9f5-2.
> retitle 878794 golang-github-nbutton23-zxcvbn-go-dev 
> 0.0~git20170830.0.f4cd9f5-2 causes FTBFS in golang-github-chzyer-readline
Bug #878794 [golang-github-nbutton23-zxcvbn-go-dev] 
golang-github-chzyer-readline FTBFS: readline-pass-strength.go:53:14: 
undefined: pam.PasswordStrength
Changed Bug title to 'golang-github-nbutton23-zxcvbn-go-dev 
0.0~git20170830.0.f4cd9f5-2 causes FTBFS in golang-github-chzyer-readline' from 
'golang-github-chzyer-readline FTBFS: readline-pass-strength.go:53:14: 
undefined: pam.PasswordStrength'.
> affects 878794 src:golang-github-chzyer-readline
Bug #878794 [golang-github-nbutton23-zxcvbn-go-dev] 
golang-github-nbutton23-zxcvbn-go-dev 0.0~git20170830.0.f4cd9f5-2 causes FTBFS 
in golang-github-chzyer-readline
Added indication that 878794 affects src:golang-github-chzyer-readline
> thanks
Stopping processing here.

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



Bug#883183: libdbd-firebird-perl FTBFS on i386: t/embed-rt110979.t failure

2017-11-30 Thread Damyan Ivanov
Control: tags -1 confirmed

-=| Adrian Bunk, 30.11.2017 14:06:34 +0200 |=-
> Source: libdbd-firebird-perl
> Version: 1.26-1
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=libdbd-firebird-perl=i386=1.26-1=1511985831=0

I am able to reproduce this in a (freshly created) i386 sbuild chroot.

Not really sure what is going on, the upstream changes since 1.25 
don't seem relevant.

Ah, trying 1.25-1 builds OK, but most of the tests aren't run, because 
libfbembed is not found. The "detect Firebird API version even when 
patch are supplied via environment" is relevant, because API version 
30+ is used to check whether libfbclient2 can be used in embedded 
mode.

So it seems the root bug was there with 1.25-1 too, just not triggered 
because the embedded tests weren't run.

> DBD::FirebirdEmbedded::st finish failed: Firebird error
> -invalid database handle (no active connection) at t/embed-rt110979.t line 68.
> # Tests were run but no plan was declared and done_testing() was not seen.
> # Looks like your test exited with 255 just after 7.
> t/embed-rt110979.t .. 
> ok 1 - Connected to the database
> ok 2 - Table is 'TESTAA'
> ok 3 - CREATE TABLE 'TESTAA'
> ok 4 - create generator gen_TESTAA
> ok 5 - create trigger TESTAA_bi
> ok 6 - Insert worked
> ok 7 - Autoinc PK retrieved
> Dubious, test returned 255 (wstat 65280, 0xff00)
> All 7 subtests passed 



Processed: Re: Bug#883183: libdbd-firebird-perl FTBFS on i386: t/embed-rt110979.t failure

2017-11-30 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 confirmed
Bug #883183 [src:libdbd-firebird-perl] libdbd-firebird-perl FTBFS on i386: 
t/embed-rt110979.t failure
Added tag(s) confirmed.

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



Bug#882263: libc6-dev-mips64el-cross breaks linking executables

2017-11-30 Thread Aurelien Jarno
On 2017-11-20 21:42, Helmut Grohne wrote:
> Package: libc6-dev-mips64el-cross
> Version: 20
> Severity: serious
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> I was trying to use gcc-mips64el-linux-gnuabi64 to link a trivial
> executable:
> 
> $ echo 'int main(){return 0;}' | mips64el-linux-gnuabi64-gcc -x c - -o 
> /dev/null
> 
> With libc6-dev:mips64el installed, this just works. As soon as I install
> libc6-dev-mips64el-cross, it fails though:
> 
> /usr/lib/gcc-cross/mips64el-linux-gnuabi64/7/../../../../mips64el-linux-gnuabi64/bin/ld:
>  cannot find /usr/mips64el-linux-gnuabi64/lib/ld.so.1
> collect2: error: ld returned 1 exit status
> 
> This renders libc6-dev-mips64el-cross pretty much useless.

This is due to the following change, introduced in
cross-toolchain-base-20:

diff -Nru cross-toolchain-base-19/debian/dpkg-cross 
cross-toolchain-base-20/debian/dpkg-cross
--- cross-toolchain-base-19/debian/dpkg-cross   2016-01-21 08:48:01.0 
+
+++ cross-toolchain-base-20/debian/dpkg-cross   2017-11-19 22:01:44.0 
+
@@ -1026,6 +1026,11 @@
# Skip links that are going to point to themselves
next if ($lv eq $_);
 
+   # skip /usr/$(multiarch)/lib/ld.so.1 for mips n32 and 64.
+   # their ld.so.1 should be in lib32 and lib64.
+   next if ($multiarch =~ m/^mips[n32,64]/ && $_ =~ 
m/lib\/ld.so.1$/);
+
+   # m/lib\/ld.so.1$/);
# skip links to private modules and plugins that are not
# useful or packaged in the -cross package, basically anything
# in a directory beneath /usr/lib/. See #499292

I don't really see the point of this change, and why it would be
different the s390x cross-libc for example, which has ld64.so.1 in
/usr/s390x-linux-gnu/lib/ while the rtld directory is /lib64. Removing
this file has the same effect:

| $ echo 'int main(){return 0;}' | s390x-linux-gnu-gcc  -x c - -o /dev/null 
| $ sudo rm /usr/s390x-linux-gnu/lib/ld64.so.1  
| $ echo 'int main(){return 0;}' | s390x-linux-gnu-gcc  -x c - -o /dev/null 
| /usr/lib/gcc-cross/s390x-linux-gnu/7/../../../../s390x-linux-gnu/bin/ld: 
cannot find /usr/s390x-linux-gnu/lib/ld64.so.1
| collect2: error: ld returned 1 exit status

It therefore looks like to me that this hunk has to be reverted.

Aurelien

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



Bug#882308: http-parser 2.7 breaks ruby-em-http-request's tests

2017-11-30 Thread Christoph Biedl
Control: tags 882308 confirmed help

No clue, I don't speak Ruby and after some looking around I'm rather
lost and could use some advice.

Matthias Klose wrote...

> 1) EventMachine::HttpRequest should close connection on
> invalid HTTP response Failure/Error: if !client.continue?
> 
>   NoMethodError:
>   undefined method `continue?' for
> nil:NilClass#

The thing that puzzles me is the "nil:NilClass" - it's probably
supposed to be "EventMachine::HttpClient" so I assume initialization
failed but this did not abort program execution.

Christoph


signature.asc
Description: Digital signature


Processed: Re: Bug#882308: http-parser 2.7 breaks ruby-em-http-request's tests

2017-11-30 Thread Debian Bug Tracking System
Processing control commands:

> tags 882308 confirmed help
Bug #882308 [src:http-parser] http-parser 2.7 breaks ruby-em-http-request's 
tests
Added tag(s) help and confirmed.

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



Bug#876818: marked as done (golang-github-vbatts-tar-split FTBFS with Go 1.9)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 21:15:29 +
with message-id 
and subject line Bug#876818: fixed in golang-github-vbatts-tar-split 0.10.2-1
has caused the Debian Bug report #876818,
regarding golang-github-vbatts-tar-split FTBFS with Go 1.9
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.)


-- 
876818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-vbatts-tar-split
Version: 0.9.13-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-vbatts-tar-split.html

...
--- FAIL: TestRoundTrip (0.00s)
tar_test.go:121: Header mismatch.
 got &{Name:file.txt Mode:0 Uid:2097152 Gid:0 Size:18 
ModTime:2018-10-29 03:44:20 + UTC Typeflag:0 Linkname: Uname: Gname: 
Devmajor:0 Devminor:0 AccessTime:0001-01-01 00:00:00 + UTC 
ChangeTime:0001-01-01 00:00:00 + UTC Xattrs:map[]}
want &{Name:file.txt Mode:0 Uid:2097152 Gid:0 Size:18 
ModTime:2018-10-29 03:44:20 + UTC m=-0.937700630 Typeflag:0 Linkname: 
Uname: Gname: Devmajor:0 Devminor:0 AccessTime:0001-01-01 00:00:00 + UTC 
ChangeTime:0001-01-01 00:00:00 + UTC Xattrs:map[]}
--- End Message ---
--- Begin Message ---
Source: golang-github-vbatts-tar-split
Source-Version: 0.10.2-1

We believe that the bug you reported is fixed in the latest version of
golang-github-vbatts-tar-split, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated 
golang-github-vbatts-tar-split 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, 30 Nov 2017 21:21:16 +0100
Source: golang-github-vbatts-tar-split
Binary: tar-split golang-github-vbatts-tar-split-dev
Architecture: source
Version: 0.10.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Dr. Tobias Quathamer 
Description:
 golang-github-vbatts-tar-split-dev - tar archive assembly/disassembly (source)
 tar-split  - tar archive assembly/disassembly
Closes: 876818
Changes:
 golang-github-vbatts-tar-split (0.10.2-1) unstable; urgency=medium
 .
   [ Paul Tagliamonte ]
   * Team upload.
   * Use a secure transport for the Vcs-Git and Vcs-Browser URL
   * Remove Built-Using from arch:all -dev package
 .
   [ Tim Potter ]
   * Add me to uploaders
 .
   [ Dr. Tobias Quathamer ]
   * New upstream version 0.10.2
 - Fixes FTBFS with header mismatch. Closes: #876818
 - Refresh patch
   * Use debhelper v10
   * Update team name
   * Update to Standards-Version 4.1.1
 - Use HTTPS URL for d/copyright
 - Use Priority: optional
   * Use golang-any instead of golang-go
   * Update build dependencies
   * Use wrap-and-sort for d/control
   * Update d/copyright
   * Fix typo in description, spotted by lintian
   * Remove unneeded extra license file
Checksums-Sha1:
 2642f4023f1f22e97b2d3a335368a944c177f591 2399 
golang-github-vbatts-tar-split_0.10.2-1.dsc
 ad5a08ea0c2ab2aefe7f659015eb93e000b98f3d 46456 
golang-github-vbatts-tar-split_0.10.2.orig.tar.xz
 ee81f53b7c9c5fd29434db8820eb3427a70c969e 3896 
golang-github-vbatts-tar-split_0.10.2-1.debian.tar.xz
 9d2d5b47b44411956089c314ba2019b0cac6e933 6321 
golang-github-vbatts-tar-split_0.10.2-1_amd64.buildinfo
Checksums-Sha256:
 89fa0016c0c481c80f28b418a42d481044f127f648c7e71610b1f583649dfdfd 2399 
golang-github-vbatts-tar-split_0.10.2-1.dsc
 7012c8332afd35b5645bd6607ca33c8de53f4f3939c51aeeca9f0ab7984844fb 46456 
golang-github-vbatts-tar-split_0.10.2.orig.tar.xz
 221fefac82cc790ce37b53b4f3f3bfd8db358ed7b4ab6f33276a974d720133c8 3896 
golang-github-vbatts-tar-split_0.10.2-1.debian.tar.xz
 e4c53173708d40395249d4695b1c696911d2ddda3bbb59df8327257d9012f3ce 6321 
golang-github-vbatts-tar-split_0.10.2-1_amd64.buildinfo
Files:
 ee49e6c040e0db6a64a64a5c0ad86d1f 2399 devel optional 
golang-github-vbatts-tar-split_0.10.2-1.dsc
 

Bug#876521: FTBFS with CGAL 4.11

2017-11-30 Thread Sebastiaan Couwenberg
Hi Joachim,

On 11/30/2017 08:11 PM, Joachim Reichel wrote:
> On 12.11.2017 22:20, Sebastiaan Couwenberg wrote:
>> You shouldn't have waited for this issue to request the transition slot.
>> As I said before, I'll remove the SFCGAL dependency from PostGIS if this
>> issue is not resolved when the CGAL transition starts. That way we can
>> keep postgis is testing.
> 
> Don't worry, sfcgal was not the only reverse dependency that needs more than a
> binNMU.

Thanks for the notice. I've just uploaded a new revision of postgis
without SFCGAL support.

Hopefully upstream will fix this issue soon. Otherwise I'll have the
sfcgal package removed from Debian.

Kind Regards,

Bas

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



Processed: severity of 883071 is normal, user release.debian....@packages.debian.org, usertagging 883071 ...

2017-11-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 883071 normal
Bug #883071 [release.debian.org] [release.debian.org] need to recompile 
eclipse-titan (6.1.0-1) in stable
Severity set to 'normal' from 'grave'
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
a...@adam-barratt.org.uk).
> usertags 883071 + nmu
There were no usertags set.
Usertags are now: nmu.
> tags 883071 + stretch
Bug #883071 [release.debian.org] [release.debian.org] need to recompile 
eclipse-titan (6.1.0-1) in stable
Added tag(s) stretch.
> retitle 883071 nmu: eclipse-titan
Bug #883071 [release.debian.org] [release.debian.org] need to recompile 
eclipse-titan (6.1.0-1) in stable
Changed Bug title to 'nmu: eclipse-titan' from '[release.debian.org] need to 
recompile eclipse-titan (6.1.0-1) in stable'.
> thanks
Stopping processing here.

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



Processed: Not a problem in stretch

2017-11-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 876521 buster sid
Bug #876521 [src:sfcgal] FTBFS with CGAL 4.11
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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



Bug#874295: Not a bug

2017-11-30 Thread Ben Finney
Ian Jackson  writes:

> Ben Finney writes ("Re: Bug#874295: Not a bug"):
> > (Yes, I think a web browser should not download and execute
> > arbitrary JavaScript either. That one problem remains unaddressed is
> > not a justification for the same problem elsewhere.)
>
> This is obviously out of scope for the discussion of this bug.

Certainly. I was responding parenthetically to a point that, I agree
with you, was out of scope.

-- 
 \  “I would rather be exposed to the inconveniences attending too |
  `\  much liberty than those attending too small a degree of it.” |
_o__)—Thomas Jefferson, 1791-12-23 |
Ben Finney 



Bug#867166: marked as done (Future of linux-grec in Debian)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 20:36:25 +0100
with message-id <1512070585.2719.47.ca...@debian.org>
and subject line Re: Bug#867166: Future of linux-grec in Debian
has caused the Debian Bug report #867166,
regarding Future of linux-grec in Debian
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.)


-- 
867166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux-grsec
Severity: serious
I wanted to ask you about the future of linux-grsec in debian. The package 
wasn't updated for some time and it's now at 4.9.18 version while last official 
grsecurity version is 4.9.24. Additionally there are few forward ports of 
grsecurity for 4.9 LTS kernel line [1],[2] .
As 4.9 LTS kernel is used in current Debian stable release, something like 
linux-unofficial_grsec, based on forward grsec ports for 4.9 kernel would be a 
great addition for stable-backports and/or unstable. It could be abandoned when 
4.9 kernel gets EOL status. Hopefully by then mainline linux will get some 
security improvements, currently worked on linux-hardened project [2] and KSPP .
As for now there is nothing comparable to grsecurity and loosing it completely 
would be huge blow for debian community. I know that Alpine Linux developers 
decided to continue maintaining their grsec a like kernel [3].
It will be nice to clarify linux-grsec package situation as users now get stuck 
in limbo.
[1]https://github.com/dapperlinux/dapper-secure-kernel-patchset-stable
[2] https://github.com/minipli/linux-unofficial_grsec/releases
[3] https://github.com/thestinger/linux-hardened
[4] https://pkgs.alpinelinux.org/package/edge/main/x86_64/linux-hardened--- End Message ---
--- Begin Message ---
On Wed, 2017-11-29 at 08:43 -0500, Jordan Glover wrote:
> I think this bug can be closed now.
> 

Closing then :)
-- 
Yves-Alexis

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


Processed: Re: Bug#876521: FTBFS with CGAL 4.11

2017-11-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 876521 serious
Bug #876521 [src:sfcgal] FTBFS with CGAL 4.11
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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



Bug#883212: blktap FTBFS with glibc 2.25

2017-11-30 Thread Adrian Bunk
Source: blktap
Version: 2.0.90-4
Severity: serious
Tags: buster sid

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

...
tap-ctl-allocate.c: In function 'tap_ctl_make_device':
tap-ctl-allocate.c:114:13: error: In the GNU C Library, "makedev" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "makedev", include 
 directly. If you did not intend to use a system-defined macro
 "makedev", you should undefine it after including . [-Werror]
  err = mknod(devname, perm, makedev(major, minor));
 ^~~ 



Bug#826056: marked as done (smokeping: please Build-Depend on rename)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 18:20:52 +
with message-id 
and subject line Bug#826056: fixed in smokeping 2.6.11-4
has caused the Debian Bug report #826056,
regarding smokeping: please Build-Depend on rename
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.)


-- 
826056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: smokeping
Version: 2.6.11-3
Severity: normal
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition rename-deprecation

Dear maintainer,

This package was found to contain uses of the 'rename' and/or 'prename'
(which is an alias) command. This was previously implemented by a script
added to the perl package by Debian, but there is now a maintained
alternative in the 'rename' package.

Please add a Build-Depends on 'rename', to avoid breakage in your
package when we remove the rename script from the perl package
(expected after the release of stretch). Additionally, if you are
currently using 'prename', please use 'rename' (which is handled by the
alternatives mechanism) or file-rename, which is the new implementation.

You can see more background about this change at
.

Thanks,
Dominic

Details of the use of (p)rename in your package follow:

debian/rules
38: rename 's/\.dist$$//' $(TMP)/etc/smokeping/*.dist
--- End Message ---
--- Begin Message ---
Source: smokeping
Source-Version: 2.6.11-4

We believe that the bug you reported is fixed in the latest version of
smokeping, 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 826...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated smokeping 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: Tue, 28 Nov 2017 11:57:04 -0500
Source: smokeping
Binary: smokeping
Architecture: source all
Version: 2.6.11-4
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Description:
 smokeping  - latency logging and graphing system
Closes: 760945 826056 847924
Changes:
 smokeping (2.6.11-4) unstable; urgency=medium
 .
   * add missing build-dep on rename (Closes: #826056)
   * check config file validity - thanks Matus UHLAR (Closes: #847924)
   * fix slave permissions configuration - thanks Sven Hartge (Closes: #760945)
   * bump dh compat, no change
Checksums-Sha1:
 b3c0bf3281c65838236e4b0fe6bae4ef800111e4 1840 smokeping_2.6.11-4.dsc
 358830a8e6d7711af965e271480d78ee7c20cd4c 21576 smokeping_2.6.11-4.debian.tar.xz
 08e1b25f63ef0dd54985ecee2538ca898ea15bc9 407012 smokeping_2.6.11-4_all.deb
 1527ed31284ea367511817122643dc11226a80b1 8144 
smokeping_2.6.11-4_amd64.buildinfo
Checksums-Sha256:
 307a246c2f2bb1574146a2b2403c646978ca1a0d8ecf14103f910187e668aee4 1840 
smokeping_2.6.11-4.dsc
 9a48e578a1e96eebdb6c66bc6cbf1f3e2e8ce272a54e7ef0374a5f73b974370d 21576 
smokeping_2.6.11-4.debian.tar.xz
 b1daba4c8a3c3e639ee6a95cb51216a3692dfb97fa49735898a870ae0c324318 407012 
smokeping_2.6.11-4_all.deb
 a38ac0aab1c5d37be6dd7fe5398a6faed272eaf6ce0dc7b361f4d5079f9c5509 8144 
smokeping_2.6.11-4_amd64.buildinfo
Files:
 8ddcf7acc6ece0618a536c8bc264814a 1840 net extra smokeping_2.6.11-4.dsc
 91f1d3cc4ab79a8d03f22fbd14f0483a 21576 net extra 
smokeping_2.6.11-4.debian.tar.xz
 e28345ad11b4e6b059c6d1800b2623ff 407012 net extra smokeping_2.6.11-4_all.deb
 a654f6e8495bf694e5e0bdd484adc987 8144 net extra 
smokeping_2.6.11-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAlogROoACgkQPqHd3bJh
2Xu1AggAn1alJiFFbaGvmpI2h7A66D8tLST2rwJqnR2uBB1OqPgo27QluMXzM5eC
Q16ZwB0qFz3sqg5X08AtHMT95n9RRJfnw5IE43/Lio4u48LrKJwlexQ9ZE6UTTuf
1aV25CFDdrR2k4cWCenp6QqcgV2TIt/QBVGqYu1kZQr6bWpfEcYV9JwT1/g/P2FD
RHDWdp24zsiySwriUY+5dTpSLDr+8YJRqQYmVk5XkMidejQIke3SHCIRHLyBfySG
DKI704i0Dd+DI3QHKqxoTYsVwehn0CFGf6qiRTA7EwDy5KwHRo1obFyvvmfASBWS
IZGrgl/ZF5s5wWzS8zqdc9NxP7UPwA==
=ocY1
-END PGP SIGNATURE End Message ---


Bug#859550: pgadmin3: Please migrate to openssl1.1 in buster

2017-11-30 Thread Björn Harrtell
On Sun, 19 Nov 2017 03:51:19 +0100 Cyril Brulebois  wrote:
> Control: tag -1 patch
>
> Hi Sebastian, hi Denis,
>
> Sebastian Andrzej Siewior  (2017-11-14):
> > On 2017-10-21 16:37:14 [+0200], Denis Briand wrote:
> > > Pgadmin3 is no longer supported by upstream team and I haven't
> > > enought skills in openssl lib to fix this bug. Feel free to raise
> > > the bug severity to prevent pgadmin3 to be in buster.
> > >
> > > In a marvelous world we should build pgadmin4 instead but it's
> > > completly not the same interface (web) and needs many work hours and
> > > skills in web software package building.
> >
> > What is your final pgadmin plan for Buster? According to the webpage 3
> > is no longer supported. Do you want 3 in or plan to package 4?
>
> I've had the pleasure to discuss this with Denis at MiniDebConf in
> Toulouse, and AFAIUI it seems it would be nice to keep pgadmin3 around
> until pgadmin4 gets packaged.
>
> Looking at the build failure, it happens in paths involving libssh2:
>   pgadmin/libssh2
>   pgadmin/include/libssh2
>
> Since this seemed like an embedded code copy, I've looked into libssh2
> vs. openssl 1.1, and found this:
>   https://github.com/libssh2/libssh2/pull/70/commits
>
> I've applied both commits to openssl.{c,h} in pgadmin3 (need to patch
> both of them manually since they are not in the same directory):
>
https://github.com/libssh2/libssh2/pull/70/commits/a62842a9275fe3d6ba4b67b7f01ab3f00d086f83
>
https://github.com/libssh2/libssh2/pull/70/commits/eb497bddd5f382ca1468d72c6cd3d804ca68afb5
>
> (Add “.patch” at the end of the URL to get a raw patch.)
>
> The build can then be resumed but fails later, possibly because patches
> in libssh2 were incomplete or because openssl made more changes. I
> didn't investigate at this point since it's clear that having embedded
> code copies is awful already.
>   https://wiki.debian.org/EmbeddedCodeCopies
>
> I've briefly looked into configure.ac to see how library detection is
> performed, and found out that the embedded libssh2 depends on openssl
> being activated through ./configure; it's the default, but can be
> switched off, to use libgcrypt instead. I've added two flags in
> debian/rules, which made it possible to build the package. I didn't
> update build-depends, and I didn't test a full build under cowbuilder or
> sbuild, but that might be something that would help you keep pgadmin3 in
> testing a bit longer. See attached source debdiff.
>
> Please make sure to test your package extensively, I only checked it
> builds with these settings; also feel free to reword the changelog entry
> as you wish. :)
>
>
> Denis, On a personal note: you did a very good job organizing this
> Mini-DebConf, and an even better job getting people to look at your RC
> bugs! ;)
>

Would be sad to see pgadmin3 go, hoping for the patch to be accepted.


Bug#882889: marked as done (jsonlint FTBFS with phpunit 6.4.4-2)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 17:33:45 +
with message-id 
and subject line Bug#882889: fixed in jsonlint 1.6.2-1
has caused the Debian Bug report #882889,
regarding jsonlint FTBFS with phpunit 6.4.4-2
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.)


-- 
882889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jsonlint
Version: 1.6.1-1
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/jsonlint-1.6.1'
phpunit --bootstrap src/Seld/JsonLint/autoload.php
PHP Fatal error:  Class 'PHPUnit_Framework_TestCase' not found in 
/build/1st/jsonlint-1.6.1/tests/JsonParserTest.php on line 16
debian/rules:16: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 255
--- End Message ---
--- Begin Message ---
Source: jsonlint
Source-Version: 1.6.2-1

We believe that the bug you reported is fixed in the latest version of
jsonlint, 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 882...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated jsonlint 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, 30 Nov 2017 07:09:43 -1000
Source: jsonlint
Binary: jsonlint
Architecture: source
Version: 1.6.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Description:
 jsonlint   - validating parser of JSON data structures
Closes: 882889
Changes:
 jsonlint (1.6.2-1) unstable; urgency=medium
 .
   [ Jordi Boggiano ]
   * Rename readme file
 .
   [ David Prévot ]
   * Move to namespaced phpunit versions (Closes: #882889)
   * Update Standards-Version to 4.1.1
   * Adapt packaging to renamed file
Checksums-Sha1:
 6954e21acc38aa76d654ed1b9e7d247b445aa9ca 1690 jsonlint_1.6.2-1.dsc
 66d2ce96fa9e50b4984318a31125752c8bc6922d 11620 jsonlint_1.6.2.orig.tar.gz
 1cf2eb5f6ead2f4b68470d83b852204412a88355 3572 jsonlint_1.6.2-1.debian.tar.xz
Checksums-Sha256:
 7e1a01616fff41579c7719249d6c90c682395cb2a10c4b59b23dde3fa0fce1af 1690 
jsonlint_1.6.2-1.dsc
 d514d482abf2b969f7052fd09236c78add841ffc45a8907b4db85a38ce3022b2 11620 
jsonlint_1.6.2.orig.tar.gz
 92c181b5e1588a3fd2ad5a67db210802ce7649af9f6482e0bfdf48b2c1671f99 3572 
jsonlint_1.6.2-1.debian.tar.xz
Files:
 309259584d22e060b784bd3c6adb8ae9 1690 php optional jsonlint_1.6.2-1.dsc
 dba451dafa179e278566701989f7931f 11620 php optional jsonlint_1.6.2.orig.tar.gz
 1d6a5246d11aa96b52d7e73e6caa7b06 3572 php optional 
jsonlint_1.6.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAlogPAkACgkQBYwc+UT2
vTw27ggAlSokl9NiAJtTtQp+3TEn+Ix8SiXk0rP9LHvUqXL0FNlK1PmlaeXNb3aY
SheEueCgDQggyk7fK9RV1zE6LnroO5t8quxvcTUvcI+j9vQphg+AALFhBYYxrBIe
Cd1BTXucDc0eU5J7W+ta6GPQ+U7FY44MsnTadIJnDH/c38hYziHbqjZbKA+SkrbI
obT7UDS7P3ZPGNfJTyNzrYEEXdE+ykviv4gmXq/2cNodRyAeSfFFr9SVhXAYTc7h
Z2W5GqWzLqqJOff0LM9F5ZBDEBN1zvMONgltUXKgRhQHt1PwrZyqwEpAOSYSPXUZ
bIv9mbCNWOuyLMyZ9XyilDKJ9SbaxA==
=uHDj
-END PGP SIGNATURE End Message ---


Processed: [bts-link] source package src:xrdp

2017-11-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:xrdp
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #882463 (http://bugs.debian.org/882463)
> # Bug title: xrdp: CVE-2017-16927: Buffer-overflow in scp_v0s_accept function 
> in session manager
> #  * https://github.com/neutrinolabs/xrdp/pull/958
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 882463 + fixed-upstream
Bug #882463 [src:xrdp] xrdp: CVE-2017-16927: Buffer-overflow in scp_v0s_accept 
function in session manager
Added tag(s) fixed-upstream.
> usertags 882463 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 882463 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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



Processed: [bts-link] source package gcc-7

2017-11-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package gcc-7
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #881918 (http://bugs.debian.org/881918)
> # Bug title: gfortran-7: ICE building open-coarrays
> #  * http://gcc.gnu.org/PR83021
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 881918 + fixed-upstream
Bug #881918 [gfortran-7] gfortran-7: ICE building open-coarrays
Added tag(s) fixed-upstream.
> usertags 881918 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 881918 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> thanks
Stopping processing here.

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



Bug#881058: marked as done (gwhois: please switch Depends from lynx-cur to lynx)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 16:49:35 +
with message-id 
and subject line Bug#881058: fixed in gwhois 20120626-1.2
has caused the Debian Bug report #881058,
regarding gwhois: please switch Depends from lynx-cur to lynx
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.)


-- 
881058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gwhois
Version: 20120626-1.1
Severity: serious

Hi,

lynx-cur was a transitional package in stretch and is now gone from
sid. Please update the dependency to lynx.


Andreas
--- End Message ---
--- Begin Message ---
Source: gwhois
Source-Version: 20120626-1.2

We believe that the bug you reported is fixed in the latest version of
gwhois, 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 881...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated gwhois 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: Wed, 15 Nov 2017 16:44:51 +0100
Source: gwhois
Binary: gwhois
Architecture: source all
Version: 20120626-1.2
Distribution: unstable
Urgency: medium
Maintainer: Juliane Holzt 
Changed-By: gregor herrmann 
Description:
 gwhois - generic Whois Client / Server
Closes: 881058
Changes:
 gwhois (20120626-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "please switch Depends from lynx-cur to lynx":
 do as the bug report requests.
 (Closes: #881058)
Checksums-Sha1:
 809ec3f2c64cd9d1c8c13181b707b48ab00ccbed 1545 gwhois_20120626-1.2.dsc
 3f242278b261a02399c443020cd77791536ebcd7 41800 gwhois_20120626-1.2.tar.gz
 8dfee989c4dae017589e798b6255324b27903e52 34800 gwhois_20120626-1.2_all.deb
 1b008f5c1343a3ab91d55e9f44862a10bbcd5d98 5477 
gwhois_20120626-1.2_amd64.buildinfo
Checksums-Sha256:
 67033a4e620c80e0e0671b7d760a5d108086fbd515ff0c7d3172985750021677 1545 
gwhois_20120626-1.2.dsc
 4932031a58747b7a5ed713f4de61c91c38776f6a162a477433dd62efde20f966 41800 
gwhois_20120626-1.2.tar.gz
 3fd1f0fc941e0e0f910584915856d048da153bf81d163ea6cbcfd5f1f0ac3b57 34800 
gwhois_20120626-1.2_all.deb
 93758914f9032ecac1b54ae88019a1edcd90cb01bb794802f407b91e32ddfcf4 5477 
gwhois_20120626-1.2_amd64.buildinfo
Files:
 fc8304e62c685d094d53e9427e9a7331 1545 net optional gwhois_20120626-1.2.dsc
 951083af913806333ab0259e26c9a6b4 41800 net optional gwhois_20120626-1.2.tar.gz
 cd257fc880ea74ac38c44c8096aa5d65 34800 net optional gwhois_20120626-1.2_all.deb
 fd59a711571d80efc4ac460366b6e646 5477 net optional 
gwhois_20120626-1.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAloMYRZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbUJA/9EPjFDz6QT5A+JLSYjk1J6rOiIKnI8oBO+uDTW+L7Mi3fx/VzpjbgATCP
ABIQYGjKeNYeQSt0sgPjICvKctCwOwBdrt8ZGO46lDvH3gprNo9e+OJturZubOEI
cnUJZUfTxisidqeOwkFleHMp+HUNzAFstV5mewD5RF3me5vqpeAvYhO46KNFsZjM
vV47PNJYYCKG/F730/biM7O/zpiVPgiOtBdZhYTrB/Bq1bhual9xW8rQkgYZ0PbF
yammSZNLxnYXAogAdVEHNV6sx2RXxqDh+LOFZ6zW3O5URtP3/ywoFTQXrXa0NQCR
Wf4Vnw/aeITFYnvwAD9D55ILmV0zLsid6Ny/yQDEHZis2lU0Gl3PSygMYNFhcUl4
Phtm6H/92mGXQx5vTN+9hxZVKYam1df7CoEST7BNQdOLcKKxJhvO4TjuOHNlVv7M
M1EYT24OKAhYQ+htimFEBdJDgKExWYzyPuHvMqaLoQ8g3O4INhoYD25Mpzh0DwFO
5CjLTShd6Payv7hbVdNQpHjSEtxkCKQvyuSfyK3fLgNrwTG83uqM8W5wGEm2Tgld
i+ok1zqW1V4EKAcX2at/VZ7U5vvlwqo8XzknJBQB1tYk8ld4Tciy73uwwlFFFjTg
S435bomnj9wUzLLxfWgo7I+CkJtirQwGHLvFqBQ9RaDWsLRWYEE=
=yolr
-END PGP SIGNATURE End Message ---


Bug#878107: src:pcre3: stack frame size detection is broken

2017-11-30 Thread Matthew Vernon

On 20/11/17 22:22, Adrian Bunk wrote:

[snip]


One real-world problem where this dodgy code does break has been found
to affect real software, and the suggested patch that disables some
otherwise possible optimizations for one function is confirmed to
workaround this specific breakage.

This is a quite minimal workaround for this specific breakage.


[snip]

Thanks for your mail, and for your patience. I have applied the patch, 
and assuming my builds+testing go OK, will be uploading it shortly.


Regards,

Matthew



Bug#878107: marked as done (src:pcre3: stack frame size detection is broken)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 16:21:54 +
with message-id 
and subject line Bug#878107: fixed in pcre3 2:8.39-6
has caused the Debian Bug report #878107,
regarding src:pcre3: stack frame size detection is broken
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.)


-- 
878107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pcre3
Version: 2:8.39-5
Severity: grave

Dear Maintainer,

the system-wide pcre3 library stack frame size detection is broken as described 
in
https://bugs.exim.org/show_bug.cgi?id=2173

and that breaks at least ppc64el and s390x build causing segfaults in the test 
suite (+ autopkgtest).

The patch from Sergei @ MariaDB is quite simple at it should pose no risk 
applying it:

diff --git a/pcre/pcre_exec.c b/pcre/pcre_exec.c
--- a/pcre/pcre_exec.c
+++ b/pcre/pcre_exec.c
@@ -509,6 +509,12 @@
  (e.g. stopped by repeated call or recursion limit)
 */
 
+#ifdef __GNUC__
+static int
+match(REGISTER PCRE_PUCHAR eptr, REGISTER const pcre_uchar *ecode,
+  PCRE_PUCHAR mstart, int offset_top, match_data *md, eptrblock *eptrb,
+  unsigned int rdepth) __attribute__((noinline,noclone));
+#endif
 static int
 match(REGISTER PCRE_PUCHAR eptr, REGISTER const pcre_uchar *ecode,
 PCRE_PUCHAR mstart, int offset_top, match_data *md, eptrblock *eptrb,

Please apply the patch in the next maintenance window for PCRE3,
including stable and possibly oldstable as this causes segfaults (at
least) in src:mariadb-10.1 on affected platforms (and both ppc64el and
s390x are our release architectures).

Cheers,
Ondrej

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: pcre3
Source-Version: 2:8.39-6

We believe that the bug you reported is fixed in the latest version of
pcre3, 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 878...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthew Vernon  (supplier of updated pcre3 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, 30 Nov 2017 15:38:57 +
Source: pcre3
Binary: libpcre3 libpcre3-udeb libpcrecpp0v5 libpcre3-dev libpcre3-dbg pcregrep 
libpcre16-3 libpcre32-3
Architecture: i386 source
Version: 2:8.39-6
Distribution: unstable
Urgency: medium
Maintainer: Matthew Vernon 
Changed-By: Matthew Vernon 
Closes: 876299 878107
Description: 
 libpcre16-3 - Old Perl 5 Compatible Regular Expression Library - 16 bit runtime
 libpcre32-3 - Old Perl 5 Compatible Regular Expression Library - 32 bit runtime
 libpcre3-dbg - Old Perl 5 Compatible Regular Expression Library - debug symbols
 libpcre3-dev - Old Perl 5 Compatible Regular Expression Library - development 
fi
 libpcre3   - Old Perl 5 Compatible Regular Expression Library - runtime files
 libpcre3-udeb - Old Perl 5 Compatible Regular Expression Library - runtime 
files  (udeb)
 libpcrecpp0v5 - Old Perl 5 Compatible Regular Expression Library - C++ runtime 
fi
 pcregrep   - grep utility that uses perl 5 compatible regexes.
Changes:
 pcre3 (2:8.39-6) unstable; urgency=medium
 .
   * patch from Sergei from MariaDB (via Ondřej Surý) to fix stack frame
 size detection (Closes: #878107, #876299)
Checksums-Sha1: 
 3f86e02ecc1095fa1d2953382fbba54204cbb752 2224 pcre3_8.39-6.dsc
 d95cd8676fafa3d661c4b053eded917207f6134c 26125 pcre3_8.39-6.debian.tar.gz
 faf91e800c9dbc3173dae33536fc86ee5038ef38 5637 pcre3_8.39-6_source.buildinfo
 91c53955141e813cc4e0a3c360cecc2b249eb69f 256916 libpcre16-3_8.39-6_i386.deb
 c0f67bc7544e47144b889720bf42fe5d6ed91694 799800 libpcre3-dbg_8.39-6_i386.deb
 d122090ae4df221c5bcd513b55769a7606f687f0 647320 libpcre3-dev_8.39-6_i386.deb
 

Bug#876299: marked as done (pcre3: ftbfs on s390x, test failures)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 16:21:54 +
with message-id 
and subject line Bug#876299: fixed in pcre3 2:8.39-6
has caused the Debian Bug report #876299,
regarding pcre3: ftbfs on s390x, 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.)


-- 
876299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pcre3
Version: 2:8.39-5
Severity: serious
Tags: sid butcher

ftbfs on s390x, test failures

/usr/bin/make check VERBOSE=1
make[1]: Entering directory '/<>'
/usr/bin/make  check-am
make[2]: Entering directory '/<>'
/usr/bin/make
make[3]: Entering directory '/<>'
/usr/bin/make  all-am
make[4]: Entering directory '/<>'
make[4]: Leaving directory '/<>'
make[3]: Leaving directory '/<>'
/usr/bin/make  check-TESTS
make[3]: Entering directory '/<>'
make[4]: Entering directory '/<>'
PASS: pcrecpp_unittest
PASS: pcre_scanner_unittest
PASS: pcre_stringpiece_unittest
FAIL: RunTest
PASS: RunGrepTest
=
   PCRE 8.39: ./test-suite.log
=

# TOTAL: 5
# PASS:  4
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: RunTest
=


PCRE C library tests using test data from ./testdata
PCRE version 8.39 2016-06-14

 Testing 8-bit library 

Test 1: Main functionality (Compatible with Perl >= 5.10)
  OK
  OK with study
Test 2: API, errors, internals, and non-Perl stuff (not UTF-8)
  OK
  OK with study
Cannot test locale-specific features - none of the 'fr_FR', 'fr' or
'french' locales exist, or the "locale" command is not available
to check for them.

Test 4: UTF-8 support (Compatible with Perl >= 5.10)
  OK
  OK with study
Test 5: API, internals, and non-Perl stuff for UTF-8 support
  OK
  OK with study
Test 6: Unicode property support (Compatible with Perl >= 5.10)
  OK
  OK with study
Test 7: API, internals, and non-Perl stuff for Unicode property support
  OK
  OK with study
Test 8: DFA matching main functionality
  OK
  OK with study
Test 9: DFA matching with UTF-8
  OK
  OK with study
Test 10: DFA matching with Unicode properties
  OK
  OK with study
Test 11: Internal offsets and code size tests
  OK
  OK with study
Test 12: JIT-specific features (when JIT is available)
  Skipped because JIT is not available or not usable
Test 13: JIT-specific features (when JIT is not available)
  OK
Test 14: Specials for the basic 8-bit library
  OK
  OK with study
Test 15: Specials for the 8-bit library with UTF-8 support
  OK
  OK with study
Test 16: Specials for the 8-bit library with Unicode propery support
  OK
  OK with study
Test 17: Specials for the basic 16/32-bit library
  Skipped when running 8-bit tests
Test 18: Specials for the 16/32-bit library with UTF-16/32 support
  Skipped when running 8-bit tests
Test 19: Specials for the 16/32-bit library with Unicode property support
  Skipped when running 8-bit tests
Test 20: DFA specials for the basic 16/32-bit library
  Skipped when running 8-bit tests
Test 21: Reloads for the basic 16/32-bit library
  Skipped when running 8-bit tests
Test 22: Reloads for the 16/32-bit library with UTF-16/32 support
  Skipped when running 8-bit tests
Test 23: Specials for the 16-bit library
  Skipped when running 8/32-bit tests
Test 24: Specials for the 16-bit library with UTF-16 support
  Skipped when running 8/32-bit tests
Test 25: Specials for the 32-bit library
  Skipped when running 8/16-bit tests
Test 26: Specials for the 32-bit library with UTF-32 support
  Skipped when running 8/16-bit tests

 Testing 16-bit library 

Test 1: Main functionality (Compatible with Perl >= 5.10)
  OK
  OK with study
Test 2: API, errors, internals, and non-Perl stuff (not UTF-16)
Segmentation fault

** Test 2 requires a lot of stack. If it has crashed with a
** segmentation fault, it may be that you do not have enough
** stack available by default. Please see the 'pcrestack' man
** page for a discussion of PCRE's stack usage.

FAIL RunTest (exit status: 1)


Testsuite summary for PCRE 8.39

# TOTAL: 5
# PASS:  4
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log

Makefile:2618: recipe for target 'test-suite.log' failed
make[4]: *** 

Bug#883102: (no subject)

2017-11-30 Thread Mauro Sacchetto
The same error for Italian version:
==
Preparativi per estrarre .../13-kwrite_4%3a17.08.3-1_amd64.deb...
Estrazione di kwrite (4:17.08.3-1) su (4:16.08.3-1+b1)...
dpkg: errore nell'elaborare l'archivio /tmp/apt-dpkg-install-pOWute/13-
kwrite_4%3a17.08.3-1_amd64.deb (--unpack):
 tentata sovrascrittura di "/usr/share/doc/HTML/it/kwrite/index.cache.bz2" 
presente anche nel pacchetto kde-l10n-it 4:16.04.3-5
==

ms



Bug#880508: marked as done (openvswitch: FTBFS on mips64el: ofproto-dpif test 1072 fails repeatedly)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 15:11:06 +
with message-id 
and subject line Bug#880508: fixed in openvswitch 2.8.1+dfsg1-4
has caused the Debian Bug report #880508,
regarding openvswitch: FTBFS on mips64el: ofproto-dpif test 1072 fails 
repeatedly
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.)


-- 
880508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openvswitch
Version: 2.8.1+dfsg1-2
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-m...@lists.debian.org
Usertags: mips64el

The latest build of openvswitch for mips64el failed due to repeated
failure of test

  1072: ofproto-dpif - controller action without megaflows FAILED 
(ofproto-dpif.at:1686)

which appears to have logged an extra packet:

  ./ofproto-dpif.at:1686: cat ofctl_monitor.log
  --- - 2017-11-01 06:15:54.072354362 +
  +++ 
/<>/openvswitch-2.8.1+dfsg1/tests/testsuite.dir/at-groups/1072/stdout 
  2017-11-01 06:15:54.058645194 +
  @@ -2,4 +2,6 @@
   
vlan_tci=0x,dl_src=50:54:00:00:00:09,dl_dst=50:54:00:00:00:0a,dl_type=0x4321
   NXT_PACKET_IN (xid=0x0): cookie=0x0 total_len=14 in_port=1 (via action) 
data_len=14 (unbuffered)
   
vlan_tci=0x,dl_src=50:54:00:00:00:09,dl_dst=50:54:00:00:00:0a,dl_type=0x4321
  +NXT_PACKET_IN (xid=0x0): cookie=0x0 total_len=14 in_port=1 (via action) 
data_len=14 (unbuffered)
  
+vlan_tci=0x,dl_src=50:54:00:00:00:09,dl_dst=50:54:00:00:00:0a,dl_type=0x4321

You can find the full log at
https://buildd.debian.org/status/fetch.php?pkg=openvswitch=mips64el=2.8.1%2Bdfsg1-2=1509517022=0

FWIW, there were also transient failures of tests 15, 788, and 2319;
and test 1072 also failed repeatedly on the non-release architecture
hppa (along with several other tests; detailed report to follow).

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: openvswitch
Source-Version: 2.8.1+dfsg1-4

We believe that the bug you reported is fixed in the latest version of
openvswitch, 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 880...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated openvswitch 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, 30 Nov 2017 11:37:36 +0100
Source: openvswitch
Binary: openvswitch-common openvswitch-dbg openvswitch-dev openvswitch-ipsec 
openvswitch-pki openvswitch-switch openvswitch-testcontroller openvswitch-vtep 
ovn-central ovn-controller-vtep ovn-host python-openvswitch python3-openvswitch
Architecture: source amd64 all
Version: 2.8.1+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 openvswitch-common - Open vSwitch common components
 openvswitch-dbg - Debug symbols for Open vSwitch packages
 openvswitch-dev - Open vSwitch development package
 openvswitch-ipsec - Open vSwitch GRE-over-IPsec support
 openvswitch-pki - Open vSwitch public key infrastructure dependency package
 openvswitch-switch - Open vSwitch switch implementations
 openvswitch-testcontroller - Simple controller for testing OpenFlow setups
 openvswitch-vtep - Open vSwitch VTEP utilities
 ovn-central - OVN central components
 ovn-controller-vtep - OVN vtep controller
 ovn-host   - OVN host components
 python-openvswitch - Python bindings for Open vSwitch
 python3-openvswitch - Python 3 bindings for Open vSwitch
Closes: 880508 880509
Changes:
 openvswitch (2.8.1+dfsg1-4) unstable; urgency=medium
 .
   * Remove tests broken in mips64el and mipsel (Closes: #880508, 880509).
Checksums-Sha1:
 d964b520206be039908782f6c8e40a032a10d728 3212 openvswitch_2.8.1+dfsg1-4.dsc
 4e873ae8dd2d01aff7bc4793b39734e9b160b446 47828 
openvswitch_2.8.1+dfsg1-4.debian.tar.xz
 

Bug#883137: marked as done (backblaze-b2: /usr/bin/b2 already provided by libboost1.XX-tools-dev)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 15:04:55 +
with message-id 
and subject line Bug#883137: fixed in backblaze-b2 1.0.0-2
has caused the Debian Bug report #883137,
regarding backblaze-b2: /usr/bin/b2 already provided by libboost1.XX-tools-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.)


-- 
883137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: backblaze-b2
Version: 1.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

Since I expect these two binaries to be unrelated, using Breaks+Replaces
or Conflicts would be an *incorrect*  solution. The new package will have
to rename its binary to avoid this conflict.

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

  Selecting previously unselected package backblaze-b2.
  Preparing to unpack .../16-backblaze-b2_1.0.0-1_all.deb ...
  Unpacking backblaze-b2 (1.0.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-TBtTWT/16-backblaze-b2_1.0.0-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/b2', which is also in package 
libboost1.63-tools-dev 1.63.0+dfsg-1.1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-TBtTWT/16-backblaze-b2_1.0.0-1_all.deb


cheers,

Andreas


libboost1.63-tools-dev=1.63.0+dfsg-1.1_backblaze-b2=1.0.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: backblaze-b2
Source-Version: 1.0.0-2

We believe that the bug you reported is fixed in the latest version of
backblaze-b2, 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 883...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Kobližek  (supplier of updated backblaze-b2 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, 30 Nov 2017 14:08:46 +0100
Source: backblaze-b2
Binary: backblaze-b2
Architecture: source
Version: 1.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Ondřej Kobližek 
Description:
 backblaze-b2 - Command Line Tool for Backblaze B2
Closes: 883137
Changes:
 backblaze-b2 (1.0.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Change maintainer to Python Applications Packaging Team
 .
   [ Ondřej Kobližek ]
   * Rename binary from b2 -> backblaze-b2. (Closes: #883137)
Checksums-Sha1:
 3d775e747e0572dbcfc9cc6b5ed8228ec6a9595a 2403 backblaze-b2_1.0.0-2.dsc
 7ed1b5c5deb3ed775b60948c17452edaa4b12ed3 61912 
backblaze-b2_1.0.0-2.debian.tar.xz
 776b9ef6c23660a83dcfe670f3fbc898978f9316 6890 
backblaze-b2_1.0.0-2_amd64.buildinfo
Checksums-Sha256:
 4a7477955939fe432b4d80ec6d877767932110b17be6a9fb074539032d721bc9 2403 
backblaze-b2_1.0.0-2.dsc
 247f34dcea6cfe45a95980e8cc8e3cb4ba32e06816e486a3708c0fb547811696 61912 
backblaze-b2_1.0.0-2.debian.tar.xz
 b89898860413cb07313c07e07fe40ac5fad6d8ce747e6eddb62f18851d3fbf60 6890 
backblaze-b2_1.0.0-2_amd64.buildinfo
Files:
 48587712d0f08907ac4a65280cd93bd1 2403 utils optional backblaze-b2_1.0.0-2.dsc
 21e71352c3563dc5a2b5562e396ae289 61912 utils optional 
backblaze-b2_1.0.0-2.debian.tar.xz
 d6af14e5d060eac21639e41011ed529e 6890 utils optional 
backblaze-b2_1.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJaIAS9AAoJEGP+EOrVXQ/boe8P/2pZ+X09z2IJecFS8WXRdSYw
q7/ZvkWRrT0x3O3qVeCXCMZ38kpSKSkK+lqQcXkQz08tTltm9COBARHB+LqHDMRn
Je8pWFReltUAVhTTMdeUaJ/Pe2o/Ybs+a1/wSOmBm8j3uO8oDuUIs/LeKwg13wS5
HgvmTngKlM1/Adpm3yqM31coaoODLQrRTN+/lwrUZ6A8WwHKpAt3dMyOuS6uQwVf
saFZUyzG5vn9huly1IiCBIpE8DPqEtBDTjMNKjE+u2biUlAEfB2Vf5v1giFnkdex
BWCe8YswSDDy76FmJefnrCBheIYE8gHKzb5HsRoIBqP3enAgX0cPjkICxvM+sW8z
a+sbHJGFc0nWHpaigZdirHHIpbANe/2Oo0cp//UaowjgoPSzpNBAMojS+PuObZ/s
cY4ZWPGZBg6ZuhhB4pZy8vEtDMwbPkON5zXfhV+fMjx1H+75k6tzxNpVwINKmilv
u806hJxQuMr2b1G5Wc2PtCqqVAqLmgOt5TK+Mysr2y7Th1K9EsO+PiF7CwdOwJ8C

Bug#880509: marked as done (openvswitch: FTBFS on mipsel: ofproto-dpif test 1133 fails repeatedly)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 15:11:06 +
with message-id 
and subject line Bug#880509: fixed in openvswitch 2.8.1+dfsg1-4
has caused the Debian Bug report #880509,
regarding openvswitch: FTBFS on mipsel: ofproto-dpif test 1133 fails repeatedly
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.)


-- 
880509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openvswitch
Version: 2.8.1+dfsg1-2
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-m...@lists.debian.org
Usertags: mipsel

The latest build of openvswitch for mipsel failed due to repeated
failure of test

  1133: ofproto-dpif - sFlow packet sampling - LACP structures FAILED 
(ofproto-dpif.at:6160)

which reports missing (if I have the sense of the diff right this time
around) one of the two LAC PDUs:

  --- - 2017-11-01 05:38:13.067238490 +
  +++ 
/<>/openvswitch-2.8.1+dfsg1/tests/testsuite.dir/at-groups/1133/stdout 
  2017-11-01 05:38:13.053596605 +
  @@ -11,7 +11,7 @@
 markerRespPDUsRx=4294967295
 unknownRx=4294967295
 illegalRx=0
  -  LACPDUsTx=1
  +  LACPDUsTx=2
 markerPDUsTx=4294967295
 markerRespPDUsTx=4294967295

You can find the full log at

https://buildd.debian.org/status/fetch.php?pkg=openvswitch=mipsel=2.8.1%2Bdfsg1-2=1509514741=0

FWIW, there were also transient failures of tests 788, 1209, and 2319;
and test 1133 also failed on the non-release architectures alpha and
hppa (but wasn't the only failure on either architecture, so I'll
follow up with separate reports).

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: openvswitch
Source-Version: 2.8.1+dfsg1-4

We believe that the bug you reported is fixed in the latest version of
openvswitch, 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 880...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated openvswitch 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, 30 Nov 2017 11:37:36 +0100
Source: openvswitch
Binary: openvswitch-common openvswitch-dbg openvswitch-dev openvswitch-ipsec 
openvswitch-pki openvswitch-switch openvswitch-testcontroller openvswitch-vtep 
ovn-central ovn-controller-vtep ovn-host python-openvswitch python3-openvswitch
Architecture: source amd64 all
Version: 2.8.1+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 openvswitch-common - Open vSwitch common components
 openvswitch-dbg - Debug symbols for Open vSwitch packages
 openvswitch-dev - Open vSwitch development package
 openvswitch-ipsec - Open vSwitch GRE-over-IPsec support
 openvswitch-pki - Open vSwitch public key infrastructure dependency package
 openvswitch-switch - Open vSwitch switch implementations
 openvswitch-testcontroller - Simple controller for testing OpenFlow setups
 openvswitch-vtep - Open vSwitch VTEP utilities
 ovn-central - OVN central components
 ovn-controller-vtep - OVN vtep controller
 ovn-host   - OVN host components
 python-openvswitch - Python bindings for Open vSwitch
 python3-openvswitch - Python 3 bindings for Open vSwitch
Closes: 880508 880509
Changes:
 openvswitch (2.8.1+dfsg1-4) unstable; urgency=medium
 .
   * Remove tests broken in mips64el and mipsel (Closes: #880508, 880509).
Checksums-Sha1:
 d964b520206be039908782f6c8e40a032a10d728 3212 openvswitch_2.8.1+dfsg1-4.dsc
 4e873ae8dd2d01aff7bc4793b39734e9b160b446 47828 
openvswitch_2.8.1+dfsg1-4.debian.tar.xz
 1ca0f9e6616635a0247ad71cebeabc933c2deaf3 1608292 
openvswitch-common_2.8.1+dfsg1-4_amd64.deb
 80daf3d589b995fc5aa6b778c5d0bcd88809e7f7 5271608 
openvswitch-dbg_2.8.1+dfsg1-4_amd64.deb
 86042bbb891189e325c57241c0f302ce483fe469 1486024 

Bug#882622: marked as done (networking-mlnx FTBFS: test failures)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 15:09:43 +
with message-id 
and subject line Bug#882622: fixed in networking-mlnx 1:11.0.0-1
has caused the Debian Bug report #882622,
regarding networking-mlnx 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.)


-- 
882622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: networking-mlnx
Version: 1:9.0.0~b1-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes networking-mlnx FTBFS:

https://tests.reproducible-builds.org/debian/history/networking-mlnx.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/networking-mlnx.html

...
==
FAIL: 
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test__output_hosts_file_log_only_twice
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test__output_hosts_file_log_only_twice
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/neutron/tests/base.py", line 118, in 
func
return f(self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/neutron/tests/base.py", line 118, in 
func
return f(self, *args, **kwargs)
  File 
"/usr/lib/python2.7/dist-packages/neutron/tests/unit/agent/linux/test_dhcp.py", 
line 2178, in test__output_hosts_file_log_only_twice
dm._output_hosts_file()
  File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/dhcp.py", line 
702, in _output_hosts_file
if self._get_port_extra_dhcp_opts(port):
  File "networking_mlnx/dhcp/mlnx_dhcp.py", line 45, in 
_get_port_extra_dhcp_opts
if hasattr(port, edo_ext.EXTRADHCPOPTS):
AttributeError: 'module' object has no attribute 'EXTRADHCPOPTS'


==
FAIL: 
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test_host_and_opts_file_on_net_with_V6_stateless_and_V4_subnets
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test_host_and_opts_file_on_net_with_V6_stateless_and_V4_subnets
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/neutron/tests/base.py", line 118, in 
func
return f(self, *args, **kwargs)
  File "networking_mlnx/tests/unit/dhcp/test_mlnx_dhcp.py", line 219, in 
test_host_and_opts_file_on_net_with_V6_stateless_and_V4_subnets
dm._output_hosts_file()
  File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/dhcp.py", line 
691, in _output_hosts_file
if not no_opts and self._get_port_extra_dhcp_opts(port):
  File "networking_mlnx/dhcp/mlnx_dhcp.py", line 45, in 
_get_port_extra_dhcp_opts
if hasattr(port, edo_ext.EXTRADHCPOPTS):
AttributeError: 'module' object has no attribute 'EXTRADHCPOPTS'


==
FAIL: 
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test_host_and_opts_file_on_stateless_dhcpv6_network
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test_host_and_opts_file_on_stateless_dhcpv6_network
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/neutron/tests/base.py", line 118, in 
func
return f(self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/neutron/tests/base.py", line 118, in 
func
return f(self, *args, **kwargs)
  File 
"/usr/lib/python2.7/dist-packages/neutron/tests/unit/agent/linux/test_dhcp.py", 
line 2237, in test_host_and_opts_file_on_stateless_dhcpv6_network
dm._output_hosts_file()
  File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/dhcp.py", line 
691, in _output_hosts_file
if not no_opts and self._get_port_extra_dhcp_opts(port):
  File "networking_mlnx/dhcp/mlnx_dhcp.py", line 45, in 
_get_port_extra_dhcp_opts
if hasattr(port, edo_ext.EXTRADHCPOPTS):
AttributeError: 'module' object has no attribute 'EXTRADHCPOPTS'


==
FAIL: 
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test_host_file_on_net_with_v6_slaac_and_v4
networking_mlnx.tests.unit.dhcp.test_mlnx_dhcp.TestMlnxDnsmasq.test_host_file_on_net_with_v6_slaac_and_v4
--

Bug#778720: [Pkg-dns-devel] Bug#778720: Re: bind9: hangs / crashes on mips after some time

2017-11-30 Thread James Cowgill
Hi,

On 30/11/17 14:16, Ondřej Surý wrote:
> James,
> 
> thanks for the poke - I moved the mentioned issue to public queue.

Thanks!

> Could you check whether
> https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=commit;h=404c9b1c53fd13f3a7f404522b13f48e2a71a8a0
> 
> fixes the issue.  I think it might be better to backport this
> stdatomic.h patch (from 9.12) to 9.11 instead of using custom patch just
> for mips if possible.

I'll have a look, but I expect that patch will work. The original bug
was caused by incorrect register constraints that caused gcc to reuse
some registers (ending with bad results). This can't happen if GCC
intrinsics are used.

If you do apply that, I would prefer if you completely removed the buggy
mips atomics code so there is no chance this bug will return in the future.

James



signature.asc
Description: OpenPGP digital signature


Bug#778720: [Pkg-dns-devel] Bug#778720: Re: bind9: hangs / crashes on mips after some time

2017-11-30 Thread Ondřej Surý
In fact v9_11 branch already has this cherry-picked in
99056063905a9273ec59cf477ae747e0490182b7 (and it needs some extra
commits on top of that, but this is the base patch)

Ondrej
-- 
Ondřej Surý 

On Thu, Nov 30, 2017, at 15:16, Ondřej Surý wrote:
> James,
> 
> thanks for the poke - I moved the mentioned issue to public queue.
> 
> Could you check whether
> https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=commit;h=404c9b1c53fd13f3a7f404522b13f48e2a71a8a0
> 
> fixes the issue.  I think it might be better to backport this
> stdatomic.h patch (from 9.12) to 9.11 instead of using custom patch just
> for mips if possible.
> 
> O.
> -- 
> Ondřej Surý 
> 
> On Thu, Nov 30, 2017, at 15:02, James Cowgill wrote:
> > Control: found -1 1:9.10.6+dfsg-1
> > 
> > Hi,
> > 
> > On 23/10/17 12:09, Bernhard Schmidt wrote:
> > > Control: fixed -1 1:9.10.6+dfsg-1
> > > 
> > > This has been fixed upstream
> > > 
> > >   --- 9.10.5b1 released ---
> > > [...]
> > > 4414. [bug]   Corrected a bug in the MIPS implementation of
> > >   isc_atomic_xadd(). [RT #41965]
> > 
> > As far as I can see, this is:
> > https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=commit;h=ad2611f9af42c7cc654106463dbb26de6ff3bfe4
> > 
> > [Grumbles about "semi-open" ISC bug tracker]
> > 
> > That change has nothing to do with this bug. This Debian bug actually
> > describes a major bug with the new code submitted upstream!
> > 
> > Please reinstate my 32_mips_atomic.diff patch from message #60 of this
> > bug.
> > 
> > Thanks,
> > James
> > 
> > ___
> > pkg-dns-devel mailing list
> > pkg-dns-de...@lists.alioth.debian.org
> > https://lists.alioth.debian.org/mailman/listinfo/pkg-dns-devel
> > Email had 1 attachment:
> > + signature.asc
> >   1k (application/pgp-signature)



Bug#778720: [Pkg-dns-devel] Bug#778720: Re: bind9: hangs / crashes on mips after some time

2017-11-30 Thread Ondřej Surý
James,

thanks for the poke - I moved the mentioned issue to public queue.

Could you check whether
https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=commit;h=404c9b1c53fd13f3a7f404522b13f48e2a71a8a0

fixes the issue.  I think it might be better to backport this
stdatomic.h patch (from 9.12) to 9.11 instead of using custom patch just
for mips if possible.

O.
-- 
Ondřej Surý 

On Thu, Nov 30, 2017, at 15:02, James Cowgill wrote:
> Control: found -1 1:9.10.6+dfsg-1
> 
> Hi,
> 
> On 23/10/17 12:09, Bernhard Schmidt wrote:
> > Control: fixed -1 1:9.10.6+dfsg-1
> > 
> > This has been fixed upstream
> > 
> > --- 9.10.5b1 released ---
> > [...]
> > 4414.   [bug]   Corrected a bug in the MIPS implementation of
> > isc_atomic_xadd(). [RT #41965]
> 
> As far as I can see, this is:
> https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=commit;h=ad2611f9af42c7cc654106463dbb26de6ff3bfe4
> 
> [Grumbles about "semi-open" ISC bug tracker]
> 
> That change has nothing to do with this bug. This Debian bug actually
> describes a major bug with the new code submitted upstream!
> 
> Please reinstate my 32_mips_atomic.diff patch from message #60 of this
> bug.
> 
> Thanks,
> James
> 
> ___
> pkg-dns-devel mailing list
> pkg-dns-de...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/pkg-dns-devel
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)



Processed: Bug#778720: Re: bind9: hangs / crashes on mips after some time

2017-11-30 Thread Debian Bug Tracking System
Processing control commands:

> found -1 1:9.10.6+dfsg-1
Bug #778720 {Done: James Cowgill } [bind9] bind9: hangs / 
crashes on mips after some time
Marked as found in versions bind9/1:9.10.6+dfsg-1; no longer marked as fixed in 
versions bind9/1:9.10.6+dfsg-1 and reopened.

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



Bug#778720: Re: bind9: hangs / crashes on mips after some time

2017-11-30 Thread James Cowgill
Control: found -1 1:9.10.6+dfsg-1

Hi,

On 23/10/17 12:09, Bernhard Schmidt wrote:
> Control: fixed -1 1:9.10.6+dfsg-1
> 
> This has been fixed upstream
> 
>   --- 9.10.5b1 released ---
> [...]
> 4414. [bug]   Corrected a bug in the MIPS implementation of
>   isc_atomic_xadd(). [RT #41965]

As far as I can see, this is:
https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=commit;h=ad2611f9af42c7cc654106463dbb26de6ff3bfe4

[Grumbles about "semi-open" ISC bug tracker]

That change has nothing to do with this bug. This Debian bug actually
describes a major bug with the new code submitted upstream!

Please reinstate my 32_mips_atomic.diff patch from message #60 of this
bug.

Thanks,
James



signature.asc
Description: OpenPGP digital signature


Bug#880841: freeipa 4.4 fixes for samba 4.7 (backport)

2017-11-30 Thread Alexander Bokovoy
Hi,

I've backported upstream patches that add support for Samba 4.7 to
freeIPA 4.4 branch. You can find them here:
https://github.com/abbra/freeipa/commits/4.4-samba_4.7_fixes

$ git log --format=short origin/ipa-4-4..HEAD
commit c2fd529cb3ca56ab243e53fb1098748a76c42cde (HEAD -> 4.4-samba_4.7_fixes, 
github-abbra/4.4-samba_4.7_fixes)
Author: Alexander Bokovoy 

ipa-sam: use smbldap_set_bind_callback for Samba 4.7 or later

commit 7edccc9347410e7249ab18ec56b18c2161636daa
Author: Alexander Bokovoy 

ipa-sam: use own private structure, not ldapsam_privates

commit 64d23dd1382223fd2c0eb4aea0988977118b5799
Author: Sumit Bose 

ipa-sam: replace encode_nt_key() with E_md4hash()

commit 0f450488b0883c3e66cc8dfebd9498e9a5c13a7c
Author: Florence Blanc-Renaud 

ipa-sam: create the gidNumber attribute in the trusted domain entry


-- 
/ Alexander Bokovoy


signature.asc
Description: PGP signature


Processed: unarchive #778720

2017-11-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> unarchive 778720
Bug #778720 {Done: James Cowgill } [bind9] bind9: hangs / 
crashes on mips after some time
Unarchived Bug 778720
> thanks
Stopping processing here.

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



Bug#876698: marked as done (octave-image FTBFS on 32bit: test failures)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 14:32:40 +0100
with message-id <20171130133240.3rswtyjorweaf...@laboissiere.net>
and subject line Re: Bug#876698: octave-image FTBFS on 32bit: test failures
has caused the Debian Bug report #876698,
regarding octave-image FTBFS on 32bit: 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.)


-- 
876698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-image
Version: 2.6.1-4
Severity: serious

https://buildd.debian.org/status/package.php?p=octave-image=sid
--- End Message ---
--- Begin Message ---

Control: fixed -1 2.6.2-3

Version 2.6.2-3 of the package builds correctly on all architectures. I 
am hereby closing this bug report.


Rafael

* Adrian Bunk  [2017-09-25 01:25]:


 Source: octave-image
 Version: 2.6.1-4
 Severity: serious

https://buildd.debian.org/status/package.php?p=octave-image=sid--- End Message ---


Processed: Bug#883186 marked as pending

2017-11-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 883186 pending
Bug #883186 [libc6-dev] libc6-dev: posix_fadvise64 missing from static mips64el 
build
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#883186: marked as pending

2017-11-30 Thread Aurelien Jarno
tag 883186 pending
thanks

Hello,

Bug #883186 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:

https://anonscm.debian.org/cgit/pkg-glibc/glibc.git/commit/?id=72c8c59

---
commit 72c8c592e031dafa2aa91deeb9b45382abd49acf
Author: Aurelien Jarno 
Date:   Thu Nov 30 14:08:45 2017 +0100

Fix missing posix_fadvise64 from static mips64el build. Closes: #883186.

diff --git a/debian/changelog b/debian/changelog
index 3f530fd..bbe817a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,8 @@ glibc (2.25-3) UNRELEASED; urgency=medium
   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix assertion failure in posix_spawn().  Closes: #882794.
+- Fix missing posix_fadvise64 from static mips64el build. Closes:
+  #883186.
 
  -- Aurelien Jarno   Wed, 22 Nov 2017 00:21:54 +0100
 



Processed: Re: Bug#883186: e2fsprogs FTBFS on mips64el: undefined reference to `posix_fadvise64'

2017-11-30 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 libc6-dev 2.25-1
Bug #883186 [libc6] e2fsprogs FTBFS on mips64el: undefined reference to 
`posix_fadvise64'
Bug reassigned from package 'libc6' to 'libc6-dev'.
Ignoring request to alter found versions of bug #883186 to the same values 
previously set
Ignoring request to alter fixed versions of bug #883186 to the same values 
previously set
Bug #883186 [libc6-dev] e2fsprogs FTBFS on mips64el: undefined reference to 
`posix_fadvise64'
Marked as found in versions glibc/2.25-1.
> retitle -1 libc6-dev: posix_fadvise64 missing from static mips64el build
Bug #883186 [libc6-dev] e2fsprogs FTBFS on mips64el: undefined reference to 
`posix_fadvise64'
Changed Bug title to 'libc6-dev: posix_fadvise64 missing from static mips64el 
build' from 'e2fsprogs FTBFS on mips64el: undefined reference to 
`posix_fadvise64''.
> tags -1 fixed-upstream
Bug #883186 [libc6-dev] libc6-dev: posix_fadvise64 missing from static mips64el 
build
Ignoring request to alter tags of bug #883186 to the same tags previously set
> forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=21232
Bug #883186 [libc6-dev] libc6-dev: posix_fadvise64 missing from static mips64el 
build
Ignoring request to change the forwarded-to-address of bug#883186 to the same 
value
> affects -1 src:e2fsprogs
Bug #883186 [libc6-dev] libc6-dev: posix_fadvise64 missing from static mips64el 
build
Added indication that 883186 affects src:e2fsprogs

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



Bug#883186: e2fsprogs FTBFS on mips64el: undefined reference to `posix_fadvise64'

2017-11-30 Thread James Cowgill
Control: reassign -1 libc6-dev 2.25-1
Control: retitle -1 libc6-dev: posix_fadvise64 missing from static mips64el 
build
Control: tags -1 fixed-upstream
Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=21232
Control: affects -1 src:e2fsprogs

Hi,

On 30/11/17 12:22, Helmut Grohne wrote:
> Source: e2fsprogs
> Version: 1.43.7-1
> Severity: serious
> Justification: FTBFS
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> I was investigating a bootstrap failure for mips64el
> (https://jenkins.debian.net/job/rebootstrap_mips64el_gcc7_nobiarch/51)
> and wondered whether this was a native issue. Indeed a native build of
> e2fsprogs fails on mips64el and the build log ends as follows:
> 
> | /usr/bin/make -C /home/helmutg/e2fsprogs-1.43.7/debian/BUILD-STD/e2fsck V=1 
> e2fsck.static
> | make[1]: Entering directory 
> '/home/helmutg/e2fsprogs-1.43.7/debian/BUILD-STD/e2fsck'
> | gcc -Wl,-z,relro -Wl,-z,now -static -o e2fsck.static unix.o e2fsck.o 
> super.o pass1.o pass1b.o pass2.o pass3.o pass4.o pass5.o journal.o 
> badblocks.o util.o dirinfo.o dx_dirinfo.o ehandler.o problem.o message.o 
> quota.o recovery.o region.o revoke.o ea_refcount.o rehash.o logfile.o 
> sigcatcher.o  readahead.o extents.o   ../lib/libsupport.a ../lib/libext2fs.a 
> ../lib/libcom_err.a -lpthread -lblkid -luuid -luuid  -luuid   ../lib/libe2p.a 
> -ldl -lblkid  
> | logfile.o: In function `expand_percent_expression':
> | ./debian/BUILD-STD/e2fsck/../../../e2fsck/logfile.c:141: warning: Using 
> 'getpwuid_r' in statically linked applications requires at runtime the shared 
> libraries from the glibc version used for linking
> | ../lib/libext2fs.a(unix_io.o): In function `unix_cache_readahead':
> | ./debian/BUILD-STD/lib/ext2fs/../../../../lib/ext2fs/unix_io.c:969: 
> undefined reference to `posix_fadvise64'
> | ./debian/BUILD-STD/lib/ext2fs/../../../../lib/ext2fs/unix_io.c:969: 
> undefined reference to `posix_fadvise64'

It appears that libc.a from glibc 2.25 does not contain a
posix_fadvise64 symbol on mips64el

# nm /usr/lib/mips64el-linux-gnuabi64/libc.a 2>/dev/null | grep posix_fadvise
posix_fadvise.o:
posix_fadvise64.o:
 T __posix_fadvise64_l64
 T posix_fadvise

I found an upstream bug about it and it has already been fixed in glibc
2.26:
https://sourceware.org/bugzilla/show_bug.cgi?id=21232

Thanks,
James



signature.asc
Description: OpenPGP digital signature


Bug#874295: Not a bug

2017-11-30 Thread Thomas Pierson
Hi Ben,

Le 30 novembre 2017 07:47:41 GMT+01:00, Ben Finney  a écrit 
:
>That is still a problem, IMO. It would be best if the program did not
>do
>that, and instead prompted the user to install the non-free package
>providing that plug-in.

Actually the program prompt a dialog asking the user if he want to install the 
extra plugin.
But yes maybe it should be more explicit about the non-free nature of the 
plugin. I will open a new bug about that.

Regards,
Thomas




Processed: Re: Bug#883186: e2fsprogs FTBFS on mips64el: undefined reference to `posix_fadvise64'

2017-11-30 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 libc6
Bug #883186 [src:e2fsprogs] e2fsprogs FTBFS on mips64el: undefined reference to 
`posix_fadvise64'
Bug reassigned from package 'src:e2fsprogs' to 'libc6'.
No longer marked as found in versions e2fsprogs/1.43.7-1.
Ignoring request to alter fixed versions of bug #883186 to the same values 
previously set
> tag -1 + fixed-upstream
Bug #883186 [libc6] e2fsprogs FTBFS on mips64el: undefined reference to 
`posix_fadvise64'
Added tag(s) fixed-upstream.
> forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=21232
Bug #883186 [libc6] e2fsprogs FTBFS on mips64el: undefined reference to 
`posix_fadvise64'
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=21232'.

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



Bug#883186: e2fsprogs FTBFS on mips64el: undefined reference to `posix_fadvise64'

2017-11-30 Thread Aurelien Jarno
control: reassign -1 libc6
control: tag -1 + fixed-upstream
control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=21232

On 2017-11-30 13:22, Helmut Grohne wrote:
> Source: e2fsprogs
> Version: 1.43.7-1
> Severity: serious
> Justification: FTBFS
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> I was investigating a bootstrap failure for mips64el
> (https://jenkins.debian.net/job/rebootstrap_mips64el_gcc7_nobiarch/51)
> and wondered whether this was a native issue. Indeed a native build of
> e2fsprogs fails on mips64el and the build log ends as follows:
> 
> | /usr/bin/make -C /home/helmutg/e2fsprogs-1.43.7/debian/BUILD-STD/e2fsck V=1 
> e2fsck.static
> | make[1]: Entering directory 
> '/home/helmutg/e2fsprogs-1.43.7/debian/BUILD-STD/e2fsck'
> | gcc -Wl,-z,relro -Wl,-z,now -static -o e2fsck.static unix.o e2fsck.o 
> super.o pass1.o pass1b.o pass2.o pass3.o pass4.o pass5.o journal.o 
> badblocks.o util.o dirinfo.o dx_dirinfo.o ehandler.o problem.o message.o 
> quota.o recovery.o region.o revoke.o ea_refcount.o rehash.o logfile.o 
> sigcatcher.o  readahead.o extents.o   ../lib/libsupport.a ../lib/libext2fs.a 
> ../lib/libcom_err.a -lpthread -lblkid -luuid -luuid  -luuid   ../lib/libe2p.a 
> -ldl -lblkid  
> | logfile.o: In function `expand_percent_expression':
> | ./debian/BUILD-STD/e2fsck/../../../e2fsck/logfile.c:141: warning: Using 
> 'getpwuid_r' in statically linked applications requires at runtime the shared 
> libraries from the glibc version used for linking
> | ../lib/libext2fs.a(unix_io.o): In function `unix_cache_readahead':
> | ./debian/BUILD-STD/lib/ext2fs/../../../../lib/ext2fs/unix_io.c:969: 
> undefined reference to `posix_fadvise64'
> | ./debian/BUILD-STD/lib/ext2fs/../../../../lib/ext2fs/unix_io.c:969: 
> undefined reference to `posix_fadvise64'
> | collect2: error: ld returned 1 exit status
> | Makefile:428: recipe for target 'e2fsck.static' failed
> | make[1]: *** [e2fsck.static] Error 1
> | make[1]: Leaving directory 
> '/home/helmutg/e2fsprogs-1.43.7/debian/BUILD-STD/e2fsck'
> | debian/rules:262: recipe for target 'debian/stampdir/build-std-stamp' failed
> | make: *** [debian/stampdir/build-std-stamp] Error 2
> | dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
> status 2
> 
> Since this could either be a mips issue or a glibc issue, I put both
> lists into X-Debbugs-Cc and hope that someone will sort this out.

This is definitely a glibc bug, happening only on mips64el for the
static version of libc6. The bug has already been fixed upstream, I'll
pull the patch from there and do an upload in the next days.

Aurelien

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



Bug#883186: e2fsprogs FTBFS on mips64el: undefined reference to `posix_fadvise64'

2017-11-30 Thread Helmut Grohne
Source: e2fsprogs
Version: 1.43.7-1
Severity: serious
Justification: FTBFS
User: helm...@debian.org
Usertags: rebootstrap

I was investigating a bootstrap failure for mips64el
(https://jenkins.debian.net/job/rebootstrap_mips64el_gcc7_nobiarch/51)
and wondered whether this was a native issue. Indeed a native build of
e2fsprogs fails on mips64el and the build log ends as follows:

| /usr/bin/make -C /home/helmutg/e2fsprogs-1.43.7/debian/BUILD-STD/e2fsck V=1 
e2fsck.static
| make[1]: Entering directory 
'/home/helmutg/e2fsprogs-1.43.7/debian/BUILD-STD/e2fsck'
| gcc -Wl,-z,relro -Wl,-z,now -static -o e2fsck.static unix.o e2fsck.o super.o 
pass1.o pass1b.o pass2.o pass3.o pass4.o pass5.o journal.o badblocks.o util.o 
dirinfo.o dx_dirinfo.o ehandler.o problem.o message.o quota.o recovery.o 
region.o revoke.o ea_refcount.o rehash.o logfile.o sigcatcher.o  readahead.o 
extents.o   ../lib/libsupport.a ../lib/libext2fs.a ../lib/libcom_err.a 
-lpthread -lblkid -luuid -luuid  -luuid   ../lib/libe2p.a -ldl -lblkid  
| logfile.o: In function `expand_percent_expression':
| ./debian/BUILD-STD/e2fsck/../../../e2fsck/logfile.c:141: warning: Using 
'getpwuid_r' in statically linked applications requires at runtime the shared 
libraries from the glibc version used for linking
| ../lib/libext2fs.a(unix_io.o): In function `unix_cache_readahead':
| ./debian/BUILD-STD/lib/ext2fs/../../../../lib/ext2fs/unix_io.c:969: undefined 
reference to `posix_fadvise64'
| ./debian/BUILD-STD/lib/ext2fs/../../../../lib/ext2fs/unix_io.c:969: undefined 
reference to `posix_fadvise64'
| collect2: error: ld returned 1 exit status
| Makefile:428: recipe for target 'e2fsck.static' failed
| make[1]: *** [e2fsck.static] Error 1
| make[1]: Leaving directory 
'/home/helmutg/e2fsprogs-1.43.7/debian/BUILD-STD/e2fsck'
| debian/rules:262: recipe for target 'debian/stampdir/build-std-stamp' failed
| make: *** [debian/stampdir/build-std-stamp] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Since this could either be a mips issue or a glibc issue, I put both
lists into X-Debbugs-Cc and hope that someone will sort this out.

Helmut



Bug#883183: libdbd-firebird-perl FTBFS on i386: t/embed-rt110979.t failure

2017-11-30 Thread Adrian Bunk
Source: libdbd-firebird-perl
Version: 1.26-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=libdbd-firebird-perl=i386=1.26-1=1511985831=0

...
DBD::FirebirdEmbedded::st finish failed: Firebird error
-invalid database handle (no active connection) at t/embed-rt110979.t line 68.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 7.
t/embed-rt110979.t .. 
ok 1 - Connected to the database
ok 2 - Table is 'TESTAA'
ok 3 - CREATE TABLE 'TESTAA'
ok 4 - create generator gen_TESTAA
ok 5 - create trigger TESTAA_bi
ok 6 - Insert worked
ok 7 - Autoinc PK retrieved
Dubious, test returned 255 (wstat 65280, 0xff00)
All 7 subtests passed 
...

Test Summary Report
---
t/embed-rt110979.t(Wstat: 65280 Tests: 7 Failed: 0)
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
Files=88, Tests=1121, 17 wallclock secs ( 0.60 usr  0.16 sys + 13.34 cusr  1.50 
csys = 15.60 CPU)
Result: FAIL
Failed 1/88 test programs. 0/1121 subtests failed.
Makefile:1063: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 255



Bug#738260: marked as done (xpilot-ng-common: Please replace ttf-freefont by fonts-freefont-ttf in package dependencies)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 11:58:28 +
with message-id <13c3dc22-f784-b6b0-37ed-5782423aa...@p10link.net>
and subject line re: xpilot-ng-common: Please replace ttf-freefont by 
fonts-freefont-ttf in package dependencies
has caused the Debian Bug report #738260,
regarding xpilot-ng-common: Please replace ttf-freefont by fonts-freefont-ttf 
in package dependencies
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.)


-- 
738260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xpilot-ng-common
Version: N/A
Severity: normal

Hello,

The ttf-freefont binary package has been renamed to fonts-freefont-ttf
as per the Font Packaging Team internal naming policy.

The package provides a transitional package but we would like to drop
it and therefore we need packages that depend on ttf-freefont to
switch their dependency to fonts-freefont-ttf.

Thanks in advance.

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

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

Version: 1:4.7.3-2.3

Seems the version of the upload without the closes was the one that ended up 
being accepted by the archive. Closing the bug manually.--- End Message ---


Bug#883181: linux-image-4.9.0-4-amd64: Default stretch kernel raises cgroup strack traces under high load

2017-11-30 Thread Tom Stocker
Package: src:linux
Version: 4.9.51-1
Severity: serious
Justification: Policy 2.2.1



-- Package-specific info:
** Version:
Linux version 4.9.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.51-1 (2017-09-28)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 
root=/dev/mapper/de--bln--vm--017--vg-root ro quiet

** Not tainted

** Kernel log:
[1.533757] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: 
(null)
[1.847797] ip_tables: (C) 2000-2006 Netfilter Core Team
[1.912833] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[1.912859] systemd[1]: Detected virtualization vmware.
[1.912863] systemd[1]: Detected architecture x86-64.
[1.914546] systemd[1]: Set hostname to .
[2.058639] random: crng init done
[2.131752] systemd[1]: Set up automount Arbitrary Executable File Formats 
File System Automount Point.
[2.131812] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[2.131843] systemd[1]: Listening on Syslog Socket.
[2.131885] systemd[1]: Started Forward Password Requests to Wall Directory 
Watch.
[2.131920] systemd[1]: Listening on udev Control Socket.
[2.131955] systemd[1]: Started Dispatch Password Requests to Console 
Directory Watch.
[2.363268] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
[2.516531] systemd-journald[833]: Received request to flush runtime journal 
from PID 1
[2.819683] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[2.819691] ACPI: Power Button [PWRF]
[2.819819] ACPI: AC Adapter [ACAD] (on-line)
[2.875315] input: PC Speaker as /devices/platform/pcspkr/input/input5
[2.881700] vmw_vmci :00:07.7: Found VMCI PCI device at 0x11080, irq 16
[2.881767] vmw_vmci :00:07.7: Using capabilities 0xc
[2.882410] Guest personality initialized and is active
[2.882410] VMCI host device registered (name=vmci, major=10, minor=58)
[2.882410] Initialized host personality
[2.930410] [drm] Initialized
[2.941291] sd 0:0:0:0: Attached scsi generic sg0 type 0
[2.941374] sd 0:0:1:0: Attached scsi generic sg1 type 0
[2.941446] sd 0:0:2:0: Attached scsi generic sg2 type 0
[2.941516] sd 0:0:3:0: Attached scsi generic sg3 type 0
[2.941562] sr 2:0:0:0: Attached scsi generic sg4 type 5
[3.012775] [drm] DMA map mode: Using physical TTM page addresses.
[3.012868] [drm] Capabilities:
[3.012873] [drm]   Rect copy.
[3.012874] [drm]   Cursor.
[3.012875] [drm]   Cursor bypass.
[3.012876] [drm]   Cursor bypass 2.
[3.012877] [drm]   8bit emulation.
[3.012878] [drm]   Alpha cursor.
[3.012879] [drm]   Extended Fifo.
[3.012880] [drm]   Multimon.
[3.012881] [drm]   Pitchlock.
[3.012882] [drm]   Irq mask.
[3.012883] [drm]   Display Topology.
[3.012884] [drm]   GMR.
[3.012885] [drm]   Traces.
[3.012886] [drm]   GMR2.
[3.012887] [drm]   Screen Object 2.
[3.012888] [drm]   Command Buffers.
[3.012889] [drm]   Command Buffers 2.
[3.012890] [drm]   Guest Backed Resources.
[3.012891] [drm]   DX Features.
[3.012893] [drm] Max GMR ids is 64
[3.012894] [drm] Max number of GMR pages is 65536
[3.012895] [drm] Max dedicated hypervisor surface memory is 0 kiB
[3.012896] [drm] Maximum display memory size is 4096 kiB
[3.012898] [drm] VRAM at 0xe800 size is 4096 kiB
[3.012899] [drm] MMIO at 0xfe00 size is 256 kiB
[3.012901] [drm] global init.
[3.013022] [TTM] Zone  kernel: Available graphics memory: 60855752 kiB
[3.013023] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[3.013024] [TTM] Initializing pool allocator
[3.013029] [TTM] Initializing DMA pool allocator
[3.013122] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[3.013127] [drm] No driver support for vblank timestamp query.
[3.013382] [drm] Screen Target Display device initialized
[3.013441] [drm] width 640
[3.013453] [drm] height 480
[3.013465] [drm] bpp 32
[3.014570] [drm] Fifo max 0x0004 min 0x1000 cap 0x077f
[3.015450] [drm] Using command buffers with DMA pool.
[3.015460] [drm] DX: no.
[3.015695] fbcon: svgadrmfb (fb0) is primary device
[3.017598] Console: switching to colour frame buffer device 100x37
[3.096662] ppdev: user-space parallel port driver
[3.112337] [drm] Initialized vmwgfx 2.12.0 20170221 for :00:0f.0 on 
minor 0
[3.194699] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 
10737418240 ms ovfl timer
[3.194702] RAPL PMU: hw unit of domain pp0-core 2^-0 Joules
[3.194703] RAPL PMU: hw unit of domain package 2^-0 Joules
[3.194704] RAPL PMU: hw unit of domain dram 2^-16 Joules
[3.235157] shpchp: Standard Hot Plug PCI Controller Driver 

Bug#874295: Not a bug

2017-11-30 Thread Ian Jackson
Ben Finney writes ("Re: Bug#874295: Not a bug"):
> Thomas Pierson  writes:
> > It's only if a user want to connect to a particular external service
> > that a plugin file is downloaded and used.
> 
> That is still a problem, IMO. It would be best if the program did not do
> that, and instead prompted the user to install the non-free package
> providing that plug-in.

I agree with Ben that it would be better if the program used a
non-free package from Debian instead.  Maybe we could clone this bug
into a wishlist bug for that.

> (Yes, I think a web browser should not download and execute arbitrary
> JavaScript either. That one problem remains unaddressed is not a
> justification for the same problem elsewhere.)

This is obviously out of scope for the discussion of this bug.

If you want to change Debian's stance about this, you will need to
agitate with ftpmaster, on -project, or -devel, or pass a GR, or
something.

Ian.



Bug#882122: thunderbird: Thunderbird can't connect to X server, fails to start

2017-11-30 Thread Guido Günther
Hi,
On Thu, Nov 23, 2017 at 03:14:18PM -0500, Simon Deziel wrote:
> On 2017-11-23 03:12 PM, Jack Henschel wrote:
> > $ sudo dmesg -T | grep apparmor
> > ...
> > [Thu Nov 23 21:01:24 2017] audit: type=1400 audit(1511467287.665:8): 
> > apparmor="STATUS" operation="profile_load" profile="unconfined" 
> > name="thunderbird" pid=498 comm="apparmor_parser"
> > [Thu Nov 23 21:01:24 2017] audit: type=1400 audit(1511467287.665:9): 
> > apparmor="STATUS" operation="profile_load" profile="unconfined" 
> > name="thunderbird//gpg" pid=498 comm="apparmor_parser"
> > [Thu Nov 23 21:01:24 2017] audit: type=1400 audit(1511467287.665:10): 
> > apparmor="STATUS" operation="profile_load" profile="unconfined" 
> > name="thunderbird//lsb_release" pid=498 comm="apparmor_parser"
> > [Thu Nov 23 21:01:24 2017] audit: type=1400 audit(1511467287.665:11): 
> > apparmor="STATUS" operation="profile_load" profile="unconfined" 
> > name="thunderbird//sanitized_helper" pid=498 comm="apparmor_parser"
> > 
> > I does not seem like apparmor is blocking anything.
> 
> Agreed, Apparmor doesn't seem to get in the way. Thanks for checking!

The apparmor profile has denials. That means that it will prevent TB
from accessing files but not lock it. So what the above is not prove
that Apparmor is not at fault yet. You would have to disable the profile
using aa-disable and see if thunderbird starts then.
Cheers,
 -- Guido

> 
> Regards,
> Simon
> 



Bug#882790: marked as done (aiozmq: sourceful upload needed for the python3.6 transition)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 11:32:53 +0100
with message-id <20171130103253.mhrpxgorxd5fb...@sar0.p1otr.com>
and subject line -2 uploaded to unstable
has caused the Debian Bug report #882790,
regarding aiozmq: sourceful upload needed for the python3.6 transition
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.)


-- 
882790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aiozmq
Version: 0.7.1-1
Severity: serious
Tags: sid buster
Control: block 866335 with -1

Hi,

a sourceful upload of aiozmq is needed for the python3.6
transition. There are no changes needed to the packaging for this
transition (rebuilding in an up-to-date sid environment will
automatically generate updated dependencies), but since the package
builds arch:all packages depending on pythonX.Y, it cannot be
binNMUed. A source-only upload (without any maintainer-built .debs)
is preferred.


Andreas
--- End Message ---
--- Begin Message ---
Source: aiozmq
Source-Version: 0.7.0-2

-2 doesn't have a hard dependency on python3.X anymore--- End Message ---


Bug#881630: marked as done (vdr-plugin-xineliboutput: FTBFS with multiarchified xine-lib-1.2 >= 1.2.6-2)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 09:50:29 +
with message-id 
and subject line Bug#881630: fixed in vdr-plugin-xineliboutput 2.0.0-1.1
has caused the Debian Bug report #881630,
regarding vdr-plugin-xineliboutput: FTBFS with multiarchified xine-lib-1.2 >= 
1.2.6-2
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.)


-- 
881630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-xineliboutput
Version: 2.0.0-1
Severity: serious

Dear maintainer,

I multiarchified xine-lib-1.2 (i.e. just using dh_auto_configure with
compat level >= 9), and that apparently also affects how other packages
places their files.
In particular, vdr-plugin-xineliboutput seems to fail with it (log at
the bottom).
Fix should be as easy as declaring a stricter build-dep on libxine2-dev
and changing the .install files to use a multiarchified path.


Note that I might NMU this package in some days to fix this.



   dh_install
install -d debian/vdr-plugin-xineliboutput//usr/share
cp --reflink=auto -a ./debian/tmp/usr/share/locale 
debian/vdr-plugin-xineliboutput//usr/share/
install -d debian/vdr-plugin-xineliboutput/etc/vdr/conf.avail/
cp --reflink=auto -a ./debian/xineliboutput.conf 
debian/vdr-plugin-xineliboutput/etc/vdr/conf.avail//
install -d 
debian/vdr-plugin-xineliboutput/etc/vdr/plugins/xineliboutput/
cp --reflink=auto -a ./examples/allowed_hosts.conf 
debian/vdr-plugin-xineliboutput/etc/vdr/plugins/xineliboutput//
install -d debian/vdr-plugin-xineliboutput/usr/lib/vdr/plugins/
cp --reflink=auto -a ./libvdr-xineliboutput.so.2.3.8 
debian/vdr-plugin-xineliboutput/usr/lib/vdr/plugins//
install -d debian/.debhelper/generated/vdr-plugin-xineliboutput
install -d debian/.debhelper/generated/vdr-plugin-xineliboutput-dbg
install -d debian/libxineliboutput-fbfe/usr/lib/vdr/plugins/
cp --reflink=auto -a ./libxineliboutput-fbfe.so.2.0.0 
debian/libxineliboutput-fbfe/usr/lib/vdr/plugins//
install -d debian/.debhelper/generated/libxineliboutput-fbfe
install -d debian/.debhelper/generated/libxineliboutput-fbfe-dbg
install -d debian/libxineliboutput-sxfe/usr/lib/vdr/plugins/
cp --reflink=auto -a ./libxineliboutput-sxfe.so.2.0.0 
debian/libxineliboutput-sxfe/usr/lib/vdr/plugins//
install -d debian/.debhelper/generated/libxineliboutput-sxfe
install -d debian/.debhelper/generated/libxineliboutput-sxfe-dbg
install -d debian/xineliboutput-fbfe//usr/bin
cp --reflink=auto -a debian/tmp/usr/bin/vdr-fbfe 
debian/xineliboutput-fbfe//usr/bin/
install -d debian/xineliboutput-fbfe/usr/share/applications/
cp --reflink=auto -a ./debian/vdr-fbfe.desktop 
debian/xineliboutput-fbfe/usr/share/applications//
install -d debian/.debhelper/generated/xineliboutput-fbfe
install -d debian/.debhelper/generated/xineliboutput-fbfe-dbg
install -d debian/xineliboutput-sxfe//usr/bin
cp --reflink=auto -a debian/tmp/usr/bin/vdr-sxfe 
debian/xineliboutput-sxfe//usr/bin/
install -d debian/xineliboutput-sxfe/usr/share/applications/
cp --reflink=auto -a ./debian/vdr-sxfe.desktop 
debian/xineliboutput-sxfe/usr/share/applications//
install -d debian/.debhelper/generated/xineliboutput-sxfe
install -d debian/.debhelper/generated/xineliboutput-sxfe-dbg
dh_install: Cannot find (any matches for) "usr/lib/xine" (tried in ., 
debian/tmp)

dh_install: libxine2-xvdr missing files: usr/lib/xine
install -d debian/.debhelper/generated/libxine2-xvdr
install -d debian/.debhelper/generated/libxine2-xvdr-dbg
dh_install: missing files, aborting
debian/rules:7: recipe for target 'binary' failed
make: *** [binary] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: vdr-plugin-xineliboutput
Source-Version: 2.0.0-1.1

We believe that the bug you reported is fixed in the latest version of
vdr-plugin-xineliboutput, which is due to be installed in the Debian FTP 

Bug#871105: debian-faq: FTBFS: Addendum po4a/add_fr/commentaires.add does NOT apply to fr/debian-faq.sgml (translation discarded).

2017-11-30 Thread Joost van Baal-Ilić
tags 871105 pending
thanks

Could reproduce it, after applying patch by Baptiste Jammet (see #851414)
no longer reproducable.  Therefore, closing in upcoming upload.

Thanks!

On Thu, Nov 30, 2017 at 07:00:18AM +0100, Joost van Baal-Ilić wrote:
> Yes, this is indeed buggy.  I'll work on it.  More details below.




Bug#859671: marked as done (qtbase-opensource-src: Please migrate to openssl1.1 in Buster)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 09:34:36 +
with message-id 
and subject line Bug#859671: fixed in qtbase-opensource-src 5.10.0~rc1+dfsg-1
has caused the Debian Bug report #859671,
regarding qtbase-opensource-src: Please migrate to openssl1.1 in Buster
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.)


-- 
859671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qtbase-opensource-src
Version: 5.7.1~20161021+dfsg-5
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle.

Sebastian
--- End Message ---
--- Begin Message ---
Source: qtbase-opensource-src
Source-Version: 5.10.0~rc1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
qtbase-opensource-src, 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 859...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated qtbase-opensource-src 
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: Tue, 28 Nov 2017 16:43:35 +0300
Source: qtbase-opensource-src
Binary: libqt5core5a libqt5gui5 qt5-gtk-platformtheme libqt5network5 
libqt5opengl5 libqt5sql5 libqt5sql5-mysql libqt5sql5-odbc libqt5sql5-psql 
libqt5sql5-sqlite libqt5sql5-tds libqt5sql5-ibase libqt5xml5 libqt5dbus5 
libqt5test5 libqt5concurrent5 libqt5widgets5 libqt5printsupport5 qtbase5-dev 
qtbase5-private-dev libqt5opengl5-dev qtbase5-dev-tools qt5-qmake-bin qt5-qmake 
qtbase5-examples qt5-default qtbase5-doc qtbase5-doc-html
Architecture: source
Version: 5.10.0~rc1+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Dmitry Shachnev 
Description:
 libqt5concurrent5 - Qt 5 concurrent module
 libqt5core5a - Qt 5 core module
 libqt5dbus5 - Qt 5 D-Bus module
 libqt5gui5 - Qt 5 GUI module
 libqt5network5 - Qt 5 network module
 libqt5opengl5 - Qt 5 OpenGL module
 libqt5opengl5-dev - Qt 5 OpenGL library development files
 libqt5printsupport5 - Qt 5 print support module
 libqt5sql5 - Qt 5 SQL module
 libqt5sql5-ibase - Qt 5 Firebird database driver
 libqt5sql5-mysql - Qt 5 MySQL database driver
 libqt5sql5-odbc - Qt 5 ODBC database driver
 libqt5sql5-psql - Qt 5 PostgreSQL database driver
 libqt5sql5-sqlite - Qt 5 SQLite 3 database driver
 libqt5sql5-tds - Qt 5 FreeTDS database driver
 libqt5test5 - Qt 5 test module
 libqt5widgets5 - Qt 5 widgets module
 libqt5xml5 - Qt 5 XML module
 qt5-default - Qt 5 development defaults package
 qt5-gtk-platformtheme - Qt 5 GTK+ 3 platform theme
 qt5-qmake  - Qt 5 qmake Makefile generator tool
 qt5-qmake-bin - Qt 5 qmake Makefile generator tool — binary file
 qtbase5-dev - Qt 5 base development files
 qtbase5-dev-tools - Qt 5 base development programs
 qtbase5-doc - Qt 5 base documentation
 qtbase5-doc-html - Qt 5 base HTML documentation
 qtbase5-examples - Qt 5 base examples
 qtbase5-private-dev - Qt 5 base private development files
Closes: 859671
Changes:
 qtbase-opensource-src (5.10.0~rc1+dfsg-1) experimental; urgency=medium
 .
   * New upstream release candidate.
   * Update debian/watch to track 5.10 development releases.
   * Drop qglxconvenience_nullptr.diff, included upstream.
   * Build with OpenSSL 1.1 (closes: #859671).
   * Update install files for the new version.
   * Update symbols files from the current build logs.
   * Update debian/copyright using debian/scripts/update-copyright.
Checksums-Sha1:
 aa3e9bc2b0611b94ca43049006b481911fcc565a 5069 
qtbase-opensource-src_5.10.0~rc1+dfsg-1.dsc
 31c1d2e249002bfa60624edae980bc189c39a4ac 45657604 
qtbase-opensource-src_5.10.0~rc1+dfsg.orig.tar.xz
 fc35251369320617aee8d94e1147b5dc7d775f35 220196 
qtbase-opensource-src_5.10.0~rc1+dfsg-1.debian.tar.xz
 a23a13aceeacddb9d197391ae7b3ad0634ed5477 9228 
qtbase-opensource-src_5.10.0~rc1+dfsg-1_source.buildinfo
Checksums-Sha256:
 75f59bc408a479ab3539f901eafaaef02776f3329f76bb8023f65f7ef93c9e79 

Processed: Re: Bug#871105: debian-faq: FTBFS: Addendum po4a/add_fr/commentaires.add does NOT apply to fr/debian-faq.sgml (translation discarded).

2017-11-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 871105 pending
Bug #871105 [src:debian-faq] debian-faq: FTBFS: Addendum 
po4a/add_fr/commentaires.add does NOT apply to fr/debian-faq.sgml (translation 
discarded).
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#883159: bind9 FTBFS in binary-any builds

2017-11-30 Thread Adrian Bunk
Source: bind9
Version: 1:9.11.2+dfsg-1
Severity: serious

https://buildd.debian.org/status/package.php?p=bind9=sid

...
cp doc/arm/*.html debian/bind9-doc/usr/share/doc/bind9-doc/arm
cp: target 'debian/bind9-doc/usr/share/doc/bind9-doc/arm' is not a directory
debian/rules:129: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1



Bug#882924: marked as done (php-symfony-security-acl FTBFS with phpunit 6.4.4-2)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 09:04:01 +
with message-id 
and subject line Bug#882924: fixed in php-symfony-security-acl 3.0.0-3
has caused the Debian Bug report #882924,
regarding php-symfony-security-acl FTBFS with phpunit 6.4.4-2
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.)


-- 
882924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-symfony-security-acl
Version: 3.0.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-symfony-security-acl.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-symfony-security-acl-3.0.0'
phpunit --bootstrap autoload.php
PHP Fatal error:  Class 'PHPUnit_Framework_TestCase' not found in 
/build/1st/php-symfony-security-acl-3.0.0/Tests/Dbal/AclProviderBenchmarkTest.php
 on line 23
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 255
--- End Message ---
--- Begin Message ---
Source: php-symfony-security-acl
Source-Version: 3.0.0-3

We believe that the bug you reported is fixed in the latest version of
php-symfony-security-acl, 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 882...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated php-symfony-security-acl 
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, 29 Nov 2017 22:32:44 -1000
Source: php-symfony-security-acl
Binary: php-symfony-security-acl
Architecture: source
Version: 3.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Description:
 php-symfony-security-acl -
Closes: 882924
Changes:
 php-symfony-security-acl (3.0.0-3) unstable; urgency=medium
 .
   * Update test for recent phpunit versions (Closes: #882924)
   * Drop versioned dependencies satisfied in stable
   * Update Standards-Version to 4.1.1
Checksums-Sha1:
 8f2bbf777bfa8ba41877d4e772db05bf42c76c01 1982 
php-symfony-security-acl_3.0.0-3.dsc
 cf595aebc11afb4780456765ff61868dd85bbe5e 6856 
php-symfony-security-acl_3.0.0-3.debian.tar.xz
Checksums-Sha256:
 2632ed765c02ff951e8dd5d5e39356f7d6e43c8b831f24b2f4c8d4e9b805fa09 1982 
php-symfony-security-acl_3.0.0-3.dsc
 711b234544295309bc9d7e4363ed262bfeb6b0cbc890513d78f38dfaf4860692 6856 
php-symfony-security-acl_3.0.0-3.debian.tar.xz
Files:
 0570112a623858f8fe4f0f0cf2dc858f 1982 php optional 
php-symfony-security-acl_3.0.0-3.dsc
 033780e29dd0ee690077f9504606a02c 6856 php optional 
php-symfony-security-acl_3.0.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAlofwwAACgkQBYwc+UT2
vTzrYwf+KpNpQ4XUkp+pSTPtuo8uTLz0RZ1VOtpmHEnOha6lYPWuPAiczkROSytH
DZPbfSwt+e4nqerSHiGMEdHSjX99m56+nMwRaS+mFJr/1rgv3BjjDcdPH/OYq4b+
PJa2tVqHKyvItct/7sdzqMWD9+NzY2clUV2tCqAo1DKjFOOqAfmL/Quj+WMrt/Pl
5gF6AMeQHsS7++VSLrIOfPQwZK7gqP44hs0efGG6fe24AAFwJvNC04ovkFjVPc8g
Owngmi8iENnQiUb6pVFk9XGZ0c6uh9uKOGGMXR5ACxXHiVcsSO8r6smTMPnAMhXg
0+8B7tlFe1hqiK6mgqCHgka5UbgW/Q==
=aoxc
-END PGP SIGNATURE End Message ---


Bug#882893: marked as done (php-doctrine-data-fixtures FTBFS with phpunit 6.4.4-2)

2017-11-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 Nov 2017 08:53:30 +
with message-id 
and subject line Bug#882893: fixed in php-doctrine-data-fixtures 1.2.2-2
has caused the Debian Bug report #882893,
regarding php-doctrine-data-fixtures FTBFS with phpunit 6.4.4-2
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.)


-- 
882893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-doctrine-data-fixtures
Version: 1.2.2-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-doctrine-data-fixtures.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-doctrine-data-fixtures-1.2.2'
phpunit --include-path lib
PHP Fatal error:  Class 'PHPUnit_Framework_TestCase' not found in 
/build/1st/php-doctrine-data-fixtures-1.2.2/tests/Doctrine/Tests/Common/DataFixtures/BaseTest.php
 on line 32
debian/rules:21: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 255
--- End Message ---
--- Begin Message ---
Source: php-doctrine-data-fixtures
Source-Version: 1.2.2-2

We believe that the bug you reported is fixed in the latest version of
php-doctrine-data-fixtures, 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 882...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated 
php-doctrine-data-fixtures 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, 29 Nov 2017 21:26:21 -1000
Source: php-doctrine-data-fixtures
Binary: php-doctrine-data-fixtures
Architecture: source
Version: 1.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Description:
 php-doctrine-data-fixtures -
Closes: 882893
Changes:
 php-doctrine-data-fixtures (1.2.2-2) unstable; urgency=medium
 .
   * Update tests for recent phpunit versions (Closes: #882893)
   * Drop versioned dependencies satisfied in stable
Checksums-Sha1:
 c072fee1a312a287d0a27a41c3a8614d2cd2df83 1925 
php-doctrine-data-fixtures_1.2.2-2.dsc
 d1d662da7a25e208a427ed906a7cedac62650a31 5316 
php-doctrine-data-fixtures_1.2.2-2.debian.tar.xz
Checksums-Sha256:
 03ecd88dc83f0abf3cef70842c4b8a1484664e81a72be440f3e27d7751280f72 1925 
php-doctrine-data-fixtures_1.2.2-2.dsc
 8a94292a3c6ada9fb082cea4d1bf0e288dd2997af6b0789482270dbeb36ae179 5316 
php-doctrine-data-fixtures_1.2.2-2.debian.tar.xz
Files:
 37afa5309ea718b1bde180a8d54f4a12 1925 php optional 
php-doctrine-data-fixtures_1.2.2-2.dsc
 ba00b6af61cbec62e057f69db0bf9e4e 5316 php optional 
php-doctrine-data-fixtures_1.2.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAloftJwACgkQBYwc+UT2
vTys8Af9HGCEHDnbJGqsZv4jg2+gYadpsiW1TqIkUYRNCcaX1dJu5FP1dUs0JLj1
i85NuyRCt7NHsylNOGg2HlTJzxwFGqoZjXPsiJd2EOQBVAMSjWa5oW63wfHEcL6j
IMWSnTgAwbXvxDVxbIDCeSAVizQp/ACNdjK7cAzhqjGVtKb8bHwZP13rUrZfz70x
ycrNGQKsh1JwIEhNjTVWMwYhrGViuzAeGfHzZ50ERo0oukwgGIbIRB8o82cIZhlU
GjJDJde3GCHwRMKXknY4S9NMC6KnCTMSq+snrUz0Rzk52zs+PoadbKc2gZMXKW4l
foQuAaTGH2kLpdt4THUuj6tPlbSDXw==
=CMwW
-END PGP SIGNATURE End Message ---


Processed: limit source to php-symfony-security-acl, tagging 882924

2017-11-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> limit source php-symfony-security-acl
Limiting to bugs with field 'source' containing at least one of 
'php-symfony-security-acl'
Limit currently set to 'source':'php-symfony-security-acl'

> tags 882924 + pending
Bug #882924 [src:php-symfony-security-acl] php-symfony-security-acl FTBFS with 
phpunit 6.4.4-2
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#881328: mininet requires missing ovs-controller

2017-11-30 Thread Santiago R.R.
Control: tags -1 + patch fixed-upstream

On Fri, 10 Nov 2017 12:15:39 +0100 "Santiago R.R."  
wrote:
…
> mn tries to run ovs-controller, which has been renamed to
> /usr/bin/ovs-testcontroller according to
> https://github.com/openvswitch/ovs/blob/9a180f2c002adf73951e0ee9990c44e5e5cd4a0f/NEWS#L600

ovs-controller -> test-controller -> ovs-testcontroller

https://github.com/openvswitch/ovs/blob/9a180f2c002adf73951e0ee9990c44e5e5cd4a0f/NEWS#L471

> mininet should Depends or Recomends on openvswitch-testcontroller

It seems I am wrong about this.

> 
> $ sudo mn --topo tree,depth=2,fanout=3
> *** Creating network
> *** Adding controller
> *** Adding hosts:
> h1 h2 h3 h4 h5 h6 h7 h8 h9
> *** Adding switches:
> s1 s2 s3 s4
> *** Adding links:
> (s1, s2) (s1, s3) (s1, s4) (s2, h1) (s2, h2) (s2, h3) (s3, h4) (s3, h5) (s3, 
> h6) (s4, h7) (s4, h8) (s4, h9)
> *** Configuring hosts
> h1 h2 h3 h4 h5 h6 h7 h8 h9
> *** Starting controller
> c0 Cannot find required executable ovs-controller.
> Please make sure that it is installed and available in your $PATH:
> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin)
…
> Versions of packages mininet depends on:
> ii  cgroup-bin0.41-8
> ii  iperf 2.0.10+dfsg1-1
> ii  libc6 2.24-17
> ii  net-tools 1.60+git20161116.90da8a0-1
> ii  openvswitch-switch2.8.1+dfsg1-3
> ii  python2.7.14-1
> ii  python-pkg-resources  36.6.0-1
> ii  socat 1.7.3.2-1
> ii  telnet0.17-41

(I am new on this, and I am trying to understand how mininet relies on
openvswitch, so sorry if what I say doesn't make any sense.)

Actually, the issue doesn't happen in stretch or buster, or more
precisely, with openvswitch-switch 2.6.2~pre+git20161223-3.

As far as I understand, the reason why mininet complains against
openvswtich is because openvswith-common includes
/usr/bin/ovs-testcontroller since 2.8.1+dfsg1-1. Binary that was part of
openvswitch-testcontroller before. Installing -testcontroller in stretch
or buster makes that mininet also complains.

And it also seems that it was already fixed by upstream in commit
57abd9baef8b3ec3ce3c349829b37022cfef724a. Patch attached to this mail.

Cheers,

  -- Santiago

P.S. Question for openvswitch maintainers: does it make sense to include
back /usr/bin/ovs-testcontroller in the -testcontroller package?
From a5a3485edbb15d2442eb42d776fb9ba370526e7a Mon Sep 17 00:00:00 2001
From: Santiago 
Date: Wed, 29 Nov 2017 18:30:12 +0100
Subject: [PATCH] Add
 debian/patches/upstream_0001-Use-correct-command-name-in-OVSController.patch
 to take into account the three possible names of ovs-testcontroller

Signed-off-by: Santiago 
---
 debian/patches/series  |  1 +
 ...Use-correct-command-name-in-OVSController.patch | 38 ++
 2 files changed, 39 insertions(+)
 create mode 100644 debian/patches/series
 create mode 100644 debian/patches/upstream_0001-Use-correct-command-name-in-OVSController.patch

diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..54f122c
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+upstream_0001-Use-correct-command-name-in-OVSController.patch
diff --git a/debian/patches/upstream_0001-Use-correct-command-name-in-OVSController.patch b/debian/patches/upstream_0001-Use-correct-command-name-in-OVSController.patch
new file mode 100644
index 000..e91ea01
--- /dev/null
+++ b/debian/patches/upstream_0001-Use-correct-command-name-in-OVSController.patch
@@ -0,0 +1,38 @@
+From 57abd9baef8b3ec3ce3c349829b37022cfef724a Mon Sep 17 00:00:00 2001
+From: Bob Lantz 
+Date: Tue, 24 May 2016 17:40:00 -0700
+Subject: [PATCH] Use correct command name in OVSController
+
+---
+ mininet/node.py | 10 +-
+ 1 file changed, 5 insertions(+), 5 deletions(-)
+
+diff --git a/mininet/node.py b/mininet/node.py
+index ea7851b..1e50b51 100644
+--- a/mininet/node.py
 b/mininet/node.py
+@@ -1423,16 +1423,16 @@ def isAvailable( cls ):
+ 
+ class OVSController( Controller ):
+ "Open vSwitch controller"
+-def __init__( self, name, command='ovs-controller', **kwargs ):
+-if quietRun( 'which test-controller' ):
+-command = 'test-controller'
+-Controller.__init__( self, name, command=command, **kwargs )
++def __init__( self, name, **kwargs ):
++kwargs.setdefault( 'command', self.isAvailable() or
++   'ovs-controller' )
++Controller.__init__( self, name, **kwargs )
+ 
+ @classmethod
+ def isAvailable( cls ):
+ return ( quietRun( 'which ovs-controller' ) or
+  quietRun( 'which test-controller' ) or
+- quietRun( 'which ovs-testcontroller' ) )
++ quietRun( 'which ovs-testcontroller' ) ).strip()
+ 
+ class NOX( 

Processed: Re: mininet requires missing ovs-controller

2017-11-30 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch fixed-upstream
Bug #881328 [mininet] mininet requires missing ovs-controller
Added tag(s) patch and fixed-upstream.

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