Bug#895043: libgtk-3-0: unexplained downstream patch disables VIQR input method in Vietnamese locales

2018-04-14 Thread Khang Nguyen Trong
Hi McVittie,

I definitely cannot speak for all Vietnamese users. I do not know how many
people out there are still using VIQR. However, for people who do not know
or are not used to VIQR, it is definitely a troublemaker. The same can be
said for other input methods.

I grew up in an environment in which people were used to VNI or Telex input
methods. I know nothing about VIQR. Although I would really like to not
have VIQR as the default choice, I have no objection to letting it be
enabled. Disabling it to me seems like a quick fix.

What I am trying to say is that it should not be the default, but it should
not be disabled either. That is my take on this matter.

Thank you for letting us know about this. We really appreciate your effort
to reach out to us.

Khang Nguyen.


On Fri, Apr 6, 2018 at 2:03 PM Simon McVittie  wrote:

> On Fri, 06 Apr 2018 at 13:34:32 -0400, Jeremy Bicha wrote:
> > On Fri, Apr 6, 2018 at 10:03 AM, Simon McVittie  wrote:
> > > The Debian packages for GTK+ 2 and GTK+ 3 both have the patch quoted
> > > below, which changes the upstream default behaviour.
> >
> > The Ubuntu bug is
> > https://launchpad.net/bugs/191451
>
> Thanks, that provides a lot more context. I've changed the commit message
> to the following:
>
> > From: Ming Hua 
> > Date: Thu, 13 Mar 2008 18:09:25 -0500
> > Subject: Do not use VIQR input method for vi locale by default
> > MIME-Version: 1.0
> > Content-Type: text/plain; charset="utf-8"
> > Content-Transfer-Encoding: 8bit
> >
> > In the Vietnamese Quoted-Readable input method, punctuation following a
> > base letter is converted into diacritical marks, for example a( → ă.
> > (See .)
> > A 2008 bug report in Ubuntu argued that this is a problematic default,
> > particularly when typing passwords, where the effect of the punctuation
> > is non-obvious.
> >
> > According to the bug reporter, VIQR is popular with Vietnamese users
> > living elsewhere in the world, where Vietnamese keyboards are unlikely
> > to be readily available, but is not a popular choice within Vietnam,
> > where the Telex or VNI input modes are preferred.
> >
> > [smcv: Add a summary of the Ubuntu bug]
> > Bug-Debian: https://bugs.debian.org/895043
> > Bug-Ubuntu:
> https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/191451
> > Forwarded: no
>
> Is that a good summary of the situation?
>
> Vietnamese users: Is this a change we should be asking for upstream, for
> GTK+ 4? I would prefer it to either go upstream, or be reverted: having a
> permanent Debian-specific change seems bad.
>
> At the moment, we apply this patch to GTK+ 2 and GTK+ 3, but not to GTK+ 4.
>
> smcv
>
>


Bug#895721: librsvg: test 93 failure on arm64

2018-04-14 Thread Tim Lunn
Source: librsvg
Version: 2.42.3-1
Severity: important
Tags: upstream

Test 93 is failing on arm64 and also appears to have the same failure on s390x 
(other s390x failures will file seperately)

# librsvg-MESSAGE: CSS parsing error

# librsvg-MESSAGE: CSS unrecoverable error

# Storing test result image at /tmp/pservers-grad-08-b-out.png
# 7 pixels differ (with maximum difference of 2) from reference image

# Storing test result image at /tmp/pservers-grad-08-b-diff.png
not ok 93 /rsvg-test/reftests/svg1.1/pservers-grad-08-b.svg
FAIL: rsvg-test 93 /rsvg-test/reftests/svg1.1/pservers-grad-08-b.svg


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

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



Bug#871094: proposed NMU

2018-04-14 Thread Michael Tokarev
15.04.2018 05:19, Adam Borowski wrote:
> Hi!
> This FTBFS has been unresponded for 8 months, has a patch rotting for 6.
> Sounds like NMU time.
> 
> Here's a debdiff that includes this and #833444.  I'll upload to DELAYED/7,
> please yell if anything is wrong.

Oh. I haven't noticed this bugreport. I've been preparing a refresh of several
qemu-related packages (incl seabios and openbios and this one), already
fixed the non-reproducible build issue locally, but haven't seen the
FTBFS issue. So far it weren't me who dealt with these packages.

Lemme force the new version...  Thank you for the reminder!

/mjt



Bug#895720: Installation of Buster successfully at Asus UX501

2018-04-14 Thread Bernhard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: installation-reports

Boot method: USB Flash drive
Image version: Self-made ISO image with current installer from testing
Date: 2018-04-14

Machine: ASUS Zenbook UX501J
Processor: Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz
Memory: 16GB
Partitions:

> DateisystemTyp  1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
> udev   devtmpfs   8144048   0   81440480% /dev
> tmpfs  tmpfs  16315729108   16224641% /run
> /dev/sda1  ext4 106144480 5783648  949259526% /
> tmpfs  tmpfs  81578524960   81528921% /dev/shm
> tmpfs  tmpfs 5120   4  51161% /run/lock
> tmpfs  tmpfs  8157852   0   81578520% /sys/fs/cgroup
> tmpfs  tmpfs  1631568  20   16315481% /run/user/1000

Output of lspci -knn:

> 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
> Processor DRAM Controller [8086:0c04] (rev 06)
>   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
> DRAM Controller [1043:18dd]
>   Kernel modules: ie31200_edac
> 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
> Processor PCI Express x16 Controller [8086:0c01] (rev 06)
>   Kernel driver in use: pcieport
>   Kernel modules: shpchp
> 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core 
> Processor Integrated Graphics Controller [8086:0416] (rev 06)
>   Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
> Graphics Controller [1043:18dd]
>   Kernel driver in use: i915
>   Kernel modules: i915
> 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
> Processor HD Audio Controller [8086:0c0c] (rev 06)
>   Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD 
> Audio Controller [8086:2010]
>   Kernel driver in use: snd_hda_intel
>   Kernel modules: snd_hda_intel
> 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset 
> Family USB xHCI [8086:8c31] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> USB xHCI [1043:18dd]
>   Kernel driver in use: xhci_hcd
>   Kernel modules: xhci_pci
> 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 
> Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> MEI Controller [1043:18dd]
>   Kernel driver in use: mei_me
>   Kernel modules: mei_me
> 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset 
> Family USB EHCI #2 [8086:8c2d] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> USB EHCI [1043:18dd]
>   Kernel driver in use: ehci-pci
>   Kernel modules: ehci_pci
> 00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
> High Definition Audio Controller [8086:8c20] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset High 
> Definition Audio Controller [1043:18dd]
>   Kernel driver in use: snd_hda_intel
>   Kernel modules: snd_hda_intel
> 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset 
> Family PCI Express Root Port #1 [8086:8c10] (rev d5)
>   Kernel driver in use: pcieport
>   Kernel modules: shpchp
> 00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset 
> Family PCI Express Root Port #3 [8086:8c14] (rev d5)
>   Kernel driver in use: pcieport
>   Kernel modules: shpchp
> 00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset 
> Family PCI Express Root Port #4 [8086:8c16] (rev d5)
>   Kernel driver in use: pcieport
>   Kernel modules: shpchp
> 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset 
> Family USB EHCI #1 [8086:8c26] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> USB EHCI [1043:18dd]
>   Kernel driver in use: ehci-pci
>   Kernel modules: ehci_pci
> 00:1f.0 ISA bridge [0601]: Intel Corporation HM87 Express LPC Controller 
> [8086:8c4b] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. HM87 Express LPC Controller [1043:18dd]
>   Kernel driver in use: lpc_ich
>   Kernel modules: lpc_ich
> 00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series 
> Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c03] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> 6-port SATA Controller 1 [AHCI mode] [1043:18dd]
>   Kernel driver in use: ahci
>   Kernel modules: ahci
> 00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family 
> SMBus Controller [8086:8c22] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> SMBus Controller [1043:18dd]
>   Kernel driver in use: 

Bug#891288: tiff: CVE-2018-7456: null pointer dereference

2018-04-14 Thread GCS
Hi Hugo,

On Sun, Apr 15, 2018 at 6:08 AM, Hugo Lefeuvre  wrote:
> My MR was accepted. I'm going to backport the fix to Wheezy tomorrow,
> should I also prepare a patch for Jessie & Stretch at the same time ?
 Thanks for the offer - I would like to do it late in the afternoon
when I get back home.

Cheers,
Laszlo/GCS



Bug#891288: tiff: CVE-2018-7456: null pointer dereference

2018-04-14 Thread Hugo Lefeuvre
Hi,

My MR was accepted. I'm going to backport the fix to Wheezy tomorrow,
should I also prepare a patch for Jessie & Stretch at the same time ?

Cheers,
 Hugo

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ 9C4F C8BF A4B0 8FC5 48EB 56B8 1962 765B B9A8 BACA


signature.asc
Description: PGP signature


Bug#895719: iproute2: When ss is invoked with the no-header flag and there is no result it segfaults.

2018-04-14 Thread René Jochum
Package: iproute2
Version: 4.15.0-3.1
Severity: normal
Tags: patch

Patch found upstream: https://www.spinics.net/lists/netdev/msg486801.html


When ss is invoked with the no-header flag, if the query doesn't return
any result, render() is called with 'buffer' uninitialized. This
currently leads to a segfault. Ensure that buffer is initialized before
rendering.

The bug can be triggered with: ss -H sport = 10

Signed-off-by: Jean-Philippe Brucker 
---
 misc/ss.c | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/misc/ss.c b/misc/ss.c
index e047f9c0..e087bef7 100644
--- a/misc/ss.c
+++ b/misc/ss.c
@@ -1197,10 +1197,15 @@ newline:
 /* Render buffered output with spacing and delimiters, then free up buffers */
 static void render(int screen_width)
 {
-   struct buf_token *token = (struct buf_token *)buffer.head->data;
+   struct buf_token *token;
int printed, line_started = 0;
struct column *f;

+   if (!buffer.head)
+   return;
+
+   token = (struct buf_token *)buffer.head->data;
+
/* Ensure end alignment of last token, it wasn't necessarily flushed */
buffer.tail->end += buffer.cur->len % 2;

--
2.16.2



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

Kernel: Linux 4.15.15-1-pve (SMP w/8 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_AT:de (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages iproute2 depends on:
ii  libc62.27-3
ii  libdb5.3 5.3.28-13.1+b1
ii  libelf1  0.170-0.4
ii  libmnl0  1.0.4-2
ii  libselinux1  2.7-2+b2

Versions of packages iproute2 recommends:
ii  libatm1   1:2.5.1-2
ii  libxtables12  1.6.2-1

Versions of packages iproute2 suggests:
pn  iproute2-doc  

-- no debconf information



Bug#895718: python-pyqt5: import PyQt5.QtCore fails

2018-04-14 Thread Scott Kitterman
Package: python-pyqt5
Version: 5.9.2+dfsg-1
Severity: grave
Justification: renders package unusable

Tried this on sid with both pyqt5 5.9.2 and 5.10.1:

Unpacking python-pyqt5 (5.10.1+dfsg-1) over (5.9.2+dfsg-1+b1) ...
Setting up python-pyqt5 (5.10.1+dfsg-1) ...
# python
Python 2.7.14+ (default, Apr  2 2018, 04:16:25)
[GCC 7.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import PyQt5.QtCore
Traceback (most recent call last):
  File "", line 1, in 
ImportError: libQt5Core.so.5: cannot open shared object file: No such file or 
directory
>>>

I checked and libQt5Core.so.5 is installed at the expected location:

# ls -l /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
lrwxrwxrwx 1 root root 20 Apr  7 19:35 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 -> libQt5Core.so.5.10.1

# ls -l /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.1
-rw-r--r-- 1 root root 5224752 Apr  7 19:35 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.1

The same thing happenson python3 too:

Python 3.6.5 (default, Apr  1 2018, 05:46:30)
[GCC 7.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import PyQt5.QtCore
Traceback (most recent call last):
  File "", line 1, in 
ImportError: libQt5Core.so.5: cannot open shared object file: No such file or 
directory

Scott K



Bug#895717: ITP: nb2plots -- Converting between ipython notebooks and sphinx docs

2018-04-14 Thread Sandro Tosi
Package: wnpp
Severity: wishlist
Owner: Sandro Tosi 

* Package name: nb2plots
  Version : 0.6
  Upstream Author : Matthew Brett
* URL : http://github.com/matthew-brett/nb2plots
* License : BSD
  Programming Lang: Python
  Description : Converting between ipython notebooks and sphinx docs

nb2plots converts Jupyter notebooks to ReST files for Sphinx, and back again.

Nb2plots assumes that the ReST document will become the source for your Sphinx
web pages, but also for future versions of the notebook. The notebook may serve
as a draft for the polished ReST page, and an output format from the Sphinx
build.

this is needed by python-networkx/2.1



Bug#895686: installation-birthday: Incorrectly identifies the birthdate of my system

2018-04-14 Thread Boyd Stephen Smith Jr.
On Saturday, April 14, 2018 10:53:58 PM CDT Chris Lamb wrote:
> Can you
> hunt around for any file you think matches?

ctime of /etc/inittab or /root/.profile might work.

ctime candidates attached.

-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net   ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/
% find / \( -ctime +3756 -not -ctime +3787 -ls \) -o \( -name home -type d -prune \) 2>&- > find-install-ctime
 6517  0 lrwxrwxrwx   1 root root   20 Dec 17  2007 /bin/mt -> /etc/alternatives/mt
 8998  0 lrwxrwxrwx   1 root root   13 Dec 17  2007 /etc/X11/X -> /usr/bin/Xorg
 8883  4 -rw-r--r--   1 root root  319 Feb 13  2007 /etc/X11/Xresources/x11-common
 7387  8 -rw-r--r--   1 root root 6270 Sep 30  2006 /etc/X11/fonts/misc/xfonts-base.alias
 8902 28 -rw-r--r--   1 root root28252 Jun 30  2006 /etc/X11/fonts/Type1/gsfonts-x11.alias
 8901  8 -rw-r--r--   1 root root 7439 Jun 30  2006 /etc/X11/fonts/Type1/gsfonts-x11.scale
 9629  4 -rw-r--r--   1 root root 2654 Nov 18  2006 /etc/X11/fonts/Type1/xfonts-scalable.scale
 8880  4 -rw-r--r--   1 root root  166 Feb 13  2007 /etc/X11/Xsession.d/99x11-common_start
 7264  4 -rw-r--r--   1 root root 2982 Dec 18  2007 /etc/X11/xorg.conf.20071218003554
 8881  4 -rw-r--r--   1 root root  265 Feb 13  2007 /etc/X11/Xsession.options
 8962  4 -rw-r--r--   1 root root 3184 Jan 12  2007 /etc/X11/app-defaults/Viewres
 8982  4 -rw-r--r--   1 root root  920 Jan 12  2007 /etc/X11/app-defaults/Xmessage-color
 8981  4 -rw-r--r--   1 root root  248 Jan 12  2007 /etc/X11/app-defaults/Xmessage
 9453  4 -rw-r--r--   1 root root 3796 Sep  2  2006 /etc/X11/app-defaults/SshAskpass
 9368  4 -rwxr-xr-x   1 root root  144 Mar  6  2007 /etc/apm/event.d/gpm
 9384  4 -rwxr-xr-x   1 root root 2265 Feb 16  2007 /etc/apm/event.d/20hdparm
 9159  4 -rwxr-xr-x   1 root root  753 Oct 14  2006 /etc/apm/event.d/anacron
 7289  4 -rwxr-xr-x   1 root root 3849 Feb 25  2007 /etc/apm/apmd_proxy
  175  4 -rw-r--r--   1 root root  182 Dec 20  2006 /etc/apt/apt.conf.d/70debconf
   10  4 -rw-r--r--   1 root root   40 Dec 17  2007 /etc/apt/apt.conf.d/00trustcdrom
 9923  4 -rw-r--r--   1 root root   48 Dec 17  2007 /etc/apt/listbugs/ignore_bugs
  393  0 -rw-r--r--   1 root root0 Dec 17  2007 /etc/apt/sources.list~
 6178  0 drwxr-xr-x   2 root root   48 Dec 17  2007 /etc/opt
  401  4 -rwxr-xr-x   1 root root  268 Dec  1  2006 /etc/rmt
 6265  4 -rw-r--r--   1 root root  887 Feb  1  2007 /etc/rpc
 7334  0 -rw-r--r--   1 root root0 Dec 13  2005 /etc/resolvconf/resolv.conf.d/base
 7377  0 -rw-r--r--   1 root root0 Dec 18  2007 /etc/resolvconf/resolv.conf.d/tail
 7378  4 -rw-r--r--   1 root root   51 Dec 18  2007 /etc/resolvconf/resolv.conf.d/original
 9238  4 -rw-r--r--   1 root root  260 Jan 18  2006 /etc/dpkg/shlibs.default
  194  4 -rw-r--r--   1 root root   82 Jan  2  2007 /etc/dpkg/origins/debian
 9237  4 -rw-r--r--   1 root root  253 Jan 18  2006 /etc/dpkg/shlibs.override
 9337  0 drwxr-xr-x   3 root root   72 Dec 17  2007 /etc/gimp
 9225  4 -rw-r--r--   1 root root 2489 Jan  2  2007 /etc/java/security/classpath.security
 9221  0 -rw-r--r--   1 root root0 Jan  2  2007 /etc/java/security/security.d/1001-gnu.javax.crypto.jce.GnuCrypto
 9220  0 -rw-r--r--   1 root root0 Jan  2  2007 /etc/java/security/security.d/1000-gnu.java.security.provider.Gnu
 9223  0 -rw-r--r--   1 root root0 Jan  2  2007 /etc/java/security/security.d/1003-gnu.javax.net.ssl.provider.Jessie
 9222  0 -rw-r--r--   1 root root0 Jan  2  2007 /etc/java/security/security.d/1002-gnu.javax.crypto.jce.GnuSasl
 9224  0 -rw-r--r--   1 root root0 Jan  2  2007 /etc/java/security/security.d/1004-gnu.javax.security.auth.callback.GnuCallbacks
 9359  4 -rw-r--r--   1 root root  127 Sep 10  2005 /etc/kde3/konqsidebartng.rc
 9419  4 -rw-r--r--   1 root root 1010 Sep 10  2005 /etc/kde3/kmail.antivirusrc
 9269  0 drwxr-xr-x   2 root root   48 Dec 17  2007 /etc/keys
 9086  0 drwxr-xr-x   3 root root   72 Dec 17  2007 /etc/perl/XML
  214  4 -rw-r--r--   1 root root  220 Dec 11  2006 

Bug#895686: installation-birthday: Incorrectly identifies the birthdate of my system

2018-04-14 Thread Boyd Stephen Smith Jr.
On Saturday, April 14, 2018 10:53:58 PM CDT Chris Lamb wrote:
> Hi!
> 
> > > Getcha. Can you provide the output of:
> > >  $ ls -l --sort=time /var/log /etc
> 
> Hm, none of these seem like good candidates to add. :(  Can you
> hunt around for any file you think matches? Perhaps an "ls -l --
> sort=time" for "/" and "/root" and "/boot" might help here?

I'm attached a couple lists this time.  The first is your requested command, 
which might be helpful, / contains two directories and a symlink that have the 
right date.

The second is a broader approach.  I assumed the 2007-12 timeframe was correct 
and just did a find starting in /, with mtime bounds.  Then, I redacted the 
entries from /home.  It should be a comprehensive list of candidates, if you 
use mtime.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net   ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/
/boot:
total 92556
-rw-r--r-- 1 root root 25889955 Mar 28 19:24 initrd.img-4.15.0-1-amd64
-rw-r--r-- 1 root root 22438475 Mar 25 16:45 initrd.img-4.9.0-5-amd64
-rw-r--r-- 1 root root 22569629 Mar 25 16:45 initrd.img-4.9.0-6-amd64
drwxr-xr-x 5 root root  336 Mar 25 02:47 grub
-rw-r--r-- 1 root root   186567 Mar  2 01:52 config-4.9.0-6-amd64
-rw-r--r-- 1 root root  3189623 Mar  2 01:52 System.map-4.9.0-6-amd64
-rw-r--r-- 1 root root  4224800 Mar  2 01:52 vmlinuz-4.9.0-6-amd64
-rw-r--r-- 1 root root   197970 Feb 18 02:36 config-4.15.0-1-amd64
-rw-r--r-- 1 root root  3084776 Feb 18 02:36 System.map-4.15.0-1-amd64
-rw-r--r-- 1 root root  4917008 Feb 18 02:36 vmlinuz-4.15.0-1-amd64
-rw-r--r-- 1 root root   186473 Jan  4 05:12 config-4.9.0-5-amd64
-rw-r--r-- 1 root root  3185098 Jan  4 05:12 System.map-4.9.0-5-amd64
-rw-r--r-- 1 root root  4216608 Jan  4 05:12 vmlinuz-4.9.0-5-amd64
-rw-r--r-- 1 root root   182704 Jun 25  2015 memtest86+.bin
-rw-r--r-- 1 root root   184840 Jun 25  2015 memtest86+_multiboot.bin

/:
total 40
drwxrwxrwt  29 root root  760 Apr 14 23:02 tmp
drwxr-xr-x 197 root root 9656 Apr 14 13:16 etc
drwxr-xr-x  40 root root 1280 Apr 14 02:56 run
drwxr-xr-x  20 root root 4180 Apr  5 23:07 dev
dr-xr-xr-x  13 root root0 Apr  5 23:07 sys
dr-xr-xr-x 596 root root0 Apr  5 23:06 proc
drwxr-xr-x  23 root root  960 Apr  4 19:01 lib
drwxr-xr-x   2 root root 6992 Apr  4 19:01 sbin
drwxr-xr-x   2 root root  168 Apr  4 19:01 lib64
drwxr-xr-x   2 root root 1552 Apr  4 19:01 lib32
drwxr-xr-x   3 root root  640 Mar 28 19:24 boot
drwxr-xr-x   2 root root 4624 Mar 28 19:24 bin
drwxr-xr-x   1 root root   80 Mar 25 03:21 usr
lrwxrwxrwx   1 root root   30 Mar 25 02:46 initrd.img -> 
boot/initrd.img-4.15.0-1-amd64
lrwxrwxrwx   1 root root   29 Mar 25 02:46 initrd.img.old -> 
boot/initrd.img-4.9.0-6-amd64
lrwxrwxrwx   1 root root   27 Mar 25 02:46 vmlinuz -> 
boot/vmlinuz-4.15.0-1-amd64
lrwxrwxrwx   1 root root   26 Mar 25 02:46 vmlinuz.old -> 
boot/vmlinuz-4.9.0-6-amd64
drwxr-xr-x  27 root root 1128 Aug 27  2017 root
drwxr-xr-x   5 root root  200 Jul 15  2017 media
dr-xr-xr-x   1 root root   66 Feb 11  2017 opt
drwxr-xr-x   2 root root   48 Apr 27  2015 mnt
drwxr-xr-x   1 root root  214 May  5  2014 var
drwxr-xr-x  10 root root  240 Mar 11  2013 home
lrwxrwxrwx   1 root root   36 May 29  2012 libnss3.so -> 
/usr/lib/x86_64-linux-gnu/libnss3.so
lrwxrwxrwx   1 root root   44 May 29  2012 libsoftokn3.so -> 
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
drwxr-xr-x   1 root root   24 Mar  1  2008 srv
drwxr-xr-x   3 root root   80 Dec 17  2007 emul
drwxr-xr-x   2 root root   48 Dec 17  2007 initrd
lrwxrwxrwx   1 root root   11 Dec 17  2007 cdrom -> media/cdrom

/root:
total 0
drwxr-xr-x 3 root root 72 Dec  5  2013 Steam
 6517  0 lrwxrwxrwx   1 root root   20 Dec 17  2007 /bin/mt 
-> /etc/alternatives/mt
 8998  0 lrwxrwxrwx   1 root root   13 Dec 17  2007 
/etc/X11/X -> /usr/bin/Xorg
 6234  4 -rwxr-xr-x   1 root root 3517 Dec 30  2007 
/etc/X11/Xsession
10331  4 -rw-r--r--   1 root root  187 Dec 30  2007 
/etc/X11/Xsession.d/40x11-common_xsessionrc
 7264  4 -rw-r--r--   1 root root 2982 Dec 18  2007 
/etc/X11/xorg.conf.20071218003554
   10  4 -rw-r--r--   1 root root   40 Dec 17  2007 
/etc/apt/apt.conf.d/00trustcdrom
 9923  4 -rw-r--r--   1 root root   48 Dec 17  2007 
/etc/apt/listbugs/ignore_bugs
  393  0 -rw-r--r--   1 root root0 Dec 17  2007 
/etc/apt/sources.list~
 6178  0 drwxr-xr-x   2 root root   48 Dec 17  2007 /etc/opt
10024  4 -rw---   1 root root  668 Dec 17  2007 
/etc/ssh/ssh_host_dsa_key.broken
10025  4 -rw-r--r--   1 root root  604 Dec 17  2007 
/etc/ssh/ssh_host_dsa_key.pub.broken
10021  4 -rw---   1 root root 1675 Dec 17  2007 
/etc/ssh/ssh_host_rsa_key.broken
10023  4 

Bug#895701: dlib: Incomplete debian/copyright?

2018-04-14 Thread Hugo Lefeuvre
Hi Chris,

> I just ACCEPTed dlib from NEW but noticed it was missing attribution 
> in debian/copyright for at least assert.h, numerical_integration.cpp,
> fhog.h, and possibly all of dlib-models, I am unsure..
> 
> (This is in no way exhaustive so please check over the entire package 
> carefully and address these on your next upload.)

Right, we didn't notice these dlib/ files:

 setup.py: Copyright (C) 2015  Ehsan Azar (dash...@linux.com)

 dlib/sockets/sockets_kernel_1.cpp:// Copyright (C) 2003  Davis E. King 
(da...@dlib.net), Miguel Grinberg
 dlib/sockets/sockets_kernel_2.h:// Copyright (C) 2003  Davis E. King 
(da...@dlib.net), Miguel Grinberg
 dlib/sockets/sockets_kernel_1.h:// Copyright (C) 2003  Davis E. King 
(da...@dlib.net), Miguel Grinberg
 dlib/sockets/sockets_kernel_2.cpp:// Copyright (C) 2003  Davis E. King 
(da...@dlib.net), Miguel Grinberg

 dlib/matlab/mex_wrapper.cpp:// Copyright (C) 2012 Massachusetts Institute of 
Technology, Lincoln Laboratory
 dlib/matlab/mex_wrapper.cpp:// Copyright (C) 2012 Massachusetts Institute of 
Technology, Lincoln Laboratory
 dlib/matlab/call_matlab.h:// Copyright (C) 2012 Massachusetts Institute of 
Technology, Lincoln Laboratory

 dlib/gui_widgets/nativefont.h:// Copyright (C) 2006 Keita Mochizuki 

 dlib/gui_core/gui_core_kernel_2.cpp:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), Keita Mochizuki
 dlib/gui_core/gui_core_kernel_2.h:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), Keita Mochizuki
 dlib/gui_core/gui_core_kernel_1.h:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), Keita Mochizuki 
 dlib/gui_core/gui_core_kernel_1.cpp:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), Keita Mochizuki
 dlib/gui_widgets/base_widgets.h:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), Keita Mochizuki
 dlib/gui_core/gui_core_kernel_abstract.h:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), Keita Mochizuki
 dlib/gui_widgets/widgets.h:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), Keita Mochizuki
 dlib/gui_widgets/widgets.cpp:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), Keita Mochizuki
 dlib/gui_widgets/drawable.h:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), Keita Mochizuki
 dlib/gui_widgets/widgets_abstract.h:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), Keita Mochizuki
 dlib/gui_widgets/drawable.cpp:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), Keita Mochizuki
 dlib/gui_widgets/base_widgets.cpp:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), Keita Mochizuki
 dlib/gui_widgets/base_widgets_abstract.h:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), Keita Mochizuki
 dlib/unicode/unicode.cpp:// Copyright (C) 2008 Keita Mochizuki, Davis E. King 
(da...@dlib.net)

 dlib/gui_widgets/fonts_abstract.h:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), Nils Labugt, Keita Mochizuki
 dlib/gui_widgets/fonts.h:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), and Nils Labugt, Keita Mochizuki
 dlib/gui_widgets/fonts.cpp:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), and Nils Labugt, Keita Mochizuki

 dlib/test/numerical_integration.cpp:// Copyright (C) 2013 Steve Taylor 
(steve98...@gmail.com)
 dlib/numerical_integration.h:// Copyright (C) 2013 Steve Taylor 
(steve98...@gmail.com)
 dlib/numerical_integration/integrate_function_adapt_simpson.h:// Copyright (C) 
2013 Steve Taylor (steve98...@gmail.com)
 dlib/numerical_integration/integrate_function_adapt_simpson_abstract.h:// 
Copyright (C) 2013 Steve Taylor (steve98...@gmail.com)

 dlib/statistics/statistics.h:// Copyright (C) 2008  Davis E. King 
(da...@dlib.net), Steve Taylor
 dlib/statistics/statistics_abstract.h:// Copyright (C) 2008  Davis E. King 
(da...@dlib.net), Steve Taylor
 dlib/numeric_constants.h://Copyright (C) 2013 Steve Taylor 
(steve98...@gmail.com), Davis E. King

 dlib/matrix/lapack/fortran_id.h://  Copyright (C) 2002, 2003 Si-Lab b.v.b.a., 
Toon Knapen and Kresimir Fresl 

 dlib/image_loader/jpeg_loader.h:// Copyright (C) 2010  Davis E. King 
(da...@dlib.net), Nils Labugt
 dlib/image_loader/png_loader.h:// Copyright (C) 2008  Davis E. King 
(da...@dlib.net), Nils Labugt
 dlib/image_loader/png_loader.cpp:// Copyright (C) 2008  Davis E. King 
(da...@dlib.net), Nils Labugt
 dlib/image_loader/png_loader_abstract.h:// Copyright (C) 2008  Davis E. King 
(da...@dlib.net), Nils Labugt
 dlib/image_loader/jpeg_loader.cpp:// Copyright (C) 2010  Davis E. King 
(da...@dlib.net), Nils Labugt
 dlib/gui_widgets/canvas_drawing_abstract.h:// Copyright (C) 2005  Davis E. 
King (da...@dlib.net), and Nils Labugt
 dlib/image_loader/load_image_abstract.h:// Copyright (C) 2011  Davis E. King 
(da...@dlib.net), Nils Labugt
 dlib/image_loader/jpeg_loader_abstract.h:// Copyright (C) 2010  Davis E. King 
(da...@dlib.net), Nils Labugt
 dlib/gui_widgets/canvas_drawing.h:// Copyright (C) 2005  Davis E. King 
(da...@dlib.net), and Nils Labugt
 dlib/gui_widgets/style.h:// Copyright (C) 2008  Davis E. King 

Bug#895716: src:bcpp: Please migrate to new -dbgsym debug package

2018-04-14 Thread Boyuan Yang
Package: src:bcpp
Version: 0.0.20131209-1
Severity: wishlist

Dear maintainer,

It would be great if we could migrate package bcpp to automatic debug packages
as documented in https://wiki.debian.org/AutomaticDebugPackages .

--
Regards,
Boyuan Yang



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

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



Bug#895715: src:bcpp: Please add homepage information to d/control

2018-04-14 Thread Boyuan Yang
Package: src:bcpp
Version: 0.0.20131209-1
Severity: wishlist

Dear Maintainer,

It would be great if we could document the homepage of bcpp project in
debian/control file.

--
Regards,
Boyuan Yang



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

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



Bug#895714: mutt: breaks attachments by converting to bogus encodings

2018-04-14 Thread Adam Borowski
Package: mutt
Version: 1.7.2-1
Severity: normal

Hi!
I just tried to attach a patch to a mail.  The patch looks fine:

[/tmp]$ file ohw.debdiff 
ohw.debdiff: unified diff output, UTF-8 Unicode text

And indeed, inside there's a name with 'ä' in it.  All ok, properly encoded,
using a sane locale, LC_CTYPE is ok, etc.  However, mutt does:

- I 1 /tmp/mutt-tartarus-1000-26079-3022800448 
[text/plain, 8bit, utf-8, 0.3K]
  A 2 /tmp/ohw.debdiff
[text/plain, 8bit, iso-8859-1, 5.1K]

I've actually sent it as a test (#871094), and indeed, it's not merely wrong
metadata, but it's a well-formed message maliciously converted to an ancient
charset.  Obviously, such a patch is corrupted, and will cause woe if
someone tries to apply it (in this case, lintian would scream, but most
files wouldn't be this lucky).

There's no reason for a file in an ancient locale to exist on any modern
Unix machine -- it will break the vast majority of tools, cause mojibake
when displayed, etc.

I have not a single option about encoding in my .muttrc; so it's a problem
with the default config.  Looking around, I see Linus having chewed out
someone for this very problem just three days ago:
https://marc.info/?l=linux-kernel=152355328529145
I don't think it's reasonable to require obscure workarounds for basic
functionality like this -- especially that having none of such conversion
logic and sending files as-is would take less work.


Meow!
-- Package-specific info:
NeoMutt 20170113 (1.7.2)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 4.9.0-4-amd64 (x86_64)
libidn: 1.33 (compiled with 1.33)
hcache backends: tokyocabinet

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.3.0-2' 
--with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs 
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared 
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext 
--enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ 
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk 
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre 
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.3.0 20161229 (Debian 6.3.0-2) 

Configure options: '--build=x86_64-linux-gnu' '--prefix=/usr' 
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man' 
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' 
'--disable-silent-rules' '--libdir=\${prefix}/lib/x86_64-linux-gnu' 
'--libexecdir=\${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--with-mailpath=/var/mail' 
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' 
'--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-pop' 
'--enable-sidebar' '--enable-nntp' '--enable-notmuch' '--disable-fmemopen' 
'--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' 
'--with-sasl' '--without-gdbm' '--without-bdb' '--without-qdbm' 
'--with-tokyocabinet' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 
-fdebug-prefix-map=/build/mutt-K2ak0h/mutt-1.7.2=. -fstack-protector-strong 
-Wformat -Werror=format-security' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now' 
'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'

Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2 
-fdebug-prefix-map=/build/mutt-K2ak0h/mutt-1.7.2=. -fstack-protector-strong 
-Wformat -Werror=format-security -fno-delete-null-pointer-checks

Compile options:
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME 
+DEBUG +DL_STANDALONE +ENABLE_NLS -EXACT_ADDRESS -HOMESPOOL -LOCALES_HACK 
-SUN_ATTACHMENT +HAVE_BKGDSET +HAVE_COLOR +HAVE_CURS_SET +HAVE_FUTIMENS 
+HAVE_GETADDRINFO +HAVE_GETSID +HAVE_ICONV +HAVE_LANGINFO_CODESET 
+HAVE_LANGINFO_YESEXPR +HAVE_LIBIDN +HAVE_META +HAVE_REGCOMP +HAVE_RESIZETERM 

Bug#895580: RFS: peek/1.3.1-1 [ITP] -- Simple animated GIF screen recorder with GUI

2018-04-14 Thread Boyuan Yang
在 2018年4月15日星期日 CST 上午9:53:52,Sergio Durigan Junior 写道:
> On Friday, April 13 2018, I wrote:
> > On Thursday, April 12 2018, Boyuan Yang wrote:
> >>   Dear mentors,
> >>   
> >>   I am looking for a sponsor for my package "peek"
> >>  
> >>  * Package name: peek
> >>  
> >>Version : 1.3.1-1
> >>Upstream Author : Philipp Wolfer 
> >>  
> >>  * URL : https://github.com/phw/peek
> >>  * License : GPL-3+
> >>  
> >>Section : graphics
> > 
> > Hi, Boyuan,
> > 
> > I'm looking at the package right now.  So far, everything seems to be
> > OK.  I appreciated the way you took care of the licensing stuff, and how
> > d/copyright seems to cover all the bases.
> > 
> > I'll let you know if I have questions, or when I upload it.
> 
> Hi again,
> 
> I've been having a few problems when building the package locally.  It's
> a build failure due to a missing header, and the strange thing is that
> it happens intermitently (i.e., sometimes I can build everything just
> fine, sometimes the build fails).  Here's the error:
> 
>   /build/peek-debian/peek-tmp/obj-x86_64-linux-gnu/src/utils.c:16:10: fatal
> error: application.h: No such file or directory #include "application.h"
> ^~~
>   compilation terminated.
>   make[4]: *** [tests/CMakeFiles/peek-test-utils.dir/build.make:126:
> tests/CMakeFiles/peek-test-utils.dir/__/src/utils.c.o] Error 1 make[4]: ***
> Waiting for unfinished jobs
> 
> After spending some time tracking down the issue, what I found is that
> "application.h" is generated automatically by Vala (see the
> "vala_precompile" rule on CMakeLists.txt).  I've compared the build logs
> generated by a successful build against those generated by an
> unsuccessful one, and there's nothing really wrong that I see.  Plus, if
> I rerun the "make" command after the failure the build succeeds.  So
> far, this is telling me that the problem seems to be a race condition
> (due to the way cmake parallelizes the jobs, maybe).
> 
> I'll see if I manage to investigate a bit more, but I'd appreciate if
> you could take a look at this.

That looks quite weird. I can now think of an immediate workaround (forcing 
non-parallel build to dh). Will perhaps try to dig into it later. Indeed we 
can proceed safely now and probably file a Debian bug (as well as an upstream 
one) to track this issue.

> Meanwhile, I have small nits to point out that I'd like answered/solved
> before we proceed with the upload:
> 
> 1) On d/rules, is there any reason you're using:
> 
>   export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
> 
>   ?

This passes --as-needed flag to the linker and strips unnecessary library 
dependencies. It can be unnecessary sometimes but mostly harmless. In fact I 
have added it to all packages I maintain and no regressions have been found 
before.
 
> 2) You can remove the following line from override_dh_auto_configure
> (also on d/rules):
> 
>   -DCMAKE_LIBRARY_ARCHITECTURE="$(DEB_TARGET_MULTIARCH)"
> 
>   Since you're not building a library, this is not needed.

Indeed. Will remove it from d/rules.
 
> 3) I'd like to see the buildsystem explicitly specified on the "%" rule,
> like:
> 
>   %:
>   dh $@ --buildsystem=cmake

That's optional but benificial. Will fix it and explicitly specify the 
buildsystem (cmake).

> Other than that, the package looks good to me.  Once we solve the build
> failure, I'll gladly upload it for you!

I have committed onto Salsa packaging repo with changes above (non-parallel 
build and issue 2) and 3)). Source package on mentors.d.o is also updated.


--
Regards,
Boyuan Yang

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


Bug#871094: proposed NMU

2018-04-14 Thread Adam Borowski
Hi!
This FTBFS has been unresponded for 8 months, has a patch rotting for 6.
Sounds like NMU time.

Here's a debdiff that includes this and #833444.  I'll upload to DELAYED/7,
please yell if anything is wrong.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ 
⢿⡄⠘⠷⠚⠋⠀ ... what's the frequency of that 5V DC?
⠈⠳⣄
diff -Nru openhackware-0.4.1+git-20140423.c559da7c/debian/changelog 
openhackware-0.4.1+git-20140423.c559da7c/debian/changelog
--- openhackware-0.4.1+git-20140423.c559da7c/debian/changelog   2016-07-03 
22:53:56.0 +0200
+++ openhackware-0.4.1+git-20140423.c559da7c/debian/changelog   2018-04-15 
03:56:36.0 +0200
@@ -1,3 +1,11 @@
+openhackware (0.4.1+git-20140423.c559da7c-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with gcc-7 (Johannes Brandstätter). Closes: #871094.
+  * Make the build reproducible (Chris Lamb). Closes: #833444.
+
+ -- Adam Borowski   Sun, 15 Apr 2018 03:56:36 +0200
+
 openhackware (0.4.1+git-20140423.c559da7c-4) unstable; urgency=medium
 
   * d/patches/001_build.patch: pass -fno-stack-protector.  This is not
diff -Nru 
openhackware-0.4.1+git-20140423.c559da7c/debian/patches/002_reproducible-build.patch
 
openhackware-0.4.1+git-20140423.c559da7c/debian/patches/002_reproducible-build.patch
--- 
openhackware-0.4.1+git-20140423.c559da7c/debian/patches/002_reproducible-build.patch
1970-01-01 01:00:00.0 +0100
+++ 
openhackware-0.4.1+git-20140423.c559da7c/debian/patches/002_reproducible-build.patch
2018-04-15 03:56:12.0 +0200
@@ -0,0 +1,17 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2016-08-04
+
+--- openhackware-0.4.1+git-20140423.c559da7c.orig/Makefile
 openhackware-0.4.1+git-20140423.c559da7c/Makefile
+@@ -36,8 +36,8 @@ else
+ DEBUG:= \#
+ endif
+ 
+-BUILD_DATE:= $(shell date -u +%F)
+-BUILD_TIME:= $(shell date -u +%T)
++BUILD_DATE:= $(shell date -u --date="@$${SOURCE_DATE_EPOCH:-$$(date +%s)}" 
+%F)
++BUILD_TIME:= $(shell date -u --date="@$${SOURCE_DATE_EPOCH:-$$(date +%s)}" 
+%T)
+ 
+ OBJDIR:= .objs
+ DISTDIR:= .
diff -Nru 
openhackware-0.4.1+git-20140423.c559da7c/debian/patches/fix_gcc7_build_failures.patch
 
openhackware-0.4.1+git-20140423.c559da7c/debian/patches/fix_gcc7_build_failures.patch
--- 
openhackware-0.4.1+git-20140423.c559da7c/debian/patches/fix_gcc7_build_failures.patch
   1970-01-01 01:00:00.0 +0100
+++ 
openhackware-0.4.1+git-20140423.c559da7c/debian/patches/fix_gcc7_build_failures.patch
   2018-04-15 03:55:23.0 +0200
@@ -0,0 +1,65 @@
+--- openhackware-0.4.1+git-20140423.c559da7c.orig/src/bloc.c
 openhackware-0.4.1+git-20140423.c559da7c/src/bloc.c
+@@ -1249,6 +1249,7 @@ static int mem_ioctl (bloc_device_t *bd,
+ case MEM_SET_SIZE:
+ u32 = args;
+ bd->trks = (*u32 + bd->seclen - 1) / bd->seclen + 1;
++__attribute__((fallthrough));
+ default:
+ ret = -1;
+ break;
+--- openhackware-0.4.1+git-20140423.c559da7c.orig/src/char.c
 openhackware-0.4.1+git-20140423.c559da7c/src/char.c
+@@ -154,6 +154,7 @@ int console_open (void)
+ CHARDEV_DPRINTF("one serial port\n");
+ register_outd = 1;
+ /* No break here */
++__attribute__((fallthrough));
+ case CHARDEV_KBD:
+ CHARDEV_DPRINTF("one input port %d %d\n", n, i);
+ if (i < 16 && chardev_open(cur) == 0) {
+@@ -162,6 +163,7 @@ int console_open (void)
+ if (!register_outd)
+ break;
+ /* No break here */
++__attribute__((fallthrough));
+ case CHARDEV_DISPLAY:
+ CHARDEV_DPRINTF("one output port %d %d\n", n, j);
+ if (j < 16 && chardev_open(cur) == 0) {
+@@ -587,6 +589,7 @@ int adb_cmd (adb_dev_t *dev, uint8_t cmd
+ case ADB_LISTEN:
+ memcpy(adb_send + 1, buf, len);
+ /* No break here */
++__attribute__((fallthrough));
+ case ADB_TALK:
+ adb_send[0] = (dev->addr << 4) | cmd | reg;
+ break;
+--- openhackware-0.4.1+git-20140423.c559da7c.orig/src/libc/src/format.c
 openhackware-0.4.1+git-20140423.c559da7c/src/libc/src/format.c
+@@ -281,6 +281,7 @@ int _vprintf(outf_t outf, void *private,
+ goto next;
+ }
+ /* No break here */
++__attribute__((fallthrough));
+ case '1' ... '9':
+ switch (maxfill) {
+ case -2:
+@@ -350,6 +351,7 @@ int _vprintf(outf_t outf, void *private,
+ goto invalid;
+ } else {
+ tmp = outc(outf, private, '%', maxlen - totlen);
++__attribute__((fallthrough));
+ }
+ default:
+ invalid:
+--- openhackware-0.4.1+git-20140423.c559da7c.orig/src/of.c
 openhackware-0.4.1+git-20140423.c559da7c/src/of.c
+@@ -3000,7 +3000,7 @@ void OF_finalize_pci_ide (void *dev,
+ {
+ OF_env_t *OF_env = OF_env_main;
+ OF_node_t *pci_ata = 

Bug#895580: RFS: peek/1.3.1-1 [ITP] -- Simple animated GIF screen recorder with GUI

2018-04-14 Thread Sergio Durigan Junior
On Saturday, April 14 2018, I wrote:

> On Friday, April 13 2018, I wrote:
>
>> On Thursday, April 12 2018, Boyuan Yang wrote:
>>
>>>   Dear mentors,
>>>
>>>   I am looking for a sponsor for my package "peek"
>>>
>>>  * Package name: peek
>>>Version : 1.3.1-1
>>>Upstream Author : Philipp Wolfer 
>>>  * URL : https://github.com/phw/peek
>>>  * License : GPL-3+
>>>Section : graphics
>>
>> Hi, Boyuan,
>>
>> I'm looking at the package right now.  So far, everything seems to be
>> OK.  I appreciated the way you took care of the licensing stuff, and how
>> d/copyright seems to cover all the bases.
>>
>> I'll let you know if I have questions, or when I upload it.
>
> Hi again,
>
> I've been having a few problems when building the package locally.  It's
> a build failure due to a missing header, and the strange thing is that
> it happens intermitently (i.e., sometimes I can build everything just
> fine, sometimes the build fails).  Here's the error:
>
>   /build/peek-debian/peek-tmp/obj-x86_64-linux-gnu/src/utils.c:16:10: fatal 
> error: application.h: No such file or directory
>#include "application.h"
> ^~~
>   compilation terminated.
>   make[4]: *** [tests/CMakeFiles/peek-test-utils.dir/build.make:126: 
> tests/CMakeFiles/peek-test-utils.dir/__/src/utils.c.o] Error 1
>   make[4]: *** Waiting for unfinished jobs
>
> After spending some time tracking down the issue, what I found is that
> "application.h" is generated automatically by Vala (see the
> "vala_precompile" rule on CMakeLists.txt).  I've compared the build logs
> generated by a successful build against those generated by an
> unsuccessful one, and there's nothing really wrong that I see.  Plus, if
> I rerun the "make" command after the failure the build succeeds.  So
> far, this is telling me that the problem seems to be a race condition
> (due to the way cmake parallelizes the jobs, maybe).
>
> I'll see if I manage to investigate a bit more, but I'd appreciate if
> you could take a look at this.

So, I tried disabling parallel builds:

  %:
  dh $@ --no-parallel

And was able to build the package at least 10 consecutive times without
any problems.  I think there's a bug in the parallel build, indeed.  Not
sure if it's something related to CMakeLists.txt (likely), or to cmake.

Anyway, I think we can proceed safely if you disable parallel builds for
now.  This is not the perfect solution, but it works fine, and the
program is small enough that even a non-parallel build finishes quick.

I'll wait until you address all the comments I've made, and then I'll
upload the package to the archives.

Thanks!

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature


Bug#895580: RFS: peek/1.3.1-1 [ITP] -- Simple animated GIF screen recorder with GUI

2018-04-14 Thread Sergio Durigan Junior
On Friday, April 13 2018, I wrote:

> On Thursday, April 12 2018, Boyuan Yang wrote:
>
>>   Dear mentors,
>>
>>   I am looking for a sponsor for my package "peek"
>>
>>  * Package name: peek
>>Version : 1.3.1-1
>>Upstream Author : Philipp Wolfer 
>>  * URL : https://github.com/phw/peek
>>  * License : GPL-3+
>>Section : graphics
>
> Hi, Boyuan,
>
> I'm looking at the package right now.  So far, everything seems to be
> OK.  I appreciated the way you took care of the licensing stuff, and how
> d/copyright seems to cover all the bases.
>
> I'll let you know if I have questions, or when I upload it.

Hi again,

I've been having a few problems when building the package locally.  It's
a build failure due to a missing header, and the strange thing is that
it happens intermitently (i.e., sometimes I can build everything just
fine, sometimes the build fails).  Here's the error:

  /build/peek-debian/peek-tmp/obj-x86_64-linux-gnu/src/utils.c:16:10: fatal 
error: application.h: No such file or directory
   #include "application.h"
^~~
  compilation terminated.
  make[4]: *** [tests/CMakeFiles/peek-test-utils.dir/build.make:126: 
tests/CMakeFiles/peek-test-utils.dir/__/src/utils.c.o] Error 1
  make[4]: *** Waiting for unfinished jobs

After spending some time tracking down the issue, what I found is that
"application.h" is generated automatically by Vala (see the
"vala_precompile" rule on CMakeLists.txt).  I've compared the build logs
generated by a successful build against those generated by an
unsuccessful one, and there's nothing really wrong that I see.  Plus, if
I rerun the "make" command after the failure the build succeeds.  So
far, this is telling me that the problem seems to be a race condition
(due to the way cmake parallelizes the jobs, maybe).

I'll see if I manage to investigate a bit more, but I'd appreciate if
you could take a look at this.

Meanwhile, I have small nits to point out that I'd like answered/solved
before we proceed with the upload:

1) On d/rules, is there any reason you're using:

  export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed

  ?

2) You can remove the following line from override_dh_auto_configure
(also on d/rules):

  -DCMAKE_LIBRARY_ARCHITECTURE="$(DEB_TARGET_MULTIARCH)"

  Since you're not building a library, this is not needed.

3) I'd like to see the buildsystem explicitly specified on the "%" rule,
like:

  %:
  dh $@ --buildsystem=cmake

Other than that, the package looks good to me.  Once we solve the build
failure, I'll gladly upload it for you!

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature


Bug#838372: stterm: New upstream version

2018-04-14 Thread WubTheCaptain
Followup-For: Bug #838372
Package: stterm
Version: 0.6-1
X-Debbugs-CC: Jari Aalto 

Dear Maintainer,

I've attached a gzip compressed diff for an unreleased st 0.6 ->
0.8.1-1.1 (UNRELEASED) Debian package update. (First time, be gentle.)
I hope you find it useful.

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

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

Versions of packages stterm depends on:
ii  libc6   2.27-3
ii  libfontconfig1  2.13.0-4
ii  libx11-62:1.6.5-1
ii  libxft2 2.3.2-1+b2

stterm recommends no packages.

stterm suggests no packages.

-- no debconf information


stterm_0.6-1.dsc_stterm_0.8.1-1.1.dsc.diff.gz
Description: application/gzip


Bug#895681: RFS: arc/5.21q-6

2018-04-14 Thread Paul Wise
On Sat, Apr 14, 2018 at 10:19 PM, Ricardo Fantin da Costa wrote:

> Changes since the last upload:

These seem relatively minor and not worth a rebuild.

If you lack ideas for how to improve the package:

https://tracker.debian.org/pkg/arc
https://packages.qa.debian.org/a/arc.html

I would suggest forwarding the security issues to the upstream github repo.

In addition you could check the package with check-all-the-things.

> I checked the
> https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt and no
> change appear to be necessary.

Then you should bump the Standards-Version and mention that in the changelog.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



Bug#895713: FTBFS with googletest 1.8.0-7

2018-04-14 Thread Steve M. Robbins
Source: ros-catkin
Version: 0.7.11-1
Severity: serious
Justification: fails to build from source

Debian's googletest package used to ship only sources, not a compiled
libgtest.  The ros-catkin package has a build-dep on libgtest-dev.
However: at build time libgtest is probed for, not found, and C++
tests are not built:

-- gtest not found, C++ tests can not be built. Please install the gtest 
headers globally in your system to enable gtests

https://buildd.debian.org/status/fetch.php?pkg=ros-catkin=all=0.7.11-1=1522532229=0


In libgtest-dev 1.8.0-7, a compiled libgtest was added.  Now the
ros-catkin fails while attempting to build tests:

-- Found gtest: gtests will be built
CMake Error at cmake/test/gtest.cmake:369 (add_library):
  add_library cannot create imported target "gtest" because another target
  with the same name already exists.
Call Stack (most recent call first):
  cmake/all.cmake:147 (include)
  CMakeLists.txt:8 (include)


Additionally, the flaw in gtest.cmake appears to be the cause of
ros-rospack build failure tracked in Bug #895708 -- contrary to what
was previously written in that bug -- as the ros-rospack build fails
at the same lines in the installed version of gtest.cmake:

-- Found gtest: gtests will be built
CMake Error at /usr/share/catkin/cmake/test/gtest.cmake:369 (add_library):
  add_library cannot create imported target "gtest" because another target
  with the same name already exists.
Call Stack (most recent call first):
  /usr/share/catkin/cmake/all.cmake:147 (include)
  /usr/share/catkin/cmake/catkinConfig.cmake:20 (include)
  CMakeLists.txt:4 (find_package)


I suspect that other ROS packages will be similarly affected.

-Steve




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

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



Bug#895712: ITP: misspell-fixer -- Tool for fixing common misspellings, typos in source code.

2018-04-14 Thread Paul Wise
On Sun, 15 Apr 2018 00:49:05 +0100 Lajos Veres wrote:

> I have not found any sourcecode typofixer tool in Debian.

codespell -w
spellintian (doesn't autofix)

Some more that are not yet in Debian:

https://jwilk.net/software/mwic
https://jwilk.net/software/anorack
https://github.com/client9/misspell
https://github.com/lyda/misspell-check

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Bug#864588: Intention to adopt

2018-04-14 Thread HUGEPRIME
I have been advised in #debian-mentors to tell you i am working on this bug and 
ask if i may adopt this bug

Thank you

Bug#895712: ITP: misspell-fixer -- Tool for fixing common misspellings, typos in source code.

2018-04-14 Thread Lajos Veres
Package: wnpp
Severity: wishlist
Owner: Lajos Veres 

* Package name: misspell-fixer
  Version : 2018.04.15
  Upstream Author : Lajos Veres 
* URL : https://github.com/vlajos/misspell-fixer
* License : BSD
  Programming Lang: Bash
  Description : Tool for fixing common misspellings, typos in source code.

 Utility to fix common misspellings, typos in source code.
 There are lots of typical misspellings in program code.
 Typically they are more eye-catching in the living code but they can easily
hide in comments, examples, samples, notes and documentation.
 With this utility you can fix a large number of them very quickly.

---
Reason:
I have not found any sourcecode typofixer tool in Debian.
Some users also mentioned that their life would be a little easier with a
packaged version.



Bug#895711: gstreamer1.0: please add support for riscv64

2018-04-14 Thread Aurelien Jarno
Package: gstreamer1.0
Version: 1.14.0-1
Severity: normal
Tags: upstream patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=795271

Hi,

We are in the process of bootstrapping a Debian port for the
riscv64 architecture (https://wiki.debian.org/RISC-V). It happens that
gstreamer needs an architecture specific defined about aligned accesses,
otherwise it fails to build with:

| In file included from ../gst_private.h:42:0,
|  from parse.l:2:
| ../../gst/gstconfig.h:112:4: error: #error "Could not detect architecture; 
don't know whether it supports unaligned access! Please file a bug."
|  #  error "Could not detect architecture; don't know whether it supports 
unaligned access! Please file a bug."

Full build log is available here:
https://buildd.debian.org/status/fetch.php?pkg=gstreamer1.0=riscv64=1.14.0-1=1522656689=0

As requested in the error message, I have filed a bug with at patch
upstream: 
https://bugzilla.gnome.org/show_bug.cgi?id=795271

I have also prepared the corresponding patch for the debian package,
please find it attached. Would it be possible to include it to the next
upload?

Thanks,
Aurelien

-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: riscv64

Kernel: Linux 4.15.0_riscv-linux-4.15_2b0aa1de4+ (SMP w/1 CPU core)
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)
diff -Nru gstreamer1.0-1.14.0/debian/patches/0002-riscv64.patch 
gstreamer1.0-1.14.0/debian/patches/0002-riscv64.patch
--- gstreamer1.0-1.14.0/debian/patches/0002-riscv64.patch   1970-01-01 
01:00:00.0 +0100
+++ gstreamer1.0-1.14.0/debian/patches/0002-riscv64.patch   2018-04-13 
23:55:26.0 +0200
@@ -0,0 +1,11 @@
+--- a/gst/gstconfig.h.in
 b/gst/gstconfig.h.in
+@@ -104,7 +104,7 @@
+  * http://docs.oracle.com/cd/E19205-01/820-4155/c++_faq.html#Vers6
+  * https://software.intel.com/en-us/node/583402
+  */
+-#if defined(__alpha__) || defined(__arc__) || defined(__arm__) || 
defined(__aarch64__) || defined(__bfin) || defined(__hppa__) || 
defined(__nios2__) || defined(__MICROBLAZE__) || defined(__mips__) || 
defined(__or1k__) || defined(__sh__) || defined(__SH4__) || defined(__sparc__) 
|| defined(__sparc) || defined(__ia64__) || defined(_M_ALPHA) || 
defined(_M_ARM) || defined(_M_IA64) || defined(__xtensa__) || defined(__e2k__)
++#if defined(__alpha__) || defined(__arc__) || defined(__arm__) || 
defined(__aarch64__) || defined(__bfin) || defined(__hppa__) || 
defined(__nios2__) || defined(__MICROBLAZE__) || defined(__mips__) || 
defined(__or1k__) || defined(__sh__) || defined(__SH4__) || defined(__sparc__) 
|| defined(__sparc) || defined(__ia64__) || defined(_M_ALPHA) || 
defined(_M_ARM) || defined(_M_IA64) || defined(__xtensa__) || defined(__e2k__) 
|| defined(__riscv)
+ #  define GST_HAVE_UNALIGNED_ACCESS 0
+ #elif defined(__i386__) || defined(__i386) || defined(__amd64__) || 
defined(__amd64) || defined(__x86_64__) || defined(__ppc__) || 
defined(__ppc64__) || defined(__powerpc__) || defined(__powerpc64__) || 
defined(__m68k__) || defined(_M_IX86) || defined(_M_AMD64) || defined(_M_X64) 
|| defined(__s390__) || defined(__s390x__) || defined(__zarch__)
+ #  define GST_HAVE_UNALIGNED_ACCESS 1
diff -Nru gstreamer1.0-1.14.0/debian/patches/series 
gstreamer1.0-1.14.0/debian/patches/series
--- gstreamer1.0-1.14.0/debian/patches/series   2018-03-20 08:41:52.0 
+0100
+++ gstreamer1.0-1.14.0/debian/patches/series   2018-04-13 23:55:34.0 
+0200
@@ -1 +1,2 @@
 0001-registrybinary-Update-magic-version-string.patch
+0002-riscv64.patch


Bug#895707: gumbo-parser: diff for NMU version 0.10.1+dfsg-2.2

2018-04-14 Thread Steve M. Robbins
Control: tags 895707 + patch
Control: tags 895707 + pending

Dear maintainer,

I've prepared an NMU for gumbo-parser (versioned as 0.10.1+dfsg-2.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru gumbo-parser-0.10.1+dfsg/debian/changelog gumbo-parser-0.10.1+dfsg/debian/changelog
--- gumbo-parser-0.10.1+dfsg/debian/changelog	2015-12-30 12:45:37.0 -0600
+++ gumbo-parser-0.10.1+dfsg/debian/changelog	2018-04-14 18:20:28.0 -0500
@@ -1,3 +1,10 @@
+gumbo-parser (0.10.1+dfsg-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Tweak 00-tests.patch to ignore system libgtest (Closes: #895707)
+
+ -- Steve M. Robbins   Sat, 14 Apr 2018 18:20:28 -0500
+
 gumbo-parser (0.10.1+dfsg-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru gumbo-parser-0.10.1+dfsg/debian/patches/00-tests.patch gumbo-parser-0.10.1+dfsg/debian/patches/00-tests.patch
--- gumbo-parser-0.10.1+dfsg/debian/patches/00-tests.patch	2015-12-30 12:22:04.0 -0600
+++ gumbo-parser-0.10.1+dfsg/debian/patches/00-tests.patch	2018-04-14 15:52:03.0 -0500
@@ -3,11 +3,15 @@
 Forwarded: not-needed
 Last-Update: 2014-10-13
 
 a/Makefile.am
-+++ b/Makefile.am
-@@ -9,31 +9,17 @@
+--- gumbo-parser-0.10.1+dfsg.orig/Makefile.am
 gumbo-parser-0.10.1+dfsg/Makefile.am
+@@ -7,35 +7,17 @@
  
- if !HAVE_SHARED_LIBGTEST
+ ACLOCAL_AMFLAGS = -I m4
+ 
+-if !HAVE_SHARED_LIBGTEST
++# Using Debian's libgtest-dev for tests
++GTEST_DIR = /usr/src/gtest
  
 -# Build gtest before we build protobuf tests.  We don't add gtest to SUBDIRS
 -# because then "make check" would also build and run all of gtest's own tests,
@@ -34,9 +38,6 @@
 -		echo "Making clean in gtest"; \
 -		cd gtest && $(MAKE) $(AM_MAKEFLAGS) clean; \
 -	fi
-+# Using Debian's libgtest-dev for tests
-+GTEST_DIR = /usr/src/gtest
-+
 +tests/gtest-all.o:
 +	$(CXX) $(CPPFLAGS) -I$(GTEST_DIR) $(CXXFLAGS) -c \
 +$(GTEST_DIR)/src/gtest-all.cc -o tests/gtest-all.o
@@ -44,19 +45,25 @@
 +tests/gtest_main.o:
 +	$(CXX) $(CPPFLAGS) -I$(GTEST_DIR) $(CXXFLAGS) -c \
 +$(GTEST_DIR)/src/gtest_main.cc -o tests/gtest_main.o
-+
  
- endif !HAVE_SHARED_LIBGTEST
+-endif !HAVE_SHARED_LIBGTEST
+ 
+ gentags: src/tag.in
+ 	@python gentags.py $<
+@@ -97,13 +79,9 @@
+ gumbo_test_DEPENDENCIES = libgumbo.la
+ gumbo_test_LDADD = libgumbo.la
  
-@@ -101,8 +87,9 @@
- # FIXME(bnoordhuis) Should be configurable by the user.
- gumbo_test_LDADD += -lgtest -lgtest_main
- else
+-if HAVE_SHARED_LIBGTEST
+-# FIXME(bnoordhuis) Should be configurable by the user.
+-gumbo_test_LDADD += -lgtest -lgtest_main
+-else
 -gumbo_test_DEPENDENCIES += check-local
 -gumbo_test_LDADD += gtest/lib/libgtest.la gtest/lib/libgtest_main.la
+-endif
 +gumbo_test_DEPENDENCIES += tests/gtest-all.o tests/gtest_main.o
 +gumbo_test_LDADD += tests/gtest-all.o tests/gtest_main.o
 +gumbo_test_LDFLAGS = -pthread
- endif
  
  noinst_PROGRAMS = clean_text find_links get_title positions_of_class benchmark serialize prettyprint
+ LDADD = libgumbo.la


signature.asc
Description: PGP signature


Bug#895710: ghc: Doesn't provide haddock-interface-31 on hppa

2018-04-14 Thread John David Anglin
Source: ghc
Version: 8.2.2-3
Severity: normal

Dear Maintainer,

The virtual package haddock-interface-31 does not seem to be provided on hppa:

mx3210:/home/dave/gnu/gcc/objdir# apt-get install ghc-doc ghc
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 ghc-doc : Depends: haddock-interface-31 but it is not installable
E: Unable to correct problems, you have held broken packages.

mx3210:/home/dave/gnu/gcc/objdir# apt-get install ghc
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libghc-base-orphans-dev libghc-base-orphans-prof libghc-contravariant-dev
  libghc-contravariant-prof libghc-data-default-class-dev
  libghc-data-default-class-prof libghc-data-default-instances-containers-dev
  libghc-data-default-instances-containers-prof
  libghc-data-default-instances-dlist-dev
  libghc-data-default-instances-dlist-prof
  libghc-data-default-instances-old-locale-dev
  libghc-data-default-instances-old-locale-prof libghc-distributive-dev
  libghc-distributive-prof libghc-dlist-dev libghc-dlist-prof
  libghc-exceptions-dev libghc-exceptions-prof libghc-parsec3-dev
  libghc-parsec3-prof libghc-prelude-extras-dev libghc-prelude-extras-prof
  libghc-primitive-dev libghc-primitive-prof libghc-semigroups-dev
  libghc-semigroups-prof libghc-statevar-dev libghc-statevar-prof
  libghc-tagged-dev libghc-tagged-prof libghc-transformers-compat-dev
  libghc-transformers-compat-prof libghc-utf8-string-dev
  libghc-utf8-string-prof libghc-void-dev libghc-void-prof libnfs8
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  ghc-prof libghc-assert-failure-dev libghc-assert-failure-prof
  libghc-async-dev libghc-async-prof libghc-base-orphans-dev
  libghc-base-orphans-prof libghc-call-stack-dev libghc-contravariant-dev
  libghc-contravariant-prof libghc-data-default-class-dev
  libghc-data-default-class-prof libghc-data-default-instances-containers-dev
  libghc-data-default-instances-containers-prof
  libghc-data-default-instances-dlist-dev
  libghc-data-default-instances-dlist-prof
  libghc-data-default-instances-old-locale-dev
  libghc-data-default-instances-old-locale-prof libghc-distributive-dev
  libghc-distributive-prof libghc-dlist-dev libghc-dlist-prof
  libghc-enummapset-th-dev libghc-enummapset-th-prof libghc-exceptions-dev
  libghc-exceptions-prof libghc-hashable-dev libghc-hashable-prof
  libghc-haskell-lexer-dev libghc-haskell-lexer-prof libghc-hunit-dev
  libghc-minimorph-dev libghc-minimorph-prof libghc-miniutter-dev
  libghc-miniutter-prof libghc-mtl-dev libghc-mtl-prof libghc-old-locale-dev
  libghc-old-locale-prof libghc-old-time-dev libghc-old-time-prof
  libghc-parsec3-dev libghc-parsec3-prof libghc-prelude-extras-dev
  libghc-prelude-extras-prof libghc-pretty-show-dev libghc-pretty-show-prof
  libghc-primitive-dev libghc-primitive-prof libghc-random-dev
  libghc-random-prof libghc-semigroups-dev libghc-semigroups-prof
  libghc-split-dev libghc-split-prof libghc-statevar-dev libghc-statevar-prof
  libghc-stm-dev libghc-stm-prof libghc-tagged-dev libghc-tagged-prof
  libghc-text-dev libghc-text-prof libghc-transformers-compat-dev
  libghc-transformers-compat-prof libghc-unordered-containers-dev
  libghc-unordered-containers-prof libghc-utf8-string-dev
  libghc-utf8-string-prof libghc-void-dev libghc-void-prof libghc-zlib-dev
  libghc-zlib-prof
Suggested packages:
  ghc-doc haskell-doc llvm-3.9 libghc-assert-failure-doc libghc-async-doc
  libghc-base-orphans-doc libghc-call-stack-doc libghc-call-stack-prof
  libghc-contravariant-doc libghc-data-default-class-doc
  libghc-data-default-instances-containers-doc
  libghc-data-default-instances-dlist-doc
  libghc-data-default-instances-old-locale-doc libghc-distributive-doc
  libghc-dlist-doc libghc-enummapset-th-doc libghc-exceptions-doc
  libghc-hashable-doc libghc-haskell-lexer-doc libghc-hunit-doc
  libghc-hunit-prof libghc-minimorph-doc libghc-miniutter-doc libghc-mtl-doc
  libghc-old-locale-doc libghc-old-time-doc libghc-parsec3-doc
  libghc-prelude-extras-doc libghc-pretty-show-doc libghc-primitive-doc
  libghc-random-doc libghc-semigroups-doc libghc-split-doc libghc-statevar-doc
  libghc-stm-doc libghc-tagged-doc libghc-text-doc
  libghc-transformers-compat-doc libghc-unordered-containers-doc
  libghc-utf8-string-doc libghc-void-doc libghc-zlib-doc
The following packages will be REMOVED:
  ghc-doc libghc-bifunctors-dev libghc-bifunctors-prof libghc-byteable-doc
  libghc-cairo-dev libghc-cairo-prof libghc-comonad-dev 

Bug#833270: poor text wrapping for Wastebasket icon in default install

2018-04-14 Thread Andriy Grytsenko
control: reassign -1 pcmanfm
control: affects -1 + lxde-common

Thank you for the report.

Actually you reported three issues into one, that is not an appropriate
way to do reports.

In regards of exact issue. Wrapping is done by the desktop manager in an
obvious reason - the text does not fit into default space under the icon.
There are two solutions for that:
 - decrease desktop font size (currently: Sans 12, in desktop config);
 - increase desktop cell size (currently: 100 pt, in pcmanfm sources).
Note that in case of default font size we can change only value applied
to newly created users or after ~/.config/pcmanfm reset. In other cases
only manual changes may be applied.



Bug#895709: libvirt-daemon-system: conffiles not removed

2018-04-14 Thread Paul Wise
Package: libvirt-daemon-system
Version: 4.2.0-2
Severity: normal
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate

The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by
dh_installdeb to remove these obsolete conffiles on upgrade.

https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
https://manpages.debian.org/man/1/dh_installdeb

This bug report brought to you by adequate:

http://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/

$ pkg=libvirt-daemon-system ; adequate $pkg ; dpkg-query -W -f='${Conffiles}\n' 
$pkg | grep obsolete
libvirt-daemon-system: obsolete-conffile /etc/logrotate.d/libvirtd.uml
libvirt-daemon-system: obsolete-conffile /etc/logrotate.d/libvirtd.qemu
libvirt-daemon-system: obsolete-conffile /etc/logrotate.d/libvirtd.lxc
libvirt-daemon-system: obsolete-conffile /etc/logrotate.d/libvirtd.libxl
libvirt-daemon-system: obsolete-conffile /etc/logrotate.d/libvirtd
 /etc/logrotate.d/libvirtd.uml 9c5dbd5acdeb2d796fa02bf24a0cf8f3 obsolete
 /etc/logrotate.d/libvirtd.qemu 3e69942456971307a2d7c97e3ac75713 obsolete
 /etc/logrotate.d/libvirtd.lxc 957837303a5d07d8d8bf7d9e4437e078 obsolete
 /etc/logrotate.d/libvirtd.libxl 995ed139010ce8834956277b53a1994d obsolete
 /etc/logrotate.d/libvirtd 07c99d1b26b30055fb4d1fc26652dc94 obsolete

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages libvirt-daemon-system depends on:
ii  adduser3.117
ii  debconf [debconf-2.0]  1.5.66
ii  gettext-base   0.19.8.1-6
ii  iptables   1.6.2-1
ii  libacl12.2.52-3+b1
ii  libapparmor1   2.12-4
ii  libaudit1  1:2.8.2-1
ii  libblkid1  2.31.1-0.5
ii  libc6  2.27-3
ii  libcap-ng0 0.7.7-3.1+b1
ii  libdbus-1-31.12.6-2
ii  libdevmapper1.02.1 2:1.02.145-4.1
ii  libgnutls303.5.18-1
ii  libnl-3-2003.2.27-2
ii  libnl-route-3-200  3.2.27-2
ii  libnuma1   2.0.11-2.1
ii  libselinux12.7-2+b2
ii  libvirt-clients4.2.0-2
ii  libvirt-daemon 4.2.0-2
ii  libvirt0   4.2.0-2
ii  libxml22.9.4+dfsg1-6.1
ii  libyajl2   2.1.0-2+b3
ii  logrotate  3.11.0-0.1
ii  lsb-base   9.20170808
ii  policykit-10.105-20

Versions of packages libvirt-daemon-system recommends:
pn  bridge-utils 
ii  dmidecode3.1-1
ii  dnsmasq-base [dnsmasq-base]  2.79-1
ii  ebtables 2.0.10.4-3.5+b1
ii  iproute2 4.15.0-3
ii  parted   3.2-21

Versions of packages libvirt-daemon-system suggests:
pn  apparmor
pn  auditd  
pn  nfs-common  
ii  pm-utils1.4.1-17
pn  radvd   
ii  systemd 238-4
pn  systemtap   
pn  zfsutils

-- debconf information:
  libvirt-daemon-system/id_warning: true

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Bug#895673: lios: Lios crashing on start

2018-04-14 Thread Samuel Thibault
Control: tags -1 + pending

Hello,

Claudio Ferreira, le sam. 14 avril 2018 08:51:53 -0300, a ecrit:
> So, was to install this package and Lios works again. IMHO, isn't a good idea
> to add this package as dependency of Lios? 

Indeed, that was missing, will uploaded with it.

Thanks,
Samuel



Bug#895505: googletest 1.8.0-7 makes many packages FTBFS

2018-04-14 Thread Steve Robbins
clone 895505 -1 -2 
reassign -1 gumbo-parser
reassign -2 ros-rospack
retitle -1 use gtest sources or use -pthread with system libgtest
retitle -2 use gtest sources or use -pthread with system libgtest
tags 895505 + pending
thanks

On Thursday, April 12, 2018 1:28:45 AM CDT you wrote:
> Package: googletest
> Version: 1.8.0-7
> Severity: serious
> Control: affects -1 src:gumbo-parser src:ros-rospack src:colobot
> src:arrayfire src:opensurgsim src:rapidjson src:gfal2 src:kodi src:davix
> src:libqtdbustest src:properties-cpp src:libqtdbusmock

Two independent changes to googletest 1.8.0-7 led to the failures:

1. The shipped /usr/src/gtest/CMakeLists.txt has a bug that makes it unuseable 
-- install TARGETS is now a variable that relies on include(GNUInstallDirs).  
Bug #895505 is tracking this issue.

2. A compiled library is now included.  gumbo-parser and ros-rospack 
dynamically detect this and attempt to use it without using -pthread.  These 
packages need to either ignore the system lib and use the sources or link with 
-pthread.  This is being tracked in the two cloned bugs.

-Steve


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


Bug#893212: Pending fixes for bugs in the jsoup package

2018-04-14 Thread pkg-java-maintainers
tag 893212 + pending
thanks

Some bugs in the jsoup package are closed in revision
e410d0dcb216812d65fda0ca9e59da747649e6b6 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jsoup.git/commit/?id=e410d0d

Commit message:

Ignore the test failures with Java 9.

Closes: #893212



Bug#895706: Please add the full GPL-3 COPYING text for Valama's cmake module

2018-04-14 Thread Nicholas D Steeves
Package: kio-gdrive
Version: 1.2.2-1
Severity: normal
Tags: upstream

Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=393148

This bug tracks the upstream status of Scott K's (FTP Master) request
for full license text for a GPL-3 cmake module in kio-gdrive's GPL-2
source package.



Bug#895705: missing ";" passed syntax checks

2018-04-14 Thread 積丹尼 Dan Jacobson
Package: perl
Version: 5.26.1-5
Severity: wishlist

This missing ";" passed syntax checks:

use Data::Dumper;
use Time::Piece
$Data::Dumper::Indent = $Data::Dumper::Sortkeys = 1;
my $doc;



Bug#891636: latexmk: Please do upload this

2018-04-14 Thread Reuben Thomas
Package: latexmk
Version: 1:4.41-1
Followup-For: Bug #891636

It would be great to have this, as I am finding bugs in latexmk 4.41 that
are fixed since then, and already it is too late for Ubuntu 16.04. It would
be nice not to have to work around these bugs, or have to install a newer
version of latexmk manually, for too many more years!

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages latexmk depends on:
ii  perl5.22.1-9ubuntu0.2
ii  texlive-latex-base  2017.20170619-1~16.04.york0

Versions of packages latexmk recommends:
ii  evince [postscript-viewer]   3.18.2-1ubuntu4.3
ii  ghostscript [postscript-viewer]  9.18~dfsg~0-0ubuntu2.7
ii  mupdf [pdf-viewer]   1.7a-1
ii  okular [postscript-viewer]   4:15.12.3-0ubuntu1

Versions of packages latexmk suggests:
ii  ghostscript  9.18~dfsg~0-0ubuntu2.7

-- no debconf information



Bug#895704: ctioga2: Don't Build-Depend on cdbs

2018-04-14 Thread Jeremy Bicha
Source: ctioga2
Version: 0.14.1-1
Severity: minor
Tags: patch
X-Debbugs-CC: nthyk...@debian.org

ctioga2 is unusual because it uses both dh and cdbs [1].

I created a merge proposal to fix this issue. [2]

[1] 
https://nthykier.wordpress.com/2016/04/26/putting-debian-packages-in-labelled-boxes/
[2] https://salsa.debian.org/ruby-team/ctioga2/merge_requests/1

Thanks,
Jeremy Bicha



Bug#895674: lintian: maybe-not-arch-all-binnmuable emitted for (= ${source:Version})

2018-04-14 Thread Jeremy Bicha
On Sat, Apr 14, 2018 at 5:49 PM, Chris Lamb  wrote:
> I don't see how any of these (*) are useful to some wishing to
> uncover hidden problems with their packages.

I guess I'd want to know if the source format were not 3.0 (quilt) but
that's a rare enough issue that it's probably not worth the noise.
I'll go ahead and turn off classification on my system.

Thanks,
Jeremy Bicha



Bug#893697:

2018-04-14 Thread Sascha Steinbiss
Hi Sandro,

thanks for your reply.

>> this is also a problem in iva [1]. Patch attached — any comments? I don’t 
>> have too much experience with NMUs, would that be OK here? What delay would 
>> you recommend?
> 
> please hold your NMU, i'll prepare the new upstream release instead

Sure, thanks a lot for that!

Cheers
Sascha


signature.asc
Description: Message signed with OpenPGP


Bug#893809: screengrab: It's not possible to set a systemwide config

2018-04-14 Thread Alf Gaida
not really - but this will take some time
https://github.com/lxqt/screengrab/issues/48
https://github.com/lxqt/screengrab/issues/49

screengrab is/was a really ancient application - so the cleanup will
take some time. We just have decided not to implement screenshots and
their handling in lximage-qt - and to modernize screengrab.



Bug#895703: Continuous LIBUSB_ERROR_NO_DEVICE in journal after removing a Yubikey 4 (USB-C)

2018-04-14 Thread Luke W Faraone
Package: pcscd
Version: 1.8.23-2
Severity: normal

Dear maintainer,

This appears to be similar symptoms to bug #459827, but reporting
separately, as this has nothing to do with PCMCIA.

After removing a Yubikey 4 (USB-C) from my XPS 13 9360, syslog is filled
with errors like this about once a second:

```
Apr 04 11:04:56 zinc pcscd[4147]:  ccid_usb.c:849:WriteUSB() write 
failed (3/2): -4 LIBUSB_ERROR_NO_DEVICE
Apr 04 11:04:56 zinc pcscd[4147]: 0056 ifdwrapper.c:364:IFDStatusICC() Card 
not transacted: 617
Apr 04 11:04:57 zinc pcscd[4147]: 01000882 
eventhandler.c:334:EHStatusHandlerThread() Error communicating to: Yubico 
Yubikey 4 OTP+U2F+CCID 00 00
Apr 04 11:04:57 zinc pcscd[4147]: 0029 ccid_usb.c:1312:InterruptRead() 
libusb_submit_transfer failed: LIBUSB_ERROR_NO_DEVICE
Apr 04 11:04:57 zinc pcscd[4147]: 00400296 ccid_usb.c:849:WriteUSB() write 
failed (3/2): -4 LIBUSB_ERROR_NO_DEVICE
Apr 04 11:04:57 zinc pcscd[4147]: 0017 ifdwrapper.c:364:IFDStatusICC() Card 
not transacted: 617
```

This specific issue happened after a resume-from-suspend when the device
was removed between suspend and resume, but in general it happens any
time I remove the USB-C device.

This does not occur with a Yubikey Neo (USB 2.0).

I was also able to replicate it on a fellow developer's XPS 13 9350.
Please let me know if there is any other debugging information I can
provide.

Cheers,
Luke Faraone

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

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

Versions of packages pcscd depends on:
ii  libc6   2.27-3
ii  libccid [pcsc-ifd-handler]  1.4.29-2
ii  libpcsclite11.8.23-2
ii  libsystemd0 238-4
ii  libudev1238-4
ii  lsb-base9.20170808

pcscd recommends no packages.

Versions of packages pcscd suggests:
ii  systemd  238-4

-- no debconf information



Bug#895686: installation-birthday: Incorrectly identifies the birthdate of my system

2018-04-14 Thread Chris Lamb
Hi!

> > Getcha. Can you provide the output of:
> > 
> >  $ ls -l --sort=time /var/log /etc

Hm, none of these seem like good candidates to add. :(  Can you
hunt around for any file you think matches? Perhaps an "ls -l --
sort=time" for "/" and "/root" and "/boot" might help here?


Regards,

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



Bug#895674: lintian: maybe-not-arch-all-binnmuable emitted for (= ${source:Version})

2018-04-14 Thread Chris Lamb
Hi Jeremy,

> Do you have a list of all the classification checks to
> help me reconsider?

  control-tarball-compression-format
  ctrl-script
  data-tarball-compression-format
  debhelper-autoscript-in-maintainer-scripts
  debian-build-system
  elf-maintainer-script
  maintainer-script-interpreter
  maybe-not-arch-all-binnmuable
  no-ctrl-scripts
  rules-does-not-require-root
  rules-requires-root-explicitly
  rules-requires-root-implicitly
  source-format

I don't see how any of these (*) are useful to some wishing to
uncover hidden problems with their packages. Indeed, it is almost
certianly a net negative due to the additional output they would
emit, leading to stronger errors and warnings being potentially
hidden from human eyes.

> I don't show experimental tags.

To show classification tags yet not experimental ones is very rare
way of regularly using Lintian IMHO. Classification tags are designed
for reporting/statistics purposes, eg. generating pretty graphs on
lintian.debian.org.

Putting it another way, if you are using a classification tag for
_actionable_ advice, then it suggests that tag should not be a
classification tag.

(*) This, I believe, is the case for maybe-not-arch-all-binnmuable.
As I see it, it should be moved to a experimental severity and,
perhaps, something added to the text to underline that it should
not be blindly followed.


Regards,

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



Bug#895649: inkscape: Segfault closing dialog after importing PDF

2018-04-14 Thread Mattia Rizzolo
Control: tag -1 unreproducible

Hi Kevin,

On Fri, Apr 13, 2018 at 07:25:25PM -0600, Kevin Locke wrote:
> 4.  Open a second, PDF file with a different name (can be same or
> different file contents).
> This should open a second window for second PDF, but the second
> window will have no dialogs open while the first window has two
> duplicate Layers dialogs open.

I tried a couple of times, but this doesn't happen to me as you
describe, the second PDF opens in a new window, with not Layers dialog,
and the first window keeps only one -its own- Layers dialog.

> At this point Inkscape will crash with SIGSEGV and the following
> backtrace:
… 
> If you need any more details or more symbols in the backtrace, let me
> know.

Could you please open a bug upstream on
https://bugs.launchpad.net/inkscape ?
We will then add a bug link here, but it's really an upstream problem.

Thanks in advance.

-- 
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#893187: Pending fixes for bugs in the csvjdbc package

2018-04-14 Thread pkg-java-maintainers
tag 893187 + pending
thanks

Some bugs in the csvjdbc package are closed in revision
366fe849bcc940c0f5809ace9fa78dcec72bf054 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/csvjdbc.git/commit/?id=366fe84

Commit message:

Ignore the timestamp test failure which is not a problem but prevents the

package from building.

Closes: #893187



Bug#893697:

2018-04-14 Thread Sandro Tosi
> this is also a problem in iva [1]. Patch attached — any comments? I don’t 
> have too much experience with NMUs, would that be OK here? What delay would 
> you recommend?

please hold your NMU, i'll prepare the new upstream release instead

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



Bug#895702: zulupolkit: description is lacking details

2018-04-14 Thread Daniel Kahn Gillmor
Package: zulupolkit
Severity: normal

zulupolkit's "Description" in english is:

  "handler the polkit privileges"

It should say something more detailed about what the package actually
is -- the one-line description needs to be useful on its own, not just
when compared with other binary packages of the same source.

 --dkg

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

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

Versions of packages zulupolkit depends on:
ii  libc6   2.27-3
ii  libgcc1 1:8-20180402-1
ii  libqt5core5a5.9.2+dfsg-12
ii  libqt5network5  5.9.2+dfsg-12
ii  libstdc++6  8-20180402-1
ii  policykit-1 0.105-20

zulupolkit recommends no packages.

zulupolkit suggests no packages.



Bug#895505: googletest 1.8.0-7 makes many packages FTBFS

2018-04-14 Thread Adrian Bunk
On Sat, Apr 14, 2018 at 03:45:06PM -0500, Steve Robbins wrote:
>...
> The remaining links lead to a summary page that says things like 
> "build_id_differences_only".  Is this truly a build failure?  Can you point 
> me 
> to a build log?

Please click on the "rbuild" link at the left side.

> Thanks again,
> -Steve

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#895505: googletest 1.8.0-7 makes many packages FTBFS

2018-04-14 Thread Steve Robbins
Adrian:

Thanks for the rapid feedback!

On Thursday, April 12, 2018 1:28:45 AM CDT you wrote:
> Package: googletest
> Version: 1.8.0-7
> Severity: serious
> Control: affects -1 src:gumbo-parser src:ros-rospack src:colobot
> src:arrayfire src:opensurgsim src:rapidjson src:gfal2 src:kodi src:davix
> src:libqtdbustest src:properties-cpp src:libqtdbusmock

> I do not know whether these are one or more regressions in googletest,
> or whether these are bugs in the packages that now FTBFS.

Three of the links listed:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gumbo-parser.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/
rapidjson.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/
libqtdbustest.html

lead to build logs that indeed are probably regressions due to the new 
googletest.  I will propose patches for each.

The remaining links lead to a summary page that says things like 
"build_id_differences_only".  Is this truly a build failure?  Can you point me 
to a build log?

Thanks again,
-Steve


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


Bug#895696: firmware-ath9k-htc: doesn't work with wlx* interface names

2018-04-14 Thread Vagrant Cascadian
Control: retitle 895696 firmware-ath9k-htc: does not work with network-manager 
wifi.scan-rand-mac-address
Control: forwarded 895696 
https://github.com/qca/open-ath9k-htc-firmware/issues/132

On 2018-04-14, Oleksij Rempel wrote:
> firmware has no idea about interface name.
> Most probably you are affected by this bug:
> https://github.com/qca/open-ath9k-htc-firmware/issues/132

Thanks for the quick response!

Indeed, the workaround described there fixed it. Repeating here just for
completeness:

Create /etc/NetworkManager/conf.d/no_mac_random.conf
[device-wlxa0f3c1187111]
match-device=wlxa0f3c1187111
wifi.scan-rand-mac-address=0

Adjust wlx* to match your device name.

live well,
  vagrant


signature.asc
Description: PGP signature


Bug#895701: dlib: Incomplete debian/copyright?

2018-04-14 Thread Chris Lamb
Source: dlib
Version: 19.10-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Hugo Lefeuvre 

Hi,

I just ACCEPTed dlib from NEW but noticed it was missing attribution 
in debian/copyright for at least assert.h, numerical_integration.cpp,
fhog.h, and possibly all of dlib-models, I am unsure..

(This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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



Bug#895700: installation-reports: Pinebook success with custom kernel

2018-04-14 Thread Vagrant Cascadian
Package: installation-reports
Severity: normal

Pinebook install mostly worked, though required an updated 4.16 kernel
with a custom device-tree, and a custom u-boot build. As some of that
gets mainlined, this might actually be a workable arm64 laptop soon!

live well,
  vagrant

-- Package-specific info:

Boot method: microSD
Image version: 
https://d-i.debian.org/daily-images/armhf/20180413-00:11/netboot/netboot.tar.gz
Date: 2018-04-13

Machine: Pinebook
Partitions:
 Filesystem Type 1K-blocksUsed Available Use% Mounted on
 udev   devtmpfs953752   0953752   0% /dev
 tmpfs  tmpfs   2017483108198640   2% /run
 /dev/mmcblk2p1 ext4   4739200 1812136   212  41% /
 tmpfs  tmpfs  1008736   0   1008736   0% /dev/shm
 tmpfs  tmpfs 5120   0  5120   0% /run/lock
 tmpfs  tmpfs  1008736   0   1008736   0% /sys/fs/cgroup
 tmpfs  tmpfs  1008736  48   1008688   1% /tmp
 tmpfs  tmpfs   201744   0201744   0% /run/user/1000

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [E]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[E]
Overall install:[O]

Comments/Problems:

Other than having to use a custom linux kernel, the install went quite
smoothly. I've added some of the required features into the kernel
packaging git, so the next experimental upload should include the
minimal features. A custom device-tree will be needed until the
device-tree is in mainline linux.

U-boot support is also not yet mainlined, so required a patched build
based on 2018.03.

atf-allwinner supports this model.

working: USB, microSD, eMMC, LCD (framebuffer console and X), keyboard,
  touchpad, serial console

not working: battery, wifi

not tested: audio output, hdmi video/audio

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20180413-02:03"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux pbke 4.16.0-trunk-arm64 #1 SMP Debian 4.16-1~exp2~20180413~3 
(2018-04-14) aarch64 GNU/Linux
usb-list: 
usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 4.16.0-trunk-arm64 ehci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 02 Device 01: Generic Platform OHCI controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 4.16.0-trunk-arm64 ohci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 03 Device 01: Generic Platform OHCI controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 4.16.0-trunk-arm64 ohci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 04 Device 01: EHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 4.16.0-trunk-arm64 ehci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 04 Device 02: USB2.0 Hub [05e3:0608]
usb-list:Level 01 Parent 01 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 04 Device 03: USB KEYBOARD [258a:000c]
usb-list:Level 02 Parent 02 Port 00  Class 00(>ifc ) Subclass 00 Protocol 00
usb-list:Manufacturer: HAILUCK CO.,LTD
usb-list:Interface 00: Class 03(HID  ) Subclass 01 Protocol 01 Driver usbhid
usb-list:Interface 01: Class 03(HID  ) Subclass 00 Protocol 00 Driver usbhid
usb-list: 
usb-list: Bus 04 Device 04: USB 10/100 LAN [0bda:8152]
usb-list:Level 02 Parent 02 Port 01  Class 00(>ifc ) Subclass 00 Protocol 00
usb-list:Manufacturer: Realtek
usb-list:Interface 00: Class ff(vend.) Subclass ff Protocol 00 Driver r8152
usb-list: 
usb-list: Bus 04 Device 05: USB 2.0 PC Cam [090c:037c]
usb-list:Level 02 Parent 02 Port 02  Class ef(misc ) Subclass 02 Protocol 01
usb-list:Manufacturer: Image Processor
usb-list:Interface 00: Class 0e(video) Subclass 01 Protocol 00 Driver 
uvcvideo
usb-list:Interface 01: 

Bug#712841: A bit late, but still an issue...

2018-04-14 Thread Axel Sommerfeldt
Just a reminder that this bug is still a thing. And yes, the model can be found 
in uLinux.conf:

root@qnap119:~# mount -o ro -t ext2 /dev/mtdblock5 /mnt
root@qnap119:~# more /mnt/uLinux.conf 
[System]
Model = TS-119
Internal Model = TS-119
...

BTW: Martin, thanks a lot for all the work. Having Debian on a qnap really 
rocks.



Bug#890399: problem with systemd overrides

2018-04-14 Thread Hans Freitag
Hello Libor,

I think that override.conf should not be there in the first place,
because that directory is for user configs. I wonder what the reason was
to do that sort of strange hack in the first place.

regards

Hans
-- 
Conesphere GmbH - In den Sohlen 34 - 29328 Faßberg - Germany
Handelsregister Amtsgericht Lüneburg: HRB 206882 | USt-ID: DE311851670
Geschäftsführer: Hans Freitag
https://www.conesphere.com/Telephone: +49 173 2345 227



Bug#895699: peruse: Incomplete debian/copyright?

2018-04-14 Thread Chris Lamb
Source: peruse
Version: 1.2+dfsg-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: tsimo...@ubuntu.com

Hi,

I just ACCEPTed peruse from NEW but noticed it was missing 
attribution in debian/copyright for at least Vishesh Handa.

This is in no way exhaustive (!) so please check over the
entire package carefully and address these on your next upload.


Regards,

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



Bug#895696: firmware-ath9k-htc: doesn't work with wlx* interface names

2018-04-14 Thread Oleksij Rempel
Hi,

firmware has no idea about interface name.
Most probably you are affected by this bug:
https://github.com/qca/open-ath9k-htc-firmware/issues/132

-- 
Regards,
Oleksij



signature.asc
Description: OpenPGP digital signature


Bug#895674: lintian: maybe-not-arch-all-binnmuable emitted for (= ${source:Version})

2018-04-14 Thread Jeremy Bicha
On Sat, Apr 14, 2018 at 3:32 PM, Chris Lamb  wrote:
>   
> https://salsa.debian.org/lintian/lintian/commit/800b1344880b70995c5a26754d2a891ae0ef7d5d
>
> … in particular:
>
>  At this time, please do not attempt to "fix" the problem.  It
>  is not clear what the solution is (if any at all).  Nor is it clear
>  that this is something that will be supported.

Note that that text was *removed* from the tag description in that commit (!!).

> So, alas, changes may even be incorrect (!). I am unsure, hence
> tagging as moreinfo for the time being.
>
> (As an aside, how come you show classification checks? Surely they
> are far too noisy/useless..? I also wonder if this should be an
> X "experimental" tag instead as that would have been less strange.)

I thought some of the classification tags were useful. Do you have a
list of all the classification checks to help me reconsider? I don't
show experimental tags.

This particular tag is problematic because it encourages people who
see the tag to change the packaging so that the tag isn't emitted. ( I
have done that in several packages but will undo it as I touch the
packages again and notice.)

Thanks,
Jeremy Bicha



Bug#895686: installation-birthday: Incorrectly identifies the birthdate of my system

2018-04-14 Thread Boyd Stephen Smith Jr.
  121337 Apr 14 14:00 Xorg.0.log
-rw-r-  1 root  adm42143 Apr 14 13:48 kern.log
-rw-r-  1 root  adm40337 Apr 14 13:48 messages
-rw-r-  1 root  adm11160 Apr 14 13:16 debug
-rw-r--r--  1 root  root   47308 Apr 14 13:16 dpkg.log
-rw-r--r--  1 root  root 188 Apr 14 13:16 
alternatives.log
drwxr-xr-x  1 root  root 756 Apr 14 13:16 apt
-rw---  1 root  root   60174 Apr 14 13:10 
preload.log
-rw-r--r--  1 root  root 996 Apr 14 10:24 aptitude
-rw-r-  1 root  adm20299 Apr 14 04:24 user.log
drwxr-xr-x  1 root  root 162 Apr 14 00:12 sysstat
-rw-r--r--  1 root  root  60 Apr 14 00:12 
prelink.log
-rw-r-  1 root  adm    72812 Apr 14 00:12 
syslog-20180414
drwxr-s---  1 Debian-exim   adm  626 Apr 14 00:12 exim4
drwxr-xr-x  1 root  root1596 Apr 14 00:12 cups
drwxr-xr-x  1 root  root4748 Apr 14 00:12 apache2
-rw-r--r--  1 minidlna  minidlna1053 Apr 13 16:42 
minidlna.log
-rw-r--r--  1 root  root   10193 Apr 13 16:41 
apcupsd.events
-rw-r-  1 root  adm 5400 Apr 13 00:10 
syslog-20180413.xz
-rw-r--r--  1 root  root   51119 Apr 12 04:54 
popularity-contest
-rw-r--r--  1 root  root  156224 Apr 12 04:54 
popularity-contest.new
-rw-r--r--  1 root  root   51066 Apr 12 00:14 
popularity-contest.0
-rw-r-  1 root  adm 6716 Apr 12 00:14 
syslog-20180412.xz
-rw-r-  1 root  adm 6308 Apr 11 00:10 
syslog-20180411.xz
-rw-r-  1 root  adm 6516 Apr 10 00:13 
syslog-20180410.xz
drwxr-x---  1 root  adm 1074 Apr  9 00:09 samba
-rw-r-  1 root  adm 6644 Apr  9 00:09 
syslog-20180409.xz
-rw-r-  1 root  adm   211653 Apr  8 00:13 messages.1
drwxrwxr-t  1 root  postgres 602 Apr  8 00:13 postgresql
-rw-r--r--  1 minidlna  minidlna 587 Apr  8 00:13 
minidlna.log.1
-rw-r-  1 root  adm42701 Apr  8 00:13 user.log.1
-rw-r-  1 root  adm   228827 Apr  8 00:13 
daemon.log.1
-rw-r-  1 root  adm   242216 Apr  8 00:13 auth.log.1
-rw-r-  1 root  adm 6988 Apr  8 00:13 
syslog-20180408.xz
-rw-r-  1 root  adm   251162 Apr  7 22:19 kern.log.1
-rw-r-  1 root  adm39594 Apr  5 23:07 debug.1
-rw-r--r--  1 root  root  182536 Apr  5 22:53 
Xorg.0.log.old
-rw-r--r--  1 root  root   38986 Apr  5 04:54 
popularity-contest.1.gz
-rw-r--r--  1 root  root   38977 Apr  5 00:13 
popularity-contest.2.gz
-rw-r-  1 root  adm52436 Apr  2 00:10 
daemon.log.2.xz
-rw-r-  1 root  adm74160 Apr  2 00:10 
messages.2.xz
-rw-r--r--  1 minidlna  minidlna 688 Apr  2 00:10 
minidlna.log.2.xz
-rw-r-  1 root  adm18028 Apr  2 00:10 
user.log.2.xz
-rw-r-  1 root  adm16736 Apr  2 00:10 
auth.log.2.xz
-rw-r-  1 root  adm71600 Apr  1 23:55 
kern.log.2.xz
-rw-r-  1 root  adm15752 Apr  1 13:00 debug.2.xz
-rw---  1 root  utmp   0 Apr  1 00:13 btmp
drwxr-x---  1 root  adm78720 Apr  1 00:13 
unattended-upgrades
drwxr-xr-x  1 root  root 152 Apr  1 00:13 ConsoleKit
-rw-r--r--  1 root  root  323636 Mar 29 19:46 dpkg.log.1
-rw-r--r--  1 root  root   38894 Mar 29 04:54 
popularity-contest.3.gz
-rw-r--r--  1 root  root   38934 Mar 29 00:14 
popularity-contest.4.gz
-rw-r--r--  1 root  root   11917 Mar 28 19:22 
alternatives.log.1
-rw-rw-r--  1 root  utmp   86400 Mar 27 19:00 wtmp.1
-rw-r--r--  1 root  root   15572 Mar 26 14:07 aptitude.1
-rw-rw-r--  1 root  utmp18704352 Mar 26 13:58 lastlog
-rw-r-  1 root  adm16480 Mar 25 02:03 
messages.3.xz
-rw-r--r--  1 minidlna  minidlna 476 Mar 25 02:03 
minidlna.log.3.xz
-rw-r-  1 root  adm15436 Mar 25 02:03 
daemon.log.3.xz
-rw-r-  1 root  adm 3700 Mar 25 02:03 
user.lo

Bug#895698: O: djvubind -- simple creation of djvu files

2018-04-14 Thread Clint Adams
Package: wnpp
Severity: normal

I intend to orphan the djvubind package.

The package description is:
 Djvubind facilitates creating high-quality djvu files, especially
 digital versions of scanned books. It functions as a wrapper that
 combines the djvulibre tools, minidjvu, and various ocr engines to
 provide a simple, single command creation of a djvu file.



Bug#895696: firmware-ath9k-htc: doesn't work with wlx* interface names

2018-04-14 Thread Vagrant Cascadian
Package: firmware-ath9k-htc
Version: 1.4.0-97-g75b3e59+dfsg-1
Severity: important

I've had problems with my USB wifi adapters on several systems where
it appears to associate and then promptly deassociates when the
interface name is generated by systemd (e.g. wlx*) and using
network-manager.

It gets caught in a loop for a few cycles between associating and
immediately after deassociating:

  aborting authentication by local choice (Reason: 3=DEAUTH_LEAVING)

A workaround is to disable systemd's interface renaming so that the
interfaces are named "wlan0" and such:

  ln -s /dev/null /etc/systemd/network/99-default.link

Works like a charm after rebooting with interfaces named wlan*.


The following thread seems to describe the issue where I found the
workaround:

  
https://unix.stackexchange.com/questions/386925/aborting-authentication-by-local-choice-reason-3-deauth-leaving-when-trying


live well,
  vagrant


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

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

-- no debconf information


signature.asc
Description: PGP signature


Bug#856288: (no subject)

2018-04-14 Thread Morgan Lee
Control: retitle -1 ITA: easygit -- git for mere mortals
Control: owner -1 !
I intend to adopt this package


Bug#895697: libconfig-model-tester-perl FTBFS: Can't locate Module/Build.pm in @INC

2018-04-14 Thread Adrian Bunk
Source: libconfig-model-tester-perl
Version: 3.006-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=libconfig-model-tester-perl=all=3.006-1=1523734360=0

...
   dh_auto_configure -i
perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
"ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Can't locate Module/Build.pm in @INC (you may need to install the Module::Build 
module) (@INC contains: . /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 
/usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at Build.PL 
line 15.
BEGIN failed--compilation aborted at Build.PL line 15.
dh_auto_configure: perl -I. Build.PL --installdirs vendor --config "optimize=-g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
"ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" 
returned exit code 2
make: *** [debian/rules:4: build-indep] Error 2



Bug#895695: elki FTBFS: java.base/jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to java.base/java.net.URLClassLoader

2018-04-14 Thread Adrian Bunk
Source: elki
Version: 0.7.1-6
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/elki.html

...
[INFO] --- exec-maven-plugin:1.6.0:exec (generate-javadoc-parameters) @ elki ---
Exception in thread "main" java.lang.ExceptionInInitializerError
at 
de.lmu.ifi.dbs.elki.application.internal.DocumentParameters.buildParameterIndex(DocumentParameters.java:251)
at 
de.lmu.ifi.dbs.elki.application.internal.DocumentParameters.main(DocumentParameters.java:149)
Caused by: java.lang.ClassCastException: 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to 
java.base/java.net.URLClassLoader
at 
de.lmu.ifi.dbs.elki.utilities.ELKIServiceRegistry.(ELKIServiceRegistry.java:53)
... 2 more
[ERROR] Command execution failed.



Bug#895674: lintian: maybe-not-arch-all-binnmuable emitted for (= ${source:Version})

2018-04-14 Thread Chris Lamb
tags 895674 + moreinfo
thanks

Hi Jeremy,

First, thanks for filing this; so much easier to work with these
various arch/any tags in email in my experience...

> C: gnome-shell source: maybe-not-arch-all-binnmuable gnome-shell ->
>gnome-shell-common

Next, have you noticed that that this is a C-level classification
tag, not even a pedantic warning? :)

Anyway, if you look at:

  
https://salsa.debian.org/lintian/lintian/commit/800b1344880b70995c5a26754d2a891ae0ef7d5d

… in particular:

 At this time, please do not attempt to "fix" the problem.  It
 is not clear what the solution is (if any at all).  Nor is it clear
 that this is something that will be supported.

So, alas, changes may even be incorrect (!). I am unsure, hence
tagging as moreinfo for the time being.

(As an aside, how come you show classification checks? Surely they
are far too noisy/useless..? I also wonder if this should be an
X "experimental" tag instead as that would have been less strange.)


Regards,

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



Bug#862883: Port from libnm-glib/libnm-util to libnm

2018-04-14 Thread Michael Biebl
Am 14.04.2018 um 15:21 schrieb Michael Biebl:

> I tried updating solid-networkstartus to use QT_NO_KEYWORDS and the Q_
> macros, but ran into a problem. The QNtrack headers use the slots
> keyword, so if I set -DQT_NO_KEYWORDS,
> solid-networkstatus/kded/ntracknetworkstate.cpp fails to compile.
> 
> So while I could get the networkmanager backend compile successfully
> with the attached patch, I had to disable QNtrack support.

I found a way to avoid that situation.
As networkmanagerstatus.cpp only uses the D-Bus interface, using
#include 
instead of
#include 
was sufficient and it avoids that gio related headers are included, so
-DQT_NO_KEYWORDS is not necessary.

Lubo, as NM upstream, wdyt about using nm-dbus-interface.h directly
instead of the include-all NetworkManager.h?

v2 of the patch is attached.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
diff -Nru kde-runtime-17.08.3/debian/changelog 
kde-runtime-17.08.3/debian/changelog
--- kde-runtime-17.08.3/debian/changelog2018-01-11 09:22:25.0 
+0100
+++ kde-runtime-17.08.3/debian/changelog2018-04-14 15:02:04.0 
+0200
@@ -1,3 +1,12 @@
+kde-runtime (4:17.08.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update solid-networkstatus to use libnm. (Closes: #862883)
+This requires the use of -DQT_NO_KEYWORDS which is not compatible with
+QNtrack, so disable support for that backend.
+
+ -- Michael Biebl   Sat, 14 Apr 2018 13:02:04 +
+
 kde-runtime (4:17.08.3-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru kde-runtime-17.08.3/debian/control kde-runtime-17.08.3/debian/control
--- kde-runtime-17.08.3/debian/control  2018-01-06 11:49:18.0 +0100
+++ kde-runtime-17.08.3/debian/control  2018-04-14 15:02:04.0 +0200
@@ -24,7 +24,7 @@
libjpeg-dev,
libkactivities-dev,
liblzma-dev,
-   libnm-util-dev (>= 0.7) [linux-any],
+   libnm-dev (>= 1.0.0) [linux-any],
libntrack-qt4-dev [linux-any],
libopenexr-dev,
libphonon-dev (>= 4:4.6.0really4.4.3),
@@ -35,7 +35,6 @@
libwebp-dev,
libx11-dev,
libxcursor-dev,
-   network-manager-dev (>= 0.7.0) [linux-any],
pkg-config,
pkg-kde-tools (>= 0.12),
shared-mime-info,
diff -Nru 
kde-runtime-17.08.3/debian/patches/cmake-add-NetworkManager-module.patch 
kde-runtime-17.08.3/debian/patches/cmake-add-NetworkManager-module.patch
--- kde-runtime-17.08.3/debian/patches/cmake-add-NetworkManager-module.patch
1970-01-01 01:00:00.0 +0100
+++ kde-runtime-17.08.3/debian/patches/cmake-add-NetworkManager-module.patch
2018-04-14 15:02:04.0 +0200
@@ -0,0 +1,56 @@
+From 5711ab8b4b053e5d2f4f0b5831ff2a1d37cdf9fa Mon Sep 17 00:00:00 2001
+From: Lubomir Rintel 
+Date: Tue, 19 Dec 2017 19:45:23 +0100
+Subject: [PATCH] cmake: add NetworkManager module
+
+This one looks for libnm as opposed to the deprecated libnm-glib.
+---
+ cmake/modules/FindNetworkManager.cmake | 40 ++
+ 1 file changed, 40 insertions(+)
+ create mode 100644 cmake/modules/FindNetworkManager.cmake
+
+Index: kde-runtime-17.08.3/cmake/modules/FindNetworkManager.cmake
+===
+--- /dev/null
 kde-runtime-17.08.3/cmake/modules/FindNetworkManager.cmake
+@@ -0,0 +1,40 @@
++# - Try to find NetworkManager
++# Once done this will define
++#
++#  NETWORKMANAGER_FOUND - system has NetworkManager
++#  NETWORKMANAGER_INCLUDE_DIRS - the NetworkManager include directories
++#  NETWORKMANAGER_LIBRARIES - the libraries needed to use NetworkManager
++#  NETWORKMANAGER_CFLAGS - Compiler switches required for using NetworkManager
++#  NETWORKMANAGER_VERSION - version number of NetworkManager
++
++# Copyright (c) 2006, Alexander Neundorf, 
++# Copyright (c) 2007, Will Stephenson, 
++#
++# Redistribution and use is allowed according to the terms of the BSD license.
++# For details see the accompanying COPYING-CMAKE-SCRIPTS file.
++
++
++IF (NETWORKMANAGER_INCLUDE_DIRS)
++   # in cache already
++   SET(NetworkManager_FIND_QUIETLY TRUE)
++ENDIF (NETWORKMANAGER_INCLUDE_DIRS)
++
++IF (NOT WIN32)
++   # use pkg-config to get the directories and then use these values
++   # in the FIND_PATH() and FIND_LIBRARY() calls
++   find_package(PkgConfig)
++   PKG_SEARCH_MODULE( NETWORKMANAGER libnm )
++ENDIF (NOT WIN32)
++
++IF (NETWORKMANAGER_FOUND)
++   IF (NOT NetworkManager_FIND_QUIETLY)
++  MESSAGE(STATUS "Found libnm ${NETWORKMANAGER_VERSION}: 
${NETWORKMANAGER_LIBRARY_DIRS}")
++   ENDIF (NOT NetworkManager_FIND_QUIETLY)
++ELSE (NETWORKMANAGER_FOUND)
++   IF (NetworkManager_FIND_REQUIRED)
++  MESSAGE(FATAL_ERROR "Could NOT find 

Bug#886400: python3-pyqt5.qtwebengine: segfaults on simple test

2018-04-14 Thread Dmitry Shachnev
Control: reassign -1 libqt5gui5 5.10.1+dfsg-5
Control: forwarded -1 https://bugreports.qt.io/browse/QTBUG-67537

On Fri, Jan 05, 2018 at 08:28:25PM -0400, David Bremner wrote:
> Sure, here is a stracktrace from
>
>  /usr/bin/python3 testbrowser_webengine.py url=https://www.debian.org
>
> If you let me know which debug symbol packages to install, I'm happy to
> try again with more symbols.
>
> #0  0x in  ()
> #1  0x71333826 in QOpenGLContext::makeCurrent(QSurface*) () at 
> /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
> #2  0x7fffe733f6c7 in  () at 
> /usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5
> #3  0x7fffe734199e in QQuickWidget::resizeEvent(QResizeEvent*) ()
> at /usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5
> ...

I just realized that this may be a variant of QTBUG-67537, which I had fixed
in upstream recently. I will backport a patch for it to our Qt 5.10 packaging.

--
Dmitry Shachnev


signature.asc
Description: PGP signature


Bug#891682: [Pkg-pascal-devel] Bug#891682: castle-game-engine: FTBFS on arm64: assorted test suite errors and failures

2018-04-14 Thread Punit Agrawal
block 891682 by 895693

On Sat, Apr 14, 2018 at 7:29 PM, Paul Gevers  wrote:
> Hi Punit,
>
> Thanks for your work.
>
> On 14-04-18 19:25, Punit Agrawal wrote:
>> I'll file a bug against the debian fpc package. What would be the best
>> way to bring this to upstream's attention?
>
> Upstream bug tracker lives here:
> https://bugs.freepascal.org/my_view_page.php

Thanks for the pointer.

Bugs filed both in debian[0] and upstream[0].

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895693
[1] https://bugs.freepascal.org/view.php?id=33607



Bug#895694: ITA: storebackup -- fancy compressing managing checksumming deduplicating hard-linking cp -ua

2018-04-14 Thread Oliver Meißner
Package: wnpp
Severity: normal

I intend to adopt the storebackup package.

I still created a package at mentors.debian.net, including the newest
upstream version and closing some bugs. Maybe there's someone out there
who wants to review and sponsor it. Oh, btw... I could need a mentor in
order to become a DM (or DD) someday :)

The source package is downloadable at
https://mentors.debian.net/debian/pool/main/s/storebackup/storebackup_3.5-2.dsc

The package description is:
 Copies directory hierarchies recursively into another location,
 by date (e.g.  /home/ => /var/bkup/2002.12.13_04.27.56/).
 Permissions are preserved, so users with access to the backup
 directory can recover their files themselves.
 .
 File comparisons are done with MD5 checksums, so no changes go
 unnoticed.
 .
 Hard-links unchanged backuped files to old versions and
 identical files within the backuped tree.
 .
 Compresses large files (that don't match exclusion patterns).



Bug#895428: Port from libnm-glib/libnm-util to libnm

2018-04-14 Thread Mike Gabriel

Hi Michael,

On  Sa 14 Apr 2018 01:03:58 CEST, Michael Biebl wrote:


Control: severity -1 serious

Hi,

I intend to upload a new version of network-manager soonish which will
drop libnm-glib/libnm-util. I'm thus bumping this issue to RC in
preparation for that.

Regards,
Michael


ACK. Will take a look.

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



pgplE5s301F_z.pgp
Description: Digitale PGP-Signatur


Bug#895444: [Pkg-ayatana-devel] Bug#895444: Uses deprecated NetworkManager.pc

2018-04-14 Thread Mike Gabriel

Hi,

On  Sa 14 Apr 2018 01:04:15 CEST, Michael Biebl wrote:


Control: severity -1 serious

Hi,

I intend to upload a new version of network-manager soonish which will
drop libnm-glib/libnm-util. I'm thus bumping this issue to RC in
preparation for that.

Regards,
Michael


Ouch (libqtdbusmock). I presume that I have to patch this for Debian  
instead of waiting for upstream to fix this.


Noted. Let's see what I can find...
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



pgpB4wnLLeOHP.pgp
Description: Digitale PGP-Signatur


Bug#895693: arm64: Incorrect record member value when returned from a function

2018-04-14 Thread Paul Gevers
Hi Punit,

On 14-04-18 20:30, Punit Agrawal wrote:
> While investigating build failure reported in #891682 I've stumbled
> upon what seems like a free pascal compiler issue on arm64.

Please let us know when you filed the bug upstream and set the forwarded
field of this bug appropriately. Such that we can port back the solution
when upstream fixes the issue.

Mind you, upstream hasn't released arm64 support yet (that is a Debian
thing), so be gentle with them.

Paul



signature.asc
Description: OpenPGP digital signature


Bug#895693:

2018-04-14 Thread Punit Agrawal
forwarded 895693 https://bugs.freepascal.org/view.php?id=33607

thanks



Bug#895604: [pkg-php-pear] Bug#895604: php-symfony-polyfill: FTBFS and Debci failure with phpunit 7.0.3-1

2018-04-14 Thread David Prévot
Le 13/04/2018 à 08:45, Paul Gevers a écrit :

> Interestingly, the explicit testing of phpunit 7.0.3-1 with all code
> from testing on 1 April 2018¹ was successful.

Don’t believe the trigger entry on such a date. The test log shows that
“PHPUnit 6.5.5” was used.

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-symfony-polyfill/98094/log.gz

Regards

David



signature.asc
Description: OpenPGP digital signature


Bug#891682: [Pkg-pascal-devel] Bug#891682: castle-game-engine: FTBFS on arm64: assorted test suite errors and failures

2018-04-14 Thread Paul Gevers
Hi Punit,

Thanks for your work.

On 14-04-18 19:25, Punit Agrawal wrote:
> I'll file a bug against the debian fpc package. What would be the best
> way to bring this to upstream's attention?

Upstream bug tracker lives here:
https://bugs.freepascal.org/my_view_page.php

Paul



signature.asc
Description: OpenPGP digital signature


Bug#895693: arm64: Incorrect record member value when returned from a function

2018-04-14 Thread Punit Agrawal
Source: fpc
Version: 3.0.4+dfsg-16
Severity: normal

Dear Maintainer,

While investigating build failure reported in #891682 I've stumbled
upon what seems like a free pascal compiler issue on arm64.

The value of a member of a record returned by a function varies
depending on usage.

The observed value of

   S.Width where S := R.ScaleAround0(2)

differs from the value of

   R.ScaleAround0(2).Width

The values differ on arm64 but agree on x86-64.

The attached reproducer gives the following output on arm64 -

arm64:~/src/fpc-test$ ./test
S.Width=0 R.ScaleAround0(2).Width=214748364800

while on x86-64

x86-64$ ./test
S.Width=0 R.ScaleAround0(2).Width=0

The reproducer is derived from a failing test in Castle Game Engine.

Thanks,
Punit
program test;

{$mode objfpc}{$H+}
{$modeSwitch advancedRecords}

type
   TRectangle = record
   public
   Left, Bottom: Integer;
   Width, Height: Cardinal;

function ScaleAround0(const Factor: Single): TRectangle;
end;

function TRectangle.ScaleAround0(const Factor: Single): TRectangle;
begin
   if Width <= 0 then
   begin
  Result.Width  := Width;
  Result.Left   := Left;
   end else
  Writeln('This should never happen');

   Result.Height := Height;
   Result.Bottom := Bottom;
end;

function Rectangle(const Left, Bottom: Integer;
   const Width, Height: Cardinal): TRectangle;
begin
   Rectangle.Left := Left;
   Rectangle.Bottom := Bottom;
   Rectangle.Width := Width;
   Rectangle.Height := Height;
end;

var
   R, S :  TRectangle;
begin
   R := Rectangle(10, 20, 0, 50);
   S := R.ScaleAround0(2);

   Writeln('S.Width=', S.Width, ' R.ScaleAround0(2).Width=', 
R.ScaleAround0(2).Width);   
end.


Bug#895686: installation-birthday: Incorrectly identifies the birthdate of my system

2018-04-14 Thread Chris Lamb
Hi Stephen.

Thanks for the report. Please keep <895...@bugs.debian.org> in any
followups and replies :)

> D: Checking mtime of /root
> D: Using mtime from /root
> D: Today's date: 2018-04-14
> I: Installation date: 2017-08-27
> D: Dates do not match
> 
> The system is *definitely* older that that.  My oldest files in /var/log are
> from 2007-12-17 ('news/', 'uucp.log', and 'boot.2.gz').  That seems like the
> right timeframe for when I may have done the install.

Getcha. Can you provide the output of:

 $ ls -l --sort=time /var/log /etc
 

Best wishes,

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



Bug#895692: ejabberd: Does not use IPv6 for PostgreSQL and LDAP

2018-04-14 Thread Dominik George
Source: ejabberd
Version: 18.01-2
Severity: important
Tags: ipv6

ejabberd 18.01 fails hard when one of the SQL or LDAP hosts does not
have an A record and is IPv6 only. Providing an IPv6 address directly in
the configuration also fails. It looks like ejabberd does simply not
support AF_INET6 for its client sockets.

With IPv4 addresses running out on our infrastructure, we wanted to drop
IPv4 from all hosts not used directly from outside, and ejabberd turned
out to be a showstopper there because it cannot use our databases
anymore that way.

-- 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=de_DE.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#889968: RFS: inotify-tools/3.14-4 -- summary of situation

2018-04-14 Thread Sean Whitton
Hello Dmitry, Gianfranco,

I did some research and testing into this bug...

On Sat, Apr 14 2018, kact...@gnu.org wrote:

> Hello. I am a bit lost about state of this RFS, but it seems I did
> stupid thing with format=1.0; complicating sponsoring.
>
> Let me settle things, provide sane package with format=3.0 (quilt), with
> pristine tar. I will ping once I am ready. Sorry for noise.

That is not the problem.  The orig.tar is already in the archive so
no-one should need pristine-tar.  I can obtain something that works like
this:

% git clone salsa.debian.org:iu-guest/inotify-tools
% cd inotify-tools
% origtargz
% sbuild# or similar

Gianfranco, please try that :)

Now as to the FTBFS I was seeing, I investigated further.
dh_auto_configure works fine, but dpkg-buildpackage does not:

configure:3383: ./conftest
==28639==ASan runtime does not come first in initial library list; you 
should either link runtime to your application or manually preload it with 
LD_PRELOAD.
configure:3387: $? = 1

I found a bug report[1] which says that this error is bogus when
triggered by cowbuilder or fakeroot.  dpkg-buildpackage doesn't use
fakeroot when it invokes dh_auto_configure, though ...

I would suggest just disabling address sanitising for now.  My sbuild
setup is v. similar to the buildds, so I suspect we are going to see an
FTBFS if this is left turned on.

[1]  https://github.com/google/sanitizers/issues/786

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#895691: RFS: budgie-indicator-applet/0.6-1 RC

2018-04-14 Thread foss.freedom
Package: sponsorship-requests
Severity: important

  Dear mentors,

  I am looking for a sponsor for my package "budgie-indicator-applet"

 * Package name: budgie-indicator-applet
   Version : 0.6-1
  Upstream Author : David Mohammed 
 * URL : https://github.com/UbuntuBudgie/budgie-indicator-applet
 * License : GPL-2+
   Section : misc

  It builds those binary packages:

budgie-indicator-applet - Application Indicator for the budgie-desktop

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

  https://mentors.debian.net/package/budgie-indicator-applet


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

dget -x 
https://mentors.debian.net/debian/pool/main/b/budgie-indicator-applet/budgie-indicator-applet_0.6-1.dsc

 Notes:
  I am the developer and package maintainer for this.

  check-all-the-things run and corrections made (see changelog)
lintian -i -I --pedantic run: one Information for missing test-suite.
I don't feel this is necessary for this package

I've tagged this as RC important due to this bug report
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895039) where a
package is about to be removed and this upload prevents
budgie-indicator-applet from being deleted since the associated
build-dependency has now been updated.

If possible please can I be allowed to continue maintaining this in
the future by DM upload privileges through auth via dak (dcut dm --uid
"jane doe" --allow budgie-indicator-applet) ? N.B. my debian
maintainer key is registered in the maintainership keyring

  Changes since the last upload:

[David Mohammed]
  * New upstream release
- Support budgie vertical panels
- Ensure the applet is styled correctly to blend into
  the panel
  Force resizing of GIcons to appindicator spec of 22px (LP: #1641457)
- Removing self theming since this is now handled by
  budgie-desktop v10.4 (LP: #1711928)
- fix startup warning
- add applet blacklist
  * Packaging changes
- debian/copyright - year change and repo name change
- debian/copyright - Ensure debian/* files are GPL-2+ licensed
- debian/copyright: http --> https
- debian/{control/compat} debhelper v11
- debian/control Standards-Version bump (no changes required)
- debian/control: build-dependency restriction of >= 10.4 for
  budgie-core-dev added due to theming change
- debian/control: remove deprecated build dependencies
- update metadata to resolve check-all-the-things warnings and errors

  [Mike Gabriel ]
  * Add the following changes:
- Make the package build against Ubuntu Indicators and Ayatana
  Indicators alike (Closes: #893707)
- Re-enable (and fix)
  Indicators NG file support (loading indicators from service
  files.
  * debian/control:
- Add B-Ds: libayatana-indicator3-dev, libayatana-ido3-0.4-dev.
  to support building against Ayatana Indicators on Debian. Leaving
  Ubuntu Indicators B-Ds in the control file, too, so that on Ubuntu
  we can build (see debian/rules) against Ubuntu Indicators.
  * debian/rules:
- Select the Indicator implementation to build against based on the
  distribution the package is built for (Debian vs. Ubuntu).



  Regards,
   David Mohammed



Bug#895186: asciidoctor: url-related issues are fixed upstream

2018-04-14 Thread Joseph Herlant
Control: tag -1 + fixed-upstream

Hi,

The issue has been fixed upstream and will be released as part of
1.5.7 whose timeline is being discussed in
https://github.com/asciidoctor/asciidoctor/issues/2663

Thanks,
Joseph



Bug#380470: 11 years on, this would still be nice

2018-04-14 Thread Bill Allombert
On Sat, Apr 14, 2018 at 04:45:13PM +0100, Conrad Hughes wrote:
> I'm yet another of those users who read the label on the tin and assumed
> "lossless transformation of JPEG files" was just that.  Having a warning
> about imperfect transformations and directing to the hidden depths of
> the manpage where these details are explained would be really helpful.

It is certainly lossless. 

In any case, you are probably using the package libjpeg-turbo-progs
and not libjpeg-progs so you should probably report it to
libjpeg-turbo-progs

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



Bug#891682: [Pkg-pascal-devel] Bug#891682: castle-game-engine: FTBFS on arm64: assorted test suite errors and failures

2018-04-14 Thread Punit Agrawal
On Sat, Apr 14, 2018 at 1:56 PM, Michalis Kamburelis
 wrote:
>  2018-04-14 12:42 GMT+02:00 Punit Agrawal :
>> At this point, I suspect it's a compiler issue. I've created a
>> reproducer (attached) that highlights the problem and behaves
>> differently on arm64 and x86.
>>
>> Note: I am not at all familiar with Pascal. Input from somebody more
>> familiar with the language ecosystem will be greatly appreciated.
>>
>
> Great job!
>
> Note that in your testcase, the minimized "TRectangle.ScaleAround0"
> does not set Result.Width, Result.Left in some cases. And, since this
> is a record, the uninitialized fields are undefined (may contain
> memory garbage).
>
> It should not matter for the result (from what I see, the
> TRectangle.Width is always guaranteed to be 0 when calling this). But
> maybe writing something like
>
> """
>if Width <= 0 then
>begin
>   Result.Width  := Width;
>   Result.Left   := Left;
>end else
>   Writeln('This should never happen');
> """
>
> would make this clearer?

I updated the reproducer as you suggested. The behaviour is unchanged as below.

>
> The testcase definitely makes sense to me, and if you get different
> results on different CPUs -- then indeed we have nicely reproducible
> FPC bug.

The output on arm64

arm64:~/src/fpc-test$ ./test
S.Width=0 R.ScaleAround0(2).Width=214748364800

and on x86-64

x86-64$ ./test
S.Width=0 R.ScaleAround0(2).Width=0

I'll file a bug against the debian fpc package. What would be the best
way to bring this to upstream's attention?

>
> (P.S. I'm the castle-game-engine upstream author.)

Cool! Thanks a lot for looking over the findings. Very much appreciated.


test.pas
Description: Binary data


Bug#895690: libpetsc-real3.8-dev: uninstallable with current openmpi version in sid

2018-04-14 Thread Giacomo Mulas
Package: libpetsc-real3.8-dev
Version: 3.8.4+dfsg1-2
Severity: important

Dear Maintainer,

with the release in sid of the new major version of openmpi,
libpetsc-*3.8-dev packages became uninstallable, since they depend on the
2.1 version of libopenmpi-dev. It might be just a matter of recompiling the
packages and modifying the versioned dependence. Let me know if I can help
with it.

Best regards
Giacomo Mulas

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

Kernel: Linux 4.15.11-jak (SMP w/4 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to it_IT.UTF-8), LANGUAGE=it_IT,en_EN (charmap=UTF-8) (ignored: LC_ALL set 
to it_IT.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpetsc-real3.8-dev depends on:
ii  gfortran  4:7.3.0-3
ii  libfftw3-dev  3.3.7-1
ii  libfftw3-mpi-dev  3.3.7-1
ii  libhdf5-mpi-dev   1.10.0-patch1+docs-4
ii  libhypre-dev  2.14.0-2
ii  libmumps-dev  5.1.2-4
ii  libopenmpi-dev2.1.1-8
ii  libpetsc-real3.8  3.8.4+dfsg1-2
ii  libptscotch-dev   6.0.4.dfsg1-8
ii  libscalapack-mpi-dev  2.0.2-4
ii  libspooles-dev2.2-12+b1
ii  libssl-dev1.1.0h-2
ii  libsuitesparse-dev1:5.2.0+dfsg-1
ii  libsuperlu-dev5.2.1+dfsg1-3
ii  libsuperlu-dist-dev   5.3.0+dfsg1-1
ii  python2.7.14-4

Versions of packages libpetsc-real3.8-dev recommends:
ii  ksh   93u+20120801-3.1
ii  mksh  56c-1
ii  zsh   5.5-1

Versions of packages libpetsc-real3.8-dev suggests:
pn  libluminate-dev   
pn  libpetsc-real3.8-dbg  
ii  petsc-dev 3.8.4+dfsg1-2
ii  petsc3.8-doc  3.8.4+dfsg1-2

-- no debconf information



Bug#895187: asciidoctor: url-related issues are fixed upstream

2018-04-14 Thread Joseph Herlant
Control: tag -1 + fixed-upstream

Hi,

The issue has been fixed upstream and will be released as part of
1.5.7 whose timeline is being discussed in
https://github.com/asciidoctor/asciidoctor/issues/2663

Thanks,
Joseph



Bug#895682: cacti: 1.1.37+ds1-1 has failing autopkgtests

2018-04-14 Thread Paul Gevers
Control: forwarded -1 https://github.com/Cacti/cacti/issues/1539

Thanks for reporting.

On 14-04-18 16:37, Jeremy Bicha wrote:
> cacti's autopkgtests starting failing with the 1.1.37+ds1-1 upload.
> This is a problem for Ubuntu which uses autopkgtest regressions to
> block packages from being promoted to the regular archive.
> 
> The test log has this line:
> 
> ERROR PHP NOTICE: Undefined index: type_id in file:
> /usr/share/cacti/site/data_input.php  on line: 469

Already reported and fixed upstream.

Paul



signature.asc
Description: OpenPGP digital signature


Bug#889968: RFS: inotify-tools/3.14-4

2018-04-14 Thread Sean Whitton
Hello,

On Sat, Apr 14 2018, kact...@gnu.org wrote:

> Hello. I am a bit lost about state of this RFS, but it seems I did
> stupid thing with format=1.0; complicating sponsoring.
>
> Let me settle things, provide sane package with format=3.0 (quilt),
> with pristine tar. I will ping once I am ready. Sorry for noise.

The source package format is not the issue, afaict.  pristine-tar can
work with source format 1.0

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#890083: [PATCH] dl10n-check script: dpkg: warning: --compare-versions used with obsolete relation operator '>'

2018-04-14 Thread Christian PERRIER
Quoting Laura Arjona Reina (larj...@debian.org):
> Please ignore the former patch.
> 
> The correct patch is this one:

As we say in French : MDR:-)

There hasn't been as much activity on i18n infrastructure than today
during last months (if not years) and both of us report the same bug
with the same patch...:-)

I "git pulled" again





signature.asc
Description: PGP signature


Bug#895689: dl10n-check uses an obsolete version comparison ooperator with "dpkg --compare-versions"

2018-04-14 Thread Christian Perrier
Package: dl10n
Severity: normal
Tags: patch

dl10n-check spits out many warning messages when used (for instance on
i18n.debian.org) :

dpkg: warning: --compare-versions used with obsolete relation operator
'>'

This is indeed quite easy to fix with the attached patch.


-- System Information:
Debian Release: 9.4
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-6-686-pae (SMP w/1 CPU core)
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/bash
Init: systemd (via /run/systemd/system)

Versions of packages dl10n depends on:
ii  gettext   0.19.8.1-2
ii  liblocale-gettext-perl1.07-3+b1
ii  libmailtools-perl 2.18-1
ii  libtimedate-perl  2.3000-2
ii  libwww-perl   6.15-1
ii  perl  5.24.1-3+deb9u2
ii  perl-modules-5.24 [perl-modules]  5.24.1-3+deb9u2

dl10n recommends no packages.

dl10n suggests no packages.
diff --git a/dl10n-check b/dl10n-check
index 4bad7a1..7b6b0cf 100755
--- a/dl10n-check
+++ b/dl10n-check
@@ -281,7 +281,7 @@ PKG: while ($dsc = shift @pkg_list) {
 $data->maintainer($pkg, $maint);
 my $newer = ($data->version($pkg) ne $ver);
 if ($newer) {
-$newer = system ("dpkg","--compare-versions", 
$data->version($pkg), "\>", $ver);
+$newer = system ("dpkg","--compare-versions", 
$data->version($pkg), "gt", $ver);
 }
 if ((!$force) && $newer==0 && $data->version($pkg) ne ""
 && !( $force_material &&


Bug#895185: transition: dde-qt-dbus-factory

2018-04-14 Thread Emilio Pozuelo Monfort
Control: tags -1 confirmed

On 08/04/18 10:38, Boyuan Yang wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-CC: pkg-deepin-de...@lists.alioth.debian.org
> 
> Dear Release Team,
> 
> For package dde-qt-dbus-factory, upstream has released a new version
> with bumped SONAME (libdframeworkdbus1 -> libdframeworkdbus2). Thus I
> am requesting a transition approval here before the new version gets
> uploaded into Unstable.
> 
> All the reverse dependencies are under Debian Deepin Packaging Team
> and will be coordinated inside the team. To be more concrete, affected
> packages are:
> 
> % LANG=C apt rdepends libdframeworkdbus1
> libdframeworkdbus1
> Reverse Depends:
>   Depends: deepin-menu
>   Depends: libdframeworkdbus1-dbgsym (= 0.4.2-2)
>   Depends: libdtkwidget2
>   Depends: libdframeworkdbus-dev (= 0.4.2-2)
> 
> Transition tracker entry:
> 
> https://release.debian.org/transitions/html/auto-dde-qt-dbus-factory.html
> 
> I will handle all reverse dependencies to complete the transition.

I wanted to wait for the Qt transition, which has just finished. So go ahead.

Emilio



Bug#894891: [Pkg-phototools-devel] Bug#894891: Bug#894891: Bug#894891: pngquant: please, package new upstream version

2018-04-14 Thread Herbert Fortes
Em 11-04-2018 14:46, Herbert Fortes escreveu:
> Em 06-04-2018 09:40, Herbert Fortes escreveu:
>> Em 06-04-2018 07:19, Rogério Brito escreveu:
>>> Hi, Herbert.
>>>
>>> On Thu, Apr 5, 2018 at 11:52 AM, Herbert Fortes  wrote:
 Em 05-04-2018 06:57, Rogério Brito escreveu:
> The upstream of pngquant has released quite a few releases since 2.5.0
> that's currently in Debian. The current version is 2.11.7.
>
> Can we, please, have something newer than the current version?

 It is stopped because of a dependency:

 pngquant (2.8.2-1) UNRELEASED; urgency=medium

   TODO: * Needs packaging of
 https://github.com/ImageOptim/libimagequant
   (but no new packages for Stretch ...)
 * check whether CVE-2016-5735 is fixed in latest upstream
>>> (...)
>>>
>>> Ah, I see... I didn't know that newer versions of the package required
>>> a new library...
>>
>>
>> I think the project was splitted.
>>
>> version 2.8
>> ---
>>  - libimagequant is a separate project
>>
>> The maintainer is very active. And I think the packages - pngquant
>> and libimagequant - should walk together.
>>
>>>
>>> BTW, taking a look at the repository for the library, it has bindings
>>> for a lot of languages and, perhaps, they should be built as needed,
>>> since, otherwise, they may be bloating the archive and never be used
>>> (depending if clients in the archive use this library)...
>>
>> I saw that too. I do not know what to do exactly (right now).
>>
>>>
 I can send an ITP and try to do the Debian package if that helps.
>>>
>>> That would be awesome, if you could do that, because the lack of SSE2
>>> optimization (if I understood things correctly with the current
>>> binaries) is a pain with amd64 systems (especially on my Core 2 Duo
>>> notebook that is already being loaded with some image processing tasks
>>> and trying to help the kernel team with support for the recent
>>> oversized armel kernels).
>>>
>>
>> As said, the maintainer is very active. Let's wait a few days.
>>
> 
> I started the packaging - libimagequant0(shared) and libimagequant-dev.
> No *-doc package yet. I think it can be an overkill.
> 
> And I created a repository[0].
> 
> [0] - https://salsa.debian.org/debian-phototools-team/libimagequant
> 
> About the build:
> 
>  - debian/copyright must be checked.
>  - there is a lintian that I do not understand why:
> 
>W: file-name-contains-wildcard-character
>N:
>N:   The file name contains shell wildcard characters.
>N:   
>N:   These are most likely unexpanded wildcard characters from (for
>N:   example) debian/*.install files, or it may have been installed by
>N:   accident.
>N:   
>N:   Severity: normal, Certainty: possible
>N:   
>N:   Check: files, Type: binary, udeb
>N:
> 
>   It is true. The '*' is unexpanded. Here it should be 'x86_64-linux-gnu'
>   as it is in 'debian/tmp'.
> 
> 
> If someone wants to be a 'Uploaders', please do it.
> 

I just push to salsa a new debian directory.

The configure and Makefile files were made by hand. That's why the 
lintian above, I guess. So I put some extra lines in debian/rules file.

I also finished debian/copyrigh file and builded the debian/*.symbols
file.



Bug#895646: gnupg: do not allow short key IDS in gpg.conf

2018-04-14 Thread Georges Khaznadar
Some more information:

Thanks to Ian Jackson, I saw that it is not safe to ignore a ligne with
"default-key 12345678" (or any other short ID) in gpg's configuration
file, because it can result in using anoter key chosen by gpg's logic
inside one's keyring.

So, the fix cannot be given by
https://salsa.debian.org/debian/gnupg2/merge_requests/3



signature.asc
Description: PGP signature


Bug#895688: RFP: libtepl -- a text editor library

2018-04-14 Thread John Scott
Package: wnpp
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: libtepl
  Version : 4.0.0
  Upstream Author : Sébastien Wilmet 
* URL : https://wiki.gnome.org/Projects/Tepl
* License : LGPL
  Programming Lang: C
  Description : a text editor library

Tepl is a library that eases the development of GtkSourceView-based
text editors and IDEs. Tepl is the acronym for “Text editor product line”.
It serves as an incubator for GtkSourceView.

The upstream author maintains this library with the intent of making Gedit
source code more reusable for use in text editors using GtkSourceView.

I believe that this package is needed in Debian because it is a dependency
of recent versions of GNOME LaTeX, formerly called LaTeXila, which is
currently packaged under the latter name in Stretch and Buster. This
library is needed to package a new upstream version.

Tepl 3.99.1+ requires GtkSourceView 4, which is only in experimental at the
moment.

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEJwCMxdBfG24Y2trvfWFEpid5MHIFAlrSK1QSHGpzY290dEBw
b3N0ZW8ubmV0AAoJEH1hRKYneTBylhQH/iVC5+BlGNDfVBIcOrX0dbQBQTwdgKJx
9ZwR8v3RR3pRx6wX42Oo13qCym4eB3JG8bHL5tpSeS6G5dhjxrPH9JOMUChyM4ks
VFEBB10fN+J5owZXN3lzgIZYN9F/8RUkX5/Z3Rruct/hnbLMLL5TAaSXKLk1gxSb
+l+NOiiANyXDvGXdU6i33wd1c5s559NMAggj6P3AN+CI/cl3OyqfJpJ2CeRHX6Tr
dNBQf5sSc9SEk3Jsr2+OvTmctGJJO8l1KgJj4qi+YcyYCvPOlm8TzCrkFBZUnG4N
9FVc66x3ZA1bVqIcZth8SdLIUOExJ6MzxWQT4KlcKOGKPBSQ9regQwI=
=snG2
-END PGP SIGNATURE-


Bug#895685: nvidia-kernel-dkms: please upgrade to 396.18 for linux 4.16 compatibility

2018-04-14 Thread Luca Boccassi
Control: forcemerge 895429 -1

On Sun, 2018-04-15 at 00:46 +0900, Norbert Preining wrote:
> Just FYI
> 
> > linux 4.16 and nvidia << 396.18 don' work together due to changes
> > in the
> > GPL exports of symbols.
> > 
> > Please update the driver to the current version that supports linux
> > 4.16.
> 
> I tried the patch in your svn with linux 4.16.2, but it did hard-
> freeze
> my system, Sysrq-r was necessary. So I don't think that this is the
> solution.
> 
> Norbert
> 
> --
> PREINING Norbert   http://www.preining.in
> fo
> Accelia Inc. +JAIST +TeX Live +Debian
> Developer
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C
> DC13

I have tested the patch on my desktop and it worked fine. More
importantly, it's exactly the same fix applied by Nvidia to 396.18. Are
you sure the nvidia kernel module is causing the freeze?

Note that there is quite a lot of work to do before 396+ can be
uploaded, as i386 and armhf are being dropped so changes have to be
made to distribute the 32bit libraries, so it won't happen anytime
soon. But the kernel module patch should work.

-- 
Kind regards,
Luca Boccassi

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


Bug#380470: 11 years on, this would still be nice

2018-04-14 Thread Conrad Hughes
I'm yet another of those users who read the label on the tin and assumed
"lossless transformation of JPEG files" was just that.  Having a warning
about imperfect transformations and directing to the hidden depths of
the manpage where these details are explained would be really helpful.

Conrad



Bug#895687: cheese: No device found

2018-04-14 Thread Victor Porton
Package: cheese
Version: 3.28.0-1
Severity: important

Dear Maintainer,

Cheese does not work at all:
https://bugzilla.gnome.org/show_bug.cgi?id=795221


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

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

Versions of packages cheese depends on:
ii  cheese-common  3.28.0-1
ii  gnome-video-effects0.4.3-2
ii  libc6  2.27-2
ii  libcanberra-gtk3-0 0.30-6
ii  libcheese-gtk253.28.0-1
ii  libcheese8 3.28.0-1
ii  libclutter-1.0-0   1.26.2+dfsg-4
ii  libclutter-gtk-1.0-0   1.8.4-3
ii  libgdk-pixbuf2.0-0 2.36.11-2
ii  libglib2.0-0   2.56.0-4
ii  libgnome-desktop-3-17  3.28.0-1
ii  libgstreamer1.0-0  1.14.0-1
ii  libgtk-3-0 3.22.29-2

Versions of packages cheese recommends:
ii  gvfs  1.36.0-1
ii  yelp  3.26.0-2

Versions of packages cheese suggests:
pn  gnome-video-effects-frei0r  

-- no debconf information



Bug#887107: https://i18n.debian.org/material/data/unstable.gz not updated since 2017-11-23

2018-04-14 Thread Laura Arjona Reina
Hello

I've had a look at today's log and there is only the warning that is
reported in bug  #890083 (dpkg --compare-versions using obsolete operator).

Guillem Jover ACK'ed my patch for #890083 and thus I have applied it in
the repo.

Christian, do you mind to update again the repo in tye?

Let's hope tomorrow we have our unstable.gz updated :)
Cheers
-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona



Bug#895685: nvidia-kernel-dkms: please upgrade to 396.18 for linux 4.16 compatibility

2018-04-14 Thread Norbert Preining
Just FYI

> linux 4.16 and nvidia << 396.18 don' work together due to changes in the
> GPL exports of symbols.
> 
> Please update the driver to the current version that supports linux 4.16.

I tried the patch in your svn with linux 4.16.2, but it did hard-freeze
my system, Sysrq-r was necessary. So I don't think that this is the
solution.

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#895670: kaddressbook: Can't edit postal addresses anymore

2018-04-14 Thread Klaumi Klingsporn
Am / On Sat, 14 Apr 2018 17:31:45 +0200
schrieb / wrote Sandro Knauß :

> It sounds like you don't have kdepim-addons installed.
> Please try again with kdepim-addons installed.

Thanks!
Installing kdepim-addons fixed the problem.

There should be a dependency in the kaddressbook-package to
kdepim-addons, I think?

Klaumi


---
Klaus-Michael Klingsporn 
phone: +49-30-9445363
mail: klaumi...@gmx.de
web: www.klaumikli.de


pgpHlLkxvxJN8.pgp
Description: Digitale Signatur von OpenPGP


Bug#826695:

2018-04-14 Thread Kirill Trofimov
Hello, can you try:

1. check status of chronyd
2. run ‘chronyc online’
3. run ‘chronyc burst 5/10’
4. show output from ‘chronyc sources -v’ ?

I hope that help you.


Bug#895686: installation-birthday: Incorrectly identifies the birthdate of my system

2018-04-14 Thread Boyd Stephen Smith Jr.
Package: installation-birthday
Version: 8
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

I have a system that was originally installed as Etch/amd64 via debootstrap
from a running Gentoo system.  Since then, I've used LVM to migrate the
filesystems to new drives, and done some filesystem convertions (e.g.
reiserfs/ext3 to btrfs), and enabled multiarch, among other things.

Here's what installation-birthday thinks about my system:
% installation-birthday --verbosity 2
D: Determining block device for /
D: Checking mtime of /var/log/installer
D: Failed to get mtime of /var/log/installer
D: Checking mtime of /var/log/bootstrap.log
D: Failed to get mtime of /var/log/bootstrap.log
D: Checking mtime of /lost+found
D: Failed to get mtime of /lost+found
D: Checking mtime of /root
D: Using mtime from /root
D: Today's date: 2018-04-14
I: Installation date: 2017-08-27
D: Dates do not match

The system is *definitely* older that that.  My oldest files in /var/log are
from 2007-12-17 ('news/', 'uucp.log', and 'boot.2.gz').  That seems like the
right timeframe for when I may have done the install.

It's been a while, but I know it was no earlier that the release date of Etch,
as I was awailing and official release with amd64 support.  I believe it was no
later than 2008-04-01, because I was running Debian on my desktop before I
installed OpenSUSE on my laptop to "dogfood" during a contract where I was
porting software to SLES and that contract started 2008-03.

installation-birthday gives the same output when run as root via sudo.

- -- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (900, 'stable-updates'), (900, 'stable'), (850, 
'proposed-updates'), (700, 'testing'), (500, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages installation-birthday depends on:
ii  e2fsprogs  1.43.4-2
ii  python33.5.3-1

installation-birthday recommends no packages.

installation-birthday suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHQEARECADQWIQTFhn3a8g2plxzZYyjnmmovsbVAWQUCWtIgShYcYnNzQGlndWFu
YXN1aWNpZGUubmV0AAoJEOeaai+xtUBZh9UAnAtLmcF7EKrmQiq6KY5+PzhFtd0N
AJ9jH3g7k4slmfk3gHicHK4OLDZ/LA==
=EF2M
-END PGP SIGNATURE-



  1   2   >