Bug#717613: marked as done (systemd-udevd failes to execute /lib/udev/socket:@/org/freedesktop/hal/udev_event)

Your message dated Tue, 20 May 2014 06:52:10 + with message-id and subject line Bug#747662: Removed package(s) from unstable has caused the Debian Bug report #705489, regarding systemd-udevd failes to execute /lib/udev/socket:@/org/freedesktop/hal/udev_event to be marked as done. This means

Bug#747583: marked as done (Package is obsolete)

Your message dated Tue, 20 May 2014 06:49:18 + with message-id and subject line Bug#747175: Removed package(s) from unstable has caused the Debian Bug report #747583, regarding Package is obsolete to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#705489: marked as done (Uses deprecated RUN+="socket:")

Your message dated Tue, 20 May 2014 06:52:10 + with message-id and subject line Bug#747662: Removed package(s) from unstable has caused the Debian Bug report #705489, regarding Uses deprecated RUN+="socket:" to be marked as done. This means that you claim that the problem has been dealt with.

Bug#746131: marked as done (haskell-representable-tries: FTBFS: Ambiguous module name `Control.Monad.Representable.Reader')

Your message dated Tue, 20 May 2014 06:48:33 + with message-id and subject line Bug#747176: Removed package(s) from unstable has caused the Debian Bug report #746131, regarding haskell-representable-tries: FTBFS: Ambiguous module name `Control.Monad.Representable.Reader' to be marked as done.

Bug#694143: marked as done (FTBFS against libav 9)

Your message dated Tue, 20 May 2014 06:48:21 + with message-id and subject line Bug#747952: Removed package(s) from unstable has caused the Debian Bug report #694143, regarding FTBFS against libav 9 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#745076: marked as done (enna cannot be installe due to unsatisfiable dependencies)

Your message dated Tue, 20 May 2014 06:40:58 + with message-id and subject line Bug#748050: Removed package(s) from unstable has caused the Debian Bug report #745076, regarding enna cannot be installe due to unsatisfiable dependencies to be marked as done. This means that you claim that the p

Processed: Re: belle-sip: FTBFS on kfreebsd-i386 (internal error: belle_sdp.g : java.lang.NullPointerException)

Processing commands for cont...@bugs.debian.org: > notfound 747418 belle-sip/1.3.0-1.1 Bug #747418 {Done: Aníbal Monsalve Salazar } [src:belle-sip] belle-sip: FTBFS on kfreebsd-i386 (internal error: belle_sdp.g : java.lang.NullPointerException) No longer marked as found in versions belle-sip/1.3

Bug#748728: id-utils and libuser: error when trying to install together

Package: libuser,id-utils Version: libuser/1:0.60~dfsg-1 Version: id-utils/4.6+git20120811-4 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-05-20 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the s

Bug#748603: Not serious

severity 748603 normal thanks Hi Franz! Thanks a lot for your feedback, but no, this is not a bug at all, it's just normal sid breakage when packages *got* uploaded but some of them need to pass trough the NEW queue [0] due to a binary changing it's name. [0]

Processed: Not serious

Processing commands for cont...@bugs.debian.org: > severity 748603 normal Bug #748603 [kde-telepathy] [kde-telepathy] Version from sid not installable Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 748603: http://bugs.debia

Processed: tagging 748472

Processing commands for cont...@bugs.debian.org: > tags 748472 - pending Bug #748472 [python3-wsme] python3-wsme: Uninstallable due to dropping of python3-ipaddr Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 748472: http://bugs.debian.or

Bug#748472: [PKG-Openstack-devel] Bug#748472: python3-wsme: Uninstallable due to dropping of python3-ipaddr

On Monday, May 19, 2014 18:26:02 Thomas Goirand wrote: > On 05/17/2014 11:20 PM, Scott Kitterman wrote: > > On Saturday, May 17, 2014 10:20:32 you wrote: > > ... > > > >> That makes this a trivial package change. I'll upload and NMU to delay 7 > >> shortly to clean this up. Feel free to cancel i

Bug#747135: chromium: FTBFS on i386 due to 32bit linker

Hi! I just tested this by adding gcc (>= 4:4.9.0-2exp2), g++ (>= 4:4.9.0-2exp2), to the build-deps and rebuilding inside cowbuilder. With gcc-4.9 chromium is finally able to be linked: LINK(target) out/Release/chrome: Finished touch out/Release/obj.target/chrome/chrome.stamp make[1]: Leav

Bug#748673: chromium-browser: FTBFS, missing protobuf-compiler Build-Depends

James McCoy write: > The latest experimental upload didn't include protobuf-compiler in > Build-Depends, so the buildd build failed[0]. > [0]: https://buildd.debian.org/status/fetch.php?pkg=chromium-browser&arch=i386&ver=35.0.1916.99-1&stamp=1400365223 Also missing: gperf bison ninja-build And

Bug#747761: xulrunner-dev: ships mozilla-js.pc which is also in libmozjs-dev

On Tue, May 20, 2014 at 01:23:12AM +0300, Martin-Éric Racine wrote: > 2014-05-12 19:07 GMT+03:00 Rene Engelhard : > > Hi, > > > > On Mon, May 12, 2014 at 04:41:35PM +0200, Rene Engelhard wrote: > >> On Mon, May 12, 2014 at 02:01:28PM +0300, Martin-Éric Racine wrote: > >> > xulrunner-dev probably ne

Processed: usertag piuparts

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was hol...@layer-acht.org). > usertag 708496 + piuparts Usertags were: piuparts. Usertags are now: piuparts. > found 708496 jessie/None Bug #708496 [src:nana] nana: Please

Bug#747761: xulrunner-dev: ships mozilla-js.pc which is also in libmozjs-dev

2014-05-12 19:07 GMT+03:00 Rene Engelhard : > Hi, > > On Mon, May 12, 2014 at 04:41:35PM +0200, Rene Engelhard wrote: >> On Mon, May 12, 2014 at 02:01:28PM +0300, Martin-Éric Racine wrote: >> > xulrunner-dev probably needs to Conflicts/Provides/Replaces libmozjs-dev > > Yep. > > What I needed for u

Bug#748662: marked as done (missing license in debian/copyright)

Your message dated Mon, 19 May 2014 22:06:08 + with message-id and subject line Bug#748662: fixed in gloox 1.0.10-2 has caused the Debian Bug report #748662, regarding missing license in debian/copyright to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: bug#712980: tags

Processing commands for cont...@bugs.debian.org: > tags 712980 - upstream Bug #712980 {Done: Jordi Mallach } [alsa-utils] alsa-utils startup script creates /.pulse files ("Failed to create secure directory") when pulseaudio is installed Bug #675857 {Done: Felipe Sateler } [alsa-utils] PulseAudi

Bug#739426: marked as done (kino: FTBFS with libav10)

Your message dated Mon, 19 May 2014 21:35:09 + with message-id and subject line Bug#739426: fixed in kino 1.3.4-2.1 has caused the Debian Bug report #739426, regarding kino: FTBFS with libav10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#748614: [pkg-kolab] Bug#748614: [libkolabxml0] looses information about birthdays

Hello, I duplicated the issue with libkolabxml 0.8.4 and libkolab 0.4.2. It looks like birthday isn't being serialized to the kolab mails. I suspect the birthday still shows up on the local machine because its cached in akonadi. Upstream has new versions of libkolabxml & libkolab that we need

Bug#748655: marked as done (FTBFS: litl (ab)uses unstable Doxygen interface LATEX_HEADER)

Your message dated Mon, 19 May 2014 21:35:45 + with message-id and subject line Bug#748655: fixed in litl 0.1.3+dfsg-1 has caused the Debian Bug report #748655, regarding FTBFS: litl (ab)uses unstable Doxygen interface LATEX_HEADER to be marked as done. This means that you claim that the prob

Processed: Re: [Pkg-libvirt-maintainers] Bug#748703: libvirt-bin: libvirtd version 1.2.4-3 cannot probe backing volume format

Processing commands for cont...@bugs.debian.org: > severity 748703 important Bug #748703 [libvirt-bin] libvirt-bin: libvirtd version 1.2.4-3 cannot probe backing volume format Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#748703: [Pkg-libvirt-maintainers] Bug#748703: libvirt-bin: libvirtd version 1.2.4-3 cannot probe backing volume format

severity 748703 important thanks On Mon, May 19, 2014 at 04:29:07PM -0400, Bob Weber wrote: > Package: libvirt-bin > Version: 1.2.4-3 > Severity: grave > Justification: renders package unusable > > > After upgrading to 1.2.4-3 libvirtd reports: > > kern.log.1:May 17 19:20:06 bob libvirtd[11315]

Processed: Bug#675857: merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 742388 alsa-utils Bug #742388 {Done: Felipe Sateler } [libpulse0] libpulse0: spurious files .pulse and .pulse-cookie in /root directory Bug reassigned from package 'libpulse0' to 'alsa-utils'. No longer marked as found in versions pulsea

Bug#748655: doxygen generate invalid \+ latex command

Control: tags -1 + pending Helmut Grohne, le Mon 19 May 2014 18:03:18 +0200, a écrit : > This is because litl uses an unstable interface of Doxygen. It defines > its own LATEX_HEADER Ah. I should have checked that kind of thing indeed, sorry. Thanks for the explanation, I'll see with upstream.

Processed: Re: Bug#748655: doxygen generate invalid \+ latex command

Processing control commands: > tags -1 + pending Bug #748655 [src:litl] FTBFS: litl (ab)uses unstable Doxygen interface LATEX_HEADER Added tag(s) pending. -- 748655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#748694: sys/sdt.h is architecture specific, and causing issues on unsupported architectures

Am 19.05.2014 21:00, schrieb Mark Wielaard: > On Mon, 2014-05-19 at 20:17 +0200, Matthias Klose wrote: >> The sys/sdt.h header file is shipped in an architecture independent package, >> and >> installed into /usr/include where it is found on the include path for every >> architecture. [...] what a

Bug#748703: libvirt-bin: libvirtd version 1.2.4-3 cannot probe backing volume format

Package: libvirt-bin Version: 1.2.4-3 Severity: grave Justification: renders package unusable After upgrading to 1.2.4-3 libvirtd reports: kern.log.1:May 17 19:20:06 bob libvirtd[11315]: internal error: cannot probe backing volume format: Debian-7.4-base.img This happens for every VM that I ha

Bug#748702: kernel-package: make-kpkg creates packages with missing architecture on i386

Package: kernel-package Version: 13.011 Severity: serious On i386, "make-kpkg linux-image" creates packages without an "Architecture:" field which dpkg will then fail to process (unless --force-architecture is specified). This is due to a broken logic in /usr/share/kernel-package/ruleset/targets/

Processed: limit source to opensmtpd, tagging 741238, tagging 748513

Processing commands for cont...@bugs.debian.org: > #opensmtpd (5.4.2p1-1) unstable; urgency=medium > # > # * This build against the new openssl package permits opensmtpd to start > #again (Closes: #748513); the underlying problem has been reported > upstream > # * Install CONFIG-UPDATE.txt.

Bug#748694: sys/sdt.h is architecture specific, and causing issues on unsupported architectures

On Mon, 2014-05-19 at 20:17 +0200, Matthias Klose wrote: > The sys/sdt.h header file is shipped in an architecture independent package, > and > installed into /usr/include where it is found on the include path for every > architecture. [...] what about issues on architectures not supported by > s

Bug#748694: sys/sdt.h is architecture specific, and causing issues on unsupported architectures

Hi, [ Adding reporter of #726248 to CC and quoting the bug report fully for him. ] Matthias Klose writes: > The sys/sdt.h header file is shipped in an architecture independent package, > and > installed into /usr/include where it is found on the include path for every > architecture. Seen th

Processed: bug 748657 is forwarded to https://savannah.gnu.org/bugs/index.php?42390

Processing commands for cont...@bugs.debian.org: > forwarded 748657 https://savannah.gnu.org/bugs/index.php?42390 Bug #748657 [make-dfsg] make-dfsg failed to run test: work/misc/fopen-fail.mk Set Bug forwarded-to-address to 'https://savannah.gnu.org/bugs/index.php?42390'. > thanks Stopping process

Bug#748657: marked as forwarded (make-dfsg failed to run test: work/misc/fopen-fail.mk)

Your message dated Mon, 19 May 2014 18:32:25 + with message-id <20140519-143224.sv260.56...@savannah.gnu.org> has caused the report #748657, regarding make-dfsg failed to run test: work/misc/fopen-fail.mk to be marked as having been forwarded to the upstream software author(s) (NB:

Bug#747105: policykit-1: depends on systemd

2014-05-06 from Laurent Bigonville: > ConsoleKit is dead for years I wouldn't rather call it "dead for years" -- v0.4.5 relesed 2011-05-02, v0.4.6 released 2013-08-19: http://www.freedesktop.org/wiki/Software/ConsoleKit/ > it's time IMVHO to start moving away from ConsoleKit > on linux architectu

Bug#748657: marked as forwarded (make-dfsg failed to run test: work/misc/fopen-fail.mk)

Your message dated Mon, 19 May 2014 18:23:39 + with message-id <20140519-132338.sv10516.10...@savannah.gnu.org> has caused the report #748657, regarding make-dfsg failed to run test: work/misc/fopen-fail.mk to be marked as having been forwarded to the upstream software author(s) (

Bug#748694: sys/sdt.h is architecture specific, and causing issues on unsupported architectures

Package: systemtap Version: 2.3-2 Severity: serious Tags: sid jessie The sys/sdt.h header file is shipped in an architecture independent package, and installed into /usr/include where it is found on the include path for every architecture. Seen that the mere inclusion of this header causes build

Processed: Re: Bug#747428: [xbmc] passwords are stored in plain xml file

Processing control commands: > found -1 2:11.0~git20120510.82388d5-1 Bug #747428 [xbmc] [xbmc] passwords are stored in plain xml file Marked as found in versions xbmc/2:11.0~git20120510.82388d5-1. > tags -1 confirmed Bug #747428 [xbmc] [xbmc] passwords are stored in plain xml file Added tag(s) con

Bug#747428: [xbmc] passwords are stored in plain xml file

Control: found -1 2:11.0~git20120510.82388d5-1 Control: tags -1 confirmed 2014-05-08 16:41 GMT+02:00 Adrien Grellier : > Package: xbmc > Version: 2:13.0+dfsg1-1 > Severity: grave > Tags: security > X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org > > Hi, > > I just add a webdav source in

Bug#748657: make-dfsg failed to run test: work/misc/fopen-fail.mk

Hi, Thanks for the report. So, the question now is why is fopen failing here? I have an amd64 development box, make has built just last week both outside and inside clean environments, and the tests passed. The build daemons reported no issues as well. Something has changed.

Bug#747698: marked as done (vtk: FTBFS on kfreebsd (The method run() of type new Runnable(){} must override a superclass method))

Your message dated Mon, 19 May 2014 16:37:33 + with message-id and subject line Bug#747698: fixed in vtk 5.8.0-17.2 has caused the Debian Bug report #747698, regarding vtk: FTBFS on kfreebsd (The method run() of type new Runnable(){} must override a superclass method) to be marked as done. T

Bug#705690: marked as done (libuser: CVE-2012-5630 CVE-2012-5644)

Your message dated Mon, 19 May 2014 16:19:07 + with message-id and subject line Bug#705690: fixed in libuser 1:0.60~dfsg-1 has caused the Debian Bug report #705690, regarding libuser: CVE-2012-5630 CVE-2012-5644 to be marked as done. This means that you claim that the problem has been dealt w

Bug#748685: bibletime: FTBFS when rebuilt against libsword10

Source: bibletime Version: 2.9.2-1 Severity: serious Hi, Your package FTBFS when rebuilt against libsword10. The relevant part of the build log appears to be: """ /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CMakeFiles 1 Building CXX ob

Processed: Re: Bug#748655: doxygen generate invalid \+ latex command

Processing control commands: > reassign -1 src:litl Bug #748655 [doxygen] doxygen generate invalid \+ latex command Bug reassigned from package 'doxygen' to 'src:litl'. No longer marked as found in versions doxygen/1.8.7-1. Ignoring request to alter fixed versions of bug #748655 to the same values

Bug#748655: doxygen generate invalid \+ latex command

Control: reassign -1 src:litl Control: retitle -1 FTBFS: litl (ab)uses unstable Doxygen interface LATEX_HEADER On Mon, May 19, 2014 at 12:06:47PM +0200, Samuel Thibault wrote: > The newer version of doxygen emits an invalid latex command: in > modules.tex one can read: > > Here is a list of all m

Processed: Re: Bug#746034: chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no longer in the testing archive

Processing control commands: > notfound -1 33.0.1750.152-1 Bug #746034 [chromium] chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no longer in the testing archive No longer marked as found in versions chromium-browser/33.0.1750.152-1. -- 746034: http://bugs.debian.org/cgi-bin/bugre

Bug#746034: chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no longer in the testing archive

Control: notfound -1 33.0.1750.152-1 On 2014-05-19 03:31 +0200, shirish शिरीष wrote: > Control: reopen 746034 Please don't do that, unless you know what it means. The bug _has_ been fixed in newer versions, although those are only available on amd64. > Even on amd64 there is NO 34.0.1847.116-2

Bug#748574: 3.14.1 does not boot on Dell server

On 05/19/2014 10:52 AM, John Bleichert wrote: Ben, I patched, built and installed the kernel and it still crashes. I am attaching the call trace to this message again. If I can get you any more info please let me know. Please note that, having noticed I was a bit out of date, I flashed my B

Bug#746587: Acknowledgement (Use systemd built-in mechanisms for mounting remote file systems like NFS during early boot)

Any comments from the sysvinit maintainers? I'm willing to work on a different solution (with your help) if you don't consider the proposed patch as sufficient. Since this is a rather serious bug, I will upload an NMU soonish otherwise. Regards, Michael -- Why is it that all of the instruments

Bug#748673: chromium-browser: FTBFS, missing protobuf-compiler Build-Depends

Source: chromium-browser Version: 35.0.1916.99-1 Severity: serious Justification: Policy 7.7 The latest experimental upload didn't include protobuf-compiler in Build-Depends, so the buildd build failed[0]. [0]: https://buildd.debian.org/status/fetch.php?pkg=chromium-browser&arch=i386&ver=35.0.19

Bug#748667: python-vtk6: bogus RPATH

Thanks for pointing that out. Are there any recommendations how to fix it properly? Anton 2014-05-19 14:57 GMT+02:00 Sebastian Ramacher : > Control: found -1 6.0.0-7 > > On 2014-05-19 14:31:12, Jakub Wilk wrote: >> Source: python-vtk6 >> Version: 6.1.0+dfsg-2 >> Severity: grave >> Tags: security

Bug#748671: libnss-sss: Multiarch package removes configuration without reference counting

Package: libnss-sss Version: 1.11.5.1-1 Severity: serious Hi, libnss-sss has the following code in postrm: sed -i --regexp-extended ' /^(passwd|group|shadow|netgroup):/ { s/\bsss\b//g s/[[:space:]]+$// } ' /etc/nsswitch.conf This code is executed on removal o

Bug#748667: python-vtk6: bogus RPATH

Control: found -1 6.0.0-7 On 2014-05-19 14:31:12, Jakub Wilk wrote: > Source: python-vtk6 > Version: 6.1.0+dfsg-2 > Severity: grave > Tags: security > > /usr/bin/pvtk, /usr/bin/vtk6python and /usr/bin/pvtkpython all have RPATH > set to: > > /usr/lib/jvm/default-java/jre/lib/amd64/xawt:/usr/lib/j

Bug#748326: systemd-sysv

I installed systemd-sysv and my problem was fixed. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#748667: python-vtk6: bogus RPATH

Processing control commands: > found -1 6.0.0-7 Bug #748667 [python-vtk6] python-vtk6: bogus RPATH Marked as found in versions vtk6/6.0.0-7. -- 748667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRI

Processed: reassign 748667 to python-vtk6, found 748667 in 6.1.0+dfsg-2

Processing commands for cont...@bugs.debian.org: > # Stupid reportbug! (see bug #690169) > reassign 748667 python-vtk6 Bug #748667 [src:python-vtk6] python-vtk6: bogus RPATH Warning: Unknown package 'src:python-vtk6' Bug reassigned from package 'src:python-vtk6' to 'python-vtk6'. No longer marked

Bug#748667: python-vtk6: bogus RPATH

Source: python-vtk6 Version: 6.1.0+dfsg-2 Severity: grave Tags: security /usr/bin/pvtk, /usr/bin/vtk6python and /usr/bin/pvtkpython all have RPATH set to: /usr/lib/jvm/default-java/jre/lib/amd64/xawt:/usr/lib/jvm/default-java/jre/lib/amd64/server:/tmp/buildd/vtk6-6.1.0+dfsg/debian/build/lib:

Bug#748666: base: Screen garbled on booting in the linux kernel

Package: base Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? After installation, on Dell Inspiron 1501, after grub booting on the linux kernel the screen goes garbled

Bug#748603: [kde-telepathy] Version from sid not installable

Control: reassign -1 kde-telepathy 0.8.1 On Du, 18 mai 14, 19:29:27, Franz Schrober wrote: > Source: kde-telepathy > Version: 0.8.1 > Severity: serious > > The current version of kde-telepathy in sid is not installable because the > ktp-common-internals was not uploaded and all packages depend o

Processed: Re: Bug#748603: [kde-telepathy] Version from sid not installable

Processing control commands: > reassign -1 kde-telepathy 0.8.1 Bug #748603 [src:kde-telepathy] [kde-telepathy] Version from sid not installable Warning: Unknown package 'src:kde-telepathy' Bug reassigned from package 'src:kde-telepathy' to 'kde-telepathy'. No longer marked as found in versions kde

Bug#710635: marked as done (pynac: FTBFS: ld: cannot find -lz)

Your message dated Mon, 19 May 2014 12:00:07 + with message-id and subject line Bug#710635: fixed in pynac 0.3.2+dfsg-1 has caused the Debian Bug report #710635, regarding pynac: FTBFS: ld: cannot find -lz to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#747418: marked as done (belle-sip: FTBFS on kfreebsd-i386 (internal error: belle_sdp.g : java.lang.NullPointerException))

Your message dated Mon, 19 May 2014 21:42:39 +1000 with message-id <20140519114239.ga12...@master.debian.org> and subject line Re: belle-sip: FTBFS on kfreebsd-i386 (internal error: belle_sdp.g : java.lang.NullPointerException) has caused the Debian Bug report #747418, regarding belle-sip: FTBFS o

Bug#747418: belle-sip: FTBFS on kfreebsd-i386 (internal error: belle_sdp.g : java.lang.NullPointerException)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 16 May 2014 11:28:47 +0100 Source: belle-sip Binary: libbellesip0 libbellesip-dev libbellesip-dbg Architecture: source mipsel Version: 1.3.0-1.1 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team Changed-By: A

Bug#748662: missing license in debian/copyright

Package: gloox Version: 1.0.10-1 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing licenses of: src/md5.* to debian/copyright. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-rc-re

Bug#748472: [PKG-Openstack-devel] Bug#748472: python3-wsme: Uninstallable due to dropping of python3-ipaddr

On May 19, 2014 6:26:02 AM EDT, Thomas Goirand wrote: >On 05/17/2014 11:20 PM, Scott Kitterman wrote: >> On Saturday, May 17, 2014 10:20:32 you wrote: >> ... >>> That makes this a trivial package change. I'll upload and NMU to >delay 7 >>> shortly to clean this up. Feel free to cancel it, speed

Bug#748657: make-dfsg failed to run test: work/misc/fopen-fail.mk

Package: make-dfsg Version: 4.0-7 Severity: serious I test in on both amd64 and mips64el. I tried to run this step manually, it does hang. functions/warning ... ok (4 passed) functions/wildcard .. ok (6 passed) functi

Bug#739460: openscenegraph: diff for NMU version 3.2.0~rc1-5.1

Reinhard Tartler writes: > On 18.05.2014 09:00, Manuel A. Fernandez Montecelo wrote: >> 2014-05-18 12:10 GMT+01:00 Reinhard Tartler : So, can you please remove that change in the NMU, if you want to keep the NMU at all? >>> >>> Sure, I've just canceled the NMU. >> >> Thanks. >> >>

Bug#748472: [PKG-Openstack-devel] Bug#748472: python3-wsme: Uninstallable due to dropping of python3-ipaddr

On 05/17/2014 11:20 PM, Scott Kitterman wrote: > On Saturday, May 17, 2014 10:20:32 you wrote: > ... >> That makes this a trivial package change. I'll upload and NMU to delay 7 >> shortly to clean this up. Feel free to cancel it, speed it up, etc. I'll >> send the NMU diff to this bug as well.

Bug#748323: marked as done (blender: FTBFS on non-x86)

Your message dated Mon, 19 May 2014 10:19:53 + with message-id and subject line Bug#748323: fixed in blender 2.70a-1 has caused the Debian Bug report #748323, regarding blender: FTBFS on non-x86 to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#748322: marked as done (blender: FTBFS on non-Linux)

Your message dated Mon, 19 May 2014 10:19:53 + with message-id and subject line Bug#748322: fixed in blender 2.70a-1 has caused the Debian Bug report #748322, regarding blender: FTBFS on non-Linux to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#705690: up-to-date packaging for libuser

On Mon, Apr 28, 2014 at 09:46:22AM +0200, Tzafrir Cohen wrote: > Hi, > > It seems that libuser has not recieved any decent maintinance in recent > years. As its removal will remove my package (mock), I tried fixing this > bug. > > It turned out to be more complicated than I thought, and I ended u

Bug#748655: doxygen generate invalid \+ latex command

Package: doxygen Version: 1.8.7-1 Severity: serious Justification: Makes litl FTBFS Hello, The newer version of doxygen emits an invalid latex command: in modules.tex one can read: Here is a list of all modules\+:\begin{DoxyCompactList} resulting to the following failure: ! Undefined control s

Bug#741666: marked as done (scribus: Scribus included non-free contents)

Your message dated Mon, 19 May 2014 09:23:31 + with message-id and subject line Bug#741666: fixed in scribus 1.4.2.dfsg.1+r18267-0.1 has caused the Debian Bug report #741666, regarding scribus: Scribus included non-free contents to be marked as done. This means that you claim that the problem

Bug#748155: marked as done (plastimatch: error while loading shared libraries: libitkgdcmDICT-4.5.so.1: cannot open shared object file: No such file or directory)

Your message dated Mon, 19 May 2014 09:22:25 + with message-id and subject line Bug#748155: fixed in plastimatch 1.5.16+dfsg-1 has caused the Debian Bug report #748155, regarding plastimatch: error while loading shared libraries: libitkgdcmDICT-4.5.so.1: cannot open shared object file: No suc

Bug#747298: marked as done (request-tracker4: Missing dependency on libcss-squish-perl)

Your message dated Mon, 19 May 2014 09:23:03 + with message-id and subject line Bug#747298: fixed in request-tracker4 4.2.4-1 has caused the Debian Bug report #747298, regarding request-tracker4: Missing dependency on libcss-squish-perl to be marked as done. This means that you claim that the

Bug#748650: vmdebootstrap: uninstallable with current extlinux in unstable

Package: vmdebootstrap Version: 0.2-2 Severity: grave vmdebootstrap Depends: extlinux (<< 3:6.00~), but unstable now has 3:6.03~pre1+dfsg-4, as of Saturday. vmdebootstrap is therefore now uninstallable in unstable, and will prevent the migration of the new version of syslinux to testing. Thanks,

Bug#748641: installation-reports: Garbled screen on Dell Inspiron 1501

Control: severity -1 normal Maurizio (2014-05-19): > Package: installation-reports > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > *** Please consider answering these questions, where appropriate *** > >* What led up to the situation? > Just installing fro

Processed: Re: Bug#748641: installation-reports: Garbled screen on Dell Inspiron 1501

Processing control commands: > severity -1 normal Bug #748641 [installation-reports] installation-reports: Garbled screen on Dell Inspiron 1501 Severity set to 'normal' from 'grave' -- 748641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748641 Debian Bug Tracking System Contact ow...@bugs.

Bug#748495: closed by Daniel Baumann (reply to daniel.baum...@progress-technologies.net) (Re: Missing required dependencies)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Even then you should make sure you are recommending the correct version (python3 >= 3.3) which currently is not the case. Furthermore when running basic commands (and starting a container really IS basic) doesn't work then it makes this package unu