Bug#826727: Workaround

As a workaround, for Sid there is an alpha build of a qt5 branch that's working for me (and others). Alpha: https://anki.tenderapp.com/discussions/beta-testing/231-anki-210-alpha-9 General information: https://anki.tenderapp.com/discussions/beta-testing

Bug#849132: google-perftools FTBFS on i386: FAIL: profiler_unittest.sh

On Thu, 22 Dec 2016 22:46:06 +0200 Adrian Bunk wrote: > Source: google-perftools > Version: 2.5-2 > Severity: serious > > https://buildd.debian.org/status/logs.php?pkg=google-perftools=i386 > > ... > PASS: profile_handler_unittest > rm -f profiler_unittest.sh > cp -p

Bug#852883: systemd: FTBFS: Test failures

On 28/01/17 at 10:40 +0100, Michael Biebl wrote: > The package built fine on the buildds just a couple of days ago. Do you have > an idea how the aws build environment differs? No, sorry Lucas

Bug#853036: marked as done (node-liftoff: Non-determistically FTBFS due to unreliable timing in tests)

Your message dated Sun, 29 Jan 2017 07:04:56 + with message-id <1485673496.438276.863023496.78483...@webmail.messagingengine.com> and subject line (Closing duplicate) has caused the Debian Bug report #853036, regarding node-liftoff: Non-determistically FTBFS due to unreliable timing in tests

Processed: add fixed version, to allow migration to testing

Processing commands for cont...@bugs.debian.org: > fixed 852808 0.6.3.0+debian1 Bug #852808 {Done: Pirate Praveen } [diaspora-common] diaspora-common: fails to upgrade from stretch: chown: cannot access '/var/lib/diaspora': No such file or directory Marked as fixed in

Bug#853035: node-liftoff: Non-determistically FTBFS due to unreliable timing in tests

Source: node-liftoff Version: 2.3.0-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-liftoff's testsuite appears to use method

Bug#853036: node-liftoff: Non-determistically FTBFS due to unreliable timing in tests

Source: node-liftoff Version: 2.3.0-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-liftoff's testsuite appears to use method

Bug#853032: ruby-hamster: Non-determistically FTBFS due to unreliable timing in tests

Source: ruby-hamster Version: 3.0.0-1 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, ruby-hamster's testsuite appears to use method

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 815378 important Bug #815378 [src:libxmlbird] libxmlbird has incorrect soname or incorrect package name Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 815378:

Bug#851820: marked as done (libmojolicious-plugin-assetpack-perl: FTBFS: Failed 6/36 test programs. 20/242 subtests failed.)

Your message dated Sun, 29 Jan 2017 04:18:36 + with message-id and subject line Bug#851820: fixed in libmojolicious-plugin-assetpack-perl 1.39-1 has caused the Debian Bug report #851820, regarding libmojolicious-plugin-assetpack-perl: FTBFS: Failed 6/36

Processed: bug 794316 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=731654

Processing commands for cont...@bugs.debian.org: > forwarded 794316 https://bugzilla.gnome.org/show_bug.cgi?id=731654 Bug #794316 [gdm3] can't unlock desktop: Too many open files (inotify fds leaked on unsuccessful login) Set Bug forwarded-to-address to

Processed: tagging 853018, tagging 789118

Processing commands for cont...@bugs.debian.org: > tags 853018 + pending Bug #853018 [gnome-shell] Cannot unlock screen after upgrading: Error: can't convert this._frame to an integer Added tag(s) pending. > tags 789118 + pending Bug #789118 [gdm3] Cannot unlock screen after upgrading: Type of

Bug#842446: marked as done (sbsigntool: FTBFS: test sign-verify.sh failed on arch x86_64)

Your message dated Sun, 29 Jan 2017 01:34:13 + with message-id and subject line Bug#842446: fixed in sbsigntool 0.6-3.2 has caused the Debian Bug report #842446, regarding sbsigntool: FTBFS: test sign-verify.sh failed on arch x86_64 to be marked as done.

Bug#842446: sbsigntool: FTBFS: test sign-verify.sh failed on arch x86_64

On Sat, 29 Oct 2016 11:14:49 +0100 Chris Lamb wrote: [...] >   FAIL: sign-verify.sh >   FAIL: sign-verify-detached.sh >   FAIL: sign-detach-verify.sh >   FAIL: sign-attach-verify.sh >   PASS: sign-missing-image.sh >   PASS: sign-missing-cert.sh >   PASS: sign-missing-key.sh >   

Bug#852822: signing buildinfo by default breaks compatibility

Guillem Jover writes ("Re: Bug#852822: signing buildinfo by default breaks compatibility"): > I actually realized this while I was waking up today, and brought it > up on IRC. My biggest concern was the buildd network, because that > is explicitly not signing files from inside the chroots. But

Processed: Pending fixes for bugs in the commons-math3 package

Processing commands for cont...@bugs.debian.org: > tag 852880 + pending Bug #852880 [src:commons-math3] commons-math3: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please

Bug#852880: Pending fixes for bugs in the commons-math3 package

tag 852880 + pending thanks Some bugs in the commons-math3 package are closed in revision 9634aaa7bf9c60bc94cc58c4e53633430eb56be3 in branch 'master' by tony mancill The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/commons-math3.git/commit/?id=9634aaa Commit message:

Processed: tagging 852880

Processing commands for cont...@bugs.debian.org: > tags 852880 + confirmed Bug #852880 [src:commons-math3] commons-math3: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory Added tag(s) confirmed. > thanks Stopping processing here.

Bug#821892: marked as done (pycountry: FTBFS: tests/test_general.py:28: AssertionError)

Your message dated Sun, 29 Jan 2017 00:08:04 + with message-id and subject line Bug#821892: fixed in pycountry 1.8+ds1-0.2 has caused the Debian Bug report #821892, regarding pycountry: FTBFS: tests/test_general.py:28: AssertionError to be marked as done.

Bug#821892: Missing patch

Hi, here's the missing patch, sorry, my email had a snafu. D. -- Daniel Silverstone http://www.digital-scurf.org/ PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69 diff -Nru pycountry-1.8+ds1/debian/changelog pycountry-1.8+ds1/debian/changelog ---

Bug#851576: marked as done (xtables-addons-dkms: Error building against Linux 4.9)

Your message dated Sat, 28 Jan 2017 23:48:31 + with message-id and subject line Bug#851576: fixed in xtables-addons 2.12-0.1 has caused the Debian Bug report #851576, regarding xtables-addons-dkms: Error building against Linux 4.9 to be marked as done.

Bug#821892: Fix patch - disables broken asserts

Hi, I have prepared an NMU which disables the rogue asserts. They make an assumption on the size of the iso-codes databases which have moved on since pycountry. Rather than updating the numbers in the package which will fail the next time iso-codes changes size again, simply disable the rogue

Bug#852472: marked as done (linux-image-4.9.0-1-amd64 fails compiling xt_ACCOUNT.ko out of package xtables-addons-dkms)

Your message dated Sat, 28 Jan 2017 23:48:31 + with message-id and subject line Bug#851576: fixed in xtables-addons 2.12-0.1 has caused the Debian Bug report #851576, regarding linux-image-4.9.0-1-amd64 fails compiling xt_ACCOUNT.ko out of package

Bug#757083: Migration from sysvinit to systemd: reboot fails to complete

Control: tag -1 pending On Tue, 3 Jan 2017 19:41:28 -0300 Felipe Sateler wrote: > Control: severity -1 serious > Control: tags -1 - patch >  >  > On 31 December 2016 at 08:30, Francesco Poli > wrote: > > On Fri, 30 Dec 2016 22:21:32 +0100 Michael

Processed: Re: Migration from sysvinit to systemd: reboot fails to complete

Processing control commands: > tag -1 pending Bug #757083 [initscripts] initscripts: please treat /usr (if separate) the same as / Added tag(s) pending. -- 757083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#852917: marked as done (botch: FTBFS: Error: Unbound value Architecture.read_triplettable)

0.21-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170128 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' >

Bug#853017: marked as done (bitlbee: FTBFS on every autobuilder: dh_testroot: You must run this as root (or use fakeroot).)

Your message dated Sat, 28 Jan 2017 22:48:42 + with message-id and subject line Bug#853017: fixed in bitlbee 3.5-2 has caused the Debian Bug report #853017, regarding bitlbee: FTBFS on every autobuilder: dh_testroot: You must run this as root (or use

Bug#789118: Cannot unlock screen after upgrading GNOME if locked before upgrade

Control: clone 789118 -2 Control: retitle 789118 Cannot unlock screen after upgrading: Type of message, '(sssb)', does not match expected type '(sssbb)' Control: retitle -2 Cannot unlock screen after upgrading: Error: can't convert this._frame to an integer Control: reassign -2

Processed: Re: Bug#789118: Cannot unlock screen after upgrading GNOME if locked before upgrade

Processing control commands: > clone 789118 -2 Bug #789118 [gdm3] Cannot unlock screen after upgrading GNOME if locked before upgrade Bug 789118 cloned as bug 853018 > retitle 789118 Cannot unlock screen after upgrading: Type of message, > '(sssb)', does not match expected type

Bug#853017: bitlbee: FTBFS on every autobuilder: dh_testroot: You must run this as root (or use fakeroot).

Yeah already preparing a fix. Turns out the fix from 3.4-1.1 was a different fix from the one posted by the NMU'er on the bug. :-(

Bug#853017: bitlbee: FTBFS on every autobuilder: dh_testroot: You must run this as root (or use fakeroot).

Package: src:bitlbee Version: 3.5-1.1 Severity: serious Tags: patch Dear maintainer: I tried to build this package with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-indep dh_testdir mkdir -p

Processed: user debian...@lists.debian.org, usertagging 822138, affects 822138, found 707903 in 1.1.0-10.2 ...

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 822138 piuparts Usertags were: piuparts. Usertags are now: piuparts. > affects 822138 + libqpidcommon2 libqpid-perl qpidd Bug #822138

Processed: tagging 824442

Processing commands for cont...@bugs.debian.org: > tags 824442 + upstream Bug #824442 [src:glibc] and conflict needs to be resolved Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 824442:

Processed: even stops apt

Processing commands for cont...@bugs.debian.org: > severity 853016 grave Bug #853016 [nodm] warn user all his work will be lost Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 853016:

Processed: bug 849652 is forwarded to https://github.com/joke2k/faker/issues/454

Processing commands for cont...@bugs.debian.org: > forwarded 849652 https://github.com/joke2k/faker/issues/454 Bug #849652 [src:faker] faker: FTBFS on 32-bit: ValueError: timestamp out of range for platform time_t Set Bug forwarded-to-address to 'https://github.com/joke2k/faker/issues/454'. >

Bug#846679: NMU diff

Simple fix for build failure is to add --no-dynamic-linker to the linker command lines. Here's the NMU diff; this is in incoming now... -- Steve McIntyre, Cambridge, UK.st...@einval.com "You can't barbecue lettuce!" -- Ellie Crane diff -Nru

Bug#852988: Bug#852986: Bug#852988: wine: please do not build-depend on oss4-dev on Linux

> Le 28 janv. 2017 à 13:04, Simon McVittie a écrit : > > Control: found 852988 1.8.6-1 > >> On Sat, 28 Jan 2017 at 17:57:35 +, Simon McVittie wrote: >> This package build-depends on oss4-dev, which is built by RC-buggy source >> package oss4. > > Adjusting "found"

Bug#852767: marked as done (wordpress: 4.7.2 security release (CVE-2017-5610 CVE-2017-5611 CVE-2017-5612))

Your message dated Sat, 28 Jan 2017 22:07:13 + with message-id and subject line Bug#852767: fixed in wordpress 4.7.2+dfsg-1 has caused the Debian Bug report #852767, regarding wordpress: 4.7.2 security release (CVE-2017-5610 CVE-2017-5611 CVE-2017-5612)

Bug#852853: marked as done (libwww-curl-perl: FTBFS (Cannot find curl.h))

Your message dated Sat, 28 Jan 2017 21:35:54 + with message-id and subject line Bug#852853: fixed in libwww-curl-perl 4.17-4 has caused the Debian Bug report #852853, regarding libwww-curl-perl: FTBFS (Cannot find curl.h) to be marked as done. This means

Bug#852082: closed by Jaromír Mikeš <mira.mi...@seznam.cz> (Bug#852082: fixed in gwc 0.21.19~dfsg0-7)

Hello, Excellent, thank you James and Jaromír for the very quick response! Best regards, -Christian

Bug#853008: mysql-server-5.7: purge could delete mariadb-server files with inadequate warning

Package: mysql-server-5.7 Version: 5.7.16-2 Severity: serious Hello! I'm really confused by the change in the postrm introduced in response to LP: #1602945, and I simply do not understand the rationale of the original bug report, and the comment there (and in the git commit log) that "Remove the

Bug#853006: qemu: CVE-2016-9602: 9p: virtfs allows guest to access host filesystem

Source: qemu Version: 1:2.8+dfsg-1 Severity: grave Tags: security upstream Hi, the following vulnerability was published for qemu. Rationale: I'm raising the issue for now as grave severity, since a privileged user inside guest could use this flaw to access host file system beyond the shared

Bug#825608: libnet-hiveminder-perl is marked for autoremoval from testing

On Sat, 28 Jan 2017 21:07:14 +0100, Axel Beckert wrote: > > Hrm, that bug is marked as pending since beginning of November, but > > there doesn't seem to have been an upload fixing that. > Yes: According to the current UNRELEASED changelog entry: > > TODO: > according to

Bug#852767: wordpress: 4.7.2 security release

Control: retitle -1 wordpress: 4.7.2 security release (CVE-2017-5610 CVE-2017-5611 CVE-2017-5612) On Fri, Jan 27, 2017 at 07:15:10AM +0100, Salvatore Bonaccorso wrote: > Source: wordpress > Version: 4.7.1+dfsg-1 > Severity: grave > Tags: security upstream fixed-upstream > > Hi > > A new

Processed: Re: Bug#852767: wordpress: 4.7.2 security release

Processing control commands: > retitle -1 wordpress: 4.7.2 security release (CVE-2017-5610 CVE-2017-5611 > CVE-2017-5612) Bug #852767 [src:wordpress] wordpress: 4.7.2 security release Changed Bug title to 'wordpress: 4.7.2 security release (CVE-2017-5610 CVE-2017-5611 CVE-2017-5612)' from

Bug#853004: security: javascript in the book can access files on the computer using XMLHttpRequest?

Package: calibre Version: 2.71.0+dfsg-1 Severity: critical File: /usr/bin/ebook-viewer Tags: security Hi, Someone pointed me to this note in the 2.75.1 changelog: E-book viewer: Prevent javascript in the book from accessing files on the computer using XMLHttpRequest. The ticket link

Bug#852983: marked as done (allegro4.4: please do not build-depend on oss4-dev on Linux)

Your message dated Sat, 28 Jan 2017 20:48:51 + with message-id and subject line Bug#852983: fixed in allegro4.4 2:4.4.2-10 has caused the Debian Bug report #852983, regarding allegro4.4: please do not build-depend on oss4-dev on Linux to be marked as done.

Bug#852213: marked as done (tigervnc: CVE-2017-5581: Buffer overflow in ModifiablePixelBuffer::fillRect)

Your message dated Sat, 28 Jan 2017 20:50:11 + with message-id and subject line Bug#852213: fixed in tigervnc 1.7.0+dfsg-3 has caused the Debian Bug report #852213, regarding tigervnc: CVE-2017-5581: Buffer overflow in ModifiablePixelBuffer::fillRect to

Bug#852213: [Pkg-tigervnc-devel] Bug#852213: Bug#852213: tigervnc: diff for NMU version 1.7.0+dfsg-2.1

Sure will do that. // Ola On 28 January 2017 at 21:18, Salvatore Bonaccorso wrote: > Hi Ola, > > On Sat, Jan 28, 2017 at 09:10:43PM +0100, Ola Lundqvist wrote: >> Hi >> >> Thank you. I'll make a "real" upload now instead. Thank you for the patch. > > Thank you that's fine!

Bug#852959: [pkg-go] Bug#852959: prometheus FTBFS on armhf: github.com/prometheus/prometheus/storage/local fails

On 28/01/17 16:24, Martín Ferrari wrote: >> and the machines where prometheus failed have 4 GB RAM. > > abel too... Now it fails on abel too.. I guess it was always too close to the limit, and anything else running killed it. >> "2680815616 in use", that is 2.6 GB. >> >> You have only 3 GB

Bug#852213: [Pkg-tigervnc-devel] Bug#852213: tigervnc: diff for NMU version 1.7.0+dfsg-2.1

Hi Ola, On Sat, Jan 28, 2017 at 09:10:43PM +0100, Ola Lundqvist wrote: > Hi > > Thank you. I'll make a "real" upload now instead. Thank you for the patch. Thank you that's fine! Can you then please make as well an unblock request for the release team? The fix should go to stretch, but will not

Bug#852213: [Pkg-tigervnc-devel] Bug#852213: tigervnc: diff for NMU version 1.7.0+dfsg-2.1

Hi Thank you. I'll make a "real" upload now instead. Thank you for the patch. // Ola On 28 January 2017 at 11:47, Salvatore Bonaccorso wrote: > Control: tags 852213 + pending > > Dear maintainer, > > I've prepared an NMU for tigervnc (versioned as 1.7.0+dfsg-2.1) and >

Bug#825608: libnet-hiveminder-perl is marked for autoremoval from testing

Hi, Debian testing autoremoval watch wrote: > libnet-hiveminder-perl 0.08-2 is marked for autoremoval from testing on > 2017-01-29 > > It (build-)depends on packages with these RC bugs: > 825608: libnet-jifty-perl: FTBFS: t/006-uploads.t failure Hrm, that bug is marked as pending since

Bug#825608: libnet-hiveminder-perl is marked for autoremoval from testing

Axel Beckert wrote: > Debian testing autoremoval watch wrote: > > libnet-hiveminder-perl 0.08-2 is marked for autoremoval from testing on > > 2017-01-29 > > > > It (build-)depends on packages with these RC bugs: > > 825608: libnet-jifty-perl: FTBFS: t/006-uploads.t failure > > Hrm, that bug is

Processed: tagging 852867

Processing commands for cont...@bugs.debian.org: > tags 852867 + pending Bug #852867 [icedove] icedove: debuild fails because mozilla build system requires SHELL env var set Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 852867:

Processed: tagging 832908

Processing commands for cont...@bugs.debian.org: > tags 832908 + pending Bug #832908 {Done: Laszlo Boszormenyi (GCS) } [mongodb-clients] mongodb: CVE-2016-6494: world-readable .dbshell history file Added tag(s) pending. > thanks Stopping processing here. Please contact me if

Processed: tagging 833087

Processing commands for cont...@bugs.debian.org: > tags 833087 + pending Bug #833087 [mongodb-server] bruteforcable challenge responses in unprotected logfile Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 833087:

Bug#852959: [pkg-go] Bug#852959: prometheus FTBFS on armhf: github.com/prometheus/prometheus/storage/local fails

On 28/01/17 16:10, Adrian Bunk wrote: > AFAIK the buildds are building one package at a time, Uhm, don't know about that, but I many times I have experienced test failures which are somehow timing-related on some buildds, failures I can only reproduce with very high CPU contention. > and the

Processed: Bug#848230 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 848230 pending Bug #848230 [python3-neovim-gui] /usr/bin/pynvim: crashes on startup ("Cannot add child handler") Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 848230:

Processed: tagging 851814

Processing commands for cont...@bugs.debian.org: > # doesnt affect jessie as its only caused by very recent versions of sed > tags 851814 + sid stretch Bug #851814 {Done: Axel Beckert } [apt-build] apt-build: Broken postinst by less permissive sed Added tag(s) stretch and sid. >

Bug#852959: [pkg-go] Bug#852959: prometheus FTBFS on armhf: github.com/prometheus/prometheus/storage/local fails

On Sat, Jan 28, 2017 at 03:59:45PM -0300, Martín Ferrari wrote: > On 28/01/17 11:58, Adrian Bunk wrote: > > Source: prometheus > > Version: 1.5.0+ds-1 > > Severity: serious > > > > https://buildd.debian.org/status/fetch.php?pkg=prometheus=armhf=1.5.0%2Bds-1=1485604675=0 > > As it can be seen in

Bug#852959: [pkg-go] Bug#852959: prometheus FTBFS on armhf: github.com/prometheus/prometheus/storage/local fails

On 28/01/17 11:58, Adrian Bunk wrote: > Source: prometheus > Version: 1.5.0+ds-1 > Severity: serious > > https://buildd.debian.org/status/fetch.php?pkg=prometheus=armhf=1.5.0%2Bds-1=1485604675=0 As it can be seen in the log: runtime: out of memory: cannot allocate 4194304-byte block (2680815616

Bug#851021: marked as done (nikola: FTBFS: pkg_resources.DistributionNotFound: The 'olefile' distribution was not found and is required by Pillow)

Your message dated Sat, 28 Jan 2017 19:29:00 +0100 with message-id <20170128182900.ukty223iowhwk...@betterave.cristau.org> and subject line Re: Bug#851021: nikola: FTBFS: pkg_resources.DistributionNotFound: The 'olefile' distribution was not found and is required by Pillow has caused the Debian

Bug#848927: mount: bad option.

Control: tags -1 +moreinfo,unreprodible Control: severity -1 normal On Tue, Dec 20, 2016 at 01:20:29PM -0800, Ray Andrews wrote: >Package: gparted >Version: 0.25.0-1 >Severity: grave >Justification: renders package unusable > >Dear Maintainer, > >*** Reporter, please consider answering these

Processed (with 1 error): Re: Bug#848927: mount: bad option.

Processing control commands: > tags -1 +moreinfo,unreprodible Unknown tag/s: unreprodible. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n

Processed: Version tracking fix

Processing commands for cont...@bugs.debian.org: > found 852988 1.8.6-1 Bug #852988 [src:wine] wine: please do not build-depend on oss4-dev on Linux Ignoring request to alter found versions of bug #852988 to the same values previously set > thanks Stopping processing here. Please contact me if

Bug#852991: gnocchi: FTBFS (failing tests)

Package: src:gnocchi Version: 3.0.0-2 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-indep pyversions: missing

Processed: Re: Bug#852988: wine: please do not build-depend on oss4-dev on Linux

Processing control commands: > found 852988 1.8.6-1 Bug #852988 [src:wine] wine: please do not build-depend on oss4-dev on Linux Marked as found in versions wine/1.8.6-1. -- 852986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852986 852988:

Bug#852986: Bug#852988: wine: please do not build-depend on oss4-dev on Linux

Control: found 852988 1.8.6-1 On Sat, 28 Jan 2017 at 17:57:35 +, Simon McVittie wrote: > This package build-depends on oss4-dev, which is built by RC-buggy source > package oss4. Adjusting "found" metadata so this doesn't prevent wine/1.8.6-3 from migrating before the hard freeze. I'd

Bug#852988: wine: please do not build-depend on oss4-dev on Linux

Source: wine Version: 1.8.6-3 Severity: serious Justification: release team consensus This package build-depends on oss4-dev, which is built by RC-buggy source package oss4. I discussed this with some release team members and their opinion is that oss4 should only be used on non-Linux

Bug#852989: wine-development: please do not build-depend on oss4-dev on Linux

Source: wine-development Version: 2.0~rc2-1 Severity: serious Justification: release team consensus This package build-depends on oss4-dev, which is built by RC-buggy source package oss4. I discussed this with some release team members and their opinion is that oss4 should only be used on

Bug#852742: python-oslo.middleware: CVE-2017-2592: CatchErrors leaks sensitive values in oslo.middleware

Hi Thomas, On Fri, Jan 27, 2017 at 04:57:09PM +0100, Thomas Goirand wrote: > On 01/26/2017 10:11 PM, Salvatore Bonaccorso wrote: > > Source: python-oslo.middleware > > Version: 3.19.0-2 > > Severity: grave > > Tags: security patch upstream > > Forwarded: https://launchpad.net/bugs/1628031 > > >

Bug#852984: audacious-plugins: please do not build-depend on oss4-dev on Linux

Source: audacious-plugins Version: 3.7.2-2 Severity: serious Justification: release team consensus This package build-depends on oss4-dev, which is built by RC-buggy source package oss4. I discussed this with some release team members and their opinion is that oss4 should only be used on

Bug#852983: allegro4.4: please do not build-depend on oss4-dev on Linux

Source: allegro4.4 Version: 2:4.4.2-9 Severity: serious Justification: release team consensus allegro4.4 build-depends on oss4-dev, which is built by RC-buggy source package oss4. I discussed this with some release team members and their opinion is that oss4 should only be used on non-Linux

Bug#852985: gsequencer: please do not build-depend on oss4-dev on Linux

Source: gsequencer Version: 0.7.122-1 Severity: serious Justification: release team consensus This package build-depends on oss4-dev, which is built by RC-buggy source package oss4. I discussed this with some release team members and their opinion is that oss4 should only be used on non-Linux

Bug#852986: qmmp: please do not build-depend on oss4-dev on Linux

Source: qmmp Version: 1.1.6-1 Severity: serious Justification: release team consensus This package build-depends on oss4-dev, which is built by RC-buggy source package oss4. I discussed this with some release team members and their opinion is that oss4 should only be used on non-Linux

Bug#852920: [Pkg-openssl-devel] Bug#852920: libnet-ssleay-perl: FTBFS: Test failures

On Sat, Jan 28, 2017 at 06:07:02PM +0100, gregor herrmann wrote: > On Sat, 28 Jan 2017 16:35:44 +0100, Kurt Roeckx wrote: > > > On Sat, Jan 28, 2017 at 04:02:02PM +0100, gregor herrmann wrote: > > > Control: forwarded -1 > > > https://rt.cpan.org/Public/Bug/Display.html?id=120006 > > > > I've

Bug#852894: [Pkg-clamav-devel] Bug#852894: clamav: FTBFS: dh_install: missing files, aborting

On Saturday, January 28, 2017 06:40:05 PM Reiner Herrmann wrote: > On Sat, Jan 28, 2017 at 12:31:09PM -0500, Scott Kitterman wrote: > > I think during pre-release freeze was not the best time to do this change? > > How many other packages did you break and did you coordinate this with the > >

Bug#852000: marked as done (oddjob-mkhomedir: fails to install: oddjobd: unrecognized service)

Your message dated Sat, 28 Jan 2017 17:49:55 + with message-id and subject line Bug#852000: fixed in oddjob 0.34.3-4 has caused the Debian Bug report #852000, regarding oddjob-mkhomedir: fails to install: oddjobd: unrecognized service to be marked as done.

Bug#848927: mount: bad option.

Control: tags -1 + moreinfo Hello Ray Andrews, Thanks for your bug report. On Tue, Dec 20, 2016 at 01:20:29PM -0800, Ray Andrews wrote: [...] > gparted fails completely with the message: > > "mount: bad option. Note that mmoving a mount " [...] Could you please describe how you

Processed: Re: mount: bad option.

Processing control commands: > tags -1 + moreinfo Bug #848927 [gparted] mount: bad option. Added tag(s) moreinfo. -- 848927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#834746: marked as done (jemalloc: FTBFS on i386: inlining failed...: target specific option mismatch)

Your message dated Sat, 28 Jan 2017 17:49:12 + with message-id and subject line Bug#834746: fixed in jemalloc 3.6.0-9.1 has caused the Debian Bug report #834746, regarding jemalloc: FTBFS on i386: inlining failed...: target specific option mismatch to be

Bug#852887: marked as done ("FTBFS: sbuild prevents luaotfload-tool to create a HOME cache directoey")

Source: bibtool Version: 2.66+ds-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170128 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]:

Bug#834746: NMU Fix for FTBFS

Control: tags -1 patch pending Hi, Attached is an NMU patch which corrects the problem in this bug. This is related to the fact that the test suite (and only the test suite) relies on SSE2 for i386 (which should be no issue for the buildds). I have uploaded this to unstable. Thanks, Daniel.

Processed: NMU Fix for FTBFS

Processing control commands: > tags -1 patch pending Bug #834746 [src:jemalloc] jemalloc: FTBFS on i386: inlining failed...: target specific option mismatch Added tag(s) patch and pending. -- 834746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834746 Debian Bug Tracking System Contact

Processed: summary 851446 58 ..., severity of 851446 is important

Processing commands for cont...@bugs.debian.org: > summary 851446 58 Ignoring request to change the summary of bug 851446 to the same value > retitle 851446 initscripts upgrade may result in symlink loop between > /dev/shm and /run/shm Bug #851446 [initscripts] mkdir: cannot create directory

Bug#852894: [Pkg-clamav-devel] Bug#852894: clamav: FTBFS: dh_install: missing files, aborting

On Sat, Jan 28, 2017 at 12:31:09PM -0500, Scott Kitterman wrote: > I think during pre-release freeze was not the best time to do this change? > How many other packages did you break and did you coordinate this with the > Release Team? I agree, but you should ask this the curl maintainers. :)

Bug#852894: [Pkg-clamav-devel] Bug#852894: clamav: FTBFS: dh_install: missing files, aborting

On Saturday, January 28, 2017 06:02:59 PM Reiner Herrmann wrote: > > dh_install: Cannot find (any matches for) "debian/tmp/usr/bin/clamsubmit" > > (tried in "." and "debian/tmp") > Building clamsubmit is only enabled, if libcurl is found. > > > checking for libcurl installation... /usr > >

Bug#851513: Build failing

I applied all four patches to the zfs-dkms 0.6.5.8-3 package, but compiling fails (SPL built fine after I patched it): CC [M] /var/lib/dkms/zfs/0.6.5.8/build/module/zfs/zpl_export.o /var/lib/dkms/zfs/0.6.5.8/build/module/zfs/zpl_ctldir.c:424:13: error: initialization from incompatible pointer

Processed: Re: clamav: FTBFS: dh_install: missing files, aborting

Processing control commands: > tag -1 + patch Bug #852894 [src:clamav] clamav: FTBFS: dh_install: missing files, aborting Added tag(s) patch. -- 852894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#852894: clamav: FTBFS: dh_install: missing files, aborting

Control: tag -1 + patch The attached patch changes the detection of libcurl by not checking for the curl.h header, but for the curl-config command provided by the same -dev package. Regards, Reiner diff --git a/debian/patches/curl-detection.patch b/debian/patches/curl-detection.patch new file

Bug#852920: [Pkg-openssl-devel] Bug#852920: libnet-ssleay-perl: FTBFS: Test failures

On Sat, 28 Jan 2017 16:35:44 +0100, Kurt Roeckx wrote: > On Sat, Jan 28, 2017 at 04:02:02PM +0100, gregor herrmann wrote: > > Control: forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=120006 > > I've just filed: > https://rt.cpan.org/Public/Bug/Display.html?id=120006 Is this a

Bug#852894: clamav: FTBFS: dh_install: missing files, aborting

> dh_install: Cannot find (any matches for) "debian/tmp/usr/bin/clamsubmit" > (tried in "." and "debian/tmp") Building clamsubmit is only enabled, if libcurl is found. > checking for libcurl installation... /usr > configure: WARNING: libcurl not found. Please use the web interface for >

Bug#852886: marked as done (libvirt-python: FTBFS: ERROR: failed virConnectSecretEventRegisterAny)

ibvirt-python Version: 2.5.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170128 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules b

Bug#795690: NMU diff for libcdio

I'm uploading this to unstable now rather than to DELAYED; there's not been any obvious maintainer activity here for ages... -- Steve McIntyre, Cambridge, UK.st...@einval.com "Since phone messaging became popular, the young generation has lost the ability to read

Bug#852367: marked as done (wims build-depends on autoconf2.59)

Your message dated Sat, 28 Jan 2017 16:05:52 + with message-id and subject line Bug#852367: fixed in wims 1:4.13c~dfsg1-2 has caused the Debian Bug report #852367, regarding wims build-depends on autoconf2.59 to be marked as done. This means that you

Processed: I botched the merge

Processing commands for cont...@bugs.debian.org: > forcemerge 850958 852263 852337 Bug #850958 [ldc] ldc on ppc64el is broken Bug #852337 [ldc] ldc FTBFS on ppc64el: Failed to compile empty program using D compiler '/usr/bin/ldmd2' Added indication that 852337 affects

Processed (with 1 error): ldc on ppc64el is broken

Processing control commands: > reassign -1 ldc 1:1.1.0+b6-1 Bug #850958 [src:terminix] terminix: FTBFS on ppc64el: segmentation fault Bug reassigned from package 'src:terminix' to 'ldc'. No longer marked as found in versions terminix/1.4.0-1. Ignoring request to alter fixed versions of bug

Bug#850958: ldc on ppc64el is broken

Control: reassign -1 ldc 1:1.1.0+b6-1 Control: reassign 852263 ldc 1:1.1.0+b6-1 Control: reassign 852337 ldc 1:1.1.0+b6-1 Control: -1 852263 852337 Control: retitle -1 ldc on ppc64el is broken Control: affects -1 src:terminix src:onedrive src:gtk-d src:mustache-d Further information:

Bug#852245: fix_python2_selectors.patch is not correct

On Sat, 28 Jan 2017 13:10:15 +0100 Irmen de Jong wrote: > I'm not sure what the best course of action is here, but I strongly suggest > to re-open > the bug for now and not have the patch as it is right now. I think I have a proper solution in place for the next Pyro4

  1   2   3   >