Processed: Bug#880528 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 880528 pending Bug #880528 {Done: Craig Small } [src:wordpress] wordpress: CVE-2017-16510: Unsafe queries with wpdb->prepare Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Bug#880528: marked as pending

tag 880528 pending thanks Hello, Bug #880528 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/collab-maint/wordpress.git/commit/?id=88c9ef8 --- commit

Bug#865975: docker.io breaks (bridged) network for VMs

On Sun, Oct 22, 2017 at 02:00:58AM +0200, Alban Browaeys wrote: > or a config item in /etc/docker/daemon.json: > { > "iptables": false > } Seems like the docker.io package should ship this as a conffile then.

Bug#885631: marked as done (src:juffed: Will FTBFS with new qscintilla2)

Your message dated Thu, 04 Jan 2018 02:52:39 + with message-id and subject line Bug#885631: fixed in juffed 0.10-85-g5ba17f9-17 has caused the Debian Bug report #885631, regarding src:juffed: Will FTBFS with new qscintilla2 to be marked as done. This

Bug#886119: marked as done (e2fsprogs: FTBFS on big-endian architectures)

Your message dated Thu, 04 Jan 2018 01:04:02 + with message-id and subject line Bug#886119: fixed in e2fsprogs 1.43.8-2 has caused the Debian Bug report #886119, regarding e2fsprogs: FTBFS on big-endian architectures to be marked as done. This means that

Processed: Not a problem in stretch

Processing commands for cont...@bugs.debian.org: > tags 885961 buster sid Bug #885961 [src:util-vserver] FTBFS: __kernel_rwf_t in 4.14 kernel headers Added tag(s) sid and buster. > tags 885955 buster sid Bug #885955 [src:jcc] FTBFS: /usr/bin/ld: cannot find -ljvm Added tag(s) sid and buster. >

Bug#883526: marked as done (geeqie build does not trap errors from make)

Your message dated Wed, 03 Jan 2018 23:20:03 + with message-id and subject line Bug#883526: fixed in geeqie 1:1.4-1 has caused the Debian Bug report #883526, regarding geeqie build does not trap errors from make to be marked as done. This means that you

Processed: Not a problem in stretch

Processing commands for cont...@bugs.debian.org: > tags 867950 buster sid Bug #867950 [mailnag] mailnag: Uses deprecated gir1.2-gnomekeyring-1.0 Added tag(s) sid and buster. > tags 867946 buster sid Bug #867946 [src:libsocialweb] libsocialweb: Build-Depends on deprecated libgnome-keyring-dev

Bug#886290: node-timed-out: FTBFS: Assumes

Source: node-timed-out Version: 4.0.1-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, node-timed-out fails to build from source in

Processed: Not an RC issue for stretch

Processing commands for cont...@bugs.debian.org: > tags 867561 buster sid Bug #867561 {Done: Didier Raboud } [hplip-gui] hplip-gui: Depending on gksu is not good Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#787527: Google

What is going on

Bug#886288: node-macaddress: FTBFS: Assumes build environment has network interfaces

Source: node-macaddress Version: 0.2.8-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, node-macaddress fails to build from source in

Bug#886287: node-coveralls: FTBFS: makes assumptions about build path

Source: node-coveralls 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, node-coveralls fails to build from source in

Bug#878588: marked as done (sysbench must pass --without-gcc-arch to configure)

Your message dated Wed, 03 Jan 2018 22:35:10 + with message-id and subject line Bug#878588: fixed in sysbench 1.0.11+ds-1 has caused the Debian Bug report #878588, regarding sysbench must pass --without-gcc-arch to configure to be marked as done. This

Bug#878429: marked as done (octave-ltfat: FTBFS on mips(el): tests time out)

Your message dated Wed, 3 Jan 2018 23:26:55 +0100 with message-id <20180103222655.gd3...@laboissiere.net> and subject line Re: [Pkg-octave-devel] Bug#878429: octave-ltfat: FTBFS on mips(el): tests time out has caused the Debian Bug report #878429, regarding octave-ltfat: FTBFS on mips(el): tests

Bug#886133: ndpi: FTBFS on mips, s390x, powerpc, and ppc64: tests time out

Thank you for looking into this. On Tue, Jan 2, 2018 at 12:15 PM Aaron M. Ucko wrote: > > It so happens that I was having a brief look already :) > > Great, thanks! > > > The hang occurs inside the above while loop. Notice that the value > > loaded into "label" inside the loop

Bug#886133: ndpi: FTBFS on mips, s390x, powerpc, and ppc64: tests time out

On 2018-01-02 10:57, Aaron M. Ucko wrote: > Source: ndpi > Version: 2.2-1 > Severity: serious > Tags: upstream > Justification: fails to build from source (but built successfully in the past) > User: debian-m...@lists.debian.org > Usertags: mips > > Builds of ndpi for mips, s390x, and the

Bug#884236: marked as done (fis-gtm FTBFS with linux-libc-dev 4.14.2-1)

Your message dated Wed, 03 Jan 2018 21:34:46 + with message-id and subject line Bug#884236: fixed in fis-gtm 6.3-002-4 has caused the Debian Bug report #884236, regarding fis-gtm FTBFS with linux-libc-dev 4.14.2-1 to be marked as done. This means that you

Bug#884200: marked as done (libsynthesis FTBFS with libical3)

Your message dated Wed, 03 Jan 2018 21:12:01 + with message-id and subject line Bug#884200: fixed in libsynthesis 3.4.0.47.5+syncevolution-1.5.2-3 has caused the Debian Bug report #884200, regarding libsynthesis FTBFS with libical3 to be marked as done.

Processed: Not a problem in stretch

Processing commands for cont...@bugs.debian.org: > tags 885252 buster sid Bug #885252 [src:yahtzeesharp] yahtzeesharp: Build-Depends on libart2.0-cil-dev Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 885252:

Processed: Not a problem in stretch

Processing commands for cont...@bugs.debian.org: > tags 867929 buster sid Bug #867929 [src:bisho] bisho: Build-Depends on deprecated libgnome-keyring-dev Added tag(s) sid and buster. > tags 674107 buster sid Bug #674107 [mx] mx: Consider dropping libcluttergesture-dev build-depends Added tag(s)

Processed: Not a problem in stretch

Processing commands for cont...@bugs.debian.org: > tags 885134 buster sid Bug #885134 {Done: Debian FTP Masters } [src:gnome-icon-theme-extras] gnome-icon-theme-extras: Don't include in Debian Added tag(s) sid and buster. > thanks Stopping processing here.

Bug#883100: Bug#886245: RM: ksudoku [armel armhf] -- ROM; does not support Desktop OpenGL

On mercoledì 3 gennaio 2018 20:48:25 CET Adrian Bunk wrote: > On Wed, Jan 03, 2018 at 07:32:46PM +0100, Pino Toscano wrote: > > On mercoledì 3 gennaio 2018 20:26:53 CET Adrian Bunk wrote: > > > On Wed, Jan 03, 2018 at 07:14:58PM +0100, Pino Toscano wrote: > > > > On mercoledì 3 gennaio 2018

Processed: Not a problem in stretch

Processing commands for cont...@bugs.debian.org: > tags 885133 buster sid Bug #885133 {Done: Debian FTP Masters } [src:gnome-search-tool] gnome-search-tool: Don't include in Buster Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me

Bug#883100: Bug#886245: RM: ksudoku [armel armhf] -- ROM; does not support Desktop OpenGL

On Wed, Jan 03, 2018 at 07:32:46PM +0100, Pino Toscano wrote: > On mercoledì 3 gennaio 2018 20:26:53 CET Adrian Bunk wrote: > > On Wed, Jan 03, 2018 at 07:14:58PM +0100, Pino Toscano wrote: > > > On mercoledì 3 gennaio 2018 20:12:05 CET Adrian Bunk wrote: > > >... > > > > Regarding ksudoku, is

Processed: Not a problem in stretch

Processing commands for cont...@bugs.debian.org: > tags 879034 buster sid Bug #879034 [pdfshuffler] pdfshuffler: port to gir1.2-poppler-0.18 Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 879034:

Processed: lower severity of pygtkspellcheck to match zim's pygtk bug

Processing commands for cont...@bugs.debian.org: > severity 885375 important Bug #885375 [src:pygtkspellcheck] pygtkspellcheck: Depends on unmaintained pygtk Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. --

Bug#886275: gourmet: Don't depend on python-poppler

From 1cf2c5fbd5520fdf16c2d9aab401329fc00ba930 Mon Sep 17 00:00:00 2001 From: Jeremy Bicha Date: Wed, 3 Jan 2018 12:49:20 -0500 Subject: [PATCH] Don't depend on python-poppler since it's being removed from Debian and don't install the printing plugin. Thanks Steve Langasek.

Bug#886275: gourmet: Don't depend on python-poppler

Source: gourmet Version: 0.17.4-4 Severity: serious Tags: patch pending X-Debbugs-CC: steve.langa...@ubuntu.com I am uploading an NMU to the DELAYED/10 queue to drop the python-poppler dependency and not install gourmet's printing plugin since that seems more reasonable than dropping gourmet

Bug#885829: marked as done (lios: Lios crashing on start)

Your message dated Wed, 03 Jan 2018 17:49:58 + with message-id and subject line Bug#885829: fixed in lios 2.7-1 has caused the Debian Bug report #885829, regarding lios: Lios crashing on start to be marked as done. This means that you claim that the

Bug#873370: marked as done (kmenuedit: All versions in repositories are extremely out of date.)

Your message dated Wed, 3 Jan 2018 14:32:33 -0300 with message-id <20180103173229.ojun3lyvtj7bp...@neoptolemo.gnuservers.com.ar> and subject line Re: Bug#873370: kmenuedit: All versions in repositories are extremely out of date. has caused the Debian Bug report #873370, regarding kmenuedit: All

Bug#873370: kmenuedit: All versions in repositories are extremely out of date.

¡Hola Brice! El 2017-08-26 a las 21:51 -0600, Brice Hunt escribió: Package: kmenuedit Version: 4:5.8.4-1 Severity: grave Don't abuse the bug severities. Justification: renders package unusable The out of date kmenuedit saves configuration files in the wrong directories, causing most

Processed: tagging 885829

Processing commands for cont...@bugs.debian.org: > tags 885829 + pending Bug #885829 [lios] lios: Lios crashing on start Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 885829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885829 Debian

Bug#869484: marked as done (haskell-stack: << build dependencies on packages with a more recent version)

Your message dated Wed, 03 Jan 2018 17:04:39 + with message-id and subject line Bug#869484: fixed in haskell-stack 1.5.1-1 has caused the Debian Bug report #869484, regarding haskell-stack: << build dependencies on packages with a more recent version to

Bug#878009: marked as done (easytag fails to add tags to .ogg files)

Your message dated Wed, 03 Jan 2018 17:04:24 + with message-id and subject line Bug#855251: fixed in easytag 2.4.3-2 has caused the Debian Bug report #855251, regarding easytag fails to add tags to .ogg files to be marked as done. This means that you

Bug#855251: marked as done (easytag corrupt ogg files)

Your message dated Wed, 03 Jan 2018 17:04:24 + with message-id and subject line Bug#855251: fixed in easytag 2.4.3-2 has caused the Debian Bug report #855251, regarding easytag corrupt ogg files to be marked as done. This means that you claim that the

Bug#871091: marked as done (khotkeys: FTBFS: make[4]: *** No rule to make target 'app/org.kde.khotkeys.xml', needed by 'kcm_hotkeys/khotkeys_interface.cpp'. Stop.)

Your message dated Wed, 3 Jan 2018 13:56:48 -0300 with message-id <20180103165645.n3vqxmgw2pyzx...@neoptolemo.gnuservers.com.ar> and subject line Re: Bug#871091: khotkeys: FTBFS: make[4]: *** No rule to make target 'app/org.kde.khotkeys.xml', needed by 'kcm_hotkeys/khotkeys_interface.cpp'. Stop.

Bug#855251: easytag corrupt ogg files

Control: clone -1 -2 Control: notfound -2 2.4.3-1 Control: found -2 2.4.3-2 Control: severity -2 normal Control: tags -2 - pending Control: retitle -2 easytag: re-enable ogg after corruption bug is fixed Hi, On 16/02/17 01:02, Samuele Battarra wrote: > Package: easytag > Version: 2.4.3-1 >

Processed (with 6 errors): Re: Bug#855251: easytag corrupt ogg files

Processing control commands: > clone -1 -2 Bug #855251 [easytag] easytag corrupt ogg files Bug #878009 [easytag] easytag fails to add tags to .ogg files Failed to clone 855251: Bug is marked as being merged with others. Use an existing clone. > notfound -2 2.4.3-1 Failed to remove found on -2:

Processed: Bug#855251 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 855251 pending Bug #855251 [easytag] easytag corrupt ogg files Bug #878009 [easytag] easytag fails to add tags to .ogg files Added tag(s) pending. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Bug#855251: marked as pending

tag 855251 pending thanks Hello, Bug #855251 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: http://anonscm.debian.org/git/pkg-multimedia/easytag.git/commit/?id=82a46fb --- commit

Bug#886224: printer-driver-cups-pdf: Virtual pdf printer error: no output and config problem

You are right - the cups pdf printer is now working. I changed the pdf output directory a long time ago before using Apparmor, but now Apparmor needs to allow rw access to this directory. So I updated /etc/apparmor.d/usr.sbin.cupsd and the pdf printing works. The config problem remains

Bug#884196: marked as done (debtags FTBFS with pyflakes 1.6.0-1)

Your message dated Wed, 03 Jan 2018 16:19:15 + with message-id and subject line Bug#884196: fixed in debtags 2.1.5 has caused the Debian Bug report #884196, regarding debtags FTBFS with pyflakes 1.6.0-1 to be marked as done. This means that you claim that

Bug#885793: #885793: tldr-py,tldr: File collision when installing together: /usr/bin/tldr (and maybe further files)

On Wed, Jan 03, 2018 at 04:48:12PM +0100, Ondrej Novy wrote: > I prefer to use update-alternatives. > > What do you think Clint? I haven't looked at the different implementations but alternatives sounds like the right answer to me.

Bug#790176: guake gtk3

Hi The upstream are working hard to port guake to gtk3, I hope upload the new version soon. Regards! -- Daniel Echeverry http://wiki.debian.org/DanielEcheverry http://rinconinformatico.net Linux user: #477840 Debian user

Bug#885793: #885793: tldr-py,tldr: File collision when installing together: /usr/bin/tldr (and maybe further files)

Hi, I prefer to use update-alternatives. What do you think Clint? -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B

Bug#878216: Info received (Regression in linux in jessie-proposed-updates)

Hi again, As problem is too in Vanilla flavour, must we open a ticket directly at kernel.org ? (Or should we wait some answer here first ?) Best regards Vince

Bug#886117: FTBFS: most of testsuite

On Wed, Jan 03, 2018 at 06:29:06PM +1000, Alexander Zangerl wrote: > On Tue, 02 Jan 2018 14:40:33 +0100, Adam Borowski writes: > >I'm afraid that your package fails to build on current unstable, failing the > >vast majority of tests: > > looks like every one of the failed tests fails for the same

Processed: severity of 885111 is important

Processing commands for cont...@bugs.debian.org: > severity 885111 important Bug #885111 [kdepim-runtime] kdepim-runtime: kdepim-runtime depends on libkolab-dev Bug #886107 [kdepim-runtime] kdepim: depends on a lot of developer packages Severity set to 'important' from 'serious' Severity set to

Bug#885111: Note that this bug prevents to install libssl-dev and force libssl1.0-dev => severity should be raised

Dear user, On mercoledì 3 gennaio 2018 14:54:08 CET Eric Valette wrote: > severity 885111 serious Please do not bump the severity of bugs with random criterias. Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.

Bug#884466: mesa: firefox, thunderbird, chromium don't start with mesa 17.3.0-1

Package: libglx-mesa0 Followup-For: Bug #884466 This works for me with [AMD/ATI] Baffin [Radeon RX 460] (rev cf) I can open chromium and firefox just fine. -- System Information: Debian Release: 9.3 APT prefers stable APT policy: (900, 'stable'), (505, 'oldstable'), (500, 'oldoldstable'),

Bug#886224: printer-driver-cups-pdf: Virtual pdf printer error: no output and config problem

2018-01-03 11:51 GMT+02:00 Rudolf Polzer : > Package: printer-driver-cups-pdf > Version: 3.0.1-4 > Severity: grave > Justification: renders package unusable > > > > -- System Information: > Debian Release: buster/sid > APT prefers stable-updates > APT policy: (500,

Processed (with 1 error): Rize severity correctly

Processing commands for cont...@bugs.debian.org: > severity 885111 serious Bug #885111 [kdepim-runtime] kdepim-runtime: kdepim-runtime depends on libkolab-dev Bug #886107 [kdepim-runtime] kdepim: depends on a lot of developer packages Severity set to 'serious' from 'wishlist' Severity set to

Processed: retitle 886024 to dh-elpa: make maintainer scripts more robust, severity of 886024 is important

Processing commands for cont...@bugs.debian.org: > retitle 886024 dh-elpa: make maintainer scripts more robust Bug #886024 [dh-elpa] dh-elpa: make maintainer scripts more robust, severity it importnat Changed Bug title to 'dh-elpa: make maintainer scripts more robust' from 'dh-elpa: make

Processed: reassign 886024 to dh-elpa ...

Processing commands for cont...@bugs.debian.org: > reassign 886024 dh-elpa Bug #886024 [emacsen-common, markdown-mode] emacsen-addon package installation may never comes to an end Bug reassigned from package 'emacsen-common, markdown-mode' to 'dh-elpa'. Ignoring request to alter found versions

Bug#785562: Status update

Am 01.01.2018 um 17:55 schrieb gregor herrmann: > On Sat, 16 Dec 2017 23:41:05 +0100, Dr. Tobias Quathamer wrote: >> Am 15.12.2017 um 16:51 schrieb Emilio Pozuelo Monfort: [...] >>> Why was this renamed to openshot-qt? Upstream is still called 'openshot', >>> so I'm >>> not sure it makes sense

Bug#886024: split off anything-el related part

On Wed, Jan 3, 2018, at 03:45, H.-Dirk Schmitt wrote: > On Mi, 2018-01-03 at 02:06 +0200, era eriksson wrote: > > Code outline for an emacs batch wrapper > > I do not insist on bash – you are free to fix it in any programming > language ;-) A fair amont of work has gone into

Bug#858736: marked as done (xul-ext-gcontactsync: Depends on icedove or iceape but not thunderbird)

Your message dated Wed, 03 Jan 2018 11:04:43 + with message-id and subject line Bug#858736: fixed in gcontactsync 2.0.13-1 has caused the Debian Bug report #858736, regarding xul-ext-gcontactsync: Depends on icedove or iceape but not thunderbird to be

Bug#885603: gajim in stretch-backports depends on python3-nbxmpp, which is not in stretch-backports

Thank you so much! Patrik On Sun, Dec 31, 2017 at 12:44:54AM +0100, W. Martin Borgert wrote: > Dear Patrik, > > python-nbxmpp (which includes python3-nbxmpp) is now in backports. > Gajim should be installablen now! > > Have fun! signature.asc Description: PGP signature

Bug#884204: marked as done (webcit FTBFS with libical3)

Your message dated Wed, 03 Jan 2018 10:21:04 + with message-id and subject line Bug#884204: fixed in webcit 916-dfsg-1 has caused the Debian Bug report #884204, regarding webcit FTBFS with libical3 to be marked as done. This means that you claim that the

Bug#859789: marked as done (webcit: Please migrate to openssl1.1 in Buster)

Your message dated Wed, 03 Jan 2018 10:21:04 + with message-id and subject line Bug#859789: fixed in webcit 916-dfsg-1 has caused the Debian Bug report #859789, regarding webcit: Please migrate to openssl1.1 in Buster to be marked as done. This means that

Bug#884203: marked as done (citadel FTBFS with libical3)

Your message dated Wed, 03 Jan 2018 10:19:25 + with message-id and subject line Bug#884203: fixed in citadel 916-1 has caused the Debian Bug report #884203, regarding citadel FTBFS with libical3 to be marked as done. This means that you claim that the

Bug#851086: marked as done (citadel: Please migrate to openssl1.1 in buster)

Your message dated Wed, 03 Jan 2018 10:19:25 + with message-id and subject line Bug#851086: fixed in citadel 916-1 has caused the Debian Bug report #851086, regarding citadel: Please migrate to openssl1.1 in buster to be marked as done. This means that

Bug#886224: printer-driver-cups-pdf: Virtual pdf printer error: no output and config problem

Package: printer-driver-cups-pdf Version: 3.0.1-4 Severity: grave Justification: renders package unusable -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign

Bug#886200: FTBFS: XPA$ERROR: invalid host name specified: $host:$port.

Control: tag -1 moreinfo Hi Adam, I couldn't reproduce this on amd64; my test build runs fine (see attached log). Did you change anything in the setup of the machine between the successfull and the failing build? Specifically in the networking? Since xpa is a network protocol, it needs at least

Processed: FTBFS: XPA$ERROR: invalid host name specified: $host:$port.

Processing control commands: > tag -1 moreinfo Bug #886200 [src:xpa] FTBFS: XPA$ERROR: invalid host name specified: $host:$port. Added tag(s) moreinfo. -- 886200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#886218: ostree: FTBFS on big-endian CPUs: test failure in tests/test-basic-user-only.sh

Source: ostree Version: 2017.15-1 Severity: serious Tags: patch pending upstream Justification: fails to build from source (but built successfully in the past) Forwarded: https://github.com/ostreedev/ostree/issues/1392 ostree fails to build from source on mips, s390x, hppa, powerpc, ppc64 and

Bug#886117: FTBFS: most of testsuite

On Tue, 02 Jan 2018 14:40:33 +0100, Adam Borowski writes: >I'm afraid that your package fails to build on current unstable, failing the >vast majority of tests: looks like every one of the failed tests fails for the same reason, (which to me indicates rather a failure of the test suite than a