Bug#796806: fix pending upload

[Martín Ferrari]

So, I can reliably reproduce this if I run the build with nice and have
some processes eating the cpu away. I have added the information to the
upstream bug, but in the meantime I am uploading a new release that just
disables these tests.


-- 
Martín Ferrari (Tincho)

Bug#797855: spice-gtk:spice-common/common/generated_* not reliably generated from source

[Liang Guo]

Hi, Chris,

On Thu, Sep 3, 2015 at 3:00 PM, Chris Lamb  wrote:
> Hi Liang,
>
>> I cannot reproduce this error on my build environment. it looks this
>> is caused by lack dependency on python-six module.
>
> Not completely. Please re-read my initial bug report:
>
>> > Depending on the timezone of the build system, the package may FTBFS as
>> > the `spice-common/python_modules/codegen.py` tool used to regenerate
>> > these files requires python-six which is not included in the
>> > Build-Depends.
>> >
>> > (ie. I don't believe simply including python-six as a build-dependency
>> > entirely resolves the issue)
>
> If any of that is unclear, please let me know and I will try and
> rephrase it.
>
> Just as a summary, adding python-six is not complete fix - your package
> would still not being built from the generated sources.
>

spice_codegen.py is called in your build procedure, but not in mine.
even I build
with a brand new pbuilder environment.  with following command line:

TZ=/usr/share/zoneinfo/Etc/GMT-14 pbuilder build spice-gtk_0.29-1.dsc

Do you know the reason?

I remove spice-common/common/generated* to force build system regenerate
these files, the generated files are same with the original file.

Would you like show me the build log with python-six on Build-deps ?

Thanks,
-- 
Liang Guo

Processed (with 1 errors): severity of 797644 is important

[Debian Bug Tracking System]

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

> severity 797644 important
Bug #797644 [kdelibs5-dev] kdelibs5-dev: kopete FTBFS: No rule to make target 
'/usr/lib/libsoprano.so', needed by 'kopete/kopete'
Severity set to 'important' from 'serious'
> tag -1 wontfix
Failed to alter tags of Bug -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_tag did not pass regex check
.

> thanks
Stopping processing here.

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

Processed: Re: Bug#797866: libtorrent: ABI transition needed for libstdc++ v5

[Debian Bug Tracking System]

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

> tag 797866 confirmed
Bug #797866 [src:libtorrent] libtorrent: ABI transition needed for libstdc++ v5
Added tag(s) confirmed.
> quit
Stopping processing here.

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

Processed: tagging 788465

[Debian Bug Tracking System]

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

> tags 788465 + pending
Bug #788465 [kdepim-mobileui-data] kdepim-mobileui-data: fails to upgrade from 
'sid' - trying to overwrite 
/usr/share/kde4/apps/libmessageviewer/pics/mobile_bg.png
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: found 797644 in 4:4.14.2-4

[Debian Bug Tracking System]

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

> found 797644 4:4.14.2-4
Bug #797644 [kdelibs5-dev] kdelibs5-dev: kopete FTBFS: No rule to make target 
'/usr/lib/libsoprano.so', needed by 'kopete/kopete'
Marked as found in versions kde4libs/4:4.14.2-4.
> thanks
Stopping processing here.

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

Processed: severity of 767613 is important

[Debian Bug Tracking System]

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

> severity 767613 important
Bug #767613 [kleopatra] [kleopatra] hangs on OpenPGP-Zertifikate aktualisieren
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#797644: kdelibs5-dev: kopete FTBFS: No rule to make target '/usr/lib/libsoprano.so', needed by 'kopete/kopete'

[Scott Kitterman]

On Tue, 1 Sep 2015 09:45:33 +0100 Simon McVittie  wrote:
> On Tue, 01 Sep 2015 at 09:20:17 +0100, Simon McVittie wrote:
> > If a particular -dev package requires linking with some other library,
> > it should depend on that library's -dev package (the same principle
> > as depending on the -dev packages of the libraries mentioned in a
> > pkg-config .pc file).
> 
> For kopete, installing libsoprano-dev is enough to build successfully.
> I think this means kdelibs5-dev should depend on libsoprano-dev (and the
> -dev packages for any other libraries that it indirectly requires
> in the same way).
> 
> Adding Build-Depends: libsoprano-dev to kopete seems to be a viable
> workaround that would prevent this bug from stalling the libmsn
> sub-transition within the libstdc++ transition, and potentially
> lower its severity to non-RC. I might NMU kopete with that change if
> it becomes necessary.

This was unfortunately necessary as part of the transition from nepomuk to the 
new baloo package.  At the time upstream did the switch, it was not well 
integrated into KDE4 and so we were stuck with dropping some build-depends to 
get the necessary internal build behavior.  As a team, in the Qt-KDE team 
we've been adding libsoprano-dev to other packages as needed and that's the 
right thing to do for kopete.

Scott K

Bug#796806: marked as done (golang-check.v1: Non-determistically FTBFS due to unreliable timing in tests)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 15:30:25 +
with message-id 
and subject line Bug#796806: fixed in golang-check.v1 0.0+git20150729.11d3bc7-2
has caused the Debian Bug report #796806,
regarding golang-check.v1: Non-determistically FTBFS due to unreliable timing 
in tests
to be marked as done.

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

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


-- 
796806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-check.v1
Version: 0.0+git20150729.11d3bc7-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

golang-check.v1's testsuite appears to use method timing/benchmarking in
such
a way that it will non-deterministically FTBFS:

  [..]

 dh_auto_test -O--buildsystem=golang
go test -v gopkg.in/check.v1
  === RUN Test
  
  --
  FAIL: benchmark_test.go:39: BenchmarkS.TestBenchmark
  
  benchmark_test.go:59:
  c.Assert(output.value, Matches, expected)
  ... value string = "PASS: check_test.go:144:
  FixtureHelper.Benchmark1\t  50\t261765 ns/op\n"
  ... regex string = "PASS: check_test\\.go:[0-9]+:
  FixtureHelper\\.Benchmark1\t *100\t *[12][0-9]{5} ns/op\n"
  
  
  --
  FAIL: benchmark_test.go:62: BenchmarkS.TestBenchmarkBytes
  
  benchmark_test.go:74:
  c.Assert(output.value, Matches, expected)
  ... value string = "PASS: check_test.go:151:
  FixtureHelper.Benchmark2\t  50\t346352 ns/op\t   2.96 MB/s\n"
  ... regex string = "PASS: check_test\\.go:[0-9]+:
  FixtureHelper\\.Benchmark2\t *100\t *[12][0-9]{5} ns/op\t
  *[4-9]\\.[0-9]{2} MB/s\n"
  
  OOPS: 125 passed, 2 FAILED
  --- FAIL: Test (0.46s)
  FAIL
  exit status 1
  FAILgopkg.in/check.v1   0.469s
  dh_auto_test: go test -v gopkg.in/check.v1 returned exit code 1
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 1
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/golang-check.v1_0.0+git20150729.11d3bc7-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Aug 21 23:48:20 GMT+12 2015
I: pbuilder-time-stamp: 1440244100
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 9.0.0), dh-golang, golang-go
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on dh-golang; however:
  Package dh-golang is not installed.
 pbuilder-satisfydepends-dummy depends on golang-go; however:
  Package golang-go is not installed.

Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
The following NEW packages will be installed:
  dh-golang{a} golang-go{a} 

Bug#796735: marked as done (ruby-omniauth-kerberos: Missing Build-Depends on ruby-rack-test)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 16:37:29 +
with message-id 
and subject line Bug#796735: fixed in ruby-omniauth-kerberos 0.3.0-2
has caused the Debian Bug report #796735,
regarding ruby-omniauth-kerberos: Missing Build-Depends on ruby-rack-test
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.)


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

Dear Maintainer,

ruby-omniauth-kerberos fails to build from source in unstable/amd64 due
to missing Build-Depends on ruby-rack-test:

  [..]
  
┌──┐
  │ Run tests for ruby2.1 from debian/ruby-tests.rake   
  │
  
└──┘
  
  
RUBYLIB=/tmp/buildd/ruby-omniauth-kerberos-0.3.0/debian/ruby-omniauth-kerberos/usr/lib/ruby/vendor_ruby:.
  rake2.1 -f debian/ruby-tests.rake
  /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
  /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
  `require': cannot load such file -- rack/test (LoadError)
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from

/tmp/buildd/ruby-omniauth-kerberos-0.3.0/spec/omniauth/strategy/kerberos_spec.rb:2:in
`'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`load'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`block in load_spec_files'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`each'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in
`setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in
`invoke'
from /usr/bin/rspec:4:in `'
  /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
  failed
  ERROR: Test "ruby2.1" failed. Exiting.
  dh_auto_install: dh_ruby --install
  /tmp/buildd/ruby-omniauth-kerberos-0.3.0/debian/ruby-omniauth-kerberos
  returned exit code 1
  debian/rules:18: recipe for target 'binary' failed
  make: *** [binary] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/ruby-omniauth-kerberos_0.3.0-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sat Aug 22 03:39:35 GMT+12 2015
I: pbuilder-time-stamp: 1440257975
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 7.0.50~), gem2deb, rake, ruby-omniauth-multipassword, 
ruby-rspec, ruby-timfel-krb5-auth (>= 0.8)
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...

Processed: severity of 796657 is serious

[Debian Bug Tracking System]

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

> severity 796657 serious
Bug #796657 [python3-pygit2] python3-pygit2: Can't import pygit2 
(PermissionError: [Errno 13] Permission denied: 
'/usr/lib/python3/dist-packages/pygit2/__pycache__/pygit2_cffi_1b714a1x5470904.c')
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 795814

[Debian Bug Tracking System]

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

> tags 795814 - pending
Bug #795814 [src:k3d] FTBFS: boost/math/tools/test.hpp: No such file or 
directory
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#797618: marked as done (opencolorio: transition needed for g++-5 ABIs)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 18:00:13 +
with message-id 
and subject line Bug#796925: fixed in opencolorio 1.0.9~dfsg0-4
has caused the Debian Bug report #796925,
regarding opencolorio: transition needed for g++-5 ABIs
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.)


-- 
796925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opencolorio
Version: 1.0.9~dfsg0-3
Severity: serious
Justification: breaks reverse-dependencies
Tags: patch

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of opencolorio, std::string appears in header files that
get installed, so it seems very likely that a transition is needed.
The transition consists of renaming the library package, adding a
v5 suffix. A patch is available in Ubuntu,
.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

In the case of opencolorio:

* there is a circular build-dep with openimageio which will need some
  care (Ubuntu temporarily disabled openimageio support in opencolorio,
  which seems a reasonable solution)
* boost, opencv, openexr already started their transitions
* Qt does not need a rename
* I think the rest are C and so do not need renames

so I think these two packages are ready to go.

The package is likely to be NMU'd in the near future if there is no
maintainer response, with a patch very similar to the one in Ubuntu. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html
--- End Message ---
--- Begin Message ---
Source: opencolorio
Source-Version: 1.0.9~dfsg0-4

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

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated opencolorio package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 Sep 2015 13:55:34 +0200
Source: opencolorio
Binary: libopencolorio-dev libopencolorio1v5 opencolorio-tools opencolorio-doc 
python-pyopencolorio
Architecture: source amd64 all
Version: 1.0.9~dfsg0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Matteo F. Vescovi 
Description:
 libopencolorio-dev - complete color management solution - development
 libopencolorio1v5 - complete color management solution - runtime
 opencolorio-doc - complete color management solution - documentation
 opencolorio-tools - complete color management solution - utilities
 python-pyopencolorio - complete color management solution - python bindings
Closes: 796925
Changes:
 opencolorio (1.0.9~dfsg0-4) unstable; urgency=medium
 .
   * debian/: fix g++-5 ABI transition issue (Closes: #796925)
   * debian/control:
 - libopenimageio-dev b-dep dropped
 - Uploader e-mail address updated
   * 

Processed: Actually this bug makes clang not so useful

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 clang-3.5
Bug #797917 [libboost-program-options-dev] libboost-program-options-dev: 
clang++: undefined reference to boost::program_options::arg
Bug reassigned from package 'libboost-program-options-dev' to 'clang-3.5'.
No longer marked as found in versions boost-defaults/1.58.0.1.
Ignoring request to alter fixed versions of bug #797917 to the same values 
previously set
> retitle -1 clang should use the new CXX11_ABI
Bug #797917 [clang-3.5] libboost-program-options-dev: clang++: undefined 
reference to boost::program_options::arg
Changed Bug title to 'clang should use the new CXX11_ABI' from 
'libboost-program-options-dev: clang++: undefined reference to 
boost::program_options::arg'
> severity -1 serious
Bug #797917 [clang-3.5] clang should use the new CXX11_ABI
Severity set to 'serious' from 'normal'

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

Bug#797855: spice-gtk:spice-common/common/generated_* not reliably generated from source

[Chris Lamb]

Hi Liang,

> spice_codegen.py is called in your build procedure, but not in mine.

Sure, no problem :)  Without codegen being called:

 
https://reproducible.debian.net/rbuild/unstable/amd64/spice-gtk_0.29-1.rbuild.log

With codegen being called:

 
https://reproducible.debian.net/logs/unstable/amd64/spice-gtk_0.29-1.build2.log.gz

If it helps, here is a diff between the two:

 
https://reproducible.debian.net/logdiffs/unstable/amd64/spice-gtk_0.29-1.diff.gz


Regards,

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

Bug#778039: marked as done (oolite: ftbfs with GCC-5)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 17:22:23 +
with message-id 
and subject line Bug#778039: fixed in oolite 1.82-1
has caused the Debian Bug report #778039,
regarding oolite: ftbfs with GCC-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.)


-- 
778039: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:oolite
Version: 1.77.1-3
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/oolite_1.77.1-3_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files.  For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html

[...]
make[5]: *** Waiting for unfinished jobs
/usr/share/GNUstep/Makefiles/rules.make:468: recipe for target 
'obj/oolite.obj/Entity.m.o' failed
src/Core/Entities/PlayerEntityLegacyScriptEngine.m: In function 
'-[PlayerEntity(Scripting) setFuelLeak:]':
src/Core/Entities/PlayerEntityLegacyScriptEngine.m:2148:3: error: format not a 
string literal and no format arguments [-Werror=format-security]
   OOLog(kOOLogNoteFuelLeak, @"FUEL LEAK activated!");
   ^
src/Core/Entities/PlayerEntityLegacyScriptEngine.m: In function 
'-[PlayerEntity(Scripting) debugOn]':
src/Core/Entities/PlayerEntityLegacyScriptEngine.m:2333:2: error: format not a 
string literal and no format arguments [-Werror=format-security]
  OOLog(kOOLogDebugOnOff, @"SCRIPT debug messages ON");
  ^
src/Core/Entities/PlayerEntityLegacyScriptEngine.m: In function 
'-[PlayerEntity(Scripting) debugOff]':
src/Core/Entities/PlayerEntityLegacyScriptEngine.m:2339:2: error: format not a 
string literal and no format arguments [-Werror=format-security]
  OOLog(kOOLogDebugOnOff, @"SCRIPT debug messages OFF");
  ^
src/Core/Entities/PlayerEntityLegacyScriptEngine.m: In function 
'-[PlayerEntity(Scripting) setGalacticHyperspaceFixedCoordsTo:]':
src/Core/Entities/PlayerEntityLegacyScriptEngine.m:2863:3: error: format not a 
string literal and no format arguments [-Werror=format-security]
   OOLog(@"player.setGalacticHyperspaceFixedCoords.invalidInput",
   ^
src/Core/Entities/PlayerEntityLoadSave.m: In function '-[PlayerEntity(LoadSave) 
quicksavePlayer]':
src/Core/Entities/PlayerEntityLoadSave.m:188:3: error: format not a string 
literal and no format arguments [-Werror=format-security]
   OOLog(@"quickSave.failed.noName", @"ERROR no file name returned by 
[[gameView gameController] playerFileToLoad]");
   ^
cc1obj: some warnings being treated as errors
make[5]: *** [obj/oolite.obj/PlanetEntity.m.o] Error 1
/usr/share/GNUstep/Makefiles/rules.make:468: recipe for target 
'obj/oolite.obj/PlanetEntity.m.o' failed
cc1obj: some warnings being treated as errors
make[5]: *** [obj/oolite.obj/PlayerEntityLoadSave.m.o] Error 1
/usr/share/GNUstep/Makefiles/rules.make:468: recipe for target 
'obj/oolite.obj/PlayerEntityLoadSave.m.o' failed
cc1obj: some warnings being treated as errors
make[5]: *** [obj/oolite.obj/PlayerEntityLegacyScriptEngine.m.o] Error 1
/usr/share/GNUstep/Makefiles/rules.make:468: recipe for target 
'obj/oolite.obj/PlayerEntityLegacyScriptEngine.m.o' failed
cc1obj: some warnings being treated as errors
make[5]: *** [obj/oolite.obj/PlayerEntityControls.m.o] Error 1
/usr/share/GNUstep/Makefiles/rules.make:468: recipe for target 
'obj/oolite.obj/PlayerEntityControls.m.o' failed
cc1obj: some warnings being treated as errors
make[5]: *** [obj/oolite.obj/PlayerEntity.m.o] Error 1
/usr/share/GNUstep/Makefiles/rules.make:468: recipe for target 
'obj/oolite.obj/PlayerEntity.m.o' failed
make[4]: *** [internal-objc_program-all_] 

Processed: your mail

[Debian Bug Tracking System]

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

> tags 797865 + fixed pending
Bug #797865 [src:libpqxx] libpqxx: ABI transition needed for libstdc++ v5
Added tag(s) fixed and pending.
> thanks
Stopping processing here.

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

Bug#788465: marked as done (kdepim-mobileui-data: fails to upgrade from 'sid' - trying to overwrite /usr/share/kde4/apps/libmessageviewer/pics/mobile_bg.png)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 16:51:22 +
with message-id 
and subject line Bug#788465: fixed in kdepim 4:4.14.10-2
has caused the Debian Bug report #788465,
regarding kdepim-mobileui-data: fails to upgrade from 'sid' - trying to 
overwrite /usr/share/kde4/apps/libmessageviewer/pics/mobile_bg.png
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.)


-- 
788465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kdepim-mobileui-data
Version: 4:4.14.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package kdepim-mobileui-data.
  Preparing to unpack .../kdepim-mobileui-data_4%3a4.14.5-1_all.deb ...
  Unpacking kdepim-mobileui-data (4:4.14.5-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kdepim-mobileui-data_4%3a4.14.5-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/kde4/apps/libmessageviewer/pics/mobile_bg.png', which is also in 
package libmessageviewer4 4:4.14.2-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

Andreas


libmessageviewer4=4%4.14.2-2_kdepim-mobileui-data=4%4.14.5-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: kdepim
Source-Version: 4:4.14.10-2

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated kdepim 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, 03 Sep 2015 11:05:40 -0400
Source: kdepim
Binary: kdepim kdepim-mobile kdepim-doc akregator kaddressbook 
kaddressbook-mobile kalarm kdepim-kresources storageservicemanager kleopatra 
kmail kmail-mobile knode knotes notes-mobile konsolekalendar kontact 
tasks-mobile korganizer korganizer-mobile ktimetracker libcalendarsupport4 
libcomposereditorng4 libeventviews4 libincidenceeditorsng4 libpimcommon4 
libkdepim4 libkdepimdbusinterfaces4 libkdgantt2-0 libkleo4 libkpgp4 libksieve4 
libkmanagesieve4 libksieveui4 libmailcommon4 libmailimporter4 
libmessagecomposer4 libmessagecore4 libmessagelist4 libmessageviewer4 
libsendlater4 libfollowupreminder4 libtemplateparser4 libkdepimmobileui4 
kdepim-mobileui-data kjots blogilo akonadiconsole libnoteshared4 ktnef 
kdepim-themeeditors kdepim-dbg
Architecture: source amd64 all
Version: 4:4.14.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Scott Kitterman 
Description:
 akonadiconsole - management and debugging console for akonadi
 akregator  - RSS/Atom feed aggregator
 blogilo- graphical blogging client
 kaddressbook - address book and contact data manager
 kaddressbook-mobile - address book and contact data manager for mobile 
environments
 kalarm - alarm message, command and email scheduler
 kdepim - Personal Information Management apps from the official KDE releas
 kdepim-dbg - debugging symbols for kdepim
 kdepim-doc - KDE Personal Information Management library documentation
 kdepim-kresources - KDE PIM resource plugins
 kdepim-mobile - Personal Information Management apps for mobile environments
 kdepim-mobileui-data - common data files for KDE PIM mobile applications
 kdepim-themeeditors - Theme Editors for KDE PIM applications
 kjots  - note-taking utility
 kleopatra  - certificate Manager
 kmail  - full featured graphical email client
 kmail-mobile - email client for mobile environments
 knode  - 

Bug#796925: marked as done (opencolorio: library transition needed with GCC 5 as default)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 18:00:13 +
with message-id 
and subject line Bug#796925: fixed in opencolorio 1.0.9~dfsg0-4
has caused the Debian Bug report #796925,
regarding opencolorio: library transition needed with GCC 5 as default
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.)


-- 
796925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opencolorio
Version: 1.0.9~dfsg0-3
Severity: serious
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Hi,

your library exposes std::string or std::list in its public API, and
therefore the library package needs to be renamed.

Specifically I'm concerned about the string member of
OpenColorIO::Exception; probably safer overall to rename the package.

Cheers,
Julien

The following is a form letter:

Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 are using the new ABI.  Libraries built
from this source package export some of the new __cxx11 or B5cxx11 symbols, and
dropping other symbols.  If these symbols are part of the API of the library,
then this rebuild with g++-5 will trigger a transition for the library.

What is needed:

 - Rebuild the library using g++/g++-5. Note that most likely all C++
   libraries within the build dependencies need a rebuild too. You can
   find the log for a rebuild in
 https://people.debian.org/~doko/logs/gcc5-20150813/
   Search for "BEGIN GCC CXX11" in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.
 
 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append "v5" to the name of the package
   (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   cont...@bugs.debian.org:
   
 user release.debian@packages.debian.org
 usertag  + transition
 block  by 790756
 reassign  release.debian.org
   
 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition



signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: opencolorio
Source-Version: 1.0.9~dfsg0-4

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

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated opencolorio package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 Sep 2015 13:55:34 +0200
Source: opencolorio
Binary: libopencolorio-dev libopencolorio1v5 opencolorio-tools opencolorio-doc 
python-pyopencolorio
Architecture: source amd64 all
Version: 1.0.9~dfsg0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Matteo F. Vescovi 

Bug#797955: initramfs-tools: initramfs fails to activate swap on encrypted LVM2 partition; fails boot

[Arnaud Installe]

Package: initramfs-tools
Version: 0.120
Severity: critical
Justification: breaks the whole system

All my partitions (except /boot) are on encrypted LVM2 partitions.

When booting, initramfs asks for the passwords to unlock the /root & /usr
partitions, which are mounted successfully. It then fails to ask for the swap
partition password, instead looping a few minutes, posting messages that it is
waiting for all volumes to become available and "/run/lvm/lvmetad.socket:
connect failed". Disabling lvmetad did not help.

Workaround:

Eventually, it dropped to a shell, which allowed me to run cryptsetup for the
swap partition. After that, I exited the shell, and the system booted
successfully.

My setup:

/etc/crypttab:
==
boulez-_home__crypt UUID=70967099-611f-4082-aad4-3d3e9966fad6 /etc/secretkey
luks
boulez-_root__crypt UUID=b8806964-812e-4239-8914-60b1c33c0491 none luks
boulez-_swap__crypt UUID=d7b4dcc6-3d5d-408b-a5cf-60af0fe9260f none luks
boulez-_usr__crypt UUID=386fb30f-389d-4feb-9c59-352628c0de6b none luks
boulez-_var__crypt UUID=97d4e051-a1b8-4ecc-9dd3-5a69eeed4686 /etc/secretkey
luks
==

/etc/fstab:
==
proc  /proc   procdefaults
0   0
/dev/mapper/boulez-_root__crypt   /   ext4
noatime,errors=remount-ro 0   1
# /boot was on /dev/sda1 during installation
UUID=b3cbbc88-4911-42aa-ba25-dce6a6222ae7 /boot   ext3noatime
0   2
/dev/mapper/boulez-_home__crypt   /home   ext4noatime
0   2
/dev/mapper/boulez-_usr__crypt/usrext4noatime
0   2
/dev/mapper/boulez-_var__crypt/varext4noatime
0   2
/dev/mapper/boulez-_swap__crypt   noneswapsw
0   0
==



-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 19M Aug 17 16:54 /boot/initrd.img-4.0.0-1-amd64
-rw-r--r-- 1 root root 19M Sep  3 22:41 /boot/initrd.img-4.1.0-2-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.1.0-2-amd64 root=/dev/mapper/boulez-_root__crypt ro quiet 
atkbd.reset

-- resume
RESUME=/dev/mapper/boulez-_swap__crypt
-- /proc/filesystems
btrfs
ext3
ext2
ext4
fuseblk

-- lsmod
Module  Size  Used by
rfcomm 61440  14
fuse   86016  3
ctr16384  2
ccm20480  2
ipt_MASQUERADE 16384  1
nf_nat_masquerade_ipv416384  1 ipt_MASQUERADE
iptable_nat16384  1
nf_nat_ipv416384  1 iptable_nat
xt_addrtype16384  2
br_netfilter   24576  0
nf_nat 20480  2 nf_nat_ipv4,nf_nat_masquerade_ipv4
bridge102400  1 br_netfilter
stp16384  1 bridge
llc16384  2 stp,bridge
dm_thin_pool   61440  1
dm_persistent_data 53248  1 dm_thin_pool
dm_bio_prison  16384  1 dm_thin_pool
libcrc32c  16384  1 dm_persistent_data
cpufreq_stats  16384  0
cpufreq_conservative16384  0
cpufreq_userspace  16384  0
cpufreq_powersave  16384  0
bnep   20480  2
binfmt_misc20480  1
pci_stub   16384  1
vboxpci24576  0
vboxnetadp 28672  0
vboxnetflt 28672  0
vboxdrv   385024  3 vboxnetadp,vboxnetflt,vboxpci
ip6t_REJECT16384  2
nf_reject_ipv6 16384  1 ip6t_REJECT
nf_log_ipv616384  3
nf_conntrack_ipv6  20480  1
nf_defrag_ipv6 36864  1 nf_conntrack_ipv6
ip6table_filter16384  1
ip6_tables 28672  1 ip6table_filter
ipt_REJECT 16384  2
nf_reject_ipv4 16384  1 ipt_REJECT
xt_limit   16384  2
nf_log_ipv416384  3
nf_log_common  16384  2 nf_log_ipv4,nf_log_ipv6
xt_LOG 16384  6
xt_tcpudp  16384  32
nf_conntrack_ipv4  20480  3
nf_defrag_ipv4 16384  1 nf_conntrack_ipv4
xt_conntrack   16384  3
nf_conntrack   94208  6 
nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4,nf_conntrack_ipv6
iptable_filter 16384  1
ip_tables  28672  2 iptable_filter,iptable_nat
x_tables   28672  12 
ip6table_filter,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_limit,xt_conntrack,xt_LOG,iptable_filter,ipt_REJECT,ip6_tables,xt_addrtype,ip6t_REJECT
qmi_wwan   24576  0
cdc_wdm20480  2 qmi_wwan
usbnet 36864  1 qmi_wwan
mii16384  1 usbnet
qcserial   20480  0
usb_wwan   20480  1 qcserial
uvcvideo   86016  0
videobuf2_vmalloc  16384  1 uvcvideo
videobuf2_memops   16384  1 videobuf2_vmalloc
videobuf2_core 40960  1 uvcvideo
v4l2_common16384  1 videobuf2_core
videodev  131072  3 uvcvideo,v4l2_common,videobuf2_core
media  20480  2 uvcvideo,videodev
usbserial 

Bug#788708: iceweasel: GStreamer causes segmentation fault

[Fabio Natali]

Package: iceweasel
Version: 40.0.3-3
Followup-For: Bug #788708

Hi everyone!

Since a recent upgrade, Iceweasel has been crashing regularly whenever
a video is loaded (eg on youtube pages). The crash happens immediately
and no part of the video is shown.

I'm on Sid but tried different Iceweasel versions (testing, unstable
and experimental). All of them were affected by the issue.

I tried with an empty `.mozilla` folder and with the `-safe-mode`
option - still no luck.

Any hints?

Thanks,

Fabio.


-- Package-specific info:

-- Extensions information
Name: Adblock Plus
Location: ${PROFILE_EXTENSIONS}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: enabled

Name: Default theme
Location: 
/usr/lib/iceweasel/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled

-- Plugins information
Name: Gnome Shell Integration
Location: /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
Package: gnome-shell
Status: enabled


-- Addons package information
ii  gnome-shell3.16.3-1 amd64graphical shell for the GNOME des
ii  iceweasel  40.0.3-3 amd64Web browser based on Firefox

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

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

Versions of packages iceweasel depends on:
ii  debianutils   4.5.1
ii  fontconfig2.11.0-6.3
ii  libasound21.0.29-1
ii  libatk1.0-0   2.16.0-2
ii  libc6 2.19-19
ii  libcairo2 1.14.2-2
ii  libdbus-1-3   1.8.20-1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2
ii  libffi6   3.2.1-3
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-4
ii  libgcc1   1:5.2.1-15
ii  libgdk-pixbuf2.0-02.31.5-1
ii  libglib2.0-0  2.44.1-1.1
ii  libgtk2.0-0   2.24.28-1
ii  libhunspell-1.3-0 1.3.3-3+b1
ii  libnspr4  2:4.10.9-2
ii  libnss3   2:3.20-1
ii  libpango-1.0-01.36.8-3
ii  libsqlite3-0  3.8.11.1-1
ii  libstartup-notification0  0.12-4
ii  libstdc++65.2.1-15
ii  libvpx2   1.4.0-4
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.8-1+b1
ii  libxt61:1.1.4-1+b1
ii  procps2:3.3.10-3
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages iceweasel recommends:
ii  gstreamer1.0-libav 1.4.5-3
ii  gstreamer1.0-plugins-good  1.4.5-2+b2

Versions of packages iceweasel suggests:
ii  fonts-lmodern  2.004.4-5
ii  fonts-stix [otf-stix]  1.1.1-3
ii  libcanberra0   0.30-2.1
ii  libgnomeui-0   2.24.5-3
ii  libgssapi-krb5-2   1.13.2+dfsg-2
pn  mozplugger 

-- no debconf information

Bug#777924: marked as done (kde-workspace: ftbfs with GCC-5)

[Debian Bug Tracking System]

Your message dated Thu, 3 Sep 2015 22:39:08 +0200
with message-id <55e8afec.2020...@debian.org>
and subject line Re: kde-workspace: ftbfs with GCC-5
has caused the Debian Bug report #777924,
regarding kde-workspace: ftbfs with GCC-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.)


-- 
777924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kde-workspace
Version: 4:4.11.13-2
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/kde-workspace_4.11.13-2_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files.  For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html

[...]
+#MISSING: 4:4.11.13-2# _ZN4KWin15ScreenPaintDataD0Ev@ABI_1_5 4:4.11.1
+#MISSING: 4:4.11.13-2# _ZN4KWin15ScreenPaintDataD1Ev@ABI_1_5 4:4.11.1
+#MISSING: 4:4.11.13-2# _ZN4KWin15ScreenPaintDataD2Ev@ABI_1_5 4:4.11.1
  _ZN4KWin15ScreenPaintDataaSERKS0_@ABI_1_5 4:4.11.1
  _ZN4KWin15ScreenPaintDatamLERK9QVector2D@ABI_1_5 4:4.11.1
  _ZN4KWin15ScreenPaintDatamLERK9QVector3D@ABI_1_5 4:4.11.1
@@ -186,9 +186,9 @@
  _ZN4KWin19xRenderBlendPictureEd@ABI_1_5 4:4.11.1
  _ZN4KWin21GlobalShortcutsEditorC1EP7QWidget@ABI_1_5 4:4.11.1
  _ZN4KWin21GlobalShortcutsEditorC2EP7QWidget@ABI_1_5 4:4.11.1
- _ZN4KWin21GlobalShortcutsEditorD0Ev@ABI_1_5 4:4.11.1
- _ZN4KWin21GlobalShortcutsEditorD1Ev@ABI_1_5 4:4.11.1
- _ZN4KWin21GlobalShortcutsEditorD2Ev@ABI_1_5 4:4.11.1
+#MISSING: 4:4.11.13-2# _ZN4KWin21GlobalShortcutsEditorD0Ev@ABI_1_5 4:4.11.1
+#MISSING: 4:4.11.13-2# _ZN4KWin21GlobalShortcutsEditorD1Ev@ABI_1_5 4:4.11.1
+#MISSING: 4:4.11.13-2# _ZN4KWin21GlobalShortcutsEditorD2Ev@ABI_1_5 4:4.11.1
  _ZN4KWin22xRenderOffscreenTargetEv@ABI_1_5 4:4.11.1
  _ZN4KWin28scene_xRenderOffscreenTargetEv@ABI_1_5 4:4.11.1
  _ZN4KWin31scene_setXRenderOffscreenTargetEj@ABI_1_5 4:4.11.1
@@ -402,4 +402,4 @@
  _ZTVN4KWin9PaintDataE@ABI_1_5 4:4.11.1
  _ZZN4KWin10connectionEvE5s_con@ABI_1_5 4:4.11.1
  dlrestrictions_data@ABI_1_5 4:4.11.1
- (c++)"non-virtual thunk to 
KWin::GlobalShortcutsEditor::~GlobalShortcutsEditor()@ABI_1_5" 4:4.11.1
+#MISSING: 4:4.11.13-2# (c++)"non-virtual thunk to 
KWin::GlobalShortcutsEditor::~GlobalShortcutsEditor()@ABI_1_5" 4:4.11.1
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
dh_makeshlibs: failing due to earlier errors
make[2]: *** [override_dh_makeshlibs] Error 2
debian/rules:27: recipe for target 

Processed: tagging 797332

[Debian Bug Tracking System]

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

> tags 797332 + stretch sid
Bug #797332 [src:ibus-pinyin] ibus-pinyin: hardcoded dependency on libpyzy-1.0-0
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

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

Processed: ibus-pinyin: diff for NMU version 1.5.0-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 797332 + patch
Bug #797332 [src:ibus-pinyin] ibus-pinyin: hardcoded dependency on libpyzy-1.0-0
Added tag(s) patch.
> tags 797332 + pending
Bug #797332 [src:ibus-pinyin] ibus-pinyin: hardcoded dependency on libpyzy-1.0-0
Added tag(s) pending.

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

Bug#797944: simgear: library transition needed with GCC 5 as default

[Julien Cristau]

Source: simgear
Version: 3.4.0-2
Severity: serious
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Hi,

your library exposes std::string or std::list in its public API, and
therefore the library package needs to be renamed.

Cheers,
Julien

The following is a form letter:

Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 are using the new ABI.  Libraries built
from this source package export some of the new __cxx11 or B5cxx11 symbols, and
dropping other symbols.  If these symbols are part of the API of the library,
then this rebuild with g++-5 will trigger a transition for the library.

What is needed:

 - Rebuild the library using g++/g++-5. Note that most likely all C++
   libraries within the build dependencies need a rebuild too. You can
   find the log for a rebuild in
 https://people.debian.org/~doko/logs/gcc5-20150813/
   Search for "BEGIN GCC CXX11" in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.
 
 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append "v5" to the name of the package
   (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   cont...@bugs.debian.org:
   
 user release.debian@packages.debian.org
 usertag  + transition
 block  by 790756
 reassign  release.debian.org
   
 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition



signature.asc
Description: Digital signature

Bug#797941: src:pbnj: maintainer address bounces

[Ansgar Burchardt]

Source: pbnj
Severity: serious
Tags: sid

The maintainer address for pbnj bounces, see below.

Given the package was last uploaded by the maintainer in 2007, maybe the
package should be orphaned?

Ansgar

Mail Delivery System  writes:
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   ja...@ccs.neu.edu
> SMTP error from remote mail server after RCPT TO::
> host amber.ccs.neu.edu [129.10.116.51]: 550 unknown user
>
> -- This is a copy of the message, including all the headers. --
>
[...]
> To: ja...@ccs.neu.edu (Joshua D. Abraham), gregor herrmann 
> X-DAK: dak process-upload
> X-Debian: DAK
> X-Debian-Package: pbnj
> Precedence: bulk
> Auto-Submitted: auto-generated
> MIME-Version: 1.0
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: 8bit
> Subject: pbnj_2.04-4.1_sourceonly.changes ACCEPTED into unstable
> Message-Id: 
> Date: Mon, 31 Aug 2015 17:23:33 +
>
>
>
> Accepted:
>
> Format: 1.8
> Date: Wed, 26 Aug 2015 18:37:26 +0200
> Source: pbnj
> Binary: pbnj
> Architecture: source
> Version: 2.04-4.1
> Distribution: unstable
> Urgency: medium
> Maintainer: Joshua D. Abraham 
> Changed-By: gregor herrmann 
> Closes: 795637
> Description: 
>  pbnj   - a suite of tools to monitor changes on a network
> Changes:
>  pbnj (2.04-4.1) unstable; urgency=medium
>  .
>* Non-maintainer upload.
>* Fix "FTBFS with perl 5.22 in experimental (MakeMaker changes)":
>  use DESTDIR in debian/rules.
>  (Closes: #795637)
> Checksums-Sha1: 
>  e639e9d6ffbf13ce22995a8d5dc3f98846f2d7d1 1959 pbnj_2.04-4.1.dsc
>  0a497e7c312526937613ff9238cbb7be0562293f 2841 pbnj_2.04-4.1.diff.gz
> Checksums-Sha256: 
>  717239508ec532f3f59e5f520efb511aa9e756680c358ca22237cdba294ab572 1959 
> pbnj_2.04-4.1.dsc
>  16f0653da19de1b6e2819ebd67a59fb047196320927b4674af612ce8d1594821 2841 
> pbnj_2.04-4.1.diff.gz
> Files: 
>  3563b6f8fab4f91601346ce046338bcb 1959 net optional pbnj_2.04-4.1.dsc
>  6b6fd5e1386e11c477ffa7647c632485 2841 net optional pbnj_2.04-4.1.diff.gz
>
>
>
> Thank you for your contribution to Debian.

Bug#795814: FTBFS: boost/math/tools/test.hpp: No such file or directory

[Jonathan Wiltshire]

On Mon, Aug 24, 2015 at 09:30:25AM +0100, Manuel A. Fernandez Montecelo wrote:
> So it will need a bit more investigation and possibly to speak with
> upstream about it -- I think that the fix will need a few days (at
> least) to arrive.

As there is no prospect of a fix for now and k3d is causing a blockage on
several interrelated transitions, I have temporarily removed it from
testing.



-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Processed: reopening 796925

[Debian Bug Tracking System]

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

> reopen 796925
Bug #796925 {Done: m...@debian.org (Matteo F. Vescovi)} [src:opencolorio] 
opencolorio: library transition needed with GCC 5 as default
Bug #797618 {Done: m...@debian.org (Matteo F. Vescovi)} [src:opencolorio] 
opencolorio: transition needed for g++-5 ABIs
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions opencolorio/1.0.9~dfsg0-4.
No longer marked as fixed in versions opencolorio/1.0.9~dfsg0-4.
> thanks
Stopping processing here.

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

Bug#797917: Actually this bug makes clang not so useful

[Danny Edel]

On Thu, 3 Sep 2015 17:45:27 + (UTC) Gianfranco Costamagna
 wrote:
> according to [1] there might be no fix.
> 

This may not be a permanent fix, but Debian could take up the "dual-abi"
idea that gcc upstream does with their libstdc++.so.6.

Example:

$ nm -D /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | c++filt | grep
std::locale::name
0009e300 T std::locale::name[abi:cxx11]() const
000b8900 T std::locale::name() const

For reference, the un-beautified symbol names are

0009e300 T _ZNKSt6locale4nameB5cxx11Ev
000b8900 T _ZNKSt6locale4nameEv


The symbol is exported twice, once with the new ABI and once with the
old. If someone™ figured out how to make the gcc compiler do that, boost
(and other libraries') maintainers could adapt those flags when
compiling with gcc, so we don't generate a vendor lock-in.

If we could make those "Dual-ABI compile flags" the default on
gcc-compiled libraries, clang upstream should have enough time
implementing [abi:cxx11] and remain usable in Debian.

- Danny

Bug#791264: marked as done (qwtplot3d: library transition may be needed when GCC 5 is the default)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 22:00:17 +
with message-id 
and subject line Bug#791264: fixed in qwtplot3d 0.2.7+svn191-8
has caused the Debian Bug report #791264,
regarding qwtplot3d: library transition may be needed when GCC 5 is the default
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.)


-- 
791264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qwtplot3d
Version: 0.2.7+svn191-7
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
and dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

What is needed:

 - Rebuild the library using g++/g++-5 from experimental. Note that
   most likely all C++ libraries within the build dependencies need
   a rebuild too. You can find the log for a rebuild in
 https://people.debian.org/~doko/logs/gcc5-20150701/
   Search for "BEGIN GCC CXX11" in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.
 
 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append "v5" to the name of the package
   (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   cont...@bugs.debian.org:
   
 user release.debian@packages.debian.org
 usertag  + transition
 block  by 790756
 reassign  release.debian.org
   
 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
--- End Message ---
--- Begin Message ---
Source: qwtplot3d
Source-Version: 0.2.7+svn191-8

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

Debian distribution maintenance software
pp.
Gudjon I. Gudjonsson  (supplier of updated qwtplot3d package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 02 Sep 2015 07:04:48 +0100
Source: qwtplot3d
Binary: libqwtplot3d-qt4-dev libqwtplot3d-qt4-0v5 libqwtplot3d-doc
Architecture: source all amd64
Version: 0.2.7+svn191-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Gudjon I. Gudjonsson 
Description:
 libqwtplot3d-doc - 3D plotting library based on Qt/OpenGL (documentation)
 libqwtplot3d-qt4-0v5 - 3D plotting library based on Qt4/OpenGL (runtime)
 libqwtplot3d-qt4-dev - 3D plotting library based on Qt4/OpenGL (development)
Closes: 791264
Changes:
 qwtplot3d 

Bug#790324: luakit: Improve security level, dubious features

[Santiago Vila]

Philippe Grégoire  wrote:
> From what I understood from an earlier bug report, these
> changes were made due to not reproducible builds.

No, they are completely unrelated.

I'll explain below.

Mason Larobina wrote:
> Hi Philippe,
> I'm the upstream.
> 
> What is this 'ugh' patch?

The "ugh" patch could be described as an artifact of using git for
development and the "3.0 (quilt)" source format for Debian releases.

When you change some file in the source and do "dpkg-buildpackage",
the package manager detects that there are changes not reflected in
any of the debian/patches/* and automatically allows the maintainer to
create a new patch. By default, this patch contains the latest
changelog entries, which is the reason you might think that *all* the
changes made to the package are related to whatever changelog entries
were added in the last place.


This package is currently orphaned, but I'm going to do a "QA upload"
fixing the https thing and the soup.ssl_strict thing to close this bug.

If there are still issues, please report them in *different* bugs
(or just talk with the author, who happens to be around). Mixing
different issues in a single bug report makes things more difficult to
manage for us.

Thanks.

Processed: user release.debian....@packages.debian.org, usertagging 796925 ...

[Debian Bug Tracking System]

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

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was j...@debian.org).
> usertags 796925 transition
There were no usertags set.
Usertags are now: transition.
> reassign 796925 release.debian.org
Bug #796925 [src:opencolorio] opencolorio: library transition needed with GCC 5 
as default
Bug #797618 [src:opencolorio] opencolorio: transition needed for g++-5 ABIs
Bug reassigned from package 'src:opencolorio' to 'release.debian.org'.
Bug reassigned from package 'src:opencolorio' to 'release.debian.org'.
No longer marked as found in versions opencolorio/1.0.9~dfsg0-3.
No longer marked as found in versions opencolorio/1.0.9~dfsg0-3.
Ignoring request to alter fixed versions of bug #796925 to the same values 
previously set
Ignoring request to alter fixed versions of bug #797618 to the same values 
previously set
> retitle 796925 transition: opencolorio
Bug #796925 [release.debian.org] opencolorio: library transition needed with 
GCC 5 as default
Bug #797618 [release.debian.org] opencolorio: transition needed for g++-5 ABIs
Changed Bug title to 'transition: opencolorio' from 'opencolorio: library 
transition needed with GCC 5 as default'
Changed Bug title to 'transition: opencolorio' from 'opencolorio: transition 
needed for g++-5 ABIs'
> thanks
Stopping processing here.

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

Bug#797940: src:dh-elpa: maintainer address bounces

[Ansgar Burchardt]

Source: dh-elpa
Source-Version: 0.0.5
Severity: serious
X-Debbugs-Cc: David Bremner 

The maintainer address bounces. I guess the list is on
@lists.*alioth*.d.o, not @lists.d.o.

Ansgar

Mail Delivery System  writes:
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   pkg-emacsen-add...@lists.debian.org
> SMTP error from remote mail server after RCPT 
> TO::
> host bendel.debian.org [2001:41b8:202:deb:216:36ff:fe40:4002]:
> 550 5.1.1 :
> Recipient address rejected: User unknown in virtual alias table
>
> -- This is a copy of the message, including all the headers. --
>
[...]
> To: Debian Emacs addons team , David 
> Bremner 
> X-DAK: dak process-upload
> X-Debian: DAK
> X-Debian-Package: dh-elpa
> Precedence: bulk
> Auto-Submitted: auto-generated
> MIME-Version: 1.0
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: 8bit
> Subject: dh-elpa_0.0.5_amd64.changes ACCEPTED into unstable
> Message-Id: 
> Date: Tue, 01 Sep 2015 22:48:40 +
>
>
>
> Accepted:
>
> Format: 1.8
> Date: Tue, 01 Sep 2015 19:09:51 -0300
> Source: dh-elpa
> Binary: dh-elpa
> Architecture: source all
> Version: 0.0.5
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Emacs addons team 
> Changed-By: David Bremner 
> Description:
>  dh-elpa- Debian helper tools for packaging emacs lisp extensions
> Changes:
>  dh-elpa (0.0.5) unstable; urgency=medium
>  .
>* Use debian/.debhelper/elpa for temp files. This allows easier
>  debugging.
>* Add a check for ${elpa_name}-pkg.el in multi-file packages
>* Link all top level files/directories into flavour directory, not
>  just *.el
> Checksums-Sha1:
>  420e8199d3209bf93e9d0638850115225c2f397c 1322 dh-elpa_0.0.5.dsc
>  b9186e0a45e93b7b866be9b1dc35f4e323d7516b 6538 dh-elpa_0.0.5.tar.gz
>  96a54ce03351565dbdf677517dd63a5d3cd4072e 9168 dh-elpa_0.0.5_all.deb
> Checksums-Sha256:
>  7eedff75b9bccfefab070b50c65cee8285407f86b8ac5ac7fe3b595795ffc226 1322 
> dh-elpa_0.0.5.dsc
>  6a271064ef771a37e5294fc8aecdde5c704002e75d452cf15e692f076db2601d 6538 
> dh-elpa_0.0.5.tar.gz
>  15d36252953837d9479b7ce2323e3984732ede8b0ac6eac6b5e87816998b486e 9168 
> dh-elpa_0.0.5_all.deb
> Files:
>  79a210e59db78409cdbad319021e3285 1322 devel optional dh-elpa_0.0.5.dsc
>  a9528cafcfb0db785d409287c12c26e4 6538 devel optional dh-elpa_0.0.5.tar.gz
>  3a823e8fa1341519abb0b30e760e34ce 9168 devel optional dh-elpa_0.0.5_all.deb
>
>
>
> Thank you for your contribution to Debian.

Processed: closing 757134

[Debian Bug Tracking System]

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

> close 757134 0.8.0-13
Bug #757134 [src:gtkmathview] please build using dh-autoreconf and link with -lm
Marked as fixed in versions gtkmathview/0.8.0-13.
Bug #757134 [src:gtkmathview] please build using dh-autoreconf and link with -lm
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#788708: iceweasel: GStreamer causes segmentation fault

[Guillaume Dupuy]

This is still happening as of today ; i however don't have the problem 
with chromium (v44.0.2403.157-1 from sid repository)

Processed: Re: [pkg-fgfs-crew] Bug#797936: flightgear: Crash on startup: symbol lookup error

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #797936 [flightgear] flightgear: Crash on startup: symbol lookup error
Severity set to 'grave' from 'important'
> reassign -1 libsimgearscene3.4.0
Bug #797936 [flightgear] flightgear: Crash on startup: symbol lookup error
Bug reassigned from package 'flightgear' to 'libsimgearscene3.4.0'.
No longer marked as found in versions flightgear/3.4.0-1.
Ignoring request to alter fixed versions of bug #797936 to the same values 
previously set

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

Bug#797863: FTBFS: error: 'class BluezQt::Device' has no member named 'connectDevice'

[Julien Cristau]

Source: bluedevil
Version: 4:5.3.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: stretch sid

Your package no longer builds in sid, see the logs at
https://buildd.debian.org/status/logs.php?pkg=bluedevil=4%3A5.3.2-1%2Bb1=sid

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#797800: lvm2 configure.in, librt.so vs librt.pc

[Peter Rajnoha]

On 09/02/2015 07:35 PM, Andreas Henriksson wrote:
> Hello Alasdair G Kergon.
> 
> I'm mailing you because of an issue I've run into which I think comes
> from your commit:
> https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=3cd644aeb5cac432a92ad50584973a3430168ed6
> 
> On Debian there's librt.so but no librt.pc.
> 

I think librt.pc file is not present at all (at least
not in glibc upstream repo).

I've patched this, the -lrt should be stated under
Libs.private:

https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=fc35b6988d65fe3f11a3f668cd8f01fe3294b562

There's also -lm which is also used, but it was
not mentioned in the devmapper.pc.

-- 
Peter

Bug#797865: libpqxx: ABI transition needed for libstdc++ v5

[Simon McVittie]

Source: libpqxx
Version: 4.0.1+dfsg-3
Severity: serious
Justification: breaks ABI without a package rename
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of libpqxx, std::string appears in the installed headers
in many places, so it seems very likely that a transition is needed.
The transition normally consists of renaming the
affected library packages, adding a v5 suffix (libpqxx-4.0v5).
The SONAME should not be changed when doing this.

If an upgrade to a new upstream SONAME is already planned, and that
SONAME has never been available in Debian compiled with g++-4, then an
alternative way to carry out the transition would be to bump the
SONAME. Please avoid doing this unless the new upstream version
is very low-risk.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the build-dependencies of libpqxx, there do not seem to be
any C++ libraries, so it seems ready to go.

The package might be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html

Bug#797867: libzypp: ABI transition needed for libstdc++ v5

[Simon McVittie]

Source: libzypp
Version: 15.3.0-1
Severity: serious
Justification: breaks ABI without a package rename
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of libzypp, std::string appears in major classes such as
Pathname, so it seems very likely that a transition is needed. The
transition normally consists of renaming the affected library packages,
adding a v5 suffix. The SONAME should not be changed when doing this.
However, libzypp is not packaged according to Policy §8.1 and does
not generate correct dependencies (I'll file a separate bug),
so a versioned Breaks on zypper will probably be needed as well.

If an upgrade to a new upstream SONAME is already planned, and that
SONAME has never been available in Debian compiled with g++-4, then an
alternative way to carry out the transition would be to bump the
SONAME. Please avoid doing this unless the new upstream version
is very low-risk.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the build-dependencies of libzypp, the C++ libraries
are Boost, which has had its rename already (while moving from 1.55
to 1.58), and libproxy, which only has a C ABI so does not need a
rename; so this sub-transition is ready to start.

The package might be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html

Bug#794581: Happened again! Argh!

[Martin Steigerwald]

Hi Dominik, Luca, Borden,

Am Mittwoch, 26. August 2015, 14:00:48 schrieb Luca Ghio:
> On Tue, 25 Aug 2015 18:42:11 -0400 Scott Kitterman  
wrote:
> > You should only have to downgrade breeze.  Today's rebuild of kdecorations
> > should resolve its problems.
> I'm sorry, when I sent my message I hadn't read your message and I hadn't
> noticed the new packages in testing yet.
> > So downgrade breeze to the testing version and upgrade kdecorations to the
> > +b1 version.
> I can confirm that the new packages +b1 work with breeze (testing version).

Can I close this?

In unstable it works. How about testing?

You can also close yourself by writing to "794581-d...@bugs.debian.org" with 
an explaination. By closing transitional bugs like this yourself, you can help 
the Qt/KDE team to progress faster.

Thanks,
-- 
Martin

Bug#797866: libtorrent: ABI transition needed for libstdc++ v5

[Simon McVittie]

Source: libtorrent
Version: 0.13.2-1
Severity: serious
Justification: breaks ABI without a package rename
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of libtorrent, std::string appears in functions that are
explicitly exported, so it seems very likely that a transition is needed.
The transition normally consists of renaming the
affected library packages, adding a v5 suffix (libtorrent14v5).
The SONAME should not be changed when doing this.

If an upgrade to a new upstream SONAME is already planned, and that
SONAME has never been available in Debian compiled with g++-4, then an
alternative way to carry out the transition would be to bump the
SONAME. Please avoid doing this unless the new upstream version
is very low-risk.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the build-dependencies of libtorrent, the C++ libraries
are libcppunit and libsigc++, which have both had their renames
already; so this sub-transition is ready to start.

The package might be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html

Bug#766884: libxml2 broken in sid for months already

[Raphael Hertzog]

Control: severity 766884 important

Hi Aron,

please keep me in copy as I'm not subscribed to
debian-xml-sgml-p...@lists.alioth.debian.org... I just discovered your
reply by chance.

On Mon, 31 Aug 2015, Aron Xu wrote:
> Let's reopen #766884 for tracking, it's not really fixed, but just
> avoided. Unfortunately #781232 is opened. I would like to block this
> version to testing as it's not the proper way of fixing the problem
> (but it is indeed the most straightforward way of avoiding it).

Why don't you want to let this version in testing?

The release team has made it clear that they prefer to have the same
version in unstable and in testing... and the version in unstable is not
worse than the version in testing.

> The proper way of working this bug around would be bisecting and
> patching which is quite time consuming. I haven't yet managed to get
> it done and help is welcomed, but if no one step up I'll do it
> eventually (or cross finger for finding a proper fix, :D).

Someone already did this that in the upstream bug tracker:
https://bugzilla.gnome.org/show_bug.cgi?id=737840

So if you want you can try to revert this commit:
https://git.gnome.org/browse/libxml2/commit/?id=a16eb968075a82ec33b2c1e77db8909a35b44620

But Daniel Veillard made it clear that this commit
was not at fault, it was only making the problem visible:
https://bugzilla.gnome.org/show_bug.cgi?id=737840#c2

So yes, maybe switching to 1.9.2 and reverting this
one would be better until a proper fix is available.

But this bug should not prevent the migration of the package to testing
since the package in sid does not exhibit the problem currently. So
I'm reducing its severity to important in particular since you do not seem
to want to close it until a proper fix is available upstream.

I just added another commit on request of Julien Cristau.  Whatever you
decide, you need to make a new upload so that the "icu" migration can be
completed in unstable.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Processed: Re: Bug#766884: libxml2 broken in sid for months already

[Debian Bug Tracking System]

Processing control commands:

> severity 766884 important
Bug #766884 [libxml2] libxml2: "validity error : ID ... already defined" errors 
with xmllint --noent
Bug #796031 [libxml2] publican: FTBFS: validity:513 in Test_DB5_Book.xml on 
line 11: ID We_Need_Feedback already defined
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'

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

Bug#797217: pgadmin3: Dependency broken

[Christoph Berg]

Re: Zlatko Calusic 2015-09-01 <55e5cd2b.4010...@bitsync.net>
> Christoph, i have the same problem, pgadmin3 currently depends on obsolete
> libwx libraries.
> 
> Forcing the old libraries to install forces too much other software to be
> removed, packages that have been recompiled to use the new libraries.
> 
> Please just recompile the package, new -dev packages already depend on the
> proper v5 libraries.

Hi,

I've uploaded the version previously in experimental to unstable, so
this issue should be fixed. (I had inspected the old dependencies but
couldn't see any incompatibilities, and installing worked for me, but
this gcc5 transition has more wrinkles than I'm overseeing atm...)

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/


signature.asc
Description: Digital signature

Bug#797217: pgadmin3: Dependency broken

[Zlatko Calusic]

On 03.09.2015 10:09, Christoph Berg wrote:

Re: Zlatko Calusic 2015-09-01 <55e5cd2b.4010...@bitsync.net>

Christoph, i have the same problem, pgadmin3 currently depends on obsolete
libwx libraries.

Forcing the old libraries to install forces too much other software to be
removed, packages that have been recompiled to use the new libraries.

Please just recompile the package, new -dev packages already depend on the
proper v5 libraries.


Hi,

I've uploaded the version previously in experimental to unstable, so
this issue should be fixed. (I had inspected the old dependencies but
couldn't see any incompatibilities, and installing worked for me, but
this gcc5 transition has more wrinkles than I'm overseeing atm...)

Christoph



Thank you Christoph. This new version installs and runs just fine.

--
Zlatko

Processed: 1

[Debian Bug Tracking System]

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

> fixed 796989 monit/1:5.14-1
Bug #796989 [monit] monit: Monit 5.9 has a serious umask bug.
Marked as fixed in versions monit/1:5.14-1.
> thanks
Stopping processing here.

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

Bug#791041: marked as done (ganv: library transition may be needed when GCC 5 is the default)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 07:00:16 +
with message-id 
and subject line Bug#791041: fixed in ganv 1.4.2~dfsg0-1.1
has caused the Debian Bug report #791041,
regarding ganv: library transition may be needed when GCC 5 is the default
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.)


-- 
791041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ganv
Version: 1.4.2~dfsg0-1
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
and dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

What is needed:

 - Rebuild the library using g++/g++-5 from experimental. Note that
   most likely all C++ libraries within the build dependencies need
   a rebuild too. You can find the log for a rebuild in
 https://people.debian.org/~doko/logs/gcc5-20150701/
   Search for "BEGIN GCC CXX11" in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.
 
 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append "v5" to the name of the package
   (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   cont...@bugs.debian.org:
   
 user release.debian@packages.debian.org
 usertag  + transition
 block  by 790756
 reassign  release.debian.org
   
 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
--- End Message ---
--- Begin Message ---
Source: ganv
Source-Version: 1.4.2~dfsg0-1.1

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated ganv 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: Mon, 31 Aug 2015 11:35:35 +0100
Source: ganv
Binary: libganv-1-1v5 libganv-dev gir1.2-ganv-1.0
Architecture: amd64 source
Version: 1.4.2~dfsg0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Alessio Treglia 
Changed-By: Simon McVittie 
Closes: 791041
Description: 
 gir1.2-ganv-1.0 - GObject Introspection data for Ganv
 libganv-1-1v5 - canvas widget for graph-based interfaces
 libganv-dev - canvas widget for graph-based interfaces (development files)
Changes:
 ganv (1.4.2~dfsg0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload for libstdc++ transition (Closes: #791041)
 .
   [ Steve Langasek ]
   * Rename 

Bug#797620: marked as done (openimageio: transition needed for g++-5 ABIs)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 07:00:24 +
with message-id 
and subject line Bug#797620: fixed in openimageio 1.5.18~dfsg0-1
has caused the Debian Bug report #797620,
regarding openimageio: transition needed for g++-5 ABIs
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.)


-- 
797620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openimageio
Version: 1.5.17~dfsg0-1
Severity: serious
Justification: breaks reverse-dependencies

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of openimageio, std::string appears in header files that
get installed, so it seems very likely that a transition is needed.
The transition consists of renaming the library package, adding a
v5 suffix. A patch is available in Ubuntu,
.
It also has unrelated Ubuntu changes, which is why I'm not tagging this
"patch", but you might want to consider those changes as well.
 will need to be fixed at the same time,
and is also part of the Ubuntu patch.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

In the case of openimageio:

* there is a circular build-dep with opencolorio which will need some
  care (Ubuntu temporarily disabled openimageio support in opencolorio,
  which seems a reasonable solution)
* boost, opencv, openexr already started their transitions
* Qt does not need a rename
* I think the rest are C and so do not need renames

so I think these two packages are ready to go.

The package is likely to be NMU'd in the near future if there is no
maintainer response, with a patch based on the one in Ubuntu. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html
--- End Message ---
--- Begin Message ---
Source: openimageio
Source-Version: 1.5.18~dfsg0-1

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

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated openimageio package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 01 Sep 2015 13:45:16 +0200
Source: openimageio
Binary: libopenimageio1.5v5 libopenimageio-dev openimageio-tools
Architecture: source amd64
Version: 1.5.18~dfsg0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Matteo F. Vescovi 
Description:
 libopenimageio-dev - Library for reading and writing images - development
 libopenimageio1.5v5 - Library for reading and writing images - runtime
 openimageio-tools - Library for reading and writing images - command line tools
Closes: 794702 797620
Changes:
 openimageio (1.5.18~dfsg0-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/: gcc-4.9/g++-4.9 support dropped (Closes: #794702)
   * 

Bug#794702: marked as done (openimageio explicitly built using g++-4.9)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 07:00:24 +
with message-id 
and subject line Bug#794702: fixed in openimageio 1.5.18~dfsg0-1
has caused the Debian Bug report #794702,
regarding openimageio explicitly built using g++-4.9
to be marked as done.

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

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


-- 
794702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openimageio
Version: 1.5.17~dfsg0-1
Severity: serious
Tags: sid stretch

openimageio explicitly built using g++-4.9. You must use the default GCC now,
4.9 is no option anymore. See https://wiki.debian.org/GCC5
--- End Message ---
--- Begin Message ---
Source: openimageio
Source-Version: 1.5.18~dfsg0-1

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

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated openimageio package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 01 Sep 2015 13:45:16 +0200
Source: openimageio
Binary: libopenimageio1.5v5 libopenimageio-dev openimageio-tools
Architecture: source amd64
Version: 1.5.18~dfsg0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Matteo F. Vescovi 
Description:
 libopenimageio-dev - Library for reading and writing images - development
 libopenimageio1.5v5 - Library for reading and writing images - runtime
 openimageio-tools - Library for reading and writing images - command line tools
Closes: 794702 797620
Changes:
 openimageio (1.5.18~dfsg0-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/: gcc-4.9/g++-4.9 support dropped (Closes: #794702)
   * debian/: fix g++-5 ABI transition issue (Closes: #797620)
Checksums-Sha1:
 af0b47b48c320a3ea8f75a3bf8062f9af99ad3a0 2666 openimageio_1.5.18~dfsg0-1.dsc
 dbb95656ead5860d550ce26c30f7c8e21f274fed 19250125 
openimageio_1.5.18~dfsg0.orig.tar.gz
 2abc76a9ac5948573c03cac9744e191640eba3fd 17524 
openimageio_1.5.18~dfsg0-1.debian.tar.xz
 3719c986afe91cea613f686c3e8634d816b9f4d5 1676664 
libopenimageio-dev_1.5.18~dfsg0-1_amd64.deb
 c1bbb3f3a08762195e44e38d9792ba9ef0d78265 1529816 
libopenimageio1.5v5_1.5.18~dfsg0-1_amd64.deb
 65601eff1e536d11742d7d816c4bcb08a2433b70 397390 
openimageio-tools_1.5.18~dfsg0-1_amd64.deb
Checksums-Sha256:
 4318e178507830ef4d1860bfe90c5cc3e2f3b1a9dcb9dc3d6622d878a6cfbc90 2666 
openimageio_1.5.18~dfsg0-1.dsc
 8dca6af8c44860d947a840db4bc7b544747fe91b0503a2d37b927eae5445679d 19250125 
openimageio_1.5.18~dfsg0.orig.tar.gz
 254ac9444e47720705b5da8bd0b4deaa739c39300adbd375ab58de4b024beef8 17524 
openimageio_1.5.18~dfsg0-1.debian.tar.xz
 c541eaf4ab1e7e490024570ffb064c8a57df097c2730d8caad6092959ec993c9 1676664 
libopenimageio-dev_1.5.18~dfsg0-1_amd64.deb
 c0ff80763aae2926f0c78ad4d2b80762c9954ea91831c48a4c48ac1e059cd29d 1529816 
libopenimageio1.5v5_1.5.18~dfsg0-1_amd64.deb
 9676a53e136b0f64a45e6570eed7b64a362c7b6c3fa7c7716840dceab54f8411 397390 
openimageio-tools_1.5.18~dfsg0-1_amd64.deb
Files:
 07151c8f2b66cba8d2dedd34277c675d 2666 libs optional 
openimageio_1.5.18~dfsg0-1.dsc
 4358652df844fec989f3d7118fcbc886 19250125 libs optional 
openimageio_1.5.18~dfsg0.orig.tar.gz
 9fe83216996e607a4a62f7eeed6994e4 17524 libs optional 
openimageio_1.5.18~dfsg0-1.debian.tar.xz
 47d61fe64b64171eeb763d795149481e 1676664 libdevel optional 
libopenimageio-dev_1.5.18~dfsg0-1_amd64.deb
 8fbf8dcedccf80aa57e2f894b85b6787 1529816 libs optional 
libopenimageio1.5v5_1.5.18~dfsg0-1_amd64.deb
 7fd5b1040df119087f733a180f0741f7 397390 graphics optional 
openimageio-tools_1.5.18~dfsg0-1_amd64.deb

-BEGIN PGP SIGNATURE-
Comment: Debian powered!

iQJ8BAEBCgBmBQJV5uB+XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGM0REMDlGOERBODdEMURGNTA0NkM5OUIw
NjEyRjQ5NDRFQ0RDRDVBAAoJEAYS9JROzc1aDY8QAKY0jzv/63ci2+Rq4NQiXwqj
4fNsWWmng5NNW7ATtYOtzz8lCNvCY8bri3WrncLTqo4AT7Qa3yf8pkwEgrEFRWqB

Bug#797855: spice-gtk:spice-common/common/generated_* not reliably generated from source

[Chris Lamb]

Hi Liang,

> I cannot reproduce this error on my build environment. it looks this
> is caused by lack dependency on python-six module.

Not completely. Please re-read my initial bug report:

> > Depending on the timezone of the build system, the package may FTBFS as
> > the `spice-common/python_modules/codegen.py` tool used to regenerate
> > these files requires python-six which is not included in the
> > Build-Depends.
> > 
> > (ie. I don't believe simply including python-six as a build-dependency
> > entirely resolves the issue)

If any of that is unclear, please let me know and I will try and
rephrase it.

Just as a summary, adding python-six is not complete fix - your package
would still not being built from the generated sources.


Regards,

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

Bug#797869: libzypp: shared library does not generate correct dependencies

[Simon McVittie]

Source: libzypp
Version: 15.3.0-1
Severity: serious
Justification: Policy 8.1

The libzypp binary package contains a public shared library
(libzypp.so.1503), and zypper depends on it.

Policy §8.1 says:

> The run-time shared library must be placed in a package whose name
> changes whenever the SONAME of the shared library changes.

In this case, the shared library package should be libzypp1503,
and zypper should depend on that. I realise this is going to
involve a lot of going through the NEW queue, but that's what
happens if a library doesn't have a stable ABI.

In addition, libzypp does not generate correct dependencies
via its shlibs or symbol file: zypper depends on "libzypp",
with no version specified. In particular, there is nothing to stop a
user from installing libzypp/jessie (contains libzypp.so.1429) in
conjunction with zypper/stretch (requires libzypp.so.1503), or vice
versa, which will cause the dynamic linker to fail before zypper
has started. The requirement I quoted is there precisely so that
this sort of thing does not happen.

If you are not going to follow ABI-based naming (libzypp1503),
then you need some other solution to make the broken situations
impossible, for example making the shlibs/symbols generate a
dependency on "libzypp (>= 15.3), libzypp (<< 15.4)", and adding
Breaks for older versions of zypper that did not pick up this
dependency. I expect that the easiest way will be to use the
ABI-based naming as intended, instead.

For the C++ transition (#797867) an additional constraint is
that the version of libzypp that has been compiled with g++-5
needs a Breaks on versions of zypper that may have been compiled
with g++-4.

S

Processed: severity #796488 critical

[Debian Bug Tracking System]

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

> severity  #796488 critical
Bug #796488 [pyzor] pyzor: Missing binary pyzor in 0.5.0-3
Severity set to 'critical' from 'important'
>
End of message, stopping processing here.

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

Processed: lazarus: armel and armhf builds stall

[Debian Bug Tracking System]

Processing control commands:

> tags 793991 + patch
Bug #793991 [src:lazarus] lazarus: armel and armhf builds stall
Added tag(s) patch.

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

Bug#793991: lazarus: armel and armhf builds stall

[Graham Inggs]

Control: tags 793991 + patch

Hi

The attached patch works around the problem by disabling '-z relro'
for armel and armhf builds.
I have tested it on armhf and amd64.

Regards
Graham


disable-relro-on-ARM.debdiff
Description: Binary data

Bug#796854: marked as done (openbabel: transition needed for g++-5 ABIs)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 10:00:25 +
with message-id 
and subject line Bug#796854: fixed in openbabel 2.3.2+dfsg-2.2
has caused the Debian Bug report #796854,
regarding openbabel: transition needed for g++-5 ABIs
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.)


-- 
796854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openbabel
Version: 2.3.2+dfsg-2.1
Severity: serious
Justification: breaks reverse-dependencies
Tags: patch

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of openbabel, std::string appears in header files that
get installed, so it seems very likely that a transition is needed.
The transition consists of renaming the library package
containing libopenbabel.so.4 from "libopenbabel4" to "libopenbabel4v5".
A patch is available in Ubuntu,
.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the libraries on which openbabel depends
have started their transitions if required, openbabel should do the same,
closing this bug; the release team will deal with binNMUs as needed.

In the case of openbabel, libwxgtk3.0-dev has already started its
transition, and libeigen3-dev appears to be unaffected, so openbabel
is ready for its rename now.

The package might be NMU'd in the near future, with a patch very similar
to the one in Ubuntu, if its maintainers do not respond; the release
team have declared a 2 day NMU delay[2] for packages involved in the
libstdc++ transition, in order to get unstable back to a usable state
in a finite time.

S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html
--- End Message ---
--- Begin Message ---
Source: openbabel
Source-Version: 2.3.2+dfsg-2.2

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated openbabel 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: Mon, 31 Aug 2015 22:18:57 +0100
Source: openbabel
Binary: openbabel openbabel-gui libopenbabel-dev libopenbabel4v5 
libopenbabel-doc python-openbabel libchemistry-openbabel-perl openbabel-dbg
Architecture: all amd64 source
Version: 2.3.2+dfsg-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Simon McVittie 
Closes: 796854
Description: 
 libchemistry-openbabel-perl - Chemical toolbox library (perl bindings)
 libopenbabel4v5 - Chemical toolbox library
 libopenbabel-dev - Chemical toolbox library (development files)
 libopenbabel-doc - Chemical toolbox library (documentation)
 openbabel  - Chemical toolbox utilities (cli)
 openbabel-dbg - Chemical toolbox library (debugging symbols)
 openbabel-gui - Chemical toolbox utilities (graphical user interface)
 python-openbabel - Chemical toolbox library (python bindings)
Changes:
 openbabel (2.3.2+dfsg-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply Ubuntu patch for the libstdc++ transition (Closes: #796854)
 .
   [ Matthias Klose ]
   * Rename libopenbabel4 to libopenbabel4v5, follow-up transition
 to the libstdc++6 transition.
   * Add 

Bug#797285: marked as done (tango ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 10:00:32 +
with message-id 
and subject line Bug#797285: fixed in tango 8.1.2c+dfsg-6
has caused the Debian Bug report #797285,
regarding tango ftbfs in unstable
to be marked as done.

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

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


-- 
797285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tango
Version: 8.1.2c+dfsg-5
Severity: serious
Tags: sid stretch

tango ftbfs in unstable,

libtool: link: g++ -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -std=c++11 -D_REENTRANT -DOMNI_UNLOADABLE_STUBS -Wl,-z
-Wl,relro -o .libs/notifd2db notifd2db.o  -L../../lib/cpp/server
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so
-L../../lib/cpp/log4tango/src
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/log4tango/src/.libs/liblog4tango.so
-lzmq -ldl -L/usr/lib -lomniORB4 -lomniDynamic4 -lCOS4 -lnsl -lomnithread 
-lpthread
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2const::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2const::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2const::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2const::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2const::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2const::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2const::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2const::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2const::str'
collect2: error: ld returned 1 exit status
Makefile:472: recipe for target 'notifd2db' failed
make[4]: *** [notifd2db] Error 1
make[4]: Leaving directory
'/scratch/packages/tmp/tango-8.1.2c+dfsg/build/utils/notifd2db'
Makefile:432: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/scratch/packages/tmp/tango-8.1.2c+dfsg/build/utils'
Makefile:524: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/scratch/packages/tmp/tango-8.1.2c+dfsg/build'
Makefile:454: recipe for target 'all' failed
make[1]: *** [all] Error 2
--- End Message ---
--- Begin Message ---
Source: tango
Source-Version: 8.1.2c+dfsg-6

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated tango package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 02 Sep 2015 18:34:07 +0200
Source: tango
Binary: liblog4tango5v5 liblog4tango5-dev liblog4tango5v5-dbg liblog4tango5-doc 
libtango8v5 libtango8-dev libtango8v5-dbg libtango8-doc libtango-tools 
tango-common tango-db tango-db-dbg tango-starter tango-starter-dbg 
tango-accesscontrol tango-accesscontrol-dbg tango-test tango-test-dbg
Architecture: source i386 all
Version: 8.1.2c+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Description:
 liblog4tango5-dev - logging for TANGO - development library
 liblog4tango5-doc - logging for TANGO - documentation
 liblog4tango5v5 - logging for TANGO - shared library
 liblog4tango5v5-dbg - logging for TANGO - debug library
 libtango-tools - TANGO 

Processed: tagging 796437

[Debian Bug Tracking System]

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

> tags 796437 + pending
Bug #796437 [src:jython] jython: FTBFS: NoClassDefFoundError: 
org/stringtemplate/v4/STGroup
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: severity of 791319 is serious

[Debian Bug Tracking System]

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

> # causes mumble ftbfs
> severity 791319 serious
Bug #791319 [src:zeroc-ice] zeroc-ice: library transition is needed when GCC 5 
is the
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#795814: FTBFS: boost/math/tools/test.hpp: No such file or directory

[Manuel A. Fernandez Montecelo]

2015-09-03 22:27 GMT+01:00 Jonathan Wiltshire :
> On Mon, Aug 24, 2015 at 09:30:25AM +0100, Manuel A. Fernandez Montecelo wrote:
>> So it will need a bit more investigation and possibly to speak with
>> upstream about it -- I think that the fix will need a few days (at
>> least) to arrive.
>
> As there is no prospect of a fix for now and k3d is causing a blockage on
> several interrelated transitions, I have temporarily removed it from
> testing.

Goody, thanks.  I had already told jcristau on IRC to do so if it
caused problems.

I don't know when I will be able to find a solution, so good that you
removed the +pending.

-- 
Manuel A. Fernandez Montecelo 

Bug#791740: marked as done (FTBFS with GCC 5: changes to symbols file)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 22:24:43 +
with message-id 
and subject line Bug#791740: fixed in openvdb 3.0.0-3.1
has caused the Debian Bug report #791740,
regarding FTBFS with GCC 5: changes to symbols file
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.)


-- 
791740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openvdb
Version: 3.0.0-3
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

This package fails to build with GCC 5:

sbuild (Debian sbuild) 0.64.1 (13 Oct 2013) on m400-c4n1.hlinux.usa.hp.com
...
make[1]: Leaving directory '/«PKGBUILDDIR»'
   debian/rules override_dh_installdocs
make[1]: Entering directory '/«PKGBUILDDIR»'
cp -f LICENSE MPL
dh_installdocs -A MPL
make[1]: Leaving directory '/«PKGBUILDDIR»'
   dh_installchangelogs -O--parallel
   dh_installman -O--parallel
   dh_python2 -O--parallel
I: dh_python2 fs:298: renaming pyopenvdb.so to pyopenvdb.aarch64-linux-gnu.so
W: dh_python2 dh_python2:67: public extension linked with libpython2.7: 
pyopenvdb.aarch64-linux-gnu.so
   dh_perl -O--parallel
   dh_link -O--parallel
   dh_compress -O--parallel
   dh_fixperms -O--parallel
   dh_strip -O--parallel
   dh_makeshlibs -O--parallel
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libopenvdb3.0/DEBIAN/symbols doesn't match 
completely debian/libopenvdb3.0.symbols
--- debian/libopenvdb3.0.symbols (libopenvdb3.0_3.0.0-3_arm64)
+++ dpkg-gensymbolsbq0mx4   2015-07-01 01:56:15.31389 +
@@ -6,7 +6,7 @@
  (regex|c++)N7openvdb4v3_02io4File15setCopyMaxBytesE[y|m]@Base 3.0.0
  (regex|c++)N7openvdb4v3_04util10printBytesERSo[y|m]RKSsS4_bii@Base 3.0.0
  (regex|c++)N7openvdb4v3_04util11printNumberERSo[y|m]RKSsS4_bii@Base 3.0.0
- 
(regex|c++)NSt22__uninitialized_fill_nILb0EE15__uninit_fill_nIPN5boost2io6detail11format_itemIcSt11char_traitsIcESaIcEEE[j|m]S9_EEvT_T0_RKT1_@Base
 3.0.0
+#MISSING: 3.0.0-3# 
(regex|c++)NSt22__uninitialized_fill_nILb0EE15__uninit_fill_nIPN5boost2io6detail11format_itemIcSt11char_traitsIcESaIcEEE[j|m]S9_EEvT_T0_RKT1_@Base
 3.0.0
  
(regex|c++)NSt6vectorIN7openvdb4v3_02io14GridDescriptorESaIS3_EE7reserveE[j|m]@Base
 3.0.0
  (regex|c++)NSt6vectorIbSaIbEE14_M_fill_insertESt13_Bit_iterator[j|m]b@Base 
3.0.0
  _ZN5boost12bad_any_castD0Ev@Base 3.0.0
@@ -133,7 +133,7 @@
  _ZN7openvdb4v3_02io5Queue14clearNotifiersEv@Base 3.0.0
  _ZN7openvdb4v3_02io5Queue14removeNotifierEj@Base 3.0.0
  _ZN7openvdb4v3_02io5Queue4Impl25setStatusWithNotificationEjNS2_6StatusE@Base 
3.0.0
- (arch=!ppc64el !armhf 
!ppc64)_ZN7openvdb4v3_02io5Queue4Impl9setStatusEjNS2_6StatusE@Base 3.0.0
+#MISSING: 3.0.0-3# (arch=!ppc64el !armhf 
!ppc64)_ZN7openvdb4v3_02io5Queue4Impl9setStatusEjNS2_6StatusE@Base 3.0.0
  
_ZN7openvdb4v3_02io5Queue9writeGridEN5boost10shared_ptrIKNS0_8GridBaseEEERKNS1_7ArchiveERKNS0_7MetaMapE@Base
 3.0.0
  _ZN7openvdb4v3_02io5QueueC1Ej@Base 3.0.0
  _ZN7openvdb4v3_02io5QueueC2Ej@Base 3.0.0
@@ -178,11 +178,11 @@
  _ZN7openvdb4v3_02io8TempFileD2Ev@Base 3.0.0
  _ZN7openvdb4v3_04math10UnitaryMap4readERSi@Base 3.0.0
  _ZN7openvdb4v3_04math10UnitaryMap6createEv@Base 3.0.0
- (arch=armhf)_ZN7openvdb4v3_04math10UnitaryMapC1ENS1_4AxisEd@Base 3.0.0
+ _ZN7openvdb4v3_04math10UnitaryMapC1ENS1_4AxisEd@Base 3.0.0
  _ZN7openvdb4v3_04math10UnitaryMapC1ERKNS1_4Mat3IdEE@Base 3.0.0
  _ZN7openvdb4v3_04math10UnitaryMapC1ERKNS1_4Mat4IdEE@Base 3.0.0
  _ZN7openvdb4v3_04math10UnitaryMapC1ERKS2_S4_@Base 3.0.0
- (arch=armhf)_ZN7openvdb4v3_04math10UnitaryMapC2ENS1_4AxisEd@Base 3.0.0
+ _ZN7openvdb4v3_04math10UnitaryMapC2ENS1_4AxisEd@Base 3.0.0
  _ZN7openvdb4v3_04math10UnitaryMapC2ERKNS1_4Mat3IdEE@Base 3.0.0
  _ZN7openvdb4v3_04math10UnitaryMapC2ERKNS1_4Mat4IdEE@Base 3.0.0
  _ZN7openvdb4v3_04math10UnitaryMapC2ERKS2_S4_@Base 3.0.0
@@ -306,6 +306,7 @@
  _ZN7openvdb4v3_07MetaMapaSERKS1_@Base 3.0.0
  _ZN7openvdb4v3_08GridBase10createGridERKSs@Base 3.0.0
  _ZN7openvdb4v3_08GridBase10setCreatorERKSs@Base 3.0.0
+ _ZN7openvdb4v3_08GridBase11baseTreePtrEv@Base 3.0.0-3
  _ZN7openvdb4v3_08GridBase12isRegisteredERKSs@Base 3.0.0
  
_ZN7openvdb4v3_08GridBase12registerGridERKSsPFN5boost10shared_ptrIS1_EEvE@Base 
3.0.0
  _ZN7openvdb4v3_08GridBase12setGridClassENS0_9GridClassE@Base 3.0.0
@@ -338,7 +339,11 @@
  _ZN7openvdb4v3_08GridBase7setNameERKSs@Base 3.0.0
  

Bug#787084: marked as done (error: 'tbb::internal::atomic_impl::my_storage' has incomplete type)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 22:24:43 +
with message-id 
and subject line Bug#787084: fixed in openvdb 3.0.0-3.1
has caused the Debian Bug report #787084,
regarding error: 'tbb::internal::atomic_impl::my_storage' has incomplete type
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.)


-- 
787084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openvdb
Version: 3.0.0-1
Severity: serious
Justification: FTBFS

the package openvdb FTBFS on powerpc with the following error:

g++ -c -DOPENVDB_PRIVATE -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -D_FORTIFY_SOURCE=2 -fvisibility=hidden
-pthread -g -I . -I .. -isystem /usr/include -isystem
/usr/include/OpenEXR -isystem /usr/include -isystem /usr/include
-DOPENVDB_USE_LOG4CPLUS -DOPENVDB_USE_GLFW_3 -fPIC -o
io/GridDescriptor.o io/GridDescriptor.cc
In file included from ./openvdb/math/QuantizedUnitVec.h:37:0,
 from ./openvdb/math/Hermite.h:36,
 from ./openvdb/Types.h:46,
 from ./openvdb/Grid.h:40,
 from io/Archive.h:42,
 from io/Archive.cc:31:
/usr/include/tbb/atomic.h: In instantiation of 'struct
tbb::internal::atomic_impl':
/usr/include/tbb/atomic.h:413:8:   required from 'struct
tbb::atomic'
io/Archive.cc:434:34:   required from here
/usr/include/tbb/atomic.h:228:34: error:
'tbb::internal::atomic_impl::my_storage' has incomplete type
 aligned_storage my_storage;
  ^
/usr/include/tbb/atomic.h:101:8: error: declaration of 'struct
tbb::internal::aligned_storage'
 struct aligned_storage;
^
/usr/include/tbb/atomic.h: In instantiation of 'union
tbb::internal::atomic_impl::converter':
/usr/include/tbb/atomic.h:242:51:   required by substitution of
'template static typename
tbb::internal::atomic_impl::converter::bits_type
tbb::internal::atomic_impl::to_bits(value_t) [with value_t = long
long unsigned int]'
/usr/include/tbb/atomic.h:334:80:   required from
'tbb::internal::atomic_impl::value_type
tbb::internal::atomic_impl::store_with_release(tbb::internal::atomic_impl::value_type)
[with T = long long unsigned int;
tbb::internal::atomic_impl::value_type = long long unsigned int]'
/usr/include/tbb/atomic.h:420:44:   required from 'T
tbb::atomic::operator=(T) [with T = long long unsigned int]'
io/Archive.cc:376:24:   required from here
/usr/include/tbb/atomic.h:234:63: error: invalid use of incomplete
type 'struct tbb::internal::atomic_rep<8u>'
 typedef typename atomic_rep::word bits_type;
   ^
/usr/include/tbb/atomic.h:74:8: error: declaration of 'struct
tbb::internal::atomic_rep<8u>'
 struct atomic_rep;   // Primary template declared, but never defined.
^
In file included from ./openvdb/math/QuantizedUnitVec.h:37:0,
 from ./openvdb/math/Hermite.h:36,
 from ./openvdb/Types.h:46,
 from ./openvdb/Grid.h:40,
 from io/Archive.h:42,
 from io/Archive.cc:31:
/usr/include/tbb/atomic.h: In instantiation of
'tbb::internal::atomic_impl::value_type
tbb::internal::atomic_impl::store_with_release(tbb::internal::atomic_impl::value_type)
[with T = long long unsigned int;
tbb::internal::atomic_impl::value_type = long long unsigned int]':
/usr/include/tbb/atomic.h:420:44:   required from 'T
tbb::atomic::operator=(T) [with T = long long unsigned int]'
io/Archive.cc:376:24:   required from here
/usr/include/tbb/atomic.h:334:80: error: no matching function for call
to 'tbb::internal::atomic_impl::to_bits(tbb::internal::atomic_impl::value_type&)'
 __TBB_store_with_release( to_bits_ref(my_storage.my_value),
to_bits(rhs) );

 ^
/usr/include/tbb/atomic.h:334:80: note: candidate is:
In file included from ./openvdb/math/QuantizedUnitVec.h:37:0,
 from ./openvdb/math/Hermite.h:36,
 from ./openvdb/Types.h:46,
 from ./openvdb/Grid.h:40,
 from io/Archive.h:42,
 from io/Archive.cc:31:
/usr/include/tbb/atomic.h:242:51: note: template static
typename tbb::internal::atomic_impl::converter::bits_type
tbb::internal::atomic_impl::to_bits(value_t) [with value_t =
value_t; T = long long unsigned int]
 static typename converter::bits_type to_bits(value_t value){
   ^
/usr/include/tbb/atomic.h:242:51: note:   

Bug#790643: marked as done (FTBFS: Could NOT find Event (missing: Event_LIBRARIES))

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 22:50:55 +
with message-id 
and subject line Bug#797957: Removed package(s) from unstable
has caused the Debian Bug report #790643,
regarding FTBFS: Could NOT find Event (missing: Event_LIBRARIES)
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.)


-- 
790643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: museek+
Version: 1:0.2+svn20100315.r1208-3

museek+ fails to build from source:

> sbuild (Debian sbuild) 0.64.1 (13 Oct 2013) on m400-c4n1.hlinux.usa.hp.com
...
> -- Performing Test DIR_SCANDIR_H
> -- Performing Test DIR_SCANDIR_H - Success
> CMake Error at 
> /usr/share/cmake-3.2/Modules/FindPackageHandleStandardArgs.cmake:138 
> (message):
>   Could NOT find Event (missing: Event_LIBRARIES)
> Call Stack (most recent call first):
>   /usr/share/cmake-3.2/Modules/FindPackageHandleStandardArgs.cmake:374 
> (_FPHSA_FAILURE_MESSAGE)
>   cmake/FindEvent.cmake:22 (find_package_handle_standard_args)
>   NewNet/CMakeLists.txt:4 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also 
> "/build/museek+-1MshrC/museek+-0.2+svn20100315.r1208/CMakeFiles/CMakeOutput.log".
> See also 
> "/build/museek+-1MshrC/museek+-0.2+svn20100315.r1208/CMakeFiles/CMakeError.log".
> make: *** [configure-stamp] Error 1

-- 
Martin Michlmayr
Linux for HP Helion OpenStack, Hewlett-Packard
--- End Message ---
--- Begin Message ---
Version: 1:0.2+svn20100315.r1208-3+rm

Dear submitter,

as the package museek+ 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/797957

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#797863: closing 797863

[Scott Kitterman]

close 797863 4:5.4.0-1
thanks

Processed: closing 797863

[Debian Bug Tracking System]

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

> close 797863 4:5.4.0-1
Bug #797863 [src:bluedevil] FTBFS: error: 'class BluezQt::Device' has no member 
named 'connectDevice'
Marked as fixed in versions bluedevil/4:5.4.0-1.
Bug #797863 [src:bluedevil] FTBFS: error: 'class BluezQt::Device' has no member 
named 'connectDevice'
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#797937: marked as done (src:company-mode: maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 22:20:00 +
with message-id 
and subject line Bug#797937: fixed in company-mode 0.8.12-2
has caused the Debian Bug report #797937,
regarding src:company-mode: maintainer address bounces
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.)


-- 
797937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: company-mode
Source-Version: 0.8.12-1
Severity: serious
X-Debbugs-Cc: David Bremner 

The maintainer address bounces. I guess the mailing list is
@lists.*alioth*.d.o, not @lists.d.o

Ansgar

Mail Delivery System  writes:
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   pkg-emacsen-add...@lists.debian.org
> SMTP error from remote mail server after RCPT 
> TO::
> host bendel.debian.org [2001:41b8:202:deb:216:36ff:fe40:4002]:
> 550 5.1.1 :
> Recipient address rejected: User unknown in virtual alias table
>
> -- This is a copy of the message, including all the headers. --
>
> Return-path: 
[...]
> To: Debian Emacs addons team , David 
> Bremner 
> X-DAK: dak process-policy
> X-Debian: DAK
> X-Debian-Package: company-mode
> Precedence: bulk
> Auto-Submitted: auto-generated
> MIME-Version: 1.0
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: 8bit
> Subject: company-mode_0.8.12-1_amd64.changes ACCEPTED into unstable, unstable
> Message-Id: 
> Date: Wed, 02 Sep 2015 11:00:09 +
>
>
>
> Accepted:
>
> Format: 1.8
> Date: Fri, 21 Aug 2015 08:49:22 +0200
> Source: company-mode
> Binary: elpa-company
> Architecture: source all
> Version: 0.8.12-1
> Distribution: unstable
> Urgency: low
> Maintainer: Debian Emacs addons team 
> Changed-By: David Bremner 
> Description:
>  elpa-company - Modular in-buffer completion framework for Emacs
> Changes:
>  company-mode (0.8.12-1) unstable; urgency=low
>  .
>* Initial release
> Checksums-Sha1:
>  f0bd5eb142b188af633e25977e8d2db32957a3f5 1786 company-mode_0.8.12-1.dsc
>  0860d609f9104d44cc7cb9eb77483d9e2ad039d7 70379 
> company-mode_0.8.12.orig.tar.gz
>  feb789ffdf148afc174bffd3233466d50ecf07cb 2124 
> company-mode_0.8.12-1.debian.tar.xz
>  c7b280175261cc9e6b926c227d962044e4032152 59064 elpa-company_0.8.12-1_all.deb
> Checksums-Sha256:
>  f2505da463ec877e39e79000bcea4074205707b5fa4a9d5ce05f8b9f08371ea1 1786 
> company-mode_0.8.12-1.dsc
>  67937eda92a617f29091874b00aed04b4b48e8f18accf7bcb56ec64287f3d07d 70379 
> company-mode_0.8.12.orig.tar.gz
>  9e2864dd3165d60550d62fe4cbdb44eb51f2a41b2ffe77d3f1e79160df60 2124 
> company-mode_0.8.12-1.debian.tar.xz
>  d9fb689cb40f74cc494e3b3bf5cd16310dfddd9acd5470fcdefb64d18b2866b0 59064 
> elpa-company_0.8.12-1_all.deb
> Files:
>  445341b13c4df78b91f46edc555448c0 1786 lisp optional company-mode_0.8.12-1.dsc
>  2b4a286d666ca0e00c62b94aa52e7984 70379 lisp optional 
> company-mode_0.8.12.orig.tar.gz
>  4d8f36367727501b8f14bc2bb36a9f76 2124 lisp optional 
> company-mode_0.8.12-1.debian.tar.xz
>  b65e72310ee229009eb84f7d3c287f18 59064 lisp optional 
> elpa-company_0.8.12-1_all.deb
>
>
>
> Thank you for your contribution to Debian.
--- End Message ---
--- Begin Message ---
Source: company-mode
Source-Version: 0.8.12-2

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

Debian distribution maintenance software
pp.
David Bremner  (supplier of updated company-mode 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, 03 Sep 2015 18:53:25 -0300
Source: company-mode
Binary: 

Bug#797959: likwid: FTBFS: unconditional amd64 assembly

[Aaron M. Ucko]

Source: likwid
Version: 3.1.3+dfsg-1
Severity: serious
Justification: fails to build from source

Builds of likwid for non-amd64 processors (even i386) fail due to the
unconditional use of amd64 assembly, as detailed at

https://buildd.debian.org/status/logs.php?pkg=likwid=3.1.3%2Bdfsg1-1

If it is infeasible to add support for other CPU types, please
consider setting Architecture: accordingly in debian/control.

Thanks!

Bug#797940: marked as done (src:dh-elpa: maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 22:20:05 +
with message-id 
and subject line Bug#797940: fixed in dh-elpa 0.0.6
has caused the Debian Bug report #797940,
regarding src:dh-elpa: maintainer address bounces
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.)


-- 
797940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dh-elpa
Source-Version: 0.0.5
Severity: serious
X-Debbugs-Cc: David Bremner 

The maintainer address bounces. I guess the list is on
@lists.*alioth*.d.o, not @lists.d.o.

Ansgar

Mail Delivery System  writes:
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   pkg-emacsen-add...@lists.debian.org
> SMTP error from remote mail server after RCPT 
> TO::
> host bendel.debian.org [2001:41b8:202:deb:216:36ff:fe40:4002]:
> 550 5.1.1 :
> Recipient address rejected: User unknown in virtual alias table
>
> -- This is a copy of the message, including all the headers. --
>
[...]
> To: Debian Emacs addons team , David 
> Bremner 
> X-DAK: dak process-upload
> X-Debian: DAK
> X-Debian-Package: dh-elpa
> Precedence: bulk
> Auto-Submitted: auto-generated
> MIME-Version: 1.0
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: 8bit
> Subject: dh-elpa_0.0.5_amd64.changes ACCEPTED into unstable
> Message-Id: 
> Date: Tue, 01 Sep 2015 22:48:40 +
>
>
>
> Accepted:
>
> Format: 1.8
> Date: Tue, 01 Sep 2015 19:09:51 -0300
> Source: dh-elpa
> Binary: dh-elpa
> Architecture: source all
> Version: 0.0.5
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Emacs addons team 
> Changed-By: David Bremner 
> Description:
>  dh-elpa- Debian helper tools for packaging emacs lisp extensions
> Changes:
>  dh-elpa (0.0.5) unstable; urgency=medium
>  .
>* Use debian/.debhelper/elpa for temp files. This allows easier
>  debugging.
>* Add a check for ${elpa_name}-pkg.el in multi-file packages
>* Link all top level files/directories into flavour directory, not
>  just *.el
> Checksums-Sha1:
>  420e8199d3209bf93e9d0638850115225c2f397c 1322 dh-elpa_0.0.5.dsc
>  b9186e0a45e93b7b866be9b1dc35f4e323d7516b 6538 dh-elpa_0.0.5.tar.gz
>  96a54ce03351565dbdf677517dd63a5d3cd4072e 9168 dh-elpa_0.0.5_all.deb
> Checksums-Sha256:
>  7eedff75b9bccfefab070b50c65cee8285407f86b8ac5ac7fe3b595795ffc226 1322 
> dh-elpa_0.0.5.dsc
>  6a271064ef771a37e5294fc8aecdde5c704002e75d452cf15e692f076db2601d 6538 
> dh-elpa_0.0.5.tar.gz
>  15d36252953837d9479b7ce2323e3984732ede8b0ac6eac6b5e87816998b486e 9168 
> dh-elpa_0.0.5_all.deb
> Files:
>  79a210e59db78409cdbad319021e3285 1322 devel optional dh-elpa_0.0.5.dsc
>  a9528cafcfb0db785d409287c12c26e4 6538 devel optional dh-elpa_0.0.5.tar.gz
>  3a823e8fa1341519abb0b30e760e34ce 9168 devel optional dh-elpa_0.0.5_all.deb
>
>
>
> Thank you for your contribution to Debian.
--- End Message ---
--- Begin Message ---
Source: dh-elpa
Source-Version: 0.0.6

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

Debian distribution maintenance software
pp.
David Bremner  (supplier of updated dh-elpa 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, 03 Sep 2015 18:35:06 -0300
Source: dh-elpa
Binary: dh-elpa
Architecture: source all
Version: 0.0.6
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacs addons team 

Changed-By: David Bremner 
Description:
 dh-elpa- Debian helper tools for packaging emacs lisp extensions

Bug#790324: marked as done (luakit: Improve security level, dubious features)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 22:22:58 +
with message-id 
and subject line Bug#790324: fixed in luakit 2012.09.13-r1-7
has caused the Debian Bug report #790324,
regarding luakit: Improve security level, dubious features
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.)


-- 
790324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: luakit
Version: 2012.09.13-r1-4
Severity: serious

Dear Maintainer,

Looking at globals.lua, I was considering that the low level of security was
due to the (somewhat) aged package. Now, looking at the changes applied by the
'ugh' patch, I see some of these artifacts are not provided upstream, but rather
by the maintainer. From what I understood from an earlier bug report, these
changes were made due to not reproducible builds. Now, before trying to enter
testing again, I think the following points should be considered.


Search engines

All search engines, except github, are specified using an unsecured connexion
although all the servers do. The 'ugh' patch _downgrades_ them, actually. I am
also wondering why was Netflix added, since, afaik, it doesn't work out of
the box.


x509 certificates

Although debatable, support for user-provided x509 certificates is risky.
Personally, I consider certificates installed system-wide (read: by root) much
more trustable. For one, and simply, they cannot be modified by a rogue process
ran by the user.

Regarding 'soup.ssl_strict = false', I don't think I need to explain.


Looking up /etc/hosts

I am pretty sure this is the job of /etc/nsswitch.conf


Thank you


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

Kernel: Linux 4.0.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages luakit depends on:
ii  libatk1.0-0 2.16.0-2
ii  libc6   2.19-18
ii  libcairo2   1.14.2-2
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.5.2-4
ii  libgdk-pixbuf2.0-0  2.31.4-2
ii  libglib2.0-02.44.1-1
ii  libgtk2.0-0 2.24.28-1
ii  libjavascriptcoregtk-1.0-0  2.4.9-2
ii  liblua5.1-0 5.1.5-7.1
ii  libpango-1.0-0  1.36.8-3
ii  libpangocairo-1.0-0 1.36.8-3
ii  libpangoft2-1.0-0   1.36.8-3
ii  libsoup2.4-12.50.0-2
ii  libsqlite3-03.8.10.2-1
ii  libunique-1.0-0 1.1.6-5
ii  libwebkitgtk-1.0-0  2.4.9-2
ii  lua-filesystem [lua5.1-filesystem]  1.6.2-3

luakit recommends no packages.

luakit suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: luakit
Source-Version: 2012.09.13-r1-7

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

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated luakit 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, 03 Sep 2015 23:35:48 +0200
Source: luakit
Binary: luakit
Architecture: source
Version: 2012.09.13-r1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Santiago Vila 
Description:
 luakit - fast and small web browser extensible by Lua
Closes: 790324
Changes:
 luakit (2012.09.13-r1-7) unstable; urgency=medium
 .
   * QA upload.
   * Change debian/patches/2012.09.13-r1-1.diff to use https on several
 search engines allowing it.
   * Add debian/patches/soup-ssl-strict-true.diff to not allow navigation
 on sites with invalid/expired ssl certificates. Closes: #790324.
Checksums-Sha1:
 

Processed: severity of 797959 is important

[Debian Bug Tracking System]

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

> severity 797959 important
Bug #797959 [src:likwid] likwid: FTBFS: unconditional amd64 assembly
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#754659: Some actions destroy backlite on Lenovo X61s

[Santiago Vila]

reassign 754659 xserver-xorg
severity 754659 normal
thanks

On Sun, 13 Jul 2014, Klaus Ethgen wrote:

> Package: luakit
> Version: 2012.09.13-r1-3
> Severity: critical
> 
> I tagged that bug critical as it has some bad effect to the hardware. I
> am not fully sure where the problem lives in. The only informations that
> I have I will put into this report.
> 
> I use luakit on my laptop, a Lenovo X61s with a intel GM965/GL960
> graphic controller. I am not able to reproduce that bug with any other
> browser or software or any other hardware. As X is involved, I will also
> attach the full Xorg log of a broken session.
> 
> When I use luakit and _load new pages_ it often blanks the screen by
> switching the backlight of. There is no way to switch it back on again
> but with a trick, putting the laptop to sleep and waking it up again, I
> get some backlight back. Some means in this case that only the right
> side is lighted. I have to do a full system restart to get the proper
> backlight back. I do not know if that is good for the hardware or not
> but I do not think that it should be the case that a browser is able to
> destroy hardware.
> 
> I have no idea what does trigger the bug but I fear about using luakit
> on that laptop anymore.
> 
> [...]

luakit is just a web browser and has no direct access to hardware by itself.
I'm reassigning this report to xserver-xorg as the most probably package
to blame, but even in such case, be ready to provide the X maintainers
whatever additional information they might ask you.

Thanks.

Processed: Re: Some actions destroy backlite on Lenovo X61s

[Debian Bug Tracking System]

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

> reassign 754659 xserver-xorg
Bug #754659 [luakit] Some actions destroy backlite on Lenovo X61s
Bug reassigned from package 'luakit' to 'xserver-xorg'.
No longer marked as found in versions luakit/2012.09.13-r1-3.
Ignoring request to alter fixed versions of bug #754659 to the same values 
previously set
> severity 754659 normal
Bug #754659 [xserver-xorg] Some actions destroy backlite on Lenovo X61s
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.

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

Bug#797961: ecryptfs-utils: encrypted swap fails

[Richard Jasmin]

Package: ecryptfs-utils
Version: 103-5
Severity: grave
Justification: renders package unusable

mind you even though there are 50 dozen ways listed to do encrypted swap
correctly, only ONE method seems to work.

This is problematic in and of itself.

Using LUKS methods simply DO NOT WORK.

one has to rely on ecryptfs.

sudo ecryptfs-setup-swap

to get encrypted swap in the first place.

When using it we are presented with another problem.

On boot swap fails to properly encrypt.You get a nice "system service
cryptswapper" is busy (time remaining) notice, which does nothing but timeout.

Swap either never gets its random key, never gets written to disk, or never
bothers to properly mount itself.

Unfortunately I cannot tell you which happens as all I can tell is that swap
never gets mounted.There are no /dev/mapper entries for swap, even though there
SHOULD BE.

This can create problems for any other encrypted mount points as well.

Although not having swap is not critical of itself on systems with LARGE RAM,
having unencrypted swap is a security vulnerability and asking for trouble.On
systems with less than 4GB of RAM, not having ANY swap may cause serious
issues.

I do not know yet how repeatable this issue is.This is the first occurrence
since swap has been encrypted.



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
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 ecryptfs-utils depends on:
ii  gettext-base0.19.3-2
ii  keyutils1.5.9-5+b1
ii  libassuan0  2.1.2-2
ii  libc6   2.19-18
ii  libecryptfs0103-5
ii  libgpg-error0   1.17-3
ii  libgpgme11  1.5.1-6
ii  libkeyutils11.5.9-5+b1
ii  libnss3-1d  2:3.17.2-1.1+deb8u1
ii  libpam-runtime  1.1.8-3.1
ii  libpam0g1.1.8-3.1
ii  libtspi10.3.13-3

ecryptfs-utils recommends no packages.

Versions of packages ecryptfs-utils suggests:
ii  cryptsetup  2:1.6.6-5

-- no debconf information

Bug#797966: syncevolution-common: uninstallable due to libsynthesis0 dependency

[gregor herrmann]

Package: syncevolution-common
Version: 1.4.99.4-3
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

syncevolution-common is uninstallable in sid due to the hardcoded
dependency on libsynthesis0; and libsynthesis0 is gone as it got
renamed to libsynthesis0v5 in the ongoing libdstdc++6 transition.

Cheers,
gregor

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJV6O4UXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGnUAP/3GP6EIJ0FOOMcYr/SA6p7JE
bVhTU75yWmc0NUHb1NOHTKXSsNft9846pUIbwMfJKcZhcZ00FS6L5qreWFxl/Hbf
kQ8FMBIIT/lhSL8gGVsnaNciEHKyRjcLyQWR2ulEzfB5dly66PwF46uueyD1J2bZ
tEZGNrPsbq6bXlDWEI3U816SJKx7q1CjDlamJSI1UNCEsqKUVTift2cFtTAXmJJ9
hoela7juK3rcwSzNvRLtN3wPeLmIV7u65e3fx6PgPuM2gQTztxvzAoUKFG8DwlPk
BsAeu8FZ2s2NkmhIAkLDZetm5NTNhThT0yrfm/tQONzt8Xk7+Sek3FfA5BLeuw/W
ztyGDBsiO7qlUpopH1CDDBZ6eZvB6CKukXGthBk9PCsbk0iySDDbRr2RCRz86uaK
n6sieBeKpG9Of35Y5zyJ/eW+SiPO0oTyqMhXshfkUZ4HdUGvUa0YwFjIUFMm7aqO
73+4GVBz7MWAlwr0S89oi0247Dh2+ZTEKAXLg3Kp/+9dFRzzv5F1Lnl5OI7xESBu
ghJb4JMmWLPdiSaKZbrhkZtjXcqAnbZoCoQ+uDLjpmE1AkMfJ/BtXgGjV/n8+oUE
3iN1n1qLWyMfwYFFlqpjEYjNb+zuOhDm6Le+xhmpjVo5vos2YzoDv30Rb5B4Rmtd
YpgdE89a5N2X03siCS5I
=FfOC
-END PGP SIGNATURE-

Bug#787352: marked as done ([RC][cc-by-nc-sa] Please clarify license of a few svg files)

[Debian Bug Tracking System]

Your message dated Fri, 04 Sep 2015 00:34:52 -0400
with message-id <6740050.GWvYERtXme@kitterma-e6430>
and subject line Re: [RC][cc-by-nc-sa] Please clarify license of a few svg files
has caused the Debian Bug report #787352,
regarding [RC][cc-by-nc-sa] Please clarify license of a few svg files
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.)


-- 
787352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:khangman
Severity: serious
version: 4:4.14.1-1
user: lintian-ma...@debian.org
usertags: license-problem-cc-by-nc-sa

Hi,

Could you please clarify the license of:
  themes/winter/khangman_winter.svg
claimed on source to be cc-by-nc-sa, thus non free.

If it is really a non free image please purge these files.

If it is a false positive please override like in 
http://sources.debian.net/src/freecad/0.14.3702%2Bdfsg-3/debian/source/lintian-overrides/
and add a changelog entry and a full explanation on debian/copyright. You may 
ask upstream to remove this cc-by-sa-nc tag on the svg file

Bastien

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
This was an error that has been fixed upstream as of 4:15.08.0-1.

Scott K

On Sun, 31 May 2015 19:42:41 + bastien =?ISO-8859-1?Q?ROUCARI=C8S?= 
 wrote:
> Package: src:khangman
> Severity: serious
> version: 4:4.14.1-1
> user: lintian-ma...@debian.org
> usertags: license-problem-cc-by-nc-sa
> 
> Hi,
> 
> Could you please clarify the license of:
>   themes/winter/khangman_winter.svg
> claimed on source to be cc-by-nc-sa, thus non free.
> 
> If it is really a non free image please purge these files.
> 
> If it is a false positive please override like in 
> 
http://sources.debian.net/src/freecad/0.14.3702%2Bdfsg-3/debian/source/lintian-overrides/
> and add a changelog entry and a full explanation on debian/copyright. You 
may 
> ask upstream to remove this cc-by-sa-nc tag on the svg file
> 
> Bastien--- End Message ---

Processed: fixed 787352 in 4:15.08.0-1

[Debian Bug Tracking System]

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

> fixed 787352 4:15.08.0-1
Bug #787352 [src:khangman] [RC][cc-by-nc-sa] Please clarify license of a few 
svg files
Marked as fixed in versions khangman/4:15.08.0-1.
> thanks
Stopping processing here.

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

Processed: fixed 797470 in 2.1-1, fixed 797470 in 2.0-2, tagging 797470

[Debian Bug Tracking System]

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

> fixed 797470 2.1-1
Bug #797470 [src:dnsval] dnsval: val_dane_check: usage DANE-TA(2) may bypass 
cert validation entirely
Marked as fixed in versions dnsval/2.1-1.
> fixed 797470 2.0-2
Bug #797470 [src:dnsval] dnsval: val_dane_check: usage DANE-TA(2) may bypass 
cert validation entirely
Marked as fixed in versions dnsval/2.0-2.
> # taging for all affected suites so that bug does not get archived before 
> resolved in all suites
> tags 797470 + jessie stretch sid experimental
Bug #797470 [src:dnsval] dnsval: val_dane_check: usage DANE-TA(2) may bypass 
cert validation entirely
Added tag(s) jessie, sid, experimental, and stretch.
> thanks
Stopping processing here.

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

Bug#797937: src:company-mode: maintainer address bounces

[Ansgar Burchardt]

Source: company-mode
Source-Version: 0.8.12-1
Severity: serious
X-Debbugs-Cc: David Bremner 

The maintainer address bounces. I guess the mailing list is
@lists.*alioth*.d.o, not @lists.d.o

Ansgar

Mail Delivery System  writes:
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   pkg-emacsen-add...@lists.debian.org
> SMTP error from remote mail server after RCPT 
> TO::
> host bendel.debian.org [2001:41b8:202:deb:216:36ff:fe40:4002]:
> 550 5.1.1 :
> Recipient address rejected: User unknown in virtual alias table
>
> -- This is a copy of the message, including all the headers. --
>
> Return-path: 
[...]
> To: Debian Emacs addons team , David 
> Bremner 
> X-DAK: dak process-policy
> X-Debian: DAK
> X-Debian-Package: company-mode
> Precedence: bulk
> Auto-Submitted: auto-generated
> MIME-Version: 1.0
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: 8bit
> Subject: company-mode_0.8.12-1_amd64.changes ACCEPTED into unstable, unstable
> Message-Id: 
> Date: Wed, 02 Sep 2015 11:00:09 +
>
>
>
> Accepted:
>
> Format: 1.8
> Date: Fri, 21 Aug 2015 08:49:22 +0200
> Source: company-mode
> Binary: elpa-company
> Architecture: source all
> Version: 0.8.12-1
> Distribution: unstable
> Urgency: low
> Maintainer: Debian Emacs addons team 
> Changed-By: David Bremner 
> Description:
>  elpa-company - Modular in-buffer completion framework for Emacs
> Changes:
>  company-mode (0.8.12-1) unstable; urgency=low
>  .
>* Initial release
> Checksums-Sha1:
>  f0bd5eb142b188af633e25977e8d2db32957a3f5 1786 company-mode_0.8.12-1.dsc
>  0860d609f9104d44cc7cb9eb77483d9e2ad039d7 70379 
> company-mode_0.8.12.orig.tar.gz
>  feb789ffdf148afc174bffd3233466d50ecf07cb 2124 
> company-mode_0.8.12-1.debian.tar.xz
>  c7b280175261cc9e6b926c227d962044e4032152 59064 elpa-company_0.8.12-1_all.deb
> Checksums-Sha256:
>  f2505da463ec877e39e79000bcea4074205707b5fa4a9d5ce05f8b9f08371ea1 1786 
> company-mode_0.8.12-1.dsc
>  67937eda92a617f29091874b00aed04b4b48e8f18accf7bcb56ec64287f3d07d 70379 
> company-mode_0.8.12.orig.tar.gz
>  9e2864dd3165d60550d62fe4cbdb44eb51f2a41b2ffe77d3f1e79160df60 2124 
> company-mode_0.8.12-1.debian.tar.xz
>  d9fb689cb40f74cc494e3b3bf5cd16310dfddd9acd5470fcdefb64d18b2866b0 59064 
> elpa-company_0.8.12-1_all.deb
> Files:
>  445341b13c4df78b91f46edc555448c0 1786 lisp optional company-mode_0.8.12-1.dsc
>  2b4a286d666ca0e00c62b94aa52e7984 70379 lisp optional 
> company-mode_0.8.12.orig.tar.gz
>  4d8f36367727501b8f14bc2bb36a9f76 2124 lisp optional 
> company-mode_0.8.12-1.debian.tar.xz
>  b65e72310ee229009eb84f7d3c287f18 59064 lisp optional 
> elpa-company_0.8.12-1_all.deb
>
>
>
> Thank you for your contribution to Debian.

Processed: Re: Bug#775362: ergo: FTBFS on ppc64el: test suite failure

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #775362 [src:ergo] ergo: FTBFS when higly parallelized: test suite 
fails+hangs
Severity set to 'serious' from 'normal'

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

Bug#797332: ibus-pinyin: diff for NMU version 1.5.0-3.1

[Jonathan Wiltshire]

Control: tags 797332 + patch
Control: tags 797332 + pending

Dear maintainer,

I've prepared an NMU for ibus-pinyin (versioned as 1.5.0-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

diff -Nru ibus-pinyin-1.5.0/debian/changelog ibus-pinyin-1.5.0/debian/changelog
--- ibus-pinyin-1.5.0/debian/changelog	2014-06-05 14:19:18.0 +0100
+++ ibus-pinyin-1.5.0/debian/changelog	2015-09-03 22:12:08.0 +0100
@@ -1,3 +1,10 @@
+ibus-pinyin (1.5.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove hard-coded dependency on libpyzy-1.0-0 (Closes: #797332)
+
+ -- Jonathan Wiltshire   Thu, 03 Sep 2015 22:11:56 +0100
+
 ibus-pinyin (1.5.0-3) unstable; urgency=medium
 
   * Dropped gobject-introspection from depends.
diff -Nru ibus-pinyin-1.5.0/debian/control ibus-pinyin-1.5.0/debian/control
--- ibus-pinyin-1.5.0/debian/control	2014-06-05 14:07:26.0 +0100
+++ ibus-pinyin-1.5.0/debian/control	2015-09-03 22:12:21.0 +0100
@@ -27,7 +27,6 @@
 Architecture: any
 Multi-Arch: foreign
 Depends: ibus (>= 1.5),
- libpyzy-1.0-0,
  python-gi,
  python-xdg,
  ${misc:Depends},


signature.asc
Description: Digital signature

Bug#797470: libval14: val_dane_check: usage DANE-TA(2) may bypass cert validation entirely

[Alessandro Ghedini]

On Mon, Aug 31, 2015 at 10:53:21am +0200, Ondřej Surý wrote:
> Hi security team and Thomas,
> 
> I propose following patch for libval14 in stable:
> 
> Index: validator/libval/val_dane.c
> ===
> --- validator/libval/val_dane.c (revision 8325)
> +++ validator/libval/val_dane.c (working copy)
> @@ -766,23 +766,6 @@
>  break;
>  
>  case DANE_USE_TA_ASSERTION: /*2*/ {
> -SSL_CTX *ctx = SSL_get_SSL_CTX(con);
> -X509_STORE *store;
> -*do_pathval = 0;
> -if (store = X509_STORE_new()) {
> -X509 *tlsa_cert = NULL;
> -c = dane_cur->data;
> -tlsa_cert = d2i_X509(NULL, (const unsigned char
> **), 
> - dane_cur->datalen);
> -X509_STORE_add_cert(store, tlsa_cert);
> -SSL_CTX_set_cert_store(ctx, store);
> -if (SSL_get_verify_result(con) == X509_V_OK) {
> -val_log(context, LOG_INFO, "DANE:
> val_dane_match() success");
> -rv = VAL_DANE_NOERROR;
> -goto done;
> -}
> -}
> -
>  val_log(context, LOG_NOTICE, 
>  "DANE: val_dane_check() for usage %d failed",
>  dane_cur->usage);
> 
> 
> It will just make the DANE validation fail when 2 usage scenario is
> encountered.

I noticed that you applied this patch in unstable closing #797470, but then you
reopened it. Does that mean that the patch is not enough?

> Unfortunately the code in 2.1 has diverted too much (API change), so we
> are not able to use the (possibly fixed) code from there.
> 
> I will also file a bug for irssi and kamailo to drop the libval usage
> and remove the dnsval library from the Debian unless I have a strong
> promise from upstream that they will take care of the library.

It would maybe make sense to drop dnsval from jessie as well (though both irssi
and kamailio would need to be updated there too). Could you try to contact the
Release Team and see what they think about this?

Thanks


signature.asc
Description: Digital signature

Bug#797470: libval14: val_dane_check: usage DANE-TA(2) may bypass cert validation entirely

[Ondřej Surý]

On Thu, Sep 3, 2015, at 15:21, Alessandro Ghedini wrote:
> On Mon, Aug 31, 2015 at 10:53:21am +0200, Ondřej Surý wrote:
> > Hi security team and Thomas,
> > 
> > I propose following patch for libval14 in stable:
> > 
> > Index: validator/libval/val_dane.c
> > ===
> > --- validator/libval/val_dane.c (revision 8325)
> > +++ validator/libval/val_dane.c (working copy)
> > @@ -766,23 +766,6 @@
> >  break;
> >  
> >  case DANE_USE_TA_ASSERTION: /*2*/ {
> > -SSL_CTX *ctx = SSL_get_SSL_CTX(con);
> > -X509_STORE *store;
> > -*do_pathval = 0;
> > -if (store = X509_STORE_new()) {
> > -X509 *tlsa_cert = NULL;
> > -c = dane_cur->data;
> > -tlsa_cert = d2i_X509(NULL, (const unsigned char
> > **), 
> > - dane_cur->datalen);
> > -X509_STORE_add_cert(store, tlsa_cert);
> > -SSL_CTX_set_cert_store(ctx, store);
> > -if (SSL_get_verify_result(con) == X509_V_OK) {
> > -val_log(context, LOG_INFO, "DANE:
> > val_dane_match() success");
> > -rv = VAL_DANE_NOERROR;
> > -goto done;
> > -}
> > -}
> > -
> >  val_log(context, LOG_NOTICE, 
> >  "DANE: val_dane_check() for usage %d failed",
> >  dane_cur->usage);
> > 
> > 
> > It will just make the DANE validation fail when 2 usage scenario is
> > encountered.
> 
> I noticed that you applied this patch in unstable closing #797470, but
> then you reopened it. Does that mean that the patch is not enough?

Nope, I think the patch is enough. I reopened, so we don't forgot to fix
this in jessie.

> > Unfortunately the code in 2.1 has diverted too much (API change), so we
> > are not able to use the (possibly fixed) code from there.
> > 
> > I will also file a bug for irssi and kamailo to drop the libval usage
> > and remove the dnsval library from the Debian unless I have a strong
> > promise from upstream that they will take care of the library.
> 
> It would maybe make sense to drop dnsval from jessie as well (though both
> irssi and kamailio would need to be updated there too). Could you try to
> contact the Release Team and see what they think about this?

I spoke to the upstream and they are still working on the whole
dnssec-tools suite, but I would still rather see irssi and kamailio use
some better library to do the DNSSEC validation.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

Bug#797755: insighttoolkit: ABI transition needed for libstdc++ v5

[Steve M. Robbins]

On September 2, 2015 02:48:01 PM Simon McVittie wrote:

> How long ago were maintainers of packages depending on insighttoolkit 3
> told that it was obsolete and going to be removed?

Most recently: on August 12th; see 
https://lists.debian.org/debian-med/2015/08/msg00089.html


-Steve


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

Bug#796305: python-oauthlib: FTBFS: plugin distutils failed with: exit code=1:

[Daniele Tricoli]

Hello Chris,

On Monday 24 August 2015 10:36:01 Chris Lamb wrote:
> No problem and good luck :)

Many thanks! ;)

python-oauthlib 1.0.3-1 was uploaded in the meantime without the possibility 
to close this bug in the changelog.

Can I close it specifying Version in the pseudo-header? Or should I do 
something else? Thanks!

Cheers,

-- 
 Daniele Tricoli 'eriol'
 https://mornie.org

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

Bug#796458: marked as done (python-apt: FTBFS: test_pep8.PackagePep8TestCase fails)

[Debian Bug Tracking System]

Your message dated Thu, 3 Sep 2015 14:55:16 +0200
with message-id <20150903145315.ga32...@debian.org>
and subject line Re: Bug#796458: python-apt: FTBFS: 
test_pep8.PackagePep8TestCase fails
has caused the Debian Bug report #796458,
regarding python-apt: FTBFS: test_pep8.PackagePep8TestCase 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.)


-- 
796458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-apt
Version: 1.0.0~beta3.1
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

make[1]: Leaving directory '/python-apt-1.0.0~beta3.1'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/python-apt-1.0.0~beta3.1'
set -e; for python in python2.7 python3.4 ; do \
$python tests/test_all.py -q || [ "linux" = "hurd" ]; \
done;
/python-apt-1.0.0~beta3.1/tests/../doc/source/examples/dpkg-contents.py:19:39: 
W503 line break before binary operator
/python-apt-1.0.0~beta3.1/tests/../doc/source/examples/dpkg-contents.py:23:39: 
W503 line break before binary operator
/python-apt-1.0.0~beta3.1/tests/../tests/test_apt_cache.py:25:1: E402 module 
level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_apt_cache.py:26:1: E402 module 
level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_auth.py:25:1: E402 module level 
import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_auth.py:26:1: E402 module level 
import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_debfile.py:19:1: E402 module 
level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_debfile.py:20:1: E402 module 
level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_debfile_multiarch.py:17:1: E402 
module level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_debfile_multiarch.py:18:1: E402 
module level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_debfile_multiarch.py:19:1: E402 
module level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_lp659438.py:25:1: E402 module 
level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_lp659438.py:26:1: E402 module 
level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_lp659438.py:27:1: E402 module 
level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_lp659438.py:28:1: E402 module 
level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_lp659438.py:30:1: E402 module 
level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_lp659438.py:31:1: E402 module 
level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_size_to_str.py:5:1: E402 module 
level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_size_to_str.py:7:1: E402 module 
level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/test_tagfile.py:28:1: E402 module 
level import not at top of file
/python-apt-1.0.0~beta3.1/tests/../tests/old/apt-test.py:3:1: E402 module level 
import not at top of file
/python-apt-1.0.0~beta3.1/tests/../aptsources/distro.py:129:25: W503 line break 
before binary operator
/python-apt-1.0.0~beta3.1/tests/../aptsources/distro.py:132:27: W503 line break 
before binary operator
/python-apt-1.0.0~beta3.1/tests/../aptsources/sourceslist.py:381:21: W503 line 
break before binary operator
/python-apt-1.0.0~beta3.1/tests/../apt/__init__.py:30:1: E402 module level 
import not at top of file
[tests] Running on 2.7.10 (default, Jul  1 2015, 10:54:53) [GCC 4.9.2]
Using library_dir: 
'/python-apt-1.0.0~beta3.1/build/lib.linux-x86_64-2.7'WARNING: Failed to read 
mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
WARNING: Failed to read mirror file
==
FAIL: test_pep8 (test_pep8.PackagePep8TestCase)
--
Traceback (most recent call last):
  File "/python-apt-1.0.0~beta3.1/tests/test_pep8.py", line 26, in test_pep8
self.fail("pep8 failed with: %s" % res)
AssertionError: pep8 failed 

Bug#796305: python-oauthlib: FTBFS: plugin distutils failed with: exit code=1:

[Chris Lamb]

> python-oauthlib 1.0.3-1 was uploaded in the meantime without the
> possibility to close this bug in the changelog.
> 
> Can I close it specifying Version in the pseudo-header?

Yes, just send a new email as follows (or reply and modify this one):

  To: 796305-d...@bugs.debian.org
  Subject: Re: python-oauthlib: FTBFS: plugin distutils failed with:
  exit code=1:

  Version: 1.0.3-1

  (whatever you want here)


Regards,

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

Bug#797896: FTBFS: error: 'buildString' is not a member of 'Puma::StrCol'

[Julien Cristau]

Source: undertaker
Version: 1.6-2.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

your package no longer builds in sid, see logs at
https://buildd.debian.org/status/logs.php?pkg=undertaker=1.6-2.1%2Bb1=sid

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#790975: Resetting auto-removal timer

[Raphael Hertzog]

Hello,

just a short mail sent to those bugs to show that even though the fixes
have not yet landed in testing, we do care about the package not getting
removed from testing...

14:57  nthykier: will https://tracker.debian.org/pkg/autopsy be removed 
really? both bugs are fixed but they did not migrate due to the current 
transition I guess 
15:00  I can cheat and reduce the severity of both bugs, or mark them as 
not affecting testing, but I wonder if something cleaner can be done.
15:02  buxy: No, don't downgrade them!  Just send a mail to them
15:02  buxy: That is and have always been sufficient to reset the 
timer

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#797955: initramfs-tools: initramfs fails to activate swap on encrypted LVM2 partition; fails boot

[Ben Hutchings]

Control: severity -1 important
Control: reassign -1 lvm2

On Thu, 2015-09-03 at 23:30 +0200, Arnaud Installe wrote:
> Package: initramfs-tools
> Version: 0.120
> Severity: critical
> Justification: breaks the whole system
> 
> All my partitions (except /boot) are on encrypted LVM2 partitions.
> 
> When booting, initramfs asks for the passwords to unlock the /root & /usr
> partitions, which are mounted successfully. It then fails to ask for the swap
> partition password, instead looping a few minutes, posting messages that it is
> waiting for all volumes to become available and "/run/lvm/lvmetad.socket:
> connect failed". Disabling lvmetad did not help.
[...]

The initramfs has never been responsible for setting up the swap
partition.

It sounds like the fault is with lvm2 though it could be cryptsetup.

Reducing severity because this is not a normal configuration and you
have a workaround for it.

Ben.

-- 
Ben Hutchings
Q.  Which is the greater problem in the world today, ignorance or apathy?
A.  I don't know and I couldn't care less.



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

Processed: your mail

[Debian Bug Tracking System]

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

> close 794258 0.4.1-3
Bug #794258 [src:ruby-jsonify] FTBFS: "Jsonify::Builder attributes! should 
allow create object with attributes of another object" fails
Marked as fixed in versions ruby-jsonify/0.4.1-3.
Bug #794258 [src:ruby-jsonify] FTBFS: "Jsonify::Builder attributes! should 
allow create object with attributes of another object" fails
Marked Bug as done
>
End of message, stopping processing here.

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

Processed: Re: Bug#797955: initramfs-tools: initramfs fails to activate swap on encrypted LVM2 partition; fails boot

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #797955 [initramfs-tools] initramfs-tools: initramfs fails to activate swap 
on encrypted LVM2 partition; fails boot
Severity set to 'important' from 'critical'
> reassign -1 lvm2
Bug #797955 [initramfs-tools] initramfs-tools: initramfs fails to activate swap 
on encrypted LVM2 partition; fails boot
Bug reassigned from package 'initramfs-tools' to 'lvm2'.
No longer marked as found in versions initramfs-tools/0.120.
Ignoring request to alter fixed versions of bug #797955 to the same values 
previously set

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

Bug#797855: spice-gtk:spice-common/common/generated_* not reliably generated from source

[Liang Guo]

Hi, Chris,
On Fri, Sep 4, 2015 at 1:56 AM, Chris Lamb  wrote:
>
> If it helps, here is a diff between the two:
>
>  
> https://reproducible.debian.net/logdiffs/unstable/amd64/spice-gtk_0.29-1.diff.gz
>
Your pbuild have a custom script called D01_modify_environment, Can you show
me the content ?

Thanks,
-- 
Liang Guo
http://guoliang.me/

Bug#796021: marked as done (ruby-i18n-inflector-rails: FTBFS: `find_formatter': Formatter 'nested' unknown - maybe you meant 'documentation' or 'progress'?. (ArgumentError))

[Debian Bug Tracking System]

Your message dated Fri, 04 Sep 2015 05:03:43 +
with message-id 
and subject line Bug#796021: fixed in ruby-i18n-inflector-rails 1.0.7-3
has caused the Debian Bug report #796021,
regarding ruby-i18n-inflector-rails: FTBFS: `find_formatter': Formatter 
'nested' unknown - maybe you meant 'documentation' or 'progress'?. 
(ArgumentError)
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.)


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

Dear Maintainer,

ruby-i18n-inflector-rails fails to build from source on unstable/amd64:

  [..]
  Running tests for ruby2.1 using debian/ruby-tests.rake ...
  
RUBYLIB=/tmp/buildd/ruby-i18n-inflector-rails-1.0.7/debian/ruby-i18n-inflector-rails/usr/lib/ruby/vendor_ruby:.
  ruby2.1 -rrake -e ARGV.unshift\(\"-f\",\
  \"debian/ruby-tests.rake\"\)\;\ Rake.application.run
  /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
  /usr/lib/ruby/vendor_ruby/rspec/core/formatters.rb:172:in
  `find_formatter': Formatter 'nested' unknown - maybe you meant
  'documentation' or 'progress'?. (ArgumentError)
from /usr/lib/ruby/vendor_ruby/rspec/core/formatters.rb:140:in
`add'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:752:in
`add_formatter'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:114:in
`block in load_formatters_into'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:114:in
`each'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:114:in
`load_formatters_into'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:23:in
`configure'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:102:in
`setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in
`invoke'
from /usr/bin/rspec:4:in `'
  /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
  failed
  ERROR: Test "ruby2.1" failed. Exiting.
  dh_auto_install: dh_ruby --install
  /tmp/buildd/ruby-i18n-inflector-rails-1.0.7/debian/ruby-i18n-inflector-rails
  returned exit code 1
  debian/rules:15: recipe for target 'binary' failed
  make: *** [binary] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

The full build log is attached or can be viewed here:

  
https://reproducible.debian.net/logs/unstable/amd64/ruby-i18n-inflector-rails_1.0.7-2.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sat Jul 18 21:45:09 GMT+12 2015
I: pbuilder-time-stamp: 1437299109
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 9), gem2deb (>= 0.7.5~), rake, ruby-rspec, 
ruby-i18n-inflector, ruby-actionpack (>= 2:3.0), ruby-railties (>= 2:3.0)
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20236 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb