Processed: node-webpack-sources FTBFS with node-source-map 0.7.0+dfsg-1

Processing control commands: > forwarded -1 https://github.com/webpack/webpack-sources/issues/34 Bug #46 [node-webpack-sources] node-webpack-sources FTBFS with node-source-map 0.7.0+dfsg-1 Set Bug forwarded-to-address to 'https://github.com/webpack/webpack-sources/issues/34'. > tag -1 help

Bug#888846: node-webpack-sources FTBFS with node-source-map 0.7.0+dfsg-1

Package: node-webpack-sources Version: 1.0.1-1 Severity: serious Control: forwarded -1 https://github.com/webpack/webpack-sources/issues/34 Control: tag -1 help With the last upload of node-source-map, node-webpack-sources has 2 tests failing and hence FTBFS. 0.7 has many breaking changes

Processed: Re: Not in python-tackerclient

Processing commands for cont...@bugs.debian.org: > forwarded 888080 https://github.com/python-cmd2/cmd2/issues/230 Bug #888080 [python-cmd2] python-tackerclient FTBFS: AttributeError: 'module' object has no attribute 'exceptions' Set Bug forwarded-to-address to

Bug#885136: 4digits: Depends on unmaintained pygtk

On Tue, Jan 30, 2018 at 4:51 AM, Pan Yongzhi wrote: > I have updated the code to use gobject > (https://github.com/fossilet/4digits/commit/ffc2e3fe55ca73335e12b0ded42a52d21e555e9e), > though not yet released a version. How should I update it? Am I supposed to > release a new

Processed: Re: dnscrypt-proxy: upstream gone, new package

Processing control commands: > severity -1 minor Bug #11 [src:dnscrypt-proxy] dnscrypt-proxy: upstream gone, new package Severity set to 'minor' from 'serious' -- 11: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=11 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#887323: dewalls i386 test failure

On 2018-01-30 06:48 +, Philip Schuchardt wrote: > I know I’ve been dragging my feet on this. Let’s see if I can figure this out, > this week. I fished out an old netbook which is actually i386. And installed an unstable chroot on it (very slowly!) last night. Hopefully this will enable some

Bug#887761: marked as done (user-mode-linux FTBFS with glibc 2.26)

Your message dated Tue, 30 Jan 2018 13:55:49 + with message-id and subject line Bug#887761: fixed in user-mode-linux 4.14-1um-2 has caused the Debian Bug report #887761, regarding user-mode-linux FTBFS with glibc 2.26 to be marked as done. This means that

Bug#888252: marked as pending

tag 888252 pending thanks Hello, Bug #888252 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/python-modules/packages/py-radix.git/commit/?id=f235185 --- commit

Processed: Bug#888252 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 888252 pending Bug #888252 [src:py-radix] py-radix: Incomplete debian/copyright? Ignoring request to alter tags of bug #888252 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#888837: spamassassin: sa-update failed, spamd does not start anymore

Package: spamassassin Version: 3.4.1-6+deb9u1 Severity: grave Justification: renders package unusable Dear Maintainer, I enabled CRON=1 in /etc/default/spamassassin, to enable the cron job to automatically update spamassassin's rules. Then I run /etc/cron.daily/spamassassin, which failed with

Bug#888236: [Pkg-privacy-maintainers] Bug#888236: torbrowser-launcher: broken by Tor Browser 7.5: No such file or directory: '.../Docs/sources/versions'

On 2018-01-30 23:53:47, Roger Shimizu wrote: > On Tue, Jan 30, 2018 at 4:13 PM, intrigeri wrote: >> Antoine Beaupre: >>> This bug makes torbrowser-launcher completely unusable on Debian >>> stretch, as soon as the browser is updated (as it should). >> >>> What's expected

Bug#888252: marked as done (py-radix: Incomplete debian/copyright?)

Your message dated Tue, 30 Jan 2018 15:11:28 + with message-id and subject line Bug#888252: fixed in py-radix 0.10.0-2 has caused the Debian Bug report #888252, regarding py-radix: Incomplete debian/copyright? to be marked as done. This means that you

Bug#888236: [Pkg-privacy-maintainers] Bug#888236: torbrowser-launcher: broken by Tor Browser 7.5: No such file or directory: '.../Docs/sources/versions'

On Wed, Jan 31, 2018 at 12:55 AM, Antoine Beaupré wrote: > On 2018-01-30 23:53:47, Roger Shimizu wrote: >> On Tue, Jan 30, 2018 at 4:13 PM, intrigeri wrote: >>> Antoine Beaupre: This bug makes torbrowser-launcher completely unusable on Debian

Processed: Fixing up the title for #253513

Processing commands for cont...@bugs.debian.org: > retitle 253513 sender (From:) - policy specifies use of /etc/mailname on > Debian Bug #253513 [mailutils] sender (From:) - policy specifies use of /etc/mailname on Changed Bug title to 'sender (From:) - policy specifies use of /etc/mailname on

Processed: Mark as forwarded

Processing commands for cont...@bugs.debian.org: > forwarded 886018 https://projects.universe-factory.net/issues/251 Bug #886018 [fastd] fastd: FTBFS with libsodium-dev >= 1.0.15 Set Bug forwarded-to-address to 'https://projects.universe-factory.net/issues/251'. > thanks Stopping processing

Bug#882066: ansible-lint fails with ansible 2.4

Yeah, I can confirm this bug too. It is documented here: https://github.com/willthames/ansible-lint/issues/278 If it can help, here's two CI jobs trying to do the same thing, one with the Debian Sid package (fail) and one with the the latest pip version (working): Sid (3.4.13):

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

Your message dated Tue, 30 Jan 2018 17:00:15 + with message-id and subject line Bug#874009: fixed in rkt 1.29.0+dfsg-1 has caused the Debian Bug report #874009, regarding rkt FTBFS: cannot find package "github.com/aws/aws-sdk-go/private/signer/v4" to be

Bug#888837: spamassassin: sa-update failed, spamd does not start anymore

forwarded 37 https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540 thanks We hit this bug this morning with an sa-update. I'd hazard a guess that it's the faulty ruleset described in upstream bug #7540 (fixed less than two hours ago) and will clear up soon, when upstream publishes new

Processed: Re: spamassassin: sa-update failed, spamd does not start anymore

Processing commands for cont...@bugs.debian.org: > forwarded 37 https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540 Bug #37 [spamassassin] spamassassin: sa-update failed, spamd does not start anymore Set Bug forwarded-to-address to

Bug#887866: marked as done (cxref FTBFS on amd64/i386 with glibc 2.26)

Your message dated Tue, 30 Jan 2018 18:19:44 + with message-id and subject line Bug#887866: fixed in cxref 1.6e-3 has caused the Debian Bug report #887866, regarding cxref FTBFS on amd64/i386 with glibc 2.26 to be marked as done. This means that you claim

Bug#853668: closed by Santiago Garcia Mantinan <ma...@debian.org> (Bug#853668: fixed in squid 4.0.21-1~exp5)

Control: clone -1 -2 Control: reopen -2 Control: reassign -2 src:squid3 On Tue, Nov 21, 2017 at 10:03:22AM +, Debian Bug Tracking System wrote: > #853668: squid3: ftbfs with GCC-7 This bug report is very confusing now. src:squid3 FTBFS. The bug is fixed in src:squid/experimental though.

Processed: Re: Bug#853668 closed by Santiago Garcia Mantinan <ma...@debian.org> (Bug#853668: fixed in squid 4.0.21-1~exp5)

Processing control commands: > clone -1 -2 Bug #853668 {Done: Santiago Garcia Mantinan } [src:squid] squid3: ftbfs with GCC-7 Bug 853668 cloned as bug 55 > reopen -2 Bug #55 {Done: Santiago Garcia Mantinan } [src:squid] squid3: ftbfs with GCC-7

Bug#884222: valabind: Fails to build with vala 0.38

On Mon, 22 Jan 2018 06:52:24 -0500 Jeremy Bicha wrote: > https://salsa.debian.org/jbicha/valabind > > Sebastian, could you take a look? > Afaics this looks good and should be uploaded asap. This is the only bit which blocks the vala 0.38 introduction in testing. Regards,

Processed: Re: dietlibc-dev: linux-libc-dev 4.14.2-1 linux/fs.h does not compile with dietlibc-dev linux/types.h

Processing commands for cont...@bugs.debian.org: > block 885961 by 883534 Bug #885961 [src:util-vserver] FTBFS: __kernel_rwf_t in 4.14 kernel headers 885961 was not blocked by any bugs. 885961 was not blocking any bugs. Added blocking bug(s) of 885961: 883534 > thanks Stopping processing here.

Bug#888837: spamassassin: sa-update failed, spamd does not start anymore

Control: severity -1 normal Resetting severity to normal, since we don't ship with updates enabled at all by default. On Tue, Jan 30, 2018 at 09:07:26AM -0700, Will Aoki wrote: > forwarded 37 https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540 > thanks > > We hit this bug this morning

Processed: Re: Bug#888837: spamassassin: sa-update failed, spamd does not start anymore

Processing control commands: > severity -1 normal Bug #37 [spamassassin] spamassassin: sa-update failed, spamd does not start anymore Severity set to 'normal' from 'grave' -- 37: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37 Debian Bug Tracking System Contact

Bug#888860: node-js-beautify: cannot install: wants to overwrite /usr/bin/js-beautify from package jsbeautifier

Package: node-js-beautify Version: 1.7.5+dfsg-1 Severity: serious Justification: Policy 10.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 node-js-beautify tries to overwrite the file /usr/bin/js-beautify, which (when installed) is already provided by the package jsbeautifier. Please see

Processed: severity of 888162 is serious, tagging 888742

Processing commands for cont...@bugs.debian.org: > severity 888162 serious Bug #888162 [cryptsetup] cryptsetup: `loopaesOpen --key-file=-` doesn't read the key from stdin but tries to open key file "./-" Severity set to 'serious' from 'important' > tags 888742 + pending Bug #888742 [cryptsetup]

Bug#888831: [firefox-esr] NS_ERROR_NET_INADEQUATE_SECURITY for https sites - libnss3 dependency

Package: firefox-esr Version: 52.6.0esr-2 Severity: grave --- Please enter the report below this line. --- After upgrading firefox-esr today, it now refuses to access any https sites (e.g. google, bing are affected, including the results from the search bar in firefox itself). I get an error

Processed: jsbeautifier,node-js-beautify: both ship /usr/bin/js-beautify

Processing control commands: > found -1 1.6.4-6 Bug #888903 [jsbeautifier,node-js-beautify] jsbeautifier,node-js-beautify: both ship /usr/bin/js-beautify There is no source info for the package 'node-js-beautify' at version '1.6.4-6' with architecture '' Marked as found in versions

Bug#888903: jsbeautifier,node-js-beautify: both ship /usr/bin/js-beautify

Package: jsbeautifier,node-js-beautify Severity: serious Tags: buster sid User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 1.6.4-6 Control: found -1 1.7.5+dfsg-1 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their

Bug#887744: redeclipse FTBFS with glibc 2.26

I had a similar error compiling lamiae [1] and I solved it by removing the -ffast-math flag from src/makefile I don't know if it would work for you, but the code base is the same, so I assume it might be that. Greetings, Miry [1] https://github.com/Hirato/lamiae

Processed: tagging 888000

Processing commands for cont...@bugs.debian.org: > tags 888000 + fixed-upstream Bug #888000 [src:gnome-shell-extension-disconnect-wifi] Port from deprecated libnm-glib bindings to libnm Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: tagging 887998

Processing commands for cont...@bugs.debian.org: > tags 887998 + fixed-upstream Bug #887998 {Done: Kyle Robbertze } [src:gnome-shell-extension-show-ip] Port from deprecated libnm-glib bindings to libnm Added tag(s) fixed-upstream. > thanks Stopping processing here. Please

Bug#888911: giac test failures with mpfr 4.0.0 on several architectures

Package: src:giac Version: 1.2.3.57+dfsg1-2 Severity: serious Tags: sid buster see https://buildd.debian.org/status/package.php?p=giac failing tests at least on the release architectures amd64 and armhf.

Bug#888912: sagemath test failures with mpfr 4.0.0 and several architectures

Package: src:sagemath Version: 8.2-1 Severity: serious Tags: sid buster see https://buildd.debian.org/status/package.php?p=sagemath=unstable test failures on every architecture.

Bug#866415: marked as done (basemap: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Wed, 31 Jan 2018 06:15:40 +0100 with message-id <44de05b4-3506-27e6-e992-3c344af6b...@debian.org> and subject line Fixed has caused the Debian Bug report #866415, regarding basemap: depends on obsolete python-imaging (replace with python3-pil or python-pil) to be marked as

Bug#880793: closed by Yaroslav Halchenko <deb...@onerussian.com> (Bug#880793: fixed in pymvpa2 2.6.4-1)

On Tue, 30 Jan 2018, Yaroslav Halchenko wrote: > On Tue, 30 Jan 2018, Adrian Bunk wrote: > > Control: reopen -1 > > On Tue, Jan 30, 2018 at 03:39:04AM +, Debian Bug Tracking System wrote: > > >... > > > pymvpa2 (2.6.4-1) unstable; urgency=medium > > >... > > >* debian/rules > > >

Bug#888811: dnscrypt-proxy: upstream gone, new package

Control: severity -1 minor On Mon, 29 Jan 2018 22:51:23 -0800 Brian Clinkenbeard wrote: > Source: dnscrypt-proxy > Severity: serious > Tags: upstream > Justification: fails to build from source (but built successfully in the past) It succeeds to build from

Bug#888236: [Pkg-privacy-maintainers] Bug#888236: torbrowser-launcher: broken by Tor Browser 7.5: No such file or directory: '.../Docs/sources/versions'

On Tue, Jan 30, 2018 at 4:13 PM, intrigeri wrote: > Antoine Beaupre: >> This bug makes torbrowser-launcher completely unusable on Debian >> stretch, as soon as the browser is updated (as it should). > >> What's expected from stable users here? Is there going to be a stable

Bug#888403: ld: /usr/lib/crt0-efi-aarch64.o: relocation R_AARCH64_ABS16 against `EFI_SUBSYSTEM' can not be used when making a shared object

Control: affects 888789 src:u-boot On 2018-01-29, Michael Biebl wrote: > With latest versions of binutils (including 2.30-1), ld fails to > properly link systemd-boot on arm64. ... > /usr/lib/crt0-efi-aarch64.o: relocation R_AARCH64_ABS16 against > `EFI_SUBSYSTEM' can not be used when making a

Bug#888872: exiv2: CVE-2017-12956

Source: exiv2 Version: 0.26-1 Severity: grave Tags: security upstream Forwarded: https://github.com/Exiv2/exiv2/issues/59 Hi, the following vulnerability was published for exiv2, only affecting experimental. CVE-2017-12956[0]: | There is an illegal address access in

Bug#888877: llvm-toolchain-6.0: FTBFS on arm64: /usr/bin/ld.gold: unsupported TLSLE reloc 549 in shared code

Source: llvm-toolchain-6.0 Version: 1:6.0~+rc1-1 Severity: serious Hi, There are old 6.0 binaries lying around from old llvm-toolchain-snapshot versions, so this is RC as those binaries will prevent llvm-toolchain-6.0 from migrating to testing. [ 42%] Linking CXX shared library

Bug#888865: exiv2: CVE-2017-14865

Source: exiv2 Version: 0.26-1 Severity: grave Tags: security upstream Forwarded: https://github.com/Exiv2/exiv2/issues/134 Hi, the following vulnerability was published for exiv2, only affecting the experimental version. CVE-2017-14865[0]: | There is a heap-based buffer overflow in the

Bug#888881: php-mongodb FTBFS with PHP 7.2: error: 'timelib_time {aka struct _timelib_time}' has no member named 'f'

Source: php-mongodb Version: 1.2.3-1 Severity: serious Tags: buster sid https://buildd.debian.org/status/package.php?p=php-mongodb=sid ... /<>/build-7.2/src/BSON/UTCDateTime.c: In function 'php_phongo_utcdatetime_init_from_date': /<>/build-7.2/src/BSON/UTCDateTime.c:145:43: error: 'timelib_time

Bug#888862: exiv2: CVE-2018-5772

Source: exiv2 Version: 0.26-1 Severity: grave Tags: security upstream Hi, the following vulnerability was published for exiv2, and is only affecting experimental version. Marking grave to indicate should not go into unstable (the issue itself does not really warrant grave severity, so if you

Bug#888863: exiv2: CVE-2017-1000127

Source: exiv2 Version: 0.26-1 Severity: grave Tags: security upstream Forwarded: https://github.com/Exiv2/exiv2/issues/176 Hi, the following vulnerability was published for exiv2, only affecting experimental version. CVE-2017-1000127[0]: | Exiv2 0.26 contains a heap buffer overflow in tiff

Bug#888864: exiv2: CVE-2017-1000126

Source: exiv2 Version: 0.26-1 Severity: grave Tags: security upstream Forwarded: https://github.com/Exiv2/exiv2/issues/175 Hi, the following vulnerability was published for exiv2, only affecting experimental version. CVE-2017-1000126[0]: | exiv2 0.26 contains a Stack out of bounds read in webp

Bug#888869: exiv2: CVE-2017-14857

Source: exiv2 Version: 0.26-1 Severity: grave Tags: security upstream Forwarded: https://github.com/Exiv2/exiv2/issues/76 Hi, the following vulnerability was published for exiv2, only affecting the experimental version. CVE-2017-14857[0]: | In Exiv2 0.26, there is an invalid free in the Image

Bug#888874: exiv2: CVE-2017-11553

Source: exiv2 Version: 0.26-1 Severity: grave Tags: security upstream Forwarded: https://github.com/Exiv2/exiv2/issues/54 Hi, the following vulnerability was published for exiv2, only experimental is affected. CVE-2017-11553[0]: | There is an illegal address access in the extend_alias_table

Processed: nodejs: s390x uses illegal instructions on Z10

Processing control commands: > block 886294 with -1 Bug #886294 [release.debian.org] transition: nodejs 886294 was not blocked by any bugs. 886294 was not blocking any bugs. Added blocking bug(s) of 886294: 76 -- 886294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886294 76:

Bug#888876: nodejs: s390x uses illegal instructions on Z10

Source: nodejs Version: 8.9.3~dfsg-11 Severity: serious Control: block 886294 with -1 Hi, Adding a bug against nodejs to track it. The newer version of nodejs in unstable has introduced a regression on Z10 and older processors, as it's using instructions only available on newer processors,

Processed: raising severity of this report

Processing control commands: > severity -1 serious Bug #885407 [cdbs] debhelper class broken in compat level 11 (dh_systemd_enable deprecated) Severity set to 'serious' from 'normal' -- 885407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885407 Debian Bug Tracking System Contact

Bug#888878: fails to restore signed backup

Package: duplicity Version: 0.7.11-1 Severity: grave When trying to restore a signed backup, with -v 8 I get following error Volume was signed by key EE04D0D2B40F856F, not 0xEE04D0D2B40F856F Then duplicity hangs (in a futex system call checked by strace). Command was generated by duply as :

Bug#888880: php-solr FTBFS with PHP 7.2: error: 'ZEND_ACC_CLONE' undeclared here

Source: php-solr Version: 2.4.0-4 Severity: serious Tags: buster sid https://buildd.debian.org/status/package.php?p=php-solr=sid ... In file included from /usr/include/php/20170718/main/php.h:40:0, from /<>/build-7.2/src/php7/php_solr.h:28, from

Bug#888879: rheolef FTBFS on several architectures: test runs forever

Source: rheolef Version: 6.7-5 Severity: serious https://buildd.debian.org/status/package.php?p=rheolef=sid ... mpirun -np 1 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 left >/dev/null 2>/dev/null mpirun -np 2 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2

Processed: Re: Bug#880793 closed by Yaroslav Halchenko <deb...@onerussian.com> (Bug#880793: fixed in pymvpa2 2.6.4-1)

Processing control commands: > reopen -1 Bug #880793 {Done: Yaroslav Halchenko } [src:pymvpa2] pymvpa2 FTBFS on mips64el: ValueError: array is too big; `arr.size * arr.dtype.itemsize` is larger than the maximum possible size. 'reopen' may be inappropriate when a bug has

Bug#880793: closed by Yaroslav Halchenko <deb...@onerussian.com> (Bug#880793: fixed in pymvpa2 2.6.4-1)

Control: reopen -1 On Tue, Jan 30, 2018 at 03:39:04AM +, Debian Bug Tracking System wrote: >... > pymvpa2 (2.6.4-1) unstable; urgency=medium >... >* debian/rules > - run tests under fixed MVPA_SEED=1 to avoid surprises, so should >resolve spurious FTBFS (Closes: #880793)

Bug#888867: exiv2: CVE-2017-14860

Source: exiv2 Version: 0.26-1 Severity: grave Tags: security upstream Forwarded: https://github.com/Exiv2/exiv2/issues/71 Hi, the following vulnerability was published for exiv2, only affecting the experimental version. CVE-2017-14860[0]: | There is a heap-based buffer over-read in the |

Bug#888866: exiv2: CVE-2017-14863

Source: exiv2 Version: 0.26-1 Severity: grave Tags: security upstream Forwarded: https://github.com/Exiv2/exiv2/issues/132 Hi, the following vulnerability was published for exiv2, only affecting the experimental version. CVE-2017-14863[0]: | A NULL pointer dereference was discovered in |

Bug#888873: exiv2: CVE-2017-12955

Source: exiv2 Version: 0.26-1 Severity: grave Tags: security upstream Forwarded: https://github.com/Exiv2/exiv2/issues/58 Hi, the following vulnerability was published for exiv2, only affecting experimental version. CVE-2017-12955[0]: | There is a heap-based buffer overflow in basicio.cpp of

Bug#888890: [libtk-img] Undefined symbol: inflateValidate

Package: libtk-img Version: 1:1.4.7+dfsg-1 Severity: serious Affects: saods9 Dear maintainer, The newly uploaded libtk-img cannot be loaded from within tk: $ wish % package require img::tiff couldn't load file "/usr/lib/tcltk/x86_64-linux-gnu/Img1.4.7/libzlibtcl1.2.11.so":

Bug#888818: [blt] Binary (probably) incompatible with new Tcl/Tk versions (8.6)

Package: tk8.6-blt2.5 Version: 2.5.3+dfsg-3 Severity: serious Affects: skycat Dear maintainer, Somewhere in the upgrade of Tcl/Tk 8.6, BLT got binary incompatible and skycat (which uses BLT) crashes on start. Simply recompiling BLT helps here. Due to the age of the binary package (last upload:

Bug#887696: likwid FTBFS with glibc 2.26

Hi Juhani, Am 29.01.2018 um 16:02 schrieb Juhani Numminen: > > The directory ext/hwloc seems to be an embedded code copy of src:hwloc that > is not listed by security-tracker-team.[1] > > The failing file seems to be for hwloc private use only. Is it possible to > use the package libhwloc-dev

Bug#888236: torbrowser-launcher: broken by Tor Browser 7.5: No such file or directory: '.../Docs/sources/versions'

On 30/01/2018, intrigeri wrote: > Antoine Beaupre: >> This bug makes torbrowser-launcher completely unusable on Debian >> stretch, as soon as the browser is updated (as it should). > >> What's expected from stable users here? Is there going to be a stable >> update for this?

Bug#888199: marked as done (gnome-shell crashes at different circumstances (not usable anymore))

Your message dated Tue, 30 Jan 2018 09:00:43 + with message-id <20180130090043.ga8...@perpetual.pseudorandom.co.uk> and subject line Re: Bug#888199: gnome-shell crashes at different circumstances (not usable anymore) has caused the Debian Bug report #888199, regarding gnome-shell crashes at

Processed: notfixed 146113 in 0.15.1, fixed 146113 in 0.14.2.git20100726-1, notfixed 802509 in 1.60.0+dfsg-1 ...

Processing commands for cont...@bugs.debian.org: > # use fixed versions the bts knows about ... > notfixed 146113 0.15.1 Bug #146113 {Done: Marc Haber } [aide] aide: sorted output There is no source info for the package 'aide' at version '0.15.1' with

Bug#888422: marked as done (Mixing libmpfr4 and libmpfr6 doesn't work well)

on libmpfr6 - multiple precision floating-point computation Closes: 888422 Changes: mpfr4 (4.0.0-6) unstable; urgency=medium . * Update to the 4.0 branch 20180130. * libmpfr6: Break libmpc3 (<< 1.1.0-1~). Closes: #888422. Checksums-Sha1: 3fe3ceb

Processed: found 888199 in 1.50.2-3, tagging 888199

Processing commands for cont...@bugs.debian.org: > found 888199 1.50.2-3 Bug #888199 {Done: Simon McVittie } [libgjs0g] gnome-shell crashes at different circumstances (not usable anymore) Marked as found in versions gjs/1.50.2-3. > tags 888199 - moreinfo Bug #888199 {Done: Simon

Processed: Problem has been fixed

Processing control commands: > fixed -1 1.1.28-1 Bug #887969 [src:nbdkit] nbdkit FTBFS: test failures Marked as fixed in versions nbdkit/1.1.28-1. -- 887969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#888893: password-gorilla: After upgrade, password-gorilla refuses to start with "Couldn't find the package Itcl" message

Hi Tom, I have been able to reproduce your bug. It will be fixed very soon. As a workaround, you can modify the file: /usr/share/password-gorilla/gorilla.tcl exec tclsh8.5 "$0" ${1+"$@"} to exec tclsh "$0" ${1+"$@"} to patch the issue. Regards, Alexandre On Tue, Jan 30, 2018 at 4:24 PM,

Processed: Re: Bug#888877: llvm-toolchain-6.0: FTBFS on arm64: /usr/bin/ld.gold: unsupported TLSLE reloc 549 in shared code

Processing commands for cont...@bugs.debian.org: > forwarded 77 https://bugs.llvm.org/show_bug.cgi?id=36051 Bug #77 [src:llvm-toolchain-6.0] llvm-toolchain-6.0: FTBFS on arm64: /usr/bin/ld.gold: unsupported TLSLE reloc 549 in shared code Set Bug forwarded-to-address to

Bug#888893: password-gorilla: After upgrade, password-gorilla refuses to start with "Couldn't find the package Itcl" message

Package: password-gorilla Version: 1.5.3.7-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? # apt-get update && apt-get upgrade && apt-get dist-upgrade Now, starting password-gorilla gives an error message: Couldn't find the package

Bug#880793: closed by Yaroslav Halchenko <deb...@onerussian.com> (Bug#880793: fixed in pymvpa2 2.6.4-1)

On Tue, 30 Jan 2018, Yaroslav Halchenko wrote: > On Tue, 30 Jan 2018, Adrian Bunk wrote: > > Control: reopen -1 > > On Tue, Jan 30, 2018 at 03:39:04AM +, Debian Bug Tracking System wrote: > > >... > > > pymvpa2 (2.6.4-1) unstable; urgency=medium > > >... > > >* debian/rules > > >

Bug#888877: llvm-toolchain-6.0: FTBFS on arm64: /usr/bin/ld.gold: unsupported TLSLE reloc 549 in shared code

forwarded 77 https://bugs.llvm.org/show_bug.cgi?id=36051 thanks On 30/01/2018 20:57, Emilio Pozuelo Monfort wrote: > Source: llvm-toolchain-6.0 > Version: 1:6.0~+rc1-1 > Severity: serious > > Hi, > > There are old 6.0 binaries lying around from old llvm-toolchain-snapshot > versions, so

Bug#880793: closed by Yaroslav Halchenko <deb...@onerussian.com> (Bug#880793: fixed in pymvpa2 2.6.4-1)

On Tue, 30 Jan 2018, Adrian Bunk wrote: > Control: reopen -1 > On Tue, Jan 30, 2018 at 03:39:04AM +, Debian Bug Tracking System wrote: > >... > > pymvpa2 (2.6.4-1) unstable; urgency=medium > >... > >* debian/rules > > - run tests under fixed MVPA_SEED=1 to avoid surprises, so

Bug#888917: ocrmypdf fails to run it's testsuite

Package: src:ocrmypdf Version: 5.5-2 Severity: serious Tags: sid buster The recent changelog reads: * Disable test suite at package build time. It now takes a prohibitively long time to run, so we are relying on autopkgtest instead. Sorry, but this is one of the most lame excuses I

Processed: Correct the found version

Processing commands for cont...@bugs.debian.org: > notfound 888912 8.2-1 Bug #888912 [src:sagemath] sagemath test failures with mpfr 4.0.0 and several architectures The source 'sagemath' and version '8.2-1' do not appear to match any binary packages No longer marked as found in versions

Bug#888915: didjvu fails its tests in unstable

Package: src:didjvu Version: 0.8.1-2 Severity: serious Tags: sid buster didjvu fails its tests in unstable, cd tests && set -e -x; \ for python in python2.7; do \ $python /usr/bin/nosetests --all-modules --verbose; \ done + python2.7 /usr/bin/nosetests --all-modules --verbose

Bug#888919: healpix-cxx FTBFS on armel: hpxtest runs into 150m timeout

Source: healpix-cxx Version: 3.30.0-7 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=healpix-cxx=armel=3.30.0-7=1516966560=0 ... make check-TESTS make[2]: Entering directory '/<>' make[3]: Entering directory '/<>' E: Build killed with signal TERM after 150 minutes of

Bug#887010: telegram-desktop segfaults on debian buster (amd64) using Gnome3

Hi, 12.01.2018 16:31, Robin пишет: > Versions of packages telegram-desktop depends on: ... > pn libtgvoip1.0 It seems you have no installed package with libtgvoip. This may have led to such crash. > Setting the environment variabel 'XDG_CURRENT_DESKTOP' to 'NONE' solves

Bug#888915: marked as done (didjvu fails its tests in unstable)

Your message dated Wed, 31 Jan 2018 09:09:58 +0200 with message-id <20180131070958.GA8573@localhost> and subject line Re: Bug#888915: didjvu fails its tests in unstable has caused the Debian Bug report #888915, regarding didjvu fails its tests in unstable to be marked as done. This means that you

Bug#887004: marked as done (liborcus: segfaults while running tests)

Your message dated Wed, 31 Jan 2018 07:36:53 + with message-id and subject line Bug#887004: fixed in liborcus 0.13.2-1 has caused the Debian Bug report #887004, regarding liborcus: segfaults while running tests to be marked as done. This means that you

Bug#887969: Problem has been fixed

Control: fixed -1 1.1.28-1 The root cause for this bug had to do with the parameters that libguestfs passes to qemu. A versioned build dependency on libguestfs fixes this. Cheers, -Hilko

Bug#888818: marked as done ([blt] Binary (probably) incompatible with new Tcl/Tk versions (8.6))

Your message dated Tue, 30 Jan 2018 09:34:52 + with message-id and subject line Bug#18: fixed in blt 2.5.3+dfsg-4 has caused the Debian Bug report #18, regarding [blt] Binary (probably) incompatible with new Tcl/Tk versions (8.6) to be marked as

Bug#885136: 4digits: Depends on unmaintained pygtk

Hi Jeremy, I have updated the code to use gobject (https://github.com/fossilet/4digits/commit/ffc2e3fe55ca73335e12b0ded42a52d21e555e9e ), though not yet released a version. How should I update it? Am I

Processed: reopening 886816, reassign 886816 to golang-go.uber-zap-dev ...

Processing commands for cont...@bugs.debian.org: > reopen 886816 Bug #886816 {Done: Debian FTP Masters } [golang-go.uber-zap-dev,zap] golang-go.uber-zap-dev,zap: duplicate packages 'reopen' may be inappropriate when a bug has been closed with a version; all fixed

Bug#887696: likwid FTBFS with glibc 2.26

Hi Adrian, Am 29.01.2018 um 10:55 schrieb Adrian Bunk: > On Mon, Jan 29, 2018 at 10:50:20AM +0100, Christoph Martin wrote: >> So, it should never be tried to be included. Could you please try to >> find out why this is different in your setup? >> >> I can't reproduce this. > > Please send me the

Bug#888816: libdbus-glib-1-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/libdbus-glib-1-dev/AUTHORS

Package: libdbus-glib-1-doc Version: 0.110-1 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#888816: marked as done (libdbus-glib-1-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/libdbus-glib-1-dev/AUTHORS)

Your message dated Tue, 30 Jan 2018 11:19:41 + with message-id and subject line Bug#16: fixed in dbus-glib 0.110-2 has caused the Debian Bug report #16, regarding libdbus-glib-1-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite

Bug#887623: marked as done (fastnetmon FTBFS with libndpi-dev 2.2-1)

Your message dated Tue, 30 Jan 2018 11:50:01 + with message-id and subject line Bug#887623: fixed in fastnetmon 1.1.3+dfsg-5 has caused the Debian Bug report #887623, regarding fastnetmon FTBFS with libndpi-dev 2.2-1 to be marked as done. This means that