Bug#807805: vlc: Crash upon startup

2015-12-13 Thread Hormet Yiltiz
Package: vlc
Version: 2.2.1-5+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
   After a recent system upgrade in Debian Testing, `vlc` cannot start
   and crashes reporting:
   "QSystemTrayIcon::setVisible: No Icon set"
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   This is reproducable in my environment. I am running i3wm installed
   alongside with KDE5. Reinstalling or reconfiguring `vlc` did not
   solve the issue.
   * What was the outcome of this action?
   VLC crash upon startup. 
   * What outcome did you expect instead?
   VLC starts normally.



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

Kernel: Linux 4.2.0-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
Init: systemd (via /run/systemd/system)

Versions of packages vlc depends on:
ii  fonts-freefont-ttf  20120503-4
ii  libaa1  1.4p5-44
ii  libavcodec-ffmpeg56 7:2.8.3-1
ii  libavutil-ffmpeg54  7:2.8.3-1
ii  libc6   2.19-22
ii  libcaca00.99.beta19-2+b1
ii  libcairo2   1.14.4-1
ii  libegl1-mesa [libegl1-x11]  11.0.6-1
ii  libfreerdp-client1.11.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreetype62.6.1-0.1
ii  libfribidi0 0.19.7-1
ii  libgcc1 1:5.2.1-23
ii  libgl1-mesa-glx [libgl1]11.0.6-1
ii  libgles1-mesa [libgles1]11.0.6-1
ii  libgles2-mesa [libgles2]11.0.6-1
ii  libglib2.0-02.46.2-1
ii  libpulse0   7.1-2
ii  libqt5core5a5.5.1+dfsg-8
ii  libqt5gui5  5.5.1+dfsg-8
ii  libqt5widgets5  5.5.1+dfsg-8
ii  libqt5x11extras55.5.1-3
ii  librsvg2-2  2.40.11-2
ii  libsdl-image1.2 1.2.12-5+b5
ii  libsdl1.2debian 1.2.15-12
ii  libstdc++6  5.2.1-23
ii  libva-drm1  1.6.1-1
ii  libva-x11-1 1.6.1-1
ii  libva1  1.6.1-1
ii  libvlccore8 2.2.1-5+b1
ii  libvncclient1   0.9.10+dfsg-3
ii  libx11-62:1.6.3-1
ii  libxcb-composite0   1.10-3+b1
ii  libxcb-keysyms1 0.4.0-1
ii  libxcb-randr0   1.10-3+b1
ii  libxcb-shm0 1.10-3+b1
ii  libxcb-xv0  1.10-3+b1
ii  libxcb1 1.10-3+b1
ii  libxext62:1.3.3-1
ii  libxi6  2:1.7.5-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.11-1+b1
ii  vlc-nox 2.2.1-5+b1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages vlc recommends:
ii  vlc-plugin-notify  2.2.1-5+b1
ii  vlc-plugin-samba   2.2.1-5+b1
ii  xdg-utils  1.1.1-1

vlc suggests no packages.

Versions of packages vlc-nox depends on:
ii  liba52-0.7.4   0.7.4-18
ii  libasound2 1.0.29-1
ii  libass50.13.0-1
ii  libavahi-client3   0.6.32~rc+dfsg-1
ii  libavahi-common3   0.6.32~rc+dfsg-1
ii  libavc1394-0   0.5.4-2
ii  libavcodec-ffmpeg567:2.8.3-1
ii  libavformat-ffmpeg56   7:2.8.3-1
ii  libavutil-ffmpeg54 7:2.8.3-1
ii  libbasicusageenvironment0  2014.01.13-1
ii  libbluray1 1:0.9.2-1
ii  libc6  2.19-22
ii  libcddb2   1.3.2-5
ii  libcdio13  0.83-4.2+b1
ii  libchromaprint01.2-1+b1
ii  libcrystalhd3  1:0.0~git20110715.fdd2f19-11+b1
ii  libdbus-1-31.10.4-1
ii  libdc1394-22   2.2.3-1
ii  libdca00.0.5-7
ii  libdirectfb-1.2-9  1.2.10.0-5.1
ii  libdvbpsi101.3.0-2
ii  libdvdnav4 5.0.3-1
ii  libdvdread45.0.3-1
ii  libebml4v5 1.3.3-1
ii  libfaad2   2.8.0~cvs20150510-1
ii  libflac8   1.3.1-4
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.6.1-0.1
ii  libfribidi00.19.7-1
ii  libgcc11:5.2.1-23
ii  libgcrypt201.6.4-3
ii  libgnutls-deb0-28  3.3.18-1
ii  libgpg-error0  1.20-1
ii  libgroupsock1  2014.01.13-1
ii  libjpeg62-turbo1:1.4.1-2
ii  libkate1   0.4.1-5
ii  liblircclient0 0.9.0~pre1-1.2
ii  liblivemedia23 2014.01.13-1
ii  

Bug#750904: Build on arm*

2015-12-13 Thread Patrick Winnertz
Hey George,

you can close that bug here, too ;) scidavis has successfully build on
arm*. I don't want to do it, because it's your package ;)

Greetings
Patrick



Bug#807502: gcc-avr: Missing support for atxmega

2015-12-13 Thread Hakan Ardo
Hi,
I've now uploaded a new version of avr-libc with the new names on those
files. I'll also update binutils to declear that it wont work with older
avr-libc.

On Fri, Dec 11, 2015 at 7:56 PM, Hakan Ardo  wrote:

> Hi,
> the file you want is crtx384d3.o and not crtatxmega384d3.o (even i the new
> avr-libc). Dont know why he's suddenly trying to use crtatxmega384d3.o
> instead, but the issue seems to be in binutils. I'm reassigning the bug
> there and will keep looking...
>
> On Fri, Dec 11, 2015 at 4:23 PM, Lisandro Damián Nicanor Pérez Meyer <
> perezme...@gmail.com> wrote:
>
>> On Friday 11 December 2015 16:15:52 Hakan Ardo wrote:
>> > Please do.
>>
>> Done, thanks!
>>
>> > It might be that we need to update avr-libc too? That work is in
>> > progress, but was delayed. Should be ready any day now...
>>
>> It might be, if so just ping me as soon as it's available in incoming.d.o
>> and
>> I'll happily give it a try.
>>
>> Thanks!
>>
>> --
>> The volume of a pizza of thickness a and radius z can be described by
>> the following formula:
>>
>> pi zz a
>>
>> Lisandro Damián Nicanor Pérez Meyer
>> http://perezmeyer.com.ar/
>> http://perezmeyer.blogspot.com/
>>
>
>
>
> --
> Håkan Ardö
>



-- 
Håkan Ardö


Bug#807502: marked as done (gcc-avr: Missing support for atxmega384d3 since last upload)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 09:52:17 +
with message-id 
and subject line Bug#807502: fixed in binutils-avr 2.25+Atmel3.5.0-2
has caused the Debian Bug report #807502,
regarding gcc-avr: Missing support for atxmega384d3 since last upload
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.)


-- 
807502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-avr
Version: 1:4.9.2+Atmel3.5.0-1
Severity: serious
Justification: Makes package unusable

Hi Hakan! After the latests update my AtXmega384d3-based project started to 
FTBFS:

avr-gcc -Isrc  -std=gnu99 -mmcu=atxmega384d3 -Wall -gdwarf-2 -O1 
-funsigned-char -MD -MP -MT settings_asm.o -MF dep/settings_asm.o.d -x 
assembler-with-cpp -Wa,-gdwarf2 -c src/settings_asm.S -o src/settings_asm.o
avr-gcc -mmcu=atxmega384d3 -Wl,--section-start=.BOOT=0x06 src/source1.o 
src/source2.o src/source3.o src/core.o src/source4.o [...] src/main.o src -o 
project.elf
/usr/lib/gcc/avr/4.9.2/../../../avr/bin/ld: cannot find crtatxmega384d3.o: No 
such file or directory
/usr/lib/gcc/avr/4.9.2/../../../avr/bin/ld: cannot find -latxmega384d3
collect2: error: ld returned 1 exit status
Makefile:91: recipe for target 'project.elf' failed
make: *** [project.elf] Error 1

Thanks for your work!

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

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

Versions of packages gcc-avr depends on:
ii  binutils-avr  2.25+Atmel3.5.0-1
ii  libc6 2.21-3
ii  libgmp10  2:6.1.0+dfsg-2
ii  libmpc3   1.0.3-1
ii  libmpfr4  3.1.3-1
ii  zlib1g1:1.2.8.dfsg-2+b1

gcc-avr recommends no packages.

Versions of packages gcc-avr suggests:
ii  avr-libc  1:1.8.0+Atmel3.4.5-1
ii  gcc   4:5.2.1-8
pn  gcc-doc   
pn  task-c-devel  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: binutils-avr
Source-Version: 2.25+Atmel3.5.0-2

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

Debian distribution maintenance software
pp.
Hakan Ardo  (supplier of updated binutils-avr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 13 Dec 2015 09:40:31 +0100
Source: binutils-avr
Binary: binutils-avr
Architecture: source amd64
Version: 2.25+Atmel3.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Hakan Ardo 
Changed-By: Hakan Ardo 
Description:
 binutils-avr - Binary utilities supporting Atmel's AVR targets
Closes: 807502
Changes:
 binutils-avr (2.25+Atmel3.5.0-2) unstable; urgency=medium
 .
   * Declear that we break older versions of avr-libc (closes: #807502)
Checksums-Sha1:
 26d2351a9ddf7955b081d9e08b5b7c0c3c31f5ba 1875 
binutils-avr_2.25+Atmel3.5.0-2.dsc
 208165bb42ef70ffe491ce80ad15c51e2c317215 780382 
binutils-avr_2.25+Atmel3.5.0-2.diff.gz
 2d05e687a1158729a97256046f69f9d1ca73af4c 1459328 
binutils-avr_2.25+Atmel3.5.0-2_amd64.deb
Checksums-Sha256:
 ba1cfbc6a22e9064a96064203d83281a0ca6d1b96ed8079188a914a82732249d 1875 
binutils-avr_2.25+Atmel3.5.0-2.dsc
 392a7bc466e072924bd1921959e88644ce2c6840ec83ba34fd41704064ce 780382 
binutils-avr_2.25+Atmel3.5.0-2.diff.gz
 014491aa76d8f3b502a455f17ac3fae199ca790a62f5a79ebe522868e0e708ba 1459328 
binutils-avr_2.25+Atmel3.5.0-2_amd64.deb
Files:
 45050484fff16f3713765435ae2e0ff1 1875 devel extra 
binutils-avr_2.25+Atmel3.5.0-2.dsc
 3d193c0e0558bebf724bc0b68b892167 780382 devel extra 
binutils-avr_2.25+Atmel3.5.0-2.diff.gz
 67bcdaf0c2e810a3a0c69a4099e50f56 1459328 devel extra 
binutils-avr_2.25+Atmel3.5.0-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1


Bug#807805: vlc: Crash upon startup

2015-12-13 Thread Hörmetjan Yiltiz
​I realized that vlc only crashes in my i3wm setup, but does not crash if
started from the KDE5 environment. ​


Bug#783108: marked as done (file: OOM and/or segfault)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 11:35:03 +0200
with message-id <20151213093503.GA24129@tunkki>
and subject line closing
has caused the Debian Bug report #783108,
regarding file: OOM and/or segfault
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.)


-- 
783108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Source: php5
Version: 5.6.7+dfsg-1
Severity: grave
Tags: security, upstream, fixed-upstream

Hi,

the following vulnerability was published for PHP5,

"""
When calling finfo::file() or finfo::buffer() with a crafted string, PHP will
crash by either segfaulting or trying to allocate an large amount of memory
(4GiB).

This was found in the wild when a user uploaded a file (running finfo on
arbitrary files uploaded by users is one of its main use cases.). I've since
anonymised the file, and made it more minimal. At this stage, very small changes
to the string make it produce different behaviour - removing the remaining 'a',
's', or 'y' characters, for instance, will allow finfo to process it fine.
"""

For further information see:
  https://bugs.php.net/bug.php?id=68819
  
https://git.php.net/?p=php-src.git;a=commitdiff;h=f938112c495b0d26572435c0be73ac0bfe642ecd

- -- 
Henri Salo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJVN11hAAoJECet96ROqnV0NFwP/1WyM6/jYhMkuyyjIDuGJLR6
5agci0HcM64R5It7Dvoy7HPtP431Qg5XvtJBn2P5YRq9Kgh1g0T7NeA4jbQIQEQs
lj/zO4zfBSnhCvkCbsqhLDYDASx1M2esXgfXy4EDejBPvVMSPtSr3GjVt9Ptufty
/GgA3FRf+XDDNNDebGsDVvkKH5pAvK7QN8R8UsmG8uiEYP9+vdlwdAK5pykrWsGa
yZEm7x/OXjETTnjIoz+0p89ExFBBuNyryhMQGVfiJxivTMHaHMBuZ/2BlBhIM0S2
VTf42JtlLTmG6NZW71OplY2kN1f+p+ADXy/OUtwbV700tuk58wIwt+r5Ymqa9wmA
crO2xyNm2CgA0K6Vew0vEYBWVc7fFQQuGhQX6lKOwng3OXaM3Xo9BzEvrOGVrTgz
sw7ilWb4kfUTjtZoAYVOqL0YTafMi3CzjmH3MzeFMyxMRtYlqgc7S+KrqJXWMX2A
TlqA2WhAOMIHNG8xxuXdwlzzVRoPakY0Jkgx5XdUlU9QdNmeIljcxdPAIXHAeEAj
IPSBQFUjAZABB7GWKgZcyJv6p2Z9nc5GkQ9RYm297QtGbPVYGUfmBZsJOloJfXIF
V4dRZWkVoonbaC5WtjaGPyOIHnl35AZ7Hl4MkQ5JMzScbN3u1BooY1+NXNBsHTPL
JLN2O58YQiTodP1AZWfx
=y0h8
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Hi,

I made the bug split, because in IRC conversation someone said that file should
be handled separately and I made the mistake not to make proper research before
creating new issue. For the current situation please see information from Debian
security tracker:

  https://security-tracker.debian.org/tracker/CVE-2015-4604
  https://security-tracker.debian.org/tracker/CVE-2015-4605

I am very sorry about the confusion and I will avoid it in the future as best as
I can.

-- 
Henri Salo--- End Message ---


Bug#805226: marked as done (praw: FTBFS: ImportError: No module named betamax)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 10:11:23 +
with message-id 
and subject line Bug#805226: fixed in praw 3.3.0-1
has caused the Debian Bug report #805226,
regarding praw: FTBFS: ImportError: No module named betamax
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.)


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

Dear Maintainer,

The package fails to build:


==
ERROR: tests.test_comments (unittest.loader.ModuleImportFailure)
--
ImportError: Failed to import test module: tests.test_comments
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
__import__(name)
  File "tests/test_comments.py", line 5, in 
import mock
ImportError: No module named mock


==
ERROR: tests.test_authenticated_reddit (unittest.loader.ModuleImportFailure)
--
ImportError: Failed to import test module: tests.test_authenticated_reddit
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
__import__(name)
  File "tests/test_authenticated_reddit.py", line 6, in 
from .helper import PRAWTest, betamax
  File "tests/helper.py", line 8, in 
from betamax import Betamax, BaseMatcher
ImportError: No module named betamax


--
Ran 14 tests in 0.001s

FAILED (errors=13)
E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: cd 
/praw-3.2.1/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover -v 
dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
code 13

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: praw
Source-Version: 3.3.0-1

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

Debian distribution maintenance software
pp.
Riley Baird  (supplier of 
updated praw package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 11 Oct 2015 15:47:27 +1100
Source: praw
Binary: python-praw python3-praw praw-doc
Architecture: source all
Version: 3.3.0-1
Distribution: unstable
Urgency: high
Maintainer: Riley Baird 
Changed-By: Riley Baird 
Description:
 praw-doc   - Python Reddit API Wrapper (Documentation)
 python-praw - Python Reddit API Wrapper (Python 2 version)
 python3-praw - Python Reddit API Wrapper (Python 3 version)
Closes: 805226
Changes:
 praw (3.3.0-1) unstable; urgency=high
 .
   * New upstream release
   * Removed debian/patches/change-info-section.patch, as the changes
 have been integrated upstream
   * Disabled tests (Closes: #805226)
Checksums-Sha1:
 a4c3be43e4895a96e324034aaa32362e97859879 2291 praw_3.3.0-1.dsc
 21dd7318219cb9e38b255962f164a8d1764f3ed7 1582359 praw_3.3.0.orig.tar.gz
 a02f3a258a8c60f77ae86c6a086a74d0dd5f8bc9 5076 praw_3.3.0-1.debian.tar.xz
 

Bug#807564: digikam: FTBFS, cannot find Marble

2015-12-13 Thread Danny Edel
Hello List,

I'm looking into this aswell, since I want to use digikam again and got
some free time to fix it.  I hope I can provide a source-patch in the
next few days that allows the currently packaged version of digikam to
build again.

In case I get it to work, where do I send the patch?  It would affect
both #807564 and #802966 since they both say FTBFS (although for
different reasons).

Cheers,

- Danny



Bug#807805: vlc: Crash upon startup

2015-12-13 Thread Hörmetjan Yiltiz
calling `vlc --no-qt-system-tray` will start vlc and is an effective
workaround.

Best,
Hörmet

He who is worthy to receive his days and nights is worthy to receive all
else from you (and me).
 -- The Prophet, Gibran
Kahlil


On Sun, Dec 13, 2015 at 3:58 AM, Hormet Yiltiz  wrote:

> Package: vlc
> Version: 2.2.1-5+b1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate
> ***
>
>* What led up to the situation?
>After a recent system upgrade in Debian Testing, `vlc` cannot start
>and crashes reporting:
>"QSystemTrayIcon::setVisible: No Icon set"
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>This is reproducable in my environment. I am running i3wm installed
>alongside with KDE5. Reinstalling or reconfiguring `vlc` did not
>solve the issue.
>* What was the outcome of this action?
>VLC crash upon startup.
>* What outcome did you expect instead?
>VLC starts normally.
>
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing-updates
>   APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'),
> (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.2.0-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
> Init: systemd (via /run/systemd/system)
>
> Versions of packages vlc depends on:
> ii  fonts-freefont-ttf  20120503-4
> ii  libaa1  1.4p5-44
> ii  libavcodec-ffmpeg56 7:2.8.3-1
> ii  libavutil-ffmpeg54  7:2.8.3-1
> ii  libc6   2.19-22
> ii  libcaca00.99.beta19-2+b1
> ii  libcairo2   1.14.4-1
> ii  libegl1-mesa [libegl1-x11]  11.0.6-1
> ii  libfreerdp-client1.11.1.0~git20140921.1.440916e+dfsg1-5+b1
> ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-5+b1
> ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-5+b1
> ii  libfreetype62.6.1-0.1
> ii  libfribidi0 0.19.7-1
> ii  libgcc1 1:5.2.1-23
> ii  libgl1-mesa-glx [libgl1]11.0.6-1
> ii  libgles1-mesa [libgles1]11.0.6-1
> ii  libgles2-mesa [libgles2]11.0.6-1
> ii  libglib2.0-02.46.2-1
> ii  libpulse0   7.1-2
> ii  libqt5core5a5.5.1+dfsg-8
> ii  libqt5gui5  5.5.1+dfsg-8
> ii  libqt5widgets5  5.5.1+dfsg-8
> ii  libqt5x11extras55.5.1-3
> ii  librsvg2-2  2.40.11-2
> ii  libsdl-image1.2 1.2.12-5+b5
> ii  libsdl1.2debian 1.2.15-12
> ii  libstdc++6  5.2.1-23
> ii  libva-drm1  1.6.1-1
> ii  libva-x11-1 1.6.1-1
> ii  libva1  1.6.1-1
> ii  libvlccore8 2.2.1-5+b1
> ii  libvncclient1   0.9.10+dfsg-3
> ii  libx11-62:1.6.3-1
> ii  libxcb-composite0   1.10-3+b1
> ii  libxcb-keysyms1 0.4.0-1
> ii  libxcb-randr0   1.10-3+b1
> ii  libxcb-shm0 1.10-3+b1
> ii  libxcb-xv0  1.10-3+b1
> ii  libxcb1 1.10-3+b1
> ii  libxext62:1.3.3-1
> ii  libxi6  2:1.7.5-1
> ii  libxinerama12:1.1.3-1+b1
> ii  libxpm4 1:3.5.11-1+b1
> ii  vlc-nox 2.2.1-5+b1
> ii  zlib1g  1:1.2.8.dfsg-2+b1
>
> Versions of packages vlc recommends:
> ii  vlc-plugin-notify  2.2.1-5+b1
> ii  vlc-plugin-samba   2.2.1-5+b1
> ii  xdg-utils  1.1.1-1
>
> vlc suggests no packages.
>
> Versions of packages vlc-nox depends on:
> ii  liba52-0.7.4   0.7.4-18
> ii  libasound2 1.0.29-1
> ii  libass50.13.0-1
> ii  libavahi-client3   0.6.32~rc+dfsg-1
> ii  libavahi-common3   0.6.32~rc+dfsg-1
> ii  libavc1394-0   0.5.4-2
> ii  libavcodec-ffmpeg567:2.8.3-1
> ii  libavformat-ffmpeg56   7:2.8.3-1
> ii  libavutil-ffmpeg54 7:2.8.3-1
> ii  libbasicusageenvironment0  2014.01.13-1
> ii  libbluray1 1:0.9.2-1
> ii  libc6  2.19-22
> ii  libcddb2   1.3.2-5
> ii  libcdio13  0.83-4.2+b1
> ii  libchromaprint01.2-1+b1
> ii  libcrystalhd3  1:0.0~git20110715.fdd2f19-11+b1
> ii  libdbus-1-31.10.4-1
> ii  libdc1394-22   2.2.3-1
> ii  libdca00.0.5-7
> ii  libdirectfb-1.2-9  1.2.10.0-5.1
> ii  libdvbpsi101.3.0-2
> ii  libdvdnav4 5.0.3-1
> ii  libdvdread45.0.3-1
> ii  libebml4v5 1.3.3-1
> ii 

Processed: Re: Bug#807805: vlc: Crash upon startup

2015-12-13 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #807805 [vlc] vlc: Crash upon startup
Severity set to 'important' from 'grave'
> tags -1 + moreinfo
Bug #807805 [vlc] vlc: Crash upon startup
Added tag(s) moreinfo.

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



Bug#807805: vlc: Crash upon startup

2015-12-13 Thread Sebastian Ramacher
Control: severity -1 important
Control: tags -1 + moreinfo

On 2015-12-13 03:58:37, Hormet Yiltiz wrote:
> Package: vlc
> Version: 2.2.1-5+b1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
>After a recent system upgrade in Debian Testing, `vlc` cannot start
>and crashes reporting:
>"QSystemTrayIcon::setVisible: No Icon set"
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>This is reproducable in my environment. I am running i3wm installed
>alongside with KDE5. Reinstalling or reconfiguring `vlc` did not
>solve the issue.
>* What was the outcome of this action?
>VLC crash upon startup. 
>* What outcome did you expect instead?
>VLC starts normally.

Please install vlc-dbg and qtbase5-dbg and provide a full backtrace.

On 2015-12-13 06:07:25, Hörmetjan Yiltiz wrote:
> calling `vlc --no-qt-system-tray` will start vlc and is an effective
> workaround.

...

> I realized that vlc only crashes in my i3wm setup, but does not crash if
> started from the KDE5 environment.

Downgrading accordingly.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Processed: severity of 807128 is normal, severity of 807867 is normal, tagging 798749, tagging 801851 ...

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 807128 normal
Bug #807128 {Done: Emilio Pozuelo Monfort } 
[release.debian.org] nmu: gcc-5_5.3.0-3
Severity set to 'normal' from 'serious'
> severity 807867 normal
Bug #807867 [release.debian.org] nmu: all packages built without GCC 5 and 
hardening-wrapper
Severity set to 'normal' from 'grave'
> tags 798749 - moreinfo
Bug #798749 [release.debian.org] pu: package monit/1:5.9-1+jessie1
Removed tag(s) moreinfo.
> tags 801851 - moreinfo
Bug #801851 [release.debian.org] jessie-pu: package 
multipath-tools/0.5.0-6+deb8u1
Removed tag(s) moreinfo.
> tags 803362 - moreinfo
Bug #803362 [release.debian.org] jessie-pu: package exfat-utils/1.1.0-2+deb8u1
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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



Processed: severity of 805817 is normal

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 805817 normal
Bug #805817 [ftp.debian.org] RM: instanbul - dead upstream, depends on 
gstreamer 0.10
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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



Bug#784382: marked as done (ugene: Harcodes dependencies on transitional packages)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Dec 2015 05:22:41 +
with message-id 
and subject line Bug#784382: fixed in ugene 1.19.0+dfsg-1
has caused the Debian Bug report #784382,
regarding ugene: Harcodes dependencies on transitional packages
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.)


-- 
784382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ugene
Version: 1.12.3+dfsg-1
Severity: important

Hi! Ugene harcodes dependencies on libqt4-core and libqt4-gui. Neither of this
packages should be really listed here, that's ${shlibs:Depends}'s job.

I'm going to upload Qt4 without these transitional package spossibly next week.
I'll rise the severity of this bug first to serious, of course.

Kinds regards, Lisandro.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: ugene
Source-Version: 1.19.0+dfsg-1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Dec 2015 21:05:12 +0100
Source: ugene
Binary: ugene ugene-data
Architecture: source all amd64
Version: 1.19.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 ugene  - integrated bioinformatics toolkit
 ugene-data - required data for UGENE - integrated bioinformatics toolkit
Closes: 784382 784534 785035
Changes:
 ugene (1.19.0+dfsg-1) unstable; urgency=medium
 .
   [Andreas Tille]
   * New upstream version
 Closes: #785035, #784534
   * Remove non necessary harcoded dependencies on transitional
 packages (Thanks to Lisandro Damián Nicanor Pérez Meyer for the
 patch)
 Closes: #784382
   * Moved packaging from SVN to Git
   * cme fix dpkg-control
   * override false lintian positives (package-contains-timestamped-gzip)
   * DEP5 fixes
 .
   [Gert Wollny]
   * Update to build with QT5 (thanks to Gianfranco Costamagna for the initial
 transition and pointing out some quirks)
   * update d/p/use_system_sqlite.patch
Checksums-Sha1:
 4975998703bfab2b49f9e484e8feb5bf94ac4086 2312 ugene_1.19.0+dfsg-1.dsc
 920819fdbdf2456c894d490635aa013a671dae8d 15735752 ugene_1.19.0+dfsg.orig.tar.xz
 089fd6e8e0f0f13c919d764bf0667b99d791326b 11140 
ugene_1.19.0+dfsg-1.debian.tar.xz
 d6b109d77168ea84ec25d291996061a8f73573f7 6446556 
ugene-data_1.19.0+dfsg-1_all.deb
 83c0b0f4ef407cb90e90c055d7c8bda9b4d28823 22678710 ugene_1.19.0+dfsg-1_amd64.deb
Checksums-Sha256:
 d6631834a131d049803077fa53be4e41090279c33319c96e94c141cc780ca2eb 2312 
ugene_1.19.0+dfsg-1.dsc
 9416bce3ff713fe5d8aedbceb56a7fb2ca1af22dff1fb6f27d8d94729f84c7c6 15735752 
ugene_1.19.0+dfsg.orig.tar.xz
 a1924f74cbd7e76d6c662b05afc3b0a8656a371ee071d8557240651a9fd926be 11140 
ugene_1.19.0+dfsg-1.debian.tar.xz
 1558693e6655a6adc72e21e521f2d0fd52013c481a814c4757ced7be04773795 6446556 
ugene-data_1.19.0+dfsg-1_all.deb
 5f2fc54ffc8c9ff6428946ab42f3ef0ce944f6f4818a045a7cff7e98f003b428 22678710 
ugene_1.19.0+dfsg-1_amd64.deb
Files:
 d4abd226d57140604e137404940b42dc 2312 non-free/science optional 
ugene_1.19.0+dfsg-1.dsc
 2e37f2be55a3491aa4821230a45acac4 15735752 non-free/science optional 
ugene_1.19.0+dfsg.orig.tar.xz
 30357e9807a260f668c1342e4d2cc256 11140 non-free/science optional 
ugene_1.19.0+dfsg-1.debian.tar.xz
 0931980ab3ac68e2c26dd9ebe2a44fc8 6446556 non-free/science optional 
ugene-data_1.19.0+dfsg-1_all.deb
 fa449440d6021f005d0b26dce5a84870 22678710 non-free/science optional 
ugene_1.19.0+dfsg-1_amd64.deb

-BEGIN PGP 

Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

2015-12-13 Thread Andreas Metzler
On 2015-12-12 Russ Allbery  wrote:
[...]
> > when starting gnubg it uses 100% of one cpu core and then apparently
> > hangs with no output and without starting the gui.

> So, I'm not sure what's going on here, but it seems to be some sort of
> weird bug in libgnutls/libtasn1.  gnubg is going into an infinite loop
> before any gnubg code actually runs at all, during shared library
> initialization.  This is the backtrace of the infinite loop:
[...]

Some more points of strangeness:
jessie's gnubg package (1.04.000-1) works on current stretch.
Rebuilding the jessie source on current sid produces a binary which
fails.
Rebuilding with DEB_BUILD_OPTIONS=noopt works
Rebuilding on current sid with gcc-4.9 produces a working package.
Rebuilding either the jessie or the sid source with -O1 segfaults at
start:
(gdb) run
Starting program: /usr/games/gnubg
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
memcpy (__dest=0x833070,
__dest@entry=, __src=0x7fffea09a46e,
__src@entry=, __len=6,
__len@entry=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53
53


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



Bug#803300: prepare for giflib5

2015-12-13 Thread Sebastiaan Couwenberg
On Wed, 28 Oct 2015 16:02:40 +0100 Matthias Klose wrote:
> For the latter two options, please see a patch at
> http://launchpadlibrarian.net/222944251/openscenegraph_3.2.1-7ubuntu2_3.2.1-7ubuntu3.diff.gz

Upstream has fixed the giflib5 support a bit differently [0][1].

The attached debdiff uses the upstream changes for giflib 5.x instead of
those applied in Ubuntu.

Please include these changes in openscenegraph (3.2.1-9) to prevent
testing autoremoval of openscenegraph and all its reverse dependencies
because of this RC bug.

[0]
https://github.com/openscenegraph/osg/commit/afb442fccd182cfe8608f43394af016f6723f97a
[1]
https://github.com/openscenegraph/osg/commit/18213bfb67d464715af618fd8c73549f749625b9

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
diff --git a/debian/changelog b/debian/changelog
index 1cef1f3..1e021e4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+openscenegraph (3.2.1-8.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch for giflib 5 support.
+(closes: #803300)
+
+ -- Bas Couwenberg   Sun, 13 Dec 2015 16:24:35 +0100
+
 openscenegraph (3.2.1-8) unstable; urgency=medium
 
   * Adding upstream patch for GDAL 2.0 support, needed by upcoming
diff --git a/debian/patches/giflib5.patch b/debian/patches/giflib5.patch
new file mode 100644
index 000..166c724
--- /dev/null
+++ b/debian/patches/giflib5.patch
@@ -0,0 +1,20 @@
+Description: Add support for giflib 5.
+Origin: 
https://github.com/openscenegraph/osg/commit/afb442fccd182cfe8608f43394af016f6723f97a
+
https://github.com/openscenegraph/osg/commit/18213bfb67d464715af618fd8c73549f749625b9
+Bug-Debian: https://bugs.debian.org/803300
+Forwarded: not-needed
+
+--- a/OpenSceneGraph/src/osgPlugins/gif/ReaderWriterGIF.cpp
 b/OpenSceneGraph/src/osgPlugins/gif/ReaderWriterGIF.cpp
+@@ -561,7 +561,11 @@ GifImageStream** obj)
+ *width_ret = giffile->SWidth;
+ *height_ret = giffile->SHeight;
+ *numComponents_ret = 4;
++#if (GIFLIB_MAJOR >= 5&& !(GIFLIB_MAJOR == 5 && GIFLIB_MINOR == 0))
++DGifCloseFile(giffile, );
++#else
+ DGifCloseFile(giffile);
++#endif
+ return buffer;
+ }
+ 
diff --git a/debian/patches/series b/debian/patches/series
index f0c725b..27f5e1d 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -5,3 +5,4 @@ bug763818_fix_preprocessor_double_substitution
 bug765855_removecallback_use_after_free
 gdal-2.0.patch
 no-xine-malloc-aligned.diff
+giflib5.patch


Bug#807250: marked as done (fretsonfire-game: Game fail to start: obsolete function called)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 16:51:55 +
with message-id 
and subject line Bug#807250: fixed in fretsonfire 1.3.110.dfsg2-2
has caused the Debian Bug report #807250,
regarding fretsonfire-game: Game fail to start: obsolete function called
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.)


-- 
807250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fretsonfire-game
Version: 1.3.110.dfsg2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Game fail to start with this output:

Traceback (most recent call last):
  File "./FretsOnFire.py", line 74, in 
  engine = GameEngine(config)
  File "/usr/share/games/fretsonfire/game/GameEngine.py", line 194, in __init__
  self.data = Data(self.resource, self.svg)
  File "/usr/share/games/fretsonfire/game/Data.py", line 48, in __init__
  self.loadSvgDrawing(self, "star1",   "star1.svg", textureSize = (128, 
128))
  File "/usr/share/games/fretsonfire/game/Data.py", line 106, in loadSvgDrawing
  drawing  = self.resource.load(target, name, lambda: SvgDrawing(self.svg, 
fileName), synch = True)
  File "/usr/share/games/fretsonfire/game/Resource.py", line 157, in load
  return l.finish()
  File "/usr/share/games/fretsonfire/game/Resource.py", line 68, in load
  self.result = self.function()
  File "/usr/share/games/fretsonfire/game/Data.py", line 106, in 
  drawing  = self.resource.load(target, name, lambda: SvgDrawing(self.svg, 
fileName), synch = True)
  File "/usr/share/games/fretsonfire/game/Svg.py", line 552, in __init__
  self.texture = Texture(bitmapFile)
  File "/usr/share/games/fretsonfire/game/Texture.py", line 202, in __init__
  self.loadFile(name)
  File "/usr/share/games/fretsonfire/game/Texture.py", line 206, in loadFile
  self.loadImage(Image.open(name))
  File "/usr/share/games/fretsonfire/game/Texture.py", line 213, in loadImage
  string = image.tostring('raw', 'RGBA', 0, -1)
  File "/usr/lib/python2.7/dist-packages/PIL/Image.py", line 686, in tostring
  "Please call tobytes() instead.")
Exception: tostring() has been removed. Please call tobytes() instead.

Replacing 'tostring' with 'tobytes' in function loadImage in Texture.py solves 
the problem.

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

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

Versions of packages fretsonfire-game depends on:
ii  fonts-mgopen 1.1-9
ii  python   2.7.9-1
ii  python-imaging   3.0.0-1
ii  python-ogg   1.3+repack-7
ii  python-opengl3.0.2-1
ii  python-pygame1.9.1release+dfsg-10+b1
ii  python-pyvorbis  1.5-4
ii  ttf-dejavu   2.35-1

Versions of packages fretsonfire-game recommends:
pn  fretsonfire-songs-muldjord  
pn  fretsonfire-songs-sectoid   

Versions of packages fretsonfire-game suggests:
ii  vorbis-tools  1.4.0-7

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fretsonfire
Source-Version: 1.3.110.dfsg2-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated fretsonfire package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Dec 2015 16:30:45 +0100
Source: fretsonfire
Binary: fretsonfire fretsonfire-game
Architecture: source
Version: 1.3.110.dfsg2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 fretsonfire - game of musical skill and fast fingers
 fretsonfire-game - game of musical skill and fast fingers - Game files

Bug#799761: marked as done (python-nmap: FTBFS: IOError: [Errno 2] No such file or directory: 'scanme_output.xml')

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 13:20:49 +
with message-id 
and subject line Bug#799761: fixed in python-nmap 0.5.0-1-1
has caused the Debian Bug report #799761,
regarding python-nmap: FTBFS: IOError: [Errno 2] No such file or directory: 
'scanme_output.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.)


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

Dear Maintainer,

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

  [..]

pybuild --test --test-nose -i python{version} -p 2.7 --dir .
  I: pybuild base:170: cd
  /tmp/buildd/python-nmap-0.4.0/.pybuild/pythonX.Y_2.7/build; python2.7
  -m nose 
  ..EE.E
  ==
  ERROR: nmap.test_nmap.test_command_line
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 267, in
setUp
  try_run(self.test, names)
File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in
try_run
  return func()
File

"/tmp/buildd/python-nmap-0.4.0/.pybuild/pythonX.Y_2.7/build/nmap/test_nmap.py",
line 67, in xmlfile_read_setup
  nm.analyse_nmap_xml_scan(open('scanme_output.xml').read())
  IOError: [Errno 2] No such file or directory: 'scanme_output.xml'
  
  ==
  ERROR: nmap.test_nmap.test_scan_info
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 267, in
setUp
  try_run(self.test, names)
File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in
try_run
  return func()
File

"/tmp/buildd/python-nmap-0.4.0/.pybuild/pythonX.Y_2.7/build/nmap/test_nmap.py",
line 67, in xmlfile_read_setup
  nm.analyse_nmap_xml_scan(open('scanme_output.xml').read())
  IOError: [Errno 2] No such file or directory: 'scanme_output.xml'
  
  ==
  ERROR: nmap.test_nmap.test_all_hosts
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 267, in
setUp
  try_run(self.test, names)
File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in
try_run
  return func()
File

"/tmp/buildd/python-nmap-0.4.0/.pybuild/pythonX.Y_2.7/build/nmap/test_nmap.py",
line 67, in xmlfile_read_setup
  nm.analyse_nmap_xml_scan(open('scanme_output.xml').read())
  IOError: [Errno 2] No such file or directory: 'scanme_output.xml'
  
  ==
  ERROR: nmap.test_nmap.test_host
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 267, in
setUp
  try_run(self.test, names)
File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in
try_run
  return func()
File

"/tmp/buildd/python-nmap-0.4.0/.pybuild/pythonX.Y_2.7/build/nmap/test_nmap.py",
line 67, in xmlfile_read_setup
  nm.analyse_nmap_xml_scan(open('scanme_output.xml').read())
  IOError: [Errno 2] No such file or directory: 'scanme_output.xml'
  
  ==
  ERROR: nmap.test_nmap.test_port
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 267, in
setUp
  try_run(self.test, names)
File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in
try_run
  return func()
File

"/tmp/buildd/python-nmap-0.4.0/.pybuild/pythonX.Y_2.7/build/nmap/test_nmap.py",
line 67, in xmlfile_read_setup
  nm.analyse_nmap_xml_scan(open('scanme_output.xml').read())
  IOError: [Errno 2] No such file or directory: 'scanme_output.xml'
  
  ==
  ERROR: 

Bug#806246: cmucl: FTBFS (missing build-depends)

2015-12-13 Thread Peter Van Eynde
Hello Santiago,

> Seems like a missing Build-Depends on hardening-includes, the package
> containing /usr/share/hardening-includes/hardening.make, so it
> should be quite easy to fix.

Turns out it's not so easy after all, I'm still working on it...

> BTW: I wonder why this package does not exist for amd64. Is it a
> bootstrapping problem as the extended description suggests?

There is no upstream for amd64 (there was but it bitrotted). If you want
cmucl on amd64 then I suggest that you use sbcl which is a based on
cmucl, but with slightly different goals. One of which is having an
amd64 port ;).

Best regards, Peter

-- 
signature -at- pvaneynd.mailworks.org
http://pvaneynd.dreamwidth.org/
God, root, what is difference?-Pitr|God is more forgiving.-Dave Aronson|



signature.asc
Description: OpenPGP digital signature


Bug#799997: marked as done (pyroma: FTBFS: ERROR: invocation failed (exit code 1))

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 13:35:00 +
with message-id 
and subject line Bug#77: fixed in pyroma 2.0.0b2-1
has caused the Debian Bug report #77,
regarding pyroma: FTBFS: ERROR: invocation failed (exit code 1)
to be marked as done.

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

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


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

Dear Maintainer,

pyroma fails to build from source in unstable/amd64:

  [..]

 dh_auto_test
pybuild --test --test-tox -i python{version} -p 2.7 --dir .
  I: pybuild base:170: cd
  /tmp/buildd/pyroma-1.8.2/.pybuild/pythonX.Y_2.7/build; tox -c
  /tmp/buildd/pyroma-1.8.2/tox.ini -e py27
  GLOB sdist-make: /tmp/buildd/pyroma-1.8.2/setup.py
  py27 create: /tmp/buildd/pyroma-1.8.2/.tox/py27
  ERROR: invocation failed (exit code 1), logfile:
  /tmp/buildd/pyroma-1.8.2/.tox/py27/log/py27-0.log
  ERROR: actionid: py27
  msg: getenv
  cmdargs: ['/usr/bin/python3', '-m', 'virtualenv', '--python',
  '/usr/bin/python2.7', 'py27']
  env: {'HOME': '/tmp/buildd/pyroma-1.8.2/.pybuild/pythonX.Y_2.7',
  'DH_INTERNAL_BUILDFLAGS': '1', 'DEB_TARGET_ARCH_BITS': '64',
  'PYTHONHASHSEED': '1942504628', 'FCFLAGS': '-g -O2
  -fstack-protector-strong', 'SUDO_GID': '124', 'PBUILDER_PKGDATADIR':
  '/usr/share/pbuilder', 'MAIL': '/var/mail/root', 'DEB_HOST_GNU_CPU':
  'x86_64', 'https_proxy': 'https://127.0.0.1:9', 'LDFLAGS':
  '-Wl,-z,relro', 'DEB_TARGET_ARCH_OS': 'linux', 'MAKEFLAGS': 'w', '_':
  '/usr/bin/unshare', 'no_proxy': 'localhost', 'USERNAME': 'root',
  'SUDO_COMMAND': '/usr/bin/timeout -k 12.1h 12h /usr/bin/ionice -c 3
  /usr/bin/nice /usr/sbin/pbuilder --build --configfile
  /srv/reproducible-results/tmp.fi3Zm5QltE/pbuilderrc_6K4d
  --debbuildopts -b --basetgz
  /var/cache/pbuilder/unstable-reproducible-base.tgz --buildresult
  /srv/reproducible-results/tmp.fi3Zm5QltE/b1 --logfile b1/build.log
  pyroma_1.8.2-1.dsc', 'LC_ALL': 'C', 'DEB_TARGET_ARCH_ENDIAN':
  'little', 'DEB_TARGET_ARCH': 'amd64', 'VIRTUAL_ENV':
  '/tmp/buildd/pyroma-1.8.2/.tox/py27', 'DEB_BUILD_GNU_SYSTEM':
  'linux-gnu', 'LD_PRELOAD': '', 'DEB_BUILD_MULTIARCH':
  'x86_64-linux-gnu', 'DEB_BUILD_TIMESTAMP': '1440078459',
  'DEB_HOST_ARCH': 'amd64', 'DEB_BUILD_GNU_TYPE': 'x86_64-linux-gnu',
  'SOURCE_DATE_EPOCH': '1440078459', 'USER': 'pbuilder1',
  'DEB_BUILD_OPTIONS': 'parallel=15', 'LANG': 'C', 'DEB_BUILD_ARCH':
  'amd64', 'DEB_BUILD_ARCH_CPU': 'amd64', 'DEB_TARGET_GNU_TYPE':
  'x86_64-linux-gnu', 'PBUILDER_PKGLIBDIR': '/usr/lib/pbuilder',
  'LOGNAME': 'pbuilder1', 'DEB_HOST_ARCH_BITS': '64', 'http_proxy':
  'http://127.0.0.1:9', 'DEBIAN_FRONTEND': 'noninteractive', 'MFLAGS':
  '-w', 'DEB_BUILD_ARCH_OS': 'linux', 'SHELL': '/bin/bash', 'GCJFLAGS':
  '-g -O2 -fstack-protector-strong', 'DEB_HOST_GNU_TYPE':
  'x86_64-linux-gnu', 'PYTHONPATH':
  
'/tmp/buildd/pyroma-1.8.2/debian/python-pyroma/usr/lib/python2.7/dist-packages:/tmp/buildd/pyroma-1.8.2/.pybuild/pythonX.Y_2.7/build',
  'DEB_TARGET_GNU_CPU': 'x86_64', 'DH_VERBOSE': '1',
  'DEB_TARGET_MULTIARCH': 'x86_64-linux-gnu', 'OLDPWD':
  '/tmp/buildd/pyroma-1.8.2', 'DEB_HOST_ARCH_OS': 'linux', 'TZ':
  '/usr/share/zoneinfo/Etc/GMT+12', 'TERM': 'unknown',
  'DEB_HOST_MULTIARCH': 'x86_64-linux-gnu', 'CFLAGS': '-g -O2
  -fstack-protector-strong -Wformat -Werror=format-security',
  'DH_INTERNAL_OVERRIDE': 'dh_auto_test', 'DEB_BUILD_ARCH_ENDIAN':
  'little', 'DEB_BUILD_ARCH_BITS': '64', 'DEB_HOST_ARCH_ENDIAN':
  'little', 'DEB_HOST_ARCH_CPU': 'amd64', 'SUDO_UID': '114', 'CXXFLAGS':
  '-g -O2 -fstack-protector-strong -Wformat -Werror=format-security',
  'FFLAGS': '-g -O2 -fstack-protector-strong', 'DEB_TARGET_GNU_SYSTEM':
  'linux-gnu', 'DEB_TARGET_ARCH_CPU': 'amd64', 'OBJCXXFLAGS': '-g -O2
  -fstack-protector-strong -Wformat -Werror=format-security',
  'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'MAKELEVEL': '2',
  'SHLVL': '2', 'OBJCFLAGS': '-g -O2 -fstack-protector-strong -Wformat
  -Werror=format-security', 'PBCURRENTCOMMANDLINEOPERATION': '--build',
  'DEB_BUILD_GNU_CPU': 'x86_64', 'PYBUILD_NAME': 'pyroma', 'SUDO_USER':
  'jenkins', 'PWD':
  '/tmp/buildd/pyroma-1.8.2/.pybuild/pythonX.Y_2.7/build', 'PATH':
  
'/tmp/buildd/pyroma-1.8.2/.tox/py27/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games',
  'DEB_HOST_GNU_SYSTEM': 'linux-gnu', 'PBUILDER_SYSCONFDIR': 

Bug#805221: marked as done (picard: FTBFS: ImportError: No module named PyQt4)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 12:34:42 +
with message-id 
and subject line Bug#805221: fixed in picard 1.3.2-3
has caused the Debian Bug report #805221,
regarding picard: FTBFS: ImportError: No module named PyQt4
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.)


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

Dear Maintainer,

The package fails to build:


==
ERROR: test.test_versions (unittest.loader.ModuleImportFailure)
--
ImportError: Failed to import test module: test.test_versions
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
__import__(name)
  File "test/__init__.py", line 5, in 
__import__("test." + os.path.basename(filename)[:-3])
  File "test/test_amazon_urls.py", line 4, in 
from picard.util import parse_amazon_url
  File "picard/util/__init__.py", line 30, in 
from PyQt4 import QtCore
ImportError: No module named PyQt4


--
Ran 13 tests in 0.001s

FAILED (errors=13)
E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: cd 
/picard-1.3.2/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover -v 
dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
code 13

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: picard
Source-Version: 1.3.2-3

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated picard 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, 13 Dec 2015 13:13:27 +0100
Source: picard
Binary: picard
Architecture: source
Version: 1.3.2-3
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Sebastian Ramacher 
Description:
 picard - Next-Generation MusicBrainz audio files tagger
Closes: 805221
Changes:
 picard (1.3.2-3) unstable; urgency=medium
 .
   * Team upload.
   * debian/control: Add python-qt4 and python-mutagen to Build-Depends.
 (Closes: #805221)
   * debian/menu: Removed (command-in-menu-file-and-desktop-file).
Checksums-Sha1:
 bd2964bf9db9320fdafecf495e312c8a83e6151f 2036 picard_1.3.2-3.dsc
 635a9c8a0fc2e3a4b3eb67ad1dd3cf7e4f497f79 9608 picard_1.3.2-3.debian.tar.xz
Checksums-Sha256:
 572038a6e8103931701c6ebd7e16b5ce245d9ad823db0124e0fd00100d062f8c 2036 
picard_1.3.2-3.dsc
 ba05631ef8f16aa3af610ca2b8600cc0da033186b7f0b0a4187599372559c055 9608 
picard_1.3.2-3.debian.tar.xz
Files:
 ad5161dc0c2446b3f740a72f672562a8 2036 sound optional picard_1.3.2-3.dsc
 ee3a7035106a0d9af25960a23a479e94 9608 sound optional 
picard_1.3.2-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbWIpAAoJEGny/FFupxmTN08P/A8BOK7fy4NviTliQaGPY0ri
Ith3EQy5zOTtJwLeAYvYfNgy7zLLU87B+qE0UoUavGYuF8Q0k1fJfW8rQYuYjl9C
FZ4bjACdizh2gzUE/KGpdNua0IFfXHFKnuKPeLEaWj75gpPFx5jDAl+DSXXi8Jfy
zxege1YvwZ76g1gjVjY96zkvLCiBZYakM9+slutblpE3M9ZzHhCqJUVePcW1u1L0
Jkq0Ok2i/q46iP15+M/HzaW8h0cWklsN5ckkg42bcOauNnG30rLUDP8Qxjv8lLUL
P13RotoieJQdCKhk9AmRML8SQDPpYw4AZ0wC+yaICOiVkiJS9b1UKIf2I+m0Dk4d

Processed: tagging 807492

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 807492 + pending
Bug #807492 [src:libmath-bigint-gmp-perl] libmath-bigint-gmp-perl: FTBFS on 32 
bit platforms
Added tag(s) pending.
> thanks
Stopping processing here.

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



Processed: tagging 807492

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 807492 - pending
Bug #807492 [src:libmath-bigint-gmp-perl] libmath-bigint-gmp-perl: FTBFS on 32 
bit platforms
Ignoring request to alter tags of bug #807492 to the same tags previously set
> thanks
Stopping processing here.

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



Bug#803300: prepare for giflib5

2015-12-13 Thread Manuel A. Fernandez Montecelo
Hi all,

2015-12-13 15:33 GMT+00:00 Sebastiaan Couwenberg :
> On Wed, 28 Oct 2015 16:02:40 +0100 Matthias Klose wrote:
>> For the latter two options, please see a patch at
>> http://launchpadlibrarian.net/222944251/openscenegraph_3.2.1-7ubuntu2_3.2.1-7ubuntu3.diff.gz
>
> Upstream has fixed the giflib5 support a bit differently [0][1].
>
> The attached debdiff uses the upstream changes for giflib 5.x instead of
> those applied in Ubuntu.
>
> Please include these changes in openscenegraph (3.2.1-9) to prevent
> testing autoremoval of openscenegraph and all its reverse dependencies
> because of this RC bug.
>
> [0]
> https://github.com/openscenegraph/osg/commit/afb442fccd182cfe8608f43394af016f6723f97a
> [1]
> https://github.com/openscenegraph/osg/commit/18213bfb67d464715af618fd8c73549f749625b9

Thanks both.

I can work on this towards the end of next week (17-20th or so), not
before.  I don't know if Alberto will be able to upload before then.

There are a few other pending things to fix, so I think that it would
be better that either Alberto or I get around to work on this and fix
the issues in a single upload, so the less powerfull arches are not
taxed too much.  The removal from testing will happen in a month, so
there should be plenty of time.

But if for some reason we do not upload in ~10 days and you want to
finish the transition, and the NMU includes the mentioned patches,
it's OK for me (I suppose that also for Alberto, if he doesn't reply).


Cheers.
-- 
Manuel A. Fernandez Montecelo 



Bug#807675: More failures apparently unrelated to "SCU Failed: 0006:0213 Data dictionary missing"

2015-12-13 Thread Julien Lamy
Using the latest version of DCMTK, I'm unable to reproduce the error in
a freshly-updated sid pbuilder running on jessie, so the following
diagnosis is a bit of a guesswork.

The "Address already in use" message points to an already-running DICOM
server on port 2, which prohibits running the tests correctly and
causes the build process to fail. This could be caused by a DICOM server
running on your builders, but is most likely something left over from a
previous build of DCMTK++. The errors running "make test" are to be
expected: in tests/run.sh, we set up a few things for the networking
tests without which the mentioned tests fail.

I've patched the package to fix this bug (should upload soon) and will
try to improve the robustness of the tests upstream.

Cheers,
-- 
Julien

Le 11/12/2015 18:06, Gert Wollny a écrit :
> After fixing dcmtk (uploading right now) there are still failures: 
> 
> On one hand, during the build I get: 
> 
> cd build && ../tests/run.sh
> F: cannot initialize network: 0006:031c TCP Initialization Error:
> Address already in use
> E: Store Failed, file: dcmtkpp.iZA/data.dcm:
> E: 0006:0317 Peer aborted Association (or never connected)
> debian/rules:18: recipe for target 'override_dh_auto_test' failed
> 
> 
> On the other hand, when I just run "make test" in the build directory I
> get various failures: 
> 
> The following tests FAILED:
>   134 - StoreSCU_Store (Failed)
>   174 - FindSCU_Find (Failed)
>   175 - FindSCU_FindCallback (Failed)
>   216 - Association_Associate (Failed)
>   288 - GetSCU_Get (Failed)
>   289 - GetSCU_GetCallback (Failed)
>   293 - MoveSCU_Move (Failed)
>   294 - MoveSCU_MoveCallback (Failed)
>   297 - SCU_Echo (Failed)
> Errors while running CTest
> 
> The all point to the same problem: 
>   
> dcmtkpp/tests/code/../PeerFixtureBase.h(74): fatal error in "Store":
> DCMTKPP_OWN_AET is not defined
> 
> 
> Best 
> Gert 
> 



signature.asc
Description: OpenPGP digital signature


Processed: Re: camorama cannot take pictures

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 800586 important
Bug #800586 [camorama] camorama cannot take pictures
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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



Bug#800586: camorama cannot take pictures

2015-12-13 Thread Ralf Jung
severity 800586 important
thanks

Hi,

> package: camorama
> version: 0.19-3
> severity: grave
> reason: fails its primary functionality
> 
> It fails with an error message "Cannot create directory ~/Webcam_Picture
> s"
> 
> Same message after manually creating the directory.

Taking pictures is only one functionality of camorama, but I wouldn't
consider it the "primary" one. Hence I'd argue that this is important,
but not grave enough to be RC. For example, live preview is not
affected, and that's all I ever use the program for.

I can confirm that in default configuration, Clicking "Take Picture"
does nothing.
However, taking pictures works fine here, after doing "Edit -
Preferences", "Local Capture", and checking "Enable local capture". If I
now press the "Take Picture" button, a picture is created. So from all I
can tell, this is "just" bad UI.

Downgrading accordingly, to let the package go back to testing.

Kind regards,
Ralf



Bug#800216: Fwd: gniall: diff for NMU version 0.7.1-7.1

2015-12-13 Thread Raphael mota
Hi,

I uploaded a NMU to 10-day/delay queue. Feel free to cancel this upload if
needed.

The debian/changelog is:

* Non-maintainer upload.
  * Update DH level to 9 to avoid a FTBFS. (Closes: #800216)
  * debian/compat: updated to 9.
  * debian/control:
 - Added the ${misc:Depends} variable to provide the
   right install dependencies.
 - Bumped Standards-Version to 3.9.6.

I attached a debdiff.

Thanks.

Regards,

Raphael Mota


gniall.debdiff
Description: Binary data


Processed: tagging 807735

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 807735 + sid stretch
Bug #807735 [src:gmpc-plugins] gmpc-plugins: FTBFS: libmpd-internal.h:210:10: 
error: expected identifier or '(' before '__extension__'
Added tag(s) sid and stretch.
> thanks
Stopping processing here.

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



Processed: Fix "Can't find marble" FTBFS [patch]

2015-12-13 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 patch
Bug #807564 [src:digikam] digikam: FTBFS: Could not find a package 
configuration file provided by "Marble"
Added tag(s) patch.

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



Bug#807564: Fix "Can't find marble" FTBFS [patch]

2015-12-13 Thread Danny Edel
Control: tags -1 patch

Hi List,

I've tried to reproduce the build failure and it turns out that the
FindMarble.cmake file is in a path that is not in the default cmake
module search path.

If the search path is passed to cmake with EXTRA_CMAKE_ARGS, digikam
compiles successfully again.

Also the libsoprano-dev dependency is no longer a problem, because
digikam build-depends on kdelibs5-dev, which (now?) depends on
libsoprano-dev.

I hope that helps in at least building digikam again, making it easier
to look into the other remaining tickets.

PS: If you test the patch locally, don't forget to increment digikam's
version number! libstdc++6 in sid has a "Breaks: digikam-private-libs"
on versions <= 4:4.4.0-1.1+b2 defined.


I must add that although it compiles, it does *not* start out-of-the-box
on my system, it now crashes with the following error message:

*** Error in `digikam': realloc(): invalid old size: 0x00c21f80 ***
Aborted


Maybe someone with more C debugging skills can look into that?  (or
maybe it is an issue with my system)


Cheers,

- Danny
diff -ru orig/digikam-4.4.0/debian/rules digikam-4.4.0/debian/rules
--- orig/digikam-4.4.0/debian/rules	2014-01-18 00:19:58.0 +0100
+++ digikam-4.4.0/debian/rules	2015-12-13 14:39:07.711699472 +0100
@@ -12,6 +12,9 @@
   EXTRA_CMAKE_ARGS += -DDIGIKAMSC_USE_PRIVATE_KDEGRAPHICS=OFF
 endif
 
+# Location of FindMarble.cmake
+EXTRA_CMAKE_ARGS += -DCMAKE_MODULE_PATH=/usr/share/marble/cmake
+
 %:
 	dh $@ --with kde --parallel 
 


Bug#728955: libatomic-ops: diff for NMU version 7.4.2-1.2

2015-12-13 Thread Ian Wienand
The patch has not been applied because it is not clear it is correct

There is a thread that starts at [1] and ended inconclusively at [2]

It's unfortunate that the number of people who understand power memory ordering
issues at the level required can probably be counted on one hand.  But I don't
think we should apply patches upstream feel don't address the issue

-i

[1] http://www.hpl.hp.com/hosted/linux/mail-archives/gc/2014-January/005825.html
[2] 
http://www.hpl.hp.com/hosted/linux/mail-archives/gc/2014-February/005852.html

On Fri, Dec 11, 2015 at 7:32 AM, gregor herrmann  wrote:
> Control: tags 728955 + pending
>
> Dear maintainer,
>
> Fernando Seiti Furusato has prepared an NMU for libatomic-ops
> (versioned as 7.4.2-1.2) and I've uploaded it to DELAYED/5. Please
> feel free to tell me if I should delay it longer.
>
> Regards.
>
> --
>  .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
>  : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
>  `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
>`-   NP: Andrew Lloyd Webber & Tim Rice
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
>
> iQJ8BAEBCgBmBQJWaeF9XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
> QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGWO0P/3y0daKtNH43R0nQDiPuWFfp
> 3dSFljsxqvD4sElq/OJJbDiS0rCiItOqug7BNllfjKrXvRo+n925sds37Bz2vow6
> ytkOh6bBQhLGA3zZhm4FvanaJEbpq93STxtyKWH28sA7hS74lIu4zy9Fil8BXXKh
> D3cDeJ4R4rpxVTpFi7+MOdApZNWz92LyACn7H4TgjWg9ECG0INqS/eTNV1jQkJYD
> AX5oK+Ny9N3Es0l4+rprqx1VUPr4T08ieC9D1j4QD6185NiQMH+xGv0QkbtnDnPO
> bNHkS5g2HeEh/ExQZNn2yMWqWOtHGbDPBlVpwEGjSUBP9ipXy/Gd2O4lg4S5wY46
> lj/gH6HfcBRQxlmeJ0a9/f57sJd3jIt3JDy5VbtjNU2t/OGsFMpUcnDThZzvFQ9q
> dYhEYekRcJ2vfFnYm5T68RvFZHUdkXujXaUQM47CjTji49Gi5AmAjCw6ZG65YSPj
> kMiYxxfbP8D0mGSqP5/Izyn33JwnJJ9S1OLrjfK2YnVZJnmjJTEZYAescHVPabZp
> PPfLnu1FWdjGxthZMwdRVWMX8gwqUH/TOnzCBYmcYobE3juuxiK6zg5NLz2MGVWv
> ixpgcW4e0gvODdgpjyuVIbbc+nuxQ/JUM2pJvV8NOJsuzLqG28VX1mVNth78ayPe
> kKz8Vt7biE/iGgXBuZlh
> =sBVD
> -END PGP SIGNATURE-
>



Processed: clone hardening-wrapper issue to get nmu's done

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> clone 801597 -1
Bug #801597 [src:hardening-wrapper] PIE and stack protection appear missing 
since update to GCC-5
Bug 801597 cloned as bug 807867
> reassign -1 release.debian.org
Bug #807867 [src:hardening-wrapper] PIE and stack protection appear missing 
since update to GCC-5
Bug reassigned from package 'src:hardening-wrapper' to 'release.debian.org'.
No longer marked as found in versions hardening-wrapper/2.7.
Ignoring request to alter fixed versions of bug #807867 to the same values 
previously set
> retitle -1 nmu: all packages built without GCC 5 and hardening-wrapper
Bug #807867 [release.debian.org] PIE and stack protection appear missing since 
update to GCC-5
Changed Bug title to 'nmu: all packages built without GCC 5 and 
hardening-wrapper' from 'PIE and stack protection appear missing since update 
to GCC-5'
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was d...@debian.org).
> usertag -1 + binnmu
There were no usertags set.
Usertags are now: binnmu.
> thanks
Stopping processing here.

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



Processed: tagging 807657

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 807657 + sid stretch
Bug #807657 [src:dvdauthor] dvdauthor: FTBFS: compat.h:141:8: error: expected 
identifier or '(' before '__extension__'
Added tag(s) sid and stretch.
> thanks
Stopping processing here.

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



Processed: tagging 807609

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 807609 + sid stretch
Bug #807609 [src:spatial4j] spatial4j: FTBFS: [ERROR] The specified user 
settings file does not exist: /etc/maven2/settings-debian.xml
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

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



Bug#807867: nmu: all packages built without GCC 5 and hardening-wrapper

2015-12-13 Thread Matthias Klose
hardening-wrapper 1.28+nmu1 is supposed to fix hardening-wrapper, however 
binNMUs for all packages build-depending on hardening-wrapper, which got built 
(either uploaded or binNMUed) after GCC 5 became the default have to be 
successfully done.




Bug#803293: marked as done (prepare for giflib5)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 19:23:09 +
with message-id 
and subject line Bug#803293: fixed in xplanet 1.3.0-3
has caused the Debian Bug report #803293,
regarding prepare for giflib5
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.)


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

Package: src:xplanet
Version: 1.3.0-2
Tags: sid stretch patch
Blocks: 803158
User: gif...@packages.debian.org
Usertags: giflib5

Planning an update of giflib to the current version 5.1.1. Giflib slightly 
changes it's API, requiring soureful changes. There are some options for getting 
giflib5.1 support:


- Look for a newer upstream version, if upstream supports
both giflib4 and giflib5.1. Upload the new package,
and close the bug report.

- Patch the code to both use the NEW API. This can be done using
#if GIFLIB_MAJOR >= 5

#else

#endif
Please upload the package, and close the report.

- Unconditionally patch the code, not supporting giflib4 anymore.
Please upload a package to experimental once giflib5 hits
experimental.

For the latter two options, please see a patch at
http://launchpadlibrarian.net/222932858/xplanet_1.3.0-2build2_1.3.0-2ubuntu1.diff.gz

To test your changes before giflib5 is found in experimental, please use

deb https://people.debian.org/~doko/tmp/giflib5 ./

Thanks, Matthias
--- End Message ---
--- Begin Message ---
Source: xplanet
Source-Version: 1.3.0-3

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

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated xplanet 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, 13 Dec 2015 18:53:26 +
Source: xplanet
Binary: xplanet xplanet-images
Architecture: source all amd64
Version: 1.3.0-3
Distribution: unstable
Urgency: low
Maintainer: Steve McIntyre <93...@debian.org>
Changed-By: Steve McIntyre <93...@debian.org>
Description:
 xplanet- planetary body renderer
 xplanet-images - imagery for xplanet
Closes: 803293
Changes:
 xplanet (1.3.0-3) unstable; urgency=low
 .
   * Update to use giflib5, using patch from Matthias Klose (thanks!).
 Closes: #803293
   * Update Standards-Version to 3.9.6
Checksums-Sha1:
 14b163fdf82c8edde923ddda46a81cb1c16090fa 1929 xplanet_1.3.0-3.dsc
 e236500bf4ff401db9a592fae1028bb73495c71d 15008 xplanet_1.3.0-3.debian.tar.xz
 b87939b8ef86a665a544cd4c09db8eb6f39a48d2 435684 xplanet-images_1.3.0-3_all.deb
 1c2268cc41d1a25598c5b2ac9112f7209cbb7481 492508 xplanet_1.3.0-3_amd64.deb
Checksums-Sha256:
 acc6405a9ab4812ec33ea7b059a3d764da41e308f5a9e03bbd32016dfae8037d 1929 
xplanet_1.3.0-3.dsc
 e6951ef6899eab1a0149a2dff0979e80602bd8a6df796717dc6cbec47995fd03 15008 
xplanet_1.3.0-3.debian.tar.xz
 e6b82ad0c730b4c565f034a6acf7b715ffe57031468ee63c2b256c7e7f7fdf7a 435684 
xplanet-images_1.3.0-3_all.deb
 27bb1d10442dd381902bdd0cea524afc8c7257fd7b7a955ce59148ea78a7f4b0 492508 
xplanet_1.3.0-3_amd64.deb
Files:
 035a56507642ee8cf65d240b9488bfcc 1929 graphics optional xplanet_1.3.0-3.dsc
 cdae348858f7f9147707893f1a72004f 15008 graphics optional 
xplanet_1.3.0-3.debian.tar.xz
 a2031e0f756fdcc8ec8f8beda66167b4 435684 graphics optional 
xplanet-images_1.3.0-3_all.deb
 10102384b5359c4d00e17ae1979ae54b 492508 graphics optional 
xplanet_1.3.0-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbcFzAAoJEFh5eVc0QmhOWNwP/12yHvtoCit0wHfV7j+s/n+T
AfT0CnownlOs2yImaCP/iBZGpmufYdKK7mUZKcQq8W9gOIJUa8v2amIE7kNcJH+C
PtS4uXYERcLqM7lHnpi74L0diWSXjgMNYe+a8yDAOVOEuOOiPyNi2CZmJ0F0SBw1
CtxyzbnECbckLB9p8wE/0Kw/hbCrmRK0TBb9sFmKLo5y7Le6dY3A7BKgKsRKWgZA
TbAfKYrkpzxvQI1Z0baG+XoAwZltNPFlS7HfzPlW/MAzH+XXaBSMY8RV1T13k7uu
YWv63IyNIMOuuAo8rg+U021DE8SAZ7fPL65x11FrxjRF8w1tALdBI4ZGbUety2x9
OmSgKebZNb9/0FjT3DG5lwsGiqTj37tHNcmTgQgwrLxXes8F2L7mTUOYOJOxKLpu
t5OMapXx4UG1paY6rcu1aZ2pJUTlyNdjC/qkVodFm+bY4wUVTPoW7dcQ1upmzUQQ
H5mWzoG4cMNenw+1MSvL5QOVMIEpl896OBixkoSY+WvGllx6Jo0VgpYvGYpIumIA

Bug#728955: libatomic-ops: diff for NMU version 7.4.2-1.2

2015-12-13 Thread gregor herrmann
Control: tag -1 - pending

On Mon, 14 Dec 2015 08:05:22 +1100, Ian Wienand wrote:

> The patch has not been applied because it is not clear it is correct
> 
> There is a thread that starts at [1] and ended inconclusively at [2]
> 
> It's unfortunate that the number of people who understand power memory 
> ordering
> issues at the level required can probably be counted on one hand.  But I don't
> think we should apply patches upstream feel don't address the issue
> 
> -i
> 
> [1] 
> http://www.hpl.hp.com/hosted/linux/mail-archives/gc/2014-January/005825.html
> [2] 
> http://www.hpl.hp.com/hosted/linux/mail-archives/gc/2014-February/005852.html

Thanks for this additional information.
I've cancelled the aforementioned NMU.


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Various Artists: A Pair Of Brown Eyes


signature.asc
Description: Digital Signature


Processed: Re: Bug#728955: libatomic-ops: diff for NMU version 7.4.2-1.2

2015-12-13 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 - pending
Bug #728955 [src:libatomic-ops] FTBFS on powerpc: FAIL: test_stack
Removed tag(s) pending.

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



Processed: this is broken.

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 765419 serious
Bug #765419 [mumble-django] mumble-django: wont install , broken is useless
Severity set to 'serious' from 'normal'
> --
Stopping processing here.

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



Bug#797651: marked as done (mummy fails to build (libgccxml-dev vs GCC-5))

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 19:00:53 +
with message-id 
and subject line Bug#806818: Removed package(s) from unstable
has caused the Debian Bug report #797651,
regarding mummy fails to build (libgccxml-dev vs GCC-5)
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.)


-- 
797651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mummy
Version: 1.0.3-2
Severity: grave


mummy FTBFS in sid:

/usr/bin/cmake -E cmake_link_script CMakeFiles/mummy.dir/link.txt
--verbose=1
/usr/bin/c++   -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -D_FORTIFY_SOURCE=2  -O2 -g -DNDEBUG   -Wl,-z,relro
CMakeFiles/mummy.dir/MummyMain.cxx.o  -o bin/mummy -rdynamic
bin/libmummyLib.a -lCableGenerators -lCableParsers -lexpat -lCxxTypes
-lgxsys
bin/libmummyLib.a(MummyCsharpGenerator.cxx.o): In function
`ExtractTypeAndCountFromHintLine(std::__cxx11::basic_string const&,
std::__cxx11::basic_string&, std::__cxx11::basic_string&)':
/home/mathieu/tmp/mummy-1.0.3/MummyCsharpGenerator.cxx:437: undefined
reference to
`gxsys::RegularExpression::find(std::__cxx11::basic_string const&)'
bin/libmummyLib.a(MummyCsharpGenerator.cxx.o): In function
`ReturnTypeMatchesHintType(cable::Type*, std::__cxx11::basic_string const&)':
/home/mathieu/tmp/mummy-1.0.3/MummyCsharpGenerator.cxx:456: undefined
reference to
`gxsys::SystemTools::UpperCase(std::__cxx11::basic_string const&)'
bin/libmummyLib.a(MummyCsharpGenerator.cxx.o): In function
`ExtractCountFromMethodDeclarationLine(std::__cxx11::basic_string const&,
std::__cxx11::basic_string&)':
/home/mathieu/tmp/mummy-1.0.3/MummyCsharpGenerator.cxx:500: undefined
reference to
`gxsys::RegularExpression::find(std::__cxx11::basic_string const&)'
/home/mathieu/tmp/mummy-1.0.3/MummyCsharpGenerator.cxx:507: undefined
reference to
`gxsys::RegularExpression::find(std::__cxx11::basic_string const&)'
/home/mathieu/tmp/mummy-1.0.3/MummyCsharpGenerator.cxx:514: undefined
reference to
`gxsys::RegularExpression::find(std::__cxx11::basic_string const&)'
/home/mathieu/tmp/mummy-1.0.3/MummyCsharpGenerator.cxx:521: undefined
reference to
`gxsys::RegularExpression::find(std::__cxx11::basic_string const&)'
bin/libmummyLib.a(MummyCsharpGenerator.cxx.o): In function
`MummyCsharpGenerator::CacheExternalHints(std::__cxx11::basic_string const&)':
/home/mathieu/tmp/mummy-1.0.3/MummyCsharpGenerator.cxx:138: undefined
reference to
`gxsys::RegularExpression::find(std::__cxx11::basic_string const&)'
bin/libmummyLib.a(MummyLineOrientedTextFileReader.cxx.o):/home/mathieu/tmp/mummy-1.0.3/MummyLineOrientedTextFileReader.cxx:368:
more undefined references to
`gxsys::RegularExpression::find(std::__cxx11::basic_string const&)' follow
bin/libmummyLib.a(MummySettings.cxx.o): In function
`MummySettings::AddArgumentHandlers(gxsys::CommandLineArguments&)':
/home/mathieu/tmp/mummy-1.0.3/MummySettings.cxx:115: undefined reference to
`gxsys::CommandLineArguments::AddArgument(char const*,
gxsys::CommandLineArguments::ArgumentTypeEnum,
std::__cxx11::basic_string*, char const*)'
/home/mathieu/tmp/mummy-1.0.3/MummySettings.cxx:122: undefined reference to
`gxsys::CommandLineArguments::AddArgument(char const*,
gxsys::CommandLineArguments::ArgumentTypeEnum,
std::__cxx11::basic_string*, char const*)'
/home/mathieu/tmp/mummy-1.0.3/MummySettings.cxx:129: undefined reference to
`gxsys::CommandLineArguments::AddArgument(char const*,
gxsys::CommandLineArguments::ArgumentTypeEnum,
std::__cxx11::basic_string*, char const*)'
/home/mathieu/tmp/mummy-1.0.3/MummySettings.cxx:136: undefined reference to
`gxsys::CommandLineArguments::AddArgument(char const*,
gxsys::CommandLineArguments::ArgumentTypeEnum,
std::__cxx11::basic_string*, char const*)'

Bug#807675: marked as done (dcmtkpp: FTBFS: SCU Failed: 0006:0213 Data dictionary missing)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 18:19:55 +
with message-id 
and subject line Bug#807675: fixed in dcmtkpp 0.3.1-3
has caused the Debian Bug report #807675,
regarding dcmtkpp: FTBFS: SCU Failed: 0006:0213 Data dictionary missing
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.)


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

Dear Maintainer,

dcmtkpp fails to build from source in unstable/amd64:

  [..]

  Generating member index...
  Generating file index...
  Generating file member index...
  Generating example index...
  finalizing index lists...
  writing tag file...
  lookup cache used 5124/65536 hits=34949 misses=5178
  finished...
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151211163341.wUBAYFVFa6/dcmtkpp-0.3.1'
 debian/rules override_dh_auto_test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20151211163341.wUBAYFVFa6/dcmtkpp-0.3.1'
  cd build && ../tests/run.sh
  W: no data dictionary loaded, check environment variable: DCMDICTPATH
  F: cannot initialize network: 0006:031c TCP Initialization Error: Address 
already in use
  W: no data dictionary loaded, check environment variable: DCMDICTPATH
  E: DcmFileFormat: Cannot determine Version of MetaHeader
  W: no data dictionary loaded, check environment variable: DCMDICTPATH
  E: Store Failed, file: dcmtkpp.4mR/data.dcm:
  E: 0006:0213 Data dictionary missing
  E: Store SCU Failed: 0006:0213 Data dictionary missing
  debian/rules:18: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 255
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151211163341.wUBAYFVFa6/dcmtkpp-0.3.1'
  debian/rules:11: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


dcmtkpp.0.3.1-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: dcmtkpp
Source-Version: 0.3.1-3

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

Debian distribution maintenance software
pp.
Julien Lamy  (supplier of updated dcmtkpp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Dec 2015 16:34:21 +0100
Source: dcmtkpp
Binary: libdcmtkpp0 libdcmtkpp0-dev libdcmtkpp0-doc
Architecture: source amd64 all
Version: 0.3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Julien Lamy 
Description:
 libdcmtkpp0 - C++ wrapper library for the DCMTK DICOM toolkit
 libdcmtkpp0-dev - C++ wrapper library for the DCMTK DICOM toolkit (development 
file
 libdcmtkpp0-doc - C++ wrapper library for the DCMTK DICOM toolkit 
(documentation)
Closes: 807675
Changes:
 dcmtkpp (0.3.1-3) unstable; urgency=medium
 .
   * Disable network-related tests at build time (Closes: #807675)
Checksums-Sha1:
 44e67d49f20bd182fc179ff70fe0cccdb939c859 2244 dcmtkpp_0.3.1-3.dsc
 30ce53efc48e59cd9294525eb69eaf2e25c2b72c 224717 dcmtkpp_0.3.1.orig.tar.gz
 174e5b3606db064757b737004218d47bdc1a0fd8 10628 dcmtkpp_0.3.1-3.debian.tar.xz
 7491817743b56638f48546a5f5e2d1d3725fac96 57628 
libdcmtkpp0-dev_0.3.1-3_amd64.deb
 8699a9a2662088d90189beb0a75ba74e25b35752 252714 libdcmtkpp0-doc_0.3.1-3_all.deb
 b1e9f089c90e7f0788c742d970c9139765777914 606692 libdcmtkpp0_0.3.1-3_amd64.deb
Checksums-Sha256:
 9310b4a2b7c39ede4d6fb548550bdda27d06cb2be09166ee7293bdf4d584c42e 2244 
dcmtkpp_0.3.1-3.dsc
 2ea4add1318ac006939241592dc01804a9ad916b54c076faea8dfcaf8b7046f2 224717 
dcmtkpp_0.3.1.orig.tar.gz
 

Bug#750904: marked as done (scidavis: FTBFS on arm*: fatal error: sipAPIscidavis.h: No such file or directory)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 19:06:38 +0100
with message-id <20151213180638.ga31...@georges.khaznadar.fr>
and subject line Re: Build on arm*
has caused the Debian Bug report #750904,
regarding scidavis: FTBFS on arm*: fatal error: sipAPIscidavis.h: No such file 
or directory
to be marked as done.

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

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


-- 
750904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scidavis
Version: 1.D5-1
Severity: serious
Justification: FTBFS

Hi,

your package no longer builds on arm*:
| g++ -c -pipe -O2 -D_REENTRANT -Wall -W -DSCRIPTING_CONSOLE -DSCRIPTING_DIALOG 
-DSCRIPTING_MUPARSER -DPYTHON_CONFIG_PATH=\"/usr/../etc\" 
-DPYTHON_UTIL_PATH=\"/usr/share/scidavis\" -DSCRIPTING_PYTHON -DQT_PLUGIN 
-DTS_PATH=\"/usr/share/scidavis/translations\" 
-DDOC_PATH=\"/usr/share/doc/scidavis\" 
-DPLUGIN_PATH=\"/usr/lib/scidavis/plugins\" -DLEGACY_CODE_0_2_x -DQT_NO_DEBUG 
-DQT_SVG_LIB -DQT_QT3SUPPORT_LIB -DQT3_SUPPORT -DQT_XML_LIB -DQT_OPENGL_LIB 
-DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED 
-I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore 
-I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui 
-I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtXml 
-I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtSvg -I/usr/include/qt4 
-I/usr/include/qt4/QtAssistantClient -I/usr/include/qt4/QtAssistant 
-I/usr/include/python2.7 -I/usr/include/python2.7 -I/usr/include/qwt-qt4 
-I/usr/include/qwtplot3d-qt4 -I/usr/include/muParser -Isrc -Isrc/future 
-I/usr/X11R6/include -I/«PKGBU
 ILDDIR»/tmp/scidavis -I. -o ../tmp/scidavis/PythonScript.o src/PythonScript.cpp
| src/PythonScript.cpp: In member function 'virtual QVariant 
PythonScript::eval()':
| src/PythonScript.cpp:209:45: warning: suggest parentheses around assignment 
used as truth value [-Wparentheses]
| } else if (pystring = PyObject_Str(pyret)) {
|  ^
| g++ -c -pipe -O2 -D_REENTRANT -Wall -W -DSCRIPTING_CONSOLE -DSCRIPTING_DIALOG 
-DSCRIPTING_MUPARSER -DPYTHON_CONFIG_PATH=\"/usr/../etc\" 
-DPYTHON_UTIL_PATH=\"/usr/share/scidavis\" -DSCRIPTING_PYTHON -DQT_PLUGIN 
-DTS_PATH=\"/usr/share/scidavis/translations\" 
-DDOC_PATH=\"/usr/share/doc/scidavis\" 
-DPLUGIN_PATH=\"/usr/lib/scidavis/plugins\" -DLEGACY_CODE_0_2_x -DQT_NO_DEBUG 
-DQT_SVG_LIB -DQT_QT3SUPPORT_LIB -DQT3_SUPPORT -DQT_XML_LIB -DQT_OPENGL_LIB 
-DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED 
-I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore 
-I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui 
-I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtXml 
-I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtSvg -I/usr/include/qt4 
-I/usr/include/qt4/QtAssistantClient -I/usr/include/qt4/QtAssistant 
-I/usr/include/python2.7 -I/usr/include/python2.7 -I/usr/include/qwt-qt4 
-I/usr/include/qwtplot3d-qt4 -I/usr/include/muParser -Isrc -Isrc/future 
-I/usr/X11R6/include -I/«PKGBU
 ILDDIR»/tmp/scidavis -I. -o ../tmp/scidavis/PythonScripting.o 
src/PythonScripting.cpp
| src/PythonScripting.cpp:60:28: fatal error: sipAPIscidavis.h: No such file or 
directory
|  #include "sipAPIscidavis.h"
| ^
| compilation terminated.
| make[3]: *** [../tmp/scidavis/PythonScripting.o] Error 1

Full build logs:
  
https://buildd.debian.org/status/fetch.php?pkg=scidavis=armhf=1.D5-1=1401679921
  
https://buildd.debian.org/status/fetch.php?pkg=scidavis=armel=1.D5-1=1401653966

Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Bug 750904 is fixed now.

Patrick Winnertz a écrit :
> Hey George,
> 
> you can close that bug here, too ;) scidavis has successfully build on
> arm*. I don't want to do it, because it's your package ;)
> 
> Greetings
> Patrick
> 

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



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


Processed: tagging 807705, tagging 728955, tagging 807737, found 807502 in 2.25+Atmel3.5.0-1, tagging 807564

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 807705 + sid stretch
Bug #807705 [src:xserver-xorg-video-openchrome] xserver-xorg-video-openchrome: 
FTBFS: /usr/include/xorg/os.h:558:1: error: expected identifier or '(' before 
'__extension__'
Added tag(s) stretch and sid.
> tags 728955 + sid stretch
Bug #728955 [src:libatomic-ops] FTBFS on powerpc: FAIL: test_stack
Added tag(s) stretch and sid.
> tags 807737 + sid stretch
Bug #807737 [src:sqwebmail-de] sqwebmail-de: FTBFS: debian/rules:14: recipe for 
target 'override_dh_auto_build' failed
Added tag(s) stretch and sid.
> found 807502 2.25+Atmel3.5.0-1
Bug #807502 {Done: Hakan Ardo } [binutils-avr] gcc-avr: 
Missing support for atxmega384d3 since last upload
Marked as found in versions binutils-avr/2.25+Atmel3.5.0-1.
> tags 807564 + sid
Bug #807564 [src:digikam] digikam: FTBFS: Could not find a package 
configuration file provided by "Marble"
Added tag(s) sid.
> thanks
Stopping processing here.

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



Bug#804541: marked as done (lvm2 Build-depends on obsolete package libcorosync-dev)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 18:30:38 +
with message-id 
and subject line Bug#804541: fixed in lvm2 2.02.133-2
has caused the Debian Bug report #804541,
regarding lvm2 Build-depends on obsolete package libcorosync-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.)


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

Package: lvm2
Version: 2.02.133-1
Severity: serious
Tags: patch

Your package build-depends on libcorosync-dev which is no longer built 
by the corosync source package.


I replaced the build-depends on libcorosync-dev with 
libcorosync-core-dev and tried a build in a raspbian stretch-staging 
environment. Through build-testing I found I also needed to add 
libquorum-dev, libcmap-dev and libcpg-dev to get a sucessful build.


I have uploaded this to raspbian, a debdiff is available at 
http://debdiffs.raspbian.org/main/l/lvm2/lvm2_2.02.133-1%2brpi1.debdiff 
no intent to NMU in Debian.
--- End Message ---
--- Begin Message ---
Source: lvm2
Source-Version: 2.02.133-2

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

Debian distribution maintenance software
pp.
Bastian Blank  (supplier of updated lvm2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 13 Dec 2015 18:02:40 +0100
Source: lvm2
Binary: lvm2 lvm2-udeb clvm libdevmapper-dev libdevmapper1.02.1 
libdevmapper1.02.1-udeb dmsetup dmsetup-udeb libdevmapper-event1.02.1 dmeventd 
liblvm2app2.2 liblvm2cmd2.02 liblvm2-dev python-lvm2 python3-lvm2
Architecture: source amd64
Version: 2.02.133-2
Distribution: unstable
Urgency: medium
Maintainer: Debian LVM Team 
Changed-By: Bastian Blank 
Description:
 clvm   - Cluster LVM Daemon for lvm2
 dmeventd   - Linux Kernel Device Mapper event daemon
 dmsetup- Linux Kernel Device Mapper userspace library
 dmsetup-udeb - Linux Kernel Device Mapper userspace library (udeb)
 libdevmapper-dev - Linux Kernel Device Mapper header files
 libdevmapper-event1.02.1 - Linux Kernel Device Mapper event support library
 libdevmapper1.02.1 - Linux Kernel Device Mapper userspace library
 libdevmapper1.02.1-udeb - Linux Kernel Device Mapper userspace library (udeb)
 liblvm2-dev - LVM2 libraries - development files
 liblvm2app2.2 - LVM2 application library
 liblvm2cmd2.02 - LVM2 command library
 lvm2   - Linux Logical Volume Manager
 lvm2-udeb  - Linux Logical Volume Manager (udeb)
 python-lvm2 - LVM2 application library - Python 2 binding
 python3-lvm2 - LVM2 application library - Python 3 binding
Closes: 804541 807279
Changes:
 lvm2 (2.02.133-2) unstable; urgency=medium
 .
   * Build-depend on a lot corosync stuff. (closes: #804541)
   * Drop event plugin directory move.  This moves the plugins back into
 the main library path. (closes: #807279)
Checksums-Sha1:
 d9f92b3f081b26b39fc2cdb9d2c977b8b118b3e6 2678 lvm2_2.02.133-2.dsc
 e79503aa8029eca68d4c256bba2f136c759fe2fe 30872 lvm2_2.02.133-2.debian.tar.xz
 dcc4143f397c9899ef103191d1a9cf3326e55a76 492208 clvm_2.02.133-2_amd64.deb
 7c85a0fbbe3fa4ad0ef0195bf98b9e9f400b1ba9 58766 dmeventd_1.02.110-2_amd64.deb
 75adcc1dcc679db159802f25d6892412acda2d66 38934 
dmsetup-udeb_1.02.110-2_amd64.udeb
 c85cab6a6d3e701545f5395d76135a5044c15419 92354 dmsetup_1.02.110-2_amd64.deb
 c73b2338ef2381097e2fdf90e58a553c3b52acbe 6 
libdevmapper-dev_1.02.110-2_amd64.deb
 3eeb6ff64dd8f16117e3797327792a8fb88bbe25 40046 
libdevmapper-event1.02.1_1.02.110-2_amd64.deb
 1dac9022979174aafdab98d2f4a4729fd22f5b53 118402 
libdevmapper1.02.1-udeb_1.02.110-2_amd64.udeb
 86922f1921d23afde8b74f48a9ec8c26b18203f2 176844 
libdevmapper1.02.1_1.02.110-2_amd64.deb
 b7633a1c18cd05d466aab0e6ba51708573359744 100384 
liblvm2-dev_2.02.133-2_amd64.deb
 ec1437768a6bc8b78ad318c5f70a23660f53ad50 479748 
liblvm2app2.2_2.02.133-2_amd64.deb
 e625c6863981a76cd9e3ff78cafb99f8757b2864 605242 
liblvm2cmd2.02_2.02.133-2_amd64.deb
 

Processed: affects 799322, found 775385 in 1.16.6-1, found 771085 in 3.18.2-1

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> affects 799322 + libpocl-dbg
Bug #799322 [src:pocl] pocl: FTBFS: (gcc5 related?) symbols mismatches + test 
failures
Added indication that 799322 affects libpocl-dbg
> found 775385 1.16.6-1
Bug #775385 [lightdm] lightdm: unowned symlink after purge (policy 6.8, 10.8): 
/etc/systemd/system/display-manager.service
Marked as found in versions lightdm/1.16.6-1.
> found 771085 3.18.2-1
Bug #771085 [gdm3] gdm3: unowned symlink after purge (policy 6.8, 10.8): 
/etc/systemd/system/display-manager.service
Marked as found in versions gdm3/3.18.2-1.
> thanks
Stopping processing here.

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



Processed: severity of 807800 is important

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 807800 important
Bug #807800 [heimdall-flash] heimdall-flash: heimdall fails on files larger 
than 2GB
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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



Bug#804590: redhat-cluster: build-depends on libcorosync-dev which is no longer built

2015-12-13 Thread gregor herrmann
On Mon, 09 Nov 2015 20:39:32 +0100, Emilio Pozuelo Monfort wrote:

> Your package build-depends on libcorosync-dev which is no longer
> built by corosync. Please switch to the appropriate packages to
> build against the new version.

Afer replacing libcorosync-dev with libcorosync-common-dev and
libconfdb-dev, the build ends with:

make[5]: Entering directory '/build/redhat-cluster-3.1.8/config/plugins/xml'
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wformat=2 -Wshadow -Wmissing-prototypes -Wstrict-prototypes 
-Wdeclaration-after-statement -Wpointer-arith -Wwrite-strings -Wcast-align 
-Wbad-function-cast -Wmissing-format-attribute -Wformat-security 
-Wformat-nonliteral -Wno-long-long -Wno-strict-aliasing -Wmissing-declarations 
-O2 -ggdb3 -MMD -I/build/redhat-cluster-3.1.8/make 
-DDEFAULT_CONFIG_DIR=\"/etc/cluster\" -DDEFAULT_CONFIG_FILE=\"cluster.conf\" 
-DLOGDIR=\"/var/log/cluster\" -DSYSLOGFACILITY=LOG_LOCAL4 
-DSYSLOGLEVEL=LOG_INFO -DRELEASE_VERSION=\"3.1.8\" -Wall -Wformat=2 -Wshadow 
-Wmissing-prototypes -Wstrict-prototypes -Wdeclaration-after-statement 
-Wpointer-arith -Wwrite-strings -Wcast-align -Wbad-function-cast 
-Wmissing-format-attribute -Wformat-security -Wformat-nonliteral -Wno-long-long 
-Wno-strict-aliasing -Wmissing-declarations -O2 -ggdb3 -MMD 
-I/build/redhat-cluster-3.1.8/make -DDEFAULT_CONFIG_DIR=\"/etc/cluster\" 
-DDEFAULT_CONFIG_FILE=\"cluster.conf\" -DLOGDIR=\"/var/log/cluster\" 
-DSYSLOGFACILITY=LOG_LOCAL4 -DSYSLOGLEVEL=LOG_INFO -DRELEASE_VERSION=\"3.1.8\" 
-Wall -Wformat=2 -Wshadow -Wmissing-prototypes -Wstrict-prototypes 
-Wdeclaration-after-statement -Wpointer-arith -Wwrite-strings -Wcast-align 
-Wbad-function-cast -Wmissing-format-attribute -Wformat-security 
-Wformat-nonliteral -Wno-long-long -Wno-strict-aliasing -Wmissing-declarations 
-O2 -ggdb3 -MMD -I/build/redhat-cluster-3.1.8/make 
-DDEFAULT_CONFIG_DIR=\"/etc/cluster\" -DDEFAULT_CONFIG_FILE=\"cluster.conf\" 
-DLOGDIR=\"/var/log/cluster\" -DSYSLOGFACILITY=LOG_LOCAL4 
-DSYSLOGLEVEL=LOG_INFO -DRELEASE_VERSION=\"3.1.8\" -Wall -Wformat=2 -Wshadow 
-Wmissing-prototypes -Wstrict-prototypes -Wdeclaration-after-statement 
-Wpointer-arith -Wwrite-strings -Wcast-align -Wbad-function-cast 
-Wmissing-format-attribute -Wformat-security -Wformat-nonliteral -Wno-long-long 
-Wno-strict-aliasing -Wmissing-declarations -O2 -ggdb3 -MMD 
-I/build/redhat-cluster-3.1.8/make -DDEFAULT_CONFIG_DIR=\"/etc/cluster\" 
-DDEFAULT_CONFIG_FILE=\"cluster.conf\" -DLOGDIR=\"/var/log/cluster\" 
-DSYSLOGFACILITY=LOG_LOCAL4 -DSYSLOGLEVEL=LOG_INFO -DRELEASE_VERSION=\"3.1.8\" 
-fPIC -D_GNU_SOURCE `xml2-config --cflags` -I/usr/include   -c -o config.o 
/build/redhat-cluster-3.1.8/config/plugins/xml/config.c
/build/redhat-cluster-3.1.8/config/plugins/xml/config.c:6:35: fatal error: 
corosync/lcr/lcr_comp.h: No such file or directory
compilation terminated.

and corosync/lcr/lcr_comp.h seems to be gone from the archive.

Looks like this need more work than just changing build dependencies.


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Eagles: Best Of My Love


signature.asc
Description: Digital Signature


Bug#800216: marked as done (gniall: Please migrate a supported debhelper compat level)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 21:17:35 -0200
with message-id 

and subject line gniall: diff for NMU version 0.7.1-7.1
has caused the Debian Bug report #800216,
regarding gniall: Please migrate a supported debhelper compat level
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.)


-- 
800216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gniall
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package gniall is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Hi,
First, my apologies, just after send the first email to close this bug, I
noticed that some issues was not fixed, so I decided to solve them and
upload again.

I uploaded a NMU to 10-day/delay queue. Feel free to cancel this upload if
needed.

The debian/changelog is:

gniall (0.7.1-7.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Update DH level to 9 to avoid a FTBFS. (Closes: #800216)
  * debian/control:
 - Added the ${misc:Depends} variable to provide the
   right install dependencies.
 - Bumped Standards-Version to 3.9.6.
  * debian/watch: added.

I attached a debdiff.

Thanks.

Regards,

Raphael Mota


gniall.debdiff
Description: Binary data
--- End Message ---


Bug#793187: marked as done (arb: FTBFS with gcc 4.9.2+)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 23:17:08 +
with message-id 
and subject line Bug#793187: fixed in arb 6.0.2-1+deb8u1
has caused the Debian Bug report #793187,
regarding arb: FTBFS with gcc 4.9.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.)


-- 
793187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: arb
Version: 6.0.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

from a rebuild in jessie, but sid fails the same way, just with 4.9.3:

[...]
make[4]: Entering directory '/tmp/buildd/arb-6.0.2'
All tools needed for ARB compilation have been located.
 Environment [start]
ARBHOME='/tmp/buildd/arb-6.0.2'
PATH='/tmp/buildd/arb-6.0.2/bin:/tmp/buildd/arb-6.0.2/bin:/usr/sbin:/usr/bin:/sbin:/bin'
LD_LIBRARY_PATH='/tmp/buildd/arb-6.0.2/lib:/tmp/buildd/arb-6.0.2/lib:'
 Environment [end]
Compiler version check:
  - Your compiler is 'gcc' version '4.9.2'
This version is not in the list of supported gcc-versions:
* 4.3.1
* 4.3.2
* 4.3.3
* 4.3.4
* 4.4.1
* 4.4.3
* 4.4.5
* 4.4.6
* 4.4.7
* 4.5.2
* 4.6.1
* 4.6.2
* 4.6.3
* 4.7.1
* 4.7.2
* 4.7.3
* 4.8.0
* 4.8.1
* 4.8.2
* 4.8.3
* 4.9.0
* 4.9.1
  - You may either ..
- add your version to ALLOWED_gcc_VERSIONS in the Makefile and try it out or
- switch to one of the allowed versions (see arb_README_gcc.txt for 
installing
  a different version of gcc)

Makefile:739: recipe for target 'check_GCC_VERSION' failed
make[4]: *** [check_GCC_VERSION] Error 1
make[4]: Leaving directory '/tmp/buildd/arb-6.0.2'
Makefile:1971: recipe for target 'arb' failed
make[3]: *** [arb] Error 2
make[3]: Leaving directory '/tmp/buildd/arb-6.0.2'
Makefile:2304: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/tmp/buildd/arb-6.0.2'
debian/rules:40: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/tmp/buildd/arb-6.0.2'
debian/rules:28: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Andreas
--- End Message ---
--- Begin Message ---
Source: arb
Source-Version: 6.0.2-1+deb8u1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 10 Dec 2015 10:55:21 +0100
Source: arb
Binary: arb libarb libarb-dev arb-common arb-doc
Architecture: source amd64 all
Version: 6.0.2-1+deb8u1
Distribution: jessie
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 arb- Graphical suite for phylogenetic sequence analysis
 arb-common - Graphical suite for phylogenetic sequence analysis (common files)
 arb-doc- Graphical suite for phylogenetic sequence analysis (documentation
 libarb - Graphical suite for phylogenetic sequence analysis (libraries)
 libarb-dev - Graphical suite for phylogenetic sequence analysis (development f
Closes: 793187
Changes:
 arb (6.0.2-1+deb8u1) jessie; urgency=medium
 .
   * Skip compiler version check at all
 Closes: #793187
Checksums-Sha1:
 60fef97001acdd3c7ab6506d065bb72859c87ce7 2601 arb_6.0.2-1+deb8u1.dsc
 4ba2b0c734ddc8378a3e6f7c73d273a101a18edd 119088 
arb_6.0.2-1+deb8u1.debian.tar.xz
 e3b79f702d2eca4cf061ed645c1675a9e91182d6 1956560 arb_6.0.2-1+deb8u1_amd64.deb
 571063dd572b172aa2321613d3d962540b225534 572130 libarb_6.0.2-1+deb8u1_amd64.deb
 cb31f3b211c6d74eede8293081c5259583d1d8b7 401944 
libarb-dev_6.0.2-1+deb8u1_amd64.deb
 80a55337830d586d340745fc403467fd85a69599 3606536 
arb-common_6.0.2-1+deb8u1_all.deb
 

Processed: Re: Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

2015-12-13 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 gcc-5.0
Bug #807756 [libtasn1-6] gnubg: fails to start. hangs using 100% of one cpu core
Bug reassigned from package 'libtasn1-6' to 'gcc-5.0'.
Warning: Unknown package 'gcc-5.0'
Warning: Unknown package 'gcc-5.0'
Ignoring request to alter found versions of bug #807756 to the same values 
previously set
Warning: Unknown package 'gcc-5.0'
Warning: Unknown package 'gcc-5.0'
Ignoring request to alter fixed versions of bug #807756 to the same values 
previously set
Warning: Unknown package 'gcc-5.0'
> severity -1 important
Bug #807756 [gcc-5.0] gnubg: fails to start. hangs using 100% of one cpu core
Warning: Unknown package 'gcc-5.0'
Severity set to 'important' from 'grave'
Warning: Unknown package 'gcc-5.0'

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



Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

2015-12-13 Thread Russ Allbery
Control: reassign -1 gcc-5.0
Control: severity -1 important

Andreas Metzler  writes:

> Some more points of strangeness:
> jessie's gnubg package (1.04.000-1) works on current stretch.
> Rebuilding the jessie source on current sid produces a binary which
> fails.
> Rebuilding with DEB_BUILD_OPTIONS=noopt works
> Rebuilding on current sid with gcc-4.9 produces a working package.
> Rebuilding either the jessie or the sid source with -O1 segfaults at
> start:
> (gdb) run
> Starting program: /usr/games/gnubg
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

> Program received signal SIGSEGV, Segmentation fault.
> memcpy (__dest=0x833070,
> __dest@entry= detected (257).>, __src=0x7fffea09a46e,
> __src@entry= detected (257).>, __len=6,
> __len@entry= detected (257).>) at /usr/include/x86_64-linux-gnu/bits/string3.h:53
> 53

Hrm.  Okay, so the compiler is doing something weird, and this isn't a
problem with libtasn1.  Thanks for the additional information!  I'm going
to reassign this to gcc-5, and might upload a package built explicitly
with gcc-4.9 as a workaround.

-- 
Russ Allbery (r...@debian.org)   



Bug#807878: gnome: Gnome freezes when root windows are open on user screen.

2015-12-13 Thread Edilson Azevedo
Package: gnome
Version: 1:3.14+3
Severity: critical
Justification: causes serious data loss

*** Scenario ***

Non-classic gnome logged as a regular user and some root windows open. e.g.
synaptic, nautilus-as-root, root-terminal, etc.

*** Causing the problem ***

Hitting the upper left corner of the screen with mouse cursor - or - clicking
over Activities.

*** Problem ***

Screen freezes (no usual shrink) cursor moves. No reaction to clicks.

*** Observation ***

top, running on a  text window shows gnome-settings-daemon
busy (50%).

Logs like syslog, messages, etc. get huge filled with several messages like
below:

<<< gnome-session[1367]: (gnome-settings-daemon:1434): dconf-CRITICAL **:
unable to create file '/run/user/1000/dconf/user': Access denied.  dconf will
not work properly. >>>

ls -l /run/user/1000/dconf/user --> -rw--- 1 root root 2 Dec 13 21:42
/run/user/1000/dconf/user !!!
rebooting:
ls -l /run/user/1000/dconf/user --> -rw--- 1 user user 2 Dec 13 21:54
/run/user/1000/dconf/user

*** My conclusion ***

For some reason the owner of the file referred above turns from user to root.
>From this moment on gnome system is desperately trying to access it as user,
overloading the machine, filling logs with same message, and no escape.

*** My comments ***

1) As I don't know which part of software is responsible for
/run/user/1000/dconf/user writing and creation I blame gnome.
2) It can be harmful to the system because when one doesn't what to do, he/she
will press reset button and get corrupted files.
3) A workaround for the crash is to hit  and .
4) By now, when I need work as root, I hit  and startx. Some
say it might lead to safety problems ...

Thanks for your patience, anyway, I believe solution is closer.



-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

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

Versions of packages gnome depends on:
ii  alacarte   3.11.91-2
ii  avahi-daemon   0.6.31-5
ii  bijiben3.14.2-1+b1
ii  brasero3.11.4-1.1
ii  cheese 3.14.1-2
ii  cups-pk-helper 0.2.5-2+b1
ii  desktop-base   8.0.2
ii  evolution  3.12.9~git20141130.241663-1+b1
ii  evolution-plugins  3.12.9~git20141130.241663-1+b1
ii  file-roller3.14.1-1
ii  gedit  3.14.0-3
ii  gedit-plugins  3.14.0-2
ii  gimp   2.8.14-1+b1
ii  gnome-clocks   3.14.1-1
ii  gnome-color-manager3.14.1-1
ii  gnome-core 1:3.14+3
ii  gnome-documents3.14.2-1
ii  gnome-games1:3.14+3
ii  gnome-getting-started-docs 3.14.1-1
ii  gnome-logs 3.14.2-1
ii  gnome-maps 3.14.1.2-1
ii  gnome-music3.14.1-1
ii  gnome-nettool  3.8.1-1
ii  gnome-orca 3.14.0-4
ii  gnome-photos   3.14.2-1
ii  gnome-shell-extension-weather  0~20140924.git7e28508-1
ii  gnome-sound-recorder   3.14.0.1-1
ii  gnome-tweak-tool   3.14.2-2
ii  goobox 3.3.1-6
ii  gstreamer1.0-libav 1.4.4-2
ii  gstreamer1.0-plugins-ugly  1.4.4-2+b1
ii  hamster-applet 2.91.3+git20120514.b9fec3e1-1
ii  inkscape   0.48.5-3
ii  libgtk2-perl   2:1.2492-4
ii  libreoffice-calc   1:4.3.3-2+deb8u2
ii  libreoffice-evolution  1:4.3.3-2+deb8u2
ii  libreoffice-gnome  1:4.3.3-2+deb8u2
ii  libreoffice-impress1:4.3.3-2+deb8u2
ii  libreoffice-writer 1:4.3.3-2+deb8u2
ii  nautilus-sendto3.8.2-1
ii  network-manager-gnome  0.9.10.0-2
ii  polari 3.14.1-1
ii  rhythmbox  3.1-1
ii  rhythmbox-plugin-cdrecorder3.1-1
ii  rhythmbox-plugins  3.1-1
ii  rygel-playbin  0.24.2-1+b1
ii  rygel-tracker  0.24.2-1+b1
ii  seahorse   3.14.0-2
ii  simple-scan3.14.0-1
ii  telepathy-gabble   0.18.3-1+b1
ii  telepathy-rakia0.8.0-3
ii  telepathy-salut0.8.1-4
ii  totem-plugins  3.14.0-2
ii  transmission-gtk   2.84-0.2
ii  vinagre3.14.1-1
ii  xdg-user-dirs-gtk  0.10-1

Versions of packages gnome recommends:
pn  gnome-software  

Versions of packages gnome suggests:
pn  iceweasel-l10n-all 
pn  xul-ext-adblock-plus   
pn  xul-ext-gnome-keyring  

Versions of packages gnome-core depends on:
ii  

Bug#801597: marked as done (PIE and stack protection appear missing since update to GCC-5)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 22:13:17 +
with message-id 
and subject line Bug#801597: fixed in hardening-wrapper 2.8+nmu1
has caused the Debian Bug report #801597,
regarding PIE and stack protection appear missing since update to GCC-5
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.)


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

It appears that the behavior of hardening-wrapper has changed recently, and
now PIE and stack protection are missing.  mumble got a binNMU for the GCC-5
upgrade relating to library transitions for protobuf and zeroc-ice after which
these protections were missing where they had them before the binNMU.

Looking at the snapshot:
http://snapshot.debian.org/archive/debian/20141110T040546Z/pool/main/m/mumble/mumble_1.2.8-2_amd64.deb
mumble_1.2.8-2_amd64 hardening check:
Position Independent Executable: yes
Stack protected: yes
Fortify Source functions: yes (some protected functions found)
Read-only relocations: yes
Immediate binding: yes

Looking at Sid:
http://ftp.us.debian.org/debian/pool/main/m/mumble/mumble_1.2.8-2+b1_amd64.deb
mumble_1.2.8-2+b1_amd64 hardening check:
Position Independent Executable: no, normal executable!
Stack protected: no, not found!
Fortify Source functions: yes (some protected functions found)
Read-only relocations: yes
Immediate binding: yes

Reporting this as these are unexpected differences.


Also: is hardening-wrapper being deprecated?  I ask because lintian is
reporting it as such.  (See #711193)

Thanks.
   -- Chris

Chris Knadle
chris.kna...@coredump.us



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

Kernel: Linux 4.2.0-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
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: hardening-wrapper
Source-Version: 2.8+nmu1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated hardening-wrapper 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, 13 Dec 2015 21:48:47 +0100
Source: hardening-wrapper
Binary: hardening-wrapper hardening-includes
Architecture: source all amd64
Version: 2.8+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Package Hardening 
Changed-By: Matthias Klose 
Description:
 hardening-includes - Makefile for enabling compiler flags for security 
hardening
 hardening-wrapper - Compiler wrapper to enable security hardening flags
Closes: 801597 802579
Changes:
 hardening-wrapper (2.8+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Upload as 2.8+nmu1 (binutils already has a conflict against << 2.8, the
 assumption that 2.8 would be uploaded in time didn't go well).
   * Install diversions for GCC 5 and GCC 6. Closes: #801597.
   * Divert the host_alias prefixed ld binaries instead of the unprefixed
 binaries. Closes: #802579.
   * Build-depend on binutils (>= 2.25.90).
Checksums-Sha1:
 bd69b2ba7d50cecda788107af50fb3f31a495ed2 1839 hardening-wrapper_2.8+nmu1.dsc
 05f2533761dbb646f93ca0ae36cc08ee47996cf8 20004 
hardening-wrapper_2.8+nmu1.tar.xz
 84dedf00abfa56c5abdd48309a294b522ec05655 17646 
hardening-includes_2.8+nmu1_all.deb
 6c1106ed3713f92cc78da62825ba60a65b46ecea 1 
hardening-wrapper_2.8+nmu1_amd64.deb
Checksums-Sha256:
 9b701786af84a645ab38ddb32e5c80f49bdcbdf69e93f73f78f5c34c4a7b2065 1839 
hardening-wrapper_2.8+nmu1.dsc
 c7b630df59052b774163e61aeb80e718a4503071a891e84208716e0be11ea7e6 20004 

Processed: severity of 799275 is important

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 799275 important
Bug #799275 [src:gtk+2.0] [GDK] patch - avoid integer overflow when allocating 
a large block of memory
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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



Bug#802579: marked as done (binutils changed ld.bfd / ld.gold files and symlinks)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 22:13:17 +
with message-id 
and subject line Bug#802579: fixed in hardening-wrapper 2.8+nmu1
has caused the Debian Bug report #802579,
regarding binutils changed ld.bfd / ld.gold files and symlinks
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.)


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

Package: hardening-wrapper
Version: 0.27
Severity: important
Tags: sid stretch

The binutils upload currently in NEW (2.25.51.20151020-1) changed ld.bfd / 
ld.gold files and symlinks, so hardening-wrapper now needs to divert the triplet 
prefixed names.


See https://ftp-master.debian.org/new/binutils_2.25.51.20151020-1.html
or https://people.debian.org/~doko/tmp/binutils/.
--- End Message ---
--- Begin Message ---
Source: hardening-wrapper
Source-Version: 2.8+nmu1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated hardening-wrapper 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, 13 Dec 2015 21:48:47 +0100
Source: hardening-wrapper
Binary: hardening-wrapper hardening-includes
Architecture: source all amd64
Version: 2.8+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Package Hardening 
Changed-By: Matthias Klose 
Description:
 hardening-includes - Makefile for enabling compiler flags for security 
hardening
 hardening-wrapper - Compiler wrapper to enable security hardening flags
Closes: 801597 802579
Changes:
 hardening-wrapper (2.8+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Upload as 2.8+nmu1 (binutils already has a conflict against << 2.8, the
 assumption that 2.8 would be uploaded in time didn't go well).
   * Install diversions for GCC 5 and GCC 6. Closes: #801597.
   * Divert the host_alias prefixed ld binaries instead of the unprefixed
 binaries. Closes: #802579.
   * Build-depend on binutils (>= 2.25.90).
Checksums-Sha1:
 bd69b2ba7d50cecda788107af50fb3f31a495ed2 1839 hardening-wrapper_2.8+nmu1.dsc
 05f2533761dbb646f93ca0ae36cc08ee47996cf8 20004 
hardening-wrapper_2.8+nmu1.tar.xz
 84dedf00abfa56c5abdd48309a294b522ec05655 17646 
hardening-includes_2.8+nmu1_all.deb
 6c1106ed3713f92cc78da62825ba60a65b46ecea 1 
hardening-wrapper_2.8+nmu1_amd64.deb
Checksums-Sha256:
 9b701786af84a645ab38ddb32e5c80f49bdcbdf69e93f73f78f5c34c4a7b2065 1839 
hardening-wrapper_2.8+nmu1.dsc
 c7b630df59052b774163e61aeb80e718a4503071a891e84208716e0be11ea7e6 20004 
hardening-wrapper_2.8+nmu1.tar.xz
 92d14f2d85dba5263842e97443c6038aa632b7aceecc4057c4d2a4e59f870184 17646 
hardening-includes_2.8+nmu1_all.deb
 3201848be5c920a0ab211543ec799b4cd30d72f2e86f477276ec8919380fcbd4 1 
hardening-wrapper_2.8+nmu1_amd64.deb
Files:
 e7b68f562e41ef2e0c5979aaee378796 1839 devel optional 
hardening-wrapper_2.8+nmu1.dsc
 e435386fe4a28c8d77b97a01f303360b 20004 devel optional 
hardening-wrapper_2.8+nmu1.tar.xz
 ac9c3a3f8f99aa52665e0b5edf39d3bb 17646 devel optional 
hardening-includes_2.8+nmu1_all.deb
 9d4424e87cd51a1752c0324841651904 1 devel optional 
hardening-wrapper_2.8+nmu1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbeHdAAoJEL1+qmB3j6b1LH4P+wd8Mm2NrOC2XtQWcr4dvS+K
DiqoHwwCvzCfIflXvg8xJ+dP/GAlHf6e9GQlTKE80Mf8Ggd8D0g4nOILKK6wBhjw
Sl5l3ouQy/wyBa3r/n1nN5ehtaziII02AFwV0IK6N72tWMT2eYrBUJZdBB6E3/ME
FkqMr55lWGE4p4sxcvbaDeeJd1l6W+0u1t2u1ZSwB7B1as+zMx5F0sRhp0gR9c2e
aRxI2NAcJ3ouKcqjZMuhhLeAiyIaEYpynTnQzphl0nr5zo3wsl02eWCsNAM7TuS4
NV/hpMn0I/KCVQMJdf+mGEEtCslD04P3zasvFjTGhTPJnogKnr/QBmmzkNzSC6ee
TCVFwskDBNRW4ZGIWFAR2rfMvRv/HuxHb3P5b7YUnaM0J2ZyQ0CPj6v6eCQMtE5c
ug7bGKH+t+dZSleEOipOigdNnaX/hAzphBoLnZNvE0D9CNka3Xtu1zr7KgBZPo2h
74qXXilZr1ROQBnVtwTkrhsJCkGfVM1dQ1sKHDX4V9LfbCckWP8TxEBBYciiCYlj
DxCbBIucWU+AAALq9auYIbRx5k3L0BNuhnBpkW8ISK8N7n7zIXzIAyUY6Vu83ecM

Bug#786836: marked as done (packaging not yet ready for mass/stable usage)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2015 23:02:47 +
with message-id 
and subject line Bug#786836: fixed in rustc 1.5.0+dfsg1-1
has caused the Debian Bug report #786836,
regarding packaging not yet ready for mass/stable usage
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.)


-- 
786836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rustc
Version: 1.0.0+dfsg1-1
Severity: serious

Even though Rust recently reached the 1.0 milestone,
compiler and ecosystem packaging still has to reach a
"ready for the masses" status.

As some bits are still missing (cargo, external libs) and 
other still under discussion (dynlibs, lang-extensions), 
this bug is left open in order to avoid a premature migration
to testing.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: rustc
Source-Version: 1.5.0+dfsg1-1

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated rustc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 10 Dec 2015 17:23:32 +0100
Source: rustc
Binary: rustc libstd-rust-1.5 libstd-rust-dev rust-gdb rust-lldb rust-doc
Architecture: source amd64 all
Version: 1.5.0+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Rust Maintainers 
Changed-By: Sylvestre Ledru 
Description:
 libstd-rust-1.5 - Rust standard libraries
 libstd-rust-dev - Rust standard libraries - development files
 rust-doc   - Rust systems programming language - Documentation
 rust-gdb   - Rust debugger (gdb)
 rust-lldb  - Rust debugger (lldb)
 rustc  - Rust systems programming language
Closes: 786836
Changes:
 rustc (1.5.0+dfsg1-1) unstable; urgency=medium
 .
   * New upstream release
 - We believe that we should let rust transit to testing
   (Closes: #786836)
   * Move away from hash to the same rust naming schema
Checksums-Sha1:
 2481019b3282ef139499b0411a53bf85072f75d1 2854 rustc_1.5.0+dfsg1-1.dsc
 07950894ca7f7b11e9c6f2929e4f85ee373274bd 32064597 
rustc_1.5.0+dfsg1.orig-dl.tar.gz
 07d75c281a8d4221e10a1ee91d9734aa4b4327fd 9375329 rustc_1.5.0+dfsg1.orig.tar.gz
 2c730868ab8982287a7099d6f0e6279dfd7d67a5 89564 
rustc_1.5.0+dfsg1-1.debian.tar.xz
 590188a8418ce6f1bf7da0c23ee7baa9eac46608 27516260 
libstd-rust-1.5_1.5.0+dfsg1-1_amd64.deb
 1921683833038ebef7a3d42f835a3bba15b0528b 9143532 
libstd-rust-dev_1.5.0+dfsg1-1_amd64.deb
 eef149ddc8327c0b5e13cccf7769757b0ee4851f 2591102 rust-doc_1.5.0+dfsg1-1_all.deb
 f3aa971f8a85be437c35a0604ae283251c01d859 56308 rust-gdb_1.5.0+dfsg1-1_amd64.deb
 84c59f271c06e7c719dbd114c3b5575f89b3661d 57060 
rust-lldb_1.5.0+dfsg1-1_amd64.deb
 2d6c4a4efe36326f9f797a15ae2273f8b8ced520 64776 rustc_1.5.0+dfsg1-1_amd64.deb
Checksums-Sha256:
 19833ca2d06bc849df0eebbabd74323b859ec2ed6ba654d4010573e3f05189a7 2854 
rustc_1.5.0+dfsg1-1.dsc
 a0d3fffac4908b695c8d7d1d15e5dbe337f57ce1cb8bb9676e0a603113a27337 32064597 
rustc_1.5.0+dfsg1.orig-dl.tar.gz
 0f040d176d03a2dc1bacf7a08c05a8f34bcac2db77809c3995e780c4767cd9b1 9375329 
rustc_1.5.0+dfsg1.orig.tar.gz
 5bd9b28423b469961cddb2154f411f8cfbc7df2ddaa67af5b893fedc903460f4 89564 
rustc_1.5.0+dfsg1-1.debian.tar.xz
 a12e13d796e48bec919fa5eac900b097373364a5864289efab1767f3321582a1 27516260 
libstd-rust-1.5_1.5.0+dfsg1-1_amd64.deb
 990bc4c66ee01fd6b9ee1608862b9a674342a956368ee733fb3bf3470b09311d 9143532 
libstd-rust-dev_1.5.0+dfsg1-1_amd64.deb
 b2fa895a179099c88bfa21952424d5adf7931cdce02d5590c128f8a7db096839 2591102 
rust-doc_1.5.0+dfsg1-1_all.deb
 

Bug#804590: [Debian-ha-maintainers] Bug#804590: redhat-cluster: build-depends on libcorosync-dev which is no longer built

2015-12-13 Thread Ferenc Wagner
gregor herrmann  writes:

> On Mon, 09 Nov 2015 20:39:32 +0100, Emilio Pozuelo Monfort wrote:
>
>> Your package build-depends on libcorosync-dev which is no longer
>> built by corosync. Please switch to the appropriate packages to
>> build against the new version.
>
> Afer replacing libcorosync-dev with libcorosync-common-dev and
> libconfdb-dev, the build ends with:
> [...]
> /build/redhat-cluster-3.1.8/config/plugins/xml/config.c:6:35: fatal error: 
> corosync/lcr/lcr_comp.h: No such file or directory
> compilation terminated.
>
> and corosync/lcr/lcr_comp.h seems to be gone from the archive.
>
> Looks like this need more work than just changing build dependencies.

The redhat-cluster package will be removed from the archive, we don't
intend to fix it.
-- 
Regards,
Feri.



Processed: reassign 807014 to ros-message-runtime, fixed 807014 in 0.4.12-3

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 807014 ros-message-runtime 0.4.12-2
Bug #807014 {Done: Jochen Sprickerhof } 
[message-runtime,ros-message-runtime] ros-message-runtime and message-runtime: 
error when trying to install together
Warning: Unknown package 'message-runtime'
Bug reassigned from package 'message-runtime,ros-message-runtime' to 
'ros-message-runtime'.
Ignoring request to alter found versions of bug #807014 to the same values 
previously set
No longer marked as fixed in versions ros-message-runtime/0.4.12-3.
Bug #807014 {Done: Jochen Sprickerhof } 
[ros-message-runtime] ros-message-runtime and message-runtime: error when 
trying to install together
Marked as found in versions ros-message-runtime/0.4.12-2.
> fixed 807014 0.4.12-3
Bug #807014 {Done: Jochen Sprickerhof } 
[ros-message-runtime] ros-message-runtime and message-runtime: error when 
trying to install together
Marked as fixed in versions ros-message-runtime/0.4.12-3.
> thanks
Stopping processing here.

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



Bug#807547: marked as done ([alfred] copyright file incomplete)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Dec 2015 01:48:51 +
with message-id 
and subject line Bug#807547: fixed in alfred 2015.2-1
has caused the Debian Bug report #807547,
regarding [alfred] copyright file incomplete
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.)


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


The copyright file is wrong and is missing entries for people like 

Files: *
Copyright: 2006-2015, Marek Lindner 

Files: gpsd/*
Copyright: 2013-2015, Andrew Lunn 
2006-2015, Simon Wunderlich 
License: GPL-2

Files: debugfs.*
Copyright: 2009, Clark Williams 
2009, Xiao Guangrong 
License: GPL-2
--- End Message ---
--- Begin Message ---
Source: alfred
Source-Version: 2015.2-1

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

Debian distribution maintenance software
pp.
Steffen Moeller  (supplier of updated alfred 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, 14 Dec 2015 01:46:20 +0100
Source: alfred
Binary: alfred
Architecture: source amd64
Version: 2015.2-1
Distribution: unstable
Urgency: low
Maintainer: Steffen Moeller 
Changed-By: Steffen Moeller 
Description:
 alfred - Almighty Lightweight Fact Remote Exchange Daemon
Closes: 807546 807547 807549 807550 807551 807552 807555 807562 807563
Changes:
 alfred (2015.2-1) unstable; urgency=low
 .
   * New upstream version (Closes: #807555)
 .
   [Contributions by Franz Schrober]
   * Added debian/watch file and signing key (Closes: #807550)
   * Reviewed debian/copyright,
 also added Franz to copyright holders of debian/* (Closes: #807547)
   * Corrected debian/README (Closes: #807549)
   * Corrected home page URL (Closes: #807552)
   * Added pkg-config to build-dependencies (Closes: #807551)
   * Added 64 bit I/O API to enable large file support (Closes: #807563)
   * Further hardened hardining (Closes: #807562)
   * Likely-fixed: Builds on non-linux systems (Closes: #807546)
Checksums-Sha1:
 22dd76e4b1d34e47b909de83a11138bafc77c0e1 1744 alfred_2015.2-1.dsc
 a027de85edad23d835f3da9ed7101587e31dcac4 54989 alfred_2015.2.orig.tar.gz
 89b9dbafd71013b3ad6e990427d545cef7411c99 4404 alfred_2015.2-1.debian.tar.xz
 d7c1114877822a033170628aa8fd3cf93736ec1d 39584 alfred_2015.2-1_amd64.deb
Checksums-Sha256:
 ed25646273f80bd86d1a0724ebf004372825c845623b043a5d0cf0ecc10ec425 1744 
alfred_2015.2-1.dsc
 7ae81e21de64891ce55cd9ab81e98fa8aac66a89237a149e8bad5dcffb1ad933 54989 
alfred_2015.2.orig.tar.gz
 627049145440b010f583b134090aec69fb15418c5892830f4401712a9774da37 4404 
alfred_2015.2-1.debian.tar.xz
 55942f3f8d1eb8658e275d7cbbb367cf8d650abc9cb418a49d81368520a12f56 39584 
alfred_2015.2-1_amd64.deb
Files:
 361fd70d180da81d9590c6402c669185 1744 net optional alfred_2015.2-1.dsc
 e50bd17753f824fa24d3914259ab0395 54989 net optional alfred_2015.2.orig.tar.gz
 a0d14907f804898545f2c57931f795e8 4404 net optional 
alfred_2015.2-1.debian.tar.xz
 ccfd9b933c9dab7dce9b23d552f75312 39584 net optional alfred_2015.2-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbhwuAAoJEC/YvtrAIO7RIu4P/0XDhLnHXXyvugkEdrdeMdfK
uNhqULMmZ6Thh7ydSzOtEUPIR/EgzBRaDyOTOau0Pkzj25C1yyEZbJfYmZ0cahBw
CyGIQIlxBYeYwHXzCgcq4WUtOJfDu4fhQXu73COe6j15mCZVVmvyLy8y9UJzCl4k
SAqiD0jCc5JWLvskI/8YdYQxPj0tuaN6bIn3mhP+Vq7pMjonMQ42ltqg9k8kOdix
VrYFlQL/oVh7m0IJG6Kib52AEdRt8Gs0L6k/YsSdR0fZQP2XhHtfJYdLDc05WEbN
bCpkONdx1qORAuckHtGdwAPX9Zc7O5YxvIqz6JWRJGwGgUCMwU5VGLmGbQsFjApG
PH90AI7+8pXDM1yTp7MugHGhu94+jzGXfYkgNmN4MIlO390gGTw68UVzuelOluqx
UneRt7++dGOnWLA4Z015FaAt09OlCUcQ0y7QtBZnG8QKhtCBvQ+XLYRwb4M/ciSY
GicZ00QR337oSd4MqPTRe1EFQ0r6f7836KOkhTKMBt/dQKWTC4WIK+14zP24x0O3
cZFPY8sqzL6/5bGH3wunmEktmQNTqBCKeuq/AfKGnbQ4wYNDx1AvHtM1HMLfgAms

Bug#807546: marked as done ([alfred] Fails to build on non-linux systems)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Dec 2015 01:48:51 +
with message-id 
and subject line Bug#807546: fixed in alfred 2015.2-1
has caused the Debian Bug report #807546,
regarding [alfred] Fails to build on non-linux systems
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.)


-- 
807546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alfred
Version: 2015.1
Severity: grave


Package fails to build on non-linux systems systems because libcap-dev is 
missing on them. On these systems the make calls have to use the parameter 
CONFIG_ALFRED_CAPABILITIES=n and the control file has to reduce the 
Build-Depends for libcap-dev no linux-any only
--- End Message ---
--- Begin Message ---
Source: alfred
Source-Version: 2015.2-1

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

Debian distribution maintenance software
pp.
Steffen Moeller  (supplier of updated alfred 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, 14 Dec 2015 01:46:20 +0100
Source: alfred
Binary: alfred
Architecture: source amd64
Version: 2015.2-1
Distribution: unstable
Urgency: low
Maintainer: Steffen Moeller 
Changed-By: Steffen Moeller 
Description:
 alfred - Almighty Lightweight Fact Remote Exchange Daemon
Closes: 807546 807547 807549 807550 807551 807552 807555 807562 807563
Changes:
 alfred (2015.2-1) unstable; urgency=low
 .
   * New upstream version (Closes: #807555)
 .
   [Contributions by Franz Schrober]
   * Added debian/watch file and signing key (Closes: #807550)
   * Reviewed debian/copyright,
 also added Franz to copyright holders of debian/* (Closes: #807547)
   * Corrected debian/README (Closes: #807549)
   * Corrected home page URL (Closes: #807552)
   * Added pkg-config to build-dependencies (Closes: #807551)
   * Added 64 bit I/O API to enable large file support (Closes: #807563)
   * Further hardened hardining (Closes: #807562)
   * Likely-fixed: Builds on non-linux systems (Closes: #807546)
Checksums-Sha1:
 22dd76e4b1d34e47b909de83a11138bafc77c0e1 1744 alfred_2015.2-1.dsc
 a027de85edad23d835f3da9ed7101587e31dcac4 54989 alfred_2015.2.orig.tar.gz
 89b9dbafd71013b3ad6e990427d545cef7411c99 4404 alfred_2015.2-1.debian.tar.xz
 d7c1114877822a033170628aa8fd3cf93736ec1d 39584 alfred_2015.2-1_amd64.deb
Checksums-Sha256:
 ed25646273f80bd86d1a0724ebf004372825c845623b043a5d0cf0ecc10ec425 1744 
alfred_2015.2-1.dsc
 7ae81e21de64891ce55cd9ab81e98fa8aac66a89237a149e8bad5dcffb1ad933 54989 
alfred_2015.2.orig.tar.gz
 627049145440b010f583b134090aec69fb15418c5892830f4401712a9774da37 4404 
alfred_2015.2-1.debian.tar.xz
 55942f3f8d1eb8658e275d7cbbb367cf8d650abc9cb418a49d81368520a12f56 39584 
alfred_2015.2-1_amd64.deb
Files:
 361fd70d180da81d9590c6402c669185 1744 net optional alfred_2015.2-1.dsc
 e50bd17753f824fa24d3914259ab0395 54989 net optional alfred_2015.2.orig.tar.gz
 a0d14907f804898545f2c57931f795e8 4404 net optional 
alfred_2015.2-1.debian.tar.xz
 ccfd9b933c9dab7dce9b23d552f75312 39584 net optional alfred_2015.2-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbhwuAAoJEC/YvtrAIO7RIu4P/0XDhLnHXXyvugkEdrdeMdfK
uNhqULMmZ6Thh7ydSzOtEUPIR/EgzBRaDyOTOau0Pkzj25C1yyEZbJfYmZ0cahBw
CyGIQIlxBYeYwHXzCgcq4WUtOJfDu4fhQXu73COe6j15mCZVVmvyLy8y9UJzCl4k
SAqiD0jCc5JWLvskI/8YdYQxPj0tuaN6bIn3mhP+Vq7pMjonMQ42ltqg9k8kOdix
VrYFlQL/oVh7m0IJG6Kib52AEdRt8Gs0L6k/YsSdR0fZQP2XhHtfJYdLDc05WEbN
bCpkONdx1qORAuckHtGdwAPX9Zc7O5YxvIqz6JWRJGwGgUCMwU5VGLmGbQsFjApG
PH90AI7+8pXDM1yTp7MugHGhu94+jzGXfYkgNmN4MIlO390gGTw68UVzuelOluqx
UneRt7++dGOnWLA4Z015FaAt09OlCUcQ0y7QtBZnG8QKhtCBvQ+XLYRwb4M/ciSY
GicZ00QR337oSd4MqPTRe1EFQ0r6f7836KOkhTKMBt/dQKWTC4WIK+14zP24x0O3
cZFPY8sqzL6/5bGH3wunmEktmQNTqBCKeuq/AfKGnbQ4wYNDx1AvHtM1HMLfgAms
ykn6W+ueKekiVjI9sDUyBlZarR2MbXFfaU7Thb44evI/UxZdHHh9l5OkaGme1zqt
/uRfaOWWII+5l5moFR08
=OKcK
-END PGP SIGNATURE End Message ---


Processed: tagging 807735, tagging 807660, tagging 807659, found 807666 in 3.1-6, tagging 807706, tagging 807657

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 807735 + sid stretch
Bug #807735 [src:gmpc-plugins] gmpc-plugins: FTBFS: libmpd-internal.h:210:10: 
error: expected identifier or '(' before '__extension__'
Ignoring request to alter tags of bug #807735 to the same tags previously set
> tags 807660 + sid stretch
Bug #807660 {Done: Emmanuel Bourg } [src:jenkins-winstone] 
jenkins-winstone: FTBFS: jenkins-winstone-2.8/target/test-classes does not exist
Added tag(s) stretch and sid.
> tags 807659 + sid stretch
Bug #807659 {Done: Emmanuel Bourg } 
[src:libgettext-commons-java] libgettext-commons-java: FTBFS:  Error resolving 
version for plugin 'org.apache.maven.plugins:maven-eclipse-plugin' 
Added tag(s) stretch and sid.
> found 807666 3.1-6
Bug #807666 [src:mpich] mpich: overly restrictive GCC check
Marked as found in versions mpich/3.1-6.
> tags 807706 + sid stretch
Bug #807706 {Done: Emmanuel Bourg } [src:uima-addons] 
uima-addons: FTBFS: Unresolveable build extension: Plugin 
org.apache.uima:PearPackagingMavenPlugin:2.3.1 
Added tag(s) stretch and sid.
> tags 807657 + sid stretch
Bug #807657 [src:dvdauthor] dvdauthor: FTBFS: compat.h:141:8: error: expected 
identifier or '(' before '__extension__'
Ignoring request to alter tags of bug #807657 to the same tags previously set
> thanks
Stopping processing here.

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



Bug#807730: marked as done (incorrect bsd/unistd.h header)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Dec 2015 04:41:20 +
with message-id 
and subject line Bug#807730: fixed in libbsd 0.8.1-1
has caused the Debian Bug report #807730,
regarding incorrect bsd/unistd.h header
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.)


-- 
807730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbsd-dev
Version: 0.8.0-2
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

After a recent update of libbsd, programs using it now fail at compile
time with:

/usr/include/bsd/unistd.h: In function 'setproctitle':
/usr/include/bsd/unistd.h:64:2: error: expected declaration specifiers before 
'__printflike'
  __printflike(1, 2);
  ^

It seems there is a missing backslash at the end of the previous line.

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

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

Versions of packages libbsd-dev depends on:
ii  libbsd0  0.8.0-2

libbsd-dev recommends no packages.

libbsd-dev suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIbBAEBCAAGBQJWa9LxAAoJEJWkL+g1NSX5gtAP9R8iiCZnqA7dxdtrv+54K/zm
RqwW/nneJA/OgZOKkHR64wlcoJlNHOCRTIQnAm/uVpG/vcHdFkmwBf5ksZl7jkjE
yOp5vqGo1Av3EKAfVr7LQwFNoH7ubCWXaFfHS5aR6Mgt7QIojGmxuMKXULzyhi9/
nThm3De3F/8fAuNSvgO0YvEm7HvzCXsWBUU2pn+0Ahw40cI5pdACnY6YgQsoM/wB
NDhkdPLfURtyQk0DIxspFImJ9MGSAvPZdy3wpsW7A4SvgjM1FHORQRWmebE2JczN
JB9UeYIbN/WNJEK4c++YChpFFuWRWpXJUU2x5a/anD+huAEgHzL3alGwaWm4eYOr
h1PVWZ5tGlIkTxtzYtOM212ex/VFawvdcnILjhO49X2/SfFYFVoGT4eOCtlJSTt2
15dMRj4FwZcf8sl23tUmVnt6b5Ye1ryWYjfgfeGQWfvW98NnPn3wqJXJMBsWul56
VFHLzuXMuscejznXXzg1l4MUvVK1UbdT5NRi0W64S4E55FjeRD68XYREfTkVIm8S
f20SY0ZUbKeojnAXMSysqxsSRBTQx0apTdjP4bhgbl+qYIGNLCuRrRZbcdViNxEQ
1/e450Pd4hvvAgdkvpBfV/K3309Ck0/hs5a+oOByEPPrL4MOYIsdYxlUJUqazbG2
/YHvQJQMzdKv7awlP6c=
=4rdN
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libbsd
Source-Version: 0.8.1-1

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated libbsd 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, 14 Dec 2015 04:10:23 +0100
Source: libbsd
Binary: libbsd-dev libbsd0 libbsd0-udeb libbsd0-dbg
Architecture: source
Version: 0.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: Guillem Jover 
Changed-By: Guillem Jover 
Description:
 libbsd-dev - utility functions from BSD systems - development files
 libbsd0- utility functions from BSD systems - shared library
 libbsd0-dbg - utility functions from BSD systems - debugging symbols
 libbsd0-udeb - utility functions from BSD systems - shared library (udeb)
Closes: 806840 807730
Changes:
 libbsd (0.8.1-1) unstable; urgency=medium
 .
   * New upstream release.
 - Add support for GNU/Hurd and GNU/kFreeBSD. (Closes: #806840)
 - Fix implicit dependencies for non-overlaid headers. (Closes: #807730)
   * Switch debian/copyright to machine readable format, reusing upstream
 COPYING file.
   * Use https for hadrons.org URLs.
Checksums-Sha1:
 ea7659d471511d7624a1c79859db876763feccd7 2010 libbsd_0.8.1-1.dsc
 ef77627a44506e5bf3fbd3a65deaf46364724af5 343624 libbsd_0.8.1.orig.tar.xz
 d40eea96302f3c3d3792e8bead4cd78cf7984fbb 16576 libbsd_0.8.1-1.debian.tar.xz
Checksums-Sha256:
 985fa5d23d8a7fec60b8c48a2d0d436239a6525355eb9d07b718d0b9df7f3689 2010 
libbsd_0.8.1-1.dsc
 adbc8781ad720bce939b689f38a9f0247732a36792147a7c28027c393c2af9b0 343624 
libbsd_0.8.1.orig.tar.xz
 166b9fb4eaca0c3e136503474e72bddef1e5f4727b5706f0575847f0d799eef2 16576 
libbsd_0.8.1-1.debian.tar.xz

Bug#807885: libstdc++6-6-dbg: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/debug/libstdc++.a

2015-12-13 Thread Andreas Beckmann
Package: libstdc++6-6-dbg
Version: 6-20151211-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libstdc++6-6-dbg:amd64.
  (Reading database ... ^M(Reading database ... 5%^M(Reading database ... 
10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database 
... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M^M(Reading 
database ... 40%^M(Reading database ... 45%^M(Reading database ... 
50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database 
... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading 
database ... 80%^M(Reading database ... 85%^M(Reading database ... 
90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database 
... 9570 files and directories currently installed.)
  Preparing to unpack .../libstdc++6-6-dbg_6-20151211-1_amd64.deb ...
  Unpacking libstdc++6-6-dbg:amd64 (6-20151211-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libstdc++6-6-dbg_6-20151211-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/debug/libstdc++.a', which is 
also in package libstdc++6-5-dbg:amd64 5.3.1-3
  Errors were encountered while processing:
   /var/cache/apt/archives/libstdc++6-6-dbg_6-20151211-1_amd64.deb
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

There are similar problems with lib32stdc++6-6-dbg,
libx32stdc++6-6-dbg and libgccjit-6-doc.


cheers,

Andreas


libstdc++6-5-dbg=5.3.1-3_libstdc++6-6-dbg=6-20151211-1.log.gz
Description: application/gzip


Bug#806840: marked as done (libbsd: FTBFS on non-Linux systems)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Dec 2015 04:41:20 +
with message-id 
and subject line Bug#806840: fixed in libbsd 0.8.1-1
has caused the Debian Bug report #806840,
regarding libbsd: FTBFS on non-Linux systems
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.)


-- 
806840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbsd
Source-Version: 0.8.0-2
Severity: serious

Hi!

The package does not build on non-Linux based systems. I've fixed the
code for GNU/kFreeBSD upstream. And just need to finish fixing it too
for GNU/Hurd, probably by using the random translator for getentropy.

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: libbsd
Source-Version: 0.8.1-1

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated libbsd 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, 14 Dec 2015 04:10:23 +0100
Source: libbsd
Binary: libbsd-dev libbsd0 libbsd0-udeb libbsd0-dbg
Architecture: source
Version: 0.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: Guillem Jover 
Changed-By: Guillem Jover 
Description:
 libbsd-dev - utility functions from BSD systems - development files
 libbsd0- utility functions from BSD systems - shared library
 libbsd0-dbg - utility functions from BSD systems - debugging symbols
 libbsd0-udeb - utility functions from BSD systems - shared library (udeb)
Closes: 806840 807730
Changes:
 libbsd (0.8.1-1) unstable; urgency=medium
 .
   * New upstream release.
 - Add support for GNU/Hurd and GNU/kFreeBSD. (Closes: #806840)
 - Fix implicit dependencies for non-overlaid headers. (Closes: #807730)
   * Switch debian/copyright to machine readable format, reusing upstream
 COPYING file.
   * Use https for hadrons.org URLs.
Checksums-Sha1:
 ea7659d471511d7624a1c79859db876763feccd7 2010 libbsd_0.8.1-1.dsc
 ef77627a44506e5bf3fbd3a65deaf46364724af5 343624 libbsd_0.8.1.orig.tar.xz
 d40eea96302f3c3d3792e8bead4cd78cf7984fbb 16576 libbsd_0.8.1-1.debian.tar.xz
Checksums-Sha256:
 985fa5d23d8a7fec60b8c48a2d0d436239a6525355eb9d07b718d0b9df7f3689 2010 
libbsd_0.8.1-1.dsc
 adbc8781ad720bce939b689f38a9f0247732a36792147a7c28027c393c2af9b0 343624 
libbsd_0.8.1.orig.tar.xz
 166b9fb4eaca0c3e136503474e72bddef1e5f4727b5706f0575847f0d799eef2 16576 
libbsd_0.8.1-1.debian.tar.xz
Files:
 2c571171f3a58d5ead5ec01d78afbc86 2010 libs optional libbsd_0.8.1-1.dsc
 f3daff0283af6e30f25d68be2deac4ef 343624 libs optional libbsd_0.8.1.orig.tar.xz
 0ac6971102ad789ece3589463e62904e 16576 libs optional 
libbsd_0.8.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWbjOdAAoJELlyvz6krlejpFIQAKq2IpFSihAau6opS5fCyutr
mFOYYxDshuONpwX7+NUYGA9rx1IaB95Alcn41YBMVdeb8pDXmB5FeOBn5rdaOng8
upB4LF4tGsmMq/vT3fMYZ1ccB9Ew+Ii885wbi6W7nz5O+hs+he6Hh7Dv7fMJHR5t
SU8GJJHa1KjlxJCboFQxchpuyxZCs0gnAG8YNVeCJHQPWWdmezCftALCvI5sW88t
ggE6x7hu1cYiQ9P1+HAjXsmbd58mH6lc4Okm8i4EOe66R4DcT/1ajHYv1nK1W+MK
3DS1RJxbSx0VNGlZwkhcA2Ia9W5CdBUCeCKArkYORKwGoqzIr49RTpv1obR+uDoL
AC0U4w0TrwOqja+rIODETMw/lpKcG7D0Bc51zhTyqfYXRVpmztYUwUlZdRvOMa1v
VDXC0eWQWYcgZSmf+wAJvUwvtZufLzL0LHESPtTJLWSsGBvG+QwnSgFa3u1RZcY2
FCL/HyCzVRYesFjQHZtG3Qcm7yZ8xW1eiUCUcWdTZevNb4H1+m47L4HcoFn8tt96
2b9HoKuSykecom69WbX8Orf3ZWJj1NWCHS9euFFcpLbWtQ3xqC840RFy2BTPn3BH
/68sxEYpvlx+NQKyvR8xxI7NruMLmf/yAR2REyTBAOz/Sv2gdfCXnH2LFmGVTLLV
ZRG5KVpEwku/+J80FXjg
=LMCc
-END PGP SIGNATURE End Message ---


Processed: severity of 803782 is normal, severity of 805817 is serious

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 803782 normal
Bug #803782 [ftp.debian.org] RM: drawtk - unmaintained, no rev deps, depends on 
gstreamer 0.10
Severity set to 'normal' from 'serious'
> severity 805817 serious
Bug #805817 [ftp.debian.org] RM: instanbul - dead upstream, depends on 
gstreamer 0.10
Ignoring request to change severity of Bug 805817 to the same value.
> thanks
Stopping processing here.

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



Bug#807784: [Pkg-octave-devel] Bug#807784: octave-optim suggests `lyx`

2015-12-13 Thread Hörmetjan Yiltiz
Great! Thanks! So lyx was supposed to be used for "reading" some
documentation? Well, I would not think that lyx can be assumed to be a tool
to do so. Octave users will use `help` and `info`, and when necessary, the
browser and PDF reader, but certainly not lyx. Thanks for the effort!

On Sun, Dec 13, 2015, 21:34 Rafael Laboissiere 
wrote:

> Control: severity -1 normal
>
> * Hormet Yiltiz  [2015-12-12 19:29]:
>
> > Package: octave-optim
> > Version: 1.4.1-1+b1
> > Severity: serious
> > Justification: Policy 7.2
> >
> >   octave-optim suggests lyx, which is a office suite that makes working
> >   with LaTeX easy, and implements a way for reproducable research.
> >   However, `lyx` then depends on `texlive`, which is a heavy
> >   dependency. Octave-optim is a package of GNU Octave, which is used
> >   for scientific computation. octave-optim, being a package for a
> >   octave that does the computation, should NOT depend or suggest a 3rd
> >   party software that is not very related to its usage.
>
> I disagree with this interpretation.  Section 7.2 of the Policy manual
> does mandate that:
>
> "Depends […] The Depends field should be used if the depended-on package
> is required for the depending package to provide a significant amount of
> functionality. […]"
>
> However, there is no such requirement for the Suggests relationship:
>
> "Suggests: This is used to declare that one package may be more useful
> with one or more others. Using this field tells the packaging system and
> the user that the listed packages are related to this one and can perhaps
> enhance its usefulness, but that installing this one without them is
> perfectly reasonable."
>
> I am therefore downgrading the severity of this bug report to "normal"
> hereby.
>
> That said, I agree with the bug submitter that having to install lyx,
> which pulls the whole TeX distribution, is an overkill for just reading
> part of the documentation.  I am now working on a solution that will ship
> the *.pdf instead of the *.lyx, as it is currently the case.  This will
> eventually fix the bug reported here.
>
> Rafael
>
-- 

Sent from Gmail Mobile.


Processed: Re: [Pkg-octave-devel] Bug#807784: octave-optim suggests `lyx`

2015-12-13 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #807784 [octave-optim] octave-optim suggests `lyx`
Severity set to 'normal' from 'serious'

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



Bug#807784: [Pkg-octave-devel] Bug#807784: octave-optim suggests `lyx`

2015-12-13 Thread Rafael Laboissiere

Control: severity -1 normal

* Hormet Yiltiz  [2015-12-12 19:29]:


Package: octave-optim
Version: 1.4.1-1+b1
Severity: serious
Justification: Policy 7.2

  octave-optim suggests lyx, which is a office suite that makes working
  with LaTeX easy, and implements a way for reproducable research.
  However, `lyx` then depends on `texlive`, which is a heavy
  dependency. Octave-optim is a package of GNU Octave, which is used
  for scientific computation. octave-optim, being a package for a
  octave that does the computation, should NOT depend or suggest a 3rd
  party software that is not very related to its usage.


I disagree with this interpretation.  Section 7.2 of the Policy manual 
does mandate that:


"Depends […] The Depends field should be used if the depended-on package 
is required for the depending package to provide a significant amount of 
functionality. […]"


However, there is no such requirement for the Suggests relationship:

"Suggests: This is used to declare that one package may be more useful 
with one or more others. Using this field tells the packaging system and 
the user that the listed packages are related to this one and can perhaps 
enhance its usefulness, but that installing this one without them is 
perfectly reasonable."


I am therefore downgrading the severity of this bug report to "normal" 
hereby.


That said, I agree with the bug submitter that having to install lyx, 
which pulls the whole TeX distribution, is an overkill for just reading 
part of the documentation.  I am now working on a solution that will ship 
the *.pdf instead of the *.lyx, as it is currently the case.  This will 
eventually fix the bug reported here.


Rafael



Processed: reassign 804993 to libjs-pie-doc, fixed 804993 in 1.0.0+dfsg-2, severity of 804993 is serious

2015-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 804993 libjs-pie-doc 1.0.0+dfsg-1
Bug #804993 {Done: Michael Fladischer } [libvirtd] 
python-django-classy-tags-doc and libjs-pie-doc: error when trying to install 
together
Warning: Unknown package 'libvirtd'
Bug reassigned from package 'libvirtd' to 'libjs-pie-doc'.
Ignoring request to alter found versions of bug #804993 to the same values 
previously set
Ignoring request to alter fixed versions of bug #804993 to the same values 
previously set
Bug #804993 {Done: Michael Fladischer } [libjs-pie-doc] 
python-django-classy-tags-doc and libjs-pie-doc: error when trying to install 
together
Marked as found in versions css3pie/1.0.0+dfsg-1.
> fixed 804993 1.0.0+dfsg-2
Bug #804993 {Done: Michael Fladischer } [libjs-pie-doc] 
python-django-classy-tags-doc and libjs-pie-doc: error when trying to install 
together
Marked as fixed in versions css3pie/1.0.0+dfsg-2.
> severity 804993 serious
Bug #804993 {Done: Michael Fladischer } [libjs-pie-doc] 
python-django-classy-tags-doc and libjs-pie-doc: error when trying to install 
together
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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



Bug#806167: python-twisted fails to upgrade because of missing/incorrect replaces/breaks

2015-12-13 Thread Andreas Beckmann
Followup-For: Bug #806167

Hi,

python-twisted-core should have Breaks matching the recently added
Replaces, otherwise it allows for partial up- and downgrades that
result in broken (but successfully installed according to dpkg)
packages (because files have disappeared).


Andreas



Bug#803295: marked as done (prepare for giflib5)

2015-12-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Dec 2015 07:35:58 +
with message-id 
and subject line Bug#803295: fixed in spamprobe 1.4d-14
has caused the Debian Bug report #803295,
regarding prepare for giflib5
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.)


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

Package: src:spamprobe
Version: 1.4d-13
Tags: sid stretch patch
Blocks: 803158
User: gif...@packages.debian.org
Usertags: giflib5

Planning an update of giflib to the current version 5.1.1. Giflib slightly 
changes it's API, requiring soureful changes. There are some options for getting 
giflib5.1 support:


- Look for a newer upstream version, if upstream supports
both giflib4 and giflib5.1. Upload the new package,
and close the bug report.

- Patch the code to both use the NEW API. This can be done using
#if GIFLIB_MAJOR >= 5

#else

#endif
Please upload the package, and close the report.

- Unconditionally patch the code, not supporting giflib4 anymore.
Please upload a package to experimental once giflib5 hits
experimental.

For the latter two options, please see a patch at
http://launchpadlibrarian.net/222933095/spamprobe_1.4d-13build2_1.4d-13ubuntu1.diff.gz

To test your changes before giflib5 is found in experimental, please use

deb https://people.debian.org/~doko/tmp/giflib5 ./

Thanks, Matthias
--- End Message ---
--- Begin Message ---
Source: spamprobe
Source-Version: 1.4d-14

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated spamprobe 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, 14 Dec 2015 08:25:00 +0100
Source: spamprobe
Binary: spamprobe
Architecture: source
Version: 1.4d-14
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 spamprobe  - Bayesian spam filter
Closes: 767404 781682 801353 803295
Changes:
 spamprobe (1.4d-14) unstable; urgency=medium
 .
   * QA upload.
   * Add support for giflib 5, thanks to Matthias Klose.  (Closes: 803295)
   * Updated translation of debconf template:
 + Portuguese, by Pedro Ribeiro.  (Closes: #767404)
 + Brazilian Portuguese, by Adriano Rafael Gomes.  (Closes: #801353)
 + Swedish, by Martin Bagge and Anders Jonsson.  (Closes: #781682)
   * Run debconf-updatepo during clean.
Checksums-Sha1:
 cc95ef4282956ee102aecadc18b85233d8668cd9 1765 spamprobe_1.4d-14.dsc
 7722a639752d8e481f600efafbe56242c09d326b 40988 spamprobe_1.4d-14.debian.tar.xz
Checksums-Sha256:
 08e76916f2df3aa555e4f329794dea5b3295e62e73a3e4d58e8f80729676b96a 1765 
spamprobe_1.4d-14.dsc
 839be3fbc1060aa637153befa5da7e810d1721b2b5e95768d0d24f842eddb1b4 40988 
spamprobe_1.4d-14.debian.tar.xz
Files:
 4697812b2b73a3539c87c9775bce30af 1765 mail optional spamprobe_1.4d-14.dsc
 575ec7658ed4af0c26ae384efa30d833 40988 mail optional 
spamprobe_1.4d-14.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWbm9GAAoJEF+zP5NZ6e0IpUIP/jR10UEWacHiwVDlQA9yew4O
bQDrVlMC/T5QFpV4ZO5x5dJOf0joIwvQXMGqxaH8TbLhDZ284KWzHnlBInb1tt5E
7NgXO1OEX+ZMCWcBbM1rxu3gOIaTnDZ4kunOVw+qOoXvRT6E7A5/dmBW17fzvIMR
q1FGugFE4i3E4xfIEV5kmgH8XGsdW70kMCHAkwryPmbzUMC8qxju7H7JN42viMhW
e1oA4vZxcE5h2huGkxlg2gOYGEHxYjojELvYc3IIWMEUCwIRFif/e5QGTiXWzIYS
APgxPrVgLvUfpDTVfsGusWPagz0OaxbSDCBFrIeuLt1Nvr2bPiVeAl+L0TP9AMMj
SCa7Odtnx2/pI+rFlWQDHMsg+MPiCPFUHI/NAW19rcPuHz1/fb8LU89+ymdNpX1p
dF+KmzN2VqetI1VCvkQMMOpHTCp8YRk0LBYczR4mFLnDAP0gOC/3820G6Azxchnq
X9eUf5WmTdCX4zW2sFPV5pNMWY/qfW6XvVElrvsrE2W4Fc6nykCeTeJDU3m9SMBm
/RIxNmfy9rVDc/5j2qJWR8Hc+3CZ4xcdLcDY4Jw3SAMVett7qSy/8eNym2K1aR+r
JrXbBtyfYa+1qKWOezmm4o+MIuqGiiRQ3WX54TymRr9x3YN7npn/iw20rexI0w4m
3OF+0HJeaF1yoxRsdOWi
=Z5Pf
-END PGP SIGNATURE End Message ---


Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

2015-12-13 Thread Stefan Ahlers
Hi,

I'm a little bit confused about the sh4 build of libechonest. It failed
because there appears a new symbol:

 (c++)"QDebug::operator<<(QByteArray const&)@Base" 2.3.1-0.3

on all  architectures there is the following Symbol:

 (c++)"QDebug::operator<<(QString const&)@Base" 2.3.1

Why does sh4 uses QString and QByteArray for this method and why only in
the Qt5 build?

What should we do now? A new build only to fix the sh4 symbols or shell
we fix it for the next release?

Stefan



Bug#784070: Stable is still affected

2015-12-13 Thread Alexander E. Patrakov

Are there any plans to produce a stable update containing this fix?