Bug#897006: [petsc-maint] Bug#897006: petsc FTBFS on mips: f951: out of memory

On Sat, 2018-04-28 at 18:11 +0300, Adrian Bunk wrote: > > The failing command is: > mpif90 -c -g -O2 -fstack-protector-strong -fPIC -Wdate-time > -D_FORTIFY_SOURCE=2 -fdebug-prefix-map=/home/bunk/build/petsc- > 3.9.0+dfsg1=. -I/home/bunk/build/petsc-3.9.0+dfsg1/include >

Bug#896566: gummi: FTBFS against new libsyntex

Hi Samuel, Sebastian, Thanks for the patch. I'll take a look at it and upload the fix tomorrow if everything is fine. Cheers, Hugo -- Hugo Lefeuvre (hle)|www.owl.eu.com 4096/ 9C4F C8BF A4B0 8FC5 48EB 56B8 1962 765B B9A8 BACA signature.asc Description: PGP signature

Bug#897105: marked as done (cafeobj FTBFS with pandoc 2.1.2)

Your message dated Tue, 01 May 2018 00:49:57 + with message-id and subject line Bug#897105: fixed in cafeobj 1.5.7-2 has caused the Debian Bug report #897105, regarding cafeobj FTBFS with pandoc 2.1.2 to be marked as done. This means that you claim that

Bug#873976: proposed NMU

Hi! As this FTBFS has a patch rotting since December, let's upload it. Here's the NMU diff, I'm putting it into DELAYED/7. You know the drill, override/dcut/yell if anything. Thanks Markus for investigating and proposing the fix! Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢰⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ Certified airhead; got the

Bug#896423: marked as done (python-bcolz: bcolz fails to import)

Your message dated Mon, 30 Apr 2018 23:19:32 + with message-id and subject line Bug#896423: fixed in bcolz 1.2.1+ds1-1 has caused the Debian Bug report #896423, regarding python-bcolz: bcolz fails to import to be marked as done. This means that you claim

Bug#897261: matchbox-window-manager: Please drop Build-Depends on gconf

From: Jeremy Bicha Date: Mon, 30 Apr 2018 17:49:16 -0400 Subject: [PATCH 1/2] Add patch to fix build without gconf --- debian/patches/gconf.patch | 58 ++ debian/patches/series | 1 + 2 files changed, 59 insertions(+) create mode

Bug#896411: marked as done (python3-bcolz: bcolz fails to import)

Your message dated Mon, 30 Apr 2018 23:19:32 + with message-id and subject line Bug#896411: fixed in bcolz 1.2.1+ds1-1 has caused the Debian Bug report #896411, regarding python3-bcolz: bcolz fails to import to be marked as done. This means that you claim

Bug#897261: matchbox-window-manager: Please drop Build-Depends on gconf

Source: matchbox-window-manager Version: 1.5.3-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gconf Tags: sid buster patch Your package build-depends on libgconf2-dev, but gconf will be removed from Debian soon. gconf's last release was about 5 years

Bug#895246: gconf: Intent to Adopt

On Sun, Apr 8, 2018 at 3:19 PM, Adrian Bunk wrote: Sorry for not replying more promptly. > I hereby declare my intent to adopt gconf. Why? Basically there are only two things left in Buster that depend on gconf: eclipse and pulseaudio. pulseaudio is being worked on upstream so

Processed: severity of 888547 is grave

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

Processed: bug 896457 is forwarded to https://bugs.launchpad.net/mixxx/+bug/1768148

Processing commands for cont...@bugs.debian.org: > forwarded 896457 https://bugs.launchpad.net/mixxx/+bug/1768148 Bug #896457 [src:mixxx] mixxx FTBFS with Qt 5.10 Set Bug forwarded-to-address to 'https://bugs.launchpad.net/mixxx/+bug/1768148'. > thanks Stopping processing here. Please contact me

Bug#897258: syncevolution: Please drop Build-Depends on gconf

Source: syncevolution Version: 1.5.3-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gconf Tags: sid buster patch Your package build-depends on libgconf2-dev, but gconf will be removed from Debian soon. gconf's last release was about 5 years ago. It has

Bug#850886: marked as done (ruby2.3: Please migrate to openssl1.1 in buster)

Your message dated Mon, 30 Apr 2018 22:30:29 + with message-id and subject line Bug#897187: Removed package(s) from unstable has caused the Debian Bug report #850886, regarding ruby2.3: Please migrate to openssl1.1 in buster to be marked as done. This

Bug#889117: marked as done (ruby2.3 FTBFS with tzdata 2018c-1)

Your message dated Mon, 30 Apr 2018 22:30:29 + with message-id and subject line Bug#897187: Removed package(s) from unstable has caused the Debian Bug report #889117, regarding ruby2.3 FTBFS with tzdata 2018c-1 to be marked as done. This means that you

Bug#832020: marked as done (ruby2.3: ruby2.3_2.3.1-5 does not build with latest gdbm)

Your message dated Mon, 30 Apr 2018 22:30:29 + with message-id and subject line Bug#897187: Removed package(s) from unstable has caused the Debian Bug report #832020, regarding ruby2.3: ruby2.3_2.3.1-5 does not build with latest gdbm to be marked as done.

Bug#886086: marked as done (camorama: Depends on gconf)

Your message dated Mon, 30 Apr 2018 22:20:42 + with message-id and subject line Bug#897002: Removed package(s) from unstable has caused the Debian Bug report #886086, regarding camorama: Depends on gconf to be marked as done. This means that you claim

Bug#868388: marked as done (camorama: Please drop the (build-)dependency against gnome-vfs)

Your message dated Mon, 30 Apr 2018 22:20:42 + with message-id and subject line Bug#897002: Removed package(s) from unstable has caused the Debian Bug report #868388, regarding camorama: Please drop the (build-)dependency against gnome-vfs to be marked as

Bug#889932: marked as done (salt-formula-kubernetes: FTBFS and Debci failure with salt 2017.7.2)

Your message dated Mon, 30 Apr 2018 22:18:22 + with message-id and subject line Bug#896962: Removed package(s) from unstable has caused the Debian Bug report #889932, regarding salt-formula-kubernetes: FTBFS and Debci failure with salt 2017.7.2 to be

Bug#889927: marked as done (salt-formula-ceilometer: FTBFS and Debci failure with salt 2017.7.2)

Your message dated Mon, 30 Apr 2018 22:15:12 + with message-id and subject line Bug#896956: Removed package(s) from unstable has caused the Debian Bug report #889927, regarding salt-formula-ceilometer: FTBFS and Debci failure with salt 2017.7.2 to be

Bug#889929: marked as done (salt-formula-keyston: FTBFS and Debci failure with salt 2017.7.2)

Your message dated Mon, 30 Apr 2018 22:17:46 + with message-id and subject line Bug#896961: Removed package(s) from unstable has caused the Debian Bug report #889929, regarding salt-formula-keyston: FTBFS and Debci failure with salt 2017.7.2 to be marked

Bug#889933: marked as done (salt-formula-glance: FTBFS and Debci failure with salt 2017.7.2)

Your message dated Mon, 30 Apr 2018 22:16:09 + with message-id and subject line Bug#896958: Removed package(s) from unstable has caused the Debian Bug report #889933, regarding salt-formula-glance: FTBFS and Debci failure with salt 2017.7.2 to be marked as

Bug#889928: marked as done (salt-formula-cinder: FTBFS and Debci failure with salt 2017.7.2)

Your message dated Mon, 30 Apr 2018 22:15:40 + with message-id and subject line Bug#896957: Removed package(s) from unstable has caused the Debian Bug report #889928, regarding salt-formula-cinder: FTBFS and Debci failure with salt 2017.7.2 to be marked as

Bug#886059: marked as done (jana: Depends on gconf)

Your message dated Mon, 30 Apr 2018 22:14:44 + with message-id and subject line Bug#896694: Removed package(s) from unstable has caused the Debian Bug report #886059, regarding jana: Depends on gconf to be marked as done. This means that you claim that

Bug#897254: CVE-2018-9060

On 30 April 2018 at 23:54, Moritz Mühlenhoff wrote: | Hi Dirk, | | On Mon, Apr 30, 2018 at 04:33:48PM -0500, Dirk Eddelbuettel wrote: | > There is no GUI in R on | > Linux (there used to be a Gnome1/Gtk one a lng time ago). | | Ah, ok. I wasn't aware of that. | | Even if we'd build some

Bug#897254: marked as done (CVE-2018-9060)

Your message dated Mon, 30 Apr 2018 23:54:17 +0200 with message-id <20180430215417.GA16398@pisco.westfalen.local> and subject line Re: Bug#897254: CVE-2018-9060 has caused the Debian Bug report #897254, regarding CVE-2018-9060 to be marked as done. This means that you claim that the problem has

Bug#897237: marked as done (procyon: does not start)

Your message dated Mon, 30 Apr 2018 21:34:31 + with message-id and subject line Bug#897237: fixed in procyon 0.5.32-4 has caused the Debian Bug report #897237, regarding procyon: does not start to be marked as done. This means that you claim that the

Bug#897254: CVE-2018-9060

On 30 April 2018 at 23:18, Moritz Muehlenhoff wrote: | Source: r-base | Severity: grave | Tags: security | | Please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-9060 | | I'm not sure whether this has been properly reported to the upstream | developers. The timeline of the Github

Bug#897254: CVE-2018-9060

Source: r-base Severity: grave Tags: security Please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-9060 I'm not sure whether this has been properly reported to the upstream developers. The timeline of the Github link above mentions 03-27-18: Emailed author, no response 04-03-18:

Processed: severity of 892961 is grave

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

Processed: severity of 892962 is grave

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

Bug#893150: marked as done (fop FTBFS with openjdk-9)

Your message dated Mon, 30 Apr 2018 21:19:20 + with message-id and subject line Bug#893150: fixed in fop 1:2.1-8 has caused the Debian Bug report #893150, regarding fop FTBFS with openjdk-9 to be marked as done. This means that you claim that the problem

Bug#894319: NMU uploaded for ibus-chewing: Please drop Build-Depends on libgconf2-dev

Control: tags -1 +pending Following the example of ibus, ibus-chewing was imported to https://salsa.debian.org/debian/ibus-chewing Because I have commit access there, I pushed my minimal change there to drop the unused libgconf2-dev build-dependency. I have uploaded an NMU of ibus-chewing

Processed: NMU uploaded for ibus-chewing: Please drop Build-Depends on libgconf2-dev

Processing control commands: > tags -1 +pending Bug #894319 [src:ibus-chewing] ibus-chewing: Please drop Build-Depends on libgconf2-dev Added tag(s) pending. -- 894319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894319 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#894213: foo FTBFS with dh-python >= 3.20180313

On Mon, Apr 30, 2018 at 08:29:13PM +0200, Piotr Ożarowski wrote: > [Andreas Tille, 2018-04-30] > > Hmmm, inside pbuilder chroot the files are installed to > > > > /build/snakemake-4.8.0/.pybuild/cpython3_3.6_snakemake/build/bin/snakemake > > > > while > > > > # pybuild --print build_dir

Bug#897237: Bug #897237 in procyon marked as pending

Control: tag -1 pending Hello, Bug #897237 in procyon reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #897237 in procyon marked as pending

Processing control commands: > tag -1 pending Bug #897237 [procyon-decompiler] procyon: does not start Added tag(s) pending. -- 897237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#870253: marked as done (clamav-milter: disengaging debconf management destroys config)

Your message dated Mon, 30 Apr 2018 20:52:26 + with message-id and subject line Bug#870253: fixed in clamav 0.100.0+dfsg-0+deb8u1 has caused the Debian Bug report #870253, regarding clamav-milter: disengaging debconf management destroys config to be marked

Bug#886852: marked as done (nvidia-graphics-drivers: CVE-2017-5753/CVE-2017-5715 (spectre), CVE-2017-5754 (meltdown))

Your message dated Mon, 30 Apr 2018 20:52:30 + with message-id and subject line Bug#886852: fixed in nvidia-graphics-drivers 340.106-1 has caused the Debian Bug report #886852, regarding nvidia-graphics-drivers: CVE-2017-5753/CVE-2017-5715 (spectre),

Bug#894543: marked as done (cffi-toolchain and cffi-libffi systems are unusable)

Your message dated Mon, 30 Apr 2018 20:51:46 + with message-id and subject line Bug#894543: fixed in cffi 1:0.18.0-1+deb9u1 has caused the Debian Bug report #894543, regarding cffi-toolchain and cffi-libffi systems are unusable to be marked as done. This

Bug#875547: marked as done (animals: can't be played as non root user)

Your message dated Mon, 30 Apr 2018 20:51:46 + with message-id and subject line Bug#875547: fixed in animals 201207131226-2+deb9u1 has caused the Debian Bug report #875547, regarding animals: can't be played as non root user to be marked as done. This

Bug#894338: marked as done (nvidia-graphics-drivers: CVE-2018-6249, CVE-2018-6253: null pointer dereference and infinite recursion due to malformed shader)

Your message dated Mon, 30 Apr 2018 20:51:49 + with message-id and subject line Bug#894338: fixed in nvidia-graphics-drivers 384.130-1 has caused the Debian Bug report #894338, regarding nvidia-graphics-drivers: CVE-2018-6249, CVE-2018-6253: null pointer

Bug#870253: marked as done (clamav-milter: disengaging debconf management destroys config)

Your message dated Mon, 30 Apr 2018 20:51:47 + with message-id and subject line Bug#870253: fixed in clamav 0.100.0+dfsg-0+deb9u1 has caused the Debian Bug report #870253, regarding clamav-milter: disengaging debconf management destroys config to be marked

Bug#891127: marked as done (python-pysaml2: tests require network access)

Your message dated Mon, 30 Apr 2018 22:31:11 +0200 with message-id <0ea522b7-0b39-bb1d-0f95-66ed7ad29...@debian.org> and subject line Forgot to close bug in changelog has caused the Debian Bug report #891127, regarding python-pysaml2: tests require network access to be marked as done. This means

Processed: severity of 897010 is grave

Processing commands for cont...@bugs.debian.org: > severity 897010 grave Bug #897010 [src:lrzsz] lrzsz: CVE-2018-10195: rzsz: sz can leak data to receiving side Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 897010:

Bug#897251: pdf2djvu: FAIL: test-1px-font.test.test

Package: pdf2djvu Version: 0.9.8-1 Severity: serious Justification: fails to build from source (but built successfully in the past) A recent rebuild revealed this problem: == FAIL: test-1px-font.test.test

Bug#875346: marked as done (FTBFS with Java 9: tools.jar)

Your message dated Mon, 30 Apr 2018 22:05:03 +0200 with message-id <8f6497d1-49bb-eb3e-8978-8ce4dd5b5...@debian.org> and subject line Re: FTBFS with Java 9: tools.jar has caused the Debian Bug report #875346, regarding FTBFS with Java 9: tools.jar to be marked as done. This means that you claim

Bug#882550: marked as done (geogebra: Geogebra crashes with openjdk-9)

Your message dated Mon, 30 Apr 2018 19:35:02 + with message-id and subject line Bug#882550: fixed in geogebra 4.0.34.0+dfsg1-5 has caused the Debian Bug report #882550, regarding geogebra: Geogebra crashes with openjdk-9 to be marked as done. This means

Bug#895494: marked as done (kimap FTBFS: symbol disappeared)

Your message dated Mon, 30 Apr 2018 19:35:09 + with message-id and subject line Bug#895494: fixed in kimap 17.12.3-2 has caused the Debian Bug report #895494, regarding kimap FTBFS: symbol disappeared to be marked as done. This means that you claim that

Bug#896613: marked as done (cloud-sptheme FTBFS with sphinx 1.7.2)

Your message dated Mon, 30 Apr 2018 19:19:29 + with message-id and subject line Bug#896613: fixed in cloud-sptheme 1.9.4-1 has caused the Debian Bug report #896613, regarding cloud-sptheme FTBFS with sphinx 1.7.2 to be marked as done. This means that you

Processed: Bug #896613 in cloud-sptheme marked as pending

Processing control commands: > tag -1 pending Bug #896613 [src:cloud-sptheme] cloud-sptheme FTBFS with sphinx 1.7.2 Added tag(s) pending. -- 896613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#896613: Bug #896613 in cloud-sptheme marked as pending

Control: tag -1 pending Hello, Bug #896613 in cloud-sptheme reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#896410: marked as done (python-flask-limiter: flask_limiter fails to import)

Your message dated Mon, 30 Apr 2018 18:35:21 + with message-id and subject line Bug#896410: fixed in flask-limiter 1.0.1-1 has caused the Debian Bug report #896410, regarding python-flask-limiter: flask_limiter fails to import to be marked as done. This

Bug#896276: marked as done (python3-flask-limiter: flask_limiter fails to import)

Your message dated Mon, 30 Apr 2018 18:35:21 + with message-id and subject line Bug#896276: fixed in flask-limiter 1.0.1-1 has caused the Debian Bug report #896276, regarding python3-flask-limiter: flask_limiter fails to import to be marked as done. This

Bug#852515: marked as done (python-flask-limiter-doc: overwrites files from python-limits-doc: /usr/share/doc/python-limits-doc/html/_modules/index.html)

Your message dated Mon, 30 Apr 2018 18:35:21 + with message-id and subject line Bug#852515: fixed in flask-limiter 1.0.1-1 has caused the Debian Bug report #852515, regarding python-flask-limiter-doc: overwrites files from python-limits-doc:

Bug#894213: foo FTBFS with dh-python >= 3.20180313

[Andreas Tille, 2018-04-30] > On Mon, Apr 30, 2018 at 03:57:51PM +0200, Piotr Ożarowski wrote: > > [Andreas Tille, 2018-04-30] > > > > PYTHONPATH=$(shell pybuild --print build_dir --interpreter python3) ... > > > I tried the same trick for snakemake in Git[1] but failed. > > > > > > Am I missing

Bug#894213: foo FTBFS with dh-python >= 3.20180313

On Mon, Apr 30, 2018 at 03:57:51PM +0200, Piotr Ożarowski wrote: > [Andreas Tille, 2018-04-30] > > > PYTHONPATH=$(shell pybuild --print build_dir --interpreter python3) ... > > I tried the same trick for snakemake in Git[1] but failed. > > > > Am I missing something? > > you changed PYTHONPATH,

Bug#896451: marked as done (shelxle FTBFS due to round() macro)

Your message dated Mon, 30 Apr 2018 17:20:23 + with message-id and subject line Bug#896451: fixed in shelxle 1.0.912-1 has caused the Debian Bug report #896451, regarding shelxle FTBFS due to round() macro to be marked as done. This means that you claim

Bug#897242: chromium: FTBFS on armhf: linker runs out of memory

Source: chromium-browser Version: 66.0.3359.139-1 Severity: serious Hi, As you know, chromium has been failing to build on armhf for a while now. That's specially bad as it's blocking testing migration, causing testing users to run a pretty old version with several security vulnerabilities. I

Processed: Bug #896276 in flask-limiter marked as pending

Processing control commands: > tag -1 pending Bug #896276 [python3-flask-limiter] python3-flask-limiter: flask_limiter fails to import Added tag(s) pending. -- 896276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896276 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#896276: Bug #896276 in flask-limiter marked as pending

Control: tag -1 pending Hello, Bug #896276 in flask-limiter reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#896410: Bug #896410 in flask-limiter marked as pending

Control: tag -1 pending Hello, Bug #896410 in flask-limiter reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #896410 in flask-limiter marked as pending

Processing control commands: > tag -1 pending Bug #896410 [python-flask-limiter] python-flask-limiter: flask_limiter fails to import Added tag(s) pending. -- 896410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#897239: librelion+mpi+gui-dev: uninstallable everywhere but on amd64,i386

Package: librelion+mpi+gui-dev Version: 1.4+dfsg-3 Severity: serious Hi, librelion+mpi+gui-dev depends on librelion+mpi+gui-1.4-1, which is only built on amd64/i386. Now that librelion+mpi+gui-dev is built on other architectures, it has become uninstallable. Please either restrict

Bug#893367: marked as done ("smtpctl stop" not supported by upstream anymore)

Your message dated Mon, 30 Apr 2018 16:49:31 + with message-id and subject line Bug#893367: fixed in opensmtpd 6.0.3p1-4 has caused the Debian Bug report #893367, regarding "smtpctl stop" not supported by upstream anymore to be marked as done. This means

Bug#897237: procyon: does not start

Package: procyon-decompiler Version: 0.5.32-3 Severity: grave Dear Maintainer, procyon is not able to start: $ procyon --help Cannot use final field com.strobel.decompiler.CommandLineOptions#_inputs as a parameter; compile-time constant inlining may hide new values written to it. This happens

Bug#837208: marked as done (python-ofxclient: chokes on %{secured})

Your message dated Mon, 30 Apr 2018 17:48:46 +0200 with message-id <3e0c60e7-15a2-56bc-293c-90a830a54...@collabora.co.uk> and subject line Re: python-ofxclient: chokes on %{secured} has caused the Debian Bug report #837208, regarding python-ofxclient: chokes on %{secured} to be marked as done.

Bug#896373: marked as done (python3-versiontools: versiontools fails to import)

Your message dated Mon, 30 Apr 2018 15:09:48 + with message-id and subject line Bug#896373: fixed in versiontools 1.9.1-3 has caused the Debian Bug report #896373, regarding python3-versiontools: versiontools fails to import to be marked as done. This

Bug#896571: marked as done (python-pyngus FTBFS: test failure)

Your message dated Mon, 30 Apr 2018 15:08:58 + with message-id and subject line Bug#896571: fixed in python-pyngus 2.2.2-3 has caused the Debian Bug report #896571, regarding python-pyngus FTBFS: test failure to be marked as done. This means that you

Bug#891659: marked as done (murano-common: ships files also in murano-api, murano-engine)

Your message dated Mon, 30 Apr 2018 15:06:40 + with message-id and subject line Bug#891659: fixed in murano 1:5.0.0-1 has caused the Debian Bug report #891659, regarding murano-common: ships files also in murano-api, murano-engine to be marked as done.

Bug#880794: marked as done (rakudo FTBFS on big endian: Unhandled exception: Bytecode validation error)

Your message dated Mon, 30 Apr 2018 16:24:43 +0200 with message-id <20180430142443.mhiytb2s7exty...@semistable.com> and subject line bytecode validation problems has caused the Debian Bug report #880794, regarding rakudo FTBFS on big endian: Unhandled exception: Bytecode validation error to be

Bug#894213: foo FTBFS with dh-python >= 3.20180313

[Andreas Tille, 2018-04-30] > > PYTHONPATH=$(shell pybuild --print build_dir --interpreter python3) ... > > This worked nicely for python-skbio. > > > I fixed few packages already, here's a list of other affected ones: > > ... > > snakemake Debian Med Packaging Team > > I tried the same

Bug#897226: Fwd: Bug#897226: [gimp] gimp cannot start with symbol lookup error

Forwarding reply to the bug tracker since it shows the resolution of this issue. Jeremy Bicha -- Forwarded message -- From: Hideo Oshima Date: Mon, Apr 30, 2018 at 9:18 AM Subject: Re: Bug#897226: [gimp] gimp cannot start with symbol lookup error To:

Bug#896571: Bug #896571 in python-pyngus marked as pending

Control: tag -1 pending Hello, Bug #896571 in python-pyngus reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #896571 in python-pyngus marked as pending

Processing control commands: > tag -1 pending Bug #896571 [src:python-pyngus] python-pyngus FTBFS: test failure Ignoring request to alter tags of bug #896571 to the same tags previously set -- 896571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896571 Debian Bug Tracking System Contact

Processed: Bug #896571 in python-pyngus marked as pending

Processing control commands: > tag -1 pending Bug #896571 [src:python-pyngus] python-pyngus FTBFS: test failure Added tag(s) pending. -- 896571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#896571: Bug #896571 in python-pyngus marked as pending

Control: tag -1 pending Hello, Bug #896571 in python-pyngus reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug#897226: [gimp] gimp cannot start with symbol lookup error

Processing commands for cont...@bugs.debian.org: > forcemerge 896091 897226 Bug #896091 {Done: Jeremy Bicha } [gimp] gimp fails to run with a symbol lookup error: undefined symbol: babl_process_rows Bug #896091 {Done: Jeremy Bicha } [gimp] gimp fails to run

Bug#896758: grokevt: missing build dependency on python3-distutils

Hello Adrian, Thanks for reporting that, i will prepare a fix today. -- Samuel Henrique

Bug#874660: marked as done (FTBFS with Java 9: sun.misc)

Your message dated Mon, 30 Apr 2018 15:27:55 +0200 with message-id <985308bd-8eb0-3e32-9248-14bb3e73a...@debian.org> and subject line Re: FTBFS with Java 9: sun.misc has caused the Debian Bug report #874660, regarding FTBFS with Java 9: sun.misc to be marked as done. This means that you claim

Bug#896701: marked as done (drupal7: CVE-2018-7602: SA-CORE-2018-004)

Your message dated Mon, 30 Apr 2018 13:17:40 + with message-id and subject line Bug#896701: fixed in drupal7 7.32-1+deb8u12 has caused the Debian Bug report #896701, regarding drupal7: CVE-2018-7602: SA-CORE-2018-004 to be marked as done. This means that

Bug#896701: marked as done (drupal7: CVE-2018-7602: SA-CORE-2018-004)

Your message dated Mon, 30 Apr 2018 13:17:08 + with message-id and subject line Bug#896701: fixed in drupal7 7.52-2+deb9u4 has caused the Debian Bug report #896701, regarding drupal7: CVE-2018-7602: SA-CORE-2018-004 to be marked as done. This means that

Bug#896548: marked as done (gunicorn: CVE-2018-1000164)

Your message dated Mon, 30 Apr 2018 13:17:40 + with message-id and subject line Bug#896548: fixed in gunicorn 19.0-1+deb8u1 has caused the Debian Bug report #896548, regarding gunicorn: CVE-2018-1000164 to be marked as done. This means that you claim that

Bug#897214: Fixed in 6.1.7-1

seafile-6.1.7-1 is still stuck in NEW queue. Am 30.04.2018 um 10:24 schrieb Moritz Schlarb: > Control: fixed -1 seafile-cli/6.1.7-1 > Control: tags -1 + fixed pending > > This will be resolved as soon as src:seafile/6.1.7-1 finally migrates... > --

Bug#894213: foo FTBFS with dh-python >= 3.20180313

Hi Piotr, On Thu, Apr 26, 2018 at 12:01:17PM +0200, Piotr Ożarowski wrote: > [Andreas Tille, 2018-04-26] > >ModuleNotFoundError: No module named 'skbio' > > that's because I had to change pybuild's internal paths (to make it work > with multiple modules/packages at the same time). > > I

Bug#896483: beast-mcmc FTBFS with TeX Live 2018

Control: tags -1 help Hi On Sat, Apr 21, 2018 at 05:57:50PM +0300, Adrian Bunk wrote: > > Fix is attached. I tried this patch in Git[1] but when I build the packag I'm running into ... This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018/Debian) (preloaded format=pdflatex)

Processed: Re: Bug#896483: beast-mcmc FTBFS with TeX Live 2018

Processing control commands: > tags -1 help Bug #896483 [src:beast-mcmc] beast-mcmc FTBFS with TeX Live 2018 Added tag(s) help. -- 896483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#879937: [Pkg-ayatana-devel] Bug#879937: libqtdbustest: FTBFS: unit test fails with BadAddress DBusException

On Fr 27 Okt 2017 16:45:02 CEST, ucko wrote: Mike Gabriel writes: Sooo... My assumption was, that this was related to some package upgrades in the archive. Maybe packages that have not reached the archtitectures, that showed the test failures on buildd.

Bug#897110: marked as done (libpandoc-wrapper-perl FTBFS with pandoc 2.1.2)

Your message dated Mon, 30 Apr 2018 10:34:59 + with message-id and subject line Bug#897110: fixed in libpandoc-wrapper-perl 0.8.0-1 has caused the Debian Bug report #897110, regarding libpandoc-wrapper-perl FTBFS with pandoc 2.1.2 to be marked as done.

Bug#891126: marked as done (python-proliantutils: FTBFS with TypeError: refresh() got an unexpected keyword argument 'force')

Your message dated Mon, 30 Apr 2018 11:48:17 +0200 with message-id <293aaa45-ffd9-1b46-7b7a-d7b2736d5...@debian.org> and subject line Without reply from submitter, closing has caused the Debian Bug report #891126, regarding python-proliantutils: FTBFS with TypeError: refresh() got an unexpected

Processed: Re: Bug#897108: gitano FTBFS with pandoc 2.1.2

Processing commands for cont...@bugs.debian.org: > forwarded 897108 https://trello.com/c/CrnBZptB/275 Bug #897108 [src:gitano] gitano FTBFS with pandoc 2.1.2 Set Bug forwarded-to-address to 'https://trello.com/c/CrnBZptB/275'. > thanks Stopping processing here. Please contact me if you need

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 897214 seafile/6.1.7-1 Bug #897214 [seafile-cli] seafile-cli: Depends on python-ccnet which is not a listed as a dependency Marked as fixed in versions seafile/6.1.7-1. > -- Stopping processing here. Please contact me if you need

Bug#896550: kazam: Binding 'R' failed!

On 29/04/2018 20:45, Andrew Starr-Bochicchio wrote: Could you please provide a bit more info about your set up to help track down the root cause here? ok, tell me what you want to know What desktop environment is in use? $ dpkg -l | grep " gnome " ii gnome1:3.22+9 amd64 I have

Bug#897108: gitano FTBFS with pandoc 2.1.2

forward 897108 https://trello.com/c/CrnBZptB/275 thanks On Sat, Apr 28, 2018 at 17:28:31 +0300, Adrian Bunk wrote: > pandoc --standalone --toc --chapters -V documentclass:report -V > geometry:margin=1in -V graphics:true -V papersize:a4paper -H titling.tex -H > header.tex -o gitano-admin-doc.pdf

Bug#897214: Fixed in 6.1.7-1

Control: fixed -1 seafile-cli/6.1.7-1 Control: tags -1 + fixed pending This will be resolved as soon as src:seafile/6.1.7-1 finally migrates... -- Moritz Schlarb

Processed: Fixed in 6.1.7-1

Processing control commands: > fixed -1 seafile-cli/6.1.7-1 Bug #897214 [seafile-cli] seafile-cli: Depends on python-ccnet which is not a listed as a dependency The source seafile-cli and version 6.1.7-1 do not appear to match any binary packages Marked as fixed in versions seafile-cli/6.1.7-1.

Bug#897214: seafile-cli: Depends on python-ccnet which is not a listed as a dependency

Package: seafile-cli Version: 6.1.5-1 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, seafile stopped working after an upgrade of sid. Required and install of "python-ccnet" which is not a listed dependency. -- System Information: Debian Release: