Processed: tagging 811432

Processing commands for cont...@bugs.debian.org: > tags 811432 + pending Bug #811432 [krita] sid: unable to install, missing deps: libilmbase6 libopenexr6 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 811432:

Bug#811846: #811846: status?

Hi, what's the status of this bug (xbase64 that FTBFS with GCC 6)? Because of it, xbase64 was removed from testing a couple of months ago, and now it will prevent calligra (which ships a sybase access driver for kexi) to migrate to testing. Any way I can help with this? Thanks, -- Pino Toscano

Bug#838050: GDM3-only behaviour; Wayland not totally broken; bad tablets break even that

The behaviour in gdm3 alone (outside of a user session) is different from tablet to tablet. * Wacom Intuos5 USB: no crashes, pen functions as a second crosshair pointer * HUION H610PRO USB: no crashes, pen functions as a second crosshair pointer * Genius EasyPen i405X USB: crashes

Processed: bug 838050 control

Processing commands for cont...@bugs.debian.org: > affects 838050 + libwacom2 gimp mypaint Bug #838050 [gnome-shell] gnome-shell: gdm doesn't start due to a problem with gnome-shell crashing in libwacom2 Added indication that 838050 affects libwacom2, gimp, and mypaint > tags 838050 + confirmed

Bug#838050: Breaks all tablets, no good workaround

My first through was the common Debian situation where there's a mismatch between libwacom2 (which lags releases regularly) and GNOME (which advances fast). It may well not be libwacom at fault, but without a debugging trace we can't tell yet. A recent update to libwacom 0.22 doesn't fix this

Bug#838047: Confirmed: breaks *all* tablets

GNOME sessions with gnome-shell 3.21.91-2 and libwacom2 0.22-1 still segfault when any any of my USB tablet devices are attached. This includes the Wacom USB Wireless Accessory Kit: it's fine after being plugged in initially without the tablet being turned on, but when the tablet is turned on and

Bug#822051: marked as done (lmbench: Build arch:all+arch:any but is missing build-{arch,indep} targets)

Your message dated Sun, 18 Sep 2016 00:34:04 + with message-id and subject line Bug#822051: fixed in lmbench 3.0-a9-1.2 has caused the Debian Bug report #822051, regarding lmbench: Build arch:all+arch:any but is missing build-{arch,indep} targets to be

Bug#817567: marked as done (lmbench: Removal of debhelper compat 4)

Your message dated Sun, 18 Sep 2016 00:34:04 + with message-id and subject line Bug#817567: fixed in lmbench 3.0-a9-1.2 has caused the Debian Bug report #817567, regarding lmbench: Removal of debhelper compat 4 to be marked as done. This means that you

Bug#817516: marked as done (lakai: Removal of debhelper compat 4)

Your message dated Sat, 17 Sep 2016 23:48:29 + with message-id and subject line Bug#817516: fixed in lakai 0.1-1.1 has caused the Debian Bug report #817516, regarding lakai: Removal of debhelper compat 4 to be marked as done. This means that you claim

Bug#837629: OpenRD* with debian's u-boot 2016.09

On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian wrote: > There is at one report of an OpenRD ultimate that would not boot with > the 2016.09~rc2 version of u-boot in debian. Uploaded 2016.09+dfsg-1 to > unstable a few days ago. Would you be able to confirm if OpenRD variants

Processed: Re: Bug#836993: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

Processing control commands: > tags -1 pending Bug #836993 [qgis] qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis' Added tag(s) pending. -- 836993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836993 Debian Bug Tracking System Contact

Bug#836993: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

Control: tags -1 pending Hi Andreas, On 09/17/2016 06:39 PM, Andreas Beckmann wrote: > still not completely resolved, Will the third time be the charm? I haven't been able to reproduce this issue with my piuparts setup, not now and not before, I guess piuparts.d.o. does something more

Bug#811584: marked as done (FTBFS with GCC 6: statement indented as if it were guarded by)

Your message dated Sat, 17 Sep 2016 22:28:01 + with message-id and subject line Bug#811584: fixed in phalanx 22+d051004-14 has caused the Debian Bug report #811584, regarding FTBFS with GCC 6: statement indented as if it were guarded by to be marked as

Bug#834960: marked as done (libdaemon-generic-perl: FTBFS too much often (failing tests))

Your message dated Sat, 17 Sep 2016 22:22:40 + with message-id and subject line Bug#834960: fixed in libdaemon-generic-perl 0.84-2 has caused the Debian Bug report #834960, regarding libdaemon-generic-perl: FTBFS too much often (failing tests) to be marked

Bug#820401: marked as done (ciphersaber: FTBFS on binary-indep-only build)

Your message dated Sat, 17 Sep 2016 22:00:57 + with message-id and subject line Bug#820401: fixed in ciphersaber 1.01-1 has caused the Debian Bug report #820401, regarding ciphersaber: FTBFS on binary-indep-only build to be marked as done. This means that

Bug#834960: Pending fixes for bugs in the libdaemon-generic-perl package

tag 834960 + pending thanks Some bugs in the libdaemon-generic-perl package are closed in revision 75331d5d9ccbf69f8b7c3a410ef189dd1eb791a2 in branch 'master' by gregor herrmann The full diff can be seen at

Bug#834960: libdaemon-generic-perl: FTBFS too much often (failing tests)

On Sat, 17 Sep 2016 21:27:33 +0300, Niko Tyni wrote: > > From starting at t/daemon.t my guess is that we're seeing a race > > condition or some other timing issue here -- the daemon writes to a > > log file and the test reads the logfile, and in one case the log > > message doesn't seem to be

Processed: Pending fixes for bugs in the libdaemon-generic-perl package

Processing commands for cont...@bugs.debian.org: > tag 834960 + pending Bug #834960 [src:libdaemon-generic-perl] libdaemon-generic-perl: FTBFS too much often (failing tests) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 834960:

Bug#797481: marked as done (fw4spl: FTBFS - Doesn't support boost 1.58)

Your message dated Sat, 17 Sep 2016 21:41:10 + with message-id and subject line Bug#838061: Removed package(s) from unstable has caused the Debian Bug report #797481, regarding fw4spl: FTBFS - Doesn't support boost 1.58 to be marked as done. This means

Bug#821957: marked as done (fw4spl: Depends on insighttoolkit, which is about to be removed. Please port to insighttoolkit4)

Your message dated Sat, 17 Sep 2016 21:41:10 + with message-id and subject line Bug#838061: Removed package(s) from unstable has caused the Debian Bug report #821957, regarding fw4spl: Depends on insighttoolkit, which is about to be removed. Please port

Bug#822118: marked as done (RM: fw4spl -- RoQA, unmaintained, RC-buggy, FTBFS, blocks removal of old packages)

Your message dated Sat, 17 Sep 2016 21:41:10 + with message-id and subject line Bug#838061: Removed package(s) from unstable has caused the Debian Bug report #822118, regarding RM: fw4spl -- RoQA, unmaintained, RC-buggy, FTBFS, blocks removal of old

Bug#809935: marked as done (fw4spl: FTBFS with libpng16)

Your message dated Sat, 17 Sep 2016 21:41:10 + with message-id and subject line Bug#838061: Removed package(s) from unstable has caused the Debian Bug report #809935, regarding fw4spl: FTBFS with libpng16 to be marked as done. This means that you claim

Bug#797475: marked as done (fw4spl: does not support parallel build)

Your message dated Sat, 17 Sep 2016 21:41:10 + with message-id and subject line Bug#838061: Removed package(s) from unstable has caused the Debian Bug report #797475, regarding fw4spl: does not support parallel build to be marked as done. This means that

Bug#820632: marked as done (fw4spl: depends on vtk 5)

Your message dated Sat, 17 Sep 2016 21:41:10 + with message-id and subject line Bug#838061: Removed package(s) from unstable has caused the Debian Bug report #820632, regarding fw4spl: depends on vtk 5 to be marked as done. This means that you claim that

Processed: tagging 834960

Processing commands for cont...@bugs.debian.org: > tags 834960 - unreproducible Bug #834960 [src:libdaemon-generic-perl] libdaemon-generic-perl: FTBFS too much often (failing tests) Removed tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#837192:

Hi, This bug is fixed with the latest version currently on the review process in Mentors: https://mentors.debian.net/package/gnome-shell-pomodoro It will be uploaded when validated by my mentor. If you feel like double checking the new package, every constructive comment is welcome! :-) Thanks,

Bug#836759: proftpd-dfsg: please drop the build dependency on hardening-wrapper

On 05.09.16 Matthias Klose (d...@debian.org) wrote: Hi Matthias, > This package builds using the hardening-includes package, which > is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings. > > Please consider dropping the build dependency of hardening-includes > and use the

Bug#834960: libdaemon-generic-perl: FTBFS too much often (failing tests)

On Sat, Sep 17, 2016 at 07:20:09PM +0200, gregor herrmann wrote: > CPAN RT has one issue; don't know if it's related: > https://rt.cpan.org/Public/Bug/Display.html?id=110239 I think it's a different issue. > From starting at t/daemon.t my guess is that we're seeing a race > condition or some

Bug#835992: marked as done (spl-dkms: Fails to build against kernel package 4.7.0-1)

Your message dated Sat, 17 Sep 2016 18:28:46 + with message-id and subject line Bug#835992: fixed in spl-linux 0.6.5.8-1 has caused the Debian Bug report #835992, regarding spl-dkms: Fails to build against kernel package 4.7.0-1 to be marked as done. This

Processed: owfs-common: missing Breaks: libow-2.8-15

Processing control commands: > affects -1 + owhttpd owftpd owfs-fuse owserver libow-dev libow-perl > libow-php5 libow-tcl owfs-dbg python-ow Bug #838144 [owfs-common] owfs-common: missing Breaks: libow-2.8-15 Added indication that 838144 affects owhttpd, owftpd, owfs-fuse, owserver, libow-dev,

Bug#838144: owfs-common: missing Breaks: libow-2.8-15

Package: owfs-common Version: 3.1p1-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + owhttpd owftpd owfs-fuse owserver libow-dev libow-perl libow-php5 libow-tcl owfs-dbg python-ow Hi, during a test with piuparts I noticed your package fails to

Processed: emacs24: missing Breaks: oneliner-el (<= 0.3.6-7.1)

Processing control commands: > affects -1 + oneliner-el Bug #838143 [emacs24] emacs24: missing Breaks: oneliner-el (<= 0.3.6-7.1) Added indication that 838143 affects oneliner-el -- 838143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838143 Debian Bug Tracking System Contact

Bug#838143: emacs24: missing Breaks: oneliner-el (<= 0.3.6-7.1)

Package: emacs24 Version: 24.5+1-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + oneliner-el Hi, during a test with piuparts I noticed that emacs24 is not compatible with oneliner-el (that may have been left over from a long grown wheezy

Bug#834960: libdaemon-generic-perl: FTBFS too much often (failing tests)

On Sun, 21 Aug 2016 02:21:52 +0200, gregor herrmann wrote: > > I tried to build this package in stretch with "dpkg-buildpackage -A" > > (which is what the "Arch: all" autobuilder would do to build it) > > but it failed: > Builds fine for me (amd64 sind cowbuilder). Some additional information:

Bug#833965: tcsh: uses deprecated BSD union wait type

Hi, just a friendly ping whether this is still on anyone’s radar. I assume that #837026 [1] is a direct consequence of this issue? Cheers Sascha [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837026 On Thu, 1 Sep 2016 13:02:17 +0200 Thomas Lange wrote:

Processed: affects 765120, affects 811306, user debian...@lists.debian.org, usertagging 811306 ...

Processing commands for cont...@bugs.debian.org: > affects 765120 + libmonogame-cil Bug #765120 [src:monogame] monogame: support monodevelop 5 Added indication that 765120 affects libmonogame-cil > affects 811306 + mmpong-gl Bug #811306 [mmpong] FTBFS: mmpong-gl-data missing files:

Bug#837759: network configuration stops working reliably

On 15 September 2016 at 12:36, Felipe Sateler wrote: > On 14 September 2016 at 18:34, Wolfgang Walter > wrote: >> On Wednesday, 14 September 2016 10:00:28 CEST Felipe Sateler wrote: >>> Control: tags -1 moreinfo >>> >>> On 14 September 2016 at

Processed: Re: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

Processing control commands: > found -1 2.14.6+dfsg-3 Bug #836993 {Done: Bas Couwenberg } [qgis] qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis' Marked as found in versions qgis/2.14.6+dfsg-3; no longer marked as fixed

Bug#836993: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

Followup-For: Bug #836993 Control: found -1 2.14.6+dfsg-3 Hi, still not completely resolved, I'll try to find some time to look there myself. Preparing to unpack .../qgis_2.14.6+dfsg-3_amd64.deb ... Unpacking qgis (2.14.6+dfsg-3) over (2.4.0-1+b1) ... dpkg: error processing archive

Bug#836930: marked as done (mssstest: FTBFS with GCC 6: error: reference to 'rank' is ambiguous)

Your message dated Sat, 17 Sep 2016 16:35:14 + with message-id and subject line Bug#836930: fixed in mssstest 3.0-5 has caused the Debian Bug report #836930, regarding mssstest: FTBFS with GCC 6: error: reference to 'rank' is ambiguous to be marked as

Bug#836825: marked as done (ruby-sys-filesystem: FTBFS in testing (failing tests))

Your message dated Sat, 17 Sep 2016 16:37:56 + with message-id and subject line Bug#836825: fixed in ruby-sys-filesystem 1.1.7-2 has caused the Debian Bug report #836825, regarding ruby-sys-filesystem: FTBFS in testing (failing tests) to be marked as done.

Bug#838139: syslog-ng-mod-zmq: symbol lookup error with libzmq.so

Package: syslog-ng-mod-zmq Version: 0.5.0-1 Severity: grave Justification: renders package unusable when using the plugin syslog-ng fails to start with syslog-ng: symbol lookup error: /usr/lib/syslog-ng/3.7/libzmq.so: undefined symbol: init_sequence_number a fix seems to

Bug#815433: marked as done (libdata-messagepack-stream-perl: FTBFS with new msgpack-c library)

Your message dated Sat, 17 Sep 2016 16:33:39 + with message-id and subject line Bug#815433: fixed in libdata-messagepack-stream-perl 1.01+ds-1 has caused the Debian Bug report #815433, regarding libdata-messagepack-stream-perl: FTBFS with new msgpack-c

Bug#834170: marked as done (arb: FTBFS with GCC 6)

Your message dated Sat, 17 Sep 2016 16:21:37 + with message-id and subject line Bug#834170: fixed in arb 6.0.3-2 has caused the Debian Bug report #834170, regarding arb: FTBFS with GCC 6 to be marked as done. This means that you claim that the problem has

Bug#838137: critterding: FTBFS in experimental: be_command_system.cpp:13:94: error: '_1' was not declared in this scope

Source: critterding Version: 1.0-beta14+dfsg-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, critterding/experimental FTBFS, probably due to the default compiler now being GCC 6: [ 34%] Building CXX object

Processed: owner 806617

Processing commands for cont...@bugs.debian.org: > owner 806617 stapelb...@debian.org Bug #806617 [src:freeradius] freeradius: FTBFS when built with dpkg-buildpackage -A (dh_install: freeradius-common missing files) Owner recorded as stapelb...@debian.org. > thanks Stopping processing here.

Bug#838050: gnome-shell: gdm doesn't start due to a problem with gnome-shell crashing in libwacom2

Am Samstag, den 17.09.2016, 09:37 +0200 schrieb Michael Biebl: > Am 17.09.2016 um 01:09 schrieb Erik Tews: > > > > > After startup, gdm doesn't show up and just shows a grey screen. > > Looking at syslog reveals the reason: > > > > syslog:Sep 16 23:27:25 matte kernel: [  172.983123] gnome- > >

Processed: bug 836825 is forwarded to https://github.com/djberg96/sys-filesystem/issues/22

Processing commands for cont...@bugs.debian.org: > forwarded 836825 https://github.com/djberg96/sys-filesystem/issues/22 Bug #836825 [src:ruby-sys-filesystem] ruby-sys-filesystem: FTBFS in testing (failing tests) Set Bug forwarded-to-address to

Bug#836816: marked as done (calligra-l10-*: not installable in sid)

Your message dated Sat, 17 Sep 2016 16:24:53 +0200 with message-id <1608480.BXfNpC1VFq@pendragon> and subject line Re: Bug#836816: calligra-l10-*: not installable in sid has caused the Debian Bug report #836816, regarding calligra-l10-*: not installable in sid to be marked as done. This means

Processed: severity of 837976 is serious, user debian...@lists.debian.org, usertagging 837222 ...

Processing commands for cont...@bugs.debian.org: > severity 837976 serious Bug #837976 [mmh] mmh: Fails to install if package pick is installed Severity set to 'serious' from 'important' > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags

Bug#838116: libgpod-nogtk-dev: fails to install in sid/i386 with --install-recommends

Package: libgpod-nogtk-dev Version: 0.8.3-8 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 the severity.

Bug#830242: [Pkg-javascript-devel] Bug#830242: nodejs: accesses the internet during build

control: found -1 4.3.1~dfsg-1 On Sat, Sep 17, 2016 at 03:42:49PM +0200, Jérémy Lal wrote: > > Is this a regression in 4.4.7, or is 4.3.1 also affected? This is blocking > > testing migration, which is preventing the mips64el binaries from entering > > testing. > > It's been like this forever.

Processed: Re: Bug#830242: [Pkg-javascript-devel] Bug#830242: nodejs: accesses the internet during build

Processing control commands: > found -1 4.3.1~dfsg-1 Bug #830242 [src:nodejs] nodejs: accesses the internet during build Marked as found in versions nodejs/4.3.1~dfsg-1. -- 830242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830242 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#838050: gnome-shell: gdm doesn't start due to a problem with gnome-shell crashing in libwacom2

On Sat, 17 Sep 2016 09:37:48 +0200 Michael Biebl wrote: > Am 17.09.2016 um 01:09 schrieb Erik Tews: >  > > After startup, gdm doesn't show up and just shows a grey screen. Looking at syslog reveals the reason: > >  > > syslog:Sep 16 23:27:25 matte kernel: [  172.983123] gnome-

Bug#830242: [Pkg-javascript-devel] Bug#830242: nodejs: accesses the internet during build

2016-09-17 15:20 GMT+02:00 Emilio Pozuelo Monfort : > Hi, > > On Thu, 07 Jul 2016 16:38:15 +0200 Chris Lamb wrote: > > Source: nodejs > > Version: 4.4.7~dfsg-2 > > Severity: serious > > Justification: Policy 4.9 > > User: la...@debian.org > > Usertags:

Bug#837786: mutter: Issues repainting the display on mouse movement

Since Wednesday, I've done as follows: - Upgraded to mutter 3.21.91-2 and gnome-shell 3.21.91-1 (repaint/redraw issues). - Tried to report the bug, but reportbug showed a version of mutter in unstable. - Upgraded to mutter 3.31.92-1 and gnome-shell 3.21.92-1 (repaint/redraw issues). - Reported the

Processed: limit source to imagemagick, tagging 836174

Processing commands for cont...@bugs.debian.org: > limit source imagemagick Limiting to bugs with field 'source' containing at least one of 'imagemagick' Limit currently set to 'source':'imagemagick' > tags 836174 + pending Bug #836174 [src:imagemagick] Prevent runtime error: divide by zero

Bug#831243: marked as done (nodejs: FTBFS: Tests failures)

Your message dated Sat, 17 Sep 2016 15:22:34 +0200 with message-id <220603eb-42db-125d-36a6-e42c5f449...@debian.org> and subject line Re: nodejs: FTBFS: Tests failures has caused the Debian Bug report #831243, regarding nodejs: FTBFS: Tests failures to be marked as done. This means that you claim

Processed: limit source to libdata-messagepack-perl, tagging 827576

Processing commands for cont...@bugs.debian.org: > limit source libdata-messagepack-perl Limiting to bugs with field 'source' containing at least one of 'libdata-messagepack-perl' Limit currently set to 'source':'libdata-messagepack-perl' > tags 827576 + pending Bug #827576

Bug#830242: nodejs: accesses the internet during build

Hi, On Thu, 07 Jul 2016 16:38:15 +0200 Chris Lamb wrote: > Source: nodejs > Version: 4.4.7~dfsg-2 > Severity: serious > Justification: Policy 4.9 > User: la...@debian.org > Usertags: network-access > > Dear Maintainer, > > Whilst nodejs builds successfully on unstable/amd64,

Bug#838114: varnish-modules: FTBFS against varnish 5, GCC 6

Source: varnish-modules Version: 0.9.1-3 Severity: serious Justification: fails to build from source (but built successfully in the past) varnish-modules against the recently uploaded varnish 5 and/or GCC 6 vmod_xkey.c:456:10: error: 'enum exp_event_e' declared inside parameter list will not be

Bug#838113: pathspider: missing dependency on python3-libtrace

Package: pathspider Version: 0.9.0-1 Severity: serious Justification: Policy 3.5 Hi, Need that dep. Thanks, Iain.

Bug#838112: uctodata: fails to upgrade from 'jessie' - trying to overwrite /etc/ucto/es.abr

Package: uctodata Version: 0.1.1-1 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 'jessie', then the upgrade to 'sid' fails because it tries to overwrite other

Bug#838047: Confirmed: breaks *all* tablets

Upgraded to 0.22-1. No change, unfortunately. [   12.990227] gnome-shell[1168]: segfault at 10 ip 7f35122ab844 sp 7ffd8efd9be0 error 4 in libwacom.so.2.5.0[7f35122a8000+9000] [   14.569733] gnome-shell[1239]: segfault at 10 ip 7f724d4e6844 sp 7fffda2ec150 error 4 in

Bug#838047: Confirmed: breaks *all* tablets

On Sat, 2016-09-17 at 09:34 +0300, Timo Aaltonen wrote: > On 17.09.2016 02:47, a.t.chadw...@gmail.com wrote: > Confirmed. This bug breaks all graphics tablets in GNOME (at least). > It > is not specific to the driver. See the attached logs. > > Symptoms: when a graphics tablet is plugged in,

Bug#835680: marked as done (mathgl: FTBFS: complex_io.cpp:32:18: fatal error: hdf5.h: No such file or directory)

Your message dated Sat, 17 Sep 2016 12:32:12 + with message-id and subject line Bug#835680: fixed in mathgl 2.3.4-1.1 has caused the Debian Bug report #835680, regarding mathgl: FTBFS: complex_io.cpp:32:18: fatal error: hdf5.h: No such file or directory

Bug#834683: marked as done (mini-buildd: FTBFS too much often (failing tests))

Your message dated Sat, 17 Sep 2016 12:32:37 + with message-id and subject line Bug#834683: fixed in mini-buildd 1.0.19 has caused the Debian Bug report #834683, regarding mini-buildd: FTBFS too much often (failing tests) to be marked as done. This means

Bug#837942: marked as done (gtk-doc-tools: Missing dependency on pkg-config)

Your message dated Sat, 17 Sep 2016 12:28:01 + with message-id and subject line Bug#837942: fixed in gtk-doc 1.25-5 has caused the Debian Bug report #837942, regarding gtk-doc-tools: Missing dependency on pkg-config to be marked as done. This means that

Bug#838105: marked as done (libssl1.1: relocation error: /usr/lib/libpromises.so.3: symbol X509_get_notAfter, version OPENSSL_1_1_0 not defined in file libcrypto.so.1.1 with link time reference)

Your message dated Sat, 17 Sep 2016 14:27:16 +0200 with message-id <20160917122715.plgveaomympvi...@roeckx.be> and subject line Re: [Pkg-openssl-devel] Bug#838105: libssl1.1: relocation error: /usr/lib/libpromises.so.3: symbol X509_get_notAfter, version OPENSSL_1_1_0 not defined in file

Bug#837783: marked as done (iio-sensor-proxy: hold transition to testing)

Your message dated Sat, 17 Sep 2016 12:28:22 + with message-id and subject line Bug#837783: fixed in iio-sensor-proxy 1.3-1 has caused the Debian Bug report #837783, regarding iio-sensor-proxy: hold transition to testing to be marked as done. This means

Bug#831164: marked as done (aces3: FTBFS with GCC 6: ld: cannot find -lgfortranbegin)

Your message dated Sat, 17 Sep 2016 12:25:05 + with message-id and subject line Bug#831164: fixed in aces3 3.0.8-5.1 has caused the Debian Bug report #831164, regarding aces3: FTBFS with GCC 6: ld: cannot find -lgfortranbegin to be marked as done. This

Bug#785799: marked as done ([festvox-ca-ona-hts] Since las festival upgrade, catalan voice is not correctly recognized and does not work)

Your message dated Sat, 17 Sep 2016 12:25:49 + with message-id and subject line Bug#785799: fixed in festvox-ca-ona-hts 1.3-1 has caused the Debian Bug report #785799, regarding [festvox-ca-ona-hts] Since las festival upgrade, catalan voice is not

Processed: Re: [Pkg-alsa-devel] Bug#837590: Bug#837590: alsa-tools FTBFS on armel: gcc-6 narrowing conversions

Processing control commands: > tags -1 + fixed pending Bug #837590 [src:alsa-tools] alsa-tools FTBFS on armel: gcc-6 narrowing conversions Added tag(s) fixed and pending. -- 837590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837590 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#837590: [Pkg-alsa-devel] Bug#837590: Bug#837590: alsa-tools FTBFS on armel: gcc-6 narrowing conversions

Control: tags -1 + fixed pending * Elimar Riesebieter [2016-09-12 18:57 +0200]: > Control: forwarded -1 > http://mailman.alsa-project.org/pipermail/alsa-devel/2016-September/112697.html > > * Helmut Grohne [2016-09-12 18:23 +0200]: > > > Source:

Bug#837276: python-mne: FTBFS: build-dependency not installable: mayavi2 (>= 4.4.3-1)

Hi, I am unable to reproduce this FTBFS in a current sid amd64 cowbuilder chroot. See attached build log. I can see that the latest mayavi2 NMU (4.4.3-2.2) failed to build for amd64, but I was sure able to get 4.4.3-2.1. I’m not sure I understand if this might be the reason for this failure

Processed: libssl1.1: relocation error: /usr/lib/libpromises.so.3: symbol X509_get_notAfter, version OPENSSL_1_1_0 not defined in file libcrypto.so.1.1 with link time reference

Processing control commands: > affects -1 cfengine3 Bug #838105 [libssl1.1] libssl1.1: relocation error: /usr/lib/libpromises.so.3: symbol X509_get_notAfter, version OPENSSL_1_1_0 not defined in file libcrypto.so.1.1 with link time reference Added indication that 838105 affects cfengine3 --

Bug#838105: libssl1.1: relocation error: /usr/lib/libpromises.so.3: symbol X509_get_notAfter, version OPENSSL_1_1_0 not defined in file libcrypto.so.1.1 with link time reference

Package: libssl1.1 Version: 1.1.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 cfengine3 Hi, during a test with piuparts I noticed cfengine3/experimental failed to install in experimental with a openssl symbol related problem. >From the attached

Processed: raise severity for issues, because hardening-wrapper/hardening-includes is not installable

Processing commands for cont...@bugs.debian.org: > severity 836634 serious Bug #836634 [libmsn] libmsn: please drop the build dependency on hardening-wrapper Severity set to 'serious' from 'important' > severity 836647 serious Bug #836647 [postgresql-9.5] postgresql-9.5: please drop the build

Processed: found 837786 in 3.21.91-2

Processing commands for cont...@bugs.debian.org: > found 837786 3.21.91-2 Bug #837786 [mutter] mutter: Issues repainting the display on mouse movement Marked as found in versions mutter/3.21.91-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 837786:

Bug#837786: mutter: Issues repainting the display on mouse movement

On Sat, 17 Sep 2016 09:18:45 +0200 Michael Biebl wrote: Am 14.09.2016 um 17:16 schrieb JWM: > After upgrading my system this morning and restarting a new gnome-shell session > (by rebooting), everything being displayed fails to repaint properly. > > Everytime I launch an

Bug#835581: node-es6-promise: FTBFS in testing (compile-modules shows usage help)

Hi, node-ast-types 0.9.0-2 migrated to testing two weeks ago, so it should now be pretty trivial to check whether the problem is gone. Can you confirm my intuition? Thanks, Snark on #debian-js

Bug#838080: bacula-director-pgsql: make_catalog_backup fails

Package: bacula-director-pgsql Version: 7.4.3+dfsg-6 Severity: serious XXX_DBUSER_XXX is not replaced by the name of the database user in make_catalog_backup: user=${2:-XXX_DBUSER_XXX} consequently, the catalog backup fails.

Bug#835185: mysql-workbench: Segfault when opening connection

The same problem here. On 6-Sep-2016 I updated libmysqlcppconn7v5 (sid), which solved the problem with Segfault. On 16-Sep-2016 I updated libreoffice (stretch) and the connection to the mysql server crashes again with SIGSEGV. Here is gdbtrace.log: warning: Currently logging to gdbtrace.log.

Processed: Bug in xml-core which affects several packages

Processing commands for cont...@bugs.debian.org: > affects 837620 src:w3-dtd-mathml Bug #837620 [xml-core] w3-dtd-mathml: FTBFS: dh_installxmlcatalogs: Unexpected debhelper version format Bug #837618 [xml-core] docbook-slides: FTBFS: dh_installxmlcatalogs: Unexpected debhelper version format

Processed: Bug in xml-core which affects several packages

Processing commands for cont...@bugs.debian.org: > reassign 837618 xml-core Bug #837618 [src:docbook-slides] docbook-slides: FTBFS: dh_installxmlcatalogs: Unexpected debhelper version format Bug reassigned from package 'src:docbook-slides' to 'xml-core'. No longer marked as found in versions

Bug#835992: [Pkg-zfsonlinux-devel] Bug#835992: 835992

Dear Petter, the build failure reported here is independent of the dkms problem in #836578. I applied the suggested patch from #836578, but the build still fails with Linux 4.7 (see attached /var/lib/dkms/spl/0.6.5.7/build/make.log). The changes of ZFS v0.6.5.8 [1] contain the compatibility

Bug#837994: [debian-mysql] Bug#837994: Bug#837994: mysql-5.5: FTBFS on armhf

Control: severity -1 important Hi Lars, hi all, It finally worked on another buildd, namely henze, https://db.debian.org/machines.cgi?host=henze I'm lowering the severity to important since we have now all builds. But before eventually closing it would be nice if we can get an idea why it

Processed: Re: [debian-mysql] Bug#837994: Bug#837994: mysql-5.5: FTBFS on armhf

Processing control commands: > severity -1 important Bug #837994 [src:mysql-5.5] mysql-5.5: FTBFS on armhf Severity set to 'important' from 'serious' -- 837994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#830609: marked as done (python-structlog: accesses the internet during build)

Your message dated Sat, 17 Sep 2016 08:19:22 + with message-id and subject line Bug#830609: fixed in python-structlog 16.1.0-1 has caused the Debian Bug report #830609, regarding python-structlog: accesses the internet during build to be marked as done.

Processed (with 2 errors): merge bugs

Processing commands for cont...@bugs.debian.org: > reassign 837227 src:rebar Bug #837227 [rebar] neotoma: FTBFS: Uncaught error in rebar_core: {'EXIT', Bug reassigned from package 'rebar' to 'src:rebar'. Ignoring request to alter found versions of bug #837227 to the same values previously set

Bug#830609: marked as pending

tag 830609 pending thanks Hello, Bug #830609 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-structlog.git;a=commitdiff;h=f5a148c --- commit

Processed: Bug#830609 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 830609 pending Bug #830609 [src:python-structlog] python-structlog: accesses the internet during build Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 830609:

Bug#837942: gtk-doc-tools: Missing dependency on pkg-config

Am 15.09.2016 um 19:58 schrieb Andreas Metzler: > Package: gtk-doc-tools > Version: 1.25-4 > Severity: serious > > gtk-doc-tools in experimental is lacking a dependency on pkg-config, > GTK_DOC_CHECK will fail if it is missing. > > --- > AC_DEFUN([GTK_DOC_CHECK], > [

Bug#808055: marked as done (php-pinba: FTBFS: PHP Fatal error: Call to a member function getFilelist() on null in /usr/share/php/PEAR/Command/Install.php on line 747)

Your message dated Sat, 17 Sep 2016 09:58:06 +0200 with message-id and subject line Re: Bug#808055: php-pinba: FTBFS: PHP Fatal error: Call to a member function getFilelist() on null in /usr/share/php/PEAR/Command/Install.php on line 747 has caused the Debian Bug

Processed (with 2 errors): merge bugs

Processing commands for cont...@bugs.debian.org: > reassign 837227 rebar Bug #837227 [src:neotoma] neotoma: FTBFS: Uncaught error in rebar_core: {'EXIT', Bug reassigned from package 'src:neotoma' to 'rebar'. No longer marked as found in versions neotoma/1.7.3+dfsg-1. Ignoring request to alter

Bug#837234: marked as done (rebar: FTBFS: Uncaught error in rebar_core: {'EXIT',)

Your message dated Sat, 17 Sep 2016 07:48:50 + with message-id and subject line Bug#837234: fixed in rebar 2.6.4-1 has caused the Debian Bug report #837234, regarding rebar: FTBFS: Uncaught error in rebar_core: {'EXIT', to be marked as done. This means

Bug#837786: mutter: Issues repainting the display on mouse movement

Am 14.09.2016 um 17:16 schrieb JWM: > After upgrading my system this morning and restarting a new gnome-shell > session > (by rebooting), everything being displayed fails to repaint properly. > > Everytime I launch an application and try to move the window it leaves traces > (i.e., shadows of

Bug#838050: gnome-shell: gdm doesn't start due to a problem with gnome-shell crashing in libwacom2

Am 17.09.2016 um 01:09 schrieb Erik Tews: > After startup, gdm doesn't show up and just shows a grey screen. Looking at > syslog reveals the reason: > > syslog:Sep 16 23:27:25 matte kernel: [ 172.983123] gnome-shell[3206]: > segfault > at 10 ip 7f8e7c85d6c4 sp 7ffd151d0a80 error 4 in

Processed (with 1 error): merge bugs

Processing commands for cont...@bugs.debian.org: > merge 837234 837227 837277 837275 837259 837252 837283 837231 837286 837250 Bug #837234 [src:rebar] rebar: FTBFS: Uncaught error in rebar_core: {'EXIT', Unable to merge bugs because: package of #837227 is 'src:neotoma' not 'src:rebar' package of

Bug#838047: Confirmed: breaks *all* tablets

On 17.09.2016 02:47, a.t.chadw...@gmail.com wrote: > Confirmed. This bug breaks all graphics tablets in GNOME (at least). It > is not specific to the driver. See the attached logs. > > Symptoms: when a graphics tablet is plugged in, within a few seconds the > running X session terminates.

  1   2   >