Bug#852048: marked as done (retitle: prospector: pinned pycodestyle version breaks prospector)

Your message dated Tue, 07 Feb 2017 07:33:28 + with message-id and subject line Bug#852048: fixed in prospector 0.12.4-2 has caused the Debian Bug report #852048, regarding retitle: prospector: pinned pycodestyle version breaks prospector to be marked as

Bug#848574: Fwd: Re: [open-mpi/ompi] Failure on mips64el (#2922)

The package in experimental (2.0.2-1) seems having no this problem. On Sun, 5 Feb 2017 19:11:04 + Alastair McKinstry wrote: > This hints at a linker issue on stretch > > Forwarded Message > Subject: Re: [open-mpi/ompi] Failure on mips64el

Processed: retitle 852048

Processing commands for cont...@bugs.debian.org: > retitle 852048 retitle: prospector: pinned pycodestyle version breaks > prospector Bug #852048 [prospector] pycodestyle >= 2.1.0 breaks prospector 0.12.4 Changed Bug title to 'retitle: prospector: pinned pycodestyle version breaks prospector'

Bug#851513: marked as done (Build fails with Linux kernel 4.9.0)

Your message dated Tue, 07 Feb 2017 06:33:43 + with message-id and subject line Bug#851513: fixed in zfs-linux 0.6.5.9-1 has caused the Debian Bug report #851513, regarding Build fails with Linux kernel 4.9.0 to be marked as done. This means that you

Bug#852253: kryo-serializers: no longer FTBFS in stretch

Source: kryo-serializers Followup-For: Bug #852253 I am not able to reproduce this bug and believe it can be closed. As Emmanuel suggests, it was addressed with the migration of libkryo-java 2.20-6 into testing on January 23rd [1]. Reproducible builds shows it building successfully in unstable

Processed: Re: Bug#854079: firefox-esr: firefox dies immediately on arm64

Processing control commands: > severity -1 serious Bug #854079 [firefox-esr] firefox-esr: firefox dies immediately on arm64 Severity set to 'serious' from 'important' -- 854079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854079 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#851612: CVE-2017-0381

On Mon, Feb 06, 2017 at 08:45:01PM +0100, Julien Cristau wrote: > On Tue, Jan 31, 2017 at 15:32:13 +1030, Ron wrote: > > > I've CC'd -release, to see what they'd prefer we do for Jessie. > > It might be that the best option here is to just put something later > > in -bpo, and if people are

Bug#854430: fritzing: Fritzing fails to find core parts

Package: fritzing Version: 0.9.3b+dfsg-4 Severity: grave Similar to 847655, while displaying a screen that says, "loading bin 'Core Parts'", Fritzing displays another screen that says, "Cannot read file screw_terminal_2_3.5mm.fzp: No such file or directory.". That file exists in

Bug#854314: youtube-dl: 'Signature extraction failed' on some YouTube videos

Hi. I'm using my phone to answer, so I will be brief. I intend to upload a new version of youtube-dl this week. -- Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito DebianQA:

Bug#854289: newbiedoc: Too outdated for being useful

Adrian Bunk wrote: > But as documentation for newbies (or anyone else) it is > no longer suitable. I agree. Any objection to removing this from Debian...? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Processed: Re: debdelta: installation leaves gpg-agent process running

Processing control commands: > fixed -1 debdelta/0.58exp Bug #852135 [debdelta] debdelta: installation leaves gpg-agent process running Marked as fixed in versions debdelta/0.58exp; no longer marked as fixed in versions debdelta/0.58exp. -- 852135:

Bug#852135: debdelta: installation leaves gpg-agent process running

Control: fixed -1 debdelta/0.58exp On Sat, 21 Jan 2017 21:41:02 +0100 Andreas Beckmann wrote: > This agent is automatically started by the gpg command in the postinst script > unfortunately there is no option to automatically terminate such a temporary > agent. But you could add the following

Processed: fixed 852135 in debdelta/0.58exp

Processing commands for cont...@bugs.debian.org: > fixed 852135 debdelta/0.58exp Bug #852135 [debdelta] debdelta: installation leaves gpg-agent process running Marked as fixed in versions debdelta/0.58exp. > thanks Stopping processing here. Please contact me if you need assistance. -- 852135:

Processed: retry

Processing commands for cont...@bugs.debian.org: > forwarded 831540 https://github.com/Theano/Theano/issues/5498 Bug #831540 [src:theano] theano: assertion error in test_fit_int64 on i386 and hurd/kreebsd-i386 Changed Bug forwarded-to-address to 'https://github.com/Theano/Theano/issues/5498'

Bug#848764: (no subject)

Control: tags -1 patch Three patches because this is logically three bugs, though it's filed as two upstream: https://github.com/Theano/Theano/issues/5494 https://github.com/Theano/Theano/issues/5396 First patch taken from upstream

Processed: bug 854280 is forwarded to https://github.com/matplotlib/matplotlib/issues/8034

Processing commands for cont...@bugs.debian.org: > forwarded 854280 https://github.com/matplotlib/matplotlib/issues/8034 Bug #854280 [src:matplotlib] matplotlib: contains image with non-free color calibration profile Set Bug forwarded-to-address to

Bug#831540: (no subject)

Control: forwarded -1 https://github.com/Theano/Theano/issues/5498 Control: tags -1 patch I don't think this is a regression - it's Python 3 specific (numpy.array(list of longs, which this test uses on Python 2)=int64 array, but numpy(list of Python 3 ints)=int_nativesize array; see above

Processed: tagging 854288

Processing commands for cont...@bugs.debian.org: > # As Adrian wrote: "b-d on clisp is not in stretch", but it _is_ in sid > tags 854288 - sid Bug #854288 [src:apt-dpkg-ref] apt-dpkg-ref FTBFS: build dependency clisp is not in stretch Removed tag(s) sid. > thanks Stopping processing here.

Bug#837004: marked as done (installation-locale: FTBFS: no output file produced because warnings were issued)

Your message dated Mon, 06 Feb 2017 22:34:20 + with message-id and subject line Bug#837004: fixed in installation-locale 1.7 has caused the Debian Bug report #837004, regarding installation-locale: FTBFS: no output file produced because warnings were

Bug#812002: smokeqt: FTBFS with GCC 6: deleted function

Control: tags -1 + patch On Tue, 19 Jan 2016 20:25:00 -0800 Martin Michlmayr wrote: > Package: smokeqt > Version: 4:4.14.3-1 > Severity: important > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-6 > > This package fails to build with GCC 6. GCC 6 has not been released >

Processed: Re: smokeqt: FTBFS with GCC 6: deleted function

Processing control commands: > tags -1 + patch Bug #812002 [smokeqt] smokeqt: FTBFS with GCC 6: deleted function Added tag(s) patch. -- 812002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: CVE-2016-9577 CVE-2016-9578

Processing control commands: > tags -1 patch Bug #854336 [src:spice] CVE-2016-9577 CVE-2016-9578 Added tag(s) patch. -- 854336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#854336: CVE-2016-9577 CVE-2016-9578

Control: tags -1 patch Hi, patches are available at http://pkgs.fedoraproject.org/cgit/rpms/spice.git/commit/?id=d919d639ae5f83a9735a04d843eed675f9357c0d signature.asc Description: OpenPGP digital signature

Processed: tagging 853935

Processing commands for cont...@bugs.debian.org: > # > https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=853935;filename=signature.asc;msg=36 > tags 853935 + pending Bug #853935 [rephrase] rephrase: No more works with gpg2 and causes one pinentry popup per guess Added tag(s) pending. >

Bug#854419: ifscheme: Path to ifstate is incorrect

Package: ifscheme Version: 1.7-4 Severity: grave Justification: renders package unusable Dear Maintainer, I just installed ifscheme on Debian Sid. ifscheme uses /etc/network/run/ifstate as the path to the interface state. But that file does not exist in Debian Sid. Debian Sid has

Bug#852048: pycodestyle >= 2.1.0 breaks prospector 0.12.4,,version graph

I've got deeper into it now. I think that was pinned by mistake, but pydocstyle was mend, the corresponding changelog entry is on that. I've commented on the commit [1], waiting for a reaction ... A simple patch for setup.py which removes the pinning would do it, because actually there are no

Processed: severity of 854405 is normal

Processing commands for cont...@bugs.debian.org: > severity 854405 normal Bug #854405 [reportbug] reportbug: Should handle missing optional runtime depencies more gracefully Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#854405: reportbug: Should handle missing optional runtime depencies more gracefully

reopen 854405 retitle 854405 reportbug: Should handle missing optional runtime depencies more gracefully severity 84405 normal kthxbye The issue is a little more complex. Reportbug behaves differently depending on which packages are missing. If python3-gi is missing, it falls back to text mode

Bug#850632: marked as done (openuniverse: fails to start "input in flex scanner failed)

Your message dated Mon, 06 Feb 2017 20:53:39 + with message-id and subject line Bug#850632: fixed in openuniverse 1.0beta3.1+dfsg-6 has caused the Debian Bug report #850632, regarding openuniverse: fails to start "input in flex scanner failed to be marked

Bug#852245: marked as done (python2-pyro4: Pyro4 require python selectors or selectors34 which are unavailable)

Your message dated Mon, 06 Feb 2017 20:53:52 + with message-id and subject line Bug#852245: fixed in pyro4 4.53-3 has caused the Debian Bug report #852245, regarding python2-pyro4: Pyro4 require python selectors or selectors34 which are unavailable to be

Processed (with 1 error): reportbug: Should handle missing optional runtime depencies more gracefully

Processing commands for cont...@bugs.debian.org: > reopen 854405 Bug #854405 {Done: Sandro Tosi } [reportbug] reportbug: Can't start reportbug from XFCE4 Menu Bug reopened Ignoring request to alter fixed versions of bug #854405 to the same values previously set > retitle

Bug#854405: reportbug: Can't start reportbug from XFCE4 Menu

Package: reportbug Version: 7.1.4 Followup-For: Bug #854405 It didn't fallback to command line. For me the missing package was gir1.2-vte-2.91. Regards Mechtilde -- Package-specific info: ** Environment settings: INTERFACE="gtk2" ** /home/mechtilde/.reportbugrc: reportbug_version "6.3.1"

Bug#851612: CVE-2017-0381

On 06/02/17 02:45 PM, Julien Cristau wrote: > On Tue, Jan 31, 2017 at 15:32:13 +1030, Ron wrote: > >> I've CC'd -release, to see what they'd prefer we do for Jessie. >> It might be that the best option here is to just put something later >> in -bpo, and if people are paranoid, they can choose to

Bug#851612: CVE-2017-0381

On Tue, Jan 31, 2017 at 15:32:13 +1030, Ron wrote: > I've CC'd -release, to see what they'd prefer we do for Jessie. > It might be that the best option here is to just put something later > in -bpo, and if people are paranoid, they can choose to use that? > I'd prefer to review patches rather

Bug#854405: marked as done (reportbug: Can't start reportbug from XFCE4 Menu)

Your message dated Mon, 6 Feb 2017 14:42:27 -0500 with message-id

Processed: Re: Bug#818379: doxygen: Does not properly trap for errors when calling dot

Processing control commands: > severity -1 important Bug #818379 [doxygen] doxygen: Does not properly trap for errors when calling dot Severity set to 'important' from 'serious' -- 818379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818379 Debian Bug Tracking System Contact

Bug#818379: doxygen: Does not properly trap for errors when calling dot

Control: severity -1 important On Wed, Mar 23, 2016 at 02:18:20PM +0100, Santiago Vila wrote: > I have at least one "successful" build log for each of the listed > packages which is not really successful because of errors in doxygen > that were not trapped. The build logs are similar to the ones

Bug#854405: reportbug: Can't start reportbug from XFCE4 Menu

Package: reportbug Version: 7.1.4 Severity: grave Justification: renders package unusable If I start it at console as described I get the following error message $ reportbug --exit-prompt --ui gtk2 Traceback (most recent call last): File "/usr/bin/reportbug", line 2234, in main() File

Bug#837004: installation-locale: FTBFS: no output file produced because warnings were issued

Aurelien Jarno (2017-02-06): > On 2017-02-06 00:50, Cyril Brulebois wrote: > > Hi, > > > > Aurelien Jarno (2017-02-06): > > > Well this kind of patch is not mergeable upstream, so we will have to > > > keep it forever. > > > > Or just for stretch

Bug#852893: marked as done (gtkhash: FTBFS: Test failures)

Your message dated Mon, 06 Feb 2017 18:03:46 + with message-id and subject line Bug#852893: fixed in gtkhash 1.0-2 has caused the Debian Bug report #852893, regarding gtkhash: FTBFS: Test failures to be marked as done. This means that you claim that the

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 854314 grave Bug #854314 [youtube-dl] youtube-dl: 'Signature extraction failed' on some YouTube videos Severity set to 'grave' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. --

Processed: [bts-link] source package tracker

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package tracker > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

Bug#842428: debsecan: error 403 forbidden since 10/27/2016

I just want to hint on a workaround for this bug by running: debsecan --config <(echo SOURCE="https://security-tracker.debian.org/tracker/debsecan/release/1/;) Tested to run fine on Squeeze, Wheezy and Jessie. Cheers, Lars

Bug#852811: udev: Doesn't start after upgrade mipsel, powerpc

Hi, On 06/02/17 13:52, Michael Biebl wrote: > Am 06.02.2017 um 11:21 schrieb James Cowgill: >> On Sun, 5 Feb 2017 12:16:41 + James Cowgill wrote: >>> Control: retitle -1 udev: Doesn't start after upgrade mipsel, powerpc >>> >>> Hi, >>> >>> FWIW, and as predicted by

Processed: Pending fixes for bugs in the golang-go-xdg package

Processing commands for cont...@bugs.debian.org: > tag 830446 + pending Bug #830446 [src:golang-go-xdg] golang-go-xdg: FTBFS: dh_auto_test: go test -v launchpad.net/go-xdg/v0 returned exit code 1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#830446: Pending fixes for bugs in the golang-go-xdg package

tag 830446 + pending thanks Some bugs in the golang-go-xdg package are closed in revision f50bcbb2cbb0b516fb45f729dff683e5f13c22c0 in branch ' mentors' by Roger Shimizu The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/golang-go-xdg.git/commit/?id=f50bcbb Commit

Bug#854390: python-bottle-cork: insecure default hashing algorithm

Source: python-bottle-cork Severity: grave Tags: upstream security Justification: user security hole As reported on https://github.com/FedericoCeratto/bottle-cork/issues/112, the "bottle-cork" module uses a very unsecure hashing algorithm (sha1 with 10 iterations) as default. the defaults should

Processed: fix version

Processing commands for cont...@bugs.debian.org: > found 854354 1.15.0-2 Bug #854354 {Done: Timo Aaltonen } [sssd] sssd prevents system booting up Bug #854048 {Done: Timo Aaltonen } [sssd] sssd: Socket activation of SSSD doesn't work and leads to chaos

Bug#854341: libchado-perl: FTBFS: The following enviroment variables not detected: CHADO_DB_USERNAME

Hi Chris, On Mon, Feb 06, 2017 at 10:31:18PM +1300, Chris Lamb wrote: > > I tried to build the package in an unstable chroot but can not > > reproduce the issue described below. > > How up-to-date? :) My chroot is completely and I can still reproduce. You catched me - after recreating my chroot

Bug#852811: udev: Doesn't start after upgrade mipsel, powerpc

Am 06.02.2017 um 11:21 schrieb James Cowgill: > On Sun, 5 Feb 2017 12:16:41 + James Cowgill wrote: >> Control: retitle -1 udev: Doesn't start after upgrade mipsel, powerpc >> >> Hi, >> >> FWIW, and as predicted by comments on the upstream bugreport, this also >> fails on

Bug#854354: [Pkg-sssd-devel] Bug#854354: Bug#854354: sssd prevents system booting up

On 06.02.2017 15:28, Jonathan McDowell wrote: > On Mon, Feb 06, 2017 at 02:50:27PM +0200, Timo Aaltonen wrote: >> On 06.02.2017 12:49, Jonathan McDowell wrote: >>> Package: sssd >>> Version: 1.50.0-2 >>> Severity: grave >>> >>> I updated my stretch system this morning which led to it failing to

Processed: bump severity

Processing commands for cont...@bugs.debian.org: > severity 854048 grave Bug #854048 {Done: Timo Aaltonen } [sssd] sssd: Socket activation of SSSD doesn't work and leads to chaos Bug #854354 {Done: Timo Aaltonen } [sssd] sssd prevents system booting up

Bug#854354: [Pkg-sssd-devel] Bug#854354: sssd prevents system booting up

forcemerge 854048 854354 thanks On 06.02.2017 12:49, Jonathan McDowell wrote: > Package: sssd > Version: 1.50.0-2 > Severity: grave > > I updated my stretch system this morning which led to it failing to > reach a login prompt; the system would start up and then avahi-daemon, > ModemManager and

Processed: Re: [Pkg-sssd-devel] Bug#854354: sssd prevents system booting up

Processing commands for cont...@bugs.debian.org: > forcemerge 854048 854354 Bug #854048 [sssd] sssd: Socket activation of SSSD doesn't work and leads to chaos Bug #854048 [sssd] sssd: Socket activation of SSSD doesn't work and leads to chaos There is no source info for the package 'sssd' at

Bug#852930: marked as done (libxml-security-java: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Mon, 06 Feb 2017 12:33:29 + with message-id and subject line Bug#852930: fixed in libxml-security-java 1.5.8-2 has caused the Debian Bug report #852930, regarding libxml-security-java: FTBFS: E: Build killed with signal TERM after 150

Bug#854355: Acknowledgement (/usr/bin/kmail: Unable to send emails - Could not compose message: Inappropriate ioctl for device)

The reason for this seems to be gnupg related: When I start KMail from a terminal and try to send a message, a text ssh-askpass dialogue is shown on the terminal. If I enter my gnupg key password there, the email is being send without any problems. My assumption is now that ksshaskpass is

Bug#787527: Upstream bug?

Hi, did anyone contacted upstream about this issue? Was a bug opened on bugs.chromium.org? If so, can anyone please share a bug number with me? Thank you, Tom

Bug#820974: plans for bug #820974

On Fri, 27 Jan 2017 08:06:08 -0500 Michael Gilbert wrote: > On Thu, Jan 26, 2017 at 6:41 AM, Arturo Borrero Gonzalez wrote: > > could you please share yours plans regarding this bug? > > Patches welcome? > Indeed, please see message 35 [0] in this same bug report. BTW this

Bug#854354: sssd prevents system booting up

Hi, Also, sprach Jonathan McDowell am Montag, den 06. Februar 2017 um 11:49: > Looking at the errors provided by systemd in my logs led me to: > > https://lists.debian.org/debian-user/2017/02/msg00025.html > > which provided the clue I needed to try downgrading ssd from > 1.15.0-2 (which was

Processed: found 827199 in 3.9.0~r4595-3

Processing commands for cont...@bugs.debian.org: > # From: Tino Didriksen > # To: 827...@bugs.debian.org > # Subject: Re: Bug#827199: hfst: FTBFS: twolc test fails on big-endian systems > # Date: Wed, 15 Jun 2016 17:03:20 +0200 > # ... > # While it did successfully build in

Bug#854355: /usr/bin/kmail: Unable to send emails - Could not compose message: Inappropriate ioctl for device

Package: kmail Version: 4:16.04.3-3 Severity: grave File: /usr/bin/kmail Justification: renders package unusable Dear Maintainer, whenever I try to send an email using KMail, I get following error message right after pressing the "Send" button: Could not compose message: Inappropriate ioctl

Bug#854354: sssd prevents system booting up

Package: sssd Version: 1.50.0-2 Severity: grave I updated my stretch system this morning which led to it failing to reach a login prompt; the system would start up and then avahi-daemon, ModemManager and NetworkManager would all fail to start, then systemd-logind would fail. This repeated in a

Processed: closing 852250

Processing commands for cont...@bugs.debian.org: > close 852250 Bug #852250 [lua-socket] [lua-socket] luasocket was not compiled with UNIX sockets support Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 852250:

Bug#852811: udev: Doesn't start after upgrade mipsel, powerpc

On Sun, 5 Feb 2017 12:16:41 + James Cowgill wrote: > Control: retitle -1 udev: Doesn't start after upgrade mipsel, powerpc > > Hi, > > FWIW, and as predicted by comments on the upstream bugreport, this also > fails on at least mipsel. I haven't checked the other mips

Processed: unattended-upgrades: files got created under /var/ mountpoint

Processing commands for cont...@bugs.debian.org: > severity 809669 critical Bug #809669 [unattended-upgrades] unattended-upgrades: files got created under /var/ mountpoint Severity set to 'critical' from 'important' > tags 809669 + patch Bug #809669 [unattended-upgrades] unattended-upgrades:

Bug#854346: tails-installer: Should not be part of Stretch

Package: tails-installer Severity: serious I'm opening this RC bug in order to prevent tails-installer from migrating to testing. The Tails ISO format might change, and upstream is not sure whether the current installer will still be able to install Tails images in ~2 years. That's why upstream

Bug#788062: os-prober corrupts LVs/partitions while being mounted inside a VM

In which cases does this happen? Should a vhost do high I/O at the time of os-prober running to get fs corrupted?

Bug#853119: texlive-luatex: basic lualatex document does not compile anymore without additionnal dependencies

> \usepackage[T1]{fontenc} Yes, that is anyway necessary, otherwise you would fall into OT1 encoding. Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3

Bug#851707: pinentry-gtk-2 frequently fails to grab the keyboard under awesome

On 2017-02-02 19:29:19 +0100, Vincent Bernat wrote: > Index: pinentry-1.0.0/gtk+-2/pinentry-gtk-2.c > === > --- pinentry-1.0.0.orig/gtk+-2/pinentry-gtk-2.c > +++ pinentry-1.0.0/gtk+-2/pinentry-gtk-2.c [...] > - while (tries++ <

Bug#852901: marked as done (lua-discount: FTBFS: Test failures)

Your message dated Mon, 06 Feb 2017 09:50:01 + with message-id and subject line Bug#852901: fixed in lua-discount 2.1.8-3 has caused the Debian Bug report #852901, regarding lua-discount: FTBFS: Test failures to be marked as done. This means that you

Bug#854341: libchado-perl: FTBFS: The following enviroment variables not detected: CHADO_DB_USERNAME

Andreas Tille wrote: > I tried to build the package in an unstable chroot but can not > reproduce the issue described below. How up-to-date? :) My chroot is completely and I can still reproduce. Glancing quickly at Makefile.PL and debian/rules it looks like the variable names have changed (eg.

Processed: [ti...@debian.org: Bug#854341: libchado-perl: FTBFS: The following enviroment variables not detected: CHADO_DB_USERNAME]

Processing commands for cont...@bugs.debian.org: > tag 854341 moreinfo, unreproducible Bug #854341 [src:libchado-perl] libchado-perl: FTBFS: The following enviroment variables not detected: CHADO_DB_USERNAME Added tag(s) moreinfo and unreproducible. > thanks Stopping processing here. Please

Bug#848999: marked as done (pinentry-gtk2: Fails to work, appears as gpg-agent not working)

Your message dated Mon, 06 Feb 2017 09:18:48 + with message-id and subject line Bug#851707: fixed in pinentry 1.0.0-2 has caused the Debian Bug report #851707, regarding pinentry-gtk2: Fails to work, appears as gpg-agent not working to be marked as done.

Bug#854280: matplotlib: contains image with non-free color calibration profile

Quoting Sandro Tosi (2017-02-06 05:41:38) > also, could you specify how to verify your claim? like: what command > to use, etc etc One approach is to use exiftool in the package libimage-exiftool-perl. Without options it summarizes metatags founds - which includes a copyright statement but no

Bug#850708: marked as done (pinentry-gtk-2 frequently fails to grab the pointer under fvwm)

Your message dated Mon, 06 Feb 2017 09:18:48 + with message-id and subject line Bug#850708: fixed in pinentry 1.0.0-2 has caused the Debian Bug report #850708, regarding pinentry-gtk-2 frequently fails to grab the pointer under fvwm to be marked as done.

Bug#851707: marked as done (pinentry-gtk-2 frequently fails to grab the keyboard under awesome)

Your message dated Mon, 06 Feb 2017 09:18:48 + with message-id and subject line Bug#851707: fixed in pinentry 1.0.0-2 has caused the Debian Bug report #851707, regarding pinentry-gtk-2 frequently fails to grab the keyboard under awesome to be marked as

Bug#854341: libchado-perl: FTBFS: The following enviroment variables not detected: CHADO_DB_USERNAME

tag -1 moreinfo, unreproducible thanks Hi, I tried to build the package in an unstable chroot but can not reproduce the issue described below. Kind regards Andreas. On Mon, Feb 06, 2017 at 09:26:27PM +1300, Chris Lamb wrote: > Source: libchado-perl > Version: 1.31-3 > Severity: serious

Bug#853119: texlive-luatex: basic lualatex document does not compile anymore without additionnal dependencies

Hi, sorry, this of course than can be fixed by e.g. \usepackage[T1]{fontenc} Cheers, Julian Am Mon, 6 Feb 2017 08:51:03 +0100 schrieb Julian Wollrath : > Hi Norbert, > > yes, the crash is unrelated, but it was the only log I had; sorry, I > should have used a better example.

Bug#851909: Patch works for me

The unreleased deb8u2 version fixes the login problem for me. Thanks, Nicola -- Nicola Mori, Ph.D. University of Florence and INFN Florence Via Bruno Rossi 1, 50019 Sesto F.no (Italy) +390554572660 m...@fi.infn.it smime.p7s Description: S/MIME Cryptographic Signature

Processed: forcibly merging 851707 848999

Processing commands for cont...@bugs.debian.org: > forcemerge 851707 848999 Bug #851707 [pinentry-gtk2] pinentry-gtk-2 frequently fails to grab the keyboard under awesome Bug #848999 [pinentry-gtk2] pinentry-gtk2: Fails to work, appears as gpg-agent not working Severity set to 'grave' from

Bug#852892: swi-prolog: FTBFS: Test failures

Hi Sébastien, 05.02.2017 22:11, Lev Lamberov пишет: > 05.02.2017 22:02, Sébastien Villemot пишет: >> Hi Lev, >> >> Le dimanche 05 février 2017 à 20:03 +0500, Lev Lamberov a écrit : >> >>> 05.02.2017 18:37, Sébastien Villemot пишет: On Sat, 28 Jan 2017 09:27:37 +0100 Lucas Nussbaum

Bug#854341: libchado-perl: FTBFS: The following enviroment variables not detected: CHADO_DB_USERNAME

Source: libchado-perl Version: 1.31-3 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, libchado-perl fails to build from source in unstable/amd64: