Bug#832133: Checklist for uploading new versions

[Pirate Praveen]

On 07/23/2016 01:43 AM, Antonio Terceiro wrote:
> On Sat, Jul 23, 2016 at 12:12:16AM +0530, Pirate Praveen wrote:
>> On 07/22/2016 11:50 PM, Pirate Praveen wrote:
>>> I think the solution is to build rails on a system which still has
>>> ruby-json 1.8.3 and upload that version to archive.
>>>
>>
>> I have built rails locally without strict dependency on ruby-json. If
>> someone can confirm its okay to upload, I can upload it.
> 
> you also need to patch the dependency specification on
> activesupport/activesupport.gemspec otherwise rails will blow up on
> startup anyway.
> 
> activesupport/activesupport.gemspec does have:
> 
>   s.add_dependency 'json',   '~> 1.7', '>= 1.7.7'
> 
> which indeed implies << 2.0, but if the changes are minor as Lucas said,
> you can just drop the '~> 1.7' from there.
> 

Thanks! I have patched gemspec as well and uploaded rails 4.2.6-2. Once
we confirm the remaining reverse dependencies also works, we can close
this bug.



signature.asc
Description: OpenPGP digital signature

Bug#830987: libjs-handlebars: missing source

[Pirate Praveen]

On Wed, 13 Jul 2016 15:44:34 +0100 Ansgar Burchardt  wrote:
> I briefly looked into the package due to the discussion on -devel@ and
> the ctte bug.  The source for the javascript code seems to be missing:
> it contains generated lexer/parser code, see the upstream source at
> 
>   https://github.com/wycats/handlebars.js/blob/v1.3.0/src/handlebars.l
> 
> (Just search for "yytext" in handlebars-v1.3.0.js
> or vendor/assets/javascripts/handlebars.js for ruby-handlebar-assets.)
> 
> That seems to be a bit more than just concatenating files.
> 
> Ansgar
> 
> 

Ansgar,

Can I upload it to contrib till ctte decides? I could then reduce the severity 
and let it migrate to testing. A proper fix can take a long time and I'd like 
to see diaspora (which depends on ruby-handlebars-assets) in stretch, at least 
in contrib.

Praveen
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#817373: marked as done (bb: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sat, 23 Jul 2016 00:33:30 +
with message-id 
and subject line Bug#817373: fixed in bb 1.3rc1-8.5
has caused the Debian Bug report #817373,
regarding bb: 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.)


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

Hi,

The package bb 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: bb
Source-Version: 1.3rc1-8.5

We believe that the bug you reported is fixed in the latest version of
bb, 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.
Axel Beckert  (supplier of updated bb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 21 Jul 2016 19:21:48 +0200
Source: bb
Binary: bb
Architecture: source amd64
Version: 1.3rc1-8.5
Distribution: unstable
Urgency: medium
Maintainer: Uwe Hermann 
Changed-By: Axel Beckert 
Description:
 bb - ASCII-art demo based on AAlib
Closes: 817373
Changes:
 bb (1.3rc1-8.5) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Axel Beckert ]
   * Move from no more supported debhelper compatibility level 4 to
 currently recommended level 9 and make debian/rules and debian/control
 more future-proof:
 + Change "dh_clean -k" to "dh_prep".
 + Remove explicit argument from dh_installchangelogs. (No more needed.)
 + Add recommended targets build-indep and build-arch.
 + Add ${misc:Depends} to Depends
 + Closes: #817373
   * Remove config.guess and config.sub from Debian's .diff.gz and use
 dh_autotools-dev_{restore,update}config to provide up-to-date files at
 build time.
 + Add build-dependency on autotools-dev.
 .
   [ Logan Rosen ]
   * debian/rules: Don't ignore all distclean errors.
   * debian/copyright: Don't point to symlink GPL.
Checksums-Sha1:
 16cc4b2f762a44f17100c81ba759137024b6f42a 1690 bb_1.3rc1-8.5.dsc
 e0d48757a659af7e56970bea3cc4e2179fb60359 10193 bb_1.3rc1-8.5.diff.gz
 9378fc02bbcfe0577eb29e8a299e237379f9f998 96950 bb-dbgsym_1.3rc1-8.5_amd64.deb
 497b3542394742ef2d3480f0912f18fe55807b7d 990054 bb_1.3rc1-8.5_amd64.deb
Checksums-Sha256:
 08dcae09a7fa4d6427713c3737f1e62c2baedd7d3b8289665ecaefa6cb3cb8ea 1690 
bb_1.3rc1-8.5.dsc
 dd8b2a0e48bdb0b64b5544fca53c42e1558fb4d282c5deafaa4e08eaf0188c35 10193 
bb_1.3rc1-8.5.diff.gz
 073d9c5b45b9180dedd269ce42134c49b3103d6706ebca2c31313f99470bd505 96950 
bb-dbgsym_1.3rc1-8.5_amd64.deb
 6f6b3a935d420f00addb7982b86f9517485144421a02a3398a7d475666d617f0 990054 
bb_1.3rc1-8.5_amd64.deb
Files:
 e4c5d4bc98999348f99557fe8010c4ec 1690 games optional bb_1.3rc1-8.5.dsc
 21c6c1f50e0e8035a0d032dbe81a600d 10193 games optional bb_1.3rc1-8.5.diff.gz
 5537415c4b2e07f261d33839adcabc63 96950 debug extra 
bb-dbgsym_1.3rc1-8.5_amd64.deb
 89500e856b6433e505d7e0d7be95b7fb 990054 games optional bb_1.3rc1-8.5_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXkQUCAAoJEGvmY8daNcl1JVEP+gO2YxBeDYn0K2ytBOSnaX93
HT25JdlEQYkOK1yvblQrg7/iB0F4FlKjQ76tyLD9XNWI7NUZRtq/qXIbhUyMnR+A
U+ABPB8vuEKsnt2bGejCcTNXpi4LV+PI6GXDcCmcYXQ0PZV7jz3mSJxU0nYB/6bJ
s4+6hFNw3Pf9TeAR0sq29Hmk3Qfg6cxW1ZCDdd+PxWavDopt5cx4JJcDMWd2kDQk
i/ubEiUswdgp0oNqsjylJHerA5T8uGg3F7DDBa3eNoLh7TSHq6fxxTS2yjN/T9Vg
SOPKqnaJAcK8oxkCuN0HYuWl3U/BlAQDAyGWGTzpOPhf96ltZQ9fkQ4z7FBnhkC0

Bug#832155: New ssh-session-cleanup.service kills ssh user session during upgrade

[Michael Biebl]

Hi Colin

Am 23.07.2016 um 01:42 schrieb Michael Biebl:
> See also the relevant upstream commit:
> 
> https://github.com/systemd/systemd/commit/8c856804780681e135d98ca94d08afe247557770
> 
> This fix is part of v230. Before that, we had no proper ordering on
> shutdown, so it was indeed possible that some user sessions were not
> properly terminated before the network was stopped (as some users
> reported) due to race conditions.

Btw, if you have any systemd related questions, feel free to poke use
via the pkg-systemd-maintainers@ mailing list (in CC).
We are always happy to provide feedback/help.

Regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#832155: New ssh-session-cleanup.service kills ssh user session during upgrade

[Michael Biebl]

See also the relevant upstream commit:

https://github.com/systemd/systemd/commit/8c856804780681e135d98ca94d08afe247557770

This fix is part of v230. Before that, we had no proper ordering on
shutdown, so it was indeed possible that some user sessions were not
properly terminated before the network was stopped (as some users
reported) due to race conditions.


Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#832155: New ssh-session-cleanup.service kills ssh user session during upgrade

[Michael Biebl]

Package: openssh-server
Version: 1:7.2p2-6
Severity: serious

Hi,

the addition of ssh-session-cleanup.service in the latest upload [1] is
imho a bad idea. It's an aweful hack and besides, it also kills your SSH
sessions on upgrades (thus severity RC).

The proper fix is to use libpam-systemd. This will register a proper
session scope when users log in via SSH. Those session scopes are
ordered against systemd-user-sessions.service which itself has a proper
ordering against network.target. So those user session are stopped
before the network stack is shutdown.

Please drop ssh-session-cleanup.service again and simply add a
dependency on libpam-systemd. It's the correct solution for this
problem.

Regards,
Michael

[1] https://anonscm.debian.org/cgit/pkg-ssh/openssh.git/commit/?id=b66f1de1c94

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

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 openssh-server depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.59
ii  dpkg   1.18.9
ii  init-system-helpers1.39
ii  libaudit1  1:2.6.5-1
ii  libc6  2.23-2
ii  libcomerr2 1.43.1-1
ii  libgssapi-krb5-2   1.14.2+dfsg-1
ii  libkrb5-3  1.14.2+dfsg-1
ii  libpam-modules 1.1.8-3.3
ii  libpam-runtime 1.1.8-3.3
ii  libpam0g   1.1.8-3.3
ii  libselinux12.5-3
ii  libssl1.0.21.0.2h-1
ii  libsystemd0230-7
ii  libwrap0   7.6.q-25
ii  lsb-base   9.20160629
ii  openssh-client 1:7.2p2-6
ii  openssh-sftp-server1:7.2p2-6
ii  procps 2:3.3.12-2
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages openssh-server recommends:
ii  ncurses-term  6.0+20160625-1
ii  xauth 1:1.0.9-1

Versions of packages openssh-server suggests:
ii  ksshaskpass [ssh-askpass]  4:5.7.0-1
pn  molly-guard
pn  monkeysphere   
pn  rssh   
ii  ssh-askpass1:1.2.4.1-9
pn  ufw

-- debconf information excluded

Bug#811943: marked as done (xorp: FTBFS with GCC 6: template instantiation depth exceeds maximum)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 22:52:53 +
with message-id 
and subject line Bug#811943: fixed in xorp 1.8.6~wip.20160715-1
has caused the Debian Bug report #811943,
regarding xorp: FTBFS with GCC 6: template instantiation depth exceeds maximum
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.)


-- 
811943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xorp
Version: 1.8.5-4.1
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
...
> scons: Building targets ...
> scons: Configure: creating obj/x86_64-unknown-linux-gnu/xorp_config.h
> g++ -o obj/x86_64-unknown-linux-gnu/cli/tools/cli_generic.o -c 
> -Wno-error=cast-qual -Wno-error=sizeof-pointer-memaccess 
> -Wno-error=sizeof-array-argument -O2 -g3 -Werror -W -Wall -Wwrite-strings 
> -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual 
> -ftemplate-depth=30 -pipe -DXORP_BUILDINFO -DXRL_PF=120 -DXORP_VERSION=1.8.5 
> -Iobj/x86_64-unknown-linux-gnu -I. -I. cli/tools/cli_generic.cc
> In file included from /usr/include/c++/6/bits/move.h:57:0,
>  from /usr/include/c++/6/bits/nested_exception.h:40,
>  from /usr/include/c++/6/exception:171,
>  from /usr/include/c++/6/new:40,
>  from ./libxorp/xorp.h:84,
>  from cli/tools/cli_generic.cc:23:
> /usr/include/c++/6/type_traits: In instantiation of 'struct 
> std::is_reference':
> /usr/include/c++/6/type_traits:120:12:   required from 'struct 
> std::__or_, std::is_void >'
> /usr/include/c++/6/type_traits:125:12:   required from 'struct 
> std::__or_, std::is_reference, 
> std::is_void >'
> /usr/include/c++/6/type_traits:154:38:   required from 'struct 
> std::__not_, 
> std::is_reference, std::is_void > >'
> /usr/include/c++/6/type_traits:590:12:   required from 'struct 
> std::is_object'
> /usr/include/c++/6/type_traits:120:12:   required from 'struct 
> std::__or_, std::is_reference >'
> /usr/include/c++/6/type_traits:627:12:   [ skipping 19 instantiation 
> contexts, use -ftemplate-backtrace-limit=0 to disable ]
> /usr/include/c++/6/bits/move.h:106:12:   required from 'struct 
> std::__move_if_noexcept_cond'
> /usr/include/c++/6/bits/stl_iterator.h:1212:26:   required by substitution of 
> 'template _ReturnType 
> std::__make_move_if_noexcept_iterator(_Tp*) [with _Tp = XrlAtom; _ReturnType 
> = ]'
> /usr/include/c++/6/bits/stl_uninitialized.h:303:3:   required from 
> '_ForwardIterator std::__uninitialized_move_if_noexcept_a(_InputIterator, 
> _InputIterator, _ForwardIterator, _Allocator&) [with _InputIterator = 
> XrlAtom*; _ForwardIterator = XrlAtom*; _Allocator = std::allocator]'
> /usr/include/c++/6/bits/vector.tcc:422:8:   required from 'void 
> std::vector<_Tp, _Alloc>::_M_emplace_back_aux(_Args&& ...) [with _Args = 
> {const XrlAtom&}; _Tp = XrlAtom; _Alloc = std::allocator]'
> /usr/include/c++/6/bits/stl_vector.h:924:4:   required from 'void 
> std::vector<_Tp, _Alloc>::push_back(const value_type&) [with _Tp = XrlAtom; 
> _Alloc = std::allocator; std::vector<_Tp, _Alloc>::value_type = 
> XrlAtom]'
> ./libxipc/xrl_args.hh:557:23:   required from here
> /usr/include/c++/6/type_traits:570:12: fatal error: template instantiation 
> depth exceeds maximum of 30 (use -ftemplate-depth= to increase the maximum)
>  struct is_reference
> ^~~~
> 
> compilation terminated.

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: xorp
Source-Version: 1.8.6~wip.20160715-1

We believe that the bug you reported is fixed in the latest version of
xorp, 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 

Bug#832116: edgar: Source missing for some GPL licensed assets

[Zorian M]

I've sent an email to the author of "Devilish design" to request an
additional CC-BY license, and sent a PR on the edgar repository to
re-credit the author of Medicine:
https://github.com/riksweeney/edgar/pull/18

On 7/22/16, Guus Sliepen  wrote:
> Source: edgar
> Severity: serious
> Justification: source missing for GPL licensed assets
>
> According to debian/copyright, the edgar-data package contains a number
> of songs which are licensed under the GPL-3+. However, only the final
> rendered music is present in the form of a .ogg file.
>
>> Files:
>>   music/Battle?in?the?winter.ogg
>>   music/Devilish?design.ogg
>>   music/A?wintertale_0.ogg
>>   music/Medicine.ogg
>> Copyright: Copyright (c) Johan Brodd
>> Comment: http://opengameart.org/users/jobromedia
>> License: GPL-3+
>
> Upon checking OpenGameArt, I found out that "Battle in the winter" and "A
> winter tale" are dual-licensed, and available under the CC-BY 3.0 and
> CC-BY-SA 3.0 licenses respectively, so it should be a simple matter of
> updating the copyright notice here. However, "Devilish design" is only
> available under GPL 3.0. As such, I believe that unless the source can
> be found or Johan Brodd can be contacted and asked if the license could
> be changed, this song should be removed from the source package.
>
> Also, Medicine.ogg is, according to OpenGameArt.org, created by
> Alexander Zhelanov, and is licensed only under CC-BY 3.0.
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.6.0-1-amd64 (SMP w/12 CPU cores)
> Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> -- no debconf information
>

Bug#824734: marked as done (omnievents: FTBFS: cp: cannot stat './TODOdoc/omnievents.docbook.css': No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 22:52:31 +
with message-id 
and subject line Bug#824734: fixed in omnievents 1:2.6.2-3
has caused the Debian Bug report #824734,
regarding omnievents: FTBFS: cp: cannot stat 
'./TODOdoc/omnievents.docbook.css': No such file or directory
to be marked as done.

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

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


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

Dear Maintainer,

omnievents fails to build from source in unstable/amd64:

  [..]

  Transferring function references...
  Combining using relations...
  Adding members to index pages...
  Generating style sheet...
  Generating search indices...
  Generating example documentation...
  Generating file sources...
  Generating code for file Callback.h...
  Generating code for file channel.cc...
  Generating code for file config.h...
  Generating code for file ConsumerAdmin.cc...
  Generating code for file ConsumerAdmin.h...
  Generating code for file daemon.h...
  Generating code for file daemon_unix.cc...
  Generating code for file daemon_unix.h...
  Generating code for file daemon_windows.cc...
  Generating code for file daemon_windows.h...
  Generating code for file defaults.h...
  Generating code for file eventc.cc...
  Generating code for file EventChannel.cc...
  Generating code for file EventChannel.h...
  Generating code for file EventChannelFactory.cc...
  Generating code for file EventChannelFactory.h...
  Generating code for file eventf.cc...
  Generating code for file EventQueue.cc...
  Generating code for file EventQueue.h...
  Generating code for file events.cc...
  Generating code for file Filter.cc...
  Generating code for file 
F/home/lamby/temp/cdt.20160519114003.DPE6TFccSI.omnievents/omnievents-2.6.2/src/defaults.h:82:
 warning: Found unknown command `\TEMP'
  
/home/lamby/temp/cdt.20160519114003.DPE6TFccSI.omnievents/omnievents-2.6.2/src/naming.h:84:
 warning: Unsupported xml/html tag  found
  
/home/lamby/temp/cdt.20160519114003.DPE6TFccSI.omnievents/omnievents-2.6.2/src/naming.h:84:
 warning: Unsupported xml/html tag  found
  
/home/lamby/temp/cdt.20160519114003.DPE6TFccSI.omnievents/omnievents-2.6.2/src/naming.h:84:
 warning: Unsupported xml/html tag  found
  
/home/lamby/temp/cdt.20160519114003.DPE6TFccSI.omnievents/omnievents-2.6.2/src/naming.h:84:
 warning: Unsupported xml/html tag  found
  
/home/lamby/temp/cdt.20160519114003.DPE6TFccSI.omnievents/omnievents-2.6.2/src/naming.h:84:
 warning: Unsupported xml/html tag  found
  
/home/lamby/temp/cdt.20160519114003.DPE6TFccSI.omnievents/omnievents-2.6.2/src/naming.h:84:
 warning: Unsupported xml/html tag  found
  
/home/lamby/temp/cdt.20160519114003.DPE6TFccSI.omnievents/omnievents-2.6.2/src/naming.h:84:
 warning: Unsupported xml/html tag  found
  
/home/lamby/temp/cdt.20160519114003.DPE6TFccSI.omnievents/omnievents-2.6.2/src/naming.h:84:
 warning: Unsupported xml/html tag  found
  ilter.h...
  Generating code for file gethostname.h...
  Generating code for file getopt.cc...
  Generating code for file getopt.h...
  Generating code for file main.cc...
  Generating code for file main.h...
  Generating code for file Mapper.h...
  Generating code for file naming.cc...
  Generating code for file naming.h...
  Generating code for file omniEvents.cc...
  Generating code for file omniEvents.h...
  Generating code for file omniEventsLog.cc...
  Generating code for file omniEventsLog.h...
  Generating code for file Orb.cc...
  Generating code for file Orb.h...
  Generating code for file PersistNode.cc...
  Generating code for file PersistNode.h...
  Generating code for file ProxyManager.cc...
  Generating code for file ProxyManager.h...
  Generating code for file ProxyPullConsumer.cc...
  Generating code for file ProxyPullConsumer.h...
  Generating code for file ProxyPullSupplier.cc...
  Generating code for file ProxyPullSupplier.h...
  Generating code for file ProxyPushConsumer.cc...
  Generating code for file ProxyPushConsumer.h...
  Generating code for file ProxyPushSupplier.cc...
  Generating code for file ProxyPushSupplier.h...
  Generating code for file pullcons.cc...
  Generating code for file pullsupp.cc...
  Generating code for file pushcons.cc...
  Generating code for file pushsupp.cc...
  Generating code for file rmeventc.cc...
  

Bug#817231: rabbitvcs: All files in home folder removed

[W. Martin Borgert]

This seems to be this bug:
https://github.com/rabbitvcs/rabbitvcs/issues/127
(dupe: https://github.com/rabbitvcs/rabbitvcs/issues/161)

Bug#831092: marked as done (qsynth: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 22:26:17 +
with message-id 
and subject line Bug#831092: fixed in qsynth 0.4.1-2
has caused the Debian Bug report #831092,
regarding qsynth: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No 
such file or directory
to be marked as done.

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

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


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

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -c -m64 -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -O2 -std=gnu++0x 
> -Wall -W -D_REENTRANT -fPIC -DDATADIR="/usr/share" -DQT_NO_DEBUG 
> -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -I. 
> -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/local/include 
> -isystem /usr/include -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets 
> -isystem /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I.ui 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o .obj/qsynth.o 
> qsynth.cpp
> In file included from /usr/include/c++/6/bits/stl_algo.h:59:0,
>  from /usr/include/c++/6/algorithm:62,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:88,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:37,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:37,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstringlist.h:34,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QStringList:1,
>  from qsynthSetup.h:25,
>  from qsynthOptions.h:25,
>  from qsynth.cpp:23:
> /usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or 
> directory
>  #include_next 
>  ^
> compilation terminated.
> make[3]: *** [.obj/qsynth.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/qsynth_0.4.1-1_unstable_gcc6.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: qsynth
Source-Version: 0.4.1-2

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

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

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

Debian distribution maintenance software
pp.
Jaromír Mikeš  (supplier of updated qsynth 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: Wed, 20 Jul 2016 23:30:13 +0200
Source: qsynth
Binary: qsynth
Architecture: source amd64
Version: 0.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jaromír Mikeš 
Description:
 qsynth - fluidsynth MIDI sound synthesiser front-end
Closes: 831092
Changes:
 qsynth (0.4.1-2) unstable; urgency=medium
 .
   * Add patch to build with gcc6. (Closes: #831092).
   * Build with dh-autoreconf.
   * Tune .gitignore file.
   * Add description to patch.
   * Update copyright file.
Checksums-Sha1:
 97a0c1a6b251aeb857594c84279dd556a0b1e98c 

Bug#831170: marked as done (qjackctl: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 22:25:54 +
with message-id 
and subject line Bug#831170: fixed in qjackctl 0.4.2-2
has caused the Debian Bug report #831170,
regarding qjackctl: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No 
such file or directory
to be marked as done.

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

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


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

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -c -m64 -pipe -Wall -g -O2 -std=gnu++0x -Wall -W -D_REENTRANT -fPIC 
> -DDATADIR="/usr/share" -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB 
> -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. -I. -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/local/include -isystem 
> /usr/include -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I.ui 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o .obj/qjackctl.o 
> qjackctl.cpp
> In file included from /usr/include/c++/6/bits/stl_algo.h:59:0,
>  from /usr/include/c++/6/algorithm:62,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:88,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qnamespace.h:37,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:41,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:40,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qsettings.h:37,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QSettings:1,
>  from qjackctlConnectAlias.h:25,
>  from qjackctlSetup.h:25,
>  from qjackctl.cpp:23:
> /usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or 
> directory
>  #include_next 
>  ^
> compilation terminated.
> make[3]: *** [.obj/qjackctl.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/qjackctl_0.4.2-1_unstable_gcc6.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: qjackctl
Source-Version: 0.4.2-2

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

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

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

Debian distribution maintenance software
pp.
Jaromír Mikeš  (supplier of updated qjackctl 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: Wed, 20 Jul 2016 13:46:23 +0200
Source: qjackctl
Binary: qjackctl
Architecture: source amd64
Version: 0.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jaromír Mikeš 
Description:
 qjackctl   - User interface for controlling the JACK sound server
Closes: 831170
Changes:
 qjackctl (0.4.2-2) unstable; urgency=medium
 .
   * Tune .gitignore file.
   * Add patch to build with gcc6. 

Bug#830550: marked as done (elasticsearch-curator: accesses the internet during build)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 22:19:25 +
with message-id 
and subject line Bug#830550: fixed in elasticsearch-curator 4.0.1-2
has caused the Debian Bug report #830550,
regarding elasticsearch-curator: 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.)


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

Dear Maintainer,

Whilst elasticsearch-curator 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 7469885a829d.56130 > dnscache.uct.ac.za.domain: 40204+ A? 
docs.python.org. (33)
  00:00:00.57 IP 7469885a829d.56130 > dnscache.uct.ac.za.domain: 3119+ 
? docs.python.org. (33)
  00:00:00.302535 IP dnscache.uct.ac.za.domain > 7469885a829d.56130: 40204 
3/4/4 CNAME python.map.fastly.net., CNAME prod.python.map.fastlylb.net., A 
151.101.16.223 (259)
  00:00:00.302925 IP dnscache.uct.ac.za.domain > 7469885a829d.56130: 3119 2/1/0 
CNAME python.map.fastly.net., CNAME prod.python.map.fastlylb.net. (178)
  00:00:00.303331 IP 7469885a829d.47148 > 151.101.16.223.https: Flags [S], seq 
1581698832, win 29200, options [mss 1460,sackOK,TS val 105205706 ecr 
0,nop,wscale 7], length 0
  00:00:00.452128 IP 151.101.16.223.https > 7469885a829d.47148: Flags [S.], seq 
1850767652, ack 1581698833, win 28560, options [mss 1440,sackOK,TS val 
1173103029 ecr 105205706,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
   `-


elasticsearch-curator.4.0.1-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: elasticsearch-curator
Source-Version: 4.0.1-2

We believe that the bug you reported is fixed in the latest version of
elasticsearch-curator, 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.
Apollon Oikonomopoulos  (supplier of updated 
elasticsearch-curator package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 22 Jul 2016 23:51:01 +0300
Source: elasticsearch-curator
Binary: elasticsearch-curator python-elasticsearch-curator 
python3-elasticsearch-curator python-elasticsearch-curator-doc
Architecture: source
Version: 4.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Apollon Oikonomopoulos 
Description:
 elasticsearch-curator - command-line tool for managing Elasticsearch 
time-series indices
 python-elasticsearch-curator - Python library for managing Elasticsearch 
time-series indices
 python-elasticsearch-curator-doc - Python library for managing Elasticsearch 
time-series indices (do
 python3-elasticsearch-curator - Python 3 library for managing Elasticsearch 
time-series indices
Closes: 830550
Changes:
 elasticsearch-curator (4.0.1-2) unstable; urgency=medium
 .
   * Restrict intersphinx from downloading object inventory data (Closes:
 #830550):
 + sphinx: use local inventory references for intersphinx
 + B-D on python3-doc and python-elasticsearch-doc
Checksums-Sha1:
 444d4e0b0d803a48a23a06ba3c0bdb421f707e0a 2805 elasticsearch-curator_4.0.1-2.dsc
 e033e608a831b72493f8225e6f967e1d95a2c342 6100 
elasticsearch-curator_4.0.1-2.debian.tar.xz
Checksums-Sha256:
 449f5e5c8846026d0f31674e74930132da59d5459c70ad473f4491a746af744f 2805 
elasticsearch-curator_4.0.1-2.dsc
 84e69804631af1a51d0d274a6ea6862ae33b42c0dc9de02ca710a44922ba931b 6100 
elasticsearch-curator_4.0.1-2.debian.tar.xz
Files:
 

Processed: fixed 829724 in 0.6.13-1

[Debian Bug Tracking System]

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

> fixed 829724 0.6.13-1
Bug #829724 {Done: Jelmer Vernooij } [src:bzr-git] bzr-git: 
FTBFS: AssertionError: not equal: a = [..] DeprecationWarning  [..]  b = ''
Marked as fixed in versions bzr-git/0.6.13-1.
> thanks
Stopping processing here.

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

Processed: Bug 831527 : Change severity to grave

[Debian Bug Tracking System]

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

> severity 831527 grave
Bug #831527 [flashplugin-nonfree] flashplugin-nonfree: New Flash player 
11.2.202.632 is available -- fixes a security issue
Severity set to 'grave' from 'important'
>
End of message, stopping processing here.

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

Bug#831170: marked as pending

[Jaromír Mikeš]

tag 831170 pending
thanks

Hello,

Bug #831170 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/qjackctl.git;a=commitdiff;h=356e303

---
commit 356e303ffb5fc415fa1fc7f92ad3a6fdc65e92fc
Author: Jaromír Mikeš 
Date:   Fri Jul 22 22:41:01 2016 +0200

Finalize changelog.

diff --git a/debian/changelog b/debian/changelog
index bdce13b..9f8a3d1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,10 @@
-qjackctl (0.4.2-2) UNRELEASED; urgency=medium
+qjackctl (0.4.2-2) unstable; urgency=medium
 
-  * Start new upload.
+  * Tune .gitignore file.
+  * Add patch to build with gcc6. (Closes: #831170)
+  * Build with dh-autoreconf.
+  * Add description to the patch.
+  * Add spelling patch.
 
  -- Jaromír Mikeš   Wed, 20 Jul 2016 13:46:23 +0200
 

Processed: Bug#831170 marked as pending

[Debian Bug Tracking System]

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

> tag 831170 pending
Bug #831170 [src:qjackctl] qjackctl: FTBFS with GCC 6: cstdlib:75:25: fatal 
error: stdlib.h: No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade

[Carl Eugen Hoyos]

Thank you for the backtrace!

Could you check if removing some or all entries from 
vaapi_encode_h264_defaults in libavcodec/vaapi_encode_h264.c 
fixes the issue? I was unable to quickly find the vaapi 
source file containing the option strings and I don't 
have a cpu with vaapi capabilities.

Thank you, Carl Eugen

Processed: patch

[Debian Bug Tracking System]

Processing control commands:

> tags 831195 +patch
Bug #831195 [src:xmacro] xmacro: FTBFS with GCC 6: stl_algobase.h:243:56: 
error: macro "min" passed 3 arguments, but takes just 2
Added tag(s) patch.

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

Bug#831195: patch

[Eduard Bloch]

Control: tags 831195 +patch

While this problem can be easily patched, I have no motivation to work
on this package anymore. RFH will be opened soon.

Regards,
Eduard.
>From b1bf5f03735b5a0310698ac5143a1397dc8c0cca Mon Sep 17 00:00:00 2001
From: Eduard Bloch 
Date: Fri, 22 Jul 2016 22:26:31 +0200
Subject: [PATCH] Working around FTBFS, #831195

---
 debian/changelog  |  7 +++
 debian/source/format  |  1 +
 debian/source/options |  3 +++
 xmacroplay.cpp| 18 +++---
 xmacrorec.cpp | 15 ---
 xmacrorec2.cpp| 12 ++--
 6 files changed, 24 insertions(+), 32 deletions(-)
 create mode 100644 debian/source/format
 create mode 100644 debian/source/options

diff --git a/debian/changelog b/debian/changelog
index a400044..b599bbd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+xmacro (0.3pre-2911-7) UNRELEASED; urgency=low
+
+  * Fixing build failure with GCC-6 via rearanging the header order
+(closes: #831195)
+
+ -- Eduard Bloch   Fri, 22 Jul 2016 22:26:14 +0200
+
 xmacro (0.3pre-2911-6) unstable; urgency=low
 
   * Proper build with original tarball
diff --git a/debian/source/format b/debian/source/format
new file mode 100644
index 000..163aaf8
--- /dev/null
+++ b/debian/source/format
@@ -0,0 +1 @@
+3.0 (quilt)
diff --git a/debian/source/options b/debian/source/options
new file mode 100644
index 000..4332117
--- /dev/null
+++ b/debian/source/options
@@ -0,0 +1,3 @@
+compression=xz
+single-debian-patch
+auto-commit
diff --git a/xmacroplay.cpp b/xmacroplay.cpp
index c48f6c7..8eb206c 100644
--- a/xmacroplay.cpp
+++ b/xmacroplay.cpp
@@ -34,7 +34,13 @@
 /* 
  * Includes
  /
-#include 		
+/* 
+ * What iostream do we have?
+ /
+#include 
+#include 
+
+#include 
 #include 
 #include 
 #include 
@@ -47,16 +53,6 @@
 #include 
 
 #include "chartbl.h"
-/* 
- * What iostream do we have?
- /
-#ifdef HAVE_IOSTREAM
-#include 
-#include 
-#else
-#include 
-#include 
-#endif
 
 using namespace std;
 
diff --git a/xmacrorec.cpp b/xmacrorec.cpp
index 7526eb1..64090bf 100644
--- a/xmacrorec.cpp
+++ b/xmacrorec.cpp
@@ -36,6 +36,10 @@
 /* 
  * Includes
  /
+
+#include 
+#include 
+
 #include 		
 #include 
 #include 
@@ -46,17 +50,6 @@
 #include 
 #include 
 
-/* 
- * What iostream do we have?
- /
-#ifdef HAVE_IOSTREAM
-#include 
-#include 
-#else
-#include 
-#include 
-#endif
-
 using namespace std;
 
 #define PROG "xmacrorec"
diff --git a/xmacrorec2.cpp b/xmacrorec2.cpp
index 09e10bb..7f5c437 100644
--- a/xmacrorec2.cpp
+++ b/xmacrorec2.cpp
@@ -38,6 +38,8 @@
 /* 
  * Includes
  /
+#include 
+#include 
 #include 		
 #include 
 #include 
@@ -48,16 +50,6 @@
 #include 
 #include 
 
-/* 
- * What iostream do we have?
- /
-#ifdef HAVE_IOSTREAM
-#include 
-#include 
-#else
-#include 
-#include 
-#endif
 
 using namespace std;
 
-- 
2.8.1

Bug#806984: Mail to Myself

[john brown]

--
Sent from myMail app for Android

Bug#831092: marked as pending

[Jaromír Mikeš]

tag 831092 pending
thanks

Hello,

Bug #831092 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/qsynth.git;a=commitdiff;h=8796f75

---
commit 8796f752b5ca1da30c857c3d8c66a019aed0e6d6
Author: Jaromír Mikeš 
Date:   Fri Jul 22 21:50:04 2016 +0200

Finalize changelog.

diff --git a/debian/changelog b/debian/changelog
index af76ff2..8aacb0b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,10 @@
-qsynth (0.4.1-2) UNRELEASED; urgency=medium
+qsynth (0.4.1-2) unstable; urgency=medium
 
-  * Start new upload.
+  * Add patch to build with gcc6. (Closes: #831092).
+  * Build with dh-autoreconf.
+  * Tune .gitignore file.
+  * Add description to patch.
+  * Update copyright file.
 
  -- Jaromír Mikeš   Wed, 20 Jul 2016 23:30:13 +0200
 

Processed: Bug#831092 marked as pending

[Debian Bug Tracking System]

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

> tag 831092 pending
Bug #831092 [src:qsynth] qsynth: FTBFS with GCC 6: cstdlib:75:25: fatal error: 
stdlib.h: No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#812022: marked as done (traverso: FTBFS with GCC 6: flexible array member...)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 19:49:13 +
with message-id 
and subject line Bug#812022: fixed in traverso 0.49.4-2
has caused the Debian Bug report #812022,
regarding traverso: FTBFS with GCC 6: flexible array member...
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.)


-- 
812022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: traverso
Version: 0.49.4-1
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
...
> Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -O2 -Wall -fPIC
> -msse -mfpmath=sse   -o CMakeFiles/traversosheetcanvas.dir/PluginChainView.o 
> -c /<>/src/sheetcanvas/PluginChainView.cpp
> In file included from /<>/src/plugins/PluginChain.cpp:26:0:
> /<>/src/common/Tsar.h: At global scope:
> /<>/src/common/Tsar.h:66:12: error: flexible array member 
> 'TsarEvent::_a' not at end of 'struct TsarEvent'
>   void*  _a[];
> ^
--- End Message ---
--- Begin Message ---
Source: traverso
Source-Version: 0.49.4-2

We believe that the bug you reported is fixed in the latest version of
traverso, 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.
James Cowgill  (supplier of updated traverso 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: Fri, 22 Jul 2016 18:36:57 +0100
Source: traverso
Binary: traverso
Architecture: source
Version: 0.49.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: James Cowgill 
Description:
 traverso   - Multitrack audio recorder and editor
Closes: 812022
Changes:
 traverso (0.49.4-2) unstable; urgency=medium
 .
   * Team upload.
 .
   * debian/control:
 - Update VCS fields.
 - Bump standards to 3.9.8.
   * debian/dirs:
 - Drop useless dirs file.
   * debian/menu, debian/traverso.xpm
 - Drop menu file and xpm icon.
   * debian/patches:
 - Fix FTBFS with GCC 6. (Closes: #812022)
   * debian/rules:
 - Move linker flags to standard dpkg-buildflags variable.
 - Enable all hardening flags.
Checksums-Sha1:
 8f1f031cbd8101704f737d8ff739b94598b9863a 2248 traverso_0.49.4-2.dsc
 71d19cd9d6ee7da3975f7d0be7d036ca060aaa15 7204 traverso_0.49.4-2.debian.tar.xz
Checksums-Sha256:
 28a6229362d2afa1982df68395da12ecb7a8743034d5f86b4ca5f86abd5b6d11 2248 
traverso_0.49.4-2.dsc
 c311674dd0e4fe6ef6c49ec049fe27a96fd7e6083c9ad6005cb2007d0f26a7df 7204 
traverso_0.49.4-2.debian.tar.xz
Files:
 1d77f2acbd6c2a9d468612849b3165b3 2248 sound optional traverso_0.49.4-2.dsc
 d6f45fe1b286a363fd2cd5338f05d197 7204 sound optional 
traverso_0.49.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJXknRoAAoJEMfxZ23qLQHvYasQAJCfuPi31y7msN3ZkC+fhXK1
rZM1EHyKU9OFfjRKtkVPwtxurrZjQymsABi9ive3BjQaFqT4U/R8vfde7XSHAvvJ
yFABO9PwxWQZJJXLs/QPW1V8IxcU9fLtWYLHPaAS6HNgzZWtbL3TP9iC4HsWlUTG
ai/5MI4M2bQ8KD42nhuDF4EcPX+RIYZA536ZO2NIJHfCptlQRoc7PoisF1Uj1h38
3fNIxkMijjAoUS8sxf6WzWPc3Bm1RDX7G48MfFdBLrQ6oJhq/ZmH1K9/6tgdBfcg
cBzHnNJkgzUCULwpYDEJqWMQPYEhxdbesOOQMeKzYyI4XMqqBwRbxM+dqLqXgre/
2vh4a+PwvMETOwmgJJZ5sOOiuev3oh3/JJnKOAivNfJ02kEPqMo0LLvoZNJnfAdY
gtIgI6N7ZVqEBSj/W9sUZeM8ATI6A88vSznqZneRU47Jj4djh5ZUunIf18+gRUhg
TM3hZi23tETo1CoKTjoO7KIbW+SkNEwnXKkFCnn63G2E0fLxRS3ggEAPyLExC+fn
cmb3+GA/ZQ3CqHbMt/uN9NZdHyrV5xAFhN6sSlTcsXejYc/6JfozWDnETP3FKjfW
sj18ke4RPhabgvGd2dy1hDoVXzKWeYSVpF9a6TYDUv29vIq+nxb26HnPPV6ZyUwb
t0pBKlViGDhGbPGVCDHk
=3VFE
-END PGP 

Processed: forcibly merging 813820 831567

[Debian Bug Tracking System]

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

> forcemerge 813820 831567
Bug #813820 [src:ssreflect] ssreflect: FTBFS: Error: Unbound type constructor 
glob_constr_and_expr
Bug #831567 [src:ssreflect] ssreflect: Version 1.6 released, compatible with 
coq/{testing,unstable}
Severity set to 'serious' from 'normal'
Marked as found in versions ssreflect/1.5-3.
Merged 813820 831567
> thanks
Stopping processing here.

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

Bug#831111: marked as done (qsampler: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 19:33:54 +
with message-id 
and subject line Bug#83: fixed in qsampler 0.4.0-2
has caused the Debian Bug report #83,
regarding qsampler: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No 
such file or directory
to be marked as done.

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

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


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

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -c -m64 -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -O2 -std=gnu++0x 
> -Wall -W -D_REENTRANT -fPIC -DDATADIR="/usr/share" -DQT_NO_DEBUG 
> -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/local/include -isystem 
> /usr/include -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I.ui 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o .obj/qsampler.o 
> qsampler.cpp
> In file included from /usr/include/c++/6/bits/stl_algo.h:59:0,
>  from /usr/include/c++/6/algorithm:62,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:88,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qnamespace.h:37,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:41,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:40,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qsettings.h:37,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QSettings:1,
>  from qsamplerOptions.h:26,
>  from qsampler.cpp:24:
> /usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or 
> directory
>  #include_next 
>  ^
> compilation terminated.
> make[3]: *** [.obj/qsampler.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/qsampler_0.4.0-1_unstable_gcc6.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: qsampler
Source-Version: 0.4.0-2

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

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

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

Debian distribution maintenance software
pp.
Jaromír Mikeš  (supplier of updated qsampler 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: Wed, 20 Jul 2016 23:12:43 +0200
Source: qsampler
Binary: qsampler
Architecture: source amd64
Version: 0.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jaromír Mikeš 
Description:
 qsampler   - LinuxSampler GUI frontend based on the Qt toolkit
Closes: 83
Changes:
 qsampler (0.4.0-2) unstable; urgency=medium
 .
   * Add patch to build with gcc6. (Closes: #83)
   * Build with dh-autoreconf.
   * Tune .gitignore file.
   * Update copyright file.
   * Simplify 

Bug#812022: marked as pending

[James Cowgill]

tag 812022 pending
thanks

Hello,

Bug #812022 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/traverso.git;a=commitdiff;h=40a85c9

---
commit 40a85c9594750e9a7b0296aa2c1339d197a9398f
Author: James Cowgill 
Date:   Fri Jul 22 19:58:27 2016 +0100

Upload to unstable

diff --git a/debian/changelog b/debian/changelog
index a8d7c85..260ef2e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,21 @@
-traverso (0.49.4-2) UNRELEASED; urgency=medium
+traverso (0.49.4-2) unstable; urgency=medium
 
   * Team upload.
-  *
 
- -- James Cowgill   Fri, 22 Jul 2016 18:05:58 +0100
+  * debian/control:
+- Update VCS fields.
+- Bump standards to 3.9.8.
+  * debian/dirs:
+- Drop useless dirs file.
+  * debian/menu, debian/traverso.xpm
+- Drop menu file and xpm icon.
+  * debian/patches:
+- Fix FTBFS with GCC 6. (Closes: #812022)
+  * debian/rules:
+- Move linker flags to standard dpkg-buildflags variable.
+- Enable all hardening flags.
+
+ -- James Cowgill   Fri, 22 Jul 2016 18:36:57 +0100
 
 traverso (0.49.4-1) unstable; urgency=low
 

Processed: Bug#812022 marked as pending

[Debian Bug Tracking System]

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

> tag 812022 pending
Bug #812022 [traverso] traverso: FTBFS with GCC 6: flexible array member...
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#831111 marked as pending

[Debian Bug Tracking System]

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

> tag 83 pending
Bug #83 [src:qsampler] qsampler: FTBFS with GCC 6: cstdlib:75:25: fatal 
error: stdlib.h: No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#831111: marked as pending

[Jaromír Mikeš]

tag 83 pending
thanks

Hello,

Bug #83 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/qsampler.git;a=commitdiff;h=cd7861a

---
commit cd7861ac8b3f6d44f47d0e92a5012798fc409d4c
Author: Jaromír Mikeš 
Date:   Fri Jul 22 21:17:34 2016 +0200

Finalize changelog.

diff --git a/debian/changelog b/debian/changelog
index 2b50043..d0e7936 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,10 @@
-qsampler (0.4.0-2) UNRELEASED; urgency=medium
+qsampler (0.4.0-2) unstable; urgency=medium
 
-  * Start new upload.
+  * Add patch to build with gcc6. (Closes: #83)
+  * Build with dh-autoreconf.
+  * Tune .gitignore file.
+  * Update copyright file.
+  * Simplify gbp.conf file.
 
  -- Jaromír Mikeš   Wed, 20 Jul 2016 23:12:43 +0200
 

Bug#832133: Checklist for uploading new versions

[Pirate Praveen]

On 07/22/2016 11:50 PM, Pirate Praveen wrote:
> I think the solution is to build rails on a system which still has
> ruby-json 1.8.3 and upload that version to archive.
> 

I have built rails locally without strict dependency on ruby-json. If
someone can confirm its okay to upload, I can upload it.



signature.asc
Description: OpenPGP digital signature

Bug#817586: Info received (most: diff for NMU version 5.0.0a-2.4)

[Benj. Mako Hill]

> Hopefully everyone is fine with this and no harm done. If the
> maintainer wants any changes I'm happy to re-upload.

I can take a look and make any changes in my own upload.

Later,
Mako


-- 
Benjamin Mako Hill
http://mako.cc/

Creativity can be a social contribution, but only in so far
as society is free to use the results. --GNU Manifesto


signature.asc
Description: PGP signature

Bug#832133: Checklist for uploading new versions

[Pirate Praveen]

On 07/22/2016 11:46 PM, Pirate Praveen wrote:
> On 07/22/2016 11:22 PM, Pirate Praveen wrote:
>> The failure is at:
>>  ruby-activesupport : Depends: ruby-json (< 2.0) but 2.0.1+dfsg-1 is to
>> be installed
> 
> I tried relaxing the requirement in rails package and build, but it
> fails to build because of circular dependencies :(
> 

I think the solution is to build rails on a system which still has
ruby-json 1.8.3 and upload that version to archive.



signature.asc
Description: OpenPGP digital signature

Bug#832133: Checklist for uploading new versions

[Pirate Praveen]

On 07/22/2016 11:22 PM, Pirate Praveen wrote:
> The failure is at:
>  ruby-activesupport : Depends: ruby-json (< 2.0) but 2.0.1+dfsg-1 is to
> be installed

I tried relaxing the requirement in rails package and build, but it
fails to build because of circular dependencies :(



signature.asc
Description: OpenPGP digital signature

Bug#831170: qjackctl: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory

[Petter Reinholdtsen]

[Lucas Nussbaum]
> During a rebuild of all packages in sid using the gcc-defaults package
> available in experimental to make GCC default to version 6, your package 
> failed
> to build on amd64. For more information about GCC 6 and Stretch, see:
> - https://wiki.debian.org/GCC6
> - https://lists.debian.org/debian-devel-announce/2016/06/msg7.html
> 
> Relevant part (hopefully):
>> g++ -c -m64 -pipe -Wall -g -O2 -std=gnu++0x -Wall -W -D_REENTRANT -fPIC 
>> -DDATADIR="/usr/share" -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB 
>> -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. -I. -isystem 
>> /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/local/include -isystem 
>> /usr/include -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
>> /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem 
>> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
>> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
>> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
>> /usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I.ui 
>> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o .obj/qjackctl.o 
>> qjackctl.cpp

I asked on #debian-multimedia, and there they told me that the problem here is
the use of -isystem.  See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129 >.  I guess dropping it
will solve the build problem.

-- 
Happy hacking
Petter Reinholdtsen

Processed: severity of 829188 is important

[Debian Bug Tracking System]

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

> severity 829188 important
Bug #829188 [icedove] SEGVs too frequently (~every other day)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

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

[Carsten Schoenert]

Severity: important
thanks

On Fri, Jul 01, 2016 at 10:43:33AM +0100, Matthew Vernon wrote:
> Package: icedove
> Version: 1:45.1.0-1
> Severity: serious

decreasing the severity to important.

The package isn't violating the Debian policy nor the package is
unsuitable for release.

https://www.debian.org/Bugs/Developer#severities

Regards
Carsten

Bug#832133: Checklist for uploading new versions

[Pirate Praveen]

On 07/22/2016 10:41 PM, Lucas Nussbaum wrote:
> The failure you quoted is about a strict dependency. Do you know if it's
> justified? The changes on ruby-json's side are fairly small. Also it
> seems that the strict dependency was dropped from the gemspec (it's not
> there anymore in version 1.0.2 of validate_url).

The failure is at:
 ruby-activesupport : Depends: ruby-json (< 2.0) but 2.0.1+dfsg-1 is to
be installed

ruby-validate-url only declares ruby-activemodel as build dependency.

sbuild log was not very clear, cowbuilder log was more helpful.



signature.asc
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 17:53:53 +
with message-id 
and subject line Bug#831960: fixed in pygobject-2 2.28.6-13
has caused the Debian Bug report #831960,
regarding pygobject-2: FTBFS with dpkg-buildpackage -A: make: *** No rule to 
make target 'build-indep'.  Stop.
to be marked as done.

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

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


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

Hi,

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


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

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

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

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

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

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/pygobject-2_2.28.6-12_unstable_archallonly.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort  (supplier of updated pygobject-2 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 22 Jul 2016 19:25:33 +0200
Source: pygobject-2
Binary: python-gobject-2 python-gobject-2-dev python-gobject-2-dbg
Architecture: source
Version: 2.28.6-13
Distribution: unstable
Urgency: low
Maintainer: Josselin Mouette 
Changed-By: Emilio Pozuelo Monfort 
Description:
 python-gobject-2 - deprecated static Python bindings for the GObject library
 python-gobject-2-dbg - deprecated static Python bindings for the GObject 
library (debug
 python-gobject-2-dev - development headers for the static GObject Python 
bindings
Closes: 831960
Changes:
 pygobject-2 (2.28.6-13) unstable; urgency=low
 .
   * debian/rules:
 + Disable silent rules.
   * Add build-indep and build-arch targets. Closes: #831960.
Checksums-Sha1:
 f65ce421b84620b6006fc6dc716aba214cfd6595 2507 pygobject-2_2.28.6-13.dsc
 4eda7d2b97f495a2ad7d4cdc234d08ca5408d9d5 888240 pygobject-2_2.28.6.orig.tar.bz2
 1597dfc4aca57bd8d9c2c972be44d9f2ee6545cf 19200 
pygobject-2_2.28.6-13.debian.tar.xz
Checksums-Sha256:
 e2285e27fff9b0c72ab7127773211b12e58e4b5cd5896ddc6a1248a10b5718d2 2507 
pygobject-2_2.28.6-13.dsc
 e4bfe017fa845940184c82a4d8949db3414cb29dfc84815fb763697dc85bdcee 888240 
pygobject-2_2.28.6.orig.tar.bz2
 0c11a5d0e8545282b3a0ba818fa2e99900fdc6c594644178b8a7eba29ec1735e 19200 

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

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 17:54:00 +
with message-id 
and subject line Bug#831945: fixed in pygtk 2.24.0-5
has caused the Debian Bug report #831945,
regarding pygtk: FTBFS with dpkg-buildpackage -A: make: *** No rule to make 
target 'build-indep'.  Stop.
to be marked as done.

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

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


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

Hi,

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


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

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

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

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

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

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/pygtk_2.24.0-4_unstable_archallonly.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort  (supplier of updated pygtk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 22 Jul 2016 19:24:13 +0200
Source: pygtk
Binary: python-gtk2 python-gtk2-dbg python-gtk2-dev python-glade2 
python-gtk2-doc
Architecture: source
Version: 2.24.0-5
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Bacher 
Changed-By: Emilio Pozuelo Monfort 
Description:
 python-glade2 - GTK+ bindings: Glade support
 python-gtk2 - Python bindings for the GTK+ widget set
 python-gtk2-dbg - Python bindings for the GTK+ widget set (debug extension)
 python-gtk2-dev - GTK+ bindings: devel files
 python-gtk2-doc - Python bindings for the GTK+ widget set - documentation
Closes: 831945
Changes:
 pygtk (2.24.0-5) unstable; urgency=medium
 .
   * Add build-indep and build-arch targets. Closes: #831945.
Checksums-Sha1:
 870641028d2b6d3d69b2f5e0fe97a0fe0689f9ef 2870 pygtk_2.24.0-5.dsc
 95fce378c45e8d5aceb9640bd75ec2c7f4132880 3234341 pygtk_2.24.0.orig.tar.gz
 21ef5a512a24c73dd0863745fa4f7bb425a8b2a4 15568 pygtk_2.24.0-5.debian.tar.xz
Checksums-Sha256:
 ac336197cee8f59d05a11b940ce1b3f1af28bfa0ca84639ee887962d56054c48 2870 
pygtk_2.24.0-5.dsc
 6e3e54fa6e65a69ac60bd58cb2e60a57f3346ac52efe995f3d10b6c38c972fd8 3234341 
pygtk_2.24.0.orig.tar.gz
 cc13cc0c1a4dfef473bed11a6a0faa91937ec492ec1a358727fac974141c5202 15568 
pygtk_2.24.0-5.debian.tar.xz
Files:
 6645e78b054f383b4f23737108ca15cd 2870 python optional 

Bug#830359: marked as done (mini-buildd: FTBFS: unsatisfiable build-dependency: python-django (< 1.10) but 1:1.9.7-2 is to be installed)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 17:50:15 +
with message-id 
and subject line Bug#830359: fixed in mini-buildd 1.0.13
has caused the Debian Bug report #830359,
regarding mini-buildd: FTBFS: unsatisfiable build-dependency: python-django (< 
1.10) but 1:1.9.7-2 is to be installed
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.)


-- 
830359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mini-buildd
Version: 1.0.12
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):
> ┌──┐
> │ Install mini-buildd build dependencies (apt-based resolver) 
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-mini-buildd-dummy : Depends: python-django (< 1.10) but 
> 1:1.9.7-2 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/mini-buildd_1.0.12_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: mini-buildd
Source-Version: 1.0.13

We believe that the bug you reported is fixed in the latest version of
mini-buildd, 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.
Stephan Sürken  (supplier of updated mini-buildd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 22 Jul 2016 17:20:28 +
Source: mini-buildd
Binary: python-mini-buildd mini-buildd mini-buildd-common
Architecture: source all
Version: 1.0.13
Distribution: unstable
Urgency: medium
Maintainer: Stephan Sürken 
Changed-By: Stephan Sürken 
Description:
 mini-buildd - minimal build daemon - daemon
 mini-buildd-common - minimal build daemon - 08x upgrade dummy package
 python-mini-buildd - minimal build daemon - python library and user tool
Closes: 829337 830359 831749
Changes:
 mini-buildd (1.0.13) unstable; urgency=medium
 .
   * [09793e2] Add systemd unit file: mini-buildd.service.
   * [e76bfc0] control: Adapt dependencies to new python-django epoch in
 version. Thanks to Lucas Nussbaum (Closes: 830359)
   * [0fa253c] example packages: Autoconf files update.
   * [20f9301] pt_BR.po: Add translation for "Brazilian Portuguese". Thanks
 to Adriano Rafael Gomes (Closes: 829337)
   * [2c9ecc7] builder.py: Install gnupg explicitly before using apt-key
 (apt no longer depends on it). Thanks to Boyuan Yang (Closes: 831749)
Checksums-Sha1:
 56d0ee067a8389ba5dfddfc6422e29122dfa9c6a 2137 mini-buildd_1.0.13.dsc
 2edf06958413347aa90a732614a9f635b3797620 856272 mini-buildd_1.0.13.tar.xz
 60573612c75a4e474eb6e70da2964d09155dd908 75658 
mini-buildd-common_1.0.13_all.deb
 399b335b7b1ec18172a3508d1b517f2b7d7dda12 703614 mini-buildd_1.0.13_all.deb
 760c53dc9586a1409f815ebc63ce5d73f0f043c7 378146 
python-mini-buildd_1.0.13_all.deb

Bug#832133: Checklist for uploading new versions

[Pirate Praveen]

On 07/22/2016 10:41 PM, Lucas Nussbaum wrote:
> Hi,
> 
> yesterday on IRC:
> 23:29 < lucas> long time without doing any ruby packaging, let's hope I 
> didn't break the world
> 
> Looks like I did :/

I guessed :)

> The failure you quoted is about a strict dependency. Do you know if it's
> justified? The changes on ruby-json's side are fairly small. Also it
> seems that the strict dependency was dropped from the gemspec (it's not
> there anymore in version 1.0.2 of validate_url).

Generally a major version bump means it broke compatibility with
previous versions.

> Sorry about that, but before reverting, we should probably evaluate what
> is the exact damage: it's not reasonable to stick to older version just
> because other packages have unjustified(?) strict dependencies.

49 packages depends on ruby-json and it may not be really breaking
anything, but since its a major version we should check all or if we are
really sure it did not introduce any breaking change, we can just relax
the strict dependency. But it would be much better if we handle the
relaxing part before uploading.

> Lucas
> 




signature.asc
Description: OpenPGP digital signature

Bug#832133: ruby-json 2.0 broke rails: metabug to prevent testing migration

[Pirate Praveen]

package: ruby-json
version: 2.0.1+dfsg-1
severity: grave

ruby-json upload just broke rails and a whole lot of dependencies.

The following packages have unmet dependencies:
 ruby-activesupport : Depends: ruby-json (< 2.0) but 2.0.1+dfsg-1 is to
be installed

One sample failure
https://ci.debian.net/data/packages/unstable/amd64/r/ruby-validate-url/latest-autopkgtest/log.gz

We need to test compatibility of all these reverse dependencies. It
would have been much better if we tested these _before_ the upload.

$ apt-cache rdepends ruby-json|uniq
ruby-json
Reverse Depends:
  ruby-swd
  whatweb
  tdiary
 |shelr
  ruby-twitter-oauth
  ruby-tinder
  ruby-activesupport
  ruby-source-map
  ruby-simplecov
  ruby-sidekiq
  ruby-sequel
  ruby-sdoc
  ruby-ridley
  ruby-rabl-rails
  ruby-rabl
  ruby-openstack
  ruby-omniauth-twitter
  ruby-json-schema
  ruby-influxdb
  ruby-gon
  ruby-gemojione
  ruby-gelf
  ruby-fog-libvirt
  ruby-azure
  ruby-aws-sdk
  ruby-autoprefixer-rails
  ruby-asetus
  ruby-appraiser
  how-can-i-help
  ruby-activesupport
  r10k
  pcs
  opennebula-context
  opennebula-sunstone
  opennebula-gate
  opennebula-flow
  mikutter
  mcollective-common
  librarian-puppet
  coquelicot
  hiera
  gist
  fencing-agent
  fuel-nailgun-agent
  foremancli
  facter
  diaspora



signature.asc
Description: OpenPGP digital signature

Bug#830672: marked as done (golang-github-azure-go-autorest: accesses the internet during build)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 17:22:29 +
with message-id 
and subject line Bug#830672: fixed in golang-github-azure-go-autorest 7.0.4-2
has caused the Debian Bug report #830672,
regarding golang-github-azure-go-autorest: 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.)


-- 
830672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-azure-go-autorest
Version: 7.0.4-1
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst golang-github-azure-go-autorest 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 17e100504765.35716 > dnscache.uct.ac.za.domain: 33685+ 
? microsoft.com. (31)
  00:00:00.48 IP 17e100504765.33860 > dnscache.uct.ac.za.domain: 20870+ A? 
microsoft.com. (31)
  00:00:00.017802 IP dnscache.uct.ac.za.domain > 17e100504765.33860: 20870 
5/4/8 A 104.40.211.35, A 104.43.195.251, A 23.100.122.175, A 23.96.52.53, A 
191.239.213.197 (367)
  00:00:00.208338 IP dnscache.uct.ac.za.domain > 17e100504765.35716: 33685 
0/1/0 (86)
  00:00:00.208773 IP 17e100504765.35524 > 104.40.211.35.https: Flags [S], seq 
480852211, win 29200, options [mss 1460,sackOK,TS val 120877368 ecr 
0,nop,wscale 7], length 0
  00:00:00.422695 IP 104.40.211.35.https > 17e100504765.35524: Flags [S.], seq 
4072704715, ack 480852212, win 8192, options [mss 1440,nop,wscale 8,sackOK,TS 
val 216103281 ecr 120877368], length 0

  [..]

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


Regards,

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


golang-github-azure-go-autorest.7.0.4-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: golang-github-azure-go-autorest
Source-Version: 7.0.4-2

We believe that the bug you reported is fixed in the latest version of
golang-github-azure-go-autorest, 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.
Martín Ferrari  (supplier of updated 
golang-github-azure-go-autorest package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 22 Jul 2016 16:18:42 +
Source: golang-github-azure-go-autorest
Binary: golang-github-azure-go-autorest-dev
Architecture: source all
Version: 7.0.4-2
Distribution: unstable
Urgency: medium
Maintainer: pkg-go 
Changed-By: Martín Ferrari 
Description:
 golang-github-azure-go-autorest-dev - HTTP request pipeline suitable for use 
across multiple go-routine
Closes: 830672
Changes:
 golang-github-azure-go-autorest (7.0.4-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Paul Tagliamonte ]
   * Use a secure transport for the Vcs-Git and Vcs-Browser URL
 .
   [ Martín Ferrari ]
   * debian/control:
 - Update dh-golang dependency.
 - Update Standards-Version (no changes).
 - Remove Built-Using.
   * debian/rules: Use --no-binaries.
   * Patch tests that try to access the network. Closes: #830672.
   * Install README.md file.
Checksums-Sha1:
 2f25a61a4c34da6edaf7c6ec7f738be9e9480713 2297 
golang-github-azure-go-autorest_7.0.4-2.dsc
 f06c7732417c7aa4134d7bc2b1f93f83186084e3 3156 
golang-github-azure-go-autorest_7.0.4-2.debian.tar.xz
 c79cc6a299ee51526305cb452037cdd9432749e3 51358 
golang-github-azure-go-autorest-dev_7.0.4-2_all.deb
Checksums-Sha256:
 f44e6fb68546d676920ea6b984f45e6bb8f84bf09f5d4475416c5770af8b71e9 2297 
golang-github-azure-go-autorest_7.0.4-2.dsc
 6ef017fdfd7080793f6e0aa24da06ece08092ac56e09db3fc67954e6a4c4227e 3156 
golang-github-azure-go-autorest_7.0.4-2.debian.tar.xz
 550721c7c152e580f516aa20063ab4a19b4d611f4215f2884d289d704eedb42f 51358 
golang-github-azure-go-autorest-dev_7.0.4-2_all.deb
Files:
 217c5c7cb39151d2c3d979414016e1f7 2297 devel extra 

Bug#831814: marked as done (lepton: CVE-2016-6234 CVE-2016-6235 CVE-2016-6236 CVE-2016-6237 CVE-2016-6238)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 17:24:24 +
with message-id 
and subject line Bug#831814: fixed in lepton 1.2.1-1
has caused the Debian Bug report #831814,
regarding lepton: CVE-2016-6234 CVE-2016-6235 CVE-2016-6236 CVE-2016-6237 
CVE-2016-6238
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.)


-- 
831814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lepton
Version: 1.0-2
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

Multiple issues were found in lepton. The CVE request was at
http://www.openwall.com/lists/oss-security/2016/07/17/1 referencing
https://github.com/dropbox/lepton/issues/26 (note to compile with
address sanitizer to reproduce the issues).

lepton got several CVE assigned in subsequent
http://www.openwall.com/lists/oss-security/2016/07/17/6

I'm not sure if current master fixes all the reported cases from #26.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: lepton
Source-Version: 1.2.1-1

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

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

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

Debian distribution maintenance software
pp.
ChangZhuo Chen (陳昌倬)  (supplier of updated lepton package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 23 Jul 2016 00:43:13 +0800
Source: lepton
Binary: lepton
Architecture: source amd64
Version: 1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: ChangZhuo Chen (陳昌倬) 
Description:
 lepton - tool to compress JPEGs losslessly
Closes: 831814 831897
Changes:
 lepton (1.2.1-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #831814
   * Kill lepton after unit test to ensure no process leaves after build.
 Closes: #831897
   * Set architecture to i386 amd64 x32 due to SSE.
Checksums-Sha1:
 39a2e0a067889d05c3409d8e977ea01d80e4d89e 2027 lepton_1.2.1-1.dsc
 fe246da5d87a666bd69d3e4c19f3b80ccb5a9044 50226336 lepton_1.2.1.orig.tar.gz
 2ab3523ba372642debbdd1275a138141675ff03a 5488 lepton_1.2.1-1.debian.tar.xz
 357e122afcd7edd7f9c3f90364978e985ff058aa 1525772 
lepton-dbgsym_1.2.1-1_amd64.deb
 76f6b04cda18a715f88058fb46558ea181a4063f 149396 lepton_1.2.1-1_amd64.deb
Checksums-Sha256:
 a49dcb17c352e7e4e413557a17b4260f99dd8f8f3bcf21d8988072c91781b571 2027 
lepton_1.2.1-1.dsc
 c4612dbbc88527be2e27fddf53aadf1bfc117e744db67e373ef8940449cdec97 50226336 
lepton_1.2.1.orig.tar.gz
 4d21ae6137be48217d922ee680b0e9c002458333731421e79f477dab07dff475 5488 
lepton_1.2.1-1.debian.tar.xz
 6422bc0b984d7d8d774ea822cfd9098b218991668d998fa75abebdaf032e00d8 1525772 
lepton-dbgsym_1.2.1-1_amd64.deb
 ea0d1cac132e26f631953f70c81319ebecf335de71545d4d73c1c16ad88139a7 149396 
lepton_1.2.1-1_amd64.deb
Files:
 dc06bed90a5675ce2630f8a8d200d750 2027 graphics optional lepton_1.2.1-1.dsc
 79fad1d65eb68efed0222b1db4916429 50226336 graphics optional 
lepton_1.2.1.orig.tar.gz
 f281ca2f3cacae9fa5be7887179fe3ff 5488 graphics optional 
lepton_1.2.1-1.debian.tar.xz
 cb26ba11dd6d2475aad15478082a5b1b 1525772 debug extra 
lepton-dbgsym_1.2.1-1_amd64.deb
 100e4036def98e3002538099e8c7e827 149396 graphics optional 
lepton_1.2.1-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXklFAAAoJELTYlw90nD9qB0oQAIjDoZvmrDNwP4oP3JqT5F39
agXKYl2NJvIAztzQce90jLAk7x93le0sFgzoDmudzNhm5GHCyZeyVFqas7xbvR9G
Z2j1bBrkRSOBo7cvZOddKhjI/waMy8b8LDkvmwMhuFgC24XYKnipnJlLCgu7pXGG
Lg/qn1cYd1/jafeDPMK/HeA4vxcWvcoy+MPthIfJzbQdB4775Y60JqiYqWfDXIOy
mSolGfhfJA+WOsv0eUTENV15rjYNlA7FKxWyLvTi0oKnpwk6Ad+A/WyUT+6oO3z2
t/piyuYhBXFWMo5GdT/9tDCV6jUj/ruSA+e+NDV1RGktq7PMKToBgI6RHlwjjBFq
AGC1E3OJZKdvPOWE54CfZiC/8ebKiQXRTbdQP1DSkBoy4SCRBbuoteA6e1neOlrH
jYTeQCR8yUOfmAW0cXMG+R21HZ1lUzYRfIsqtFC3ytS2S/p8cNCjNUszdmaEshx2
Xg/O1njTwo/P8Hy9WLkjgoBqAdA/PNm88Nqd8niJfyxqe0jkZwSsZ75+KUGti/Vb
qDgyAyBfiq0ZyuXoLCPYHyCy8m9h/QsJy61KOOuY1/WBs1REJNw0RHcV6/+oHsdo

Processed: limit source to pygobject-2, tagging 831960

[Debian Bug Tracking System]

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

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

> tags 831960 + pending
Bug #831960 [src:pygobject-2] pygobject-2: FTBFS with dpkg-buildpackage -A: 
make: *** No rule to make target 'build-indep'.  Stop.
Ignoring request to alter tags of bug #831960 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: Re: Bug#812022: traverso: FTBFS with GCC 6: flexible array member...

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - patch
Bug #812022 [traverso] traverso: FTBFS with GCC 6: flexible array member...
Removed tag(s) patch.

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

Bug#831897: marked as done (lepton: leaves a zombie process around after build)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 17:24:24 +
with message-id 
and subject line Bug#831897: fixed in lepton 1.2.1-1
has caused the Debian Bug report #831897,
regarding lepton: leaves a zombie process around after 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.)


-- 
831897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: lepton
version: 1.0-2
severity: serious
user: reproducible-bui...@lists.alioth.debian.org
usertags: ftbfs
x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org

Dear maintainer,
while building packages I noticed that a builder stuck for a very long
time.  After inspection turns out it was waiting to be able to umount
/proc, which was kept busy by a process like
./lepton -socket=/tmp/f93406ea-94c9-45e3-a35b-bdfb1452a9ec -timebound=10ms 
-preload
with an open fd.

Killing that process unlocked the situation.

I was able to reproduce this in my notebook too.

That said, I find totally unacceptable for a build to leak a process and
leave it zombie (because that process had no parent, actually), so I'm
filing this at RC level.

(PS: in the meantime, blacklisted for reproducibility testing, but be
happy the build was reproducible (after having poked it) ;))

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: lepton
Source-Version: 1.2.1-1

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

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

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

Debian distribution maintenance software
pp.
ChangZhuo Chen (陳昌倬)  (supplier of updated lepton package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 23 Jul 2016 00:43:13 +0800
Source: lepton
Binary: lepton
Architecture: source amd64
Version: 1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: ChangZhuo Chen (陳昌倬) 
Description:
 lepton - tool to compress JPEGs losslessly
Closes: 831814 831897
Changes:
 lepton (1.2.1-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #831814
   * Kill lepton after unit test to ensure no process leaves after build.
 Closes: #831897
   * Set architecture to i386 amd64 x32 due to SSE.
Checksums-Sha1:
 39a2e0a067889d05c3409d8e977ea01d80e4d89e 2027 lepton_1.2.1-1.dsc
 fe246da5d87a666bd69d3e4c19f3b80ccb5a9044 50226336 lepton_1.2.1.orig.tar.gz
 2ab3523ba372642debbdd1275a138141675ff03a 5488 lepton_1.2.1-1.debian.tar.xz
 357e122afcd7edd7f9c3f90364978e985ff058aa 1525772 
lepton-dbgsym_1.2.1-1_amd64.deb
 76f6b04cda18a715f88058fb46558ea181a4063f 149396 lepton_1.2.1-1_amd64.deb
Checksums-Sha256:
 a49dcb17c352e7e4e413557a17b4260f99dd8f8f3bcf21d8988072c91781b571 2027 
lepton_1.2.1-1.dsc
 c4612dbbc88527be2e27fddf53aadf1bfc117e744db67e373ef8940449cdec97 50226336 
lepton_1.2.1.orig.tar.gz
 4d21ae6137be48217d922ee680b0e9c002458333731421e79f477dab07dff475 5488 
lepton_1.2.1-1.debian.tar.xz
 6422bc0b984d7d8d774ea822cfd9098b218991668d998fa75abebdaf032e00d8 1525772 
lepton-dbgsym_1.2.1-1_amd64.deb
 ea0d1cac132e26f631953f70c81319ebecf335de71545d4d73c1c16ad88139a7 149396 
lepton_1.2.1-1_amd64.deb
Files:
 dc06bed90a5675ce2630f8a8d200d750 2027 graphics optional lepton_1.2.1-1.dsc
 79fad1d65eb68efed0222b1db4916429 50226336 graphics optional 
lepton_1.2.1.orig.tar.gz
 f281ca2f3cacae9fa5be7887179fe3ff 5488 graphics optional 
lepton_1.2.1-1.debian.tar.xz
 cb26ba11dd6d2475aad15478082a5b1b 1525772 debug extra 
lepton-dbgsym_1.2.1-1_amd64.deb
 100e4036def98e3002538099e8c7e827 149396 graphics optional 
lepton_1.2.1-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Processed: limit source to pygtk, tagging 831945

[Debian Bug Tracking System]

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

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

> tags 831945 + pending
Bug #831945 [src:pygtk] pygtk: FTBFS with dpkg-buildpackage -A: make: *** No 
rule to make target 'build-indep'.  Stop.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: limit source to pygobject-2, tagging 831960

[Debian Bug Tracking System]

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

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

> tags 831960 + pending
Bug #831960 [src:pygobject-2] pygobject-2: FTBFS with dpkg-buildpackage -A: 
make: *** No rule to make target 'build-indep'.  Stop.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: limit source to pygobject-2, tagging 831960

[Debian Bug Tracking System]

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

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

> tags 831960 + pending
Bug #831960 [src:pygobject-2] pygobject-2: FTBFS with dpkg-buildpackage -A: 
make: *** No rule to make target 'build-indep'.  Stop.
Ignoring request to alter tags of bug #831960 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: limit source to pygtk, tagging 831945

[Debian Bug Tracking System]

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

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

> tags 831945 + pending
Bug #831945 [src:pygtk] pygtk: FTBFS with dpkg-buildpackage -A: make: *** No 
rule to make target 'build-indep'.  Stop.
Ignoring request to alter tags of bug #831945 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#812022: traverso: FTBFS with GCC 6: flexible array member...

[James Cowgill]

Control: tags -1 - patch

Hi,

On Fri, 2016-07-22 at 15:31 +0200, intrigeri wrote:
> Hi,
> 
> The package has been removed from testing even though a patch was
> proposed 6 months ago, so I'm wondering: what's the status here?

Not sure why nothing happened, but the package still FTBFS with gcc 6
even after applying the patch. I'll take a look at it.

James

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

Bug#829360: closed by Jan Mojžíš <jan.moj...@gmail.com> (Bug#829360: fixed in dq 20160720-1)

[Mike Miller]

On Thu, Jul 21, 2016 at 16:57:13 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the dqcache-run package:
> 
> #829360: dqcache-run: priority is standard but depends on optional packages
> 
> It has been closed by Jan Mojžíš .

Please also file a ftp-master override bug to fix the priority in the
archive, see https://wiki.debian.org/FtpMaster/Override.

I didn't mention this earlier, but I see you are a new maintainer and
may not be aware that the priority in the repository is not changed with
each upload.

Thanks!

-- 
mike

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

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 16:39:02 +
with message-id 
and subject line Bug#830931: fixed in ruby-ruby2ruby 2.3.0-1
has caused the Debian Bug report #830931,
regarding Gem::LoadError: Could not find 'ruby2ruby' (>= 0) among 13 total 
gem(s)
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.)


-- 
830931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
  `-
--- End Message ---
--- Begin Message ---
Source: ruby-ruby2ruby
Source-Version: 2.3.0-1

We believe that the bug you reported is fixed in the latest version of
ruby-ruby2ruby, 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.
Cédric Boutillier  (supplier of updated ruby-ruby2ruby 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 21 Jul 2016 05:34:56 +0200
Source: ruby-ruby2ruby
Binary: ruby-ruby2ruby
Architecture: source
Version: 2.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-ruby2ruby - Generate pure ruby code easily from ParseTree's Sexps
Closes: 830931
Changes:
 ruby-ruby2ruby (2.3.0-1) unstable; urgency=medium
 .
   * Team upload
   * Imported Upstream version 2.3.0
   * The gemspec file gets installed (Closes: #830931)
   * Bump debhelper compatibility level to 9
   * Remove version in the gem2deb build-dependency
   * Use https:// in Vcs-* fields
   * Bump Standards-Version to 3.9.8 (no changes needed)
   * Run wrap-and-sort on packaging files
   * Drop dont_require_rubygems patch. Not needed any more
   * Set Testsuite field to autopkgtest-pkg-ruby
   * Set minimal version for ruby-sexp-processor dependency to 4.7
   * Add read_ruby2ruby.patch
Checksums-Sha1:
 b348440ba5829f4feeec832cdb032338f3e76a4e 1794 ruby-ruby2ruby_2.3.0-1.dsc
 555e1254c0d39986bd24f338ce7f7f5319a6c6e5 19716 ruby-ruby2ruby_2.3.0.orig.tar.gz
 557086d2cad17bd333c1d4e16ed526f839008536 3204 
ruby-ruby2ruby_2.3.0-1.debian.tar.xz
Checksums-Sha256:
 abe12aa8d2904785eb3158f8eba8bc4f058f36019f4f0858988f34c70d439d6c 1794 
ruby-ruby2ruby_2.3.0-1.dsc
 84dd18053707e935aad1b139b70d867205a75f6a98e89f030d9aede4e9921596 19716 
ruby-ruby2ruby_2.3.0.orig.tar.gz
 d2029e8e01ea4a25ff36022cf7a9f583789d5e05a5a0299ca4784a88bae80c56 3204 
ruby-ruby2ruby_2.3.0-1.debian.tar.xz
Files:
 49f3e322a90f1f6825ad9df45d430cd8 1794 ruby optional ruby-ruby2ruby_2.3.0-1.dsc
 0da07f0fc9598acf8f5c41aaee9665b7 19716 ruby optional 
ruby-ruby2ruby_2.3.0.orig.tar.gz
 daef427dc06eae8c44938f547172a1fc 3204 ruby optional 
ruby-ruby2ruby_2.3.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJXkibeAAoJEImvgrc5zSF6lJAH/jojOeqsf9BAr69K5jjNo/pj
DCcbaKwsQkJWk1RgMCBpRsEjEfARAKX67Cp9HzeclhOyzlp1bRY7qHkVrqJKWSvo
gSGz/cornI/Z/ndmPDdbLejSGh62U8Asfcs0P+sZIndMD0+B/3RNQxkj52J3i4Ch
CsGehg75SPl91kr/I3m4rAYx6eLtWJ97rvNdT9RYqpCi3VrHeks9wRXNYKs41gvW
3YnJOAeYTpdEl4gSVBgGJqMlA4Xfvknm3THXHHPdsHaOKF0gA79eU+JfPcAIzy7t
Q6d6K1dlc7KADJE1N/BRw4x9PyQnh1vbyJWej4M0s8/cvjO20CElquWpoXpb6F8=
=DT4o
-END PGP SIGNATURE End Message ---

Bug#830496: marked as done (libspring-java: FTBFS: Could not resolve javax.el:el-api:2.2.)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 16:33:59 +
with message-id 
and subject line Bug#830496: fixed in libspring-java 4.1.9-2
has caused the Debian Bug report #830496,
regarding libspring-java: FTBFS: Could not resolve javax.el:el-api:2.2.
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.)


-- 
830496: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libspring-java
Version: 4.1.9-1
Severity: serious

>From my pbuilder build log:

...
:spring-web:compileJava (Thread[main,5,main]) completed. Took 0.18 secs.

FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all dependencies for configuration
':spring-web:compileClasspath'.
> Could not resolve javax.el:el-api:2.2.
  Required by:
  org.springframework:spring-web:4.1.9.RELEASE >
javax.servlet.jsp:javax.servlet.jsp-api:2.2.1
   > No cached version of javax.el:el-api:2.2 available for offline mode.
> Could not resolve javax.servlet:servlet-api:2.2.
  Required by:
  org.springframework:spring-web:4.1.9.RELEASE >
javax.servlet.jsp:javax.servlet.jsp-api:2.2.1
   > No cached version of javax.servlet:servlet-api:2.2 available for
offline mode.

* Try:
Run with --debug option to get more log output.

* Exception is:
org.gradle.api.artifacts.ResolveException: Could not resolve all
dependencies for configuration ':spring-web:compileClasspath'.
at 
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration.rethrowFailure(DefaultLenientConfiguration.java:62)
at 
org.gradle.api.internal.artifacts.ivyservice.DefaultResolvedConfiguration.rethrowFailure(DefaultResolvedConfiguration.java:36)
at 
org.gradle.api.internal.artifacts.ivyservice.SelfResolvingDependencyConfigurationResolver$FilesAggregatingResolvedConfiguration.rethrowFailure(SelfResolvingDependencyConfigurationResolver.java:112)
at 
org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver$ErrorHandlingResolvedConfiguration.rethrowFailure(ErrorHandlingConfigurationResolver.java:189)
at 
org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$ConfigurationFileCollection.getFiles(DefaultConfiguration.java:666)
at 
org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.getFiles(DefaultConfiguration.java:292)
at 
org.gradle.api.internal.artifacts.configurations.DefaultConfiguration_Decorated.getFiles(Unknown
Source)
at 
org.gradle.api.internal.file.collections.DefaultFileCollectionResolveContext$FileTreeConverter.convertInto(DefaultFileCollectionResolveContext.java:202)
at 
org.gradle.api.internal.file.collections.DefaultFileCollectionResolveContext.doResolve(DefaultFileCollectionResolveContext.java:103)
at 
org.gradle.api.internal.file.collections.DefaultFileCollectionResolveContext.resolveAsFileTrees(DefaultFileCollectionResolveContext.java:74)
at 
org.gradle.api.internal.file.collections.DefaultFileCollectionResolveContext$FileTreeConverter.convertInto(DefaultFileCollectionResolveContext.java:188)
at 
org.gradle.api.internal.file.collections.DefaultFileCollectionResolveContext.doResolve(DefaultFileCollectionResolveContext.java:98)
at 
org.gradle.api.internal.file.collections.DefaultFileCollectionResolveContext.resolveAsFileTrees(DefaultFileCollectionResolveContext.java:74)
at 
org.gradle.api.internal.changedetection.state.DefaultFileCollectionSnapshotter.visitFiles(DefaultFileCollectionSnapshotter.java:41)
at 
org.gradle.api.internal.changedetection.state.AbstractFileCollectionSnapshotter.snapshot(AbstractFileCollectionSnapshotter.java:57)
at 
org.gradle.api.internal.changedetection.state.DefaultFileCollectionSnapshotter.snapshot(DefaultFileCollectionSnapshotter.java:29)
at 
org.gradle.api.internal.changedetection.rules.AbstractFileSnapshotTaskStateChanges.createSnapshot(AbstractFileSnapshotTaskStateChanges.java:47)
at 
org.gradle.api.internal.changedetection.rules.InputFilesTaskStateChanges.(InputFilesTaskStateChanges.java:33)
at 
org.gradle.api.internal.changedetection.rules.TaskUpToDateState.(TaskUpToDateState.java:52)
at 
org.gradle.api.internal.changedetection.changes.DefaultTaskArtifactStateRepository$TaskArtifactStateImpl.getStates(DefaultTaskArtifactStateRepository.java:142)
at 
org.gradle.api.internal.changedetection.changes.DefaultTaskArtifactStateRepository$TaskArtifactStateImpl.isUpToDate(DefaultTaskArtifactStateRepository.java:73)
at 

Bug#817373: bb: Removal of debhelper compat 4

[Uwe Hermann]

Hi,

On Thu, Jul 21, 2016 at 07:32:24PM +0200, Axel Beckert wrote:
> Uwe: Feel free to tell me if I should fast-forward it or if I should
> delay it longer.

Feel free to fast-forward / NMU, looks good to me from a quick glance.

 
> P.S.: Uwe: Do you want a co-maintainer for bb?

Sure, feel free to add yourself as co-maintainer / uploader etc., or if
you like you can also take over the package completely. Let me know if I
should post an "official" RFA for that, or just feel free to adopt it
right away. I'm currently short on spare time so another maintainer
would be great.


Cheers, Uwe.
-- 
http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org

Processed: Pending fixes for bugs in the golang-github-azure-go-autorest package

[Debian Bug Tracking System]

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

> tag 830672 + pending
Bug #830672 [src:golang-github-azure-go-autorest] 
golang-github-azure-go-autorest: accesses the internet during build
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#830672: Pending fixes for bugs in the golang-github-azure-go-autorest package

[pkg-go-maintainers]

tag 830672 + pending
thanks

Some bugs in the golang-github-azure-go-autorest package are closed
in revision 9b6c0859ba2a0bdb6ca5822ec40e6f49a3445632 in branch
'master' by Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-azure-go-autorest.git/commit/?id=9b6c085

Commit message:

Patch tests that try to access the network. Closes: #830672.

Processed: inventor: FTBFS with GCC 6: narrowing conversion

[Debian Bug Tracking System]

Processing control commands:

> tags 811781 patch
Bug #811781 [inventor] inventor: FTBFS with GCC 6: narrowing conversion
Added tag(s) patch.

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

Processed: severity of 805002 is normal

[Debian Bug Tracking System]

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

> severity 805002 normal
Bug #805002 [apparmor] libvirt-client: "virsh attach-disk" fails with AppArmor 
enabled 
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#832127: libtest-aggregate-perl: Breaks with Test-Simple >= 1.3

[gregor herrmann]

Package: libtest-aggregate-perl
Version: 0.372-2
Severity: serious
Tags: upstream
Justification: not fit for release
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=100035

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Test::Aggregate up to 0.373 doesn't work with the new Test-Simple
(>= 1.3), in libtest-simple-perl (still in experimental but will go
into unstable soon), and in perl core since 5.25.1 (not in Debian for
another ~9 months). The new libtest-simple-perl already has a Breaks
on libtest-aggregate-perl.

So the current versions 0.372-2/testing and 0.373-1/unstable should
not go into a release.

I fixed the 2 reverse build dependencies, so libtest-aggregate-perl
can savely be removed from testing (and wait in unstable for an
upstream fix).


Cheers,
gregor

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXkjtmXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG/AAP/1e7mG1CwSMn//fk2FTcBecJ
yHrDsWSKv/CjDiM0mR888KYZ0LfVW9uzME+V9XtSV4jhO5nKV9e71AjJqgJ3+Dce
gqX26FfgbCIXXnANEJ0nv5G8LXu6tQpxGRZuNl1ijqwJQwqIrObBi9SvliTensmk
B5M1FD88fLcn4hk46Wa9zdwc/4U4mwroaw9hqvID+v2bOPWt+3qBPpslwCwkENvP
lgOx1X94QnSzyCQaiUHsVp18V4H/uP/ual6EvsF3jlCKv8I6mCg9/DSMFNerPg29
vVoccxGGylDIJkjujfR+K78PoiAj0bw0Tnas8OL6/cVRAiV8pO2gYbT/rpB/kjEa
m1Klek/RuFYhjxBaerDtuJwTvuAjAyixePCEJTCjCZB/pxQ1ULnqTTJsRZKft6EZ
pTYaTMNMfJPGqSBe5iIdOsxipdxC7ABsvQ9phpo6StXey8/gTCBz71kCVcGsFur0
gOykajZf7H5By+yuxJ8o9GiXOP43KPOw8R+AfkJpKiA2G3cMfNlDy97GHmqsI/2F
7ofx2FWpCryGXOHt5/BUP3vuDzt4ZaO/q6XyZKHTWibi4AqzDoqoKdng7hxj7orz
tUUCC4A25yfJnbOxox4E2+b4/aZwllumzVBSNskVj6KJcCqSMbfBfmcBv/6D1Z8U
7x9ihncOlDWteMU61MoH
=7IHz
-END PGP SIGNATURE-

Bug#832103: docker.io: Can't run images after upgrading to 1.11.2~ds1-6

[Sandro Knauß]

hey,

> > downgrading to 1.11.2~ds1-5 and restart the daemon fixed the problem:
> Did you try restarting the daemon before you downgraded? (and if not,
> would you be willing to upgrade again and give it a shot?)

I thought, that I restarted my machine in between. I gave it another try and 
restarted the daemon afterwards and this fixed the problem. So only the 
restarting is missing.

Regards,

sandro



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

Bug#831825: gcompris: Crash when i click on menu

[Theodore Lytras]

I get the exact same crash, under sid amd64. 
It seems to have something to do with the sound. 

When the game starts it plays the intro music. As long as the music plays, I 
can click wherever I want with no crash. When the music finishes, if I click 
on anything (not just the menu) the game crashes. Now if I turn off both music 
and sounds while the intro music plays, then I can play without problems. If 
music or sounds are turned on again, then the game crashes on first click.

Therefore it has something to do with the sound. 
I also tried installing package canberra-gtk-module, to no effect.

I should also mention that my machine has no pulseaudio (only ALSA) and the 
sound chip is a realtek alc892. On another debian sid amd64 machine, with 
intel sound chip + pulseaudio, this bug is not reproduced. I didn't try 
installing pulseaudio on my first machine to see whether it makes any 
difference (why should it?)...

Processed (with 1 error): forcibly merging 731400 738423

[Debian Bug Tracking System]

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

> forcemerge 731400 738423
Bug #731400 [src:ocamlduce] ocamlduce: needs update for ocaml 4.01.0
Bug #738423 [src:ocamlduce] ocamlduce: FTBFS: tar: 
/usr/src/ocaml-source-4.01.0.tar.bz2: Cannot open: No such file or directory
Failed to forcibly merge 731400: Not altering archived bugs; see unarchive.

> thanks
Stopping processing here.

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

Bug#832125: chromium: Chromium immediately crashes

[Nils Dagsson Moskopp]

Package: chromium
Version: 51.0.2704.79-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I started chromium. It crashed immediately with SIGSEGV. dmesg(1) tells me:

--- snib ---
[153066.919129] chromium[15304]: segfault at 10 ip aa110788 sp bfb16160 error 4 
in libnettle.so.4.7[aa0ee000+33000]
--- snab ---

I expected chromium to not crash; it has worked fine a lot of times before.

Attached is strace output for the crash.

-- System Information:
Debian Release: 8.5
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages chromium depends on:
ii  libasound2   1.0.28-1
ii  libatk1.0-0  2.14.0-1
ii  libavcodec57 7:3.1.1-2
ii  libavformat577:3.1.1-2
ii  libavutil55  7:3.1.1-2
ii  libc62.19-18+deb8u4
ii  libcairo21.14.0-2.1+deb8u1
ii  libcups2 2.1.4-4
ii  libdbus-1-3  1.10.8-1
ii  libexpat12.1.0-6+deb8u3
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-3+deb8u1
ii  libgcc1  1:4.9.2-10
ii  libgdk-pixbuf2.0-0   2.31.1-2+deb8u5
ii  libglib2.0-0 2.48.1-2
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk2.0-0  2.24.25-3+deb8u1
ii  libharfbuzz0b0.9.35-2
ii  libjpeg62-turbo  1:1.3.1-12
ii  libnspr4 2:4.12-2
ii  libnss3  2:3.23-2
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpci3  1:3.3.1-1.1
ii  libspeechd2  0.8-7
ii  libstdc++6   6.1.1-9
ii  libx11-6 2:1.6.2-3
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2+b2
ii  libxi6   2:1.7.4-1+b2
ii  libxml2  2.9.1+dfsg1-5+deb8u2
ii  libxrandr2   2:1.4.2-1+b1
ii  libxrender1  1:0.9.8-1+b1
ii  libxslt1.1   1.1.28-2+deb8u1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+2
ii  xdg-utils1.1.1-1

Versions of packages chromium recommends:
ii  fonts-liberation  1.07.4-1

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information
execve("/usr/bin/chromium", ["chromium"], [/* 54 vars */]) = 0
brk(NULL)   = 0xb80f9000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb773
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=99503, ...}) = 0
mmap2(NULL, 99503, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7717000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/i386-linux-gnu/i686/cmov/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, 
"\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300\233\1\0004\0\0\0"..., 512) 
= 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1750780, ...}) = 0
mmap2(NULL, 1755772, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0xb756a000
mmap2(0xb7711000, 12288, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a7000) = 0xb7711000
mmap2(0xb7714000, 10876, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7714000
close(3)= 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb7569000
set_thread_area({entry_number:-1, base_addr:0xb7569940, limit:1048575, 
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, 
useable:1}) = 0 (entry_number:6)
mprotect(0xb7711000, 8192, PROT_READ)   = 0
mprotect(0xb7773000, 4096, PROT_READ)   = 0
mprotect(0xb7754000, 4096, PROT_READ)   = 0
munmap(0xb7717000, 99503)   = 0
getpid()= 17664
rt_sigaction(SIGCHLD, {0xb7766bc0, ~[RTMIN RT_1], 0}, NULL, 8) = 0
geteuid32() = 1000
brk(NULL)   = 0xb80f9000
brk(0xb811a000) = 0xb811a000
getppid()   = 17661
stat64("/home/erlehmann", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64(".", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open("/usr/bin/chromium", O_RDONLY) = 3
fcntl64(3, F_DUPFD, 10) = 10
close(3)= 0
fcntl64(10, F_SETFD, FD_CLOEXEC)= 0
rt_sigaction(SIGINT, NULL, {SIG_DFL, [], 0}, 8) = 0
rt_sigaction(SIGINT, {0xb7766bc0, ~[RTMIN RT_1], 0}, NULL, 8) = 0
rt_sigaction(SIGQUIT, NULL, {SIG_DFL, [], 0}, 8) = 0
rt_sigaction(SIGQUIT, {SIG_DFL, ~[RTMIN RT_1], 0}, NULL, 

Bug#817586: Info received (most: diff for NMU version 5.0.0a-2.4)

[Wookey]

On 2016-07-22 01:12 +, Debian Bug Tracking System wrote:

Herman and I tried to re-arrange things so that my more thorough
upload ended up in the archive, after 10 days, but I screwed up and
accidentally did an immediate upload.

Hopefully everyone is fine with this and no harm done. If the
maintainer wants any changes I'm happy to re-upload.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: Digital signature

Processed: merging 830793 830944

[Debian Bug Tracking System]

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

> merge 830793 830944
Bug #830793 [ruby-validate-url] en.yml should be installed in /usr/share
Bug #830793 [ruby-validate-url] en.yml should be installed in /usr/share
Marked as found in versions ruby-validate-url/1.0.2-1.
Bug #830944 [ruby-validate-url] ruby-validate-url: 
/usr/lib/ruby/vendor_ruby/locale/en.yml also in ruby-validate-email
Merged 830793 830944
> thanks
Stopping processing here.

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

Bug#832103: docker.io: Can't run images after upgrading to 1.11.2~ds1-6

[Tianon Gravi]

On 22 July 2016 at 03:40, Sandro Knauß  wrote:
> downgrading to 1.11.2~ds1-5 and restart the daemon fixed the problem:

Did you try restarting the daemon before you downgraded? (and if not,
would you be willing to upgrade again and give it a shot?)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#832119: unicorn: start script won't start if config file exists!

[Jörg-Volker Peetz]

Package: unicorn
Version: 5.0.1-1
Severity: grave

Dear Maintainer,

there seems to be an error in /etc/init.d/unicorn which forbids to start
unicorn if a config file exists (and not if it *not* exist).

In lines 42--44 it reads

  if [ -s $CONFIG_RB ]; then
exit_with_message "Unicorn config.rb is missing (see /etc/default/unicorn)."
  fi

Shouldn't that be

  if [ ! -s $CONFIG_RB ]; then

in line 42 or something like that?

Regards,
jvp.


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

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

Versions of packages unicorn depends on:
ii  init-system-helpers  1.39
ii  libc62.23-1
ii  libgmp10 2:6.1.1+dfsg-1
ii  libruby2.3   2.3.1-3
ii  ruby 1:2.3.0+4
ii  ruby-kgio2.10.0-1+b2
ii  ruby-rack1.6.4-4
ii  ruby-raindrops   0.16.0-1+b1

unicorn recommends no packages.

unicorn suggests no packages.

-- Configuration Files:
/etc/default/unicorn changed:
TIMEOUT=60
CONFIG_RB="/usr/share/redmine/config/unicorn.conf.rb"
PID=/run/unicorn.pid
UNICORN_OPTS="-E production"


-- no debconf information

Bug#832118: ruby-puppet-forge: FTBFS: psych.rb:471:in `initialize': No such file or directory @ rb_sysopen - /usr/lib/ruby/locales/config.yaml (Errno::ENOENT)

[Chris Lamb]

Source: ruby-puppet-forge
Version: 2.2.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,

ruby-puppet-forge fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../ruby-minitest_5.9.0-1_all.deb ...
  Unpacking ruby-minitest (5.9.0-1) ...
  Selecting previously unselected package ruby-net-telnet.
  Preparing to unpack .../ruby-net-telnet_0.1.1-2_all.deb ...
  Unpacking ruby-net-telnet (0.1.1-2) ...
  Selecting previously unselected package ruby-power-assert.
  Preparing to unpack .../ruby-power-assert_0.3.0-1_all.deb ...
  Unpacking ruby-power-assert (0.3.0-1) ...
  Selecting previously unselected package ruby-test-unit.
  Preparing to unpack .../ruby-test-unit_3.1.7-2_all.deb ...
  Unpacking ruby-test-unit (3.1.7-2) ...
  Selecting previously unselected package libyaml-0-2:amd64.
  Preparing to unpack .../libyaml-0-2_0.1.6-3_amd64.deb ...
  Unpacking libyaml-0-2:amd64 (0.1.6-3) ...
  Selecting previously unselected package libruby2.3:amd64.
  Preparing to unpack .../libruby2.3_2.3.1-5_amd64.deb ...
  Unpacking libruby2.3:amd64 (2.3.1-5) ...
  Selecting previously unselected package ruby2.3.
  Preparing to unpack .../ruby2.3_2.3.1-5_amd64.deb ...
  Unpacking ruby2.3 (2.3.1-5) ...
  Selecting previously unselected package ruby.
  Preparing to unpack .../ruby_1%3a2.3.0+4_amd64.deb ...
  Unpacking ruby (1:2.3.0+4) ...
  Selecting previously unselected package rake.
  Preparing to unpack .../archives/rake_10.5.0-2_all.deb ...
  Unpacking rake (10.5.0-2) ...
  Selecting previously unselected package gem2deb-test-runner.
  Preparing to unpack .../gem2deb-test-runner_0.31_amd64.deb ...
  Unpacking gem2deb-test-runner (0.31) ...
  Selecting previously unselected package libgmpxx4ldbl:amd64.
  Preparing to unpack .../libgmpxx4ldbl_2%3a6.1.1+dfsg-1_amd64.deb ...
  Unpacking libgmpxx4ldbl:amd64 (2:6.1.1+dfsg-1) ...
  Selecting previously unselected package libgmp-dev:amd64.
  Preparing to unpack .../libgmp-dev_2%3a6.1.1+dfsg-1_amd64.deb ...
  Unpacking libgmp-dev:amd64 (2:6.1.1+dfsg-1) ...
  Selecting previously unselected package ruby2.3-dev:amd64.
  Preparing to unpack .../ruby2.3-dev_2.3.1-5_amd64.deb ...
  Unpacking ruby2.3-dev:amd64 (2.3.1-5) ...
  Selecting previously unselected package ruby-all-dev:amd64.
  Preparing to unpack .../ruby-all-dev_1%3a2.3.0+4_amd64.deb ...
  Unpacking ruby-all-dev:amd64 (1:2.3.0+4) ...
  Selecting previously unselected package ruby-setup.
  Preparing to unpack .../ruby-setup_3.4.1-9_all.deb ...
  Unpacking ruby-setup (3.4.1-9) ...
  Selecting previously unselected package gem2deb.
  Preparing to unpack .../gem2deb_0.31_amd64.deb ...
  Unpacking gem2deb (0.31) ...
  Selecting previously unselected package ruby-multipart-post.
  Preparing to unpack .../ruby-multipart-post_1.2.0-2_all.deb ...
  Unpacking ruby-multipart-post (1.2.0-2) ...
  Selecting previously unselected package ruby-faraday.
  Preparing to unpack .../ruby-faraday_0.9.2-3_all.deb ...
  Unpacking ruby-faraday (0.9.2-3) ...
  Selecting previously unselected package ruby-faraday-middleware.
  Preparing to unpack .../ruby-faraday-middleware_0.10.0-1_all.deb ...
  Unpacking ruby-faraday-middleware (0.10.0-1) ...
  Selecting previously unselected package ruby-fast-gettext.
  Preparing to unpack .../ruby-fast-gettext_1.0.0-1_all.deb ...
  Unpacking ruby-fast-gettext (1.0.0-1) ...
  Selecting previously unselected package ruby-locale.
  Preparing to unpack .../ruby-locale_2.1.2-1_all.deb ...
  Unpacking ruby-locale (2.1.2-1) ...
  Selecting previously unselected package ruby-text.
  Preparing to unpack .../ruby-text_1.3.0-1_all.deb ...
  Unpacking ruby-text (1.3.0-1) ...
  Selecting previously unselected package ruby-gettext.
  Preparing to unpack .../ruby-gettext_3.1.7-1_all.deb ...
  Unpacking ruby-gettext (3.1.7-1) ...
  Selecting previously unselected package ruby-gettext-setup.
  Preparing to unpack .../ruby-gettext-setup_0.3-1_all.deb ...
  Unpacking ruby-gettext-setup (0.3-1) ...
  Selecting previously unselected package ruby-minitar.
  Preparing to unpack .../ruby-minitar_0.5.4-3_all.deb ...
  Unpacking ruby-minitar (0.5.4-3) ...
  Selecting previously unselected package ruby-diff-lcs.
  Preparing to unpack .../ruby-diff-lcs_1.2.5-2_all.deb ...
  Unpacking ruby-diff-lcs (1.2.5-2) ...
  Selecting previously unselected package ruby-rspec-support.
  Preparing to unpack .../ruby-rspec-support_3.4.0c3e0m1s1-1_all.deb ...
  Unpacking ruby-rspec-support (3.4.0c3e0m1s1-1) ...
  Selecting previously unselected package ruby-rspec-expectations.
  Preparing to unpack .../ruby-rspec-expectations_3.4.0c3e0m1s1-1_all.deb ...
  Unpacking ruby-rspec-expectations (3.4.0c3e0m1s1-1) ...
  Selecting previously unselected package ruby-rspec-mocks.
  Preparing to unpack .../ruby-rspec-mocks_3.4.0c3e0m1s1-1_all.deb ...
  Unpacking ruby-rspec-mocks 

Bug#817586: marked as done (most: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 13:49:19 +
with message-id 
and subject line Bug#817586: fixed in most 5.0.0a-2.4
has caused the Debian Bug report #817586,
regarding most: 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.)


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

Hi,

The package most 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: most
Source-Version: 5.0.0a-2.4

We believe that the bug you reported is fixed in the latest version of
most, 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.
Wookey  (supplier of updated most 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: Fri, 22 Jul 2016 01:26:53 +0100
Source: most
Binary: most
Architecture: source amd64
Version: 5.0.0a-2.4
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Mako Hill 
Changed-By: Wookey 
Description:
 most   - Pager program similar to more and less
Closes: 817586
Changes:
 most (5.0.0a-2.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bump debhelper compat to 9 (Closes: #817586)
   * Update to policy 3.9.8 (use dpkg-buildflags,
 add build-arch/build-indep targets)
   * Fix lintian issues (above plus missing misc:depends)
   * Don't force $CC=gcc (breaks cross-building)
   * Use dh_autoreconf to support new architectures
   * Reinstate quiltification from 5.0.0a-2.2 NMU
Checksums-Sha1:
 e990bfe2d60580a0dd5cda6af91cd72fc8bcc7e5 1683 most_5.0.0a-2.4.dsc
 fc78ebdc0cc6729ad46b8cd925d52bb9b4e1e14e 9288 most_5.0.0a-2.4.debian.tar.xz
 4db0e2491db352cee5eb227ef0b1dea27dccaf6e 54382 most-dbgsym_5.0.0a-2.4_amd64.deb
 6c4e836e0570a412d7d0bad2b327cdd5a8667730 46894 most_5.0.0a-2.4_amd64.deb
Checksums-Sha256:
 a9ddaa0a4076a93f032083a80c467a4ce30ef83e218c79972915c45c2d5fd813 1683 
most_5.0.0a-2.4.dsc
 1666840222187b61ff008b33048429a8f5da65e2210933315ded6c6c94aadeef 9288 
most_5.0.0a-2.4.debian.tar.xz
 a28e363a5bc3713b8b452d871c423e93336bcdc4738001021f995e3a093c0ad6 54382 
most-dbgsym_5.0.0a-2.4_amd64.deb
 0fb4bb3a2fbfe18796bcc127c0462ee87fc75e4c903a827f77e093976f4ff3b7 46894 
most_5.0.0a-2.4_amd64.deb
Files:
 87fa497416436dd85d66cfee8ee238dc 1683 text optional most_5.0.0a-2.4.dsc
 34fea6338075541e4d1f3161a026ad1e 9288 text optional 
most_5.0.0a-2.4.debian.tar.xz
 0a290df9765f2a12a73183875f1862cf 54382 debug extra 
most-dbgsym_5.0.0a-2.4_amd64.deb
 02d0f7158056a1bbf90a3a9e2c863e4e 46894 text optional most_5.0.0a-2.4_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXkXLYAAoJEPuGMlGob55H4H0P/iRCYVjP4NNK+POl8gGAb8KY
hnCeXbCWB+04A3x//XvQTNegnLnKifp/xnTtvnnyTFOI9/+lM00S/jiC/nm+8ow2
ON/mWOIMFAh85uqyRCmcYtPkbU/bXymbZuV9AE//0Au3r+0L7+fwhxzCGmjXYwUN
ZJMuvpTRv+PD1uxzPX8qC0dn7sBMd7X/rPcbYvg9vl8dpbPhoVw3Tz6WqXoWDH+B
SB1rnZKgeHBYChhdU1UOCXSaPMdqhwTn06SQSVCfL/hLigV77g+U6n10mZDiwtzR
M5QdwjWmjZSCoqWkDKdy17FpR4MoOuHQ9Q4pFt5PQx/6RMiSuvjjraKe08YFwfdl
0VztfmNJCyO7FbfW5qrjIs3RMNcG26MzK9xb6Dtm0TcEqzwGp3wcIhGa4JbLLMUd
DASf+4PtIYZEqh+jW8Zk7ItiTuEF1iPqLDw6HZ+tkE4b3E3rTM2qiZGPHWcO4n7T
MiGJNYeGVxaRGOymeREqGiEGenVW9gwJsurGn3NSXCLP6e5h+dT+lwHD98gsJhjF
cajql++5R6lrLx+eVY3FftDmRm+o40xtLrL0YvJ3ukwplz3WC7LpkQHBuskbKGcD
iWrvXV0rXKMiNZCpvFtdVoCp9dfq0WE907WM85XBPfNZvoEDV9ZAZSdWgCk39WAJ
E2sGkErLi8+ikDoPsV9D
=cD0u
-END PGP SIGNATURE End Message ---

Bug#811866: marked as done (hyphy: FTBFS with GCC 6: no matching function for call to)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 13:49:12 +
with message-id 
and subject line Bug#811866: fixed in hyphy 2.2.6+dfsg-4
has caused the Debian Bug report #811866,
regarding hyphy: FTBFS with GCC 6: no matching function for call to
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.)


-- 
811866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hyphy
Version: 2.2.6+dfsg-3
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
...
> [ 35%] Building CXX object CMakeFiles/HYPHYGTK.dir/src/gui/HYModelWindow.cpp.o
> /usr/bin/c++   -DGDK_PIXBUF_ENABLE_BACKEND 
> -D_HYPHY_LIBDIRECTORY_=\"/usr/lib/hyphy\" -D_SLKP_LFENGINE_REWRITE_ 
> -D_SLKP_USE_SSE_INTRINSICS -D__AFYP_REWRITE_BGM__ -D__HYPHYCURL__ 
> -D__HYPHY_64__ -D__HYPHY_GTK__ -D__UNIX__ 
> -I/<>/hyphy-2.2.6+dfsg/src/core/include 
> -I/<>/hyphy-2.2.6+dfsg/src/lib/Link 
> -I/<>/hyphy-2.2.6+dfsg/src/new/include 
> -I/<>/hyphy-2.2.6+dfsg/src/gui/include 
> -I/<>/hyphy-2.2.6+dfsg/src/gui/include/Components 
> -I/<>/hyphy-2.2.6+dfsg/src/gui/include/WindowClasses 
> -I/<>/hyphy-2.2.6+dfsg/contrib/gtest-1.7.0/include 
> -I/<>/hyphy-2.2.6+dfsg/tests/gtests -I/usr/lib/openmpi/include 
> -I/usr/lib/openmpi/include/openmpi -I/usr/include/gtk-2.0 
> -I/usr/include/freetype2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/atk-1.0 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/<>/hyphy-2.2
> .6+dfsg/src/gui/gtk/include 
> -I/<>/hyphy-2.2.6+dfsg/src/gui/gtk/include/Components 
> -I/Developer/Headers/FlatCarbon  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-g -fsigned-char 
> -O3 -msse3   -o CMakeFiles/HYPHYGTK.dir/src/gui/HYModelWindow.cpp.o -c 
> /<>/hyphy-2.2.6+dfsg/src/gui/HYModelWindow.cpp
> /<>/hyphy-2.2.6+dfsg/src/gui/HYModelWindow.cpp: In member function 
> 'virtual bool _HYModelWindow::ProcessEvent(_HYEvent*)':
> /<>/hyphy-2.2.6+dfsg/src/gui/HYModelWindow.cpp:860:40: error: no 
> matching function for call to '_Formula::_Formula(_String&, NULL, bool)'
>  _Formula f (cText,nil,false);
> ^
> 
> In file included from 
> /<>/hyphy-2.2.6+dfsg/src/core/include/parser.h:54:0,
>  from 
> /<>/hyphy-2.2.6+dfsg/src/core/include/batchlan.h:44,
>  from 
> /<>/hyphy-2.2.6+dfsg/src/gui/include/Components/HYTableComponent.h:13,
>  from 
> /<>/hyphy-2.2.6+dfsg/src/gui/include/WindowClasses/HYModelWindow.h:13,
>  from 
> /<>/hyphy-2.2.6+dfsg/src/gui/HYModelWindow.cpp:41:
> /<>/hyphy-2.2.6+dfsg/src/core/include/formula.h:88:5: note: 
> candidate: _Formula::_Formula(_PMathObj, bool)
>  _Formula (_PMathObj, bool isAVar = false);
>  ^~~~
> 
> /<>/hyphy-2.2.6+dfsg/src/core/include/formula.h:88:5: note:   
> candidate expects 2 arguments, 3 provided
> /<>/hyphy-2.2.6+dfsg/src/core/include/formula.h:87:5: note: 
> candidate: _Formula::_Formula(_String&, _VariableContainer*, _String*)
>  _Formula (_String&,_VariableContainer* theParent=nil,_String* 
> errorString = nil);
>  ^~~~
> 
> /<>/hyphy-2.2.6+dfsg/src/core/include/formula.h:87:5: note:   no 
> known conversion for argument 3 from 'bool' to '_String*'
> /<>/hyphy-2.2.6+dfsg/src/core/include/formula.h:86:5: note: 
> candidate: _Formula::_Formula()
>  _Formula (void);
>  ^~~~
> 
> /<>/hyphy-2.2.6+dfsg/src/core/include/formula.h:86:5: note:   
> candidate expects 0 arguments, 3 provided
> /<>/hyphy-2.2.6+dfsg/src/core/include/formula.h:79:9: note: 
> candidate: _Formula::_Formula(const _Formula&)
>  class   _Formula   // a computational formula
>  ^~~~
> 
> /<>/hyphy-2.2.6+dfsg/src/core/include/formula.h:79:9: note:   
> candidate expects 1 argument, 3 provided
> CMakeFiles/HYPHYGTK.dir/build.make:785: recipe for target 
> 

Bug#789739: libdevel-ebug-perl: FTBFS in sid: test failures

[Salvatore Bonaccorso]

Hi,

On Sun, Sep 27, 2015 at 09:47:41PM +0300, Niko Tyni wrote:
> Control: retitle -1 libdevel-ebug-perl: FTBFS in sid: test failures
> 
> On Tue, Aug 11, 2015 at 08:48:20PM +0200, gregor herrmann wrote:
> > On Wed, 24 Jun 2015 00:59:37 +0100, Dominic Hargreaves wrote:
> > 
> > > Source: libdevel-ebug-perl
> > > Version: 0.56-1
> > > Severity: serious
> > > Justification: FTBFS
> > > 
> > > This package FTBFS in a clean sid sbuild setup:
> 
> > https://reproducible.debian.net/rbuild/unstable/amd64/libdevel-ebug-perl_0.56-1.rbuild.log
> > 
> > JFTR:
> > At the moment it fails for me with:
> 
> > Test Summary Report
> > ---
> > t/stack.t  (Wstat: 1792 Tests: 29 Failed: 7)
> >   Failed tests:  12, 14-15, 19, 27-29
> >   Non-zero exit status: 7
> 
> This stack.t failure is a different issue from the original ebug.t one. It
> was probably caused by libdevel-stacktrace-perl 2.-1. AFAICS the
> test is just hardcoding Devel::StackTrace output so it would probably
> be enough to just update it to correspond to the new version.  This is
> https://rt.cpan.org/Ticket/Display.html?id=100615 FWIW.
> 
> Not sure if it's worth having two bugs, retitling this for now.
> The silence upstream suggests this module might be abandoned?

Any objection inf we finally remove this package from the archive?

Regards,
Salvatore

Processed: Re: Bug#805002: libvirt-client: "virsh attach-disk" fails with AppArmor enabled

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 apparmor
Bug #805002 [libvirt-clients] libvirt-client: "virsh attach-disk" fails with 
AppArmor enabled 
Bug reassigned from package 'libvirt-clients' to 'apparmor'.
No longer marked as found in versions libvirt/1.2.21-1.
Ignoring request to alter fixed versions of bug #805002 to the same values 
previously set
> affects -1 libvirt-daemon
Bug #805002 [apparmor] libvirt-client: "virsh attach-disk" fails with AppArmor 
enabled 
Added indication that 805002 affects libvirt-daemon

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

Processed: Re: isympy start fails: No module named sympy.interactive

[Debian Bug Tracking System]

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

> severity 827740 serious
Bug #827740 [isympy] isympy start fails: No module named sympy.interactive
Severity set to 'serious' from 'important'
> tags 827740 + patch
Bug #827740 [isympy] isympy start fails: No module named sympy.interactive
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#805002: libvirt-client: "virsh attach-disk" fails with AppArmor enabled

[Guido Günther]

Control: reassign -1 apparmor
Control: affects -1 libvirt-daemon

Dear apparmor maintainers,

On Fri, Nov 13, 2015 at 09:32:15AM +, Carlo Rengo wrote:
> Package: libvirt-client
> Version: 1.2.21-1
> Severity: serious
> 
> Dear Maintainer,
> 
> Running “virsh attach-disk   ” with AppArmor enabled 
> and 
> the domain confined in enforce mode gives this error:
> 
> root@host:~# virsh attach-disk debian8 
> /var/lib/libvirt/images/disk_to_attach.img vdd
> error: Failed to attach disk
> error: internal error: unable to execute QEMU command 'device_add': Property 
> 'virtio-blk-device.drive' can't find value 'drive-virtio-disk3'
> 
> From journal:
> 
> audit: type=1400 audit(1447406591.802:2015): apparmor="STATUS" 
> operation="profile_replace" 
> name="libvirt-73a13868-fbfd-4dce-bbf1-effde396bb12" pid=57268 
> comm="apparmor_parser"
> audit: type=1400 audit(1447406591.862:2016): apparmor="STATUS" 
> operation="profile_replace" name="qemu_bridge_helper" pid=57268 
> comm="apparmor_parser"
> audit: type=1400 audit(1447406591.892:2017): apparmor="DENIED" 
> operation="open" profile="libvirt-73a13868-fbfd-4dce-bbf1-effde396bb12" 
> name="/var/lib/libvirt/images/to_attach.img" pid=56392 comm="kvm" 
> requested_mask="r" denied_mask="r" fsuid=0 ouid=0
> audit: type=1400 audit(1447406591.952:2018): apparmor="DENIED" 
> operation="open" profile="libvirt-73a13868-fbfd-4dce-bbf1-effde396bb12" 
> name="/var/lib/libvirt/images/to_attach.img" pid=56392 comm="kvm" 
> requested_mask="r" denied_mask="r" fsuid=0 ouid=0
> audit: type=1400 audit(1447406592.002:2019): apparmor="DENIED" 
> operation="open" profile="libvirt-73a13868-fbfd-4dce-bbf1-effde396bb12" 
> name="/var/lib/libvirt/images/to_attach.img" pid=56392 comm="kvm" 
> requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0
> audit: type=1400 audit(1447406592.262:2020): apparmor="STATUS" 
> operation="profile_replace" 
> name="libvirt-73a13868-fbfd-4dce-bbf1-effde396bb12" pid=57270 
> comm="apparmor_parser"
> audit: type=1400 audit(1447406592.342:2021): apparmor="STATUS" 
> operation="profile_replace" name="qemu_bridge_helper" pid=57270 
> comm=“apparmor_parser"
> 
> When putting the domain in complain/disabled mode, the error keeps showing up 
> until 
> the domain is destroyed/recreated or saved/restored.

I can confirm this (see below).

> 
> This errors appears with libvirt from debian stable, debian testing and from 
> a compiled 
> version of the source. Ubuntu 15.10 is not affected by this bug.

I think this issue is not within in libvirt but related to apparmor not
correctly refreshing the profiles of running processes. As outlined in
#826218 I can reproduce this without having virt-aa-helper in the game
(by changing the profile on disk and reloading it into the kernel via
apparmor_parser -r). Can be reproduced via:

   echo "/var/lib/libvirt/images/powerpc.img rw," >> 
/etc/apparmor.d/libvirt/libvirt-a9287b6e-ca06-42fe-b1a2-06830752843a.files
   chmod u+rw /var/lib/libvirt/images/powerpc.img
   chown libvirt-qemu: /var/lib/libvirt/images/powerpc.img
   /sbin/apparmor_parser -r  
/etc/apparmor.d/libvirt/libvirt-a9287b6e-ca06-42fe-b1a2-06830752843a
   virsh qemu-monitor-command wheezy --pretty --cmd 
'{"execute":"human-monitor-command","arguments":{"command-line":"drive_add 
dummy file=/var/li

I have also observed that aa-{disable,complain} dont affect running VMs
but this might just an omission in the documentation.

I'm happy to help debug this further but would be glad to see if I'm
going into the right direction.

Cheers,
 -- Guido

Processed: tagging 812022

[Debian Bug Tracking System]

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

> tags 812022 + patch
Bug #812022 [traverso] traverso: FTBFS with GCC 6: flexible array member...
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#812022: traverso: FTBFS with GCC 6: flexible array member...

[intrigeri]

Hi,

The package has been removed from testing even though a patch was
proposed 6 months ago, so I'm wondering: what's the status here?

Cheers,
--
intrigeri

Bug#831182: Being worked on

[Lisandro Damián Nicanor Pérez Meyer]

This bug is being worked on with upstream.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#811754: ibus-unikey: FTBFS with GCC 6: narrowing conversion

[intrigeri]

Hi Lê Quốc Tuấn,

this package was removed from testing a week ago. I would find it sad
if we have to stop shipping it in Tails once we're based on Stretch.
Do you have any plans to fix this RC bug?

Cheers,
--
intrigeri

Processed: singular: FTBFS with GCC 6: segfault

[Debian Bug Tracking System]

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

> forwarded 831072 https://github.com/Singular/Sources/issues/772
Bug #831072 [src:singular] singular: FTBFS with GCC 6: segfault
Set Bug forwarded-to-address to 
'https://github.com/Singular/Sources/issues/772'.
> thanks
Stopping processing here.

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

Bug#831210: marked as pending

[Fabian Wolff]

tag 831210 pending
thanks

Hello,

Bug #831210 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=collab-maint/squirrel3.git;a=commitdiff;h=d711981

---
commit d7119816ccf21340a6f2b659409b36996ae0afcc
Author: Fabian Wolff 
Date:   Fri Jul 22 13:33:16 2016 +0200

Delete symbols file to fix a FTBFS with GCC 6

diff --git a/debian/changelog b/debian/changelog
index 0799887..dab0e6b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+squirrel3 (3.1-4) UNRELEASED; urgency=medium
+
+  * Delete libsquirrel3-0.symbols.amd64 (Closes: #831210).
+
+ -- Fabian Wolff   Fri, 22 Jul 2016 13:12:57 +0200
+
 squirrel3 (3.1-3) unstable; urgency=medium
 
   * Add Vcs-Git and Vcs-Browser fields to debian/control.

Processed: Bug#831210 marked as pending

[Debian Bug Tracking System]

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

> tag 831210 pending
Bug #831210 [src:squirrel3] squirrel3: FTBFS with GCC 6: dh_makeshlibs: failing 
due to earlier errors
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#832116: edgar: Source missing for some GPL licensed assets

[Guus Sliepen]

Source: edgar
Severity: serious
Justification: source missing for GPL licensed assets

According to debian/copyright, the edgar-data package contains a number
of songs which are licensed under the GPL-3+. However, only the final
rendered music is present in the form of a .ogg file.

> Files:
>   music/Battle?in?the?winter.ogg
>   music/Devilish?design.ogg
>   music/A?wintertale_0.ogg
>   music/Medicine.ogg
> Copyright: Copyright (c) Johan Brodd
> Comment: http://opengameart.org/users/jobromedia
> License: GPL-3+

Upon checking OpenGameArt, I found out that "Battle in the winter" and "A
winter tale" are dual-licensed, and available under the CC-BY 3.0 and
CC-BY-SA 3.0 licenses respectively, so it should be a simple matter of
updating the copyright notice here. However, "Devilish design" is only
available under GPL 3.0. As such, I believe that unless the source can
be found or Johan Brodd can be contacted and asked if the license could
be changed, this song should be removed from the source package.

Also, Medicine.ogg is, according to OpenGameArt.org, created by
Alexander Zhelanov, and is licensed only under CC-BY 3.0.


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

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

-- no debconf information

Processed: singular: FTBFS with GCC 6: segfault

[Debian Bug Tracking System]

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

> retitle 831072 singular: FTBFS with GCC 6: segfault
Bug #831072 [src:singular] singular: FTBFS with GCC 6: help2man: can't get 
`--help' info from /«BUILDDIR»/singular-4.0.3-p1+ds/Singular/Singular
Changed Bug title to 'singular: FTBFS with GCC 6: segfault' from 'singular: 
FTBFS with GCC 6: help2man: can't get `--help' info from 
/«BUILDDIR»/singular-4.0.3-p1+ds/Singular/Singular'.
> thanks
Stopping processing here.

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

Bug#831072: singular: FTBFS with GCC 6: segfault

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

retitle 831072 singular: FTBFS with GCC 6: segfault
thanks


Hello Folks,

it appears that it is segfault bug.

I could reproduced it the vanilla source ball by
building with GCC compilers (6.1.1) and by forcing shared library
at configure time:

$ ./configure --enable-shared --disable-static

Then, after processing `make', ./Singular/Singular emits a segfault.

The GDB prints:

 GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./Singular/Singular...done.
[New LWP 7786]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./Singular/Singular'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fa9769a810d in idrec::get(char const*, int) () from 
/home/calculus/singular/unpacked/singular-4.0.3-11/Singular/.libs/libSingular-4.0.3.so

Exporting dpkg-buildflags FLAGS, shows that the issue is emiited from line 104 
of Singular/ipid.cc :

l=IDLEV(h);

where `idhdl h = this;' (line 94) and IDLEV is the macro  `((a)->lev)' defined 
in Singular/ipid.h .

Thanks,
Jerome



- -- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
-BEGIN PGP SIGNATURE-

iQQcBAEBCgAGBQJXkgy7AAoJED+SGaZ/NsaLfa4gAKkOJfSVdtNLv3WUO5mfDFr3
/iaky+2BxHMEXt/s5/hURe0/6JbdP5I/Y2dIsuHXObTp8xt0WKIIVgIhF7BuJ53m
vU4bOv4F/ByncstN+6fekXTTwI0xYi2EZwmhPCdAcz5Dn4Rx4gE7ixPynDOl5iJZ
6CWOBdlH+Cq6nqqHZun6cihol6FjKUiDWtRyvnuGqEopv05aEbtH3MZFECAHxi3j
himoj9VOgGDOYZ2IW/Ro0mAPkZyay5KcBAY0NGen4kry0OlYV6OmG+N5ogV6IKFh
o2ICpF7m5mbiagLF2XcjK03oZWLcCeS/EzG0YIIL1fd/Y7dJg6KxHvAJwSD04mW+
c8AGmqTeeeWxv7JnvU+MtixiVVjQPwkSs53K5EOMzJVT/6gtH/wUWTN/AtXn20te
cbo8KXht/K1x+oFuq/ELpRWK8yvuzCJ9WT1vvkxE1bTm/8D8ABgmyDHIXQ6siUWk
zFQtiWV9aRLpQjO4WWMRFx/UW3cg4uG0lnvirbxBK9nCKk6BrV5X5lh+98/bPvnd
F+Ab51Rf+s50TLEN6Z2ju3yD5RCGPrBIY3MckiG8U2sglKfbfDwMxu+EAqWjESsb
dYiby2h4FWWODUOK8N1JzLc0aMS9Gc6vX+IVLilCVKxfAzvCXJ5SZ54ZvUsTfZg/
oOGWcM0EkEsZGAgSOHonLOa+AbvdwOFfPAjm63u+MXGE3537Gteo9U6MmLfF8Yc6
HYpopsYMvxd4b57tRETc+d4KPTLqR/jjl4ObtxQ79nFjR1CnEIRuI+6P7593aJAw
Dlo8nhzgIuitwysfd+vKbmPCjXk47NtN/cVi7qHfd93vYlUFaR+7Ey3KVqA4Emut
W4lscFaR7PVjRYW+HPzR5zmUdB++ZIm21awlbCCgzqYq8MJb785jxdogbf6ekpC/
FiS1kk0PyWWQbFu7sOEkjwCtTfvr4+5XvIeDsh5U8oJJV8BgfDvMOfdi9lIKAg7P
13KCdLtqGn7XxaMvWHjVcpxfmd6V8MuSAfWdf/ywguIiEN0LoxAM7T4MzPufOLVs
P1RhQioURYGVc73QD6lH0Q5y6uU4t2PjLr7CNRNIfhuD2HBXgmtkQAlr9luFbqXx
TStcMNIr/yWkMz1QWNW8QJlWq3oRL34t7ipaCmkG/eQkXOOrLxYNFAoezNyB6FPd
M2AFsHV9PDxUqkSsJZ9ciw6P1ZS7HUh3iP4W+DGZzGQh1NUVsVMHqXi1pqKVksyr
gdXCF6Rucp1+jVNew/ncWw7sxZAXZl3EiNT9/uxvJvZ6ho/pl/07TXGXZsp1jFqM
m+OkuG7Y4H2yAUUYaxuR6M8KNQ7CWFRjEWvTBbJEbElIeBOUu17qaoRDsMpMZCU=
=z9wv
-END PGP SIGNATURE-

Bug#817586: most: diff for NMU version 5.0.0a-2.4

[gregor herrmann]

On Fri, 22 Jul 2016 03:36:06 +0200, gregor herrmann wrote:

> > I'd love to see your NMU with all those fixes get into the archive
> > (compared to my minimal "just bump debhelper compat level"), so I've
> > reschedule my NMU to DELAYED/12 (as a hopefully not needed fallback).
> 
> Or did I reschedule your NMU? Or was your NMU rejected and I
> rescheduled mine? Or something else?
> 
> https://ftp-master.debian.org/deferred/ currently shows my .changes
> -- and nothing more from me or you :/

It's back, and it seems to be my variant ...
I guess I should cancel it so that you can upload your version?


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Leonard Cohen: So long, Marianne


signature.asc
Description: Digital Signature

Bug#831181: oding: ftbfs with gcc-6

[Gianfranco Costamagna]

new debdiff attached.

G.
diff -Nru odin-2.0.2/debian/changelog odin-2.0.2/debian/changelog
--- odin-2.0.2/debian/changelog 2016-07-16 09:33:28.0 +0200
+++ odin-2.0.2/debian/changelog 2016-07-22 13:58:53.0 +0200
@@ -1,3 +1,10 @@
+odin (2.0.2-0.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Revert a little bit of the previous gcc-6-fix2.
+
+ -- Gianfranco Costamagna   Fri, 22 Jul 2016 
13:58:23 +0200
+
 odin (2.0.2-0.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru odin-2.0.2/debian/patches/gcc-6-fix2.patch 
odin-2.0.2/debian/patches/gcc-6-fix2.patch
--- odin-2.0.2/debian/patches/gcc-6-fix2.patch  2016-07-16 09:52:15.0 
+0200
+++ odin-2.0.2/debian/patches/gcc-6-fix2.patch  2016-07-22 13:58:22.0 
+0200
@@ -2,25 +2,6 @@
 
 Author: Gianfranco Costamagna 
 
 odin-2.0.2.orig/odinseq/seqgradspiral.cpp
-+++ odin-2.0.2/odinseq/seqgradspiral.cpp
-@@ -27,12 +27,12 @@ float SeqGradSpiral::readout_npts() cons
- const kspace_coord& tds=traj_cache->calculate(s);
- if(i) {
-   
deltaKtangential=STD_max(double(deltaKtangential),norm(tds.kx-last_kx,tds.ky-last_ky));
--  max_grad_diff=STD_max(double(max_grad_diff),fabs(tds.Gx-last_Gx));
--  max_grad_diff=STD_max(double(max_grad_diff),fabs(tds.Gy-last_Gy));
-+  max_grad_diff=STD_max(max_grad_diff,fabs(tds.Gx-last_Gx));
-+  max_grad_diff=STD_max(max_grad_diff,fabs(tds.Gy-last_Gy));
- }
- 
--max_grad_magn=STD_max(double(max_grad_magn),fabs(tds.Gx));
--max_grad_magn=STD_max(double(max_grad_magn),fabs(tds.Gy));
-+max_grad_magn=STD_max(max_grad_magn,fabs(tds.Gx));
-+max_grad_magn=STD_max(max_grad_magn,fabs(tds.Gy));
- 
- last_kx=tds.kx;
- last_ky=tds.ky;
 --- odin-2.0.2.orig/cmdline-utils/swab.cpp
 +++ odin-2.0.2/cmdline-utils/swab.cpp
 @@ -28,7 +28,7 @@ int main(int argc, char* argv[]) {


signature.asc
Description: OpenPGP digital signature

Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade

[Sebastian Dröge]

On Fri, 22 Jul 2016 13:27:09 +0300 Faidon Liambotis  wrote:

> I still don't exactly understand how H.264/VA-API are related when playing
> just a .wav file, though...

They are not, it's just that the initialization of this GStreamer
plugin (the ffmpeg/libav one) is going through all the codecs that are
provided and remembers what is available.

> #0  0x76fc01c8 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:54
> #1  0x76fc164a in __GI_abort () at abort.c:89
> #2  0x7fffeda6260b in init_context_defaults (s=s@entry=0x70095720, 
> codec=codec@entry=0x7fffee3a8900 )
> at src/libavcodec/options.c:142

All the hardware based ffmpeg codecs should be disabled in gst-libav
though. It of course still shouldn't crash like this, which seems like
a problem in ffmpeg, but I'll fix gst-libav to ignore them all now.

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

Bug#832103: docker.io: Can't run images after upgrading to 1.11.2~ds1-6

[Sandro Knauß]

Package: docker.io
Version: 1.11.2~ds1-6
Severity: grave
Justification: renders package unusable

Hey,

after upgrading from 1.11.2~ds1-5 -> 1.11.2~ds1-6. I can't run any image.
It fails with:

$ docker run -it debian:sid
exec: "/bin/bash": stat /bin/bash: no such file or directory
docker: Error response from daemon: Container command not found or does
not exist..

downgrading to 1.11.2~ds1-5 and restart the daemon fixed the problem:

docker run -it debian:sid
root@686f2edff3f2:/# 

Regards,

sandro

-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
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 docker.io depends on:
ii  adduser  3.115
ii  containerd   0.2.1~ds1-2
ii  init-system-helpers  1.39
ii  iptables 1.6.0-2
ii  libapparmor1 2.10.95-4
ii  libc62.23-2
ii  libdevmapper1.02.1   2:1.02.130-1
ii  libsqlite3-0 3.13.0-1
ii  libsystemd0  230-7
ii  runc 0.1.1+dfsg1-1

Versions of packages docker.io recommends:
ii  ca-certificates  20160104
ii  cgroupfs-mount   1.3
ii  git  1:2.8.1-1
ii  xz-utils 5.1.1alpha+20120614-2.1

Versions of packages docker.io suggests:
pn  aufs-tools   
ii  btrfs-progs  4.5.2-1
ii  debootstrap  1.0.81
pn  lxc  
pn  rinse
pn  zfs-fuse | zfsutils  

-- no debconf information

Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade

[Faidon Liambotis]

On Fri, Jul 22, 2016 at 10:21:05AM +0200, Sebastian Ramacher wrote:
> Unfortunately I am unable to reproduce the issue. Since there are some 
> accounts
> of random crashes when building ffmpeg with tree vectorization enabled, I've
> uploaded 7:3.1.1-3 with vectorization disabled. Could you please check if the
> issue disappears with -3?

I upgraded all ffmpeg packages to 7:3.1.1-3 but I'm still experiencing
crashes.

I then installed libavcodec57-dbgsym, libgstreamer1.0-0-dbg,
gstreamer1.0-libav-dbg and gstreamer1.0-plugins-good-dbg. The full
backtrace is below. The "codec = " seems
relevant, since this is on an Intel Broadwell, which may not be the case
for you. This looks a lot like #831529, doesn't it?

I still don't exactly understand how H.264/VA-API are related when playing
just a .wav file, though... This was with the same gstreamer pipeline,
  gst-launch-1.0 filesrc location=/usr/share/sounds/purple/alert.wav  !
  wavparse ! audioconvert ! fakesink


#0  0x76fc01c8 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:54
#1  0x76fc164a in __GI_abort () at abort.c:89
#2  0x7fffeda6260b in init_context_defaults (s=s@entry=0x70095720, 
codec=codec@entry=0x7fffee3a8900 )
at src/libavcodec/options.c:142
#3  0x7fffeda626d6 in avcodec_alloc_context3 (codec=0x7fffee3a8900 
) at src/libavcodec/options.c:163
#4  0x7fffef360540 in gst_ffmpeg_cfg_install_property 
(klass=0x70095200, base=8) at gstavcfg.c:732
#5  0x7fffef356e53 in gst_ffmpegvidenc_class_init (klass=0x70095200)
at gstavvidenc.c:225
#6  0x7788c22d in g_type_class_ref (pclass=0x70094690, 
node=0x70094500) at 
/build/glib2.0-vjfO_h/glib2.0-2.48.1/./gobject/gtype.c:2241
#7  0x7788c22d in g_type_class_ref (type=type@entry=140737220527360)
at /build/glib2.0-vjfO_h/glib2.0-2.48.1/./gobject/gtype.c:2956
#8  0x77b09da4 in gst_element_register (plugin=plugin@entry=0x69bbf0 
[GstPlugin], name=name@entry=0x7006d110 "avenc_h264_vaapi", 
rank=rank@entry=128, type=type@entry=140737220527360) at gstelementfactory.c:243
#9  0x7fffef3575b3 in gst_ffmpegvidenc_register 
(plugin=plugin@entry=0x69bbf0 [GstPlugin]) at gstavvidenc.c:1009
#10 0x7fffef349e20 in plugin_init (plugin=0x69bbf0 [GstPlugin])
at gstav.c:158
#11 0x77b2b537 in gst_plugin_register_func (plugin=0x69bbf0 
[GstPlugin], desc=0x7fffef578180 , user_data=0x0) at 
gstplugin.c:523
#12 0x77b2d425 in _priv_gst_plugin_load_file_for_registry 
(filename=0x6c2e20 "/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so", 
registry=0x61c150 [GstRegistry], registry@entry=0x0, 
error=error@entry=0x74de7bf0)
at gstplugin.c:826
#13 0x77b2dcea in gst_plugin_load_file (filename=, 
error=error@entry=0x74de7bf0) at gstplugin.c:680
#14 0x77b2e12c in gst_plugin_load_by_name (name=0x6c218d "libav")
at gstplugin.c:1265
#15 0x77b2ea8d in gst_plugin_feature_load 
(feature=feature@entry=0x6e58a0 [GstTypeFindFactory]) at gstpluginfeature.c:111
#16 0x77b547e3 in gst_type_find_factory_call_function (factory=0x6e58a0 
[GstTypeFindFactory], find=0x74de7c90) at gsttypefindfactory.c:210
#17 0x75d89421 in gst_type_find_helper_for_data (obj=obj@entry=0x812070 
[GstWavParse], data=, size=, 
prob=prob@entry=0x74de7db4) at gsttypefindhelper.c:535
#18 0x75d895a4 in gst_type_find_helper_for_buffer 
(obj=obj@entry=0x812070 [GstWavParse], buf=buf@entry=0x70003450, 
prob=prob@entry=0x74de7db4)
at gsttypefindhelper.c:591
#19 0x75b3546a in gst_wavparse_add_src_pad (wav=wav@entry=0x812070 
[GstWavParse], buf=0x70003450) at gstwavparse.c:1908
#20 0x75b35b47 in gst_wavparse_stream_data (wav=wav@entry=0x812070 
[GstWavParse]) at gstwavparse.c:2061
#21 0x75b3bbb1 in gst_wavparse_loop (pad=0x8042a0 [GstPad])
at gstwavparse.c:2202
#22 0x77b4fe71 in gst_task_func (task=0x81c050 [GstTask])
at gsttask.c:332
#23 0x775bc55e in g_thread_pool_thread_proxy (data=) at 
/build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gthreadpool.c:307
#24 0x775bbbc5 in g_thread_proxy (data=0x81a800) at 
/build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gthread.c:780
#25 0x77335464 in start_thread (arg=0x74de8700) at 
pthread_create.c:333
#26 0x7707430d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109


Thanks,
Faidon

Bug#832062: supertuxkart: source for GPL song Boom_boom_boom.ogg missing

[James Cowgill]

On Thu, 2016-07-21 at 22:59 +0200, Guus Sliepen wrote:
> Source: supertuxkart
> Version: 0.9.2-1
> Severity: serious
> Justification: does not include source code of GPL licensed work
> 
> Supertuxkart contains a song called "Boom boom boom" in Ogg Vorbis
> format. According to the credits and debian/copyright, this song is
> created by Matt Thomas, and is licensed under the GNU GPL v3 or
> later. The source of the .ogg file is missing. Although what consists
> the source of media assets can be unclear, I would like to point out
> that there is also a module tracker version of this song, which can
> reasonably considered the source, as it contains the score, the
> samples used and can be editted in any module editor:
> 
> https://modarchive.org/index.php?request=view_by_moduleid=38184

If this is the source then there is a more serious problem. The license
of modarchive modules prohibits modification, so the file would be non-
free for Debian anyway (even if the "source" was included).

https://modarchive.org/index.php?terms-upload
https://modarchive.org/index.php?faq-licensing

James

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

Bug#829409: libhtml-tidy-perl: FTBFS: Failed 7/21 test programs. 8/69 subtests failed.

[Simon McVittie]

On Sun, 03 Jul 2016 at 07:54:05 +0200, Chris Lamb wrote:
> libhtml-tidy-perl fails to build from source in unstable/amd64

I don't think it was necessarily a good idea to forward this upstream:
the build failure is because Debian forked this Perl module to stop using
its author's fork (tidyp) of the underlying C library (tidy), and now we've
also replaced the C library with a different fork (tidy-html5), which is
what's making the tests fail.

The author of HTML::Tidy seems quite likely to respond "if you had
packaged my fork of tidy like the documentation told you to, you wouldn't
have this problem".

However, tidy-html5 seems likely to be better than either tidy or tidyp,
so hopefully the HTML::Tidy author will be somewhat receptive to the idea
of supporting tidy-html5.

Possible patches for the Debian packaging attached, also available from
.

S
>From 2bca8ddf43494c9f6d2b5c516088e0c3cf5682ac Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Fri, 22 Jul 2016 09:45:53 +0100
Subject: [PATCH 1/4] d/p/fix-error-message-in-webtidy: move to end of patch
 series

This is a firmly Debian-specific change that is not suitable for upstream.
---
 debian/changelog  | 5 +
 debian/patches/series | 2 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index 1eeac67..d0db8e1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -10,6 +10,11 @@ libhtml-tidy-perl (1.56-2) UNRELEASED; urgency=medium
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
 
+  [ Simon McVittie ]
+  * d/p/fix-error-message-in-webtidy: move to end of patch series.
+This is a firmly Debian-specific change that is not suitable for
+upstream.
+
  -- gregor herrmann   Thu, 27 Feb 2014 22:36:29 +0100
 
 libhtml-tidy-perl (1.56-1) unstable; urgency=low
diff --git a/debian/patches/series b/debian/patches/series
index 57718d6..4adbeaa 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,3 @@
-fix-error-message-in-webtidy
 remove-tidy_version.patch
 tidy-not-tidyp.patch
+fix-error-message-in-webtidy
-- 
2.8.1

>From 447aa2e692a4276dc51c0e1d958c19f231c54279 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Fri, 22 Jul 2016 09:46:18 +0100
Subject: [PATCH 2/4] d/patches: put all patches in the git style allowed by
 DEP-3, so they can be manipulated with gbp-pq

---
 debian/changelog|  2 +
 debian/patches/fix-error-message-in-webtidy | 13 +++--
 debian/patches/remove-tidy_version.patch| 79 ++---
 debian/patches/tidy-not-tidyp.patch | 19 +--
 4 files changed, 76 insertions(+), 37 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index d0db8e1..2c0a999 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -14,6 +14,8 @@ libhtml-tidy-perl (1.56-2) UNRELEASED; urgency=medium
   * d/p/fix-error-message-in-webtidy: move to end of patch series.
 This is a firmly Debian-specific change that is not suitable for
 upstream.
+  * d/patches: put all patches in the git style allowed by DEP-3,
+so they can be manipulated with gbp-pq
 
  -- gregor herrmann   Thu, 27 Feb 2014 22:36:29 +0100
 
diff --git a/debian/patches/fix-error-message-in-webtidy b/debian/patches/fix-error-message-in-webtidy
index afdfb7c..0efb8d3 100644
--- a/debian/patches/fix-error-message-in-webtidy
+++ b/debian/patches/fix-error-message-in-webtidy
@@ -1,10 +1,17 @@
-Description: make webtidy error message more debianish
-Author: Ryan Niebur 
+From: Ryan Niebur 
+Date: Tue, 2 Jun 2009 21:15:36 -0700
+Subject: make webtidy error message more debianish
+
 Forwarded: not-needed
+---
+ bin/webtidy | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
 
+diff --git a/bin/webtidy b/bin/webtidy
+index be57814..4a92423 100755
 --- a/bin/webtidy
 +++ b/bin/webtidy
-@@ -29,7 +29,7 @@
+@@ -29,7 +29,7 @@ for my $url ( @ARGV ) {
  my @lines;
  if ( $url =~ /^https?:/ ) {
  if ( !eval { require LWP::Simple; 1; } ) {
diff --git a/debian/patches/remove-tidy_version.patch b/debian/patches/remove-tidy_version.patch
index 6bbeffa..7b553f2 100644
--- a/debian/patches/remove-tidy_version.patch
+++ b/debian/patches/remove-tidy_version.patch
@@ -1,15 +1,26 @@
-Description: remove tidyVersion as it is a special call
- to Andy Lester's modified version of libtidy. Also remove
- the corresponding call from Perl, the documentation, and
- the tests.
-Author: gregor herrmann 
+From: gregor herrmann 
+Date: Sat, 20 Feb 2010 09:50:30 -0500
+Subject: remove tidyVersion
+
+It is a special call to Andy Lester's modified version of libtidy. Also
+remove the corresponding call from Perl, the documentation, and the tests.
+
 Reviewed-by: Jonathan Yu 
 Origin: vendor
 

Bug#826816: openjpeg removal patch

[Ole Streicher]

Control: tags -1 patch

Dear Alastair,

I am the maintainer of gnudatalanguage, which is a transitive dependency
of grib-api.

since grib-api does not support openjpeg2 without changes (also not when
d/p/openjpeg2.patch is applied), it may be worth just to disabple
openjpeg for the moment completely, in order to avoid removal of
grib-api and its dependencies from Testing. Once grib-api works with the
openjpeg2 API, it may be re-enabled without effort.

The attached patch just removes the build dependency from d/control.
Since the autoremoval is scheduled for Aug 8, I would do a NMU in the
first days of august.

Best regards

Ole
diff -Nru grib-api-1.16.0/debian/changelog grib-api-1.16.0/debian/changelog
--- grib-api-1.16.0/debian/changelog	2016-07-08 16:48:39.0 +0200
+++ grib-api-1.16.0/debian/changelog	2016-07-22 11:04:16.0 +0200
@@ -1,3 +1,10 @@
+grib-api (1.16.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove libopenjpeg-dev build dependency. Closes: #826816
+
+ -- Ole Streicher   Fri, 22 Jul 2016 10:09:37 +0200
+
 grib-api (1.16.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru grib-api-1.16.0/debian/control grib-api-1.16.0/debian/control
--- grib-api-1.16.0/debian/control	2016-07-08 16:48:39.0 +0200
+++ grib-api-1.16.0/debian/control	2016-07-22 11:03:13.0 +0200
@@ -5,7 +5,7 @@
 Uploaders: Enrico Zini 
 Build-Depends: debhelper (>= 9), dh-buildinfo, cmake,
   libjpeg-dev, libpng-dev, gfortran, flex, bison, quilt,
-  libnetcdf-dev, libopenjpeg-dev, libboost-dev, libhdf5-dev, 
+  libnetcdf-dev, libboost-dev, libhdf5-dev, 
   curl,swig, 
   python3-all-dev,  python3-numpy, python3-six,
   python-all-dev, python-numpy, python-six,

Processed: openjpeg removal patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #826816 [src:grib-api] grib-api: OpenJPEG removal
Added tag(s) patch.

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

Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade

[Sebastian Ramacher]

Hi

On 2016-07-20 22:06:05, Faidon Liambotis wrote:
> Package: libavcodec57
> Version: 7:3.1.1-2
> Severity: grave
> 
> I ran Debian testing on my desktop. Since about a day ago, pidgin
> started crashing unexpectedly. After a little bit of debugging, I found
> that it reproducibly crashes when trying to play sounds. Going a step
> further, I made the test case as simple as:
> 
> $ gst-launch-1.0 filesrc location=/usr/share/sounds/purple/alert.wav  ! 
> wavparse ! audioconvert !  fakesink
> Setting pipeline to PAUSED ...
> Pipeline is PREROLLING ...
> Aborted (core dumped)

Unfortunately I am unable to reproduce the issue. Since there are some accounts
of random crashes when building ffmpeg with tree vectorization enabled, I've
uploaded 7:3.1.1-3 with vectorization disabled. Could you please check if the
issue disappears with -3?

> My dpkg.log has a bunch of ffmpeg-related package upgrades, including
> libavcodec57, being installed on 2016-07-18, approximately when those
> crashes started. Because of this and the backtrace below, I'm filing
> this against libavcodec57 -- feel free to reassign if that's wrong.
> 
> The backtrace seems to be:
>PID: 4121 (gst-launch-1.0)
>UID: 1000 (paravoid)
>GID: 1000 (paravoid)
> Signal: 6 (ABRT)
>  Timestamp: Τετ 2016-07-20 21:55:59 EEST (5min ago)
>   Command Line: gst-launch-1.0 filesrc 
> location=/usr/share/sounds/purple/alert.wav ! wavparse ! audioconvert ! 
> fakesink
> Executable: /usr/bin/gst-launch-1.0
>  Control Group: /
>  Slice: -.slice
>Boot ID: fc3d59275e1042c491633f9a920c10e5
> Machine ID: ddb673bb6861472487a0edbc40f6f1fc
>   Hostname: donald
>   Coredump: 
> /var/lib/systemd/coredump/core.gst-launch-1\x2e0.1000.fc3d59275e1042c491633f9a920c10e5.4121.1469040959.xz
>Message: Process 4121 (gst-launch-1.0) of user 1000 dumped core.
> 
> Stack trace of thread 4122:
> #0  0x7fa47ae7f1c8 raise (libc.so.6)
> #1  0x7fa47ae8064a abort (libc.so.6)
> #2  0x7fa4719b8f5b n/a (libavcodec.so.57)
> #3  0x7fa4719b9026 avcodec_alloc_context3 
> (libavcodec.so.57)
> #4  0x7fa473360540 n/a (libgstlibav.so)
> #5  0x7fa473356e53 n/a (libgstlibav.so)
> #6  0x7fa47b74b22d g_type_class_ref (libgobject-2.0.so.0)
> #7  0x7fa47b9c8da4 gst_element_register 
> (libgstreamer-1.0.so.0)
> #8  0x7fa4733575b3 n/a (libgstlibav.so)
> #9  0x7fa473349e20 n/a (libgstlibav.so)
> #10 0x7fa47b9ea537 n/a (libgstreamer-1.0.so.0)
> #11 0x7fa47b9ec425 n/a (libgstreamer-1.0.so.0)
> #12 0x7fa47b9ed12c gst_plugin_load_by_name 
> (libgstreamer-1.0.so.0)
> #13 0x7fa47b9eda8d gst_plugin_feature_load 
> (libgstreamer-1.0.so.0)
> #14 0x7fa47ba137e3 gst_type_find_factory_call_function 
> (libgstreamer-1.0.so.0)
> #15 0x7fa479c48421 gst_type_find_helper_for_data 
> (libgstbase-1.0.so.0)
> #16 0x7fa479c485a4 gst_type_find_helper_for_buffer 
> (libgstbase-1.0.so.0)
> #17 0x7fa4799f446a n/a (libgstwavparse.so)
> #18 0x7fa4799f4b47 n/a (libgstwavparse.so)
> #19 0x7fa4799fabb1 n/a (libgstwavparse.so)
> #20 0x7fa47ba0ee71 n/a (libgstreamer-1.0.so.0)
> #21 0x7fa47b47b55e n/a (libglib-2.0.so.0)
> #22 0x7fa47b47abc5 n/a (libglib-2.0.so.0)
> #23 0x7fa47b1f4464 start_thread (libpthread.so.0)
> #24 0x7fa47af3330d __clone (libc.so.6)
> 
> Stack trace of thread 4121:
> #0  0x7fa47af2a19d poll (libc.so.6)
> #1  0x7fa47b45439c n/a (libglib-2.0.so.0)
> #2  0x7fa47b454722 g_main_loop_run (libglib-2.0.so.0)
> #3  0x7fa47b9af8e9 gst_bus_poll (libgstreamer-1.0.so.0)
> #4  0x004046f8 n/a (gst-launch-1.0)
> #5  0x004036e9 n/a (gst-launch-1.0)
> #6  0x7fa47ae6c730 __libc_start_main (libc.so.6)
> #7  0x00403d19 n/a (gst-launch-1.0)
> 
> Stack trace of thread 4123:
> #0  0x7fa47af2a19d poll (libc.so.6)
> #1  0x7fa47b45439c n/a (libglib-2.0.so.0)
> #2  0x7fa47b4544ac g_main_context_iteration 
> (libglib-2.0.so.0)
> #3  0x7fa47b4544e9 n/a (libglib-2.0.so.0)
> #4  0x7fa47b47abc5 n/a (libglib-2.0.so.0)
> #5  0x7fa47b1f4464 start_thread (libpthread.so.0)
> #6  0x7fa47af3330d __clone (libc.so.6)

Please install libavcodec57-dbgsym and the -dbgsym packages 

Bug#817361: marked as done (aspell-sl: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 10:03:51 +0200
with message-id <1d09d3f6-2b6c-bf3b-2304-4b87a5bd9...@tablix.org>
and subject line Re: aspell-sl: Removal of debhelper compat 4
has caused the Debian Bug report #817361,
regarding aspell-sl: 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.)


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

Hi,

The package aspell-sl 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 ---
Version: 0.60-4

Hi

This has been fixed in aspell-sl 0.60-4 which set debhelper compat level
to 9.

Best regards
Tomaž



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

Bug#832091: kpatch install: Error! Bad return status for module build on kernel: 4.6.0-1-amd64 (x86_64)

[choury]

Package: kpatch
Version: 0.3.2-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,


When install the kpatch with apt, it comes:
Error! Bad return status for module build on kernel: 4.6.0-1-amd64 (x86_64)

And the error log of build:
DKMS make.log for kpatch-0.3.2 for kernel 4.6.0-1-amd64 (x86_64)

 
2016年 07月 22日 星期五 15:51:07 CST  

   
make: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod'

 
make -C core clean  

 
make[1]: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core'

 
rm -f -Rf .*.o.cmd .*.ko.cmd .tmp_versions *.o *.ko *.mod.c \   

 
Module.symvers  

 
make[1]: Leaving directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core' 

 
make -C core

 
make[1]: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core'

 
make -C /lib/modules/4.6.0-1-amd64/build 
M=/var/lib/dkms/kpatch/0.3.2/build/kmod/core kpatch.ko  


make[2]: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core'

 
make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.   

 
  CC [M]  /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.o 

 
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:255:13: error: initialization 
from incompatible pointer type [-Werror=incompatible-pointer-types] 
 
  .address = kpatch_backtrace_address_verify,   

 
 ^  

 
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:255:13: note: (near 
initialization for 'kpatch_backtrace_ops.address')  

   
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:275:13: error: initialization 
from incompatible pointer type [-Werror=incompatible-pointer-types] 
 
  .address = kpatch_print_trace_address,

  

Bug#832087: mps-youtube: Missing dependency python-pkg-resources

[Pawel Rozanski]

Package: mps-youtube
Version: 0.01.46-3
Severity: serious
Justification: 3

Dear Maintainer,
I installed mps-youtube and tried to run it:

$ mpsyt
Traceback (most recent call last):
  File "/usr/bin/mpsyt", line 5, in 
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

After debug it find out, that package python-pkg-resources is required to use 
mpsyt, and
it is not listed as dependency in mps-youtube package.

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

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

Versions of packages mps-youtube depends on:
ii  mplayer2 2.0-728-g2c378c7-4+b1
ii  python   2.7.9-1
ii  python-pafy  0.3.62-1

mps-youtube recommends no packages.

mps-youtube suggests no packages.

-- no debconf information