Processed: limit source to ftp.app, tagging 897524

Processing commands for cont...@bugs.debian.org: > limit source ftp.app Limiting to bugs with field 'source' containing at least one of 'ftp.app' Limit currently set to 'source':'ftp.app' > tags 897524 + pending Bug #897524 [src:ftp.app] ftp.app: FTBFS: convert-im6.q16: improper image header

Processed: severity of 897986 is important

Processing commands for cont...@bugs.debian.org: > severity 897986 important Bug #897986 [systemd] systemctl failures during dist-upgrade due to missing libcryptsetup.so.12 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. --

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

Your message dated Sun, 13 May 2018 01:49:42 + with message-id and subject line Bug#851076: fixed in gvpe 3.0-2 has caused the Debian Bug report #851076, regarding gridengine: Please migrate to openssl1.1 in buster to be marked as done. This means that

Bug#887662: marked as done (gvpe FTBFS with glibc 2.26)

Your message dated Sun, 13 May 2018 01:49:42 + with message-id and subject line Bug#887662: fixed in gvpe 3.0-2 has caused the Debian Bug report #887662, regarding gvpe FTBFS with glibc 2.26 to be marked as done. This means that you claim that the problem

Processed: Re: u-boot-rockchip: firefly-rk3288 hangs on: Loading Environment from MMC

Processing control commands: > found 898520 2018.03+dfsg1-2 Bug #898520 [u-boot-rockchip] u-boot-rockchip: firefly-rk3288 hangs on: Loading Environment from MMC Marked as found in versions u-boot/2018.03+dfsg1-2. -- 898520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898520 Debian Bug

Bug#898520: u-boot-rockchip: firefly-rk3288 hangs on: Loading Environment from MMC

Control: found 898520 2018.03+dfsg1-2 On 2018-05-12, Vagrant Cascadian wrote: > Booting firefly-rk3288 seems to hang looking for environment: > > U-Boot 2018.05+dfsg-1 (May 10 2018 - 20:24:57 +) > > Model: Firefly-RK3288 > DRAM: 2 GiB > MMC: dwmmc@ff0c: 1, dwmmc@ff0f: 0

Bug#898524: FTBFS: unsatisfiable dependencies

Source: stylish-haskell Version: 0.8.1.0-1 Severity: serious Justification: fails to build from source Tags: sid buster Install stylish-haskell build dependencies (apt-based resolver) --- Installing build dependencies Reading package

Bug#898520: u-boot-rockchip: firefly-rk3288 hangs on: Loading Environment from MMC

Package: u-boot-rockchip Severity: serious Version: 2018.05+dfsg-1 Booting firefly-rk3288 seems to hang looking for environment: U-Boot 2018.05+dfsg-1 (May 10 2018 - 20:24:57 +) Model: Firefly-RK3288 DRAM: 2 GiB MMC: dwmmc@ff0c: 1, dwmmc@ff0f: 0 Loading Environment

Bug#898380: marked as done (libreadline-java-doc: fails to upgrade from 'stretch' - trying to overwrite /usr/share/doc/libreadline-java/NEWS.gz)

Your message dated Sat, 12 May 2018 23:52:32 + with message-id and subject line Bug#898380: fixed in libreadline-java 0.8.0.1+dfsg-8 has caused the Debian Bug report #898380, regarding libreadline-java-doc: fails to upgrade from 'stretch' - trying to

Bug#898380: Bug #898380 in libreadline-java marked as pending

Control: tag -1 pending Hello, Bug #898380 in libreadline-java 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 #898380 in libreadline-java marked as pending

Processing control commands: > tag -1 pending Bug #898380 [libreadline-java-doc] libreadline-java-doc: fails to upgrade from 'stretch' - trying to overwrite /usr/share/doc/libreadline-java/NEWS.gz Added tag(s) pending. -- 898380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898380 Debian

Bug#898518: why silently dropped the ppc64el and s390x builds

Package: src:why Version: 2.40-2 Severity: serious Tags: sid buster why silently dropped the ppc64el and s390x builds, the changelog doesn't tell a word about it. This hinders propagation of the package to testing.

Bug#898468: debian-installer: black screen/long delay in graphical installer after switching from linux 4.15 to 4.16

On Sat, 2018-05-12 at 05:36 +0200, Cyril Brulebois wrote: > Package: debian-installer > Severity: serious > Justification: graphical installer regression > > Hi, > > Ever since we switched from linux 4.15 to 4.16, the graphical installer > gets a black screen. Comparing Xorg logs, everything is

Bug#898264: marked as done (gnome-shell: Hold in unstable until bolt migrates to testing)

Your message dated Sat, 12 May 2018 19:18:51 -0400 with message-id

Bug#898491: marked as done (mercurial: FTBFS on 32bit architectures (xdiff-related))

Your message dated Sat, 12 May 2018 23:06:37 + with message-id and subject line Bug#898491: fixed in mercurial 4.6-2 has caused the Debian Bug report #898491, regarding mercurial: FTBFS on 32bit architectures (xdiff-related) to be marked as done. This

Processed: Bug #898491 in mercurial marked as pending

Processing control commands: > tag -1 pending Bug #898491 [src:mercurial] mercurial: FTBFS on 32bit architectures (xdiff-related) Added tag(s) pending. -- 898491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#898491: Bug #898491 in mercurial marked as pending

Control: tag -1 pending Hello, Bug #898491 in mercurial 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: your mail

Processing commands for cont...@bugs.debian.org: > reopen 850921 Bug #850921 {Done: Emmanuel Bourg } [openjfx] openjfx version for openjdk 9.0 Bug #874132 {Done: Emmanuel Bourg } [openjfx] FTBFS with Java 9: import sun.misc.. Bug #893190 {Done: Emmanuel

Bug#893194: marked as done (fontawesomefx FTBFS with openjdk-9)

Your message dated Sat, 12 May 2018 23:43:14 +0200 with message-id <5ce445e4-c1ec-9b09-e708-5b5f64490...@apache.org> and subject line Re: Bug#850921: why do we still have openjfx-java version 8 in unstable ? has caused the Debian Bug report #850921, regarding fontawesomefx FTBFS with openjdk-9 to

Bug#893345: marked as done (javafxsvg FTBFS with openjdk-9)

Your message dated Sat, 12 May 2018 23:43:14 +0200 with message-id <5ce445e4-c1ec-9b09-e708-5b5f64490...@apache.org> and subject line Re: Bug#850921: why do we still have openjfx-java version 8 in unstable ? has caused the Debian Bug report #850921, regarding javafxsvg FTBFS with openjdk-9 to be

Bug#850921: marked as done (openjfx version for openjdk 9.0)

Your message dated Sat, 12 May 2018 23:43:14 +0200 with message-id <5ce445e4-c1ec-9b09-e708-5b5f64490...@apache.org> and subject line Re: Bug#850921: why do we still have openjfx-java version 8 in unstable ? has caused the Debian Bug report #850921, regarding openjfx version for openjdk 9.0 to be

Bug#893348: marked as done (openjfx not available for openjdk-9)

Your message dated Sat, 12 May 2018 23:43:14 +0200 with message-id <5ce445e4-c1ec-9b09-e708-5b5f64490...@apache.org> and subject line Re: Bug#850921: why do we still have openjfx-java version 8 in unstable ? has caused the Debian Bug report #850921, regarding openjfx not available for openjdk-9

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

Your message dated Sat, 12 May 2018 23:43:14 +0200 with message-id <5ce445e4-c1ec-9b09-e708-5b5f64490...@apache.org> and subject line Re: Bug#850921: why do we still have openjfx-java version 8 in unstable ? has caused the Debian Bug report #850921, regarding FTBFS with Java 9: import sun.misc..

Bug#893190: marked as done (afterburner.fx FTBFS with openjdk-9)

Your message dated Sat, 12 May 2018 23:43:14 +0200 with message-id <5ce445e4-c1ec-9b09-e708-5b5f64490...@apache.org> and subject line Re: Bug#850921: why do we still have openjfx-java version 8 in unstable ? has caused the Debian Bug report #850921, regarding afterburner.fx FTBFS with openjdk-9

Bug#850921: why do we still have openjfx-java version 8 in unstable ?

Dear maintainer, Why do we have libopenjfx-java version 8 in unstable - $ apt-cache policy libopenjfx-java libopenjfx-java: Installed: (none) Candidate: 8u161-b12-1 Version table: 8u161-b12-1 100 100 http://cdn-fastly.deb.debian.org/debian unstable/main amd64 Packages When

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 887586 node-mocha/4.0.1-7 Bug #887586 {Done: Bastien ROUCARIES } [mocha] mocha 4.0.1-3 causes build hangs in various build-rdeps Marked as fixed in versions node-mocha/4.0.1-7. > thanks Stopping processing

Bug#893346: marked as done (libxerces2-java FTBFS with openjdk-9)

Your message dated Sat, 12 May 2018 20:54:26 + with message-id and subject line Bug#893346: fixed in libxerces2-java 2.11.0-9 has caused the Debian Bug report #893346, regarding libxerces2-java FTBFS with openjdk-9 to be marked as done. This means that

Bug#872894: Patch for FTBFS

tags 872894 +patch tags 872903 +patch thanks Hi there, I pushed a the new upstream version to the salsa repository, which indeed fixes the autopkgtests. Since I'm not a DD I will seek sponsoring for the new package. Cheers, Andreas -- PGP-encrypted mails preferred PGP Fingerprint: 74CD D9FE

Bug#893346: Bug #893346 in libxerces2-java marked as pending

Control: tag -1 pending Hello, Bug #893346 in libxerces2-java 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: Patch for FTBFS

Processing commands for cont...@bugs.debian.org: > tags 872894 +patch Bug #872894 [src:node-policyfile] node-policyfile: autopkgtests fail with nodejs 6 Added tag(s) patch. > tags 872903 +patch Bug #872903 [node-policyfile] node-policyfile: wrong homepage Added tag(s) patch. > thanks Stopping

Processed: Bug #893346 in libxerces2-java marked as pending

Processing control commands: > tag -1 pending Bug #893346 [src:libxerces2-java] libxerces2-java FTBFS with openjdk-9 Added tag(s) pending. -- 893346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#898502: ucommon: Please update symbols for riscv64 and ia64

Source: ucommon Version: 7.0.0-12 Severity: serious User: debian-ri...@lists.debian.org Usertags: riscv64 Hi, This is possibly related with #897878 (FTBFS due to symbols with GCC-8), and indeed the solution it's similar, needs an update to the symbols file, but decided to report it separately

Bug#898501: Broken symlinks

Package: fonts-font-awesome Version: 5.0.10-1 Severity: grave Control: affects -1 cider Dear maintainer, The latest upload introduces some new broken symlinks: fonts-font-awesome: broken-symlink /usr/share/fonts-font-awesome/fonts/FontAwesome.otf ->

Processed: Broken symlinks

Processing control commands: > affects -1 cider Bug #898501 [fonts-font-awesome] Broken symlinks Added indication that 898501 affects cider -- 898501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#869994: work around solution

I ran into this problem myself and found myself reading this thread. In message #10 Gregor Herrmann posted a link about the removal of the current directory in perl-5.26. The solution to get it back is to add the following directive to the sql- ledger-httpd.conf file SetEnv PERL5LIB "."

Bug#885699: smokeping: symbolic link to smokeping.cgi missing

Control: tags -1 +pending Control: severity -1 normal On Fri, Dec 29, 2017 at 10:48:43AM +0100, Sigbjorn Kjetland wrote: > Dear Maintainer, > >* What led up to the situation? > I am installing smokeping on a new server to replace old smokeping server > I have configured and restarted

Processed: Re: Bug#885699: smokeping: symbolic link to smokeping.cgi missing

Processing control commands: > tags -1 +pending Bug #885699 [smokeping] smokeping: symbolic link to smokeping.cgi missing Added tag(s) pending. > severity -1 normal Bug #885699 [smokeping] smokeping: symbolic link to smokeping.cgi missing Severity set to 'normal' from 'serious' -- 885699:

Bug#896420: marked as done (python3-winrm: winrm fails to import)

Your message dated Sat, 12 May 2018 19:20:55 + with message-id and subject line Bug#896420: fixed in pywinrm 0.3.0-2 has caused the Debian Bug report #896420, regarding python3-winrm: winrm fails to import to be marked as done. This means that you claim

Bug#898327: cppcheck: *** stack smashing detected ***: terminated

I tested this with packages from unstable from the moment the package was built: deb http://snapshot.debian.org/archive/debian/20180412T222117Z/ unstable main cppcheck worked flawlessly in this environment. It only started crashing when I upgraded libtinyxml2-6 (6.0.0+dfsg-1 ->

Processed: Was never built on mips/s390x

Processing commands for cont...@bugs.debian.org: > severity 897001 important Bug #897001 [libghc-cmark-gfm-dev] libghc-cmark-gfm-dev: not big-endian-safe Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 897001:

Bug#898433: marked as done (FTBFS: README.md -> README.rst)

Your message dated Sat, 12 May 2018 19:04:41 + with message-id and subject line Bug#898433: fixed in ansible 2.5.2+dfsg-2 has caused the Debian Bug report #898433, regarding FTBFS: README.md -> README.rst to be marked as done. This means that you claim

Processed: bug 898491 is forwarded to https://bz.mercurial-scm.org/show_bug.cgi?id=5885

Processing commands for cont...@bugs.debian.org: > forwarded 898491 https://bz.mercurial-scm.org/show_bug.cgi?id=5885 Bug #898491 [src:mercurial] mercurial: FTBFS on 32bit architectures (xdiff-related) Set Bug forwarded-to-address to 'https://bz.mercurial-scm.org/show_bug.cgi?id=5885'. > thanks

Processed: Patch pushed to salsa

Processing commands for cont...@bugs.debian.org: > tags 892658 +patch Bug #892658 [src:node-ip] node-ip FTBFS with mocha 4.0.1-3 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 892658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892658

Bug#892658: Patch pushed to salsa

tags 892658 +patch thanks Hi there, I have pushed a fix for this build failure (and a second that showed after fixing the one described in this issue) to the salsa repository. I am not a DD though and need a sponsor for the upload. I will file a sponsorship request in a couple days if no one

Bug#895920: ecj: only a virtual package and not installable

Control: reassign -1 ftp.debian.org Control: severity -1 normal Control: retitle -1 RM: ecj1 libecj-java-gcj ecj-gcj [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x] -- NBS; no longer built after gcj removal On Tue, Apr 17, 2018 at

Processed: Re: Bug#895920: ecj: only a virtual package and not installable

Processing control commands: > reassign -1 ftp.debian.org Bug #895920 [src:ecj] ecj: only a virtual package and not installable Bug reassigned from package 'src:ecj' to 'ftp.debian.org'. No longer marked as found in versions ecj/3.13.2-2. Ignoring request to alter fixed versions of bug #895920 to

Bug#897975: gdm3: System fails to boot due to GDM restarting constantly.

Looks like it does boot after ten minutes or so. It seems only Wayland variant of gdm is failing. Gnome on Wayland has no issues though. On Sat, May 5, 2018, 14:00 Mladen Mijatov wrote: > Package: gdm3 > Version: 3.28.1-1 > Severity: grave > Justification: renders package

Bug#898483: PHYSFS_setWriteDir creates an empty file

Hello Patrick, Am 12.05.2018 um 16:19 schrieb James Cowgill: [...] > I think this is a bug in libphysfs 3.0.1. It seems that in this version > (unlike 2.0.3), PHYSFS_setWriteDir has the side effect of creating an > empty file if the path it is given does not exist. This will later cause >

Bug#898228: marked as done (ruby-gitaly: Required dependency not specified on deb package)

Your message dated Sat, 12 May 2018 15:35:31 + with message-id and subject line Bug#898228: fixed in golang-gitaly-proto 0.99.0+dfsg-2 has caused the Debian Bug report #898228, regarding ruby-gitaly: Required dependency not specified on deb package to be

Bug#898491: mercurial: FTBFS on 32bit architectures (xdiff-related)

Source: mercurial Version: 4.6-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Tags: upstream help armel: https://buildd.debian.org/status/fetch.php?pkg=mercurial=armel=4.6-1=1526067243=0 armhf:

Bug#898483: Acknowledgement (failed creating configuration directroy: unsupported)

Control: tags -1 - patch Hi, On 12/05/18 14:33, Lumin wrote: > control: tag -1 +patch > I think the problem lays in main.cpp : > >81 // Set configuration directory >82 //sprintf(writedir, "%s.%s", userdir, application); >83 sprintf(writedir, "%s%s", userdir,

Processed: Re: Bug#898483: Acknowledgement (failed creating configuration directroy: unsupported)

Processing control commands: > tags -1 - patch Bug #898483 [lincity-ng] failed creating configuration directroy: unsupported Removed tag(s) patch. -- 898483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#898483: failed creating configuration directroy: unsupported

Processing control commands: > tags -1 confirmed Bug #898483 [lincity-ng] failed creating configuration directroy: unsupported Added tag(s) confirmed. -- 898483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#898483: failed creating configuration directroy: unsupported

Control: tags -1 confirmed Am 12.05.2018 um 15:06 schrieb Lumin: > Package: lincity-ng > Version: 2.9~git20150314-3 > Severity: serious > > Dear lincity-ng maintainer, > > When there is no ~/.lincity-ng directory under user's home, lincity-ng > will fail on start. > > ~ ❯❯❯ lincity-ng >

Bug#895792: gplaycli: dependency androguard switched to Python 3, gplaycli is incompatible with Python 3

Le 25 avril 2018 03:04:12 GMT+02:00, Andres Salomon a écrit : >Just FYI, I have a new gplaycli package prepared (and its new gpapi >dependency). It is python3 only. > >However, it requires a newer version of protobuf, so we've been stuck >waiting on that. See

Bug#898483: Acknowledgement (failed creating configuration directroy: unsupported)

control: tag -1 +patch I think the problem lays in main.cpp : 81 // Set configuration directory 82 //sprintf(writedir, "%s.%s", userdir, application); 83 sprintf(writedir, "%s%s", userdir, application); 84 if(!PHYSFS_setWriteDir(writedir)) { 85 // try to

Processed: Re: Bug#898483: Acknowledgement (failed creating configuration directroy: unsupported)

Processing control commands: > tag -1 +patch Bug #898483 [lincity-ng] failed creating configuration directroy: unsupported Added tag(s) patch. -- 898483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#898483: failed creating configuration directroy: unsupported

Package: lincity-ng Version: 2.9~git20150314-3 Severity: serious Dear lincity-ng maintainer, When there is no ~/.lincity-ng directory under user's home, lincity-ng will fail on start. ~ ❯❯❯ lincity-ng Starting lincity-ng (version 2.9.beta)... Unexpected exception: Failed creating configuration

Processed: fixed 892961 in 0.27.0+dfsg.1-0.1

Processing commands for cont...@bugs.debian.org: > fixed 892961 0.27.0+dfsg.1-0.1 Bug #892961 [src:libgit2] libgit2: CVE-2018-8098 Marked as fixed in versions libgit2/0.27.0+dfsg.1-0.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 892961:

Processed: fixed 892962 in 0.27.0+dfsg.1-0.1

Processing commands for cont...@bugs.debian.org: > fixed 892962 0.27.0+dfsg.1-0.1 Bug #892962 [src:libgit2] libgit2: CVE-2018-8099 Marked as fixed in versions libgit2/0.27.0+dfsg.1-0.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 892962:

Bug#898327: cppcheck: *** stack smashing detected ***: terminated

Hi Jakub, I can reproduce this on i386 with the binary package from the archive (but not on amd64). I'm not able to reproduce the problem if I build the package myself in an up-to-date sid chroot. It also does not happen if I use g++ 7.3.0-15 which was used on the autobuilder, but there are of

Bug#898375: libduo-dev: overly generic header name: /usr/include/util.h

On Fri, 11 May 2018 00:08:16 +0200 Andreas Beckmann wrote: > Hi, > > during a test with piuparts I noticed your package uses a very generic > header file name that now clashes with other packages: > > /usr/include/util.h Dear maintainer, using repology.org and pkgs.org I

Bug#898228: ruby-gitaly: Required dependency not specified on deb package

On Wed, 09 May 2018 10:39:31 +0530 Pirate Praveen wrote:> I'm aware of this issue and ruby-grpc 1.11 is ready for upload. I'm waiting for libgrpc6 to clear NEW. It also needs ruby-rugged >= 0.27 which needs libgit2 0.27 in NEW. signature.asc Description: OpenPGP

Bug#897975: gdm3: System fails to boot due to GDM restarting constantly.

Package: gdm3 Version: 3.22.3-3+deb9u1 Followup-For: Bug #897975 Dear Maintainer, I observe the same problem on my notebook and would like to add some additional information. 1) CPU Intel(R) Celeron(R) CPU N3160 with integrated graphics. This might be interesting, as there is one (EE) entry

Processed: tagging 895695

Processing commands for cont...@bugs.debian.org: > tags 895695 + fixed-upstream Bug #895695 [src:elki] elki FTBFS: java.base/jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to java.base/java.net.URLClassLoader Added tag(s) fixed-upstream. > thanks Stopping processing here.

Processed: severity of 895029 is serious

Processing commands for cont...@bugs.debian.org: > severity 895029 serious Bug #895029 [src:node-stringprep] node-stringprep: FTBFS with recent GCC Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 895029:

Processed: thefuck: diff for NMU version 3.11-2.1

Processing control commands: > tags 842393 + patch Bug #842393 [thefuck] thefuck: Missing dependency on python-pkg-resources Added tag(s) patch. -- 842393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#842393: thefuck: diff for NMU version 3.11-2.1

Control: tags 842393 + patch Dear maintainer, I've prepared an NMU for thefuck (versioned as 3.11-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness.