Bug#730592: marked as done (r-bioc-biostrings: FTBFS: error: unknown type name 'cachedCharSeq')

Your message dated Wed, 27 Nov 2013 09:20:35 + with message-id e1vlbir-ln...@franck.debian.org and subject line Bug#730592: fixed in r-bioc-biostrings 2.30.1-1 has caused the Debian Bug report #730592, regarding r-bioc-biostrings: FTBFS: error: unknown type name 'cachedCharSeq' to be

Bug#713167: marked as done (ruby-hiera-puppet: FTBFS: tests failed)

Your message dated Wed, 27 Nov 2013 09:23:24 + with message-id e1vlbla-0001ki...@franck.debian.org and subject line Bug#730322: Removed package(s) from unstable has caused the Debian Bug report #713167, regarding ruby-hiera-puppet: FTBFS: tests failed to be marked as done. This means that you

Bug#722479: marked as done (Doesn't contain license full text in source package)

Your message dated Wed, 27 Nov 2013 09:34:06 + with message-id e1vlbvw-0005s2...@franck.debian.org and subject line Bug#729673: Removed package(s) from unstable has caused the Debian Bug report #722479, regarding Doesn't contain license full text in source package to be marked as done. This

Bug#703053: marked as done (lastmp: switch from python-libmpdclient to python-mpd)

Your message dated Wed, 27 Nov 2013 09:36:18 + with message-id e1vlbxe-0006dn...@franck.debian.org and subject line Bug#730168: Removed package(s) from unstable has caused the Debian Bug report #703053, regarding lastmp: switch from python-libmpdclient to python-mpd to be marked as done. This

Bug#713366: marked as done (openmpi1.6: FTBFS: install: cannot change owner and permissions of 'debian/openmpi1.6-bin/DEBIAN': Operation not permitted)

Your message dated Wed, 27 Nov 2013 09:51:56 + with message-id e1vlbmm-0003qu...@franck.debian.org and subject line Bug#730473: Removed package(s) from unstable has caused the Debian Bug report #713366, regarding openmpi1.6: FTBFS: install: cannot change owner and permissions of

Bug#712479: marked as done (RM: py-sendfile -- RoQA; namespace conflict with pysendfile)

Your message dated Wed, 27 Nov 2013 09:49:57 + with message-id e1vlbkr-0003ej...@franck.debian.org and subject line Bug#712479: Removed package(s) from unstable has caused the Debian Bug report #712479, regarding RM: py-sendfile -- RoQA; namespace conflict with pysendfile to be marked as done.

Bug#727787: marked as done ([mantis] Install fail)

Your message dated Wed, 27 Nov 2013 09:51:22 + with message-id e1vlbme-0003fv...@franck.debian.org and subject line Bug#730121: Removed package(s) from unstable has caused the Debian Bug report #727787, regarding [mantis] Install fail to be marked as done. This means that you claim that the

Processed (with 1 errors): change severity

Processing commands for cont...@bugs.debian.org: severity 730507 important Bug #730507 [ganglia-web] ganglia-web: CVE-2013-6395: XSS flaw in Ganglia web interface Severity set to 'important' from 'grave' done Unknown command or malformed arguments to command. End of message, stopping

Bug#669831: marked as done (mantis: transition towards Apache 2.4)

Your message dated Wed, 27 Nov 2013 09:51:22 + with message-id e1vlbme-0003fv...@franck.debian.org and subject line Bug#730121: Removed package(s) from unstable has caused the Debian Bug report #669831, regarding mantis: transition towards Apache 2.4 to be marked as done. This means that you

Processed: your mail

Processing commands for cont...@bugs.debian.org: forwarded 715427 https://github.com/dreamworksanimation/openvdb_dev/issues/12 Bug #715427 [src:openvdb] openvdb: FTBFS on i386: unsigned int vs. unsigned long long discrepancy Set Bug forwarded-to-address to

Bug#730345: [Pkg-libvirt-maintainers] Bug#730345: libvirt: FTBFS on armel

Hi, 1.1.4-1.1 is now in Installed state on armel, so presumably this bug should be marked as fixed by this version? Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To

Processed: your mail

Processing commands for cont...@bugs.debian.org: tags 715427 + confirmed upstream Bug #715427 [src:openvdb] openvdb: FTBFS on i386: unsigned int vs. unsigned long long discrepancy Added tag(s) upstream and confirmed. End of message, stopping processing here. Please contact me if you need

Bug#715427:

More info at: https://groups.google.com/forum/#!original/openvdb-forum/x5G2sKP2oCw/FaqY8HXsh2oJ -- 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#728124: tsung doesn't start: init terminating in do_boot

Processing commands for cont...@bugs.debian.org: severity 728124 grave Bug #728124 [tsung] tsung doesn't start: init terminating in do_boot Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 728124:

Bug#728249: marked as done (FTBFS on mips, mipsel and s390x due to -Werror=format-security)

Your message dated Wed, 27 Nov 2013 10:49:10 + with message-id e1vlcga-0008tk...@franck.debian.org and subject line Bug#728249: fixed in mpqc 2.3.1-16 has caused the Debian Bug report #728249, regarding FTBFS on mips, mipsel and s390x due to -Werror=format-security to be marked as done. This

Processed: tagging 672066, reassign 652797 to simgear, fixed 652797 in 2.4.0-1.1, tagging 652797 ...

Processing commands for cont...@bugs.debian.org: tags 672066 - jessie sid wheezy Bug #672066 {Done: Cleto Martín cl...@debian.org} [libzeroc-ice34-dev] zeroc-ice34: slice2cpp generates invalid C++ code Removed tag(s) sid, wheezy, and jessie. reassign 652797 simgear Bug #652797 {Done:

Bug#726859: marked as done (the pyepr build downloads build requirements from the net)

Your message dated Wed, 27 Nov 2013 12:05:28 + with message-id e1vlds0-0002dp...@franck.debian.org and subject line Bug#726859: fixed in pyepr 0.8.1-1 has caused the Debian Bug report #726859, regarding the pyepr build downloads build requirements from the net to be marked as done. This means

Bug#730626: python-swiftclient: CVE-2013-6396

Package: python-swiftclient Severity: grave Tags: security upstream patch Hi Thomas, (This is similar to #718282, CVE-2013-4111 for python-glanceclient.) the following vulnerability was published for python-swiftclient. CVE-2013-6396[0]: does not properly verify the server SSL certificates If

Bug#730632: calligra: FTBFS with libpqxx-4.0

Package: calligra Version: 1:2.6.4-1 Severity: serious Hi Guys, I'm maintaining libpqxx and as it just made to testing transition is now in progress. Unfortunately Calligra is having problems with it. I suppose it's caused by this (300871[1]) upstream bug. As the upstream is preparing to abandon

Bug#730637: gtk+3.0: FTBFS when building with -j8

Source: gtk+3.0 Version: 3.4.2-6 Severity: serious Hi, Building gtk+3.0 from wheezy with -j8 makes it FTBFS: Making all in gtk make[5]: Entering directory `/tmp/buildd/gtk+3.0-3.4.2/debian/build/shared/docs/reference/gtk' DOC Preparing build DOC Scanning header files DOC

Bug#730632: calligra: FTBFS with libpqxx-4.0

forwarded 730632 https://bugs.kde.org/show_bug.cgi?id=300871 thanks On Wednesday 27 November 2013 13:38:55 Marcin Kulisz wrote: Package: calligra Version: 1:2.6.4-1 Severity: serious Hi Guys, I'm maintaining libpqxx and as it just made to testing transition is now in progress.

Processed: Re: Bug#730632: calligra: FTBFS with libpqxx-4.0

Processing commands for cont...@bugs.debian.org: forwarded 730632 https://bugs.kde.org/show_bug.cgi?id=300871 Bug #730632 [calligra] calligra: FTBFS with libpqxx-4.0 Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=300871'. thanks Stopping processing here. Please contact

Bug#730632: calligra: FTBFS with libpqxx-4.0

CCing the release.d.o bug. Marcin: As you already stated, Calligra won't switch to libpqxx4 but to libpq. But that will happen (hopefully) early next year. We really don't want to drop psql support. Is there any chance to have libpqxx3 back with a bigger epoch until that release? The dev

Processed: Re: xbmc: FTBFS with samba 4.0: fatal error: libsmbclient.h: No such file or directory

Processing commands for cont...@bugs.debian.org: tags 728594 pending patch Bug #728594 [xbmc] xbmc: FTBFS with samba 4.0: fatal error: libsmbclient.h: No such file or directory Added tag(s) pending and patch. tags 676702 pending Bug #676702 [xbmc-bin] Uses deprecated HAL Added tag(s) pending.

Bug#728594: xbmc: FTBFS with samba 4.0: fatal error: libsmbclient.h: No such file or directory

tags 728594 pending patch tags 676702 pending thanks Hi, On 11/03/2013 01:52 PM, Andreas Beckmann wrote: Package: xbmc Version: 2:12.0~git20130127.fb595f2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, xbmc/experimental fails to

Bug#730641: request-tracker4: FTBFS: Can't locate Plack/Handler/Starlet.pm in @INC

Package: request-tracker4 Severity: serious Version: 4.0.17-2 Hello there, I tried building your package, but it failed in a clean sbuild chroot: SOME DEPENDENCIES WERE MISSING. PSGI missing dependencies: Plack::Handler::Starlet ...MISSING Can't locate

Processed: severity of 730133 is minor

Processing commands for cont...@bugs.debian.org: severity 730133 minor Bug #730133 {Done: Sylvestre Ledru sylves...@debian.org} [src:java-common] java-common: policy vs lintian: needless-dependency-on-jre Severity set to 'minor' from 'serious' thanks Stopping processing here. Please contact

Bug#724134: marked as done (cups: FTBFS: make[2]: *** No rule to make target `Makedefs'. Stop.)

Your message dated Wed, 27 Nov 2013 17:03:54 + with message-id e1vliwo-0003vb...@franck.debian.org and subject line Bug#724134: fixed in cups 1.6.4-1 has caused the Debian Bug report #724134, regarding cups: FTBFS: make[2]: *** No rule to make target `Makedefs'. Stop. to be marked as done.

Bug#718149: marked as done (turbojson: FTBFS: Tests failed)

Your message dated Wed, 27 Nov 2013 17:04:37 + with message-id e1vlixv-0003p9...@franck.debian.org and subject line Bug#718149: fixed in turbojson 1.3.2-2.1 has caused the Debian Bug report #718149, regarding turbojson: FTBFS: Tests failed to be marked as done. This means that you claim that

Processed: severity of 730400 is serious, severity of 730397 is serious

Processing commands for cont...@bugs.debian.org: severity 730400 serious Bug #730400 [src:wmnut] Please switch build-dependency from libupsclient1-dev to libupsclient-dev Severity set to 'serious' from 'important' severity 730397 serious Bug #730397 [src:collectd] Please switch

Bug#730644: ruby-bio: FTBFS: Error: libxml-ruby library is not present.

Package: ruby-bio Version: 1.4.3.0001-1 Severity: serious Hello there, I tried building your package in a clean unstable chroot, but it failed: === Failure: Error: libxml-ruby library is not present. Please install

Bug#729140: Closing bug

fixed 729140 3.0.4-6 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: Closing bug

Processing commands for cont...@bugs.debian.org: fixed 729140 3.0.4-6 Bug #729140 {Done: Anton Gladky gl...@debian.org} [mpich] mpich2: please remove Build-Depends on valgrind on armel Ignoring request to alter fixed versions of bug #729140 to the same values previously set thanks Stopping

Processed: Closing bug

Processing commands for cont...@bugs.debian.org: fixed 729139 3.0.4-6 Bug #729139 [src:mpich] mpich: please remove Build-Depends on valgrind on armel Marked as fixed in versions mpich/3.0.4-6. thanks Stopping processing here. Please contact me if you need assistance. -- 729139:

Bug#729139: marked as done (mpich: please remove Build-Depends on valgrind on armel)

Your message dated Wed, 27 Nov 2013 19:11:56 +0100 with message-id calf6qjmi7m+w52bw3nsopcajhrxrnau_y+uz2thuprn-q7a...@mail.gmail.com and subject line Closing bug has caused the Debian Bug report #729139, regarding mpich: please remove Build-Depends on valgrind on armel to be marked as done.

Bug#729139: Closing bug

fixed 729139 3.0.4-6 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#730526: why: uninstallable on sid

Le 2013-11-26 08:01, Johan Gronqvist a écrit : * What led up to the situation? The package frama-c was updated to a new upstream version in sid, but the versioned dependency in frama-c was not updated, which makes the package why uninstallable in sid on amd64 (and others). * What

Processed: buzztard: diff for NMU version 0.6.0-1.1

Processing commands for cont...@bugs.debian.org: tags 707351 + patch Bug #707351 [src:buzztard] buzztard: FTBFS: gstobject.h:283:3: error: unknown type name 'GStaticRecMutex' Added tag(s) patch. tags 707351 + pending Bug #707351 [src:buzztard] buzztard: FTBFS: gstobject.h:283:3: error: unknown

Bug#707351: buzztard: diff for NMU version 0.6.0-1.1

tags 707351 + patch tags 707351 + pending thanks Dear maintainer, I've prepared an NMU for buzztard (versioned as 0.6.0-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key

Bug#730652: volumecontrol.app: VolumeControl fails to open with error: can't open mixer /dev/mixer.

Package: volumecontrol.app Version: 0.5-3.1+b1 Severity: grave Justification: renders package unusable * What led up to the situation? 1. Clean install of Debian testing (amd64). 2. Installed gnustep and volumecontrol.app. 3. Tried to start it through desktop menu or through console. *

Bug#718002: marked as done (gir1.2-colordgtk-1.0: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/girepository-1.0/ColordGtk-1.0.typelib)

Your message dated Wed, 27 Nov 2013 19:18:33 + with message-id e1vlkd7-0005dr...@franck.debian.org and subject line Bug#718002: fixed in colord-gtk 0.1.25-1.1 has caused the Debian Bug report #718002, regarding gir1.2-colordgtk-1.0: fails to upgrade from 'wheezy' - trying to overwrite

Processed: Re: Bug#695284: tsung compiled with outdated erlang version

Processing commands for cont...@bugs.debian.org: unarchive 695284 Bug #695284 {Done: Julián Moreno Patiño jul...@debian.org} [tsung] tsung compiled with outdated erlang version Unarchived Bug 695284 found 695284 1.4.2-1.1 Bug #695284 {Done: Julián Moreno Patiño jul...@debian.org} [tsung] tsung

Bug#728574: vxl: FTBFS on ia64 but built there in the past

On Sun, Nov 3, 2013 at 10:48:04 +0100, Mathieu Malaterre wrote: forcemerge 718047 728574 thanks doko@d.o thinks this is not a serious issue: http://bugs.debian.org/718047#34 I should be able to hide the symptoms with a source upload which removes --as-needed to speed up transition.

Processed: closing 730345

Processing commands for cont...@bugs.debian.org: close 730345 1.1.4-1.1 Bug #730345 [libvirt] libvirt: FTBFS on armel There is no source info for the package 'libvirt' at version '1.1.4-1.1' with architecture '' Unable to make a source version for version '1.1.4-1.1' Marked as fixed in versions

Processed: Re: Bug#730637: gtk+3.0: FTBFS when building with -j8

Processing commands for cont...@bugs.debian.org: severity 730637 important Bug #730637 [src:gtk+3.0] gtk+3.0: FTBFS when building with -j8 Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 730637:

Bug#730637: gtk+3.0: FTBFS when building with -j8

severity 730637 important thanks On 27/11/13 16:15, Raphael Geissert wrote: Source: gtk+3.0 Version: 3.4.2-6 Severity: serious Hi, Building gtk+3.0 from wheezy with -j8 makes it FTBFS: We don't specify support for parallel builds in debian/rules, so -jN shouldn't be used. I guess you

Bug#722136: postgrey: diff for NMU version 1.34-1.2

tags 722136 + pending thanks Dear maintainer, I've prepared an NMU for postgrey (versioned as 1.34-1.2) which I'm about to upload. Please find the diff attached. Cheers, Julien diff -u postgrey-1.34/debian/changelog postgrey-1.34/debian/changelog --- postgrey-1.34/debian/changelog +++

Processed: postgrey: diff for NMU version 1.34-1.2

Processing commands for cont...@bugs.debian.org: tags 722136 + pending Bug #722136 [postgrey] postgrey fails to start with perl-base 5.18.1-3 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 722136:

Processed: your mail

Processing commands for cont...@bugs.debian.org: tags 704335 + pending Bug #704335 [lxappearance] Update uploaders field Added tag(s) pending. tags 704336 + pending Bug #704336 [lxappearance-obconf] Update uploaders field Added tag(s) pending. tags 704341 + pending Bug #704341 [lxlauncher]

Bug#715424:

tags 715424 + patch thanks Hi all, attached is a debdiff against the current sid source package. It was recently uploaded to Ubuntu 14.04 and built successfully. Upstream 3.4rc1 does not appear to have any arm-related changes for this build failure. Cheers, --dan debdiff Description: Binary

Processed: your mail

Processing commands for cont...@bugs.debian.org: tags 715424 + patch Bug #715424 [src:dragonegg] dragonegg: FTBFS on arm*: != may not appear in macro parameter list Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 715424:

Bug#726920: marked as done (gst-plugins-good0.10: FTBFS with linux-headers-3.10-3)

Your message dated Wed, 27 Nov 2013 21:20:16 + with message-id e1vlmwu-0003tf...@franck.debian.org and subject line Bug#726920: fixed in gst-plugins-good0.10 0.10.31-3+nmu2 has caused the Debian Bug report #726920, regarding gst-plugins-good0.10: FTBFS with linux-headers-3.10-3 to be marked as

Bug#702366: marked as done (gst-plugins-good0.10: FTBFS with linux-libc-dev from experimental installed)

Your message dated Wed, 27 Nov 2013 21:20:16 + with message-id e1vlmwu-0003tb...@franck.debian.org and subject line Bug#702366: fixed in gst-plugins-good0.10 0.10.31-3+nmu2 has caused the Debian Bug report #702366, regarding gst-plugins-good0.10: FTBFS with linux-libc-dev from experimental

Bug#707365: marked as done (gst-plugins-good0.10: FTBFS: gstv4l2bufferpool.c:184:3: error: 'struct v4l2_buffer' has no member named 'input')

Your message dated Wed, 27 Nov 2013 21:20:16 + with message-id e1vlmwu-0003tb...@franck.debian.org and subject line Bug#702366: fixed in gst-plugins-good0.10 0.10.31-3+nmu2 has caused the Debian Bug report #702366, regarding gst-plugins-good0.10: FTBFS: gstv4l2bufferpool.c:184:3: error:

Bug#722136: marked as done (postgrey fails to start with perl-base 5.18.1-3)

Your message dated Wed, 27 Nov 2013 21:21:00 + with message-id e1vlmxc-0003hi...@franck.debian.org and subject line Bug#722136: fixed in postgrey 1.34-1.2 has caused the Debian Bug report #722136, regarding postgrey fails to start with perl-base 5.18.1-3 to be marked as done. This means that

Bug#728675: marked as done (telepathy-qt: FTBFS: QT4_CREATE_MOC_COMMAND Macro invoked with incorrect arguments for macro)

Your message dated Wed, 27 Nov 2013 21:22:06 + with message-id e1vlmyg-00049k...@franck.debian.org and subject line Bug#728675: fixed in telepathy-qt 0.9.3-2 has caused the Debian Bug report #728675, regarding telepathy-qt: FTBFS: QT4_CREATE_MOC_COMMAND Macro invoked with incorrect arguments

Processed: your mail

Processing commands for cont...@bugs.debian.org: tags 722100 - pending Bug #722100 [bluefish] bluefish: tidy is installed, but it doesn't work in bluefish. Removed tag(s) pending. tags 722110 + pending Bug #722110 [src:lxlauncher] lxlauncher: unsatisfiable libmenu-cache1 (build-)depends Added

Processed: fixed 728675 in 0.9.3-2, tagging 728675

Processing commands for cont...@bugs.debian.org: fixed 728675 0.9.3-2 Bug #728675 {Done: Diane Trout di...@ghic.org} [src:telepathy-qt] telepathy-qt: FTBFS: QT4_CREATE_MOC_COMMAND Macro invoked with incorrect arguments for macro Ignoring request to alter fixed versions of bug #728675 to the

Bug#730278: marked as done (liblttng-ust-ctl2: fails to install, trying to overwrite /usr/lib/x86_64-linux-gnu/liblttng-ust-ctl.so.2.0.0)

Your message dated Wed, 27 Nov 2013 22:04:21 + with message-id e1vlndz-0004gb...@franck.debian.org and subject line Bug#730278: fixed in ust 2.3.0-4 has caused the Debian Bug report #730278, regarding liblttng-ust-ctl2: fails to install, trying to overwrite

Bug#730300: marked as done (liblttng-ust2 and liblttng-ust0: error when trying to install together)

Your message dated Wed, 27 Nov 2013 22:04:21 + with message-id e1vlndz-0004gg...@franck.debian.org and subject line Bug#730300: fixed in ust 2.3.0-4 has caused the Debian Bug report #730300, regarding liblttng-ust2 and liblttng-ust0: error when trying to install together to be marked as done.

Bug#722542: gcc-spu went away but is still being used

On 2013-11-26 13:46, Agustin Henze wrote: Hi all, I'm glad to announce that I've adopted this package :) Hi, Thanks for taking care of this package. :) and I've uploaded a new version (2.0.0-1). This version doesn't build newlib-spu anymore. It arrived on the archive a few days ago, should

Bug#720358: marked as done (libsvn-notify-perl: FTBFS: POD coverage)

Your message dated Wed, 27 Nov 2013 22:18:55 + with message-id e1vlnrf-0007si...@franck.debian.org and subject line Bug#720358: fixed in libsvn-notify-perl 2.81-1.1 has caused the Debian Bug report #720358, regarding libsvn-notify-perl: FTBFS: POD coverage to be marked as done. This means

Bug#724180: bespin: FTBFS: dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision

peter green wrote: I just uploaded a NMU for bespin to delayed/5. There were no changes to the source itself, the only changes were to use a version number ( 0.r1552+nmu1 ) which is compatible with 3.0 (native) and to rebuild against current sid (in particular against the new kde-workspace).

Bug#715424: marked as done (dragonegg: FTBFS on arm*: != may not appear in macro parameter list)

Your message dated Wed, 27 Nov 2013 22:48:33 + with message-id e1vlnul-0004xj...@franck.debian.org and subject line Bug#715424: fixed in dragonegg 3.3-2 has caused the Debian Bug report #715424, regarding dragonegg: FTBFS on arm*: != may not appear in macro parameter list to be marked as done.

Bug#726410: spandsp: FTBFS in parallel mode

Hi Gregor, hi Daniel, the same build failure happened in Ubuntu on i386 and amd64, the 2 fastest building architectures in Ubuntu. This leads me to believe this is a race condition and, while full local builds always succeeded, here is a way to reproduce: After doing a full build, cd into

Bug#730675: Contains static library libminiupnpc.a; should be in -dev package

Package: libminiupnpc5 Version: 1.5-2 Severity: serious libminiupnpc5 contains the static library /usr/lib/libminiupnpc.a . This library should be in the -dev package, not the shared library package. In addition to violating Debian Policy, and making this package incompatible with a potential

Bug#730675: Contains static library libminiupnpc.a; should be in -dev package

On 11/28/2013 09:58 AM, Josh Triplett wrote: Package: libminiupnpc5 Version: 1.5-2 Severity: serious libminiupnpc5 contains the static library /usr/lib/libminiupnpc.a . This library should be in the -dev package, not the shared library package. In addition to violating Debian Policy, and

Processed: Re: Bug#730675: Contains static library libminiupnpc.a; should be in -dev package

Processing commands for cont...@bugs.debian.org: fixed 730675 1.6-2 Bug #730675 [libminiupnpc5] Contains static library libminiupnpc.a; should be in -dev package There is no source info for the package 'libminiupnpc5' at version '1.6-2' with architecture '' Unable to make a source version for

Bug#730678: skimage: FTBFS: favors python(3)-imaging over *-pil

Source: skimage Version: 0.9.3-1 Severity: serious Justification: fails to build from source Automatic builds of skimage have been failing because its build dependencies formally favor the nonexistent python3-imaging package over python3-pil, and Debian's autobuilders only consider the former for

Bug#730679: openvpn: fails to install: ln: failed to create symbolic link '/run/sendsigs.omit.d/openvpn.*.pid': No such file or directory

Package: openvpn Version: 2.3.2-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the

Bug#730680: gpsd: prompting due to modified conffiles which were not modified by the user

Package: gpsd Version: 3.10-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no

Processed: forcibly merging 729778 726720

Processing commands for cont...@bugs.debian.org: forcemerge 729778 726720 Bug #729778 [coinor-libclp1] coinor-libclp1: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man1/clp.1.gz Bug #726720 [coinor-libclp1] coinor-libclp1: fails to upgrade from 'sid' - trying to overwrite