Processed: closing 861633

Processing commands for cont...@bugs.debian.org: > close 861633 2.6.1-1 Bug #861633 [nut-hal-drivers] nut-hal-drivers: fails to install in chroot on stretch host Warning: Unknown package 'nut-hal-drivers' There is no source info for the package 'nut-hal-drivers' at version '2.6.1-1' with

Bug#861633: nut-hal-drivers: fails to install in chroot on stretch host

Package: nut-hal-drivers Version: 2.4.3-1.1squeeze2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: close -1 hal/2.6.1-1 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

Bug#860464: Bug#782456: Bug#860463: nodm: Missing handling of plymouth (#782456)

Hi, Simon McVittie wrote: > On Mon, 17 Apr 2017 at 12:05:41 +0200, Niels Thykier wrote: > > For init scripts that can be done by the following shell snippet (just > > before starting the DM): > > > > """ > > if [ -x /bin/plymouth ] ; then > >/bin/plymouth quit > > fi > > """ JFTR: This

Bug#860576: marked as done (wdm: Missing dependency on an X server)

Your message dated Mon, 01 May 2017 23:18:43 + with message-id and subject line Bug#860576: fixed in wdm 1.28-20 has caused the Debian Bug report #860576, regarding wdm: Missing dependency on an X server to be marked as done. This means that you claim

Bug#860464: marked as done (wdm: Missing handling of plymouth (#782456))

Your message dated Mon, 01 May 2017 23:18:43 + with message-id and subject line Bug#860464: fixed in wdm 1.28-20 has caused the Debian Bug report #860464, regarding wdm: Missing handling of plymouth (#782456) to be marked as done. This means that you

Bug#860464: wdm: Missing handling of plymouth (#782456)

Hi, Niels Thykier wrote: > > So I wonder: Shall I upload the fix suggested by Niels anyways? (Not > > untested, but unverified.) > > Laurent, can you help here? Chatted with Laurent on IRC this weekend. He has no idea either. We agreed that since calling "plymouth quit" shouldn't hurt, we'll go

Bug#861388: [Pkg-roundcube-maintainers] Bug#861388: roundcube: CVE-2017-8114: security issue in virtualmin and sasl drivers

Control: tag -1 pending On Fri, 28 Apr 2017 at 12:25:02 +0200, Salvatore Bonaccorso wrote: > the following vulnerability was published for roundcube. > > CVE-2017-8114[0]: > security issue in virtualmin and sasl drivers Thanks, pushed. Sandro, Vincent, would you mind tagging & uploading? --

Processed: Re: [Pkg-roundcube-maintainers] Bug#861388: roundcube: CVE-2017-8114: security issue in virtualmin and sasl drivers

Processing control commands: > tag -1 pending Bug #861388 [src:roundcube] roundcube: CVE-2017-8114: security issue in virtualmin and sasl drivers Added tag(s) pending. -- 861388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861388 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#857937: marked as done (gsequencer: memory leaks while g_timeout_add() function in GUI)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857937: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857937, regarding gsequencer: memory leaks while g_timeout_add() function in GUI to be marked as done.

Bug#857936: marked as done (gsequencer: duplicated flag AGS_MIDI_PARSER_EOT makes header useless)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857936: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857936, regarding gsequencer: duplicated flag AGS_MIDI_PARSER_EOT makes header useless to be marked as

Bug#857910: marked as done (gsequencer: GObject::dispose() is not implemented)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857910: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857910, regarding gsequencer: GObject::dispose() is not implemented to be marked as done. This means

Bug#857935: marked as done (gsequencer: SIGSEGV as doing NULL pointer dereference as restoring AgsFFPlayer)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857935: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857935, regarding gsequencer: SIGSEGV as doing NULL pointer dereference as restoring AgsFFPlayer to

Bug#857931: marked as done (gsequencer: AgsSynth possible division by zero by oscillator)

Your message dated Mon, 01 May 2017 21:03:50 + with message-id and subject line Bug#857931: fixed in gsequencer 0.8.0-1 has caused the Debian Bug report #857931, regarding gsequencer: AgsSynth possible division by zero by oscillator to be marked as done.

Processed: Re: Bug#861218: libgssapi-krb5-2: soname-independent files in shared library package (policy 8.2)

Processing control commands: > severity -1 normal Bug #861218 [libgssapi-krb5-2] libgssapi-krb5-2: soname-independent files in shared library package (policy 8.2) Severity set to 'normal' from 'serious' -- 861218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861218 Debian Bug Tracking

Bug#861218: libgssapi-krb5-2: soname-independent files in shared library package (policy 8.2)

control: severity -1 normal Will remove this file early in buster.

Bug#860247: marked as done (umockdev FTBFS on arm64/mips*/s390x: test-umockdev.c:1939:t_testbed_proc: assertion failed: (g_str_has_prefix(contents, "processor")))

Your message dated Mon, 1 May 2017 21:38:44 +0200 with message-id <20170501193844.GA1099@donald> and subject line Re: Bug#860247: umockdev FTBFS on arm64/mips*/s390x: test-umockdev.c:1939:t_testbed_proc: assertion failed: (g_str_has_prefix(contents, "processor")) has caused the Debian Bug report

Processed: Re: Bug#861567: sphinx: 1.5.3+ breaks src:dask build

Processing control commands: > reassign -1 src:dask 0.12.0-1 Bug #861567 [src:sphinx] sphinx: 1.5.3+ breaks src:dask build Bug reassigned from package 'src:sphinx' to 'src:dask'. No longer marked as found in versions sphinx/1.5.5-1. Ignoring request to alter fixed versions of bug #861567 to the

Bug#861567: sphinx: 1.5.3+ breaks src:dask build

Control: reassign -1 src:dask 0.12.0-1 Control: severity -1 important Control: tags -1 +patch Hi, On Sun, Apr 30, 2017 at 07:31:26PM +, Gianfranco Costamagna wrote: > Hello, I'm not sure if this is a problem in sphinx or not, > I noticed this failure on src:dask in Ubuntu, and it is >

Bug#860479: [ovs-dev] Bug#860479: openvswitch-datapath-dkms (and openvswitch-datapath-source) fail compiling on fresh install of 7.11

On Mon, Apr 17, 2017 at 07:04:12PM +0300, Bogdan Ilisei wrote: > Package: openvswitch-datapath-dkms > Version: 1.4.2+git20120612-9.1~deb7u1.1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Installing openvswitch-datapath-dkms (OR openvswitch-datapath-source)

Bug#860710: [pkg-go] Bug#860710: golang-google-api: FTBFS on i386: dh_auto_test

Am 01.05.2017 um 17:06 schrieb Roger Shimizu: On Mon, 1 May 2017 16:07:07 +0200 "Dr. Tobias Quathamer" wrote: This is not correct. Unblocks are never triggered automatically. You always need to file an unblock request. See this mail for more details:

Bug#860710: [pkg-go] Bug#860710: golang-google-api: FTBFS on i386: dh_auto_test

On Mon, 1 May 2017 16:07:07 +0200 "Dr. Tobias Quathamer" wrote: > This is not correct. Unblocks are never triggered automatically. You > always need to file an unblock request. > > See this mail for more details: >

Bug#861612: Bug#534058: Fenix build-depends not available on amd64

On Tue, Feb 28, 2017 at 08:38:52PM +0200, Adrian Bunk wrote: > Since pixbros and pixfrogger are the only 2 packages in Debian with > this problem,[1] what about simply making them binary-any with an > architecture list of all 32bit architectures? CC'd to the CC-list from the thread about which

Bug#861313: fixed in linux 3.16.43-2

Hi, the update indeed fixes the issue. Thanks! Cheers, Stefan On 04/30/2017 01:36 PM, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the src:linux package: > > #861313: kernel BUG with kvm > > It has been closed by Ben

Bug#861614: rzip: CVE-2017-8364

Source: rzip Version: 2.1-1 Severity: grave Tags: security upstream Justification: user security hole Hi, the following vulnerability was published for rzip, filled with RC severity due to the heap overflow write, but no further investigation done so far. CVE-2017-8364[0]: | The read_buf

Processed: Re: Bug#861539: tcpreplay FTBFS on armel/armhf/mips*: L7 fuzzing test: Makefile:963: recipe for target 'rewrite_l7fuzzing' failed

Processing commands for cont...@bugs.debian.org: > tags 861539 confirmed upstream Bug #861539 [src:tcpreplay] tcpreplay FTBFS on armel/armhf/mips*: L7 fuzzing test: Makefile:963: recipe for target 'rewrite_l7fuzzing' failed Added tag(s) upstream and confirmed. > thanks Stopping processing here.

Bug#860710: [pkg-go] Bug#860710: golang-google-api: FTBFS on i386: dh_auto_test

Am 01.05.2017 um 15:50 schrieb Roger Shimizu: Thanks for your help to upload! I find if RC bug is closed by the upload, unblock will be triggered automatically (or release team is monitoring on these, so they will unblock when see it). This is not correct. Unblocks are never triggered

Bug#860608: 132 packages with several sources for stretch in the archive… (Re: Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/ne

On Fri, Apr 21, 2017 at 11:29:30 +, Holger Levsen wrote: > On Fri, Apr 21, 2017 at 01:00:20PM +0200, Lucas Nussbaum wrote: > > FYI, that's the number of additional copies of source packages in > > stretch, per source package: > > > > udd=> select source, count(*) from sources where

Bug#861612: pixbros: level designs appear to be non-free

Package: pixbros Severity: serious Justification: Policy 2.3 Hi all, Pix Bros describes itself "as inspired" by Bubble Bobble, Snow Bros and Tumblepop. In the source package, there are screenshots of what I believe are Snow Bros' levels 21-50 in the "recursos/floors" folder. The levels for the

Bug#860710: [pkg-go] Bug#860710: golang-google-api: FTBFS on i386: dh_auto_test

On Mon, 1 May 2017 11:48:45 +0200 "Dr. Tobias Quathamer" wrote: > I've just uploaded your fix to unstable, thanks for your work! Are you > going to file an unblock request bug report? Thanks for your help to upload! I find if RC bug is closed by the upload, unblock will be

Bug#861605: marked as done (pixfrogger: FTBFS on amd64)

Your message dated Mon, 1 May 2017 14:40:55 +0200 with message-id <20170501124055.65cny7w4hbzuo...@betterave.cristau.org> and subject line Re: Bug#861605: pixfrogger: FTBFS on amd64 has caused the Debian Bug report #861605, regarding pixfrogger: FTBFS on amd64 to be marked as done. This means

Bug#861486: [Pkg-julia-devel] Bug#861486: julia: FTBFS on mips64el (segmentation fault)

Hi Julien On 29 April 2017 at 17:19, Julien Cristau wrote: > https://buildd.debian.org/status/fetch.php?pkg=julia=mips64el=0.4.7-6%2Bb3=1493472677=0 I've been unable to reproduce the build failure above. I see it was subsequently given back and built successfully:

Bug#534058: FTBFS on amd64

Control: severity -1 normal On Mon, May 1, 2017 at 13:12:32 +0200, Santiago Vila wrote: > retitle 534058 FTBFS on amd64 > severity 534058 serious > thanks > > Packages must autobuild in our autobuilders. Because our Arch:all > autobuilder is amd64, this is RC. > No, it very much isn't.

Processed: Re: Bug#534058: FTBFS on amd64

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

Bug#861605: pixfrogger: FTBFS on amd64

Package: src:pixfrogger Severity: serious Same problem as #534058: Build-depends are not available on amd64. Because our Arch:all autobuilder is amd64, this is RC for stretch. Thanks.

Processed: Re: Bug#534058: FTBFS on amd64

Processing commands for cont...@bugs.debian.org: > retitle 534058 FTBFS on amd64 Bug #534058 [pixbros] build-depends not available on amd64 Changed Bug title to 'FTBFS on amd64' from 'build-depends not available on amd64'. > severity 534058 serious Bug #534058 [pixbros] FTBFS on amd64 Severity

Bug#860805: Could we set bug #860805 against beignet-opencl-icd to stretch-is-blocker?

On Fri, Apr 28, 2017 at 10:50:46 +0200, Andreas Tille wrote: > Hi Niels, > > On Fri, Apr 28, 2017 at 07:21:00AM +, Niels Thykier wrote: > > @Andreas: Assuming worst case, what are the options for dropping beignet > > support in your packages? (I appreciate that they are probably not the > >

Bug#861112: xsane: always crashes on start

On Sun, Apr 30, 2017 at 06:53:32PM +0200, Jörg Frings-Fürst wrote: > I have a bugfix release for sane-backend ready and I send it to you. > > Please can you test the packages? I did tests on different DEs (KDE, MATE, GNOME, Xfce) after installing the new packages in each case. Both 'scanimage

Bug#860710: marked as done (golang-google-api: FTBFS on i386: dh_auto_test: go test -v -p 64 [...] returned exit code 2)

Your message dated Mon, 01 May 2017 10:03:40 + with message-id and subject line Bug#860710: fixed in golang-google-api 0.0~git20161128.3cc2e59-2 has caused the Debian Bug report #860710, regarding golang-google-api: FTBFS on i386: dh_auto_test: go test -v

Bug#860710: [pkg-go] Bug#860710: golang-google-api: FTBFS on i386: dh_auto_test

Am 27.04.2017 um 17:15 schrieb Roger Shimizu: Control: tag -1 +patch I pushed a fix commit to stretch branch in git repo. Confirmed that FTBFS fixed on DoM: http://debomatic-i386.debian.net/distribution#unstable/golang-google-api/0.0~git20161128.3cc2e59-2/buildlog Package also uploaded to

Bug#861121: version in jessie-backports still vulnerable

Weechat version 1.5-1~bpo8+10 in jessie-backports is still vulnerable to CVE-2017-8073. The same for 1.0.1-1~bpo70+1 in weezy-backports.

Bug#861591: libgnupg-interface-perl: FTBFS: Failed 10/22 test programs. 23/53 subtests failed.

Hi > HOME=/home/lamby > LOGNAME=lamby > SHLVL=1 > PWD=/home/lamby/temp/cdt.20170430222311.WuN76MAfhh.db.libgnupg-interface-perl/libgnupg-interface-perl-0.52 > OLDPWD=/home/lamby/temp/cdt.20170430222311.WuN76MAfhh.db.libgnupg-interface-perl I think that's only indirectly a problem by

Bug#861593: postfix-cdb: Broken after upgrade from jessie

Package: postfix-cdb Version: 3.1.4-4 Severity: grave Justification: renders package unusable Unlike the other postfix map packages, postfix-cdb doesn't have a breaks on earlier versions of postfix, so addmap can fire with the jessie version still in place resulting in a non-functioning package.

Bug#861592: node-dateformat: FTBFS: AssertionError: '1:19:44 PM GMT' === '1:19:44 PM UTC'

Source: node-dateformat Version: 1.0.11-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, node-dateformat fails to build from source in

Bug#861591: libgnupg-interface-perl: FTBFS: Failed 10/22 test programs. 23/53 subtests failed.

Source: libgnupg-interface-perl Version: 0.52-5 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, libgnupg-interface-perl fails to build from

Processed: Re: [Pkg-nagios-devel] Bug#861077: Bug#861077: icinga-idoutils: fails to upgrade squeeze -> wheezy -> jessie -> stretch

Processing control commands: > tags -1 pending Bug #861077 [icinga-idoutils] icinga-idoutils: fails to upgrade squeeze -> wheezy -> jessie -> stretch Added tag(s) pending. -- 861077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861077 Debian Bug Tracking System Contact

Bug#861077: [Pkg-nagios-devel] Bug#861077: Bug#861077: icinga-idoutils: fails to upgrade squeeze -> wheezy -> jessie -> stretch

Control: tags -1 pending On 04/28/2017 05:33 PM, Sebastiaan Couwenberg wrote: > On 04/28/2017 05:10 PM, Andreas Beckmann wrote: >> On 2017-04-28 15:10, Sebastiaan Couwenberg wrote: >>> No joy there either. The upgrade to wheezy fails again for unrelated >>> reasons: >>> >>> The following

Bug#861333: r-base: R packages uploaded to Debian before 14 April 2017 that use .C or .Fortran fail to find objects

Le Sat, Apr 29, 2017 at 09:50:01AM -0500, Dirk Eddelbuettel a écrit : > > I think I will cover these by hand now: > >package dotFortran dotC recommended > 1: class-7.3-14 FALSE TRUETRUE > 2: cluster-2.0.6 TRUE TRUETRUE > 3: