Bug#817116: civicrm: FTBFS: dh_linktree: link destination debian/civicrm-common/usr/share/civicrm/vendor/phenx/php-font-lib/classes is a directory

Source: civicrm Version: 4.7.2+dfsg-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, civicrm fails to build from source in unstable/amd64:

Bug#817012: ruby-amqp and ruby-amq-client: error when trying to install together

Bonjour Sebastien, thanks for the removal of ruby-amq-client. However, I think that you still should add to ruby-amqp Replaces/Conflicts with ruby-amq-client, in order allow for smooth upgrade from old installations. Cheers -Ralf.

Bug#814976: whitedune: diff for NMU version 0.30.10-2.1

Control: tags 814976 + patch Control: tags 814976 + pending Dear maintainer, This bug is caused by a recent update on grep. This update modified a bit the heuristic used for determining when the given input is binary. I've prepared an NMU for whitedune (versioned as 0.30.10-2.1). As I don't

Bug#816376: [Pkg-owncloud-maintainers] Bug#816376: Unfit upstream

On Monday, March 7, 2016 5:43:20 PM AMT Sébastien Villemot wrote: > Dear David, > > First, let me thank you for the work that you put into packaging > owncloud for Debian, it is really appreciated. > > On Tue, 1 Mar 2016 07:07:10 -0400 David =?iso-8859-1?Q?Pr=E9vot?= >

Bug#817006: ack to NMU

Hi Adam, Thank you for your report. I appreciate your enthusiasm. Sorry, I forgot to append my reply to Andreas to #811708: http://lists.alioth.debian.org/pipermail/openrc-devel/Week-of-Mon-20160307/000436.html Basically, my taking to this bug is to ignore it, leaving the users to fix

Processed: whitedune: diff for NMU version 0.30.10-2.1

Processing control commands: > tags 814976 + patch Bug #814976 [src:whitedune] whitedune: FTBFS: dune1.rc.c:1392: syntax error Added tag(s) patch. > tags 814976 + pending Bug #814976 [src:whitedune] whitedune: FTBFS: dune1.rc.c:1392: syntax error Added tag(s) pending. -- 814976:

Bug#817112: libvirglrenderer0 and libvirglrenderer-dev: error when trying to install together

Package: libvirglrenderer-dev,libvirglrenderer0 Version: libvirglrenderer-dev/0.4.0-4 Version: libvirglrenderer0/0.4.0-4 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2016-03-08 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages

Bug#817057: network-manager-openconnect: Update unstable version to latest Upstream Build

Thanks for clarifying the issue you’re seeing. I don’t think this is related to the D-Bus changes. Also, to be clear: I’m not the maintainer of this package, I sponsored mtmiller@’s uploads, who maintains the package. On Tue, Mar 8, 2016 at 3:09 AM, Ryan Chewning wrote: >

Bug#784616: marked as done ([dff] Qt4's WebKit removal)

Your message dated Tue, 08 Mar 2016 06:11:30 + with message-id and subject line Bug#816970: Removed package(s) from unstable has caused the Debian Bug report #784616, regarding [dff] Qt4's WebKit removal to be marked as done. This means that you claim

Bug#798168: marked as done (caret: depends on vtk 5)

Your message dated Tue, 08 Mar 2016 06:10:42 + with message-id and subject line Bug#816918: Removed package(s) from unstable has caused the Debian Bug report #798168, regarding caret: depends on vtk 5 to be marked as done. This means that you claim that

Bug#817092: libjs-handlebars: Minified source is non-free

Package: libjs-handlebars Version: 1.3.0-1 Severity: serious Justification: DSFG §2 Hello, I noticed that, aside from the version in experimental, libjs-handlebars is combined into a single file and already pre-"built". That means that Debian is not distributing the actual source, which fails

Processed: patch and intent to NMU

Processing control commands: > tags -1 +patch Bug #817006 [openrc] openrc: dangling diversion of /usr/sbin/{invoke,update}-rc.d Added tag(s) patch. -- 817006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#817006: patch and intent to NMU

Control: tags -1 +patch Hi! Here's a patch (attached). Because of the bug's severity, and, unlike the cooperate-or-divert issue recently, the fix being obvious, I intend to NMU by, say, today evening, unless you say something. Proposed debdiff attached as well. Meow! -- A tit a day keeps the

Bug#816517: marked as done (boxbackup: FTBFS: TEST FAILURE: Condition [::system("perl testfiles/testrequests.pl") == 0] )

Your message dated Tue, 08 Mar 2016 04:19:46 + with message-id and subject line Bug#816517: fixed in boxbackup 0.11.1~r2837-2 has caused the Debian Bug report #816517, regarding boxbackup: FTBFS: TEST FAILURE: Condition [::system("perl

Bug#816376: Unfit upstream

Hi Sébastien, Le 07/03/2016 12:43, Sébastien Villemot a écrit : > On Tue, 1 Mar 2016 07:07:10 -0400 David Prévot wrote: > >> Upstream doesn’t wish to see their software in Debian anymore. Unless >> the situation changes in the next few months, owncloud will not be part >> of

Bug#817057: network-manager-openconnect: Update unstable version to latest Upstream Build

Michael, I copied you on this bug as you're the package maintainer for network-manager-openconnect and the imports of the upstream are failing. Currently, upstream for network-open-connect is at 1.91 and in Debian unstable/testing are both on the 1.0.2 release which isn't working with the

Bug#817058: marked as done (sketch: FTBFS in stretch (TeX error))

Your message dated Tue, 08 Mar 2016 01:24:48 + with message-id and subject line Bug#817058: fixed in sketch 1:0.3.7-2 has caused the Debian Bug report #817058, regarding sketch: FTBFS in stretch (TeX error) to be marked as done. This means that you claim

Processed: tagging 813647

Processing commands for cont...@bugs.debian.org: > tags 813647 + sid stretch Bug #813647 [connman] connman: daemon no longer starts after upgrade Added tag(s) sid and stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 813647:

Bug#814970: marked as done (libm4ri: FTBFS: libpng12.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status)

Your message dated Mon, 7 Mar 2016 22:52:34 + with message-id <56de0632.7040...@debian.org> and subject line Re: FTBFS: libpng12.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status has caused the Debian Bug report #814970, regarding libm4ri: FTBFS: libpng12.a: error

Processed: notfixed 787294 in 2.1-1, reassign 817012 to ruby-amqp, affects 817012, fixed 817012 in 1.5.1-2

Processing commands for cont...@bugs.debian.org: > # unconfuse bts > notfixed 787294 2.1-1 Bug #787294 {Done: Thomas Liske } [needrestart] needrestart: provide Nagios/Icinga check for needrestart No longer marked as fixed in versions needrestart/2.1-1. > reassign 817012

Bug#816801: Info from 817039

Hi, Just to re-iterate the info I added in 817039 as it's kinda hidden by the merging process: An alternate fix would be to remove the erroneous version check altogether as the version of python-dbus is managed by dpkg, making this check redundant. As to why I've upgraded this to grave: this

Processed: Merge identical bugs 816801 and 817039

Processing commands for cont...@bugs.debian.org: > package volti Limiting to bugs with field 'package' containing at least one of 'volti' Limit currently set to 'package':'volti' > severity 816801 grave Bug #816801 [volti] volti: The script /usr/bin/volti incorrectly checks the version of dbus

Bug#813970: marked as done (dbus: purge fails: invoke-rc.d: initscript dbus, action "stop" failed.)

Your message dated Mon, 07 Mar 2016 22:22:22 + with message-id and subject line Bug#813970: fixed in dbus 1.11.2-1 has caused the Debian Bug report #813970, regarding dbus: purge fails: invoke-rc.d: initscript dbus, action "stop" failed. to be marked as

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

IRC people tell me that a transition bug will fix everything. There is an existing transition bug #815919.

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

Hi Jeff, > Jeff Breidenbach hat am 7. März 2016 um 21:22 > geschrieben: > Thanks for working with me and sorry about the trouble. Don't worry, things like that happen - let's just try to solve the bug completely now :) > I don't know what you mean by not closing bug #815056 >

Processed: reassign 813972 to libncarg-dev, fixed 813972 in 6.3.0-7, affects 813972, tagging 816518 ...

Processing commands for cont...@bugs.debian.org: > reassign 813972 libncarg-dev 6.3.0-6 Bug #813972 {Done: Alastair McKinstry } [libncarg-dev,libncl-dev] libncl-dev and libncarg-dev: error when trying to install together Bug reassigned from package

Bug#784514: QWT

On 07-03-16 21:36, Lisandro Damián Nicanor Pérez Meyer wrote: > On Friday 22 January 2016 17:52:08 Sebastiaan Couwenberg wrote: >> On 22-01-16 17:03, Lisandro Damián Nicanor Pérez Meyer wrote: >>> FWIW you also need Qt5's QWT. The packages are kind of ready in >>> experimental but need a

Bug#815131: marked as done (hg-git: FTBFS: Warning: test-empty-working-tree.t output changed)

Your message dated Mon, 7 Mar 2016 21:13:51 + with message-id <20160307211351.GA4393@tesla> and subject line Re: [Python-apps-team] Bug#815131: hg-git: FTBFS: Warning: test-empty-working-tree.t output changed has caused the Debian Bug report #815131, regarding hg-git: FTBFS: Warning:

Bug#817071: Backup fails if sync_first is used and some files are modified while rsync runs

Package: rsnapshot Version: 1.4.1-1 Severity: grave Tags: upstream patch Hi, I just noticed that my backups are broken since a while. rsnapshot happily makes backups of an old state of its .sync directory. Symptoms on stderr are: [snip]

Processed: reassign 817063 to src:linux, severity of 817063 is important

Processing commands for cont...@bugs.debian.org: > reassign 817063 src:linux 4.3.5-1 Bug #817063 [linux-image-4.3.0-1-powerpc64le] Severe performance regression in Infiniband or IPoIB Bug reassigned from package 'linux-image-4.3.0-1-powerpc64le' to 'src:linux'. No longer marked as found in

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

jbreiden: Just report a transition bug for release.debian.org to +transition back So they rebuild the stuff against the old ABI again

Bug#784514: QWT

On Friday 22 January 2016 17:52:08 Sebastiaan Couwenberg wrote: > On 22-01-16 17:03, Lisandro Damián Nicanor Pérez Meyer wrote: > > FWIW you also need Qt5's QWT. The packages are kind of ready in > > experimental but need a transition. I haven't heard of qwt's > > maintainer in almost two

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

Thanks for working with me and sorry about the trouble. I don't know what you mean by not closing bug #815056 properly. The bug tracker says it is closed. https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=tesseract If I look at the package tracking system, it seems to be claiming

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

It must be mad that there is no libtesseract4 anymore. I'm going to try to get help for that on IRC.

Bug#812087: [pcscd]

On 03/07/2016 07:34 PM, Ludovic Rousseau wrote: > printf("fds: %d %d\n", fds[0].revents, fds[1].revents); fds: 0 1 always I also printed udev_dev from udev_monitor_receive_device() it's always null So we get fds[1].revents but don't get anything from udev_monitor_receive_device() so it's

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

Hi Jeff, thanks for your effort! I think the problem right now is that 3.04.01-4 is still not in testing (I think you didn't close bug #815056 properly). So making tesseract transition to testing would make the situation much better. It might be, that I still have to rebuild gimagereader, as it

Bug#816638: mhonarc: fails to run with perl5.22

Yikes. I wasn't expecting this for mhonarc 2.6.19. Patches from a perl programmer appreciated. Will also check with upstream.

Bug#813647: connman: daemon no longer starts after upgrade

I guess so. There have been updates however on the git, but they were never uploaded: http://anonscm.debian.org/cgit/collab-maint/connman.git/tree/debian/changelog Anyway, it seems an updated package is on it's way: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816542 On Mon, Mar 07, 2016 at

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

I'm in over my head, so I asked for help. The folks on debian-devel IRC channel advised me to not bump soname and instead attempt an ABI repair. It was supposed to be harmless to gimagereader. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815056 I'm really not sure what to do at this point.

Bug#813970: marked as done (dbus: purge fails: invoke-rc.d: initscript dbus, action "stop" failed.)

Your message dated Mon, 07 Mar 2016 19:49:22 + with message-id and subject line Bug#813970: fixed in dbus 1.10.8-1 has caused the Debian Bug report #813970, regarding dbus: purge fails: invoke-rc.d: initscript dbus, action "stop" failed. to be marked as

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 817063 serious Bug #817063 [linux-image-4.3.0-1-powerpc64le] Severe performance regression in Infiniband or IPoIB Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: your mail

Processing commands for cont...@bugs.debian.org: > retitle 816997 Replace swig2.0 by swig in BD Bug #816997 [src:gmsh] gmsh: FTBFS in stretch, build dependencies not in stretch Changed Bug title to 'Replace swig2.0 by swig in BD' from 'gmsh: FTBFS in stretch, build dependencies not in stretch' >

Processed: severity of 812335 is important

Processing commands for cont...@bugs.debian.org: > severity 812335 important Bug #812335 [pocketsphinx] pocketsphinx: FTBFS on mipsel/mips64el: testsuite failures Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 812335:

Bug#812087: [pcscd]

Le 07/03/2016 10:21, Philippe Teuwen a écrit : I recompiled libusb with debug symbols: Normal CPU: Thread 5 (Thread 0x7f0238fcb700 (LWP 24364)): #0 0x7f02394dfb6d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f0238fdbafc in poll (__timeout=-1, __nfds=2,

Bug#816997: gmsh: FTBFS in stretch, build dependencies not in stretch

retitle 816997 Replace swig2.0 by swig in BD severity 816997 important thanks Ok, thanks for clarification. Will fix it in next upload. Cheers Anton Anton 2016-03-07 19:30 GMT+01:00 Julien Cristau : > On Mon, Mar 7, 2016 at 19:23:41 +0100, Anton Gladky wrote: > >> Hi

Bug#816997: gmsh: FTBFS in stretch, build dependencies not in stretch

On Mon, Mar 7, 2016 at 19:23:41 +0100, Anton Gladky wrote: > Hi Santiago, > > thanks for the bug report. AFAIK the unsatisfied build dependencies > can only be a serious bug for the sid. In sid gmsh builds just fine. > Please close this bug. > No, Santiago's right, swig2.0 is replaced by swig,

Bug#813647: connman: daemon no longer starts after upgrade

Isn't connman maintained anymore in Debian ?!

Bug#816857: Submitted bug upstream

On Mon, 7 Mar 2016 16:36:49 +0100 Philip Rinn wrote: > Hi, > > I just want to keep you in the loop: I filed a bug upstream to solve this at > the > bottom of the problem: > > https://github.com/tesseract-ocr/tesseract/issues/254 > > Best, > Philip Thanks Philip. Kind regards, -- Manolo

Bug#816997: gmsh: FTBFS in stretch, build dependencies not in stretch

Hi Santiago, thanks for the bug report. AFAIK the unsatisfied build dependencies can only be a serious bug for the sid. In sid gmsh builds just fine. Please close this bug. Anton 2016-03-07 1:10 GMT+01:00 Santiago Vila : > Package: src:gmsh > Version: 2.11.0+dfsg1-2 >

Bug#816742: marked as done (libc6: sem_post/sem_wait not working for 32bit to 64bit inter-process communication)

Your message dated Mon, 7 Mar 2016 18:41:07 +0100 with message-id <20160307174107.ga29...@aurel32.net> and subject line Re: Bug#816742: libc6: sem_post/sem_wait not working for 32bit to 64bit inter-process communication has caused the Debian Bug report #816742, regarding libc6: sem_post/sem_wait

Bug#815062: marked as done (openttd-openmsx: FTBFS: override_dh_auto_test [..] Differences in md5sums)

Your message dated Mon, 07 Mar 2016 17:33:33 + with message-id and subject line Bug#815062: fixed in openttd-openmsx 0.3.1-4 has caused the Debian Bug report #815062, regarding openttd-openmsx: FTBFS: override_dh_auto_test [..] Differences in md5sums to

Bug#817057: network-manager-openconnect: Update unstable version to latest Upstream Build

On Mon, Mar 7, 2016 at 9:07 AM, Ryan Chewning wrote: > Package: network-manager-openconnect > Version: 1.0.2-1+b1 > Severity: grave > Tags: upstream > Justification: renders package unusable > > The latest builds of networkmanager in testing/unstable no longer support > dbus.

Bug#817058: sketch: FTBFS in stretch (TeX error)

Package: src:sketch Version: 1:0.3.7-1 Severity: serious Dear maintainer: I tried to build this package with "dpkg-buildpackage -A" (i.e. only architecture-independent packages), and it failed. The error, however, seems to happen with ordinary "dpkg-buildpackage" as well, which is why I'm using

Bug#817059: vagrant: domain_name gem not found

Package: vagrant Version: 1.8.1+dfsg-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, Until #817011 on ruby-domain-name is fixed by the maintainer, vagrant does not work without a manual fix (gemspec file) available in

Bug#817057: network-manager-openconnect: Update unstable version to latest Upstream Build

Package: network-manager-openconnect Version: 1.0.2-1+b1 Severity: grave Tags: upstream Justification: renders package unusable The latest builds of networkmanager in testing/unstable no longer support dbus. https://blogs.gnome.org/dcbw/2016/02/19/die-dbus-glib-die/ There is an updated version of

Bug#817012: marked as done (ruby-amqp and ruby-amq-client: error when trying to install together)

Your message dated Mon, 07 Mar 2016 16:46:18 + with message-id and subject line Bug#817012: fixed in ruby-amqp 1.5.1-2 has caused the Debian Bug report #817012, regarding ruby-amqp and ruby-amq-client: error when trying to install together to be marked as

Bug#816376: Unfit upstream

Dear David, First, let me thank you for the work that you put into packaging owncloud for Debian, it is really appreciated. On Tue, 1 Mar 2016 07:07:10 -0400 David =?iso-8859-1?Q?Pr=E9vot?= wrote: > Upstream doesn’t wish to see their software in Debian anymore. Unless > the

Bug#812638: marked as done (gbirthday: FTBFS - build-depends on non-existent package python-support)

Your message dated Mon, 07 Mar 2016 16:22:17 + with message-id and subject line Bug#812638: fixed in gbirthday 0.6.10-0.1 has caused the Debian Bug report #812638, regarding gbirthday: FTBFS - build-depends on non-existent package python-support to be

Processed: retitle 815125 to Boot failure in 4.4 related to EFI run-time calls, forcibly merging 815125 816157

Processing commands for cont...@bugs.debian.org: > retitle 815125 Boot failure in 4.4 related to EFI run-time calls Bug #815125 [src:linux] linux-image-4.4.0-1-amd64 fails to load initrd - no booting Bug #815779 [src:linux] linux-image-4.4.0-1-amd64: Recent kernels freeze after loading

Bug#816857: Submitted bug upstream

Hi, I just want to keep you in the loop: I filed a bug upstream to solve this at the bottom of the problem: https://github.com/tesseract-ocr/tesseract/issues/254 Best, Philip signature.asc Description: PGP signature

Processed: Re: linux-image-4.4.0-trunk-686-pae: sdhci module repeatedly crashes, eventually brings whole system down

Processing control commands: > severity -1 important Bug #815298 [src:linux] linux-image-4.4.0-trunk-686-pae: sdhci module repeatedly crashes, eventually brings whole system down Severity set to 'important' from 'grave' > tag -1 moreinfo Bug #815298 [src:linux] linux-image-4.4.0-trunk-686-pae:

Bug#815298: linux-image-4.4.0-trunk-686-pae: sdhci module repeatedly crashes, eventually brings whole system down

Control: severity -1 important Control: tag -1 moreinfo On Sat, 20 Feb 2016 17:30:59 + Thomas Thurman wrote: [...] > Here's an excerpt from kern.log a few days ago, showing the problem: >  > Feb 15 11:21:48 emley-moor kernel: [  169.188034] usb 1-1.2: reset high-speed >

Processed: tagging 815125, bug 815125 is forwarded to m...@codeblueprint.co.uk

Processing commands for cont...@bugs.debian.org: > tags 815125 + upstream Bug #815125 [src:linux] linux-image-4.4.0-1-amd64 fails to load initrd - no booting Bug #815779 [src:linux] linux-image-4.4.0-1-amd64: Recent kernels freeze after loading initramfs on HP HBook 80 Added tag(s) upstream.

Processed: Re: linux-image-4.4.0-1-amd64 spontaneously reboots my Braswell NUC5PPYH

Processing control commands: > severity -1 important Bug #815652 [src:linux] linux-image-4.4.0-1-amd64 spontaneously reboots my Braswell NUC5PPYH Severity set to 'important' from 'critical' > tag -1 moreinfo Bug #815652 [src:linux] linux-image-4.4.0-1-amd64 spontaneously reboots my Braswell

Bug#815652: linux-image-4.4.0-1-amd64 spontaneously reboots my Braswell NUC5PPYH

Control: severity -1 important Control: tag -1 moreinfo On Tue, 23 Feb 2016 05:50:26 -0500 james sarbello wrote: [...] > Just to note in passing, the last two kernel message lines > before the reboot is related to ACPI, something like: >  > [#] ACPI: Core revision # >

Processed: retitle 808038 to linux-image should force upgrade of initramfs-tools to ensure nvme is included ...

Processing commands for cont...@bugs.debian.org: > retitle 808038 linux-image should force upgrade of initramfs-tools to ensure > nvme is included Bug #808038 [src:linux] linux-image-4.4.0-rc4-amd64: Fails to boot on kernel 4.4rc4 Changed Bug title to 'linux-image should force upgrade of

Bug#817011: ruby-domain-name: missing RubyGems integration, breaks other softwares like Vagrant

On Mon, 07 Mar 2016 15:15:38 +0900 =?UTF-8?Q?Marc_Dequ=C3=A8nes_=28duck=29?= wrote: > I'm in the team but I don't have time or tools at the moment to get into > more details why this file is missing (I remember gem2deb to already > have all the necessary magic and this

Bug#812406: usb: Strange USB bugs

On 2016-01-23 23:56, Aurelien Jarno wrote: > control: tag -1 + moreinfo > control: tag -1 - upstream > > Hi, > > On 2016-01-23 15:05, Nickolay Ilyushin wrote: > > Package: libusb-1.0-0 > > Version: 2:1.0.20-1 > > Severity: critical > > File: usb > > Tags: upstream > > Justification: causes

Bug#817042: duplicity: corrupted files when backup is interrupted

Package: duplicity Version: 0.7.06-1 Severity: critical Justification: causes serious data loss * What led up to the situation? I backup my homedir with duplicity * What exactly did you do (or not do) that was effective (or ineffective)? I try to restore a file * What was the outcome

Bug#817008: unfulfilled dependencies

Thank you for reporting the bug. Actually the reason to this is that I used ${source:Version} for "android-sdk-platform-tools" and "android-sdk-build-tools", which is substituted to the version of the source package rather than their own. I have fixed it but not yet uploaded it. The reason of

Bug#817041: librem0: Missing run-time dependency on libre0

Package: librem0 Version: 0.4.7-1 Severity: serious Hi! This package provides a shared library that is not self-contained, and it is missing a run-time dependency on libre0, as it uses some of its symbols. The library should link against all libraries it uses directly, because otherwise it is

Processed: Re: ruby-amqp and ruby-amq-client: error when trying to install together

Processing commands for cont...@bugs.debian.org: > tags 817012 + pending Bug #817012 [ruby-amq-client,ruby-amqp] ruby-amqp and ruby-amq-client: error when trying to install together Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 817012:

Bug#817012: ruby-amqp and ruby-amq-client: error when trying to install together

tags 817012 + pending thanks Hi Ralf, Thanks for this bug report! Just fixed the issue (request a ROM of ruby-amq-client, (upstream dead), and prepared a new version for ruby-amqp). Cheers, Seb signature.asc Description: PGP signature

Bug#817039: volti: Fails to start due to incorrect python-dbus version check

Package: volti Version: 0.2.3-6 Severity: grave Justification: renders package unusable Dear Maintainer, The python-dbus version check on line 27 of /usr/lib/volti/volti.run is incorrect due to recent changes to how the version of python-dbus is stored. > assert dbus.version >= (0, 80, 0)

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

Your message dated Mon, 07 Mar 2016 13:50:02 + with message-id and subject line Bug#803286: fixed in mtpaint 3.40-2.2 has caused the Debian Bug report #803286, regarding prepare for giflib5 to be marked as done. This means that you claim that the problem

Bug#803286: mtpaint: diff for NMU version 3.40-2.2

Control: tags 803286 + pending Dear maintainer, I've prepared an NMU for mtpaint (versioned as 3.40-2.2) and uploaded it to unstable. I am attaching the debdiff to this bug report. Regards, Markus diff -Nru mtpaint-3.40/debian/changelog mtpaint-3.40/debian/changelog ---

Processed: mtpaint: diff for NMU version 3.40-2.2

Processing control commands: > tags 803286 + pending Bug #803286 [src:mtpaint] prepare for giflib5 Added tag(s) pending. -- 803286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#800188: marked as done (ebook-dev-alp: Please migrate a supported debhelper compat level)

Your message dated Mon, 07 Mar 2016 11:49:45 + with message-id and subject line Bug#800188: fixed in ebook-dev-alp 200407-2 has caused the Debian Bug report #800188, regarding ebook-dev-alp: Please migrate a supported debhelper compat level to be marked as

Bug#800306: marked as done (mpi-specs: Please migrate a supported debhelper compat level)

Your message dated Mon, 07 Mar 2016 11:20:19 + with message-id and subject line Bug#800306: fixed in mpi-specs 20040719-3 has caused the Debian Bug report #800306, regarding mpi-specs: Please migrate a supported debhelper compat level to be marked as done.

Processed: bug 817025 is forwarded to https://github.com/coreos/fleet/issues/1468

Processing commands for cont...@bugs.debian.org: > forwarded 817025 https://github.com/coreos/fleet/issues/1468 Bug #817025 [src:fleet] fleet: FTBFS: coreos.go:26:2: cannot find package "github.com/opencontainers/runc/libcontainer/netlink Set Bug forwarded-to-address to

Processed: tagging 817025

Processing commands for cont...@bugs.debian.org: > tags 817025 + confirmed upstream Bug #817025 [src:fleet] fleet: FTBFS: coreos.go:26:2: cannot find package "github.com/opencontainers/runc/libcontainer/netlink Added tag(s) confirmed and upstream. > thanks Stopping processing here. Please

Bug#816587: shared-mime-info: FTBFS: LaTeX Error: File `ulem.sty' not found.

reassign 816587 docbook-utils reassign 817026 docbook-utils reassign 817027 docbook-utils forcemerge 816587 817026 817027 thanks On Do, 2016-03-03 at 10:45 +0200, Sebastian Dröge wrote: > On Do, 2016-03-03 at 08:36 +, Chris Lamb wrote: > > > > Source: shared-mime-info > > Version: 1.5-2 > >

Processed: Re: Bug#816587: shared-mime-info: FTBFS: LaTeX Error: File `ulem.sty' not found.

Processing commands for cont...@bugs.debian.org: > reassign 816587 docbook-utils Bug #816587 [src:shared-mime-info] shared-mime-info: FTBFS: LaTeX Error: File `ulem.sty' not found. Bug reassigned from package 'src:shared-mime-info' to 'docbook-utils'. No longer marked as found in versions

Bug#817000: pymvpa2: FTBFS in stretch, build dependencies not in stretch

On Sun, 6 Mar 2016, Yaroslav Halchenko wrote: > On Mon, 07 Mar 2016, Santiago Vila wrote: > > The following packages have unmet dependencies: > > sbuild-build-depends-pymvpa2-dummy : Depends: swig2.0 but it is not > > installable or > >swig (<=

Bug#817025: fleet: FTBFS: coreos.go:26:2: cannot find package "github.com/opencontainers/runc/libcontainer/netlink

Source: fleet Version: 0.11.5+dfsg1-3 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, fleet fails to build from source in unstable/amd64:

Bug#817027: gstreamer1.0: FTBFS: LaTeX Error: File `ulem.sty' not found.

Source: gstreamer1.0 Version: 1.6.3-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, gstreamer1.0 fails to build from source in

Bug#817026: gstreamer0.10: FTBFS: ! LaTeX Error: File `ulem.sty' not found.

Source: gstreamer0.10 Version: 0.10.36-1.5 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, gstreamer0.10 fails to build from source in

Processed: bug 812114 is forwarded to https://github.com/jsonpickle/jsonpickle/issues/142

Processing commands for cont...@bugs.debian.org: > forwarded 812114 https://github.com/jsonpickle/jsonpickle/issues/142 Bug #812114 [src:jsonpickle] jsonpickle: FTBFS: SyntaxError: unexpected EOF while parsing Set Bug forwarded-to-address to

Bug#812087: [pcscd]

I forgot to say, removing TEMP_FAILURE_RETRY() didn't change anything.

Bug#812087: [pcscd]

I recompiled libusb with debug symbols: Normal CPU: Thread 5 (Thread 0x7f0238fcb700 (LWP 24364)): #0 0x7f02394dfb6d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f0238fdbafc in poll (__timeout=-1, __nfds=2, __fds=0x7f0238fcaee0) at

Bug#811185: failed tests

I need to test on my computer, this could be related to a new swi-prolog version introduction incompatible backwards modifications.

Processed: more fiddling to get bts to understand its done

Processing commands for cont...@bugs.debian.org: > notfound 810881 totem-pl-parser/3.10.6-1 Bug #810881 {Done: Andreas Henriksson } [libtotem-plparser18] libtotem-plparser18: linker issue, causes grilo-plugins to FTBFS No longer marked as found in versions