Bug#940578: printer-driver-cups-pdf: cups pdf printer cannot create pdf file

2019-09-18 Thread Martin-Éric Racine
ke 18. syysk. 2019 klo 12.11 intrigeri (intrig...@debian.org) kirjoitti: > > Martin-Éric Racine: > > ke 18. syysk. 2019 klo 10.03 intrigeri (intrig...@debian.org) kirjoitti: > >> C. Disable AppArmor confinement by default for the program that gets > >> bloc

Bug#940578: printer-driver-cups-pdf: cups pdf printer cannot create pdf file

2019-09-18 Thread Martin-Éric Racine
ke 18. syysk. 2019 klo 10.03 intrigeri (intrig...@debian.org) kirjoitti: > C. Disable AppArmor confinement by default for the program that gets blocked > >If you choose this option, then this bug should be reassigned to >cups-daemon. This indeed is the best option. Bugs about issues

Bug#940578: printer-driver-cups-pdf: cups pdf printer cannot create pdf file

2019-09-18 Thread Martin-Éric Racine
ke 18. syysk. 2019 klo 10.03 intrigeri (intrig...@debian.org) kirjoitti: >Here it's already kind of the case: >https://sources.debian.org/src/cups-pdf/3.0.1-5/debian/README.Debian/#L12 > >But that file incorrectly suggests that this caveat applies only to >Ubuntu, which is not the

Bug#940578: printer-driver-cups-pdf: cups pdf printer cannot create pdf file

2019-09-17 Thread Martin-Éric Racine
This very much seems like an issue caused by AppArmor. Reassigned. Martin-Éric ti 17. syysk. 2019 klo 16.45 Rudolf Polzer (rudolf.pol...@i-r-p.de) kirjoitti: > > Package: printer-driver-cups-pdf > Version: 3.0.1-5 > Severity: normal > > > > -- System Information: > Debian Release: 10.0 > APT

Bug#940089: debianutils: broken maintainer scripts

2019-09-12 Thread Martin-Éric Racine
Package: debianutils Version: 4.9 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Preparing to unpack .../debianutils_4.9_i386.deb ... Unpacking debianutils (4.9) over (4.8.6.3) ... Setting up debianutils (4.9) ... Use of uninitialized value $ARGV[0] in string ne at

Bug#935146: appstream: unable to open cache

2019-09-06 Thread Martin-Éric Racine
atthias Klumpp > : > > > > Am Di., 20. Aug. 2019 um 10:51 Uhr schrieb Martin-Éric Racine > > : > > > > > > Geode has no PAE. Maximum memory on these as per memory controller is > > > 1GB which is what it has. Part of this is used by the GPU. > > > >

Bug#935146: appstream: unable to open cache

2019-08-20 Thread Martin-Éric Racine
Swap: 1646624 0 1646624 ti 20. elok. 2019 klo 11.38 Matthias Klumpp (matth...@tenstral.net) kirjoitti: > > Am Di., 20. Aug. 2019 um 09:53 Uhr schrieb Matthias Klumpp > : > > > > Am Di., 20. Aug. 2019 um 09:24 Uhr schrieb Martin-Éric Racine > > : >

Bug#935146: appstream: unable to open cache

2019-08-20 Thread Martin-Éric Racine
Package: appstream Version: 0.12.8-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 When running 'apt-get update' I routinely get this error message: ** (appstreamcli:1275): CRITICAL **: 10:15:19.825: Unable to open temporary cache: Unable to open cache: Cannot allocate

Bug#934703: keyboard-configuration: debconf localisation for Finnish full of Russian and Spanish prompts

2019-08-15 Thread Martin-Éric Racine
to 15. elok. 2019 klo 17.30 Cyril Brulebois (k...@debian.org) kirjoitti: > > Martin-Éric Racine (2019-08-15): > > to 15. elok. 2019 klo 16.53 Cyril Brulebois (k...@debian.org) kirjoitti: > > > #924657 I suppose? > > > > It seems similar enough. However, #

Bug#934703: keyboard-configuration: debconf localisation for Finnish full of Russian and Spanish prompts

2019-08-15 Thread Martin-Éric Racine
to 15. elok. 2019 klo 16.53 Cyril Brulebois (k...@debian.org) kirjoitti: > Holger Wansing (2019-08-14): > > Martin-Éric Racine wrote: > > > Package: keyboard-configuration > > > Version: 1.191 > > > Severity: important > > > Tags: l10n > > &g

Bug#934703: keyboard-configuration: debconf localisation for Finnish full of Russian and Spanish prompts

2019-08-13 Thread Martin-Éric Racine
Package: keyboard-configuration Version: 1.191 Severity: important Tags: l10n -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The debconf template in keyboard-configuration for Finnish is full of prompts and selectable options written in Russian or Spanish. This is a serious usability issue.

Bug#934602: simple-scan: Stretch to Buster: scanning no longer works

2019-08-12 Thread Martin-Éric Racine
Package: simple-scan Version: 3.30.1.1-1+b1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Since upgrading to Buster, simple-scan fails silently. Upon startup, simple-scan correctly identifies the connected USB scanner, but selecting a text or picture to scan produces an

Bug#932211: gedit: Stretch to Buster: cursor is gone

2019-07-16 Thread Martin-Éric Racine
Package: gedit Version: 3.30.2-2 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Since upgrading to Buster, the cursor is no longer visible in gedit. - -- Package-specific info: Active plugins: - 'spell' - 'modelines' - 'filebrowser' - 'time' - 'docinfo' No

Bug#932189: gedit: Stretch to Buster: highlight misspelled words is broken

2019-07-16 Thread Martin-Éric Racine
Package: gedit Version: 3.30.2-2 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Since upgrading to Buster, the option to highlight misspelled words is broken. If the option is selected, the whole text (not just misspelled words) is highlighted. Unseöecting the option and

Bug#932114: bridge-utils: outdated scripts make the kernel complain

2019-07-15 Thread Martin-Éric Racine
Package: bridge-utils Version: 1.6-2 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 [ 33.066556] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. auto br0 iface br0 inet dhcp

Bug#931363: Fails to create output PDF (permission denied)

2019-07-06 Thread Martin-Éric Racine
sed CTRL-P in whichever application I was using at that moment. Martin-Éric ke 3. heinäk. 2019 klo 15.39 Martin-Éric Racine (martin-eric.rac...@iki.fi) kirjoitti: > > ke 3. heinäk. 2019 klo 14.51 martin f krafft (madd...@debian.org) kirjoitti: > > > > I straced gs run directly (as u

Bug#910344: libgssapi-krb5-2: conffiles not removed

2019-07-05 Thread Martin-Éric Racine
It is very much expected to be resolved. Please see: https://manpages.debian.org/wheezy/dpkg/dpkg-maintscript-helper.1.en.html pe 5. heinäk. 2019 klo 18.58 Benjamin Kaduk (ka...@mit.edu) kirjoitti: > > On Fri, Jul 05, 2019 at 06:35:20PM +0300, Martin-Éric Racine wrote: > > &g

Bug#931473: hostapd: Stretch to Buster: broken systemd integration

2019-07-05 Thread Martin-Éric Racine
Package: hostapd Version: 2:2.7+git20190128+0c1e29f-6 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After upgrading from Stretch to Buster, the hostapd stanza in /etc/network/interfaces is ignored. Instead, systemd tries to force-start hostapd, which fails anyhow, since

Bug#911744: thermald: conffiles not removed

2019-07-05 Thread Martin-Éric Racine
Package: thermald Followup-For: Bug #911744 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This issue is still not resolved in Buster, which is scheduled to become the new STABLE release tomorrow. - -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500,

Bug#910344: libgssapi-krb5-2: conffiles not removed

2019-07-05 Thread Martin-Éric Racine
Package: libgssapi-krb5-2 Version: 1.17-3 Followup-For: Bug #910344 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This issue is still not resolved in Buster, which is scheduled to become the new STABLE release tomorrow. - -- System Information: Debian Release: 10.0 APT prefers testing APT

Bug#931472: grub2-common: Stretch to Buster: two oldconfigs remaining

2019-07-05 Thread Martin-Éric Racine
Package: grub2-common Version: 2.02+dfsg1-20 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 During the upgrade from Stretch to Buster, dpkg reported the following oldconfig: grub2-common: /etc/kernel/postrm.d/zz-update-grub grub2-common: /etc/kernel/postinst.d/zz-update-grub

Bug#931471: deborphan: oldconfig: /etc/bash_completion.d/deborphan

2019-07-05 Thread Martin-Éric Racine
Package: deborphan Version: 1.7.31 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 During the upgrade from Stretch to Buster, dpkg reported the following oldconfig: /etc/bash_completion.d/deborphan This should have been removed by maintainer script helpers. - -- System

Bug#931469: apt-show-versions: oldconfig: /etc/bash_completion.d/apt-show-versions

2019-07-05 Thread Martin-Éric Racine
Package: apt-show-versions Version: 0.22.11 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 During the upgrade from Stretch to Buster, dpkg reported the following oldconfig: /etc/bash_completion.d/apt-show-versions This should have been removed by maintainer script helpers. -

Bug#928672: firmware-misc-nonfree: please include GV100 signed firmware

2019-07-05 Thread Martin-Éric Racine
Package: firmware-misc-nonfree Version: 20190114-1 Followup-For: Bug #928672 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This issue remains unresolved in Buster, which will become the Stable release tomorrow. - -- System Information: Debian Release: 10.0 APT prefers testing APT policy:

Bug#931363: Fails to create output PDF (permission denied)

2019-07-03 Thread Martin-Éric Racine
ke 3. heinäk. 2019 klo 14.51 martin f krafft (madd...@debian.org) kirjoitti: > > I straced gs run directly (as user "nobody"), as well as gs run from > cupsd. After replacing all hex addresses with 0xdeadbeef, the two > traces are nigh identical, except cupsd seems to close FDs 0–2, so > that when

Bug#931363: Fails to create output PDF (permission denied)

2019-07-03 Thread Martin-Éric Racine
ke 3. heinäk. 2019 klo 14.08 martin f krafft (madd...@debian.org) kirjoitti: > > Quoting "Martin-Éric Racine", who wrote on 2019-07-03 at 13:06 Uhr +0300: > >My best guess is that you bumped into a symptom of upgrading from > >cups-pdf 2 to cups-pdf 3. The back-en

Bug#931363: Fails to create output PDF (permission denied)

2019-07-03 Thread Martin-Éric Racine
ke 3. heinäk. 2019 klo 12.40 martin f krafft (madd...@debian.org) kirjoitti: > > Quoting "Martin-Éric Racine", who wrote on 2019-07-03 at 11:18 Uhr +0300: > >Is the host where this fails running a cups-pdf that was upgraded from > >previous > >releases? >

Bug#931363: Fails to create output PDF (permission denied)

2019-07-03 Thread Martin-Éric Racine
Hey Martin, Thanks for this bug report. Is the host where this fails running a cups-pdf that was upgraded from previous releases? Martin-Éric ke 3. heinäk. 2019 klo 11.09 martin f krafft (madd...@debian.org) kirjoitti: > Package: printer-driver-cups-pdf > Version: 3.0.1-5 > Severity: normal

Bug#931335: lightdm: default configuration fails to start

2019-07-02 Thread Martin-Éric Racine
Package: lightdm Version: 1.26.0-4 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The package currently shipping fails to work with the stock configuration: Upon first run, it complains about a missing '/var/lib/lightdm/data' and exits. Manually creating the directory and

Bug#924243: debuild: debsign ignores DEB_SIGN_KEYID value

2019-03-10 Thread Martin-Éric Racine
Package: devscripts Version: 2.19.3 Severity: important Since recent devscripts releases, debuild calls debsign in a way that ignores the value of DEB_SIGN_KEYID, which results in gnupg asking for the password of an GPG obsolete key. DEB_SIGN_KEYID value is the same in .bashrc and in

Bug#922045: logrotate.service: Failed with result 'exit-code'.

2019-02-11 Thread Martin-Éric Racine
Package: logrotate Version: 3.14.0-4 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Systemd systematically reports a failure to launch logrotate: $ LC_ALL=C systemctl status logrotate.service * logrotate.service - Rotate log files Loaded: loaded

Bug#922039: dpkg-buildpackage: error: short OpenPGP key IDs are broken; please use key fingerprints instead

2019-02-11 Thread Martin-Éric Racine
Package: dpkg-dev Version: 1.19.2 Severity: important The above error message is useless. It doesn't tell what needs to be fixed or where. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (800, 'unstable') Architecture: i386 (x86_64) Kernel: Linux

Bug#903343: two causes

2018-07-31 Thread Martin-Éric Racine
The causes are simple: First of all: $ find . -name '*README*' ./README.md This would suggest a raw README with markup, except that 1) there is no markup in that file and 2) no README gets generated. Additionaly, we try to install two fles that were not generated: $ cat debian/docs README

Bug#904327: clamav-freshclam: more specific error code to indicate failure

2018-07-23 Thread Martin-Éric Racine
Package: clamav-freshclam Version: 0.100.0+dfsg-0+deb9u2 Severity: important Related to bug #903896, I cannot help but notice the content of the e-mail that is sent to the administrator: XSubject: [voima] job cron-clamav-freshclam-clamav-0 failed ● cron-clamav-freshclam-clamav-0.service -

Bug#903896: freshclam: 0.100.1 to Stable ASAP: cron job complains about old version

2018-07-16 Thread Martin-Éric Racine
Here's a result of a manual run of freshclam: $ sudo freshclam Mon Jul 16 18:39:33 2018 -> ClamAV update process started at Mon Jul 16 18:39:33 2018 Mon Jul 16 18:39:33 2018 -> ^Your ClamAV installation is OUTDATED! Mon Jul 16 18:39:33 2018 -> ^Local version: 0.100.0 Recommended version: 0.100.1

Bug#903896: freshclam: 0.100.1 to Stable ASAP: cron job complains about old version

2018-07-16 Thread Martin-Éric Racine
Package: clamav-freshclam Version: 0.100.0+dfsg-0+deb9u2 Severity: important clamav-freshclam has started complaining about an outdated version. This complain is sent at regular intervals whenever the cron job tries to fetch updates. This seems to be due to upstream having started pushing data

Bug#900108: xserver-xorg-video-geode: FTBFS with xserver 1.20

2018-07-09 Thread Martin-Éric Racine
It ought to be noted that: 1) This bug was fixed ages ago. 2) It only concerns building against Xserver 1.20, which has been stuck in unstable for ages. 3) Basically, the version in testing works as expected with the Xserver that is in testing. Despite this, xf86-video-geode has been slated for

Bug#896831: rapid-photo-downloader: needs a dependency on libmediainfo0v5

2018-04-24 Thread Martin-Éric Racine
Package: rapid-photo-downloader Version: 0.9.9-1 Severity: important RPD currently depends on python3-pymediainfo, which itself does NOT depend upon libmediainfo0v5. As a result, upon startup, RPD complains that some features won't be available because mediainfo doesn't seem to be installed.

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

2018-04-01 Thread Martin-Éric Racine
: >> >> Am 19.12.2017 um 02:18 schrieb Martin-Éric Racine: >> >> > 2017-12-19 2:02 GMT+02:00 Michael Biebl <bi...@debian.org>: >> >> >> Am 18.12.2017 um 20:07 schrieb Martin-Éric Racine: >> >> >>> 2017-12-18 2:08 GMT+02:00 Mich

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

2018-01-16 Thread Martin-Éric Racine
2018-01-17 4:24 GMT+02:00 Michael Biebl <bi...@debian.org>: > On Tue, 19 Dec 2017 06:55:34 +0100 Michael Biebl <bi...@debian.org> wrote: >> Am 19.12.2017 um 02:18 schrieb Martin-Éric Racine: >> > 2017-12-19 2:02 GMT+02:00 Michael Biebl <bi...@debian.org>:

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

2018-01-03 Thread Martin-Éric Racine
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,

Bug#757909: pulseaudio-module-gconf: migration to a dconf PA backend

2017-12-29 Thread Martin-Éric Racine
At least, paprefs uses gconf as its backend, Martin-Éric 2017-12-30 3:22 GMT+02:00 Jeremy Bicha : > Control: severity -1 important > Control: user pkg-gnome-maintain...@lists.alioth.debian.org > Control: usertags -1 oldlibs gconf > > As far as I am aware, there is no desktop

Bug#802026: bug still present with 2.1?

2017-12-20 Thread Martin-Éric Racine
2017-12-20 14:43 GMT+02:00 David Bremner : > > Control: tag -1 moreinfo > > Can you confirm this problem is still present in 2.1-*? nullmailer. Right. Had to look up the bug report to even know what you were asking about. Seems to work fine now. Let's close this. Cheers!

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

2017-12-18 Thread Martin-Éric Racine
2017-12-19 2:02 GMT+02:00 Michael Biebl <bi...@debian.org>: > Am 18.12.2017 um 20:07 schrieb Martin-Éric Racine: >> 2017-12-18 2:08 GMT+02:00 Michael Biebl <bi...@debian.org>: >>> Hi, >>> >>> I just uploaded v236 today. Before we try to debug thi

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

2017-12-18 Thread Martin-Éric Racine
2017-12-18 2:08 GMT+02:00 Michael Biebl : > Hi, > > I just uploaded v236 today. Before we try to debug this further, it > would be great if you can give this version a try. Maybe your issue is > already fixed. > If not, we'll have to involve upstream at some point by filing an >

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

2017-12-13 Thread Martin-Éric Racine
2017-12-13 22:58 GMT+02:00 Michael Biebl <bi...@debian.org>: > Control: found 883877 235-3 > > Am 08.12.2017 um 21:47 schrieb Martin-Éric Racine: >> http://q-funk.iki.fi/core.systemd.2857 >> > > Not really a backtrace, but a core file, but ok. > Looks like t

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

2017-12-08 Thread Martin-Éric Racine
http://q-funk.iki.fi/core.systemd.2857 http://q-funk.iki.fi/reportbug-systemd-backup-20171208-3454-me2okrv0 2017-12-08 22:26 GMT+02:00 Michael Biebl <bi...@debian.org>: > Am 08.12.2017 um 20:37 schrieb Martin-Éric Racine: >> 2017-12-08 21:31 GMT+02:00 Michael Biebl <bi...@d

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

2017-12-08 Thread Martin-Éric Racine
2017-12-08 21:31 GMT+02:00 Michael Biebl <bi...@debian.org>: > Am 08.12.2017 um 20:27 schrieb Martin-Éric Racine: >> I can reproduce the problem. >> > > After a reboot? Yes.

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

2017-12-08 Thread Martin-Éric Racine
I can reproduce the problem. Why didn't you just reassign the bug instead of closing it, if you think that it's the wrong package? Martin-Éric 2017-12-08 20:49 GMT+02:00 Michael Biebl <bi...@debian.org>: > Am 08.12.2017 um 19:10 schrieb Martin-Éric Racine: >> Package: rsyslog >

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

2017-12-08 Thread Martin-Éric Racine
Package: rsyslog Version: 8.31.0-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 $ sudo LC_ALL=C dpkg --configure --pending Setting up rsyslog (8.31.0-1) ... Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out

Bug#865880: deborphan: reports packages that are Recommends of others

2017-06-25 Thread Martin-Éric Racine
Package: deborphan Version: 1.7.28.8-0.3+b1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The options I use: - --guess-all --libdevel What deborphan suggests removing: python-cffi-backend* python-cryptography* python-enum34* python-openssl* python-pyasn1* Why removing

Bug#865766: printer-driver-cups-pdf: Bdependenca problem - printer-driver-cups-pdf cannot be upgraded to 3.0.1

2017-06-24 Thread Martin-Éric Racine
Greetings, I'm really not sure I understand what the problem is. Removing the transitional package 'cups-pdf' is entirely the job of whichever package manager you use, typically 'apt' or 'aptitude'. This is never handled by the packages themselves. Martin-Éric 2017-06-24 19:31 GMT+03:00 Hans-J.

Bug#714414: 05_debian_theme: make colours user-configurable

2017-06-21 Thread Martin-Éric Racine
Package: grub-pc Version: 2.02~beta3-5 Followup-For: Bug #714414 This issue is caused by hardwired colors in 05_debian_theme. Unless the script finds that 1) GRUB is running on an Ubuntu host OR that 2) a background image exists, cyan/blue and white/blue colors are enforced. Adding insult to

Bug#865170: libexif-gtk5: Depends on a transitional package

2017-06-19 Thread Martin-Éric Racine
Package: libexif-gtk5 Version: 0.3.5-5 Severity: important $ sudo dpkg -P $(dpkg -l | grep transitional | awk '{print $2}') dpkg: dependency problems prevent removal of libpango1.0-0:amd64: libexif-gtk5 depends on libpango1.0-0 (>= 1.14.0). dpkg: error processing package libpango1.0-0:amd64

Bug#865169: python-poppler: Depends on transitional package python-gobject

2017-06-19 Thread Martin-Éric Racine
Package: python-poppler Version: 0.12.1-9 Severity: important $ sudo dpkg -P $(dpkg -l | grep transitional | awk '{print $2}') dpkg: dependency problems prevent removal of python-gobject: python-poppler depends on python-gobject (>= 2.10.1). dpkg: error processing package python-gobject

Bug#673589: gnome-online-accounts: Google account credentials expire immediately after login

2017-06-12 Thread Martin-Éric Racine
Package: gnome-online-accounts Version: 3.22.5-1 Followup-For: Bug #673589 Just upgraded to Stretch. Google credentials from Jessie no longer work. GOA tells me that credentials have expired. I went and gave Google permission to allow application GNOME. Exit GOA. Upon returning to GOA, it shows

Bug#823796: Phatch RC bug

2017-06-02 Thread Martin-Éric Racine
It wasn't there this morning when I fetched the sources and attempted to produce the NMU. All is good then. Thanks! 2017-06-02 10:53 GMT+03:00 Emilio Pozuelo Monfort <po...@debian.org>: > On 02/06/17 09:07, Martin-Éric Racine wrote: >> Greetings, >> >> I've tried m

Bug#823796: Phatch RC bug

2017-06-02 Thread Martin-Éric Racine
Greetings, I've tried merging this patch to submit an NMU. This fails miserably because the existing patches are not applied in a known order and dpkg complains loudly that patches are either fuzzy or cannot be applied as-is. To guarantee that patches are always applied in the same order, their

Bug#861012: bridge-utils: fetches IP via wrong interface

2017-04-23 Thread Martin-Éric Racine
Package: bridge-utils Version: 1.5-9 Severity: normal Dear maintainer, On one particular host, bridge-utils insists upon fetching an IP via the wrong interface. It uses the MAC address of eth1 even though the connection to the outside world comes via eth0. My /etc/network/interfaces: auto lo

Bug#559685: still valid as of CUPS-PDF 2.5.1 ?

2017-03-11 Thread Martin-Éric Racine
Greetings, Does this issue still apply to 3.0.1-3 (currently found in unstable)? Martin-Éric

Bug#847462: the problem is with CUPS

2017-03-04 Thread Martin-Éric Racine
2017-03-04 20:43 GMT+02:00 Brian Potkin <claremont...@gmail.com>: > On Fri 03 Mar 2017 at 20:28:56 +0200, Martin-Éric Racine wrote: > >> 2017-03-03 18:25 GMT+02:00 Francesco Potortì <poto...@isti.cnr.it>: >> >> > This apparently has to do with the old proble

Bug#847462: the problem is with CUPS

2017-03-03 Thread Martin-Éric Racine
2017-03-03 18:25 GMT+02:00 Francesco Potortì : > This apparently has to do with the old problem of cups-pdf converting > PDF to PS and back to PDF. > > I have an old Ubuntu Lucid installation where the problem does not > exist. Debian and Ubuntu both briefly used a patch

Bug#856128: debian-watch-may-check-gpg-signature: false positives

2017-02-26 Thread Martin-Éric Racine
2017-02-26 12:07 GMT+02:00 Mattia Rizzolo <mat...@debian.org>: > Control: tag -1 moreinfo > > On Sat, Feb 25, 2017 at 01:04:54PM +0000, Martin-Éric Racine wrote: >> It appears that debian-watch-may-check-gpg-signature generates false >> positives. >> >>

Bug#856128: debian-watch-may-check-gpg-signature: false positives

2017-02-25 Thread Martin-Éric Racine
Package: lintian Version: 2.5.50.1 Severity: normal It appears that debian-watch-may-check-gpg-signature generates false positives. On src:cups-pdf Lintian reports debian-watch-may-check-gpg-signature yet upstream does not publish any GPG signature. However, upstream does publish

Bug#679645: devscripts: debuild does not properly forward coloured output

2017-02-23 Thread Martin-Éric Racine
2017-02-23 14:27 GMT+02:00 James McCoy <james...@debian.org>: > On Thu, Feb 23, 2017 at 11:55:04AM +0000, Martin-Éric Racine wrote: >> Basically, if >> dpkg-buildpackage finds the terminal and enables colors accordingly, >> there is no reason for debuild to f

Bug#679645: devscripts: debuild does not properly forward coloured output

2017-02-23 Thread Martin-Éric Racine
Package: devscripts Version: 2.17.1 Followup-For: Bug #679645 Except that 'debuild' very much is run from CLI. Basically, if dpkg-buildpackage finds the terminal and enables colors accordingly, there is no reason for debuild to fail at finding the terminal and asking dpkg to run in colorized

Bug#855646: linux-image-4.9.0-1-686-pae: [i915] kernel oops on Dell D430

2017-02-20 Thread Martin-Éric Racine
Package: src:linux Version: 4.9.6-3 Severity: important The DRM driver for i915 hardware oopses in a systematic way during bootup on this Dell D430 using kernel 4.9 from testing/frozen. Booting with kernel 3.16 from stable/updates doesn't produce these symptoms. -- Package-specific info: **

Bug#851072: gdm3: barfs if x-x-i-evdev|mouse|synaptics is installed on Linux 4.x kernel host

2017-01-12 Thread Martin-Éric Racine
2017-01-12 13:17 GMT+02:00 Andreas Henriksson <andr...@fatal.se>: > Control: tags -1 + unreproducible moreinfo > > Hello Martin-Éric Racine, > > On Thu, Jan 12, 2017 at 12:56:40AM +0200, Martin-Éric Racine wrote: >> Package: gdm3 >> Version: 3.22.1-1 >> S

Bug#851072: gdm3: barfs if x-x-i-evdev|mouse|synaptics is installed on Linux 4.x kernel host

2017-01-11 Thread Martin-Éric Racine
Package: gdm3 Version: 3.22.1-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 If xserver-xorg-input-[evdev|mouse|synaptics] are installed on an host running current X, GDM3 fails to start. Removing those allows GDM to start again. - -- System Information: Debian Release:

Bug#848709: xserver-xorg-video-geode-dbg: depends on xserver-xorg-core-dbg, which is no longer built

2016-12-19 Thread Martin-Éric Racine
2016-12-19 20:26 GMT+02:00 Emilio Pozuelo Monfort : > Package: xserver-xorg-video-geode-dbg > Version: 2.11.18-2 > Severity: serious > > Hi, > > x-x-v-geode-dbg depends on xserver-xorg-core-dbg, but we no longer build > that, and rely on debhelper creating dbgsym packages

Bug#839259: W: Target Contents-deb-legacy (Contents-{amd64, i386, all}) is configured multiple times in /etc/apt/sources.list

2016-12-18 Thread Martin-Éric Racine
2016-12-18 14:20 GMT+02:00 Niels Thykier <ni...@thykier.net>: > Martin-Éric Racine wrote: >> Package: apt >> Version: 1.4~beta1 >> Followup-For: Bug #839259 >> >> Maintainers, >> >> Could we please hear the rationale for this change? >

Bug#839259: W: Target Contents-deb-legacy (Contents-{amd64, i386, all}) is configured multiple times in /etc/apt/sources.list

2016-12-08 Thread Martin-Éric Racine
Package: apt Version: 1.4~beta1 Followup-For: Bug #839259 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Maintainers, Could we please hear the rationale for this change? More to the point, what would a non-legacy target be expected to look like? Cheers! Martin-Éric -BEGIN PGP

Bug#846036: xul-ext-mozvoikko: please package new upstream 2.2

2016-11-28 Thread Martin-Éric Racine
ite. + * [debian/watch] + = Migrated the watch URL to the current upstream site. + + Added checking of the upstream GPG signature. + * [debian/upstream/signing-key.asc] + + Imported upstream's public GPG key block. + + -- Martin-Éric Racine <martin-eric.rac...@iki.fi> Mon, 28 No

Bug#846036: xul-ext-mozvoikko: please package new upstream 2.2

2016-11-27 Thread Martin-Éric Racine
Package: xul-ext-mozvoikko Version: 2.0.1-1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 In the process of overhauling the packaging of mozvoikko, I found out that the upstream source has migrated to a new host and that a new version has been released. My proposed

Bug#846022: nmu: mozvoikko_2.0.1-1

2016-11-27 Thread Martin-Éric Racine
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 nmu mozvoikko_2.0.1-1 . ANY . stretch . -m "Rebuild to drop iceweasel Depends and migrate to firefox-esr (Closes: #819457)." - -- System

Bug#819457: xul-ext-mozvoikko: Please add firefox(-esr) as alternative dependencies

2016-11-27 Thread Martin-Éric Racine
Package: xul-ext-mozvoikko Version: 2.0.1-1 Followup-For: Bug #819457 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Looking at the Debian source, all this needs to get fixed is a bin-NMU. The source Build-Depends on mozilla-devscripts which provides an extension that is called in

Bug#843910: cups-pdf FTCBFS: uses build architecture compiler

2016-11-16 Thread Martin-Éric Racine
2016-11-16 16:40 GMT+02:00 Helmut Grohne <hel...@subdivi.de>: > On Wed, Nov 16, 2016 at 01:59:50PM +0200, Martin-Éric Racine wrote: >> I cannot help but wonder if setting CC for cross-build would be best >> handled by the build tools themselves, rather than compensated

Bug#843910: cups-pdf FTCBFS: uses build architecture compiler

2016-11-16 Thread Martin-Éric Racine
2016-11-10 18:10 GMT+02:00 Helmut Grohne : > Source: cups-pdf > Version: 2.6.1-21 > Tags: patch > User: helm...@debian.org > Usertags: rebootstrap > > cups-pdf fails to cross build from source, because it uses the build > architecture compiler. Defaulting CC to a

Bug#841700: linux-image-4.7.0-1-686: upgrade from 4.7.6-1 to 4.7.8-1 prevents booting; freezes during initrd loading

2016-10-24 Thread Martin-Éric Racine
2016-10-24 16:21 GMT+03:00 Ben Hutchings <b...@decadent.org.uk>: > On Mon, 2016-10-24 at 11:02 +0300, Martin-Éric Racine wrote: >> > 2016-10-24 5:00 GMT+03:00 Ben Hutchings <b...@decadent.org.uk>: >> > Control: tag -1 moreinfo >> > >> > On Sat,

Bug#841700: linux-image-4.7.0-1-686: upgrade from 4.7.6-1 to 4.7.8-1 prevents booting; freezes during initrd loading

2016-10-24 Thread Martin-Éric Racine
2016-10-24 5:00 GMT+03:00 Ben Hutchings <b...@decadent.org.uk>: > Control: tag -1 moreinfo > > On Sat, 2016-10-22 at 16:24 +0300, Martin-Éric Racine wrote: >> Package: src:linux >> Version: 4.7.8-1 >> Severity: important >> >> After upgrading from 4

Bug#841700: linux-image-4.7.0-1-686: upgrade from 4.7.6-1 to 4.7.8-1 prevents booting; freezes during initrd loading

2016-10-22 Thread Martin-Éric Racine
Package: src:linux Version: 4.7.8-1 Severity: important After upgrading from 4.7.6-1 to 4.7.8-1 this host cannot boot under kernel 4 anymore. The host freezes while loading the initrd image. GRUB displays "loading linux-image", followed by "loading initrd-image" and then become unresponsive.

Bug#841531: openssh-client: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1

2016-10-21 Thread Martin-Éric Racine
2016-10-21 14:40 GMT+03:00 Adam D. Barratt <a...@adam-barratt.org.uk>: > On 2016-10-21 12:26, Martin-Éric Racine wrote: >> >> Unable to negotiate with 172.16.1.254 port 22: no matching key >> exchange method found. Their offer: diffie-hellman-group1-sha1 >> >

Bug#841531: openssh-client: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1

2016-10-21 Thread Martin-Éric Racine
Package: openssh-client Version: 1:7.3p1-1 Severity: important Unable to negotiate with 172.16.1.254 port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 I get the above error when trying to connect to a router using openssh-client from Testing. Connecting

Bug#841510: gnome-shell: various bugs under xf86-video-nouveau

2016-10-21 Thread Martin-Éric Racine
Package: gnome-shell Version: 3.22.1-1 Severity: important As the attached logs show, gnome-session fails at making a number of operations when running under xf86-video-nouveau. This causes random freezes and video randering bugs. -- System Information: Debian Release: stretch/sid APT

Bug#644838: xserver-xorg-video-nouveau: X lockup, DRM reports "fail ttm_validate" and DMA_W_PROTECTION fault

2016-10-21 Thread Martin-Éric Racine
Package: xserver-xorg-video-nouveau Version: 1:1.0.13-1 Followup-For: Bug #644838 This issues still exists in Testing. It regularly makes gnome-session take up to 50% of available memory, at which point the desktop session completely freezes for a few minutes. -- Package-specific info: X

Bug#822081: gnome-control-center: Mouse settings have no effect since 3.20

2016-10-17 Thread Martin-Éric Racine
Package: gnome-control-center Version: 1:3.22.1-1 Followup-For: Bug #822081 Here, I don't have any touchpad since this is a desktop. However, left-handed mouse is completely ignored since 3.20 came into testing. -- System Information: Debian Release: stretch/sid APT prefers testing APT

Bug#839259: W: Target Contents-deb-legacy (Contents-{amd64, i386, all}) is configured multiple times in /etc/apt/sources.list

2016-10-12 Thread Martin-Éric Racine
Package: apt Version: 1.3.1 Followup-For: Bug #839259 I just noticed this when I upgraded one host from stable. Until recently, Contents-{arch} wasn't fetched at all. Now, it is fetched for every FQDN present in sources.list or in sources.list.d files. The problem is that the change doesn't

Bug#840433: gnome-shell: barfs on Nouveau X.org

2016-10-11 Thread Martin-Éric Racine
Package: gnome-shell Version: 3.22.0-1+b1 Severity: important [ 270.252432] nouveau :00:05.0: gnome-shell[1197]: fail ttm_validate [ 270.252439] nouveau :00:05.0: gnome-shell[1197]: validating bo list [ 270.252454] nouveau :00:05.0: gnome-shell[1197]: validate: -12 I get this

Bug#819457: xul-ext-mozvoikko: Please add firefox(-esr) as alternative dependencies

2016-10-11 Thread Martin-Éric Racine
Package: xul-ext-mozvoikko Version: 2.0.1-1 Followup-For: Bug #819457 Heikki, Would you kindly allow an NMU on the package currently in unstable? -- System Information: Debian Release: 8.6 APT prefers stable APT policy: (, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64)

Bug#840409: gnome-shell: Depends on gnome-backgrounds perhaps excessive?

2016-10-11 Thread Martin-Éric Racine
Package: gnome-shell Version: 3.22.0-1+b1 Severity: normal Greetings, I cannot help but wonder why gnome-backgrounds is an absolute Depends rather than a mere Recommends. While there is nothing wrong with the background images per-se, I simply have no use for them and they are wasting space

Bug#840391: mouse: left-handed setting ignored

2016-10-11 Thread Martin-Éric Racine
Package: gnome-control-center Version: 1:3.14.2-3 Severity: important For whatever reason, the left/right preference in the mouse settings is ignored by gnome-settings-daemon. The desktop forcefully runs as right-handed. -- System Information: Debian Release: 8.6 APT prefers stable APT

Bug#814599: [Bash-completion-devel] Bug#814599: bash-completion: different behavior in /etc/bash_completion.d/ than in /usr/share/bash-completion/completions/

2016-10-01 Thread Martin-Éric Racine
2016-10-01 12:41 GMT+03:00 Paul Wise <p...@debian.org>: > On Sat, 13 Feb 2016 21:50:19 +0200 Martin-Éric Racine wrote: > >> This detail would need to be added to the error that Lintian throws at >> maintainers when their script is still at the old location. > >

Bug#838919: closed by Ben Hutchings <b...@decadent.org.uk> (Re: Bug#838919: debian-installer: please calculate swap parition according to max RAM supported by the motherboard)

2016-09-29 Thread Martin-Éric Racine
2016-09-29 14:15 GMT+03:00 Ben Hutchings <b...@decadent.org.uk>: > On Wed, 2016-09-28 at 16:20 +0300, Martin-Éric Racine wrote: > [...] >> The thing is, right now, the user has two choices: >> >> 1) Trust d-i to make the right choices once, even though more RAM

Bug#838919: closed by Ben Hutchings <b...@decadent.org.uk> (Re: Bug#838919: debian-installer: please calculate swap parition according to max RAM supported by the motherboard)

2016-09-28 Thread Martin-Éric Racine
therboard > On Mon, 2016-09-26 at 10:23 -0400, Lennart Sorensen wrote: >> On Mon, Sep 26, 2016 at 05:06:18PM +0300, Martin-Éric Racine wrote: >> > >> > Package: debian-installer >> > Severity: wishlist >> > >> > As far as I can tell, d-i ca

Bug#838919: debian-installer: please calculate swap parition according to max RAM supported by the motherboard

2016-09-26 Thread Martin-Éric Racine
Package: debian-installer Severity: wishlist As far as I can tell, d-i calculates the size of the swap partition according to the curently installed amount of RAM. Whenever the RAM is upgraded later on, the swap parition no longer fulfills its intended purpose, in cases when it would be needed

Bug#830066: tidy: fails to use ~/.tidy.conf , unless HTML_TIDY is appropriately set

2016-08-02 Thread Martin-Éric Racine
Package: tidy Version: 1:5.2.0-1.1 Followup-For: Bug #830066 Was also bitten by this bug. I really cannot help but wonder what was the point of migrating from .tidyrc to .tidy.conf and of not even attempting to source the user's own config in the first place. I would treat issue this as a

Bug#828746: hwclock: RTC to wrong offset after reboot

2016-06-27 Thread Martin-Éric Racine
2016-06-27 23:34 GMT+03:00 Andreas Henriksson : > Control: tags -1 + moreinfo > > Please check the contents of your /etc/adjtime for starters. UTC as expected. > Given you're using systemd you're not even running hwclock during your > boot. Please see 'systemctl status

Bug#828746: hwclock: RTC to wrong offset after reboot

2016-06-27 Thread Martin-Éric Racine
Package: util-linux Version: 2.28-5 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Whenever rebooting this host, the RTC time is 3 hours ahead of what it should be. This wasn't the case when using whatever is currently in Debian/stable. - -- System Information: Debian

Bug#827457: cups-browsed: upgrade fails

2016-06-16 Thread Martin-Éric Racine
Package: cups-browsed Version: 1.9.0-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Setting up cups-browsed (1.9.0-1) ... Failed to start cups-browsed.service: Unit cups.service not found. invoke-rc.d: initscript cups-browsed, action "start" failed. dpkg: error processing

Bug#827385: opensc: browser plug-in: enable software selection of card slot

2016-06-15 Thread Martin-Éric Racine
Package: opensc Version: 0.14.0-2 Severity: wishlist Currently, OpenSC requires configuring which card slots will be accessed, and this needs to be done globally. This is a usability issue when using the browser plug-in, since it will systematically ask for the exact same PIN codes,

  1   2   3   4   5   6   7   8   9   10   >