Bug#860739: libghc-xcb-types-dev: cannot parse xcb-proto 1.12

Package: libghc-xcb-types-dev Version: 0.7.1-4 Severity: grave Tags: sid stretch Control: block 839314 by -1 Hi, Currently haskell-xcb-types cannot parse xcb-proto 1.12. While strictly speaking you don't have to use this package to just parse the files from xcb-proto, it is the package's main

Processed: libghc-xcb-types-dev: cannot parse xcb-proto 1.12

Processing control commands: > block 839314 by -1 Bug #839314 [src:xcffib] xcffib: FTBFS: xcffibgen: Invalid bitCase: QName {qName = "required_start_align", qURI = Nothing, qPrefix = Nothing} 839314 was not blocked by any bugs. 839314 was not blocking any bugs. Added blocking bug(s) of 839314:

Bug#860701: marked as done (glm: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Wed, 19 Apr 2017 15:05:58 + with message-id and subject line Bug#860701: fixed in glm 0.9.8.3-3 has caused the Debian Bug report #860701, regarding glm: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity to

Processed: CVE-2017-7941 memory leak in sgi

Processing control commands: > found -1 8:6.7.7.10-5 Bug #860734 [src:imagemagick] CVE-2017-7941 memory leak in sgi Marked as found in versions imagemagick/8:6.7.7.10-5. > found -1 8:6.8.9.9-5 Bug #860734 [src:imagemagick] CVE-2017-7941 memory leak in sgi Marked as found in versions

Bug#860734: CVE-2017-7941 memory leak in sgi

Package: src:imagemagick Version: 8:6.6.0.4-3 Severity: serious Tags: security X-Debbugs-CC: t...@security.debian.org control: found -1 8:6.7.7.10-5 control: found -1 8:6.8.9.9-5 forwarded: https://github.com/ImageMagick/ImageMagick/issues/428 Fixed by

Bug#860637: mkosi: FTBFS on i386: help2man: can't get `--help' info from ./mkosi

Andreas Henriksson [2017-04-19 14:48 +0200]: > I've tried to reproduce this but failed. I'm using an amd64 stretch > install as a base, with a newly debootstrapped --arch=i386 > --variant=minbase chroot where I installed mkosi build-deps, fetched > mkosi sources and ran debian/rules binary. > I've

Processed: Bug #839314: xcffib: FTBFS: xcffibgen: Invalid bitCase: QName {qName = "required_start_align", qURI = Nothing, qPrefix = Nothing}

Processing control commands: > found -1 0.3.6-1 Bug #839314 [src:xcffib] xcffib: FTBFS: xcffibgen: Invalid bitCase: QName {qName = "required_start_align", qURI = Nothing, qPrefix = Nothing} Marked as found in versions xcffib/0.3.6-1. -- 839314:

Bug#839314: Bug #839314: xcffib: FTBFS: xcffibgen: Invalid bitCase: QName {qName = "required_start_align", qURI = Nothing, qPrefix = Nothing}

Control: found -1 0.3.6-1 Hi, On Sat, 1 Oct 2016 11:08:21 +0200 Lucas Nussbaum wrote: > Source: xcffib > Version: 0.4.2-2 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20160930 qa-ftbfs > Justification: FTBFS on amd64 > > Hi,

Bug#860650: zookeeper: FTBFS on i386: java.io.FileNotFoundException: /home/user42/.ant/cache/resolved-org.apache.zookeeper-zookeeper-3.4.9-2.xml (No such file or directory)

Good catch, thank you Lucas. There is an i386 specific test override in debian/rules: ifeq (i386, $(DEB_BUILD_ARCH)) override_dh_auto_test-indep: # Run core Java test suite against zookeeper ant -Dversion=$(DEB_UPSTREAM_VERSION) -DlastRevision=-1 test-core-java endif The Ant

Processed: CVE-2017-7942: memory leak in avs

Processing control commands: > found -1 8:6.7.7.10-5 Bug #860735 [src:imagemagick] CVE-2017-7942: memory leak in avs Marked as found in versions imagemagick/8:6.7.7.10-5. > found -1 8:6.8.9.9-5 Bug #860735 [src:imagemagick] CVE-2017-7942: memory leak in avs Marked as found in versions

Bug#860735: CVE-2017-7942: memory leak in avs

Package: src:imagemagick Version: 8:6.6.0.4-3 Severity: serious Tags: security X-Debbugs-CC: t...@security.debian.org control: found -1 8:6.7.7.10-5 control: found -1 8:6.8.9.9-5 forwarded: https://github.com/ImageMagick/ImageMagick/issues/428 Fixed by 962282327f3a28ffb1138f3ad3fb0438b57ae6b1

Bug#860736: CVE-2017-7943 Memory leak in svg

Package: src:imagemagick Version: 8:6.6.0.4-3 Severity: serious Tags: security X-Debbugs-CC: t...@security.debian.org control: found -1 8:6.7.7.10-5 control: found -1 8:6.8.9.9-5 forwarded: https://github.com/ImageMagick/ImageMagick/issues/427

Processed: CVE-2017-7943 Memory leak in svg

Processing control commands: > found -1 8:6.7.7.10-5 Bug #860736 [src:imagemagick] CVE-2017-7943 Memory leak in svg Marked as found in versions imagemagick/8:6.7.7.10-5. > found -1 8:6.8.9.9-5 Bug #860736 [src:imagemagick] CVE-2017-7943 Memory leak in svg Marked as found in versions

Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity

Hi! On 19/04/17 at 14:02 +0100, Chris Lamb wrote: > Lucas Nussbaum wrote: > > > > test_output_verbose (test_runner.test_debug_sql.TestDebugSQL) ... ok > > > E: Build killed with signal TERM after 150 minutes of inactivity > > Can't reproduce this locally alas... I tried again and still can;

Processed (with 2 errors): forcibly merging 860696 860683, affects 860696

Processing commands for cont...@bugs.debian.org: > forcemerge 860696 860683 Bug #860696 [src:ruby-spy] ruby-spy: FTBFS on i386: ERROR: Test "ruby2.3" failed: SyntaxError: /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:229: syntax error, unexpected '-', expecting '|' Unable to

Bug#860695: win32-loader: FTBFS on i386: segmentation fault

On 2017-04-19 13:32 +0200, Didier 'OdyX' Raboud wrote: > Control: tags -1 +moreinfo +help > > Le mercredi, 19 avril 2017, 09.28:30 h CEST Lucas Nussbaum a écrit : >> During a rebuild of all packages in stretch (in a stretch chroot, not a >> sid chroot), your package failed to build on i386. > >

Bug#860637: mkosi: FTBFS on i386: help2man: can't get `--help' info from ./mkosi

On 19/04/17 at 14:48 +0200, Andreas Henriksson wrote: > Hello all, > > On Wed, Apr 19, 2017 at 09:41:09AM +0200, Lucas Nussbaum wrote: > [...] > > During a rebuild of all packages in stretch (in a stretch chroot, not a > > sid chroot), your package failed to build on i386. > > > > Relevant part

Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity

Hi Lucas, > I tried again and still can; maybe diff your build log with mine to see > if something comes up? Good idea; mine is at: https://gist.github.com/lamby/e2152b47a6d3d69d29e34975059c6be7/raw (Testsuite runs in parallel so this might be difficult...) Regards, -- ,''`. :

Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity

Lucas Nussbaum wrote: > That's a build log for amd64, not i386. D'oh! > python2.7[39117]: segfault at ffc2cffc ip f61a8170 sp > ffc2d000 error 6 in libsqlite3.so.0.8.6[f6135000+115000] I don't have stretch/i386 within reach atm but this looks like it has narrowed it down. Any

Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity

On 19/04/17 at 15:59 +0100, Chris Lamb wrote: > Hi Lucas, > > > I tried again and still can; maybe diff your build log with mine to see > > if something comes up? > > Good idea; mine is at: > > https://gist.github.com/lamby/e2152b47a6d3d69d29e34975059c6be7/raw That's a build log for amd64,

Processed: Re: Bug#860695: win32-loader: FTBFS on i386: segmentation fault

Processing control commands: > tags -1 -moreinfo +pending Bug #860695 [src:win32-loader] win32-loader: FTBFS on i386: segmentation fault Removed tag(s) moreinfo. Bug #860695 [src:win32-loader] win32-loader: FTBFS on i386: segmentation fault Added tag(s) pending. -- 860695:

Bug#860695: win32-loader: FTBFS on i386: segmentation fault

Control: tags -1 -moreinfo +pending Le mercredi, 19 avril 2017, 15.44:00 h CEST Sven Joachim a écrit : > >> Relevant part (hopefully): > > Actually: > >> > # Prepare the README file > >> > awk > >> > (…) > >> > Segmentation fault > > > > `awk` segfaults here. This seems to be an awk bug, or

Processed: Setting bug forwarded

Processing commands for cont...@bugs.debian.org: > forwarded 860629 https://github.com/grahambell/pymoc/issues/3 Bug #860629 [src:pymoc] pymoc: FTBFS on i386: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13 Set Bug forwarded-to-address to

Bug#860611: dsniff: FTBFS: ld: cannot find -lmissing

Hello Lukas Maybe you should create a "debian/stretch" branch from 2.4b1+debian-24 tag and commit your patch here. If you want, you can add yourself as uploader and tag it as "2.4b1+debian-25" release. Later we will merge it with "debian/master" branch. I hope there's some DD willing to

Processed: reassign 860683 to src:ruby-spy, forcibly merging 860696 860683, affects 860696

Processing commands for cont...@bugs.debian.org: > reassign 860683 src:ruby-spy Bug #860683 [src:ruby-liquid] ruby-liquid: FTBFS on i386: ERROR: Test "ruby2.3" failed: SyntaxError: /usr/lib/ruby/vendor_ruby/spy/subroutine.rb:229: syntax error, unexpected '-', expecting '|' Bug reassigned from

Bug#860698: marked as done (fxt: FTBFS on i386: Test failures)

Your message dated Wed, 19 Apr 2017 16:31:14 +0200 with message-id <20170419143114.iy2ett2dgsqgo...@xanadu.blop.info> and subject line Re: Bug#860698: fxt: FTBFS on i386: Test failures has caused the Debian Bug report #860698, regarding fxt: FTBFS on i386: Test failures to be marked as done. This

Bug#860744: upgrade stuck at displaying license

Le 04/19/17 à 19:24, Gianfranco Costamagna a écrit : > control: fixed -1 5.1.20-2 > control: close -1 > > Fixed in the new upload! > > thanks for reporting it > > G. > And thanks for fixing it

Bug#859262: Re: freezes Orca screen reader

Hi On 19-04-17 01:13, Niels Thykier wrote: > Reading the log file, we at least have one bug in Orca itself (a Python > "NameError"). I am not entirely sure whether this bug triggers the > "hung" process or the "hung" process triggers the "NameError". Not sure if you (Niels) looked at the code,

Bug#860607: marked as done (gcc-mingw-w64: FTBFS: make[3]: *** No rule to make target 'gcov-dump.texi', needed by 'gcov-dump.pod')

Your message dated Wed, 19 Apr 2017 18:34:04 + with message-id and subject line Bug#860607: fixed in gcc-mingw-w64 19.3 has caused the Debian Bug report #860607, regarding gcc-mingw-w64: FTBFS: make[3]: *** No rule to make target 'gcov-dump.texi', needed

Bug#860610: marked as done (gnat-mingw-w64: FTBFS: make[3]: *** No rule to make target 'gcov-dump.texi', needed by 'gcov-dump.pod'. Stop.)

Your message dated Wed, 19 Apr 2017 18:34:10 + with message-id and subject line Bug#860610: fixed in gnat-mingw-w64 19.4 has caused the Debian Bug report #860610, regarding gnat-mingw-w64: FTBFS: make[3]: *** No rule to make target 'gcov-dump.texi',

Bug#860744: marked as done (upgrade stuck at displaying license)

Your message dated Wed, 19 Apr 2017 18:50:16 + with message-id and subject line Bug#860744: fixed in virtualbox-ext-pack 5.1.20-2 has caused the Debian Bug report #860744, regarding upgrade stuck at displaying license to be marked as done. This means that

Bug#860317: upgrade to latest stretch version breaks

On 2017-04-17 "Brent S. Elmer Ph.D." wrote: [...] > paniclog and mainlog contains this: > 2017-04-17 14:30:26 IPv6 socket creation failed: Address family not > supported by protocol This looks like 610918, i.e. having changed Debian's default default setup to disable IPv6

Bug#860744: upgrade stuck at displaying license

control: fixed -1 5.1.20-2 control: close -1 Fixed in the new upload! thanks for reporting it G.

Processed: Re: Bug#860744: upgrade stuck at displaying license

Processing control commands: > fixed -1 5.1.20-2 Bug #860744 [virtualbox-ext-pack] upgrade stuck at displaying license There is no source info for the package 'virtualbox-ext-pack' at version '5.1.20-2' with architecture '' Unable to make a source version for version '5.1.20-2' Marked as fixed

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reopen 860744 Bug #860744 {Done: Gianfranco Costamagna } [virtualbox-ext-pack] upgrade stuck at displaying license 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be

Bug#860663: [Python-modules-team] Bug#860663: pytest: FTBFS on i386: segfault during tests

Control: tags -1 + moreinfo unreproducible On 2017-04-19 09:26:48, Lucas Nussbaum wrote: > Source: pytest > Version: 3.0.6-1 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20170418-i386 qa-ftbfs > Justification: FTBFS in stretch on i386 > > Hi, >

Processed: Re: [Python-modules-team] Bug#860663: pytest: FTBFS on i386: segfault during tests

Processing control commands: > tags -1 + moreinfo unreproducible Bug #860663 [src:pytest] pytest: FTBFS on i386: segfault during tests Added tag(s) unreproducible and moreinfo. -- 860663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860663 Debian Bug Tracking System Contact

Processed: tagging 860751

Processing commands for cont...@bugs.debian.org: > tags 860751 - help Bug #860751 [mawk] mawk: segfaults on i386 during win32-loader build Removed tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 860751:

Bug#860695: marked as done (win32-loader: FTBFS on i386: segmentation fault)

Your message dated Wed, 19 Apr 2017 16:19:00 + with message-id and subject line Bug#860695: fixed in win32-loader 0.8.3 has caused the Debian Bug report #860695, regarding win32-loader: FTBFS on i386: segmentation fault to be marked as done. This means

Bug#860611: dsniff: FTBFS: ld: cannot find -lmissing

Control: tags -1 + pending Hi, On Wed, 19 Apr 2017 15:36:07 +0200 Marcos Fouces wrote: > Maybe you should create a "debian/stretch" branch from > 2.4b1+debian-24 tag and commit your patch here. If you want, you can > add yourself as uploader and tag it as

Processed: Re: Bug#860611: dsniff: FTBFS: ld: cannot find -lmissing

Processing control commands: > tags -1 + pending Bug #860611 [src:dsniff] dsniff: FTBFS: ld: cannot find -lmissing Added tag(s) pending. -- 860611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#734101: Bug#860521: [pkg-horde] Bug#860521: unblock: php-horde-core/2.27.6+debian1-1

Niels Thykier: > Control: tags -1 moreinfo > > Mathieu Parent (Debian): >> 2017-04-18 9:09 GMT+02:00 Mathieu Parent : >> [...] >>> [...] and prevent all >>> Horde to be removed from stretch because of jquery-mobile removal (See >>> #734101). >> >> I'm a bit afraid because

Bug#859926: speechd-up: fails to install

On 4/18/17, Paul Gevers wrote: > Hi all, > > I don't know what to make of it, but when I first start the speechd-up > daemon by hand, then the init script succeeds (because it finds the > daemon already running). But now it comes, I then can stop and start the > daemon

Bug#860544: [debian-mysql] Bug#860544: Security fixes from the April 2017 CPU

Hi, - car...@debian.org wrote: > Hi Lars, > > On Wed, Apr 19, 2017 at 04:26:30AM -0700, Lars Tangvald wrote: > > Hi, > > > > > > We've prepared and tested the update to MySQL 5.5.55 for Jessie. > > Debdiff output is attached. > > Only packaging changes are one refreshed patch and one that

Bug#859262: Re: freezes Orca screen reader

Niels Thykier, on mer. 19 avril 2017 20:19:00 +, wrote: > Time to hunt for some dbus experts who can tell us why a process might > fail to respond to a ping. Well, the application could simply be busy doing other stuff, like processing huge packages lists for synaptic. And that's not a

Processed: Pending fixes for bugs in the libnb-platform-java package

Processing commands for cont...@bugs.debian.org: > tag 858876 + pending Bug #858876 [libnb-platform18-java] libjna-jni: causes NoClassDefFoundError Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 858876:

Processed: Re: Bug#860702: pcl: FTBFS on i386: segmentation fault

Processing control commands: > tags -1 + moreinfo unreproducible Bug #860702 [src:pcl] pcl: FTBFS on i386: segmentation fault Added tag(s) moreinfo and unreproducible. -- 860702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860702 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#859262: Re: freezes Orca screen reader

Paul Gevers: > Hi > > On 19-04-17 01:13, Niels Thykier wrote: >> Reading the log file, we at least have one bug in Orca itself (a Python >> "NameError"). I am not entirely sure whether this bug triggers the >> "hung" process or the "hung" process triggers the "NameError". > > Not sure if you

Bug#860702: pcl: FTBFS on i386: segmentation fault

Control: tags -1 + moreinfo unreproducible * Lucas Nussbaum [2017-04-19 09:26]: > > This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian) > > (preloaded format=latex) > > restricted \write18 enabled. > > entering extended mode > > (./_formulas.tex > > LaTeX2e

Bug#860702: pcl: FTBFS on i386: segmentation fault

* Jochen Sprickerhof [2017-04-19 22:10]: > > > Segmentation fault > > > doc/doxygen/CMakeFiles/doc.dir/build.make:60: recipe for target > > > 'doc/doxygen/CMakeFiles/doc' failed > > > make[3]: *** [doc/doxygen/CMakeFiles/doc] Error 139 > > I'm unable to reproduce this.

Processed: Re: Bug#858876: libjna-jni: causes NoClassDefFoundError

Processing control commands: > reassign -1 libnb-platform18-java Bug #858876 [libjna-jni] libjna-jni: causes NoClassDefFoundError Bug reassigned from package 'libjna-jni' to 'libnb-platform18-java'. No longer marked as found in versions libjna-java/4.2.2-2. Ignoring request to alter fixed

Bug#858876: libjna-jni: causes NoClassDefFoundError

Control: reassign -1 libnb-platform18-java Hi, As discussed in this bug report and on IRC, I am going to reassign this bug to libnb-platform18-java. We haven't found any hints of embedded jar files. It is strange that the recent change of libjna-java had no effect on Netbeans though. For the

Bug#860744: upgrade stuck at displaying license

Le 04/19/17 à 20:48, athurh a écrit : > Problem persist for me. > Package virtualbox-ext-pack 5.1.20-1 If I understand correctly it is fixed in 5.1.20-2 Meanwhile what I did was: vboxmanage extpack install --replace /usr/share/virtualbox-ext-pack/Oracle* mv

Bug#859262: Re: gnome-orca: Gets stuck if target app is busy

Control: retitle -1 gnome-orca: Gets stuck if target app is busy Samuel Thibault: > Niels Thykier, on mer. 19 avril 2017 20:19:00 +, wrote: >> Time to hunt for some dbus experts who can tell us why a process might >> fail to respond to a ping. > > Well, the application could simply be busy

Processed: Re: Bug#859262: Re: gnome-orca: Gets stuck if target app is busy

Processing control commands: > retitle -1 gnome-orca: Gets stuck if target app is busy Bug #859262 [gnome-orca] freezes Orca screen reader Changed Bug title to 'gnome-orca: Gets stuck if target app is busy' from 'freezes Orca screen reader'. -- 859262:

Bug#860611: dsniff: FTBFS: ld: cannot find -lmissing

Hello Lukas, Uploaded. Thanks for your contribution, Please go forward with unblock request. Kind regards, -- Julián Moreno Patiño Debian Developer .''`. Debian GNU/{Linux,KfreeBSD} : :' : Free Operating Systems `. `' http://debian.org/ `- GPG Fingerprint: C2C8 904E 314C D8FA 041D 9B00

Bug#858876: Pending fixes for bugs in the libnb-platform-java package

tag 858876 + pending thanks Some bugs in the libnb-platform-java package are closed in revision d3eb2da837fb75478873254a14e513b18940e3f7 in branch ' stretch' by Markus Koschany The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/libnb-platform-java.git/commit/?id=d3eb2da

Bug#860673: [Python-modules-team] Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity

Chris Lamb writes: > Lucas Nussbaum wrote: > >> > test_output_verbose (test_runner.test_debug_sql.TestDebugSQL) ... ok >> > E: Build killed with signal TERM after 150 minutes of inactivity > > Can't reproduce this locally alas... I couldn't reproduce this locally. I use a

Bug#859262: Re: gnome-orca: Gets stuck if target app is busy

Am 19.04.2017 um 22:37 schrieb Niels Thykier: > Control: retitle -1 gnome-orca: Gets stuck if target app is busy > > Samuel Thibault: >> Niels Thykier, on mer. 19 avril 2017 20:19:00 +, wrote: >>> Time to hunt for some dbus experts who can tell us why a process might >>> fail to respond to a

Bug#859262: Re: freezes Orca screen reader

On 04/19/2017 04:28 PM, Samuel Thibault wrote: > Niels Thykier, on mer. 19 avril 2017 20:19:00 +, wrote: >> Time to hunt for some dbus experts who can tell us why a process might >> fail to respond to a ping. > > Well, the application could simply be busy doing other stuff, like > processing

Bug#860317: upgrade to latest stretch version breaks

On Wed, 2017-04-19 at 18:45 +0200, Andreas Metzler wrote: > On 2017-04-17 "Brent S. Elmer Ph.D." wrote: > [...] > > paniclog and mainlog contains this: > > 2017-04-17 14:30:26 IPv6 socket creation failed: Address family not > > supported by protocol > > This looks like 610918,

Processed: Re: libnb-ide14-java: broken symlinks: /usr/share/netbeans/ide14/modules/ext/*.jar

Processing control commands: > severity -1 serious Bug #857955 [libnb-ide14-java] libnb-ide14-java: broken symlinks: /usr/share/netbeans/ide14/modules/ext/*.jar Severity set to 'serious' from 'normal' -- 857955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857955 Debian Bug Tracking System

Bug#860611: marked as done (dsniff: FTBFS: ld: cannot find -lmissing)

Your message dated Wed, 19 Apr 2017 21:08:30 + with message-id and subject line Bug#860611: fixed in dsniff 2.4b1+debian-25 has caused the Debian Bug report #860611, regarding dsniff: FTBFS: ld: cannot find -lmissing to be marked as done. This means that

Bug#860744: upgrade stuck at displaying license

Package: virtualbox-ext-pack Version: 5.1.20-1 Severity: grave When trying to upgrade the package, the license if displayed, then nothing, no way to accept or refuse it. Must kill several processes and end up with a non working package. -- System Information: Debian Release: 8.7 APT prefers

Bug#860744: upgrade stuck at displaying license

Hello, >nothing, no way to accept or refuse it. >* virtualbox-ext-pack/license: true strange, this is something new to me... in the meanwhile please do vboxmanage extpack install --replace /usr/share/virtualbox-ext-pack/Oracle* this should at least fix the issue for you G.

Bug#860736: marked as done (CVE-2017-7943 Memory leak in svg)

Your message dated Wed, 19 Apr 2017 22:04:23 + with message-id and subject line Bug#860736: fixed in imagemagick 8:6.9.7.4+dfsg-6 has caused the Debian Bug report #860736, regarding CVE-2017-7943 Memory leak in svg to be marked as done. This means that

Bug#860734: marked as done (CVE-2017-7941 memory leak in sgi)

Your message dated Wed, 19 Apr 2017 22:04:23 + with message-id and subject line Bug#860734: fixed in imagemagick 8:6.9.7.4+dfsg-6 has caused the Debian Bug report #860734, regarding CVE-2017-7941 memory leak in sgi to be marked as done. This means that

Bug#860735: marked as done (CVE-2017-7942: memory leak in avs)

Your message dated Wed, 19 Apr 2017 22:04:23 + with message-id and subject line Bug#860735: fixed in imagemagick 8:6.9.7.4+dfsg-6 has caused the Debian Bug report #860735, regarding CVE-2017-7942: memory leak in avs to be marked as done. This means that

Bug#858316: confirm the bug on 32 bit machine

Hello, tried to have a look at it. Program received signal SIGSEGV, Segmentation fault. 0x80015110 in mount () (gdb) bt #0 0x80015110 in mount () #1 0xb7f8ff03 in fuse_mount_sys (mnt_opts=0x800163a8 "rw,nosuid,nodev", mo=0xb398, mnt=0x80016288

Bug#814030: CVE-2017-6100: Security flaw fixed in version 6.2.0

On Tue, 18 Apr 2017, Moritz Mühlenhoff wrote: > > Moritz/Salvatore, do you want this in jessie-proposed-updates or in > > jessie-security? > > Please fix these via the upcoming jessie point update. Ok. Laurent, can you file a bug against "release.debian.org" to ask for permission to upload a

Bug#860695: win32-loader: FTBFS on i386: segmentation fault

Control: clone -1 -2 Control: reassign -2 mawk 1.3.3-17 Control: reopen -2 o...@debian.org Control: retitle -2 mawk: segfaults on i386 during win32-loader build Control: severity -2 serious Le mercredi, 19 avril 2017, 17.31:26 h CEST Didier 'OdyX' Raboud a écrit : > Le mercredi, 19 avril 2017,

Processed: Re: Bug#860695: win32-loader: FTBFS on i386: segmentation fault

Processing control commands: > clone -1 -2 Bug #860695 {Done: Didier Raboud } [src:win32-loader] win32-loader: FTBFS on i386: segmentation fault Bug 860695 cloned as bug 860751 > reassign -2 mawk 1.3.3-17 Bug #860751 {Done: Didier Raboud } [src:win32-loader]

Bug#860426: marked as done (Urweb package has missing runtime dependency on gcc.)

Your message dated Thu, 20 Apr 2017 03:34:14 + with message-id and subject line Bug#860426: fixed in urweb 20170105+dfsg-2 has caused the Debian Bug report #860426, regarding Urweb package has missing runtime dependency on gcc. to be marked as done. This

Processed: bug 860735 is forwarded to https://github.com/ImageMagick/ImageMagick/issues/429

Processing commands for cont...@bugs.debian.org: > forwarded 860735 https://github.com/ImageMagick/ImageMagick/issues/429 Bug #860735 {Done: Bastien Roucariès } [src:imagemagick] CVE-2017-7942: memory leak in avs Changed Bug forwarded-to-address to

Bug#860663: [Python-modules-team] Bug#860663: pytest: FTBFS on i386: segfault during tests

On 19/04/17 at 20:42 +0200, Sebastian Ramacher wrote: > Control: tags -1 + moreinfo unreproducible > > On 2017-04-19 09:26:48, Lucas Nussbaum wrote: > > Source: pytest > > Version: 3.0.6-1 > > Severity: serious > > Tags: stretch sid > > User: debian...@lists.debian.org > > Usertags:

Bug#859262: Re: gnome-orca: Gets stuck if target app is busy

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=756514 Michael Biebl, on mer. 19 avril 2017 22:55:01 +0200, wrote: > Am 19.04.2017 um 22:37 schrieb Niels Thykier: > > Control: retitle -1 gnome-orca: Gets stuck if target app is busy > > > > Samuel Thibault: > >> Niels Thykier, on

Processed: Re: Bug#859262: Re: gnome-orca: Gets stuck if target app is busy

Processing control commands: > forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=756514 Bug #859262 [gnome-orca] gnome-orca: Gets stuck if target app is busy Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=756514'. -- 859262:

Bug#858876: marked as done (libjna-jni: causes NoClassDefFoundError)

Your message dated Wed, 19 Apr 2017 21:30:25 + with message-id and subject line Bug#858876: fixed in libnb-platform18-java 8.1+dfsg1-5 has caused the Debian Bug report #858876, regarding libjna-jni: causes NoClassDefFoundError to be marked as done. This

Bug#859926: speechd-up: fails to install

Hi, 1st, I have always had the idea the the spd service had bugs and was not really usable: spent so resource, didn't run really, etc. Hence the fact it's always been in "no" in defaults/speech-dispatcher. 2nd, given this feedback, maybe we may try requesting to the initscript to wait for some

Bug#860468: marked as done (gir1.2-notify-0.7: missing dependency on ${gir:Depends})

Your message dated Wed, 19 Apr 2017 23:49:26 + with message-id and subject line Bug#860468: fixed in libnotify 0.7.7-2 has caused the Debian Bug report #860468, regarding gir1.2-notify-0.7: missing dependency on ${gir:Depends} to be marked as done. This

Bug#860405: marionnet: segfaults after installation, not usable

The same situation here... eriberto@canopus:~$ marionnet Segmentation fault Debian Stretch, updated today. marionnet 0.90.6+bzr457-1+b1 installed today. Regards, Eriberto

Bug#860544: [debian-mysql] Bug#860544: Security fixes from the April 2017 CPU

Hei, Denne patchen: https://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/tree/debian/patches/fix_use_after_free_in_mysql_prune_stmt_list.patch?h=debian/wheezy Ble lagt til (kun debian 7) for 5.5.54, og får konflikt i 5.5.55. Har du tid til å ta en titt og evt. lage oppdatert patch? -- Lars

Bug#860614: golang-github-rackspace-gophercloud: FTBFS on i386: Test failures

Source: golang-github-rackspace-gophercloud Version: 1.0.0+git20161013.1012.e00690e8-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a

Bug#860617: python-skbio: FTBFS on i386: build-dependency not installable: libssw-dev

Source: python-skbio Version: 0.5.1-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package

Bug#860616: pbh5tools: FTBFS on i386: build-dependency not installable: python-pbcore

Source: pbh5tools Version: 0.8.0+dfsg-5 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package

Bug#860623: golang-github-jacobsa-bazilfuse: FTBFS on i386: dh_auto_build: go install -v -p 1 github.com/jacobsa/bazilfuse returned exit code 2

Source: golang-github-jacobsa-bazilfuse Version: 0.0~git20150622-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a

Bug#860622: ryu: FTBFS on i386: Test failures

Source: ryu Version: 4.4+dfsg1-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to

Bug#860618: golang-github-seccomp-libseccomp-golang: FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/seccomp/libseccomp-golang returned exit code 1

Source: golang-github-seccomp-libseccomp-golang Version: 0.0~git20150813.0.1b506fc-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a

Bug#860615: python-pbcommand: FTBFS on i386: build-dependency not installable: python-pbcore

Source: python-pbcommand Version: 0.5.3-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package

Bug#860619: python-passlib: FTBFS on i386: Test failures

Source: python-passlib Version: 1.7.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package

Bug#860676: pbalign: FTBFS on i386: build-dependency not installable: python-pbcore (>= 0.8.5)

Source: pbalign Version: 0.3.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to

Bug#860677: spades: FTBFS on i386: unsatisfiable build-dependencies: libssw-dev, bwa

Source: spades Version: 3.9.1+dfsg-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed

Bug#860685: dolphin-emu: FTBFS on i386: dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCA

Source: dolphin-emu Version: 5.0+dfsg-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package

Bug#860683: ruby-liquid: FTBFS on i386: ERROR: Test "ruby2.3" failed: SyntaxError: /usr/lib/ruby/vendor_ruby/spy/subroutine.rb:229: syntax error, unexpected '-', expecting '|'

Source: ruby-liquid Version: 3.0.6-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed

Bug#860674: htseq: FTBFS on i386: build-dependency not installable: python-pysam

Source: htseq Version: 0.6.1p1-4 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to

Bug#860666: dune-istl: FTBFS on i386: io.hh:577:5: error: 'begin' was not declared in this scope

Source: dune-istl Version: 2.5.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed

Bug#860663: pytest: FTBFS on i386: segfault during tests

Source: pytest Version: 3.0.6-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to

Bug#860688: rapmap: FTBFS on i386: build-dependency not installable: libjellyfish-2.0-dev

Source: rapmap Version: 0.4.0+dfsg-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed

Bug#860682: bcftools: FTBFS on i386: Test failures

Source: bcftools Version: 1.3.1-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to

Bug#860701: glm: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity

Source: glm Version: 0.9.8.3-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to

  1   2   3   >