Bug#829161: gplots: FTBFS: dh_clean: Please specify the compatibility level in debian/compat

Source: gplots Version: 3.0.1-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, gplots fails to build from source in unstable/amd64: [..]

Bug#825704: swift-im: should it be removed from Debian?

On Thu, Jun 16, 2016 at 09:17:32PM +0100, Kevin Smith wrote: > Thanks very much - I’ve had something I think’s ready to go for a > couple of days (I realised the license wasn’t a blocker), I’d been > trying to hunt Olly out on IRC, now I know why I was failing. Today should have been the day

Bug#827927: marked as done (hime: postinst fails due to "set -e" and "dpkg --compare-versions")

Your message dated Fri, 01 Jul 2016 04:46:01 + with message-id and subject line Bug#827927: fixed in hime 0.9.10+git20150916+dfsg1-7 has caused the Debian Bug report #827927, regarding hime: postinst fails due to "set -e" and "dpkg --compare-versions" to

Bug#812041: thrift-compiler: diff for NMU version 0.9.1-2.1

Control: tags 812041 + patch Control: tags 812041 + pending Dear maintainer, I've prepared an NMU for thrift-compiler (versioned as 0.9.1-2.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer or if you would like me to dcut the upload. Also, I would be

Processed: thrift-compiler: diff for NMU version 0.9.1-2.1

Processing control commands: > tags 812041 + patch Bug #812041 [thrift-compiler] thrift-compiler: FTBFS with GCC 6: operands to ?: have different Added tag(s) patch. > tags 812041 + pending Bug #812041 [thrift-compiler] thrift-compiler: FTBFS with GCC 6: operands to ?: have different Added

Bug#826022: marked as done (Does not work with Django 1.8)

Your message dated Fri, 01 Jul 2016 04:35:42 + with message-id and subject line Bug#826022: fixed in django-tastypie 0.13.3-1 has caused the Debian Bug report #826022, regarding Does not work with Django 1.8 to be marked as done. This means that you claim

Bug#822718: marked as done (flrig: FTBFS with GCC 6: reference to 'ignore' is ambiguous)

Your message dated Fri, 01 Jul 2016 04:36:04 + with message-id and subject line Bug#822718: fixed in flrig 1.3.26-1 has caused the Debian Bug report #822718, regarding flrig: FTBFS with GCC 6: reference to 'ignore' is ambiguous to be marked as done. This

Processed: user debian...@lists.debian.org, usertagging 827927, found 827927 in 0.9.10+git20150916+dfsg1-6 ...

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 827927 piuparts There were no usertags set. Usertags are now: piuparts. > found 827927 0.9.10+git20150916+dfsg1-6 Bug #827927 [hime]

Bug#829152: liblapack3: misses Breaks: liblapack3gf

Package: liblapack3 Version: 3.5.0-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed again some error: octave3.0: error while loading shared libraries: liblapack.so.3gf: cannot open shared object file: No such file or directory

Processed: bug 812264 is forwarded to https://bugzilla.samba.org/show_bug.cgi?id=11750

Processing commands for cont...@bugs.debian.org: > forwarded 812264 https://bugzilla.samba.org/show_bug.cgi?id=11750 Bug #812264 [samba] samba: FTBFS with GCC 6: ctype.h:216: first defined here Set Bug forwarded-to-address to 'https://bugzilla.samba.org/show_bug.cgi?id=11750'. > thanks Stopping

Processed: tagging 812264

Processing commands for cont...@bugs.debian.org: > tags 812264 + confirmed upstream fixed-upstream Bug #812264 [samba] samba: FTBFS with GCC 6: ctype.h:216: first defined here Added tag(s) fixed-upstream, confirmed, and upstream. > thanks Stopping processing here. Please contact me if you need

Processed: minetest-data: fails to upgrade from 'jessie' - trying to overwrite /usr/share/icons/hicolor/scalable/apps/minetest.svg

Processing control commands: > affects -1 + minetest-dbg Bug #829150 [minetest-data] minetest-data: fails to upgrade from 'jessie' - trying to overwrite /usr/share/icons/hicolor/scalable/apps/minetest.svg Added indication that 829150 affects minetest-dbg -- 829150:

Bug#829150: minetest-data: fails to upgrade from 'jessie' - trying to overwrite /usr/share/icons/hicolor/scalable/apps/minetest.svg

Package: minetest-data Version: 0.4.14+repack-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + minetest-dbg Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to

Bug#829149: gcin: fails to upgrade from testing: subprocess installed post-installation script returned error exit status 1

Package: gcin Version: 2.8.4+dfsg1-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'stretch', then the upgrade to 'sid' fails. >From the attached log (scroll to

Bug#829148: alljoyn-gateway-1504: repeated postinst execution creates wrong symlink

Package: alljoyn-gateway-1504 Version: 15.04~git20160606-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus

Processed: Re: hime: postinst fails due to "set -e" and "dpkg --compare-versions"

Processing control commands: > found -1 0.9.10+git20150916+dfsg1-5 Bug #827927 {Done: ChangZhuo Chen (陳昌倬) } [hime] hime: postinst fails due to "set -e" and "dpkg --compare-versions" Marked as found in versions hime/0.9.10+git20150916+dfsg1-5 and reopened. -- 827927:

Bug#827927: hime: postinst fails due to "set -e" and "dpkg --compare-versions"

Package: hime Version: 0.9.10+git20150916+dfsg1-6 Followup-For: Bug #827927 Unfortunately, the bug still exists. Please see my original bug report for the change that needs to be made. I am encountering this bug upgrading from hime:amd64 0.9.10+git20150916+dfsg1-5 to 0.9.10+git20150916+dfsg1-6.

Bug#827927: hime: postinst fails due to "set -e" and "dpkg --compare-versions"

Followup-For: Bug #827927 Control: found -1 0.9.10+git20150916+dfsg1-5 Hi, that postinst script is still broken. You could just try to apt-get install hime apt-get install --reinstall hime in a minimal chroot. You probably wanted to do something like this (untested!):

Processed: tagging 812303, tagging 812289, tagging 812280, tagging 812274, tagging 812272, tagging 812270 ...

Processing commands for cont...@bugs.debian.org: > tags 812303 + sid stretch Bug #812303 [synergy] synergy: FTBFS with GCC 6: test suite segfaults Added tag(s) stretch and sid. > tags 812289 + sid stretch Bug #812289 {Done: Fredrik Hallenberg } [google-mock] google-mock: FTBFS

Processed: tagging 811723, tagging 811719, tagging 811717, found 811707 in 1.03+repack-3, tagging 811702 ...

Processing commands for cont...@bugs.debian.org: > tags 811723 + sid stretch Bug #811723 [fcitx-unikey] fcitx-unikey: FTBFS with GCC 6: narrowing conversion Added tag(s) stretch and sid. > tags 811719 + sid stretch Bug #811719 [fbterm] fbterm: FTBFS with GCC 6: narrowing conversion Added tag(s)

Bug#811886: marked as done (grass: FTBFS with GCC 6: declaration of ... has a different exception specifier)

Your message dated Thu, 30 Jun 2016 23:30:51 + with message-id and subject line Bug#811886: fixed in grass 7.0.4-3 has caused the Debian Bug report #811886, regarding grass: FTBFS with GCC 6: declaration of ... has a different exception specifier to be

Bug#795081: marked as done (Incompatible with subversion 1.9)

Your message dated Thu, 30 Jun 2016 22:37:44 + with message-id and subject line Bug#795081: fixed in svn-all-fast-export 1.0.10+git4158cb06-1 has caused the Debian Bug report #795081, regarding Incompatible with subversion 1.9 to be marked as done. This

Bug#811744: marked as done (libraw: FTBFS with GCC 6: narrowing conversion)

Your message dated Thu, 30 Jun 2016 22:35:53 + with message-id and subject line Bug#811744: fixed in libraw 0.17.2-3 has caused the Debian Bug report #811744, regarding libraw: FTBFS with GCC 6: narrowing conversion to be marked as done. This means that

Bug#811811: marked as done (mriconvert: FTBFS with GCC 6: no match for)

Your message dated Thu, 30 Jun 2016 22:36:08 + with message-id and subject line Bug#811811: fixed in mriconvert 1:2.0.8-4 has caused the Debian Bug report #811811, regarding mriconvert: FTBFS with GCC 6: no match for to be marked as done. This means that

Bug#812284: Workaround for googletest

Dear Maintainer, while the issue in googletest is still open, please consider applying a workaround for this bug. Attached you'll find a proposed patch. I'll upload this soon to a short DELAYED queue, please let me know if you want me to delay this further or cancel the upload. Best, --

Bug#829140: mutter: FTBFS on ILP32 architectures: format '%ld' expects 'long int', but argument 3 has type 'gint64 {aka long long int}'

Control: tags 829140 - patch On Thu, 30 Jun 2016 at 22:55:12 +0100, Simon McVittie wrote: > Since converting to dh, mutter fails to build on what appear to be all > 32-bit architectures. I believe the patch attached to upstream bug > https://bugzilla.gnome.org/show_bug.cgi?id=762407 is the

Processed: Re: Bug#829140: mutter: FTBFS on ILP32 architectures: format '%ld' expects 'long int', but argument 3 has type 'gint64 {aka long long int}'

Processing control commands: > tags 829140 - patch Bug #829140 [src:mutter] mutter: FTBFS on ILP32 architectures: format '%ld' expects 'long int', but argument 3 has type 'gint64 {aka long long int}' Removed tag(s) patch. -- 829140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829140

Processed: tagging 817430, found 817430 in 0.99.36+nmu2

Processing commands for cont...@bugs.debian.org: > tags 817430 = Bug #817430 [src:dh-kpatches] dh-kpatches: Removal of debhelper compat 4 Removed tag(s) stretch and sid. > found 817430 0.99.36+nmu2 Bug #817430 [src:dh-kpatches] dh-kpatches: Removal of debhelper compat 4 Marked as found in

Bug#812016: marked as done (soundmodem: FTBFS with GCC 6: return-statement with a value)

Your message dated Thu, 30 Jun 2016 15:15:03 -0700 with message-id

Bug#829142: debhelper: dh_strip triggers fatal lintian error for packages with multiple hardlinks

Package: debhelper Version: 9.20160618.1 Severity: serious For packages which ship files with multiple hardlinks, dh_strip produces broken -dbgsym packages that trigger the library-in-debug-or-profile-should-not-be-stripped lintian error, which unfortunately leads to auto-rejection by the FTP

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

Am 30.06.2016 um 21:37 schrieb Eric Valette: > On 30/06/2016 21:32, Felipe Sateler wrote: >> On 30 June 2016 at 15:20, Eric Valette wrote: >>> On 30/06/2016 21:18, Martin Pitt wrote: Control: reassing -1 libaudit1 Control: forcemerge 828991 -1 Hello

Bug#829140: mutter: FTBFS on ILP32 architectures: format '%ld' expects 'long int', but argument 3 has type 'gint64 {aka long long int}'

Source: mutter Version: 3.20.3-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Tags: upstream patch Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=762407 Since converting to dh, mutter fails to build on what appear to be all 32-bit

Processed: Re: Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

Processing control commands: > unmerge -1 Bug #829127 [libaudit1] systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr Bug #828991 [libaudit1] libaudit1 gained a dependency against libcap-ng.so.0 which is installed in /usr Bug #829110 [libaudit1] systemd: FTBFS:

Bug#829088: ccache may silently miscompile symlinked source files

Thanks for the bug report. I have reproduced the issue, see the attached script. Yes, to trigger the bug, the source file path must be absolute and CCACHE_BASEDIR must be enabled. The behavior change in question comes from this commit: <

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

Control: unmerge -1 Control: retitle -1 initrd does not mount /usr Control: reassign -1 initramfs-tools Control: tags -1 moreinfo On 30 June 2016 at 16:24, Eric Valette wrote: > On 30/06/2016 22:17, Eric Valette wrote: >> >> On 30/06/2016 22:06, Felipe Sateler wrote: >>

Processed: Re: Bug#829003: wine: FTBFS since unicode 9 update

Processing control commands: > tags -1 + pending Bug #829003 [wine] wine: FTBFS since unicode 9 update Added tag(s) pending. -- 829003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#829003: wine: FTBFS since unicode 9 update

control: tags -1 + pending Fix committed, based on the previously mentioned 2 commits. Some files/contents were moved between Wine 1.8 and 1.9.13 (which carries the Unicode 9.0 changes), which made spotting changes to autogenerated files a bit harder. In the resulting patch there are still some

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

On 30/06/2016 22:17, Eric Valette wrote: On 30/06/2016 22:06, Felipe Sateler wrote: initramfs-tools If you add debug to your kernel command line, you should get a (possibly very verbose) log at /run/initramfs/initramfs.debug. Does it say anything about mounting /usr? Same answer : I cannot

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

On 30 June 2016 at 15:37, Eric Valette wrote: > On 30/06/2016 21:32, Felipe Sateler wrote: >> >> On 30 June 2016 at 15:20, Eric Valette wrote: >>> >>> On 30/06/2016 21:18, Martin Pitt wrote: Control: reassing -1 libaudit1 Control:

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

On Thu, 30 Jun 2016 21:52:09 +0200 Eric Valette wrote: > On 30/06/2016 21:50, Laurent Bigonville wrote: > > On Thu, 30 Jun 2016 21:37:24 +0200 Eric Valette > > wrote: > >> On 30/06/2016 21:32, Felipe Sateler wrote: > >> > On 30 June 2016 at 15:20,

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

On 30/06/2016 21:46, Martin Pitt wrote: Hello Eric, Eric Valette [2016-06-30 21:33 +0200]: I have an initrd on this machine so this is something else OK, I owe you an apology then, sorry. In #771652 you didn't yet, so I just assumed that was still the case. I was lucky to see at the top of

Bug#829131: avro-java: FTBFS: Could not resolve dependencies for project org.apache.avro:avro-compiler:bundle:1.7.7

Source: avro-java Version: 1.7.7-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, avro-java fails to build from source in unstable/amd64:

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

On 30/06/2016 21:50, Laurent Bigonville wrote: On Thu, 30 Jun 2016 21:37:24 +0200 Eric Valette wrote: On 30/06/2016 21:32, Felipe Sateler wrote: > On 30 June 2016 at 15:20, Eric Valette wrote: >> On 30/06/2016 21:18, Martin Pitt wrote: >>> >>>

Bug#805547: marked as done (libhtml-calendarmonth-perl: FTBFS: Failed test '(2010/03 i8n) Spanish Mexico (wb:1) using auto-detect')

Your message dated Thu, 30 Jun 2016 19:49:41 + with message-id and subject line Bug#805547: fixed in libhtml-calendarmonth-perl 2.04-1 has caused the Debian Bug report #805547, regarding libhtml-calendarmonth-perl: FTBFS: Failed test '(2010/03 i8n) Spanish

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

On Thu, 30 Jun 2016 21:37:24 +0200 Eric Valette wrote: > On 30/06/2016 21:32, Felipe Sateler wrote: > > On 30 June 2016 at 15:20, Eric Valette wrote: > >> On 30/06/2016 21:18, Martin Pitt wrote: > >>> > >>> Control: reassing -1 libaudit1 > >>>

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

Hello Eric, Eric Valette [2016-06-30 21:33 +0200]: > > I have an initrd on this machine so this is something else OK, I owe you an apology then, sorry. In #771652 you didn't yet, so I just assumed that was still the case. > I was lucky to see at the top of the screen something about shared

Processed: reassign 829127 to libaudit1, forcibly merging 828991 829127

Processing commands for cont...@bugs.debian.org: > reassign 829127 libaudit1 Bug #829127 [systemd] systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr Bug reassigned from package 'systemd' to 'libaudit1'. No longer marked as found in versions systemd/230-3.

Processed: affects 828991

Processing commands for cont...@bugs.debian.org: > affects 828991 + systemd Bug #828991 [libaudit1] libaudit1 gained a dependency against libcap-ng.so.0 which is installed in /usr Bug #829110 [libaudit1] systemd: FTBFS: FAIL: test-process-util [..] test-calendarspec Added indication that 828991

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

On 30 June 2016 at 15:20, Eric Valette wrote: > On 30/06/2016 21:18, Martin Pitt wrote: >> >> Control: reassing -1 libaudit1 >> Control: forcemerge 828991 -1 >> >> Hello Eric, > > >> This has never been a supported configuration, and just because it >> happend to mostly work

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

On 30/06/2016 21:20, Eric Valette wrote: On 30/06/2016 21:18, Martin Pitt wrote: Control: reassing -1 libaudit1 Control: forcemerge 828991 -1 I martin I have an initrd on this machine so this is something else I was lucky to see at the top of the screen something about shared object,

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

On 30/06/2016 21:18, Martin Pitt wrote: Control: reassing -1 libaudit1 Control: forcemerge 828991 -1 Hello Eric, This has never been a supported configuration, and just because it happend to mostly work once it doesn't mean that it can be guaranteed forever, sorry. I have an initrd on this

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

Control: reassing -1 libaudit1 Control: forcemerge 828991 -1 Hello Eric, Eric Valette [2016-06-30 21:05 +0200]: > Package: systemd > Version: 230-3 > Severity: critical > Justification: breaks the whole system > > Today a system using initrd was unbootable after upgrade because of the very >

Processed (with 2 errors): Re: Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

Processing control commands: > reassing -1 libaudit1 Unknown command or malformed arguments to command. > forcemerge 828991 -1 Bug #828991 [libaudit1] libaudit1 gained a dependency against libcap-ng.so.0 which is installed in /usr Bug #829110 [libaudit1] systemd: FTBFS: FAIL: test-process-util

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

Package: systemd Version: 230-3 Severity: critical Justification: breaks the whole system Today a system using initrd was unbootable after upgrade because of the very same problem of /usr/lib library dependency. Please make a check afetr building the binary so this is automagically detected!

Bug#829126: libcap-ng0: /sbin/init now depend on libcap-ng.so.0 which is in /usr

Package: libcap-ng0 Version: 0.7.7-2 Severity: critical Justification: breaks the whole system I have a system with /usr and / on dfferent filesystem. Yet as I use an initrd it should be transparent but is not. Today upgrade ended up with a crash in /sbin/init as /sbin/init depends on libcap-ng0

Processed: reassign 811920 to src:ompl, fixed 811920 in 1.1.0+ds1-1

Processing commands for cont...@bugs.debian.org: > # get rid of some weird fixed versions > reassign 811920 src:ompl 1.0.0+ds2-1 Bug #811920 {Done: Leopold Palomo-Avellaneda } [ompl] ompl: FTBFS with GCC 6: use of deleted function Bug reassigned from package 'ompl' to

Processed: reassign 811920 to ompl, fixed 811920 in 1.1.0+ds1-1

Processing commands for cont...@bugs.debian.org: > reassign 811920 ompl 1.0.0+ds2-1 Bug #811920 {Done: Leopold Palomo-Avellaneda } [ompl] ompl: FTBFS with GCC 6: use of deleted function Ignoring request to reassign bug #811920 to the same package Bug #811920 {Done: Leopold

Processed: tagging 811591, tagging 811642, tagging 811659, tagging 811733, tagging 811863, tagging 811868 ...

Processing commands for cont...@bugs.debian.org: > tags 811591 + sid stretch Bug #811591 [ifhp] FTBFS with GCC 6: statement indented as if it were guarded by Added tag(s) sid and stretch. > tags 811642 + sid stretch Bug #811642 [fracplanet] FTBFS with GCC 6: cannot convert x to y Added tag(s)

Bug#811750: marked as done (FTBFS with GCC 6: narrowing conversion)

Your message dated Thu, 30 Jun 2016 18:27:37 + with message-id and subject line Bug#811750: fixed in rsbackup 3.1-2 has caused the Debian Bug report #811750, regarding FTBFS with GCC 6: narrowing conversion to be marked as done. This means that you claim

Bug#829124: viva build-depends on libpajeutils-dev which is no longer built

Package: viva Version: 1.1+git20150820.1a3d1f680f-1 Severity: serious Viva build-depends on libpajeutils-dev which is no longer built by source package pajeng.

Bug#817778: info-beamer: nmu 1.0~pre3+dfsg-0.1

Hello James, Am Mittwoch, den 29.06.2016, 02:14 +0100 schrieb James Cowgill: > I have uploaded an NMU to DELAYED/10 to fix the following bugs. > Please tell me if I should cancel / delay it. >  #817778 silkscreen font is not DFSG compliant >  #826288 info-beamer: please use glfw3 Thanks for

Bug#817372: bandwidthcalc: Removal of debhelper compat 4

Hi Niels, On Wed, Mar 09, 2016 at 08:46:10PM +0100, ni...@thykier.net wrote: > The package bandwidthcalc uses debhelper with a compat level of 4, > which is deprecated and scheduled for removal. autoremove of bandwidthcalc is fine. Since I ask for remove before the jessie release (#781926), I

Processed: Fix blocked by sphinx bug

Processing control commands: > block -1 by 829118 Bug #828980 [src:pyx3] pyx3: FTBFS in testing (LaTeX Error: File `iftex.sty' not found) 828980 was not blocked by any bugs. 828980 was not blocking any bugs. Added blocking bug(s) of 828980: 829118 -- 828980:

Processed: Fix blocked by sphinx bug

Processing control commands: > block -1 by 829118 Bug #828981 [src:pyx] pyx: FTBFS in testing (LaTeX Error: File `iftex.sty' not found) 828981 was not blocked by any bugs. 828981 was not blocking any bugs. Added blocking bug(s) of 828981: 829118 -- 828981:

Bug#829052: libneo4j-client8-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/neo4j-client.h

On 2016-06-30 08:09, Chris Leishman wrote: > Hi Andreas, > > If you don't mind, I was hoping for a little direction in resolving this. Let's discuss this within the bug report ... even if it does not fit perfectly. > It seems I've got a mistake in the packaging, whereby the -dev package for >

Bug#812281: marked as done (oce: FTBFS with GCC 6: test suite failures)

Your message dated Thu, 30 Jun 2016 19:05:48 +0200 with message-id

Processed: Not relevant in a newer oce-version

Processing commands for cont...@bugs.debian.org: > fixed 812281 0.17.2-1 Bug #812281 [oce] oce: FTBFS with GCC 6: test suite failures There is no source info for the package 'oce' at version '0.17.2-1' with architecture '' Unable to make a source version for version '0.17.2-1' Marked as fixed in

Bug#828963: marked as done (squirrel3: FTBFS: Makefile:66: recipe for target 'stdlib.pdf' failed)

Your message dated Thu, 30 Jun 2016 16:48:28 + with message-id and subject line Bug#828963: fixed in squirrel3 3.1-3 has caused the Debian Bug report #828963, regarding squirrel3: FTBFS: Makefile:66: recipe for target 'stdlib.pdf' failed to be marked as

Bug#829106: marked as done (sisu-inject: FTBFS: the artifact javax.servlet:servlet-api:jar:debian has not been downloaded)

Your message dated Thu, 30 Jun 2016 16:48:22 + with message-id and subject line Bug#829106: fixed in sisu-inject 0.3.2-2 has caused the Debian Bug report #829106, regarding sisu-inject: FTBFS: the artifact javax.servlet:servlet-api:jar:debian has not been

Bug#811873: marked as done (scidavis: FTBFS with GCC 6: no matching function for call to)

Your message dated Thu, 30 Jun 2016 16:48:10 + with message-id and subject line Bug#811873: fixed in scidavis 1.D9-2 has caused the Debian Bug report #811873, regarding scidavis: FTBFS with GCC 6: no matching function for call to to be marked as done.

Bug#829102: marked as done (modello: FTBFS: the artifact org.jdom:jdom:jar:debian has not been downloaded)

Your message dated Thu, 30 Jun 2016 16:45:47 + with message-id and subject line Bug#829102: fixed in modello 1.8.3-3 has caused the Debian Bug report #829102, regarding modello: FTBFS: the artifact org.jdom:jdom:jar:debian has not been downloaded to be

Bug#811870: marked as done (libmems: FTBFS with GCC 6: no matching function for call to)

Your message dated Thu, 30 Jun 2016 16:44:34 + with message-id and subject line Bug#811870: fixed in libmems 1.6.0+4725-3 has caused the Debian Bug report #811870, regarding libmems: FTBFS with GCC 6: no matching function for call to to be marked as done.

Bug#816571: marked as done (libwx-scintilla-perl: FTBFS with GCC 6: call overloaded is ambiguous)

Your message dated Thu, 30 Jun 2016 16:44:56 + with message-id and subject line Bug#816571: fixed in libwx-scintilla-perl 0.39-3 has caused the Debian Bug report #816571, regarding libwx-scintilla-perl: FTBFS with GCC 6: call overloaded is ambiguous to be

Bug#828107: marked as done (FTBFS on armel (egr_bound isn't zero))

Your message dated Thu, 30 Jun 2016 16:36:06 + with message-id and subject line Bug#828107: fixed in eclib 20160206-2 has caused the Debian Bug report #828107, regarding FTBFS on armel (egr_bound isn't zero) to be marked as done. This means that you claim

Bug#822711: marked as done (chromium-bsu: FTBFS with GCC 6: call of overloaded 'abs(float&)' is ambiguous)

Your message dated Thu, 30 Jun 2016 16:35:50 + with message-id and subject line Bug#822711: fixed in chromium-bsu 0.9.16-1 has caused the Debian Bug report #822711, regarding chromium-bsu: FTBFS with GCC 6: call of overloaded 'abs(float&)' is ambiguous to

Bug#829110: systemd: FTBFS: FAIL: test-process-util [..] test-calendarspec

Control: reassign -1 libaudit1 Control: forcemerge 828991 -1 Hello Chris, Chris Lamb [2016-06-30 16:53 +0100]: > systemd fails to build from source in unstable/amd64: This is known, due to yesterday's libaudit. Merging/linking bugs. Thanks, Martin -- Martin Pitt|

Processed: Re: Bug#829110: systemd: FTBFS: FAIL: test-process-util [..] test-calendarspec

Processing control commands: > reassign -1 libaudit1 Bug #829110 [src:systemd] systemd: FTBFS: FAIL: test-process-util [..] test-calendarspec Bug reassigned from package 'src:systemd' to 'libaudit1'. No longer marked as found in versions systemd/230-4. Ignoring request to alter fixed versions of

Bug#811606: FTBFS with GCC 6: multiple errors

Hi zigo, On 14:13 Thu 30 Jun , Thomas Goirand wrote: > Hi, > > I've been looking into this problem, and the following has to bee added > to the SConstruct file (around line 720) to allow mongodb to build: > > -Wdeprecated-declarations > -Wno-error=misleading-indentation >

Bug#827716: Non-maintainer upload to fix RC bugs

Hi Ondřej, >> I'd be happy to merge other fixes I have made since version 1:5.2.0-1 >> into http://anonscm.debian.org/cgit/collab-maint/tidy-html5.git/ if >> that's OK with you. I've merged a few of my improvements into collab-maint/tidy-html5.git today, and merged back most of your improvements

Bug#829111: spock: FTBFS: exception IOException is never thrown in body of corresponding try statement

Source: spock Version: 0.7-groovy-2.0-2 Severity: serious >From my pbuilder build log: ... dh_auto_build -O--buildsystem=ant ant -Duser.name debian Buildfile: /build/spock-0.7-groovy-2.0/debian/build.xml init: [mkdir] Created dir: /build/spock-0.7-groovy-2.0/dist build.core:

Bug#829103: plexus-compiler: FTBFS: the artifact org.codehaus.plexus:plexus-component-metadata:jar:1.5.5 has not been downloaded

On Thu, Jun 30, 2016 at 8:40 AM, Emmanuel Bourg wrote: > I'm unable to reproduce this error with pbuilder. Are you using locally > rebuilt packages? Yes, this was with locally rebuilt packages - sorry I neglected to check against a vanilla pbuilder chroot, I was assuming all

Bug#829103: plexus-compiler: FTBFS: the artifact org.codehaus.plexus:plexus-component-metadata:jar:1.5.5 has not been downloaded

Le 30/06/2016 à 17:32, Daniel Schepler a écrit : > [ERROR] Plugin org.codehaus.plexus:plexus-component-metadata:1.5.5 or > one of its dependencies could not be resolved: Cannot access central > (https://repo.maven.apache.org/maven2) in offline mode and the > artifact

Bug#829106: sisu-inject: FTBFS: the artifact javax.servlet:servlet-api:jar:debian has not been downloaded

Source: sisu-inject Version: 0.3.2-1 Severity: serious >From my pbuilder build log: ... [INFO] [INFO] Reactor Summary: [INFO] [INFO] Sisu Inject SUCCESS [ 0.002 s] [INFO]

Bug#829105: sisu-guice: FTBFS: the artifact org.apache.ant:ant:jar:debian has not been downloaded

Source: sisu-guice Version: 3.2.6-2 Severity: serious >From my pbuilder build log: ... [INFO] [INFO] Reactor Summary: [INFO] [INFO] Sisu Guice . SUCCESS [ 0.003 s] [INFO] Sisu Guice

Bug#829103: plexus-compiler: FTBFS: the artifact org.codehaus.plexus:plexus-component-metadata:jar:1.5.5 has not been downloaded

Source: plexus-compiler Version: 2.4-3 Severity: serious >From my pbuilder build log: ... [INFO] [INFO] Reactor Summary: [INFO] [INFO] Plexus Compiler FAILURE [ 0.002 s] [INFO] Plexus

Bug#829101: maven-shade-plugin: FTBFS: the artifact org.codehaus.plexus:plexus-component-metadata:jar:1.5.5 has not been downloaded

Source: maven-shade-plugin Version: 2.4.3-1 Severity: serious >From my pbuilder build log: ... [INFO] [INFO] Building Apache Maven Shade Plugin 2.4.3 [INFO]

Processed: Pending fixes for bugs in the libwx-scintilla-perl package

Processing commands for cont...@bugs.debian.org: > tag 816571 + pending Bug #816571 [libwx-scintilla-perl] libwx-scintilla-perl: FTBFS with GCC 6: call overloaded is ambiguous Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 816571:

Processed: limit source to sgt-puzzles, tagging 684193, tagging 811577, tagging 767531, tagging 791982

Processing commands for cont...@bugs.debian.org: > limit source sgt-puzzles Limiting to bugs with field 'source' containing at least one of 'sgt-puzzles' Limit currently set to 'source':'sgt-puzzles' > tags 684193 + pending Bug #684193 [sgt-puzzles] guess command conflicts with nvram-wakeup;

Bug#817531: marked as done (libimage-info-perl: Removal of debhelper compat 4)

Your message dated Thu, 30 Jun 2016 13:53:51 + with message-id and subject line Bug#817531: fixed in libimage-info-perl 1.28-1.2 has caused the Debian Bug report #817531, regarding libimage-info-perl: Removal of debhelper compat 4 to be marked as done.

Bug#812030: marked as done (previsat: FTBFS with GCC 6: needed for in-class initialization)

Your message dated Thu, 30 Jun 2016 13:59:45 + with message-id and subject line Bug#812030: fixed in previsat 3.5.1.7+dfsg1-2 has caused the Debian Bug report #812030, regarding previsat: FTBFS with GCC 6: needed for in-class initialization to be marked as

Bug#817529: marked as done (libimage-base-bundle-perl: Removal of debhelper compat 4)

Your message dated Thu, 30 Jun 2016 13:53:37 + with message-id and subject line Bug#817529: fixed in libimage-base-bundle-perl 1.0.7-3.2 has caused the Debian Bug report #817529, regarding libimage-base-bundle-perl: Removal of debhelper compat 4 to be

Bug#811667: Fix in upstream

could you pick the relevant SVN changes?

Bug#811739: marked as done (adplay: FTBFS with GCC 6: narrowing conversion)

Your message dated Thu, 30 Jun 2016 13:18:50 + with message-id and subject line Bug#811739: fixed in adplay 1.7-2 has caused the Debian Bug report #811739, regarding adplay: FTBFS with GCC 6: narrowing conversion to be marked as done. This means that you

Processed: libqtpas: FTBFS with GCC 6: symbol changes

Processing control commands: > severity -1 important Bug #811965 [libqt4pas] libqt4pas: FTBFS with GCC 6: symbol changes Severity set to 'important' from 'serious' -- 811965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811965 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#811965: libqtpas: FTBFS with GCC 6: symbol changes

Control: severity -1 important Hi! I can only adapt the symbols file correctly if GCC 6 is default, because otherwise this package would likely FTBFS with the current GCC 5 compiler. Therefore adjusting severity to important, and this will get fixed as soon as GCC 6 is the default compiler in

Bug#811675: marked as done (FTBFS with GCC 6: cannot convert x to y)

Your message dated Thu, 30 Jun 2016 12:50:12 + with message-id and subject line Bug#811675: fixed in xdrawchem 2.0-5 has caused the Debian Bug report #811675, regarding FTBFS with GCC 6: cannot convert x to y to be marked as done. This means that you

Bug#828767: marked as done (toxiproxy: FTBFS: B-D favors old mux, logrus packages)

Your message dated Thu, 30 Jun 2016 12:38:30 + with message-id and subject line Bug#828767: fixed in toxiproxy 2.0.0+dfsg1-3 has caused the Debian Bug report #828767, regarding toxiproxy: FTBFS: B-D favors old mux, logrus packages to be marked as done.

Bug#811997: marked as done (aria2: FTBFS with GCC 6: call overloaded is ambiguous)

Your message dated Thu, 30 Jun 2016 12:33:56 + with message-id and subject line Bug#811997: fixed in aria2 1.24.0-1 has caused the Debian Bug report #811997, regarding aria2: FTBFS with GCC 6: call overloaded is ambiguous to be marked as done. This means

Processed: bug 828985 is forwarded to https://github.com/gosimple/slug/issues/8

Processing commands for cont...@bugs.debian.org: > forwarded 828985 https://github.com/gosimple/slug/issues/8 Bug #828985 [src:golang-github-gosimple-slug] golang-github-gosimple-slug: FTBFS: FAIL: TestSubstituteLang (0.00s)slug_test.go:155: 1. Substitute("o a o",

Bug#829088: ccache may silently miscompile symlinked source files

found 829088 3.2.5-1 thanks Version 3.2.5-1 is also affected by this issue. Attached is a log file from that version. Since the path names are rather complicated in the examples: The dir with the symlinked source files is (note the obj in the 3rd component):

  1   2   >