Bug#736731: marked as done ([src:jscoverage] Sourceless file)

[Debian Bug Tracking System]

Your message dated Mon, 12 May 2014 06:43:37 +
with message-id 
and subject line Bug#747401: Removed package(s) from unstable
has caused the Debian Bug report #736731,
regarding [src:jscoverage] Sourceless file
to be marked as done.

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

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


-- 
736731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jscoverage
Version:   0.5.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: source-contains-prebuilt-javascript-object
X-Debbugs-CC: ftpmas...@debian.org

I could find the source of:
jscoverage 0.5.1-2 (source)

doc/sh_html.min.js
doc/sh_javascript.min.js
doc/sh_main.min.js


Bastien
--- End Message ---
--- Begin Message ---
Version: 0.5.1-2+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#684850: marked as done (jscoverage: FTBFS: src/js.c:163:9: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Mon, 12 May 2014 06:43:37 +
with message-id 
and subject line Bug#747401: Removed package(s) from unstable
has caused the Debian Bug report #684850,
regarding jscoverage: FTBFS: src/js.c:163:9: error: format not a string literal 
and no format arguments [-Werror=format-security]
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.)


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

Hi,

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

Relevant part:
> gcc -D_FORTIFY_SOURCE=2 -DOSSP -DXP_UNIX -DEXPORT_JS_API -DJS_HAS_FILE_OBJECT 
> -DHAVE_CONFIG_H -Isrc  -O2 -fstack-protector --param=ssp-buffer-size=4 
> -Wformat -Werror=format-security -Wall -DNDEBUG -pipe  -o src/js.o -c src/js.c
> src/js.c: In function 'GetLine':
> src/js.c:163:9: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cc1: some warnings being treated as errors
> make[3]: *** [src/js.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/08/14/jscoverage_0.3.1-1_wheezy.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 ---
Version: 0.5.1-2+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#579227: marked as done (Embedded code copy: libmozjs)

[Debian Bug Tracking System]

Your message dated Mon, 12 May 2014 06:43:37 +
with message-id 
and subject line Bug#747401: Removed package(s) from unstable
has caused the Debian Bug report #579227,
regarding Embedded code copy: libmozjs
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.)


-- 
579227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jscoverage
Version: 0.4-1
Severity: serious
Tags: security
Justification: ECC

Hi (again),

it was just noticed that the FTBFS on s390 I reported sounded like an
FTBFS previously dealt with in libmozjs, meaning you're embedding it
instead of just using libmozjs-dev and dropping your embedded code copy.
Given the security records on xulrunner thingies, I'm opening this at
serious severity with security tag…

Mraw,
KiBi.


--- End Message ---
--- Begin Message ---
Version: 0.5.1-2+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#747780: syncevolution: FTBFS: error: akonadi.pc not found

[Patrick Ohly]

On Sun, 2014-05-11 at 21:37 +0200, Tino Mettler wrote:
> On Sun, May 11, 2014 at 18:45:24 +0200, David Suárez wrote:
> > Source: syncevolution
> > Version: 1.4-1
> > Severity: serious
> > Tags: jessie sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20140510 qa-ftbfs
> > Justification: FTBFS on amd64
> > 
> > Hi,
> > 
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> > 
> > Relevant part (hopefully):
> > > checking for rst2html... /usr/bin/rst2html
> > > checking for SYNTHESIS... yes
> > > checking for GNOMEBLUETOOTH... no
> > > checking for qmake... qmake
> > > checking Akonadi/Collection usability... no
> > > configure: error: akonadi.pc not found. Install it to compile with the 
> > > Akonadi backend enabled.
> > > checking Akonadi/Collection presence... no
> > > checking for Akonadi/Collection... no
> 
> The message about a missing akonadi.pc is misleading, upstream is aware
> of this.
> 
> The full build log revealed this:
> 
> configure:21874: checking Akonadi/Collection usability
> configure:21874: g++ -c -g -O2 -fPIE -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security
> ---D_FORTIFY_SOURCE=2 -I/usr/include/ -I/usr/include//KDE
> I/usr/include/qt4 conftest.cpp >&5
> In file included from
> /usr/include//KDE/Akonadi/../../akonadi/collection.h:25:0,
>  from /usr/include//KDE/Akonadi/Collection:1,
>  from conftest.cpp:80:
> /usr/include/akonadi/entity.h:24:19: fatal error: QString: No such file
> or directory
>  #include 
>^
> compilation terminated.
> 
> I'm not sure if this is a syncevolution bug

Akonadi seems to have changed some header file dependencies and
SyncEvolution 1.4 was not adapted to that yet. I really wish Akonadi
would provide .pc files.

Anyway, the fix went into SyncEvoltution 1.4.1:

commit 7aa9f6d87fc1bd511b86b06a434766fc6aaf3866
Author: Niels Ole Salscheider 
Date:   Sun Mar 2 12:59:32 2014 +0100

autotools: Add QtCore include path to KDEPIM_CFLAGS (FDO #75670)

This fixes an issue where configure fails to find Akonadi when
test programs do not compile because QString is not found:

checking for Akonadi/Collection... no
configure: error: akonadi.pc not found. Install it to compile with the 
Akonadi backend enabled.
...

configure:21857: checking Akonadi/Collection presence
configure:21857: g++ -E  -I/usr/include/ -I/usr/include//KDE 
-I/usr/include/qt4 conftest.cpp
In file included from 
/usr/include//KDE/Akonadi/../../akonadi/collection.h:25:0,
 from /usr/include//KDE/Akonadi/Collection:1,
 from conftest.cpp:44:
/usr/include/akonadi/entity.h:24:19: fatal error: QString: No such file or 
directory
 #include 

diff --git a/src/backends/akonadi/configure-sub.in 
b/src/backends/akonadi/configure-sub.in
index 064c2ed..ed05f1b 100644
--- a/src/backends/akonadi/configure-sub.in
+++ b/src/backends/akonadi/configure-sub.in
@@ -10,7 +10,7 @@ AKONADIFOUND=yes
 if ! test "$KDEPIM_CFLAGS"; then
KDEPIM_CFLAGS="-I`kde4-config --path include` -I`kde4-config --path 
include`/KDE"
if test "$QMAKE"; then
-  KDEPIM_CFLAGS="$KDEPIM_CFLAGS -I`$QMAKE -query QT_INSTALL_HEADERS`"
+  KDEPIM_CFLAGS="$KDEPIM_CFLAGS -I`$QMAKE -query QT_INSTALL_HEADERS` 
-I`$QMAKE -query QT_INSTALL_HEADERS`/QtCore"
fi
 fi
 if ! test "$KDEPIM_LIBS"; then

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: your mail

[Debian Bug Tracking System]

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

> found 747698 5.8.0-17
Bug #747698 [vtk] The method run() of type new Runnable(){} must override a 
superclass method
There is no source info for the package 'vtk' at version '5.8.0-17' with 
architecture ''
Unable to make a source version for version '5.8.0-17'
Marked as found in versions 5.8.0-17.
>
End of message, stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: jessie

[Debian Bug Tracking System]

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

> tags 739208 + sid jessie
Bug #739208 {Done: Reinhard Tartler } 
[acoustid-fingerprinter] Fails to build from source against libav10
Added tag(s) sid and jessie.
> tags 739209 + sid jessie
Bug #739209 [alsa-plugins] FTBFS against libav10
Added tag(s) sid and jessie.
> tags 739220 + sid jessie
Bug #739220 [dvbcut] FTBFS with libav10
Ignoring request to alter tags of bug #739220 to the same tags previously set
> tags 739213 + sid jessie
Bug #739213 [src:avifile] FTBFS against libav10
Added tag(s) sid and jessie.
> tags 739191 + sid jessie
Bug #739191 [src:avbin] Fails to build from source against libav 10
Added tag(s) sid and jessie.
>
End of message, stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: jessie

[Debian Bug Tracking System]

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

> tags 745306 + sid jessie
Bug #745306 [apt-p2p] AptPackages.py: /etc/init.d/apt-p2p start fails
Added tag(s) sid and jessie.
> tags 739314 + sid jessie
Bug #739314 [src:linphone] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739315 + sid jessie
Bug #739315 [vice] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739220 + sid jessie
Bug #739220 [dvbcut] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739439 + sid jessie
Bug #739439 {Done: Reinhard Tartler } [src:opal] FTBFS with 
libav10
Added tag(s) sid and jessie.
> tags 739426 + sid jessie
Bug #739426 [kino] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739377 + sid jessie
Bug #739377 {Done: Reinhard Tartler } [yorick-av] FTBFS 
with libav10
Added tag(s) sid and jessie.
> tags 739442 + sid jessie
Bug #739442 [src:strigi] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739455 + sid jessie
Bug #739455 [xmms2] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739440 + sid jessie
Bug #739440 [src:opencv] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739458 + sid jessie
Bug #739458 [src:xine-lib-1.2] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739460 + sid jessie
Bug #739460 [src:openscenegraph] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739461 + sid jessie
Bug #739461 [zoneminder] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739462 + sid jessie
Bug #739462 [vtk] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739332 + sid jessie
Bug #739332 [src:survex] survex: Needs rebuilding with libav10
Added tag(s) sid and jessie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
739220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739220
739314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739314
739315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739315
739332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739332
739377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739377
739426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739426
739439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739439
739440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739440
739442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739442
739455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739455
739458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739458
739460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739460
739461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739461
739462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739462
745306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#739431: marked as done (FTBFS with libav10)

[Debian Bug Tracking System]

Your message dated Mon, 12 May 2014 03:36:38 +
with message-id 
and subject line Bug#739431: fixed in xjadeo 0.7.6-3
has caused the Debian Bug report #739431,
regarding FTBFS with libav10
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.)


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

Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.

Migration documentation can be found at
https://wiki.libav.org/Migration/10

Cheers,
Moritz

make[5]: Entering directory `/home/jmm/av10/xjadeo-0.7.6/src/xjadeo'
gcc -DHAVE_CONFIG_H -I. -I../..   -D_FORTIFY_SOURCE=2 -Wall -g -O3  
-I/usr/include/freetype2-D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL 
 "-DSUBVERSION=\"\"" -g -O2 -fstack-protector --param=ssp-buffer-size=4 
-Wformat -Werror=format-security -c -o xjadeo-xjadeo.o `test -f 'xjadeo.c' || 
echo './'`xjadeo.c
xjadeo.c: In function 'open_movie':
xjadeo.c:413:19: error: 'AVStream' has no member named 'r_frame_rate'
  else if(av_stream->r_frame_rate.den && av_stream->r_frame_rate.num) {
   ^
xjadeo.c:413:50: error: 'AVStream' has no member named 'r_frame_rate'
  else if(av_stream->r_frame_rate.den && av_stream->r_frame_rate.num) {
  ^
xjadeo.c:414:31: error: 'AVStream' has no member named 'r_frame_rate'
   framerate = av_q2d(av_stream->r_frame_rate);
   ^
xjadeo.c:530:2: warning: 'avcodec_alloc_frame' is deprecated (declared at 
/usr/include/libavcodec/avcodec.h:3110) [-Wdeprecated-declarations]
  pFrame=avcodec_alloc_frame();
  ^
xjadeo.c:540:2: warning: 'avcodec_alloc_frame' is deprecated (declared at 
/usr/include/libavcodec/avcodec.h:3110) [-Wdeprecated-declarations]
  pFrameFMT=avcodec_alloc_frame();
  ^
xjadeo.c: In function 'my_seek_frame':
xjadeo.c:690:49: error: 'AVStream' has no member named 'r_frame_rate'
   timestamp=av_rescale_q(timestamp,c1_Q,v_stream->r_frame_rate); //< 
timestamp/=framerate;
 ^
make[5]: *** [xjadeo-xjadeo.o] Error 1
make[5]: Leaving directory `/home/jmm/av10/xjadeo-0.7.6/src/xjadeo'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/home/jmm/av10/xjadeo-0.7.6/src/xjadeo'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/jmm/av10/xjadeo-0.7.6/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/jmm/av10/xjadeo-0.7.6'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/jmm/av10/xjadeo-0.7.6'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: xjadeo
Source-Version: 0.7.6-3

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated xjadeo 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: Sun, 11 May 2014 22:05:41 -0400
Source: xjadeo
Binary: xjadeo
Architecture: source amd64
Version: 0.7.6-3
Distribution: unstable
Urgency: medium
Maintainer: Reinhard Tartler 
Changed-By: Reinhard Tartler 
Description: 
 xjadeo - Video player with JACK sync
Closes: 739431
Changes: 
 xjadeo (0.7.6-3) unstable; urgency=medium
 .
   * Team upload.
   * Upload to unstable
   * Recompile against libav10 (Closes: #739431)
   * Bump standards version.
Checksums-Sha1: 
 09ad7f7e0c6969df751e245f0129d941a5479231 2151 xjadeo_0.7.6-3.dsc
 1508b6afe07172926be4bb16ea1697ade86760c3 199360 xjadeo_0.7.6-3.debian.tar.xz
 093601bf9122a9d63cdb6c3eda7a6416b1ade92f 339372 xjadeo_0.7.6-3_amd64.deb
Checksums-Sha256: 
 a2794288f7c67446be03aefcd8e9b706a99629e4b30da4c1febeda3dc2668fa3 2151 
xjadeo_0.7.6-3.dsc
 de51825a03b551df97afe571781ba1336e56801920c0a48f3f3531e2

Bug#718004: paramiko: diff for NMU version 1.10.1-1.1

[dai]

i might abuse nmudiff and DELAYED queue to contact the maintainers.
i will be more careful after this.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: Digital signature

Bug#718004: paramiko: diff for NMU version 1.10.1-1.1

[dai]

On Sun, May 11, 2014 at 09:37:21PM -0400, Jeremy T. Bouse wrote:
> https://github.com/jbouse-debian/paramiko/commits/master

i saw http://anonscm.debian.org/gitweb/?p=collab-maint/paramiko.git
from p.q.d.o information.  i did not know you worked on github repo.
so i misunderstood this package was not active about half year.
i cancelled my NMU.  sorry to give you many trouble.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: Digital signature

Bug#747828: iceweasel: the UI is completely broken: no menu bar, no status bar...

[Mike Hommey]

severity 747828 wishlist
title 747828 New UI is confusing at first
thanks

On Mon, May 12, 2014 at 03:21:01AM +0200, Vincent Lefevre wrote:
> On 2014-05-12 06:49:30 +0900, Mike Hommey wrote:
> > On Sun, May 11, 2014 at 11:11:03PM +0200, Vincent Lefevre wrote:
> > > After upgrading to iceweasel 29.0.1-1, the UI got completely broken:
> > > the menu bar no longer appears, the status bar is absent as well, and
> > > the user config has completely been modified.
> 
> For this one, it appears that upstream provides something[*]
> (I don't know whether this is complete), but I didn't see
> anything with the Debian upgrade.

Oh, so your bug report is really "I don't like the new UI". I thought it
was "iceweasel doesn't work at all", a bit like when you get xul errors.

> [*] https://bugzilla.mozilla.org/show_bug.cgi?id=1008761

So, as mentioned in the bug, there is a tour... except it's a Firefox
page on mozilla.org doing that.

> > > BTW, I can't test with "iceweasel -no-remote -safe-mode" as it no longer
> > > works at all. I get the following error:
> > > 
> > >   Iceweasel is already running, but is not responding. To open a new
> > >   window, you must first close the existing Iceweasel process, or
> > >   restart your system.
> > 
> > It sounds like you have an old iceweasel still running in the
> > background. Kill it.
> 
> Well, the goal of -no-remote is that Iceweasel shouldn't try to
> connect to a running version (I'm using this option for testing
> because I don't want to kill the running instance). So, this is
> broken again. The real message should have something like the
> profile is locked (after spending some time, it seems to be the
> real problem). Unfortunately upstream doesn't want to fix the
> message in this case. Trying to test with -safe-mode is rather
> discouraging...

It has been this way for a long time. There's nothing new here.
-no-remote has never allowed to run two instances on the same profile.

Mike


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#718004: paramiko: diff for NMU version 1.10.1-1.1

[Jeremy T. Bouse]

On 05/11/2014 10:33 PM, d...@debian.org wrote:
> On Sun, May 11, 2014 at 09:37:21PM -0400, Jeremy T. Bouse wrote:
>> https://github.com/jbouse-debian/paramiko/commits/master
> 
> i saw http://anonscm.debian.org/gitweb/?p=collab-maint/paramiko.git
> from p.q.d.o information.  i did not know you worked on github repo.
> so i misunderstood this package was not active about half year.
> i cancelled my NMU.  sorry to give you many trouble.
> 

I began to make the move over to GitHub after repeated unreliability
with anonscm.d.o when I tried to access it in the past and because that
is what upstream utilizes so it allows me to track both easily. I began
the GitHub repo from the anonscm repo copy that I had off-line locally
during one such outage and haven't bothered trying to keep it updated.
As soon as I release a new upload with the Vcs-* lines in debian/control
updated I'll get that repo removed.

Again this confusion would have easily been cleared up with an email
to the maintainer, who as you can tell does respond to them.



signature.asc
Description: OpenPGP digital signature

Processed (with 1 errors): Re: Bug#747828: iceweasel: the UI is completely broken: no menu bar, no status bar...

[Debian Bug Tracking System]

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

> severity 747828 wishlist
Bug #747828 [iceweasel] iceweasel: the UI is completely broken: no menu bar, no 
status bar...
Severity set to 'wishlist' from 'grave'
> title 747828 New UI is confusing at first
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#743141: system hangs when building gcc on kfreebsd-amd64

[Steven Chamberlain]

An even simpler way, don't need the expect program.  Create a thread in
a 64-bit process, and try to execve() a 32-bit executable:

> #include 
> #include 
> 
> void *thread_main() {
> char *cmdline[] = { "./testcase32", NULL };
> execve(cmdline[0], cmdline, NULL);
> }
> 
> int main() {
> pthread_t thread;
> pthread_create(&thread, NULL, thread_main, NULL);
> pthread_join(thread, NULL);
> return 0;
> }

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#718004: paramiko: diff for NMU version 1.10.1-1.1

[Jeremy T. Bouse]

On 05/11/2014 09:16 PM, d...@debian.org wrote:
> On Fri, May 09, 2014 at 02:54:57PM -0400, Jeremy T. Bouse wrote:
>> If this work was not done through the very public, very accessible Git repo
>> that is used to manage the package then it has wasted your time and made
>> mine harder as I've already been working on 1.10.1. So for wasting the time
>> that I do have I thank you.
> 
> if this DELAYED NMU could put pressure or somthing on you, i am really sorry.
> if your working goes on, i will cancel my NMU.  please tell me.
> 

https://github.com/jbouse-debian/paramiko/commits/master

I've been working on 1.12.2 even though 1.14.0 is released as well but
between
1.10 and 1.12 was fork, merge and change of upstream which has made the
process
as simple. Then complicated by still trying to get my new 4096 bit RSA
key into
the keyring and issues at work which have delayed my time to actually
work on it.

Attempt to help work within the packaging done within Git would have
been much more
helpful. As well I recall more than a couple tickets which looking
through would
have identified efforts being made before attempts to do a NMU without
having
first attempted contact with the maintainer of the package in question.

I guess I expect more of Debian Developers but this seems to be a
continuing trend
those that have joined the project within the past 3-5 years now. I
might suggest
going back to the Developers Corner and re-reading the content... Maybe
starting
with https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu



signature.asc
Description: OpenPGP digital signature

Bug#746122: deets: FTBFS: (.text+0x1d): undefined reference to `MD5Update'

[Guillem Jover]

Control: reassign -1 libdpkg-dev
Control: retitle -1 libdpkg-dev: Has stopped providing MD5 functions
Control: affects -1 deets

Hi!

Just noticed deets stopped building with lattest libdpkg-dev, and
and of course here's the RC bug.

On Tue, 2014-04-29 at 15:49:42 +, Clint Adams wrote:
> On Sun, Apr 27, 2014 at 02:02:57PM +0200, David Suárez wrote:
> > The full build log is available from:
> >http://aws-logs.debian.net/ftbfs-logs/2014/04/26/deets_0.2-3_unstable.log
> 
> Something changed with libdpkg-dev.

Indeed, that's my fault. I moved those functions to libcompat. I'm
working now on a fix for 1.17.10.

Clint, in the future, please do not hesitate to poke me to check if
such changes are intentional or not.

Thanks,
Guillem


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#746122: deets: FTBFS: (.text+0x1d): undefined reference to `MD5Update'

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libdpkg-dev
Bug #746122 [src:deets] deets: FTBFS: (.text+0x1d): undefined reference to 
`MD5Update'
Bug reassigned from package 'src:deets' to 'libdpkg-dev'.
No longer marked as found in versions deets/0.2-3.
Ignoring request to alter fixed versions of bug #746122 to the same values 
previously set
> retitle -1 libdpkg-dev: Has stopped providing MD5 functions
Bug #746122 [libdpkg-dev] deets: FTBFS: (.text+0x1d): undefined reference to 
`MD5Update'
Changed Bug title to 'libdpkg-dev: Has stopped providing MD5 functions' from 
'deets: FTBFS: (.text+0x1d): undefined reference to `MD5Update''
> affects -1 deets
Bug #746122 [libdpkg-dev] libdpkg-dev: Has stopped providing MD5 functions
Added indication that 746122 affects deets

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747828: iceweasel: the UI is completely broken: no menu bar, no status bar...

[Vincent Lefevre]

On 2014-05-12 06:49:30 +0900, Mike Hommey wrote:
> On Sun, May 11, 2014 at 11:11:03PM +0200, Vincent Lefevre wrote:
> > After upgrading to iceweasel 29.0.1-1, the UI got completely broken:
> > the menu bar no longer appears, the status bar is absent as well, and
> > the user config has completely been modified.

For this one, it appears that upstream provides something[*]
(I don't know whether this is complete), but I didn't see
anything with the Debian upgrade.

[*] https://bugzilla.mozilla.org/show_bug.cgi?id=1008761

> > BTW, I can't test with "iceweasel -no-remote -safe-mode" as it no longer
> > works at all. I get the following error:
> > 
> >   Iceweasel is already running, but is not responding. To open a new
> >   window, you must first close the existing Iceweasel process, or
> >   restart your system.
> 
> It sounds like you have an old iceweasel still running in the
> background. Kill it.

Well, the goal of -no-remote is that Iceweasel shouldn't try to
connect to a running version (I'm using this option for testing
because I don't want to kill the running instance). So, this is
broken again. The real message should have something like the
profile is locked (after spending some time, it seems to be the
real problem). Unfortunately upstream doesn't want to fix the
message in this case. Trying to test with -safe-mode is rather
discouraging...

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#718004: paramiko: diff for NMU version 1.10.1-1.1

[dai]

On Fri, May 09, 2014 at 02:54:57PM -0400, Jeremy T. Bouse wrote:
> If this work was not done through the very public, very accessible Git repo
> that is used to manage the package then it has wasted your time and made
> mine harder as I've already been working on 1.10.1. So for wasting the time
> that I do have I thank you.

if this DELAYED NMU could put pressure or somthing on you, i am really sorry.
if your working goes on, i will cancel my NMU.  please tell me.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: Digital signature

Bug#743141: system hangs when building gcc on kfreebsd-amd64

[Steven Chamberlain]

Attached is a ktrace of expect spawning a 64-bit executable.

I can't do this for the 32-bit testcase because the system crashes
before any ktrace output is written to disk.  Ivo's screenshot
implicated a 'spin lock held too long'.

I tried replacing the testcase with something that does "sleep(10)"
instead.  The crash still happens immediately (upon program start, not
program exit).

In Ivo's screenshot, "sched lock 4" implicates the ULE scheduler,
something to do with thread queues.  kern/kern_mutex.c suggests that
kfreebsd 9.2 compiled with WITNESS might give a little more info.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


ktrace.txt.gz
Description: GNU Zip compressed data

Bug#739308: libzip-dev: Include file in wrong place

[John Paul Adrian Glaubitz]

>  /usr/lib/*/libzip/include/zipconf.h looks like multiarch file,
> is it not the right place?

Indeed. The mentioned header file is platform-specific, so it might
not be wise to put it under the general /usr/include directory
structure.

On the other hand, the libzip-dev package is not a Multi-Arch package,
so you wouldn't expect the package to ship Multi-Arch-specific files:

glaubitz@z6:~> apt-cache show libzip2:amd64 |grep Multi-Arch
glaubitz@z6:~> apt-cache show libzip-dev:amd64 |grep Multi-Arch
glaubitz@z6:~>

I'm also not sure how sensible it is to ship -dev packages as Multi-Arch
files since, as this case proofs, obviously creates more problems than
it solves. The advantage of shipping Multi-Arch files in this case would
be the possibility to cross-build. Since it is more sensible to build
packages in a clean chroot anyway, you don't really win anything by
making the -dev package Multi-Arch-capable.

I therefore suggest that, at least for the time being, we apply Mateusz'
patch and revert the package back to a non-Multi-Arch version such that
other packages which build-depend on libzip will no longer FTBFS.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: closing 739238

[Debian Bug Tracking System]

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

> close 739238 2.70-2
Bug #739238 [src:blender] FTBFS with libav10
The source 'blender' and version '2.70-2' do not appear to match any binary 
packages
Marked as fixed in versions blender/2.70-2.
Bug #739238 [src:blender] FTBFS with libav10
Marked Bug as done
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: bug 747832 is forwarded to https://github.com/xtingray/tupi/issues/7

[Debian Bug Tracking System]

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

> forwarded 747832 https://github.com/xtingray/tupi/issues/7
Bug #747832 [src:tupi] tupi: tupi build-depends on missing qtmobility-dev on 
!linux
Set Bug forwarded-to-address to 'https://github.com/xtingray/tupi/issues/7'.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#743141: system hangs when building gcc on kfreebsd-amd64

[Steven Chamberlain]

Finally getting somewhere!

testcase.c can be just:
> int main() { }

Use the system GCC, don't need to compile it from source.

> $ gcc -o testcase testcase.c

This is on kfreebsd-amd64, the executable is 64-bit.

Use expect to spawn it like this (same way that dejagnu does in the GCC
testsuite) :

> $ expect
> expect1.1> open "| ./testcase |& cat" "r"
> file6

This is okay.

Now need gcc-multilib installed for this:

> $ gcc -m32 -o testcase testcase.c
> $ expect
> expect1.1> open "| ./testcase |& cat" "r"

The 32-bit executable, spawned this way by expect, triggers an immediate
reboot.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: found 739221 in 1.5-2, closing 739221

[Debian Bug Tracking System]

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

> found 739221 1.5-2
Bug #739221 [src:ffdiaporama] FTBFS with libav10
Marked as found in versions ffdiaporama/1.5-2.
> close 739221 1.5-3
Bug #739221 [src:ffdiaporama] FTBFS with libav10
Marked as fixed in versions ffdiaporama/1.5-3.
Bug #739221 [src:ffdiaporama] FTBFS with libav10
Marked Bug as done
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#743141: system hangs when building gcc on kfreebsd-amd64

[Steven Chamberlain]

On 11/05/14 18:18, Petr Salinger wrote:
> I tried under plain FreeBSD kernel (via kfreebsd-downloader-10)
> and it does not reboot for me.

It still crashes reproducibly for me, on upstream's build of:
GNU/kFreeBSD debian 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu
Jan 16 22:34:59 UTC 2014
r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC x86_64

I deleted all tests except for
src/gcc/testsuite/gcc.c-torture/compile/pr44686.c
and then:

> steven@debian:~/gcc-4.7-4.7.3/build/gcc$ make check 
> RUNTESTFLAGS='--target_board "unix/-m32" -v -v'
...
> Testing gcc.c-torture/execute/builtins/20010124-1.c,  -O0
> doing compile
> Invoking the compiler as /home/steven/gcc-4.7-4.7.3/build/gcc/xgcc 
> -B/home/steven/gcc-4.7-4.7.3/build/gcc/ 
> /home/steven/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/execute/builtins/20010124-1.c
>  
> /home/steven/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/execute/builtins/20010124-1-lib.c
>  
> /home/steven/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/execute/builtins/lib/main.c
>-w  -O0   -lm   -m32 -o 
> /home/steven/gcc-4.7-4.7.3/build/gcc/testsuite/gcc/20010124-1.x0
> Setting timeout to 300
> Executing on host: /home/steven/gcc-4.7-4.7.3/build/gcc/xgcc 
> -B/home/steven/gcc-4.7-4.7.3/build/gcc/ 
> /home/steven/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/execute/builtins/20010124-1.c
>  
> /home/steven/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/execute/builtins/20010124-1-lib.c
>  
> /home/steven/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/execute/builtins/lib/main.c
>-w  -O0   -lm   -m32 -o 
> /home/steven/gcc-4.7-4.7.3/build/gcc/testsuite/gcc/20010124-1.x0(timeout 
> = 300)
> pid is 2166 -2166
> waitres is 2166 exp8 0 0
> output is  status 0
> Checking pattern "sparc-*-sunos*" with x86_64-pc-kfreebsd-gnu
> Checking pattern "alpha*-*-*" with x86_64-pc-kfreebsd-gnu
> Checking pattern "hppa*-*-hpux*" with x86_64-pc-kfreebsd-gnu
> Checking pattern "sparc-*-sunos*" with x86_64-pc-kfreebsd-gnu
> Checking pattern "alpha*-*-*" with x86_64-pc-kfreebsd-gnu
> Checking pattern "hppa*-*-hpux*" with x86_64-pc-kfreebsd-gnu
> Checking "spu-*-*" against "x86_64-pc-kfreebsd-gnu"
> Checking x86_64-pc-kfreebsd-gnu against x86_64-pc-kfreebsd-gnu
> loading to unix/-m32
> Setting LD_LIBRARY_PATH to 
> :/home/steven/gcc-4.7-4.7.3/build/gcc:/home/steven/gcc-4.7-4.7.3/build/gcc/32::/home/steven/gcc-4.7-4.7.3/build/gcc:/home/steven/gcc-4.7-4.7.3/build/gcc/32
> spawning command 
> /home/steven/gcc-4.7-4.7.3/build/gcc/testsuite/gcc/20010124-1.x0


This even works inside of a BSD jail.

After a reboot, 20010124-1.x0 was missing.  Even though the filesystem
is UFS, mounted with the sync option.

I can compile it by hand, then run it with the LD_LIBRARY_PATH as above,
but it doesn't trigger the crash that way.

I'd really like to go to upstream with this, but the testcase is
currently "a full Debian GNU/kFreeBSD sid chroot, a fully built GCC-4.7
source tree and all build dependencies" and I think we need to find
something smaller.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: tagging 739238, tagging 739239, tagging 739321, tagging 739325, tagging 739328, tagging 739431 ...

[Debian Bug Tracking System]

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

> tags 739238 + sid jessie
Bug #739238 [src:blender] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739239 + sid jessie
Bug #739239 [forked-daapd] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739321 + sid jessie
Bug #739321 [src:gpac] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739325 + sid jessie
Bug #739325 [src:libquicktime] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739328 + sid jessie
Bug #739328 [src:lightspark] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739431 + sid jessie
Bug #739431 [xjadeo] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739433 + sid jessie
Bug #739433 [performous] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739441 + sid jessie
Bug #739441 [xbmc] FTBFS with libav10
Added tag(s) sid and jessie.
> tags 739453 + sid jessie
Bug #739453 [xine-lib] FTBFS with libav10
Added tag(s) sid and jessie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
739238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739238
739239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739239
739321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739321
739325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739325
739328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739328
739431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739431
739433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739433
739441: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739441
739453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747833: libpam-yubico: unable to dlopen: symbol ykclient_set_url_bases [...] not defined in libykclient.so.3

[Clemens Lang]

Package: libpam-yubico
Version: 2.15-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

libpam-yubico seems to be broken in its current state. PAM fails to load
the plugin with the following message in /var/log/auth.log:

  PAM unable to dlopen(pam_yubico.so): /lib/security/pam_yubico.so: symbol 
ykclient_set_url_bases, version YKCLIENT_2.12 not defined in file 
libykclient.so.3 with link time reference

The following output might be helpful in debugging the problem:

  # readelf --syms /lib/security/pam_yubico.so | grep ykclient_set_url
20:  0 FUNCGLOBAL DEFAULT  UND 
ykclient_set_url_bases@YKCLIENT_2.12 (10)
76:  0 FUNCGLOBAL DEFAULT  UND 
ykclient_set_url_template@Base (14)

  # readelf --syms /usr/lib/x86_64-linux-gnu/libykclient.so.3 | grep 
ykclient_set_url
53: 380029 FUNCGLOBAL DEFAULT   12 
ykclient_set_url_template@@Base
62: 3620   254 FUNCGLOBAL DEFAULT   12 
ykclient_set_url_bases@@YKCLIENT_2.12
77: 37e022 FUNCGLOBAL DEFAULT   12 
ykclient_set_url_template@@Base

I don't know enough about symbol versioning to find out what went wrong
here, but it seems the different number of @ signs in the symbol names
are to blame. Would a rebuild fix this?

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

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

Versions of packages libpam-yubico depends on:
ii  debconf [debconf-2.0]  1.5.53
ii  libc6  2.18-5
ii  libldap-2.4-2  2.4.39-1
ii  libpam-runtime 1.1.8-3
ii  libpam0g   1.1.8-3
ii  libykclient3   2.12-1
ii  libykpers-1-1  1.15.1-1
ii  libyubikey01.11-2

libpam-yubico recommends no packages.

libpam-yubico suggests no packages.

-- debconf information:
  libpam-yubico/module_args: mode=client try_first_pass id=3 
key=SECRETSECRETSECRETSECRETSEC= 
url=https://secreturl.example.net/wsapi/2.0/verify?id=%d&otp=%s


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: found 739237 in 0.29-2, closing 739237, tagging 739237

[Debian Bug Tracking System]

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

> found 739237 0.29-2
Bug #739237 [ffmpeg2theora] FTBFS with libav10
Marked as found in versions ffmpeg2theora/0.29-2.
> close 739237 0.29.0~git+20140316-1
Bug #739237 [ffmpeg2theora] FTBFS with libav10
Marked as fixed in versions ffmpeg2theora/0.29.0~git+20140316-1.
Bug #739237 [ffmpeg2theora] FTBFS with libav10
Marked Bug as done
> tags 739237 + sid jessie
Bug #739237 {Done: Sebastian Ramacher } [ffmpeg2theora] 
FTBFS with libav10
Added tag(s) sid and jessie.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#739337: marked as done (FTBFS with libav10)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 23:18:52 +
with message-id 
and subject line Bug#739337: fixed in mplayer2 2.0-728-g2c378c7-2
has caused the Debian Bug report #739337,
regarding FTBFS with libav10
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.)


-- 
739337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mplayer2
Version: 2.0-701-gd4c5b7f-2
Severity: important

Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.

Migration documentation can be found at
https://wiki.libav.org/Migration/10

Cheers,
Moritz


-I/usr/include/bs2b   -c -o screenshot.o screenshot.c
screenshot.c: In function 'destroy_ctx':
screenshot.c:60:5: warning: 'avcodec_free_frame' is deprecated (declared at 
/usr/include/libavcodec/avcodec.h:3135) [-Wdeprecated-declarations]
 avcodec_free_frame(&ctx->pic);
 ^
screenshot.c: In function 'screenshot_get_ctx':
screenshot.c:72:9: warning: 'avcodec_alloc_frame' is deprecated (declared at 
/usr/include/libavcodec/avcodec.h:3110) [-Wdeprecated-declarations]
 ctx->pic = avcodec_alloc_frame();
 ^
screenshot.c: In function 'write_png':
screenshot.c:86:54: error: 'CODEC_ID_PNG' undeclared (first use in this 
function)
 struct AVCodec *png_codec = avcodec_find_encoder(CODEC_ID_PNG);
  ^
screenshot.c:86:54: note: each undeclared identifier is reported only once for 
each function it appears in
screenshot.c:113:5: warning: 'avcodec_get_frame_defaults' is deprecated 
(declared at /usr/include/libavcodec/avcodec.h:3120) [-Wdeprecated-declarations]
 avcodec_get_frame_defaults(pic);
 ^
screenshot.c:118:5: error: implicit declaration of function 
'avcodec_encode_video' [-Werror=implicit-function-declaration]
 int size = avcodec_encode_video(avctx, outbuffer, outbuffer_size, pic);
 ^
cc1: some warnings being treated as errors
make[2]: *** [screenshot.o] Error 1
make[2]: *** Waiting for unfinished jobs
make[2]: Leaving directory `/home/jmm/av10/mplayer2-2.0-701-gd4c5b7f'
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory `/home/jmm/av10/mplayer2-2.0-701-gd4c5b7f'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: mplayer2
Source-Version: 2.0-728-g2c378c7-2

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated mplayer2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 May 2014 15:24:13 -0400
Source: mplayer2
Binary: mplayer2 mplayer2-dbg
Architecture: source amd64
Version: 2.0-728-g2c378c7-2
Distribution: unstable
Urgency: low
Maintainer: Reinhard Tartler 
Changed-By: Reinhard Tartler 
Description: 
 mplayer2   - next generation movie player for Unix-like systems
 mplayer2-dbg - Debugging symbols for mplayer2
Closes: 739337 743604
Changes: 
 mplayer2 (2.0-728-g2c378c7-2) unstable; urgency=low
 .
   * Upload to unstable, closes: #739337
   * Compile against samba-4.0, Closes: #743604
   * Bump standards version, no changes needed
Checksums-Sha1: 
 a8d12c64aabd13a764abd08d16aabb0773c85d99 3220 mplayer2_2.0-728-g2c378c7-2.dsc
 fea8d2266f9c00ea01711022cf8663373aee21df 11888 
mplayer2_2.0-728-g2c378c7-2.debian.tar.xz
 c894c77ffb8206ece53e320bf5a83a3bf85f0b92 923476 
mplayer2_2.0-728-g2c378c7-2_amd64.deb
 47f28686c01468b76c81345a038dd9b09bfb2bf0 2459312 
mplayer2-dbg_2.0-728-g2c378c7-2_amd64.deb
Checksums-Sha256: 
 1d449db1e3162d0e01a5e9fcd729c09079cddd04ff6a262e28cadfe197a20c54 3220 
mplayer2_2.0-728-g2c378c7-2.dsc
 d5c2adcf69664f91813e7fc52a4fec7fffa5123c30aa948a9e472c1cb01e04e0 11888 
mplayer2_2.0-728-g2c378c7-2.debian.tar.xz
 ec47fc7b8152cf1fe95d7ed65da3c60f9585db61e862f33905b9d614e1ffd326 923476 
mpl

Bug#747832: tupi: tupi build-depends on missing qtmobility-dev on !linux

[Sebastian Ramacher]

Source: tupi
Version: 0.2+git04-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

tupi build-depends on qmobility-dev which only exists on Linux
architectures. Hence tupi cannot be built on kfreebsd-* which blocks the
migration of 0.2+git04-1 to testing. If qmobility-dev is only an
optional build dependency, please add the appropriate architecture
qualification to it. If not, please file a bug against ftp.debian.org
and get the o-o-d tupi binaries removed on kfreebsd-*.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#747831: libreoffice-accessodf: can't be installed with current libreoffice

[Christoph Anton Mitterer]

Package: libreoffice-accessodf
Version: 0.1-4
Severity: grave
Justification: renders package unusable


Hi.

The package can't be installed with the current libreoffice version in sid.

Cheers,
Chris.


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

Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_DE.utf8, LC_CTYPE=en_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libreoffice-accessodf depends on:
ii  libaccessodf-java  0.1-4

libreoffice-accessodf recommends no packages.

libreoffice-accessodf suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#723957: [Pkg-openldap-devel] Bug#723957: slapd: commented olcDbDirectory config line causes unusable system and potential data loss on upgrade

[Ryan Tandy]

Hi Dominik,

On 11/05/14 08:57 AM, Dominik George wrote:
> Reproducible here, except I have no commented out olcDbDirectory lines.
> 
> I have an accesslog overlay in /var/lib/ldap/accesslog, and that broke
> the same way as the OT described.

I believe that's resolved by a recent git commit, not yet uploaded:

http://anonscm.debian.org/gitweb/?p=pkg-openldap/openldap.git;a=commitdiff;h=3e970b4f263e4f9306dde4a2ae2bcfb82459ddd1;hp=4207c36b7d83456ba51d2ab487365ee039cf3fd3

See the referenced Ubuntu bug, https://bugs.launchpad.net/bugs/1003854

thanks,
Ryan



signature.asc
Description: OpenPGP digital signature

Bug#747420: marked as done (libsword-dev: libsword.so is a broken symlink)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 22:20:59 +
with message-id 
and subject line Bug#747420: fixed in sword 1.7.2+dfsg-2
has caused the Debian Bug report #747420,
regarding libsword-dev: libsword.so is a broken symlink
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.)


-- 
747420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsword-dev
Version: 1.7.2+dfsg-1
Severity: grave
Justification: renders package unusable

libsword10 ships libsword.so.10.
libsword-dev ships libsword.so as a symlink to libsword.so.9.

Cheers,
Julien


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: sword
Source-Version: 1.7.2+dfsg-2

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

Debian distribution maintenance software
pp.
Dimitri John Ledkov  (supplier of updated sword package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 May 2014 22:09:52 +0100
Source: sword
Binary: libsword10 libsword-dev libsword-common libsword-utils libsword-dbg 
diatheke
Architecture: all amd64 source
Version: 1.7.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: CrossWire Packages 
Changed-By: Dimitri John Ledkov 
Closes: 747420
Description: 
 diatheke   - command line bible browsing and search tool
 libsword10 - API/library for bible software
 libsword-common - common settings and module repository for libsword
 libsword-dbg - API/library for bible software - Debug Files
 libsword-dev - Development files for libsword
 libsword-utils - conversion utilities for bible documents in SWORD supported 
forma
Changes: 
 sword (1.7.2+dfsg-2) unstable; urgency=medium
 .
   * Correct shared library symlink. (Closes: #747420)
Checksums-Sha1: 
 8fe95989f790c121c3b7f7378458170c93cce590 2249 sword_1.7.2+dfsg-2.dsc
 b8ffce6f90f225dea8ca9f2f1fb00c8b07e847d9 35568 sword_1.7.2+dfsg-2.debian.tar.xz
 828ab8ef192c7b11cde9033c71b90e9b0f1894c1 436942 
libsword10_1.7.2+dfsg-2_amd64.deb
 bec0d5f08f3093b07918eff72282dd813a74e769 582568 
libsword-dev_1.7.2+dfsg-2_amd64.deb
 3e8320c01b75a05dfe6926b7c0c63fe32dec1161 143422 
libsword-common_1.7.2+dfsg-2_all.deb
 8e85dccdee60006496250a47767befcc116e2a42 145974 
libsword-utils_1.7.2+dfsg-2_amd64.deb
 92cd7b92d2880bf5c12931aa2723f665395cb932 4184854 
libsword-dbg_1.7.2+dfsg-2_amd64.deb
 92c43bdcad7f8b6f0eaf88da24041ea3034c 78064 diatheke_1.7.2+dfsg-2_amd64.deb
Checksums-Sha256: 
 277f58399302475c47b01fbe47a7e1e21467443e71334db3e40b337f652583ee 2249 
sword_1.7.2+dfsg-2.dsc
 0d54c9431b0ceb218ddf7c6b3de20840b7415c0057db003755c6396f1291 35568 
sword_1.7.2+dfsg-2.debian.tar.xz
 00dba296da38d108234c6d0b357d8bacb8a2aeb807f8000503d32e9dc12362ec 436942 
libsword10_1.7.2+dfsg-2_amd64.deb
 2545fcc07472e94234a59ff1ddd6656cfc5399b5f3548bee512cfbf182e46186 582568 
libsword-dev_1.7.2+dfsg-2_amd64.deb
 66cd4f5845f3e5e6f669be72ab2bf1b1ded603027738f4558a195974596a51c6 143422 
libsword-common_1.7.2+dfsg-2_all.deb
 c8a80219d47b899950f4633b7c6d4131e01fec11108f0426da8164c6bec49a87 145974 
libsword-utils_1.7.2+dfsg-2_amd64.deb
 22208a0e42ea7045043dee0a6551d0e249e7ec38426104ae8831e9b14a9d4d66 4184854 
libsword-dbg_1.7.2+dfsg-2_amd64.deb
 4bdd8adf9ff59aed83695965a28af080be034abc159ae53e5df7ac943cb73def 78064 
diatheke_1.7.2+dfsg-2_amd64.deb
Files: 
 369a94a443cc123b0bd7c16f47a5db6f 2249 libs optional sword_1.7.2+dfsg-2.dsc
 7877213db5d493ce9d8264a4f112e9c3 35568 libs optional 
sword_1.7.2+dfsg-2.debian.tar.xz
 e5ee37c53a89ad90d6e57739afa312d8 436942 libs optional 
libsword10_1.7.2+dfsg-2_amd64.deb
 954d8edecd2e033922f0e062c42a21ad 582568 libdevel optional 
libsword-dev_1.7.2+dfsg-2_amd64.deb
 fdecd11748c61b5e35c64d7c25a280fe 143422 devel optional 
libsword-common_1.7.2+dfsg-2_all.deb
 cb70bfb2b58e6e42b2a51396a800deb0 145974 devel optional 
libsword-utils_1.7.2+dfsg-2_amd64.deb
 bd8d4ba6c0fc40446d9e57ca13c289f2 4184854 debug extra 
libsword-dbg_1.7.2+dfsg-2_amd64.deb
 24496a345777617439ffe2ca08170e01 78064 text optional 
diatheke_1.7.

Processed: Re: Bug#747393: fixed in sdformat 2.0.0-3

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #747393 {Done: Jose Luis Rivero } 
[libsdformat1,libsdformat2] libsdformat2 and libsdformat1: error when trying to 
install together
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions sdformat/2.0.0-3.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747393: fixed in sdformat 2.0.0-3

[Julien Cristau]

Control: reopen -1

On Sun, May 11, 2014 at 21:23:54 +, Jose Luis Rivero wrote:

>  sdformat (2.0.0-3) unstable; urgency=medium
>  .
>* [f03ab47] Conflict with libsdformat1. (Closes: #747393)

This is not an appropriate fix.  See policy §8.2:

 If your package contains files whose names do not change with each
 change in the library shared object version, you must not put them in
 the shared library package.  Otherwise, several versions of the shared
 library cannot be installed at the same time without filename clashes,
 making upgrades and transitions unnecessarily difficult.

Cheers,
Julien


signature.asc
Description: Digital signature

Processed: found 739301 in 2.5.0-4, closing 739301, tagging 739301

[Debian Bug Tracking System]

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

> found 739301 2.5.0-4
Bug #739301 [src:cmus] FTBFS with libav10
Marked as found in versions cmus/2.5.0-4.
> close 739301 2.5.0-5
Bug #739301 [src:cmus] FTBFS with libav10
Marked as fixed in versions cmus/2.5.0-5.
Bug #739301 [src:cmus] FTBFS with libav10
Marked Bug as done
> tags 739301 + sid jessie
Bug #739301 {Done: Sebastian Ramacher } [src:cmus] FTBFS 
with libav10
Added tag(s) sid and jessie.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747828: iceweasel: the UI is completely broken: no menu bar, no status bar...

[Mike Hommey]

On Sun, May 11, 2014 at 11:11:03PM +0200, Vincent Lefevre wrote:
> Package: iceweasel
> Version: 29.0.1-1
> Severity: grave
> Justification: renders package unusable
> 
> After upgrading to iceweasel 29.0.1-1, the UI got completely broken:
> the menu bar no longer appears, the status bar is absent as well, and
> the user config has completely been modified.
> 
> BTW, I can't test with "iceweasel -no-remote -safe-mode" as it no longer
> works at all. I get the following error:
> 
>   Iceweasel is already running, but is not responding. To open a new
>   window, you must first close the existing Iceweasel process, or
>   restart your system.

It sounds like you have an old iceweasel still running in the
background. Kill it.

Mike


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#747726: SIGSGV in gfxContext::PushGroupAndCopyBackground on zoom

[Debian Bug Tracking System]

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

> severity 747726 important
Bug #747726 [iceweasel] SIGSGV in gfxContext::PushGroupAndCopyBackground on zoom
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747766: marked as done (cclive: FTBFS: configure.ac: error: possibly undefined macro: AC_DEFINE)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 21:49:32 +
with message-id 
and subject line Bug#747766: fixed in cclive 0.7.16-2
has caused the Debian Bug report #747766,
regarding cclive: FTBFS: configure.ac: error: possibly undefined macro: 
AC_DEFINE
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with autoreconf
>dh_testdir
>dh_autoreconf
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `config.aux'.
> libtoolize: copying file `config.aux/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
> libtoolize: copying file `m4/libtool.m4'
> libtoolize: copying file `m4/ltoptions.m4'
> libtoolize: copying file `m4/ltsugar.m4'
> libtoolize: copying file `m4/ltversion.m4'
> libtoolize: copying file `m4/lt~obsolete.m4'
> configure.ac:46: error: possibly undefined macro: AC_DEFINE
>   If this token and others are legitimate, please use m4_pattern_allow.
>   See the Autoconf documentation.
> autoreconf: /usr/bin/autoconf failed with exit status: 1
> dh_autoreconf: autoreconf -f -i returned exit code 1
> make: *** [build] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/05/10/cclive_0.7.16-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Alejandro Garrido Mota  (supplier of updated cclive 
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: Sun, 11 May 2014 16:51:26 -0430
Source: cclive
Binary: cclive
Architecture: source amd64
Version: 0.7.16-2
Distribution: unstable
Urgency: low
Maintainer: Alejandro Garrido Mota 
Changed-By: Alejandro Garrido Mota 
Description: 
 cclive - lightweight command line video extraction tool
Closes: 747766
Changes: 
 cclive (0.7.16-2) unstable; urgency=low
 .
   * fix-rpath.diff: Add Last-Update statement.
   * Add pkg-config to BD in d/control (Closes: #747766)
   * Update Standards-Version to 3.9.5
Checksums-Sha1: 
 d73f461fa607686bd6f906c5d125f9659dd46980 1393 cclive_0.7.16-2.dsc
 c9ae3f6a82fbc96d3125ca7943cc893c59620997 3716 cclive_0.7.16-2.debian.tar.xz
 b836b1bc1475444b021a7bfd0a9f657c31c37d81 133574 cclive_0.7.16-2_amd64.deb
Checksums-Sha256: 
 033e241eba639286cb4e20d7791094d3e94bdd2c44439375894357f4139fee7d 1393 
cclive_0.7.16-2.dsc
 fa0eac1ed8be6b4bf5bef127c3ab267aa301447b677324963e075cfdfe356869 3716 
cclive_0.7.16-2.debian.tar.xz
 f0705f42754c9630990853ebb8fd2d8d6e54c6dda622d0cf9e6b41d9ec27bc1c 133574 
cclive_0.7.16-2_amd64.deb
Files: 
 a89ebc2255f9b33ffdfa91c94a090da3 133574 video optional 
cclive_0.7.16-2_amd64.deb
 61a03aad1a3977a511cb1a0a0cd48437 1393 video optional cclive_0.7.16-2.dsc
 005d9a98b298d0e0d1c9a08d7179ed9f 3716 video optional 
cclive_0.7.16-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlNv65gACgkQ9rCWRbJL8gCCIwCgoZhTim8V8V81WBI82UiD95Sh
gksAn1bFlNGDjk3NIYLVvN52nQhwbgT4
=/bWL
-END PGP SIGNATURE End Message ---

Bug#747726: SIGSGV in gfxContext::PushGroupAndCopyBackground on zoom

[Mike Hommey]

severity 747726 important
thanks

On Sun, May 11, 2014 at 02:10:33PM +0200, Kai Wasserbäch wrote:
> Package: iceweasel
> Version: 29.0-2
> Severity: grave
> Tags: upstream
> 
> Dear maintainers,
> visiting [0] and pressing Ctrl + + three times in a row reliably crashes
> iceweasel. Attached you'll find a backtrace of this issue.
> 
> The crash also happens in safe-mode from which I've attached the GDB
> backtrace and register dump. The crash also happens with a vanilla amd64
> build from upstream (I've tested their 29.0.1). I triggered the crash
> reporter, but I don't see the report yet on the crash stats page. Anyway
> it should show up in the reports tab of [1], which already contains some
> other reports, including at least three, that seem to happen on nybooks.com.
> 
> Let me know, if you need something else.
> 
> Kind regards,
> Kai Wasserbäch
> 
> 
> [0] 
> 
> [1] 
> 

Considering the low number of reports, and the fact that i can't
reproduce, I'm tempted to say this is *very* environment/hardware related.

Downgrading severity accordingly.

Mike


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: found 739304 in 0.7.3-2, closing 739304, tagging 739304

[Debian Bug Tracking System]

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

> found 739304 0.7.3-2
Bug #739304 [harvid] FTBFS with libav10
Marked as found in versions harvid/0.7.3-2.
> close 739304 0.7.3-3
Bug #739304 [harvid] FTBFS with libav10
Marked as fixed in versions harvid/0.7.3-3.
Bug #739304 [harvid] FTBFS with libav10
Marked Bug as done
> tags 739304 + sid jessie
Bug #739304 {Done: Sebastian Ramacher } [harvid] FTBFS 
with libav10
Added tag(s) sid and jessie.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747733: ruby-heckle: incompatible with ruby-parser >= 3.0

[Cédric Boutillier]

Package: ruby-heckle
Followup-For: Bug #747733

This bug is not specific to ruby2.1. According to its metadata file,
ruby-heckle requires ruby-parser at version 2.3.1. Its source code
relies on the :scope kind of nodes provided by ruby-parser in that
version.

But ruby-parser 3.0 dropped support for those :scope nodes. Newer
versions of ruby-parser broke ruby-heckle. Since upstream is not very
active, probably the way forward is to remove this package...

Cheers,

Cédric


signature.asc
Description: Digital signature

Bug#747797: totem-plugin-arte: FTBFS: error: The name `action_error' does not exist in the context of `Totem.Object'

[Nicolas Delvaux]

Hi and thank you for the report.


The package FTBS because Totem 3.12 dropped support for "traditional"
plugins like totem-plugin-arte.
I don't know yet if there will be a new upstream version of
totem-plugin-arte that will fix this FTBS.

Porting the project to the Grilo API will require some work/time and the
result should not be specific to Totem anymore (so the current
"totem-plugin-arte" package may become irrelevant).


I think we should wait a bit before doing anything on the Debian side.


Regards,
Nicolas


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747704: marked as done (mesa-vdpau-drivers:amd64: playback does not work with LLVM 3.4.1)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 21:23:03 +
with message-id 
and subject line Bug#747701: fixed in llvm-toolchain-3.4 1:3.4.1-2
has caused the Debian Bug report #747701,
regarding mesa-vdpau-drivers:amd64: playback does not work with LLVM 3.4.1
to be marked as done.

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

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


-- 
747701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mesa-vdpau-drivers
Version: 10.1.2-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

todays update pulled LLVM 3.4.1 on my machine and no playback utilizing
the VDPAU backend fails with

  Failed to open VDPAU backend libLLVM-3.4.so.1: cannot open shared
  object file: No such file or directory

Since libllvm3.4 version 1:3.4.1-1 does not provide libLLVM-3.4.so.1
anymore this is either a problem with mesa, ergo mesa should be rebuild
against the new LLVM version or since LLVM 3.4.1 is only a bugfix
release it should provide a symlink from
/usr/lib/x86_64-linux-gnu/libLLVM-3.4.so.1
-> /usr/lib/x86_64-linux-gnu/libLLVM-3.4.1.so.1 ans it is a bug in the
libllvm3.4 package. If the later is the case, please consider
reassigning it and accept my apologies for the noise.


With best regards,
Julian Wollrath

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

Kernel: Linux 3.15.0-rc5 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mesa-vdpau-drivers:amd64 depends on:
ii  libc6  2.18-5
ii  libdrm-nouveau22.4.54-1
ii  libdrm-radeon1 2.4.54-1
ii  libdrm22.4.54-1
ii  libelf10.158-2
ii  libexpat1  2.1.0-4
ii  libffi63.1~rc1+r3.0.13-12
ii  libgcc11:4.9.0-2
ii  libllvm3.4 1:3.4.1-1
ii  libstdc++6 4.9.0-2
ii  libtinfo5  5.9+20140118-1
ii  libvdpau1  0.7-2
ii  libx11-6   2:1.6.2-1
ii  libx11-xcb12:1.6.2-1
ii  libxcb-dri2-0  1.10-2
ii  libxcb11.10-2
ii  multiarch-support  2.18-5

mesa-vdpau-drivers:amd64 recommends no packages.

mesa-vdpau-drivers:amd64 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJTbz7MAAoJEFl2dmpRMS8zRZoIAJd0oH7sMapY1nNnn7x71BMp
v4lR7lCcVVw9Z69muhm04jW/lwftBEFgl6sThdIfd+huHBJcA1TfKxIxvzTGcpEz
6ZPorCwGH6lr2UF+tnHn+0uSmNJznoZSQHYirEIHcM3bH0/7tIW8CzlogWNrm8hC
o738AOUcZ1VIbXGPaJQVd9rYN7KhLJpr6DMfLaBgSkOIOO6v7YUoRQ99byzw9C+w
cDcSFbSXAPLMjQujCIceHTGi2ebDPTzkN/tuRan7M2EASu0jy0bNxabpQyiUlxY/
1YmZW+Ko9204ZouR03I74pRAFMbdzjAa4wv6xfAAt62Qcv7szgL4lIcUmX3V24U=
=rQvQ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-3.4
Source-Version: 1:3.4.1-2

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-3.4 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 May 2014 17:29:22 +0200
Source: llvm-toolchain-3.4
Binary: clang-3.4 clang-format-3.4 cpp11-migrate-3.4 clang-modernize-3.4 
clang-3.4-doc libclang1-3.4 libclang1-3.4-dbg libclang-3.4-dev 
libclang-common-3.4-dev python-clang-3.4 clang-3.4-examples libllvm3.4 
libllvm3.4-dbg llvm-3.4 llvm-3.4-runtime llvm-3.4-dev llvm-3.4-tools 
libllvm-3.4-ocaml-dev llvm-3.4-doc llvm-3.4-examples lldb-3.4 lldb-3.4-dev
Architecture: source amd64 all
Version: 1:3.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description: 
 clang-3.4  - C, C++ and Objective-C compiler (LLVM based)
 clang-3.4-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation
 clang-3.4-examples - Clang examples
 clang-format-3.4 - Tool to format C/C++/Obj-C code
 clang-modernize-3.4 - Tool to convert C++98 and C++03 c

Bug#747393: marked as done (libsdformat2 and libsdformat1: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 21:23:54 +
with message-id 
and subject line Bug#747393: fixed in sdformat 2.0.0-3
has caused the Debian Bug report #747393,
regarding libsdformat2 and libsdformat1: error when trying to install together
to be marked as done.

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

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


-- 
747393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsdformat1,libsdformat2
Version: libsdformat1/1.4.11-1
Version: libsdformat2/2.0.0-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2014-05-08
Architecture: amd64
Distribution: sid

Hi,

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


Selecting previously unselected package libboost-system1.54.0:amd64.
(Reading database ... 10937 files and directories currently installed.)
Preparing to unpack .../libboost-system1.54.0_1.54.0-5_amd64.deb ...
Unpacking libboost-system1.54.0:amd64 (1.54.0-5) ...
Selecting previously unselected package libboost-filesystem1.54.0:amd64.
Preparing to unpack .../libboost-filesystem1.54.0_1.54.0-5_amd64.deb ...
Unpacking libboost-filesystem1.54.0:amd64 (1.54.0-5) ...
Selecting previously unselected package libboost-program-options1.54.0:amd64.
Preparing to unpack .../libboost-program-options1.54.0_1.54.0-5_amd64.deb ...
Unpacking libboost-program-options1.54.0:amd64 (1.54.0-5) ...
Selecting previously unselected package libicu52:amd64.
Preparing to unpack .../libicu52_52.1-3_amd64.deb ...
Unpacking libicu52:amd64 (52.1-3) ...
Selecting previously unselected package libboost-regex1.54.0:amd64.
Preparing to unpack .../libboost-regex1.54.0_1.54.0-5_amd64.deb ...
Unpacking libboost-regex1.54.0:amd64 (1.54.0-5) ...
Selecting previously unselected package libboost-thread1.54.0:amd64.
Preparing to unpack .../libboost-thread1.54.0_1.54.0-5_amd64.deb ...
Unpacking libboost-thread1.54.0:amd64 (1.54.0-5) ...
Selecting previously unselected package libtinyxml2.6.2:amd64.
Preparing to unpack .../libtinyxml2.6.2_2.6.2-2_amd64.deb ...
Unpacking libtinyxml2.6.2:amd64 (2.6.2-2) ...
Selecting previously unselected package libconsole-bridge0.2:amd64.
Preparing to unpack .../libconsole-bridge0.2_0.2.5-2_amd64.deb ...
Unpacking libconsole-bridge0.2:amd64 (0.2.5-2) ...
Selecting previously unselected package liburdfdom-model-state0.2:amd64.
Preparing to unpack .../liburdfdom-model-state0.2_0.2.10+dfsg-1_amd64.deb ...
Unpacking liburdfdom-model-state0.2:amd64 (0.2.10+dfsg-1) ...
Selecting previously unselected package liburdfdom-model0.2:amd64.
Preparing to unpack .../liburdfdom-model0.2_0.2.10+dfsg-1_amd64.deb ...
Unpacking liburdfdom-model0.2:amd64 (0.2.10+dfsg-1) ...
Selecting previously unselected package liburdfdom-sensor0.2:amd64.
Preparing to unpack .../liburdfdom-sensor0.2_0.2.10+dfsg-1_amd64.deb ...
Unpacking liburdfdom-sensor0.2:amd64 (0.2.10+dfsg-1) ...
Selecting previously unselected package liburdfdom-world0.2:amd64.
Preparing to unpack .../liburdfdom-world0.2_0.2.10+dfsg-1_amd64.deb ...
Unpacking liburdfdom-world0.2:amd64 (0.2.10+dfsg-1) ...
Selecting previously unselected package libsdformat1:amd64.
Preparing to unpack .../libsdformat1_1.4.11-1_amd64.deb ...
Unpacking libsdformat1:amd64 (1.4.11-1) ...
Selecting previously unselected package liburdfdom-model-state0.3:amd64.
Preparing to unpack .../liburdfdom-model-state0.3_0.3.0-1_amd64.deb ...
Unpacking liburdfdom-model-state0.3:amd64 (0.3.0-1) ...
Selecting previously unselected package liburdfdom-model0.3:amd64.
Preparing to unpack .../liburdfdom-model0.3_0.3.0-1_amd64.deb ...
Unpacking liburdfdom-model0.3:amd64 (0.3.0-1) ...
Selecting previously unselected package liburdfdom-sensor0.3:amd64.
Preparing to unpack .../liburdfdom-sensor0.3_0.3.0-1_amd64.deb ...
Unpacking liburdfdom-sensor0.3:amd64 (0.3.0-1) ...
Selecting previously unselected package liburdfdom-world0.3:amd64.
Preparing to unpack .../liburdfdom-world0.3_0.3.0-1_amd64.deb ...
Unpacking liburdfdom-world0.3:amd64 (0.3.0-1) ...
Selecting previously unselected package libsdformat2:amd64.
Preparing to unpack .../libsdformat2_2.0.0-2_amd64.deb ...
Unpacking libsdformat2:amd64 (2.0.0-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/libsdformat2_2.0.0-2_amd64.deb (--unpack):
 trying to overwrite '/usr/share/sdformat/1.3/model.sdf', which is also in 
package libsdformat1:amd64 1.4.11-1
Errors were encountered while processing:
 /var/cache/apt/archives/libsdformat2_2.0.0-2_amd64.deb
E:

Bug#747361: marked as done (sdformat: FTBFS: most odd-numbered tests time out)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 21:23:54 +
with message-id 
and subject line Bug#747361: fixed in sdformat 2.0.0-3
has caused the Debian Bug report #747361,
regarding sdformat: FTBFS: most odd-numbered tests time out
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.)


-- 
747361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sdformat
Version: 2.0.0-1
Severity: serious
Justification: fails to build from source

Automated builds of sdformat have all been encountering test timeouts,
in a distinctive pattern:

  The following tests FAILED:
  1 - INTEGRATION_audio (Timeout)
  3 - INTEGRATION_cfm_damping_implicit_spring_damper (Timeout)
  5 - INTEGRATION_fixed_joint_reduction (Timeout)
  7 - INTEGRATION_joint_axis_frame (Timeout)
  9 - INTEGRATION_provide_feedback (Timeout)
  11 - PERFORMANCE_parser_urdf (Timeout)
  13 - UNIT_SDF_TEST (Timeout)
  15 - UNIT_Console_TEST (Timeout)
  19 - UNIT_parser_urdf_TEST (Timeout)

It's not clear why, but I do see that the tests were always running in
parallel; could they somehow interfere with each other?  At any rate,
please do take a look.

Thanks!
--- End Message ---
--- Begin Message ---
Source: sdformat
Source-Version: 2.0.0-3

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated sdformat 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 09 May 2014 19:35:55 +
Source: sdformat
Binary: libsdformat2 libsdformat-dev libsdformat2-dbg sdformat-doc
Architecture: source amd64 all
Version: 2.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description: 
 libsdformat-dev - Simulation Description Format (SDF) parser - Development 
files
 libsdformat2 - Simulation Description Format (SDF) parser - Shared library
 libsdformat2-dbg - Simulation Description Format (SDF) parser - Debugging 
symbols
 sdformat-doc - Simulation Description Format (SDF) parser - Documentation
Closes: 747361 747393
Changes: 
 sdformat (2.0.0-3) unstable; urgency=medium
 .
   * [f03ab47] Conflict with libsdformat1. (Closes: #747393)
   * [2f73b57] Restrict test suite only to amd64 (Closes: #747361)
   * [2b207c6] Support for autopkgtest
Checksums-Sha1: 
 fddef9535ebecee3c86e6bfba6233205ce46e450 2379 sdformat_2.0.0-3.dsc
 cd3e84292463abb3870dab03bcfdb6651716bdd6 10556 sdformat_2.0.0-3.debian.tar.xz
 2279f73f3012b75655632db0bdd81589bd0d8cb5 212150 libsdformat2_2.0.0-3_amd64.deb
 d635c50753530e467c657f233197e03d19681859 16500 
libsdformat-dev_2.0.0-3_amd64.deb
 98cc9decefaa56a43e010dbfda9b9b3990e21088 1624040 
libsdformat2-dbg_2.0.0-3_amd64.deb
 d3fd0f8d638db1d4c192f0a63deb42be40c69f3a 119170 sdformat-doc_2.0.0-3_all.deb
Checksums-Sha256: 
 925f2bd12b4a4d9d3ffa4093734ce2830aac5068cc8455dad467cf6cd8e7ddb3 2379 
sdformat_2.0.0-3.dsc
 5e5a44de2e0145aa3bffacc803fa46c26c78994b51d7e287cb23036813b63ca8 10556 
sdformat_2.0.0-3.debian.tar.xz
 696f8077e341c1ddfa80e8a8558c8c5e27f3dd110ef1b73e592f99ff1620037a 212150 
libsdformat2_2.0.0-3_amd64.deb
 0e7ca54c8022f89a4e3b4297c2a89887a358d38c38a67eb18a439510d14852bf 16500 
libsdformat-dev_2.0.0-3_amd64.deb
 6ce1973f17f37f4d6d1ec19930bac958a0b3394fbd6ab943aa2e19b3ccf4f4dd 1624040 
libsdformat2-dbg_2.0.0-3_amd64.deb
 11f42b9acdc082832a70a100c189c376a245beb76f51024c1cf06547927c77cb 119170 
sdformat-doc_2.0.0-3_all.deb
Files: 
 03ba394529611af4a2a350a58df04ff0 212150 libs extra 
libsdformat2_2.0.0-3_amd64.deb
 4d99aa861251d683d5faea9f5739353a 16500 libdevel extra 
libsdformat-dev_2.0.0-3_amd64.deb
 68ab696ef556c3cbce43ef7a03802c4e 1624040 debug extra 
libsdformat2-dbg_2.0.0-3_amd64.deb
 0433bdc06c68aa6364c261e4c27e4de1 119170 doc extra sdformat-doc_2.0.0-3_all.deb
 33809fefc2588cae1a10354adec2fd59 2379 science extra sdformat_2.0.0-3.dsc
 f2f1676f17c31afb0114d09e0bcf39bb 10556 science extra 
s

Bug#747701: marked as done (libgl1-mesa-dri: Broken by upgrade to libllvm3.4 1:3.4.1-1)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 21:23:03 +
with message-id 
and subject line Bug#747701: fixed in llvm-toolchain-3.4 1:3.4.1-2
has caused the Debian Bug report #747701,
regarding libgl1-mesa-dri: Broken by upgrade to libllvm3.4 1:3.4.1-1
to be marked as done.

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

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


-- 
747701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgl1-mesa-dri
Version: 10.1.2-1
Severity: normal

ld /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so gives the following:
/usr/bin/ld.bfd.real: warning: libLLVM-3.4.so.1, needed by
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so, not found

Can you recompile/relink with libLLVM-3.4.1.so.1?
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-3.4
Source-Version: 1:3.4.1-2

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-3.4 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 May 2014 17:29:22 +0200
Source: llvm-toolchain-3.4
Binary: clang-3.4 clang-format-3.4 cpp11-migrate-3.4 clang-modernize-3.4 
clang-3.4-doc libclang1-3.4 libclang1-3.4-dbg libclang-3.4-dev 
libclang-common-3.4-dev python-clang-3.4 clang-3.4-examples libllvm3.4 
libllvm3.4-dbg llvm-3.4 llvm-3.4-runtime llvm-3.4-dev llvm-3.4-tools 
libllvm-3.4-ocaml-dev llvm-3.4-doc llvm-3.4-examples lldb-3.4 lldb-3.4-dev
Architecture: source amd64 all
Version: 1:3.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description: 
 clang-3.4  - C, C++ and Objective-C compiler (LLVM based)
 clang-3.4-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation
 clang-3.4-examples - Clang examples
 clang-format-3.4 - Tool to format C/C++/Obj-C code
 clang-modernize-3.4 - Tool to convert C++98 and C++03 code to C++11
 cpp11-migrate-3.4 - Tool to convert C++98 and C++03 code to C++11
 libclang-3.4-dev - clang library - Development package
 libclang-common-3.4-dev - clang library - Common development package
 libclang1-3.4 - C interface to the clang library
 libclang1-3.4-dbg - clang library
 libllvm-3.4-ocaml-dev - Modular compiler and toolchain technologies, OCaml 
bindings
 libllvm3.4 - Modular compiler and toolchain technologies, runtime library
 libllvm3.4-dbg - Modular compiler and toolchain technologies, debugging 
libraries
 lldb-3.4   - Next generation, high-performance debugger
 lldb-3.4-dev - Next generation, high-performance debugger - Header files
 llvm-3.4   - Modular compiler and toolchain technologies
 llvm-3.4-dev - Modular compiler and toolchain technologies, libraries and 
header
 llvm-3.4-doc - Modular compiler and toolchain technologies, documentation
 llvm-3.4-examples - Modular compiler and toolchain technologies, examples
 llvm-3.4-runtime - Modular compiler and toolchain technologies, IR interpreter
 llvm-3.4-tools - Modular compiler and toolchain technologies, tools
 python-clang-3.4 - Clang Python Bindings
Closes: 747701
Changes: 
 llvm-toolchain-3.4 (1:3.4.1-2) unstable; urgency=medium
 .
   * Fix the soname. No changes in the ABI, so, no need to update the soname
 (Closes: #747701)
Checksums-Sha1: 
 02a18f3a95039e07fd71131f566d3acb2d47c5db 5492 llvm-toolchain-3.4_3.4.1-2.dsc
 fc6950dd9c5691d9263fe9eb379b81599fcf0b2a 44412 
llvm-toolchain-3.4_3.4.1-2.debian.tar.xz
 1ecdf60be0a6ac7bbbdfb5135c3f83b84d8bcdb3 18540170 clang-3.4_3.4.1-2_amd64.deb
 608fbbc244671f816944fbdcf879afd7d586abd7 3104156 
clang-format-3.4_3.4.1-2_amd64.deb
 f5303d6fd0cf4c19700c56634a49b0ffe4da14f7 11800 
cpp11-migrate-3.4_3.4.1-2_amd64.deb
 156541885fcd82611829093f4e15fe4e9e2af8c2 3296886 
clang-modernize-3.4_3.4.1-2_amd64.deb
 1a38af19da4ea9028142ff60120b7e6fe6d24f5d 471384 clang-3.4-doc_3.4.1-2_all.deb
 f99d1784457a45c4265aeda8bfe3ec657f608642 3524964 
libclang1-3.4_3.4.1-2_amd64.deb
 7ff6e214a7b83580b983e6eef1a94583f7d2ed13 97122034 
libclang1-3.4-dbg_3.4.1-2_amd64.deb

Bug#747759: marked as done (libdrm2: (EE) AIGLX error: dlopen of r600_dri.so failed)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 21:23:03 +
with message-id 
and subject line Bug#747701: fixed in llvm-toolchain-3.4 1:3.4.1-2
has caused the Debian Bug report #747701,
regarding libdrm2: (EE) AIGLX error: dlopen of r600_dri.so failed
to be marked as done.

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

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


-- 
747701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdrm2
Version: 2.4.54-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?

upgrading libdrm2.

Now on X startup getting:

[48.745] (EE) AIGLX error: dlopen of 
/usr/lib/x86_64-linux-gnu/dri/r600_dri.so failed (libLLVM-3.4.so.1: cannot open 
shared object file: No such file or directory)
[48.745] (EE) AIGLX: reverting to software rendering
[48.787] (EE) AIGLX error: dlopen of 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed (libLLVM-3.4.so.1: cannot 
open shared object file: No such file or directory)
[48.787] (EE) GLX: could not load software renderer

even though those shared libraries exist.

Applications using opengl now fail.

$ glxinfo
name of display: :0
Error: couldn't find RGB GLX visual or fbconfig
Error: couldn't find RGB GLX visual or fbconfig

I'm happy to help troubleshoot but not sure which of these packages just
upgraded were the culprit(s):

[UPGRADE] libdrm-dev:amd64 2.4.53-1 -> 2.4.54-1
[UPGRADE] libdrm-intel1:amd64 2.4.53-1 -> 2.4.54-1
[UPGRADE] libdrm-nouveau2:amd64 2.4.53-1 -> 2.4.54-1
[UPGRADE] libdrm-radeon1:amd64 2.4.53-1 -> 2.4.54-1
[UPGRADE] libdrm-radeon1-dbg:amd64 2.4.53-1 -> 2.4.54-1
[UPGRADE] libdrm2:amd64 2.4.53-1 -> 2.4.54-1
[UPGRADE] libdrm2-dbg:amd64 2.4.53-1 -> 2.4.54-1
[UPGRADE] libllvm3.4:amd64 1:3.4-2 -> 1:3.4.1-1
[UPGRADE] libva-dev:amd64 1.3.0-2 -> 1.3.1-1
[UPGRADE] libva-drm1:amd64 1.3.0-2 -> 1.3.1-1
[UPGRADE] libva-egl1:amd64 1.3.0-2 -> 1.3.1-1
[UPGRADE] libva-glx1:amd64 1.3.0-2 -> 1.3.1-1
[UPGRADE] libva-tpi1:amd64 1.3.0-2 -> 1.3.1-1
[UPGRADE] libva-wayland1:amd64 1.3.0-2 -> 1.3.1-1
[UPGRADE] libva-x11-1:amd64 1.3.0-2 -> 1.3.1-1
[UPGRADE] libva1:amd64 1.3.0-2 -> 1.3.1-1
[UPGRADE] llvm-3.4:amd64 1:3.4-2 -> 1:3.4.1-1
[UPGRADE] llvm-3.4-runtime:amd64 1:3.4-2 -> 1:3.4.1-1

video card is a Radeon 3850HD (RV670):

[47.359] (--) RADEON(0): Chipset: "ATI Radeon HD3850" (ChipID = 0x9505)

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


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

Kernel: Linux 3.15.0-rc5+ (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libdrm2 depends on:
ii  libc6  2.18-5
ii  multiarch-support  2.18-5

libdrm2 recommends no packages.

libdrm2 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-3.4
Source-Version: 1:3.4.1-2

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-3.4 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 May 2014 17:29:22 +0200
Source: llvm-toolchain-3.4
Binary: clang-3.4 clang-format-3.4 cpp11-migrate-3.4 clang-modernize-3.4 
clang-3.4-doc libclang1-3.4 libclang1-3.4-dbg libclang-3.4-dev 
libclang-common-3.4-dev python-clang-3.4 clang-3.4-examples libllvm3.4 
libllvm3.4-dbg llvm-3.4 llvm-3.4-runtime llvm-3.4-dev llvm-3.4-tools 
libllvm-3.4-ocaml-dev llvm-3.4-doc llvm-3.4-examples lldb-3.4 lldb-3.4-dev
Architecture: source amd64 all
Version: 1:3.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description: 
 clang-3.4  - C, C++ and Objective-C compiler (LLVM based)
 clang-3.4-doc - C, C++ and O

Bug#747828: iceweasel: the UI is completely broken: no menu bar, no status bar...

[Vincent Lefevre]

Package: iceweasel
Version: 29.0.1-1
Severity: grave
Justification: renders package unusable

After upgrading to iceweasel 29.0.1-1, the UI got completely broken:
the menu bar no longer appears, the status bar is absent as well, and
the user config has completely been modified.

BTW, I can't test with "iceweasel -no-remote -safe-mode" as it no longer
works at all. I get the following error:

  Iceweasel is already running, but is not responding. To open a new
  window, you must first close the existing Iceweasel process, or
  restart your system.

-- Package-specific info:

-- Extensions information
Name: -Global Styles- userstyle
Status: enabled

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

Name: Add-on Compatibility Reporter
Location: ${PROFILE_EXTENSIONS}/compatibil...@addons.mozilla.org.xpi
Status: enabled

Name: AlloCiné userstyle
Status: enabled

Name: Bamboo Feed Reader
Location: ${PROFILE_EXTENSIONS}/{b2e69492-2358-071a-7056-24ad0c3defb1}
Status: enabled

Name: Cinémathèque Française userstyle
Status: enabled

Name: Combine Stop/Reload buttons userstyle
Status: enabled

Name: DOM Inspector
Location: ${PROFILE_EXTENSIONS}/inspec...@mozilla.org
Status: enabled

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

Name: Dictionnaire français «Moderne»
Location: ${PROFILE_EXTENSIONS}/fr-mode...@dictionaries.addons.mozilla.org
Status: enabled

Name: Different cursor for links that open in new windows userstyle
Status: enabled

Name: Disable autocomplete userstyle
Status: user-disabled

Name: Disable marquee userstyle
Status: user-disabled

Name: DownloadHelper
Location: ${PROFILE_EXTENSIONS}/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}
Status: enabled

Name: Ecosia - The search engine that plants trees
Location: ${PROFILE_EXTENSIONS}/{d04b0b40-3dab-4f0b-97a6-04ec3eddbfb0}.xpi
Status: user-disabled

Name: Firebug
Location: ${PROFILE_EXTENSIONS}/fire...@software.joehewitt.com.xpi
Status: enabled

Name: Flagfox
Location: ${PROFILE_EXTENSIONS}/{1018e4d6-728f-4b20-ad56-37578a4de76b}.xpi
Status: enabled

Name: Flashblock
Location: ${PROFILE_EXTENSIONS}/{3d7eb24f-2740-49df-8937-200b1cc08f8a}
Status: enabled

Name: Font Finder
Location: ${PROFILE_EXTENSIONS}/fontfin...@bendodson.com.xpi
Status: enabled

Name: Forecastfox
Location: ${PROFILE_EXTENSIONS}/{0538E3E3-7E9B-4d49-8831-A227C80A7AD3}
Status: app-disabled

Name: FxIF
Location: ${PROFILE_EXTENSIONS}/{11483926-db67-4190-91b1-ef20fcec5f33}.xpi
Status: enabled

Name: GLPI - assistance.ens-lyon.fr userstyle
Status: enabled

Name: Google Search userstyle
Status: enabled

Name: Greasemonkey
Location: ${PROFILE_EXTENSIONS}/{e4a8a97b-f2ed-450b-b12d-ee082ba24781}.xpi
Status: enabled

Name: HeadingsMap
Location: ${PROFILE_EXTENSIONS}/headi...@niquelheadings.net.xpi
Status: enabled

Name: IMDb userstyle
Status: enabled

Name: Link Widgets
Location: ${PROFILE_EXTENSIONS}/linkwid...@clav.mozdev.org
Status: enabled

Name: Live HTTP headers
Location: ${PROFILE_EXTENSIONS}/{8f8fe09b-0bd3-4470-bc1b-8cad42b8203a}
Status: enabled

Name: MemChaser
Location: ${PROFILE_EXTENSIONS}/memcha...@quality.mozilla.org.xpi
Status: enabled

Name: Move tabbar to the bottom userstyle
Status: user-disabled

Name: Move tabbar to the left userstyle
Status: user-disabled

Name: Move tabbar to the right userstyle
Status: user-disabled

Name: Multiple row bookmark toolbar userstyle
Status: user-disabled

Name: Nerim userstyle
Status: enabled

Name: Open in Browser
Location: ${PROFILE_EXTENSIONS}/openinbrow...@www.spasche.net.xpi
Status: enabled

Name: PeopleForCinema userstyle
Status: enabled

Name: Pinger
Location: ${PROFILE_EXTENSIONS}/jane...@pinger.xpi
Status: enabled

Name: QuickWiki
Location: ${PROFILE_EXTENSIONS}/{EE223D7A-F30F-11DD-8F0A-D2AD55D89593}.xpi
Status: enabled

Name: SearchStatus
Location: ${PROFILE_EXTENSIONS}/{d57c9ff1-6389-48fc-b770-f78bd89b6e8a}.xpi
Status: enabled

Name: Showcase
Location: ${PROFILE_EXTENSIONS}/{89506680-e3f4-484c-a2c0-ed711d481eda}.xpi
Status: enabled

Name: Slashdot.org - Remove ads userstyle
Status: enabled

Name: SourceForge font size in comments userstyle
Status: enabled

Name: Stylish
Location: ${PROFILE_EXTENSIONS}/{46551EC9-40F0-4e47-8E18-8E5CF550CFB8}.xpi
Status: enabled

Name: Stylish-Custom
Location: ${PROFILE_EXTENSIONS}/stylish-cus...@choggi.dyndns.org
Status: enabled

Name: Tab Mix Plus
Location: ${PROFILE_EXTENSIONS}/{dc572301-7619-498c-a57d-39143191b318}.xpi
Status: enabled

Name: TinEye Reverse Image Search
Location: ${PROFILE_EXTENSIONS}/tin...@ideeinc.com
Status: enabled

Name: United States English Spellchecker dictionary
Location: ${PROFILE_EXTENSIONS}/en...@dictionaries.addons.mozilla.org
Status: enabled

Name: Web Developer
Location: ${PROFILE_EXTENSIONS}/{c45c406e-ab73-11d8-be73-000a95be3b12}.xpi
Status: enabled

Name: Wikipedia font size userstyle
Status: enabled

Name: X-Ray
Locatio

Processed: severity of 746587 is serious, affects 746587

[Debian Bug Tracking System]

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

> severity 746587 serious
Bug #746587 [initscripts] Use systemd built-in mechanisms for mounting remote 
file systems like NFS during early boot
Severity set to 'serious' from 'important'
> affects 746587 systemd
Bug #746587 [initscripts] Use systemd built-in mechanisms for mounting remote 
file systems like NFS during early boot
Added indication that 746587 affects systemd
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: retitle 739332 to survex: Needs rebuilding with libav10

[Debian Bug Tracking System]

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

> retitle 739332 survex: Needs rebuilding with libav10
Bug #739332 [src:survex] FTBFS with libav10
Changed Bug title to 'survex: Needs rebuilding with libav10' from 'FTBFS with 
libav10'
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#735339: boost1.54 Non free w3c valid icons

[Dimitri John Ledkov]

This has now been fixed in boost1.55. I don't intend to fix this in
boost1.54, as boost1.54 shouldn't ship with Jessie, instead everything
should migrate to boost1.55.

-- 
Regards,

Dimitri.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: unarchiving 734187, found 734187 in 3.8.4-2

[Debian Bug Tracking System]

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

> unarchive 734187
Bug #734187 {Done: Andreas Henriksson } [gnome-documents] 
gnome-documents: Failed to start gnome-documents
Unarchived Bug 734187
> found 734187 3.8.4-2
Bug #734187 {Done: Andreas Henriksson } [gnome-documents] 
gnome-documents: Failed to start gnome-documents
Marked as found in versions gnome-documents/3.8.4-2.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#602724: please remove kfreebsd-any from Architecture

[Robert Millan]

On 11/05/14 21:06, Julien Cristau wrote:

On Sun, May 11, 2014 at 17:37:29 +0200, Robert Millan wrote:


I've uploaded an NMU with the removal of "kfreebsd-any" (and "hurd-any"
as per porter's request) from Architecture. A debdiff is attached.


Do you plan on also handling the reverse dependencies (with binary
removals and/or patches, as appropriate)?


That's something I'm responsible for.

Thanks for the reminder.

--
Robert Millan


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747826: obexftp: FTBFS on sid/amd64: cannot create regular file '/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/obexftp.so': Permission denied

[Niko Tyni]

Package: obexftp
Version: 0.23-1.3
Severity: serious
X-Debbugs-Cc: ruby...@packages.debian.org

This package fails to build on current sid/amd64:

  Making install in ruby
  make[3]: Entering directory '/tmp/buildd/obexftp-0.23/swig/ruby'
  make[4]: Entering directory '/tmp/buildd/obexftp-0.23/swig/ruby'
  make[4]: Nothing to be done for 'install-exec-am'.
  /usr/bin/make -j1 -fMakefile.ruby install
  make[5]: Entering directory '/tmp/buildd/obexftp-0.23/swig/ruby'
  /usr/bin/install -c -m 0755 obexftp.so 
/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0
  /usr/bin/install: cannot create regular file 
'/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/obexftp.so': Permission denied
  Makefile.ruby:184: recipe for target 'install-so' failed
  make[5]: *** [install-so] Error 1
  make[5]: Leaving directory '/tmp/buildd/obexftp-0.23/swig/ruby'
  Makefile:376: recipe for target 'install-data-local' failed
  make[4]: *** [install-data-local] Error 2
  make[4]: Leaving directory '/tmp/buildd/obexftp-0.23/swig/ruby'
  Makefile:290: recipe for target 'install-am' failed
  make[3]: *** [install-am] Error 2
  make[3]: Leaving directory '/tmp/buildd/obexftp-0.23/swig/ruby'
  Makefile:264: recipe for target 'install-recursive' failed
  make[2]: *** [install-recursive] Error 1
  make[2]: Leaving directory '/tmp/buildd/obexftp-0.23/swig'
  Makefile:349: recipe for target 'install-recursive' failed
  make[1]: *** [install-recursive] Error 1
  make[1]: Leaving directory '/tmp/buildd/obexftp-0.23'
  debian/rules:95: recipe for target 'install' failed
  make: *** [install] Error 2
 
I assume this is due to the ongoing Ruby 2.1.0 transition, see #747609.
Cc'ing the Ruby maintainers.
-- 
Niko Tyni   nt...@debian.org


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#746114: marked as done (multiverse-core: FTBFS: Build failures: groovy.lang.MissingMethodException)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 17:31:13 -0300
with message-id <20140511203113.ga23...@alice.nomadium.lan>
and subject line Re: multiverse-core: FTBFS: Build failures: 
groovy.lang.MissingMethodException
has caused the Debian Bug report #746114,
regarding multiverse-core: FTBFS: Build failures: 
groovy.lang.MissingMethodException
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.)


-- 
746114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: multiverse-core
Version: 0.7.0-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140426 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»'
> mkdir /«PKGBUILDDIR»/.gradlehome
> gradle --project-prop finalRelease=true --stacktrace --offline assemble
> java.lang.OutOfMemoryError: Java heap space
>   at java.util.ArrayList.(ArrayList.java:144)
>   at 
> org.codehaus.groovy.reflection.GeneratedMetaMethod$DgmMethodRecord.loadDgmInfo(GeneratedMetaMethod.java:193)
>   at 
> org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.registerMethods(MetaClassRegistryImpl.java:155)
>   at 
> org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.(MetaClassRegistryImpl.java:83)
>   at 
> org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.(MetaClassRegistryImpl.java:61)
>   at groovy.lang.GroovySystem.(GroovySystem.java:29)
>   at 
> org.gradle.api.internal.AbstractClassGenerator.generate(AbstractClassGenerator.java:100)
>   at 
> org.gradle.api.internal.ClassGeneratorBackedInstantiator.newInstance(ClassGeneratorBackedInstantiator.java:36)
>   at 
> org.gradle.initialization.DefaultGradleLauncherFactory.doNewInstance(DefaultGradleLauncherFactory.java:126)
>   at 
> org.gradle.initialization.DefaultGradleLauncherFactory.newInstance(DefaultGradleLauncherFactory.java:99)
>   at 
> org.gradle.initialization.DefaultGradleLauncherFactory.newInstance(DefaultGradleLauncherFactory.java:46)
>   at 
> org.gradle.launcher.exec.InProcessGradleLauncherActionExecuter.execute(InProcessGradleLauncherActionExecuter.java:38)
>   at 
> org.gradle.launcher.exec.InProcessGradleLauncherActionExecuter.execute(InProcessGradleLauncherActionExecuter.java:25)
>   at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:50)
>   at 
> org.gradle.api.internal.Actions$RunnableActionAdapter.execute(Actions.java:171)
>   at 
> org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:201)
>   at 
> org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:174)
>   at 
> org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:170)
>   at 
> org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:139)
>   at 
> org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
>   at 
> org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
>   at org.gradle.launcher.Main.doAction(Main.java:48)
>   at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
>   at org.gradle.launcher.Main.main(Main.java:39)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:50)
>   at 
> org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:32)
>   at org.gradle.launcher.GradleMain.main(GradleMain.java:26)
> 
> FAILURE: Build aborted because of an internal error.
> 
> * What went wrong:
> Build aborted because of an unexpected internal error. Please file an issue 
> at: http://forums.gradle.org.
> 
> * Try:
> Run with --debug option to get additional debug info.
> 
> * Exception is:
> groovy.lang.MissingMethodException: No signature of method: 
> org.gradle.util.MutableURLClassLoader.invokeMethod() is applicable for 
> argument types: (java.lang.String, [Ljava.lang.Object;) values: [defineClass, 
> [org.gradle.initializa

Bug#747709: FTBFS: cannot stat 'debian/tmp/usr/lib/xmms2/libxmms_airplay.so'

[Benjamin Drung]

Am Sonntag, den 11.05.2014, 21:52 +0200 schrieb Rémi Vanicat:
> I've a fix: it has nothing to do with ruby, but came probably from a
> change in dependency in libcurl4-openssl-dev.
> 
> I have to wait for libav10 to land on my local mirror to upload the
> fix. 
> 
> Benjamin: I seem unable to push on alioth tonight. So I've attached the
> commit, to be applied after the change in the 9.1 NMU.

Thanks Rémi for taking care of xmms2. Do you have the patch for the 9.1
NMU which I can apply with git am?

-- 
Benjamin Drung
Debian & Ubuntu Developer


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747502: Pending fixes for bugs in the libcatalyst-modules-perl package

[pkg-perl-maintainers]

tag 747502 + pending
thanks

Some bugs in the libcatalyst-modules-perl package are closed in
revision 5aa21215aad313c5308b4bf37fe4cd03a192e790 in branch ' 
dam-bundle-2.0' by Damyan Ivanov

The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libcatalyst-modules-perl.git;a=commitdiff;h=5aa2121

Commit message:

add patch from John Napiorkowski fixing test failure in 
Catalyst-Plugin-SubRequest with Catalyst 5.9

Closes: #747502 -- FTBFS


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Pending fixes for bugs in the libcatalyst-modules-perl package

[Debian Bug Tracking System]

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

> tag 747502 + pending
Bug #747502 [libcatalyst-modules-perl] FTBFS: test failure in 
Catalyst-Plugin-SubRequest
Added tag(s) pending.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747709: FTBFS: cannot stat 'debian/tmp/usr/lib/xmms2/libxmms_airplay.so'

[Rémi Vanicat]

I've a fix: it has nothing to do with ruby, but came probably from a
change in dependency in libcurl4-openssl-dev.

I have to wait for libav10 to land on my local mirror to upload the
fix. 

Benjamin: I seem unable to push on alioth tonight. So I've attached the
commit, to be applied after the change in the 9.1 NMU.

>From d3d57d27f6fc14683a910f9577f7edbc905008e4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?R=C3=A9mi=20Vanicat?= 
Date: Sun, 11 May 2014 19:46:02 +0200
Subject: [PATCH 2/2] Add a dependency on libssl-dev

Conflicts:
	debian/changelog
---
 debian/changelog | 8 
 debian/control   | 1 +
 2 files changed, 9 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index df0c6fd..ef676b5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+xmms2 (0.8+dfsg-10) unstable; urgency=low
+
+  * Add a build dependency on libssl-dev
+  * Acknowledge NMU. Thanks Reinhard.
+  * compile against libav10 (Closes: #739455)
+
+ -- Rémi Vanicat   Sun, 11 May 2014 21:35:12 +0200
+
 xmms2 (0.8+dfsg-9.1) experimental; urgency=low
 
   * Non-maintainer upload.
diff --git a/debian/control b/debian/control
index b948e4f..8ce7a73 100644
--- a/debian/control
+++ b/debian/control
@@ -15,6 +15,7 @@ Build-Depends: debhelper (>= 9),
libboost-signals-dev,
libcdio-cdda-dev,
libcurl4-openssl-dev,
+   libssl-dev,
libdiscid0-dev,
libexpat1-dev,
libfaad-dev,
-- 
2.0.0.rc2

 
-- 
Rémi Vanicat

Bug#721108: marked as done (tribler: depends on ffmpeg which is going away)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 19:53:05 +
with message-id 
and subject line Bug#721108: fixed in tribler 6.2.0+git20130731.149555fa-2
has caused the Debian Bug report #721108,
regarding tribler: depends on ffmpeg which is going away
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.)


-- 
721108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tribler
Version: 6.0.0+svn20121015.r28821-1
Severity: serious
Justification: renders the package unusable soon

tribler depends on ffmpeg which is no longer built by libav. This will
render the package unusable soon.

tripler needs to be adopted to use avconv (from libav-tools) instead of
ffmpeg.

Regards
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: tribler
Source-Version: 6.2.0+git20130731.149555fa-2

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

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated tribler 
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: Mon, 12 May 2014 02:57:29 +0800
Source: tribler
Binary: tribler tribler-swift
Architecture: source all i386
Version: 6.2.0+git20130731.149555fa-2
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Description: 
 tribler- Python based Bittorrent/Internet TV application
 tribler-swift - Fast peer-to-peer file distribution helper program for tribler.
Closes: 721108
Changes: 
 tribler (6.2.0+git20130731.149555fa-2) unstable; urgency=low
 .
   [ Ying-Chun Liu (PaulLiu)  ]
   * Bump Standards-Version to 3.9.5: nothing needs to be changed.
 .
   [ Tobias Frost  ]
   * Use avconf instead of ffmpeg. See patch use-libav-instead-of-ffmpeg.patch
 (Closes: #721108) and change dependency accordingly to libav-tools
Checksums-Sha1: 
 a2427c11d18e38ffa2e04fdd88969743a52a6626 1977 
tribler_6.2.0+git20130731.149555fa-2.dsc
 d065670ae952bec7f3a815eaade5e6b90b76c3f9 7600 
tribler_6.2.0+git20130731.149555fa-2.debian.tar.xz
 f1b2d37717d2fb24590ff71cbbd2013e49a4dc7b 1293206 
tribler_6.2.0+git20130731.149555fa-2_all.deb
 b53223ff8bdce3f36d7d086b99b823be8b8d3d80 2949360 
tribler-swift_6.2.0+git20130731.149555fa-2_i386.deb
Checksums-Sha256: 
 e5e1e8685afcceb6d75a3531b4faab658fa2f2cfc0805bb4633cf276be58e872 1977 
tribler_6.2.0+git20130731.149555fa-2.dsc
 33bbefc383bd0ae7dda563aec5b6b373c3a06f41b07967e2261674d23b3647f1 7600 
tribler_6.2.0+git20130731.149555fa-2.debian.tar.xz
 077d4953e30762dde61b03d54e07d67bf19d5014d081f64472a8e6d7e724615b 1293206 
tribler_6.2.0+git20130731.149555fa-2_all.deb
 5bf557a60293ce832c1519837d4a6745a4232c3f6061b892535f24791cf0bc05 2949360 
tribler-swift_6.2.0+git20130731.149555fa-2_i386.deb
Files: 
 2c3c09f2dd73570942ec937db49b5e20 1293206 net optional 
tribler_6.2.0+git20130731.149555fa-2_all.deb
 79a4e428484c6d164b624a59264239bd 2949360 net optional 
tribler-swift_6.2.0+git20130731.149555fa-2_i386.deb
 2d9fa3eaec25f3c960c465abc22c4656 1977 net optional 
tribler_6.2.0+git20130731.149555fa-2.dsc
 08222a09360cfa2d67ee149f7e559911 7600 net optional 
tribler_6.2.0+git20130731.149555fa-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJTb9IPAAoJEPgLgUbQQog23+gP/jZZuaNozE3t9o3+qcN6sijh
xC+xiGPNZFEonmMZKgERII3QbvN4XdXLnsibG4KMWyPVWBmjkOS7ShwB5VRXQpnl
/Wg0rqfLl/QPii2eebyXMNugqyP2iHbZrUVOnD8BhBOtFBK9rgc/NFPZm3t1nGj2
kfwcio1kLu72vJ5NkQ3/MKECvB8+rROwg5RKoDvija2KRfqwcVi5iQrjBEooM20p
0Z5Nh5E0uPzl8jvmoehqCvLQMKn++0GEPQRb42DdfaJU7NRHamKGiut3dpBs4U0t
KpgKF6avDN3SEbIl+09yhornU/1zJ83+jUsQQ1dGsrkKmS2Vi0hc63CCbZm16sAf
kAl9ulouNp+U7PcS/0Hy9sfkm5ELnpwCMEYMGLIYFkV/PkJFX/MQFV7U4EI9IUCy
SS43yEcBGBJMJbV+JAQO6Yhz7aYhvJsHSNA6tg7vJ8L9xCht787DS9Mv7dIsQ3yN
szsLJnZEWkYc8wnRx9skDC2mGFcFxRMkgf6EfppSQyj3omuljqBgjnQLaM8k0w1w
9/jQEULWnda7blaA+SaIL4rEq/28iejJy4i/8k1VTjOEOJHAr3VvIP+1wiMEPiU5
WapO3B83KL652hjHeEcdGz56j12h8te/l5ddTghexrn8aa0gfYhn2wSbg1Y8fvXn
bJZCMGWKZU9taHHnJ7UE
=9El5

Bug#747780: syncevolution: FTBFS: error: akonadi.pc not found

[Tino Mettler]

On Sun, May 11, 2014 at 18:45:24 +0200, David Suárez wrote:
> Source: syncevolution
> Version: 1.4-1
> Severity: serious
> Tags: jessie sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20140510 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > checking for rst2html... /usr/bin/rst2html
> > checking for SYNTHESIS... yes
> > checking for GNOMEBLUETOOTH... no
> > checking for qmake... qmake
> > checking Akonadi/Collection usability... no
> > configure: error: akonadi.pc not found. Install it to compile with the 
> > Akonadi backend enabled.
> > checking Akonadi/Collection presence... no
> > checking for Akonadi/Collection... no

The message about a missing akonadi.pc is misleading, upstream is aware
of this.

The full build log revealed this:

configure:21874: checking Akonadi/Collection usability
configure:21874: g++ -c -g -O2 -fPIE -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security
---D_FORTIFY_SOURCE=2 -I/usr/include/ -I/usr/include//KDE
I/usr/include/qt4 conftest.cpp >&5
In file included from
/usr/include//KDE/Akonadi/../../akonadi/collection.h:25:0,
 from /usr/include//KDE/Akonadi/Collection:1,
 from conftest.cpp:80:
/usr/include/akonadi/entity.h:24:19: fatal error: QString: No such file
or directory
 #include 
   ^
compilation terminated.

I'm not sure if this is a syncevolution bug or rather a missing
dependency in kdepimlibs5-dev.  I'd vote for the latter, so I'll
reassign the bug to kdepimlibs5-dev in the next few days if there are
no objections.

Regards,
Tino


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: pending

[Debian Bug Tracking System]

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

> tags 739455 + pending
Bug #739455 [xmms2] FTBFS with libav10
Added tag(s) pending.
> tags 747709 + pending
Bug #747709 [src:xmms2] FTBFS: cannot stat 
'debian/tmp/usr/lib/xmms2/libxmms_airplay.so'
Added tag(s) pending.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#733322: [PATCH] NMU patch for version 0.10.1-1.1 fixing a few bugs in comedilib

[Petter Reinholdtsen]

Package: comedilib
Version: 0.10.1-1.1

I've just uploaded a NMU to the 7 day delayed queue to fix the RC bug
causing xoscope and other packages used by Debian Edu to be removed from
testing.  I fixed a few other issues in the process.

The attached patch is the debdiff for my upload.

-- 
Happy hacking
Petter Reinholdtsen
diff -Nru comedilib-0.10.1/debian/changelog comedilib-0.10.1/debian/changelog
--- comedilib-0.10.1/debian/changelog	2013-08-18 10:32:17.0 +0200
+++ comedilib-0.10.1/debian/changelog	2014-05-11 20:52:06.0 +0200
@@ -1,3 +1,24 @@
+comedilib (0.10.1-1.1) unstable; urgency=low
+
+  * Non-maintainer upload to fix RC bug #733322.
+  * Fix build problem with newer bison (Closes: #733322).  Patch from
+Daniel T Chen and Ubuntu via A. Maitland Bottoms backporting
+upstream changesets 90ce9a9, cc0c9e7, f4e228e, c689eff, and
+2277e82.
+  * Use dh-autoreconf to fix build problem on some architectures
+(Closes: #727345).  Drop now obsolete autotools-dev build
+dependency.  Patch from Daniel T Chen and Ubuntu via A. Maitland
+Bottoms.
+  * Add new executables comedi_soft_calibrate and comedi_board_info to
+the libcomedi1 package (Closes: #711203). Add new directory
+/var/lib/comedi/calibrations to the package, and build using
+--localstatedir=/var to store the state to the correct location.
+Patch from A. Maitland Bottoms.
+  * Adjusted 01_calibrate_build.patch to remove check for comedilib.h too,
+to ensure the comedi-calibrate/configure script work without libcomedi0.
+
+ -- Petter Reinholdtsen   Sun, 11 May 2014 20:52:01 +0200
+
 comedilib (0.10.1-1) unstable; urgency=low
 
   * New upstream release
diff -Nru comedilib-0.10.1/debian/control comedilib-0.10.1/debian/control
--- comedilib-0.10.1/debian/control	2013-04-27 23:12:24.0 +0200
+++ comedilib-0.10.1/debian/control	2014-05-11 14:24:43.0 +0200
@@ -2,7 +2,7 @@
 Section: devel
 Priority: optional
 Maintainer: Gudjon I. Gudjonsson 
-Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1~), python-all-dev, autotools-dev,
+Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1~), python-all-dev, dh-autoreconf,
  swig, docbook-utils, dblatex, bison, flex, libtool, xmlto, imagemagick, fop,
  libboost-program-options-dev, libgsl0-dev, hardening-wrapper
 Standards-Version: 3.9.4
diff -Nru comedilib-0.10.1/debian/libcomedi0.dirs comedilib-0.10.1/debian/libcomedi0.dirs
--- comedilib-0.10.1/debian/libcomedi0.dirs	2012-06-04 01:35:26.0 +0200
+++ comedilib-0.10.1/debian/libcomedi0.dirs	2014-05-11 14:24:43.0 +0200
@@ -6,3 +6,4 @@
 usr/share/doc/libcomedi0/
 etc/pcmcia/
 lib/udev/rules.d/
+var/lib/comedi/calibrations
diff -Nru comedilib-0.10.1/debian/libcomedi0.install comedilib-0.10.1/debian/libcomedi0.install
--- comedilib-0.10.1/debian/libcomedi0.install	2012-06-04 01:35:38.0 +0200
+++ comedilib-0.10.1/debian/libcomedi0.install	2014-05-11 14:53:12.0 +0200
@@ -1,7 +1,9 @@
 usr/lib/libcomedi.so.*
 #usr/lib/ruby/*
 usr/sbin/*
+usr/bin/comedi_board_info
 usr/bin/comedi_calibrate
+usr/bin/comedi_soft_calibrate
 usr/bin/comedi_test
 usr/share/man/man7/*
 usr/share/man/man8/*
diff -Nru comedilib-0.10.1/debian/patches/01_calibrate_build.patch comedilib-0.10.1/debian/patches/01_calibrate_build.patch
--- comedilib-0.10.1/debian/patches/01_calibrate_build.patch	2013-01-20 19:02:21.0 +0100
+++ comedilib-0.10.1/debian/patches/01_calibrate_build.patch	2014-05-11 16:12:00.0 +0200
@@ -1,12 +1,151 @@
 Allows comedi_calibrate to be built without having libcomedi0 installed.
 This is a patch to configure, a machine generated file. A better solution
-without patching machine generated files would be preferable.
 a/comedi-calibrate/configure
-+++ b/comedi-calibrate/configure
-@@ -5616,81 +5616,6 @@
- 
+without patching machine generated files would be preferable, but the tools do
+to thus are currently missing.
+
+Index: comedilib-0.10.1-pere/comedi-calibrate/configure
+===
+--- comedilib-0.10.1-pere.orig/comedi-calibrate/configure	2014-05-11 16:10:54.925251751 +0200
 comedilib-0.10.1-pere/comedi-calibrate/configure	2014-05-11 16:11:17.405352278 +0200
+@@ -5481,216 +5481,6 @@
+ done
  
  
+-if test "${ac_cv_header_comedilib_h+set}" = set; then
+-  { echo "$as_me:$LINENO: checking for comedilib.h" >&5
+-echo $ECHO_N "checking for comedilib.h... $ECHO_C" >&6; }
+-if test "${ac_cv_header_comedilib_h+set}" = set; then
+-  echo $ECHO_N "(cached) $ECHO_C" >&6
+-fi
+-{ echo "$as_me:$LINENO: result: $ac_cv_header_comedilib_h" >&5
+-echo "${ECHO_T}$ac_cv_header_comedilib_h" >&6; }
+-else
+-  # Is the header compilable?
+-{ echo "$as_me:$LINENO: checking comedilib.h usability" >&5
+-echo $ECHO_N "checking comedilib.h usability... $ECHO_C" >&6; }
+-cat >conftest.$ac_ext <<_ACEOF
+-/* confdefs.h.  */
+-_ACEOF
+-cat confdefs.h >>conftest.$ac_ext
+-cat >>conftest.$ac_ext <<_ACEOF
+-/* end confdefs.h.  *

Bug#747792: marked as done (plm: FTBFS: error: package org.json.simple does not exist)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 19:18:48 +
with message-id 
and subject line Bug#747792: fixed in plm 2.3+repack-4
has caused the Debian Bug report #747792,
regarding plm: FTBFS: error: package org.json.simple does not exist
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.)


-- 
747792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747792
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plm
Version: 2.3+repack-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):   ^
> src/plm/core/model/Course.java:7: error: package org.json.simple does not 
> exist
> import org.json.simple.JSONArray;
>   ^
> src/plm/core/model/Course.java:8: error: package org.json.simple does not 
> exist
> import org.json.simple.JSONObject;
>   ^
> src/plm/core/model/Course.java:9: error: package org.json.simple does not 
> exist
> import org.json.simple.JSONValue;
>   ^
> src/plm/core/model/ServerUserData.java:9: error: package org.json.simple does 
> not exist
> import org.json.simple.JSONArray;
>   ^
> src/plm/core/model/ServerUserData.java:10: error: package org.json.simple 
> does not exist
> import org.json.simple.JSONObject;
>   ^
> src/plm/core/model/ServerUserData.java:11: error: package org.json.simple 
> does not exist
> import org.json.simple.JSONValue;
>   ^
> src/plm/core/model/HelpAppEngine.java:11: error: package org.json.simple does 
> not exist
> import org.json.simple.JSONObject;
>   ^
> src/plm/core/model/session/ZipSessionKit.java:16: error: package 
> org.json.simple does not exist
> import org.json.simple.JSONObject;
>   ^
> src/plm/core/model/session/ZipSessionKit.java:17: error: package 
> org.json.simple does not exist
> import org.json.simple.JSONValue;
>   ^
> src/plm/core/model/session/ZipSessionKit.java:18: error: package 
> org.json.simple.parser does not exist
> import org.json.simple.parser.ParseException;
>  ^
> src/plm/core/model/tracking/ServerSpy.java:3: error: package org.json.simple 
> does not exist
> import org.json.simple.JSONObject;
>   ^
> src/plm/core/ui/action/ExportCloudSession.java:27: error: package 
> org.json.simple does not exist
> import org.json.simple.JSONObject;
>   ^
> src/plm/core/ui/action/ExportCloudSession.java:28: error: package 
> org.json.simple does not exist
> import org.json.simple.JSONValue;
>   ^
> src/plm/core/model/Course.java:53: error: cannot find symbol
> JSONObject jsonObject = new JSONObject();
> ^
>   symbol:   class JSONObject
>   location: class Course
> src/plm/core/model/Course.java:53: error: cannot find symbol
> JSONObject jsonObject = new JSONObject();
> ^
>   symbol:   class JSONObject
>   location: class Course
> src/plm/core/model/Course.java:75: error: cannot find symbol
> JSONObject jsonObject = new JSONObject();
> ^
>   symbol:   class JSONObject
>   location: class Course
> src/plm/core/model/Course.java:75: error: cannot find symbol
> JSONObject jsonObject = new JSONObject();
> ^
>   symbol:   class JSONObject
>   location: class Course
> src/plm/core/model/Course.java:102: error: cannot find symbol
> JSONObject jsonObject = new JSONObject();
> ^
>   symbol:   class JSONObject
>   location: class Course
> src/plm/core/model/Course.java:102: error: cannot find symbol
> JSONObject jsonObject = new JSONObject();
> ^
>   symbol:   class JSONObject
>   location: class Course
> src/plm/core/model/Course.java:123: error: cannot find symbol
> JSONObject jsonObject = new JSONObject();
> ^
>   symbol:   class JSONObject
>   location: class Course
> src/plm/core/model/Course.java:123: error: cannot find symbol
> JSONObject jsonObject = new JSONObject();
> ^
>   symbol:   class JSONObject
>   location: class Course
> src/plm/core/model/Course.java:133: error: cannot find symbol
> JSONArray arrayResult = (JSONArray) JSONValue.parse(response);
> ^
>   symbol:   class JSONAr

Processed: Re: Processed: systemd-sysv: #747535 Was: Re: systemd-fsck?

[Debian Bug Tracking System]

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

> severity 747535 important
Bug #747535 [systemd-sysv] systemd-sysv: Ask before installing when upgrading 
to/installing jessie
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747771: marked as done (bti: FTBFS: configure: line 3571: syntax error near unexpected token `PKG_CHECK_MODULES')

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 19:18:28 +
with message-id 
and subject line Bug#747771: fixed in bti 034-2
has caused the Debian Bug report #747771,
regarding bti: FTBFS: configure: line 3571: syntax error near unexpected token 
`PKG_CHECK_MODULES'
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.)


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

Hi,

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

Relevant part (hopefully):
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking whether gcc understands -c and -o together... yes
> checking for style of include used by make... GNU
> ./configure: line 3571: syntax error near unexpected token `PKG_CHECK_MODULES'
> ./configure: line 3571: `PKG_CHECK_MODULES(LIBOAUTH, oauth)'

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/05/10/bti_034-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated bti package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 11 May 2014 21:01:38 +0200
Source: bti
Binary: bti
Architecture: source amd64
Version: 034-2
Distribution: unstable
Urgency: medium
Maintainer: gregor herrmann 
Changed-By: gregor herrmann 
Description: 
 bti- command line Twitter client
Closes: 747771
Changes: 
 bti (034-2) unstable; urgency=medium
 .
   * debian/watch: switch upstream URL back to kernel.org.
   * Also update Source field in debian/copyright.
   * Add build dependency on pkg-config.
 Thanks to David Suárez for the bug report.
 (Closes: #747771)
Checksums-Sha1: 
 a276f506fb721ed4a6e8f31873d5d6ce16cdb454 2089 bti_034-2.dsc
 5fc5cfe0ba605cd13387e9077fa014654005143e 8656 bti_034-2.debian.tar.xz
 f1ad9aa041e6f2b869be2a5977c17766bf22c1eb 31460 bti_034-2_amd64.deb
Checksums-Sha256: 
 f960f1288039677ff3cb7eb1d1c8e98e4a794a2a45cb3b3dd3ae0ecbb07d0664 2089 
bti_034-2.dsc
 07a4f340725c277c4f8698c8511867972ba7a664ae6a779369d9f509e7103bf2 8656 
bti_034-2.debian.tar.xz
 3ac5a38cc215e16a7088c3a3de2678fd25a22410936078b5464a76966f5090ad 31460 
bti_034-2_amd64.deb
Files: 
 6d7c75f1afd2553a763d37a8aee5d416 31460 net extra bti_034-2_amd64.deb
 79e4f18ff3ff6b104edec36941e50cb7 2089 net extra bti_034-2.dsc
 ab5c334fa0ba404ad4684bebb1491944 8656 net extra bti_034-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJrBAEBCgBVBQJTb8mBThSAAB0AKGlzc3Vlci1mcHJAZ3BnLmNvbW9kby5w
cml2LmF0RDFFMTMxNkU5M0E3NjBBODEwNEQ4NUZBQkIzQTY4MDE4NjQ5QUEwNgAK
CRC7OmgBhkmqBrgDEAC94/hogOQqvF1SFmcXFOmlqkqbx+e59sWWOYqyoNmLwFHq
lK2rYv+ic9I8cNNV61vJ26YaIokrK+/9hVgKA7Rp3Lce/IdtJ6fa/o1oyOoP+f/f
YjeL5xyDeNHFIU2zGKb2rdhanAeIPykSKDGIsX5ELBZwpFmy+IH4QydL9AW/Fi2d
WdhCSLX2epplGIC3VPUEOfgbFZYDwiriIQmPYPgyibEcl3+RxRe/bXbgMq52l5oD
P4myPT8cOJgWjSPsc3g+g+zj8Cn6vf07dmFcLIYo4u18W+WRwsqMJSbn5YzacRc5
rwCehCmLiWeHuBtOcfiA07Q9WKZSMaIkeOjGFCZdEL/lt5OVcMG8IDHXtGrJTtdy
rQZxknTlHbsUuoJpYCif0axLsjqpioXLw6s3JEl6MCY+SYoYxkJ1JE9szByHk009
3D0NX7cL3lrDmr88GcqAyGZpyh8CmGW/ag8pEsgIR0Id+Yvp2aUFO5GJlUgMwXeF
r/AidVSPPmpkJy6ngmqfUtACf6VKBuHlAwKjXi4mI6WDYWwDb9SwgMQ6sTD/x/B/
c4cPqB2At7tNpz3nxk6sLA0lfueo4ksAwM5fgt6IEpScukspZ7bNnbMXnlJ0BGW2
1JvjZm02O1wm/ykHz7dc/l5CHkKEmQle8qyaDzUXoTvCmvgNhMUBfnI3tFu2JA==
=KK7k
-END PGP SIGNATURE End 

Bug#747535: Processed: systemd-sysv: #747535 Was: Re: systemd-fsck?

[Tollef Fog Heen]

severity 747535 important
thanks

]]  (Debian Bug Tracking System)

> Processing commands for cont...@bugs.debian.org:
> 
> > severity 747535 serious
> Bug #747535 [systemd-sysv] systemd-sysv: Ask before installing when upgrading 
> to/installing jessie
> Severity set to 'serious' from 'important'

No, it's not.  We don't consider it unsuitable for release.  Feel free
to get the release team to chime in or provide a justification pointing
to the relevant bit of policy.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: found 739327 in 2.2.2~ds0-3, closing 739327

[Debian Bug Tracking System]

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

> found 739327 2.2.2~ds0-3
Bug #739327 [src:lives] FTBFS with libav10
Marked as found in versions lives/2.2.2~ds0-3.
> close 739327 2.2.2~ds0-4~exp1
Bug #739327 [src:lives] FTBFS with libav10
Marked as fixed in versions lives/2.2.2~ds0-4~exp1.
Bug #739327 [src:lives] FTBFS with libav10
Marked Bug as done
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#724207: marked as done (minidlna: FTBFS: stat.h:91:21: error: unknown type name 'time_t')

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 21:05:42 +0200
with message-id <20140511190542.ga24...@ramacher.at>
and subject line Re: Bug#724207: minidlna: FTBFS: stat.h:91:21: error: unknown 
type name 'time_t'
has caused the Debian Bug report #724207,
regarding minidlna: FTBFS: stat.h:91:21: error: unknown type name 'time_t'
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.)


-- 
724207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: minidlna
Version: 1.0.24+dfsg-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130922 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):  ^
> In file included from inotify.c:28:0:
> /usr/include/x86_64-linux-gnu/sys/stat.h:366:31: error: array type has 
> incomplete element type
>  const struct timespec __times[2],
>^
> /usr/include/x86_64-linux-gnu/sys/stat.h:373:54: error: array type has 
> incomplete element type
>  extern int futimens (int __fd, const struct timespec __times[2]) __THROW;
>   ^
> In file included from upnpglobalvars.h:54:0,
>  from inotify.c:39:
> minidlnatypes.h:106:2: error: unknown type name 'time_t'
>   time_t age;
>   ^
> In file included from inotify.c:39:0:
> upnpglobalvars.h:182:1: error: unknown type name 'time_t'
>  extern time_t startup_time;
>  ^
> inotify.c:64:1: error: unknown type name 'time_t'
>  static time_t next_pl_fill = 0;
>  ^
> inotify.c: In function 'inotify_insert_file':
> inotify.c:411:4: warning: implicit declaration of function 'time' 
> [-Wimplicit-function-declaration]
> next_pl_fill = time(NULL) + 120; // Schedule a playlist scan for 2 
> minutes from now.
> ^
> The following command failed:
> gcc -Wall -g -O3 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/ffmpeg 
> -I/usr/include/libavutil -I/usr/include/libavcodec -I/usr/include/libavformat 
> -I/usr/include/ffmpeg/libavutil -I/usr/include/ffmpeg/libavcodec 
> -I/usr/include/ffmpeg/libavformat -o inotify.o -c inotify.c
> Linking minidlna
> gcc: error: minidlna.o: No such file or directory
> gcc: error: upnphttp.o: No such file or directory
> gcc: error: upnpdescgen.o: No such file or directory
> gcc: error: upnpsoap.o: No such file or directory
> gcc: error: daemonize.o: No such file or directory
> gcc: error: upnpglobalvars.o: No such file or directory
> gcc: error: options.o: No such file or directory
> gcc: error: minissdp.o: No such file or directory
> gcc: error: uuid.o: No such file or directory
> gcc: error: upnpevents.o: No such file or directory
> gcc: error: sql.o: No such file or directory
> gcc: error: utils.o: No such file or directory
> gcc: error: metadata.o: No such file or directory
> gcc: error: scanner.o: No such file or directory
> gcc: error: tagutils/tagutils.o: No such file or directory
> gcc: error: playlist.o: No such file or directory
> gcc: error: albumart.o: No such file or directory
> gcc: error: log.o: No such file or directory
> gcc: error: inotify.o: No such file or directory
> make[1]: *** [minidlna] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/09/22/minidlna_1.0.24+dfsg-1_unstable.log

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

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

On 2013-09-22 19:00:04, David Suárez wrote:
> Source: minidlna
> Version: 1.0.24+dfsg-1
> Severity: serious
> Tags: jessie sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20130922 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):  ^
> > In file included from inotify.c:28:0:
> > /usr/include/x86_64-linux-gnu/sys/stat.h:366:31: error: array type has 
> > incomplete element type
> >  const struct timespec __times[2],
> >^
> > /usr/include/x86_64-linux-gnu/sys/stat.h:373:54: error: array type has 
> > incomplete element type
> >  extern int futimens (int __fd, const s

Bug#602724: please remove kfreebsd-any from Architecture

[Julien Cristau]

On Sun, May 11, 2014 at 17:37:29 +0200, Robert Millan wrote:

> I've uploaded an NMU with the removal of "kfreebsd-any" (and "hurd-any"
> as per porter's request) from Architecture. A debdiff is attached.
> 
Do you plan on also handling the reverse dependencies (with binary
removals and/or patches, as appropriate)?  (I fully expect a "yes", but
I haven't seen anything yet, so just making sure.)

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#741427: marked as done (bognor-regis: Please update for tracker-0.18)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 19:03:36 +
with message-id 
and subject line Bug#741427: fixed in bognor-regis 0.6.12+git20101007.02c25268-9
has caused the Debian Bug report #741427,
regarding bognor-regis: Please update for tracker-0.18
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.)


-- 
741427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bognor-regis
Version: 0.6.12+git20101007.02c25268-8
Severity: important
User: bi...@debian.org
Usertags: tracker-0.18

Hi,

your package bognor-regis uses tracker and has a build dependency on
libtracker-sparql-0.16-dev.

I'd like to update tracker to version 0.18, where the API version was
finally declared stable and bumped to 1.0. So hopefully, we no longer
have an API bump every 6 months.

This means, you'll have to update the Build-Depends from
libtracker-sparql-0.16-dev to libtracker-sparql-1.0-dev and update
the configure check to check for the tracker-sparql-1.0 .pc file.

If your package already supports tracker-0.16, this should be
sufficient in most cases.

I've uploaded tracker 0.17.x pre-releases to experimental [0], so you
can prepare and test your package against this version. As soon as
the final tracker 0.18.0 version is released, I'd like to proceed
with the upload to unstable. I'll notify you before I make the
unstable upload.

Regards, Michael

[0] https://packages.debian.org/experimental/tracker 
--- End Message ---
--- Begin Message ---
Source: bognor-regis
Source-Version: 0.6.12+git20101007.02c25268-9

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

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated bognor-regis 
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: Mon, 12 May 2014 02:30:54 +0800
Source: bognor-regis
Binary: bognor-regis libbognor-regis-0.6-0 libbognor-regis-dev 
libbognor-regis-0.6-0-dbg
Architecture: source i386
Version: 0.6.12+git20101007.02c25268-9
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Description: 
 bognor-regis - Media daemon and play queue manager
 libbognor-regis-0.6-0 - Media daemon and play queue manager library
 libbognor-regis-0.6-0-dbg - Media daemon and play queue manager library (debug 
symbols)
 libbognor-regis-dev - Media daemon and play queue manager library (development 
files)
Closes: 741427
Changes: 
 bognor-regis (0.6.12+git20101007.02c25268-9) unstable; urgency=low
 .
   * Update debian/patches/port_to_tracker-sparql-1.0.patch
 - Build against tracker 1.0. (Closes: #741427)
 - Modify from port_to_tracker-sparql-0.16.patch
   * Bump Standards-Version to 3.9.5: Nothing needs to be changed.
Checksums-Sha1: 
 7559a8941dc34237628671e1792fae5735879912 2355 
bognor-regis_0.6.12+git20101007.02c25268-9.dsc
 f580149cddcc0627be0058aa25a7fb077cd5f03f 5608 
bognor-regis_0.6.12+git20101007.02c25268-9.debian.tar.xz
 6d9c3788867fc8a34bc40723df4e61c0146aa8d8 37230 
bognor-regis_0.6.12+git20101007.02c25268-9_i386.deb
 4dc414989363c4edc50fe910cab4716523d5ebc9 12800 
libbognor-regis-0.6-0_0.6.12+git20101007.02c25268-9_i386.deb
 be5ef8bd181728cb44ecc1b66ce099fe9f13a638 13838 
libbognor-regis-dev_0.6.12+git20101007.02c25268-9_i386.deb
 d81e11d423f147b04b051934aacf961da4872f89 105850 
libbognor-regis-0.6-0-dbg_0.6.12+git20101007.02c25268-9_i386.deb
Checksums-Sha256: 
 7ca3a84fe41c0715361252447ee1cfac154970b84706deaeddf7a8d48ab0fa89 2355 
bognor-regis_0.6.12+git20101007.02c25268-9.dsc
 59d678e093ffd8207a1ec4304ed964b57fa5e80e408cf8d3cb00ec4492243711 5608 
bognor-regis_0.6.12+git20101007.02c25268-9.debian.tar.xz
 d92670963e453c7f722461e5c3010d782776f55db3b108f97ddf409611374325 37230 
bognor-regis_0.6.12+git20101007.02c25268-9_i386.deb
 4d6be8116ea1766565d8d5e8a040883fb3c631580e82cb99c1f158651e02b37e 12800 
libbognor-regis-0.6-0_0.6.12+git20101007.02c25268-9_i386.deb
 cb80d85e0fd3478accb9e95296abdf4af3d503ab2a948230a496b3b019f8c289 13838 
libbog

Bug#747813: minidlna: FTBFS against libav10

[Sebastian Ramacher]

Source: minidlna
Version: 1.1.2+dfsg-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: sid jessie
User: j...@debian.org
Usertag: libav10

minidlna fails to build against libav10 which has just been uploaded to
unstable:
|   CC   metadata.o
| metadata.c: In function 'GetVideoMetadata':
| metadata.c:775:9: error: 'CODEC_ID_MP3' undeclared (first use in this 
function)
| case CODEC_ID_MP3:
|  ^
| metadata.c:775:9: note: each undeclared identifier is reported only once for 
each function it appears in
| metadata.c:778:9: error: 'CODEC_ID_AAC' undeclared (first use in this 
function)
| case CODEC_ID_AAC:
|  ^
| metadata.c:819:9: error: 'CODEC_ID_AC3' undeclared (first use in this 
function)
| case CODEC_ID_AC3:
|  ^
| metadata.c:820:9: error: 'CODEC_ID_DTS' undeclared (first use in this 
function)
| case CODEC_ID_DTS:
|  ^
| metadata.c:823:9: error: 'CODEC_ID_WMAV1' undeclared (first use in this 
function)
| case CODEC_ID_WMAV1:
|  ^
| metadata.c:824:9: error: 'CODEC_ID_WMAV2' undeclared (first use in this 
function)
| case CODEC_ID_WMAV2:
|  ^
| metadata.c:833:9: error: 'CODEC_ID_WMAPRO' undeclared (first use in this 
function)
| case CODEC_ID_WMAPRO:
|  ^
| metadata.c:837:9: error: 'CODEC_ID_MP2' undeclared (first use in this 
function)
| case CODEC_ID_MP2:
|  ^
| metadata.c:840:9: error: 'CODEC_ID_AMR_NB' undeclared (first use in this 
function)
| case CODEC_ID_AMR_NB:
|  ^
| metadata.c:844:26: error: 'CODEC_ID_PCM_S16LE' undeclared (first use in this 
function)
|  if( (ac->codec_id >= CODEC_ID_PCM_S16LE) &&
|   ^
| metadata.c:845:25: error: 'CODEC_ID_ADPCM_IMA_QT' undeclared (first use in 
this function)
|  (ac->codec_id < CODEC_ID_ADPCM_IMA_QT) )
|  ^
| metadata.c:882:24: error: 'CODEC_ID_MPEG4' undeclared (first use in this 
function)
| if( vc->codec_id == CODEC_ID_MPEG4 )
| ^
| metadata.c:906:9: error: 'CODEC_ID_MPEG1VIDEO' undeclared (first use in this 
function)
| case CODEC_ID_MPEG1VIDEO:
|  ^
| metadata.c:917:9: error: 'CODEC_ID_MPEG2VIDEO' undeclared (first use in this 
function)
| case CODEC_ID_MPEG2VIDEO:
|  ^
| metadata.c:990:9: error: 'CODEC_ID_H264' undeclared (first use in this 
function)
| case CODEC_ID_H264:
|  ^
| metadata.c:1008:36: error: 'AVStream' has no member named 'r_frame_rate'
|   if (ctx->streams[video_stream]->r_frame_rate.den)
| ^
| metadata.c:1009:39: error: 'AVStream' has no member named 'r_frame_rate'
|fps = ctx->streams[video_stream]->r_frame_rate.num / 
ctx->streams[video_stream]->r_frame_rate.den;
|^
| metadata.c:1009:86: error: 'AVStream' has no member named 'r_frame_rate'
|fps = ctx->streams[video_stream]->r_frame_rate.num / 
ctx->streams[video_stream]->r_frame_rate.den;
|   
^
| metadata.c:1012:66: error: 'AVStream' has no member named 'r_frame_rate'
|   interlaced = vc->time_base.den ? 
(ctx->streams[video_stream]->r_frame_rate.num / vc->time_base.den) : 0;
|   ^
| metadata.c:1364:9: error: 'CODEC_ID_WMV3' undeclared (first use in this 
function)
| case CODEC_ID_WMV3:
|  ^
| metadata.c:1373:9: error: 'CODEC_ID_VC1' undeclared (first use in this 
function)
| case CODEC_ID_VC1:
|  ^
| metadata.c:1472:9: error: 'CODEC_ID_MSMPEG4V3' undeclared (first use in this 
function)
| case CODEC_ID_MSMPEG4V3:
|  ^
| make[3]: *** [metadata.o] Error 1
| Makefile:589: recipe for target 'metadata.o' failed

The full build log is available at
http://people.debian.org/~sramacher/logs/libav10/minidlna_1.1.2+dfsg-1_amd64-20140511-2057.log

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#747715: marked as done (FTBFS: make[1]: *** [check] Error 1)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 21:01:38 +0200
with message-id <20140511190138.ga30...@nq.home.zeha.at>
and subject line Caused by build environment
has caused the Debian Bug report #747715,
regarding FTBFS: make[1]: *** [check] Error 1
to be marked as done.

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

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


-- 
747715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debci
Version: 0.5.2
Severity: serious
Justification: fails to build from source
User: debian-r...@lists.debian.org
Usertags: ruby2.0-rm

Dear Maintainer,

During a rebuild of ruby-related packages your package failed to
build with these errors:

./test_blame.sh
shm_open: Bad address
[..]
shm_open: Bad address
test_package_that_never_passed_a_test_cant_blame
ASSERT:expected:<> but was:
test_failing_test_blames_dependencies
ASSERT:expected: but was:
test_updated_dependency_of_already_failing_package_is_not_blamed
ASSERT:expected: but was:
test_new_dependency_of_already_failing_package_is_not_blamed
ASSERT:expected: but was:
test_passing_the_test_resets_the_blame
ASSERT:expected:<> but was:
test_blame_updated_dependency
ASSERT:expected: but was:
test_updated_dependencies_dont_get_blamed_when_package_is_also_updated
ASSERT:expected:<> but was:
test_package_is_not_blamed_for_its_own_failure
ASSERT:expected:<> but was:

Ran 8 tests.

FAILED (failures=8)
☐ ./test_blame.sh failed at least one test


The test build was done in a rather standard schroot/sbuild combination
on a host running systemd as PID 1, and DEB_BUILD_OPTIONS=parallel=12.

Please note that the default ruby has been switched to 2.1 in sid.
If possible, please switch to the metapackages and `dh_ruby
--print-supported` for detecting the ruby to build for.
(Also, if everything goes according to plan, this is the last ruby
transition for jessie.)

Please find the full build log attached.

Thanks,
  -ch


debci_0.5.2_amd64.build
Description: inode/symlink
--- End Message ---
--- Begin Message ---
Sorry for wasting your time, this build failure is caused by
eatmydata being present in the build environment.

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

Bug#747792: plm: FTBFS: error: package org.json.simple does not exist

[Martin Quinson]

Thanks for the report.

I'm astonished, as I swear I built that package in a pbuilder before
uploading it, and it obviously worked. I'll investigate if json
changed recently.

Martin, puzzeled.

On Sun, May 11, 2014 at 07:26:13PM +0200, David Suárez wrote:
> Source: plm
> Version: 2.3+repack-3
> Severity: serious
> Tags: jessie sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20140510 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully): ^
> > src/plm/core/model/Course.java:7: error: package org.json.simple does not 
> > exist
> > import org.json.simple.JSONArray;
> >   ^
> > src/plm/core/model/Course.java:8: error: package org.json.simple does not 
> > exist
> > import org.json.simple.JSONObject;
> >   ^
> > src/plm/core/model/Course.java:9: error: package org.json.simple does not 
> > exist
> > import org.json.simple.JSONValue;
> >   ^
> > src/plm/core/model/ServerUserData.java:9: error: package org.json.simple 
> > does not exist
> > import org.json.simple.JSONArray;
> >   ^
> > src/plm/core/model/ServerUserData.java:10: error: package org.json.simple 
> > does not exist
> > import org.json.simple.JSONObject;
> >   ^
> > src/plm/core/model/ServerUserData.java:11: error: package org.json.simple 
> > does not exist
> > import org.json.simple.JSONValue;
> >   ^
> > src/plm/core/model/HelpAppEngine.java:11: error: package org.json.simple 
> > does not exist
> > import org.json.simple.JSONObject;
> >   ^
> > src/plm/core/model/session/ZipSessionKit.java:16: error: package 
> > org.json.simple does not exist
> > import org.json.simple.JSONObject;
> >   ^
> > src/plm/core/model/session/ZipSessionKit.java:17: error: package 
> > org.json.simple does not exist
> > import org.json.simple.JSONValue;
> >   ^
> > src/plm/core/model/session/ZipSessionKit.java:18: error: package 
> > org.json.simple.parser does not exist
> > import org.json.simple.parser.ParseException;
> >  ^
> > src/plm/core/model/tracking/ServerSpy.java:3: error: package 
> > org.json.simple does not exist
> > import org.json.simple.JSONObject;
> >   ^
> > src/plm/core/ui/action/ExportCloudSession.java:27: error: package 
> > org.json.simple does not exist
> > import org.json.simple.JSONObject;
> >   ^
> > src/plm/core/ui/action/ExportCloudSession.java:28: error: package 
> > org.json.simple does not exist
> > import org.json.simple.JSONValue;
> >   ^
> > src/plm/core/model/Course.java:53: error: cannot find symbol
> > JSONObject jsonObject = new JSONObject();
> > ^
> >   symbol:   class JSONObject
> >   location: class Course
> > src/plm/core/model/Course.java:53: error: cannot find symbol
> > JSONObject jsonObject = new JSONObject();
> > ^
> >   symbol:   class JSONObject
> >   location: class Course
> > src/plm/core/model/Course.java:75: error: cannot find symbol
> > JSONObject jsonObject = new JSONObject();
> > ^
> >   symbol:   class JSONObject
> >   location: class Course
> > src/plm/core/model/Course.java:75: error: cannot find symbol
> > JSONObject jsonObject = new JSONObject();
> > ^
> >   symbol:   class JSONObject
> >   location: class Course
> > src/plm/core/model/Course.java:102: error: cannot find symbol
> > JSONObject jsonObject = new JSONObject();
> > ^
> >   symbol:   class JSONObject
> >   location: class Course
> > src/plm/core/model/Course.java:102: error: cannot find symbol
> > JSONObject jsonObject = new JSONObject();
> > ^
> >   symbol:   class JSONObject
> >   location: class Course
> > src/plm/core/model/Course.java:123: error: cannot find symbol
> > JSONObject jsonObject = new JSONObject();
> > ^
> >   symbol:   class JSONObject
> >   location: class Course
> > src/plm/core/model/Course.java:123: error: cannot find symbol
> > JSONObject jsonObject = new JSONObject();
> > ^
> >   symbol:   class JSONObject
> >   location: class Course
> > src/plm/core/model/Course.java:133: error: cannot find symbol
> > JSONArray arrayResult = (JSONArray) JSONValue.parse(response);
> > ^
> >   symbol:   class JSONArray
> >   location: class Course
> > src/plm/core/model/Course.java:133: error: cannot find symbol
> > JSONArray arrayResult = (JSONArray) JSONValue.parse(response);
> >  ^
> >   symbol:   class JSONArray
> >   location: class Course
> > src/plm/core/model/Course.java:133: error: cannot find symbol

Bug#747811: soundscaperenderer: FTBFS on all archs

[Ivo De Decker]

package: soundscaperenderer
severity: serious
version: 0.4.1~dfsg-1

Hi,

The initial release of soundscaperenderer seems to fail on all architectures:

https://buildd.debian.org/status/package.php?p=soundscaperenderer&suite=sid

Please try to build it in a clean environment before uploading.

Cheers,

Ivo


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747769: marked as done (clamz: FTBFS: error: The pkg-config script could not be found)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 18:48:29 +
with message-id 
and subject line Bug#747769: fixed in clamz 0.5-2
has caused the Debian Bug report #747769,
regarding clamz: FTBFS: error: The pkg-config script could not be 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.)


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

Hi,

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

Relevant part (hopefully):
> checking for gcc option to accept ISO C89... none needed
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for update-mime-database... :
> checking for update-desktop-database... :
> checking for XML_ParserCreate in -lexpat... yes
> configure: error: in `/«PKGBUILDDIR»'
> checking for pkg-config... no
> configure: error: The pkg-config script could not be found or is too old.  
> Make sure it
> is in your PATH or set the PKG_CONFIG environment variable to the full
> path to pkg-config.
> 
> Alternatively, you may set the environment variables LIBCURL_CFLAGS
> and LIBCURL_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> 
> To get pkg-config, see .
> See `config.log' for more details
> checking for LIBCURL... ==> config.log <==
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> It was created by Clamz configure 0.5, which was
> generated by GNU Autoconf 2.68.  Invocation command line was

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/05/10/clamz_0.5-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Vincent Bernat  (supplier of updated clamz package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 May 2014 20:31:39 +0200
Source: clamz
Binary: clamz
Architecture: source amd64
Version: 0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Vincent Bernat 
Changed-By: Vincent Bernat 
Description: 
 clamz  - command-line program to download MP3's from Amazon
Closes: 747769
Changes: 
 clamz (0.5-2) unstable; urgency=medium
 .
   * Build-Depends on pkg-config to fix FTBFS. Closes: #747769.
   * Bump Standards-Version to 3.9.5.
   * Update Vcs-* fields.
Checksums-Sha1: 
 3ab64199b6756ee3fbb1983f759193e80038b885 1863 clamz_0.5-2.dsc
 bc1cb841237e14fe2625845e5d2dafefaedaf93f 2328 clamz_0.5-2.debian.tar.xz
 03e0a77ef66f5601ae3791964b2148be2f570f4b 22506 clamz_0.5-2_amd64.deb
Checksums-Sha256: 
 8a825b333933175ecb42a477933f9cbe249d8fc83686db601afaf8b1ee8683ed 1863 
clamz_0.5-2.dsc
 28000548e5d2ceba14646bc21707dbc1948d8145405164563b932ef73fa5cbcd 2328 
clamz_0.5-2.debian.tar.xz
 89991fa68625899880ba1e1e46e80515270b27358acaffbc2119304fedee726f 22506 
clamz_0.5-2_amd64.deb
Files: 
 7d09acad161b61300d007bf738e04ea0 22506 utils extra clamz_0.5-2_amd64.deb
 73771d9af786b9c9a8acf2ab3cb2af18 1863 utils extra clamz_0.5-2.dsc
 432d6510fa61ce0287767cb4182afa9c 2328 utils extra clamz_0.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJTb8NsAAoJEJWkL+g1NSX5SaUQAItxsz+YucVlgdgLJ7tx5J14
WAUTnr1stdHoEx57M9pfmzt72uMYnNf9k4knVOaZJelBNRjjxFEDmDuBc6DHupTA
iG9/y64evdsrf4VpugtpxhxwqwEQXyYG+kgEHnwx/lBnquvVQh6xMh+x0nggDdbv
KEjlZTHrVghnxiF4dLR

Processed: found 739376 in 1.0.86-2, closing 739376

[Debian Bug Tracking System]

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

> found 739376 1.0.86-2
Bug #739376 [shotdetect] FTBFS with libav10
Marked as found in versions shotdetect/1.0.86-2.
> close 739376 1.0.86-3
Bug #739376 [shotdetect] FTBFS with libav10
Marked as fixed in versions shotdetect/1.0.86-3.
Bug #739376 [shotdetect] FTBFS with libav10
Marked Bug as done
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#739208: marked as done (Fails to build from source against libav10)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 14:35:13 -0400
with message-id 

and subject line Accidentally reopened
has caused the Debian Bug report #739208,
regarding Fails to build from source against libav10
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.)


-- 
739208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: acoustid-fingerprinter
Severity: important

Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.

Migration documentation can be found at
https://wiki.libav.org/Migration/10

/usr/bin/g++   -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG 
-DQT_NO_DEBUG_OUTPUT -DVERSION=\"0.6\" -D__STDC_CONSTANT_MACROS 
-D__STDC_LIMIT_MACROS -g -O2 -fstack-protector --param=ssp-buffer-size=4 
-Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG 
-isystem /usr/include/qt4 -isystem /usr/include/qt4/QtGui -isystem 
/usr/include/qt4/QtNetwork -isystem /usr/include/qt4/QtCore 
-I/home/jmm/av10/acoustid-fingerprinter-0.6/obj-x86_64-linux-gnu 
-I/usr/include/taglib-o CMakeFiles/fpsubmit.dir/decoder.cpp.o -c 
/home/jmm/av10/acoustid-fingerprinter-0.6/decoder.cpp
In file included from /home/jmm/av10/acoustid-fingerprinter-0.6/decoder.cpp:1:0:
/home/jmm/av10/acoustid-fingerprinter-0.6/decoder.h:70:33: error: 
'AVCODEC_MAX_AUDIO_FRAME_SIZE' was not declared in this scope
  static const int BUFFER_SIZE = AVCODEC_MAX_AUDIO_FRAME_SIZE * 2;
 ^
/home/jmm/av10/acoustid-fingerprinter-0.6/decoder.h: In constructor 
'Decoder::Decoder(const string&)':
/home/jmm/av10/acoustid-fingerprinter-0.6/decoder.h:78:12: warning: 
'Decoder::m_stream' will be initialized after [-Wreorder]
  AVStream *m_stream;
^
/home/jmm/av10/acoustid-fingerprinter-0.6/decoder.h:77:7: warning:   'bool 
Decoder::m_codec_open' [-Wreorder]
  bool m_codec_open;
   ^
/home/jmm/av10/acoustid-fingerprinter-0.6/decoder.h:111:8: warning:   when 
initialized here [-Wreorder]
 inline Decoder::Decoder(const std::string &file_name)
^
/home/jmm/av10/acoustid-fingerprinter-0.6/decoder.h: In member function 'bool 
Decoder::Open()':
/home/jmm/av10/acoustid-fingerprinter-0.6/decoder.h:167:36: warning: comparison 
between signed and unsigned integer expressions
[-Wsign-compare]
  for (int i = 0; i < m_format_ctx->nb_streams; i++) {
^
/home/jmm/av10/acoustid-fingerprinter-0.6/decoder.h: In member function 'void 
Decoder::Decode(FingerprintCalculator*, int)':
/home/jmm/av10/acoustid-fingerprinter-0.6/decoder.h:255:45: error: 
'avcodec_decode_audio3' was not declared in this scope
 &packet_temp);
 ^
make[3]: *** [CMakeFiles/fpsubmit.dir/decoder.cpp.o] Error 1
make[3]: Leaving directory 
`/home/jmm/av10/acoustid-fingerprinter-0.6/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/fpsubmit.dir/all] Error 2
make[2]: Leaving directory 
`/home/jmm/av10/acoustid-fingerprinter-0.6/obj-x86_64-linux-gnu'
make[1]: *** [all] Error 2
make[1]: Leaving directory 
`/home/jmm/av10/acoustid-fingerprinter-0.6/obj-x86_64-linux-gnu'
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 0.6-3

Sorry, I've accidentally reopened this bug.  The package needs to be
rebuilt against libav10 nevertheless.

-- 
regards,
Reinhard--- End Message ---

Bug#739377: marked as done (FTBFS with libav10)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 14:34:00 -0400
with message-id 

and subject line Fixed in unstable
has caused the Debian Bug report #739377,
regarding FTBFS with libav10
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.)


-- 
739377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yorick-av
Severity: important

Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.

Migration documentation can be found at
https://wiki.libav.org/Migration/10

Cheers,
Moritz


yav.c:241:10: error: 'CODEC_ID_FLV1' undeclared (first use in this function)
 case CODEC_ID_FLV1:
  ^
yav.c:242:10: error: 'CODEC_ID_ASV1' undeclared (first use in this function)
 case CODEC_ID_ASV1:
  ^
yav.c:243:10: error: 'CODEC_ID_ASV2' undeclared (first use in this function)
 case CODEC_ID_ASV2:
  ^
yav.c: In function 'yav_opencodec':
yav.c:269:5: warning: 'avcodec_alloc_frame' is deprecated (declared at 
/usr/include/libavcodec/avcodec.h:3110) [-Wdeprecated-declarations]
 obj->picture = avcodec_alloc_frame();
 ^
yav.c:281:42: error: 'CODEC_ID_H264' undeclared (first use in this function)
 if (obj->oc->oformat->video_codec == CODEC_ID_H264 ||
  ^
yav.c:282:35: error: 'CODEC_ID_THEORA' undeclared (first use in this function)
  obj->oc->oformat->video_codec == CODEC_ID_THEORA) obj->picture->pts=-1;
   ^
yav.c:289:7: warning: 'avcodec_alloc_frame' is deprecated (declared at 
/usr/include/libavcodec/avcodec.h:3110) [-Wdeprecated-declarations]
   obj->tmp_picture = avcodec_alloc_frame();
   ^
yav.c: In function 'Y_av_write':
yav.c:381:40: error: 'CODEC_ID_H264' undeclared (first use in this function)
   if (obj->oc->oformat->video_codec == CODEC_ID_H264 ||
^
yav.c:382:40: error: 'CODEC_ID_THEORA' undeclared (first use in this function)
   obj->oc->oformat->video_codec == CODEC_ID_THEORA) ++obj->picture->pts;
^
make[2]: *** [yav.o] Error 1
make[2]: Leaving directory `/home/jmm/av10/yorick-av-0.0.2'
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory `/home/jmm/av10/yorick-av-0.0.2'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Version: 0.0.3-1

This package should be OK, still needs to be rebuilt though.

-- 
regards,
Reinhard--- End Message ---

Bug#739439: marked as done (FTBFS with libav10)

[Debian Bug Tracking System]

Your message dated Sun, 11 May 2014 14:30:14 -0400
with message-id 

and subject line Accidentally reopened
has caused the Debian Bug report #739439,
regarding FTBFS with libav10
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.)


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

Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.

Migration documentation can be found at
https://wiki.libav.org/Migration/10

Cheers,
Moritz

make[5]: Nothing to be done for `all'.
make[5]: Leaving directory 
`/home/jmm/av10/opal-3.10.10~dfsg/plugins/video/H.261-vic'
make[5]: Entering directory 
`/home/jmm/av10/opal-3.10.10~dfsg/plugins/video/H.263-1998'
[CC] h263-1998.cxx
In file included from h263-1998.cxx:50:0:
h263-1998.h:118:23: error: 'CodecID' has not been declared
 virtual bool Init(CodecID codecId);
   ^
In file included from h263-1998.cxx:58:0:
../common/dyna.h:91:27: error: expected ')' before 'codec'
 FFMPEGLibrary(CodecID codec);
   ^
../common/dyna.h:96:38: error: use of enum 'CodecID' without previous 
declaration
 AVCodec *AvcodecFindEncoder(enum CodecID id);
  ^
../common/dyna.h:97:38: error: use of enum 'CodecID' without previous 
declaration
 AVCodec *AvcodecFindDecoder(enum CodecID id);
  ^
../common/dyna.h:120:5: error: 'CodecID' does not name a type
 CodecID m_codec;
 ^
h263-1998.cxx:97:44: error: 'CODEC_ID_H263P' was not declared in this scope
 static FFMPEGLibrary FFMPEGLibraryInstance(CODEC_ID_H263P);
^
h263-1998.cxx:206:37: error: 'bool H263_Base_EncoderContext::Init' is not a 
static member of 'class H263_Base_EncoderContext'
 bool H263_Base_EncoderContext::Init(CodecID codecId)
 ^
h263-1998.cxx:206:37: error: 'CodecID' was not declared in this scope
h263-1998.cxx:207:1: error: expected ',' or ';' before '{' token
 {
 ^
make[5]: *** 
[/home/jmm/av10/opal-3.10.10~dfsg/plugins/../lib_linux_x86_64/plugins/h263_ffmpeg/h263-1998.o]
 Error 1
make[5]: Leaving directory 
`/home/jmm/av10/opal-3.10.10~dfsg/plugins/video/H.263-1998'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/home/jmm/av10/opal-3.10.10~dfsg/plugins'
make[3]: *** [subdirs] Error 2
make[3]: Leaving directory `/home/jmm/av10/opal-3.10.10~dfsg'
make[2]: *** [opt] Error 2
make[2]: Leaving directory `/home/jmm/av10/opal-3.10.10~dfsg'
dh_auto_build: make -j1 
PKG_CONFIG_PATH=/home/jmm/av10/opal-3.10.10~dfsg/samples opt docs returned exit 
code 2
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory `/home/jmm/av10/opal-3.10.10~dfsg'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Version: 3.10.10~dfsg-2.2


Sorry, this bug was reopened accidentally

-- 
regards,
Reinhard--- End Message ---

Bug#739458: Sorry, reopened accidentally

[Reinhard Tartler]

Version: 1.2.5-1

Sorry, this bug was reopened accidentally. We need to recompile the
xine-lib-1.2 package however anyways.

-- 
regards,
Reinhard


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#739332: Can be fixed with a binNMU

[Reinhard Tartler]

AFAIUI, this bug can be fixed with a binNMU as soon as libav10 built everywhere


-- 
regards,
Reinhard


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed (with 48 errors): Libav10 is now in unstable, please recompile

[Debian Bug Tracking System]

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

> reopen 739191
Bug #739191 {Done: Reinhard Tartler } [src:avbin] Fails to 
build from source against libav 10
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions avbin/7-3.
> severity 739191 serious
Bug #739191 [src:avbin] Fails to build from source against libav 10
Severity set to 'serious' from 'important'
> reopen 739208
Bug #739208 {Done: Jerome Charaoui } 
[acoustid-fingerprinter] Fails to build from source against libav10
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions acoustid-fingerprinter/0.6-3.
> severity 739208 serious
Bug #739208 [acoustid-fingerprinter] Fails to build from source against libav10
Severity set to 'serious' from 'important'
> reopen 739211
Failed to reopen 739211: Not altering archived bugs; see unarchive.

> severity 739211 serious
Failed to set severity of Bug 739211 to serious: Not altering archived bugs; 
see unarchive.

> reopen 739212
Failed to reopen 739212: Not altering archived bugs; see unarchive.

> severity 739212 serious
Failed to set severity of Bug 739212 to serious: Not altering archived bugs; 
see unarchive.

> reopen 739213
Bug #739213 {Done: Reinhard Tartler } [src:avifile] FTBFS 
against libav10
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions avifile/1:0.7.48~20090503.ds-14.1.
> severity 739213 serious
Bug #739213 [src:avifile] FTBFS against libav10
Severity set to 'serious' from 'important'
> reopen 739214
Failed to reopen 739214: Not altering archived bugs; see unarchive.

> severity 739214 serious
Failed to set severity of Bug 739214 to serious: Not altering archived bugs; 
see unarchive.

> reopen 739220
Bug #739220 {Done: Reinhard Tartler } [dvbcut] FTBFS with 
libav10
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions dvbcut/0.5.4+svn178-5.
> severity 739220 serious
Bug #739220 [dvbcut] FTBFS with libav10
Severity set to 'serious' from 'important'
> reopen 739221
Bug #739221 {Done: Reinhard Tartler } [src:ffdiaporama] 
FTBFS with libav10
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ffdiaporama/1.5-3.
> severity 739221 serious
Bug #739221 [src:ffdiaporama] FTBFS with libav10
Severity set to 'serious' from 'important'
> reopen 739237
Bug #739237 {Done: Reinhard Tartler } [ffmpeg2theora] 
FTBFS with libav10
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ffmpeg2theora/0.29.0~git+20140316-1.
> severity 739237 serious
Bug #739237 [ffmpeg2theora] FTBFS with libav10
Severity set to 'serious' from 'important'
> reopen 739238
Bug #739238 {Done: mfvesc...@gmail.com (Matteo F. Vescovi)} [src:blender] FTBFS 
with libav10
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions blender/2.69+git20140225.cef73d54-1.
> severity 739238 serious
Bug #739238 [src:blender] FTBFS with libav10
Severity set to 'serious' from 'important'
> reopen 739240
Failed to reopen 739240: Not altering archived bugs; see unarchive.

> severity 739240 serious
Failed to set severity of Bug 739240 to serious: Not altering archived bugs; 
see unarchive.

> reopen 739242
Failed to reopen 739242: Not altering archived bugs; see unarchive.

> severity 739242 serious
Failed to set severity of Bug 739242 to serious: Not altering archived bugs; 
see unarchive.

> reopen 739243
Bug #739243 {Done: Alberto Garcia } [fuse-emulator-utils] 
FTBFS with libav10
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions fuse-emulator-utils/1.1.1-2.
> severity 739243 serious
Bug #739243 [fuse-emulator-utils] FTBFS with libav10
Severity set to 'serious' from 'important'
> reopen 739244
Failed to reopen 739244: Not altering archived bugs; see unarchive.

> severity 739244 serious
Failed to set severity of Bug 739244 to serious: Not altering archived bugs; 
see unarchive.

> reopen 739301
Bug #739301 {Done: Reinhard Tartler } [src:cmus] FTBFS 
with libav10
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions wi

Processed: systemd-sysv: #747535 Was: Re: systemd-fsck?

[Debian Bug Tracking System]

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

> severity 747535 serious
Bug #747535 [systemd-sysv] systemd-sysv: Ask before installing when upgrading 
to/installing jessie
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed (with 1 errors): Libav10 is now in unstable

[Debian Bug Tracking System]

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

> Libav 10 is now in unstable.
Unknown command or malformed arguments to command.
> severity 739239 serious
Bug #739239 [forked-daapd] FTBFS with libav10
Severity set to 'serious' from 'important'
> severity 739328 serious
Bug #739328 [src:lightspark] FTBFS with libav10
Severity set to 'serious' from 'important'
> severity 739453 serious
Bug #739453 [xine-lib] FTBFS with libav10
Severity set to 'serious' from 'important'
> severity 739664 serious
Bug #739664 [src:libavg] libavg: FTBFS with libav 10
Severity set to 'serious' from 'important'
> severity 739312 serious
Bug #739312 [src:k3b] FTBFS with libav10
Severity set to 'serious' from 'important'
> severity 739433 serious
Bug #739433 [performous] FTBFS with libav10
Severity set to 'serious' from 'important'
> severity 739209 serious
Bug #739209 [alsa-plugins] FTBFS against libav10
Severity set to 'serious' from 'important'
> severity 739440 serious
Bug #739440 [src:opencv] FTBFS with libav10
Severity set to 'serious' from 'important'
> severity 739462 serious
Bug #739462 [vtk] FTBFS with libav10
Severity set to 'serious' from 'important'
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
739209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739209
739239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739239
739312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739312
739328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739328
739433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739433
739440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739440
739453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739453
739462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739462
739664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747808: libkolab: FTBFS: error: redefinition of 'struct QMetaTypeId'

[David Suárez]

Source: libkolab
Version: 0.4.2-7.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> /usr/bin/cmake -E cmake_progress_report 
> /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 6
> [ 79%] Building CXX object 
> tests/CMakeFiles/calendaringtest.dir/calendaringtest.cpp.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/tests && /usr/bin/c++   
> -DKDEPIMLIBS_VERSION_DEVEL -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB 
> -DQT_NETWORK_LIB -DQT_SVG_LIB -DQT_TEST_LIB -DQT_XML_LIB 
> -DTEST_DATA_PATH=\"/«PKGBUILDDIR»/tests\" -D_BSD_SOURCE -g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -D_FORTIFY_SOURCE=2  -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align 
> -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions 
> -DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual 
> -fno-threadsafe-statics -fvisibility=hidden -Werror=return-type 
> -fvisibility-inlines-hidden -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef 
> -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security 
> -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common 
> -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden 
> -Werror=return-type -fvisibility-inlines-hidden -fexceptions 
> -UQT_NO_EXCEPTIONS -fPIC -g -I/usr/include/qt4/phonon 
> -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtXml 
> -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest 
> -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtSql 
> -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtScript 
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtHelp 
> -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative 
> -I/usr/include/qt4/QtDBus -I/usr/include/qt4/Qt3Support 
> -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/include/qt4/Qt 
> -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 -I/usr/include/KDE 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu -I/«PKGBUILDDIR»/kolabformatV2 
> -I/usr/include/kolabxml -I/«PKGBUILDDIR»/. 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/tests-o 
> CMakeFiles/calendaringtest.dir/calendaringtest.cpp.o -c 
> /«PKGBUILDDIR»/tests/calendaringtest.cpp
> In file included from /usr/include/qt4/QtTest/qtestcase.h:48:0,
>  from /usr/include/qt4/QtTest/qtest.h:46,
>  from /usr/include/qt4/QtTest/QTest:1,
>  from /«PKGBUILDDIR»/tests/calendaringtest.cpp:21:
> /usr/include/qt4/QtCore/qmetatype.h:268:12: error: redefinition of 'struct 
> QMetaTypeId'
>  struct QMetaTypeId< TYPE >  \
> ^
> /«PKGBUILDDIR»/tests/testhelpers.h:47:1: note: in expansion of macro 
> 'Q_DECLARE_METATYPE'
>  Q_DECLARE_METATYPE(KCalCore::Duration);
>  ^
> /usr/include/qt4/QtCore/qmetatype.h:268:12: error: previous definition of 
> 'struct QMetaTypeId'
>  struct QMetaTypeId< TYPE >  \
> ^
> make[3]: *** [tests/CMakeFiles/calendaringtest.dir/calendaringtest.cpp.o] 
> Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/05/10/libkolab_0.4.2-7.1_unstable.log

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

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747807: accessodf: FTBFS: error: method createMessageBox in interface XMessageBoxFactory cannot be applied to given types

[David Suárez]

Source: accessodf
Version: 0.1-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> ant -Don-debian=True uno-package
> Buildfile: /«PKGBUILDDIR»/build.xml
> 
> -detect-os:
> 
> -windows-properties:
> 
> -macosx-properties:
> 
> -linux-properties:
> 
> -debian-properties:
> 
> -init-build:
> 
> -copy-external-jars:
> [mkdir] Created dir: /«PKGBUILDDIR»/dist/lib
> 
> -pre-init:
> 
> -do-init:
> 
> -uno-project-init:
> [mkdir] Created dir: /«PKGBUILDDIR»/build/idl
> [mkdir] Created dir: /«PKGBUILDDIR»/build/idl/urd
> [mkdir] Created dir: /«PKGBUILDDIR»/build/idl/rdb
> [mkdir] Created dir: /«PKGBUILDDIR»/build/img
> [mkdir] Created dir: /«PKGBUILDDIR»/build/cpreg
> 
> -uno-idl-idlc-condition:
> 
> -uno-idl-idlc:
> [propertyfile] Creating new property file: 
> /«PKGBUILDDIR»/build/idl/idl_list.properties
> 
> -uno-idl-regmerge:
> 
> -uno-idl-javamaker-condition:
> 
> -uno-idl-javamaker:
> 
> -uno-idl-result:
> [touch] Creating /«PKGBUILDDIR»/build/idlc.compile
>  [echo] build UNO idl files finished
> 
> uno-idl-compile:
> 
> -check-uno-types:
> 
> -do-empty-unopath:
> 
> -do-idl-unopath:
> 
> -do-uno-types:
> 
> -jar-idl-types:
> 
> -post-init:
> 
> -init-check:
> 
> -init-macrodef-javac:
> 
> -init-macrodef-junit:
> 
> init:
> 
> -compile-core:
> [mkdir] Created dir: /«PKGBUILDDIR»/build/core-classes
> [javac] Compiling 16 source files to /«PKGBUILDDIR»/build/core-classes
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 1.5
> [javac] 1 warning
> 
> -build-core:
>   [jar] Building jar: /«PKGBUILDDIR»/dist/lib/accessodf.jar
> 
> core-jar:
> 
> -deps-jar-init:
> 
> deps-jar:
> 
> -warn-already-built-jar:
> [propertyfile] Updating property file: 
> /«PKGBUILDDIR»/build/built-jar.properties
> 
> -check-automatic-build:
> 
> -clean-after-automatic-build:
> 
> -verify-automatic-build:
> 
> -pre-pre-compile:
> [mkdir] Created dir: /«PKGBUILDDIR»/build/addon-classes
> 
> -pre-compile:
> 
> -copy-persistence-xml:
> 
> -compile-depend:
> 
> -do-compile:
> [mkdir] Created dir: /«PKGBUILDDIR»/build/empty
> [javac] Compiling 33 source files to /«PKGBUILDDIR»/build/addon-classes
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 1.5
> [javac] 
> /«PKGBUILDDIR»/addon/be/docarch/accessodf/ooo/UnoAwtUtils.java:116: error: 
> method createMessageBox in interface XMessageBoxFactory cannot be applied to 
> given types;
> [javac] XMessageBox box = 
> messageBoxFactory.createMessageBox(parentWindowPeer, messageBoxRectangle, 
> messageBoxType, messageBoxButtons, messageBoxTitle, message);
> [javac]^
> [javac]   required: XWindowPeer,MessageBoxType,int,String,String
> [javac]   found: XWindowPeer,Rectangle,String,int,String,String
> [javac]   reason: actual and formal argument lists differ in length
> [javac] Note: 
> /«PKGBUILDDIR»/addon/be/docarch/accessodf/ooo/CentralRegistrationClass.java 
> uses unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 1 error
> [javac] 1 warning
> 
> BUILD FAILED
> /«PKGBUILDDIR»/build.xml:769: The following error occurred while executing 
> this line:
> /«PKGBUILDDIR»/build.xml:644: Compile failed; see the compiler error output 
> for details.
> 
> Total time: 4 seconds
> make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/05/10/accessodf_0.1-4_unstable.log

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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747806: cyrus-imapd-2.4: FTBFS: ld.bfd.real: cannot find -lpci

[David Suárez]

Source: cyrus-imapd-2.4
Version: 2.4.17+caldav~beta9-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -L/usr/lib -L/usr/lib -Wl,-z,defs -Wl,--as-needed  -lpthread -o master 
> master.o masterconf.o cyrusMasterMIB.o ../lib/lock_fcntl.o 
> ../lib/libcyrus_min.a -Wl,-z,relro -Wl,-z,now -L/usr/lib/x86_64-linux-gnu 
> -lnetsnmpmibs -lpci -ldl -lnetsnmpagent -lwrap -Wl,-E -lnetsnmp -lcrypto -lm  
> -ldl  -lfl   -L/usr/lib  -ldb -lssl -lcrypto -lz -lcom_err 
> /usr/bin/ld.bfd.real: cannot find -lpci
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/05/10/cyrus-imapd-2.4_2.4.17+caldav~beta9-3_unstable.log

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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747803: libmrss: FTBFS: configure: line 12750: syntax error near unexpected token `NXML,'

[David Suárez]

Source: libmrss
Version: 0.19.2-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.
> checking curl/curl.h presence... yes
> checking for curl/curl.h... yes
> checking for curl_version in -lcurl... yes
> ./configure: line 12750: syntax error near unexpected token `NXML,'
> ./configure: line 12750: `PKG_CHECK_MODULES(NXML, nxml >= 0.18 , nxml=yes, 
> nxml=no)'


Relevant part (hopefully):
The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/05/10/libmrss_0.19.2-5_unstable.log

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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747800: meep-mpich2: FTBFS: error: guile-config is broken

[David Suárez]

Source: meep-mpich2
Version: 1.1.1-10
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh_testdir
> mkdir -p debian/build-mpich2
> cat configure | \
>   sed "s/PACKAGE_NAME='meep'/PACKAGE_NAME='meep-mpich2'/g" |\
>   sed "s/PACKAGE='meep'/PACKAGE='meep-mpich2'/g" > configure-mpich2
> chmod 755 configure-mpich2
> cd debian/build-mpich2 && \
> F77=gfortran ../../configure-mpich2 --host=x86_64-linux-gnu 
> --build=x86_64-linux-gnu --prefix=/usr --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --with-libctl=/usr/share/libctl3 
> --enable-shared --with-pic --enable-cxx --with-mpi=yes 
> configure-mpich2: WARNING: unrecognized options: --enable-cxx
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for x86_64-linux-gnu-g++... x86_64-linux-gnu-g++
> checking for C++ compiler default output file name... a.out
> checking whether the C++ compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables... 
> checking for suffix of object files... o
> checking whether we are using the GNU C++ compiler... yes
> checking whether x86_64-linux-gnu-g++ accepts -g... yes
> checking for style of include used by make... GNU
> checking dependency style of x86_64-linux-gnu-g++... gcc3
> checking for mpic++... mpic++
> checking for MPI_Init... yes
> checking for mpi.h... yes
> checking for extra flag needed to combine stdio.h and mpi.h... none
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc
> checking whether we are using the GNU C compiler... yes
> checking whether x86_64-linux-gnu-gcc accepts -g... yes
> checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed
> checking dependency style of x86_64-linux-gnu-gcc... gcc3
> checking for C++ compiler vendor... gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by x86_64-linux-gnu-gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 1572864
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for x86_64-linux-gnu-objdump... x86_64-linux-gnu-objdump
> checking how to recognize dependent libraries... pass_all
> checking for x86_64-linux-gnu-ar... x86_64-linux-gnu-ar
> checking for x86_64-linux-gnu-strip... x86_64-linux-gnu-strip
> checking for x86_64-linux-gnu-ranlib... x86_64-linux-gnu-ranlib
> checking command to parse /usr/bin/nm -B output from x86_64-linux-gnu-gcc 
> object... ok
> checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... yes
> checking whether we are using the GNU C++ compiler... (cached) yes
> checking whether mpic++ accepts -g... (cached) yes
> checking dependency style of mpic++... (cached) gcc3
> checking how to run the C++ preprocessor... mpic++ -E
> checking for objdir... .libs
> checking if x86_64-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
> checking for x86_64-linux-gnu-gcc option to produce PIC... -fPIC -DPIC
> checking if x86_64-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes
> checking if x86_64-linux-gnu-gcc static flag -static works... yes
> checking if x86_64-linux-gnu-gcc supports -c -o file.o... yes
> checking if x86_64-linux-gnu-gcc supports -c -o file.o... (cached) yes
> checking whether the x86_64-linux-gnu-gcc linker (/usr/bin/ld -m elf_x86_64) 
> supports shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libra

Bug#747805: duo-unix: FTBFS: error: OpenSSL not found

[David Suárez]

Source: duo-unix
Version: 1.9.6-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> checking for openssl/ssl.h in /usr/ssl... no
> checking for openssl/ssl.h in /usr/pkg... no
> checking for openssl/ssl.h in /usr/local... no
> checking for openssl/ssl.h in /usr... no
> checking whether compiling and linking against OpenSSL works... no
> configure: error: in `/«PKGBUILDDIR»'
> configure: error: OpenSSL not found
> See `config.log' for more details

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/05/10/duo-unix_1.9.6-1_unstable.log

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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747799: certmonger: FTBFS: error: krb5-config not found

[David Suárez]

Source: certmonger
Version: 0.57-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> checking for xmlrpc-c-config... /usr/bin/xmlrpc-c-config
> checking for XMLRPC CFLAGS... -I/usr/include 
> checking for XMLRPC LIBS... -L/usr/lib   -lxmlrpc_client -lxmlrpc 
> -lxmlrpc_util -lxmlrpc_xmlparse -lxmlrpc_xmltok -L/usr/lib/x86_64-linux-gnu 
> -lcurl 
> checking for struct xmlrpc_curl_xportparms.gssapi_delegation... no
> checking for krb5-config... no
> configure: error: krb5-config not found
> dh_auto_configure: ../configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=${prefix}/include --mandir=${prefix}/share/man 
> --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --libexecdir=${prefix}/lib/certmonger --disable-maintainer-mode 
> --disable-dependency-tracking --with-tmpdir=/var/run/certmonger CFLAGS= 
> LDFLAGS= returned exit code 1
> make[1]: *** [override_dh_auto_configure] Error 2
> debian/rules:20: recipe for target 'override_dh_auto_configure' failed
> make[1]: Leaving directory '/«PKGBUILDDIR»'

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/05/10/certmonger_0.57-1_unstable.log

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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747801: ario: FTBFS: error: Missing dependency: libgcrypt

[David Suárez]

Source: ario
Version: 1.5.1-1.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> checking if msgfmt accepts -c... yes
> checking for gmsgfmt... (cached) /usr/bin/msgfmt
> checking for xgettext... (cached) /usr/bin/xgettext
> checking for libgcrypt-config... no
> checking for LIBGCRYPT - version >= 1.4.0... no
> configure: error: Missing dependency: libgcrypt

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/05/10/ario_1.5.1-1.1_unstable.log

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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747798: libquvi: FTBFS: configure.ac:79: error: possibly undefined macro: AC_DEFINE

[David Suárez]

Source: libquvi
Version: 0.4.1-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with autoreconf
>dh_testdir
>dh_autoreconf
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `config.aux'.
> libtoolize: copying file `config.aux/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
> libtoolize: copying file `m4/libtool.m4'
> libtoolize: copying file `m4/ltoptions.m4'
> libtoolize: copying file `m4/ltsugar.m4'
> libtoolize: copying file `m4/ltversion.m4'
> libtoolize: copying file `m4/lt~obsolete.m4'
> configure.ac:79: error: possibly undefined macro: AC_DEFINE
>   If this token and others are legitimate, please use m4_pattern_allow.
>   See the Autoconf documentation.
> autoreconf: /usr/bin/autoconf failed with exit status: 1
> dh_autoreconf: autoreconf -f -i returned exit code 1
> make: *** [build] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/05/10/libquvi_0.4.1-2_unstable.log

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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747802: epiphany-browser: FTBFS: error "Headers and cannot be included together."

[David Suárez]

Source: epiphany-browser
Version: 3.8.2-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I/«PKGBUILDDIR»/./embed/web-extension -I../..  -I/«PKGBUILDDIR»/./embed 
> -I/«PKGBUILDDIR»/./lib  -D_FORTIFY_SOURCE=2 -pthread 
> -I/usr/include/webkitgtk-3.0 -I/usr/include/gtk-3.0 
> -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
> -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libdrm -I/usr/include/libpng12 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 
> -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 
> -I/usr/include/webkitgtk-3.0 -I/usr/include/libsecret-1 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -Wall -c -o libephywebextension_la-ephy-web-extension.lo `test -f 
> 'ephy-web-extension.c' || echo 
> '/«PKGBUILDDIR»/./embed/web-extension/'`ephy-web-extension.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. 
> -I/«PKGBUILDDIR»/./embed/web-extension -I../.. -I/«PKGBUILDDIR»/./embed 
> -I/«PKGBUILDDIR»/./lib -D_FORTIFY_SOURCE=2 -pthread 
> -I/usr/include/webkitgtk-3.0 -I/usr/include/gtk-3.0 
> -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
> -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libdrm -I/usr/include/libpng12 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 
> -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 
> -I/usr/include/webkitgtk-3.0 -I/usr/include/libsecret-1 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -Wall -c /«PKGBUILDDIR»/./embed/web-extension/ephy-web-extension.c  -fPIC 
> -DPIC -o .libs/libephywebextension_la-ephy-web-extension.o
> In file included from /«PKGBUILDDIR»/./embed/ephy-web-view.h:32:0,
>  from /«PKGBUILDDIR»/./embed/ephy-embed.h:26,
>  from /«PKGBUILDDIR»/./embed/ephy-adblock.h:23,
>  from /«PKGBUILDDIR»/./embed/uri-tester.h:22,
>  from 
> /«PKGBUILDDIR»/./embed/web-extension/ephy-web-extension.c:30:
> /usr/include/webkitgtk-3.0/webkit2/webkit2.h:22:2: error: #error "Headers 
>  and  cannot be included 
> together."
>  #error "Headers  and  
> cannot be included together."
>   ^
> In file included from 
> /«PKGBUILDDIR»/./embed/web-extension/ephy-web-extension.c:34:0:
> /usr/include/webkitgtk-3.0/webkit2/webkit-web-extension.h:21:2: error: #error 
> "Headers  and  cannot be 
> included together."
>  #error "Headers  and  
> cannot be included together."
>   ^
> make[5]: *** [libephywebextension_la-ephy-web-extension.lo] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/05/10/epiphany-browser_3.8.2-5_unstable.log

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

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747797: totem-plugin-arte: FTBFS: error: The name `action_error' does not exist in the context of `Totem.Object'

[David Suárez]

Source: totem-plugin-arte
Version: 3.2.1-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/«PKGBUILDDIR»'
> valac --library=arteplus7 arteplus7.vala arteparser.vala cache.vala 
> url-extractor.vala video.vala cell-renderer-video.vala video-list-view.vala 
> connection-status.vala --pkg Totem-1.0 --pkg PeasGtk-1.0 --pkg libsoup-2.4 
> --pkg gtk+-3.0 --pkg gio-2.0 --pkg json-glib-1.0 -X -D_FORTIFY_SOURCE=2 -X -g 
> -X -O2 -X -fstack-protector -X --param=ssp-buffer-size=4 -X -Wformat -X 
> -Werror=format-security -X -Wl,-z,relro -X -fPIC -X -shared --Xcc="-D 
> GETTEXT_PACKAGE=\"totem-arte\"" -o libarteplus7.so
> arteplus7.vala:68.23-68.52: warning: Soup.SessionAsync.with_options is 
> deprecated
> arteplus7.vala:81.23-81.52: warning: Soup.SessionAsync.with_options is 
> deprecated
> video-list-view.vala:280.54-280.62: warning: Gtk.Stock has been deprecated 
> since 3.10
> arteparser.vala:78.32-78.51: warning: Soup.KnownStatusCode has been 
> deprecated since vala-0.22. Use Status
> arteplus7.vala:431.13-431.26: error: The name `action_error' does not exist 
> in the context of `Totem.Object'
> t.action_error (_("Markup Parser Error"),
> ^^
> arteplus7.vala:434.13-434.26: error: The name `action_error' does not exist 
> in the context of `Totem.Object'
> t.action_error (_("Network problem"),
> ^^
> arteparser.vala:144.32-144.51: warning: Soup.KnownStatusCode has been 
> deprecated since vala-0.22. Use Status
> arteplus7.vala:503.17-503.30: error: The name `action_error' does not exist 
> in the context of `Totem.Object'
> t.action_error (_("This video access is restricted"),
> ^^
> arteplus7.vala:507.17-507.30: error: The name `action_error' does not exist 
> in the context of `Totem.Object'
> t.action_error (_("This video is not available yet"),
> ^^
> arteplus7.vala:511.17-511.30: error: The name `action_error' does not exist 
> in the context of `Totem.Object'
> t.action_error (_("Video URL Extraction Error"),
> ^^
> arteplus7.vala:515.17-515.30: error: The name `action_error' does not exist 
> in the context of `Totem.Object'
> t.action_error (_("Video URL Extraction Error"),
> ^^
> arteplus7.vala:521.9-521.34: error: The name `add_to_playlist_and_play' does 
> not exist in the context of `Totem.Object'
> t.add_to_playlist_and_play (stream_url, title);
> ^^
> arteplus7.vala:174.17-174.25: warning: Gtk.Stock has been deprecated since 
> 3.10
> arteplus7.vala:178.17-178.25: warning: Gtk.Stock has been deprecated since 
> 3.10
> Compilation failed: 7 error(s), 7 warning(s)
> make[2]: *** [all] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/05/10/totem-plugin-arte_3.2.1-2_unstable.log

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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747804: spotlighter: FTBFS: error: Test for GTK3+ failed

[David Suárez]

Source: spotlighter
Version: 0.3-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> checking for pkg-config... /usr/bin/pkg-config
> checking for GTK+ - version >= 2.99.3... no
> *** Could not run GTK+ test program, checking why...
> *** The test program failed to compile or link. See the file config.log for 
> the
> *** exact error that occured. This usually means GTK+ is incorrectly 
> installed.
> configure: error: Test for GTK3+ failed. See the file 'INSTALL' for help.

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/05/10/spotlighter_0.3-1_unstable.log

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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#747795: mysql-workbench: FTBFS: undefined reference to `sqlite::command::operator%(long)'

[David Suárez]

Source: mysql-workbench
Version: 6.1.4+dfsg-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140510 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /usr/bin/c++   -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -D_FORTIFY_SOURCE=2-Wl,-z,relro -Wl,--as-needed 
> CMakeFiles/genwrap.dir/genwrap.cpp.o  -o genwrap  
> -L/«BUILDDIR»/mysql-workbench-6.1.4+dfsg/obj-x86_64-linux-gnu/antlr-wb 
> -rdynamic ../../library/grt/src/libgrt.so ../../library/base/libwbbase.so 
> ../../backend/wbpublic/libwbpublic.so -lpcre -lpcrecpp -lmysqlclient 
> -lpython2.7 -llua5.1 -lm -lxml2 -luuid ../../library/base/libwbbase.so 
> ../../library/canvas/src/libmdcanvas.so ../../library/forms/libmforms.so 
> ../../frontend/linux/linux_utilities/liblinux_utilities.so -ltinyxml 
> ../../library/dbc/libcdbc.so -lmysqlcppconn -lvsqlitepp -lcairo 
> ../../ext/scintilla/gtk/libwbscintilla.so 
> ../../library/mysql-parser/libmysqlparser.so -lfreetype -lgtk-x11-2.0 
> -lgdk-x11-2.0 -lcairo -lpango-1.0 -lpangocairo-1.0 -lpangoft2-1.0 
> -lpangoxft-1.0 -lgdk_pixbuf-2.0 -lgthread-2.0 -lgmodule-2.0 -lgio-2.0 
> -latk-1.0 -lgobject-2.0 -lglib-2.0 -lgtkmm-2.4 -lgdkmm-2.4 -lpangomm-1.4 
> -lcairomm-1.0 -lgiomm-2.4 -latkmm-1.6 -lglibmm-2.4 -lsigc-2.0 -lgmodule-2.0 
> -lgthread-2.0 
> -L/«BUILDDIR»/mysql-workbench-6.1.4+dfsg/obj-x86_64-linux-gnu/antlr-wb 
> -lantlr3c_wb -lgnome-keyring -lglib-2.0 -lctemplate -lGL -lSM -lICE -lX11 
> -lXext -lpcre -lpcrecpp 
> -Wl,-rpath,/«BUILDDIR»/mysql-workbench-6.1.4+dfsg/obj-x86_64-linux-gnu/antlr-wb:/«BUILDDIR»/mysql-workbench-6.1.4+dfsg/obj-x86_64-linux-gnu/library/grt/src:/«BUILDDIR»/mysql-workbench-6.1.4+dfsg/obj-x86_64-linux-gnu/library/base:/«BUILDDIR»/mysql-workbench-6.1.4+dfsg/obj-x86_64-linux-gnu/backend/wbpublic:/«BUILDDIR»/mysql-workbench-6.1.4+dfsg/obj-x86_64-linux-gnu/library/canvas/src:/«BUILDDIR»/mysql-workbench-6.1.4+dfsg/obj-x86_64-linux-gnu/library/forms:/«BUILDDIR»/mysql-workbench-6.1.4+dfsg/obj-x86_64-linux-gnu/frontend/linux/linux_utilities:/«BUILDDIR»/mysql-workbench-6.1.4+dfsg/obj-x86_64-linux-gnu/library/dbc:/«BUILDDIR»/mysql-workbench-6.1.4+dfsg/obj-x86_64-linux-gnu/ext/scintilla/gtk:/«BUILDDIR»/mysql-workbench-6.1.4+dfsg/obj-x86_64-linux-gnu/library/mysql-parser
>  
> ../../backend/wbpublic/libwbpublic.so: undefined reference to 
> `sqlite::command::operator%(long)'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/05/10/mysql-workbench_6.1.4+dfsg-2_unstable.log

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

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org