Bug#845757: geneweb FTBFS on mipsel: dpkg-deb (subprocess): compressing tar member: lzma error: Cannot allocate memory

[Christian PERRIER]

Quoting Guillaume Brochu (guillaume.bro...@gmail.com):

> This modification was introduced in June 2012:
> 
> https://anonscm.debian.org/cgit/collab-maint/geneweb.git/commit/?id=16cddde963e4169c09bfe49cb6949fe0dc484f0c
> 
> At first sight, I don't see any reason to use compression level 9, so I will
> apply your patch on the git repository.

Indeed no good reason. This change was done when exchanging with
Hideki Yamane who was preparing a talk about switching to xz, for
DebConf 12. As much as I remember, I proposed Yamane-san to swith "my"
geneweb package to xz and even enforce the highest compression level,
as an illustration of "yes we can".

Later on, several discussions showed that this compression level puts
too much load on autobuilders and then the default was setto use
xz's own default.

But, geneweb was never changed later on, which explains this. So, in
short, there was no special reason except experimentation.

I'm building the package modified by Guillaume and will upload
soon. Thank you for your work.




signature.asc
Description: PGP signature

Processed: tagging 828269

[Debian Bug Tracking System]

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

> tags 828269 + pending
Bug #828269 [src:condor] condor: FTBFS with openssl 1.1.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#831240: marked as done (google-perftools: FTBFS: Running death test 0 hangs)

[Debian Bug Tracking System]

Your message dated Sun, 27 Nov 2016 07:33:31 +
with message-id 
and subject line Bug#831240: fixed in google-perftools 2.5-1
has caused the Debian Bug report #831240,
regarding google-perftools: FTBFS: Running death test 0 hangs
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.)


-- 
831240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: google-perftools
Version: 2.2.1-0.3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160714 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):
> PASS: malloc_extension_debug_test
> PASS
> PASS: memalign_debug_unittest
> PASS
> PASS: realloc_debug_unittest
> make[2]: *** wait: No child processes.  Stop.
> make[2]: *** Waiting for unfinished jobs
> make[2]: *** wait: No child processes.  Stop.
> make[1]: *** wait: No child processes.  Stop.
> make[1]: *** Waiting for unfinished jobs
> make[1]: *** wait: No child processes.  Stop.
> make: *** wait: No child processes.  Stop.
> make: *** Waiting for unfinished jobs
> make: *** wait: No child processes.  Stop.
> E: Caught signal ‘Terminated’: terminating immediately
> Running death test 0Build killed with signal TERM after 150 minutes of 
> inactivity

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/14/google-perftools_2.2.1-0.3_unstable_gcc5.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: google-perftools
Source-Version: 2.5-1

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

Debian distribution maintenance software
pp.
Daigo Moriwaki  (supplier of updated google-perftools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 27 Nov 2016 14:28:33 +0900
Source: google-perftools
Binary: libgoogle-perftools-dev libtcmalloc-minimal4 libtcmalloc-minimal4-dbg 
libgoogle-perftools4 libgoogle-perftools4-dbg google-perftools
Architecture: source all amd64
Version: 2.5-1
Distribution: unstable
Urgency: medium
Maintainer: Daigo Moriwaki 
Changed-By: Daigo Moriwaki 
Description:
 google-perftools - command line utilities to analyze the performance of C++ 
programs
 libgoogle-perftools-dev - libraries for CPU and heap analysis, plus an 
efficient thread-cac
 libgoogle-perftools4 - libraries for CPU and heap analysis, plus an efficient 
thread-cac
 libgoogle-perftools4-dbg - libraries for CPU and heap analysis, plus an 
efficient thread-cac
 libtcmalloc-minimal4 - efficient thread-caching malloc
 libtcmalloc-minimal4-dbg - efficient thread-caching malloc
Closes: 831240
Changes:
 google-perftools (2.5-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #831240)
   * Update watch file
   * Remove patches that the upstream has applied
 - debian/patches/unbreak-heap-profiler-unittest-on-gcc-5.patch
 - debian/patches/unbreak-heap_checker_unittest-on-gcc-5.patch
Checksums-Sha1:
 caeffd74dda43faf69056eae171ab17358e9cbb6 2665 google-perftools_2.5-1.dsc
 b7b0a24cbe052e0c4b69d43d7ecb5d8fca1dfa1c 895687 
google-perftools_2.5.orig.tar.gz
 31cb2768e4b88cd3ad73f6741089eb90d0ffdb65 6339 google-perftools_2.5-1.diff.gz
 6a64baef266657f4191e1957a0b5602dad185383 78900 google-perftools_2.5-1_all.deb
 34e21a099bb6ac5a00310435b0b77daab1e802ee 6067 
google-perftools_2.5-1_amd64.buildinfo
 0df283669b21db0aad61d7b2c90c860172552d70 459100 
libgoogle-perftools-dev_2.5-1_amd64.deb
 415c2422883c0120f3f7febf09f823c32a4089cd 2635572 

Bug#845082: numexpr FTBFS on ppc64el: test failures

[Antonio Valentino]

tags 845082 + pending

thanks

-- 
Antonio Valentino

Processed: fixed 845244 in 8:6.9.5.9+dfsg-1

[Debian Bug Tracking System]

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

> fixed 845244 8:6.9.5.9+dfsg-1
Bug #845244 {Done: Bastien ROUCARIES } 
[src:imagemagick] Add check for invalid mat file
Marked as fixed in versions imagemagick/8:6.9.5.9+dfsg-1.
> thanks
Stopping processing here.

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

Bug#844925: marked as done (ruby-sidekiq-cron: FTBFS: ERROR: Test "ruby2.3" failed: ArgumentError: argument out of range)

[Debian Bug Tracking System]

Your message dated Sun, 27 Nov 2016 07:03:22 +
with message-id 
and subject line Bug#844925: fixed in ruby-sidekiq-cron 0.4.2-6
has caused the Debian Bug report #844925,
regarding ruby-sidekiq-cron: FTBFS: ERROR: Test "ruby2.3" failed: 
ArgumentError: argument out of range
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.)


-- 
844925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sidekiq-cron
Version: 0.4.2-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> ArgumentError: argument out of range
> /<>/test/unit/poller_test.rb:83:in `initialize'
> /<>/test/unit/poller_test.rb:83:in `new'
> /<>/test/unit/poller_test.rb:83:in `block (2 levels) in  (required)>'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in 
> run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block (2 levels) in 
> run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:255:in `time_it'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:348:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:275:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:799:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:322:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:310:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:309:in `each'
> /usr/lib/ruby/vendor_ruby/minitest.rb:309:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:348:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest.rb:335:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest.rb:308:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `block in __run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `map'
> /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `__run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:135:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:62:in `block in autorun'
> 
> 83 runs, 155 assertions, 0 failures, 4 errors, 0 skips
> rake aborted!
> Command failed with status (1): [ruby -I"lib:test"  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/unit/job_test.rb" 
> "test/unit/poller_test.rb" "test/unit/web_extesion_test.rb" ]
> 
> Tasks: TOP => test
> (See full trace by running task with --trace)
> + cleanup
> + kill -9 114156
> rake aborted!
> Command failed with status (1): [./debian/start-redis-server.sh ruby2.3 -S 
> ...]
> /<>/debian/ruby-tests.rake:5:in `block in '
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/ruby-sidekiq-cron_0.4.2-5_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-sidekiq-cron 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 27 Nov 2016 11:51:48 +0530
Source: ruby-sidekiq-cron
Binary: ruby-sidekiq-cron
Architecture: source
Version: 0.4.2-6
Distribution: unstable

Processed: bug 844925 is forwarded to https://github.com/ondrejbartas/sidekiq-cron/issues/119

[Debian Bug Tracking System]

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

> forwarded 844925 https://github.com/ondrejbartas/sidekiq-cron/issues/119
Bug #844925 [src:ruby-sidekiq-cron] ruby-sidekiq-cron: FTBFS: ERROR: Test 
"ruby2.3" failed: ArgumentError: argument out of range
Set Bug forwarded-to-address to 
'https://github.com/ondrejbartas/sidekiq-cron/issues/119'.
> thanks
Stopping processing here.

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

Bug#844905: node-nan: FTBFS: Tests failures

[Pirate Praveen]

On Sat, 19 Nov 2016 08:02:29 +0100 Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.


From upstream discussion,

"The bug is that the Global destructor runs at process exit and tries to
free the object slot but that doesn't work because the VM is dead. In ye
olden days, one could check with v8::V8::IsDead() whether it's safe to
release but that stopped working in V8 3.29..."

Can we disable this test?



signature.asc
Description: OpenPGP digital signature

Bug#844974: marked as done (falcon: FTBFS: error: Could not find suitable distribution for Requirement.parse('keepalive>=0.5'))

[Debian Bug Tracking System]

Your message dated Sun, 27 Nov 2016 05:48:25 +
with message-id 
and subject line Bug#844974: fixed in falcon 1.8.3-1
has caused the Debian Bug report #844974,
regarding falcon: FTBFS: error: Could not find suitable distribution for 
Requirement.parse('keepalive>=0.5')
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.)


-- 
844974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: falcon
Version: 1.8.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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[5]: Entering directory '/<>/DEXTRACTOR'
> rsync -av dexta undexta /<>/inst/bin
> sending incremental file list
> dexta
> undexta
> 
> sent 133,708 bytes  received 54 bytes  267,524.00 bytes/sec
> total size is 133,512  speedup is 1.00
> make[5]: Leaving directory '/<>/DEXTRACTOR'
> cd /<>/pypeFLOW; python setup.py install --prefix 
> /<>/inst
> running install
> running bdist_egg
> running egg_info
> creating pypeflow.egg-info
> writing requirements to pypeflow.egg-info/requires.txt
> writing pypeflow.egg-info/PKG-INFO
> writing top-level names to pypeflow.egg-info/top_level.txt
> writing dependency_links to pypeflow.egg-info/dependency_links.txt
> writing entry points to pypeflow.egg-info/entry_points.txt
> writing manifest file 'pypeflow.egg-info/SOURCES.txt'
> reading manifest file 'pypeflow.egg-info/SOURCES.txt'
> writing manifest file 'pypeflow.egg-info/SOURCES.txt'
> installing library code to build/bdist.linux-x86_64/egg
> running install_lib
> running build_py
> creating build
> creating build/lib.linux-x86_64-2.7
> creating build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/common.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/task.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/data.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/controller.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/do_task.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/pwatcher_bridge.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/__init__.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/util.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/simple_pwatcher_bridge.py -> 
> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/do_support.py -> build/lib.linux-x86_64-2.7/pypeflow
> creating build/lib.linux-x86_64-2.7/pwatcher
> copying ./pwatcher/fs_based.py -> build/lib.linux-x86_64-2.7/pwatcher
> copying ./pwatcher/network_based.py -> build/lib.linux-x86_64-2.7/pwatcher
> copying ./pwatcher/__init__.py -> build/lib.linux-x86_64-2.7/pwatcher
> copying ./pwatcher/blocking.py -> build/lib.linux-x86_64-2.7/pwatcher
> creating build/lib.linux-x86_64-2.7/pwatcher/mains
> copying ./pwatcher/mains/pwatcher.py -> 
> build/lib.linux-x86_64-2.7/pwatcher/mains
> copying ./pwatcher/mains/query_server.py -> 
> build/lib.linux-x86_64-2.7/pwatcher/mains
> copying ./pwatcher/mains/network_heartbeat.py -> 
> build/lib.linux-x86_64-2.7/pwatcher/mains
> copying ./pwatcher/mains/__init__.py -> 
> build/lib.linux-x86_64-2.7/pwatcher/mains
> copying ./pwatcher/mains/pypeflow_example.py -> 
> build/lib.linux-x86_64-2.7/pwatcher/mains
> copying ./pwatcher/mains/fs_heartbeat.py -> 
> build/lib.linux-x86_64-2.7/pwatcher/mains
> copying ./pwatcher/mains/job_start.sh -> 
> build/lib.linux-x86_64-2.7/pwatcher/mains
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/egg
> creating build/bdist.linux-x86_64/egg/pwatcher
> copying build/lib.linux-x86_64-2.7/pwatcher/fs_based.py -> 
> build/bdist.linux-x86_64/egg/pwatcher
> creating build/bdist.linux-x86_64/egg/pwatcher/mains
> copying build/lib.linux-x86_64-2.7/pwatcher/mains/pwatcher.py -> 
> build/bdist.linux-x86_64/egg/pwatcher/mains
> copying build/lib.linux-x86_64-2.7/pwatcher/mains/query_server.py -> 
> build/bdist.linux-x86_64/egg/pwatcher/mains
> copying build/lib.linux-x86_64-2.7/pwatcher/mains/network_heartbeat.py -> 
> build/bdist.linux-x86_64/egg/pwatcher/mains
> copying build/lib.linux-x86_64-2.7/pwatcher/mains/job_start.sh -> 
> build/bdist.linux-x86_64/egg/pwatcher/mains
> copying build/lib.linux-x86_64-2.7/pwatcher/mains/__init__.py -> 
> build/bdist.linux-x86_64/egg/pwatcher/mains
> copying build/lib.linux-x86_64-2.7/pwatcher/mains/pypeflow_example.py -> 
> 

Bug#845937: tiny-initramfs: init binary crashes on 4.8.x kernels - need to rebuild against newer dietlibc

[James Braid]

Package: tiny-initramfs
Version: 0.1-2
Severity: critical

Recent Debian kernels (4.8.x) have disabled support for legacy vsyscall
emulation.

changelog entry from kernel packages:

  * [amd64] Enable LEGACY_VSYSCALL_NONE instead of LEGACY_VSYSCALL_EMULATE.
This breaks (e)glibc 2.13 and earlier, and can be reverted using the
kernel
parameter: vsyscall=emulate

This causes problems with tiny-initramfs as the init binary is linked
against an old version of dietlibc which uses the vsyscall for accessing
the kernel gettimeofday functions. This manifests as the init process being
killed when it attempts to access the vsyscall interface which renders the
system unbootable.

dietlibc 0.33 adds changes to use the kernel vDSO instead of the legacy
vsyscall interface.

I have tested rebuilding tiny-initramfs against the latest dietlibc in
Debian (0.34~cvs20160606-3) and the rebuilt init binary works successfully
on 4.8.x kernels.

Setting severity to critical as this renders systems using tiny-initramfs
unbootable when the upgraded kernel package is installed. It would be great
to get an updated tiny-initramfs package rebuilt against the latest
dietlibc.

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

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

Versions of packages tiny-initramfs depends on:
ii  tiny-initramfs-core  0.1-2

tiny-initramfs recommends no packages.

tiny-initramfs suggests no packages.

-- no debconf information

Bug#844960: marked as done (byobu: FTBFS: python syntax error)

[Debian Bug Tracking System]

Your message dated Sun, 27 Nov 2016 00:00:11 -0500
with message-id 

Bug#845926: marked as done (Cannot install package openbox-lxde-session: trying to overwrite '/etc/xdg/lxsession/LXDE/autostart', which is also in package lxde-common 0.99.2-1)

[Debian Bug Tracking System]

Your message dated Sun, 27 Nov 2016 01:48:31 +
with message-id 
and subject line Bug#845926: fixed in lxde-common 0.99.2-2
has caused the Debian Bug report #845926,
regarding Cannot install package openbox-lxde-session: trying to overwrite 
'/etc/xdg/lxsession/LXDE/autostart', which is also in package lxde-common 
0.99.2-1
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.)


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

Package: openbox-lxde-session
Version: 0.99.2-1
Severity: grave

When trying to install openbox-lxde-session package, dpkg fails with an error 
message:

dpkg: error processing archive .../openbox-lxde-session_0.99.2-1_all.deb 
(--unpack):
 trying to overwrite '/etc/xdg/lxsession/LXDE/autostart', which is also in 
package lxde-common 0.99.2-1
--- End Message ---
--- Begin Message ---
Source: lxde-common
Source-Version: 0.99.2-2

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

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

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

Debian distribution maintenance software
pp.
Andriy Grytsenko  (supplier of updated lxde-common 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, 27 Nov 2016 03:24:54 +0200
Source: lxde-common
Binary: lxde-common openbox-lxde-session
Architecture: source all
Version: 0.99.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian LXDE Maintainers 

Changed-By: Andriy Grytsenko 
Description:
 lxde-common - LXDE common configuration files
 openbox-lxde-session - LXDE session manager and configuration files
Closes: 845926
Changes:
 lxde-common (0.99.2-2) unstable; urgency=medium
 .
   * Fixing conffiles transition from lxde-common to openbox-lxde-session
 (Closes: #845926).
Checksums-Sha1:
 411cc97cee8533383b24750b08a96f24456c1341 2063 lxde-common_0.99.2-2.dsc
 38f09afd9ad949d9ea855b84ef6cf46e303a5645 8524 
lxde-common_0.99.2-2.debian.tar.xz
 f40038c192788fd40547f1808719d81f978e454f 5871 
lxde-common_0.99.2-2_20161127T012704z-c30a8e37.buildinfo
 46becec3ff1c534a38ad5afc9978009ff9489e76 807826 lxde-common_0.99.2-2_all.deb
 93a1d8e9bc4e220e4b3db620b2f3440fe052b4af 18374 
openbox-lxde-session_0.99.2-2_all.deb
Checksums-Sha256:
 f92374b1e9662420551c394d548fddccbd502ada9f8058942e34c2edfd84da9f 2063 
lxde-common_0.99.2-2.dsc
 c673120a6afb225089788b17ff37342f573d62ad27080bda1541dbaf638c4a58 8524 
lxde-common_0.99.2-2.debian.tar.xz
 756f0c3f73e59905798cadfbe7b22be6279961867f370d063f90ecab3f4f9eb8 5871 
lxde-common_0.99.2-2_20161127T012704z-c30a8e37.buildinfo
 0134697f7983245fa76d66a93a97a1527b4c7e85620260793dc4a981ed63878e 807826 
lxde-common_0.99.2-2_all.deb
 e65f9b02275f2cb6db7ce1648c57db9ed9b1bcff339448b00cc1a8e1358a3541 18374 
openbox-lxde-session_0.99.2-2_all.deb
Files:
 24bb89c3791cbefd3991f1bf33686770 2063 x11 optional lxde-common_0.99.2-2.dsc
 5c32af5d8b9e9291ecc84358eff7abd9 8524 x11 optional 
lxde-common_0.99.2-2.debian.tar.xz
 c30a8e370d7cbc0b03605db0d0f43cba 5871 x11 optional 
lxde-common_0.99.2-2_20161127T012704z-c30a8e37.buildinfo
 753ed4c692f070a65612c177efc32ff6 807826 x11 optional 
lxde-common_0.99.2-2_all.deb
 c7cd4e3b4fde87d5e3011f8f5e893bac 18374 x11 optional 
openbox-lxde-session_0.99.2-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCgAGBQJYOjeWAAoJEAV2MC/hidTS/p0P/i4Nn+dyjbVkDrN+ZPFpnr3N
uvLlZz7UZOMGLaCBCZZyNE9X3bIUH7kBUVF4uHSxNjEin9aDKeisCZID3E+JasEp
MDfmP4aEmlMWIB5cDEC61pVJuzsO+j+hN0SM8S4bsX+k7NEo0SogCtZplAwqqCtA
vVIPuJKVVlZPZOBncfqWz/C3Uid3kqk3n/zLFvEjGrnMHVldbXP+8PMmymwCPcXm
g6ChG0ja7UeEFD2eYWTX+2UBS7lEsW5h1lnuQjefP2/PlUBmxg7+mF52PBLQteBE
8f5Vrw2I6Xmo1OjRIgWZM4ys7Z1NEMDSdW4UtlHrS1+ErkfvAy/rlrpk3B3UA+/D
ytyVO5TaVHNQjefRdvECo/sjVmOKU8JTJJcdPywCvzD51v5R3m8mqE+RkRepJ+ln
NatEmgCE2tVybD0zUzfxBdOspRIgci2yjx2ZS5m1YHFiy1qqJdfZ+Rar9qGTQbrq
x1m4jPtYXev7TmK8RxItXg0p2si4J/RzAvi/DTIt6fEcpTt0HVA/NW3kvFAvEU0Y
lUMzRV/YtdHaVEKSeX6gIDVLj9qqeiqwiZl3FsXFOIK400S3NGnwxjVYkOBoDbm8

Processed: Re: Bug#845926: Cannot install package openbox-lxde-session: trying to overwrite '/etc/xdg/lxsession/LXDE/autostart', which is also in package lxde-common 0.99.2-1

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 lxde-common
Bug #845926 [openbox-lxde-session] Cannot install package openbox-lxde-session: 
trying to overwrite '/etc/xdg/lxsession/LXDE/autostart', which is also in 
package lxde-common 0.99.2-1
Bug reassigned from package 'openbox-lxde-session' to 'lxde-common'.
No longer marked as found in versions lxde-common/0.99.2-1.
Ignoring request to alter fixed versions of bug #845926 to the same values 
previously set

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

Bug#845926: Cannot install package openbox-lxde-session: trying to overwrite '/etc/xdg/lxsession/LXDE/autostart', which is also in package lxde-common 0.99.2-1

[Evgeny Kapun]

Control: reassign -1 lxde-common

On 27.11.2016 03:52, Andriy Grytsenko wrote:

I believe it's some dpkg error, just look at list of files in lxde-common
package at https://packages.debian.org/sid/all/lxde-common/filelist:

/etc/xdg/lxpanel/LXDE/config
/etc/xdg/lxpanel/LXDE/panels/panel
/etc/xdg/pcmanfm/LXDE/pcmanfm.conf
/usr/share/doc/lxde-common/README.Debian
/usr/share/doc/lxde-common/changelog.Debian.gz
/usr/share/doc/lxde-common/changelog.gz
/usr/share/doc/lxde-common/copyright
/usr/share/lxde/images/logout-banner.png
/usr/share/lxde/images/lxde-icon.png
/usr/share/lxde/wallpapers/lxde_blue.jpg
/usr/share/lxde/wallpapers/lxde_green.jpg
/usr/share/lxde/wallpapers/lxde_red.jpg

there is no /etc/xdg/lxsession/LXDE/autostart file there! I have no idea
what was happened in your system.



Actually, after further investigation, I think that this file is a conffile 
left from a previous version of lxde-common package. These files should be 
removed by a maintainer script [1]. Since the maintainer script for lxde-common 
package doesn't do this, this is a bug in that package.

[1] https://wiki.debian.org/DpkgConffileHandling

Bug#845926: Cannot install package openbox-lxde-session: trying to overwrite '/etc/xdg/lxsession/LXDE/autostart', which is also in package lxde-common 0.99.2-1

[Andriy Grytsenko]

Ah, forget about previous message, found the problem.
Thank you for a report, fixed version will come soon.

Bug#845926: Cannot install package openbox-lxde-session: trying to overwrite '/etc/xdg/lxsession/LXDE/autostart', which is also in package lxde-common 0.99.2-1

[Andriy Grytsenko]

>Package: openbox-lxde-session
>Version: 0.99.2-1
>Severity: grave

>When trying to install openbox-lxde-session package, dpkg fails with an error 
>message:

> dpkg: error processing archive .../openbox-lxde-session_0.99.2-1_all.deb 
> (--unpack):
>  trying to overwrite '/etc/xdg/lxsession/LXDE/autostart', which is also 
> in package lxde-common 0.99.2-1

I believe it's some dpkg error, just look at list of files in lxde-common
package at https://packages.debian.org/sid/all/lxde-common/filelist:

/etc/xdg/lxpanel/LXDE/config
/etc/xdg/lxpanel/LXDE/panels/panel
/etc/xdg/pcmanfm/LXDE/pcmanfm.conf
/usr/share/doc/lxde-common/README.Debian
/usr/share/doc/lxde-common/changelog.Debian.gz
/usr/share/doc/lxde-common/changelog.gz
/usr/share/doc/lxde-common/copyright
/usr/share/lxde/images/logout-banner.png
/usr/share/lxde/images/lxde-icon.png
/usr/share/lxde/wallpapers/lxde_blue.jpg
/usr/share/lxde/wallpapers/lxde_green.jpg
/usr/share/lxde/wallpapers/lxde_red.jpg

there is no /etc/xdg/lxsession/LXDE/autostart file there! I have no idea
what was happened in your system.

Bug#844534: uftp: FTBFS: encrypt_openssl.c:352:20: error: storage size of 'ctx' isn't known

[Reiner Herrmann]

Control: tags -1 + patch

Hi,

attached is a patch for compatibility with OpenSSL 1.1.

Regards,
  Reiner
diff --git a/debian/patches/openssl1.1.patch b/debian/patches/openssl1.1.patch
new file mode 100644
index 000..960d827
--- /dev/null
+++ b/debian/patches/openssl1.1.patch
@@ -0,0 +1,400 @@
+Author: Reiner Herrmann 
+Description: Fix compatibility with OpenSSL 1.1
+Bug-Debian: https://bugs.debian.org/844534
+
+--- a/encrypt_openssl.c
 b/encrypt_openssl.c
+@@ -349,7 +349,7 @@
+   const unsigned char *src, unsigned int srclen,
+   unsigned char *dest, unsigned int *destlen)
+ {
+-EVP_CIPHER_CTX ctx;
++EVP_CIPHER_CTX *ctx;
+ const EVP_CIPHER *cipher = get_cipher(keytype);
+ int mode, len;
+ 
+@@ -358,32 +358,32 @@
+ return 0;
+ }
+ mode = EVP_CIPHER_mode(cipher);
+-EVP_CIPHER_CTX_init();
+-if (!EVP_EncryptInit_ex(, cipher, NULL, NULL, NULL)) {
++ctx = EVP_CIPHER_CTX_new();
++if (!EVP_EncryptInit_ex(ctx, cipher, NULL, NULL, NULL)) {
+ log_ssl_err("EncryptInit for cipher failed");
+ return 0;
+ }
+ #ifdef EVP_CIPH_GCM_MODE
+ if (mode == EVP_CIPH_GCM_MODE) {
+-if (!EVP_CIPHER_CTX_ctrl(, EVP_CTRL_GCM_SET_IVLEN, GCM_IV_LEN, 0)) {
++if (!EVP_CIPHER_CTX_ctrl(ctx, EVP_CTRL_GCM_SET_IVLEN, GCM_IV_LEN, 0)) {
+ log_ssl_err("EVP_CIPHER_CTX_ctrl for IVLEN failed");
+-EVP_CIPHER_CTX_cleanup();
++EVP_CIPHER_CTX_free(ctx);
+ return 0;
+ }
+ } else if (mode == EVP_CIPH_CCM_MODE) {
+-if (!EVP_CIPHER_CTX_ctrl(, EVP_CTRL_CCM_SET_IVLEN, CCM_IV_LEN, 0)) {
++if (!EVP_CIPHER_CTX_ctrl(ctx, EVP_CTRL_CCM_SET_IVLEN, CCM_IV_LEN, 0)) {
+ log_ssl_err("EVP_CIPHER_CTX_ctrl for IVLEN failed");
+-EVP_CIPHER_CTX_cleanup();
++EVP_CIPHER_CTX_free(ctx);
+ return 0;
+ }
+-if (!EVP_CIPHER_CTX_ctrl(, EVP_CTRL_CCM_SET_TAG, CCM_TAG_LEN, 0)) {
++if (!EVP_CIPHER_CTX_ctrl(ctx, EVP_CTRL_CCM_SET_TAG, CCM_TAG_LEN, 0)) {
+ log_ssl_err("EVP_CIPHER_CTX_ctrl for tag len failed");
+-EVP_CIPHER_CTX_cleanup();
++EVP_CIPHER_CTX_free(ctx);
+ return 0;
+ }
+ }
+ #endif
+-if (!EVP_EncryptInit_ex(, NULL, NULL, key, IV)) {
++if (!EVP_EncryptInit_ex(ctx, NULL, NULL, key, IV)) {
+ log_ssl_err("EncryptInit for key/IV failed");
+ return 0;
+ }
+@@ -391,53 +391,53 @@
+ #ifdef EVP_CIPH_GCM_MODE
+ if ((mode == EVP_CIPH_GCM_MODE) || (mode == EVP_CIPH_CCM_MODE)) {
+ if (mode == EVP_CIPH_CCM_MODE) {
+-if (!EVP_EncryptUpdate(, NULL, , NULL, srclen)) {
++if (!EVP_EncryptUpdate(ctx, NULL, , NULL, srclen)) {
+ log_ssl_err("EncryptUpdate for datalen failed");
+-EVP_CIPHER_CTX_cleanup();
++EVP_CIPHER_CTX_free(ctx);
+ return 0;
+ }
+ }
+ if ((aad != NULL) && (aadlen > 0)) {
+-if (!EVP_EncryptUpdate(, NULL, , aad, aadlen)) {
++if (!EVP_EncryptUpdate(ctx, NULL, , aad, aadlen)) {
+ log_ssl_err("EncryptUpdate for authdata failed");
+-EVP_CIPHER_CTX_cleanup();
++EVP_CIPHER_CTX_free(ctx);
+ return 0;
+ }
+ }
+ }
+ #endif
+-if (!EVP_EncryptUpdate(, dest, , src, srclen)) {
++if (!EVP_EncryptUpdate(ctx, dest, , src, srclen)) {
+ log_ssl_err("EncryptUpdate for data failed");
+-EVP_CIPHER_CTX_cleanup();
++EVP_CIPHER_CTX_free(ctx);
+ return 0;
+ }
+ *destlen = len;
+-if (!EVP_EncryptFinal_ex(, dest + *destlen, )) {
++if (!EVP_EncryptFinal_ex(ctx, dest + *destlen, )) {
+ log_ssl_err("EncryptFinal failed");
+-EVP_CIPHER_CTX_cleanup();
++EVP_CIPHER_CTX_free(ctx);
+ return 0;
+ }
+ #ifdef EVP_CIPH_GCM_MODE
+ if (mode == EVP_CIPH_GCM_MODE) {
+-if (!EVP_CIPHER_CTX_ctrl(, EVP_CTRL_GCM_GET_TAG, GCM_TAG_LEN,
++if (!EVP_CIPHER_CTX_ctrl(ctx, EVP_CTRL_GCM_GET_TAG, GCM_TAG_LEN,
+  dest + *destlen)) {
+ log_ssl_err("EVP_CIPHER_CTX_ctrl for get tag failed");
+-EVP_CIPHER_CTX_cleanup();
++EVP_CIPHER_CTX_free(ctx);
+ return 0;
+ }
+ len += GCM_TAG_LEN;
+ } else if (mode == EVP_CIPH_CCM_MODE) {
+-if (!EVP_CIPHER_CTX_ctrl(, EVP_CTRL_CCM_GET_TAG, CCM_TAG_LEN,
++if (!EVP_CIPHER_CTX_ctrl(ctx, EVP_CTRL_CCM_GET_TAG, CCM_TAG_LEN,
+  dest + *destlen)) {
+ log_ssl_err("EVP_CIPHER_CTX_ctrl for get tag failed");
+-EVP_CIPHER_CTX_cleanup();
++EVP_CIPHER_CTX_free(ctx);
+ return 0;
+ }
+ len += CCM_TAG_LEN;
+ }
+ #endif
+ *destlen += len;
+-EVP_CIPHER_CTX_cleanup();
++

Processed: Re: uftp: FTBFS: encrypt_openssl.c:352:20: error: storage size of 'ctx' isn't known

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #844534 [src:uftp] uftp: FTBFS: encrypt_openssl.c:352:20: error: storage 
size of 'ctx' isn't known
Added tag(s) patch.

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

Bug#845929: lua-sandbox FTBFS on 32bit architectures: test_heka_message fails

[Adrian Bunk]

Source: lua-sandbox
Version: 1.2.1-2
Severity: serious

https://buildd.debian.org/status/package.php?p=lua-sandbox

...
  Start  7: test_heka_message
 7/14 Test  #7: test_heka_message ..***Failed0.00 sec
line: 345 (hlen == 5 + i) i: 4 received 5
Tests run: 9

  Start  8: test_heka_message_matcher
...

Bug#845926: Cannot install package openbox-lxde-session: trying to overwrite '/etc/xdg/lxsession/LXDE/autostart', which is also in package lxde-common 0.99.2-1

[Evgeny Kapun]

Package: openbox-lxde-session
Version: 0.99.2-1
Severity: grave

When trying to install openbox-lxde-session package, dpkg fails with an error 
message:

dpkg: error processing archive .../openbox-lxde-session_0.99.2-1_all.deb 
(--unpack):
 trying to overwrite '/etc/xdg/lxsession/LXDE/autostart', which is also in 
package lxde-common 0.99.2-1

Bug#831944: marked as done (pyorbit: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop.)

[Debian Bug Tracking System]

Your message dated Sun, 27 Nov 2016 00:33:48 +
with message-id 
and subject line Bug#831944: fixed in pyorbit 2.24.0-7.2
has caused the Debian Bug report #831944,
regarding pyorbit: FTBFS with dpkg-buildpackage -A: make: *** No rule to make 
target 'build-indep'.  Stop.
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.)


-- 
831944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyorbit
Version: 2.24.0-7.1
Severity: important
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.


The specific error below usually happens when there is no build-indep target in
debian/rules.

If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now. If not, debian/rules
should be modified so that the build-indep and binary-indep target generates
the architecture independent packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
>  debian/rules build-indep
> make: *** No rule to make target 'build-indep'.  Stop.

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/pyorbit_2.24.0-7.1_unstable_archallonly.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: pyorbit
Source-Version: 2.24.0-7.2

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated pyorbit 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, 27 Nov 2016 00:55:45 +0100
Source: pyorbit
Binary: python-pyorbit python-pyorbit-dev python-pyorbit-omg
Architecture: source
Version: 2.24.0-7.2
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Bacher 
Changed-By: Dr. Tobias Quathamer 
Description:
 python-pyorbit - A Python language binding for the ORBit2 CORBA implementation
 python-pyorbit-dev - PyORBit: development files
 python-pyorbit-omg - PyORBit - Python CORBA OMG standard files
Closes: 831944
Changes:
 pyorbit (2.24.0-7.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS with dpkg-buildpackage -A. Thanks to
 Santiago Vila  for the patch. Closes: #831944
   * Remove Loic Minier from Uploaders, due to Debian GNOME team policy
Checksums-Sha1:
 dbd593679ebefac3f6593622eb26e90f55b057de 2014 pyorbit_2.24.0-7.2.dsc
 6f1e218a374012b352757062b8b16caa5beed612 6005 pyorbit_2.24.0-7.2.diff.gz
Checksums-Sha256:
 11e3762433c33d621dd0c4ead8cc24b9b74c37cce378c4b939ce268a9a9d271a 2014 
pyorbit_2.24.0-7.2.dsc
 faeae5bd40fae729b240d0795ed0fdf6b4f87926afd1b25776fb609d532c8511 6005 
pyorbit_2.24.0-7.2.diff.gz
Files:
 552e9e1160cea1968c871e4b3c5b3e34 2014 python optional pyorbit_2.24.0-7.2.dsc
 5c1bb17c1c79f8304762a63bd759e805 6005 python optional 
pyorbit_2.24.0-7.2.diff.gz

-BEGIN 

Bug#831944: NMU of pyorbit

[Dr. Tobias Quathamer]

Hi,

please find the attached patch of the NMU I've just uploaded.

Regards,
Tobias
diff -u pyorbit-2.24.0/debian/changelog pyorbit-2.24.0/debian/changelog
--- pyorbit-2.24.0/debian/changelog
+++ pyorbit-2.24.0/debian/changelog
@@ -1,3 +1,12 @@
+pyorbit (2.24.0-7.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with dpkg-buildpackage -A. Thanks to
+Santiago Vila  for the patch. Closes: #831944
+  * Remove Loic Minier from Uploaders, due to Debian GNOME team policy
+
+ -- Dr. Tobias Quathamer   Sun, 27 Nov 2016 00:55:45 +0100
+
 pyorbit (2.24.0-7.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u pyorbit-2.24.0/debian/control pyorbit-2.24.0/debian/control
--- pyorbit-2.24.0/debian/control
+++ pyorbit-2.24.0/debian/control
@@ -6,7 +6,7 @@
 Section: python
 Priority: optional
 Maintainer: Sebastien Bacher 
-Uploaders: Debian GNOME Maintainers , Josselin Mouette , Loic Minier 
+Uploaders: Debian GNOME Maintainers , Josselin Mouette 
 Build-Depends: debhelper (>= 5.0.37.2),
dh-python,
gnome-pkg-tools (>= 0.10),
diff -u pyorbit-2.24.0/debian/rules pyorbit-2.24.0/debian/rules
--- pyorbit-2.24.0/debian/rules
+++ pyorbit-2.24.0/debian/rules
@@ -51,6 +51,10 @@
 	$(MAKE) -C build-$*
 	touch $@
 
+build-arch: build
+
+build-indep: build
+
 build: $(PYVERS:%=build-%/build-stamp)
 
 install-clean:
@@ -110 +114 @@
-.PHONY: build clean binary-indep binary-arch binary install patch unpatch
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install patch unpatch


signature.asc
Description: OpenPGP digital signature

Bug#831921: marked as done (daemontools: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop.)

[Debian Bug Tracking System]

Your message dated Sun, 27 Nov 2016 00:03:51 +
with message-id 
and subject line Bug#831921: fixed in daemontools 1:0.76-6.1
has caused the Debian Bug report #831921,
regarding daemontools: FTBFS with dpkg-buildpackage -A: make: *** No rule to 
make target 'build-indep'.  Stop.
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.)


-- 
831921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: daemontools
Version: 1:0.76-6
Severity: important
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.


The specific error below usually happens when there is no build-indep target in
debian/rules.

If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now. If not, debian/rules
should be modified so that the build-indep and binary-indep target generates
the architecture independent packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
>  debian/rules build-indep
> make: *** No rule to make target 'build-indep'.  Stop.

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/daemontools_0.76-6_unstable_archallonly.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: daemontools
Source-Version: 1:0.76-6.1

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated daemontools 
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, 27 Nov 2016 00:26:56 +0100
Source: daemontools
Binary: daemontools daemontools-run
Architecture: source
Version: 1:0.76-6.1
Distribution: unstable
Urgency: medium
Maintainer: Gerrit Pape 
Changed-By: Dr. Tobias Quathamer 
Description:
 daemontools - collection of tools for managing UNIX services
 daemontools-run - daemontools service supervision
Closes: 776876 793003 819036 831921
Changes:
 daemontools (1:0.76-6.1) unstable; urgency=medium
 .
   [ Jan Mojzis ]
   * Non-maintainer upload.
   * supervise.c: restart the monitored process when
 fork(2) fails (Closes: #819036)
   * d/rules: fix mtimes before building binary package to produce
 reproducible output (Closes: #793003) (Closes: #776876)
   * d/rules: do not FTBFS with dpkg-buildpackage -A (thx Santiago
 Vila) (Closes: #831921)
   * d/implicit: fixed md5sums permissions 0664 -> 0644
   * d/control: bump to standards-version 3.9.8
   * d/control: fixed the description
 .
   [ Dr. Tobias Quathamer ]
   * New upload with all changes from Jan, his previous NMU
 to DELAYED/5 did not end up in unstable.
Checksums-Sha1:
 3eec85af794cad3394156a79cf4ae28df04905dc 1665 daemontools_0.76-6.1.dsc
 19bd2fcd469cc24a75985d25dfde896f792cda73 19739 daemontools_0.76-6.1.diff.gz
Checksums-Sha256:
 

Bug#828269: [htcondor-debian] Bug#828269: Info from upstream

[Tim Theisen]

I have been working on getting HTCondor working with OpenSSL 1.1.

Although we would prefer to compile with VOMS support, it is preferable
to turn this off, rather than miss getting into stretch. I have a patch
to turn off compilation with VOMS. (rules.patch) We should revert this
patch when the VOMS folks fix up their OpenSSL issues.

Once the VOMS dependency was eliminated, I found a few minor changes
that needed to be addressed within HTCondor itself. I have included a
patch to 8.4.9 (OpenSSL1.1.patch). This update will be released as part
of the HTCondor 8.4.10 release, expected on December 1st.

Let me know if you need anything more, ...Tim

On 11/04/2016 06:31 AM, Michael Hanke wrote:
> Relaying information from upstream's triaging:
>
>
> 
> I concluded that the problem was not with HTCondor. It had to do with the
> following packages: libglobus-gsi-proxy-core, libglobus-gsi-proxy-ssl and
> voms. The Globus folks addressed the first two issues. However, the VOMS issue
> (#828595) is a blocker for us.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828595
> https://github.com/italiangrid/voms/issues/50
> 
> ___
> htcondor-debian mailing list
> htcondor-deb...@cs.wisc.edu
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-debian

-- 
Tim Theisen
Release Manager
HTCondor & Open Science Grid
Center for High Throughput Computing
Department of Computer Sciences
University of Wisconsin - Madison
4261 Computer Sciences and Statistics
1210 W Dayton St
Madison, WI 53706-1685
+1 608 265 5736

diff --git a/src/condor_includes/condor_crypt_3des.h b/src/condor_includes/condor_crypt_3des.h
index e2967d8..dc29b6a 100644
--- a/src/condor_includes/condor_crypt_3des.h
+++ b/src/condor_includes/condor_crypt_3des.h
@@ -61,7 +61,7 @@ class Condor_Crypt_3des : public Condor_Crypt_Base {
 //--
 // Private constructor
 //--
-des_key_schedule  keySchedule1_, keySchedule2_, keySchedule3_;
+DES_key_schedule  keySchedule1_, keySchedule2_, keySchedule3_;
 unsigned char ivec_[8];
 int   num_;
 };
diff --git a/src/condor_io/condor_auth_ssl.cpp b/src/condor_io/condor_auth_ssl.cpp
index b8bb6cf..3c366b3 100644
--- a/src/condor_io/condor_auth_ssl.cpp
+++ b/src/condor_io/condor_auth_ssl.cpp
@@ -36,7 +36,9 @@
 #endif
 
 // Symbols from libssl
+#if OPENSSL_VERSION_NUMBER < 0x1010L
 static long (*SSL_CTX_ctrl_ptr)(SSL_CTX *, int, long, void *) = NULL;
+#endif
 static void (*SSL_CTX_free_ptr)(SSL_CTX *) = NULL;
 static int (*SSL_CTX_load_verify_locations_ptr)(SSL_CTX *, const char *, const char *) = NULL;
 #if OPENSSL_VERSION_NUMBER < 0x1000L
@@ -55,8 +57,12 @@ static void (*SSL_free_ptr)(SSL *) = NULL;
 static int (*SSL_get_error_ptr)(const SSL *, int) = NULL;
 static X509 *(*SSL_get_peer_certificate_ptr)(const SSL *) = NULL;
 static long (*SSL_get_verify_result_ptr)(const SSL *) = NULL;
+#if OPENSSL_VERSION_NUMBER < 0x1010L
 static int (*SSL_library_init_ptr)() = NULL;
 static void (*SSL_load_error_strings_ptr)() = NULL;
+#else
+static int (*OPENSSL_init_ssl_ptr)(uint64_t, const OPENSSL_INIT_SETTINGS *) = NULL;
+#endif
 static SSL *(*SSL_new_ptr)(SSL_CTX *) = NULL;
 static int (*SSL_read_ptr)(SSL *, void *, int) = NULL;
 static void (*SSL_set_bio_ptr)(SSL *, BIO *, BIO *) = NULL;
@@ -79,7 +85,11 @@ Condor_Auth_SSL :: Condor_Auth_SSL(ReliSock * sock, int /* remote */)
 
 Condor_Auth_SSL :: ~Condor_Auth_SSL()
 {
+#if OPENSSL_VERSION_NUMBER < 0x1000L
 ERR_remove_state( 0 );
+#elif OPENSSL_VERSION_NUMBER < 0x1010L
+ERR_remove_thread_state( 0 );
+#endif
 	if(m_crypto) delete(m_crypto);
 }
 
@@ -96,7 +106,9 @@ bool Condor_Auth_SSL::Initialize()
 
 	if ( Condor_Auth_Kerberos::Initialize() == false ||
 		 (dl_hdl = dlopen(LIBSSL_SO, RTLD_LAZY)) == NULL ||
+#if OPENSSL_VERSION_NUMBER < 0x1010L
 		 !(SSL_CTX_ctrl_ptr = (long (*)(SSL_CTX *, int, long, void *))dlsym(dl_hdl, "SSL_CTX_ctrl")) ||
+#endif
 		 !(SSL_CTX_free_ptr = (void (*)(SSL_CTX *))dlsym(dl_hdl, "SSL_CTX_free")) ||
 		 !(SSL_CTX_load_verify_locations_ptr = (int (*)(SSL_CTX *, const char *, const char *))dlsym(dl_hdl, "SSL_CTX_load_verify_locations")) ||
 #if OPENSSL_VERSION_NUMBER < 0x1000L
@@ -115,8 +127,12 @@ bool Condor_Auth_SSL::Initialize()
 		 !(SSL_get_error_ptr = (int (*)(const SSL *, int))dlsym(dl_hdl, "SSL_get_error")) ||
 		 !(SSL_get_peer_certificate_ptr = (X509 *(*)(const SSL *))dlsym(dl_hdl, "SSL_get_peer_certificate")) ||
 		 !(SSL_get_verify_result_ptr = (long (*)(const SSL *))dlsym(dl_hdl, "SSL_get_verify_result")) ||
+#if OPENSSL_VERSION_NUMBER < 0x1010L
 		 !(SSL_library_init_ptr = (int (*)())dlsym(dl_hdl, "SSL_library_init")) ||
 		 !(SSL_load_error_strings_ptr = (void (*)())dlsym(dl_hdl, "SSL_load_error_strings")) ||
+#else
+		 !(OPENSSL_init_ssl_ptr = (int (*)(uint64_t, const OPENSSL_INIT_SETTINGS *))dlsym(dl_hdl, 

Bug#844144: marked as done (w1retap: FTBFS: ld: cannot find -lowfat)

[Debian Bug Tracking System]

Your message dated Sat, 26 Nov 2016 23:35:22 +
with message-id 
and subject line Bug#844144: fixed in w1retap 1.4.4-2
has caused the Debian Bug report #844144,
regarding w1retap: FTBFS: ld: cannot find -lowfat
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.)


-- 
844144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: w1retap
Version: 1.4.4-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-2016 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):
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -rdynamic  -Wl,--export-dynamic -lgmodule-2.0 
> -pthread -lglib-2.0 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o hbhttest 
> hbhttest.o -L. -lowfat -lw1common -lm -lxml2 -lrt -lm 
> libtool: link: gcc -shared  -fPIC -DPIC  .libs/ds2480ut.o .libs/linuxlnk.o 
> .libs/owllu.o .libs/ownetu.o .libs/owsesu.o .libs/owtrnu.o   -Wl,-rpath 
> -Wl,/<>/src/libusblinux300/.libs -Wl,-rpath 
> -Wl,/usr/lib/x86_64-linux-gnu/w1retap -L. 
> /<>/src/libusblinux300/.libs/libw1common.so -lxml2 -lrt -lm  -g 
> -O2 -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed  
>  -pthread -Wl,-soname -Wl,libw1serial.so.0 -o .libs/libw1serial.so.0.0.0
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -rdynamic 
> -Wl,--export-dynamic -pthread -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed 
> -o .libs/gethumd gethumd.o findtype.o  -lgmodule-2.0 -lglib-2.0 -L. -lowfat 
> /<>/src/libusblinux300/.libs/libw1common.so -lxml2 -lrt -lm 
> -pthread -Wl,-rpath -Wl,/usr/lib/x86_64-linux-gnu/w1retap
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -rdynamic 
> -Wl,--export-dynamic -pthread -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed 
> -o .libs/setds2409 setds2409.o  -lgmodule-2.0 -lglib-2.0 -L. -lowfat 
> /<>/src/libusblinux300/.libs/libw1common.so -lxml2 -lrt -lm 
> -pthread -Wl,-rpath -Wl,/usr/lib/x86_64-linux-gnu/w1retap
> /usr/bin/ld: cannot find -lowfat
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -rdynamic 
> -Wl,--export-dynamic -pthread -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed 
> -o .libs/counter counter.o findtype.o  -lgmodule-2.0 -lglib-2.0 -L. -lowfat 
> /<>/src/libusblinux300/.libs/libw1common.so -lxml2 -lrt -lm 
> -pthread -Wl,-rpath -Wl,/usr/lib/x86_64-linux-gnu/w1retap
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/11/w1retap_1.4.4-1_unstable.log

This failure happens on a CPU with TSX extensions available, but is not
reproducible on a machine without them. For context, I recommend reading the
thread starting at https://lists.debian.org/debian-devel/2016/11/msg00210.html

The node used is an Amazon EC2 VM with 64 cores. /proc/cpuinfo says:
   model: 79
   model name : Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
   stepping : 1

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: w1retap
Source-Version: 1.4.4-2

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

Debian distribution maintenance software
pp.
Thomas Stewart  (supplier of updated w1retap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Nov 

Bug#844081: Reproducer

[Christian Geier]

Hi Filip,
could you perhaps run the attached file on the test machine (with
`py.test vdir_test.py`, py.test is needed for the creation of a temp
directory).

On my machine the output looks like this:
[(0, 10), (0.0001, 8), (0.001, 0), (0.01, 0), (0.1, 0), (1, 0)]

Similar experiments before made me choose the current delay.

Best regards,
Christian

Quoting Filip Pytloun (2016-11-24 00:20:50)
> On 2016/11/24 00:00, Santiago Vila wrote:
> > Try using a chroot without union-type=overlay.
> 
> Unfortunately it will result in the same error :-/
import os
import time


def get_etag_from_file(f):
'''Get mtime-based etag from a filepath or file-like object.

This function will flush/sync the file as much as necessary to obtain a
correct mtime.
'''
stat = os.stat(f)
mtime = getattr(stat, 'st_mtime_ns', None)
if mtime is None:
mtime = stat.st_mtime
return '{:.9f}'.format(mtime)


def test_etag(tmpdir):
fpath = os.path.join(str(tmpdir), 'foo')
stats = dict()
for delay in [0, 0.0001, 0.001, 0.01, 0.1, 1]:
failed = list()
for one in range(10):

file_ = open(fpath, 'w')
file_.write('foo')
file_.close()

old_etag = get_etag_from_file(fpath)
time.sleep(delay)

file_ = open(fpath, 'w')
file_.write('bar')
file_.close()

new_etag = get_etag_from_file(fpath)

if old_etag == new_etag:
failed.append(
(one, new_etag)
)
stats[delay] = len(failed)
print(sorted(stats.items()))
assert False  # here to make sure we get the print output via py.test

Bug#806627: marked as done (libconfig: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

[Debian Bug Tracking System]

Your message dated Sat, 26 Nov 2016 22:49:54 +
with message-id 
and subject line Bug#806627: fixed in libconfig 1.5-0.3
has caused the Debian Bug report #806627,
regarding libconfig: FTBFS when built with dpkg-buildpackage -A (No such file 
or directory)
to be marked as done.

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

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


-- 
806627: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libconfig
Version: 1.5-0.2
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel --with autoreconf
   dh_testdir -i -O--parallel
   dh_autoreconf -i -O--parallel
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `aux-build'.
libtoolize: copying file `aux-build/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'

[... snipped ...]

[18] [19] [20] [21] [22] [23] [24] [25] [26] Chapter 5 [27] [28] Chapter 6
[29] [30]
Underfull \hbox (badness 1) in paragraph at lines 2018--2019
 @texttt ([-+]?([0-9]*)?\.[0-9]*([eE][-+]?[0-9]+)?)|([-+]([0-
Appendix A [31] [32] (/<>/doc/LGPL.texi
[33] [34] [35] [36] [37] [38] [39] [40]) (Function Index) [41] [42]
(./libconfig.fns [43]) (Type Index) [44] (./libconfig.tps) (Concept Index)
[45] [46] (./libconfig.cps) [47] [48] )
(see the transcript file for additional information) 
Output written on libconfig.pdf (52 pages, 306180 bytes).
Transcript written on libconfig.log.
make[2]: Leaving directory '/<>/doc'
make[1]: Leaving directory '/<>'
   dh_auto_test -i -O--parallel
make -j1 test
make[1]: Entering directory '/<>'
cd tests && ./libconfig_tests
/bin/bash: ./libconfig_tests: No such file or directory
Makefile:871: recipe for target 'test' failed
make[1]: *** [test] Error 127
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 test returned exit code 2
debian/rules:14: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one. The common hints are:

* If the only architecture-independent packages are dummy transitional
ones and they were released with jessie, the easy fix is to drop them
now.

* When using "dh", it is allowed to use (independently)
optional targets override_dh_foo-arch and override_dh_foo-indep
(for several values of "foo").


Once that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, the package would be suitable to be uploaded in source-only
form if you wish.

Thanks.
--- End Message ---
--- Begin Message ---
Source: libconfig
Source-Version: 1.5-0.3

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated libconfig 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, 26 Nov 2016 23:19:25 +0100
Source: libconfig
Binary: libconfig9 libconfig++9v5 libconfig-dev libconfig8-dev libconfig++-dev 
libconfig++8-dev libconfig-dbg libconfig++-dbg libconfig-doc
Architecture: source
Version: 1.5-0.3
Distribution: unstable
Urgency: medium
Maintainer: Jonathan McCrohan 
Changed-By: Dr. Tobias Quathamer 
Description:
 libconfig++-dbg - parsing/manipulation of structured config files (C++ debug 
symbol
 libconfig++-dev - parsing/manipulation of structured config files (C++ 

Bug#806627: NMU of libconfig

[Dr. Tobias Quathamer]

Hi,

please find the attached patch of the NMU I've just uploaded.

Regards,
Tobias
diff -Nru libconfig-1.5/debian/changelog libconfig-1.5/debian/changelog
--- libconfig-1.5/debian/changelog	2015-08-04 17:20:08.0 +0200
+++ libconfig-1.5/debian/changelog	2016-11-26 23:19:25.0 +0100
@@ -1,3 +1,12 @@
+libconfig (1.5-0.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when built with dpkg-buildpackage -A.
+Thanks to Santiago Vila  (Closes: #806627)
+  * Remove Jose Luis Tallon from Uploaders list. (Closes: #838077)
+
+ -- Dr. Tobias Quathamer   Sat, 26 Nov 2016 23:19:25 +0100
+
 libconfig (1.5-0.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libconfig-1.5/debian/control libconfig-1.5/debian/control
--- libconfig-1.5/debian/control	2015-08-04 17:20:08.0 +0200
+++ libconfig-1.5/debian/control	2016-11-26 23:19:25.0 +0100
@@ -1,7 +1,6 @@
 Source: libconfig
 Priority: optional
 Maintainer: Jonathan McCrohan 
-Uploaders: Jose Luis Tallon 
 Build-Depends: debhelper (>= 9), dh-autoreconf, texinfo, g++ (>= 4:5)
 Build-Depends-Indep: texlive-latex-base, texlive-fonts-recommended
 Standards-Version: 3.9.6
@@ -16,7 +15,7 @@
 Description: parsing/manipulation of structured configuration files
  This library features a fully reentrant parser and includes bindings for
  both the C and C++ programming languages. It runs on modern POSIX-compliant
- systems such as Linux, Solaris, and Mac OS X (Darwin), as well as on 
+ systems such as Linux, Solaris, and Mac OS X (Darwin), as well as on
  Microsoft Windows 2000/XP and later (Visual Studio or MinGW).
  .
  This library allows parsing, manipulating and writing structured configuration
@@ -32,7 +31,7 @@
 Description: parsing/manipulation of structured configuration files (C++ binding)
  This library features a fully reentrant parser and includes bindings for
  both the C and C++ programming languages. It runs on modern POSIX-compliant
- systems such as Linux, Solaris, and Mac OS X (Darwin), as well as on 
+ systems such as Linux, Solaris, and Mac OS X (Darwin), as well as on
  Microsoft Windows 2000/XP and later (Visual Studio or MinGW).
  .
  This library allows parsing, manipulating and writing structured configuration
@@ -51,7 +50,7 @@
 Description: parsing/manipulation of structured config files (development)
  This library features a fully reentrant parser and includes bindings for
  both the C and C++ programming languages. It runs on modern POSIX-compliant
- systems such as Linux, Solaris, and Mac OS X (Darwin), as well as on 
+ systems such as Linux, Solaris, and Mac OS X (Darwin), as well as on
  Microsoft Windows 2000/XP and later (Visual Studio or MinGW).
  .
  This library allows parsing, manipulating and writing structured configuration
@@ -86,7 +85,7 @@
 Description: parsing/manipulation of structured config files (C++ development)
  This library features a fully reentrant parser and includes bindings for
  both the C and C++ programming languages. It runs on modern POSIX-compliant
- systems such as Linux, Solaris, and Mac OS X (Darwin), as well as on 
+ systems such as Linux, Solaris, and Mac OS X (Darwin), as well as on
  Microsoft Windows 2000/XP and later (Visual Studio or MinGW).
  .
  This library allows parsing, manipulating and writing structured configuration
diff -Nru libconfig-1.5/debian/rules libconfig-1.5/debian/rules
--- libconfig-1.5/debian/rules	2015-08-04 17:20:08.0 +0200
+++ libconfig-1.5/debian/rules	2016-11-26 23:19:25.0 +0100
@@ -3,6 +3,8 @@
 # Uncomment this to turn on verbose mode.
 # # export DH_VERBOSE=1
 
+override_dh_auto_test-indep:
+
 override_dh_auto_build-indep:
 	$(MAKE) -C doc pdf
 


signature.asc
Description: OpenPGP digital signature

Bug#805989: marked as done (accountsservice: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

[Debian Bug Tracking System]

Your message dated Sat, 26 Nov 2016 22:19:59 +
with message-id 
and subject line Bug#805989: fixed in accountsservice 0.6.40-4
has caused the Debian Bug report #805989,
regarding accountsservice: FTBFS when built with dpkg-buildpackage -A (No such 
file or directory)
to be marked as done.

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

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


-- 
805989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:accountsservice
Version: 0.6.40-3
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 fakeroot debian/rules binary-indep
dh binary-indep --parallel --with=autoreconf,systemd
   dh_testroot -i -O--parallel
   dh_prep -i -O--parallel
   dh_auto_install -i -O--parallel
make -j1 install DESTDIR=/<>/debian/tmp 
AM_UPDATE_INFO_DIR=no
make[1]: Entering directory '/<>'
Making install in src
make[2]: Entering directory '/<>/src'
make  install-recursive
make[3]: Entering directory '/<>/src'
Making install in .
make[4]: Entering directory '/<>/src'
make[5]: Entering directory '/<>/src'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/accountsservice'
  /bin/bash ../libtool   --mode=install /usr/bin/install -c accounts-daemon 
'/<>/debian/tmp/usr/lib/accountsservice'
libtool: install: /usr/bin/install -c accounts-daemon 
/<>/debian/tmp/usr/lib/accountsservice/accounts-daemon
make  install-data-hook
make[6]: Entering directory '/<>/src'
/bin/mkdir -p "/<>/debian/tmp/var/lib/AccountsService/users"
/bin/mkdir -p "/<>/debian/tmp/var/lib/AccountsService/icons"
make[6]: Leaving directory '/<>/src'

[... snipped ...]

cat debian/accountsservice.install debian/accountsservice.install.linux.in > 
debian/accountsservice.install.linux
dh_install
# patch is only applied conditionally, only install when present
if [ -d debian/tmp/usr/share/language-tools ]; then \
cp -r debian/tmp/usr/share/language-tools 
debian/accountsservice/usr/share/; \
fi
cp: cannot create directory 'debian/accountsservice/usr/share/': No such file 
or directory
debian/rules:35: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:12: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one, but I can give some general hints:

* If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now.
 
* If not, debian/rules should be modified so that the binary-indep
target works in all cases, even when binary-arch is not used (this is
what the "Architecture: all" autobuilder does). For that:

* If you are using debhelper, you might want to use options -a and -i
for dh_* commands so that they do not act on packages they do not
have to act.

* Also, if you are using dh, the (independently) optional targets
override_dh_foo-arch and override_dh_foo-indep (for several values
of "foo") may be useful to write a debian/rules which behaves exactly
as desired.


After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B"
work properly, this package will be suitable to be uploaded in
source-only form if you wish (you might want to try it).

Thanks.
--- End Message ---
--- Begin Message ---
Source: accountsservice
Source-Version: 0.6.40-4

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated accountsservice 
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

Bug#845757: geneweb FTBFS on mipsel: dpkg-deb (subprocess): compressing tar member: lzma error: Cannot allocate memory

[Guillaume Brochu]

Dear Adrian,


Thank you for this explanation about the cause of the FTBFS on mipsel.

If I understand well, the "cannot allocate memory" error with lzma on 
mipsel is caused by the high compression level 9, while the default 
value for xz compression is 6.


This modification was introduced in June 2012:

https://anonscm.debian.org/cgit/collab-maint/geneweb.git/commit/?id=16cddde963e4169c09bfe49cb6949fe0dc484f0c

At first sight, I don't see any reason to use compression level 9, so I 
will apply your patch on the git repository.



Best regards,


Guillaume Brochu

Bug#845753: Treescape fails to build on i386 and armhf architecture

[Andreas Tille]

Hi,

in the Debian bug tracking system you can find a bug report about the
build failure:

https://bugs.debian.org/845753

The build log for i386 says:


** preparing package for lazy loading
Creating a generic function for 'toJSON' from package 'jsonlite' in package 
'googleVis'
Warning in rgl.init(initValue, onlyNULL) :
  RGL: unable to open X11 display
Warning: 'rgl_init' failed, running with rgl.useNULL = TRUE
Error: segfault from C stack overflow


I admit I have no idea how to track this down.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#845752: ShortRead fails do build on armel architecture with C stack overflow

[Andreas Tille]

Hi,

the Debian bug tracker contains a bug report that ShortRead fails to
build on armel architecture (while any other Debian architecture seems
to be fine).  Please have a look here:

   https://bugs.debian.org/845752

I admit I have no idea how to track this issue down.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#787956: raising the severity, prevents usage of the multilib packages

[Matthias Klose]

On 26.11.2016 20:35, Mark Brown wrote:
> On Sat, Nov 26, 2016 at 07:52:26PM +0100, Matthias Klose wrote:
>> On 26.11.2016 19:42, Mark Brown wrote:
>>> On Sat, Nov 26, 2016 at 03:56:21PM +0100, Matthias Klose wrote:
> 
>>> Please allow at least a little time for a response, I've no real idea
>>> what you're even asking for here.
> 
>> well, I asked you in private before, without getting replies on all messages 
>> and
>> proposals.
> 
> You sent me a mail last week asking for some additional multilib
> packages for x32 ABI which seemed a bit strange at this point in the
> release cycle and not that urgent as a new ABI would be at most
> wishlist.  I'd been intending to have a look to try to work out what's
> going on with x32 over the weekend.  I'm having a hard time relating
> that to what you're talking about here though I do see you mentioned
> that this was for "libgphobos (gdc runtime)" in both.
> 
>> This exactly is the correct issue, not "some random bug".
> 
> I'm afraid I'm still unclear what you are trying to do or why.

well, you removed the example from your reply and didn't comment on it.

> This is
> a bug about trying to use the lib32z1-dev package, your private mails
> were about adding x32 multilib packages and I'm really confused about
> how either of these things relates to the shared libgphobos you keep
> mentioning.  The proposed changes below don't have anything to do with
> x32 either so I'm just completely confused now.

I'm filing a separate issue for the x32 multilibs.

> Can you please provide a clear, from first steps description of what's
> needed and why?

again, here is the example which you removed:

$ cat tst.c
#include 
$ gcc -m32 -c tst.c
In file included from tst.c:1:0:
/usr/include/zlib.h:34:19: fatal error: zconf.h: No such file or directory
 #include "zconf.h"
   ^
compilation terminated.

The example fails because the zconf.h header is not found. You can see the list
of the standard include paths when calling gcc with the -v option.

>> attaching the diff for the proposed changes
> 
> Please do not upload this, I will be back at home on Monday and can do
> an upload then and...
> 
>> +  * Non-maintainer upload.
>> +  * Install the zconf.h header file for the multilib packages. Closes: 
>> #787956.
>> +  * Use the target prefixed ar, available since binutils 2.26.
>> +  * Run dh_makeshlibs for the 64bit multilib library.
>> +  * Add ${misc:Depends} to zlib1g-dbg's dependencies.
>> +  * Support nobiarch build profile (Johannes Schauer). Closes: #709623.
> 
> ...this clearly isn't just fixing the bug and there are a bunch of
> additional changes not mentioned in the changelog. 

If I forgot some, sorry about these.

> I need to investigate what's going on here as I'm unconvinced that this
> doesn't introduce further problems (will this break multiarch for
> example, I appear to be able to build with -m32...).  This might be a
> lot clearer with split out incremental patches and really seems
> inappropriate for a zero notice NMU.
> 
>> -Standards-Version: 3.9.4
>> +Standards-Version: 3.9.8
> 
> If you're making changes like this they ought to be mentioned in the
> changelog.
> 
>> -Build-Depends: debhelper (>= 8.1.3~), binutils (>= 2.18.1~cvs20080103-2) 
>> [mips mipsel], gcc-multilib [amd64 i386 kfreebsd-amd64 mips mipsel powerpc 
>> ppc64 s390 sparc s390x], dpkg-dev (>= 1.16.1)
>> +Build-Depends: debhelper (>= 9), gcc-multilib [amd64 i386 kfreebsd-amd64 
>> mips mipsel powerpc ppc64 s390 sparc s390x] , dpkg-dev (>= 1.16.1)
> 
> Not sure why the debhelper dependency got changed or why we dropped the
> binutils dependency.

The binutils dependency is not necessary anymore. even oldstable has 2.22.  The
profile change is to fix issue #709623 (also mentioned in the changelog).

Bug#828800: verbiste: FTBFS in testing (Only can be included directly)

[Sébastien Villemot]

Control: tags -1 + patch pending

Le jeudi 24 novembre 2016 à 11:30 +0100, Sébastien Villemot a écrit :
> Le mardi 28 juin 2016 à 02:46 +0200, Tomasz Buchert a écrit :
> > On 27/06/16 23:52, Santiago Vila wrote:
> > > Package: src:verbiste
> > > Version: 0.1.43-1
> > > User: reproducible-bui...@lists.alioth.debian.org
> > > Usertags: ftbfs
> > > Severity: serious
> > > 
> > > Dear maintainer:
> > > 
> > > This package currently fails to build in stretch:
> > This bug is related to gtk2 vs. gtk3 API. I'll work on it during
> > debconf.
> 
> Any news on this? There is not much time left to fix it if we want
> verbiste to be part of stretch (it has been removed from testing, and
> it
> must be back there before Jan 5).
> 
> If you think this is the right solution, I can do an NMU where the
> MATE
> applet is removed.

I have uploaded to DELAYED/5 a NMU that fixes this issue, by removing
the MATE applet. The debdiff is attached. Don't hesitate to tell me if
you disagree with this NMU.

Best,

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594

diff -Nru verbiste-0.1.43/debian/changelog verbiste-0.1.43/debian/changelog
--- verbiste-0.1.43/debian/changelog	2016-03-25 06:52:24.0 +0100
+++ verbiste-0.1.43/debian/changelog	2016-11-26 20:37:56.0 +0100
@@ -1,3 +1,10 @@
+verbiste (0.1.43-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop verbiste-mate-applet package, fixes FTBFS. (Closes: #828800)
+
+ -- Sébastien Villemot   Sat, 26 Nov 2016 20:37:56 +0100
+
 verbiste (0.1.43-1) unstable; urgency=medium
 
   * Imported Upstream version 0.1.43
diff -Nru verbiste-0.1.43/debian/control verbiste-0.1.43/debian/control
--- verbiste-0.1.43/debian/control	2016-03-25 06:52:24.0 +0100
+++ verbiste-0.1.43/debian/control	2016-11-26 20:32:20.0 +0100
@@ -5,7 +5,6 @@
 Build-Depends: debhelper (>= 9),
dh-autoreconf,
libgnomeui-dev,
-   libmate-panel-applet-dev,
libxml-parser-perl,
locales,
pkg-config
@@ -38,20 +37,6 @@
  .
  This package contains a GNOME graphical interface.
 
-Package: verbiste-mate-applet
-Section: x11
-Architecture: any
-Depends: libmate-panel-applet-4-1,
- libverbiste-0.1-0v5 (= ${binary:Version}),
- verbiste-gnome (= ${binary:Version}),
- ${misc:Depends},
- ${shlibs:Depends}
-Description: French and Italian conjugator - MATE Panel applet
- Verbiste is a program that gives the complete conjugation for French and
- Italian verbs. The knowledge base contains over 6800 verbs.
- .
- This package contains a MATE panel applet.
-
 Package: verbiste-el
 Section: lisp
 Architecture: all
diff -Nru verbiste-0.1.43/debian/rules verbiste-0.1.43/debian/rules
--- verbiste-0.1.43/debian/rules	2016-03-25 06:52:24.0 +0100
+++ verbiste-0.1.43/debian/rules	2016-11-26 20:32:32.0 +0100
@@ -4,7 +4,7 @@
 CPPFLAGS += -DMATELOCALEDIR=\"/usr/share/locale\"
 
 override_dh_auto_configure:
-	dh_auto_configure -- --with-gtk-app --with-gnome-app --with-mate-applet --libexecdir=/usr/lib/mate-applets
+	dh_auto_configure -- --with-gtk-app --with-gnome-app
 
 override_dh_installdocs:
 	dh_installdocs -A README LISEZMOI HACKING
diff -Nru verbiste-0.1.43/debian/verbiste-mate-applet.install verbiste-0.1.43/debian/verbiste-mate-applet.install
--- verbiste-0.1.43/debian/verbiste-mate-applet.install	2016-03-25 06:52:24.0 +0100
+++ verbiste-0.1.43/debian/verbiste-mate-applet.install	1970-01-01 01:00:00.0 +0100
@@ -1,3 +0,0 @@
-debian/tmp/usr/lib/mate-applets/verbiste-mate-applet
-debian/tmp/usr/share/dbus-1/services/org.mate.panel.applet.VerbisteAppletFactory.service
-debian/tmp/usr/share/mate-panel/applets/org.mate.applets.VerbisteApplet.mate-panel-applet
diff -Nru verbiste-0.1.43/debian/verbiste-mate-applet.lintian-overrides verbiste-0.1.43/debian/verbiste-mate-applet.lintian-overrides
--- verbiste-0.1.43/debian/verbiste-mate-applet.lintian-overrides	2016-03-25 06:52:24.0 +0100
+++ verbiste-0.1.43/debian/verbiste-mate-applet.lintian-overrides	1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-# False positive
-verbiste-mate-applet: hardening-no-fortify-functions usr/lib/mate-applets/verbiste-mate-applet


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

Processed: Re: Bug#828800: verbiste: FTBFS in testing (Only can be included directly)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch pending
Bug #828800 [src:verbiste] verbiste: FTBFS in testing (Only  can be 
included directly)
Added tag(s) pending and patch.

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

Bug#787956: raising the severity, prevents usage of the multilib packages

[Mark Brown]

On Sat, Nov 26, 2016 at 07:52:26PM +0100, Matthias Klose wrote:
> On 26.11.2016 19:42, Mark Brown wrote:
> > On Sat, Nov 26, 2016 at 03:56:21PM +0100, Matthias Klose wrote:

> > Please allow at least a little time for a response, I've no real idea
> > what you're even asking for here.

> well, I asked you in private before, without getting replies on all messages 
> and
> proposals.

You sent me a mail last week asking for some additional multilib
packages for x32 ABI which seemed a bit strange at this point in the
release cycle and not that urgent as a new ABI would be at most
wishlist.  I'd been intending to have a look to try to work out what's
going on with x32 over the weekend.  I'm having a hard time relating
that to what you're talking about here though I do see you mentioned
that this was for "libgphobos (gdc runtime)" in both.

> This exactly is the correct issue, not "some random bug".

I'm afraid I'm still unclear what you are trying to do or why.  This is
a bug about trying to use the lib32z1-dev package, your private mails
were about adding x32 multilib packages and I'm really confused about
how either of these things relates to the shared libgphobos you keep
mentioning.  The proposed changes below don't have anything to do with
x32 either so I'm just completely confused now.

Can you please provide a clear, from first steps description of what's
needed and why?

> attaching the diff for the proposed changes

Please do not upload this, I will be back at home on Monday and can do
an upload then and...

> +  * Non-maintainer upload.
> +  * Install the zconf.h header file for the multilib packages. Closes: 
> #787956.
> +  * Use the target prefixed ar, available since binutils 2.26.
> +  * Run dh_makeshlibs for the 64bit multilib library.
> +  * Add ${misc:Depends} to zlib1g-dbg's dependencies.
> +  * Support nobiarch build profile (Johannes Schauer). Closes: #709623.

...this clearly isn't just fixing the bug and there are a bunch of
additional changes not mentioned in the changelog.  

I need to investigate what's going on here as I'm unconvinced that this
doesn't introduce further problems (will this break multiarch for
example, I appear to be able to build with -m32...).  This might be a
lot clearer with split out incremental patches and really seems
inappropriate for a zero notice NMU.

> -Standards-Version: 3.9.4
> +Standards-Version: 3.9.8

If you're making changes like this they ought to be mentioned in the
changelog.

> -Build-Depends: debhelper (>= 8.1.3~), binutils (>= 2.18.1~cvs20080103-2) 
> [mips mipsel], gcc-multilib [amd64 i386 kfreebsd-amd64 mips mipsel powerpc 
> ppc64 s390 sparc s390x], dpkg-dev (>= 1.16.1)
> +Build-Depends: debhelper (>= 9), gcc-multilib [amd64 i386 kfreebsd-amd64 
> mips mipsel powerpc ppc64 s390 sparc s390x] , dpkg-dev (>= 1.16.1)

Not sure why the debhelper dependency got changed or why we dropped the
binutils dependency.

Processed: Raise severity of bug again ...

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #840364 [src:kannel] kannel: Please remove build dependency on jade
Severity set to 'serious' from 'important'

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

Bug#798789: netperf: diff for NMU version 2.6.0-2.1

[Andrey Rahmatullin]

Control: tags 798789 + pending

Dear maintainer,

I've prepared an NMU for netperf (versioned as 2.6.0-2.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
WBR, wRAR
diff -Nru netperf-2.6.0/debian/changelog netperf-2.6.0/debian/changelog
--- netperf-2.6.0/debian/changelog	2013-05-09 03:13:43.0 +0600
+++ netperf-2.6.0/debian/changelog	2016-11-27 00:13:57.0 +0500
@@ -1,3 +1,11 @@
+netperf (2.6.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Adjust inline statements to fix FTBFS, patch from Sascha Steinbiss
+(Closes: #798789)
+
+ -- Andrey Rahmatullin   Sun, 27 Nov 2016 00:13:57 +0500
+
 netperf (2.6.0-2) unstable; urgency=low
 
   * [cbaabea7] [rules] removed explicit call of patchsys-quilt.mk
diff -Nru netperf-2.6.0/debian/patches/11_inline_statement.patch netperf-2.6.0/debian/patches/11_inline_statement.patch
--- netperf-2.6.0/debian/patches/11_inline_statement.patch	1970-01-01 05:00:00.0 +0500
+++ netperf-2.6.0/debian/patches/11_inline_statement.patch	2016-11-27 00:13:57.0 +0500
@@ -0,0 +1,25 @@
+Description: move around inline statement
+Author: Sascha Steinbiss 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798789
+--- a/src/netlib.c
 b/src/netlib.c
+@@ -4026,7 +4026,7 @@
+inline directive has to appear in netlib.h... */
+ void demo_interval_tick(uint32_t units)
+ #else
+-  inline void demo_interval_tick(uint32_t units)
++  void demo_interval_tick(uint32_t units)
+ #endif
+ {
+   double actual_interval = 0.0;
+--- a/src/netlib.h
 b/src/netlib.h
+@@ -504,7 +504,7 @@
+ extern void   demo_rr_interval(uint32_t units);
+ extern void   demo_rr_setup(uint32_t units);
+ extern void   demo_stream_interval(uint32_t units);
+-extern void   demo_interval_tick(uint32_t units);
++extern inline void   demo_interval_tick(uint32_t units);
+ extern void   demo_interval_final();
+ #endif
+ #endif 
diff -Nru netperf-2.6.0/debian/patches/series netperf-2.6.0/debian/patches/series
--- netperf-2.6.0/debian/patches/series	2013-05-09 03:13:43.0 +0600
+++ netperf-2.6.0/debian/patches/series	2016-11-27 00:13:57.0 +0500
@@ -1,2 +1,3 @@
 20_fix_debug_file_location.diff
 10_man_fix_unknown_macro.diff
+11_inline_statement.patch


signature.asc
Description: PGP signature

Processed: netperf: diff for NMU version 2.6.0-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 798789 + pending
Bug #798789 [netperf] netperf: FTBFS with GCC 5: undefined reference to 
`demo_interval_tick'
Added tag(s) pending.

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

Bug#822502: nemiver: FTBFS: error: cannot convert 'const sigc::slot_base' to 'bool' in return

[Andrey Rahmatullin]

Control: tags -1 - patch

The patch is currently not enough:

nmv-dbg-perspective.cc: In member function 'void 
nemiver::DBGPerspective::switch_to_asm(const nemiver::common::DisassembleInfo&, 
const std::__cxx11::list&, nemiver::SourceEditor*, bool)':
nmv-dbg-perspective.cc:5675:68: error: no match for 'operator==' (operand types 
are 'Glib::RefPtr' and 'int')
 if ((asm_buf = a_source_editor->get_assembly_source_buffer ()) == 0) {
 ~~~^~~~

nmv-dbg-perspective.cc: In member function 'void 
nemiver::DBGPerspective::switch_to_source_code()':
nmv-dbg-perspective.cc:5723:73: error: no match for 'operator==' (operand types 
are 'Glib::RefPtr' and 'int')
 if ((source_buf = source_editor->get_non_assembly_source_buffer ()) == 0) {
 ^~~~


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Processed: Re: Bug#822502: nemiver: FTBFS: error: cannot convert 'const sigc::slot_base' to 'bool' in return

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - patch
Bug #822502 [nemiver] nemiver: FTBFS: error: cannot convert 'const 
sigc::slot_base' to 'bool' in return
Removed tag(s) patch.

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

Bug#845793: lib64z1-dev doesn't provide a shlibs file, causing package build failures

[Matthias Klose]

Package: src:zlib
Version: 1:1.2.8.dfsg-2
Severity: serious
Tags: patch sid stretch

dh_makeshlibs is not called for the lib64z1-dev package, causing package build
failures. see

https://buildd.debian.org/status/fetch.php?pkg=gcc-7=i386=7-20161116-1=1479399831

dh_shlibdeps -plib64gphobos68
-l/«PKGBUILDDIR»/debian/lib64gcc1/lib64:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/lib64:/usr/lib64
dpkg-shlibdeps: error: no dependency information found for /usr/lib64/libz.so.1
(used by debian/lib64gphobos68/usr/lib64/libgphobos.so.68.0.0)
Hint: check if the library actually comes from a package.
dh_shlibdeps: dpkg-shlibdeps -Tdebian/lib64gphobos68.substvars
-l/«PKGBUILDDIR»/debian/lib64gcc1/lib64 -l/lib/x86_64-linux-gnu
-l/usr/lib/x86_64-linux-gnu -l/lib64 -l/usr/lib64
debian/lib64gphobos68/usr/lib64/libgphobos.so.68.0.0
debian/lib64gphobos68/usr/lib64/libgdruntime.so.68.0.2 returned exit code 2
debian/rules.d/binary-d.mk:219: recipe for target
'stamps/08-binary-stamp-lib64phobos' failed
make[1]: *** [stamps/08-binary-stamp-lib64phobos] Error 2

The patch is attached in the issue #787956.

Bug#787956: raising the severity, prevents usage of the multilib packages

[Matthias Klose]

reopen 787956
thanks

On 26.11.2016 19:42, Mark Brown wrote:
> On Sat, Nov 26, 2016 at 03:56:21PM +0100, Matthias Klose wrote:
> 
>> Control: severity -1 serious
> 
> This appears to be some random bug that's a user error and should've
> been closed after the initial discussion with the submitter (which I'm
> now doing).   I'm not sure I can relate it to...
> 
>> now that libgphobos, the gdc's D runtime library is built as a shared 
>> library,
>> I'd like to use the still present multilib builds.  There is currently a
>> fall-back to embed the library, but that doesn't sound as clean as using the
>> multilib packages.  Dropping the multilib packages isn't yet an option from 
>> my
>> point of view, because the buildds are not able to depend on other 
>> architectures.
> 
> ...any of this.  Can you please file a new bug that's a bit more
> explicit about whatever it is that you're looking for here.  As far as
> I can tell this might be a request for multilib packages but zlib
> already has multilib packages so I'm pretty confused.
> 
>> I'm preparing a NMU for that.
> 
> Please allow at least a little time for a response, I've no real idea
> what you're even asking for here.

well, I asked you in private before, without getting replies on all messages and
proposals.

This exactly is the correct issue, not "some random bug".

$ cat tst.c
#include 
$ gcc -m32 -c tst.c
In file included from tst.c:1:0:
/usr/include/zlib.h:34:19: fatal error: zconf.h: No such file or directory
 #include "zconf.h"
   ^
compilation terminated.


attaching the diff for the proposed changes

diff -Nru zlib-1.2.8.dfsg/debian/changelog zlib-1.2.8.dfsg/debian/changelog
--- zlib-1.2.8.dfsg/debian/changelog2014-08-16 23:48:57.0 +0200
+++ zlib-1.2.8.dfsg/debian/changelog2016-11-26 15:57:08.0 +0100
@@ -1,3 +1,14 @@
+zlib (1:1.2.8.dfsg-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install the zconf.h header file for the multilib packages. Closes: #787956.
+  * Use the target prefixed ar, available since binutils 2.26.
+  * Run dh_makeshlibs for the 64bit multilib library.
+  * Add ${misc:Depends} to zlib1g-dbg's dependencies.
+  * Support nobiarch build profile (Johannes Schauer). Closes: #709623.
+
+ -- Matthias Klose   Sat, 26 Nov 2016 15:57:08 +0100
+
 zlib (1:1.2.8.dfsg-2) unstable; urgency=low
 
   * Drop zlib-bin package as minizip has now been packaged separately,
diff -Nru zlib-1.2.8.dfsg/debian/control zlib-1.2.8.dfsg/debian/control
--- zlib-1.2.8.dfsg/debian/control  2014-08-16 16:13:26.0 +0200
+++ zlib-1.2.8.dfsg/debian/control  2016-11-26 15:57:08.0 +0100
@@ -2,9 +2,9 @@
 Section: libs
 Priority: optional
 Maintainer: Mark Brown 
-Standards-Version: 3.9.4
+Standards-Version: 3.9.8
 Homepage: http://zlib.net/
-Build-Depends: debhelper (>= 8.1.3~), binutils (>= 2.18.1~cvs20080103-2) [mips 
mipsel], gcc-multilib [amd64 i386 kfreebsd-amd64 mips mipsel powerpc ppc64 s390 
sparc s390x], dpkg-dev (>= 1.16.1)
+Build-Depends: debhelper (>= 9), gcc-multilib [amd64 i386 kfreebsd-amd64 mips 
mipsel powerpc ppc64 s390 sparc s390x] , dpkg-dev (>= 1.16.1)
 
 Package: zlib1g
 Architecture: any
@@ -35,7 +35,7 @@
 Section: debug
 Priority: extra
 Architecture: any
-Depends: zlib1g (= ${binary:Version})
+Depends: zlib1g (= ${binary:Version}), ${misc:Depends}
 Provides: libz-dbg
 Description: compression library - development
  zlib is a library implementing the deflate compression method found
@@ -56,6 +56,7 @@
 Architecture: sparc s390 i386 powerpc mips mipsel
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Replaces: amd64-libs (<< 1.4)
+Build-Profiles: 
 Description: compression library - 64 bit runtime
  zlib is a library implementing the deflate compression method found
  in gzip and PKZIP.  This package includes a 64 bit version of the
@@ -67,6 +68,7 @@
 Depends: lib64z1 (= ${binary:Version}), zlib1g-dev (= ${binary:Version}), 
lib64c-dev, ${misc:Depends}
 Replaces: amd64-libs-dev (<< 1.4)
 Provides: lib64z-dev
+Build-Profiles: 
 Description: compression library - 64 bit development
  zlib is a library implementing the deflate compression method found
  in gzip and PKZIP.  This package includes the development support
@@ -77,6 +79,7 @@
 Conflicts: libc6-i386 (<= 2.9-18)
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Replaces: ia32-libs (<< 1.5)
+Build-Profiles: 
 Description: compression library - 32 bit runtime
  zlib is a library implementing the deflate compression method found
  in gzip and PKZIP.  This package includes a 32 bit version of the
@@ -89,6 +92,7 @@
 Depends: lib32z1 (= ${binary:Version}), zlib1g-dev (= ${binary:Version}), 
lib32c-dev, ${misc:Depends}
 Provides: lib32z-dev
 Replaces: ia32-libs-dev (<< 1.5)
+Build-Profiles: 
 Description: compression library - 32 bit development
  zlib is a library implementing the deflate compression method found
  in gzip and PKZIP.  This package includes the development 

Processed: Re: Bug#787956: raising the severity, prevents usage of the multilib packages

[Debian Bug Tracking System]

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

> reopen 787956
Bug #787956 {Done: Mark Brown } [lib32z1-dev] lib32z1-dev: 
Compiling anything that includes  with -m32 fails
Bug reopened
Ignoring request to alter fixed versions of bug #787956 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#787956: marked as done (lib32z1-dev: Compiling anything that includes with -m32 fails)

[Debian Bug Tracking System]

Your message dated Sat, 26 Nov 2016 18:42:06 +
with message-id <20161126184206.rfv33lxn4kx2v...@sirena.org.uk>
and subject line Re: Bug#787956: raising the severity, prevents usage of the 
multilib packages
has caused the Debian Bug report #787956,
regarding lib32z1-dev: Compiling anything that includes  with -m32 fails
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.)


-- 
787956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lib32z1-dev
Version: 1:1.2.8.dfsg-2+b1
Severity: important

lib32z1-dev fails to include zconf.h, which results in compiling
(AFAICT) any zlib-using program to fail:


$ cat zlib-32.c 
#include 
$ gcc -m32 -c zlib-32.c 
In file included from zlib-32.c:1:0:
/usr/include/zlib.h:34:19: fatal error: zconf.h: No such file or directory
 #include "zconf.h"
   ^
compilation terminated.


Sami


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

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

Versions of packages lib32z1-dev depends on:
ii  lib32z1  1:1.2.8.dfsg-2+b1
ii  libc6-dev-i386 [lib32c-dev]  2.19-18
ii  zlib1g-dev   1:1.2.8.dfsg-2+b1

lib32z1-dev recommends no packages.

lib32z1-dev suggests no packages.

-- no debconf information


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
On Sat, Nov 26, 2016 at 03:56:21PM +0100, Matthias Klose wrote:

> Control: severity -1 serious

This appears to be some random bug that's a user error and should've
been closed after the initial discussion with the submitter (which I'm
now doing).   I'm not sure I can relate it to...

> now that libgphobos, the gdc's D runtime library is built as a shared library,
> I'd like to use the still present multilib builds.  There is currently a
> fall-back to embed the library, but that doesn't sound as clean as using the
> multilib packages.  Dropping the multilib packages isn't yet an option from my
> point of view, because the buildds are not able to depend on other 
> architectures.

...any of this.  Can you please file a new bug that's a bit more
explicit about whatever it is that you're looking for here.  As far as
I can tell this might be a request for multilib packages but zlib
already has multilib packages so I'm pretty confused.

> I'm preparing a NMU for that.

Please allow at least a little time for a response, I've no real idea
what you're even asking for here.--- End Message ---

Processed: msrtool: diff for NMU version 1:20141027-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 837570 + pending
Bug #837570 [src:msrtool] msrtool: FTBFS with bindnow and PIE enabled
Added tag(s) pending.

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

Bug#837570: msrtool: diff for NMU version 1:20141027-1.1

[Andrey Rahmatullin]

Control: tags 837570 + pending

Dear maintainer,

I've prepared an NMU for msrtool (versioned as 1:20141027-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
WBR, wRAR
diff -Nru msrtool-20141027/debian/changelog msrtool-20141027/debian/changelog
--- msrtool-20141027/debian/changelog	2014-10-28 06:17:10.0 +0500
+++ msrtool-20141027/debian/changelog	2016-11-26 23:42:53.0 +0500
@@ -1,3 +1,10 @@
+msrtool (1:20141027-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with PIE enabled, patch by Adrian Bunk (Closes: #837570).
+
+ -- Andrey Rahmatullin   Sat, 26 Nov 2016 23:42:53 +0500
+
 msrtool (1:20141027-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru msrtool-20141027/debian/patches/fix-pie.patch msrtool-20141027/debian/patches/fix-pie.patch
--- msrtool-20141027/debian/patches/fix-pie.patch	1970-01-01 05:00:00.0 +0500
+++ msrtool-20141027/debian/patches/fix-pie.patch	2016-11-26 23:38:39.0 +0500
@@ -0,0 +1,17 @@
+Description: Don't build with -fno-pic
+ -fno-pic isn't needed, and it breaks building when
+ the compiler defaults to PIE.
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/837570
+
+--- msrtool-20141027.orig/Makefile.in
 msrtool-20141027/Makefile.in
+@@ -23,7 +23,7 @@ PROGRAM = msrtool
+ CC  = @CC@
+ INSTALL = @INSTALL@
+ PREFIX  = @PREFIX@
+-CFLAGS  = @CFLAGS@ -fno-pic
++CFLAGS  = @CFLAGS@
+ LDFLAGS = @LDFLAGS@
+ 
+ TARGETS = geodegx2.o geodelx.o cs5536.o k8.o intel_pentium3_early.o intel_pentium3.o intel_pentium4_early.o intel_pentium4_later.o intel_core1.o intel_core2_early.o intel_core2_later.o intel_nehalem.o intel_atom.o
diff -Nru msrtool-20141027/debian/patches/series msrtool-20141027/debian/patches/series
--- msrtool-20141027/debian/patches/series	1970-01-01 05:00:00.0 +0500
+++ msrtool-20141027/debian/patches/series	2016-11-26 23:39:47.0 +0500
@@ -0,0 +1 @@
+fix-pie.patch


signature.asc
Description: PGP signature

Bug#845777: marked as done (nagios3: seriously buggy (7 open CVEs) should not be shipped like this in stretch)

[Debian Bug Tracking System]

Your message dated Sat, 26 Nov 2016 18:38:14 +
with message-id 
and subject line Bug#845765: Removed package(s) from unstable
has caused the Debian Bug report #845777,
regarding nagios3: seriously buggy (7 open CVEs) should not be shipped like 
this in stretch
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.)


-- 
845777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:nagios3
severity: serious
version: 3.5.1.dfsg-2

Hi,

according to https://security-tracker.debian.org/tracker/source-package/nagios3
nagios3 in stable, stretch and unstable is affected by

CVE-2016-6209
CVE-2014-1878
CVE-2013-7205
CVE-2013-7108
CVE-2013-7107
CVE-2013-4214

and another unimportant CVE (CVE-2008-5027), so it's high time this
package (in this state) gets removed from stretch.

Upstream has also abendonded it and is developing nagios4.

Please also see #845765.

For stretch users, it's recommend to switch to icinga2, which is largely
compatible.


-- 
cheers,
Holger


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 3.5.1.dfsg-2.2+rm

Dear submitter,

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

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

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

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

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

Bug#776118: marked as done (nagios3-cgi: prompting due to modified conffiles which were not modified by the user: /etc/nagios3/cgi.cfg)

[Debian Bug Tracking System]

Your message dated Sat, 26 Nov 2016 18:38:14 +
with message-id 
and subject line Bug#845765: Removed package(s) from unstable
has caused the Debian Bug report #776118,
regarding nagios3-cgi: prompting due to modified conffiles which were not 
modified by the user: /etc/nagios3/cgi.cfg
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.)


-- 
776118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nagios3-cgi
Version: 3.4.1-3+deb7u1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 nagios3

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

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

This has been observed on an upgrade test from lenny to squeeze to
wheezy ...

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

  Setting up nagios3-cgi (3.4.1-3+deb7u1) ...
  
  Configuration file `/etc/nagios3/cgi.cfg'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** cgi.cfg (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing nagios3-cgi 
(--configure):
   EOF on stdin at conffile prompt
  Setting up nagios3-core (3.4.1-3+deb7u1) ...
  configured to not write apport reports
  invoke-rc.d: policy-rc.d denied execution of start.
  dpkg: dependency problems prevent configuration of nagios3:
   nagios3 depends on nagios3-cgi (= 3.4.1-3+deb7u1); however:
Package nagios3-cgi is not configured yet.
  
  dpkg: error processing nagios3 (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   nagios3-cgi
   nagios3


cheers,

Andreas


nagios3_3.5.1.dfsg-2+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 3.5.1.dfsg-2.2+rm

Dear submitter,

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

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

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

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

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

Bug#825248: hgview: diff for NMU version 1.9.0-1.1

[Andrey Rahmatullin]

Control: tags 825248 + pending

Dear maintainer,

I've prepared an NMU for hgview (versioned as 1.9.0-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
WBR, wRAR
diff -u hgview-1.9.0/debian/changelog hgview-1.9.0/debian/changelog
--- hgview-1.9.0/debian/changelog
+++ hgview-1.9.0/debian/changelog
@@ -1,3 +1,11 @@
+hgview (1.9.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix hgview-curses for Mercurial 3.8.2, patch by Zhang Jingqiang (Closes:
+#825248)
+
+ -- Andrey Rahmatullin   Sat, 26 Nov 2016 22:58:51 +0500
+
 hgview (1.9.0-1) unstable; urgency=medium
 
   [ Rémi Cardona ]
diff -u hgview-1.9.0/debian/control hgview-1.9.0/debian/control
--- hgview-1.9.0/debian/control
+++ hgview-1.9.0/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: David Douard 
 Uploaders: Julien Cristau , Alain Leufroy , Pierre-Yves David , Pierre-Yves David ,
-Build-Depends: debhelper (>= 9), pyqt4-dev-tools, python (>=2.6.6-3~), xmlto, asciidoc, mercurial
+Build-Depends: debhelper (>= 9), quilt, pyqt4-dev-tools, python (>=2.6.6-3~), xmlto, asciidoc, mercurial
 X-Python-Version: >= 2.5
 Standards-Version: 3.9.1
 Vcs-Hg: http://hg.logilab.org/master/hgview/
diff -u hgview-1.9.0/debian/rules hgview-1.9.0/debian/rules
--- hgview-1.9.0/debian/rules
+++ hgview-1.9.0/debian/rules
@@ -12,7 +12,7 @@
 #export DH_VERBOSE=1
 
 %:
-	dh $@ --buildsystem=python_distutils --with python2
+	dh $@ --buildsystem=python_distutils --with python2,quilt
 
 clean: 
 	dh clean
only in patch2:
unchanged:
--- hgview-1.9.0.orig/debian/patches/mercurial-3.8.2.patch
+++ hgview-1.9.0/debian/patches/mercurial-3.8.2.patch
@@ -0,0 +1,31 @@
+--- a/hgviewlib/curses/graphlog.py.orig	2016-05-25 12:52:57.196775537 +0800
 b/hgviewlib/curses/graphlog.py	2016-05-25 13:22:33.085859338 +0800
+@@ -312,6 +312,10 @@
+ # some support of obsolete relation display
+ # assert -2 < coldiff < 2
+ assert height > 0
++
++echars = []
++echars.extend(('|', ' ') * (ncols + coldiff))
++
+ if coldiff == -1:
+ _fixlongrightedges(edges)
+ # add_padding_line says whether to rewrite
+@@ -323,7 +327,7 @@
+ # nodeline is the line containing the node character (typically o)
+ nodeline = ["|", " "] * idx
+ nodeline.extend([('GraphLog.node', char), " "])
+-nodeline.extend(_getnodelineedgestail(idx, state[1], ncols, coldiff,
++nodeline.extend(_getnodelineedgestail(echars, idx, state[1], ncols, coldiff,
+ state[0], fix_nodeline_tail))
+ # shift_interline is the line containing the non-vertical
+ # edges between this entry and the next
+@@ -340,7 +344,7 @@
+ shift_interline.extend(n_spaces * [" "])
+ shift_interline.extend([edge_ch, " "] * (ncols - idx - 1))
+ # draw edges from the current node to its parents
+-_drawedges(edges, nodeline, shift_interline)
++_drawedges(echars, edges, nodeline, shift_interline)
+ # lines is the list of all graph lines to print
+ lines = [nodeline]
+ if add_padding_line:
only in patch2:
unchanged:
--- hgview-1.9.0.orig/debian/patches/series
+++ hgview-1.9.0/debian/patches/series
@@ -0,0 +1 @@
+mercurial-3.8.2.patch


signature.asc
Description: PGP signature

Processed: hgview: diff for NMU version 1.9.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 825248 + pending
Bug #825248 [hgview-curses] hgview-curses: Patch needed to work with mercurial 
3.8.2
Added tag(s) pending.

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

Bug#840305: libatteanx-store-memorytriplestore-perl: FTBFS with perl 5.24 or without . in @INC

[gregor herrmann]

Control: retitle -1 libatteanx-store-memorytriplestore-perl: depends on 
unavailable AtteanX::RDFQueryTranslator

On Mon, 10 Oct 2016 14:42:29 +0200, Andreas Beckmann wrote:

> Source: libatteanx-store-memorytriplestore-perl
> Version: 0.001~20150811-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> Hi,
> 
> your package FTBFS against perl 5.24 or against a perl without . in @INC:

I think the reason is different:
 
> PERL_DL_NONLAZY=1 PERL_USE_UNSAFE_INC=1 "/usr/bin/perl" 
> "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef 
> *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t
> Can't locate AtteanX/RDFQueryTranslator.pm in @INC (you may need to install 
> the AtteanX::RDFQueryTranslator module) (@INC contains: 
> /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
> /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
> t/planning.t line 12,  line 1.

AtteanX/RDFQueryTranslator.pm was in libattean-perl but according to
its d/changelog:

+ Remove AtteanX::RDFQueryTranslator (split into a new package) and
  all other references to RDF::Query.

So someone would need to package the now separate
AtteanX::RDFQueryTranslator.

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: [DKP]: Die drei Flüsse (Ungarn)


signature.asc
Description: Digital Signature

Processed: Re: Bug#840305: libatteanx-store-memorytriplestore-perl: FTBFS with perl 5.24 or without . in @INC

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libatteanx-store-memorytriplestore-perl: depends on unavailable 
> AtteanX::RDFQueryTranslator
Bug #840305 [src:libatteanx-store-memorytriplestore-perl] 
libatteanx-store-memorytriplestore-perl: FTBFS with perl 5.24 or without . in 
@INC
Changed Bug title to 'libatteanx-store-memorytriplestore-perl: depends on 
unavailable AtteanX::RDFQueryTranslator' from 
'libatteanx-store-memorytriplestore-perl: FTBFS with perl 5.24 or without . in 
@INC'.

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

Bug#845786: gammaray FTBFS on armhf: QFatal in quickinspectortest

[Adrian Bunk]

Source: gammaray
Version: 2.6.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=gammaray=armhf=2.6.0-1=1480176282

...
  Start 36: quickinspectortest

36: Test command: /«PKGBUILDDIR»/obj-qt5/bin/quickinspectortest
36: Test timeout computed to be: 9.99988e+06
36: * Start testing of QuickInspectorTest *
36: Config: Using QtTest library 5.7.1, Qt 5.7.1 
(arm-little_endian-ilp32-eabi-hardfloat shared (dynamic) release build; by GCC 
6.2.0 20161103)
36: PASS   : QuickInspectorTest::initTestCase()
36: QWARN  : QuickInspectorTest::testModelsReparent() Failed to connect to 
launcher, can't receive probe settings! "QLocalSocket::connectToServer: Invalid 
name"
36: 
...
36: QFatal in quickinspectortest (/«PKGBUILDDIR»/obj-qt5/bin/quickinspectortest)
36: START BACKTRACE:
36: 1   
/«PKGBUILDDIR»/obj-qt5/lib/libgammaray_core-qt5_7-arm.so.2.6.0(+0x7fdb4) 
[0xb6e0edb4]
36: 2   
/«PKGBUILDDIR»/obj-qt5/lib/libgammaray_core-qt5_7-arm.so.2.6.0(+0x62e58) 
[0xb6df1e58]
36: 3   /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5(+0x808f2) [0xb649b8f2]
36: 4   /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5(QMessageLogger::fatal(char 
const*, ...) const+0x27) [0xb649c7e8]
36: 5   /usr/lib/arm-linux-gnueabihf/libQt5Test.so.5(+0x97ec) [0xb6d6c7ec]
36: 6   /lib/arm-linux-gnueabihf/libc.so.6(+0x24fd0) [0xb621dfd0]
36: END BACKTRACE
...

Bug#821983: ftgl: diff for NMU version 2.1.3~rc5-4+nmu1.1

[Andrey Rahmatullin]

Control: tags 821983 + pending

Dear maintainer,

I've prepared an NMU for ftgl (versioned as 2.1.3~rc5-4+nmu1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
WBR, wRAR
diff -Nru ftgl-2.1.3~rc5/debian/changelog ftgl-2.1.3~rc5/debian/changelog
--- ftgl-2.1.3~rc5/debian/changelog	2014-01-05 22:20:22.0 +0600
+++ ftgl-2.1.3~rc5/debian/changelog	2016-11-26 22:25:04.0 +0500
@@ -1,3 +1,11 @@
+ftgl (2.1.3~rc5-4+nmu1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add build-arch and build-indep targets, patch by Santiago Vila (Closes:
+#821983).
+
+ -- Andrey Rahmatullin   Sat, 26 Nov 2016 22:25:04 +0500
+
 ftgl (2.1.3~rc5-4+nmu1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru ftgl-2.1.3~rc5/debian/rules ftgl-2.1.3~rc5/debian/rules
--- ftgl-2.1.3~rc5/debian/rules	2014-01-05 22:18:34.0 +0600
+++ ftgl-2.1.3~rc5/debian/rules	2016-11-26 22:25:04.0 +0500
@@ -30,6 +30,8 @@
 		--libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
 	touch $@
 
+build-arch: build
+build-indep: build
 build: build-stamp
 build-stamp: configure-stamp
 	dh_testdir
@@ -89,4 +91,4 @@
 	dh_builddeb -a
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure


signature.asc
Description: PGP signature

Processed: ftgl: diff for NMU version 2.1.3~rc5-4+nmu1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 821983 + pending
Bug #821983 [src:ftgl] ftgl: Build arch:all+arch:any but is missing 
build-{arch,indep} targets
Added tag(s) pending.

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

Processed: proot: diff for NMU version 5.1.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 788113 + pending
Bug #788113 [src:proot] proot: FTBFS on arm64
Added tag(s) pending.

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

Bug#788113: proot: diff for NMU version 5.1.0-1.1

[Andrey Rahmatullin]

Control: tags 788113 + pending

Dear maintainer,

I've prepared an NMU for proot (versioned as 5.1.0-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
WBR, wRAR
diff -Nru proot-5.1.0/debian/changelog proot-5.1.0/debian/changelog
--- proot-5.1.0/debian/changelog	2015-01-27 18:29:21.0 +0500
+++ proot-5.1.0/debian/changelog	2016-11-26 22:12:08.0 +0500
@@ -1,3 +1,10 @@
+proot (5.1.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS on arm64, patch by Sebastian Ramacher (Closes: #788113).
+
+ -- Andrey Rahmatullin   Sat, 26 Nov 2016 22:12:08 +0500
+
 proot (5.1.0-1) unstable; urgency=low
   * Upgrade to latest PRoot version
 - PRoot is now embedding is own ELF interpreter
diff -Nru proot-5.1.0/debian/patches/arm64.patch proot-5.1.0/debian/patches/arm64.patch
--- proot-5.1.0/debian/patches/arm64.patch	1970-01-01 05:00:00.0 +0500
+++ proot-5.1.0/debian/patches/arm64.patch	2016-11-26 22:11:22.0 +0500
@@ -0,0 +1,134 @@
+diff -ru proot-5.1.0.orig/src/arch.h proot-5.1.0/src/arch.h
+--- proot-5.1.0.orig/src/arch.h
 proot-5.1.0/src/arch.h
+@@ -125,6 +125,9 @@
+ #define OFFSETOF_STAT_UID_32 0
+ #define OFFSETOF_STAT_GID_32 0
+ 
++#define EXEC_PIC_ADDRESS   0x5000
++#define INTERP_PIC_ADDRESS 0x6f00
++
+ #elif defined(ARCH_X86)
+ 
+ #define SYSNUMS_HEADER1 "syscall/sysnums-i386.h"
+diff -ru proot-5.1.0.orig/src/loader/assembly-arm64.h proot-5.1.0/src/loader/assembly-arm64.h
+--- /dev/null
 proot-5.1.0/src/loader/assembly-arm64.h
+@@ -0,0 +1,93 @@
++/* -*- c-set-style: "K"; c-basic-offset: 8 -*-
++ *
++ * This file is part of PRoot.
++ *
++ * Copyright (C) 2014 STMicroelectronics
++ *
++ * This program is free software; you can redistribute it and/or
++ * modify it under the terms of the GNU General Public License as
++ * published by the Free Software Foundation; either version 2 of the
++ * License, or (at your option) any later version.
++ *
++ * This program is distributed in the hope that it will be useful, but
++ * WITHOUT ANY WARRANTY; without even the implied warranty of
++ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
++ * General Public License for more details.
++ *
++ * You should have received a copy of the GNU General Public License
++ * along with this program; if not, write to the Free Software
++ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
++ * 02110-1301 USA.
++ */
++
++#define BRANCH(stack_pointer, destination) do {			\
++	asm volatile (		\
++		"// Restore initial stack pointer.	\n\t"	\
++		"mov sp, %0\n\t"	\
++		"	\n\t"	\
++		"// Clear rtld_fini.			\n\t"	\
++		"mov x0, #0\n\t"	\
++		"	\n\t"	\
++		"// Start the program.			\n\t"	\
++		"br %1	\n"	\
++		: /* no output */\
++		: "r" (stack_pointer), "r" (destination)	\
++		: "memory", "sp", "x0");			\
++	__builtin_unreachable();\
++	} while (0)
++
++#define PREPARE_ARGS_1(arg1_)\
++	register word_t arg1 asm("x0") = arg1_;		\
++
++#define PREPARE_ARGS_3(arg1_, arg2_, arg3_)		\
++	PREPARE_ARGS_1(arg1_)\
++	register word_t arg2 asm("x1") = arg2_;		\
++	register word_t arg3 asm("x2") = arg3_;		\
++
++#define PREPARE_ARGS_4(arg1_, arg2_, arg3_, arg4_)	\
++	PREPARE_ARGS_3(arg1_, arg2_, arg3_)		\
++	register word_t arg4 asm("x3") = arg4_;
++
++#define PREPARE_ARGS_6(arg1_, arg2_, arg3_, arg4_, arg5_, arg6_)	\
++	PREPARE_ARGS_3(arg1_, arg2_, arg3_)\
++	register word_t arg4 asm("x3") = arg4_;\
++	register word_t arg5 asm("x4") = arg5_;\
++	register word_t arg6 asm("x5") = arg6_;
++
++#define OUTPUT_CONTRAINTS_1			\
++	"r" (arg1)
++
++#define OUTPUT_CONTRAINTS_3			\
++	OUTPUT_CONTRAINTS_1,			\
++	"r" (arg2), "r" (arg3)
++
++#define OUTPUT_CONTRAINTS_4			\
++	OUTPUT_CONTRAINTS_3,			\
++	"r" (arg4)
++
++#define OUTPUT_CONTRAINTS_6\
++	OUTPUT_CONTRAINTS_3,\
++	"r" (arg4), "r" (arg5), "r" (arg6)
++
++#define SYSCALL(number_, nb_args, args...)			\
++	({			\
++		register word_t number asm("w8") = number_;	\
++		register word_t result asm("x0");		\
++		PREPARE_ARGS_##nb_args(args)			\
++			asm volatile (\
++"svc #0x	\n\t"	\
++: "=r" (result)			\
++: "r" (number),			\
++OUTPUT_CONTRAINTS_##nb_args	\
++: "memory");			\
++			result;	\
++	})
++
++#define OPENAT	56
++#define CLOSE	57
++#define MMAP	222
++#define MMAP_OFFSET_SHIFT 0
++#define EXECVE	221
++#define EXIT	93
++#define PRCTL	167
++
+diff -ru proot-5.1.0.orig/src/loader/loader.c proot-5.1.0/src/loader/loader.c
+--- proot-5.1.0.orig/src/loader/loader.c
 proot-5.1.0/src/loader/loader.c
+@@ -39,6 +39,8 @@
+ #include "loader/assembly-x86_64.h"
+ #elif defined(ARCH_ARM_EABI)
+ #include "loader/assembly-arm.h"
++#elif defined(ARCH_ARM64)
++#include "loader/assembly-arm64.h"
+ #elif defined(ARCH_X86)
+ #include "loader/assembly-x86.h"
+ #else
+@@ -134,7 +136,11 @@
+ 			/* Fall through.  */

Bug#839580: [request-tracker-maintainers] Bug#839580: Bug#839580: request-tracker4: FTBFS in testing (failed tests)

[Dominic Hargreaves]

On Thu, Nov 24, 2016 at 12:01:20PM +, Dominic Hargreaves wrote:
> Firstly, I'm sorry that you didn't get any response on this, and thank
> you for pushing this issue. I must confess to being rather frustrated
> by the situation as well as not having any spare cycles for Debian
> work for a while.
> 
> It seems like at least for RT, any update to a version of
> libgnupg-interface-perl which drops support for gpg1 is going to be
> quite invasive, because the RT test suite depends on a particular
> version of gpg. I note you didn't get any response on the gnupg upstream
> portability issue - was there any other progress on that front? It
> would certainly be much easier for upstream to take the patchset if
> it didn't break compatibility with GPG1 (even if we might be able to
> do so in Debian).
> 
> I will try and do some testing with RT and the version of this pacakge
> in experimental. Do you have any idea whether the other rdeps are
> similarly sensitive?
> 
> FTR, I've just filed #845534 about another related issue which I failed
> to spot; RT is currently configured to use gpg1 for tests, but the default
> (which is now gpg2) at runtime, and that probably doesn't work.
> 
> (GPG isn't that commonly used in RT, so I wouldn't be surprised if this
> hasn't been road tested in sid :( )

FTR: I've filed #845781 against libgnupg-interface-perl, which is
probably the right place to continue this discussion.

Best,
Dominic.

Bug#845783: leveldb FTBFS on armhf: Test DBTest.HiddenValuesAreRemoved failed

[Adrian Bunk]

Source: leveldb
Version: 1.19-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=leveldb=armhf=1.19-2=1480164699

 Test DBTest.HiddenValuesAreRemoved
db/db_test.cc:1248: failed: [ tiny, 
Makefile:162: recipe for target 'check' failed
make[2]: *** [check] Error 1
make[2]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_test: make -j4 check returned exit code 2
debian/rules:32: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:25: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Bug#845741: marked as done (xserver-xorg-video-qxl: Fails to build from source with xorg 1.19: implicit declaration of function 'QueryGlyphExtents')

[Debian Bug Tracking System]

Your message dated Sat, 26 Nov 2016 17:04:25 +
with message-id 
and subject line Bug#845741: fixed in xserver-xorg-video-qxl 
0.1.4+20161126git4d7160c-1
has caused the Debian Bug report #845741,
regarding xserver-xorg-video-qxl: Fails to build from source with xorg 1.19: 
implicit declaration of function 'QueryGlyphExtents'
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.)


-- 
845741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-video-qxl
Version: 0.1.4-3+b1
Severity: serious
Tags: upstream

The bin-NMU for Xorg 1.19 failed:
../../../src/uxa/uxa-damage.c: In function 'uxa_damage_chars':
../../../src/uxa/uxa-damage.c:947:5: error: implicit declaration of function 
'QueryGlyphExtents' [-Werror=implicit-function-declaration]
 QueryGlyphExtents(font, charinfo, n, );
 ^

This has been fixed upstream with this commit:
https://cgit.freedesktop.org/xorg/driver/xf86-video-qxl/commit/?id=a184774ad161031cceed264d62d48ebd019ac800

It doesn't apply cleanly due to some intermediary cleanups. A further change 
allowed the usage
of libXfont2:
https://cgit.freedesktop.org/xorg/driver/xf86-video-qxl/commit/?id=e13d28ee5d8724fc4b22f26bce01a7d36355f272

Maybe you just want to release a git snapshot or manually backport those 
patches.

Cheers,
--- End Message ---
--- Begin Message ---
Source: xserver-xorg-video-qxl
Source-Version: 0.1.4+20161126git4d7160c-1

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

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

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated 
xserver-xorg-video-qxl 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, 26 Nov 2016 17:38:32 +0100
Source: xserver-xorg-video-qxl
Binary: xserver-xorg-video-qxl
Architecture: source amd64
Version: 0.1.4+20161126git4d7160c-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Laurent Bigonville 
Description:
 xserver-xorg-video-qxl - X.Org X server -- QXL display driver
Closes: 799379 801081 845741
Changes:
 xserver-xorg-video-qxl (0.1.4+20161126git4d7160c-1) unstable; urgency=medium
 .
   * Team upload.
   [ Laurent Bigonville ]
   * New git snapshot (4d7160c) (Closes: #845741)
 - Drop debian/patches/pciaccess_io.diff, applied upstream
   * Rely on automatically built dbgsym packages instead of creating a dbg one
   * debian/control: Fix wording in xserver-xspice description (Closes:
 #799379)
   * debian/control: Bump Standards-Version to 3.9.8, no further changes
   * debian/control: Add dh-python to the build-dependencies
   * debian/control: Explicitly build-depend against libxfont-dev
   * Drop debian/patches/xextproto.diff and build-depend against libxext-dev
 instead
   * Disable Xspice again, it's not working with XOrg 1.19 release
   * debian/patches/qxl-kms-disable-composite.patch,
 debian/patches/no-surfaces-kms.patch: Fix performance issues/crashes and
 fix graphical glitches by disabling COMPOSITE extension. (Closes: #801081)
 .
   [ Andreas Boll ]
   * Update a bunch of URLs in packaging to https.
Checksums-Sha1:
 63a3a8dadfe75b0d473c63d79135d47aa9f7a874 2234 
xserver-xorg-video-qxl_0.1.4+20161126git4d7160c-1.dsc
 e793945d8de290e5ddd1ef257d6119ac575d7247 171102 
xserver-xorg-video-qxl_0.1.4+20161126git4d7160c.orig.tar.gz
 8805f5ac66e317f4eba82a5cfbb2d1881ce644c6 70233 
xserver-xorg-video-qxl_0.1.4+20161126git4d7160c-1.diff.gz
 f0ebeb6b0a47d073c672ad072d920ddcd475d294 631896 
xserver-xorg-video-qxl-dbgsym_0.1.4+20161126git4d7160c-1_amd64.deb
 0f07c269d5e29c745d99837faa03ed84a6504f11 7726 
xserver-xorg-video-qxl_0.1.4+20161126git4d7160c-1_amd64.buildinfo
 d58290cd8f7ab4e636c740f6d3a13b6cf431562a 141706 
xserver-xorg-video-qxl_0.1.4+20161126git4d7160c-1_amd64.deb
Checksums-Sha256:
 2ef745922300719d58a7baabeb960482377ae3523c3b47f7e3bf82fd52ce5f8b 2234 

Bug#842446: (no subject)

[Andrey Rahmatullin]

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


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#845777: nagios3: seriously buggy (7 open CVEs) should not be shipped like this in stretch

[Holger Levsen]

package: src:nagios3
severity: serious
version: 3.5.1.dfsg-2

Hi,

according to https://security-tracker.debian.org/tracker/source-package/nagios3
nagios3 in stable, stretch and unstable is affected by

CVE-2016-6209
CVE-2014-1878
CVE-2013-7205
CVE-2013-7108
CVE-2013-7107
CVE-2013-4214

and another unimportant CVE (CVE-2008-5027), so it's high time this
package (in this state) gets removed from stretch.

Upstream has also abendonded it and is developing nagios4.

Please also see #845765.

For stretch users, it's recommend to switch to icinga2, which is largely
compatible.


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#825079: marked as done (Package links against libmysqlclient_r)

[Debian Bug Tracking System]

Your message dated Sat, 26 Nov 2016 16:21:24 +
with message-id 
and subject line Bug#825079: fixed in icinga2 2.5.4-3
has caused the Debian Bug report #825079,
regarding Package links against libmysqlclient_r
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.)


-- 
825079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: icinga2-ido-mysql
Version: 2.4.1-2
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

Please stop linking against libmysqlclient_r and link directly against
libmysqlclient instead.

Your package currently links against libmysqlclient_r. libmysqlclient_r
was the thread-safe version of libmysqlclient in previous MySQL
releases. However, libmysqlclient has been itself been made thread-safe
since before the current libmysqlclient18. Thus libmysqlclient_r is
currently deprecated and provided as a compatibility symlink only, and
will disappear in MySQL 5.7. This change can be made now, in advance of
a possible future transition to libmysqlclient20, which does not provide
the _r variant.

For icinga2, we have done this in Ubuntu with the attached quilt patch,
which I believe is also applicable to Debian.

Thanks,

Robie Basak
Debian MySQL maintainers team
Ubuntu developer
Author: Robie Basak 
Bug-Ubuntu: https://launchpad.net/bugs/1564871
Forwarded: no
Last-Update: 2016-04-01

--- a/third-party/cmake/FindMySQL.cmake
+++ b/third-party/cmake/FindMySQL.cmake
@@ -67,7 +67,7 @@
 $ENV{ProgramFiles}/MySQL/*/lib/${libsuffixDist}
 $ENV{SystemDrive}/MySQL/*/lib/${libsuffixDist})
 ELSE (WIN32)
-  FIND_LIBRARY(MYSQL_LIB NAMES mysqlclient_r
+  FIND_LIBRARY(MYSQL_LIB NAMES mysqlclient
 PATHS
 $ENV{MYSQL_DIR}/libmysql_r/.libs
 $ENV{MYSQL_DIR}/lib
@@ -95,7 +95,7 @@
   FIND_LIBRARY(MYSQL_ZLIB zlib PATHS ${MYSQL_LIB_DIR})
   FIND_LIBRARY(MYSQL_YASSL yassl PATHS ${MYSQL_LIB_DIR})
   FIND_LIBRARY(MYSQL_TAOCRYPT taocrypt PATHS ${MYSQL_LIB_DIR})
-  SET(MYSQL_CLIENT_LIBS mysqlclient_r)
+  SET(MYSQL_CLIENT_LIBS mysqlclient)
   IF (MYSQL_ZLIB)
 SET(MYSQL_CLIENT_LIBS ${MYSQL_CLIENT_LIBS} zlib)
   ENDIF (MYSQL_ZLIB)
--- End Message ---
--- Begin Message ---
Source: icinga2
Source-Version: 2.5.4-3

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

Debian distribution maintenance software
pp.
Alexander Wirt  (supplier of updated icinga2 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, 26 Nov 2016 17:00:09 +0100
Source: icinga2
Binary: icinga2 icinga2-common icinga2-bin icinga2-doc icinga2-classicui 
icinga2-ido-mysql icinga2-ido-pgsql icinga2-dbg libicinga2 icinga2-studio 
vim-icinga2
Architecture: source amd64 all
Version: 2.5.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Alexander Wirt 
Description:
 icinga2- host and network monitoring system
 icinga2-bin - host and network monitoring system - daemon
 icinga2-classicui - host and network monitoring system - classic UI
 icinga2-common - host and network monitoring system - common files
 icinga2-dbg - host and network monitoring system - debug symbols
 icinga2-doc - host and network monitoring system - documentation
 icinga2-ido-mysql - host and network monitoring system - MySQL support
 icinga2-ido-pgsql - host and network monitoring system - PostgreSQL support
 icinga2-studio - host and network monitoring system - studio API GUI
 libicinga2 - host and network monitoring system - internal libraries
 vim-icinga2 - syntax highlighting for Icinga 2 config files in VIM
Closes: 825079
Changes:
 icinga2 (2.5.4-3) unstable; urgency=medium
 .
   * [e09f7d4] Link against libmysqlclient (Closes: #825079)
Checksums-Sha1:
 d6960afcb291cac160b3e74d262ed71a942bc8e2 2927 icinga2_2.5.4-3.dsc
 9bf426b585b7819408f7df7274e3e669049529a5 30468 

Bug#833636: marked as done (compile error with gcc-6)

[Debian Bug Tracking System]

Your message dated Sat, 26 Nov 2016 16:09:21 +
with message-id 
and subject line Bug#845717: Removed package(s) from unstable
has caused the Debian Bug report #833636,
regarding compile error with gcc-6
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.)


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

Package: gtest
Version: 1.7.0-4
Severity: serious
thanks

Hi,

building the alljoyn package with gtest and gcc-6 gives the following 
compile error. I guess the "#include " jusst needs to be replaced 
by "#include " for gcc-6 now.


Thanks!
 Thorsten



g++ -o build/linux/x86_64/release/obj/about/unittest/gtest-all.o -c -Wall 
-Werror -pipe -std=gnu++0x -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Os -m64 -fPIC -Wno-deprecated-declarations -DNDEBUG 
-DROUTER -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX 
-D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC -DQCC_CPU_X86 -DQCC_CPU_X86_64 
-DGTEST_HAS_RTTI=0 -Ibuild/linux/x86_64/release/dist/cpp/inc 
-Ibuild/linux/x86_64/release/dist/c/inc 
-Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc -I/usr/src/gtest 
-I/usr/src/gtest/include /usr/src/gtest/src/gtest-all.cc
In file included from /usr/src/gtest/src/gtest.cc:38:0,
 from /usr/src/gtest/src/gtest-all.cc:42:
/usr/include/c++/6/math.h:63:12: error: 'std::fpclassify' has not been declared
 using std::fpclassify;
^~
/usr/include/c++/6/math.h:64:12: error: 'std::isfinite' has not been declared
 using std::isfinite;
^~~~
/usr/include/c++/6/math.h:65:12: error: 'std::isinf' has not been declared
 using std::isinf;
^
/usr/include/c++/6/math.h:66:12: error: 'std::isnan' has not been declared
 using std::isnan;
^
/usr/include/c++/6/math.h:67:12: error: 'std::isnormal' has not been declared
 using std::isnormal;
^~~~
/usr/include/c++/6/math.h:68:12: error: 'std::signbit' has not been declared
 using std::signbit;
^~~
/usr/include/c++/6/math.h:69:12: error: 'std::isgreater' has not been declared
 using std::isgreater;
^
/usr/include/c++/6/math.h:70:12: error: 'std::isgreaterequal' has not been 
declared
 using std::isgreaterequal;
^~
/usr/include/c++/6/math.h:71:12: error: 'std::isless' has not been declared
 using std::isless;
^~
/usr/include/c++/6/math.h:72:12: error: 'std::islessequal' has not been declared
 using std::islessequal;
^~~
/usr/include/c++/6/math.h:73:12: error: 'std::islessgreater' has not been 
declared
 using std::islessgreater;
^
/usr/include/c++/6/math.h:74:12: error: 'std::isunordered' has not been declared
 using std::isunordered;
^~~
scons: *** [build/linux/x86_64/release/obj/about/unittest/gtest-all.o] 
Error 1

scons: building terminated because of errors.
--- End Message ---
--- Begin Message ---
Version: 1.7.0-4+rm

Dear submitter,

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

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

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

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

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

Bug#845686: marked as done (protobuf: FTBFS (32-bit): name 'long' is not defined)

[Debian Bug Tracking System]

Your message dated Sat, 26 Nov 2016 16:04:28 +
with message-id 
and subject line Bug#845686: fixed in protobuf 3.0.0-9
has caused the Debian Bug report #845686,
regarding protobuf: FTBFS (32-bit): name 'long' is not defined
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.)


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

32-bit Linux builds of protobuf failed:

  Traceback (most recent call last):
File "/«PKGBUILDDIR»/python3/google/protobuf/internal/reflection_test.py", 
line 639, in testIntegerTypes
  TestGetAndDeserialize('optional_uint32', 1 << 31, long)
  NameError: name 'long' is not defined

(Non-Linux builds have been failing for other reasons, per #837310.)

Could you please take a look?

Thanks!

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

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

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated protobuf 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 Nov 2016 16:11:01 +
Source: protobuf
Binary: libprotobuf10 libprotobuf-lite10 libprotobuf-dev libprotoc10 
libprotoc-dev protobuf-compiler python-protobuf python3-protobuf 
libprotobuf-java
Architecture: source amd64 all
Version: 3.0.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian protobuf maintainers 

Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 libprotobuf-dev - protocol buffers C++ library (development files)
 libprotobuf-java - Java bindings for protocol buffers
 libprotobuf-lite10 - protocol buffers C++ library (lite version)
 libprotobuf10 - protocol buffers C++ library
 libprotoc-dev - protocol buffers compiler library (development files)
 libprotoc10 - protocol buffers compiler library
 protobuf-compiler - compiler for protocol buffer definition files
 python-protobuf - Python bindings for protocol buffers
 python3-protobuf - Python 3 bindings for protocol buffers
Closes: 845686
Changes:
 protobuf (3.0.0-9) unstable; urgency=medium
 .
   * Backport upstream fix for Python 3 build failure (closes: #845686).
Checksums-Sha1:
 0d718ff008a78742f5b24a387ca1f4c0f5439af1 3036 protobuf_3.0.0-9.dsc
 412860d6b860a5836f20207390f542e13183ddaf 22828 protobuf_3.0.0-9.debian.tar.xz
 2bfdc7af2997623c7f5ca18bc39b6a124051d2fb 954116 
libprotobuf-dev_3.0.0-9_amd64.deb
 64e448da94a62ecb4dab0ced35c8c29e28546f7b 643918 
libprotobuf-java_3.0.0-9_all.deb
 1636660a3c40b83df269991f72421df8135c12a7 715794 
libprotobuf-lite10-dbgsym_3.0.0-9_amd64.deb
 1359a4e5bfb17e14a82b55846fa36f3f96dcb663 124592 
libprotobuf-lite10_3.0.0-9_amd64.deb
 d2462a06d98e1e0c848d23055783fd7ef2d90a3e 6459362 
libprotobuf10-dbgsym_3.0.0-9_amd64.deb
 baa537a69173509bd0b4d2a9aa8f5d2867014ac4 680836 libprotobuf10_3.0.0-9_amd64.deb
 2086be33f0d22d56fb5d81fa8d9bb2a76780aace 706828 libprotoc-dev_3.0.0-9_amd64.deb
 40407828547dde32c5e0f0e9d83787616dfbb7cd 9018472 
libprotoc10-dbgsym_3.0.0-9_amd64.deb
 46c184b2ced3e8d08c0df4647268540d485087a7 625714 libprotoc10_3.0.0-9_amd64.deb
 c12f129a964c0c69bae8396f9e8b237806809910 51172 
protobuf-compiler-dbgsym_3.0.0-9_amd64.deb
 c20148928009f0499d959455254c94ba0bbac2a0 52784 
protobuf-compiler_3.0.0-9_amd64.deb
 dfd5ac5603444dde0a89a81a08dba2762459a7f1 15239 protobuf_3.0.0-9_amd64.buildinfo
 f9e5df3514bcb5d88561d014d74ba5ea20a78df6 750174 
python-protobuf-dbgsym_3.0.0-9_amd64.deb
 326b6b7d5b734656b90850f7fa7479abf8084123 291738 
python-protobuf_3.0.0-9_amd64.deb
 5d5486fcf7fb9e6c7b4cdbc615ef18b928f3d3cb 765080 

Processed: limit source to xserver-xorg-video-qxl, tagging 801081, tagging 845741

[Debian Bug Tracking System]

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

> limit source xserver-xorg-video-qxl
Limiting to bugs with field 'source' containing at least one of 
'xserver-xorg-video-qxl'
Limit currently set to 'source':'xserver-xorg-video-qxl'

> tags 801081 + pending
Bug #801081 [xserver-xorg-video-qxl] xserver-xorg-video-qxl: QXL video unusable 
due to performance
Added tag(s) pending.
> tags 845741 + pending
Bug #845741 [xserver-xorg-video-qxl] xserver-xorg-video-qxl: Fails to build 
from source with xorg 1.19: implicit declaration of function 'QueryGlyphExtents'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: This issue looks pretty RC

[Debian Bug Tracking System]

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

> severity 797166 grave
Bug #797166 [libjs-chosen] Breaks with jQuery 1.11.3: $.browser is undefined
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: owner 845741

[Debian Bug Tracking System]

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

> owner 845741 !
Bug #845741 [xserver-xorg-video-qxl] xserver-xorg-video-qxl: Fails to build 
from source with xorg 1.19: implicit declaration of function 'QueryGlyphExtents'
Owner recorded as Laurent Bigonville .
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> forcemerge 783430 821588
Bug #783430 [php-mail-mbox] php-mail-mbox: Needs an update for PHP 7.0
Bug #783430 [php-mail-mbox] php-mail-mbox: Needs an update for PHP 7.0
Marked as found in versions php-mail-mbox/0.6.3-1.
Bug #821588 [php-mail-mbox] php-mail-mbox: PHP 7.0 Transition
Merged 783430 821588
> thanks
Stopping processing here.

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

Bug#845301: marked as done (hdf5: CVE-2016-4330 CVE-2016-4331 CVE-2016-4332 CVE-2016-4333)

[Debian Bug Tracking System]

Your message dated Sat, 26 Nov 2016 15:19:28 +
with message-id 
and subject line Bug#845301: fixed in hdf5 1.10.0-patch1+docs-1~exp5
has caused the Debian Bug report #845301,
regarding hdf5: CVE-2016-4330 CVE-2016-4331 CVE-2016-4332 CVE-2016-4333
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.)


-- 
845301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hdf5
Version: 1.8.16+docs-8
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

the following vulnerabilities were published for hdf5.

CVE-2016-4330[0]:
| In the HDF5 1.8.16 library's failure to check if the number of
| dimensions for an array read from the file is within the bounds of the
| space allocated for it, a heap-based buffer overflow will occur,
| potentially leading to arbitrary code execution.

CVE-2016-4331[1]:
| When decoding data out of a dataset encoded with the H5Z_NBIT
| decoding, the HDF5 1.8.16 library will fail to ensure that the
| precision is within the bounds of the size leading to arbitrary code
| execution.

CVE-2016-4332[2]:
| The library's failure to check if certain message types support a
| particular flag, the HDF5 1.8.16 library will cast the structure to an
| alternative structure and then assign to fields that aren't supported
| by the message type and the library will write outside the bounds of
| the heap buffer. This can lead to code execution under the context of
| the library.

CVE-2016-4333[3]:
| The HDF5 1.8.16 library allocating space for the array using a value
| from the file has an impact within the loop for initializing said
| array allowing a value within the file to modify the loop's
| terminator. Due to this, an aggressor can cause the loop's index to
| point outside the bounds of the array when initializing it.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-4330
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4330
[1] https://security-tracker.debian.org/tracker/CVE-2016-4331
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4331
[2] https://security-tracker.debian.org/tracker/CVE-2016-4332
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4332
[3] https://security-tracker.debian.org/tracker/CVE-2016-4333
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4333

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: hdf5
Source-Version: 1.10.0-patch1+docs-1~exp5

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

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

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

Debian distribution maintenance software
pp.
Gilles Filippini  (supplier of updated hdf5 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Nov 2016 23:30:44 +0100
Source: hdf5
Binary: libhdf5-100 libhdf5-cpp-100 libhdf5-dev libhdf5-openmpi-100 
libhdf5-openmpi-dev libhdf5-mpich-100 libhdf5-mpich-dev libhdf5-mpi-dev 
libhdf5-doc hdf5-helpers hdf5-tools libhdf5-serial-dev
Architecture: source
Version: 1.10.0-patch1+docs-1~exp5
Distribution: experimental
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Gilles Filippini 
Description:
 hdf5-helpers - Hierarchical Data Format 5 (HDF5) - Helper tools
 hdf5-tools - Hierarchical Data Format 5 (HDF5) - Runtime tools
 libhdf5-100 - Hierarchical Data Format 5 (HDF5) - runtime files - serial versio
 libhdf5-cpp-100 - Hierarchical Data Format 5 (HDF5) - C++ libraries
 libhdf5-dev - Hierarchical Data Format 5 (HDF5) - development files - serial ve
 libhdf5-doc - Hierarchical Data Format 5 (HDF5) - Documentation
 libhdf5-mpi-dev - Hierarchical Data Format 5 (HDF5) - development files - 
default M
 libhdf5-mpich-100 - Hierarchical Data Format 5 (HDF5) - runtime 

Bug#840094: marked as done (blends-dev: Does not recognize multiline dependencies)

[Debian Bug Tracking System]

Your message dated Sat, 26 Nov 2016 15:18:30 +
with message-id 
and subject line Bug#840094: fixed in blends 0.6.95
has caused the Debian Bug report #840094,
regarding blends-dev: Does not recognize multiline dependencies
to be marked as done.

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

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


-- 
840094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: blends-dev
Version: 0.6.94
Severity: serious

When a "Depends:" field in a task file contains more than one line, only
the first line is used to create the dependency in debian/control. All
others are silently ignored.

I observed this on the "debian-astro" package which uses blends-dev.

Since this is quite dangerous (it is not recognized unless one really
checks the generated d/control file) and generates incorrect blends
packages, I make it severity "serious".

Short code inspection shows that there seem to be *two* places where the
list is parsed (in blend-gen-control): once on gen_control (aroound line
250), and then in load_task (around line 570). In the first appearance,
only the first line is used, while in the second one the full list is
there. Unfortunately, my perl is not enough to fix this...

Best regards

Ole
--- End Message ---
--- Begin Message ---
Source: blends
Source-Version: 0.6.95

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated blends 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, 26 Nov 2016 15:45:52 +0100
Source: blends
Binary: blends-dev blends-common blends-doc blends-tasks
Architecture: source all
Version: 0.6.95
Distribution: unstable
Urgency: medium
Maintainer: Debian Pure Blend Team 
Changed-By: Andreas Tille 
Description:
 blends-common - Debian Pure Blends common package
 blends-dev - Debian Pure Blends common files for developing metapackages
 blends-doc - Debian Pure Blends documentation
 blends-tasks - Debian Pure Blends tasks for new installations
Closes: 840094
Changes:
 blends (0.6.95) unstable; urgency=medium
 .
   [ Ole Streicher ]
   * Adjusted blend-gen-control to handle RFC822 style continuation
 lines as well as backslash style (Closes: #840094).
 .
   [ Andreas Tille ]
   * Remove Mandriva from doc, since link was not active any more.
Checksums-Sha1:
 ceefb761166bc6e522ab2b313043cdd57003d17b 1919 blends_0.6.95.dsc
 15a04f707f75dd0a00fd40366b5b7f18dab2f4ca 101752 blends_0.6.95.tar.xz
 9c72b8d0de8ef78c9be48bb78227ba906eed1c12 23236 blends-common_0.6.95_all.deb
 782d58994847db29e2e470f1c4cff9add986cd59 32904 blends-dev_0.6.95_all.deb
 70ccba27f18be098242086440e563a762cc9f3e9 447442 blends-doc_0.6.95_all.deb
 21d8e6913a3d6c0e4bcafea9b9c74c2c550fdc8c 12806 blends-tasks_0.6.95_all.deb
 2d07e21b370758124b50fc1bd52fac3e5bbdf80b 9031 blends_0.6.95_amd64.buildinfo
Checksums-Sha256:
 ea0120aed00f0891a470832e74879af7d300e0240381294ba95365a606fe0e9d 1919 
blends_0.6.95.dsc
 9770d03cc0f21757c1d24ca1bf8f53595cd1c2a982fb7d41fd2135eb5fa52f62 101752 
blends_0.6.95.tar.xz
 2ee1e56dc3c91ffa4d66f153bf71ceb61d1af44c1356581e5f15b9b1050f8502 23236 
blends-common_0.6.95_all.deb
 09721308f351a1021d6bbdd1f2b87a071d4b7ace2e4c7ead88405307ff56df36 32904 
blends-dev_0.6.95_all.deb
 0563f2e3e68f1dc9c483e96a56c01e69cfee91a925f37ced0972d914f95b373c 447442 
blends-doc_0.6.95_all.deb
 efd7b6f4cf8d4897a88dbc9144d6881ba4855f5c8a08c421010e169d2b711431 12806 
blends-tasks_0.6.95_all.deb
 4ce1307cffb4b3a4b2cbd2267ef4cb29fdc7e5996ee0dbdf300841113364c523 9031 
blends_0.6.95_amd64.buildinfo
Files:
 615dde43903c0ffbfd55852127c1434a 1919 devel optional blends_0.6.95.dsc
 69a321bf1d42cc7edefff952db41cbf3 101752 devel optional blends_0.6.95.tar.xz
 52a089172eb2abfd133628bf093f07e7 23236 misc optional 
blends-common_0.6.95_all.deb
 b1c4e91e9b788199fbefdd33f00c2979 32904 devel optional blends-dev_0.6.95_all.deb
 

Bug#828387: libcrypt-openssl-rsa-perl: FTBFS with openssl 1.1.0

[gregor herrmann]

On Sun, 02 Oct 2016 23:17:10 +0200, Sebastian Andrzej Siewior wrote:

> On 2016-10-01 22:04:02 [+0200], To Kurt Roeckx wrote:
> > compiles, test suite passes. There is still RSA_generate_key().
> since that code is *that* old here is a version without
> RSA_generate_key() so we don't have to touch this one again once that
> function is gone.

Thanks Sebastian.

I also mentioned your patch in the upstream bug:
https://rt.cpan.org/Ticket/Display.html?id=117481
which contains a different patch from Petr Písař.

No reaction there from either Petr or the upstream authors.
I just pinged the ticket again.

If we can't get an upstream reaction (which seems probable), maybe
Petr and Sebastian can at least cross-check their patches and come up
with a common one?


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: U2: Desire


signature.asc
Description: Digital Signature

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> forcemerge 817754 821578
Bug #817754 [php-google-auth] php-google-auth: Needs an update for PHP 7.0
Bug #817754 [php-google-auth] php-google-auth: Needs an update for PHP 7.0
Marked as found in versions google-auth-library-php/0.6-1.
Added tag(s) stretch and sid.
Bug #821578 [php-google-auth] php-google-auth: PHP 7.0 Transition
Merged 817754 821578
> thanks
Stopping processing here.

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

Bug#840393: [Pkg-fonts-devel] Bug#840393: Bug#840393: Bug#840393: Bug#840393: mensis: FTBFS with newly released fontforge

[Vasudev Kamath]

Adrian Bunk  writes:

> On Sat, Nov 12, 2016 at 10:05:06PM +0530, Vasudev Kamath wrote:
>> Adrian Bunk  writes:
>> 
>> > In unstable this is provided by:
>> >   /usr/include/fontforge/basics.h:extern void *grealloc(void *,long size);
>> 
>> Yeah right, but its no longer provided in new fontforge. Upstream also
>> mentioned same.
>
> What is the suggested fix for that?

There is no fix suggested by fontforge upstream. They said the upstream
of mensis is dead and it will be a lot of task to make it work with new
fontforge. So it should be decided if we intend to keep mensis in Debian
or drop it.

Processed: raising the severity, prevents usage of the multilib packages

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #787956 [lib32z1-dev] lib32z1-dev: Compiling anything that includes 
 with -m32 fails
Severity set to 'serious' from 'important'

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

Processed: Building with OpenSSL 1.0.2 is sufficient for stretch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #828563 [src:stunserver] stunserver: FTBFS with openssl 1.1.0
Added tag(s) patch.

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

Bug#828563: Building with OpenSSL 1.0.2 is sufficient for stretch

[Adrian Bunk]

Control: tags -1 patch

Not a perfect solution but sufficient for stretch is the patch below to 
use OpenSSL 1.0.2

The "| libssl-dev (<< 1.1.0~)" is added for backports.

--- debian/control.old  2016-11-26 14:49:45.0 +
+++ debian/control  2016-11-26 14:49:53.0 +
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian VoIP Team 
 Uploaders: Kilian Krause 
-Build-Depends: debhelper (>= 9), libboost-dev, libssl-dev
+Build-Depends: debhelper (>= 9), libboost-dev, libssl1.0-dev | libssl-dev (<< 
1.1.0~)
 Standards-Version: 3.9.6
 Homepage: http://www.stunprotocol.org/
 Vcs-Svn: svn://anonscm.debian.org/pkg-voip/stunserver/trunk/


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#845751: Processed: Re: Bug#845751: yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349

[Matthias Klose]

Control: severity -1 important
Control: reassign -1 gcc-6

Mathieu, these issues are not RC issues, gcc doesn't become unusable.

On 26.11.2016 15:39, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
>> reassign 845751 gcc 4:6.2.1-1
> Bug #845751 [src:yadifa] yadifa FTBFS on ppc64el: internal compiler error: in 
> push_reload, at reload.c:1349
> Bug reassigned from package 'src:yadifa' to 'gcc'.
> No longer marked as found in versions yadifa/2.2.2-1.
> Ignoring request to alter fixed versions of bug #845751 to the same values 
> previously set
> Bug #845751 [gcc] yadifa FTBFS on ppc64el: internal compiler error: in 
> push_reload, at reload.c:1349
> Marked as found in versions gcc-defaults/1.164.
>> thanks
> Stopping processing here.
> 
> Please contact me if you need assistance.
> 

Processed: Re: Processed: Re: Bug#845751: yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #845751 [gcc-6] yadifa FTBFS on ppc64el: internal compiler error: in 
push_reload, at reload.c:1349
Severity set to 'important' from 'serious'
> reassign -1 gcc-6
Bug #845751 [gcc-6] yadifa FTBFS on ppc64el: internal compiler error: in 
push_reload, at reload.c:1349
Ignoring request to reassign bug #845751 to the same package

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

Processed: your mail

[Debian Bug Tracking System]

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

> affects 845751 src:yadifa
Bug #845751 [gcc] yadifa FTBFS on ppc64el: internal compiler error: in 
push_reload, at reload.c:1349
Added indication that 845751 affects src:yadifa
>
End of message, stopping processing here.

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

Processed: Fwd:

[Debian Bug Tracking System]

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

> reassign 845751 gcc-6 6.2.1-4
Bug #845751 [gcc] yadifa FTBFS on ppc64el: internal compiler error: in 
push_reload, at reload.c:1349
Bug reassigned from package 'gcc' to 'gcc-6'.
No longer marked as found in versions gcc-defaults/1.164.
Ignoring request to alter fixed versions of bug #845751 to the same values 
previously set
Bug #845751 [gcc-6] yadifa FTBFS on ppc64el: internal compiler error: in 
push_reload, at reload.c:1349
Marked as found in versions gcc-6/6.2.1-4.
>
End of message, stopping processing here.

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

Processed: Re: Bug#845751: yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349

[Debian Bug Tracking System]

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

> reassign 845751 gcc 4:6.2.1-1
Bug #845751 [src:yadifa] yadifa FTBFS on ppc64el: internal compiler error: in 
push_reload, at reload.c:1349
Bug reassigned from package 'src:yadifa' to 'gcc'.
No longer marked as found in versions yadifa/2.2.2-1.
Ignoring request to alter fixed versions of bug #845751 to the same values 
previously set
Bug #845751 [gcc] yadifa FTBFS on ppc64el: internal compiler error: in 
push_reload, at reload.c:1349
Marked as found in versions gcc-defaults/1.164.
> thanks
Stopping processing here.

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

Bug#845751: yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349

[Mathieu Malaterre]

reassign 845751 gcc 4:6.2.1-1
thanks

On Sat, Nov 26, 2016 at 1:57 PM, Adrian Bunk  wrote:
> Source: yadifa
> Version: 2.2.2-1
> Severity: serious
>
> https://buildd.debian.org/status/fetch.php?pkg=yadifa=ppc64el=2.2.2-1=1480164499
>
> ...
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I./include/dnscore -Wdate-time 
> -D_FORTIFY_SOURCE=2 -DNDEBUG -g -DDNSCORE_BUILD -D_THREAD_SAFE -D_REENTRANT 
> -D_FILE_OFFSET_BITS=64 -I/«PKGBUILDDIR»/lib/dnscore 
> -I/«PKGBUILDDIR»/lib/dnscore/include -fno-ident -ansi -pedantic -Wall 
> -Wno-unknown-pragmas -Werror=missing-field-initializers -std=gnu99 
> -mtune=native -DUSES_GCC -DPREFIX=\"/usr\" -DSYSCONFDIR=\"/etc\" 
> -DLOCALSTATEDIR=\"/var\" -DDATAROOTDIR=\"/usr/share\" 
> -DDATADIR=\"/usr/share\" -DLOCALEDIR=\"/usr/share/locale\" 
> -DLOGDIR=\"/var/log/yadifa\" -DTCLDIR=\"\" -DNDEBUG -O3 -g -DCMR -c 
> src/message_print_format_dig.c -o src/message_print_format_dig.o
> src/message_print_format_dig.c: In function 'message_print_format_dig_buffer':
> src/message_print_format_dig.c:304:1: internal compiler error: in 
> push_reload, at reload.c:1349
>  }
>  ^
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See  for instructions.
> Preprocessed source stored into /tmp/ccy8l7aF.out file, please attach this to 
> your bugreport.
>

ICE reassigned to gcc.

Bug#845757: geneweb FTBFS on mipsel: dpkg-deb (subprocess): compressing tar member: lzma error: Cannot allocate memory

[Adrian Bunk]

Source: geneweb
Version: 6.08+git20161106+dfsg-1
Severity: serious
Tags: patch

https://buildd.debian.org/status/fetch.php?pkg=geneweb=mipsel=6.08+git20161106+dfsg-1=1479583820

...
dpkg-deb: building package 'geneweb-gui' in 
'../geneweb-gui_6.08+git20161106+dfsg-1_mipsel.deb'.
dpkg-deb (subprocess): compressing tar member: lzma error: Cannot allocate 
memory
dpkg-deb: error: subprocess  from tar -cf returned error exit status 2
dh_builddeb: dpkg-deb -Zxz -Sextreme -z9 --build debian/geneweb-gui .. returned 
exit code 2
...


This is caused by xz now using multiple threads by default.

xz is already the default compression method in dpkg,
and I do not see a good reason why geneweb should
deviate from the default compression level.

The following patch should therefore fix it:

--- debian/rules.old2016-11-26 13:50:25.0 +
+++ debian/rules2016-11-26 13:50:59.0 +
@@ -67,5 +67,3 @@
debian/mktemplates
dh_installdebconf
 
-override_dh_builddeb:
-   dh_builddeb -- -Zxz -Sextreme -z9

Bug#845753: r-cran-treescape FTBFS on armhf, i386: Error: segfault from C stack overflow

[Adrian Bunk]

Source: r-cran-treescape
Version: 1.10.17-1
Severity: serious

https://buildd.debian.org/status/package.php?p=r-cran-treescape=sid

...
** preparing package for lazy loading
Creating a generic function for 'toJSON' from package 'jsonlite' in package 
'googleVis'
Warning in rgl.init(initValue, onlyNULL) :
  RGL: unable to open X11 display
Warning: 'rgl_init' failed, running with rgl.useNULL = TRUE
Error: segfault from C stack overflow
* removing 
'/«PKGBUILDDIR»/debian/r-cran-treescape/usr/lib/R/site-library/treescape'
dh_auto_install: R CMD INSTALL -l 
/«PKGBUILDDIR»/debian/r-cran-treescape/usr/lib/R/site-library --clean . 
--built-timestamp='Fri, 28 Oct 2016 12:02:47 +0200' returned exit code 1
debian/rules:4: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2

Bug#845749: libwebp FTBFS on armhf: inlining failed in call to always_inline 'vtrnq_s32': target specific option mismatch

[Adrian Bunk]

Source: libwebp
Version: 0.5.1-3
Severity: serious

https://buildd.debian.org/status/logs.php?pkg=libwebp=armhf

...
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src/webp -DNDEBUG 
-Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -Wall 
-Wdeclaration-after-statement -Wextra -Wfloat-conversion -Wformat 
-Wformat-nonliteral -Wformat -Wformat-security -Wmissing-declarations 
-Wmissing-prototypes -Wold-style-definition -Wshadow -Wunreachable-code 
-Wunused-but-set-variable -Wunused -Wvla -g -O2 
-fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -pthread -c dec_neon.c  -fPIC -DPIC -o 
.libs/libwebpdspdecode_neon_la-dec_neon.o
In file included from ./neon.h:15:0,
 from enc_neon.c:20:
./neon.h: In function 'Transpose4x4':
/usr/lib/gcc/arm-linux-gnueabihf/6/include/arm_neon.h:8203:1: error: inlining 
failed in call to always_inline 'vtrnq_s32': target specific option mismatch
 vtrnq_s32 (int32x4_t __a, int32x4_t __b)
 ^
In file included from enc_neon.c:20:0:
./neon.h:71:23: note: called from here
 const int32x4x2_t out23 = vtrnq_s32(vreinterpretq_s32_u64(row23.val[0]),
   ^
In file included from ./neon.h:15:0,
 from enc_neon.c:20:
/usr/lib/gcc/arm-linux-gnueabihf/6/include/arm_neon.h:14375:1: error: inlining 
failed in call to always_inline 'vreinterpretq_s32_u64': target specific option 
mismatch
 vreinterpretq_s32_u64 (uint64x2_t __a)
 ^
In file included from enc_neon.c:20:0:
./neon.h:71:31: note: called from here
 const int32x4x2_t out23 = vtrnq_s32(vreinterpretq_s32_u64(row23.val[0]),
   ^~
 vreinterpretq_s32_u64(row23.val[1]));
 
...



0.5.1-2 built fine, but back then gcc-5 was the default gcc.

Bug#825079: patch suitable? (icinga2 links against libmysqlclient_r and shouldnt)

[Holger Levsen]

On Sat, Nov 26, 2016 at 01:36:11PM +0100, Emilio Pozuelo Monfort wrote:
> While doing this, please switch the build-dependency from libmysqlclient-dev 
> to
> default-libmysqlclient-dev.

ack.


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#845751: yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349

[Adrian Bunk]

Source: yadifa
Version: 2.2.2-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=yadifa=ppc64el=2.2.2-1=1480164499

...
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I./include/dnscore -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -g -DDNSCORE_BUILD -D_THREAD_SAFE -D_REENTRANT 
-D_FILE_OFFSET_BITS=64 -I/«PKGBUILDDIR»/lib/dnscore 
-I/«PKGBUILDDIR»/lib/dnscore/include -fno-ident -ansi -pedantic -Wall 
-Wno-unknown-pragmas -Werror=missing-field-initializers -std=gnu99 
-mtune=native -DUSES_GCC -DPREFIX=\"/usr\" -DSYSCONFDIR=\"/etc\" 
-DLOCALSTATEDIR=\"/var\" -DDATAROOTDIR=\"/usr/share\" -DDATADIR=\"/usr/share\" 
-DLOCALEDIR=\"/usr/share/locale\" -DLOGDIR=\"/var/log/yadifa\" -DTCLDIR=\"\" 
-DNDEBUG -O3 -g -DCMR -c src/message_print_format_dig.c -o 
src/message_print_format_dig.o
src/message_print_format_dig.c: In function 'message_print_format_dig_buffer':
src/message_print_format_dig.c:304:1: internal compiler error: in push_reload, 
at reload.c:1349
 }
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
Preprocessed source stored into /tmp/ccy8l7aF.out file, please attach this to 
your bugreport.

Bug#845752: r-bioc-shortread FTBFS on armel: Error: segfault from C stack overflow

[Adrian Bunk]

Source: r-bioc-shortread
Version: 1.32.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=r-bioc-shortread=armel=1.32.0-1=1480164374

...
make[1]: Entering directory '/«PKGBUILDDIR»/src'
make[1]: Leaving directory '/«PKGBUILDDIR»/src'
installing to 
/«PKGBUILDDIR»/debian/r-bioc-shortread/usr/lib/R/site-library/ShortRead/libs
** R
** inst
** preparing package for lazy loading
Error: segfault from C stack overflow
* removing 
'/«PKGBUILDDIR»/debian/r-bioc-shortread/usr/lib/R/site-library/ShortRead'
dh_auto_install: R CMD INSTALL -l 
/«PKGBUILDDIR»/debian/r-bioc-shortread/usr/lib/R/site-library --clean . 
--built-timestamp='Wed, 26 Oct 2016 17:08:54 +0200' returned exit code 1
debian/rules:4: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2

Processed: tagging 844915

[Debian Bug Tracking System]

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

> tags 844915 + pending
Bug #844915 [src:notmuch] notmuch: FTBFS: Tests failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#838358: icinga2 builds fine now on armhf?!

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #838358 [src:icinga2] icinga2: FTBFS on armhf: test failures
Severity set to 'serious' from 'important'

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

Bug#825079: patch suitable? (icinga2 links against libmysqlclient_r and shouldnt)

[Emilio Pozuelo Monfort]

On Sat, 26 Nov 2016 12:00:37 + Holger Levsen  wrote:
> Hi,
> 
> icinga2 is currently missing from Stretch due to this bug. Does the
> patch look reasonable to you (icinga2 maintainers)? I'm pondering an NMU
> to get icinga2 back into Stretch…

While doing this, please switch the build-dependency from libmysqlclient-dev to
default-libmysqlclient-dev.

Cheers,
Emilio

Bug#823044: cl-babel: diff for NMU version 0.3.0+20091229-1.1

[Andrey Rahmatullin]

Control: tags 823044 + patch
Control: tags 823044 + pending

Dear maintainer,

I've prepared an NMU for cl-babel (versioned as 0.3.0+20091229-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
WBR, wRAR
diff -u cl-babel-0.3.0+20091229/debian/install cl-babel-0.3.0+20091229/debian/install
--- cl-babel-0.3.0+20091229/debian/install
+++ cl-babel-0.3.0+20091229/debian/install
@@ -1,3 +1,3 @@
-*.asd *.lisp usr/share/common-lisp/source/babel/
+*.asd usr/share/common-lisp/source/babel/
 src/*.lisp usr/share/common-lisp/source/babel/src/
 tests/*.lisp usr/share/common-lisp/source/babel/tests/
diff -u cl-babel-0.3.0+20091229/debian/changelog cl-babel-0.3.0+20091229/debian/changelog
--- cl-babel-0.3.0+20091229/debian/changelog
+++ cl-babel-0.3.0+20091229/debian/changelog
@@ -1,3 +1,11 @@
+cl-babel (0.3.0+20091229-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't install non-existent files (Closes: #823044).
+  * Add explicit debian/source/format.
+
+ -- Andrey Rahmatullin   Sat, 26 Nov 2016 16:54:50 +0500
+
 cl-babel (0.3.0+20091229-1) unstable; urgency=low
 
   * New upstream with minor changes.
only in patch2:
unchanged:
--- cl-babel-0.3.0+20091229.orig/debian/source/format
+++ cl-babel-0.3.0+20091229/debian/source/format
@@ -0,0 +1 @@
+1.0


signature.asc
Description: PGP signature

Processed: cl-babel: diff for NMU version 0.3.0+20091229-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 823044 + patch
Bug #823044 [src:cl-babel] cl-babel: FTBFS: dh_install: Cannot find (any 
matches for) "*.lisp" (tried in "." and "debian/tmp")
Added tag(s) patch.
> tags 823044 + pending
Bug #823044 [src:cl-babel] cl-babel: FTBFS: dh_install: Cannot find (any 
matches for) "*.lisp" (tried in "." and "debian/tmp")
Added tag(s) pending.

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

Bug#821786: trivial-features: diff for NMU version 0.6-1.1

[Andrey Rahmatullin]

Control: tags 821786 + patch
Control: tags 821786 + pending

Dear maintainer,

I've prepared an NMU for trivial-features (versioned as 0.6-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
WBR, wRAR
diff -u trivial-features-0.6/debian/changelog trivial-features-0.6/debian/changelog
--- trivial-features-0.6/debian/changelog
+++ trivial-features-0.6/debian/changelog
@@ -1,3 +1,11 @@
+trivial-features (0.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't install non-existent files (Closes: #821786).
+  * Add explicit debian/source/format.
+
+ -- Andrey Rahmatullin   Sat, 26 Nov 2016 17:00:45 +0500
+
 trivial-features (0.6-1) unstable; urgency=low
 
   * First packaged.
diff -u trivial-features-0.6/debian/install trivial-features-0.6/debian/install
--- trivial-features-0.6/debian/install
+++ trivial-features-0.6/debian/install
@@ -1,3 +1,3 @@
-*.asd *.lisp usr/share/common-lisp/source/trivial-features/
+*.asd usr/share/common-lisp/source/trivial-features/
 src/*.lisp usr/share/common-lisp/source/trivial-features/src/
 tests/*.lisp usr/share/common-lisp/source/trivial-features/tests/
only in patch2:
unchanged:
--- trivial-features-0.6.orig/debian/source/format
+++ trivial-features-0.6/debian/source/format
@@ -0,0 +1 @@
+1.0


signature.asc
Description: PGP signature

Processed: trivial-features: diff for NMU version 0.6-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 821786 + patch
Bug #821786 [src:trivial-features] trivial-features: FTBFS: dh_install: Cannot 
find (any matches for) "*.lisp" (tried in "." and "debian/tmp")
Added tag(s) patch.
> tags 821786 + pending
Bug #821786 [src:trivial-features] trivial-features: FTBFS: dh_install: Cannot 
find (any matches for) "*.lisp" (tried in "." and "debian/tmp")
Added tag(s) pending.

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

Bug#825079: patch suitable? (icinga2 links against libmysqlclient_r and shouldnt)

[Holger Levsen]

Hi,

icinga2 is currently missing from Stretch due to this bug. Does the
patch look reasonable to you (icinga2 maintainers)? I'm pondering an NMU
to get icinga2 back into Stretch…


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Processed: icinga2 builds fine now on armhf?!

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #838358 [src:icinga2] icinga2: FTBFS on armhf: test failures
Severity set to 'important' from 'serious'

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

Bug#838358: icinga2 builds fine now on armhf?!

[Holger Levsen]

control: severity -1 important

Hi,

according to
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/icinga2.html
incinga2 built fine (twice) on armhf on November 16th 2016, so can this
bug be closed now?

looking at
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/icinga2.html
I can see it also build fine on 2016-10-22, while the last failure we
saw was on 2016-10-17.

Downgrading severity for now. Probably closing would be more
appropriate.


-- 
cheers,
Holger


signature.asc
Description: Digital signature