Bug#868958: marked as done (bcftools FTBFS on 32bit: test failures)

Your message dated Thu, 12 Oct 2017 04:33:42 + with message-id and subject line Bug#868958: fixed in bcftools 1.5-2 has caused the Debian Bug report #868958, regarding bcftools FTBFS on 32bit: test failures to be marked as done. This means that you claim

Bug#868958: [Debian-med-packaging] bcftools FTBFS on 32bit: test failures

على السبت 7 تشرين الأول 2017 ‫05:04، كتب Graham Inggs: > On 3 October 2017 at 13:52, peter green wrote: >> Unfortunately while 1.4-3 built successfully on armel, armhf and mipsel >> 1.5-1 did not. > > I think some patches were missed from the update_1.4.1 branch. >

Processed: tagging 876596

Processing commands for cont...@bugs.debian.org: > # fixed in pkg-gnome svn > tags 876596 + pending Bug #876596 [src:libcanberra] libcanberra FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available Added tag(s) pending. > thanks Stopping processing here. Please contact me if you

Processed: Bug#877428: mozjs52: FTBFS on mips64el: regress-157652.js timeout; regress-422348.js timeout; ecma_6/Array/for_of_1.js got 150, expected 300

Processing control commands: > retitle 877428 mozjs52: FTBFS on mips64el: regress-157652.js timeout; > regress-422348.js timeout; ecma_6/Array/for_of_1.js got 150, expected 300 Bug #877428 [src:mozjs52] FTBFS on mips64el: various test failures Changed Bug title to 'mozjs52: FTBFS on mips64el:

Bug#877428: mozjs52: FTBFS on mips64el: regress-157652.js timeout; regress-422348.js timeout; ecma_6/Array/for_of_1.js got 150, expected 300

Control: retitle 877428 mozjs52: FTBFS on mips64el: regress-157652.js timeout; regress-422348.js timeout; ecma_6/Array/for_of_1.js got 150, expected 300 [Re-sending to the correct clone, sorry for the noise] On Sun, 01 Oct 2017 at 19:03:46 +0100, Simon McVittie wrote: > On Sat, 23 Sep 2017 at

Bug#873778: mozjs52: FTBFS on s390x and other big-endian machines

powerpc64 (pizzetti) gets the same test failures as s390x (zelenka), suggesting that they are something that happens on big-endian 64-bit. hppa doesn't seem to have a porterbox and sparc64's (notker) was unresponsive, so I can't confirm that theory. powerpc (partch) only gets one of those

Bug#873778: Bug#877428: FTBFS on mips64el: regress-157652.js timeout; regress-422348.js timeout; ecma_6/Array/for_of_1.js got 150, expected 300

On Sun, 01 Oct 2017 at 19:03:46 +0100, Simon McVittie wrote: > On Sat, 23 Sep 2017 at 12:29:08 +0200, Emilio Pozuelo Monfort wrote: > > Let's track the mips64el failure in a different bug, as it's > > completely different from this. > > Cloned away. I haven't investigated those failures at all.

Bug#873778: mozjs52 on s390x and other big-endian machines

On Mon, 09 Oct 2017 at 10:36:52 +0100, Simon McVittie wrote: > On Sun, 01 Oct 2017 at 23:36:52 +0200, Michael Biebl wrote: > > >> The remaining problem seems to be a big-endian issue (mips, s390x, > > >> hppa, powerpc, sparc64). ppc64 fails in a slightly different > > >> manner, might just be

Bug#870848: marked as done (jackson-databind: CVE-2017-7525: Deserialization vulnerability via readValue method of ObjectMapper)

Your message dated Wed, 11 Oct 2017 23:19:05 + with message-id and subject line Bug#870848: fixed in jackson-databind 2.9.1-1 has caused the Debian Bug report #870848, regarding jackson-databind: CVE-2017-7525: Deserialization vulnerability via readValue

Bug#873868: marked as done (zeitgeist FTBFS with vala 0.36)

Your message dated Wed, 11 Oct 2017 22:51:45 + with message-id and subject line Bug#873868: fixed in zeitgeist 1.0-0.1 has caused the Debian Bug report #873868, regarding zeitgeist FTBFS with vala 0.36 to be marked as done. This means that you claim that

Bug#878270: This NMU of anthy is not good enough

Source: anthy Severity: grave Version: 1:0.3-5.1 In short, my NMU was bad. I need to upload new version based on 1:0.3-5. (Maybe with typo fix.) Although NMU tries to accomodate slow library migration, it doesn't reach its goal. This is due to binary packages anthy and anthy-common arn't

Processed: found 878266 in 2.0.0+dfsg-3

Processing commands for cont...@bugs.debian.org: > found 878266 2.0.0+dfsg-3 Bug #878266 [src:libsdl2-image] libsdl2-image: CVE-2017-2887: Incorrect XCF property handling Marked as found in versions libsdl2-image/2.0.0+dfsg-3. > thanks Stopping processing here. Please contact me if you need

Bug#878266: libsdl2-image: CVE-2017-2887: Incorrect XCF property handling

Source: libsdl2-image Version: 2.0.1+dfsg-1 Severity: grave Tags: patch security upstream Control: clone -1 -2 Control: reassign -2 src:sdl-image1.2 Control: found -2 1.2.12-1 Control: retitle -2 sdl-image1.2: CVE-2017-2887: Incorrect XCF property handling Hi, the following vulnerability was

Processed: found 878264 in 2.0.2+dfsg1-6

Processing commands for cont...@bugs.debian.org: > found 878264 2.0.2+dfsg1-6 Bug #878264 [src:libsdl2] libsdl2: CVE-2017-2888: Integer overflow while creating a new RGB surface Marked as found in versions libsdl2/2.0.2+dfsg1-6. > thanks Stopping processing here. Please contact me if you need

Processed: libsdl2-image: CVE-2017-2887: Incorrect XCF property handling

Processing control commands: > clone -1 -2 Bug #878266 [src:libsdl2-image] libsdl2-image: CVE-2017-2887: Incorrect XCF property handling Bug 878266 cloned as bug 878267 > reassign -2 src:sdl-image1.2 Bug #878267 [src:libsdl2-image] libsdl2-image: CVE-2017-2887: Incorrect XCF property handling

Bug#877499: marked as done (kmplayer FTBFS: AutoMoc: Error: moc process failed for moc_kmplayer_part.cpp)

Your message dated Wed, 11 Oct 2017 21:04:39 + with message-id and subject line Bug#877499: fixed in kmplayer 1:0.12.0b-2 has caused the Debian Bug report #877499, regarding kmplayer FTBFS: AutoMoc: Error: moc process failed for moc_kmplayer_part.cpp to

Bug#878264: libsdl2: CVE-2017-2888: Integer overflow while creating a new RGB surface

Source: libsdl2 Version: 2.0.6+dfsg1-2 Severity: grave Tags: patch security upstream Hi, the following vulnerability was published for libsdl2. CVE-2017-2888[0]: | An exploitable integer overflow vulnerability exists when creating a | new RGB Surface in SDL 2.0.5. A specially crafted file can

Processed: tagging 877499

Processing commands for cont...@bugs.debian.org: > tags 877499 + pending Bug #877499 [src:kmplayer] kmplayer FTBFS: AutoMoc: Error: moc process failed for moc_kmplayer_part.cpp Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 877499:

Bug#877150: marked as done (python-h5netcdf FTBFS: OSError: Can't read data (no appropriate function for conversion path))

Your message dated Wed, 11 Oct 2017 18:41:50 + with message-id and subject line Bug#877150: fixed in python-h5netcdf 0.4.3-1 has caused the Debian Bug report #877150, regarding python-h5netcdf FTBFS: OSError: Can't read data (no appropriate function for

Bug#877736: xserver-xorg-video-intel: Xorg crashes with hardware acceleration on

Ok, I figured out what happened. I had libegl1-mesa on hold because there is a grave bug opened for it (#874656). I decided to upgrade to the newest version despite this bug, and this seems to have fixed my problem with 3D acceleration on my graphics card. Removing the relevant configuration

Bug#853675: marked as done (etl-dev: /usr/include/ETL/_surface.h error with gcc 7)

Your message dated Wed, 11 Oct 2017 17:33:39 + with message-id and subject line Bug#853674: fixed in etl 0.04.19-1.1 has caused the Debian Bug report #853674, regarding etl-dev: /usr/include/ETL/_surface.h error with gcc 7 to be marked as done. This means

Bug#853674: marked as done (etl-dev: /usr/include/ETL/_surface.h error with gcc 7)

Your message dated Wed, 11 Oct 2017 17:33:39 + with message-id and subject line Bug#853674: fixed in etl 0.04.19-1.1 has caused the Debian Bug report #853674, regarding etl-dev: /usr/include/ETL/_surface.h error with gcc 7 to be marked as done. This means

Bug#878246: lxc package uninstallable

Package: lxc Version: 1:2.0.8-2 Severity: grave Justification: renders package unusable lxc package depends on python3-lxc package, which is currently uninstallable because it depends on python3 <3.6 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500,

Bug#784450: marked as done ([arc-gui-clients] Qt4's WebKit removal)

Your message dated Wed, 11 Oct 2017 15:48:58 + with message-id and subject line Bug#784450: fixed in arc-gui-clients 0.4.6-5 has caused the Debian Bug report #784450, regarding [arc-gui-clients] Qt4's WebKit removal to be marked as done. This means that

Bug#875930: marked as done (arc-gui-clients: should it be removed from Debian?)

Your message dated Wed, 11 Oct 2017 15:48:58 + with message-id and subject line Bug#875930: fixed in arc-gui-clients 0.4.6-5 has caused the Debian Bug report #875930, regarding arc-gui-clients: should it be removed from Debian? to be marked as done. This

Bug#878240: eclipse-pydev: Eclipse doesn't show the ability to create a Python project anymore

Package: eclipse-pydev Version: 3.9.2-5 Severity: grave Justification: renders package unusable Hi. After a period of not using Eclipse for Python development, I saw that jython was updated and, then, I tried to import a project that I wanted restart working on. Upon start, eclipse hung when I

Bug#877548: marked as done (lwt FTBFS: Error: This variant or record definition does not match that of type Unix.open_flag)

Your message dated Wed, 11 Oct 2017 15:16:39 +0100 with message-id <20171011141639.d4cdnt6pmjphc...@perpetual.pseudorandom.co.uk> and subject line Re: Bug#877548: lwt FTBFS: Error: This variant or record definition does not match that of type Unix.open_flag has caused the Debian Bug report

Bug#878236: lwt: FTBFS on armel, mips* and some non-release architectures: Cannot find (any matches for) "/usr/lib/ocaml/lwt/dlllwt-unix_stubs.so" (tried in ., debian/tmp)

Source: lwt Version: 2.7.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Control: block 871469 by -1 https://buildd.debian.org/status/fetch.php?pkg=lwt=armel=2.7.1-1=1507629485=0

Processed: lwt: FTBFS on armel, mips* and some non-release architectures: Cannot find (any matches for) "/usr/lib/ocaml/lwt/dlllwt-unix_stubs.so" (tried in ., debian/tmp)

Processing control commands: > block 871469 by -1 Bug #871469 [release.debian.org] transition: ocaml 871469 was blocked by: 877548 878235 871469 was blocking: 876570 876752 Added blocking bug(s) of 871469: 878236 -- 871469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871469 878236:

Bug#878235: lwt: FTBFS on arm64,i386,ppc64el,s390x,powerpc,ppc64: Files /usr/lib/ocaml/ppx_tools/ppx_tools.cmxa and /usr/lib/ocaml/compiler-libs/ocamlcommon.cmxa make inconsistent assumptions over imp

Source: lwt Version: 2.7.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Control: block 871469 by -1 https://buildd.debian.org/status/fetch.php?pkg=lwt=arm64=2.7.1-1=1507629114=0

Processed: lwt: FTBFS on arm64,i386,ppc64el,s390x,powerpc,ppc64: Files /usr/lib/ocaml/ppx_tools/ppx_tools.cmxa and /usr/lib/ocaml/compiler-libs/ocamlcommon.cmxa make inconsistent assumptions over impl

Processing control commands: > block 871469 by -1 Bug #871469 [release.debian.org] transition: ocaml 871469 was blocked by: 877548 871469 was blocking: 876570 876752 Added blocking bug(s) of 871469: 878235 -- 871469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871469 878235:

Bug#877146: Pending fixes for bugs in the runc package

tag 877146 + pending thanks Some bugs in the runc package are closed in revision e1ede313e8bee2acd8b8e8f3f38e8daa99cc0f6d in branch 'master' by Balint Reczey The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/runc.git/commit/?id=e1ede31 Commit message: Mark runc

Processed: Pending fixes for bugs in the runc package

Processing commands for cont...@bugs.debian.org: > tag 877146 + pending Bug #877146 {Done: Balint Reczey } [runc] update to runc (1.0.0~rc4) breaks docker Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 877146:

Bug#872635: util-linux: FTBFS on armel: test failure

Forwarding this bug report to the debian-arm porters list so not only Aurelien and Steve are aware of the issue. Would be great if you can take a look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872635 and help us find a solution. On Sat, 19 Aug 2017 17:10:13 +0200 Cyril Brulebois

Bug#862837: marked as done (xrdp: Package install failure - dpkg: error processing package xrdp (--configure))

Your message dated Wed, 11 Oct 2017 14:45:42 +0200 with message-id <38618228-9075-4140-8545-8444d871c...@naturalnet.de> and subject line ... has caused the Debian Bug report #862837, regarding xrdp: Package install failure - dpkg: error processing package xrdp (--configure) to be marked as done.

Bug#878203: [pkg-apparmor] Bug#878203: Bug#878203: AA breaks libvirt when running with kernel 4.13

Am 11.10.2017 um 13:06 schrieb Christian Boltz: > I noticed one denial that probably isn't covered by the upstream profile > yet: > > apparmor="DENIED" operation="open" profile="libvirt-c6ae5f8d- > e017-484d-9176-96b0e079c66d" name="/proc/726/cmdline" pid=6188 > comm="qemu-system-x86"

Bug#871299: libmyguiengine3debian1v5: requires rebuild against GCC 7 and symbols/shlibs bump

Hello, I've hopefully addressed the issues brought up and made an additional commit/push. Can you review and see if this is correct and ready for upload? I have no access. Cheers, Bret On Mon, Sep 25, 2017 at 11:31 AM, Simon McVittie wrote: > On Mon, 07 Aug 2017 at 15:47:16

Bug#877590: Please help upgrading htsjdk (Was: Bug#877590: FTBFS: error: package org.testng does not exist)

On Wed, Oct 11, 2017 at 12:05:28PM +0200, Olivier Sallou wrote: > > Failure seems related to not finding the *tags* extension to Test. > Seems introduced by scalatest , one of the plugins loaded by graddle. > scalatest does not seem to be available in debian. > the *tag* element seems to be

Bug#877213: node-d3-color: B-D npm not available in testing

Pirate Praveen: > On Tue, 10 Oct 2017 15:23:00 + Ximin Luo wrote: >> I was following https://wiki.debian.org/Javascript/Policy > > The top of the page says "This document is still work in progress.' > > Anyway, I have started a thread in pkg-javascript-devel list [1],

Bug#878203: [pkg-apparmor] Bug#878203: Bug#878203: AA breaks libvirt when running with kernel 4.13

Hello, there were some more profile changes done - first in openSUSE [1], but AFAIK they were already upstreamed. I had a quick look at the log - most denials are fixed with the latest upstream profile, so I'd recommend to grab that one. I noticed one denial that probably isn't covered by the

Bug#876033: primusrun doesn't find libGL.so.1

On Wed, 2017-10-11 at 11:57 +0200, Andreas Beckmann wrote: > On 10/11/2017 11:46 AM, Luca Boccassi wrote: > > Andreas, > > > > Long term, the only easy to maintain solution I can see (until > > there is > > proper support upstream for GLVND) would be to change the config in > > a > > postinst,

Bug#877213: node-d3-color: B-D npm not available in testing

On Tue, 10 Oct 2017 15:23:00 + Ximin Luo wrote: > I was following https://wiki.debian.org/Javascript/Policy The top of the page says "This document is still work in progress.' Anyway, I have started a thread in pkg-javascript-devel list [1], lets continue this

Bug#877960: marked as done (kodi-data,kodi-repository-kodi: both ship usr/share/kodi/addons/repository.xbmc.org/{addon.xml,icon.png})

Your message dated Wed, 11 Oct 2017 12:50:49 +0200 with message-id <150771904995.24709.9306329336220778...@auryn.jones.dk> and subject line Re: Bug#877960: kodi-data, kodi-repository-kodi: both ship usr/share/kodi/addons/repository.xbmc.org/{addon.xml, icon.png} has caused the Debian Bug report

Bug#875399: Uploaded fixed to DELAYED/7

Hi, Since this is a RC bug, I've uploaded sphinx-testing to unstable through the DELAYED/7 queue. This upgrades to version 0.7.2, plus a few fixes. Debdiff (for the relevant debian folder part) is attached. If you oppose to the upload, please do so before the 7 days delay. Note that this new

Bug#864162: Fwd: Debian opendkim package -- #864162

Message transféré Sujet : Debian opendkim package -- #864162 Date : Wed, 11 Oct 2017 12:17:25 +0200 De :Declercq Laurent Organisation : iHMS/i-MSCP Pour : sc...@kitterman.com Good morning, I would attire your attention on the changes

Bug#874295: clementine: installs non-free plugin at runtime

Package: clementine Version: 1.3.1+git276-g3485bbe43+dfsg-1 Followup-For: Bug #874295 Clementine has been removed from Debian testing. Can the package maintainer please comment on if there is a fix ? THe patch that Jonas has mentioned should be good enough to get this bug resolved. BTW Jonas,

Bug#877590: [Debian-med-packaging] Bug#877590: Please help upgrading htsjdk (Was: Bug#877590: FTBFS: error: package org.testng does not exist)

- Mail original - > De: "Andreas Tille" > À: 877...@bugs.debian.org, "Charles Plessy" , "Olivier > Sallou" , "Vincent > Danjean" > Cc: "Debian Bug Tracking System" > Envoyé: Mercredi

Bug#876033: primusrun doesn't find libGL.so.1

On 10/11/2017 11:46 AM, Luca Boccassi wrote: > Andreas, > > Long term, the only easy to maintain solution I can see (until there is > proper support upstream for GLVND) would be to change the config in a > postinst, depending on what package is installed. But that feels very > wrong (changing

Bug#876033: primusrun doesn't find libGL.so.1

On Thu, 2017-10-05 at 18:24 +0100, Luca Boccassi wrote: > On Thu, 2017-10-05 at 19:08 +0200, Gunman wrote: > > On 04.10.2017 00:22, Luca Boccassi wrote: > > > Unfortunately the problem can't be reproduced on Stretch given > > > there's > > > no glvnd there. At the moment I do not have a Sid

Bug#877590: Please help upgrading htsjdk (Was: Bug#877590: FTBFS: error: package org.testng does not exist)

Will try to look, but error is completly unknown and strange to me Olivier Le mer. 11 oct. 2017 11:23, Andreas Tille a écrit : > Hi folks, > > it seems no-one of the Java-competent uploaders cared for this in the > first place and so I gave the new version a shot in Git.

Bug#877590: Please help upgrading htsjdk (Was: Bug#877590: FTBFS: error: package org.testng does not exist)

Hi folks, it seems no-one of the Java-competent uploaders cared for this in the first place and so I gave the new version a shot in Git. It seems to be a usual pattern that we need to adapt several patches which I hopefully managed correctly. Its also a usual pattern that each new version

Bug#852561: marked as done (dahdi-tools: Update udevadm path)

Your message dated Wed, 11 Oct 2017 08:49:09 + with message-id and subject line Bug#852561: fixed in dahdi-tools 1:2.11.1-3 has caused the Debian Bug report #852561, regarding dahdi-tools: Update udevadm path to be marked as done. This means that you

Bug#869588: marked as done (libcap2 FTBFS: error: conflicting types for '__cap_lookup_name')

Your message dated Wed, 11 Oct 2017 08:50:07 + with message-id and subject line Bug#869588: fixed in libcap2 1:2.25-1.1 has caused the Debian Bug report #869588, regarding libcap2 FTBFS: error: conflicting types for '__cap_lookup_name' to be marked as

Bug#666414: FTBFS on s390x: Segmentation fault during installation

Control: severity -1 important On Sun, 13 Jul 2014 04:28:32 +0200 Cyril Brulebois wrote: > Dirk Eddelbuettel (2012-04-01): > > I also ran this by upstream, given that there were some changes to the > > .C() interface in R lately.  But upstream couldn't tickle

Processed: Re: Bug#666414: FTBFS on s390x: Segmentation fault during installation

Processing control commands: > severity -1 important Bug #666414 [src:rggobi] FTBFS on s390x: Segmentation fault during installation Severity set to 'important' from 'serious' -- 666414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666414 Debian Bug Tracking System Contact

Bug#878203: [pkg-apparmor] Bug#878203: AA breaks libvirt when running with kernel 4.13

Am 11.10.2017 um 04:35 schrieb Seth Arnold: > Hello Michael, do you still have the DENIED lines from your kernel logs > when experiencing this problem? If so please share them here. > > Thanks > attached is the output of "grep audit /var/log/kern.log" -- Why is it that all of the instruments

Bug#853497: marked as done (libmemcached: ftbfs with GCC-7)

Your message dated Wed, 11 Oct 2017 07:49:02 + with message-id and subject line Bug#853497: fixed in libmemcached 1.0.18-4.2 has caused the Debian Bug report #853497, regarding libmemcached: ftbfs with GCC-7 to be marked as done. This means that you claim

Bug#876299: pcre3: ftbfs on s390x, test failures

control: tags -1 -moreinfo > Could you try re-running this test on s390x with a higher stack limit > set, please? ulimit -s unlimited && dpkg-buildpackage works on zelenka (s390x porterbox) G. signature.asc Description: OpenPGP digital signature

Processed: Re: Bug#876299: pcre3: ftbfs on s390x, test failures

Processing control commands: > tags -1 -moreinfo Bug #876299 [src:pcre3] pcre3: ftbfs on s390x, test failures Removed tag(s) moreinfo. -- 876299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#853462: marked as done (json-c: ftbfs with GCC-7)

Your message dated Wed, 11 Oct 2017 07:04:43 + with message-id and subject line Bug#853462: fixed in json-c 0.12.1-1.2 has caused the Debian Bug report #853462, regarding json-c: ftbfs with GCC-7 to be marked as done. This means that you claim that the