Bug#874712: python-h5py: all arches FTBFS

Package: python-h5py Version: 2.7.0-1+b1 Severity: serious Justification: FTBFS Your new version of h5py fails to build from source. All arches. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64

Bug#784181: razorqt: Razor-Qt dead upstream, superseded by LXQt

Control: retitle -1 razorqt: Razor-Qt dead upstream, superseded by LXQt Control: severity -1 grave Hello, Bump on this. razorqt has been dead upstream for several years now (several LXQt releases have made it in Debian, even making it into Stretch), and popcon statistics have dropped. I would

Processed: razorqt: Razor-Qt dead upstream, superseded by LXQt

Processing control commands: > retitle -1 razorqt: Razor-Qt dead upstream, superseded by LXQt Bug #784181 [src:razorqt] razorqt: Razor-Qt dead upstream, superseded by LXDE-Qt Changed Bug title to 'razorqt: Razor-Qt dead upstream, superseded by LXQt' from 'razorqt: Razor-Qt dead upstream,

Bug#852563: marked as done (ipheth: Update udevadm path)

Your message dated Fri, 08 Sep 2017 23:49:29 + with message-id and subject line Bug#852563: fixed in ipheth 1.0-5 has caused the Debian Bug report #852563, regarding ipheth: Update udevadm path to be marked as done. This means that you claim that the

Bug#874656: libegl1-mesa: Makes team fortress 2 crash the entire machine

Well I had to downgrade to testing since it was making my machine crash. Il 08 Set 2017 19:34, "Timo Aaltonen" ha scritto: > On 08.09.2017 16:48, Salvo Tomaselli wrote: > > Package: libegl1-mesa > > Version: 17.2.0-2 > > Severity: grave > > Justification: causes non-serious

Bug#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

On Fri, 8 Sep 2017 23:17:49 +0200 Rene Engelhard wrote: > On Fri, Sep 08, 2017 at 07:37:03PM +0200, Francesco Poli wrote: > > Will libreoffice/1:5.4.1-1 (currently in unstable and testing) break, > > if I upgrade coinor-libcoinutils3v5 from version 2.9.15-4 to version > > 2.10.14+repack1-1 ? > >

Bug#873557: marked as done (mbedtls: CVE-2017-14032: authentication bypass)

Your message dated Fri, 08 Sep 2017 22:17:08 + with message-id and subject line Bug#873557: fixed in mbedtls 2.4.2-1+deb9u1 has caused the Debian Bug report #873557, regarding mbedtls: CVE-2017-14032: authentication bypass to be marked as done. This means

Bug#874611: marked as done (python-shapely,python3-shapely: uninstallable in sid)

Your message dated Fri, 8 Sep 2017 23:56:41 +0200 with message-id <4f7596f7-7d6b-7088-1560-7fe0e8320...@debian.org> and subject line Re: Bug#874611: python-shapely,python3-shapely: uninstallable in sid has caused the Debian Bug report #874611, regarding python-shapely,python3-shapely:

Bug#874654: marked as done (xmltooling: provide a GCC 7 build with strict enough shlibs)

Your message dated Fri, 08 Sep 2017 21:49:51 + with message-id and subject line Bug#874654: fixed in xmltooling 1.6.0-5 has caused the Debian Bug report #874654, regarding xmltooling: provide a GCC 7 build with strict enough shlibs to be marked as done.

Bug#861333: Why does r-cran-rcppgsl not migrate to testing?

On 8 September 2017 at 22:47, Andreas Tille wrote: | Hi Dirk, | | On Thu, Sep 07, 2017 at 02:46:04PM -0500, Dirk Eddelbuettel wrote: | > | > On 7 September 2017 at 21:20, Andreas Tille wrote: | > | Hi Dirk, | > | | > | On Wed, Sep 06, 2017 at 04:22:33PM -0500, Dirk Eddelbuettel wrote: | > | >

Bug#872844: marked as done (connman: [CVE-2017-12865] stack overflow in dns proxy feature)

Your message dated Fri, 08 Sep 2017 21:17:39 + with message-id and subject line Bug#872844: fixed in connman 1.21-1.2+deb8u1 has caused the Debian Bug report #872844, regarding connman: [CVE-2017-12865] stack overflow in dns proxy feature to be marked as

Bug#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

On Fri, Sep 08, 2017 at 07:37:03PM +0200, Francesco Poli wrote: > Will libreoffice/1:5.4.1-1 (currently in unstable and testing) break, > if I upgrade coinor-libcoinutils3v5 from version 2.9.15-4 to version > 2.10.14+repack1-1 ? The fix for LO is: rebuild coinmp. It works without rebuilding LO.

Bug#784464: marked as done ([freecad] Qt4's WebKit removal)

Your message dated Fri, 08 Sep 2017 21:05:39 + with message-id and subject line Bug#784464: fixed in freecad 0.16.6712+dfsg1-1 has caused the Debian Bug report #784464, regarding [freecad] Qt4's WebKit removal to be marked as done. This means that you

Bug#858643: marked as done (An incomplete active theme can cause post-inst to fail on upgrade/reinstall)

Your message dated Fri, 08 Sep 2017 21:02:13 + with message-id and subject line Bug#858643: fixed in desktop-base 9.0.2+deb9u1 has caused the Debian Bug report #858643, regarding An incomplete active theme can cause post-inst to fail on upgrade/reinstall

Bug#874611: python-shapely,python3-shapely: uninstallable in sid

It looks like this bug has been fixed by 1.6.1-1+b1. Andreas, please confirm. Kind regards, -- Ben Caradoc-Davies Director Transient Software Limited New Zealand

Bug#861333: Why does r-cran-rcppgsl not migrate to testing?

Hi Dirk, On Thu, Sep 07, 2017 at 02:46:04PM -0500, Dirk Eddelbuettel wrote: > > On 7 September 2017 at 21:20, Andreas Tille wrote: > | Hi Dirk, > | > | On Wed, Sep 06, 2017 at 04:22:33PM -0500, Dirk Eddelbuettel wrote: > | > On 6 September 2017 at 22:48, Andreas Tille wrote: > | > | On Wed, Sep

Bug#873921:

oh, ignore my last comment - fixed as of some updates I got today.

Processed: tagging 872668

Processing commands for cont...@bugs.debian.org: > tags 872668 + pending Bug #872668 [src:aspcud] aspcud FTBFS on arm64/armhf with gcc 7 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 872668:

Processed: severity of 852591 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852591 serious Bug #852591 [flashcache] flashcache: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you

Processed: severity of 852587 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852587 serious Bug #852587 [wader] wader: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Processed: severity of 852594 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852594 serious Bug #852594 [buzztrax] buzztrax: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you

Processed: severity of 852583 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852583 serious Bug #852583 [bluez] bluez: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Processed: severity of 852560 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852560 serious Bug #852560 [golang-github-shirou-gopsutil] golang-github-shirou-gopsutil: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping

Processed: severity of 852590 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852590 serious Bug #852590 [ltspfs] ltspfs: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Processed: severity of 852592 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852592 serious Bug #852592 [bilibop] bilibop: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Processed: severity of 852593 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852593 serious Bug #852593 [hwinfo] hwinfo: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Processed: severity of 852580 is important

Processing commands for cont...@bugs.debian.org: > severity 852580 important Bug #852580 [udev] udev: Drop /sbin/udevadm compat symlink Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 852580:

Processed: severity of 852585 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852585 serious Bug #852585 [sg3-utils] sg3-utils: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you

Processed: severity of 852589 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852589 serious Bug #852589 [ovirt-guest-agent] ovirt-guest-agent: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please

Processed: severity of 852580 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852580 serious Bug #852580 [udev] udev: Drop /sbin/udevadm compat symlink Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if

Processed: severity of 852564 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852564 serious Bug #852564 [cloud-init] cloud-init: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you

Processed: severity of 852575 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852575 serious Bug #852575 [powerpc-utils] powerpc-utils: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me

Processed: severity of 852569 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852569 serious Bug #852569 [cloud-initramfs-tools] cloud-initramfs-tools: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here.

Processed: severity of 852571 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852571 serious Bug #852571 [open-infrastructure-system-boot] open-infrastructure-system-boot: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping

Processed: severity of 852578 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852578 serious Bug #852578 [scsitools] scsitools: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you

Processed: severity of 852563 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852563 serious Bug #852563 [ipheth] ipheth: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Processed: severity of 852573 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852573 serious Bug #852573 [magnum] magnum: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Processed: severity of 852572 is serious

Processing commands for cont...@bugs.debian.org: > # We will remove the symlink soon, so bumping the severity. > severity 852572 serious Bug #852572 [s390-tools] s390-tools: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you

Processed: severity of 852561 is serious

Processing commands for cont...@bugs.debian.org: > #We will remove the symlink soon, so bumping the severity. > severity 852561 serious Bug #852561 [dahdi-tools] dahdi-tools: Update udevadm path Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if

Bug#874693: breaks other packages

Package: gjs Version: 1.49.92-1 Severity: serious The version from experimental apparently breaks other packages like gnome-weather: [14:29:37] (org.gnome.Weather.Application:3731): Gjs-CRITICAL **: JS ERROR: SyntaxError: redeclaration of let copyright @

Bug#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

On Mon, 28 Aug 2017 20:39:29 +0100 James Cowgill wrote: > Hi, > > On 28/08/17 19:57, Anton Gladky wrote: > > Thanks all for discussion, explanations and investigations! > > > > @Rene, I propose to close this bug or to wait till upload of libreoffice. > > > > Next time, when the new coinutils

Bug#874656: libegl1-mesa: Makes team fortress 2 crash the entire machine

On 08.09.2017 16:48, Salvo Tomaselli wrote: > Package: libegl1-mesa > Version: 17.2.0-2 > Severity: grave > Justification: causes non-serious data loss > > Dear Maintainer, > > after the upgrade, trying to play team fortress 2 causes the machine to get > stuck after a few seconds of playing. >

Bug#874688: libpsl FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 8046: ordinal not in range(128)

Source: libpsl Version: 0.18.0-3 Severity: serious Tags: patch Hi Daniel, your -3 upload switching to python3 made libpsl FTBFS on all architectures. Since building libpsl is important to me, I came up with the attached patch to make it build again. It bypasses any locale settings and forces the

Bug#874621: screen lock cannot be unlocked in vnc session

On 09/08/2017 01:39 PM, Simon McVittie wrote: > You might also be able to use loginctl to list sessions, then something > like "loginctl unlock-session 42" to unlock your session. no, that did not work after I got locked in for the 3rd time. I was able to lock and unlock manually, but the problem

Bug#874220: openni2 mustn't build with NEON on armel/armhf

Hi Adrian, Thanks for tagging "mrpt" here! Is there any expected action on our side? Should we disable linking against openni2 in armhf in the meanwhile... or it's better to wait for this bug to be solved? It actually blocks mrpt to get into testing... Cheers, On Mon, Sep 4, 2017 at 12:45 PM,

Bug#874679: libssh2: Fails to build on stable if libssl-dev is installed

Source: libssh2 Version: 1.7.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) libssh2 fails to build on stable if libssl-dev is installed: - libtool: compile: gcc -DHAVE_CONFIG_H -I../include -I../src -Wdate-time

Bug#874521:

So I can't reproduce this. More details will be needed. If you can please file a bug upstream (https://github.com/hughsie/fwupd/) it would be best for upstream to work on solving this. The following items are needed: 1. /usr/lib/fwupd/fwupd -v output 2. Information about the hardware

Bug#870304: marked as done (yabause FTBFS with buster libgtkglext1-dev)

Your message dated Fri, 08 Sep 2017 13:51:20 + with message-id and subject line Bug#870304: fixed in yabause 0.9.14-2.1 has caused the Debian Bug report #870304, regarding yabause FTBFS with buster libgtkglext1-dev to be marked as done. This means that

Bug#874656: libegl1-mesa: Makes team fortress 2 crash the entire machine

Package: libegl1-mesa Version: 17.2.0-2 Severity: grave Justification: causes non-serious data loss Dear Maintainer, after the upgrade, trying to play team fortress 2 causes the machine to get stuck after a few seconds of playing. Seemingly, downgrading fixes the issues. I'm opening this at

Processed: cloning 853598, reassign -1 to xmltooling ..., block 853598 with -1

Processing commands for cont...@bugs.debian.org: > clone 853598 -1 Bug #853598 [src:opensaml2] opensaml2: ftbfs with GCC-7 Bug 853598 cloned as bug 874654 > reassign -1 xmltooling Bug #874654 [src:opensaml2] opensaml2: ftbfs with GCC-7 Bug reassigned from package 'src:opensaml2' to 'xmltooling'.

Bug#867889: marked as done (jarjar FTBFS: java.lang.RuntimeException: RemappingClassAdapter is deprecated, use ClassRemapper instead)

Your message dated Fri, 08 Sep 2017 12:49:54 + with message-id and subject line Bug#867889: fixed in jarjar 1.4+svn142-7 has caused the Debian Bug report #867889, regarding jarjar FTBFS: java.lang.RuntimeException: RemappingClassAdapter is deprecated, use

Processed: Pending fixes for bugs in the jarjar package

Processing commands for cont...@bugs.debian.org: > tag 867889 + pending Bug #867889 [src:jarjar] jarjar FTBFS: java.lang.RuntimeException: RemappingClassAdapter is deprecated, use ClassRemapper instead Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Bug#867889: Pending fixes for bugs in the jarjar package

tag 867889 + pending thanks Some bugs in the jarjar package are closed in revision 16b243cd48f9f76e97c2dc383649425346642c65 in branch 'master' by Emmanuel Bourg The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/jarjar.git/commit/?id=16b243c Commit message: Revert to

Bug#871186: marked as done (ibus-skk: FTBFS with vala 0.36)

Your message dated Fri, 08 Sep 2017 11:05:16 + with message-id and subject line Bug#871186: fixed in ibus-skk 1.4.2-1.1 has caused the Debian Bug report #871186, regarding ibus-skk: FTBFS with vala 0.36 to be marked as done. This means that you claim that

Bug#874621: screen lock cannot be unlocked in vnc session

On 09/08/2017 01:46 PM, Simon McVittie wrote: > On Fri, 08 Sep 2017 at 12:22:37 +0530, Pirate Praveen wrote: >> package: gnome-shell >> version: 3.22.3-3 >> >> This broke after a dist upgrade in sid yesterday. > What did you upgrade? Please look at /var/log/apt/*.log*. gnome-shell > hasn't been

Processed: tagging 874614, severity of 874614 is normal

Processing commands for cont...@bugs.debian.org: > tags 874614 - patch Bug #874614 [libblockdev2] Please demote some packages from dependency to recommendation Removed tag(s) patch. > severity 874614 normal Bug #874614 [libblockdev2] Please demote some packages from dependency to recommendation

Processed: tagging 857377

Processing commands for cont...@bugs.debian.org: > tags 857377 + pending Bug #857377 [kopano-dev] kopano-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/x86_64-linux-gnu/libmapi.so Ignoring request to alter tags of bug #857377 to the same tags previously set > thanks Stopping

Processed: tagging 861775

Processing commands for cont...@bugs.debian.org: > tags 861775 + pending Bug #861775 [kopanocore] kopanocore: src:kopanocore has a harcoded php7.0-mapi binary Ignoring request to alter tags of bug #861775 to the same tags previously set > thanks Stopping processing here. Please contact me if

Processed: tagging 863958

Processing commands for cont...@bugs.debian.org: > tags 863958 + pending Bug #863958 [kopano-server] kopano-server: postrm script still refers to zarafa-server Ignoring request to alter tags of bug #863958 to the same tags previously set > thanks Stopping processing here. Please contact me if

Processed: tagging 865320

Processing commands for cont...@bugs.debian.org: > tags 865320 + pending Bug #865320 [src:kopanocore] kopanocore FTBFS: error: expected class-name before '{' token Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 865320:

Processed: tagging 871276

Processing commands for cont...@bugs.debian.org: > tags 871276 + pending Bug #871276 [kopano-libs] kopano-libs: requires rebuild against GCC 7 and symbols/shlibs bump Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 871276:

Bug#874621: screen lock cannot be unlocked in vnc session

On Fri, 08 Sep 2017 at 12:22:37 +0530, Pirate Praveen wrote: > package: gnome-shell > version: 3.22.3-3 > > This broke after a dist upgrade in sid yesterday. What did you upgrade? Please look at /var/log/apt/*.log*. gnome-shell hasn't been updated in sid since April, so unless your sid

Bug#874621: screen lock cannot be unlocked in vnc session

On Fri, 08 Sep 2017 at 12:22:37 +0530, Pirate Praveen wrote: > Now I have to kill gnome-shell and use metacity to not lose the session > or kill vncserver and restart session. You might also be able to use loginctl to list sessions, then something like "loginctl unlock-session 42" to unlock your

Bug#873888: marked as done (dcl: FTBFS when not building dcl-f77-docs)

Your message dated Fri, 08 Sep 2017 07:04:14 + with message-id and subject line Bug#873888: fixed in dcl 7.2.3-2 has caused the Debian Bug report #873888, regarding dcl: FTBFS when not building dcl-f77-docs to be marked as done. This means that you claim

Bug#874621: screen lock cannot be unlocked in vnc session

package: gnome-shell version: 3.22.3-3 severity: grave justification: makes it unusable and it is a regression This broke after a dist upgrade in sid yesterday. It was working earlier. The password screen automatically gets submitted before completion of password entry every few seconds. I

Bug#874009: rkt FTBFS: cannot find package "github.com/aws/aws-sdk-go/private/signer/v4"

Dear maintainer, When I update aws-sdk-go[1], I know rkt upstream is still using the old version. But we need go forward with updating aws-sdk-go library since it's too old. I have prepare a patch to fix this FTBFS[1], but I don't use rkt and I'm not sure if the patch really works(I don't have