Bug#900259: mate-tweak: Colors in marco-compton are weird

[Erik de Castro Lopo]

Package: mate-tweak
Version: 18.04.16-1
Severity: normal

Dear Maintainer,

Had been experiencing some flakiness in my video display and then the
mounse and keyboard locked up. I sshed in from another machine and tried
'sudo init 6', but that lock up the terminal session. Finally I resorted
to a hard reset.

On reboot, the lightdm login screen was fine, but when I logged in all
the mate components (top bar, mate terminal etc) were being dimplayed
in weird colours (reds and yellows, it looked like an indexed 256 colour
pallete). 

After some considerable debugging I found that switching from the 
marco-compton window manager back to just marco fixed everything. To make
sure this is what it was, I switched back to the compton version which
again had weird colours and then back to marco which fixed the issue.

IMHO, marco-compton should either be fixed or deprecated.


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

Kernel: Linux 4.16.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mate-tweak depends on:
ii  dconf-cli  0.28.0-2
ii  gir1.2-gtk-3.0 3.22.29-3
ii  gir1.2-notify-0.7  0.7.7-3
ii  mate-panel 1.20.1-3
ii  mesa-utils 8.4.0-1
ii  python33.6.5-3
ii  python3-gi 3.28.2-1
ii  python3-pkg-resources  39.1.0-1
ii  python3-psutil 5.4.2-1
ii  python3-setproctitle   1.1.10-1+b1
ii  x11-xserver-utils  7.7+8

Versions of packages mate-tweak recommends:
ii  compton0.1~beta2+20150922-1
ii  mate-indicator-applet  1.20.0-1

Versions of packages mate-tweak suggests:
pn  indicator-application  
pn  indicator-messages 
pn  indicator-power
pn  indicator-session  
pn  indicator-sounds   

-- no debconf information

Bug#900258: shadowsocks-libev: Drop apg/pwgen from Depends

[Shengjing Zhu]

Source: shadowsocks-libev
Severity: wishlist
Tags: patch

Dear Maintainer,

This package depends apg or pwgen to generate an initial password, but I
don't think it's needed to use an extra program.

perl-base is an Essential package, so every Debian based system has perl
interpreter. You can just use perl's rand function to do this. So that
this package has less depends and I can reduce the install size.

passwd=$(perl -e 'print map{("a".."z","A".."Z",0..9)[int(rand(62))]}(1..12)')

This snippet is taken from mysql-5.7 package.
diff -Nru shadowsocks-libev-3.1.3+ds/debian/changelog 
shadowsocks-libev-3.1.3+ds/debian/changelog
--- shadowsocks-libev-3.1.3+ds/debian/changelog 2018-03-21 12:15:49.0 
+0800
+++ shadowsocks-libev-3.1.3+ds/debian/changelog 2018-05-28 13:29:05.0 
+0800
@@ -1,3 +1,10 @@
+shadowsocks-libev (3.1.3+ds-2.1) UNRELEASED; urgency=medium
+
+  * Drop apg and pwgen from Depends, use perl rand to generate
+password.
+
+ -- Shengjing Zhu   Mon, 28 May 2018 13:29:05 +0800
+
 shadowsocks-libev (3.1.3+ds-2) unstable; urgency=medium
 
   [ Sync from 3.1.3+ds-1ubuntu1 ]
diff -Nru shadowsocks-libev-3.1.3+ds/debian/control 
shadowsocks-libev-3.1.3+ds/debian/control
--- shadowsocks-libev-3.1.3+ds/debian/control   2018-03-21 12:09:19.0 
+0800
+++ shadowsocks-libev-3.1.3+ds/debian/control   2018-05-28 13:29:05.0 
+0800
@@ -26,7 +26,6 @@
 Breaks: shadowsocks (<< 1.5.3-2)
 Architecture: any
 Depends:
- apg | pwgen,
  libcap2-bin [linux-any],
  lsb-base (>= 3.0-6),
  ${misc:Depends},
diff -Nru shadowsocks-libev-3.1.3+ds/debian/shadowsocks-libev.postinst 
shadowsocks-libev-3.1.3+ds/debian/shadowsocks-libev.postinst
--- shadowsocks-libev-3.1.3+ds/debian/shadowsocks-libev.postinst
2018-03-19 00:38:32.0 +0800
+++ shadowsocks-libev-3.1.3+ds/debian/shadowsocks-libev.postinst
2018-05-28 13:29:05.0 +0800
@@ -32,14 +32,7 @@
echo "setcap not installed; ss-* will only be runnable 
by root."
fi
if [ ! -f /etc/shadowsocks-libev/config.json ]; then
-   set +e
-   pathfind apg
-   if [ $? -eq 0 ]; then
-   passwd=$(apg -n 1 -M ncl)
-   else
-   passwd=$(pwgen 12 1)
-   fi
-   set -e
+   passwd=$(perl -e 'print 
map{("a".."z","A".."Z",0..9)[int(rand(62))]}(1..12)')
mkdir -p /etc/shadowsocks-libev
sed "s/barfoo!/$passwd/" 
/usr/share/shadowsocks-libev/config.json \
> /etc/shadowsocks-libev/config.json


signature.asc
Description: PGP signature

Bug#900257: ITP: sphinxcontrib-asyncio -- sphinx extension to support coroutines in markup

[Diane Trout]

Package: wnpp
Severity: wishlist
Owner: Diane Trout 

* Package name: sphinxcontrib-asyncio
  Version : 0.2.0
  Upstream Author : Andrew Svetlov 
* URL : https://github.com/aio-libs/sphinxcontrib-asyncio
* License : Apache 2.0
  Programming Lang: Python
  Description : sphinx extension to support coroutines in markup

 Sphinx extension for adding asyncio-specific markups
 such as cofunction or async-for
 .
 This contains the Python 3 version.

This is a dependency to build the documentation for hangups, pypi (and
librar.io) suggest that several other libraries like aiohttp and aiopg also use
this library for their documentation.
https://libraries.io/pypi/sphinxcontrib-asyncio/usage

I was planning on maintaining it in the Debian Python Modules Team.

Diane

Bug#900256: RFS: deepin-image-viewer/1.2.22-1

[Yanhao Mo]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "deepin-image-viewer"

* Package name: deepin-image-viewer
  Version : 1.2.22-1
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://github.com/linuxdeepin/deepin-image-viewer
* License : GPL-3+
  Section : graphics

It builds those binary packages:

  deepin-image-viewer - Image Viewer for Deepin Desktop Environment

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/deepin-image-viewer

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-image-viewer/deepin-image-viewer_1.2.22-1.dsc

More information about hello can be obtained from 
https://salsa.debian.org/pkg-deepin-team/deepin-image-viewer

Changes since the last upload:
  * New upstream release.

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#900255: RFS: deepin-menu/3.3.4-1

[Yanhao Mo]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "deepin-menu"

 * Package name: deepin-menu
   Version : 3.3.4-1
   Upstream Author : Deepin Technology Co., Ltd.
 * License : GPL-3+
   Section : x11

It builds those binary packages:

deepin-menu - Deepin menu service

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/deepin-menu


Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-menu/deepin-menu_3.3.4-1.dsc

More information about hello can be obtained from 
https://salsa.debian.org/pkg-deepin-team/deepin-menu

Changes since the last upload:
  * New upstream release.

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#899605: [Pkg-mactel-devel] Bug#899658: pommed/macfanctld: Invalid maintainer address pkg-mactel-de...@lists.alioth.debian.org

[Thibaut Paumard]

Le 28/05/2018 à 02:04, Nobuhiro Iwamatsu a écrit :

Hi, Thibaut.

I am planning to organize it with tracker.d.o.
Do you think about this?
https://tracker.debian.org/teams/pkg-mactel-devel/

Best regards,
   Nobuhiro



Great, go ahead.

I don't have access to a mactel for the moment, so I will not be able to 
participate in the forseable future. I've seen that you have already 
uploaded macfanctld, can you take care also of pommed?


Kind regards, Thibaut.


2018-05-26 21:01 GMT+09:00 Thibaut Paumard :

control: severity -1 important


Le 24/05/2018 à 10:38, Thibaut Paumard a écrit :


Thanks,

I've asked for the migration of pkg-mactel-de...@lists.alioth.debian.org.

Regards, Thibaut.




Since this is only a temporary solution, we should still think of choosing
another address with the next upload.

Regards, Thibaut.

Bug#900253: nslcd: disabling ppolicy breaks authentication

[duck]

Package: nslcd
Version: 0.9.7-2
Severity: important


Quack,

I was annoyed by slapd warning me about "unrecognized control", and as 
we do not use ppolicy I decided to set "pam_authc_ppolicy no". I 
realized this setting breaks PAM authentication on my system. 
nslcd/authc reports "Unknown error" when I try to authenticate.


From what I can see in the source code this error only applies to 
ppolicy processing ('compat/ldap_passwordpolicy_err2txt.c'). If I'm not 
mistaken the authenticate() function in 'pynslcd/pam.py' should check 
for 'cfg->pam_authc_ppolicy' before binding with a 
'PasswordPolicyControl()' unconditionally.


Regards.


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

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=C 
(charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nslcd depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.61
ii  libc6  2.24-11+deb9u3
ii  libgssapi-krb5-2   1.15-1+deb9u1
ii  libldap-2.4-2  2.4.44+dfsg-5+deb9u1
ii  lsb-base   9.20161125

Versions of packages nslcd recommends:
ii  bind9-host [host]   1:9.10.3.dfsg.P4-12.3+deb9u4
ii  ca-certificates 20161130+nmu1
ii  ldap-utils  2.4.44+dfsg-5+deb9u1
ii  libnss-ldapd [libnss-ldap]  0.9.7-2
ii  libpam-ldapd [libpam-ldap]  0.9.7-2
ic  nscd2.11.2-2
pn  nslcd-utils 

Versions of packages nslcd suggests:
pn  kstart  

-- debconf information excluded

--
Marc Dequènes

Bug#900254: reportbug: suggests upgrading to non-stable version

[duck]

Package: reportbug
Version: 7.1.7+deb9u1
Severity: important


Quack,

I'm using stable, with occasional backports. I just opened a BR using 
reportbug and here is its output:


Your version (0.9.7-2) of nslcd appears to be out of date.
The following newer release(s) are available in the Debian archive:
  testing: 0.9.9-1
  unstable: 0.9.9-1
Do you still want to file a report [y|N|q|?]? y

It really make me feels I'm doing something wrong and should really 
upgrade before reporting anything. This is obviously wrong to suggest 
our users to switch to an unreleased suite.


If I proceed reportbug is able to get my APT configuration right:

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

So I guess this recommendation should be disabled when the APT policy 
contains 'stable' (just a guess, might be more complex than it seems).


Regards.
\_o<

--
Marc Dequènes

Bug#900252: Gnome hangs when switching keyboard layout

[Lumin]

Package: gnome-shell
Version: 3.28.2-1
Severity: important

I have two keyboard layouts, English (US) and German (DE), which are
configured via gnome control center -> region and language -> input
sources.

When switching the keyboard layout between English and German,
the gnome shell will hang at a small probability. I don't know
how to manually trigger that, but it happens occasionally.

This problem should be set to imporant because it may be annoying for
multi-lingual users.

Bug#900203: guile-2.2 FTCBFS for mipsel: In procedure load-thunk-from-memory: No such file or directory

[Helmut Grohne]

On Sun, May 27, 2018 at 03:04:43PM -0500, Rob Browning wrote:
> What's the top-level debian/rules invocation/environment?  i.e. how
> would I reproduce this?

There are a number of ways to reproduce:
 * pbuilder --host-arch mipsel guile-2.2_*.dsc
 * sbuild --host=mipsel --add-depends=libc-dev,libstdc++-dev
   --profiles=cross,nocheck
   (That --add-depends is necessary, because #815172.)
 * DEB_BUILD_PROFILES="cross nocheck" DEB_BUILD_OPTIONS=nocheck
   dpkg-architecture -amipsel -c dpkg-buildpackage -B

Hope this helps.

Helmut

Bug#900251: Please don't compress the mutt examples

[Lumin]

Package: mutt
Version: 1.10.0-1
Severity: important

Dear Mutt maintainers,

Please don't compress the mutt config examples, because I guess some
users have directly sourced these files in their personal config files.
At least I did so.

After upgrading from mutt 1.9.5 to 1.10.0, some files turned into
compressed format, e.g.

  /usr/share/doc/mutt/examples/gpg.rc  -->  gpg.rc.gz

It broke my mutt config file. So I have to make corresponding changes:

   # Import GnuPG
  -source /usr/share/doc/mutt/examples/gpg.rc
  +source "gzip -c -d /usr/share/doc/mutt/examples/gpg.rc |"

Thanks.

Bug#900250: cinnamon: Cinammon is crashing constantly after a regular update

[Tamas Pal]

Package: cinnamon
Version: 3.2.7-4
Severity: normal

Dear Maintainer,
After a regular update and upgrade cinnamon is crashing constantly in my lenovo
G50-45 laptop. How to fix it ?

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



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

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cinnamon depends on:
ii  caribou  0.4.21-1+b1
ii  cinnamon-common  3.2.7-4
ii  cinnamon-control-center  3.2.1-3
ii  cinnamon-desktop-data3.2.4-4
ii  cinnamon-screensaver 3.2.13-4
ii  cinnamon-session 3.2.0-4
ii  cinnamon-settings-daemon 3.2.1-3
ii  cjs  3.2.0-3
ii  cups-pk-helper   0.2.6-1+b1
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gir1.2-accountsservice-1.0   0.6.43-1
ii  gir1.2-caribou-1.0   0.4.21-1+b1
ii  gir1.2-clutter-1.0   1.26.0+dfsg-3
ii  gir1.2-cmenu-3.0 3.2.0-3
ii  gir1.2-cogl-1.0  1.22.2-2
ii  gir1.2-cvc-1.0   3.2.4-4
ii  gir1.2-gdkpixbuf-2.0 2.36.5-2+deb9u2
ii  gir1.2-gkbd-3.0  3.22.0.1-1+b1
ii  gir1.2-glib-2.0  1.50.0-1+b1
ii  gir1.2-gnomedesktop-3.0  3.22.2-1
ii  gir1.2-gtk-3.0   3.22.11-1
ii  gir1.2-gtkclutter-1.01.8.2-2
ii  gir1.2-javascriptcoregtk-3.0 2.4.11-3
ii  gir1.2-keybinder-3.0 0.3.1-1
ii  gir1.2-meta-muffin-0.0   3.2.1-2
ii  gir1.2-networkmanager-1.01.6.2-3
ii  gir1.2-notify-0.70.7.7-2
ii  gir1.2-pango-1.0 1.40.5-1
ii  gir1.2-polkit-1.00.105-18
ii  gir1.2-soup-2.4  2.56.0-2+deb9u1
ii  gir1.2-upowerglib-1.00.99.4-4+b1
ii  gir1.2-xapp-1.0  1.0.2-1
ii  gkbd-capplet 3.22.0.1-1+b1
ii  gnome-backgrounds3.22.1-1
ii  gnome-themes-standard3.22.2-2
ii  gsettings-desktop-schemas3.22.0-1
ii  iso-flags-png-320x2401.0.1-1
ii  libatk-bridge2.0-0   2.22.0-2
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u3
ii  libcairo21.14.8-1
ii  libcinnamon-menu-3-0 3.2.0-3
ii  libcjs0  3.2.0-3
ii  libclutter-1.0-0 1.26.0+dfsg-3
ii  libcogl-pango20  1.22.2-2
ii  libcogl-path20   1.22.2-2
ii  libcogl201.22.2-2
ii  libcroco30.6.11-3
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libgirepository-1.0-11.50.0-1+b1
ii  libgl1-mesa-glx [libgl1] 13.0.6-1+b2
ii  libglib2.0-0 2.50.3-2
ii  libglib2.0-bin   2.50.3-2
ii  libgstreamer1.0-01.10.4-1
ii  libgtk-3-0   3.22.11-1
ii  libjs-jquery 3.1.1-2
ii  libmozjs-24-024.2.0-5.1+b2
ii  libmuffin0   3.2.1-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libstartup-notification0 0.12-4+b2
ii  libx11-6 2:1.6.4-3
ii  libxfixes3   1:5.0.3-1
ii  libxml2  2.9.4+dfsg1-2.2+deb9u2
ii  mesa-utils   8.3.0-3
ii  muffin   3.2.1-2
ii  nemo 3.2.2-3
ii  policykit-1-gnome0.105-6
ii  python 

Bug#900249: general: after I just regularly updated debian stretch in my lenovo G-50-45 laptop it's crashing conatcntly saying Cinnamon is running on fallback mode before upgrade it was working fine.

[Tamas Pal]

Package: general
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



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

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#900248: nvidia-driver: update to 390.59 breaks direct rendering

[Norbert Preining]

Package: nvidia-driver
Version: 390.59-1
Severity: grave
Justification: renders package unusable

Update to the current version in sid breaks direct rendering, my
system now uses the software pipe:
$ glxinfo | grep OpenGL
...
OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
...

Looking at the Xorg.0.log I see
[12.045] (EE) NVIDIA(0): Failed to initialize the GLX module; please check 
in your X
[12.045] (EE) NVIDIA(0): log file that the GLX module has been loaded 
in your X
[12.045] (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX 
module.  If
[12.045] (EE) NVIDIA(0): you continue to encounter problems, Please try
[12.045] (EE) NVIDIA(0): reinstalling the NVIDIA driver.

So then I did as root
# # update-glx --config nvidia
There is only one alternative in link group nvidia (providing 
/usr/lib/nvidia/nvidia): /usr/lib/nvidia/current
Nothing to configure.
Processing triggers for glx-alternative-nvidia (0.8.3) ...
Processing triggers for update-glx (0.8.3) ...
Processing triggers for glx-alternative-nvidia (0.8.3) ...
Processing triggers for libc-bin (2.27-3) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.16.11
#

and even after reboot nothing has changed.

Best

Norbert


-- Package-specific info:
uname -a:
Linux bulldog 4.16.11 #50 SMP Thu May 24 12:35:27 JST 2018 x86_64 GNU/Linux

/proc/version:
Linux version 4.16.11 (norbert@bulldog) (gcc version 7.3.0 (Debian 7.3.0-19)) 
#50 SMP Thu May 24 12:35:27 JST 2018

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  9 22:33:42 PDT 
2018
GCC version:  gcc version 7.3.0 (Debian 7.3.0-19) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107 [GeForce GTX 
1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:11bf]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.909202] pci :01:00.0: vgaarb: setting as boot VGA device
[0.909202] pci :01:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.909202] pci :01:00.0: vgaarb: bridge control possible
[0.909202] vgaarb: loaded
[1.309924] fb0: EFI VGA frame buffer device
[1.470133] Linux agpgart interface v0.103
[1.911353] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[2.728879] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14
[2.730912] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15
[2.733010] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input16
[3.419570] nvidia: loading out-of-tree module taints kernel.
[3.420013] nvidia: module license 'NVIDIA' taints kernel.
[3.429869] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 245
[3.430493] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[3.430987] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  
9 22:33:42 PDT 2018 (using threaded interrupts)
[3.463770] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for 
UNIX platforms  390.59  Wed May  9 21:59:27 PDT 2018
[3.486333] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver
[3.486813] [drm] Initialized nvidia-drm 0.0.0 20160202 for :01:00.0 on 
minor 0
[   12.697265] nvidia-modeset: Allocated GPU:0 
(GPU-ae45f56a-df50-cbc7-737d-a20dd48d7bdd) @ PCI::01:00.0
[   12.843050] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLAB object 'nvidia_stack_cache' (offset 11440, size 3)!
[   12.843056] Modules linked in: ip6table_filter ip6_tables xt_conntrack 
devlink tun iptable_filter nf_nat nf_conntrack br_netfilter bridge stp llc 
pci_stub overlay vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) 
scsi_transport_iscsi joydev binfmt_misc x86_pkg_temp_thermal kvm_intel uvcvideo 
videobuf2_vmalloc hid_generic videobuf2_memops kvm videobuf2_v4l2 irqbypass 
videobuf2_common crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_usb_audio videodev pcbc snd_usbmidi_lib media snd_rawmidi usbhid hid 
aesni_intel crypto_simd glue_helper cryptd serio_raw pcspkr iTCO_wdt mxm_wmi 
iTCO_vendor_support mei_me sg intel_pch_thermal mei acpi_pad evdev ext4 crc16 
mbcache jbd2 fscrypto nvidia_drm(PO) drm_kms_helper drm loop nvidia_modeset(PO) 
nvidia(PO) ipmi_devintf ipmi_msghandler i2c_dev sunrpc parport_pc
[   12.843186]  os_memcpy_to_user+0x21/0x40 [nvidia]
[   12.843279]  _nv009383rm+0xbf/0xe0 [nvidia]
[   12.843358]  ? _nv028084rm+0x79/0x90 [nvidia]
[   

Bug#900247: gpg-check-pattern.1: Some formatting changes in the manual

[Bjarni Ingi Gislason]

Package: gpg-agent
Version: 2.2.5-1
Severity: minor
Tags: patch

Dear Maintainer,

   * What led up to the situation?

  Warning from "groff":

:19 (macro BR): only 1 argument, but more are expected

Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z 

  [ "test-groff" is a developmental version of "groff" ]

###

  Summary of changes:

Use correct font for "options" (denotes variable text)

Split long lines (> 80) (and make only the first word bold)

Change a two-fonts macro to an one-font macro for a singular argument

###

  Details:

Test nr. 16:

Use the correct macro for the font change of one argument.
Split a punctuation mark from the only argument if one is there

19:.BR \-\-check

#

Test nr. 42:

Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause.

gpg-check-pattern.1: line 12length 90
.B gpg\-check\-pattern checks a passphrase given on stdin against a specified 
patternfile.

#

  Patch:

--- gpg-check-pattern.1 2018-02-22 22:20:18.0 +
+++ gpg-check-pattern.1.new 2018-05-28 00:57:21.0 +
@@ -5,18 +5,19 @@ gpg-check-pattern \- Check a passphrase
 
 .SH SYNOPSIS
 .B gpg\-check\-pattern
-.RB [ options ]
+.RI [ options ]
 .I patternfile
 
 .SH DESCRIPTION
-.B gpg\-check\-pattern checks a passphrase given on stdin against a specified 
patternfile.
+.B gpg\-check\-pattern
+checks a passphrase given on stdin against a specified patternfile.
 
 .SH OPTIONS
 .TP
 .BR \-v ", " \-\-verbose
 Produce verbose output
 .TP
-.BR \-\-check
+.B \-\-check
 run only a syntax check on the patternfile
 .TP
 .BR \-0 ",  " \-\-null


-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.88-1-u1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gpg-agent depends on:
ii  gpgconf   2.2.5-1
ii  libassuan02.5.1-2
ii  libc6 2.27-3
ii  libgcrypt20   1.8.2-2
ii  libgpg-error0 1.31-1
ii  libnpth0  1.5-3
ii  pinentry-gtk2 [pinentry]  1.1.0-1+b1

Versions of packages gpg-agent recommends:
ii  gnupg  2.2.5-1

Versions of packages gpg-agent suggests:
pn  dbus-user-session  
pn  libpam-systemd 
pn  pinentry-gnome3
pn  scdaemon   

-- no debconf information

-- 
Bjarni I. Gislason

Bug#896934: diffoscope: decode monitor EDID data to text

[Paul Wise]

On Sat, 2018-05-26 at 08:37 +0100, Chris Lamb wrote:

> Is this something you think you can drive or should someone take
> over..?

If someone wants to take over, please feel free.
Otherwise I'll get to it at some point.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#900165: calibre: segfault

[Norbert Preining]

tags 900165 + moreinfo unreproducible
severity 900165 important
thanks

> File "/usr/lib/calibre/duktape/__init__.py", line 15, in 
> import dukpy
> ImportError: No module named dukpy

Interesting, I have 3.24, but was running 3.23 of course, and never saw
this behavior. Do you have any special initialization code or setup?
Here I cannot reproduce this behavior at all.

Best

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#900040: dpkg-trigger.1: Some formatting fixes in the manual

[Guillem Jover]

Hi!

On Fri, 2018-05-25 at 00:41:59 +, Bjarni Ingi Gislason wrote:
> Package: dpkg
> Version: 1.19.0.5+b1
> Severity: minor
> Tags: patch

>   Summary:
> 
>   Change ".BR " to ".B "

Good.

>   Protect ellipis on both sides, "\&...\&"

See other mail, why?

>   Know the difference between "abc..." and "abc ...".
>   See a manual of style.

See other mail, seems wrong.

>   Use macros instead of font escapes "\f..."

See other mail, makes possible conversion more noisy.

>   Begin each sentence on a new line

See other mail, not for otherwise untouched lines.

Thanks,
Guillem

Bug#900035: dpkg-split.1: Some formatting fixes in the manual

[Guillem Jover]

Hi!

On Thu, 2018-05-24 at 23:35:11 +, Bjarni Ingi Gislason wrote:
> Package: dpkg
> Version: 1.19.0.5+b1
> Severity: minor
> Tags: patch

>   Summary:
> 
>   Change '.BR "one argument"' to '.B "one argument"'

Good.

>   Fix one spelling mistake (queueing)

Good.

>   Add a left italic correction (instead of using a macro)

Ok I guess, will probably be irrelevant in POD.

>   Protect ellipsis on both ends (\&...\&)

See other mail, why?

>   Know the difference between "abc..." and "abc ..."
>   See a style guide

See other mail, seems wrong.

>   Let new sentences begin on a new line.

See other mail, not for otherwise untouched lines.

Thanks,
Guillem

Bug#900033: dpkg-deb.1: Some fixes in the manual

[Guillem Jover]

On Mon, 2018-05-28 at 02:47:40 +0200, Guillem Jover wrote:
> On Thu, 2018-05-24 at 22:34:36 +, Bjarni Ingi Gislason wrote:
> >   Begin each sentence on a new line (or use two spaces between them,
> > which is not recommended as the text contains formatting commands).
> > See man-pages(7) [package "manpages"] and "info groff".
> 
> This is a somewhat controversial style dispute in general, and I find
> two spaces uglier. :) In addition vim seems to agree, and prints red
> on ".  " with syntax highlighting.

Let me clarify. I do not agree with the explicit two space after dot,
I've always found that to be rather ugly. OTOH I find the rationale
for splitting sentences on newline sound, because it reduces diff
changes as it requires less text reflowing. The fact that groff
considers that an implicit ".  " is then minor, although still
slightly annoying. :) Split lines still looks ugly and unnatural when
reading the source though, so I'm still not 100% sold on that one.

But I've only split lines for text I've added or changed, I don't
think touching existing text just for this is worth the diff noise.

Thanks,
Guillem

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

[Russell Mosemann]

 
Package: src:linux
Version: 4.16.5-1~bpo9+1
Severity: important


 
May 26 23:27:39 vhost004 kernel: qemu-system-x86: page allocation failure: 
order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO)
, nodemask=(null)
May 26 23:27:39 vhost004 kernel: qemu-system-x86 cpuset=emulator 
mems_allowed=0-1
May 26 23:27:39 vhost004 kernel: CPU: 2 PID: 7150 Comm: qemu-system-x86 
Tainted: G  I  4.16.0-0.bpo.1-amd64 #1 Debian 4.16.5-1~bpo9+1
May 26 23:27:39 vhost004 kernel: Hardware name: HP ProLiant DL380 G6, BIOS P62 
08/16/2015
May 26 23:27:39 vhost004 kernel: Call Trace:
May 26 23:27:39 vhost004 kernel:  dump_stack+0x5c/0x85
May 26 23:27:39 vhost004 kernel:  warn_alloc+0xfc/0x180
May 26 23:27:39 vhost004 kernel:  __alloc_pages_slowpath+0xded/0xe00
May 26 23:27:39 vhost004 kernel:  ? _cond_resched+0x16/0x40
May 26 23:27:39 vhost004 kernel:  __alloc_pages_nodemask+0x212/0x250
May 26 23:27:39 vhost004 kernel:  kmalloc_order+0x14/0x40
May 26 23:27:39 vhost004 kernel:  kmalloc_order_trace+0x1d/0xa0
May 26 23:27:39 vhost004 kernel:  kvm_dev_ioctl+0xb4/0x680 [kvm]
May 26 23:27:39 vhost004 kernel:  do_vfs_ioctl+0xa2/0x620
May 26 23:27:39 vhost004 kernel:  SyS_ioctl+0x74/0x80
May 26 23:27:39 vhost004 kernel:  do_syscall_64+0x6c/0x130
May 26 23:27:39 vhost004 kernel:  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
May 26 23:27:39 vhost004 kernel: RIP: 0033:0x7efc0b493dd7
May 26 23:27:39 vhost004 kernel: RSP: 002b:7ffc347a3e68 EFLAGS: 0246 
ORIG_RAX: 0010
May 26 23:27:39 vhost004 kernel: RAX: ffda RBX: ae01 
RCX: 7efc0b493dd7
May 26 23:27:39 vhost004 kernel: RDX:  RSI: ae01 
RDI: 000b
May 26 23:27:39 vhost004 kernel: RBP:  R08: 55cf715469b8 
R09: 0050
May 26 23:27:39 vhost004 kernel: R10: 0020 R11: 0246 
R12: 55cf7395a990
May 26 23:27:39 vhost004 kernel: R13: 0002 R14: 0120 
R15: 
May 26 23:27:39 vhost004 kernel: Mem-Info:
May 26 23:27:39 vhost004 kernel: active_anon:9353 inactive_anon:13039 
isolated_anon:0
  active_file:42309 inactive_file:958933 
isolated_file:0
  unevictable:16419 dirty:28554 writeback:0 
unstable:0
  slab_reclaimable:61294 
slab_unreclaimable:493294
  mapped:24247 shmem:9742 pagetables:5234 
bounce:0
  free:72657 free_pcp:0 free_cma:0
May 26 23:27:39 vhost004 kernel: Node 0 active_anon:21852kB 
inactive_anon:32808kB active_file:106820kB inactive_file:1963792kB 
unevictable:3580kB isolated(anon):0kB isolated(file):0kB mapped:39564kB 
dirty:26556kB writeback:0kB shmem:5500kB shmem_thp: 0kB shmem_pmdmapped: 0kB 
anon_thp: 0kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
May 26 23:27:39 vhost004 kernel: Node 1 active_anon:15560kB 
inactive_anon:19348kB active_file:62416kB inactive_file:1871940kB 
unevictable:62096kB isolated(anon):0kB isolated(file):0kB mapped:57424kB 
dirty:87660kB writeback:0kB shmem:33468kB shmem_thp: 0kB shmem_pmdmapped: 0kB 
anon_thp: 16384kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
May 26 23:27:39 vhost004 kernel: Node 0 DMA free:15892kB min:20kB low:32kB 
high:44kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB 
unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB 
kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB 
free_cma:0kB
May 26 23:27:39 vhost004 kernel: lowmem_reserve[]: 0 3486 30139 30139 30139
May 26 23:27:39 vhost004 kernel: Node 0 DMA32 free:126260kB min:5204kB 
low:8772kB high:12340kB active_anon:19824kB inactive_anon:30548kB 
active_file:103544kB inactive_file:1920600kB unevictable:576kB 
writepending:25004kB present:3643520kB managed:3577952kB mlocked:576kB 
kernel_stack:2768kB pagetables:9160kB bounce:0kB free_pcp:0kB local_pcp:0kB 
free_cma:0kB
May 26 23:27:39 vhost004 kernel: lowmem_reserve[]: 0 0 26653 26653 26653
May 26 23:27:39 vhost004 kernel: Node 0 Normal free:41688kB min:39784kB 
low:67076kB high:94368kB active_anon:1900kB inactive_anon:2344kB 
active_file:3276kB inactive_file:43192kB unevictable:3004kB writepending:1552kB 
present:27787264kB managed:27292884kB mlocked:3004kB kernel_stack:1576kB 
pagetables:400kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
May 26 23:27:39 vhost004 kernel: lowmem_reserve[]: 0 0 0 0 0
May 26 23:27:39 vhost004 kernel: Node 1 Normal free:106788kB min:45096kB 
low:76032kB high:106968kB active_anon:15336kB inactive_anon:19348kB 
active_file:62416kB inactive_file:1872512kB unevictable:62096kB 
writepending:87660kB present:31457276kB managed:30943772kB mlocked:62096kB 
kernel_stack:4792kB pagetables:11376kB bounce:0kB free_pcp:0kB local_pcp:0kB 
free_cma:0kB
May 26 23:27:39 vhost004 kernel: lowmem_reserve[]: 0 0 0 0 0
May 26 23:27:39 vhost004 kernel: Node 0 DMA: 1*4kB (U) 0*8kB 1*16kB (U) 

Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

[Russell Mosemann]

 
Package: src:linux
Version: 4.16.5-1~bpo9+1
Severity: important


 
 
 
May 27 00:48:35 vhost003 kernel: qemu-system-x86: page allocation failure: 
order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null)
May 27 00:48:35 vhost003 kernel: qemu-system-x86 cpuset=emulator 
mems_allowed=0-1
May 27 00:48:35 vhost003 kernel: CPU: 15 PID: 18064 Comm: qemu-system-x86 
Tainted: G  I  4.16.0-0.bpo.1-amd64 #1 Debian 4.16.5-1~bpo9+1
May 27 00:48:35 vhost003 kernel: Hardware name: HP ProLiant DL380 G6, BIOS P62 
08/16/2015
May 27 00:48:35 vhost003 kernel: Call Trace:
May 27 00:48:35 vhost003 kernel:  dump_stack+0x5c/0x85
May 27 00:48:35 vhost003 kernel:  warn_alloc+0xfc/0x180
May 27 00:48:35 vhost003 kernel:  ? _cond_resched+0x16/0x40
May 27 00:48:35 vhost003 kernel:  __alloc_pages_slowpath+0xded/0xe00
May 27 00:48:35 vhost003 kernel:  ? _cond_resched+0x16/0x40
May 27 00:48:35 vhost003 kernel:  __alloc_pages_nodemask+0x212/0x250
May 27 00:48:35 vhost003 kernel:  kmalloc_order+0x14/0x40
May 27 00:48:35 vhost003 kernel:  kmalloc_order_trace+0x1d/0xa0
May 27 00:48:35 vhost003 kernel:  kvm_dev_ioctl+0xb4/0x680 [kvm]
May 27 00:48:35 vhost003 kernel:  do_vfs_ioctl+0xa2/0x620
May 27 00:48:35 vhost003 kernel:  SyS_ioctl+0x74/0x80
May 27 00:48:35 vhost003 kernel:  do_syscall_64+0x6c/0x130
May 27 00:48:35 vhost003 kernel:  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
May 27 00:48:35 vhost003 kernel: RIP: 0033:0x7f5c3d754dd7
May 27 00:48:35 vhost003 kernel: RSP: 002b:7ffcf1b0e568 EFLAGS: 0246 
ORIG_RAX: 0010
May 27 00:48:35 vhost003 kernel: RAX: ffda RBX: ae01 
RCX: 7f5c3d754dd7
May 27 00:48:35 vhost003 kernel: RDX:  RSI: ae01 
RDI: 000b
May 27 00:48:35 vhost003 kernel: RBP:  R08: 55823c50e9b8 
R09: 0050
May 27 00:48:35 vhost003 kernel: R10: 0020 R11: 0246 
R12: 55823d408960
May 27 00:48:35 vhost003 kernel: R13: 0002 R14: 0120 
R15: 
May 27 00:48:35 vhost003 kernel: Mem-Info:
May 27 00:48:35 vhost003 kernel: active_anon:8688 inactive_anon:12407 
isolated_anon:0
  active_file:32533 inactive_file:764155 
isolated_file:0
  unevictable:16418 dirty:59304 writeback:1 
unstable:0
  slab_reclaimable:51961 
slab_unreclaimable:712568
  mapped:24577 shmem:10071 pagetables:4125 
bounce:0
  free:76640 free_pcp:0 free_cma:0
May 27 00:48:35 vhost003 kernel: Node 0 active_anon:22468kB 
inactive_anon:33036kB active_file:66776kB inactive_file:2209948kB 
unevictable:63768kB isolated(anon):0kB isolated(file):0kB mapped:76208kB 
dirty:114924kB writeback:0kB shmem:39584kB shmem_thp: 0kB shmem_pmdmapped: 0kB 
anon_thp: 14336kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
May 27 00:48:35 vhost003 kernel: Node 1 active_anon:12284kB 
inactive_anon:16592kB active_file:63356kB inactive_file:846672kB 
unevictable:1904kB isolated(anon):0kB isolated(file):0kB mapped:22100kB 
dirty:122292kB writeback:4kB shmem:700kB shmem_thp: 0kB shmem_pmdmapped: 0kB 
anon_thp: 0kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
May 27 00:48:35 vhost003 kernel: Node 0 DMA free:15892kB min:20kB low:32kB 
high:44kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB 
unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB 
kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB 
free_cma:0kB
May 27 00:48:35 vhost003 kernel: lowmem_reserve[]: 0 3486 30139 30139 30139
May 27 00:48:35 vhost003 kernel: Node 0 DMA32 free:122660kB min:5204kB 
low:8772kB high:12340kB active_anon:20984kB inactive_anon:31620kB 
active_file:65752kB inactive_file:2169296kB unevictable:59584kB 
writepending:105876kB present:3643520kB managed:3577952kB mlocked:59584kB 
kernel_stack:1696kB pagetables:7456kB bounce:0kB free_pcp:0kB local_pcp:0kB 
free_cma:0kB
May 27 00:48:35 vhost003 kernel: lowmem_reserve[]: 0 0 26653 26653 26653
May 27 00:48:35 vhost003 kernel: Node 0 Normal free:41880kB min:39784kB 
low:67076kB high:94368kB active_anon:1484kB inactive_anon:1416kB 
active_file:1024kB inactive_file:40752kB unevictable:4184kB writepending:9048kB 
present:27787264kB managed:27292884kB mlocked:4184kB kernel_stack:1640kB 
pagetables:268kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
May 27 00:48:35 vhost003 kernel: lowmem_reserve[]: 0 0 0 0 0
May 27 00:48:35 vhost003 kernel: Node 1 Normal free:126128kB min:45096kB 
low:76032kB high:106968kB active_anon:11932kB inactive_anon:16788kB 
active_file:62992kB inactive_file:846392kB unevictable:1904kB 
writepending:122296kB present:31457276kB managed:30943772kB mlocked:1904kB 
kernel_stack:5080kB pagetables:8776kB bounce:0kB free_pcp:0kB local_pcp:0kB 
free_cma:0kB
May 27 00:48:35 vhost003 kernel: lowmem_reserve[]: 0 0 0 0 0
May 27 

Bug#900033: dpkg-deb.1: Some fixes in the manual

[Guillem Jover]

Hi!

[ I've seen you have filed a different bug report for each man page
  you have checked/reviewed, but that might mean tons of bugs for lots
  of pages. Probably better to reuse one of this for further fixes, or
  this might get a bit out of control. :) ]

On Thu, 2018-05-24 at 22:34:36 +, Bjarni Ingi Gislason wrote:
> Package: dpkg
> Version: 1.19.0.5+b1
> Severity: minor
> Tags: patch

>   Warnings from "groff":
> 
> :133 (macro IR): only 1 argument, but more are expected
> :210 (macro BR): only 1 argument, but more are expected
> :279 (macro BR): only 1 argument, but more are expected
> 
> Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z 
> 
>   ["test-groff" is a developmental version of "groff"]

Ah, nice stuff. Thanks for trying to cleanup the markup, it's
always appreciated. :)

> ###
> 
>   Summary:

Some of these I do not agree with, and in addition might even make a
possible conversion to POD
()
I've been pondering about, more difficult. Some others might actually
make it easier, and some might be irrelevant, as pod2man does
unfortunately not care (such as the - and \- distinction).

>   Remove extra quotation mark (").

Good.

>   Use '\(en', not '\-' to denote a range of numbers.

Ok I guess, with POD we could encode it with E<>, or ignore it.

>   Protect an ellipsis on both sides, '\&...\&'.

Why do we need this?

>   Protect a full stop, exclamation mark, that is not an end of sentence.

Idem?

>   Know the difference between "abc..." and "abc ...".

This one seems wrong. In the cases I've seen changed, it applies to
command-line argument description, where "foo..." has a distinctive meaning
of repetition, so splitting it seems wrong.

>   Print a reverse solidus (\) with '\e', not '\\'.

Ok I guess. Although I think in POD we'd just use \\.

>   Use a macro 'I', 'IX', or 'XI' instead of escape requests, where the
> italic correction is too often missing in the text.

If this was being writen from scratch, then I guess, but given the
current text I think it makes little sense, and it makes the conversion
uglier. So I'd rather avoid it. Also if we wanted better markup I'd
rather consider switching from man to mdoc macros.

>   Begin each sentence on a new line (or use two spaces between them,
> which is not recommended as the text contains formatting commands).
> See man-pages(7) [package "manpages"] and "info groff".

This is a somewhat controversial style dispute in general, and I find
two spaces uglier. :) In addition vim seems to agree, and prints red
on ".  " with syntax highlighting.

> #
> 
> Test nr. 40:
> 
> Add a comma after "e.g." and "i.e." (man-pages(7) [package "manpages"]).
> 
> 251:members (i.e. \fBcontrol.tar\fP and \fBdata.tar\fP; since dpkg 1.17.6).

This probably needs to be done globally over the entire git repo's
contents.

Thanks,
Guillem

Bug#845297: problem in the cvs -> git conversion: commit messages truncated

[Paul Wise]

On Sun, May 27, 2018 at 11:58 PM, Laura Arjona Reina wrote:

> For example looking at the commit message for
> 1adf8ff0d235a7f1c310fd9e4268981e80a10cab
> at the end it looks truncated:
> """
> portuguese/security/2003/dsa-231.wml: 1.1 -> 1.2
> portuguese/security/2003/dsa-233.wml: 1.1 -> 1.2
> portuguese/sec
> """

This looks like it is truncated in the part that we are adding to the
CVS commit messages, which contains CVS revision numbers.

> If it solves the problem, we can add this to the documentation for the
> final conversion "howto". (If you know better solution, just tell).

Feel free to drop the addition of CVS revision numbers to commit
messages if the patch does not fix the issue.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#900236: tlmgr manpage: 32-bit OpenPGP key IDs

[Norbert Preining]

tags 900236 + pending
thanks

Hi Jakub,

> Please don't use 32-bit OpenPGP key IDs. It's computationally trivial to

Ok, I fixed this upstream. Will be in the next upload.

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#839046: [PATCH] Enable merged-/usr by default again now that dpkg-shlibdeps is fixed (Closes: #839046)

[Hideki Yamane]

On Sun, 27 May 2018 21:08:42 +0200
Raphael Hertzog  wrote:
> If anything your argument would mean that we should have different default
> for the --merged-usr flag for different release. This might indeed be
> important if we want to make sure that recent debootstrap do not introduce
> unexpected problems when building chroot for very old releases.

 Yes, I mean that.

-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#875311: Bug #875311: gedit: CVE-2017-14108: CPU consumption via crafted file

[Alan Coopersmith]

Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=791037

Bug#900088: dpkg-dev: dpkg-buildflags.man description of pie is a bit unclear

[Guillem Jover]

Hi!

On Fri, 2018-05-25 at 18:12:49 -0400, Michael Gilbert wrote:
> package: dpkg-dev
> severity: minor
> version: 1.19.0.5
> tag: patch

> I found the manpage a bit unclear when it comes to handling of the pie
> hardening option.  Attached is a proposed rewording.

Right, I was not really happy with that text, even when I wrote it!
Your proposal has some problems though, as it makes it look as if dpkg
knew when gcc has the support built-in, but this is just hardcoded,
and it misses some of the cases.

How about the attached patch? We can keep tuning it until it makes
more sense. :)

Thanks,
Guillem
diff --git i/man/dpkg-buildflags.man w/man/dpkg-buildflags.man
index a0a76ed53..7712c5576 100644
--- i/man/dpkg-buildflags.man
+++ w/man/dpkg-buildflags.man
@@ -390,18 +390,25 @@ above). The option cannot become enabled if \fBrelro\fP is not enabled.
 .
 .TP
 .B pie
-This setting (with no default since dpkg 1.18.23, and injected by default
-by gcc on the amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386,
-mips, mipsel, mips64el, ppc64el, s390x, sparc and sparc64 Debian architectures)
-adds the required options via gcc specs files if
-needed to enable or disable PIE. When enabled and injected by gcc,
-adds nothing. When enabled and not injected by gcc, adds \fB\-fPIE\fP
-to \fBCFLAGS\fP, \fBCXXFLAGS\fP, \fBOBJCFLAGS\fP, \fBOBJCXXFLAGS\fP,
-\fBGCJFLAGS\fP, \fBFFLAGS\fP and \fBFCFLAGS\fP, and \fB\-fPIE \-pie\fP
-to \fBLDFLAGS\fP. When disabled and injected by gcc, adds \fB\-fno\-PIE\fP
-to \fBCFLAGS\fP, \fBCXXFLAGS\fP, \fBOBJCFLAGS\fP, \fBOBJCXXFLAGS\fP,
-\fBGCJFLAGS\fP, \fBFFLAGS\fP and \fBFCFLAGS\fP, and
-\fB\-fno\-PIE \-no\-pie\fP to \fBLDFLAGS\fP.
+This setting (with no global default since dpkg 1.18.23, as it is enabled
+by default now by gcc on the amd64, arm64, armel, armhf, hurd-i386, i386,
+kfreebsd-amd64, kfreebsd-i386, mips, mipsel, mips64el, powerpc, ppc64,
+ppc64el, riscv64, s390x, sparc and sparc64 Debian architectures) adds
+the required options to enable or disable PIE via gcc specs files, if
+needed, depending on whether gcc injects on that architecture the flags
+by itself or not.
+When the setting is enabled and gcc injects the flags, it adds nothing.
+When the setting is enabled and gcc does not inject the flags, it adds
+\fB\-fPIE\fP (via \fI%PKGDATADIR%/pie-compiler.specs\fP) to \fBCFLAGS\fP,
+\fBCXXFLAGS\fP, \fBOBJCFLAGS\fP, \fBOBJCXXFLAGS\fP, \fBGCJFLAGS\fP,
+\fBFFLAGS\fP and \fBFCFLAGS\fP, and
+\fB\-fPIE \-pie\fP (via \fI%PKGDATADIR%/pie-link.specs\fP) to \fBLDFLAGS\fP.
+When the setting is disabled and gcc injects the flags, it adds
+\fB\-fno\-PIE\fP (via \fI%PKGDATADIR%/no-pie-compile.specs\fP) to \fBCFLAGS\fP,
+\fBCXXFLAGS\fP, \fBOBJCFLAGS\fP, \fBOBJCXXFLAGS\fP, \fBGCJFLAGS\fP,
+\fBFFLAGS\fP and \fBFCFLAGS\fP, and
+\fB\-fno\-PIE \-no\-pie\fP (via \fI%PKGDATADIR%/no-pie-link.specs\fP) to
+\fBLDFLAGS\fP.
 
 Position Independent
 Executable are needed to take advantage of Address Space Layout

Bug#900246: python3-spyder needs to be updated to 3.2.8

[Hayden Barnes]

Package: python3-spyder
Version: 3.2.6+dfsg1-2
Tags: sid

python3-spyder needs to be updated to 3.2.8.

It is currently at 3.2.6 which is out of date.

https://github.com/spyder-ide/spyder/releases

Thanks.

Bug#900245: gftodvi.1: Some formatting fixes

[Bjarni Ingi Gislason]

Package: texlive-binaries
Version: 2018.20180416.47457-3+b1
Severity: minor
Tags: patch

Dear Maintainer,

   * What led up to the situation?

  Warning from "groff":

:63 (macro BR): only 1 argument, but more are expected

Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z 

  [ "test-groff" is a developmental version of "groff" ]

  The patch is in the attachment.



  Summary of changes:

Add a missing italic correction (or use a macro).

Add a space character between sentences to make them two (or begin each
sentence on a new line).

Change a two-fonts macro to an one-font macro with a singular argument.

Protect '.' if not end of sentence by adding '\&'.

###

  Details:

Test nr. 41:

Wrong distance between sentences or protect the indicator.

1) Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) [package "manpages"] and "info groff".

Or

2) Adjust space between sentences (two spaces),

3) or protect the indicator by adding "\&" after it.

The "indicator" is an "end-of-sentence character" (.!?).

37:software that has already been written for \*(TX). The characters in the
48:pixels that actually make up the character. (We wouldn't
51:is used for the information at the top of the page. A `label' font
52:is used for the labels on key points of the figure. A `slant'
65:\*(MF source file, or you can change the fonts online. An online dialog
68:with a `/'. For example,
77:OK; any more? grayfontarea /home/art/don/
80:OK; any more? slantfont /home/fonts/slantimagen6
83:OK; any more? 
97:DVI-reading software. The output file name uses the same
102:extension added. For example, the input file
128:TEXFONTS. If that is not set, it uses the system default.
146:Donald E. Knuth,
152:Donald E. Knuth et al.,
156:Donald E. Knuth wrote the program. It was published as part of the

#

Test nr. 45:

Add a missing italic left correction in front of \fI, or use a macro

20:.RB [ \-overflow-label-offset=\fIreal\fP ]

#
 
-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.88-1-u1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages texlive-binaries depends on:
[removed, too long a list]

Versions of packages texlive-binaries recommends:
ii  texlive-base  2018.20180505-1

texlive-binaries suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason
--- gftodvi.1   2018-05-13 21:39:41.0 +
+++ gftodvi.1.new   2018-05-27 23:46:23.0 +
@@ -17,7 +17,7 @@
 gftodvi \- make proof sheets from generic font files
 .SH SYNOPSIS
 .B gftodvi
-.RB [ \-overflow-label-offset=\fIreal\fP ]
+.RB [ \-overflow-label-offset=\fI\,real\/\fP ]
 .RB [ \-verbose ]
 .I gf_file_name
 .\"=
@@ -34,7 +34,7 @@ program converts a generic font
 file output by, for example,
 .BR mf (1),
 to a device independent (DVI) file (that can then be typeset using the same
-software that has already been written for \*(TX). The characters in the
+software that has already been written for \*(TX).  The characters in the
 .I gf
 file will appear one per page, with labels, titles, and annotations
 as specified in Appendix H (Hardcopy Proofs) of
@@ -45,11 +45,11 @@ uses other fonts in addition to the main
 .I gf
 file.
 A `gray' font is used to typeset the
-pixels that actually make up the character. (We wouldn't
+pixels that actually make up the character.  (We wouldn't
 want all the pixels to be simply black, since then labels,
 key points, and other information would be lost.)  A `title' font
-is used for the information at the top of the page. A `label' font
-is used for the labels on key points of the figure. A `slant'
+is used for the information at the top of the page.  A `label' font
+is used for the labels on key points of the figure.  A `slant'
 font is used to typeset diagonal lines, which
 otherwise have to be simulated using horizontal and vertical rules.
 The default gray, title, and label fonts are
@@ -60,12 +60,12 @@ and
 respectively; there is no default slant font.
 .PP
 To change the default fonts, you can give
-.BR special
+.B special
 commands in your
 \*(MF source file, or you can change the fonts online. An online dialog
 ensues if you end the
 .I gf_file_name
-with a `/'. For example,
+with a `/'.  For example,
 .br
 .ti +2
 gftodvi cmr10.300gf/
@@ -94,12 +94,12 @@ The
 on the command line must be complete.  Because
 the resolution is part of the extension, it would not make
 sense to append a default extension as is done with \*(TX or
-DVI-reading software. The output file name uses the same
+DVI-reading software.  The output file 

Bug#429577: #429577: ITP: emacs-snapshot -- The GNU Emacs editor (development snapshot)

[Arnaud Fontaine]

Rob Browning  writes:

> The unversioning is nearly finished, so I suspect the thing to do is for
> me to finish the work, and then we'll look at your changes in that
> context.  Any changes outside debian/ should be relatively unaffected,
> but others may require accommodation.  In any case, I'll be happy to
> work with you on that once we're there.
>
> Unless something unexpected happens, I expect to upload the unversioned
> packages in the next week or so, if not sooner.

Great,  thanks!   Let  me  know  when  it  has  been  pushed  so  I  can
merge/rebase my  changes. I  will probably  have a few  more by  then as
there  are  a few  more  Lintian  warnings that  I  want  to fix  before
uploading emacs-snapshot to NEW...

-- 
Arnaud Fontaine


signature.asc
Description: PGP signature

Bug#900060: apt-get build-dep debian-policy installs too much

[Rodrigo Siqueira]

On 05/25, Sean Whitton wrote:
> control: reassign -1 dia
> control: severity -1 wishlist
> control: retitle -1 Provide binary package containing CLI dia, without GUI 
> dependencies
> 
> Hello,
> 
> On Fri, May 25 2018, Russ Allbery wrote:
> 
> > dia is at fault for all of this, which is in Build-Depends to allow
> > the maintainer script state diagrams to be maintained in the preferred
> > form for modification.
> >
> > It depends on python-gtk2, which in turn depends on python-numpy.  It
> > also depends on libgtk2.0-0, which depends on libcups2, which pulls in
> > libavahi-common3.  libgtk2.0-0 depends on both gnome-icon-theme and
> > hicolor-icon-theme (but gnome-icon-theme depends on hicolor-icon-theme
> > anyway).
> 
> On Fri, May 25 2018, Russ Allbery wrote:
> 
> > Ian Jackson  writes:
> >
> >> I'm afraid to ask, but: why does python-gtk2 depend on numpy ?  Don't
> >> get me wrong, I like numpy, but, err, needed for gtk ?
> >
> >> Also, does dia really need python-gtk2 for the invocations we are
> >> using ?  Or, indeed for most of its invocations ?  ... looks at the
> >> manpage ... oh it's primarily a gui program.  *sigh*
> >
> > Yeah, it's a GUI program we're running in batch mode.  In an ideal
> > world, there would be some separate library and CLI tool that would do
> > batch conversions that would be kept separate from all the GUI
> > machinery, but I'm sure life is short for upstream and they haven't
> > had an obvious reason to bother with this.
> 
> Ah.
> 
> Reassigning, as the bug is not in the debian-policy package.  Hopefully
> I've quoted enough context for the dia maintainer (who is CCed).

Hi,

I will carefully look at the issues pointed out in the thread.

Thanks for the report.
 
> -- 
> Sean Whitton

Bug#899605: Bug#899658: pommed/macfanctld: Invalid maintainer address pkg-mactel-de...@lists.alioth.debian.org

[Nobuhiro Iwamatsu]

Hi, Thibaut.

I am planning to organize it with tracker.d.o.
Do you think about this?
https://tracker.debian.org/teams/pkg-mactel-devel/

Best regards,
  Nobuhiro

2018-05-26 21:01 GMT+09:00 Thibaut Paumard :
> control: severity -1 important
>
>
> Le 24/05/2018 à 10:38, Thibaut Paumard a écrit :
>>
>> Thanks,
>>
>> I've asked for the migration of pkg-mactel-de...@lists.alioth.debian.org.
>>
>> Regards, Thibaut.
>
>
>
> Since this is only a temporary solution, we should still think of choosing
> another address with the next upload.
>
> Regards, Thibaut.
>



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#892517: linux: swiotlb coherent allocation failed

[nfb]

Hi,
this is happening to me too, with nouveau drivers, and it starts for
example with a huge file transfer over LAN.
Btw as i can read on lklm.org and some other places on the net, it
seems the proposed patch is just addressing log spamming and
suppressing all those dmesg lines, while in my case i can say that
this issue is affecting user interaction as well, since the graphics
interface is stuttering and looks very unresponsive while the problem
is in progress. It's not just a matter of logs noise.
For example my interface was really laggish few minutes ago, and i
tryed to kill a firefox instance running inside a Xephyr display which
i discovered not responding anymore. The error messages suddenly
stopped filling the logs, and the general user interaction came back
as fluid as it should normally be. So i don't know if it's just me,
but in my case there is an impact on the graphical performance.

Thank you.

-- 
free as in freedom, not free beer

Bug#875858: pkgsel: Offer to install/manage unattended-upgrades

[Cyril Brulebois]

Hi Moritz,

Moritz Mühlenhoff  (2018-05-27):
> Sorry for the late reply, busy and backlogged in my inbox.

No worries, I know the feeling; and thanks for the detailed answer!

Replying only briefly (for similar reasons):

> u-u is also very rudimentary. It doesn't support service restarts
> e.g., so installing an openssl update is pretty pointless as it
> doesn't even attempt to warn/act on library restarts.
> 
> It's also very brittle, only a few days ago I had to fix a stretch
> system where it uninstalled virtually all KDE packages after
> installing the VLC update (which installed a new version of libvlccore
> and all went kaboom).
> 
> All this crap falls back to the security team, because people think
> our update broke the system. Or stuff like
> https://lists.debian.org/debian-security/2018/05/msg00011.html
> 
> u-u breaks stuff (and would even more so if installed by default on
> servers, where it will cause unpredictable server downtimes during
> restarts etc.) and Debian should not be broken by default.
> 
> If userse make a concious decision to accept the consequences of
> unattended-upgrades, then they can install it explicitly and have to
> deal with the fallout, but it must not be part of a default
> installation.
> 
> If this had been proposed to t...@security.debian.org before making
> the change we would have objected immediately as we are the ones
> primarily affected.  We can't sensibly follow all the
> discussions/developments made in Debian, it's far too big. (And being
> in the security team is already so time-demanding that it leaves
> little for other Debian work anyway).

Sorry about the fallouts. I can't say for sure but ISTR I only found out
about this change when preparing a release announcement, even if there
were prior discussions in other channels (debian-devel@). The security
team should have been looped in, and I'm sorry I didn't think of it at
the time, even after the fact (= right after a D-I Alpha was published).

debian-boot@: the requested revert looks fine to me, bonus points if it
comes with a (short) summary of these reasons in changelog, so that they
can be emphasized in the release announcement. :)

Thanks to everyone involved.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#900244: NVM error information log entry count increase not an error

[martin f krafft]

Package: smartmontools
Version: 6.5+svn4324-1
Severity: normal
File: /usr/sbin/smartd

As of late, I get

  Device: /dev/nvme0, number of Error Log entries increased from 373 to 374

mailed to me every day. However, this is not an error log, but an
error "information" log, and used by NVM apparently also for simple
state logging, i.e. a new entry being appended to the log does not
actually constitute an error.

I'll try to figure out how to filter this stuff using smartd.conf,
but filing the issue here as I think the default handling of NVMs
should be fixed accordingly.

Thanks,
martin

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages smartmontools depends on:
ii  debianutils  4.8.4
ii  init-system-helpers  1.51
ii  libc62.27-3
ii  libcap-ng0   0.7.9-1
ii  libgcc1  1:8.1.0-2
ii  libselinux1  2.7-2+b2
ii  libstdc++6   8.1.0-2
ii  lsb-base 9.20170808

Versions of packages smartmontools recommends:
ii  bsd-mailx [mailx]  8.1.2-0.20160123cvs-4

Versions of packages smartmontools suggests:
pn  gsmartcontrol   
pn  smart-notifier  

-- Configuration Files:
/etc/smartd.conf changed [not included]

-- debconf-show failed


-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#900243: python-minimock: new upstream version 1.2.8 available

[tony mancill]

Package: python-minimock
Version: 1.2.7-1
Severity: wishlist

Hello,

MiniMock 1.2.8 is available.  This version includes updates to support
Python 3.  This update would be a natural predecessor to adding a
python3-minimock binary package.

Thank you,
tony

Bug#875439: ansi2html -c

[Adam Borowski]

> A lot of software colorizes their build logs.

> around 2% does so unconditionally, this results in raw ANSI
> codes in the HTML.

> Thus, please pipe the logs through "ansi2html -nw" (package colorized-logs).

The version in unstable[1] has just grown an option to make sure there's no
white on white.  That would happen if a log requests explicit "white" rather
than "bold".  Same applies to black-on-black or pink-on-pink.

I didn't make this the default for generic use (as it's not what real
terminals do), but you don't care about accuracy but not losing information. 
Thus, it'd be nice if you could filter the logs through "ansi2html -nwc".


Meow!

[1]. Which, if you approve this idea, can get to stretch-bpo.
-- 
⢀⣴⠾⠻⢶⣦⠀ .globl _start↵.data↵rc: .ascii "/etc/init.d/rcS\0"↵.text↵_start
⣾⠁⢰⠒⠀⣿⡁ mov $57,%rax↵syscall↵cmp $0,%rax↵jne child↵parent:↵mov $61,%rax
⢿⡄⠘⠷⠚⠋⠀ mov $-1,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall↵jmp parent↵child:
⠈⠳⣄ mov $59,%rax↵mov $rc,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall

Bug#900242: samba-common: update 'panic-action' script message, samba-dbg renamed to samba-dbgsym

[Anatolii Borodin]

Package: samba-common
Version: 2:4.7.6+dfsg

The script /usr/share/samba/panic-action contains lines:

echo "If the problem persists, you are encouraged to first install the"
echo "samba-dbg package, which contains the debugging symbols for the Samba"
echo "binaries.  Then submit the provided information as a bug report to"

But since the 4.4.5+dfsg-3 version (see
https://salsa.debian.org/samba-team/samba/commit/f9bf7cd633a68d7c2e881801e90aa2af43fd72b7)
the package samba-dbg has been dropped and replaced with samba.dbgsym
(see #819776). The message printed by the script became misleading.

1. The debug package name should be updated.
2. Installing a -dbgsym package requires enabling of the additional
ddeb repository, which is not trivial and requires some googling.
Adding some links to https://wiki.debian.org/AutomaticDebugPackages
and/or https://wiki.ubuntu.com/Debug%20Symbol%20Packages could be
helpful.

See also https://bugs.launchpad.net/ubuntu/+source/samba/+bug/#819776

-- 
Mit freundlichen Grüßen,
Anatolii Borodin

Bug#898873: Bug #898873 in matplotlib marked as pending

[Sandro Tosi]

thanks, fixed as 33e2199a (will upload soon, so that i can eventual catch
some more tests error to submit upstream)
On Sun, May 27, 2018 at 9:33 AM Graham Inggs  wrote:

> On 27 May 2018 at 04:31, Sandro Tosi  wrote:
> > i did that on
> >
https://salsa.debian.org/python-team/modules/matplotlib/commit/2d081bc5a3841277f7d4469fec853fa9d9a5ad0f
> > but i didnt push it until now, are more archs needed in that exclusion
list?

> Oh nice, thanks!

> I went through the list and checked what hadn't built according to the
> buildd logs.

> dvipng: seems to be available on sparc64
> inkscape: I concur
> python(3)-cairocffi: I concur
> python(3)-pandas: please add !sparc64
> python(3)-pyqt5: seems to be available on alpha

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#899318: virtualbox: FTBFS: vboxssdt-standard.hex:16:23: error: expected initializer before '-' token

[Mattia Dongili]

On Fri, May 25, 2018 at 07:07:53AM +0900, Mattia Dongili wrote:
[...]
> Gianfranco,
> if you need a work-around, changing the file prefix to something that is
> a legal C identifier might help.

Gianfranco,
so are you going to patch virtualbox?
In terms of severity, I think this bug against acpica-unix should be
"Important" rather than "Serious".

Thanks
-- 
mattia
:wq!

Bug#900241: no root.key provided by libunbound2

[Simon Deziel]

Package: unbound
Version: 1.7.1-1

TL;DR: applications using libunbound2 should have access to a fresh root.key

If one installs unbound-anchor or unbound-host or any other application
using libunbound2, they will be missing a fresh copy of the root.key for
DNSSEC validation. This is because /var/lib/unbound/root.key is managed
by a helper script provided by the unbound package only.

Ideally, installing libunbound2 should provide a root.key that is kept
up to date for root KSK rollovers.

A possible solution would be to have libunbound2 depend on
unbound-anchor and have the unbound-anchor package ship a cron job (or
systemd.timer unit) to periodically refresh the root.key file.

If the proposed solution makes sense to you, I'd be happy to work on the
implementation.

Regards,
Simon


P.S: This problem was initially reported to Ubuntu
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1771545



signature.asc
Description: OpenPGP digital signature

Bug#900173: git-annex: internal error: evacuate: strange closure type 4325404

[Anthony DeRobertis]

On 05/27/2018 05:24 PM, Joey Hess wrote:

Anthony DeRobertis wrote:

So right now, it's just refusing the run in the background :-/

If you're able to reproduce the bug on demand that way,
that could point to the way git-annex daemonizes itself with
forkProcess. Which from its documentation:

 forkProcess comes with a giant warning: since any other running threads
 are not copied into the child process, it's easy to go wrong: e.g. by
 accessing some shared resource that was held by another thread in the
 parent.

git-annex tries to use forkProcess in a safe way, but that's not
especially well-defined or easy to check.

You might try running git-annex watch instead of git-annex assistant,
since they both daemonize but the latter has a simpler code path.

I stopped the (foreground) assistant with "git annex assistant --stop"; 
then ran "git annex assistant" (worked). Then stopped it again. Then 
started (failed). Tried another few times, all failed. I tried a few 
"git annex watch" followed by "git annex watch --stop" (after getting 
the "(started...)" message in the log — all of those worked. Tried a few 
more "git annex assistant", all failed.


So, absent the one "git annex assistant" which worked, those all failed. 
And all of the "git annex watch" worked. So does starting the assistant 
with "git annex assistant --foreground". (And maybe that's why the 
webapp was working for me earlier too — it doesn't fork...)


Honestly, if that code is a nightmare... you could just remove it. "git 
annex assistant --foreground &" is easy enough. And presumably entirely 
avoids the forkProcess issue there.

Bug#900240: cmake: FTBFS on hurd-i386: please update cmlibuv

[Samuel Thibault]

Package: cmake
Version: 3.11.2-1
Severity: important
Tags: patch

Hello,

Once libuv1 will be fixed (#881882), cmake will still FTBFS, because the
cmake build still builds the embedded libuv. The attached patch updates
it to the patch applied to libuv1, to fix the FTBFS.

Samuel

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages cmake depends on:
ii  cmake-data3.11.2-1
ii  libarchive13  3.2.2-3.1
ii  libc6 2.27-3
ii  libcurl3  7.58.0-2
ii  libexpat1 2.2.5-3
ii  libgcc1   1:8.1.0-3
ii  libjsoncpp1   1.7.4-3
ii  librhash0 1.3.6-2
ii  libstdc++68.1.0-3
ii  libuv11.18.0-3
ii  procps2:3.3.14-1+b1
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages cmake recommends:
ii  gcc   4:7.2.0-1d1
ii  make  4.1-9.1

Versions of packages cmake suggests:
pn  cmake-doc
ii  ninja-build  1.8.2-1

-- no debconf information

-- 
Samuel
 FYLG> Tiens, vlà une URL qui va bien :
 FYLG> ftp://127.0.0.1/WaReZ/NiouZeS/WinDoZe/NeWSMoNGeR/SuPeR
 c'est gentil sauf que l'adresse ne fonctionne pas sa me fais une erreur
 -+- Furtif in Guide du Neuneu Usenet :  -+-
Index: cmake-3.11.2/Utilities/cmlibuv/src/unix/fs.c
===
--- cmake-3.11.2.orig/Utilities/cmlibuv/src/unix/fs.c
+++ cmake-3.11.2/Utilities/cmlibuv/src/unix/fs.c
@@ -427,6 +427,7 @@ static ssize_t uv__fs_scandir(uv_fs_t* r
 }
 
 
+#if _POSIX_VERSION < 200809L
 static ssize_t uv__fs_pathmax_size(const char* path) {
   ssize_t pathmax;
 
@@ -442,12 +443,19 @@ static ssize_t uv__fs_pathmax_size(const
 
   return pathmax;
 }
+#endif
 
 static ssize_t uv__fs_readlink(uv_fs_t* req) {
   ssize_t len;
   char* buf;
+  struct stat st;
+  int ret;
 
-  len = uv__fs_pathmax_size(req->path);
+  ret = lstat(req->path, );
+  if (ret != 0) {
+return -1;
+  }
+  len = st.st_size;
   buf = uv__malloc(len + 1);
 
   if (buf == NULL) {
@@ -474,9 +482,16 @@ static ssize_t uv__fs_readlink(uv_fs_t*
 }
 
 static ssize_t uv__fs_realpath(uv_fs_t* req) {
-  ssize_t len;
   char* buf;
 
+#if _POSIX_VERSION >= 200809L
+  buf = realpath(req->path, NULL);
+  if (buf == NULL) {
+return -1;
+  }
+#else
+  ssize_t len;
+
   len = uv__fs_pathmax_size(req->path);
   buf = uv__malloc(len + 1);
 
@@ -489,6 +504,7 @@ static ssize_t uv__fs_realpath(uv_fs_t*
 uv__free(buf);
 return -1;
   }
+#endif
 
   req->ptr = buf;
 

Bug#900239: libprocps-dev: symlink to libprocps.so broken in /usr/lib

[Stanislaw Halik]

Package: libprocps-dev
Version: 2:3.3.15-1
Severity: normal

Hey,

The libprocps-dev package depends on `libprocps7' but contains a broken
symlink to `libprocps.so.6' in the /usr/lib search path.

Otherwise the compiler picks up `libprocps.a' from the same directory,
that fails since it's not built with -fPIC.

I believe the original intention was to have a non-broken symlink to
`libprocps.so.7'.

cheers,
sh

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8), LANGUAGE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libprocps-dev depends on:
ii  libprocps7  2:3.3.15-1

libprocps-dev recommends no packages.

libprocps-dev suggests no packages.

-- no debconf information

Bug#900237: libuv1: FTBFS on hppa: not ok 46 - fs_copyfile

[John David Anglin]

Source: libuv1
Version: 1.20.3-1
Severity: normal

Dear Maintainer,

Test 46 fails on hppa:

not ok 46 - fs_copyfile
# exit code 6
# Output from process `fs_copyfile`:
# Assertion failed in test/test-fs-copyfile.c on line 182: r == 0 || r == 
UV_ENOSYS || r == UV_ENOTSUP || r == UV_ENOTTY

The value of r in the failing assertion is -233.  If the value is a standard
errno, it is ENOBUFS.

Full build log is here:
https://buildd.debian.org/status/fetch.php?pkg=libuv1=hppa=1.20.3-1=1527441587=0

Regards,
Dave Anglin

-- System Information:
Debian Release: buster/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 4.14.44+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Bug#900238: ITP: node-ldap-client -- LDAP client library for Node.js

[Xavier Guimard]

Package: wnpp
Severity: wishlist
Owner: Xavier Guimard 

* Package name: node-ldap-client
  Version : 3.1.3
  Upstream Author : Jeremy Childs 
* URL : https://github.com/jeremycx/node-LDAP
* License : Expat
  Programming Lang: JavaScript
  Description : LDAP client library for Node.js

ldap-client provides OpenLDAP client bindings for Node.js. It can be
used to connect a Node.js software to any LDAP server.

For now Debian has no LDAP client library for Node.js. This library
seems to be the more used and provides a complete LDAP client
interface. It was previously named LDAP (the first LDAP hit on
npmjs.org).

Regards,
Xavier

Bug#898209: charliecloud: Change service by systemd in po-debconf

[Alban Vidal]

Dear Peter,

Thanks for the merge of the patch.

I think it's not necessary to disturb the translate teams.
If you whant, i can update by myself and create merge request.

Regards,

Alban


Le 27/05/2018 à 19:45, Peter Wienemann a écrit :
> Dear Alban,
>
> thanks for providing this patch which I gladly applied.
>
> Shall I simply go ahead and do the "translations" of "systemctl restart
> procps" in the various po files myself (to avoid bothering the
> translators with such a straightforward change) or would that interfere
> with the workflow of the language teams?
>
> Best regards,
>
> Peter

Bug#900173: git-annex: internal error: evacuate: strange closure type 4325404

[Joey Hess]

Anthony DeRobertis wrote:
> So right now, it's just refusing the run in the background :-/

If you're able to reproduce the bug on demand that way,
that could point to the way git-annex daemonizes itself with
forkProcess. Which from its documentation:

forkProcess comes with a giant warning: since any other running threads
are not copied into the child process, it's easy to go wrong: e.g. by
accessing some shared resource that was held by another thread in the
parent.

git-annex tries to use forkProcess in a safe way, but that's not
especially well-defined or easy to check.

You might try running git-annex watch instead of git-annex assistant,
since they both daemonize but the latter has a simpler code path.

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#897315: ITA: yaml-mode -- emacs mode for YAML files

[Nicholas D Steeves]

Update: I intend to upload an elpafied + new upstream version of
yaml-mode to mentors the first weekend in June.  Unfortunately it will
be necessary to defer switching to machine-readable copyright format
to a later release if we don't hear from Jari for #897942 before then.

Take care!
Nicholas


signature.asc
Description: PGP signature

Bug#899384: vlc: Hardware acceleration fails after upgrade to 3.0.2

[Sebastian Ramacher]

On 2018-05-28 00:10:42, Antoni Marcinek wrote:
> Hi,
> 
> I downgraded to 2.2.7-1~deb9u1. As I remembered I can increase the
> speed up to 64x. The messages in the console are the following:
> 
> VLC media player 2.2.7 Umbrella (revision 2.2.7-0-g6e32381286)
> [55798d591178] core libvlc: Running vlc with the default
> interface. Use 'cvlc' to use vlc without interface.
> Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
> object file: No such file or directory
> 
> There is nothing about VA-API, nor profile(3). So I wonder what is going on...

vlc with -vvv should tell you what's used in the end.

> 
> Anyway, what about the optirun? I think I did see in some forums
> people complaining about it (so it is not just my issue).

I don't know. I don't have a suitable system to test it. My best would be to get
help from VLC or Qt upstream.

Cheers

> 
> 
> Cheers,
> Antoni
> 
> 2018-05-27 11:52 GMT+03:00 Sebastian Ramacher :
> > On 2018-05-27 11:05:32, Antoni Marcinek wrote:
> >> Hi,
> >>
> >> dmo packages replaced, but it doesn't help.
> >>
> >> As for other Qt applications, I can run for example qpdfview (Qt5) and
> >> qtconfig (Qt4) with optirun.
> >>
> >>
> >> As for the codec: before update to VLC 3.0.2 I didn't observe the
> >> performance problem with this movie file. So either hardware
> >> acceleration didn't fail, what is in conflict with "your hardware
> >> doesn't support the codec" or it did fail with the same error, but I
> >> didn't notice the error message and the performance with software
> >> decoding was much better. In order to verify this, I would have to
> >> revert my vlc to the previous version. Are there downloadable Debian
> >> packages for the previous version that was shipped with Debian 9.4?
> >
> > The stretch repos still have 2.2.7 packages until the next point release. 
> > After
> > that you can always get older packages from snapshot.debian.org.
> >
> > Cheers
> >
> >>
> >> Cheers,
> >> Antoni
> >>
> >> 2018-05-26 10:26 GMT+03:00 Sebastian Ramacher :
> >> > Control: tags -1 + moreinfo
> >> >
> >> > Hi
> >> >
> >> > On 2018-05-23 18:29:41, Antoni Marcinek wrote:
> >> >> Package: src:vlc
> >> >> Version: 3.0.2-0+deb9u1
> >> >> Severity: important
> >> >>
> >> >> Dear Maintainer,
> >> >>
> >> >> After recent upgrade to 3.0.2 when I try to increase the speed above
> >> >> certain level (16x), the video is frozen. The same procedure on
> >> >> the same movie file worked without problem up to 64x before the upgrade.
> >> >> Looks like there is some problem with hardware acceleration, which is
> >> >> set to AUTO in the VLC config - I am getting the following error in the
> >> >> console:
> >> >>
> >> >> libva info: VA-API version 0.39.4
> >> >> libva info: va_getDriverName() returns 0
> >> >> libva info: Trying to open
> >> >> /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
> >> >> libva info: Found init function __vaDriverInit_0_39
> >> >> libva info: va_openDriver() returns 0
> >> >> [7f249c016240] vaapi generic error: profile(3) is not supported
> >> >
> >> > Not much vlc can do about that. If your hardware doesn't support the 
> >> > codec, then
> >> > it can only fallback to software decoding.
> >> >
> >> >> Failed to open VDPAU backend libvdpau_i965.so: cannot open shared 
> >> >> object file: No such file or directory
> >> >>
> >> >> I am doing this on a laptop with integrated Intel graphics + Optimus
> >> >> nvidia card. What I understand is happening it tries to run vaapi
> >> >> (fails) and then falls back to vdpau, which also fails. The vdpau
> >> >> probably would require to run with nvidia card, but unfortunately
> >> >> > optirun vlc
> >> >> is unable to open the Qt interface and falls back to console interface
> >> >> which is pretty useless (at least for my case).
> >> >>
> >> >> Maybe the new VLC version requires newer libva - libva2, which provides
> >> >> VA-API 1.0.0?
> >> >>
> >> >> If the problem with VA-API cannot be solved, then maybe it is easier to
> >> >> make VLC Qt interface run with optirun? While it would not bring the
> >> >> user experience back to what was before upgrade to 3.0.2 (hardware
> >> >> acceleration out-of-the-box on Intel graphics), it would still be
> >> >> acceptable.
> >> >
> >> > Are you able to use any other Qt-based applications when started with 
> >> > optirun?
> >> >
> >> >> ii  libavcodec57 10:3.3.7-dmo1+deb9u1
> >> >> ii  libavformat5710:3.3.7-dmo1+deb9u1
> >> >> ii  libavutil55  10:3.3.7-dmo1+deb9u1
> >> >
> >> > This combination of packages is not supported by us. Please replace all 
> >> > dmo
> >> > packages with the packages provided by Debian.
> >> >
> >> > Cheers
> >> > --
> >> > Sebastian Ramacher
> >>
> >> ___
> >> pkg-multimedia-maintainers mailing list
> >> pkg-multimedia-maintain...@alioth-lists.debian.net
> >> 

Bug#900236: tlmgr manpage: 32-bit OpenPGP key IDs

[Jakub Wilk]

Package: texlive-base
Version: 2018.20180505-1

The tlmgr(1) manual page reads:

The signature is created by the TeX Live Distribution GPG key 
0x06BAB6BC, which in turn is signed by Karl Berry’s key 0x30D155AD and 
Norbert Preining’s key 0x6CACA448. 


Please don't use 32-bit OpenPGP key IDs. It's computationally trivial to 
generate a new key with chosen short ID. Please use 64-bit key IDs, or, 
even better, full fingerprints.


In fact, if you request the 0x30D155AD key from a keyserver, you will 
get _two_ keys; one of them is presumable a sham key originating from 
.


OTOH, there's no 0x6CACA448 key on keyservers. An attacker could upload 
their own key with such ID without rising much suspicion.


--
Jakub Wilk

Bug#899384: vlc: Hardware acceleration fails after upgrade to 3.0.2

[Antoni Marcinek]

Hi,

I downgraded to 2.2.7-1~deb9u1. As I remembered I can increase the
speed up to 64x. The messages in the console are the following:

VLC media player 2.2.7 Umbrella (revision 2.2.7-0-g6e32381286)
[55798d591178] core libvlc: Running vlc with the default
interface. Use 'cvlc' to use vlc without interface.
Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
object file: No such file or directory

There is nothing about VA-API, nor profile(3). So I wonder what is going on...


Anyway, what about the optirun? I think I did see in some forums
people complaining about it (so it is not just my issue).


Cheers,
Antoni

2018-05-27 11:52 GMT+03:00 Sebastian Ramacher :
> On 2018-05-27 11:05:32, Antoni Marcinek wrote:
>> Hi,
>>
>> dmo packages replaced, but it doesn't help.
>>
>> As for other Qt applications, I can run for example qpdfview (Qt5) and
>> qtconfig (Qt4) with optirun.
>>
>>
>> As for the codec: before update to VLC 3.0.2 I didn't observe the
>> performance problem with this movie file. So either hardware
>> acceleration didn't fail, what is in conflict with "your hardware
>> doesn't support the codec" or it did fail with the same error, but I
>> didn't notice the error message and the performance with software
>> decoding was much better. In order to verify this, I would have to
>> revert my vlc to the previous version. Are there downloadable Debian
>> packages for the previous version that was shipped with Debian 9.4?
>
> The stretch repos still have 2.2.7 packages until the next point release. 
> After
> that you can always get older packages from snapshot.debian.org.
>
> Cheers
>
>>
>> Cheers,
>> Antoni
>>
>> 2018-05-26 10:26 GMT+03:00 Sebastian Ramacher :
>> > Control: tags -1 + moreinfo
>> >
>> > Hi
>> >
>> > On 2018-05-23 18:29:41, Antoni Marcinek wrote:
>> >> Package: src:vlc
>> >> Version: 3.0.2-0+deb9u1
>> >> Severity: important
>> >>
>> >> Dear Maintainer,
>> >>
>> >> After recent upgrade to 3.0.2 when I try to increase the speed above
>> >> certain level (16x), the video is frozen. The same procedure on
>> >> the same movie file worked without problem up to 64x before the upgrade.
>> >> Looks like there is some problem with hardware acceleration, which is
>> >> set to AUTO in the VLC config - I am getting the following error in the
>> >> console:
>> >>
>> >> libva info: VA-API version 0.39.4
>> >> libva info: va_getDriverName() returns 0
>> >> libva info: Trying to open
>> >> /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
>> >> libva info: Found init function __vaDriverInit_0_39
>> >> libva info: va_openDriver() returns 0
>> >> [7f249c016240] vaapi generic error: profile(3) is not supported
>> >
>> > Not much vlc can do about that. If your hardware doesn't support the 
>> > codec, then
>> > it can only fallback to software decoding.
>> >
>> >> Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
>> >> file: No such file or directory
>> >>
>> >> I am doing this on a laptop with integrated Intel graphics + Optimus
>> >> nvidia card. What I understand is happening it tries to run vaapi
>> >> (fails) and then falls back to vdpau, which also fails. The vdpau
>> >> probably would require to run with nvidia card, but unfortunately
>> >> > optirun vlc
>> >> is unable to open the Qt interface and falls back to console interface
>> >> which is pretty useless (at least for my case).
>> >>
>> >> Maybe the new VLC version requires newer libva - libva2, which provides
>> >> VA-API 1.0.0?
>> >>
>> >> If the problem with VA-API cannot be solved, then maybe it is easier to
>> >> make VLC Qt interface run with optirun? While it would not bring the
>> >> user experience back to what was before upgrade to 3.0.2 (hardware
>> >> acceleration out-of-the-box on Intel graphics), it would still be
>> >> acceptable.
>> >
>> > Are you able to use any other Qt-based applications when started with 
>> > optirun?
>> >
>> >> ii  libavcodec57 10:3.3.7-dmo1+deb9u1
>> >> ii  libavformat5710:3.3.7-dmo1+deb9u1
>> >> ii  libavutil55  10:3.3.7-dmo1+deb9u1
>> >
>> > This combination of packages is not supported by us. Please replace all dmo
>> > packages with the packages provided by Debian.
>> >
>> > Cheers
>> > --
>> > Sebastian Ramacher
>>
>> ___
>> pkg-multimedia-maintainers mailing list
>> pkg-multimedia-maintain...@alioth-lists.debian.net
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
>
> --
> Sebastian Ramacher

Bug#884923: abiword: CVE-2017-17529

[Gabriel Corona]

Hi,

Are you sure this is vulnerable ? I did not manage to trigger anything
problematic.

The code referenced is (in fallback_open_uri):


gintargc;
gchar **argv = NULL;
char   *cmd_line = g_strconcat (browser, " %1", NULL);

if (g_shell_parse_argv (cmd_line, , , err)) {
  /* check for '%1' in an argument and substitute the url
   * otherwise append it */
  gint i;
  char *tmp;

  for (i = 1 ; i < argc ; i++)
if (NULL != (tmp = strstr (argv[i], "%1"))) {
  *tmp = '\0';
  tmp = g_strconcat (argv[i],
(clean_url != NULL) ? (char const *)clean_url : url,
tmp+2, NULL);
  g_free (argv[i]);
  argv[i] = tmp;
  break;
}

  /* there was actually a %1, drop the one we added */
  if (i != argc-1) {
g_free (argv[argc-1]);
argv[argc-1] = NULL;
  }
  g_spawn_async (NULL, argv, NULL, G_SPAWN_SEARCH_PATH,
NULL, NULL, NULL, err);
  g_strfreev (argv);
}
g_free (cmd_line);


This seems correct with respect to injection through the URI:
the URI string cannot be expanded into multiple arguments
and is not passed to `system()`.

-- 
Gabriel

Bug#900213: lintian: please add override_dh_build to the possible dh_* misspellings

[Chris Lamb]

tags 900213 + pending
thanks

Good idea! Implemented in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/6ac0d1debee3663864070d6188b44e2da051bd6f

  checks/debhelper.pm  | 7 ---
  debian/changelog | 4 
  t/tests/debhelper-override-typos/debian/debian/rules | 3 +++
  t/tests/debhelper-override-typos/tags| 3 ++-
  4 files changed, 13 insertions(+), 4 deletions(-)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#897060: Reproducing the bug

[Joris Rau]

I can actually still reproduce the bug when I wait some time before
entering my hard drive decryption password.

Bug#898501: Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

[Sean Whitton]

control: tag 898501 +wontfix
control: notfixed 898501 fonts-font-awesome/5.0.10-3
control: affects 899124 mkdocs-bootstrap
control: affects 899124 cider

Hello Alexis,

On Sat, May 26, 2018 at 04:07:59PM +0200, Alexis Murzeau wrote:
> close 898501 5.0.10-3
> thanks
>
> Hi,
>
> I'm re-closing #898501: Broken symlinks as they are indeed fixed now and
> to keep only one bug open (#899124) about the incompatibilities caused
> by version 5.

The broken symlinks I originally reported in this bug are not fixed --
try building something depending on mkdocs-bootstrap, e.g. src:cider.

However, discussion in #899124 suggest that the links in question
/can't/ be fixed, because there no longer exists a single font-awesome,
instead three variants.  Hence the wontfix tag.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#892332: fim: Please use 'pkg-config' to find FreeType 2

[Rafael Laboissière]

Control: severity -1 normal
Control: tags -1 upstream

* hugh.mcmas...@outlook.com  [2018-03-08 22:52]:


 Source: fim
 Severity: important

Dear Maintainer,

The next release of libfreetype6-dev will *not* ship 
`freetype-config', as the script has now been deprecated in favour of 
`pkg-config'.


This is an upstream change:

"Use of the `freetype-config' script to get compilation and

linking options is deprecated since it doesn't support

cross-compiling, among other deficiencies. Instead, you should

use the `pkg-config' interface." [1]

Please use `pkg-config' to detect the FreeType 2 headers and 
libraries in fim.


If this bug is not resolved prior to the release of FreeType 2.9.1, 
your package may FTBFS.


Thank you for the heads up.  I am hereby tagging this bug "upstream". It 
will be really preferable that the upstream author (who, BTW, is also the 
maintainer of the Debian package) fix this in the upstream source, when 
time comes.


At any rate, I am also hereby downgrading the severity from "important" 
to "normal", because version 2.9.1 of the FreeType package is not yet in 
Debian, not even in experimental.


Please, feel free to ping us when version 2.9.1 will be uploaded to 
Debian.


Best,

Rafael Laboissière

Bug#898391: nvidia-driver-libs-nonglvnd: cannot upgrade due to libglvnd0 conflict

[Tom Maneiro]

I'm also affected here: I'm trying to update to Mesa 17.3 after 
installing the 390.48.2~bpo9+3 drivers on my Stretch laptop (I'm using a 
hybrid graphics laptop so I need both drivers for my setup), but either 
I get updated Mesa or lose the nVidia blob due to conflicts with the new 
packaging specs (??), rendering my setup completely unupgradable and 
unusable.

Bug#900235: O: freelan -- Peer-to-peer virtual private network daemon

[Mattia Rizzolo]

Package: wnpp

The current maintainer of freelan, Rolf Leggewie ,
has orphaned this package.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: freelan
Binary: freelan
Version: 2.0-6
Maintainer: Debian QA Group 
Uploaders: Julien Kauffmann 
Build-Depends: debhelper (>= 9), libssl-dev, libcurl4-openssl-dev, 
libboost-system-dev, libboost-thread-dev, libboost-program-options-dev, 
libboost-filesystem-dev, libboost-iostreams-dev, scons
Architecture: any
Standards-Version: 4.0.0
Format: 3.0 (quilt)
Files:
 e53b8b0d3b947f2c68f5b6909bc0eeb2 2063 freelan_2.0-6.dsc
 dc60ebce9730e896122d43b2a3a291b4 4330112 freelan_2.0.orig.tar.gz
 bd50189e299f759a87ba40e19834b4cf 17204 freelan_2.0-6.debian.tar.xz
Vcs-Browser: 
https://github.com/freelan-developers/freelan-all/tree/debian/unstable
Vcs-Git: https://github.com/freelan-developers/freelan.git -b debian/unstable
Checksums-Sha256:
 57285fe05cb0beda4246b4252c31e2dad6faa5ed0fa98b9a368ea95773b2e9e5 2063 
freelan_2.0-6.dsc
 02fa5b4806655ca7ad24bdb265a7b79e2e8b900797dca1c87a157e76ec85f529 4330112 
freelan_2.0.orig.tar.gz
 7c5e5a22a690678ab9fabd1002c81d8145413697e456d7e0d09ee703d43319a2 17204 
freelan_2.0-6.debian.tar.xz
Homepage: http://www.freelan.org
Package-List: 
 freelan deb net extra arch=any
Directory: pool/main/f/freelan
Priority: optional
Section: misc

Package: freelan
Version: 2.0-6
Installed-Size: 2339
Maintainer: Debian QA Group 
Architecture: amd64
Depends: libboost-date-time1.62.0, libboost-filesystem1.62.0, 
libboost-iostreams1.62.0, libboost-program-options1.62.0, 
libboost-system1.62.0, libboost-thread1.62.0, libc6 (>= 2.14), libcurl3 (>= 
7.16.3), libgcc1 (>= 1:3.0), libssl1.1 (>= 1.1.0), libstdc++6 (>= 5.2), 
lsb-base (>= 3.0-6)
Description: Peer-to-peer virtual private network daemon
Description-md5: a2a818e761aa190b96c2e07944278664
Homepage: http://www.freelan.org
Section: net
Priority: optional
Filename: pool/main/f/freelan/freelan_2.0-6_amd64.deb
Size: 627580
MD5sum: 209663d98d08b0ba0543ab31f5540296
SHA256: f2753529528bf77a06ca0ec52ca39fc127683eece4225749a487a2395882a3ba


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#900173: git-annex: internal error: evacuate: strange closure type 4325404

[Anthony DeRobertis]

On 05/27/2018 01:20 PM, Joey Hess wrote:

One person reported the same error message 7 years ago here:
https://ghc.haskell.org/trac/ghc/ticket/5085
They were using git-annex get, not the assistant when it crashed.

They also were able to git bisect git-annex's code and found an utterly
innocuous commit that triggered whatever the problem is.
(commit 828a84ba3341d4b7a84292d8b9002a8095dd2382)

It's probably a memory problem, or a ghc bug, or a bug in some library
that is doing something memory related and messes up, such that ghc's
garbage collector sees bad data.


First off, thank you for git-annex. It's really useful software. I can't 
imagine syncing all this data between several desktops, laptops, & a few 
tablets without it. And apologies in advance for this rambling message.


Just finished 2, almost 3 passes of memtest86+ with no errors. (Before 
starting using them machine, several years ago, it had over 24h of 
memtest). It's been stable, haven't seen any random 
crashes/corruption/etc. — so I doubt it's a hardware issue. It's also 
not overclocked or anything silly like that.


I'm not sure what bisecting this would entail; as far as I can tell... 
it's random.


(BTW: I use the CLI interface too, quite a lot, and have never seen a 
weird error from it. Only from the assistant).


Freshly after booting, I ran "git annex assistant"; it gave one of those 
errors in the log. So I ran "git annex assistant --debug"; on the 
console it gave:


[2018-05-27 15:56:53.403932801] read: uname ["-o"]
[2018-05-27 15:56:53.405388769] process done ExitSuccess
[2018-05-27 15:56:53.502601514] logging to .git/annex/daemon.log
[2018-05-27 15:56:53.503385967] read: git 
["--git-dir=.git","--work-tree=.","--literal-pathspecs","show-ref","git-annex"]
[2018-05-27 15:56:53.505100304] process done ExitSuccess
[2018-05-27 15:56:53.505256854] read: git 
["--git-dir=.git","--work-tree=.","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"]
[2018-05-27 15:56:53.50805146] process done ExitSuccess
[2018-05-27 15:56:53.517155935] chat: git 
["--git-dir=.git","--work-tree=.","--literal-pathspecs","cat-file","--batch"]
[2018-05-27 15:56:53.517579777] chat: git 
["--git-dir=.git","--work-tree=.","--literal-pathspecs","cat-file","--batch-check=%(objectname)
 %(objecttype) %(objectsize)"]
[2018-05-27 15:56:53.522956836] logging to .git/annex/daemon.log

and in the log,

[2018-05-27 15:56:40.385313411] main: starting assistant version 6.20180509
[2018-05-27 15:56:40.39050583] read: git 
["--git-dir=.git","--work-tree=.","--literal-pathspecs","show-ref","git-annex"]
[2018-05-27 15:56:40.393284694] process done ExitSuccess
[2018-05-27 15:56:40.393397832] read: git 
["--git-dir=.git","--work-tree=.","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"]
[2018-05-27 15:56:40.395763112] process done ExitSuccess
[2018-05-27 15:56:40.396781131] chat: git 
["--git-dir=.git","--work-tree=.","--literal-pathspecs","cat-file","--batch"]
git-annex: internal error: evacuate: strange closure type 4325407
(GHC version 8.2.2 for x86_64_unknown_linux)
Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug

I ran the same command again; got the same (promising!). Then I added 
"--foreground" hoping to get some more debug outout... and isntead, it 
decided to work. The working log is (of course) longer, it looks like:


[2018-05-27 15:57:10.648904305] main: starting assistant version 6.20180509
[2018-05-27 15:57:10.652259294] read: git 
["--git-dir=.git","--work-tree=.","--literal-pathspecs","show-ref","git-annex"]
[2018-05-27 15:57:10.712408937] process done ExitSuccess
[2018-05-27 15:57:10.712560137] read: git 
["--git-dir=.git","--work-tree=.","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"]
[2018-05-27 15:57:10.715542944] process done ExitSuccess
[2018-05-27 15:57:10.716916651] chat: git 
["--git-dir=.git","--work-tree=.","--literal-pathspecs","cat-file","--batch"]
[2018-05-27 15:57:10.717421932] chat: git 
["--git-dir=.git","--work-tree=.","--literal-pathspecs","cat-file","--batch-check=%(objectname)
 %(objecttype) %(objectsize)"]
[2018-05-27 15:57:10.843564188] Cronner: waiting Seconds {fromSeconds = 43369} 
for next scheduled fsck self 15m every day at 4 AM
[2018-05-27 15:57:10.958325684] read: git 
["--git-dir=.git","--work-tree=.","--literal-pathspecs","ls-files","--stage","-z","--","."]
[2018-05-27 15:57:11.034783419] process done ExitSuccess
[2018-05-27 15:57:11.034973766] read: git 
["--git-dir=.git","--work-tree=.","--literal-pathspecs","ls-files","--stage","-z","--","."]
[2018-05-27 15:57:11.162696] process done ExitSuccess
[2018-05-27 15:57:11.250761052] chat: nice 
["ionice","-c3","nocache","/usr/bin/git-annex","remotedaemon","--foreground"]
[2018-05-27 15:57:11.251914205] TransferScanner: Syncing with zia, einstein
[2018-05-27 15:57:11.3242642] TransferWatcher: watching for transfers
[2018-05-27 15:57:11.324391068] MountWatcher: Using running DBUS service 

Bug#900233: zip: Files created with zip -e do not ask for a password when using unzip

[Santiago Vila]

On Sun, May 27, 2018 at 03:32:53PM -0400, Ankman wrote:

> this does only occur on my machine [...]

So, how can you be sure it's a bug in the zip package and not, for
example, a hardware problem in your computer?

In case it helps, these are the kind of questions I would ask myself
if this happened to me. Can you provide the answers?


Does it happen in a newly installed Debian 9 system?

Does it happen in a newly installed Debian 9 system upgraded to testing?

Is the zip command the one from the Debian package, or maybe you tried
to compile and install it by hand yourself?

Is the zip command corrupted on disk? (Try "debsums zip" to check)

Is your RAM healthy? (Try memtest+ to check).

Do you have an alias for the zip command?

Are you executing zip inside an emacs buffer?

Does the problem still happen if you do "apt-get --reinstall install zip"?


[ As you may have guessed by now, it is almost sure that I will not be
  able to do anything about this bug if you do not provide a lot more of
  information about it. ]

Thanks.

Bug#900203: guile-2.2 FTCBFS for mipsel: In procedure load-thunk-from-memory: No such file or directory

[Rob Browning]

Helmut Grohne  writes:

> Source: guile-2.2
> Version: 2.2.3+1-4
> User: helm...@debian.org
> Usertags: rebootstrap
>
> I assume that guile-2.2 is supposed to replace guile-2.0 eventually. At
> present, guile-2.0 is part of the bootstrap set and thus needs to be
> cross buildable. Thus it seems safe to say that guile-2.2 should be
> cross buildable eventually. Better start now. Well it doesn't work.

What's the top-level debian/rules invocation/environment?  i.e. how
would I reproduce this?

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#900068: searx cannot run in uWSGI; CI fails as well

[Johannes Schauer]

A trivial workaround for this issue is the following patch:

--- a/debian/tests/general
+++ b/debian/tests/general
@@ -7,6 +7,7 @@ cp /usr/share/doc/searx/examples/nginx/sites-available/searx 
/etc/nginx/sites-av
 ln -s ../sites-available/searx /etc/nginx/sites-enabled/searx
 cp /usr/share/doc/searx/examples/uwsgi/apps-available/searx.ini 
/etc/uwsgi/apps-available
 ln -s ../apps-available/searx.ini /etc/uwsgi/apps-enabled/searx.ini
+sed -i 's/autoload = true/#autoload = true/' /usr/share/uwsgi/conf/default.ini
 mkdir /etc/searx
 gzip --to-stdout --decompress /usr/share/doc/searx/examples/settings.yml.gz > 
/etc/searx/settings.yml
 sed -i -e "s/ultrasecretkey/$(openssl rand -hex 16)/g" /etc/searx/settings.yml

I'm not tagging this bug patch because this is not the proper fix. It should
not be necessary to mess around in /usr/share/uwsgi to make this work. More
details can be found in #900174.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#900174: uwsgi: Segmentation fault with searx and even simple python3 application

[Johannes Schauer]

Control: affets -1 + libcap-ng searx

On Sun, 27 May 2018 07:18:27 +0200 Johannes 'josch' Schauer  
wrote:
> Now upgrade the system to some new package versions of six days later:
> 
> # echo 'deb http://snapshot.debian.org/archive/debian/20180430T00Z 
> sid main' > /etc/apt/sources.list
> # apt update -o Acquire::Check-Valid-Until=false
> # apt upgrade -o Acquire::Check-Valid-Until=false
> 
> The following packages will be upgraded:
> 
> file gcc-8-base ifupdown libargon2-0 libaudit-common libaudit1
> libcap-ng0 libgcc1 liblognorm5 libmagic-mgc libmagic1 libncurses5
> libncursesw5 libnorm1 libreadline7 libseccomp2 libstdc++6 libtinfo5
> libzstd1 ncurses-base ncurses-bin perl-base vim-common vim-tiny xxd
> zlib1g
> 
> After this upgrade, try restarting uwsgi and witness that it now fails

After poking around a bit, it turns out that upgrading libcap-ng0 from
0.7.7-3.1+b1 to 0.7.9-1 triggers this problem.

A workaround in case of searx (and maybe others) is to comment the line

autoload = true

in /usr/share/uwsgi/conf/default.ini. If that line is commented, then it will
work again even after upgrading libcap-ng0.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#900214: RFS: elpy/1.21.0-1

[Chris Lamb]

tags 900214 + pending
thanks

> I am looking for a sponsor for my package "elpy"

Uploaded. :P)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#867731: RFS: smart-mode-line/2.11.0-1 [ITP]

[Chris Lamb]

Hi Nicholas,

> OTTO documentation

(Hm?)

> I'm thinking about a mini-project that could save a lot of people time and
> that might encourage every maintainer to provide a README.source ;-)

Only if it contains genuinely useful info specific to that package --
would really love to avoid the "boy who cried wolf" with that file.

See, for example, this bug report from 2009:

  https://bugs.debian.org/543260


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#900027: vlc: VLC doesn't parse arguments properly

[Cyr Bol]

It turned out I was adding an extraneous space after the backslash at line
4:

 /usr/bin/cvlc -vvv \
 screen:// :screen-fps=30 \
--canvas-width=1280 --canvas-height=720 \
--sout-transcode-vcodec=h264 \
 --sout-x264-profile=high --sout-x264-level=3.1 \
 --sout-x264-vbv-maxrate=5000 --sout-x264-vbv-bufsize=8000
--sout-x264-vbv-init=0.2 \
 --input-slave=pulse://alsa_output.pci-_00_03.0.hdmi-surround.monitor
--sout-transcode-acodec=aac \
...

That was a little bit stupid, sorry.

Please close the bug.

Cyrille


On Fri, May 25, 2018 at 9:12 AM, Cyr Bol  wrote:

> well, that's strange...
>
> That's true that when I run these commands on the command line, and go
> back to the histroy afterwards, I can see it translated to something like:
>
>  screen:// :screen-fps=30 --canvas-width=1280
> --canvas-height=720 --sout-transcode-vcodec=h264
>  --sout-x264-profile=high --sout-x264-level=3.1
>  --sout-x264-vbv-maxrate=5000 --sout-x264-vbv-bufsize=8000
> --sout-x264-vbv-init=0.2  --input-slave=pulse://alsa_out
> put.pci-_00_03.0.hdmi-surround.monitor --sout-transcode-acodec=aac \
>
> So, I can see it interpreted by the shell indeed
>
> Could it be that VLC has issues with all the spaces generate by the shell
> between the arguments?
>
> I will test that further when I'll have access to my machine.
>
> BR
>
> On Thu, May 24, 2018 at 10:17 PM, Sebastian Ramacher  > wrote:
>
>> Control: tags -1 + moreinfo
>>
>> On 2018-05-24 22:05:56, Cyrille wrote:
>> > Package: src:vlc
>> > Version: 3.0.2-1+b1
>> > Severity: normal
>> >
>> > Dear Maintainer,
>> >
>> > VLC doesn't parse arguments properly.
>> >
>> > How to reproduce?
>> >
>> > Create a shell script with the following content:
>> >
>> > #!/bin/sh
>> >
>> > # start VLC
>> > /usr/bin/cvlc -vvv \
>> > screen:// :screen-fps=30 \
>> > --canvas-width=1280 --canvas-height=720
>> --sout-transcode-vcodec=h264 \
>> > --sout-x264-profile=high --sout-x264-level=3.1 \
>> > --sout-x264-vbv-maxrate=5000 --sout-x264-vbv-bufsize=8000
>> --sout-x264-vbv-init=0.2 \
>> > 
>> > --input-slave=pulse://alsa_output.pci-_00_03.0.hdmi-surround.monitor
>> --sout-transcode-acodec=aac \
>> > --sout-transcode-ab=192 --sout-transcode-channels=2
>> --sout-transcode-samplerate=48000 \
>> > --sout 
>> > '#transcode{venc=x264{preset=ultrafast}}:rtp{sdp=rtsp://:9090/kodi.sdp}'
>> 2>&1
>> >
>> > launch it. You can now connect to your computer at the follwing URI and
>> watch your screen streamed in RTP.
>> >
>> > Now, modify this script as follow:
>> >
>> > #!/bin/sh
>> >
>> > # start VLC
>> > /usr/bin/cvlc -vvv \
>> > screen:// :screen-fps=30 \
>> > --canvas-width=1280 --canvas-height=720 \
>> > --sout-transcode-vcodec=h264 \
>> > --sout-x264-profile=high --sout-x264-level=3.1 \
>> > --sout-x264-vbv-maxrate=5000 --sout-x264-vbv-bufsize=8000
>> --sout-x264-vbv-init=0.2 \
>> > 
>> > --input-slave=pulse://alsa_output.pci-_00_03.0.hdmi-surround.monitor
>> --sout-transcode-acodec=aac \
>> > --sout-transcode-ab=192 --sout-transcode-channels=2
>> --sout-transcode-samplerate=48000 \
>> > --sout 
>> > '#transcode{venc=x264{preset=ultrafast}}:rtp{sdp=rtsp://:9090/kodi.sdp}'
>> 2>&1
>> >
>> > launch it, and watch VLC freak out...
>> >
>> > 100% reproductible here.
>>
>> You'll need to be a little bit more specific. The difference
>>
>> @@ -1,6 +1,7 @@
>>  /usr/bin/cvlc -vvv \
>>  screen:// :screen-fps=30 \
>> ---canvas-width=1280 --canvas-height=720
>> --sout-transcode-vcodec=h264 \
>> +--canvas-width=1280 --canvas-height=720 \
>> +--sout-transcode-vcodec=h264 \
>>  --sout-x264-profile=high --sout-x264-level=3.1 \
>>  --sout-x264-vbv-maxrate=5000 --sout-x264-vbv-bufsize=8000
>> --sout-x264-vbv-init=0.2 \
>>  --input-slave=pulse://alsa_output.pci-_00_03.0.hdmi-surround.monitor
>> --sout-transcode-acodec=aac \
>>
>> isn't even visible to vlc, since that's interpreted by the shell.
>>
>> Cheers
>>
>> >
>> > Best regards,
>> >
>> > Cyrille
>> > -- System Information:
>> > Debian Release: buster/sid
>> >   APT prefers testing
>> >   APT policy: (500, 'testing')
>> > Architecture: amd64 (x86_64)
>> >
>> > Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
>> > Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8),
>> LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
>> > Shell: /bin/sh linked to /bin/dash
>> > Init: systemd (via /run/systemd/system)
>> > LSM: AppArmor: enabled
>> >
>> > Versions of packages vlc depends on:
>> > ii  vlc-bin  3.0.2-1+b1
>> > ii  vlc-plugin-base  3.0.2-1+b1
>> > ii  vlc-plugin-qt3.0.2-1+b1
>> > ii  vlc-plugin-video-output  3.0.2-1+b1
>> >
>> > Versions of packages vlc recommends:
>> > ii  vlc-l10n   3.0.2-1
>> > ii  vlc-plugin-notify  

Bug#900234: O: bugz -- command-line interface to Bugzilla

[Mattia Rizzolo]

Package: wnpp

The current maintainer of bugz, Rolf Leggewie ,
has orphaned this package.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: bugz
Binary: bugz
Version: 0.10.1-6
Maintainer: Debian QA Group 
Uploaders: Rolf Leggewie 
Build-Depends: debhelper (>= 9), python
Architecture: all
Standards-Version: 3.9.4
Format: 3.0 (quilt)
Files:
 282cbe49b9e24d9bffd43c58e841d959 1833 bugz_0.10.1-6.dsc
 cda5b7b3316df5143d36570a2837de1a 23142 bugz_0.10.1.orig.tar.gz
 b90c35a7d85ebc3a767c0ab1d4cbd572 3304 bugz_0.10.1-6.debian.tar.xz
Vcs-Browser: https://github.com/leggewie-DM/bugz
Vcs-Git: https://github.com/leggewie-DM/bugz.git
Checksums-Sha256:
 9bd070ca7431cad17c012f3e823aeb1ebf5c8e08aaf78f95d3f2d723996154c9 1833 
bugz_0.10.1-6.dsc
 e8bd14e11b4c244767216dffcfa1bf5b4058d296638c6509f43dd84be8156cec 23142 
bugz_0.10.1.orig.tar.gz
 df7828595138b0202ba772c0367f877acd9bb945c0417d0fb41460be0f204e58 3304 
bugz_0.10.1-6.debian.tar.xz
Homepage: http://www.liquidx.net/pybugz/
Package-List: 
 bugz deb misc optional arch=all
Directory: pool/main/b/bugz
Priority: source
Section: misc

Package: bugz
Version: 0.10.1-6
Installed-Size: 86
Maintainer: Debian QA Group 
Architecture: all
Provides: python-bugz
Depends: python (>= 2.7), python (<< 2.8), python:any (>= 2.6.6-7~)
Description: command-line interface to Bugzilla
Description-md5: f981c52cb13e3054a077e596ceaecd3a
Homepage: http://www.liquidx.net/pybugz/
Tag: devel::bugtracker, implemented-in::python, role::program,
 works-with::bugs
Section: misc
Priority: optional
Filename: pool/main/b/bugz/bugz_0.10.1-6_all.deb
Size: 19008
MD5sum: d91a7f0605b0b23ed06ef7203ca82a93
SHA256: 9a1452cc1efc999a504f46e13a52998bd2f616607b88e68f5c2948834ec1aeb9


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#885407: raising severity of this report

[Mike Gabriel]

HI Niels,

On  Sa 26 Mai 2018 11:19:00 CEST, Niels Thykier wrote:


Control: severity -1 important

On Tue, 30 Jan 2018 20:15:31 + Mike Gabriel
 wrote:

Control: severity -1 serious

Dear CDBS maintainers,

this issue really becomes bothering... Thus, raising severity to an RC
bug. (All people switch to DH compat level 11 these days).

Thanks for maintaing CDBS,
Mike

--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



Hi,

I can certainly appreciate that cdbs's lack of support compat 11 is
frustrating and I would personally also very much like to see cdbs add
support for compat 11 in buster.

However, cdbs does work with the stable non-deprecated compat versions 9
and 10.  Contributors using cdbs can (and should) simply stick with
those compat versions for now.  I see no reason why we should consider
either stalling the release or removing cdbs for lack of compat 11
support in buster.  As such I am downgrading this to important for now.

Of course, the situation is likely to change after the buster release if
the bug remains unfixed.

Thanks,
~Niels


I agree... Still, I would love to see CDBS keeping up the pace with DH  
development.


Question to the maintainers / developers:

How is the current status of CDBS development?
Who actively maintains CDBS?
Patches should be sent to Debian BTS?
Is anyone working on this bug?

Thanks+Greets,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpablEbzUkDG.pgp
Description: Digitale PGP-Signatur

Bug#900233: zip: Files created with zip -e do not ask for a password when using unzip

[Ankman]

Package: zip
Version: 3.0-11+b1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Creating a zip file with the option -e
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
zip -e secret.zip open.txt
   * What was the outcome of this action?
A zip file created with "zip -e ..." doesn't prompt for a password when using 
"unzip secret.zip".
   * What outcome did you expect instead?
To prompt for a password. Let me add that this does only occur on my machine 
while on other Debian versions and other Linux flavors I could test it does NOT 
occur. Also zip -P ... does work here.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (1001, 'testing')
Architecture: i386 (i686)

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

Versions of packages zip depends on:
ii  libbz2-1.0  1.0.6-8.1
ii  libc6   2.27-3

Versions of packages zip recommends:
ii  unzip  6.0-21

zip suggests no packages.

-- no debconf information

Bug#764557: Problem persists

[Michael Biebl]

Control: tags -1 + moreinfo

Hi

On Tue, 10 Oct 2017 18:51:33 +0200 Michael Biebl  wrote:
> Please reopen or file a new bug report, if you still experience specific
> problems with journald.

You reopened the bug report in the mean time.
Does that mean, journalctl still hangs when you have those corrupt
journal files?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#892258: Please package latest upstream

[Andreas Moog]

On Wed, Mar 07, 2018 at 05:19:24PM +0530, Pirate Praveen wrote:
> On March 7, 2018 2:54:29 PM GMT+05:30, Julien Puydt 
>  wrote:
> >Package: node-resolve
> >Version: 1.4.0-1
> >Severity: wishlist
> >
> >Upstream released version 1.5.0, and it's needed to update one of my
> >packages.
> >
> >I can help on the git repo like last time if you want,
> 
> Just do the right thing for all team maintained packages. In case of breaking 
> changes, test all reverse dependencies. 

I did a quick rebuild and test with autopkgtest and found that the newest
version (1.7.1) unfortunately breaks node-browser-resolve, version 1.6.0
however doesn't seem to break any packages. What version of node-resolve do you
need in your package, Julien?

-- 
PGP-encrypted mails preferred
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624


signature.asc
Description: PGP signature

Bug#832566: systemd-machined breaks automounting nfs shares

[Michael Biebl]

On Mon, 26 Mar 2018 07:29:34 +1030 John Pearson  wrote:
> Hi Michael,
> 
> If I disable libvirtd, systemd-machined isn't started.
> 
> Can't say if this problem also occurs in Stretch - this is the only 
> machine with this configuration I have access to, and upgrading to 
> Stretch is on hold due to other considerations; I'll see if I can create 
> a similar environment to check, or failing that report back when it's 
> upgraded.

Any news here?

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#900232: collectd: FTBFS: sed: can't read /usr/lib/pkgconfig/OpenIPMIpthread.pc: No such file or directory

[Niko Tyni]

Source: collectd
Version: 5.8.0-5
Severity: serious

This package fails to build from source on current sid.

It probably broke with

openipmi (2.0.25-1) unstable; urgency=medium

  [...]
  * move pkg-config files to a multiarch location. Thanks Helmut
closes: Bug#852739
  [...]

 -- Noël Köthe   Fri, 18 May 2018 13:44:36 +0200


>From the build log:

  # This is a work-around for #474087 (broken openipmi .pc files).
  mkdir debian/pkgconfig
  sed -re 's/^(Requires:.*) pthread(.*)$/\1\2/' \
/usr/lib/pkgconfig/OpenIPMIpthread.pc \
> debian/pkgconfig/OpenIPMIpthread.pc
  sed: can't read /usr/lib/pkgconfig/OpenIPMIpthread.pc: No such file or 
directory
  make: *** [debian/rules:205: build-stamp] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
 
-- 
Niko Tyni   nt...@debian.org

Bug#429577: #429577: ITP: emacs-snapshot -- The GNU Emacs editor (development snapshot)

[Rob Browning]

David Bremner  writes:

> As far as I know checking is a manual process with the stable emacs
> uploads. But there are many fewer such uploads.

Right.  At the moment, I don't have any package-level automated testing.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#839046: [PATCH] Enable merged-/usr by default again now that dpkg-shlibdeps is fixed (Closes: #839046)

[Raphael Hertzog]

Hi,

On Sun, 27 May 2018, Hideki Yamane wrote:
> On Tue, 22 May 2018 16:21:01 +0200
> Raphael Hertzog  wrote:
> > I don't understand your question. The required fixes are in the version of
> > dpkg that is in stretch.
> 
>  I mean, if we try to create new stretch chroot with merged-usr,
>  it becomes to be NOT equal to stretch environment since its /lib*,
>  /bin and /sbin are merged to /usr. We should not apply it for pre-buster,
>  IMHO.

The same will hold true even for buster+1 given that stretch will
still be supported at that time.

If anything your argument would mean that we should have different default
for the --merged-usr flag for different release. This might indeed be
important if we want to make sure that recent debootstrap do not introduce
unexpected problems when building chroot for very old releases.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#881882: libuv1-dev: [hurd-i386] undefined references to uv__io_poll et al.

[Samuel Thibault]

Samuel Thibault, le dim. 27 mai 2018 20:38:59 +0200, a ecrit:
> Aaron M. Ucko, le mer. 15 nov. 2017 20:21:02 -0500, a ecrit:
> > The build of libstorj for hurd-i386 (admittedly not a release
> > architecture) failed because libuv had undefined references to symbols
> > it should have defined internally:
> > 
> > /usr/lib/i386-gnu/libuv.so: undefined reference to `uv__io_check_fd'
> > /usr/lib/i386-gnu/libuv.so: undefined reference to 
> > `uv__platform_loop_delete'
> > /usr/lib/i386-gnu/libuv.so: undefined reference to `uv__hrtime'
> > /usr/lib/i386-gnu/libuv.so: undefined reference to 
> > `uv__platform_invalidate_fd'
> > /usr/lib/i386-gnu/libuv.so: undefined reference to `uv__io_poll'
> > /usr/lib/i386-gnu/libuv.so: undefined reference to `uv__platform_loop_init'
> > /usr/lib/i386-gnu/libuv.so: undefined reference to `uv__fs_event_close'
> 
> We have the same issue with cmake (which is very problematic of course
> :) ). The attached patch is fixing it.

I forgot to make uv-posix.h installed, here is the fixed patch.

Samuel
Index: libuv1-1.20.3/Makefile.am
===
--- libuv1-1.20.3.orig/Makefile.am
+++ libuv1-1.20.3/Makefile.am
@@ -389,6 +389,13 @@ libuv_la_SOURCES += src/unix/bsd-ifaddrs
 test_run_tests_LDFLAGS += -lutil
 endif
 
+if HURD
+include_HEADERS += include/uv-posix.h
+libuv_la_SOURCES += src/unix/no-fsevents.c \
+src/unix/posix-hrtime.c \
+src/unix/posix-poll.c
+endif
+
 if LINUX
 include_HEADERS += include/uv-linux.h
 libuv_la_CFLAGS += -D_GNU_SOURCE
Index: libuv1-1.20.3/configure.ac
===
--- libuv1-1.20.3.orig/configure.ac
+++ libuv1-1.20.3/configure.ac
@@ -56,6 +56,7 @@ AM_CONDITIONAL([CYGWIN],   [AS_CASE([$ho
 AM_CONDITIONAL([DARWIN],   [AS_CASE([$host_os],[darwin*],   [true], [false])])
 AM_CONDITIONAL([DRAGONFLY],[AS_CASE([$host_os],[dragonfly*],[true], [false])])
 AM_CONDITIONAL([FREEBSD],  [AS_CASE([$host_os],[*freebsd*], [true], [false])])
+AM_CONDITIONAL([HURD], [AS_CASE([$host_os],[gnu*],  [true], [false])])
 AM_CONDITIONAL([LINUX],[AS_CASE([$host_os],[linux*],[true], [false])])
 AM_CONDITIONAL([MSYS], [AS_CASE([$host_os],[msys*], [true], [false])])
 AM_CONDITIONAL([NETBSD],   [AS_CASE([$host_os],[netbsd*],   [true], [false])])
Index: libuv1-1.20.3/debian/libuv1.symbols
===
--- libuv1-1.20.3.orig/debian/libuv1.symbols
+++ libuv1-1.20.3/debian/libuv1.symbols
@@ -22,14 +22,14 @@ libuv.so.1 libuv1 #MINVER#
  (arch=linux-any)uv__eventfd2@Base 1.11.0
  (arch=linux-any)uv__eventfd@Base 1.11.0
  uv__free@Base 1.11.0
- (arch=!hurd-any)uv__fs_event_close@Base 1.11.0
+ uv__fs_event_close@Base 1.11.0
  uv__fs_poll_close@Base 1.11.0
  uv__fs_scandir_cleanup@Base 1.11.0
  uv__getaddrinfo_translate_error@Base 1.11.0
  uv__getiovmax@Base 1.11.0
  uv__getpwuid_r@Base 1.11.0
  uv__handle_type@Base 1.11.0
- (arch=!hurd-any)uv__hrtime@Base 1.11.0
+ uv__hrtime@Base 1.11.0
  uv__idle_close@Base 1.11.0
  (arch=linux-any)uv__inotify_add_watch@Base 1.11.0
  (arch=linux-any)uv__inotify_fork@Base 1.18.0
@@ -37,12 +37,12 @@ libuv.so.1 libuv1 #MINVER#
  (arch=linux-any)uv__inotify_init@Base 1.11.0
  (arch=linux-any)uv__inotify_rm_watch@Base 1.11.0
  uv__io_active@Base 1.11.0
- (arch=!hurd-any)uv__io_check_fd@Base 1.11.0
+ uv__io_check_fd@Base 1.11.0
  uv__io_close@Base 1.11.0
  uv__io_feed@Base 1.11.0
- (arch=!hurd-any)uv__io_fork@Base 1.18.0
+ uv__io_fork@Base 1.18.0
  uv__io_init@Base 1.11.0
- (arch=!hurd-any)uv__io_poll@Base 1.11.0
+ uv__io_poll@Base 1.11.0
  uv__io_start@Base 1.11.0
  uv__io_stop@Base 1.11.0
  uv__loop_close@Base 1.11.0
@@ -58,9 +58,9 @@ libuv.so.1 libuv1 #MINVER#
  uv__open_file@Base 1.11.0
  (arch=linux-any)uv__pipe2@Base 1.11.0
  uv__pipe_close@Base 1.11.0
- (arch=!hurd-any)uv__platform_invalidate_fd@Base 1.11.0
- (arch=!hurd-any)uv__platform_loop_delete@Base 1.11.0
- (arch=!hurd-any)uv__platform_loop_init@Base 1.11.0
+ uv__platform_invalidate_fd@Base 1.11.0
+ uv__platform_loop_delete@Base 1.11.0
+ uv__platform_loop_init@Base 1.11.0
  uv__poll_close@Base 1.11.0
  (arch=linux-any)uv__preadv@Base 1.11.0
  uv__prepare_close@Base 1.11.0
@@ -146,9 +146,9 @@ libuv.so.1 libuv1 #MINVER#
  uv_fs_close@Base 1.4.2
  uv_fs_copyfile@Base 1.18.0
  uv_fs_event_getpath@Base 1.4.2
- (arch=!hurd-any)uv_fs_event_init@Base 1.4.2
- (arch=!hurd-any)uv_fs_event_start@Base 1.4.2
- (arch=!hurd-any)uv_fs_event_stop@Base 1.4.2
+ uv_fs_event_init@Base 1.4.2
+ uv_fs_event_start@Base 1.4.2
+ uv_fs_event_stop@Base 1.4.2
  uv_fs_fchmod@Base 1.4.2
  uv_fs_fchown@Base 1.4.2
  uv_fs_fdatasync@Base 1.4.2
Index: libuv1-1.20.3/include/uv-unix.h
===
--- libuv1-1.20.3.orig/include/uv-unix.h
+++ libuv1-1.20.3/include/uv-unix.h
@@ -64,6 +64,8 @@
 # include "uv-bsd.h"
 #elif 

Bug#900231: rhythmbox: Fails to open databases owned by another users but with r/w permissions

[Genomian]

Package: rhythmbox
Version: 3.4.1-2+b1
Severity: normal

Dear Maintainer,

rhythmbox fails to open a database when it's owned by another user but it has
r/w permissions on it by group or other means

Do:

# chmod 664 $YOURUSERHOME/.local/share/rhythmbox/*
# chown -R $OTHERUSER:$YOURUSER $YOURUSERHOME/.local/share/rhythmbox
Open rhythmbox

Rhythmbox will show a blank database because he thinks that he cannot open
files owned by another user



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

Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages rhythmbox depends on:
ii  dbus1.10.24-0+deb9u1
ii  gstreamer1.0-plugins-base   1.10.4-1
ii  gstreamer1.0-plugins-good   1.10.4-1
ii  gstreamer1.0-x  1.10.4-1
ii  libc6   2.24-11+deb9u1
ii  libglib2.0-02.50.3-2
ii  libgstreamer-plugins-base1.0-0  1.10.4-1
ii  libgstreamer1.0-0   1.10.4-1
ii  libgtk-3-0  3.22.11-1
ii  libpeas-1.0-0   1.20.0-1+b1
ii  librhythmbox-core10 3.4.1-2+b1
ii  libx11-62:1.6.4-3
ii  media-player-info   22-3
ii  rhythmbox-data  3.4.1-2

Versions of packages rhythmbox recommends:
ii  avahi-daemon0.6.32-2
ii  gnome-shell [notification-daemon]   3.22.3-3
ii  gstreamer1.0-plugins-ugly   1.10.4-1
ii  gstreamer1.0-pulseaudio 1.10.4-1
ii  gvfs-backends   1.30.4-1
ii  plasma-workspace [notification-daemon]  4:5.8.6-2.1+deb9u1
ii  rhythmbox-plugins   3.4.1-2+b1
ii  yelp3.22.0-1

Versions of packages rhythmbox suggests:
pn  gnome-codec-install  
ii  gnome-control-center 1:3.22.2-3
ii  gstreamer1.0-plugins-bad 1.10.4-1
ii  rhythmbox-plugin-cdrecorder  3.4.1-2+b1

-- debconf-show failed

Bug#898209: charliecloud: Change service by systemd in po-debconf

[Peter Wienemann]

Dear Alban,

thanks for providing this patch which I gladly applied.

Shall I simply go ahead and do the "translations" of "systemctl restart
procps" in the various po files myself (to avoid bothering the
translators with such a straightforward change) or would that interfere
with the workflow of the language teams?

Best regards,

Peter

On 08.05.2018 20:26, Alban Vidal wrote:
> Package: charliecloud
> Version: 0.2.3-2
> Severity: wishlist
> Tags: patch
> 
> Dear mainteners,
> 
> I suggest to change the following lines in po-debconf for systemd.
> 
> Current:
> service procps restart
> 
> Proposal:
> systemctl restart procps
> 
> Best regards,
> 
> Alban Vidal

Bug#900230: nqp: autopkgtest times out

[Paul Gevers]

Source: nqp
Version: 2018.03+dfsg-2
Severity: normal
User: debian...@lists.debian.org
Usertags: regression timeout

Since version 2018.03+dfsg-2, the autopkgtests¹ are timing out (~ 3
hours) while previous runs tested in about 1 minute.
Could you please investigate how to get rid of the timeout?

I will blacklist nqp on ci.debian.net for now, but will reactivate it
when this bug is closed and the test doesn't time out anymore.

A note about time outs. If it really takes this much time to run the
tests, time outs can often be worked around by splitting a test into
multiple autopkgtest because each gets its own timeout. On the other
hand, if that is the case, is 3 hours or more on the ci.d.n really worth it?

Don't hesitate to ask for help for the Debian CI team² if you need help
solving this issue.

Paul

¹ https://ci.debian.net/packages/n/nqp
² #debci on oftc or debian...@lists.debian.org

https://ci.debian.net/data/autopkgtest/unstable/amd64/n/nqp/367665/log.gz

autopkgtest [04:33:54]: test command1: [---
t/concurrency/01-thread.t .. ok
t/concurrency/02-lock.t  ok
t/concurrency/03-semaphore.t ... ok
t/concurrency/04-osr-crash.t ... ok
t/hll/01-language.t  skipped: design changes, need
re-work
t/hll/02-modules.t . skipped: design changes, need
re-work
t/hll/03-exports.t . skipped: design changes (EXPORT
now lexical), need re-work
t/hll/04-import.t .. skipped: design changes (EXPORT
now lexical), need re-work
t/hll/05-commandline.t . ok
t/hll/06-sprintf.t . ok
t/moar/01-continuations.t .. ok
t/moar/02-qast-references.t  ok
t/moar/03-line-seps.t .. ok
t/moar/04-argument-truncation.t  ok
t/moar/05-decoder.t  ok
t/moar/07-eqatic.t . ok
t/moar/08-indexic.t  ok
t/moar/09-concat.t . ok
t/moar/10-eqatim.t . ok
t/moar/11-decode.t . ok
t/moar/50-jit-register-alloc.t . ok
t/moar/51-jit-div_i.t .. ok
t/nativecall/01-basic.t  ok
t/nqp/001-literals.t ... ok
t/nqp/002-if.t . ok
t/nqp/003-if-else.t  ok
t/nqp/004-unless.t . ok
t/nqp/005-comments.t ... ok
t/nqp/006-args-pos.t ... ok
t/nqp/007-boolean.t  ok
t/nqp/008-blocks.t . ok
t/nqp/009-var.t  ok
t/nqp/010-cmp.t  ok
t/nqp/011-sub.t  ok
t/nqp/012-logical.t  ok
t/nqp/013-op.t . ok
t/nqp/014-while.t .. ok
t/nqp/015-list.t ... ok
t/nqp/016-ternary.t  ok
t/nqp/017-positional.t . ok
t/nqp/018-associative.t  ok
t/nqp/019-file-ops.t ... ok
t/nqp/020-return.t . ok
t/nqp/021-contextual.t . ok
t/nqp/022-optional-args.t .. ok
t/nqp/023-named-args.t . ok
t/nqp/024-module.t . ok
t/nqp/025-class.t .. ok
t/nqp/026-methodops.t .. ok
t/nqp/027-self.t ... ok
t/nqp/028-subclass.t ... ok
t/nqp/029-make.t ... ok
t/nqp/031-grammar.t  ok
t/nqp/032-protoregex.t . ok
t/nqp/033-init.t ... ok
t/nqp/034-rxcodeblock.t  ok
t/nqp/035-prefix-sigil.t ... ok
t/nqp/036-callable.t ... ok
t/nqp/037-slurpy.t . ok
t/nqp/038-quotes.t . ok
t/nqp/039-pointy.t . ok
t/nqp/040-lists.t .. ok
t/nqp/041-flat.t ... ok
t/nqp/042-cond-loop.t .. ok
t/nqp/043-package-var.t  ok
t/nqp/044-try-catch.t .. ok
t/nqp/045-smartmatch.t . ok
t/nqp/046-charspec.t ... ok
t/nqp/047-loop-control.t ... ok
t/nqp/048-closure.t  ok
t/nqp/049-regex-interpolation.t  ok
t/nqp/050-regex.t .. ok
t/nqp/051-multi.t .. ok
t/nqp/053-knowhow.t  ok
t/nqp/055-multi-method.t ... ok
t/nqp/056-role.t ... ok
t/nqp/057-construction.t ... ok
t/nqp/058-attrs.t .. ok
t/nqp/059-nqpop.t .. ok
t/nqp/060-bigint.t . ok
t/nqp/061-mixin.t .. ok
t/nqp/062-subst.t .. ok
t/nqp/063-slurp.t .. ok
t/nqp/064-native.t . ok
t/nqp/065-how.t  ok
t/nqp/066-pararole.t 

Bug#899979: keyboard-configuration: the caron dead-key of the czech keyboard on the console does not work as expected

[Samuel Thibault]

Anton Zinoviev, le dim. 27 mai 2018 20:05:30 +0300, a ecrit:
> Ah, I didn't know that the compose sequences are used for the dead keys.

Dead keys simply produce compose + '`' or '\'' or '^' or '~' or '"' or
',' yes.

> Compose sequences in console-setup are encoding-based.  See for example 
> /etc/console-setup/compose.ISO-8859-2.inc.

Dcaron is not there. Is it created by hand? All decomposable latin2
characters should be added there then.

Samuel

Bug#900229: O: fteproxy -- programmable proxy for censorship circumvention

[Mattia Rizzolo]

Package: wnpp

The current maintainer of fteproxy, Rolf Leggewie ,
has orphaned this package.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: fteproxy
Binary: fteproxy
Version: 0.2.19-2
Maintainer: Debian QA Group 
Uploaders: Kevin P. Dyer 
Build-Depends: debhelper (>= 9), libgmp-dev, python-dev, python-setuptools
Architecture: any
Standards-Version: 3.9.6
Format: 3.0 (quilt)
Files:
 c0845354f085bc06cfd41f284b4465fc 1925 fteproxy_0.2.19-2.dsc
 0f36f05e6bf4df51fec7b674ef19c71d 35804 fteproxy_0.2.19.orig.tar.gz
 5037ae587917ac73aff7f9649a60a2c2 4988 fteproxy_0.2.19-2.debian.tar.xz
Vcs-Browser: https://github.com/kpdyer/fteproxy/tree/debian/unstable
Vcs-Git: git://g...@github.com:kpdyer/fteproxy.git -b debian/unstable
Checksums-Sha256:
 fdfbb987a56e2be6afae0dd60ea36bb681fed87632f0201bc73e8098666bd900 1925 
fteproxy_0.2.19-2.dsc
 73a56be69f5dce8700b981ff897fe8804c5a4332add98c206b7e75d6bf70e770 35804 
fteproxy_0.2.19.orig.tar.gz
 c665869477612b8f5bf22e64dc667c6b348048a8cfbb65737d90e1e90bd655d4 4988 
fteproxy_0.2.19-2.debian.tar.xz
Homepage: https://fteproxy.org/
Package-List: 
 fteproxy deb net extra arch=any
Directory: pool/main/f/fteproxy
Priority: optional
Section: misc

Package: fteproxy
Version: 0.2.19-2
Installed-Size: 116
Maintainer: Debian QA Group 
Architecture: amd64
Depends: python, python-twisted, obfsproxy (>= 0.2.9), python-pyptlib, 
python-fte
Description: programmable proxy for censorship circumvention
Description-md5: bedb986ce493cdddf55bbd3be9156872
Homepage: https://fteproxy.org/
Section: net
Priority: optional
Filename: pool/main/f/fteproxy/fteproxy_0.2.19-2_amd64.deb
Size: 16968
MD5sum: 4e22cd04479d563efb534ca7a3cd74ea
SHA256: 08d188ae2219c30972b5d50802516102fa28c2bc97880916d39a9d1bcf78436b


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#881882: libuv1-dev: [hurd-i386] undefined references to uv__io_poll et al.

[Samuel Thibault]

Hello,

Aaron M. Ucko, le mer. 15 nov. 2017 20:21:02 -0500, a ecrit:
> The build of libstorj for hurd-i386 (admittedly not a release
> architecture) failed because libuv had undefined references to symbols
> it should have defined internally:
> 
> /usr/lib/i386-gnu/libuv.so: undefined reference to `uv__io_check_fd'
> /usr/lib/i386-gnu/libuv.so: undefined reference to `uv__platform_loop_delete'
> /usr/lib/i386-gnu/libuv.so: undefined reference to `uv__hrtime'
> /usr/lib/i386-gnu/libuv.so: undefined reference to 
> `uv__platform_invalidate_fd'
> /usr/lib/i386-gnu/libuv.so: undefined reference to `uv__io_poll'
> /usr/lib/i386-gnu/libuv.so: undefined reference to `uv__platform_loop_init'
> /usr/lib/i386-gnu/libuv.so: undefined reference to `uv__fs_event_close'

We have the same issue with cmake (which is very problematic of course
:) ). The attached patch is fixing it.

Samuel
Index: libuv1-1.20.3/Makefile.am
===
--- libuv1-1.20.3.orig/Makefile.am
+++ libuv1-1.20.3/Makefile.am
@@ -389,6 +389,12 @@ libuv_la_SOURCES += src/unix/bsd-ifaddrs
 test_run_tests_LDFLAGS += -lutil
 endif
 
+if HURD
+libuv_la_SOURCES += src/unix/no-fsevents.c \
+src/unix/posix-hrtime.c \
+src/unix/posix-poll.c
+endif
+
 if LINUX
 include_HEADERS += include/uv-linux.h
 libuv_la_CFLAGS += -D_GNU_SOURCE
Index: libuv1-1.20.3/configure.ac
===
--- libuv1-1.20.3.orig/configure.ac
+++ libuv1-1.20.3/configure.ac
@@ -56,6 +56,7 @@ AM_CONDITIONAL([CYGWIN],   [AS_CASE([$ho
 AM_CONDITIONAL([DARWIN],   [AS_CASE([$host_os],[darwin*],   [true], [false])])
 AM_CONDITIONAL([DRAGONFLY],[AS_CASE([$host_os],[dragonfly*],[true], [false])])
 AM_CONDITIONAL([FREEBSD],  [AS_CASE([$host_os],[*freebsd*], [true], [false])])
+AM_CONDITIONAL([HURD], [AS_CASE([$host_os],[gnu*],  [true], [false])])
 AM_CONDITIONAL([LINUX],[AS_CASE([$host_os],[linux*],[true], [false])])
 AM_CONDITIONAL([MSYS], [AS_CASE([$host_os],[msys*], [true], [false])])
 AM_CONDITIONAL([NETBSD],   [AS_CASE([$host_os],[netbsd*],   [true], [false])])
Index: libuv1-1.20.3/debian/libuv1.symbols
===
--- libuv1-1.20.3.orig/debian/libuv1.symbols
+++ libuv1-1.20.3/debian/libuv1.symbols
@@ -22,14 +22,14 @@ libuv.so.1 libuv1 #MINVER#
  (arch=linux-any)uv__eventfd2@Base 1.11.0
  (arch=linux-any)uv__eventfd@Base 1.11.0
  uv__free@Base 1.11.0
- (arch=!hurd-any)uv__fs_event_close@Base 1.11.0
+ uv__fs_event_close@Base 1.11.0
  uv__fs_poll_close@Base 1.11.0
  uv__fs_scandir_cleanup@Base 1.11.0
  uv__getaddrinfo_translate_error@Base 1.11.0
  uv__getiovmax@Base 1.11.0
  uv__getpwuid_r@Base 1.11.0
  uv__handle_type@Base 1.11.0
- (arch=!hurd-any)uv__hrtime@Base 1.11.0
+ uv__hrtime@Base 1.11.0
  uv__idle_close@Base 1.11.0
  (arch=linux-any)uv__inotify_add_watch@Base 1.11.0
  (arch=linux-any)uv__inotify_fork@Base 1.18.0
@@ -37,12 +37,12 @@ libuv.so.1 libuv1 #MINVER#
  (arch=linux-any)uv__inotify_init@Base 1.11.0
  (arch=linux-any)uv__inotify_rm_watch@Base 1.11.0
  uv__io_active@Base 1.11.0
- (arch=!hurd-any)uv__io_check_fd@Base 1.11.0
+ uv__io_check_fd@Base 1.11.0
  uv__io_close@Base 1.11.0
  uv__io_feed@Base 1.11.0
- (arch=!hurd-any)uv__io_fork@Base 1.18.0
+ uv__io_fork@Base 1.18.0
  uv__io_init@Base 1.11.0
- (arch=!hurd-any)uv__io_poll@Base 1.11.0
+ uv__io_poll@Base 1.11.0
  uv__io_start@Base 1.11.0
  uv__io_stop@Base 1.11.0
  uv__loop_close@Base 1.11.0
@@ -58,9 +58,9 @@ libuv.so.1 libuv1 #MINVER#
  uv__open_file@Base 1.11.0
  (arch=linux-any)uv__pipe2@Base 1.11.0
  uv__pipe_close@Base 1.11.0
- (arch=!hurd-any)uv__platform_invalidate_fd@Base 1.11.0
- (arch=!hurd-any)uv__platform_loop_delete@Base 1.11.0
- (arch=!hurd-any)uv__platform_loop_init@Base 1.11.0
+ uv__platform_invalidate_fd@Base 1.11.0
+ uv__platform_loop_delete@Base 1.11.0
+ uv__platform_loop_init@Base 1.11.0
  uv__poll_close@Base 1.11.0
  (arch=linux-any)uv__preadv@Base 1.11.0
  uv__prepare_close@Base 1.11.0
@@ -146,9 +146,9 @@ libuv.so.1 libuv1 #MINVER#
  uv_fs_close@Base 1.4.2
  uv_fs_copyfile@Base 1.18.0
  uv_fs_event_getpath@Base 1.4.2
- (arch=!hurd-any)uv_fs_event_init@Base 1.4.2
- (arch=!hurd-any)uv_fs_event_start@Base 1.4.2
- (arch=!hurd-any)uv_fs_event_stop@Base 1.4.2
+ uv_fs_event_init@Base 1.4.2
+ uv_fs_event_start@Base 1.4.2
+ uv_fs_event_stop@Base 1.4.2
  uv_fs_fchmod@Base 1.4.2
  uv_fs_fchown@Base 1.4.2
  uv_fs_fdatasync@Base 1.4.2
Index: libuv1-1.20.3/include/uv-unix.h
===
--- libuv1-1.20.3.orig/include/uv-unix.h
+++ libuv1-1.20.3/include/uv-unix.h
@@ -64,6 +64,8 @@
 # include "uv-bsd.h"
 #elif defined(__CYGWIN__) || defined(__MSYS__)
 # include "uv-posix.h"
+#elif defined(__GNU__)
+# include "uv-posix.h"
 #endif
 
 #ifndef PTHREAD_BARRIER_SERIAL_THREAD

Bug#900228: plasma-workspace: Fails to resume login screen after unused

[Genomian]

Package: plasma-workspace
Version: 4:5.8.6-2.1+deb9u1
Severity: important

Dear Mantainer,

plasmashell seems to crash when reaccessin the machine after leaving it unused
for a certain time (with suspend deactivated), audio output usable, possibility
of connecting to the console via other means and such but fails to resume login
screen



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

Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages plasma-workspace depends on:
ii  dbus-x11 1.10.24-0+deb9u1
ii  frameworkintegration 5.28.0-1
ii  gdb-minimal [gdb]7.12-6
ii  iso-codes3.75-1
ii  kactivitymanagerd5.8.4-1
ii  kde-cli-tools4:5.8.4-2
ii  kded55.28.0-1
ii  kinit5.28.0-1
ii  kio  5.28.0-2
ii  kpackagetool55.28.1-1
ii  libc62.24-11+deb9u1
ii  libcln6  1.3.4-2+b1
ii  libdbusmenu-qt5-20.9.3+16.04.20160218-1
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libgps22 3.16-4
ii  libice6  2:1.0.9-2
ii  libkf5activities55.28.0-1
ii  libkf5auth5  5.28.0-2
ii  libkf5baloo5 5.28.0-2
ii  libkf5bookmarks5 5.28.0-1
ii  libkf5calendarevents55.28.0-1
ii  libkf5completion55.28.0-1
ii  libkf5configcore55.28.0-2
ii  libkf5configgui5 5.28.0-2
ii  libkf5configwidgets5 5.28.0-2
ii  libkf5coreaddons55.28.0-2
ii  libkf5crash5 5.28.0-1
ii  libkf5dbusaddons55.28.0-1
ii  libkf5declarative5   5.28.0-1
ii  libkf5globalaccel-bin5.28.0-1
ii  libkf5globalaccel5   5.28.0-1
ii  libkf5guiaddons5 5.28.0-1
ii  libkf5holidays5  16.04.2-1
ii  libkf5i18n5  5.28.0-2
ii  libkf5iconthemes55.28.0-2
ii  libkf5idletime5  5.28.0-1
ii  libkf5itemviews5 5.28.0-1
ii  libkf5jobwidgets55.28.0-2
ii  libkf5js55.28.0-1
ii  libkf5jsembed5   5.28.0-1
ii  libkf5kdelibs4support5   5.28.0-1
ii  libkf5kiocore5   5.28.0-2
ii  libkf5kiofilewidgets55.28.0-2
ii  libkf5kiowidgets55.28.0-2
ii  libkf5networkmanagerqt6  5.28.0-2
ii  libkf5newstuff5  5.28.0-1
ii  libkf5notifications5 5.28.0-1
ii  libkf5notifyconfig5  5.28.0-1
ii  libkf5package5   5.28.1-1
ii  libkf5plasma55.28.0-2
ii  libkf5plasmaquick5   5.28.0-2
ii  libkf5quickaddons5   5.28.0-1
ii  libkf5runner55.28.0-1
ii  libkf5service-bin5.28.0-1
ii  libkf5service5   5.28.0-1
ii  libkf5solid5 5.28.0-3
ii  libkf5texteditor55.28.0-2
ii  libkf5textwidgets5   5.28.0-1
ii  libkf5wallet-bin 5.28.0-3
ii  libkf5wallet55.28.0-3
ii  libkf5waylandclient5 4:5.28.0-1
ii  libkf5widgetsaddons5 5.28.0-3
ii  libkf5windowsystem5  5.28.0-2
ii  libkf5xmlgui55.28.0-1
ii  libkf5xmlrpcclient5  5.28.0-1
ii  libkscreenlocker55.8.6-2
ii  libksgrd74:5.8.4-1
ii  libkworkspace5-5 4:5.8.6-2.1+deb9u1
ii  libphonon4qt5-4  4:4.9.0-4
ii  libplasma-geolocation-interface5 4:5.8.6-2.1+deb9u1
ii  libprocesscore7  4:5.8.4-1
ii  libprocessui74:5.8.4-1
ii  libqalculate5v5  0.9.7-9.2
ii  libqt5core5a 5.7.1+dfsg-3+b1
ii  libqt5dbus5  5.7.1+dfsg-3+b1
ii  libqt5gui5   5.7.1+dfsg-3+b1
ii  libqt5network5

Bug#899102: Cross-submit on Github

[Maximilian Stein]

Hey,

in the meantime, I cross-submitted this bug to the upstream Github
project: https://github.com/imaplib2/imaplib2/issues/3

Best,

Maximilian Stein
E-Mail: m...@steiny.biz 



signature.asc
Description: OpenPGP digital signature

Bug#900227: nss FTBFS on a few architectures: fails linking ibfreeblpriv3.so with undefined references

[Helmut Grohne]

Source: nss
Version: 2:3.37-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

nss fails to build from source on at least armel, armhf, mips and
mipsel. It fails linking libfreeblpriv3.so with lots of undefined
references. For build logs see e.g.

https://buildd.debian.org/status/fetch.php?pkg=nss=armel=2%3A3.37-1=1526257952=0
https://buildd.debian.org/status/fetch.php?pkg=nss=armhf=2%3A3.37-1=1526279305=0
https://buildd.debian.org/status/fetch.php?pkg=nss=mips=2%3A3.37-1=1526253089=0
https://buildd.debian.org/status/fetch.php?pkg=nss=mipsel=2%3A3.37-1=1526264929=0

Since the issue persists for 13 days now and also affects cross builds,
I figured that it is better to have a bug number for it.

Helmut

Bug#900226: sddm: HideUsers options not working

[Genomian]

Package: sddm
Version: 0.14.0-4
Severity: normal

Dear Maintainer,

sddm completely ignores HideUsers options as described in this issue:

https://github.com/sddm/sddm/issues/626

Always reproducible, simply tipe any username in HideUsers and it will be still
shown by the login screen

Also I suggest to checking the commits history of sddm, it seems that there are
many more bugs



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

Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages sddm depends on:
ii  adduser   3.115
ii  debconf [debconf-2.0] 1.5.61
ii  libc6 2.24-11+deb9u1
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libpam0g  1.1.8-3.6
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5dbus5   5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5network55.7.1+dfsg-3+b1
ii  libqt5qml55.7.1-2+b2
ii  libqt5quick5  5.7.1-2+b2
ii  libstdc++66.3.0-18+deb9u1
ii  libsystemd0   232-25+deb9u3
ii  libxcb-xkb1   1.12-1
ii  libxcb1   1.12-1
ii  qml-module-qtquick2   5.7.1-2+b2
ii  x11-common1:7.7+19
ii  xserver-xephyr [xserver]  2:1.19.2-1+deb9u2
ii  xserver-xorg [xserver]1:7.7+19

Versions of packages sddm recommends:
ii  libpam-systemd   232-25+deb9u3
ii  sddm-theme-debian-maui [sddm-theme]  0.14.0-4

Versions of packages sddm suggests:
ii  libpam-kwallet5  5.8.4-1

-- debconf-show failed

Bug#900225: fuser.1: Some changes in the manual

[Bjarni Ingi Gislason]

Package: psmisc
Version: 23.1-1+b1
Severity: minor
Tags: patch

Dear Maintainer,

   * What led up to the situation?

  Warnings from "groff":

:29 (macro RB): only 1 argument, but more are expected
:32 (macro RB): only 1 argument, but more are expected

Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z 

  [ "test-groff" is a developmental version of "groff" ]

  The patch is in the attachment.



  Summary of changes:

Use macros for font changes instead of font escapes

Change a two-fonts macro to an one-font macro for one argument

Add an italic correction (\/) in front of '\c' as that removes the
correction in the macro.

Fix the spelling of "comparisions" and "seatbelt"

Protect '.' if not end of sentence (change " ..." to " \&...\&")

Begin a sentence in a new line

Add a comma after "e.g." (instead of using '\&')



  Details:

Input file is fuser.1

Test nr. 8:

Protect a full stop (.) with "\&", if it has a blank (white-space) in
front of or (ignoring characters transparent to it) after it, and it
does not mean an end of a sentence.

166:shortcut notation \fIname\fB/\fIspace\fR (e.g. \fI80\fB/\fItcp\fR)

#

Test nr. 16:

Use the correct macro for the font change of one argument.
Split a  punctuation mark from the only argument if one is there

29:.RB \-l
32:.RB \-V

#

Test nr. 21:

Use a macro to change to the italic font, instead of \fI [1], if
possible.
The macros have the italic corrections, but "\c" removes them
  or
add the italic corrections.
[1] man-pages(7) [package "manpages"]

91:\fB[\fR\fIlcl_port\fR\fB][\fR,\fB[\fR\fIrmt_host\fR\fB][\fR,\fB[\fIrmt_port\fR\fB]]]
112:\fB\-\fR\fISIGNAL\fR, SIGKILL is sent.  An
135:\fB\-m\fR \fINAME\fR, \fB\-\-mount\fR \fINAME\fR
157:\fB\-n \fISPACE\fR, \fB\-\-namespace\fR \fISPACE\fR
166:shortcut notation \fIname\fB/\fIspace\fR (e.g. \fI80\fB/\fItcp\fR)
179:\fB\-\fISIGNAL\fR
227:\fBif fuser \-s /dev/ttyS1; then :; else \fIsomething\fB; fi\fR

#

Test nr. 40:

Add a comma after "e.g." and "i.e." (man-pages(7) [package "manpages"]).

166:shortcut notation \fIname\fB/\fIspace\fR (e.g. \fI80\fB/\fItcp\fR)
181:Signals can be specified either by name (e.g.
183:number (e.g.

#

Test nr. 41:

Wrong distance between sentences or protect the indicator.

1) Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) [package "manpages"] and "info groff".

Or

2) Adjust space between sentences (two spaces),

3) or protect the indicator by adding "\&" after it.

The "indicator" is an "end-of-sentence character" (.!?).

80:option. By default
121:Ask the user for confirmation before killing a process. This option is

#

Test nr. 42:

Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause.

fuser.1: line 91length 84
\fB[\fR\fIlcl_port\fR\fB][\fR,\fB[\fR\fIrmt_host\fR\fB][\fR,\fB[\fIrmt_port\fR\fB]]]

#


-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.88-1-u1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages psmisc depends on:
ii  libc62.27-3
ii  libselinux1  2.7-2+b2
ii  libtinfo66.1+20180210-4

psmisc recommends no packages.

psmisc suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason
--- fuser.1 2018-05-06 08:19:46.0 +
+++ fuser.1.new 2018-05-27 17:36:59.0 +
@@ -21,15 +21,14 @@ fuser \- identify processes using files
 .RB [ \-i ]
 .RB [ \-M ]
 .RB [ \-w ]
-.RB [ \- \fISIGNAL\fR]
+.RB [ \-\c
+.IR SIGNAL ]
 ]
-.IR name " ..."
+.IR name " \&...\&"
 .br
-.B fuser
-.RB \-l
+.B fuser \-l
 .br
-.B fuser
-.RB \-V
+.B fuser \-V
 .ad b
 .SH DESCRIPTION
 .B fuser
@@ -88,7 +87,7 @@ options.  The socket(s) can be specified
 and the remote address.  All fields are optional, but commas in front
 of missing fields must be present:
 .PP
-\fB[\fR\fIlcl_port\fR\fB][\fR,\fB[\fR\fIrmt_host\fR\fB][\fR,\fB[\fIrmt_port\fR\fB]]]
+.RI [ lcl_port ][,[ rmt_host ][,[ rmt_port ]]]
 .PP
 Either symbolic or numeric values can be used for IP addresses and port
 numbers.
@@ -97,19 +96,21 @@ numbers.
 outputs only the PIDs to stdout, everything else is sent to stderr.
 .SH OPTIONS
 .TP
-\fB\-a\fR, \fB\-\-all\fR
+.BR \-a ", " \-\-all
 Show all files specified on the command line.  By default, only files
 that are accessed by at least one process are shown.
 .TP
-\fB\-c\fR
+.B \-c
 Same as \-m option, used for POSIX compatibility.
 .TP
-\fB\-f\fR
+.B \-f
 Silently ignored, used for POSIX compatibility.
 .TP
-\fB\-k\fR, \fB\-\-kill\fR
+.BR \-k ", "\-\-kill
 Kill processes accessing the file.  Unless changed with

Bug#900217: quakespam FTCBFS: uses the build architecture toolchain

[Stephen Kitt]

On Sun, 27 May 2018 19:28:47 +0200, Helmut Grohne  wrote:
> quakespasm fails to cross build from source, because it uses the build
> architecture toolchain. For the makefile buildsystem being used here,
> the simplest solution is to let dh_auto_build pass cross tools to make.
> While doing so, I figured that debian/rules could be simplified by
> passing --sourcedirectory to dh. Next, the upstream build system hard
> codes the build architecture pkg-config. The attached patch fixes both
> of these issues, but it doesn't make quakespasm cross buildable, because
> it runs into #899138 and thus fails finding opusfile.pc. Please consider
> applying the attached patch anyway and closing this bug when doing so.

Pushed, thanks!

Regards,

Stephen


pgpv4alJCSn9l.pgp
Description: OpenPGP digital signature

Bug#900223: dumpkeys.1: Some changes in the manual

[Bjarni Ingi Gislason]

Package: kbd
Version: 2.0.4-2
Severity: minor
Tags: patch

Dear Maintainer,

   * What led up to the situation?

  Warning from "groff":

:217 (macro BI): only 1 argument, but more are expected

Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z 

  [ "test-groff" is a developmental version of "groff" ]

  The patch is in the attachment.

##

  Summary:

Begin a sentence on a new line

Change "ie." to "i.e.,"

Change '--' to '\-\-' to indicate an option.

Remove unneeded '.LP' lines

Change '-' to '\(en' when it means a numeric range

Change a two-fonts macro to an one-font macro for only one argument

Remove an empty line at the end of the file

###

  Details:

Input file is dumpkeys.1

mandoc: dumpkeys.1:123:2: WARNING: skipping paragraph macro: LP empty
mandoc: dumpkeys.1:123:2: WARNING: skipping paragraph macro: LP empty
mandoc: dumpkeys.1:123:2: WARNING: skipping paragraph macro: LP empty
mandoc: dumpkeys.1:126:2: WARNING: skipping paragraph macro: LP empty
mandoc: dumpkeys.1:138:2: WARNING: skipping paragraph macro: LP empty
mandoc: dumpkeys.1:145:2: WARNING: skipping paragraph macro: LP empty
mandoc: dumpkeys.1:161:2: WARNING: skipping paragraph macro: LP empty
mandoc: dumpkeys.1:164:2: WARNING: skipping paragraph macro: LP empty
mandoc: dumpkeys.1:172:2: WARNING: skipping paragraph macro: LP empty
mandoc: dumpkeys.1:180:2: WARNING: skipping paragraph macro: LP empty
mandoc: dumpkeys.1:187:2: WARNING: skipping paragraph macro: LP empty
mandoc: dumpkeys.1:206:2: WARNING: skipping paragraph macro: LP empty
mandoc: dumpkeys.1:209:2: WARNING: skipping paragraph macro: LP empty
mandoc: dumpkeys.1:213:2: WARNING: skipping paragraph macro: LP empty

###

Test nr. 5:

Change '-' (\-) to '\(en' (en-dash) for a numeric range.

dumpkeys.1:198:Where X is a digit in 1-9.  If no

#

Test nr. 8:

Protect a full stop (.) with "\&", if it has a blank (white-space) in
front of or (ignoring characters transparent to it) after it, and it
does not mean an end of a sentence.

68:definition, ie. the

#

Test nr. 13:

Change -- in x--y to \(em (em-dash), or, if an
option, to \-\-

95:.B --long-info
121:.B dumpkeys --funcs-only
132:.B --short-info

#

Test nr. 16:

Use the correct macro for the font change of one argument.
Split a  punctuation mark from the only argument if one is there

217:.BI /usr/share/keymaps

#

Test nr. 41:

Wrong distance between sentences or protect the indicator.

1) Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) [package "manpages"] and "info groff".

Or

2) Adjust space between sentences (two spaces),

3) or protect the indicator by adding "\&" after it.

The "indicator" is an "end-of-sentence character" (.!?).

38:Prints some characteristics of the kernel's keyboard driver. The items
47:keyword in keytable files. See
56:various modifier keys. If the value is 16 for example, you can define up
57:to 16 different actions to a key combined with modifiers. When the value
68:definition, ie. the
87:usually remain the same. However, the list of action code ranges can be
93:program. To see this, you compare the range list with the action symbol
103:strings of characters. These action codes are traditionally bound to
105:to send standard escape sequences. However, you can redefine these to
110:to send some useful strings. See
131:to print a long information listing. The output is the same as with the
152:and output the key bindings in the canonical form. First a keymaps
154:is printed. Then for each key a row with a column for each
155:modifier combination is printed. For
157:every row will have seven action code columns. This format
169:prints only the function key string definitions. Normally
177:prints only the key bindings. Normally
193:set. This affects only the translation of character code values to
194:symbolic names. Valid values for
204:loadkeys how to interpret the keymap. (For example, "division" is

#

-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.88-1-u1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages kbd depends on:
ii  libc6  2.27-3

Versions of packages kbd recommends:
ii  console-data   2:1.12-6
ii  console-setup  1.184

kbd suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason
--- dumpkeys.1  2017-09-15 08:33:29.0 +
+++ dumpkeys.1.new  2018-05-26 01:01:31.0 +
@@ -35,8 +35,8 @@ Prints the program's version number and
 program's standard error output and exits.
 .TP
 .B \-i \-\-short-info
-Prints some characteristics of the kernel's keyboard driver. The items
-shown are:
+Prints some characteristics 

Bug#900224: fgconsole.1: Some formatting and textual fixes in the manual

[Bjarni Ingi Gislason]

Package: kbd
Version: 2.0.4-2
Severity: minor
Tags: patch

Dear Maintainer,

   * What led up to the situation?

  Warnings from "groff":

:8 (macro BI): only 1 argument, but more are expected
:42 (macro IR): only 1 argument, but more are expected

Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z 

  [ "test-groff" is a developmental version of "groff" ]

###

  Summary of changes:

Fix spelling of "Feburary"

Fix formatting in the SYNOPSIS line

Remove space at end of lines.

Add missing "--n" in the description

Begin a sentence in a new line

Change a two-fonts macro to an one-font macro.

  The patch is in the attachment.

###

  Details:

Input file is fgconsole.1

mandoc: fgconsole.1:22:41: STYLE: whitespace at end of input line
mandoc: fgconsole.1:23:9: STYLE: whitespace at end of input line
mandoc: fgconsole.1:38:6: STYLE: whitespace at end of input line
mandoc: fgconsole.1:40:20: STYLE: whitespace at end of input line

###

Test nr. 1:

Remove space characters at the end of lines.

Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

22:If the console is a serial console, then 
23:"serial" 
38:Under 
40:the consoles are in 

#

Test nr. 16:

Use the correct macro for the font change of one argument.
Split a  punctuation mark from the only argument if one is there

8:.BI [
42:.IR devfsd

#

Input file is fgconsole.1
Test nr. 41:

Wrong distance between sentences or protect the indicator.

1) Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) [package "manpages"] and "info groff".

Or

2) Adjust space between sentences (two spaces),

3) or protect the indicator by adding "\&" after it.

The "indicator" is an "end-of-sentence character" (.!?).

33:Will show the next unallocated virtual terminal. Normally 6 virtual

#


-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.88-1-u1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages kbd depends on:
ii  libc6  2.27-3

Versions of packages kbd recommends:
ii  console-data   2:1.12-6
ii  console-setup  1.184

kbd suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason
--- fgconsole.1 2017-09-15 08:33:29.0 +
+++ fgconsole.1.new 2018-05-27 00:09:31.0 +
@@ -1,17 +1,12 @@
-.TH FGCONSOLE 1 "14 Feburary 2002" "" "Linux User's Manual"
+.TH FGCONSOLE 1 "14 February 2002" "" "Linux User's Manual"
 
 .SH NAME
 fgconsole \- print the number of the active VT.
 
 .SH SYNOPSIS
 .B fgconsole
-.BI [
-\-h \-\-help
-|
-\-V \-\-version
-|
-\-n \-\-next-available
-]
+.RB "[ " "\-h \-\-help" " | " "\-V \-\-version" " | " \
+"\-n \-\-next-available" " ]"
 .SH DESCRIPTION
 If the active Virtual Terminal is
 .IR /dev/ttyN ,
@@ -19,8 +14,8 @@ then prints
 .I N
 on standard output.
 
-If the console is a serial console, then 
-"serial" 
+If the console is a serial console, then
+"serial"
 is printed instead.
 .TP
 .I \-h \-\-help
@@ -29,17 +24,18 @@ Prints short usage message and exits.
 .I \-V \-\-version
 Prints version number and exits.
 .TP
-.I \-\-next\-available
-Will show the next unallocated virtual terminal. Normally 6 virtual
+.I \-n \-\-next\-available
+Will show the next unallocated virtual terminal.
+Normally 6 virtual
 terminals are allocated, with number 7 used for X; this will return
 "8" in this case.
 
 .SH NOTES
-Under 
+Under
 .IR devfs ,
-the consoles are in 
+the consoles are in
 .IR /dev/vc/N .
-.IR devfsd
+.I devfsd
 may maintain symlinks for compatibility.
 .SH "SEE ALSO"
 .BR chvt (1).

Bug#900071: dpkg ignores DPKG_ADMINDIR environment variable

[Guillem Jover]

Control: tags -1 moreinfo

Hi!

On Fri, 2018-05-25 at 19:47:50 +0300, Alexander Zhukov wrote:
> Package: dpkg
> Version: 1.19.0.5

> dpkg ignores DPKG_ADMINDIR environment variable because in main.c on
> line 207 admindir variable incorrectly intitialized with ADMINDIR
> define. The variable must be initialized with NULL. Otherwise
> DPKG_ADMINDIR is always ignored (see lib/dpkg/dbdir.c, function
> dpkg_db_set_dir.

That was done on purpose when this got implemented, see commit
e63e1fa4a4afdf98847f13f2506a0aeea68c33c7 and bug #97076 for more
details. You'll see that the variable is not documented in the dpkg
man page as an External variable. The concern back then was that it
was a possible security issue, and dpkg itself should ignore such
variable.

Perhaps that was too conservative and it's hindering some usages?
Where did you find this to be a problem? The only one I'm aware might
be a problem is when dpkg acts as a dpkg-query frontend.

Thanks,
Guillem

Bug#900221: RM: mod-authn-webid -- RoQA; orphaned, dead upstream, RC-buggy

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Hi,
please remove mod-authn-webid. It's orphaned for over four years without an
adopter and dead upstream. It's also RC-buggy as it's incompatible with
OpenSSL 1.1.

Cheers,
Moritz

Bug#900222: RM: polygraph -- RoQA; orphaned, RC-buggy, unused

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Hi,
please remove polygraph. It's orphaned for two years without an adopter
and RC-buggy due to missing support for OpenSSL 1.1, popcon is marginal.

Cheers,
Moritz

Bug#900220: RM: stone -- RoQA; dead upstream, unmaintained, RC-buggy

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please remove stone:
- Dead upstream (last commit a decade ago)
- Unmaintained (last maintainer upload eight years ago)
- RC-buggy due to lack of OpenSSL 1.1 support
- Marginal popcon

Cheers,
Moritz

Bug#891612: closed by Marcelo Jorge Vieira <me...@debian.org> (Re: thumbor: uninstallable after python-imaging removal)

[Adrian Bunk]

Control: reopen -1

On Sun, May 20, 2018 at 10:45:03PM +, Debian Bug Tracking System wrote:
>
> Hi,
> 
> I'm closing this bug because piuparts test seems ok now.
> 
> https://piuparts.debian.org/sid/source/t/thumbor.html

This successful test was in 2017.

I just confirmed that your package is not installable in a sid chroot.

> Cheers,

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#900219: nmh FTCBFS: does not pass --host to ./configure

[Helmut Grohne]

Source: nmh
Version: 1.7.1-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

nmh fails to cross build from source, because it does not pass --host to
./configure. The easiest way of doing so is letting dh_auto_configure do
it. After switching to dh_auto_configure, nmh cross builds successfully.
Please consider applying the attached patch.

Helmut
diff --minimal -Nru nmh-1.7.1/debian/changelog nmh-1.7.1/debian/changelog
--- nmh-1.7.1/debian/changelog  2018-03-08 09:28:52.0 +0100
+++ nmh-1.7.1/debian/changelog  2018-05-27 19:46:38.0 +0200
@@ -1,3 +1,10 @@
+nmh (1.7.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 27 May 2018 19:46:38 +0200
+
 nmh (1.7.1-1) unstable; urgency=medium
 
   * New upstream release
diff --minimal -Nru nmh-1.7.1/debian/rules nmh-1.7.1/debian/rules
--- nmh-1.7.1/debian/rules  2018-01-14 02:30:02.0 +0100
+++ nmh-1.7.1/debian/rules  2018-05-27 19:46:34.0 +0200
@@ -24,7 +24,7 @@
 build-stamp:
dh_testdir
dh_autoreconf
-   ./configure \
+   dh_auto_configure -- \
  --prefix= \
  --bindir='$${prefix}/usr/bin/mh' \
  --sysconfdir='$${prefix}/etc' \

Bug#900218: unionfs-fuse FTCBFS: does not pass cross flags to cmake

[Helmut Grohne]

Source: unionfs-fuse
Version: 1.0-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

unionfs-fuse fails to cross build from source, because it runs cmake for
the build architecture. The easiest way to pass the relevant cross
compilation flags to cmake is deferring the task to dh_auto_configure.
After doing so, unionfs-fuse cross builds successfully. Please consider
applying the attached patch.

Helmut
diff --minimal -Nru unionfs-fuse-1.0/debian/changelog 
unionfs-fuse-1.0/debian/changelog
--- unionfs-fuse-1.0/debian/changelog   2015-07-12 21:26:05.0 +0200
+++ unionfs-fuse-1.0/debian/changelog   2018-05-27 19:38:49.0 +0200
@@ -1,3 +1,10 @@
+unionfs-fuse (1.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass cross flags to cmake. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 27 May 2018 19:38:49 +0200
+
 unionfs-fuse (1.0-1) unstable; urgency=medium
 
   * New upstream release
diff --minimal -Nru unionfs-fuse-1.0/debian/rules unionfs-fuse-1.0/debian/rules
--- unionfs-fuse-1.0/debian/rules   2015-07-14 00:12:27.0 +0200
+++ unionfs-fuse-1.0/debian/rules   2018-05-27 19:38:47.0 +0200
@@ -28,9 +28,7 @@
 configure-stamp:
dh_testdir
# Add here commands to configure the package.
-   mkdir -p debian/build
-   cd debian/build \
-   && cmake ../../ -DCMAKE_INSTALL_PREFIX=/usr \
+   dh_auto_configure --builddirectory=debian/build -- \
-DCMAKE_C_FLAGS="$(CFLAGS)" \
-DCMAKE_SKIP_RPATH=TRUE
 

Bug#900217: quakespam FTCBFS: uses the build architecture toolchain

[Helmut Grohne]

Source: quakespasm
Version: 0.93.0+dfsg-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

quakespasm fails to cross build from source, because it uses the build
architecture toolchain. For the makefile buildsystem being used here,
the simplest solution is to let dh_auto_build pass cross tools to make.
While doing so, I figured that debian/rules could be simplified by
passing --sourcedirectory to dh. Next, the upstream build system hard
codes the build architecture pkg-config. The attached patch fixes both
of these issues, but it doesn't make quakespasm cross buildable, because
it runs into #899138 and thus fails finding opusfile.pc. Please consider
applying the attached patch anyway and closing this bug when doing so.

Helmut
diff --minimal -Nru quakespasm-0.93.0+dfsg/debian/changelog 
quakespasm-0.93.0+dfsg/debian/changelog
--- quakespasm-0.93.0+dfsg/debian/changelog 2018-01-16 10:23:33.0 
+0100
+++ quakespasm-0.93.0+dfsg/debian/changelog 2018-05-27 19:19:16.0 
+0200
@@ -1,3 +1,12 @@
+quakespasm (0.93.0+dfsg-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Improve cross buildability: (Closes: #-1)
++ Let dh_auto_build pass cross tools to make.
++ cross.patch: Make pkg-config substitutable.
+
+ -- Helmut Grohne   Sun, 27 May 2018 19:19:16 +0200
+
 quakespasm (0.93.0+dfsg-2) unstable; urgency=medium
 
   * Move git hosting to salsa.debian.org
diff --minimal -Nru quakespasm-0.93.0+dfsg/debian/patches/cross.patch 
quakespasm-0.93.0+dfsg/debian/patches/cross.patch
--- quakespasm-0.93.0+dfsg/debian/patches/cross.patch   1970-01-01 
01:00:00.0 +0100
+++ quakespasm-0.93.0+dfsg/debian/patches/cross.patch   2018-05-27 
19:19:16.0 +0200
@@ -0,0 +1,21 @@
+--- quakespasm-0.93.0+dfsg.orig/Quake/Makefile
 quakespasm-0.93.0+dfsg/Quake/Makefile
+@@ -46,6 +46,7 @@
+ LINKER = $(CC)
+ 
+ STRIP ?= strip
++PKG_CONFIG ?= pkg-config
+ 
+ #CPUFLAGS= -mtune=i686
+ #CPUFLAGS= -march=pentium4
+@@ -152,8 +153,8 @@
+ # but they include the headers without the opus directory
+ # prefix and rely on pkg-config. ewww...
+ CFLAGS+= -DUSE_CODEC_OPUS
+-CFLAGS+= $(shell pkg-config --cflags opusfile)
+-CODECLIBS+= $(shell pkg-config --libs   opusfile)
++CFLAGS+= $(shell $(PKG_CONFIG) --cflags opusfile)
++CODECLIBS+= $(shell $(PKG_CONFIG) --libs   opusfile)
+ endif
+ ifeq ($(USE_CODEC_VORBIS),1)
+ CFLAGS+= -DUSE_CODEC_VORBIS $(cpp_vorbisdec)
diff --minimal -Nru quakespasm-0.93.0+dfsg/debian/patches/series 
quakespasm-0.93.0+dfsg/debian/patches/series
--- quakespasm-0.93.0+dfsg/debian/patches/series2018-01-16 
10:23:33.0 +0100
+++ quakespasm-0.93.0+dfsg/debian/patches/series2018-05-27 
19:19:16.0 +0200
@@ -4,3 +4,4 @@
 mkpak-bashism.patch
 reproducible-build.patch
 spelling-fixes.patch
+cross.patch
diff --minimal -Nru quakespasm-0.93.0+dfsg/debian/rules 
quakespasm-0.93.0+dfsg/debian/rules
--- quakespasm-0.93.0+dfsg/debian/rules 2018-01-16 10:23:33.0 +0100
+++ quakespasm-0.93.0+dfsg/debian/rules 2018-05-27 19:18:37.0 +0200
@@ -8,7 +8,7 @@
 CXXFLAGS+=$(CPPFLAGS)
 
 %:
-   dh $@
+   dh $@ --sourcedirectory=Quake
 
 ifeq (,$(filter noopt,$(DEB_BUILD_OPTIONS)))
 maybe_debug = DEBUG=0
@@ -16,11 +16,8 @@
 maybe_debug = DEBUG=1
 endif
 
-override_dh_auto_clean:
-   make -C Quake clean
-
 override_dh_auto_build:
-   make -C Quake \
+   dh_auto_build -- \
$(maybe_debug) \
STRIP=": do not strip:" \
DO_USERDIRS=1 \
@@ -29,7 +26,9 @@
USE_CODEC_OPUS=1 \
USE_CODEC_MIKMOD=1 \
USE_CODEC_UMX=1
-   make -C Misc/qs_pak
+   dh_auto_build --sourcedirectory=Misc/qs_pak
 
 override_dh_strip:
dh_strip --ddeb-migration='quakespasm-dbg (<< 0.90.1+dfsg-2~)'
+
+override_dh_auto_install: