Processed: Re: [uim-chewing] Future uim-utils removal

Processing control commands: > severity -1 serious Bug #875759 [src:uim-chewing] [uim-chewing] Future uim-utils removal Severity set to 'serious' from 'wishlist' -- 875759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875759 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#869638: slic3r-prusa FTBFS on big endian: admesh works correctly on little endian machines only

[Adrian Bunk] > If this is not fixable with reasonable effort, an RM bug for the old mips > binary should be sent against ftp.debian.org and this bug downgraded to > important. I had a quick look at the code, and the trigger is of course this in xs/src/admesh/stl.h: #ifndef BOOST_LITTLE_ENDIAN

Bug#877063: marked as done (libitpp FTBFS on i386 with gcc 7)

Your message dated Sun, 01 Oct 2017 03:52:15 + with message-id and subject line Bug#877063: fixed in libitpp 4.3.1-8 has caused the Debian Bug report #877063, regarding libitpp FTBFS on i386 with gcc 7 to be marked as done. This means that you claim that

Bug#871083: [Debian-med-packaging] Bug#871083: python-pysam: FTBFS: Test failures

On 30/09/17 21:43, Afif Elghraoui wrote: The new upstream version is the solution to this problem, but we've been going back and forth over issues (fixing one, revealing another) in updating the package. I'll see if I can do it today, but I don't understand why this should be blocking python

Bug#853338: Andreas' NMU in DELAYED/7

Control: tags -1 +pending > I've prepared a minimal NMU and will be looking for a sponsor. I've put the NMU into DELAYED/7. Preferred way to NACK is to upload a better fix yourself, but if anything is wrong, please holler. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ We domesticated dogs 36000 years ago; together we

Processed: Andreas' NMU in DELAYED/7

Processing control commands: > tags -1 +pending Bug #853338 [src:bossa] bossa: ftbfs with GCC-7 Added tag(s) pending. -- 853338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#877365: pjproject: source contains non-free files

Source: pjproject Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 A recent inspection of copyright and licensing revealed several files lacking proper licensing. debian/copyright has been corrected, including hinting for repackaging source - but I am not familiar with the git

Bug#877364: pjproject: source file licensed as BSD-4-clause and GPL-2+ effectively unlicensed

Source: pjproject Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The file pjlib/src/pj/sock_linux_kernel.c is licensed as both BSD-4-clause and GPL-2+. Not dual-licensed, but separately declared. Those licenses are incompatible, and therefore the licensing is useless. -

Bug#869404: resiprocate: CVE-2017-11521: Adding too many media connections may lead to memory exhaustion

On Sun, Jul 23, 2017 at 07:55:20AM +0200, Salvatore Bonaccorso wrote: > Source: resiprocate > Version: 1:1.9.7-5 > Severity: grave > Tags: upstream security > Forwarded: https://github.com/resiprocate/resiprocate/pull/88 > > Hi, > > the following vulnerability was published for resiprocate. > >

Processed: closing 817765

Processing commands for cont...@bugs.debian.org: > # symfony and php-cache-tag-interop currently in NEW depend on php-psr-cache > close 817765 Bug #817765 [php-psr-cache] Useless in Stretch Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#871083: [Debian-med-packaging] Bug#871083: python-pysam: FTBFS: Test failures

على السبت 30 أيلول 2017 ‫16:43، كتب Afif Elghraoui: > I'll see if I can do it today, I see Andreas Tille is on top of this. The current issue right now is this upstream bug we encounter when trying to build the latest upstream version: https://github.com/pysam-developers/pysam/issues/542

Bug#871083: [Debian-med-packaging] Bug#871083: python-pysam: FTBFS: Test failures

Hi, Peter, على السبت 30 أيلول 2017 ‫09:18، كتب peter green: > Any ETA on fixing this? it is blocking the migration of python2.7 to testing. > > I notice that the package tracker claims that there is a new upstream version > available. > The new upstream version is the solution to this

Bug#877353: acpica-unix FTBFS on mips64el: error: cast from pointer to integer of different size

Source: acpica-unix Version: 20170831-1 Severity: serious Tags: patch https://buildd.debian.org/status/fetch.php?pkg=acpica-unix=mips64el=20170831-1=1506550333=0 ... - Intermediate obj/aslcompilerparse.c /<>/generate/unix/iasl/obj/aslcompiler.y: In function 'AslCompilerparse':

Bug#877212: [Pkg-javascript-devel] Bug#877212: Bug#877212: node-d3-color: B-D npm not available in testing

Hi, Le 30/09/2017 à 21:06, Jérémy Lal a écrit : > > I did a quick check on acorn and rollup and i fail to see how > acorn-object-spread > is related to these modules. Even the github issue is not really explicit. > Can you explain please ? The dep thread is the following: rollup needs

Bug#877212: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing

Hello, On Sat, Sep 30 2017, Christian Seiler wrote: > Ack. Wouldn't it be preferable to just include a copy of the prebuilt > node-d3-color "binary" alongside its actual source tarball and have > debian/rules just copy the prebuilt "binary" for now? That would > fulfill one of the widely

Bug#877212: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing

On 09/30/2017 09:10 PM, Sean Whitton wrote: > On Sun, Oct 01 2017, Pirate Praveen wrote: >> Packaging of rollup is stuck [1] and I can make progress with gitlab >> package with node-d3-color in contrib. Quite a lot of work can happen >> even with gitlab in contrib, like making sure everything is

Processed: FTBFS in reproducible, but not everywhere else

Processing control commands: > severity -1 normal Bug #876922 [src:golang-github-approvals-go-approval-tests] golang-github-approvals-go-approval-tests FTBFS with Go 1.9 Severity set to 'normal' from 'serious' -- 876922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876922 Debian Bug

Bug#876875: FTBFS in reproducible, but not everywhere else

Control: severity -1 normal These FTBFS are in reproducible builds reliably present in sid and not in buster: https://tests.reproducible-builds.org/debian/history/golang-github-approvals-go-approval-tests.html https://tests.reproducible-builds.org/debian/history/packer.html

Processed: FTBFS in reproducible, but not everywhere else

Processing control commands: > severity -1 normal Bug #876929 [src:packer] packer FTBFS with Go 1.9 Severity set to 'normal' from 'serious' -- 876929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: FTBFS in reproducible, but not everywhere else

Processing control commands: > severity -1 normal Bug #876875 [src:golang-github-gin-gonic-gin] golang-github-gin-gonic-gin FTBFS with Go 1.9 Severity set to 'normal' from 'serious' -- 876875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876875 Debian Bug Tracking System Contact

Bug#853349: codeblocks: Patch for the build-failure

Please go ahead, I currently don't have time :( David (sorry for topquoting, replying from my mobile) Il 30 Set 2017 20:51, "Andreas Moog" ha scritto: > Control: tags 853349 + patch > > Dear maintainer, > > this particular error is fixed already in upstream's SVN

Bug#877212: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing

Hello Pirate, On Sun, Oct 01 2017, Pirate Praveen wrote: > On 09/30/2017 09:26 PM, Sean Whitton wrote: >> To my mind, this complies with the letter of Policy but not its >> spirit. > > The whole purpose of having contrib and non-free is to host packages > that can't be in main, either

Bug#877212: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing

2017-09-30 20:37 GMT+02:00 Pirate Praveen : > On 09/30/2017 09:26 PM, Sean Whitton wrote: > > To my mind, this complies with the letter of Policy but not its spirit. > > The whole purpose of having contrib and non-free is to host packages > that can't be in main, either

Bug#869916: marked as done (ghostscript: CVE-2017-9612: heap-use-after-free in Ins_IP(base/ttinterp.c))

Your message dated Sat, 30 Sep 2017 18:48:24 + with message-id and subject line Bug#869916: fixed in ghostscript 9.20~dfsg-3.2+deb9u1 has caused the Debian Bug report #869916, regarding ghostscript: CVE-2017-9612: heap-use-after-free in

Bug#869977: marked as done (ghostscript: CVE-2017-11714: Out of bounds read in igc_reloc_struct_ptr())

Your message dated Sat, 30 Sep 2017 18:48:24 + with message-id and subject line Bug#869977: fixed in ghostscript 9.20~dfsg-3.2+deb9u1 has caused the Debian Bug report #869977, regarding ghostscript: CVE-2017-11714: Out of bounds read in

Bug#869910: marked as done (ghostscript: CVE-2017-9739: heap-buffer-overflow in Ins_JMPR)

Your message dated Sat, 30 Sep 2017 18:48:24 + with message-id and subject line Bug#869910: fixed in ghostscript 9.20~dfsg-3.2+deb9u1 has caused the Debian Bug report #869910, regarding ghostscript: CVE-2017-9739: heap-buffer-overflow in Ins_JMPR to be

Processed: codeblocks: Patch for the build-failure

Processing control commands: > tags 853349 + patch Bug #853349 [src:codeblocks] codeblocks: ftbfs with GCC-7 Added tag(s) patch. -- 853349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#869907: marked as done (ghostscript: CVE-2017-9835: heap-buffer-overflow in gs_alloc_ref_array(ialloc.c))

Your message dated Sat, 30 Sep 2017 18:48:24 + with message-id and subject line Bug#869907: fixed in ghostscript 9.20~dfsg-3.2+deb9u1 has caused the Debian Bug report #869907, regarding ghostscript: CVE-2017-9835: heap-buffer-overflow in

Bug#869913: marked as done (ghostscript: CVE-2017-9727: heap-buffer-overflow in gx_ttfReader__Read(base/gxttfb.c))

Your message dated Sat, 30 Sep 2017 18:48:24 + with message-id and subject line Bug#869913: fixed in ghostscript 9.20~dfsg-3.2+deb9u1 has caused the Debian Bug report #869913, regarding ghostscript: CVE-2017-9727: heap-buffer-overflow in

Bug#869915: marked as done (ghostscript: CVE-2017-9726: heap-use-after-free in Ins_MDRP(base/ttinterp.c))

Your message dated Sat, 30 Sep 2017 18:48:24 + with message-id and subject line Bug#869915: fixed in ghostscript 9.20~dfsg-3.2+deb9u1 has caused the Debian Bug report #869915, regarding ghostscript: CVE-2017-9726: heap-use-after-free in

Bug#869917: marked as done (ghostscript: CVE-2017-9611: heap-buffer-overflow in Ins_MIRP(base/ttinterp.c))

Your message dated Sat, 30 Sep 2017 18:48:24 + with message-id and subject line Bug#869917: fixed in ghostscript 9.20~dfsg-3.2+deb9u1 has caused the Debian Bug report #869917, regarding ghostscript: CVE-2017-9611: heap-buffer-overflow in

Bug#853349: codeblocks: Patch for the build-failure

Control: tags 853349 + patch Dear maintainer, this particular error is fixed already in upstream's SVN repo: https://sourceforge.net/p/codeblocks/code/11006/ I've attached a minimal nmu for which I will seek sponsoring. Please tell me if I shouldn't upload this! Thanks! Regards, Andreas

Bug#877341: libapache2-mod-md: Doesn't seem to work at all: "AH02572: Failed to configure at least one certificate and key" (seems to require a patched version of mod_ssl / apache2)

Thank you! On Sat, 30 Sep 2017 at 11:31 Axel Beckert wrote: > Control: tag -1 + confirmed > Control: retitle -1 libapache2-mod-md: Doesn't work yet: "AH02572: Failed > to configure at least one certificate and key" (require a patched version > of apache2) > > Hi Ondřej, > >

Bug#877212: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing

On 09/30/2017 09:26 PM, Sean Whitton wrote: > To my mind, this complies with the letter of Policy but not its spirit. The whole purpose of having contrib and non-free is to host packages that can't be in main, either permanently or temporarily. I fail to see how it is against the spirit. > Could

Bug#877341: libapache2-mod-md: Doesn't seem to work at all: "AH02572: Failed to configure at least one certificate and key" (seems to require a patched version of mod_ssl / apache2)

Control: tag -1 + confirmed Control: retitle -1 libapache2-mod-md: Doesn't work yet: "AH02572: Failed to configure at least one certificate and key" (require a patched version of apache2) Hi Ondřej, Ondřej Surý wrote: > you are right and I intended to fill an bug on apache2 to get the patch >

Processed: Re: Bug#877341: libapache2-mod-md: Doesn't seem to work at all: "AH02572: Failed to configure at least one certificate and key" (seems to require a patched version of mod_ssl / apache2)

Processing control commands: > tag -1 + confirmed Bug #877341 [libapache2-mod-md] libapache2-mod-md: Doesn't seem to work at all: "AH02572: Failed to configure at least one certificate and key" (seems to require a patched version of mod_ssl / apache2) Added tag(s) confirmed. > retitle -1

Bug#877212: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing

On 09/30/2017 01:30 PM, Andreas Beckmann wrote: > Unstable is not outside the archive. But that dos not seem logical. Does it mean these packages can stay in testing if we remove npm from unstable? signature.asc Description: OpenPGP digital signature

Bug#877344: python-mne FTBFS: ERROR: Test ICA on raw and epochs

Source: python-mne Version: 0.13.1+dfsg-3 Severity: serious Tags: buster sid Some recent change in unstable makes python-mne FTBFS: https://tests.reproducible-builds.org/debian/history/python-mne.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-mne.html ...

Bug#876860: marked as done (qtwebengine-opensource-src FTBFS with debhelper 10.9)

Your message dated Sat, 30 Sep 2017 17:51:13 + with message-id and subject line Bug#876860: fixed in qtwebengine-opensource-src 5.9.1+dfsg-5 has caused the Debian Bug report #876860, regarding qtwebengine-opensource-src FTBFS with debhelper 10.9 to be

Processed: Re: Bug#877341: libapache2-mod-md: Doesn't seem to work at all: "AH02572: Failed to configure at least one certificate and key" (seems to require a patched version of mod_ssl / apache2)

Processing control commands: > clone 877341 -1 Bug #877341 [libapache2-mod-md] libapache2-mod-md: Doesn't seem to work at all: "AH02572: Failed to configure at least one certificate and key" (seems to require a patched version of mod_ssl / apache2) Bug 877341 cloned as bug 877343 > reassign -1

Bug#877341: libapache2-mod-md: Doesn't seem to work at all: "AH02572: Failed to configure at least one certificate and key" (seems to require a patched version of mod_ssl / apache2)

Control: clone 877341 -1 Control: reassign -1 src:apache2 Control: retitle -1 apache2: please include mod_md patch in apache2 Control: severity -1 normal Control: block 877341 by -1 Hi Axel, you are right and I intended to fill an bug on apache2 to get the patch included. But I didn't get to it

Bug#877341: libapache2-mod-md: Doesn't seem to work at all: "AH02572: Failed to configure at least one certificate and key" (seems to require a patched version of mod_ssl / apache2)

Package: libapache2-mod-md Version: 0.9.0-1 Severity: grave Dear Ondřej, I've installed libapache2-mod-md on a machine (Raspberry Pi) running Debian Unstable where apache2 was already installed. I've disabled all previous site configurations and wrote a new site configuration from scratch and

Bug#877339: libreoffice-core: OOlibreoffice SEGV in _expand_stack_to on most documents

Hi, sent to early. On Sat, Sep 30, 2017 at 05:53:47PM +0100, Matthew Vernon wrote: > #0 0x51fb0f95 in _expand_stack_to(unsigned char*) () >from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so OpenJDK. > Identifier:

Bug#877339: libreoffice-core: OOlibreoffice SEGV in _expand_stack_to on most documents

retitle 877339 libreoffice-core: libreoffice SEGV in _expand_stack_to on most documents reassign 877339 src:linux forcemerge 865303 877339 thanks Hi, On Sat, Sep 30, 2017 at 05:53:47PM +0100, Matthew Vernon wrote: > I've found stable's version of libreoffice basically unusable (I > previously

Processed: Re: Bug#877339: libreoffice-core: OOlibreoffice SEGV in _expand_stack_to on most documents

Processing commands for cont...@bugs.debian.org: > retitle 877339 libreoffice-core: libreoffice SEGV in _expand_stack_to on most > documents Bug #877339 [libreoffice-core] libreoffice-core: OOlibreoffice SEGV in _expand_stack_to on most documents Changed Bug title to 'libreoffice-core:

Bug#877175: marked as done (libreoffice-help-* still depend on removed virtual package libreoffice-style-default)

Your message dated Sat, 30 Sep 2017 17:07:04 + with message-id and subject line Bug#877175: fixed in libreoffice 1:5.4.2~rc2-1 has caused the Debian Bug report #877175, regarding libreoffice-help-* still depend on removed virtual package

Bug#853347:

In buster (testing) the version 61.0.3163.100-2 that is not in the repository of testing is working correctly and security bugs have been fixed in this version. Could update this version for testing repository? Thanks.

Bug#875822: Should certmaster be removed from Debian?

Hello Nima, I've been looking at this bug report and wonder if the best course of action for Debian would be to remove certmaster from the archive. It hasn't seen any maintainer-upload since 2009, the homepage is gone and I can't find any active upstream development repository. Additionally,

Bug#877146: marked as done (update to runc (1.0.0~rc4) breaks docker)

Your message dated Sat, 30 Sep 2017 16:21:09 + with message-id and subject line Bug#877146: fixed in runc 1.0.0~rc4+dfsg1-2 has caused the Debian Bug report #877146, regarding update to runc (1.0.0~rc4) breaks docker to be marked as done. This means that

Bug#876123: marked as done (libpcap0.8-dev: `pcap-config --libs` output starting with a space may cause FTBFS)

Your message dated Sat, 30 Sep 2017 16:20:27 + with message-id and subject line Bug#876123: fixed in libpcap 1.8.1-5 has caused the Debian Bug report #876123, regarding libpcap0.8-dev: `pcap-config --libs` output starting with a space may cause FTBFS to

Bug#877212: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing

Hello Pirate, On Sat, Sep 30 2017, Pirate Praveen wrote: > On വെള്ളി 29 സെപ്റ്റംബര്‍ 2017 11:04 വൈകു, Jérémy Lal wrote: >> >> Build-Depending on npm is a sign something very wrong, >> policy-breaking, is happening, like downloading a npm module during >> build. > > Hence this is in contrib and

Processed: Re: Bug#877146: update to runc (1.0.0~rc4) breaks docker

Processing control commands: > clone -1 -2 Bug #877146 [runc] update to runc (1.0.0~rc4) breaks docker Bug 877146 cloned as bug 877329 877329 was blocked by: 877284 877329 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #877329 to the same blocks previously set >

Bug#877146: update to runc (1.0.0~rc4) breaks docker

Control: clone -1 -2 Control: reassign -2 docker.io 1.13.1~ds1-2 Control: retitle -2 docker.io: Please switch to using docker-runc Hi, I'm fixing the original bug by adding Breaks: with current docker.io version to runc, please switch to using docker-runc in docker.io. Thanks, Balint

Bug#877146: update to runc (1.0.0~rc4) breaks docker

Hi Shengjing, 2017-09-30 2:34 GMT-04:00 Shengjing Zhu : >>> I see activity in docker.io's packaging repository in the v17.05.0-ce.new >>> which may work with rc4 but according to the control file it does not. >>> >>> How about I upload docker-runc with previous runc version shipping

Bug#877322: git-buildpackage: FTBFS: openjade:E: cannot open "/usr/share/gtk-doc/data/gtk-doc.dsl" (No such file or directory)

Hi Guido Am 30.09.2017 um 17:04 schrieb Guido Günther: > On Sat, Sep 30, 2017 at 04:32:46PM +0200, Andreas Beckmann wrote: >> openjade:E: cannot open "/usr/share/gtk-doc/data/gtk-doc.dsl" (No such file >> or directory) > > The gtk-doc package dropped the stylesheet in 1.26. gtk-doc maintainers

Bug#877322: git-buildpackage: FTBFS: openjade:E: cannot open "/usr/share/gtk-doc/data/gtk-doc.dsl" (No such file or directory)

Hi, On Sat, Sep 30, 2017 at 04:32:46PM +0200, Andreas Beckmann wrote: > Source: git-buildpackage > Version: 0.8.18 > Severity: serious > Justification: fails to build from source > > Hi, > > after some recent change in sid, git-buildpackage in sid and > experimental started to FTBFS: > > [...]

Bug#877325: rss2email: ImportError: No module named rss2email.main

Package: rss2email Version: 1:3.9-3 Severity: grave Hi, since I've upgraded from 1:3.9-2.1 to 1:3.9-3, rss2email fails to start: $ r2e Traceback (most recent call last): File "/usr/bin/r2e", line 3, in import rss2email.main ImportError: No module named rss2email.main

Bug#877322: git-buildpackage: FTBFS: openjade:E: cannot open "/usr/share/gtk-doc/data/gtk-doc.dsl" (No such file or directory)

Source: git-buildpackage Version: 0.8.18 Severity: serious Justification: fails to build from source Hi, after some recent change in sid, git-buildpackage in sid and experimental started to FTBFS: [...] make -C docs make[3]: Entering directory '/build/git-buildpackage-0.8.18/docs' echo '' >

Bug#877320: ruby-kramdown FTBFS and Debci failure: test failures

Source: ruby-kramdown Version: 1.14.0-1 Severity: serious Some recent change in unstable makes ruby-kramdown FTBFS and Debci fail: https://ci.debian.net/packages/r/ruby-kramdown/unstable/amd64/ https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-kramdown.html ... 1)

Bug#877319: golang-github-golang-geo: FTBFS on i386

Source: golang-github-golang-geo Version: 0.0~git20170112.0.f819552-1 Severity: serious Justification: fails to build from source Hi, golang-github-golang-geo builds fine on amd64, but fails on i386: debian/rules build dh build --buildsystem=golang --with=golang dh_update_autotools_config

Bug#877317: golang-golang-x-debug: FTBFS on i386

Package: golang-golang-x-debug Version: 0.0~git20160621.0.fb50892-1 Severity: serious Justification: fails to build from source Hi, golang-golang-x-debug builds fine on amd64, but fails on i386: debian/rules build dh build --buildsystem=golang --with=golang dh_update_autotools_config

Bug#877313: marked as done (kcalcore FTBFS: undefined reference to `qt_qhash_seed')

Your message dated Sat, 30 Sep 2017 16:53:32 +0300 with message-id <20170930135332.4gsi4aevjrrjdpmt@localhost> and subject line kcalcore in experimental builds has caused the Debian Bug report #877313, regarding kcalcore FTBFS: undefined reference to `qt_qhash_seed' to be marked as done. This

Bug#876608: [Pkg-sass-devel] Bug#876608: ruby-compass (build) depends on ruby-sass (< 3.5), but 3.5.1-2 is in unstable

Quoting Jonas Smedegaard (2017-09-30 15:38:39) > Quoting Adrian Bunk (2017-09-24 01:16:20) >> ruby-compass depends ond build depends on ruby-sass (< 3.5), but >> 3.5.1-2 is in unstable. > > This is unlikely to change, since ruby-compass is dead upstream and > ruby-sass has moved on. :-(

Processed: ruby-compass breaking ruby-compass-rails

Processing commands for cont...@bugs.debian.org: > affects 876608 ruby-compass-rails Bug #876608 [ruby-compass] ruby-compass (build) depends on ruby-sass (< 3.5), but 3.5.1-2 is in unstable Added indication that 876608 affects ruby-compass-rails > End of message, stopping processing here.

Bug#877229: marked as pending

tag 877229 pending thanks Hello, Bug #877229 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-wml/wml.git/commit/?id=77cef80 --- commit

Processed: Bug#877229 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 877229 pending Bug #877229 [src:insserv] insserv: FTBFS with GCC 7: error: 'extension' undeclared Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 877229:

Bug#877314: ruby-premailer FTBFS and Debci failure: test failure

Source: ruby-premailer Version: 1.8.6-1 Severity: serious Tags: buster sid Some recent change in unstable makes ruby-premailer FTBFS and Debci fail: https://ci.debian.net/packages/r/ruby-premailer/unstable/amd64/

Bug#877147: closed by Chris Lamb <la...@debian.org> (Bug#877147: fixed in lintian 2.5.54)

Control: reopen -1 On Fri, Sep 29, 2017 at 06:09:09PM +, Debian Bug Tracking System wrote: >... >* t/tests/binaries-from-other-arch/debian/debian/dumpobj: > + [CL] Apply patch from Jakub Wilk to prevent test failures on >armhf/arm64, etc. (Closes: #877147) >... Now

Processed: Re: Bug#877147 closed by Chris Lamb <la...@debian.org> (Bug#877147: fixed in lintian 2.5.54)

Processing control commands: > reopen -1 Bug #877147 {Done: Chris Lamb } [lintian] lintian: FTBFS on armhf/arm64: dh_shlibdeps: file -e apptype -e ascii -e encoding -e cdf -e compress -e tar debian/binaries-from-other-arch/usr/bin/elfobject returned exit code 1 'reopen' may

Bug#877313: kcalcore FTBFS: undefined reference to `qt_qhash_seed'

Source: kcalcore Version: 4:16.04.2-1 Severity: serious Tags: buster sid Some recent change in unstable makes kcalcore FTBFS: https://tests.reproducible-builds.org/debian/history/kcalcore.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kcalcore.html ...

Bug#877295: [Pkg-kde-extras] Bug#877295: amarok build-depends on removed package libgpod-nogtk-dev

In data sabato 30 settembre 2017 16:12:19 CEST, Adrian Bunk ha scritto: > On Sat, Sep 30, 2017 at 02:04:58PM +0200, Pino Toscano wrote: > > In data sabato 30 settembre 2017 14:55:34 CEST, Adrian Bunk ha scritto: > >... > > > Current status quo in Debian is that it is completely normal that > > > a

Bug#876608: [Pkg-sass-devel] Bug#876608: ruby-compass (build) depends on ruby-sass (< 3.5), but 3.5.1-2 is in unstable

Quoting Adrian Bunk (2017-09-24 01:16:20) > ruby-compass depends ond build depends on ruby-sass (< 3.5), > but 3.5.1-2 is in unstable. This is unlikely to change, since ruby-compass is dead upstream and ruby-sass has moved on. :-( - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt

Bug#870151: marked as done (zeroinstall-injector FTBFS with OCaml 4.05.0: Option -a cannot be used with .cmxa input files.)

Your message dated Sat, 30 Sep 2017 13:36:51 + with message-id and subject line Bug#870151: fixed in zeroinstall-injector 2.12.2-1 has caused the Debian Bug report #870151, regarding zeroinstall-injector FTBFS with OCaml 4.05.0: Option -a cannot be used

Bug#877311: pythonqt ships generated files without documented way to regenerate

Source: pythonqt Version: 3.0-3 Severity: serious generated_cpp_5* are not source. In addition to the DFSG issue, the armhf/armel FTBFS in unstable might be fixable if files generated during the build would be used.

Processed: tagging 877227

Processing commands for cont...@bugs.debian.org: > tags 877227 + pending Bug #877227 [src:wml] wml: FTBFS on i386: cp: target '/build/wml-2.4.1ds1/obj-i386-linux-gnu/wml_test/' is not a directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance.

Processed: Re: Bug#877261: jemalloc: FTBFS on 32-bit archs: operator new/delete symbols have changed

Processing control commands: > retitle -1 jemalloc: FTBFS on 32-bit archs: incorrect symbols for operator > new/delete Bug #877261 [src:jemalloc] jemalloc: FTBFS on 32-bit archs: operator new/delete symbols have changed Changed Bug title to 'jemalloc: FTBFS on 32-bit archs: incorrect symbols

Bug#871083: python-pysam: FTBFS: Test failures

Any ETA on fixing this? it is blocking the migration of python2.7 to testing. I notice that the package tracker claims that there is a new upstream version available.

Bug#877261: jemalloc: FTBFS on 32-bit archs: operator new/delete symbols have changed

Control: retitle -1 jemalloc: FTBFS on 32-bit archs: incorrect symbols for operator new/delete Control: tag -1 pending On 09/30/2017 02:08 PM, Faidon Liambotis wrote: > I've fixed this in git a while ago[1] but haven't uploaded because that > version has a bunch of FTBFSes in other

Bug#877310: nbdkit FTBFS on armhf/i386: FAIL: test-socket-activation

Source: nbdkit Version: 1.1.15-1 Severity: serious https://buildd.debian.org/status/package.php?p=nbdkit=sid ... FAIL: test-socket-activation /<>/src/nbdkit -P /tmp/nbdkitE9W6gC/pid -o -v /<>/plugins/example1/.libs/nbdkit-example1-plugin.so nbdkit: debug: TLS

Processed: reassign 875826 to mutter

Processing commands for cont...@bugs.debian.org: > reassign 875826 mutter 3.26.0+20170925~ea214fb-1 Bug #875826 [epiphany-browser] epiphany-browser: typing in URL bar lags a lot, preventing correct typing Bug reassigned from package 'epiphany-browser' to 'mutter'. No longer marked as found in

Bug#877295: [Pkg-kde-extras] Bug#877295: amarok build-depends on removed package libgpod-nogtk-dev

On Sat, Sep 30, 2017 at 02:04:58PM +0200, Pino Toscano wrote: > In data sabato 30 settembre 2017 14:55:34 CEST, Adrian Bunk ha scritto: >... > > Current status quo in Debian is that it is completely normal that > > a new upload of some package is followed by me filing 10-50 RC bugs > > against

Bug#875826: epiphany-browser: typing in URL bar lags a lot, preventing correct typing

Control: reassign -1 mutter/3.26.0+20170925~ea214fb-1 Control: affects -1 epiphany-browser On 2017-09-14 at 22:44 (+0200), Matteo F. Vescovi wrote: > Package: epiphany-browser > Version: 3.26.0-1 > Severity: serious > > Dear Maintainer, > > I've noticed that, since 3.25.9x version uploaded to

Processed (with 1 error): Re: Bug#875826: epiphany-browser: typing in URL bar lags a lot, preventing correct typing

Processing control commands: > reassign -1 mutter/3.26.0+20170925~ea214fb-1 Unknown command or malformed arguments to command. > affects -1 epiphany-browser Bug #875826 [epiphany-browser] epiphany-browser: typing in URL bar lags a lot, preventing correct typing Added indication that 875826

Bug#869034: marked as done (ruby-combustion: FTBFS: ERROR: Test "ruby2.3" failed.)

Your message dated Sat, 30 Sep 2017 14:56:40 +0200 with message-id <20170930125640.2mz7pn7kok5qfmy2@esfahan> and subject line closed with the upload of 1.0.6-2 has caused the Debian Bug report #869034, regarding ruby-combustion: FTBFS: ERROR: Test "ruby2.3" failed. to be marked as done. This

Bug#877261: jemalloc: FTBFS on 32-bit archs: operator new/delete symbols have changed

Hi Andreas, Thanks for the bug report. On Fri, Sep 29, 2017 at 10:55:59PM +0200, Andreas Beckmann wrote: > jemalloc 5 FTBFS on all 32-bit architectures since the signatures for > operator new/delete have changed with GCC 7: I don't think it's a GCC 7 issue. I think it was just a packaging error

Processed: reassign 869034 to ruby-rails-dom-testing

Processing commands for cont...@bugs.debian.org: > reassign 869034 ruby-rails-dom-testing Bug #869034 [src:ruby-combustion] ruby-combustion: FTBFS: ERROR: Test "ruby2.3" failed. Bug reassigned from package 'src:ruby-combustion' to 'ruby-rails-dom-testing'. No longer marked as found in versions

Processed: fixed 869034 in ruby-rails-dom-testing/1.0.6-2

Processing commands for cont...@bugs.debian.org: > fixed 869034 ruby-rails-dom-testing/1.0.6-2 Bug #869034 [ruby-rails-dom-testing] ruby-combustion: FTBFS: ERROR: Test "ruby2.3" failed. Marked as fixed in versions ruby-rails-dom-testing/1.0.6-2. > thanks Stopping processing here. Please contact

Processed: notfound 869034 in ruby-combustion/0.5.4-1

Processing commands for cont...@bugs.debian.org: > notfound 869034 ruby-combustion/0.5.4-1 Bug #869034 [ruby-rails-dom-testing] ruby-combustion: FTBFS: ERROR: Test "ruby2.3" failed. Ignoring request to alter found versions of bug #869034 to the same values previously set > thanks Stopping

Processed: found 869034 in ruby-rails-dom-testing/1.0.6-1

Processing commands for cont...@bugs.debian.org: > found 869034 ruby-rails-dom-testing/1.0.6-1 Bug #869034 [ruby-rails-dom-testing] ruby-combustion: FTBFS: ERROR: Test "ruby2.3" failed. Marked as found in versions ruby-rails-dom-testing/1.0.6-1. > thanks Stopping processing here. Please contact

Bug#877295: [Pkg-kde-extras] Bug#877295: amarok build-depends on removed package libgpod-nogtk-dev

In data sabato 30 settembre 2017 14:55:34 CEST, Adrian Bunk ha scritto: > On Sat, Sep 30, 2017 at 01:28:54PM +0200, Pino Toscano wrote: > > In data sabato 30 settembre 2017 13:17:43 CEST, Adrian Bunk ha scritto: > > > libgpod-nogtk-dev was a transitional package removed in libgpod 0.8.3-9. > > >

Bug#877295: [Pkg-kde-extras] Bug#877295: amarok build-depends on removed package libgpod-nogtk-dev

On Sat, Sep 30, 2017 at 01:28:54PM +0200, Pino Toscano wrote: > In data sabato 30 settembre 2017 13:17:43 CEST, Adrian Bunk ha scritto: > > libgpod-nogtk-dev was a transitional package removed in libgpod 0.8.3-9. > > > > amarok is the only package build-depending on libgpod-nogtk-dev. > > Even

Bug#877295: [Pkg-kde-extras] Bug#877295: amarok build-depends on removed package libgpod-nogtk-dev

In data sabato 30 settembre 2017 13:17:43 CEST, Adrian Bunk ha scritto: > libgpod-nogtk-dev was a transitional package removed in libgpod 0.8.3-9. > > amarok is the only package build-depending on libgpod-nogtk-dev. Even if amarok is the only rdep, the "first I break, then I file serious bugs on

Bug#875423: [Pkg-openssl-devel] Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1 (at least in testing)

Hi, On Fri, Sep 22, 2017 at 12:21:26AM +0200, Kurt Roeckx wrote: > On Mon, Sep 11, 2017 at 12:30:30PM +0200, Raphael Hertzog wrote: > > But in Debian testing, we have real end-users (direct and through > > "rolling" derivatives) and they should not have to be impacted by this > > experiment IMO. >

Bug#877300: digikam FTBFS: undefined references

Source: digikam Version: 4:5.3.0-3 Severity: serious https://buildd.debian.org/status/package.php?p=digikam=sid ... ../models/CMakeFiles/digikamdatabasemodels_src.dir/imagemodel.cpp.o: In function `Digikam::ImageModel::ImageModel(QObject*)':

Bug#877299: haskell-tls FTBFS: Couldn't match expected type `B.ByteString' with actual type `[asn1-types-0.3.2:Data.ASN1.Types.ASN1]'

Source: haskell-tls Version: 1.3.11-1 Severity: serious https://buildd.debian.org/status/package.php?p=haskell-tls=sid ... [4 of 7] Compiling Certificate ( Tests/Certificate.hs, dist-ghc/build/test-tls/test-tls-tmp/Certificate.o ) Tests/Certificate.hs:17:72: error: * Couldn't match

Bug#877298: swift FTBFS FAIL: test_get (test.unit.common.test_db.TestDatabaseBroker)

Source: swift Version: 2.10.2-1 Severity: serious Some recent change in unstable makes swift FTBFS: https://tests.reproducible-builds.org/debian/history/swift.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/swift.html ...

Bug#853338: bossa: Patch for the build failure

Control: tags 853338 + patch Dear maintainer, This particular build failure has an easy fix available in Upstream's git repository, https://github.com/shumatech/BOSSA/commit/3ace00ee9a5a1372c321f4b97b941eb7c040ef80 I've prepared a minimal NMU and will be looking for a sponsor. You might want

Processed: bossa: Patch for the build failure

Processing control commands: > tags 853338 + patch Bug #853338 [src:bossa] bossa: ftbfs with GCC-7 Added tag(s) patch. -- 853338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#876583: marked as done (libgpod FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available)

Your message dated Sat, 30 Sep 2017 10:19:12 + with message-id and subject line Bug#876583: fixed in libgpod 0.8.3-9 has caused the Debian Bug report #876583, regarding libgpod FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available to be

Bug#877295: amarok build-depends on removed package libgpod-nogtk-dev

Source: amarok Version: 2.8.0-8 Severity: serious Tags: buster sid libgpod-nogtk-dev was a transitional package removed in libgpod 0.8.3-9. amarok is the only package build-depending on libgpod-nogtk-dev. To fix this bug, remove the first alternative from libgpod-nogtk-dev (>= 0.7.0) |

  1   2   >