date:20181121

On Wed, Nov 21, 2018 at 5:57 AM Jeremy Davis  wrote:
> On 20/11/18 18:50, Olaf van der Spek wrote:
> > IMO apt shouldn't be run in such a way that packages get removed
> > automatically though..
>
> If you have any specific suggestions on how to ensure that apt won't
> remove packages, I'd be interested to hear.

No, unfortunately.
Are you aware of the unattended-upgrades package though?

> Also, IIRC there have been cases where removal of old packages were
> required (I think that was the case with Samba security updates within
> Jessie?! - Although perhaps I am confused).

> Possibly the easiest way to reproduce the issue would be to download our
> v15.0 (Stretch based) LAMP appliance ISO[1] (signed hash file here[2])
> and install it to a VM and NOT run the initial firstboot "security
> updates" script (i.e. select "skip" when asked). Once logged in as root,
> you can then poke around inside and see exactly what is going on.

Have you tried figuring out why apt wants to remove mariadb-server?

Gr,

Olaf

Bug#914261: RFS: libt3window/0.3.1-1

2018-11-21 Thread Gertjan Halkes

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "libt3window"

* Package name: libt3window
  Version : 0.3.1-1
  Upstream Author : Gertjan Halkes 
* URL : https://os.ghalkes.nl/t3/libt3window.html
* License : GPLv3
  Section : libs

It builds those binary packages:

  libt3window-dev - Development files for libt3window
  libt3window0 - Library for creating window-based terminal programs

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

https://mentors.debian.net/package/libt3window

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

dget -x
https://mentors.debian.net/debian/pool/main/libt/libt3window/libt3window_0.3.1-1.dsc

Changes since the last upload:

  * New upstream release.

Regards,
  Gertjan Halkes

Bug#914256: lintian: conflict between no-template-description and untranslatable-debconf-templates

Hi Vincent.

> Version: 2.5.50.4
[…]
> I also had a look at the git repository and could not see recent
> work related to either of the tags involved here.

Granted and will try and reproduce later but just an FYI that
2.5.112~bpo9+1 is in stretch-backports so it should be easy to
install and reconfirm with the latest version.


Regards,

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

Bug#914183: shutter: No way to install shutter in debian buster

2018-11-21 Thread Ludovic CHEVALIER

OK. Thanks for your answer.

Bug#914262: Segfaults on "Write Output" if more than 8 keysyms per key are present

2018-11-21 Thread Christoph Berg

Package: xkeycaps
Version: 2.47-4.1
Severity: grave
Tags: stretch patch

The code only deals with 8 names per key, but unfortunately doesn't expose that
number as a constant that is easily changed. Clip to 8 so we don't segfault.

 Program received signal SIGSEGV, Segmentation fault.
 strlen () at ../sysdeps/x86_64/strlen.S:106
 106   ../sysdeps/x86_64/strlen.S: Datei oder Verzeichnis nicht gefunden.
 (gdb) bt
 #0  strlen () at ../sysdeps/x86_64/strlen.S:106
 #1  0x76a2fa45 in __GI__IO_fputs (
 str=str@entry=0x7fff000a ,
 fp=fp@entry=0x559f6da0) at iofputs.c:33
 #2  0x555dc2a4 in fprintf (__fmt=0x555e49e1 "%s", 
__stream=)
 at /usr/include/x86_64-linux-gnu/bits/stdio2.h:97
 #3  button_write (button=, client_data=,
 call_data=) at commands.c:629
 #4  0x77944aad in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
 #5  0x77944f15 in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
 #6  0x77945bdd in _XtTranslateEvent () from 
/usr/lib/x86_64-linux-gnu/libXt.so.6
 #7  0x7791def2 in XtDispatchEventToWidget () from 
/usr/lib/x86_64-linux-gnu/libXt.so.6
 #8  0x7791e8dd in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
 #9  0x7791e9b9 in XtDispatchEvent () from 
/usr/lib/x86_64-linux-gnu/libXt.so.6
 #10 0x555d2d96 in xkeycaps_main_loop (app=0x559a81a0, 
keyboard=)
 at xkeycaps.c:232
 #11 main (argc=, argv=) at xkeycaps.c:355
 (gdb) f 3
 #3  button_write (button=, client_data=,
 call_data=) at commands.c:629
 629 fprintf (out, "%s", differences[i].names[j]);
 (gdb) p i
 $1 = 1
 (gdb) p j
 $2 = 9
 (gdb) p differences
 $3 = {{key = 0x55a0dde0, count = 3, names = {0x76e13fc6 
<_XkeyTable+134> "Escape",
   0x555e4448 "NoSymbol", 0x76e13fc6 <_XkeyTable+134> "Escape", 0x0,
   0x1d7 ,
   0x1000 ,
   0x8 ,
   0x5a42ab91 }}, {key = 
0x55a0dfa0,
 count = 10, names = {0x76e144be <_XkeyTable+1406> "F1",
   0x76e144be <_XkeyTable+1406> "F1", 0x76e144be <_XkeyTable+1406> 
"F1",
   0x76e144be <_XkeyTable+1406> "F1", 0x76e144be <_XkeyTable+1406> 
"F1",
   0x76e144be <_XkeyTable+1406> "F1",
   0x76e1dfaf <_XkeyTable+41071> "XF86Switch_VT_1",
   0x76e144be <_XkeyTable+1406> "F1"}}, {key = 0x55a0e160, count = 
10, names = {
   0x76e144c7 <_XkeyTable+1415> "F2", 0x76e144c7 <_XkeyTable+1415> 
"F2",
   0x76e144c7 <_XkeyTable+1415> "F2", 0x76e144c7 <_XkeyTable+1415> 
"F2",
   0x76e144c7 <_XkeyTable+1415> "F2", 0x76e144c7 <_XkeyTable+1415> 
"F2",
   0x76e1dfc5 <_XkeyTable+41093> "XF86Switch_VT_2",
   0x76e144c7 <_XkeyTable+1415> "F2"}},

--- a/commands.c
+++ b/commands.c
@@ -440,6 +440,7 @@ button_write (button, client_data, call_
 keysyms = XGetKeyboardMapping (XtDisplay (widget),
key->key.keycode,
1, &count);
+if (count > 8) count = 8; /* FIXME: we are only prepared for 8 
names per key, clip here */
 if (! keysyms) count = 0;
 all [all_count].key = key;
 for (; count > 0; count--)


Christoph

Bug#914264: O: pdf2htmlex -- Converts PDF to HTML while retaining most formatting

2018-11-21 Thread Johannes 'josch' Schauer

Package: wnpp
Severity: normal

I intend to orphan the pdf2htmlex package.

The package description is:
 pdf2htmlEX converts PDF to HTML while retaining text, format and style as much
 as possible by making use of HTML5, JavaScript and modern CSS features.
 Even difficult content like PDFs with embedded fonts, multicolumn documents,
 scientific papers with complicated figures and mathematical formulas will
 mostly be represented correctly. Fallback mode generates HTML pages which
 do not require any JavaScript to view them correctly at the expense of a
 larger file size.

Upstream has been looking for a new maintainer for nearly two years now:

http://pdf2htmlex.blogspot.com/2016/12/looking-for-new-maintainer.html

An upstream bug indicates that nobody new has been found:

https://github.com/coolwanglu/pdf2htmlEX/issues/726

The last commit by upstream was Dec 11, 2016:

https://github.com/coolwanglu/pdf2htmlEX/commits/master

But the package suffers from two RC bugs:

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

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

Fixing these problems requires a deep understanding of the software
which I do not have nor the time to acquire it.

I'm thus orphaning the package in the hopes that somebody else picks up
the pieces.

Thanks!

cheers, josch

Bug#914263: cabextract: -F option doesn't work correctly.

2018-11-21 Thread Jactry Zeng

Package: cabextract
Version: 1.9-1
Severity: normal
Tags: newcomer

Dear Maintainer,

Steps to reproduce:
1) $ axel
https://download.microsoft.com/download/4/4/d/44de8a9e-630d-4c10-9f17-b9b34d3f6417/scripten.exe
2) $ cabextract -q scripten.exe -F jscript.dll
3) $ md5sum jscript.dll
889911313faa1670f196e2cb24aff0b6  jscript.dll

Expected:
md5sum 492d5ed2ee82c373a8ba3d3946de3a38

Installed package information(by `aptitude show cabextract`):
Package: cabextract
Version: 1.9-1
New: yes
State: installed
Automatically installed: no
Multi-Arch: foreign
Priority: optional
Section: utils
Maintainer: Eric Sharkey 
Architecture: amd64
Uncompressed Size: 85.0 k
Depends: libc6 (>= 2.14), libmspack0 (>= 0.4)
Conflicts: cabextract:i386
Enhances: konqueror
Provides: cabextract:i386 (= 1.9-1)
Provided by: cabextract:i386 (1.9-1)
Description: Microsoft Cabinet file unpacker
 Cabextract is a program which unpacks cabinet (.cab) files, which are a form
of archive Microsoft uses to distribute their software and things like Windows
 Font Packs.
Tags: interface::commandline, role::program, scope::utility, works-
with::archive

$  md5sum /usr/bin/cabextract
dd075679f7ee8c2f95639ab68d312107  /usr/bin/cabextract

I also tried to compile a cabextract binary from source downloaded by `apt
source cabextract`, and it worked correctly.



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

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

Versions of packages cabextract depends on:
ii  libc6   2.27-8
ii  libmspack0  0.8-1

cabextract recommends no packages.

cabextract suggests no packages.

-- no debconf information

Bug#914172: [debian-mysql] Bug#914172: Bug#914172: mariadb-server-10.1: mariadb-server sec-update (10.1.37-0+deb9u1) uninstalls default-mysql-server, mysql-server, mariadb-server-10.1 & mariadb-client

2018-11-21 Thread Jeremy Davis

On 21/11/18 19:08, Olaf van der Spek wrote:
> Are you aware of the unattended-upgrades package though?

I have heard of it, but never actually tested it.

FWIW we've been using this config for ~10 years now and this is only the
4th time it's bitten us (albeit one of the worst).

Perhaps it's time to have a closer look at unattended-upgrades?!

> Have you tried figuring out why apt wants to remove mariadb-server?

Pretty sure it's because we don't have libconfig-inifiles-perl installed
by default, which appears to (now?) be a 'depends' of mariadb-client-10.1.

FWIW we have apt configured to only install 'depends' and I assume that
it has moved from a 'recommends' to a 'depends' although that is only a
guess...

signature.asc
Description: OpenPGP digital signature

Bug#914265: stretch-pu: package xkeycaps/2.47-4.1+deb9u1

2018-11-21 Thread Christoph Berg

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hi,

please unblock xkeycaps/2.47-4.1+deb9u1. It fixes a segfault if more
than 8 keysyms per key are present, which is apparently the case in
the default setup nowadays.

Christoph

No differences were encountered between the control files

diff -Nru xkeycaps-2.47/commands.c xkeycaps-2.47/commands.c
--- xkeycaps-2.47/commands.c	2005-02-22 23:33:15.0 +0100
+++ xkeycaps-2.47/commands.c	2018-11-21 10:08:41.0 +0100
@@ -440,6 +440,7 @@
 	  keysyms = XGetKeyboardMapping (XtDisplay (widget),
 	 key->key.keycode,
 	 1, &count);
+	  if (count > 8) count = 8; /* FIXME: we are only prepared for 8 names per key, clip here */
 	  if (! keysyms) count = 0;
 	  all [all_count].key = key;
 	  for (; count > 0; count--)
diff -Nru xkeycaps-2.47/debian/changelog xkeycaps-2.47/debian/changelog
--- xkeycaps-2.47/debian/changelog	2018-11-21 10:08:41.0 +0100
+++ xkeycaps-2.47/debian/changelog	2018-11-21 10:08:41.0 +0100
@@ -1,3 +1,10 @@
+xkeycaps (2.47-4.1+deb9u1) stretch; urgency=medium
+
+  * Prevent segfault in commands.c when more than 8 keysyms per key are
+present. (Closes: #914262)
+
+ -- Christoph Berg   Wed, 21 Nov 2018 09:47:46 +0100
+
 xkeycaps (2.47-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.


signature.asc
Description: PGP signature

Bug#914190: blender: Crashes on startup




On Tue, 20 Nov 2018 22:45:46 +0100 "Matteo F. Vescovi"  wrote:
> Hi again!
> 
> On 2018-11-20 at 18:55 (+0100), Lucio Crusca wrote:
> > On 20/11/18 18:06, Matteo F. Vescovi wrote:
> >> Is it ok for you, Lucio?
> >
> > Yes, no problem, I can wait. Thanks.
> 
> Meanwhile, I figured out what's the problem here: OpenColorIO library.
> 
> A rebuild+install on up-to-date unstable/sid machine of that library
> made Blender run back again.
> 
> I'll ask for a give-back on all architectures, since OCIO seems to be
> not part of any transition, at the moment.

Normally when a rebuild fixes a problem like this, there's probably an ABI 
break somewhere, which needs to be addressed properly.

Thread 1 "blender" received signal SIGSEGV, Segmentation fault.
YAML::detail::node_data::get, std::allocator > > (pMemory=..., 
key="ocio_profile_version", this=) at 
/usr/include/yaml-cpp/node/detail/impl.h:91
91  /usr/include/yaml-cpp/node/detail/impl.h: No such file or directory.
(gdb) bt
#0  0x74dc95e2 in 
YAML::detail::node_data::get, std::allocator > 
>(std::__cxx11::basic_string, std::allocator 
> const&, boost::shared_ptr) const (pMemory=..., 
key="ocio_profile_version", this=)
at /usr/include/yaml-cpp/node/detail/impl.h:91
#1  0x74dc95e2 in 
YAML::detail::node_ref::get, std::allocator > 
>(std::__cxx11::basic_string, std::allocator 
> const&, boost::shared_ptr) const (pMemory=..., 
key="ocio_profile_version", this=)
at /usr/include/yaml-cpp/node/detail/node_ref.h:61
#2  0x74dc95e2 in 
YAML::detail::node::get, std::allocator > 
>(std::__cxx11::basic_string, std::allocator 
> const&, boost::shared_ptr) const (pMemory=..., 
key="ocio_profile_version", this=)
at /usr/include/yaml-cpp/node/detail/node.h:121
#3  0x74dc95e2 in YAML::Node::operator[](char const (&) 
[21]) const (this=this@entry=0x7fffdbc0, key=...) at 
/usr/include/yaml-cpp/node/impl.h:370
#4  0x74dc2b1d in OpenColorIO::v1::(anonymous 
namespace)::load(YAML::Node const&, OpenColorIO::v1::ConfigRcPtr&, char const*) 
(node=..., c=std::tr1::shared_ptr (use count 1, weak 
count 0) = {...}, filename=filename@entry=0x7fffe200 
"/usr/share/blender/datafiles/colormanagement/config.ocio") at 
./src/core/OCIOYaml.cpp:1445
#5  0x74dc669d in OpenColorIO::v1::OCIOYaml::open(std::istream&, 
std::tr1::shared_ptr&, char const*) const 
(this=, istream=..., 
c=std::tr1::shared_ptr (use count 1, weak count 0) = 
{...}, filename=filename@entry=0x7fffe200 
"/usr/share/blender/datafiles/colormanagement/config.ocio")
at ./src/core/OCIOYaml.cpp:1841
#6  0x74d3fa63 in OpenColorIO::v1::Config::CreateFromFile(char const*) 
(filename=0x7fffe200 
"/usr/share/blender/datafiles/colormanagement/config.ocio") at 
./src/core/Config.cpp:385
#7  0x5801f37f in OCIOImpl::configCreateFromFile(char const*) ()
#8  0x56fc3d3a in colormanagement_init ()
#9  0x565a3fe2 in main ()
(gdb) quit

The crash is happening in libyaml-cpp.

ii  libyaml-cpp0.5v5:amd64  0.5.3-0.1   
  amd64YAML parser and emitter for C++

Note that that was updated to 0.5.3 two days ago. Downgrading to the
version in testing fixes this crash. So it seems like yaml-cpp broke
the ABI in 0.5.3 if a rebuild of opencolorio against the new version
solves the crash.

I have noticed that both yaml-cpp and opencolorio build-dep on libboost-dev,
but they don't depend on any boost package. If yaml-cpp is exposing some
boost symbols in its own ABI, it could need a SONAME bump for every
boost transition.

Cheers,
Emilio

Bug#668549: libfribidi-bin: refers to wrong debian package

Version: 18.04.5-1

On Thu, Apr 12, 2012 at 01:44:48PM -0400, whatmeurgent wrote:
> Package: libfribidi-bin
> Version: 0.19.2-3
> Severity: normal
> 
> Dear Maintainer,
> I was helping someone with a bidi issue, and received the following message on
> a debian command line:
> 
> The program 'fribidi' is currently not installed.  To run 'fribidi' please ask
> your administrator to install the package 'libfribidi0'
> fribidi: command not found
> 
> The problem with that message is that the debian package for the command-line
> utility is libfribidi-bin.
> 
> This became frustrating for me as that package was, in fact, already 
> installed.


So, I'm not sure what your problem was precisely, as it depends on the status
of the Contents files 6 years ago, but it seems to work now.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#914190: blender: Crashes on startup

On Wed, 21 Nov 2018 10:16:45 +0100 Emilio Pozuelo Monfort  
wrote:
> I have noticed that both yaml-cpp and opencolorio build-dep on libboost-dev,
> but they don't depend on any boost package. If yaml-cpp is exposing some
> boost symbols in its own ABI, it could need a SONAME bump for every
> boost transition.

Or maybe it just needs to link against boost, given it's using boost symbols?

ii  libyaml-cpp0.5v5:amd64 0.5.3-0.1amd64YAML parser and emitter 
for C++

emilio@tatooine:~$ nm -D /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5.3 | grep 
boost
00033ca0 T 
_ZN4YAML6detail9node_data14convert_to_mapEN5boost10shared_ptrINS0_13memory_holderEEE
0001d900 W _ZN5boost6detail15sp_counted_base7destroyEv
00074ab8 V _ZTIN5boost6detail17sp_counted_impl_pIN4YAML6detail4nodeEEE

emilio@tatooine:~$ ldd /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5.3 | grep 
boost
emilio@tatooine:~$

Probably the same thing with opencolorio.

Emilio

Bug#914172: [debian-mysql] Bug#914172: Bug#914172: mariadb-server-10.1: mariadb-server sec-update (10.1.37-0+deb9u1) uninstalls default-mysql-server, mysql-server, mariadb-server-10.1 & mariadb-client

On Wed, Nov 21, 2018 at 10:05 AM Jeremy Davis  wrote:
> > Have you tried figuring out why apt wants to remove mariadb-server?
>
> Pretty sure it's because we don't have libconfig-inifiles-perl installed
> by default, which appears to (now?) be a 'depends' of mariadb-client-10.1.
>
> FWIW we have apt configured to only install 'depends' and I assume that
> it has moved from a 'recommends' to a 'depends' although that is only a
> guess...

I think it wasn't in recommends either but that's not relevant.
The question is: why didn't apt just install libconfig-inifiles-perl?

Could you reproduce the issue and find out?



-- 
Olaf

Bug#913542: teckit: Fails to build on Ubuntu's ppc64el (symbols)

Control: tags -1 + patch

proposed patch at
https://patches.ubuntu.com/t/teckit/teckit_2.5.8+ds2-5ubuntu1.patch

Bug#847190: The following feature isn't implemented by Apache FOP, yet: table-layout="auto" (on fo:table)

2018-11-21 Thread Petter Reinholdtsen

[Mathieu Malaterre]
> I'll upload 2.3 soon to unstable, so removing the tag patch since it
> does not apply anymore.

Would you be willing to carry an updated patch in Debian before it is
applied upstream?
--
Happy hacking
Petter Reinholdtsen

Bug#914266: reproducible: vary running debian/rules binary target under fakeroot/etc

2018-11-21 Thread Paul Wise

Package: jenkins.debian.org
Severity: wishlist
Tags: patch
Usertags: sentpatch

For reproducible builds I would like to perform build2 using fakeroot
even if Rules-Requires-Root is set to no.

This will find packages that really should not have the debian/control
Rules-Requires-Root field set to no.

This will find packages that will build differently with older dpkg
versions that do not support Rules-Requires-Root and always use
fakeroot/etc.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

From 5bbfb0fe95282ab736c798fc039df5b47a587ffc Mon Sep 17 00:00:00 2001
From: Paul Wise 
Date: Wed, 21 Nov 2018 17:50:58 +0800
Subject: [PATCH] reproducible: perform build2 using fakeroot even if
 Rules-Requires-Root is set to no

This will find packages that really should not have Rules-Requires-Root: no

This will find packages that will build differently with older dpkg versions
that do not support Rules-Requires-Root and always use fakeroot/etc.
---
 bin/reproducible_build.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bin/reproducible_build.sh b/bin/reproducible_build.sh
index 8b177d57..158b3dbd 100755
--- a/bin/reproducible_build.sh
+++ b/bin/reproducible_build.sh
@@ -665,7 +665,7 @@ EOF
 		/usr/sbin/pbuilder --build \
 			--configfile $TMPCFG \
 			--hookdir /etc/pbuilder/rebuild-hooks \
-			--debbuildopts "-b --buildinfo-id=${ARCH}" \
+			--debbuildopts "-b --buildinfo-id=${ARCH} --rules-requires-root" \
 			--basetgz /var/cache/pbuilder/$SUITE-reproducible-base.tgz \
 			--buildresult $TMPDIR/b2 \
 			--logfile b2/build.log \
-- 
2.19.1



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

Bug#914159: Problem still present

2018-11-21 Thread Er_Maqui

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

After upgrade to 11.2, gitlab is not giving a 500 internal server error
when configuring GPG key.

But, is only getting one email identity from the key, and it isn't the
identity registered in the user.

On gitlab 10.5, configuring GPG key gives all email identities on the key.

Regards,

https://maqui.darkbolt.net/
Linux registered user ~#363219
PGP keys avaiables at KeyServ. ID: 0x4233E9F2
Los hombres somos esclavos de la historia
-BEGIN PGP SIGNATURE-

iF0EARECAB0WIQQIUZK8y555KYqDrRx8WMDgQjPp8gUCW/UrdwAKCRB8WMDgQjPp
8oIwAKDeG8273BuRkeolDYf4XcRE7fLUnwCgtvCKeMfF2HTgAGmJif0pxezmgdc=
=tyIM
-END PGP SIGNATURE-

Bug#914175: lightning is not installable after binNMUs

2018-11-21 Thread Holger Schröder




Same here, upgrade wants to remove lightning


...

Bug#785130: old version has issues

2018-11-21 Thread Paul Wise

On Thu, 2 Mar 2017 10:34:17 +0100 Rémi Letot wrote:

> Is the new version problematic in any way ?

For the record, when I heard about the eXtremeSHOK fork I checked it
out, but I was very unimpressed with the changes being made so I won't
be updating it to the new version.

Feel free to take over the package if you feel differently.

I think the correct thing to do is to finally get freshclam's support
for third-party signatures into shape and turn this package into a
configuration file drop-in for freshclam.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#914267: mesa: [regression] with Mesa 18.2.5-2 the charackter model in Tomb Raider is no longer rendered.

2018-11-21 Thread Axel R.

Package: mesa
Version: 18.2.5-2
Severity: normal

Dear Maintainer,

I upgraded Mesa to 18.2.5 but in Tomb Raider the main charackter model is no 
longer rendered. After downgrading bakc to Mesa 18.1.9 everything is working 
again and the model is rendered. 
Here are some screens of the bug:
Multiplayer with 18.2.5: https://i.imgur.com/WYBg7mq.jpg
Benchmark with 18.2.5: https://i.imgur.com/L4acazz.jpg
Benchmark after Downgrading back to 18.1.9: https://i.imgur.com/BiR4avk.jpg



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

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

Bug#914268: llvm-toolchain-7: baseline violation on armhf

Source: llvm-toolchain-7
Version: 1:7.0.1~+rc2-1~exp1
Severity: grave
Control: block 912164 by -1
Control: affects -1 src:rust-pulldown-cmark src:mesa src:cargo

LLVM now violates the armhf baseline by using NEON,
this can be reproduced as easy as:

(sid_armhf-dchroot)bunk@abel:~$ llvm-config-7
Illegal instruction
(sid_armhf-dchroot)bunk@abel:~$

gdb confirms that this is due to NEON usage.


Additionally, this also causes FTBFS on some of our buildds:
https://buildd.debian.org/status/fetch.php?pkg=rust-pulldown-cmark&arch=armhf&ver=0.2.0-1&stamp=1542734241&raw=0
https://buildd.debian.org/status/fetch.php?pkg=cargo&arch=armhf&ver=0.31.0-4&stamp=1542700136&raw=0
https://buildd.debian.org/status/fetch.php?pkg=mesa&arch=armhf&ver=18.2.5-2&stamp=1542760450&raw=0

It might even result in silently misbuilt packages, just imagine
mesa would have disabled the feature instead of AC_MSG_ERROR.


Note that these mentioned buildd problems are just the visible
tip of the iceberg, the baseline violation is a problem that
must be fixed even when the buildds change.

Bug#914269: google-i18n-address FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 11

Source: google-i18n-address
Version: 2.3.2-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=google-i18n-address&arch=all&ver=2.3.2-2&stamp=1542749879&raw=0

...
=== FAILURES ===
___ test_downloader_country[None-file_names0-data0] 

tmpdir = local('/tmp/pytest-of-buildd/pytest-1/test_downloader_country_None_f0')
country = None, file_names = ('pl.json', 'us.json', 'all.json')
data = {'all.json': {'PL': 'dat\u0105', 'US': 'data'}, 'pl.json': {'PL': 
'dat\u0105'}, 'us.json': {'US': 'data'}}

@pytest.mark.parametrize('country, file_names, data', [
(None, ('pl.json', 'us.json', 'all.json'), {
'pl.json': {'PL': 'dat\u0105'},
'us.json': {'US': 'data'},
'all.json': {'PL': 'dat\u0105', 'US': 'data'}}),
('PL', ('pl.json', 'all.json'), {
'pl.json': {'PL': 'dat\u0105'},
'all.json': {'PL': 'dat\u0105'}})])
def test_downloader_country(tmpdir, country, file_names, data):
data_dir = tmpdir.join('data')
download(country)
for file_name in file_names:
assert data_dir.join(file_name).exists()
>   assert json.load(
data_dir.join(file_name), encoding='utf-8') == data[file_name]

tests/test_downloader.py:47: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.6/json/__init__.py:296: in load
return loads(fp.read(),
/usr/lib/python3/dist-packages/py/_path/common.py:171: in read
return f.read()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
input = b'{"PL": "dat\xc4\x85"}', final = True

def decode(self, input, final=False):
>   return codecs.ascii_decode(input, self.errors)[0]
E   UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 
11: ordinal not in range(128)

/usr/lib/python3.6/encodings/ascii.py:26: UnicodeDecodeError
 test_downloader_country[PL-file_names1-data1] _

tmpdir = local('/tmp/pytest-of-buildd/pytest-1/test_downloader_country_PL_fil0')
country = 'PL', file_names = ('pl.json', 'all.json')
data = {'all.json': {'PL': 'dat\u0105'}, 'pl.json': {'PL': 'dat\u0105'}}

@pytest.mark.parametrize('country, file_names, data', [
(None, ('pl.json', 'us.json', 'all.json'), {
'pl.json': {'PL': 'dat\u0105'},
'us.json': {'US': 'data'},
'all.json': {'PL': 'dat\u0105', 'US': 'data'}}),
('PL', ('pl.json', 'all.json'), {
'pl.json': {'PL': 'dat\u0105'},
'all.json': {'PL': 'dat\u0105'}})])
def test_downloader_country(tmpdir, country, file_names, data):
data_dir = tmpdir.join('data')
download(country)
for file_name in file_names:
assert data_dir.join(file_name).exists()
>   assert json.load(
data_dir.join(file_name), encoding='utf-8') == data[file_name]

tests/test_downloader.py:47: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.6/json/__init__.py:296: in load
return loads(fp.read(),
/usr/lib/python3/dist-packages/py/_path/common.py:171: in read
return f.read()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
input = b'{"PL": "dat\xc4\x85"}', final = True

def decode(self, input, final=False):
>   return codecs.ascii_decode(input, self.errors)[0]
E   UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 
11: ordinal not in range(128)

/usr/lib/python3.6/encodings/ascii.py:26: UnicodeDecodeError
= 2 failed, 41 passed in 1.04 seconds ==
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.6_i18address/build; python3.6 -m pytest 
tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.7 3.6" 
returned exit code 13
make: *** [debian/rules:5: binary-indep] Error 25

Bug#914270: ruby-sprockets-rails FTBFS: test failure

Source: ruby-sprockets-rails
Version: 2.3.2+git-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=ruby-sprockets-rails&arch=all&ver=2.3.2%2Bgit-1&stamp=1542787326&raw=0

...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/<>/ruby-sprockets-rails-2.3.2+git/debian/ruby-sprockets-rails/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-sprockets-rails/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_helper.rb" 
"test/test_railtie.rb" "test/test_task.rb" -v
/usr/lib/ruby/vendor_ruby/active_support/core_ext/hash/slice.rb:21: warning: 
method redefined; discarding old slice
/usr/lib/ruby/vendor_ruby/active_support/core_ext/hash/keys.rb:8: warning: 
method redefined; discarding old transform_keys
/usr/lib/ruby/vendor_ruby/active_support/core_ext/hash/keys.rb:19: warning: 
method redefined; discarding old transform_keys!
/usr/lib/ruby/vendor_ruby/active_support/core_ext/enumerable.rb:20: warning: 
method redefined; discarding old sum
/usr/lib/ruby/vendor_ruby/active_support/core_ext/object/duplicable.rb:111: 
warning: BigDecimal.new is deprecated; use Kernel.BigDecimal method instead.
Run options: -v --seed 32539

# Running:

AutomaticDependenciesFromHelpersTest#test_ignores_missing_dependencies = 0.37 s 
= .
AutomaticDependenciesFromHelpersTest#test_dependency_added = 0.06 s = .
AutomaticDependenciesFromHelpersTest#test_truth = 0.08 s = .
HelperTest#test_truth = 0.05 s = .
PrecompileHelperTest#test_truth = 0.06 s = .
PrecompileHelperTest#test_debug_mode = 0.07 s = .
PrecompileHelperTest#test_asset_not_precompiled_error = 0.12 s = .
PrecompileHelperTest#test_non_javascripts_and_stylesheets = 0.06 s = .
PrecompileHelperTest#test_public_folder_fallback_works_correctly = 0.07 s = .
DebugDigestHelperTest#test_javascript_include_tag = 0.10 s = .
DebugDigestHelperTest#test_asset_digest_path = 0.06 s = .
DebugDigestHelperTest#test_stylesheet_link_tag = 0.11 s = .
DebugDigestHelperTest#test_stylesheet_path = 0.06 s = .
DebugDigestHelperTest#test_javascript_path = 0.07 s = .
DebugDigestHelperTest#test_asset_url = 0.07 s = .
DebugDigestHelperTest#test_asset_digest = 0.06 s = .
DebugDigestHelperTest#test_truth = 0.07 s = .
RelativeHostHelperTest#test_truth = 0.06 s = .
RelativeHostHelperTest#test_stylesheet_path = 0.06 s = .
RelativeHostHelperTest#test_asset_url = 0.08 s = .
RelativeHostHelperTest#test_javascript_path = 0.06 s = .
NoHostHelperTest#test_javascript_include_tag = 0.06 s = .
NoHostHelperTest#test_javascript_path = 0.07 s = .
NoHostHelperTest#test_stylesheet_link_tag = 0.06 s = .
NoHostHelperTest#test_truth = 0.05 s = .
NoHostHelperTest#test_stylesheet_path = 0.07 s = .
DebugHelperTest#test_truth = 0.06 s = .
DebugHelperTest#test_stylesheet_path = 0.07 s = .
DebugHelperTest#test_javascript_include_tag = 0.10 s = .
DebugHelperTest#test_javascript_path = 0.06 s = .
DebugHelperTest#test_stylesheet_link_tag = 0.10 s = .
DebugManifestHelperTest#test_truth = 0.06 s = .
DebugManifestHelperTest#test_javascript_path = 0.05 s = .
DebugManifestHelperTest#test_absolute_asset_path_error = 0.07 s = .
DebugManifestHelperTest#test_asset_digest = 0.05 s = .
DebugManifestHelperTest#test_javascript_include_tag = 0.06 s = .
DebugManifestHelperTest#test_stylesheet_link_tag = 0.07 s = .
DebugManifestHelperTest#test_asset_digest_path = 0.06 s = .
DebugManifestHelperTest#test_stylesheet_path = 0.07 s = .
TestTask#test_clean = 0.01 s = .
TestTask#test_clobber = 
/<>/ruby-sprockets-rails-2.3.2+git/debian/ruby-sprockets-rails/usr/lib/ruby/vendor_ruby/sprockets/rails/task.rb:53:
 warning: instance variable @cache_path not initialized
0.01 s = .
TestTask#test_precompile = 0.01 s = .
TestTask#test_precompile_without_manifest = 0.01 s = .
NoDigestHelperTest#test_asset_url = 0.07 s = .
NoDigestHelperTest#test_stylesheet_link_tag = 0.08 s = .
NoDigestHelperTest#test_stylesheet_path = 0.06 s = .
NoDigestHelperTest#test_asset_digest = DEPRECATED: Use assert_nil if expecting 
nil from /<>/ruby-sprockets-rails-2.3.2+git/test/test_helper.rb:275. 
This will fail in Minitest 6.
DEPRECATED: Use assert_nil if expecting nil from 
/<>/ruby-sprockets-rails-2.3.2+git/test/test_helper.rb:276. This will 
fail in Minitest 6.
0.06 s = .
NoDigestHelperTest#test_javascript_include_tag = 0.08 s = .
NoDigestHelperTest#test_javascript_path = 0.06 s = .
NoDigestHelperTest#test_truth = 0.06 s = .
DigestHelperTest#test_asset_digest = 0.07 s = .
DigestHelperTest#test_javascript_include_tag = 0.07 s = .
DigestHelperTest#test_asset_digest_path = 0.07 s = .
DigestHelperTest#test

Bug#914271: lintian: Rationale behind hyphen-in-upstream-part-of-debian-changelog-version

2018-11-21 Thread Johannes 'josch' Schauer

Package: lintian
Version: 2.5.112
Severity: normal

Hi,

my package rss-bridge was just tagged with
hyphen-in-upstream-part-of-debian-changelog-version. The description
text reads:

N:   The upstream version in the debian changelog contains one ore more
N:   hyphens. While that is okay according to policy, some tools may croak.

Why is this a lintian warning at all?

Either we know tools that fail to properly parse Debian versions and in
this case we should:

 - file bugs against the tools in question
 - list these tools in the lintian warning

Or there are no tools which fail to properly parse Debian versions in
which case this lintian tag is useless.

Assuming it's the first case, could you please at least extend the
warning message with a list of tools that do not implement proper Debian
version parsing?

I don't think it's useful to fix a problem by curing the symptoms
instead of the cause. If packages now change their versioning style in
response to this lintian tag, then lintian has successfully helped to
hide a bug in other software projects.

Thanks!

cheers, josch

Bug#914272: mysql-5.7: [INTL:tr] turkish translation update

2018-11-21 Thread Atila KOÇ


Package: mysql-5.7
Version: N/A
Severity: wishlist
Tags: l10n patch

Please find attached the Turkish translation of mysql-5.7 package.
It has been submitted for review to the debian-l10n-turkish mailing list.

Regards,
Atila KOÇ

# Turkish translation of mysql-server.
# This file is distributed under the same license as the mysql-server package.
# GÃ¼rkan Aslan , 2004
# Atila KOÃ , 2015, 2018
#
msgid ""
msgstr ""
"Project-Id-Version: mysql-5.7\n"
"Report-Msgid-Bugs-To: mysql-...@packages.debian.org\n"
"POT-Creation-Date: 2018-01-10 07:21+\n"
"PO-Revision-Date: 2018-11-05 14:07+0300\n"
"Last-Translator: Atila KOÃ \n"
"Language-Team: Turkish \n"
"Language: tr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Poedit 1.8.11\n"

#. Type: note
#. Description
#: ../mysql-server-5.7.templates:2001
msgid "Automatic maintenance of MySQL server daemon disabled"
msgstr "MySQL sunucusunun kendiliÄinden bakÄ±mÄ± devre dÄ±ÅÄ±"

#. Type: note
#. Description
#: ../mysql-server-5.7.templates:2001
msgid ""
"Packaging maintainer scripts detected a case that it does not know how to "
"handle and cannot continue configuring MySQL. Automatic management of your "
"MySQL installation has been disabled to allow other packaging tasks to "
"complete. For more details, see /etc/mysql/FROZEN."
msgstr ""
"Paketleme yÃ¶netim betikleri nasÄ±l Ã§Ã¶zeceÄini bilemediÄi bir durum ile "
"karÅÄ±laÅtÄ±ÄÄ±ndan MySQL yapÄ±landÄ±rmasÄ±nÄ± sÃ¼rdÃ¼remeyecek. DiÄer paketleme "
"gÃ¶revlerinin tamamlanabilmesi iÃ§in MySQL kurulumunuzun kendiliÄinden "
"yÃ¶netimi devre dÄ±ÅÄ± bÄ±rakÄ±ldÄ±. Daha fazla bilgi iÃ§in /etc/mysql/FROZEN "
"dosyasÄ±na bakÄ±n."

#. Type: note
#. Description
#: ../mysql-server-5.7.templates:3001
msgid "Important note for NIS/YP users"
msgstr "NIS/YP kullanÄ±cÄ±larÄ± iÃ§in Ã¶nemli not"

#. Type: note
#. Description
#: ../mysql-server-5.7.templates:3001
msgid ""
"Using MySQL under NIS/YP requires a mysql user account to be added on the "
"local system with:"
msgstr ""
"MySQL'in NIS/YP ile kullanÄ±lmasÄ± iÃ§in aÅaÄÄ±daki komut Ã§alÄ±ÅtÄ±rÄ±larak bir "
"mysql kullanÄ±cÄ± hesabÄ±nÄ±n yerel sisteme eklenmesi gereklidir:"

#. Type: note
#. Description
#: ../mysql-server-5.7.templates:3001
msgid ""
"You should also check the permissions and ownership of the /var/lib/mysql "
"directory:"
msgstr ""
"/var/lib/mysql dizininin sahiplik ve izin ayarlarÄ±nÄ± da gÃ¶zden "
"geÃ§irmelisiniz:"

#. Type: boolean
#. Description
#: ../mysql-server-5.7.templates:4001
msgid "Remove all MySQL databases?"
msgstr "TÃ¼m MySQL veritabanlarÄ± kaldÄ±rÄ±lsÄ±n mÄ±?"

#. Type: boolean
#. Description
#: ../mysql-server-5.7.templates:4001
msgid ""
"The /var/lib/mysql directory which contains the MySQL databases is about to "
"be removed."
msgstr ""
"MySQL veritabanlarÄ±nÄ± barÄ±ndÄ±ran /var/lib/mysql dizini kaldÄ±rÄ±lmak Ã¼zere"

#. Type: boolean
#. Description
#: ../mysql-server-5.7.templates:4001
msgid ""
"This will also erase all data in /var/lib/mysql-files as well as /var/lib/"
"mysql-keyring."
msgstr ""
"Bu aynÄ± zamanda /var/lib/mysql-files ve /var/lib/mysql-keyring "
"dosyalarÄ±ndaki tÃ¼m verileri de silecek."

#. Type: boolean
#. Description
#: ../mysql-server-5.7.templates:4001
msgid ""
"If you're removing the MySQL package in order to later install a more recent "
"version or if a different mysql-server package is already using it, the data "
"should be kept."
msgstr ""
"EÄer MySQL paketini sonrasÄ±nda daha gÃ¼ncel bir sÃ¼rÃ¼mÃ¼nÃ¼ kurmak Ã¼zere "
"kaldÄ±rÄ±yorsanÄ±z ya da veritabanlarÄ±nÄ±za baÅka bir mysql-server paketi ile "
"eriÅiyorsanÄ±z, veritabanlarÄ±nÄ±zÄ± kaldÄ±rmamalÄ±sÄ±nÄ±z."

#. Type: boolean
#. Description
#: ../mysql-server-5.7.templates:5001
msgid "Start the MySQL server on boot?"
msgstr "MySQL aÃ§Ä±lÄ±Å sÄ±rasÄ±nda kendiliÄinden baÅlatÄ±lsÄ±n mÄ±?"

#. Type: boolean
#. Description
#: ../mysql-server-5.7.templates:5001
msgid ""
"The MySQL server can be launched automatically at boot time or manually with "
"the '/etc/init.d/mysql start' command."
msgstr ""
"MySQL sunucusu aÃ§Ä±lÄ±Å sÄ±rasÄ±nda kendiliÄinden ya da sonradan elle '/etc/init."
"d/mysql start' komutu Ã§alÄ±ÅtÄ±rÄ±larak baÅlatÄ±labilir."

#. Type: password
#. Description
#: ../mysql-server-5.7.templates:6001
msgid "New password for the MySQL \"root\" user:"
msgstr "MySQL \"root\" kullanÄ±cÄ±sÄ± iÃ§in yeni parola:"

#. Type: password
#. Description
#: ../mysql-server-5.7.templates:6001
msgid ""
"While not mandatory, it is highly recommended that you set a password for "
"the MySQL administrative \"root\" user."
msgstr ""
"Zorunlu olmasa da MySQL yÃ¶netimsel \"root\" kullanÄ±cÄ±sÄ± iÃ§in bir parola "
"oluÅturulmasÄ± kuvvetle Ã¶nerilir."

#. Type: password
#. Description
#: ../mysql-server-5.7.templates:6001
msgid "If this field is left blank, the password will not be changed."
msgstr "Bu alanÄ±n boÅ bÄ±rakÄ±lmasÄ± durumunda parola deÄiÅti

Bug#914273: symfony fails a lot of autopkg tests, even on amd64

Package: src:symfony
Version: 3.4.17+dfsg-1
Severity: serious
Tags: sid buster
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

please see
https://ci.debian.net/data/packages/unstable/amd64/s/symfony/latest-autopkgtest/log.gz

for the failed tests

Bug#912790: llvmlite: Please switch to llvm-toolchain-7

2018-11-21 Thread Daniel Stender


Upstream needs some time to adapt, v0.26.0rc1 (released recently):

"LLVM 7 support was originally slated for this release, but had to be delayed
after some issues arose in testing.  LLVM 6 is still required for llvmlite."

DS

--
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/

Bug#914274: please package python3 version

2018-11-21 Thread Per Andersson

Package: python-ibm-db-sa
Severity: wishlist
Control: block 914253 by -1

Dear maintainer,

Please add a python3 version e.g. python3-ibm-db-sa.

It is a build dependency for python-sqlalchemy-migrate.


--
Per


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

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

Versions of packages python-ibm-db-sa depends on:
ii  dpkg   1.19.2
ii  python 2.7.15-3
ii  python-sqlalchemy  1.2.8+ds1-1

python-ibm-db-sa recommends no packages.

python-ibm-db-sa suggests no packages.

Bug#914275: Massive /etc/services reindent obscuring changes

2018-11-21 Thread Steve McIntyre

Package: netbase
Version: 5.5
Severity: minor

Why was /etc/services totally reindented and switched from spaces to
tabs going from 5.4 to 5.5? Every single sid chroot on all my machines
demanded attention becasue of this change. That includes newly-created
chroots where I've made no changes at all to the original file, which
is worrying.

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

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

-- no debconf information

Bug#578523: command-not-found: no automatic updating of cache

On Tue, Apr 20, 2010 at 07:07:24PM +0300, Julian Gilbey wrote:
> Package: command-not-found
> Version: 0.2.38-1
> Severity: important
> 
> The package should run update-command-not-found on installation,
> possibly asking a debconf question first.  It should also do this on a
> regular basis via a cron job.  (This could be enabled/disabled via an
> entry in /etc/default/command-not-found.)

JFTR: The database is now updated during apt(-file) update in 18.04.5-1, or
by manually running the update tool. update-command-not-found is a symlink
to cnf-update-db in /usr/share/command-not-found (and /usr/lib), I think
I might drop it eventually, as it's not really necessary anymore.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#914276: monkeysign tries to access an external key server during the tests

Package: src:monkeysign
Version: 2.2.4
Severity: important
Tags: sid buster
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

monkeysign tries to access an external key server during the tests, and then in
a restricted test environment, it fails tests.  Please either use a proxy or
disable the tests with network access.

Bug#914273: symfony fails a lot of autopkg tests, even on amd64

2018-11-21 Thread Karlos GNU CON KERNEL LINUX

Bug#913069: transition: python3.7 as default

Control: tags -1 confirmed

On 17/11/2018 18:43, Mattia Rizzolo wrote:
> On Sat, Nov 17, 2018 at 12:05:33PM +0100, Emilio Pozuelo Monfort wrote:
>>> affects: .build-depends ~ /python3-dev/ | .build-depends ~ /python3-dbg/
>>> good: .depends ~ /python3 \(<< 3\.8\)/ | .depends ~ /(lib)?python3\.7/ | 
>>> .depends ~ /python3-dbg \(<< 3\.8\)/ | .depends ~ /(lib)?python3\.7-dbg/
>>> bad: .depends ~ /python3 \(<< 3\.7\)/ | (.depends ~ /(lib)?python3\.6/ & 
>>> !.depends ~ /(lib)?python3\.7/) | .breaks ~ /python \(>= 3\.7\)/ | .depends 
>>> ~ /python3-dbg \(<< 3\.7\)/ | .breaks ~ /python3-dbg \(>= 3\.7\)/
>>
>>
>> I have reused the previous python3.6-default tracker instead.
>> Shout if more of those are needed.
> 
> this being the default change means the -all- ones shouldn't be bothered
> in theory_, but well, that one you used should also be good enough.

Hmm, yeah, there seems to be too many noise in there. Should I remove the -all-
ones from is_affected?

>> Let's wait a bit for the buildds to catch up with boost et al, then
>> I'll ack this.

Some arches are having a little trouble catching up, but let's go ahead with
this and I'll slowly schedule the binNMUs.

Cheers,
Emilio

Bug#913210: transition: libqalculate

Control: tags -1 confirmed

On 08/11/2018 07:12, Vincent Legout wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hello,
> 
> I'd like to request a transition slot for libqalculate.
> 
> The new version is in experimental. It has 4 reverse dependencies.
> qalculate-gtk has also been uploaded to experimental, and I plan to
> upload it to unstable just after libqalculate. The other 3 build fine
> with the new version.

Go ahead.

Emilio

Bug#914271: lintian: Rationale behind hyphen-in-upstream-part-of-debian-changelog-version

[adding felix.lech...@lease-up.com to CC]

Hi Johannes,

> my package rss-bridge was just tagged with […]

As it wasn't immediately obvious from the bug report-alone

 rss-bridge | 2018-07-17-1.2 | buster | source, all
 rss-bridge | 2018-07-17-1.2 | sid| source, all
  

> N:   The upstream version in the debian changelog contains one ore more
> N:   hyphens. While that is okay according to policy, some tools may croak.
> 
> Why is this a lintian warning at all?

This was added in:

  
https://salsa.debian.org/lintian/lintian/commit/0005c81dc200a0787a2716aacd6e00f859101c36

Felix, can you clarify to josch here? I would agree with the
sentiment that we should just fix the other tools instead of
warning here.


Best wishes,

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

Bug#914253: ITP: python-sqlalchemy-migrate -- Database schema migration for SQLAlchemy

2018-11-21 Thread Arto Jantunen

Per Andersson  writes:

> Package: wnpp
> Severity: wishlist
> Owner: Per Andersson 
>
> * Package name: python-sqlalchemy-migrate
>   Version : 0.11.0
>   Upstream Author : OpenStack 
> * URL : https://pypi.org/project/sqlalchemy-migrate/
> * License : MIT/Expat
>   Programming Lang: Python
>   Description : Database schema migration for SQLAlchemy
>
> Inspired by Ruby on Rails’ migrations, Migrate provides a way to deal
> with database schema changes in SQLAlchemy projects.
>
> Migrate extends SQLAlchemy to have database changeset handling. It
> provides a database change repository mechanism which can be used from
> the command line as well as from inside python code.
>
> This is required for new versions of pytrainer.
>
> I plan to maintain this in the Python Modules Team.
>

This is already packaged as python-migrate by the Openstack team. It
might be a different upstream fork, though.

-- 
Arto Jantunen

Bug#913069: transition: python3.7 as default

2018-11-21 Thread Mattia Rizzolo

On Wed, Nov 21, 2018 at 01:01:45PM +0100, Emilio Pozuelo Monfort wrote:
> >> I have reused the previous python3.6-default tracker instead.
> >> Shout if more of those are needed.
> > 
> > this being the default change means the -all- ones shouldn't be bothered
> > in theory_, but well, that one you used should also be good enough.
> 
> Hmm, yeah, there seems to be too many noise in there. Should I remove the 
> -all-
> ones from is_affected?

I think so, yes.
Those will turn up while removing py3.6 anyway, and will receive a bug
if I see them (and corrisponding fix upload if I can).

> Some arches are having a little trouble catching up, but let's go ahead with
> this and I'll slowly schedule the binNMUs.

Matthis, this is your clue ;)

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#914277: firmware-iwlwifi: Microcode error in adhoc mode

2018-11-21 Thread Mark van Rossum

Package: firmware-iwlwifi
Version: 20180825+dfsg-1
Severity: normal

Dear Maintainer,

Dear Maintainer,

I'm trying to set up an adhoc network with my 6205 Intel card.

> iwconfig wlp3s0 mode ad-hoc essid test key 1234567890


Every time I run
> ifconfig wlp3s0 up
it replies
> SIOCSIFFLAGS: Input/output error

The adhoc network does not come up.
Other network types run fine.
I see the following in the log (below).

I'm not sure it is a firmware issue, but it is the first suspicious log entry.


Nov 21 10:57:38 x220 kernel: [ 1423.333829] iwlwifi :03:00.0: Radio
type=0x1-0x2-0x0
Nov 21 10:57:39 x220 kernel: [ 1423.630185] iwlwifi :03:00.0: Radio
type=0x1-0x2-0x0
=> Nov 21 10:57:39 x220 kernel: [ 1423.713443] iwlwifi :03:00.0: Microcode
SW error detected.  Restarting 0x8200.
Nov 21 10:57:39 x220 kernel: [ 1423.713459] iwlwifi :03:00.0: Loaded
firmware version: 18.168.6.1
Nov 21 10:57:39 x220 kernel: [ 1423.713607] iwlwifi :03:00.0: Start IWL
Error Log Dump:
Nov 21 10:57:39 x220 kernel: [ 1423.713614] iwlwifi :03:00.0: Status:
0x000C, count: 6
Nov 21 10:57:39 x220 kernel: [ 1423.713621] iwlwifi :03:00.0: 0x14E7 |
ADVANCED_SYSASSERT
Nov 21 10:57:39 x220 kernel: [ 1423.713628] iwlwifi :03:00.0: 0x000178A0 |
uPc
Nov 21 10:57:39 x220 kernel: [ 1423.713634] iwlwifi :03:00.0: 0x00017886 |
branchlink1
Nov 21 10:57:39 x220 kernel: [ 1423.713640] iwlwifi :03:00.0: 0x00017886 |
branchlink2
Nov 21 10:57:39 x220 kernel: [ 1423.713646] iwlwifi :03:00.0: 0xD6BE |
interruptlink1
Nov 21 10:57:39 x220 kernel: [ 1423.713652] iwlwifi :03:00.0: 0x |
interruptlink2
Nov 21 10:57:39 x220 kernel: [ 1423.713658] iwlwifi :03:00.0: 0x |
data1
Nov 21 10:57:39 x220 kernel: [ 1423.713664] iwlwifi :03:00.0: 0x0064 |
data2
Nov 21 10:57:39 x220 kernel: [ 1423.713670] iwlwifi :03:00.0: 0x035D |
line
Nov 21 10:57:39 x220 kernel: [ 1423.713676] iwlwifi :03:00.0: 0x711E |
beacon time
Nov 21 10:57:39 x220 kernel: [ 1423.713682] iwlwifi :03:00.0: 0x00011EE2 |
tsf low
Nov 21 10:57:39 x220 kernel: [ 1423.713688] iwlwifi :03:00.0: 0x |
tsf hi
Nov 21 10:57:39 x220 kernel: [ 1423.713694] iwlwifi :03:00.0: 0x |
time gp1
Nov 21 10:57:39 x220 kernel: [ 1423.713700] iwlwifi :03:00.0: 0x00011EE7 |
time gp2
Nov 21 10:57:39 x220 kernel: [ 1423.713706] iwlwifi :03:00.0: 0x |
time gp3
Nov 21 10:57:39 x220 kernel: [ 1423.713712] iwlwifi :03:00.0: 0x754312A8 |
uCode version
Nov 21 10:57:39 x220 kernel: [ 1423.713718] iwlwifi :03:00.0: 0x00B0 |
hw version
Nov 21 10:57:39 x220 kernel: [ 1423.713724] iwlwifi :03:00.0: 0x00488700 |
board version
Nov 21 10:57:39 x220 kernel: [ 1423.713731] iwlwifi :03:00.0: 0x090A0010 |
hcmd
Nov 21 10:57:39 x220 kernel: [ 1423.713737] iwlwifi :03:00.0: 0x00122080 |
isr0
Nov 21 10:57:39 x220 kernel: [ 1423.713743] iwlwifi :03:00.0: 0x |
isr1
Nov 21 10:57:39 x220 kernel: [ 1423.713749] iwlwifi :03:00.0: 0x0602 |
isr2
Nov 21 10:57:39 x220 kernel: [ 1423.713755] iwlwifi :03:00.0: 0x014000C0 |
isr3
Nov 21 10:57:39 x220 kernel: [ 1423.713760] iwlwifi :03:00.0: 0x |
isr4
Nov 21 10:57:39 x220 kernel: [ 1423.713767] iwlwifi :03:00.0: 0x01000112 |
isr_pref
Nov 21 10:57:39 x220 kernel: [ 1423.713773] iwlwifi :03:00.0: 0x00024B96 |
wait_event
Nov 21 10:57:39 x220 kernel: [ 1423.713779] iwlwifi :03:00.0: 0x |
l2p_control
Nov 21 10:57:39 x220 kernel: [ 1423.713785] iwlwifi :03:00.0: 0x |
l2p_duration
Nov 21 10:57:39 x220 kernel: [ 1423.713791] iwlwifi :03:00.0: 0x |
l2p_mhvalid
Nov 21 10:57:39 x220 kernel: [ 1423.713797] iwlwifi :03:00.0: 0x |
l2p_addr_match
Nov 21 10:57:39 x220 kernel: [ 1423.713803] iwlwifi :03:00.0: 0x0047 |
lmpm_pmg_sel
Nov 21 10:57:39 x220 kernel: [ 1423.713809] iwlwifi :03:00.0: 0x06061222 |
timestamp
Nov 21 10:57:39 x220 kernel: [ 1423.713815] iwlwifi :03:00.0: 0x0818 |
flow_handler
Nov 21 10:57:39 x220 kernel: [ 1423.713884] iwlwifi :03:00.0: Start IWL
Event Log Dump: nothing in log
Nov 21 10:57:39 x220 kernel: [ 1423.713973] iwlwifi :03:00.0: FW error in
SYNC CMD REPLY_RXON
Nov 21 10:57:39 x220 kernel: [ 1423.713994] CPU: 3 PID: 6189 Comm: ifconfig
Tainted: GW  O  4.18.6-mvr #1
Nov 21 10:57:39 x220 kernel: [ 1423.714001] Hardware name: LENOVO
429137G/429137G, BIOS 8DET76WW (1.46 ) 06/21/2018
Nov 21 10:57:39 x220 kernel: [ 1423.714007] Call Trace:
Nov 21 10:57:39 x220 kernel: [ 1423.714033]  dump_stack+0x5c/0x82
Nov 21 10:57:39 x220 kernel: [ 1423.714068]
iwl_trans_pcie_send_hcmd+0x499/0x4b0 [iwlwifi]
Nov 21 10:57:39 x220 kernel: [ 1423.714085]  ? finish_wait+0x80/0x80
Nov 21 10:57:39 x220 kernel: [ 1423.714111]  iwl_trans_send_cmd+0x61/0xd0
[iwlwifi]
Nov 21 10:57:39 x220 kernel: [ 1423.714136]  iwl_dvm_send_cmd_pdu+0x55/0x70
[iwldvm]
Nov 21 10:57:39 x220 kernel: [ 1423.714157]  iwlagn_commit_rxon+0x4c0/0xa70
[iwldvm]
Nov

Bug#807120:

2018-11-21 Thread matthew sporleder

you might want to check a more updated version of 2.4 than 2.4.10

Bug#914278: openjdk-11: Reproducible properties file header when SOURCE_DATE_EPOCH is specified

2018-11-21 Thread Emmanuel Bourg

Source: openjdk-11
Severity: normal
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps toolchain

When writing a properties file using the java.util.Properties class, a header
containing the current date is automatically added. This renders the output non
reproducible.

Here is a patch for java.util.Properties checking if the SOURCE_DATE_EPOCH
environment variable is specified and using it instead of the current date
for the timestamp.
Description: Makes the timestamp in the properties files header reproducible 
when SOURCE_DATE_EPOCH is specified
Author: Emmanuel Bourg 
Forwarded: no
--- a/src/java.base/share/classes/java/util/Properties.java
+++ b/src/java.base/share/classes/java/util/Properties.java
@@ -905,7 +905,7 @@
 if (comments != null) {
 writeComments(bw, comments);
 }
-bw.write("#" + new Date().toString());
+bw.write("#" + getFormattedTimestamp());
 bw.newLine();
 synchronized (this) {
 for (Map.Entry e : entrySet()) {
@@ -1555,4 +1555,22 @@
 }
 this.map = map;
 }
+
+/**
+ * Returns a formatted timestamp to be used in the properties file header.
+ * The date used is the current date, unless the SOURCE_DATE_EPOCH
+ * environment variable is specified. In this case the format used is
+ * locale and timezone insensitive to ensure the output is reproducible.
+ */
+private String getFormattedTimestamp() {
+if (System.getenv("SOURCE_DATE_EPOCH") == null) {
+return new Date().toString();
+} else {
+// Use the SOURCE_DATE_EPOCH timestamp and make the format 
locale/timezone insensitive
+java.text.SimpleDateFormat fmt = new 
java.text.SimpleDateFormat("-MM-dd HH:mm:ss z", java.util.Locale.ENGLISH);
+fmt.setTimeZone(java.util.TimeZone.getTimeZone("UTC"));
+Date date = new Date(1000 * 
Long.parseLong(System.getenv("SOURCE_DATE_EPOCH")));
+return fmt.format(date);
+}
+}
 }

Bug#914280: git-buildpackage: Correct "saving" typo

Source: git-buildpackage
Version: 0.9.10+nmu1
Severity: minor
Tags: patch

Hi,

Patch attached that corrects a "saving" typo.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/gbp/scripts/pq.py b/gbp/scripts/pq.py
index babff1c..794617a 100755
--- a/gbp/scripts/pq.py
+++ b/gbp/scripts/pq.py
@@ -260,7 +260,7 @@ def safe_patches(series, repo):
 patches = os.path.join(tmpdir, 'patches')
 series = os.path.join(patches, name)
 
-gbp.log.debug("Safeing patches '%s' in '%s'" % (src, tmpdir))
+gbp.log.debug("Saving patches '%s' in '%s'" % (src, tmpdir))
 shutil.copytree(src, patches)
 
 return (tmpdir, series)

Bug#914279: RM: mercurial-nested -- ROM; abandoned by upstream

2018-11-21 Thread Mathias Behrle

Package: ftp.debian.org
Severity: normal
X-CC-Debugs: maintain...@debian.tryton.org

The maintainer has declared to not support furthermore hgnested and it is
currently yet unsupported for the current mercurial version.

Reverse Depends:
 None


-- 

Mathias Behrle
PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6


pgpVnDOC6mfP_.pgp
Description: Digitale Signatur von OpenPGP

Bug#914281: git-buildpackage: -Pq suffixes not actually optional

Package: git-buildpackage
Version: 0.9.10+nmu1
Severity: normal

Hi,

The documentation claims that the -Pq suffixes are optional but
they appear not to be. For example, writing this new commit message
on the exported branch:

  Subject line here

  Gbp: Name target-filename.patch

… when exported yields a "0001-Subject-line-here.patch" file
instead of "target-filename.patch". The code in question appears to
be:

cmds = {'topic': topic} if topic else {}
# Parse 'Gbp: ' style commands
(cmds_gbp, info['body']) = parse_gbp_commands(info, 'gbp',
  ('ignore'),
  ('topic', 'name'),
  ('topic', 'name'))
cmds.update(cmds)
# Parse 'Gbp-Pq: ' style commands
(cmds_gbp_pq, info['body']) = parse_gbp_commands(info,
 'gbp-pq',
 ('ignore'),
 ('topic', 'name'),
 ('topic', 'name'))
cmds.update(cmds_gbp_pq)


(Are we, perhaps not finding the 'Name' in the second call to
`parse_gbp_commands` and then removing the name from `cmds`?)


Regards,

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

Bug#914278: openjdk-11: Reproducible properties file header when SOURCE_DATE_EPOCH is specified

Hi,

> openjdk-11: Reproducible properties file header when
> SOURCE_DATE_EPOCH is specified

Thanks for this patch! I've updated the reference to the
corresponding "issue" in our Git repository here:

  
https://salsa.debian.org/reproducible-builds/reproducible-notes/commit/6e9c5774bfc3f16f5bb03f1563af058dc3d733e2


Regards,

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

Bug#914282: O: multistrap -- multiple repository bootstrap based on apt

2018-11-21 Thread Johannes 'josch' Schauer

Package: wnpp
Severity: normal

I intend to orphan the multistrap package.

The package description is:
A debootstrap replacement with multiple repository support,
using apt to handle all dependency issues and conflicts.
.
Multistrap includes support for native and foreign architecture
bootstrap environments. Foreign bootstraps only need minimal
configuration on the final device. Also supports cleaning up the
generated bootstrap filesystem to remove downloaded packages and
hooks to modify the files in the bootstrap filesystem after the
packages have been unpacked but before being configured.
.
Unlike debootstrap, multistrap relies on working versions of
dpkg and apt outside the final filesystem. If dpkg supports
MultiArch, foreign architecture libraries can be installed,
where available.

I took over multistrap maintainership in 2016 because it provides many
advantages over debootstrap because it uses apt as a backend. This in
turn allows multiple repositories, resolution of complex dependencies
and installing foreign architecture packages.

Unfortunately I was never very happy with the codebase which led me to a
big 1500-line-diff rewrite of the codebase:

https://gitlab.mister-muffin.de/josch/multistrap/commit/ff96767b2f6a574e2651768225ad61557880e12f

Followed by a 1842-line-diff commit which even more restructured the
codebase:

https://gitlab.mister-muffin.de/josch/multistrap/commit/cd5dfbbbf2435bae8fc34ac32ee7d716c24bada8

But I still wasn't happy and realized that to make myself happy, I would
have to change behaviour of multistrap that would make its interface
incompatible with earlier versions.

In the end, I ended up with a complete rewrite and out came my package
mmdebstrap:

https://tracker.debian.org/pkg/mmdebstrap

Similar to multistrap it uses apt at its core but in contrast to
multistrap it doesn't offer a configuration file system.

Unfortunately I'm very happy with mmdebstrap and thus I now decided to
not spend more time into multistrap. I did a last upload that fixes a
FTBFS issue and its last outstanding RC bug but after that it's now
orphaned.

Bug#914267: mesa: [regression] with Mesa 18.2.5-2 the charackter model in Tomb Raider is no longer rendered.

2018-11-21 Thread Bogdan Vatra

I can confirm this issue, on a Radeon RX 580.

BogDan.

Bug#914153: Update to version 2.3.0-3 breaks Megaglest

2018-11-21 Thread Manuel A. Fernandez Montecelo

Control: tags -1 + serious

Hi,

Em qua, 21 de nov de 2018 às 02:10, Frank Heckenbach
 escreveu:
>
> Hi Evgeny,
>
> > >After updating libftgl2 from version 2.1.3~rc5-5 to version 2.3.0-3, text 
> > >rendering in Megaglest is broken. Text is shown correctly in menus, but 
> > >text displayed in the game itself is replaced by white rectangles.
> >
> > Thanks for the report.
> >
> > Any idea of what's going on, Frank?
> >
> > For me it works in some menus, there are white squares in others.  zaz,
> > another application using ftgl, seems to work fine, while critterding
> > also shows white squares.
>
> That's probably a consequence of a fix made by sammy in 2009(!)
> (commit 29603ae: "Remove GL_BLEND tampering. It's the caller
> application's responsibility to enable or disable blending").
>
> For some reason, that patch (and a few others) hadn't made it into
> Debian before and only now got in as a "bycatch" when we
> synchronized everything.
>
> Though it is an incompatible change, it was a necessary one, since
> what the library did before was wrong (which prompted a bug report
> of my own, #742469 which would solve it for some particular cases
> while adding a dependency on GL_GLEXT_PROTOTYPES). So the better
> solution is probably the earlier (and now current) one which puts
> the responsibility on the caller.
>
> I had seen the same problem in another test program recently, and in
> this case it helped to add the following two lines in an appropriate
> place. You can try the same in your code (shouldn't hurt if compiled
> with older ftgl versions as well):
>
>   glEnable(GL_BLEND);
>   glBlendFunc(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA);
>
> Or, if you like a better blending function (see my description in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742469), you can
> use this instead:
>
> #define GL_GLEXT_PROTOTYPES
>
>   glEnable(GL_BLEND);
>   glBlendFuncSeparate(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA,
>   GL_ONE, GL_ONE_MINUS_SRC_ALPHA);

I think that we should revert this change for the time being, though,
because if it was working in this way for about a decade and the
programs using FTGL worked "fine" despite having some bug there,
there's no need to change this now and break applications with only a
few weeks to fix this in 15+ other packages before the freeze.

Otherwise we have to get the fix in several of this packages, which is
way more difficult, specially if not well maintained in Debian,
upstream or both.


Cheers.
-- 
Manuel A. Fernandez Montecelo

Bug#914249: Bug #914249: gimp: GIMP Crashed when I was editing a image

2018-11-21 Thread Bernhard Übelacker

Dear Maintainer,
just tried to reconstruct a better readable stack with
function names, that would probably look like this:


0x...e27 | 0x779c9e27: 0x779c9e22 : 
callq  0x779bf150 
0x...4a0 | 0x556274a0: 0x5562749b :   callq  
0x55621790 
0x...8d8 | 0x556278d8: 0x556278d3 :
callq  0x556271b0 
0x...037 | 0x55628037 :   callq  
0x556278f0 
0x...8e0 | 0x767068e0 <__restore_rt+0>: mov$0xf,%rax  ; 
0x...f3b | 0x7656bf3b: 0x7656bf39 <__GI_raise+265>: syscall 
0x...2f1 | 0x7656d2f1: 0x7656d2ec <__GI_abort+332>: callq  
0x7656be30 <__GI_raise>  ; abort.c:79raise (SIGABRT);
0x...a8a | 0x76564a8a: 0x76564a85 <__assert_fail_base+325>: 
callq  0x7656d1a0 <__GI_abort>
0x...b02 | 0x76564b02: 0x76564afd <__GI___assert_fail+61>:  
callq  0x76564940 <__assert_fail_base>
0x...6bb | 0x764326bb: 0x764326b6 : 
callq  0x7640bdd0 <__assert_fail@plt>
0x...760 | 0x76432760 in poll_for_response (...) at 
../../src/xcb_io.c:303
0x...a5d | 0x76432a5d in _XEventsQueued (...) at ../../src/xcb_io.c:363
0x...7b7 | 0x764247b7 in XPending (...) at ../../src/Pending.c:55
0x...8d5 | 0x77a8a8d5 in gdk_check_xpending (...) at 
./gdk/x11/gdkevents-x11.c:159
0x...821 | 0x768fc821 in g_main_context_check (...) at 
../../../../glib/gmain.c:3753
0x...df0 | 0x768fcdf0 in g_main_context_iterate (...) at 
../../../../glib/gmain.c:3917
0x...1d2 | 0x768fd1d2 in g_main_loop_run (...) at 
../../../../glib/gmain.c:4116
0x...cb7 | 0x55626cb7 in app_run (...) at app.c:440
0x...5b5 | 0x556265b5 in main (...) at main.c:524


I assume the point where things started to go wrong is in function 
poll_for_event.


disassemble /m poll_for_event
...
260 throw_thread_fail_assert("Unknown 
sequence "
   0x7643269c : lea0x7241d(%rip),%rcx   
 # 0x764a4ac0 <__PRETTY_FUNCTION__.15060>
   0x764326a3 : mov$0x107,%edx
   0x764326a8 : lea0x71fc4(%rip),%rsi   
 # 0x764a4673
   0x764326af : lea0x72152(%rip),%rdi   
 # 0x764a4808
   0x764326b6 : callq  0x7640bdd0 
<__assert_fail@plt>
   0x764326bb:  nopl   0x0(%rax,%rax,1)
...
(xcb_io.c)


(gdb) list poll_for_event
233 static xcb_generic_reply_t *poll_for_event(Display *dpy, Bool 
queued_only)
...
258 if (XLIB_SEQUENCE_COMPARE(event_sequence, >, 
request))
259 {
260 throw_thread_fail_assert("Unknown 
sequence "
261  "number while "
262  "processing 
queue",
263 
xcb_xlib_threads_sequence_lost);


If this issue is reproducable the output, when started from a terminal,
could give further information.

In that case would it also be great to have gdb and the debug symbols
installed like described in [1].

Kind regards,
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace
> fatal error: Abortado

Stack trace:
```
/usr/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x397)[0x7f8ed515fe27]
gimp-2.10(+0xd34a0)[0x559a57d004a0]
gimp-2.10(+0xd38d8)[0x559a57d008d8]
gimp-2.10(+0xd4037)[0x559a57d01037]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x128e0)[0x7f8ed3e9d8e0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7f8ed3d01f3b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x151)[0x7f8ed3d032f1]
/lib/x86_64-linux-gnu/libc.so.6(+0x2ea8a)[0x7f8ed3cfaa8a]
/lib/x86_64-linux-gnu/libc.so.6(+0x2eb02)[0x7f8ed3cfab02]
/usr/lib/x86_64-linux-gnu/libX11.so.6(+0x436bb)[0x7f8ed3bc86bb]
/usr/lib/x86_64-linux-gnu/libX11.so.6(+0x43760)[0x7f8ed3bc8760]
/usr/lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x5d)[0x7f8ed3bc8a5d]
/usr/lib/x86_64-linux-gnu/libX11.so.6(XPending+0x57)[0x7f8ed3bba7b7]
/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(+0x588d5)[0x7f8ed52208d5]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_check+0x1e1)[0x7f8ed4092821]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4ddf0)[0x7f8ed4092df0]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0xb2)[0x7f8ed40931d2]
gimp-2.10(app_run+0x357)[0x559a57cffcb7]
gimp-2.10(main+0x395)[0x559a57cff5b5]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f8ed3ceeb17]
gimp-2.10(_start+0x2a)[0x559a57cff73a]

```



apt install devscripts dpkg-dev xserver-xorg lightdm openbox gdb dbus-x11 gimp 
gimp-dbgsym libglib2.0-0-dbgsym libgtk2.0-0-dbgsym libx11-6-dbgsym libc6-dbg 

systemctl start lightdm


mkdir glibc/orig -p
cdglibc/orig
apt source glibc
cd ../..

mkdir libx11-6/orig -p
cdlibx11-6/orig
apt source libx11-6
cd ../..





export DISPLAY=:0
gdb -q --args gimp

directory /home/benutzer/glibc/ori

Bug#914174: RFS: easy-rsa [ITA]

2018-11-21 Thread Michele Orru


On 11/21/18 6:45 AM, Adam Borowski wrote:

On Tue, Nov 20, 2018 at 08:45:09AM +0100, Michele Orrù wrote:

* Package name: easy-rsa
   Version : 3.0.5-1



https://salsa.debian.org/maker-guest/easy-rsa/

Changes since the last upload:

* New upstream version 3.0.5
* Updated d/README.Debian


Hi!
The package's changelog is set as UNRELEASED, which marks the current state
as not meant for upload.

The changelog doesn't also list your takeover.

The package fails to build:
dh_installdocs: Cannot find (any matches for) 
"debian/README-Debian-much-features-such-wow" (tried in ., debian/tmp)
(the file is deleted in the packaging now)

Rules-Require-Root should be "Requires".



Hi,


thanks a lot for your prompt response!

I really apologise for the silly mistake on dh_installdocs: it should be 
fixed now, together with the other issues you reported.


I pushed the modifications on salsa, and uploaded the package on 
mentors.debian.net



I also took the liberty of removing: ${shlibs:Depends} from the list of 
dependencies. They were empty, plus easy-rsa is just a shell script that 
relies solely on openssl, which is explicit in the package. Hope that's 
fine.


Cheers,
--
μ.

Bug#914172: [debian-mysql] Bug#914172: Bug#914172: mariadb-server-10.1: mariadb-server sec-update (10.1.37-0+deb9u1) uninstalls default-mysql-server, mysql-server, mariadb-server-10.1 & mariadb-client

2018-11-21 Thread Faustin Lammler

Jeremy Davis ,
21/11/2018 - 15:57:31 (+1100):

> I'll aim to provide as much relevant info as possible, if there is
> anything else you need please ask. Hopefully it's not too waffley and/or
> includes too much irrelevant info... (I'm often told that I need to turn
> verbosity down...)
Verbosity in bug reporting is super helpful IMO!

I have installed your appliance and the problem is the following option:
-o Dir::Etc::sourceparts=nonexistent

root@lamp ~# apt-get dist-upgrade -o APT::Get::Show-Upgraded=true \
-o Dir::Etc::sourcelist=/etc/apt/sources.list.d/security.sources.list \
-o DPkg::Options::=--force-confdef \
-o DPkg::Options::=--force-confold
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  libconfig-inifiles-perl linux-image-4.9.0-8-amd64
The following packages will be upgraded:
  adminer apache2 apache2-bin apache2-data apache2-utils base-files
  ca-certificates confconsole curl dehydrated dpkg file git git-core
  git-man gnupg gnupg-agent gpgv grub-common grub-pc grub-pc-bin
  grub2-common hdparm libapache2-mod-php7.0 libcurl3 libcurl3-gnutls
  libfuse2 libgnutls30 libldap-2.4-2 libldap-common libmagic-mgc
  libmagic1 libmariadbclient18 libpython2.7 libpython2.7-minimal
  libpython2.7-stdlib libpython3.5-minimal libpython3.5-stdlib
  libseccomp2 libsystemd0 libudev1 linux-image-amd64 mariadb-client-10.1
  mariadb-client-core-10.1 mariadb-common mariadb-server-10.1
  mariadb-server-core-10.1 openssh-client openssh-server
  openssh-sftp-server php7.0-cli php7.0-common php7.0-json php7.0-mysql
  php7.0-opcache php7.0-readline php7.0-xml python2.7 python2.7-minimal
  python3.5 python3.5-minimal ssh systemd systemd-sysv tklbam tzdata
  udev
67 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 99.9 MB of archives.
After this operation, 194 MB of additional disk space will be used.
Do you want to continue? [Y/n]

root@lamp ~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  libconfig-inifiles-perl linux-image-4.9.0-8-amd64
The following packages will be upgraded:
  adminer apache2 apache2-bin apache2-data apache2-utils base-files
  ca-certificates confconsole curl dehydrated dpkg file git git-core
  git-man gnupg gnupg-agent gpgv grub-common grub-pc grub-pc-bin
  grub2-common hdparm libapache2-mod-php7.0 libcurl3 libcurl3-gnutls
  libfuse2 libgnutls30 libldap-2.4-2 libldap-common libmagic-mgc
  libmagic1 libmariadbclient18 libpython2.7 libpython2.7-minimal
  libpython2.7-stdlib libpython3.5-minimal libpython3.5-stdlib
  libseccomp2 libsystemd0 libudev1 linux-image-amd64 mariadb-client-10.1
  mariadb-client-core-10.1 mariadb-common mariadb-server-10.1
  mariadb-server-core-10.1 openssh-client openssh-server
  openssh-sftp-server php7.0-cli php7.0-common php7.0-json php7.0-mysql
  php7.0-opcache php7.0-readline php7.0-xml python2.7 python2.7-minimal
  python3.5 python3.5-minimal ssh systemd systemd-sysv tklbam tzdata
  udev
67 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 99.9 MB of archives.
After this operation, 194 MB of additional disk space will be used.
Do you want to continue? [Y/n]

So there is no problem with this security upgrade.

May I suggest you to check why you use this option?
I can't find any relevant documentation...

If you find some useful information you want to add to this, please do
it and then please close this bug report.

Thanks again for your help!

Regards,
Faustin

Bug#914283: [libboost-context-dev] Provide ucontext_t alternative build

2018-11-21 Thread Bogdan Vatra

Package: libboost-context-dev
Version: 1.67.0.1
Severity: normal

--- Please enter the report below this line. ---
Dear Maintainer,

  By default context boost uses fcontext_t, which makes address & thread 
sanitizers unusable (strangely thread sanitizers used to work with boost 1.62, 
but with 1.67 are unusable).
  It will be great if debian provides also an ucontext_t alternative build 
(libboost-ucontext-dev ?) which replaces fcontext_t and enables the usage of 
address & thread sanitizers.

For more informations check:
https://github.com/boostorg/coroutine2/issues/12
https://github.com/boostorg/coroutine/issues/30
https://www.boost.org/doc/libs/1_67_0/libs/context/doc/html/context/cc/
implementations__fcontext_t__ucontext_t_and_winfiber.html

Thanks!

--- System information. ---
Architecture: 
Kernel:   Linux 4.18.0-2-amd64

--- Package information. ---
Depends   (Version) | Installed
===-+-===
libboost-context1.67-dev| 1.67.0-10

Bug#914172: [debian-mysql] Bug#914172: Bug#914172: mariadb-server-10.1: mariadb-server sec-update (10.1.37-0+deb9u1) uninstalls default-mysql-server, mysql-server, mariadb-server-10.1 & mariadb-client

On Wed, Nov 21, 2018 at 2:46 PM Faustin Lammler  wrote:
>
> Jeremy Davis ,
> 21/11/2018 - 15:57:31 (+1100):
> May I suggest you to check why you use this option?
> I can't find any relevant documentation...

https://manpages.debian.org/testing/apt/apt-get.8.en.html

/etc/apt/sources.list.d/
File fragments for locations to fetch packages from. Configuration
Item: Dir::Etc::SourceParts.

-- 
Olaf

Bug#913910: atop crashed with "Malloc failed for 1826553824 deviated tasks"

2018-11-21 Thread Marc Haber

severity #913910 normal
thanks

On Mon, Nov 19, 2018 at 09:58:04AM +0100, Vincent Lefevre wrote:
> Raising to grave, because as soon as the system is slightly loaded
> (e.g. executing a "configure" script), atop fails.

Sorry, disagreed, you're the only one reporting this.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#914172: [debian-mysql] Bug#914172: Bug#914172: mariadb-server-10.1: mariadb-server sec-update (10.1.37-0+deb9u1) uninstalls default-mysql-server, mysql-server, mariadb-server-10.1 & mariadb-client

2018-11-21 Thread Faustin Lammler

Thanks Olaf!

Olaf van der Spek ,
21/11/2018 - 14:52:05 (+0100):

> /etc/apt/sources.list.d/
> File fragments for locations to fetch packages from. Configuration
> Item: Dir::Etc::SourceParts.
Yes, but what does 'nonexistent'?

Bug#914132: RFS: cwm/6.3-1 -- lightweight and efficient window manager for X11

2018-11-21 Thread Dmitry Bogatov



[2018-11-19 18:44] James McDonald 
> It builds those binary packages:
> 
>   cwm -- lightweight and efficient window manager for X11
> [...]
> 
>   dget -x https://mentors.debian.net/debian/pool/main/c/cwm/cwm_6.3-1.dsc

404.

Bug#822753: /lib/init/init-d-script: exit 0 at end of script prevents all other exit codes

2018-11-21 Thread Dmitry Bogatov

[2018-11-20 10:15] Jonathan de Boyne Pollard 

>
> part   text/plain1073
> Dmitry Bogatov:
> 
> > Can you please elaborate, what exactly would break?
>
> Look at the way that the init-d-script script is used.  It isn't used as 
> the interpreter of an rc script.  (Your manual needs fixing to show the 
> correct way to invoke it, by the way.) 

I believe I already wrote in init-d-script(5) correct invocation:

#!/usr/bin/env /lib/init/init-d-script

> It is invoked as:
> > #!/bin/sh
> > if [ true != "$INIT_D_SCRIPT_SOURCED" ] ; then
> > set "$0" "$@"; INIT_D_SCRIPT_SOURCED=true . /lib/init/init-d-script
> > fi

True, many do it this way.

> init-d-script proceeds to source the script that sourced it. Consider
> what happens if its final action is not to exit $?.  The shell returns
> to the original rc script, and runs the rest of it *again*.  This
> wouldn't be a problem if rc scripts were purely pseudo-declarative, as
> it would just run some variable assignments and function definitions a
> second time.  But in reality people are writing rc scripts like these,
> cargo-cult style:

I do not object `exit $?'. But last line of `init-d-script' is `exit 0'.

But thank you for your explanation. Now I agrue to change `exit 0' to
`exit $?'.

Bug#914174: RFS: easy-rsa [ITA]

2018-11-21 Thread Dmitry Bogatov



[2018-11-20 08:45] Michele Orrù 
> 
> * Package name: easy-rsa
>   Version : 3.0.5-1
>   Upstream Author : the Open-Source OpenVPN development community
> * URL : https://github.com/OpenVPN/easy-rsa/
> * License : GPLv2
> 
> It builds those binary packages:
> 
>   easy-rsa - Simple shell based CA utility

For commit 7a17:

 * typo in `debian/control': correct is `Rules-Requires-Root'
  ^
 * FTBFS:

dh_installdocs: Cannot find (any matches for) 
"debian/README-Debian-much-features-such-wow" (tried in ., debian/tmp)

Bug#914172: [debian-mysql] Bug#914172: Bug#914172: mariadb-server-10.1: mariadb-server sec-update (10.1.37-0+deb9u1) uninstalls default-mysql-server, mysql-server, mariadb-server-10.1 & mariadb-client

On Wed, Nov 21, 2018 at 2:59 PM Faustin Lammler  wrote:
>
> Thanks Olaf!
>
> Olaf van der Spek ,
> 21/11/2018 - 14:52:05 (+0100):
>
> > /etc/apt/sources.list.d/
> > File fragments for locations to fetch packages from. Configuration
> > Item: Dir::Etc::SourceParts.
> Yes, but what does 'nonexistent'?

It's a non-existing path (hopefully), so apt won't read any files from
/etc/apt/sources.d (the default for that setting).


-- 
Olaf

Bug#914172: [debian-mysql] Bug#914172: Bug#914172: mariadb-server-10.1: mariadb-server sec-update (10.1.37-0+deb9u1) uninstalls default-mysql-server, mysql-server, mariadb-server-10.1 & mariadb-client

On Wed, Nov 21, 2018 at 3:11 PM Faustin Lammler  wrote:
>
> Olaf van der Spek ,
> 21/11/2018 - 15:03:07 (+0100):
>
> > It's a non-existing path (hopefully), so apt won't read any files from
> > /etc/apt/sources.d (the default for that setting).
> OK but I still can not understand why they do that.

It's used to exclude updates from third party repos I guess.

> And why apt then
> removes these packages:
> default-mysql-server mariadb-client-10.1 mariadb-server-10.1 mysql-server

If you're able to repro that then it shouldn't be too hard to figure out right?


-- 
Olaf

Bug#904132: ITP: browsh -- Fully interactive, realtime, and modern text-based browser

2018-11-21 Thread Paride Legovini

Just a quick follow-up. Hopefully most of the dependencies are packaged
now. There is an upstream blocker:

https://github.com/browsh-org/browsh/issues/238

It should be easy to fix with a Debian patch, but I would prefer to see
it fixed upstream. The ITP has been quiet because some dependencies had
to be packaged first.

Paride

Bug#914153: Update to version 2.3.0-3 breaks Megaglest

2018-11-21 Thread Frank Heckenbach

Hi,

> I think that we should revert this change for the time being, though,
> because if it was working in this way for about a decade and the
> programs using FTGL worked "fine" despite having some bug there,

Sorry, they did *NOT* all work fine, see my bug report. And if we
apply my patch from 742469 instead, that might break programs in
other ways (and will require yet another breaking change in the
future, when we apply sammy's patch properly).

> there's no need to change this now and break applications with only a
> few weeks to fix this in 15+ other packages before the freeze.

For me, there was very much a need to change. This was one of the
reasons I started working on ftgl at all if you remember. Without
either fix (sammy's or mine), ftgl is useless to me, so I'm not
gonna do this in my repo.

> Otherwise we have to get the fix in several of this packages, which is
> way more difficult, specially if not well maintained in Debian,
> upstream or both.

As I said, it's a messy situation. A bug that was actually fixed in
2009, not applied downstream, rediscovered by me in 2014, and
accidentally pulled downstream by syncing from the repo you pointed
me do early this year (which I had (naively?) assumed to be mostly
in sync with your version). I'm used to bugs in Debian getting
ignored for years and the wontfixed (or silenly buried), but that
mess seems to be special even in comparison.

So what can we actually do now?

- If you view it as an ABI breaking change, I can bump the version
  to 3.0.0, just let me know. (This would mean that programs using
  the library would need to be rechecked anyway, right? So if we
  document this prominently, they'll know what to look for, both in
  source code and in program behaviour.)

- If you insist on a version without either of those bugfixes, do
  this in your code, but then I'm out, sorry. For me this will mean
  at least 2 more years working with an out-of-distro version (and I
  fear it would get neglected again, so maybe more like 10 more
  years or forever), so I'd have no reason to care about the distro
  version.

- Otherwise just let the other packages find and fix the resulting
  bugs, like the saying goes "better ask for forgiveness than for
  permission".

- A slightly more complex solution would be a flag to select the
  behaviour. Of course, it would need to be a runtime flag. It may
  default to the old behaviour, but that should be deprecated (and
  print a strong depreciation message -- unfortunately that would
  have to be at runtime too AFAICS, or is there a way to warn at
  compile time when a program, say, does *not* reference a
  particular function?).

Cheers,
Frank

Bug#914174: RFS: easy-rsa [ITA]

2018-11-21 Thread Adam Borowski

On Wed, Nov 21, 2018 at 02:27:17PM +0100, Michele Orru wrote:
> On 11/21/18 6:45 AM, Adam Borowski wrote:
> > On Tue, Nov 20, 2018 at 08:45:09AM +0100, Michele Orrù wrote:
> > > * Package name: easy-rsa
> > >Version : 3.0.5-1
> > 
> > > https://salsa.debian.org/maker-guest/easy-rsa/
> 
> thanks a lot for your prompt response!
> 
> I really apologise for the silly mistake on dh_installdocs: it should be
> fixed now, together with the other issues you reported.
> 
> I pushed the modifications on salsa, and uploaded the package on
> mentors.debian.net

Awesome.

There's one more issue that's better to fix before uploading:
 Maintainer: Debian QA Group 
-- you'd want to update this.

> I also took the liberty of removing: ${shlibs:Depends} from the list of
> dependencies. They were empty, plus easy-rsa is just a shell script that
> relies solely on openssl, which is explicit in the package. Hope that's
> fine.

It's generally better to keep this even if unused as an empty var that's
referenced is ok but a non-empty var that's missing would cause problems.
This might happen if you one day need to include a bit of compiled code
in the package.  But then, for now there's no difference either way.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ We domesticated dogs 36000 years ago; together we chased
⣾⠁⢰⠒⠀⣿⡁ animals, hung out and licked or scratched our private parts.
⢿⡄⠘⠷⠚⠋⠀ Cats domesticated us 9500 years ago, and immediately we got
⠈⠳⣄ agriculture, towns then cities. -- whitroth on /.

Bug#910917: RFA: apache2 -- Apache HTTP Server

2018-11-21 Thread Stefan Fritsch

Hi,

Xavier, yes, please do a join request. If you are looking for work, one thing 
that should be done before buster is enabling http/2 by default (#880993).

Mosab and Jason, are you still interested?

Cheers,
Stefan

On Tuesday, 20 November 2018 10:41:55 CET Xavier wrote:
> Hi all,
> 
> I'm DD, Apache user and maintainer of libapache2-mod-fcgid. I can't
> maintain this package alone since I'm not enough experimented in C but I
> can help (review, tests and upload if needed). So what is the best,
> join-request to apache-team on salsa for Jason, Mosab and me?
> 
> Cheers,
> Xavier

Bug#914284: yaml-cpp update to 0.6.2?

Package: src:yaml-cpp
Version: 0.5.3-0.1
X-Debbugs-CC: Boyuan Yang 

yaml-cpp was just updated to 0.5.3, a version released in 2016. Is this
appropriate, when there is are newer releases available?  Are there any concerns
with the 0.6.x releases?

Bug#914188: [debian-mysql] Bug#914188: mariadb-server: Upgrade faild due to 'unknown variable': 'server_audit_file_path=/path/to/audit.log'

2018-11-21 Thread Marc Lagies


Hello Faustin

On 20.11.18 19:35, Faustin Lammler wrote:

May I ask you which version of mariadb you where upgrading from?


10.1.26-0+deb9u1 (2018-07-31)

I enabled the plugin about three weeks ago.




And also please respond to the following:

I commented out the audit plugin relateted lines in the mariadb config
file.

Can you give me the path of this config file?


/etc/mysql/my.cnf




Did you uncommented the precedent line after upgrade?


Yes.



Please provide output of following SQL command:
SHOW GLOBAL VARIABLES LIKE '%server_audit%';



+---+-+
| Variable_name | Value   |
+---+-+
| server_audit_events   | CONNECT |
| server_audit_excl_users   | |
| server_audit_file_path| /var/log/mysql/mariadb_server_audit.log |
| server_audit_file_rotate_now  | OFF |
| server_audit_file_rotate_size | 1073741824  |
| server_audit_file_rotations   | 9   |
| server_audit_incl_users   | |
| server_audit_logging  | ON  |
| server_audit_mode | 0   |
| server_audit_output_type  | file|
| server_audit_query_log_limit  | 1024|
| server_audit_syslog_facility  | LOG_USER|
| server_audit_syslog_ident | mysql-server_auditing   |
| server_audit_syslog_info  | |
| server_audit_syslog_priority  | LOG_INFO|
+---+-+


Kind regards
Marc

Bug#910917: RFA: apache2 -- Apache HTTP Server

2018-11-21 Thread Mosab Ibrahim

Hello Stefan,

Yes, I am still interested. Will go through the code base, and the
packaging process for debian this weekend, unless you have other
suggestions.

On Wed, Nov 21, 2018 at 3:21 PM Stefan Fritsch  wrote:

> Hi,
>
> Xavier, yes, please do a join request. If you are looking for work, one
> thing
> that should be done before buster is enabling http/2 by default (#880993).
>
> Mosab and Jason, are you still interested?
>
> Cheers,
> Stefan
>
> On Tuesday, 20 November 2018 10:41:55 CET Xavier wrote:
> > Hi all,
> >
> > I'm DD, Apache user and maintainer of libapache2-mod-fcgid. I can't
> > maintain this package alone since I'm not enough experimented in C but I
> > can help (review, tests and upload if needed). So what is the best,
> > join-request to apache-team on salsa for Jason, Mosab and me?
> >
> > Cheers,
> > Xavier
>
>
>
>
> --
*Mosab Ibrahim*
*Software Engineer*
*https://www.mos3abof.com *

Bug#914172: [debian-mysql] Bug#914172: Bug#914172: mariadb-server-10.1: mariadb-server sec-update (10.1.37-0+deb9u1) uninstalls default-mysql-server, mysql-server, mariadb-server-10.1 & mariadb-client

2018-11-21 Thread Faustin Lammler

Olaf van der Spek ,
21/11/2018 - 15:03:07 (+0100):

> It's a non-existing path (hopefully), so apt won't read any files from
> /etc/apt/sources.d (the default for that setting).
OK but I still can not understand why they do that. And why apt then
removes these packages:
default-mysql-server mariadb-client-10.1 mariadb-server-10.1 mysql-server

Faustin

Bug#913740: fetch-url does not use --no-check-certificate on HTTP to HTTPS redirects

2018-11-21 Thread Mauricio Oliveira

Hi Philipp,

On Thu, Nov 15, 2018 at 7:21 AM Philipp Kern  wrote:
[...]
> Why do we need to build out this insecure option more rather than the
> target having supported SSL certificates (now that Let's Encrypt and
> friends exist)? [...]

Point taken, however this seems orthogonal to the current problem,
which is the 'allow_unauthenticated_ssl=true' option it not used even
if the user requests it, in the particular case of HTTP-HTTPS redirect.

That is a problem.  Of course, not using of valid/supported SSL certificates
_may_ be _another_ problem, i.e., a security concern, but it's arguably not so
in some scenarios, e.g., restricted-access and test/debug environments.
In this case, the latter problem may be _acceptable), but the former problem
prevents it from even being _usable_ regardless of the user's choice/decision.

So, I can certainly appreciate the point you brought up about it,
but I believe this is more of fixing a corner/particular case bug
that is not yet covered for a functionality that is already in place.

> [...] I will note that it's also possible to copy additional
> root certificates into the initrd pre-install. (At least it used to work
> before HTTPS was generally available.)

It looks like this requires rebuilding the initrd, which is some extra work
(and unfortunately it does not allow using the already
distributed/official files out there),
and someone can also decide to do that for the case without
HTTP->HTTPS redirect,
so not really particular to this problem/bug report itself, if I
understand it correctly.

Hope this helps!

Best regards,

-- 
Mauricio Faria de Oliveira

Bug#914174: RFS: easy-rsa [ITA]

2018-11-21 Thread Michele Orru




On 11/21/18 3:14 PM, Adam Borowski wrote:
> On Wed, Nov 21, 2018 at 02:27:17PM +0100, Michele Orru wrote:
>> On 11/21/18 6:45 AM, Adam Borowski wrote:
>>> On Tue, Nov 20, 2018 at 08:45:09AM +0100, Michele Orrù wrote:
 * Package name: easy-rsa
 Version : 3.0.5-1
>>>
  https://salsa.debian.org/maker-guest/easy-rsa/
>>
>> thanks a lot for your prompt response!
>>
>> I really apologise for the silly mistake on dh_installdocs: it should be
>> fixed now, together with the other issues you reported.
>>
>> I pushed the modifications on salsa, and uploaded the package on
>> mentors.debian.net
>
> Awesome.
>
> There's one more issue that's better to fix before uploading:
>   Maintainer: Debian QA Group 
> -- you'd want to update this.
>

… right, thanks again. It should be fixed now (both on mentors and on 
salsa).


>> I also took the liberty of removing: ${shlibs:Depends} from the list of
>> dependencies. They were empty, plus easy-rsa is just a shell script that
>> relies solely on openssl, which is explicit in the package. Hope that's
>> fine.
>
> It's generally better to keep this even if unused as an empty var that's
> referenced is ok but a non-empty var that's missing would cause problems.
> This might happen if you one day need to include a bit of compiled code
> in the package.  But then, for now there's no difference either way.

I see your point, I'll keep that in mind. However, unless you really 
think it would be best to keep it, I'd leave as it is to get rid of that 
lintian warning.


I also went through:
https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt
to update the Standards version, which apparently required no additional 
changes to the package, or the metadata. Hope that's fine.


--
μ.

Bug#914271: lintian: Rationale behind hyphen-in-upstream-part-of-debian-changelog-version

2018-11-21 Thread Felix Lechner

Well, I also agree with Josch's well-articulated argument. A merge
request to remove the tag is pending (!72). Thank you for bringing
this to our attention!

Bug#914274: Please take over the package

2018-11-21 Thread Thomas Goirand

Hi,

We don't use it within the OpenStack team anymore. Please take over the
package and add Python 3 support as you need.

Cheers,

Thomas Goirand (zigo)

Bug#914276: monkeysign tries to access an external key server during the tests

2018-11-21 Thread Antoine Beaupré

Control: tags -1 +moreinfo

On 2018-11-21 12:56:40, Matthias Klose wrote:
> Package: src:monkeysign
> Version: 2.2.4
> Severity: important
> Tags: sid buster
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: breaks needs-update
>
> monkeysign tries to access an external key server during the tests, and then 
> in
> a restricted test environment, it fails tests.  Please either use a proxy or
> disable the tests with network access.

The network tests are disabled in the debian package build.

They are not, in the normal test suite however.

Do you mean to say that network access occurs in the package build? If
so, please provide a detailed build log.

Thanks!

-- 
Choose a job you love and you will never have to work a day in your
life.
 - Confucius

Bug#914269: google-i18n-address FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 11

2018-11-21 Thread Daniel Kahn Gillmor

Control: tags 914269 + confirmed help

I see this error in my cowbuilder instance as well, but i don't see the
error when i build by hand on a buster/sid system.

more confusingly, this error crops up in python3.6, but not when
using python3.7 -- so i don't understand what the issue is, or how to
debug it further.

I welcome any pointers.

  --dkg


signature.asc
Description: PGP signature

Bug#914266: [Qa-jenkins-dev] Bug#914266: reproducible: vary running debian/rules binary target under fakeroot/etc

2018-11-21 Thread Holger Levsen

control: tags -1 + moreinfo

Hi Paul,

I'm afraid I don't see much point in this. Maybe you can elaborate some
more?

On Wed, Nov 21, 2018 at 05:59:40PM +0800, Paul Wise wrote:
> For reproducible builds I would like to perform build2 using fakeroot
> even if Rules-Requires-Root is set to no.
> 
> This will find packages that really should not have the debian/control
> Rules-Requires-Root field set to no.

while I can see how this is interesting, I don't see how this is
relevant for reproducible builds or benefical for Debian in general.

ok, it finds some minor bugs, with AFAIK have no real relevance today.

> This will find packages that will build differently with older dpkg
> versions that do not support Rules-Requires-Root and always use
> fakeroot/etc.

for reproducible builds we require/strongly suggest to use the same
version of packages, incl dpkg, as was used in the original build, so
i'm not sure why one want to build with an older dpkg.

also, when was Rules-Requires-Root introduced? (with what dpkg version?)
I remember it was roughly around the same time as dpkg with features needed
for reproducible builds arrived in sid, which was December 2016. So building
with an earlier dpkg is useless (from our POV) anyway.

-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

signature.asc
Description: PGP signature

Bug#914284: yaml-cpp update to 0.6.2?

On 21.11.18 16:02, Boyuan Yang wrote:
> X-Debbugs-CC: tsimo...@ubuntu.com d...@debian.org
> 
> 在 2018-11-21三的 15:23 +0100，Matthias Klose写道：
>> Package: src:yaml-cpp
>> Version: 0.5.3-0.1
>> X-Debbugs-CC: Boyuan Yang 
>>
>> yaml-cpp was just updated to 0.5.3, a version released in 2016. Is this
>> appropriate, when there is are newer releases available?  Are there any
>> concerns
>> with the 0.6.x releases?
> 
> The 0.5.3 version was an old release with many bugfixes. Yaml-cpp 0.6.x (seems
> to) have ABI break that needs transition. I'm not sure if we could finished it
> before Buster freeze.
> 
> I'm aware of the 2 CVEs; however it seems that upstream hasn't reach a final
> conclusion yet.
> 
> Besides, Andreas Tille wishes no longer be the uploader of the package and the
> other 2 maintainers are not responding to the email. However Simon Quigley
> expressed interest in the package recently and I believe he should join the
> discussion.
> 
> I'm not into maintaining yaml-cpp on a long-term basis (I jumped in simply
> because of boost1.67 transition and that this package is a dependency of
> librime and a series of packages in the Input Method Team). Please consider
> making tests and properly uploading new versions as you want (of course, try
> not to break downstream software).

ok, thanks for the notification.

However, please note the 0.5.3 already seems to introduce an ABI break, as
discussed today on #debian-release.

Bug#914271: lintian: Rationale behind hyphen-in-upstream-part-of-debian-changelog-version

tags 914271 + pending
thanks

Applied in Git, pending upload. Thanks, Felix.

  
https://salsa.debian.org/lintian/lintian/commit/09d86b2fd208f95a816430e8ce5595b08fe0f3b3

  checks/source-changelog.desc | 8 
  checks/source-changelog.pm   | 3 ---
  debian/changelog | 4 
  t/tests/changelog-version-special-chars/tags | 1 -
  4 files changed, 4 insertions(+), 12 deletions(-)


Regards,

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

Bug#913124: Resolving deltas takes a long time when cloning Debian's security tracker

2018-11-21 Thread Antoine Beaupré

> Any ideas how to tackle this? Do you maybe remember an upstream
> discussion about  similar issue?

The latest git-rev news has some blurb about git-commit-graph:

https://git.github.io/rev_news/2018/11/21/edition-45/

It says it improves push times, but i wonder if it could also resolve
other issues we're having. At least it would improve push time, which
does take a few seconds here already.

A.

-- 
You can't conquer a free man; the most you can do is kill him.
   -  Robert A. Heinlein

Bug#783938: openjdk-11: Reproducible timestamp in javadoc files

2018-11-21 Thread Emmanuel Bourg

Control: tags -1 + patch

Here is a patch adding SOURCE_DATE_EPOCH support to the javadoc tool.
Description: Makes the timestamp in the javadoc files reproducible when 
SOURCE_DATE_EPOCH is specified
Author: Emmanuel Bourg 
Forwarded: no
--- 
a/src/jdk.javadoc/share/classes/jdk/javadoc/internal/doclets/formats/html/markup/Head.java
+++ 
b/src/jdk.javadoc/share/classes/jdk/javadoc/internal/doclets/formats/html/markup/Head.java
@@ -256,6 +256,9 @@
  */
 public Content toContent() {
 Date now = showTimestamp ? calendar.getTime() : null;
+if (now != null && System.getenv("SOURCE_DATE_EPOCH") != null) {
+now = new Date(1000 * 
Long.parseLong(System.getenv("SOURCE_DATE_EPOCH")));
+}
 
 HtmlTree tree = new HtmlTree(HtmlTag.HEAD);
 if (showGeneratedBy) {
@@ -269,6 +272,9 @@
 
 if (showMetaCreated) {
 SimpleDateFormat dateFormat = new SimpleDateFormat("-MM-dd");
+if (System.getenv("SOURCE_DATE_EPOCH") != null) {
+dateFormat.setTimeZone(TimeZone.getTimeZone("UTC"));
+}
 tree.addContent(HtmlTree.META(
 (htmlVersion == HtmlVersion.HTML5) ? "dc.created" : "date",
 dateFormat.format(now)));
@@ -298,7 +304,14 @@
 private Comment getGeneratedBy(boolean timestamp, Date now) {
 String text = "Generated by javadoc"; // marker string, deliberately 
not localized
 if (timestamp) {
-text += " ("+ docletVersion + ") on " + now;
+text += " ("+ docletVersion + ") on ";
+if (System.getenv("SOURCE_DATE_EPOCH") == null) {
+text += now;
+} else {
+SimpleDateFormat fmt = new SimpleDateFormat("-MM-dd 
HH:mm:ss z");
+fmt.setTimeZone(TimeZone.getTimeZone("UTC"));
+text += fmt.format(now);
+}
 }
 return new Comment(text);
 }

Bug#914269: google-i18n-address FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 11

Control: tags -1 - help

On Wed, Nov 21, 2018 at 10:01:41AM -0500, Daniel Kahn Gillmor wrote:
> Control: tags 914269 + confirmed help
> 
> I see this error in my cowbuilder instance as well, but i don't see the
> error when i build by hand on a buster/sid system.
> 
> more confusingly, this error crops up in python3.6, but not when
> using python3.7 -- so i don't understand what the issue is, or how to
> debug it further.
> 
> I welcome any pointers.

Fails:
LC_ALL=C dpkg-buildpackage

Builds:
LC_ALL=C.UTF-8 dpkg-buildpackage

Python 3.7 has a workaround for C locale.

In debian/rules add:
export LC_ALL=C.UTF-8

>   --dkg

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#914285: dbus: system bus logs repeated denials for session buses calling GetDynamicUsers() on systemd Manager lines

2018-11-21 Thread Simon McVittie

Control: retitle -1 dbus: system bus logs repeated denials for session buses 
calling GetDynamicUsers() on systemd Manager

On Wed, 21 Nov 2018 at 15:29:37 +0100, Francesco Potortì wrote:
> dbus generates over 100 lines a day like this in auth.log:
> 
> Nov 21 13:20:39 tucano dbus-daemon[3507]: [system] Rejected send message, 4 
> matched rules; type="method_call", sender=":1.383314" (uid=1000 pid=2330 
> comm="/usr/bin/dbus-daemon --syslog --fork --print-pid 5") 
> interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" error 
> name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" 
> (uid=0 pid=1 comm="/lib/systemd/systemd --system --deserialize 538 ")
> 
> This happens while I work at the console, but not when I work remotely.
> 
> Using the atop logs, I can tell that process 2330 was a dbus-daemon starting 
> and ending at 13:20:39.

Code in the session dbus-daemon doesn't explicitly connect to the system
dbus-daemon and comunicate with pid 1, so I think this must be something
in a shared library that it uses, most likely libsystemd or a PAM module?

systemd installs a policy with

so this is meant to be allowed.

"4 matched rules" is consistent with the matched rules being:

*  in /usr/share/dbus-1/system.conf
* 
  in /usr/share/dbus-1/system.d/org.freedesktop.systemd1.conf
* the rule above in /usr/share/dbus-1/system.d/org.freedesktop.systemd1.conf
* some other rule

... so perhaps you have a  rule in /usr/share/dbus-1/system.d/*.conf
or in /etc/dbus-1/system.d/*.conf, with higher precedence,
that is interfering with those messages? If you search for
org.freedesktop.systemd1 or GetDynamicUsers in those files, what do
you get?

smcv

Bug#913910: atop crashed with "Malloc failed for 1826553824 deviated tasks"

2018-11-21 Thread Vincent Lefevre

Control: severity -1 important
Control: found -1 2.2.6-4

That's at least important, because of possible DoS: if the value
is big and the malloc succeeds, it can take the whole memory (and
this may be very bad on machines with a lot of swap).

atop from stable is affected (but on a Debian/unstable machine,
as I couldn't reproduce the problem on a Debian/stable machine).

On 2018-11-21 14:55:28 +0100, Marc Haber wrote:
> Sorry, disagreed, you're the only one reporting this.

Perhaps because users don't run atop very often (and note that not
all machines are affected).

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

Bug#913261: RFS: chkboot/1.2-1 [ITP]

2018-11-21 Thread Baptiste BEAUPLAT

Hello Herbert,

I hope you are well.

I was wondering if you had time to take a second look at this package?

Best regards,

On 11/10/18 2:14 PM, Baptiste BEAUPLAT wrote:
>> The package does not build twice in a row:
> This is fixed now.

-- 
Baptiste BEAUPLAT - lyknode

signature.asc
Description: OpenPGP digital signature

Bug#913910: atop crashed with "Malloc failed for 1826553824 deviated tasks"

2018-11-21 Thread Marc Haber

On Wed, Nov 21, 2018 at 04:26:11PM +0100, Vincent Lefevre wrote:
> Control: severity -1 important

Not in a mood to play games or to escalate. So be it. I still disagree.


-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#913364: real bug, too low severity

2018-11-21 Thread Marc Haber

On Sun, Nov 18, 2018 at 01:27:53AM +0100, Adam Borowski wrote:
> > Not a bug in Debian. Kindly fix Devuan bugs in Devuan.
> 
> Except that it _is_ a bug in Debian.  The Devuan package the submitter has
> is unmodified (just like almost anything not related to systemd), and I just
> reproduced the bug on pure Debian unstable (I don't use Devuan save for a
> couple of containers that are hardly ever up).

I still don't understand what the bug _IS_. Make it easy to reproduce
and I'll try. Give me riddles and I'll do things that are more fun than
debugging sysv stuff.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#914286: new stable upstream version 1.3 available

2018-11-21 Thread Sebastien Bacher


Package: opus
Version: 1.3~beta+20180518-1

Hey there,

There is a new upstream version available

http://opus-codec.org/release/stable/2018/10/18/libopus-1_3.html

It would be nice to update the Debian beta snapshot to the stable releease

Bug#914271: lintian: Rationale behind hyphen-in-upstream-part-of-debian-changelog-version

2018-11-21 Thread Johannes Schauer

Hi Felix,

Quoting Felix Lechner (2018-11-21 15:52:02)
> Well, I also agree with Josch's well-articulated argument. A merge
> request to remove the tag is pending (!72). Thank you for bringing
> this to our attention!

in your original commit you were talking about "some tools".

This suggests that you know tools that behave wrongly.

If you share the tools you know of, then we could file bugs.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#903163: Adding OpenPGP smartcard support to LUKS

Hi Peter et al.,

Guilhem Moulin wrote:

> > GnuPG upstream was asked about a documented API to retrieve the stubs
> > but hasn't answered yet AFAIK.

Did they get back to you yet out of interest, Guilhem?

> > I'm not sure if the implementation currently found in our branch would
> > choke if the wrong smartcard is inserted: I wasn't able to test this
> > as I have only one token :-)

Can I fix that for you? (Serious offer; I can get this shipped to
you ASAP...)

> I have an idea on how to do this all more elegantly, but I haven't found
> the time to work it out yet. Please don't block on this when the current
> solution works for single reader, single smartcard cases.

Indeed, it would be great to see this land in the main Debian
packages; what are the remaining blockers to this? :)

Best wishes,

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

Bug#914287: lsb-release: please parse /usr/lib/os-release and deprecate /etc/lsb-release

2018-11-21 Thread Simon McVittie

Package: lsb-release
Version: 9.20170808
Severity: wishlist

Debian's Python implementation of the LSB-standardized lsb_release
command parses various sources of data, including the non-standardized
configuration file /etc/lsb-release. That file doesn't exist in Debian,
but is typically shipped in base-files by derivatives. It is not "API"
itself, although packages designed for Ubuntu sometimes treat it as
though it was.

systemd defines a new "API", which has been adopted in Debian even
for non-systemd systems: the /usr/lib/os-release file (formerly
/etc/os-release, which is now a symlink). This "API" is defined in terms
of parsing a text file, not running a Python program, so it's much faster
to use.

If lsb_release looked at /usr/lib/os-release, then derivatives could edit
that file and /etc/dpkg/origins/default (which they need to do anyway)
and wouldn't usually need to add /etc/lsb-release. /usr/lib/os-release
uses the same subset of shell syntax as /etc/lsb-release.

The fields are:

lsb_release -r, --release: e.g. "9.6"
/etc/lsb-release DISTRIB_RELEASE

This appears to be os-release's optional VERSION_ID (not VERSION,
for which the example given in the man page includes a Fedora release
codename as well as the bare version number), except that stretch's
os-release just says "9", not "9.6". For the sorts of uses people
make of lsb_release (for example gating features that should only be
enabled in newer Debian), I think it would probably make most sense
for this to be 10 for the whole lifetime of buster, ignoring point
releases?  Or it could preferentially come from /etc/debian_version,
which would retain the minor version.

lsb_release -c, --codename: e.g. "stretch"
/etc/lsb-release DISTRIB_CODENAME

This is exactly os-release's optional VERSION_CODENAME.

lsb_release -i, --id: e.g. "Debian" or "Ubuntu"
/etc/lsb-release DISTRIB_ID
/etc/dpkg/origins/default Vendor

There is no direct equivalent in os-release (ID is "debian", NAME is
"Debian GNU/Linux", neither of which matches) but /etc/dpkg/origins
should be sufficient to not need /etc/lsb-release; using os-release
ID, possibly transformed to title-case, might be a good fallback.

lsb_release -d, --description: e.g. "Debian GNU/Linux 9.6 (stretch)"
/etc/lsb-release DISTRIB_DESCRIPTION
Fallback is "${ID} ${OS} ${RELEASE} (${CODENAME})"

os-release PRETTY_NAME looks suitable for this. It can include the
OS vendor, version number and/or codename. One difference is that
stretch has PRETTY_NAME="Debian GNU/Linux 9 (stretch)", without the
9.6; but I don't think that's a very important distinction, so it
might make most sense for $(lsb_release -ds) in the buster release
to be "Debian GNU/Linux 10 (buster)" across all point releases.

Regards,
smcv

Bug#887056: gdebi: Invalid 'gnome-mime-application-x-deb' icon in AppStream metadata

Chris Lamb wrote:

> According to:
> 
>   https://appstream.debian.org/sid/main/issues/gdebi.html
> 
> ... the gdebi .desktop file specifies an invalid icon value of:
> 
>   gnome-mime-application-x-deb

Gentle ping on this?


Best wishes,

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

Bug#914288: libpgplot-perl: FTBFS and autopkgtest fail with new giza-dev: test waits for input

2018-11-21 Thread gregor herrmann

Source: libpgplot-perl
Version: 1:2.21-7
Severity: serious
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first noted on ci.d.n: With

- -libcpgplot0 1.0.0-2
+libcpgplot0 1.1.0-1
- -libgiza0 1.0.0-2
+libgiza0 1.1.0-1
- -libpgplot0 1.0.0-2
+libpgplot0 1.1.0-1

libpgplot-perl's hangs, waiting for some input:


   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/libpgplot-perl-2.21'
PGPLOT_DEV="/XSERVE" xvfb-run -a dh_auto_test
make V=1 -j1 test TEST_VERBOSE=1
make[2]: Entering directory '/build/libpgplot-perl-2.21'
"/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- PGPLOT.bs 
blib/arch/auto/PGPLOT/PGPLOT.bs 644
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-Iblib/lib" "-Iblib/arch" test.pl
== Running test1.p ==

Testing simple point plot...

PGPLOT module version 2.21

PGPLOT giza-1.1.0 library

%giza - ERROR - giza_newpage_prompt: Failed to read character from stdin
== Running test2.p ==


Testing advanced point and line plot routines...

PGPLOT module version 2.21

PGPLOT giza-1.1.0 library

Entering interactive cursor test...
Enter some points with the cursor


Cheers
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlv1hbNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZIHQ/9E1M0r8pG4oeu8x7wdXIUgCh+YijlQsuBS8C00N3n8f8wx4klBiw68GWk
wU905ZwkuibwZCyV/SRNgDiy2xMRr8yJ6Phtj/sWobx6rGT/HgqiLKRuW54i9Ef6
OSGEzsxUuALLpEn+oD/1kK3MnRCPnKtu3uc+jc3a7WMlsthkz/kp3tPTORN/jQfr
H8ooFCGsvoKxei0bSTRqs6TrZPoZH70I4QeeVxXnSMqIWuzISImEBHFQrMI+cydI
ipaf1Qj69LBqZlRPOwaJeMOZFCo26533VO8nwJVOTjJ+kExEW1GFeiQyKsZxbUU6
pK8y2l51sxwc6/IDr2Rm8e8pfNuMm5AoJdflQiAVwmEeEeJSzXdGAIm5yXwo7/WV
ifiGIjVOGJO0fq+WNVI0UHJtL4x/KcJu9o2ZL5J9BTa7ZWoV/PmmbwlYvBOwbuMb
IqRHBdV/046Z9AMLH0GFxgWfpRbJB1Sfz/g6q5b5mBoDSc0YxNQZJk4Qx7Q2UtLT
1W9CAaJbj3CJ1NVB1EmXLnIzCVDbLO/usPC4sH9tDVepwfE0RtYWI4Ex0OwnrIbW
FVETK4pSO2rpX9s1q1j07hz4qQwbdgu0jX/z0LoADtM1DkVQ7/ndreK6jjUd3d5D
CC3VNCQSU0i09TBJuXe4IbY6sHq10vj0z07xbsy0p9r18iv5HPg=
=1fYN
-END PGP SIGNATURE-

Bug#906609: fixed in gnucash 1:3.3-1

[resending due to archived bug]

Hi Dmitry et al.,

> It was entirely my fault to miss that but I'm not uploading the fix yet due 
> to unrelated FTBFS on i386 that I hope to address when upstream fixes it:
> 
>   https://bugs.gnucash.org/show_bug.cgi?id=796878

This has been merged upstream; can we make a new upload to Debian?
gnucash has been out of testing for a while, alas. :(

(Not tagging /this/ bug as "fixed-upstream" as it's a separate issue AIUI...)


Best wishes,

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

Bug#914285: dbus: system bus logs repeated denials for session buses calling GetDynamicUsers() on systemd Manager lines

2018-11-21 Thread Francesco Potortì

>... so perhaps you have a  rule in /usr/share/dbus-1/system.d/*.conf
>or in /etc/dbus-1/system.d/*.conf, with higher precedence,
>that is interfering with those messages? If you search for
>org.freedesktop.systemd1 or GetDynamicUsers in those files, what do
>you get?

fgrep -i -l org.freedesktop.systemd1 /etc/dbus-1/system.d/*.conf  
/usr/share/dbus-1/system.d/*.conf  /usr/share/dbus-1/system.conf
/etc/dbus-1/system.d/org.freedesktop.systemd-shim.conf
/usr/share/dbus-1/system.d/org.freedesktop.systemd1.conf
/usr/share/dbus-1/system.conf

~$ fgrep -i -l GetDynamicUsers /etc/dbus-1/system.d/*.conf  
/usr/share/dbus-1/system.d/*.conf  /usr/share/dbus-1/system.conf
/usr/share/dbus-1/system.d/org.freedesktop.systemd1.conf

So, there are 3 concerned files, which I am appending below.  Thanks for
following up.  As far as I can tell, I have not modified any of them.


===File /etc/dbus-1/system.d/org.freedesktop.systemd-shim.conf===
 
http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";>























































===File /usr/share/dbus-1/system.d/org.freedesktop.systemd1.conf===
 
http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";>





























































































































































































































===File /usr/share/dbus-1/system.conf===




http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";>


  
  system

  
  messagebus

  
  

  
  

  
  /usr/lib/dbus-1.0/dbus-daemon-launch-helper

  
  /run/dbus/pid

  
  

  
  EXTERNAL

  
  unix:path=/var/run/dbus/system_bus_socket

  


























  

  
  

  

  
  

  

  
  

  

  
  /etc/dbus-1/system.conf.dpkg-bak

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

  
  system.d

  /etc/dbus-1/system.d

  
  /etc/dbus-1/system-local.conf

  contexts/dbus_contexts

Bug#914190: yaml-cpp: diff for NMU version 0.5.3-0.2

Control: reassign -1 src:yaml-cpp
Control: tags 914190 + patch
Control: tags 914190 + pending

Dear maintainer,

I've prepared an NMU for yaml-cpp (versioned as 0.5.3-0.2) and
uploaded it to DELAYED/1. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
diff -Nru yaml-cpp-0.5.3/debian/changelog yaml-cpp-0.5.3/debian/changelog
--- yaml-cpp-0.5.3/debian/changelog	2018-11-19 16:29:13.0 +0100
+++ yaml-cpp-0.5.3/debian/changelog	2018-11-21 16:57:39.0 +0100
@@ -1,3 +1,10 @@
+yaml-cpp (0.5.3-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload 
+  * Bump soname to libyaml-cpp0.5d1 to account for ABI break (Closes: #914190)
+
+ -- Julian Andres Klode   Wed, 21 Nov 2018 16:57:39 +0100
+
 yaml-cpp (0.5.3-0.1) unstable; urgency=medium
 
   * Non-maintainer upload with acknowledgement from Andreas Tille.
diff -Nru yaml-cpp-0.5.3/debian/control yaml-cpp-0.5.3/debian/control
--- yaml-cpp-0.5.3/debian/control	2018-11-19 16:29:11.0 +0100
+++ yaml-cpp-0.5.3/debian/control	2018-11-21 16:57:39.0 +0100
@@ -12,15 +12,13 @@
 Vcs-Browser: https://salsa.debian.org/debian/yaml-cpp
 Homepage: https://github.com/jbeder/yaml-cpp
 
-Package: libyaml-cpp0.5v5
+Package: libyaml-cpp0.5d1
 Architecture: any
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends},
  ${misc:Depends}
 Pre-Depends: ${misc:Pre-Depends}
-Conflicts: libyaml-cpp0.5
-Replaces: libyaml-cpp0.5
 Description: YAML parser and emitter for C++
  yaml-cpp is a C++ library for parsing and emitting data in YAML 1.2, a
  human-readable data serialization format.
@@ -31,7 +29,7 @@
 Architecture: any
 Multi-Arch: same
 Section: libdevel
-Depends: libyaml-cpp0.5v5 (= ${binary:Version}),
+Depends: libyaml-cpp0.5d1 (= ${binary:Version}),
  libboost-dev,
  ${misc:Depends}
 Description: YAML parser and emitter for C++ - development files
diff -Nru yaml-cpp-0.5.3/debian/libyaml-cpp0.5d1.install yaml-cpp-0.5.3/debian/libyaml-cpp0.5d1.install
--- yaml-cpp-0.5.3/debian/libyaml-cpp0.5d1.install	1970-01-01 01:00:00.0 +0100
+++ yaml-cpp-0.5.3/debian/libyaml-cpp0.5d1.install	2018-11-19 15:49:19.0 +0100
@@ -0,0 +1 @@
+usr/lib/*/libyaml-cpp.so.*
diff -Nru yaml-cpp-0.5.3/debian/libyaml-cpp0.5v5.install yaml-cpp-0.5.3/debian/libyaml-cpp0.5v5.install
--- yaml-cpp-0.5.3/debian/libyaml-cpp0.5v5.install	2018-11-19 15:49:19.0 +0100
+++ yaml-cpp-0.5.3/debian/libyaml-cpp0.5v5.install	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-usr/lib/*/libyaml-cpp.so.*
diff -Nru yaml-cpp-0.5.3/debian/patches/bump-soname-for-abi-break.patch yaml-cpp-0.5.3/debian/patches/bump-soname-for-abi-break.patch
--- yaml-cpp-0.5.3/debian/patches/bump-soname-for-abi-break.patch	1970-01-01 01:00:00.0 +0100
+++ yaml-cpp-0.5.3/debian/patches/bump-soname-for-abi-break.patch	2018-11-21 16:57:39.0 +0100
@@ -0,0 +1,17 @@
+Description:  Bump soname to libyaml-cpp0.5d1 to account for ABI break 
+ A new field has been added to a class, breaking ABI
+Author: Julian Andres Klode 
+Bug-Debian: https://bugs.debian.org/914190
+Last-Update: 2018-11-21
+
+--- yaml-cpp-0.5.3.orig/CMakeLists.txt
 yaml-cpp-0.5.3/CMakeLists.txt
+@@ -280,7 +280,7 @@ set_target_properties(yaml-cpp PROPERTIE
+ 
+ set_target_properties(yaml-cpp PROPERTIES
+ 	VERSION "${YAML_CPP_VERSION}"
+-	SOVERSION "${YAML_CPP_VERSION_MAJOR}.${YAML_CPP_VERSION_MINOR}"
++	SOVERSION "${YAML_CPP_VERSION_MAJOR}.${YAML_CPP_VERSION_MINOR}d1"
+ 	PROJECT_LABEL "yaml-cpp ${LABEL_SUFFIX}"
+ )
+ 
diff -Nru yaml-cpp-0.5.3/debian/patches/series yaml-cpp-0.5.3/debian/patches/series
--- yaml-cpp-0.5.3/debian/patches/series	2018-11-19 16:10:30.0 +0100
+++ yaml-cpp-0.5.3/debian/patches/series	2018-11-21 16:57:39.0 +0100
@@ -3,3 +3,4 @@
 reproducible-build.patch
 0003-Workaround-bug-in-googletest-fixing-bug-812284.patch
 0006-Fix-usage-of-boost-next-and-boost-prior.patch
+bump-soname-for-abi-break.patch

Bug#914271: lintian: Rationale behind hyphen-in-upstream-part-of-debian-changelog-version

2018-11-21 Thread Felix Lechner

> This suggests that you know tools that behave wrongly.

Unfortunately, I cannot help. I remember having issues when
experimenting with less common version numbers, but that may not have
been with dashes. My hope was to build a fence around policy to save a
maintainer from potential headaches (which I saw as a precaution more
than a cure). Since then, many packages have been so tagged, and none
of you have any problems. Turns out no fence was needed. Thank you for
following up!

Bug#914278: openjdk-11: Reproducible properties file header when SOURCE_DATE_EPOCH is specified

2018-11-21 Thread Holger Levsen

clone 914278 -1 
reassign -1 strip-nondeterminism
block -1 by 914278
retitle -1 strip-nondeterminism: disable javadoc handler
# thanks Emmanuel


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#914190: yaml-cpp: diff for NMU version 0.5.3-0.2

Actually, I missed a bit in the diff.
-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
diff -Nru yaml-cpp-0.5.3/debian/changelog yaml-cpp-0.5.3/debian/changelog
--- yaml-cpp-0.5.3/debian/changelog	2018-11-19 16:29:13.0 +0100
+++ yaml-cpp-0.5.3/debian/changelog	2018-11-21 16:57:39.0 +0100
@@ -1,3 +1,10 @@
+yaml-cpp (0.5.3-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload 
+  * Bump soname to libyaml-cpp0.5d1 to account for ABI break (Closes: #914190)
+
+ -- Julian Andres Klode   Wed, 21 Nov 2018 16:57:39 +0100
+
 yaml-cpp (0.5.3-0.1) unstable; urgency=medium
 
   * Non-maintainer upload with acknowledgement from Andreas Tille.
diff -Nru yaml-cpp-0.5.3/debian/control yaml-cpp-0.5.3/debian/control
--- yaml-cpp-0.5.3/debian/control	2018-11-19 16:29:11.0 +0100
+++ yaml-cpp-0.5.3/debian/control	2018-11-21 16:57:39.0 +0100
@@ -12,15 +12,13 @@
 Vcs-Browser: https://salsa.debian.org/debian/yaml-cpp
 Homepage: https://github.com/jbeder/yaml-cpp
 
-Package: libyaml-cpp0.5v5
+Package: libyaml-cpp0.5d1
 Architecture: any
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends},
  ${misc:Depends}
 Pre-Depends: ${misc:Pre-Depends}
-Conflicts: libyaml-cpp0.5
-Replaces: libyaml-cpp0.5
 Description: YAML parser and emitter for C++
  yaml-cpp is a C++ library for parsing and emitting data in YAML 1.2, a
  human-readable data serialization format.
@@ -31,7 +29,7 @@
 Architecture: any
 Multi-Arch: same
 Section: libdevel
-Depends: libyaml-cpp0.5v5 (= ${binary:Version}),
+Depends: libyaml-cpp0.5d1 (= ${binary:Version}),
  libboost-dev,
  ${misc:Depends}
 Description: YAML parser and emitter for C++ - development files
diff -Nru yaml-cpp-0.5.3/debian/libyaml-cpp0.5d1.install yaml-cpp-0.5.3/debian/libyaml-cpp0.5d1.install
--- yaml-cpp-0.5.3/debian/libyaml-cpp0.5d1.install	1970-01-01 01:00:00.0 +0100
+++ yaml-cpp-0.5.3/debian/libyaml-cpp0.5d1.install	2018-11-19 15:49:19.0 +0100
@@ -0,0 +1 @@
+usr/lib/*/libyaml-cpp.so.*
diff -Nru yaml-cpp-0.5.3/debian/libyaml-cpp0.5v5.install yaml-cpp-0.5.3/debian/libyaml-cpp0.5v5.install
--- yaml-cpp-0.5.3/debian/libyaml-cpp0.5v5.install	2018-11-19 15:49:19.0 +0100
+++ yaml-cpp-0.5.3/debian/libyaml-cpp0.5v5.install	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-usr/lib/*/libyaml-cpp.so.*
diff -Nru yaml-cpp-0.5.3/debian/patches/bump-soname-for-abi-break.patch yaml-cpp-0.5.3/debian/patches/bump-soname-for-abi-break.patch
--- yaml-cpp-0.5.3/debian/patches/bump-soname-for-abi-break.patch	1970-01-01 01:00:00.0 +0100
+++ yaml-cpp-0.5.3/debian/patches/bump-soname-for-abi-break.patch	2018-11-21 16:57:39.0 +0100
@@ -0,0 +1,19 @@
+Description:  Bump soname to libyaml-cpp0.5d1 to account for ABI break 
+ A new field has been added to a class, breaking ABI
+Author: Julian Andres Klode 
+Bug-Debian: https://bugs.debian.org/914190
+Last-Update: 2018-11-21
+
+--- a/CMakeLists.txt
 b/CMakeLists.txt
+@@ -279,8 +279,8 @@ set_target_properties(yaml-cpp PROPERTIE
+ )
+ 
+ set_target_properties(yaml-cpp PROPERTIES
+-	VERSION "${YAML_CPP_VERSION}"
+-	SOVERSION "${YAML_CPP_VERSION_MAJOR}.${YAML_CPP_VERSION_MINOR}"
++	VERSION "${YAML_CPP_VERSION}d1"
++	SOVERSION "${YAML_CPP_VERSION_MAJOR}.${YAML_CPP_VERSION_MINOR}d1"
+ 	PROJECT_LABEL "yaml-cpp ${LABEL_SUFFIX}"
+ )
+ 
diff -Nru yaml-cpp-0.5.3/debian/patches/series yaml-cpp-0.5.3/debian/patches/series
--- yaml-cpp-0.5.3/debian/patches/series	2018-11-19 16:10:30.0 +0100
+++ yaml-cpp-0.5.3/debian/patches/series	2018-11-21 16:57:39.0 +0100
@@ -3,3 +3,4 @@
 reproducible-build.patch
 0003-Workaround-bug-in-googletest-fixing-bug-812284.patch
 0006-Fix-usage-of-boost-next-and-boost-prior.patch
+bump-soname-for-abi-break.patch

Bug#914276: monkeysign tries to access an external key server during the tests