Bug#921363: marked as done (Not suitable for buster, package unmaintained)

Your message dated Fri, 15 Feb 2019 07:52:23 + with message-id and subject line Bug#921363: fixed in ejs.js 1.0.0+dfsg1-2 has caused the Debian Bug report #921363, regarding Not suitable for buster, package unmaintained to be marked as done. This means that you claim that the problem has

Bug#921365: marked as done (Not suitable for buster, package probably unmaintained)

Your message dated Fri, 15 Feb 2019 07:55:03 + with message-id and subject line Bug#921365: fixed in node-async-stacktrace 0.0.2-3 has caused the Debian Bug report #921365, regarding Not suitable for buster, package probably unmaintained to be marked as done. This means that you claim that

Bug#920709: distcc: fails to upgrade from 'testing': causes dpkg trigger loop

On 28 janv. 2019 15:07, Andreas Beckmann wrote: > Hi Guillem, > > do you have any recommendations for this trigger loop? > I think at this point it is already dpkg 1.19.4 that is running > (dpkg is being upgraded during the same run). Guillem ? Would be nice to have your advice on this bug.

Bug#922350: udevd does not start after reboot

Le 15/02/2019 à 08:01, Vincent Danjean a écrit : > Le 14/02/2019 à 22:59, Felipe Sateler a écrit : >> Is udev by any chance i386 instead of amd64? > > I don't think so: > vdanjean@eyak:~$ apt-cache policy udev:i386 > udev:i386: > Installé : (aucun) However, systemd was installed as i386:

Bug#922350: udevd does not start after reboot

Le 14/02/2019 à 22:59, Felipe Sateler a écrit : > Is udev by any chance i386 instead of amd64? I don't think so: vdanjean@eyak:~$ apt-cache policy udev:i386 udev:i386: Installé : (aucun) Candidat : 240-5 Table de version : 240-5 500 500 http://ftp.fr.debian.org/debian

Processed: Bug #922271 in camomile marked as pending

Processing control commands: > tag -1 pending Bug #922271 [src:camomile] camomile: ocaml-gettext build still fails, due to wrong search path caused by camomile build Added tag(s) pending. -- 922271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922271 Debian Bug Tracking System Contact

Bug#922271: Bug #922271 in camomile marked as pending

Control: tag -1 pending Hello, Bug #922271 in camomile 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#922369: javamail: FTBFS on Buster/Sid

Source: javamail Severity: serious Tags: ftbfs Justification: fails to build from source You can also see the same build failure from the reproducible builds projects efforts. https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/javamail.html [ 254s] Generating

Processed: limit source to php-zeta-base, tagging 917744, tagging 882917

Processing commands for cont...@bugs.debian.org: > limit source php-zeta-base Limiting to bugs with field 'source' containing at least one of 'php-zeta-base' Limit currently set to 'source':'php-zeta-base' > tags 917744 + pending Bug #917744 [src:php-zeta-base] php-zeta-base: FTBFS: PHP Fatal

Processed: limit source to php-zeta-console-tools, tagging 917760

Processing commands for cont...@bugs.debian.org: > limit source php-zeta-console-tools Limiting to bugs with field 'source' containing at least one of 'php-zeta-console-tools' Limit currently set to 'source':'php-zeta-console-tools' > tags 917760 + pending Bug #917760

Bug#921895: marked as done (bitlbee: does not build all binary packages by default)

Your message dated Fri, 15 Feb 2019 00:49:33 + with message-id and subject line Bug#921895: fixed in bitlbee 3.5.1-1.2 has caused the Debian Bug report #921895, regarding bitlbee: does not build all binary packages by default to be marked as done. This means that you claim that the problem

Bug#920018: Memory Leak in journald? Failed to write entry (23 items, 500 bytes), ignoring: Cannot allocate memory

I still seeing this bug on hppa with systemd 240-5.  Started with 240-4. Regards, Dave -- John David Anglin dave.ang...@bell.net

Bug#922356: nbd: FTBFS in sid (rm: cannot remove 'gitstatus': No such file or directory)

Package: src:nbd Version: 1:3.19-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a

Bug#922355: vmdb2: FTBFS in sid (LaTeX Error: File `lmodern.sty' not found)

Package: src:vmdb2 Version: 0.13.2+git20190214-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-indep dh build-indep --with=python3

Bug#917485: Bug#919043: nmu: ckermit_302-5.3 (stretch)

On 2019-02-02 14:46:54 [+0100], Andreas Beckmann wrote: > I'm not going to touch that package, please go ahead with preparing a > NMU (or probably rather QA upload if it is gone from sid) to stretch, > since you seem to know how to properly fix this bug once and for all :-) I'm proposing this

Bug#864657: marked as done (ca-certificates-java has circular Depends on openjdk-8-jre-headless)

Your message dated Thu, 14 Feb 2019 22:22:37 + with message-id and subject line Bug#864657: fixed in ca-certificates-java 20190214 has caused the Debian Bug report #864657, regarding ca-certificates-java has circular Depends on openjdk-8-jre-headless to be marked as done. This means that you

Bug#917739: lucene-solr: FTBFS: [exec] Execute failed: java.io.IOException: Cannot run program "svnversion" (in directory "/<>/lucene-solr-3.6.2+dfsg/solr/contrib/dataimporthandler"): error=

On Sat, 29 Dec 2018 23:26:49 +0100 Lucas Nussbaum wrote: > Source: lucene-solr > Version: 3.6.2+dfsg-16 > Severity: serious > Justification: FTBFS on amd64 > Tags: buster sid > Usertags: ftbfs-20181229 ftbfs-buster > > Hi, > > During a rebuild of all packages in sid, your package failed to

Bug#922350: udevd does not start after reboot

On Thu, Feb 14, 2019 at 6:39 PM Vincent Danjean wrote: > Package: udev > Version: 240-5 > Severity: serious > Justification: render the system unbootable > > Hi, > > After a major upgrade to unstable (the system was not upgraded > during a few months) and after a reboot, udevd refuse to

Bug#873016: A way to fix node-lodash-packages ?

https://salsa.debian.org/js-team/node-lodash/blob/master/.travis.yml shows the way to build lodash-packages from lodash : $ yarn $ git clone --depth=10 --branch=master git://github.com/lodash/lodash-cli ./node_modules/lodash-cli $ mkdir -p ./node_modules/lodash-cli/node_modules/lodash $ cd $_ $

Bug#864657: Bug #864657 in ca-certificates-java marked as pending

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

Processing control commands: > tag -1 pending Bug #864657 [ca-certificates-java] ca-certificates-java has circular Depends on openjdk-8-jre-headless Added tag(s) pending. -- 864657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864657 Debian Bug Tracking System Contact

Bug#922027: python-django: Django security release

Hi Moritz, > > Security team, may I upload this to stretch-security? Diff attached. > > This doesn't warrant a DSA, let's postpone this until more severe comes up. Noted. Can you update data/CVE/list? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 

Bug#922027: python-django: Django security release

On Mon, Feb 11, 2019 at 03:07:36PM +0100, Chris Lamb wrote: > [Adding t...@security.debian.org to CC] > > Chris Lamb wrote: > > > retitle 922027 CVE-2019-6975: Memory exhaustion in > > django.utils.numberformat.format() > > severity 922027 grave > > found 922027 1:1.10.7-2+deb9u3 > > tags

Bug#922133: marked as done (src:marionnet: build-depends/depends on cruft packages)

Your message dated Thu, 14 Feb 2019 22:14:41 +0100 with message-id <20190214211441.gb25...@seneca.home.org> and subject line Re: Bug#922133: src:marionnet: build-depends/depends on cruft packages has caused the Debian Bug report #922133, regarding src:marionnet: build-depends/depends on cruft

Bug#922286: marked as done (python-apptools-doc: missing Breaks+Replaces: python-apptools (<< 4.4.0))

Your message dated Thu, 14 Feb 2019 21:04:26 + with message-id and subject line Bug#922286: fixed in python-apptools 4.4.0-2 has caused the Debian Bug report #922286, regarding python-apptools-doc: missing Breaks+Replaces: python-apptools (<< 4.4.0) to be marked as done. This means that you

Bug#922346: eog: Opened an image and my display server crashed

Le jeudi 14 février 2019 à 20:31 +, Simon McVittie a écrit : > Control: reassign -1 libgl1-mesa-dri > Control: tags -1 + moreinfo > > On Thu, 14 Feb 2019 at 21:18:42 +0100, Michel Le Bihan wrote: > > I opened a png file in eog and my display server crashed. > > eog shouldn't be able to cause

Processed: Taking ownership of python-apptools bug

Processing commands for cont...@bugs.debian.org: > owner 922286 ! Bug #922286 [python-apptools-doc] python-apptools-doc: missing Breaks+Replaces: python-apptools (<< 4.4.0) Owner recorded as Stewart Ferguson . > thank you Stopping processing here. Please contact me if you need assistance. --

Processed: Re: Bug#922346: eog: Opened an image and my display server crashed

Processing control commands: > reassign -1 libgl1-mesa-dri Bug #922346 [eog] eog: Opened an image and my display server crashed Bug reassigned from package 'eog' to 'libgl1-mesa-dri'. No longer marked as found in versions eog/3.28.4-2. Ignoring request to alter fixed versions of bug #922346 to

Bug#922346: eog: Opened an image and my display server crashed

Control: reassign -1 libgl1-mesa-dri Control: tags -1 + moreinfo On Thu, 14 Feb 2019 at 21:18:42 +0100, Michel Le Bihan wrote: > I opened a png file in eog and my display server crashed. eog shouldn't be able to cause this, even if it wanted to, so this is a bug in the display server or some

Bug#922286: Bug #922286 in python-apptools marked as pending

Control: tag -1 pending Hello, Bug #922286 in python-apptools 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 #922286 in python-apptools marked as pending

Processing control commands: > tag -1 pending Bug #922286 [python-apptools-doc] python-apptools-doc: missing Breaks+Replaces: python-apptools (<< 4.4.0) Added tag(s) pending. -- 922286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922286 Debian Bug Tracking System Contact

Bug#922346: eog: Opened an image and my display server crashed

Package: eog Version: 3.28.4-2+b1 Severity: critical Justification: breaks the whole system I opened a png file in eog and my display server crashed. Here is the relevant part of my syslog: Feb 14 20:44:45 debian org.gnome.Shell.desktop[1414]: Window manager warning: Buggy client sent a

Bug#922345: msmtp: CVE-2019-8337

Source: msmtp Version: 1.8.2-1 Severity: grave Tags: security upstream Hi, The following vulnerability was published for msmtp. CVE-2019-8337[0]: | In msmtp 1.8.2, when tls_trust_file has its default configuration, | certificate-verification results are not properly checked. If you fix the

Bug#922297: marked as done (rxvt-unicode: *blink* *blink* *blink*)

Your message dated Thu, 14 Feb 2019 17:50:11 + with message-id and subject line Bug#922297: fixed in rxvt-unicode 9.22-6 has caused the Debian Bug report #922297, regarding rxvt-unicode: *blink* *blink* *blink* to be marked as done. This means that you claim that the problem has been dealt

Bug#892661: marked as done (node-static-extend: FTBFS and Debci failure)

Your message dated Thu, 14 Feb 2019 17:49:17 + with message-id and subject line Bug#892661: fixed in node-static-extend 0.1.2-2 has caused the Debian Bug report #892661, regarding node-static-extend: FTBFS and Debci failure to be marked as done. This means that you claim that the problem has

Processed: bug 922333 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=128513

Processing commands for cont...@bugs.debian.org: > forwarded 922333 https://rt.cpan.org/Ticket/Display.html?id=128513 Bug #922333 [libmail-message-perl] libmail-message-perl 3.008 breaks (the testsuite of) libmail-box-perl Ignoring request to change the forwarded-to-address of bug#922333 to the

Bug#922287: marked as done (msxpertsuite-massxpert: missing Breaks+Replaces: massxpert)

Your message dated Thu, 14 Feb 2019 17:35:05 + with message-id and subject line Bug#922287: fixed in msxpertsuite 5.8.6-1 has caused the Debian Bug report #922287, regarding msxpertsuite-massxpert: missing Breaks+Replaces: massxpert to be marked as done. This means that you claim that the

Processed: bug 922333 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=128513

Processing commands for cont...@bugs.debian.org: > forwarded 922333 https://rt.cpan.org/Ticket/Display.html?id=128513 Bug #922333 [libmail-message-perl] libmail-message-perl 3.008 breaks (the testsuite of) libmail-box-perl Set Bug forwarded-to-address to

Processed: limit source to rxvt-unicode, tagging 922268, tagging 922289, tagging 922297, tagging 922299 ...

Processing commands for cont...@bugs.debian.org: > limit source rxvt-unicode Limiting to bugs with field 'source' containing at least one of 'rxvt-unicode' Limit currently set to 'source':'rxvt-unicode' > tags 922268 + pending Bug #922268 [rxvt-unicode] rxvt-unicode: tabbed extension segfaults

Bug#922333: libmail-message-perl 3.008 breaks (the testsuite of) libmail-box-perl

Package: libmail-message-perl Version: 3.008-1 Severity: serious Tags: upstream sid Justification: breaks other package -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As first seen on ci.debian.net, libmail-message-perl 3.008-1 breaks libmail-box-perl's test suite (which causes a build

Bug#922297: rxvt-unicode: *blink* *blink* *blink*

On Thu, Feb 14, 2019 at 06:05:03PM +0100, Jakub Wilk wrote: > I can reproduce the issue without any custom settings or extensions > The effect is quite subtle, so I can imagine some people might not > notice it. Even after clearing out all resources, I'm unable to reproduce it on either of my

Processed: [bts-link] source package src:borgbackup

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:borgbackup > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package systemd

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#879642: fixed in simple-cdd 0.6.6

On 2019-02-11, Alexandre Belgrand wrote: > The bug does not seem to be fixed. While similar in end result, I believe the bug you are experiencing is more similar to: https://bugs.debian.org/919572 > I am still getting this error: > > 2019-02-11 15:45:44 ERROR verify gpg signature exited with

Bug#922297: rxvt-unicode: *blink* *blink* *blink*

* Ryan Kavanagh , 2019-02-14, 09:01: The terminal screen blinks all the time. What resources do you have set for URxvt? (See output of "appres URxvt".) What perl extensions are you using? I can reproduce the issue without any custom settings or extensions, that is: $ appres URxvt

Bug#892661: Bug #892661 in node-static-extend marked as pending

Control: tag -1 pending Hello, Bug #892661 in node-static-extend 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 #892661 in node-static-extend marked as pending

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

Bug#802350: Package unusable

Control: forwarded -1 https://github.com/andrewrk/node-yawl/issues/5 Control: tags -1 + upstream confirmed Upstream tests fail even using a fresh "npm install".

Processed: Package unusable

Processing control commands: > forwarded -1 https://github.com/andrewrk/node-yawl/issues/5 Bug #802350 [src:node-yawl] node-yawl: FTBFS: "yawl buffered messages" times out Set Bug forwarded-to-address to 'https://github.com/andrewrk/node-yawl/issues/5'. > tags -1 + upstream confirmed Bug #802350

Bug#915175: marked as done (oath-toolkit FTBFS with glibc 2.28)

Your message dated Thu, 14 Feb 2019 16:36:35 + with message-id and subject line Bug#915175: fixed in oath-toolkit 2.6.1-1.3 has caused the Debian Bug report #915175, regarding oath-toolkit FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt

Bug#922328: libblockdev-swap2: Swap seems to freeze the system

Package: libblockdev-swap2 Version: 2.20-6 Severity: grave Tags: a11y Justification: renders package unusable Dear Maintainer, Not sure if I choose the right package. * What led up to the situation? When loading a tif image with feh of 100MB or (which was the next image) 749MB the system

Bug#922218: marked as done (gnome-shell fills up logs with an stack trace)

Your message dated Thu, 14 Feb 2019 16:13:24 + with message-id <20190214161324.ga31...@espresso.pseudorandom.co.uk> and subject line Re: Bug#922218: gnome-shell fills up logs with an stack trace has caused the Debian Bug report #922218, regarding gnome-shell fills up logs with an stack trace

Processed: tagging 922218, block 922218 with 906016

Processing commands for cont...@bugs.debian.org: > tags 922218 - moreinfo Bug #922218 [gnome-shell] gnome-shell fills up logs with an stack trace Removed tag(s) moreinfo. > block 922218 with 906016 Bug #922218 [gnome-shell] gnome-shell fills up logs with an stack trace 922218 was not blocked by

Bug#915995: marked as done (nfs-utils FTBFS with glibc 2.28)

Your message dated Thu, 14 Feb 2019 15:50:13 + with message-id and subject line Bug#915995: fixed in nfs-utils 1:1.3.4-2.4 has caused the Debian Bug report #915995, regarding nfs-utils FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#919340: marked as done (fenix-plugins: FTBFS: configure.ac:36: error: possibly undefined macro: AC_CHECK_FT2)

Your message dated Thu, 14 Feb 2019 15:49:28 + with message-id and subject line Bug#919340: fixed in fenix-plugins 0.0.20070803-8 has caused the Debian Bug report #919340, regarding fenix-plugins: FTBFS: configure.ac:36: error: possibly undefined macro: AC_CHECK_FT2 to be marked as done.

Processed: bug 922265 is forwarded to https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/commit/77ccc9bbc3ac70f9c71c527e6062eebec41be57d

Processing commands for cont...@bugs.debian.org: > forwarded 922265 > https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/commit/77ccc9bbc3ac70f9c71c527e6062eebec41be57d Bug #922265 {Done: Xavier Guimard } [src:lemonldap-ng] lemonldap-ng: FTBFS in sid (failing tests) Set Bug forwarded-to-address

Processed: found 922265 in 2.0.2+ds-3, notfound 922265 in 2.0.2+ds-4

Processing commands for cont...@bugs.debian.org: > found 922265 2.0.2+ds-3 Bug #922265 {Done: Xavier Guimard } [src:lemonldap-ng] lemonldap-ng: FTBFS in sid (failing tests) The source 'lemonldap-ng' and version '2.0.2+ds-3' do not appear to match any binary packages Marked as found in versions

Bug#922306: linux: btrfs corruption (compressed data + hole data)

Here's the "proper" patch: https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg85515.html

Bug#922262: marked as done (ripe-atlas-tools: FTBFS (Could not import extension sphinx.ext.pngmath))

Your message dated Thu, 14 Feb 2019 15:19:32 + with message-id and subject line Bug#922262: fixed in ripe-atlas-tools 2.3.0-2 has caused the Debian Bug report #922262, regarding ripe-atlas-tools: FTBFS (Could not import extension sphinx.ext.pngmath) to be marked as done. This means that you

Bug#912051: marked as done (rsyncrypto: FTBFS: aclocal-1.15: command not found)

Your message dated Thu, 14 Feb 2019 15:19:43 + with message-id and subject line Bug#912051: fixed in rsyncrypto 1.14-1.1 has caused the Debian Bug report #912051, regarding rsyncrypto: FTBFS: aclocal-1.15: command not found to be marked as done. This means that you claim that the problem has

Bug#884721: marked as done (rsyncrypto: Segmentation fault with --delete)

Your message dated Thu, 14 Feb 2019 15:19:43 + with message-id and subject line Bug#884721: fixed in rsyncrypto 1.14-1.1 has caused the Debian Bug report #884721, regarding rsyncrypto: Segmentation fault with --delete to be marked as done. This means that you claim that the problem has been

Bug#922218: gnome-shell fills up logs with an stack trace

O Mér, 13-02-2019 ás 11:30 +, Simon McVittie escribiu: > Control: tags -1 + moreinfo > > On Wed, 13 Feb 2019 at 11:51:08 +0100, Sergio Villar wrote: > > gnome-shell is making my system unusable by completelly filling up > > the /var partition due to the errors it spits into several log > >

Bug#921779: Bug#919413: cascade of FTBFS

On Thu, Feb 14, 2019 at 03:16:22PM +0100, Dominique Dumont wrote: > On Tuesday, 12 February 2019 16:54:12 CET Andreas Tille wrote: > > I'm > > not sure how to deal with the jquery.js one since this is potentially an > > issue with lots of dependencies - I remember discussions about this > > which

Bug#921779: Bug#919413: cascade of FTBFS

Hi Dominique, see below Il 14/02/2019 15:16, Dominique Dumont ha scritto: On Tuesday, 12 February 2019 16:54:12 CET Andreas Tille wrote: I'm not sure how to deal with the jquery.js one since this is potentially an issue with lots of dependencies - I remember discussions about this which I did

Bug#920953: marked as done (ruby-haml-rails FTBFS: invalid byte sequence in US-ASCII (ArgumentError))

Your message dated Thu, 14 Feb 2019 14:47:18 + with message-id and subject line Bug#920953: fixed in ruby-haml-rails 1.0.0-2 has caused the Debian Bug report #920953, regarding ruby-haml-rails FTBFS: invalid byte sequence in US-ASCII (ArgumentError) to be marked as done. This means that you

Bug#922252: marked as done (ganeti-2.15: FTBFS (ImportError: cannot import name Directive))

Your message dated Thu, 14 Feb 2019 14:45:08 + with message-id and subject line Bug#922252: fixed in ganeti-2.15 2.15.2-14 has caused the Debian Bug report #922252, regarding ganeti-2.15: FTBFS (ImportError: cannot import name Directive) to be marked as done. This means that you claim that

Bug#922145: closed by Rhonda D'Vine (Bug#922145: fixed in irssi 1.2.0-2)

nvm, doing another 'aptitude safe-upgrade' right after made the problem go away again. signature.asc Description: This is a digitally signed message part.

Bug#921779: Bug#919413: cascade of FTBFS

On Tuesday, 12 February 2019 16:54:12 CET Andreas Tille wrote: > I'm > not sure how to deal with the jquery.js one since this is potentially an > issue with lots of dependencies - I remember discussions about this > which I did not followed. Fortunately, jquery is available as a Debian package.

Bug#922145: closed by Rhonda D'Vine (Bug#922145: fixed in irssi 1.2.0-2)

On woensdag 13 februari 2019 15:51:04 CET you wrote: > #922145: irssi: trying to overwrite '/usr/share/irssi/help/otr', which is > also in package irssi-plugin-otr > > It has been closed by Rhonda D'Vine . I think it's not actually fixed as I just got the error again. Now with version 1.2.0-2,

Bug#920953: Bug #920953 in ruby-haml-rails marked as pending

Control: tag -1 pending Hello, Bug #920953 in ruby-haml-rails 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 #920953 in ruby-haml-rails marked as pending

Processing control commands: > tag -1 pending Bug #920953 [src:ruby-haml-rails] ruby-haml-rails FTBFS: invalid byte sequence in US-ASCII (ArgumentError) Added tag(s) pending. -- 920953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920953 Debian Bug Tracking System Contact

Processed: Re: Bug#922297: rxvt-unicode: *blink* *blink* *blink*

Processing control commands: > tags -1 unreproducible moreinfo Bug #922297 [rxvt-unicode] rxvt-unicode: *blink* *blink* *blink* Added tag(s) unreproducible and moreinfo. -- 922297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922297 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#922297: rxvt-unicode: *blink* *blink* *blink*

Control: tags -1 unreproducible moreinfo On Thu, Feb 14, 2019 at 12:02:27PM +0100, Jakub Wilk wrote: > The terminal screen blinks all the time. What resources do you have set for URxvt? (See output of "appres URxvt".) What perl extensions are you using? I'll try to debug this bug (and all of

Bug#918850: marked as done (libmypaint: FTBFS with Sphinx 1.8: No module named 'sphinx.ext.pngmath')

Your message dated Thu, 14 Feb 2019 13:50:24 + with message-id and subject line Bug#918850: fixed in libmypaint 1.3.0-2.1 has caused the Debian Bug report #918850, regarding libmypaint: FTBFS with Sphinx 1.8: No module named 'sphinx.ext.pngmath' to be marked as done. This means that you

Bug#922265: marked as done (lemonldap-ng: FTBFS in sid (failing tests))

Your message dated Thu, 14 Feb 2019 13:50:09 + with message-id and subject line Bug#922265: fixed in lemonldap-ng 2.0.2+ds-4 has caused the Debian Bug report #922265, regarding lemonldap-ng: FTBFS in sid (failing tests) to be marked as done. This means that you claim that the problem has

Bug#890117: marked as done (bedtools FTBFS on big endian: Tools failing: bamtobed bamtofastq coverage genomecov groupby intersect jaccard map merge multicov negativecontrol)

Your message dated Thu, 14 Feb 2019 13:49:21 + with message-id and subject line Bug#890117: fixed in bedtools 2.27.1+dfsg-4 has caused the Debian Bug report #890117, regarding bedtools FTBFS on big endian: Tools failing: bamtobed bamtofastq coverage genomecov groupby intersect jaccard map

Bug#922313: kopano-search: missing an end of line character in /etc/apparmor.d/usr.sbin.kopano-search

Package: kopano-search Version: 8.7.0-1 Severity: serious Justification: 2 Hello, The kopano-search gives a parser error on the apparmor profile. Setting up kopano-search (8.7.0-1) ... AppArmor parser error for /etc/apparmor.d/usr.sbin.kopano-search in /etc/apparmor.d/usr.sbin.kopano-search

Bug#890117: Bug #890117 in bedtools marked as pending

Control: tag -1 pending Hello, Bug #890117 in bedtools 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#871105: Status of debian-faq

Dear FTP Masters, the package "debian-faq" has been uploaded three months ago and contains various important fixes. It's currently stuck in BYHAND. Is there any chance that we can get this package into buster? Regards, Tobias signature.asc Description: OpenPGP digital signature

Processed: Bug #890117 in bedtools marked as pending

Processing control commands: > tag -1 pending Bug #890117 [src:bedtools] bedtools FTBFS on big endian: Tools failing: bamtobed bamtofastq coverage genomecov groupby intersect jaccard map merge multicov negativecontrol Ignoring request to alter tags of bug #890117 to the same tags previously

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

>>> wlp5s0: WPA: IGTK keyid 1024 pn d0caa82e44b2 >>> WPA: IGTK - hexdump(len=16): [REMOVED] >>> wpa_driver_nl80211_set_key: ifindex=3 (wlp5s0) alg=4 addr=0x55e7e55d2909 >>> key_idx=1024 set_tx=0 seq_len=6 key_len=16 >> >> A key_idx=1024 looks wrong, it should be 4 or 5 for IGTK. I tend to >>

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

>>> wlp5s0: WPA: IGTK keyid 1024 pn d0caa82e44b2 >>> WPA: IGTK - hexdump(len=16): [REMOVED] >>> wpa_driver_nl80211_set_key: ifindex=3 (wlp5s0) alg=4 addr=0x55e7e55d2909 >>> key_idx=1024 set_tx=0 seq_len=6 key_len=16 >> >> A key_idx=1024 looks wrong, it should be 4 or 5 for IGTK. I tend to >>

Bug#922265: marked as done (lemonldap-ng: FTBFS in sid (failing tests))

Your message dated Thu, 14 Feb 2019 12:49:16 + with message-id and subject line Bug#922265: fixed in lemonldap-ng 2.0.2+ds-3 has caused the Debian Bug report #922265, regarding lemonldap-ng: FTBFS in sid (failing tests) to be marked as done. This means that you claim that the problem has

Bug#922272: marked as done (irssi-plugin-otr: trying to overwrite '/usr/share/irssi/help/otr', which is also in package irssi 1.2.0-1)

Your message dated Thu, 14 Feb 2019 13:35:31 +0100 with message-id and subject line Re: Bug#922272: irssi-plugin-otr: trying to overwrite '/usr/share/irssi/help/otr', which is also in package irssi 1.2.0-1 has caused the Debian Bug report #922272, regarding irssi-plugin-otr: trying to overwrite

Bug#922306: linux: btrfs corruption (compressed data + hole data)

Source: linux Version: 4.19.20-1 Severity: critical Tags: upstream patch Justification: causes serious data loss Hi. Apparently there was a longer existing data corruption bug in btrfs[0], AFAIU it happened when compression was used together with holes in data and there was *no* recognition by

Bug#907766: marked as done (node-chokidar: FTBFS in buster/sid (failing tests))

Your message dated Thu, 14 Feb 2019 12:19:06 + with message-id and subject line Bug#907766: fixed in node-chokidar 1.7.0-3 has caused the Debian Bug report #907766, regarding node-chokidar: FTBFS in buster/sid (failing tests) to be marked as done. This means that you claim that the problem

Bug#906390: marked as done (node-vhost: FTBFS in buster/sid (autobuilder hangs))

Your message dated Thu, 14 Feb 2019 12:04:14 + with message-id and subject line Bug#906390: fixed in node-vhost 3.0.2-1 has caused the Debian Bug report #906390, regarding node-vhost: FTBFS in buster/sid (autobuilder hangs) to be marked as done. This means that you claim that the problem has

Bug#907766: Bug #907766 in node-chokidar marked as pending

Control: tag -1 pending Hello, Bug #907766 in node-chokidar 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 #907766 in node-chokidar marked as pending

Processing control commands: > tag -1 pending Bug #907766 [src:node-chokidar] node-chokidar: FTBFS in buster/sid (failing tests) Added tag(s) pending. -- 907766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#906390: Bug #906390 in node-vhost marked as pending

Control: tag -1 pending Hello, Bug #906390 in node-vhost 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 #906390 in node-vhost marked as pending

Processing control commands: > tag -1 pending Bug #906390 [src:node-vhost] node-vhost: FTBFS in buster/sid (autobuilder hangs) Added tag(s) pending. -- 906390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#877202: Bug #877202 in pyxdg marked as pending

On Mon, 30 Apr 2018 at 02:35:03 +, a...@debian.org wrote: > New upstream release. > - Add support for Scale and ScaledDirectories keys (Closes: #877202). > - DesktopEntry: New method findTryExec() (Closes: #618514). > * Drop patches applied upstream: fix-DesktopEntry-docstring.patch >

Bug#922297: rxvt-unicode: *blink* *blink* *blink*

Package: rxvt-unicode Version: 9.22-5 Severity: grave Justification: makes my head hurt The terminal screen blinks all the time. -- System Information: Architecture: i386 Versions of packages rxvt-unicode depends on: ii libc6 2.28-7 ii libfontconfig12.13.1-2

Bug#922254: marked as done (jsxgraph: FTBFS (ERROR: module path does not exist))

Your message dated Thu, 14 Feb 2019 10:49:24 + with message-id and subject line Bug#922254: fixed in jsxgraph 1.3.5+dfsg1-2 has caused the Debian Bug report #922254, regarding jsxgraph: FTBFS (ERROR: module path does not exist) to be marked as done. This means that you claim that the problem

Bug#921796: marked as done (node-libnpx: FTBFS (failing tests))

Your message dated Thu, 14 Feb 2019 10:49:39 + with message-id and subject line Bug#921796: fixed in node-libnpx 10.2.0+repack-1 has caused the Debian Bug report #921796, regarding node-libnpx: FTBFS (failing tests) to be marked as done. This means that you claim that the problem has been

Bug#908815: [libdmtx0a] Structs in dmtx.h have changed without new ABI number

On Fri, 14 Sep 2018 at 12:24:52 +0200, Sven Schmidt wrote: > In header file dmtx.h the structs and enumeration in version 0.7.5 have > changed to insert a new varible "fnc1" representing undefinded state. > > When loading older DMTX binary linked against new libdmtx.so the program > will crash

Bug#921299: It is not caffe that is broken

Control: tags -1 moreinfo Control: reassign -1 doxygen Control: retitle -1 "Doxygen breaks caffe" Hi, I've build caffe with latest doxygen and can not confirm the result you wrote. The Build-Depends: doxygen-latex ensures that the style file `listofitems.sty' is available. I rather get a

Processed: It is not caffe that is broken

Processing control commands: > tags -1 moreinfo Bug #921299 [src:caffe] caffe: FTBFS with upcoming doxygen 1.8.15 Added tag(s) moreinfo. > reassign -1 doxygen Bug #921299 [src:caffe] caffe: FTBFS with upcoming doxygen 1.8.15 Bug reassigned from package 'src:caffe' to 'doxygen'. No longer marked

Bug#896596: poppler-glib always returns 0 length for PopplerInputStream

Control: tags -1 + patch On Sat, 28 Apr 2018 at 20:59:16 +0900, d...@debian.org wrote: > original bug report: https://bugs.debian.org/896596 > previous forwarded: https://github.com/ruby-gnome2/ruby-gnome2/issues/1159 > > below comments and patch by Kouhei Sutou . > > > Poppler adds getLength()

Processed: Re: Bug#896596: poppler-glib always returns 0 length for PopplerInputStream

Processing control commands: > tags -1 + patch Bug #896596 [libpoppler-glib8] poppler-glib always returns 0 length for PopplerInputStream Bug #897464 [libpoppler-glib8] ruby-cairo: FTBFS: ERROR: Test "ruby2.5" failed: Error: test: time(PDFSurfaceTest::#set_metadata::modified date):

  1   2   >