Bug#882141: closed by Scott Kitterman <sc...@kitterman.com> (Bug#882141: fixed in postfix 3.2.4-1)

[Scott Kitterman]

On Fri, 9 Feb 2018 09:34:43 +0100 Bastian Blank  wrote:
> On Fri, Feb 09, 2018 at 01:50:29AM -0500, Scott Kitterman wrote:
> > Because I don't get that error when I try to replicate the condition.
> 
> So postconf does not fail for you if inet_interfaces lists an ip the
> system does not currently have?
> 
> > Feb 09 01:28:58 relay02 postmulti[3783]: fatal: parameter inet_interfaces: 
no 
> > local interface found for 1.2.3.4
> 
> According to this, postmulti errors out.  And as postconf uses the same
> code, I don't see how it would succeed.
> 
> > Not sure how to replicate the error you're having.
> 
> The problem is a failing postconf/postmulti if the ip does not exists.
> And while the generator is called, apart from 127.0.0.1 and ::1, _none_
> exist.

Would you please check that your /lib/systemd/system/postfix@.service has:

After=network-online.target nss-lookup.target
Wants=network-online.target

At least as I understand it, that's supposed to make sure the network is up 
before postfix starts.

Scott K

Processed: fix tag

[Debian Bug Tracking System]

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

> tag 889533 + sid
Bug #889533 [src:leiningen-clojure] leiningen-clojure FTBFS with 
libclojure-java 1.9.0~alpha15-1
Added tag(s) sid.
>
End of message, stopping processing here.

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

Bug#889533: leiningen-clojure FTBFS with libclojure-java 1.9.0~alpha15-1

[Elana Hashman]

Control: tags sid


Hi Adrian! Thanks for your report. The Clojure Team was aware of this
bug but has not yet fixed it.

Leiningen is not compatible with Clojure >1.8 as a build dependency.
This is why I blocked the new Clojure 1.9 alpha from migrating to
testing (#887382).

Hence, this bug doesn't exactly affect version 2.8.1-4. This version of
leiningen will build just fine in testing, but the bug marks that for
removal too.

I will mark this as closed once we upload a versioned clojure1.8 to
coexist with version 1.9 in the clojure package, and change leiningen's
builddep to use clojure1.8.

- e


signature.asc
Description: Digital signature

Bug#860198: ruby-rack-proxy: accesses the internet during build

[Sergio Durigan Junior]

Control: tags -1 + patch

On Wednesday, April 12 2017, Chris Lamb wrote:

> Dear Maintainer,
>
> Whilst ruby-rack-proxy builds successfully on unstable/amd64, according to
> Debian Policy 4.9 packages may not attempt network access during
> a build.
>
>00:00:00.00 IP d682a225d2b3.36041 > OpenWrt.lan.domain: 28604+ A? 
> www.trix.pl. (29)
>00:00:00.44 IP d682a225d2b3.36041 > OpenWrt.lan.domain: 34431+ ? 
> www.trix.pl. (29)
>00:00:00.092699 IP OpenWrt.lan.domain > d682a225d2b3.36041: 28604 2/0/0 
> CNAME the-trix.herokuapp.com., A 79.125.24.174 (81)
>00:00:00.191672 IP OpenWrt.lan.domain > d682a225d2b3.36041: 34431 1/0/0 
> CNAME the-trix.herokuapp.com. (65)
>00:00:00.191856 IP d682a225d2b3.57820 > 
> ec2-79-125-24-174.eu-west-1.compute.amazonaws.com.http: Flags [S], seq 
> 1530273777, win 29200, options [mss 1460,sackOK,TS val 260183652 ecr 
> 0,nop,wscale 7], length 0
>00:00:00.213026 IP ec2-79-125-24-174.eu-west-1.compute.amazonaws.com.http 
> > d682a225d2b3.57820: Flags [S.], seq 3395934634, ack 1530273778, win 26847, 
> options [mss 1400,sackOK,TS val 558302644 ecr 260183652,nop,wscale 8], length > 0
>00:00:00.213062 IP d682a225d2b3.57820 > 
> ec2-79-125-24-174.eu-west-1.compute.amazonaws.com.http: Flags [.], ack 1, win 
> 229, options [nop,nop,TS val 260183657 ecr 558302644], length 0
>00:00:00.213380 IP d682a225d2b3.57820 > 
> ec2-79-125-24-174.eu-west-1.compute.amazonaws.com.http: Flags [P.], seq 
> 1:127, ack 1, win 229, options [nop,nop,TS val 260183657 ecr 558302644], 
> length 126: HTTP: GET / HTTP/1.1
>00:00:00.237399 IP ec2-79-125-24-174.eu-west-1.compute.amazonaws.com.http 
> > d682a225d2b3.57820: Flags [.], ack 127, win 105, options [nop,nop,TS val 
> 558302650 ecr 260183657], length 0
>00:00:00.253453 IP ec2-79-125-24-174.eu-west-1.compute.amazonaws.com.http 
> > d682a225d2b3.57820: Flags [.], seq 1:1389, ack 127, win 105, options 
> [nop,nop,TS val 558302653 ecr 260183657], length 1388: HTTP: HTTP/1.1 200 OK 
>
>   [..]
>
> The full build log (including tcpdump output) is attached.

Hi,

I decided to give this bug a try, and came up with the patch attached.

The problem here is that some testcases are trying to access the
internet, which, as has been mentioned already, is not allowed under the
Debian Policy.  Unfortunately, this is one of those cases when it's not
really possible to disable network access for the tests, so the "best"
fix is to prevent the tests from running.  The patch does that.

This makes the package buildable on my cowbuilder chroot (without
internet) again.

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

diff --git a/debian/changelog b/debian/changelog
index aedc978..a38cfef 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+ruby-rack-proxy (0.6.1-2) unstable; urgency=medium
+
+  * Prevent testcases that access the internet to run.
+Some testcases (test/http_streaming_response_test.rb and
+test/rack_proxy_test.rb) try to access the internet, but that is
+against Debian Policy guidelines, and therefore we need to disable
+them. (Closes: #860198)
+
+ -- Sergio Durigan Junior   Sun, 11 Feb 2018 18:15:01 -0500
+
 ruby-rack-proxy (0.6.1-1) unstable; urgency=medium
 
   * Initial release (Closes: #859878)
diff --git a/debian/ruby-tests.rake b/debian/ruby-tests.rake
index c085c38..b856dc9 100644
--- a/debian/ruby-tests.rake
+++ b/debian/ruby-tests.rake
@@ -2,5 +2,5 @@ require 'gem2deb/rake/testtask'
 
 Gem2Deb::Rake::TestTask.new do |t|
   t.libs = ['test']
-  t.test_files = FileList['test/**/*_test.rb'] + FileList['test/**/test_*.rb'] - FileList['test/net_http_hacked_test.rb']
+  t.test_files = FileList['test/**/*_test.rb'] + FileList['test/**/test_*.rb'] - FileList['test/net_http_hacked_test.rb'] - FileList['test/http_streaming_response_test.rb'] - FileList['test/rack_proxy_test.rb']
 end


signature.asc
Description: PGP signature

Processed: Re: Bug#860198: ruby-rack-proxy: accesses the internet during build

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #860198 [src:ruby-rack-proxy] ruby-rack-proxy: accesses the internet during 
build
Added tag(s) patch.

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

Bug#888912: marked as done (sagemath test failures with mpfr 4.0.0 and several architectures)

[Debian Bug Tracking System]

Your message dated Sun, 11 Feb 2018 23:50:34 +
with message-id 
and subject line Bug#888912: fixed in sagemath 8.1-3
has caused the Debian Bug report #888912,
regarding sagemath test failures with mpfr 4.0.0 and several architectures
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.)


-- 
888912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sagemath
Version: 8.2-1
Severity: serious
Tags: sid buster

see https://buildd.debian.org/status/package.php?p=sagemath=unstable

test failures on every architecture.
--- End Message ---
--- Begin Message ---
Source: sagemath
Source-Version: 8.1-3

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated sagemath package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Feb 2018 21:20:28 +
Source: sagemath
Binary: sagemath sagemath-common sagemath-jupyter sagemath-doc-ca 
sagemath-doc-de sagemath-doc-en sagemath-doc-es sagemath-doc-fr sagemath-doc-hu 
sagemath-doc-it sagemath-doc-ja sagemath-doc-pt sagemath-doc-ru sagemath-doc-tr
Architecture: source
Version: 8.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Hansen 
Description:
 sagemath   - Open Source Mathematical Software
 sagemath-common - Open Source Mathematical Software - architecture-independent 
file
 sagemath-doc-ca - Open Source Mathematical Software - documentation (Catalan; 
Valen
 sagemath-doc-de - Open Source Mathematical Software - documentation (German)
 sagemath-doc-en - Open Source Mathematical Software - documentation (English)
 sagemath-doc-es - Open Source Mathematical Software - documentation (Spanish; 
Casti
 sagemath-doc-fr - Open Source Mathematical Software - documentation (French)
 sagemath-doc-hu - Open Source Mathematical Software - documentation (Hungarian)
 sagemath-doc-it - Open Source Mathematical Software - documentation (Italian)
 sagemath-doc-ja - Open Source Mathematical Software - documentation (Japanese)
 sagemath-doc-pt - Open Source Mathematical Software - documentation 
(Portuguese)
 sagemath-doc-ru - Open Source Mathematical Software - documentation (Russian)
 sagemath-doc-tr - Open Source Mathematical Software - documentation (Turkish)
 sagemath-jupyter - Open Source Mathematical Software - Jupyter kernel
Closes: 888912
Changes:
 sagemath (8.1-3) unstable; urgency=medium
 .
   [ Tobias Hansen ]
   * Update Vcs-* links for salsa.
   * New patches:
 - u0-version-mpfr-4.0.patch
   Fixes for libmpfr 4.0.
 - u0-version-matplotlib-2.1.0.patch
   New dependencies:
   - python-subprocess32
   - python-backports.functools-lru-cache
   * Modified patches:
 - dt-more-fix-test-cases.patch
   Fix ordering issue in two tests in the documentation.
 .
   [ Ximin Luo ]
   * Tests now pass fine after fixes in other packages. (Closes: #888912)
   * Modified patches:
 - dt-more-fix-test-cases.patch
   Ignore sigabrt in sage_object.pyx doctest.
   * Add dbg packages to the pkg.sagemath.dbg build-profile to make
 stack traces work.
   * Touch the dummy spkg file to avoid rebuilds in some cases.
Checksums-Sha1:
 da3d5c5c97a1f506e2e434c371c512061a06b145 6813 sagemath_8.1-3.dsc
 5d65c9398852d707469002b5606e9780f2c13d98 87168 sagemath_8.1-3.debian.tar.xz
 38110b32f4c89cde6539c618b271ae8ff456f440 28264 sagemath_8.1-3_source.buildinfo
Checksums-Sha256:
 8c9c43beb06e0e812db552147930d1aa50a4266001ab40b6ec1565e0437103dd 6813 
sagemath_8.1-3.dsc
 bee3f0f0724ab17c546417fe348e9ac11d68e5b3399426f51d38abcef65cd0cd 87168 
sagemath_8.1-3.debian.tar.xz
 7d7befe56dc3b71fa24b80b2b9a013b9e741754c462bbbccbf501fce37ca716c 28264 
sagemath_8.1-3_source.buildinfo
Files:
 8ff2b0361ddba17a4a69eba91209df86 6813 math optional sagemath_8.1-3.dsc
 

Processed: fixed 890098 in 3.1.0-5

[Debian Bug Tracking System]

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

> fixed 890098 3.1.0-5
Bug #890098 {Done: Rafael Laboissière } [octave-interval] 
FTBFS: imagemagick in Build-Depends-Indep but needed for arch build
Marked as fixed in versions octave-interval/3.1.0-5.
> thanks
Stopping processing here.

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

Bug#888403: marked as done (u-boot: FTBFS on arm64: relocation R_AARCH64_ABS16 against `EFI_SUBSYSTEM')

[Debian Bug Tracking System]

Your message dated Sun, 11 Feb 2018 14:08:30 -0800
with message-id <87inb3kwm9@aikidev.net>
and subject line Re: Bug#888403: u-boot: FTBFS on arm64: relocation 
R_AARCH64_ABS16 against `EFI_SUBSYSTEM'
has caused the Debian Bug report #888403,
regarding u-boot: FTBFS on arm64: relocation R_AARCH64_ABS16 against 
`EFI_SUBSYSTEM'
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.)


-- 
888403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: u-boot
Version: 2017.11+dfsg1-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid that u-boot fails to build on arm64, both the unstable and
experimental versions:

ld.bfd: arch/arm/lib/crt0_aarch64_efi.o: relocation R_AARCH64_ABS16 against 
`EFI_SUBSYSTEM' can not be used when making a shared object
scripts/Makefile.lib:399: recipe for target 'lib/efi_loader/helloworld_efi.so' 
failed
make[5]: *** [lib/efi_loader/helloworld_efi.so] Error 1
rm lib/efi_loader/helloworld.o
/<>/u-boot-2017.11+dfsg1/scripts/Makefile.build:425: recipe for 
target 'lib/efi_loader' failed
make[4]: *** [lib/efi_loader] Error 2

Reproduced on reproducible builds as well.  Adrian Bunk suggests it's due to
recent binutils upgrade.

Log attached.


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 4.15.0-rc9-00159-g643b0ec3477e (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


u-boot_arm64.build
Description: inode/symlink
--- End Message ---
--- Begin Message ---
On 2018-01-24, Adam Borowski wrote:
> I'm afraid that u-boot fails to build on arm64, both the unstable and
> experimental versions:
>
> ld.bfd: arch/arm/lib/crt0_aarch64_efi.o: relocation R_AARCH64_ABS16 against 
> `EFI_SUBSYSTEM' can not be used when making a shared object
> scripts/Makefile.lib:399: recipe for target 
> 'lib/efi_loader/helloworld_efi.so' failed
> make[5]: *** [lib/efi_loader/helloworld_efi.so] Error 1
> rm lib/efi_loader/helloworld.o
> /<>/u-boot-2017.11+dfsg1/scripts/Makefile.build:425: recipe for 
> target 'lib/efi_loader' failed
> make[4]: *** [lib/efi_loader] Error 2
>
> Reproduced on reproducible builds as well.  Adrian Bunk suggests it's due to
> recent binutils upgrade.

This was fixed in binutils 2.30-2, bug #888789.

I've tested with a couple local builds as well as on the reproducible
builds infrastructure, and it is building successfully again.


live well,
  vagrant


signature.asc
Description: PGP signature
--- End Message ---

Bug#890098: marked as done (FTBFS: imagemagick in Build-Depends-Indep but needed for arch build)

[Debian Bug Tracking System]

Your message dated Sun, 11 Feb 2018 22:31:25 +0100
with message-id <20180211213125.gn15...@laboissiere.net>
and subject line Re: Bug#890098: FTBFS: imagemagick in Build-Depends-Indep but 
needed for arch build
has caused the Debian Bug report #890098,
regarding FTBFS: imagemagick in Build-Depends-Indep but needed for arch build
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.)


-- 
890098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: octave-interval
Version: 3.1.0-4
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear maintainer,

The latest upload of octave-interval fails to build on all architectures
currently on the autobuilders because, with the move to dh-octave,
imagemagick is now needed as part of the arch build, not just the
arch-independent build:

OCTAVE='octave --no-window-system --no-init-file --eval "addpath (genpath 
(\"../debian/octave-interval/usr\"));"' \
make -C doc manual.html
make[2]: Entering directory '/<>/doc'
octave --no-window-system --no-init-file --eval "addpath (genpath 
(\"../debian/octave-interval/usr\"));" \
--no-gui --silent --no-history \
--eval "source ('image/interval-sombrero.m');" \
--eval "print (gcf, 'image/interval-sombrero.m.png');"
warning: print.m: epstool binary is not available.
Some output formats are not available.
warning: called from
__print_parse_opts__ at line 385 column 9
print at line 315 column 8
warning: print.m: fig2dev binary is not available.
Some output formats are not available.
warning: called from
__print_parse_opts__ at line 388 column 9
print at line 315 column 8
warning: print.m: pstoedit binary is not available.
Some output formats are not available.
warning: called from
__print_parse_opts__ at line 391 column 9
print at line 315 column 8
convert -density 98.425 -units PixelsPerCentimeter 
"image/interval-sombrero.m.png" "image/interval-sombrero.m.png"
/bin/sh: 1: convert: not found
Makefile:26: recipe for target 'image/interval-sombrero.m.png' failed
make[2]: *** [image/interval-sombrero.m.png] Error 127
make[2]: Leaving directory '/<>/doc'
debian/rules:39: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 2

(https://buildd.debian.org/status/fetch.php?pkg=octave-interval=amd64=3.1.0-4=1518313429=0)

Moving imagemagick from build-depends-indep to build-depends is sufficient
to fix this build failure.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru octave-interval-3.1.0/debian/control 
octave-interval-3.1.0/debian/control
--- octave-interval-3.1.0/debian/control2018-01-26 05:47:52.0 
-0800
+++ octave-interval-3.1.0/debian/control2018-02-10 23:37:27.0 
-0800
@@ -4,9 +4,9 @@
 Maintainer: Debian Octave Group 
 Uploaders: Oliver Heimlich ,
 Build-Depends-Indep: texinfo, texlive, texlive-generic-recommended,
- imagemagick, gnuplot-nox,
+ gnuplot-nox,
 Build-Depends: debhelper (>= 11), dh-octave,
- libmpfr-dev (>= 3.1.0), ghostscript
+ libmpfr-dev (>= 3.1.0), ghostscript, imagemagick
 Standards-Version: 4.1.3
 Homepage: https://octave.sourceforge.io/interval/
 Vcs-Git: https://salsa.debian.org/pkg-octave-team/octave-interval.git
--- End Message ---
--- Begin Message ---

Control: fixed -1 3.1.0-5

* Rafael Laboissière  [2018-02-11 10:42]:


* Steve Langasek  [2018-02-10 23:50]:


Package: octave-interval
Version: 3.1.0-4
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear maintainer,

The latest upload of octave-interval fails to build on all 
architectures currently on the autobuilders because, with the move 
to dh-octave, imagemagick is now needed as part of the arch build, 
not just the arch-independent build:


[snip]


Thanks for the bug report.  Indeed, I screwed things up in commit 
e22b79d.  I will look at this soon.


It is done.  I am hereby closing this bug report because I wrote the 
wrong number in the "Closes:" statement in debian/changelog of version 
3.1.0-5 of the package.

Bug#889303: marked as done (syslog-ng FTBFS: FAIL: modules/python/pylib/test_pylib)

[Debian Bug Tracking System]

Your message dated Sun, 11 Feb 2018 21:27:25 +
with message-id 
and subject line Bug#889303: fixed in syslog-ng 3.13.2-3
has caused the Debian Bug report #889303,
regarding syslog-ng FTBFS: FAIL: modules/python/pylib/test_pylib
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.)


-- 
889303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: syslog-ng
Version: 3.13.2-2
Severity: serious

Some recent change in unstable makes syslog-ng FTBFS:

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

...
FAIL: modules/python/pylib/test_pylib
=

make[7]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
nosetests ../../modules/python/pylib/syslogng

--
Ran 108 tests in 0.230s

OK
pep8 --ignore=E501 ../../modules/python/pylib/syslogng
pylint -r n --rcfile=../../modules/python/pylib/pylintrc 
../../modules/python/pylib/syslogng
Using config file /build/1st/syslog-ng-3.13.2/modules/python/pylib/pylintrc
Unable to create directory /nonexistent/first-build/.pylint.d
Unable to create file /nonexistent/first-build/.pylint.d/syslogng1.stats: 
[Errno 2] No such file or directory: 
'/nonexistent/first-build/.pylint.d/syslogng1.stats'
* Module syslogng.debuggercli.templatelexer
/build/1st/syslog-ng-3.13.2/modules/python/pylib/syslogng/debuggercli/templatelexer.py:127:
 [R1710(inconsistent-return-statements), 
TemplateLexer.t_dollarparen_PAREN_CLOSE] Either all return statements in a 
function should return an expression, or none of them should.
* Module syslogng.debuggercli.completerlang
/build/1st/syslog-ng-3.13.2/modules/python/pylib/syslogng/debuggercli/completerlang.py:57:
 [R1710(inconsistent-return-statements), CompleterLang.p_error] Either all 
return statements in a function should return an expression, or none of them 
should.
* Module syslogng.debuggercli.commandlinelexer
/build/1st/syslog-ng-3.13.2/modules/python/pylib/syslogng/debuggercli/commandlinelexer.py:56:
 [R1710(inconsistent-return-statements), CommandLineLexer._get_next_token] 
Either all return statements in a function should return an expression, or none 
of them should.
/build/1st/syslog-ng-3.13.2/modules/python/pylib/syslogng/debuggercli/commandlinelexer.py:89:
 [R1710(inconsistent-return-statements), 
CommandLineLexer._process_normal_character] Either all return statements in a 
function should return an expression, or none of them should.
/build/1st/syslog-ng-3.13.2/modules/python/pylib/syslogng/debuggercli/commandlinelexer.py:105:
 [R1710(inconsistent-return-statements), CommandLineLexer._close_paren] Either 
all return statements in a function should return an expression, or none of 
them should.
/build/1st/syslog-ng-3.13.2/modules/python/pylib/syslogng/debuggercli/commandlinelexer.py:112:
 [R1710(inconsistent-return-statements), CommandLineLexer._close_current_token] 
Either all return statements in a function should return an expression, or none 
of them should.

---
Your code has been rated at 9.96/10

Makefile:18463: recipe for target 'python-pylint' failed
make[7]: *** [python-pylint] Error 8
FAIL modules/python/pylib/test_pylib.sh (exit status: 2)


Testsuite summary for syslog-ng 3.13.2

# TOTAL: 71
# PASS:  70
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log

Makefile:16576: recipe for target 'test-suite.log' failed
make[6]: *** [test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: syslog-ng
Source-Version: 3.13.2-3

We believe that the bug you reported is fixed in the latest version of
syslog-ng, 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 889...@bugs.debian.org,
and the maintainer 

Bug#890110: marked as done (castle-game-engine binary-all FTBFS: install: cannot stat 'tools/texture-font-to-pascal/texture-font-to-pascal': No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 11 Feb 2018 21:20:29 +
with message-id 
and subject line Bug#890110: fixed in castle-game-engine 6.4+dfsg1-2
has caused the Debian Bug report #890110,
regarding castle-game-engine binary-all FTBFS: install: cannot stat 
'tools/texture-font-to-pascal/texture-font-to-pascal': No such file or directory
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.)


-- 
890110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: castle-game-engine
Version: 6.4+dfsg1-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=castle-game-engine=all=6.4%2Bdfsg1-1=1518301579=0

...
   debian/rules override_dh_auto_install-indep
make[1]: Entering directory '/<>/castle-game-engine-6.4+dfsg1'
dh_auto_install
make -j4 install 
DESTDIR=/<>/castle-game-engine-6.4\+dfsg1/debian/tmp 
AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true"
make[2]: Entering directory '/<>/castle-game-engine-6.4+dfsg1'
install -d /<>/castle-game-engine-6.4+dfsg1/debian/tmp/usr/local/bin
install tools/texture-font-to-pascal/texture-font-to-pascal 
/<>/castle-game-engine-6.4+dfsg1/debian/tmp/usr/local/bin
install: cannot stat 'tools/texture-font-to-pascal/texture-font-to-pascal': No 
such file or directory
Makefile:94: recipe for target 'install' failed
make[2]: *** [install] Error 1
--- End Message ---
--- Begin Message ---
Source: castle-game-engine
Source-Version: 6.4+dfsg1-2

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated castle-game-engine package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Feb 2018 20:39:37 +0100
Source: castle-game-engine
Binary: fp-units-castle-game-engine castle-game-engine-doc 
castle-game-engine-src
Architecture: source
Version: 6.4+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Paul Gevers 
Description:
 castle-game-engine-doc - Castle Game Engine - Developer's Documentation
 castle-game-engine-src - Castle Game Engine - Source code for Lazarus 
integration
 fp-units-castle-game-engine - Castle Game Engine - 3D game engine for 
FreePascal / Lazarus
Closes: 890110
Changes:
 castle-game-engine (6.4+dfsg1-2) unstable; urgency=medium
 .
   * Fix arch:all target for stand-alone builds (Closes: #890110)
Checksums-Sha1:
 4e4dc83ccf55e752db48642fa9260bfe26bbf2e6 2305 
castle-game-engine_6.4+dfsg1-2.dsc
 cb5986f4d64281fbf8fd91641bce9cb85eb54aaf 21876 
castle-game-engine_6.4+dfsg1-2.debian.tar.xz
Checksums-Sha256:
 40d39cfd389abe529ebe1452b77352a108160d9e973422eb92f840c5b11a8963 2305 
castle-game-engine_6.4+dfsg1-2.dsc
 3449b4adc707731266bad3886a71aaa8e924830ef095348b9e2a55a2e5c342da 21876 
castle-game-engine_6.4+dfsg1-2.debian.tar.xz
Files:
 0a13490ffeb2dd947bc5aadef6ee15b4 2305 misc optional 
castle-game-engine_6.4+dfsg1-2.dsc
 10d23d57f7f1e50fc1b3f1a8b2e88574 21876 misc optional 
castle-game-engine_6.4+dfsg1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlqAnIoACgkQnFyZ6wW9
dQo7KQgAwLbrAoqCbFJelxhiPpbeaWWCJlPJJg/DFcUq1Sc/g6RjcyZRwn4yfiAl
e27W4K6+uxfzbCE9qBvqV9yQXk3QtygE37Ja5C/6U26Ldie7gbI/RCBJqpgns5rf
aSB675I6HxtaIDBqT8v8kKb0wG82wXvUcSWm711FYJ14TeFilYvuEHONmdwGuSlB
uA9MHYGgc5ftK8Nrb4V55XlaKXS7xL96jikkNXJQfCDiruGMKslhxtOkfLNzWQpr
LptQeEfduFRDhr3HsipA7oHL/1fPhiaVg9ow1CfjlzNYr+T8vmejBM5QfF4azdlb
4ahWajwpRUqoncpIAK9rgwBDpOkwkw==
=g3bJ
-END PGP SIGNATURE End Message ---

Bug#885570: After upgrade I can continue to reproduce this

[Andrew Latham]

I updated to the stretch-proposed-updates version and am very happy thus
far. Sorry for the noise and thank you for the fix.

# uname -a
Linux lappy7 4.9.0-5-amd64 #1 SMP Debian 4.9.80-2 (2018-02-09) x86_64
GNU/Linux

# dmesg | grep 915
[   15.124116] snd_hda_intel :00:03.0: bound :00:02.0 (ops
i915_audio_component_bind_ops [i915])
[   15.124123] [drm] Initialized i915 1.6.0 20160919 for :00:02.0 on
minor 0
[   16.332502] i915 :00:02.0: fb0: inteldrmfb frame buffer device


On Sun, Feb 11, 2018 at 2:11 PM, Andrew Latham  wrote:

> Yves-Alexis
>
> Thank you. Would enabling that repo/branch and testing help at all with
> this?
>
> My confusion is that https://packages.debian.org/stretch/linux-image-amd64
> and https://packages.debian.org/stretch/linux-image-4.9.0-5-amd64 did not
> match up. I wonder if this is a mistake. I will go back and re-read the
> pages.
>
> On Sun, Feb 11, 2018 at 1:59 PM, Yves-Alexis Perez 
> wrote:
>
>> On Sun, 2018-02-11 at 13:33 -0600, Andrew Latham wrote:
>> > Related info in dmesg
>> > [0.00] Linux version 4.9.0-5-amd64
>> (debian-ker...@lists.debian.org)
>> > (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-
>> > 3+deb9u2 (2018-01-04)
>> > [  273.787162] [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO
>> > underrun
>>
>> This is not the fixed version. You want to upgrade to 4.9.80-1 (or -2)
>> which
>> is currently sitting in stable-proposed-updates and will be available in
>> the
>> next point release.
>>
>> Regards,
>> --
>> Yves-Alexis
>
>
>
>
> --
> - Andrew "lathama" Latham -
>



-- 
- Andrew "lathama" Latham -

Bug#746005: lilypond bundles a convenience copy of an ancient guile version

[Don Armstrong]

Control: severity -1 important

On Sun, 11 Feb 2018, Thorsten Glaser wrote:
> Justification: violates Policy 4.1.3.0 §4.13 (Convenience copies of code)
>
> While bundling its own Guile might make lilypond “work” for
> users, it’s definitely not ripe for a stable release like that.

Policy §4.13 is should, not must. This is absolutely a bug, but it's the
only copy of guile 1.8 which is in the archive, and it's this way
because guile 2.0 has multiple issues which have been exposed by
lilypond.

The moment that lilypond upstream releases a version that can actually
build with guile 2.0, we will remove the convenience copy of guile.

As far as stable releases go, if the RMs disagree with this decision,
they can upgrade this bug, but it will mean that lilypond will not stay
in testing, and will not be present in a stable release.


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

The whole modern world has divided itself into Conservatives and
Progressives. The business of Progressives is to go on making
mistakes. The business of the Conservatives is to prevent the mistakes
from being corrected.
 -- G. K. Chesterton "Illustrated London News (1924-04-19)"

Processed: Re: Bug#746005: lilypond bundles a convenience copy of an ancient guile version

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #746005 [lilypond] lilypond: please migrate to guile-2.0
Severity set to 'important' from 'serious'

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

Bug#885570: After upgrade I can continue to reproduce this

[Andrew Latham]

Yves-Alexis

Thank you. Would enabling that repo/branch and testing help at all with
this?

My confusion is that https://packages.debian.org/stretch/linux-image-amd64
and https://packages.debian.org/stretch/linux-image-4.9.0-5-amd64 did not
match up. I wonder if this is a mistake. I will go back and re-read the
pages.

On Sun, Feb 11, 2018 at 1:59 PM, Yves-Alexis Perez 
wrote:

> On Sun, 2018-02-11 at 13:33 -0600, Andrew Latham wrote:
> > Related info in dmesg
> > [0.00] Linux version 4.9.0-5-amd64 (debian-kernel@lists.debian.
> org)
> > (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-
> > 3+deb9u2 (2018-01-04)
> > [  273.787162] [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO
> > underrun
>
> This is not the fixed version. You want to upgrade to 4.9.80-1 (or -2)
> which
> is currently sitting in stable-proposed-updates and will be available in
> the
> next point release.
>
> Regards,
> --
> Yves-Alexis




-- 
- Andrew "lathama" Latham -

Bug#885570: After upgrade I can continue to reproduce this

[Yves-Alexis Perez]

On Sun, 2018-02-11 at 13:33 -0600, Andrew Latham wrote:
> Related info in dmesg
> [0.00] Linux version 4.9.0-5-amd64 (debian-ker...@lists.debian.org)
> (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-
> 3+deb9u2 (2018-01-04)
> [  273.787162] [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO
> underrun

This is not the fixed version. You want to upgrade to 4.9.80-1 (or -2) which
is currently sitting in stable-proposed-updates and will be available in the
next point release.

Regards,
-- 
Yves-Alexis

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

Bug#885570: After upgrade I can continue to reproduce this

[Andrew Latham]

Thinkpad X1 Carbon Gen3 Intel HD Graphics 5500 Broadwell - WQHD (2560x1440)
Simple Debian Stretch install, updated, using KDE desktop

No bells or tweaks, standard install.

Reproduce
1. Open Google Chrome web browser
2. Open KDE Konsole app
3. Press enter or type a char
4. Screen scrolls horizontally wildly
5. Attempt to use CTRL ALT F2
6. Screen still scrolls horizontally wildly
7. From another system login over SSH and kill both Google Chrome and
Konsole
8. System returns to usable state.
9 Open Google Chrome and type this email
10. From remote system gather debug info and find little if any mention
that there was an issue.

Related info in dmesg
[0.00] Linux version 4.9.0-5-amd64 (debian-ker...@lists.debian.org)
(gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian
4.9.65-3+deb9u2 (2018-01-04)
[  273.787162] [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO
underrun

lspci
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev
09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev
09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI
Controller (rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI
Controller #1 (rev 03)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3)
I218-LM (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition
Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root
Port #2 (rev e3)
00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root
Port #3 (rev e3)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev
03)
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller
[AHCI Mode] (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP
Thermal Management Controller (rev 03)
04:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)


Please advise what I can do to help troubleshoot this issue.


--
- Andrew "lathama" Latham -

Bug#890111: marked as done (gcab FTBFS: Program or command 'git' not foundor not executable)

[Debian Bug Tracking System]

Your message dated Sun, 11 Feb 2018 18:05:48 +
with message-id 
and subject line Bug#890111: fixed in gcab 1.1-2
has caused the Debian Bug report #890111,
regarding gcab FTBFS: Program or command 'git' not foundor not executable
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.)


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

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

...
Appending CFLAGS from environment: '-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security'
Appending LDFLAGS from environment: '-Wl,-z,relro -Wl,-z,now'
Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2'
Build machine cpu family: x86_64
Build machine cpu: x86_64

Meson encountered an error in file meson.build, line 8, column 0:
Program or command 'git' not foundor not executable
--- End Message ---
--- Begin Message ---
Source: gcab
Source-Version: 1.1-2

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated gcab 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: Sun, 11 Feb 2018 18:49:38 +0100
Source: gcab
Binary: gcab libgcab-1.0-0 libgcab-dev libgcab-doc gir1.2-gcab-1.0
Architecture: source
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 gcab   - Microsoft Cabinet file manipulation tool
 gir1.2-gcab-1.0 - Microsoft Cabinet file manipulation library - gir bindings
 libgcab-1.0-0 - Microsoft Cabinet file manipulation library
 libgcab-dev - Microsoft Cabinet file manipulation library - development files
 libgcab-doc - Microsoft Cabinet file manipulation library - documentation
Closes: 890111
Changes:
 gcab (1.1-2) unstable; urgency=medium
 .
   * Patch the build to avoid requiring git. Closes: #890111.
Checksums-Sha1:
 c7d74b94a0ee89d5dd77488bc77eb8a9e9023946 2134 gcab_1.1-2.dsc
 91d29854662f969e22d150344f03e5e90a9ba33f 5232 gcab_1.1-2.debian.tar.xz
 3eba132be4ece7337e88713ef90a7d4cb98bb358 9214 gcab_1.1-2_source.buildinfo
Checksums-Sha256:
 ee052fafe589ac118a8a60bd06b684aadde5773190e4d505b87671c4d118c12e 2134 
gcab_1.1-2.dsc
 0d6c9aab57f0a1806b290d3f2c70abf45d2d6329667c658be83309b7847680eb 5232 
gcab_1.1-2.debian.tar.xz
 5e245a194daf34c66b89ab952c2e087553076650b1d24e95c6011506972dc98e 9214 
gcab_1.1-2_source.buildinfo
Files:
 eab6b90b250d719a6959ad73a48167cb 2134 utils optional gcab_1.1-2.dsc
 8f837c00b9f29e53ec23f81b3b1dd39b 5232 utils optional gcab_1.1-2.debian.tar.xz
 358f086f88edbeddda78ff71bcbe6d8c 9214 utils optional 
gcab_1.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAlqAglwACgkQgNMC9Yht
g5zYfxAAnTy31W9RnKwZnz9jnONI52J+7IoyRNa1uYGk5FPNRG2cIVyzNVuvDubu
3e1ZuNA6DkSwoewz5vGh3Cyw69OsPazdKN/Ik8d+SELfFlW7X4XaRSLJ3N4e3Jb2
oipFiQecWN3bBT3lYHt2Xmm/7LkB1Pig6Ug8wGLnqZDXgjr8u1giu0gY89S3bQi/
G7VzkpKmiB+SMy9oG8rQ+AYNm9MaZ1EOmnP56z+hNcmol9O+E4A2HhE8UEWzBC+g
S1K0FkSJVJypWDxqfJU8cuR6YMXDMzoDu74Ef0/UDGADQ/13p2t7PU8fzUVhxKSL
JxOgV24gleGbOhHOGrt3r1IQzVIggLS0xmOO43qZqNj0LU57wJkUzjffwvtTyTfo
3Pb9fgxwSKkmmgdT3oVfm/YIiCNnqxSkPlyVldappmgPzvJJxlLseux2mskj5PJw
kSKJ0cMaMMI2nf9RWJKW2VMwZyFDcD+YFJNOZEhYWvtAc0ltiOhqVoHVd6DQ8hK5
LrXqtdFypLHO5b9hamPiCrrcqkuDb1UCOwhXHEycuH1k0SvGN9mQ8nn1aAQSxrxH
9lGyW4avvMQ0vLKiFF8ZeG6+S5M4p+qw6R37k+UrdDQZTjQczKBDbKq5zsiVc+Gk
l/CirHtapFmEhH4wE0eqeyg7bppYF3Eys0tKoCtCVbUWblAqO6E=
=/yq0
-END PGP SIGNATURE End Message ---

Bug#888316: jackson-databind: CVE-2018-5968

[Markus Koschany]

Am 11.02.2018 um 08:42 schrieb Sébastien Delafond:
[...]
> Hi Markus,
> 
> thanks a lot for patches. I've reviewed them, and your approach is
> sound: please upload.
> 
> Cheers,
> 
> --Seb

Hi Seb,

thanks for the review. I've just uploaded both packages.

Cheers,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#888148: marked as done (ruby-certificate-authority: FTBFS on ruby2.5: CSR varies?)

[Debian Bug Tracking System]

Your message dated Sun, 11 Feb 2018 16:52:37 +
with message-id 
and subject line Bug#888148: fixed in ruby-certificate-authority 
0.2.0~434c15cd-1
has caused the Debian Bug report #888148,
regarding ruby-certificate-authority: FTBFS on ruby2.5: CSR varies?
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.)


-- 
888148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-certificate-authority
Version: 0.2.0~6dd483bf-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


Failures:

  1) CertificateAuthority::SigningRequest Generating CSRs should generate a CSR
 Failure/Error: expect(@csr.to_pem).to eq(expected)

   expected: "-BEGIN CERTIFICATE 
REQUEST-\nMIIBUTCBuwIBADAUMRIwEAYDVQQDDAlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQE...YfwPc8CxclIYt1+HyCmBndXIDvGR0JO8/lEdSObZQYHV197hWOay\nreDW940=\n-END
 CERTIFICATE REQUEST-\n"
got: "-BEGIN CERTIFICATE 
REQUEST-\nMIIBUzCBvQIBADAUMRIwEAYDVQQDDAlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQE...N1uYQ1mpmN/LtseP8PkP7S3MzJK1SSdI7929EhWfJo4Zrm0+\ngPav58ePPg==\n-END
 CERTIFICATE REQUEST-\n"

   (compared using ==)

   Diff:

   @@ -1,11 +1,11 @@
-BEGIN CERTIFICATE REQUEST-
   -MIIBUTCBuwIBADAUMRIwEAYDVQQDDAlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQEB
   +MIIBUzCBvQIBADAUMRIwEAYDVQQDDAlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQEB
BQADgY0AMIGJAoGBALGIZV9Gt/3QIea9dr5dhYTibstnWyVzpzEhjIiBm5DlPwB6
pRqRvJhjjAxRHaBnikM+z9Yazx9brqrbeqYdKvVtDodovzOdsPtQv8iKLKJbwjXW
ituuGKYjHUDrTqqLz/SBBz4fznWDNS6x3nGAo/Zf6g/FjHdUbd2mSwuc0rUjAgMB
   -AAEwDQYJKoZIhvcNAQENBQADgYEAZWLXHmJJyHz+9AdWUJ3U3pLHR/ghA1f3Ihyu
   -2PuYvwqfnGfGTA8DUnQx7l7J6ATIn76SBadmOquBBbbuhJG05WfKZt0oqCAPdsIa
   -XBlLOqVQmWR7YfwPc8CxclIYt1+HyCmBndXIDvGR0JO8/lEdSObZQYHV197hWOay
   -reDW940=
   +AAGgADANBgkqhkiG9w0BAQ0FAAOBgQANCCSnS9L5tUZrtysGF+uP+eSc6O76jRbL
   +9XueRH57ZIddHm/z3xK/01IjyKVlLK7azlL187K1JZwBCwREhodBRULoQJGumhRT
   +qh9RuoJtuzEmviAYN1uYQ1mpmN/LtseP8PkP7S3MzJK1SSdI7929EhWfJo4Zrm0+
   +gPav58ePPg==
-END CERTIFICATE REQUEST-
 # ./spec/units/signing_request_spec.rb:137:in `block (3 levels) in '

Finished in 2.15 seconds (files took 0.57521 seconds to load)
196 examples, 1 failure, 3 pending

Failed examples:

rspec ./spec/units/signing_request_spec.rb:124 # 
CertificateAuthority::SigningRequest Generating CSRs should generate a CSR

[Coveralls] Outside the CI environment, not sending data.
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-certificate-authority-0.2.0\~6dd483bf/debian/ruby-certificate-authority
 returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-certificate-authority.log

Please fix it!

Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: ruby-certificate-authority
Source-Version: 0.2.0~434c15cd-1

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

Debian distribution maintenance software
pp.
Sebastien Badia  (supplier of updated 
ruby-certificate-authority 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: Sun, 11 Feb 2018 16:48:34 +0100
Source: ruby-certificate-authority
Binary: ruby-certificate-authority
Architecture: source
Version: 0.2.0~434c15cd-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras 

Bug#889017: Bug#888953: gobby accesses the network during the build

[Adrian Bunk]

Control: severity -1 normal

On Thu, Feb 01, 2018 at 10:38:08AM +, Simon McVittie wrote:
> On Thu, 01 Feb 2018 at 11:23:28 +0200, Adrian Bunk wrote:
> > On Wed, Jan 31, 2018 at 03:53:11PM +0100, Matthias Klose wrote:
> > > While seen on a launchpad build, it looks like a missing build dependency,
> > > because it tries to access the docbookx.dtd from the network:
> 
> My understanding is that it's currently up to the package being built
> (e.g. gobby, not gnome-doc-utils) to build-depend on the appropriate
> package to get the DTDs of its XML documentation to be registered
> in the xml-core catalog and available without hitting the network:
> docbook-xml for docbookx.dtd, rarian-compat for scrollkeeper-omf.dtd,
> and possibly others.
>...

For the same issue in yelp-tools (#839549),
is this also a missing build dependency in aisleriot?

> > There is also the related issue that 
> > /usr/share/gnome-doc-utils/gnome-doc-utils.make
> > shouldn't call xmllint without --nonet
> 
> I'm not sure that this would be a good idea to do
> unconditionally. gnome-doc-utils.make gets copied into source packages
> by gnome-doc-prepare (analogous to autoconf, automake, libtoolize) so
> by making this change, we would be imposing Debian policy on upstream
> packages that happen to have been prepared by a `make dist` on a Debian
> system.
> 
> In Debian, accessing the network during build is forbidden (for good
> reason), and we have the xml-core catalog as a way to get DTDs without
> doing so. However, when packages whose upstream release happens to have
> been made on a Debian system are built on less enlightened distributions
> that don't have (or want) that policy, and that don't necessarily even
> have an equivalent of xml-core, they still need to build successfully.
> 
> Is there a canonical way to detect that we are in a Debian package build,
> that could be used to add --nonet to the xmllint command-line if and only
> if this is a Debian package build?

The yelp-tools fix of adding it only to "make check" might also apply here?
https://git.gnome.org/browse/yelp-tools/commit/?id=71e8c4bd285a576ad3b3c38eb6aa9a2a0a1b24de

> smcv

cu
Adrian

-- 

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

Processed: Re: Bug#888953: gobby accesses the network during the build

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #889017 [gnome-doc-utils] gnome-doc-utils.make should forbid accessing the 
network
Severity set to 'normal' from 'serious'

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

Bug#890031: marked as done (aseba: frequent parallel FTBFS)

[Debian Bug Tracking System]

Your message dated Sun, 11 Feb 2018 15:04:53 +
with message-id 
and subject line Bug#890031: fixed in aseba 1.6.0-2
has caused the Debian Bug report #890031,
regarding aseba: frequent parallel FTBFS
to be marked as done.

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

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


-- 
890031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aseba
Version: 1.6.0-1
Severity: serious
Tags: patch

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

...
[ 78%] Built target asebaqtplugins
make -f clients/studio/CMakeFiles/asebastudio.dir/build.make 
clients/studio/CMakeFiles/asebastudio.dir/depend
make -f clients/studio/CMakeFiles/thymiovpl.dir/build.make 
clients/studio/CMakeFiles/thymiovpl.dir/depend
make -f clients/studio/CMakeFiles/rendervplblocks.dir/build.make 
clients/studio/CMakeFiles/rendervplblocks.dir/depend
make[3]: Entering directory '/<>/obj-powerpc64le-linux-gnu'
make[3]: Entering directory '/<>/obj-powerpc64le-linux-gnu'
make[3]: Entering directory '/<>/obj-powerpc64le-linux-gnu'
[ 79%] Generating aseba-doc.qch
[ 79%] Generating aseba-doc.qch
[ 79%] Generating aseba-doc.qch
cd /<>/obj-powerpc64le-linux-gnu/clients/studio && 
/usr/lib/powerpc64le-linux-gnu/qt4/bin/qhelpgenerator 
/<>/clients/studio/aseba-doc.qhp -o 
/<>/obj-powerpc64le-linux-gnu/clients/studio/aseba-doc.qch
cd /<>/obj-powerpc64le-linux-gnu/clients/studio && 
/usr/lib/powerpc64le-linux-gnu/qt4/bin/qhelpgenerator 
/<>/clients/studio/aseba-doc.qhp -o 
/<>/obj-powerpc64le-linux-gnu/clients/studio/aseba-doc.qch
cd /<>/obj-powerpc64le-linux-gnu/clients/studio && 
/usr/lib/powerpc64le-linux-gnu/qt4/bin/qhelpgenerator 
/<>/clients/studio/aseba-doc.qhp -o 
/<>/obj-powerpc64le-linux-gnu/clients/studio/aseba-doc.qch
Cannot register namespace aseba.main!
Building up file structure...
clients/studio/CMakeFiles/thymiovpl.dir/build.make:193: recipe for target 
'clients/studio/aseba-doc.qch' failed
make[3]: *** [clients/studio/aseba-doc.qch] Error 255


Generating the same file 3 times in parallel is simply wrong.

Note that this does not depend on the architecture,
it is just more likely to FTBFS with higher levels
of parallelism:
"dpkg-buildpackage -J1" builds on ppc64el and
"dpkg-buildpackage -J100" FTBFS on amd64.

The proper fix would be to fix the parallel build,
but if that is not easily possible the following
change to disable parallel building would be
sufficient:

--- debian/rules.old2018-02-10 10:05:25.449354215 +
+++ debian/rules2018-02-10 10:05:36.221354113 +
@@ -15,6 +15,6 @@
 
 
 %:
-   dh $@
+   dh $@ --no-parallel
 
 
--- End Message ---
--- Begin Message ---
Source: aseba
Source-Version: 1.6.0-2

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated aseba package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Feb 2018 13:23:09 +0100
Source: aseba
Binary: aseba
Architecture: source amd64
Version: 1.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 aseba  - Event-based framework for distributed mobile robots control
Closes: 890031
Changes:
 aseba (1.6.0-2) unstable; urgency=medium
 .
   * applied Adrian Bunk's patch. Closes: #890031
Checksums-Sha1:
 a0f35dd83893cc9b0ee9ffb0ec74e6b6442a34e4 2048 aseba_1.6.0-2.dsc
 adc2a0448a7dbd534060b5f58c8b8c4b6f311757 7568 aseba_1.6.0-2.debian.tar.xz
 90f5878c8a69d7a8edd9b05691cdb22c88a2e951 32603644 
aseba-dbgsym_1.6.0-2_amd64.deb
 ee2706b09d2665734f899c57adc20d62042e08a9 13786 aseba_1.6.0-2_amd64.buildinfo
 63123f3a7b624dc0f51397ae7883076b0bb369a5 8424760 aseba_1.6.0-2_amd64.deb
Checksums-Sha256:
 ab40c5e7ae05ed29416415319db9386047f705985ddc4a9768608526b728c33d 2048 
aseba_1.6.0-2.dsc
 e62d268ef18a53f74e7dff1bda44ae7037f2c09282fa852ffacd8eee4c56cf39 7568 

Bug#890141: node-dashdash FTBFS with Node.js 8.9.3: test failure

[Adrian Bunk]

Source: node-dashdash
Version: 1.14.1-1
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-dashdash-1.14.1'
nodeunit test/*.test.js

basics.test.js
✔ exports
✔ createParser
✔ Parser
✔ parse
✔ old Parser.parse() API
✔ slice
✔ synopsisFromOpt
✔ case 0: node tool.js
✔ case 1: node tool.js a b c
✔ case 2: node tool.js a b
✔ case 3: node tool.js -- a
✔ case 4: node tool.js a -- b
✔ case 5: node tool.js a -- --help
✔ case 6: node tool.js --help
✔ case 7: node tool.js --help a b
✔ case 8: node tool.js a --help b
✔ case 9: node tool.js a --help b
✔ case 10: node tool.js a --help b
✔ case 11: node tool.js --help=foo
✔ case 12: node tool.js --file
✔ case 13: node tool.js
✔ case 14: node tool.js --file foo.txt
✔ case 15: node tool.js --file=foo.txt
✔ case 16: node tool.js -
✔ case 17: node tool.js -h
✔ case 18: node tool.js -f
✔ case 19: node tool.js -f foo.txt
✔ case 20: node tool.js -ffoo.txt
✔ case 21: node ls.js -l -a dir
✔ case 22: node ls.js -l dir -a
✔ case 23: node ls.js -l dir -a
✔ case 24: node ls.js -la dir
✔ case 25: node tool.js -af
✔ case 26: node tool.js -af foo.txt
✔ case 27: node tool.js -affoo.txt
✔ case 28: node tool.js -v -vvf
✔ case 29: node tool.js -v -vvf foo.txt
✔ case 30: node tool.js -v -vvffoo.txt
✔ case 31: node tool.js -a 5 -b4 -c -1 -d -3.14159 -e 1.0e42 foo
✔ case 32: node tool.js -t 5a
✔ case 33: node tool.js -vvv foo bar
✔ case 34: node tool.js foo bar
✔ case 35: node tool.js -w club --weapon mallet -w sword bang
✔ case 36: node tool.js --split 10 -s 5 -s 0.01 bang
✔ case 37: node tool.js --help
✔ case 38: node option-groups-tool.js --help
✔ case 39: node tool.js -t 0
✔ case 40: node tool.js -t 42
✔ case 41: node tool.js -t42
✔ case 42: node tool.js -t -5
✔ case 43: node tool.js -t-5
✔ case 44: node tool.js -t 1e2
✔ case 45: node tool.js -t 0x32
✔ case 46: node tool.js -t 3.1
✔ case 47: node tool.js -t 42.
✔ case 48: node tool.js -t 1e-2
✔ case 49: node tool.js
✔ case 50: node tool.js -t 42
✔ case 51: node tool.js -t 1 -t 2 -t -3
✔ case 52: node tool.js -t 1 -t 1e2
✔ case 53: node tool.js -t 0
✔ case 54: node tool.js -t 42
✔ case 55: node tool.js -t42
✔ case 56: node tool.js -t -5
✔ case 57: node tool.js -t42
✔ case 58: node tool.js -t 42 -t -5
✔ case 59: node foo.js -v
✔ case 60: FOO_VERBOSE=1 node foo.js -v
✔ case 61: FOO_VERBOSE=1 node foo.js
✔ case 62: FOO_VERBOSE=0 node foo.js
✔ case 63: FOO_VERBOSE= node foo.js
✔ case 64: node tool.js --help
✔ case 65: node foo.js -t 42
✔ case 66: FOO_TIMEOUT=32 node foo.js
✔ case 67: FOO_TIMEOUT=32 node foo.js -t 52
✔ case 68: FOO_TIMEOUT=wallawalla node foo.js -t 52
✔ case 69: FOO_TIMEOUT=wallawalla node foo.js
✔ case 70: FOO_VERBOSE=blah node foo.js
✔ case 71: FOO_VERBOSE=blah node foo.js -v
✔ case 72: FOO_VERBOSE=blah node foo.js -vv
✔ case 73: node foo.js --dry-run
✔ case 74: node foo.js --foo-bar-
✔ case 75: node foo.js
✔ case 76: FOO_FILE=env.file node foo.js
✔ case 77: FOO_FILE=env.file node foo.js -f argv.file
✔ case 78: node foo.js
✔ case 79: FOO_VERBOSE=1 node foo.js
✔ case 80: FOO_VERBOSE=0 node foo.js
✔ case 81: FOO_VERBOSE=0 node foo.js -v
✔ case 82: node tool.js a --help -b --cheese
✔ case 83: node tool.js a -bcd --cheese --help
✔ case 84: node foo.js -s
✔ case 85: node foo.js -s notadate
✔ case 86: node foo.js -s 0
✔ case 87: node foo.js -s 1
✔ case 88: node foo.js -s 1396065084
✔ case 89: node foo.js -s 2014-04-01
✔ case 90: node foo.js -s 2014-04-01T
✖ case 91: node foo.js -s 2014-04-01T12:01:02

AssertionError: { start: 2014-04-02T00:01:02.000Z, _args: [] } deepEqual { 
start: 2014-04-01T12:01:02.000Z, _args: [] }
at Object.deepEqual (/usr/lib/nodejs/nodeunit/lib/types.js:83:39)
at Object. 
(/build/1st/node-dashdash-1.14.1/test/basics.test.js:1177:15)
at Object._ (/build/1st/node-dashdash-1.14.1/test/tap4nodeunit.js:56:32)
at /usr/lib/nodejs/nodeunit/lib/core.js:232:20
at /usr/lib/nodejs/nodeunit/deps/async.js:168:13
at /usr/lib/nodejs/nodeunit/deps/async.js:131:25
at /usr/lib/nodejs/nodeunit/deps/async.js:165:17
at /usr/lib/nodejs/nodeunit/deps/async.js:463:34
at Object. 
(/build/1st/node-dashdash-1.14.1/test/basics.test.js:72:5)
at Object._setup 
(/build/1st/node-dashdash-1.14.1/test/tap4nodeunit.js:35:39)

✔ case 92: node foo.js -s 2014-04-01T12:01:02Z
✖ case 93: node foo.js -s 2014-04-01T12:01:02.7

AssertionError: { start: 2014-04-02T00:01:02.700Z, _args: [] } deepEqual { 
start: 2014-04-01T12:01:02.700Z, _args: [] }
at Object.deepEqual (/usr/lib/nodejs/nodeunit/lib/types.js:83:39)
at Object. 
(/build/1st/node-dashdash-1.14.1/test/basics.test.js:1177:15)
at Object._ (/build/1st/node-dashdash-1.14.1/test/tap4nodeunit.js:56:32)
at /usr/lib/nodejs/nodeunit/lib/core.js:232:20
at /usr/lib/nodejs/nodeunit/deps/async.js:168:13
at /usr/lib/nodejs/nodeunit/deps/async.js:131:25
at 

Processed: Add another affected package

[Debian Bug Tracking System]

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

> affects 887666 src:jzmq
Bug #887666 [javahelper] jh_linkjars: Invalid option: N
Added indication that 887666 affects src:jzmq
> thanks
Stopping processing here.

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

Bug#890137: jellyfish FTBFS on arm64/ppc64el: FAIL: tests/generate_sequence

[Adrian Bunk]

Source: jellyfish
Version: 2.2.7-1
Severity: serious

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

...
FAIL: tests/generate_sequence
=

Seed: 3141592653
Creating fasta file 'seq10m.fa'
Seed: 1040104553
Creating fasta file 'seq1m_0.fa'
Creating fasta file 'seq1m_1.fa'
Creating fasta file 'seq1m_2.fa'
Creating fasta file 'seq1m_3.fa'
Creating fasta file 'seq1m_4.fa'
Seed: 1473540700
Creating fastq file 'seq10m.fq'
Usage: fastq2sam [options] fastq:string+
Use --help for more information
FAIL tests/generate_sequence.sh (exit status: 1)

SKIP: tests/big
===

Skip big test
SKIP tests/big.sh (exit status: 77)

SKIP: tests/sam
===

Skip SAM/BAM/CRAM file format test
SKIP tests/sam.sh (exit status: 77)

SKIP: tests/swig_python
===

SKIP tests/swig_python.sh (exit status: 77)

SKIP: tests/swig_ruby
=

SKIP tests/swig_ruby.sh (exit status: 77)


Testsuite summary for jellyfish 2.2.7

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

See ./test-suite.log
Please report to gmarc...@umd.edu

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


There are also FTBFS on other architectures, but the arm64/ppc64el
ones are RC since 2.2.6-6 built there.

Bug#890136: libbpp-phyl: FTBFS on mipsel: Test took too much time

[Boyuan Yang]

Source: libbpp-phyl
Version: 2.3.2-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=libbpp-phyl=mipsel=2.3.2-2=1518221367=0

[...]

10/14 Test #13: test_tree_getpath    Passed0.42 sec
  Start 14: test_tree_rootat
11/14 Test #14: test_tree_rootat .   Passed3.21 sec
12/14 Test #11: test_simulations .   Passed  1052.22 sec
13/14 Test #12: test_tree    Passed  197.04 sec
E: Build killed with signal TERM after 150 minutes of inactivity

Build finished at 2018-02-10T00:09:20Z

Please investigate into it.

--
Thanks,
Boyuan Yang

Processed: xserver-xorg-video-ast: diff for NMU version 1.1.5-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 887076 + patch
Bug #887076 [src:xserver-xorg-video-ast] xserver-xorg-video-ast: unused 
build-dependency on libxatracker-dev
Added tag(s) patch.
> tags 887076 + pending
Bug #887076 [src:xserver-xorg-video-ast] xserver-xorg-video-ast: unused 
build-dependency on libxatracker-dev
Added tag(s) pending.

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

Bug#887076: xserver-xorg-video-ast: diff for NMU version 1.1.5-1.1

[Adrian Bunk]

Control: tags 887076 + patch
Control: tags 887076 + pending

Dear maintainer,

I've prepared an NMU for xserver-xorg-video-ast (versioned as 1.1.5-1.1) 
and uploaded it to DELAYED/10. Please feel free to tell me if I should 
cancel it.

cu
Adrian

-- 

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

diff -Nru xserver-xorg-video-ast-1.1.5/debian/changelog xserver-xorg-video-ast-1.1.5/debian/changelog
--- xserver-xorg-video-ast-1.1.5/debian/changelog	2016-02-01 01:39:05.0 +0200
+++ xserver-xorg-video-ast-1.1.5/debian/changelog	2018-02-11 14:37:01.0 +0200
@@ -1,3 +1,11 @@
+xserver-xorg-video-ast (1.1.5-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove the unused build dependency on libxatracker-dev.
+(Closes: #887076)
+
+ -- Adrian Bunk   Sun, 11 Feb 2018 14:37:01 +0200
+
 xserver-xorg-video-ast (1.1.5-1) unstable; urgency=medium
 
   * Initial release (Closes: #813325)
diff -Nru xserver-xorg-video-ast-1.1.5/debian/control xserver-xorg-video-ast-1.1.5/debian/control
--- xserver-xorg-video-ast-1.1.5/debian/control	2016-02-01 01:39:29.0 +0200
+++ xserver-xorg-video-ast-1.1.5/debian/control	2018-02-11 14:36:30.0 +0200
@@ -18,7 +18,6 @@
  libdrm-dev [!hurd-i386],
  libxext-dev,
  libx11-dev,
- libxatracker-dev [linux-any],
 Standards-Version: 3.9.6
 # Vcs-Git: git://anonscm.debian.org/git/pkg-xorg/driver/xserver-xorg-video-ast
 # Vcs-Browser: http://anonscm.debian.org/cgit/pkg-xorg/driver/xserver-xorg-video-ast.git

Bug#890031: aseba: frequent parallel FTBFS

[Georges Khaznadar]

Thank you Adrian!

I shall upload a fixed revision immediately.

Best regards,   Georges.

Adrian Bunk a écrit :
> Source: aseba
> Version: 1.6.0-1
> Severity: serious
> Tags: patch
> 
> https://buildd.debian.org/status/package.php?p=aseba=sid
> 
> ...
> [ 78%] Built target asebaqtplugins
> make -f clients/studio/CMakeFiles/asebastudio.dir/build.make 
> clients/studio/CMakeFiles/asebastudio.dir/depend
> make -f clients/studio/CMakeFiles/thymiovpl.dir/build.make 
> clients/studio/CMakeFiles/thymiovpl.dir/depend
> make -f clients/studio/CMakeFiles/rendervplblocks.dir/build.make 
> clients/studio/CMakeFiles/rendervplblocks.dir/depend
> make[3]: Entering directory '/<>/obj-powerpc64le-linux-gnu'
> make[3]: Entering directory '/<>/obj-powerpc64le-linux-gnu'
> make[3]: Entering directory '/<>/obj-powerpc64le-linux-gnu'
> [ 79%] Generating aseba-doc.qch
> [ 79%] Generating aseba-doc.qch
> [ 79%] Generating aseba-doc.qch
> cd /<>/obj-powerpc64le-linux-gnu/clients/studio && 
> /usr/lib/powerpc64le-linux-gnu/qt4/bin/qhelpgenerator 
> /<>/clients/studio/aseba-doc.qhp -o 
> /<>/obj-powerpc64le-linux-gnu/clients/studio/aseba-doc.qch
> cd /<>/obj-powerpc64le-linux-gnu/clients/studio && 
> /usr/lib/powerpc64le-linux-gnu/qt4/bin/qhelpgenerator 
> /<>/clients/studio/aseba-doc.qhp -o 
> /<>/obj-powerpc64le-linux-gnu/clients/studio/aseba-doc.qch
> cd /<>/obj-powerpc64le-linux-gnu/clients/studio && 
> /usr/lib/powerpc64le-linux-gnu/qt4/bin/qhelpgenerator 
> /<>/clients/studio/aseba-doc.qhp -o 
> /<>/obj-powerpc64le-linux-gnu/clients/studio/aseba-doc.qch
> Cannot register namespace aseba.main!
> Building up file structure...
> clients/studio/CMakeFiles/thymiovpl.dir/build.make:193: recipe for target 
> 'clients/studio/aseba-doc.qch' failed
> make[3]: *** [clients/studio/aseba-doc.qch] Error 255
> 
> 
> Generating the same file 3 times in parallel is simply wrong.
> 
> Note that this does not depend on the architecture,
> it is just more likely to FTBFS with higher levels
> of parallelism:
> "dpkg-buildpackage -J1" builds on ppc64el and
> "dpkg-buildpackage -J100" FTBFS on amd64.
> 
> The proper fix would be to fix the parallel build,
> but if that is not easily possible the following
> change to disable parallel building would be
> sufficient:
> 
> --- debian/rules.old  2018-02-10 10:05:25.449354215 +
> +++ debian/rules  2018-02-10 10:05:36.221354113 +
> @@ -15,6 +15,6 @@
>  
>  
>  %:
> - dh $@
> + dh $@ --no-parallel
>  
>  

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature

Bug#890123: marked as done (biomaj3-core: missing build dependency on python3-requests)

[Debian Bug Tracking System]

Your message dated Sun, 11 Feb 2018 12:19:17 +
with message-id 
and subject line Bug#890123: fixed in biomaj3-core 3.0.11-2
has caused the Debian Bug report #890123,
regarding biomaj3-core: missing build dependency on python3-requests
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.)


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

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd 
/build/1st/biomaj3-core-3.0.11/.pybuild/pythonX.Y_3.6/build; python3.6 -m nose 
tests
E
==
ERROR: Failure: ModuleNotFoundError (No module named 'requests')
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
  File "/usr/lib/python3/dist-packages/nose/loader.py", line 417, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "/usr/lib/python3.6/imp.py", line 235, in load_module
return load_source(name, filename, file)
  File "/usr/lib/python3.6/imp.py", line 172, in load_source
module = _load(spec)
  File "", line 684, in _load
  File "", line 665, in _load_unlocked
  File "", line 678, in exec_module
  File "", line 219, in _call_with_frames_removed
  File 
"/build/1st/biomaj3-core-3.0.11/.pybuild/pythonX.Y_3.6/build/tests/biomaj_tests.py",
 line 10, in 
from biomaj_core.utils import Utils
  File 
"/build/1st/biomaj3-core-3.0.11/.pybuild/pythonX.Y_3.6/build/biomaj_core/utils.py",
 line 12, in 
import requests
ModuleNotFoundError: No module named 'requests'

--
Ran 1 test in 1.546s

FAILED (errors=1)
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/biomaj3-core-3.0.11/.pybuild/pythonX.Y_3.6/build; python3.6 -m nose 
tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.6 returned 
exit code 13
debian/rules:5: recipe for target 'build' failed
make: *** [build] Error 25
--- End Message ---
--- Begin Message ---
Source: biomaj3-core
Source-Version: 3.0.11-2

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

Debian distribution maintenance software
pp.
Olivier Sallou  (supplier of updated biomaj3-core package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Feb 2018 11:49:53 +
Source: biomaj3-core
Binary: python3-biomaj3-core
Architecture: source all
Version: 3.0.11-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Olivier Sallou 
Description:
 python3-biomaj3-core - BioMAJ core library - Python 3.X
Closes: 890123
Changes:
 biomaj3-core (3.0.11-2) unstable; urgency=medium
 .
   * Add missing build-dep  (Closes: #890123).
Checksums-Sha1:
 93db9c167c01f04f67b7391c3a9a87f421f1a73f 2114 biomaj3-core_3.0.11-2.dsc
 5f249b2d7d9829ed66ba8627b64e40fe63613ad9 12512 
biomaj3-core_3.0.11-2.debian.tar.xz
 db30bac6b5afa670b9f591011b36381bb99a1c85 5292 
biomaj3-core_3.0.11-2_amd64.buildinfo
 62d0bdc2effe2b0f7059f9337a6513fec149b037 22844 
python3-biomaj3-core_3.0.11-2_all.deb
Checksums-Sha256:
 b38e335f05da6ae947e2a5425c02819ded95040941e95f6996efa554916ce7d3 2114 
biomaj3-core_3.0.11-2.dsc
 cb84056b7e522cad0d2d0de038f6e5049790d0a07d1a74acfe3ea2633fffb7d9 12512 
biomaj3-core_3.0.11-2.debian.tar.xz
 

Bug#889544: Bug

[Ritesh Raj Sarraf]

Thanks for the reply. This was an issue that crept in in 1.72-1 and was
quickly resolved with 1.72-2.


s3nt fr0m a $martph0ne, excuse typ0s

On 11-Feb-2018 14:24, "Jean-Marie Favreau" 
wrote:

> Dear Maintainer,
>
> When the laptop-mode was activated, I was getting in `dmesg` similiar
> messages
> every few seconds :
>
> Feb 10 22:21:26 chernomorets kernel: [  488.561908] sd 0:0:0:0: [sda]
> Synchronizing SCSI cache
> Feb 10 22:21:26 chernomorets kernel: [  488.563039] sd 0:0:0:0: [sda]
> Stopping
> disk
> Feb 10 22:21:27 chernomorets kernel: [  489.918355] sd 0:0:0:0: [sda]
> Starting
> disk
>
> After a non regular time, the disk did not start again, the system was
> frozen
> (cannot use applications on kde, cannot log in a virtual console).
> The last messages in syslog are:
> Feb 10 22:22:02 chernomorets kernel: [  524.697773] sd 0:0:0:0: [sda]
> Synchronizing SCSI cache
> Feb 10 22:22:02 chernomorets kernel: [  524.698990] sd 0:0:0:0: [sda]
> Stopping
> disk
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>
> I removed/purged the package. Finally, in order to reproduce the messages,
> I
> reinstall it, and everything seems to come back to the normal. It might be
> a
> configuration problem.
>
> Sorry for these messages.
>
> Thank you,
>
> --
> Jean-Marie Favreau - http://jmfavreau.info
>

Bug#890123: biomaj3-core: missing build dependency on python3-requests

[Adrian Bunk]

Source: biomaj3-core
Version: 3.0.11-1
Severity: serious

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd 
/build/1st/biomaj3-core-3.0.11/.pybuild/pythonX.Y_3.6/build; python3.6 -m nose 
tests
E
==
ERROR: Failure: ModuleNotFoundError (No module named 'requests')
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
  File "/usr/lib/python3/dist-packages/nose/loader.py", line 417, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "/usr/lib/python3.6/imp.py", line 235, in load_module
return load_source(name, filename, file)
  File "/usr/lib/python3.6/imp.py", line 172, in load_source
module = _load(spec)
  File "", line 684, in _load
  File "", line 665, in _load_unlocked
  File "", line 678, in exec_module
  File "", line 219, in _call_with_frames_removed
  File 
"/build/1st/biomaj3-core-3.0.11/.pybuild/pythonX.Y_3.6/build/tests/biomaj_tests.py",
 line 10, in 
from biomaj_core.utils import Utils
  File 
"/build/1st/biomaj3-core-3.0.11/.pybuild/pythonX.Y_3.6/build/biomaj_core/utils.py",
 line 12, in 
import requests
ModuleNotFoundError: No module named 'requests'

--
Ran 1 test in 1.546s

FAILED (errors=1)
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/biomaj3-core-3.0.11/.pybuild/pythonX.Y_3.6/build; python3.6 -m nose 
tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.6 returned 
exit code 13
debian/rules:5: recipe for target 'build' failed
make: *** [build] Error 25

Bug#890122: kcompletion FTBFS on architectures where Qt uses OpenGL ES

[Adrian Bunk]

Source: kcompletion
Version: 5.42.0-2
Severity: serious
Tags: patch

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
xvfb-run -a dh_auto_test
cd obj-arm-linux-gnueabi && make -j4 test ARGS\+=-j4
make[2]: Entering directory '/<>/obj-arm-linux-gnueabi'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j4
Test project /<>/obj-arm-linux-gnueabi
Start 1: kcompletioncoretest
Start 2: klineedit_unittest
Start 3: kcombobox_unittest
Start 4: ksortablelisttest
1/4 Test #4: ksortablelisttest    Passed0.31 sec
2/4 Test #1: kcompletioncoretest ..***Exception: SegFault  0.36 sec
QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/run/user/2952', 
please create it with 0700 permissions.
libEGL warning: DRI2: failed to create any config

3/4 Test #2: klineedit_unittest ...***Exception: SegFault  0.38 sec
QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/run/user/2952', 
please create it with 0700 permissions.
libEGL warning: DRI2: failed to create any config

4/4 Test #3: kcombobox_unittest ...***Exception: SegFault  0.37 sec
QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/run/user/2952', 
please create it with 0700 permissions.
libEGL warning: DRI2: failed to create any config


25% tests passed, 3 tests failed out of 4

Total Test time (real) =   0.40 sec

The following tests FAILED:
  1 - kcompletioncoretest (SEGFAULT)
  2 - klineedit_unittest (SEGFAULT)
  3 - kcombobox_unittest (SEGFAULT)
Errors while running CTest
Makefile:122: recipe for target 'test' failed
make[2]: *** [test] Error 8


Fix (stolen from Ubuntu):

--- debian/rules.old2018-02-11 11:03:20.291380680 +
+++ debian/rules2018-02-11 11:03:36.281213576 +
@@ -15,4 +15,4 @@
dh_strip --dbgsym-migration='libkf5completion5-dbg (<= 5.19.0-1~~)'
 
 override_dh_auto_test:
-   xvfb-run -a dh_auto_test
+   xvfb-run -a --server-args="-screen 0 1024x768x24+32" dh_auto_test

Bug#887940: marked as done (libpq-dev: changed version format in pg_config causes other packages to FTBFS)

[Debian Bug Tracking System]

Your message dated Sun, 11 Feb 2018 11:04:41 +
with message-id 
and subject line Bug#887940: fixed in libpreludedb 3.1.0-2
has caused the Debian Bug report #887940,
regarding libpq-dev: changed version format in pg_config causes other packages 
to FTBFS
to be marked as done.

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

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


-- 
887940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpq-dev
Version: 10.1-3
Severity: serious
Control: affects -1 src:libpreludedb

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

...
checking for ... checking for pg_config... /usr/bin/pg_config
checking for PostgreSQL libraries... yes
./configure: line 19300: test: too many arguments
...
   dh_install
dh_install: Cannot find (any matches for) 
"debian/tmp/usr/lib/*/libpreludedb/plugins/sql/pgsql*" (tried in ., debian/tmp)

dh_install: libpreludedb7-pgsql missing files: 
debian/tmp/usr/lib/*/libpreludedb/plugins/sql/pgsql*
dh_install: missing files, aborting
debian/rules:27: recipe for target 'binary' failed
make: *** [binary] Error 25


Root cause:

postgresql-10 (10.1-3) unstable; urgency=medium
...
  * Include package version number in "extra version" so it is reported by
"psql --version" and friends.

https://sources.debian.org/src/autoconf-archive/20170321-1/m4/ax_lib_postgresql.m4/#L97
--- End Message ---
--- Begin Message ---
Source: libpreludedb
Source-Version: 3.1.0-2

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

Debian distribution maintenance software
pp.
Thomas Andrejak  (supplier of updated libpreludedb 
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: Sat, 10 Feb 2018 01:00:00 +0200
Source: libpreludedb
Binary: libpreludedb-dev libpreludedb-doc libpreludedb7 libpreludedbcpp2 
preludedb-utils python-preludedb python3-preludedb libpreludedb7-mysql 
libpreludedb7-pgsql libpreludedb7-sqlite
Architecture: source
Version: 3.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Pierre Chifflier 
Changed-By: Thomas Andrejak 
Description:
 libpreludedb-dev - Security Information Management System [ Development files ]
 libpreludedb-doc - Security Information Management System [ Documentation ]
 libpreludedb7 - Security Information Management System [ Base library ]
 libpreludedb7-mysql - Security Information Management System [ MySQL library ]
 libpreludedb7-pgsql - Security Information Management System [ PGSQL library ]
 libpreludedb7-sqlite - Security Information Management System [ SQLite library 
]
 libpreludedbcpp2 - Security Information Management System [ C++ library ]
 preludedb-utils - Security Information Management System [ Library utils ]
 python-preludedb - Security Information Management System [ Python2 bindings ]
 python3-preludedb - Security Information Management System [ Python3 bindings ]
Closes: 722799 887940
Changes:
 libpreludedb (3.1.0-2) unstable; urgency=medium
 .
   * Bump Standard-Version to 4.1.3, no changes needed
   * Bump debhelper version to 11
   * Update compat file from 10 to 11
   * New patches:
 - 007-update_m4_postgresql.patc
   Fix compatibility with new libpq (Closes: #887940)
 - 008-Fix_libdir_definition.patch
   Fix libdir definition (Closes: #722799)
   * Update d/control Vcs-* entries to migrate to Salsa
Checksums-Sha1:
 086e421c4610f35dac9a9f6812fb696aa982a18f 3067 libpreludedb_3.1.0-2.dsc
 0082260bb94617d0c38c7c96c0fd035f03b9b5fc 17252 
libpreludedb_3.1.0-2.debian.tar.xz
 9c91b791146934304de469816070765506870c84 13778 
libpreludedb_3.1.0-2_amd64.buildinfo
Checksums-Sha256:
 c0331c5bbef6aa75a9c4fa54daa17c83e010d0995031b3521f846560c492bfc7 3067 
libpreludedb_3.1.0-2.dsc
 b4f6e2fecdfeb67053a595584c730bf427a6ce8ac967e5bebf35cf609f8702fe 17252 
libpreludedb_3.1.0-2.debian.tar.xz
 6b2f78078f118a09aa32e3175270e139e727daaf47218622910af756a85009d1 13778 

Processed: Fix the bug title

[Debian Bug Tracking System]

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

> retitle 890107 docker-runc FTBFS on s390x: kill.go:42:20: error: reference to 
> undefined identifier 'syscall.SIGUNUSED'
Bug #890107 [src:docker-runc] docker-runc FTBFS on s390x:
Changed Bug title to 'docker-runc FTBFS on s390x: kill.go:42:20: error: 
reference to undefined identifier 'syscall.SIGUNUSED'' from 'docker-runc FTBFS 
on s390x:'.
> thanks
Stopping processing here.

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

Bug#890117: bedtools FTBFS on big endian: Tools failing: bamtobed bamtofastq coverage genomecov groupby intersect jaccard map merge multicov negativecontrol

[Adrian Bunk]

Source: bedtools
Version: 2.27.1+dfsg-1
Severity: serious

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

...
--
 Test Results 
--
Tools passing:  bed12tobed6 closest cluster complement expand fisher flank 
general getfasta makewindows reldist sample shift shuffle slop sort spacing 
split subtract
Tools failing:  bamtobed bamtofastq coverage genomecov groupby intersect 
jaccard map merge multicov negativecontrol
NB: the 'negativecontrol' test is supposed to fail. If it wasn't caught, 
something went wrong with this test script.
Makefile:196: recipe for target 'test' failed
make[1]: *** [test] Error 1

Bug#890116: bedtools FTBFS on 32bit: Tools failing: coverage intersect negativecontrol reldist shuffle split

[Adrian Bunk]

Source: bedtools
Version: 2.27.1+dfsg-1
Severity: serious

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

...
--
 Test Results 
--
Tools passing:  bamtobed bamtofastq bed12tobed6 closest cluster complement 
expand fisher flank general genomecov getfasta groupby jaccard makewindows map 
merge multicov sample shift slop sort spacing subtract
Tools failing:  coverage intersect negativecontrol reldist shuffle split
NB: the 'negativecontrol' test is supposed to fail. If it wasn't caught, 
something went wrong with this test script.
Makefile:196: recipe for target 'test' failed
make[1]: *** [test] Error 1

Bug#889702: marked as done (reptyr FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Sun, 11 Feb 2018 10:35:41 +
with message-id 
and subject line Bug#889702: fixed in reptyr 0.6.2-1.2
has caused the Debian Bug report #889702,
regarding reptyr FTBFS: test failure
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.)


-- 
889702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: reptyr
Version: 0.6.2-1.1
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
if ! [ -f /dev/tty0 ]; \
then echo disable tests; \
else dh_auto_test; \
fi
disable tests
if ! [ -f /proc/sys/kernel/yama/ptrace_scope ] || \
  [ "$(cat /proc/sys/kernel/yama/ptrace_scope)" = 0 ]; then \
  dh_auto_test; \
fi \

make -j4 test
make[2]: Entering directory '/<>'
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Werror -D_GNU_SOURCE -g -Wdate-time 
-D_FORTIFY_SOURCE=2  -c -o test/victim.o test/victim.c
cc -Wl,-z,relro -Wl,-z,now  test/victim.o   -o test/victim
python test/basic.py
Traceback (most recent call last):
  File "test/basic.py", line 10, in 
reptyr.expect("ECHO: world")
  File "/usr/lib/python2.7/dist-packages/pexpect/spawnbase.py", line 321, in 
expect
timeout, searchwindowsize, async)
  File "/usr/lib/python2.7/dist-packages/pexpect/spawnbase.py", line 345, in 
expect_list
return exp.expect_loop(timeout)
  File "/usr/lib/python2.7/dist-packages/pexpect/expect.py", line 105, in 
expect_loop
return self.eof(e)
  File "/usr/lib/python2.7/dist-packages/pexpect/expect.py", line 50, in eof
raise EOF(msg)
pexpect.exceptions.EOF: End Of File (EOF). Exception style platform.

command: ./reptyr
args: ['./reptyr', '30493']
buffer (last 100 chars): ''
before (last 100 chars): 'd stop.\r\n[-] Unable to stat /dev/console\r\nUnable 
to attach to pid 30493: No such file or directory\r\n'
after: 
match: None
match_index: None
exitstatus: 1
flag_eof: True
pid: 30494
child_fd: 6
closed: False
timeout: 30
delimiter: 
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
0: re.compile("ECHO: world")
Makefile:23: recipe for target 'test' failed
make[2]: *** [test] Error 1
--- End Message ---
--- Begin Message ---
Source: reptyr
Source-Version: 0.6.2-1.2

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

Debian distribution maintenance software
pp.
Mateusz Łukasik  (supplier of updated reptyr 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, 07 Feb 2018 12:50:10 +0100
Source: reptyr
Binary: reptyr
Architecture: source
Version: 0.6.2-1.2
Distribution: unstable
Urgency: medium
Maintainer: Evan Broder 
Changed-By: Mateusz Łukasik 
Description:
 reptyr - Tool for moving running programs between ptys
Closes: 889702
Changes:
 reptyr (0.6.2-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Disable tests for while - fix FTBFS. (Closes: #889702)
Checksums-Sha1:
 6cab15ee217e6b8dde3f91c4c0c09ef249f1486c 1868 reptyr_0.6.2-1.2.dsc
 bf004050c8d4b9a59a35bf43cac245e36513e2d4 3824 reptyr_0.6.2-1.2.debian.tar.xz
 27e1a72c74f530b176c2c9dea57523c42df6e0f0 5761 reptyr_0.6.2-1.2_source.buildinfo
Checksums-Sha256:
 1482acd4d04723ffda76fe805bfff49657942f51ce8c5c7944e86be16b75c09d 1868 
reptyr_0.6.2-1.2.dsc
 e302ef29100a46f8779bc8375f9d11e2b734f32df8bcca9aa6cee5d6a8c04b19 3824 
reptyr_0.6.2-1.2.debian.tar.xz
 e93b1b49783ce4afba6e60b74479ee0b92687184bbee87f902919012f085fd5b 5761 
reptyr_0.6.2-1.2_source.buildinfo
Files:
 0e54d240ffe6965ab17959f108fd8f08 1868 misc optional reptyr_0.6.2-1.2.dsc
 787c87d9648aefd1a8965eb0fc983b15 3824 misc optional 
reptyr_0.6.2-1.2.debian.tar.xz
 470a8d8eb519a04214cf95f61a8d5c60 5761 misc optional 

Processed: Add affects

[Debian Bug Tracking System]

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

> affects 76 src:prometheus-alertmanager
Bug #76 [src:nodejs] nodejs: s390x uses illegal instructions on Z10
Added indication that 76 affects src:prometheus-alertmanager
> thanks
Stopping processing here.

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

Bug#887688: debhelper: empty build of src:ck

[Niels Thykier]

Adrian Bunk:
>  [...]
>> Overview of the packages mentioned in this bug report
>> =
> 
> Thanks a lot for doing this.
> 

:)

>> Packages that has an open RC bug related to this issue:
>>
>>  * apr: #888593 (patch)
>>  * ck: #888591 (patch)
>>  * cpputest: #888598 (patch)

NB: cpputest is now fixed.

>>  * debian-handbook: #888578 (patch)
>>  * iaxmodem: #888601 (patch)
>>  * moarvm: #888582 (patch)
>>  * jscommunicator: #888579 (patch)
>>  * libtemplate-perl: #888663 (patch)
>>  * monotone: #888612 (patch)
>> ...
> 
> One new .PHONY case that needs a bug:
>   
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apr-util.html
> 
> [...]

Filed as #890108.  Discovered a "hidden" FTBFS beneath that bug as there
is also a test failure in apr-util's test suite.  My patch(es) does not
attempt to solve that problem; they are limited to the debhelper part of
the problem.

Thanks,
~Niels

Bug#890111: gcab FTBFS: Program or command 'git' not foundor not executable

[Adrian Bunk]

Source: gcab
Version: 1.1-1
Severity: serious

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

...
Appending CFLAGS from environment: '-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security'
Appending LDFLAGS from environment: '-Wl,-z,relro -Wl,-z,now'
Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2'
Build machine cpu family: x86_64
Build machine cpu: x86_64

Meson encountered an error in file meson.build, line 8, column 0:
Program or command 'git' not foundor not executable

Bug#890108: apr-util: FTBFS with debhelper/11.1 due to empty build target

[Niels Thykier]

Source: apr-util
Version: 1.6.1-1
Severity: serious
Tags: patch

Hi,

The apr-util package FTBFS with debhelper/11.1 as it has an empty
build target.  This is caused by debhelper had a bug in its handling
of "explicitly defined rules targets" that has now been fixed.

Previously, this happened to work because dpkg-buildpackage would
invoke "debian/rules build" (which would be a no-op) followed by
"fakeroot debian/rules binary".  During the binary target, dh's
suboptimal handling would run the build commands.


The solution is trivial but less pretty; explicitly define "build"
with the same content as the "%:" target (or rename the "build" folder
and drop the ".PHONY" target).  I have attached a patch for this.

I have also added two optional patches (0002 + 0003) to remove some
redundancy by reducing the number of options passed to dh.  When
apr-util in unstable was rebuilt, they produced bit-for-bit identical
output compared to apr-util in sid (with 0001; I could not built it
without 0001, which is why I am filing the bug).
  Both patches bumps the minimum debhelper version requriement for
building apr-util.  Most likely, it will be a non-issue for you as the
minimum requirements are satisfied in stable and oldstable-backports.


Unfortunately, even after fixing this bug, apr-util FTBFS due to a
test failure[1].  I verified that this test failure also occurs when
building with debhelper/11 and is therefore unrelated to this issue.
However, it meant that all of my builds had to be done with
DEB_BUILD_OPTIONS=nocheck.  I also noted a warning that is probably
unrelated to this test failure but may cause issues as well[2].


More details can be found in:
 * #886901 comment #35
 * #887688 comment #37
 * #880840

Apologies for the inconvenience.

Thanks,
~Niels

[1] testdbm : -Line 155: expected <0>, but saw <20014>
FAILED 1 of 3

[2]:
/dbd/apr_dbd_mysql.c: In function 'dbd_mysql_init':
/dbd/apr_dbd_mysql.c:1265:5: warning: implicit declaration of 
function 'my_init'; did you mean 'mysql_init'? [-Wimplicit-func]
 my_init();
 ^~~
 mysql_init
>From 5ec6f1fd0419eb65785b610bea4be166dd6c7d24 Mon Sep 17 00:00:00 2001
From: Niels Thykier 
Date: Sun, 11 Feb 2018 09:51:23 +
Subject: [PATCH 1/3] Avoid empty build target

The dh sequencer as of debhelper/11.1 is stricter with this in order
to solve #880840 (where debhelper would fail to handle such targets
correctly).

Signed-off-by: Niels Thykier 
---
 debian/rules | 5 +
 1 file changed, 5 insertions(+)

diff --git a/debian/rules b/debian/rules
index 871244c..386921a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -22,6 +22,11 @@ DB_VERSION = $(shell dpkg-query -W -f '$${Version}' 
libdb-dev | \
 # The 'build' target needs special handling because there there is a directory
 # named 'build'.
 .PHONY: build
+# The build target must not be empty.  Sadly because of how make
+# works, we have do duplicate the target in this case.
+build:
+   dh $@ -B$(BUILDDIR) --parallel --with autotools_dev
+
 %:
dh $@ -B$(BUILDDIR) --parallel --with autotools_dev
 
-- 
2.15.1

>From 127bf9c0d541a535b24198f07b4157f4a49c4aa3 Mon Sep 17 00:00:00 2001
From: Niels Thykier 
Date: Sun, 11 Feb 2018 10:00:46 +
Subject: [PATCH 2/3] Drop deprecated autotools-dev sequence

Signed-off-by: Niels Thykier 
---
 debian/control | 2 +-
 debian/rules   | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/debian/control b/debian/control
index ce88602..523f365 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: libs
 Priority: optional
 Maintainer: Debian Apache Maintainers 
 Uploaders: Stefan Fritsch 
-Build-Depends: debhelper (>> 9~), autoconf, autotools-dev, mawk, libldap2-dev, 
libexpat1-dev, libdb-dev, libgdbm-dev, libpcre3-dev, libapr1-dev (>> 1.4.8-2~), 
libsqlite3-dev, libpq-dev, python:any, default-libmysqlclient-dev, 
unixodbc-dev, doxygen, libssl-dev
+Build-Depends: debhelper (>> 9~), autoconf, mawk, libldap2-dev, libexpat1-dev, 
libdb-dev, libgdbm-dev, libpcre3-dev, libapr1-dev (>> 1.4.8-2~), 
libsqlite3-dev, libpq-dev, python:any, default-libmysqlclient-dev, 
unixodbc-dev, doxygen, libssl-dev
 Standards-Version: 4.0.1
 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-apache/apr-util.git
 Vcs-Git: git://anonscm.debian.org/pkg-apache/apr-util.git
diff --git a/debian/rules b/debian/rules
index 386921a..59690ae 100755
--- a/debian/rules
+++ b/debian/rules
@@ -25,10 +25,10 @@ DB_VERSION = $(shell dpkg-query -W -f '$${Version}' 
libdb-dev | \
 # The build target must not be empty.  Sadly because of how make
 # works, we have do duplicate the target in this case.
 build:
-   dh $@ -B$(BUILDDIR) --parallel --with autotools_dev
+   dh $@ -B$(BUILDDIR) --parallel
 
 %:
-   dh $@ -B$(BUILDDIR) --parallel --with autotools_dev
+   dh $@ -B$(BUILDDIR) --parallel
 
 #
 # configure

Bug#890109: octave-ltfat binary-all FTBFS: gzip: usr/share/octave/packages/ltfat-2.2.0/ChangeLog: No such file or directory

[Adrian Bunk]

Source: octave-ltfat
Version: 2.2.0+dfsg-6
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=octave-ltfat=all=2.2.0%2Bdfsg-6=1518327616=0

...
   dh_octave_changelogs -i -O--buildsystem=octave
gzip: 
debian/octave-ltfat-common/usr/share/octave/packages/ltfat-2.2.0/ltfat/inst/ChangeLog
debian/octave-ltfat-common/usr/share/octave/packages/ltfat-2.2.0/ChangeLog: No 
such file or directory
dh_octave_changelogs: gzip 
"debian/octave-ltfat-common/usr/share/octave/packages/ltfat-2.2.0/ltfat/inst/ChangeLog\
debian/octave-ltfat-common/usr/share/octave/packages/ltfat-2.2.0/ChangeLog" 
returned exit code 1
debian/rules:5: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1

Bug#890110: castle-game-engine binary-all FTBFS: install: cannot stat 'tools/texture-font-to-pascal/texture-font-to-pascal': No such file or directory

[Adrian Bunk]

Source: castle-game-engine
Version: 6.4+dfsg1-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=castle-game-engine=all=6.4%2Bdfsg1-1=1518301579=0

...
   debian/rules override_dh_auto_install-indep
make[1]: Entering directory '/<>/castle-game-engine-6.4+dfsg1'
dh_auto_install
make -j4 install 
DESTDIR=/<>/castle-game-engine-6.4\+dfsg1/debian/tmp 
AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true"
make[2]: Entering directory '/<>/castle-game-engine-6.4+dfsg1'
install -d /<>/castle-game-engine-6.4+dfsg1/debian/tmp/usr/local/bin
install tools/texture-font-to-pascal/texture-font-to-pascal 
/<>/castle-game-engine-6.4+dfsg1/debian/tmp/usr/local/bin
install: cannot stat 'tools/texture-font-to-pascal/texture-font-to-pascal': No 
such file or directory
Makefile:94: recipe for target 'install' failed
make[2]: *** [install] Error 1

Bug#890106: colmap: baseline violation on amd64/i386 and FTBFS everywhere else

[Adrian Bunk]

Source: colmap
Version: 3.4-1
Severity: serious

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

cmake/CheckSSEExtensions.cmake:
AVX is not part of the amd64 port baseline.
SSE is not part of the i386 port baseline.

src/ext/PBA/CMakeLists.txt:
"-march=core2 -mfpmath=sse" violates the
amd64+i386 port baselines and causes FTBFS
everywhere else.

Bug#890107: docker-runc FTBFS on s390x:

[Adrian Bunk]

Source: docker-runc
Version: 1.0.0~rc2+git+docker1.13.1~ds1-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=docker-runc=s390x=1.0.0~rc2%2Bgit%2Bdocker1.13.1~ds1-3=1518260100=0

...
github.com/urfave/cli
github.com/opencontainers/runc
# github.com/opencontainers/runc
src/github.com/opencontainers/runc/kill.go:42:20: error: reference to undefined 
identifier 'syscall.SIGUNUSED'
  "UNUSED": syscall.SIGUNUSED,
^
github.com/opencontainers/runc/libcontainer/devices
github.com/opencontainers/runc/libcontainer/xattr
github.com/opencontainers/runc/vendor/github.com/docker/docker/pkg/term/winconsole
dh_auto_build: cd _build && go install 
-gcflags=\"-trimpath=/<>/docker-runc-1.0.0\~rc2\+git\+docker1.13.1\~ds1/_build/src\"
 
-asmflags=\"-trimpath=/<>/docker-runc-1.0.0\~rc2\+git\+docker1.13.1\~ds1/_build/src\"
 -v -p 1 -tags "apparmor seccomp" github.com/opencontainers/runc 
github.com/opencontainers/runc/libcontainer 
github.com/opencontainers/runc/libcontainer/apparmor 
github.com/opencontainers/runc/libcontainer/cgroups 
github.com/opencontainers/runc/libcontainer/cgroups/fs 
github.com/opencontainers/runc/libcontainer/cgroups/systemd 
github.com/opencontainers/runc/libcontainer/configs 
github.com/opencontainers/runc/libcontainer/configs/validate 
github.com/opencontainers/runc/libcontainer/criurpc 
github.com/opencontainers/runc/libcontainer/devices 
github.com/opencontainers/runc/libcontainer/keys 
github.com/opencontainers/runc/libcontainer/label 
github.com/opencontainers/runc/libcontainer/nsenter 
github.com/opencontainers/runc/libcontainer/seccomp github.com/openconta
 iners/runc/libcontainer/selinux 
github.com/opencontainers/runc/libcontainer/specconv 
github.com/opencontainers/runc/libcontainer/stacktrace 
github.com/opencontainers/runc/libcontainer/system 
github.com/opencontainers/runc/libcontainer/user 
github.com/opencontainers/runc/libcontainer/utils 
github.com/opencontainers/runc/libcontainer/xattr 
github.com/opencontainers/runc/vendor/github.com/docker/docker/pkg/mount 
github.com/opencontainers/runc/vendor/github.com/docker/docker/pkg/symlink 
github.com/opencontainers/runc/vendor/github.com/docker/docker/pkg/term 
github.com/opencontainers/runc/vendor/github.com/docker/docker/pkg/term/winconsole
 
github.com/opencontainers/runc/vendor/github.com/opencontainers/runtime-spec/specs-go
 returned exit code 2
debian/rules:34: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2


I've also reproduced this with 1.0.0~rc2+git+docker1.13.1~ds1-2.

Bug#889702: NMU debdiff

[Adam Borowski]

Hi!
Here's the debdiff for Mateusz's NMU I'm about to upload.

As it's a RC fixup to a prior NMU, I'm uploading directly, without the usual
waiting period.

On the other hand, I believe the real bug is in yama not reptyr...


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ The bill with 3 years prison for mentioning Polish concentration
⣾⠁⢰⠒⠀⣿⡁ camps is back.  What about KL Warschau (operating until 1956)?
⢿⡄⠘⠷⠚⠋⠀ Zgoda?  Łambinowice?  Most ex-German KLs?  If those were "soviet
⠈⠳⣄ puppets", Bereza Kartuska?  Sikorski's camps in UK (thanks Brits!)?
diff -Nru reptyr-0.6.2/debian/changelog reptyr-0.6.2/debian/changelog
--- reptyr-0.6.2/debian/changelog   2018-01-27 18:37:40.0 +0100
+++ reptyr-0.6.2/debian/changelog   2018-02-07 12:50:10.0 +0100
@@ -1,3 +1,10 @@
+reptyr (0.6.2-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable tests for while - fix FTBFS. (Closes: #889702)
+
+ -- Mateusz Łukasik   Wed, 07 Feb 2018 12:50:10 +0100
+
 reptyr (0.6.2-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru reptyr-0.6.2/debian/rules reptyr-0.6.2/debian/rules
--- reptyr-0.6.2/debian/rules   2018-01-19 22:34:52.0 +0100
+++ reptyr-0.6.2/debian/rules   2018-02-05 19:59:03.0 +0100
@@ -14,12 +14,4 @@
 # reptyr's test suite relies on being able to ptrace non-child
 # processes, which isn't allowed under yama's defaults on Ubuntu
 override_dh_auto_test:
-   if ! [ -f /dev/tty0 ]; \
-   then echo disable tests; \
-   else dh_auto_test; \
-   fi
-
-   if ! [ -f /proc/sys/kernel/yama/ptrace_scope ] || \
- [ "$$(cat /proc/sys/kernel/yama/ptrace_scope)" = 0 ]; then \
- dh_auto_test; \
-   fi \
+   #disable

Processed: Also requires fixing in buster

[Debian Bug Tracking System]

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

> tags 890096 buster
Bug #890096 [bio-tradis] bio-tradis uninstallable: r-bioc-edger removed from 
unstable
Added tag(s) buster.
> thanks
Stopping processing here.

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

Bug#889629: marked as done (pd-iemutils binary-all FTBFS: debian/*//usr/lib/pd/extra': No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 11 Feb 2018 10:57:01 +0100
with message-id <89dd2812-3fe3-a5f2-3ecf-e8f08dae9...@debian.org>
and subject line Re: pd-iemutils binary-all FTBFS: debian/*//usr/lib/pd/extra': 
No such file or directory
has caused the Debian Bug report #889629,
regarding pd-iemutils binary-all FTBFS: debian/*//usr/lib/pd/extra': No such 
file or directory
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.)


-- 
889629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-iemutils
Version: 0.0.20161027-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=pd-iemutils=all=0.0.20161027-2=1517780292=0

...
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
find /<>/debian/*//usr/lib/pd/extra -name "*.pd_linux" -exec \
chmod 0664 {} +
find: '/<>/debian/*//usr/lib/pd/extra': No such file or directory
debian/rules:34: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
--- End Message ---
--- Begin Message ---
On Mon, 05 Feb 2018 09:19:58 +0200 Adrian Bunk  wrote:
> Source: pd-iemutils
> Version: 0.0.20161027-2
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=pd-iemutils=all=0.0.20161027-2=1517780292=0
> 
> ...
>debian/rules override_dh_install
> make[1]: Entering directory '/<>'
> dh_install
> find /<>/debian/*//usr/lib/pd/extra -name "*.pd_linux" -exec \
>   chmod 0664 {} +
> find: '/<>/debian/*//usr/lib/pd/extra': No such file or directory
> debian/rules:34: recipe for target 'override_dh_install' failed
> make[1]: *** [override_dh_install] Error 1
> 
> 


this was fixed in the 0.0.20161027-3 upload which was rejected (because
the arch:all package were dropped from the archives because of this bug).
the next (and accepted) upload (a few days later) was 0.0.20180206-1
which included the bugfix but did not automatically close it any more.

fgasnmrd
IOhannes



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

Bug#890102: openshot: Openshot 2.4.1-2 will not start

[Svein Engelsgjerd]

Package: openshot
Version: 2.4.1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
I ran an upgrade

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

   * What was the outcome of this action?
When I start openshot the GUI constantly flickers between the main window and 
the "welcome window" / tutorial dialog.
It is not possible to click the next button so the welcome window prevents the 
application from being useful.
(the desktop environment is XFCE)

   * What outcome did you expect instead?
I expect that the GUI does not flicker and does not constantly change focus 
between the two windows.

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


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

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

Versions of packages openshot depends on:
ii  openshot-qt  2.4.1-2

openshot recommends no packages.

openshot suggests no packages.

-- no debconf information

Bug#890098: FTBFS: imagemagick in Build-Depends-Indep but needed for arch build

[Rafael Laboissière]

* Steve Langasek  [2018-02-10 23:50]:


Package: octave-interval
Version: 3.1.0-4
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear maintainer,

The latest upload of octave-interval fails to build on all architectures 
currently on the autobuilders because, with the move to dh-octave, 
imagemagick is now needed as part of the arch build, not just the 
arch-independent build:


[snip]


Thanks for the bug report.  Indeed, I screwed things up in commit 
e22b79d.  I will look at this soon.


Rafael Laboissière

Bug#855494: Broken with different error - I'm going to ask for removal of the package soon

[Andreas Tille]

Hi,

I just get:


$ runPmv 
Run PMV from  /usr/lib/python2.7/dist-packages/Pmv
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/Pmv/__init__.py", line 381, in runPmv
title=title, withShell= not interactive, verbose=False, gui=gui)
  File "/usr/lib/python2.7/dist-packages/Pmv/moleculeViewer.py", line 1026, in 
__init__
trapExceptions=trapExceptions)
  File "/usr/lib/python2.7/dist-packages/ViewerFramework/VF.py", line 384, in 
__init__
self.GUI = ViewerFrameworkGUI(self, title=title,
NameError: global name 'ViewerFrameworkGUI' is not defined

Please include this Traceback in your bug report.

hit enter to continue



There is some splash screen that vanishes after hitting enter in the
terminal.

Please fix the package soon or I'll ask for removal from Debian.

Thank you

   Andreas.

-- 
http://fam-tille.de

Bug#889544: Bug

[Jean-Marie Favreau]

Dear Maintainer,

When the laptop-mode was activated, I was getting in `dmesg` similiar messages 
every few seconds :

Feb 10 22:21:26 chernomorets kernel: [  488.561908] sd 0:0:0:0: [sda] 
Synchronizing SCSI cache 
Feb 10 22:21:26 chernomorets kernel: [  488.563039] sd 0:0:0:0: [sda] Stopping 
disk 
Feb 10 22:21:27 chernomorets kernel: [  489.918355] sd 0:0:0:0: [sda] Starting 
disk 

After a non regular time, the disk did not start again, the system was frozen 
(cannot use applications on kde, cannot log in a virtual console).
The last messages in syslog are:
Feb 10 22:22:02 chernomorets kernel: [  524.697773] sd 0:0:0:0: [sda] 
Synchronizing SCSI cache 
Feb 10 22:22:02 chernomorets kernel: [  524.698990] sd 0:0:0:0: [sda] Stopping 
disk 
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

I removed/purged the package. Finally, in order to reproduce the messages, I 
reinstall it, and everything seems to come back to the normal. It might be a 
configuration problem.

Sorry for these messages.

Thank you,

-- 
Jean-Marie Favreau - http://jmfavreau.info