Bug#826727: Workaround

[Douglas Perkins]

As a workaround, for Sid there is an alpha build of a qt5 branch that's 
working for me (and others).


Alpha:
https://anki.tenderapp.com/discussions/beta-testing/231-anki-210-alpha-9

General information:
https://anki.tenderapp.com/discussions/beta-testing

Bug#849132: google-perftools FTBFS on i386: FAIL: profiler_unittest.sh

[Niels Thykier]

On Thu, 22 Dec 2016 22:46:06 +0200 Adrian Bunk  wrote:
> Source: google-perftools
> Version: 2.5-2
> Severity: serious
> 
> https://buildd.debian.org/status/logs.php?pkg=google-perftools=i386
> 
> ...
> PASS: profile_handler_unittest
> rm -f profiler_unittest.sh
> cp -p ./src/tests/profiler_unittest.sh profiler_unittest.sh
> FAIL: profiler_unittest.sh
> PASS: tcmalloc_and_profiler_unittest
> 
> Testsuite summary for gperftools 2.5
> 
> # TOTAL: 47
> # PASS:  46
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See ./test-suite.log
> Please report to gperfto...@googlegroups.com
> 
> Makefile:5903: recipe for target 'test-suite.log' failed
> make[3]: *** [test-suite.log] Error 1
> 
> 

Hi,

Are there any news on the FTBFS bug? It has been stalling the fix for
#838562 for about 40 days.

~Niels

Bug#852883: systemd: FTBFS: Test failures

[Lucas Nussbaum]

On 28/01/17 at 10:40 +0100, Michael Biebl wrote:
> The package built fine on the buildds just a couple of days ago. Do you have 
> an idea how the aws build environment differs? 

No, sorry

Lucas

Bug#853036: marked as done (node-liftoff: Non-determistically FTBFS due to unreliable timing in tests)

[Debian Bug Tracking System]

Your message dated Sun, 29 Jan 2017 07:04:56 +
with message-id 
<1485673496.438276.863023496.78483...@webmail.messagingengine.com>
and subject line (Closing duplicate)
has caused the Debian Bug report #853036,
regarding node-liftoff: Non-determistically FTBFS due to unreliable timing in 
tests
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.)


-- 
853036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-liftoff
Version: 2.3.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

node-liftoff's testsuite appears to use method timing/benchmarking
in such a way that it will non-deterministically FTBFS:

  […]

  
    1) Liftoff launch should skip respawning if process.argv has no values 
from v8flags in it:
   Error: timeout of 5000ms exceeded
at null. (/usr/lib/nodejs/mocha/lib/runnable.js:139:19)
at Timer.listOnTimeout (timers.js:92:15)
  
  
  
  debian/rules:13: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:8: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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


Regards,

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

Processed: add fixed version, to allow migration to testing

[Debian Bug Tracking System]

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

> fixed 852808 0.6.3.0+debian1
Bug #852808 {Done: Pirate Praveen } [diaspora-common] 
diaspora-common: fails to upgrade from stretch: chown: cannot access 
'/var/lib/diaspora': No such file or directory
Marked as fixed in versions diaspora-installer/0.6.3.0+debian1.
>
End of message, stopping processing here.

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

Bug#853035: node-liftoff: Non-determistically FTBFS due to unreliable timing in tests

[Chris Lamb]

Source: node-liftoff
Version: 2.3.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

node-liftoff's testsuite appears to use method timing/benchmarking
in such a way that it will non-deterministically FTBFS:

  […]

  
    1) Liftoff launch should skip respawning if process.argv has no values 
from v8flags in it:
   Error: timeout of 5000ms exceeded
at null. (/usr/lib/nodejs/mocha/lib/runnable.js:139:19)
at Timer.listOnTimeout (timers.js:92:15)
  
  
  
  debian/rules:13: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:8: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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


node-liftoff.2.3.0-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#853036: node-liftoff: Non-determistically FTBFS due to unreliable timing in tests

[Chris Lamb]

Source: node-liftoff
Version: 2.3.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

node-liftoff's testsuite appears to use method timing/benchmarking
in such a way that it will non-deterministically FTBFS:

  […]

  
    1) Liftoff launch should skip respawning if process.argv has no values 
from v8flags in it:
   Error: timeout of 5000ms exceeded
at null. (/usr/lib/nodejs/mocha/lib/runnable.js:139:19)
at Timer.listOnTimeout (timers.js:92:15)
  
  
  
  debian/rules:13: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:8: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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

Bug#853032: ruby-hamster: Non-determistically FTBFS due to unreliable timing in tests

[Chris Lamb]

Source: ruby-hamster
Version: 3.0.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

ruby-hamster's testsuite appears to use method timing/benchmarking in
such a way that it will non-deterministically FTBFS:

  […]
  
  Failures:
  
1) Hamster::List doesn't give horrendously bad performance if thread 
realizing the list sleeps
   Failure/Error: elapsed.should_not > 0
  
 expected not: > 0.3
  got:   0.315172362
   # ./spec/lib/hamster/list/multithreading_spec.rb:46:in `block (2 levels) 
in '
  
  Finished in 12.39 seconds (files took 1.34 seconds to load)
  4595 examples, 1 failure
  
  Failed examples:
  
  rspec ./spec/lib/hamster/list/multithreading_spec.rb:33 # Hamster::List 
doesn't give horrendously bad performance if thread realizing the list sleeps
  
  /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
  ERROR: Test "ruby2.3" failed. Exiting.
  dh_auto_install: dh_ruby --install «BUILDDIR»/debian/ruby-hamster returned 
exit code 1
  debian/rules:18: recipe for target 'binary' failed
  make: *** [binary] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
2

  […]

The full build log is attached.


Regards,

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


ruby-hamster.3.0.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Processed: your mail

[Debian Bug Tracking System]

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

> severity 815378 important
Bug #815378 [src:libxmlbird] libxmlbird has incorrect soname or incorrect 
package name
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#851820: marked as done (libmojolicious-plugin-assetpack-perl: FTBFS: Failed 6/36 test programs. 20/242 subtests failed.)

[Debian Bug Tracking System]

Your message dated Sun, 29 Jan 2017 04:18:36 +
with message-id 
and subject line Bug#851820: fixed in libmojolicious-plugin-assetpack-perl 
1.39-1
has caused the Debian Bug report #851820,
regarding libmojolicious-plugin-assetpack-perl: FTBFS: Failed 6/36 test 
programs. 20/242 subtests failed.
to be marked as done.

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

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


-- 
851820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmojolicious-plugin-assetpack-perl
Version: 1.30-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

libmojolicious-plugin-assetpack-perl fails to build from source in 
unstable/amd64:

  […]

  Failed 2/10 subtests 
  t/reloader-process.t . skipped: cpanm CSS::Sass
  Mojo::Home::parse is DEPRECATED at t/Helper.pm line 22.
  Mojo::Home::rel_dir is DEPRECATED in favor of Mojo::Home::rel_file at 
«BUILDDIR»/blib/lib/Mojolicious/Plugin/AssetPack.pm line 28.
  Mojo::Home::parts is DEPRECATED at 
«BUILDDIR»/blib/lib/Mojolicious/Plugin/AssetPack.pm line 28.
  [Thu Jan 19 14:02:26 2017] [debug] GET "/"
  [Thu Jan 19 14:02:26 2017] [debug] Rendering template "index.html.ep" from 
DATA section
  [Thu Jan 19 14:02:26 2017] [debug] Processed asset "app.css". [36b3e7b800]
  [Thu Jan 19 14:02:26 2017] [debug] 200 OK (0.00268s, 373.134/s)
  [Thu Jan 19 14:02:26 2017] [debug] GET "/asset/36b3e7b800/t-reloader.css"
  [Thu Jan 19 14:02:26 2017] [debug] Routing to a callback
  [Thu Jan 19 14:02:26 2017] [debug] 200 OK (0.00057s, 1754.386/s)
  [Thu Jan 19 14:02:26 2017] [debug] GET "/mojo-assetpack-reloader-ws"
  [Thu Jan 19 14:02:26 2017] [debug] Routing to a callback
  [Thu Jan 19 14:02:26 2017] [debug] 101 Switching Protocols (0.000358s, 
2793.296/s)
  [Thu Jan 19 14:02:26 2017] [debug] GET "/"
  [Thu Jan 19 14:02:26 2017] [debug] Rendering cached template "index.html.ep" 
from DATA section
  [Thu Jan 19 14:02:26 2017] [debug] Processed asset "app.css". [5958b3a722]
  [Thu Jan 19 14:02:26 2017] [debug] 200 OK (0.001898s, 526.870/s)
  [Thu Jan 19 14:02:26 2017] [debug] GET "/asset/5958b3a722/t-reloader.css"
  [Thu Jan 19 14:02:26 2017] [debug] Routing to a callback
  [Thu Jan 19 14:02:26 2017] [debug] 200 OK (0.00088s, 1136.364/s)
  t/reloader.t . 
  ok 1 - GET /
  ok 2 - 200 OK
  ok 3 - element for selector "link[href="/asset/36b3e7b800/t-reloader.css"]" 
exists
  ok 4 - GET /asset/36b3e7b800/t-reloader.css
  ok 5 - exact match for content
  ok 6 - WebSocket handshake with /mojo-assetpack-reloader-ws
  ok 7 - WebSocket closed with status 1005
  ok 8 - GET /
  ok 9 - 200 OK
  ok 10 - element for selector "link[href="/asset/5958b3a722/t-reloader.css"]" 
exists
  ok 11 - GET /asset/5958b3a722/t-reloader.css
  ok 12 - exact match for content
  1..12
  ok
  Mojo::Home::parse is DEPRECATED at t/Helper.pm line 22.
  Mojo::Home::rel_dir is DEPRECATED in favor of Mojo::Home::rel_file at 
«BUILDDIR»/blib/lib/Mojolicious/Plugin/AssetPack.pm line 28.
  Mojo::Home::parts is DEPRECATED at 
«BUILDDIR»/blib/lib/Mojolicious/Plugin/AssetPack.pm line 28.
  [Thu Jan 19 14:02:26 2017] [debug] Processed asset "app.js". [7373328564]
  [Thu Jan 19 14:02:26 2017] [debug] GET "/"
  [Thu Jan 19 14:02:26 2017] [debug] Rendering template "index.html.ep" from 
DATA section
  [Thu Jan 19 14:02:26 2017] [debug] 200 OK (0.002382s, 419.815/s)
  [Thu Jan 19 14:02:26 2017] [debug] GET "/asset/7373328564/r1.tag"
  [Thu Jan 19 14:02:26 2017] [debug] Routing to a callback
  [Thu Jan 19 14:02:26 2017] [debug] 200 OK (0.000522s, 1915.709/s)
  t/riotjs-not-loaded.t  
  ok 1 - GET /
  ok 2 - 200 OK
  ok 3 - element for selector "link[href="/asset/7373328564/r1.tag"]" exists
  ok 4 - GET /asset/7373328564/r1.tag
  ok 5 - 200 OK
  ok 6 - Content-Type: text/css
  ok 7 - content is similar
  1..7
  ok
  t/riotjs.t ... skipped: TEST_RIOTJS=1
  Mojo::Home::parse is DEPRECATED at t/Helper.pm line 22.
  Mojo::Home::rel_dir is DEPRECATED in favor of Mojo::Home::rel_file at 
«BUILDDIR»/blib/lib/Mojolicious/Plugin/AssetPack.pm line 28.
  Mojo::Home::parts is DEPRECATED at 
«BUILDDIR»/blib/lib/Mojolicious/Plugin/AssetPack.pm line 28.
  [Thu Jan 19 14:02:27 2017] [debug] Processed asset "app.css". [681090d69b]
  t/route.t  
  ok 1 - one route
  ok 2 - two routes
  1..2
  ok
  t/sass-bin.t . skipped: TEST_SASS=1
  

Processed: bug 794316 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=731654

[Debian Bug Tracking System]

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

> forwarded 794316 https://bugzilla.gnome.org/show_bug.cgi?id=731654
Bug #794316 [gdm3] can't unlock desktop: Too many open files (inotify fds 
leaked on unsuccessful login)
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=731654'.
> thanks
Stopping processing here.

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

Processed: tagging 853018, tagging 789118

[Debian Bug Tracking System]

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

> tags 853018 + pending
Bug #853018 [gnome-shell] Cannot unlock screen after upgrading: Error: can't 
convert this._frame to an integer
Added tag(s) pending.
> tags 789118 + pending
Bug #789118 [gdm3] Cannot unlock screen after upgrading: Type of message, 
'(sssb)', does not match expected type '(sssbb)'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#842446: marked as done (sbsigntool: FTBFS: test sign-verify.sh failed on arch x86_64)

[Debian Bug Tracking System]

Your message dated Sun, 29 Jan 2017 01:34:13 +
with message-id 
and subject line Bug#842446: fixed in sbsigntool 0.6-3.2
has caused the Debian Bug report #842446,
regarding sbsigntool: FTBFS: test sign-verify.sh failed on arch x86_64
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.)


-- 
842446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sbsigntool
Version: 0.6-3.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

sbsigntool fails to build from source in unstable/amd64:

  […]

  objcopy -j .text -j .sdata -j .data \
-j .dynamic -j .dynsym  -j .rel \
-j .rela -j .reloc \
--target=efi-app-x86-64 test-x86_64.elf test-x86_64.pecoff
  strip test-x86_64.pecoff
  gcc -m32 -Wdate-time -D_FORTIFY_SOURCE=2  -c -o test-i386.o test.S
  gcc  -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161029111343.v3qnIZZMCr.db.sbsigntool/sbsigntool-0.6=.
 -fstack-protector-strong -Wformat -Werror=format-security  -nostdlib -T 
./test-i386.lds -o test-i386.elf test-i386.o
  objcopy -j .text -j .sdata -j .data \
-j .dynamic -j .dynsym  -j .rel \
-j .rela -j .reloc \
--target=efi-app-i386 test-i386.elf test-i386.pecoff
  strip test-i386.pecoff
  make[4]: Nothing to be done for 'test-wrapper.sh'.
  openssl genrsa -out private-key.rsa 2048
  Generating RSA private key, 2048 bit long modulus
  
..+++
  
.+++
  e is 65537 (0x10001)
  openssl req -x509 -sha256 -subj '/' -new -key private-key.rsa -out 
public-cert.pem
  rm test-x86_64.elf test-i386.o test-i386.elf test-x86_64.o
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20161029111343.v3qnIZZMCr.db.sbsigntool/sbsigntool-0.6/tests'
  make  check-TESTS
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20161029111343.v3qnIZZMCr.db.sbsigntool/sbsigntool-0.6/tests'
  make[5]: Entering directory 
'/home/lamby/temp/cdt.20161029111343.v3qnIZZMCr.db.sbsigntool/sbsigntool-0.6/tests'
  FAIL: sign-verify.sh
  FAIL: sign-verify-detached.sh
  FAIL: sign-detach-verify.sh
  FAIL: sign-attach-verify.sh
  PASS: sign-missing-image.sh
  PASS: sign-missing-cert.sh
  PASS: sign-missing-key.sh
  PASS: verify-missing-image.sh
  FAIL: verify-missing-cert.sh
  PASS: sign-invalidattach-verify.sh
  FAIL: cert-table-header.sh
  FAIL: resign-warning.sh
  FAIL: reattach-warning.sh
  FAIL: detach-remove.sh
  ==
 sbsigntool 0.6: tests/test-suite.log
  ==
  
  # TOTAL: 14
  # PASS:  5
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  9
  # XPASS: 0
  # ERROR: 0
  
  .. contents:: :depth: 2
  
  FAIL: sign-verify
  =
  
  Invalid a.out machine type
  Error parsing a.out header
  test sign-verify.sh failed on arch x86_64
  
  Invalid a.out machine type
  Error parsing a.out header
  test sign-verify.sh failed on arch i386
  
  FAIL sign-verify.sh (exit status: 1)
  
  FAIL: sign-verify-detached
  ==
  
  Invalid a.out machine type
  Error parsing a.out header
  test sign-verify-detached.sh failed on arch x86_64
  
  Invalid a.out machine type
  Error parsing a.out header
  test sign-verify-detached.sh failed on arch i386
  
  FAIL sign-verify-detached.sh (exit status: 1)
  
  FAIL: sign-detach-verify
  
  
  Invalid a.out machine type
  Error parsing a.out header
  test sign-detach-verify.sh failed on arch x86_64
  
  Invalid a.out machine type
  Error parsing a.out header
  test sign-detach-verify.sh failed on arch i386
  
  FAIL sign-detach-verify.sh (exit status: 1)
  
  FAIL: sign-attach-verify
  
  
  Invalid a.out machine type
  Error parsing a.out header
  test sign-attach-verify.sh failed on arch x86_64
  
  Invalid a.out machine type
  Error parsing a.out header
  test sign-attach-verify.sh failed on arch i386
  
  FAIL sign-attach-verify.sh (exit status: 1)
  
  FAIL: verify-missing-cert
  =
  
  Invalid a.out machine type
  Error parsing a.out header
  test verify-missing-cert.sh failed on arch x86_64
  
  Invalid a.out machine type
  Error parsing a.out header
  test verify-missing-cert.sh failed on 

Bug#842446: sbsigntool: FTBFS: test sign-verify.sh failed on arch x86_64

[Ben Hutchings]

On Sat, 29 Oct 2016 11:14:49 +0100 Chris Lamb  wrote:
[...]
>   FAIL: sign-verify.sh
>   FAIL: sign-verify-detached.sh
>   FAIL: sign-detach-verify.sh
>   FAIL: sign-attach-verify.sh
>   PASS: sign-missing-image.sh
>   PASS: sign-missing-cert.sh
>   PASS: sign-missing-key.sh
>   PASS: verify-missing-image.sh
>   FAIL: verify-missing-cert.sh
>   PASS: sign-invalidattach-verify.sh
>   FAIL: cert-table-header.sh
>   FAIL: resign-warning.sh
>   FAIL: reattach-warning.sh
>   FAIL: detach-remove.sh
>   ==
>  sbsigntool 0.6: tests/test-suite.log
>   ==
>   
>   # TOTAL: 14
>   # PASS:  5
>   # SKIP:  0
>   # XFAIL: 0
[...]

Andrey Rahmatullin  wrote:
> I get an even earlier error on an amd64 system:
> 
> make[4]: Entering directory '/<>/tests'
> gcc -m64 -Wdate-time -D_FORTIFY_SOURCE=2  -c -o test-x86_64.o test.S
> gcc  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security  -nostdlib -T ./test-x86_64.lds -o 
> test-x86_64.elf test-x86_64.o
> /usr/bin/ld: test-x86_64.elf: Not enough room for program headers, try 
> linking with -N
[...]

With a current unstable system I can reproduce this, and if I use an
archive snapshot from 2016-10-29 I can reproduce the test failures
Chris got.

The problem seems to be that ld is attempting to set the dynamic linker
path in the header of a program that isn't meant to be dynamically
linked.  This seems like a bug in binutils, but in any case I've seen
it before and it can be solved by adding --no-dynamic-linker to the ld
command line.  This fixes the build failure and fixes the test failures
with the older toolchain.

I made an NMU to fix this, and am attaching the debdiff.

Ben.

-- 
Ben Hutchings
All the simple programs have been written, and all the good names
taken.
diff -Nru sbsigntool-0.6/debian/changelog sbsigntool-0.6/debian/changelog
--- sbsigntool-0.6/debian/changelog	2016-06-26 22:39:15.0 +0100
+++ sbsigntool-0.6/debian/changelog	2017-01-29 01:00:17.0 +
@@ -1,3 +1,10 @@
+sbsigntool (0.6-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix linker flags for test cases (Closes: #842446)
+
+ -- Ben Hutchings   Sun, 29 Jan 2017 01:00:17 +
+
 sbsigntool (0.6-3.1) unstable; urgency=medium
 
   * Non-maintainer upload with approval of maintainer
diff -Nru sbsigntool-0.6/debian/patches/fix-linker-flags-for-test-cases.patch sbsigntool-0.6/debian/patches/fix-linker-flags-for-test-cases.patch
--- sbsigntool-0.6/debian/patches/fix-linker-flags-for-test-cases.patch	1970-01-01 01:00:00.0 +0100
+++ sbsigntool-0.6/debian/patches/fix-linker-flags-for-test-cases.patch	2017-01-29 01:00:17.0 +
@@ -0,0 +1,21 @@
+Author: Ben Hutchings 
+Date: Sun, 29 Jan 2017 00:25:50 +
+Description: Fix linker flags for test cases
+ We need to explicitly disable use of a dynamic linker.  When using
+ Debian's binutils 2.27-9, ld succeeds but appears to generate broken
+ headers that cause the tests to fail.  When using binutils 2.28, ld
+ fails, reporting "Not enough room for program headers, try linking
+ with -N".
+Bug-Debian: https://bugs.debian.org/842446
+
+--- a/tests/Makefile.am
 b/tests/Makefile.am
+@@ -29,7 +29,7 @@ test-i386.pecoff: test_lds = $(srcdir)/t
+ test-i386.pecoff: ASFLAGS += -m32
+ test-i386.pecoff: LDFLAGS += -m32
+ 
+-test-%.elf: LDFLAGS = -nostdlib -T $(test_lds)
++test-%.elf: LDFLAGS = -nostdlib -T $(test_lds) -Wl,--no-dynamic-linker
+ test-%.elf: test-%.$(OBJEXT) $(test_lds)
+ 	$(LINK) $<
+ 
diff -Nru sbsigntool-0.6/debian/patches/series sbsigntool-0.6/debian/patches/series
--- sbsigntool-0.6/debian/patches/series	2016-06-26 21:55:38.0 +0100
+++ sbsigntool-0.6/debian/patches/series	2017-01-29 01:00:17.0 +
@@ -13,3 +13,4 @@
 sbsign_check_write_return.patch
 update-openssl-api-usage-to-support-openssl-1.1.patch
 fix-efi-arch-detection.patch
+fix-linker-flags-for-test-cases.patch


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

Bug#852822: signing buildinfo by default breaks compatibility

[Ian Jackson]

Guillem Jover writes ("Re: Bug#852822: signing buildinfo by default breaks 
compatibility"):
> I actually realized this while I was waking up today, and brought it
> up on IRC. My biggest concern was the buildd network, because that
> is explicitly not signing files from inside the chroots. But due to
> gnupg not being installed anymore by default (and very few packages
> at least directly Build-Depending on it), and the buildd chroots not
> containing any home directory, the signing is not performed anyway.
> So in that sense the upload was "safe" from the major fallout. And I
> was then planning on fixing this for .20, after the testing migration
> as it indeed breaks user's and other tools expectations.

Thanks for fixing it earlier.

I didn't do thorough tests, but the change would have broken dgit.
Probably the test suite; perhaps the build wrapper methods; and
certainly the workflow documentation.

> Yes, that's also the conclusion I had arrived at noon, even though
> that makes the semantics suck a bit, but oh well. The other thing I
> was planning (and I've done locally), is to add a new --no-sign
> option which will make this kind of thing future-proof.

Can you please make a short alias for --no-sign ?  Many tasks
(particularly ones done by non-dds) involve building packages without
signing them.

Also, please bear in mind that runes in documentation like
dgit-user(7) will live on in people's finger macros for many years.

Thanks,
Ian.

https://manpages.debian.org/testing/dgit/dgit-user.7.en.html

-- 
Ian Jackson    These opinions are my own.

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

Processed: Pending fixes for bugs in the commons-math3 package

[Debian Bug Tracking System]

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

> tag 852880 + pending
Bug #852880 [src:commons-math3] commons-math3: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#852880: Pending fixes for bugs in the commons-math3 package

[pkg-java-maintainers]

tag 852880 + pending
thanks

Some bugs in the commons-math3 package are closed in revision
9634aaa7bf9c60bc94cc58c4e53633430eb56be3 in branch 'master' by tony
mancill

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/commons-math3.git/commit/?id=9634aaa

Commit message:

add --allow-script-in-comments to maven-javadoc-plugin invocation

Closes: #852880 (FTBFS)

Processed: tagging 852880

[Debian Bug Tracking System]

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

> tags 852880 + confirmed
Bug #852880 [src:commons-math3] commons-math3: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#821892: marked as done (pycountry: FTBFS: tests/test_general.py:28: AssertionError)

[Debian Bug Tracking System]

Your message dated Sun, 29 Jan 2017 00:08:04 +
with message-id 
and subject line Bug#821892: fixed in pycountry 1.8+ds1-0.2
has caused the Debian Bug report #821892,
regarding pycountry: FTBFS: tests/test_general.py:28: AssertionError
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.)


-- 
821892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pycountry
Version: 1.8+ds1-0.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

pycountry fails to build from source in unstable/amd64:

  [..]

  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'pycountry-build-deps' in 
'../pycountry-build-deps_1.8+ds1-0.1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package pycountry-build-deps.
  (Reading database ... 22998 files and directories currently installed.)
  Preparing to unpack pycountry-build-deps_1.8+ds1-0.1_all.deb ...
  Unpacking pycountry-build-deps (1.8+ds1-0.1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
iso-codes python-py python-pytest python-setuptools python3-pkg-resources
python3-py python3-pytest python3-setuptools unzip
  Suggested packages:
isoquery subversion python-pytest-xdist python-mock python-setuptools-doc
zip
  The following NEW packages will be installed:
iso-codes python-py python-pytest python-setuptools python3-pkg-resources
python3-py python3-pytest python3-setuptools unzip
  0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 3376 kB of archives.
  After this operation, 21.1 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 unzip amd64 6.0-20 
[161 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 python-setuptools all 
20.7.0-1 [202 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 python3-pkg-resources 
all 20.7.0-1 [111 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 python3-setuptools 
all 20.7.0-1 [121 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 python-py all 
1.4.31-1 [81.8 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 python-pytest all 
2.9.1-1 [166 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 python3-py all 
1.4.31-1 [81.9 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 python3-pytest all 
2.9.1-1 [166 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 iso-codes all 3.67-1 
[2285 kB]
  Fetched 3376 kB in 0s (49.2 MB/s)
  Selecting previously unselected package unzip.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23002 files and directories currently installed.)
  Preparing to unpack .../unzip_6.0-20_amd64.deb ...
  Unpacking unzip (6.0-20) ...
  Selecting previously unselected package python-setuptools.
  Preparing to unpack .../python-setuptools_20.7.0-1_all.deb ...
  Unpacking python-setuptools (20.7.0-1) ...
  Selecting previously unselected package python3-pkg-resources.
  Preparing to unpack .../python3-pkg-resources_20.7.0-1_all.deb ...
  Unpacking python3-pkg-resources (20.7.0-1) ...
  Selecting previously unselected package python3-setuptools.
  Preparing to unpack .../python3-setuptools_20.7.0-1_all.deb ...
  Unpacking python3-setuptools (20.7.0-1) ...
  Selecting previously unselected package python-py.
  Preparing to unpack .../python-py_1.4.31-1_all.deb ...
  Unpacking python-py 

Bug#821892: Missing patch

[Daniel Silverstone]

Hi,

here's the missing patch, sorry, my email had a snafu.

D.

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69
diff -Nru pycountry-1.8+ds1/debian/changelog pycountry-1.8+ds1/debian/changelog
--- pycountry-1.8+ds1/debian/changelog	2014-08-27 00:21:20.0 +0100
+++ pycountry-1.8+ds1/debian/changelog	2017-01-28 23:28:00.0 +
@@ -1,3 +1,10 @@
+pycountry (1.8+ds1-0.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add 01-disable-failing-asserts.patch (Closes: #821892)
+
+ -- Daniel Silverstone   Sat, 28 Jan 2017 23:27:30 +
+
 pycountry (1.8+ds1-0.1) unstable; urgency=medium
 
   * New upstream release
diff -Nru pycountry-1.8+ds1/debian/patches/02-disable-failing-asserts.patch pycountry-1.8+ds1/debian/patches/02-disable-failing-asserts.patch
--- pycountry-1.8+ds1/debian/patches/02-disable-failing-asserts.patch	1970-01-01 01:00:00.0 +0100
+++ pycountry-1.8+ds1/debian/patches/02-disable-failing-asserts.patch	2017-01-28 23:31:34.0 +
@@ -0,0 +1,52 @@
+Description: Disable failing asserts
+ iso-codes has long moved on beyond that which pycountry knows.
+ This means the count of countries, subdivisions, etc are out of
+ date.  Rather than risk an FTBFS when iso-codes moves on once more
+ simply comment out the specific asserts, leaving the rest of the
+ testing intact.
+Author: Daniel Silverstone 
+Origin: other
+Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821892
+Forwarded: no
+Reviewed-by: Jonathan Wiltshire 
+Last-Update: 2017-02-28
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/pycountry/tests/test_general.py
 b/src/pycountry/tests/test_general.py
+@@ -25,7 +25,7 @@
+ 
+ 
+ def test_subdivisions_directly_accessible():
+-assert len(pycountry.subdivisions) == 4847
++#assert len(pycountry.subdivisions) == 4847
+ assert isinstance(list(pycountry.subdivisions)[0], pycountry.db.Data)
+ 
+ de_st = pycountry.subdivisions.get(code='DE-ST')
+@@ -51,7 +51,7 @@
+ 
+ 
+ def test_scripts():
+-assert len(pycountry.scripts) == 169
++#assert len(pycountry.scripts) == 169
+ assert isinstance(list(pycountry.scripts)[0], pycountry.db.Data)
+ 
+ latin = pycountry.scripts.get(name='Latin')
+@@ -61,7 +61,7 @@
+ 
+ 
+ def test_currencies():
+-assert len(pycountry.currencies) == 182
++#assert len(pycountry.currencies) == 182
+ assert isinstance(list(pycountry.currencies)[0], pycountry.db.Data)
+ 
+ argentine_peso = pycountry.currencies.get(letter='ARS')
+@@ -71,7 +71,7 @@
+ 
+ 
+ def test_languages():
+-assert len(pycountry.languages) == 487
++#assert len(pycountry.languages) == 487
+ assert isinstance(list(pycountry.languages)[0], pycountry.db.Data)
+ 
+ aragonese = pycountry.languages.get(alpha2='an')
diff -Nru pycountry-1.8+ds1/debian/patches/series pycountry-1.8+ds1/debian/patches/series
--- pycountry-1.8+ds1/debian/patches/series	2014-07-09 16:49:47.0 +0100
+++ pycountry-1.8+ds1/debian/patches/series	2017-01-28 23:26:49.0 +
@@ -1,2 +1,3 @@
 00-use_system_iso-codes.patch
 01-prevent_logger_warning.patch
+02-disable-failing-asserts.patch

Bug#851576: marked as done (xtables-addons-dkms: Error building against Linux 4.9)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 23:48:31 +
with message-id 
and subject line Bug#851576: fixed in xtables-addons 2.12-0.1
has caused the Debian Bug report #851576,
regarding xtables-addons-dkms: Error building against Linux 4.9
to be marked as done.

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

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


-- 
851576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xtables-addons-dkms
Version: 2.11-3
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

DKMS make.log for xtables-addons-2.11 for kernel 4.9.0-1-amd64 (x86_64)
Mon 16 Jan 13:34:05 GMT 2017
make: Entering directory '/usr/src/linux-headers-4.9.0-1-amd64'
make -C /usr/src/linux-headers-4.9.0-1-amd64 
KBUILD_SRC=/usr/src/linux-headers-4.9.0-1-common \
- -f /usr/src/linux-headers-4.9.0-1-common/Makefile modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo >&2;   \
echo >&2 "  ERROR: Kernel configuration is invalid.";   \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are 
missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";  \
echo >&2 ;  \
/bin/false)
mkdir -p /var/lib/dkms/xtables-addons/2.11/build/extensions/.tmp_versions ; rm 
-f /var/lib/dkms/xtables-addons/2.11/build/extensions/.tmp_versions/*
make -f /usr/src/linux-headers-4.9.0-1-common/scripts/Makefile.build 
obj=/var/lib/dkms/xtables-addons/2.11/build/extensions
   gcc-6 
-Wp,-MD,/var/lib/dkms/xtables-addons/2.11/build/extensions/.compat_xtables.o.d  
-nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/6/include 
-I/usr/src/linux-headers-4.9.0-1-common/arch/x86/include 
-I./arch/x86/include/generated/uapi -I./arch/x86/include/generated  
-I/usr/src/linux-headers-4.9.0-1-common/include -I./include 
-I/usr/src/linux-headers-4.9.0-1-common/arch/x86/include/uapi 
-I/usr/src/linux-headers-4.9.0-1-common/include/uapi -I./include/generated/uapi 
-include /usr/src/linux-headers-4.9.0-1-common/include/linux/kconfig.h 
-I/usr/src/linux-headers-4.9.0-1-common//var/lib/dkms/xtables-addons/2.11/build/extensions
 -I/var/lib/dkms/xtables-addons/2.11/build/extensions -D__KERNEL__ -Wall 
-Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common 
-Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE 
-mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 
-falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 
-mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time 
-maccumulate-outgoing-args -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 
-DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 
-DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 
-DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe 
-Wno-sign-compare -fno-asynchronous-unwind-tables 
-fno-delete-null-pointer-checks -Wno-frame-address -O2 
--param=allow-store-data-races=0 -Wframe-larger-than=2048 
-fstack-protector-strong -Wno-unused-but-set-variable 
-Wno-unused-const-variable -fno-var-tracking-assignments -g -pg -mfentry 
-DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign 
-fno-strict-overflow -fconserve-stack -Werror=implicit-int 
-Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types 
-DCC_HAVE_ASM_GOTO  -DMODULE  -DKBUILD_BASENAME='"compat_xtables"'  
-DKBUILD_MODNAME='"compat_xtables"' -c -o 
/var/lib/dkms/xtables-addons/2.11/build/extensions/.tmp_compat_xtables.o 
/var/lib/dkms/xtables-addons/2.11/build/extensions/compat_xtables.c
   gcc-6 
-Wp,-MD,/var/lib/dkms/xtables-addons/2.11/build/extensions/.xt_CHAOS.o.d  
-nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/6/include 
-I/usr/src/linux-headers-4.9.0-1-common/arch/x86/include 
-I./arch/x86/include/generated/uapi -I./arch/x86/include/generated  
-I/usr/src/linux-headers-4.9.0-1-common/include -I./include 
-I/usr/src/linux-headers-4.9.0-1-common/arch/x86/include/uapi 
-I/usr/src/linux-headers-4.9.0-1-common/include/uapi -I./include/generated/uapi 
-include /usr/src/linux-headers-4.9.0-1-common/include/linux/kconfig.h 
-I/usr/src/linux-headers-4.9.0-1-common//var/lib/dkms/xtables-addons/2.11/build/extensions
 -I/var/lib/dkms/xtables-addons/2.11/build/extensions -D__KERNEL__ -Wall 
-Wundef -Wstrict-prototypes 

Bug#821892: Fix patch - disables broken asserts

[Daniel Silverstone]

Hi,

I have prepared an NMU which disables the rogue asserts.  They make an
assumption on the size of the iso-codes databases which have moved on since
pycountry.  Rather than updating the numbers in the package which will fail the
next time iso-codes changes size again, simply disable the rogue asserts and
just let the rest of the test suite run.

I have uploaded this to Unstable.

D.

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69

Bug#852472: marked as done (linux-image-4.9.0-1-amd64 fails compiling xt_ACCOUNT.ko out of package xtables-addons-dkms)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 23:48:31 +
with message-id 
and subject line Bug#851576: fixed in xtables-addons 2.12-0.1
has caused the Debian Bug report #851576,
regarding linux-image-4.9.0-1-amd64 fails compiling xt_ACCOUNT.ko out of 
package xtables-addons-dkms
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.)


-- 
851576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-4.9.0-1-amd64
Status: install ok installed
Priority: optional
Section: kernel
Installed-Size: 183299
Maintainer: Debian Kernel Team 
Architecture: amd64
Source: linux-signed (4)
Version: 4.9.2-2
Replaces: linux-image-4.9.0-1-amd64-unsigned
Depends: kmod, linux-base (>= 4.3~), initramfs-tools (>= 0.110~) |
linux-initramfs-tool
Recommends: firmware-linux-free, irqbalance
Suggests: linux-doc-4.9, debian-kernel-handbook, grub-pc |
grub-efi-amd64 | extlinux
Breaks: initramfs-tools (<< 0.110~), xserver-xorg-input-vmmouse (<<
1:13.0.99)
Conflicts: linux-image-4.9.0-1-amd64-unsigned
Description: Linux 4.9 for 64-bit PCs (signed)
 The Linux kernel 4.9 and modules for use on PCs with AMD64, Intel 64 or
 VIA Nano processors.
 .
 This kernel also runs on a Xen hypervisor.  It supports both privileged
 (dom0) and unprivileged (domU) operation.
 .
 The kernel image and modules are signed for use with Secure Boot.
Built-Using: linux (= 4.9.2-2)
Homepage: https://www.kernel.org/


Package: xtables-addons-dkms
Status: install ok installed
Priority: extra
Section: kernel
Installed-Size: 1563
Maintainer: Pierre Chifflier 
Architecture: all
Source: xtables-addons
Version: 2.11-3
Depends: xtables-addons-common (>= 2.11), dkms (>= 2.1.0.0), make
Recommends: linux-headers
Description: Extensions targets and matches for iptables
 Xtables-addons provides extra modules for iptables not present in the
 kernel, and is the successor of patch-o-matic.
 Extensions includes new targets like TEE, TARPIT, CHAOS, or modules like
 geoip and account.
 .
 The dkms package will automatically compile the driver for your current
 kernel version.
Homepage: http://xtables-addons.sourceforge.net/


Calling Error-Message to reproduce:
---
# apt install xtables-addons-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  xtables-addons-common
Recommended packages:
  linux-headers
The following NEW packages will be installed:
  xtables-addons-common xtables-addons-dkms
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/343 kB of archives.
After this operation, 1914 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Selecting previously unselected package xtables-addons-common.
(Reading database ... 66169 files and directories currently installed.)
Preparing to unpack .../xtables-addons-common_2.11-3_amd64.deb ...
Unpacking xtables-addons-common (2.11-3) ...
Selecting previously unselected package xtables-addons-dkms.
Preparing to unpack .../xtables-addons-dkms_2.11-3_all.deb ...
Unpacking xtables-addons-dkms (2.11-3) ...
Setting up xtables-addons-common (2.11-3) ...
Processing triggers for libc-bin (2.24-8) ...
Setting up xtables-addons-dkms (2.11-3) ...
Loading new xtables-addons-2.11 DKMS files...
Building for 4.9.0-1-amd64
Building initial module for 4.9.0-1-amd64
Error!  Build of xt_ACCOUNT.ko failed for: 4.9.0-1-amd64 (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/xtables-addons/2.11/build/ for more information.
Processing triggers for man-db (2.7.6.1-2) ...


Make.log:
---
# cat /var/lib/dkms/xtables-addons/2.11/build/make.log
DKMS make.log for xtables-addons-2.11 for kernel 4.9.0-1-amd64 (x86_64)
Tue Jan 24 19:36:03 CET 2017
make: Entering directory '/usr/src/linux-headers-4.9.0-1-amd64'
make -C /usr/src/linux-headers-4.9.0-1-amd64
KBUILD_SRC=/usr/src/linux-headers-4.9.0-1-common \
-f /usr/src/linux-headers-4.9.0-1-common/Makefile modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo >&2;   \
echo >&2 "  ERROR: Kernel configuration is invalid.";   \
echo >&2 " include/generated/autoconf.h or
include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to
fix it.";   \
echo >&2 ;  \
/bin/false)
mkdir -p

Bug#757083: Migration from sysvinit to systemd: reboot fails to complete

[Ben Hutchings]

Control: tag -1 pending

On Tue, 3 Jan 2017 19:41:28 -0300 Felipe Sateler  wrote:
> Control: severity -1 serious
> Control: tags -1 - patch
> 
> 
> On 31 December 2016 at 08:30, Francesco Poli  
> wrote:
> > On Fri, 30 Dec 2016 22:21:32 +0100 Michael Biebl wrote:
> >
> >> Am 30.12.2016 um 22:16 schrieb Felipe Sateler:
> > [...]
> >> > But, your experience appears to uncover
> >> > another bug: for some reason the sysvinit mount scripts will unmount
> >> > /usr! This is a bad idea, as the distinction between / and /usr is not
> >> > relevant anymore (because we now have initramfs), and will stop
> >> > existing after the /usr merge. The question is, why would sysvinit
> >> > unmount /usr, it probably shouldn't.
> >>
> >> Can anyone reproduce this? If so, this should probably be filed as a RC
> >> bug (*) against initscripts to not do that.
> > [...]
> >> (*) RC as in this should be fixed for stretch
> >
> > I searched through the bug reports assigned to binary packages built
> > from sysvinit source package.
> > Maybe the bug has already been reported:
> > https://bugs.debian.org/757083
> > I haven't had the time to read all the bug log carefully: does this bug
> > include the issue under discussion?
> > Maybe the severity of this bug report should be raised...
> 
> Indeed, I think it should and am now raising it, and this should really
> be fixed for stretch.
> 
> Unmounting /usr alongside other filesystems is problematic because:
> 
> 1. Commands used after that might live or use a library that lives in /usr
> 2. Is not compatible with merging / into /usr.

I've committed a fix for this in git.  Could one of the maintainers
please upload the pending changes?

Ben.

-- 
Ben Hutchings
It is easier to write an incorrect program than to understand a correct
one.



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

Processed: Re: Migration from sysvinit to systemd: reboot fails to complete

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #757083 [initscripts] initscripts: please treat /usr (if separate) the same 
as /
Added tag(s) pending.

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

Bug#852917: marked as done (botch: FTBFS: Error: Unbound value Architecture.read_triplettable)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 22:49:16 +
with message-id <e1cxbo4-0004am...@fasolo.debian.org>
and subject line Bug#852917: fixed in botch 0.21-3
has caused the Debian Bug report #852917,
regarding botch: FTBFS: Error: Unbound value Architecture.read_triplettable
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.)


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

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> atdgen -j -j-std datatypes.atd
> atdgen -t datatypes.atd
> OCAMLPATH=/<>/dose/_build ocamlbuild -lflags 
> -runtime-variant,_pic -classic-display -use-ocamlfind -cflags "-w +a-4-9-24" 
> create-graph.native print-stats.native bin2src.native src2bin.native 
> build-fixpoint.native clean-repository.native buildgraph2srcgraph.native 
> annotate-strong.native partial-order.native find-fvs.native 
> collapse-srcgraph.native optuniv.native calculate-fas.native 
> buildcheck-more-problems.native distcheck-more-problems.native
> ocamlfind ocamldep -package dose3 -package dose3.doseparseNoRpm -package 
> atdgen -package xmlm -package parmap -package extlib -pp cppo -modules 
> create-graph.ml > create-graph.ml.depends
> ocamlfind ocamldep -package dose3 -package dose3.doseparseNoRpm -package 
> atdgen -package xmlm -package parmap -package extlib -pp cppo -modules 
> bootstrapCommon.ml > bootstrapCommon.ml.depends
> ocamlfind ocamldep -package dose3 -package dose3.doseparseNoRpm -package 
> atdgen -package xmlm -package parmap -package extlib -pp cppo -modules 
> buildGraph.ml > buildGraph.ml.depends
> ocamlfind ocamlc -c -w +a-4-9-24 -package dose3 -package dose3.doseparseNoRpm 
> -package atdgen -package xmlm -package re.pcre -package parmap -package 
> extlib -pp cppo -o bootstrapCommon.cmo bootstrapCommon.ml
> ocamlfind ocamldep -package dose3 -package dose3.doseparseNoRpm -package 
> atdgen -package xmlm -package parmap -package extlib -pp cppo -modules 
> graphUtils.ml > graphUtils.ml.depends
> ocamlfind ocamldep -package dose3 -package dose3.doseparseNoRpm -package 
> atdgen -package xmlm -package parmap -package extlib -pp cppo -modules 
> graphmlReader.ml > graphmlReader.ml.depends
> ocamlfind ocamldep -package dose3 -package dose3.doseparseNoRpm -package 
> atdgen -package xmlm -package parmap -package extlib -pp cppo -modules 
> unique.ml > unique.ml.depends
> ocamlfind ocamlc -c -w +a-4-9-24 -package dose3 -package dose3.doseparseNoRpm 
> -package atdgen -package xmlm -package re.pcre -package parmap -package 
> extlib -pp cppo -o graphUtils.cmo graphUtils.ml
> ocamlfind ocamlc -c -w +a-4-9-24 -package dose3 -package dose3.doseparseNoRpm 
> -package atdgen -package xmlm -package re.pcre -package parmap -package 
> extlib -pp cppo -o graphmlReader.cmo graphmlReader.ml
> ocamlfind ocamlc -c -w +a-4-9-24 -package dose3 -package dose3.doseparseNoRpm 
> -package atdgen -package xmlm -package re.pcre -package parmap -package 
> extlib -pp cppo -o unique.cmo unique.ml
> ocamlfind ocamlc -c -w +a-4-9-24 -package dose3 -package dose3.doseparseNoRpm 
> -package atdgen -package xmlm -package re.pcre -package parmap -package 
> extlib -pp cppo -o buildGraph.cmo buildGraph.ml
> ocamlfind ocamlc -c -w +a-4-9-24 -package dose3 -package dose3.doseparseNoRpm 
> -package atdgen -package xmlm -package re.pcre -package parmap -package 
> extlib -pp cppo -o create-graph.cmo create-graph.ml
> ocamlfind ocamlopt -c -w +a-4-9-24 -package dose3 -package 
> dose3.doseparseNoRpm -package atdgen -package xmlm -package re.pcre -package 
> parmap -package extlib -pp cppo -o bootstrapCommon.cmx bootstrapCommon.ml
> ocamlfind ocamlopt -c -w +a-4-9-24 -package dose3 -package 
> dose3.doseparseNoRpm -package atdgen -package xmlm -package re.pcre -package 
> parmap -package extlib -pp cppo -o graphUtils.cmx graphUtils.ml
> ocamlfind ocamlopt -c -w +a-4-9-24 -package dose3 -package 
> dose3.doseparseNoRpm -package atdgen -package xmlm -package re.pcre -package 
> parmap -package extlib -pp cppo -o graphmlReader.cmx graphmlReader.ml
> ocamlfind ocamlopt -c -w +a-4-9-24 

Bug#853017: marked as done (bitlbee: FTBFS on every autobuilder: dh_testroot: You must run this as root (or use fakeroot).)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 22:48:42 +
with message-id 
and subject line Bug#853017: fixed in bitlbee 3.5-2
has caused the Debian Bug report #853017,
regarding bitlbee: FTBFS on every autobuilder: dh_testroot: You must run this 
as root (or use fakeroot).
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.)


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

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh_testdir
mkdir -p debian/build-native
ROOT=$PWD; cd debian/build-native; BITLBEE_VERSION="3.5-1.1" 
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" LDFLAGS="-Wl,-z,relro" $ROOT/configure --debug=0 
--prefix=/usr --etcdir=/etc/bitlbee --events=libevent --otr=plugin --skype=0 
BitlBee configure

configure script run from a different directory. Will create some symlinks...
Spoofing version number: 3.5-1.1

Architecture: Linux

Configuration done:
  Debugging disabled.
  AddressSanitizer (ASAN) disabled.

[... snipped ...]

/usr/bin/make -C doc/user-guide
make[1]: Entering directory '/<>/doc/user-guide'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/<>/doc/user-guide'
touch build-stamp
dh_testdir
dh_testroot
dh_testroot: You must run this as root (or use fakeroot).
debian/rules:77: recipe for target 'install' failed
make: *** [install] Error 255
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This happens because the build-* targets depend on their binary-* counterparts,
but this should never be the case, because they are invoked as a normal user by
either "dpkg-buildpackage -A" or "dpkg-buildpackage -B", so we are not root yet
to execute the binary-targets.

Suggested fix: There was already a working build target, just make the two
additional build-* targets to depend on it.

Trivial (but untested) patch follows. Please ensure that the package is 
buildable
with both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" before uploading 
again.

Thanks.

--- a/debian/rules
+++ b/debian/rules
@@ -41,8 +41,8 @@ CONFIGURE_OVERRIDES:=CPPFLAGS="$(CPPFLAGS)" 
CFLAGS="$(CFLAGS)" LDFLAGS="$(LDFLAG
 
 HAS_DH_SYSTEMD:=$(shell dpkg-query -W -f='$${Status}' dh-systemd 2>/dev/null | 
grep -c "ok installed")
 # https://bugs.debian.org/821967
-build-indep: binary-indep
-build-arch: binary-arch
+build-indep: build
+build-arch: build
 
 build: build-stamp
 build-stamp:
--- End Message ---
--- Begin Message ---
Source: bitlbee
Source-Version: 3.5-2

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

Debian distribution maintenance software
pp.
Wilmer van der Gaast  (supplier of updated bitlbee 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: Sat, 28 Jan 2017 21:06:27 +
Source: bitlbee
Binary: bitlbee bitlbee-libpurple bitlbee-common bitlbee-dev bitlbee-plugin-otr 
bitlbee-plugin-skype skyped
Architecture: source all amd64
Version: 3.5-2
Distribution: unstable
Urgency: medium
Maintainer: Wilmer van der Gaast 
Changed-By: Wilmer van der Gaast 
Description:
 bitlbee- IRC to other chat networks gateway (default version)
 bitlbee-common - IRC to other chat networks gateway (common files/docs)
 bitlbee-dev - IRC to other chat networks gateway (dev files)
 bitlbee-libpurple - IRC to other chat networks gateway (using libpurple)
 bitlbee-plugin-otr - IRC to other chat networks gateway (OTR plugin)
 bitlbee-plugin-skype - IRC to other chat networks gateway (Skype plugin)
 skyped - Daemon to control Skype remotely
Closes: 

Bug#789118: Cannot unlock screen after upgrading GNOME if locked before upgrade

[Simon McVittie]

Control: clone 789118 -2
Control: retitle 789118 Cannot unlock screen after upgrading: Type of message, 
'(sssb)', does not match expected type '(sssbb)'
Control: retitle -2 Cannot unlock screen after upgrading: Error: can't convert 
this._frame to an integer
Control: reassign -2 gnome-shell 3.14.4-1

On Wed, 25 Jan 2017 at 12:52:13 +, Simon McVittie wrote:
> On Sun, 11 Oct 2015 at 15:48:10 -0700, Josh Triplett wrote:
> > gnome-session[551]: (gnome-shell:956): Gjs-WARNING **: JS ERROR: Failed to 
> > start verification for user: Gio.DBusError: 
> > GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: 
> > GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Type of message, 
> > '(sssb)', does not match expected type '(sssbb)'
> 
> This is really a gdm3 issue

Using #789118 to represent this. My patch can fix this by being applied
to stretch, although I seem to have got the preinst logic wrong:
/run/gdm3-upgraded-from-debian-8 didn't get created and I had to do that
by hand.

On Wed, 25 Jan 2017 at 14:13:36 +, Simon McVittie wrote:
> I think this might be caused by gnome-shell raising an exception when
> it fails to load an animation, with the traceback below, and the PAM
> conversation not proceeding because gnome-shell is no longer talking
> to the gdm-session-worker as a result of that exception.
...
> That looks like https://bugzilla.redhat.com/show_bug.cgi?id=1350303
> which is some sort of install-order issue, or possibly the existing
> gnome-shell trying to use the old pixbuf loader cache that has been
> invalidated in the meantime by upgrading.
> 
> There is a workaround for that bug in stretch's gnome-shell, added
> by ;
> but of course during a live upgrade we're still dealing with jessie's
> gnome-shell, not stretch's, so we can't fix bugs.

Using the cloned bug to represent this, and reassigning back to gnome-shell.
This is going to be really difficult to fix unless we can find the
underlying issue (in gdk-pixbuf?), because it's difficult to get a
gnome-shell with the workaround deployed on the to-be-upgraded system
*before* doing the upgrade.

S

Processed: Re: Bug#789118: Cannot unlock screen after upgrading GNOME if locked before upgrade

[Debian Bug Tracking System]

Processing control commands:

> clone 789118 -2
Bug #789118 [gdm3] Cannot unlock screen after upgrading GNOME if locked before 
upgrade
Bug 789118 cloned as bug 853018
> retitle 789118 Cannot unlock screen after upgrading: Type of message, 
> '(sssb)', does not match expected type '(sssbb)'
Bug #789118 [gdm3] Cannot unlock screen after upgrading GNOME if locked before 
upgrade
Changed Bug title to 'Cannot unlock screen after upgrading: Type of message, 
'(sssb)', does not match expected type '(sssbb)'' from 'Cannot unlock 
screen after upgrading GNOME if locked before upgrade'.
> retitle -2 Cannot unlock screen after upgrading: Error: can't convert 
> this._frame to an integer
Bug #853018 [gdm3] Cannot unlock screen after upgrading GNOME if locked before 
upgrade
Changed Bug title to 'Cannot unlock screen after upgrading: Error: can't 
convert this._frame to an integer' from 'Cannot unlock screen after upgrading 
GNOME if locked before upgrade'.
> reassign -2 gnome-shell 3.14.4-1
Bug #853018 [gdm3] Cannot unlock screen after upgrading: Error: can't convert 
this._frame to an integer
Bug reassigned from package 'gdm3' to 'gnome-shell'.
No longer marked as found in versions gdm3/3.14.2-2.
Ignoring request to alter fixed versions of bug #853018 to the same values 
previously set
Bug #853018 [gnome-shell] Cannot unlock screen after upgrading: Error: can't 
convert this._frame to an integer
Marked as found in versions gnome-shell/3.14.4-1.

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

Bug#853017: bitlbee: FTBFS on every autobuilder: dh_testroot: You must run this as root (or use fakeroot).

[Wilmer van der Gaast]

Yeah already preparing a fix. Turns out the fix from 3.4-1.1 was a
different fix from the one posted by the NMU'er on the bug. :-(

Bug#853017: bitlbee: FTBFS on every autobuilder: dh_testroot: You must run this as root (or use fakeroot).

[Santiago Vila]

Package: src:bitlbee
Version: 3.5-1.1
Severity: serious
Tags: patch

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh_testdir
mkdir -p debian/build-native
ROOT=$PWD; cd debian/build-native; BITLBEE_VERSION="3.5-1.1" 
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" LDFLAGS="-Wl,-z,relro" $ROOT/configure --debug=0 
--prefix=/usr --etcdir=/etc/bitlbee --events=libevent --otr=plugin --skype=0 
BitlBee configure

configure script run from a different directory. Will create some symlinks...
Spoofing version number: 3.5-1.1

Architecture: Linux

Configuration done:
  Debugging disabled.
  AddressSanitizer (ASAN) disabled.

[... snipped ...]

/usr/bin/make -C doc/user-guide
make[1]: Entering directory '/<>/doc/user-guide'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/<>/doc/user-guide'
touch build-stamp
dh_testdir
dh_testroot
dh_testroot: You must run this as root (or use fakeroot).
debian/rules:77: recipe for target 'install' failed
make: *** [install] Error 255
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This happens because the build-* targets depend on their binary-* counterparts,
but this should never be the case, because they are invoked as a normal user by
either "dpkg-buildpackage -A" or "dpkg-buildpackage -B", so we are not root yet
to execute the binary-targets.

Suggested fix: There was already a working build target, just make the two
additional build-* targets to depend on it.

Trivial (but untested) patch follows. Please ensure that the package is 
buildable
with both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" before uploading 
again.

Thanks.

--- a/debian/rules
+++ b/debian/rules
@@ -41,8 +41,8 @@ CONFIGURE_OVERRIDES:=CPPFLAGS="$(CPPFLAGS)" 
CFLAGS="$(CFLAGS)" LDFLAGS="$(LDFLAG
 
 HAS_DH_SYSTEMD:=$(shell dpkg-query -W -f='$${Status}' dh-systemd 2>/dev/null | 
grep -c "ok installed")
 # https://bugs.debian.org/821967
-build-indep: binary-indep
-build-arch: binary-arch
+build-indep: build
+build-arch: build
 
 build: build-stamp
 build-stamp:

Processed: user debian...@lists.debian.org, usertagging 822138, affects 822138, found 707903 in 1.1.0-10.2 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 822138 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
> affects 822138 + libqpidcommon2 libqpid-perl qpidd
Bug #822138 [qpid-cpp] Boost 1.55 to be removed; your attention required
Added indication that 822138 affects libqpidcommon2, libqpid-perl, and qpidd
> found 707903 1.1.0-10.2
Bug #707903 [drgeo] drgeo: please migrate to guile-2.0
Bug #745996 [drgeo] drgeo: please migrate to guile-2.0
Marked as found in versions drgeo/1.1.0-10.2.
Marked as found in versions drgeo/1.1.0-10.2.
> found 707852 1.7-2
Bug #707852 [kabikaboo] kabikaboo: depends on python-gtkspell which is going 
away
Marked as found in versions kabikaboo/1.7-2.
> usertags 842524 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 842524 + libghc-wreq-doc
Bug #842524 [libghc-wreq-dev] libghc-wreq-dev: fails to build from source
Added indication that 842524 affects libghc-wreq-doc
> usertags 840151 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 840151 + libswiften-dev
Bug #840151 [swift-im] swift-im: FTBFS on i386: Qt wants this to be built with 
-fPIC
Added indication that 840151 affects libswiften-dev
> affects 811672 + libqtgui4-perl libqtnetwork4-perl libqttest4-perl 
> libqtxml4-perl
Bug #811672 [qt4-perl] FTBFS with GCC 6: cannot convert x to y
Added indication that 811672 affects libqtgui4-perl, libqtnetwork4-perl, 
libqttest4-perl, and libqtxml4-perl
> usertags 838137 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
> usertags 788032 piuparts
There were no usertags set.
Usertags are now: piuparts.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
707852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707852
707903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707903
745996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745996
788032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788032
811672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811672
822138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822138
840151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840151
842524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 824442

[Debian Bug Tracking System]

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

> tags 824442 + upstream
Bug #824442 [src:glibc]  and  conflict needs to be 
resolved
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: even stops apt

[Debian Bug Tracking System]

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

> severity 853016 grave
Bug #853016 [nodm] warn user all his work will be lost
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Processed: bug 849652 is forwarded to https://github.com/joke2k/faker/issues/454

[Debian Bug Tracking System]

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

> forwarded 849652 https://github.com/joke2k/faker/issues/454
Bug #849652 [src:faker] faker: FTBFS on 32-bit: ValueError: timestamp out of 
range for platform time_t
Set Bug forwarded-to-address to 'https://github.com/joke2k/faker/issues/454'.
> thanks
Stopping processing here.

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

Bug#846679: NMU diff

[Steve McIntyre]

Simple fix for build failure is to add --no-dynamic-linker to the
linker command lines. Here's the NMU diff; this is in incoming now...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"You can't barbecue lettuce!" -- Ellie Crane
diff -Nru syslinux-6.03+dfsg/debian/changelog 
syslinux-6.03+dfsg/debian/changelog
--- syslinux-6.03+dfsg/debian/changelog 2016-06-18 13:49:54.0 +
+++ syslinux-6.03+dfsg/debian/changelog 2017-01-28 18:39:54.0 +
@@ -1,3 +1,10 @@
+syslinux (3:6.03+dfsg-14.1) unstable; urgency=medium
+
+  * NMU
+  * Add --no-dynamic-linker to link lines, Closes: #846679
+
+ -- Steve McIntyre <93...@debian.org>  Sat, 28 Jan 2017 18:39:54 +
+
 syslinux (3:6.03+dfsg-14) unstable; urgency=medium
 
   * QA upload.
diff -Nru 
syslinux-6.03+dfsg/debian/patches/0014_fix_ftbfs_no_dynamic_linker.patch 
syslinux-6.03+dfsg/debian/patches/0014_fix_ftbfs_no_dynamic_linker.patch
--- syslinux-6.03+dfsg/debian/patches/0014_fix_ftbfs_no_dynamic_linker.patch
1970-01-01 00:00:00.0 +
+++ syslinux-6.03+dfsg/debian/patches/0014_fix_ftbfs_no_dynamic_linker.patch
2017-01-28 18:39:54.0 +
@@ -0,0 +1,13 @@
+Fix for https://bugs.debian.org/846679 : syslinux: FTBFS: ld:
+ldlinux.elf: Not enough room for program headers, try linking with -N
+--- a/core/Makefile2017-01-28 18:33:22.750959519 +
 b/core/Makefile2017-01-28 18:27:47.387981830 +
+@@ -165,7 +165,7 @@
+ 
+ %.elf: %.o $(LIBDEP) $(LDSCRIPT) $(AUXLIBS)
+   $(LD) $(LDFLAGS) -Bsymbolic $(LD_PIE) -E --hash-style=gnu -T 
$(LDSCRIPT) -M -o $@ $< \
+-  --start-group $(LIBS) $(subst $(*F).elf,lib$(*F).a,$@) 
--end-group \
++  --start-group $(LIBS) $(subst $(*F).elf,lib$(*F).a,$@) 
--end-group --no-dynamic-linker \
+   > $(@:.elf=.map)
+   $(OBJDUMP) -h $@ > $(@:.elf=.sec)
+   $(PERL) $(SRC)/lstadjust.pl $(@:.elf=.lsr) $(@:.elf=.sec) $(@:.elf=.lst)
diff -Nru syslinux-6.03+dfsg/debian/patches/series 
syslinux-6.03+dfsg/debian/patches/series
--- syslinux-6.03+dfsg/debian/patches/series2016-06-18 13:24:13.0 
+
+++ syslinux-6.03+dfsg/debian/patches/series2017-01-28 18:39:54.0 
+
@@ -11,3 +11,4 @@
 0011-bios-Dont-try-to-guess-the-section-alignment.patch
 0012-ldlinux-Fix-return-pointer-to-local-data.patch
 0013-extlinux-pull-in-sys_sysmacros.h-for-major_minor_makedev.patch
+0014_fix_ftbfs_no_dynamic_linker.patch

Bug#852988: Bug#852986: Bug#852988: wine: please do not build-depend on oss4-dev on Linux

[Matteo Cypriani]

> Le 28 janv. 2017 à 13:04, Simon McVittie  a écrit :
> 
> Control: found 852988 1.8.6-1
> 
>> On Sat, 28 Jan 2017 at 17:57:35 +, Simon McVittie wrote:
>> This package build-depends on oss4-dev, which is built by RC-buggy source
>> package oss4.
> 
> Adjusting "found" metadata so this doesn't prevent wine/1.8.6-3 from
> migrating before the hard freeze.
> 
> I'd suggest waiting til that version has migrated before uploading.
> 
>S

Forwarding this to the right bug, for the record.

Bug#852767: marked as done (wordpress: 4.7.2 security release (CVE-2017-5610 CVE-2017-5611 CVE-2017-5612))

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 22:07:13 +
with message-id 
and subject line Bug#852767: fixed in wordpress 4.7.2+dfsg-1
has caused the Debian Bug report #852767,
regarding wordpress: 4.7.2 security release (CVE-2017-5610 CVE-2017-5611 
CVE-2017-5612)
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.)


-- 
852767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wordpress
Version: 4.7.1+dfsg-1
Severity: grave
Tags: security upstream fixed-upstream

Hi

A new wordpress release was announced, marked as security release.

Cf. http://www.openwall.com/lists/oss-security/2017/01/27/2 for the
CVE request for the three issues.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: wordpress
Source-Version: 4.7.2+dfsg-1

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated wordpress 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, 29 Jan 2017 08:22:44 +1100
Source: wordpress
Binary: wordpress wordpress-l10n wordpress-theme-twentysixteen 
wordpress-theme-twentyfifteen wordpress-theme-twentyseventeen
Architecture: source all
Version: 4.7.2+dfsg-1
Distribution: unstable
Urgency: high
Maintainer: Craig Small 
Changed-By: Craig Small 
Description:
 wordpress  - weblog manager
 wordpress-l10n - weblog manager - language files
 wordpress-theme-twentyfifteen - weblog manager - twentytfifteen theme files
 wordpress-theme-twentyseventeen - weblog manager - twentyseventeen theme files
 wordpress-theme-twentysixteen - weblog manager - twentysixteen theme files
Closes: 852767
Changes:
 wordpress (4.7.2+dfsg-1) unstable; urgency=high
 .
   *  New upstream release fixes 3 security issues Closes: #852767
  - CVE-2017-5610
The user interface for assigning taxonomy terms in Press This is
shown to users who do not have permissions to use it.
  - CVE-2017-5611
WP_Query is vulnerable to a SQL injection (SQLi)
  - CVE-2017-5612
XSS in the posts list table
Checksums-Sha1:
 7e070ca21294e15a7ad8450dbe1386d42a629f27 2539 wordpress_4.7.2+dfsg-1.dsc
 d72547978a92d2629b02ff365bb0946525c994fc 6137000 
wordpress_4.7.2+dfsg.orig.tar.xz
 5535963bbd19aa6ceac583d97f13a8cebd0a2b0e 6777332 
wordpress_4.7.2+dfsg-1.debian.tar.xz
 84daf68b40a8018b6fbb536ce7e70dfeadb6c55b 4382802 
wordpress-l10n_4.7.2+dfsg-1_all.deb
 648c8ad901c0b36befb8d04f1d21cc80332c9bfa 699592 
wordpress-theme-twentyfifteen_4.7.2+dfsg-1_all.deb
 43debe40af23c6669a96a3a23a4f92ba7bd45914 939326 
wordpress-theme-twentyseventeen_4.7.2+dfsg-1_all.deb
 204332c140e96be4c2cf489bbfd1a3d30571fd8f 588362 
wordpress-theme-twentysixteen_4.7.2+dfsg-1_all.deb
 260754b650c461e873d93e327ec5b61cb44abe28 3968852 wordpress_4.7.2+dfsg-1_all.deb
 e173a8fdd69286a20738c8fcd8c7c524e24403eb 6271 
wordpress_4.7.2+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 17d417489d84aed7293426b3151dd01e4e13cff1c25b09c758c61108827280b1 2539 
wordpress_4.7.2+dfsg-1.dsc
 4803e59e54c47a0324c79fc44ab868c1ff71756ce73dc45c37b3303c3af07714 6137000 
wordpress_4.7.2+dfsg.orig.tar.xz
 4ad9cc6f64ba2ffcbc2f55f535b1e51acdb19bea21a6b81ba56ce94f5517f98e 6777332 
wordpress_4.7.2+dfsg-1.debian.tar.xz
 c28180b1448c8c24a6b86f63be30d39d64cce1d9271e51f02187177e249ba8c1 4382802 
wordpress-l10n_4.7.2+dfsg-1_all.deb
 f3128513019a5239f0b53d0c9a6cfd76b0fb7b63a7800e7e757d28cd230fc898 699592 
wordpress-theme-twentyfifteen_4.7.2+dfsg-1_all.deb
 20b3b2e34acca79700c7ff3c695f8e6ae6a831438e390f4aa39fa6ee389c1c09 939326 
wordpress-theme-twentyseventeen_4.7.2+dfsg-1_all.deb
 823bbb7d589d4de223013d5aa082203f4059bb8bbd55b183720658a6bf53e24d 588362 
wordpress-theme-twentysixteen_4.7.2+dfsg-1_all.deb
 11407af5870054e2511ba3e5e11bbb13bad4c8c9c17a9bc08b72e4013f541f1d 3968852 
wordpress_4.7.2+dfsg-1_all.deb
 89bf1463c87045823aaa4ca9ef5e2c7a3a52b0b625f02e503d32719ce6aaf2ae 6271 

Bug#852853: marked as done (libwww-curl-perl: FTBFS (Cannot find curl.h))

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 21:35:54 +
with message-id 
and subject line Bug#852853: fixed in libwww-curl-perl 4.17-4
has caused the Debian Bug report #852853,
regarding libwww-curl-perl: FTBFS (Cannot find curl.h)
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.)


-- 
852853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libwww-curl-perl
Version: 4.17-3
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch
   dh_testdir -a
   dh_update_autotools_config -a
   dh_auto_configure -a
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
-Wl,-z,now"
Locating required external dependency bin:curl-config... found at 
/usr/bin/curl-config.
The version is libcurl 7.52.1
Cannot find curl.h - cannot build constants files  - see Makefile.PL at 
Makefile.PL line 96.
dh_auto_configure: perl -I. Makefile.PL INSTALLDIRS=vendor OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 LD=x86_64-linux-gnu-gcc 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now returned exit code 2
debian/rules:6: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


It also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libwww-curl-perl.html

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: libwww-curl-perl
Source-Version: 4.17-4

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libwww-curl-perl 
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, 28 Jan 2017 22:13:04 +0100
Source: libwww-curl-perl
Binary: libwww-curl-perl
Architecture: source
Version: 4.17-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 852853
Description: 
 libwww-curl-perl - Perl bindings to libcurl
Changes:
 libwww-curl-perl (4.17-4) unstable; urgency=medium
 .
   * Add patch to add curl's new multiarch include path to Makefile.PL.
 Thanks to Santiago Vila for the bug report. (Closes: #852853)
Checksums-Sha1: 
 8b854f8645d2742754603668fc48f8a37194cdc6 2385 libwww-curl-perl_4.17-4.dsc
 8130f2134a1c1db12d067762e3d0962522257ebb 13524 
libwww-curl-perl_4.17-4.debian.tar.xz
Checksums-Sha256: 
 bd44ee3675a41d4a1313877da598001e3163da92dfbb6bb5b323644ad83102ad 2385 
libwww-curl-perl_4.17-4.dsc
 c1bb07da90a652697839b964fda0b4a9ebc391f8a396fcfc32a600453281b68c 13524 
libwww-curl-perl_4.17-4.debian.tar.xz
Files: 
 327102e0fe9daf798434f489d0b2157e 2385 perl optional libwww-curl-perl_4.17-4.dsc
 359ee2ad76276748cdbf8f43b15efe82 13524 perl optional 
libwww-curl-perl_4.17-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAliNCdlfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaYfxAAphA76Na5bmrThf39bCRh2k3x6OVafcrCGqlPszlF4YvnMb+ER9TwIpAn

Bug#852082: closed by Jaromír Mikeš <mira.mi...@seznam.cz> (Bug#852082: fixed in gwc 0.21.19~dfsg0-7)

[Christian Grigis]

Hello,

Excellent, thank you James and Jaromír for the very quick response!

Best regards,

-Christian

Bug#853008: mysql-server-5.7: purge could delete mariadb-server files with inadequate warning

[Julian Gilbey]

Package: mysql-server-5.7
Version: 5.7.16-2
Severity: serious

Hello!

I'm really confused by the change in the postrm introduced in response
to LP: #1602945, and I simply do not understand the rationale of the
original bug report, and the comment there (and in the git commit log)
that "Remove the check on the server binary, since it shouldn't be
possible for another package to own that file anyway" is clearly
incorrect: during a postrm remove|purge run, if that file exists -
which it may well do, it will certainly belong to a different package,
such as mysql-server-5.8 or mariadb-server-10.1.

Regarding upgrading, I have upgraded from mysql-5.6 to mariadb-10.0
with no noticeable problems whatsoever.  I have done a file comparison
looking for differences between /var/lib/mysql following this
mysql->mariadb conversion and a clean mariadb installation, and the
only ones I could see are:

mysql/ndb_binlog_index.*
mysql/slave_master_info.*
mysql/slave_relay_log_info.*
mysql/slave_worker_info.*
auto.cnf

If it is really the case the mariadb needs a different set of files
from mysql because of incompatibilities, then they should not share
the same /var/lib/mysql or it should be addressed in some other way:
mariadb could use /var/lib/mariadb instead, for instance, or the
mariadb installation could run some "clean up old /var/lib/mysql
directory from mysql instance" (which I think it already does).

So by removing the check on the existence of /usr/sbin/mysqld, you
leave sysadmins with the potential to inadvertantly wipe their entire
running mysql instance's database, for example if they purge an old
mysql-server-5.7 after installing mysql-server-5.8 at some point in
the future!

So as long as the various mysql/mariadb servers share the
/var/lib/mysql directory, the check for /usr/sbin/mysqld must be
reinstated: I cannot think of any situation in which rm -rf
/var/lib/mysql would be desired if /usr/sbin/mysqld is present, as
this means that there is some other package with responsibility for
/var/lib/mysql installed, and therefore this would fail the Debian
policy directive of not interferiyng with other packages' data.  (And
that is why I have labelled this bug as severity "serious".)  If a
sysadmin really wants to delete the directory in this situation, they
are welcome to do so manually.

The patch for this is simple: simply revert commit
554ecf472109f2b2e2fdfa0aaa0302cf2247ac1e

This would reopen the LP bug report, and I would ask the original
reporter there to explain the circumstances in which there are
problems, so that those can be addressed appropriately.

In addition, the current postrm_remove_databases debconf
question should be enhanced to explicitly mention mariadb.  I would
also suggest being even more explicit: instead of "the data should be
kept", say "do NOT remove the databases, and say NO to this question."

Best wishes,

   Julian

Bug#853006: qemu: CVE-2016-9602: 9p: virtfs allows guest to access host filesystem

[Salvatore Bonaccorso]

Source: qemu
Version: 1:2.8+dfsg-1
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for qemu.

Rationale: I'm raising the issue for now as grave severity, since a
privileged user inside guest could use this flaw to access host file
system beyond the shared folder and potentially escalating their
privileges on a host. But note as well, that the original proposed
patch is not fixing the issue, so upstream is still working on a
fix[1].

CVE-2016-9602[0]:
9p: virtfs allows guest to access host filesystem

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-9602
[1] http://www.openwall.com/lists/oss-security/2017/01/17/14
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1413929

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#825608: libnet-hiveminder-perl is marked for autoremoval from testing

[gregor herrmann]

On Sat, 28 Jan 2017 21:07:14 +0100, Axel Beckert wrote:

> > Hrm, that bug is marked as pending since beginning of November, but
> > there doesn't seem to have been an upload fixing that.

> Yes: According to the current UNRELEASED changelog entry:
> 
>   TODO:
>   according to https://rt.cpan.org/Ticket/Display.html?id=112231#txn-1681043
>   the patch for #825608 is wrong.
> 
> Sounds like a reason. :-)

And the pending tag was removed a 21 minutes after setting it :)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Domenica Vernossa: Figlio a Meta


signature.asc
Description: Digital Signature

Bug#852767: wordpress: 4.7.2 security release

[Salvatore Bonaccorso]

Control: retitle -1 wordpress: 4.7.2 security release (CVE-2017-5610 
CVE-2017-5611 CVE-2017-5612)

On Fri, Jan 27, 2017 at 07:15:10AM +0100, Salvatore Bonaccorso wrote:
> Source: wordpress
> Version: 4.7.1+dfsg-1
> Severity: grave
> Tags: security upstream fixed-upstream
> 
> Hi
> 
> A new wordpress release was announced, marked as security release.
> 
> Cf. http://www.openwall.com/lists/oss-security/2017/01/27/2 for the
> CVE request for the three issues.

CVE's have been assigned for those now:


> [] 1/ The user interface for assigning taxonomy terms in Press This is shown 
> to
> users who do not have permissions to use it. Reported by David Herrera of 
> Alley
> Interactive.
> https://github.com/WordPress/WordPress/commit/21264a31e0849e6ff793a06a17de877dd88ea454

Use CVE-2017-5610.


> [] 2/ WP_Query is vulnerable to a SQL injection (SQLi) when passing unsafe 
> data.
> WordPress core is not directly vulnerable to this issue, but we've added
> hardening to prevent plugins and themes from accidentally causing a
> vulnerability. Reported by Mo Jangda (batmoo).
> https://github.com/WordPress/WordPress/commit/85384297a6094e27e417eac56d24267054cb

Use CVE-2017-5611.


> [] 3/ A cross-site scripting (XSS) vulnerability was discovered in the posts 
> list
> table. Reported by Ian Dunn of the WordPress Security Team.
> https://github.com/WordPress/WordPress/commit/4482f9207027de8f36630737ae085110896ea849

Use CVE-2017-5612.

Cf. http://www.openwall.com/lists/oss-security/2017/01/28/5

Regards,
Salvatore

Processed: Re: Bug#852767: wordpress: 4.7.2 security release

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 wordpress: 4.7.2 security release (CVE-2017-5610 CVE-2017-5611 
> CVE-2017-5612)
Bug #852767 [src:wordpress] wordpress: 4.7.2 security release
Changed Bug title to 'wordpress: 4.7.2 security release (CVE-2017-5610 
CVE-2017-5611 CVE-2017-5612)' from 'wordpress: 4.7.2 security release'.

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

Bug#853004: security: javascript in the book can access files on the computer using XMLHttpRequest?

[Antoine Beaupre]

Package: calibre
Version: 2.71.0+dfsg-1
Severity: critical
File: /usr/bin/ebook-viewer
Tags: security

Hi,

Someone pointed me to this note in the 2.75.1 changelog:

E-book viewer: Prevent javascript in the book from accessing files
on the computer using XMLHttpRequest.

The ticket link (#1651728) is dead so I don't have extra details for
this.

This does seem like a security issue. Considering how little followup
is done by upstream on security issues, I suspect this is not properly
documented anywhere either.

So this is the first step in opening up an investigation about this.

The next step is to figure out which versions are affected and the
severity of this bug.

Someone should also request a CVE at the oss-security mailing list
once this is clarified.

It seems to me we should review the upstream changelog more thoroughly
when a new version is packaged. This way we would have found out about
this issue, which probably affect Debian users already.

A.

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

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

Versions of packages calibre depends on:
ii  calibre-bin  2.75.1+dfsg-1
ii  fonts-liberation 1:1.07.4-2
ii  imagemagick  8:6.9.7.0+dfsg-2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.6.6+dfsg-1
ii  libjs-mathjax2.7.0-1
ii  poppler-utils0.48.0-2
ii  python-apsw  3.13.0-r1-1
ii  python-beautifulsoup 3.2.1-1
ii  python-chardet   2.3.0-2
ii  python-cherrypy3 3.5.0-2
ii  python-cssselect 1.0.0-1
ii  python-cssutils  1.0-4.1
ii  python-dateutil  2.5.3-2
ii  python-dbus  1.2.4-1
ii  python-feedparser5.1.3-3
ii  python-imaging   3.4.2-1
ii  python-lxml  3.7.1-1
ii  python-markdown  2.6.7-1
ii  python-mechanize 1:0.2.5-3
ii  python-netifaces 0.10.4-0.1+b2
ii  python-pil   3.4.2-1
ii  python-pkg-resources 32.3.1-1
ii  python-pyparsing 2.1.10+dfsg1-1
ii  python-pyqt5 5.7+dfsg-4
ii  python-pyqt5.qtsvg   5.7+dfsg-4
ii  python-pyqt5.qtwebkit5.7+dfsg-4
ii  python-routes2.3.1-2
ii  python2.72.7.13-1
ii  xdg-utils1.1.1-1

Versions of packages calibre recommends:
ii  python-dnspython  1.15.0-1

calibre suggests no packages.

-- no debconf information

Bug#852983: marked as done (allegro4.4: please do not build-depend on oss4-dev on Linux)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 20:48:51 +
with message-id 
and subject line Bug#852983: fixed in allegro4.4 2:4.4.2-10
has caused the Debian Bug report #852983,
regarding allegro4.4: please do not build-depend on oss4-dev on Linux
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.)


-- 
852983: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: allegro4.4
Version: 2:4.4.2-9
Severity: serious
Justification: release team consensus

allegro4.4 build-depends on oss4-dev, which is built by RC-buggy source
package oss4.

I discussed this with some release team members and their opinion is that
oss4 should only be used on non-Linux architectures: on Linux, we should be
using ALSA, either directly or via intermediaries like PulseAudio.
Please restrict the build-dependency to oss4-dev [kfreebsd-any] or possibly
oss4-dev [kfreebsd-any hurd-any], and set the CMake options so OSS is only
requested on those architectures, similar to what is done in
vlc (>= 2.2.0~pre3-1).

Regards,
smcv
helping the Cambridge BSP

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

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: allegro4.4
Source-Version: 2:4.4.2-10

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

Debian distribution maintenance software
pp.
Andreas Rönnquist  (supplier of updated allegro4.4 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: Sat, 28 Jan 2017 19:42:25 +0100
Source: allegro4.4
Binary: liballegro4.4 liballegro4-dev allegro4-doc liballeggl4.4 
liballeggl4-dev libjpgalleg4.4 libjpgalleg4-dev libloadpng4.4 libloadpng4-dev 
liblogg4.4 liblogg4-dev
Architecture: source all amd64
Version: 2:4.4.2-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Andreas Rönnquist 
Description:
 allegro4-doc - documentation for the Allegro library
 liballeggl4-dev - development files for the allegrogl library
 liballeggl4.4 - library to mix OpenGL graphics with Allegro routines
 liballegro4-dev - development files for the Allegro library
 liballegro4.4 - portable library for cross-platform game and multimedia 
developme
 libjpgalleg4-dev - development files for the JPG loading addon for Allegro 4
 libjpgalleg4.4 - JPG loading addon for Allegro 4
 libloadpng4-dev - development files for the PNG loading addon for Allegro 4
 libloadpng4.4 - PNG loading addon for Allegro 4
 liblogg4-dev - development files for the OGG loading addon for Allegro 4
 liblogg4.4 - OGG loading addon for Allegro 4
Closes: 852983
Changes:
 allegro4.4 (2:4.4.2-10) unstable; urgency=medium
 .
   * Remove build-depend on oss4-dev on Linux, use ALSA instead
 (Closes: #852983)
Checksums-Sha1:
 fcffbde3eab8952802b1e8f6326e66a8b2302dbe 2827 allegro4.4_4.4.2-10.dsc
 3aa18269bfc07015d8a06926f7015f5c7601930d 58036 
allegro4.4_4.4.2-10.debian.tar.xz
 63d8a5125d25e7c145110e71320f8b66dbb12b33 1649280 allegro4-doc_4.4.2-10_all.deb
 07f0c49019447563934faf8b02377ca2760ee818 13184 
allegro4.4_4.4.2-10_amd64.buildinfo
 ea7c61986ed4bf6cff772993be759c6e342790d8 138794 
liballeggl4-dev_4.4.2-10_amd64.deb
 88b40c43eac85e4fd55aa087fa3e4c4dc2d2b877 648990 
liballeggl4.4-dbgsym_4.4.2-10_amd64.deb
 b8a200b8b38366eb089a9b6645f2abcbbe095a4e 191116 
liballeggl4.4_4.4.2-10_amd64.deb
 7b2db97d51571c6c8a80741b6aaeb997d22d5213 779378 
liballegro4-dev-dbgsym_4.4.2-10_amd64.deb
 7d316c155af159902108a5b962de4f973a4d7436 295464 
liballegro4-dev_4.4.2-10_amd64.deb
 

Bug#852213: marked as done (tigervnc: CVE-2017-5581: Buffer overflow in ModifiablePixelBuffer::fillRect)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 20:50:11 +
with message-id 
and subject line Bug#852213: fixed in tigervnc 1.7.0+dfsg-3
has caused the Debian Bug report #852213,
regarding tigervnc: CVE-2017-5581: Buffer overflow in 
ModifiablePixelBuffer::fillRect
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.)


-- 
852213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tigervnc
Version: 1.7.0+dfsg-2
Severity: grave
Tags: patch security upstream
Justification: user security hole
Forwarded: https://github.com/TigerVNC/tigervnc/pull/399

Hi

Cf. http://www.openwall.com/lists/oss-security/2017/01/22/1 where as
well a CVE was requested for this issue.

Upstream bug: https://github.com/TigerVNC/tigervnc/pull/399
Commit: 
https://github.com/TigerVNC/tigervnc/commit/18c020124ff1b2441f714da2017f63dba50720ba

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: tigervnc
Source-Version: 1.7.0+dfsg-3

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

Debian distribution maintenance software
pp.
Ola Lundqvist  (supplier of updated tigervnc 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: Sat, 28 Jan 2017 21:08:53 +0100
Source: tigervnc
Binary: tigervnc-common tigervnc-scraping-server tigervnc-standalone-server 
tigervnc-xorg-extension tigervnc-viewer
Architecture: source amd64
Version: 1.7.0+dfsg-3
Distribution: unstable
Urgency: high
Maintainer: TigerVNC Packaging Team 
Changed-By: Ola Lundqvist 
Description:
 tigervnc-common - Virtual network computing; Common software needed by servers
 tigervnc-scraping-server - Virtual network computing server performing X 
screen scraping
 tigervnc-standalone-server - Standalone virtual network computing server
 tigervnc-viewer - Virtual network computing client for X
 tigervnc-xorg-extension - Virtual network computing X server extension
Closes: 852213
Changes:
 tigervnc (1.7.0+dfsg-3) unstable; urgency=high
 .
   [ Salvatore Bonaccorso ]
   * Fix buffer overflow in ModifiablePixelBuffer::fillRect (CVE-2017-5581)
 (Closes: #852213)
 .
   [ Joachim Falk ]
   * Shut up lintian manpage-has-errors-from-man for vnc.conf.5x.gz
 Basically the default value for $sslAutoGenCertCommand is too large
 to fit into a 80 column manpage output. Broke that into multiple
 lines.
Checksums-Sha1:
 012d0b8ccf3ccc20820dc3d6f2a7091c7b92f5b6 4451 tigervnc_1.7.0+dfsg-3.dsc
 6a336ce883bbec2eb5474600662c1407e428b1ae 53040 
tigervnc_1.7.0+dfsg-3.debian.tar.xz
 be6498f187f77a3ab8a4771da87c847674d22bc7 235770 
tigervnc-common-dbgsym_1.7.0+dfsg-3_amd64.deb
 14bf08d545c6bbd6ca598e0c83b7e62f23827f82 66216 
tigervnc-common_1.7.0+dfsg-3_amd64.deb
 8760753e575877573b31955df8cc8c7d35a772fb 1152538 
tigervnc-scraping-server-dbgsym_1.7.0+dfsg-3_amd64.deb
 176b1427558d35d32d4ca146cb5e3bd42ef5b6a1 187910 
tigervnc-scraping-server_1.7.0+dfsg-3_amd64.deb
 f7e1282363c90aa4abe7f3cdcc850471da3114c9 5834048 
tigervnc-standalone-server-dbgsym_1.7.0+dfsg-3_amd64.deb
 0aa6205c1d54b2e03a18af08c0c8a8552d067a80 994916 
tigervnc-standalone-server_1.7.0+dfsg-3_amd64.deb
 1e15547311ba92e1494344ad84efadf2e6f9217d 1008636 
tigervnc-viewer-dbgsym_1.7.0+dfsg-3_amd64.deb
 e3e5a78dbc0081db3e97fc5afd2d2d1d3e062e47 166962 
tigervnc-viewer_1.7.0+dfsg-3_amd64.deb
 5ab1f27a3ab66b8171711cb6862db4db298d09de 1309476 
tigervnc-xorg-extension-dbgsym_1.7.0+dfsg-3_amd64.deb
 47a8328312037c32a4d033b4f6d83b6f03b9dd81 196994 
tigervnc-xorg-extension_1.7.0+dfsg-3_amd64.deb
 2c5d00f55078647a0e020529bcc1042c086f869f 14158 
tigervnc_1.7.0+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 9a9628412d2ff846422f247c4e82884e0531917abf0a48aed5967e5ba8e1 4451 
tigervnc_1.7.0+dfsg-3.dsc
 476052ba1080134d5aef82b1c0d0a4a06ecc1ae723ea567ab20b4a53027bc302 53040 
tigervnc_1.7.0+dfsg-3.debian.tar.xz
 3da39625f0bb0a9a635d65340e9dbdcdb5c126e4f9b9d15809faf30a56e1df2f 235770 

Bug#852213: [Pkg-tigervnc-devel] Bug#852213: Bug#852213: tigervnc: diff for NMU version 1.7.0+dfsg-2.1

[Ola Lundqvist]

Sure will do that.

// Ola

On 28 January 2017 at 21:18, Salvatore Bonaccorso  wrote:
> Hi Ola,
>
> On Sat, Jan 28, 2017 at 09:10:43PM +0100, Ola Lundqvist wrote:
>> Hi
>>
>> Thank you. I'll make a "real" upload now instead. Thank you for the patch.
>
> Thank you that's fine! Can you then please make as well an unblock
> request for the release team? The fix should go to stretch, but will
> not automatically anymore due to the freeze approeaching in some days.
>
> Regards,
> Salvatore
>
> ___
> Pkg-tigervnc-devel mailing list
> pkg-tigervnc-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tigervnc-devel



-- 
 - Ola Lundqvist ---
/  o...@debian.org Folkebogatan 26  \
|  o...@inguza.com  654 68 KARLSTAD  |
|  http://inguza.com/  +46 (0)70-332 1551   |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---

Bug#852959: [pkg-go] Bug#852959: prometheus FTBFS on armhf: github.com/prometheus/prometheus/storage/local fails

[Martín Ferrari]

On 28/01/17 16:24, Martín Ferrari wrote:
>> and the machines where prometheus failed have 4 GB RAM.
>
> abel too...

Now it fails on abel too.. I guess it was always too close to the limit,
and anything else running killed it.

>> "2680815616 in use", that is 2.6 GB.
>>
>> You have only 3 GB address space in userspace,
>> and I'd guess that is the limit you hit.
>
> possibly.
>
>> Is this test expected to use huge amounts of memory?
>
> I will re-run the tests with /usr/bin/time on abel and see how much
> memory do they take.

Time says the maximum resident size was 2184076 KB, it is a bit less on
amd64 (with tests passing).


Now I don't know what to do.. If I upload a fix (disabling the test), it
will be too late for Stretch.

-- 
Martín Ferrari (Tincho)

Bug#852213: [Pkg-tigervnc-devel] Bug#852213: tigervnc: diff for NMU version 1.7.0+dfsg-2.1

[Salvatore Bonaccorso]

Hi Ola,

On Sat, Jan 28, 2017 at 09:10:43PM +0100, Ola Lundqvist wrote:
> Hi
> 
> Thank you. I'll make a "real" upload now instead. Thank you for the patch.

Thank you that's fine! Can you then please make as well an unblock
request for the release team? The fix should go to stretch, but will
not automatically anymore due to the freeze approeaching in some days.

Regards,
Salvatore

Bug#852213: [Pkg-tigervnc-devel] Bug#852213: tigervnc: diff for NMU version 1.7.0+dfsg-2.1

[Ola Lundqvist]

Hi

Thank you. I'll make a "real" upload now instead. Thank you for the patch.

// Ola

On 28 January 2017 at 11:47, Salvatore Bonaccorso  wrote:
> Control: tags 852213 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for tigervnc (versioned as 1.7.0+dfsg-2.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
>
> Regards,
> Salvatore
>
> ___
> Pkg-tigervnc-devel mailing list
> pkg-tigervnc-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tigervnc-devel



-- 
 - Ola Lundqvist ---
/  o...@debian.org Folkebogatan 26  \
|  o...@inguza.com  654 68 KARLSTAD  |
|  http://inguza.com/  +46 (0)70-332 1551   |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---

Bug#825608: libnet-hiveminder-perl is marked for autoremoval from testing

[Axel Beckert]

Hi,

Debian testing autoremoval watch wrote:
> libnet-hiveminder-perl 0.08-2 is marked for autoremoval from testing on 
> 2017-01-29
> 
> It (build-)depends on packages with these RC bugs:
> 825608: libnet-jifty-perl: FTBFS: t/006-uploads.t failure

Hrm, that bug is marked as pending since beginning of November, but
there doesn't seem to have been an upload fixing that.

Any reason for that?

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

Bug#825608: libnet-hiveminder-perl is marked for autoremoval from testing

[Axel Beckert]

Axel Beckert wrote:
> Debian testing autoremoval watch wrote:
> > libnet-hiveminder-perl 0.08-2 is marked for autoremoval from testing on 
> > 2017-01-29
> > 
> > It (build-)depends on packages with these RC bugs:
> > 825608: libnet-jifty-perl: FTBFS: t/006-uploads.t failure
> 
> Hrm, that bug is marked as pending since beginning of November, but
> there doesn't seem to have been an upload fixing that.
> 
> Any reason for that?

Yes: According to the current UNRELEASED changelog entry:

  TODO:
  according to https://rt.cpan.org/Ticket/Display.html?id=112231#txn-1681043
  the patch for #825608 is wrong.

Sounds like a reason. :-)

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

Processed: tagging 852867

[Debian Bug Tracking System]

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

> tags 852867 + pending
Bug #852867 [icedove] icedove: debuild fails because mozilla build system 
requires SHELL env var set
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 832908

[Debian Bug Tracking System]

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

> tags 832908 + pending
Bug #832908 {Done: Laszlo Boszormenyi (GCS) } 
[mongodb-clients] mongodb: CVE-2016-6494: world-readable .dbshell history file
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 833087

[Debian Bug Tracking System]

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

> tags 833087 + pending
Bug #833087 [mongodb-server] bruteforcable challenge responses in unprotected 
logfile
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#852959: [pkg-go] Bug#852959: prometheus FTBFS on armhf: github.com/prometheus/prometheus/storage/local fails

[Martín Ferrari]

On 28/01/17 16:10, Adrian Bunk wrote:

> AFAIK the buildds are building one package at a time,

Uhm, don't know about that, but I many times I have experienced test
failures which are somehow timing-related on some buildds, failures I
can only reproduce with very high CPU contention.

> and the machines where prometheus failed have 4 GB RAM.

abel too...

> "2680815616 in use", that is 2.6 GB.
> 
> You have only 3 GB address space in userspace,
> and I'd guess that is the limit you hit.

possibly.

> Is this test expected to use huge amounts of memory?

I will re-run the tests with /usr/bin/time on abel and see how much
memory do they take.


-- 
Martín Ferrari (Tincho)

Processed: Bug#848230 marked as pending

[Debian Bug Tracking System]

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

> tag 848230 pending
Bug #848230 [python3-neovim-gui] /usr/bin/pynvim: crashes on startup ("Cannot 
add child handler")
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 851814

[Debian Bug Tracking System]

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

> # doesnt affect jessie as its only caused by very recent versions of sed
> tags 851814 + sid stretch
Bug #851814 {Done: Axel Beckert } [apt-build] apt-build: 
Broken postinst by less permissive sed
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

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

Bug#852959: [pkg-go] Bug#852959: prometheus FTBFS on armhf: github.com/prometheus/prometheus/storage/local fails

[Adrian Bunk]

On Sat, Jan 28, 2017 at 03:59:45PM -0300, Martín Ferrari wrote:
> On 28/01/17 11:58, Adrian Bunk wrote:
> > Source: prometheus
> > Version: 1.5.0+ds-1
> > Severity: serious
> > 
> > https://buildd.debian.org/status/fetch.php?pkg=prometheus=armhf=1.5.0%2Bds-1=1485604675=0
> 
> As it can be seen in the log:
> 
> runtime: out of memory: cannot allocate 4194304-byte block (2680815616
> in use)
> fatal error: out of memory
> 
> Yesterday I'd asked for a give back, since in the previous attempt the
> tests timed out. I can't reproduce this on the abel porterbox, and it
> seems to me like a problem of a very busy buildd more than any bug in
> the package.

AFAIK the buildds are building one package at a time,
and the machines where prometheus failed have 4 GB RAM.

"2680815616 in use", that is 2.6 GB.

You have only 3 GB address space in userspace,
and I'd guess that is the limit you hit.

Is this test expected to use huge amounts of memory?

cu
Adrian

-- 

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

Bug#852959: [pkg-go] Bug#852959: prometheus FTBFS on armhf: github.com/prometheus/prometheus/storage/local fails

[Martín Ferrari]

On 28/01/17 11:58, Adrian Bunk wrote:
> Source: prometheus
> Version: 1.5.0+ds-1
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=prometheus=armhf=1.5.0%2Bds-1=1485604675=0

As it can be seen in the log:

runtime: out of memory: cannot allocate 4194304-byte block (2680815616
in use)
fatal error: out of memory

Yesterday I'd asked for a give back, since in the previous attempt the
tests timed out. I can't reproduce this on the abel porterbox, and it
seems to me like a problem of a very busy buildd more than any bug in
the package.


-- 
Martín Ferrari (Tincho)

Bug#851021: marked as done (nikola: FTBFS: pkg_resources.DistributionNotFound: The 'olefile' distribution was not found and is required by Pillow)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 19:29:00 +0100
with message-id <20170128182900.ukty223iowhwk...@betterave.cristau.org>
and subject line Re: Bug#851021: nikola: FTBFS: 
pkg_resources.DistributionNotFound: The 'olefile' distribution was not found 
and is required by Pillow
has caused the Debian Bug report #851021,
regarding nikola: FTBFS: pkg_resources.DistributionNotFound: The 'olefile' 
distribution was not found and is required by Pillow
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ./debian/nikola.sh init -q debian/dpackaging_site
> Traceback (most recent call last):
>   File "/<>/debian/nikola/usr/bin/nikola", line 6, in 
> from pkg_resources import load_entry_point
>   File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
> 3019, in 
> @_call_aside
>   File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
> 3003, in _call_aside
> f(*args, **kwargs)
>   File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
> 3032, in _initialize_master_working_set
> working_set = WorkingSet._build_master()
>   File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
> 655, in _build_master
> ws.require(__requires__)
>   File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
> 963, in require
> needed = self.resolve(parse_requirements(requirements))
>   File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
> 849, in resolve
> raise DistributionNotFound(req, requirers)
> pkg_resources.DistributionNotFound: The 'olefile' distribution was not found 
> and is required by Pillow
> debian/rules:25: recipe for target 'override_dh_bash-completion' failed
> make[1]: *** [override_dh_bash-completion] Error 1

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

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
On Wed, Jan 11, 2017 at 19:50:10 +0100, Lucas Nussbaum wrote:

> Source: nikola
> Version: 7.6.4-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170111 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
from the followup it sounds like this was a bug in python-pil that was
fixed there.

Cheers,
Julien--- End Message ---

Bug#848927: mount: bad option.

[Steve McIntyre]

Control: tags -1 +moreinfo,unreprodible
Control: severity -1 normal

On Tue, Dec 20, 2016 at 01:20:29PM -0800, Ray Andrews wrote:
>Package: gparted
>Version: 0.25.0-1
>Severity: grave
>Justification: renders package unusable
>
>Dear Maintainer,
>
>*** Reporter, please consider answering these questions, where appropriate ***
>
>   * What led up to the situation?
>   * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
>gparted fails completely  with the message:
>
>"mount: bad option. Note that mmoving a mount "
>
>I noticed the identical bug searching with Google, but 
>didn't see that bug in the list that reportbug offered me.
>One of the bug reports said that it was due to 'udisks2' and 
>it was supposed to be fixed, but it is not.

Hi Ray,

I've just tried gparted locally and it seemed to work OK for me. Could
you give us more information about exactly what you did to trigger
this please?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"We're the technical experts.  We were hired so that management could
 ignore our recommendations and tell us how to do our jobs."  -- Mike Andrews

Processed (with 1 error): Re: Bug#848927: mount: bad option.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +moreinfo,unreprodible
Unknown tag/s: unreprodible.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid 
help security upstream pending sarge sarge-ignore experimental d-i confirmed 
ipv6 lfs fixed-in-experimental fixed-upstream l10n newcomer etch etch-ignore 
lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie 
jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore.

Bug #848927 [gparted] mount: bad option.
Ignoring request to alter tags of bug #848927 to the same tags previously set
> severity -1 normal
Bug #848927 [gparted] mount: bad option.
Severity set to 'normal' from 'grave'

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

Processed: Version tracking fix

[Debian Bug Tracking System]

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

> found 852988 1.8.6-1
Bug #852988 [src:wine] wine: please do not build-depend on oss4-dev on Linux
Ignoring request to alter found versions of bug #852988 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#852991: gnocchi: FTBFS (failing tests)

[Santiago Vila]

Package: src:gnocchi
Version: 3.0.0-2
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,sphinxdoc
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   dh_auto_build -i -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
python setup.py build --force
running build
running build_py

[... snipped ...]

 (datetime.datetime(2014, 1, 1, 
12, 0, tzinfo=),
  300,
  69),
 (datetime.datetime(2014, 1, 1, 
12, 10, tzinfo=),
  300,
  42)],
 : []}
actual= defaultdict(, {: [], : []})


==
FAIL: gnocchi.tests.test_storage.TestStorageDriver.test_updated_measures
gnocchi.tests.test_storage.TestStorageDriver.test_updated_measures
--
_StringException: Empty attachments:
  stderr
  stdout

Traceback (most recent call last):
  File "gnocchi/tests/base.py", line 55, in skip_if_not_implemented
return func(*args, **kwargs)
  File "gnocchi/tests/test_storage.py", line 325, in test_updated_measures
], self.storage.get_measures(self.metric))
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 350, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 435, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: !=:
reference = [(datetime.datetime(2014, 1, 1, 0, 0, tzinfo=), 
86400.0, 55.5),
 (datetime.datetime(2014, 1, 1, 12, 0, tzinfo=), 3600.0, 55.5),
 (datetime.datetime(2014, 1, 1, 12, 0, tzinfo=), 300.0, 69),
 (datetime.datetime(2014, 1, 1, 12, 5, tzinfo=), 300.0, 42.0)]
actual= []


--
Ran 304 tests in 55.760s

FAILED (failures=44, skipped=24)
debian/rules:44: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends, not necessarily the relevant part.

I've put several build logs here:

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

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

The bug should be reproducible with sbuild on a single CPU virtual machine.

Note: My build history is like this:

[...]
Status: successful  gnocchi_3.0.0-2_amd64-20170122T094410Z
Status: failed  gnocchi_3.0.0-2_amd64-20170126T170124Z
[...]

where every previous build was ok and now it always fail. Maybe some
build-dependency entered testing between 2017-01-22 and 2017-01-26
which is related to this failure.

Thanks.

Processed: Re: Bug#852988: wine: please do not build-depend on oss4-dev on Linux

[Debian Bug Tracking System]

Processing control commands:

> found 852988 1.8.6-1
Bug #852988 [src:wine] wine: please do not build-depend on oss4-dev on Linux
Marked as found in versions wine/1.8.6-1.

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

Bug#852986: Bug#852988: wine: please do not build-depend on oss4-dev on Linux

[Simon McVittie]

Control: found 852988 1.8.6-1

On Sat, 28 Jan 2017 at 17:57:35 +, Simon McVittie wrote:
> This package build-depends on oss4-dev, which is built by RC-buggy source
> package oss4.

Adjusting "found" metadata so this doesn't prevent wine/1.8.6-3 from
migrating before the hard freeze.

I'd suggest waiting til that version has migrated before uploading.

S

Bug#852988: wine: please do not build-depend on oss4-dev on Linux

[Simon McVittie]

Source: wine
Version: 1.8.6-3
Severity: serious
Justification: release team consensus

This package build-depends on oss4-dev, which is built by RC-buggy source
package oss4.

I discussed this with some release team members and their opinion is that
oss4 should only be used on non-Linux architectures: on Linux, we should be
using ALSA, either directly or via intermediaries like PulseAudio.
Please restrict the build-dependency to oss4-dev [kfreebsd-any] or possibly
oss4-dev [kfreebsd-any hurd-any], and if necessary set the configure options
so OSS is only requested on those architectures, similar to what is done in
vlc (>= 2.2.0~pre3-1).

Regards,
smcv
helping the Cambridge BSP

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

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

Bug#852989: wine-development: please do not build-depend on oss4-dev on Linux

[Simon McVittie]

Source: wine-development
Version: 2.0~rc2-1
Severity: serious
Justification: release team consensus

This package build-depends on oss4-dev, which is built by RC-buggy source
package oss4.

I discussed this with some release team members and their opinion is that
oss4 should only be used on non-Linux architectures: on Linux, we should be
using ALSA, either directly or via intermediaries like PulseAudio.
Please restrict the build-dependency to oss4-dev [kfreebsd-any] or possibly
oss4-dev [kfreebsd-any hurd-any], and if necessary set the configure options
so OSS is only requested on those architectures, similar to what is done in
vlc (>= 2.2.0~pre3-1).

Regards,
smcv
helping the Cambridge BSP

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

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

Bug#852742: python-oslo.middleware: CVE-2017-2592: CatchErrors leaks sensitive values in oslo.middleware

[Salvatore Bonaccorso]

Hi Thomas,

On Fri, Jan 27, 2017 at 04:57:09PM +0100, Thomas Goirand wrote:
> On 01/26/2017 10:11 PM, Salvatore Bonaccorso wrote:
> > Source: python-oslo.middleware
> > Version: 3.19.0-2
> > Severity: grave
> > Tags: security patch upstream
> > Forwarded: https://launchpad.net/bugs/1628031
> > 
> > Hi,
> > 
> > the following vulnerability was published for python-oslo.middleware.
> > 
> > CVE-2017-2592[0]:
> > CatchErrors leaks sensitive values in oslo.middleware
> > 
> > If you fix the vulnerability please also make sure to include the
> > CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> > 
> > For further information see:
> > 
> > [0] https://security-tracker.debian.org/tracker/CVE-2017-2592
> > [1] https://launchpad.net/bugs/1628031
> > 
> > Regards,
> > Salvatore
> 
> Hi Salvatore,
> 
> Thanks for the notification.
> 
> IMO this isn't a grave issue. To be able to read the logs, someone would
> need to have access to the server logs, meaning having privileged access
> to the server.
> 
> I have never the less uploaded the upstream patch to Sid, and asked for
> an unblock to the release team (with 5 days delay).

Thanks for the quick followup. Apparently the upload was not accepted,
cf. no trace of it in
https://tracker.debian.org/pkg/python-oslo.middleware . Can you please
recheck, and reupload? Already appreciated, since we should have the
fix in stretch.

Regards,
Salvatore

Bug#852984: audacious-plugins: please do not build-depend on oss4-dev on Linux

[Simon McVittie]

Source: audacious-plugins
Version: 3.7.2-2
Severity: serious
Justification: release team consensus

This package build-depends on oss4-dev, which is built by RC-buggy source
package oss4.

I discussed this with some release team members and their opinion is that
oss4 should only be used on non-Linux architectures: on Linux, we should be
using ALSA, either directly or via intermediaries like PulseAudio.
Please restrict the build-dependency to oss4-dev [kfreebsd-any] or possibly
oss4-dev [kfreebsd-any hurd-any], and if necessary set the configure options
so OSS is only requested on those architectures, similar to what is done in
vlc (>= 2.2.0~pre3-1).

Regards,
smcv
helping the Cambridge BSP

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

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

Bug#852983: allegro4.4: please do not build-depend on oss4-dev on Linux

[Simon McVittie]

Source: allegro4.4
Version: 2:4.4.2-9
Severity: serious
Justification: release team consensus

allegro4.4 build-depends on oss4-dev, which is built by RC-buggy source
package oss4.

I discussed this with some release team members and their opinion is that
oss4 should only be used on non-Linux architectures: on Linux, we should be
using ALSA, either directly or via intermediaries like PulseAudio.
Please restrict the build-dependency to oss4-dev [kfreebsd-any] or possibly
oss4-dev [kfreebsd-any hurd-any], and set the CMake options so OSS is only
requested on those architectures, similar to what is done in
vlc (>= 2.2.0~pre3-1).

Regards,
smcv
helping the Cambridge BSP

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

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

Bug#852985: gsequencer: please do not build-depend on oss4-dev on Linux

[Simon McVittie]

Source: gsequencer
Version: 0.7.122-1
Severity: serious
Justification: release team consensus

This package build-depends on oss4-dev, which is built by RC-buggy source
package oss4.

I discussed this with some release team members and their opinion is that
oss4 should only be used on non-Linux architectures: on Linux, we should be
using ALSA, either directly or via intermediaries like PulseAudio.
Please restrict the build-dependency to oss4-dev [kfreebsd-any] or possibly
oss4-dev [kfreebsd-any hurd-any], and set the configure options so OSS is
only requested on those architectures, similar to what is done in
vlc (>= 2.2.0~pre3-1).

Regards,
smcv
helping the Cambridge BSP

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

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

Bug#852986: qmmp: please do not build-depend on oss4-dev on Linux

[Simon McVittie]

Source: qmmp
Version: 1.1.6-1
Severity: serious
Justification: release team consensus

This package build-depends on oss4-dev, which is built by RC-buggy source
package oss4.

I discussed this with some release team members and their opinion is that
oss4 should only be used on non-Linux architectures: on Linux, we should be
using ALSA, either directly or via intermediaries like PulseAudio.
Please restrict the build-dependency to oss4-dev [kfreebsd-any] or possibly
oss4-dev [kfreebsd-any hurd-any], and if necessary set the CMake options
so OSS is only requested on those architectures, similar to what is done in
vlc (>= 2.2.0~pre3-1).

Regards,
smcv
helping the Cambridge BSP

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

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

Bug#852920: [Pkg-openssl-devel] Bug#852920: libnet-ssleay-perl: FTBFS: Test failures

[Kurt Roeckx]

On Sat, Jan 28, 2017 at 06:07:02PM +0100, gregor herrmann wrote:
> On Sat, 28 Jan 2017 16:35:44 +0100, Kurt Roeckx wrote:
> 
> > On Sat, Jan 28, 2017 at 04:02:02PM +0100, gregor herrmann wrote:
> > > Control: forwarded -1 
> > > https://rt.cpan.org/Public/Bug/Display.html?id=120006
> > 
> > I've just filed:
> > https://rt.cpan.org/Public/Bug/Display.html?id=120006
> 
> Is this a copypaste error?

Yes,

I meant:
https://github.com/openssl/openssl/issues/2313

A patch is being worked at at:
https://github.com/openssl/openssl/pull/2314


Kurt

Bug#852894: [Pkg-clamav-devel] Bug#852894: clamav: FTBFS: dh_install: missing files, aborting

[Scott Kitterman]

On Saturday, January 28, 2017 06:40:05 PM Reiner Herrmann wrote:
> On Sat, Jan 28, 2017 at 12:31:09PM -0500, Scott Kitterman wrote:
> > I think during pre-release freeze was not the best time to do this change?
> > How many other packages did you break and did you coordinate this with the
> > Release Team?
> 
> I agree, but you should ask this the curl maintainers. :)
> Looking at [0] it looks like some other packages are affected by that.
> 
> [0]
> https://udd.debian.org/bugs/bugs/bugs/?release=stretch_and_sid=ign
> rged=ign=ign=7=1=id=asc=1=1
> rred=1#results

Thanks for patch.  I wrongly assumed you were one of the curl maintainers.  
The release team is considering if the change should be reverted, so I'm going 
to hold off on this for the moment, but I appreciate you putting it together 
so quickly.

Scott K



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

Bug#852000: marked as done (oddjob-mkhomedir: fails to install: oddjobd: unrecognized service)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 17:49:55 +
with message-id 
and subject line Bug#852000: fixed in oddjob 0.34.3-4
has caused the Debian Bug report #852000,
regarding oddjob-mkhomedir: fails to install: oddjobd: unrecognized service
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.)


-- 
852000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: oddjob-mkhomedir
Version: 0.34.3-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package oddjob-mkhomedir.
  (Reading database ... 
(Reading database ... 4525 files and directories currently installed.)
  Preparing to unpack .../oddjob-mkhomedir_0.34.3-3_amd64.deb ...
  Unpacking oddjob-mkhomedir (0.34.3-3) ...
  Processing triggers for oddjob (0.34.3-3) ...
  oddjobd: unrecognized service
  dpkg: error processing package oddjob (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of oddjob-mkhomedir:
   oddjob-mkhomedir depends on oddjob (= 0.34.3-3); however:
Package oddjob is not configured yet.
  
  dpkg: error processing package oddjob-mkhomedir (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for dbus (1.10.14-1) ...
  Errors were encountered while processing:
   oddjob
   oddjob-mkhomedir


cheers,

Andreas


oddjob-mkhomedir_0.34.3-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: oddjob
Source-Version: 0.34.3-4

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated oddjob 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: Sat, 28 Jan 2017 19:24:48 +0200
Source: oddjob
Binary: oddjob oddjob-mkhomedir
Architecture: source
Version: 0.34.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Description:
 oddjob - D-Bus service which runs odd jobs -- daemon
 oddjob-mkhomedir - Oddjob helper which creates and populates home directories
Closes: 852000
Changes:
 oddjob (0.34.3-4) unstable; urgency=medium
 .
   * control, postinst: Depend on systemd and move the trigger check after
 debhelper. (Closes: #852000)
Checksums-Sha1:
 a3191e6505743b40b944201101c26fb34d9c96d8 2113 oddjob_0.34.3-4.dsc
 edd4532033fcdf406ba7173575d52823216ff8ed 3164 oddjob_0.34.3-4.debian.tar.xz
Checksums-Sha256:
 38db95fd7f6438782a2fa6a20a4fb9fc0aef272bdbcb97b09750d7140141be63 2113 
oddjob_0.34.3-4.dsc
 bfb05a7abffd26afe07b114b9b68acc36004bdf69ef42ca7acd60d5ad6deabc6 3164 
oddjob_0.34.3-4.debian.tar.xz
Files:
 40fd22e7cdcdc1d669b8b67c32218479 2113 admin optional oddjob_0.34.3-4.dsc
 d6d0b3a44803785a8ef9ba4df715f582 3164 admin optional 
oddjob_0.34.3-4.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYjNPrAAoJEMtwMWWoiYTcE14QAIDX7R2DNGBd+hwZVf8Hg3us
90P7UzxJ0rUZhBlr40fNmwaZM7HXVptp8mnrJnBwHC5iXS60ms0gRZzmY5gmCFRP
z3j9VZFMVf2WwSFjEnh91+TStaBv8ixywHvmIirtRKwKoOdf28N4Yc5/YA0Uw2N0
XhD1NsxNrPob3/Po9TnCt+pJzdfIUa6gQ2MMz/InpmyDK+hbHQvB8cLvmBbn5OqB
bZLnMVDPXLmkcj667KdLlGbx6B2aFZx/NZKd1ldNg9fRDTIJfA8lNqm2R59GNlFw
sw2OSnrgV5WCpiCFNh3n4PVJ/wJnK4QWMR7xc3DC152Hs+o6n7/hNSQgrUachE7o
dQfz4SSD1Yyic5dRnVaMTwnCoDfPHig3vAfS7b2Jr5/13JKn9UVZPOgVlrn497gs
/nkvdqXeDnPhm/nPO4Z5/yakLH8A2DgMl5KstRxaQNb2U9t+cjDB8gK83+4M+Yoa
GApfEHhrsdIIwF3gvQOyAJQgNDuCOsQIW4rUa5MI/SSgsg/NRJhSHJmYiYOqCQjN
1SBdtaGpPmsW8nVjJopgOqzOctQYz4PC4Ac1d4oh0g7g+bbgImLcIpMYKkCh/jSe
EuBjxyc5BLWp6KVXx6Yg1JTKd1e3Z0COTJ1iXdb5mKEvtCwxzX9gVDxGEc7Huqyh

Bug#848927: mount: bad option.

[Andreas Henriksson]

Control: tags -1 + moreinfo

Hello Ray Andrews,

Thanks for your bug report.

On Tue, Dec 20, 2016 at 01:20:29PM -0800, Ray Andrews wrote:
[...]
> gparted fails completely  with the message:
> 
> "mount: bad option. Note that mmoving a mount "
[...]


Could you please describe how you triggered this?

If you could reproduce the issue while running gparted
under strace, eg. strace -e trace=process gparted,
and send a log of that it would likely help much
to be able to identify exactly which mount command
is being executed and thus be able to locate the
relevant part of the gparted source code which 
spawns it

Regards,
Andreas Henriksson

Processed: Re: mount: bad option.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #848927 [gparted] mount: bad option.
Added tag(s) moreinfo.

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

Bug#834746: marked as done (jemalloc: FTBFS on i386: inlining failed...: target specific option mismatch)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 17:49:12 +
with message-id 
and subject line Bug#834746: fixed in jemalloc 3.6.0-9.1
has caused the Debian Bug report #834746,
regarding jemalloc: FTBFS on i386: inlining failed...: target specific option 
mismatch
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.)


-- 
834746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jemalloc
Version: 3.6.0-9
Severity: serious

>From my pbuilder build log, on i386:

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/jemalloc-3.6.0'
make check
make[2]: Entering directory '/build/jemalloc-3.6.0'
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/jemalloc.jet.o src/jemalloc.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/arena.jet.o src/arena.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/atomic.jet.o src/atomic.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/base.jet.o src/base.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/bitmap.jet.o src/bitmap.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/chunk.jet.o src/chunk.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/chunk_dss.jet.o src/chunk_dss.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/chunk_mmap.jet.o src/chunk_mmap.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/ckh.jet.o src/ckh.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/ctl.jet.o src/ctl.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/extent.jet.o src/extent.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/hash.jet.o src/hash.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/huge.jet.o src/huge.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/mb.jet.o src/mb.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/mutex.jet.o src/mutex.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude -Iinclude -o
src/prof.jet.o src/prof.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-std=gnu99 -fvisibility=hidden -DJEMALLOC_JET -c -Wdate-time
-D_FORTIFY_SOURCE=2  -D_GNU_SOURCE -D_REENTRANT -Iinclude 

Bug#852887: marked as done ("FTBFS: sbuild prevents luaotfload-tool to create a HOME cache directoey")

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 17:48:30 +
with message-id <e1cxx70-000gnk...@fasolo.debian.org>
and subject line Bug#852887: fixed in bibtool 2.66+ds-4
has caused the Debian Bug report #852887,
regarding "FTBFS: sbuild prevents luaotfload-tool to create a HOME cache 
directoey"
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.)


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

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/bibtool-2.66+ds/doc'
> ./make_version.pl ../version.c > config.tex
> lualatex -no-shell-escape -interaction=batchmode -draftmode bibtool.tex
> This is LuaTeX, Version 0.95.0 (TeX Live 2016/Debian) 
> bibtex -terse bibtool
> I couldn't open file name `bibtool.aux'
> Makefile:47: recipe for target 'bibtool.pdf' failed
> make[2]: *** [bibtool.pdf] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/01/28/bibtool_2.66+ds-2_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Jerome Benoit <calcu...@rezozer.net> (supplier of updated bibtool 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, 28 Jan 2017 17:16:54 +
Source: bibtool
Binary: bibtool
Architecture: source
Version: 2.66+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Tex Maintainers <debian-tex-ma...@lists.debian.org>
Changed-By: Jerome Benoit <calcu...@rezozer.net>
Description:
 bibtool- tool to manipulate BibTeX files
Closes: 852887
Changes:
 bibtool (2.66+ds-4) unstable; urgency=medium
 .
   * FTBFS fix release (Closes: #852887, second attempt), override sbuild
 HOME setting as workaround to #852980.
Checksums-Sha1:
 b185d737eb3f2e88aa3ea13d9649f509c0208208 2917 bibtool_2.66+ds-4.dsc
 d7307dc5358acacdf8fa9b5d886924c28588603d 21240 bibtool_2.66+ds-4.debian.tar.xz
 fedb70b6ad8b9519cce44a3399f99d81751f8aec 6886 
bibtool_2.66+ds-4_source.buildinfo
Checksums-Sha256:
 6c8ffee0132c5fbf212ce20393c48e4f137ee9cff00f61348bd526d2224fe687 2917 
bibtool_2.66+ds-4.dsc
 9e7a630ab91a74a3396665e3d7b4f0b01f41a13573a0e6a33cd487b6e0361b6d 21240 
bibtool_2.66+ds-4.debian.tar.xz
 9dffd7dd17f1f53b3a53662542da148c1fc09fae83d5659e35371140e0e419b3 6886 
bibtool_2.66+ds-4_source.buildinfo
Files:
 4138d33343301398211b5a622503798e 2917 tex optional bibtool_2.66+ds-4.dsc
 4a630c1a7e2c1178ec72803ef0548454 21240 tex optional 
bibtool_2.66+ds-4.debian.tar.xz
 9b8bb5b0bab32271f9200b5eb6f8f279 6886 tex optional 
bibtool_2.66+ds-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQcBAEBCgAGBQJYjNUtAAoJED+SGaZ/NsaLZDMgAMkCYoAEgxSFB4gWnfrjkc7t
nHfFpCNQQ115qMOYo05rjaF1CJoVp/i4YAMPaqT6gadIwVLV6fo2M029kKbi+Dva
sFyM18Kc23CguTMH3Qfewjv+0MB+7oolwsM4OTVoFRxY5EF13jBK2C9/09JQlAnf
R08zTOXgxY3nCLjXuAI3yGFwqKDhq2gRbm324jkgy6Oq7zIXgASbWXWIb/Is1/sq
tEfVAM4cqGIb1sjhSti7d/PRUbYqkzh4z5d1nYwt8B3rj8r3YwDA2mH0YkdWnTtw
XAmdVEiQo1fwnXUmJ8Wq/JyGsngbMDb2B0MIjK73MQZCBGnAVWea+1ySl/vhwiRc
EyeueCkD9VqJTebffJirHYtM6jSexD3CoP5C4p4yP8V56lVoz6284+PmaJAmkUM6
AR4s4yPCFZ/dxbIzRKXoDJ+bKtX91LDqxxHHu+VPVXbXitVwUcGEf/WixtE4xIzG
C26qWQyG84KzmtcyXpi+l71qGqEjVvtJyEVUsBTCpJM4z5OzsS51DI7W6u40NyoL
JDshfMk2eh0hW4w0R3RmsHJOc5WPcggXornIYed3TW+GXHiJtpX/y+U7FzoK0SZ6
pO

Bug#834746: NMU Fix for FTBFS

[Daniel Silverstone]

Control: tags -1 patch pending

Hi,

Attached is an NMU patch which corrects the problem in this bug.  This is
related to the fact that the test suite (and only the test suite) relies on
SSE2 for i386 (which should be no issue for the buildds).

I have uploaded this to unstable.

Thanks,

Daniel.

-- 
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69
diff -Nru jemalloc-3.6.0/debian/changelog jemalloc-3.6.0/debian/changelog
--- jemalloc-3.6.0/debian/changelog	2016-01-27 21:20:33.0 +
+++ jemalloc-3.6.0/debian/changelog	2017-01-28 17:21:21.0 +
@@ -1,3 +1,12 @@
+jemalloc (3.6.0-9.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add testflags.patch which adds a TESTFLAGS env var support when
+compiling tests.
+  * Add -msse4.1 to i386 TESTFLAGS (Closes: #834746)
+
+ -- Daniel Silverstone   Sat, 28 Jan 2017 17:21:21 +
+
 jemalloc (3.6.0-9) unstable; urgency=medium
 
   [ Balint Reczey ]
diff -Nru jemalloc-3.6.0/debian/patches/series jemalloc-3.6.0/debian/patches/series
--- jemalloc-3.6.0/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ jemalloc-3.6.0/debian/patches/series	2017-01-28 17:07:36.0 +
@@ -0,0 +1 @@
+testflags.patch
diff -Nru jemalloc-3.6.0/debian/patches/testflags.patch jemalloc-3.6.0/debian/patches/testflags.patch
--- jemalloc-3.6.0/debian/patches/testflags.patch	1970-01-01 01:00:00.0 +0100
+++ jemalloc-3.6.0/debian/patches/testflags.patch	2017-01-28 17:20:53.0 +
@@ -0,0 +1,31 @@
+Description: Add support for TESTFLAGS
+ Add support to Makefile.in to allow passing TESTFLAGS to give
+ extra CFLAGS to the compilation of test files.
+Author: Daniel Silverstone 
+Origin: other
+Bug: 834746
+Forwarded: no
+Reviewed-by: Steve McIntyre 
+Last-Update: 2017-01-28
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/Makefile.in
 b/Makefile.in
+@@ -207,7 +207,7 @@
+ $(C_UTIL_INTEGRATION_OBJS): $(objroot)src/%.integration.$(O): $(srcroot)src/%.c
+ $(C_TESTLIB_STRESS_OBJS): $(objroot)test/src/%.stress.$(O): $(srcroot)test/src/%.c
+ $(C_TESTLIB_STRESS_OBJS): CPPFLAGS += -DJEMALLOC_STRESS_TEST -DJEMALLOC_STRESS_TESTLIB
+-$(C_TESTLIB_OBJS): CPPFLAGS += -I$(srcroot)test/include -I$(objroot)test/include
++$(C_TESTLIB_OBJS): CPPFLAGS += -I$(srcroot)test/include -I$(objroot)test/include $(TESTFLAGS)
+ $(TESTS_UNIT_OBJS): CPPFLAGS += -DJEMALLOC_UNIT_TEST
+ $(TESTS_UNIT_AUX_OBJS): CPPFLAGS += -DJEMALLOC_UNIT_TEST
+ define make-unit-link-dep
+@@ -218,7 +218,7 @@
+ $(TESTS_INTEGRATION_OBJS): CPPFLAGS += -DJEMALLOC_INTEGRATION_TEST
+ $(TESTS_STRESS_OBJS): CPPFLAGS += -DJEMALLOC_STRESS_TEST
+ $(TESTS_OBJS): $(objroot)test/%.$(O): $(srcroot)test/%.c
+-$(TESTS_OBJS): CPPFLAGS += -I$(srcroot)test/include -I$(objroot)test/include
++$(TESTS_OBJS): CPPFLAGS += -I$(srcroot)test/include -I$(objroot)test/include $(TESTFLAGS)
+ ifneq ($(IMPORTLIB),$(SO))
+ $(C_OBJS): CPPFLAGS += -DDLLEXPORT
+ endif
diff -Nru jemalloc-3.6.0/debian/rules jemalloc-3.6.0/debian/rules
--- jemalloc-3.6.0/debian/rules	2016-01-27 21:16:22.0 +
+++ jemalloc-3.6.0/debian/rules	2017-01-28 17:21:21.0 +
@@ -27,6 +27,12 @@
   DEB_CPPFLAGS_MAINT_APPEND += -DPATH_MAX=8192
 endif
 
+ifeq ($(DEB_HOST_ARCH),i386)
+  # i386 needs -msse4.1 in order to be able to run the test suite
+  # and as far as we can tell, *ONLY* the test suite
+  TESTFLAGS += -msse4.1
+endif
+
 DEB_CFLAGS_MAINT_APPEND += -std=gnu99
 
 export DEB_CFLAGS_MAINT_APPEND DEB_CPPFLAGS_MAINT_APPEND
@@ -40,7 +46,7 @@
 ifeq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),)
 export ASAN_OPTIONS = suppressions=$(CURDIR)/debian/asan-suppressions.txt
 override_dh_auto_test:
-	make check
+	make check "TESTFLAGS=$(TESTFLAGS)"
 endif
 
 override_dh_auto_install:

Processed: NMU Fix for FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #834746 [src:jemalloc] jemalloc: FTBFS on i386: inlining failed...: target 
specific option mismatch
Added tag(s) patch and pending.

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

Processed: summary 851446 58 ..., severity of 851446 is important

[Debian Bug Tracking System]

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

> summary 851446 58
Ignoring request to change the summary of bug 851446 to the same value
> retitle 851446 initscripts upgrade may result in symlink loop between 
> /dev/shm and /run/shm
Bug #851446 [initscripts] mkdir: cannot create directory `/run/shm': File exists
Changed Bug title to 'initscripts upgrade may result in symlink loop between 
/dev/shm and /run/shm' from 'mkdir: cannot create directory `/run/shm': File 
exists'.
> # This is clearly not a common problem
> severity 851446 important
Bug #851446 [initscripts] initscripts upgrade may result in symlink loop 
between /dev/shm and /run/shm
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#852894: [Pkg-clamav-devel] Bug#852894: clamav: FTBFS: dh_install: missing files, aborting

[Reiner Herrmann]

On Sat, Jan 28, 2017 at 12:31:09PM -0500, Scott Kitterman wrote:
> I think during pre-release freeze was not the best time to do this change?  
> How many other packages did you break and did you coordinate this with the 
> Release Team?

I agree, but you should ask this the curl maintainers. :)
Looking at [0] it looks like some other packages are affected by that.

[0] 
https://udd.debian.org/bugs/bugs/bugs/?release=stretch_and_sid=ign=ign=ign=7=1=id=asc=1=1=1#results


signature.asc
Description: Digital signature

Bug#852894: [Pkg-clamav-devel] Bug#852894: clamav: FTBFS: dh_install: missing files, aborting

[Scott Kitterman]

On Saturday, January 28, 2017 06:02:59 PM Reiner Herrmann wrote:
> > dh_install: Cannot find (any matches for) "debian/tmp/usr/bin/clamsubmit"
> > (tried in "." and "debian/tmp")
> Building clamsubmit is only enabled, if libcurl is found.
> 
> > checking for libcurl installation... /usr
> > configure: WARNING: libcurl not found. Please use the web interface for
> > submitting FPs/FNs.
> ... which is not the case anymore.
> 
> Since curl 7.52.1-1, the headers are in a multiarch path:
> /usr/include/x86_64-linux-gnu/curl/curl.h, but clamav is checking for
> $LIBCURL_HOME/include/curl/curl.h [0]
> 
> [0]
> https://sources.debian.net/src/clamav/0.99.2%2Bdfsg-5/m4/reorganization/lib
> s/curl.m4/#L21

I think during pre-release freeze was not the best time to do this change?  
How many other packages did you break and did you coordinate this with the 
Release Team?

Scott K

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

Bug#851513: Build failing

[Stijn Segers]

I applied all four patches to the zfs-dkms 0.6.5.8-3 package, but compiling 
fails (SPL built fine after I patched it):

CC [M] /var/lib/dkms/zfs/0.6.5.8/build/module/zfs/zpl_export.o
/var/lib/dkms/zfs/0.6.5.8/build/module/zfs/zpl_ctldir.c:424:13: error: 
initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]
.rename = zpl_snapdir_rename,
^~
/var/lib/dkms/zfs/0.6.5.8/build/module/zfs/zpl_ctldir.c:424:13: note: (near 
initialization for ‘zpl_ops_snapdir.rename’)
cc1: some warnings being treated as errors
/usr/src/linux-headers-4.9.0-1-common/scripts/Makefile.build:298: recept voor 
doel '/var/lib/dkms/zfs/0.6.5.8/build/module/zfs/zpl_ctldir.o' is mislukt
make[7]: *** [/var/lib/dkms/zfs/0.6.5.8/build/module/zfs/zpl_ctldir.o] Fout 1

These are stretch installs as well (have three with ZFS, all the same error).

Thanks

Stijn

Processed: Re: clamav: FTBFS: dh_install: missing files, aborting

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #852894 [src:clamav] clamav: FTBFS: dh_install: missing files, aborting
Added tag(s) patch.

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

Bug#852894: clamav: FTBFS: dh_install: missing files, aborting

[Reiner Herrmann]

Control: tag -1 + patch

The attached patch changes the detection of libcurl by not checking for
the curl.h header, but for the curl-config command provided by the same
-dev package.

Regards,
  Reiner
diff --git a/debian/patches/curl-detection.patch b/debian/patches/curl-detection.patch
new file mode 100644
index 000..8a463d8
--- /dev/null
+++ b/debian/patches/curl-detection.patch
@@ -0,0 +1,18 @@
+Author: Reiner Herrmann 
+Description: Fix detection of libcurl
+ curl headers are now in a multiarch include directory, so the current
+ check no longer succeeds. Check for curl-config instead, which is
+ provided by the same -dev package as the headers.
+Bug-Debian: https://bugs.debian.org/852894
+
+--- a/m4/reorganization/libs/curl.m4
 b/m4/reorganization/libs/curl.m4
+@@ -18,7 +18,7 @@
+ AC_MSG_RESULT([$LIBCURL_HOME])
+ ])
+ 
+-if test ! -f "$LIBCURL_HOME/include/curl/curl.h"
++if test ! -f "$LIBCURL_HOME/bin/curl-config"
+ then
+ AC_MSG_WARN([libcurl not found. Please use the web interface for submitting FPs/FNs.])
+ else
diff --git a/debian/patches/series b/debian/patches/series
index 5b943a3..32b7e8b 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -11,3 +11,4 @@ Add-support-for-LLVM-3.7.patch
 Add-support-for-LLVM-3.8.patch
 Add-support-for-LLVM-3.9.patch
 bb11549-fix-temp-file-cleanup-issue.patch
+curl-detection.patch


signature.asc
Description: PGP signature

Bug#852920: [Pkg-openssl-devel] Bug#852920: libnet-ssleay-perl: FTBFS: Test failures

[gregor herrmann]

On Sat, 28 Jan 2017 16:35:44 +0100, Kurt Roeckx wrote:

> On Sat, Jan 28, 2017 at 04:02:02PM +0100, gregor herrmann wrote:
> > Control: forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=120006
> 
> I've just filed:
> https://rt.cpan.org/Public/Bug/Display.html?id=120006

Is this a copypaste error?


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: David Bowie: Space Oddity


signature.asc
Description: Digital Signature

Bug#852894: clamav: FTBFS: dh_install: missing files, aborting

[Reiner Herrmann]

> dh_install: Cannot find (any matches for) "debian/tmp/usr/bin/clamsubmit" 
> (tried in "." and "debian/tmp")

Building clamsubmit is only enabled, if libcurl is found.

> checking for libcurl installation... /usr
> configure: WARNING: libcurl not found. Please use the web interface for 
> submitting FPs/FNs.

... which is not the case anymore.

Since curl 7.52.1-1, the headers are in a multiarch path:
/usr/include/x86_64-linux-gnu/curl/curl.h, but clamav is checking for
$LIBCURL_HOME/include/curl/curl.h [0]

[0] 
https://sources.debian.net/src/clamav/0.99.2%2Bdfsg-5/m4/reorganization/libs/curl.m4/#L21


signature.asc
Description: Digital signature

Bug#852886: marked as done (libvirt-python: FTBFS: ERROR: failed virConnectSecretEventRegisterAny)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 16:49:30 +
with message-id <e1cxwbu-0009ya...@fasolo.debian.org>
and subject line Bug#852886: fixed in libvirt-python 3.0.0-2
has caused the Debian Bug report #852886,
regarding libvirt-python: FTBFS: ERROR: failed virConnectSecretEventRegisterAny
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3,python2 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> /usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt
> /usr/bin/python generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml
> Found 418 functions in /usr/share/libvirt/api/libvirt-api.xml
> Found 0 functions in libvirt-override-api.xml
> Generated 344 wrapper functions
> Missing type converters: 
> virConnectSecretEventGenericCallback:1 
> virStorageVolInfoPtr:1 
> ERROR: failed virConnectSecretEventRegisterAny
> ERROR: failed virStorageVolGetInfoFlags
> error: command '/usr/bin/python' failed with exit status 1
> E: pybuild pybuild:283: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python setup.py build 
> dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
> debian/rules:8: recipe for target 'build' failed
> make: *** [build] Error 25

The full build log is available from:
   http://aws-logs.debian.net/2017/01/28/libvirt-python_2.5.0-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Guido Günther <a...@sigxcpu.org> (supplier of updated libvirt-python 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: Sat, 28 Jan 2017 13:35:36 +0100
Source: libvirt-python
Binary: python-libvirt python3-libvirt
Architecture: source
Version: 3.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther <a...@sigxcpu.org>
Changed-By: Guido Günther <a...@sigxcpu.org>
Closes: 852886
Description: 
 python3-libvirt - libvirt Python 3 bindings
 python-libvirt - libvirt Python bindings
Changes:
 libvirt-python (3.0.0-2) unstable; urgency=medium
 .
   * Upload to unstable (Closes: #852886)
Checksums-Sha1: 
 53d6f7ba342bce45f7d32207736fe73099174ba7 2175 libvirt-python_3.0.0-2.dsc
 6644ec3f2f812eea4dda846cc8bb1fbe7690725f 6704 
libvirt-python_3.0.0-2.debian.tar.xz
Checksums-Sha256: 
 3f9948860469a984b0d18b29926ef21c5d9a4b170f9ea05e01f448b04f9d10a4 2175 
libvirt-python_3.0.0-2.dsc
 4825fadb4d4613a7053fe40e2735a213bf06300352bd45b43f49d7f2fc42b68a 6704 
libvirt-python_3.0.0-2.debian.tar.xz
Files: 
 33658bc507609ae83836242b9527cffd 2175 python optional 
libvirt-python_3.0.0-2.dsc
 d8b9917b7a9f226741f37e995e5e60a8 6704 python optional 
libvirt-python_3.0.0-2.debian.ta

Bug#795690: NMU diff for libcdio

[Steve McIntyre]

I'm uploading this to unstable now rather than to DELAYED; there's not
been any obvious maintainer activity here for ages...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Since phone messaging became popular, the young generation has lost the
 ability to read or write anything that is longer than one hundred and sixty
 characters."  -- Ignatios Souvatzis
diff -Nru libcdio-0.83/debian/changelog libcdio-0.83/debian/changelog
--- libcdio-0.83/debian/changelog   2014-09-02 11:07:11.0 +1400
+++ libcdio-0.83/debian/changelog   2017-01-29 03:52:41.0 +1400
@@ -1,3 +1,14 @@
+libcdio (0.83-4.3) unstable; urgency=medium
+
+  * NMU
+  * Run tests using TZ=UTC to avoid breakage in libcdio with weird time
+zones. Closes: #795690
+  * Move Japanese manpages to the right directory. Closes: #850628
+  * Switch to multi-arch; thanks to Francois Gouget and Matthias Klose for
+very similar patches. Closes: #777222,#812915
+
+ -- Steve McIntyre <93...@debian.org>  Sat, 28 Jan 2017 13:52:41 +
+
 libcdio (0.83-4.2) unstable; urgency=low
 
   * Non-maintainer upload with maintainers permission.
diff -Nru libcdio-0.83/debian/compat libcdio-0.83/debian/compat
--- libcdio-0.83/debian/compat  2011-12-29 12:58:43.0 +1400
+++ libcdio-0.83/debian/compat  2017-01-29 03:52:41.0 +1400
@@ -1 +1 @@
-8
+9
diff -Nru libcdio-0.83/debian/control libcdio-0.83/debian/control
--- libcdio-0.83/debian/control 2014-09-02 11:05:05.0 +1400
+++ libcdio-0.83/debian/control 2017-01-29 03:52:41.0 +1400
@@ -2,7 +2,7 @@
 Priority: optional
 Section: libs
 Maintainer: Nicolas Boullis 
-Build-Depends: debhelper (>= 8.0.0), dctrl-tools | grep-dctrl, libpopt-dev, 
libncurses5-dev | libncurses-dev, libcam-dev [kfreebsd-any], dh-autoreconf
+Build-Depends: debhelper (>= 9), dctrl-tools | grep-dctrl, libpopt-dev, 
libncurses5-dev | libncurses-dev, libcam-dev [kfreebsd-any], dh-autoreconf
 Standards-Version: 3.9.2
 Homepage: http://www.gnu.org/software/libcdio/
 
@@ -25,6 +25,8 @@
 Package: libcdio13
 Section: libs
 Architecture: any
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: library to read and control CD-ROM
  This library is to encapsulate CD-ROM reading and
@@ -38,6 +40,7 @@
 Package: libiso9660-dev
 Section: libdevel
 Architecture: any
+Multi-Arch: same
 Depends: libiso9660-8 (= ${binary:Version}), libcdio-dev (>= 0.78.2-1), 
${libcdev}, ${misc:Depends}
 Description: library to work with ISO9660 filesystems (development files)
  This package contains development files (headers and static library)
@@ -49,6 +52,8 @@
 Package: libiso9660-8
 Section: libs
 Architecture: any
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: library to work with ISO9660 filesystems
  This library is made to read and write ISO9660 filesystems; those
@@ -70,6 +75,8 @@
 Package: libcdio-cdda1
 Section: libs
 Architecture: any
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: library to read and control digital audio CDs
  This library is made to read and control digital audio CDs. It does
@@ -80,6 +87,7 @@
 Package: libcdio-paranoia-dev
 Section: libdevel
 Architecture: any
+Multi-Arch: same
 Depends: libcdio-paranoia1 (= ${binary:Version}), libcdio-cdda-dev, 
libcdio-dev, ${libcdev}, ${misc:Depends}
 Description: library to read digital audio CDs with error correction 
(development files)
  This package contains development files (headers and static library)
@@ -93,6 +101,8 @@
 Package: libcdio-paranoia1
 Section: libs
 Architecture: any
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: library to read digital audio CDs with error correction
  This library is made to read digital audio CDs, with error
@@ -103,6 +113,7 @@
 Package: libudf-dev
 Section: libdevel
 Architecture: any
+Multi-Arch: same
 Depends: libudf0 (= ${binary:Version}), libcdio-dev (>= 0.78.2-1), ${libcdev}, 
${misc:Depends}
 Description: library to work with UDF filesystems (development files)
  This package contains development files (headers and static library)
@@ -114,6 +125,8 @@
 Package: libudf0
 Section: libs
 Architecture: any
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: library to work with UDF filesystems
  This library is made to read and write UDF filesystems; those
@@ -122,6 +135,7 @@
 Package: libcdio-utils
 Section: otherosfs
 Architecture: any
+Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: sample applications based on the CDIO libraries
  This package contains a collection of small libcdio-based tools:
diff -Nru libcdio-0.83/debian/libcdio-cdda-dev.install 
libcdio-0.83/debian/libcdio-cdda-dev.install
--- 

Bug#852367: marked as done (wims build-depends on autoconf2.59)

[Debian Bug Tracking System]

Your message dated Sat, 28 Jan 2017 16:05:52 +
with message-id 
and subject line Bug#852367: fixed in wims 1:4.13c~dfsg1-2
has caused the Debian Bug report #852367,
regarding wims build-depends on autoconf2.59
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.)


-- 
852367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wims
Version: 1:4.13b~dfsg1-1
Severity: serious

autoconf2.59 is planned to be removed from Debian (see #852235).

wims build-depends on autoconf2.59|autoconf, and the buildds
are only considering the first alternative.

Please change the build dependency from "autoconf2.59|autoconf"
to "autoconf".
--- End Message ---
--- Begin Message ---
Source: wims
Source-Version: 1:4.13c~dfsg1-2

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated wims 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: Sat, 28 Jan 2017 14:26:34 +0100
Source: wims
Binary: wims wims-modules wims-java-applets flydraw
Architecture: source amd64 all
Version: 1:4.13c~dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 flydraw- command-line drawing tool
 wims   - server for educational content: courses, exercises, and exams
 wims-java-applets - applets for modules used by WIMS
 wims-modules - minimal set of modules used by WIMS
Closes: 852367
Changes:
 wims (1:4.13c~dfsg1-2) unstable; urgency=medium
 .
   * Changed the build-dependency on autoconf; Closes: #852367
Checksums-Sha1:
 14fd4744da5538d7d992672ba0245bddeffd8089 2345 wims_4.13c~dfsg1-2.dsc
 17b4bd76601d79056c9dcb54fd3dcc4f4bea6d04 198612 
wims_4.13c~dfsg1-2.debian.tar.xz
 015b87bec319ffdd29ac42c0c0dada7e56b9d3ec 57396 flydraw_4.13c~dfsg1-2_amd64.deb
 a818914a7eb566f8571f629a741be0e28c673f5c 107126 
wims-dbgsym_4.13c~dfsg1-2_amd64.deb
 ce442af706ec530146b0bb162cd501cd4b9791d6 2573026 
wims-java-applets_4.13c~dfsg1-2_amd64.deb
 b761a3fd0f9149469fcd34ec65ba8dc9c852b7a3 1350956 
wims-modules_4.13c~dfsg1-2_all.deb
 d4e3e0c1200636ceef6be66f07d324b8f2414d64 16049 
wims_4.13c~dfsg1-2_amd64.buildinfo
 7c39528a7e63cd8fe3e5178b5ddb146d27fcced7 19268332 wims_4.13c~dfsg1-2_amd64.deb
Checksums-Sha256:
 3322ce19e8707358380ff9e48dab02da7494432a83708d0deaf52bd7699b5e2f 2345 
wims_4.13c~dfsg1-2.dsc
 a0ddb31c2e40a6aeb113ca4e5b9912efca23e70ef34195d0d743787eae9ed831 198612 
wims_4.13c~dfsg1-2.debian.tar.xz
 9174ef7206e0618e97aad55caf0bd714889e7b210adf846429ef551076675569 57396 
flydraw_4.13c~dfsg1-2_amd64.deb
 f1fe3dce6a3922e87737c9c18fead8d388be23f499784a2861512ca2966e6587 107126 
wims-dbgsym_4.13c~dfsg1-2_amd64.deb
 f6ee4bee7100506aaa877d5cd549fcef9480f7e3b47846aef8d358d4755a3454 2573026 
wims-java-applets_4.13c~dfsg1-2_amd64.deb
 ada6be257ae23ab42aa52fe4330e33679d54c5819b7e64f39ce15840f4a8e5af 1350956 
wims-modules_4.13c~dfsg1-2_all.deb
 5ffc7ca0347fe7976243bea04706098198a121d453bc00103b238d6420b1b2dd 16049 
wims_4.13c~dfsg1-2_amd64.buildinfo
 48e7885b5bf71001f2d8305f822067d3a063f91b074386317a66db58a9b234d7 19268332 
wims_4.13c~dfsg1-2_amd64.deb
Files:
 fdb26f9d5f5a40863455c5104b9d46ca 2345 web optional wims_4.13c~dfsg1-2.dsc
 4cc3ec3a44acca29baf1b19fd3f2582c 198612 web optional 
wims_4.13c~dfsg1-2.debian.tar.xz
 0611bc2223adbd3bbdc6f7e4cbe0b036 57396 graphics optional 
flydraw_4.13c~dfsg1-2_amd64.deb
 9b7ed6b7e99163398491aa4f68d71348 107126 debug extra 
wims-dbgsym_4.13c~dfsg1-2_amd64.deb
 3ca55b5bcdfd098043c14c0fb00ab23b 2573026 web optional 
wims-java-applets_4.13c~dfsg1-2_amd64.deb
 3214e541349095599782530c2caf75b7 1350956 web optional 
wims-modules_4.13c~dfsg1-2_all.deb
 c4f1c361a63fe887cbacf7e58f3ccf07 16049 web optional 
wims_4.13c~dfsg1-2_amd64.buildinfo
 cbb2445fdc4141c61060a3f38f6d 19268332 web optional 
wims_4.13c~dfsg1-2_amd64.deb

-BEGIN PGP 

Processed: I botched the merge

[Debian Bug Tracking System]

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

> forcemerge 850958 852263 852337
Bug #850958 [ldc] ldc on ppc64el is broken
Bug #852337 [ldc] ldc FTBFS on ppc64el: Failed to compile empty program using D 
compiler '/usr/bin/ldmd2'
Added indication that 852337 affects 
src:gtk-d,src:terminix,src:onedrive,src:mustache-d
Bug #852263 [ldc] mustache-d FTBFS on ppc64el: Unknown compiler "ldc2"
Added indication that 852263 affects 
src:gtk-d,src:terminix,src:onedrive,src:mustache-d
Merged 850958 852263 852337
> thanks
Stopping processing here.

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

Processed (with 1 error): ldc on ppc64el is broken

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ldc 1:1.1.0+b6-1
Bug #850958 [src:terminix] terminix: FTBFS on ppc64el: segmentation fault
Bug reassigned from package 'src:terminix' to 'ldc'.
No longer marked as found in versions terminix/1.4.0-1.
Ignoring request to alter fixed versions of bug #850958 to the same values 
previously set
Bug #850958 [ldc] terminix: FTBFS on ppc64el: segmentation fault
Marked as found in versions ldc/1:1.1.0+b6-1.
> reassign 852263 ldc 1:1.1.0+b6-1
Bug #852263 [src:mustache-d] mustache-d FTBFS on ppc64el: Unknown compiler 
"ldc2"
Bug reassigned from package 'src:mustache-d' to 'ldc'.
No longer marked as found in versions mustache-d/0.1.3-1.
Ignoring request to alter fixed versions of bug #852263 to the same values 
previously set
Bug #852263 [ldc] mustache-d FTBFS on ppc64el: Unknown compiler "ldc2"
Marked as found in versions ldc/1:1.1.0+b6-1.
> reassign 852337 ldc 1:1.1.0+b6-1
Bug #852337 [src:ldc] ldc FTBFS on ppc64el: Failed to compile empty program 
using D compiler '/usr/bin/ldmd2'
Bug reassigned from package 'src:ldc' to 'ldc'.
No longer marked as found in versions ldc/1:1.1.0+b6-2.
Ignoring request to alter fixed versions of bug #852337 to the same values 
previously set
Bug #852337 [ldc] ldc FTBFS on ppc64el: Failed to compile empty program using D 
compiler '/usr/bin/ldmd2'
Marked as found in versions ldc/1:1.1.0+b6-1.
> -1 852263 852337
Unknown command or malformed arguments to command.

> retitle -1 ldc on ppc64el is broken
Bug #850958 [ldc] terminix: FTBFS on ppc64el: segmentation fault
Changed Bug title to 'ldc on ppc64el is broken' from 'terminix: FTBFS on 
ppc64el: segmentation fault'.
> affects -1 src:terminix src:onedrive src:gtk-d src:mustache-d
Bug #850958 [ldc] ldc on ppc64el is broken
Added indication that 850958 affects src:terminix, src:onedrive, src:gtk-d, and 
src:mustache-d

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

Bug#850958: ldc on ppc64el is broken

[Adrian Bunk]

Control: reassign -1 ldc 1:1.1.0+b6-1
Control: reassign 852263 ldc 1:1.1.0+b6-1
Control: reassign 852337 ldc 1:1.1.0+b6-1
Control: -1 852263 852337
Control: retitle -1 ldc on ppc64el is broken
Control: affects -1 src:terminix src:onedrive src:gtk-d src:mustache-d


Further information:
  https://lists.debian.org/debian-release/2017/01/msg00592.html


cu
Adrian

-- 

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

Bug#852245: fix_python2_selectors.patch is not correct

[Irmen de Jong]

On Sat, 28 Jan 2017 13:10:15 +0100 Irmen de Jong  wrote:

> I'm not sure what the best course of action is here, but I strongly suggest 
> to re-open
> the bug for now and not have the patch as it is right now.

I think I have a proper solution in place for the next Pyro4 release (4.54).
You can view the relevant commit here:
https://github.com/irmen/Pyro4/commit/edfdbb2ce4279d929b306d00ac8fbc6543a0807b

It avoids the immediate crash when importing Pyro4 and only raises a 
(meaningful) error
when the user attempts to create a multiplex server, without the selectors34 
module
installed.

My suggestion is to use this change, instead of the broken (IMO) import select 
as
selectors patch.

Even better is of course to package selectors34, but I understand that is not 
easily done.


Irmen de Jong
(Pyro4)