Bug#860486: Systemd service unit fails with permission error in X.Org Server

2017-08-21 Thread Paul Menzel
Control: reopen -1


Am Montag, den 07.08.2017, 09:25 +0200 schrieb Paul Menzel:

> Am Montag, den 17.04.2017, 19:48 +0200 schrieb Paul Menzel:
> > Package: kodi
> > Version: 2:17.1+dfsg1-2
> > Severity: normal
> 
> […]
> 
> > After having added the user *kodi* with `sudo adduser kodi`, then
> > trying to start Kodi using the systemd service unit [1] with `sudo
> > systemctl start kodi.service`, Kodi doesn’t start, as the X.Org Server
> > quits with a fatal error.
> > 
> > ```
> > (EE) xf86OpenConsole: Cannot open virtual console 7 (Permission denied)
> > ```
> > 
> > The page *HOW-TO:Autostart Kodi for Linux* in the Kodi Wiki [2]
> > suggests to run `sudo dpkg-reconfigure x11-common`, but that doesn’t do
> > anything on the system here.
> > 
> > Is something else needed, to get the systemd service unit working?
> 
> Since package version 2:17.3+dfsg1-2 the upstream service unit is used.
> That works. (Though sometimes it still doesn’t start, but that’s
> probably a different issue due to some race condition.)

No idea, why, but I am getting the error again, and Kodi does not start
with the same error. Maybe some race condition?


Thanks,

Paul


> > [1] 
> > https://sources.debian.net/src/kodi/2:17.1%2Bdfsg1-2/debian/kodi.service/
> > [2] 
> > http://kodi.wiki/view/HOW-TO:Autostart_Kodi_for_Linux#Add_a_new_systemd_script

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


Bug#470417: new upstream version out with ipv6 support

2017-08-21 Thread Gabriel Filion
Hello,

Just wanted to send a ping to this bug report.

apparently 0.10.0 has finally been released with IPv6 support just a
couple of days ago:

https://github.com/fail2ban/fail2ban/releases/tag/0.10.0

maybe 0.10.0 should go to unstable?



signature.asc
Description: OpenPGP digital signature


Bug#871540: e2fsck: out-of-bounds read in get_qid()

2017-08-21 Thread Theodore Ts'o
tags 871540 +pending
thanks

Thanks for reporting this bug.  The following fix will be in the next
release of e2fsprogs.

- Ted

commit 75153dae6e0a9807e2c57fcc9fb3bb23dc7c19cc
Author: Theodore Ts'o 
Date:   Tue Aug 22 00:54:15 2017 -0400

libsupport: don't try accessing the project quota for 128 byte inodes

If the file system has 128 byte inode, it's not possible to access its
project quota id, since the inode is too small.  So prevent a
potential out-of-bounds read in get_qid().

The problem was found by valgrind and American Fuzzy Lop.

Address-Debian-Bug: #871540

Signed-off-by: Theodore Ts'o 

diff --git a/lib/support/mkquota.c b/lib/support/mkquota.c
index 931a839dd..e65c95b76 100644
--- a/lib/support/mkquota.c
+++ b/lib/support/mkquota.c
@@ -249,6 +249,11 @@ static int dict_uint_cmp(const void *a, const void *b)
return -1;
 }
 
+static inline int project_quota_valid(quota_ctx_t qctx)
+{
+   return (EXT2_INODE_SIZE(qctx->fs->super) > EXT2_GOOD_OLD_INODE_SIZE);
+}
+
 static inline qid_t get_qid(struct ext2_inode_large *inode, enum quota_type 
qtype)
 {
unsigned int inode_size;
@@ -392,6 +397,8 @@ void quota_data_add(quota_ctx_t qctx, struct 
ext2_inode_large *inode,
inode_uid(*inode),
inode_gid(*inode), space);
for (qtype = 0; qtype < MAXQUOTAS; qtype++) {
+   if (qtype == PRJQUOTA && !project_quota_valid(qctx))
+   continue;
dict = qctx->quota_dict[qtype];
if (dict) {
dq = get_dq(dict, get_qid(inode, qtype));
@@ -419,6 +426,8 @@ void quota_data_sub(quota_ctx_t qctx, struct 
ext2_inode_large *inode,
inode_uid(*inode),
inode_gid(*inode), space);
for (qtype = 0; qtype < MAXQUOTAS; qtype++) {
+   if (qtype == PRJQUOTA && !project_quota_valid(qctx))
+   continue;
dict = qctx->quota_dict[qtype];
if (dict) {
dq = get_dq(dict, get_qid(inode, qtype));
@@ -444,6 +453,8 @@ void quota_data_inodes(quota_ctx_t qctx, struct 
ext2_inode_large *inode,
inode_uid(*inode),
inode_gid(*inode), adjust);
for (qtype = 0; qtype < MAXQUOTAS; qtype++) {
+   if (qtype == PRJQUOTA && !project_quota_valid(qctx))
+   continue;
dict = qctx->quota_dict[qtype];
if (dict) {
dq = get_dq(dict, get_qid(inode, qtype));



Bug#858255: Multiple security issues

2017-08-21 Thread Salvatore Bonaccorso
Control: clone -1 -2
Control: retitle -2 virglrenderer: CVE-2017-6386

Hi

There was an upload to unstable (0.6.0-1). Out of the CVEs one was not
yet fixed: CVE-2017-6386. Cloning to record that one separately.

Regards,
Salvatore



Bug#872846: temporarily readd POT-Creation-Date

2017-08-21 Thread Helmut Grohne
On Mon, Aug 21, 2017 at 10:32:40PM +0200, Santiago Vila wrote:
> That's a bug in an upstream bug tracker.
> 
> Does our glibc also FTBFS for the same reason? Where is the Debian bug number?

Yes, it does. If you need a number, clone it.

> It just makes the .mo files to be different when you rebuild the
> package. But in general this is supposed to happen at the same time
> in all architectures, triggered by a new Debian revision.

There is nothing that ensures that packages are built at the same time.
Thus I ran into precisely that issue. I didn't pull this one out of my
hair.

> Moreover: How many of those in the list do not also violate Debian policy 
> section 8.2?

Guess: most.

> Also, bug #872806 does not seem a good example to me, because the library
> should not contain unversioned .mo files to begin with.

I'd like to to provide better examples, but with the current breakage
this is difficult to analyze.

> So, if I have to revert, I will do, but so far I don't see this is a
> catastrophic failure that requires a reversion.

It currently breaks the rebootstrap qa. This happens regularly, but the
difference here is that the present gettext issue is very hard to work
around.  Thus it "blinds" me of other bootstrap issues and makes them
harder to track down. If you have ideas for reasonable workarounds,
that'd be welcome. The source/binary version skew of glibc is currently
fatal to dpkg.

The present glibc FTBFS also prevents CVE fixes from transitioning to
testing.

Your comparison to gcc-7 is a straw man as for every gcc major release a
full archive rebuild is performed and bug reports are filed ahead of the
upload. People had months to fix. In contrast, this change was
cherry-picked from upstream, so glibc is kinda unprepared here.

Please reconsider (or send patches).

Helmut



Bug#871539: e2fsck: buffer underwrite in raw_read_blk()

2017-08-21 Thread Theodore Ts'o
On Wed, Aug 09, 2017 at 12:10:22AM +0200, Jakub Wilk wrote:
> Package: e2fsprogs
> Version: 1.43.5-1
> 
> $ gzip -d underwrite.ext2.gz
> $ valgrind /sbin/e2fsck -f -y underwrite.ext2 > /dev/null
> ==6645== Memcheck, a memory error detector
> ==6645== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
> ==6645== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
> ==6645== Command: /sbin/e2fsck -f -y underwrite.ext2
> ==6645==
> e2fsck 1.43.5 (04-Aug-2017)
> ==6645== Invalid write of size 1
> ==6645==at 0x48349C0: memset (in 
> /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
> ==6645==by 0x4892A2E: memset (string3.h:90)
> ==6645==by 0x4892A2E: raw_read_blk (unix_io.c:250)
> ==6645==by 0x48936FE: unix_read_blk64.part.5 (unix_io.c:862)
> ==6645==by 0x4880D82: ext2fs_read_inode_full (inode.c:803)
> ==6645==by 0x4880FF4: ext2fs_read_inode (inode.c:845)
> ==6645==by 0x11745F: check_resize_inode (super.c:346)
> ==6645==by 0x1126C0: main (unix.c:1761)
> ==6645==  Address 0x4affac7 is 1 bytes before a block of size 1,024 alloc'd
> ==6645==at 0x482E2BC: malloc (in 
> /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
> ==6645==by 0x488198D: ext2fs_get_mem (ext2fs.h:1740)
> ==6645==by 0x488198D: io_channel_alloc_buf (io_manager.c:140)
> ==6645==by 0x4892CDE: alloc_cache (unix_io.c:401)
> ==6645==by 0x4893CEE: unix_open_channel (unix_io.c:644)
> ==6645==by 0x4885046: ext2fs_open2 (openfs.c:160)
> ==6645==by 0x1151AA: try_open_fs (unix.c:1141)
> ==6645==by 0x1120E3: main (unix.c:1447)
> ...

I'm not able to reproduce the problem.  Can you double check whether
you uploaded the correct image?  (In particular, is it possible that
you uploaded the image after it was modified by running "/sbin/e2fsck
-f -y" on the image?

Thanks,

- Ted

 {/build/e2fsprogs-maint/e2fsck}  
1279% gunzip < /tmp/underwrite.ext2.gz  > /tmp/underwrite.ext2
 {/build/e2fsprogs-maint/e2fsck}  
1280% sha1sum /tmp/underwrite.ext2
32f671c8659cd0ac2f2d273b45669642d016344a  /tmp/underwrite.ext2
 {/build/e2fsprogs-maint/e2fsck}  
1281% valgrind /sbin/e2fsck -f -y /tmp/foo.img > /dev/null
==7619== Memcheck, a memory error detector
==7619== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==7619== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==7619== Command: /sbin/e2fsck -f -y /tmp/foo.img
==7619== 
e2fsck 1.43.5 (04-Aug-2017)
==7619== 
==7619== HEAP SUMMARY:
==7619== in use at exit: 18,231 bytes in 163 blocks
==7619==   total heap usage: 480 allocs, 317 frees, 184,872 bytes allocated
==7619== 
==7619== LEAK SUMMARY:
==7619==definitely lost: 0 bytes in 0 blocks
==7619==indirectly lost: 0 bytes in 0 blocks
==7619==  possibly lost: 0 bytes in 0 blocks
==7619==still reachable: 18,231 bytes in 163 blocks
==7619== suppressed: 0 bytes in 0 blocks
==7619== Rerun with --leak-check=full to see details of leaked memory
==7619== 
==7619== For counts of detected and suppressed errors, rerun with: -v
==7619== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)



Bug#872883: simgrid: FTBFS on sh4: Could not figure out the stack setup

2017-08-21 Thread Aaron M. Ucko
Source: simgrid
Version: 3.16+dfsg-1
Severity: important
Justification: fails to build from source (but built successfully in the past)

The build of simgrid for sh4 (admittedly not a release architecture) failed:

  CMake Error at CMakeLists.txt:602 (message):
Could not figure out the stack setup.  Compil: 1.  Exec: TRUE.  Output:
pc=0x7f6b163e sr=0x0001 pr=0x7ffee910 fpscr=0x0008
  
spc=0x ssr=0x gbr=0x7f7bf5a8 vbr=0x
  
sgr=0x dbr=0x delayed_pc=0x7ffee8f8 fpul=0x
  
r0=0x72ec r1=0x0001 r2=0xfed4 r3=0x
  
r4=0x71fc r5=0x41414141 r6=0x r7=0x7f57b008
  
r8=0x00010010 r9=0x r10=0x r11=0x
  
r12=0x7034 r13=0x r14=0x r15=0x7ffecfc0
  
r16=0x r17=0x r18=0x r19=0x
  
r20=0x r21=0x r22=0x r23=0x
  
Unhandled trap: 0x180

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



Bug#872882: simgrid: FTBFS with Java 1.5 (the latest on hppa)

2017-08-21 Thread Aaron M. Ucko
Source: simgrid
Version: 3.16+dfsg-1
Severity: important
Justification: fails to build from source (but built successfully in the past)

The build of simgrid for hppa (admittedly not a release architecture)
failed because Java is too old there:

  -- Could NOT find Java: Found unsuitable version "1.5.0", but required is at 
least "1.7" (found /usr/bin/java)

Please version simgrid's build dependency on default-jdk to (>= 2:1.7~)
accordingly.

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



Bug#872881: simgrid: FTBFS: `__atomic_fetch_add_8' undefined

2017-08-21 Thread Aaron M. Ucko
Source: simgrid
Version: 3.16+dfsg-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Builds of simgrid failed on armel, mips, mipsel, and the non-release
architectures m68k and powerpc:

  lib/libsimgrid.so.3.16: undefined reference to `__atomic_fetch_add_8'
  collect2: error: ld returned 1 exit status
  CMakeFiles/testall.dir/build.make:314: recipe for target 'testall' failed

Please link libsimgrid against -latomic on these architectures.  You
can in general do so without hardcoding an architecture list by
arranging to link with

  -Wl,--as-needed -latomic --Wl,--no-as-needed

but I don't know how easy that is to do under CMake.

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



Bug#872880: libemf: FTBFS: #error Unknown CPU architecture!

2017-08-21 Thread Aaron M. Ucko
Source: libemf
Version: 1.0.9+git.9.e2f97d9-1
Severity: important
Tags: upstream
Justification: fails to build from source

Builds of libemf have been failing on arm64, mips*, and the
non-release architectures hppa, m68k, and sh4:

  In file included from ../include/libEMF/wine/windef.h:16:0,
   from ../include/libEMF/emf.h:27,
   from libemf.h:32,
   from libemf.cpp:24:
  ../include/libEMF/wine/winnt.h:61:3: error: #error Unknown CPU architecture!
   # error Unknown CPU architecture!
 ^
  In file included from ../include/libEMF/wine/windef.h:16:0,
   from ../include/libEMF/emf.h:27,
   from libemf.h:32,
   from libemf.cpp:24:
  ../include/libEMF/wine/winnt.h:1429:2: error: #error You need to define a 
CONTEXT for your CPU
   #error You need to define a CONTEXT for your CPU
^
  ../include/libEMF/wine/winnt.h:1432:9: error: 'CONTEXT' does not name a type; 
did you mean 'CONTEXT86'?
   typedef CONTEXT *PCONTEXT;
   ^~~
   CONTEXT86

Could you please take a look?  It would be best if you could cut out
the CPU-dependent code altogether.  However, if that's infeasible,
please restrict libemf's official Architecture accordingly so that
incompatible autobuilders don't bother trying to cover it.

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



Bug#872553: synaptic: Segmentation fault

2017-08-21 Thread Schmidt Cristian Hernan
Package: synaptic
Version: 0.84.2
Followup-For: Bug #872553

Segmentation fault when it is executed



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

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.15-1
ii  libapt-inst2.0   1.5~beta1
ii  libapt-pkg5.01.5~beta1
ii  libatk1.0-0  2.24.0-1
ii  libc62.24-14
ii  libcairo-gobject21.14.10-1
ii  libcairo21.14.10-1
ii  libept1.5.0  1.1+nmu3+b1
ii  libgcc1  1:7.1.0-13
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.53.4-3
ii  libgnutls30  3.5.14-2
ii  libgtk-3-0   3.22.18-1
ii  libpango-1.0-0   1.40.6-1
ii  libpangocairo-1.0-0  1.40.6-1
ii  libpcre2-8-0 10.22-3
ii  libstdc++6   7.1.0-13
ii  libvte-2.91-00.46.2-1
ii  libx11-6 2:1.6.4-3
ii  libxapian30  1.4.4-2
ii  policykit-1  0.105-18
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages synaptic recommends:
ii  libgtk2-perl   2:1.24992-1+b1
ii  rarian-compat  0.8.1-6+b1
ii  xdg-utils  1.1.1-1

Versions of packages synaptic suggests:
pn  apt-xapian-index 
ii  deborphan1.7.28.8-0.3+b1
pn  dwww 
ii  menu 2.1.47+b1
ii  software-properties-gtk  0.96.20.2-1
ii  tasksel  3.39

-- no debconf information



Bug#872879: wmaker menu lost most of my apps

2017-08-21 Thread anomie
Package: wmaker
Version: 0.95.8-2

After upgrading from 0.95.8-1 to 0.95.8-2, the menu seems to have lost
the vast majority of my applications.

~/.xsession-errors tells me the following:

/usr/lib/WindowMaker/wmaker(configureMenu(rootmenu.c:1513)): warning: using 
default menu file "/usr/share/WindowMaker/menu" as the menu referenced in 
WMRootMenu could not be found 
/usr/lib/WindowMaker/wmaker(WMReadPropListFromFile(proplist.c:1548)): warning: 
syntax error in file /usr/share/WindowMaker/menu, line 1: extra data after end 
of property list

Not that /usr/share/WindowMaker/menu actually contains reference to the
missing applications anyway.

I suspect that whatever the "fix" was for bug 868431 somehow broke
things.



Bug#872795: ITP: adv-17v35x-dkms -- DKMS source for Advantech PCIe Multiport device driver

2017-08-21 Thread Ben Hutchings
On Mon, 2017-08-21 at 13:36 +0300, Andrey Drobyshev wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Andrey Drobyshev 
> 
> * Package name: adv-17v35x-dkms
>   Version : 5.0.3.0
>   Upstream Author : Advantech Co., Ltd
> * URL : 
> http://support.advantech.com/support/DownloadSRDetail_New.aspx?Doc_Source=Download_ID=1-1W8FZ5
> * License : GPL-2+
>   Programming Lang: C
>   Description : DKMS source for Advantech PCIe Multiport device driver
> 
> This serial driver provides kernel support for various multiport Advantech
> boards. Driver sources are taken from support.advantech.com (search for
> "Linux Driver for ACOM").
> 
> This package is aimed to provide DKMS sources for the driver.

These devices ought to be supported by the in-tree 8250_exar driver,
though it doesn't appear to match the Advantech device IDs yet.

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.



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


Bug#872878: sagenb-export: FTBFS when python3.5 is removed

2017-08-21 Thread Steve Langasek
Package: sagenb-export
Version: 3.2-2
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Dear Ximin,

The sagenb-export package now fails to build in Ubuntu, because python3.5
has been removed from artful - python3-all now depends only on python3.6 -
but debian/rules tries to run tox against python3.5.

I've uploaded the attached patch to Ubuntu to correct this, by running tox
only for the default python and python3 versions.

A more complete fix might iterate over 'py3versions -s' and run tox for
each, but that would require some dynamic mangling of tox.ini; so I think
just testing against the current default should be sufficient for now.

Since the python3.6 transition has begun in Debian and python3.5 will
therefore be dropped from unstable fairly soon, I'm marking this bug as
serious; but you can downgrade it in the short term if necessary,
understanding that it will become serious again.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru sagenb-export-3.2/debian/patches/python-versions-in-tox 
sagenb-export-3.2/debian/patches/python-versions-in-tox
--- sagenb-export-3.2/debian/patches/python-versions-in-tox 1969-12-31 
16:00:00.0 -0800
+++ sagenb-export-3.2/debian/patches/python-versions-in-tox 2017-08-21 
17:34:22.0 -0700
@@ -0,0 +1,30 @@
+Description: test against the current python versions, not hard-coded ones
+ Upstream test suite is testing against python2.7 and python3.5 at
+ build-time.  Fix this to test against 'python' and 'python3' to use
+ whatever the current Debian default is for this release, instead of
+ hard-coding a specific version number.
+Author: Steve Langasek 
+
+Index: sagenb-export-3.2/tox.ini
+===
+--- sagenb-export-3.2.orig/tox.ini
 sagenb-export-3.2/tox.ini
+@@ -1,12 +1,12 @@
+ [tox]
+-envlist = py27, py34
++envlist = python, python3
+ 
+-[testenv:py27]
+-commands=python2.7 -m unittest discover
++[testenv:python]
++commands=python -m unittest discover
+ 
+-[testenv:py34]
++[testenv:py3.4]
+ commands=python3.4 -m unittest discover
+ 
+-[testenv:py35]
+-commands=python3.5 -m unittest discover
++[testenv:python3]
++commands=python3 -m unittest discover
+ 
diff -Nru sagenb-export-3.2/debian/patches/series 
sagenb-export-3.2/debian/patches/series
--- sagenb-export-3.2/debian/patches/series 1969-12-31 16:00:00.0 
-0800
+++ sagenb-export-3.2/debian/patches/series 2017-08-21 17:32:40.0 
-0700
@@ -0,0 +1 @@
+python-versions-in-tox
diff -Nru sagenb-export-3.2/debian/rules sagenb-export-3.2/debian/rules
--- sagenb-export-3.2/debian/rules  2017-08-16 12:39:30.0 -0700
+++ sagenb-export-3.2/debian/rules  2017-08-21 17:34:29.0 -0700
@@ -16,7 +16,7 @@
 #  PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml
docs/ build/html # HTML generator
 #  PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bman
docs/ build/man # Manpage generator
 
-TOX_ENVLIST = py27,py35
+TOX_ENVLIST = python,python3
 
 override_dh_auto_test:
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))


Bug#872877: src:util-linux: fails to set Important: yes on binary packages

2017-08-21 Thread Adam Borowski
Package: src:util-linux
Version: 2.29.2-4
Severity: normal

Hi!
I'm afraid that current dpkg-gencontrol doesn't support the "Important:"
field.  It throws a warning then ignores it.  But, you can make it add
whatever you wish by giving it a X[BSC]*- prefix.

In this case, binary:mount and binary:fdisk should have:
XB-Important: yes

"man deb-src-control" has more information; thanks to Bastian Blank for a
better solution than my sed hack.


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

Kernel: Linux 4.13.0-rc6-debug-ubsan-00198-gafd58c2be315 (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)



Bug#866005: Backport TLS Client Certificate fixes

2017-08-21 Thread Paul Tagliamonte
retitle 866005 Backport TLS Client Certificate fixes
thanks

A few more changes I sent upstream have been accepted. I'm maintaining
the delta locally, is there any chance you could backport these patches
to the Debian package?

Since there was an upload since I filed the debdiff, I just attached the
patch, as fit for the debian/patches series. If the team is OK with it,
I can go ahead and upload this.

Thanks!
 Paul


-- 
Description: Multiple fixes to Client Certifciate handling
 The first is a fix to the verify-depth flag, which allows Client
 Certificates to be signed off an intermediary Certificate Authority.
 .
 Additionally, this will write x509 DER to the uwsgi buffer
 This will write the full x.509 DER into the buffer for use by clients
 during runtime. This feature is intended to allow clients to handle
 per-user ACL with the direct x.509 Certificate, without having to
 configure the webserver to extract the right bits, which may or may not
 be custom extensions.
 .
 One such example would be using and extracting the UPN SAN, or some
 other exotic extension.
Author: Paul Tagliamomnte 
Origin: upstream, https://github.com/unbit/uwsgi/pull/1562, https://github.com/unbit/uwsgi/issues/1563
Last-Update: 2017-08-21

diff --git a/core/ssl.c b/core/ssl.c
index 02e5449..c5e3ae7 100644
--- a/core/ssl.c
+++ b/core/ssl.c
@@ -326,8 +326,7 @@ SSL_CTX *uwsgi_ssl_new_server_context(char *name, char *crt, char *key, char *ci
 else {
 SSL_CTX_set_verify(ctx, SSL_VERIFY_PEER, uwsgi_ssl_verify_callback);
 }
-// in the future we should allow to set the verify depth
-SSL_CTX_set_verify_depth(ctx, 1);
+SSL_CTX_set_verify_depth(ctx, uwsgi.ssl_verify_depth);
 
 		if (uwsgi.ssl_tmp_dir && !uwsgi_starts_with(client_ca, strlen(client_ca), "-BEGIN ", 11)) {
 			if (!name) {
diff --git a/core/uwsgi.c b/core/uwsgi.c
index f2fdc0f..816dcbc 100644
--- a/core/uwsgi.c
+++ b/core/uwsgi.c
@@ -653,6 +653,7 @@ static struct uwsgi_option uwsgi_base_options[] = {
 	{"snmp-community", required_argument, 0, "set the snmp community string", uwsgi_opt_snmp_community, NULL, 0},
 #ifdef UWSGI_SSL
 	{"ssl-verbose", no_argument, 0, "be verbose about SSL errors", uwsgi_opt_true, _verbose, 0},
+	{"ssl-verify-depth", optional_argument, 0, "set maximum certificate verification depth", uwsgi_opt_set_int, _verify_depth, 1},
 #ifdef UWSGI_SSL_SESSION_CACHE
 	// force master, as ssl sessions caching initialize locking early
 	{"ssl-sessions-use-cache", optional_argument, 0, "use uWSGI cache for ssl sessions storage", uwsgi_opt_set_str, _sessions_use_cache, UWSGI_OPT_MASTER},
diff --git a/plugins/http/https.c b/plugins/http/https.c
index 1d04666..dc629e3 100644
--- a/plugins/http/https.c
+++ b/plugins/http/https.c
@@ -187,6 +187,12 @@ int hr_https_add_vars(struct http_session *hr, struct corerouter_peer *peer, str
 #endif
 hr->ssl_client_cert = SSL_get_peer_certificate(hr->ssl);
 if (hr->ssl_client_cert) {
+int client_cert_len;
+unsigned char *client_cert_der = NULL;
+client_cert_len = i2d_X509(hr->ssl_client_cert, _cert_der);
+if (client_cert_len < 0) return -1;
+if (uwsgi_buffer_append_keyval(out, "HTTPS_CLIENT_CERTIFICATE", 24, (char*)client_cert_der, client_cert_len)) return -1;
+
 X509_NAME *name = X509_get_subject_name(hr->ssl_client_cert);
 if (name) {
 hr->ssl_client_dn = X509_NAME_oneline(name, NULL, 0);
diff --git a/uwsgi.h b/uwsgi.h
index 069e240..c706e2f 100644
--- a/uwsgi.h
+++ b/uwsgi.h
@@ -2791,6 +2791,10 @@ struct uwsgi_server {
 	// uWSGI 2.1 backport
 	int new_argc;
 	char **new_argv;
+
+#ifdef UWSGI_SSL
+	int ssl_verify_depth;
+#endif
 };
 
 struct uwsgi_rpc {
-- 
2.14.1



Bug#866796: ring: FTBFS against msgpack-c 2.x

2017-08-21 Thread James McCoy
On Sat, Jul 01, 2017 at 03:14:05PM -0400, James McCoy wrote:
> While performing rebuilds of packages which Build-Depend on
> libmsgpack-dev with the 2.x version in experimental, I found that ring
> FTBFS:
> 
> […]
> 
> I haven't looked into ring's code, but there were some API breaking
> changes in 2.x.

As a note, a quick fix until full support for the 2.x API is to build
with -DMSGPACK_DEFAULT_API_VERSION=1 in CXXFLAGS.  This forces the use
of the older C++ API.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB



Bug#683222: debian-policy: Policy section 4.4 is imprecise with respect to section 12.7

2017-08-21 Thread Russ Allbery
Sean Whitton  writes:

> Thus I am seeking seconds for the following patch:

> diff --git a/policy/ch-source.rst b/policy/ch-source.rst
> index f706a13..89b355a 100644
> --- a/policy/ch-source.rst
> +++ b/policy/ch-source.rst
> @@ -99,10 +99,11 @@ later reconfigure the package without losing the changes 
> you made.
>  Debian changelog: ``debian/changelog``
>  --
>  
> -Changes in the Debian version of the package should be briefly explained
> -in the Debian changelog file ``debian/changelog``.  [#]_ This includes
> -modifications made in the Debian package compared to the upstream one as
> -well as other changes and updates to the package.  [#]_
> +Every source package must include the Debian changelog file,
> +``debian/changelog``.  Changes in the Debian version of the package
> +should be briefly explained in this file.  [#]_ This includes
> +modifications made in the Debian package compared to the upstream one
> +as well as other changes and updates to the package.  [#]_
>  
>  The format of the ``debian/changelog`` allows the package building tools
>  to discover which version of the package is being built and find out

Looks good to me.  Seconded.

-- 
Russ Allbery (r...@debian.org)   



Bug#683222: debian-policy: Policy section 4.4 is imprecise with respect to section 12.7

2017-08-21 Thread Jonathan Nieder
Sean Whitton wrote:
> On Wed, Aug 01, 2012 at 08:07:01AM +0900, Charles Plessy wrote:

>> Otherwise, how about something along these lines: [...]
>
> Commenting on Charles' patch, I think that it would be clearer to have
> the 'should' and 'must' requirements in separate sentences.
>
> Thus I am seeking seconds for the following patch:
>
> diff --git a/policy/ch-source.rst b/policy/ch-source.rst
> index f706a13..89b355a 100644
> --- a/policy/ch-source.rst
> +++ b/policy/ch-source.rst
> @@ -99,10 +99,11 @@ later reconfigure the package without losing the changes 
> you made.
>  Debian changelog: ``debian/changelog``
>  --
>  
> -Changes in the Debian version of the package should be briefly explained
> -in the Debian changelog file ``debian/changelog``.  [#]_ This includes
> -modifications made in the Debian package compared to the upstream one as
> -well as other changes and updates to the package.  [#]_
> +Every source package must include the Debian changelog file,
> +``debian/changelog``.  Changes in the Debian version of the package
> +should be briefly explained in this file.  [#]_ This includes
> +modifications made in the Debian package compared to the upstream one
> +as well as other changes and updates to the package.  [#]_
> 
>  The format of the ``debian/changelog`` allows the package building tools
>  to discover which version of the package is being built and find out

Seconded.  Thanks for tying up this loose end.

Sincerely,
Jonathan



Bug#872876: gnome-control-center: Wacom Tablet [on Wayland]: No tablet detected

2017-08-21 Thread Andrew Chadwick
Package: gnome-control-center
Version: 1:3.22.2-3
Severity: normal

Dear Maintainer,

The GNOME control center has stopped displaying the configuration
options for my [known working and good] Cintiq 13HD. When the tablet is
powered up and plugged in using its USB cable, the Wacom Tablet page of
gnome-control-center in Wayland still displays:

> No tablet detected
> Please plug in or turn on your Wacom tablet

See also bug#872875: under Xorg, this operation just crashes. Could this
Wayland problem be related?

One other discrepancy on my system: gnome-settings-daemon was recently
updated to 3.24.3-1 from 3.22.2-5. gnome-control-center is languishing
at a 3.22 version. I don't know if that is significant, so feel free to
refile this report if needed.

I can provide further info as needed, just let me know what to look at.

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

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

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.43-1
ii  apg2.2.3.dfsg.1-4+b1
ii  colord 1.3.3-2
ii  desktop-file-utils 0.23-2
ii  gnome-control-center-data  1:3.22.2-3
ii  gnome-desktop3-data3.22.2-1
ii  gnome-settings-daemon  3.24.3-1
ii  gsettings-desktop-schemas  3.24.0-2
ii  libaccountsservice00.6.43-1
ii  libatk1.0-02.24.0-1
ii  libc6  2.24-14
ii  libcairo-gobject2  1.14.10-1
ii  libcairo2  1.14.10-1
ii  libcanberra-gtk3-0 0.30-3
ii  libcanberra0   0.30-3
ii  libcheese-gtk253.22.1-1+b1
ii  libcheese8 3.22.1-1+b1
ii  libclutter-1.0-0   1.26.2+dfsg-1
ii  libclutter-gtk-1.0-0   1.8.2-2
ii  libcolord-gtk1 0.1.26-1.1
ii  libcolord2 1.3.3-2
ii  libcups2   2.2.4-3
ii  libfontconfig1 2.12.3-0.2
ii  libgdk-pixbuf2.0-0 2.36.5-2
ii  libglib2.0-0   2.53.6-1
ii  libgnome-bluetooth13   3.20.1-1
ii  libgnome-desktop-3-12  3.22.2-1
ii  libgoa-1.0-0b  3.22.5-1
ii  libgoa-backend-1.0-1   3.22.5-1
ii  libgrilo-0.3-0 0.3.3-2
ii  libgtk-3-0 3.22.18-1
ii  libgtop-2.0-10 2.34.2-1
ii  libgudev-1.0-0 230-3
ii  libibus-1.0-5  1.5.14-3
ii  libkrb5-3  1.15.1-2
ii  libmm-glib01.6.8-1
ii  libnm0 1.8.2-1
ii  libnma01.8.2-1
ii  libpango-1.0-0 1.40.6-1
ii  libpangocairo-1.0-01.40.6-1
ii  libpolkit-gobject-1-0  0.105-18
ii  libpulse-mainloop-glib010.0-2
ii  libpulse0  10.0-2
ii  libpwquality1  1.3.0-1+b1
ii  libsmbclient   2:4.6.5+dfsg-8
ii  libsoup2.4-1   2.56.0-2
ii  libupower-glib30.99.5-3
ii  libwacom2  0.25-0local
ii  libx11-6   2:1.6.4-3
ii  libxi6 2:1.7.9-1
ii  libxml22.9.4+dfsg1-3

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime  2.9.2-5+b1
ii  cups-pk-helper0.2.6-1+b1
ii  gkbd-capplet  3.22.0.1-1+b1
ii  gnome-online-accounts 3.22.5-1
ii  gnome-user-guide  3.22.0-1
ii  gnome-user-share  3.18.3-1+b1
ii  iso-codes 3.75-1
ii  libcanberra-pulse 0.30-3
ii  libnss-myhostname 234-2
ii  mousetweaks   3.12.0-1+b1
ii  network-manager-gnome 1.8.2-1
ii  policykit-1   0.105-18
ii  pulseaudio-module-bluetooth   10.0-2
pn  realmd
ii  rygel 0.32.1-3+b1
ii  rygel-tracker 0.32.1-3+b1
ii  system-config-printer-common  1.5.9-2

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

-- no debconf information
Aug 22 01:58:05 spatula kernel: [ 2856.921605] usb 1-1: new high-speed USB 
device number 23 using xhci_hcd
Aug 22 01:58:05 spatula kernel: [ 2857.061947] usb 1-1: New USB device found, 
idVendor=056a, idProduct=0305
Aug 22 01:58:05 spatula kernel: [ 2857.061953] usb 1-1: New USB device strings: 
Mfr=1, Product=2, SerialNumber=0
Aug 22 01:58:05 spatula kernel: [ 2857.061956] usb 1-1: Product: Wacom Cintiq 
13HD USB Hub
Aug 22 01:58:05 spatula kernel: [ 2857.061958] usb 1-1: Manufacturer: Wacom 
Co., Ltd.
Aug 22 01:58:05 

Bug#856586: Translation fix for e2fsprogs

2017-08-21 Thread Theodore Ts'o
On Tue, Aug 15, 2017 at 09:15:13PM +0200, Benno Schulenberg wrote:
> But you could do one step better.  Leaving the PO files entirely alone,
> any e2fsprogs util could, when asking a question and taking one keystroke
> for an answer, after checking whether the keystroke is in the translations
> for the "yY" or "nN" or "aA" strings, and not finding any match -- then,
> instead of assuming , it could check whether the keystroke is maybe
> "y" or "Y" (untranslated), and if so, assume that the user means .
> This would solve the problem no matter what translators do and no matter
> whether msgstrs go fuzzy in the future.

Thanks, that's a good suggestion.  I have reverted the po file changes
and make the change you've suggested.

- Ted



Bug#872875: Wacom: crash, "schema 'org.gnome.settings-daemon.peripherals.wacom' is not installed"

2017-08-21 Thread Andrew Chadwick
Package: gnome-control-center
Version: 1:3.22.2-3
Severity: important

Dear Maintainer,

The "Wacom Tablet" control panel applet crashes under Xorg any time my
Cintiq 13HD is plugged in via its USB connection. The fault seems to be
a missing schema definition. Affects completely new system users with a
new home dir.

Q: What led up to the situation?

I needed to configure my Wacom tablet in the normal fashion on a GNOME
desktop. I knew a recent update had apparently changed several things in
the Debian GNOME setup, and I was comparing Xorg behaviour against
Wayland behaviour to see if it was worth taking the jump yet (spoiler:
it's not).

Q: What exactly did you do (or not do) that was effective (or ineffective)?

Attempted to run the Wacom Tablet control panel applet when the tablet's
USB connector was 1. plugged in to the computer 2. not plugged in.

Q:  What was the outcome of this action?

1: crash. 2: no crash. In all cases, no ability to configure my tablet.

A run of "gdb -ex r --args gnome-control-center wacom" seemed to
indicate that this was due to a missing schema definition. reportbug
permitting, you should find attached a full backtrace run under a
freshly-created user account.

Q: What outcome did you expect instead?

No crash in all cases.
The ability to configure my tablet.

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


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

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

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.43-1
ii  apg2.2.3.dfsg.1-4+b1
ii  colord 1.3.3-2
ii  desktop-file-utils 0.23-2
ii  gnome-control-center-data  1:3.22.2-3
ii  gnome-desktop3-data3.22.2-1
ii  gnome-settings-daemon  3.24.3-1
ii  gsettings-desktop-schemas  3.24.0-2
ii  libaccountsservice00.6.43-1
ii  libatk1.0-02.24.0-1
ii  libc6  2.24-14
ii  libcairo-gobject2  1.14.10-1
ii  libcairo2  1.14.10-1
ii  libcanberra-gtk3-0 0.30-3
ii  libcanberra0   0.30-3
ii  libcheese-gtk253.22.1-1+b1
ii  libcheese8 3.22.1-1+b1
ii  libclutter-1.0-0   1.26.2+dfsg-1
ii  libclutter-gtk-1.0-0   1.8.2-2
ii  libcolord-gtk1 0.1.26-1.1
ii  libcolord2 1.3.3-2
ii  libcups2   2.2.4-3
ii  libfontconfig1 2.12.3-0.2
ii  libgdk-pixbuf2.0-0 2.36.5-2
ii  libglib2.0-0   2.53.6-1
ii  libgnome-bluetooth13   3.20.1-1
ii  libgnome-desktop-3-12  3.22.2-1
ii  libgoa-1.0-0b  3.22.5-1
ii  libgoa-backend-1.0-1   3.22.5-1
ii  libgrilo-0.3-0 0.3.3-2
ii  libgtk-3-0 3.22.18-1
ii  libgtop-2.0-10 2.34.2-1
ii  libgudev-1.0-0 230-3
ii  libibus-1.0-5  1.5.14-3
ii  libkrb5-3  1.15.1-2
ii  libmm-glib01.6.8-1
ii  libnm0 1.8.2-1
ii  libnma01.8.2-1
ii  libpango-1.0-0 1.40.6-1
ii  libpangocairo-1.0-01.40.6-1
ii  libpolkit-gobject-1-0  0.105-18
ii  libpulse-mainloop-glib010.0-2
ii  libpulse0  10.0-2
ii  libpwquality1  1.3.0-1+b1
ii  libsmbclient   2:4.6.5+dfsg-8
ii  libsoup2.4-1   2.56.0-2
ii  libupower-glib30.99.5-3
ii  libwacom2  0.25-0local   (see bug 872871 :-)
ii  libx11-6   2:1.6.4-3
ii  libxi6 2:1.7.9-1
ii  libxml22.9.4+dfsg1-3

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime  2.9.2-5+b1
ii  cups-pk-helper0.2.6-1+b1
ii  gkbd-capplet  3.22.0.1-1+b1
ii  gnome-online-accounts 3.22.5-1
ii  gnome-user-guide  3.22.0-1
ii  gnome-user-share  3.18.3-1+b1
ii  iso-codes 3.75-1
ii  libcanberra-pulse 0.30-3
ii  libnss-myhostname 234-2
ii  mousetweaks   3.12.0-1+b1
ii  network-manager-gnome 1.8.2-1
ii  policykit-1   0.105-18
ii  pulseaudio-module-bluetooth   10.0-2
pn  realmd
ii  rygel 0.32.1-3+b1
ii  rygel-tracker 0.32.1-3+b1
ii  system-config-printer-common  1.5.9-2

Versions of packages gnome-control-center suggests:
ii  gstreamer1.0-pulseaudio  1.12.2-1
ii  libcanberra-gtk-module   0.30-3
ii  libcanberra-gtk3-module  0.30-3
ii  x11-xserver-utils

Bug#864622: RFS: rich-minority/1.0.1-1 [ITP]

2017-08-21 Thread Nicholas D Steeves
Hi,

On Fri, Jul 07, 2017 at 09:20:03PM -0400, Nicholas D Steeves wrote:
> On Tue, Jun 13, 2017 at 06:42:28PM +0100, Sean Whitton wrote:
> > Hello Nicholas,
> > 
> > On Mon, Jun 12, 2017 at 07:33:12PM -0400, Nicholas D Steeves wrote:
> > > Would it be better to ship README.org and file a bug against the
> > > package myself?
> > 
> > Yes.  Why not ship README.org in the interim?
> 
> Let's discuss .org documentation at DebConf.  I've converted the
> README to plaintext for now.

At DebConf consensus was reached that emacs users prefer READMEs as
org files ;-) Commit 393e81b and the package on mentors now reflects
this.

> > > These two points seem contradictory to me.  Do you know how
> > > diminish.el is more quick and simple?  Also, can I use your answer for
> > > a patch against the upstream description, because I might not be the
> > > only one who's not confused about this.  Failing that, I can open an
> > > upstream issue/request for clarified description.
> > 
> > diminish.el works like this:
> > 
> > (diminish 'auto-fill-function)
> > 
> > That's it.  Clearly simpler.
> 
> I think this is probably the simplest rich-minority-mode equivalent,
> assuming that subsequent (diminish 'minor-mode-function) adds items
> to-be-hidden:
> 
> (push " Fill" rm-blacklist)
> 
> I haven't investigated corner cases, but it would seem that
> rich-minority-mode might also be simple :-)

Would you like me to add this to the documentation?  Of course I'll
also submit a patch upstream.

Also, please let me know if you're currently too busy to sponsor this
one.  I can find an off-team sponsor if necessary.

Cheers,
Nicholas


signature.asc
Description: PGP signature


Bug#872874: libxkbcommon-x11-dev: Missing depends on libxkbcommon-dev

2017-08-21 Thread Jeremy Bicha
Package: libxkbcommon-x11-dev
Version: 0.7.1-1
Severity: serious

libxkbcommon-x11-dev has this line in its pkgconfig file:

Requires: xkbcommon

That means it needs a Depends on libxkbcommon-dev .

Thanks,
Jeremy Bicha



Bug#872868: debian-policy: section numbers missing

2017-08-21 Thread Russ Allbery
Sean Whitton  writes:

> The PDF, HTML, info and ePub output formats have section numbering.

> The plain text format doesn't yet, mainly because it's put together with
> a local hack -- Sphinx generates one plain text file for each chapter,
> but we want a single policy.txt.  We are waiting on better upstream
> support.

Well, it's not just that, but also that Sphinx in general doesn't add
section numbers to the text output.  But yes, it's unfortunately a
casualty of the reStructuredText conversion.

If we have to, we'll hack together something that will add section
numbers at some point, but I'm still hoping that Sphinx upstream will add
support for this.

-- 
Russ Allbery (r...@debian.org)   



Bug#683222: debian-policy: Policy section 4.4 is imprecise with respect to section 12.7

2017-08-21 Thread Sean Whitton
control: tag -1 +patch

On Wed, Aug 01, 2012 at 08:07:01AM +0900, Charles Plessy wrote:
> Otherwise, how about something along these lines: [...]

Commenting on Charles' patch, I think that it would be clearer to have
the 'should' and 'must' requirements in separate sentences.

Thus I am seeking seconds for the following patch:

diff --git a/policy/ch-source.rst b/policy/ch-source.rst
index f706a13..89b355a 100644
--- a/policy/ch-source.rst
+++ b/policy/ch-source.rst
@@ -99,10 +99,11 @@ later reconfigure the package without losing the changes 
you made.
 Debian changelog: ``debian/changelog``
 --
 
-Changes in the Debian version of the package should be briefly explained
-in the Debian changelog file ``debian/changelog``.  [#]_ This includes
-modifications made in the Debian package compared to the upstream one as
-well as other changes and updates to the package.  [#]_
+Every source package must include the Debian changelog file,
+``debian/changelog``.  Changes in the Debian version of the package
+should be briefly explained in this file.  [#]_ This includes
+modifications made in the Debian package compared to the upstream one
+as well as other changes and updates to the package.  [#]_
 
 The format of the ``debian/changelog`` allows the package building tools
 to discover which version of the package is being built and find out

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#872873: ITP: emacs-neotree -- Emacs directory tree plugin like NerdTree for Vim

2017-08-21 Thread Nicholas D Steeves
P.S. elpa-neotree is also needed for progress towards spacemacs (
https://pkg-emacsen.alioth.debian.org/spacemacs/ )



Bug#695188: Multiple "Bug#" references in subject

2017-08-21 Thread Antoine Bernard
Dear Maintainers

Here my patch proposal for this bug.

Cheers,

-- 

Antoine BERNARD

From 7447b5e5a0eced6e1d1b38da05c1c60e5e0ecd71 Mon Sep 17 00:00:00 2001
From: Antoine Bernard 
Date: Tue, 22 Aug 2017 00:50:16 +0200
Subject: [PATCH] Fix 695188 intelligent add of Bug#XX

We prefix the subject of a mail by Bug#XX: only if the subject does
not already contain it.
---
 scripts/process | 14 ++
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/scripts/process b/scripts/process
index 3eba1fc..b135566 100755
--- a/scripts/process
+++ b/scripts/process
@@ -731,7 +731,13 @@ if ($ref<0) { # new bug report
 print {$debugfh} "maintainers >".join(' ',@maintaddrs)."<\n";
 
 my $orgsender= defined($header{'sender'}) ? "Original-Sender: $header{'sender'}\n" : '';
-my $newsubject= $subject;  $newsubject =~ s/^$gBug#$ref:*\s*//;
+
+my $newsubject;
+if ($subject =~ /$gBug#$ref:*\s*/) {
+$newsubject = $subject;
+} else {
+$newsubject = "$gBug#$ref: $subject";
+}
 
 my $xcchdr= $header{ 'x-debbugs-cc' } || '';
 if ($xcchdr =~ m/\S/) {
@@ -829,7 +835,7 @@ my $common_headers='';
 if ($codeletter eq 'U') { # sent to -submitter
 ("Message", "sent on", $data->{originator}, "$gBug#$ref.");
 my $enc_msg=<{originator}
 ${resentcc}${common_headers}Resent-Date: $tdate
@@ -851,7 +857,7 @@ END
  (length($data->{package})? "; Package ".html_escape($data->{package})."" : '').
  ".");
 my $enc_msg=<

Bug#872872: python-pika-pool: add missing test dependency

2017-08-21 Thread Nishanth Aravamudan
Package: python-pika-pool
Version: 0.1.3-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Dear Maintainer,


In Ubuntu, the attached patch was applied to achieve the following:

  * d/tests/control: add python3-all as depedency of pika-pool-unit-tests. 

Thanks for considering the patch.

*** /tmp/tmpknmYDd/python-pika-pool_0.1.3-1ubuntu2.debdiff
diff -Nru python-pika-pool-0.1.3/debian/tests/control 
python-pika-pool-0.1.3/debian/tests/control
--- python-pika-pool-0.1.3/debian/tests/control 2016-03-04 12:20:20.0 
-0800
+++ python-pika-pool-0.1.3/debian/tests/control 2017-06-12 17:37:30.0 
-0700
@@ -1,3 +1,3 @@
 Tests: pika-pool-unit-tests
-Depends: python-pytest, python3-pytest, python-pika, python3-pika, 
rabbitmq-server
+Depends: python-pytest, python3-pytest, python-pika, python3-pika, 
rabbitmq-server, python3-all
 Restrictions: needs-root


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

Kernel: Linux 4.12.0-11-generic (SMP w/4 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)

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd



Bug#872873: ITP: emacs-neotree -- Emacs directory tree plugin like NerdTree for Vim

2017-08-21 Thread Nicholas D Steeves
Package: wnpp
Severity: wishlist
Owner: Nicholas D Steeves 

* Package name: emacs-neotree
  Version : 0.5.2
  Upstream Author : Aborn Jiang 
* URL : https://github.com/jaypei/emacs-neotree
* License : GPL-3+
  Programming Lang: lisp
  Description : Emacs directory tree sidebar like NerdTree for Vim

This is package is for convenience and feature parity with other
IDEs...and with Vim :-o Is useful for anyone who is used to this
feature, and especially for anyone with a widescreen monitor.  I will
start using it as soon as I have packaged it.  One surprising thing it
supports is optional icons!

I plan to maintain it as a member of the Emacs Addons Team, and I will
need a sponsor.

Sincerely,
Nicholas



Bug#872870: RFS: fountain-mode/2.3.0-1 [ITP]

2017-08-21 Thread Nicholas D Steeves
Package: sponsorship-requests
Severity: wishlist

Control: block 850337 by -1

Dear mentors and Emacs Addons Team,

I am looking for a sponsor for my package "fountain-mode".

Package name: fountain-mode
Version : 2.3.0-1
Upstream Author : Paul Rankin 
URL : https://github.com/rnkn/fountain-mode
License : GPL-3+
Section : lisp

It builds this binary package:

elpa-fountain-mode - Emacs major mode for screenwriting in Fountain markup

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

https://mentors.debian.net/package/fountain-mode

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

dget -x 
https://mentors.debian.net/debian/pool/main/f/fountain-mode/fountain-mode_2.3.0-1.dsc

I plan to maintain this package as part of the Emacs Addons Team.  One can 
clone its git repo using this command:

git clone ssh://git.debian.org/git/pkg-emacsen/pkg/fountain-mode.git


fountain-mode (2.3.0-1) unstable; urgency=medium

  * Initial release. (Closes: #850337)

 -- Nicholas D Steeves   Mon, 21 Aug 2017 19:28:45 -0400


Regards,
Nicholas D Steeves



Bug#872871: libwacom2: New upstream version available (0.25)

2017-08-21 Thread Andrew Chadwick
Package: libwacom2
Version: 0.24
Severity: normal

Dear Maintainer,

A new upstream version of libwacom is available: 0.25. It builds cleanly
with the current 0.24-1 debian/ subtree and a fresh ChangeLog entry for
0.25-0whatever.

Q. What led up to the situation?

I'm investigating a Cintiq 13HD configuration which has stopped working
on a recent GNOME update (... Wayland has become the default...)

Q. What exactly did you do (or not do) that was effective (or ineffective)?

Was unable to use the GNOME Wacom control panel: it either crashed (X11)
or refused to recognised the tablet (Wayland).

My new libwacom2 build does not solve this problem, but it may be
relevant for GNOME Wacom setups in other ways during the current Time of
Great Change.

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

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

Versions of packages libwacom2 depends on:
ii  libc62.24-14
ii  libglib2.0-0 2.53.4-3
ii  libgudev-1.0-0   230-3
ii  libwacom-common  0.25-0local

Versions of packages libwacom2 recommends:
ii  libwacom-bin  0.25-0local

libwacom2 suggests no packages.

-- no debconf information



Bug#617285: pptpsetup: use absolute path for pptp in tunnel file

2017-08-21 Thread James Cameron
Thanks, taken upstream.

63eea745af41f781b60cfdd39813e4f000ead5f0

pptpsetup - use absolute path to pptp

/usr/sbin may not be in PATH, especially when pptp is configured for use
by non-root user.

See discussion in Debian bug 617285.



Bug#872868: debian-policy: section numbers missing

2017-08-21 Thread Sean Whitton
control: retitle -1 Plain text output format lacks section numbering

Hello Adam,

On Tue, Aug 22 2017, Adam Borowski wrote:

> I'm afraid that the new upload of the policy doesn't include section numbers
> in the text -- neither in the TOC nor in the body.  As that's how we usually
> refer to parts of the Policy, that makes any such references impossible.

The PDF, HTML, info and ePub output formats have section numbering.

The plain text format doesn't yet, mainly because it's put together with
a local hack -- Sphinx generates one plain text file for each chapter,
but we want a single policy.txt.  We are waiting on better upstream
support.

In the meantime, you might consider using the info output format.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#870889: Depends: libc-bin (> 2.25) but 2.24-14 is installed

2017-08-21 Thread Axel Beckert
Hi Jidanni,

積丹尼 Dan Jacobson wrote:
> AB> If you install locales from experimental, you should also install
> AB> libc-bin from experimental.
> 
> There is no libc-bin from experimental.

Ah, for some reasons it's only available on incoming.debian.org (but for
about one and a half day already — that's unusal):
https://incoming.debian.org/debian-buildd/pool/main/g/glibc/libc-bin_2.25-0experimental1_amd64.deb

Sorry that I didn't noticed that detail earlier:

~ → apt-cache policy libc-bin
libc-bin:
  Installed: 2.24-14
  Candidate: 2.24-15
  Version table:
 2.25-0experimental1 1
  1 https://incoming.debian.org/debian-buildd buildd-experimental/main 
amd64 Packages
 2.24-15 990
990 https://ftp.ch.debian.org/debian sid/main amd64 Packages
500 https://incoming.debian.org/debian-buildd buildd-unstable/main 
amd64 Packages
 *** 2.24-14 600
600 https://ftp.ch.debian.org/debian testing/main amd64 Packages
100 /var/lib/dpkg/status

> Closing this bug.

Thanks. Should solve itself as soon as that upload it hits the normal
mirrors.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#872869: msgfmt: trailing null bytes in header's msgstr

2017-08-21 Thread Jakub Wilk

Package: gettext
Version: 0.19.8.1-3
Control: affects -1 + i18nspector

The upstream commmit d13f165b8370 updates the header message msgstr, but it 
keeps the original msgstr_len ("the number of bytes in msgstr, including the 
terminating NUL"). As consequence, in the generated MO file there's a bunch of 
null bytes at the end of the msgstr.


I guess this does not matter for gettext-runtime, but it makes i18nspector (and 
maybe other strict MO parsers) upset:


  $ msgunfmt /usr/share/locale/pl/LC_MESSAGES/gettext-runtime.mo | msgfmt -
  $ i18nspector messages.mo
  E: messages.mo: invalid-mo-file unexpected null byte in msgstr


-- System Information:
Architecture: i386

Versions of packages gettext depends on:
ii  libc6  2.24-14
ii  libcroco3  0.6.12-1
ii  libglib2.0-0   2.53.4-3
ii  libgomp1   7.2.0-1
ii  libncurses56.0+20170715-2
ii  libtinfo5  6.0+20170715-2
ii  libunistring2  0.9.7-2
ii  libxml22.9.4+dfsg1-3.1
ii  gettext-base   0.19.8.1-3
ii  dpkg   1.18.24
ii  install-info   6.4.90.dfsg.1-1+b1

--
Jakub Wilk



Bug#646881: pptp-linux: pptpsetup fails to properly store password with quotation mark (") in /etc/ppp/chap-secrets

2017-08-21 Thread James Cameron
Thanks, taken upstream.

e62bfa7f11b0af355ff0367f8e1f22c42328639b



Bug#872798: nslcd: can be killed by the OOM Killer, DoS

2017-08-21 Thread Vincent Lefevre
Control: severity -1 normal

(fixing the typo in the Control line)

On 2017-08-21 21:47:04 +0200, Arthur de Jong wrote:
> Control: sevirity -1 normal
> 
> On Mon, 2017-08-21 at 13:17 +0200, Vincent Lefevre wrote:
> > Severity: grave
> > Justification: causes non-serious data loss and DoS from an end user.
> 
> The severity is a bit questionable and, at the very least not a flaw in
> or unique to nslcd.

Perhaps not unique to nslcd, but the consequences are the worst when
nslcd is killed: one can no longer access to the machine.

> Any local user that does not have resource limits applied to them
> can DoS the whole system easily so I'm lowering the severity to
> normal.

Note that users here are not malicious (they would have serious
problems if they DoS the whole system on purpose). Memory can be
exhausted by mistake (e.g. due to bugs) or just because the users
try to push the limits to solve some problems, and for this reason,
there are no resource limits. Still, one expects that the system
reacts in a reasonable manner if possible, e.g. the whole machine
should not crash and should remain accessible.

> The OOM is indeed a bit of Russian roulette on your system. You can
> tune it a bit with vm.panic_on_oom and vm.overcommit_memory sysctls or
> perform the following action that is equivalent to what newer nslcd
> does:
> 
> echo -1000 > /proc/`cat /var/run/nslcd/nslcd.pid`/oom_score_adj

I suppose that a workaround based on this in /etc/init.d/nslcd could
be after "start-stop-daemon --start ...":

  status=$?
  if [ $status -eq 0 ]; then
echo -1000 > /proc/`cat $NSLCD_PIDFILE`/oom_score_adj
  fi
  log_end_msg $status
  ;;

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#872868: debian-policy: section numbers missing

2017-08-21 Thread Adam Borowski
Package: debian-policy
Version: 4.1.0.0
Severity: normal

Hi!
I'm afraid that the new upload of the policy doesn't include section numbers
in the text -- neither in the TOC nor in the body.  As that's how we usually
refer to parts of the Policy, that makes any such references impossible.


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

Kernel: Linux 4.13.0-rc6-debug-ubsan-00198-gafd58c2be315 (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages debian-policy depends on:
ii  libjs-sphinxdoc  1.5.6-2

debian-policy recommends no packages.

Versions of packages debian-policy suggests:
pn  doc-base  

-- no debconf information



Bug#872760: asterisk-opus: uninstallable in unstable

2017-08-21 Thread Sam Hartman
OK, if the checksum doesn't change regularly, I can understand why  the
current arrangement makes sense.

It would bxe great to get asterisk-opus rebuilt though:-)



Bug#872867: is ISO-3166 really the optimal list for our users?

2017-08-21 Thread Daniel Pocock
Package: localechooser
Version: 2.69
Severity: wishlist

While visiting Kosovo, I have met several people interested in becoming
Debian users.

The first time I helped one of them run the Debian installation, I was
baffled to find that their country was not in the list offered by the
installer.

It is potentially not a good situation for a developer to be in a
country, surround by 1.8 million people who consider themselves to be
citizens of a country that our installer doesn't know about. 
Fortunately Kosovans are really nice people and weren't upset about this
but I can image they must feel quite sad each time something like this
happens.

According to this section in the Debian Installer i18n guide[1], the
list of countries is based on ISO3166.

According to wikipedia, ISO3166 comes from a group of 10
representatives[2] from mostly rich countries.

The Debian Social Contract[3], point 4, requires us to put our users
first.  Can Debian do more to listen to the 1.8 million potential users
in Kosovo and other countries like it?  Are we actually obliged to
respect how our users see themselves over and above the way some
bureaucrats in Geneva see them?

I would propose that we regard ISO3166 as a subset of the list of
countries perceived by our users and that for the next installer
release, the locale chooser offers a list of countries with a disclaimer
that some of them are not in ISO3166 but they are included at the
request of our users.

Maybe the list can show two columns, country and country code.  For
countries where ISO3166 is not competent, the country code column could
be blank.

Implementing this might be tricky but not impossible.  For example, a
crude implementation may simply display the extra countries in the main
list, but if somebody selects one of them, the installer shows a message
apologizing for the fact they are not fully supported and offering to
help them choose from a subset of related country codes.  Maybe their
preferred choice (verbose country name) could be saved somewhere for
later use when their country is fully supported and a future version of
localechooser will help them adapt to their eventual country code during
a future dist-upgrade.

For Kosovo in particular, Wikipedia notes[4] that "The code XK is being
used by the European Commission
,^[21]
 the IMF
, and SWIFT
,^[22]
 CLDR and
other organizations as a temporary country code for Kosovo
.".  Other 2-letter codes are
mentioned elsewhere so the ideal solution may avoid using a 2 letter
code for such countries or maybe it can borrow one of the codes used by
other international organizations who didn't wait for ISO3166.

It may be interesting to support micronations like the Principality of
Hutt River[5] too.

Regards,

Daniel


1. https://d-i.alioth.debian.org/doc/i18n/ch01s05.html#idm45330184240096
2. https://en.wikipedia.org/wiki/ISO_3166#Members
3. https://www.debian.org/social_contract
4. https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2
5. https://en.wikipedia.org/wiki/Principality_of_Hutt_River



Bug#786470: debian-policy: [copyright-format] Add an optional “License-Grant” field

2017-08-21 Thread Sean Whitton
On Tue, Aug 22 2017, Ben Finney wrote:

> On 20-Aug-2017, Sean Whitton wrote:
>
>> - note that this bug doesn't apply to policy's HEAD anymore because
>>   we've switched to rST
>
> Did you find a conflict? I have pulled the latest HEAD (commit hash
> f0f316c879a7e60e), and the ‘./copyright-format-1.0.xml’ remains the
> only source document of the “Machine-readable debian/copyright file”
> specification.

Sorry, I forgot that we haven't actually converted that file.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#872814: sakura: terminal window closes when pressing any key

2017-08-21 Thread Diego Caraffini
Thanks, I imagined as much, but I figured that an actual bug report could
 help track the resolution of the issue.

---
Diego Caraffini

Anar caluva tielyanna
  (The Sun shall shine on your path)
   from Unfinished Tales  by JRR Tolkien

On Mon, Aug 21, 2017 at 10:41 AM, Andreas Ronnquist 
wrote:

> Control: forwarded -1 https://bugs.launchpad.net/sakura/+bug/1658413
> Control: tag -1 + pending
>
> >
> > Dear Maintainer,
> >
> > I used "aptitude safe-update" to transition from Stretch to  Buster a
> > couple of weeks ago; since then I run aptitude update a few times.
> > Over the last few days, the sakura temninal window closes on its own
> > as soon as I try to type a command.
> >
>
> Yeah, this is due to the bug you mentioned, and you running Wayland.
> I'll provide an updated Debian package, either with patches fixing it,
> or a new upstream release fixing this if it released soon. There's a
> patch provided in the upstream report.
>
> I am waiting and hoping for a new upstream release, but since it's
> vacation times, it could be some time.
>
> -- Andreas Rönnquist
> gus...@debian.org
>


Bug#872828: RFS: node-regjsgen/0.3.0-1 ITP

2017-08-21 Thread Bastien ROUCARIES
On Mon, Aug 21, 2017 at 11:22 PM, Julien Puydt  wrote:
> Re,
>
> Le 21/08/2017 à 22:31, Bastien ROUCARIES a écrit :
>> Will sponsor
>
> Thanks!
>
>> On Mon, Aug 21, 2017 at 10:25 PM, Bastien ROUCARIES
>>  wrote:
>>> control: owner -1 ro...@debian.org
>>>
>>> On Mon, Aug 21, 2017 at 9:52 PM, Julien Puydt  
>>> wrote:
 Hi,

 Le 21/08/2017 à 20:54, Bastien Roucaries a écrit :
>>   Section : web
>
> Section: JavaScript

 Changed.

 Snark on #debian-js

>>
>> Some remark:
>> - watch is now version 4
>
> Ok -- I'll have to check what goodies there are in this version.
>
>> - copyright only 2017 and one author what give git log about year and author 
>> ?
>
> The logs show Benjamin Tan and small contributions from Mathias Bynens.
> I pushed a change on the dates.
>
>> - test data json does not build from source. This need a repack (use
>> copyright file excluded and uscan. It is free but FTBFS so add +ds
>> suffix)
>
> Are you sure? The tests/ directory isn't used at all by my packaging, so
> it shouldn't be a FTBFS.

Yes source-is-missing warning

>> - a small smoke test supplied as example and run will help
>
> I added debian/tests/compose and debian/example.js (shipped in
> /usr/share/doc/node-regjsgen).
>
> Snark on #debian-js



Bug#872753: RFS: node-regjsparser/0.2.1-1 ITP

2017-08-21 Thread roucaries bastien
On Mon, Aug 21, 2017 at 11:38 PM, Julien Puydt  wrote:
> Hi,
>
> Le 21/08/2017 à 22:44, roucaries bastien a écrit :
>> On Mon, Aug 21, 2017 at 10:33 PM, roucaries bastien
>>  wrote:
>>> control: owner -1 ro...@debian.org
>>>
>>> Will sponsor this one. Will review
>>>
>>> On Sun, Aug 20, 2017 at 9:59 PM, Andrey Rahmatullin  wrote:
 Control: retitle -1 RFS: node-regjsparser/0.2.1-1 [ITP]
>>
>> * uscan is now 4
>
> Done.
>
>> *demo should be supplied as example
>
> I don't know how that demo is to be run, so I find it annoying to ship
> it as an example :-/
>
> Notice that the manpage I wrote has examples.
>
>> * test/*.json should be remove FTBFS (if you could regenerate you are
>> welcome to do)
>
> Same question as for nodejsgen : if it isn't used, do we still consider
> it FTBFS?
Yes repack is safer and bonus point package is smaller

>
>> * parser.js FTBFS search generated in source
>
> Darn. I had checked that we had the tool to generate it in node-esprima,
> but now I see it requires node-unicode-8.0.0, which we don't have :-(
>
>> * a smoketest will be welcome (readme.md seems to include something)
>
> I added one.
>
> The problem with parser.js is definitively a show stopper : that means
> I'll have to tackle the node-unicode-* packages issue sooner than I
> expected :-/
>
> Snark on #debian-js



Bug#872866: wily: Appears to contain non-free code

2017-08-21 Thread Jacob Adams
Package: wily
Version: 0.13.33-2
Severity: serious
Justification: 2.1.1

According to wily's debian/copyright the entire work is licensed under the 
Artistic License.
However, according the files in libframe and libXg appear to be proprietary:

/* Copyright (c) 1992 AT - All rights reserved. */

At bare minimum debian/copyright has to be updated with the correct license for 
these files.
If they are actually proprietary as they appear, this package should be removed 
from Debian.

Given the current state of the wily package, I suspect no one will ever respond 
to this bug.
Therefore, the severity is higher than it probably should be for a simple 
d/copyright mistake.
(assuming those files aren't actually proprietary)

However, I've found several copies of this library online in other projects and 
they contain the
same or slightly different (1998 Lucent Technologies) copyright notices. 

I would rather not remove working software from Debian, but it really seems 
like this package is non-free.

Sorry,
Jacob



Bug#759725: postgresql-common: non-synchronous service postgresql stop

2017-08-21 Thread Ludovic Gasc
Hi,

I confirm the problem when you have a systemd service with postgresql
dependency.
In case you have a big database to start, you will have race conditions
with the dependant services.
Tested with Debian Stretch.

Apparently, postgresql has now a sd_notify integration:
https://www.postgresql.org/docs/9.6/static/server-start.html

But it's with postgres process directly, not with pg_ctlcluster.

Is it planned to have an integration with sd_notify in pg_ctlcluster ?

Thanks for your response.


Bug#872687: xfce4-pulseaudio-plugin: Unable to click or use volume slider

2017-08-21 Thread Unit 193

Howdy,

This is not a bug specific to xfce4-pulseaudio-plugin but to GTK+3.  You can see 
upstream reports in GTK+3[1], Xfce[2], and even one over at Arch[3].


If you apply the simple patch by Carlos Garnacho and rebuild GTK+3 you will no 
longer have this issue.



[1]: https://bugzilla.gnome.org/show_bug.cgi?id=786029
[2]: https://bugzilla.xfce.org/show_bug.cgi?id=13770
[3]: https://bugs.archlinux.org/task/55114


~Unit 193
Unit193 @ Freenode
Unit193 @ OFTC



Bug#872503: ffmpeg: armhf SIGBUS in ff_diff_pixels_armv6 running winff autopkgtest

2017-08-21 Thread Carl Eugen Hoyos
Michael has committed a patch that is supposed to fix this crash:
http://ffmpeg.org/pipermail/ffmpeg-cvslog/2017-August/108709.html

Thank you for the useful report!

Carl Eugen



Bug#872753: RFS: node-regjsparser/0.2.1-1 ITP

2017-08-21 Thread Julien Puydt
Hi,

Le 21/08/2017 à 22:44, roucaries bastien a écrit :
> On Mon, Aug 21, 2017 at 10:33 PM, roucaries bastien
>  wrote:
>> control: owner -1 ro...@debian.org
>>
>> Will sponsor this one. Will review
>>
>> On Sun, Aug 20, 2017 at 9:59 PM, Andrey Rahmatullin  wrote:
>>> Control: retitle -1 RFS: node-regjsparser/0.2.1-1 [ITP]
> 
> * uscan is now 4

Done.

> *demo should be supplied as example

I don't know how that demo is to be run, so I find it annoying to ship
it as an example :-/

Notice that the manpage I wrote has examples.

> * test/*.json should be remove FTBFS (if you could regenerate you are
> welcome to do)

Same question as for nodejsgen : if it isn't used, do we still consider
it FTBFS?

> * parser.js FTBFS search generated in source

Darn. I had checked that we had the tool to generate it in node-esprima,
but now I see it requires node-unicode-8.0.0, which we don't have :-(

> * a smoketest will be welcome (readme.md seems to include something)

I added one.

The problem with parser.js is definitively a show stopper : that means
I'll have to tackle the node-unicode-* packages issue sooner than I
expected :-/

Snark on #debian-js



Bug#855346: (no subject)

2017-08-21 Thread Michael Biebl
bringing the apparmor team into the loop here.

They might want to usertag this bug accordingly and maybe can provide
some help/input.

Fwiw, I can confirm that opening attachments from TB with AA active is
currently broken e.g. for PDF files. My PDF viewer is evince.

Michael

On Sat, 20 May 2017 10:13:42 +0200 Carsten Schoenert
 wrote:
> Hello Ulrike,
> 
> I just wanted to ping on this again. Some useful news on this issue?
> 
> Regards
> Carsten
> 
> On Tue, Mar 28, 2017 at 08:21:12PM +0200, Carsten Schoenert wrote:
> > Hello Ulrike,
> > 
> > On Sat, Mar 18, 2017 at 04:12:00PM +, u wrote:
> > > Sorry for writing three emails for one problem..
> > > 
> > > I forgot to mention that if the upstream patch gets integrated, we would
> > > need to copy this into the Debian AppArmor profile too.
> > 
> > we preparing a new upload of Thunderbird 45.8.0.
> > We can simply adopt this commit and close this report by a upload?
> > https://git.launchpad.net/~u-d/apparmor-profiles/commit/?id=a8b1ce686aa1b40f40baa2f12228586b398f6302
> > 
> > Regards
> > Carsten
> 
> 

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



signature.asc
Description: OpenPGP digital signature


Bug#872865: libtecla: gl_get_line() fails to detect EOF

2017-08-21 Thread Guido Berhoerster
Package: libtecla1
Version: 1.6.3-1
Severity: normal
File: libtecla
Tags: patch upstream

gl_get_line() in server mode will errenously fail to detect an EOF
condition when reading from a fd which is not a tty and return
GL_READ_BLOCKED indefinetly. The bug is in gl_read_unmasked() which
calls isatty() before checking the errno from the read() call and
thereby clobbering errno if the fd in fact does not refer to a tty.
I've tried to contact upstream but the email address in the docs and
on the homepage bounces. A patch fixing the issue is attached.

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

Kernel: Linux 4.4.0-89-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set 
LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE=en_US.UTF-8 (charmap=locale: Cannot set LC_ALL to default 
locale: No such file or directory
UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libtecla1 depends on:
ii  libc6  2.24-11+deb9u1

libtecla1 recommends no packages.

libtecla1 suggests no packages.

-- debconf information excluded
--- libtecla.orig/getline.c 2013-09-12 07:04:00.0 +
+++ libtecla/getline.c  2017-08-21 14:40:39.248681309 +
@@ -3296,6 +3296,7 @@
 static GlReadStatus gl_read_unmasked(GetLine *gl, int fd, char *c)
 {
   int nread;  /* The return value of read() */
+  int saved_errno;
 /*
  * Unblock the signals that we are trapping, while waiting for I/O.
  */
@@ -3307,6 +3308,7 @@
   do {
 errno = 0;
 nread = read(fd, c, 1);
+saved_errno = errno;
   } while(nread < 0 && errno==EINTR);
 /*
  * Block all of the signals that we are trapping.
@@ -3319,7 +3321,7 @@
   case 1:
 return GL_READ_OK;
   case 0:
-return (isatty(fd) || errno != 0) ? GL_READ_BLOCKED : GL_READ_EOF;
+return (isatty(fd) || saved_errno != 0) ? GL_READ_BLOCKED : GL_READ_EOF;
   default:
 return GL_READ_ERROR;
   };


Bug#872755: [ibus-gtk3] Installation causes libgtk-3-dev Debian archive builds to fail?

2017-08-21 Thread OmegaPhil
On 21/08/17 22:15, Osamu Aoki wrote:
> On Mon, Aug 21, 2017 at 08:28:14PM +0100, OmegaPhil wrote:
> ...
>> I'm building the libgtk-3-dev Debian source package with the usual
>> 'dpkg-buildpackage -b --jobs=auto -i.*' (the bit at the end is to ignore
>> changes so that I can trivially patch in my own stuff). The current
>> situation happens without any changes.
> 
> Oh, I overlooked and misunderstood your position.  Did you check symbol
> file situation and made proper library versioning.
> 
> If you build your own libgtk-3-dev  you must have used
> wrong compilation option which caused to skip some wayland function
> generation.  This is your problem.  Check your compile option.  Run
> ./configure by yourself.
> 
> If ibus compile failes with libgtk-3-dev in unstable, I need to rebuild
> ibus against updated libgtk-3-dev for unstable.  Maybe I need to do
> this.  But if there is symbol change, library versioning scheme should
> help prevent it if library is packaged properly.
> 
> Anyway, then this isn't a bug on my package.
> 
> Good luck with experimenting with compiler.  I don't have time to help
> your local experiment.
> 
> Osamu


It shouldn't be possible for me to use the wrong compilation option -
the configuration is defined in the Debian rules file.

OK, if you think this is something local, I can't argue against that
since I don't have enough experience. In terms of a library versioning
issue, ibus-gtk3 is after libgtk-3-0 (>= 3.9.10) which is of course
satisfied.

For anyone else interested, you can test for the problem with:



apt-get source libgtk-3-dev
cd 
dpkg-buildpackage -b --jobs=auto



The build takes a long time but will eventually reach the testing stage,
where the bug previously mentioned appears.

In the meantime I'm building in a VM with ibus-gtk3 removed.



signature.asc
Description: OpenPGP digital signature


Bug#872807: [pkg-go] Bug#872807: Bug#872807: Bug#872807: dh-make-golang: Please find dependencies based on Homepage, too

2017-08-21 Thread Tianon Gravi
On 21 August 2017 at 14:11, Michael Hudson-Doyle
 wrote:
> On 22 August 2017 at 01:17, Paul R. Tagliamonte  wrote:
>> Why not use the import path I so lovingly put in the generated control
>> file for times like these?
>
> That's still missing from heaps of packages, isn't it? I know someone who
> likes writing scripts to fix lots of golang packages at once...

Also, some packages include multiple import paths, usually via a
symlink.  These are often the result of a rename, or of two imports
for the same project (ala, "github.com/foo/bar" and
"gopkg.in/foo/bar.vN"), so it might be worth considering making that a
list instead of simply a single package path.


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4



Bug#872828: RFS: node-regjsgen/0.3.0-1 ITP

2017-08-21 Thread Julien Puydt
Re,

Le 21/08/2017 à 22:31, Bastien ROUCARIES a écrit :
> Will sponsor

Thanks!

> On Mon, Aug 21, 2017 at 10:25 PM, Bastien ROUCARIES
>  wrote:
>> control: owner -1 ro...@debian.org
>>
>> On Mon, Aug 21, 2017 at 9:52 PM, Julien Puydt  
>> wrote:
>>> Hi,
>>>
>>> Le 21/08/2017 à 20:54, Bastien Roucaries a écrit :
>   Section : web

 Section: JavaScript
>>>
>>> Changed.
>>>
>>> Snark on #debian-js
>>>
> 
> Some remark:
> - watch is now version 4

Ok -- I'll have to check what goodies there are in this version.

> - copyright only 2017 and one author what give git log about year and author ?

The logs show Benjamin Tan and small contributions from Mathias Bynens.
I pushed a change on the dates.

> - test data json does not build from source. This need a repack (use
> copyright file excluded and uscan. It is free but FTBFS so add +ds
> suffix)

Are you sure? The tests/ directory isn't used at all by my packaging, so
it shouldn't be a FTBFS.

> - a small smoke test supplied as example and run will help

I added debian/tests/compose and debian/example.js (shipped in
/usr/share/doc/node-regjsgen).

Snark on #debian-js



Bug#750946: Update on the upstream side

2017-08-21 Thread Kjetil Kjernsmo
Hi all!

Greg has made a patch and a pull request:
https://github.com/tobyink/p5-html-html5-parser/pull/3
but so far, we haven't heard from the main developer.

Also, as you can see, the patch is met with some resistance, so we're not 
really sure how to solve this now...

Meanwhile, we should relax the relationships between this module and the 
RDF toolchain. The HTML parser really is somewhat on the outskirts and 
isn't a dependency to any of it, so it shouldn't have that far-reaching 
consequences.

Cheers,

Kjetil



Bug#872807: [pkg-go] Bug#872807: Bug#872807: dh-make-golang: Please find dependencies based on Homepage, too

2017-08-21 Thread Michael Hudson-Doyle
On 22 August 2017 at 01:17, Paul R. Tagliamonte  wrote:

> Why not use the import path I so lovingly put in the generated control
> file for times like these?
>

That's still missing from heaps of packages, isn't it? I know someone who
likes writing scripts to fix lots of golang packages at once...

Cheers,
mwh



> On Aug 21, 2017 9:12 AM, "Balint Reczey" 
> wrote:
>
>> Package: dh-make-golang
>> Version: 0.0~git20170703.0.5eaf198-2
>> Severity: wishlist
>>
>> Dead Maintainer,
>>
>> When looking for packaged build-dependencies the vendor's path
>> (github.com/onsi/ginkgo) is converted using the default go library
>> naming scheme
>> (to golang-github-onsi-ginkgo-dev) which package may not exist in
>> Debian but may exist under a different name
>> (golang-github-ginkgo-dev).
>>
>> In case the build-dependency does not exist in Debian as a package
>> following the
>> standard go naming scheme dh-make-golang could look for it under a
>> different name using the Homepage field of the packages:
>>
>> $ grep-dctrl -FHomepage github.com/onsi/ginkgo -sPackage \
>>  /var/lib/apt/lists/*Packages | sort | uniq
>> Package: golang-ginkgo-dev
>>
>> Cheers,
>> Balint
>>
>>
>> --
>> Balint Reczey
>> Debian & Ubuntu Developer
>>
>> ___
>> Pkg-go-maintainers mailing list
>> pkg-go-maintain...@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-
>> go-maintainers
>>
>
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>


Bug#872864: Checkout upstream signatures as well when using pristine-tar

2017-08-21 Thread Guido Günther
Package: git-buildpackage
Version: 0.9.0~exp4~2.gbpa7b96a
Severity: wishlist

We should checkout the upstream signatures from the pristine-tar branch
as well.

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

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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)

Versions of packages git-buildpackage depends on:
ii  devscripts 2.17.9
ii  git1:2.14.0-1
ii  man-db 2.7.6.1-2
ii  python33.5.3-3
ii  python3-dateutil   2.6.0-1
ii  python3-pkg-resources  36.0.1-1
ii  python3-six1.10.0-4

Versions of packages git-buildpackage recommends:
ii  cowbuilder0.85
ii  pbuilder  0.228.7
ii  pristine-tar  1.40
ii  python3-requests  2.12.4-1
ii  sbuild0.73.0-4

Versions of packages git-buildpackage suggests:
ii  python3-notify2  0.3-3
ii  sudo 1.8.20p2-1
ii  unzip6.0-21

-- no debconf information



Bug#872863: /usr/bin/dh_sphinxdoc: fails to detect 'singlehtml' docs

2017-08-21 Thread Sean Whitton
Package: sphinx-common
Version: 1.5.6-2
Severity: normal
File: /usr/bin/dh_sphinxdoc
control: affects -1 debian-policy

Dear maintainers,

dh_sphinxdoc cannot find output generating using Sphinx's 'singlehtml'
target.  I tried passing the directory containing my documentation to
dh_sphinxdoc, but it complained that the directory does not contain any
Sphinx documentation.

For a sample of singlehtml output, see
/usr/share/doc/debian-policy/policy.html/ (a directory).

Thanks!

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

Kernel: Linux 4.12.0-1-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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sphinx-common depends on:
ii  libjs-sphinxdoc  1.5.6-2

Versions of packages sphinx-common recommends:
ii  python3-sphinx  1.5.6-2

sphinx-common suggests no packages.

-- no debconf information

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#763040: npm: "npm help " is broken

2017-08-21 Thread Roland Hieber
Package: npm
Version: 1.4.21+ds-2
Followup-For: Bug #763040

Huh, funny. I have here two systems, both systems are running
npm-1.4.21+ds-2.

The first system is running Debian GNU/Linux 9.1 (stretch), there the
bug does not happen, because there are the right symlinks in
/usr/share/man/man1.

On this system where I'm writing this mail, running Debian GNU/Linux
testing (buster), the bug _does_ happen, because the symlinks are
missing, even after a aptitude reinstall npm.

 - Roland

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

Kernel: Linux 4.11.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.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)

Versions of packages npm depends on:
ii  node-abbrev   1.0.9-1
ii  node-ansi 0.3.0-2
ii  node-ansi-color-table 1.0.0-1
ii  node-archy1.0.0-1
ii  node-block-stream 0.0.9-1
ii  node-fstream  1.0.10-1
ii  node-fstream-ignore   0.0.6-2
ii  node-github-url-from-git  1.4.0-1
ii  node-glob 7.1.1-1
ii  node-graceful-fs  4.1.11-1
ii  node-gyp  3.4.0-1
ii  node-inherits 2.0.3-1
ii  node-ini  1.1.0-1
ii  node-lockfile 0.4.1-1
ii  node-lru-cache4.0.2-1
ii  node-minimatch3.0.3-1
ii  node-mkdirp   0.5.0-1
ii  node-nopt 3.0.6-3
ii  node-npmlog   0.0.4-1
ii  node-once 1.4.0-2
ii  node-osenv0.1.0-1
ii  node-read 1.0.7-1
ii  node-read-package-json1.2.4-1
ii  node-request  2.26.1-1
ii  node-retry0.6.0-1
ii  node-rimraf   2.5.4-3
ii  node-semver   5.3.0-1
ii  node-sha  1.2.3-1
ii  node-slide1.1.4-1
ii  node-tar  2.2.1-1
ii  node-underscore   1.8.3~dfsg-1
ii  node-which1.2.11-1
ii  nodejs4.8.4~dfsg-1

npm recommends no packages.

npm suggests no packages.

-- debconf-show failed



Bug#872079: libwine32 will not install

2017-08-21 Thread Antoine
Right now there is a discrepancy between amd64 and i386 versions of
libc6 in Sid:

$ apt policy libc6:{amd64,i386}
libc6:
  Installé : 2.24-14
  Candidat : 2.24-15
 Table de version :
 2.25-0experimental1 1
  1 http://mirror.grifon.fr/debian experimental/main amd64 Packages
 2.24-15 500
500 http://mirror.grifon.fr/debian unstable/main amd64 Packages
 *** 2.24-14 500
500 http://mirror.grifon.fr/debian testing/main amd64 Packages
100 /var/lib/dpkg/status
 2.24-11+deb9u1 500
500 http://mirror.grifon.fr/debian stable/main amd64 Packages
500 http://mirror.grifon.fr/debian-security stable/updates/main
amd64 Packages
libc6:i386:
  Installé : 2.24-14
  Candidat : 2.24-14
 Table de version :
 *** 2.24-14 500
500 http://mirror.grifon.fr/debian testing/main i386 Packages
500 http://mirror.grifon.fr/debian unstable/main i386 Packages
100 /var/lib/dpkg/status
 2.24-11+deb9u1 500
500 http://mirror.grifon.fr/debian stable/main i386 Packages
500 http://mirror.grifon.fr/debian-security stable/updates/main
i386 Packages

I’m pretty sure this is the reason you can’t install the i386 version of
WINE, and you probably won’t be able to install any i386 package right now.

A simple workaround would be to add buster/testing repositories to your
APT sources, and install the 2.24-14 version of libc6:amd64 and
libc6:i386. Some libc6-related packages might need to be downgraded to
2.24-14 too.

By the way, this means this bug report is actually unrelated to WINE itself.



signature.asc
Description: OpenPGP digital signature


Bug#872862: linux-image-4.11.0-0.bpo.1-amd64: It would be good if CONFIG_LEDS_BRIGHTNESS_HW_CHANGED were enabled

2017-08-21 Thread Daniel Silverstone
Package: src:linux
Version: 4.11.6-1~bpo9+1
Severity: wishlist

Dear Maintainer,

With kernel 4.11, a feature has been added which allows the LED drivers to
indicate why a change in value has occurred.  Including allowing the userland
to know if it was a software or a hardware event which made the brightness
change.  This would be super-useful to have, especially when trying to write
tooling to manage keyboard backlights on modern thinkpads.

I believe the tpacpi driver has been updated to support this feature, so all
which would be required from the kernel maintainers would be to enable the
feature CONFIG_LEDS_BRIGHTNESS_HW_CHANGED and then, ideally, upload a new
backport :-)

Thanks,

Daniel.

(I'll leave this stuff in, even though it's not really necessary, it might be
of interest to someone looking at modern thinkpad support ;-)

-- Package-specific info:
** Version:
Linux version 4.11.0-0.bpo.1-amd64 (debian-ker...@lists.debian.org) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.11.6-1~bpo9+1 
(2017-07-09)

** Command line:
BOOT_IMAGE=/vmlinuz-4.11.0-0.bpo.1-amd64 root=/dev/mapper/pn-root ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 20J6CT01WW
product_version: ThinkPad T470p
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: R0FET33W (1.13 )
board_vendor: LENOVO
board_name: 20J6CT01WW
board_version: 0B98417 WIN

** Loaded modules:
rfcomm
ctr
ccm
xt_CHECKSUM
iptable_mangle
ipt_MASQUERADE
nf_nat_masquerade_ipv4
iptable_nat
nf_nat_ipv4
nf_nat
nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack
nf_conntrack
libcrc32c
ipt_REJECT
nf_reject_ipv4
xt_tcpudp
tun
bridge
stp
llc
ebtable_filter
ebtables
ip6table_filter
ip6_tables
iptable_filter
cmac
bnep
cpufreq_powersave
cpufreq_conservative
cpufreq_userspace
bbswitch(O)
nls_ascii
nls_cp437
vfat
fat
snd_hda_codec_hdmi
snd_hda_codec_realtek
snd_hda_codec_generic
arc4
iwlmvm
intel_rapl
mac80211
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
kvm
i915
irqbypass
uvcvideo
intel_cstate
videobuf2_vmalloc
iwlwifi
videobuf2_memops
videobuf2_v4l2
snd_hda_intel
intel_uncore
videobuf2_core
drm_kms_helper
snd_hda_codec
rtsx_pci_ms
videodev
snd_hda_core
btusb
memstick
intel_rapl_perf
media
efi_pstore
snd_hwdep
cfg80211
joydev
btrtl
evdev
drm
snd_pcm
snd_timer
mei_me
i2c_algo_bit
efivars
shpchp
serio_raw
pcspkr
mei
intel_pch_thermal
iTCO_wdt
iTCO_vendor_support
hci_uart
btbcm
btqca
btintel
wmi
thinkpad_acpi
bluetooth
nvram
battery
snd
ac
soundcore
rfkill
video
intel_lpss_acpi
intel_lpss
button
acpi_pad
parport_pc
ppdev
lp
parport
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
jbd2
crc32c_generic
fscrypto
ecb
mbcache
algif_skcipher
af_alg
dm_crypt
dm_mod
hid_generic
usbhid
rtsx_pci_sdmmc
mmc_core
crct10dif_pclmul
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
pcbc
aesni_intel
aes_x86_64
crypto_simd
glue_helper
cryptd
psmouse
e1000e
ptp
pps_core
i2c_i801
xhci_pci
nvme
xhci_hcd
nvme_core
rtsx_pci
mfd_core
usbcore
usb_common
thermal
i2c_hid
hid

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5910] (rev 05)
Subsystem: Lenovo Device [17aa:505d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) 
[8086:1901] (rev 05) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:01.2 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x4) 
[8086:1909] (rev 05) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:591b] 
(rev 04) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:505e]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller [8086:a12f] (rev 31) (prog-if 

Bug#872846: temporarily readd POT-Creation-Date

2017-08-21 Thread Santiago Vila
On Mon, Aug 21, 2017 at 09:51:36PM +0200, Helmut Grohne wrote:
> Package: gettext
> Version: 0.19.8.1-3
> Severity: serious
> Justification: glibc ftbfs
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> The removal of POT-Creation-Date (#792687) is a nice thing to do, but
> the archive isn't quite ready for it.
> 
>  * glibc FTBFS https://sourceware.org/bugzilla/show_bug.cgi?id=21508 and
>no patch is available as of this writing.

In fact, breaking other packages is hardly a good reason to revert the
change.

Consider the example of GCC 7. There are lots of packages that FTBFS
because of new GCC 7, and I'm sure that a lot of them without patches
as well, but this was never a reason not to upload GCC 7 for unstable
or to revert the fact that we made GCC 7 the default gcc.

We never said "the archive is not ready for it" for GCC 7,
why this small change in gettext should be different?

Please reassign and merge when you report the bug against glibc.
This is not a bug in gettext, it's a bug in glibc at most.

Thanks.



Bug#872861: ITP: node-gulp-mocha -- Run Mocha tests

2017-08-21 Thread Bastien ROUCARIES
Package: wnpp
Severity: wishlist
Owner: ro...@debian.org
X-Debbugs-CC: debian-de...@lists.debian.org
control: block -1 by 855469

* Package name: node-gulp-mocha
  Version : 4.3.1
  Upstream Author : Sindre Sorhus  (sindresorhus.com)
* URL : https://github.com/sindresorhus/gulp-mocha#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Run Mocha tests

This module allows one to use gulp toolkit to run mocha test.
.
Mocha is a feature-rich JavaScript test framework running
on Node.js and browser, making asynchronous testing
simple.
.
gulp is a toolkit that helps you automate painful or time-consuming tasks in
 your development workflow.



Bug#866741: offer debug output

2017-08-21 Thread c.buhtz
Can you offer the debug output please?

Start backintime from comanndline.

backintime-qt --debug



Bug#872860: csound FTBFS with libgmm++-dev 5.2+dfsg1-5

2017-08-21 Thread Adrian Bunk
Source: csound
Version: 1:6.09.1~dfsg-1
Severity: serious

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

...
/build/1st/csound-6.09.1~dfsg/Opcodes/linear_algebra.cpp: In member function 
'int la_i_print_vr_t::init(CSOUND*)':
/build/1st/csound-6.09.1~dfsg/Opcodes/linear_algebra.cpp:633:12: error: no 
match for 'operator<<' (operand types are 'std::ostringstream {aka 
std::__cxx11::basic_ostringstream}' and 'std::vector')
 stream << array->vr << std::endl;
 ~~~^~~~
In file included from /usr/include/c++/7/istream:39:0,
 from /usr/include/c++/7/sstream:38,
 from /usr/include/c++/7/complex:45,
 from 
/build/1st/csound-6.09.1~dfsg/Opcodes/linear_algebra.cpp:345:
/usr/include/c++/7/ostream:108:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>::__ostream_type& std::basic_ostream<_CharT, 
_Traits>::operator<<(std::basic_ostream<_CharT, _Traits>::__ostream_type& 
(*)(std::basic_ostream<_CharT, _Traits>::__ostream_type&)) [with _CharT = char; 
_Traits = std::char_traits; std::basic_ostream<_CharT, 
_Traits>::__ostream_type = std::basic_ostream]
   operator<<(__ostream_type& (*__pf)(__ostream_type&))
   ^~~~
/usr/include/c++/7/ostream:108:7: note:   no known conversion for argument 1 
from 'std::vector' to 'std::basic_ostream::__ostream_type& 
(*)(std::basic_ostream::__ostream_type&) {aka std::basic_ostream& 
(*)(std::basic_ostream&)}'
/usr/include/c++/7/ostream:117:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>::__ostream_type& std::basic_ostream<_CharT, 
_Traits>::operator<<(std::basic_ostream<_CharT, _Traits>::__ios_type& 
(*)(std::basic_ostream<_CharT, _Traits>::__ios_type&)) [with _CharT = char; 
_Traits = std::char_traits; std::basic_ostream<_CharT, 
_Traits>::__ostream_type = std::basic_ostream; std::basic_ostream<_CharT, 
_Traits>::__ios_type = std::basic_ios]
   operator<<(__ios_type& (*__pf)(__ios_type&))
   ^~~~
/usr/include/c++/7/ostream:117:7: note:   no known conversion for argument 1 
from 'std::vector' to 'std::basic_ostream::__ios_type& 
(*)(std::basic_ostream::__ios_type&) {aka std::basic_ios& 
(*)(std::basic_ios&)}'
/usr/include/c++/7/ostream:127:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>::__ostream_type& std::basic_ostream<_CharT, 
_Traits>::operator<<(std::ios_base& (*)(std::ios_base&)) [with _CharT = char; 
_Traits = std::char_traits; std::basic_ostream<_CharT, 
_Traits>::__ostream_type = std::basic_ostream]
   operator<<(ios_base& (*__pf) (ios_base&))
   ^~~~
/usr/include/c++/7/ostream:127:7: note:   no known conversion for argument 1 
from 'std::vector' to 'std::ios_base& (*)(std::ios_base&)'
/usr/include/c++/7/ostream:166:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>::__ostream_type& std::basic_ostream<_CharT, _Traits>::operator<<(long 
int) [with _CharT = char; _Traits = std::char_traits; 
std::basic_ostream<_CharT, _Traits>::__ostream_type = std::basic_ostream]
   operator<<(long __n)
   ^~~~
/usr/include/c++/7/ostream:166:7: note:   no known conversion for argument 1 
from 'std::vector' to 'long int'
/usr/include/c++/7/ostream:170:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>::__ostream_type& std::basic_ostream<_CharT, _Traits>::operator<<(long 
unsigned int) [with _CharT = char; _Traits = std::char_traits; 
std::basic_ostream<_CharT, _Traits>::__ostream_type = std::basic_ostream]
   operator<<(unsigned long __n)
   ^~~~
/usr/include/c++/7/ostream:170:7: note:   no known conversion for argument 1 
from 'std::vector' to 'long unsigned int'
/usr/include/c++/7/ostream:174:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>::__ostream_type& std::basic_ostream<_CharT, _Traits>::operator<<(bool) 
[with _CharT = char; _Traits = std::char_traits; 
std::basic_ostream<_CharT, _Traits>::__ostream_type = std::basic_ostream]
   operator<<(bool __n)
   ^~~~
/usr/include/c++/7/ostream:174:7: note:   no known conversion for argument 1 
from 'std::vector' to 'bool'
In file included from /usr/include/c++/7/ostream:693:0,
 from /usr/include/c++/7/istream:39,
 from /usr/include/c++/7/sstream:38,
 from /usr/include/c++/7/complex:45,
 from 
/build/1st/csound-6.09.1~dfsg/Opcodes/linear_algebra.cpp:345:
/usr/include/c++/7/bits/ostream.tcc:91:5: note: candidate: 
std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT, 
_Traits>::operator<<(short int) [with _CharT = char; _Traits = 
std::char_traits]
 basic_ostream<_CharT, _Traits>::
 ^~
/usr/include/c++/7/bits/ostream.tcc:91:5: note:   no known conversion for 
argument 1 from 'std::vector' to 'short int'
In file included from /usr/include/c++/7/istream:39:0,
 from /usr/include/c++/7/sstream:38,
 from /usr/include/c++/7/complex:45,
 from 

Bug#872753: RFS: node-regjsparser/0.2.1-1 ITP

2017-08-21 Thread roucaries bastien
On Mon, Aug 21, 2017 at 10:33 PM, roucaries bastien
 wrote:
> control: owner -1 ro...@debian.org
>
> Will sponsor this one. Will review
>
> On Sun, Aug 20, 2017 at 9:59 PM, Andrey Rahmatullin  wrote:
>> Control: retitle -1 RFS: node-regjsparser/0.2.1-1 [ITP]

* uscan is now 4
*demo should be supplied as example
* test/*.json should be remove FTBFS (if you could regenerate you are
welcome to do)
* parser.js FTBFS search generated in source
* a smoketest will be welcome (readme.md seems to include something)

Bastien



Bug#872846: temporarily readd POT-Creation-Date

2017-08-21 Thread Santiago Vila
On Mon, Aug 21, 2017 at 09:51:36PM +0200, Helmut Grohne wrote:
> Package: gettext
> Version: 0.19.8.1-3
> Severity: serious
> Justification: glibc ftbfs
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> The removal of POT-Creation-Date (#792687) is a nice thing to do, but
> the archive isn't quite ready for it.
> 
>  * glibc FTBFS https://sourceware.org/bugzilla/show_bug.cgi?id=21508 and
>no patch is available as of this writing.

That's a bug in an upstream bug tracker.

Does our glibc also FTBFS for the same reason? Where is the Debian bug number?

The way I read the upstream bug report: "tst-gettext fails", it does
not seem the kind of bug which is difficult to fix.

>  * The commit changes .mo files and thus breaks M-A:sameness allover the
>archive, e.g. #872806. Likely all packages shipping .mo files in
>M-A:same packages are affected. The multiarch database on delfin.d.o
>gives a clue:

The commit does not really change any existing .mo file in the archive.

It just makes the .mo files to be different when you rebuild the
package. But in general this is supposed to happen at the same time
in all architectures, triggered by a new Debian revision.

Moreover: How many of those in the list do not also violate Debian policy 
section 8.2?

Also, bug #872806 does not seem a good example to me, because the library
should not contain unversioned .mo files to begin with.

So, if I have to revert, I will do, but so far I don't see this is a
catastrophic failure that requires a reversion.

Thanks.



Bug#872859: kate: fails to build against libgit2 0.26.0

2017-08-21 Thread Russell Sim
Package: kate
Version: 4:16.08.2-1
Severity: normal

Dear Maintainer,

Currently Kate fails to build against libgit2 0.26.0 which has just been
uploaded to experimental. Please consider updating Kates dependencies to see if
it will sucessfuly build against this newer version.

>From what I can see, support for libgit2 has been removed from Kates master
branch because it was deemed to be too unstable, so you may be able to backport
that patch if it's too troublesome getting it to build against 0.26.0.

Thanks,
Russell



-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages kate depends on:
ii  kate5-data   4:16.08.3-1
ii  ktexteditor-katepart 5.27.0-1
ii  libc62.24-11
ii  libgit2-24   0.25.1+really0.24.6-1
ii  libkf5activities55.27.0-1
ii  libkf5bookmarks5 5.27.0-1
ii  libkf5completion55.27.0-1
ii  libkf5configcore55.27.0-1
ii  libkf5configgui5 5.27.0-1
ii  libkf5configwidgets5 5.27.0-1
ii  libkf5coreaddons55.27.0-1
ii  libkf5crash5 5.27.0-1
ii  libkf5dbusaddons55.27.0-1
ii  libkf5guiaddons5 5.27.0-1
ii  libkf5i18n5  5.27.0-2
ii  libkf5iconthemes55.27.0-1
ii  libkf5itemmodels55.27.0-1
ii  libkf5jobwidgets55.27.0-1
ii  libkf5kiocore5   5.27.0-2
ii  libkf5kiofilewidgets55.27.0-2
ii  libkf5kiowidgets55.27.0-2
ii  libkf5newstuff5  5.28.0-1
ii  libkf5parts5 5.28.0-1
ii  libkf5plasma55.28.0-2
ii  libkf5service-bin5.27.0-1
ii  libkf5service5   5.27.0-1
ii  libkf5texteditor55.28.0-2
ii  libkf5textwidgets5   5.27.0-1
ii  libkf5threadweaver5  5.27.0-1
ii  libkf5wallet-bin 5.27.0-1
ii  libkf5wallet55.27.0-1
ii  libkf5widgetsaddons5 5.27.0-1
ii  libkf5windowsystem5  5.27.0-1
ii  libkf5xmlgui55.27.0-1
ii  libqt5core5a 5.7.1+dfsg-3+b1
ii  libqt5dbus5  5.7.1+dfsg-3+b1
ii  libqt5gui5   5.7.1+dfsg-3+b1
ii  libqt5sql5   5.7.1+dfsg-3+b1
ii  libqt5widgets5   5.7.1+dfsg-3+b1
ii  libqt5xml5   5.7.1+dfsg-3+b1
ii  libstdc++6   6.3.0-18
ii  plasma-framework 5.28.0-2
ii  qml-module-org-kde-kquickcontrolsaddons  5.27.0-1
ii  qml-module-qtquick-layouts   5.7.1-2+b2
ii  qml-module-qtquick2  5.7.1-2+b2

kate recommends no packages.

Versions of packages kate suggests:
ii  aspell 0.60.7~20110707-3+b2
ii  ispell 3.4.00-5
pn  khelpcenter
pn  konsole-kpart  

-- no debconf information



Bug#872858: backintime-qt: python3-pyqt5 removed because of transistions

2017-08-21 Thread Christian Buhtz
Package: backintime-qt
Version: 1.2.0~alpha0
Severity: important

Dear Maintainer,

in the current unstable/sid version of Debian GNU/Linux backintime will be
removed by an update/upgrade because python3-pyqt5 is removed because of three
open transistions.

The process is to complex for me. I don't understand it completly. Can we do
here something?



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

Kernel: Linux 4.12.8-towo.1-siduction-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages backintime-qt depends on:
ii  backintime-common1.2.0~alpha0
ii  libnotify-bin0.7.7-2
ii  policykit-1  0.105-18
ii  python3  3.5.3-3
ii  python3-dbus.mainloop.pyqt5  5.7+dfsg-5+b1
ii  python3-pyqt55.7+dfsg-5+b1
ii  x11-utils7.7+3+b1

Versions of packages backintime-qt recommends:
ii  python3-secretstorage  2.3.1-2

Versions of packages backintime-qt suggests:
ii  meld  3.16.4-1

-- no debconf information



Bug#867617: Should be ok

2017-08-21 Thread Julien Puydt
control: tags -1 -moreinfo

I pushed dh compat to 10 and d/copyright already uses https.

Snark on #debian-js



Bug#872753: RFS: node-regjsparser/0.2.1-1 ITP

2017-08-21 Thread roucaries bastien
control: owner -1 ro...@debian.org

Will sponsor this one. Will review

On Sun, Aug 20, 2017 at 9:59 PM, Andrey Rahmatullin  wrote:
> Control: retitle -1 RFS: node-regjsparser/0.2.1-1 [ITP]
>
> --
> WBR, wRAR



Bug#816197: close

2017-08-21 Thread c.buhtz
Please close this bug because it is fixed.



Bug#872828: RFS: node-regjsgen/0.3.0-1 ITP

2017-08-21 Thread Bastien ROUCARIES
Will sponsor

On Mon, Aug 21, 2017 at 10:25 PM, Bastien ROUCARIES
 wrote:
> control: owner -1 ro...@debian.org
>
> On Mon, Aug 21, 2017 at 9:52 PM, Julien Puydt  
> wrote:
>> Hi,
>>
>> Le 21/08/2017 à 20:54, Bastien Roucaries a écrit :
   Section : web
>>>
>>> Section: JavaScript
>>
>> Changed.
>>
>> Snark on #debian-js
>>

Some remark:
- watch is now version 4
- copyright only 2017 and one author what give git log about year and author ?
- test data json does not build from source. This need a repack (use
copyright file excluded and uscan. It is free but FTBFS so add +ds
suffix)
- a small smoke test supplied as example and run will help



Bug#872824: ITP: node-regjsgen -- Generate regular expression in Node.js

2017-08-21 Thread Julien Puydt
Hi,

Le 21/08/2017 à 22:22, Bastien ROUCARIES a écrit :
> On Mon, Aug 21, 2017 at 9:55 PM, Julien Puydt  
> wrote:
>
>> Does it look better:
>> Description: Regular expression from abstract syntax trees in Node.js
>>  This module accepts an abstract syntax tree representing a regular
>> expression
>>  (like the ones created by regjsparser, for example), and turns them into a
>>  regular expression string.
> .
>  This kind of process could be used for instance for creating [to fill
> but I suppose it it unicode sequence]

Uh, well, regular expressions are generally used to recognize things
more than creating anything... and I didn't define what an "abstract
syntax tree" is either :-/

I see the point of having a better description, but I don't think it
should be a complete course in computer science :-/

Snark on #debian-js



Bug#872857: gnuastro: fails to bulid against libgit 0.26.0

2017-08-21 Thread Russell Sim
Source: gnuastro
Severity: normal

Dear Maintainer,

Please consider investigating why gnuasto [1] won't build against libgit2
0.26.0 in experimental.

>From what I can see there are no newer versions with explicit support,  but it
may build anyway if the dependencies are updated.

Thanks,
Russell

1.
https://people.debian.org/~infinity0/libgit2/gnuastro_0.3.33-1_amd64-2017-08-01T12:02:23Z.build.xz



-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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



Bug#872824: ITP: node-regjsgen -- Generate regular expression in Node.js

2017-08-21 Thread Bastien ROUCARIES
On Mon, Aug 21, 2017 at 9:55 PM, Julien Puydt  wrote:
> Hi,
>
> Le 21/08/2017 à 18:34, Bastien Roucaries a écrit :
>
>>>  Description : Generate regular expression in Node.js
>>> This module can generate regular expressions from the abstract syntax
>>> trees
>>> created by regjsparser for example.
>>> .
>>> Node.js is an event-based server-side JavaScript engine.
>>
>> The long description does not carry more information than short. Could you 
>> improve
>>
>
> Does it look better:
> Description: Regular expression from abstract syntax trees in Node.js
>  This module accepts an abstract syntax tree representing a regular
> expression
>  (like the ones created by regjsparser, for example), and turns them into a
>  regular expression string.
.
 This kind of process could be used for instance for creating [to fill
but I suppose it it unicode sequence]
>  .
>  Node.js is an event-based server-side JavaScript engine.
>
> ?
>
> Snark on #debian-js



Bug#872828: RFS: node-regjsgen/0.3.0-1 ITP

2017-08-21 Thread Bastien ROUCARIES
control: owner -1 ro...@debian.org

On Mon, Aug 21, 2017 at 9:52 PM, Julien Puydt  wrote:
> Hi,
>
> Le 21/08/2017 à 20:54, Bastien Roucaries a écrit :
>>>   Section : web
>>
>> Section: JavaScript
>
> Changed.
>
> Snark on #debian-js
>



Bug#872849: [Debichem-devel] Bug#872849: psi4: Reconfigure libderiv for higher angular momentum

2017-08-21 Thread Michael Banck
Hi,

On Mon, Aug 21, 2017 at 10:02:07PM +0200, Georg wrote:
> Package: psi4
> Version: 1:1.0-1+b1
> Severity: normal
> 
> Dear Maintainer,
>* What led up to the situation?
> Running a KS/CC-PVQZ H2O computation with geometry optimisation
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> Applying the cc-pvqz basis set. Smaller sets (e. g. cc-pvtz or cc-pvdz) were 
> ok.

Thanks for the report. I can reproduce it here with the example
/usr/share/doc/psi4/examples/tu3-h2o-opt.dat and replacing "set basis
cc-pVDZ" with "set basis cc-pVQZ".

I agree that a geometry optimization of water at quadruple zeta level is
reasonable and this shouldn't crash. On the other hand, I think
quintuple zeta (i.e. cc-pV5Z) is not really general-purpose anymore and
having to recompile things would possibly be acceptable. We should
document this better, however.

This will needs to be changed in libint-dev though I believe, as we
changed psi4 not to use the internal copy of libint.


Michael



Bug#872824: ITP: node-regjsgen -- Generate regular expression in Node.js

2017-08-21 Thread Julien Puydt
Hi,

Le 21/08/2017 à 18:34, Bastien Roucaries a écrit :

>>  Description : Generate regular expression in Node.js
>> This module can generate regular expressions from the abstract syntax
>> trees
>> created by regjsparser for example.
>> .
>> Node.js is an event-based server-side JavaScript engine.
> 
> The long description does not carry more information than short. Could you 
> improve
> 

Does it look better:
Description: Regular expression from abstract syntax trees in Node.js
 This module accepts an abstract syntax tree representing a regular
expression
 (like the ones created by regjsparser, for example), and turns them into a
 regular expression string.
 .
 Node.js is an event-based server-side JavaScript engine.

?

Snark on #debian-js



Bug#872808: [debian-policy] nocheck DEB_BUILD_OPTIONS DEB_BUILD_PROFILES

2017-08-21 Thread roucaries bastien
On Mon, Aug 21, 2017 at 9:14 PM, Jonathan Nieder  wrote:
> Hi Bastien,
>
> Bastien ROUCARIÈS wrote:
>
>> I think the following patch is needed even if profiles are not fully 
>> specified.
>> Maybe an example about nodoc and help2man will also help. The nocheck should
>> check both BUILD_OPTIONS and BUILD_PROFILES. It will help when implementing 
>> as
>> policy profiles
>>
>> diff --git a/policy/ch-source.rst b/policy/ch-source.rst
>> index f706a13..d3d868c 100644
>> --- a/policy/ch-source.rst
>> +++ b/policy/ch-source.rst
>> @@ -465,7 +465,8 @@ The meaning of the following tags has been standardized:
>>
>>  ``nocheck``
>>  This tag says to not run any build-time test suite provided by the
>> -package.
>> +package. This tag could be also specified using
>> +   ``DEB_BUILD_PROFILES`` variable with nocheck flag
>>
>>  ``nodoc``
>>  This tag says to skip any build steps that only generate package
>> @@ -531,7 +532,7 @@ order to make it work for your package.
>>
>>  build:
>>  # ...
>> -ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
>> +ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS $DEB_BUILD_PROFILES)))
>>  # Code to run the package test suite.
>>  endif
>
> I am all for starting small in documenting build profiles (perhaps by
> documenting DEB_BUILD_PROFILES before the Build-Depends syntax) but it
> is possible to go too small.  This patch doesn't give context for what
> DEB_BUILD_PROFILES means and it makes policy harder to understand.
>
> In other words, if a patch
> - described what a build profile is
> - explained the DEB_BUILD_PROFILES environment variable
> - listed which values in that variable are required to be supported
>
> then that would already be enough for me to second it.  This patch
> doesn't do that.
>
> Do you mind if I merge this with bug#757760?

Feel free to do
>
> Thanks,
> Jonathan



Bug#872856: equivs: generates invalid install file when filename contains { or }

2017-08-21 Thread Juan Grigera
Package: equivs
Version: 2.1.0.1
Severity: normal

Dear Maintainer,

I have found that equivs-build generates a debian/install file that fails to 
escape
characters such as { or } in filenames (e.g. 
{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi).

A really simple patch could be: (but not 100% sure of side effects, I havent 
written
perl in a decade)

--- a/usr/bin/equivs-build
+++ b/usr/bin/equivs-build
@@ -92,6 +92,8 @@ open INSTALL, '>', "$builddir/debian/install" or
   die "Cannot open $builddir/debian/install for writing: $!\n";
 foreach my $target (keys %install_files, keys %create_files, keys 
%create_links) {
   $target =~ s/ +//g;
+  # escape filenames with {, }
+  $target =~ s/({|})/\\$1/g;
   my $dest;
   my $cnt = 0;
   if ($target =~ m/^(preinst|postinst|prerm|postrm)$/) {


Not sure if there are other special chars to be escaped, but I was just hit by 
this
bug.

Many thanks,
Juan


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

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

Versions of packages equivs depends on:
ii  debhelper  10.7.2
ii  dpkg-dev   1.18.24
ii  fakeroot   1.21-3.1
ii  make   4.1-9.1
ii  perl   5.26.0-5

equivs recommends no packages.

equivs suggests no packages.

-- no debconf information



Bug#872855: shutter: Shutter hangs gnome desktop environment when capture

2017-08-21 Thread machavez
Package: shutter
Version: 0.93.1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm able to open the application but when trying to capture the screen is 
distorted and the whole desktop environment crashes. I can go to a TTY and kill 
shutter process, in that way I can get back to the desktop again.

This behavior is not present in Cinnamon, I can use it whithout problems.


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

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

Versions of packages shutter depends on:
ii  imagemagick8:6.9.7.4+dfsg-16
ii  imagemagick-6.q16 [imagemagick]8:6.9.7.4+dfsg-16
ii  libfile-basedir-perl   0.07-1
ii  libfile-copy-recursive-perl0.38-1
ii  libfile-which-perl 1.21-1
ii  libglib-perl   3:1.326-1+b2
ii  libgnome2-canvas-perl  1.002-4+b2
ii  libgnome2-gconf-perl   1.044-6+b2
ii  libgnome2-perl 1.046-3+b2
ii  libgnome2-vfs-perl 1.082-1+b4
ii  libgnome2-wnck-perl0.16-3+b4
ii  libgtk2-imageview-perl 0.05-2+b4
ii  libgtk2-perl   2:1.24992-1+b1
ii  libgtk2-unique-perl0.05-3+b2
ii  libimage-magick-perl [perlmagick]  8:6.9.7.4+dfsg-16
ii  libjson-perl   2.94-1
ii  libjson-xs-perl3.030-1+b1
ii  liblocale-gettext-perl 1.07-3+b3
ii  libnet-dbus-perl   1.1.0-4+b3
ii  libnet-dropbox-api-perl1.9-1
ii  libpath-class-perl 0.37-1
ii  libproc-processtable-perl  0.53-2+b2
ii  libproc-simple-perl1.32-1
ii  librsvg2-common2.40.18-1
ii  libsort-naturally-perl 1.03-1
ii  libwww-mechanize-perl  1.83-1
ii  libwww-perl6.15-2
ii  libx11-protocol-other-perl 29-2
ii  libx11-protocol-perl   0.56-7
ii  libxml-simple-perl 2.24-1
ii  procps 2:3.3.12-3
ii  xdg-utils  1.1.1-1

Versions of packages shutter recommends:
ii  libgoo-canvas-perl 0.06-2+b4
ii  libgtk2-appindicator-perl  0.15-1+b5

Versions of packages shutter suggests:
pn  gnome-web-photo 
pn  libimage-exiftool-perl  
pn  libnet-dbus-glib-perl   
ii  nautilus-sendto 3.8.4-2+b1

-- no debconf information

Aditional Gnome information:

#dpkg --status gnome

Package: gnome
Status: install ok installed
Priority: optional
Section: metapackages
Installed-Size: 33
Maintainer: Debian GNOME Maintainers 

Architecture: amd64
Source: meta-gnome3
Version: 1:3.22+3
Depends: gnome-core (= 1:3.22+3), desktop-base, network-manager-gnome (>= 1.4), 
libproxy1-plugin-networkmanager, cheese (>= 3.22), evolution (>= 3.22), 
evolution-plugins (>= 3.22), file-roller (>= 3.22), gnome-calendar (>= 3.22), 
gnome-clocks (>= 3.22), gnome-color-manager (>= 3.22), gnome-dictionary (>= 
3.20), gnome-documents (>= 3.22), gnome-getting-started-docs (>= 3.22), 
gnome-maps (>= 3.22), gnome-music (>= 3.22), shotwell | gnome-photos (>= 3.22), 
gnome-screenshot (>= 3.22), gnome-sound-recorder, gnome-tweak-tool (>= 3.22), 
gnome-weather (>= 3.20), nautilus-sendto (>= 3.8), gnome-orca (>= 3.22), 
rygel-playbin (>= 0.24), rygel-tracker (>= 0.24), seahorse (>= 3.20), vinagre 
(>= 3.22), avahi-daemon, gimp (>= 2.8), inkscape (>= 0.48), 
libreoffice-evolution, libreoffice-gnome, libreoffice-writer, libreoffice-calc, 
libreoffice-impress, libgsf-bin, rhythmbox (>= 3.0), simple-scan, 
xdg-user-dirs-gtk, cups-pk-helper (>= 0.2), gedit-plugins (>= 3.22), 
gstreamer1.0-libav (>= 1.10), gstrea
 mer1.0-plugins-ugly (>= 1.10), rhythmbox-plugins, rhythmbox-plugin-cdrecorder, 
totem-plugins, libgtk2-perl (>= 1:1.130)
Recommends: brasero, gnome-games, polari, transmission-gtk
Suggests: alacarte, empathy, goobox | sound-juicer, xul-ext-ublock-origin, 
xul-ext-gnome-keyring, firefox-esr-l10n-all | firefox-l10n-all
Description: Full GNOME Desktop Environment, with extra components
 This is the GNOME Desktop environment, an intuitive and attractive
 desktop, with extra components.
 .
 This metapackage depends on the standard distribution of the GNOME
 desktop environment, plus a complete range of plugins and other
 applications integrating with GNOME and Debian, providing the best
 possible environment to date.



Bug#872854: dnsdist: CVE-2016-7069 CVE-2017-7557

2017-08-21 Thread Salvatore Bonaccorso
Source: dnsdist
Version: 1.1.0-2
Severity: important
Tags: security patch upstream

Hi,

the following vulnerabilities were published for dnsdist, not filling
two bugs individually since 1.1.0 is commont for all affected suites.

CVE-2016-7069[0]:
Crafted backend responses can cause a denial of service

CVE-2017-7557[1]:
Alteration of ACLs via API authentication bypass

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-7069
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7069
[1] https://security-tracker.debian.org/tracker/CVE-2017-7557
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7557

Regards,
Salvatore



Bug#872853: ruby-rugged: New upstream version 0.26.0

2017-08-21 Thread Russell Sim
Package: ruby-rugged
Version: 0.24.0+ds1-3
Severity: normal

Dear Maintainer,

Please consider updating ruby-rugged to the latest version 0.26.0.

libgit2 0.26.0 has been uploaded to experimental.

Cheers,
Russell



-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages ruby-rugged depends on:
ii  libc6   2.24-11
ii  libgit2-24  0.25.1+really0.24.6-1
ii  libgmp102:6.1.2+dfsg-1
ii  libruby2.3  2.3.3-1
ii  ruby1:2.3.3

ruby-rugged recommends no packages.

ruby-rugged suggests no packages.

-- no debconf information



Bug#872828: RFS: node-regjsgen/0.3.0-1 ITP

2017-08-21 Thread Julien Puydt
Hi,

Le 21/08/2017 à 20:54, Bastien Roucaries a écrit :
>>   Section : web
>  
> Section: JavaScript 

Changed.

Snark on #debian-js



Bug#872852: libc6-dev: libm.a is a linker script that refers to libm-2.25.a which does not exist.

2017-08-21 Thread Abhijit Hoskeri
Package: libc6-dev
Version: 2.25-0experimental1
Severity: important

Dear Maintainer,

libc6-dev on experimental does not ship with static library
libm-2.25.a. libm.a is a linker script that refers to this file, but its
not installed.

This causes for example, busybox static compilation to fail.

Thanks,
Abhijit

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

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

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


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

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

Versions of packages libc6-dev depends on:
ii  libc-dev-bin2.25-0experimental1
ii  libc6   2.25-0experimental1
ii  linux-libc-dev  4.13~rc5-1~exp1

libc6-dev recommends no packages.

Versions of packages libc6-dev suggests:
ii  glibc-doc 2.25-0experimental1
ii  manpages-dev  4.12-2

-- no debconf information



Bug#872851: openssh-server: Please drop upstart integration

2017-08-21 Thread Dimitri John Ledkov
Package: openssh-server
Version: 1:7.5p1-5
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

Please drop upstart integration from openssh:

* Patch to drop upstart jobs
* Patch to fix up build

* Please rebase git dpm patches, and drop doc-upstart.patch

Regards,

Dimitri.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJZmz34AAoJEMrC2LnNLKX5mJUH/iD0T6B6i6OWBuEEUF/m+7/H
adrH/BAA4oqCGOqmCsab4z95aE6NB/gDErW1jkOC7oOAAErfr9R/INJD1JENonzi
7c1fGOGgNK1b9+3Cbhs2In0QgTqloeJpamgqp3/6uTop/mWwNeDGD9dCm22K2Smw
boPgvoh2lqUMzm13kcBYOMi6e/zgHgkE0GqDiDAWCaMEHI1Tb+D+A4D8U6C5FqAB
kRcm0ye9Q/TcJ8ikM7BOtYNZNshALOi1XY923tlf85G+pr4xl+J2L9nvv3heUWDC
qWTNd/kGyne2wTWQWiLP4/t+3mpb1q07ClRJNGb5hjSgg60nJwjbDt2735riRX0=
=q/4M
-END PGP SIGNATURE-
>From 575d6aa8c62e7d9f873d0c3fe66d6a51db69dd80 Mon Sep 17 00:00:00 2001
From: Dimitri John Ledkov 
Date: Mon, 21 Aug 2017 12:48:31 +0100
Subject: [PATCH 1/2] Drop upstart system and user jobs.

---
 debian/agent-launch   |  8 +---
 debian/changelog  |  4 
 debian/openssh-client.install |  5 -
 debian/openssh-server.maintscript |  1 +
 debian/openssh-server.postinst|  7 ---
 debian/openssh-server.ssh.init| 12 
 debian/openssh-server.ssh.upstart | 29 -
 debian/ssh-agent.user-session.upstart |  7 ---
 8 files changed, 6 insertions(+), 67 deletions(-)
 delete mode 100644 debian/openssh-server.ssh.upstart
 delete mode 100644 debian/ssh-agent.user-session.upstart

diff --git a/debian/agent-launch b/debian/agent-launch
index 79c75a5..f3cbfae 100755
--- a/debian/agent-launch
+++ b/debian/agent-launch
@@ -1,5 +1,5 @@
 #!/bin/sh
-# helper script for launching ssh-agent, used by systemd unit and upstart job
+# helper script for launching ssh-agent, used by systemd unit
 set -e
 
 if [ ! -d "$XDG_RUNTIME_DIR" ]; then
@@ -11,17 +11,11 @@ if [ "$1" = start ]; then
 if [ -z "$SSH_AUTH_SOCK" ] && grep -s -q '^use-ssh-agent$' /etc/X11/Xsession.options; then
 S="$XDG_RUNTIME_DIR/openssh_agent"
 dbus-update-activation-environment --verbose --systemd SSH_AUTH_SOCK=$S SSH_AGENT_LAUNCHER=openssh
-if [ "$UPSTART_SESSION" ] && type initctl >/dev/null 2>&1; then
-initctl set-env --global SSH_AUTH_SOCK=$S
-fi
 exec ssh-agent -D -a $S
 fi
 elif [ "$1" = stop ]; then
 if [ "$SSH_AGENT_LAUNCHER" = openssh ]; then
 dbus-update-activation-environment --systemd  SSH_AUTH_SOCK=
-if [ "$UPSTART_SESSION" ] && type initctl >/dev/null 2>&1; then
-initctl unset-env --global SSH_AUTH_SOCK
-fi
 fi
 else
 echo "Unknown command $1" >&2
diff --git a/debian/changelog b/debian/changelog
index 153a8f7..0aed26a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,10 +1,14 @@
 openssh (1:7.5p1-6) UNRELEASED; urgency=medium
 
+  [ Colin Watson ]
   * Test configuration before starting or reloading sshd under systemd
 (closes: #865770).
   * Create /run/sshd under systemd using RuntimeDirectory rather than
 tmpfiles.d (thanks, Dmitry Smirnov; closes: #864190).
 
+  [ Dimitri John Ledkov ]
+  * Drop upstart system and user jobs.
+
  -- Colin Watson   Mon, 26 Jun 2017 10:09:28 +0100
 
 openssh (1:7.5p1-5) unstable; urgency=medium
diff --git a/debian/openssh-client.install b/debian/openssh-client.install
index b8b798d..838f981 100755
--- a/debian/openssh-client.install
+++ b/debian/openssh-client.install
@@ -32,10 +32,5 @@ debian/agent-launch usr/lib/openssh
 # yet.
 debian/openssh-client.apport => usr/share/apport/package-hooks/openssh-client.py
 
-# Upstart user job (only used under user sessions).
-debian/ssh-agent.user-session.upstart => usr/share/upstart/sessions/ssh-agent.conf
-
 # systemd user unit (only used under sessions)
 debian/systemd/ssh-agent.service usr/lib/systemd/user
-# disable above upstart job when running the systemd user unit
-debian/systemd/ssh-agent.override usr/share/upstart/systemd-session/upstart
diff --git a/debian/openssh-server.maintscript b/debian/openssh-server.maintscript
index f9e3c4d..0e44b28 100644
--- a/debian/openssh-server.maintscript
+++ b/debian/openssh-server.maintscript
@@ -1 +1,2 @@
 mv_conffile /etc/pam.d/ssh /etc/pam.d/sshd 1:4.7p1-4~
+rm_conffile /etc/init/ssh.conf 1:7.5p1-6~ openssh-server
diff --git a/debian/openssh-server.postinst b/debian/openssh-server.postinst
index 8b554ee..94a47da 100644
--- a/debian/openssh-server.postinst
+++ b/debian/openssh-server.postinst
@@ -128,13 +128,6 @@ if [ "$action" = configure ]; then
 	if dpkg --compare-versions "$2" lt-nl 1:5.5p1-6; then
 	rm -f /run/sshd/.placeholder
 	fi
-	if dpkg --compare-versions "$2" lt-nl 1:6.2p2-3 && \
-	   which initctl >/dev/null && initctl version 2>/dev/null | grep -q upstart && \
-	   ! status ssh 2>/dev/null | grep -q ' start/'; then
-	# We must stop the sysvinit-controlled sshd 

Bug#872850: libgit2-glib-1.0-0: New upstream release v0.26.0

2017-08-21 Thread Russell Sim
Package: libgit2-glib-1.0-0
Version: 0.24.4-1
Severity: normal

Dear Maintainer,

Please consider updating to the latest upstream stable release of libgit2-glib
v0.26.0 as soon as possible.

libgit2 0.26.0 has been uploaded to experimental.

Thanks,
Russell



-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libgit2-glib-1.0-0 depends on:
ii  libc6  2.24-11
ii  libgirepository-1.0-1  1.50.0-1+b1
ii  libgit2-24 0.25.1+really0.24.6-1
ii  libglib2.0-0   2.50.3-2

libgit2-glib-1.0-0 recommends no packages.

libgit2-glib-1.0-0 suggests no packages.

-- no debconf information



Bug#872302: vim sends cursor-blink sequence to terminal

2017-08-21 Thread Daniel Andersson
Package: vim
Version: 2:8.0.0946-1
Followup-For: Bug #872302

This is discussed as issue 1986 at Github [0] and seems to have been
resolved in Vim patch 8.0.0973 [1] (I have not tested it myself, but
other reports seem positive). Once a version newer than this is uploaded
to Debian, this bug should be resolved.

[0]: https://github.com/vim/vim/issues/1986
[1]: https://github.com/vim/vim/commit/ce1c3278



Bug#855469: [Pkg-javascript-devel] Bug#855469: RFP: node-dargs -- Convert options into an array of arguments

2017-08-21 Thread Bastien ROUCARIES
control: retitle -1 ITP: node-dargs -- Convert options into an array
of arguments

On Mon, Aug 21, 2017 at 9:35 PM, Bastien ROUCARIES
 wrote:
> control: tags -1 owner



Bug#872849: psi4: Reconfigure libderiv for higher angular momentum

2017-08-21 Thread Georg
Package: psi4
Version: 1:1.0-1+b1
Severity: normal

Dear Maintainer,
   * What led up to the situation?
Running a KS/CC-PVQZ H2O computation with geometry optimisation
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Applying the cc-pvqz basis set. Smaller sets (e. g. cc-pvtz or cc-pvdz) were ok.
   * What was the outcome of this action?
In the output file there is an error message:
ERROR: ERI - libderiv cannot handle angular momentum this high.
 In a fresh object directory, reconfigure libderiv for higher angular 
momentum, then recompile.
An error has occurred python-side. Traceback (most recent call last):

  File "", line 33, in 

  File "/usr/share/psi/python/driver.py", line 1023, in optimize
G, wfn = gradient(lowername, return_wfn=True, molecule=moleculeclone, 
**kwargs)

  File "/usr/share/psi/python/driver.py", line 592, in gradient
wfn = procedures['gradient'][lowername](lowername, molecule=molecule, 
**kwargs)

  File "/usr/share/psi/python/procedures/proc.py", line 2513, in 
run_dft_gradient
wfn = run_scf_gradient(name, **kwargs)

  File "/usr/share/psi/python/procedures/proc.py", line 1709, in 
run_scf_gradient
grad = psi4.scfgrad(ref_wfn)

RuntimeError: X%^?

   * What outcome did you expect instead?
The application running successfully to the end


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

Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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)

Versions of packages psi4 depends on:
ii  libblas3 [libblas.so.3]  3.7.1-1
ii  libc62.24-15
ii  libchemps2-2 1.8.4-2
ii  libgcc1  1:7.2.0-1
ii  libgomp1 7.2.0-1
ii  libhdf5-100  1.10.0-patch1+docs-4
ii  libint1  1.1.6-2+b1
ii  liblapack3 [liblapack.so.3]  3.7.1-1
ii  libpython2.7 2.7.13-4
ii  libstdc++6   7.2.0-1
ii  libsz2   0.3.2-2
ii  psi4-data1:1.0-1
ii  zlib1g   1:1.2.8.dfsg-5

psi4 recommends no packages.

psi4 suggests no packages.

-- no debconf information



Bug#872848: dav-text: please support line syntax "dav +42 file"

2017-08-21 Thread Adam Borowski
Package: dav-text
Version: 0.8.6-1
Severity: wishlist

Hi!
There's an option to start at a given line:
-l[#]  Starts Dav at the line number [#].

However, every single editor I know that runs in a terminal accepts a
standard syntax of prefixing the file to be opened by +# where # is the
line number.

dav has instead just -l# (which also needs to come after the filename, not
before).  It would be nice if you recognized +# as well.


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

Kernel: Linux 4.12.8+ (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages dav-text depends on:
ii  libc62.24-14
ii  libncurses5  6.0+20170715-2
ii  libtinfo56.0+20170715-2

dav-text recommends no packages.

dav-text suggests no packages.

-- no debconf information



Bug#872798: nslcd: can be killed by the OOM Killer, DoS

2017-08-21 Thread Arthur de Jong
Control: sevirity -1 normal

On Mon, 2017-08-21 at 13:17 +0200, Vincent Lefevre wrote:
> Severity: grave
> Justification: causes non-serious data loss and DoS from an end user.

The severity is a bit questionable and, at the very least not a flaw in
or unique to nslcd. Any local user that does not have resource limits
applied to them can DoS the whole system easily so I'm lowering the
severity to normal.

> It appears that nslcd can be killed by the OOM Killer when some user
> process takes all the memory. In such a case, it is no longer
> possible to connect to the machine by SSH. Thus this is DoS by an end
> user, with possible data loss concerning what is running on the
> machine.

The OOM is indeed a bit of Russian roulette on your system. You can
tune it a bit with vm.panic_on_oom and vm.overcommit_memory sysctls or
perform the following action that is equivalent to what newer nslcd
does:

echo -1000 > /proc/`cat /var/run/nslcd/nslcd.pid`/oom_score_adj

The patch should be pretty easy to backport though. I've put it on my
list but can't really guarantee a turn-around-time.

Thanks,

-- 
-- arthur - adej...@debian.org - https://people.debian.org/~adejong --


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


Bug#872847: fritzing: fails to bulid against libgit2 0.26.0

2017-08-21 Thread Russell Sim
Package: fritzing
Version: 0.9.3b+dfsg-4
Severity: normal

Dear Maintainer,

A new version of libgit2 0.26.0 has been added to Experimental.  It appears
that the version of fritzing in unstable won't build against this version [1].

>From what I can see Debian has the latests version of Fritzing.  So if this
problem is due to upsteam not supporting 0.26.0 can you please follow up with
them to get the version of libgit2 required updated to the latest version.

Thanks,
Russell


1.
https://people.debian.org/~infinity0/libgit2/fritzing_0.9.3b+dfsg-4_amd64-2017-08-01T11:37:39Z.build.xz



-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages fritzing depends on:
ii  fritzing-data 0.9.3b+dfsg-4
ii  libc6 2.24-11
ii  libgcc1   1:6.3.0-18
ii  libgit2-240.25.1+really0.24.6-1
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libqt5concurrent5 5.7.1+dfsg-3+b1
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5network55.7.1+dfsg-3+b1
ii  libqt5printsupport5   5.7.1+dfsg-3+b1
ii  libqt5serialport5 5.7.1~20161021-2
ii  libqt5sql55.7.1+dfsg-3+b1
ii  libqt5sql5-sqlite 5.7.1+dfsg-3+b1
ii  libqt5svg55.7.1~20161021-2+b2
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libqt5xml55.7.1+dfsg-3+b1
ii  libstdc++66.3.0-18
ii  zlib1g1:1.2.8.dfsg-5

fritzing recommends no packages.

Versions of packages fritzing suggests:
ii  fritzing-parts  0.9.3b-1

-- no debconf information



Bug#872846: temporarily readd POT-Creation-Date

2017-08-21 Thread Helmut Grohne
Package: gettext
Version: 0.19.8.1-3
Severity: serious
Justification: glibc ftbfs
User: helm...@debian.org
Usertags: rebootstrap

The removal of POT-Creation-Date (#792687) is a nice thing to do, but
the archive isn't quite ready for it.

 * glibc FTBFS https://sourceware.org/bugzilla/show_bug.cgi?id=21508 and
   no patch is available as of this writing.
 * The commit changes .mo files and thus breaks M-A:sameness allover the
   archive, e.g. #872806. Likely all packages shipping .mo files in
   M-A:same packages are affected. The multiarch database on delfin.d.o
   gives a clue:

   SELECT distinct source
 FROM package
 WHERE multiarch = 'same'
   AND EXISTS (SELECT 1
 FROM content
 WHERE package.id = content.pid
   AND filename LIKE './usr/share/%/%.mo')
 ORDER BY source;

   apt avahi colord-gtk cpluff cracklib2 cutter-testing-framework
   cwidget eb elfutils exo fcitx-anthy fcitx-cloudpinyin
   fcitx-googlepinyin fcitx-hangul fcitx-kkc fcitx-m17n giac girara
   gnutls28 grilo-plugins gsmlib gst-plugins-bad1.0 gst-plugins-base1.0
   gst-plugins-good1.0 gst-plugins-ugly1.0 gstreamer1.0 gtkspell3
   imhangul imhangul3 kde-gtk-config libexif libgpg-error libgphoto2
   libguestfs libhdate libisds libisocodes libticables libticalcs
   libtifiles libvisual libvisual-plugins lunar-date mozc newt poldi
   popt postgresql-9.6 purpose scim-chewing scim-thai tre vips
   webkit2gtk webkitgtk xfce4-pulseaudio-plugin

   We'd likely have to binNMU these.

I talked with Daniel Shahaf and we concluded that a temporary revert
would be the best way forward. It shall leave time for fixing the above
issues.

Helmut



Bug#872841: yamagi-quake2-core: Missing game.so for xatrix, rogue, ctf

2017-08-21 Thread Simon McVittie
On Mon, 21 Aug 2017 at 08:58:04 +0200, Arjen Balfoort wrote:
>  Sources: 
>  https://github.com/yquake2/xatrix
>  https://github.com/yquake2/rogue

Unfortunately we cannot distribute these two with Debian. Their source code is
derived from the Quake II mod SDK, not from the GPL source release of Quake II,
and carries restrictions that are certainly unsuitable for main/contrib
and potentially also unsuitable for non-free (it is not obvious whether the
"LIMITED PROGRAM SOURCE CODE LICENSE" is OK for non-free).

However, if you build the quake2-groundzero-data and quake2-reckoning-data
packages using game-data-packager, then game-data-packager will automatically
download and compile the game.so from (releases of) the same git repositories
you mentioned.

>  https://github.com/yquake2/ctf

This one is (claimed to be) GPL-2+, so maybe we can include it in yquake2.
Please confirm that it works correctly?

S



Bug#872845: base-files: Public SCM seem to be not available

2017-08-21 Thread Askar Safin
Package: base-files
Version: 9.9+deb9u1
Severity: normal

It seems public SCM for base-files is not available. When I type "apt-get 
source base-files" I don't see something like "'base-files' packaging is 
maintained in the ... version control system". Please provide some public SCM.

For example, I may want to do "git bisect" to determine when some config change 
appeared in base-files.

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 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)

Versions of packages base-files depends on:
ii  gawk [awk]  1:4.1.4+dfsg-1
ii  mawk [awk]  1.3.3-17+b3

base-files recommends no packages.

base-files suggests no packages.

-- no debconf information



Bug#872339: libgda-5.0-4: Can't rebuild package with --with-ui

2017-08-21 Thread Andreas Henriksson
On Wed, Aug 16, 2017 at 11:30:38PM -0500, Pavlo Solntsev wrote:
> ok, I was able to compile the package with ui support. Could you please
> explain why this option was turned off?

Debian is a volunteer project. You're the only one showing interest for
this package. Who are you adressing when you say 'Could *you* ...'?

Please note that libgda5 is up for removal from debian because of
lacking interest from volunteers to keep it in shape. If you want it to
stay around *you* need to step up and contribute.

Speaking about that thanks for your effort of your previously submitted
patch. It's roughly equivalent to the upstream commit
https://git.gnome.org/browse/libgda/commit/?id=68af249e1c36cbac2e3990

In other words the problem has already been fixed upstream, together
with several other issues that might also be relevant.

Unfortunately the upstream software has not seen a new release in over
two years now. It looks like upstream might need someone to volunteer
helping out.

Right now, with the upstream project basically dead and with basically
no applications in debian using libgda anymore and very few people
showing interest in actually maintaining the software it's not looking
bright to expand the offered functionality. First step would be to
maintain the currently offered functionality, then move on to expand
it if successful and you're able to provide additional resources on
top of that.

Please see the following urls where you can track debian information:
https://tracker.debian.org/pkg/libgda5
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=libgda5

Here are some instructions that might be helpful for you to work on
the packaging:

apt install devscripts svn-buildpackage
mkdir -p ~/playground
cd ~/playground
debcheckout --source=download-only libgda5
cd libgda5
wget -O debian/patches/git_fix_libgda-ui_build.patch \
https://git.gnome.org/browse/libgda/patch/?id=68af249e1c36cbac2
echo "git_fix_libgda-ui_build.patch" >> debian/patches/series
svn add debian/patches/*
dch -i
svn-buildpackage

Hope this helps.

If you want to enable building an additional shared library from the
sources you likely need to modify debian/rules for configure flags and
then debian/control to add the new library package + the new development
package. Then finally add debian/.install files listing which
files to ship in the package. Don't forget to list (the reason for) your
changes in debian/changelog.

Once you've produced a working package feel free to submit your changes
to this bug report. Also do come visit #debian-gnome on OFTC
(irc.debian.org).

Regards,
Andreas Henriksson



Bug#872844: connman: [CVE-2017-12865] stack overflow in dns proxy feature

2017-08-21 Thread Luciano Bello
Package: connman
X-Debbugs-CC: t...@security.debian.org secure-testing-
t...@lists.alioth.debian.org
Severity: grave
Version:  1.33-3
Tags: security patch

Hi,

the following vulnerability was published for connman.

CVE-2017-12865[0]:
stack overflow in dns proxy feature

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

The commit that fix the vulnerability can be found here: https://
git.kernel.org/pub/scm/network/connman/connman.git/commit/?
id=5c281d182ecdd0a424b64f7698f32467f8f67b71

The vulnerability was fixed in  1.35, therefore sid and  buster are not 
affected.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-12865
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12865

Please adjust the affected versions in the BTS as needed.



  1   2   3   4   >