Bug#859635: marked as done (php-horde-crypt: CVE-2017-7413 CVE-2017-7414)

Your message dated Wed, 03 May 2017 05:48:26 + with message-id and subject line Bug#859635: fixed in php-horde-crypt 2.7.5-2 has caused the Debian Bug report #859635, regarding php-horde-crypt: CVE-2017-7413 CVE-2017-7414 to be marked as done. This means

Bug#861575: tilix: Does not start on Stretch (symbol lookup error: undefined symbol)

On Sun, Apr 30, 2017 at 06:43:18PM -0400, Mathieu Basille wrote: > Following the name change from terminix to tilix, I updated > my Stretch system (which uses apt pining to install Sid > packages whenever possible) to use the new developments of > tilix. > > Install of v1.5.4-1 works without

Bug#861711: buildd.debian.org: Architecture: all B-D confusion

Package: buildd.debian.org Severity: serious Justification: makes some packages fail to build from source Per https://buildd.debian.org/status/package.php?p=gsequencer=sid , gsequencer shows up as BD-Uninstallable for Architecture: all with the explanation gsequencer build-depends on missing: -

Bug#852261: proposed fix upstream

There is a proposed fix from upstream: https://github.com/boothj5/profanity/commit/3e18aab9f38fad3cd971ec09684f7e03f299cc87 This commit worked for me on armhf, but it should fix it also for all the other architecture. -- Diego Roversi

Processed: Re: Bug#861497: gcc-6-cross: FTBFS in stretch

Processing control commands: > severity -1 minor Bug #861497 [src:gcc-6-cross] gcc-6-cross: FTBFS in stretch Severity set to 'minor' from 'serious' > tags -1 + moreinfo Bug #861497 [src:gcc-6-cross] gcc-6-cross: FTBFS in stretch Added tag(s) moreinfo. -- 861497:

Bug#861497: gcc-6-cross: FTBFS in stretch

Control: severity -1 minor Control: tags -1 + moreinfo On 29.04.2017 19:53, Santiago Vila wrote: > Package: src:gcc-6-cross > Version: 21 > Severity: serious > > Dear maintainer: > > I tried to build this package in stretch with "dpkg-buildpackage -A" > but it failed: fine, but you should make

Processed: Treating similar bugs similarly

Processing commands for cont...@bugs.debian.org: > severity 534058 important Bug #534058 [pixbros] pixbros: FTBFS on amd64: build-depends not available Severity set to 'important' from 'normal' > severity 861605 important Bug #861605 {Done: Julien Cristau } [src:pixfrogger]

Bug#861605: Treating similar bugs similarly

severity 534058 important severity 861605 important reopen 861605 thanks

Bug#860805: marked as done (beignet-opencl-icd: OpenCL fails with: drm_intel_gem_bo_context_exec() failed: Device or resource busy)

Your message dated Tue, 02 May 2017 23:18:32 + with message-id and subject line Bug#860805: fixed in beignet 1.3.0-3 has caused the Debian Bug report #860805, regarding beignet-opencl-icd: OpenCL fails with: drm_intel_gem_bo_context_exec() failed: Device

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

On 2017-05-03 00:31, Rebecca N. Palmer wrote: > Someone please upload beignet (as currently in Alioth); I'll file an > unblock request. Upload is on its way. You can probably wait a few days with the unblock request, the release-team will probably pick up the upload fixing an RC bug on their own.

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

Control: tags -1 pending The above looks like success - thanks. Someone please upload beignet (as currently in Alioth); I'll file an unblock request.

Processed: Re: [Pkg-opencl-devel] Bug#860805: Bug#860805: Could we set bug #860805 against beignet-opencl-icd to stretch-is-blocker?

Processing control commands: > tags -1 pending Bug #860805 [beignet-opencl-icd] beignet-opencl-icd: OpenCL fails with: drm_intel_gem_bo_context_exec() failed: Device or resource busy Added tag(s) pending. -- 860805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860805 Debian Bug Tracking

Bug#861431: restic: Rebuild needed for CVE-2017-3204; #859655

> It's built happily on ppc64el for the archive, so please either close this > bug or leave the fixed version in place (by all means keep it open if you > want to explore possible resource exhaustion on other machines). I haven't had a chance to re-test this build. If it's building fine for the

Bug#860703: marked as done (golang-github-jacobsa-fuse: FTBFS on i386: dh_auto_build: go install -v -p 1 github.com/jacobsa/fuse github.com/jacobsa/fuse/fsutil github.com/jacobsa/fuse/fuseops github.c

Your message dated Tue, 02 May 2017 21:49:04 + with message-id and subject line Bug#860703: fixed in golang-github-jacobsa-fuse 0.0~git20150806.0.9a7512a-2 has caused the Debian Bug report #860703, regarding golang-github-jacobsa-fuse: FTBFS on i386:

Bug#861467: marked as done (dput-ng: FTBFS (failing tests))

Your message dated Tue, 02 May 2017 21:34:11 + with message-id and subject line Bug#861467: fixed in dput-ng 1.12 has caused the Debian Bug report #861467, regarding dput-ng: FTBFS (failing tests) to be marked as done. This means that you claim that the

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

On 2 May 2017 at 18:58, Peter Colberg wrote: > Could you comment all lines and then successively uncomment to see > which line triggers the segfault? I commented out practically your entire program and it still randomly segfaults. > You could also try querying a symbol in

Bug#860463: nodm: Missing handling of plymouth

On Tue, 02 May 2017 at 08:00:44 +0100, Simon McVittie wrote: > On Tue, 02 May 2017 at 01:38:15 +0200, Axel Beckert wrote: > > JFTR: This needs an "|| true" if your init script uses "set -e", > > otherwise starting or restarting the DM besides a fresh system bootup > > might fail. > > Oh, good

Bug#861682: marked as done (libpoco-dev: missing Depends on libssl-dev)

Your message dated Tue, 02 May 2017 21:07:03 + with message-id and subject line Bug#861682: fixed in poco 1.7.6+dfsg1-5 has caused the Debian Bug report #861682, regarding libpoco-dev: missing Depends on libssl-dev to be marked as done. This means that

Bug#861690: marked as done (gerris: FTBFS - uses dh-exec without Build-Depends on it)

Your message dated Tue, 02 May 2017 21:05:12 + with message-id and subject line Bug#861690: fixed in gerris 20131206+dfsg-16 has caused the Debian Bug report #861690, regarding gerris: FTBFS - uses dh-exec without Build-Depends on it to be marked as done.

Bug#861431: restic: Rebuild needed for CVE-2017-3204; #859655

Control: found -1 0.3.3-1+b1 Control: fixed -1 0.3.3-1+b2 Hi, On Sun, Apr 30, 2017 at 12:51:03PM +0200, Félix Sipma wrote: > ppc64el rebuilding seems to give the same error as yours, though. > > Do you think we can close this bug, or associate it with ppc64el only? > > It may be an issue with

Processed: Re: Bug#861431: restic: Rebuild needed for CVE-2017-3204; #859655

Processing control commands: > found -1 0.3.3-1+b1 Bug #861431 [restic] restic: Rebuild needed for CVE-2017-3204; #859655 Marked as found in versions restic/0.3.3-1. > fixed -1 0.3.3-1+b2 Bug #861431 [restic] restic: Rebuild needed for CVE-2017-3204; #859655 Marked as fixed in versions

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

Hi, On Tue, May 02, 2017 at 07:40:43AM +0100, Rebecca N. Palmer wrote: > Has anyone tried the clFFT test I requested above? I've now done a test on my system (Thinkpad T440s, i5-4300U): 1. Without the patch (stderr): drm_intel_gem_bo_context_exec() failed: Device or resource busy

Bug#859262: Re: freezes Orca screen reader

Control: tags -1 pending Control: owner -1 Hi all, On 02-05-17 21:48, Joanmarie Diggs wrote: > On 05/02/2017 03:26 PM, Paul Gevers wrote: > >> @Joanmarie, did you get any feedback on the Orca list? > > Nope. I take that to mean all is well. If this bug doesn't receive negative feedback about

Processed (with 1 error): Re: Bug#859262: Re: freezes Orca screen reader

Processing control commands: > tags -1 pending Bug #859262 [gnome-orca] gnome-orca: Gets stuck if target app is busy Added tag(s) pending. > owner -1 Unknown command or malformed arguments to command. -- 859262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859262 Debian Bug Tracking System

Bug#861696: certbot: Python package not found.

Package: certbot Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? test -x /usr/bin/certbot -a \! -d /run/systemd/system && perl -e 'sleep int(rand(3600))' && certbot -q renew * What exactly did you do (or not do) that was effective

Bug#857296: marked as done (hol88-library is an empty package on arm64, hppa, and m68k)

Your message dated Tue, 02 May 2017 14:50:27 + with message-id <87vapj8g98@valiant.maguirefamily.org> and subject line Re: hol-library empty on arm64 has caused the Debian Bug report #857296, regarding hol88-library is an empty package on arm64, hppa, and m68k to be marked as done. This

Bug#859262: Re: freezes Orca screen reader

On 05/02/2017 03:26 PM, Paul Gevers wrote: > @Joanmarie, did you get any feedback on the Orca list? Nope. I take that to mean all is well. --joanie

Processed: severity of 861693 is grave

Processing commands for cont...@bugs.debian.org: > severity 861693 grave Bug #861693 [src:swftools] swftools: CVE-2017-8400 CVE-2017-8401 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 861693:

Bug#861683: Package: installation-reports GNOME is not Working

On Mon, 1 May 2017 00:28:59 -0500 Gerardo Flores wrote: > Package:installation-reports > Boot method: (Virtual box) > > Image version: > RC3 > Date: Abril 29 20717 > Machine: Virtual BOX DELL Presicion and Lenovo

Bug#860805: [Pkg-opencl-devel] Bug#860805: beignet-opencl-icd: OpenCL fails with: drm_intel_gem_bo_context_exec() failed: Device or resource busy

Hi Rebecca, On Tue, May 02, 2017 at 07:04:20PM +0100, Rebecca N. Palmer wrote: > > Could > >you please give a direct link what program to run once I have rebuild? > > https://bugs.freedesktop.org/show_bug.cgi?id=100639#c15 > where patch_clfft_haswell.patch is >

Processed: Fix severity Re: [j...@debian.org: Re: Bug#861589: unblock: gnumed-client/1.6.11+dfsg-3]

Processing commands for cont...@bugs.debian.org: > severity 861570 grave Bug #861570 {Done: Andreas Tille } [gnumed-client] Recommends python-hl7, but does not start without it Severity set to 'grave' from 'important' > severity 861589 normal Bug #861589 {Done: Jonathan

Bug#861690: gerris: FTBFS - uses dh-exec without Build-Depends on it

Source: gerris Version: 20131206+dfsg-15 Severity: serious Hi, The just uploaded version of gerris FTBFS as it uses dh-exec without Build-Depends on dh-exec. Thanks, ~Niels

Processed: [j...@debian.org: Re: Bug#861589: unblock: gnumed-client/1.6.11+dfsg-3]

Processing commands for cont...@bugs.debian.org: > severity 861589 grave Bug #861589 {Done: Jonathan Wiltshire } [release.debian.org] unblock: gnumed-client/1.6.11+dfsg-3 Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need

Bug#859262: Re: freezes Orca screen reader

Hi all, On 30-04-17 21:09, Joanmarie Diggs wrote: > From your output I see you clicked on the Apply button in Synaptic, a > bunch of events from DEAD accessible objects resulted, that Orca kept > processing events, presented the window you Alt+Tabbed into, etc. > > Having said that, if memory

Processed: reassign 851120 to src:xorg, forcibly merging 861683 851120

Processing commands for cont...@bugs.debian.org: > reassign 851120 src:xorg Bug #851120 [xserver-xorg-video-all] gdm3 does not start on fresh stretch install in vbox Bug reassigned from package 'xserver-xorg-video-all' to 'src:xorg'. Ignoring request to alter found versions of bug #851120 to the

Bug#860805: [Pkg-opencl-devel] Bug#860805: beignet-opencl-icd: OpenCL fails with: drm_intel_gem_bo_context_exec() failed: Device or resource busy

On 02/05/17 07:57, Andreas Tille wrote: I can confirm that beignet-dev_1.3.0-2 produces a lot of errors which vanished when using said status from Git. Good so far. - the clFFT test from https://bugs.freedesktop.org/show_bug.cgi?id=100639 This needs a small change to work in sid (its

Bug#861676: ruby-prof: broken symlink: /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> ../../../fonts/truetype/lato/Lato-RegularItalic.ttf

Control: severity -1 normal Hi, On Tue, May 02, 2017 at 05:23:34PM +0200, Andreas Beckmann wrote: > Package: ruby-prof > Version: 0.16.2+dfsg-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package ships (or

Processed: Re: Bug#861676: ruby-prof: broken symlink: /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> ../../../fonts/truetype/lato/Lato-RegularItalic.ttf

Processing control commands: > severity -1 normal Bug #861676 [ruby-prof] ruby-prof: broken symlink: /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> ../../../fonts/truetype/lato/Lato-RegularItalic.ttf Severity set to 'normal' from 'serious' -- 861676:

Bug#861684: r-cran-randomfields: FTBFS against r-base 3.4.0-1

Package: r-cran-randomfields Version: 3.1.36-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, This package FTBFS against r-base 3.4.0-1 which was uploaded to unstable recently. [..] make[1]: Leaving directory '/<>/src' make[1]:

Bug#861683: Install xserver-xorg-legacy by default for stretch

Source: xorg Version: 1:7.7+18 Severity: serious With virtualbox-dkms gone for stretch, trying to install GNOME inside Virtualbox will lead to gdm failing to start, as it tries to run Xorg as unprivileged user. This requires a KMS compatible driver though. Same is true for users of startx. They

Bug#861677: marked as done (libgfs-dev: broken symlink on i386: /usr/lib/x86_64-linux-gnu/libgfs[23]D-1.3.so -> libgfs[23]D-1.3.so.2.0.0)

Your message dated Tue, 02 May 2017 17:33:26 + with message-id and subject line Bug#861677: fixed in gerris 20131206+dfsg-15 has caused the Debian Bug report #861677, regarding libgfs-dev: broken symlink on i386:

Bug#861682: libpoco-dev: missing Depends on libssl-dev

Package: libpoco-dev Version: 1.7.6+dfsg1-4 Severity: serious Dear Maintainer, In file included from /usr/include/Poco/Crypto/X509Certificate.h:24:0, from /usr/include/Poco/Net/Context.h:25, from /usr/include/Poco/Net/SecureServerSocket.h:25,

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

Hi Graham, On Mon, May 01, 2017 at 01:53:43PM +0200, Graham Inggs wrote: > Simply running, e.g. 'debian/shlibdeps pow', 10 or so times in a row > is enough to get it to segfault. > Unfortunately, it doesn't seem to happen when run in gdb. > I don't know why this program [1], which is used to

Bug#861645: gsequencer FTBFS on mips/mipsel: FAIL: ags_xorg_application_context_test

Hi I have experienced on some other architectures with ags_xorg_application_context_test the same problems. It was not evident to me if the problem was related to Gtk+-2.0 or xvfb-run since the stack-trace ended as doing gtk_widget_show(window); However other architectures just pass the test.

Bug#861678: libi8x FTBFS on 32bit: FAIL: valid/test-corpus

Source: libi8x Version: 0.0.3-1 Severity: serious https://buildd.debian.org/status/package.php?p=libi8x=sid ... make check-TESTS PASS: exec/ops/test-deref PASS: exec/test-factorial PASS: exec/test-smoke FAIL: valid/test-corpus libi8x 0.0.3:

Bug#861486: julia: FTBFS on mips64el (segmentation fault)

A quick way to reproduce this on a porterbox, without having to build the entire julia package: Install julia's build-dependencies Change root to sid_mips64el-dchroot $ apt source julia $ cd julia-0.4.7/ $ debian/rules override_dh_link-arch If it manages to generate the links without a

Bug#861677: libgfs-dev: broken symlink on i386: /usr/lib/x86_64-linux-gnu/libgfs[23]D-1.3.so -> libgfs[23]D-1.3.so.2.0.0

Package: libgfs-dev Version: 20131206+dfsg-14 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m26.4s ERROR: FAIL: Broken

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > unarchive 661958 Bug #661958 {Done: "Adam D. Barratt" } [release.debian.org] transition: apache2 2.4 Unarchived Bug 661958 > forcemerge 669785 816310 Bug #669785 {Done: Debian FTP Masters

Bug#860703: golang-github-jacobsa-fuse: FTBFS on i386: dh_auto_build

On Tue, 2 May 2017 16:34:02 +0900 Roger Shimizu wrote: > but the following errors still exist. I don't have clue yet. > > > src/github.com/jacobsa/fuse/internal/buffer/runtime.go:22: missing function > > body for "memclr" > >

Processed (with 1 error): Merge duplicates

Processing commands for cont...@bugs.debian.org: > forcemerge 669785 816310 Bug #669785 {Done: Debian FTP Masters } [websvn] websvn: transition towards Apache 2.4 Bug #816310 [websvn] WebSVN wants do write to non existing folder "/etc/apache2/conf.d" Severity

Processed: Pending fixes for bugs in the golang-github-jacobsa-fuse package

Processing commands for cont...@bugs.debian.org: > tag 860703 + pending Bug #860703 [src:golang-github-jacobsa-fuse] golang-github-jacobsa-fuse: FTBFS on i386: dh_auto_build: go install -v -p 1 github.com/jacobsa/fuse github.com/jacobsa/fuse/fsutil github.com/jacobsa/fuse/fuseops

Bug#860703: Pending fixes for bugs in the golang-github-jacobsa-fuse package

tag 860703 + pending thanks Some bugs in the golang-github-jacobsa-fuse package are closed in revision 09331450f4b0b3a5acb6b1b86d1c71faa036ab10 in branch 'master' by Roger Shimizu The full diff can be seen at

Bug#861676: ruby-prof: broken symlink: /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> ../../../fonts/truetype/lato/Lato-RegularItalic.ttf

Package: ruby-prof Version: 0.16.2+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m20.4s ERROR: FAIL: Broken symlinks:

Processed: Not relevant for jessie

Processing commands for cont...@bugs.debian.org: > tags 852044 stretch sid Bug #852044 {Done: Daniel Silverstone } [src:lua-curl] lua-curl: FTBFS: No rule to make target '/usr/include/curl/curl.h', needed by 'curlopt.h' Added tag(s) sid and stretch. > thanks Stopping

Processed: tagging 860646

Processing commands for cont...@bugs.debian.org: > tags 860646 + pending Bug #860646 [src:golang-github-jacobsa-ogletest] golang-github-jacobsa-ogletest: FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/jacobsa/ogletest github.com/jacobsa/ogletest/srcutil

Processed: tagging 861474

Processing commands for cont...@bugs.debian.org: > tags 861474 + pending Bug #861474 [slim] slim: Session restarts in a loop rendering the whole system useless Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 861474:

Processed: user debian...@lists.debian.org, usertagging 827122, reassign 827122 to liboasis3-dev ...

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 827122 piuparts There were no usertags set. Usertags are now: piuparts. > reassign 827122 liboasis3-dev 3.mct+dfsg.121022-7 Bug #827122

Processed: found 856966 in libtextutils-ocaml-dev/112.17.00-4, found 852125 in 0.13-1.1, found 776173 in 1.3.6-5 ...

Processing commands for cont...@bugs.debian.org: > found 856966 libtextutils-ocaml-dev/112.17.00-4 Bug #856966 [src:janest-core] Uninstallable on sid Bug #843312 [src:janest-core] FTBFS: libsexplib-camlp4-dev is no longer available Bug #852890 [src:janest-core] ocaml-textutils: FTBFS:

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forwarded 860618 https://github.com/seccomp/libseccomp-golang/issues/24 Bug #860618 [src:golang-github-seccomp-libseccomp-golang] golang-github-seccomp-libseccomp-golang: FTBFS on i386: dh_auto_test: go test -v -p 1

Processed: Re: BROKEN: 0.4.11 lacks support for get_info and URLs with a prefix path

Processing commands for cont...@bugs.debian.org: > retitle 861656 0.4.11 lacks support for get_info and URLs with a prefix path Bug #861656 [src:python-jenkins] BROKEN: 0.4.11 lacks support for get_info and URLs with a prefix path Changed Bug title to '0.4.11 lacks support for get_info and URLs

Bug#861474: slim: Session restarts in a loop renedering whole system useless.

Control: tags -1 patch Hi all, On Sun, 30 Apr 2017 12:38:33 +0200 Lukas wrote: > Hi > > Got the same problem on stretch. > > Changing the systemd service type to simple solves the problem for me: > > echo "Type=simple" >> /lib/systemd/system/slim.service > systemctl

Processed: Re: slim: Session restarts in a loop renedering whole system useless.

Processing control commands: > tags -1 patch Bug #861474 [slim] slim: Session restarts in a loop rendering the whole system useless Added tag(s) patch. -- 861474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#861474: slim: Session restarts in a loop renedering whole system useless.

Same problem here on debian testing with 1.3.6-5. My current workaround: - Open a root shell (via ctrl+alt+f1) - Stop slim via: /etc/init.d/slim stop (it is stopped via systemctl) - Start slim by simply entering slim I would guess it has something to do with the systemd startup scripts. Cheers

Bug#861656: BROKEN: 0.4.11 lacks support for get_info and URLs with a prefix path

On 05/02/2017 01:18 PM, Antoine Musso wrote: > Source: python-jenkins > Version: 0.4.11-1 > Severity: important > > python-jenkins 0.4.11 is partly broken. There is at least two severe > breakages: > > * does not support a server URLs using a prefix such as: > http://example.org/ci > *

Processed: severity of 861656 is grave

Processing commands for cont...@bugs.debian.org: > severity 861656 grave Bug #861656 [src:python-jenkins] BROKEN: 0.4.11 lacks support for get_info and URLs with a prefix path Ignoring request to change severity of Bug 861656 to the same value. > thanks Stopping processing here. Please contact

Processed: severity of 861656 is grave

Processing commands for cont...@bugs.debian.org: > severity 861656 grave Bug #861656 [src:python-jenkins] BROKEN: 0.4.11 lacks support for get_info and URLs with a prefix path Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance.

Bug#770369: Bug#737491: eterm: Occurs on upgrade to Jessie from Wheezy

Hi, Thanks for your help! I think this bug is the same than bug #770369. I tried to file this as a followup to the existing bug but must have messed up with my usage of `reportbug`; sorry! This bug is close in stretch (testing). As it is expected the release stretch occurs soon, the

Processed: Re: Bug#861108: live-build: stretch image produced with default configuration does not boot

Processing control commands: > severity -1 normal Bug #861108 [live-build] live-build: stretch image produced with default configuration does not boot Severity set to 'normal' from 'grave' > reassign -1 src:live-manual Bug #861108 [live-build] live-build: stretch image produced with default

Bug#861108: live-build: stretch image produced with default configuration does not boot

Control: severity -1 normal Control: reassign -1 src:live-manual Control: retitle -1 live-manual: minimum RAM requirements not documented On Tue, May 02, 2017 at 10:54:02AM +0200, Lukas Schwaighofer wrote: > Hi, > > I think the problem reported by Antonio is because the default RAM size > of kvm

Processed: bug 860646 is forwarded to https://github.com/jacobsa/ogletest/pull/30

Processing commands for cont...@bugs.debian.org: > forwarded 860646 https://github.com/jacobsa/ogletest/pull/30 Bug #860646 [src:golang-github-jacobsa-ogletest] golang-github-jacobsa-ogletest: FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/jacobsa/ogletest

Bug#857995: respawn loop due to insufficient permissions

Am 02.05.2017 um 13:43 schrieb Michael Biebl: > After further investigation, this particular information is incorrect, > it seems. It's not the main gdm3 process which dies. So the respawning > is not done by systemd, but by the main gdm process: Which seems to be a result of the session scope

Bug#857995: respawn loop due to insufficient permissions

Am 17.03.2017 um 01:06 schrieb Michael Biebl: > Am 17.03.2017 um 00:56 schrieb Michael Biebl: >> To reproduce the problem: >> >> reboot, login, logout, switch to console, login as root, systemctl >> restart gdm3. >> >> The result ist a constantly respawned gdm3.service which fails to start >>

Bug#770369: Bug#737491: eterm: Occurs on upgrade to Jessie from Wheezy

(I am writing to bugs #737491 and #770369 as the fix is the same) Dear Andy, I think this bug is the same than bug #770369. This bug is close in stretch (testing). As it is expected the release stretch occurs soon, the easiest way is: 1. To wait for the release of stretch to get this problem

Bug#860646: Patch available

Control: tags -1 patch upstream The attached debdiff makes the package build cleanly on i386 (also tested on amd64). It extends upstream's existing code for sanitizing the test output to replace all instances of `runtime.call\d+' with `runtime.callXX', so that the test output will not vary

Processed: Patch available

Processing control commands: > tags -1 patch upstream Bug #860646 [src:golang-github-jacobsa-ogletest] golang-github-jacobsa-ogletest: FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/jacobsa/ogletest github.com/jacobsa/ogletest/srcutil github.com/jacobsa/ogletest/test_cases

Bug#861484: [Pkg-julia-devel] Bug#861484: julia: FTBFS on arm64

Hi Julien On 29/04/2017 17:13, Julien Cristau wrote: julia's build looks unreliable on arm64, it sometimes (often?) segfaults: https://buildd.debian.org/status/fetch.php?pkg=julia=arm64=0.4.7-6%2Bb3=1493471432=0

Bug#860646: Failure analysis

Hi, The build failure is due to panicking_test producing different output on i386 than what is expected by the golden file. The difference is that all occurrences of `runtime.call32' in the golden file are replaced by `runtime.call16' in the actual output. ---

Bug#861204: marked as done (deb-systemd-invoke: fails to handle units with escaped characters)

Your message dated Tue, 02 May 2017 10:49:15 + with message-id and subject line Bug#861204: fixed in init-system-helpers 1.48 has caused the Debian Bug report #861204, regarding deb-systemd-invoke: fails to handle units with escaped characters to be marked

Bug#861515: reproducibile here

I have set up an i386 debci lxc testbed with: debci_arch=i386 debci setup then confirmed that the lxc container has indeed been created: lxc-ls --fancy NAME STATE AUTOSTART GROUPS IPV4 IPV6 adt-sid-amd64 STOPPED 0 - -- adt-sid-i386 STOPPED 0 -

Bug#857855: redis FTBFS on arm64: Executing test client: NOREPLICAS Not enough good slaves to write..

severity 857855 important thanks > It built on arm64 on the second attempt. So you can probably downgrade > this bug, or close it altogether if nobody can reproduce the build > failure. Lets downgrade it for now... Regards, -- ,''`. : :' : Chris Lamb `. `'`

Processed: Re: redis FTBFS on arm64: Executing test client: NOREPLICAS Not enough good slaves to write..

Processing commands for cont...@bugs.debian.org: > severity 857855 important Bug #857855 [src:redis] redis FTBFS on arm64: Executing test client: NOREPLICAS Not enough good slaves to write.. Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you

Bug#857855: redis FTBFS on arm64: Executing test client: NOREPLICAS Not enough good slaves to write..

It built on arm64 on the second attempt. So you can probably downgrade this bug, or close it altogether if nobody can reproduce the build failure.

Bug#845786: gammaray FTBFS on arm64, armel, mips* and s390x: QFatal in quickinspectortest

It worked on arm64 on the third attempt. The second failure was different from the first failure. So perhaps worth trying several times on other architectures.

Bug#861108: live-build: stretch image produced with default configuration does not boot

Hi, I think the problem reported by Antonio is because the default RAM size of kvm is too little. Antonio: Can you retry with `-m 256M` or even `-m 512M` to have more than the default of 128M RAM? Yves: I cannot reproduce the problems reported by you. In particular, microcode packages should

Bug#860608: [pkg-golang-devel] Bug#860608: Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt

On 2 May 2017 at 19:23, Michael Stapelberg wrote: > Sorry for the late reply, I’ve been swamped. > > On Fri, Apr 21, 2017 at 10:28 AM, Niels Thykier wrote: > >> Michael Stapelberg: >> > On Fri, Apr 21, 2017 at 9:45 AM, Niels Thykier

Processed: Re: gpsshogi FTBFS on i386: error: '__builtin_ia32_psubd128' was not declared in this scope

Processing control commands: > reassign -1 src:libosl 0.8.0-1.3 Bug #861273 [src:gpsshogi] gpsshogi FTBFS on i386: error: '__builtin_ia32_psubd128' was not declared in this scope Bug reassigned from package 'src:gpsshogi' to 'src:libosl'. No longer marked as found in versions gpsshogi/0.7.0-1.1.

Bug#861273: gpsshogi FTBFS on i386: error: '__builtin_ia32_psubd128' was not declared in this scope

Control: reassign -1 src:libosl 0.8.0-1.3 Control: close -1 0.8.0-1.4 Control: affects -1 + gpsshogi On Wed, 26 Apr 2017 22:44:19 +0300 Adrian Bunk wrote: > /usr/include/osl/bits/quadInt.h: In member function 'osl::container::QuadInt& > osl::container::QuadInt::operator-=(const

Bug#825355: marked as done (firefox-esr: FTBFS on arm64: Error while running startup cache precompilation)

Your message dated Tue, 02 May 2017 08:08:45 + with message-id and subject line Bug#825355: fixed in firefox-esr 45.8.0esr-1~deb8u1 has caused the Debian Bug report #825355, regarding firefox-esr: FTBFS on arm64: Error while running startup cache

Bug#861645: gsequencer FTBFS on mips/mipsel: FAIL: ags_xorg_application_context_test

Source: gsequencer Version: 0.8.0-1 Severity: serious https://buildd.debian.org/status/package.php?p=gsequencer=sid ... make check-TESTS make[3]: Entering directory '/«PKGBUILDDIR»' make[4]: Entering directory '/«PKGBUILDDIR»' PASS: ags_thread_test PASS: ags_audio_application_context_test PASS:

Bug#861644: gpsshogi: FTBFS on i386: kifuViewer.cc:368:6: error: prototype for 'void KifuViewer::AnalysisOnlineDialog::showPVInt(...) does not match any in class

Package: gpsshogi Version: 0.7.0-1.1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, after fixing libosl in several iterations, gpsshogi starts to build on i386 without SSE related problems. But now it fails here: g++ -c -pipe -DOSL_SMP

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forwarded 860684 https://github.com/streadway/amqp/issues/261 Bug #860684 [src:golang-github-streadway-amqp] golang-github-streadway-amqp: FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/streadway/amqp returned exit code 1 Set Bug

Bug#860703: golang-github-jacobsa-fuse: FTBFS on i386: dh_auto_build

> src/github.com/jacobsa/fuse/fusetesting/stat_linux.go:33: cannot use > sys.(*syscall.Stat_t).Nlink (type uint32) as type uint64 in assignment issue above can be resolved by the patch enclosed. but the following errors still exist. I don't have clue yet. >

Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt

Sorry for the late reply, I’ve been swamped. On Fri, Apr 21, 2017 at 10:28 AM, Niels Thykier wrote: > Michael Stapelberg: > > On Fri, Apr 21, 2017 at 9:45 AM, Niels Thykier > wrote: > > > >> [...] > >>> > >> > >> They seem to be arch:all packages. We

Bug#857360: marked as done (gitlab: Fails to install in Stretch)

Your message dated Tue, 2 May 2017 12:40:55 +0530 with message-id <0ef5b071-35fe-e66b-bd77-50c7be33d...@debian.org> and subject line Re: gitlab_8.13.11+dfsg-4 no longer available, unable to install has caused the Debian Bug report #857360, regarding gitlab: Fails to install in Stretch to be

Bug#861388: marked as done (roundcube: CVE-2017-8114: security issue in virtualmin and sasl drivers)

Your message dated Tue, 02 May 2017 07:03:52 + with message-id and subject line Bug#861388: fixed in roundcube 1.2.3+dfsg.1-4 has caused the Debian Bug report #861388, regarding roundcube: CVE-2017-8114: security issue in virtualmin and sasl drivers to be

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

On Tue, 02 May 2017 at 01:38:15 +0200, Axel Beckert wrote: > JFTR: This needs an "|| true" if your init script uses "set -e", > otherwise starting or restarting the DM besides a fresh system bootup > might fail. Oh, good point. I should change that for nodm. > > Should this say "/bin/plymouth

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

❦ 1 mai 2017 23:57 +0200, Guilhem Moulin  : >> 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? Done. Thanks! --

Bug#860805: beignet-opencl-icd: OpenCL fails with: drm_intel_gem_bo_context_exec() failed: Device or resource busy

Hi Rebecca, On Sat, Apr 29, 2017 at 12:43:19PM +0100, Rebecca N. Palmer wrote: > The above patch is now in Alioth, but please do *not* upload it yet. I have tested beignet-dev_1.3.0-2 and compared it to what you get when building commit 7d60bf92c6706f174305393172841e2078ecd508. > > $ grep

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

Has anyone tried the clFFT test I requested above? Nothing further from upstream.