Bug#757417: libparted2-udeb: breaks auto-lvm in d-i

[Petter Reinholdtsen]

Hi.  Could this issue also affect the grub installer udeb?  When
testing Debian Edu based on Jessie, I had to manually partition to
work around the automatic lvm partition issue, but at the end of the
installation grub was unable to find the file system partitions.  I
could install lilo, but the installed system did not boot at the
end. :( I have not had time to investigate further.

-- 
Happy hacking
Petter Reinholdtsen


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

Bug#757581: pytables: FTBFS on s390x

[Antonio Valentino]

The problem seems to be related to the lz4 compressor.

I am investigating it.


cheers

-- 
Antonio Valentino


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

Bug#689778: marked as done (havp should maintain /var/run/havp in init script and postrm)

[Debian Bug Tracking System]

Your message dated Sun, 10 Aug 2014 06:03:35 +
with message-id 
and subject line Bug#689778: fixed in havp 0.92a-3
has caused the Debian Bug report #689778,
regarding havp should maintain /var/run/havp in init script and postrm
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.)


-- 
689778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: havp
Version: 0.92a-2
Severity: serious

Hi,

The havp postinst does:
chown havp:havp /var/run/havp

however, nothing created this folder. Moreover, this should be only
done in the postinst, and this folder should be removed in the postrm.

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
Source: havp
Source-Version: 0.92a-3

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated havp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 10 Aug 2014 01:12:27 -0400
Source: havp
Binary: havp
Architecture: source i386
Version: 0.92a-3
Distribution: unstable
Urgency: medium
Maintainer: ClamAV Team 
Changed-By: Scott Kitterman 
Description:
 havp   - HTTP Anti Virus Proxy
Closes: 628612 628613 628615 664346 666016 689778 689892
Changes:
 havp (0.92a-3) unstable; urgency=medium
 .
   [ Sebastian Andrzej Siewior ]
   * convert package to git-dpm and drop dpatch (Closes: #664346).
   * Do not ship /var/run/havp, patch by Thomas Goirand (Closes: #689892).
   * purge /var/run/havp und removal (Closes: #689778).
   * remove the -x flag from .html files in the debian folder where the package
 got intalled to actually fix lintian executable-not-elf-or-script.
   * redo the rules with minimal debhelper 8
 .
   [ Andreas Cadhalpun ]
   * Use 'set -e' in maintainer scripts.
   * Add homepage to debian/control.
   * Add CPPFLAGS to CFLAGS, because CPPFLAGS are not respected by havp's
 build system.
   * Call 'modprobe loop' in the init script before trying to mount a loop
 device. This is necessary for newer kernels.
   * Remove all logs in /var/log/havp, the contents of /var/lib/havp and
 /etc/default/havp on purge (Closes: #666016).
   * Fix restart action of init script. (Closes: #628612)
 Thanks to Laurent Baysse for the bug report and patch.
 .
   [ Scott Kitterman ]
   * Agreed maintainer change to pkg-clamav team, added myself, Sebastian
 Andrzej Siewior, and Andreas Cadhalpun as uploaders along with Rene
 Mayrhofer (the previous maintainer)
   * Fix PID file naming for reload statement in havp.init, partially addresses
 #524045
   * Add lsb-base (>= 3.2-13) to depends
   * Use lsb common functions to simplify status case in havp.init
   * Added remote_fs to Required-start and Required stop in havp.init
   * Add run level 1 to default stop in havp.init
   * Bump stanards version to 3.9.5
   * Add SSLTIMEOUT to etc/havp/havp.config.in (Closes: #628613)
   * Set default clamd socket value to the correct location for Debian
(Closes: #628615)
Checksums-Sha1:
 6fc52064c48f43bf258d3ec5a425d3d0372ca967 2076 havp_0.92a-3.dsc
 4cb06fb0c2d6b9cbee1a2e8f0ac4eea529d5415d 23472 havp_0.92a-3.debian.tar.xz
 e7808e87acae26d9d80ef6d197d6f570aed83e1b 137310 havp_0.92a-3_i386.deb
Checksums-Sha256:
 1838fc17a285ea577198273230984da626c18326831c522c525c51876b50fc7d 2076 
havp_0.92a-3.dsc
 338cb927ae0743fd1963f75b1db37c43ecee09ef4f44c65f1445b8a1dff18874 23472 
havp_0.92a-3.debian.tar.xz
 15457578bcbb825968ab75f20f572bd1047447d36453582d1094b96798d0decf 137310 
havp_0.92a-3_i386.deb
Files:
 50f5875b306e721b6c41c0f32ddd84e6 137310 net optional havp_0.92a-3_i386.deb
 3ab0337a5d1f63d2cc649a6c09744f8b 2076 net optional havp_0.92a-3.dsc
 54b7404d684031215f816f2ee6f51e0b 23472 net optional havp_0.92a-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJT5wnHAAoJEHjX3vua1ZrxWKUQALpXd9UhGlyInVxAlZWrr+HP
RIpXw3nSdZpxkCLcIsZ2EprwOG/PSVHHXVu2dgS6lFK7A8GLNMuZVSSsakGI/R7d
m6COqD4UZDhYaqKd+uMWAKhRUB

Bug#689892: marked as done (Ships a folder in /var/run or /var/lock (Policy Manual section 9.3.2))

[Debian Bug Tracking System]

Your message dated Sun, 10 Aug 2014 06:03:35 +
with message-id 
and subject line Bug#689892: fixed in havp 0.92a-3
has caused the Debian Bug report #689892,
regarding Ships a folder in /var/run or /var/lock (Policy Manual section 9.3.2)
to be marked as done.

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

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


-- 
689892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: havp
Version: 3.0-a9-1
Severity: serious
Tags: patch

Dear Maintainer,

Andreas Beckmann  reported in -devel that your package
(as well as 27 others) ships a folder either in /var/run or /var/lock. This
is forbidden by policy.

Lintian detects the problem and warns as follow:

/var/run may be a temporary filesystem, so any directories or files needed
/there must be created dynamically at boot time.

Refer to Debian Policy Manual section 9.3.2 (Writing the scripts) for
details.

Severity: serious, Certainty: possible
Check: files, Type: binary, udeb

which is why I am reporting this bug with severity serious (and there fore,
release critical).

Please fix your package. I have attached what I believe is a good fix the
problem, however, I haven't tried it, and I haven't tested if something more
for creating the necessary folder at runtime should be added. Please make
sure to test before applying the patch blindly.

Cheers,

Thomas Goirand (zigo)
diff -u havp-0.92a/debian/changelog havp-0.92a/debian/changelog
--- havp-0.92a/debian/changelog
+++ havp-0.92a/debian/changelog
@@ -1,3 +1,10 @@
+havp (0.92a-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fixes (Closes: #XX).
+
+ -- Thomas Goirand   Sun, 07 Oct 2012 11:05:10 +
+
 havp (0.92a-2) unstable; urgency=low
 
   * Include debconf language updates from previous NMU and new updates.
diff -u havp-0.92a/debian/havp.init havp-0.92a/debian/havp.init
--- havp-0.92a/debian/havp.init
+++ havp-0.92a/debian/havp.init
@@ -37,6 +37,13 @@
 
 set -e
 
+if [ ! -d ${RUNDIR} ] ; then
+	mkdir -p ${RUNDIR}
+	if [ -d ${RUNDIR} ] ; then
+		chown ${USER}:${GROUP} ${RUNDIR}
+	fi
+fi
+
 case "$1" in
   start)
 # Create the run directory if it doesn't exist
diff -u havp-0.92a/debian/havp.postinst havp-0.92a/debian/havp.postinst
--- havp-0.92a/debian/havp.postinst
+++ havp-0.92a/debian/havp.postinst
@@ -37,7 +37,6 @@
   fi
   # care for proper ownership in any case (e.g. updating from an earlier 
   # havp package with different paths)
-  chown havp:havp /var/run/havp
   chown havp:havp /var/log/havp
   chown havp:havp /var/lib/havp
   chown havp:havp /var/spool/havp
diff -u havp-0.92a/debian/havp.postrm havp-0.92a/debian/havp.postrm
--- havp-0.92a/debian/havp.postrm
+++ havp-0.92a/debian/havp.postrm
@@ -29,7 +29,7 @@
   rm /var/lib/havp/havp.tmp
   rm /etc/default/havp
 fi
-
+	rm -rf /var/run/havp
 ;;
 
remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
--- End Message ---
--- Begin Message ---
Source: havp
Source-Version: 0.92a-3

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated havp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 10 Aug 2014 01:12:27 -0400
Source: havp
Binary: havp
Architecture: source i386
Version: 0.92a-3
Distribution: unstable
Urgency: medium
Maintainer: ClamAV Team 
Changed-By: Scott Kitterman 
Description:
 havp   - HTTP Anti Virus Proxy
Closes: 628612 628613 628615 664346 666016 689778 689892
Changes:
 havp (0.92a-3) unstable; urgency=medium
 .
   [ Sebastian Andrzej Siewior ]
   * convert package to git-dpm and drop dpatch (Closes: #664346).
   * Do not ship /var/run/havp, patch by Thomas Goirand (Closes: #689892).
   * purge /var/run/havp und removal (Closes: #689778).
   * remove the -x flag from .html files in the debian folder where the package
 got intalled to actually fix lintian executable-not-elf-or-script.
   * redo the rules with minimal de

Processed: block 754629 with 752295

[Debian Bug Tracking System]

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

> block 754629 with 752295
Bug #754629 {Done: Agustin Henze } [src:gdb-arm-none-eabi] 
gdb-arm-none-eabi: FTBFS on kfreebsd-i386: error: right-hand operand of comma 
expression has no effect
754629 was not blocked by any bugs.
754629 was not blocking any bugs.
Added blocking bug(s) of 754629: 752295
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
754629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754629
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#750621: marked as done (swig3.0 required)

[Debian Bug Tracking System]

Your message dated Sun, 10 Aug 2014 05:09:46 +0200
with message-id <1407640186.3151.83.ca...@fortknox.nn7.de>
and subject line 
has caused the Debian Bug report #746893,
regarding swig3.0 required
to be marked as done.

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

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


-- 
746893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: swig
Version: 2.0.7-3
Severity: serious

Please package swig3.0.2 ASAP.

The introduction of g++ 4.8/4.9 in the archive makes c++11 enabled swig
wrapper code fail to compile like 

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746893

swig3.0 fixes this and is a hard requirement to get such packages fixed
/ keep them in testing.


Thank you very much!

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

Kernel: Linux 3.14.4 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages swig depends on:
ii  swig2.0  2.0.7-3

swig recommends no packages.

Versions of packages swig suggests:
pn  swig-doc   
pn  swig-examples  

-- no debconf information
--- End Message ---
--- Begin Message ---



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

Bug#746893: marked as done (python-shogun: ftbfs with GCC-4.9)

[Debian Bug Tracking System]

Your message dated Sun, 10 Aug 2014 05:09:46 +0200
with message-id <1407640186.3151.83.ca...@fortknox.nn7.de>
and subject line 
has caused the Debian Bug report #746893,
regarding python-shogun: ftbfs with GCC-4.9
to be marked as done.

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

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


-- 
746893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-shogun
Version: 3.2.0-1
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

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

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/python-shogun_3.2.0-1_unstable_gcc49.log
The last lines of the build log are at the end of this report.

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

  apt-get -t experimental install g++ 

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

[...]
/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/interfaces/python_modular/modshogunPYTHON_wrap.cxx:16728:84:
 note:   cannot convert 'arg2' (type 
'SwigValueWrapper<__gnu_cxx::__normal_iterator > 
>') to type 'std::vector::const_iterator {aka 
__gnu_cxx::__normal_iterator >}'
   result = (arg1)->insert(arg2,(std::vector< double >::value_type const 
&)*arg3);

^
/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/interfaces/python_modular/modshogunPYTHON_wrap.cxx:
 In function 'PyObject* _wrap_DoubleStdVector_insert__SWIG_1(PyObject*, 
PyObject*)':
/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/interfaces/python_modular/modshogunPYTHON_wrap.cxx:16809:80:
 error: no matching function for call to 
'std::vector::insert(SwigValueWrapper<__gnu_cxx::__normal_iterator > >&, std::vector::size_type&, const value_type&)'
   (arg1)->insert(arg2,arg3,(std::vector< double >::value_type const 
&)*arg4);

^
/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/interfaces/python_modular/modshogunPYTHON_wrap.cxx:16809:80:
 note: candidates are:
In file included from /usr/include/c++/4.9/vector:69:0,
 from 
/usr/include/shogun/optimization/liblinear/shogun_liblinear.h:42,
 from /usr/include/shogun/classifier/svm/LibLinear.h:20,
 from 
/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/interfaces/python_modular/modshogunPYTHON_wrap.cxx:5127:
/usr/include/c++/4.9/bits/vector.tcc:107:5: note: std::vector<_Tp, 
_Alloc>::iterator std::vector<_Tp, _Alloc>::insert(std::vector<_Tp, 
_Alloc>::const_iterator, const value_type&) [with _Tp = double; _Alloc = 
std::allocator; std::vector<_Tp, _Alloc>::iterator = 
__gnu_cxx::__normal_iterator >; typename 
std::_Vector_base<_Tp, _Alloc>::pointer = double*; std::vector<_Tp, 
_Alloc>::const_iterator = __gnu_cxx::__normal_iterator >; typename __gnu_cxx::__alloc_traits::_Tp_alloc_type>::const_pointer = const double*; 
std::vector<_Tp, _Alloc>::value_type = double]
 vector<_Tp, _Alloc>::
 ^
/usr/include/c++/4.9/bits/vector.tcc:107:5: note:   candidate expects 2 
arguments, 3 provided
In file included from /usr/include/c++/4.9/vector:64:0,
 from 
/usr/include/shogun/optimization/liblinear/shogun_liblinear.h:42,
 from /usr/include/shogun/classifier/svm/LibLinear.h:20,
 from 
/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/interfaces/python_modular/modshogunPYTHON_wrap.cxx:5127:
/usr/include/c++/4.9/bits/stl_vector.h:1014:7: note: std::vector<_Tp, 
_Alloc>::iterator std::vector<_Tp, _Alloc>::insert(std::vector<_Tp, 
_Alloc>::const_iterator, std::vector<_Tp, _Alloc>::value_type&&) [with _Tp = 
double; _Alloc = std::allocator; std::vector<_Tp, _Alloc>::iterator = 
__gnu_cxx::__normal_iterator >; typename 
std::_Vector_base<_Tp, _Alloc>::pointer = double*; std::vector<_Tp, 
_Alloc>::const_iterator = __gnu_cxx::__normal_iterator >; typename __gnu_cxx::__alloc_traits::_Tp_alloc_type>::const_pointer = const double*; 
std::vector<_Tp, _Alloc>::value_type = double]
   insert(const_iterator __position, value_type&& __x)
   ^
/usr/include/c++/4.9/

Bug#757639: qtwebkit: FTBFS on arm64

[Wookey]

Package: qtwebkit
Version: 2.2.1-7
Severity: serious
Tags: upstream patch
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertag: arm64


qtwebkit does not build on arm64 (which is (just) now in the main
archive). The simple attached patch fixes this issue. It was actually
done a couple of months ago but I apparently failed to file this bug,
mostly because there were two versions upstream and I thought I should
check both out. 

I see there has been an NMU since then. I'll check that this still
works OK with that. Then plan to do an NMU in order to unblock arm64 builds.

Wookey
diff -Nru qtwebkit-2.2.1/debian/changelog qtwebkit-2.2.1/debian/changelog
--- qtwebkit-2.2.1/debian/changelog	2013-11-05 01:15:31.0 +
+++ qtwebkit-2.2.1/debian/changelog	2014-06-08 00:20:13.0 +
@@ -1,3 +1,10 @@
+qtwebkit (2.2.1-7+arm64) unreleased; urgency=low
+
+  * Non-maintainer upload.
+  * Add basic arm64/aarch64 support
+
+ -- Wookey   Sun, 08 Jun 2014 00:19:24 +
+
 qtwebkit (2.2.1-7) unstable; urgency=low
 
   [ Nobuhiro Iwamatsu ]
diff -Nru qtwebkit-2.2.1/debian/patches/arm64-support.diff qtwebkit-2.2.1/debian/patches/arm64-support.diff
--- qtwebkit-2.2.1/debian/patches/arm64-support.diff	1970-01-01 00:00:00.0 +
+++ qtwebkit-2.2.1/debian/patches/arm64-support.diff	2014-06-08 00:41:24.0 +
@@ -0,0 +1,33 @@
+Description: Add arm64/aarch64 support
+ Add basic aarch64 suport
+Author: Wookey 
+Origin: Linaro, https://bugs.launchpad.net/linaro-aarch64/+bug/1096053/+attachment/3482961/+files/aarch64.patch
+Bug: https://bugs.launchpad.net/linaro-aarch64/+bug/1096053
+Last-Update: <2014-06-07
+
+Index: qtwebkit-2.2.1/Source/JavaScriptCore/wtf/Platform.h
+===
+--- qtwebkit-2.2.1.orig/Source/JavaScriptCore/wtf/Platform.h
 qtwebkit-2.2.1/Source/JavaScriptCore/wtf/Platform.h
+@@ -369,6 +369,11 @@
+ #define WTF_CPU_NEEDS_ALIGNED_ACCESS 1
+ #endif
+ 
++/* CPU(AARCH64) - Aarch64 */
++#if defined(__aarch64__)
++#define WTF_CPU_AARCH64 1
++#endif
++
+ /*  OS() - underlying operating system; only to be used for mandated low-level services like 
+virtual memory, not to choose a GUI toolkit  */
+ 
+@@ -998,7 +1003,8 @@
+ || CPU(ALPHA) \
+ || CPU(SPARC64) \
+ || CPU(S390X) \
+-|| CPU(PPC64)
++|| CPU(PPC64) \
++|| CPU(AARCH64)
+ #define WTF_USE_JSVALUE64 1
+ #else
+ #define WTF_USE_JSVALUE32_64 1
diff -Nru qtwebkit-2.2.1/debian/patches/series qtwebkit-2.2.1/debian/patches/series
--- qtwebkit-2.2.1/debian/patches/series	2013-07-24 03:29:27.0 +
+++ qtwebkit-2.2.1/debian/patches/series	2014-06-08 00:38:36.0 +
@@ -18,3 +18,4 @@
 hurd.diff
 webkit_qt_hide_symbols.diff
 ignore-unused-local-typedefs_error.diff
+arm64-support.diff

Bug#756941: gnome-shell: Gnome-Shell 3.13-1 hangs at GDM

[Marc Bonnor]

After installing gnome-shell and gnome-shell-common again and being
presented with the blank screen after reboot I found some errors in the
user.log, see attached text file.

Hope this helps ...


-- 
Regards

Marc
Aug  9 18:41:46 debian gdm-Xorg-:0[1226]: > Warning:  Compat map for group 3 redefined
Aug  9 18:41:46 debian gdm-Xorg-:0[1226]: >   Using new definition
Aug  9 18:41:46 debian gdm-Xorg-:0[1226]: > Warning:  Compat map for group 4 redefined
Aug  9 18:41:46 debian gdm-Xorg-:0[1226]: >   Using new definition
Aug  9 18:41:46 debian gdm-Xorg-:0[1226]: Errors from xkbcomp are not fatal to the X server
Aug  9 18:41:46 debian gdm-Xorg-:0[1226]: resize called 1920 1200
Aug  9 18:41:46 debian gnome-session[1286]: gnome-shell: symbol lookup error: /usr/lib/gnome-shell/libgnome-shell.so: undefined symbol: meta_is_wayland_compositor
Aug  9 18:41:47 debian gnome-session[1286]: (gnome-settings-daemon:1427): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
Aug  9 18:44:01 debian gdm-Xorg-:0[1226]: (II) AIGLX: Suspending AIGLX clients for VT switch
Aug  9 18:44:01 debian gdm-Xorg-:0[1226]: (II) NOUVEAU(0): NVLeaveVT is called.

Processed: fixed 752347 in 3.18-2

[Debian Bug Tracking System]

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

> fixed 752347 3.18-2
Bug #752347 {Done: gregor herrmann } [highlight] highlight: 
hardcodes /usr/lib/perl5
Marked as fixed in versions highlight/3.18-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
752347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752347
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#747270: [Python-modules-team] Bug#747270: Bug#747270: python-librabbitmq

[Brian May]

On 10 August 2014 01:12, Michael Fladischer  wrote:

> You are right. I'm preparing a new kombu upload right now, that will
> have python-librabbitmq (>= 1.5.2) as a Recommends.


[...]


> I also prepared an upload for librabbitmq-0.5.0 which will then close
> this bug. I also tested python-librabbitmq with this release and it
> also worked fine.
>

Great! Thanks for your work.
-- 
Brian May 

Bug#757637: dpkg: Fails to build on non-Linux systems

[Guillem Jover]

Source: dpkg
Source-Version: 1.17.11
Severity: serious

Hi!

Ok so it's failing to build on all non-Linux ports. I've a fix queued
locally, which I'll be pushing tomorrow in case there's anything else
to fix.

Thanks,
Guillem


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

Bug#754787: marked as done (mosquitto: does not handle errors from authentication plugins correctly)

[Debian Bug Tracking System]

Your message dated Sun, 10 Aug 2014 01:33:43 +
with message-id 
and subject line Bug#754787: fixed in mosquitto 1.3.4-1
has caused the Debian Bug report #754787,
regarding mosquitto: does not handle errors from authentication plugins 
correctly
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.)


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

If an end user uses mosquitto with an authentication plugin, and the
plugin returns an application error when making an authentication check
(such as if a database was unavailable), then mosquitto incorrectly
treats this as a successful authentication.

This has the potential for unauthorised clients to access the running
mosquitto broker and gain access to information to which it is not
authorised. In general this does not represent a wider security hole.

No authentication plugins are provided with mosquitto and there are only
a limited number of examples available on the internet, so it is
unlikely that this bug will affect many installations.
--- End Message ---
--- Begin Message ---
Source: mosquitto
Source-Version: 1.3.4-1

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

Debian distribution maintenance software
pp.
Roger A. Light  (supplier of updated mosquitto package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 06 Aug 2014 00:43:39 +0100
Source: mosquitto
Binary: mosquitto libmosquitto1 libmosquitto-dev libmosquittopp1 
libmosquittopp-dev mosquitto-clients python-mosquitto python3-mosquitto 
mosquitto-dbg
Architecture: source amd64 all
Version: 1.3.4-1
Distribution: unstable
Urgency: medium
Maintainer: Roger A. Light 
Changed-By: Roger A. Light 
Description:
 libmosquitto-dev - MQTT version 3.1 client library, development files
 libmosquitto1 - MQTT version 3.1 client library
 libmosquittopp-dev - MQTT version 3.1 client C++ library, development files
 libmosquittopp1 - MQTT version 3.1 client C++ library
 mosquitto  - MQTT version 3.1/3.1.1 compatible message broker
 mosquitto-clients - Mosquitto command line MQTT clients
 mosquitto-dbg - debugging symbols for mosquitto binaries
 python-mosquitto - MQTT version 3.1 Python client library
 python3-mosquitto - MQTT version 3.1 Python 3 client library
Closes: 725014 754787
Changes:
 mosquitto (1.3.4-1) unstable; urgency=medium
 .
   * New upstream release: http://mosquitto.org/2014/08/version-1-3-4-released/
(closes: #725014, #754787)
   * Add dependency on libuuid, c-ares.
   * Bumped standards version to 3.9.5. No changes needed.
   * Example config files are now installed to
 /usr/share/doc/mosquitto/examples/
   * debian/copyright year updated.
   * compiling.txt is no longer distributed.
   * Updated debian/copyright with new dates.
Checksums-Sha1:
 6105efcdcd94505b793ec9a908e67cd29993ea5b 2431 mosquitto_1.3.4-1.dsc
 b818672cc0db723995d7c3201ef6962931dd891a 351761 mosquitto_1.3.4.orig.tar.gz
 7f3ba031ef4e794219bac545bb81c5d36f68bb9b 20048 mosquitto_1.3.4-1.debian.tar.xz
 dc9410f99a6aa06e4c170f35476df1ccc3ad46e0 110292 mosquitto_1.3.4-1_amd64.deb
 7773de44e0ef4422c2a26a001cd2179d9983d5ad 41532 libmosquitto1_1.3.4-1_amd64.deb
 087b79737c72a44e7dcecb8864b9d050ff2c7231 32286 libmosquitto-dev_1.3.4-1_all.deb
 3de18bf2fa690bd2cec6d6f174d285f4c3b5808f 24674 
libmosquittopp1_1.3.4-1_amd64.deb
 5249c7b2d3eedf39ee4eb42d42f38cdb514ed666 20976 
libmosquittopp-dev_1.3.4-1_all.deb
 fc53d6a665a9b7f2af179225e7084a902b644e4a 40856 
mosquitto-clients_1.3.4-1_amd64.deb
 98b7bfd31cbe36fbb2f103f6c54a06e69eaace39 34526 python-mosquitto_1.3.4-1_all.deb
 0598425ddf7d3b0b9b4399f3d536aceefb9d79fd 34616 
python3-mosquitto_1.3.4-1_all.deb
 09d6125c6dbd74b935fd21051056eed4c1a28f50 539484 mosquitto-dbg_1.3.4-1_amd64.deb
Checksums-Sha256:
 1fe9b6b9976cf9e5f7f1ed5902b456b497de7ee32c8e2d74b65b7ca85e05467c 2431 
mosquitto_1.3.4-1.dsc
 0a3982d6b875a458909c882873

Processed: severity of 757543 is normal

[Debian Bug Tracking System]

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

> severity 757543 normal
Bug #757543 [e2fsprogs] MUST NOT say "* REBOOT LINUX *" before safe to 
do so
Bug #757544 [e2fsprogs] Don't say "* FILE SYSTEM WAS MODIFIED *" before 
actually finished modifying!
Severity set to 'normal' from 'grave'
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
757543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757543
757544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757544
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: reopening 754425, found 754425 in 0.4.3-1

[Debian Bug Tracking System]

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

> reopen 754425
Bug #754425 {Done: robe...@connexer.com (Roberto C. Sanchez)} [gpxviewer] 
gpxviewer: incorrect /etc/mailcap entry for application/xml
'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 luabind/0.9.1+dfsg-9.
> found 754425 0.4.3-1
Bug #754425 [gpxviewer] gpxviewer: incorrect /etc/mailcap entry for 
application/xml
Ignoring request to alter found versions of bug #754425 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
754425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754425
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#754425: marked as done (gpxviewer: incorrect /etc/mailcap entry for application/xml)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 23:33:41 +
with message-id 
and subject line Bug#754425: fixed in luabind 0.9.1+dfsg-9
has caused the Debian Bug report #754425,
regarding gpxviewer: incorrect /etc/mailcap entry for application/xml
to be marked as done.

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

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


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

The /etc/mailcap file contains the following entry:

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

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

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

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

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

gpxviewer recommends no packages.

gpxviewer suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: luabind
Source-Version: 0.9.1+dfsg-9

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

Debian distribution maintenance software
pp.
Roberto C. Sanchez  (supplier of updated luabind 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: Sat, 09 Aug 2014 18:58:32 -0400
Source: luabind
Binary: libluabind0.9.1 libluabind-dbg libluabind-dev libluabind-doc 
libluabind-examples
Architecture: source all amd64
Version: 0.9.1+dfsg-9
Distribution: unstable
Urgency: low
Maintainer: Roberto C. Sanchez 
Changed-By: Roberto C. Sanchez 
Description:
 libluabind-dbg - luabind c++ binding for lua: unstripped binaries
 libluabind-dev - luabind c++ binding for lua: static library and headers
 libluabind-doc - luabind c++ binding for lua: documentation files
 libluabind-examples - luabind c++ binding for lua: example files
 libluabind0.9.1 - luabind c++ binding for lua: runtime library
Closes: 754425 757542
Changes:
 luabind (0.9.1+dfsg-9) unstable; urgency=low
 .
   * Change Build-Depends from "libboost1.54-all-dev | libboost1.55-all-dev |
 libboost1.53-dev | libboost1.49-dev" to libboost-all-dev (Closes: #757542)
   * libluabind-dev: Change Depends from "libboost1.53-dev | libboost-dev
 (>= 1.46.1-3~)" to libboost-dev (Closes: #754425)
   * debian/rules: Add build-arch and build-indep targets to the .PHONY target
Checksums-Sha1:
 8fd4f83543f42cb8046bcb8913f058cf5513c752 2224 luabind_0.9.1+dfsg-9.dsc
 49689d39c9fd120b14f7f266d8da7c36688c06a1 13536 
luabind_0.9.1+dfsg-9.debian.tar.xz
 337a4fdf886dcf6b202267921b4341d41fd7f08c 84312 
libluabind-doc_0.9.1+dfsg-9_all.deb
 523ec1ee1d7d04bfa9a55d25e12c25364f8b 15666 
libluabind-examples_0.9.1+dfsg-9_all.deb
 400618c4f032f33dc452c4645799e74ab97650b0 42458 
libluabind0.9.1_0.9.1+dfsg-9_amd64.deb
 52fa1b41944a4feeb05c326a7db6619c61695ecc 728162 
libluabind-dbg_0.9.1+dfsg-9_amd64.deb
 fc53d01d6683882d8dab8ac7d04f65344e0a5a44 93780 
libluabind-dev_0.9.1+dfsg-9_amd64.deb
Checksums-Sha256:
 d3ef053710dd828960556ac3a493df5aa9300f3a2144c1ace61f30c9da327675 2224 
luabind_0.9.1+dfsg-9.dsc
 eadeaf7c834a4b3140958d45d40fa65964754bb90b0f873520216ab5edf4c385 13536 
luabind_0.9.1+dfsg-9.debian.tar.xz
 6821d4ccee77c93e0d3f6d03f8ca4c1a8f7c25056cb06dab3c2e91c4938d5c99 84312 
libluabind-doc_0.9.1+dfsg-9_all.deb
 aa8db81bcf49b5bebec0715e14206c8cbf0cbfb92871bce4df7d2890bbc26dcf 15666 
libluabind-examples_0.9.1+dfsg-9_all.deb
 6f0eaa78b7c37a4cd36a581552cc5776e995e55652237b35f

Processed: tagging 664346

[Debian Bug Tracking System]

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

> tags 664346 + pending
Bug #664346 [havp] [PATCH] havp: Helping to update to packaging format 3.0
Added tag(s) pending.
> tags 689892 + pending
Bug #689892 [havp] Ships a folder in /var/run or /var/lock (Policy Manual 
section 9.3.2)
Added tag(s) pending.
> tags 689778 + pending
Bug #689778 [havp] havp should maintain /var/run/havp in init script and postrm
Added tag(s) pending.
> tags 666016 + pending
Bug #666016 [havp] havp: unowned files after purge (policy 6.8, 10.8)
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
664346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664346
666016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666016
689778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689778
689892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689892
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#757543: MUST NOT say "***** REBOOT LINUX *****" before safe to do so

[積丹尼 Dan Jacobson]

forcemerge 757543 757544
thanks
The main damage appears to be tons of missing .so files!
Good thing I can use dpkg -V !
You probably want to use two messages
BEGINNING TO 
DONE DOING ... YOU MAY NOW SAFELY REMOVE...
Thanks.


-- 
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#757543: MUST NOT say "***** REBOOT LINUX *****" before safe to do so

[Debian Bug Tracking System]

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

> forcemerge 757543 757544
Bug #757543 [e2fsprogs] MUST NOT say "* REBOOT LINUX *" before safe to 
do so
Bug #757544 [e2fsprogs] Don't say "* FILE SYSTEM WAS MODIFIED *" before 
actually finished modifying!
Severity set to 'grave' from 'normal'
Merged 757543 757544
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
757543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757543
757544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757544
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#754850: upower 0.99 drops support for non-systemd

[Andreas Henriksson]

Control: retitle -1 Please support suspend/hibernate on non-systemd systems
Control: severity -1 wishlist

Hello Adam Boroski!

For some reason this bug shows up at the top of my Debian Maintainer
Dashboard even though I'm not involved with XFCE. Anyway, lets take the
chance to deal with the confusion in this bug report.

On Fri, Jul 18, 2014 at 02:39:44AM +0200, Adam Borowski wrote:
[...]
> As upower 0.99 drops support for suspend and hibernate, relying on it to
> provide said support is futile.  If you want to use 0.99, it must be
> provided by some other means, such as calling pm-utils directly.

The above statement contains (technical) inaccuracies, but I'll focus
on the overall wost parts of it.

Your statement makes me feel the need to quote the Debian Constitution:

"Nothing in this constitution imposes an obligation on anyone to do work for
the Project. A person who does not want to do a task which has been delegated
or assigned to them does not need to do it. However, they must not actively
work against these rules and decisions properly made under them."

I hope there's no need for me to paraphrase this You should also go
read the part which lists the rights of a developer.

If the XFCE maintainer feels that only supporting suspend/hibernate
through logind interfaces, then it's up to *you* to work out an
alternative solution that suits *your* needs. There's no must involved
for the maintainer.
Once you've provided a patch the maintainers should (note should, not
must!) consider your suggested solution -- to be in line with the
tech-cttes wishes to support multiple init systems when possible.
(Please note that there are many reasons to reject such a patch, so
don't be surprised if it is. I doubt there are much room for added
maintenance burden on XFCE in Debian and since it seems every project
out there are now standardising on the logind D-Bus abstraction, with
different backends implementations, using another API is probably not
worth investing time in. Instead you should probably focus on
implementing yet another backend if the ones out there doesn't suite
you.)

I also feel the need to add that I'm not aware of any /requirement/ at all
for a desktop environment in debian to support suspend/hibernate in any
form at all. If that was the case, then I bet we'd have a whole bunch of
bug reports to file.

Now that we've cleared up the confusion here, I'm adjusting the title
and severity of this bug report accordingly as you can see above.
(My interpretation was also that the maintainer considered this a
"wontfix", but I've held off on setting the tag for now.)
I'd recommend that you try to set the correct severity from the beginning in
your future feature requests. My experience is that there's a much bigger
chance a solution is actually implemented if you avoid over-inflating the
severity and use the word "please" instead of making demands.


Regards,
Andreas Henriksson


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

Processed: Re: upower 0.99 drops support for non-systemd

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 Please support suspend/hibernate on non-systemd systems
Bug #754850 [xfce4-session] upower: no suspend/hibernate on non-systemd systems
Changed Bug title to 'Please support suspend/hibernate on non-systemd systems' 
from 'upower: no suspend/hibernate on non-systemd systems'
> severity -1 wishlist
Bug #754850 [xfce4-session] Please support suspend/hibernate on non-systemd 
systems
Severity set to 'wishlist' from 'serious'

-- 
754850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754850
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#757621: Octocat Ball is non-free (trademark)

[Calinou]

Package: neverball
Version: 1.6.0-2
Severity: serious

The game includes several balls, which the player can choose from (the 
difference is purely cosmetic, nothing gameplay-related is involved). 
However, 1.6.0 includes a problematic one, the Octocat Ball which is 
likely non-free, since it's a registered trademark of GitHub, Inc 
.


I guess “censoring” (by removing the ball or adding a placeholder 
instead) will work in order to fix that.



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

Bug#757622: libtemplates-parser: FTBFS - unsatisfiable B-D on libxmlada4.4.0-dev

[Niels Thykier]

Source: libtemplates-parser
Version: 11.8.2014-1
Severity: serious


Hi,

The package libxmlada4.4.0-dev is no longer built from libxmlada and
based on the changelog it is not coming back:

"""
   * New upstream release GPL 2014 (between 4.4 and 4.5).
 SO version does not change, but ALI version does. Per Ada policy,
 dev package is renamed and Breaks/Replaces with previous ones
"""

~Niels


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

Bug#757620: gnat-gps: FTBFS - unsatisfiable B-D on libxmlada4.4.0-dev

[Niels Thykier]

Source: gnat-gps
Version: 5.3-2.2
Severity: serious

Hi,

The package libxmlada4.4.0-dev is no longer built from libxmlada and
based on the changelog it is not coming back:

"""
   * New upstream release GPL 2014 (between 4.4 and 4.5).
 SO version does not change, but ALI version does. Per Ada policy,
 dev package is renamed and Breaks/Replaces with previous ones
"""

~Niels


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

Bug#757335: [buildd-tools-devel] Bug#757335: Bug#757335: postgresql-debversion: No package for postgresql 9.4

[Roger Leigh]

On Fri, Aug 08, 2014 at 02:50:01PM +0100, Roger Leigh wrote:
> On Thu, Aug 07, 2014 at 10:13:54PM +0200, Andreas Tille wrote:
> > Hi,
> > 
> > sorry, but the given patch applies to what?  It does not help
> > when trying to apply to `apt-get source postgresql-debversion`
> > and I also tried
> > 
> >   gbp-clone git://git.debian.org/git/buildd-tools/postgresql-debversion
> > 
> > just to realise that this is outdated for years. :-(
> > 
> > Is there any current Git repository where impatient people could just
> > git-buildpackage??
> 
> Hmm, it looks like this might have been reverted back when Alioth got
> restored from backup last year.  I've got a local copy at home; I'll push
> the current state later today.  All the buildd-tools repos are missing
> from the main gitweb page as well.

Actually it was fine, you were just looking on the wrong branch.
master contains the upstream main releases; the debian revisions are
on the debian branch.  Since there were no code changes required to
support new PostgreSQL versions for some time, there hasn't been any
need to make any new upstream release.  We could require extensions
and drop 9.0 support, but there's no pressing need to do so.

I've uploaded a 1.0.7-4 which will support 9.4 (or in fact any
version since this is now generalised).


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linuxhttp://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-GPG Public Key  F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800


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

Bug#753516: marked as done (xscorch: fails to parse its data file)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 21:36:58 +
with message-id 
and subject line Bug#753516: fixed in xscorch 0.2.1-1+nmu1
has caused the Debian Bug report #753516,
regarding xscorch: fails to parse its data 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.)


-- 
753516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xscorch
Version: 0.2.1-1+b1
Severity: grave

Not sure since when it started to fail, but it does not start up at all today:

$ xscorch
XScorch version 0.2.1
Copyright(c) 2000-2004 Justin David Smith
Copyright(c) 2000-2009 Jacob Luna Lundberg
Licensed under the GNU General Public License, version 2
See the Help menu for the license and a list of contributors.
/usr/share/games/xscorch//profiles.def: error: Malformed value for "tetRadius": 
11 13

/usr/share/games/xscorch//profiles.def:9: error: Failed to add variable 
"tetRadius" to block "Standard"(7) (continuable error)
/usr/share/games/xscorch//profiles.def: error: Malformed value for "mob": t  
true

/usr/share/games/xscorch//profiles.def:11: error: Failed to add variable "mob" 
to block "Standard"(7) (continuable error)
/usr/share/games/xscorch//profiles.def: error: Malformed value for "tetRadius": 
11 13

/usr/share/games/xscorch//profiles.def:24: error: Failed to add variable 
"tetRadius" to block "DoubleTrack"(22) (continuable error)
/usr/share/games/xscorch//profiles.def: error: Malformed value for "efiency": 1 
 115

/usr/share/games/xscorch//profiles.def:26: error: Failed to add variable 
"efiency" to block "DoubleTrack"(22) (continuable error)
/usr/share/games/xscorch//profiles.def: error: Malformed value for "hness": 99 
90

/usr/share/games/xscorch//profiles.def:27: error: Failed to add variable 
"hness" to block "DoubleTrack"(22) (continuable error)
/usr/share/games/xscorch//profiles.def: error: Malformed value for "mob": t  
true

/usr/share/games/xscorch//profiles.def:28: error: Failed to add variable "mob" 
to block "DoubleTrack"(22) (continuable error)
/usr/share/games/xscorch//profiles.def: error: Malformed value for "tetRadius": 
11 13

/usr/share/games/xscorch//profiles.def:41: error: Failed to add variable 
"tetRadius" to block "Fortification"(39) (continuable error)
/usr/share/games/xscorch//profiles.def: error: Malformed value for "haess": 1  
125

/usr/share/games/xscorch//profiles.def:43: error: Failed to add variable 
"haess" to block "Fortification"(39) (continuable error)
/usr/share/games/xscorch//profiles.def: error: Malformed value for "mobi":  
falsese

/usr/share/games/xscorch//profiles.def:44: error: Failed to add variable "mobi" 
to block "Fortification"(39) (continuable error)
/usr/share/games/xscorch//profiles.def: warning: "__null" isn't a valid class 
in this context, for variable "Standard".
/usr/share/games/xscorch//profiles.def: warning: "__null" isn't a valid class 
in this context, for variable "DoubleTrack".
/usr/share/games/xscorch//profiles.def: warning: "__null" isn't a valid class 
in this context, for variable "Fortification".
config_new: failed to build tanks_profile, or no tanks in def file.

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

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

Versions of packages xscorch depends on:
ii  libatk1.0-0  2.12.0-1
ii  libc62.19-4
ii  libcairo21.12.16-2
ii  libfontconfig1   2.11.0-5
ii  libfreetype6 2.5.2-1
ii  libgdk-pixbuf2.0-0   2.30.7-1
ii  libglib2.0-0 2.40.0-3
ii  libgtk2.0-0  2.24.24-1
ii  libmikmod3   3.3.6-2
ii  libpango-1.0-0   1.36.3-1
ii  libpangocairo-1.0-0  1.36.3-1
ii  libpangoft2-1.0-01.36.3-1

Versions of packages xscorch recommends:
ii  xfonts-100dpi  1:1.0.3

xscorch suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xscorch
Source-Version: 0.2.1-1+nmu1

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

Debian

Bug#752870: marked as done (xul-ext-nostalgy: Folder selection and preferences broken in icedove 31)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 21:35:41 +
with message-id 
and subject line Bug#752870: fixed in nostalgy 0.2.32+4real-1
has caused the Debian Bug report #752870,
regarding xul-ext-nostalgy: Folder selection and preferences broken in icedove 
31
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.)


-- 
752870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-nostalgy
Version: 0.2.31-1
Severity: important

Dear Maintainer,

since upgrading to icedove 31 in unstable, folder selection 
has stopped to work in nostalgy. I can use the shortcuts, 
and il will actually work, but I don't see a list of candidate
folders in which to select my destination. Which is a bit like 
shooting in the dark when i have several folders with similar 
names :-)

Moreover, the "Keys" tab in the preferences is empty, and the 
preference dialog won't close when I push the "ok" button. I 
have to close the dialog like a normal window, and it does not 
retain any modification that I made.

I have manually downloaded the development version from 
nostalgy's home page, which fixes all problems.

Thanks for your work,
-- 
Rémi


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

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

Versions of packages xul-ext-nostalgy depends on:
ii  icedove  31.0~b1-2

xul-ext-nostalgy recommends no packages.

xul-ext-nostalgy suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nostalgy
Source-Version: 0.2.32+4real-1

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated nostalgy 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: Sat, 09 Aug 2014 15:34:14 -0400
Source: nostalgy
Binary: xul-ext-nostalgy
Architecture: source all
Version: 0.2.32+4real-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: David Prévot 
Description:
 xul-ext-nostalgy - keyboard shortcut extension for Icedove
Closes: 752870
Changes:
 nostalgy (0.2.32+4real-1) unstable; urgency=medium
 .
   * Team upload of the actual 0.2.32 version (the previous upload was
 actually a beta release)
 .
   [ alain.frisch ]
   * Fix for TB 31. (Closes: #752870)
   * Cleanup, restore tab completion.
   * Require TB 31.
 .
   [ David Prévot ]
   * Bump standards version to 3.9.5
Checksums-Sha1:
 c564ca86a7772aec3dc8d6594898684c1ae883d3 2007 nostalgy_0.2.32+4real-1.dsc
 665faa7045946c1753a40552ebccd37b84f160ea 33839 
nostalgy_0.2.32+4real.orig.tar.gz
 218f54b95789852bef8fd102777c0371b9a5bf48 3676 
nostalgy_0.2.32+4real-1.debian.tar.xz
 03f1e32303541239d3d3f80094bd7ca60b27396f 32662 
xul-ext-nostalgy_0.2.32+4real-1_all.deb
Checksums-Sha256:
 6ab1fce0e307ecfa019e66f583f660d9954552248fee5af6c8588a2bde22b0ff 2007 
nostalgy_0.2.32+4real-1.dsc
 0ccf22f61740918da6c99a4ce71bdaf77f10c29860e936397dda68bfee63f669 33839 
nostalgy_0.2.32+4real.orig.tar.gz
 8442d415da6403a48631b387dab85fa5ec4268060ff1b7edb80f80d9b50bc505 3676 
nostalgy_0.2.32+4real-1.debian.tar.xz
 b7e20aa32b07f0723d1940fd600f21080e693d158bc54c70a707be95534e3bd3 32662 
xul-ext-nostalgy_0.2.32+4real-1_all.deb
Files:
 913d6c3b636a4f3304717d3d82a1df7e 32662 mail optional 
xul-ext-nostalgy_0.2.32+4real-1_all.deb
 023813ad3fea32d121dcffdc482fe20e 2007 mail optional nostalgy_0.2.32+4real-1.dsc
 36a642d6d8dbb6c8cee6995b43ad21a9 33839 mail optional 
nostalgy_0.2.32+4real.orig.tar.gz
 9ef650aee64db62d77184e96554d3be4 3676 mail optional 
nostalgy_0.2.32+4real-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJT5ntNAAoJELgqIXr9/gnyH3gP/1EhZR2cpjBfWG21q9BqaUGZ
i09g/+FbcGqeRe286/iAFdbaaKPstMIqWwfBUIx7Ho+WRM6L2yqMmzJvZ4PNrTLc
P4+okPn3aWX6WAw64U15

Bug#755761: gdm3: Unable to start KDE after last gdm3 upgrade

[Andreas Henriksson]

On Sat, Aug 09, 2014 at 10:11:32PM +0200, Andreas Henriksson wrote:
> Hello Tom Maneiro!
> 
> Thanks for your bug report. You probably want to check with the KDE
> people if they have any ideas what kdeinit4 is waiting for.
> If you could rebuild kdelibs-bin with debugging enabled (and no optimization)
> that would probably be able to  give a more informative backtrace.
> (Try: DEB_BUILD_OPTIONS="noopt debug nostrip" dpkg-buildpackage -uc -us)

I was notified that kde4libs has a debug package, so please try
getting a backtrace with the kdelibs5-dbg package installed. That should
hopefully be enough to get us some more information.

Regards,
Andreas Henriksson


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

Bug#747033: offlineimap uses OpenSSL, causing Debian to violate the GPL when distributing it

[Caitlin Matos]

forwarded 747033 https://github.com/OfflineIMAP/offlineimap/issues/104
thanks

On Sun, 04 May 2014 18:01:31 -0400 Simon Fondrie-Teitler 
 wrote:

Package: offlineimap
Version: 6.5.5-0.1
Severity: serious
Justification: 2.3

Dear Maintainer,

offlineimap/imaplib2.py currently uses Python's ssl library, which
pulls in OpenSSL as described here:
https://docs.python.org/2/license.html#openssl

Additionally offlineimap/folder/Maildir.py uses the md5 function from
the ssl library if available, and offlineimap/imaplibutil.py uses the
sha1 function. Both of these also use OpenSSL code.

The GPL and the OpenSSL license are incompatible. See the following
debian-legal thread for more information.
https://lists.debian.org/debian-legal/2002/10/msg00113.html

Regards,
Simon Fondrie-Teitler

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

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

Versions of packages offlineimap depends on:
ii  libjs-sphinxdoc  1.2.2+dfsg-1
ii  python   2.7.5-5

Versions of packages offlineimap recommends:
ii  python-sqlite  1.0.1-11

Versions of packages offlineimap suggests:
pn  doc-base 
pn  python-kerberos  

-- debconf-show failed





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

Processed: Re: offlineimap uses OpenSSL, causing Debian to violate the GPL when distributing it

[Debian Bug Tracking System]

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

> forwarded 747033 https://github.com/OfflineIMAP/offlineimap/issues/104
Bug #747033 [offlineimap] offlineimap uses OpenSSL, causing Debian to violate 
the GPL when distributing it
Set Bug forwarded-to-address to 
'https://github.com/OfflineIMAP/offlineimap/issues/104'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
747033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747033
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#755761: gdm3: Unable to start KDE after last gdm3 upgrade

[Andreas Henriksson]

Hello Tom Maneiro!

Thanks for your bug report. You probably want to check with the KDE
people if they have any ideas what kdeinit4 is waiting for.
If you could rebuild kdelibs-bin with debugging enabled (and no optimization)
that would probably be able to  give a more informative backtrace.
(Try: DEB_BUILD_OPTIONS="noopt debug nostrip" dpkg-buildpackage -uc -us)

Regards,
Andreas Henriksson

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755761


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

Bug#670872: offlineimap: There appears to be a memory leak somewhere

[Guillem Jover]

Hi!

On Sat, 2014-08-09 at 14:54:13 -0400, Caitlin Matos wrote:
> tags 670872 + moreinfo
> thanks

> >> It appears that the longer offlineimap runs and the more folders it
> >> syncs, the more memory it consumes. Before finishing up syncing my
> >> mail (around 70 folders) the process ended up using around 513m VIRT
> >> and 335m RES, which is pretty huge.
> >>
> >> Please let me know how I might help tracking it down, if you need
> >> that, as I'm not really familiar with python.
> >>
> >It grows up to 1G here and doesn't finish the sync before it gets
> >OOM-killed.  This didn't happen before upgrading from 6.3.4-1.

> Can someone verify whether or not this still occurs in 6.5.5-0.1?
> 
> I cannot replicate it, but I do not have so many folders.

Yes, pretty much. Although I've since switched to isync, which while
evaluating, outperformed offlineimap in speed and memory usage. It
halved my sync times to less than 2 minutes, and uses around 8.5 MiB
as baseline per folder, and for me it peaks at 25 MiB for one of my
largest one with 70k mails, after which it goes back to its baseline,
which seems to be what I'd expect from an IMAP syncing program. :)

Thanks,
Guillem


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

Bug#670872: offlineimap: There appears to be a memory leak somewhere

[Caitlin Matos]

tags 670872 + moreinfo
thanks

Can someone verify whether or not this still occurs in 6.5.5-0.1?

I cannot replicate it, but I do not have so many folders.


> Hi!
>
> It appears that the longer offlineimap runs and the more folders it
> syncs, the more memory it consumes. Before finishing up syncing my
> mail (around 70 folders) the process ended up using around 513m VIRT
> and 335m RES, which is pretty huge.
>
> Please let me know how I might help tracking it down, if you need
> that, as I'm not really familiar with python.
>
It grows up to 1G here and doesn't finish the sync before it gets
OOM-killed.  This didn't happen before upgrading from 6.3.4-1.

Cheers,
Julien



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

Bug#757609: libvirtd internal error: Unable to parse /proc/meminfo

[Jamie Heilman]

Package: libvirt-daemon
Version: 1.2.7-6
Severity: grave

The parsing of /proc/meminfo in the latest versions of the libvirt
packages is flawed.  Please remove it until upstream figures out what
they're doing.

There have been reports of the parsing failing when running under Xen,
but it fails in in other scenarios too; In my case Linux 3.16 (I
tested 3.15.8 too) with:

[2]cucamonga<~/>grep -i huge /boot/config-3.1*
/boot/config-3.15.8:CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
/boot/config-3.15.8:CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
/boot/config-3.15.8:CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y
/boot/config-3.15.8:CONFIG_TRANSPARENT_HUGEPAGE=y
/boot/config-3.15.8:CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y
/boot/config-3.15.8:# CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not set
/boot/config-3.15.8:# CONFIG_HUGETLBFS is not set
/boot/config-3.15.8:# CONFIG_HUGETLB_PAGE is not set
/boot/config-3.16.0:CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
/boot/config-3.16.0:CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
/boot/config-3.16.0:CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y
/boot/config-3.16.0:CONFIG_TRANSPARENT_HUGEPAGE=y
/boot/config-3.16.0:CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y
/boot/config-3.16.0:# CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not set
/boot/config-3.16.0:# CONFIG_HUGETLBFS is not set
/boot/config-3.16.0:# CONFIG_HUGETLB_PAGE is not set

In any case, /proc/meminfo does not always have the items libvirtd
assumes it does, and handles that failure poorly.

2014-08-09 18:32:30.722+: 3589: info : libvirt version: 1.2.7, package: 6 
(root 2014-08-08-16:09:22 bogon)
2014-08-09 18:32:30.722+: 3589: error : virAuditOpen:62 : Unable to 
initialize audit layer: Protocol not supported
2014-08-09 18:32:31.720+: 3712: error : virFileGetDefaultHugepageSize:2958 
: internal error: Unable to parse /proc/meminfo
2014-08-09 18:32:31.720+: 3712: error : virStateInitialize:749 : 
Initialization of QEMU state driver failed: internal error: Unable to parse 
/proc/meminfo
2014-08-09 18:32:31.720+: 3712: error : daemonRunStateInit:922 : Driver 
state initialization failed

Reverting to libvirt-bin 1.2.4 allows libvirtd to work again.

-- 
Jamie Heilman http://audible.transient.net/~jamie/


-- 
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#670872: offlineimap: There appears to be a memory leak somewhere

[Debian Bug Tracking System]

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

> tags 670872 + moreinfo
Bug #670872 [offlineimap] offlineimap: There appears to be a memory leak 
somewhere
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
670872: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670872
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#735651: marked as done (dlr-languages: ruby1.8 won't be available on Jessie)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 18:10:06 +
with message-id 
and subject line Bug#757586: Removed package(s) from unstable
has caused the Debian Bug report #735651,
regarding dlr-languages: ruby1.8 won't be available on Jessie
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.)


-- 
735651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dlr-languages
Severity: serious
User: debian-r...@lists.debian.org
Usertags: ruby18-removal

Dear maintainer,

dlr-languages produces one or more binary packages that depends on
ruby1.8, or it uses ruby1.8 to build. ruby1.8 is unmaintainable at
this point, and we can't keep it for Jessie. We plan to request its
removal in 4 weeks.

Recommendations for some common cases:

If your package contains Ruby programs that are hardcoded to use
ruby1.8, you need to port those to a more recent version. Please use
/usr/bin/ruby instead. Please do not change to /usr/bin/ruby1.9.1 

If your package calls `ruby1.8` during build, please make it call
`ruby` instead. If your scripts don't work with a newer Ruby, you
need to port them. Please do not change `ruby1.8` to `ruby1.9.1` as
it will require more work later when we want to get rid of ruby1.9.1
(and we will).

If your packages builds binary extensions for ruby1.8, you need to
remove those. Please consider building binary extensions for all
supported Ruby versions. You can get a list of supported Ruby
versions at runtime by build-depending on gem2deb and running

$ dh_ruby --print-supported

I'm flagging this bug as release critical, since it's impossible to
have ruby1.8 in the next release.

If you need advice on the best way to handle your package, please
feel free to get in touch with debian-r...@lists.debian.org 
--- End Message ---
--- Begin Message ---
Version: 20090805+git.e6b28d27+dfsg-4+rm

Dear submitter,

as the package dlr-languages 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/757586

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#657340: marked as done (src:dlr-languages: FTBFS with Mono 2.10; updated version required)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 18:10:06 +
with message-id 
and subject line Bug#757586: Removed package(s) from unstable
has caused the Debian Bug report #657340,
regarding src:dlr-languages: FTBFS with Mono 2.10; updated version required
to be marked as done.

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

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


-- 
657340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dlr-languages
Version: 20090805+git.e6b28d27+dfsg-4
Severity: serious
User: debian-...@lists.debian.org
Usertags: mono-2.10-transition


This package no longer builds, due to the Mono 2.10 transition.

An updated upstream release is needed.


--- End Message ---
--- Begin Message ---
Version: 20090805+git.e6b28d27+dfsg-4+rm

Dear submitter,

as the package dlr-languages 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/757586

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#735647: marked as done (ironruby-utils: please do not depend on deprecated ruby packages or rubygems)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 18:10:06 +
with message-id 
and subject line Bug#757586: Removed package(s) from unstable
has caused the Debian Bug report #735647,
regarding ironruby-utils: please do not depend on deprecated ruby packages or 
rubygems
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.)


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

Dear Maintainer,

The package ironruby-utils is currently depending on rubygems1.8. However,
this package will soon be removed from the archive because it was only
needed by ruby1.8, which is now obsolete (and will also be removed).

http://bugs.debian.org/735576

Also librack-ruby1.8  has been since wheezy a transitional package.
Please depend on ruby-rack instead.

Cheers,

Cédric


*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

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


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 20090805+git.e6b28d27+dfsg-4+rm

Dear submitter,

as the package dlr-languages 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/757586

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: mercator: diff for NMU version 0.3.2-1.1

[Debian Bug Tracking System]

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

> tags 713344 + patch
Bug #713344 [src:mercator] mercator: FTBFS: dpkg-gensymbols errors
Added tag(s) patch.
> tags 713344 + pending
Bug #713344 [src:mercator] mercator: FTBFS: dpkg-gensymbols errors
Added tag(s) pending.
> tags 734961 + patch
Bug #734961 [src:mercator] mercator: B-D on unavailable package 
libwfmath-1.0-dev
Added tag(s) patch.
> tags 734961 + pending
Bug #734961 [src:mercator] mercator: B-D on unavailable package 
libwfmath-1.0-dev
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
713344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713344
734961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734961
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#713344: mercator: diff for NMU version 0.3.2-1.1

[Tobias Frost]

tags 713344 + patch
tags 713344 + pending
tags 734961 + patch
tags 734961 + pending
thanks

Dear maintainer,

I've prepared an NMU for mercator (versioned as 0.3.2-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

NOTE: This will be done as a source-only upload [1] to ensure that
libwfmath-1.0 is available before building this package (or for an easy
give-back for amd64)

Regards.

-- 
tobi

diff -Nru mercator-0.3.2/debian/changelog mercator-0.3.2/debian/changelog
--- mercator-0.3.2/debian/changelog 2013-06-21 19:21:39.0 +0200
+++ mercator-0.3.2/debian/changelog 2014-08-09 18:46:44.0 +0200
@@ -1,3 +1,13 @@
+mercator (0.3.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix symbol file (Closes: #713344)
+  * To ensure that it will be build against libwfmath-1.0 (NMU pending, must go
+through NEW), this upload will be done as a source-only upload.
+(Closes: #734961)
+
+ -- Tobias Frost   Sat, 09 Aug 2014 16:46:37 +
+
 mercator (0.3.2-1) unstable; urgency=low
 
   * new upstream release
diff -Nru mercator-0.3.2/debian/libmercator-0.3-3.symbols 
mercator-0.3.2/debian/libmercator-0.3-3.symbols
--- mercator-0.3.2/debian/libmercator-0.3-3.symbols 2013-06-21 
19:21:39.0 +0200
+++ mercator-0.3.2/debian/libmercator-0.3-3.symbols 2014-08-09 
18:18:13.0 +0200
@@ -1,10 +1,13 @@
 libmercator-0.3.so.3 libmercator-0.3-3 #MINVER#
- (c++)"ZeroSpiralOrdering::~ZeroSpiralOrdering()@Base" 0.3.0
- (c++)"ZeroSpiralOrdering::operator()(int, int)@Base" 0.3.0
- (optional=inline)_ZN6WFMath7PolygonILi2EED1Ev@Base 0.3.0
- (optional=inline)_ZN6WFMath7PolygonILi2EED2Ev@Base 0.3.0
- (c++)"Mercator::AreaShader::AreaShader(int)@Base" 0.3.0
- (c++)"Mercator::AreaShader::~AreaShader()@Base" 0.3.0
+ _ZN18ZeroSpiralOrderingD0Ev@Base 0.3.0
+ _ZN18ZeroSpiralOrderingD1Ev@Base 0.3.0
+ _ZN18ZeroSpiralOrderingD2Ev@Base 0.3.0
+ _ZN18ZeroSpiralOrderingclEii@Base 0.3.0
+ _ZN8Mercator10AreaShaderC1Ei@Base 0.3.0
+ _ZN8Mercator10AreaShaderC2Ei@Base 0.3.0
+ _ZN8Mercator10AreaShaderD0Ev@Base 0.3.0
+ _ZN8Mercator10AreaShaderD1Ev@Base 0.3.0
+ _ZN8Mercator10AreaShaderD2Ev@Base 0.3.0
  _ZN8Mercator10BandShader16key_lowThresholdE@Base 0.3.0
  _ZN8Mercator10BandShader17key_highThresholdE@Base 0.3.0
  _ZN8Mercator10BandShader20default_lowThresholdE@Base 0.3.0
@@ -29,11 +32,19 @@
  _ZN8Mercator10HighShaderC1Ef@Base 0.3.0
  _ZN8Mercator10HighShaderC2ERKSt3mapISsfSt4lessISsESaISt4pairIKSsfEEE@Base 
0.3.0
  _ZN8Mercator10HighShaderC2Ef@Base 0.3.0
- (c++)"Mercator::HighShader::~HighShader()@Base" 0.3.0
- (c++)"Mercator::TerrainMod::TerrainMod()@Base" 0.3.0
- (c++)"Mercator::TerrainMod::~TerrainMod()@Base" 0.3.0
- (c++)"Mercator::TileShader::TileShader()@Base" 0.3.0
- (c++)"Mercator::TileShader::~TileShader()@Base" 0.3.0
+ _ZN8Mercator10HighShaderD0Ev@Base 0.3.0
+ _ZN8Mercator10HighShaderD1Ev@Base 0.3.0
+ _ZN8Mercator10HighShaderD2Ev@Base 0.3.0
+ _ZN8Mercator10TerrainModC1Ev@Base 0.3.0
+ _ZN8Mercator10TerrainModC2Ev@Base 0.3.0
+ _ZN8Mercator10TerrainModD0Ev@Base 0.3.0
+ _ZN8Mercator10TerrainModD1Ev@Base 0.3.0
+ _ZN8Mercator10TerrainModD2Ev@Base 0.3.0
+ _ZN8Mercator10TileShaderC1Ev@Base 0.3.0
+ _ZN8Mercator10TileShaderC2Ev@Base 0.3.0
+ _ZN8Mercator10TileShaderD0Ev@Base 0.3.0
+ _ZN8Mercator10TileShaderD1Ev@Base 0.3.0
+ _ZN8Mercator10TileShaderD2Ev@Base 0.3.0
  _ZN8Mercator11DepthShader14key_murkyDepthE@Base 0.3.0
  _ZN8Mercator11DepthShader14key_waterLevelE@Base 0.3.0
  _ZN8Mercator11DepthShader18default_murkyDepthE@Base 0.3.0
@@ -311,9 +322,6 @@
  _ZN8Mercator9ShaderKitD0Ev@Base 0.3.0
  _ZN8Mercator9ShaderKitD1Ev@Base 0.3.0
  _ZN8Mercator9ShaderKitD2Ev@Base 0.3.0
- _ZN9RandCache8OrderingD0Ev@Base 0.3.0
- _ZN9RandCache8OrderingD1Ev@Base 0.3.0
- _ZN9RandCache8OrderingD2Ev@Base 0.3.0
  _ZNK8Mercator10AreaShader14checkIntersectERKNS_7SegmentE@Base 0.3.0
  _ZNK8Mercator10AreaShader5shadeERNS_7SurfaceE@Base 0.3.0
  _ZNK8Mercator10AreaShader9shadeAreaERNS_7SurfaceEPKNS_4AreaE@Base 0.3.0
@@ -359,7 +367,7 @@
  _ZNK8Mercator4Area15checkIntersectsERKNS_7SegmentE@Base 0.3.0
  _ZNK8Mercator4Area15updateToSegmentERNS_7SegmentE@Base 0.3.0
  _ZNK8Mercator4Area17removeFromSegmentERNS_7SegmentE@Base 0.3.0
- (regex)"_ZNK8Mercator4Area8containsE(ff|dd)@Base" 0.3.2
+ _ZNK8Mercator4Area8containsEff@Base 0.3.2
  _ZNK8Mercator4Area9setShaderEPKNS_6ShaderE@Base 0.3.0
  _ZNK8Mercator6BufferIfE10getSegmentEv@Base 0.3.0
  _ZNK8Mercator6BufferIfE11getChannelsEv@Base 0.3.0
@@ -386,106 +394,68 @@
  _ZNK8Mercator7Terrain3getEff@Base 0.3.0
  _ZNK8Mercator9LowShader14checkIntersectERKNS_7SegmentE@Base 0.3.0
  _ZNK8Mercator9LowShader5shadeERNS_7SurfaceE@Base 0.3.0
- 
(optional=inline)_ZNKSt8_Rb_treeIiSt4pairIKiPKN8Mercator4AreaEESt10_Select1stIS6_ESt4lessIiESaIS6_EE5countERS1_@Base
 0.3.0
- 
(optional=inline)_ZNKSt8_Rb_treeISsSt4pairIKSsfESt10_Select1stIS2_ESt4lessISsESaIS2_EE4findERS1_@Base
 0.3.0
- (optional=inline)_ZNSt10_List_baseIN8Mercator4EdgeESaIS1_EE8_M_clearEv@Base 
0.3.0
- 

Processed: normal

[Debian Bug Tracking System]

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

> severity 757533 normal
Bug #757533 [src:debian-archive-keyring] debian-archive-keyring: source package 
signed by removed key
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
757533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757533
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: ants: FTFBFS against insighttoolkit 4.6

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 757594
Bug #757595 [src:ants] ants: FTFBFS against insighttoolkit 4.6
757595 was not blocked by any bugs.
757595 was not blocking any bugs.
Added blocking bug(s) of 757595: 757594

-- 
757595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757595
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#757595: ants: FTFBFS against insighttoolkit 4.6

[Sebastian Ramacher]

Source: ants
Version: 2.0.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: block -1 by 757594

After fixing #757594 locally ants still fails to build against
insighttoolkit 4.6:
| cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/Examples && /usr/lib/ccache/c++   
-DITK_IO_FACTORY_REGISTER_MANAGER -Dl_antsApplyTransforms_EXPORTS -g -O2 
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2   -Wall -Wcast-align -Wdisabled-optimization -Wextra 
-Wformat=2 -Winvalid-pch -Wno-format-nonliteral -Wpointer-arith -Wshadow 
-Wunused -Wwrite-strings -funit-at-a-time -Wno-strict-overflow -Wno-deprecated 
-Wno-invalid-offsetof -Woverloaded-virtual -Wstrict-null-sentinel -fPIC   
-Wno-deprecated -fPIC -I/«PKGBUILDDIR»/Examples/. 
-I/«PKGBUILDDIR»/Examples/../Temporary -I/«PKGBUILDDIR»/Examples/../Tensor 
-I/«PKGBUILDDIR»/Examples/../GraphTheory 
-I/«PKGBUILDDIR»/Examples/../ImageSegmentation 
-I/«PKGBUILDDIR»/Examples/../ImageRegistration 
-I/«PKGBUILDDIR»/Examples/../Utilities -I/usr/include/vtk-5.8 
-I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/ITKIOFactoryRegistration 
-I/tmp/buildd/insighttoolkit4-4.6.0/BUILD/Modules/ThirdParty/HDF5/src 
-I/usr/include/dcmtk -I/usr/include/dcmtk/oflog -I/usr/include/dcmtk/ofstd 
-I/usr/include/dcmtk/dcmtls -I/usr/include/dcmtk/dcmsr 
-I/usr/include/dcmtk/dcmsign -I/usr/include/dcmtk/dcmqrdb 
-I/usr/include/dcmtk/dcmpstat -I/usr/include/dcmtk/dcmnet 
-I/usr/include/dcmtk/dcmjpls -I/usr/include/dcmtk/dcmjpeg 
-I/usr/include/dcmtk/dcmimgle -I/usr/include/dcmtk/dcmimage 
-I/usr/include/dcmtk/dcmdata -I/usr/include/dcmtk/config 
-I/usr/include/x86_64-linux-gnu -I/usr/include/gdcm-2.4 -I/usr/include/ITK-4.6  
  -o CMakeFiles/l_antsApplyTransforms.dir/antsApplyTransforms.cxx.o -c 
/«PKGBUILDDIR»/Examples/antsApplyTransforms.cxx
| /«PKGBUILDDIR»/Examples/antsAlignOrigin.cxx:18:51: fatal error: 
itkTransformToDisplacementFieldSource.h: No such file or directory
|  #include "itkTransformToDisplacementFieldSource.h"
|^
| compilation terminated.

The full build log is available at
https://people.debian.org/~sramacher/logs/itk4/ants_2.0.0-2_amd64-20140809-1752.log.
Please take a look.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#752716: ming: hardcodes /usr/lib/perl5

[Stuart Anderson]

On Sat, 9 Aug 2014, gregor herrmann wrote:


On Fri, 08 Aug 2014 21:14:12 +0200, Gabriele Giacone wrote:


Anyway, I'd really appreciate if Stuart, current maintainer, DD and
also upstream developer, jumped into the discussion and upload it
himself but seems quite unresponsive lately.


Ack.


Hi all,
FYI, I've long since left the project that got me into ming, so my 
interest
in it has gone way down. With this in mind, I did move it to the pkg-flash repo
to facilitate others helping out, so I do appreciate the help, and would be glad
to add a DM upload or team upload if there are others out there  with a higher
interest level that want to work on this package.

I'm also one of the the upstream devs for ming, so what I will try to do
this weekend, is to sync these fixed back upstream, then make a new upstream
release there, so that we can reset the package on that.


Stuart

Stuart R. Anderson   ander...@netsweng.com
Network & Software Engineering   http://www.netsweng.com/
1024D/37A79149:  0791 D3B8 9A4C 2CDC A31F
 BD03 0A62 E534 37A7 9149


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

Processed: libinsighttoolkit4-dev: missing libhdf5-dev dependency

[Debian Bug Tracking System]

Processing control commands:

> affects -1 ants plastimatch
Bug #757594 [libinsighttoolkit4-dev] libinsighttoolkit4-dev: missing 
libhdf5-dev dependency
Added indication that 757594 affects ants and plastimatch

-- 
757594: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757594
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#757594: libinsighttoolkit4-dev: missing libhdf5-dev dependency

[Sebastian Ramacher]

Package: libinsighttoolkit4-dev
Version: 4.6.0-1
Severity: serious
Control: affects -1 ants plastimatch

The cmake files provided by libinsighttoolkit4-dev gained references to
/usr/lib//libhdf5.so, but this is not reflected in the
dependencies of libinsighttoolkit4-dev.

Due to the missing libhdf5-dev Depends ants and platimatch fail to build
when rebuilt against 4.6.0-1. ants fails with:

| make[4]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libhdf5.so', 
needed by 'bin/jointfusion'.  Stop

and plastimatch fails with:

| make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libhdf5.so', 
needed by 'landmark_warp'.  Stop.

Please add libhdf5-dev to libinsighttoolkit4-dev's Depends to fix this
issue.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Processed: gurlchecker: diff for NMU version 0.13.1-2.2

[Debian Bug Tracking System]

Processing control commands:

> tags 757394 + pending
Bug #757394 [gurlchecker] gurlchecker: Conflicting b-d: libgnutls-dev <-> 
libgnomevfs2-dev
Added tag(s) pending.

-- 
757394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757394
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#757394: gurlchecker: diff for NMU version 0.13.1-2.2

[Andreas Metzler]

Control: tags 757394 + pending

Dear maintainer,

I've prepared an NMU for gurlchecker (versioned as 0.13.1-2.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

kind regards
Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru gurlchecker-0.13.1/debian/changelog gurlchecker-0.13.1/debian/changelog
--- gurlchecker-0.13.1/debian/changelog	2012-04-17 21:02:47.0 +0200
+++ gurlchecker-0.13.1/debian/changelog	2014-08-07 19:50:16.0 +0200
@@ -1,3 +1,10 @@
+gurlchecker (0.13.1-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild against GnuTLS v3, fixing a FTBFS. Closes: #757394
+
+ -- Andreas Metzler   Thu, 07 Aug 2014 19:49:43 +0200
+
 gurlchecker (0.13.1-2.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru gurlchecker-0.13.1/debian/control gurlchecker-0.13.1/debian/control
--- gurlchecker-0.13.1/debian/control	2011-04-21 20:48:53.0 +0200
+++ gurlchecker-0.13.1/debian/control	2014-08-07 19:39:27.0 +0200
@@ -4,7 +4,7 @@
 Maintainer: Daniel Leidert (dale) 
 Build-Depends: debhelper (>> 7.0.50~), autotools-dev, imagemagick, intltool,
  libcroco3-dev (>> 0.6.0), libglade2-dev, libgnet-dev, libgnomeui-dev,
- libgnutls-dev (>> 1.0), libgtk2.0-dev (>> 2.6), libjson-glib-dev (>> 0.8),
+ libgnutls28-dev, libgtk2.0-dev (>> 2.6), libjson-glib-dev (>> 0.8),
  libsqlite3-dev (>> 3.6), libtidy-dev, libxml2-dev (>> 2.6)
 Standards-Version: 3.9.1
 Homepage: http://gurlchecker.labs.libre-entreprise.org


signature.asc
Description: Digital signature

Bug#757543: MUST NOT say "***** REBOOT LINUX *****" before safe to do so

[Theodore Ts'o]

severity 757543 normal
thanks

I agree this should be fixed, but what e2fsck was doing was at best a
contributory factor.  #1, the user pulled the disk while it was still
being active.  And #2, e2fsck is writing back the updated superblock
and block group descriptors.  If any of these changes had been lost, a
second run of e2fsck should have fixed them.

The fact that the disk did additional damage on a power fail which
caused the data loss is the disk's problem, not e2fsck's.

I'll fix this, but even so, unexpected power lost should have caused
anything other than a need to rerun e2fsck.  I suspect the fault of
the hardware.

- Ted


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

Bug#757589: elastix: FTFBFS against insighttoolkit 4.6

[Sebastian Ramacher]

Source: elastix
Version: 4.7-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

elastix fails to build against insighttoolkit 4.6:
| cd 
/«PKGBUILDDIR»/obj-x86_64-linux-gnu/Components/FixedImagePyramids/FixedRecursivePyramid
 && /usr/lib/ccache/c++   -DELASTIX_USE_OPENMP 
-DITK_IO_FACTORY_REGISTER_MANAGER -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2  
 -fopenmp -O3 -DNDEBUG 
-I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/ITKIOFactoryRegistration 
-I/tmp/buildd/insighttoolkit4-4.6.0/BUILD/Modules/ThirdParty/HDF5/src 
-I/usr/include/dcmtk -I/usr/include/dcmtk/oflog -I/usr/include/dcmtk/ofstd 
-I/usr/include/dcmtk/dcmtls -I/usr/include/dcmtk/dcmsr 
-I/usr/include/dcmtk/dcmsign -I/usr/include/dcmtk/dcmqrdb 
-I/usr/include/dcmtk/dcmpstat -I/usr/include/dcmtk/dcmnet 
-I/usr/include/dcmtk/dcmjpls -I/usr/include/dcmtk/dcmjpeg 
-I/usr/include/dcmtk/dcmimgle -I/usr/include/dcmtk/dcmimage 
-I/usr/include/dcmtk/dcmdata -I/usr/include/dcmtk/config 
-I/usr/include/x86_64-linux-gnu -I/usr/include/gdcm-2.4 -I/usr/include/ITK-4.6 
-I/«PKGBUILDDIR»/src/Common -I/«PKGBUILDDIR»/src/Common/CostFunctions 
-I/«PKGBUILDDIR»/src/Common/CUDA -I/«PKGBUILDDIR»/src/Common/ImageSamplers 
-I/«PKGBUILDDIR»/src/Common/KNN -I/«PKGBUILDDIR»/src/Common/KNN/ann_1.1/include 
-I/«PKGBUILDDIR»/src/Common/LineSearchOptimizers 
-I/«PKGBUILDDIR»/src/Common/ParameterFileParser 
-I/«PKGBUILDDIR»/src/Common/Transforms -I/«PKGBUILDDIR»/src/Common/xout 
-I/«PKGBUILDDIR»/src/Common/MevisDicomTiff -I/«PKGBUILDDIR»/src/Core 
-I/«PKGBUILDDIR»/src/Core/Install -I/«PKGBUILDDIR»/src/Core/Kernel 
-I/«PKGBUILDDIR»/src/Core/ComponentBaseClasses 
-I/«PKGBUILDDIR»/src/Core/Configuration -I/«PKGBUILDDIR»/src/Core/Main 
-I/«PKGBUILDDIR»/src/Components/FixedImagePyramids 
-I/«PKGBUILDDIR»/src/Components/ImageSamplers 
-I/«PKGBUILDDIR»/src/Components/Interpolators 
-I/«PKGBUILDDIR»/src/Components/Metrics 
-I/«PKGBUILDDIR»/src/Components/MovingImagePyramids 
-I/«PKGBUILDDIR»/src/Components/Optimizers 
-I/«PKGBUILDDIR»/src/Components/Registrations 
-I/«PKGBUILDDIR»/src/Components/ResampleInterpolators 
-I/«PKGBUILDDIR»/src/Components/Resamplers 
-I/«PKGBUILDDIR»/src/Components/Transforms 
-I/«PKGBUILDDIR»/obj-x86_64-linux-gnu-o 
CMakeFiles/FixedRecursivePyramid.dir/elxFixedRecursivePyramid.cxx.o -c 
/«PKGBUILDDIR»/src/Components/FixedImagePyramids/FixedRecursivePyramid/elxFixedRecursivePyramid.cxx
| In file included from 
/«PKGBUILDDIR»/src/Core/ComponentBaseClasses/elxTransformBase.h:341:0,
|  from /«PKGBUILDDIR»/src/Core/Kernel/elxElastixTemplate.h:35,
|  from /«PKGBUILDDIR»/src/Core/Install/elxIncludes.h:35,
|  from 
/«PKGBUILDDIR»/src/Components/FixedImagePyramids/FixedRecursivePyramid/elxFixedRecursivePyramid.h:17,
|  from 
/«PKGBUILDDIR»/src/Components/FixedImagePyramids/FixedRecursivePyramid/elxFixedRecursivePyramid.cxx:15:
| /«PKGBUILDDIR»/src/Core/ComponentBaseClasses/elxTransformBase.hxx:25:51: 
fatal error: itkTransformToDisplacementFieldSource.h: No such file or directory
|  #include "itkTransformToDisplacementFieldSource.h"
|^
| compilation terminated.
| make[3]: *** 
[Components/FixedImagePyramids/FixedRecursivePyramid/CMakeFiles/FixedRecursivePyramid.dir/elxFixedRecursivePyramid.cxx.o]
 Error 1

Full build log is available at
https://people.debian.org/~sramacher/logs/itk4/elastix_4.7-2_amd64-20140809-1726.log.
Please take a look.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#753430: marked as done (src:inkscape: needs to adapt for libwpg 0.3 (and librevenge))

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 15:35:29 +
with message-id 
and subject line Bug#753430: fixed in inkscape 0.48.5-2
has caused the Debian Bug report #753430,
regarding src:inkscape: needs to adapt for libwpg 0.3 (and librevenge)
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.)


-- 
753430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: inkscape
Version: 0.48.4-4
Severity: important
Tags: patch

A new upstream libwpg is there and it's now using librevenge as base, so it
changed API and ABI version and it needs some bigger adaptions to the code.

Fortunately the librevenge authors provided patches (or did it themselves,
as for LO) for all known affected applications - this includes inkscape.
(Though I got this specific one from Fedora git[1], as the "general" one
from librevenge upstreams21] seemed to be for some git version)

I attach a full debdiff for reference.

Note that
 a) configure is automatically regenerated and thus a subsequent build fails as 
configure changed. I switched to dh-autoreconf which does do the handling
automatically and should prevent it
 b) the patch needs an update for some new upstream when that happens...
Especially the 0.91 from experimental...

The library is also in experimental to test.

Note that this bug _might_ become serious _before_ the jessie release,  
the transition starts. (LO 4.3 also needs all those new libs and doesn't
support the old ones anymore, and I still hope for it for jessie.)  

The transition is tracked in #753426.

Regards,

Rene
[1]
http://pkgs.fedoraproject.org/cgit/inkscape.git/commit/?id=2aa77aa6cbbde044d027f206e57f0a26a0aba1b8
[2]
#libreoffice-dev.05-27.log:22:16 <@dtardon> _rene_, patches for calligra, 
inkscape and abiword are available at 
http://dtardon.fedorapeople.org/librevenge/0001-switch-to-librevenge-based-import-libs.patch,
 http://people.freedesktop.org/~fridrich/abiword-librevenge.diff and 
http://people.freedesktop.org/~fridrich/inkscape-librevenge.diff
diff -Nru inkscape-0.48.4/debian/changelog inkscape-0.48.4/debian/changelog
--- inkscape-0.48.4/debian/changelog2014-05-27 16:23:42.0 +0200
+++ inkscape-0.48.4/debian/changelog2014-05-31 14:33:58.0 +0200
@@ -1,3 +1,13 @@
+inkscape (0.48.4-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * fix build with libwpg 0.3 (and librevenge) and adapt Build-Depends: -
+patch "stolen" from Fedora
+  * switch to --with=autoreconf instead of --with=autotools-dev to clean up
+changes configure automatically afterwards...
+
+ -- Rene Engelhard   Sat, 31 May 2014 14:30:55 +0200
+
 inkscape (0.48.4-4) unstable; urgency=medium
 
   * debian/: python dependency fixed
diff -Nru inkscape-0.48.4/debian/control inkscape-0.48.4/debian/control
--- inkscape-0.48.4/debian/control  2014-05-27 16:23:42.0 +0200
+++ inkscape-0.48.4/debian/control  2014-05-31 14:34:10.0 +0200
@@ -6,8 +6,8 @@
 Build-Depends:
  autoconf,
  automake,
- autotools-dev,
  debhelper (>= 9),
+ dh-autoreconf,
  intltool,
  libart-2.0-dev (>= 2.3.10),
  libaspell-dev,
@@ -26,10 +26,10 @@
  libpoppler-glib-dev,
  libpoppler-private-dev,
  libpopt-dev,
+ librevenge-dev,
  libsigc++-2.0-dev (>= 2.0.16-2),
  libtool,
- libwpd-dev (>= 0.9.0),
- libwpg-dev (>= 0.2.0),
+ libwpg-dev (>= 0.3.0),
  libxml-parser-perl,
  libxml2-dev (>= 2-2.4.24),
  libxslt1-dev,
diff -Nru inkscape-0.48.4/debian/patches/0006-update-to-new-libwpg.patch 
inkscape-0.48.4/debian/patches/0006-update-to-new-libwpg.patch
--- inkscape-0.48.4/debian/patches/0006-update-to-new-libwpg.patch  
1970-01-01 01:00:00.0 +0100
+++ inkscape-0.48.4/debian/patches/0006-update-to-new-libwpg.patch  
2014-05-31 14:27:01.0 +0200
@@ -0,0 +1,112 @@
+From 12fe3298bcdfe45d74b36f77b8238ebb6937 Mon Sep 17 00:00:00 2001
+From: David Tardon 
+Date: Tue, 27 May 2014 16:47:39 +0200
+Subject: [PATCH] switch to librevenge-based import libs
+
+---
+ configure.ac | 19 ++---
+ src/extension/internal/wpg-input.cpp | 41 
+ 2 files changed, 15 insertions(+), 45 deletions(-)
+
+diff --git a/configure.ac b/configure.ac
+index fcff879..4bce58c 100644
+--- a/configure.ac
 b/configure.ac
+@@ -676,23 +676,8 @@ dnl **
+ 
+ with_libwpg=no
+ 
+-PKG_CHECK_MODULES(LIBWPG01, libwpg-0.1 libwpg-stream-0.1, with_libwpg

Processed: tagging 757588

[Debian Bug Tracking System]

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

> tags 757588 - d-i
Bug #757588 [sysvinit-core] sysvinit-core: installation fails when systemd is 
present
Removed tag(s) d-i.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
757588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757588
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#757588: sysvinit-core: installation fails when systemd is present

[Miguel Filgueiras]

Package: sysvinit-core
Version: 2.88dsf-53.3
Severity: critical
Tags: d-i
Justification: breaks the whole system

A dist-upgrade done last week replaced, without asking, sysvinit by
systemd that I do not want to use. I checked which packages were
available for reinstalling sysvinit and found sysvinit-core.
I installed it (and sysvinit-utils) with apt-get and got an error
because systemd was running. On reboot the system went on single user
because /sbin/init was not available. I tried to run systemd and got
an error message saying that the system was booted by sysvinit.

I recovered from this situation by using a Live CD to copy the
files in the package data.tar to the system disk.

In my opinion there are two problems here:
- the hidden installation of systemd and removal of sysvinit
(I am aware this should be a bug report on systemd...)
- the loose way the sysvinit-core is installed by not taking
heed in an appropriate way of an error that breaks the system,
leaving it with no process launcher.

Best regards,
Miguel Filgueiras

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

Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages sysvinit-core depends on:
ii  debconf [debconf-2.0]  1.5.50
ii  debianutils4.3.4
ii  initscripts2.88dsf-41
ii  libc6  2.17-3
ii  libselinux12.1.13-2
ii  libsepol1  2.1.9-2
ii  sysv-rc2.88dsf-41
ii  sysvinit-utils 2.88dsf-41

sysvinit-core recommends no packages.

sysvinit-core suggests no packages.

-- debconf information excluded


-- 
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#757544: Don't say "***** FILE SYSTEM WAS MODIFIED *****" before actually finished modifying!

[Debian Bug Tracking System]

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

> severity 757544 normal
Bug #757544 [e2fsprogs] Don't say "* FILE SYSTEM WAS MODIFIED *" before 
actually finished modifying!
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
757544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757544
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#748004: Processed: raise severity of issues fo rpackages build-depending on GCC 4.7

[Rene Engelhard]

Hi,


On Sat, Aug 09, 2014 at 01:15:20PM +, Debian Bug Tracking System wrote:
> > severity 748004 serious
> Bug #748004 [libreoffice] libreoffice: non-standard cpp used for build 
> (cpp-4.7)
> Bug #753373 [libreoffice] libreoffice: Please migrate away from gcc-4.7 in 
> Jessie if possible
> Severity set to 'serious' from 'important'
> Severity set to 'serious' from 'important'

I only think it's serious when gcc-4.7 is actually removed (or being that
in short time, but I don't even see a RM: bug).

Anyway, won't argue here.

But the situation hasn't changed. To fix this I need
ucpp (no, I am not going to use the internal version). That one was ITP'ed and
is in NEW now since > 1 month :-(

(The block is already in place since I ITP'ed ucpp.)

Regards,

Rene


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

Bug#747270: [Python-modules-team] Bug#747270: Bug#747270: python-librabbitmq

[Michael Fladischer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Brian May wrote on 2014-08-09 11:52:
> If I install this package and start a celery process, it works.
> 
> If I downgrade python-librabbitmq to the version in unstable, it
> breaks again. So I think the new version may have fixed the
> problem.

Yes, I can confirm this. 1.5.2 seems to have fixed the segfault for
all my Celery instances.

> Oddly enough though, python-kombu still appears to require
> python-amqp to be installed even when using python-librabbitmq, as
> kombu/exceptions.py contains:
> 
> from amqp import ChannelError, ConnectionError, ResourceError
> 
> This cannot be satisfied by python-librabbitmq

You are right. I'm preparing a new kombu upload right now, that will
have python-librabbitmq (>= 1.5.2) as a Recommends.

> I also opened this bug report about librabbitmq-dev being an old
> version in Debian, note though I didn't have to update this to
> solve this segmentation fault.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757553

I also prepared an upload for librabbitmq-0.5.0 which will then close
this bug. I also tested python-librabbitmq with this release and it
also worked fine.

Cheers,
- -- 
Michael Fladischer
Fladi.at
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJT5jpOAAoJEGlMre9Rx7W2kAMP/R5MHZ/BULgdY2UL6DvRu7d8
tDWw1WkubIsx/k6pBVNuYWw0BhL6VbeW1fYnf0eycTzyLjEa7RXnjBP8xXkchCAl
wWx76FeTzVPKrNd9zP+fCFDc/KN528btaY51M2vJQBOrv4HG2DfFbdQHdKnDE9mM
Elva4o2IfkBu3hppDZi6hLWURKL8M55EZe6FlzWAsX0fG/lkyIOrhPQIPz53TlxL
SzVQTHdKIY//SPJR64seiZFJgEPsc1rBtIUW3obPXk4E8mvxhH05huBQqHnNJSTk
9kAPUqi/yG3bOCrKp0Xd3EX6ONlqdwNy5wzgDMFBQhFMdYXLI1n+KSOGqT6qiqiw
4l73EoGRc07lqw6eHQV5K64zHql+wLEzmX66tPWY9t4RkEemO4IbYYeioMkcyyV8
Q08KYgVEYNTQvqzW0rWcmort1x2xevuSF3F6hayjbQsRwgosxqtNYPcqWtZPXjxd
tfJFLcswWdObAz0iR+QpT3uP/nxCxixT3A7ympwSsYs06WiiqUueaURtFDCutLX2
nsfOpb7fn3miHcVnUaPsk/BDFtb4TMEIOm5x503hzdELy4DmsuNUAznGoMx44DLZ
rCTP+bltJ0EIHJ3CmrIpxSPZZowyZ5zO2dCV6Dyz5ccoU/nWqV/8wYHH94LPqIrl
vCkhu5YQt/UaLhhTV5K0
=Ax0k
-END PGP SIGNATURE-


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

Processed: wfmath: diff for NMU version 1.0.2+dfsg1-0.1

[Debian Bug Tracking System]

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

> tags 736315 + patch
Bug #736315 [src:wfmath] wfmath: Please upload version 1.0 to to satisfy other 
packages B-D (and fix their RC bugs)
Added tag(s) patch.
> tags 736315 + pending
Bug #736315 [src:wfmath] wfmath: Please upload version 1.0 to to satisfy other 
packages B-D (and fix their RC bugs)
Added tag(s) pending.
> tags 746920 + pending
Bug #746920 {Done: Matthias Klose } [src:wfmath] wfmath: ftbfs 
with GCC-4.9
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
736315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736315
746920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746920
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#757581: pytables: FTBFS on s390x

[Sebastian Ramacher]

Source: pytables
Version: 3.1.1-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

pytables failed to build on s390x:
| ==
| ERROR: None (tables.tests.test_tables.CompressBloscLZ4TablesTestCase)
| --
| Traceback (most recent call last):
|   File "/«PKGBUILDDIR»/build/lib.linux-s390x-2.7/tables/tests/common.py", 
line 144, in newmethod
| return oldmethod(self, *args, **kwargs)
|   File 
"/«PKGBUILDDIR»/build/lib.linux-s390x-2.7/tables/tests/test_tables.py", line 
494, in test01a_extslice
| rec = result[-1]
| IndexError: list index out of range
|
| ==
| ERROR: None (tables.tests.test_tables.CompressBloscLZ4TablesTestCase)
| --
| Traceback (most recent call last):
|   File "/«PKGBUILDDIR»/build/lib.linux-s390x-2.7/tables/tests/common.py", 
line 144, in newmethod
| return oldmethod(self, *args, **kwargs)
|   File 
"/«PKGBUILDDIR»/build/lib.linux-s390x-2.7/tables/tests/test_tables.py", line 
431, in test01a_fetch_all_fields
| rec = result[-1]
| IndexError: list index out of range
|
| ==
| FAIL: None (tables.tests.test_tables.CompressBloscLZ4TablesTestCase)
| --
| Traceback (most recent call last):
|   File "/«PKGBUILDDIR»/build/lib.linux-s390x-2.7/tables/tests/common.py", 
line 144, in newmethod
| return oldmethod(self, *args, **kwargs)
|   File 
"/«PKGBUILDDIR»/build/lib.linux-s390x-2.7/tables/tests/test_tables.py", line 
399, in test01_readTable
| (b"0001", nrows, b"1"))
| AssertionError: Tuples differ: ('0001', 1684300899, '1') != ('0001', 99, '1')
|
| First differing element 1:
| 1684300899
| 99
|
| - ('0001', 1684300899, '1')
| ?  
|
| + ('0001', 99, '1')
|
| ==
| FAIL: None (tables.tests.test_tables.CompressBloscLZ4TablesTestCase)
| --
| Traceback (most recent call last):
|   File "/«PKGBUILDDIR»/build/lib.linux-s390x-2.7/tables/tests/common.py", 
line 144, in newmethod
| return oldmethod(self, *args, **kwargs)
|   File 
"/«PKGBUILDDIR»/build/lib.linux-s390x-2.7/tables/tests/test_tables.py", line 
475, in test01a_integer
| self.assertEqual(len(result), 20)
| AssertionError: 0 != 20
|
| ==
| FAIL: None (tables.tests.test_tables.CompressBloscLZ4TablesTestCase)
| --
| Traceback (most recent call last):
|   File "/«PKGBUILDDIR»/build/lib.linux-s390x-2.7/tables/tests/common.py", 
line 144, in newmethod
| return oldmethod(self, *args, **kwargs)
|   File 
"/«PKGBUILDDIR»/build/lib.linux-s390x-2.7/tables/tests/test_tables.py", line 
607, in test01b_readTable
| self.assertEqual(rec['var5'], float(nrows - 1))
| AssertionError: -416338112.0 != 99.0
|
| ==
| FAIL: None (tables.tests.test_tables.CompressBloscLZ4TablesTestCase)
| --
| Traceback (most recent call last):
|   File "/«PKGBUILDDIR»/build/lib.linux-s390x-2.7/tables/tests/common.py", 
line 144, in newmethod
| return oldmethod(self, *args, **kwargs)
|   File 
"/«PKGBUILDDIR»/build/lib.linux-s390x-2.7/tables/tests/test_tables.py", line 
655, in test01c_readTable
| self.assertEqual(result, [[0, 0], [0, 1], [1, 0], [1, 1]])
| AssertionError: Lists differ: [] != [[0, 0], [0, 1], [1, 0], [1, 1...
|
| Second list contains 4 additional elements.
| First extra element 0:
| [0, 0]
|
| - []
| + [[0, 0], [0, 1], [1, 0], [1, 1]]
|
| ==
| FAIL: None (tables.tests.test_tables.CompressBloscLZ4TablesTestCase)
| --
| Traceback (most recent call last):
|   File "/«PKGBUILDDIR»/build/lib.linux-s390x-2.7/tables/tests/common.py", 
line 144, in newmethod
| return oldmethod(self, *args, **kwargs)
|   File 
"/«PKGBUILDDIR»/build/lib.linux-s390x-2.7/tables/tests/test_tables.py", line 
676, in test01d_readTable
| self.assertEqual(result, [[0, 0], [0, 1], [1, 0], [1, 1]])
| AssertionError: Lists differ: [] != [[0, 0], [0, 1], [1, 0], [1, 1...
|
| Second list contains 4 additional elements.
| First extra element 0:
| [0, 0]
|
| - []
| + [[0, 0], [0, 1], [1, 0], [1, 1]]
|
| ==
| FAIL: None (tables.tests.test_tables.CompressBloscLZ4TablesTestCase)
| -

Bug#757574: apq: FTBFS almost everywhere

[Adrian-Ken Rueegsegger]

On 08/09/2014 03:44 PM, Sebastian Ramacher wrote:
> apq failed to build almost everywhere: |debian/rules
> override_dh_auto_install | make[1]: Entering directory
> '/«PKGBUILDDIR»' | dh_auto_install | make[2]: Entering directory
> '/«PKGBUILDDIR»' | ./scripts/install.sh | make[2]: Leaving
> directory '/«PKGBUILDDIR»' | rm -f
> debian/tmp/usr/lib/apq-debug/relocatable/libapq.so | chmod 644
> debian/tmp/usr/lib/apq-debug/relocatable/* | chmod 644
> debian/tmp/usr/lib/apq-debug/static/libapq.a | chmod: cannot access
> 'debian/tmp/usr/lib/apq-debug/static/libapq.a': No such file or
> directory | make[1]: *** [override_dh_auto_install] Error 1
> 
> Full build logs are available from 
> https://buildd.debian.org/status/logs.php?pkg=apq&ver=3.2.0-1.1.
> Please take a look.

Thanks for reporting. I plan to fix the NMU and do a proper update of
the APQ package over the weekend.


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

Processed: Re: Processed: your mail

[Debian Bug Tracking System]

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

> found 746952 kfreebsd-8/8.3
Bug #746952 [src:kfreebsd-8] CVE-2014-3000: TCP reassembly vulnerability
The source kfreebsd-8 and version 8.3 do not appear to match any binary packages
Marked as found in versions kfreebsd-8/8.3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
746952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746952
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: your mail

[Debian Bug Tracking System]

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

> tag 747270 + pending
Bug #747270 [python-librabbitmq] segfault in amqp_pool_alloc
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
747270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747270
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#757533: debian-archive-keyring: source package signed by removed key

[Adam D. Barratt]

On 2014-08-09 0:41, Michael Gilbert wrote:

The archive keyring package is currently signed by Philip Kern's old
removed key.


Slightly tangentially, you mean Philipp.

Regards,

Aam


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

Bug#757576: yade: FTBFS on i386 and powerpc

[Sebastian Ramacher]

Source: yade
Version: 1.11.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

yade failed to build on i386 and powerpc due to failures in the test
DEM-PFV-check.py. On i386 it failed with:
| running:  DEM-PFV-check.py
| DEM-PFV: difference in bulk modulus: 247572.019786 vs. target  252759.905803
| DEM-PFV: difference in permeability: 0.0421610459924  vs. target  
0.040399916554
| DEM-PFV: difference in final pressure: 644.825915149  vs. target  
628.314160434
| DEM-PFV: difference in final deformation 0.00255470775947  vs. target  
0.00258113045083
| (INFO) DEM-PFV: More than 60\% of cpu time in FlowEngine ( 71.9831717446 %). 
Should not happen with efficient libraries (check blas/lapack/cholmod 
implementations)
| DEM-PFV: Metis is not used during cholmod's reordering although explicitly 
enabled, something wrong with libraries
| Status: FAILURE!!!

and on powerpc it failed with:
| running:  DEM-PFV-check.py
| DEM-PFV: difference in final pressure: 636.16359666  vs. target  628.314160434
| DEM-PFV: Metis is not used during cholmod's reordering although explicitly 
enabled, something wrong with libraries
| Status: FAILURE!!!

Full build logs are available from
https://buildd.debian.org/status/logs.php?pkg=yade&ver=1.11.0-1. Please
take a look.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#747991: marked as done (ruby-image-science: non-standard gcc/g++ used for build (gcc-4.6))

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 13:50:29 +
with message-id 
and subject line Bug#747991: fixed in ruby-image-science 1.2.2-1.2
has caused the Debian Bug report #747991,
regarding ruby-image-science: non-standard gcc/g++ used for build (gcc-4.6)
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.)


-- 
747991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-image-science
Version: 1.2.2-1.1
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-4.6, gcc-4.6-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-4.9/g++-4.9.

Please drop build dependencies of the form libstdc++6-4.6-dev, these
are not needed and fulfilled by build-essential.

Please keep this report open until the package uses the default
compiler version (or gcc-4.9) for the package build.

The severity of this report is likely to be raised before the release,
so that the gcc-4.6 package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: ruby-image-science
Source-Version: 1.2.2-1.2

We believe that the bug you reported is fixed in the latest version of
ruby-image-science, 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.
Matthias Klose  (supplier of updated ruby-image-science 
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: Sat, 09 Aug 2014 15:29:51 +0200
Source: ruby-image-science
Binary: ruby-image-science
Architecture: source all
Version: 1.2.2-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Matthias Klose 
Description:
 ruby-image-science - Clean Ruby library to provide simple transformations on 
images
Closes: 735724 747991
Changes:
 ruby-image-science (1.2.2-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove the build dependency libstdc++6-4.6-dev. Closes: #747991.
   * Stop building transitional packages. Closes: #735724.
Checksums-Sha1:
 6aa6965bdd0192513145a1b5884f28c7908e165d 1519 ruby-image-science_1.2.2-1.2.dsc
 34dc99181b2a71f9deacad258c7421c368379f01 4596 
ruby-image-science_1.2.2-1.2.debian.tar.xz
 56d3f2dc2eac4cf152de2b0acdf27b574b0a2f90 10640 
ruby-image-science_1.2.2-1.2_all.deb
Checksums-Sha256:
 977cbfbfb5dc5d9ef3cef5e35c622ccec5e6a1195f48d81660fd175864aba309 1519 
ruby-image-science_1.2.2-1.2.dsc
 226a003e33661c80260f3102676a1497a569e3905eea9d85c8d9352001fa2e34 4596 
ruby-image-science_1.2.2-1.2.debian.tar.xz
 9aa2873b3bc7ab332e78617f6953176709fc5744622d167339dfebaf56d9abe0 10640 
ruby-image-science_1.2.2-1.2_all.deb
Files:
 5e94eb232ce1445df16b1aa5da41b35a 10640 ruby optional 
ruby-image-science_1.2.2-1.2_all.deb
 230b6fbf8df7f2005accd7067d26c39d 1519 ruby optional 
ruby-image-science_1.2.2-1.2.dsc
 79a14e1801617a7444e5c1eb5591ff64 4596 ruby optional 
ruby-image-science_1.2.2-1.2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlPmI7kACgkQStlRaw+TLJzZqwCfXJcDTk6utMgwRvWMFQ7yoKFg
KnIAoL/1ZWl+v0Ybgec+muT2CtGsMc0p
=4bN3
-END PGP SIGNATURE End Message ---

Bug#757574: apq: FTBFS almost everywhere

[Sebastian Ramacher]

Source: apq
Version: 3.2.0-1.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

apq failed to build almost everywhere:
|debian/rules override_dh_auto_install
| make[1]: Entering directory '/«PKGBUILDDIR»'
| dh_auto_install
| make[2]: Entering directory '/«PKGBUILDDIR»'
| ./scripts/install.sh
| make[2]: Leaving directory '/«PKGBUILDDIR»'
| rm -f debian/tmp/usr/lib/apq-debug/relocatable/libapq.so
| chmod 644 debian/tmp/usr/lib/apq-debug/relocatable/*
| chmod 644 debian/tmp/usr/lib/apq-debug/static/libapq.a
| chmod: cannot access 'debian/tmp/usr/lib/apq-debug/static/libapq.a': No such 
file or directory
| make[1]: *** [override_dh_auto_install] Error 1

Full build logs are available from
https://buildd.debian.org/status/logs.php?pkg=apq&ver=3.2.0-1.1. Please
take a look.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#757573: texmaker: FTBFS on kfreebsd-*

[Sebastian Ramacher]

Source: texmaker
Version: 4.3-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

texmaker failed to build on kfreebsd-* due to unresolved symbols:
| g++ -Wl,-z,relro -Wl,-rpath-link,/usr/lib/x86_64-kfreebsd-gnu -o texmaker 
.obj/main.o .obj/geticon.o .obj/texmakerapp.o .obj/texmaker.o 
.obj/documentview.o .obj/pageitem.o .obj/presentationview.o .obj/minisplitter.o 
.obj/playerbutton.o .obj/symbollistwidget.o .obj/icondelegate.o 
.obj/latexeditor.o .obj/latexhighlighter.o .obj/latexeditorview.o 
.obj/linenumberwidget.o .obj/lightlatexeditor.o .obj/lightlatexhighlighter.o 
.obj/lightlinenumberwidget.o .obj/sourceview.o .obj/logeditor.o 
.obj/loghighlighter.o .obj/findwidget.o .obj/gotolinewidget.o 
.obj/lightfindwidget.o .obj/lightgotolinewidget.o .obj/replacewidget.o 
.obj/structdialog.o .obj/filechooser.o .obj/graphicfilechooser.o 
.obj/tabbingdialog.o .obj/arraydialog.o .obj/tabdialog.o .obj/letterdialog.o 
.obj/addoptiondialog.o .obj/quickdocumentdialog.o .obj/usermenudialog.o 
.obj/usertooldialog.o .obj/refdialog.o .obj/configdialog.o .obj/aboutdialog.o 
.obj/spellerdialog.o .obj/xmltagslistwidget.o .obj/blockdata.o 
.obj/manhattanstyle.o .obj/stylehelper.o .obj/styleanimator.o 
.obj/keysequencedialog.o .obj/browser.o .obj/pdfviewerwidget.o .obj/pdfviewer.o 
.obj/userquickdialog.o .obj/encodingdialog.o .obj/usercompletiondialog.o 
.obj/texdocdialog.o .obj/scandialog.o .obj/exportdialog.o 
.obj/usertagslistwidget.o .obj/addtagdialog.o .obj/versiondialog.o 
.obj/unicodedialog.o .obj/unicodeview.o .obj/quickbeamerdialog.o 
.obj/affentry.o .obj/affixmgr.o .obj/csutil.o .obj/dictmgr.o .obj/hashmgr.o 
.obj/hunspell.o .obj/phonet.o .obj/suggestmgr.o .obj/filemgr.o .obj/replist.o 
.obj/hunzip.o .obj/qtlocalpeer.o .obj/qtsingleapplication.o 
.obj/qtsinglecoreapplication.o .obj/CharDistribution.o 
.obj/ChineseGroupProber.o .obj/JapaneseGroupProber.o .obj/JpCntx.o 
.obj/LangBulgarianModel.o .obj/LangCyrillicModel.o .obj/LangGreekModel.o 
.obj/LangHebrewModel.o .obj/LangHungarianModel.o .obj/LangThaiModel.o 
.obj/nsBig5Prober.o .obj/nsCharSetProber.o .obj/nsEscCharsetProber.o 
.obj/nsEscSM.o .obj/nsEUCJPProber.o .obj/nsEUCKRProber.o .obj/nsEUCTWProber.o 
.obj/nsGB2312Prober.o .obj/nsHebrewProber.o .obj/nsLatin1Prober.o 
.obj/nsMBCSGroupProber.o .obj/nsMBCSSM.o .obj/nsSBCharSetProber.o 
.obj/nsSBCSGroupProber.o .obj/nsSJISProber.o .obj/nsUniversalDetector.o 
.obj/qencodingprober.o .obj/UnicodeGroupProber.o .obj/x11fontdialog.o 
.obj/qrc_texmaker.o .obj/moc_texmaker.o .obj/moc_documentview.o 
.obj/moc_pageitem.o .obj/moc_presentationview.o .obj/moc_playerbutton.o 
.obj/moc_symbollistwidget.o .obj/moc_icondelegate.o .obj/moc_latexeditor.o 
.obj/moc_latexhighlighter.o .obj/moc_latexeditorview.o 
.obj/moc_linenumberwidget.o .obj/moc_lightlatexeditor.o 
.obj/moc_lightlatexhighlighter.o .obj/moc_lightlinenumberwidget.o 
.obj/moc_sourceview.o .obj/moc_logeditor.o .obj/moc_loghighlighter.o 
.obj/moc_findwidget.o .obj/moc_gotolinewidget.o .obj/moc_lightfindwidget.o 
.obj/moc_lightgotolinewidget.o .obj/moc_replacewidget.o .obj/moc_structdialog.o 
.obj/moc_filechooser.o .obj/moc_graphicfilechooser.o .obj/moc_tabbingdialog.o 
.obj/moc_arraydialog.o .obj/moc_tabdialog.o .obj/moc_letterdialog.o 
.obj/moc_addoptiondialog.o .obj/moc_quickdocumentdialog.o 
.obj/moc_usermenudialog.o .obj/moc_usertooldialog.o .obj/moc_refdialog.o 
.obj/moc_configdialog.o .obj/moc_aboutdialog.o .obj/moc_spellerdialog.o 
.obj/moc_xmltagslistwidget.o .obj/moc_manhattanstyle.o .obj/moc_styleanimator.o 
.obj/moc_keysequencedialog.o .obj/moc_browser.o .obj/moc_pdfviewerwidget.o 
.obj/moc_pdfviewer.o .obj/moc_userquickdialog.o .obj/moc_encodingdialog.o 
.obj/moc_usercompletiondialog.o .obj/moc_texdocdialog.o .obj/moc_scandialog.o 
.obj/moc_exportdialog.o .obj/moc_usertagslistwidget.o .obj/moc_addtagdialog.o 
.obj/moc_versiondialog.o .obj/moc_unicodedialog.o .obj/moc_unicodeview.o 
.obj/moc_quickbeamerdialog.o .obj/moc_qtlocalpeer.o 
.obj/moc_qtsingleapplication.o .obj/moc_qtsinglecoreapplication.o 
.obj/moc_x11fontdialog.o   -lz -lpoppler-qt5 -lsynctex -lQt5WebKitWidgets 
-lQt5Quick -lQt5OpenGL -lQt5PrintSupport -lQt5WebKit -lQt5Qml -lQt5Widgets 
-lQt5Script -lQt5Concurrent -lQt5Network -lQt5Xml -lQt5Gui -lQt5Core -lGL 
-lpthread 
| 
/usr/lib/gcc/x86_64-kfreebsd-gnu/4.9/../../../x86_64-kfreebsd-gnu/libQt5WebKit.so:
 undefined reference to `shm_unlink'
| 
/usr/lib/gcc/x86_64-kfreebsd-gnu/4.9/../../../x86_64-kfreebsd-gnu/libQt5WebKit.so:
 undefined reference to `shm_open'

Full build logs are available from
https://buildd.debian.org/status/logs.php?pkg=texmaker&ver=4.3-1. Please
take a look.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#757572: libinput: Missing copyright information

[Luca Falavigna]

Source: libinput
Version: 0.2.0-2
Severity: serious
Justification: Policy §4.5

Some files have different copyright holders and/or licenses than those listed
in copyright file:
 * doc/html/search/search.js (it als
 * doc/html/jquery.js (also a minified JavaScript library)

Please make sure to add the correct references to all the licenses.

For jquery.js, you could want to create debian/missing-source, and populate it
with the corresponding non-minified version of jquery.js.

Cheers,
Luca



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

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


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

Bug#757571: owfs: FTBFS on kfreebsd-*

[Sebastian Ramacher]

Source: owfs
Version: 2.9p5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

owfs failed to build on kfreebsd-* with symbol errors:
| dh_makeshlibs --no-package libow-php5 --no-package libow-tcl
| dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
| dpkg-gensymbols: warning: debian/libow-2.9-5/DEBIAN/symbols doesn't match 
completely debian/libow-2.9-5.symbols
| --- debian/libow-2.9-5.symbols (libow-2.9-5_2.9p5-1_kfreebsd-amd64)
| +++ dpkg-gensymbolsmVBLFz 2014-08-07 04:19:46.0 +
| @@ -180,7 +180,7 @@
|   DNSServiceRefSockFD@Base 2.8p4
|   DNSServiceRegister@Base 2.8p4
|   DNSServiceResolve@Base 2.8p4
| - DS1410_detect@Base 2.8p4
| +#MISSING: 2.9p5-1# DS1410_detect@Base 2.8p4
|   DS2480_detect@Base 2.8p4
|   DS2480_level_docheck_errors@Base 2.8p4
|   DS2480_read_fd_isset@Base 2.8p4
| Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
| Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
| dh_makeshlibs: failing due to earlier errors
| make[1]: *** [override_dh_makeshlibs] Error 2

Full build logs are available from
https://buildd.debian.org/status/logs.php?pkg=owfs&ver=2.9p5-1. Please
take  look.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#750316: marked as done (galax: FTBFS: make[4]: *** No rule to make target 'clean'. Stop.)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 13:33:55 +
with message-id 
and subject line Bug#750316: fixed in galax 1.1-12
has caused the Debian Bug report #750316,
regarding galax: FTBFS: make[4]: *** No rule to make target 'clean'.  Stop.
to be marked as done.

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

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


-- 
750316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: galax
Version: 1.1-11
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140601 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[4]: Entering directory '/«PKGBUILDDIR»/examples/docs'
> ../../config/Makefile.galax:1072: ../../config/Makefile.conf: No such file or 
> directory
> 
> You must run the Configure script before attempting to build Galax!
>   e.g. ../../Configure
> 
> Read the INSTALL file for more details!
> 
> make[4]: Nothing to be done for 'clean'.
> make[4]: Leaving directory '/«PKGBUILDDIR»/examples/docs'
> make[4]: Entering directory '/«PKGBUILDDIR»/examples/extensions'
> make[4]: *** No rule to make target 'clean'.  Stop.
> make[4]: Leaving directory '/«PKGBUILDDIR»/examples/extensions'
> make[3]: *** [clean] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/06/01/galax_1.1-11_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: galax
Source-Version: 1.1-12

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

Debian distribution maintenance software
pp.
Mehdi Dogguy  (supplier of updated galax 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: Sat, 09 Aug 2014 14:29:25 +0200
Source: galax
Binary: galax galax-extra galaxd libgalax-ocaml-dev galax-doc
Architecture: source amd64 all
Version: 1.1-12
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Mehdi Dogguy 
Description:
 galax  - XQuery implementation with static typing - command line front-end
 galax-doc  - XQuery implementation with static typing - documentation
 galax-extra - XQuery implementation with static typing - utilities
 galaxd - XQuery implementation with static typing - network servers
 libgalax-ocaml-dev - XQuery implementation with static typing - OCaml libraries
Closes: 750316
Changes:
 galax (1.1-12) unstable; urgency=medium
 .
   * Team upload.
   * Fix space/tab issues in some Makefiles.
   * Generate a dummy Makefile.conf so that "make clean" doesn't fail.
 (Closes: #750316).
Checksums-Sha1:
 f8c0b9823ececa9df1da5d80e0223da876373e87 2284 galax_1.1-12.dsc
 7b1acc3a6dbd41fce0bc44197b4b914f4eec951d 17400 galax_1.1-12.debian.tar.xz
 b798e943a033b97b39494adc683bc8ff8320767a 4622814 galax_1.1-12_amd64.deb
 e6982438746a6a177599a7b9c9e2be0130a76feb 17891912 galax-extra_1.1-12_amd64.deb
 d9198b36ce41c6ba1528d958c0fe14f33a82b4b7 6865184 galaxd_1.1-12_amd64.deb
 9824dfa9c6a48856b85cad8626249e3ff230f75c 2647692 
libgalax-ocaml-dev_1.1-12_amd64.deb
 285d95c0cd216b7e2403aba70e2377d11ca1226b 949370 galax-doc_1.1-12_all.deb
Checksums-Sha256:
 8f9666498e061f463a92cd5b6a991e9374e565679f1bc403a70e1a63d4e8 2284 
galax_1.1-12.dsc
 7752e07a41e7237bfbdb9187a823665fca409045652bb3719a88afe1867f14ad 17400 
galax_1.1-12.debian.tar.xz
 23a2ddffa76e1917b56f916e62b333989109c64f72f0581e64f17e72ef872c95 4622814 
galax_1.1-12_amd64.deb
 49b485bb56b97caf749691f3afba13858ac403d9e9994a32792d9ed36008d6d4 17891912 
galax-extra_1.1-12_amd64.deb
 7c107f68c2983fb10a59d40bcb0668d0528a131029d0117d67c32936e12177c1 6865184 
galaxd_1.1-12_amd64.deb
 b022a92e810d313ab90145ff

Bug#751304: marked as done (contextfree: non-standard gcc/g++ used for build (gcc-4.8))

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 13:33:26 +
with message-id 
and subject line Bug#751304: fixed in contextfree 3.0.5+dfsg1-2.2
has caused the Debian Bug report #751304,
regarding contextfree: non-standard gcc/g++ used for build (gcc-4.8)
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.)


-- 
751304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: contextfree
Version: 3.0.5+dfsg1-2.1
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-4.7, gcc-4.7-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-4.9/g++-4.9.

Please drop build dependencies of the form libstdc++6-4.7-dev, these
are not needed and fulfilled by build-essential.

Please keep this report open until the package uses the default
compiler version (or gcc-4.9) for the package build.

The severity of this report is likely to be raised before the release,
so that the gcc-4.7 package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: contextfree
Source-Version: 3.0.5+dfsg1-2.2

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated contextfree 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: Sat, 09 Aug 2014 14:31:18 +0200
Source: contextfree
Binary: contextfree
Architecture: source i386
Version: 3.0.5+dfsg1-2.2
Distribution: unstable
Urgency: medium
Maintainer: Bram Senders 
Changed-By: Matthias Klose 
Description:
 contextfree - image generator based on context-free grammars
Closes: 751304
Changes:
 contextfree (3.0.5+dfsg1-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using the default GCC. Closes: #751304.
Checksums-Sha1:
 80984ddb79043f6c21c6ef9e97b8e3ea37ed7d27 1193 contextfree_3.0.5+dfsg1-2.2.dsc
 97259ef1ad466f928a85ee9d58cf3822f3f0758c 7832 
contextfree_3.0.5+dfsg1-2.2.debian.tar.xz
 2e352343c5b42a2e3e98a3b7d06444760bcde006 256888 
contextfree_3.0.5+dfsg1-2.2_i386.deb
Checksums-Sha256:
 cb50f1be1d1d7373b8db12579dd455ba957c59874bc1e4cb19810a39c88f074b 1193 
contextfree_3.0.5+dfsg1-2.2.dsc
 710217ebc691b5710dbe4dcea8afdbcbf052dea2c3e92e08d7146ac12155b6d7 7832 
contextfree_3.0.5+dfsg1-2.2.debian.tar.xz
 36e62b6eacab142fbab8587908a0e6bac86aaebfd576f457332c4beef459ccc4 256888 
contextfree_3.0.5+dfsg1-2.2_i386.deb
Files:
 248580ed091a2089c9080ae008c235c7 256888 graphics extra 
contextfree_3.0.5+dfsg1-2.2_i386.deb
 3e526ea85f9d89ed1ef37435fbe207d3 1193 graphics extra 
contextfree_3.0.5+dfsg1-2.2.dsc
 559f6e4959ce82e8296fe68324fc849f 7832 graphics extra 
contextfree_3.0.5+dfsg1-2.2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlPmIRUACgkQStlRaw+TLJzwNwCgwtejydFwHU6y0ql4iYWi3V2E
LCoAn1PM16BOoHAnkNcrwc2keJ9Kz9GK
=jexD
-END PGP SIGNATURE End Message ---

Bug#752811: marked as done (redhat-cluster: hardcodes /usr/lib/perl5)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 13:19:30 +
with message-id 
and subject line Bug#752811: fixed in redhat-cluster 3.1.8-1.2
has caused the Debian Bug report #752811,
regarding redhat-cluster: hardcodes /usr/lib/perl5
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.)


-- 
752811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: redhat-cluster
Version: 3.1.8-1.1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition

Starting with version 5.20.0 (currently in experimental), the Debian
perl package is changing the "vendorarch" library paths (currently
/usr/lib/perl5) to include the multiarch triplet and the perl version. See
#748380 for details.

For this to work, packages containing binary perl modules need to migrate
from using the hardcoded /usr/lib/perl5 directory to the value of the
$Config{vendorarch} variable, as defined in the 'Config' module.

This package fails to build with perl_5.20.0-1 from experimental:

  dh_install --sourcedir=debian/tmp --list-missing
  cp: cannot stat 'debian/tmp/usr/lib/perl5/auto/Cluster/CCS/CCS.so': No such 
file or directory
  dh_install: cp -a debian/tmp/usr/lib/perl5/auto/Cluster/CCS/CCS.so 
debian/libccs-perl//usr/lib/perl5/auto/Cluster/CCS/ returned exit code 1
  make[1]: *** [override_dh_install] Error 2
  debian/rules:29: recipe for target 'override_dh_install' failed
  make[1]: Leaving directory '/«PKGBUILDDIR»'
  make: *** [binary-arch] Error 2

One solution for this might be an executable debhelper install file
(available with debhelper compat level 9) expanding $Config{vendorarch}.
See #751924 for an example of this.

Please ask on the debian-perl list if you want help with this, and see
 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.20-transition;users=debian-p...@lists.debian.org
for a list of similar bugs and patches.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: redhat-cluster
Source-Version: 3.1.8-1.2

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated redhat-cluster package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Aug 2014 12:34:59 +
Source: redhat-cluster
Binary: redhat-cluster-suite cman liblogthread3 liblogthread-dev libccs3 
libccs-dev libccs-perl libcman3 libcman-dev libdlm3 libdlm-dev libdlmcontrol3 
libdlmcontrol-dev libfence4 libfence-dev rgmanager
Architecture: source all amd64
Version: 3.1.8-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Damyan Ivanov 
Description:
 cman   - Red Hat cluster suite - cluster manager
 libccs-dev - Red Hat cluster suite - cluster manager development files
 libccs-perl - Red Hat cluster suite - cluster configuration module
 libccs3- Red Hat cluster suite - cluster configuration libraries
 libcman-dev - Red Hat cluster suite - cluster manager development files
 libcman3   - Red Hat cluster suite - cluster manager libraries
 libdlm-dev - Red Hat cluster suite - distributed lock manager development file
 libdlm3- Red Hat cluster suite - distributed lock manager library
 libdlmcontrol-dev - Red Hat cluster suite - distributed lock manager 
development file
 libdlmcontrol3 - Red Hat cluster suite - distributed lock manager library
 libfence-dev - Red Hat cluster suite - fence server development files
 libfence4  - Red Hat cluster suite - fence client library
 liblogthread-dev - Red Hat cluster suite - cluster logging development files
 liblogthread3 - Red Hat cluster suite - cluster logging libraries
 redhat-cluster-suite - Red Hat cluster suite - metapackage
 rgmanager  - Red Hat cluster suite - clustered resource group manager
Closes: 752811
Changes:
 redhat-cluster (3.1.8-1.2) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * Non-maintainer upload.
   * Fix "hardcodes /usr/lib/perl5":
 make debian/libccs-perl.install 

Bug#751331: marked as done (spek: non-standard gcc/g++ used for build (gcc-4.8))

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 13:19:36 +
with message-id 
and subject line Bug#751331: fixed in spek 0.8.2-3.2
has caused the Debian Bug report #751331,
regarding spek: non-standard gcc/g++ used for build (gcc-4.8)
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.)


-- 
751331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spek
Version: 0.8.2-3.1
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-4.7, gcc-4.7-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-4.9/g++-4.9.

Please drop build dependencies of the form libstdc++6-4.7-dev, these
are not needed and fulfilled by build-essential.

Please keep this report open until the package uses the default
compiler version (or gcc-4.9) for the package build.

The severity of this report is likely to be raised before the release,
so that the gcc-4.7 package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: spek
Source-Version: 0.8.2-3.2

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated spek 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: Sat, 09 Aug 2014 15:04:29 +0200
Source: spek
Binary: spek
Architecture: source i386
Version: 0.8.2-3.2
Distribution: unstable
Urgency: medium
Maintainer: Alexander Kojevnikov 
Changed-By: Matthias Klose 
Description:
 spek   - acoustic spectrum analyser
Closes: 751331
Changes:
 spek (0.8.2-3.2) unstable; urgency=medium
 .
   * Build using the default GCC. Closes: #751331.
Checksums-Sha1:
 6ecb5956634326b782b6f4e181cebdc0125dee99 1264 spek_0.8.2-3.2.dsc
 269b2a5ecb8910e391dc746100fe654cbb22047a 4172 spek_0.8.2-3.2.debian.tar.xz
 1474a70cb69b444aea44d9d127c02e98be3fa1fe 92232 spek_0.8.2-3.2_i386.deb
Checksums-Sha256:
 19fdfb696e4ee31ea61bcf80efb7da8a2aed675decad99ac689951a5c6eacdbc 1264 
spek_0.8.2-3.2.dsc
 f93848b9bbcccd31225cae2f21b9b0bc2bec01ec52f6766e194e4d1e491d6788 4172 
spek_0.8.2-3.2.debian.tar.xz
 34ed8dd352c1cfb41c6bb40cf26158a28198565de03abca78ab4e2b648c29f4b 92232 
spek_0.8.2-3.2_i386.deb
Files:
 e14f9a5f3acf27aa9a367740f74b3078 92232 sound optional spek_0.8.2-3.2_i386.deb
 893027b9fcfe1516283fedda929000f4 1264 sound optional spek_0.8.2-3.2.dsc
 0c5744b9e0cdeab6a9f7d444a60803a8 4172 sound optional 
spek_0.8.2-3.2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlPmHVEACgkQStlRaw+TLJxJ/QCeIG7+bwlZETf9b25VlBED5fPu
UVEAnRBqnSKwJbvVpsaWX6IEZi/elKT6
=bqXS
-END PGP SIGNATURE End Message ---

Bug#751318: marked as done (libvpx: non-standard gcc/g++ used for build (gcc-4.8))

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 13:18:41 +
with message-id 
and subject line Bug#751318: fixed in libvpx 1.3.0-2.1
has caused the Debian Bug report #751318,
regarding libvpx: non-standard gcc/g++ used for build (gcc-4.8)
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.)


-- 
751318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvpx
Version: 1.3.0-2
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-4.7, gcc-4.7-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-4.9/g++-4.9.

Please drop build dependencies of the form libstdc++6-4.7-dev, these
are not needed and fulfilled by build-essential.

Please keep this report open until the package uses the default
compiler version (or gcc-4.9) for the package build.

The severity of this report is likely to be raised before the release,
so that the gcc-4.7 package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: libvpx
Source-Version: 1.3.0-2.1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libvpx 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: Sat, 09 Aug 2014 14:38:23 +0200
Source: libvpx
Binary: libvpx-dev libvpx1 libvpx1-dbg libvpx-doc vpx-tools
Architecture: source all i386
Version: 1.3.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Dröge 
Changed-By: Matthias Klose 
Description:
 libvpx-dev - VP8 video codec (development files)
 libvpx-doc - VP8 video codec (API documentation)
 libvpx1- VP8 video codec (shared library)
 libvpx1-dbg - VP8 video codec (debugging symbols)
 vpx-tools  - VP8 video codec encoding/decoding tools
Closes: 674570 726485 751318
Changes:
 libvpx (1.3.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using the default GCC. Closes: #751318.
   * Move doxygen and php5-cli to B-D-I (Peter Pentchev). Closes: #726485.
   * Build using hardening defaults. Closes: #674570.
   * Apply bug fix for ssse3 quantize function.
Checksums-Sha1:
 699f30e1ff0f3c19413e9b938e8cf4ec8af55494 1367 libvpx_1.3.0-2.1.dsc
 99be6d514046d363a9a4e7865e545b2671a18bf6 10712 libvpx_1.3.0-2.1.debian.tar.xz
 26d5a8df5327d9b9a4e873cf06fc00b005a1e10f 192332 libvpx-doc_1.3.0-2.1_all.deb
 d8a0157953f4cf47ac5d73f76321f2dd6d1663b8 647028 libvpx-dev_1.3.0-2.1_i386.deb
 a509b59c291b1efe089a11a6702c7fa898109d34 550562 libvpx1_1.3.0-2.1_i386.deb
 46da894764d9e00a3b9109765cb44f59d5ce811d 1319558 libvpx1-dbg_1.3.0-2.1_i386.deb
 5a2aff0547fa8e570cb5a168ddf97ba01339e1d7 81254 vpx-tools_1.3.0-2.1_i386.deb
Checksums-Sha256:
 e4b3503e00d0b69e7f7dc8efba131f5b7bd44e774a93299ad1889daab1ba70e6 1367 
libvpx_1.3.0-2.1.dsc
 2909b551335f91db416b3818be8c6a31f9472547058cc3ee9bbab7a83dc32c52 10712 
libvpx_1.3.0-2.1.debian.tar.xz
 0e01c5e6626bcf68d73f65bbe5fe1f8381b64a3b4774b29b0eb538e60e4f7c1f 192332 
libvpx-doc_1.3.0-2.1_all.deb
 dcf6f1d8c02f51a8ae09c41c926c8c9d6b806163a05374f35909901cce926610 647028 
libvpx-dev_1.3.0-2.1_i386.deb
 8aa5acfd8014d6557d7c59965e05cff70c6886cb80429faa1ffa44d0523b2a7d 550562 
libvpx1_1.3.0-2.1_i386.deb
 c0537a4434264ce6f3bea31104e71df5d3ecf225d373a347db54049703b79c70 1319558 
libvpx1-dbg_1.3.0-2.1_i386.deb
 b0cc59318bbd272ad4bf85c14b26e05c9f2b8b38de5ebdced1ffb456611f5cec 81254 
vpx-tools_1.3.0-2.1_i386.deb
Files:
 eb5d2e6dd46b72e08a104da382ca6f2f 192332 doc optional 
libvpx-doc_1.3.0-2.1_all.deb
 37b09c724e0667377bca57ef511759c5 647028 libdevel optional 
libvpx-dev_1.3.0-2.1_i386.deb
 e576382d12c9e301b6fa328b78e2cba1 550562 libs optional 
libvpx1_1.3.0-2.1_i386.deb
 569a78c07a7cc4167d5f288a8e5f5e61 1319558 debug extra 
libvpx1-dbg_1.3.0-2.1_i386.deb
 5b93f0a4e8a7e19ccd9ff1ef868a167b 81254 utils optional 
vpx-tools_1.3.0-2.1_i386.deb
 2415fd843b2a8e9595e183a937e63ded 1367 video optio

Processed: raise severity of issues for packages build-depending on GCC 4.6

[Debian Bug Tracking System]

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

> severity 747980 serious
Bug #747980 [estic] estic: non-standard gcc/g++ used for build (gcc-4.6)
Severity set to 'serious' from 'important'
> severity 747990 serious
Bug #747990 [gnat-4.6] gnat-4.6: non-standard gcc/g++ used for build (gcc-4.6)
Severity set to 'serious' from 'important'
> severity 747991 serious
Bug #747991 [ruby-image-science] ruby-image-science: non-standard gcc/g++ used 
for build (gcc-4.6)
Severity set to 'serious' from 'important'
> severity 747992 serious
Bug #747992 [rubyluabridge] rubyluabridge: non-standard gcc/g++ used for build 
(gcc-4.6)
Severity set to 'serious' from 'important'
> severity 747993 serious
Bug #747993 [xorp] xorp: non-standard gcc/g++ used for build (gcc-4.6)
Severity set to 'serious' from 'important'
> severity 747983 serious
Bug #747983 [kfreebsd-9] kfreebsd-9: non-standard gcc/g++ used for build 
(gcc-4.6)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
747980: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747980
747983: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747983
747990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747990
747991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747991
747992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747992
747993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747993
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#752716: marked as done (ming: hardcodes /usr/lib/perl5)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 13:19:00 +
with message-id 
and subject line Bug#752716: fixed in ming 1:0.4.5-1.2
has caused the Debian Bug report #752716,
regarding ming: hardcodes /usr/lib/perl5
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.)


-- 
752716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ming
Version: 1:0.4.5-1.1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition

Starting with version 5.20.0 (currently in experimental), the Debian
perl package is changing the "vendorarch" library paths (currently
/usr/lib/perl5) to include the multiarch triplet and the perl version. See
#748380 for details.

For this to work, packages containing binary perl modules need to migrate
from using the hardcoded /usr/lib/perl5 directory to the value of the
$Config{vendorarch} variable, as defined in the 'Config' module.

This package fails to build with perl_5.20.0-1 from experimental:

  chrpath -d debian/tmp/usr/lib/perl5/auto/SWF/SWF.so
  open: No such file or directory
  elf_open: Invalid argument
  make: *** [install] Error 1
  debian/rules:119: recipe for target 'install' failed

I see debian/libswf-perl.install also hardcodes /usr/lib/perl5.
One solution for that one might be an executable debhelper install file
(available with debhelper compat level 9) expanding $Config{vendorarch}.
See #751924 for an example of this.

Please ask on the debian-perl list if you want help with this, and see
 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.20-transition;users=debian-p...@lists.debian.org
for a list of similar bugs and patches.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: ming
Source-Version: 1:0.4.5-1.2

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Aug 2014 14:59:22 +0200
Source: ming
Binary: libming1 libming-dev ming-fonts-dejavu ming-fonts-opensymbol 
libswf-perl libming-util python-ming php5-ming
Architecture: source all amd64
Version: 1:0.4.5-1.2
Distribution: unstable
Urgency: medium
Maintainer: Stuart R. Anderson 
Changed-By: gregor herrmann 
Description:
 libming-dev - Library to generate SWF (Flash) Files (development files)
 libming-util - Library to generate SWF (Flash) Files - Utilities
 libming1   - Library to generate SWF (Flash) Files
 libswf-perl - Ming (SWF) module for Perl
 ming-fonts-dejavu - Ming format DejaVue Fonts
 ming-fonts-opensymbol - Ming format Opensymbol Fonts
 php5-ming  - Ming module for php5
 python-ming - Ming (SWF) module for Python
Closes: 752716
Changes:
 ming (1:0.4.5-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload with team member's permission.
 .
   [ Gabriele Giacone ]
   * Do not hardcode /usr/lib/perl5 in d/rules and d/*.install (Closes: 
#752716).
Checksums-Sha1:
 2ee292ff383b585e575d262a372cfe9478991325 2436 ming_0.4.5-1.2.dsc
 6951e3c2783867ab1d7c6a9973e49ee773752fb0 20718 ming_0.4.5-1.2.diff.gz
 bd77eadc11e051998167d90cae37e0940d170cc1 149336 
ming-fonts-dejavu_0.4.5-1.2_all.deb
 05c38e3ec03fac85509fcdc0a67d8b8cb04ffba5 120556 
ming-fonts-opensymbol_0.4.5-1.2_all.deb
Checksums-Sha256:
 cadb46f734897bf6a677b796774f02756a24b16e1d5401e670ce85e8eca7dae9 2436 
ming_0.4.5-1.2.dsc
 dcb86e560f72cd109cab1c0e0a0e64513e958f36bb7ea464b862b6e3d743eb75 20718 
ming_0.4.5-1.2.diff.gz
 ebd536fc884ff41a16e2e5fc5b239854ef7f30506c2042eba728598af777df82 149336 
ming-fonts-dejavu_0.4.5-1.2_all.deb
 3cd3b5c1331233abe42c870863fd36f7494dc822d7d8849a169e1c91acf8ce0d 120556 
ming-fonts-opensymbol_0.4.5-1.2_all.deb
Files:
 da43bff5a4a07f11d375428a475652e5 149336 web optional 
ming-fonts-dejavu_0.4.5-1.2_all.deb
 e060063607eaea44e5a58f99aba6e6da 120556 web optional 
ming-fonts-opensymbol_0.4.5-1.2_all.deb
 e7d4c5e8c7fb473ecb8e229c99abbcb0 2436 libs optional ming_0.4.5-1.2.dsc
 ae154ae37

Bug#752716: ming: hardcodes /usr/lib/perl5

[gregor herrmann]

On Fri, 08 Aug 2014 21:14:12 +0200, Gabriele Giacone wrote:

> Anyway, I'd really appreciate if Stuart, current maintainer, DD and
> also upstream developer, jumped into the discussion and upload it
> himself but seems quite unresponsive lately.

Ack.

> explains why I'm treating it as a team maintained package.
> If that's not enough, no problem, NMU it as you prefer.

Thanks, I've now uploaded -1.2 taking -1.1 and your commit for the
perl issue (modulo changelog fiddling).

Debdiff attached.

Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Simon and Garfunkel: Fifty Ways To Leave Your Lover
diff -u ming-0.4.5/debian/changelog ming-0.4.5/debian/changelog
--- ming-0.4.5/debian/changelog
+++ ming-0.4.5/debian/changelog
@@ -1,3 +1,12 @@
+ming (1:0.4.5-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload with team member's permission.
+
+  [ Gabriele Giacone ]
+  * Do not hardcode /usr/lib/perl5 in d/rules and d/*.install (Closes: #752716).
+
+ -- gregor herrmann   Sat, 09 Aug 2014 14:59:22 +0200
+
 ming (1:0.4.5-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u ming-0.4.5/debian/libswf-perl.dirs ming-0.4.5/debian/libswf-perl.dirs
--- ming-0.4.5/debian/libswf-perl.dirs
+++ ming-0.4.5/debian/libswf-perl.dirs
@@ -1,3 +1 @@
-usr/lib/perl5/SWF
-usr/lib/perl5/auto/SWF
 usr/share/man/man3
reverted:
--- ming-0.4.5/debian/libswf-perl.install
+++ ming-0.4.5.orig/debian/libswf-perl.install
@@ -1,3 +0,0 @@
-usr/lib/perl5/SWF/*
-usr/lib/perl5/SWF.pm
-usr/lib/perl5/auto/SWF/*
diff -u ming-0.4.5/debian/rules ming-0.4.5/debian/rules
--- ming-0.4.5/debian/rules
+++ ming-0.4.5/debian/rules
@@ -20,6 +20,8 @@
 PYDEF=$(shell pyversions -d)
 PYVERS=$(shell pyversions -r)
 
+PERLARCHLIB := $(shell perl -MConfig -e 'print $$Config{vendorarch}')
+
 CFLAGS = -Wall -g
 
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
@@ -110,6 +112,7 @@
 	rm -f libming-util.1
 	if [ -f Makefile ]; then $(MAKE) distclean; fi
 	rm -f config.log config.sub config.guess
+	rm -f debian/libswf-perl.install
 
 	$(MAKE) -f /usr/share/quilt/quilt.make unpatch
 
@@ -125,7 +128,7 @@
 	# debian/tmp.
 	$(MAKE) install prefix=$(CURDIR)/debian/tmp/usr
 
-	chrpath -d debian/tmp/usr/lib/perl5/auto/SWF/SWF.so
+	chrpath -d debian/tmp/$(PERLARCHLIB)/auto/SWF/SWF.so
 	chrpath -d debian/tmp/usr/lib/php5/*/ming.so
 
 	# 0.4.5 has the man pages we were mising
@@ -133,7 +136,9 @@
 	dh_installman -p libming-util libming-util.1
 
 #	# Perl extension
-#	strip --remove-section=.comment --remove-section=.note --strip-unneeded debian/tmp/usr/lib/perl5/auto/SWF/SWF.so
+#	strip --remove-section=.comment --remove-section=.note --strip-unneeded debian/tmp/$(PERLARCHLIB)/auto/SWF/SWF.so
+
+	sed -e 's,$${perlarchlib},$(PERLARCHLIB),g' debian/libswf-perl.install.in > debian/libswf-perl.install
 
 	# install Python extension
 	for python in $(PYVERS); do \
only in patch2:
unchanged:
--- ming-0.4.5.orig/debian/libswf-perl.install.in
+++ ming-0.4.5/debian/libswf-perl.install.in
@@ -0,0 +1,3 @@
+${perlarchlib}/SWF/*
+${perlarchlib}/SWF.pm
+${perlarchlib}/auto/SWF/*


signature.asc
Description: Digital Signature

Processed: raise severity of issues fo rpackages build-depending on GCC 4.7

[Debian Bug Tracking System]

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

> severity 747998 serious
Bug #747998 [gcc-msp430] gcc-msp430: non-standard gcc/g++ used for build 
(gcc-4.7)
Severity set to 'serious' from 'important'
> severity 748004 serious
Bug #748004 [libreoffice] libreoffice: non-standard cpp used for build (cpp-4.7)
Bug #753373 [libreoffice] libreoffice: Please migrate away from gcc-4.7 in 
Jessie if possible
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> severity 748007 serious
Bug #748007 [nwchem] nwchem: non-standard gcc/g++ used for build (gcc-4.7)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
747998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747998
748004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748004
748007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748007
753373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753373
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#752809: marked as done (qt4-perl: hardcodes /usr/lib/perl5)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 13:04:39 +
with message-id 
and subject line Bug#752809: fixed in qt4-perl 4.8.4-1.1
has caused the Debian Bug report #752809,
regarding qt4-perl: hardcodes /usr/lib/perl5
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.)


-- 
752809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qt4-perl
Version: 4.8.4-1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition

Starting with version 5.20.0 (currently in experimental), the Debian
perl package is changing the "vendorarch" library paths (currently
/usr/lib/perl5) to include the multiarch triplet and the perl version. See
#748380 for details.

For this to work, packages containing binary perl modules need to migrate
from using the hardcoded /usr/lib/perl5 directory to the value of the
$Config{vendorarch} variable, as defined in the 'Config' module.

This package fails to build with perl_5.20.0-1 from experimental:

  dh_install -plibqtcore4-perl  
  cp: cannot stat 'debian/tmp/usr/lib/perl5/auto/QtCore4/QtCore4.so': No such 
file or directory
  dh_install: cp -a debian/tmp/usr/lib/perl5/auto/QtCore4/QtCore4.so 
debian/libqtcore4-perl//usr/lib/perl5/auto/QtCore4/ returned exit code 1
  make: *** [binary-install/libqtcore4-perl] Error 2

One solution for this might be an executable debhelper install file
(available with debhelper compat level 9) expanding $Config{vendorarch}.
See #751924 for an example of this.

Please ask on the debian-perl list if you want help with this, and see
 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.20-transition;users=debian-p...@lists.debian.org
for a list of similar bugs and patches.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: qt4-perl
Source-Version: 4.8.4-1.1

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Aug 2014 12:20:06 +
Source: qt4-perl
Binary: libqtcore4-perl libqtgui4-perl libqtxml4-perl libqtnetwork4-perl 
libqttest4-perl
Architecture: source amd64
Version: 4.8.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: Sune Vuorela 
Changed-By: Damyan Ivanov 
Description:
 libqtcore4-perl - perl bindings for the Qt Core library
 libqtgui4-perl - perl bindings for the Qt Gui library
 libqtnetwork4-perl - perl bindings for the Qt Network library
 libqttest4-perl - perl bindings for the Qt Test library
 libqtxml4-perl - perl bindings for the Qt Xml library
Closes: 752809
Changes:
 qt4-perl (4.8.4-1.1) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * Non-maintainer upload.
   * Fix "hardcodes /usr/lib/perl5":
 dynamically create debian/*.install files with the correct path from
 debian/rules during build
 (Closes: #752809)
Checksums-Sha1:
 6a47bf9d5c88b58d3901857df2ecb263db7026f6 2000 qt4-perl_4.8.4-1.1.dsc
 0bc2edf25eca66601f7937a24b70b815b57c2d29 2916 qt4-perl_4.8.4-1.1.debian.tar.xz
 a428eb2a2e3050546c015c6d94d5e62445353179 181278 
libqtcore4-perl_4.8.4-1.1_amd64.deb
 32bc8ef9d0862ce851285ec4e566ce22457c62b9 231812 
libqtgui4-perl_4.8.4-1.1_amd64.deb
 8de52bff1494f48facd1fce7cf6741b2678cd5ee 10214 
libqtxml4-perl_4.8.4-1.1_amd64.deb
 e00087840955e2829b31f1b100195be57ae23c9a 16072 
libqtnetwork4-perl_4.8.4-1.1_amd64.deb
 a36172a28995faee7dc88c41716c3198a47c3c45 32342 
libqttest4-perl_4.8.4-1.1_amd64.deb
Checksums-Sha256:
 a5deb3a84c1f79167182d5ac6f586a6defaa4bc8c71361340e757ee7bf56b3bb 2000 
qt4-perl_4.8.4-1.1.dsc
 9e197442f0c4c36a8506e45e6f39f5f34c1ec9e3fc58731100906de9bec9d83a 2916 
qt4-perl_4.8.4-1.1.debian.tar.xz
 4e1533c5e1e7b76ea3a24a6cce65a82e48af001f5b498029f1a5a89f25a3af8a 181278 
libqtcore4-perl_4.8.4-1.1_amd64.deb
 551677c34d3612df227e9b35936e7b43a3e2e7820d8ca81ff4e043059a03f5f5 231812 
libqtgui4-perl_4.8.4-1.1_amd64.deb
 f77e9a1ae6aca3529fbe383603fbf404dfa849baed6c9

Bug#752808: marked as done (qpid-cpp: hardcodes /usr/lib/perl5)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 13:04:28 +
with message-id 
and subject line Bug#752808: fixed in qpid-cpp 0.16-7.2
has caused the Debian Bug report #752808,
regarding qpid-cpp: hardcodes /usr/lib/perl5
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.)


-- 
752808: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qpid-cpp
Version: 0.16-7.1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition

Starting with version 5.20.0 (currently in experimental), the Debian
perl package is changing the "vendorarch" library paths (currently
/usr/lib/perl5) to include the multiarch triplet and the perl version. See
#748380 for details.

For this to work, packages containing binary perl modules need to migrate
from using the hardcoded /usr/lib/perl5 directory to the value of the
$Config{vendorarch} variable, as defined in the 'Config' module.

This package fails to build with perl_5.20.0-1 from experimental:

 dh_install -a
  cp: cannot stat 'debian/tmp/usr/lib/perl5': No such file or directory
  dh_install: cp -a debian/tmp/usr/lib/perl5 debian/libqpid-perl//usr/lib/ 
returned exit code 1
  make: *** [binary-arch] Error 2

One solution for this might be an executable debhelper install file
(available with debhelper compat level 9) expanding $Config{vendorarch}.
See #751924 for an example of this.

Please ask on the debian-perl list if you want help with this, and see
 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.20-transition;users=debian-p...@lists.debian.org
for a list of similar bugs and patches.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: qpid-cpp
Source-Version: 0.16-7.2

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated qpid-cpp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Aug 2014 11:56:12 +
Source: qpid-cpp
Binary: qpidd qpid-client libqmf1 libqmf-dev libqmf2-1 libqmf2-dev 
libqmfconsole2 libqmfconsole2-dev libqpidmessaging2 libqpidmessaging2-dev 
libsslcommon2 libsslcommon2-dev librdmawrap2 librdmawrap2-dev libqpidtypes1 
libqpidtypes1-dev libqpidcommon2 libqpidcommon2-dev libqpidclient2 
libqpidclient2-dev libqpidbroker2 libqpidbroker2-dev libqmfengine1 
libqmfengine1-dev python-cqpid python-qmf2 python-cqmf2 python-qmf qmfgen 
qpid-doc ruby-qpid libqpid-ruby1.8 libqpid-perl
Architecture: source amd64 all
Version: 0.16-7.2
Distribution: unstable
Urgency: medium
Maintainer: Cajus Pollmeier 
Changed-By: Damyan Ivanov 
Description:
 libqmf-dev - enterprise messaging system - QMF development files
 libqmf1- enterprise messaging system - QMF libraries
 libqmf2-1  - enterprise messaging system - QMF2 libraries
 libqmf2-dev - enterprise messaging system - QMF2 development files
 libqmfconsole2 - enterprise messaging system - QMF console library
 libqmfconsole2-dev - enterprise messaging system - QMF console development 
files
 libqmfengine1 - enterprise messaging system - QMF engine libraries
 libqmfengine1-dev - enterprise messaging system - QMF engine development files
 libqpid-perl - enterprise messaging system - Perl bindings
 libqpid-ruby1.8 - Transitional package for ruby-qpid
 libqpidbroker2 - enterprise messaging system - broker libraries
 libqpidbroker2-dev - enterprise messaging system - broker development files
 libqpidclient2 - enterprise messaging system - client libraries
 libqpidclient2-dev - enterprise messaging system - client development files
 libqpidcommon2 - enterprise messaging system - common libraries
 libqpidcommon2-dev - enterprise messaging system - common development files
 libqpidmessaging2 - enterprise messaging system - AMQP messaging libraries
 libqpidmessaging2-dev - enterprise messaging system - AMQP messaging 
development files
 libqpidtypes1 - enterprise messaging system - API libraries
 libqpidtypes1-dev - enterprise messaging system

Bug#746920: marked as done (wfmath: ftbfs with GCC-4.9)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 12:35:39 +
with message-id 
and subject line Bug#746920: fixed in wfmath 0.3.12-3.1
has caused the Debian Bug report #746920,
regarding wfmath: ftbfs with GCC-4.9
to be marked as done.

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

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


-- 
746920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wfmath
Version: 0.3.12-3
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

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

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/wfmath_0.3.12-3_unstable_gcc49.log
The last lines of the build log are at the end of this report.

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

  apt-get -t experimental install g++ 

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

[...]
  _ZGVZN6WFMath5PointILi3EE4ZEROEvE9zeroPoint@Base 0.3.11
  _ZGVZN6WFMath6VectorILi2EE4ZEROEvE10zeroVector@Base 0.3.11
@@ -48,7 +48,7 @@
  _ZN6WFMath13_ScaleEpsilonEPKfS1_id@Base 0.3.11
  _ZN6WFMath13_ScaleEpsilonEddd@Base 0.3.11
  
_ZN6WFMath14BoundingSphereILi2ESt6vectorEENS_4BallIXT_EEERKT0_INS_5PointIXT_EEESaIS6_EE@Base
 0.3.11
- (optional)_ZN6WFMath14SloppyDistanceILi2EEEfRKNS_5PointIXT_EEES4_@Base 0.3.12
+#MISSING: 0.3.12-3# 
(optional)_ZN6WFMath14SloppyDistanceILi2EEEfRKNS_5PointIXT_EEES4_@Base 0.3.12
  _ZN6WFMath14SloppyDistanceILi3EEEfRKNS_5PointIXT_EEES4_@Base 0.3.11
  _ZN6WFMath14_ReadCoordListERSiPfi@Base 0.3.11
  _ZN6WFMath15ColinearVectorsILi2EED0Ev@Base 0.3.11
@@ -964,10 +964,10 @@
  _ZNK6WFMath9RotMatrixILi3EEeqERKS1_@Base 0.3.11
  _ZNK6WFMath9RotMatrixILi3EEneERKS1_@Base 0.3.11
  
(optional=inline)_ZNSs12_S_constructIPcEES0_T_S1_RKSaIcESt20forward_iterator_tag@Base
 0.3.12
- (regex|optional=inline)_ZNSsC[12]IPcEET_S1_RKSaIcE@Base 0.3.11
- (optional=inline)_ZNSt10_List_baseI13LinePointDataSaIS0_EE8_M_clearEv@Base 
0.3.12
- 
(optional=inline)_ZNSt10_List_baseIN6WFMath11_PolyReaderILi3EEESaIS2_EE8_M_clearEv@Base
 0.3.12
- 
(optional=inline)_ZNSt10_List_baseIN6WFMath9_miniball13Wrapped_arrayILi2EEESaIS3_EE8_M_clearEv@Base
 0.3.12
+#MISSING: 0.3.12-3# (regex|optional=inline)_ZNSsC[12]IPcEET_S1_RKSaIcE@Base 
0.3.11
+#MISSING: 0.3.12-3# 
(optional=inline)_ZNSt10_List_baseI13LinePointDataSaIS0_EE8_M_clearEv@Base 
0.3.12
+#MISSING: 0.3.12-3# 
(optional=inline)_ZNSt10_List_baseIN6WFMath11_PolyReaderILi3EEESaIS2_EE8_M_clearEv@Base
 0.3.12
+#MISSING: 0.3.12-3# 
(optional=inline)_ZNSt10_List_baseIN6WFMath9_miniball13Wrapped_arrayILi2EEESaIS3_EE8_M_clearEv@Base
 0.3.12
  _ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 0.3.11
  _ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 0.3.11
  _ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 0.3.11
@@ -977,12 +977,14 @@
  
_ZNSt6vectorIfSaIfEE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPfS1_EERKf@Base
 0.3.11
  
(regex)_ZNSt6vectorIfSaIfEE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPfS1_EE[mj]RKf@Base
 0.3.11
  _ZNSt6vectorIfSaIfEE6insertEN9__gnu_cxx17__normal_iteratorIPfS1_EERKf@Base 
0.3.11
- (regex|optional=inline)_ZNSt6vectorIfSaIfEED[12]Ev@Base 0.3.12
- 
(regex)_ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIf[il]fEvT_T0_S8_T1_@Base
 0.3.11
- 
(optional=inline)_ZSt13__heap_selectIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIfEvT_S7_S7_@Base
 0.3.11
- 
_ZSt16__insertion_sortIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIfEvT_S7_@Base
 0.3.11
- 
(regex)_ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIf[li]EvT_S7_T0_@Base
 0.3.11
- 
(optional=inline)_ZSt19__move_median_firstIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIfEvT_S7_S7_@Base
 0.3.11
+#MISSING: 0.3.12-3# (regex|optional=inline)_ZNSt6vectorIfSaIfEED[12]Ev@Base 
0.3.12
+#MISSING: 0.3.12-3# 
(regex)_ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIf[il]fEvT_T0_S8_T1_@Base
 0.3.11
+ 
_ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIflfNS0_5__ops15_Iter_less_iterEEvT_T0_SA_T1_T2_@Base
 0.3.12-3
+#MISSING: 0.3.12-3# 
(optional=inline)_ZSt13__heap_selectIN9__gnu

Bug#752800: marked as done (openbabel: hardcodes /usr/lib/perl5)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 12:34:06 +
with message-id 
and subject line Bug#752800: fixed in openbabel 2.3.2+dfsg-1.2
has caused the Debian Bug report #752800,
regarding openbabel: hardcodes /usr/lib/perl5
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.)


-- 
752800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openbabel
Version: 2.3.2+dfsg-1.1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition

Starting with version 5.20.0 (currently in experimental), the Debian
perl package is changing the "vendorarch" library paths (currently
/usr/lib/perl5) to include the multiarch triplet and the perl version. See
#748380 for details.

For this to work, packages containing binary perl modules need to migrate
from using the hardcoded /usr/lib/perl5 directory to the value of the
$Config{vendorarch} variable, as defined in the 'Config' module.

This package fails to build with perl_5.20.0-1 from experimental:

  dh_install -Xperllocal.pod --list-missing
  dh_install: libchemistry-openbabel-perl missing files (usr/lib/perl*), 
aborting
  make[1]: *** [override_dh_install] Error 255
  debian/rules:46: recipe for target 'override_dh_install' failed
  make[1]: Leaving directory '/«BUILDDIR»/openbabel-2.3.2+dfsg'
  make: *** [binary-arch] Error 2

One solution for this might be an executable debhelper install file
(available with debhelper compat level 9) expanding $Config{vendorarch}.
See #751924 for an example of this.

Please ask on the debian-perl list if you want help with this, and see
 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.20-transition;users=debian-p...@lists.debian.org
for a list of similar bugs and patches.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: openbabel
Source-Version: 2.3.2+dfsg-1.2

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

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

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated openbabel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Aug 2014 11:31:02 +
Source: openbabel
Binary: openbabel openbabel-gui libopenbabel-dev libopenbabel4 libopenbabel-doc 
python-openbabel libchemistry-openbabel-perl
Architecture: source amd64 all
Version: 2.3.2+dfsg-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Damyan Ivanov 
Description:
 libchemistry-openbabel-perl - Chemical toolbox library (perl bindings)
 libopenbabel-dev - Chemical toolbox library (development files)
 libopenbabel-doc - Chemical toolbox library (documentation)
 libopenbabel4 - Chemical toolbox library
 openbabel  - Chemical toolbox utilities (cli)
 openbabel-gui - Chemical toolbox utilities (graphical user interface)
 python-openbabel - Chemical toolbox library (python bindings)
Closes: 752800
Changes:
 openbabel (2.3.2+dfsg-1.2) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * Non-maintainer upload.
   * Fix "hardcodes /usr/lib/perl5":
 - remove debian/libchemistry-openbabel-perl.install
 - pass perl directory to dh_install in debian/rules,
   expanded from $Config{vendorarch}
 (Closes: #752800)
Checksums-Sha1:
 33af60cc9866b5be396939bb7be6357917e424a4 2530 openbabel_2.3.2+dfsg-1.2.dsc
 7aab83a93ba8450e80ceffdf69f9dbbede8d6fd3 13864 
openbabel_2.3.2+dfsg-1.2.debian.tar.xz
 0802f2957d4bcf2ab881c3c406887c4653f76639 250298 
openbabel_2.3.2+dfsg-1.2_amd64.deb
 3de811c834e545d4ca1a56014ea5db422dc9237c 221668 
openbabel-gui_2.3.2+dfsg-1.2_amd64.deb
 496ac347795f22ef903d177104687ae9d8246096 314108 
libopenbabel-dev_2.3.2+dfsg-1.2_amd64.deb
 98f147e6d446ca977020671d75c49d14ae403336 2899080 
libopenbabel4_2.3.2+dfsg-1.2_amd64.deb
 3b8a6718d85dcad3aa1e96460d0feb11d3f27487 6057438 
libopenbabel-doc_2.3.2+dfsg-1.2_all.deb
 9e24a1f15efe4c6c2232d59de46c619fc3b0f281 794870 
python-openbabel_2.3.2+dfsg-1.2_amd64.deb
 b985752de705e7cbd2c27cee22f5e6fddfcc21e0 809442 
libchemistry-openbabel-perl_2.3.2+

Bug#746907: marked as done (qtwebkit: ftbfs with GCC-4.9)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 12:34:55 +
with message-id 
and subject line Bug#746907: fixed in qtwebkit 2.2.1-7.1
has caused the Debian Bug report #746907,
regarding qtwebkit: ftbfs with GCC-4.9
to be marked as done.

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

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


-- 
746907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qtwebkit
Version: 2.2.1-7
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

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

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/qtwebkit_2.2.1-7_unstable_gcc49.log
The last lines of the build log are at the end of this report.

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

  apt-get -t experimental install g++ 

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

[...]
../JavaScriptCore/wtf/PassOwnPtr.h: In member function 'bool 
WTF::PassOwnPtr::operator!=(const WTF::PassOwnPtr&)':
../JavaScriptCore/wtf/Assertions.h:326:47: warning: typedef 
'dummyOwnPtrs_should_never_be_equal' locally defined but not used 
[-Wunused-local-typedefs]
 #define COMPILE_ASSERT(exp, name) typedef int dummy##name [(exp) ? 1 : -1]
   ^
../JavaScriptCore/wtf/PassOwnPtr.h:96:70: note: in expansion of macro 
'COMPILE_ASSERT'
 template bool operator!=(const PassOwnPtr&) { 
COMPILE_ASSERT(!sizeof(U*), OwnPtrs_should_never_be_equal); return false; }
  ^
../JavaScriptCore/wtf/PassOwnPtr.h: In member function 'bool 
WTF::PassOwnPtr::operator==(const WTF::OwnPtr&)':
../JavaScriptCore/wtf/Assertions.h:326:47: warning: typedef 
'dummyOwnPtrs_should_never_be_equal' locally defined but not used 
[-Wunused-local-typedefs]
 #define COMPILE_ASSERT(exp, name) typedef int dummy##name [(exp) ? 1 : -1]
   ^
../JavaScriptCore/wtf/PassOwnPtr.h:97:66: note: in expansion of macro 
'COMPILE_ASSERT'
 template bool operator==(const OwnPtr&) { 
COMPILE_ASSERT(!sizeof(U*), OwnPtrs_should_never_be_equal); return false; }
  ^
../JavaScriptCore/wtf/PassOwnPtr.h: In member function 'bool 
WTF::PassOwnPtr::operator!=(const WTF::OwnPtr&)':
../JavaScriptCore/wtf/Assertions.h:326:47: warning: typedef 
'dummyOwnPtrs_should_never_be_equal' locally defined but not used 
[-Wunused-local-typedefs]
 #define COMPILE_ASSERT(exp, name) typedef int dummy##name [(exp) ? 1 : -1]
   ^
../JavaScriptCore/wtf/PassOwnPtr.h:98:66: note: in expansion of macro 
'COMPILE_ASSERT'
 template bool operator!=(const OwnPtr&) { 
COMPILE_ASSERT(!sizeof(U*), OwnPtrs_should_never_be_equal); return false; }
  ^
../JavaScriptCore/runtime/JSVariableObject.h: In constructor 
'JSC::JSVariableObject::JSVariableObject(JSC::JSGlobalData&, JSC::Structure*, 
JSC::SymbolTable*, JSC::Register*)':
../JavaScriptCore/wtf/Assertions.h:326:47: warning: typedef 
'dummyRegister_should_be_same_size_as_WriteBarrier' locally defined but not 
used [-Wunused-local-typedefs]
 #define COMPILE_ASSERT(exp, name) typedef int dummy##name [(exp) ? 1 : -1]
   ^
../JavaScriptCore/runtime/JSVariableObject.h:75:13: note: in expansion of macro 
'COMPILE_ASSERT'
 COMPILE_ASSERT(sizeof(WriteBarrier) == sizeof(Register), 
Register_should_be_same_size_as_WriteBarrier);
 ^
../JavaScriptCore/runtime/JSGlobalObject.h: In constructor 
'JSC::JSGlobalObject::JSGlobalObject(JSC::JSGlobalData&, JSC::Structure*)':
../JavaScriptCore/wtf/Assertions.h:326:47: warning: typedef 
'dummyJSGlobalObject_has_only_a_single_slot' locally defined but not used 
[-Wunused-local-typedefs]
 #define COMPILE_ASSERT(exp, name) typedef int dummy##name [(exp) ? 1 : -1]
   ^
../JavaScriptCore/runtime/JSGlobalObject.h:127:13: note: in expansion of macro 
'COMPILE_AS

Processed: Re: qtwebkit: ftbfs with GCC-4.9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #746907 [src:qtwebkit] qtwebkit: ftbfs with GCC-4.9
Added tag(s) patch.

-- 
746907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746907
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#746907: qtwebkit: ftbfs with GCC-4.9

[Matthias Klose]

Control: tags -1 + patch

uploaded the attached fix to delayed/5.
diff -Nru qtwebkit-2.2.1/debian/changelog qtwebkit-2.2.1/debian/changelog
--- qtwebkit-2.2.1/debian/changelog 2013-11-05 02:15:31.0 +0100
+++ qtwebkit-2.2.1/debian/changelog 2014-08-09 13:24:46.0 +0200
@@ -1,3 +1,10 @@
+qtwebkit (2.2.1-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Ignore warnings introduced by GCC 4.9. Closes: #746907.
+
+ -- Matthias Klose   Sat, 09 Aug 2014 13:23:55 +0200
+
 qtwebkit (2.2.1-7) unstable; urgency=low
 
   [ Nobuhiro Iwamatsu ]
diff -Nru qtwebkit-2.2.1/debian/patches/ignore-new_gcc_warnings.diff 
qtwebkit-2.2.1/debian/patches/ignore-new_gcc_warnings.diff
--- qtwebkit-2.2.1/debian/patches/ignore-new_gcc_warnings.diff  1970-01-01 
01:00:00.0 +0100
+++ qtwebkit-2.2.1/debian/patches/ignore-new_gcc_warnings.diff  2014-08-09 
13:26:30.0 +0200
@@ -0,0 +1,13 @@
+Index: b/Source/WebKit.pri
+===
+--- a/Source/WebKit.pri
 b/Source/WebKit.pri
+@@ -114,7 +114,7 @@ CONFIG -= warn_on
+ 
+ # Treat warnings as errors on x86/Linux/GCC
+ linux-g++*|glibc-*|hurd-* {
+-isEqual(QT_ARCH,x86_64)|isEqual(QT_ARCH,i386): QMAKE_CXXFLAGS += -Werror 
-Wno-error=unused-local-typedefs
++isEqual(QT_ARCH,x86_64)|isEqual(QT_ARCH,i386): QMAKE_CXXFLAGS += -Werror 
-Wno-error=unused-local-typedefs -Wno-error=unused-function
+ 
+ greaterThan(QT_GCC_MAJOR_VERSION, 3):greaterThan(QT_GCC_MINOR_VERSION, 5) 
{
+ if (!contains(QMAKE_CXXFLAGS, -std=c++0x) && 
!contains(QMAKE_CXXFLAGS, -std=gnu++0x)) {
diff -Nru qtwebkit-2.2.1/debian/patches/series 
qtwebkit-2.2.1/debian/patches/series
--- qtwebkit-2.2.1/debian/patches/series2013-07-24 05:29:27.0 
+0200
+++ qtwebkit-2.2.1/debian/patches/series2014-08-09 13:23:40.0 
+0200
@@ -18,3 +18,4 @@
 hurd.diff
 webkit_qt_hide_symbols.diff
 ignore-unused-local-typedefs_error.diff
+ignore-new_gcc_warnings.diff

Bug#746884: marked as done (molds: ftbfs with GCC-4.9)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 12:19:29 +
with message-id 
and subject line Bug#746884: fixed in molds 0.3.0-3.1
has caused the Debian Bug report #746884,
regarding molds: ftbfs with GCC-4.9
to be marked as done.

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

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


-- 
746884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:molds
Version: 0.3.0-3
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

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

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/molds_0.3.0-3_unstable_gcc49.log
The last lines of the build log are at the end of this report.

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

  apt-get -t experimental install g++ 

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

[...]
 from base/MolDSException.cpp:28:
/usr/include/c++/4.9/iomanip:175:5: note: template 
std::basic_ostream<_CharT, _Traits>& std::operator<<(std::basic_ostream<_CharT, 
_Traits>&, std::_Setfill<_CharT>)
 operator<<(basic_ostream<_CharT, _Traits>& __os, _Setfill<_CharT> __f)
 ^
/usr/include/c++/4.9/iomanip:175:5: note:   template argument 
deduction/substitution failed:
base/MolDSException.cpp:164:10: note:   'boost::archive::text_oarchive' is not 
derived from 'std::basic_ostream<_CharT, _Traits>'
oa << this;
  ^
In file included from /usr/include/boost/archive/basic_text_oprimitive.hpp:27:0,
 from /usr/include/boost/archive/text_oarchive.hpp:30,
 from base/MolDSException.cpp:28:
/usr/include/c++/4.9/iomanip:205:5: note: template 
std::basic_ostream<_CharT, _Traits>& std::operator<<(std::basic_ostream<_CharT, 
_Traits>&, std::_Setprecision)
 operator<<(basic_ostream<_CharT, _Traits>& __os, _Setprecision __f)
 ^
/usr/include/c++/4.9/iomanip:205:5: note:   template argument 
deduction/substitution failed:
base/MolDSException.cpp:164:10: note:   'boost::archive::text_oarchive' is not 
derived from 'std::basic_ostream<_CharT, _Traits>'
oa << this;
  ^
In file included from /usr/include/boost/archive/basic_text_oprimitive.hpp:27:0,
 from /usr/include/boost/archive/text_oarchive.hpp:30,
 from base/MolDSException.cpp:28:
/usr/include/c++/4.9/iomanip:235:5: note: template 
std::basic_ostream<_CharT, _Traits>& std::operator<<(std::basic_ostream<_CharT, 
_Traits>&, std::_Setw)
 operator<<(basic_ostream<_CharT, _Traits>& __os, _Setw __f)
 ^
/usr/include/c++/4.9/iomanip:235:5: note:   template argument 
deduction/substitution failed:
base/MolDSException.cpp:164:10: note:   'boost::archive::text_oarchive' is not 
derived from 'std::basic_ostream<_CharT, _Traits>'
oa << this;
  ^
base/MolDSException.cpp: In instantiation of 'void 
MolDS_base::MolDSException::serialize(Archive&, unsigned int) [with Archive = 
boost::archive::text_iarchive]':
/usr/include/boost/serialization/access.hpp:118:9:   required from 'static void 
boost::serialization::access::serialize(Archive&, T&, unsigned int) [with 
Archive = boost::archive::text_iarchive; T = MolDS_base::MolDSException]'
/usr/include/boost/serialization/serialization.hpp:69:69:   required from 'void 
boost::serialization::serialize(Archive&, T&, unsigned int) [with Archive = 
boost::archive::text_iarchive; T = MolDS_base::MolDSException]'
/usr/include/boost/serialization/serialization.hpp:128:27:   required from 
'void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with 
Archive = boost::archive::text_iarchive; T = MolDS_base::MolDSException]'
/usr/include/boost/archive/detail/iserializer.hpp:192:5:   required from 'void 
boost::archive::detail::iserializer::load_object_data(boost::archive::detail::basic_iarchive&, void*, unsigned 
int) const [with Archive = boost::archive::text_iarchive; T = 
MolDS_base::MolDSException]'
/usr/include/boost/archive/detail/iserializer.hpp:120:1:   required from 'class 
boost::archive::detail::iserializer'
/usr/include/boost/archive/detail/iserializer.hpp:344:5:   [ skipping 7 
instantiation

Bug#746866: marked as done (kumofs: ftbfs with GCC-4.9)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 12:18:56 +
with message-id 
and subject line Bug#746866: fixed in kumofs 0.4.13-6.1
has caused the Debian Bug report #746866,
regarding kumofs: ftbfs with GCC-4.9
to be marked as done.

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

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


-- 
746866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kumofs
Version: 0.4.13-6
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

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

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/kumofs_0.4.13-6_unstable_gcc49.log
The last lines of the build log are at the end of this report.

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

  apt-get -t experimental install g++ 

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

[...]
 from ./gateway/framework.h:21,
 from gateway/mod_store.cc:18:
gateway/mod_store.cc:500:43: note: 'rpc::msgobj res' previously declared here
 RPC_REPLY_IMPL(mod_store_t, Delete, from, res, err, z,
   ^
../logic/rpc_server.h:135:62: note: in definition of macro 'RPC_REPLY_IMPL'
  void MOD::res_##NAME(basic_shared_session from, rpc::msgobj res, rpc::msgobj 
err, \
  ^
gateway/mod_store.cc:270:16: error: redeclaration of 'kumo::gate::res_delete 
res' [-fpermissive]
  response_type res; \
^
gateway/mod_store.cc:541:1: note: in expansion of macro 'GATEWAY_CATCH'
 GATEWAY_CATCH(ResDelete, gate::res_delete)
 ^
In file included from ../logic/client_logic.h:22:0,
 from ./gateway/framework.h:21,
 from gateway/mod_store.cc:18:
gateway/mod_store.cc:500:43: note: 'rpc::msgobj res' previously declared here
 RPC_REPLY_IMPL(mod_store_t, Delete, from, res, err, z,
   ^
../logic/rpc_server.h:135:62: note: in definition of macro 'RPC_REPLY_IMPL'
  void MOD::res_##NAME(basic_shared_session from, rpc::msgobj res, rpc::msgobj 
err, \
  ^
gateway/mod_store.cc:275:16: error: redeclaration of 'kumo::gate::res_delete 
res' [-fpermissive]
  response_type res; \
^
gateway/mod_store.cc:541:1: note: in expansion of macro 'GATEWAY_CATCH'
 GATEWAY_CATCH(ResDelete, gate::res_delete)
 ^
In file included from ../logic/client_logic.h:22:0,
 from ./gateway/framework.h:21,
 from gateway/mod_store.cc:18:
gateway/mod_store.cc:500:43: note: 'rpc::msgobj res' previously declared here
 RPC_REPLY_IMPL(mod_store_t, Delete, from, res, err, z,
   ^
../logic/rpc_server.h:135:62: note: in definition of macro 'RPC_REPLY_IMPL'
  void MOD::res_##NAME(basic_shared_session from, rpc::msgobj res, rpc::msgobj 
err, \
  ^
make[5]: *** [kumo_gateway-mod_store.o] Error 1
make[5]: Leaving directory `/«PKGBUILDDIR»/src/logic'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/«PKGBUILDDIR»/src/logic'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/«PKGBUILDDIR»/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/«PKGBUILDDIR»'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/«PKGBUILDDIR»'
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: kumofs
Source-Version: 0.4.13-6.1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier o

Bug#746833: marked as done (cadabra: ftbfs with GCC-4.9)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 12:03:51 +
with message-id 
and subject line Bug#746833: fixed in cadabra 1.39-0.1
has caused the Debian Bug report #746833,
regarding cadabra: ftbfs with GCC-4.9
to be marked as done.

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

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


-- 
746833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cadabra
Version: 1.29-1
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

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

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/cadabra_1.29-1_unstable_gcc49.log
The last lines of the build log are at the end of this report.

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

  apt-get -t experimental install g++ 

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

[...]
g++ -g -O2 -Wall -I. -I../src `pkg-config modglue --cflags` 
-D"RELEASE=\"1.29\"" -D"DATETIME=\"`date | sed -e 's/  / /'`\"" 
-DHOSTNAME=\"`hostname`\" -c -o defaults.o defaults.cc
g++ -g -O2 -Wall -I. -I../src `pkg-config modglue --cflags` 
-D"RELEASE=\"1.29\"" -D"DATETIME=\"`date | sed -e 's/  / /'`\"" 
-DHOSTNAME=\"`hostname`\" -c -o stopwatch.o stopwatch.cc
g++ -o cadabra  -Wl,--as-needed preprocessor.o storage.o display.o parser.o 
main.o algorithm.o manipulator.o youngtab.o combinatorics.o props.o settings.o 
exchange.o defaults.o stopwatch.o modules/algebra.o modules/pertstring.o 
modules/convert.o modules/gamma.o modules/field_theory.o modules/select.o 
modules/dummies.o modules/output.o modules/properties.o modules/relativity.o 
modules/substitute.o modules/tableaux.o modules/diff_geometry.o 
modules/numerical.o modules/linear.o modules/combinat.o modules/xperm_new.o 
modules/lie.o modules/lists.o modules/eval.o `pkg-config modglue --libs` 
-lgmpxx -lpcrecpp -lgmp
g++ -g -O2 -Wall -I. -I../src `pkg-config modglue --cflags` 
-D"RELEASE=\"1.29\"" -D"DATETIME=\"`date | sed -e 's/  / /'`\"" 
-DHOSTNAME=\"`hostname`\" -c -o test_gmp.o test_gmp.cc
g++ -o test_gmp test_gmp.o  -lgmpxx -lgmp
g++ -g -O2 -Wall -I. -I../src `pkg-config modglue --cflags` 
-D"RELEASE=\"1.29\"" -D"DATETIME=\"`date | sed -e 's/  / /'`\"" 
-DHOSTNAME=\"`hostname`\" -c -o test_preprocessor.o test_preprocessor.cc
g++ -o test_preprocessor test_preprocessor.o preprocessor.o  -lgmpxx -lgmp
g++ -g -O2 -Wall -I. -I../src `pkg-config modglue --cflags` 
-D"RELEASE=\"1.29\"" -D"DATETIME=\"`date | sed -e 's/  / /'`\"" 
-DHOSTNAME=\"`hostname`\" -c -o test_tree.o test_tree.cc
g++ -o test_tree test_tree.o
g++ -g -O2 -Wall -I. -I../src `pkg-config modglue --cflags` 
-D"RELEASE=\"1.29\"" -D"DATETIME=\"`date | sed -e 's/  / /'`\"" 
-DHOSTNAME=\"`hostname`\" -c -o tree_example.o tree_example.cc
g++ -o tree_example tree_example.o
g++ -g -O2 -Wall -I. -I../src `pkg-config modglue --cflags` 
-D"RELEASE=\"1.29\"" -D"DATETIME=\"`date | sed -e 's/  / /'`\"" 
-DHOSTNAME=\"`hostname`\" -c -o test_combinatorics.o test_combinatorics.cc
g++ -o test_combinatorics test_combinatorics.o combinatorics.o
g++ -g -O2 -Wall -I. -I../src `pkg-config modglue --cflags` 
-D"RELEASE=\"1.29\"" -D"DATETIME=\"`date | sed -e 's/  / /'`\"" 
-DHOSTNAME=\"`hostname`\" -c -o test_young.o test_young.cc
g++ -o test_young test_young.o youngtab.o combinatorics.o  -lgmpxx -lgmp
g++ -g -O2 -Wall -I. -I../src `pkg-config modglue --cflags` 
-D"RELEASE=\"1.29\"" -D"DATETIME=\"`date | sed -e 's/  / /'`\"" 
-DHOSTNAME=\"`hostname`\" -c -o tree_regression_tests.o tree_regression_tests.cc
tree_regression_tests.cc: In function 'int test2()':
tree_regression_tests.cc:90:38: warning: variable 'more_text' set but not used 
[-Wunused-but-set-variable]
  tree::sibling_iterator more_text=tr.append_child(body, "more 
text");
  ^
g++ -o tree_regression_tests tree_regression_tests.o
g++ -g -O2 -Wall -I. -I../src `pkg-config modglue --cflags` 
-D"RELEASE=\"1.29\"" -D"DATETIME=\"`date | sed -e 's/  / /'`\"" 
-DHOSTNAME=\"`hostname`\" -c -o test_xperm.o test_xperm.cc
gcc  -g -O2 -Wall -I. -I../src `pkg-config modglue --cflags` 
-D"RELEASE=\"1.29\"" -D"DATETIME=\"`da

Bug#752813: marked as done (rrdtool: hardcodes /usr/lib/perl5)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 12:04:35 +
with message-id 
and subject line Bug#752813: fixed in rrdtool 1.4.8-1.1
has caused the Debian Bug report #752813,
regarding rrdtool: hardcodes /usr/lib/perl5
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.)


-- 
752813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rrdtool
Version: 1.4.8-1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition

Starting with version 5.20.0 (currently in experimental), the Debian
perl package is changing the "vendorarch" library paths (currently
/usr/lib/perl5) to include the multiarch triplet and the perl version. See
#748380 for details.

For this to work, packages containing binary perl modules need to migrate
from using the hardcoded /usr/lib/perl5 directory to the value of the
$Config{vendorarch} variable, as defined in the 'Config' module.

This package fails to build with perl_5.20.0-1 from experimental:

  dh_install --sourcedir=/«PKGBUILDDIR»/debian/tmp -X.la --fail-missing
  cp: cannot stat '/«PKGBUILDDIR»/debian/tmp/usr/lib/perl5/auto/RRDs': No such 
file or directory
  dh_install: cp -a /«PKGBUILDDIR»/debian/tmp/usr/lib/perl5/auto/RRDs 
debian/librrds-perl//usr/lib/perl5/auto/ returned exit code 1
  make: *** [install-common-stamp] Error 2

One solution for this might be an executable debhelper install file
(available with debhelper compat level 9) expanding $Config{vendorarch}.
See #751924 for an example of this.

Please ask on the debian-perl list if you want help with this, and see
 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.20-transition;users=debian-p...@lists.debian.org
for a list of similar bugs and patches.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: rrdtool
Source-Version: 1.4.8-1.1

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated rrdtool package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Aug 2014 11:16:56 +
Source: rrdtool
Binary: rrdtool rrdcached rrdtool-dbg librrd4 librrd-dev librrds-perl 
librrdp-perl rrdtool-tcl python-rrdtool ruby-rrd librrd-ruby librrd-ruby1.8 
librrd-ruby1.9.1 liblua5.1-rrd0 liblua5.1-rrd-dev
Architecture: source amd64 all
Version: 1.4.8-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian RRDtool Team 
Changed-By: Damyan Ivanov 
Description:
 liblua5.1-rrd-dev - time-series data storage and display system (Lua 5.1 
development)
 liblua5.1-rrd0 - time-series data storage and display system (Lua 5.1 
interface)
 librrd-dev - time-series data storage and display system (development)
 librrd-ruby - Transitional package to ruby-rrd
 librrd-ruby1.8 - Transitional package to ruby-rrd
 librrd-ruby1.9.1 - Transitional package to ruby-rrd
 librrd4- time-series data storage and display system (runtime library)
 librrdp-perl - time-series data storage and display system (Perl interface, 
pipe
 librrds-perl - time-series data storage and display system (Perl interface, 
shar
 python-rrdtool - time-series data storage and display system (Python interface)
 rrdcached  - data caching daemon for RRDtool
 rrdtool- time-series data storage and display system (programs)
 rrdtool-dbg - time-series data storage and display system (debugging symbols)
 rrdtool-tcl - time-series data storage and display system (Tcl interface)
 ruby-rrd   - time-series data storage and display system (Ruby interface)
Closes: 752813
Changes:
 rrdtool (1.4.8-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix failure to build with perl 5.20 from experimental
 Closes: #752813
 + convert librrds-perl.install to executable script using
   $Config{vendorarch} instead of hardcoding /usr/lib/perl5
 + bump debhelper build-dependency and compat level to 9, needed for having
   an executable .install
Checksums-Sha1:
 2aec27b07bc3da81a89c69cba

Bug#746854: marked as done (glob2: ftbfs with GCC-4.9)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 12:04:04 +
with message-id 
and subject line Bug#746854: fixed in glob2 0.9.4.4-2.3
has caused the Debian Bug report #746854,
regarding glob2: ftbfs with GCC-4.9
to be marked as done.

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

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


-- 
746854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:glob2
Version: 0.9.4.4-2.2
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

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

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/glob2_0.9.4.4-2.2_unstable_gcc49.log
The last lines of the build log are at the end of this report.

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

  apt-get -t experimental install g++ 

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

[...]
g++ -o libgag/src/CursorManager.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
-D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL 
libgag/src/CursorManager.cpp
g++ -o libgag/src/FileManager.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
-D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL libgag/src/FileManager.cpp
g++ -o libgag/src/FormatableString.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
-D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL 
libgag/src/FormatableString.cpp
g++ -o libgag/src/GraphicContext.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
-D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL 
libgag/src/GraphicContext.cpp
g++ -o libgag/src/GUIAnimation.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
-D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL libgag/src/GUIAnimation.cpp
g++ -o libgag/src/GUIBase.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 -D_REENTRANT 
-Ilibgag/include -I. -I/usr/include/SDL libgag/src/GUIBase.cpp
g++ -o libgag/src/GUIButton.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
-D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL libgag/src/GUIButton.cpp
g++ -o libgag/src/GUIFileList.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
-D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL libgag/src/GUIFileList.cpp
g++ -o libgag/src/GUIKeySelector.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
-D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL 
libgag/src/GUIKeySelector.cpp
g++ -o libgag/src/GUIList.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 -D_REENTRANT 
-Ilibgag/include -I. -I/usr/include/SDL libgag/src/GUIList.cpp
g++ -o libgag/src/GUIMessageBox.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
-D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL 
libgag/src/GUIMessageBox.cpp
g++ -o libgag/src/GUINumber.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
-D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL libgag/src/GUINumber.cpp
g++ -o libgag/src/GUIRatio.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 -D_REENTRANT 
-Ilibgag/include -I. -I/usr/include/SDL libgag/src/GUIRatio.cpp
g++ -o libgag/src/GUISelector.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
-D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL libgag/src/GUISelector.cpp
g++ -o libgag/src/GUIStyle.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 -D_REENTRANT 
-Ilibgag/include -I. -I/usr/include/SDL libgag/src/GUIStyle.cpp
g++ -o libgag/src/GUITextArea.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
-D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL libgag/src/GUITextArea.cpp
g++ -o libgag/src/GUIText.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 -D_REENTRANT 
-Ilibgag/include -I. -I/usr/include/SDL libgag/src/GUIText.cpp
g++ -o libgag/src/GUITextInput.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
-D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL libgag/src/GUITextInput.cpp
g++ -o libgag/src/GUIImage.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 -D_REENTRANT 
-Ilibgag/include -I. -I/usr/include/SDL libgag/src/GUIImage.cpp
g++ -o libgag/src/GUIProgressBar.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
-D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL 
libgag/src/GUIProgressBar.cpp
g++ -o libgag/src/KeyPress.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 -D_REENTRANT 
-Ilibgag/include -I. -I/usr/include/SDL libgag/src/KeyPress.cpp
g++ -o libgag/src/Sprite.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 -D_REENTRANT 
-Ilibgag/include

Bug#736014: marked as done (please build-depend on libtiff-dev, not libtiff4-dev)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 11:18:56 +
with message-id 
and subject line Bug#736014: fixed in iaxmodem 1.2.0~dfsg-2
has caused the Debian Bug report #736014,
regarding please build-depend on libtiff-dev, not libtiff4-dev
to be marked as done.

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

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


-- 
736014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iaxmodem
Version: 1.2.0~dfsg-1
User: q...@debian.org
Usertags: libtiff4-dev

The libtiff4-dev package is a transitional package that is going to
disappear soon.  Please update your build dependency from libtiff4-dev
to libtiff-dev.
--- End Message ---
--- Begin Message ---
Source: iaxmodem
Source-Version: 1.2.0~dfsg-2

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

Debian distribution maintenance software
pp.
Tzafrir Cohen  (supplier of updated iaxmodem 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: Sat, 26 Jul 2014 22:25:16 +0300
Source: iaxmodem
Binary: iaxmodem
Architecture: source amd64
Version: 1.2.0~dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Debian VoIP Team 
Changed-By: Tzafrir Cohen 
Description:
 iaxmodem   - software modem with IAX2 connectivity
Closes: 641729 688548 736014
Changes:
 iaxmodem (1.2.0~dfsg-2) unstable; urgency=low
 .
   * Allow building with libtiff5 (Closes: #736014).
   * jblache is no longer an uploader (Closes: #688548).
   * Switch to dpkg V3 format.
   * Fix link command for building with ld --as-needed (Closes: #641729).
   * Update VCS fields.
   * Convert to dh.
   * Explicit [L]GPL-2 in debian/copyright.
   * uild_flags.patch: pass flags from dpkg-buildflags.
Checksums-Sha1:
 2404330815bbcea39c40d168bc313024c32e0cee 1861 iaxmodem_1.2.0~dfsg-2.dsc
 289db2b194102b2d4e20e117eb721ea695c4cb22 8004 
iaxmodem_1.2.0~dfsg-2.debian.tar.xz
 343b71c848417b57b6955fb71b238a3b6455a681 140630 iaxmodem_1.2.0~dfsg-2_amd64.deb
Checksums-Sha256:
 99558fd676c05e7dc37de7fcf9cc54b91cf9fa4cbbc01c0be342d12113c36b1b 1861 
iaxmodem_1.2.0~dfsg-2.dsc
 d7355925ad50da6cf082d9972b6bdf7a66570ab75e4e3766579ef4edaeb929c1 8004 
iaxmodem_1.2.0~dfsg-2.debian.tar.xz
 c844ae42ab394ddf348b9863607a2fceb7d1e86a7830875c321d37c00cf50c82 140630 
iaxmodem_1.2.0~dfsg-2_amd64.deb
Files:
 d325141054d310cbf5915f3fcf0030d2 140630 comm optional 
iaxmodem_1.2.0~dfsg-2_amd64.deb
 7cbab3f0d11ca8721528908a1dd7453b 1861 comm optional iaxmodem_1.2.0~dfsg-2.dsc
 ebf8d761261b16d4c22d78d51dceccac 8004 comm optional 
iaxmodem_1.2.0~dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQGcBAEBCAAGBQJT5gCoAAoJEJGAk2faxSZiju0L/jrde0nTlLLyz9BMxwQIql/K
6JbkAnC3qJEhkPyD1vsqSBJHv34vAezO6n0ntPwyeawT9fiNQqGe7110PooVcNv3
thH5a6zJjgTnqXWzV34XcIa9LGZ6ycZOiq9PQprG7px0lLUfOignKEo1gZHDOu8y
M6UDmVVlcvLluN9JG7O58VwAo55VvmKLoi9iSO9orr0OvTHHa68q7AvjOZXS7ORb
9VO/PImRww6rUUZ6Fyb1CP4ODnnI3+Sbzol/ypktSeZAVS8btBTamDJiMJ38qI+M
mS6yZb3hWzK6r8sKMJ5A8NgiY8vUj6LenQbmG+0k17Ty81xQ7S0mI6MPCSSMMo2e
DTpKK+xciIQ4c5BbmumAyXZosUE49k35aU3HBRRn2wtSctl92wM8+KJpesWrpumv
TuoeWJLu4G+q2QachKeugdSPmTaVsGaKvrI/STBARxJDTGi2wCVFR8QnFs2Z39Yb
6+Q9PrzWQ799anEV83GlpZG/FyGlP9p50oO7fcDnQA==
=VOoo
-END PGP SIGNATURE End Message ---

Bug#746889: marked as done (okteta: ftbfs with GCC-4.9)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 13:14:03 +0200
with message-id <53e6027b.90...@debian.org>
and subject line apparently built
has caused the Debian Bug report #746889,
regarding okteta: ftbfs with GCC-4.9
to be marked as done.

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

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


-- 
746889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:okteta
Version: 4:4.11.3-3
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

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

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/okteta_4.11.3-3_unstable_gcc49.log
The last lines of the build log are at the end of this report.

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

  apt-get -t experimental install g++ 

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

[...]
  _ZN7Kasten238AbstractModelStreamEncoderConfigEditorD2Ev@ABI_2_0 4:4.10.2
- _ZN7Kasten240AbstractModelExporterConfigEditorFactoryD0Ev@ABI_2_0 4:4.10.2
- _ZN7Kasten240AbstractModelExporterConfigEditorFactoryD1Ev@ABI_2_0 4:4.10.2
- _ZN7Kasten240AbstractModelExporterConfigEditorFactoryD2Ev@ABI_2_0 4:4.10.2
+#MISSING: 4:4.11.3-3# 
_ZN7Kasten240AbstractModelExporterConfigEditorFactoryD0Ev@ABI_2_0 4:4.10.2
+#MISSING: 4:4.11.3-3# 
_ZN7Kasten240AbstractModelExporterConfigEditorFactoryD1Ev@ABI_2_0 4:4.10.2
+#MISSING: 4:4.11.3-3# 
_ZN7Kasten240AbstractModelExporterConfigEditorFactoryD2Ev@ABI_2_0 4:4.10.2
  
_ZN7Kasten242ModelEncoderFileSystemExporterConfigEditor11qt_metacallEN11QMetaObject4CallEiPPv@ABI_2_0
 4:4.10.2
  
_ZN7Kasten242ModelEncoderFileSystemExporterConfigEditor11qt_metacastEPKc@ABI_2_0
 4:4.10.2
  
_ZN7Kasten242ModelEncoderFileSystemExporterConfigEditor16staticMetaObjectE@ABI_2_0
 4:4.10.2
@@ -306,12 +306,12 @@
  _ZN7Kasten242ModelEncoderFileSystemExporterConfigEditorD0Ev@ABI_2_0 4:4.10.2
  _ZN7Kasten242ModelEncoderFileSystemExporterConfigEditorD1Ev@ABI_2_0 4:4.10.2
  _ZN7Kasten242ModelEncoderFileSystemExporterConfigEditorD2Ev@ABI_2_0 4:4.10.2
- 
(optional=gccinternal|arch=!armhf)_ZN7Kasten245AbstractModelDataGeneratorConfigEditorFactoryD0Ev@ABI_2_0
 4:4.10.2
- 
(optional=gccinternal|arch=!armhf)_ZN7Kasten245AbstractModelDataGeneratorConfigEditorFactoryD1Ev@ABI_2_0
 4:4.10.2
- 
(optional=gccinternal|arch=!armhf)_ZN7Kasten245AbstractModelDataGeneratorConfigEditorFactoryD2Ev@ABI_2_0
 4:4.10.2
- 
(optional=gccinternal|arch=!armhf)_ZN7Kasten245AbstractModelStreamEncoderConfigEditorFactoryD0Ev@ABI_2_0
 4:4.10.2
- 
(optional=gccinternal|arch=!armhf)_ZN7Kasten245AbstractModelStreamEncoderConfigEditorFactoryD1Ev@ABI_2_0
 4:4.10.2
- 
(optional=gccinternal|arch=!armhf)_ZN7Kasten245AbstractModelStreamEncoderConfigEditorFactoryD2Ev@ABI_2_0
 4:4.10.2
+#MISSING: 4:4.11.3-3# 
(optional=gccinternal|arch=!armhf)_ZN7Kasten245AbstractModelDataGeneratorConfigEditorFactoryD0Ev@ABI_2_0
 4:4.10.2
+#MISSING: 4:4.11.3-3# 
(optional=gccinternal|arch=!armhf)_ZN7Kasten245AbstractModelDataGeneratorConfigEditorFactoryD1Ev@ABI_2_0
 4:4.10.2
+#MISSING: 4:4.11.3-3# 
(optional=gccinternal|arch=!armhf)_ZN7Kasten245AbstractModelDataGeneratorConfigEditorFactoryD2Ev@ABI_2_0
 4:4.10.2
+#MISSING: 4:4.11.3-3# 
(optional=gccinternal|arch=!armhf)_ZN7Kasten245AbstractModelStreamEncoderConfigEditorFactoryD0Ev@ABI_2_0
 4:4.10.2
+#MISSING: 4:4.11.3-3# 
(optional=gccinternal|arch=!armhf)_ZN7Kasten245AbstractModelStreamEncoderConfigEditorFactoryD1Ev@ABI_2_0
 4:4.10.2
+#MISSING: 4:4.11.3-3# 
(optional=gccinternal|arch=!armhf)_ZN7Kasten245AbstractModelStreamEncoderConfigEditorFactoryD2Ev@ABI_2_0
 4:4.10.2
  
_ZN7Kasten249ModelEncoderFileSystemExporterConfigEditorFactoryC1EPNS_45AbstractModelStreamEncoderConfigEditorFactoryE@ABI_2_0
 4:4.10.2
  
_ZN7Kasten249ModelEncoderFileSystemExporterConfigEditorFactoryC2EPNS_45AbstractModelStreamEncoderConfigEditorFactoryE@ABI_2_0
 4:4.10.2
  _ZN7Kasten249ModelEncoderFileSystemExporterConfigEditorFactoryD0Ev@ABI_2_0 
4:4.10.2
@@ -523,8 +523,8 @@
  _ZTVN7Kasten249ModelEncoderFileSystemExporterConfigEditorFactoryE@ABI_2_0 
4:4.10.2
  _ZTVN7Kasten29DummyViewE@ABI_2_0 4:4.10.2
  _ZTVN7Kasten29StatusBarE@A

Bug#730033: marked as done (okteta: FTBFS: 'QDir().mkpath(path)' returned FALSE.)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 13:14:03 +0200
with message-id <53e6027b.90...@debian.org>
and subject line apparently built
has caused the Debian Bug report #730033,
regarding okteta: FTBFS: 'QDir().mkpath(path)' returned FALSE.
to be marked as done.

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

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


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

Automatic builds of okteta for most architectures failed with test
suite errors:

  * Start testing of TestDocumentFileSynchronizerTest *
  Config: Using QTest library 4.8.6, Qt 4.8.6
  FAIL!  : TestDocumentFileSynchronizerTest::initTestCase() 
'QDir().mkpath(path)' returned FALSE. ()
 Loc: [../../../../../libs/kasten/core/tests/util/filesystem.cpp(71)]
  PASS   : TestDocumentFileSynchronizerTest::cleanupTestCase()
  Totals: 1 passed, 1 failed, 0 skipped
  * Finished testing of TestDocumentFileSynchronizerTest *
  [...]  
  The following tests FAILED:
  2 - libkasten-core-testdocumentfilesynchronizertest (Failed)
  3 - libkasten-core-testdocumentfilesynchronizerfactorytest (Failed)
 40 - oktetakasten-io-bytearrayrawfilesynchronizertest (Failed)
 41 - oktetakasten-io-bytearrayrawfilesynchronizerfactorytest (Failed)

I suspect these tests were relying on a writable HOME, which Debian's
autobuilders don't provide.  At any rate, could you please take a look?

Thanks!
--- End Message ---
--- Begin Message ---
Version: 4:4.13.3-1

apparently built.--- End Message ---

Bug#746865: marked as done (kde-workspace: ftbfs with GCC-4.9)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 13:06:26 +0200
with message-id <53e600b2.2080...@debian.org>
and subject line apparently built
has caused the Debian Bug report #746865,
regarding kde-workspace: ftbfs with GCC-4.9
to be marked as done.

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

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


-- 
746865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kde-workspace
Version: 4:4.11.8-1
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

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

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/kde-workspace_4.11.8-1_unstable_gcc49.log
The last lines of the build log are at the end of this report.

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

  apt-get -t experimental install g++ 

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

[...]
dpkg-gensymbols: warning: debian/libkwineffects1abi5/DEBIAN/symbols doesn't 
match completely debian/libkwineffects1abi5.symbols
--- debian/libkwineffects1abi5.symbols (libkwineffects1abi5_4:4.11.8-1_amd64)
+++ dpkg-gensymbolsQjinoK   2014-04-19 19:38:27.787064723 +
@@ -221,7 +221,7 @@
  _ZN4KWin6EffectD0Ev@ABI_1_5 4:4.11.1
  _ZN4KWin6EffectD1Ev@ABI_1_5 4:4.11.1
  _ZN4KWin6EffectD2Ev@ABI_1_5 4:4.11.1
- (optional=templinst)_ZN4KWin6MotionI7QPointFE9calculateEi@ABI_1_5 4:4.11.2
+#MISSING: 4:4.11.8-1# 
(optional=templinst)_ZN4KWin6MotionI7QPointFE9calculateEi@ABI_1_5 4:4.11.2
  (optional=templinst|arch=ia64 
powerpc)_ZN4KWin6MotionI7QPointFEC1ERKS2_@ABI_1_5 4:4.11.3
  (optional=templinst|arch=ia64 
powerpc)_ZN4KWin6MotionI7QPointFEC2ERKS2_@ABI_1_5 4:4.11.3
  _ZN4KWin7effectsE@ABI_1_5 4:4.11.1
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libkephal4abi1/DEBIAN/symbols doesn't match 
completely debian/libkephal4abi1.symbols
--- debian/libkephal4abi1.symbols (libkephal4abi1_4:4.11.8-1_amd64)
+++ dpkg-gensymbolsB7F3LE   2014-04-19 19:38:28.239063565 +
@@ -14,9 +14,9 @@
  _ZN6Kephal6Screen4geomEv@ABI_4_1 4:4.6.1
  _ZN6Kephal6ScreenC1EP7QObject@ABI_4_1 4:4.6.1
  _ZN6Kephal6ScreenC2EP7QObject@ABI_4_1 4:4.6.1
- _ZN6Kephal6ScreenD0Ev@ABI_4_1 4:4.6.5
- _ZN6Kephal6ScreenD1Ev@ABI_4_1 4:4.6.5
- _ZN6Kephal6ScreenD2Ev@ABI_4_1 4:4.6.5
+#MISSING: 4:4.11.8-1# _ZN6Kephal6ScreenD0Ev@ABI_4_1 4:4.6.5
+#MISSING: 4:4.11.8-1# _ZN6Kephal6ScreenD1Ev@ABI_4_1 4:4.6.5
+#MISSING: 4:4.11.8-1# _ZN6Kephal6ScreenD2Ev@ABI_4_1 4:4.6.5
  _ZN6Kephal7Screens10s_instanceE@ABI_4_1 4:4.6.1
  _ZN6Kephal7Screens11qt_metacallEN11QMetaObject4CallEiPPv@ABI_4_1 4:4.6.1
  _ZN6Kephal7Screens11qt_metacastEPKc@ABI_4_1 4:4.6.1
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
Use of uninitialized value in numeric eq (==) at /usr/bin/dh_makeshlibs line 
251.
dh_makeshlibs: failing due to earlier errors
make[2]: *** [override_dh_makeshlibs] Error 2
make[2]: Leaving directory `/«PKGBUILDDIR»'
make[1]: *** [pre_binary-arch_dh_makeshlibs] Error 2
make[1]: Leaving directory `/«PKGBUILDDIR»'
make: *** [debian/dhm

Bug#746870: marked as done (libopenraw: ftbfs with GCC-4.9)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 10:49:08 +
with message-id 
and subject line Bug#746870: fixed in libopenraw 0.0.9-3.5
has caused the Debian Bug report #746870,
regarding libopenraw: ftbfs with GCC-4.9
to be marked as done.

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

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


-- 
746870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libopenraw
Version: 0.0.9-3.4
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9

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

The full build log can be found at:
http://people.debian.org/~doko/logs/failed-gcc49/libopenraw_0.0.9-3.4_unstable_gcc49.log
The last lines of the build log are at the end of this report.

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

  apt-get -t experimental install g++ 

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

[...]
+#MISSING: 0.0.9-3.4# 
(optional=templinst)_ZTv0_n12_NK5boost16exception_detail10clone_implINS0_19error_info_injectorINS_2io13too_many_args5cloneEv@Base
 0.0.9
+#MISSING: 0.0.9-3.4# 
(optional=templinst)_ZTv0_n12_NK5boost16exception_detail10clone_implINS0_19error_info_injectorINS_2io17bad_format_string5cloneEv@Base
 0.0.9
+#MISSING: 0.0.9-3.4# 
(optional=templinst)_ZTv0_n16_NK5boost16exception_detail10clone_implINS0_19error_info_injectorINS_17bad_function_call7rethrowEv@Base
 0.0.9
+#MISSING: 0.0.9-3.4# 
(optional=templinst)_ZTv0_n16_NK5boost16exception_detail10clone_implINS0_19error_info_injectorINS_2io12too_few_args7rethrowEv@Base
 0.0.9
+#MISSING: 0.0.9-3.4# 
(optional=templinst)_ZTv0_n16_NK5boost16exception_detail10clone_implINS0_19error_info_injectorINS_2io13too_many_args7rethrowEv@Base
 0.0.9
+#MISSING: 0.0.9-3.4# 
(optional=templinst)_ZTv0_n16_NK5boost16exception_detail10clone_implINS0_19error_info_injectorINS_2io17bad_format_string7rethrowEv@Base
 0.0.9
+#MISSING: 0.0.9-3.4# 
(optional=templinst)_ZTv0_n20_N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_17bad_function_callD0Ev@Base
 0.0.9
+#MISSING: 0.0.9-3.4# 
(optional=templinst)_ZTv0_n20_N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_17bad_function_callD1Ev@Base
 0.0.9
+#MISSING: 0.0.9-3.4# 
(optional=templinst)_ZTv0_n20_N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_2io12too_few_argsD0Ev@Base
 0.0.9
+#MISSING: 0.0.9-3.4# 
(optional=templinst)_ZTv0_n20_N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_2io12too_few_argsD1Ev@Base
 0.0.9
+#MISSING: 0.0.9-3.4# 
(optional=templinst)_ZTv0_n20_N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_2io13too_many_argsD0Ev@Base
 0.0.9
+#MISSING: 0.0.9-3.4# 
(optional=templinst)_ZTv0_n20_N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_2io13too_many_argsD1Ev@Base
 0.0.9
+#MISSING: 0.0.9-3.4# 
(optional=templinst)_ZTv0_n20_N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_2io17bad_format_stringD0Ev@Base
 0.0.9
+#MISSING: 0.0.9-3.4# 
(optional=templinst)_ZTv0_n20_N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_2io17bad_format_stringD1Ev@Base
 0.0.9
  
(optional=templinst)_ZTv0_n24_NK5boost16exception_detail10clone_implINS0_19error_info_injectorINS_17bad_function_call5cloneEv@Base
 0.0.9
  
(optional=templinst)_ZTv0_n24_NK5boost16exception_detail10clone_implINS0_19error_info_injectorINS_2io12too_few_args5cloneEv@Base
 0.0.9
  
(optional=templinst)_ZTv0_n24_NK5boost16exception_detail10clone_implINS0_19error_info_injectorINS_2io13too_many_args5cloneEv@Base
 0.0.9
@@ -907,19 +911,19 @@
  
(optional=templinst)_ZZN5boost9function1IPN7OpenRaw7RawFileEPNS1_2IO6StreamEE9assign_toINS_3_bi6bind_tIS3_PFS3_S6_ENS9_5list1INS_3argILi1EvT_E13stored_vtable@Base
 0.0.9
  
_ZZN7OpenRaw9Internals14RawFileFactory10extensionsEvE18rawExtensionsTable@Base 
0.0.9
  _ZZN7OpenRaw9Internals14RawFileFactory5tableEvE15rawFactoryTable@Base 0.0.9
- (c++|optional=templinst)"construction vtable for std::basic_ostream >-in-boost::io::basic_oaltstringstream, std::allocator >@Base" 0.0.9
+#MISSING: 0.0.9-3.4#

Processed: reassign to python-shogun, swig3.0 is now in unstable

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python-shogun
Bug #746893 [swig] python-shogun: ftbfs with GCC-4.9
Bug #750621 [swig] swig3.0 required
Bug reassigned from package 'swig' to 'python-shogun'.
Bug reassigned from package 'swig' to 'python-shogun'.
No longer marked as found in versions swig2.0/2.0.7-3.
No longer marked as found in versions swig2.0/2.0.7-3.
Ignoring request to alter fixed versions of bug #746893 to the same values 
previously set
Ignoring request to alter fixed versions of bug #750621 to the same values 
previously set

-- 
746893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746893
750621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750621
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#746893: reassign to python-shogun, swig3.0 is now in unstable

[Matthias Klose]

Control: reassign -1 python-shogun

please update the packaging to use swig3.0.


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

Bug#731685: marked as done (ocaml-sqlexpr: FTBFS with ocaml 4.01.0)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 12:32:05 +0200
with message-id <2784ffacaf126adc63b6105bd1361...@dogguy.org>
and subject line Re: Bug#731685: ocaml-sqlexpr: FTBFS with ocaml 4.01.0
has caused the Debian Bug report #731685,
regarding ocaml-sqlexpr: FTBFS with ocaml 4.01.0
to be marked as done.

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

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


-- 
731685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocaml-sqlexpr
Version: 0.4.1-2
Severity: serious
Tags: jessie sid
Control: block 718767 with -1

Hi,

ocaml-sqlexpr FTBFS when binNMUed against ocaml 4.01.0.

From the amd64 build log:
> ocamlfind ocamldoc -dump sqlexpr_sqlite.odoc -package unix -package threads 
> -package sqlite3 -package lwt.unix -package lwt.syntax -package lwt -package 
> estring -package csv -package camlp4.quotations.r -package camlp4.lib 
> -package batteries sqlexpr_sqlite.mli
> + ocamlfind ocamldoc -dump sqlexpr_sqlite.odoc -package unix -package threads 
> -package sqlite3 -package lwt.unix -package lwt.syntax -package lwt -package 
> estring -package csv -package camlp4.quotations.r -package camlp4.lib 
> -package batteries sqlexpr_sqlite.mli
> ocamlfind: [WARNING] Package `threads' signals error: Missing -thread or 
> -vmthread switch
> ocamlfind ocamldoc -dump sqlexpr_sqlite_lwt.odoc -package unix -package 
> threads -package sqlite3 -package lwt.unix -package lwt.syntax -package lwt 
> -package estring -package csv -package camlp4.quotations.r -package 
> camlp4.lib -package batteries sqlexpr_sqlite_lwt.mli
> + ocamlfind ocamldoc -dump sqlexpr_sqlite_lwt.odoc -package unix -package 
> threads -package sqlite3 -package lwt.unix -package lwt.syntax -package lwt 
> -package estring -package csv -package camlp4.quotations.r -package 
> camlp4.lib -package batteries sqlexpr_sqlite_lwt.mli
> ocamlfind: [WARNING] Package `threads' signals error: Missing -thread or 
> -vmthread switch
> Warning: Module or module type Sqlexpr_sqlite.S not found
> Warning: Element Sqlexpr_sqlite.S not found
> rm -rf sqlexpr.docdir
> mkdir -p sqlexpr.docdir
> ocamlfind ocamldoc -load sqlexpr_concurrency.odoc -load sqlexpr_sqlite.odoc 
> -load sqlexpr_sqlite_lwt.odoc -html -d sqlexpr.docdir
> E: Malformed log file '/«PKGBUILDDIR»/setup.log' at line 1
> make[1]: *** [override_dh_auto_build] Error 1
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> make: *** [build-arch] Error 2

Full build logs available via:

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

Cheers,

-- 
Stéphane
--- End Message ---
--- Begin Message ---

Version: 0.5.5-2

This issue looks fixed in 0.5.5-2.

Le 2013-12-08 13:04, Stéphane Glondu a écrit :

Source: ocaml-sqlexpr
Version: 0.4.1-2
Severity: serious
Tags: jessie sid
Control: block 718767 with -1

Hi,

ocaml-sqlexpr FTBFS when binNMUed against ocaml 4.01.0.

From the amd64 build log:
ocamlfind ocamldoc -dump sqlexpr_sqlite.odoc -package unix -package 
threads -package sqlite3 -package lwt.unix -package lwt.syntax 
-package lwt -package estring -package csv -package 
camlp4.quotations.r -package camlp4.lib -package batteries 
sqlexpr_sqlite.mli
+ ocamlfind ocamldoc -dump sqlexpr_sqlite.odoc -package unix -package 
threads -package sqlite3 -package lwt.unix -package lwt.syntax 
-package lwt -package estring -package csv -package 
camlp4.quotations.r -package camlp4.lib -package batteries 
sqlexpr_sqlite.mli
ocamlfind: [WARNING] Package `threads' signals error: Missing -thread 
or -vmthread switch
ocamlfind ocamldoc -dump sqlexpr_sqlite_lwt.odoc -package unix 
-package threads -package sqlite3 -package lwt.unix -package 
lwt.syntax -package lwt -package estring -package csv -package 
camlp4.quotations.r -package camlp4.lib -package batteries 
sqlexpr_sqlite_lwt.mli
+ ocamlfind ocamldoc -dump sqlexpr_sqlite_lwt.odoc -package unix 
-package threads -package sqlite3 -package lwt.unix -package 
lwt.syntax -package lwt -package estring -package csv -package 
camlp4.quotations.r -package camlp4.lib -package batteries 
sqlexpr_sqlite_lwt.mli
ocamlfind: [WARNING] Package `threads' signals error: Missing -thread 
or -vmthread switch

Warning: Module or module type Sqlexpr_sqlite.S not found
Warning: Element Sqlexpr_sqlite.S not found
rm -rf sqlexpr.docdir
mkdir -p sqlexpr.docdir
ocamlfind ocamldoc -load sqlexpr_concurrency.odoc -load 
sqlexpr_sqlite.odoc -load sqlexpr_sqlite_lwt.odoc -html -d 
sqlexpr.docdir

E: Malformed log file '/«PKGBUILDDIR»/setup.log' at line 1
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory `/«PKGBUILDDIR»'
make

Bug#752351: marked as done (pdl: hardcodes /usr/lib/perl5)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 10:24:40 +
with message-id 
and subject line Bug#752351: fixed in pdl 1:2.007-2.1
has caused the Debian Bug report #752351,
regarding pdl: hardcodes /usr/lib/perl5
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.)


-- 
752351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pdl
Version: 1:2.007-2
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition

Starting with version 5.20.0 (currently in experimental), the Debian
perl package is changing the "vendorarch" library path (currently
/usr/lib/perl5) to include the multiarch triplet and the perl version. See
#748380 for details.

For this to work, packages containing binary perl modules need to migrate
from using the hardcoded /usr/lib/perl5 directory to the value of the
$Config{vendorarch} variable, as defined in the 'Config' module.

This package builds successfully with perl_5.20.0-1 from experimental,
but still installs the Perl files into /usr/lib/perl5 so they won't be
on the Perl search path anymore.

Please ask on the debian-perl list if you want help with this.

drwxr-xr-x root/root 0 2014-06-17 14:19 ./usr/lib/perl5/
drwxr-xr-x root/root 0 2014-06-17 14:19 ./usr/lib/perl5/PDL/
drwxr-xr-x root/root 0 2014-06-17 14:19 ./usr/lib/perl5/PDL/Doc/
-rw-r--r-- root/root  8640 2013-05-12 23:09 
./usr/lib/perl5/PDL/Doc/mkhtmldoc.pl
-rw-r--r-- root/root  2770 2014-06-17 14:11 
./usr/lib/perl5/PDL/Doc/scantree.pl

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: pdl
Source-Version: 1:2.007-2.1

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated pdl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Aug 2014 07:54:19 +
Source: pdl
Binary: pdl
Architecture: source amd64
Version: 1:2.007-2.1
Distribution: unstable
Urgency: medium
Maintainer: Henning Glawe 
Changed-By: Damyan Ivanov 
Description:
 pdl- perl data language: Perl extensions for numerics
Closes: 752351
Changes:
 pdl (1:2.007-2.1) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * Non-maintainer upload.
   * Fix "hardcodes /usr/lib/perl5":
 - rename files in debian/ which contain "/usr/lib/perl5" to .in, replace
   "/usr/lib/perl5" with a variable
 - create original files from debian/rules, replacing the variable with
   the current value of $Config{vendorarch}
 (Closes: #752351)
Checksums-Sha1:
 9d4843a8bfb55ba3fafbe7a2710a0d8f0f8fc200 2060 pdl_2.007-2.1.dsc
 b13a353c66256b0436ee36213d725286634f6315 24020 pdl_2.007-2.1.debian.tar.xz
 81569e739c4c62359c7623cee83861025d2e6bf1 3931660 pdl_2.007-2.1_amd64.deb
Checksums-Sha256:
 d7f0c5071c1bad24bc83270976e3f580518edfd536e56c612bb7231522fee3dd 2060 
pdl_2.007-2.1.dsc
 e8fc0ea2390cd8794f48c4bd4680ed0cdfd13245e218238cbebb107cd575108b 24020 
pdl_2.007-2.1.debian.tar.xz
 8aaa8c2e3b190dd1cb8190d4b0f21dd513d6e19ef1a75c7dde002c5891108d76 3931660 
pdl_2.007-2.1_amd64.deb
Files:
 f261a53a21931f3b9ee951ddb8d59683 3931660 math optional pdl_2.007-2.1_amd64.deb
 52d21c33c7226078ddce8042773fe817 2060 math optional pdl_2.007-2.1.dsc
 8475e1cd86229aec33cde1821fa74aca 24020 math optional 
pdl_2.007-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJT31mhAAoJENu+nU2Z0qAETLMP+wWRQoFqzHavsytBrEzmm+gq
nIXpTGutabz1Udn77a/wL+81nBDPkj/dEsULSw5m8DWiHma05ZGwGobNSOJr760Z
9CNgUXk6IYO8ZRA1Ko0VItUjVo5prdlx3SaOY9zqXdH8sYKea1T6FeSRw1xhAQnS
x8aSRRNF27qMN5/Q7QcmG8HldVsN7VdZT5AoQmNvPCQnYyNsm7v8dSSwm+nj/5OX
2Wy0RgD5K4Pl8f8T1OZ+TsC7PyLWjRJ/WlK+LAyKpiVfwghMMXoOPodzzoagPXbr
pWmTeAKEyaTpQ/yVtDHv9E+dU7q9ErZ4pFbC/yMq+UJZYkgH/deQXXdOGLZqMufy
0AJ4/1BngF17dv5QM+JCTJ/fL9bZp1BHnZPLCtyxUStHIWmEXEWm0TfUfEX3gnLg
H9UYMuxAM5Nv98l4GzsFoNaDsLgxem9oy590G7A38WCjjt5irgdcSXcbOwPHNIkF
XkeufVIItMN+lHpnneiS9BGBrneOLLRft6Hi8Rqtc4mMoybzjcfz39gkNtjJq3vy
xWP7qvMCSUz4xID7T0jED+BdJblDE

Bug#735827: marked as done (python-wstools: FTBFS: ImportError: No module named setuptools)

[Debian Bug Tracking System]

Your message dated Sat, 09 Aug 2014 10:24:52 +
with message-id 
and subject line Bug#735827: fixed in python-wstools 0.4.3-1.1
has caused the Debian Bug report #735827,
regarding python-wstools: FTBFS: ImportError: No module named setuptools
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.)


-- 
735827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-wstools
Version: 0.4.3-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140114 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):
>  fakeroot debian/rules clean
> dh clean --with python2
>dh_testdir
>dh_auto_clean
> pyversions: missing X(S)-Python-Version in control file, fall back to 
> debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
> Traceback (most recent call last):
>   File "setup.py", line 5, in 
> from setuptools import setup, find_packages
> ImportError: No module named setuptools
> dh_auto_clean: python setup.py clean -a returned exit code 1
> make: *** [clean] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/01/14/python-wstools_0.4.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.
--- End Message ---
--- Begin Message ---
Source: python-wstools
Source-Version: 0.4.3-1.1

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated python-wstools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 28 Jan 2014 21:14:11 +0600
Source: python-wstools
Binary: python-wstools
Architecture: source all
Version: 0.4.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Cyril Bouthors 
Changed-By: Andrey Rahmatullin 
Description:
 python-wstools - WSDL parsing services package for Web Services
Closes: 735827
Changes:
 python-wstools (0.4.3-1.1) unstable; urgency=medium
 .
   [ Andrey Rahmatullin ]
   * Non-maintainer upload.
   * Add Build-Depends: python-setuptools (Closes: #735827)
Checksums-Sha1:
 bdc89a90c05bffdef145c5aac23625430e5d1d78 1834 python-wstools_0.4.3-1.1.dsc
 a2adda72de0936b900aad3420eac638754dc7009 2216 
python-wstools_0.4.3-1.1.debian.tar.xz
 5bf527bd737e4bf198e65012d6ec2db8ccc0dea7 140354 
python-wstools_0.4.3-1.1_all.deb
Checksums-Sha256:
 71f94b54366adb05cca387f0372c5352f801b7c0cc272fec7b1f01fec4051a07 1834 
python-wstools_0.4.3-1.1.dsc
 11b6f6dbfe9ded212fc447e25f9efef72857ed1190bfbdfd2935483f49a963a7 2216 
python-wstools_0.4.3-1.1.debian.tar.xz
 aa72896179df6ede27f2115177186d5c3df36b23c1332b23f571beae4722fceb 140354 
python-wstools_0.4.3-1.1_all.deb
Files:
 39d3c2b0ead9cf6f613a8ad74eb24c0d 140354 python optional 
python-wstools_0.4.3-1.1_all.deb
 431f5d1f73f8c5db288389703e08315d 1834 python optional 
python-wstools_0.4.3-1.1.dsc
 21d9b74397da9f719306da14f6a48c92 2216 python optional 
python-wstools_0.4.3-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJT5fQsAAoJEOs2Fxpv+UNfqGQP/2Z15VLEUbSrq/4jeMiL+mmM
IuXfK+sWDsV2W0T9vscORbKXDG7sP0Vt7cq0+fFLJLrfJElZ8cAacreL4100AFTj
nbF5wx0Hvwl0icu+qBqGeCPnVHIsWjUmpaZuzf9UlvezcjfLxzWJCVD9PcDYcM5G
7RbHRa87nE6F3KuTPC9D7XfitNm3ffuoajDUaespVILBcYtkeWOAOPgtdgsFlBLb
Uo5eEz+E1IZ7F09loII28+Omaua7WR3NAsVx9md1sbf3xEt4Qeki3zXFNpgebFyt
s8+mtCeOZH3EsB2aFdsjPq0PuWWz/Yvfz116J8R7o4cWytX1gWSKtWzOpbBulJXO
tnpJDB6OJAT4EkEEMLninZgwk8E5PZHSeBuq6EkE5jHh4gUvWin+ph8ilAEqRgvN
AMl7ymLRCHNniVnZIA4VyS65VfOi4cUBHeyL3k2XF1iIOKyoAS73qzm0WYzR7qf5
4ePLn5x65h9avsbgrbZTlAI78R/OnUkbyYl1dgLxHlYDNg

Bug#747270: [Python-modules-team] Bug#747270: python-librabbitmq

[Michael Fladischer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Brian May wrote on 2014-08-09 10:28:
> So it makes sense not to use it, but I don't see any justification
> for repackaging the orig.tar.gz file.
> 
> Did I miss something?

The idea was to save archive space by not shipping duplicated code in
the source package.

If you think that it's better to leave the upstream tarball untouched,
feel free to drop this one line from d/copyright.

Cheers,
- -- 
Michael Fladischer
Fladi.at
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJT5fVvAAoJEGlMre9Rx7W2b/MP/jicM+tbBBVoCKYHs8k+WGmR
nESmJVvry0aa2k3dhOjAQl3myggXeeK7MhYR95HcAb9C2ll++DEpwvDZGZbgq36K
+TibVvScgawVA1/Z0rNm7INeCrfK7dK8qzXPEBBvIsVt9ivDaSSNSWRD5XB4mnCv
JhQV8DdPVJ8z5o37L+DbFdGV9RPfrIIdIgXGdfkJExK7cGYDLiKBatDt68ppXQK3
JIkx5scYHEFtxQIYHbi5sCn4zRD2Ea3KJ/1fl+cOBEAsqfgPUyMXW9+4mxvBsPSt
7i5eifDKmdaWfVMKRJc51jBkjtjb6qTpseDeiwrm5L39WIDc6WtKjEb9GUb91YRJ
rY5plpLH4pm3//WgtwiTKUmd0itNiruLrdSCkKpkkWBxijwmr+xNYwa+TboguhD2
4nRHK/17XP9qqvUPmoRSgL1exDMnxtzH1Q2Vtne9VeG06SpIO6lXgBoyiaBMNT3m
U1y5XoFMg8IC1o/uBd9rYuA+e8mzP4Qj/hJCJfHmlu4umQaQo2oXwa+HgfDxtLC+
GhMHB5+UnLl0cnuM4VAE1unmUkVZ9LKciaBJM/LCxmWIIL2HoJfsu4HdhJvaujtP
1/1qX+dyv5VjTkSr00y6+YGyxVQ0g4HuUJ0aUQ6GO81MIPk23vf844/+5emODftu
3vwzlRiiaTv667hgFsrO
=1JYC
-END PGP SIGNATURE-


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