Bug#902470: influxdb-python: FTBFS in buster/sid (failing tests)

Control: tags -1 help Hi, the diff can be found here 'foo,hello=there 0="1",1=1i,2=1.1 0\nfoo,hello=there 0="2",1=2i,2=2.2 36000\n' != 'foo,hello=there 0="1",1=1i,2=1.111 0\nfoo,hello=there 0="2",1=2i,2=2.222 36000\n'

Processed: Re: influxdb-python: FTBFS in buster/sid (failing tests)

Processing control commands: > tags -1 help Bug #902470 [src:influxdb-python] influxdb-python: FTBFS in buster/sid (failing tests) Added tag(s) help. -- 902470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#902774: jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 CVE-2018-12536 CVE-2018-12538

Processing control commands: > retitle -1 jetty9: CVE-2018-12536 Bug #902774 [jetty9] jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2018-12536 Changed Bug title to 'jetty9: CVE-2018-12536' from 'jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2018-12536'. > retitle 902953 jetty9: CVE-2017-7656 CVE-2017-7657

Processed: Re: Bug#902774: jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 CVE-2018-12536 CVE-2018-12538

Processing control commands: > retitle -1 jetty9: CVE-2018-12536 Bug #902774 [jetty9] jetty9: CVE-2018-12536 Ignoring request to change the title of bug#902774 to the same title > retitle 902953 jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 Bug #902953 [jetty9] jetty9: CVE-2017-7656

Bug#902774: jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 CVE-2018-12536 CVE-2018-12538

Control: retitle -1 jetty9: CVE-2018-12536 Control: retitle 902953 jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 Hi After discussion with Emmanuel, CVE-2017-7656, CVE-2017-7657 and VE-2017-7658 are fixed all in 9.2.25-1 with https://github.com/eclipse/jetty.project/commit/a285deea . So

Bug#902466: marked as done (golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid (failing tests))

Your message dated Wed, 04 Jul 2018 03:34:02 + with message-id and subject line Bug#902466: fixed in golang-github-grpc-ecosystem-go-grpc-prometheus 1.2.0-1 has caused the Debian Bug report #902466, regarding golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid (failing

Processed: tagging 902467

Processing commands for cont...@bugs.debian.org: > tags 902467 + upstream Bug #902467 [src:golang-github-kardianos-osext] golang-github-kardianos-osext: FTBFS in buster/sid (failing tests) Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: bug 902467 is forwarded to https://github.com/kardianos/osext/issues/21

Processing commands for cont...@bugs.debian.org: > forwarded 902467 https://github.com/kardianos/osext/issues/21 Bug #902467 [src:golang-github-kardianos-osext] golang-github-kardianos-osext: FTBFS in buster/sid (failing tests) Set Bug forwarded-to-address to

Processed: retitle 866371

Processing commands for cont...@bugs.debian.org: > retitle 866371 FP register corruption on ppc64el with lock elision Bug #866371 [src:linux] openldap FTBFS on ppc64{,el}: slapd-mtread failed (139) Bug #866122 [src:linux] test060-mt-hot failing on ppc64el buildd Changed Bug title to 'FP register

Processed: Re: Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid

Processing control commands: > found -1 4.17.3-1 Bug #866122 [src:linux] test060-mt-hot failing on ppc64el buildd Bug #866371 [src:linux] openldap FTBFS on ppc64{,el}: slapd-mtread failed (139) Marked as found in versions linux/4.17.3-1. Marked as found in versions linux/4.17.3-1. -- 866122:

Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid

Control: found -1 4.17.3-1 Hi, On Mon, Jul 02, 2018 at 08:42:45PM -0700, Ryan Tandy wrote: However it looks like it might be resolved with the kernel in unstable. I will run some more iterations and let you know. The issue still reproduces with stretch userland and the current unstable

Processed: Re: Bug#902946: Fails to load autofs module through autofs4 alias

Processing control commands: > notfound -1 239-1 Bug #902946 [systemd] Fails to load autofs module through autofs4 alias No longer marked as found in versions systemd/239-1. > found -1 238-5 Bug #902946 [systemd] Fails to load autofs module through autofs4 alias Marked as found in versions

Bug#902946: Fails to load autofs module through autofs4 alias

Control: notfound -1 239-1 Control: found -1 238-5 Control: found -1 239-3 On Tue, 2018-07-03 at 23:42 +0200, Michael Biebl wrote: > Am 03.07.2018 um 23:10 schrieb Ben Hutchings: > > On Tue, 2018-07-03 at 23:08 +0200, Michael Biebl wrote: > > > Am 03.07.2018 um 20:11 schrieb Ben Hutchings: > > >

Bug#902962: mandelbulber2: Missing Replaces: header

Package: mandelbulber2 Version: 2.08.3-1+b1 Severity: serious Justification: file conflicts Unpacking mandelbulber2 (2.13.2-3) over (2.08.3-1+b1) ... dpkg: error processing archive /var/cache/apt/archives/mandelbulber2_2.13.2-3_amd64.deb (--unpack): trying to overwrite

Bug#902197: mozjs52 FTBFS with icu 60.2

On Wed, 04 Jul 2018 at 00:14:25 +0100, Simon McVittie wrote: > Having fixed that, I get a different FTBFS This is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902961

Processed: tagging 902961

Processing commands for cont...@bugs.debian.org: > tags 902961 + ftbfs help Bug #902961 [src:mozjs52] mozjs52: FTBFS in recent unstable: ReserveProcessExecutableMemory() fails during tests Added tag(s) help and ftbfs. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#902961: mozjs52: FTBFS in recent unstable: ReserveProcessExecutableMemory() fails during tests

Source: mozjs52 Version: 52.3.1-8 Severity: serious Justification: fails to build from source (but built successfully in the past) (X-Debbugs-Cc to contributors to #897178, to which this seems related, and #902197) After fixing #902197, the mozjs52 build-time tests failed on the amd64 Debian

Processed: Re: Bug#902197: mozjs52 FTBFS with icu 60.2

Processing control commands: > tags -1 + patch Bug #902197 [src:mozjs52] mozjs52 FTBFS with icu 60.2 Added tag(s) patch. -- 902197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#902197: mozjs52 FTBFS with icu 60.2

Control: tags -1 + patch On Sat, 23 Jun 2018 at 16:33:40 +0100, Simon McVittie wrote: > On Sat, 23 Jun 2018 at 12:52:01 +0300, Adrian Bunk wrote: > > make[3]: *** No rule to make target 'ParagraphLayout.ao', needed by > > '../lib/libiculx.a'. Stop. > > It looks as though Ubuntu might have a

Bug#899693: marked as done (sunpinyin: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

Your message dated Tue, 03 Jul 2018 22:20:35 + with message-id and subject line Bug#899693: fixed in sunpinyin 3.0.0~rc1+ds1-1 has caused the Debian Bug report #899693, regarding sunpinyin: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org to be marked as done. This means

Processed: severity of 901404 is serious, severity of 901405 is serious

Processing commands for cont...@bugs.debian.org: > severity 901404 serious Bug #901404 [systemd-shim] systemd-shim: Please dpkg-divert the dbus services you want dbus-activatable Severity set to 'serious' from 'important' > severity 901405 serious Bug #901405 [systemd-shim] systemd-shim: Please

Bug#902959: pluginhook: switch Build-Depends to golang-golang-x-crypto-dev

Source: pluginhook Version: 0~20150216.0~a320158-2 Severity: serious Tags: sid buster The transitional package golang-go.crypto-dev is gone. Please adjust the Build-Depends and use golang-golang-x-crypto-dev instead. Andreas

Bug#902958: obfs4proxy: switch Build-Depends to golang-golang-x-crypto-dev

Source: obfs4proxy Version: 0.0.7-3 Severity: serious The transitional package golang-go.crypto-dev is gone. Please adjust the Build-Depends and use golang-golang-x-crypto-dev instead. Andreas

Bug#902957: golang-ed25519-dev: switch Build-Depends to golang-golang-x-crypto-dev

Source: golang-ed25519-dev Version: 0~20140907.d2b94fd-3 Severity: serious The transitional package golang-go.crypto-dev is gone. Please adjust the Build-Depends and use golang-golang-x-crypto-dev instead. Andreas

Bug#902946: Fails to load autofs module through autofs4 alias

Am 03.07.2018 um 23:10 schrieb Ben Hutchings: > On Tue, 2018-07-03 at 23:08 +0200, Michael Biebl wrote: >> Am 03.07.2018 um 20:11 schrieb Ben Hutchings: >>> Package: systemd >>> Version: 239-1 >>> Severity: serious >>> >>> Starting with Linux 4.18, the autofs4 kernel module is renamed >>> to

Bug#902946: Fails to load autofs module through autofs4 alias

On Tue, 2018-07-03 at 23:08 +0200, Michael Biebl wrote: > Am 03.07.2018 um 20:11 schrieb Ben Hutchings: > > Package: systemd > > Version: 239-1 > > Severity: serious > > > > Starting with Linux 4.18, the autofs4 kernel module is renamed > > to autofs, but retaining an 'autofs4' alias. > > > >

Bug#902946: Fails to load autofs module through autofs4 alias

Am 03.07.2018 um 20:11 schrieb Ben Hutchings: > Package: systemd > Version: 239-1 > Severity: serious > > Starting with Linux 4.18, the autofs4 kernel module is renamed > to autofs, but retaining an 'autofs4' alias. > > Despite the presence of the alias, systemd fails to load the > autofs

Bug#902943: cryptsetup-initramfs: Encrypted rootfs in LVM is not found after upgrade

On Tue, 03 Jul 2018 at 20:01:02 +0200, doak wrote: > After system upgrade the system is not bootable anymore due the > initramfs is unable to find the "source" for the rootfs and boot > hangs. Not forever, though. It drops to a debug shell after ‘rootdelay’ (default 180) seconds, unless you've

Processed: severity of 898406 is grave

Processing commands for cont...@bugs.debian.org: > severity 898406 grave Bug #898406 [src:flif] flif: CVE-2018-10971 Warning: Unknown package 'src:flif' Severity set to 'grave' from 'important' Warning: Unknown package 'src:flif' > thanks Stopping processing here. Please contact me if you need

Processed: cloning 902774, retitle 902774 to jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2018-12536 ...

Processing commands for cont...@bugs.debian.org: > clone 902774 -1 Bug #902774 [jetty9] jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 CVE-2018-12536 Bug 902774 cloned as bug 902953 > retitle 902774 jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2018-12536 Bug #902774 [jetty9] jetty9: CVE-2017-7656

Processed: bug 902946 is forwarded to https://github.com/systemd/systemd/issues/9501

Processing commands for cont...@bugs.debian.org: > forwarded 902946 https://github.com/systemd/systemd/issues/9501 Bug #902946 [systemd] Fails to load autofs module through autofs4 alias Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/9501'. > thanks Stopping

Processed: Re: this is a bug

Processing control commands: > severity -1 important Bug #253513 [mailutils] sender (From:) - policy specifies use of /etc/mailname on Debian Severity set to 'important' from 'serious' -- 253513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=253513 Debian Bug Tracking System Contact

Bug#253513: this is a bug

Control: severity -1 important On Wed, 6 Sep 2017 10:52:32 +0100 Daniel Pocock wrote: > > According to policy > > /usr/share/doc/debian-policy/policy.txt.gz > > "Non-conformance with > guidelines denoted by _should_ (or _recommended_) will generally be > considered a bug, but

Bug#902934: [pkg-php-pear] Bug#902934: phpunit: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org

On Tue, Jul 03, 2018 at 07:25:09PM +, Thorsten Glaser wrote: > David Prévot dixit: > > >pkg-php-pear != pkg-php-maint > > But all those Alioth lists no longer exist. This one does, thanks to the lists.alioth.debian.org migration. I do get your messages to the BTS through it.

Processed: reassign 902898 to libreoffice-core, found 902898 in 1:6.1.0~beta2-1

Processing commands for cont...@bugs.debian.org: > reassign 902898 libreoffice-core Bug #902898 [libreoffice] libreoffice: missing versioned dependency to uno-libs3 >= 6.1 Bug reassigned from package 'libreoffice' to 'libreoffice-core'. No longer marked as found in versions

Processed: severity of 902898 is serious ...

Processing commands for cont...@bugs.debian.org: > severity 902898 serious Bug #902898 [libreoffice] libreoffice: missing dependency to uno-libs3 Severity set to 'serious' from 'normal' > retitle 902898 libreoffice: missing versioned dependency to uno-libs3 >= 6.1 Bug #902898 [libreoffice]

Bug#902934: marked as done (phpunit: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org)

Your message dated Tue, 3 Jul 2018 08:56:05 -1000 with message-id <4cffadfb-bb80-082f-9004-477755dd4...@tilapin.org> and subject line [pkg-php-pear] Bug#902934: phpunit: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org has caused the Debian Bug report #902934, regarding phpunit:

Bug#902945: igraph: FTBFS with ARPACK 3.6

Control: forwarded -1 https://github.com/igraph/igraph/issues/1107 Control: tags -1 help Control: tags -1 upstream Hi, thanks for the bug report. I've forwarded the issue upstream. Kind regards Andreas. -- http://fam-tille.de

Processed: Re: Bug#902945: igraph: FTBFS with ARPACK 3.6

Processing control commands: > forwarded -1 https://github.com/igraph/igraph/issues/1107 Bug #902945 [src:igraph] igraph: FTBFS with ARPACK 3.6 Set Bug forwarded-to-address to 'https://github.com/igraph/igraph/issues/1107'. > tags -1 help Bug #902945 [src:igraph] igraph: FTBFS with ARPACK 3.6

Bug#902934: [pkg-php-pear] Bug#902934: phpunit: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org

David Prévot dixit: >pkg-php-pear != pkg-php-maint But all those Alioth lists no longer exist. bye, //mirabilos -- 18:47⎜ well channels… you see, I see everything in the same window anyway 18:48⎜ i know, you have some kind of telnet with automatic pong 18:48⎜ haha, yes :D 18:49⎜

Bug#902632: nvidia-legacy-340xx-kernel-dkms: the compiled module fails to load with error 'Invalid module format'

I also had this bug when upgrading today. I had this in dmesg: module: nvidia: Unknown rela relocation: 4 Possibly some issue with the linker or the elf loader in the newer kernel. Anyway, I just upgraded the kernel to 4.16 and added the correct arg to /etc/defaults/grub and it's working

Bug#902933: marked as done (phpunit : Depends: php-phar-io-version (< 2~~) but 2.0.0-1 is to be installed)

Your message dated Tue, 03 Jul 2018 19:03:59 + with message-id and subject line Bug#902933: fixed in phpunit 7.2.6-1 has caused the Debian Bug report #902933, regarding phpunit : Depends: php-phar-io-version (< 2~~) but 2.0.0-1 is to be installed to be marked as done. This means that you

Processed: limit source to phpunit, tagging 902933

Processing commands for cont...@bugs.debian.org: > limit source phpunit Limiting to bugs with field 'source' containing at least one of 'phpunit' Limit currently set to 'source':'phpunit' > tags 902933 + pending Bug #902933 [phpunit] phpunit : Depends: php-phar-io-version (< 2~~) but 2.0.0-1 is

Bug#902947: seafile-daemon and seafile-cli are unusable in 6.2.0

Source: seafile Version: 6.2.0-1 Severity: serious Tags: upstream Justification: Policy 3.5 This bug is mainly to prevent migration of the 6.2.0 package. Upstream is working on removing the ccnet dependency, but right now they've only done that for the non-python parts of the package. --

Bug#902945: igraph: FTBFS with ARPACK 3.6

Source: igraph Version: 0.7.1-2.1 Severity: serious Tags: ftbfs Hi maintainer Since the upload of arpack 3.6.0-1 to unstable, igraph FTBFS [1] with the following test failures: BLAS, LAPACK and ARPACK based functions 191: Basic BLAS functions (igraph_blas_*): ok 192: Dense symmetric

Bug#902946: Fails to load autofs module through autofs4 alias

Package: systemd Version: 239-1 Severity: serious Starting with Linux 4.18, the autofs4 kernel module is renamed to autofs, but retaining an 'autofs4' alias. Despite the presence of the alias, systemd fails to load the autofs module: systemd[1]: Failed to insert module 'autofs4': No such

Bug#902943: cryptsetup-initramfs: Encrypted rootfs in LVM is not found after upgrade

Package: cryptsetup-initramfs Version: 2:2.0.3-4 Severity: critical Justification: breaks the whole system Dear Maintainer, After system upgrade the system is not bootable anymore due the initramfs is unable to find the "source" for the rootfs and boot hangs. Before the upgrade this

Bug#790196: Rasmol needs severe contribution to stay in Debian

On Tue, 2018-07-03 at 15:25 +0100, Carnë Draug wrote: > On 3 July 2018 at 14:59, Andreas Tille wrote: > > Hi, > > > > the bug log of #790196[1] shows that rasmol in its current state > > will > > not be distributable with Buster. Upstream is dead so if we want > > to > > keep it in Debian we

Bug#902934: phpunit: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org

Package: phpunit Version: 7.2.4-1 Severity: serious Justification: Policy 3.3 See #899636 et al. for all the gory details. -- System Information: Debian Release: buster/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100,

Bug#902933: phpunit : Depends: php-phar-io-version (< 2~~) but 2.0.0-1 is to be installed

Package: phpunit Version: 7.2.4-1 Severity: serious Justification: package no longer installable in sid The recent upload of php-phar-io-version broke even the most recent upload of phpunit. -- System Information: Debian Release: buster/sid APT prefers unreleased APT policy: (500,

Bug#902921: boost1.63: FTBFS with python3.7 supported: libs/python/src/converter/builtin_converters.cpp:51:35: error: invalid conversion from 'const void*' to 'void*' [-fpermissive]

Hi, Il 03/07/2018 17:01, Simon McVittie ha scritto:> Similar to #902702, boost1.63 fails to build when binNMU'd against > python3.7. This example build log is from amd64: Thanks for reporting. My feeling here is that it would be advisable to just remove boost1.63 from unstable. No package depends

Bug#902644: upower: Upower breaks power saving settings after upgrade to 0.99.8-1

It worked here. Commenting out this option fixes the bug. Thank you for the solution. Em ter, 3 de jul de 2018 às 11:49, Michael Biebl escreveu: > Hi > > On Thu, 28 Jun 2018 21:55:01 -0300 Adilson dos Santos Dantas > wrote: > > Package: upower > > Version: 0.99.8-1 > > Severity: important > >

Bug#864309: marked as done (pgloader: crashes on startup if libssl1.0.2 is not installed)

Your message dated Tue, 3 Jul 2018 18:26:52 +0200 with message-id <20180703162652.ga3...@msg.df7cb.de> and subject line Re: Bug#864309: pgloader: crashes on startup if libssl1.0.2 is not installed has caused the Debian Bug report #864309, regarding pgloader: crashes on startup if libssl1.0.2 is

Bug#875885: marked as done (netkit-tftp: does not trap ./configure errors)

Your message dated Tue, 03 Jul 2018 16:04:17 + with message-id and subject line Bug#875885: fixed in netkit-tftp 0.17-20 has caused the Debian Bug report #875885, regarding netkit-tftp: does not trap ./configure errors to be marked as done. This means that you claim that the problem has been

Bug#897533: marked as done (sunflow: FTBFS: convert-im6.q16: unable to open file `/tmp/magick-22610UfLlJYiQTV4q': No such file or directory @ error/constitute.c/ReadImage/544.)

Your message dated Tue, 03 Jul 2018 15:49:50 + with message-id and subject line Bug#897533: fixed in sunflow 0.07.2.svn396+dfsg-17 has caused the Debian Bug report #897533, regarding sunflow: FTBFS: convert-im6.q16: unable to open file `/tmp/magick-22610UfLlJYiQTV4q': No such file or

Processed: Bug #897533 in sunflow marked as pending

Processing control commands: > tag -1 pending Bug #897533 [src:sunflow] sunflow: FTBFS: convert-im6.q16: unable to open file `/tmp/magick-22610UfLlJYiQTV4q': No such file or directory @ error/constitute.c/ReadImage/544. Added tag(s) pending. -- 897533:

Bug#897533: Bug #897533 in sunflow marked as pending

Control: tag -1 pending Hello, Bug #897533 in sunflow reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#875885: netkit-tftp: does not trap ./configure errors

On Tue, Jul 03, 2018 at 12:29:00PM +0200, Alberto Gonzalez Iniesta wrote: > Have you tested your assertion? Because if ./configure fails, MCONFIG is > not created and the build (make) fails: That was a general statement. I think it doesn't really matter whether it practically does cause

Bug#902921: boost1.63: FTBFS with python3.7 supported: libs/python/src/converter/builtin_converters.cpp:51:35: error: invalid conversion from 'const void*' to 'void*' [-fpermissive]

Source: boost1.63 Version: 1.63.0+dfsg-1.1 Severity: serious Justification: fails to build from source (but built successfully in the past) Similar to #902702, boost1.63 fails to build when binNMU'd against python3.7. This example build log is from amd64:

Bug#902644: upower: Upower breaks power saving settings after upgrade to 0.99.8-1

Hi On Thu, 28 Jun 2018 21:55:01 -0300 Adilson dos Santos Dantas wrote: > Package: upower > Version: 0.99.8-1 > Severity: important > > Dear Maintainer, > > After upgrading upower to 0.99.8-1, my KDE power saving settings stops > working. > There is no reaction when I unplug and plug back my

Bug#790196: Rasmol needs severe contribution to stay in Debian

On 3 July 2018 at 14:59, Andreas Tille wrote: > Hi, > > the bug log of #790196[1] shows that rasmol in its current state will > not be distributable with Buster. Upstream is dead so if we want to > keep it in Debian we have the option: > >1) Port it to Gtk+ 3 (see porting guide [2]) >2)

Bug#790196: Rasmol needs severe contribution to stay in Debian

Hi, the bug log of #790196[1] shows that rasmol in its current state will not be distributable with Buster. Upstream is dead so if we want to keep it in Debian we have the option: 1) Port it to Gtk+ 3 (see porting guide [2]) 2) Find a Gtk+ 2 replacement for libvte 3) Give up and remove

Bug#897504: fixed in golang-github-hashicorp-go-plugin 0.0~git20170621.5ee1a665-1

found 897504 0.0~git20170621.5ee1a665-1 thanks Hello. I tried to rebuild this package in buster and it failed with the same error initially posted by Lucas Nussbaum: --- FAIL: TestClient_syncStreams (0.10s) rpc_client_test.go:59: bad:

Processed: Re: Bug#897504: fixed in golang-github-hashicorp-go-plugin 0.0~git20170621.5ee1a665-1

Processing commands for cont...@bugs.debian.org: > found 897504 0.0~git20170621.5ee1a665-1 Bug #897504 {Done: Dmitry Smirnov } [src:golang-github-hashicorp-go-plugin] golang-github-hashicorp-go-plugin: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1

Bug#900772: marked as done (cakephp: depends on php-mcrypt which is no longer available in php7.2)

Your message dated Tue, 03 Jul 2018 12:49:05 + with message-id and subject line Bug#900772: fixed in cakephp 2.10.11-1 has caused the Debian Bug report #900772, regarding cakephp: depends on php-mcrypt which is no longer available in php7.2 to be marked as done. This means that you claim

Bug#900399: It's confirmed: memtest86+ can kill lenovo mainboard

Hi, On Wed, Jun 06, 2018 at 03:35:36PM +0600, Сергей Коган wrote: > [...] > It looks like T6x, T400/500, T410/510, T420/520 laptop families could be > affected by this problem. Starting from the T430/530 series, a communication > protocol with the EC was changed - breaking tp_smapi driver and

Bug#871068: marked as done (cbmc: FTBFS: wmm/abstract_event.h:23:7: error: '.abstract_eventt::operation' may be used uninitialized in this function [-Werror=maybe-uninitialized])

Your message dated Tue, 03 Jul 2018 12:20:05 + with message-id and subject line Bug#871068: fixed in cbmc 5.9-1 has caused the Debian Bug report #871068, regarding cbmc: FTBFS: wmm/abstract_event.h:23:7: error: '.abstract_eventt::operation' may be used uninitialized in this function

Bug#875885: netkit-tftp: does not trap ./configure errors

On Fri, Sep 15, 2017 at 05:17:44PM +0200, Helmut Grohne wrote: > Source: netkit-tftp > Version: 0.17-18.1 > Severity: serious > Justification: policy 4.6 > > netkit-tftp's debian/rules does not trap errors from ./configure. In > case ./configure fails, the build continues. This can produces >

Processed: Re: Bug#902900: python3-celery: python3-celery fails to install with Python 3.7

Processing commands for cont...@bugs.debian.org: > found 902900 4.2.0-1 Bug #902900 [python3-celery] python3-celery: python3-celery fails to install with Python 3.7 Marked as found in versions celery/4.2.0-1. > tags 902900 + upstream Bug #902900 [python3-celery] python3-celery: python3-celery

Bug#902900: python3-celery: python3-celery fails to install with Python 3.7

found 902900 4.2.0-1 tags 902900 + upstream forwarded 902900 https://github.com/celery/celery/pull/4852 user debian-pyt...@lists.debian.org usertag 902900 + python3.7 thanks * Antoine R. Dumont [2018-07-03 10:09:56 +0200]: > Package: python3-celery > Version: 4.1.0-4 > Severity: serious >

Bug#902895: marked as done (ant: Automatically setting the value of the javac --release attribute breaks josm build.)

Your message dated Tue, 03 Jul 2018 10:19:04 + with message-id and subject line Bug#902895: fixed in ant 1.10.4-2 has caused the Debian Bug report #902895, regarding ant: Automatically setting the value of the javac --release attribute breaks josm build. to be marked as done. This means

Processed: merge 901919 902891 901919

Processing commands for cont...@bugs.debian.org: > reassign 902868 nvidia-driver Bug #902868 [src:nvidia-graphics-drivers] linux-image-4.16.0-2-amd64 fails to boot Bug reassigned from package 'src:nvidia-graphics-drivers' to 'nvidia-driver'. Ignoring request to alter found versions of bug

Bug#902895: Bug #902895 in ant marked as pending

Control: tag -1 pending Hello, Bug #902895 in ant reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #902895 in ant marked as pending

Processing control commands: > tag -1 pending Bug #902895 [src:ant] ant: Automatically setting the value of the javac --release attribute breaks josm build. Added tag(s) pending. -- 902895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902895 Debian Bug Tracking System Contact

Bug#845786: marked as done (gammaray FTBFS on arm64, armel, mips* and s390x: QFatal in quickinspectortest)

Your message dated Tue, 3 Jul 2018 11:52:38 +0200 with message-id <8f97d421-0329-e1f3-194c-a43e43d75...@debian.org> and subject line Re: gammaray FTBFS on armhf: QFatal in quickinspectortest has caused the Debian Bug report #845786, regarding gammaray FTBFS on arm64, armel, mips* and s390x: QFatal

Bug#891156: Bug #891156 in mutter marked as pending

Control: tag -1 pending Hello, Bug #891156 in mutter reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #891156 in mutter marked as pending

Processing control commands: > tag -1 pending Bug #891156 [src:mutter] mutter: Incomplete debian/copyright? Added tag(s) pending. -- 891156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#902098: marked as done (gammaray: Cannot install gammaray on sid, please rebuild it with qt 5.10)

Your message dated Tue, 03 Jul 2018 08:34:12 + with message-id and subject line Bug#902098: fixed in gammaray 2.9.0-2.1 has caused the Debian Bug report #902098, regarding gammaray: Cannot install gammaray on sid, please rebuild it with qt 5.10 to be marked as done. This means that you

Bug#902409: Bug #902409 in devscripts marked as pending

Control: tag -1 pending Hello, Bug #902409 in devscripts reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #902409 in devscripts marked as pending

Processing control commands: > tag -1 pending Bug #902409 [devscripts] devscripts: CVE-2018-13043 - grep-excuses uses YAML::Syck in a unsafe way Added tag(s) pending. -- 902409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902409 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#902098: gammaray: uploaded

Control: tags 902098 + patch Control: tags 902098 + pending Dear maintainer, I've prepared an NMU for gammaray (versioned as 2.9.0-2.1) and uploaded it to DELAYED/0. Please feel free to tell me if I should delay it longer. Regards. G. diff -Nru gammaray-2.9.0/debian/changelog

Processed: gammaray: uploaded

Processing control commands: > tags 902098 + patch Bug #902098 [gammaray] gammaray: Cannot install gammaray on sid, please rebuild it with qt 5.10 Added tag(s) patch. > tags 902098 + pending Bug #902098 [gammaray] gammaray: Cannot install gammaray on sid, please rebuild it with qt 5.10 Added

Bug#901712: marked as done (linux: FTBFS when built with dpkg-buildpackage -A (needs bison))

Your message dated Tue, 03 Jul 2018 08:10:29 + with message-id and subject line Bug#901712: fixed in linux 4.17.3-1 has caused the Debian Bug report #901712, regarding linux: FTBFS when built with dpkg-buildpackage -A (needs bison) to be marked as done. This means that you claim that the

Bug#902901: FTBFS: Tests fail

Source: haskell-polynomial Version: 0.7.3-3 Severity: serious Tags: upstream ftbfs Forwarded: https://github.com/mokus0/polynomial/issues/13 $ ./dist/build/polynomial-test/polynomial-test --test-seed 1421927705 -t chebyshevFit Math.Polynomial.Chebyshev: chebyshevFit: sane (Double): [OK,

Bug#875400: marked as done (gammaray: B-D on qt3d-assimpsceneio-plugin which was removed)

Your message dated Tue, 3 Jul 2018 10:08:59 +0200 with message-id and subject line Re: gammaray: B-D on qt3d-assimpsceneio-plugin which was removed has caused the Debian Bug report #875400, regarding gammaray: B-D on qt3d-assimpsceneio-plugin which was removed to be marked as done. This means

Bug#864825: gammaray: crashes target program on attach

Control: severity -1 important Hello, can you please try again with the new gammaray in sid? (it will build in a few hours) please set back the severity to serious if you still experience this crash thanks! Gianfranco

Processed: gammaray: crashes target program on attach

Processing control commands: > severity -1 important Bug #864825 [gammaray] gammaray: crashes target program on attach Severity set to 'important' from 'grave' -- 864825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864825 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#902900: python3-celery: python3-celery fails to install with Python 3.7

Package: python3-celery Version: 4.1.0-4 Severity: serious Hello, Setting up python3-celery (4.2.0-1) ... File "/usr/lib/python3/dist-packages/celery/backends/redis.py", line 22 from . import async, base ^ SyntaxError: invalid syntax File

Bug#875885: netkit-tftp: does not trap ./configure errors

Hello, Raphael. Dead upstream requires few updates to a package. Anyway, I was just looking into that now. Regards, Alberto On Tue, Jul 03, 2018 at 09:44:46AM +0200, Raphael Hertzog wrote: > Hello Alberto, > > it's been 8 years that you haven't touched netkit-tftp and the package > has been

Bug#889048: Votre boîte aux lettres est

Votre boîte aux lettres est pleine et doit être validée pour éviter la désactivation. Cliquez sur le lien ci-dessous pour éviter que votre compte ne soit désactivé. Cliquez ici Support Zimbra / Webmail

Bug#875885: netkit-tftp: does not trap ./configure errors

Hello Alberto, it's been 8 years that you haven't touched netkit-tftp and the package has been removed from Debian testing due to the bug I'm replying to. Can you take care of fixing the bug and/or properly orphaning the package if you are no longer interested in it? Regards, On Fri, 15 Sep

Bug#860064: 8.11 update breaks dnsmasq

Hi, The Debian 8.11 update (20180623) included the problematic version of dns-root-data. Hence dnsmasq can not be started if the init.d script is not patched. Regards, Henrik