Processed: Re: Processed (with 1 errors): found 763803 1:0.8.0+git20141002-1

Processing commands for cont...@bugs.debian.org: > found 763803 1:0.8.0+git20141002-1 Bug #763803 [ettercap-common] ettercap-common: cannot be upgraded because conflicts with same version of ettercap-graphical Marked as found in versions ettercap/1:0.8.0+git20141002-1. > thanks Stopping processin

Bug#760735: libgnutls26: [dummy bug] Must not be shipped in jessie

On 2014-10-03 Kurt Roeckx wrote: > On Sun, Sep 07, 2014 at 02:16:03PM +0200, Andreas Metzler wrote: >> Package: libgnutls26 >> Version: 2.12.23-17 >> GnuTLS 2.12 should not be shipped in jessie, let's make sure it does >> not accidentally re-enter testing after its removal (which is not yet >> s

Bug#763823: util-linux: diff for NMU version 2.20.1-5.10

Dear maintainer, I made an NMU for util-linux (versioned as 2.20.1-5.10) with the attached changes. Ben. -- Ben Hutchings One of the nice things about standards is that there are so many of them. diff -u util-linux-2.20.1/debian/changelog util-linux-2.20.1/debian/changelog --- util-linux-2.20.1

Bug#763823: marked as done (hwclock-set script should protect against being run twice)

Your message dated Sat, 04 Oct 2014 03:23:33 + with message-id and subject line Bug#763823: fixed in util-linux 2.20.1-5.10 has caused the Debian Bug report #763823, regarding hwclock-set script should protect against being run twice to be marked as done. This means that you claim that the pr

Bug#763948: evolution-mapi build-dependencies unsatisfiable in jessie

Package: evolution-mapi Severity: serious Debian policy requires that debian packages are buildable within the same release. Your package build-depends on libmapi-dev (>= 1:2.2). libmapi-dev is provided by source package openchange which is at version 1.2.1-1 in testing. The new version of op

Processed: tagging 763777

Processing commands for cont...@bugs.debian.org: > tags 763777 + pending Bug #763777 [initramfs-tools] fsck: Superblock set in the future, fixing system clock Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 763777: http://bugs.debian.org/cgi

Processed (with 2 errors): Re: Bug#674743: nullmailer: init.d: LSB: Should-Start: network-manager

Processing commands for cont...@bugs.debian.org: > unarchive 674743 > tag 674743 +wontfix Bug #674743 [nullmailer] nullmailer: init.d: LSB: Should-Start: network-manager Added tag(s) wontfix. > archive 674743 Bug #674743 [nullmailer] nullmailer: init.d: LSB: Should-Start: network-manager Bug 67474

Processed: your mail

Processing commands for cont...@bugs.debian.org: > notfound 763803 1:0.8.0+git20140910-1 Bug #763803 [ettercap-common] ettercap-common: cannot be upgraded because conflicts with same version of ettercap-graphical No longer marked as found in versions ettercap/1:0.8.0+git20140910-1. > thanks Stopp

Bug#763923: marked as done (libldb1: wheezy backport breaks stock wheezy sssd)

Your message dated Sat, 4 Oct 2014 01:28:26 +0200 with message-id <20141003232826.ga3...@jelmer.uk> and subject line has caused the Debian Bug report #763923, regarding libldb1: wheezy backport breaks stock wheezy sssd to be marked as done. This means that you claim that the problem has been deal

Processed: severity of 763744 is important

Processing commands for cont...@bugs.debian.org: > severity 763744 important Bug #763744 [samba] samba: Huge number of samba panic messages Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 763744: http://bugs.debian.org/cg

Bug#763360: Bug#754988: Bug#763360: libjpeg-turbo is hijacking binaries from other source packages

On Fri, Oct 03, 2014 at 12:37:09PM +0200, Emilio Pozuelo Monfort wrote: > >>seemed like the sensible thing to do, and I didn't see any problem > >>with the proposed plan. After all, libjpeg62 had been long > >>deprecated in favor of libjpeg8. Neither of us thought you would > >>care about libjpeg62

Bug#763685: marked as done (apt-cacher-ng: FTBFS[!linux]: C++11 syntax error, systemd dependency)

Your message dated Fri, 03 Oct 2014 22:18:42 + with message-id and subject line Bug#763685: fixed in apt-cacher-ng 0.8.0~rc4-1 has caused the Debian Bug report #763685, regarding apt-cacher-ng: FTBFS[!linux]: C++11 syntax error, systemd dependency to be marked as done. This means that you cla

Bug#763840: iagno: file conflict with gnome-accessibility-themes < 3.14

Hey man, Thanks for the patch, but where do you go to apply it? On Fri, 03 Oct 2014 07:25:54 +0200 Pino Toscano wrote: > Package: iagno > Version: 1:3.14.0-1 > Severity: serious > Tags: patch > Justification: Policy 7.6.1, Policy 10.1 > > Hi, > > when upgrading iagno to 1:3.14.0-1 (i.e. today's

Bug#763840: iagno: file conflict with gnome-accessibility-themes < 3.14

I'm seeing this bug too, for what it's worth. By the way, if you do # apt-get remove iagno ...the result is very bad -- apt-get claims it will remove 'gnome' and 'gnome-desktop-environment', among other things! The reason appears to be that 'gnome' depends on 'gnome-games', and 'gnome-games'

Bug#763924: onak: unbuildable on !linux archs

Source: onak Version: 0.4.5-1 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) Hi, currently onak cannot be built on non-Linux architectures, because of the systemd (Linux-specific) build dependencies. Since the features they enable are

Bug#763923: libldb1: wheezy backport breaks stock wheezy sssd

Package: libldb1 Version: 1:1.1.17-1~bpo70+1 Severity: critical Justification: breaks unrelated software Dear Maintainer, originally looking for a Sogo update, I installed samba from wheezy backports, which includes the current libldb1 (i.e. 1.1.17). Unfortunately, the version handling of libld

Bug#763922: torque: CVE-2014-3684: non-root users able to kill any process on any node in a job

Source: torque Version: 2.4.8+dfsg-9 Severity: grave Tags: security upstream fixed-upstream Dear Torque maintainers, the following vulnerability was published for torque. CVE-2014-3684[0]: non-root users able to kill any process on any node in a job >From a quick look it looked also applicable

Bug#760033: marked as done (debhelper: dh_clean removes Git refs information with certain suffixes like .orig, .rej, ...)

Your message dated Fri, 03 Oct 2014 19:33:41 + with message-id and subject line Bug#760033: fixed in debhelper 9.20141003 has caused the Debian Bug report #760033, regarding debhelper: dh_clean removes Git refs information with certain suffixes like .orig, .rej, ... to be marked as done. Thi

Bug#759850: marked as done (apq-postgresql: FTBFS: ld: cannot find -lgnat-4.9.1)

Your message dated Fri, 3 Oct 2014 21:33:05 +0200 with message-id <20141003193305.GA5572@pegase> and subject line Bug 759850 has been closed by 3.2.0-3 has caused the Debian Bug report #759850, regarding apq-postgresql: FTBFS: ld: cannot find -lgnat-4.9.1 to be marked as done. This means that you

Bug#763919: php-sasl: .deb is missing mandatory field

Package: php-sasl Version: 0.1.0-3 Severity: serious Hi, php-sasl's upload on arm64 is being rejected because it's missing a mandatory field. I'm not sure which one it is, but I think it's Description. I get: $ dpkg -I php5-sasl_0.1.0-3_arm64.deb new debian package, version 2.0. size 10824 by

Bug#747141: [debhelper-devel] Bug#747141: debhelper: "dh_installdocs --link-doc" breaks binNMUs

Aurelien Jarno wrote: > We have scheduled a few thousands of binNMUs on s390x due to the libc > ABI breakage. It occurs that most of the non binNMUs safe packages are > wrongly using this --link-doc option. > > I am therefore increasing the severity of this bug. dh_installdocs > --link-doc should

Bug#763891: marked as done (pkg-perl-tools: Lintian check module-name traverses user's current directory instead of package contents)

Your message dated Fri, 03 Oct 2014 18:34:44 + with message-id and subject line Bug#763891: fixed in pkg-perl-tools 0.19 has caused the Debian Bug report #763891, regarding pkg-perl-tools: Lintian check module-name traverses user's current directory instead of package contents to be marked as

Bug#762860: dfc: "Error while stating /run/user/1000/gvfs : No such file or directory"

Hi Thomas, On Thu, 25 Sep 2014 20:28:58 +0200 Thomas Kreft wrote: > "Error while stating /run/user/1000/gvfs : No such file or directory" > […] > ...but a file called gvfs nowhere to be found in /run/user. I can't reproduce this problem on my box. I do have gvfs installed (version 1.22.0-1+b1),

Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked

Package: reportbug Version: 6.5.1 Followup-For: Bug #758619 What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: ** Environment settings: INTERFACE="text" ** /home/tester/.reportbugrc: reportbug_version "6.4.4" mode novice ui

Bug#762612: reportbug, mirage and pyrenamer not starting

Package: reportbug Version: 6.5.1 Package: mirage Version: 0.9.5.1-3 Package: pyrenamer Version: 0.6.0-1.1 Apart from reportbug (#762612 merged with 758619) and mirage (#763602) I also get the same error message when trying to start pyrenamer. Judging from the time the problem arose first and

Bug#760735: libgnutls26: [dummy bug] Must not be shipped in jessie

On Sun, Sep 07, 2014 at 02:16:03PM +0200, Andreas Metzler wrote: > Package: libgnutls26 > Version: 2.12.23-17 > Severity: serious > > GnuTLS 2.12 should not be shipped in jessie, let's make sure it does > not accidentally re-enter testing after its removal (which is not yet > scheduled). Can you

Bug#763763: marked as done (vtk6: FTBFS on arm*)

Your message dated Fri, 03 Oct 2014 17:51:39 + with message-id and subject line Bug#763763: fixed in vtk6 6.1.0+dfsg2-3 has caused the Debian Bug report #763763, regarding vtk6: FTBFS on arm* to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#763148: Prevent migration to jessie

Hi Michael, On 03.10.2014 02:10, Michael Gilbert wrote: On Thu, Oct 2, 2014 at 1:16 PM, Andreas Cadhalpun wrote: So I hope the maintainer of chromium is now happy to be able to use more system libraries. chromium moves way too fast to take advantage of any stable ffmpeg api. How did you com

Bug#760038: minor problem subsists

Dear maintainer, Occasionally when I log in to e17, the screen goes black, then I get the following error message: Enlightenment Error This is very bad. Enlightenment SEGV'd. This is not meant to happen and is likely a sign of a bug in Enlightenment or the libraries it relies on. We were not a

Bug#763909: viewmol: /usr/bin/viewmol missing for most archs

Source: viewmol Version: 2.4.1-20 Severity: serious Hi Maintainer I noticed that /usr/bin/viewmol is only present in the amd64 viewmol package. For all other archs built on the buildds, /usr/bin/viewmol is missing. Excerpt from the i386 build log: make[1]: Entering directory `/«PKGBUILDDIR»/sou

Bug#763906: nghttp2: FTBFS on armel

Source: nghttp2 Version: 0.6.2-2 Severity: serious Justification: FTBFS Hello, Your package fails to build from source on Debian autobuilder network. Please check your package build logs at: g++ -DHAVE_CONFIG_H -I. -I..

Bug#763725: git-flow: "Bad variable name" when space characters in path

On Thu, 02 Oct 2014 09:30:33 +0200 Jeremie Burtin wrote: > Package: git-flow > Version: 1.7.0-1 > Severity: grave > Tags: upstream > Justification: renders package unusable > > Hi, > When trying to perform "git flow feature start feature_name", the script fails > with a "Bad variable name" error.

Processed: adjusting severity

Processing commands for cont...@bugs.debian.org: > severity 763890 important Bug #763890 [xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: glxinfo crashes my machine Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: Re: Bug#76361: marked as done (mutt: saving/deleting a thread while in limited view doesn't work)

Processing commands for cont...@bugs.debian.org: > reopen 76361 Bug #76361 {Done: Dirk Eddelbuettel } [mutt] mutt: saving/deleting a thread while in limited view doesn't work Bug reopened Ignoring request to alter fixed versions of bug #76361 to the same values previously set > close 763761 Bug

Bug#763899: marked as done (jenkins: multiple security vulnerabilities)

Your message dated Fri, 03 Oct 2014 15:49:44 + with message-id and subject line Bug#763899: fixed in jenkins 1.565.3-1 has caused the Debian Bug report #763899, regarding jenkins: multiple security vulnerabilities to be marked as done. This means that you claim that the problem has been dealt

Bug#763816: marked as done (libopenscenegraph100: osgDB fails to load any plugin)

Your message dated Fri, 03 Oct 2014 15:26:36 + with message-id and subject line Bug#763816: fixed in openscenegraph 3.2.1-4 has caused the Debian Bug report #763816, regarding libopenscenegraph100: osgDB fails to load any plugin to be marked as done. This means that you claim that the problem

Bug#763818: marked as done (libopenscenegraph100: Unable to load any model in flightgear)

Your message dated Fri, 03 Oct 2014 15:26:36 + with message-id and subject line Bug#763816: fixed in openscenegraph 3.2.1-4 has caused the Debian Bug report #763816, regarding libopenscenegraph100: Unable to load any model in flightgear to be marked as done. This means that you claim that the

Bug#729160: marked as done (mricron: FTBFS on armhf, powerpc, sparc)

Your message dated Fri, 03 Oct 2014 15:23:51 + with message-id and subject line Bug#729160: fixed in mricron 0.20140804.1~dfsg.1-1 has caused the Debian Bug report #729160, regarding mricron: FTBFS on armhf, powerpc, sparc to be marked as done. This means that you claim that the problem has b

Bug#763587: Still having problems

>>> Undefined User writes: > I'm sorry, but I didn't understand. You say it is already fixed, but > I'm still not able to upgrade the system (03-oct-2014). Do we have to > wait for the fix to be uploaded to Debian servers? The fix is on debian unstable, and will in time make its way to testi

Processed: Re: Bug#762773: argyll: FTBFS on kFreeBSD: linux/usbdevice_fs.h: No such file or directory

Processing commands for cont...@bugs.debian.org: > found 762773 1.6.3-2 Bug #762773 {Done: Jörg Frings-Fürst } [src:argyll] argyll: FTBFS on kFreeBSD: linux/usbdevice_fs.h: No such file or directory Marked as found in versions argyll/1.6.3-2; no longer marked as fixed in versions argyll/1.6.3-2

Bug#762773: argyll: FTBFS on kFreeBSD: linux/usbdevice_fs.h: No such file or directory

found 762773 1.6.3-2 thanks Thanks for looking into this bug. Although the original error is indeed gone, there are still USB-related build errors on kFreeBSD: spectro/hidio.c:90:21: fatal error: usbhid.h: No such file or directory Per https://packages.debian.org/search?searchon=contents&key

Bug#763899: jenkins: multiple security vulnerabilities

Package: jenkins Version: 1.565.2-2 Severity: grave Tags: security Dear Maintainer, The upstream vendor announced a security advisory. In this advisory, some vulnerabilities are rated critical severity. https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2014-10-01 >SECURITY-8

Bug#759208: goplay: shows no results at all

Contro: tag -1 + help I've now tested version 0.8 in testing, after running update-apt-xapian-index as root, and the GUI showed up but no programs were listed neither in goplay nor in golearn. I have no idea how to debug this, but the current implementation of goplay seem to be compiletely broken

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

for those who cannot live without keepnote ,like myself, there is a way to run it in a meantime. I dont understand this debdiff thingy, sorry devs, so I downgraded following packages : gir1.2-glib-2.0_1.40.0-2_i386.deb libglib-perl_1.305-1+b1_i386.deb libglib2.0-data_2.40.0-4_all.deb libglibmm-2

Bug#763263: fbi: FTBFS: transupp.c:892: undefined reference to `jpeg_core_output_dimensions'

On Sun, Sep 28, 2014 at 06:41:58PM +0200, David Suárez wrote: > Source: fbi > Version: 2.07-14 > Severity: serious > Tags: jessie sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20140926 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your

Processed: limit source to lava-server, tagging 763310

Processing commands for cont...@bugs.debian.org: > limit source lava-server Limiting to bugs with field 'source' containing at least one of 'lava-server' Limit currently set to 'source':'lava-server' > tags 763310 + pending Bug #763310 [src:lava-server] Fails to upgrade from 2014.07.1-1 to 2014.0

Bug#762485: geographiclib: FTBFS on hppa: symbols

severity 762485 important thanks On Wed, 1 Oct 2014 20:12:03 -0400 John David Anglin wrote: > Package: geographiclib Version: 1.37-2 Followup-For: Bug #762485 > > See build log: > http://buildd.debian-ports.org/status/fetch.php?pkg=geographiclib&arch=hppa&ver=1.37-2&stamp=1412084220 > > -- Sys

Processed: Re: geographiclib: FTBFS on hppa: symbols

Processing commands for cont...@bugs.debian.org: > severity 762485 important Bug #762485 {Done: Ross Gammon } [src:geographiclib] geographiclib: FTBFS on 32-bit architectures: symbols not quite as expected Severity set to 'important' from 'serious' > thanks Stopping processing here. Please conta

Bug#763891: pkg-perl-tools: Lintian check module-name traverses user's current directory instead of package contents

Package: pkg-perl-tools Version: 0.12 Severity: serious Justification: maintainer's opinion, severe performance issue File: /usr/share/lintian/checks/pkg-perl/module-name.pm Hi, commit c096fef2d01e5d75e0376a6eadf89d187e449aa0 (by yours truly) introduced a severe performance issue depending on the

Bug#763765: marked as done (afflib: FTBFS on several arches)

Your message dated Fri, 03 Oct 2014 13:33:38 + with message-id and subject line Bug#763765: fixed in afflib 3.7.4+dfsg-3 has caused the Debian Bug report #763765, regarding afflib: FTBFS on several arches to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#763890: xserver-xorg-video-nouveau: glxinfo crashes my machine

Package: xserver-xorg-video-nouveau Version: 1:1.0.11-1 Severity: serious Since I upgraded from wheezy to jessie, mesa no longer works ok in my machine. When I start stellarium, for example, the screen becomes a mosaic and the machine freezes completely. (I'm using "severity: serious" because thi

Bug#723964: Fix uploaded

FTR, I've just uploaded a fix (Gregor's patch #2) to 7-day DELAYED. -- Marcin Owsiany http://marcin.owsiany.pl/ GnuPG: 2048R/02F946FC 35E9 1344 9F77 5F43 13DD 6423 DBF4 80C6 02F9 46FC -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscr

Bug#748525: marked as done (Fails on launch if set to widescreen)

Your message dated Fri, 03 Oct 2014 13:19:28 + with message-id and subject line Bug#748525: fixed in pangzero 1.4.1+git20121103-1 has caused the Debian Bug report #748525, regarding Fails on launch if set to widescreen to be marked as done. This means that you claim that the problem has been

Bug#761522: marked as done (sisu-guice: FTBFS: Error(s) found in manifest configuration)

Your message dated Fri, 03 Oct 2014 13:19:53 + with message-id and subject line Bug#761522: fixed in sisu-guice 3.2.4-1 has caused the Debian Bug report #761522, regarding sisu-guice: FTBFS: Error(s) found in manifest configuration to be marked as done. This means that you claim that the prob

Bug#761548: marked as done (javamail: FTBFS: Manifest com.sun.mail:javax.mail:jar:1.5.2 : null, for cmd: range, arguments; [range, [==,+)])

Your message dated Fri, 03 Oct 2014 13:04:09 + with message-id and subject line Bug#761548: fixed in javamail 1.5.2-2 has caused the Debian Bug report #761548, regarding javamail: FTBFS: Manifest com.sun.mail:javax.mail:jar:1.5.2 : null, for cmd: range, arguments; [range, [==,+)] to be marked

Bug#763228: cbmc: FTBFS: ld: final link failed: Bad value

This also occurs with arb: https://buildd.debian.org/fetch.cgi?pkg=arb&arch=i386&ver=6.0.2-1&stamp=1412337993&file=log > It seems to be a bug in binutils[1]. I'd say a change in binutils exposed a bug somewhere in the toolchain. Here's the commit which added the check and the message: https://w

Bug#763360: Bug#754988: Bug#763360: libjpeg-turbo is hijacking binaries from other source packages

Hi, looking a bit from the outside it looks to me as different questions discussed in parallel. The one question is how we came here. * Bill Allombert (ballo...@debian.org) [141003 12:15]: > On Fri, Oct 03, 2014 at 01:41:02AM +0200, Emilio Pozuelo Monfort wrote: > > On 30/09/14 11:32, Bill Al

Bug#763873: owncloud-client: Owncloud client Failed to load module "canberra-gtk-module"

> > but it has no icon in Gnomes message area. Looks like it it not compatible > > with Gnome 3.14. > > > > This is #750847, I guess, and it started before Gnome 3.14 ;-) > Yes, that looks like my missing icon bug. But this report is about a missing dependency. The package needs a dependency to

Processed: follow-up for mis-formatted changelog entries...

Processing commands for cont...@bugs.debian.org: > fixed 763710 1:1.26.9-2 Bug #763710 [src:libguestfs] FTBFS on various architectures, test-suite failures Marked as fixed in versions libguestfs/1:1.26.9-2. > fixed 763741 1:1.26.9-2 Bug #763741 [src:libguestfs] libguestfs: Incorrect build-dependen

Bug#761522: Regression caused by maven-bundle-plugin/2.3.7

Thanks Emmanuel, I couldn't get my head around this issue in sisu-guice. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#763873: owncloud-client: Owncloud client Failed to load module "canberra-gtk-module"

Joachim Fahrner writes: > but it has no icon in Gnomes message area. Looks like it it not compatible > with Gnome 3.14. > This is #750847, I guess, and it started before Gnome 3.14 ;-) Just my 2 cents, Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPG

Bug#763587: Still having problems

I'm sorry, but I didn't understand. You say it is already fixed, but I'm still not able to upgrade the system (03-oct-2014). Do we have to wait for the fix to be uploaded to Debian servers?

Bug#763816: libopenscenegraph100: osgDB fails to load any plugin

Hi, in the meantime, it is easier to set OSG_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/ in your environment. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#763134: acpi-support-base: /usr/share/acpi-support/power-funcs broken from line 24 if consolekit installed and no dbus running

On Sun, Sep 28, 2014 at 05:12:45AM +0200, waijb wrote: > just testing if /usr/bin/ck-list-sessions is executable doesn't do the > trick. > until just now i had consolekit installed (some dependency somewhere), but > dbus was (and still is and will be) not running. this leads to an error in > line 2

Processed: libopenscenegraph100: osgDB fails to load any plugin

Processing commands for cont...@bugs.debian.org: > merge 763816 763818 Bug #763816 [libopenscenegraph100] libopenscenegraph100: osgDB fails to load any plugin Bug #763818 [libopenscenegraph100] libopenscenegraph100: Unable to load any model in flightgear Merged 763816 763818 > thanks Stopping pr

Bug#763375: marked as done (openssh is not binNMU safe)

Your message dated Fri, 03 Oct 2014 11:49:02 + with message-id and subject line Bug#763375: fixed in openssh 1:6.6p1-8 has caused the Debian Bug report #763375, regarding openssh is not binNMU safe to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#761522: Regression caused by maven-bundle-plugin/2.3.7

The update of maven-bundle-plugin to the version 2.3.7 has caused build failures on javamail (#761548) and sisu-guice (#761522). After reverting to the version 2.3.5 they both build fine. For javamail, I checked out a clean copy of the upstream source, upgraded maven-bundle-plugin to 2.3.7 in the

Bug#763741: libguestfs: Incorrect build-dependencies (libsystemd-id128-0, libsystemd-journal0), fails binNMU

I'm not complete clear on what change is being made to Debian. However from the build log, the problem is that 'libsystemd.so.0' isn't making it into the appliance. This seems to be because the following upstream commit shoud be backported to the 1.26 branch (either in Debian or upstream): comm

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 742875 libgdk-pixbuf2.0-0 Bug #742875 [hicolor-icon-theme] hicolor-icon-theme: upgrade reports broken installation Bug reassigned from package 'hicolor-icon-theme' to 'libgdk-pixbuf2.0-0'. No longer marked as found in versions hicolor-ic

Bug#763257: marked as done (psensor: FTBFS: app-indicator.h:221:2: error: unknown type name 'GtkStatusIcon')

Your message dated Fri, 03 Oct 2014 10:49:20 + with message-id and subject line Bug#763257: fixed in psensor 1.1.3-1 has caused the Debian Bug report #763257, regarding psensor: FTBFS: app-indicator.h:221:2: error: unknown type name 'GtkStatusIcon' to be marked as done. This means that you c

Bug#763360: Bug#754988: Bug#763360: libjpeg-turbo is hijacking binaries from other source packages

On 03/10/14 12:14, Bill Allombert wrote: On Fri, Oct 03, 2014 at 01:41:02AM +0200, Emilio Pozuelo Monfort wrote: On 30/09/14 11:32, Bill Allombert wrote: On Mon, Sep 29, 2014 at 08:55:16PM +0200, Ondřej Surý wrote: Bill, I am very sorry that I have not Cced everything related to the libjpeg-t

Bug#763873: owncloud-client: Owncloud client Failed to load module "canberra-gtk-module"

Package: owncloud-client Version: 1.7.0~beta1+really1.6.3+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, when starting the owncloud sync client it abort with error message: Gtk-Message: Failed to load module "canberra-gtk-module" A strace shows that it is attemp

Bug#763360: Bug#754988: Bug#763360: libjpeg-turbo is hijacking binaries from other source packages

On Fri, Oct 03, 2014 at 01:41:02AM +0200, Emilio Pozuelo Monfort wrote: > On 30/09/14 11:32, Bill Allombert wrote: > >On Mon, Sep 29, 2014 at 08:55:16PM +0200, Ondřej Surý wrote: > >>Bill, > >> > >>I am very sorry that I have not Cced everything related to the > >>libjpeg-transition > >>to you. I h

Bug#763227: marked as done (libinline-c-perl: FTBFS: Tests failures)

Your message dated Fri, 03 Oct 2014 09:51:25 + with message-id and subject line Bug#763227: fixed in libinline-c-perl 0.64-1 has caused the Debian Bug report #763227, regarding libinline-c-perl: FTBFS: Tests failures to be marked as done. This means that you claim that the problem has been de

Bug#761536: marked as done (lazarus: FTBFS: recipe for target 'install-arch-stamp' failed)

Your message dated Fri, 03 Oct 2014 09:51:10 + with message-id and subject line Bug#761536: fixed in lazarus 1.2.4+dfsg-2 has caused the Debian Bug report #761536, regarding lazarus: FTBFS: recipe for target 'install-arch-stamp' failed to be marked as done. This means that you claim that the

Bug#763264: marked as done (ooniprobe: FTBFS: Tests failures)

Your message dated Fri, 03 Oct 2014 09:23:34 + with message-id and subject line Bug#763264: fixed in ooniprobe 1.2.0-1 has caused the Debian Bug report #763264, regarding ooniprobe: FTBFS: Tests failures to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#763823: marked as done (hwclock-set script should protect against being run twice)

Your message dated Fri, 03 Oct 2014 09:24:40 + with message-id and subject line Bug#763823: fixed in util-linux 2.25.1-2 has caused the Debian Bug report #763823, regarding hwclock-set script should protect against being run twice to be marked as done. This means that you claim that the probl

Bug#756963: marked as done (direnv: FTBFS due to test suite failures)

Your message dated Fri, 03 Oct 2014 09:19:38 + with message-id and subject line Bug#756963: fixed in direnv 2.4.0-2 has caused the Debian Bug report #756963, regarding direnv: FTBFS due to test suite failures to be marked as done. This means that you claim that the problem has been dealt with

Bug#763693: marked as done (dnsmasq: FTBFS[kfreebsd]: missing strlcpy)

Your message dated Fri, 03 Oct 2014 09:19:47 + with message-id and subject line Bug#763693: fixed in dnsmasq 2.72-2 has caused the Debian Bug report #763693, regarding dnsmasq: FTBFS[kfreebsd]: missing strlcpy to be marked as done. This means that you claim that the problem has been dealt wit

Processed: Bug#763605: apt-get removes libjepg-progs and installs libjpeg-turbo-progs

Processing commands for cont...@bugs.debian.org: > retitle 763605 apt-get removes libjepg-progs and installs libjpeg-turbo-progs Bug #763605 [libjpeg-turbo-progs] libjpeg-turbo-progs: Please don't drop libjpeg-progs dummy package Changed Bug title to 'apt-get removes libjepg-progs and installs l

Bug#763855: xchat FTBFS on ppc64el, hurd, kfreebsd

* Andreas Barth (a...@ayous.org) [141003 11:00]: > * Andreas Barth (a...@ayous.org) [141003 10:48]: > > Even though the non-working one is longer, it misses -lm -lgmodule-2.0 > > -ldl. Of those the -lgmodule-2.0 is the relevant one. > > And the reason for that is that > pkg-config --libs "libsexy

Bug#763855: xchat FTBFS on ppc64el, hurd, kfreebsd

* Andreas Barth (a...@ayous.org) [141003 10:48]: > Even though the non-working one is longer, it misses -lm -lgmodule-2.0 > -ldl. Of those the -lgmodule-2.0 is the relevant one. And the reason for that is that pkg-config --libs "libsexy >= 0.1.8" gives different output. Andi -- To UNSUBSCRIB

Processed: reopening 763763

Processing commands for cont...@bugs.debian.org: > reopen 763763 Bug #763763 {Done: Anton Gladky } [src:vtk6] vtk6: FTBFS on arm* 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer ma

Processed: notfixed 763763 in 6.1.0+dfsg2-2

Processing commands for cont...@bugs.debian.org: > notfixed 763763 6.1.0+dfsg2-2 Bug #763763 [src:vtk6] vtk6: FTBFS on arm* Ignoring request to alter fixed versions of bug #763763 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 7

Bug#763855: xchat FTBFS on ppc64el, hurd, kfreebsd

* Andreas Barth (a...@ayous.org) [141003 10:35]: > That seems to come from linktool not using the right DSOs. If I copy > the linking command from the x86-build and do that by hand, I could > continue to build the binary packages. Further investigation shows that replacing GUI_LIBS with the value

Bug#763857: globus-gram-job-manager: FTBFS on several arches

Source: globus-gram-job-manager Version: 14.20-1 Severity: serious Justification: FTBFS Hello, Your package fails to build from source on Debian autobuilder network. Please check your package build logs at:

Bug#763855: xchat FTBFS on ppc64el, hurd, kfreebsd

Package: xchat Version: 2.8.8-7.1 Severity: serious Hi, xchat FTBFS on three different architectures, one of them being a release architecture it built before. The error is the same everywhere: > /usr/bin/ld: plugin-tray.o: undefined reference to symbol 'g_module_symbol' while linking xchat That

Processed: reassign 762186 to src:python-pypdf

Processing commands for cont...@bugs.debian.org: > reassign 762186 src:python-pypdf Bug #762186 [python-pypdf] python-pypdf: Unexpectedly breaks existing programs on update Bug reassigned from package 'python-pypdf' to 'src:python-pypdf'. No longer marked as found in versions pypdf2/1.23-1. Ignor

Processed: reassign 762186 to python-pypdf

Processing commands for cont...@bugs.debian.org: > reassign 762186 python-pypdf Bug #762186 [python-pypdf] python-pypdf: Unexpectedly breaks existing programs on update Ignoring request to reassign bug #762186 to the same package > thanks Stopping processing here. Please contact me if you need a

Processed (with 2 errors): your mail

Processing commands for cont...@bugs.debian.org: > severity 763803 serious Bug #763803 [ettercap-common] ettercap-common: cannot be upgraded because conflicts with same version of ettercap-graphical Severity set to 'serious' from 'normal' > thanks, Unknown command or malformed arguments to comman

Processed: reassign 762186 to python-pypdf

Processing commands for cont...@bugs.debian.org: > reassign 762186 python-pypdf 1.23-1 Bug #762186 [python-pypdf] python-pypdf: Unexpectedly breaks existing programs on update Ignoring request to reassign bug #762186 to the same package Bug #762186 [python-pypdf] python-pypdf: Unexpectedly breaks

Bug#762186: [Python-modules-team] Bug#762186: python-pypdf: Unexpectedly breaks existing programs on update

I believe that to fix this there is still a need for a new upload of python-pypdf (1) with an higher version number (an epoch?). I'm cc-ing the maintainer of python-pypdf, since I'm not sure that the BTS is knowing about the right addresses. It would be nice if this upload added a DeprecationErr

Processed: reopening 762186

Processing commands for cont...@bugs.debian.org: > reopen 762186 Bug #762186 {Done: Laszlo Boszormenyi (GCS) } [python-pypdf] python-pypdf: Unexpectedly breaks existing programs on update 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared,

Processed: tagging 724272

Processing commands for cont...@bugs.debian.org: > tags 724272 + pending Bug #724272 [mailutils-guile] mailutils-guile: update dependency to guile 2.0 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 724272: http://bugs.debian.org/cgi-bin/bugr

Bug#763763: marked as done (vtk6: FTBFS on arm*)

Your message dated Fri, 03 Oct 2014 07:35:20 + with message-id and subject line Bug#763763: fixed in vtk6 6.1.0+dfsg2-2 has caused the Debian Bug report #763763, regarding vtk6: FTBFS on arm* to be marked as done. This means that you claim that the problem has been dealt with. If this is not