Bug#829724: marked as done (bzr-git: FTBFS: AssertionError: not equal: a = [..] DeprecationWarning [..] b = '')

[Debian Bug Tracking System]

Your message dated Wed, 13 Jul 2016 07:39:18 +0200
with message-id <137afe13-4794-4580-bad6-2dae7e7c8...@jelmer.uk>
and subject line Done
has caused the Debian Bug report #829724,
regarding bzr-git: FTBFS: AssertionError: not equal: a = [..] 
DeprecationWarning  [..]  b = ''
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.)


-- 
829724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bzr-git
Version: 0.6.12+bzr1635-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,

bzr-git fails to build from source in unstable/amd64:

  [..]

  
bzrlib.plugins.git.tests.test_transportgit.TransportObjectStoreTests.test_add_objects
   OK5ms
  
bzrlib.plugins.git.tests.test_transportgit.TransportObjectStoreTests.test_iter  
 OK4ms
  bzrlib.plugins.git.tests.test_unpeel_map.TestUnpeelMap.test_new   OK
3ms
  bzrlib.plugins.git.tests.test_branch.BranchTests.test_interbranch_pull   OK   
   132ms
  bzrlib.plugins.git.tests.test_branch.TestGitBranch.test_open_by_ref   OK  
  4ms
  
bzrlib.plugins.git.tests.test_branch.TestWithGitBranch.test_get_physical_lock_status
   OK   15ms
  bzrlib.plugins.git.tests.test_cache.SqliteGitShaMapTests.test_commit   OK 
 966ms
  bzrlib.plugins.git.tests.test_cache.IndexGitShaMapTests.test_commit   OK  
  7ms
  bzrlib.plugins.git.tests.test_cache.TdbGitShaMapTests.test_tree   OK  
100ms
  bzrlib.plugins.git.tests.test_fetch.ImportObjects.test_import_tree_empty   OK 
   5ms
  bzrlib.plugins.git.tests.test_cache.TdbGitShaMapTests.test_revids   OK   
90ms
  bzrlib.plugins.git.tests.test_fetch.ImportObjects.test_import_blob_simple   
OK5ms
  bzrlib.plugins.git.tests.test_fetch.LocalRepositoryFetchTests.test_empty   OK 
  11ms
  bzrlib.plugins.git.tests.test_git_remote_helper.FetchTests.test_no_wants   OK 
  23ms
  bzrlib.plugins.git.tests.test_mapping.DirectoryToTreeTests.test_empty   OK
2ms
  bzrlib.plugins.git.tests.test_mapping.FileidTests.test_unescape_control_l   
OK1ms
  
bzrlib.plugins.git.tests.test_mapping.RoundtripRevisionsFromGit.test_commit_encoding
   OK2ms
  
bzrlib.plugins.git.tests.test_mapping.TestRevidConversionV1.test_simple_bzr_to_git_revision_id
   OK2ms
  
bzrlib.plugins.git.tests.test_object_store.FindMissingBzrRevidsTests.test_simple
   OK1ms
  
bzrlib.plugins.git.tests.test_pristine_tar.ReadPristineTarData.test_read_pristine_tar_data
   OK2ms
  
bzrlib.plugins.git.tests.test_push.InterToGitRepositoryTests.test_pointless_fetch_refs
   OK   15ms
  bzrlib.plugins.git.tests.test_remote.SplitUrlTests.test_simple   OK3ms
  
bzrlib.plugins.git.tests.test_repository.TestGitRepository.test_get_signature_text
   OK   10ms
  bzrlib.plugins.git.tests.test_fetch.LocalRepositoryFetchTests.test_executable 
  OK  127ms
  
bzrlib.plugins.git.tests.test_repository.TestGitRepositoryFeatures.test_open_existing
   OK6ms
  bzrlib.plugins.git.tests.test_roundtrip.FileIdRoundTripTests.test_deserialize 
  OK2ms
  bzrlib.plugins.git.tests.test_roundtrip.RoundtripTests.test_properties   OK   
 2ms
  
bzrlib.plugins.git.tests.test_transportgit.TransportObjectStoreTests.test_close 
  OK4ms
  
bzrlib.plugins.git.tests.test_transportgit.TransportObjectStoreTests.test_iter_tree_contents_include_trees
   OK   12ms
  bzrlib.plugins.git.tests.test_workingtree.GitWorkingTreeTests.test_conflicts  
 OK8ms
  bzrlib.plugins.git.tests.test_cache.SqliteGitShaMapTests.test_blob   OK  
897ms
  bzrlib.plugins.git.tests.test_git_remote_helper.FetchTests.test_simple   OK   
   139ms
  bzrlib.plugins.git.tests.test_mapping.DirectoryToTreeTests.test_empty_dir   
OK2ms
  bzrlib.plugins.git.tests.test_mapping.FileidTests.test_unescape_underscore   
OK2ms
  
bzrlib.plugins.git.tests.test_mapping.RoundtripRevisionsFromGit.test_commit_zero_utc_timezone
   OK3ms
  
bzrlib.plugins.git.tests.test_mapping.TestRevidConversionV1.test_simple_git_to_bzr_revision_id
   OK2ms
  
bzrlib.plugins.git.tests.test_object_store.FindMissingBzrRevidsTests.test_two_missing
   OK2ms
  
bzrlib.plugins.git.tests.test_pristine_tar.ReadPristineTarData.test_read_pristine_tar_data_no_branch
   OK2ms
  
bzrlib.plugins.git.tests.test_push.InterToGitRepositoryTests.test_pointless_fetch_refs_old_mapping
   

Bug#784612: [anki] Qt4's WebKit removal

[Nicolas Kuttler]

There are alpha builds with Qt5 available,

http://ankisrs.net/download/mirror/alpha/

https://anki.tenderapp.com/discussions/beta-testing/172-anki-210-alpha-1

https://anki.tenderapp.com/discussions/beta-testing/174-anki-210-alpha-2

Bug#811844: marked as done (composite: FTBFS with GCC 6: no match for)

[Debian Bug Tracking System]

Your message dated Wed, 13 Jul 2016 04:04:57 +
with message-id 
and subject line Bug#811844: fixed in composite 0.006.2+dfsg0-5
has caused the Debian Bug report #811844,
regarding composite: FTBFS with GCC 6: no match for
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.)


-- 
811844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: composite
Version: 0.006.2+dfsg0-4
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-no-match

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> cd /<>/composite-0.006.2+dfsg0/obj-x86_64-linux-gnu/src/Tritium && 
> /usr/bin/c++   -DFLAC_SUPPORT -DJACK_SUPPORT -DLADSPA_SUPPORT -DLRDF_SUPPORT 
> -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_XML_LIB -DTritium_EXPORTS 
> -I/<>/composite-0.006.2+dfsg0/obj-x86_64-linux-gnu -isystem 
> /usr/include/qt4 -isystem /usr/include/qt4/QtGui -isystem 
> /usr/include/qt4/QtXml -isystem /usr/include/qt4/QtCore 
> -I/<>/composite-0.006.2+dfsg0 
> -I/<>/composite-0.006.2+dfsg0/src/Tritium/.  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -O2 -g -DNDEBUG -fPIC   -o 
> CMakeFiles/Tritium.dir/src/Sampler.o -c 
> /<>/composite-0.006.2+dfsg0/src/Tritium/src/Sampler.cpp
> /<>/composite-0.006.2+dfsg0/src/Tritium/src/LocalFileMng.cpp: In 
> member function 'int Tritium::LocalFileMng::savePlayList(const string&)':
> /<>/composite-0.006.2+dfsg0/src/Tritium/src/LocalFileMng.cpp:719:20:
>  warning: converting to non-pointer type 'int' from NULL [-Wconversion-null]
>  return NULL;
> ^~~~
> 
> /<>/composite-0.006.2+dfsg0/src/Tritium/src/LocalFileMng.cpp: In 
> member function 'int Tritium::LocalFileMng::loadPlayList(const string&)':
> /<>/composite-0.006.2+dfsg0/src/Tritium/src/LocalFileMng.cpp:736:21:
>  error: no match for 'operator==' (operand types are 'std::ifstream {aka 
> std::basic_ifstream}' and 'long int')
>  if ( verify == NULL ) {
>   ~~~^~~~
> 
> /<>/composite-0.006.2+dfsg0/src/Tritium/src/LocalFileMng.cpp:736:21:
>  note: candidate: operator==(int, long int) 
> /<>/composite-0.006.2+dfsg0/src/Tritium/src/LocalFileMng.cpp:736:21:
>  note:   no known conversion for argument 1 from 'std::ifstream {aka 
> std::basic_ifstream}' to 'int'
> In file included from /usr/include/qt4/QtCore/qchar.h:45:0,
>  from /usr/include/qt4/QtCore/qstring.h:45,
>  from /usr/include/qt4/QtCore/qdir.h:45,
>  from /usr/include/qt4/QtCore/qabstractfileengine.h:45,
>  from /usr/include/qt4/QtCore/QtCore:3,
>  from 
> /<>/composite-0.006.2+dfsg0/src/Tritium/./Tritium/Logger.hpp:30,
>  from 
> /<>/composite-0.006.2+dfsg0/src/Tritium/src/LocalFileMng.cpp:26:
> /usr/include/qt4/QtCore/qglobal.h:2140:13: note: candidate: bool 
> operator==(QBool, bool)
>  inline bool operator==(QBool b1, bool b2) { return !b1 == !b2; }
>  ^~~~
--- End Message ---
--- Begin Message ---
Source: composite
Source-Version: 0.006.2+dfsg0-5

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

Debian distribution maintenance software
pp.
Jaromír Mikeš  (supplier of updated composite 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: SHA1

Format: 1.8
Date: Tue, 12 Jul 2016 13:44:40 +0200
Source: composite
Binary: composite composite-data
Architecture: source all amd64
Version: 0.006.2+dfsg0-5
Distribution: unstable

Bug#817708: uml-utilities marked for removal

[Mattia Dongili]

On Tue, Jul 12, 2016 at 06:29:14PM +0200, Ritesh Raj Sarraf wrote:
...

> PS: And I just noticed you did some work with uml-utilities. Thanks.

Yes, I'm trying to upload a new revision.

-- 
mattia
:wq!

Processed: Bug#811844 marked as pending

[Debian Bug Tracking System]

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

> tag 811844 pending
Bug #811844 [composite] composite: FTBFS with GCC 6: no match for
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#811844: marked as pending

[Jaromír Mikeš]

tag 811844 pending
thanks

Hello,

Bug #811844 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-multimedia/composite.git;a=commitdiff;h=8e6e1b2

---
commit 8e6e1b24e094c5c0ac30489bc60369dc4296cac0
Author: Jaromír Mikeš 
Date:   Wed Jul 13 04:01:35 2016 +0200

Finalize changelog.

diff --git a/debian/changelog b/debian/changelog
index e01c9f1..bc6bb2b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -6,7 +6,7 @@ composite (0.006.2+dfsg0-5) unstable; urgency=medium
   * Fix some hardening.
   * Update copyright file.
   * Replace scripts by triggers file.
-  * Add patch to fix FTBFS with gcc-6.
+  * Add patch to fix FTBFS with gcc-6 (Closes: #811844).
   * Fix more spelling.
   * Dropping dbg package.
   * Update watch file for gitlab.

Bug#830939: knot-resolver: FTBFS: missing files: usr/lib/knot-resolver/tinyweb/*

[Aaron M. Ucko]

Source: knot-resolver
Version: 1.1.0~git2016070600-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of knot-resolver on mips(el) and powerpc(spe) have been failing:

  Optional
  
  [yes] doxygen (doc)
  [no] go (modules/go, Go buildmode=c-shared support)
  [no] geoip (modules/tinyweb, github.com/abh/geoip)
  [...]
  dh_install --fail-missing
  dh_install: Cannot find (any matches for) "usr/lib/knot-resolver/tinyweb/*" 
(tried in "." and "debian/tmp")
  dh_install: knot-resolver-module-tinyweb missing files: 
usr/lib/knot-resolver/tinyweb/*
  dh_install: missing files, aborting
  debian/rules:76: recipe for target 'override_dh_install' failed

Could you please take a look?  With any luck, it should suffice to declare

  Architecture: amd64 i386 armhf armel arm64

for knot-resolver-module-tinyweb, in keeping with the relevant build
dependencies' architecture restrictions.

Thanks!

Processed: affects 829691

[Debian Bug Tracking System]

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

> affects 829691 ruby-shoulda
Bug #829691 [ruby-shoulda-matchers] ruby-shoulda-matchers: can not be used to 
satisfy shoulda dependency
Added indication that 829691 affects ruby-shoulda
> thanks
Stopping processing here.

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

Bug#830931: Gem::LoadError: Could not find 'ruby2ruby' (>= 0) among 13 total gem(s)

[Christian Hofstaedtler]

Package: ruby-ruby2ruby
Version: 2.0.7-1
Severity: serious
X-Debbugs-CC: debian-r...@lists.debian.org

Dear Maintainer,

your gem library fails to load on ruby2.3:

GEM_PATH= ruby2.3 -e gem\ \"ruby2ruby\"
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'ruby2ruby' (>= 0) among 13 total gem(s) (Gem::LoadError)
Checked in 
'GEM_PATH=/home/debci/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
 execute `gem env` for more information

Given the last upload date and package contents, this also applies
to jessie/ruby2.1.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#830924: Gem::LoadError: Could not find 'rack-flash3' (>= 0) among 17 total gem(s)

[Christian Hofstaedtler]

Package: ruby-rack-flash3
Version: 1.0.5-1
Severity: serious
X-Debbugs-CC: debian-r...@lists.debian.org

Dear Maintainer,

your gem library fails to load on ruby2.3:

GEM_PATH= ruby2.3 -e gem\ \"rack-flash3\"
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'rack-flash3' (>= 0) among 17 total gem(s) (Gem::LoadError)
Checked in 
'GEM_PATH=/home/debci/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
 execute `gem env` for more information

Given the last upload date and package contents, this also applies
to jessie/ruby2.1.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#830918: Could not find 'paint' (>= 0) among 13 total gem(s)

[Christian Hofstaedtler]

Package: ruby-paint
Version: 0.8.6-1
Severity: serious
X-Debbugs-CC: debian-r...@lists.debian.org

Dear Maintainer,

your gem library fails to load on ruby2.3:

GEM_PATH= ruby2.3 -e gem\ \"paint\"
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'paint' (>= 0) among 18 total gem(s) (Gem::LoadError)
Checked in 
'GEM_PATH=/home/debci/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
 execute `gem env` for more information

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#830917: Gem::LoadError: Could not find 'rack-openid' (~> 1.3.1) - did find: [rack-openid-1.4.2]

[Christian Hofstaedtler]

Package: ruby-omniauth-openid
Version: 1.0.1-3
Severity: serious
X-Debbugs-CC: debian-r...@lists.debian.org

Dear Maintainer,

your gem library fails to load on ruby2.3:

ruby2.3 -e gem\ \"omniauth-openid\"
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'rack-openid' (~> 1.3.1) - did find: [rack-openid-1.4.2] (Gem::LoadError)
Checked in 
'GEM_PATH=/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
 execute `gem env` for more information
[...]

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#830916: ActionView::Template::Error (undefined method `recaptcha_tags` ...)

[Christian Hofstaedtler]

Package: redmine-plugin-recaptcha
Version: 0.1.0+git20121018-3
Severity: serious

Dear Maintainer,

when testing your redmine plugin against the current redmine in
sid (3.2.3-1), I've found that redmine aborts with an internal error when
clicking on the "Register" link. From production.log:

  Started GET "/account/register" for 192.168.234.1 at 2016-07-13 00:37:27 +0200
  Processing by AccountController#register as HTML
Current user: anonymous
Rendered plugins/redmine_recaptcha/app/views/account/register.html.erb 
within layouts/base (775.4ms)
  Completed 500 Internal Server Error in 782ms (ActiveRecord: 0.9ms)
  
  ActionView::Template::Error (undefined method `recaptcha_tags' for 
#<#:0x007f1f95b5d6f8>):
  40: 
  41: 
  42: 
  43: <%= recaptcha_tags :public_key => 
Setting.plugin_redmine_recaptcha['recaptcha_public_key'], :ssl => true %>
  44:  
  45: <%= submit_tag l(:button_submit) %>
  46: <% end %>
plugins/redmine_recaptcha/app/views/account/register.html.erb:43:in `block 
in 
_plugins_redmine_recaptcha_app_views_account_register_html_erb__732500603993694831_69886816182180'
plugins/redmine_recaptcha/app/views/account/register.html.erb:3:in 
`_plugins_redmine_recaptcha_app_views_account_register_html_erb__732500603993694831_69886816182180'
lib/redmine/sudo_mode.rb:63:in `sudo_mode'


-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Processed: Re: Bug#811825: ppl: FTBFS with GCC 6: no match for

[Debian Bug Tracking System]

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

> tags 811825 - patch pending
Bug #811825 [ppl] ppl: FTBFS with GCC 6: no match for
Removed tag(s) patch and pending.
> thanks
Stopping processing here.

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

Bug#817452: marked as done (fftw: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 21:51:17 +
with message-id 
and subject line Bug#817452: fixed in fftw 2.1.5-4
has caused the Debian Bug report #817452,
regarding fftw: Removal of debhelper compat 4
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.)


-- 
817452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fftw
Severity: important
Usertags: compat-4-removal

Hi,

The package fftw uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: fftw
Source-Version: 2.1.5-4

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

Debian distribution maintenance software
pp.
Thibaut Paumard  (supplier of updated fftw package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 12 Jul 2016 09:42:31 +0200
Source: fftw
Binary: fftw2 fftw-dev sfftw2 sfftw-dev fftw-docs
Architecture: source
Version: 2.1.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Thibaut Paumard 
Description:
 fftw-dev   - library for computing Fast Fourier Transforms
 fftw-docs  - documentation for fftw
 fftw2  - library for computing Fast Fourier Transforms
 sfftw-dev  - library for computing Fast Fourier Transforms
 sfftw2 - library for computing Fast Fourier Transforms
Closes: 817452
Changes:
 fftw (2.1.5-4) unstable; urgency=medium
 .
   * Team upload
   * Bug fix: "Removal of debhelper compat 4", thanks to
 ni...@thykier.net; (Closes: #817452).
Checksums-Sha1:
 2548fc20d66b932863566bbc021cc875192ebefa 2188 fftw_2.1.5-4.dsc
 670d3ac720d7526c1cdfc3dd88c926504173097d 58072 fftw_2.1.5-4.debian.tar.xz
Checksums-Sha256:
 31fb76b29c119f6d1c6b49533d661cdf5d74411d1d8962eb51b3d960926b9acc 2188 
fftw_2.1.5-4.dsc
 7c8b4233e0996319c7849b2f0b642efae09fed100494932a30005ed86cf8d9df 58072 
fftw_2.1.5-4.debian.tar.xz
Files:
 41ff490ba0daf621fed3f6320790cd33 2188 oldlibs extra fftw_2.1.5-4.dsc
 9acf562af35f610396deaef7439bf125 58072 oldlibs extra fftw_2.1.5-4.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXhV6HAAoJEJOUU0jg3ChACFgQANWCW+KQNMZI8lwOLQoLjAVJ
sIcedm2Ulf9+3zwXAdeAQb3C1FGffpdynokz9Kf9w82nb0kSJn3YFFRrkVYVGyMB
QyPIGy4WtH07Px3nG+gurHSvuGUAgw+GzfS+ynoUEcvHBJiLcvlrO3WBvvybEjOc
N0R8FHs3dV138BK449ziInlsSs0tSe6wdU7jFAYIT6OY+cU5MvdZlXhMBvthF13N
q9rBF/Etul26zWZvlIvCsVmMQaam+X81qSsGZBhsIk5/d/DTBBUzmR/n4mJrG6Zv
IzgOpyoIVx4uezSOO0u/etZzcR9p8l/k6zaBZ8Bi23w6hX0b2SAepRARUtei2nd+
YotCjhJTfiZyPG37VLhQdtAwGpsLO+oczz6vS9Qvf9hsFCoBlNLlrNMGVAmttSZu
8NhnBisdovKR9azMp5Hcxrwd1FiGVoEMl5D8KSEl9Lz70Hke1qCy6jduJdS0YrHe
o4AD90U/RU9NHyraT8++JJCMwMK1HeYksrkVTNdp5C2KIDfQY2l03SHQeO9P2tso
om323x0p05bQpBGCeVOp1eAtsHFsx3XdIeOcoEpVRheiGo79zBUAVq4CeNcnoSBi
Y6BzQojtC5oo/LpkE2i0q7e+Maem5MLaBYIDZ5i9avn/RTeRM2EmeumT3PmeB2in
l8IJF22myUyY5SMFDRfW
=w0T2
-END PGP SIGNATURE End Message ---

Bug#828713: marked as done (appstream-generator: FTBFS: source/archive.d:546:11: error: instead of C-style syntax, use D-style syntax 'ubyte[] emptyGz')

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 21:50:47 +
with message-id 
and subject line Bug#828713: fixed in appstream-generator 0.4.0-1
has caused the Debian Bug report #828713,
regarding appstream-generator: FTBFS: source/archive.d:546:11: error: instead 
of C-style syntax, use D-style syntax 'ubyte[] emptyGz'
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.)


-- 
828713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: appstream-generator
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,

appstream-generator fails to build from source in unstable/amd64:

  [..]

  Selecting previously unselected package libtiff5:amd64.
  Preparing to unpack .../libtiff5_4.0.6-1_amd64.deb ...
  Unpacking libtiff5:amd64 (4.0.6-1) ...
  Selecting previously unselected package shared-mime-info.
  Preparing to unpack .../shared-mime-info_1.6-1_amd64.deb ...
  Unpacking shared-mime-info (1.6-1) ...
  Selecting previously unselected package libgdk-pixbuf2.0-common.
  Preparing to unpack .../libgdk-pixbuf2.0-common_2.34.0-1_all.deb ...
  Unpacking libgdk-pixbuf2.0-common (2.34.0-1) ...
  Selecting previously unselected package libgdk-pixbuf2.0-0:amd64.
  Preparing to unpack .../libgdk-pixbuf2.0-0_2.34.0-1_amd64.deb ...
  Unpacking libgdk-pixbuf2.0-0:amd64 (2.34.0-1) ...
  Selecting previously unselected package libgirepository-1.0-1:amd64.
  Preparing to unpack .../libgirepository-1.0-1_1.48.0-2_amd64.deb ...
  Unpacking libgirepository-1.0-1:amd64 (1.48.0-2) ...
  Selecting previously unselected package gir1.2-glib-2.0:amd64.
  Preparing to unpack .../gir1.2-glib-2.0_1.48.0-2_amd64.deb ...
  Unpacking gir1.2-glib-2.0:amd64 (1.48.0-2) ...
  Selecting previously unselected package gir1.2-gdkpixbuf-2.0:amd64.
  Preparing to unpack .../gir1.2-gdkpixbuf-2.0_2.34.0-1_amd64.deb ...
  Unpacking gir1.2-gdkpixbuf-2.0:amd64 (2.34.0-1) ...
  Selecting previously unselected package libgdk-pixbuf2.0-dev.
  Preparing to unpack .../libgdk-pixbuf2.0-dev_2.34.0-1_amd64.deb ...
  Unpacking libgdk-pixbuf2.0-dev (2.34.0-1) ...
  Selecting previously unselected package libjs-highlight.js.
  Preparing to unpack .../libjs-highlight.js_8.2+ds-4_all.deb ...
  Unpacking libjs-highlight.js (8.2+ds-4) ...
  Selecting previously unselected package libjs-jquery.
  Preparing to unpack .../libjs-jquery_1.12.4-1_all.deb ...
  Unpacking libjs-jquery (1.12.4-1) ...
  Selecting previously unselected package libjs-jquery-flot.
  Preparing to unpack .../libjs-jquery-flot_0.8.3+dfsg-1_all.deb ...
  Unpacking libjs-jquery-flot (0.8.3+dfsg-1) ...
  Selecting previously unselected package liblmdb0:amd64.
  Preparing to unpack .../liblmdb0_0.9.18-4_amd64.deb ...
  Unpacking liblmdb0:amd64 (0.9.18-4) ...
  Selecting previously unselected package liblmdb-dev:amd64.
  Preparing to unpack .../liblmdb-dev_0.9.18-4_amd64.deb ...
  Unpacking liblmdb-dev:amd64 (0.9.18-4) ...
  Selecting previously unselected package libmustache-d-dev.
  Preparing to unpack .../libmustache-d-dev_0.1.1-1_amd64.deb ...
  Unpacking libmustache-d-dev (0.1.1-1) ...
  Selecting previously unselected package fontconfig.
  Preparing to unpack .../fontconfig_2.11.0-6.4_amd64.deb ...
  Unpacking fontconfig (2.11.0-6.4) ...
  Selecting previously unselected package libthai-data.
  Preparing to unpack .../libthai-data_0.1.24-2_all.deb ...
  Unpacking libthai-data (0.1.24-2) ...
  Selecting previously unselected package libdatrie1:amd64.
  Preparing to unpack .../libdatrie1_0.2.10-2_amd64.deb ...
  Unpacking libdatrie1:amd64 (0.2.10-2) ...
  Selecting previously unselected package libthai0:amd64.
  Preparing to unpack .../libthai0_0.1.24-2_amd64.deb ...
  Unpacking libthai0:amd64 (0.1.24-2) ...
  Selecting previously unselected package libpango-1.0-0:amd64.
  Preparing to unpack .../libpango-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpango-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libgraphite2-3:amd64.
  Preparing to unpack .../libgraphite2-3_1.3.8-1_amd64.deb ...
  Unpacking libgraphite2-3:amd64 (1.3.8-1) ...
  Selecting previously unselected package libharfbuzz0b:amd64.
  Preparing to unpack .../libharfbuzz0b_1.2.6-2_amd64.deb ...
  Unpacking libharfbuzz0b:amd64 (1.2.6-2) ...
  Selecting previously unselected package libpangoft2-1.0-0:amd64.
  Preparing to unpack .../libpangoft2-1.0-0_1.40.1-1_amd64.deb 

Processed: Re: nfs-common: move of rpc_pipefs mountpoint to /run breaks blkmapd

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #828826 [nfs-common] nfs-common: move of rpc_pipefs mountpoint to /run 
breaks blkmapd
Severity set to 'serious' from 'important'

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

Processed: Bug#830832 marked as pending

[Debian Bug Tracking System]

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

> tag 830832 pending
Bug #830832 {Done: Daniel Echeverry } [hashcat] hashcat: 
FTBFS with dpkg-buildpackage -B
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#830832: marked as pending

[Daniel Echeverry]

tag 830832 pending
thanks

Hello,

Bug #830832 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-security/hashcat.git;a=commitdiff;h=9c13c20

---
commit 9c13c2070981c78c536631aa3a803698891e7463
Author: Daniel Echeverry 
Date:   Mon Jul 11 21:08:12 2016 -0500

Imported Debian patch 3.00-2

diff --git a/debian/changelog b/debian/changelog
index 8330062..372a7e2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+hashcat (3.00-2) unstable; urgency=medium
+
+  * debian/rules
++ Fix FTBFS with dpkg-buildpackage -B (Closes: #830832)
+
+ -- Daniel Echeverry   Mon, 11 Jul 2016 21:08:12 -0500
+
 hashcat (3.00-1) unstable; urgency=medium
 
   * New upstream release.

Bug#830902: openBVE doesn't start

[Elia Argentieri]

Package: openbve
Version: 1.4.0.10-3
Severity: grave

Dear maintainer,

I installed openBVE, but it doesn't start. It just prints these lines in a 
terminal and nothing more happens.
The only thing to do is CTRL+C.

libpng error: invalid after png_start_read_image or png_read_update_info
libpng error: invalid after png_start_read_image or png_read_update_info
libpng error: invalid after png_start_read_image or png_read_update_info
System.ArgumentNullException: Value cannot be null.
Parameter name: value
  at System.Windows.Forms.ImageList+ImageCollection+ImageListItem..ctor 
(System.Drawing.Image value) <0x419f73f0 + 0x00157> in :0 
  at System.Windows.Forms.ImageList+ImageCollection.Add (System.String key, 
System.Drawing.Image image) <0x419f7380 + 0x0003b> in :0 
  at OpenBve.formMain.formMain_Load (System.Object sender, System.EventArgs e) 
<0x419eae80 + 0x04fc3> in :0 
  at System.Windows.Forms.Form.OnLoad (System.EventArgs e) <0x419eacb0 + 
0x00071> in :0 
  at System.Windows.Forms.Form.OnLoadInternal (System.EventArgs e) <0x419eaa90 
+ 0x0007f> in :0 


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (800, 'testing'), (200, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages openbve depends on:
ii  libmono-corlib4.5-cil4.2.1.102+dfsg2-8
ii  libmono-i18n4.0-all  4.2.1.102+dfsg2-8
ii  libmono-system-drawing4.0-cil4.2.1.102+dfsg2-8
ii  libmono-system-windows-forms4.0-cil  4.2.1.102+dfsg2-8
ii  libmono-system4.0-cil4.2.1.102+dfsg2-8
ii  libtaoframework-openal1.1-cil2.1.svn20090801-14
ii  libtaoframework-opengl3.0-cil2.1.svn20090801-14
ii  libtaoframework-sdl1.2-cil   2.1.svn20090801-14
ii  mono-runtime 4.2.1.102+dfsg2-8
ii  openbve-data 1.4.0.10+dfsg-1

Versions of packages openbve recommends:
pn  bve-route  
pn  bve-train  

openbve suggests no packages.

-- no debconf information

Bug#826896: xul-ext-noscript: incompatible with firefox-esr in jessie

[Rebecca N. Palmer]

Is this going to get a stable update (as previously suggested)?

On 11/06/16 08:04, Rebecca N. Palmer wrote:

a no-change rebuild of the sid
(2.9.0.11-1) source in jessie fixes the problem.[...]Such updates have
previously been allowed in stable: see #744730.)

Bug#829549: marked as done (libmoox-options-perl: FTBFS: Failed 2/31 test programs. 2/156 subtests failed.)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 18:34:59 +
with message-id 
and subject line Bug#829549: fixed in libmoox-options-perl 4.022-2
has caused the Debian Bug report #829549,
regarding libmoox-options-perl: FTBFS: Failed 2/31 test programs. 2/156 
subtests failed.
to be marked as done.

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

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


-- 
829549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmoox-options-perl
Version: 4.022-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,

libmoox-options-perl fails to build from source in unstable/amd64:

  [..]

  ok 5 - only one missing for moose
  1..5
  ok 5 - test required
  # Subtest: test help
  # test help
  ok 1 - help, exit 0
  ok 2 - str_reg is missing
  1..2
  ok 6 - test help
  # Subtest: test short help
  # test short help
  ok 1 - help, exit 0
  ok 2 - str_reg is missing
  ok 3 - usage message ok
  1..3
  ok 7 - test short help
  # Subtest: value override
  # value override
  ok 1 - str req is ok
  ok 2 - str req is override with ok
  1..2
  ok 8 - value override
  # Subtest: split_complexe_str
  # split on complexe str
  ok 1 - str req is ok
  ok 2 - str req is ok
  ok 3 - str req is ok
  ok 4 - str req is ok
  ok 5 - str req is ok
  ok 6 - str req is ok
  ok 7 - str req is ok
  ok 8 - str req is ok
  1..8
  ok 9 - split_complexe_str
  # Subtest: split_complexe_str_short
  # split on complexe str short
  ok 1 - str req is ok
  ok 2 - str req is ok
  ok 3 - str req is ok
  ok 4 - str req is ok
  1..4
  ok 10 - split_complexe_str_short
  # Subtest: split_str_shorter_name
  # shorter long split
  ok 1 - str req is ok
  ok 2 - str req is ok
  # shorter long split with conflict
  ok 3 - conflict detected
  ok 4 - conflict detected
  1..4
  ok 11 - split_str_shorter_name
  # Subtest: should_die_ok
  # Test chain method
  ok 1 - should die ok
  1..1
  ok 12 - should_die_ok
  # Subtest: test usage
  # test usage method
  ok 1 - exit code is correct
  ok 2 - custom message is present
  ok 3 - custom message is really present
  ok 4 - help is present
  ok 5 - attr no doc is present
  1..5
  ok 13 - test usage
  # Subtest: test short usage
  # test usage method
  ok 1 - exit code is correct
  ok 2 - short message ok
  1..2
  ok 14 - test short usage
  # Subtest: doc usage
  # doc usage
  ok 1 - exit code is correct
  ok 2 - doc on attribute
  1..2
  ok 15 - doc usage
  # Subtest: test short
  # test short
  ok 1 - short doc ok
  1..1
  ok 16 - test short
  # Subtest: test skip_options
  # test skip_options
  ok 1 - multi is no more an option
  1..1
  ok 17 - test skip_options
  # Subtest: test prefer_commandline
  # test prefer_commandline
  ok 1 - prefer_commandline ok
  1..1
  ok 18 - test prefer_commandline
  # Subtest: test dash
  # test dash
  ok 1 - --start_date ok
  ok 2 - --start-date ok
  ok 3 - -s ok
  1..3
  ok 19 - test dash
  # Subtest: json
  # json
  ok 1 - json properly set
  ok 2 - decode json failed
  ok 3 - json help message properly set
  # USAGE: moose.t [-ht] [long options...]
  # 
  # -t: JSON
  # no doc for t
  # 
  # 
  
  # 
  # --usage:
  # show a short help message
  # 
  # -h:
  # show a compact help message
  # 
  # --help:
  # show a long help message
  # 
  # --man:
  # show the manual
  # 
  ok 4 - json help message properly set
   

Bug#808433: nethogs STILL crashes in STABLE (Jessie), two months after bug was closed

[S. G.]

Agreed! Thanks for the backports package.

Am Dienstag, den 12.07.2016, 10:14 +0200 schrieb Luca Capello:
> fixed 808433 0.8.1-1~bpo8+1
> user product...@infomaniak.com
> usertag 808433 + infomaniak.com-network
> thanks
> 
> Hi there,
> 
> On Sun, 12 Jun 2016 10:01:20 +0200, S. G. wrote:
> > I'm desparately waiting to see this fix in jessie.
> > 
> > Is there a schedule for patching 0.8.0?
> 
> No need for a jessie-pu, the problem is fixed for us using the
> jessie-backports package (bug updated).
> 
> Thx, bye,
> Gismo / Luca
> 

Bug#829188: SEGVs too frequently (~every other day)

[Carsten Schoenert]

Hello Tony,

On Tue, Jul 12, 2016 at 03:47:27PM +0100, Tony Houghton wrote:
> I've also been experiencing frequent crashes with version 4x. I'm not
> sure, but it seems to occur just after it's opened and displayed a
> message. One particular message has just triggered a crash twice in a
> row, but not every time I open it; it's multipart html+text but with no
> images.
> 
> I recently got around to hacking up a start-up wrapper and the desktop
> file to enable core dumps. It's quite a big file so I've uploaded it to
> .

this file is not available (any longer).

The information on how to get a "valid" backtrace can be found in the
Debian Wiki. Please do a log by the way described in the wiki.

  https://wiki.debian.org/Icedove#Debugging

BTW: The current 42.0~b1-1 isn't crashed here for a long time, so I'd be
 interessted in a GDB log to see there the crashes happen.

Regards
Carsten

Processed: Re: Bug#828036: glfw: do not ship with stretch

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #828036 [src:glfw] glfw: do not ship with stretch
Bug reassigned from package 'src:glfw' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #828036 to the same values 
previously set
Ignoring request to alter fixed versions of bug #828036 to the same values 
previously set
> severity -1 normal
Bug #828036 [ftp.debian.org] glfw: do not ship with stretch
Severity set to 'normal' from 'serious'
> tags -1 - sid stretch
Bug #828036 [ftp.debian.org] glfw: do not ship with stretch
Removed tag(s) sid and stretch.
> retitle -1 RM: glfw -- ROM; dead upstream, superseded by glfw3
Bug #828036 [ftp.debian.org] glfw: do not ship with stretch
Changed Bug title to 'RM: glfw -- ROM; dead upstream, superseded by glfw3' from 
'glfw: do not ship with stretch'.

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

Bug#828036: glfw: do not ship with stretch

[James Cowgill]

Control: reassign -1 ftp.debian.org
Control: severity -1 normal
Control: tags -1 - sid stretch
Control: retitle -1 RM: glfw -- ROM; dead upstream, superseded by glfw3

Hi,

Now that all the reverse dependencies of glfw have been ported to
glfw3, the package can be removed from unstable.

James

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

Bug#830886: ffmpeg FTBFS for mips64el on configure

[Sebastian Ramacher]

Control: severity -1 important
Control: reassign -1 src:ffmpeg 7:3.1.1-1
Control: forcemerge 830868 -1
Control: found -1 7:3.0.2-1

On 2016-07-12 17:00:08, Dejan Latinovic wrote:
> Package: ffmpeg
> Version: 7:3.0.2-1
> Severity: serious

How is it serious? ffmpeg was never available in stretch in mips64el.

> Tags: sid, patch
> Justification: FTBFS
> User: debian-m...@lists.debian.org
> Usertags: mips-patch
> 
> 
> Package ffmpeg FTBFS for mips64el on configure with the following error:
> > ERROR: LoadLibrary/dlopen not found for avisynth
> 
> Error message from config.log:
> > /usr/bin/ld: /tmp/ffconf.09oJ6qCG.o: linking -mnan=2008 module with 
> > previous -mnan=legacy modules
> > /usr/bin/ld: failed to merge target specific data of file 
> > /tmp/ffconf.09oJ6qCG.o
> > collect2: error: ld returned 1 exit status

Please check existing bug reports before filing new ones. Thanks

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#830886: ffmpeg FTBFS for mips64el on configure

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #830886 {Done: James Cowgill } [ffmpeg] ffmpeg FTBFS 
for mips64el on configure
Severity set to 'important' from 'serious'
> reassign -1 src:ffmpeg 7:3.1.1-1
Bug #830886 {Done: James Cowgill } [ffmpeg] ffmpeg FTBFS 
for mips64el on configure
Bug reassigned from package 'ffmpeg' to 'src:ffmpeg'.
No longer marked as found in versions ffmpeg/7:3.0.2-1.
No longer marked as fixed in versions 7:3.1.1-2.
Bug #830886 {Done: James Cowgill } [src:ffmpeg] ffmpeg 
FTBFS for mips64el on configure
Marked as found in versions ffmpeg/7:3.1.1-1.
> forcemerge 830868 -1
Bug #830868 {Done: Sebastian Ramacher } [src:ffmpeg] 
ffmpeg: FTBFS on mips64el: fatal error: gnu/stubs-n64_hard_2008.h: No such file 
or directory
Bug #830868 {Done: Sebastian Ramacher } [src:ffmpeg] 
ffmpeg: FTBFS on mips64el: fatal error: gnu/stubs-n64_hard_2008.h: No such file 
or directory
Added tag(s) sid.
Bug #830886 {Done: James Cowgill } [src:ffmpeg] ffmpeg 
FTBFS for mips64el on configure
The source ffmpeg and version 7:3.1.1-2 do not appear to match any binary 
packages
Marked as fixed in versions ffmpeg/7:3.1.1-2.
Merged 830868 830886
> found -1 7:3.0.2-1
Bug #830886 {Done: James Cowgill } [src:ffmpeg] ffmpeg 
FTBFS for mips64el on configure
Bug #830868 {Done: Sebastian Ramacher } [src:ffmpeg] 
ffmpeg: FTBFS on mips64el: fatal error: gnu/stubs-n64_hard_2008.h: No such file 
or directory
Marked as found in versions ffmpeg/7:3.0.2-1.
Marked as found in versions ffmpeg/7:3.0.2-1.

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

Processed: the evil mail client strikes again

[Debian Bug Tracking System]

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

> fixed 830886 7:3.1.1-2
Bug #830886 {Done: James Cowgill } [ffmpeg] ffmpeg FTBFS 
for mips64el on configure
There is no source info for the package 'ffmpeg' at version '7:3.1.1-2' with 
architecture ''
Unable to make a source version for version '7:3.1.1-2'
Marked as fixed in versions 7:3.1.1-2.
> thanks
Stopping processing here.

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

Bug#830886: marked as done (ffmpeg FTBFS for mips64el on configure)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 18:06:22 +0100
with message-id <1468343182.7439.16.ca...@debian.org>
and subject line Re: Bug#830886: ffmpeg FTBFS for mips64el on configure
has caused the Debian Bug report #830886,
regarding ffmpeg FTBFS for mips64el on configure
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.)


-- 
830886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ffmpeg
Version: 7:3.0.2-1
Severity: serious
Tags: sid, patch
Justification: FTBFS
User: debian-m...@lists.debian.org
Usertags: mips-patch


Package ffmpeg FTBFS for mips64el on configure with the following error:
> ERROR: LoadLibrary/dlopen not found for avisynth

Error message from config.log:
> /usr/bin/ld: /tmp/ffconf.09oJ6qCG.o: linking -mnan=2008 module with previous 
> -mnan=legacy modules
> /usr/bin/ld: failed to merge target specific data of file 
> /tmp/ffconf.09oJ6qCG.o
> collect2: error: ld returned 1 exit status

The reason for that is usage of -mips64r6 flag that triggers -mnan=200 flag.

Solution is to disable mips64r6 in debian rules.
Patch that includes this fix is attached.

I will rebuild locally latest ffmpeg version (7:3.1.1-1) for 
mips/mipsel/mips64el to confirm that patch fixes mips64el and does not break 
mips/mipsel.

Regards,
Dejandiff -uNr debian.orig/rules debian/rules
--- debian.orig/rules	2016-07-12 02:53:53.0 +0200
+++ debian/rules	2016-07-12 18:47:04.548881017 +0200
@@ -169,7 +169,8 @@
 	CONFIG += --disable-mipsdsp \
 		--disable-mipsdspr2 \
 		--disable-loongson3 \
-		--disable-mips32r6
+		--disable-mips32r6 \
+		--disable-mips64r6
 endif
 ifneq (,$(filter $(DEB_HOST_ARCH),mips mipsel))
 	CONFIG += --disable-mipsfpu
--- End Message ---
--- Begin Message ---
Version: 7:3.1.1-2

On Tue, 2016-07-12 at 17:00 +, Dejan Latinovic wrote:
> Package: ffmpeg
> Version: 7:3.0.2-1
> Severity: serious
> Tags: sid, patch
> Justification: FTBFS
> User: debian-m...@lists.debian.org
> Usertags: mips-patch
> 
> 
> Package ffmpeg FTBFS for mips64el on configure with the following
> error:
> > ERROR: LoadLibrary/dlopen not found for avisynth
[...]
> Solution is to disable mips64r6 in debian rules.
> Patch that includes this fix is attached.
> 
> I will rebuild locally latest ffmpeg version (7:3.1.1-1) for
> mips/mipsel/mips64el to confirm that patch fixes mips64el and does
> not break mips/mipsel.

Too slow! It was fixed earlier today:

ffmpeg (7:3.1.1-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Aurelien Jarno ]
   * debian/rules: Fix FTBFS on mips64el by adding --disable-mips64r6.
(Closes: #830868)

James

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

Bug#830886: ffmpeg FTBFS for mips64el on configure

[Dejan Latinovic]

Package: ffmpeg
Version: 7:3.0.2-1
Severity: serious
Tags: sid, patch
Justification: FTBFS
User: debian-m...@lists.debian.org
Usertags: mips-patch


Package ffmpeg FTBFS for mips64el on configure with the following error:
> ERROR: LoadLibrary/dlopen not found for avisynth

Error message from config.log:
> /usr/bin/ld: /tmp/ffconf.09oJ6qCG.o: linking -mnan=2008 module with previous 
> -mnan=legacy modules
> /usr/bin/ld: failed to merge target specific data of file 
> /tmp/ffconf.09oJ6qCG.o
> collect2: error: ld returned 1 exit status

The reason for that is usage of -mips64r6 flag that triggers -mnan=200 flag.

Solution is to disable mips64r6 in debian rules.
Patch that includes this fix is attached.

I will rebuild locally latest ffmpeg version (7:3.1.1-1) for 
mips/mipsel/mips64el to confirm that patch fixes mips64el and does not break 
mips/mipsel.

Regards,
Dejandiff -uNr debian.orig/rules debian/rules
--- debian.orig/rules	2016-07-12 02:53:53.0 +0200
+++ debian/rules	2016-07-12 18:47:04.548881017 +0200
@@ -169,7 +169,8 @@
 	CONFIG += --disable-mipsdsp \
 		--disable-mipsdspr2 \
 		--disable-loongson3 \
-		--disable-mips32r6
+		--disable-mips32r6 \
+		--disable-mips64r6
 endif
 ifneq (,$(filter $(DEB_HOST_ARCH),mips mipsel))
 	CONFIG += --disable-mipsfpu

Bug#817708: uml-utilities marked for removal

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Mattia,

I just got back home from DebConf.

On Wed, 2016-07-06 at 07:05 -0700, Mattia Dongili wrote:
> > 
> > Are there any plans for fixing it ?
> 
> No. At the moment it doesn't make much sense to keep uml-utilities in
> the archive. Even if/when UML is re-added, it should be considered
> whether uml-utilities are all that useful.
> 

Okay! So in that case I'll demote uml-utilities to a Recommends/Suggests.

> > PS: I'm trying to bring back user-mode-linux back into the archive. So any
> help
> > on retaining uml-utilities in the archive will be nice.
> 
> Thanks for doing that. I'd like to say that I'm trying too, but
> effectively I have a lot of ideas but very little time to go after them.
> Specifically, the biggest problem I had with the previous packaging was
> that it required too much maintenance burden. UML should be one of the
> artifacts created by the regular Debian kernel builds.

Yes. I do remember you talking about it in our last email conversation. First,
I'll work on uml this week, to get it back in the archive. And then later I'll
see how best to integrate it into debian-kernel.

PS: And I just noticed you did some work with uml-utilities. Thanks.


- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXhRrbAAoJEKY6WKPy4XVpmScP/3RplgXlOxvyQ68Ff4NI6zGv
FilFteOwRRKSzI6SESR21IfRrkNEh8wg27sRO8LMtLOT7X5o5yQ19N6kEmEZ042t
mDa/de17NFR5tCFSyarLjrxNYMntpr25bPLUk2msqNtnaRC27/05SQIbP2BI54i6
EJRNKMU+s/wmAJ+THx3yCatEd7Wpq2eg/t/P9T/2yBMIQ5HpNciRJdLoysQmkkFr
gFxtN7lXEgigr2ogaUNucdnTkalQZOQrmxr765yYXZlOZXKY0y6GLW7Len/X9R9W
V8SJalDjjBlTFb0kmWNTeZ6H4I+2oW5aop87jV12z6fOzYTokssLcjYFxNHUmuI1
PeUrEuChcXtxYsa15phu4xkfI0RSRjY5DelW1/pMRbYAOMPbLIgGRnwcA/dx542v
Fe9YZRvWGaJVJMU/3WHTr3hf4ZQJDYhdxspW85c1PVfDC0oO5wicRMXqeH7KM1IQ
UlXLQiNsuYMBm+c5P6HIUkB0afxSjTjTH/2OvgPBKw3wVt4hjDsmoVOTGTHSeQoi
j4xTg3oEVNKkgQhe3ZkTqGJjnb3hI+o9xXC9bvfw+EkVCTsFHHQ4+hOs5UMfVOKq
DJhGboAO93UCdqqwxFbSsNY1EXF/0OyRu/BUOBPZlzMUm5rpO2R5ExpPZ9yn8TKP
6wp7I2GxSo8p/TfTNqiJ
=oPea
-END PGP SIGNATURE-

Bug#830611: marked as done (python-webob: accesses the internet during build)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 16:21:15 +
with message-id 
and subject line Bug#830611: fixed in python-webob 1.6.1-1
has caused the Debian Bug report #830611,
regarding python-webob: accesses the internet during build
to be marked as done.

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

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


-- 
830611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-webob
Version: 1.6.0-1
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst python-webob builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

  00:00:00.00 IP b229d4e7eb4f.41020 > dnscache.uct.ac.za.domain: 47638+ A? 
docs.python.org. (33)
  00:00:00.44 IP b229d4e7eb4f.41020 > dnscache.uct.ac.za.domain: 45630+ 
? docs.python.org. (33)
  00:00:00.300030 IP dnscache.uct.ac.za.domain > b229d4e7eb4f.41020: 47638 
3/4/4 CNAME python.map.fastly.net., CNAME prod.python.map.fastlylb.net., A 
151.101.16.223 (259)
  00:00:00.300390 IP dnscache.uct.ac.za.domain > b229d4e7eb4f.41020: 45630 
2/1/0 CNAME python.map.fastly.net., CNAME prod.python.map.fastlylb.net. (178)
  00:00:00.300785 IP b229d4e7eb4f.34476 > 151.101.16.223.https: Flags [S], seq 
4147157445, win 29200, options [mss 1460,sackOK,TS val 110406334 ecr 
0,nop,wscale 7], length 0
  00:00:00.452034 IP 151.101.16.223.https > b229d4e7eb4f.34476: Flags [S.], seq 
2817875647, ack 4147157446, win 28560, options [mss 1440,sackOK,TS val 
1720332837 ecr 110406334,nop,wscale 9], length 0

  [..]

This appears to be caused by (at least) Sphinx's intersphinx mapping extension.
Please see #830186 for more information, including suggestions on how to fix it.

The full build log (including tcpdump output) is attached.


Regards,

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


python-webob.1.6.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-webob
Source-Version: 1.6.1-1

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

Debian distribution maintenance software
pp.
Barry Warsaw  (supplier of updated python-webob package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 12 Jul 2016 11:14:11 -0400
Source: python-webob
Binary: python-webob python3-webob python-webob-doc
Architecture: source all
Version: 1.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Barry Warsaw 
Changed-By: Barry Warsaw 
Description:
 python-webob - Python module providing WSGI request and response objects 
(Python
 python-webob-doc - Python module providing WSGI request and response objects 
(docume
 python3-webob - Python module providing WSGI request and response objects 
(Python
Closes: 830611
Changes:
 python-webob (1.6.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * d/patches/intersphinx-local.patch: Use local documentation for
 intersphinx, preventing build-time access to the internet.
 (Closes: #830611)
   * d/rules: Build the Sphinx documentation under the
 override_dh_sphinxdoc rule rather than override_dh_installdocs.
   * d/control:
 - Add dependencies to python-doc and python3-doc for local intersphinx
   links.
 - Bump Standards-Version with no other changes needed.
 - wrap-and-sort
   * d/tests: Remove, since autodep8 will do these tests for us.
Checksums-Sha1:
 7ac03e57e59e80d14b0ab814ecd688ed8d408e01 2395 python-webob_1.6.1-1.dsc
 b815ba45ea172c87a89fd4a21a27523200d45e83 204676 python-webob_1.6.1.orig.tar.gz
 3e04e9f48fd760fc1e1be0d284b1657f038f5332 5252 
python-webob_1.6.1-1.debian.tar.xz
 80ba8f793f16ce2e1e0c7b79aee7c4d83743daa5 153372 
python-webob-doc_1.6.1-1_all.deb
 b40f03eaab2b28902cf90aaf1097141da870a64e 63266 python-webob_1.6.1-1_all.deb
 

Bug#818193: marked as done (aaphoto: Jasper removal)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 16:05:04 +
with message-id 
and subject line Bug#818193: fixed in aaphoto 0.45-1
has caused the Debian Bug report #818193,
regarding aaphoto: Jasper removal
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.)


-- 
818193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aaphoto
Severity: important
User: j...@debian.org
Usertags: jasper-rm

Hi, jasper will be removed from Debian for the stretch release (and
following that, the archive in general).

It's been unmaintained for nearly a decade, please als see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812630

Your package uses jasper, so please either remove the JPEG2000
functionality or move to a supported implementation (e.g. openjpeg or
ffmpeg).

A removal tracker has been setup by the release team at
https://release.debian.org/transitions/html/jasper-rm.html

This bug will be bumped to release-critical status in a few weeks.

Cheers,

Moritz 
--- End Message ---
--- Begin Message ---
Source: aaphoto
Source-Version: 0.45-1

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

Debian distribution maintenance software
pp.
Denis Briand  (supplier of updated aaphoto package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 10 Jul 2016 13:38:19 +0200
Source: aaphoto
Binary: aaphoto
Architecture: source amd64
Version: 0.45-1
Distribution: unstable
Urgency: low
Maintainer: Denis Briand 
Changed-By: Denis Briand 
Description:
 aaphoto- Auto Adjust Photo, automatic color correction of photos
Closes: 818193
Changes:
 aaphoto (0.45-1) unstable; urgency=low
 .
   * New upstream release (Closes: #818193).
   * Remove libjasper-dev build dependency.
   * Remove merged patches:
   + 01_fix-Makefile.patch
   + 02_modernize-configure.patch
   * Simplify and update debian/copyright file.
   * Fix spelling error in manpage.
   * Fix a segmentation fault with libpng 1.6
   * Bump standards version to 3.9.8
Checksums-Sha1:
 ff8c3f79e1898dd3e7372eb8df247705826c8ce7 1737 aaphoto_0.45-1.dsc
 d8a0b9a0d46b4302c03e04b91adc443eeca51632 134605 aaphoto_0.45.orig.tar.gz
 9a1939e1ca426efc12033eb6a8515ebe78336fab 4608 aaphoto_0.45-1.debian.tar.xz
 f62405e35fbb5f4c88cc4b9366d433d686b43dac 64016 aaphoto-dbgsym_0.45-1_amd64.deb
 162a180ff3ca7a3e0f2165cab8887251dd1d 42718 aaphoto_0.45-1_amd64.deb
Checksums-Sha256:
 1d02c3a4698fa53591cd15236a50c93430b65f6cdc10349ff0c20e45fbfa6af2 1737 
aaphoto_0.45-1.dsc
 3dc12ba310439186b8b9e11e449e1a90d5534cae02afae53e7df09df78b97bee 134605 
aaphoto_0.45.orig.tar.gz
 28b5d92ab8bad90df42eafe98a1a40b698d74b263bf586cb9f565065a632b03f 4608 
aaphoto_0.45-1.debian.tar.xz
 348cb04580284af8f09033c9d474b279f3cf236280a166b407ddae3924aed732 64016 
aaphoto-dbgsym_0.45-1_amd64.deb
 1fa0c9d6863cd7b89a8c32fb522e67c58cb35b5cbd76e5d645dd209ddb3c82b0 42718 
aaphoto_0.45-1_amd64.deb
Files:
 b0f63edb10dbeac8b7d80aff2cf56b68 1737 graphics optional aaphoto_0.45-1.dsc
 d4db3edd217e3f523c4e006f2d2e9502 134605 graphics optional 
aaphoto_0.45.orig.tar.gz
 f8a5706b2e8bbb5437942afca92645a2 4608 graphics optional 
aaphoto_0.45-1.debian.tar.xz
 0ca95fb8ec804785a48194f7d1db087c 64016 debug extra 
aaphoto-dbgsym_0.45-1_amd64.deb
 acd7f1f439c94239b33e39b115cf3b86 42718 graphics optional 
aaphoto_0.45-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXhPV8AAoJEN7oBD7hfrswBDIQAJDv3GtnFVB+VE8qw5LUeKRH
rVylRcML4Yq9Ap1zJxOnFzkNQvb9EFaIx1g8E5ywMQD1Sm4PbQMXBsq4VTg/sItg
v/7vXtUobtxV27eNligeJGso9yYz5XSBV0D56eQ4oixRr4dTMjNXNQdtDGS5Y2kJ
cFx06wlq8QU/lTv/raecxpTHR5r4c3gGve9xdFflMCDLi3ap5t1dBYvx6E98iyJn
oNFdSUesNGD+GMy5EglTxCv8EC1EpqBQuOhMa3WD6upJp9gisF+hLEjcMCvOHFpZ
hDxSMm2PSubaM0kkPcIvMDNIlrRqbbPwl5h+A7eE0Bf1v4BEj6sAfT+R3EDV0YDH
EilNgXbWYTWqQwr1AipPVPbIxHZjJKpy49X9+0ijDPEueEamT2Jhp1fmgg9vyR4t
O1KXPQJ7lvi4onP5262+pkPiZDF18owyZKTNSJ6M7gftiJ6kG7YAMcDkOVEwmTO6

Processed: limit source to audit, tagging 829500, tagging 830244

[Debian Bug Tracking System]

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

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

> tags 829500 + pending
Bug #829500 [libaudit-dev] undefined reference to `capng_have_capability'
Added tag(s) pending.
> tags 830244 + pending
Bug #830244 [auditd] auditd: Crash at startup
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#821795: lttng-modules-dkms: module FTBFS in jessie against Linux 3.16: error: conflicting types for 'trace_mm_page_alloc_extfrag'

[Jon Bernard]

* Michael Jeanson  wrote:
> Hi Jon,
> 
> Here is an updated debdiff, it works on a fully updated jessie. Should
> we track these updates in a branch of the collab-maint repo?

Excellent, thanks.  This patch works and I've put it into a dedicated
stable branch 'jessie' so this will be easier to track.

In looking at the stable update procedure, I need to request permission
to submit an update and I wonder: would it be more valuable to update
our Jessie version (2.5.1) to the latest supported stable version
upstream (2.5.6) and rebase these patches on that version?  Give that
upstream supports a stable branch (which I think is unusual, but very
awesome), this looks like a compelling approach.

Thoughts?

-- 
Jon

Bug#829481: marked as done (python-bioblend: FTBFS: make[2]: sphinx-build: Command not found)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 16:52:38 +0200
with message-id 

Bug#829188: SEGVs too frequently (~every other day)

[Tony Houghton]

Package: icedove
Version: 1:45.2~b1-1
Followup-For: Bug #829188

I've also been experiencing frequent crashes with version 4x. I'm not
sure, but it seems to occur just after it's opened and displayed a
message. One particular message has just triggered a crash twice in a
row, but not every time I open it; it's multipart html+text but with no
images.

I recently got around to hacking up a start-up wrapper and the desktop
file to enable core dumps. It's quite a big file so I've uploaded it to
.

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

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

Versions of packages icedove depends on:
ii  debianutils   4.8
ii  fontconfig2.11.0-6.4
ii  libasound21.1.1-2
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.22-13
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.8-1
ii  libdbus-glib-1-2  0.106-1
ii  libevent-2.0-52.0.21-stable-2+b1
ii  libffi6   3.2.1-4
ii  libfontconfig12.11.0-6.4
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.1.1-8
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.48.1-1
ii  libgtk2.0-0   2.24.30-2
ii  libhunspell-1.4-0 1.4.1-2
ii  libicu55  55.1-7
ii  libnspr4  2:4.12-2
ii  libnss3   2:3.23-2
ii  libpango-1.0-01.40.1-1
ii  libpangocairo-1.0-0   1.40.1-1
ii  libpangoft2-1.0-0 1.40.1-1
ii  libpixman-1-0 0.33.6-1
ii  libsqlite3-0  3.13.0-1
ii  libstartup-notification0  0.12-4
ii  libstdc++66.1.1-8
ii  libvpx3   1.5.0-3
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.2-1
ii  libxrender1   1:0.9.9-2
ii  libxt61:1.1.5-1
ii  psmisc22.21-2.1+b1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages icedove recommends:
ii  hunspell-en-gb [hunspell-dictionary]  1:5.1.3-2
ii  hunspell-en-us [hunspell-dictionary]  20070829-6
ii  iceowl-extension  1:45.2~b1-1

Versions of packages icedove suggests:
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.14.2+dfsg-1

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/applications/icedove.desktop (from icedove 
package)

Bug#825804: marked as done (ruby-notify and pdns-tools: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 16:44:36 +0200
with message-id <20160712144435.GA768@tn>
and subject line Re: #825804: ruby-notify and pdns-tools: error when trying to 
install together
has caused the Debian Bug report #825804,
regarding ruby-notify and pdns-tools: error when trying to install together
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.)


-- 
825804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pdns-tools,ruby-notify
Version: pdns-tools/4.0.0~alpha3-1
Version: ruby-notify/0.5.2-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-05-30
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:



Extracting templates from packages: 76%
Extracting templates from packages: 100%
Preconfiguring packages ...
Selecting previously unselected package libffi6:amd64.
(Reading database ... 10961 files and directories currently installed.)
Preparing to unpack .../libffi6_3.2.1-4_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-4) ...
Selecting previously unselected package libglib2.0-0:amd64.
Preparing to unpack .../libglib2.0-0_2.48.1-1_amd64.deb ...
Unpacking libglib2.0-0:amd64 (2.48.1-1) ...
Selecting previously unselected package libjpeg62-turbo:amd64.
Preparing to unpack .../libjpeg62-turbo_1%3a1.4.2-2_amd64.deb ...
Unpacking libjpeg62-turbo:amd64 (1:1.4.2-2) ...
Selecting previously unselected package libpng16-16:amd64.
Preparing to unpack .../libpng16-16_1.6.21-5_amd64.deb ...
Unpacking libpng16-16:amd64 (1.6.21-5) ...
Selecting previously unselected package libjbig0:amd64.
Preparing to unpack .../libjbig0_2.1-3.1_amd64.deb ...
Unpacking libjbig0:amd64 (2.1-3.1) ...
Selecting previously unselected package libtiff5:amd64.
Preparing to unpack .../libtiff5_4.0.6-1_amd64.deb ...
Unpacking libtiff5:amd64 (4.0.6-1) ...
Selecting previously unselected package libxau6:amd64.
Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ...
Unpacking libxau6:amd64 (1:1.0.8-1) ...
Selecting previously unselected package libxdmcp6:amd64.
Preparing to unpack .../libxdmcp6_1%3a1.1.2-1.1_amd64.deb ...
Unpacking libxdmcp6:amd64 (1:1.1.2-1.1) ...
Selecting previously unselected package libxcb1:amd64.
Preparing to unpack .../libxcb1_1.11.1-1_amd64.deb ...
Unpacking libxcb1:amd64 (1.11.1-1) ...
Selecting previously unselected package libx11-data.
Preparing to unpack .../libx11-data_2%3a1.6.3-1_all.deb ...
Unpacking libx11-data (2:1.6.3-1) ...
Selecting previously unselected package libx11-6:amd64.
Preparing to unpack .../libx11-6_2%3a1.6.3-1_amd64.deb ...
Unpacking libx11-6:amd64 (2:1.6.3-1) ...
Selecting previously unselected package gcc-6-base:amd64.
Preparing to unpack .../gcc-6-base_6.1.1-4_amd64.deb ...
Unpacking gcc-6-base:amd64 (6.1.1-4) ...
Processing triggers for libc-bin (2.22-9) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up gcc-6-base:amd64 (6.1.1-4) ...
(Reading database ... 11316 files and directories currently installed.)
Preparing to unpack .../libstdc++6_6.1.1-4_amd64.deb ...
Unpacking libstdc++6:amd64 (6.1.1-4) over (4.8.2-19) ...
Processing triggers for libc-bin (2.22-9) ...
Setting up libstdc++6:amd64 (6.1.1-4) ...
Processing triggers for libc-bin (2.22-9) ...
Selecting previously unselected package libicu55:amd64.
(Reading database ... 11330 files and directories currently installed.)
Preparing to unpack .../libicu55_55.1-7_amd64.deb ...
Unpacking libicu55:amd64 (55.1-7) ...
Selecting previously unselected package libxml2:amd64.
Preparing to unpack .../libxml2_2.9.3+dfsg1-1_amd64.deb ...
Unpacking libxml2:amd64 (2.9.3+dfsg1-1) ...
Selecting previously unselected package shared-mime-info.
Preparing to unpack .../shared-mime-info_1.6-1_amd64.deb ...
Unpacking shared-mime-info (1.6-1) ...
Selecting previously unselected package libgdk-pixbuf2.0-common.
Preparing to unpack .../libgdk-pixbuf2.0-common_2.34.0-1_all.deb ...
Unpacking libgdk-pixbuf2.0-common (2.34.0-1) ...
Selecting previously unselected package libgdk-pixbuf2.0-0:amd64.
Preparing to unpack .../libgdk-pixbuf2.0-0_2.34.0-1_amd64.deb ...
Unpacking libgdk-pixbuf2.0-0:amd64 (2.34.0-1) ...
Selecting previously unselected package libnotify4:amd64.
Preparing to unpack .../libnotify4_0.7.6-2_amd64.deb ...
Unpacking libnotify4:amd64 (0.7.6-2) ...
Selecting previously unselected package libyaml-0-2:amd64.
Preparing to unpack .../libyaml-0-2_0.1.6-3_amd64.deb ...

Processed: fixed 825804 in 4.0.0-1

[Debian Bug Tracking System]

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

> fixed 825804 4.0.0-1
Bug #825804 [pdns-tools] ruby-notify and pdns-tools: error when trying to 
install together
Marked as fixed in versions pdns/4.0.0-1.
> thanks
Stopping processing here.

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

Bug#794815: marked as done (FTBFS because go generate is missing a build dependency... and then some.)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 10:38:52 -0400
with message-id 

Bug#830743: marked as done (mypy: FTBFS: error: invalid Python installation: unable to open /usr/lib/python3.5/config-3.5m-x86_64-linux-gnu/Makefile)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 10:33:50 -0400
with message-id 

Bug#830337: marked as done (vmware-nsx: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 14:00:19 +
with message-id 
and subject line Bug#830337: fixed in vmware-nsx 8.0.0-2
has caused the Debian Bug report #830337,
regarding vmware-nsx: FTBFS: Tests failures
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> module = self._get_module_from_name(name)
>   File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
> _get_module_from_name
> __import__(name)
>   File "vmware_nsx/tests/unit/services/l2gateway/test_nsxv_driver.py", line 
> 19, in 
> from neutron.tests import base
>   File "/usr/lib/python2.7/dist-packages/neutron/tests/base.py", line 34, in 
> 
> from oslotest import base
> ImportError: No module named oslotest
> 
> 
> --
> Ran 72 tests in 1.334s
> 
> FAILED (failures=36)
> make[1]: *** [override_dh_auto_test] Error 1
> debian/rules:13: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/vmware-nsx_1.0.0-1_unstable_reb.normal.log

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

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

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

Debian distribution maintenance software
pp.
James Page  (supplier of updated vmware-nsx 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, 11 Jul 2016 10:47:40 +0100
Source: vmware-nsx
Binary: python-vmware-nsx
Architecture: source all
Version: 8.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: James Page 
Description:
 python-vmware-nsx - OpenStack virtual network service - VMWare NSX plugin
Closes: 830337
Changes:
 vmware-nsx (8.0.0-2) unstable; urgency=medium
 .
   * Fix epoch for python-neutron-lbaas dependencies.
   * Switch to ostestr for unit test execution, avoiding test races and
 associated FTBFS (Closes: #830337).
   * Add BD on python-testresources (indirect test dependency).
Checksums-Sha1:
 cdadd8385fb1d9969830dbab243d4ecf344b0d67 3156 vmware-nsx_8.0.0-2.dsc
 bdf88d3c106eac71819e1e503d74b9ee7f521f9b 2756 vmware-nsx_8.0.0-2.debian.tar.xz
 0de15ec38ee040f8f094e7fe8ac567c82fce4165 305374 
python-vmware-nsx_8.0.0-2_all.deb
Checksums-Sha256:
 ca1457d944b860ea0a7c0ab8d01e287d6d82639c68e7ae753353c59fda00a1a9 3156 
vmware-nsx_8.0.0-2.dsc
 5b6c559ac9696d143ac99bccc1d6968c90ac82227f9358826e5d41a9b96cf32a 2756 
vmware-nsx_8.0.0-2.debian.tar.xz
 9cfdf334204ae7cd9d29648950c6125e8b71a4348506e482fe16ba4e2dc1b268 305374 
python-vmware-nsx_8.0.0-2_all.deb
Files:
 1ec9870942facf59b33e7b24721b77cf 3156 net optional vmware-nsx_8.0.0-2.dsc
 3bf8e1d731f4c83ace28435ee90701ce 2756 net optional 
vmware-nsx_8.0.0-2.debian.tar.xz
 49c64b820ed37f732e418bcc0a9e47db 305374 python optional 
python-vmware-nsx_8.0.0-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXg4YOAAoJEL/srsug59jDZwYP/jOB8bb13QsjhDoIw+THkCML
AdZXR0OCDZb2oYFo/m4V3UXTK5Dyt+1b88QwApd3X4hGoBjQ6zYullyBHCHCRJ34
Qmn5nluZRAXGKbe1X/M3WOma/k8Xhq+8SK69p1wmYtwfToqBoD0vSjfqCAjK7gMa

Bug#811655: Patch for Debian bug #811655

[Andrea Claudi]

Hello,
This simple patch fix the build issue with gcc-6.
Please, let me know if it needs improvements.

Regards,
Andrea Claudi




La seguente informativa e' inserita in automatico dal sistema al fine esclusivo della realizzazione dei fini istituzionali dell'ente. 



INVESTI NELLA RICERCA 

il 5 per mille all'Universita' Politecnica delle Marche e' un investimento per i giovani, per il loro futuro - C.F. 00382520427 

http://www.univpm.it/5_per_mille 
diff -Nru starplot-0.95.5/debian/changelog starplot-0.95.5/debian/changelog
--- starplot-0.95.5/debian/changelog	2014-05-23 19:43:35.0 +0200
+++ starplot-0.95.5/debian/changelog	2016-07-12 12:13:32.0 +0200
@@ -1,3 +1,10 @@
+starplot (0.95.5-8.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS in convert.cc for gcc-6. (Closes: #811655)
+
+ -- Andrea Claudi   Tue, 12 Jul 2016 12:12:51 +0200
+
 starplot (0.95.5-8.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru starplot-0.95.5/debian/patches/03-fix-ftbfs-convert.diff starplot-0.95.5/debian/patches/03-fix-ftbfs-convert.diff
--- starplot-0.95.5/debian/patches/03-fix-ftbfs-convert.diff	1970-01-01 01:00:00.0 +0100
+++ starplot-0.95.5/debian/patches/03-fix-ftbfs-convert.diff	2016-07-12 11:14:26.0 +0200
@@ -0,0 +1,40 @@
+Index: starplot-0.95.5/src/convert/convert.cc
+===
+--- starplot-0.95.5.orig/src/convert/convert.cc
 starplot-0.95.5/src/convert/convert.cc
+@@ -49,7 +49,7 @@ void parse_star_file(istream & infile, o
+ 		 bool using_stdout, bool add_sun)
+ {
+   int lineno = 0;
+-  bool sun_found = false, moredata = true;
++  bool sun_found = false;
+   char record[1000];
+   Star * tempstar = 0, * currentstar = 0, * previousstar = 0;
+ 
+@@ -64,7 +64,7 @@ available on the StarPlot web page, you
+ in that package for more information.") << endl << endl;
+ 
+   do {
+-moredata = infile.getline(record, 999, '\n');
++infile.getline(record, 999, '\n');
+ record[999] = 0;
+ 
+ // $ ; and , have special meanings to StarPlot, so purge them:
+@@ -73,7 +73,7 @@ in that package for more information.")
+ record[i] = ' ';
+   
+ tempstar = parse_star_record(record, format);
+-if (tempstar || !moredata) {
++if (tempstar || infile.eof()) {
+   delete previousstar;
+   previousstar = currentstar;
+   currentstar = tempstar;
+@@ -111,7 +111,7 @@ in that package for more information.")
+ if (!using_stdout && !(lineno % 1000))
+   cout << starstrings::ssprintf(_("%d records converted."), lineno) << endl;
+ 
+-  } while (moredata) ;
++  } while (!infile.eof()) ;
+ 
+   delete previousstar;
+ 
diff -Nru starplot-0.95.5/debian/patches/series starplot-0.95.5/debian/patches/series
--- starplot-0.95.5/debian/patches/series	2012-06-26 21:12:55.0 +0200
+++ starplot-0.95.5/debian/patches/series	2016-07-12 12:12:29.0 +0200
@@ -1,2 +1,3 @@
 01-starplot_desktop_file.diff
 02-fix-ftbfs-and-hrdiagram-opts.diff
+03-fix-ftbfs-convert.diff

Processed: patch tag #811655

[Debian Bug Tracking System]

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

> tags 811655 patch
Bug #811655 [starplot] FTBFS with GCC 6: cannot convert x to y
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#830843: [Pkg-varnish-devel] Bug#830843: Bug#830843: varnish-modules: accesses the internet during build

[Emanuele Rocca]

On 12/07 12:21, Emanuele Rocca wrote:
> We need to either patch varnishtest and hardcode feature_dns, or avoid
> running the tests altogether.

As ssm suggested, we can use libnss-wrapper instead and avoid actually
performing the DNS request:

http://anonscm.debian.org/cgit/pkg-varnish/varnish-modules.git/commit/?id=76bb49f0be2ecb0e33d39584987916a6aac254b7

Bug#830606: marked as done (python-qtawesome: accesses the internet during build)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 13:04:08 +
with message-id 
and subject line Bug#830606: fixed in python-qtawesome 0.3.3-3
has caused the Debian Bug report #830606,
regarding python-qtawesome: accesses the internet during build
to be marked as done.

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

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


-- 
830606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-qtawesome
Version: 0.3.3-2
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst python-qtawesome builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

  00:00:00.00 IP df3f123661d0.33485 > dnscache.uct.ac.za.domain: 4772+ A? 
docs.python.org. (33)
  00:00:00.78 IP df3f123661d0.33485 > dnscache.uct.ac.za.domain: 50518+ 
? docs.python.org. (33)
  00:00:00.298447 IP dnscache.uct.ac.za.domain > df3f123661d0.33485: 50518 
2/1/0 CNAME python.map.fastly.net., CNAME prod.python.map.fastlylb.net. (178)
  00:00:00.298873 IP dnscache.uct.ac.za.domain > df3f123661d0.33485: 4772 3/4/4 
CNAME python.map.fastly.net., CNAME prod.python.map.fastlylb.net., A 
151.101.16.223 (259)
  00:00:00.299292 IP df3f123661d0.51660 > 151.101.16.223.https: Flags [S], seq 
866303703, win 29200, options [mss 1460,sackOK,TS val 109543511 ecr 
0,nop,wscale 7], length 0
  00:00:00.448191 IP 151.101.16.223.https > df3f123661d0.51660: Flags [S.], seq 
3415823459, ack 866303704, win 28560, options [mss 1440,sackOK,TS val 
1180091670 ecr 109543511,nop,wscale 9], length 0

  [..]

This appears to be caused by (at least) Sphinx's intersphinx mapping extension.
Please see #830186 for more information, including suggestions on how to fix it.

The full build log (including tcpdump output) is attached.


Regards,

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


python-qtawesome.0.3.3-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-qtawesome
Source-Version: 0.3.3-3

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

Debian distribution maintenance software
pp.
Ghislain Antony Vaillant  (supplier of updated 
python-qtawesome 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, 11 Jul 2016 15:56:18 +0100
Source: python-qtawesome
Binary: python-qtawesome python3-qtawesome python-qtawesome-common 
python-qtawesome-doc
Architecture: source
Version: 0.3.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ghislain Antony Vaillant 
Description:
 python-qtawesome - iconic fonts in PyQt and PySide applications (Python 2)
 python-qtawesome-common - common files for QtAwesome
 python-qtawesome-doc - documentation and examples for QtAwesome
 python3-qtawesome - iconic fonts in PyQt and PySide applications (Python 3)
Closes: 830606
Changes:
 python-qtawesome (0.3.3-3) unstable; urgency=medium
 .
   * d/gbp.conf: no patch numbering with gbp-pq.
   * Add patch preventing intersphinx from accessing the internet.
 Thanks to Chris Lamb (Closes: #830606)
   * Add python-doc to build dependencies.
Checksums-Sha1:
 92c646f432c82dcae9bcf7df442b577b6102c770 2448 python-qtawesome_0.3.3-3.dsc
 99cc3fb5e12c8d4ab2700b426e3e10e2648dc2c2 4932 
python-qtawesome_0.3.3-3.debian.tar.xz
Checksums-Sha256:
 151a77958a6f2d92b20d10ad196ba138a5fb32cdb138a9ac8584d016cbb3d812 2448 
python-qtawesome_0.3.3-3.dsc
 94db3db898c0199214081dcd026adc88d79cbe8add6a95fe679a988a501fa493 4932 
python-qtawesome_0.3.3-3.debian.tar.xz
Files:
 a0099685532313309f49875d21b428d4 2448 python optional 
python-qtawesome_0.3.3-3.dsc
 9670f4dde3cae5dd79bc1edf2cf293d8 4932 python optional 
python-qtawesome_0.3.3-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG 

Bug#822121: marked as done (Boost 1.55 to be removed; your attention required)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 12:33:40 +
with message-id 
and subject line Bug#822121: fixed in cufflinks 2.2.1-2
has caused the Debian Bug report #822121,
regarding Boost 1.55 to be removed; your attention required
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.)


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

Boost 1.55 has not built correctly since the GCC 5 introduction in July 2015 
and I plan
to ask for its removal from unstable very shortly.  It has already been removed 
from
testing.

The package cufflinks appeared on a list of reverse dependencies generated 
using 'dak rm -Rn boost1.55' (see below).  This bug is to request an
upload with updated boost dependencies.

If your package build-depends on the default boost, then a simple rebuild will 
suffice.
If your package uses 1.55-versioned build-deps, then please check whether you 
can
move to default boost.  Or if not, at least move to 1.58.

Output from ssh mirror.ftp-master.debian.org "dak rm -Rn boost1.55" follows.

Checking reverse dependencies...
# Broken Depends:
ball: ballview [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libball1.4 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libballview1.4 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  python-ball [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  python-ballview [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
cufflinks/non-free: cufflinks [amd64]
diet: diet-agent [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libdiet-admin2.8 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libdiet-client2.8 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libdiet-dagda2.8 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libdiet-sed2.8 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
feel++: feel++-apps [amd64 i386 powerpc]
libfeel++1 [amd64 i386 powerpc]
gqrx-sdr: gqrx-sdr [kfreebsd-amd64 kfreebsd-i386]
gr-air-modes: gr-air-modes [kfreebsd-amd64 kfreebsd-i386]
  libair-modes0 [kfreebsd-amd64 kfreebsd-i386]
gr-osmosdr: gr-osmosdr [kfreebsd-amd64 kfreebsd-i386]
libgnuradio-osmosdr0.1.3 [kfreebsd-amd64 kfreebsd-i386]
kig: kig [hurd-i386]
librime: librime-bin [hurd-i386]
 librime1 [hurd-i386]
limereg: limereg [mips mipsel]
mongodb: mongodb-clients [hurd-i386 kfreebsd-i386]
 mongodb-server [hurd-i386 kfreebsd-i386]
openvrml: libopenvrml9 [amd64 armel armhf i386 mips mipsel powerpc ppc64el 
s390x]
  openvrml-lookat [amd64 armel armhf i386 mips mipsel powerpc ppc64el 
s390x]
pcb2gcode: pcb2gcode [kfreebsd-amd64 kfreebsd-i386]
qbittorrent: qbittorrent [kfreebsd-amd64 kfreebsd-i386]
 qbittorrent-nox [kfreebsd-amd64 kfreebsd-i386]
qpid-cpp: libqpidcommon2 [amd64 arm64 i386 mipsel powerpc ppc64el]
  qpidd [amd64 arm64 i386 mipsel powerpc ppc64el]
smc: smc [amd64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel 
powerpc s390x]
swift-im: libswiften-dev [amd64 arm64 armel armhf i386 mips mipsel powerpc 
ppc64el s390x]
  libswiften2 [amd64 arm64 armel armhf i386 mips mipsel powerpc ppc64el 
s390x]
  swift-im [amd64 arm64 armel armhf i386 mips mipsel powerpc ppc64el 
s390x]
--- End Message ---
--- Begin Message ---
Source: cufflinks
Source-Version: 2.2.1-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated cufflinks package)

(This message was generated automatically at their request; if 

Bug#797280: Please help porting cufflinks to latest libboost

[Andreas Tille]

Hi Jakub,

On Tue, Jul 12, 2016 at 01:10:44PM +0200, Jakub Wilk wrote:
> 
> For some reason Eigen thinks that v.colwise().sum() cannot be treated as a
> one-dimensional vector, which smells like a bug in Eigen. Changing the last
> line to
> 
>   m = v.colwise().sum()(0, 0);
> 
> seems to do the trick.

Works.

Thanks a lot

 Andreas.

-- 
http://fam-tille.de

Bug#830762: kmail: empty folders list

[Dominik George]

Package: kmail
Followup-For: Bug #830762

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I had a similar issue after the upgrade. For me, switching the theme of
the message list a few times resolved it (but I saw that it doesn't for
mirabilos).

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

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

Versions of packages kmail depends on:
ii  akonadi-server  4:16.04.2-3
ii  kdepim-runtime  4:16.04.2-2
ii  kdepimlibs-data 4:16.04.2-2
ii  kf5-kdepimlibs-kio-plugins  4:16.04.2-2
ii  libc6   2.23-1
ii  libgcc1 1:6.1.1-9
ii  libkf5akonadiagentbase5 4:16.04.2-3
ii  libkf5akonadicalendar5  16.04.2-2
ii  libkf5akonadicontact5   4:16.04.2-2
ii  libkf5akonadicore-bin   4:16.04.2-3
ii  libkf5akonadicore5  4:16.04.2-3
ii  libkf5akonadimime5  4:16.04.2-2
ii  libkf5akonadisearchdebug5   16.04.2-2
ii  libkf5akonadiwidgets5   4:16.04.2-3
ii  libkf5alarmcalendar516.04.2-2
ii  libkf5archive5  5.23.0-1
ii  libkf5bookmarks55.23.0-1
ii  libkf5calendarcore5 4:16.04.2-1
ii  libkf5calendarsupport5  4:16.04.2-2
ii  libkf5calendarutils516.04.2-1
ii  libkf5codecs5   5.23.0-1
ii  libkf5completion5   5.23.0-1
ii  libkf5configcore5   5.23.0-1
ii  libkf5configgui55.23.0-1
ii  libkf5configwidgets55.23.0-1
ii  libkf5contacts5 16.04.2-1
ii  libkf5coreaddons5   5.23.0-1
ii  libkf5crash55.23.0-1
ii  libkf5dbusaddons5   5.23.0-1
ii  libkf5followupreminder5 4:16.04.2-2
ii  libkf5gpgmepp-pthread5  16.04.2-1
ii  libkf5gravatar5 4:16.04.2-2
ii  libkf5guiaddons55.23.0-1
ii  libkf5i18n5 5.23.0-1
ii  libkf5iconthemes5   5.23.0-1
ii  libkf5identitymanagement5   16.04.2-1
ii  libkf5incidenceeditor-bin   16.04.2-2
ii  libkf5incidenceeditor5  16.04.2-2
ii  libkf5itemmodels5   5.23.0-1
ii  libkf5itemviews55.23.0-1
ii  libkf5jobwidgets5   5.23.0-1
ii  libkf5kcmutils5 5.23.0-1
ii  libkf5kdelibs4support5  5.23.0-1
ii  libkf5kiocore5  5.23.0-1
ii  libkf5kiofilewidgets5   5.23.0-1
ii  libkf5kiowidgets5   5.23.0-1
ii  libkf5kmanagesieve5 4:16.04.2-2
ii  libkf5kontactinterface5 16.04.2-1
ii  libkf5ksieveui5 4:16.04.2-2
ii  libkf5libkdepim-plugins 4:16.04.2-2
ii  libkf5libkdepim54:16.04.2-2
ii  libkf5libkleo5  4:16.04.2-1
ii  libkf5mailcommon-plugins4:16.04.2-2
ii  libkf5mailcommon5   4:16.04.2-2
ii  libkf5mailimporter5 4:16.04.2-2
ii  libkf5mailtransport516.04.2-2
ii  libkf5messagecomposer5  4:16.04.2-2
ii  libkf5messagecore5  4:16.04.2-2
ii  libkf5messagelist5  4:16.04.2-2
ii  libkf5messageviewer54:16.04.2-2
ii  libkf5mime5 16.04.2-1
ii  libkf5notifications55.23.0-1
ii  libkf5notifyconfig5 5.23.0-1
ii  libkf5parts55.23.0-1
ii  libkf5pimcommon-plugins 4:16.04.2-2
ii  libkf5pimcommon54:16.04.2-2
ii  libkf5pimtextedit5  16.04.2-1
ii  libkf5sendlater54:16.04.2-2
ii  libkf5service-bin   5.23.0-1
ii  libkf5service5  5.23.0-1
ii  libkf5sonnetui5 5.23.0-1
ii  libkf5templateparser5   4:16.04.2-2
ii  libkf5textwidgets5  5.23.0-1
ii  libkf5wallet-bin5.23.0-1
ii  libkf5wallet5   5.23.0-1
ii  libkf5widgetsaddons55.23.0-1
ii  libkf5windowsystem5 5.23.0-1
ii  libkf5xmlgui5   5.23.0-1
ii  libqt5core5a5.6.1+dfsg-3
ii  libqt5dbus5 5.6.1+dfsg-3
ii  libqt5gui5  5.6.1+dfsg-3
ii  libqt5network5  5.6.1+dfsg-3
ii  libqt5widgets5  5.6.1+dfsg-3
ii  libqt5xml5  5.6.1+dfsg-3
ii  libstdc++6  6.1.1-9

Versions of packages kmail recommends:
ii  accountwizard   4:16.04.2-2
ii  gnupg-agent 2.1.11-7
ii  gnupg2  2.1.11-7
ii  kdepim-addons   16.04.2-2
ii  kdepim-doc  4:16.04.2-2
ii  kdepim-themeeditors 4:16.04.2-2
ii  ktnef   4:16.04.2-2
ii  pinentry-qt [pinentry-x11]  0.9.7-5

Versions of packages kmail suggests:
pn  clamav 
ii  kaddressbook   4:16.04.2-2
ii  kleopatra  4:16.04.2-2
ii  procmail   3.22-25
pn  spamassassin | bogofilter | 

Processed (with 1 error): archive python-whoosh bug: 712510

[Debian Bug Tracking System]

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

> archive 712510
Bug #712510 {Done: Dragoslav Sicarov } [python-whoosh] 
python-whoosh FTBFS:some tests failed on mips
Bug 712510 cannot be archived
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#830844: Pending fixes for bugs in the libauthen-krb5-perl package

[Damyan Ivanov]

-=| Sergio Gelato, 12.07.2016 11:51:20 +0200 |=-
> > https://anonscm.debian.org/cgit/pkg-perl/packages/libauthen-krb5-perl.git/commit/?id=3558a41
> 
> You may have missed a documentation reference in Krb5.pm:
> ---
> =item get_krbhst(realm)
> 
> Returns a list of the Kerberos servers from the specified realm.

Oh, I missed the "PREFIX = krb5_" thing in MODULE description and 
looked only for "krb5_get_krbhst".

> ---
> which raises the issue of how much Perl code out there may call
> Authen::Krb5::get_krbhst($realm) .

None in Debian: 
https://codesearch.debian.net/search?q=get_krbhst=1

And whoever used that method in some non-packaged stuff would have 
seen the undefined symbol error already.

> As far as my own needs are concerned it's OK to drop this function,
> but it is an API change and may deserve a bump in the module's version number.
> 
> Alternatively, one could lift the implementation of krb5_get_krbhst (in terms
> of profile_get_values, which is a public interface) from older libkrb5, or
> provide a new one if there are licensing issues. Of course this is more
> work and best left to upstream.
> 
> As a stop-gap, maybe one could keep Authen::Krb5::get_krbhst but with a
> dummy implementation that always returns undef?

Latest upstream release is from 2010 and RT at 
https://rt.cpan.org/Public/Dist/Display.html?Name=Krb5 seems like it 
was never touched.

I am inclined to drop get_krbhst from the POD and move on. Yes, that 
would be API breakage, but that part of the API was already broken, 
and the patch fixes the PERL_DL_NONLAZY=1 use case so it seems like an 
improvement to me.

If an implementation using public Kerberos API appears later, amending 
would be easy. I myself don't feel qualified to write such 
implementation.

Better approaches welcome, of course. I won't rush with the POD 
removal.

Bug#825199: marked as done (python-cement: ships file in generic location: /usr/lib/python2.7/dist-packages/examples/__init__.py)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 11:07:40 +
with message-id 
and subject line Bug#825199: fixed in python-cement 2.8.2-2
has caused the Debian Bug report #825199,
regarding python-cement: ships file in generic location: 
/usr/lib/python2.7/dist-packages/examples/__init__.py
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.)


-- 
825199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cement
Version: 2.8.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: clone -1 -2
Control: reassign -2 python-starpy 1.0.1.0.git.20140806-1
Control: retitle -2 python-starpy: ships file in generic location: 
/usr/lib/python2.7/dist-packages/examples/__init__.py

Hi,

during a test with piuparts I noticed your package ships a file in a very
generic location, causing conflicts with other packages doing the same mistake:

  Selecting previously unselected package python-cement.
  Preparing to unpack .../python-cement_2.8.2-1_all.deb ...
  Unpacking python-cement (2.8.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-cement_2.8.2-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/examples/__init__.py', 
which is also in package python-starpy 1.0.1.0.git.20140806-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-cement_2.8.2-1_all.deb

The examples probably don't belong into /usr/lib/python2.7 at all.


Cheers,

Andreas


python-starpy=1.0.1.0.git.20140806-1_python-cement=2.8.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-cement
Source-Version: 2.8.2-2

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

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

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

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated python-cement 
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, 12 Jul 2016 11:49:09 +0200
Source: python-cement
Binary: python-cement python3-cement python-cement-doc
Architecture: source all
Version: 2.8.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-cement - CLI Application Framework (Python2 version)
 python-cement-doc - CLI Application Framework (Documentation)
 python3-cement - CLI Application Framework (Python3 version)
Closes: 825199 830635
Changes:
 python-cement (2.8.2-2) unstable; urgency=medium
 .
   * Add patch to prevent installation of example package in global
 namespace (Closes: #825199).
   * Add python3-sphinx-rtd-theme to Build-Depends (Closes: 830635).
   * Use https:// for copyright-format 1.0 URL.
Checksums-Sha1:
 bf70531117d391e3af91eed97470b6a57335c531 2594 python-cement_2.8.2-2.dsc
 ec56a0785c21c41bc0bce39abc1021a0ecafe8af 165697 python-cement_2.8.2.orig.tar.gz
 16c4e4a79cc36cde44913af8385cc540f7864368 5272 
python-cement_2.8.2-2.debian.tar.xz
 91b07b7a5675668d083425d399d653b4054ba988 185764 
python-cement-doc_2.8.2-2_all.deb
 15c9e27aa0cb42ee7fd1d48ea66d2a9c9ee4f831 67056 python-cement_2.8.2-2_all.deb
 945502ce85f47a1dc15c6f04efa6384674911f23 67074 python3-cement_2.8.2-2_all.deb
Checksums-Sha256:
 ed9e356af05c93330411e4422decd6dcb3543fd9034100993ba1460a2330bb8c 2594 
python-cement_2.8.2-2.dsc
 0ac204a35657d7db02e4e581ecaf4eddfa32e604ed5c1b3ebefabdd632590424 165697 
python-cement_2.8.2.orig.tar.gz
 0b6ee7bdf3094f6fd248abeef1ba9d942bedd427bfa2cd19d76c1f6c34131112 5272 
python-cement_2.8.2-2.debian.tar.xz
 2b9895bae322a1538d0268cc5d61b595e322a10056a27f6b84396c0c2bd6ba75 185764 
python-cement-doc_2.8.2-2_all.deb
 749a511d4043a51ff0d480fc7f46bb82cb56976273539ec969c89cfdc1d5c579 67056 
python-cement_2.8.2-2_all.deb
 17e47cdc823c4bd795f0a21d56b6ded440e075d97b316ddbe594bdc0c1c55bf9 67074 
python3-cement_2.8.2-2_all.deb
Files:
 d3c32d1cf1fdc389d50b6aba8359b997 2594 python optional 

Bug#830635: marked as done (python-cement: FTBFS: ImportError: No module named 'sphinx_rtd_theme')

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 11:07:40 +
with message-id 
and subject line Bug#830635: fixed in python-cement 2.8.2-2
has caused the Debian Bug report #830635,
regarding python-cement: FTBFS: ImportError: No module named 'sphinx_rtd_theme'
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.)


-- 
830635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cement
Version: 2.8.2-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,

python-cement fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../libjs-underscore_1.7.0~dfsg-1_all.deb ...
  Unpacking libjs-underscore (1.7.0~dfsg-1) ...
  Selecting previously unselected package libjs-sphinxdoc.
  Preparing to unpack .../libjs-sphinxdoc_1.4.4-3_all.deb ...
  Unpacking libjs-sphinxdoc (1.4.4-3) ...
  Selecting previously unselected package sphinx-common.
  Preparing to unpack .../sphinx-common_1.4.4-3_all.deb ...
  Unpacking sphinx-common (1.4.4-3) ...
  Selecting previously unselected package python3-sphinx.
  Preparing to unpack .../python3-sphinx_1.4.4-3_all.deb ...
  Unpacking python3-sphinx (1.4.4-3) ...
  Selecting previously unselected package python3-tabulate.
  Preparing to unpack .../python3-tabulate_0.7.5-1_all.deb ...
  Unpacking python3-tabulate (0.7.5-1) ...
  Selecting previously unselected package python3-yaml.
  Preparing to unpack .../python3-yaml_3.11-3+b1_amd64.deb ...
  Unpacking python3-yaml (3.11-3+b1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.23-1) ...
  Setting up libjs-jquery (1.12.4-1) ...
  Setting up python-setuptools (20.10.1-1.1) ...
  Setting up python3-roman (2.0.0-2) ...
  Setting up python-configobj (5.0.6-2) ...
  Setting up python3-imagesize (0.7.1-1) ...
  Setting up libjs-underscore (1.7.0~dfsg-1) ...
  Setting up python3-funcsigs (0.4-2) ...
  Setting up python-colorlog (2.7.0-1) ...
  Setting up python3-alabaster (0.7.8-1) ...
  Setting up python3-six (1.10.0-3) ...
  Setting up python-genshi (0.7-5) ...
  Setting up libjs-sphinxdoc (1.4.4-3) ...
  Setting up sgml-base (1.28) ...
  Setting up libmemcached11:amd64 (1.0.18-4.1) ...
  Setting up python3-pkg-resources (20.10.1-1.1) ...
  Setting up python3-markupsafe (0.23-2+b2) ...
  Setting up python-pyinotify (0.9.6-1) ...
  Setting up python3-colorlog (2.7.0-1) ...
  Setting up python3-genshi (0.7-5) ...
  Setting up libyaml-0-2:amd64 (0.1.6-3) ...
  Setting up python3-nose (1.3.7-2) ...
  Setting up python3-argcomplete (1.0.0-1) ...
  Setting up python-pbr (1.8.0-4.1) ...
  update-alternatives: using /usr/bin/python2-pbr to provide /usr/bin/pbr (pbr) 
in auto mode
  Setting up python3-all (3.5.1-4) ...
  Setting up python3-tabulate (0.7.5-1) ...
  Setting up python3-jinja2 (2.8-1) ...
  Setting up python-babel-localedata (2.3.4+dfsg.1-2) ...
  Setting up sphinx-common (1.4.4-3) ...
  Setting up python-pystache (0.5.4-5) ...
  Setting up python-funcsigs (0.4-2) ...
  Setting up python3-pystache (0.5.4-5) ...
  Setting up xml-core (0.13+nmu2) ...
  Setting up python3-configobj (5.0.6-2) ...
  Setting up python3-setuptools (20.10.1-1.1) ...
  Setting up python-argcomplete (1.0.0-1) ...
  Setting up python-nose (1.3.7-2) ...
  Setting up python-all (2.7.11-2) ...
  Setting up python3-tz (2015.7+dfsg-0.1) ...
  Setting up python3-pylibmc (1.5.0-4+b1) ...
  Setting up python-tabulate (0.7.5-1) ...
  Setting up python3-pyinotify (0.9.6-1) ...
  Setting up python3-pygments (2.1.3+dfsg-1) ...
  Setting up python3-yaml (3.11-3+b1) ...
  Setting up python3-pbr (1.8.0-4.1) ...
  Setting up python-yaml (3.11-3+b1) ...
  Setting up python3-mock (1.3.0-2.1) ...
  Setting up python-pylibmc (1.5.0-4+b1) ...
  Setting up python-mock (1.3.0-2.1) ...
  Setting up python3-babel (2.3.4+dfsg.1-2) ...
  update-alternatives: using /usr/bin/pybabel-python3 to provide 
/usr/bin/pybabel (pybabel) in auto mode
  Processing triggers for sgml-base (1.28) ...
  Setting up docutils-common (0.12+dfsg-1) ...
  Processing triggers for sgml-base (1.28) ...
  Setting up python3-docutils (0.12+dfsg-1) ...
  update-alternatives: using /usr/share/docutils/scripts/python3/rst-buildhtml 
to provide /usr/bin/rst-buildhtml (rst-buildhtml) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2html to 
provide /usr/bin/rst2html (rst2html) in 

Bug#797280: Please help porting cufflinks to latest libboost

[Jakub Wilk]

* Andreas Tille , 2016-07-12, 11:12:

In file included from /usr/include/eigen3/Eigen/Core:297:0,
from /usr/include/eigen3/Eigen/Dense:1,
from abundances.h:21,
from abundances.cpp:16:
/usr/include/eigen3/Eigen/src/Core/DenseCoeffsBase.h: In instantiation of 
'Eigen::DenseCoeffsBase::CoeffReturnType 
Eigen::DenseCoeffsBase::coeff(Eigen::Index) const [with Derived = Eigen
/usr/include/eigen3/Eigen/src/Core/DenseCoeffsBase.h:181:19:   required from 
'Eigen::DenseCoeffsBase::CoeffReturnType 
Eigen::DenseCoeffsBase::operator()(Eigen::Index) const [with Derived
abundances.cpp:3815:28:   required from here
/usr/include/eigen3/Eigen/src/Core/DenseCoeffsBase.h:141:7: error: 
'THIS_COEFFICIENT_ACCESSOR_TAKING_ONE_ACCESS_IS_ONLY_FOR_EXPRESSIONS_ALLOWING_LINEAR_ACCESS'
 is not a member of 'Eigen::internal::static_assert
  EIGEN_STATIC_ASSERT(internal::evaluator::Flags & LinearAccessBit,
  ^
Makefile:1627: recipe for target 'abundances.o' failed


The relevant code in src/abundances.cpp looks like this:

Eigen::VectorXd v;
double m = 0;
v = U.rowwise().sum();
m = v.colwise().sum()(0);

For some reason Eigen thinks that v.colwise().sum() cannot be treated as 
a one-dimensional vector, which smells like a bug in Eigen. Changing the 
last line to


m = v.colwise().sum()(0, 0);

seems to do the trick.

Upstream bug report:
https://github.com/cole-trapnell-lab/cufflinks/issues/61

--
Jakub Wilk

Bug#830403: libconfig-model-lcdproc-perl: FTBFS: Attribute (instance) does not pass the type constraint because: Validation failed for 'Config::Model::Instance' with value undef at /usr/lib/x86_64-lin

[Dominique Dumont]

Model generation from lcdproc/LCDd.conf broke with Config::Model::Itself 2.005

I'll fix that upsream.

Thanks for the report.

All the best

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Bug#830838: marked as done (nova-api does not start)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 13:20:47 +0200
with message-id <14c25816-786c-8abb-f24c-f00a32a7f...@debian.org>
and subject line Re: [PKG-Openstack-devel] Bug#830838: nova-api does not start
has caused the Debian Bug report #830838,
regarding nova-api does not start
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.)


-- 
830838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nova-api
Version: 2:13.1.0-1~bpo8+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Nova becames unusable after upgrade from backports to Mitaka.
Previous backported version 'Liberty' was working fine.
Seems like something wrong with python modules names. This is a nova-api.log:

2016-07-12 06:25:32.917 4672 WARNING oslo_reports.guru_meditation_report [-] 
Guru mediation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
2016-07-12 06:25:32.941 4672 CRITICAL nova [-] ImportError: No module named 
oslo.middleware
2016-07-12 06:25:32.941 4672 ERROR nova Traceback (most recent call last):
2016-07-12 06:25:32.941 4672 ERROR nova   File "/usr/bin/nova-api", line 10, in 

2016-07-12 06:25:32.941 4672 ERROR nova sys.exit(main())
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/nova/cmd/api.py", line 57, in main
2016-07-12 06:25:32.941 4672 ERROR nova server = service.WSGIService(api, 
use_ssl=should_use_ssl)
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/nova/service.py", line 366, in __init__
2016-07-12 06:25:32.941 4672 ERROR nova self.app = 
self.loader.load_app(name)
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/nova/wsgi.py", line 497, in load_app
2016-07-12 06:25:32.941 4672 ERROR nova return deploy.loadapp("config:%s" % 
self.config_path, name=name)
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 247, in 
loadapp
2016-07-12 06:25:32.941 4672 ERROR nova return loadobj(APP, uri, name=name, 
**kw)
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 272, in 
loadobj
2016-07-12 06:25:32.941 4672 ERROR nova return context.create()
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 710, in create
2016-07-12 06:25:32.941 4672 ERROR nova return self.object_type.invoke(self)
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 144, in invoke
2016-07-12 06:25:32.941 4672 ERROR nova **context.local_conf)
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/paste/deploy/util.py", line 55, in fix_call
2016-07-12 06:25:32.941 4672 ERROR nova val = callable(*args, **kw)
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/nova/api/openstack/urlmap.py", line 160, in 
urlmap_factory
2016-07-12 06:25:32.941 4672 ERROR nova app = loader.get_app(app_name, 
global_conf=global_conf)
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 350, in 
get_app
2016-07-12 06:25:32.941 4672 ERROR nova name=name, 
global_conf=global_conf).create()
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 710, in create
2016-07-12 06:25:32.941 4672 ERROR nova return self.object_type.invoke(self)
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 144, in invoke
2016-07-12 06:25:32.941 4672 ERROR nova **context.local_conf)
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/paste/deploy/util.py", line 55, in fix_call
2016-07-12 06:25:32.941 4672 ERROR nova val = callable(*args, **kw)
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/nova/api/auth.py", line 74, in 
pipeline_factory
2016-07-12 06:25:32.941 4672 ERROR nova return _load_pipeline(loader, 
pipeline)
2016-07-12 06:25:32.941 4672 ERROR nova   File 
"/usr/lib/python2.7/dist-packages/nova/api/auth.py", line 58, in _load_pipeline
2016-07-12 06:25:32.941 4672 ERROR nova filters = [loader.get_filter(n) for 
n in pipeline[:-1]]
2016-07-12 06:25:32.941 4672 ERROR nova   File 

Bug#811659: marked as done (FTBFS with GCC 6: cannot convert x to y)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 10:45:14 +
with message-id 
and subject line Bug#811659: fixed in wvstreams 4.6.1-9
has caused the Debian Bug report #811659,
regarding FTBFS with GCC 6: cannot convert x to y
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.)


-- 
811659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wvstreams
Version: 4.6.1-7
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> x86_64-linux-gnu-g++ -c -o streams/wvstream.o streams/wvstream.cc -MMD -MF 
> streams/.wvstream.d -MP -MQ streams/wvstream.o -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/tcl8.3 -DDEBUG=0 
> -I./include -D_BSD_SOURCE -D_GNU_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -DUNSTABLE -fPIC -Wall -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -fno-tree-dce -fno-optimize-sibling-calls -fPIC -DPIC -fno-tree-dce 
> -fno-optimize-sibling-calls -Wall -Woverloaded-virtual
> In file included from /usr/include/time.h:27:0,
>  from streams/wvstream.cc:11:
> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>^~~
> 
> streams/wvstream.cc: In member function 'void 
> WvStream::_build_selectinfo(IWvStream::SelectInfo&, time_t, bool, bool, bool, 
> bool)':
> streams/wvstream.cc:910:22: error: cannot convert 'IWvStreamCallback {aka 
> std::tr1::function}' to 'bool' in assignment
>   si.wants.readable = readcb;
>   ^~
> 
> streams/wvstream.cc:911:22: error: cannot convert 'IWvStreamCallback {aka 
> std::tr1::function}' to 'bool' in assignment
>   si.wants.writable = writecb;
>   ^~~
> 
> streams/wvstream.cc:912:25: error: cannot convert 'IWvStreamCallback {aka 
> std::tr1::function}' to 'bool' in assignment
>   si.wants.isexception = exceptcb;
>  ^~~~
> 
> streams/wvstream.cc: In member function 'IWvStream::SelectRequest 
> WvStream::get_select_request()':
> streams/wvstream.cc:1022:62: error: no matching function for call to 
> 'IWvStream::SelectRequest::SelectRequest(IWvStreamCallback&, 
> IWvStreamCallback&, IWvStreamCallback&)'
>  return IWvStream::SelectRequest(readcb, writecb, exceptcb);
>   ^
> 

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: wvstreams
Source-Version: 4.6.1-9

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

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated wvstreams 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, 11 Jul 2016 15:34:22 +
Source: wvstreams
Binary: libwvstreams4.6-base libwvstreams4.6-extras libuniconf4.6 
libwvstreams4.6-doc libwvstreams-dev uniconfd uniconf-tools
Architecture: source
Version: 4.6.1-9
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Gert Wollny 
Description:
 libuniconf4.6 - C++ network libraries for rapid application development
 libwvstreams-dev - Development libraries and header files for libwvstreams4.6
 libwvstreams4.6-base - C++ network libraries for rapid application development
 

Bug#818757: marked as done (orthanc-postgresql: does not start)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 12:42:43 +0200
with message-id <20160712104243.ge5...@an3as.eu>
and subject line Bug reporter confirmed that bug is solved
has caused the Debian Bug report #818757,
regarding orthanc-postgresql: does not start
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.)


-- 
818757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: orthanc-postgresql
Version: 2.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Orthanc does not start when the backend is set to PostgreSQL.

1) I can successfully

su - orthanc
psql -d orthanc_db

2) Orthanc will start if set to using the sqlite backend

3) it worked before dist-upgrading jessie to stretch

4) the existing orthanc_db is 0.8 and the jump is to Orthanc 1.0 (orthanc-pg 
2.0)

Logs attached.

Karsten

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

Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages orthanc-postgresql depends on:
ii  libboost-system1.58.0  1.58.0+dfsg-5+b1
ii  libc6  2.22-3
ii  libgcc11:5.3.1-11
ii  libjsoncpp0v5  0.10.5-1
ii  libpq5 9.5.1-1
ii  libstdc++6 5.3.1-11
ii  libuuid1   2.27.1-6
ii  orthanc1.0.0+dfsg-1+b1

orthanc-postgresql recommends no packages.

Versions of packages orthanc-postgresql suggests:
ii  postgresql  9.5+172

-- Configuration Files:
/etc/orthanc/postgresql.json changed:
{
/**
 * Configuration to use PostgreSQL instead of the default SQLite
 * back-end of Orthanc. You will have to install the
 * "orthanc-postgresql" package to take advantage of this feature.
 * Have a look at "/usr/share/doc/orthanc-postgresql/README.Debian"
 * for a tutorial.
 **/
"PostgreSQL" : {
// Enable the use of PostgreSQL to store the Orthanc index?
"EnableIndex" : true,
// Enable the use of PostgreSQL to store the DICOM files?
"EnableStorage" : true,
// Option 1: Specify explicit authentication parameters
//"Host" : "localhost",
//"Port" : 5432,
//"Database" : "orthanc_db",
//"Username" : "orthanc_user",
//"Password" : "my_password",
// Option 2: Authenticate using PostgreSQL connection URI
// "ConnectionUri" : 
"postgresql://orthanc_user:my_password@localhost:5432/orthanc_db",
"ConnectionUri" : "postgresql:///orthanc_db?user=orthanc",
// Optional: Disable the locking of the PostgreSQL database
"Lock" : false
}
}


-- no debconf information
Skript gestartet auf So 20 Mär 2016 14:08:50 CET
root@hermes:~# /usr/sbin/Orthanc --trace --logdir=/var/log/orthanc /etc/orthanc/
*** stack smashing detected ***: /usr/sbin/Orthanc terminated
=== Backtrace: =
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x692ab)[0xb691a2ab]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(__fortify_fail+0x37)[0xb69a9fe7]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0xf8fa8)[0xb69a9fa8]
/usr/share/orthanc/plugins/libOrthancPostgreSQLStorage.so(+0x11284)[0xb41fa284]
/usr/share/orthanc/plugins/libOrthancPostgreSQLStorage.so(+0xa9bf)[0xb41f39bf]
/usr/share/orthanc/plugins/libOrthancPostgreSQLStorage.so(OrthancPluginInitialize+0xab)[0xb41f9d7b]
/usr/sbin/Orthanc[0x8107c42]
/usr/sbin/Orthanc[0x8108aa3]
/usr/sbin/Orthanc[0x8107da9]
/usr/sbin/Orthanc[0x8068e48]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xf7)[0xb68c9527]
/usr/sbin/Orthanc[0x806f2fa]
=== Memory map: 
08048000-082c9000 r-xp  08:01 12230893   /usr/sbin/Orthanc
082c9000-082ca000 r--p 0028 08:01 12230893   /usr/sbin/Orthanc
082ca000-082cb000 rw-p 00281000 08:01 12230893   /usr/sbin/Orthanc
082cb000-082cd000 rw-p  00:00 0 
0870b000-0894 rw-p  00:00 0  [heap]
b4147000-b4177000 r-xp  08:01 6898379
/usr/lib/i386-linux-gnu/libpq.so.5.8
b4177000-b4179000 r--p 0002f000 08:01 6898379
/usr/lib/i386-linux-gnu/libpq.so.5.8
b4179000-b417a000 rw-p 00031000 08:01 6898379
/usr/lib/i386-linux-gnu/libpq.so.5.8
b417a000-b41ae000 r-xp  08:01 6899772
/usr/lib/i386-linux-gnu/libjsoncpp.so.0.10.5
b41ae000-b41af000 r--p 00033000 08:01 6899772

Bug#830855: marked as done (module does not compile)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 10:31:57 + (UTC)
with message-id <1234857285.2530490.1468319517098.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#830855: module does not compile
has caused the Debian Bug report #830855,
regarding module does not compile
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.)


-- 
830855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox-dkms
Version: 4.3.36-dfsg-1+deb8u1
Severity: serious

Hi,

This module does not build on my system any more (see attached log)

There appear to be at least 2 errors:

/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:581:21:
 error: implicit declaration of function ‘page_cache_release’ 
[-Werror=implicit-function-declaration]
 page_cache_release(pMemLnx->apPages[iPage]);

/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1032:14:
 error: too many arguments to function ‘get_user_pages’
 rc = get_user_pages(pTask,  /* Task for fault 
accounting. */
  ^
Regards,

Matthew

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 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: sysvinit (via /sbin/init)

Versions of packages virtualbox-dkms depends on:
ii  dkms  2.2.0.3-5

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  4.3.36-dfsg-1+deb8u1

virtualbox-dkms suggests no packages.

-- no debconf information
DKMS make.log for virtualbox-4.3.36 for kernel 4.6.0-1-amd64 (x86_64)
Tue 12 Jul 10:36:43 BST 2016
make: Entering directory '/usr/src/linux-headers-4.6.0-1-amd64'
  LD  /var/lib/dkms/virtualbox/4.3.36/build/built-in.o
  LD  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/built-in.o
  CC [M]  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/SUPDrvTracer.o
  CC [M]  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/alloc-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/initterm-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/memobj-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/mpnotification-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/powernotification-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memuserkernel-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/mp-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/mpnotification-r0drv-linux.o
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: 
In function ‘rtR0MemObjNativeFree’:
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:581:21:
 error: implicit declaration of function ‘page_cache_release’ 
[-Werror=implicit-function-declaration]
 page_cache_release(pMemLnx->apPages[iPage]);
 ^
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: 
In function ‘rtR0MemObjNativeLockUser’:
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1032:29:
 warning: passing argument 1 of ‘get_user_pages’ makes integer from pointer 
without a cast [-Wint-conversion]
 rc = get_user_pages(pTask,  /* Task for fault 
accounting. */
 ^
In file included from 
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/the-linux-kernel.h:88:0,
 from 
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31:
/usr/src/linux-headers-4.6.0-1-common/include/linux/mm.h:1288:6: note: expected 
‘long unsigned int’ but argument is of type ‘struct task_struct *’
 long 

Bug#830843: [Pkg-varnish-devel] Bug#830843: varnish-modules: accesses the internet during build

[Emanuele Rocca]

Hi,

On 12/07 09:22, Chris Lamb wrote:
> Whilst varnish-modules builds successfully on unstable/amd64, according to
> Debian Policy 4.9 packages may not attempt network access during
> a build.
> 
>   00:00:00.00 IP e66b957b9098.60905 > 
> sitecomwlr1000.sitecomwlr1000.domain: 10880+ A? phk.freebsd.dk. (32)
>   00:00:00.60 IP e66b957b9098.60905 > 
> sitecomwlr1000.sitecomwlr1000.domain: 24843+ ? phk.freebsd.dk. (32)
>   00:00:00.001007 IP e66b957b9098.54550 > 
> sitecomwlr1000.sitecomwlr1000.domain: 27794+ A? phk.freebsd.dk. (32)
>   00:00:00.001044 IP e66b957b9098.54550 > 
> sitecomwlr1000.sitecomwlr1000.domain: 39210+ ? phk.freebsd.dk. (32)
>   00:00:00.001129 IP e66b957b9098.45718 > 
> sitecomwlr1000.sitecomwlr1000.domain: 1+ A? phk.freebsd.dk. (32)
>   00:00:00.001152 IP e66b957b9098.45718 > 
> sitecomwlr1000.sitecomwlr1000.domain: 3037+ ? phk.freebsd.dk. (32)
> 
>   [..]

This is because of varnishtest trying to resolve phk.freebsd.dk every
time it is invoked to check if DNS works:
https://github.com/varnishcache/varnish-cache/blob/master/bin/varnishtest/vtc_main.c#L616

We need to either patch varnishtest and hardcode feature_dns, or avoid
running the tests altogether.

Bug#828037: fontconfig: font-config should not register .dpkg-tmp files in its cache, users ends up seeing squares instead of expected characters

[Raphael Hertzog]

Control: tag -1 + patch
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=96896

On Fri, 24 Jun 2016, Raphaël Hertzog wrote:
> So please make sure that the fontconfig cache update ignores any
> .dpkg-tmp file...

Please find attached some untested patch. I'm going to test this
in Kali.

> Still I wonder how this is even possible as when the fontconfig trigger
> runs, the packages are fully unpacked and those files should have been
> already insalled under their final name. Maybe GNOME has some inotify
> thing in place to update the cache dynamically? In any case, ignoring
> those files at the fontconfig level should fix this issue I believe.

I'm not sure how the system-wide and user cache interact but I found
out that gnome-settings-daemon monitor the font directories and runs

!FcConfigUptoDate (NULL) && FcInitReinitialize ()

when the monitor issues a change notification, see
http://sources.debian.net/src/gnome-settings-daemon/3.20.1-2/plugins/xsettings/fontconfig-monitor.c/#L42

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/
diff -Nru fontconfig-2.11.0/debian/changelog fontconfig-2.11.0/debian/changelog
--- fontconfig-2.11.0/debian/changelog  2016-03-12 19:01:15.0 +0100
+++ fontconfig-2.11.0/debian/changelog  2016-07-12 11:06:43.0 +0200
@@ -1,3 +1,10 @@
+fontconfig (2.11.0-6.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Skip .dpkg-tmp files when updating the cache. Closes: #828037
+
+ -- Raphaël Hertzog   Tue, 12 Jul 2016 10:49:07 +0200
+
 fontconfig (2.11.0-6.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru fontconfig-2.11.0/debian/patches/07_skip_dpkg_tmp_files.patch 
fontconfig-2.11.0/debian/patches/07_skip_dpkg_tmp_files.patch
--- fontconfig-2.11.0/debian/patches/07_skip_dpkg_tmp_files.patch   
1970-01-01 01:00:00.0 +0100
+++ fontconfig-2.11.0/debian/patches/07_skip_dpkg_tmp_files.patch   
2016-07-12 10:48:55.0 +0200
@@ -0,0 +1,19 @@
+diff --git a/src/fcdir.c b/src/fcdir.c
+index fd62a34..edfa121 100644
+--- a/src/fcdir.c
 b/src/fcdir.c
+@@ -283,7 +283,13 @@ FcDirScanConfig (FcFontSet*set,
+ }
+ while ((e = readdir (d)))
+ {
+-  if (e->d_name[0] != '.' && strlen (e->d_name) < FC_MAX_FILE_LEN)
++  size_t length_name = strlen (e->d_name);
++  /* Skip temporary dpkg files */
++  #define DPKG_TMP ".dpkg-tmp"
++  if (length_name > strlen(DPKG_TMP) &&
++  strcmp(e->d_name + length_name - strlen(DPKG_TMP), DPKG_TMP) == 
0)
++  continue;
++  if (e->d_name[0] != '.' && length_name < FC_MAX_FILE_LEN)
+   {
+   strcpy ((char *) base, (char *) e->d_name);
+   if (!FcStrSetAdd (files, file)) {
diff -Nru fontconfig-2.11.0/debian/patches/series 
fontconfig-2.11.0/debian/patches/series
--- fontconfig-2.11.0/debian/patches/series 2016-03-12 18:56:21.0 
+0100
+++ fontconfig-2.11.0/debian/patches/series 2016-07-12 10:49:03.0 
+0200
@@ -4,3 +4,4 @@
 04_mgopen_fonts.patch
 05_doc_files.patch
 06_cross.patch
+07_skip_dpkg_tmp_files.patch

Processed: Re: Bug#828037: fontconfig: font-config should not register .dpkg-tmp files in its cache, users ends up seeing squares instead of expected characters

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #828037 [fontconfig] fontconfig: font-config should not register .dpkg-tmp 
files in its cache, users ends up seeing squares instead of expected characters
Added tag(s) patch.
> forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=96896
Bug #828037 [fontconfig] fontconfig: font-config should not register .dpkg-tmp 
files in its cache, users ends up seeing squares instead of expected characters
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=96896'.

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

Bug#830832: marked as done (hashcat: FTBFS with dpkg-buildpackage -B)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 09:57:49 +
with message-id 
and subject line Bug#830832: fixed in hashcat 3.00-2
has caused the Debian Bug report #830832,
regarding hashcat: FTBFS with dpkg-buildpackage -B
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.)


-- 
830832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hashcat
Version: 3.00-1
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Hi Daniel,

Your latest hashcat upload is failing to build on all autobuilders, because
your dh_fixperms override tries to chmod files that are only present when
building the arch-independent binary packages:

 debian/rules override_dh_fixperms
  make[1]: Entering directory '/«PKGBUILDDIR»'
  dh_fixperms
  chmod 644 debian/hashcat-data/usr/share/doc/hashcat-data/examples/example0.sh
  chmod: cannot access 
'debian/hashcat-data/usr/share/doc/hashcat-data/examples/example0.sh': No such 
file or directory
  debian/rules:16: recipe for target 'override_dh_fixperms' failed
  make[1]: *** [override_dh_fixperms] Error 1
  make[1]: Leaving directory '/«PKGBUILDDIR»'
  debian/rules:7: recipe for target 'binary-arch' failed

(https://buildd.debian.org/status/fetch.php?pkg=hashcat=amd64=3.00-1=1468257422)

Please see the attached patch, which corrects this error.
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru hashcat-3.00/debian/rules hashcat-3.00/debian/rules
--- hashcat-3.00/debian/rules	2016-07-08 09:38:40.0 -0700
+++ hashcat-3.00/debian/rules	2016-07-11 18:07:00.0 -0700
@@ -12,7 +12,7 @@
 override_dh_installchangelogs:
 	dh_installchangelogs docs/changes.txt
 
-override_dh_fixperms:
+override_dh_fixperms-indep:
 	dh_fixperms
 	chmod 644 debian/hashcat-data/usr/share/doc/hashcat-data/examples/example0.sh
 	chmod 644 debian/hashcat-data/usr/share/doc/hashcat-data/examples/example400.sh
--- End Message ---
--- Begin Message ---
Source: hashcat
Source-Version: 3.00-2

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

Debian distribution maintenance software
pp.
Daniel Echeverry  (supplier of updated hashcat 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, 11 Jul 2016 21:08:12 -0500
Source: hashcat
Binary: hashcat hashcat-data
Architecture: source
Version: 3.00-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools Packaging Team 

Changed-By: Daniel Echeverry 
Description:
 hashcat- Advanced CPU-based password recovery utility
 hashcat-data - Data files for hashcat Advanced CPU-based password recovery 
utili
Closes: 830832
Changes:
 hashcat (3.00-2) unstable; urgency=medium
 .
   * debian/rules
 + Fix FTBFS with dpkg-buildpackage -B (Closes: #830832)
Checksums-Sha1:
 2caa5d60afeefe24e050bdc2d65f1ae61050a9db 2003 hashcat_3.00-2.dsc
 fa688b1d308d9db1fbe76cea8ab8c1b4d2cf5ab0 8132 hashcat_3.00-2.debian.tar.xz
Checksums-Sha256:
 9866b6f2276a54894f07d8c9773169b08d869465ae17a762b3a843f07b6ab3bb 2003 
hashcat_3.00-2.dsc
 93d954f9354f269434028e8da715c4f019789ce12479dff16e8c56e3ad71c4cc 8132 
hashcat_3.00-2.debian.tar.xz
Files:
 357fd5abd830b3c3cb2e841573c6bab6 2003 net optional hashcat_3.00-2.dsc
 916faba9f0790811d0143643c0e29db0 8132 net optional hashcat_3.00-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXhKDAAAoJEPNPCXROn13ZvaYQAIAIgPFzxO/kN1XwaFYziBwy
g0WnP44Dp+tWXhMSnJPY+MDKx6kg3DDeVss6sS3JH5ZP1RlVfh9b/FdhRNLbmv5v
t1zxnxd5z38A7O2ENeezWIF1i3uPe1CKBF4jzKUnWmdWfC0Y/hjLhOS8/mv5E5oz

Bug#830844: marked as done (Krb5.so fails to load: missing symbol krb5_free_krbhst)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 09:58:32 +
with message-id 
and subject line Bug#830844: fixed in libauthen-krb5-perl 1.9-5
has caused the Debian Bug report #830844,
regarding Krb5.so fails to load: missing symbol krb5_free_krbhst
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.)


-- 
830844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libauthen-krb5-perl
Version: 1.9-4
Severity: serious

$ env PERL_DL_NONLAZY=1 perl -MAuthen::Krb5 -e '1;'
Can't load '/usr/lib/i386-linux-gnu/perl5/5.20/auto/Authen/Krb5/Krb5.so' for 
module Authen::Krb5: 
/usr/lib/i386-linux-gnu/perl5/5.20/auto/Authen/Krb5/Krb5.so: undefined symbol: 
krb5_free_krbhst at /usr/lib/i386-linux-gnu/perl/5.20/DynaLoader.pm line 187.
 at -e line 0.
Compilation failed in require.
BEGIN failed--compilation aborted.

This breaks test suites or anything else that sets PERL_DL_NONLAZY=1.

The problem is that this module uses an internal MIT Kerberos API that has
been removed. From Krb5.xs:

/*
 * These are internal Kerberos library functions that aren't prototyped and
 * that we probably shouldn't be calling.  Prototype them with the arguments
 * we expect and leave them for now pending an API cleanup.
 */
krb5_error_code krb5_free_krbhst(krb5_context, char * const *);
krb5_error_code krb5_get_krbhst(krb5_context, const krb5_data *, char ***);

And from the changelog (doc/CHANGES) for package krb5:

commit 81fde7e475b02986c1aff88766cc48882004d5dc
Author: Greg Hudson 
Date:   Fri Mar 22 16:00:48 2013 -0400

Get rid of krb5_{get,free}_krbhst

These functions were always internal.  They haven't been used since
v5passwdd was eliminated in krb5 1.4.
--- End Message ---
--- Begin Message ---
Source: libauthen-krb5-perl
Source-Version: 1.9-5

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

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

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated libauthen-krb5-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 12 Jul 2016 09:34:48 +
Source: libauthen-krb5-perl
Binary: libauthen-krb5-perl
Architecture: source
Version: 1.9-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Damyan Ivanov 
Closes: 830844
Description: 
 libauthen-krb5-perl - Perl interface to Kerberos 5 API
Changes:
 libauthen-krb5-perl (1.9-5) unstable; urgency=medium
 .
   * Team upload
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-Browser URL to cgit web frontend
 .
   [ Axel Beckert ]
   * Change CPAN Distribution name from Authen-Krb5 to Krb5 in MetaCPAN URL
 and Upstream-Name field in debian/copyright. The module's name is
 Authen::Krb5, but the CPAN Distribution's name is just Krb5. Found by
 DUCK.
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * Change bugtracker URL(s) to HTTPS.
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
 .
   [ Damyan Ivanov ]
   * add patch removing references to obsolete krb5_{get,free}_krbhst.
 Thanks to Sergio Gelato. Closes: #830844
   * modify better-compiler-flags.patch to remove -L... from the output of
 `krb5-config -libs`
 Avoids linking with (non existing) rpath. Thanks, lintian
   * Claim conformance with Policy 3.9.8
Checksums-Sha1: 
 58404629bfede5452c30128932d0b88ec538125a 2149 libauthen-krb5-perl_1.9-5.dsc
 e022b8cbf96453a630769a9e862c3e53b7e74cb8 6640 
libauthen-krb5-perl_1.9-5.debian.tar.xz
Checksums-Sha256: 
 4dbd879e8047b884ec35a07f62a6b675fa23f1b43f0350b3afdf460b41b2160c 2149 
libauthen-krb5-perl_1.9-5.dsc
 d75a213ef8a3542f48c9a32a081ef48405c704a99f22cf2ac4ebcf5b4453b080 6640 
libauthen-krb5-perl_1.9-5.debian.tar.xz
Files: 
 e1c31e82998470f144a5b0d1c0c871f8 2149 perl optional 
libauthen-krb5-perl_1.9-5.dsc
 

Bug#830844: Pending fixes for bugs in the libauthen-krb5-perl package

[Sergio Gelato]

> https://anonscm.debian.org/cgit/pkg-perl/packages/libauthen-krb5-perl.git/commit/?id=3558a41

You may have missed a documentation reference in Krb5.pm:
---
=item get_krbhst(realm)

Returns a list of the Kerberos servers from the specified realm.
---
which raises the issue of how much Perl code out there may call
Authen::Krb5::get_krbhst($realm) .

As far as my own needs are concerned it's OK to drop this function,
but it is an API change and may deserve a bump in the module's version number.

Alternatively, one could lift the implementation of krb5_get_krbhst (in terms
of profile_get_values, which is a public interface) from older libkrb5, or
provide a new one if there are licensing issues. Of course this is more
work and best left to upstream.

As a stop-gap, maybe one could keep Authen::Krb5::get_krbhst but with a
dummy implementation that always returns undef?

Processed: Re: Bug#830842: gnome-maps: MapQuest direct tile access has been discontinued

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #830842 [gnome-maps] gnome-maps: MapQuest direct tile access has been 
discontinued
Severity set to 'grave' from 'important'
> found -1 3.14.1.2-1
Bug #830842 [gnome-maps] gnome-maps: MapQuest direct tile access has been 
discontinued
Marked as found in versions gnome-maps/3.14.1.2-1.
> forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=764841
Bug #830842 [gnome-maps] gnome-maps: MapQuest direct tile access has been 
discontinued
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=764841'.

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

Bug#812293: marked as done (armagetronad: FTBFS with GCC 6: undefined reference)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 09:49:42 +
with message-id 
and subject line Bug#812293: fixed in armagetronad 0.2.8.3.3-3
has caused the Debian Bug report #812293,
regarding armagetronad: FTBFS with GCC 6: undefined reference
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.)


-- 
812293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: armagetronad
Version: 0.2.8.3.3-2
Severity: normal
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

You can find a snapshot of GCC 6 in experimental.  To build with
GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> ^~~~
> 
> mv -f .deps/armagetronad_main-gFloor.Tpo .deps/armagetronad_main-gFloor.Po
> x86_64-linux-gnu-g++   -I../../src/tools  -I../../src/render -I../../src/ui   
>   -I../../src/network -I../../src/engine  -I../../src/thirdparty/particles 
> -I../../src/tron  -g -O2 -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -Wno-long-long   -fPIE -pie -Wl,-z,relro -Wl,-z,now 
> -Wl,--as-needed -o armagetronad_main armagetronad_main-gFloor.o libtron.a 
> libenginecore.a libengine.a libnetwork.a libui.a librender.a libtools.a 
> -lpthread -lSDL_image -ljpeg -lz -lGLU -lGL -L/usr/lib/x86_64-linux-gnu -lSDL 
> -lm -lxml2   -lpng12
> libtron.a(libtron_a-gCycle.o): In function `tOutput::tOutput tColoredString>(char const*, tColoredString const&, tColoredString const&)':
> /<>/client/src/../../src/tools/tLocale.h:128: undefined 
> reference to `tOutput::operator<<(tOutput const&)'
> /<>/client/src/../../src/tools/tLocale.h:128: undefined 
> reference to `tOutput::operator<<(tOutput const&)'
> libtron.a(libtron_a-gCycle.o): In function 
> `tOutput::tOutput(char const*, tColoredString const&)':
> /<>/client/src/../../src/tools/tLocale.h:116: undefined 
> reference to `tOutput::operator<<(tOutput const&)'
> libtron.a(libtron_a-gGame.o): In function `tOutput::tOutput int>(char const*, tString const&, int const&)':
> /<>/client/src/../../src/tools/tLocale.h:128: undefined 
> reference to `tOutput::operator<<(tOutput const&)'
> libtron.a(libtron_a-gGame.o): In function `tOutput::tOutput(char 
> const*, tString const&)':
> /<>/client/src/../../src/tools/tLocale.h:116: undefined 
> reference to `tOutput::operator<<(tOutput const&)'
> libtron.a(libtron_a-gGame.o):/<>/client/src/../../src/tools/tLocale.h:116:
>  more undefined references to `tOutput::operator<<(tOutput const&)' follow
> collect2: error: ld returned 1 exit status
> Makefile:813: recipe for target 'armagetronad_main' failed
> make[5]: *** [armagetronad_main] Error 1
> make[5]: Leaving directory '/<>/client/src'
> Makefile:2392: recipe for target 'all-recursive' failed
> make[4]: *** [all-recursive] Error 1
> make[4]: Leaving directory '/<>/client/src'
> Makefile:646: recipe for target 'all-recursive' failed
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory '/<>/client'
> Makefile:463: recipe for target 'all' failed
> make[2]: *** [all] Error 2

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: armagetronad
Source-Version: 0.2.8.3.3-3

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated armagetronad 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, 12 Jul 2016 08:46:42 +0200
Source: armagetronad
Binary: armagetronad-common armagetronad armagetronad-dedicated
Architecture: source
Version: 0.2.8.3.3-3
Distribution: unstable
Urgency: 

Bug#830855: module does not compile

[Matthew Vernon]

Package: virtualbox-dkms
Version: 4.3.36-dfsg-1+deb8u1
Severity: serious

Hi,

This module does not build on my system any more (see attached log)

There appear to be at least 2 errors:

/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:581:21:
 error: implicit declaration of function ‘page_cache_release’ 
[-Werror=implicit-function-declaration]
 page_cache_release(pMemLnx->apPages[iPage]);

/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1032:14:
 error: too many arguments to function ‘get_user_pages’
 rc = get_user_pages(pTask,  /* Task for fault 
accounting. */
  ^
Regards,

Matthew

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 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: sysvinit (via /sbin/init)

Versions of packages virtualbox-dkms depends on:
ii  dkms  2.2.0.3-5

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  4.3.36-dfsg-1+deb8u1

virtualbox-dkms suggests no packages.

-- no debconf information
DKMS make.log for virtualbox-4.3.36 for kernel 4.6.0-1-amd64 (x86_64)
Tue 12 Jul 10:36:43 BST 2016
make: Entering directory '/usr/src/linux-headers-4.6.0-1-amd64'
  LD  /var/lib/dkms/virtualbox/4.3.36/build/built-in.o
  LD  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/built-in.o
  CC [M]  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/SUPDrvTracer.o
  CC [M]  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/alloc-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/initterm-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/memobj-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/mpnotification-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/powernotification-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memuserkernel-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/mp-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/mpnotification-r0drv-linux.o
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: 
In function ‘rtR0MemObjNativeFree’:
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:581:21:
 error: implicit declaration of function ‘page_cache_release’ 
[-Werror=implicit-function-declaration]
 page_cache_release(pMemLnx->apPages[iPage]);
 ^
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: 
In function ‘rtR0MemObjNativeLockUser’:
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1032:29:
 warning: passing argument 1 of ‘get_user_pages’ makes integer from pointer 
without a cast [-Wint-conversion]
 rc = get_user_pages(pTask,  /* Task for fault 
accounting. */
 ^
In file included from 
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/the-linux-kernel.h:88:0,
 from 
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31:
/usr/src/linux-headers-4.6.0-1-common/include/linux/mm.h:1288:6: note: expected 
‘long unsigned int’ but argument is of type ‘struct task_struct *’
 long get_user_pages(unsigned long start, unsigned long nr_pages,
  ^
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1033:29:
 warning: passing argument 2 of ‘get_user_pages’ makes integer from pointer 
without a cast [-Wint-conversion]
 pTask->mm,  /* Whose pages. */
 ^
In file included from 
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/the-linux-kernel.h:88:0,
 from 
/var/lib/dkms/virtualbox/4.3.36/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31:
/usr/src/linux-headers-4.6.0-1-common/include/linux/mm.h:1288:6: note: expected 
‘long unsigned int’ but argument is of type ‘struct mm_struct *’
 long get_user_pages(unsigned long start, unsigned long nr_pages,
  ^

Bug#830577: Bug#830848: notion: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

tags 830848 + patch
tags 830577 + patch
thanks

The following patch should fix both bugs.

Please make sure that not only both "dpkg-buildpackage -B" and
"dpkg-buildpackage -A" work again but also that they generate the
"same" packages as before.

Thanks.--- a/debian/rules
+++ b/debian/rules
@@ -9,7 +9,7 @@
 override_dh_auto_build:
CFLAGS="$(CFLAGS) $(CPPFLAGS)" dh_auto_build
 
-override_dh_installman:
+override_dh_installman-arch:
for langdir in debian/tmp/usr/share/man/*; do   
\
lang=`basename $$langdir`;  
\
test $$lang = "man1" || dh_installman --language $$lang 
debian/tmp/usr/share/man/$$lang/man1/*; \
@@ -21,12 +21,12 @@ override_dh_installman:
 override_dh_auto_test:
true
 
-override_dh_installmenu:
+override_dh_installmenu-arch:
dh_installmenu
install -m644 debian/notion.menu-method.i18n \
debian/notion/etc/menu-methods/notion-i18n
 
-override_dh_install:
+override_dh_install-indep:
dh_install
 
# install headers
@@ -34,8 +34,12 @@ override_dh_install:
-prune -o -name '*.h' -exec install -m644 -D {} \
debian/notion-dev/usr/include/notion/{} \;
 
+override_dh_fixperms-indep:
+   dh_fixperms
# this needs to be executable
chmod a+x debian/notion-dev/usr/lib/notion/libextl/libextl-mkexports
 
+override_dh_install-arch:
+   dh_install
# notionflux should go into /usr/bin. The upstream install should 
probably do this
mv debian/notion/usr/lib/notion/notionflux debian/notion/usr/bin

Processed: Re: Bug#830848: notion: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Debian Bug Tracking System]

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

> tags 830848 + patch
Bug #830848 [src:notion] notion: FTBFS when built with dpkg-buildpackage -A (No 
such file or directory)
Added tag(s) patch.
> tags 830577 + patch
Bug #830577 [src:notion] notion: FTBFS in binary-arch only build: chmod: cannot 
access 'debian/notion-dev/usr/lib/notion/libextl/libextl-mkexports': No such 
file or directory
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#797280: Please help porting cufflinks to latest libboost

[Andreas Tille]

Hi,

in my last commit I tried to build cufflinks[1] against libboost 1.60
but failed.  Since the failure does not seem to related to libboost I
wonder whether somebody might be able to understand and fix this issue:

...
In file included from /usr/include/eigen3/Eigen/Core:297:0,
 from /usr/include/eigen3/Eigen/Dense:1,
 from abundances.h:21,
 from abundances.cpp:16:
/usr/include/eigen3/Eigen/src/Core/DenseCoeffsBase.h: In instantiation of 
'Eigen::DenseCoeffsBase::CoeffReturnType 
Eigen::DenseCoeffsBase::coeff(Eigen::Index) const [with Derived = 
Eigen
/usr/include/eigen3/Eigen/src/Core/DenseCoeffsBase.h:181:19:   required from 
'Eigen::DenseCoeffsBase::CoeffReturnType 
Eigen::DenseCoeffsBase::operator()(Eigen::Index) const [with Derived
abundances.cpp:3815:28:   required from here
/usr/include/eigen3/Eigen/src/Core/DenseCoeffsBase.h:141:7: error: 
'THIS_COEFFICIENT_ACCESSOR_TAKING_ONE_ACCESS_IS_ONLY_FOR_EXPRESSIONS_ALLOWING_LINEAR_ACCESS'
 is not a member of 'Eigen::internal::static_assert
   EIGEN_STATIC_ASSERT(internal::evaluator::Flags & 
LinearAccessBit,
   ^
Makefile:1627: recipe for target 'abundances.o' failed
...

Any help would be welcome

 Andreas.

[1] https://anonscm.debian.org/git/debian-med/cufflinks.git

-- 
http://fam-tille.de

Processed: Pending fixes for bugs in the libauthen-krb5-perl package

[Debian Bug Tracking System]

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

> tag 830844 + pending
Bug #830844 [libauthen-krb5-perl] Krb5.so fails to load: missing symbol 
krb5_free_krbhst
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#830844: Pending fixes for bugs in the libauthen-krb5-perl package

[pkg-perl-maintainers]

tag 830844 + pending
thanks

Some bugs in the libauthen-krb5-perl package are closed in revision
3558a417d93db006bc0d2f30034638590d98631e in branch 'master' by Damyan
Ivanov

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libauthen-krb5-perl.git/commit/?id=3558a41

Commit message:

add patch removing references to obsolete krb5_{get,free}_krbhst

Thanks to Sergio Gelato. Closes: #830844

Processed: typo in rsbackup changelog -> wrong bug closed by upload

[Debian Bug Tracking System]

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

> reopen 811750
Bug #811750 {Done: Matthew Vernon } [re] FTBFS with GCC 6: 
narrowing conversion
'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 rsbackup/3.1-2.
> quit
Stopping processing here.

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

Bug#811705: marked as done (FTBFS with GCC 6: throw will always call terminate)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 08:45:51 +0100
with message-id <9eb19eaf-3451-82b9-94f6-aa45b51fe...@debian.org>
and subject line fix correct bug number
has caused the Debian Bug report #811705,
regarding FTBFS with GCC 6: throw will always call terminate
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.)


-- 
811705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rsbackup
Version: 3.0-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-terminate

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html
> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
TBM
> g++ -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Wall -W 
> -Werror -Wpointer-arith -Wwrite-strings -MT EventLoop.o -MD -MP -MF 
> .deps/EventLoop.Tpo -c -o EventLoop.o EventLoop.cc
> EventLoop.cc: In destructor 'virtual EventLoop::~EventLoop()':
> EventLoop.cc:74:43: error: throw will always call terminate() 
> [-Werror=terminate]
>  throw SystemError("sigprocmask", errno);
>^
> 
> EventLoop.cc:74:43: note: in C++11 destructors default to noexcept
> cc1plus: all warnings being treated as errors
> Makefile:964: recipe for target 'EventLoop.o' failed
> make[3]: *** [EventLoop.o] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---

fixed 811705 3.1-1
quit

Hi,

The changelog for 3.1-1 closed 811750 by mistake, it should have closed 
811705; I've re-opened 811750, and with this email close 811705.


Regards,

Matthew--- End Message ---

Processed: notfound 828853 in 1.4.D001-2+b1, found 828853 in 1.4.D001-2, tagging 753510 ..., tagging 829488 ...

[Debian Bug Tracking System]

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

> notfound 828853 1.4.D001-2+b1
Bug #828853 [libexplain] libexplain: FTBFS on mips and mipsel - 'FS_ECOMPR_FL' 
undeclared
There is no source info for the package 'libexplain' at version '1.4.D001-2+b1' 
with architecture ''
Unable to make a source version for version '1.4.D001-2+b1'
No longer marked as found in versions 1.4.D001-2+b1.
> found 828853 1.4.D001-2
Bug #828853 [libexplain] libexplain: FTBFS on mips and mipsel - 'FS_ECOMPR_FL' 
undeclared
There is no source info for the package 'libexplain' at version '1.4.D001-2' 
with architecture ''
Unable to make a source version for version '1.4.D001-2'
Marked as found in versions 1.4.D001-2.
> tags 753510 + sid
Bug #753510 [liblognorm1] liblognorm1 - Conflicts against liblognorm0 without 
justification
Added tag(s) sid.
> found 830755 0.37.2-6
Bug #830755 {Done: bott...@debian.org (A. Maitland Bottoms)} 
[libgnuradio-iqbalance0,libgnuradio-iqbalance3.7.10] 
libgnuradio-iqbalance3.7.10 and libgnuradio-iqbalance0: error when trying to 
install together
There is no source info for the package 'libgnuradio-iqbalance0' at version 
'0.37.2-6' with architecture ''
Marked as found in versions gr-iqbal/0.37.2-6.
> found 830755 0.37.2-5
Bug #830755 {Done: bott...@debian.org (A. Maitland Bottoms)} 
[libgnuradio-iqbalance0,libgnuradio-iqbalance3.7.10] 
libgnuradio-iqbalance3.7.10 and libgnuradio-iqbalance0: error when trying to 
install together
There is no source info for the package 'libgnuradio-iqbalance3.7.10' at 
version '0.37.2-5' with architecture ''
Marked as found in versions gr-iqbal/0.37.2-5.
> found 830754 3.7.25.4b6464b-1
Bug #830754 {Done: bott...@debian.org (A. Maitland Bottoms)} 
[libgnuradio-fcdproplus0,libgnuradio-fcdproplus3.7.10] 
libgnuradio-fcdproplus3.7.10 and libgnuradio-fcdproplus0: error when trying to 
install together
There is no source info for the package 'libgnuradio-fcdproplus0' at version 
'3.7.25.4b6464b-1' with architecture ''
Marked as found in versions gr-fcdproplus/3.7.25.4b6464b-1.
> found 830754 3.7.24.cf5db38-5+b1
Bug #830754 {Done: bott...@debian.org (A. Maitland Bottoms)} 
[libgnuradio-fcdproplus0,libgnuradio-fcdproplus3.7.10] 
libgnuradio-fcdproplus3.7.10 and libgnuradio-fcdproplus0: error when trying to 
install together
There is no source info for the package 'libgnuradio-fcdproplus3.7.10' at 
version '3.7.24.cf5db38-5+b1' with architecture ''
Marked as found in versions gr-fcdproplus/3.7.24.cf5db38-5.
> tags 829488 + sid stretch
Bug #829488 [util-linux] util-linux should depend on init-system-helpers
Added tag(s) sid and stretch.
> tags 825907 + sid stretch
Bug #825907 [src:openjpeg] Remove OpenJPEG 1.5 from Debian archive
Bug #826805 [src:openjpeg] Remove OpenJPEG for stretch
Added tag(s) sid and stretch.
Added tag(s) sid and stretch.
> reassign 516200 src:isc-dhcp 3.0.6.dfsg-1ubuntu9
Bug #516200 [3.0.6.dfsg-1ubuntu9] dhcp3-common: dhcp-eval update, .SH SECURITY
Warning: Unknown package '3.0.6.dfsg-1ubuntu9'
Bug reassigned from package '3.0.6.dfsg-1ubuntu9' to 'src:isc-dhcp'.
Ignoring request to alter found versions of bug #516200 to the same values 
previously set
Ignoring request to alter fixed versions of bug #516200 to the same values 
previously set
Bug #516200 [src:isc-dhcp] dhcp3-common: dhcp-eval update, .SH SECURITY
The source 'isc-dhcp' and version '3.0.6.dfsg-1ubuntu9' do not appear to match 
any binary packages
Marked as found in versions isc-dhcp/3.0.6.dfsg-1ubuntu9.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
516200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516200
753510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753510
825907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825907
826805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826805
828853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828853
829488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829488
830754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830754
830755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: fix correct bug number

[Debian Bug Tracking System]

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

> fixed 811705 3.1-1
Bug #811705 [rsbackup] FTBFS with GCC 6: throw will always call terminate
There is no source info for the package 'rsbackup' at version '3.1-1' with 
architecture ''
Unable to make a source version for version '3.1-1'
Marked as fixed in versions 3.1-1.
> quit
Stopping processing here.

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

Bug#830500: redis: FTBFS: Test failure

[Chris Lamb]

> Hmm, I wonder if this might be a failure that only occurs randomly,
> based on timing or something like that.

This could be right - there seems to be some "sleep" and "delay" calls
in there. Will try building a few times..


Regards,

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

Processed: Re: Bug#808433: nethogs STILL crashes in STABLE (Jessie), two months after bug was closed

[Debian Bug Tracking System]

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

> fixed 808433 0.8.1-1~bpo8+1
Bug #808433 {Done: Arnout Engelen } [nethogs] nethogs 
doesn't start, saying "creating socket failed"
Bug #811273 {Done: Arnout Engelen } [nethogs] nethogs: 
creating socket failed while establishing local IP
Marked as fixed in versions nethogs/0.8.1-1~bpo8+1.
Marked as fixed in versions nethogs/0.8.1-1~bpo8+1.
> user product...@infomaniak.com
Setting user to product...@infomaniak.com (was luca.cape...@infomaniak.com).
> usertag 808433 + infomaniak.com-network
There were no usertags set.
Usertags are now: infomaniak.com-network.
> thanks
Stopping processing here.

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

Bug#808433: nethogs STILL crashes in STABLE (Jessie), two months after bug was closed

[Luca Capello]

fixed 808433 0.8.1-1~bpo8+1
user product...@infomaniak.com
usertag 808433 + infomaniak.com-network
thanks

Hi there,

On Sun, 12 Jun 2016 10:01:20 +0200, S. G. wrote:
> I'm desparately waiting to see this fix in jessie.
> 
> Is there a schedule for patching 0.8.0?

No need for a jessie-pu, the problem is fixed for us using the
jessie-backports package (bug updated).

Thx, bye,
Gismo / Luca

-- 
Luca Capello
Administrateur GNU/Linux

Infomaniak Network SA


signature.asc
Description: Digital signature

Bug#631067: marked as done (abuse-frabs: Claudio add-on does not allow distribution or commercial use)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 10:08:26 +0200
with message-id <4ea10691-6f6c-182f-9e39-1f1c8fa4b...@debian.org>
and subject line abuse-frabs was removed from Debian in 2011
has caused the Debian Bug report #631067,
regarding abuse-frabs: Claudio add-on does not allow distribution or commercial 
use
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.)


-- 
631067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: abuse-frabs
Version: 2.11-1
Severity: serious
Justification: Policy 2.1.1, 2.1.6
User: gnewsense-...@nongnu.org
Usertags: gnewsense libreplanet

The license notice in addon/claudio/claudio.lsp does not allow distribution or
commercial use. It probably applies to all files in addon/claudio.

* NOTE: This and all other files by Claudio Bolzoni contained in the archive
  *
* claudio(1.5).zip  can be used and modified freely for non-commercial 
purposes,  *
* but credits must be given to the author.  
  *
* If you intend to distribute any file, however, contact Claudio Bolzoni.   
  *
* If you want to use work done by other people than Claudio Bolzoni, contact 
the author   *
* of that work (credits are given to those authors in this file).   
  *

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

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages abuse-frabs depends on:
ii  abuse 1:0.7.1-1  SDL port of the Abuse action game

abuse-frabs recommends no packages.

abuse-frabs suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 2.11-1+rm

abuse-frabs was last released with Debian 6.0 (squeeze) in
February 2011 and removed from Debian sid/unstable later in 2011 (see
http://bugs.debian.org/626551 for details on the removal). Since
support for squeeze and squeeze-LTS has now ended, I'm closing all the
remaining bugs reported against this package.


Andreas--- End Message ---

Bug#663363: marked as done (mongrel: FTBFS: ./test/test_command.rb:9: uninitialized constant GemPlugin (NameError))

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 10:01:26 +0200
with message-id <0e1d189c-b6c5-13e5-597c-b80f04252...@debian.org>
and subject line mongrel was removed from Debian in 2012
has caused the Debian Bug report #663363,
regarding mongrel: FTBFS: ./test/test_command.rb:9: uninitialized constant 
GemPlugin (NameError)
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.)


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

Source: mongrel
Version: 1.1.5-6
Severity: serious
Justification: fails to build from source

mongrel FTBFS:
| /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby 
/usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb
| ./test/test_command.rb:9: uninitialized constant GemPlugin (NameError)
|   from /usr/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:36:in 
`gem_original_require'
|   from /usr/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:36:in 
`require'
|   from -e:1
|   from -e:1:in `each'
|   from -e:1
| ERROR: Test "ruby1.8" failed. Exiting.
| dh_auto_install: dh_ruby --install 
/build/buildd-mongrel_1.1.5-6-i386-l5Ty40/mongrel-1.1.5/debian/mongrel returned 
exit code 1
| make: *** [binary-arch] Error 1

Full build log:
https://buildd.debian.org/status/fetch.php?pkg=mongrel=i386=1.1.5-6=1326602601

--
Jakub Wilk


--- End Message ---
--- Begin Message ---
Version: 1.1.5-6+rm

mongrel was last released with Debian 6.0 (squeeze) in
February 2011 and removed from Debian sid/unstable in 2012 (see
http://bugs.debian.org/663921 for details on the removal). Since
support for squeeze and squeeze-LTS has now ended, I'm closing all the
remaining bugs reported against this package.

Andreas--- End Message ---

Bug#822128: marked as done (Boost 1.55 to be removed; your attention required)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 09:28:32 +0200
with message-id <20160712072832.gc5...@an3as.eu>
and subject line Ball builds with higher boost versions
has caused the Debian Bug report #822128,
regarding Boost 1.55 to be removed; your attention required
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.)


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

Boost 1.55 has not built correctly since the GCC 5 introduction in July 2015 
and I plan
to ask for its removal from unstable very shortly.  It has already been removed 
from
testing.

The package ball appeared on a list of reverse dependencies generated 
using 'dak rm -Rn boost1.55' (see below).  This bug is to request an
upload with updated boost dependencies.

If your package build-depends on the default boost, then a simple rebuild will 
suffice.
If your package uses 1.55-versioned build-deps, then please check whether you 
can
move to default boost.  Or if not, at least move to 1.58.

Output from ssh mirror.ftp-master.debian.org "dak rm -Rn boost1.55" follows.

Checking reverse dependencies...
# Broken Depends:
ball: ballview [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libball1.4 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libballview1.4 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  python-ball [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  python-ballview [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
cufflinks/non-free: cufflinks [amd64]
diet: diet-agent [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libdiet-admin2.8 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libdiet-client2.8 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libdiet-dagda2.8 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
  libdiet-sed2.8 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc ppc64el s390x]
feel++: feel++-apps [amd64 i386 powerpc]
libfeel++1 [amd64 i386 powerpc]
gqrx-sdr: gqrx-sdr [kfreebsd-amd64 kfreebsd-i386]
gr-air-modes: gr-air-modes [kfreebsd-amd64 kfreebsd-i386]
  libair-modes0 [kfreebsd-amd64 kfreebsd-i386]
gr-osmosdr: gr-osmosdr [kfreebsd-amd64 kfreebsd-i386]
libgnuradio-osmosdr0.1.3 [kfreebsd-amd64 kfreebsd-i386]
kig: kig [hurd-i386]
librime: librime-bin [hurd-i386]
 librime1 [hurd-i386]
limereg: limereg [mips mipsel]
mongodb: mongodb-clients [hurd-i386 kfreebsd-i386]
 mongodb-server [hurd-i386 kfreebsd-i386]
openvrml: libopenvrml9 [amd64 armel armhf i386 mips mipsel powerpc ppc64el 
s390x]
  openvrml-lookat [amd64 armel armhf i386 mips mipsel powerpc ppc64el 
s390x]
pcb2gcode: pcb2gcode [kfreebsd-amd64 kfreebsd-i386]
qbittorrent: qbittorrent [kfreebsd-amd64 kfreebsd-i386]
 qbittorrent-nox [kfreebsd-amd64 kfreebsd-i386]
qpid-cpp: libqpidcommon2 [amd64 arm64 i386 mipsel powerpc ppc64el]
  qpidd [amd64 arm64 i386 mipsel powerpc ppc64el]
smc: smc [amd64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel 
powerpc s390x]
swift-im: libswiften-dev [amd64 arm64 armel armhf i386 mips mipsel powerpc 
ppc64el s390x]
  libswiften2 [amd64 arm64 armel armhf i386 mips mipsel powerpc ppc64el 
s390x]
  swift-im [amd64 arm64 armel armhf i386 mips mipsel powerpc ppc64el 
s390x]
--- End Message ---
--- Begin Message ---
Hi,

I'm manually closing this bug since it was just missing in changelog.

Kind regards

Andreas.

-- 
http://fam-tille.de--- End Message ---

Bug#830844: Krb5.so fails to load: missing symbol krb5_free_krbhst

[Sergio Gelato]

Package: libauthen-krb5-perl
Version: 1.9-4
Severity: serious

$ env PERL_DL_NONLAZY=1 perl -MAuthen::Krb5 -e '1;'
Can't load '/usr/lib/i386-linux-gnu/perl5/5.20/auto/Authen/Krb5/Krb5.so' for 
module Authen::Krb5: 
/usr/lib/i386-linux-gnu/perl5/5.20/auto/Authen/Krb5/Krb5.so: undefined symbol: 
krb5_free_krbhst at /usr/lib/i386-linux-gnu/perl/5.20/DynaLoader.pm line 187.
 at -e line 0.
Compilation failed in require.
BEGIN failed--compilation aborted.

This breaks test suites or anything else that sets PERL_DL_NONLAZY=1.

The problem is that this module uses an internal MIT Kerberos API that has
been removed. From Krb5.xs:

/*
 * These are internal Kerberos library functions that aren't prototyped and
 * that we probably shouldn't be calling.  Prototype them with the arguments
 * we expect and leave them for now pending an API cleanup.
 */
krb5_error_code krb5_free_krbhst(krb5_context, char * const *);
krb5_error_code krb5_get_krbhst(krb5_context, const krb5_data *, char ***);

And from the changelog (doc/CHANGES) for package krb5:

commit 81fde7e475b02986c1aff88766cc48882004d5dc
Author: Greg Hudson 
Date:   Fri Mar 22 16:00:48 2013 -0400

Get rid of krb5_{get,free}_krbhst

These functions were always internal.  They haven't been used since
v5passwdd was eliminated in krb5 1.4.

Bug#830384: marked as done (ruby-file-tail: FTBFS: ERROR: Test "ruby2.3" failed.)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 07:34:45 +
with message-id 
and subject line Bug#830384: fixed in ruby-file-tail 1.1.1-1
has caused the Debian Bug report #830384,
regarding ruby-file-tail: FTBFS: ERROR: Test "ruby2.3" failed.
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-tests.rb 
>  │
> └──┘
> 
> RUBYLIB=/«PKGBUILDDIR»/debian/ruby-file-tail/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=debian/ruby-file-tail/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 debian/ruby-tests.rb
> Loaded suite debian/ruby-tests
> Started
> /«PKGBUILDDIR»/tests/file_tail_test.rb:301:in `block in test_tail_change': 
> Object#timeout is deprecated, use Timeout.timeout instead.
> /«PKGBUILDDIR»/tests/file_tail_test.rb:306: warning: constant 
> FileTailTest::TimeoutError is deprecated
> ..F
> ===
> Failure: test_tail_change(FileTailTest)
> /«PKGBUILDDIR»/tests/file_tail_test.rb:320:in `test_tail_change'
>  317: end
>  318: appender.join
>  319: logger.join
>   => 320: assert_equal(110, lines.size)
>  321: assert reopened
>  322: assert_equal 10, @in.lineno
>  323:   end
> <110> expected but was
> <100>
> 
> diff:
> ? 1100
> /«PKGBUILDDIR»/tests/file_tail_test.rb:334:in `block in test_tail_change2': 
> Object#timeout is deprecated, use Timeout.timeout instead.
> ===
> /«PKGBUILDDIR»/tests/file_tail_test.rb:197:in `block in test_tail_remove': 
> Object#timeout is deprecated, use Timeout.timeout instead.
> /«PKGBUILDDIR»/tests/file_tail_test.rb:202: warning: constant 
> FileTailTest::TimeoutError is deprecated
> /«PKGBUILDDIR»/tests/file_tail_test.rb:228:in `block in test_tail_remove2': 
> Object#timeout is deprecated, use Timeout.timeout instead.
> /«PKGBUILDDIR»/tests/file_tail_test.rb:233: warning: constant 
> FileTailTest::TimeoutError is deprecated
> ..F
> ===
> Failure: test_tail_remove2(FileTailTest)
> /«PKGBUILDDIR»/tests/file_tail_test.rb:252:in `test_tail_remove2'
>  249: end
>  250: appender.join
>  251: logger.join
>   => 252: assert_equal(30, lines.size)
>  253: assert reopened
>  254:   end
>  255: 
> <30> expected but was
> <10>
> 
> diff:
> ? 30
> ? 1 
> /«PKGBUILDDIR»/tests/file_tail_test.rb:264:in `block in test_tail_remove3': 
> Object#timeout is deprecated, use Timeout.timeout instead.
> ===
> /«PKGBUILDDIR»/tests/file_tail_test.rb:167:in `block in test_tail_truncated': 
> Object#timeout is deprecated, use Timeout.timeout instead.
> /«PKGBUILDDIR»/tests/file_tail_test.rb:172: warning: constant 
> FileTailTest::TimeoutError is deprecated
> /«PKGBUILDDIR»/tests/file_tail_test.rb:93:in `test_tail_with_block_with_n': 
> Object#timeout is deprecated, use Timeout.timeout instead.
> /«PKGBUILDDIR»/tests/file_tail_test.rb:96:in `block in 
> test_tail_with_block_with_n': Object#timeout is deprecated, use 
> Timeout.timeout instead.
> /«PKGBUILDDIR»/tests/file_tail_test.rb:101:in `block in 
> test_tail_with_block_with_n': Object#timeout is deprecated, use 
> Timeout.timeout instead.
> /«PKGBUILDDIR»/tests/file_tail_test.rb:106:in `block in 
> test_tail_with_block_with_n': Object#timeout is deprecated, use 
> Timeout.timeout instead.
> /«PKGBUILDDIR»/tests/file_tail_test.rb:112: warning: constant 
> FileTailTest::TimeoutError is deprecated
> /«PKGBUILDDIR»/tests/file_tail_test.rb:113:in `block (2 levels) in 
> test_tail_with_block_with_n': Object#timeout 

Bug#830097: marked as done (Could not find 'tins' (~> 1.0))

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 07:34:45 +
with message-id 
and subject line Bug#830097: fixed in ruby-file-tail 1.1.1-1
has caused the Debian Bug report #830097,
regarding Could not find 'tins' (~> 1.0)
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.)


-- 
830097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-file-tail
Version: 1.1.0-1
Severity: serious
X-Debbugs-CC: debian-r...@lists.debian.org

Dear Maintainer,

your gem library fails to load on ruby2.3:

% ruby -e 'gem "file-tail"' 
   
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'tins' (~> 1.0) among 137 total gem(s) (Gem::LoadError)
[...]

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-
--- End Message ---
--- Begin Message ---
Source: ruby-file-tail
Source-Version: 1.1.1-1

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

Debian distribution maintenance software
pp.
Lucas Albuquerque Medeiros de Moura  (supplier of 
updated ruby-file-tail 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, 11 Jul 2016 17:38:03 -0300
Source: ruby-file-tail
Binary: ruby-file-tail
Architecture: source
Version: 1.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Lucas Albuquerque Medeiros de Moura 
Description:
 ruby-file-tail - Ruby library for following still-growing files
Closes: 830097 830384
Changes:
 ruby-file-tail (1.1.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release (Closes: #830384)
   * debian/control: Add missing dependency ruby-tins (Closes: #830097)
   * Bump standards-version to 3.9.8
Checksums-Sha1:
 fa99d2ad058a28a03fc7842acbcc2d765cec364e 2110 ruby-file-tail_1.1.1-1.dsc
 cdcc49b92091bc8b01b5416bab8b6e82d9531112 19185 ruby-file-tail_1.1.1.orig.tar.gz
 591dbc3f9da5e9cf1fab36f832cf4909e8bdb252 2364 
ruby-file-tail_1.1.1-1.debian.tar.xz
Checksums-Sha256:
 3775df55f0f4b9174d994e1afeee1ecddc20b9595f8e190254381604ed18f10c 2110 
ruby-file-tail_1.1.1-1.dsc
 81b2e82ab69aa94662b72ccda39388190c168b09cc9b1b202ecfe5fd46e7db01 19185 
ruby-file-tail_1.1.1.orig.tar.gz
 1108973165217d04fbfd22bc5ad3228fda1019ac3fcecf3b7b2c5c6d42cfcc68 2364 
ruby-file-tail_1.1.1-1.debian.tar.xz
Files:
 af421a99f15d89759e4f3145759ab545 2110 ruby optional ruby-file-tail_1.1.1-1.dsc
 e629ebe65e85c6bc34169044561dfbca 19185 ruby optional 
ruby-file-tail_1.1.1.orig.tar.gz
 00c2d8d86a9b7a75359a97ee5b05d21a 2364 ruby optional 
ruby-file-tail_1.1.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXhJzaAAoJEFwT1tuTBS4Dsx4QAKjOEwVTHVg+HuwfoVKYLvEV
52C1vfBOLH4D+FpHBH0XU6KVNTYyrsEhELJiusx22/T0sLJN6RuUhA6T+XxUYCi2
hWZXvkHor6Bep3m1M3JImdtyVEqN2xAYTyY4psZXms897CO7RV68V52ZuJPXW55D
kAJGdDNg2TJO8ddmQQeEiTZIp5NvVcZJSeD0AOfH7Ke8wn/8Wos3+utUGQSXoVI0
QyTyYaabkO1tP9I01wsH+7Qv46s+VU+9nl7/IlEpHB96NRMaZW0wSUOyuEXGkdeO
iFNAOExlJELD8n9Lmc/588FpiuLQQSCXWEVQ4Nxe+tXMLy7kVVEm89Qnk3H4SuCM
Kl/aC5TOWLaTzjEih08N0eAVQxho1Eje93uI6PkRxeKmKq5QxxRlB5VrFdN3tGLv
648URBbS3kDjDEbOmcpj0HGEMNJ9nntgdEpUs4RCWpMQ+fs/5VyRwV/2YXgDsuXc
gIF6Mz+xiu5UVcyN+aoX0ZIWoPiqsfABBFfUj03QKocC4W5wWt24E5xhX/VgIUWD
LSxKFuXl8ZQNHC/eOja8DFaWDQbW6JErVgxCFGQtUfpPzZ2rnqPZiydkQo1MGBtk
xc3nLS7xMzM/qbIW+HKyiDqyWTpRctLydb+gnqSQbes8v/J6qTp3soof5+x/87/G
050UhoOFl3CnoqKO64iq
=xZ8Q
-END PGP SIGNATURE End Message ---

Bug#811815: marked as done (murasaki: FTBFS with GCC 6: no match for)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 07:34:39 +
with message-id 
and subject line Bug#811815: fixed in murasaki 1.68.6-6
has caused the Debian Bug report #811815,
regarding murasaki: FTBFS with GCC 6: no match for
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.)


-- 
811815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: murasaki
Version: 1.68.6-4
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-no-match

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> mpicxx -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -g 
> -I/usr/include/pstreams -Wall  -DMURASAKI_MPI -DUSE_SHM_SYSV 
> -DLARGESEQ_SUPPORT -DUSE_LIBCRYPTOPP -fno-strict-aliasing -c dinkymath.cc
> In file included from /usr/lib/openmpi/include/mpi.h:253:0,
>  from murasaki_mpi.h:33,
>  from shmvector.hh:30,
>  from sequence.h:44,
>  from murasaki.h:24,
>  from dinkymath.cc:27:
> /usr/lib/openmpi/include/mpi_portable_platform.h:374:34: warning: invalid 
> suffix on literal; C++11 requires a space between literal and string macro 
> [-Wliteral-suffix]
>   
> _STRINGIFY(__GNUC__)"."_STRINGIFY(__GNUC_MINOR__)"."_STRINGIFY(__GNUC_PATCHLEVEL__)
>   ^
> 
> /usr/lib/openmpi/include/mpi_portable_platform.h:374:63: warning: invalid 
> suffix on literal; C++11 requires a space between literal and string macro 
> [-Wliteral-suffix]
>   
> _STRINGIFY(__GNUC__)"."_STRINGIFY(__GNUC_MINOR__)"."_STRINGIFY(__GNUC_PATCHLEVEL__)
>^
> 
> dinkymath.cc: In function 'std::__cxx11::string littleEndianStr(unsigned int, 
> int)':
> dinkymath.cc:40:7: warning: variable 'last' set but not used 
> [-Wunused-but-set-variable]
>int last=0;
>^~~~
> 
> dinkymath.cc: In function 'std::__cxx11::string littleEndianPat(unsigned int, 
> int)':
> dinkymath.cc:53:7: warning: variable 'last' set but not used 
> [-Wunused-but-set-variable]
>int last=0;
>^~~~
> 
> mpicxx -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -g 
> -I/usr/include/pstreams -Wall  -DMURASAKI_MPI -DUSE_SHM_SYSV 
> -DLARGESEQ_SUPPORT -DUSE_LIBCRYPTOPP -fno-strict-aliasing -c sequence.cc
> In file included from /usr/lib/openmpi/include/mpi.h:253:0,
>  from murasaki_mpi.h:33,
>  from shmvector.hh:30,
>  from sequence.h:44,
>  from murasaki.h:24,
>  from sequence.cc:28:
> /usr/lib/openmpi/include/mpi_portable_platform.h:374:34: warning: invalid 
> suffix on literal; C++11 requires a space between literal and string macro 
> [-Wliteral-suffix]
>   
> _STRINGIFY(__GNUC__)"."_STRINGIFY(__GNUC_MINOR__)"."_STRINGIFY(__GNUC_PATCHLEVEL__)
>   ^
> 
> /usr/lib/openmpi/include/mpi_portable_platform.h:374:63: warning: invalid 
> suffix on literal; C++11 requires a space between literal and string macro 
> [-Wliteral-suffix]
>   
> _STRINGIFY(__GNUC__)"."_STRINGIFY(__GNUC_MINOR__)"."_STRINGIFY(__GNUC_PATCHLEVEL__)
>^
> 
> sequence.cc: In destructor 'Sequence::~Sequence()':
> sequence.cc:377:123: warning: throw will always call terminate() [-Wterminate]
>   throw MurasakiException("Couldn't mark System V IPC shared memory region 
> for deletion for sequence "+name+strerror(errno));
>   
>  ^
> 
> sequence.cc:377:123: note: in C++11 destructors default to noexcept
> sequence.cc: In destructor 'BitSequence::~BitSequence()':
> sequence.cc:1394:133: warning: throw will always call terminate() 
> [-Wterminate]
>   throw MurasakiException("Couldn't detach System V shared memory region for 
> "+(seq ? seq->filename:string("(anon)"))+strerror(errno));
>

Bug#830843: varnish-modules: accesses the internet during build

[Chris Lamb]

Source: varnish-modules
Version: 0.9.0-3
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst varnish-modules builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

  00:00:00.00 IP e66b957b9098.60905 > sitecomwlr1000.sitecomwlr1000.domain: 
10880+ A? phk.freebsd.dk. (32)
  00:00:00.60 IP e66b957b9098.60905 > sitecomwlr1000.sitecomwlr1000.domain: 
24843+ ? phk.freebsd.dk. (32)
  00:00:00.001007 IP e66b957b9098.54550 > sitecomwlr1000.sitecomwlr1000.domain: 
27794+ A? phk.freebsd.dk. (32)
  00:00:00.001044 IP e66b957b9098.54550 > sitecomwlr1000.sitecomwlr1000.domain: 
39210+ ? phk.freebsd.dk. (32)
  00:00:00.001129 IP e66b957b9098.45718 > sitecomwlr1000.sitecomwlr1000.domain: 
1+ A? phk.freebsd.dk. (32)
  00:00:00.001152 IP e66b957b9098.45718 > sitecomwlr1000.sitecomwlr1000.domain: 
3037+ ? phk.freebsd.dk. (32)

  [..]

The full build log (including tcpdump output) is attached.


Regards,

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


varnish-modules.0.9.0-3.unstable.amd64.log.txt.gz
Description: Binary data

Processed: Re: Bug#830776: ganeti: Upgrade 2.5.2 (wheezy) -> 2.12.4 (jessie) fails

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo + wontfix
Bug #830776 [ganeti] ganeti: Upgrade 2.5.2 (wheezy) -> 2.12.4 (jessie) fails
Removed tag(s) moreinfo.
Bug #830776 [ganeti] ganeti: Upgrade 2.5.2 (wheezy) -> 2.12.4 (jessie) fails
Added tag(s) wontfix.
> severity -1 normal
Bug #830776 [ganeti] ganeti: Upgrade 2.5.2 (wheezy) -> 2.12.4 (jessie) fails
Severity set to 'normal' from 'critical'

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

Bug#830776: ganeti: Upgrade 2.5.2 (wheezy) -> 2.12.4 (jessie) fails

[Apollon Oikonomopoulos]

Control: tags -1 - moreinfo + wontfix
Control: severity -1 normal

[Please keep @bugs.debian.org Cc'd when replying to bugs :)]

Hi,

On 08:21 Tue 12 Jul , Stefan Nitz wrote:
> Hi,
> 
> great thank you very much!
> 
> And no. i followed this:
> 
> https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#ganeti-upgrade-issues
> 
>  Because i thought that the debian upgrade skript do it all
> automatically, i do not follow the link. I thought hint it is only
> needed for DRBD.

Unfortunately cfgupgrade must be run by hand in this case. However all 
your future upgrades will be done using gnt-cluster upgrade, which takes 
care of running cfgupgrade automatically.

Anyway, good to know it worked for you!

Regards,
Apollon

Bug#812034: marked as done (klick: FTBFS with GCC 6: needed for in-class initialization)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 07:05:02 +
with message-id 
and subject line Bug#812034: fixed in klick 0.12.2-3
has caused the Debian Bug report #812034,
regarding klick: FTBFS with GCC 6: needed for in-class initialization
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.)


-- 
812034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: klick
Version: 0.12.2-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -o src/klick.o -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -W -Wall 
> -DVERSION=\"0.12.2\" -DDATA_DIR=\"/usr/share/klick\" -DHAVE_SNDFILE_OGG 
> -DENABLE_OSC -DENABLE_TERMINAL -DENABLE_RUBBERBAND src/klick.cc
> In file included from src/klick.cc:26:0:
> src/metronome_map.hh:51:42: error: 'constexpr' needed for in-class 
> initialization of static data member 'const double 
> MetronomeMap::TICKS_PER_BEAT' of non-integral type [-fpermissive]
>  static double const TICKS_PER_BEAT = 1920.0;
>   ^~
> 
> In file included from src/klick.cc:28:0:
> src/metronome_simple.hh:62:38: error: 'constexpr' needed for in-class 
> initialization of static data member 'const float 
> MetronomeSimple::MAX_TAP_AGE' of non-integral type [-fpermissive]
>  static float const MAX_TAP_AGE = 3.0;
>   ^~~
> 
> src/metronome_simple.hh:63:35: error: 'constexpr' needed for in-class 
> initialization of static data member 'const float MetronomeSimple::TAP_DIFF' 
> of non-integral type [-fpermissive]
>  static float const TAP_DIFF = 0.2;
>^~~
> 
> scons: *** [src/klick.o] Error 1
> scons: building terminated because of errors.

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: klick
Source-Version: 0.12.2-3

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

Debian distribution maintenance software
pp.
Jaromír Mikeš  (supplier of updated klick 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: SHA1

Format: 1.8
Date: Mon, 11 Jul 2016 23:35:56 +0200
Source: klick
Binary: klick
Architecture: source amd64
Version: 0.12.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jaromír Mikeš 
Description:
 klick  - advanced metronome for JACK
Closes: 812034
Changes:
 klick (0.12.2-3) unstable; urgency=medium
 .
   * Bump Standards.
   * Fix VCS fields.
   * Fix some hardening.
   * Add patch to fix FTBFS with gcc-6 (Closes: #812034).
Checksums-Sha1:
 09b75b7efbb53c0c621df12aabcd32e775407067 2052 klick_0.12.2-3.dsc
 2bc197f3eacf9f751b97416783e3509dfaafdaec 4436 klick_0.12.2-3.debian.tar.xz
 a6651ab9123cfa23b185bf5142be00cf82ff527a 761252 klick-dbgsym_0.12.2-3_amd64.deb
 04e89fc46f7c6b9cbb5c2d8751669c353b6f396b 156366 klick_0.12.2-3_amd64.deb
Checksums-Sha256:
 8c516f1a578b6f2df2fad3af8fa42ebe7682b4ec89dcdea64936e0e09153 2052 
klick_0.12.2-3.dsc
 6225d3b843c2fa21a49ab1f7022d51c9f97a9606c53b654dd3af59d4cd6df527 4436 
klick_0.12.2-3.debian.tar.xz
 86f8d492c20e15eb595ee9e74c87606b33ce3de75a612aea14ebbcfcdf62d534 761252 
klick-dbgsym_0.12.2-3_amd64.deb
 886755bef0601d52b4e0bfb6f77495f5dd0eb63d7c20a2c1bbf1029d8075bc9e 156366 
klick_0.12.2-3_amd64.deb
Files:
 dc5c2f0401cac792284d9dacf4898e3b 2052 sound optional 

Bug#812034: marked as pending

[Jaromír Mikeš]

tag 812034 pending
thanks

Hello,

Bug #812034 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-multimedia/klick.git;a=commitdiff;h=d67924e

---
commit d67924e91cbbdd03331b36241906e334452f1059
Author: Jaromír Mikeš 
Date:   Tue Jul 12 08:53:34 2016 +0200

Finalize changelog.

diff --git a/debian/changelog b/debian/changelog
index 6febd35..442a858 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,9 @@
-klick (0.12.2-3) UNRELEASED; urgency=medium
+klick (0.12.2-3) unstable; urgency=medium
 
-  * Start new upload.
+  * Bump Standards.
+  * Fix VCS fields.
+  * Fix some hardening.
+  * Add patch to fix FTBFS with gcc-6 (Closes: #812034).
 
  -- Jaromír Mikeš   Mon, 11 Jul 2016 23:35:56 +0200
 

Processed: Bug#812034 marked as pending

[Debian Bug Tracking System]

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

> tag 812034 pending
Bug #812034 [klick] klick: FTBFS with GCC 6: needed for in-class initialization
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#816870: marked as done (hplip: contains non-free code)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 06:34:20 +
with message-id 
and subject line Bug#816870: fixed in hplip 3.16.5+repack1-1
has caused the Debian Bug report #816870,
regarding hplip: contains non-free code
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.)


-- 
816870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hplip
Severity: serious
Tags: upstream
Control: forwarded -1 https://bugs.launchpad.net/hplip/+bug/1553628

In prnt/hpcups, the headers of ErnieFilter.cpp and .h say:

// This software is licensed solely for use with HP products. Redistribution
// and use with HP products in source and binary forms, with or without
// modification, are permitted provided that the following conditions are met:

As such, the code is non-free because I cannot safely redistribute it. Could 
that be changed to a normal 3-clause BSD license like the other files?

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

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

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.
--- End Message ---
--- Begin Message ---
Source: hplip
Source-Version: 3.16.5+repack1-1

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

Debian distribution maintenance software
pp.
Didier Raboud  (supplier of updated hplip package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Jul 2016 12:34:10 +0200
Source: hplip
Binary: hplip hplip-data printer-driver-postscript-hp hplip-gui hplip-doc 
hpijs-ppds printer-driver-hpijs printer-driver-hpcups libhpmud0 libhpmud-dev 
libsane-hpaio
Architecture: source
Version: 3.16.5+repack1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team 
Changed-By: Didier Raboud 
Description:
 hpijs-ppds - HP Linux Printing and Imaging - HPIJS PPD files
 hplip  - HP Linux Printing and Imaging System (HPLIP)
 hplip-data - HP Linux Printing and Imaging - data files
 hplip-doc  - HP Linux Printing and Imaging - documentation
 hplip-gui  - HP Linux Printing and Imaging - GUI utilities (Qt-based)
 libhpmud-dev - HP Multi-Point Transport Driver (hpmud) development libraries
 libhpmud0  - HP Multi-Point Transport Driver (hpmud) run-time libraries
 libsane-hpaio - HP SANE backend for multi-function peripherals
 printer-driver-hpcups - HP Linux Printing and Imaging - CUPS Raster driver 
(hpcups)
 printer-driver-hpijs - HP Linux Printing and Imaging - printer driver (hpijs)
 printer-driver-postscript-hp - HP Printers PostScript Descriptions
Closes: 816870
Changes:
 hplip (3.16.5+repack1-1) unstable; urgency=medium
 .
   * Repack the 3.16.5 upstream release to remove
 prnt/hpcups/ErnieFilter.{cpp,h} source files as they are non-free
 (Closes: #816870) (LP: #1553628)
   * Add patch to disable ErnieFilter usage everywhere, to cope with the repack
Checksums-Sha1:
 a84908ad1c9fdb0703773d9d9f18b72fdb3407ea 2964 hplip_3.16.5+repack1-1.dsc
 24200b0e0d32d006c422fc5e1777929768625c71 8853336 
hplip_3.16.5+repack1.orig.tar.xz
 6ed26aa6744961bdb41efbe3d23fbed15502822f 97400 
hplip_3.16.5+repack1-1.debian.tar.xz
Checksums-Sha256:
 6018bad8b6733ad326f43739f3393f2fd4d7fb1ff0942e0606f8098f96b6c236 2964 
hplip_3.16.5+repack1-1.dsc
 ae98da1a7a759c2ca4ead1322d7a81794a4c43b785d82ba9de6fafd86aaf7932 8853336 
hplip_3.16.5+repack1.orig.tar.xz
 ada3fc79e0b67adf5a9815adf9c70939d611404b8c77a31913af443639064191 97400 
hplip_3.16.5+repack1-1.debian.tar.xz

Bug#811982: marked as done (atlas-cpp: FTBFS with GCC 6: symbol changes)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 06:03:24 +
with message-id 
and subject line Bug#811982: fixed in atlas-cpp 0.6.3-3
has caused the Debian Bug report #811982,
regarding atlas-cpp: FTBFS with GCC 6: symbol changes
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.)


-- 
811982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: atlas-cpp
Version: 0.6.3-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-symbols

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libatlas-cpp-0.6-2/DEBIAN/symbols doesn't 
> match completely debian/libatlas-cpp-0.6-2.symbols
> --- debian/libatlas-cpp-0.6-2.symbols (libatlas-cpp-0.6-2_0.6.3-2_amd64)
> +++ dpkg-gensymbols_aoySq 2016-01-19 20:29:18.160102882 +
> @@ -140,17 +140,17 @@
>   _ZNSt11_Deque_baseIN5Atlas6Codecs6Packed5StateESaIS3_EED1Ev@Base 0.6.2
>   _ZNSt11_Deque_baseIN5Atlas6Codecs6Packed5StateESaIS3_EED2Ev@Base 0.6.2
>   
> (regex)_ZNSt11_Deque_baseINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_initialize_mapE[mj]@Base
>  0.6.2
> - 
> (optional=templinst)_ZNSt5dequeIN5Atlas6Codecs3XML5StateESaIS3_EE12emplace_backIIS3_EEEvDpOT_@Base
>  0.6.3
> +#MISSING: 0.6.3-2# 
> (optional=templinst)_ZNSt5dequeIN5Atlas6Codecs3XML5StateESaIS3_EE12emplace_backIIS3_EEEvDpOT_@Base
>  0.6.3
>   
> (optional=templinst)_ZNSt5dequeIN5Atlas6Codecs3XML5StateESaIS3_EE12emplace_backIJS3_EEEvDpOT_@Base
>  0.6.3
> - 
> (optional=templinst)_ZNSt5dequeIN5Atlas6Codecs3XML5StateESaIS3_EE16_M_push_back_auxIIS3_EEEvDpOT_@Base
>  0.6.3
> - 
> (optional=templinst)_ZNSt5dequeIN5Atlas6Codecs3XML5StateESaIS3_EE16_M_push_back_auxIJS3_EEEvDpOT_@Base
>  0.6.3
> - 
> (optional=templinst)_ZNSt5dequeIN5Atlas6Codecs4Bach5StateESaIS3_EE12emplace_backIIS3_EEEvDpOT_@Base
>  0.6.3
> +#MISSING: 0.6.3-2# 
> (optional=templinst)_ZNSt5dequeIN5Atlas6Codecs3XML5StateESaIS3_EE16_M_push_back_auxIIS3_EEEvDpOT_@Base
>  0.6.3
> +#MISSING: 0.6.3-2# 
> (optional=templinst)_ZNSt5dequeIN5Atlas6Codecs3XML5StateESaIS3_EE16_M_push_back_auxIJS3_EEEvDpOT_@Base
>  0.6.3
> +#MISSING: 0.6.3-2# 
> (optional=templinst)_ZNSt5dequeIN5Atlas6Codecs4Bach5StateESaIS3_EE12emplace_backIIS3_EEEvDpOT_@Base
>  0.6.3
>   
> (optional=templinst)_ZNSt5dequeIN5Atlas6Codecs4Bach5StateESaIS3_EE12emplace_backIJS3_EEEvDpOT_@Base
>  0.6.3
> - 
> (optional=templinst)_ZNSt5dequeIN5Atlas6Codecs6Packed5StateESaIS3_EE12emplace_backIIS3_EEEvDpOT_@Base
>  0.6.3
> +#MISSING: 0.6.3-2# 
> (optional=templinst)_ZNSt5dequeIN5Atlas6Codecs6Packed5StateESaIS3_EE12emplace_backIIS3_EEEvDpOT_@Base
>  0.6.3
>   
> (optional=templinst)_ZNSt5dequeIN5Atlas6Codecs6Packed5StateESaIS3_EE12emplace_backIJS3_EEEvDpOT_@Base
>  0.6.3
> - 
> (optional=templinst)_ZNSt5dequeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE12emplace_backIIS5_EEEvDpOT_@Base
>  0.6.3
> +#MISSING: 0.6.3-2# 
> (optional=templinst)_ZNSt5dequeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE12emplace_backIIS5_EEEvDpOT_@Base
>  0.6.3
>   
> (optional=templinst)_ZNSt5dequeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base
>  0.6.3
> - 
> (optional=templinst)_ZNSt5dequeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE16_M_push_back_auxIIS5_EEEvDpOT_@Base
>  0.6.3
> +#MISSING: 0.6.3-2# 
> (optional=templinst)_ZNSt5dequeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE16_M_push_back_auxIIS5_EEEvDpOT_@Base
>  0.6.3
>   
> (optional=templinst)_ZNSt5dequeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE16_M_push_back_auxIJS5_EEEvDpOT_@Base
>  0.6.3
>   
> _ZNSt5dequeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED1Ev@Base
>  0.6.2
>   
> _ZNSt5dequeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev@Base
>  0.6.2
> @@ -170,9 +170,9 @@
>   _ZN5Atlas5Funky6Tokens8end_listE@Base 0.6.2
>   _ZN5Atlas5Funky6Tokens9begin_mapE@Base 0.6.2
>