Processed: Re: Bug#791252: pythia8: library transition may be needed when GCC 5 is the default

[Debian Bug Tracking System]

Processing control commands:

> severity 791252 serious
Bug #791252 [src:pythia8] pythia8: library transition may be needed when GCC 5 
is the default
Severity set to 'serious' from 'important'
> tags 791252 + confirmed
Bug #791252 [src:pythia8] pythia8: library transition may be needed when GCC 5 
is the default
Added tag(s) confirmed.

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

Bug#795057: marked as done (python-xlib: Embedded code copy with missing copyright)

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 07:04:36 +
with message-id 
and subject line Bug#795057: fixed in python-xlib 0.14+20091101-3
has caused the Debian Bug report #795057,
regarding python-xlib:  Embedded code copy with missing copyright
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.)


-- 
795057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xlib
Version: 0.14+20091101-2
Severity: serious
Justification: Policy 4.5
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Your packages contains an embedded code copy of texi2html which is
copyright Lionel Cons and others and is licensed under the GPL and
Creative Commons Attribution-ShareAlike license. This information is
missing from debian/copyright of python-xlib and is thus a violation of
policy §4.5.

I found this bug while working on the reproducible builds project [1] to
make texi2html produce reproducible output.

From that point of view there are two options:

 1. remove the embedded code copy [2] and build-depend on texi2html
(this would also make policy §4.13 happy). I would prefer this
solution and would supply you with a patch if you want. 
The package would not become immediately reproducible with this
solution though because it does not use dh in debian/rules but
instead classic debhelper. Because of that $SOURCE_DATE_EPOCH has
to be exported in debian/rules [3]

 2. keep the embedded code copy and amend your debian/copyright. In this
case I would open another bug so that your embedded copy of
texi2html is patched to produce reproducible output.


Kind regards,
akira

[1] https://wiki.debian.org/ReproducibleBuilds/About
[2] https://wiki.debian.org/EmbeddedCodeCopies
[3] https://wiki.debian.org/ReproducibleBuilds/TimestampsProposal



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-xlib
Source-Version: 0.14+20091101-3

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

Debian distribution maintenance software
pp.
Andrew Shadura  (supplier of updated python-xlib 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, 13 Aug 2015 08:14:19 +0200
Source: python-xlib
Binary: python-xlib python3-xlib
Architecture: source all
Version: 0.14+20091101-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrew Shadura 
Description:
 python-xlib - interface for Python to the X11 protocol
 python3-xlib - interface for Python 3 to the X11 protocol
Closes: 565996 795057
Changes:
 python-xlib (0.14+20091101-3) unstable; urgency=medium
 .
   [ Ramkumar Ramachandra ]
   * Remove useless debugging output (Closes: #565996)
 .
   [ Andrew Shadura ]
   * Switch to 3.0 (quilt) format.
   * Rename patches.
   * Use debhelper 9 in its short form.
   * Use pybuild.
   * Bump Standards-Version.
   * Don't build or install PostScript documentation and info files.
   * Use system-provided texi2html instead of a shipped version
 (Closes: #795057).
   * Update debian/copyright (Closes: #795057).
   * Don't install Makefile or texi2html with the documentation.
   * Set executable bit for examples.
Checksums-Sha1:
 10b435453ca49959fe8b23257ae605c76038fe07 2183 python-xlib_0.14+20091101-3.dsc
 3d18c5a9507ecf6cd206a7cf01689a57b36551d6 54480 
python-xlib_0.14+20091101-3.debian.tar.xz
 df555dea19fc439b36a66bc1f2e004ad304e8553 101818 
python-xlib_0.14+20091101-3_all.deb
 9ff4f55b16e4b108d001087d30a0c6068a4bf9ff 101782 
python3-xlib_0.14+20091101-3_all.deb
Checksums-Sha256:
 ec7bcc736ff9065fc5ea0d9c79da12709e21c261021c8588288963acef260299 2183 
python-xlib_0.14+20091101-3.dsc
 61ee2e0b3447d9dcd51cf82f7cd980efedb6de287d0ffb5a823ced9c4721e589 54480 
python-xlib_0.14+20091101-3.debian.tar.xz
 d744f54863cf6cc69cf11c32629cfe52ceeef3f66aa7dd8274a04b00fc3476ce 101818 
python-xlib_0.14+20091101

Processed: Re: Bug#791201: mercator: library transition may be needed when GCC 5 is the default

[Debian Bug Tracking System]

Processing control commands:

> tags 791201 + confirmed
Bug #791201 [src:mercator] mercator: library transition may be needed when GCC 
5 is the default
Added tag(s) confirmed.
> severity 791201 serious
Bug #791201 [src:mercator] mercator: library transition may be needed when GCC 
5 is the default
Severity set to 'serious' from 'important'

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

Processed: Re: Bug#791127: libgtksourceviewmm: library transition may be needed when GCC 5 is the default

[Debian Bug Tracking System]

Processing control commands:

> tags 791127 + confirmed
Bug #791127 [src:libgtksourceviewmm] libgtksourceviewmm: library transition may 
be needed when GCC 5 is the default
Added tag(s) confirmed.
> severity 791127 serious
Bug #791127 [src:libgtksourceviewmm] libgtksourceviewmm: library transition may 
be needed when GCC 5 is the default
Severity set to 'serious' from 'important'
> retitle 791127 libgtksourceviewmm: transition to libgtksourceviewmm-3.0-0v5 
> needed
Bug #791127 [src:libgtksourceviewmm] libgtksourceviewmm: library transition may 
be needed when GCC 5 is the default
Changed Bug title to 'libgtksourceviewmm: transition to 
libgtksourceviewmm-3.0-0v5 needed' from 'libgtksourceviewmm: library transition 
may be needed when GCC 5 is the default'

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

Bug#791326: wfmath: library transition may be needed when GCC 5 is the default

[Mehdi Dogguy]

Control: tags -1 + confirmed
Control: severity -1 serious

On Fri, Jul 03, 2015 at 01:14:55PM +, Matthias Klose  
wrote:
>  - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
>library API, and are used by the reverse dependencies of the
>library.
> 

Uses of std::string are exposed in the public API. A proposed patch is available
from:

https://launchpad.net/ubuntu/+source/wfmath/1.0.2+dfsg1-0.3ubuntu1

Regards,

-- 
Mehdi Dogguy

Processed: Re: smokegen: library transition may be needed when GCC 5 is the default

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #791286 [src:smokegen] smokegen: library transition may be needed when GCC 
5 is the default
Added tag(s) confirmed.
> severity -1 serious
Bug #791286 [src:smokegen] smokegen: library transition may be needed when GCC 
5 is the default
Severity set to 'serious' from 'important'

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

Processed: Re: Bug#791326: wfmath: library transition may be needed when GCC 5 is the default

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #791326 [src:wfmath] wfmath: library transition may be needed when GCC 5 is 
the default
Ignoring request to alter tags of bug #791326 to the same tags previously set
> severity -1 serious
Bug #791326 [src:wfmath] wfmath: library transition may be needed when GCC 5 is 
the default
Ignoring request to change severity of Bug 791326 to the same value.

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

Processed: Re: Bug#791326: wfmath: library transition may be needed when GCC 5 is the default

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #791326 [src:wfmath] wfmath: library transition may be needed when GCC 5 is 
the default
Added tag(s) confirmed.
> severity -1 serious
Bug #791326 [src:wfmath] wfmath: library transition may be needed when GCC 5 is 
the default
Severity set to 'serious' from 'important'

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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 759560 + fixed pending
Bug #759560 [yate] missing license in debian/copyright
Added tag(s) fixed and pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#791316: yaml-cpp0.3: library transition may be needed when GCC 5 is the default

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #791316 [src:yaml-cpp0.3] yaml-cpp0.3: library transition may be needed 
when GCC 5 is the default
Ignoring request to alter tags of bug #791316 to the same tags previously set
> severity -1 serious
Bug #791316 [src:yaml-cpp0.3] yaml-cpp0.3: library transition may be needed 
when GCC 5 is the default
Ignoring request to change severity of Bug 791316 to the same value.

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

Processed: Re: Bug#791316: yaml-cpp0.3: library transition may be needed when GCC 5 is the default

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #791316 [src:yaml-cpp0.3] yaml-cpp0.3: library transition may be needed 
when GCC 5 is the default
Added tag(s) confirmed.
> severity -1 serious
Bug #791316 [src:yaml-cpp0.3] yaml-cpp0.3: library transition may be needed 
when GCC 5 is the default
Severity set to 'serious' from 'important'

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

Bug#791316: yaml-cpp0.3: library transition may be needed when GCC 5 is the default

[Mehdi Dogguy]

Control: tags -1 + confirmed
Control: severity -1 serious

On Fri, Jul 03, 2015 at 01:15:04PM +, Matthias Klose  
wrote:
>  - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
>library API, and are used by the reverse dependencies of the
>library.
> 

This package is affected just like src:yaml-cpp. A proposed patch is
available from:

https://launchpad.net/ubuntu/+source/yaml-cpp0.3/0.3.0-1.1ubuntu1

Regards,

-- 
Mehdi Dogguy

Processed: Re: Bug#791063: transition: libgsmme1v5

[Debian Bug Tracking System]

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

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was s...@debian.org).
> usertag 791063 + transition
There were no usertags set.
Usertags are now: transition.
> block 791063 by 790756
Bug #791063 [src:gsmlib] gsmlib: library transition may be needed when GCC 5 is 
the default
791063 was not blocked by any bugs.
791063 was not blocking any bugs.
Added blocking bug(s) of 791063: 790756
> reassign 791063 release.debian.org
Bug #791063 [src:gsmlib] gsmlib: library transition may be needed when GCC 5 is 
the default
Bug reassigned from package 'src:gsmlib' to 'release.debian.org'.
No longer marked as found in versions gsmlib/1.10+20120414.gita5e5ae9a-0.2.
Ignoring request to alter fixed versions of bug #791063 to the same values 
previously set
> retitle 791063 transition: libgsmme1v5
Bug #791063 [release.debian.org] gsmlib: library transition may be needed when 
GCC 5 is the default
Changed Bug title to 'transition: libgsmme1v5' from 'gsmlib: library transition 
may be needed when GCC 5 is the default'
> severity 791063 normal
Bug #791063 [release.debian.org] transition: libgsmme1v5
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#791063: transition: libgsmme1v5

[Simon McVittie]

user release.debian@packages.debian.org
usertag 791063 + transition
block 791063 by 790756
reassign 791063 release.debian.org
retitle 791063 transition: libgsmme1v5
severity 791063 normal
thanks

gsmlib/1.10+20120414.gita5e5ae9a-0.3 started this transition.

There doesn't seem to be an "auto-" transition tracker for this yet?

S

Bug#795343: zotero-standalone: Package stopped working after iceweasel upgrade.

[Ignacio Lopez Franco]

Package: zotero-standalone
Version: 4.0.22-1
Severity: grave

Dear Maintainer,

After upgrading iceweasel in stable zotero-standalone stopped working,
giving instead the error message:

   Error: Platform version '38.2.0' is not compatible with
   minVersion >= 24.0
   maxVersion <= 32.*

Note the similitude with #792558.
Hope this can be resolved.

Ignacio


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

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

Versions of packages zotero-standalone depends on:
ii  iceweasel  38.2.0esr-1~deb8u1

zotero-standalone recommends no packages.

zotero-standalone suggests no packages.

-- no debconf information

Bug#791115: transition: libdc0 (libdc5v5)

[Simon McVittie]

user release.debian@packages.debian.org
usertag 791115 + transition
block 791115 by 790756
reassign 791115 release.debian.org
retitle 791115 transition: libdc0 (libdc5v5)
severity 791115 normal
thanks

This transition started with libdc0/0.3.24~svn3121-2.1

Processed: Re: Bug#791115: transition: libdc0 (libdc5v5)

[Debian Bug Tracking System]

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

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was s...@debian.org).
> usertag 791115 + transition
There were no usertags set.
Usertags are now: transition.
> block 791115 by 790756
Bug #791115 [src:libdc0] libdc0: library transition may be needed when GCC 5 is 
the default
791115 was not blocked by any bugs.
791115 was not blocking any bugs.
Added blocking bug(s) of 791115: 790756
> reassign 791115 release.debian.org
Bug #791115 [src:libdc0] libdc0: library transition may be needed when GCC 5 is 
the default
Bug reassigned from package 'src:libdc0' to 'release.debian.org'.
No longer marked as found in versions libdc0/0.3.24~svn3121-2.
Ignoring request to alter fixed versions of bug #791115 to the same values 
previously set
> retitle 791115 transition: libdc0 (libdc5v5)
Bug #791115 [release.debian.org] libdc0: library transition may be needed when 
GCC 5 is the default
Changed Bug title to 'transition: libdc0 (libdc5v5)' from 'libdc0: library 
transition may be needed when GCC 5 is the default'
> severity 791115 normal
Bug #791115 [release.debian.org] transition: libdc0 (libdc5v5)
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#795344: libmems-1.6-1: not properly linked to its dependencies

[Simon McVittie]

Package: libmems-1.6-1
Version: 1.6.0+4725-1
Severity: serious
Justification: Policy 10.2

>From the i386 buildd log:

   dh_shlibdeps -a
dpkg-shlibdeps: warning: symbol _ZN6muscle4QuitEPKcz used by 
debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in none 
of the libraries
dpkg-shlibdeps: warning: symbol _ZNK6genome10gnSequence6subseqEyy used by 
debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in none 
of the libraries
dpkg-shlibdeps: warning: symbol _ZN6muscle8DistFunc8SetCountEj used by 
debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in none 
of the libraries
dpkg-shlibdeps: warning: symbol _ZN6muscle10RefineVertERNS_3MSAERKNS_4TreeEj 
used by debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found 
in none of the libraries
dpkg-shlibdeps: warning: symbol _ZNK5boost9iostreams18mapped_file_source4dataEv 
used by debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found 
in none of the libraries
dpkg-shlibdeps: warning: symbol 
_ZN5boost10filesystem4path27m_erase_redundant_separatorEj used by 
debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in none 
of the libraries
dpkg-shlibdeps: warning: symbol _ZN6muscle18SetSeqWeightMethodENS_9SEQWEIGHTE 
used by debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found 
in none of the libraries
dpkg-shlibdeps: warning: symbol _ZN6muscle8TextFileC1EPKcb used by 
debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in none 
of the libraries
dpkg-shlibdeps: warning: symbol _ZN6genome10gnSequence13setContigNameEjRKSs 
used by debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found 
in none of the libraries
dpkg-shlibdeps: warning: symbol _ZNK6muscle3MSA11GetSeqIndexEj used by 
debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in none 
of the libraries
dpkg-shlibdeps: warning: 79 other similar warnings have been skipped (use -v to 
see them all)

Among other things, this causes libmems to not show up properly in the
 transition
tracker, so the release team will not schedule the necessary binNMUs for it.

Regards,
S

Bug#792655: Further details on 792655

[Johannes Dröge]

Hi Didier,

after upgrading to CUPS version 2 from testing if found that it gave the same
errors when accessing SSL functions. So I concluded that this might be a problem
in the package libgnutls-deb0-28. After a little searching I found this recent
(14 June 2015) bug report:

https://bugs.debian.org/788704

It turns out that the bug in GnuTLS is platform-specific

processor   : 0
vendor_id   : CentaurHauls
cpu family  : 6
model   : 13
model name  : VIA Eden Processor 1500MHz

The bug is fixed in newer upstream versions of GnuTLS but the one included in
Debian Jessie still has the bug. After installing patched versions of the
package, the segfault vanished. For me this is fine now but I hope that the
patch finds its way into the stable release so other users don't run into this
problem. Therefore, its good to have this documented here.

Gruß Johannes



smime.p7s
Description: S/MIME Cryptographic Signature

Processed (with 2 errors): Re: Bug#792655: Further details on 792655

[Debian Bug Tracking System]

Processing control commands:

> retitle 792655 libgnutls segfault crashing CUPS
Bug #792655 [cups-daemon] cups-daemon: cupsd sefaults when handling ssl with 
libgnutls
Changed Bug title to 'libgnutls segfault crashing CUPS' from 'cups-daemon: 
cupsd sefaults when handling ssl with libgnutls'
> reassign 792655 gnutls28 3.3.8-6+deb8u1
Bug #792655 [cups-daemon] libgnutls segfault crashing CUPS
Bug reassigned from package 'cups-daemon' to 'gnutls28'.
No longer marked as found in versions cups/1.7.5-11+deb8u1.
Ignoring request to alter fixed versions of bug #792655 to the same values 
previously set
Bug #792655 [gnutls28] libgnutls segfault crashing CUPS
There is no source info for the package 'gnutls28' at version '3.3.8-6+deb8u1' 
with architecture ''
Unable to make a source version for version '3.3.8-6+deb8u1'
Marked as found in versions 3.3.8-6+deb8u1.
> forcemerge 788704 792655
Bug #788704 [src:gnutls28] gnutls28: VIA PadLock accelerated AES-CBC segfaults
Unable to merge bugs because:
package of #792655 is 'gnutls28' not 'src:gnutls28'
Failed to forcibly merge 788704: Did not alter merged bugs.

> affects 788704 + cups
Failed to mark 788704 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/788704 -- Unable to lock 
/org/bugs.debian.org/spool/lock/788704 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.


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

Bug#792655: Further details on 792655

[Didier 'OdyX' Raboud]

Control: retitle 792655 libgnutls segfault crashing CUPS
Control: reassign 792655 gnutls28 3.3.8-6+deb8u1
Control: forcemerge 788704 792655
Control: affects 788704 + cups

Le jeudi, 13 août 2015, 10.28:17 Johannes Dröge a écrit :
> after upgrading to CUPS version 2 from testing if found that it gave
> the same errors when accessing SSL functions. So I concluded that
> this might be a problem in the package libgnutls-deb0-28. After a
> little searching I found this recent (14 June 2015) bug report:
> 
> https://bugs.debian.org/788704
> 
> It turns out that the bug in GnuTLS is platform-specific
> 
> processor   : 0
> vendor_id   : CentaurHauls
> cpu family  : 6
> model   : 13
> model name  : VIA Eden Processor 1500MHz
> 
> The bug is fixed in newer upstream versions of GnuTLS but the one
> included in Debian Jessie still has the bug. After installing patched
> versions of the package, the segfault vanished. For me this is fine
> now but I hope that the patch finds its way into the stable release
> so other users don't run into this problem. Therefore, its good to
> have this documented here.

Great, thanks for the findings and explanation. I'm hereby reassigning 
this bug as not being a CUPS bug, assign it to GnuTLS and mark CUPS 
affected.

Thanks for your time!

Cheers,
OdyX

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

Processed (with 2 errors): Re: Bug#792655: Further details on 792655

[Debian Bug Tracking System]

Processing control commands:

> retitle 792655 libgnutls segfault crashing CUPS
Bug #792655 [gnutls28] libgnutls segfault crashing CUPS
Ignoring request to change the title of bug#792655 to the same title
> reassign 792655 gnutls28 3.3.8-6+deb8u1
Bug #792655 [gnutls28] libgnutls segfault crashing CUPS
Ignoring request to reassign bug #792655 to the same package
Bug #792655 [gnutls28] libgnutls segfault crashing CUPS
There is no source info for the package 'gnutls28' at version '3.3.8-6+deb8u1' 
with architecture ''
Unable to make a source version for version '3.3.8-6+deb8u1'
Ignoring request to alter found versions of bug #792655 to the same values 
previously set
> forcemerge 788704 792655
Bug #788704 [src:gnutls28] gnutls28: VIA PadLock accelerated AES-CBC segfaults
Unable to merge bugs because:
package of #792655 is 'gnutls28' not 'src:gnutls28'
Failed to forcibly merge 788704: Did not alter merged bugs.

> affects 788704 + cups
Failed to mark 788704 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/788704 -- Unable to lock 
/org/bugs.debian.org/spool/lock/788704 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/788704 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.


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

Processed: reassign 792655 to src:gnutls28

[Debian Bug Tracking System]

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

> reassign 792655 src:gnutls28
Bug #792655 [gnutls28] libgnutls segfault crashing CUPS
Bug reassigned from package 'gnutls28' to 'src:gnutls28'.
No longer marked as found in versions 3.3.8-6+deb8u1.
Ignoring request to alter fixed versions of bug #792655 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: retitle 790532 to FTBFS: t/GdkWindow.t crashes perl

[Debian Bug Tracking System]

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

> retitle 790532 FTBFS: t/GdkWindow.t crashes perl
Bug #790532 [libgtk2-perl] FTBFS: Failed 1/228 test programs
Changed Bug title to 'FTBFS: t/GdkWindow.t crashes perl' from 'FTBFS: Failed 
1/228 test programs'
> thanks
Stopping processing here.

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

Processed (with 1 errors): forcibly merging 788704 792655

[Debian Bug Tracking System]

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

> forcemerge 788704 792655
Bug #788704 [src:gnutls28] gnutls28: VIA PadLock accelerated AES-CBC segfaults
Unable to merge bugs because:
package of #792655 is 'gnutls28' not 'src:gnutls28'
Failed to forcibly merge 788704: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: forcibly merging 788704 792655

[Debian Bug Tracking System]

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

> forcemerge 788704 792655
Bug #788704 [src:gnutls28] gnutls28: VIA PadLock accelerated AES-CBC segfaults
Bug #788704 [src:gnutls28] gnutls28: VIA PadLock accelerated AES-CBC segfaults
Added tag(s) unreproducible.
Bug #792655 [src:gnutls28] libgnutls segfault crashing CUPS
Set Bug forwarded-to-address to 
'http://lists.gnutls.org/pipermail/gnutls-devel/2015-June/007626.html'.
Severity set to 'important' from 'grave'
Added indication that 792655 affects cups
Marked as fixed in versions gnutls28/3.3.12-1.
Marked as found in versions gnutls28/3.3.8-6 and gnutls28/3.3.8-6+deb8u1.
Added tag(s) patch.
Merged 788704 792655
> thanks
Stopping processing here.

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

Bug#790532: perl-Gtk2: GdkWindow.t fails with libgtk2 2.24.28 and libgdk-pixbuf2.0 2.31.4-2

[intrigeri]

Hi,

for the record, I see the same test failure with perl-Gtk2 1.2496.

Cheers,
-- 
intrigeri

Processed: limit source to gnome-maps, tagging 794092

[Debian Bug Tracking System]

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

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

> tags 794092 + pending
Bug #794092 [gnome-maps] gnome-maps misses dependency on gir1.2-goa-1.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#795031: marked as done (ruby-coercible: FTBFS: rspec3 port needed(?): undefined method `its')

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 11:35:07 +0200
with message-id <20150813093507.GA7309@spin>
and subject line closed by upload of 1.0.0-2
has caused the Debian Bug report #795031,
regarding ruby-coercible: FTBFS: rspec3 port needed(?): undefined method `its'
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.)


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

Dear Maintainer,

The package fails to build:

┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/ruby-coercible-1.0.0/debian/ruby-coercible/usr/lib/ruby/vendor_ruby:. 
rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
/usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in `method_missing': 
undefined method `its' for RSpec::ExampleGroups::CoercibleCoercerNew:Class 
(NoMethodError)
from 
/ruby-coercible-1.0.0/spec/unit/coercible/coercer/class_methods/new_spec.rb:10:in
 `block in '
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in 
`block in define_example_group_method'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in 
expose_example_group_alias'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2 
levels) in expose_example_group_alias_globally'
from 
/ruby-coercible-1.0.0/spec/unit/coercible/coercer/class_methods/new_spec.rb:3:in
 `'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in 
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in 
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in 
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in 
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke'
from /usr/bin/rspec:4:in `'
/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb 
failed
ERROR: Test "ruby2.1" failed. Exiting.
dh_auto_install: dh_ruby --install /ruby-coercible-1.0.0/debian/ruby-coercible 
returned exit code 1

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-coercible.html

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
fixed 79031 1.0.0-2
thanks

Hi,
This bug has been closed by 1.0.0-2. A typo in the changelog seems to
have prevented the automatic closure of this bug. Doing it manually now.

Cheers,

Cédric




signature.asc
Description: Digital signature
--- End Message ---

Bug#795344: libmems-1.6-1: not properly linked to its dependencies

[Andreas Tille]

Hi Simon,

thanks for your bug report.  Yesterday I noticed that libmems needs a
transition but it needs to wait for boost libs first.

However, from your mail it seems that there is some issue with libmuscle
which I do not understand and where I have no idea how to fix.  Could
you be so kind to give some more detailed hint how this can be fixed and
why the package is hidden from the transition tracker?

Kind regards

   Andreas.

On Thu, Aug 13, 2015 at 09:45:48AM +0100, Simon McVittie wrote:
> >From the i386 buildd log:
> 
>dh_shlibdeps -a
> dpkg-shlibdeps: warning: symbol _ZN6muscle4QuitEPKcz used by 
> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
> none of the libraries
> dpkg-shlibdeps: warning: symbol _ZNK6genome10gnSequence6subseqEyy used by 
> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
> none of the libraries
> dpkg-shlibdeps: warning: symbol _ZN6muscle8DistFunc8SetCountEj used by 
> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
> none of the libraries
> dpkg-shlibdeps: warning: symbol _ZN6muscle10RefineVertERNS_3MSAERKNS_4TreeEj 
> used by debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 
> found in none of the libraries
> dpkg-shlibdeps: warning: symbol 
> _ZNK5boost9iostreams18mapped_file_source4dataEv used by 
> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
> none of the libraries
> dpkg-shlibdeps: warning: symbol 
> _ZN5boost10filesystem4path27m_erase_redundant_separatorEj used by 
> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
> none of the libraries
> ...
-- 
http://fam-tille.de

Bug#795134: marked as done (ruby-rabl-rails: FTBFS: minitest: invalid option: -f)

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 09:45:59 +
with message-id 
and subject line Bug#795134: fixed in ruby-rabl-rails 0.4.1-1
has caused the Debian Bug report #795134,
regarding ruby-rabl-rails: FTBFS: minitest: invalid option: -f
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.)


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

Dear Maintainer,

The package fails to build:

┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/ruby-rabl-rails-0.4.0/debian/ruby-rabl-rails/usr/lib/ruby/vendor_ruby:.
 rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 -I"lib:test" -I"/usr/lib/ruby/vendor_ruby" 
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/**/test_*.rb" 
Run options: --seed 54426

# Running:

..S...

Finished in 0.022412s, 4194.1454 runs/s, 5443.4653 assertions/s.

94 runs, 122 assertions, 0 failures, 0 errors, 1 skips

You have skipped tests. Run with --verbose for details.

invalid option: -f

minitest options:
-h, --help   Display this help.
-s, --seed SEED  Sets random seed. Also via env. Eg: SEED=n 
rake
-v, --verboseVerbose. Show progress processing files.
-n, --name PATTERN   Filter run on /regexp/ or string.

Known extensions: pride
-p, --pride  Pride. Show your testing pride!


Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-rabl-rails.html

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: ruby-rabl-rails
Source-Version: 0.4.1-1

We believe that the bug you reported is fixed in the latest version of
ruby-rabl-rails, 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 795...@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-rabl-rails 
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, 13 Aug 2015 11:24:46 +0200
Source: ruby-rabl-rails
Binary: ruby-rabl-rails
Architecture: source all
Version: 0.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-rabl-rails - fast Rails 3+ templating system with JSON and XML support
Closes: 795134
Changes:
 ruby-rabl-rails (0.4.1-1) unstable; urgency=medium
 .
   * Imported Upstream version 0.4.1
   * Do not require minitest/autorun from ruby-tests.rake (Closes: #795134)
Checksums-Sha1:
 5b193ff6878a5c772926fbe193b80641aa4cb716 1848 ruby-rabl-rails_0.4.1-1.dsc
 22b371f4293e0035064cf04504e0ecbb832188e9 20667 
ruby-rabl-rails_0.4.1.orig.tar.gz
 62813099d6e4387a45b3e30b5f9db4af08578c11 2724 
ruby-rabl-rails_0.4.1-1.debian.tar.xz
 a86030c36c62b363bba808a1810da171576cb5a7 12354 ruby-rabl-rails_0.4.1-1_all.deb
Checksums-Sha256:
 f380c5a3a10897218e73d47220cc9c22e7c3c4eb5b23d57e8cc729cae3128abc 1848 
ruby-rabl-rails_0.4.1-1.dsc
 d518266759d2af1ff39c8e0dff626d28541e141115569a379beb7a4a2d2c2721 20667 
ruby-rabl-rails_0.4.1.orig.tar.gz
 644cc542859e3c4b0f3d4d17f2b619da1c8d56b3febdcfe0526d91ecd330a9f1 2724 
ruby-rabl-rails_0.4.1-1.debian.tar.xz
 9273f14e8b012cf91d4d995a7518de932e48a6a47b067c47404af128632acd7f 12354 
ruby-rabl-rails_0.4.1-1_all.deb
Files:
 be8adebd0912b03316bb95f2215b6f9d 1848 r

Bug#794165: marked as done (FTBFS: Distribution::Binomial singleton should respond to #exact_p_value fails)

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 09:45:53 +
with message-id 
and subject line Bug#794165: fixed in ruby-distribution 0.7.3+dfsg-1
has caused the Debian Bug report #794165,
regarding FTBFS: Distribution::Binomial singleton should respond to 
#exact_p_value fails
to be marked as done.

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

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


-- 
794165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-distribution
Version: 0.7.0+dfsg-1
Severity: serious
Tags: sid
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs

Dear Maintainer,

The package fails to build:

..F*F*...FF...F*.*..*..F..

Pending: (Failures listed here are expected and do not affect your suite's 
status)

  1) Distribution::Binomial singleton should respond to #exact_p_value
 # No exact_p_value
 Failure/Error: @engine.should respond_to(:exact_p_value)
   expected Distribution::Binomial to respond to :exact_p_value
 # ./spec/binomial_spec.rb:52:in `block (3 levels) in '

  2) Distribution::Binomial Distribution::Binomial::Ruby_ should return correct 
p_value for n<=100
 # Can't calculate with precision x using p
 Failure/Error: p_value.should eq(x), "For p_value(#{cdf},#{n},#{pr}) 
expected #{x}, obtained #{p_value}"
   For p_value(0.07812690734863297,10,0.75) expected 5, obtained 6
 # ./spec/binomial_spec.rb:91:in `block (6 levels) in '
 # ./spec/binomial_spec.rb:87:in `each'
 # ./spec/binomial_spec.rb:87:in `block (5 levels) in '
 # ./spec/binomial_spec.rb:86:in `each'
 # ./spec/binomial_spec.rb:86:in `block (4 levels) in '
 # ./spec/binomial_spec.rb:85:in `each'
 # ./spec/binomial_spec.rb:85:in `block (3 levels) in '

... and others.

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-distribution.html

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: ruby-distribution
Source-Version: 0.7.3+dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-distribution 
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, 13 Aug 2015 10:14:29 +0200
Source: ruby-distribution
Binary: ruby-distribution
Architecture: source all
Version: 0.7.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-distribution - Ruby library to work with probability distributions
Closes: 794165
Changes:
 ruby-distribution (0.7.3+dfsg-1) unstable; urgency=medium
 .
   * Imported Upstream version 0.7.3+dfsg
   * Use Files-Excluded: to filter non-dfsg files
   * Update year, email, homepage in copyright file
   * Refresh packaging with dh-make-ruby -w
   * Add patches to fix or workaround issues with tests (Closes: #794165)
   * Remove coverage/ when cleaning
Checksums-Sha1:
 937d19ba91fa129c93ff1a039e14b324e03a48cb 1796 
ruby-distribution_0.7.3+dfsg-1.dsc
 47940df2947f64e78d0a27fe0344649930ae8723 57888 
ruby-distribution_0.7.3+dfsg.orig.tar.gz
 11eb5a7037836874550873663b4cdf32840fca3d 3340 
ruby-distribution_0.7.3+dfsg-1.debian.tar.xz
 5a11843fc1f40ea42a5dc506e44135890a67cbae 38400 
ruby-distribution_0.7.3+dfsg-1_all.deb
Checksums-Sha256:
 c4781315dd461c9fbd8ae2fbd6e691fb6a4053535836567d57f72570ed87bd3a 1796 
ruby-distribution_0.7.3+dfsg-1.dsc
 2eba6c9fa0add81721b43d40648ee1142a00ba62fc16fc0fe95c64ae603203d3 57888 
ruby-distribution_0.7.3+dfsg.orig.tar.gz
 7dbb14bd0d7e2473afa989679ea

Bug#791190: log4cplus: library transition may be needed when GCC 5 is the default

[Andrew Pollock]

On Wed, Aug 12, 2015 at 12:49:21PM +0200, Julien Cristau wrote:
> Control: severity -1 serious
> Control: tag -1 confirmed
> 
> On Fri, Jul  3, 2015 at 13:12:38 +, Matthias Klose wrote:
> 
> >  - Rebuild the library using g++/g++-5 from experimental. Note that
> >most likely all C++ libraries within the build dependencies need
> >a rebuild too. You can find the log for a rebuild in
> >  https://people.debian.org/~doko/logs/gcc5-20150701/
> >Search for "BEGIN GCC CXX11" in the log.
> > 
> >  - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
> >library API, and are used by the reverse dependencies of the
> >library.
> > 
> log4cplus does expose std::string through the log4cplus::tstring
> typedef, so liblog4cplus-1.0-4 will need to be renamed.
> 
> A possible patch is available from
> https://launchpad.net/ubuntu/+source/log4cplus/1.0.4-1.2ubuntu1

I've got a new upstream release almost ready to upload anyway. I'll try and
upload it over the weekend.


signature.asc
Description: Digital signature

Bug#791200: marked as done (med-fichier: library transition may be needed when GCC 5 is the default)

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 10:00:47 +
with message-id 
and subject line Bug#791200: fixed in med-fichier 3.0.6-8
has caused the Debian Bug report #791200,
regarding med-fichier: library transition may be needed when GCC 5 is the 
default
to be marked as done.

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

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


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

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

What is needed:

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

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

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

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

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

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
--- End Message ---
--- Begin Message ---
Source: med-fichier
Source-Version: 3.0.6-8

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated med-fichier 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, 12 Aug 2015 19:34:51 +0200
Source: med-fichier
Binary: libmed-dev libmed-doc libmed-tools libmed1v5 libmedc-dev libmedc1v5 
libmedimport-dev libmedimport0v5
Architecture: source all
Version: 3.0.6-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 libmed-dev - Development files for libmed
 libmed-doc - Documentation for the MED-fichier library
 libmed-tools - Runtime tools to handle MED files
 libmed1v5  - Library to exchange meshed data (Fortran version)
 libmedc-dev - Development files for libmedc
 libmedc1v5 - Library to exchange meshed data (C version)
 libmedimport-dev - Development files for libmedimport0
 libmedimport

Processed: fixed 795031 in 1.0.0-2

[Debian Bug Tracking System]

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

> fixed 795031 1.0.0-2
Bug #795031 {Done: Cédric Boutillier } [src:ruby-coercible] 
ruby-coercible: FTBFS: rspec3 port needed(?): undefined method `its'
Marked as fixed in versions ruby-coercible/1.0.0-2.
> thanks
Stopping processing here.

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

Bug#795210: marked as done (bladerf-firmware-fx3: package not allowed in main)

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 10:00:18 +
with message-id 
and subject line Bug#795210: fixed in bladerf 0.2015.07-2
has caused the Debian Bug report #795210,
regarding bladerf-firmware-fx3: package not allowed in main
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.)


-- 
795210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bladerf-firmware-fx3
Version: 0.2015.07-1
Severity: serious
Justification: Policy 2.2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Debian Policy §2.2.1, no package in main is permitted to
depend on code outside of main to function.

Package description for bladerf-firmware-fx3 describes its only purpose
being to download a piece of code (firmware) via web.

Please either move the package to contrib, or (if permitted) package the
firmware itself instead.


 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJVylC5AAoJECx8MUbBoAEhjCcP/1nBTqbEwQ0Wbp3Shk2/ARbP
/UjgQzdPaoUNmXr7slHk12KRiKDTKsxz/uxmSR3y6DmBBL472oySRW0ZdsZL1RUQ
8A3w/xwKvkkWTlqjE5b9rVizwBv7lI7VhMJ9a8K/2VDKF9jrSWaVqppcih3E+7kr
hGt9nCq8FSYQL9tlhoURWSC6k7pF7QmSiO9M60ZPFnD19dnDiAXTUvX+CSuASEuf
jOpHue9h+aIkvs+dRoNC9y/rfANuxuBvFuyW4aVisgP6gOcl7LLZPWwK6sTYd/WX
RCH/BtPhuR9KIqkW1VqreY1vgN/9Sjmsr8hPs15I2UgHw3otrjxiYzj7jr0ZA108
ipHvgX6EqK3v74BEHSuBKkJqXTIu+mCWbsNPg9SYRuB8sR2mykLJFe0B2Mynzxjm
n7iyoMkwHY6U9kKQoyGZO7E5WbIfAdubgY8SE9Ijq0WffXgXZnopcc6JssE1vznB
M7afhmLQVesdXqhYWLPnQDggTYv8pDJAL5eKzJzw23NdkJ0VkqXlCXmOBH8nI+JH
6EfiQ6bzajkm6ZC8x56b7hMuj5fjsdEfU7Gf88ijI4T0qEUPrqVfH0HJ0Vv11Puz
oG2GBlQJDFEMemr1r+tLmVO0k/I39vzp5OHh0i84K9VPiPdmIPl4PGy160lu8mLh
RmvESiyqz1unyjK8jd0u
=Tq1E
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: bladerf
Source-Version: 0.2015.07-2

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated bladerf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 12 Aug 2015 00:53:59 -0400
Source: bladerf
Binary: libbladerf1 libbladerf-dev bladerf bladerf-fpga-hostedx40 
bladerf-fpga-hostedx115 bladerf-firmware-fx3
Architecture: source amd64
Version: 0.2015.07-2
Distribution: sid
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Description:
 bladerf- nuand bladeRF software-defined radio device (tools)
 bladerf-firmware-fx3 - nuand bladeRF firmware downloader (FX3)
 bladerf-fpga-hostedx115 - nuand bladeRF FPGA bitstream downloader (hostedx115)
 bladerf-fpga-hostedx40 - nuand bladeRF FPGA bitstream downloader (hostedx40)
 libbladerf-dev - nuand bladeRF software-defined radio device (header files)
 libbladerf1 - nuand bladeRF software-defined radio device
Closes: 795210
Changes:
 bladerf (0.2015.07-2) unstable; urgency=medium
 .
   * place optional installer packages in contrib (Closes: #795210)
Checksums-Sha1:
 1235062ea8a86424878760f5c4e7c40b4708c859 2324 bladerf_0.2015.07-2.dsc
 51fcd74d4de9d2684dd001805d40a510b1709c79 12952 
bladerf_0.2015.07-2.debian.tar.xz
 a116fb8c314fbc132b572702f939184ae3fdc116 16504 
bladerf-firmware-fx3_0.2015.07-2_amd64.deb
 8468f36ae689eb047ab385c2fbc07e7481a6bb03 16520 
bladerf-fpga-hostedx115_0.2015.07-2_amd64.deb
 2b6c0ad8c982f485c88019f316c1ae418cbdcc72 16516 
bladerf-fpga-hostedx40_0.2015.07-2_amd64.deb
 11d89407eac479f0332927702b9bd0a3e93baadc 79626 bladerf_0.2015.07-2_amd64.deb
 14b89f1253c7ef8313839fdc94f6db836b3bed8c 39980 
libbladerf-dev_0.2015.07-2_amd64.deb
 f06977930b40eebba17b5faf9039cb61c30690c9 84176 
libbladerf1_0.2015.07-2_amd64.deb
Checksums-Sha256:
 ad047e7ccc5cc35f191b051e936c9747385a1c614ebcbf50b53045fb75c2894f 2324 
bladerf_0.2015.07-2.dsc
 b8756695bbcd46cba04954d3a00f583fdc37035b32caa9d75303e589992475df 12952 
bladerf_0.2015.07-2.debian.tar.xz
 785409c9fdb328aebb6484c675c4bc201eddf5364df951a409b8f22b487bbad1 16504 
bladerf-firmware-fx3_0.2015.07-2_amd64.deb
 b6277ab288d1ae44534ec0fa6ad9870f871e504ad3f32fb105f95f8d4fd74829 16520 

Bug#795134: marked as done (ruby-rabl-rails: FTBFS: minitest: invalid option: -f)

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 10:24:01 +
with message-id 
and subject line Bug#795134: fixed in ruby-treetop 1.6.3-1
has caused the Debian Bug report #795134,
regarding ruby-rabl-rails: FTBFS: minitest: invalid option: -f
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.)


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

Dear Maintainer,

The package fails to build:

┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/ruby-rabl-rails-0.4.0/debian/ruby-rabl-rails/usr/lib/ruby/vendor_ruby:.
 rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 -I"lib:test" -I"/usr/lib/ruby/vendor_ruby" 
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/**/test_*.rb" 
Run options: --seed 54426

# Running:

..S...

Finished in 0.022412s, 4194.1454 runs/s, 5443.4653 assertions/s.

94 runs, 122 assertions, 0 failures, 0 errors, 1 skips

You have skipped tests. Run with --verbose for details.

invalid option: -f

minitest options:
-h, --help   Display this help.
-s, --seed SEED  Sets random seed. Also via env. Eg: SEED=n 
rake
-v, --verboseVerbose. Show progress processing files.
-n, --name PATTERN   Filter run on /regexp/ or string.

Known extensions: pride
-p, --pride  Pride. Show your testing pride!


Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-rabl-rails.html

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: ruby-treetop
Source-Version: 1.6.3-1

We believe that the bug you reported is fixed in the latest version of
ruby-treetop, 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 795...@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-treetop 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, 13 Aug 2015 11:51:47 +0200
Source: ruby-treetop
Binary: ruby-treetop treetop
Architecture: source all
Version: 1.6.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-treetop - Ruby-based text parsing and interpretation DSL
 treetop- Ruby-based text parsing and interpretation (command-line utility)
Closes: 795134
Changes:
 ruby-treetop (1.6.3-1) unstable; urgency=medium
 .
   * Imported Upstream version 1.6.3
 + add support for RSpec3 (Closes: #795134)
   * Drop drop-failing-test.patch, applied upstream
Checksums-Sha1:
 d10aa3a0eb8a76fdc212e21509b5195bcf909270 1821 ruby-treetop_1.6.3-1.dsc
 cf1ae3e9fb43831fbddf4f3d14465a858736928f 81082 ruby-treetop_1.6.3.orig.tar.gz
 91dec05fd4608bc9486aa6945a853b7c148d3aeb 4076 
ruby-treetop_1.6.3-1.debian.tar.xz
 32fc8992ffb01d078b0b10c44678112cabe4cf4d 35934 ruby-treetop_1.6.3-1_all.deb
 52384e652c810598bace1e5da9586224c3f3bce8 6292 treetop_1.6.3-1_all.deb
Checksums-Sha256:
 937da098698c09107e91e22647ba9a2b418ccbb3288864831d03545f84f778de 1821 
ruby-treetop_1.6.3-1.dsc
 fa722abb0ad3ef4b398eb1627b4dccb65c005316644d74b8f7214938dfbced35 81082 
ruby-treetop_1.6.3.orig.tar.gz
 9d8a59008bc867191ebdda65a7e98a851c127e5eb33b4c6757421297b141a70c 4076 
ruby-treetop_1.6.3-1.debian.tar.xz
 5e30176c49fd108e587aaf4322

Bug#795344: libmems-1.6-1: not properly linked to its dependencies

[Simon McVittie]

On 13/08/15 10:44, Andreas Tille wrote:
> However, from your mail it seems that there is some issue with libmuscle
> which I do not understand and where I have no idea how to fix.  Could
> you be so kind to give some more detailed hint how this can be fixed and
> why the package is hidden from the transition tracker?

The package is not in the transition trackers *because* of the linking
issue I reported: its dependencies are wrong.

>> dpkg-shlibdeps: warning: symbol _ZN6muscle4QuitEPKcz used by 
>> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
>> none of the libraries
>> dpkg-shlibdeps: warning: symbol _ZNK6genome10gnSequence6subseqEyy used by 
>> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
>> none of the libraries
>> dpkg-shlibdeps: warning: symbol _ZN6muscle8DistFunc8SetCountEj used by 
>> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
>> none of the libraries
>> dpkg-shlibdeps: warning: symbol _ZN6muscle10RefineVertERNS_3MSAERKNS_4TreeEj 
>> used by debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 
>> found in none of the libraries
>> dpkg-shlibdeps: warning: symbol 
>> _ZNK5boost9iostreams18mapped_file_source4dataEv used by 
>> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
>> none of the libraries
>> dpkg-shlibdeps: warning: symbol 
>> _ZN5boost10filesystem4path27m_erase_redundant_separatorEj used by 
>> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
>> none of the libraries

libMems-1.6.so.1.0.0 should have been linked to the libraries it depends
on, something like

gcc -o libMems-1.6.so.1.0.0 something.o someother.o \
-lmuscle -lgenome -lboost-filesystem

(those library names are just guesses and probably wrong, but hopefully
you get the general idea), but in fact it was linked without specifying
the libraries it depends on, more like

gcc -o libMems-1.6.so.1.0.0 something.o someother.o

As a result, the .so does not have the correct DT_NEEDED headers
describing the libraries that it depends on (use "objdump -Tx" to see
those). As a result of that, dpkg-shlibdeps produces those warnings, and
does not generate the dependencies that it should.

It does not appear in the transition trackers because each transition
tracker uses dependencies to find the packages that depend on the
transitioning library. At the moment, libmems-1.6-1 only depends on
libc, libgcc and libstdc++, and there is nothing in its metadata to
indicate that it should be involved in the boost or libgenome transitions.

The solution is something like this in the Makefile.am:

libMems_1_6_la_LIBADD = $(DEPS_LIBS)

You might also need to append $(BOOST_LIBS) or -lboost-filesystem or
something, I don't know how Boost is meant to work. There might also be
additional libraries among the "more warnings" that dpkg-shlibdeps
suppressed. The general principle is to keep adding libraries until
dpkg-shlibdeps stops producing "found in none of the libraries" warnings :-)

If you add -no-undefined to the LDFLAGS, the linker will fail "hard"
(FTBFS) when it encounters missing dependencies, instead of continuing
to link a partially broken library. This flag is usually a good idea
where possible; it can be used for executables and most shared
libraries, but cannot be used for some loadable modules (e.g. Python
extensions) or for circularly dependent libraries.

S

Processed: severity of 795336 is normal, tagging 795336

[Debian Bug Tracking System]

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

> severity 795336 normal
Bug #795336 [src:linux] linux-image-4.0.0-2-amd64: kernel causes mounted usb 
drives to timeout transfers
Severity set to 'normal' from 'grave'
> tags 795336 - lfs
Bug #795336 [src:linux] linux-image-4.0.0-2-amd64: kernel causes mounted usb 
drives to timeout transfers
Removed tag(s) lfs.
> thanks
Stopping processing here.

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

Bug#794627: Downgrading

[Michael Meskes]

severity 794627 important
thanks

I don't think a problem with a package in experimental should have the effect
of a testing removal. Therefore I downgrad this ug. Feel free to upgrade
again, if problem (which does not seem to be easily reproducible) still
persists once the newer gnupg version makes it into unstable/tesing.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at gmail dot com
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

Processed: Downgrading

[Debian Bug Tracking System]

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

> severity 794627 important
Bug #794627 [enigmail] enigmail does not work with gpg 2.1.6
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Processed (with 1 errors): closed by ruby-treetop/1.6.3-1

[Debian Bug Tracking System]

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

> fixed 795121 ruby-treetop/1.6.3-1
Bug #795121 [src:ruby-treetop] ruby-treetop: FTBFS: rspec3 port(?): 
Failure/Error: File.exists?(target_path).should be_false
Marked as fixed in versions ruby-treetop/1.6.3-1.
> unfixed 795134 ruby-treetop/1.6.3-1
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#795121: marked as done (ruby-treetop: FTBFS: rspec3 port(?): Failure/Error: File.exists?(target_path).should be_false)

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 13:34:28 +0200
with message-id <20150813113428.GA3931@spin>
and subject line closed by ruby-treetop/1.6.3-1
has caused the Debian Bug report #795121,
regarding ruby-treetop: FTBFS: rspec3 port(?): Failure/Error: 
File.exists?(target_path).should be_false
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.)


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

Dear Maintainer,

The package fails to build:

Failures:

  1) Treetop::Compiler::GrammarCompiler compilation of a single file to a 
default file name
 Failure/Error: File.exists?(target_path).should be_false
   expected false to respond to `false?` or perhaps you meant `be false` or 
`be_falsey`
 # ./spec/compiler/grammar_compiler_spec.rb:35:in `block (2 levels) in '

..

  3) The 'tt' comand line compiler when processing a single grammar file can 
compile a grammar file
 Failure/Error: system("ruby -S tt #{@test_grammar}").should be_true
   expected true to respond to `true?` or perhaps you meant `be true` or 
`be_truthy`
 # ./spec/compiler/tt_compiler_spec.rb:37:in `block (3 levels) in '

...

428 examples, 15 failures

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-treetop.html

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
fixed 795121 ruby-treetop/1.6.3-1
unfixed 795134 ruby-treetop/1.6.3-1
thanks

This bug has been closed by the upload of ruby-treetop/1.6.3-1.

Cheers,

Cédric



signature.asc
Description: Digital signature
--- End Message ---

Bug#794736: libvigraimpex: library transition is needed when GCC 5 is the default

[Daniel Stender]

We have a SONAME bump happening due to the Vigra 1.10.0 transition [1] which
generally could let spare a "v5" package when the two transitions would be 
combined,
isn't it?

However, I think it's better to adopt what has been already changed for 
1.10.0+dfsg-9ubuntu1
to update Vigra for 15.10 (renaming libvigraimpex5 to libvigraimpexv5 and 
rebuild) - there's
really no need to avoid this.

We have some other serious issues open for Vigra (with the Lenna image set [2] 
and test suite
problems in Mips), so I suggest we do it that way: I'm going to prepare a "v5" 
1.9.0+dfsg-11
for unstable in the next days and check the reverse deps. After that we go for 
a "v5"
1.10.0+dfsg-10 in experimental and check the reverse deps on that, that would 
close the
stdc++6 transition as the next thing to do on Vigra.

Daniel

[1] https://bugs.debian.org/793044 (transition: libvigraimpex)

[2] https://lists.debian.org/debian-devel/2015/08/msg00090.html

-- 
http://www.danielstender.com/blog/
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8

Bug#778180: xemacs21: ftbfs with GCC-5

[Mark Brown]

On Fri, Jul 10, 2015 at 03:57:40PM -0600, Brett Johnson wrote:

> gcc5 changes the semantics of inline function declarations, causing some
> inline functions in xemacs to be considered "extern", and thus cause

In what way does it change the semantics - this seems like a very
surprising and counterintuitive thing to do?


signature.asc
Description: Digital signature

Bug#784041: This bug #784041 seems to have been fixed up-stream quite some time ago, but stillnot updated in the jessie repository

[Robert M. Schmidt]

Hello,
This bug #784041 seems to have been fixed up-stream quite some time ago, 
but is still not updated in the jessie repository. How to trigger the 
update of this package in the jessie repository, please?

Thanks!

Bug#794657: reupload 3.6.0?

[Antonio Terceiro]

On Mon, Aug 10, 2015 at 11:28:08PM +0900, Youhei SASAKI wrote:
> Dear Cédric,
> 
> On Mon, 10 Aug 2015 02:13:15 +0900,
> Cédric Boutillier  wrote:
> >
> > This is affecting packages (build)depending on pry, including
> > cucumber. Since ruby-slop has a unique dependency/build-dependency
> > (pry) and upstream is not ready yet to upgrade to the v4 of ruby-slop
> > (which seems to be a complete rewrite), can we reupload the 3.6.0
> > version, with a 4.2.0+really3.6.0-1 version number in the mean time?
> 
> I need ruby-slop >= version 4 for other project, thus I'll intend to
> package named "ruby-slop3". After upload this package, I'll modify pry
> depends on ruby-slop3.

herm, since pry seems to be the only reverse dependency, I would instead
embed a copy of slop 3 into pry instead of adding a new package. The
last time we added this type of versioned package it took a while to get
rid of it (ruby-rack1.4).

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 779620 3.7~+rc2-1
Bug #779620 [lldb-3.7] lldb-3.7: CommandLine Error: Option 
'enable-objc-arc-opts' registered more than once!
There is no source info for the package 'lldb-3.7' at version '3.7~+rc2-1' with 
architecture ''
Unable to make a source version for version '3.7~+rc2-1'
Marked as fixed in versions 3.7~+rc2-1.
> thanks
Stopping processing here.

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

Bug#793833: Reducing the bug`s severity

[Anton Gladky]

severity 793833 minor
thanks

Hi I am reducing the bug`s severity, because
there is definitely the problem with the buildd,
which had not enough place to build the package.

Give-back should be requested.

Cheers

Anton

Processed: Reducing the bug`s severity

[Debian Bug Tracking System]

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

> severity 793833 minor
Bug #793833 [yade] yade FTBFS on mipsel: No space left on device
Severity set to 'minor' from 'serious'
> thanks
Stopping processing here.

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

Bug#779620: marked as done (lldb-3.7: CommandLine Error: Option 'enable-objc-arc-opts' registered more than once!)

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 12:55:34 + (UTC)
with message-id <2050974631.4162719.1439470534981.javamail.ya...@mail.yahoo.com>
and subject line Fixed in last unstable release
has caused the Debian Bug report #779620,
regarding lldb-3.7: CommandLine Error: Option 'enable-objc-arc-opts' registered 
more than once!
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.)


-- 
779620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lldb-3.7
Version: 1:3.7~svn230892-1
Severity: grave

I tried the new version to see whether the arch detection has been fixed; 
it may have been, but the new version is still unusable:

$ lldb-3.7 /bin/ls
: CommandLine Error: Option 'enable-objc-arc-opts' registered more than 
once!
LLVM ERROR: inconsistency in registered CommandLine options

$ lldb-3.7 
: CommandLine Error: Option 'enable-objc-arc-opts' registered more than 
once!
LLVM ERROR: inconsistency in registered CommandLine options


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages lldb-3.7 depends on:
ii  libc62.19-13
ii  libedit2 3.1-20140620-2
ii  libffi6  3.1-2+b2
ii  libgcc1  1:5-20150205-1
ii  liblldb-3.7  1:3.7~svn230892-1
ii  libllvm3.7   1:3.7~svn230892-1
ii  libstdc++6   4.9.2-10
ii  libtinfo55.9+20140913-1+b1
ii  llvm-3.7-dev 1:3.7~svn227076-1
ii  python   2.7.8-3
ii  python-lldb-3.7  1:3.7~svn227076-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

lldb-3.7 recommends no packages.

lldb-3.7 suggests no packages.

-- no debconf information

-- 
: Ing. Philipp Marek
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com :

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
--- End Message ---
--- Begin Message ---
Hi, according to the source code this seems to be fixed already in the last two 
Debian uploads.

Please confirm the code is working.

cheers,

Gianfranco--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> tags 714686 wontfix sid stretch jessie
Bug #714686 [src:llvm-toolchain-snapshot] llvm-toolchain-snapshot should stay 
in unstable
Added tag(s) jessie, sid, wontfix, and stretch.
> thanks
Stopping processing here.

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

Processed: notfixed 795134 in ruby-treetop/1.6.3-1

[Debian Bug Tracking System]

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

> notfixed 795134 ruby-treetop/1.6.3-1
Bug #795134 {Done: Cédric Boutillier } [src:ruby-rabl-rails] 
ruby-rabl-rails: FTBFS: minitest: invalid option: -f
No longer marked as fixed in versions ruby-treetop/1.6.3-1.
> thanks
Stopping processing here.

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

Bug#779620: closed by Gianfranco Costamagna (Fixed in last unstable release)

[Gianfranco Costamagna]

Can you please open a new issue for this?


thanks,

Gianfranco




Il Giovedì 13 Agosto 2015 15:13, Philipp Marek  ha 
scritto:
> Hi, according to the source code this seems to be fixed already in the last 
> two Debian uploads.
> 
> Please confirm the code is working.
Sorry, it's broken in another way.


  # lldb-3.7 /bin/ls

  (lldb) target create "/bin/ls"
  Current executable set to '/bin/ls' (x86_64).
  (lldb) r
  error: process launch failed: unable to locate lldb-server
  (lldb) c
  error: Process must be launched.
  (lldb) q
  # ls -la /usr/bin/lldb-*
  lrwxrwxrwx 1 root root 24 Aug  3 02:38 /usr/bin/lldb-3.7 -> 
  ../lib/llvm-3.7/bin/lldb
  lrwxrwxrwx 1 root root 27 Aug  3 02:38 /usr/bin/lldb-mi-3.7 -> 
  ../lib/llvm-3.7/bin/lldb-mi
  lrwxrwxrwx 1 root root 31 Aug  3 02:38 /usr/bin/lldb-server-3.7 -> 
  ../lib/llvm-3.7/bin/lldb-server

I guess registering "lldb" via alternatives might help, but that's only 
a workaround...

Bug#778180: xemacs21: ftbfs with GCC-5

[Mark Brown]

tag 778180 - patch
kthxbye

> --- xemacs21-21.4.22.orig/configure.in
> +++ xemacs21-21.4.22/configure.in
> @@ -1941,6 +1941,8 @@ if test "$cflags_specified" = "no"; then
>  CFLAGS="-g -O3 -Wall -Wno-switch -Winline -Wmissing-prototypes"
>  dnl Yuck, bad compares have been worth at least 3 crashes!
>  CFLAGS="$CFLAGS -Wsign-compare"
> +dnl Use old gnu inline semantics because we're too lazy to fix the source
> +CFLAGS="$CFLAGS -fgnu89-inline"
>  dnl XEmacs is known not to be strict-aliasing-safe.
>  case "`gcc -v --help 2>&1`" in
>*-fstrict-aliasing* ) CFLAGS="$CFLAGS -fno-strict-aliasing" ;;

The other thing here is that if we're overriding CFLAGS we should do it
in the packaging, not by editing configure - I've done this locally.


signature.asc
Description: Digital signature

Bug#779620: closed by Gianfranco Costamagna (Fixed in last unstable release)

[Philipp Marek]

> Hi, according to the source code this seems to be fixed already in the last 
> two Debian uploads.
> 
> Please confirm the code is working.
Sorry, it's broken in another way.


  # lldb-3.7 /bin/ls

  (lldb) target create "/bin/ls"
  Current executable set to '/bin/ls' (x86_64).
  (lldb) r
  error: process launch failed: unable to locate lldb-server
  (lldb) c
  error: Process must be launched.
  (lldb) q
  # ls -la /usr/bin/lldb-*
  lrwxrwxrwx 1 root root 24 Aug  3 02:38 /usr/bin/lldb-3.7 -> 
  ../lib/llvm-3.7/bin/lldb
  lrwxrwxrwx 1 root root 27 Aug  3 02:38 /usr/bin/lldb-mi-3.7 -> 
  ../lib/llvm-3.7/bin/lldb-mi
  lrwxrwxrwx 1 root root 31 Aug  3 02:38 /usr/bin/lldb-server-3.7 -> 
  ../lib/llvm-3.7/bin/lldb-server

I guess registering "lldb" via alternatives might help, but that's only 
a workaround...

Bug#795037: marked as done (ruby-filepath: FTBFS: rspec3 port for be_true etc.)

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 13:21:31 +
with message-id 
and subject line Bug#795037: fixed in ruby-filepath 0.6-3
has caused the Debian Bug report #795037,
regarding ruby-filepath: FTBFS: rspec3 port for be_true etc.
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.)


-- 
795037: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-filepath
Version: 0.6-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

Failures:

  1) FilePath#extension? says that  has an extension
 Failure/Error: FilePath.new(path).extension?.should be_true
   expected true to respond to `true?` or perhaps you meant `be true` or 
`be_truthy`
 # ./spec/filepath_spec.rb:185:in `block (4 levels) in '

...

  12) FilePath#each_segment goes through all the segments of an absolute path
  Failure/Error: steps.should have(4).items
  NoMethodError:
undefined method `have' for 
#
  # ./spec/filepath_spec.rb:323:in `block (3 levels) in '

...

222 examples, 52 failures

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-filepath.html

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: ruby-filepath
Source-Version: 0.6-3

We believe that the bug you reported is fixed in the latest version of
ruby-filepath, 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 795...@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-filepath 
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, 13 Aug 2015 15:09:38 +0200
Source: ruby-filepath
Binary: ruby-filepath
Architecture: source all
Version: 0.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-filepath - small library to manipulate paths
Closes: 795037
Changes:
 ruby-filepath (0.6-3) unstable; urgency=medium
 .
   * Team upload
   * Convert specs to RSpec3-compatible syntax (Closes: #795037)
   * Refresh packaging with dh-make-ruby -w
Checksums-Sha1:
 bdeca043812de2dbf2b5695c01e5fc0783a1db00 1684 ruby-filepath_0.6-3.dsc
 65ffbda9698fe1839e3a2af448be081858ddd05a 7156 ruby-filepath_0.6-3.debian.tar.xz
 364d9f79994c9375f1de6bedb5a2a0e2782631af 12600 ruby-filepath_0.6-3_all.deb
Checksums-Sha256:
 567dec3ccb672f0d48c1a7eff2c649edd3cb3e0439ee61350dd6f4f6393a6bb9 1684 
ruby-filepath_0.6-3.dsc
 9f3618a9caaac7e154a7820e6d507f4717ee0bf8e871f3c1891b1b4438bc3985 7156 
ruby-filepath_0.6-3.debian.tar.xz
 9fc2c42ff902a5bf4bbfd998c6224215fd415c54b073a33b47acaa0798395b12 12600 
ruby-filepath_0.6-3_all.deb
Files:
 1fd2364ce56597eedfcf08c9df978de9 1684 ruby optional ruby-filepath_0.6-3.dsc
 1c8d3d40ea962a7d666e351c4fe789a9 7156 ruby optional 
ruby-filepath_0.6-3.debian.tar.xz
 c400050e3a6fd4340f2ac572b945465e 12600 ruby optional 
ruby-filepath_0.6-3_all.deb

-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJVzJikAAoJEImvgrc5zSF6C5EH/3GPm6qGhSHdQHf/YyOUslko
Mm81OcUeyXClwkcY0wCbiNqYzC2zq9AEJXDp3bkQUgxp5LfToACFWa13yJw8yt3B
p0m5R+ePpP6SKIYjEdFVoNt9qyNTQ5iUsR5XnYrqJLC/yX4zkQnlSL2XZyJvGalN
Z8Ij5Q3L0oCrCTapcgtwu7LBvfi2wpwo3v+VYV3SiDHcigt8dZgQ16PHLQPLdOxC
sQwjm6eKoGrySpGFKOB7H0MM02fQ2JnVuPP7c4AuujWXDn4OWLniRcbmG6axaysl
P8Dhrq4ekCkVIHgDdg7FtwbUsR/pfLjOG3eqZQVKiVGnV97HZ2nAXg6FPxmd/5w=
=kD/n
-END PGP SIGNATURE End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> close 794539
Bug #794539 [clang-3.7-doc,llvm-3.7-doc] llvm-3.7-doc and clang-3.7-doc: error 
when trying to install together
Bug #794620 [clang-3.7-doc,llvm-3.7-doc] clang-3.7-doc,llvm-3.7-doc: error when 
trying to install together
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: tagging 321449

[Debian Bug Tracking System]

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

> tags 321449 - sid stretch
Bug #321449 [gcc-snapshot] gcc-snapshot should stay in unstable
Removed tag(s) sid and stretch.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 714686 - sid stretch
Bug #714686 [src:llvm-toolchain-snapshot] llvm-toolchain-snapshot should stay 
in unstable
Removed tag(s) sid and stretch.
> thanks
Stopping processing here.

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

Bug#795344: libmems-1.6-1: not properly linked to its dependencies

[Andreas Tille]

Hi mentors,

I have some problem with automake configuration to link library
symbols properly.

On Thu, Aug 13, 2015 at 11:31:02AM +0100, Simon McVittie wrote:
> On 13/08/15 10:44, Andreas Tille wrote:
> > However, from your mail it seems that there is some issue with libmuscle
> > which I do not understand and where I have no idea how to fix.  Could
> > you be so kind to give some more detailed hint how this can be fixed and
> > why the package is hidden from the transition tracker?
> 
> The package is not in the transition trackers *because* of the linking
> issue I reported: its dependencies are wrong.
> 
> >> dpkg-shlibdeps: warning: symbol _ZN6muscle4QuitEPKcz used by 
> >> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
> >> none of the libraries
> >> dpkg-shlibdeps: warning: symbol _ZNK6genome10gnSequence6subseqEyy used by 
> >> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
> >> none of the libraries
> >> dpkg-shlibdeps: warning: symbol _ZN6muscle8DistFunc8SetCountEj used by 
> >> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
> >> none of the libraries
> >> dpkg-shlibdeps: warning: symbol 
> >> _ZN6muscle10RefineVertERNS_3MSAERKNS_4TreeEj used by 
> >> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
> >> none of the libraries
> >> dpkg-shlibdeps: warning: symbol 
> >> _ZNK5boost9iostreams18mapped_file_source4dataEv used by 
> >> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
> >> none of the libraries
> >> dpkg-shlibdeps: warning: symbol 
> >> _ZN5boost10filesystem4path27m_erase_redundant_separatorEj used by 
> >> debian/libmems-1.6-1/usr/lib/i386-linux-gnu/libMems-1.6.so.1.0.0 found in 
> >> none of the libraries
> 
> libMems-1.6.so.1.0.0 should have been linked to the libraries it depends
> on, something like
> 
> gcc -o libMems-1.6.so.1.0.0 something.o someother.o \
> -lmuscle -lgenome -lboost-filesystem
> 
> (those library names are just guesses and probably wrong, but hopefully
> you get the general idea),

I confirm that the idea is understood.

> but in fact it was linked without specifying
> the libraries it depends on, more like
> 
> gcc -o libMems-1.6.so.1.0.0 something.o someother.o
> 
> As a result, the .so does not have the correct DT_NEEDED headers
> describing the libraries that it depends on (use "objdump -Tx" to see
> those). As a result of that, dpkg-shlibdeps produces those warnings, and
> does not generate the dependencies that it should.
> 
> It does not appear in the transition trackers because each transition
> tracker uses dependencies to find the packages that depend on the
> transitioning library. At the moment, libmems-1.6-1 only depends on
> libc, libgcc and libstdc++, and there is nothing in its metadata to
> indicate that it should be involved in the boost or libgenome transitions.
> 
> The solution is something like this in the Makefile.am:
> 
> libMems_1_6_la_LIBADD = $(DEPS_LIBS)
> 
> You might also need to append $(BOOST_LIBS) or -lboost-filesystem or
> something, I don't know how Boost is meant to work. There might also be
> additional libraries among the "more warnings" that dpkg-shlibdeps
> suppressed. The general principle is to keep adding libraries until
> dpkg-shlibdeps stops producing "found in none of the libraries" warnings :-)

I have tried the following quilt patch


--- a/Makefile.am
+++ b/Makefile.am
@@ -10,5 +10,7 @@ projects/libMems.vcproj
 pkgconfigdir = $(libdir)/pkgconfig
 pkgconfig_DATA = libMems-@GENERIC_API_VERSION@.pc

+libMems_la_LIBADD = $(DEPS_LIBS) @BOOST_FILESYSTEM_LIB@ @BOOST_IOSTREAMS_LIB@ 
@BOOST_SYSTEM_LIB@
+
 SUBDIRS = libMems

--- a/configure.ac
+++ b/configure.ac
@@ -97,6 +97,7 @@ BOOST_IOSTREAMS
 dnl Get location of libGenome Headers
 PKG_CHECK_MODULES(DEPS, libGenome-1.3 >= 1.3.1  libMUSCLE-3.7 >= 1.0.0)
 AC_SUBST(DEPS_CFLAGS)
+AC_SUBST(DEPS_LIBS)

 dnl Check for OpenMP
 #AX_OPENMP()



with no visible change in the build (I also tried the versioned
libMems_1_6_la_LIBADD with the same zero effect).  I suspect that also
libMems-1.6.pc.in might need some love but I have no idea how.
 
> If you add -no-undefined to the LDFLAGS, the linker will fail "hard"
> (FTBFS) when it encounters missing dependencies, instead of continuing
> to link a partially broken library. This flag is usually a good idea
> where possible; it can be used for executables and most shared
> libraries, but cannot be used for some loadable modules (e.g. Python
> extensions) or for circularly dependent libraries.

I'll add this but would like to fix this first that way.
 
Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#795323: [Pkg-pascal-devel] Bug#795323: fpc: FTBFS: Target "linux", package "fpgtk" not found

[Paul Gevers]

On 13-08-15 00:22, Chris West (Faux) wrote:
> The package fails to build:
> 
> ...
> fpcsrc/utils/fpcm/fpcmake -Tall -q 
> /fpc-2.6.4+dfsg/fpcsrc/rtl/morphos/Makefile.fpc
> fpcsrc/utils/fpcm/fpcmake -Tall -q 
> /fpc-2.6.4+dfsg/fpcsrc/rtl/win32/Makefile.fpc
> fpcsrc/utils/fpcm/fpcmake -Tall -q 
> /fpc-2.6.4+dfsg/fpcsrc/utils/fpcmkcfg/Makefile.fpc
> fpcsrc/utils/fpcm/fpcmake -Tall -q 
> /fpc-2.6.4+dfsg/fpcsrc/utils/fpdoc/Makefile.fpc
> fpcsrc/utils/fpcm/fpcmake -Tall -q 
> /fpc-2.6.4+dfsg/fpcsrc/utils/fpdoc/fpde/Makefile.fpc
> Error: Target "linux", package "fpgtk" not found
> debian/rules:198: recipe for target 
> '/fpc-2.6.4+dfsg/fpcsrc/utils/fpdoc/fpde/Makefile' failed

I believe I know how to solve the issue (testing right now). I am still
contemplating the exact implementation in debian/rules as there are some
minor issues with the straight forward solution.

The idea is something like adding this to one of the clean targets:
 # The following packages depend on (at least) fpgtk but were
 # not build in Debian anyways. The make-files target fails to run
 # because fpcmake checks for all Makefile.fpc files and notices
 # that the dependency is not forfilled.
 rm -rf fpcsrc/utils/fpdoc/fpde
 rm -rf fpcsrc/utils/fpmc

And an update of the disable_building_gnome1_and_gtk1.patch to including
removal of fpmc in some win / bsd targets for utils/Makefile.fpc

Paul



signature.asc
Description: OpenPGP digital signature

Bug#795376: valgrind: Fatal error at startup: a function redirection [...] cannot be set up

[Julian Andres Klode]

Package: valgrind
Version: 1:3.10.1-4
Severity: grave

Valgrind does not work on a recent system anymore (which went
through the gcc5 transition).

$ valgrind echo 
==11398== Memcheck, a memory error detector
==11398== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==11398== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==11398== Command: echo
==11398== 

valgrind:  Fatal error at startup: a function redirection
valgrind:  which is mandatory for this platform-tool combination
valgrind:  cannot be set up.  Details of the redirection are:
valgrind:  
valgrind:  A must-be-redirected function
valgrind:  whose name matches the pattern:  strlen
valgrind:  in an object with soname matching:   ld-linux-x86-64.so.2
valgrind:  was not found whilst processing
valgrind:  symbols from the object with soname: ld-linux-x86-64.so.2
valgrind:  
valgrind:  Possible fixes: (1, short term): install glibc's debuginfo
valgrind:  package on this machine.  (2, longer term): ask the packagers
valgrind:  for your Linux distribution to please in future ship a non-
valgrind:  stripped ld.so (or whatever the dynamic linker .so is called)
valgrind:  that exports the above-named function using the standard
valgrind:  calling conventions for this platform.  The package you need
valgrind:  to install for fix (1) is called
valgrind:  
valgrind:On Debian, Ubuntu: libc6-dbg
valgrind:On SuSE, openSuSE, Fedora, RHEL:   glibc-debuginfo
valgrind:  
valgrind:  Cannot continue -- exiting now.  Sorry.



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

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

Versions of packages valgrind depends on:
ii  libc6  2.19-19
ii  libc6-dbg  2.19-19

Versions of packages valgrind recommends:
ii  gdb   7.7.1+dfsg-5
pn  valgrind-dbg  

Versions of packages valgrind suggests:
pn  alleyoop  
pn  kcachegrind   
pn  valgrind-mpi  
pn  valkyrie  

-- no debconf information

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

Be friendly, do not top-post, and follow RFC 1855 "Netiquette".
- If you don't I might ignore you.

Bug#795077: kicad: FTBFS: error: 'itr' was not declared in this scope

[Nick Østergaard]

You can use the cmake option -DKICAD_SKIP_BOOST=ON  to fix this issue.
Make sure this only happens for systems with boost version above 1.54.

2015-08-10 13:03 GMT+02:00 Martin Pitt :
> Package: kicad
> Severity: serious
> Version: 0.20141025+bzr4029-2
>
> kicad fails due to tons of error messages in current sid, e. g.
>
> | In file included from 
> /«BUILDDIR»/kicad-0.20141025+bzr4029/include/boost/polygon/polygon_set_data.hpp:1003:0,
> |  from 
> /«BUILDDIR»/kicad-0.20141025+bzr4029/include/boost/polygon/polygon.hpp:81,
> |  from 
> /«BUILDDIR»/kicad-0.20141025+bzr4029/common/../polygon/polygons_defs.h:9,
> |  from 
> /«BUILDDIR»/kicad-0.20141025+bzr4029/common/../polygon/PolyLine.h:23,
> |  from 
> /«BUILDDIR»/kicad-0.20141025+bzr4029/common/../pcbnew/class_pad.h:37,
> |  from 
> /«BUILDDIR»/kicad-0.20141025+bzr4029/common/footprint_info.cpp:22:
> | 
> /«BUILDDIR»/kicad-0.20141025+bzr4029/include/boost/polygon/polygon_set_concept.hpp:281:91:
>  error: 'itr' was not declared in this scope
> |  for(typename std::list >::iterator itr = 
> polys.begin(); itr != polys.end(); itr = itr_nxt){
> | 
>^
> | 
> /«BUILDDIR»/kicad-0.20141025+bzr4029/include/boost/polygon/polygon_set_concept.hpp:281:117:
>  error: 'itr_nxt' was not declared in this scope
> |  for(typename std::list >::iterator itr = 
> polys.begin(); itr != polys.end(); itr = itr_nxt){
>   
>^
>
> Apparently this needs to be adjusted to the current boost?
>
> Thanks,
>
> Martin
>
> --
> Martin Pitt| http://www.piware.de
> Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Bug#725768: tkcvs: tk depends

[Uwe Storbeck]

On Apr 29, Matt Taggart wrote:
> I'd also be happy to use something not based on '90's technology, but
> I have yet to find anything that works as well. If people have
> suggestions I would love to hear them.

There are not many. With the same functionality there's only
kdiff3 and maybe meld. But they are much more heavyweight. One
of the advantages of tkdiff is that it's rather lightweight and
has not a lot of dependencies. Unfortunately the bundling in the
tkcvs package introduces unnecessary dependencies and reduces
this advantage.

There where plans to split this package (see the last mail in
bug #664084), but this was more than 3 years ago and nothing has
happened since then.

If someone starts to work on this package please consider to
split it up into separate packages (tkdiff, tkcvs and tkdirdiff)
and maybe drop either the tkdirdiff part or the dirdiff package
(see bugs #664084 and #699146).

Regards

Uwe

Bug#795344: libmems-1.6-1: not properly linked to its dependencies

[Simon McVittie]

On 13/08/15 15:06, Andreas Tille wrote:
> +libMems_la_LIBADD = $(DEPS_LIBS) @BOOST_FILESYSTEM_LIB@ 
> @BOOST_IOSTREAMS_LIB@ @BOOST_SYSTEM_LIB@
> +
>  SUBDIRS = libMems

Move this from /Makefile.am into /libMems/Makefile.am, where libMems.la
is built and the rest of the libMems_la_WHATEVER variables appear.

S

Processed: add patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #777977 [src:libwfut] libwfut: ftbfs with GCC-5
Added tag(s) patch.

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

Bug#777977: add patch

[Matthias Klose]

Control: tags -1 + patch

I didn't rename the library package because the package doesn't have any reverse
dependencies.

  * Update symbols file for GCC 5.

diff -Nru libwfut-0.2.3/debian/libwfut-0.2-1.symbols 
libwfut-0.2.3/debian/libwfut-0.2-1.symbols
--- libwfut-0.2.3/debian/libwfut-0.2-1.symbols  2014-10-21 21:06:08.0 
+0200
+++ libwfut-0.2.3/debian/libwfut-0.2-1.symbols  2015-08-13 16:49:14.0 
+0200
@@ -1,86 +1,136 @@
+# SymbolsHelper-Confirmed: 0.2.3 amd64 arm64 armhf i386 powerpc ppc64el
 libwfut-0.2.so.1 libwfut-0.2-1 #MINVER#
- _ZN13TiXmlDocumentD0Ev@Base 0.2.2
- _ZN13TiXmlDocumentD1Ev@Base 0.2.2
- _ZN13TiXmlDocumentD2Ev@Base 0.2.2
- _ZN16TiXmlDeclarationD0Ev@Base 0.2.2
- _ZN16TiXmlDeclarationD1Ev@Base 0.2.2
- _ZN16TiXmlDeclarationD2Ev@Base 0.2.2
+ _ZN13TiXmlDocumentD0Ev@Base 0.2.3
+ _ZN13TiXmlDocumentD1Ev@Base 0.2.3
+ _ZN13TiXmlDocumentD2Ev@Base 0.2.3
+#MISSING: 0.2.3# (arch=i386)_ZN16TiXmlDeclarationD0Ev@Base 0.2.3
+#MISSING: 0.2.3# (arch=i386)_ZN16TiXmlDeclarationD1Ev@Base 0.2.3
+#MISSING: 0.2.3# (arch=i386)_ZN16TiXmlDeclarationD2Ev@Base 0.2.3
  _ZN4WFUT10DataStructD1Ev@Base 0.2.3
  _ZN4WFUT10DataStructD2Ev@Base 0.2.3
- _ZN4WFUT10WFUTClient10updateFileERKNS_10FileObjectERKSsS5_@Base 0.2.2
- _ZN4WFUT10WFUTClient11getFileListERKSsRNS_15ChannelFileListE@Base 0.2.2
- _ZN4WFUT10WFUTClient12getLocalListERKSsRNS_15ChannelFileListE@Base 0.2.2
- _ZN4WFUT10WFUTClient13abortDownloadERKSs@Base 0.2.2
- 
_ZN4WFUT10WFUTClient13getMirrorListERKSsRSt6vectorINS_12MirrorObjectESaIS4_EE@Base
 0.2.2
- _ZN4WFUT10WFUTClient13saveLocalListERKNS_15ChannelFileListERKSs@Base 0.2.2
- _ZN4WFUT10WFUTClient13updateChannelERKNS_15ChannelFileListERKSsS5_@Base 0.2.2
- 
_ZN4WFUT10WFUTClient14getChannelListERKSsRSt4listINS_13ChannelObjectESaIS4_EE@Base
 0.2.2
- 
_ZN4WFUT10WFUTClient16calculateUpdatesERKNS_15ChannelFileListES3_S3_RS1_RKSs@Base
 0.2.2
- _ZN4WFUT10WFUTClient16onDownloadFailedERKSsS2_S2_@Base 0.2.2
- _ZN4WFUT10WFUTClient18onDownloadCompleteERKSsS2_@Base 0.2.2
- _ZN4WFUT10WFUTClient4initEv@Base 0.2.2
- _ZN4WFUT10WFUTClient4pollEv@Base 0.2.2
- _ZN4WFUT10WFUTClient8abortAllEv@Base 0.2.2
- _ZN4WFUT10WFUTClient8shutdownEv@Base 0.2.2
- _ZN4WFUT11os_dir_walkERKSsRKSt4listISsSaISsEERS4_@Base 0.2.2
+ 
_ZN4WFUT10WFUTClient10updateFileERKNS_10FileObjectERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESB_@Base
 0.2.3
+#MISSING: 0.2.3# 
(arch=i386)_ZN4WFUT10WFUTClient10updateFileERKNS_10FileObjectERKSsS5_@Base 0.2.3
+ 
_ZN4WFUT10WFUTClient11getFileListERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERNS_15ChannelFileListE@Base
 0.2.3
+#MISSING: 0.2.3# 
(arch=i386)_ZN4WFUT10WFUTClient11getFileListERKSsRNS_15ChannelFileListE@Base 
0.2.3
+ 
_ZN4WFUT10WFUTClient12getLocalListERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERNS_15ChannelFileListE@Base
 0.2.3
+#MISSING: 0.2.3# 
(arch=i386)_ZN4WFUT10WFUTClient12getLocalListERKSsRNS_15ChannelFileListE@Base 
0.2.3
+ 
_ZN4WFUT10WFUTClient13abortDownloadERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 0.2.3
+#MISSING: 0.2.3# (arch=i386)_ZN4WFUT10WFUTClient13abortDownloadERKSs@Base 0.2.3
+ 
_ZN4WFUT10WFUTClient13getMirrorListERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorINS_12MirrorObjectESaISA_EE@Base
 0.2.3
+#MISSING: 0.2.3# 
(arch=i386)_ZN4WFUT10WFUTClient13getMirrorListERKSsRSt6vectorINS_12MirrorObjectESaIS4_EE@Base
 0.2.3
+ 
_ZN4WFUT10WFUTClient13saveLocalListERKNS_15ChannelFileListERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 0.2.3
+#MISSING: 0.2.3# 
(arch=i386)_ZN4WFUT10WFUTClient13saveLocalListERKNS_15ChannelFileListERKSs@Base 
0.2.3
+ 
_ZN4WFUT10WFUTClient13updateChannelERKNS_15ChannelFileListERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESB_@Base
 0.2.3
+#MISSING: 0.2.3# 
(arch=i386)_ZN4WFUT10WFUTClient13updateChannelERKNS_15ChannelFileListERKSsS5_@Base
 0.2.3
+ 
_ZN4WFUT10WFUTClient14getChannelListERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERNS1_4listINS_13ChannelObjectESaISA_EEE@Base
 0.2.3
+#MISSING: 0.2.3# 
(arch=i386)_ZN4WFUT10WFUTClient14getChannelListERKSsRSt4listINS_13ChannelObjectESaIS4_EE@Base
 0.2.3
+ 
_ZN4WFUT10WFUTClient16calculateUpdatesERKNS_15ChannelFileListES3_S3_RS1_RKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 0.2.3
+#MISSING: 0.2.3# 
(arch=i386)_ZN4WFUT10WFUTClient16calculateUpdatesERKNS_15ChannelFileListES3_S3_RS1_RKSs@Base
 0.2.3
+ 
_ZN4WFUT10WFUTClient16onDownloadFailedERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_S8_@Base
 0.2.3
+#MISSING: 0.2.3# 
(arch=i386)_ZN4WFUT10WFUTClient16onDownloadFailedERKSsS2_S2_@Base 0.2.3
+ 
_ZN4WFUT10WFUTClient18onDownloadCompleteERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_@Base
 0.2.3
+#MISSING: 0.2.3# 
(arch=i386)_ZN4WFUT10WFUTClient18onDownloadCompleteERKSsS2_@Base 0.2.3
+ _ZN4WFUT10WFUTClient4initEv@Base 0.2.3
+ _ZN4WFUT10WFUTClient4pollEv@Base 0.2.3
+ _ZN4WFUT10WFUTClient8abortAllEv@Base 0.2.3
+ _ZN4WFUT10WFUTClient8shutdownEv@Base 0.2.3
+ 
_ZN4WFUT11os_dir_walkERKNSt7__cxx1112basic

Bug#778180: xemacs21: ftbfs with GCC-5

[Martin Michlmayr]

* Mark Brown  [2015-08-13 12:51]:
> > gcc5 changes the semantics of inline function declarations, causing some
> > inline functions in xemacs to be considered "extern", and thus cause
> 
> In what way does it change the semantics - this seems like a very
> surprising and counterintuitive thing to do?

Basically, GCC 5 changed the default from GNU89 inline semantics to
C99 inline semantics.

You can find more background here:
https://gcc.gnu.org/gcc-5/porting_to.html
see section "Different semantics for inline functions"

-- 
Martin Michlmayr
Linux for HP Helion, Hewlett-Packard

Bug#795388: youtube-dl wont download a video due to out of date

[Gareth Owen]

Package: youtube-dl
Version: current
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

youtube-dl -x https://www.youtube.com/watch?v=bZh7nRw6gl8

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 ??

   * What was the outcome of this action?

Failed with error

   * What outcome did you expect instead?

Video to download.

Using the latest version from the youtube-dl website works and upstream dev 
advised debian package was out of date.

*** End of the template - remove these template lines ***


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

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

Bug#778180: xemacs21: ftbfs with GCC-5

[Brett Johnson]

On 08/13/2015 05:51 AM, Mark Brown wrote:
> On Fri, Jul 10, 2015 at 03:57:40PM -0600, Brett Johnson wrote:
> 
>> gcc5 changes the semantics of inline function declarations, causing some
>> inline functions in xemacs to be considered "extern", and thus cause
> 
> In what way does it change the semantics - this seems like a very
> surprising and counterintuitive thing to do?

GCC5 now defaults to using the C99 standard, instead of C89.

A summary of the changes is given in [1]. Basically in this case, the
old "inline" definition is roughly equivalent to a new "extern inline"
definition, except that once you declare it "extern", you may now not
redefine it in a different TU.

I agree that it would be better to make the change in the packaging,
rather than in configure.in. If you've already done this, would you
mind submitting a patch?

[1] https://gcc.gnu.org/gcc-5/porting_to.html
-- 
Brett Johnson 
"We don't see things as they are, we see them as we are."
 ~~ Anais Nin

Bug#778180: xemacs21: ftbfs with GCC-5

[Mark Brown]

On Thu, Aug 13, 2015 at 11:33:36AM -0400, Martin Michlmayr wrote:
> * Mark Brown  [2015-08-13 12:51]:
> > > gcc5 changes the semantics of inline function declarations, causing some
> > > inline functions in xemacs to be considered "extern", and thus cause

> > In what way does it change the semantics - this seems like a very
> > surprising and counterintuitive thing to do?

> Basically, GCC 5 changed the default from GNU89 inline semantics to
> C99 inline semantics.

> You can find more background here:
> https://gcc.gnu.org/gcc-5/porting_to.html
> see section "Different semantics for inline functions"

That doesn't seem to correspond to what is happening, AFAICT the
relevant things are static inline and this claims to affect only extern
inline functions.


signature.asc
Description: Digital signature

Bug#795389: fedmsg: FTBFS: tests failures

[Dmitry Shachnev]

Source: fedmsg
Version: 0.9.3-1
Severity: serious
Justification: fails to build from source

The new dh-python automatically runs tests with nose if python-nose
is present in build-dependencies.

Unfortunately some of the tests fail during fedmsg build, like:

  ==
  ERROR: test_config_basic (fedmsg.tests.test_commands.TestCommands)
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
  return func(*args, **keywargs)
File 
"/tmp/buildd/fedmsg-0.9.3/.pybuild/pythonX.Y_2.7/build/fedmsg/tests/test_commands.py",
 line 195, in test_config_basic
  config_command()
File 
"/tmp/buildd/fedmsg-0.9.3/.pybuild/pythonX.Y_2.7/build/fedmsg/commands/config.py",
 line 90, in config
  disable_defaults=args.disable_defaults,
File 
"/tmp/buildd/fedmsg-0.9.3/.pybuild/pythonX.Y_2.7/build/fedmsg/config.py", line 
160, in load_config
  raise ValueError("No config value 'endpoints' found.")
  ValueError: No config value 'endpoints' found.

The full build log can be found at:
http://mitya57.me/builds/fedmsg_0.9.3-1_amd64.build

--
Dmitry Shachnev

signature.asc
Description: OpenPGP digital signature

Bug#791803: marked as done (abook: fails to install: abook.postinst: update-menus: not found)

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 15:50:02 +
with message-id 
and subject line Bug#791803: fixed in abook 0.6.0~pre2-5
has caused the Debian Bug report #791803,
regarding abook: fails to install: abook.postinst: update-menus: not found
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.)


-- 
791803: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: abook
Version: 0.6.0~pre2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package abook.
  (Reading database ... 
(Reading database ... 7475 files and directories currently installed.)
  Preparing to unpack .../abook_0.6.0~pre2-4_amd64.deb ...
  Unpacking abook (0.6.0~pre2-4) ...
  Setting up abook (0.6.0~pre2-4) ...
  /var/lib/dpkg/info/abook.postinst: 58: /var/lib/dpkg/info/abook.postinst: 
update-menus: not found
  dpkg: error processing package abook (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   abook
 

cheers,

Andreas


abook_0.6.0~pre2-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: abook
Source-Version: 0.6.0~pre2-5

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

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

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

Debian distribution maintenance software
pp.
Denis Briand  (supplier of updated abook 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, 13 Aug 2015 16:48:16 +0200
Source: abook
Binary: abook
Architecture: source amd64
Version: 0.6.0~pre2-5
Distribution: unstable
Urgency: low
Maintainer: Rhonda D'Vine 
Changed-By: Denis Briand 
Description:
 abook  - text-based ncurses address book application
Closes: 791612 791803
Changes:
 abook (0.6.0~pre2-5) unstable; urgency=low
 .
   * fix error into debian/postinst file (Closes: #791803).
 Thanks to Salvatore Bonaccorso.
   * Switch source package to debhelper.
   * Fix broken Vcs-git link (Closes: #791612)
Checksums-Sha1:
 10e550ecffdd3af05f0bf18d1827526aa6aa717a 1609 abook_0.6.0~pre2-5.dsc
 78c2c7354cb6132e43ad5dac0d0a4f1b9de50103 13788 abook_0.6.0~pre2-5.debian.tar.xz
 4e4f7d0d1af079b072ff8b52dab4dbfa8c666c83 78120 abook_0.6.0~pre2-5_amd64.deb
Checksums-Sha256:
 662fb54b1b2e6761ffc1c98751b3832b8c4530181229cb6cba69f8884e9bdaca 1609 
abook_0.6.0~pre2-5.dsc
 35863e3af8a319c5f36849d3c415e1e727b4292627116b88b53fd8801c0ba927 13788 
abook_0.6.0~pre2-5.debian.tar.xz
 4a5c3b19f6cfa72b3d2a2c91c383b8d827845992e8f95611539c466688a70c50 78120 
abook_0.6.0~pre2-5_amd64.deb
Files:
 d2e085b17adfa4919590e891c83bccf8 1609 mail optional abook_0.6.0~pre2-5.dsc
 39873a54241495c33e219ddc89e7df7b 13788 mail optional 
abook_0.6.0~pre2-5.debian.tar.xz
 02bb88471463802c9aa724eef8d5cac0 78120 mail optional 
abook_0.6.0~pre2-5_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJVzLAGAAoJEDH85+fdB5RhJmMIAKGxU9bUiXmxGoujr9vvYpX5
Fe8eag2nxjpTDdkeVWwWV2jyNyiMNmxnzLuJ26sGbickRT0V83a4l2+PgjFt0g6w
eecVl+Nwb50J1pvO6ABOcg6Jusog8RaRDHMBnl9BtNc1qj1d4jlvX08YtwgQh7eq
3sSblXDi7VHCOwAaLS1+UqhOVIJCbGA4+VfSzrj24Ui0euUFcjMWDb3EwLYAujjQ
dsYTIOcGkm6FnW3XMZOOXZs8esbTUgQOSWgyZD5tC8DauPmL/fC4jcF1s/kX3Nje
FXEEpGRqrbP0PVUiGRcj94IYSvU2LfVrxIGmR/Ak9duiawS8fUg8ZVVy55/Uuf0=
=LoP3
-END PGP SIGNATURE End Message ---

Processed: vlkdsvkljsd

[Debian Bug Tracking System]

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

> tag 778180 - patch
Bug #778180 [src:xemacs21] xemacs21: ftbfs with GCC-5
Removed tag(s) patch.
>
End of message, stopping processing here.

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

Bug#778180: xemacs21: ftbfs with GCC-5

[Mark Brown]

On Thu, Aug 13, 2015 at 09:39:09AM -0600, Brett Johnson wrote:

> I agree that it would be better to make the change in the packaging,
> rather than in configure.in. If you've already done this, would you
> mind submitting a patch?

Who would I submit a patch for the packaging to?!


signature.asc
Description: Digital signature

Bug#795393: celery: FTBFS: typos in method calls

[Dmitry Shachnev]

Source: celery
Version: 3.1.18-1
Severity: serious
Justification: fails to build from source

celery FTBFS in current sid:

  ==
  ERROR: test_on_chord_part_return 
(celery.tests.backends.test_redis.test_RedisBackend)
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
  return func(*args, **keywargs)
File "/tmp/buildd/celery-3.1.18/celery/tests/backends/test_redis.py", line 
254, in test_on_chord_part_return
  b.client.expire.assert_called_witeh(gkey, 86400)
File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 721, in 
__getattr__
  raise AttributeError(name)
  AttributeError: assert_called_witeh

  ==
  ERROR: test_send (celery.tests.utils.test_mail.test_Mailer)
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
  return func(*args, **keywargs)
File "/tmp/buildd/celery-3.1.18/celery/tests/utils/test_mail.py", line 49, 
in test_send
  client.sendmail.assert_called_With(msg.sender, msg.to, str(msg))
File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 721, in 
__getattr__
  raise AttributeError(name)
  AttributeError: assert_called_With

  --
  Ran 1693 tests in 32.293s

  FAILED (errors=2, skipped=44)
  debian/rules:26: recipe for target 'override_dh_auto_test' failed

These look like typos in method name (assert_called_with).

The full build log can be found at:
http://mitya57.me/builds/celery_3.1.18-1_amd64.build

--
Dmitry Shachnev

Bug#795391: fedmsg: FTBFS: tests failures

[Dmitry Shachnev]

Source: fedmsg
Version: 0.9.3-1
Severity: serious
Justification: fails to build from source

The new dh-python automatically runs tests with nose if python-nose
is present in build-dependencies.

Unfortunately some of the tests fail during fedmsg build, like:

  ==
  ERROR: test_config_basic (fedmsg.tests.test_commands.TestCommands)
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
  return func(*args, **keywargs)
File 
"/tmp/buildd/fedmsg-0.9.3/.pybuild/pythonX.Y_2.7/build/fedmsg/tests/test_commands.py",
 line 195, in test_config_basic
  config_command()
File 
"/tmp/buildd/fedmsg-0.9.3/.pybuild/pythonX.Y_2.7/build/fedmsg/commands/config.py",
 line 90, in config
  disable_defaults=args.disable_defaults,
File 
"/tmp/buildd/fedmsg-0.9.3/.pybuild/pythonX.Y_2.7/build/fedmsg/config.py", line 
160, in load_config
  raise ValueError("No config value 'endpoints' found.")
  ValueError: No config value 'endpoints' found.

The full build log can be found at:
http://mitya57.me/builds/fedmsg_0.9.3-1_amd64.build

--
Dmitry Shachnev

Processed: merging duplicate bugs

[Debian Bug Tracking System]

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

> # sorry, duplicate bug
> merge 795389 795391
Bug #795389 [src:fedmsg] fedmsg: FTBFS: tests failures
Bug #795391 [src:fedmsg] fedmsg: FTBFS: tests failures
Merged 795389 795391
> thanks
Stopping processing here.

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

Bug#768761: marked as done (bustle: FTBFS in jessie: build-dependency not installable: libghc-glade-dev)

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 17:28:32 +0200
with message-id <20150813172832.48d03c5c@sven.bartscher>
and subject line Dependency on libghc-glade-dev- gone
has caused the Debian Bug report #768761,
regarding bustle: FTBFS in jessie: build-dependency not installable: 
libghc-glade-dev
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.)


-- 
768761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bustle
Version: 0.4.2-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> ┌──┐
> │ Install bustle 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-bustle-dummy : Depends: libghc-glade-dev but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/11/08/bustle_0.4.2-1_jessie.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 ---
Greetings,

The build-dependency on libghc-glade-dev has been removed a long time
ago and bustle doesn't have any out-of-dates in unstable, so I guess
this is actually resolved.

Regards
Sven


pgpIKoh_mOSlv.pgp
Description: Digitale Signatur von OpenPGP
--- End Message ---

Bug#795344: libmems-1.6-1: not properly linked to its dependencies

[Andreas Tille]

On Thu, Aug 13, 2015 at 03:40:21PM +0100, Simon McVittie wrote:
> On 13/08/15 15:06, Andreas Tille wrote:
> > +libMems_la_LIBADD = $(DEPS_LIBS) @BOOST_FILESYSTEM_LIB@ 
> > @BOOST_IOSTREAMS_LIB@ @BOOST_SYSTEM_LIB@
> > +
> >  SUBDIRS = libMems
> 
> Move this from /Makefile.am into /libMems/Makefile.am, where libMems.la
> is built and the rest of the libMems_la_WHATEVER variables appear.

I confirm that this at least has some effect - unfortunately not the wanted
one sinde the 

@BOOST_FILESYSTEM_LIB@ @BOOST_IOSTREAMS_LIB@ @BOOST_SYSTEM_LIB@

placeholders remain unresolved and the $(DEPS_LIBS) variable remains
empty. :_(

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#778180: xemacs21: ftbfs with GCC-5

[Brett Johnson]

On 08/13/2015 09:51 AM, Mark Brown wrote:
> Who would I submit a patch for the packaging to?!

Lol. Sorry, I didn't notice you were the maintainer ;)
-- 
Brett Johnson 

Bug#795119: marked as done (ruby-stomp: FTBFS: `method_missing': undefined method `its' for #

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 16:20:38 +
with message-id 
and subject line Bug#795119: fixed in ruby-stomp 1.3.4-2
has caused the Debian Bug report #795119,
regarding ruby-stomp: FTBFS: `method_missing': undefined method `its' for 
#http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-stomp
Version: 1.3.4-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build in a very similar way to 
https://bugs.debian.org/794133

┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/ruby-stomp-1.3.4/debian/ruby-stomp/usr/lib/ruby/vendor_ruby:. ruby2.1 
debian/ruby-tests.rb
/usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in `method_missing': 
undefined method `its' for # (NoMethodError)
from /ruby-stomp-1.3.4/spec/client_spec.rb:53:in `block (3 levels) in 
'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in 
`block in define_example_group_method'
from /ruby-stomp-1.3.4/spec/client_spec.rb:50:in `block (2 levels) in 
'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in 
`block in define_example_group_method'
from /ruby-stomp-1.3.4/spec/client_spec.rb:38:in `block in '
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in 
`block in define_example_group_method'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in 
expose_example_group_alias'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2 
levels) in expose_example_group_alias_globally'
from /ruby-stomp-1.3.4/spec/client_spec.rb:7:in `'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from debian/ruby-tests.rb:2:in `block in '
from debian/ruby-tests.rb:2:in `each'
from debian/ruby-tests.rb:2:in `'
ERROR: Test "ruby2.1" failed. Exiting.

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-stomp.html

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: ruby-stomp
Source-Version: 1.3.4-2

We believe that the bug you reported is fixed in the latest version of
ruby-stomp, 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 795...@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-stomp 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, 13 Aug 2015 18:10:20 +0200
Source: ruby-stomp
Binary: ruby-stomp
Architecture: source all
Version: 1.3.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-stomp - Ruby client for the stomp messaging protocol
Closes: 795119
Changes:
 ruby-stomp (1.3.4-2) unstable; urgency=medium
 .
   * Team upload
   * Add patches for basic RSpec3 support for the test suite (Closes: #795119)
 and build-depend on ruby-rspec-its
   * Require 'rspec/autorun' to actually run the tests
   * Refresh packaging with dh-make-ruby -w
Checksums-Sha1:
 7a9cf9448d302036cd4a6a958f2f332dfd65fc24 1749 ruby-stomp_1.3.4-2.dsc
 2683063dbb97310ddc619ea553f087a3d3d19398 5600 ruby-stomp_1.3.4-2.debian.tar.xz
 9bdfd

Bug#795376: marked as done (valgrind: Fatal error at startup: a function redirection [...] cannot be set up)

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 18:30:42 +0200
with message-id <20150813163042.GA17900@jak-x230>
and subject line Re: Bug#795376: valgrind: Fatal error at startup: a function 
redirection [...] cannot be set up
has caused the Debian Bug report #795376,
regarding valgrind: Fatal error at startup: a function redirection [...] cannot 
be set up
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.)


-- 
795376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: valgrind
Version: 1:3.10.1-4
Severity: grave

Valgrind does not work on a recent system anymore (which went
through the gcc5 transition).

$ valgrind echo 
==11398== Memcheck, a memory error detector
==11398== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==11398== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==11398== Command: echo
==11398== 

valgrind:  Fatal error at startup: a function redirection
valgrind:  which is mandatory for this platform-tool combination
valgrind:  cannot be set up.  Details of the redirection are:
valgrind:  
valgrind:  A must-be-redirected function
valgrind:  whose name matches the pattern:  strlen
valgrind:  in an object with soname matching:   ld-linux-x86-64.so.2
valgrind:  was not found whilst processing
valgrind:  symbols from the object with soname: ld-linux-x86-64.so.2
valgrind:  
valgrind:  Possible fixes: (1, short term): install glibc's debuginfo
valgrind:  package on this machine.  (2, longer term): ask the packagers
valgrind:  for your Linux distribution to please in future ship a non-
valgrind:  stripped ld.so (or whatever the dynamic linker .so is called)
valgrind:  that exports the above-named function using the standard
valgrind:  calling conventions for this platform.  The package you need
valgrind:  to install for fix (1) is called
valgrind:  
valgrind:On Debian, Ubuntu: libc6-dbg
valgrind:On SuSE, openSuSE, Fedora, RHEL:   glibc-debuginfo
valgrind:  
valgrind:  Cannot continue -- exiting now.  Sorry.



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

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

Versions of packages valgrind depends on:
ii  libc6  2.19-19
ii  libc6-dbg  2.19-19

Versions of packages valgrind recommends:
ii  gdb   7.7.1+dfsg-5
pn  valgrind-dbg  

Versions of packages valgrind suggests:
pn  alleyoop  
pn  kcachegrind   
pn  valgrind-mpi  
pn  valkyrie  

-- no debconf information

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

Be friendly, do not top-post, and follow RFC 1855 "Netiquette".
- If you don't I might ignore you.
--- End Message ---
--- Begin Message ---
On Thu, Aug 13, 2015 at 04:11:54PM +0200, Julian Andres Klode wrote:
> Package: valgrind
> Version: 1:3.10.1-4
> Severity: grave
> 
> Valgrind does not work on a recent system anymore (which went
> through the gcc5 transition).

Nevermind, this was caused by merging /lib into /usr/lib (and
/bin into /usr/bin) and stuff by the usrmerge package that is
in development.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

Be friendly, do not top-post, and follow RFC 1855 "Netiquette".
- If you don't I might ignore you.--- End Message ---

Processed: [bts-link] source package libcatalyst-plugin-email-perl

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package 
> libcatalyst-plugin-email-perl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #748849 (http://bugs.debian.org/748849)
> # Bug title: libcatalyst-plugin-email-perl: FTBFS due to removal of 
> libemail-send-perl
> #  * http://rt.cpan.org/Public/Bug/Display.html?id=86843
> #  * remote status changed: open -> resolved
> #  * closed upstream
> tags 748849 + fixed-upstream
Bug #748849 [libcatalyst-plugin-email-perl] libcatalyst-plugin-email-perl: 
FTBFS due to removal of libemail-send-perl
Added tag(s) fixed-upstream.
> usertags 748849 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 748849 + status-resolved
There were no usertags set.
Usertags are now: status-resolved.
> thanks
Stopping processing here.

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

Bug#795119: marked as done (ruby-stomp: FTBFS: `method_missing': undefined method `its' for #

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 17:05:38 +
with message-id 
and subject line Bug#795119: fixed in ruby-orm-adapter 0.5.0-2
has caused the Debian Bug report #795119,
regarding ruby-stomp: FTBFS: `method_missing': undefined method `its' for 
#http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-stomp
Version: 1.3.4-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build in a very similar way to 
https://bugs.debian.org/794133

┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/ruby-stomp-1.3.4/debian/ruby-stomp/usr/lib/ruby/vendor_ruby:. ruby2.1 
debian/ruby-tests.rb
/usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in `method_missing': 
undefined method `its' for # (NoMethodError)
from /ruby-stomp-1.3.4/spec/client_spec.rb:53:in `block (3 levels) in 
'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in 
`block in define_example_group_method'
from /ruby-stomp-1.3.4/spec/client_spec.rb:50:in `block (2 levels) in 
'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in 
`block in define_example_group_method'
from /ruby-stomp-1.3.4/spec/client_spec.rb:38:in `block in '
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in 
`block in define_example_group_method'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in 
expose_example_group_alias'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2 
levels) in expose_example_group_alias_globally'
from /ruby-stomp-1.3.4/spec/client_spec.rb:7:in `'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from debian/ruby-tests.rb:2:in `block in '
from debian/ruby-tests.rb:2:in `each'
from debian/ruby-tests.rb:2:in `'
ERROR: Test "ruby2.1" failed. Exiting.

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-stomp.html

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: ruby-orm-adapter
Source-Version: 0.5.0-2

We believe that the bug you reported is fixed in the latest version of
ruby-orm-adapter, 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 795...@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-orm-adapter 
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, 13 Aug 2015 18:45:22 +0200
Source: ruby-orm-adapter
Binary: ruby-orm-adapter
Architecture: source all
Version: 0.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-orm-adapter - single point of entry for using basic features of ruby ORMs
Closes: 795119
Changes:
 ruby-orm-adapter (0.5.0-2) unstable; urgency=medium
 .
   * Team upload
   * Refresh packaging with 'dh-make-ruby -w'
   * Build-depend on ruby-rspec-its (Closes: #795119)
   * Add RSpec3 support
Checksums-Sha1:
 edb06efed1ee738a2a01069a207190f0e03cd12b 1752 ruby-orm-adapter_0.5.0-2.dsc
 25f43d24daf7f61cc877af469f0e9652faa561d8 2860 
ruby-orm-adapter_0.5.0-2.debian.tar.xz
 acd3cb888f6e8a51c0e80d

Processed: Pending

[Debian Bug Tracking System]

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

> tags 791054 +pending
Bug #791054 [src:gmsh] gmsh: library transition may be needed when GCC 5 is the 
default
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#794736: libvigraimpex: library transition is needed when GCC 5 is the default

[Andreas Metzler]

On 2015-08-13 Daniel Stender  wrote:
> We have a SONAME bump happening due to the Vigra 1.10.0 transition
> [1] which generally could let spare a "v5" package when the two
> transitions would be combined, isn't it?

> However, I think it's better to adopt what has been already changed
> for 1.10.0+dfsg-9ubuntu1 to update Vigra for 15.10 (renaming
> libvigraimpex5 to libvigraimpexv5 and rebuild) - there's really no
> need to avoid this.

I think that  is sensible., too.

> We have some other serious issues open for Vigra (with the Lenna
> image set [2] and test suite problems in Mips), so I suggest we do
> it that way: I'm going to prepare a "v5" 1.9.0+dfsg-11 for unstable
> in the next days and check the reverse deps. After that we go for a
> "v5" 1.10.0+dfsg-10 in experimental and check the reverse deps on
> that, that would close the stdc++6 transition as the next thing to
> do on Vigra.
[...]

I would suggest to make a "v5" for /experimental/ ASAP to minimize
delay due to new processing.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#794736: libvigraimpex: library transition is needed when GCC 5 is the default

[Daniel Stender]

On 13.08.2015 19:31, Andreas Metzler wrote:
>> We have some other serious issues open for Vigra (with the Lenna
>> image set [2] and test suite problems in Mips), so I suggest we do
>> it that way: I'm going to prepare a "v5" 1.9.0+dfsg-11 for unstable
>> in the next days and check the reverse deps. After that we go for a
>> "v5" 1.10.0+dfsg-10 in experimental and check the reverse deps on
>> that, that would close the stdc++6 transition as the next thing to
>> do on Vigra.
> [...]
> 
> I would suggest to make a "v5" for /experimental/ ASAP to minimize
> delay due to new processing.
> 
> cu Andreas

Yes, o.k, all right, I'll have that ready soon.

Dan

-- 
http://www.danielstender.com/blog/
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8

Bug#795404: cups-backend-bjnp: stops printing after some lines

[Björn Siebke]

Package: cups-backend-bjnp
Version: 1.2-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
Yesterday I newly installed my Canon Pixma MG6650 - it worked. I successfully
printed some pages. Today, after having changed nothing, I tried it again.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Clicked on "print" in LOWriter.

   * What was the outcome of this action?
The printer started with the first lines of the document and then stopped. The
printer's display showed a printing process going on. The queue told me there
was no connection ("printer connected?"). I used the troubleshooting dialogue
(protocol attached).

   * What outcome did you expect instead?
That the printer makes it to the end of the page.



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

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

Versions of packages cups-backend-bjnp depends on:
ii  libc6 2.19-18
ii  libcups2  1.7.5-11+deb8u1

Versions of packages cups-backend-bjnp recommends:
pn  foomatic-db-gutenprint  

cups-backend-bjnp suggests no packages.

-- no debconf information
Page 1 (Scheduler not running?):
{'cups_connection_failure': False}
Page 2 (Is local server publishing?):
{'local_server_exporting_printers': False}
Page 3 (Choose printer):
{'cups_dest': ,
 'cups_instance': None,
 'cups_queue': u'Canon-MG6650',
 'cups_queue_listed': True}
Page 4 (Check printer sanity):
{'cups_device_uri_scheme': u'bjnp',
 'cups_printer_dict': {'device-uri': u'bjnp://db-printer.fritz.box:8611',
   'printer-info': u'Canon MG6600 series',
   'printer-is-shared': True,
   'printer-location': u'',
   'printer-make-and-model': u'Canon MG6600 series 
Ver.5.00',
   'printer-state': 4,
   'printer-state-message': u"Network host 
'db-printer.fritz.box' is busy; will retry in 15 seconds...",
   'printer-state-reasons': [u'connecting-to-device'],
   'printer-type': 8556572,
   'printer-uri-supported': 
u'ipp://localhost:631/printers/Canon-MG6650'},
 'cups_printer_remote': False,
 'is_cups_class': False,
 'local_cups_queue_attributes': {'charset-configured': u'utf-8',
 'charset-supported': [u'us-ascii', u'utf-8'],
 'color-supported': False,
 'compression-supported': [u'none', u'gzip'],
 'copies-default': 1,
 'copies-supported': (1, ),
 'cups-version': u'1.7.5',
 'device-uri': 
u'bjnp://db-printer.fritz.box:8611',
 'document-format-default': 
u'application/octet-stream',
 'document-format-supported': 
[u'application/octet-stream',
   
u'application/pdf',
   
u'application/postscript',
   
u'application/vnd.adobe-reader-postscript',
   
u'application/vnd.cups-command',
   
u'application/vnd.cups-pdf',
   
u'application/vnd.cups-pdf-banner',
   
u'application/vnd.cups-postscript',
   
u'application/vnd.cups-raster',
   
u'application/vnd.cups-raw',
   
u'application/x-cshell',
   
u'application/x-csource',
   
u'application/x-perl',
   
u'application/x-shell',
   u'image/gif',
   u'image/jpeg',
   u'image/png',
   
u'image/pwg-raster',
   u'image/tiff',
   u'image/urf',
   

Bug#795237: gpsshogi FTBFS: "undefined reference to `osl::OslConfig::openingBook" and others

[Steve Langasek]

Package: gpsshogi
Version: 0.6.0-3+nmu1
Followup-For: Bug #795237
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch

The build failure here is not a bug in gpsshogi; this is that libosl needs
to be rebuilt with g++5 before gpsshogi is buildable.

However, what is a bug in gpsshogi is that it hard-codes a dependency on
libosl1.  libosl has an ABI-breaking change with g++5, and since it has
reverse-dependencies (gpsshogi), it should undergo a package name
transition.  There is currently no transition bug filed for libosl (probably
because libosl failed to build in the rebuild test), but once this is done
gpsshogi will be broken because of this hard-coded dependency.

Please do not hard-code dependencies on shared libraries.  If the shlibs
declarations for a library you depend on are incorrect, please fix them in
the library.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru gpsshogi-0.6.0/debian/changelog gpsshogi-0.6.0/debian/changelog
diff -Nru gpsshogi-0.6.0/debian/control gpsshogi-0.6.0/debian/control
--- gpsshogi-0.6.0/debian/control	2015-08-12 11:30:45.0 -0700
+++ gpsshogi-0.6.0/debian/control	2015-08-13 10:49:09.0 -0700
@@ -10,7 +10,7 @@
 
 Package: gpsshogi
 Architecture: i386 amd64
-Depends: ${shlibs:Depends}, ${misc:Depends}, libosl1 (>= 0.6.0), gpsshogi-data (= ${source:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, gpsshogi-data (= ${source:Version})
 Description: Shogi playing program based on OpenShogiLib
  GPSShogi is a Shogi playing program based on OpenShogiLib and won the 19th
  World Computer Shogi Championship. This package contains several binaries to

Bug#795322: cryptmount: FTBFS: assumes automake-1.14

[R.Penney]

Thanks for your bug-report.

I have already been working on fix for this issue, and have
cryptmount-5.1-2 awaiting upload with the support of my sponsor.

For the time being, these packages are available at
http://www.rwpenney.org.uk/software

The new build-system uses debhelper v7 and dh-autoreconf, so should
be a more robust solution in the long term.

RW Penney

Bug#790916: marked as done (gpxviewer: ddepends on unavailible package python-osmgpsmap)

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 18:56:28 +0100
with message-id <55ccda4c.4010...@andrewgee.org>
and subject line 
has caused the Debian Bug report #790916,
regarding gpxviewer: ddepends on unavailible package python-osmgpsmap
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.)


-- 
790916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpxviewer
Severity: grave
Justification: renders package unusable

hi,
since python-osmgpsmap (>= 0.7.1) is not availible in either testing or
unstable, gpxviewer is not instalable (it will probably work on
sparc64 since there python-osmgpsmap is still(?) availible there).

regards,
albert

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Fixed latest version to use new version of osmgpsmap--- End Message ---

Bug#794853: Fwd: Re: Mass bug filing about non free lena image.

[Daniel Stender]

I would love when we don't have a problem here ...

DS

 Forwarded Message 
Subject: Re: Mass bug filing about non free lena image.
Resent-Date: Wed, 12 Aug 2015 20:29:32 + (UTC)
Resent-From: debian-de...@lists.debian.org
Date: Wed, 12 Aug 2015 22:29:18 +0200
From: Jonas Smedegaard 
To: debian-de...@lists.debian.org

Quoting Jakub Wilk (2015-08-12 21:57:40)
> Has anybody asked the copyright holders to release the image under a 
> free license? Or is everybody assuming that they won't?

>From :

> While Playboy often cracks down on illegal uses of its material and 
> did initially send out notices to research publications and journals 
> that used the image,[11] over time it has decided to overlook the wide 
> use of Lena. Eileen Kent, VP of new media at Playboy said, "We decided 
> we should exploit this, because it is a phenomenon."

Above (especially the "overlook the wide use" part) made me stop look 
further for likelihood of free licensing.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

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

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 18:00:14 +
with message-id 
and subject line Bug#791054: fixed in gmsh 2.9.3+dfsg1-2
has caused the Debian Bug report #791054,
regarding gmsh: library transition may be needed when GCC 5 is the default
to be marked as done.

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

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


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

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

What is needed:

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

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

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

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

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

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
--- End Message ---
--- Begin Message ---
Source: gmsh
Source-Version: 2.9.3+dfsg1-2

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated gmsh 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: Thu, 13 Aug 2015 14:34:40 +0200
Source: gmsh
Binary: gmsh gmsh-doc libgmsh-dev libgmsh2v5 libjava-gmsh2 python-gmsh
Architecture: source all ppc64el
Version: 2.9.3+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 gmsh   - Three-dimensional finite element mesh generator
 gmsh-doc   - Three-dimensional finite element mesh generator
 libgmsh-dev - Three-dimensional finite element mesh generator. Development file
 libgmsh2v5 - Three-dimensional finite element mesh generator. Shared library
 libjava-gmsh2 - Three-dimensional finite element mesh generator. Java wrapper
 python-gmsh - Three-dimensional finite element mesh generator. Python wrapper
C

Bug#795045: marked as done (ruby-orm-adapter: FTBFS: undefined method `its' for #

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 20:04:30 +0200
with message-id <20150813180430.GA28446@spin>
and subject line closed byu 0.5.0-2
has caused the Debian Bug report #795045,
regarding ruby-orm-adapter: FTBFS: undefined method `its' for #http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-orm-adapter
Version: 0.5.0-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/ruby-orm-adapter-0.5.0/debian/ruby-orm-adapter/usr/lib/ruby/vendor_ruby:.
 rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
/usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in `method_missing': 
undefined method `its' for # (NoMethodError)
from /ruby-orm-adapter-0.5.0/spec/orm_adapter_spec.rb:9:in `block (2 
levels) in '
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in 
`block in define_example_group_method'
from /ruby-orm-adapter-0.5.0/spec/orm_adapter_spec.rb:6:in `block in 
'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in 
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in 
`block in define_example_group_method'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in 
expose_example_group_alias'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2 
levels) in expose_example_group_alias_globally'
from /ruby-orm-adapter-0.5.0/spec/orm_adapter_spec.rb:3:in `'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in 
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in 
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in 
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in 
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke'
from /usr/bin/rspec:4:in `'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-orm-adapter.html

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
fixed 795045 0.5.0-2
notfixed 795119 ruby-orm-adapter/0.5.0-2
thanks


Hi,

This bug is closed by the upload of 0.5.0-2.

Cheers,

Cédric



signature.asc
Description: Digital signature
--- End Message ---

Bug#791540: FTBFS: undefined reference to symbol 'SDL_UnlockSurface'

[Evgeni Golov]

control: tags -1 + unreproducible

Hi tbm!

On Sun, Jul 05, 2015 at 07:08:14PM -0400, Martin Michlmayr wrote:

> gnujump fails to build in unstable:
> 
> > sbuild (Debian sbuild) 0.64.1 (13 Oct 2013) on m400-c3n1.hlinux.usa.hp.com
> ...
> > /bin/bash ../libtool  --tag=CC   --mode=link gcc  -I/usr/include/libdrm  -g 
> > -DPREFIX=\"/usr\" -DDATA_PREFIX=\"/usr/share/games\" -Wl,--as-needed  -o 
> > gnujump game.o game-input.o game-output.o game-logic.o game-tools.o 
> > game-timer.o main.o menu.o menu-system.o records.o SDL_2dgl.o 
> > SDL_rotozoom.o setup.o SFont.o sprite.o surface.o tools.o replay.o 
> > effects-trail.o effects-blur.o  -lm  -lGL  -lGLU -lGL  -lSDL_image 
> > -lSDL_mixer
> > libtool: link: gcc -I/usr/include/libdrm -g -DPREFIX=\"/usr\" 
> > -DDATA_PREFIX=\"/usr/share/games\" -Wl,--as-needed -o gnujump game.o 
> > game-input.o game-output.o game-logic.o game-tools.o game-timer.o main.o 
> > menu.o menu-system.o records.o SDL_2dgl.o SDL_rotozoom.o setup.o SFont.o 
> > sprite.o surface.o tools.o replay.o effects-trail.o effects-blur.o  -lm 
> > -lGLU -lGL -lSDL_image -lSDL_mixer
> > /usr/bin/ld: SDL_rotozoom.o: undefined reference to symbol 
> > 'SDL_UnlockSurface'
> > //usr/lib/aarch64-linux-gnu/libSDL-1.2.so.0: error adding symbols: DSO 
> > missing from command line
> > collect2: error: ld returned 1 exit status
> > make[4]: *** [gnujump] Error 1

I can't reproduce this neither on my amd64 laptop, nor on asachi.d.o 
(arm64 porterbox).

Is there anything special in your setup that would trigger this?

Regards
Evgeni

-- 
Bruce Schneier can read and understand Perl programs.

Processed: closed byu 0.5.0-2

[Debian Bug Tracking System]

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

> fixed 795045 0.5.0-2
Bug #795045 [src:ruby-orm-adapter] ruby-orm-adapter: FTBFS: undefined method 
`its' for # notfixed 795119 ruby-orm-adapter/0.5.0-2
Bug #795119 {Done: Cédric Boutillier } [src:ruby-stomp] 
ruby-stomp: FTBFS: `method_missing': undefined method `its' for # thanks
Stopping processing here.

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

Bug#754425: marked as done (gpxviewer: incorrect /etc/mailcap entry for application/xml)

[Debian Bug Tracking System]

Your message dated Thu, 13 Aug 2015 19:04:20 +0100
with message-id <55ccdc24.60...@andrewgee.org>
and subject line 
has caused the Debian Bug report #754425,
regarding gpxviewer: incorrect /etc/mailcap entry for application/xml
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.)


-- 
754425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpxviewer
Version: 0.4.3-1
Severity: critical
Justification: breaks unrelated software

The /etc/mailcap file contains the following entry:

application/xml; gpxviewer %s; test=test -n "$DISPLAY"

This is stupid! Most XML files are not GPX files thus cannot be read
by gpxviewer. This breaks software (such as Mutt) using mailcap to be
able to view various kinds of files, here XML files.

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

Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gpxviewer depends on:
ii  librsvg2-common   2.40.2-1
ii  python2.7.6-2
ii  python-gnome2 2.28.1+dfsg-1
ii  python-gtk2   2.24.0-3+b1
ii  python-osmgpsmap  0.7.3-3
ii  xdg-utils 1.1.0~rc1+git20111210-7.1

gpxviewer recommends no packages.

gpxviewer suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Corrected to application/gpx+xml in latest upstream version--- End Message ---

Processed: Re: Bug#791540: FTBFS: undefined reference to symbol 'SDL_UnlockSurface'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + unreproducible
Bug #791540 [gnujump] FTBFS: undefined reference to symbol 'SDL_UnlockSurface'
Added tag(s) unreproducible.

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