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 
> >> blocked
> >>
> >>If you choose this option, then this bug should be reassigned to
> >>cups-daemon.
>
> > This indeed is the best option.
>
> Thinking about it a bit more, I'm wondering if a less drastic approach
> would be acceptable:
>
> D. Allow cups-pdf to write anywhere under /home/*
>
>This still (somewhat) protects users against security issues in
>cups-pdf. This gets rid of AppArmor denials, as long as the user
>does not customize the "Out" setting to make it point to some place
>that's elsewhere than under ${HOME}.

This was considered a number of times at Ubuntu, back when it adopted
AppArmor.  While allowing anything under ${HOME} makes perfect sense
to me (and would be a good enough compromise between security and
configurability), there's always random people who configure an
unusual output path e.g. /tmp/${USER} or somehow prefer upstream's
default at /var/spool/cups-pdf/${USER}, and who immediately file a bug
report when that doesn't work instead of checking README.Debian for
possible instructions regarding AppArmor. There's also systems where
${HOME} is, for some reason, a path other than /home/${USER}.

At the very least, allowing anything inside /home/${USER} would
probably eliminate the vast majority of bug reports. Let's try it.

Martin-Éric



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 caused by AppArmor
were already common at Ubuntu when it became an early adopter of
AppArmor AND when it chose DPKG build options that don't ship README.
Now that Debian ships AppArmor and CUPS pulls it as a dependency, bugs
about AppArmor-caused issues have started appearing here too.

Martin-Éric



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 case anymore. So I would say first thing
>is to drop the " (UBUNTU)" annotation.
>
>If you choose this option, then this bug should be reassigned back
>to cups-pdf.

It shouldn't. This is an AppArmor issue. AppArmor interferes with
CUPS-PDF configuration.

Martin-Éric



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 prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages printer-driver-cups-pdf depends on:
> ii  cups2.2.10-6
> ii  cups-client 2.2.10-6
> ii  ghostscript 9.27~dfsg-2
> ii  libc6   2.28-10
> ii  libcups22.2.10-6
> ii  libpaper-utils  1.1.28
>
> printer-driver-cups-pdf recommends no packages.
>
> Versions of packages printer-driver-cups-pdf suggests:
> pn  system-config-printer  
>
> -- Configuration Files:
> /etc/cups/cups-pdf.conf changed:
> Out ${HOME}/Transport
> Grp lpadmin
> DecodeHexStrings 1
>
>
> -- no debconf information
>
>
> -- audit error message:
> audit[11578]: AVC apparmor="DENIED" operation="mknod" 
> profile="/usr/lib/cups/backend/cups-pdf" 
> name="/home/rudi/Transport/home_rudi_Transport.pdf" pid=11578 comm="gs" 
> requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
>



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 /usr/sbin/update-mime line 
43.

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (, 'testing')
Architecture: i386 (i586)

Kernel: Linux 5.2.0-2-686 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debianutils depends on:
ii  libc6  2.28-10

debianutils recommends no packages.

debianutils suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAl16Bj8ACgkQrh+Cd8S0
17axrA/+NEzn/4DSbGLA/AmAy0f343tX0FQ4zdZSYynoOtITLeuLmyHzfg/tOjGG
Nh0Q0TBcMfSUy1wqTc38izjW3hkzS3LByIzPOI4i5x+OO4JzGGUS7hM9c6chkhGe
6m87EBPY0aznahhIVMBT605oL5uN2oLEnKRapnd/JY8sjgn0FKD3EIvMrUhj5ksK
TIfast8kUlCWHxI/ihnHCIjbUUTQIEZeXK0F8AUWRo23sIaNRHPfcf7Ee+6Dmw0B
JuNgstl7+0jcEnHVDZ+PRV0vYyTFGRMyDwnZ9emnMTSm3jkHyPO0+Cq8b/FpuVGX
xbIPncQe6fcpS2K5V2uaSKxO1K++PMkazGOjSLRqaEb3MT5ZWx0FnkkefiGADA9n
QGVL2TTYBTa8o9IY014TTSHD6gwMRK6HlB8FrjKQtDdhCQAtCT77UwftHXyxUDsT
YFYmz3quczrHhfgxVVLt9WWBfyKXnJ7QD7bQLvrXMIkjwBE1ccNmBec+kMXTxyVl
HoyWnqVjgwLJuYzxWZGT0JvHoU9Mp1e5f3B8o4bkW2TfG7r0xuMFRHlaJrwiPqmz
1q0Mr3UpYkP/2MHg1YG/tXxV6IkeLkh60OiuyKzpJHjW3Aqeauq052A5TCc1YmdN
VUK7mnbw5TJYmCn4rsvjy9q3HI82GlfvpFJ/mgHXo5cW209J1Z0=
=RKuk
-END PGP SIGNATURE-



Bug#935146: appstream: unable to open cache

2019-09-06 Thread Martin-Éric Racine
appstream (0.12.8-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 = Merged Git patch 84e11c35f9ceb1b92df83e4b9707498f5267dcd3.patch

Upgraded the following packages to the above version:

appstream apt-config-icons libappstream4

Ran the following command line:

sudo apt-get update && sudo apt-get dist-upgrade

No error reported. I guess the patch works. Thanks!

Please note that this host's 1 GB RAM is generous for the Geode
platform. More typically a Geode host comes with 128 MB of soldered-on
RAM. The mmap amount ought to keep this in mind on i386.

Debian's linux-image-686 (the kernel for legacy non-PAE i386 hosts)
happens to be configured for Geode LX platforms (Kconfig:
CONFIG_MGEODE_LX=y).

Cheers!
Martin-Éric

la 31. elok. 2019 klo 20.45 Matthias Klumpp (matth...@tenstral.net) kirjoitti:
>
> Am Sa., 31. Aug. 2019 um 19:36 Uhr schrieb Matthias 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.
> > >
> > > $ free
> > >   totalusedfree  shared  buff/cache   
> > > available
> > > Mem: 896608   56956  6774602968  162192  
> > > 706860
> > > Swap:   1646624   0 1646624
> >
> > So far I haven't been able to reproduce this in VMs, but a VM is
> > probably also not the best place to try to reproduce this issue.
> > Do you have some time to test a patch for me?
> > If you can, fetch
> > https://github.com/ximion/appstream/commit/a049482267f3caf53c5465fe6feb8d7c6a12206b.patch
>
> Actually, that's the wrong patch...
> You'd want this one instead:
> https://github.com/ximion/appstream/commit/84e11c35f9ceb1b92df83e4b9707498f5267dcd3.patch
>
> --
> I welcome VSRE emails. See http://vsre.info/



Bug#935146: appstream: unable to open cache

2019-08-20 Thread 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.

$ free
  totalusedfree  shared  buff/cache   available
Mem: 896608   56956  6774602968  162192  706860
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
> > :
> > >
> > > 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 memory
> >
> > Looks like AppStream is a bit too aggressive with the mmap'ing on 32bit 
> > systems.
> > I'll resolve this with the next upload.
>
> On closer look, only up to 512MB are mapped. How much memory does your
> system have? Is PAE enabled for your CPU?
> This issue is fairly strange, I will try to reproduce it in a VM later.
>
> Cheers,
> Matthias
>
> --
> I welcome VSRE emails. See http://vsre.info/



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 memory

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (, 'testing'), (1101, 'stable')
Architecture: i386 (i586)

Kernel: Linux 4.19.0-5-686 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages appstream depends on:
ii  libappstream4  0.12.8-1
ii  libc6  2.28-10
ii  libglib2.0-0   2.60.6-2

appstream recommends no packages.

Versions of packages appstream suggests:
ii  apt-config-icons  0.12.8-1
ii  curl  7.65.3-1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAl1bn40ACgkQrh+Cd8S0
17YWsBAAjpBB5yM0+e9tZNS/nXu/SG9/RdtGbOIO3SY0I97aJoCFQpkKGrlLdnBG
aOEGZ6VlDBAkbUe4SK0THAOljlVm5cZpVAPIBZSRUAKWOBh1syBe5FUYE97dDkRa
bI/DF3g6pZSVHTUXS7SYd456JuD2z8yS9rzV/yWpTMBx+RrYg2lSZlXks4kchp4f
C3ncfBVSV9WsIv/jFuBgXf+SraMVcsUMRTJ8BB9+207pkau5tijBy1sT6WoDOsbp
MZ7p1Lt5AXd4wv7xXm6wxWUoUVVi0qa297TNV4L40j/58li4UqoQQA5KQLGlxNdr
MSSr6W9BnUbbBJLFITYSUgOqHXM+g6qLsyODXgqS1/Vg4q+g3seP4XHDVrvaCeEX
AYUbq1Q9ZJZ3GkmMaIX2aJTqL0CQJphP7QusGRvxdOAPs7d8sD8cglkyyM2E1IGV
3cymjKK96DKvSvfjFpeDyEdxYGAT1ntAs/XW9NVL2scP5RUVWUqAVDLBLcVDir2f
jh9+QQ1Rfz/LCR6dmcX9KAK071oDaqr3RUVSzQzwIbIKvM5PMHEL4pW9PwqjSOOf
OmRywEM5kg8l9O7qCzqYprG1dksxARHt7qwavuR3X23oZRoHOlKeETjqYlNlqjIS
skCKMmSFFJHQMB5A2OKkoc5E35hG014Y/KxcWFTHMiuMLghucP4=
=C+Et
-END PGP SIGNATURE-



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, #924657 works under the assumption
> > of a changed locale, yet the locale on this host has remained at
> > fi_FI.UTF-8 ever since Debian migrated away from Latin encodings.
>
> No? The contents of the buster binaries are broken, because of the
> locale changes at build time.

Broken locales at build time sounds plausible.

> (Just filed #934826 BTW.)

Thanks!

-- Martin-Éric



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
> > >
> > > -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. In cases where a template has not been fully localised,
> > > text in the locale C would be expected.
> >
> > I which environment did you see this?
> > Did this happen while installing Debian with the debian-installer?
>
> #924657 I suppose?

It seems similar enough.  However, #924657 works under the assumption
of a changed locale, yet the locale on this host has remained at
fi_FI.UTF-8 ever since Debian migrated away from Latin encodings.

Martin-Éric



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. In cases where a template has not been fully localised, text 
in the locale C would be expected.

- -- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.71
ii  liblocale-gettext-perl  1.07-3+b4

keyboard-configuration recommends no packages.

keyboard-configuration suggests no packages.

Versions of packages console-setup depends on:
ii  console-setup-linux  1.191
ii  debconf  1.5.71
ii  xkb-data 2.26-2

Versions of packages console-setup suggests:
ii  locales   2.28-10
ii  lsb-base  10.2019051400

Versions of packages console-setup-linux depends on:
ii  init-system-helpers  1.56+nmu1
ii  initscripts  2.93-8
ii  kbd  2.0.4-4

Versions of packages console-setup-linux suggests:
ii  console-setup  1.191

Versions of packages keyboard-configuration is related to:
pn  console-common
pn  console-data  
pn  console-tools 
ii  gnome-control-center  1:3.30.3-1
ii  kbd   2.0.4-4
ii  systemd   241-5

- -- debconf information:
* keyboard-configuration/compose: No compose key
* keyboard-configuration/toggle: No toggling
  keyboard-configuration/unsupported_config_options: true
* console-setup/store_defaults_in_debconf_db: true
* console-setup/fontsize: 8x16
  console-setup/use_system_font:
* console-setup/fontsize-text47: 8x16
* keyboard-configuration/variantcode:
* keyboard-configuration/model: PC genèric de 105 tecles (intl.)
* console-setup/fontsize-fb47: 8x16
* keyboard-configuration/optionscode: lv3:ralt_switch,terminate:ctrl_alt_bksp
* keyboard-configuration/layout: Fins
* console-setup/charmap47: UTF-8
* console-setup/codeset47: Guess optimal character set
* keyboard-configuration/altgr: Right Alt (AltGr)
* keyboard-configuration/variant: Fins
* keyboard-configuration/xkb-keymap: us
* console-setup/codesetcode: guess
  console-setup/framebuffer_only:
  console-setup/guess_font:
  debian-installer/console-setup-udeb/title:
* keyboard-configuration/layoutcode: fi
* keyboard-configuration/switch: No temporary switch
* keyboard-configuration/modelcode: pc105
  keyboard-configuration/unsupported_options: true
* keyboard-configuration/store_defaults_in_debconf_db: true
* keyboard-configuration/ctrl_alt_bksp: true
* keyboard-configuration/other:
* keyboard-configuration/unsupported_layout: true
* console-setup/fontface47: Let the system select a suitable font
* keyboard-configuration/unsupported_config_layout: false

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAl1S5FcACgkQrh+Cd8S0
17ZLVw//SVppqRDkXjVRZjNCoYCfOUwwCSYUhXHSAp51idQxZrVcFrwBG7XYbDPg
XIcha8RDEmBXvG/JR+9F96rbSjV9uchtfWIxLGw0+EC7o3z9F9VBiFqjeGJVJtzR
RxVDu3+sxgG3qn9igpZLZ7KhHX5IDmPnz6Qj6Xr/tfRho3kVz/+ikd2LLUvyBktV
N+kbKEe1xpjgAfQg//oAnxqMrZSvqwN8I6hXtQ2VyO8VPplhA8ZBJistV/17BNi2
1iWm1bWyuDHoa3v20uuzblxEaox9C3Fb5xGgrLIy0iGGUs4SaXFjThf5oHENGR21
+kiRx8rC0S7zrUxfKCEO6FDV0hrnVdECki0BrphO+9+4odNT/7y+dDaXbXIGT0P3
JX5u7TIqSOZE1K7mP9j5E0vQBIM3UA3INqM1na9zVtqRXdWK2nTPBU5eGnQbiztL
m4xvtCafYvxlcUfnu6U4wkTfunmgBUvttET6y7eB73HTHMnEl8Foq/ax1q+UdnPW
rXHpvHJBbJTP+PNdvWQs8MW7s0e99pWybYfVYCYnLRe7FxtSdho5NX521/2ZpaYh
+VRAO8dNgkiL2Dzx85yovCx0rZc+uH+xW/IhjTZX/n8f2UuESQmzf+BYOEOKCijh
qGG5DaRppnIDSNkgKAiMKUh8+a4C4mLAOzgdSDjBt2XQwQ0OYu8=
=oS+B
-END PGP SIGNATURE-


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 empty page.

- -- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages simple-scan depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.16-1
ii  dbus-x11 [dbus-session-bus]   1.12.16-1
ii  dconf-gsettings-backend [gsettings-backend]   0.30.1-2
ii  libc6 2.28-10
ii  libcairo2 1.16.0-4
ii  libcolord21.4.3-4
ii  libgdk-pixbuf2.0-02.38.1+dfsg-1
ii  libglib2.0-0  2.58.3-2
ii  libgtk-3-03.24.5-1
ii  libgusb2  0.3.0-1
ii  libpackagekit-glib2-181.1.12-5
ii  libsane   1.0.27-3.2
ii  libwebp6  0.6.1-2
ii  libwebpmux3   0.6.1-2
ii  xdg-utils 1.1.3-1
ii  zlib1g1:1.2.11.dfsg-1

simple-scan recommends no packages.

simple-scan suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAl1RVxQACgkQrh+Cd8S0
17a50Q//QjYdwN9r40QBSei+bkm+PBNx64ca6gejl583VVZAIPYqmRPHQHapychL
Q/svuLdy4V5XvttmGE/YQ8+QXLgiNndpclZhi5JexH/YG78CRcmLyqP1jqSGjwk0
bpOjilpiaPq/8+4uZUBnTFUVRLGF5nLkwDRA5VGNbxHFFOedYx1X2ug88fBgK5SO
Qa8PmFwzxzF0eVBpzrRv3X3EAclls9zcrW7qOuQAuzXDFBjuyESskrwZIJCMdC2u
YwlPlYCzgbzWz13bapP0cSLQV0zrNCqQsMoPc402VQHpiI2iwbQdJyKR6BZ1cW3W
g9oJqhvTUAlYs6lKwJGU8t1JoyeLQB8invtjrFnwK3vU8032UJEWgmuXIGvgdZbi
Yjzldd5GkUHqUeWzsWef5oZk0AC0ST9I0YgJZugdCXpCbwEZHRJxhMSZ8hGhbQ80
D6pBrpgvSnoLUB1E72ZFGsEBOXjlw+a/yXH/kmnwjgJn8yuWxg/D0xG9GVja0jYQ
yVRNcM/W4H9V9kxoYPnXLOnRtavudcRBCUh4X1XfHEkr1VuMyQrsWcxvZSarbEdM
ZCFoQKjgFJyA9addFyaHFbGa17MwLIoZk48J4bV1+X5looKdRO3dG5lIhSsRs/WB
z/ESPji78p9HhmMk4KQQF67mXJ/mxuDqX0k1jigcCeyTz8ovy7A=
=BRCz
-END PGP SIGNATURE-
[+0,05s] DEBUG: simple-scan.vala:638: Starting Simple Scan 3.30.1.1, PID=2864
[+0,10s] DEBUG: app-window.vala:1715: Loading state from 
/home/perkelix/.cache/simple-scan/state
[+0,10s] DEBUG: app-window.vala:1672: Restoring window to 600x400 pixels
[+0,10s] DEBUG: app-window.vala:1676: Restoring window to maximized
[+0,10s] DEBUG: autosave-manager.vala:64: Loading autosave information
[+0,10s] DEBUG: autosave-manager.vala:259: Waiting to autosave...
[+0,12s] DEBUG: scanner.vala:1461: sane_init () -> SANE_STATUS_GOOD
[+0,12s] DEBUG: scanner.vala:1467: SANE version 1.0.27
[+0,12s] DEBUG: scanner.vala:1528: Requesting redetection of scan devices
[+0,12s] DEBUG: scanner.vala:806: Processing request
[+0,20s] DEBUG: autosave-manager.vala:281: Autosaving book information
[+0,23s] DEBUG: app-window.vala:1776: Saving state to 
/home/perkelix/.cache/simple-scan/state
[+5,13s] DEBUG: gdk_pixbuf_from_pixdata() called on:
[+5,13s] DEBUG: Encoding raw
[+5,13s] DEBUG: Dimensions: 14 x 14
[+5,13s] DEBUG: Rowstride: 56, Length: 808
[+5,13s] DEBUG: Copy pixels == false
[+5,13s] DEBUG: gdk_pixbuf_from_pixdata() called on:
[+5,13s] DEBUG: Encoding raw
[+5,13s] DEBUG: Dimensions: 14 x 14
[+5,13s] DEBUG: Rowstride: 56, Length: 808
[+5,13s] DEBUG: Copy pixels == false
[+5,14s] DEBUG: gdk_pixbuf_from_pixdata() called on:
[+5,14s] DEBUG: Encoding raw
[+5,14s] DEBUG: Dimensions: 14 x 14
[+5,14s] DEBUG: Rowstride: 56, Length: 808
[+5,14s] DEBUG: Copy pixels == false
[+5,14s] DEBUG: gdk_pixbuf_from_pixdata() called on:
[+5,14s] DEBUG: Encoding raw
[+5,14s] DEBUG: Dimensions: 14 x 14
[+5,14s] DEBUG: Rowstride: 56, Length: 808
[+5,14s] DEBUG: Copy pixels == false
[+6,58s] DEBUG: gdk_pixbuf_from_pixdata() called on:
[+6,58s] DEBUG: Encoding raw
[+6,58s] DEBUG: Dimensions: 14 x 14
[+6,58s] DEBUG: Rowstride: 56, Length: 808
[+6,58s] DEBUG: Copy pixels == false
[+6,72s] DEBUG: gdk_pixbuf_from_pixdata() called on:
[+6,72s] DEBUG: Encoding raw
[+6,72s] DEBUG: Dimensions: 14 x 14
[+6,72s] DEBUG: Rowstride: 56, Length: 808
[+6,72s] DEBUG: Copy pixels == false
[+7,87s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+7,87s] DEBUG: scanner.vala:353: Device: 

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 plugin installed in $HOME.

Module versions:
  pkg-config unavailable


- -- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), 
LANGUAGE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gedit depends on:
ii  gedit-common   3.30.2-2
ii  gir1.2-glib-2.01.58.3-2
ii  gir1.2-gtk-3.0 3.24.5-1
ii  gir1.2-gtksource-3.0   3.24.9-2
ii  gir1.2-pango-1.0   1.42.4-6
ii  gir1.2-peas-1.01.22.0-4
ii  gsettings-desktop-schemas  3.28.1-1
ii  iso-codes  4.2-1
ii  libatk1.0-02.30.0-2
ii  libc6  2.28-10
ii  libcairo-gobject2  1.16.0-4
ii  libcairo2  1.16.0-4
ii  libenchant1c2a 1.6.0-11.1+b1
ii  libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii  libgirepository-1.0-1  1.58.3-2
ii  libglib2.0-0   2.58.3-2
ii  libgspell-1-1  1.6.1-2
ii  libgtk-3-0 3.24.5-1
ii  libgtksourceview-3.0-1 3.24.9-2
ii  libpango-1.0-0 1.42.4-6
ii  libpangocairo-1.0-01.42.4-6
ii  libpeas-1.0-0  1.22.0-4
ii  libx11-6   2:1.6.7-1
ii  libxml22.9.4+dfsg1-7+b3
ii  python33.7.3-1
ii  python3-gi 3.30.4-1
ii  python3-gi-cairo   3.30.4-1
ii  python3.7  3.7.3-2

Versions of packages gedit recommends:
ii  yelp3.31.90-1
ii  zenity  3.30.0-2

Versions of packages gedit suggests:
ii  gedit-plugins  3.30.1-3

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAl0t9OAACgkQrh+Cd8S0
17aB3RAAudBGm0pUNS4XO+RT9PYCGGfYrBM/Msx4L3fE+UTM9+8yrcGGaiuTWJzl
z/YzXt2WZtaJ0IF578QWoVMrDOBvv6Mx08Zfd9X4aUEBQHt0O9scTVrApLs+/0oL
jw3lzFbBv+9rXzHJPysSlxAyqyYyymR6xeb12PfCOsNDBC2ffe9gghDmYojm/wBG
fdp5pYHF+UznzMLfV9hoynU6bmZl153TF4tXzLx9VKCq/IJ5KSSHIurBqRMIXarF
gnJFttDrSq9l6nLGEhNurDbS2e0HiZnGc+9EBVb0u/clBCpFeDJrDdebO3WOrPzj
r4GEbP3b3HuWON7qZ4uGFQv0/EJSKln8AHG2A6daxLwSBO/C87sfWa6SqaWX+G1l
wNLtLozuyfGteqlj4krHj4aZXMR69f6Q0mNUbIcOMsNzdHOYQlgRNrR7wgvXd0QP
86dPMtzW9HYhkDref/0Q+CyqlIVfBlGNZAf3bPFVDvr8u0jLFgi/EDnZwOW4m5Wr
e7Lew26DVfJHSvCjYsJ7WBa9B1y+pNs2JF24cGLRpJ6oNmK+zXLTlf1eC1nf69du
zcLVPTNS64PLcr8Pb6OSoK+yOTWtxW5+eBQH5awIaA8sCXJd5GVTNZOb+hb3xIaA
46ZzsS/2ZC6tBIPa1vRMMdLGlajGrii0CCGLkGDi/USQ0Qs15SA=
=QJUE
-END PGP SIGNATURE-



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 re-selecting it does not fix it.

- -- Package-specific info:
Active plugins:
  - 'spell'
  -  'modelines'
  -  'filebrowser'
  -  'time'
  -  'docinfo'

No plugin installed in $HOME.

Module versions:
  pkg-config unavailable


- -- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), 
LANGUAGE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gedit depends on:
ii  gedit-common   3.30.2-2
ii  gir1.2-glib-2.01.58.3-2
ii  gir1.2-gtk-3.0 3.24.5-1
ii  gir1.2-gtksource-3.0   3.24.9-2
ii  gir1.2-pango-1.0   1.42.4-6
ii  gir1.2-peas-1.01.22.0-4
ii  gsettings-desktop-schemas  3.28.1-1
ii  iso-codes  4.2-1
ii  libatk1.0-02.30.0-2
ii  libc6  2.28-10
ii  libcairo-gobject2  1.16.0-4
ii  libcairo2  1.16.0-4
ii  libenchant1c2a 1.6.0-11.1+b1
ii  libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii  libgirepository-1.0-1  1.58.3-2
ii  libglib2.0-0   2.58.3-2
ii  libgspell-1-1  1.6.1-2
ii  libgtk-3-0 3.24.5-1
ii  libgtksourceview-3.0-1 3.24.9-2
ii  libpango-1.0-0 1.42.4-6
ii  libpangocairo-1.0-01.42.4-6
ii  libpeas-1.0-0  1.22.0-4
ii  libx11-6   2:1.6.7-1
ii  libxml22.9.4+dfsg1-7+b3
ii  python33.7.3-1
ii  python3-gi 3.30.4-1
ii  python3-gi-cairo   3.30.4-1
ii  python3.7  3.7.3-2

Versions of packages gedit recommends:
ii  yelp3.31.90-1
ii  zenity  3.30.0-2

Versions of packages gedit suggests:
ii  gedit-plugins  3.30.1-3

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAl0tz0wACgkQrh+Cd8S0
17bsCg//bm1Dr1wUHGFz7djmULj+Bu3L9aUCZc/7PyraMLataDQFEYKQVhHuF/Pb
EA/7CaoJoH23eF3UdTlZRBnpou9X/ZnZFUUpbOgmFzhBC4WrETpWVEOy+PZHBa8Y
9MoDDXAA4zdxXiPDfB3rfSZJ3YOaOXzEhijp/7gM1hmW1G4swPVEwWcL8w3umMrS
930ovIUEFBOBwk5ow2zbkaycRM+utT0bni97sOcE2nHg4nem6R04ensLvjwFkBQ0
VdprRyozoA9pmY+IzGYWBYwQ11UknRSBQbEmNenI1uWti17UsA52PsYDeIhIy8vI
URz1F5/0JbPvQ3o7tgTZpLuFXPAooxHlbm4fF6RYyRW5U1fqWlV4Z+WK1My5XPeU
1hitdOh94+eGVDtsEu6e1chnocBsng5A3GI3z9w9494/t5uHNy7esJjbLiKC5p2X
jr8FVYU4gcxCCZ7QwrsrMbU4iwZk2Mt2rulhksHKNJVpZEqpVAvJTj+4DEs+tWX2
20O6V+XMHV0Dt8LoYo3ZY+r91KdVyng3qhxkXsdWA+0uuYH9y6P4wn/Vf4fvKu7e
q6KyoCHGe3icV4/yKyxTdk/NpbM8h20CZrK2FYIPnDgyEOgrrwNRlk7T0pw0dusr
pXrbz9eTg5/4YqvLQdX86ZbBeK82LmbY/IqW6AslmQsEdg2pSWw=
=uM4Q
-END PGP SIGNATURE-


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
bridge_fd 0
bridge_ports all

- -- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), 
LANGUAGE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bridge-utils depends on:
ii  libc6  2.28-10

bridge-utils recommends no packages.

Versions of packages bridge-utils suggests:
ii  ifupdown  0.8.35

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAl0sYrkACgkQrh+Cd8S0
17Y6qw/+Jh1xnyw7Jy40GEFlUnmGxELEbdPrNYHPpyhgkUxLt73Cb7SG/TVFQ631
ctQvq1urfdmrFz/gFsbfpMB5+Sch4wr+jQlT4Csvp5euCf/mwuzsvEjvQj/o8tYk
qEHY+1te95D4TUANPesVk1V2TEiXq2p7iQLORc013CpzQa9fB4pj1Hc1gg83ESDS
/5YOZ6QHR9MfQh2GMo+68Zjy9Zb57Y70VKDPgHrwWfvoRQcLU9HcUM7WiTUrCC8V
4aEiFPqzpFIgd6Fa4sAXp+IfKgQLp6HE1iuTQpuyFQNcLNcBCAAFrKDzQ7ELHbCa
P8ZbUvkVt5k3iXWQWxy2QERd1Ct4L9INiABC7BiI0BQu8hdYE93qjitfjkUzh8xX
ncR+AF/q/iXFJ59cvoSJd7CoVxo82FVoCNWMb/t8OXm8BL1wimMXG0MvduS5MaPW
78kPf+BrUI5ki1dmWZ/UTj7UrWAAhBAM8Dxrxtd0xz3GQmUWwqQ3gzfwBV8cvto2
7fc3yYuoC6VBvn/Hhiin3IQual7M6iHeH/NYaiV30aZ/x2D/iliWVmQTCzeqixzy
XaoUJX7nYO/2MnO9GD1RtdRz1jYiGEIto0pq/Sg0zTI1UFGA3PqKhM+SQo3gPzxS
og8pOQ0+R3b5BKNTtw0Eqn+9BLze2K2i7ZZoidC+44by4vPbIps=
=6rX8
-END PGP SIGNATURE-



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

2019-07-06 Thread Martin-Éric Racine
I made further tests on Stretch. My current packages:

$ dpkg -l | grep -e ghostscript -e cups-pdf | awk '{print $2, $3}'
ghostscript 9.26a~dfsg-0+deb9u3
printer-driver-cups-pdf 2.6.1-22

Test 1: print an UTF-8 text file from Gedit.  Works.

Test 2: print an ODF document from LibreOffice. Works.

Test 3: print an HTML document from Firefox-ESR. Works.

This bug thus seems to occur rather randomly.  For the record, I
indeed encountered a "permission denied" error when I tried printing
to PDF the other day, but I no longer remember from which application
I did. I probably pressed 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 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 run from cupsd, the first FD used is 0, whereas it's 3
> > otherwise.
> >
> > Apart from that, I see absolutely no difference in the syscalls
> > until one of the fails to write the output file.
> >
> > Straces attached. Go ahead load them in vimdiff!
>
> Thanks. Let's see if we can figure out what causes this.
>
> Volker: please see the whole thread at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931363
>
> Thanks!
> Martin-Éric



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:
> >
> > This issue is still not resolved in Buster, which is scheduled to become 
> > the new STABLE release tomorrow.
>
> To me the bug history implies that it is not expected to be resolved, ever.
> Do you think otherwise?  If so, what could be added to the bug history to
> make that state of affairs more clear?
>
> Thanks,
>
> Ben



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 the 
wireless dongle is marked as allow-hotplug in /etc/network/interfaces.

- -- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-5-686-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages hostapd depends on:
ii  init-system-helpers  1.56+nmu1
ii  libc62.28-10
ii  libnl-3-200  3.4.0-1
ii  libnl-genl-3-200 3.4.0-1
ii  libnl-route-3-2003.4.0-1
ii  libssl1.11.1.1c-1
ii  lsb-base 10.2019051400

hostapd recommends no packages.

hostapd suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHcEARECADgWIQQ0UNMMeTbhfuC5+Dp5evnrHgy5zQUCXR94gRocbWFydGluLWVy
aWMucmFjaW5lQGlraS5maQAKCRB5evnrHgy5zdvDAJYlg1yH1OsKll0zgBKC1WBL
2kpzAJ0bl2GqXYW7j9hJ9EK9vykewNRppg==
=g5tF
-END PGP SIGNATURE-



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, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-5-686-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages thermald depends on:
ii  libc6 2.28-10
ii  libdbus-1-3   1.12.16-1
ii  libdbus-glib-1-2  0.110-4
ii  libgcc1   1:8.3.0-6
ii  libglib2.0-0  2.58.3-2
ii  libstdc++68.3.0-6
ii  libxml2   2.9.4+dfsg1-7+b3
ii  lsb-base  10.2019051400

thermald recommends no packages.

thermald suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHgEARECADgWIQQ0UNMMeTbhfuC5+Dp5evnrHgy5zQUCXR9umRocbWFydGluLWVy
aWMucmFjaW5lQGlraS5maQAKCRB5evnrHgy5zTiwAJ0Q/HzSmsL7uUbTc+14jhiw
l0FiEQCfTA0DgbnHDM2RwOiVCwWVyeLZ1FY=
=/H8I
-END PGP SIGNATURE-



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 policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-5-686-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libgssapi-krb5-2 depends on:
ii  libc62.28-10
ii  libcom-err2  1.44.5-1
ii  libk5crypto3 1.17-3
ii  libkeyutils1 1.6-6
ii  libkrb5-31.17-3
ii  libkrb5support0  1.17-3

libgssapi-krb5-2 recommends no packages.

Versions of packages libgssapi-krb5-2 suggests:
pn  krb5-doc   
pn  krb5-user  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHgEARECADgWIQQ0UNMMeTbhfuC5+Dp5evnrHgy5zQUCXR9uNxocbWFydGluLWVy
aWMucmFjaW5lQGlraS5maQAKCRB5evnrHgy5zUZvAJ9tZXJmKrK4KS3jprPfmKeu
baCRKgCglMcSNMSjyG+pYsY0oG0NcTfh5kk=
=ftm/
-END PGP SIGNATURE-



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

These should have been removed by maintainer script helpers.

- -- Package-specific info:

*** BEGIN /proc/mounts
/dev/sda1 / ext4 rw,relatime,errors=remount-ro 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/device.map
(hd0)   /dev/disk/by-id/ata-ST320011A_3HT48T7R
*** END /boot/grub/device.map

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1'  
cc540c15-0f8a-4933-88de-5516da7b3414
else
  search --no-floppy --fs-uuid --set=root cc540c15-0f8a-4933-88de-5516da7b3414
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=fi_FI
  insmod gettext
fi
terminal_input at_keyboard
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-cc540c15-0f8a-4933-88de-5516da7b3414' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1'  
cc540c15-0f8a-4933-88de-5516da7b3414
else
  search --no-floppy --fs-uuid --set=root 
cc540c15-0f8a-4933-88de-5516da7b3414
fi
echo'Loading Linux 4.19.0-5-686-pae ...'
linux   /boot/vmlinuz-4.19.0-5-686-pae 
root=UUID=cc540c15-0f8a-4933-88de-5516da7b3414 ro panic=15 panic=15 noquiet 
nosplash
echo'Loading initial ramdisk ...'
initrd  /boot/initrd.img-4.19.0-5-686-pae
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 
'gnulinux-advanced-cc540c15-0f8a-4933-88de-5516da7b3414' {
menuentry 'Debian GNU/Linux, with Linux 4.19.0-5-686-pae' --class 
debian --class gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-4.19.0-5-686-pae-advanced-cc540c15-0f8a-4933-88de-5516da7b3414' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; 
fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root 
--hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 
--hint='hd0,msdos1'  cc540c15-0f8a-4933-88de-5516da7b3414
else
  search --no-floppy --fs-uuid --set=root 

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 Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-5-686-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages deborphan depends on:
ii  libc6  2.28-10

Versions of packages deborphan recommends:
ii  apt   1.8.2
ii  dialog1.3-20190211-1
ii  gettext-base  0.19.8.1-9

deborphan suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHgEARECADgWIQQ0UNMMeTbhfuC5+Dp5evnrHgy5zQUCXR9tARocbWFydGluLWVy
aWMucmFjaW5lQGlraS5maQAKCRB5evnrHgy5zV0dAJ9UtBcGFCkmTRSXam6zf5Q1
Ume/WACfa5oRl9Wb3gaHOhawOib2JQsAVvw=
=5vEq
-END PGP SIGNATURE-



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.

- -- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-5-686-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apt-show-versions depends on:
ii  apt   1.8.2
ii  libapt-pkg-perl   0.1.34+b1
pn  libstorable-perl  
ii  perl  5.28.1-6

apt-show-versions recommends no packages.

apt-show-versions suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHgEARECADgWIQQ0UNMMeTbhfuC5+Dp5evnrHgy5zQUCXR9sPRocbWFydGluLWVy
aWMucmFjaW5lQGlraS5maQAKCRB5evnrHgy5zaixAJ42IekycAXPg19bM2MxUIUn
OqAFrACfTFuIn300UyqGAk4HnoiRgo+DD+I=
=qEpa
-END PGP SIGNATURE-



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: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-9-686-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

firmware-misc-nonfree depends on no packages.

firmware-misc-nonfree recommends no packages.

Versions of packages firmware-misc-nonfree suggests:
it  initramfs-tools  0.133

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHgEARECADgWIQQ0UNMMeTbhfuC5+Dp5evnrHgy5zQUCXR9mmxocbWFydGluLWVy
aWMucmFjaW5lQGlraS5maQAKCRB5evnrHgy5zVwcAJsGKFeD7zDWAAxsLmSfhTGm
lInxkQCfZVCsC7oXA3GqOCrqXL2F70P5ykM=
=yQCp
-END PGP SIGNATURE-



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 run from cupsd, the first FD used is 0, whereas it's 3
> otherwise.
>
> Apart from that, I see absolutely no difference in the syscalls
> until one of the fails to write the output file.
>
> Straces attached. Go ahead load them in vimdiff!

Thanks. Let's see if we can figure out what causes this.

Volker: please see the whole thread at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931363

Thanks!
Martin-Éric



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-end has changed and maintainer
> >scripts make no attempt to upgrade the backend used by any existing
> >PDF queue. If you purge and re-install the package, does file creation
> >still fail?
>
> Yes. I purged and reinstalled, and the problem persists. I even
> removed the printer and reinstalled it. The same problem seems to be
> the case: the gs process is failing to write to the output
> directory, even if the directory is set to 777.

I just tried on my stable host.  This used to work until a few weeks
ago, but it no longer does. CUPS-PDF has not been updated, but
Ghostscript has received security updates twice in recent times. I'm
thus extremely tempted to reassign to Ghostscript.

Martin-Éric



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?
>
> Yes, just like the other host too. These are ancient systems,
> probably pre-sarge ;)

My best guess is that you bumped into a symptom of upgrading from
cups-pdf 2 to cups-pdf 3.  The back-end has changed and maintainer
scripts make no attempt to upgrade the backend used by any existing
PDF queue. If you purge and re-install the package, does file creation
still fail?

Martin-Éric



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
>
> The PDF driver is failing to write the output PDFs. For example, a
> command like
>
>   echo foo | lp -d PDF
>
> yields the following DEBUG output in the log:
>
>   Wed Jul  3 09:40:55 2019  [DEBUG] *** Final Configuration ***
>   Wed Jul  3 09:40:55 2019  [DEBUG] AnonDirName=
> "/var/spool/cups-pdf/ANONYMOUS"
>   Wed Jul  3 09:40:55 2019  [DEBUG] AnonUser   = "nobody"
>   Wed Jul  3 09:40:55 2019  [DEBUG] GhostScript= "/usr/bin/gs"
>   Wed Jul  3 09:40:55 2019  [DEBUG] GSCall = "%s -q
> -dCompatibilityLevel=%s -dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite
> -sOutputFile="%s" -dAutoRotatePages=/PageByPage
> -dAutoFilterColorImages=false -dColorImageFilter=/FlateEncode
> -dPDFSETTINGS=/prepress -c .setpdfwrite -f %s"
>   Wed Jul  3 09:40:55 2019  [DEBUG] Grp= "lpadmin"
>   Wed Jul  3 09:40:55 2019  [DEBUG] GSTmp  = "TMPDIR=/var/tmp"
>   Wed Jul  3 09:40:55 2019  [DEBUG] Log= "/var/log/cups"
>   Wed Jul  3 09:40:55 2019  [DEBUG] PDFVer = "1.4"
>   Wed Jul  3 09:40:55 2019  [DEBUG] PostProcessing = ""
>   Wed Jul  3 09:40:55 2019  [DEBUG] Out= "${HOME}/PDF"
>   Wed Jul  3 09:40:55 2019  [DEBUG] Spool  =
> "/var/spool/cups-pdf/SPOOL"
>   Wed Jul  3 09:40:55 2019  [DEBUG] UserPrefix = ""
>   Wed Jul  3 09:40:55 2019  [DEBUG] RemovePrefix   = ""
>   Wed Jul  3 09:40:55 2019  [DEBUG] OutExtension   = "pdf"
>   Wed Jul  3 09:40:55 2019  [DEBUG] Cut= -1
>   Wed Jul  3 09:40:55 2019  [DEBUG] Truncate   = 256
>   Wed Jul  3 09:40:55 2019  [DEBUG] DirPrefix  = 0
>   Wed Jul  3 09:40:55 2019  [DEBUG] Label  = 0
>   Wed Jul  3 09:40:55 2019  [DEBUG] LogType= 4
>   Wed Jul  3 09:40:55 2019  [DEBUG] LowerCase  = 1
>   Wed Jul  3 09:40:55 2019  [DEBUG] TitlePref  = 1
>   Wed Jul  3 09:40:55 2019  [DEBUG] DecodeHexStrings   = 1
>   Wed Jul  3 09:40:55 2019  [DEBUG] FixNewlines= 0
>   Wed Jul  3 09:40:55 2019  [DEBUG] AllowUnsafeOptions = 0
>   Wed Jul  3 09:40:55 2019  [DEBUG] AnonUMask  = 
>   Wed Jul  3 09:40:55 2019  [DEBUG] UserUMask  = 0077
>   Wed Jul  3 09:40:55 2019  [DEBUG] *** End of Configuration ***
>   Wed Jul  3 09:40:55 2019  [DEBUG] set new gid: lpadmin
>   Wed Jul  3 09:40:55 2019  [DEBUG] initialization finished: v3.0.1
>   Wed Jul  3 09:40:55 2019  [DEBUG] user identified: madduck
>   Wed Jul  3 09:40:55 2019  [DEBUG] output directory name generated:
> /home/ssd/madduck/PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] user information prepared
>   Wed Jul  3 09:40:55 2019  [DEBUG] spoolfile name created:
> /var/spool/cups-pdf/SPOOL/cups2pdf-8702
>   Wed Jul  3 09:40:55 2019  [DEBUG] source stream ready
>   Wed Jul  3 09:40:55 2019  [DEBUG] destination stream ready:
> /var/spool/cups-pdf/SPOOL/cups2pdf-8702
>   Wed Jul  3 09:40:55 2019  [DEBUG] owner set for spoolfile:
> /var/spool/cups-pdf/SPOOL/cups2pdf-8702
>   Wed Jul  3 09:40:55 2019  [DEBUG] using traditional fgets
>   Wed Jul  3 09:40:55 2019  [DEBUG] found beginning of postscript code:
> %!PS-Adobe-3.0
>
>   Wed Jul  3 09:40:55 2019  [DEBUG] now extracting postscript code
>   Wed Jul  3 09:40:55 2019  [DEBUG] found title in ps code: ((stdin))
>   madduck/PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] found end of postscript code: %%EOF
>
>   Wed Jul  3 09:40:55 2019  [DEBUG] all data written to spoolfile:
> /var/spool/cups-pdf/SPOOL/cups2pdf-8702
>   Wed Jul  3 09:40:55 2019  [DEBUG] trying to use commandline title:
>   Wed Jul  3 09:40:55 2019  [DEBUG] checking for hex strings:
>   Wed Jul  3 09:40:55 2019  [DEBUG] not a hex string, has no start marker:
>   Wed Jul  3 09:40:55 2019  [DEBUG] calling alternate_replace_string
>   Wed Jul  3 09:40:55 2019  [DEBUG] removing alternate special characters
> from title:
>   Wed Jul  3 09:40:55 2019  [DEBUG] empty commandline title, using PS
> title: ((stdin))
>   madduck/PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] checking for hex strings: ((stdin))
>   madduck/PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] not a hex string, has no start marker:
> ((stdin))
>   madduck/PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] calling alternate_replace_string
>   Wed Jul  3 09:40:55 2019  [DEBUG] removing alternate special characters
> from title: ((stdin))
>   madduck/PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] removing leading _ from title:
> __stdin___madduck_PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] title successfully retrieved:
> stdin___madduck_PDF
>   Wed Jul  3 09:40:55 2019  [DEBUG] input data read from stdin
>   Wed Jul  3 09:40:55 2019  [DEBUG] output filename created:
> 

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 giving it lightdm:lightdm ownership does 
not fix the issue.

As far as I can tell, the stock configuration doesn't specify which greeter to 
use, and that is what makes lightdm exit.

- -- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (, 'testing'), (1101, 'stable')
Architecture: i386 (i586)

Kernel: Linux 4.19.0-5-686 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lightdm depends on:
ii  adduser3.118
ii  dbus   1.12.16-1
ii  debconf [debconf-2.0]  1.5.71
ii  libaudit1  1:2.8.4-3
ii  libc6  2.28-10
ii  libgcrypt201.8.4-5
ii  libglib2.0-0   2.58.3-2
ii  libpam0g   1.3.1-5
ii  libxcb11.13.1-2
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.6-1
pn  logind | consolekit
ii  lsb-base   10.2019051400

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+19

Versions of packages lightdm suggests:
ii  accountsservice  0.6.45-2
ii  upower   0.99.10-1
ii  xserver-xephyr   2:1.20.4-1

- -- Configuration Files:
/etc/lightdm/lightdm.conf changed:
[LightDM]
[Seat:*]
greeter-session=lightdm-gtk-greeter
[XDMCPServer]
[VNCServer]


- -- debconf information:
* shared/default-x-display-manager: lightdm
  lightdm/daemon_name: /usr/sbin/lightdm

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAl0bOK4ACgkQrh+Cd8S0
17Z1CA//TbNIYze2VEqOcY0iy37oT57Xy+/gYG2nrZtYFI5rAtlQlfyI0HvdPbRj
h0HZkUi0Oclm/SOsRFLUCCt3LWo0Z/+SoLomhPmnHhUCq2/Nmq4ZG62G83eXZHzq
O7BgcWw6XxEaVKunsQIEgtGyKlhQKida+pVAjXoL6dShn5MoxQ0qUqBQ0M412S0w
5CdxXhnjE2/dAE3vw8/Z7z6E5EiS3iwboxbiil5lkvhTsGbLSzsakgABpNuT3l5I
GsHD4JqnYSZuhIP60QliY8aJw/hqb7OM4GKqjVMFtAHFQBQQUJHRW74GHgEct8cq
vndBmF4xH1BJE7Ihf0FjDn2BxNXf4VkvkDdYa7Z0UzuzQrQtZ6UV7rHWfbHw8wAd
4N/19A/JKUiRKo6dFSUYHuSQ2MUA2TNlMvyIkPLMWTQiPTHspXKFHJfObiHUvDgK
hfousXjFiGJWu56kLCzqTmuS5F4qJNz6KtUYO35TamdOwHbI5XL5bdHOSAnkbmjG
Bla4u0R+DEbq15y3SeArl3rWyrrtCJnbW50MqHgLCPFfRzYUVAVC6Efo2yOUhHle
p3jRIehYtp0Q0SSjAly/Ezt28DNZivbWMobR/rBuLB5eDIhRr1tWCFU+4kacPvxb
mYHSiYUqf2wtdEaEdQKWEL363Js9qnYAgTG58ON6Br+s2UFaILg=
=77ik
-END PGP SIGNATURE-



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 .devscripts (correctly set 
to my current key), so this should not happen.

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
DEB_SIGN_KEYID=C89002C77A8BEC6A4E6D7390AE1F8277C4B4D7B6

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (800, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages devscripts depends on:
ii  dpkg-dev  1.19.5
ii  fakeroot  1.23-1
ii  file  1:5.35-4
ii  gnupg 2.2.13-1
ii  gnupg22.2.13-1
ii  gpgv  2.2.13-1
ii  libc6 2.28-8
ii  libfile-homedir-perl  1.004-1
ii  libfile-which-perl1.23-1
ii  libipc-run-perl   20180523.0-1
ii  libmoo-perl   2.003004-2
ii  libwww-perl   6.36-1
ii  patchutils0.3.4-2
ii  perl  5.28.1-4
ii  python3   3.7.2-1
ii  sensible-utils0.0.12
ii  wdiff 1.2.2-2+b1

Versions of packages devscripts recommends:
ii  apt 1.8.0
ii  at  3.1.23-1
ii  curl7.64.0-2
ii  dctrl-tools 2.24-3
pn  debian-keyring  
ii  dput1.0.3
ii  equivs  2.2.0
ii  libdistro-info-perl 0.21
ii  libdpkg-perl1.19.5
ii  libencode-locale-perl   1.05-1
ii  libgit-wrapper-perl 0.048-1
ii  libgitlab-api-v4-perl   0.16-1
ii  liblist-compare-perl0.53-1
ii  liblwp-protocol-https-perl  6.07-2
ii  libsoap-lite-perl   1.27-1
ii  libstring-shellquote-perl   1.04-1
ii  libtry-tiny-perl0.30-1
ii  liburi-perl 1.76-1
ii  licensecheck3.0.31-3
ii  lintian 2.10.0
ii  man-db  2.8.5-2
ii  patch   2.7.6-3
ii  python3-apt 1.8.3
ii  python3-debian  0.1.34
ii  python3-magic   2:0.4.15-2
ii  python3-requests2.21.0-1
ii  python3-unidiff 0.5.4-1
ii  python3-xdg 0.25-5
ii  strace  4.26-0.2
ii  unzip   6.0-22
ii  wget1.20.1-1
ii  xz-utils5.2.4-1

Versions of packages devscripts suggests:
pn  adequate 
pn  autopkgtest  
pn  bls-standalone   
ii  bsd-mailx [mailx]8.1.2-0.20180807cvs-1
ii  build-essential  12.6
pn  check-all-the-things 
pn  cvs-buildpackage 
ii  debhelper12.1.1
pn  devscripts-el
pn  diffoscope   
pn  disorderfs   
pn  dose-extra   
pn  duck 
pn  faketime 
pn  gnuplot  
pn  how-can-i-help   
ii  libauthen-sasl-perl  2.1600-1
pn  libdbd-pg-perl   
pn  libfile-desktopentry-perl
pn  libnet-smtps-perl
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2
pn  libyaml-syck-perl
pn  mozilla-devscripts   
pn  mutt 
ii  openssh-client [ssh-client]  1:7.9p1-9
pn  piuparts 
pn  postgresql-client
ii  quilt0.65-3
pn  ratt 
pn  reprotest
pn  svn-buildpackage 
ii  w3m  0.5.3-37

-- no debconf information



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 (/lib/systemd/system/logrotate.service; static; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Mon 2019-02-11 16:34:08 EET; 5min 
ago
 Docs: man:logrotate(8)
   man:logrotate.conf(5)
  Process: 690 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, 
status=1/FAILURE)
 Main PID: 690 (code=exited, status=1/FAILURE)
Feb 11 16:34:08 geode systemd[1]: Starting Rotate log files...
Feb 11 16:34:08 geode logrotate[690]: error: /etc/logrotate.conf:18 duplicate 
log entry for /var/log/wtmp
Feb 11 16:34:08 geode logrotate[690]: error: /etc/logrotate.conf:25 duplicate 
log entry for /var/log/btmp
Feb 11 16:34:08 geode systemd[1]: logrotate.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 11 16:34:08 geode systemd[1]: logrotate.service: Failed with result 
'exit-code'.
Feb 11 16:34:08 geode systemd[1]: Failed to start Rotate log files.

This would suggest that there is a duplicate entry in the config file. The 
attached file might shed some light on why.

- -- Package-specific info:
Contents of /etc/logrotate.d
total 36
- -rw-r--r-- 1 root root 120 Oct 21  2017 alternatives
- -rw-r--r-- 1 root root 173 Dec 22  2009 apt
- -rw-r--r-- 1 root root 130 Aug 29 01:21 btmp
- -rw-r--r-- 1 root root 112 Oct 21  2017 dpkg
- -rw-r--r-- 1 root root 157 Feb  1  2011 pm-utils
- -rw-r--r-- 1 root root  94 Apr 18  2014 ppp
- -rw-r--r-- 1 root root 501 Jun 25  2017 rsyslog
- -rw-r--r-- 1 root root 235 Dec 11  2016 unattended-upgrades
- -rw-r--r-- 1 root root 145 Feb 19  2018 wtmp


- -- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (, 'testing'), (1101, 'stable'), (1011, 'oldstable')
Architecture: i386 (i586)

Kernel: Linux 4.19.0-2-686 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages logrotate depends on:
ii  libacl1 2.2.52-3+b1
ii  libc6   2.28-6
ii  libpopt01.16-12
ii  libselinux1 2.8-1+b1
ii  systemd-cron [cron-daemon]  1.5.14-2
ii  systemd-sysv240-5

Versions of packages logrotate recommends:
ii  bsd-mailx [mailx]  8.1.2-0.20180807cvs-1

logrotate suggests no packages.

- -- Configuration Files:
/etc/logrotate.conf changed:
daily
rotate 1
create
compress
include /etc/logrotate.d
/var/log/wtmp {
missingok
monthly
create 0664 root utmp
rotate 1
}
/var/log/btmp {
missingok
monthly
create 0660 root utmp
rotate 1
}


- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAlxhiZ4ACgkQrh+Cd8S0
17b7EA/+Ku+8EeSVCvj0S8e6puGfaIOJFuH0TjfRCEzH+KW1x24+DZNvHBJsAyu3
UdecXQ80CAZ2lp1DXBQZI19SEWwkDf+mi+yV6fcOZci6vdVdlfvl38VTzmSRn3FU
2Y6CbA59SX4omc14fMD0HB/Ams4qRmgc64C1BlDbf9mjpxxb+QcaDsE8/w7irLpo
CvplyXUONZmLkoSUjmO7PPk+4k6NIWr2ZqVq7PndBCuktCNBhRRgP6eFZ0JPgbk6
QzZH0H59h3TWg8AEr6CP+dwGNJjrq2aOCUVVzhSvXgXHUi5PjDfJG7bMB/lYTNq1
URRogpNs/CQYNuDKIkmdk83ANtGhCbjjFu6TKAZBUUHtv2H4jZHeS/nDV9CS+N9p
ysHMQOS79dxqIRbV1iYi/ou3mfVF8xe20swhSRxfmno2ZdixRvZ/3vI0S6iX+MMN
56JAk1tzBzpD5vkE5dr2dVhMKcRcz+wNHrKdkLbGzHhOdJZY6rHjYA7cPNPqrra2
KEJ7AxorIh9rdy/LFyLKWBBUXivOYOapqU9Zom5aDl4DA2cwDD6FdiYv+ZIsW4QA
4RLKTeSjzvQ1fsHWeBBbmtQQCFqn6Wc3OJgJvq3fIsdmPNt7ZwoEJJJUnYyef0Gf
050U1OWjmeF/VfWEy2mHQ4pw3BcO49i2RUuSF7aNfMUG1D6IHN4=
=UEU/
-END PGP SIGNATURE-



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 4.9.0-8-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages dpkg-dev depends on:
ii  binutils  2.31.1-7
ii  bzip2 1.0.6-9
ii  libdpkg-perl  1.19.2
ii  make  4.2.1-1.2
ii  patch 2.7.6-3
ii  perl  5.26.2-7+b1
ii  tar   1.30+dfsg-2
ii  xz-utils  5.2.2-1.3

Versions of packages dpkg-dev recommends:
ii  build-essential  12.5
ii  fakeroot 1.23-1
ii  gcc  4:8.2.0-1
ii  gcc-7 [c-compiler]   7.3.0-29
ii  gcc-8 [c-compiler]   8.2.0-8
ii  gnupg2.2.10-3
ii  gnupg2   2.2.10-3
ii  gpgv 2.2.10-3
ii  libalgorithm-merge-perl  0.08-3

Versions of packages dpkg-dev suggests:
pn  debian-keyring  

-- no debconf information



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
README.fi

As to how we got there is an entirely different story.

Martin-Éric



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 - [Cron] "36 */1 * * * clamav [ -x 
/usr/bin/freshclam ] && /usr/bin/freshclam --quiet >/dev/null"
   Loaded: loaded (/etc/cron.d/clamav-freshclam; generated; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Fri 2018-07-20 11:36:01 EEST; 36ms 
ago
 Docs: man:systemd-crontab-generator(8)
  Process: 7928 ExecStart=/bin/sh 
/run/systemd/generator/cron-clamav-freshclam-clamav-0.sh (code=exited, 
status=1/FAILURE)
 Main PID: 7928 (code=exited, status=1/FAILURE)
heinä 20 11:36:01 voima systemd[1]: Starting [Cron] "36 */1 * * * clamav [ -x 
/usr/bin/freshclam ] && /usr/bin/freshclam --quiet >/dev/null"...
heinä 20 11:36:01 voima systemd[1]: cron-clamav-freshclam-clamav-0.service: 
Main process exited, code=exited, status=1/FAILURE
heinä 20 11:36:01 voima systemd[1]: Failed to start [Cron] "36 */1 * * * clamav 
[ -x /usr/bin/freshclam ] && /usr/bin/freshclam --quiet >/dev/null".
heinä 20 11:36:01 voima systemd[1]: cron-clamav-freshclam-clamav-0.service: 
Unit entered failed state.
heinä 20 11:36:01 voima systemd[1]: cron-clamav-freshclam-clamav-0.service: 
Triggering OnFailure= dependencies.
heinä 20 11:36:01 voima systemd[1]: cron-clamav-freshclam-clamav-0.service: 
Failed with result 'exit-code'.

Unless I missed something, this doesn't specify why the script failed. It would 
be desirable to include the exit code in the e-mail sent to the administrator.

What 'freshclam' prints is:

$ sudo freshclam 
Mon Jul 23 13:49:54 2018 -> ClamAV update process started at Mon Jul 23 
13:49:54 2018
Mon Jul 23 13:49:55 2018 -> ^Your ClamAV installation is OUTDATED!
Mon Jul 23 13:49:55 2018 -> ^Local version: 0.100.0 Recommended version: 0.100.1
Mon Jul 23 13:49:55 2018 -> DON'T PANIC! Read 
https://www.clamav.net/documents/upgrading-clamav
Mon Jul 23 13:49:55 2018 -> main.cld is up to date (version: 58, sigs: 4566249, 
f-level: 60, builder: sigmgr)
Mon Jul 23 13:49:55 2018 -> daily.cld is up to date (version: 24775, sigs: 
206, f-level: 63, builder: neo)
Mon Jul 23 13:49:55 2018 -> bytecode.cld is up to date (version: 325, sigs: 90, 
f-level: 63, builder: neo)

Again, unless I missed something, freshclam doesn't have any error code to 
indicate that it succesfully fetched upgrades BUT there is a version mismatch. 
As far as I can tell, it exited with code 0 (update successful) but because it 
also printed that blob of text about the outdated version, systemd considers 
this cron job as failed.

-- Package-specific info:
--- configuration ---
Checking configuration files in /etc/clamav

Config file: clamd.conf
---
BlockMax disabled
PreludeEnable disabled
PreludeAnalyzerName = "ClamAV"
LogFile = "/var/log/clamav/clamav.log"
LogFileUnlock disabled
LogFileMaxSize = "4294967295"
LogTime = "yes"
LogClean disabled
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
LogRotate = "yes"
ExtendedDetectionInfo = "yes"
PidFile disabled
TemporaryDirectory disabled
DatabaseDirectory = "/var/lib/clamav"
OfficialDatabaseOnly disabled
LocalSocket = "/var/run/clamav/clamd.ctl"
LocalSocketGroup = "clamav"
LocalSocketMode = "666"
FixStaleSocket = "yes"
TCPSocket disabled
TCPAddr disabled
MaxConnectionQueueLength = "15"
StreamMaxLength = "26214400"
StreamMinPort = "1024"
StreamMaxPort = "2048"
MaxThreads = "12"
ReadTimeout = "180"
CommandReadTimeout = "5"
SendBufTimeout = "200"
MaxQueue = "100"
IdleTimeout = "30"
ExcludePath disabled
MaxDirectoryRecursion = "15"
FollowDirectorySymlinks disabled
FollowFileSymlinks disabled
CrossFilesystems = "yes"
SelfCheck = "3600"
DisableCache disabled
VirusEvent disabled
ExitOnOOM disabled
AllowAllMatchScan = "yes"
Foreground disabled
Debug disabled
LeaveTemporaryFiles disabled
User = "clamav"
Bytecode = "yes"
BytecodeSecurity = "TrustSigned"
BytecodeTimeout = "6"
BytecodeUnsigned disabled
BytecodeMode = "Auto"
DetectPUA disabled
ExcludePUA disabled
IncludePUA disabled
AlgorithmicDetection = "yes"
ScanPE = "yes"
ScanELF = "yes"
DetectBrokenExecutables disabled
ScanMail = "yes"
ScanPartialMessages disabled
PhishingSignatures = "yes"
PhishingScanURLs = "yes"
PhishingAlwaysBlockCloak disabled
PhishingAlwaysBlockSSLMismatch disabled
PartitionIntersection disabled
HeuristicScanPrecedence disabled
StructuredDataDetection disabled
StructuredMinCreditCardCount = "3"
StructuredMinSSNCount = "3"
StructuredSSNFormatNormal = "yes"
StructuredSSNFormatStripped disabled
ScanHTML = "yes"
ScanOLE2 = "yes"
OLE2BlockMacros disabled
ScanPDF = "yes"
ScanSWF = "yes"
ScanXMLDOCS = "yes"
ScanHWP3 = "yes"
ScanArchive = "yes"
ArchiveBlockEncrypted disabled
ForceToDisk disabled
MaxScanSize = "104857600"
MaxFileSize = "26214400"
MaxRecursion = "16"
MaxFiles = "1"
MaxEmbeddedPE = 

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
Mon Jul 16 18:39:33 2018 -> DON'T PANIC! Read
https://www.clamav.net/documents/upgrading-clamav
Mon Jul 16 18:39:33 2018 -> main.cld is up to date (version: 58, sigs:
4566249, f-level: 60, builder: sigmgr)
Mon Jul 16 18:39:33 2018 -> daily.cld is up to date (version: 24758,
sigs: 2014929, f-level: 63, builder: neo)
Mon Jul 16 18:39:33 2018 -> bytecode.cld is up to date (version: 324,
sigs: 89, f-level: 63, builder: neo)

As you can see, all the data files are up to date, but freshclam
loudly complains that the local version is outdated.

Martin-Éric



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 that is meant for 
0.100.1 releases. It would thus be desiable for this to be pushed into 
stable-updates.

Thanks!

Software settings
-
Version: 0.100.0
Optional features supported: MEMPOOL IPv6 FRESHCLAM_DNS_FIX AUTOIT_EA06 BZIP2 
LIBXML2 PCRE ICONV JSON JIT

Database information

Database directory: /var/lib/clamav
bytecode.cld: version 324, sigs: 89, built on Tue Jul 10 02:36:55 2018
main.cld: version 58, sigs: 4566249, built on Thu Jun  8 00:38:10 2017
daily.cld: version 24757, sigs: 2014720, built on Mon Jul 16 07:56:20 2018
Total number of signatures: 6581058

Platform information

uname: Linux 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) x86_64
OS: linux-gnu, ARCH: x86_64, CPU: x86_64
Full OS version: Debian GNU/Linux 9.5 (stretch)
zlib version: 1.2.8 (1.2.8), compile flags: a9
Triple: x86_64-pc-linux-gnu
CPU: ivybridge, Little-endian
platform id: 0x0a215b5b0806030001060300

Build information
-
GNU C: 6.3.0 20170516 (6.3.0)
GNU C++: 6.3.0 20170516 (6.3.0)
CPPFLAGS: -Wdate-time -D_FORTIFY_SOURCE=2
CFLAGS: -g -O2 -fdebug-prefix-map=/build/clamav-E1AVcn/clamav-0.100.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall 
-D_FILE_OFFSET_BITS=64 -fno-strict-aliasing  -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
CXXFLAGS: -g -O2 -fdebug-prefix-map=/build/clamav-E1AVcn/clamav-0.100.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall 
-D_FILE_OFFSET_BITS=64
LDFLAGS: -Wl,-z,relro -Wl,-z,now -Wl,--as-needed
Configure: '--build=x86_64-linux-gnu' '--prefix=/usr' 
'--includedir=/usr/include' '--mandir=/usr/share/man' 
'--infodir=/usr/share/info' '--sysconfdir=/etc' '--localstatedir=/var' 
'--disable-silent-rules' '--libdir=/usr/lib/x86_64-linux-gnu' 
'--libexecdir=/usr/lib/x86_64-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' 'CFLAGS=-g -O2 
-fdebug-prefix-map=/build/clamav-E1AVcn/clamav-0.100.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall 
-D_FILE_OFFSET_BITS=64' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2' 'CXXFLAGS=-g 
-O2 -fdebug-prefix-map=/build/clamav-E1AVcn/clamav-0.100.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall 
-D_FILE_OFFSET_BITS=64' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed' 
'--with-dbdir=/var/lib/clamav' '--sysconfdir=/etc/clamav' '--disable-clamav' 
'--disable-unrar' '--enable-milter' '--enable-dns-fix' '--with-libjson' 
'--with-system-libmspack' '--with-libcurl=/usr' '--with-gnu-ld' 
'-with-system-llvm
 =/usr/bin/llvm-config' '--with-llvm-linking=dynamic' 
'--with-systemdsystemunitdir=/lib/systemd/system' 'build_alias=x86_64-linux-gnu'
sizeof(void*) = 8
Engine flevel: 91, dconf: 91

--- data dir ---
total 442136
-rw-r--r-- 1 clamav clamav944128 Jul 10 03:31 bytecode.cld
-rw-r--r-- 1 clamav clamav 144288768 Jul 16 08:36 daily.cld
-rw-r--r-- 1 clamav clamav 307499008 Jun  8  2017 main.cld
-rw--- 1 clamav clamav   156 Jul 16 12:36 mirrors.dat

-- System Information:
Debian Release: 9.5
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'stable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-7-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), 
LANGUAGE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages clamav-freshclam depends on:
ii  clamav-base0.100.0+dfsg-0+deb9u2
ii  debconf [debconf-2.0]  1.5.61
ii  dpkg   1.18.25
ii  init-system-helpers1.48
ii  libc6  2.24-11+deb9u3
ii  libclamav7 0.100.0+dfsg-0+deb9u2
ii  libssl1.1  1.1.0f-3+deb9u2
ii  logrotate  3.11.0-0.1
ii  lsb-base   9.20161125
ii  procps 2:3.3.12-3+deb9u1
ii  ucf3.0036
ii  zlib1g 1:1.2.8.dfsg-5

clamav-freshclam recommends no packages.

Versions of packages clamav-freshclam suggests:
pn  apparmor 
pn  clamav-docs  

-- debconf information excluded



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 removal.  I'd
really like to know why.

Martin-Éric

2018-05-26 12:28 GMT+03:00 Emilio Pozuelo Monfort :
> Source: xserver-xorg-video-geode
> Version: 2.11.19-3
> Severity: serious
> Tags: patch
>
> geode fails to build with xserver 1.20. There is a patch available
> upstream but no release at this time:
>
> https://cgit.freedesktop.org/xorg/driver/xf86-video-geode/commit/?id=8382e6bb0c76a8029493eae3f2d7a3dbfd0cfc12
>
> Emilio



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.

Solution: one of python3-pymediainfo or rapid-photo-downloader needs an 
explicit dependency on libmediainfo0v5.

Best Regards,
Martin-Éric


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

2018-04-01 Thread Martin-Éric Racine
This seems to have resolved itself over the past few days.

I have a strong suspicion that a dangling symbolic link in
/etc/alternatives to /etc/ld.so.conf.d/i386-linux-gnu_GL.conf was the
culprit. Doing 'sudo update-alternatives --all' removed it and that
solved a bunch of issues on that particular host.

That systemd would be sensitive to that dangling link however bothers
me. It doesn't bode too well for the distribution's stability, given
how systemd is meant to replace sysvinit and a growing list of other
essential components.

2018-04-02 1:24 GMT+03:00 Michael Biebl <bi...@debian.org>:
> On Wed, 17 Jan 2018 05:20:49 +0200 =?UTF-8?Q?Martin=2D=C3=89ric_Racine?=
> <martin-eric.rac...@iki.fi> wrote:
>> 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>:
>> >> >> 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 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
>> >> >>>> upstream bug report. But let's first wait for your results with 236-1
>> >> >>>
>> >> >>> The issue is not fixed. Something fails at communicating with dbus,
>> >> >>> and it messes up everything else.
>> >> >>
>> >> >> Just to be sure, have you rebooted your system after upgrading to 
>> >> >> 236-1?
>> >> >
>> >> > Yes I have, but this required issuing "exec reboot -f" to bypass init
>> >> > entirely, otherwise it fails due to the lack of dbus connection.
>> >>
>> >> Sure, if PID 1 has crashed, it will freeze itself and no longer respond
>> >> to any (D-Bus) requests.
>> >>
>> >> When exactly does systemd crash? Is it immediately during boot or after
>> >> you've been using the system for a while?
>> >> I assume it works at least for a while, otherwise no other services
>> >> would be started and you would not be able to log in.
>> >> When systemd crashes, you should get an entry in the kernel log (dmesg)
>> >> respectively the journal.
>> >>
>> >> It would be great if you can follow the instructions at [1] to boot with
>> >> debug logging enabled and then provide a journal log which shows such a
>> >> crash.
>> >>
>> >
>> > Any updates on this?
>>
>> Not yet.  I just spent the last month or so giving interviews to the
>> media.  Will get back to this ASAP.
>>
>
> Ping
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>



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>:
>> >> 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 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
>> >>>> upstream bug report. But let's first wait for your results with 236-1
>> >>>
>> >>> The issue is not fixed. Something fails at communicating with dbus,
>> >>> and it messes up everything else.
>> >>
>> >> Just to be sure, have you rebooted your system after upgrading to 236-1?
>> >
>> > Yes I have, but this required issuing "exec reboot -f" to bypass init
>> > entirely, otherwise it fails due to the lack of dbus connection.
>>
>> Sure, if PID 1 has crashed, it will freeze itself and no longer respond
>> to any (D-Bus) requests.
>>
>> When exactly does systemd crash? Is it immediately during boot or after
>> you've been using the system for a while?
>> I assume it works at least for a while, otherwise no other services
>> would be started and you would not be able to log in.
>> When systemd crashes, you should get an entry in the kernel log (dmesg)
>> respectively the journal.
>>
>> It would be great if you can follow the instructions at [1] to boot with
>> debug logging enabled and then provide a journal log which shows such a
>> crash.
>>
>
> Any updates on this?

Not yet.  I just spent the last month or so giving interviews to the
media.  Will get back to this ASAP.

Martin-Éric



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, 'stable-updates'), (500, 'unstable'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages printer-driver-cups-pdf depends on:
> ii  cups2.2.6-4
> ii  cups-client 2.2.6-4
> ii  ghostscript 9.22~dfsg-1
> ii  libc6   2.25-6
> ii  libcups22.2.6-4
> ii  libpaper-utils  1.1.24+nmu5
>
> printer-driver-cups-pdf recommends no packages.
>
> Versions of packages printer-driver-cups-pdf suggests:
> pn  system-config-printer  
>
> -- no debconf information
>
>
> Bug description:
>
> The cups pdf printer produces no pdf output file.
>
> After deleting the pdf printer, the add printer function does not work as 
> expected:
> After selecting "Generic" as printer make, no pdf printer model is selectable.
> I instead selected one of the existing ppd files in /usr/share/ppd/cups-pdf
> but this did not make the pdf printer work.
>
> The bug started by my recent update from cups-pdf, where pdf printing did 
> work,
> to printer-driver-cups-pdf.

I notice that you're using AppArmor.  Please check what the README
says about this.

Martin-Éric



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 using gconf any more.
>
> Debian GNOME Stretch and Ubuntu 17.04+ (at least default Ubuntu
> flavor) did not include gconf by default.
>
> I don't know if we'll be able to completely remove gconf before
> Buster's release, but we are trying to get the number of packages
> using gconf as low as possible.
>
> Thanks,
> Jeremy Bicha



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!
Martin-Éric



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 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
>>> upstream bug report. But let's first wait for your results with 236-1
>>
>> The issue is not fixed. Something fails at communicating with dbus,
>> and it messes up everything else.
>
> Just to be sure, have you rebooted your system after upgrading to 236-1?

Yes I have, but this required issuing "exec reboot -f" to bypass init
entirely, otherwise it fails due to the lack of dbus connection.

Martin-Éric



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
> upstream bug report. But let's first wait for your results with 236-1

The issue is not fixed. Something fails at communicating with dbus,
and it messes up everything else.

Googling up the issue, I found this:

https://answers.launchpad.net/ubuntu/+source/systemd/+question/287454

As to whether this is the exact issue we're seeing, I wouldn't know.

However, there's one interesting problem:  purging all dbus-related
packages (dpkg -P --force-all) fails because dbus's maintainer scripts
call dbus... whose socket cannot be reached for some damn reason.
Thus, my attempt at reainstaling it also fails.

Martin-Éric



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 this is i386, so the backtrace should look like the attached
> .txt file.

Right. I simply could not think of a way to attach gdb to process 1,
and I wouldn't know how to produce an strace from a core dump.
However, systemd-cordump gave me this to work with, which, I figured,
would be a good start.

Am I to assume that the trace you attached was produced using that core dump?

Martin-Éric



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...@debian.org>:
>>> Am 08.12.2017 um 20:27 schrieb Martin-Éric Racine:
>>>> I can reproduce the problem.
>>>>
>>>
>>> After a reboot?
>>
>> Yes.
>
> Please provide a backtrace of the crash (with debug symbols installed)
> and the output of reportbug --template systemd
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>



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
>> Version: 8.31.0-1
>> Severity: important
>>
>> $ 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 (service_start_timeout=25000ms)
>> Failed to reload daemon: Failed to activate service 
>> 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
>> Failed to retrieve unit: Connection timed out
>> Failed to restart rsyslog.service: Connection timed out
>> See system logs and 'systemctl status rsyslog.service' for details.
>> invoke-rc.d: initscript rsyslog, action "restart" failed.
>> Failed to get properties: Connection timed out
>> dpkg: error processing package rsyslog (--configure):
>>  installed rsyslog package post-installation script subprocess returned 
>> error exit status 1
>> Errors were encountered while processing:
>>  rsyslog
>>
>> $ sudo LC_ALL=C systemctl status rsyslog.service
>
> This has nothing to do with rsyslog but means, that most likely systemd
> (PID 1) has crashed.
>
> If you can (reliably) reproduce the problem, please file a bug against
> systemd.
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>



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 (service_start_timeout=25000ms)
Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': 
timed out (service_start_timeout=25000ms)
Failed to retrieve unit: Connection timed out
Failed to restart rsyslog.service: Connection timed out
See system logs and 'systemctl status rsyslog.service' for details.
invoke-rc.d: initscript rsyslog, action "restart" failed.
Failed to get properties: Connection timed out
dpkg: error processing package rsyslog (--configure):
 installed rsyslog package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 rsyslog

$ sudo LC_ALL=C systemctl status rsyslog.service
Failed to get properties: Connection timed out

Dec  8 18:55:47 geode rsyslogd: action '*' treated as ':omusrmsg:*' - please 
use ':omusrmsg:*' syntax instead, '*' will not be supported in the future 
[v8.31.0 try http://www.rsyslog.com/e/2184 ]
Dec  8 18:55:47 geode rsyslogd: error during parsing file 
/etc/rsyslog.d/50-default.conf, on or before line 46: warnings occured in file 
'/etc/rsyslog.d/50-default.conf' around line 46 [v8.31.0 try 
http://www.rsyslog.com/e/2207 ]
Dec  8 18:55:47 geode rsyslogd:  [origin software="rsyslogd" swVersion="8.31.0" 
x-pid="368" x-info="http://www.rsyslog.com;] start
Dec  8 18:55:47 geode rsyslogd: action '*' treated as ':omusrmsg:*' - please 
use ':omusrmsg:*' syntax instead, '*' will not be supported in the future 
[v8.31.0 try http://www.rsyslog.com/e/2184 ]
Dec  8 18:55:47 geode rsyslogd: error during parsing file 
/etc/rsyslog.d/50-default.conf, on or before line 46: warnings occured in file 
'/etc/rsyslog.d/50-default.conf' around line 46 [v8.31.0 try 
http://www.rsyslog.com/e/2207 ]
Dec  8 18:55:47 geode rsyslogd:  [origin software="rsyslogd" swVersion="8.31.0" 
x-pid="368" x-info="http://www.rsyslog.com;] start
Dec  8 18:55:47 geode rsyslogd: Could not open output pipe '/dev/xconsole':: No 
such file or directory [v8.31.0 try http://www.rsyslog.com/e/2039 ]
Dec  8 18:55:47 geode rsyslogd: action 'action 9' suspended (module 
'builtin:ompipe'), retry 0. There should be messages before this one giving the 
reason for suspension. [v8.31.0 try http://www.rsyslog.com/e/2007 ]
Dec  8 18:55:47 geode rsyslogd: action 'action 9' suspended (module 
'builtin:ompipe'), next retry is Fri Dec  8 18:56:17 2017, retry nbr 0. There 
should be messages before this one giving the reason for suspension. [v8.31.0 
try http://www.rsyslog.com/e/2007 ]
Dec  8 18:55:47 geode rsyslogd: Could not open output pipe '/dev/xconsole':: No 
such file or directory [v8.31.0 try http://www.rsyslog.com/e/2039 ]
Dec  8 18:55:47 geode rsyslogd: action 'action 9' suspended (module 
'builtin:ompipe'), retry 0. There should be messages before this one giving the 
reason for suspension. [v8.31.0 try http://www.rsyslog.com/e/2007 ]
Dec  8 18:55:47 geode rsyslogd: action 'action 9' suspended (module 
'builtin:ompipe'), next retry is Fri Dec  8 18:56:17 2017, retry nbr 0. There 
should be messages before this one giving the reason for suspension. [v8.31.0 
try http://www.rsyslog.com/e/2007 ]

Please see also ( 
https://q-funk.blogspot.fi/2017/12/dbus-rsyslogd-systemd-which-one-is.html )

Thanks!
Martin-Éric

- -- System Information: Debian Release: buster/sid
  APT prefers testing
  APT policy: (, 'testing'), (1101, 'stable'), (1011, 'oldstable'), (1001, 
'oldoldstable'), (500, 'testing-debug')
Architecture: i386 (i586)

Kernel: Linux 4.13.0-1-686 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages rsyslog depends on:
ii  init-system-helpers  1.51
ii  libc62.25-3
ii  libestr0 0.1.10-2.1
ii  libfastjson4 0.99.7-1
ii  liblogging-stdlog0   1.0.6-1
ii  liblognorm5  2.0.3-1
ii  libsystemd0  235-3
ii  libuuid1 2.30.2-0.1
ii  lsb-base 9.20170808
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages rsyslog recommends:
ii  logrotate  3.11.0-0.1

Versions of packages rsyslog suggests:
pn  rsyslog-doc
pn  rsyslog-gnutls 
pn  rsyslog-gssapi 
pn  rsyslog-mongodb
pn  rsyslog-mysql | rsyslog-pgsql  
pn  rsyslog-relp   

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAloq1ZMACgkQrh+Cd8S0
17bmDhAAtMNCKxTK8jVeQKqFUO8TeVROqfoyrcPVDQt6YGs3/133ygAqiJnNHLlq
dD4oH++yGBbVY67Jd2NpdKEiXyd3/aQLbyQCpZNo2GDhT4UAr537wA1G2PADbjea
nW3Tjp7hgJx60d+y21HMtO20zN1jA7r8FsiYT3mWWmSNp7lKeIO/XaST0+3g4Pzn

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 these should not happen:

$ sudo apt-get --option Debug::pkgDepCache::AutoInstall=true --fix-policy 
install
Reading package lists... Done
Building dependency tree   
Reading state information... Done
  Installing python-cryptography as Recommends of python-urllib3
Installing python-cffi-backend as Depends of python-cryptography
Installing python-enum34 as Depends of python-cryptography
Installing python-pyasn1 as Depends of python-cryptography
  Installing python-openssl as Recommends of python-urllib3
The following additional packages will be installed:
  python-cffi-backend python-cryptography python-enum34 python-openssl 
python-pyasn1
Suggested packages:
  python-cryptography-doc python-cryptography-vectors python-enum34-doc 
python-openssl-doc python-openssl-dbg doc-base
The following NEW packages will be installed:
  python-cffi-backend python-cryptography python-enum34 python-openssl 
python-pyasn1
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 393 kB of archives.
After this operation, 2337 kB of additional disk space will be used.
Do you want to continue? [Y/n] 

The above affects Stretch as well as testing/unstable.

- -- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (, 'testing'), (1001, 'oldstable'), (500, 'testing-debug')
Architecture: i386 (i586)

Kernel: Linux 4.9.0-3-686 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages deborphan depends on:
ii  libc6  2.24-12

Versions of packages deborphan recommends:
ii  apt   1.4.6
ii  dialog1.3-20160828-2
ii  gettext-base  0.19.8.1-2

deborphan suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAllPy58ACgkQrh+Cd8S0
17bgFBAAnhA0lOaGzedHexO7RP6JwQnjQW9G0UXMGKq1VoPiCimvwN86puBxtf/V
bAEUzC93Iqw6MgVNhq7uah+HKqLKnmjtViSp25opZgm5ZTFG0XedWXN0AZjHzXEY
mJ8yQwF+U0l7R8DUI9AsgJi4yN3XN6zZU70PGg83fJ510kTT+p6hk7wcUvHliiV/
Aq+iXlmqzWpL+aSqF8xc31vje2m1vt2QFHgtDKYbP7R7AigfXTbmM18RKV5QJCz0
ajMeq0pFc7oeHPkZ9EDzmeJbWBkGzda5oOskwDF0zmgdUSgl4CE47FRM3/45KGQT
wg3VZrXdk+uTMlAOtJcGKr7IJRPm3ze0GEC9KCcNSESL9W4zFswGnPShPczGmq0g
XuYx4ZTrM7mU+ii7g3j2ydLkQtR+Lut6cyJYI4KkachiCJSINoZ4TPfmvauIdlx1
/YCdC/g/RHhUqnSUC8yyLDkMxADcn/dhqunB2kAPkBbM02GZS7XhkguhedSSmyXU
w+2oxJi1bORsoXWXjVgrw5aDSyaYoqwKBBI0NN+f6bAwAtFqgfz4986IQWACiWun
7YHSP+OcExLQ1WBLuYPYKVTsHwk6IdFqva2Ij673jU/kKZwi+ePnjIQi9HzCUD/y
JV5f0nJZGCBVTpnpat/8Bis0kCwYMPGc+2SLJOQTpibFwwawJIs=
=KkjN
-END PGP SIGNATURE-



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. Ullrich :
> Package: printer-driver-cups-pdf
> Version: 3.0.1-4
> Severity: normal
>
> Dear Maintainer,
>
> I am running debian/testing, and so I cannot upgrade to 
> printer-driver-cups-pdf, which is a successor to the package cups-pdf.
>
> The problem is, that printer-driver-cups-pdf inhibits to upgrade, as the 
> installer got a dependency problem with the installed cups-pdf.
>
> Workaround is, just to uninstall and purge cups-pdf, then install 
> printer-driver-cups-pdf.
> However, the debian package should know the dependencies and uninstall 
> cups-pdf automatically, then of course, install printer-driver-cups-pdf.
>
> I believe, you might want to inform the package team.
>
> Thank you for reading this.
>
> Best regards
>
> Hans
>
>
> -- System Information:
> Debian Release: 9.0
>   APT prefers testing
>   APT policy: (500, 'testing'), (500, 'stable')
> Architecture: i386 (i686)
>
> Kernel: Linux 4.9.0-3-686-pae (SMP w/2 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages printer-driver-cups-pdf depends on:
> ii  cups2.2.3-2
> ii  cups-client 2.2.3-2
> ii  ghostscript 9.20~dfsg-3.2
> ii  libc6   2.24-12
> ii  libcups22.2.3-2
> ii  libpaper-utils  1.1.24+nmu5
>
> printer-driver-cups-pdf recommends no packages.
>
> Versions of packages printer-driver-cups-pdf suggests:
> ii  system-config-printer  1.5.7-3
>
> -- no debconf information
>



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 injury, /etc/default/grub does not offer any means of 
overriding this.

IMHO, the best solution would be to stop enforcing any default color scheme 
whatsoever.

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), 
LANGUAGE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages grub-pc depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  dpkg   1.18.24
ii  grub-common2.02~beta3-5
ii  grub-pc-bin2.02~beta3-5
ii  grub2-common   2.02~beta3-5
ii  ucf3.0036

grub-pc recommends no packages.

grub-pc suggests no packages.

-- debconf information excluded



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 (--purge):
 dependency problems - not removing

$ dpkg -l | grep transitional 
pi  libpango1.0-0:amd64   1.40.5-1  
amd64Layout and rendering of internationalized text (transitional 
package)

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), 
LANGUAGE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libexif-gtk5 depends on:
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-11
ii  libcairo2   1.14.8-1
ii  libexif12   0.6.21-2+b2
ii  libfontconfig1  2.11.0-6.7+b1
ii  libfreetype62.6.3-3.2
ii  libgdk-pixbuf2.0-0  2.36.5-2
ii  libglib2.0-02.50.3-2
ii  libgtk2.0-0 2.24.31-2
pn  libpango1.0-0   

libexif-gtk5 recommends no packages.

libexif-gtk5 suggests no packages.

-- no debconf information



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 (--purge):
 dependency problems - not removing

$ dpkg -l | grep transitional 
pi  python-gobject3.22.0-2  all 
 Python 2.x bindings for GObject - transitional package

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), 
LANGUAGE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python-poppler depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  libpoppler-glib8 0.48.0-2
ii  python   2.7.13-2
ii  python-cairo 1.8.8-2.2
pn  python-gobject   
ii  python-gtk2  2.24.0-5.1

python-poppler recommends no packages.

python-poppler suggests no packages.

-- no debconf information



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 that 
credentials have expired again.

Result: the calendar app in the gnome-shell panel no longer shows my Google 
calendar, while Evolution cannot access GMail (but shows my Google calendar 
just fine).

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), 
LANGUAGE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-online-accounts depends on:
ii  libc6 2.24-11
ii  libgcr-base-3-1   3.20.0-5.1
ii  libglib2.0-0  2.50.3-2
ii  libgoa-1.0-0b 3.22.5-1
ii  libgoa-backend-1.0-1  3.22.5-1
ii  libkrb5-3 1.15-1
ii  librest-0.7-0 0.8.0-2
ii  libsoup2.4-1  2.56.0-2
ii  libwebkit2gtk-4.0-37  2.16.3-2

Versions of packages gnome-online-accounts recommends:
ii  dleyna-server 0.4.0-1.1
ii  gnome-control-center  1:3.22.2-3
ii  realmd0.16.3-1

gnome-online-accounts suggests no packages.

-- no debconf information



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 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
>> filename would need to start with a number e.g. 001_fix_for_foo.patch,
>> 002_fix_for_bar.patch and the patches would probably need to be
>> refreshed anyhow.
>>
>> Basically, unless someone is willing to overhaul Phatch's packaging
>> ASAP, it's quite likely to get removed from the Debian archive before
>> the Release.
>
> This bug is already fixed, and the upload is already unblocked and due to 
> enter
> testing in 5 days afaics. Am I missing something?
>
> Cheers,
> Emilio



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
filename would need to start with a number e.g. 001_fix_for_foo.patch,
002_fix_for_bar.patch and the patches would probably need to be
refreshed anyhow.

Basically, unless someone is willing to overhaul Phatch's packaging
ASAP, it's quite likely to get removed from the Debian archive before
the Release.

Best Regards,
Martin-Éric



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
iface lo inet loopback
auto br0
iface br0 inet dhcp
bridge_ports all
allow-hotplug eth0
iface eth0 inet manual
allow-hotplug eth1
iface eth1 inet manual

If there is a way to ensure that the brdige always connects to the outside 
world via eth0, I seem to have missed it.

Can you help?

-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bridge-utils depends on:
ii  libc6  2.19-18+deb8u7

bridge-utils recommends no packages.

Versions of packages bridge-utils suggests:
ii  ifupdown  0.7.53.1

-- no debconf information



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 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 (around version 2.5.1
>> IIRC) that bypassed the pdf2pdf filter.  It worked well for simply
>> passing documents that were already in PDF format over to CUPS for
>> output to a PDF spool.  However, it completely broke CUPS-PDF's
>> primary functionality which is to convert arbitrary document formats
>> into PDF, and it also prevented users from further manipulating the
>> documents via CUPS-PDF's configuration file options before outputting
>> them to the PDF spool. This resulted in complaints from users who
>> depended upon these features, so I removed the patch.
>
> The fullest discussion of this I know of is at
>
>   https://bugs.launchpad.net/ubuntu/+source/cups-pdf/+bug/820820
>
> Users should take note of the comment:
>
>   > The reasons for not skipping this step are known to you
>   > (it will severly impede the functionality of CUPS-PDF).
>   > Furthermore, once again, CUPS-PDF is not meant for
>   > processing PDF-input (i.e., it is not meant to be a
>   > PDF-manipulation tool).
>
> However, cups-pdf is still seen as a general "convert something to a
> PDF" utility. At one time it might have served that purpose, but not
> now. Both text and PDF input produce a below-standard, non-searchable
> output. There is a case for clarifying its purpose as a cups-filters
> plus backend method for getting a decent quality, searchable PDF from
> PostScript input only. (Okular produces PostScript; Evince doesn't).

As far as I can tell, the reason why the quality of the output has
varied over time is because the quality of Ghostscript itself has
varied a lot.

There might be better filters than Ghostscript we could call to handle
the generic document conversion step. However, that's entirely
upstream's decision.

Martin-Éric



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 (around version 2.5.1
IIRC) that bypassed the pdf2pdf filter.  It worked well for simply
passing documents that were already in PDF format over to CUPS for
output to a PDF spool.  However, it completely broke CUPS-PDF's
primary functionality which is to convert arbitrary document formats
into PDF, and it also prevented users from further manipulating the
documents via CUPS-PDF's configuration file options before outputting
them to the PDF spool. This resulted in complaints from users who
depended upon these features, so I removed the patch.

Martin-Éric



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.
>>
>> On src:cups-pdf Lintian reports debian-watch-may-check-gpg-signature
>> yet upstream does not publish any GPG signature. However, upstream
>> does publish foo.tar.gz.md5 checksums.
>
> lintian has no knowledge, nor has any way to know that a given upstream
> publish gpg signatures…

On what basis does it report the error then?

> the problem is that your watch file does not check for a gpg signature,
> exactly as the tag says.  And as the tag description says:

It does not check for it because upstream does not provide any.

> N:   If upstream distributions provide such signatures, please use the
> N:   pgpsigurlmangle options in this watch file's opts= to generate the URL
> N:   of an upstream GPG signature. This signature is automatically
> N:   downloaded and verified against a keyring stored in
> N:   debian/upstream/signing-key.asc.
>
>
> (instead of pgpsigurlmangle you can use pgpmode=auto if uscan is clever
> enough for this case)
>
>
> does this solve your issue?

No, it does not. Adding a pgpurlmangle option won't magically make
upstream produce GPG signatures.

Martin-Éric



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 
foo.tar.gz.md5 checksums. 

By the looks of it, debian-watch-may-check-gpg-signature checks for the 
presence of foo.tar.gz.* and reports a positive regardless of whether * indeed 
is a GPG signature or not.

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (800, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages lintian depends on:
ii  binutils  2.27.90.20170221-1
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1
ii  file  1:5.29-3
ii  gettext   0.19.8.1-2
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.30
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b1
ii  libdpkg-perl  1.18.22
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.416-1+b1
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-1
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libyaml-libyaml-perl  0.63-2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.24.1-1
ii  t1utils   1.39-2
ii  xz-utils  5.2.2-1.2

Versions of packages lintian recommends:
ii  dpkg 1.18.22
ii  libperlio-gzip-perl  0.19-1+b2
ii  perl 5.24.1-1
ii  perl-modules-5.24 [libautodie-perl]  5.24.1-1

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.22
ii  libhtml-parser-perl3.72-3
pn  libtext-template-perl  

-- no debconf information



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 fail at finding the terminal and
>> asking dpkg to run in colorized mode.
>
> debuild isn't failing at that.  It's attaching file descriptors to
> dpkg-buildpackage's stdout/stderr to be able to tee dpkg-buildpackage's
> output into the build log.  Therefore, dpkg-buildpackage doesn't detect
> that it's being run in a terminal.

We obviously don't want VT color escape codes in the log, so we have
to sacrifice visual feedback in the process.  Oh well...

Could this be better documented, perhaps in debuild's man page?

Cheers!
Martin-Éric



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 mode.

-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
DEBSIGN_KEYID=C4B4D7B6
DEBUILD_DPKG_BUILDPACKAGE_OPTS=

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (800, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages devscripts depends on:
ii  dpkg-dev 1.18.22
ii  libc62.24-9
ii  perl 5.24.1-1
pn  python3:any  

Versions of packages devscripts recommends:
ii  apt 1.4~rc2
ii  at  3.1.20-3
ii  curl7.52.1-3
ii  dctrl-tools 2.24-2
pn  debian-keyring  
ii  dput0.12.0
ii  equivs  2.0.9+nmu1
ii  fakeroot1.21-3.1
ii  file1:5.29-3
ii  gnupg   2.1.18-6
ii  gnupg2  2.1.18-6
ii  libdistro-info-perl 0.14
ii  libdpkg-perl1.18.22
ii  libencode-locale-perl   1.05-1
ii  libgit-wrapper-perl 0.047-1
ii  liblist-compare-perl0.53-1
ii  liblwp-protocol-https-perl  6.06-2
ii  libsoap-lite-perl   1.20-1
ii  liburi-perl 1.71-1
ii  libwww-perl 6.15-1
ii  licensecheck3.0.29-1
ii  lintian 2.5.50.1
ii  man-db  2.7.6.1-2
ii  patch   2.7.5-1
ii  patchutils  0.3.4-2
ii  python3-debian  0.1.30
ii  python3-magic   1:5.29-3
ii  sensible-utils  0.0.9
ii  strace  4.15-2
ii  unzip   6.0-21
ii  wdiff   1.2.2-2
ii  xz-utils5.2.2-1.2

Versions of packages devscripts suggests:
pn  adequate 
pn  autopkgtest  
pn  bls-standalone   
pn  bsd-mailx | mailx
ii  build-essential  12.3
pn  check-all-the-things 
pn  cvs-buildpackage 
pn  devscripts-el
pn  diffoscope   
pn  disorderfs   
pn  dose-extra   
pn  duck 
pn  faketime 
pn  gnuplot  
ii  gpgv 2.1.18-6
pn  how-can-i-help   
ii  libauthen-sasl-perl  2.1600-1
pn  libfile-desktopentry-perl
pn  libnet-smtps-perl
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2
pn  libyaml-syck-perl
pn  mozilla-devscripts   
pn  mutt 
ii  openssh-client [ssh-client]  1:7.4p1-6
pn  piuparts 
pn  ratt 
pn  reprotest
pn  svn-buildpackage 
pn  w3m  

-- no debconf information



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:
** Version:
Linux version 4.9.0-1-686-pae (debian-ker...@lists.debian.org) (gcc version 
6.3.0 20170124 (Debian 6.3.0-5) ) #1 SMP Debian 4.9.6-3 (2017-01-28)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-1-686-pae 
root=UUID=24bd6387-2e4e-4eb3-96dd-69817428d656 ro panic=15 video=TV-1:d 
video=SVIDEO-1:d video=LVDS-1:d video=SDVOB:d noquiet nosplash

** Tainted: W (512)
 * Taint on warning.

** Kernel log:

** Model information
[   25.235515] [ cut here ]
[   25.235673] WARNING: CPU: 0 PID: 46 at 
/build/linux-_rPTS4/linux-4.9.6/drivers/gpu/drm/i915/intel_fbdev.c:414 
intel_fb_initial_config+0x3fc/0x5f0 [i915]
[   25.235700] WARN_ON(!connector->state->crtc)
[   25.235707] Modules linked in:
[   25.235720]  bridge stp llc iTCO_wdt iTCO_vendor_support coretemp dell_rbtn 
pcmcia kvm_intel dell_wmi kvm sparse_keymap ppdev dell_laptop dell_smbios 
irqbypass dcdbas dell_smm_hwmon arc4 joydev serio_raw zd1211rw iwl4965 
yenta_socket i915 iwlegacy pcmcia_rsrc mac80211 pcmcia_core evdev lpc_ich sg 
cfg80211 mfd_core rng_core rfkill snd_hda_codec_hdmi snd_hda_codec_idt 
snd_hda_codec_generic wmi snd_hda_intel snd_hda_codec drm_kms_helper parport_pc 
snd_hda_core snd_hwdep parport snd_pcm drm ac i2c_algo_bit shpchp snd_timer 
video snd button battery soundcore acpi_cpufreq tpm_tis tpm_tis_core tpm 
ip_tables x_tables autofs4 sr_mod cdrom hid_generic usbhid hid ext4 crc16 jbd2 
fscrypto mbcache uas usb_storage sd_mod ata_generic psmouse uhci_hcd ehci_pci 
ehci_hcd tg3 sdhci_pci i2c_i801 i2c_smbus ptp ata_piix
[   25.235974]  libata sdhci firewire_ohci scsi_mod usbcore pps_core 
firewire_core mmc_core libphy crc_itu_t usb_common thermal
[   25.236057] CPU: 0 PID: 46 Comm: kworker/u4:1 Not tainted 4.9.0-1-686-pae #1 
Debian 4.9.6-3
[   25.236079] Hardware name: Dell Inc. Latitude D430   
/07, BIOS A01 06/20/2007
[   25.236108] Workqueue: events_unbound async_run_entry_fn
[   25.236123]  f77b5d44 dd2f1922 f77b5d58  dd066aca f916d9b1 f77b5d78 
002e
[   25.236155]  f9160f90 019e f91113cc 019e 0009 f91113cc 0001 
f6982400
[   25.236186]  0001 f77b5d64 dd066b36 0009  f77b5d58 f916d9b1 
f77b5d78
[   25.236217] Call Trace:
[   25.236236]  [] ? dump_stack+0x55/0x73
[   25.236254]  [] ? __warn+0xea/0x110
[   25.236382]  [] ? intel_fb_initial_config+0x3fc/0x5f0 [i915]
[   25.236508]  [] ? intel_fb_initial_config+0x3fc/0x5f0 [i915]
[   25.236527]  [] ? warn_slowpath_fmt+0x46/0x60
[   25.236652]  [] ? intel_fb_initial_config+0x3fc/0x5f0 [i915]
[   25.236671]  [] ? __kmalloc+0xc0/0x4f0
[   25.236796]  [] ? intelfb_create+0x4d0/0x4d0 [i915]
[   25.236821]  [] ? drm_setup_crtcs+0x1a3/0x940 [drm_kms_helper]
[   25.236860]  [] ? 
drm_mode_connector_update_edid_property+0x4a/0x70 [drm]
[   25.236891]  [] ? 
drm_helper_probe_single_connector_modes+0x1a9/0x500 [drm_kms_helper]
[   25.236922]  [] ? drm_fb_helper_initial_config+0xbc/0x410 
[drm_kms_helper]
[   25.236948]  [] ? pick_next_task_fair+0x490/0x520
[   25.237073]  [] ? intel_fbdev_initial_config+0x16/0x30 [i915]
[   25.237091]  [] ? async_run_entry_fn+0x35/0x170
[   25.237110]  [] ? process_one_work+0x144/0x390
[   25.237127]  [] ? worker_thread+0x41/0x460
[   25.237144]  [] ? process_one_work+0x390/0x390
[   25.237160]  [] ? kthread+0xa7/0xc0
[   25.237176]  [] ? kthread_park+0x50/0x50
[   25.237194]  [] ? ret_from_fork+0x1b/0x28
[   25.237210] ---[ end trace 22f94b8ab7756687 ]---
[   25.254113] fbcon: inteldrmfb (fb0) is primary device
[   25.255447] [ cut here ]
[   25.255463] WARNING: CPU: 0 PID: 46 at 
/build/linux-_rPTS4/linux-4.9.6/drivers/gpu/drm/drm_atomic_helper.c:783 
drm_atomic_helper_update_legacy_modeset_state+0x22a/0x260 [drm_kms_helper]
[   25.255533] Modules linked in: bridge stp llc iTCO_wdt iTCO_vendor_support 
coretemp dell_rbtn pcmcia kvm_intel dell_wmi kvm sparse_keymap ppdev 
dell_laptop dell_smbios irqbypass dcdbas dell_smm_hwmon arc4 joydev serio_raw 
zd1211rw iwl4965 yenta_socket i915 iwlegacy pcmcia_rsrc mac80211 pcmcia_core 
evdev lpc_ich sg cfg80211 mfd_core rng_core rfkill snd_hda_codec_hdmi 
snd_hda_codec_idt snd_hda_codec_generic wmi snd_hda_intel snd_hda_codec 
drm_kms_helper parport_pc snd_hda_core snd_hwdep parport snd_pcm drm ac 
i2c_algo_bit shpchp snd_timer video snd button battery soundcore acpi_cpufreq 
tpm_tis tpm_tis_core tpm ip_tables x_tables autofs4 sr_mod cdrom hid_generic 
usbhid hid ext4 crc16 jbd2 fscrypto mbcache uas usb_storage sd_mod ata_generic 
psmouse uhci_hcd ehci_pci ehci_hcd tg3 sdhci_pci i2c_i801 i2c_smbus
[   25.255546]  ptp ata_piix libata sdhci firewire_ohci scsi_mod usbcore 
pps_core firewire_core mmc_core libphy 

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
>> 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.
> [...]
>
> Works for me. Please provide more information about what your actual
> problem is!

GDM repeatedly restarts if any of the above packages are installed on
a Linux 4.x host.

If I revert to kernel 3.16, GDM launches as expected, as long as I
disable the Wayland session in the configuration.

This is on a Geode host. On this host, the only possible X video
drivers are fbdev, vesa or geode i.e. all drivers that lack 3D
capability and that require llvmpipe for gnome-session to launch.

Martin-Éric



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: stretch/sid
  APT prefers testing
  APT policy: (, 'testing'), (1011, 'stable')
Architecture: i386 (i586)

Kernel: Linux 3.16.0-4-586
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gdm3 depends on:
ii  accountsservice   0.6.43-1
ii  adduser   3.115
ii  dconf-cli 0.26.0-2
ii  dconf-gsettings-backend   0.26.0-2
ii  debconf [debconf-2.0] 1.5.59
ii  gir1.2-gdm-1.03.22.1-1
ii  gnome-session [x-session-manager] 3.22.2-1
ii  gnome-session-bin 3.22.2-1
ii  gnome-settings-daemon 3.22.1-1
ii  gnome-shell   3.22.2-1
ii  gnome-terminal [x-terminal-emulator]  3.22.1-1
ii  gsettings-desktop-schemas 3.22.0-1
ii  icewm [x-window-manager]  1.3.8+mod+20161220-1
ii  libaccountsservice0   0.6.43-1
ii  libaudit1 1:2.6.7-1
ii  libc6 2.24-8
ii  libcanberra-gtk3-00.30-3
ii  libcanberra0  0.30-3
ii  libgdk-pixbuf2.0-02.36.2-1
ii  libgdm1   3.22.1-1
ii  libglib2.0-0  2.50.2-2
ii  libglib2.0-bin2.50.2-2
ii  libgtk-3-03.22.5-1
ii  libkeyutils1  1.5.9-9
ii  libpam-modules1.1.8-3.4
ii  libpam-runtime1.1.8-3.4
ii  libpam-systemd232-8
ii  libpam0g  1.1.8-3.4
ii  librsvg2-common   2.40.16-1
ii  libselinux1   2.6-3
ii  libsystemd0   232-8
ii  libwrap0  7.6.q-26
ii  libx11-6  2:1.6.4-2
ii  libxau6   1:1.0.8-1
ii  libxdmcp6 1:1.1.2-1.1
ii  lsb-base  9.20161125
ii  mutter [x-window-manager] 3.22.2-2
ii  policykit-1   0.105-17
ii  ucf   3.0036
ii  x11-common1:7.7+18
ii  x11-xserver-utils 7.7+7
ii  xterm [x-terminal-emulator]   327-2

Versions of packages gdm3 recommends:
ii  at-spi2-core2.22.0-5
ii  desktop-base8.0.2
ii  x11-xkb-utils   7.7+3
ii  xserver-xephyr  2:1.19.0-3
ii  xserver-xorg1:7.7+18
ii  zenity  3.22.0-1

Versions of packages gdm3 suggests:
ii  gnome-orca3.22.2-1
ii  libpam-gnome-keyring  3.20.0-3

- -- debconf information:
  gdm3/daemon_name: /usr/sbin/gdm3
* shared/default-x-display-manager: gdm3

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAlh2uCAACgkQrh+Cd8S0
17amEw//SCT1kfvE4uABRCpl4wu3W5HS/WaoS1ceOpMVOvICfjxpsGO/bjBRXAen
/+wNWOvmZ++NQlmaXIA+7+v7CeSiLWxGbwBAneCkb9bT2epCmS4ScJ5YHsFmDMkx
DRDrMAT0BpxgfEeraivDivt8hpYfPJdWqLjgiXWXIGOKVQjbTHy7nS8+fG8Lzrp1
yAWA4Vvk+NWfmGOyg+ofEus/Y8Zrqi3g0+MXuNhjLzsaG4kndHsPGy0sa0cr5Xpj
B5v3ocofjWt+CoYS4yWKYSJCUtdPys/JSvfXtcfqEX6lagIyYUbs1R0RQe+AHOQp
XHSozrPZ5bwmaf4oMzR4Yi8yb+tZh40Vbxzh+IldaP0F91GCH0NVvLJ5K9zDhD24
Q2/JvM2A3Cf4omXAowZIWW7xBmpYj171O8b2Rl+0ce4qj/ajrrJpOmK+IFRJi2xq
hZUmkuAdalXMk+FB2Jyiq4P9UdQQJUuhClNp4zRDk1diG7lv0/3tOWmjoV1hGsHQ
H2Wd3U+VfTWYT83RR67X36I9ZeZlVygvqtFSNio3h5zQr/i3svTIK3Yr7txBBZA7
Az1/ud2I0jQKkLYt9wEz7nQ0Jpcgiecp8HOH9Y19F6VoguzOPoKG7etC4xSOWmTe
R4rVma3oO2CIICkpaiPUVgtAQcksD+5kKqXLolkQZ1iIJR9GhJ0=
=GIre
-END PGP SIGNATURE-



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 instead. Thus, please
> drop that dependency. Bonus points if you switch to -dbgsym packages too. :)

Thanks for the heads up.

Now, what I'm wondering is how that constitues a sufficient reason for
Severity:serious?

Martin-Éric



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?
>>
>> More to the point, what would a non-legacy target be expected to look like?
>
> This is partly due to apt-file supporting "Contents" files on mirrors
> without components.  The other part is how apt handles multiple sources
> lines for the same entry with this fetch rule from apt-file.
>
> If you only fetch items from Debian mirrors, you can trivially avoid
> this warning by setting:
>
>   Acquire::IndexTargets::deb::Contents-deb-legacy::DefaultEnabled
>
> to "false" in /etc/apt.conf.d/99local.conf (or a similar file).
> Alternatively you can remove the "deb::Contents-deb-legacy" from
> /etc/apt/apt.conf.d/50apt-file.conf.

Good to know. Please note that this is not documented in the apt.conf
(5) manpage.

> The only current other alternative is to rewrite the sources file so
> there is only one entry per mirror/suite.  The "deb822" format may come
> in handy here to keep things readable.  The format is described in
> sources.list.

Noted.

Cheers!
Martin-Éric



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 SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAlhJcqEACgkQrh+Cd8S0
17ax1RAAj4gyxDkNWWvwt4ge0+6VgdfV+w3hVsC1JDNJBw96adzisDmSWKIvWJI1
165HDkMC6t9uXiFBS1wOBA3cAE678dn/HUYMTXF/FyopT/BXYEzWlCVZzAWJzkaL
mNAcrMK0UWVsg6KiU2DsJe+ISj5RNHoTHEVFgB5yuOvBsdqp/wq0tTk+Rk3K7R6d
P93+NIHkiNz8oGVelwCOZkK/YAoYd3ZFqrwDlk5QrGI5yeASwm4gf1CU+jlJ8edV
Pi+aVegvojDYylYjberEtKowGLVm1AR9y4JBDsG+30kQmMzqbnUfCLfZItYel0Gx
7ji11DxmAcWPdxWA4Ov4UBUaaZGfRn6lWsSNXyi9E5Fh1NWI2L9jQm+VzXzmM9fy
gBZQiYqnVLwiezVs4Ca9rh0H+913u9NgbZz2gdkkUF2csX5gQnllUaRnTN4oLbQE
mSlJyRXfQCcZoZIce6PLQ/PKEvyDSrmYQ7zoPzbEHAwEntYKksOXsleqIVskQQue
I94yDD9jP+W7bdvn16JplymomGBEMGql2K7UMSGACzRh5dhiiQCF5455vKfzgo9l
Y00f+lbv7BFlPSDLDzr4NgF6RZXU7IT/Nr4WDrWoFS+EegJXvipHG0kY6IKNMgpb
RxQ7nguc69g3VDe6rWUNMuSORHobj9dExUH5tCn0WW6vQAPGpVk=
=o4qL
-END PGP SIGNATURE-



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

2016-11-28 Thread Martin-Éric Racine
Package: xul-ext-mozvoikko
Followup-For: Bug #846036

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Please find enclosed the diff for packaging mozvoikko 2.2, including a sizeable 
overhaul of the Debian files.

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages xul-ext-mozvoikko depends on:
pn  iceweasel | icedove | iceape  
pn  libvoikko1
pn  voikko-fi 

xul-ext-mozvoikko recommends no packages.

xul-ext-mozvoikko suggests no packages.

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAlg75jcACgkQrh+Cd8S0
17bOPg//XXCOho52QmMF3FWbVYs2Wr7aPHBQits7n03G+JT4D3VxZ/7ivA60p0Q7
AchJfLwGdh02ae3+1joZS90vWcQ71DV//o5dM7NvJaLVj/ZbI0APtvRHCDtNyECJ
p9NTQYs2qO1oM4rU/T6yYC+BbEtsel2hvYtRF/Mlws9ZjSRQGqsCc83kSd7rhGJ9
htNsPxDgSRqeFxzBn3fMc8PHhQFQ25bO26beeU+jw4mu721l1ECvwTm0bXkuSeDp
j6JqeKuIEAp8iXaV4ga3aGqGpe/l9fpV40Qv8eFfwnMGHrpyElhYGEjMwEa1C6H+
LH277HHPny11nEzbTy/sEOZIOlYV5unr3NcnYpeGzIzjnPk19oyqmad4JXf0Pyfo
tMJu3FXVEj3qgCI1I2+tEbI5jUvUU2e52Btgzw8YM1re39P6+tkhn4p+bE9jAYMx
ymxc1Nkd+bV9BTSlqRC7g+V77/QcfoJl20gKovRv5ef+8Sd1eQMyq0u5+E9Grtn/
4O/qGNnpX0nXEQAOlrphusZ3OeGErkFtq7Q7uzlUzF3O66pMyZlzQ9H3Evm36uML
bPQy/V0QmVdI85LdEVpijBKu2HUTd5NeVjtpSFpn6slnOi+LlMP/Jz7TCHSplj4o
HjiDjSLNKOpG7hCK6XimgAg5uZtV9TAU0jhKe6v5PzCYcLrh0z8=
=hdDK
-END PGP SIGNATURE-
diff -cr ../mozvoikko-2.0.1/debian/changelog ../mozvoikko-2.2/debian/changelog
*** ../mozvoikko-2.0.1/debian/changelog	2016-11-28 01:33:13.0 +0200
--- ../mozvoikko-2.2/debian/changelog	2016-11-28 09:50:44.516803607 +0200
***
*** 1,3 
--- 1,29 
+ mozvoikko (2.2-0.1) unstable; urgency=low
+ 
+   * Non-maintainer upload.
+   * New upstream release (Closes: #846036).
+   * Bumped debhelper compat to 9.
+   * [debian/control]
+ = Build-Depends on debhelper (>= 9)
+ = Bumped Standards-Version to 3.9.8 (no change required).
+ + Added the Homepage field.
+ - Dropped the mozvoikko/extra/oldlibs transitional package.
+ = Rewrote the long description to better reflect the multipurpose
+   direction of Voikko and the transition from Iceweasel to Firefox.
+ + Added a generic voikko-dictionary as an alternative to voikko-fi.
+   * [debian/rules]
+ + override_dh_install: -delete COPYING (included in [debian/copyright]).
+   * [debian/copyright]
+ = Migrated to DEP-5 format.
+ = Migrated the source URL to the current upstream site.
+   * [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 Nov 2016 09:50:19 +0200
+ 
  mozvoikko (2.0.1-1.1) unstable; urgency=medium
  
* Non-maintainer upload.
diff -cr ../mozvoikko-2.0.1/debian/compat ../mozvoikko-2.2/debian/compat
*** ../mozvoikko-2.0.1/debian/compat	2011-11-29 21:03:15.0 +0200
--- ../mozvoikko-2.2/debian/compat	2016-11-28 02:29:51.0 +0200
***
*** 1 
! 5
--- 1 
! 9
diff -cr ../mozvoikko-2.0.1/debian/control ../mozvoikko-2.2/debian/control
*** ../mozvoikko-2.0.1/debian/control	2012-01-10 19:53:33.0 +0200
--- ../mozvoikko-2.2/debian/control	2016-11-28 09:49:41.090072129 +0200
***
*** 2,29 
  Section: web
  Priority: optional
  Maintainer: Heikki Mäntysaari <heikki.mantysa...@linux.fi>
! Build-Depends: debhelper (>= 7.0.50), mozilla-devscripts
! Standards-Version: 3.9.2
  
  Package: xul-ext-mozvoikko
  Architecture: all
! Depends: ${misc:Depends}, libvoikko1, voikko-fi, ${xpi:Depends}
  Breaks: mozvoikko (<= 1.0)
  Replaces: mozvoikko
! Description: Finnish spell-checker extension for Iceweasel  
!  Finnish spell-checker extension for Iceweasel. Spell-checking 
!  functionality is provided by Voikko - a free spelling checker 
!  for Finnish language.
! 
! Package: mozvoikko
! Priority: extra
! Section: oldlibs
! Architecture: all
! Depends: ${misc:Depends}, ${shlibs:Depends}, xul-ext-mozvoikko
! Description: Finnish spell-checker extension for Iceweasel (transitional package)
!  Finnish spell-checker extension for Iceweasel. Spell-checking 
!  functionality is provided by Voikko - a free spelling checker 
!  for Finnish language.
!  .
!  This is just a transitional package to pull in xul-ext-mozvoikko
!  on upgrades. It may be safely removed
--- 2,20 
  Section: web
  Priority: optional
  Maintainer: Heikki Mäntysaari <heikki.mantysa...@linux.fi>
! Build-Depends: debhelper (>= 9), mozilla-devscripts
! Standards-Version: 3.9.8
! Homepage: http://voikko.puimula.org/
  
  Package: xul-ext-mozvoikko
  Architect

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 changes to the packaging are filed as a seperate bug report.

The new location for all voikko packages (including this XUL extension) is:

http://voikko.puimula.org/sources.html

- -- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (, 'testing'), (1011, 'stable')
Architecture: i386 (i586)

Kernel: Linux 3.16.0-4-586
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xul-ext-mozvoikko depends on:
ii  iceweasel   45.5.0esr-1
ii  libvoikko1  4.0.2-2
ii  voikko-fi   2.1-1

xul-ext-mozvoikko recommends no packages.

xul-ext-mozvoikko suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAlg7h9oACgkQrh+Cd8S0
17ZjTw/9G6zw7iaSszEkVNnc9iOXb37uOGr49rSM6GoC0mRvHGlalCB58aUEPaKm
Mle5IVkDCQeOPHAtHsQLTVMAumfE5Zif/1/NDEXBNGGHLarisIrjwqm0twh7ftKN
DDyJhRiQ/yBge4rSramHT10hMlEGt2DZXIPwBuE1zEKzDeI/rNEGz2plGK2Pbbjt
jWGxMIfSUQaf4I7vp0ub3g+KHqSOda3KK4ZJ+XBY3MiUi7EyUSBHuWPg6OFwB2Rh
haF/VhShaKzgDoSWuzsTSXmBChKRjGe7M6Asd6SI0jmUAGgxQ+OlYv5SpdXxlpSV
tKx206IIQPZLOa00SiRpnUIjK5joWbxeRnIzkbOJm5vAOp4KWD7gOfaY9Lqf+f3F
j4ZnhDiPQGoQ0Iu6gHazchr37R5BRvJKoMcGyms4A6J6aw/VztBJBF2LpaC8HEYq
ViSUahSGd0z1HyI57QMc7RDpyLE5oXvZs7IwdXSEI6yskKhVStE2FETcp1m2+51z
yS5UJcLWKIHVHnGnxoEdAdKv/j5Z+jqFebp1KE+m/orELnjNkiY0u8K5tWvnQBz4
QjTJRSqmBb19Y64BQLPblRE2eUfqFFdeLa9O6DDcDm0JZxzfsukGDOL26Uyi0+KS
SmzqUPVCKRmYw5KqbX51nLdx1WUupwn2Cqq+G5uxzk0n/nlYa+Q=
=qdSu
-END PGP SIGNATURE-



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 Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (, 'testing'), (1011, 'stable')
Architecture: i386 (i586)

Kernel: Linux 3.16.0-4-586
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-

iHgEARECADgWIQQ0UNMMeTbhfuC5+Dp5evnrHgy5zQUCWDtSChocbWFydGluLWVy
aWMucmFjaW5lQGlraS5maQAKCRB5evnrHgy5zeJNAJ43qIdxdtYb7OAaUo3YjnKt
6JNwsQCgmGdNBonsLY5IByNAZfSRhLSi+cs=
=LOxH
-END PGP SIGNATURE-



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 [debian/rules] as 'dh --with xul-ext' so the Depends of the binary 
target will be automatically updated upon rebuild.

- -- System Information: Debian Release: stretch/sid
  APT prefers testing
  APT policy: (, 'testing'), (1011, 'stable')
Architecture: i386 (i586)

Kernel: Linux 3.16.0-4-586
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xul-ext-mozvoikko depends on:
ii  iceweasel   45.5.0esr-1
ii  libvoikko1  4.0.2-2
ii  voikko-fi   2.1-1

xul-ext-mozvoikko recommends no packages.

xul-ext-mozvoikko suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHgEARECADgWIQQ0UNMMeTbhfuC5+Dp5evnrHgy5zQUCWDtQzxocbWFydGluLWVy
aWMucmFjaW5lQGlraS5maQAKCRB5evnrHgy5zUrjAJ9VjWV9WJWj5N6PlLt0l3o9
76GkrwCeJnJbj7GfHs9uBMTjN3S4m6H5ETQ=
=feFC
-END PGP SIGNATURE-



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 for by
>> individual packages' debian/rules.
>
> I'm inclined to agree, but you don't have a build system and that is
> precisely why you need to handle this here. If cups-pdf was using a
> Makefile, autotools or cmake, then dh_auto_* would just work (in most
> cases). But since you are invoking the compiler from debian/rules
> directly that's the place to set up CC.
>
> Guillem Jover has a draft[1] for a file /usr/share/dpkg/buildtools.mk or
> similar that would set up variables such as CC. Thus when that
> materializes, you can replace my patch with including such a makefile.
>
> Helmut
>
> [1] https://lists.debian.org/20150510013227.ga24...@gaara.hadrons.org

Fair enough.  I'm wondering if the enclosed patch would accomplish the
same thing.  I mean, the goal always is to set CC for the target host,
right?

Martin-Éric
diff -Nru cups-pdf-2.6.1/debian/changelog cups-pdf-2.6.1/debian/changelog
--- cups-pdf-2.6.1/debian/changelog 2016-02-23 15:18:02.0 +0200
+++ cups-pdf-2.6.1/debian/changelog 2016-11-16 16:37:40.0 +0200
@@ -1,3 +1,14 @@
+cups-pdf (2.6.1-22) unstable; urgency=medium
+
+  * Fix "cups-pdf FTCBFS: uses build architecture compiler" (Closes: #843910)
++ Added [debian/rules] fragment:
+  export CC := $(shell dpkg-architecture --query DEB_HOST_GNU_TYPE)-gcc
+= Thanks to Helmut Grohne for the alternate patch. 
+  * Updated the Copyright years in [debian/rules] and [debian/copyright].
+  * Bumped Standards-Version to 3.9.8 (no change required).
+
+ -- Martin-Éric Racine <martin-eric.rac...@iki.fi>  Wed, 16 Nov 2016 16:37:40 
+0200
+
 cups-pdf (2.6.1-21) unstable; urgency=medium
 
   * Fixed Lintian "W: spelling-error-in-readme-debian: debuging debugging"
diff -Nru cups-pdf-2.6.1/debian/control cups-pdf-2.6.1/debian/control
--- cups-pdf-2.6.1/debian/control   2016-02-23 15:15:02.0 +0200
+++ cups-pdf-2.6.1/debian/control   2016-11-16 16:35:34.0 +0200
@@ -5,7 +5,7 @@
 Maintainer: Debian CUPS Maintainers <debian-print...@lists.debian.org>
 Uploaders: Martin-Éric Racine <martin-eric.rac...@iki.fi>
 Build-Depends: debhelper (>= 9.0~)
-Standards-Version: 3.9.7
+Standards-Version: 3.9.8
 
 Package: printer-driver-cups-pdf
 Architecture: any
diff -Nru cups-pdf-2.6.1/debian/copyright cups-pdf-2.6.1/debian/copyright
--- cups-pdf-2.6.1/debian/copyright 2015-03-11 23:21:33.0 +0200
+++ cups-pdf-2.6.1/debian/copyright 2016-11-16 16:27:46.00000 +0200
@@ -23,6 +23,6 @@
 License: GPL-2+
 
 Files: debian/*
-Copyright: © 2004-2015 Martin-Éric Racine <martin-eric.rac...@iki.fi>
+Copyright: © 2004-2016 Martin-Éric Racine <martin-eric.rac...@iki.fi>
© 2009,2011 Till Kamppeter <till.kamppe...@gmail.com>
 License: GPL-2+
diff -Nru cups-pdf-2.6.1/debian/rules cups-pdf-2.6.1/debian/rules
--- cups-pdf-2.6.1/debian/rules 2015-05-06 14:31:56.0 +0300
+++ cups-pdf-2.6.1/debian/rules 2016-11-16 16:27:22.0 +0200
@@ -2,16 +2,17 @@
 #
 # debhelper-7 [debian/rules] for cups-pdf
 #
-# COPYRIGHT © 2003-2015 Martin-Éric Racine <martin-eric.rac...@iki.fi>
+# COPYRIGHT © 2003-2016 Martin-Éric Racine <martin-eric.rac...@iki.fi>
 #
 # LICENSE
 # GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html>
 #
+export CC   := $(shell dpkg-architecture --query DEB_HOST_GNU_TYPE)-gcc
 export CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS)
 export CFLAGS   := $(shell dpkg-buildflags --get CFLAGS)
 export LDFLAGS  := $(shell dpkg-buildflags --get LDFLAGS)
-# Append flags for Long File Support
-# LFS_CPPFLAGS is non-existent
+# Append flags for Long File Support (LFS)
+# LFS_CPPFLAGS does not exist
 export DEB_CFLAGS_MAINT_APPEND  +=$(shell getconf LFS_CFLAGS)
 export DEB_LDFLAGS_MAINT_APPEND +=$(shell getconf LFS_LDFLAGS)
 


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 triplet-prefixed compiler
> fixes the build. Please consider applying the attached patch.
>
> Helmut

Thanks for the patch.

I cannot help but wonder if setting CC for cross-build would be best
handled by the build tools themselves, rather than compensated for by
individual packages' debian/rules.

Opinions?

Cheers!
Martin-Éric



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, 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.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.  By comparison, launching kernel
>> > > 3.16 from the GRUB menu, kernel messages start appearing within a few
>> > > seconds of the "loading initrd-image" GRUB message.
>> >
>> >
>> > What's the kernel command line?
>>
>>
>> BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-586
>> root=UUID=97b2628b-28a5-49f2-85f7-495728b3bef8 ro panic=15 pnpbios=off
>> cs5535audio.ac97_quirk=1 nopat quiet nosplash
>
> ... and the same parameters for 4.7?

Yup.

>> > Please also get a kernel log, by replacing the 'quiet' parameter on the
>> > boot command line with 'earlyprintk=vga'.
>>
>>
>> This still doesn't get me past the "loading initrd image" GRUB prompt.
>
> *Nothing* is logged after that?

Nothing at all.

--.Martin-Éric



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.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.  By comparison, launching kernel
>> 3.16 from the GRUB menu, kernel messages start appearing within a few
>> seconds of the "loading initrd-image" GRUB message.
>
> What's the kernel command line?

BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-586
root=UUID=97b2628b-28a5-49f2-85f7-495728b3bef8 ro panic=15 pnpbios=off
cs5535audio.ac97_quirk=1 nopat quiet nosplash

> Please also get a kernel log, by replacing the 'quiet' parameter on the
> boot command line with 'earlyprintk=vga'.

This still doesn't get me past the "loading initrd image" GRUB prompt.

Martin-Éric



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.  By comparison, launching kernel 3.16 from the GRUB menu, kernel 
messages start appearing within a few seconds of the "loading initrd-image" 
GRUB message.

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information

Geode LX.  ION 603A.

** Network interface configuration:
auto lo
iface lo inet loopback

** PCI devices:
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode 
companion] Host Bridge [1022:2080] (rev 31)
Subsystem: FIRST INTERNATIONAL Computer Inc CS5536 [Geode companion] 
Host Bridge [1509:801b]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR-  [disabled]
Kernel modules: lxfb

00:01.2 Entertainment encryption device [1010]: Advanced Micro Devices, Inc. 
[AMD] Geode LX AES Security Block [1022:2082]
Subsystem: FIRST INTERNATIONAL Computer Inc Geode LX AES Security Block 
[1509:801b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- 
Kernel driver in use: ohci-pci
Kernel modules: ohci_pci

00:0f.5 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode 
companion] EHC [1022:2095] (rev 02) (prog-if 20 [EHCI])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci


** USB devices:
not available


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (, 'testing'), (1011, 'stable')
Architecture: i386 (i586)

Kernel: Linux 3.16.0-4-586
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-4.7.0-1-686 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.125
ii  kmod22-1.1
ii  linux-base  4.5

Versions of packages linux-image-4.7.0-1-686 recommends:
ii  firmware-linux-free  3.4
ii  irqbalance   1.1.0-2

Versions of packages linux-image-4.7.0-1-686 suggests:
pn  debian-kernel-handbook  
ii  grub-pc 2.02~beta3-1
pn  linux-doc-4.7   

Versions of packages linux-image-4.7.0-1-686 is related to:
ii  firmware-amd-graphics 20160824-1
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
ii  firmware-iwlwifi  20160824-1
pn  firmware-libertas 
ii  firmware-linux-nonfree20160824-1
ii  firmware-misc-nonfree 20160824-1
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information



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
>>
>> I get the above error when trying to connect to a router using
>> openssh-client from Testing.
>>
>> Connecting using the openssh-client from Stable works as expected.
>
>
> That's to be expected, given:
>
> openssh (1:7.1p1-1) unstable; urgency=medium
>
>   * New upstream release (http://www.openssh.com/txt/release-7.0, closes:
> #785190):
> - Support for the legacy SSH version 1 protocol is disabled by default
>   at compile time.
> - Support for the 1024-bit diffie-hellman-group1-sha1 key exchange is
>   disabled by default at run-time.  It may be re-enabled using the
>   instructions at http://www.openssh.com/legacy.html

That would indeed explain it.

Exception added in .ssh/config for that subnet.

Thanks!
Martin-Éric



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 using the openssh-client from Stable works as expected.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (1011, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openssh-client depends on:
ii  adduser   3.115
ii  dpkg  1.18.10
ii  libc6 2.24-3
ii  libedit2  3.1-20150325-1+b1
ii  libgssapi-krb5-2  1.14.3+dfsg-2
ii  libselinux1   2.5-3
ii  libssl1.0.2   1.0.2j-1
ii  passwd1:4.2-3.2
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages openssh-client recommends:
ii  xauth  1:1.0.9-1

Versions of packages openssh-client suggests:
pn  keychain  
pn  libpam-ssh
pn  monkeysphere  
pn  ssh-askpass   

-- no debconf information



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 prefers testing
  APT policy: (1011, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  evolution-data-server3.22.1-2
ii  gir1.2-accountsservice-1.0   0.6.40-3
ii  gir1.2-atspi-2.0 2.22.0-1
ii  gir1.2-caribou-1.0   0.4.21-1
ii  gir1.2-freedesktop   1.50.0-1
ii  gir1.2-gcr-3 3.20.0-3
ii  gir1.2-gdesktopenums-3.0 3.22.0-1
ii  gir1.2-gdm-1.0   3.22.0-1
ii  gir1.2-glib-2.0  1.50.0-1
ii  gir1.2-gnomebluetooth-1.03.20.0-1
ii  gir1.2-gnomedesktop-3.0  3.22.1-1
ii  gir1.2-gtk-3.0   3.22.1-1
ii  gir1.2-gweather-3.0  3.20.3-1
ii  gir1.2-ibus-1.0  1.5.11-1
ii  gir1.2-mutter-3.03.22.1-2
ii  gir1.2-networkmanager-1.01.4.2-1+b1
ii  gir1.2-nmgtk-1.0 1.4.2-1
ii  gir1.2-pango-1.0 1.40.3-2
ii  gir1.2-polkit-1.00.105-16
ii  gir1.2-soup-2.4  2.56.0-1
ii  gir1.2-telepathyglib-0.120.24.1-1.1
ii  gir1.2-telepathylogger-0.2   0.8.2-1
ii  gir1.2-upowerglib-1.00.99.4-4
ii  gjs  1.46.0-1+b1
ii  gnome-backgrounds3.22.1-1
ii  gnome-settings-daemon3.22.1-1
ii  gnome-shell-common   3.22.1-1
ii  gsettings-desktop-schemas3.22.0-1
ii  libatk-bridge2.0-0   2.22.0-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-3
ii  libcairo21.14.6-1+b1
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libcroco30.6.11-2
ii  libdbus-glib-1-2 0.108-1
ii  libecal-1.2-19   3.22.1-2
ii  libedataserver-1.2-223.22.1-2
ii  libgcr-base-3-1  3.20.0-3
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libgirepository-1.0-11.50.0-1
ii  libgjs0e [libgjs0-libmozjs-24-0] 1.46.0-1+b1
ii  libglib2.0-0 2.50.1-1
ii  libglib2.0-bin   2.50.1-1
ii  libgstreamer1.0-01.8.3-1
ii  libgtk-3-0   3.22.1-1
ii  libical2 2.0.0-0.5+b1
ii  libicu57 57.1-4
ii  libjson-glib-1.0-0   1.2.2-1
ii  libmozjs-24-024.2.0-3.1
ii  libmutter0i  3.22.1-2
ii  libnm-glib4  1.4.2-1+b1
ii  libnm-util2  1.4.2-1+b1
ii  libpango-1.0-0   1.40.3-2
ii  libpangocairo-1.0-0  1.40.3-2
ii  libpolkit-agent-1-0  0.105-16
ii  libpolkit-gobject-1-00.105-16
ii  libpulse-mainloop-glib0  9.0-4
ii  libpulse09.0-4
ii  libsecret-1-00.18.5-2
ii  libstartup-notification0 0.12-4
ii  libsystemd0  231-9
ii  libtelepathy-glib0   0.24.1-1.1
ii  libwayland-client0   1.11.0-2
ii  libx11-6 2:1.6.3-1
ii  libxfixes3   1:5.0.2-1
ii  mutter   3.22.1-2
ii  python3  3.5.1-4
ii  telepathy-mission-control-5  1:5.16.3-2

Versions of packages gnome-shell recommends:
ii  gdm33.22.0-1
ii  gkbd-capplet3.22.0.1-1
pn  gnome-contacts  
ii  gnome-control-center1:3.22.1-1
ii  gnome-themes-standard-data  3.22.2-1
ii  gnome-user-guide3.22.0-1
ii  

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 server symlink status:

lrwxrwxrwx 1 root root 13 Aug 17  2014 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Sep  6 16:09 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:05.0 VGA compatible controller [0300]: NVIDIA Corporation C51 [GeForce 6150 
LE] [10de:0241] (rev a2)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.7.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 
20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.6-1 (2016-10-07)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 40128 Oct 11 17:42 /var/log/Xorg.0.log
-rw-r--r-- 1 perkelix perkelix 70416 Oct 21 12:15 
/home/perkelix/.local/share/xorg/Xorg.0.log

Contents of most recent Xorg X server log file 
(/home/perkelix/.local/share/xorg/Xorg.0.log):
-
[   160.238] (--) Log file renamed from 
"/home/perkelix/.local/share/xorg/Xorg.pid-1135.log" to 
"/home/perkelix/.local/share/xorg/Xorg.0.log"
[   160.239] 
X.Org X Server 1.18.4
Release Date: 2016-07-19
[   160.242] X Protocol Version 11, Revision 0
[   160.242] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[   160.242] Current Operating System: Linux media 4.7.0-1-amd64 #1 SMP Debian 
4.7.6-1 (2016-10-07) x86_64
[   160.242] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.7.0-1-amd64 
root=UUID=e430a8a8-229e-4696-a3a6-6929d945a22c ro panic=15 iommu=noagp 
nouveau.config=NvMSI=0 video=TV-1:d quiet splash
[   160.243] Build Date: 06 September 2016  01:32:44PM
[   160.243] xorg-server 2:1.18.4-2 (https://www.debian.org/support) 
[   160.243] Current version of pixman: 0.34.0
[   160.243]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   160.243] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   160.243] (==) Log file: "/home/perkelix/.local/share/xorg/Xorg.0.log", 
Time: Fri Oct 21 11:36:02 2016
[   160.269] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   160.303] (==) No Layout section.  Using the first Screen section.
[   160.303] (==) No screen section available. Using defaults.
[   160.303] (**) |-->Screen "Default Screen Section" (0)
[   160.304] (**) |   |-->Monitor ""
[   160.331] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   160.331] (==) Automatically adding devices
[   160.331] (==) Automatically enabling devices
[   160.331] (==) Automatically adding GPU devices
[   160.331] (==) Max clients allowed: 256, resource mask: 0x1f
[   160.331] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   160.331]Entry deleted from font path.
[   160.331] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[   160.331]Entry deleted from font path.
[   160.331] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[   160.332]Entry deleted from font path.
[   160.332] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[   160.332]Entry deleted from font path.
[   160.332] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[   160.332]Entry deleted from font path.
[   160.332] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[   160.332]Entry deleted from font path.
[   160.332] (==) FontPath set to:
/usr/share/fonts/X11/misc,
built-ins
[   160.332] (==) ModulePath set to "/usr/lib/xorg/modules"
[   160.332] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   160.332] (II) Loader magic: 0x563cf1284dc0
[   160.332] (II) Module ABI versions:
[   160.333]X.Org ANSI C Emulation: 0.4
[   160.333]X.Org Video Driver: 20.0
[   160.333]X.Org XInput driver : 22.1
[   160.333]X.Org Server Extension : 9.0
[   160.337] (++) using VT number 3

[   160.364] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
[   160.365] (II) xfree86: Adding drm device (/dev/dri/card0)
[   160.387] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 9 paused 0
[   160.390] (--) PCI:*(0:0:5:0) 10de:0241:103c:2a34 rev 162, Mem @ 
0xfc00/16777216, 0xe000/268435456, 

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 policy: (1011, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.40-3
ii  apg2.2.3.dfsg.1-4
ii  colord 1.3.3-2
ii  desktop-file-utils 0.23-1
ii  gnome-control-center-data  1:3.22.1-1
ii  gnome-desktop3-data3.22.1-1
ii  gnome-settings-daemon  3.22.1-1
ii  gsettings-desktop-schemas  3.22.0-1
ii  libaccountsservice00.6.40-3
ii  libatk1.0-02.22.0-1
ii  libc6  2.24-3
ii  libcairo-gobject2  1.14.6-1+b1
ii  libcairo2  1.14.6-1+b1
ii  libcanberra-gtk3-0 0.30-3
ii  libcanberra0   0.30-3
ii  libcheese-gtk253.22.1-1
ii  libcheese8 3.22.1-1
ii  libclutter-1.0-0   1.26.0+dfsg-1
ii  libclutter-gtk-1.0-0   1.8.2-1
ii  libcolord-gtk1 0.1.26-1
ii  libcolord2 1.3.3-2
ii  libcups2   2.2.1-1
ii  libfontconfig1 2.11.0-6.7
ii  libgdk-pixbuf2.0-0 2.36.0-1
ii  libglib2.0-0   2.50.1-1
ii  libgnome-bluetooth13   3.20.0-1
ii  libgnome-desktop-3-12  3.22.1-1
ii  libgoa-1.0-0b  3.22.1-1
ii  libgoa-backend-1.0-1   3.22.1-1
ii  libgrilo-0.3-0 0.3.2-2
ii  libgtk-3-0 3.22.1-1
ii  libgtop-2.0-10 2.34.1-2
ii  libgudev-1.0-0 230-3
ii  libibus-1.0-5  1.5.11-1
ii  libkrb5-3  1.14.3+dfsg-2
ii  libmm-glib01.6.2-1
ii  libnm0 1.4.2-1+b1
ii  libnma01.4.2-1
ii  libpango-1.0-0 1.40.3-2
ii  libpangocairo-1.0-01.40.3-2
ii  libpolkit-gobject-1-0  0.105-16
ii  libpulse-mainloop-glib09.0-4
ii  libpulse0  9.0-4
ii  libpwquality1  1.3.0-1
ii  libsmbclient   2:4.4.6+dfsg-2
ii  libsoup2.4-1   2.56.0-1
ii  libupower-glib30.99.4-4
ii  libwacom2  0.22-1
ii  libx11-6   2:1.6.3-1
ii  libxi6 2:1.7.6-1
ii  libxml22.9.4+dfsg1-2

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime  2.9.2-3
ii  cups-pk-helper0.2.6-1
ii  gkbd-capplet  3.22.0.1-1
ii  gnome-online-accounts 3.22.1-1
ii  gnome-user-guide  3.22.0-1
pn  gnome-user-share  
ii  iso-codes 3.70-1
ii  libcanberra-pulse 0.30-3
ii  libnss-myhostname 231-9
ii  mousetweaks   3.12.0-1
ii  network-manager-gnome 1.4.2-1
ii  policykit-1   0.105-16
ii  pulseaudio-module-bluetooth   9.0-4
ii  realmd0.16.3-1
ii  rygel 0.32.0-2
ii  system-config-printer-common  1.5.7-2

Versions of packages gnome-control-center suggests:
ii  gstreamer1.0-pulseaudio  1.8.3-1+b1
pn  libcanberra-gtk-module   
ii  libcanberra-gtk3-module  0.30-3
ii  x11-xserver-utils7.7+7

-- no debconf information



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 take into consideration the fact that an administrator
might have purposely split components from the same repository over many lines
for better readability and there's nothing inherently wrong with doing that.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (1011, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apt depends on:
ii  adduser 3.115
ii  debian-archive-keyring  2014.3
ii  gpgv2.1.15-3
ii  init-system-helpers 1.45
ii  libapt-pkg5.0   1.3.1
ii  libc6   2.24-3
ii  libgcc1 1:6.1.1-11
ii  libstdc++6  6.1.1-11

Versions of packages apt recommends:
ii  gnupg   2.1.15-3
ii  gnupg2  2.1.15-3

Versions of packages apt suggests:
pn  apt-doc 
ii  aptitude0.8.3-1+b1
ii  dpkg-dev1.18.10
ii  powermgmt-base  1.31+nmu1
ii  python-apt  1.1.0~beta5

-- no debconf information



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 since upgrading from GNOME 3.14 (stable) to 3.20 (testing).  Tried 
removing xserver-xorg-vidoe-nouveau and let X use xserver's built-in modeline 
driver, but it doesn't solve it.  Basically, GNOME 3.20 freezes at random for 
several minutes at a time.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (1011, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  evolution-data-server3.22.0-2
ii  gir1.2-accountsservice-1.0   0.6.40-3
ii  gir1.2-atspi-2.0 2.22.0-1
ii  gir1.2-caribou-1.0   0.4.21-1
ii  gir1.2-freedesktop   1.50.0-1
ii  gir1.2-gcr-3 3.20.0-2
ii  gir1.2-gdesktopenums-3.0 3.22.0-1
ii  gir1.2-gdm-1.0   3.22.0-1
ii  gir1.2-glib-2.0  1.50.0-1
ii  gir1.2-gnomebluetooth-1.03.20.0-1
ii  gir1.2-gnomedesktop-3.0  3.22.0-1
ii  gir1.2-gtk-3.0   3.22.1-1
ii  gir1.2-gweather-3.0  3.20.3-1
ii  gir1.2-ibus-1.0  1.5.11-1
ii  gir1.2-mutter-3.03.22.0-1
ii  gir1.2-networkmanager-1.01.4.2-1
ii  gir1.2-nmgtk-1.0 1.4.2-1
ii  gir1.2-pango-1.0 1.40.3-2
ii  gir1.2-polkit-1.00.105-16
ii  gir1.2-soup-2.4  2.56.0-1
ii  gir1.2-telepathyglib-0.120.24.1-1.1
ii  gir1.2-telepathylogger-0.2   0.8.2-1
ii  gir1.2-upowerglib-1.00.99.4-4
ii  gjs  1.46.0-1
ii  gnome-backgrounds3.22.1-1
ii  gnome-settings-daemon3.22.0-1
ii  gnome-shell-common   3.22.0-1
ii  gsettings-desktop-schemas3.22.0-1
ii  libatk-bridge2.0-0   2.22.0-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-3
ii  libcairo21.14.6-1+b1
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libcroco30.6.11-2
ii  libdbus-glib-1-2 0.108-1
ii  libecal-1.2-19   3.22.0-2
ii  libedataserver-1.2-223.22.0-2
ii  libgcr-base-3-1  3.20.0-2
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libgirepository-1.0-11.50.0-1
ii  libgjs0e [libgjs0-libmozjs-24-0] 1.46.0-1
ii  libglib2.0-0 2.50.0-2
ii  libglib2.0-bin   2.50.0-2
ii  libgstreamer1.0-01.8.3-1
ii  libgtk-3-0   3.22.1-1
ii  libical2 2.0.0-0.5+b1
ii  libicu57 57.1-4
ii  libjson-glib-1.0-0   1.2.2-1
ii  libmozjs-24-024.2.0-3.1
ii  libmutter0i  3.22.0-1
ii  libnm-glib4  1.4.2-1
ii  libnm-util2  1.4.2-1
ii  libpango-1.0-0   1.40.3-2
ii  libpangocairo-1.0-0  1.40.3-2
ii  libpolkit-agent-1-0  0.105-16
ii  libpolkit-gobject-1-00.105-16
ii  libpulse-mainloop-glib0  9.0-3
ii  libpulse09.0-3
ii  libsecret-1-00.18.5-2
ii  libstartup-notification0 0.12-4
ii  libsystemd0  231-9
ii  libtelepathy-glib0   0.24.1-1.1
ii  libwayland-client0   1.11.0-2
ii  libx11-6 2:1.6.3-1
ii  libxfixes3   1:5.0.2-1
ii  mutter   3.22.0-1
ii  python3  3.5.1-4
ii  telepathy-mission-control-5  1:5.16.3-2


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)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xul-ext-mozvoikko depends on:
ii  iceweasel   45.4.0esr-1~deb8u2
ii  libvoikko1  3.7.1-1
ii  voikko-fi   1.17-1

xul-ext-mozvoikko recommends no packages.

xul-ext-mozvoikko suggests no packages.

-- no debconf information



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 on my 
-hard-disk.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (, 'testing'), (1011, 'stable')
Architecture: i386 (i586)

Kernel: Linux 4.7.0-1-686 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  evolution-data-server3.22.0-2
ii  gir1.2-accountsservice-1.0   0.6.40-3
ii  gir1.2-atspi-2.0 2.22.0-1
ii  gir1.2-caribou-1.0   0.4.21-1
ii  gir1.2-freedesktop   1.50.0-1
ii  gir1.2-gcr-3 3.20.0-2
ii  gir1.2-gdesktopenums-3.0 3.22.0-1
ii  gir1.2-gdm-1.0   3.22.0-1
ii  gir1.2-glib-2.0  1.50.0-1
ii  gir1.2-gnomebluetooth-1.03.20.0-1
ii  gir1.2-gnomedesktop-3.0  3.22.0-1
ii  gir1.2-gtk-3.0   3.22.1-1
ii  gir1.2-gweather-3.0  3.20.3-1
ii  gir1.2-ibus-1.0  1.5.11-1
ii  gir1.2-mutter-3.03.22.0-1
ii  gir1.2-networkmanager-1.01.4.2-1
ii  gir1.2-nmgtk-1.0 1.4.2-1
ii  gir1.2-pango-1.0 1.40.3-2
ii  gir1.2-polkit-1.00.105-16
ii  gir1.2-soup-2.4  2.56.0-1
ii  gir1.2-telepathyglib-0.120.24.1-1.1
ii  gir1.2-telepathylogger-0.2   0.8.2-1
ii  gir1.2-upowerglib-1.00.99.4-4
ii  gjs  1.46.0-1
ii  gnome-backgrounds3.22.1-1
ii  gnome-settings-daemon3.22.0-1
ii  gnome-shell-common   3.22.0-1
ii  gsettings-desktop-schemas3.22.0-1
ii  libatk-bridge2.0-0   2.22.0-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-3
ii  libcairo21.14.6-1+b1
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libcroco30.6.11-2
ii  libdbus-glib-1-2 0.108-1
ii  libecal-1.2-19   3.22.0-2
ii  libedataserver-1.2-223.22.0-2
ii  libgcr-base-3-1  3.20.0-2
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libgirepository-1.0-11.50.0-1
ii  libgjs0e [libgjs0-libmozjs-24-0] 1.46.0-1
ii  libglib2.0-0 2.50.0-2
ii  libglib2.0-bin   2.50.0-2
ii  libgstreamer1.0-01.8.3-1
ii  libgtk-3-0   3.22.1-1
ii  libical2 2.0.0-0.5+b1
ii  libicu57 57.1-4
ii  libjson-glib-1.0-0   1.2.2-1
ii  libmozjs-24-024.2.0-3.1
ii  libmutter0i  3.22.0-1
ii  libnm-glib4  1.4.2-1
ii  libnm-util2  1.4.2-1
ii  libpango-1.0-0   1.40.3-2
ii  libpangocairo-1.0-0  1.40.3-2
ii  libpolkit-agent-1-0  0.105-16
ii  libpolkit-gobject-1-00.105-16
ii  libpulse-mainloop-glib0  9.0-3
ii  libpulse09.0-3
ii  libsecret-1-00.18.5-2
ii  libstartup-notification0 0.12-4
ii  libsystemd0  231-9
ii  libtelepathy-glib0   0.24.1-1.1
ii  libwayland-client0   1.11.0-2
ii  libx11-6 2:1.6.3-1
ii  libxfixes3   1:5.0.2-1
ii  mutter   3.22.0-1
ii  python3  3.5.1-4
ii  telepathy-mission-control-5  1:5.16.3-2

Versions of packages gnome-shell recommends:
ii  gdm33.22.0-1
ii  gkbd-capplet3.22.0.1-1
ii  gnome-contacts  3.22.1-1+b1
ii  gnome-control-center1:3.22.0-1
ii  gnome-themes-standard-data  

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 policy: (, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.37-3+b1
ii  apg2.2.3.dfsg.1-2
ii  colord 1.2.1-1+b2
ii  desktop-file-utils 0.22-1
ii  gnome-control-center-data  1:3.14.2-3
ii  gnome-desktop3-data3.14.1-1
ii  gnome-icon-theme   3.12.0-1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  gnome-settings-daemon  3.14.2-3
ii  gsettings-desktop-schemas  3.14.1-1
ii  libaccountsservice00.6.37-3+b1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-18+deb8u6
ii  libcairo-gobject2  1.14.0-2.1+deb8u1
ii  libcairo2  1.14.0-2.1+deb8u1
ii  libcanberra-gtk3-0 0.30-2.1
ii  libcanberra0   0.30-2.1
ii  libcheese-gtk233.14.1-2
ii  libcheese7 3.14.1-2
ii  libclutter-1.0-0   1.20.0-1
ii  libclutter-gtk-1.0-0   1.6.0-1
ii  libcolord-gtk1 0.1.25-1.1+b1
ii  libcolord2 1.2.1-1+b2
ii  libcups2   1.7.5-11+deb8u1
ii  libdbus-glib-1-2   0.102-1
ii  libfontconfig1 2.11.0-6.3+deb8u1
ii  libgdk-pixbuf2.0-0 2.31.1-2+deb8u5
ii  libgl1-mesa-glx [libgl1]   10.3.2-1+deb8u1
ii  libglib2.0-0   2.42.1-1+b1
ii  libgnome-bluetooth13   3.14.0-2
ii  libgnome-desktop-3-10  3.14.1-1
ii  libgoa-1.0-0b  3.14.2-1
ii  libgoa-backend-1.0-1   3.14.2-1
ii  libgrilo-0.2-1 0.2.11-2
ii  libgtk-3-0 3.14.5-1+deb8u1
ii  libgtop2-7 2.28.5-2+b1
ii  libibus-1.0-5  1.5.9-1
ii  libkrb5-3  1.12.1+dfsg-19+deb8u2
ii  libmm-glib01.4.0-1
ii  libnm-glib-vpn10.9.10.0-7
ii  libnm-glib40.9.10.0-7
ii  libnm-gtk0 0.9.10.0-2
ii  libnm-util20.9.10.0-7
ii  libpango-1.0-0 1.36.8-3
ii  libpangocairo-1.0-01.36.8-3
ii  libpolkit-gobject-1-0  0.105-15~deb8u2
ii  libpulse-mainloop-glib05.0-13
ii  libpulse0  5.0-13
ii  libpwquality1  1.2.3-1
ii  libsmbclient   2:4.2.10+dfsg-0+deb8u3
ii  libsoup2.4-1   2.48.0-1
ii  libupower-glib30.99.1-3.2
ii  libwacom2  0.8-1
ii  libx11-6   2:1.6.2-3
ii  libxi6 2:1.7.4-1+b2
ii  libxml22.9.1+dfsg1-5+deb8u3

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime   2.9.2-1
ii  cups-pk-helper 0.2.5-2+b1
ii  gkbd-capplet   3.6.0-1
ii  gnome-online-accounts  3.14.2-1
ii  gnome-user-guide   3.14.1-1
ii  gnome-user-share   3.14.0-2
ii  iso-codes  3.57-1
ii  libnss-myhostname  0.3-9
ii  mesa-utils 8.2.0-1
ii  mousetweaks3.12.0-1
ii  network-manager-gnome  0.9.10.0-2
ii  policykit-1-gnome  0.105-2
ii  realmd 0.15.1-1+b2
ii  rygel  0.24.2-1+b1
ii  system-config-printer  1.4.6-1

Versions of packages gnome-control-center suggests:
ii  gstreamer1.0-pulseaudio  1.4.4-2
pn  libcanberra-gtk-module   
ii  libcanberra-gtk3-module  0.30-2.1
ii  x11-xserver-utils7.7+3+b1

-- no debconf information



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.
>
> Should this bug be reassigned to lintian and retitled?

Probably, yes.

-- Martin-Éric



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 is
>> likely to be added later on, at which point there won't be enough swap
>> to save the suspend image;
>
> Why do you think it's likely?  Hibernation is mostly used on laptops
> and I don't believe they often get RAM upgrades; in fact increasingly
> they don't have even have sockets for RAM upgrades.

Because it's what everyone I know does: as soon as the price for the
type of RAM their computer needs drops, they max it out.

As for hibernate, it in fact is used a lot on office desktops as well.
It was the preferred way of leaving the office at my two previous
workplaces.

>> 2) Perform every tiny step of the partitioning and filesystem creation
>> manually in order to take into consideration the memory controller's
>> maximum supported RAM capacity.
>>
>> The former is inadequate, the later is overkill and honestly beyond
>> the lay user's skills.
>>
>> How about being able to tell the automated partitioning variant how
>> much swap we want, but let it calculate the size of the other
>> partitions by itself?
>
> How many 'lay users' that would be overwhelmed by the partitioner
> nevertheless understand how to upgrade RAM, what swap space is, and why
> they might need more than the default?  I think that's a very small
> group indeed.

Pretty much everyone I know knows how to download the upgrade
instructions from the manufacturer's website, remove a couple of
screws and insert a memory module.  By comparison, very few people I
know understand the intricacies of LVM partitioning.

Martin-Éric



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
2016-09-26 19:30 GMT+03:00 Debian Bug Tracking System <ow...@bugs.debian.org>:
> This is an automatic notification regarding your Bug report
> which was filed against the debian-installer package:
>
> #838919: debian-installer: please calculate swap parition according to max 
> RAM supported by the motherboard
>
> It has been closed by Ben Hutchings <b...@decadent.org.uk>.
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Ben Hutchings 
> <b...@decadent.org.uk> by
> replying to this email.
>
>
> --
> 838919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838919
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Edelleenlähetetty viesti --
> From: Ben Hutchings <b...@decadent.org.uk>
> To: 838919-d...@bugs.debian.org
> Cc:
> Date: Mon, 26 Sep 2016 17:27:23 +0100
> Subject: Re: Bug#838919: debian-installer: please calculate swap parition 
> according to max RAM supported by the motherboard
> 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 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 to
>> > store hibernate images, since the parition was calculated to store
>> > a much smaller RAM image.
>> >
>> > A more desirable method would be for d-i to use 'dmidecode' to
>> > probe the system's memory controller for the maximum amount of RAM
>> > that is supported and to calculate the swap partition size
>> > according to that.
>>
>> Of course many people never upgrade their ram, and often going beyond 50%
>> of maximum gets very expensive.
>>
>> Also many people never suspend.
>>
>> Also dmidecode is x86 only and some older systems didn't have it, so it
>> wouldn't help the majority of architectures.
>>
>> So while it is an idea, I am not convinced it doesn't actually create
>> problems.
>
> Right, this proposal sounds like it would be worse than the current
> heuristic in general.
>
> A better way to deal with this is to use LVM and leave some space
> unallocated initially so it's possible to grow swap or whatever other
> partition needs it later.

The thing is, right now, the user has two choices:

1) Trust d-i to make the right choices once, even though more RAM is
likely to be added later on, at which point there won't be enough swap
to save the suspend image;
2) Perform every tiny step of the partitioning and filesystem creation
manually in order to take into consideration the memory controller's
maximum supported RAM capacity.

The former is inadequate, the later is overkill and honestly beyond
the lay user's skills.

How about being able to tell the automated partitioning variant how
much swap we want, but let it calculate the size of the other
partitions by itself?

Martin-Éric



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 to store hibernate images, 
since the parition was calculated to store a much smaller RAM image.

A more desirable method would be for d-i to use 'dmidecode' to probe the 
system's memory controller for the maximum amount of RAM that is supported and 
to calculate the swap partition size according to that.

-- System Information:
Debian Release: 8.6
  APT prefers stable
  APT policy: (, 'stable'), (1001, 'oldstable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



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 regression.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages tidy depends on:
ii  libc6 2.23-4
ii  libtidy5  1:5.2.0-1.1

tidy recommends no packages.

tidy suggests no packages.

-- no debconf information



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 hwclock.service'.
>
> Please read up on the RTC handling strategy usually deployed when using
> systemd. Please read the information already provided in misc bug
> reports filed by people requesting to emulate the old strategy used by
> sysvinit. Some useful sources of information might be:
> https://wiki.archlinux.org/index.php/time
> https://www.freedesktop.org/software/systemd/man/timedatectl.html
> https://www.freedesktop.org/wiki/Software/systemd/timedated/
> https://wiki.archlinux.org/index.php/systemd-timesyncd

Right.  So systemd uses an entirely different strategy for time
adjustment than sysvinit did, in addition to which it comes with a
built-in NTP client (disabled by default on Debian, for whatever
reason) that can replace standalone NTP daemons.  Great.  Nice
features but they are badly documented, from the perspective of
systems that were migrated from sysvinit.

At this point, I'm tempted to reassign this bug to release-notes,
since the migration on Debian from sysvinit as default to systemd as
default should have explained this, including the justification for
not enabling the built-in NTP client by default.

Martin-Éric



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 Release: stretch/sid
  APT prefers testing
  APT policy: (1001, 'testing'), (1001, 'stable')
Architecture: i386 (i586)

Kernel: Linux 4.6.0-1-686 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages util-linux depends on:
ii  libblkid1  2.28-5
ii  libc6  2.22-11
ii  libfdisk1  2.28-5
ii  libmount1  2.28-5
ii  libncursesw5   6.0+20160319-1
ii  libpam0g   1.1.8-3.3
ii  libselinux12.5-3
ii  libsmartcols1  2.28-5
ii  libsystemd0230-2
ii  libtinfo5  6.0+20160319-1
ii  libudev1   230-2
ii  libuuid1   2.28-5
ii  zlib1g 1:1.2.8.dfsg-2+b1

util-linux recommends no packages.

Versions of packages util-linux suggests:
ii  dosfstools  4.0-2
ii  kbd 2.0.3-2
pn  util-linux-locales  

- -- Configuration Files:
/etc/default/hwclock changed:
HWCLOCKACCESS=yes


- -- debconf information excluded

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXcRxGAAoJEK4fgnfEtNe2nN8P/RGiTyAgVpJAE9do7KqZ5sLd
CkiL20w9UdFPFw5YQ8gvCqOFFyCLm5rQH6zoUT5qZsKui2BwOwyZ6FQe8YUVlIKk
o87SITuJXa8bTeXXp9OFy1UwcWkaBHLCOmlzJ4SVLr8dLTLjWBpmyJO62hdjqYC3
dR01ykPE8zgcSA5sGASzb/JJyQlWu2woBISRiTTkV+yXW+x3uNhnzsH9WgPiy1Q4
F+aPzsZDNiEpY+aLB22101g20DpaNl/kNpydN0WJCHuulwrFDPBic6j0c+zFDUrV
ZdAdmzYP2henhQPGcAMaB222RHmY2gVC/gxh0C6JhCMBpHon3XcMdf5H49cvklBT
03HzHAuRl2irf3HNJ/ykZ3HFUrvK16etJAS3Jvi0RrXv4ED1elRwGnEGi5ubJ3wV
rUyZeln6e7DuUqaYFtazIqKS2JjiqOtOeOkfC5vh5B6LSPyxgvUQqtOKkSmGTrcn
Xvna1pMugKo+Xma+lXQ5ivN76N+A97qVIn8Z7iaxJIBeF6TlEG9MQZYp2FhWkHU0
bsZ0/YFp/0W20XJY514YPtF8a1l+/aKG5G7RBmVy9z+quH6PkQ/cT+1k5n0hw7Sp
+rUJ9mmWJytSC5lyrJbF+UmjDmWV2NGVCD4OmRJyudLX6LhOOruqZIbpVBfEFv/8
QSvO3jqyHWwbk35qzbwN
=53CV
-END PGP SIGNATURE-



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 package cups-browsed (--configure):
 subprocess installed post-installation script returned error exit status 5
Errors were encountered while processing:
 cups-browsed


- -- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (1001, 'testing'), (1001, 'stable')
Architecture: i386 (i586)

Kernel: Linux 4.5.0-2-686 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cups-browsed depends on:
ii  init-system-helpers  1.34
ii  libavahi-client3 0.6.32~rc+dfsg-1
ii  libavahi-common3 0.6.32~rc+dfsg-1
ii  libavahi-glib1   0.6.32~rc+dfsg-1
ii  libc62.22-11
ii  libcups2 2.1.3-6
ii  libglib2.0-0 2.48.1-1
ii  libldap-2.4-22.4.42+dfsg-2+b2

Versions of packages cups-browsed recommends:
ii  avahi-daemon  0.6.32~rc+dfsg-1

cups-browsed suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXYnaHAAoJEK4fgnfEtNe2N68P/0ajjOZUIMVyffNMv80OxTV7
/rqlXcP0jxxdevxtrkUjs5nuYUZvPjd9+3dKi0GnfcZim1vR+CStyitEmhptoV0O
E4MkRZR06XbCfDdakO1nA2gSoBzqEKpy2jrIkdU1WLDrhue6jB+Q1/r6L4NhImDf
OUe9WMY5ZVq0FCIa9lZGzVhmTBjwcc8bBWNBhEKCIjZHKd7HDvWnyPw5a75uoSOx
1Y/oC5z0BWfMKXMAycAR0GVNIPorEnqGqGdfRr66XZiD1vcv9p7/Ynb/wEbcOptH
fwcSEh2vcsh/q7C8hD32FyUfNj0zI2mN6WBr6L1tvgYNW4svwejLISdGQdKy14BB
tA5Hipaag8EWy8ZXllpSk9o7eZl+svPB0SbLsKCGgzGvYeN/k+nMZM+2fQJQXdfj
0fV3POLqhRZqhxWkF8aqNcu/SoZncHKvF2ooxKvxyq215N3Oc0JHhZmnb/doXONC
8TENBrukctlcWzxuoLvrlPsCbXE4gnYBGxKFtCRUczbLlNtRbVUGFb0V536GSRZh
tQ2sbFKNIO7DSJuxGeR3cTsfxQmz2V67cIVAhkc//K16efhyMxyVFSlrX+fwQ1DH
p43jjxKg0ZEM2Us/s1jFzLF4/au1ny6zgjJKR3G0+5PwtyJdOY2K48W7j94FJrY6
QsgE0CV1vWMP9hn0Mh1o
=oQU2
-END PGP SIGNATURE-



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, 
regardless of which ones any given site needs. On other OS platforms e.g. 
Mac/Windows, the smartcard support layer can be polled for a specific card 
slot's PIN on the fly.  We need this implemented on OpenSC too.

-- System Information:
Debian Release: 8.5
  APT prefers stable
  APT policy: (1001, 'stable'), (500, 'stable-updates')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages opensc depends on:
ii  libc6  2.19-18+deb8u4
ii  libreadline6   6.3-8+b3
ii  libssl1.0.01.0.1t-1+deb8u2
ii  opensc-pkcs11  0.14.0-2

opensc recommends no packages.

opensc suggests no packages.

-- Configuration Files:
/etc/opensc/opensc.conf changed:
app default {
# Amount of debug info to print
#
# A greater value means more debug info.
# Default: 0
#
debug = 0;
# The file to which debug output will be written
#
# Special values 'stdout' and 'stderr' are recognized.
# Default: stderr
#
# debug_file = /tmp/opensc-debug.log
# Re-open debug file  (used in WIN32)
#
# In Windows, file handles can not be shared between DLL-s,
#  each DLL has a separate file handle table.
# For that reason reopen debug file before every debug message.
#
# Default: true
# reopen_debug_file = false;
# PKCS#15 initialization / personalization
# profiles directory for pkcs15-init.
# Default: /usr/share/opensc
#
# profile_dir = /usr/share/opensc;
# Paranoid memory allocation.
#
# If set to 'true', then refuse to continue when locking of non-pageable
# memory fails. This can cause subtle failures but is more secure when
# you have a swap disk.
# Default: false
#
# paranoid_memory = false;
# Enable default card driver
# Default card driver is explicitely enabled for the 'opensc-explorer' 
and 'opensc-tool'.
#
# Default: false
# enable_default_driver = true;
# CT-API module configuration.
reader_driver ctapi {
# module /usr/lib/i386-linux-gnu/libtowitoko.so {
# CT-API ports:
# 0..3  COM1..4
# 4 Printer
# 5 Modem
# 6..7  LPT1..2
# ports = 0;
# }
}
# The following section shows definitions for PC/SC readers.
reader_driver pcsc {
# Limit command and response sizes.
# Default: n/a
# max_send_size = 255;
# max_recv_size = 256;
#
# Connect to reader in exclusive mode?
# Default: false
# connect_exclusive = true;
#
# What to do when disconnecting from a card (SCardDisconnect)
# Valid values: leave, reset, unpower.
# Default: reset
# disconnect_action = unpower;
#
# What to do at the end of a transaction (SCardEndTransaction)
# Valid values: leave, reset, unpower.
# Default: leave
# transaction_end_action = reset;
#
# What to do when reconnection to a card (SCardReconnect)
# Valid values: leave, reset, unpower.
# Note that this affects only the internal reconnect (after a 
SCARD_W_RESET_CARD).
# A forced reset via sc_reset() always does a full powerup.
# Default: leave
# reconnect_action = reset;
#
# Enable pinpad if detected (PC/SC v2.0.2 Part 10)
# Default: true
# enable_pinpad = false;
#
# Use specific pcsc provider.
# Default: libpcsclite.so.1
# provider_library = libpcsclite.so.1
}
# Options for OpenCT support
reader_driver openct {
# Virtual readers to allocate.
# Default: 2
# readers = 5;
#
# Limit command and response sizes.
# Default: n/a
# max_send_size = 255;
# max_recv_size = 256;
};
# What card drivers to load at start-up
#
# 

  1   2   3   4   5   6   7   8   9   10   >