Bug#879988: dijitso: Missing dependency on python-pkg-resources

Source: dijitso Version: 2017.1.0-2 Severity: serious The automatic autopkgtest for dijitso detected a missing dependency. https://ci.debian.net/packages/d/dijitso/unstable/amd64/ Test Case >From a minimal Debian install, run sudo apt install python-dijitso python >>> import dijitso Tr

Bug#876632: marked as done (sdpa FTBFS due to hardcoded (non-multiarch) path for libblas.a)

Your message dated Sat, 28 Oct 2017 00:49:31 + with message-id and subject line Bug#876632: fixed in sdpa 7.3.10+dfsg-2 has caused the Debian Bug report #876632, regarding sdpa FTBFS due to hardcoded (non-multiarch) path for libblas.a to be marked as done. This means that you claim that the p

Bug#879984: libgcrypt20: copyright does not mention OCB patent license

Package: libgcrypt20 Version: 1.7.9-1 Severity: serious libgcrypt implements OCB, which is patented[0]. The author, Phil Rogaway, provides three licenses. * The first license applies to wholly open-source implementations that do not contain any closed-source components. * The second license ap

Bug#878341: marked as done (librem-dev causes FTBFS in baresip: conflicting types for goertzel_*)

Your message dated Fri, 27 Oct 2017 23:48:49 + with message-id and subject line Bug#878341: fixed in baresip 0.5.6-1 has caused the Debian Bug report #878341, regarding librem-dev causes FTBFS in baresip: conflicting types for goertzel_* to be marked as done. This means that you claim that th

Bug#879983: ruby-cairo: Fails to build with cairo 1.15 (test failures)

Source: ruby-cairo Version: 1.15.10-1 Severity: serious ruby-cairo 1.15.10-1 fails to buid from source with cairo 1.15.8 which was recently uploaded to Debian unstable. Here's a patch that fixes one of the two test failures: https://github.com/rcairo/rcairo/commit/d0b125e Here's the other error:

Bug#879071: marked as done (0ad FTBFS with on armhf with gcc 7: error: call of overloaded 'abs(unsigned int)' is ambiguous)

Your message dated Fri, 27 Oct 2017 22:03:59 + with message-id and subject line Bug#879071: fixed in 0ad 0.0.22-2 has caused the Debian Bug report #879071, regarding 0ad FTBFS with on armhf with gcc 7: error: call of overloaded 'abs(unsigned int)' is ambiguous to be marked as done. This mean

Bug#879980: antlr: FTBFS: dh: unable to load addon maven-repo-helper

Source: antlr Version: 2.7.7+dfsg-9 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of antlr in minimal environments geared for building only its architecture-dependent binary packages (as on the autobuilders) have started failing with errors

Bug#879910: marked as done (lxqt-panel: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-panel.desktop)

Your message dated Fri, 27 Oct 2017 21:49:32 + with message-id and subject line Bug#879910: fixed in lxqt-panel 0.12.0-2 has caused the Debian Bug report #879910, regarding lxqt-panel: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-panel.desktop to be marked as done

Bug#879912: marked as done (lxqt-runner: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-runner.desktop)

Your message dated Fri, 27 Oct 2017 21:26:30 + with message-id and subject line Bug#879912: fixed in lxqt-runner 0.12.0-2 has caused the Debian Bug report #879912, regarding lxqt-runner: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-runner.desktop to be marked as d

Bug#879911: marked as done (lxqt-powermanagement: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-powermanagement.desktop)

Your message dated Fri, 27 Oct 2017 21:26:23 + with message-id and subject line Bug#879911: fixed in lxqt-powermanagement 0.12.0-2 has caused the Debian Bug report #879911, regarding lxqt-powermanagement: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-powermanagemen

Bug#879976: meson: 0.43.0-1 fails to build, test failures

On Fri, Oct 27, 2017 at 5:18 PM, Jussi Pakkanen wrote: > We can bump the version requirement of GDC tests to be >= 8. This is > would be equivalent to what we had before. We're going to have a point > release soon so this could go in that. Ok, well feel free to demote this bug to Important if you

Bug#879976: meson: 0.43.0-1 fails to build, test failures

On Sat, Oct 28, 2017 at 12:08 AM, Jeremy Bicha wrote: >> I think this is because pitti's sbuilder had an issue and it crashed >> the test runner when trying to determine the number of CPUs in the >> system. IIRC the same issue was in reproducible build environment ages >> ago. Under pbuilder the

Bug#879976: meson: 0.43.0-1 fails to build, test failures

On Fri, Oct 27, 2017 at 5:02 PM, Jussi Pakkanen wrote: > On Fri, Oct 27, 2017 at 11:37 PM, Jeremy Bicha wrote: >> meson 0.43.0-1 fails to build from source in Ubuntu and with Debian >> Reproducible Builds >> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/meson.html >> >> https

Bug#879976: meson: 0.43.0-1 fails to build, test failures

On Fri, Oct 27, 2017 at 11:37 PM, Jeremy Bicha wrote: > meson 0.43.0-1 fails to build from source in Ubuntu and with Debian > Reproducible Builds > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/meson.html > > https://launchpad.net/ubuntu/+source/meson/0.43.0-1/+build/13633070

Bug#879976: meson: 0.43.0-1 fails to build, test failures

Source: meson Version: 0.43.0-1 Severity: serious X-Debbugs-CC: mp...@debian.org meson 0.43.0-1 fails to build from source in Ubuntu and with Debian Reproducible Builds https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/meson.html https://launchpad.net/ubuntu/+source/meson/0.43.0-

Bug#879662:

Hello, TL:DR ; nanosleep. I've upgraded to apt 1.6~alpha2 (amd64)and I'm now getting the following error message. [21:02] ~ $ sudo apt-get update [sudo] Mot de passe de nicodache : Réception de:1 http://ftp.belnet.be/debian sid InRelease [235 kB] 0% [1 InRelease 2.679 B/235 kB 1%] [Connexion à

Bug#879880: marked as done (flightgear: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/man/man1/metar.1.gz)

Your message dated Fri, 27 Oct 2017 19:34:47 + with message-id and subject line Bug#879880: fixed in flightgear 1:2017.3.1+dfsg-3 has caused the Debian Bug report #879880, regarding flightgear: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/man/man1/metar.1.gz to be

Bug#879974: llvm-defaults: drop libllvm-ocaml-dev (temporarily)

Source: llvm-defaults Version: 0.36 Severity: serious Tags: sid buster With libllvm-3.8-ocaml-dev (temporarily) gone, libllvm-ocaml-dev needs to be removed as well (or needs to drop the dependency on libllvm-3.8-ocaml-dev temporarily) to allow the migration of llvm-3.8 (and ocaml) to testing. And

Processed: Re: Bug#879800: ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)

Processing commands for cont...@bugs.debian.org: > forwarded 879800 https://trac.ffmpeg.org/ticket/6766 Bug #879800 [ffmpeg] ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i) Set Bug forwarded-to-address to 'https://trac.ffmpeg.org/ticket/6766'. > tags 879800 fixed-upstream Bug #879800 [ffmpeg]

Bug#863788: oolite: Please drop dependency against mozjs 1.8.5

forwarded -1 https://github.com/OoliteProject/oolite/issues/271

Bug#879637: mariadb-10.1: FTBFS on mips64el due to test failures

Hi, On 23/10/17 19:48, Bas Couwenberg wrote: > Source: mariadb-10.1 > Version: 10.1.28-1 > Severity: serious > Justification: makes the package in question unusable or mostly so > Control: affects -1 src:gdal > > Dear Maintainer, > > mariadb-10.1 (10.1.28-1) FTBFS on mips64el, and the missing bi

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 846950 grave Bug #846950 [nfs-common] nfs-common: RPCGSSDOPTS not replicated to /run/sysconfig/nfs-utils Bug #849608 [nfs-common] nfs-common: For rpc.gssd, keytab location is hardcoded to /etc/krb5.keytab Severity set to 'grave' from 'n

Processed: Seems RC to me

Processing commands for cont...@bugs.debian.org: > severity 879961 serious Bug #879961 [disc-cover] disc-cover: Running disc-cover returns a Perl error message: Can't use 'defined(@array)' ... Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you

Bug#877939: marked as done (FTBFS: t/06-sru.t)

Your message dated Fri, 27 Oct 2017 18:04:07 + with message-id and subject line Bug#877939: fixed in libcatmandu-mab2-perl 0.21-1 has caused the Debian Bug report #877939, regarding FTBFS: t/06-sru.t to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: python3-trollius has been removed

Processing commands for cont...@bugs.debian.org: > severity 868203 serious Bug #868203 [src:python-autobahn] drop depends on python3-trollius Severity set to 'serious' from 'normal' > tags 868203 buster sid experimental Bug #868203 [src:python-autobahn] drop depends on python3-trollius Added tag(s

Processed: user debian...@lists.debian.org, usertagging 878469, affects 878469, usertagging 876608 ...

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 878469 piuparts There were no usertags set. Usertags are now: piuparts. > affects 878469 + libjs-of-ocaml Bug #878469 [src:js-of-ocaml] js

Bug#879815: marked as done (eclipse-titan not installable on current stretch/amd64)

Your message dated Fri, 27 Oct 2017 19:09:27 +0200 with message-id <27cedce8-70e6-1550-e51d-3c6b05cba...@debian.org> and subject line Re: Bug#879815: Acknowledgement (eclipse-titan not installable on current stretch/amd64) has caused the Debian Bug report #879815, regarding eclipse-titan not insta

Bug#879821: libgles1-glvnd-nvidia:amd64: upgrade failure to 375.82-6

On Thu, 2017-10-26 at 23:37 +0200, Andreas Beckmann wrote: > On 10/26/2017 11:13 PM, Rafał Olejnik wrote: > > Guess having amd64 and i386 might be a reason because on my sid i'm > > getting same error. > > having both :amd64 and :i386 packages installed does not seem to work > properly with versio

Bug#879951: marked as done (gpsd-clients,gpsd: both ship /usr/share/man/man8/ppscheck.8.gz)

Your message dated Fri, 27 Oct 2017 16:03:54 + with message-id and subject line Bug#879951: fixed in gpsd 3.17-3 has caused the Debian Bug report #879951, regarding gpsd-clients,gpsd: both ship /usr/share/man/man8/ppscheck.8.gz to be marked as done. This means that you claim that the problem

Processed: Re: Bug#879941: awesome: FTBFS on s390x: 7 tests fail, all in color_spec.lua

Processing control commands: > forwarded -1 https://github.com/awesomeWM/awesome/issues/2086 Bug #879941 [src:awesome] awesome: FTBFS on s390x: 7 tests fail, all in color_spec.lua Set Bug forwarded-to-address to 'https://github.com/awesomeWM/awesome/issues/2086'. -- 879941: https://bugs.debian

Bug#879941: awesome: FTBFS on s390x: 7 tests fail, all in color_spec.lua

Control: forwarded -1 https://github.com/awesomeWM/awesome/issues/2086 On Fri, Oct 27, 2017 at 09:31:00AM -0400, Aaron M. Ucko wrote: > The latest build of awesome for s390x failed with seven unit test > errors, all in color_spec.lua, per the below excerpt from > https://buildd.debian.org/status/f

Processed: found 879521 in 0.8.17-1

Processing commands for cont...@bugs.debian.org: > found 879521 0.8.17-1 Bug #879521 [src:irssi] irssi: multiple vulnerabilities fixed in irssi 1.0.5 Marked as found in versions irssi/0.8.17-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 879521: https://bugs.d

Processed: tagging 879521

Processing commands for cont...@bugs.debian.org: > tags 879521 + upstream fixed-upstream Bug #879521 [src:irssi] irssi: multiple vulnerabilities fixed in irssi 1.0.5 Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 879521:

Processed: found 879521 in 1.0.4-1

Processing commands for cont...@bugs.debian.org: > found 879521 1.0.4-1 Bug #879521 [src:irssi] irssi: multiple vulnerabilities fixed in irssi 1.0.5 Marked as found in versions irssi/1.0.4-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 879521: https://bugs.deb

Bug#867725: found 867725 in 3.99.5+repack1-7, closing 867725

found 867725 3.99.5+repack1-7 # Cf. notes in security-tracker for information about why marked as # fixed in 3.99.5+repack1-8 close 867725 3.99.5+repack1-8 thanks

Processed: found 867725 in 3.99.5+repack1-7, closing 867725

Processing commands for cont...@bugs.debian.org: > found 867725 3.99.5+repack1-7 Bug #867725 [src:lame] CVE-2017-9869 CVE-2017-9870 CVE-2017-9871 CVE-2017-9872 Marked as found in versions lame/3.99.5+repack1-7. > # Cf. notes in security-tracker for information about why marked as > # fixed in 3.99

Bug#871138: marked as done (vcdimager: FTBFS: iso9660.h:277:45: error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s')

Your message dated Fri, 27 Oct 2017 15:00:20 + with message-id and subject line Bug#841556: fixed in libcdio 0.94-0.2 has caused the Debian Bug report #841556, regarding vcdimager: FTBFS: iso9660.h:277:45: error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pv

Bug#871121: marked as done (mpd: FTBFS: iso9660.h:277:45: error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s')

Your message dated Fri, 27 Oct 2017 15:00:20 + with message-id and subject line Bug#841556: fixed in libcdio 0.94-0.2 has caused the Debian Bug report #841556, regarding mpd: FTBFS: iso9660.h:277:45: error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s' t

Bug#853484: marked as done (libcdio: ftbfs with GCC-7)

Your message dated Fri, 27 Oct 2017 15:00:20 + with message-id and subject line Bug#841556: fixed in libcdio 0.94-0.2 has caused the Debian Bug report #841556, regarding libcdio: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#853561: marked as done (libcdio: ftbfs with GCC-7)

Your message dated Fri, 27 Oct 2017 15:00:20 + with message-id and subject line Bug#841556: fixed in libcdio 0.94-0.2 has caused the Debian Bug report #841556, regarding libcdio: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#841556: marked as done (libcdio: ftbfs with GCC-7)

Your message dated Fri, 27 Oct 2017 15:00:20 + with message-id and subject line Bug#841556: fixed in libcdio 0.94-0.2 has caused the Debian Bug report #841556, regarding libcdio: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#841624: marked as done (libcdio: ftbfs with GCC-7)

Your message dated Fri, 27 Oct 2017 15:00:20 + with message-id and subject line Bug#841556: fixed in libcdio 0.94-0.2 has caused the Debian Bug report #841556, regarding libcdio: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#853697: marked as done (vcdimager: ftbfs with GCC-7)

Your message dated Fri, 27 Oct 2017 15:00:20 + with message-id and subject line Bug#841556: fixed in libcdio 0.94-0.2 has caused the Debian Bug report #841556, regarding vcdimager: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#853561: marked as done (libcdio: ftbfs with GCC-7)

Your message dated Fri, 27 Oct 2017 15:00:18 + with message-id and subject line Bug#841556: fixed in libcdio 0.94-0.1 has caused the Debian Bug report #841556, regarding libcdio: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#871121: marked as done (mpd: FTBFS: iso9660.h:277:45: error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s')

Your message dated Fri, 27 Oct 2017 15:00:18 + with message-id and subject line Bug#841556: fixed in libcdio 0.94-0.1 has caused the Debian Bug report #841556, regarding mpd: FTBFS: iso9660.h:277:45: error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s' t

Bug#871138: marked as done (vcdimager: FTBFS: iso9660.h:277:45: error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s')

Your message dated Fri, 27 Oct 2017 15:00:18 + with message-id and subject line Bug#841556: fixed in libcdio 0.94-0.1 has caused the Debian Bug report #841556, regarding vcdimager: FTBFS: iso9660.h:277:45: error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pv

Bug#853697: marked as done (vcdimager: ftbfs with GCC-7)

Your message dated Fri, 27 Oct 2017 15:00:18 + with message-id and subject line Bug#841556: fixed in libcdio 0.94-0.1 has caused the Debian Bug report #841556, regarding vcdimager: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#841556: marked as done (libcdio: ftbfs with GCC-7)

Your message dated Fri, 27 Oct 2017 15:00:18 + with message-id and subject line Bug#841556: fixed in libcdio 0.94-0.1 has caused the Debian Bug report #841556, regarding libcdio: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#853484: marked as done (libcdio: ftbfs with GCC-7)

Your message dated Fri, 27 Oct 2017 15:00:18 + with message-id and subject line Bug#841556: fixed in libcdio 0.94-0.1 has caused the Debian Bug report #841556, regarding libcdio: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#841624: marked as done (libcdio: ftbfs with GCC-7)

Your message dated Fri, 27 Oct 2017 15:00:18 + with message-id and subject line Bug#841556: fixed in libcdio 0.94-0.1 has caused the Debian Bug report #841556, regarding libcdio: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#879952: qt3d5-dev-tools: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/qt5/bin/qgltf

Package: qt3d5-dev-tools Version: 5.9.2+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite

Bug#878834: marked as done (freetype: Upgrade to 2.8.1 breaks font rendering in various applications)

Your message dated Fri, 27 Oct 2017 16:34:56 +0200 with message-id and subject line Re: freetype: Upgrade to 2.8.1 breaks font rendering in various applications has caused the Debian Bug report #878834, regarding freetype: Upgrade to 2.8.1 breaks font rendering in various applications to be mark

Bug#878870: marked as done (freetype 2.8.1 breaks font rendering)

Your message dated Fri, 27 Oct 2017 16:34:56 +0200 with message-id and subject line Re: freetype: Upgrade to 2.8.1 breaks font rendering in various applications has caused the Debian Bug report #878834, regarding freetype 2.8.1 breaks font rendering to be marked as done. This means that you clai

Bug#879951: gpsd-clients,gpsd: both ship /usr/share/man/man8/ppscheck.8.gz

Package: gpsd-clients,gpsd Version: 3.17-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selec

Bug#878929: marked as done (libfreetype6: font rendering broken in electron applications)

Your message dated Fri, 27 Oct 2017 16:34:56 +0200 with message-id and subject line Re: freetype: Upgrade to 2.8.1 breaks font rendering in various applications has caused the Debian Bug report #878834, regarding libfreetype6: font rendering broken in electron applications to be marked as done.

Bug#879922: pandoc: B-D: libghc-syb-dev (< 0.7) but 0.7-1 is to be installed

Quoting Andreas Beckmann (2017-10-27 16:03:09) > On 10/27/2017 03:03 PM, Jonas Smedegaard wrote: >> Quoting Andreas Beckmann (2017-10-27 11:23:12) >>> pandoc cannot be built in sid any more since libghc-syb-dev was >>> updated. >> >> No longer the case with new release of Pandoc. >> >> Not really

Processed: Re: Bug#879922: pandoc: B-D: libghc-syb-dev (< 0.7) but 0.7-1 is to be installed

Processing control commands: > fixed -1 1.19.2.4~dfsg-1 Bug #879922 {Done: Jonas Smedegaard } [src:pandoc] pandoc: B-D: libghc-syb-dev (< 0.7) but 0.7-1 is to be installed Marked as fixed in versions pandoc/1.19.2.4~dfsg-1. -- 879922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879922 Deb

Bug#879922: pandoc: B-D: libghc-syb-dev (< 0.7) but 0.7-1 is to be installed

Control: fixed -1 1.19.2.4~dfsg-1 On 10/27/2017 03:03 PM, Jonas Smedegaard wrote: > Quoting Andreas Beckmann (2017-10-27 11:23:12) >> pandoc cannot be built in sid any more since libghc-syb-dev was updated. > > No longer the case with new release of Pandoc. > > Not really caused by pandoc, howev

Bug#879800: ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)

Package: ffmpeg Version: 7:3.4-1 Followup-For: Bug #879800 Dear Maintainer, I just wanted to confirm that applying the patch you proposed fixes the problem for me. Also I enabled v4l2, since the ffmpeg/kodi is making use of v4l2 to decode video streams. I have not tested the LD_PRELOAD option

Bug#879886: libhts2: libhts2 needs to handle ABI changes

On Fri, Oct 27, 2017 at 12:52:31AM -0400, Afif Elghraoui wrote: > We've been doing this for every htslib suite release and can confirm > upstream's explanation. It seems to me the most "interesting" argument in #822701#26 is this: | What's described in that thread is undocumented internal priv

Bug#879798: marked as done (FTBFS: testsuite fails with dpkg 1.19, patch attached)

Your message dated Fri, 27 Oct 2017 13:48:48 + with message-id and subject line Bug#879798: fixed in devscripts 2.17.11 has caused the Debian Bug report #879798, regarding FTBFS: testsuite fails with dpkg 1.19, patch attached to be marked as done. This means that you claim that the problem ha

Bug#879940: virtualbox-dkms: Fail to build

Package: virtualbox-dkms Version: 5.2.0-dfsg-1 Severity: serious Dear Maintainer, >From /var/lib/dkms/virtualbox/5.2.0/build/make.log /var/lib/dkms/virtualbox/5.2.0/build/vboxpci/linux/VBoxPci-linux.c:35:10: fatal error: VBoxPciInternal.h: No such file or directory #include "VBoxPciInternal.h"

Bug#879941: awesome: FTBFS on s390x: 7 tests fail, all in color_spec.lua

Source: awesome Version: 4.2-2 Severity: serious Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-s...@lists.debian.org The latest build of awesome for s390x failed with seven unit test errors, all in color_spec.lua, per the below excerpt f

Bug#879922: marked as done (pandoc: B-D: libghc-syb-dev (< 0.7) but 0.7-1 is to be installed)

Your message dated Fri, 27 Oct 2017 15:03:47 +0200 with message-id <150910942700.29663.15989256165967632...@auryn.jones.dk> and subject line Re: Bug#879922: pandoc: B-D: libghc-syb-dev (< 0.7) but 0.7-1 is to be installed has caused the Debian Bug report #879922, regarding pandoc: B-D: libghc-syb-

Bug#871095: Close bug?

Hi, since the new version obviously builds on amd64, may this bug be closed? Cheers Ole

Bug#878411: gnome-session-bin doesn't set environmental variable of GTK_IM_MODULE

> It's unclear from your bug report whether this was working before for > you ("I can not anymore Japanes language anymore"). > Are you saying that with older gnome-session-bin versions it worked? > No. I'm saying With current GNOME Desktop, wayland(currently default in Debian sid) and curr

Bug#879821: libgles1-glvnd-nvidia:amd64: upgrade failure to 375.82-6

Control: retitle -1 libgles1-glvnd-nvidia, libgles-nvidia1: upgrade failure to 375.82-6 with both :amd64 and :i386 packages installed On 2017-10-26 23:37:18 +0200, Andreas Beckmann wrote: > On 10/26/2017 11:13 PM, Rafał Olejnik wrote: > > Guess having amd64 and i386 might be a reason because on m

Processed: Re: Bug#879821: libgles1-glvnd-nvidia:amd64: upgrade failure to 375.82-6

Processing control commands: > retitle -1 libgles1-glvnd-nvidia, libgles-nvidia1: upgrade failure to > 375.82-6 with both :amd64 and :i386 packages installed Bug #879821 [libgles1-glvnd-nvidia] libgles1-glvnd-nvidia, libgles-nvidia1: upgrade failure to 375.82-6 Changed Bug title to 'libgles1-glv

Bug#875706: marked as done (edbrowse: please package new upstream version)

Your message dated Fri, 27 Oct 2017 11:33:49 + with message-id and subject line Bug#875706: fixed in edbrowse 3.7.1-1 has caused the Debian Bug report #875706, regarding edbrowse: please package new upstream version to be marked as done. This means that you claim that the problem has been dea

Bug#879905: glee: source for GLee.c and GLee.h is missing

Steve Cotton: > Source: glee > Severity: serious > Justification: missing source (GLeeGen), missing source (GL ext specs) > > GLee already has serious bug #879123, and the auto-removal email > for dependencies was sent this morning. Most of the discussion in > #879123 looks as if a .dsfg tarball w

Bug#879932: haskell-hoauth2: B-D: libghc-aeson-dev (< 1.1) but 1.1.2.0-1 is to be installed

Source: haskell-hoauth2 Version: 0.5.7-1 Severity: serious Justification: fails to build from source (but built successfully in the past) haskell-hoauth2 can no longer be built since haskell-aeson was updated in sid. Andreas

Bug#879923: marked as done ([!] (commonjs plugin) TypeError: Cannot read property 'parse' of undefined)

Your message dated Fri, 27 Oct 2017 11:04:11 + with message-id and subject line Bug#879923: fixed in node-rollup-plugin-commonjs 8.2.4-2 has caused the Debian Bug report #879923, regarding [!] (commonjs plugin) TypeError: Cannot read property 'parse' of undefined to be marked as done. This m

Bug#879931: vagrant: VirtualBox 5.2 is not supported

Package: vagrant Version: 1.9.8+dfsg-1 Severity: serious Hi! The current version of virtualbox in sid is 5.2.0-dfsg-1, which is not supported by the current vagrant, which only got support for it in git master for which there's been no release yet. Please apply the upstream patch:

Bug#867166: Future of linux-grec in Debian

On Fri, 2017-10-27 at 05:58 -0400, Jordan Glover wrote: > linux-grsec-base[1] is missing from stable-backports and I don't see it > being prepared for upload there[2]. Other than that this bug can be closed. > Thanks for your work. > > [1] https://tracker.debian.org/pkg/linux-grsec-base > [2] http

Bug#875706: edbrowse: please package new upstream version

Control: owner -1 ! On Wed, 13 Sep 2017 21:36:44 +0200 Paul Gevers wrote: > There is a new version of edbrowse available from upstream. Because edbrowse > migrated from the mozjs suite to duktape, packaging is blocked by bug 872040 > in > src:duktape. To avoid unnecessary work, I am filing this

Processed: Re: edbrowse: please package new upstream version

Processing control commands: > owner -1 ! Bug #875706 [edbrowse] edbrowse: please package new upstream version Owner recorded as Paul Gevers . -- 875706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#867166: Future of linux-grec in Debian

linux-grsec-base[1] is missing from stable-backports and I don't see it being prepared for upload there[2]. Other than that this bug can be closed. Thanks for your work. [1] https://tracker.debian.org/pkg/linux-grsec-base [2] https://anonscm.debian.org/git/collab-maint/linux-grsec-base.git

Bug#879923: [!] (commonjs plugin) TypeError: Cannot read property 'parse' of undefined

package: node-rollup-plugin-commonjs version: 8.2.4-1 severity: serious When building rollup using node-rollup-plugin-commonjs, it fails with error (with npm installed rollup-plugin-commonjs, build succeeds). src/node-entry.js → dist/rollup.js, dist/rollup.es.js... [!] (commonjs plugin) TypeError

Bug#867058: [pkg-golang-devel] Bug#867058: golang-1.8 and mips*

On 27 October 2017 at 22:38, James Cowgill wrote: > Hi, > > On 26/10/17 20:33, John Paul Adrian Glaubitz wrote: > > On 10/26/2017 07:12 PM, peter green wrote: > >> Therefore golang maintainers you have two choices. > >> > >> 1. Accept John's changes so that your package can be built on mips*. > >

Bug#873675: marked as done (libexecs: FTBFS w/GCC 7: null where non-null expected)

Your message dated Fri, 27 Oct 2017 09:35:17 + with message-id and subject line Bug#873675: fixed in libexecs 1.1-1 has caused the Debian Bug report #873675, regarding libexecs: FTBFS w/GCC 7: null where non-null expected to be marked as done. This means that you claim that the problem has be

Bug#867058: golang-1.8 and mips*

Hi, On 26/10/17 20:33, John Paul Adrian Glaubitz wrote: > On 10/26/2017 07:12 PM, peter green wrote: >> Therefore golang maintainers you have two choices. >> >> 1. Accept John's changes so that your package can be built on mips*. >> 2. File a removal request for the binaries uploaded by John > >

Bug#875421: marked as done (libexecs-dev: missing Depends: libexecs-embedded0 (= ${binary:Version}))

Your message dated Fri, 27 Oct 2017 09:35:17 + with message-id and subject line Bug#875421: fixed in libexecs 1.1-1 has caused the Debian Bug report #875421, regarding libexecs-dev: missing Depends: libexecs-embedded0 (= ${binary:Version}) to be marked as done. This means that you claim that

Bug#879922: pandoc: B-D: libghc-syb-dev (< 0.7) but 0.7-1 is to be installed

Source: pandoc Version: 1.19.2.1.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) pandoc cannot be built in sid any more since libghc-syb-dev was updated. Andreas

Bug#879798: FTBFS: testsuite fails with dpkg 1.19, patch attached

On Fri, Oct 27, 2017 at 04:49:44AM +, Adam Conrad wrote: > I'd suggest that this commit already makes no-delta backports somewhat > problematic: > > https://anonscm.debian.org/git/collab-maint/devscripts.git/commit/?id=921696fd6c92c4299accb1e2ef1ae48d13a47b0d Well, that doesn't stop backports

Processed: Bug#879798 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 879798 pending Bug #879798 [devscripts] FTBFS: testsuite fails with dpkg 1.19, patch attached Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 879798: https://bugs.debian.org/cgi-bin/bugre

Bug#879798: marked as pending

tag 879798 pending thanks Hello, Bug #879798 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: https://anonscm.debian.org/cgit/collab-maint/devscripts.git/commit/?id=96030da --- commit 96030dac7ca3f9e70ade3970ca

Bug#877412: marked as done (beginend-el FTBFS with elpa-buttercup 1.9)

Your message dated Fri, 27 Oct 2017 09:04:05 + with message-id and subject line Bug#877412: fixed in beginend-el 2.0.0-2 has caused the Debian Bug report #877412, regarding beginend-el FTBFS with elpa-buttercup 1.9 to be marked as done. This means that you claim that the problem has been deal

Bug#877523: marked as done (openjdk-9 FTBFS with debhelper 10.9)

Your message dated Fri, 27 Oct 2017 09:00:15 + with message-id and subject line Bug#877523: fixed in openjdk-9 9.0.1+11-1 has caused the Debian Bug report #877523, regarding openjdk-9 FTBFS with debhelper 10.9 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#879917: libgambit4-dev: fails to upgrade from 'sid' - trying to overwrite /usr/include/gambit.h

Package: libgambit4-dev Version: 4.8.8-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it trie

Bug#879912: lxqt-runner: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-runner.desktop

Package: lxqt-runner Version: 0.12.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries

Bug#879911: lxqt-powermanagement: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-powermanagement.desktop

Package: lxqt-powermanagement Version: 0.12.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because

Bug#879910: lxqt-panel: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-panel.desktop

Package: lxqt-panel Version: 0.12.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries t

Bug#873860: ibus-anthy FTBFS: UnicodeDecodeError: 'euc_jp' codec can't decode byte 0xe5 in position 46: illegal multibyte sequence

On Fri, 22 Sep 2017 23:20:39 +0900 Osamu Aoki wrote: > On Fri, Sep 22, 2017 at 09:14:22AM +0200, John Paul Adrian Glaubitz wrote: > > This FTBFS can be easily fixed with: > > > > --- ibus-anthy-1.5.9.orig/data/zipcode-textdic.py > > +++ ibus-anthy-1.5.9/data/zipcode-textdic.py > > @@ -21,7 +21,7 @

Processed: retitle 879907 to python{,3}-tempest: fails to upgrade from sid - trying to overwrite /usr/bin/python[23]-check-uuid

Processing commands for cont...@bugs.debian.org: > retitle 879907 python{,3}-tempest: fails to upgrade from sid - trying to > overwrite /usr/bin/python[23]-check-uuid Bug #879907 [python-tempest,python3-tempest] pythoni{,3}-tempest: fails to upgrade from 'sid' - trying to overwrite /usr/bin/pyth

Bug#867431: marked as done (python3-hacking: incorrect dependencies)

Your message dated Fri, 27 Oct 2017 07:35:41 + with message-id and subject line Bug#867431: fixed in python-hacking 0.11.0-2.1 has caused the Debian Bug report #867431, regarding python3-hacking: incorrect dependencies to be marked as done. This means that you claim that the problem has been

Bug#877541: marked as done (golang-1.9: Invalid instruction error in i386)

Your message dated Fri, 27 Oct 2017 07:35:10 + with message-id and subject line Bug#877541: fixed in golang-1.9 1.9.2-2 has caused the Debian Bug report #877541, regarding golang-1.9: Invalid instruction error in i386 to be marked as done. This means that you claim that the problem has been d

Bug#879909: libgtksourceview-4-dev: fails to upgrade from 'sid' - trying to overwrite /usr/share/glade/catalogs/gtksourceview.xml

Package: libgtksourceview-4-dev Version: 3.99.6-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails becaus

Bug#879907: pythoni{,3}-tempest: fails to upgrade from 'sid' - trying to overwrite /usr/bin/python[23]-check-uuid

Package: python-tempest,python3-tempest Version: 1:17.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fa

Bug#877541: Pending fixes for bugs in the golang package

tag 877541 + pending thanks Some bugs in the golang package are closed in revision a0cd15c626ef6aa48037755d3d577f9c6871d1f0 in branch ' golang-1.9' by Michael Stapelberg The full diff can be seen at https://anonscm.debian.org/cgit/pkg-golang/golang.git/commit/?id=a0cd15c Commit message: Ad

Processed: Pending fixes for bugs in the golang package

Processing commands for cont...@bugs.debian.org: > tag 877541 + pending Bug #877541 [golang-1.9] golang-1.9: Invalid instruction error in i386 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 877541: https://bugs.debian.org/cgi-bin/bugreport.c

  1   2   >