Bug#831948: marked as done (ftpwatch: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute)

Your message dated Tue, 02 Aug 2016 05:48:32 + with message-id and subject line Bug#831948: fixed in ftpwatch 1.23 has caused the Debian Bug report #831948, regarding ftpwatch: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no

Bug#833134: marked as done (oolite: freezes at startup)

Your message dated Tue, 02 Aug 2016 04:20:54 + with message-id and subject line Bug#833134: fixed in oolite 1.84-1 has caused the Debian Bug report #833134, regarding oolite: freezes at startup to be marked as done. This means that you claim that the

Bug#831211: ucommon: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

Hi Lucas, Jonas, twinkle has been marked for autoremoval from testing on 2016-08-27 due to this FTBFS. Building ucommon with GCC 6 instead of GCC 5 yields slight differences in the list of visible symbols. How should this bug be dealt with? Is it not simply a matter of waiting for GCC 6 to

Bug#831039: Processed: moreinfo

It seems that it's a libav bug. If started like $ totem --gst-debug=6 the following output is produced: 0:00:05.212869886 17220 0x7fd284013b70 ERROR libav :0:: Invalid chars '.0' at the end of expression '1.0' 0:00:05.212878563 17220 0x7fd284013b70 ERROR libav

Bug#811923: marked as done (blitz++: FTBFS with GCC 6: clumsy program name interferes badly with #include directive)

Your message dated Mon, 01 Aug 2016 23:48:53 + with message-id and subject line Bug#811923: fixed in blitz++ 1:0.10+ds-1 has caused the Debian Bug report #811923, regarding blitz++: FTBFS with GCC 6: clumsy program name interferes badly with #include

Bug#831253: marked as done (memcached: FTBFS: Tests failures)

Your message dated Mon, 01 Aug 2016 23:34:37 + with message-id and subject line Bug#831253: fixed in memcached 1.4.29-1 has caused the Debian Bug report #831253, regarding memcached: FTBFS: Tests failures to be marked as done. This means that you claim

Bug#830438: marked as done (atheme-services: FTBFS: ptasks.c:135:90: error: 'mowgli_eventloop_timer_t {aka struct }' has no member named 'when')

Your message dated Mon, 01 Aug 2016 23:18:46 + with message-id and subject line Bug#830438: fixed in atheme-services 7.2.6-1 has caused the Debian Bug report #830438, regarding atheme-services: FTBFS: ptasks.c:135:90: error: 'mowgli_eventloop_timer_t {aka

Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

On Mon, 1 Aug 2016, Kurt Roeckx wrote: > Can you still reproduce the problem? I see you marked it as RC > now, but the buildds actually build it succesful. I raised to serious because I raised to serious all the bugs that were still open. Sorry if I answer your question by making another one:

Bug#831244: [DRE-maint] Bug#831244: ruby-eventmachine: FTBFS: Build hangs minutes of inactivity

* Antonio Terceiro [160801 15:21]: > On Sun, Jul 31, 2016 at 10:21:39PM +0200, Christian Hofstaedtler wrote: > > * Lucas Nussbaum [160731 20:17]: > > > During a rebuild of all packages in sid, your package failed to build on > > > amd64. > > > > So I tried

Bug#817578: marked as done (members: Removal of debhelper compat 4)

Your message dated Mon, 01 Aug 2016 22:41:00 + with message-id and subject line Bug#817578: fixed in members 20080128-5+nmu1 has caused the Debian Bug report #817578, regarding members: Removal of debhelper compat 4 to be marked as done. This means that

Bug#831182: marked as done (qtcreator: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory)

Your message dated Mon, 01 Aug 2016 22:41:10 + with message-id and subject line Bug#831182: fixed in qbs 1.5.2+dfsg-1 has caused the Debian Bug report #831182, regarding qtcreator: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or

Processed: built later just fine

Processing commands for cont...@bugs.debian.org: > severity 825476 normal Bug #825476 [src:cython] cython: FTBFS with gcc-6 and glibc 2.23: Test failures Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 825476:

Bug#825476: built later just fine

severity 825476 normal thanks 0.23.4+git4-g7eed8d8-2 built just fine in sid a few days back with libc6 2.23: https://buildd.debian.org/status/package.php?p=cython=unstable If fails to build against anything in experimental it must not be of 'serious' (rc) severity since experimental is not

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 830729 0.0~git20160621.0.756f7b1-1 Bug #830729 {Done: Tim Potter } [src:golang-github-mitchellh-go-homedir] golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~" Ignoring request to alter fixed

Processed: Re: Bug#830750: photofloat: traceback on run

Processing control commands: > severity -1 grave Bug #830750 [photofloat] photofloat: traceback on run Severity set to 'grave' from 'normal' -- 830750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#832908: mongodb: CVE-2016-6494: world-readable .dbshell history file: LTS update and upgrade handling

Hi again I just realize that we need to change back the umask after the file is created. I'll update the patch tomorrow and send one that I know works. // Ola On Tue, Aug 2, 2016 at 12:13 AM, Ola Lundqvist wrote: > Hi all > > I have prepared a preliminary patch for wheezy. I

Bug#832908: mongodb: CVE-2016-6494: world-readable .dbshell history file: LTS update and upgrade handling

Hi all I have prepared a preliminary patch for wheezy. I have not yet been able to test it fully (it is building right now). It looks like attached. You may need to modify it for later versions. Please comment. The principles should be ok even if I may have made some stupid copy+paste mistake.

Bug#831095: marked as done (p8-platform: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors)

Your message dated Mon, 01 Aug 2016 22:10:50 + with message-id and subject line Bug#831095: fixed in p8-platform 2.0.1+dfsg1-2 has caused the Debian Bug report #831095, regarding p8-platform: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

Bug#832833: marked as done (libtest-valgrind-perl: FTBFS: Tests failures)

Your message dated Mon, 01 Aug 2016 22:09:18 + with message-id and subject line Bug#832833: fixed in libtest-valgrind-perl 1.19-1 has caused the Debian Bug report #832833, regarding libtest-valgrind-perl: FTBFS: Tests failures to be marked as done. This

Bug#830729: marked as done (golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~")

Your message dated Mon, 01 Aug 2016 22:07:36 + with message-id and subject line Bug#830729: fixed in golang-github-mitchellh-go-homedir 0.0~git20160621.0.756f7b1-1 has caused the Debian Bug report #830729, regarding golang-github-mitchellh-go-homedir:

Processed: Re: FTBFS under Django 1.10

Processing commands for cont...@bugs.debian.org: > severity 828641 serious Bug #828641 [src:celery-haystack] FTBFS under Django 1.10 Severity set to 'serious' from 'important' > severity 828642 serious Bug #828642 [src:django-celery] FTBFS under Django 1.10 Severity set to 'serious' from

Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

On Mon, Jul 25, 2016 at 08:31:02PM +0200, Kurt Roeckx wrote: > On Mon, Jul 25, 2016 at 07:36:55PM +0200, Santiago Vila wrote: > > On Mon, 25 Jul 2016, Kurt Roeckx wrote: > > > > > The error you get is a testsuite failure. It outputs this to > > > stderr: > > > ERROR: ld.so: object

Bug#830729: [pkg-go] Bug#830729: Bug#830729: Bug#830729: golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~"

On 2 Aug 2016, at 4:22 AM, Tianon Gravi wrote: > > On 31 July 2016 at 20:20, Potter, Tim (HPE Linux Support) > wrote: >> Patch attached to fix this, but it's a bit icky (and has been replaced by a >> shell out to call >> getent in a later version. >

Processed: Pending fixes for bugs in the libtest-valgrind-perl package

Processing commands for cont...@bugs.debian.org: > tag 832833 + pending Bug #832833 [src:libtest-valgrind-perl] libtest-valgrind-perl: FTBFS: Tests failures Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 832833:

Bug#832833: libtest-valgrind-perl: FTBFS: Tests failures

On Mon, 01 Aug 2016 18:02:29 -0300, Vincent Pit (VPIT) wrote: > > > > then you might want > > > > to try giving a shot at the changes I pushed at : > > > > http://git.profvince.com/?p=perl/modules/Test-Valgrind.git;a=summary > > > > Ha! I finally found the time to play a bit, and applying

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 830729 0.0~git20160621.0.756f7b1-1 Bug #830729 [src:golang-github-mitchellh-go-homedir] golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~" The source 'golang-github-mitchellh-go-homedir' and version

Bug#832833: Pending fixes for bugs in the libtest-valgrind-perl package

tag 832833 + pending thanks Some bugs in the libtest-valgrind-perl package are closed in revision 48ca6875d27103ecbf1c04743a4d8b8716b46f39 in branch 'master' by gregor herrmann The full diff can be seen at

Bug#827411: piuparts: FTBFS on jessie: 'wheezy' != 'squeeze'

Hi Stefano, On Sat, Jul 30, 2016 at 06:39:28PM -0400, Stefano Rivera wrote: > Suggested solution attached. > Subject: [PATCH] Don't test the current Debian release status > Tracking that is distro-info-data's problem > def testConfStdDistroNames(self): > -

Processed: Raising severities of bugs regarding dpkg-buildpackage -A

Processing commands for cont...@bugs.debian.org: > severity 805943 serious Bug #805943 [src:hocr] hocr: FTBFS when built with dpkg-buildpackage -A (no binary artifacts) Severity set to 'serious' from 'important' > severity 805947 serious Bug #805947 [src:libforms] libforms: FTBFS when built with

Bug#832833: libtest-valgrind-perl: FTBFS: Tests failures

Le 01/08/2016 à 16:18, gregor herrmann a écrit : Control: tag -1 + patch fixed-upstream On Sat, 30 Jul 2016 18:52:19 +0200, gregor herrmann wrote: Can you tell me the output of "valgrind --version" on your system? If, as I suspect, this output now ends with a full stop, Not really: %

Bug#832840: license-reconcile: FTBFS: dh_auto_test: perl Build test --verbose 1 returned exit code 255

On Mon, 01 Aug 2016 22:32:13 +0200, Jonas Smedegaard wrote: > > In general I think that license-reconcile needs an active maintainer, > > in cooperation with the moving underlying parts, or it needs to be > > removed. Doing emergency cleanups on each new failure is not > > sustainable. > >

Bug#832840: license-reconcile: FTBFS: dh_auto_test: perl Build test --verbose 1 returned exit code 255

Quoting gregor herrmann (2016-08-01 20:51:56) > On Fri, 29 Jul 2016 09:54:49 +0200, Lucas Nussbaum wrote: > > > Source: license-reconcile > > Version: 0.11 > > Severity: serious > > Tags: stretch sid > > User: debian...@lists.debian.org > > Usertags: qa-ftbfs-20160728 qa-ftbfs > > Justification:

Processed: bug 833030 is forwarded to https://rt.perl.org/Ticket/Display.html?id=128800

Processing commands for cont...@bugs.debian.org: > forwarded 833030 https://rt.perl.org/Ticket/Display.html?id=128800 Bug #833030 [perl] perl: use base badly/mistakenly broken by CVE-2016-1238 fix Set Bug forwarded-to-address to 'https://rt.perl.org/Ticket/Display.html?id=128800'. > thanks

Processed: Re: Bug#832833: libtest-valgrind-perl: FTBFS: Tests failures

Processing control commands: > tag -1 + patch fixed-upstream Bug #832833 [src:libtest-valgrind-perl] libtest-valgrind-perl: FTBFS: Tests failures Added tag(s) patch and fixed-upstream. -- 832833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832833 Debian Bug Tracking System Contact

Bug#832833: libtest-valgrind-perl: FTBFS: Tests failures

Control: tag -1 + patch fixed-upstream On Sat, 30 Jul 2016 18:52:19 +0200, gregor herrmann wrote: > > Can you tell me the output of "valgrind --version" on your system? > > If, as I suspect, this output now ends with a full stop, > > Not really: > > % valgrind --version > valgrind-3.12.0.SVN

Bug#832656: runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory

> I'm not sure, but did you mean to report this bug against bcron package? > I fail to understand why runit should have such problem Well, it is my bad. runit-2.1.2_4 deserved a transition, but now we have at least following uninstallabe packages: bcron-run twoftpd-run tinydns-run

Bug#831336: marked as done (python-cffi: Versioned Provides not supported by buildds)

Your message dated Mon, 1 Aug 2016 15:07:13 -0400 with message-id <20160801190713.ga26...@smetana.kardiogramm.net> and subject line Re: Bug#831336: python-cffi: Versioned Provides not supported by buildds has caused the Debian Bug report #831336, regarding python-cffi: Versioned Provides not

Processed: Re: runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory

Processing control commands: > reassign -1 bcron Bug #832656 [runit] runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory Bug reassigned from package 'runit' to 'bcron'. No longer marked as found in versions runit/2.1.2-4.

Bug#832656: runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory

control: reassign -1 bcron control: found -1 0.10-3 On Thu, 28 Jul 2016 09:00:11 +0200 Andreas Beckmann wrote: > Package: runit I'm not sure, but did you mean to report this bug against bcron package? I fail to understand why runit should have such problem G. signature.asc

Processed: Re: Bug#832862: libgraph-writer-dsm-perl: FTBFS: Tests failures

Processing control commands: > tag -1 + confirmed Bug #832862 [src:libgraph-writer-dsm-perl] libgraph-writer-dsm-perl: FTBFS: Tests failures Ignoring request to alter tags of bug #832862 to the same tags previously set -- 832862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832862 Debian

Bug#832862: libgraph-writer-dsm-perl: FTBFS: Tests failures

Control: tag -1 + confirmed On Fri, 29 Jul 2016 09:48:20 +0200, Lucas Nussbaum wrote: > Source: libgraph-writer-dsm-perl > Version: 0.006-1 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20160728 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, >

Bug#832840: license-reconcile: FTBFS: dh_auto_test: perl Build test --verbose 1 returned exit code 255

Control: tag -1 + confirmed On Fri, 29 Jul 2016 09:54:49 +0200, Lucas Nussbaum wrote: > Source: license-reconcile > Version: 0.11 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20160728 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During

Processed: Re: Bug#832840: license-reconcile: FTBFS: dh_auto_test: perl Build test --verbose 1 returned exit code 255

Processing control commands: > tag -1 + confirmed Bug #832840 [src:license-reconcile] license-reconcile: FTBFS: dh_auto_test: perl Build test --verbose 1 returned exit code 255 Added tag(s) confirmed. -- 832840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832840 Debian Bug Tracking System

Bug#832599: Fails to start after upgrade

also sprach gregor herrmann [2016-08-01 19:07 +0200]: > https://sources.debian.net/src/isatapd/0.9.7-2/debian/postinst/?hl=12#L12 > > Maybe this is the way to go? > (And if yes: "disable" or "mask"?) I think disable inhibits automatic starts, whereas mask prevents starts

Bug#830729: [pkg-go] Bug#830729: Bug#830729: Bug#830729: golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~"

On 31 July 2016 at 20:20, Potter, Tim (HPE Linux Support) wrote: > Patch attached to fix this, but it's a bit icky (and has been replaced by a > shell out to call > getent in a later version. Very nice catch indeed! Given that the code in question is rewritten in newer

Processed: Re: Merging does not work

Processing commands for cont...@bugs.debian.org: > unarchive 813128 Bug #813128 {Done: Emilio Pozuelo Monfort } [release.debian.org] transition: openmpi Unarchived Bug 813128 > forcemerge 813951 831247 Bug #813951 [src:freefoam] freefoam: FTBFS with libopenmpi 1.10 Bug #831247

Bug#831336: python-cffi: Versioned Provides not supported by buildds

Hi Sebastiaan (2016.08.01_19:06:05_+0200) > Control: tags -1 - moreinfo You didn't actually provide much info, just asked me to talk to other people :) > Try to build the affected packages on the buildds Well that presumably just-works. Because there haven't been any other issues with regular

Bug#785782: marked as done (greeter screen appears without login prompt)

Your message dated Mon, 1 Aug 2016 19:38:54 +0200 with message-id <20160801173854.ga9...@fatal.se> and subject line closing bug report missing feedback regarding gdm missing login prompt has caused the Debian Bug report #785782, regarding greeter screen appears without login prompt to be marked

Bug#789839: marked as done (xemacs21-packages: FTBFS with timeout in sbuild / unwriteable home?)

Your message dated Mon, 01 Aug 2016 17:26:26 + with message-id and subject line Bug#789839: fixed in xemacs21-packages 2009.02.17.dfsg.2-3 has caused the Debian Bug report #789839, regarding xemacs21-packages: FTBFS with timeout in sbuild / unwriteable

Bug#811953: marked as done (python-cffi: FTBFS with GCC 6: left shift of negative value)

Your message dated Mon, 01 Aug 2016 17:24:17 + with message-id and subject line Bug#811953: fixed in python-cffi 1.7.0-1 has caused the Debian Bug report #811953, regarding python-cffi: FTBFS with GCC 6: left shift of negative value to be marked as done.

Bug#828917: marked as done (pysph: FTBFS in testing (other math package is already loaded))

Your message dated Mon, 01 Aug 2016 17:24:10 + with message-id and subject line Bug#828917: fixed in pysph 0~20160514.git91867dc-4 has caused the Debian Bug report #828917, regarding pysph: FTBFS in testing (other math package is already loaded) to be

Bug#831336: python-cffi: Versioned Provides not supported by buildds

Control: tags -1 - moreinfo On 08/01/2016 06:48 PM, Stefano Rivera wrote: > Hi Bas (2016.07.14_14:30:11_-0400) >> The versioned provides in enabled in 1.6.0-1 are preventing the buildds >> from rebuilding vtk6 for the ongoing gdal transition (#830966) > > That transition completed successfully,

Bug#832599: Fails to start after upgrade

On Sun, 31 Jul 2016 02:16:38 +, Chris Knadle wrote: > What I think might be helpful here is the dh-systemd package, > specifically the dh_systemd_enable command: > > Package: dh-systemd > [...] > Description-en: debhelper add-on to handle systemd unit files > dh-systemd provides a debhelper

Processed: Re: Bug#831336: python-cffi: Versioned Provides not supported by buildds

Processing control commands: > tags -1 - moreinfo Bug #831336 [src:python-cffi] python-cffi: Versioned Provides not supported by buildds Removed tag(s) moreinfo. -- 831336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831336 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: reassigning mount nfs-source bug to src:util-linux

Processing commands for cont...@bugs.debian.org: > retitle 788546 mounting as non-root using nfs-source from fstab as argument > fails Bug #788546 [nfs-common] nfs4 mount.nfs does not respect option "user" in fstab in Jessie Bug #788547 [nfs-common] nfs4 mount.nfs does not respect option "user"

Bug#811953: marked as pending

tag 811953 pending thanks Hello, Bug #811953 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/python-cffi.git;a=commitdiff;h=e4f0b1d --- commit

Processed: Bug#811953 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 811953 pending Bug #811953 [python-cffi] python-cffi: FTBFS with GCC 6: left shift of negative value Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 811953:

Bug#831336: python-cffi: Versioned Provides not supported by buildds

Control: tag -1 moreinfo Hi Bas (2016.07.14_14:30:11_-0400) > The versioned provides in enabled in 1.6.0-1 are preventing the buildds > from rebuilding vtk6 for the ongoing gdal transition (#830966) That transition completed successfully, and the bug was closed. Was there really an issue here?

Processed: Re: Bug#831336: python-cffi: Versioned Provides not supported by buildds

Processing control commands: > tag -1 moreinfo Bug #831336 [src:python-cffi] python-cffi: Versioned Provides not supported by buildds Added tag(s) moreinfo. -- 831336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#788546: nfs4 mount.nfs does not respect option "user" in fstab in Jessie

Am 01.08.2016 um 15:33 schrieb Andreas Henriksson: > Hello again Ingo. > > On Mon, Jul 25, 2016 at 10:13:29AM +0200, Ingo wrote: >> Am 24.07.2016 um 22:07 schrieb Andreas Henriksson: >>> >>> Are you sure this is the correct syntax? I would expect that you >>> should specify the mountpoint (target

Bug#832848: marked as done (sphinxcontrib-programoutput: FTBFS: Tests failures)

Your message dated Mon, 01 Aug 2016 16:33:42 + with message-id and subject line Bug#832848: fixed in sphinxcontrib-programoutput 0.8-5 has caused the Debian Bug report #832848, regarding sphinxcontrib-programoutput: FTBFS: Tests failures to be marked as

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 833144 important Bug #833144 [mpich] mpich: MPICH compiled with BCLR causes problems with valgrind Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 833144:

Bug#832541: libarchive: FTBFS on armhf: test_option_newer_than fails

Hello Aaron M. Ucko. On Mon, Aug 01, 2016 at 11:17:20AM -0400, Aaron M. Ucko wrote: > > Closing this bug report now that we have a succesful build. > > Thanks, and sorry for the noise. I'm not a buildd maintainer or > official porter, so I can't directly schedule retries either. Me neither,

Bug#833144: mpich: MPICH compiled with BCLR causes problems with valgrind

severity 833144 important thanks Hi Julian, thanks for bugreport. We will consider to drop blcr-support in Debian-builds. Reducing the bug severity as it does not break valgrind and mpich itself. Best regards Anton 2016-08-01 13:21 GMT+02:00 Julian Andrej : > Package:

Bug#833029: xen-hypervisor-4.6-amd64: Doesn't boot (at all) from GRUB2 (on EFI system)

On zondag 31 juli 2016 03:40:21 CEST you wrote: > expect Xen to work on a SandyBridge system > with EFI in Stretch. That should be a Skylake system. signature.asc Description: This is a digitally signed message part.

Bug#833157: [Debian-olpc-devel] Bug#833157: sugar-base-0.88: don't release with Stretch

Quoting Emilio Pozuelo Monfort (2016-08-01 16:35:54) > We currently have three versions of sugar: sugar-base-0.88, sugar-base > (0.98) and sugar-toolkit-gtk3 (0.106). Given this is the oldest one, > it only has one non-ported rdep (sugar-moon-activity) which seems > unmaintained, I think it is

Bug#832541: libarchive: FTBFS on armhf: test_option_newer_than fails

> Closing this bug report now that we have a succesful build. Thanks, and sorry for the noise. I'm not a buildd maintainer or official porter, so I can't directly schedule retries either. (I just look at build logs and report bugs, focusing primarily on sources corresponding to new binary

Bug#665334: [Pkg-fonts-devel] Bug#665334: non-DFSG postscript embedded in fontforge (currently August 2014)

Daniel Kahn Gillmor writes: > Hi Vasudev-- > > On Sat 2016-07-30 03:17:01 -0400, Vasudev Kamath wrote: > >> Do you still find this problem in latest fontforge in Debian >> experimental?.. I did a quick search in fontforge/othersubrs.c file I >> did not find exact license

Bug#833030:

As a side note, I have started discussing this security problem, exploits, and security measures on my blog. Please note that none of the module changes prevent the most trivial exploits against, for example, prove and you can't fix this in prove without breaking its basic guarantee. Simply put,

Bug#833030:

If the change was not accidental then it was *very poorly* understood. Removing . from @inc entirely would be less painful than expecting developers to figure out this problem in the absence even of rudimentary documentation of the change of behavior. Documentation is authoritative. The module

Bug#833157: sugar-base-0.88: don't release with Stretch

Source: sugar-base-0.88 Version: 0.88.0-4 Severity: serious We currently have three versions of sugar: sugar-base-0.88, sugar-base (0.98) and sugar-toolkit-gtk3 (0.106). Given this is the oldest one, it only has one non-ported rdep (sugar-moon-activity) which seems unmaintained, I think it is

Processed: Bug#832848 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 832848 pending Bug #832848 [src:sphinxcontrib-programoutput] sphinxcontrib-programoutput: FTBFS: Tests failures Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 832848:

Bug#811656: FTBFS with GCC 6: cannot convert x to y

tags 811656 + help severity 811656 important thanks On Tue, 19 Jan 2016, Martin Michlmayr wrote: > This package fails to build with GCC 6. GCC 6 has not been released > yet, but it's expected that GCC 6 will become the default compiler for > stretch. I don't know how to fix this, so I just

Processed: Re: FTBFS with GCC 6: cannot convert x to y

Processing commands for cont...@bugs.debian.org: > tags 811656 + help Bug #811656 [starvoyager] FTBFS with GCC 6: cannot convert x to y Added tag(s) help. > severity 811656 important Bug #811656 [starvoyager] FTBFS with GCC 6: cannot convert x to y Severity set to 'important' from 'serious' >

Bug#832848: marked as pending

tag 832848 pending thanks Hello, Bug #832848 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=openstack/sphinxcontrib-programoutput.git;a=commitdiff;h=1f091b9 --- commit

Bug#788546: nfs4 mount.nfs does not respect option "user" in fstab in Jessie

Hello again Ingo. On Mon, Jul 25, 2016 at 10:13:29AM +0200, Ingo wrote: > Am 24.07.2016 um 22:07 schrieb Andreas Henriksson: > > > > Are you sure this is the correct syntax? I would expect that you > > should specify the mountpoint (target directory) rather than the > > source of the mount. eg.

Bug#832871: texworks-manual: FTBFS: Couldn't find input index file manual nor manual.idx.

Hi, > Yes, HOME points to /sbuild-nonexistent (and that directory doesn't > exist). Umpf, again. Thank. Ok, I will work around that. Norbert -- PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info GPG: 0x860CDC13fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#831244: ruby-eventmachine: FTBFS: Build hangs minutes of inactivity

On Sun, Jul 31, 2016 at 10:21:39PM +0200, Christian Hofstaedtler wrote: > * Lucas Nussbaum [160731 20:17]: > > During a rebuild of all packages in sid, your package failed to build on > > amd64. > > So I tried debugging this a bit; for me the 'TestFileWatch' test > hangs, both

Bug#833091: marked as done (python-ssdeep: Missing dependency on python-cffi)

Your message dated Mon, 01 Aug 2016 12:49:57 + with message-id and subject line Bug#833091: fixed in python-ssdeep 3.1+dfsg-2 has caused the Debian Bug report #833091, regarding python-ssdeep: Missing dependency on python-cffi to be marked as done. This

Bug#832031: mupdf: diff for NMU version 1.9a+ds1-1.1

Control: tags 832031 + patch Control: tags 832031 + pending Dear maintainer, I've prepared an NMU for mupdf (versioned as 1.9a+ds1-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards, Salvatore diff -Nru mupdf-1.9a+ds1/debian/changelog

Processed: mupdf: diff for NMU version 1.9a+ds1-1.1

Processing control commands: > tags 832031 + patch Bug #832031 [src:mupdf] mupdf: CVE-2016-6265: use-after-free Added tag(s) patch. > tags 832031 + pending Bug #832031 [src:mupdf] mupdf: CVE-2016-6265: use-after-free Added tag(s) pending. -- 832031:

Bug#831768: radiotray stops at start a radiostream

Hello Elías, Am Samstag, den 30.07.2016, 11:17 -0500 schrieb  Alejandro: > Hi Jörg, > Could you please provide your libavcodec57 package version? > $ apt-cache policy libavcodec57 libavcodec57:   Installiert:   7:3.1.1-3   Installationskandidat: 7:3.1.1-3   Versionstabelle:  ***

Bug#817424: marked as done (debfoster: Removal of debhelper compat 4)

Your message dated Mon, 01 Aug 2016 12:03:41 + with message-id and subject line Bug#817424: fixed in debfoster 2.7-2.1 has caused the Debian Bug report #817424, regarding debfoster: Removal of debhelper compat 4 to be marked as done. This means that you

Bug#832830: marked as done (python-django-pyscss: FTBFS: Tests failures)

Your message dated Mon, 01 Aug 2016 12:05:43 + with message-id and subject line Bug#832830: fixed in python-django-pyscss 2.0.2-6 has caused the Debian Bug report #832830, regarding python-django-pyscss: FTBFS: Tests failures to be marked as done. This

Bug#833098: python3-qtile: Python3 library depends on Python 2 packages

Hi Debian (2016.07.31_16:21:48_-0400) In fact, qtile also doesn't need to depend on python{3,}-cffi. The way it is using cffi only involves the cffi backend. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 diff -Nru qtile-0.10.6/debian/control qtile-0.10.6/debian/control ---

Bug#789381: libpoe-api-peek-perl: FTBFS with perl 5.22: test failures

On Sat, 30 Jul 2016 14:35:09 +0200 intrigeri wrote: > Hi, > > Prof. Ernesto Hernández-Novich: > > On Sun, 26 Jun 2016 15:27:05 +0200 > > intrigeri wrote: > >> Prof. Ernesto Hernández-Novich wrote (23 May 2016 11:49:55 GMT) : > >> > On Sat, 21 May

Processed: moreinfo

Processing commands for cont...@bugs.debian.org: > tags 831039 + moreinfo Bug #831039 [totem] totem crash on startup, can't start it Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 831039:

Bug#825477: marked as done (libical: FTBFS with gcc-6 and glibc 2.23)

Your message dated Mon, 01 Aug 2016 11:38:47 + with message-id and subject line Bug#825477: fixed in libical 2.0.0-0.5 has caused the Debian Bug report #825477, regarding libical: FTBFS with gcc-6 and glibc 2.23 to be marked as done. This means that you

Bug#832830: marked as pending

tag 832830 pending thanks Hello, Bug #832830 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=openstack/python-django-pyscss.git;a=commitdiff;h=55ebb17 --- commit

Bug#832541: marked as done (libarchive: FTBFS on armhf: test_option_newer_than fails)

Your message dated Mon, 1 Aug 2016 13:32:07 +0200 with message-id <20160801113207.ga7...@fatal.se> and subject line Re: Bug#832541: libarchive: FTBFS on armhf: test_option_newer_than fails has caused the Debian Bug report #832541, regarding libarchive: FTBFS on armhf: test_option_newer_than fails

Processed: Bug#832830 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 832830 pending Bug #832830 [src:python-django-pyscss] python-django-pyscss: FTBFS: Tests failures Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 832830:

Bug#833144: mpich: MPICH compiled with BCLR causes problems with valgrind

Package: mpich Version: 3.2-6build1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, using the mpich package causes problems when used with valgrind, which is described well in [1]. The problem is caused by the compile option # BLCR checkpointing support

Bug#829191: marked as done (python-pydot-ng: FTBFS: pydot_ng/__init__.py:1958: InvocationException)

Your message dated Mon, 01 Aug 2016 10:53:41 + with message-id and subject line Bug#829191: fixed in python-pydot-ng 1.0.0-3 has caused the Debian Bug report #829191, regarding python-pydot-ng: FTBFS: pydot_ng/__init__.py:1958: InvocationException to be

Bug#833030: perl: use base badly/mistakenly broken by CVE-2016-1238 fix

On Sun, Jul 31, 2016 at 05:09:43AM +, Chris Travers wrote: > Package: perl > Version: 5.14.2-21+deb7u4 > Severity: grave > Justification: renders package unusable > use base died complaining that base package was empty > The problem was introduced by the fix noted in the title. The problem

Bug#818331: marked as done (aac-tactics: FTBFS: constructor vcons (in type vT) expects 2 arguments)

Your message dated Mon, 01 Aug 2016 10:52:11 + with message-id and subject line Bug#813459: fixed in aac-tactics 8.5.1-1 has caused the Debian Bug report #813459, regarding aac-tactics: FTBFS: constructor vcons (in type vT) expects 2 arguments to be marked

Bug#813459: marked as done (aac-tactics: FTBFS: Error: The constructor vcons (in type vT) expects 2 arguments.)

Your message dated Mon, 01 Aug 2016 10:52:11 + with message-id and subject line Bug#813459: fixed in aac-tactics 8.5.1-1 has caused the Debian Bug report #813459, regarding aac-tactics: FTBFS: Error: The constructor vcons (in type vT) expects 2 arguments.

Bug#830178: marked as done (mako: FTBFS: ValueError: too many values to unpack)

Your message dated Mon, 01 Aug 2016 10:27:13 + with message-id and subject line Bug#829020: fixed in zzzeeksphinx 1.0.18-2 has caused the Debian Bug report #829020, regarding mako: FTBFS: ValueError: too many values to unpack to be marked as done. This

Bug#829020: marked as done (sqlalchemy: FTBFS in testing (too many values to unpack))

Your message dated Mon, 01 Aug 2016 10:27:13 + with message-id and subject line Bug#829020: fixed in zzzeeksphinx 1.0.18-2 has caused the Debian Bug report #829020, regarding sqlalchemy: FTBFS in testing (too many values to unpack) to be marked as done.

Processed: Bug#829191 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 829191 pending Bug #829191 [src:python-pydot-ng] python-pydot-ng: FTBFS: pydot_ng/__init__.py:1958: InvocationException Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 829191:

Bug#829191: marked as pending

tag 829191 pending thanks Hello, Bug #829191 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=openstack/python-pydot-ng.git;a=commitdiff;h=c6a7745 --- commit

  1   2   >