Bug#746577: closed by Michael Biebl (Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable)

2014-05-05 Thread Michael Stapelberg
Hi Zack, Zack Weinberg writes: > Note that coinstallability is not enough -- the bulletproof procedure > (e.g. "update-init-system") must also be implemented, shipped, and > documented. Your tone is way out of line. Who are you to tell us what we _must_ do? That’s not how it works. Either you do

Bug#737803: chocolate-doom: FTBFS: race during parallel installation

2014-05-05 Thread Andreas Beckmann
On 2014-05-05 10:44, Fabian Greffrath wrote: > Dear Andreas, > > this bug is fixed in GIT since the day you reported it. However, > unfortunately my regular sponsor is short of time and has somwhow thrown > the towel for package uploads in the short term. Since I don't want to > keep this (otherwi

Bug#737803: marked as done (chocolate-doom: FTBFS: race during parallel installation)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Tue, 06 May 2014 06:18:30 + with message-id and subject line Bug#737803: fixed in chocolate-doom 2.0.0-2 has caused the Debian Bug report #737803, regarding chocolate-doom: FTBFS: race during parallel installation to be marked as done. This means that you claim that the pro

Bug#737803: chocolate-doom: FTBFS: race during parallel installation

2014-05-05 Thread Vincent Cheng
On Mon, May 5, 2014 at 1:44 AM, Fabian Greffrath wrote: > Dear Andreas, > > this bug is fixed in GIT since the day you reported it. However, > unfortunately my regular sponsor is short of time and has somwhow thrown > the towel for package uploads in the short term. Since I don't want to > keep th

Bug#746577: closed by Michael Biebl (Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable)

2014-05-05 Thread Martin Pitt
Zack Weinberg [2014-05-05 20:29 -0400]: > I contend that, therefore, "systemd-sysv", "sysvinit-core", *and* > "systemd-shim" (and "upstart" as well) (quotation marks indicate package > names) should *all* be coinstallable; an upgrade from wheezy should > install *both* "systemd-sysv" and "systemd-s

Processed: tiemu: diff for NMU version 3.03-nogdb+dfsg-2.1

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 746086 + patch Bug #746086 [src:tiemu] tiemu: FTBFS: configure: error: Package requirements (ticalcs2 >= 1.0.7) were not met Added tag(s) patch. > tags 746086 + pending Bug #746086 [src:tiemu] tiemu: FTBFS: configure: error: Package requirem

Bug#746086: tiemu: diff for NMU version 3.03-nogdb+dfsg-2.1

2014-05-05 Thread dai
tags 746086 + patch tags 746086 + pending thanks Dear maintainer, I've prepared an NMU for tiemu (versioned as 3.03-nogdb+dfsg-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. -- Regards, dai GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839

Bug#747158: marked as done (gnu-efi: new upstream version breaks compatibility with -nostdinc)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Tue, 06 May 2014 06:17:42 +0200 with message-id <53686266.8090...@progress-technologies.net> and subject line bts has caused the Debian Bug report #747158, regarding gnu-efi: new upstream version breaks compatibility with -nostdinc to be marked as done. This means that you claim

Bug#747158: gnu-efi: new upstream version breaks compatibility with -nostdinc

2014-05-05 Thread Steve Langasek
Package: gnu-efi Version: 3.0v-1 Severity: serious Hi Daniel, Nigel, The new upstream version of gnu-efi, 3.0v, introduced a dependency from efilib.h on efistdarg.h and from there to stdarg.h. This makes gnu-efi incompatible with -nostdinc, which is a typical way to build for EFI (in order to av

Bug#746799: [Pkg-alsa-devel] Bug#746799: alsa-base: Depends: kmod but it is not going to be installed

2014-05-05 Thread Marco d'Itri
On May 05, Elimar Riesebieter wrote: > So yes, why not orphan alsa-base for Jessie? It is useful to have a dummy package around because it can clean up its own config files. Otherwise you risk keeping them around forever (and maybe causing issues with kmod in the future). -- ciao, Marco sig

Bug#746577: closed by Michael Biebl (Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable)

2014-05-05 Thread Zack Weinberg
On 05/05/2014 03:43 PM, Michael Stapelberg wrote: > Hi Zack, > > Fundamentally we agree with you of course. The devil is in the detail, > though: sysvinit-core and systemd are coinstallable, for all the reasons > you explained. > > However, you seem to be using a package which depends on libpam-s

Bug#741576: marked as done (ruby-bdb: FTBFS (on AMD64): Test failures)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Tue, 06 May 2014 00:04:11 + with message-id and subject line Bug#741576: fixed in ruby-bdb 0.6.6-1 has caused the Debian Bug report #741576, regarding ruby-bdb: FTBFS (on AMD64): Test failures to be marked as done. This means that you claim that the problem has been dealt w

Bug#730960: marked as done (ruby-bdb: FTBFS: Hard dependency on ruby1.8)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Tue, 06 May 2014 00:04:11 + with message-id and subject line Bug#730960: fixed in ruby-bdb 0.6.6-1 has caused the Debian Bug report #730960, regarding ruby-bdb: FTBFS: Hard dependency on ruby1.8 to be marked as done. This means that you claim that the problem has been dealt

Bug#747105: policykit-1: depends on systemd

2014-05-05 Thread Laurent Bigonville
Adam Borowski wrote: > Michael Biebl wrote: > > non-sense. > > Per the policy, severity for "breaks unrelated software" is > "critical". Thus, this bug is valid. If you think that systemd is breaking anything on your system please open a bug against systemd package not policykit. > Please expla

Bug#747105: marked as done (policykit-1: depends on systemd)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Tue, 06 May 2014 01:24:00 +0200 with message-id <53681d90.8090...@michaelbiebl.de> and subject line Re: [Pkg-utopia-maintainers] Bug#747105: breaks unrelated packages has caused the Debian Bug report #747105, regarding policykit-1: depends on systemd to be marked as done. This

Processed: breaks unrelated packages

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 747105 Bug #747105 {Done: Michael Biebl } [policykit-1] policykit-1: depends on systemd Bug reopened Ignoring request to alter fixed versions of bug #747105 to the same values previously set > kthxbye Stopping processing here. Please con

Bug#747105: breaks unrelated packages

2014-05-05 Thread Adam Borowski
reopen 747105 kthxbye > non-sense. Per the policy, severity for "breaks unrelated software" is "critical". Thus, this bug is valid. Please explain to me why a wrapper that executes, among others, "pm-suspend" or "halt", would be related to an init system? Especially if those commands (which in

Processed: Re: Re: evolution-data-server: Unable to read any messages

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 746436 important Bug #746436 [evolution-data-server] evolution-data-server: Unable to read any messages Severity set to 'important' from 'grave' > tags 746436 moreinfo unreproducible Bug #746436 [evolution-data-server] evolution-data-ser

Bug#746436: Re: evolution-data-server: Unable to read any messages

2014-05-05 Thread Emilio Pozuelo Monfort
severity 746436 important tags 746436 moreinfo unreproducible thanks Hi, On 02/05/14 17:07, Paul Menzel wrote: > Dear Jordi, > > > thank you for your reply! > > > Am Donnerstag, den 01.05.2014, 15:32 +0200 schrieb Jordi Mallach: > >> On Wed, Apr 30, 2014 at 01:16:44AM +0200, Paul Menzel wrot

Bug#729081: [Pkg-xfce-devel] Bug#729081: Suspend not working when closing lid

2014-05-05 Thread Omen Nemo
> As far as I can tell, you're using systemd. Can you confirm/infirm > systemd is your PID1? Infirm: PID TTY STAT TIME COMMAND 1 ?Ss 0:08 init [2] 2910 ?S 0:01 /lib/systemd/systemd-logind and indeed I have packages sysvinit and sysvinit-core at version 2.88d

Bug#746577: closed by Michael Biebl (Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable)

2014-05-05 Thread Zack Weinberg
On Mon, May 5, 2014 at 5:40 PM, Tollef Fog Heen wrote: > ]] Zack Weinberg >> Fundamentally what I want is a bulletproof procedure for reverting to >> sysvinit in case something goes wrong. > > Sounds like you're arguing that sysvinit-core should no longer ship > /sbin/init, then, so systemd-sysv d

Bug#746577: closed by Michael Biebl (Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable)

2014-05-05 Thread Tollef Fog Heen
]] Zack Weinberg > On 2014-05-03 12:18 PM, Tollef Fog Heen wrote: > > Zack Weinberg wrote: > >> 1) Switching from sysvinit to systemd (and vice versa, if necessary) > >> should be accomplished via a command dedicated to the purpose; it > >> should *not* occur as a side effect of installing, remov

Bug#747004: marked as done (invesalius: FTBFS: make: dh: Command not found)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 21:35:42 + with message-id and subject line Bug#747004: fixed in invesalius 3.0~b5-2 has caused the Debian Bug report #747004, regarding invesalius: FTBFS: make: dh: Command not found to be marked as done. This means that you claim that the problem has been

Processed: block 743449 with 746436

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 743449 with 746436 Bug #743449 [release.debian.org] transition: evolution-data-server 743449 was not blocked by any bugs. 743449 was not blocking any bugs. Added blocking bug(s) of 743449: 746436 > thanks Stopping processing here. Please co

Bug#739053: rpcbind LSB initscript runlevels are incorrect

2014-05-05 Thread Roger Leigh
On Mon, May 05, 2014 at 01:15:48PM -0700, Steve Langasek wrote: > Control: reopen -1 > > Roger, > > > Please could you apply the following patch. We are planning to upgrade > > the version of insserv, and testing shows that the new version breaks > > on the dependencies declared by rpcbind (whic

Processed: chromium: FTBFS on i386 due to 32bit linker

2014-05-05 Thread Debian Bug Tracking System
Processing control commands: > block 746034 by -1 Bug #746034 {Done: Andreas Cadhalpun } [chromium] chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no longer in the testing archive 746034 was not blocked by any bugs. 746034 was not blocking any bugs. Added blocking bug(s) of 746034:

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

2014-05-05 Thread Andreas Cadhalpun
Package: chromium Version: 34.0.1847.132-1 Severity: grave Justification: FTBFS on i386 blocks #746034 Control: block 746034 by -1 Dear maintainer, chromium still fails to build on i386. The tail of the build log is [1]: /usr/bin/ld.gold: warning: hidden symbol 'hb_buffer_create' in out/Release

Bug#747131: mupdf: build-depends on missing libv8-dev on powerpc and s390x

2014-05-05 Thread Ivo De Decker
package: mupdf version: 1.4-1 severity: serious Hi, The latest mupdf upload can't be built on powerpc, s390x, sparc and hurd, as it depends on libv8-dev, which is missing on those architectures (libv8-3.14 doesn't build on any of them). Either the build-dependency should be removed, or the outda

Processed: Re: rpcbind LSB initscript runlevels are incorrect

2014-05-05 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #739053 {Done: Anibal Monsalve Salazar } [rpcbind] rpcbind LSB initscript runlevels are incorrect '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

Processed: Re: rpcbind LSB initscript runlevels are incorrect

2014-05-05 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #746170 [insserv] insserv: Still fails due to rpcbind/nfs Bug 746170 is not marked as done; doing nothing. -- 746170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- T

Bug#739053: rpcbind LSB initscript runlevels are incorrect

2014-05-05 Thread Steve Langasek
Control: reopen -1 Roger, > Please could you apply the following patch. We are planning to upgrade > the version of insserv, and testing shows that the new version breaks > on the dependencies declared by rpcbind (which doesn't match the > dependent nfs-common). This change adjusts the start ru

Processed: Re: rpcbind LSB initscript runlevels are incorrect

2014-05-05 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #739053 [rpcbind] rpcbind LSB initscript runlevels are incorrect Bug 739053 is not marked as done; doing nothing. -- 739053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: unarchiving 739053

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 739053 Bug #739053 {Done: Anibal Monsalve Salazar } [rpcbind] rpcbind LSB initscript runlevels are incorrect Unarchived Bug 739053 > thanks Stopping processing here. Please contact me if you need assistance. -- 739053: http://bugs.deb

Processed: reassign 746314

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # the bugs was in ruby-sass > reassign 746314 ruby-sass Bug #746314 {Done: Jonas Smedegaard } [ruby-compass] ruby-compass: Recent upgrade on jessie branch (either in compass/sass/other ruby module, breaks sass compiler. Bug reassigned from packa

Bug#746577: closed by Michael Biebl (Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable)

2014-05-05 Thread Michael Stapelberg
Hi Zack, Fundamentally we agree with you of course. The devil is in the detail, though: sysvinit-core and systemd are coinstallable, for all the reasons you explained. However, you seem to be using a package which depends on libpam-systemd, which, translated to English, means the package is using

Bug#747105: marked as done (policykit-1: depends on systemd)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 21:23:27 +0200 with message-id <5367e52f.7060...@michaelbiebl.de> and subject line Re: [Pkg-utopia-maintainers] Bug#747105: policykit-1: depends on systemd has caused the Debian Bug report #747105, regarding policykit-1: depends on systemd to be marked as done.

Bug#746330: still cannot install chromium on sid

2014-05-05 Thread 積丹尼 Dan Jacobson
Please be aware that this bug has not been solved still. # apt-cache policy chromium chromium: Installed: 33.0.1750.152-1 Candidate: 34.0.1847.116-1~deb7u1 Version table: 34.0.1847.116-1~deb7u1 0 500 http://ftp.br.debian.org/debian/ unstable/main i386 Packages *** 33.0.1750.152

Bug#746577: closed by Michael Biebl (Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable)

2014-05-05 Thread Zack Weinberg
On 2014-05-03 12:18 PM, Tollef Fog Heen wrote: Zack Weinberg wrote: 1) Switching from sysvinit to systemd (and vice versa, if necessary) should be accomplished via a command dedicated to the purpose; it should *not* occur as a side effect of installing, removing, upgrading, or downgrading any pa

Bug#746624: python-biopython: FTBFS - t_coffee needs HOME or TMP

2014-05-05 Thread Andreas Tille
Hi Aaron, On Mon, May 05, 2014 at 11:54:51AM -0400, Aaron M. Ucko wrote: > Andreas Tille writes: > > > Just for the sake of completeness: It seems that the non-existinsg HOME > > dir. If this exists the test is really quick but with the non-existing > > HOME it took until I killed the process w

Bug#746799: [Pkg-alsa-devel] Bug#746799: alsa-base: Depends: kmod but it is not going to be installed

2014-05-05 Thread Elimar Riesebieter
* Marco d'Itri [2014-05-05 13:57 +0200]: > On May 05, Vincent Lefevre wrote: > > > The last item is confusing: is the goal to uninstall the alsa-base > > package because it is no longer useful with kmod installed (but > > there's no "Replaces:"), or should one wait for an alsa-base update? > Ei

Bug#742391: marked as done (efl: testsuite error on kfreebsd-amd64)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 5 May 2014 19:09:29 +0200 with message-id <20140505170929.ga4...@downhill.g.la> and subject line Re: Bug#742391: efl: testsuite error on kfreebsd-amd64 has caused the Debian Bug report #742391, regarding efl: testsuite error on kfreebsd-amd64 to be marked as done. This mean

Bug#747109: getdp: FTBFS with make 4

2014-05-05 Thread Julien Cristau
Source: getdp Version: 2.4.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) User: sriva...@debian.org Usertags: transition-make-4.0 Tags: patch Hi, your package no longer builds from source due to a bug in debian/rules that gets triggered with m

Processed: your mail

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 731823 -1 Bug #731823 [libvtk-java] major version 51 is newer than 50, the highest major version supported by this compiler. Bug 731823 cloned as bug 747108 > reassign -1 libvtk6-java Bug #747108 [libvtk-java] major version 51 is newer than

Bug#746607: marked as done (jekyll: Needs dependency on ruby-colored)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 16:34:05 + with message-id and subject line Bug#746607: fixed in jekyll 1.5.1+dfsg1-2 has caused the Debian Bug report #746607, regarding jekyll: Needs dependency on ruby-colored to be marked as done. This means that you claim that the problem has been deal

Bug#747105: policykit-1: depends on systemd

2014-05-05 Thread Christoph Anton Mitterer
Package: policykit-1 Version: 0.105-5 Severity: critical Justification: breaks unrelated software Hi. While I'm actualla in favour of systemd, I don't thinkt it's mature enough yet to be used on my servers (and actually I have tons of non-critical bugs on the desktop with it as well). Anyway,

Bug#746624: python-biopython: FTBFS - t_coffee needs HOME or TMP

2014-05-05 Thread Aaron M. Ucko
Andreas Tille writes: > Just for the sake of completeness: It seems that the non-existinsg HOME > dir. If this exists the test is really quick but with the non-existing > HOME it took until I killed the process which was freezing my machine > (featuring 12GB memory). I do wonder what it's doing

Bug#747073: [cups-daemon] Doesn't work with systemd

2014-05-05 Thread Didier 'OdyX' Raboud
Le lundi, 5 mai 2014, 17.43:45 Didier 'OdyX' Raboud a écrit : > Hmm. Can you attach the content of all files and symlinks in > /etc/systemd/system/cups.socket.d ? Please also attach the output of the following command: sudo netstat -lnptu | grep 631 Cheers, OdyX -- To UNSUBSCRIBE, emai

Bug#747073: [cups-daemon] Doesn't work with systemd

2014-05-05 Thread Didier 'OdyX' Raboud
Le lundi, 5 mai 2014, 15.19:30 BogDan Vatra a écrit : > > I expect the cups maintainers are going to need more information > > here. Please look in the journal (or syslog) to see what went > > wrong, and quote it on the bug. Yay, thanks for the initial response. > > Useful commands might include

Bug#745866: marked as done (FileFd::Size failure on all big-endian architectures (patch attached))

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 15:34:33 + with message-id and subject line Bug#745866: fixed in apt 1.0.3 has caused the Debian Bug report #745866, regarding FileFd::Size failure on all big-endian architectures (patch attached) to be marked as done. This means that you claim that the pro

Bug#738438: marked as done (subsurface: FTBFS on !linux)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 13:50:06 + with message-id and subject line Bug#738438: fixed in subsurface 4.0.3-2 has caused the Debian Bug report #738438, regarding subsurface: FTBFS on !linux to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: Reassign

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 746493 libjogl2-java Bug #746493 [scilab] scilab: scilab fails to launch on powerpc Bug reassigned from package 'scilab' to 'libjogl2-java'. No longer marked as found in versions scilab/5.5.0-2. Ignoring request to alter fixed versions of

Bug#747084: must not be in jessie without proper long term support

2014-05-05 Thread Thijs Kinkhorst
Package: moodle Version: 2.6.2-1 Severity: serious At the time of writing this, I am the single active maintainer on the Moodle package in unstable/testing. The time I spend on the package I can spend at work because we're using the package in its current form as it is in unstable. It's however un

Bug#741236: marked as done (lightdm-gtk-greeter: Randomly I cannot log into my systems since the 1.8.2-1 update happened)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 15:27:39 +0200 with message-id <1399296459.10880.2.camel@scapa> and subject line Re: [Pkg-xfce-devel] Bug#741236: can't reproduce it now has caused the Debian Bug report #741236, regarding lightdm-gtk-greeter: Randomly I cannot log into my systems since the 1.8.

Bug#735453: Changes to libsbml

2014-05-05 Thread Andreas Tille
Hi Ivo, please always either keep the bug report we are working on or at least the maintainers list in CC to keep others informed that we are working on the issue. On Mon, May 05, 2014 at 01:07:26PM +0200, Ivo Maintz wrote: > Hi Andreas, > > Andreas Tille schrieb : > > > > > However, I just re

Bug#747073: [cups-daemon] Doesn't work with systemd

2014-05-05 Thread BogDan Vatra
[..] > > I expect the cups maintainers are going to need more information here. > Please look in the journal (or syslog) to see what went wrong, and quote > it on the bug. > > Useful commands might include "journalctl", "less /var/log/syslog", > "journalctl -xn", "systemctl -a status cups.service

Bug#746772: marked as done (dune-grid: FTBFS on mipsel)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 14:15:18 +0200 with message-id <536780d6.5060...@debian.org> and subject line Re: Bug#746772: dune-grid: FTBFS on mipsel has caused the Debian Bug report #746772, regarding dune-grid: FTBFS on mipsel to be marked as done. This means that you claim that the probl

Bug#746799: [Pkg-alsa-devel] Bug#746799: alsa-base: Depends: kmod but it is not going to be installed

2014-05-05 Thread Marco d'Itri
On May 05, Vincent Lefevre wrote: > The last item is confusing: is the goal to uninstall the alsa-base > package because it is no longer useful with kmod installed (but > there's no "Replaces:"), or should one wait for an alsa-base update? Either choice is fine: a dummy alsa-base package will be

Processed: Re: Bug#747073: [cups-daemon] Doesn't work with systemd

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 747073 cups-daemon+systemd: A dependency job for cups.service failed Bug #747073 [cups-daemon] [cups-daemon] Doesn't work with systemd Changed Bug title to 'cups-daemon+systemd: A dependency job for cups.service failed' from '[cups-daemon

Bug#747073: [cups-daemon] Doesn't work with systemd

2014-05-05 Thread Simon McVittie
retitle 747073 cups-daemon+systemd: A dependency job for cups.service failed tags 747073 + moreinfo thanks On Mon, 05 May 2014 at 14:23:32 +0300, BogDan Vatra wrote: > Setting up cups-daemon (1.7.2-3) ... > A dependency job for cups.service failed. See 'journalctl -xn' for details. > invoke-rc.d:

Bug#746772: dune-grid: FTBFS on mipsel

2014-05-05 Thread Ansgar Burchardt
On 05/03/2014 14:11, Ivo De Decker wrote: > The binnmu of dune-grid on mipsel failed twice: > > https://buildd.debian.org/status/logs.php?pkg=dune-grid&arch=mipsel mayer.debian.org has only 1 GB RAM (+ 0.5 GB swap), but is configured to build in parallel with 2 processes. dune-grid however needs

Bug#746799: [Pkg-alsa-devel] Bug#746799: alsa-base: Depends: kmod but it is not going to be installed

2014-05-05 Thread Vincent Lefevre
[Cc Marco d'Itri for explanations] On 2014-05-03 20:27:08 +0200, Elimar Riesebieter wrote: > $ apt-get changelog kmod | head -9 > Get:1 Changelog for kmod > (http://packages.debian.org/changelogs/pool/main/k/kmod/kmod_17-1/changelog) > [4808 B] > kmod (17-1) unstable; urgency=medium > > * New

Bug#747073: [cups-daemon] Doesn't work with systemd

2014-05-05 Thread BogDan Vatra
Package: cups-daemon Version: 1.7.2-3 Severity: grave Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. After this operation, 0

Bug#719943: (no subject)

2014-05-05 Thread Juerg Haefliger
Confirmed the problem running Debian testing (kernel 3.13.10-1 and makedumpfile 1.5.3-1). Installing makedumpfile 1.5.5-2 from unstable fixes the issues. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debia

Bug#735807: marked as done (salome-kernel: FTBFS: FATAL ERROR: some mandatory products are missing)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 10:35:34 + with message-id and subject line Bug#735807: fixed in salome-kernel 6.5.0-8 has caused the Debian Bug report #735807, regarding salome-kernel: FTBFS: FATAL ERROR: some mandatory products are missing to be marked as done. This means that you claim

Bug#737018: marked as done (pypy: Fails to install on i386 without SSE2)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 10:06:37 + with message-id and subject line Bug#737018: fixed in pypy 2.2.1+dfsg-2 has caused the Debian Bug report #737018, regarding pypy: Fails to install on i386 without SSE2 to be marked as done. This means that you claim that the problem has been deal

Bug#746111: marked as done (ruby-rabl-rails: FTBFS: E: ruby1.9.1 is not supported by gem2deb anymore)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 09:39:56 + with message-id and subject line Bug#746111: fixed in ruby-rabl-rails 0.3.4-1 has caused the Debian Bug report #746111, regarding ruby-rabl-rails: FTBFS: E: ruby1.9.1 is not supported by gem2deb anymore to be marked as done. This means that you

Bug#724816: marked as done (xotcl: FTBFS when build with Tcl/Tk 8.6 as a default)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 09:40:21 + with message-id and subject line Bug#724816: fixed in xotcl 1.6.8-1 has caused the Debian Bug report #724816, regarding xotcl: FTBFS when build with Tcl/Tk 8.6 as a default to be marked as done. This means that you claim that the problem has been

Bug#746097: marked as done (gogglesmm: FTBFS: src/GMAudioScrobbler.cpp:34:20: fatal error: gcrypt.h: No such file or directory)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 09:34:39 + with message-id and subject line Bug#746097: fixed in gogglesmm 0.12.7-3 has caused the Debian Bug report #746097, regarding gogglesmm: FTBFS: src/GMAudioScrobbler.cpp:34:20: fatal error: gcrypt.h: No such file or directory to be marked as done.

Processed: severity of 745552 is normal

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 745552 normal Bug #745552 [src:eglibc] libc6: undeclared file conflict between libc6:sparc and libc6-i386:amd64 Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 745

Bug#737803: chocolate-doom: FTBFS: race during parallel installation

2014-05-05 Thread Fabian Greffrath
Dear Andreas, this bug is fixed in GIT since the day you reported it. However, unfortunately my regular sponsor is short of time and has somwhow thrown the towel for package uploads in the short term. Since I don't want to keep this (otherwise perfectly fine) package from testing any longer and si

Bug#746803: marked as done (Device only doing partial scans.)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 14:06:06 +0530 with message-id <53674d76.7040...@gmail.com> and subject line Hardware issue has caused the Debian Bug report #746803, regarding Device only doing partial scans. to be marked as done. This means that you claim that the problem has been dealt with.

Processed (with 3 errors): limit source to eglibc, tagging 746310, tagging 689427, tagging 745552, tagging 747013 ...

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > #eglibc (2.18-6) UNRELEASED; urgency=medium > # > # * patches/any/cvs-make-4.0.diff: patch from upstream to allow GNU Make > #4.0 and greater. Closes: #747013. > # * patches/sparc/cvs-strcmp.diff: patch from upstream to fix a corner case >

Bug#747060: marked as done (Invalid usermod call in postinst)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 5 May 2014 09:54:03 +0200 with message-id <20140505075403.ga2...@blegrez.ba.issia.cnr.it> and subject line fixed has caused the Debian Bug report #747060, regarding Invalid usermod call in postinst to be marked as done. This means that you claim that the problem has been de

Bug#741236: can't reproduce it now

2014-05-05 Thread Vlad Orlov
Hmm, I can't reproduce it anymore with lightdm-gtk-greeter 1.8.4-1 (Testing).

Processed: Re: Bug#746286: libreoffice-writer: stopping gdm, clicking 'cancel', 'cancel' to file recovery resulted in data loss

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 746286 libreoffice Bug #746286 [libreoffice-writer] libreoffice-writer: stopping gdm, clicking 'cancel', 'cancel' to file recovery resulted in data loss Bug reassigned from package 'libreoffice-writer' to 'libreoffice'. No longer marked

Bug#746286: libreoffice-writer: stopping gdm, clicking 'cancel', 'cancel' to file recovery resulted in data loss

2014-05-05 Thread Rene Engelhard
reassign 746286 libreoffice found 746286 1:3.5.4+dfsg2-0+deb7u2 severity 746286 important tag 746286 + moreinfo tag 746286 + unreproducible thanks On Sat, Apr 26, 2014 at 02:58:32AM -0700, Mark Hedges wrote: > Package: libreoffice-writer Probably not, save and recovery is a central component

Bug#746358: Boot hangs if fstab contains NFS entries

2014-05-05 Thread david
A few extra cents worth may help here. 1. I can confirm that the patch given earlier fixes the boot time bug. 2. For a long time I have had a delay, say 30 sec, during startup. Now during that delay the message "Starting a job for LSB: Raising Network Interfaces" appears. (That's not the exact

Bug#747060: Invalid usermod call in postinst

2014-05-05 Thread Andrey Rahmatullin
Package: proftpd-basic Version: 1.3.5~rc4-2 Severity: serious add_sysuser() function in postinst has the following line: usermod --home=/run/proftpd || true The call must contain the username but it doesn't. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy

Bug#747059: FTBFS: missing build-dep on libselinux1-dev

2014-05-05 Thread Michael Tautschnig
Package: hardinfo Version: 0.5.1-1.3 Severity: serious Usertags: goto-cc During a rebuild of all packages in a clean sid chroot (and cowbuilder+pbuilder) the build failed with the following error. [...] gcc -g -fPIC -pipe -Wall -g -o hardinfo -Wl,-export-dynamic hardinfo.o shell.o util.o iconc

Bug#746251: catfish: /usr/bin/catfish fails to run - no such job error

2014-05-05 Thread Jackson Doak
OK. As i think i have said before, i lack the hardware to run a VM for testing, that should be fixed when my new pc gets here and i wont have the issue again. On Mon, May 5, 2014 at 4:57 PM, Vincent Cheng wrote: > On Sun, May 4, 2014 at 11:44 PM, Jackson Doak wrote: > > Please nmu/team-upload

Bug#746251: catfish: /usr/bin/catfish fails to run - no such job error

2014-05-05 Thread Vincent Cheng
On Sun, May 4, 2014 at 11:44 PM, Jackson Doak wrote: > Please nmu/team-upload this. > I have not had access to a linux pc for around a month and won't have one > for a few more weeks. Thanks for the quick reply. > I have forwarded this to the upstream developer so he sees the fix It's irrelevan