Bug#850895: bacula: Please migrate to openssl1.1 in buster

[Sebastian Andrzej Siewior]

On 2017-11-10 00:48:34 [+0100], Carsten Leonhardt wrote:
> Sebastian Andrzej Siewior  writes:
> Hi,
Hi,

> > oh boy. Yes, definitely. Something like that in the attached patch?
> > (this time not even compile tested).
> 
> adding that patch on top of the others I get the following error when
> trying to compile:
> 
> Compiling openssl.c
> openssl.c: In function 'int init_crypto()':
> openssl.c:289:11: error: invalid conversion from 'int (*)(const char*,
> stat*) throw ()' to 'int' [-fpermissive]
> return stat;

grml. The attached version should do it.

> The first set of 5 patches seem to work though, a backup run with them
> is almost finished now without apparent problems.

Okay. So if it works and you so no problems we could throw them at
upsteam, right?

> Regards,
> 
> Carsten

Sebastian
>From b24350f437064af4564d7b07263eb88b2de82a44 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior 
Date: Thu, 9 Nov 2017 21:55:20 +0100
Subject: [PATCH] crypto: remove most of OpenSSL initcallbacks for 1.1

In OpenSSL 1.1 the thread model atomically initialized the library so
there is no need to invoke the init calls, like it was needed for 1.0.2
and earlier. The may be needed for non-standard inits like no-error
strings or so (not the case here). So the ifdef avoids them.

Also, in 1.1 there is no need to teach OpenSSL how to do locking and so
on. Infect, those functions are null-macros as for 1.0.2 compat. So
another ifdef avoids them, too.

I made four function static and removed them the header file since they
don't seem to be used outside of that openssl.c file.

This leaves us the 1.1 init part down to openssl_seed_prng(). I would
actually suggest to get rid of it. OpenSSL is able to gather some
entropy if needed. I don't think reading 2x 1024KiB from system's
entropy on each invocation of the program is wise. But I leave it to
the maintainer to make a decision, I just point it out.

Signed-off-by: Sebastian Andrzej Siewior 
---
 src/lib/openssl.c | 35 +++
 src/lib/openssl.h |  4 
 2 files changed, 19 insertions(+), 20 deletions(-)

diff --git a/src/lib/openssl.c b/src/lib/openssl.c
index 64b0e96009a7..23ac946cfaee 100644
--- a/src/lib/openssl.c
+++ b/src/lib/openssl.c
@@ -41,15 +41,6 @@
 
 /* Are we initialized? */
 static int crypto_initialized = false;
-
-/* Array of mutexes for use with OpenSSL static locking */
-static pthread_mutex_t *mutexes;
-
-/* OpenSSL dynamic locking structure */
-struct CRYPTO_dynlock_value {
-   pthread_mutex_t mutex;
-};
-
 /*
  * ***FIXME*** this is a sort of dummy to avoid having to
  *   change all the existing code to pass either a jcr or
@@ -61,7 +52,6 @@ void openssl_post_errors(int code, const char *errstring)
openssl_post_errors(NULL, code, errstring);
 }
 
-
 /*
  * Post all per-thread openssl errors
  */
@@ -79,6 +69,15 @@ void openssl_post_errors(JCR *jcr, int code, const char *errstring)
}
 }
 
+#if (OPENSSL_VERSION_NUMBER < 0x1010L)
+/* Array of mutexes for use with OpenSSL static locking */
+static pthread_mutex_t *mutexes;
+
+/* OpenSSL dynamic locking structure */
+struct CRYPTO_dynlock_value {
+   pthread_mutex_t mutex;
+};
+
 /*
  * Return an OpenSSL thread ID
  *  Returns: thread ID
@@ -151,12 +150,11 @@ static void openssl_update_static_mutex (int mode, int i, const char *file, int
  *  Returns: 0 on success
  *   errno on failure
  */
-int openssl_init_threads (void)
+static int openssl_init_threads (void)
 {
int i, numlocks;
int stat;
 
-
/* Set thread ID callback */
CRYPTO_set_id_callback(get_openssl_thread_id);
 
@@ -185,7 +183,7 @@ int openssl_init_threads (void)
 /*
  * Clean up OpenSSL threading support
  */
-void openssl_cleanup_threads(void)
+static void openssl_cleanup_threads(void)
 {
int i, numlocks;
int stat;
@@ -216,13 +214,14 @@ void openssl_cleanup_threads(void)
CRYPTO_set_dynlock_destroy_callback(NULL);
 }
 
+#endif
 
 /*
  * Seed OpenSSL PRNG
  *  Returns: 1 on success
  *   0 on failure
  */
-int openssl_seed_prng (void)
+static int openssl_seed_prng (void)
 {
const char *names[]  = { "/dev/urandom", "/dev/random", NULL };
int i;
@@ -247,7 +246,7 @@ int openssl_seed_prng (void)
  *  Returns: 1 on success
  *   0 on failure
  */
-int openssl_save_prng (void)
+static int openssl_save_prng (void)
 {
// ***FIXME***
// Implement PRNG state save
@@ -262,8 +261,9 @@ int openssl_save_prng (void)
  */
 int init_crypto (void)
 {
-   int stat;
+   int stat = 0;
 
+#if (OPENSSL_VERSION_NUMBER < 0x1010L)
if ((stat = openssl_init_threads()) != 0) {
   berrno be;
   Jmsg1(NULL, M_ABORT, 0,
@@ -278,6 +278,7 @@ int init_crypto (void)
 
/* Register OpenSSL ciphers and digests */
OpenSSL_add_all_algorithms();
+#endif
 
if (!openssl_seed_prng()) {
   Jmsg0(NULL, M_ERROR_TERM, 0, _("Failed to seed OpenSSL PRNG\n"));
@@ -309,6 +310,7 @@ int cleanup_crypto (void)
   Jmsg0(NULL, M_ERROR, 0, _("Failed to sav

Bug#881302: marked as done (RFS: gnustep-sqlclient/1.8.1-2)

[Yavor Doganov]

Adam Borowski wrote:
> The changelog looks... odd:

Indeed, I merged the NMU which fixes #845851 as it still affects the
version in experimental (that's why I close the bug once again, to be
marked as "fixed" in 1.8.1-2).  Isn't this the recommended practice?

An upload to unstable requires the release team's approval for a
library transition and it would interfere with the ongoing
gnustep-base transition.

> Thus, I've uploaded as-is, as the rest looks fine.

Thanks!

Bug#880971: git-buildpackage: looking for the equivalent of svn-do

[Guido Günther]

control: tag -1 +help
control: severity -1 wishlist

Hi,
On Thu, Nov 09, 2017 at 03:37:47PM +0100, Andreas Beckmann wrote:
> On 11/09/2017 01:26 PM, Guido Günther wrote:
> > I'm not familiar with svn-do so please bear with me. Looking at:
> > 
> > https://manpages.debian.org/stretch/svn-buildpackage/svn-do.1.en.html
> > 
> > we could add a "gbp overlay-do". Let's use this bug number for sorting
> > this out.
> 
> source code for svn-do is here:
> https://anonscm.debian.org/viewvc/collab-maint/deb-maint/svn-buildpackage/trunk/contrib/svn-do?revision=23023&view=markup
> 
> You'll have at least one user that will test "gbp overlay-do" (although
> I doubt that I'll use something else than the default "$SHELL"
> command)

Since I'm not likely to become a user of it either: could you figure
something out that works for you and keep the bug report up to date with
that? If something is missing in existing tools let me know and once we
have something working we can look into merging it in. Either in
examples/ or as an "official" command.

Cheers,
 -- Guido

> 
> > 
> >> Here are the issues I've encountered so far:
> >>
> >> * only the main .orig.tar.gz is unpacked, but the sub-components
> >> .orig-*.tar.gz are not
> > 
> > This is true and I've cloned the bug to get a new number.
> 
> I noticed that this is a "normal" issue (not related to my attempt to
> get something svn-do alike) the other day when I tried to build
> nvidia-cuda-toolkit on the ppc64el porterbox and half the tree was
> missing, just didn't get around to factor this out as a separate issue.
> 
> >> * since exporting does not preserve timestamps, always the full debian/
> >>   tree will be copied back (unlike svn-do)
> > 
> > I'm not sure what you mean here. Preserve timestamps of what exactly the
> > exported debian dir? The copying back would be done by gbp-do? I you
> > think there's s.th. wrong already (even with a gbp overlay-do) please
> > clone this bug so we can work out the details there.
> 
> I don't think git archive has the opportunity to "preserve" timestamps
> from the WC (seems to be one timestamp for all files, taken from newest
> file (or commit), didn't work out the details) ... but maybe that's
> something that can be "fixed" while copying back.
> I got the "cp -vuapf X Y" from svn-do, maybe something else can be used
> to only copy back files that actually changed content (not just
> timestamp). And deleting disappeared files could be considered as well.
> 
> What I was thinking about here was that "cp -vuapf X Y" lists all files
> as copied back (or probably excluding the one that contributed the
> newest timestamp), making that output just noise, so the -v could be
> dropped as well. (With svn-do I usually got a list of files that were
> actually changed, plus some symlinks)
> 
> >> * in case of failure, the --git-builder command is used as a python
> >>   format string:
> 
> > This is sad but true and I've cloned the bug to get a new number.
> 
> wasn't sure if I had caused this by some "unsupported" type of command ...
> 
> >> * Is it possible to use an upstream-version subdirectory for the
> >>   tarball-dir? E.g.
> >>   tarball-dir = ../tarballs-nvidia-cuda-toolkit/%{upstream-version}
> > 
> > We're not doing any expansion on the tarball-dir. If this is a desireable
> > feature let's please move this into a separate wishlist bug.
> 
> Not sure if I want to pursue this ... depends on how I'm going to handle
> the storage backend of the tarball-dir (for now it will stay on svn, and
> per-upstream-version subdirectories would have allowed to do more sparse
> svn checkouts, but I'd need to implement something in the package for that).
> But since we can reproducibly build the upstream tarballs, we don't even
> need to go through a central repository any more.
> (btw, the last upstream releases of nvidia-cuda-toolkit were about
> 2.5 GB of blobs per release)
> 
> 
> Andreas
> 

Bug#881316: ITP: node-npm-package-arg -- Parse the things that can be arguments to npm install

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-npm-package-arg
  Version : 6.0.0
  Upstream Author : Isaac Z. Schlueter  (http://blog.izs.me/)
* URL : https://github.com/npm/npm-package-arg
* License : ISC
  Programming Lang: JavaScript
  Description : Parse the things that can be arguments to npm install

 Parses package name and specifier passed to commands like npm install or
 npm cache add, or as found in package.json dependency sections.
 .
 Node.js is an event-based server-side JavaScript engine.

Dependency of npm 5.x



signature.asc
Description: OpenPGP digital signature

Bug#881315: htop: the desktop htop icon requires xterm or sensible-terminal when installing mate desktop. Otherwise he does not start. I did not try under other environments.

[Christophe LELOUP]

Package: htop
Version: 2.0.2-1
Severity: normal

Dear Maintainer,

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

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

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


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

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

Versions of packages htop depends on:
ii  libc6 2.24-11+deb9u1
ii  libncursesw5  6.0+20161126-1+deb9u1
ii  libtinfo5 6.0+20161126-1+deb9u1

htop recommends no packages.

Versions of packages htop suggests:
ii  lsof4.89+dfsg-0.1
pn  strace  

-- no debconf information

Bug#881314: lvm2 upgrade causes boot failure

[Bastian Blank]

Control: severity -1 serious

On Fri, Nov 10, 2017 at 06:37:36PM +1300, Ben Caradoc-Davies wrote:
> Severity: critical
> Justification: breaks the whole system

Nope, it only breaks itself.

> upgrading to lvm2 2.02.176-2 (and related packages) results in boot failure.
> Photo of boot message attached.

Not pretty useful.

> Upgrade was:

Please provide the dpkg log.

Bastian

-- 
Death, when unnecessary, is a tragic thing.
-- Flint, "Requiem for Methuselah", stardate 5843.7

Bug#881311: [git-buildpackage/master] import-dsc: Apply filters on debian tarballs too

[Guido Günther]

tag 881311 pending
thanks

Date:   Fri Nov 10 07:42:05 2017 +0100
Author: Guido Günther 
Commit ID: d9fb2dfff4cfa94262d8def5ccd501a1fe4478a5
Commit URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=d9fb2dfff4cfa94262d8def5ccd501a1fe4478a5
Patch URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=d9fb2dfff4cfa94262d8def5ccd501a1fe4478a5

import-dsc: Apply filters on debian tarballs too

Closes: #881311

  

Bug#881293: [Pkg-libvirt-maintainers] Bug#881293: libvirt-daemon: libvirtd sefgfault when disconnect and reconnect iso

[Guido Günther]

Hi,
On Thu, Nov 09, 2017 at 11:47:01AM -0700, Jeff Ketchum wrote:
> Package: libvirt-daemon
> Version: 3.9.0-1
> Severity: important
> 
> 
> [  271.168779] libvirtd[1177]: segfault at 10 ip 7f2cae6d9208 sp 
> 7f2cb80049a0 error 4 in libvirt_driver_qemu.so[7f2cae64d000+173000]

Domain XML and virsh commands you use for disconnect / reconnect
please.
Cheers,
 -- Guido

> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
> LANGUAGE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages libvirt-daemon depends on:
> ii  libacl1 2.2.52-3+b1
> ii  libapparmor12.11.1-3
> ii  libaudit1   1:2.8.1-2
> ii  libavahi-client30.7-3
> ii  libavahi-common30.7-3
> ii  libblkid1   2.30.2-0.1
> ii  libc6   2.24-17
> ii  libcap-ng0  0.7.7-3.1+b1
> ii  libcurl3-gnutls 7.56.1-1
> ii  libdbus-1-3 1.12.0-1
> ii  libdevmapper1.02.1  2:1.02.145-1
> ii  libfuse22.9.7-1
> ii  libgnutls30 3.5.16-1
> ii  libnetcf1   1:0.2.8-1+b2
> ii  libnl-3-200 3.2.27-2
> ii  libnl-route-3-200   3.2.27-2
> ii  libnuma12.0.11-2.1
> ii  libparted2  3.2-18
> ii  libpcap0.8  1.8.1-5
> ii  libpciaccess0   0.13.4-1+b2
> ii  libsasl2-2  2.1.27~101-g0780600+dfsg-3
> ii  libselinux1 2.7-2
> ii  libssh2-1   1.8.0-1
> ii  libudev1235-2
> ii  libvirt03.9.0-1
> ii  libxen-4.8  4.8.1-1+deb9u3
> ii  libxenstore3.0  4.8.1-1+deb9u3
> ii  libxml2 2.9.4+dfsg1-5+b1
> ii  libyajl22.1.0-2+b3
> 
> Versions of packages libvirt-daemon recommends:
> ii  libxml2-utils   2.9.4+dfsg1-5+b1
> ii  netcat-openbsd  1.178-3
> ii  qemu1:2.10.0+dfsg-2
> ii  qemu-kvm1:2.10.0+dfsg-2
> 
> Versions of packages libvirt-daemon suggests:
> pn  libvirt-daemon-driver-storage-gluster   
> pn  libvirt-daemon-driver-storage-rbd   
> pn  libvirt-daemon-driver-storage-sheepdog  
> pn  libvirt-daemon-driver-storage-zfs   
> ii  libvirt-daemon-system   3.9.0-1
> pn  numad   
> 
> -- no debconf information
> 
> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers
> 

Bug#881311: git-buildpackage: gbp import-dsc: Ignores option --filter

[Guido Günther]

Hi,
On Fri, Nov 10, 2017 at 02:42:20AM +0100, Jonas Smedegaard wrote:
> Package: git-buildpackage
> Version: 0.9.1
> Severity: normal
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> I want to fork a package, and track my work using git-buildpackage.
> 
> I start out with this command:
> 
>   gbp import-dsc --filter='*/gbp.conf' --filter=debian/gbp.conf apt:hashcat
> 
> What I expect is a git with no .git* files and no debian/gbp.conf - but
> those files exist in the created git.

We only filered on the upstream tarball so far (but the manpage didn't
say that explicitly) so I added filtering on the debian tarball as well.
Cheers,
 -- Guido

Bug#881314: lvm2 upgrade causes boot failure

[Ben Caradoc-Davies]

Package: lvm2
Version: 2.02.176-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

upgrading to lvm2 2.02.176-2 (and related packages) results in boot failure.
Photo of boot message attached.

Upgrade was:

dmeventd:amd64 (2:1.02.145-1, 2:1.02.145-2)
dmsetup:amd64 (2:1.02.145-1, 2:1.02.145-2)
libdevmapper-event1.02.1:amd64 (2:1.02.145-1, 2:1.02.145-2)
libdevmapper1.02.1:amd64 (2:1.02.145-1, 2:1.02.145-2)
liblvm2app2.2:amd64 (2.02.176-1, 2.02.176-2)
liblvm2cmd2.02:amd64 (2.02.176-1, 2.02.176-2)
lvm2:amd64 (2.02.176-1, 2.02.176-2)

Workaround is to downgrade these packages, which results in a normal boot.

Kind regards,
Ben.



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

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

Versions of packages lvm2 depends on:
pn  dmeventd  
pn  dmsetup   
ii  libblkid1 2.30.2-0.1
ii  libc6 2.24-17
pn  libdevmapper-event1.02.1  
pn  libdevmapper1.02.1
pn  liblvm2app2.2 
ii  libreadline5  5.2+dfsg-3+b1
ii  libsystemd0   235-2
ii  libudev1  235-2
ii  lsb-base  9.20170808

Versions of packages lvm2 recommends:
ii  thin-provisioning-tools  0.7.4-2

lvm2 suggests no packages.

-- Configuration Files:
/etc/lvm/lvm.conf changed:
config {
# Configuration option config/checks.
# If enabled, any LVM configuration mismatch is reported.
# This implies checking that the configuration key is understood by
# LVM and that the value of the key is the proper type. If disabled,
# any configuration mismatch is ignored and the default value is used
# without any warning (a message about the configuration key not being
# found is issued in verbose mode only).
checks = 1
# Configuration option config/abort_on_errors.
# Abort the LVM process if a configuration mismatch is found.
abort_on_errors = 0
# Configuration option config/profile_dir.
# Directory where LVM looks for configuration profiles.
profile_dir = "/etc/lvm/profile"
}
devices {
# Configuration option devices/dir.
# Directory in which to create volume group device nodes.
# Commands also accept this as a prefix on volume group names.
# This configuration option is advanced.
dir = "/dev"
# Configuration option devices/scan.
# Directories containing device nodes to use with LVM.
# This configuration option is advanced.
scan = [ "/dev" ]
# Configuration option devices/obtain_device_list_from_udev.
# Obtain the list of available devices from udev.
# This avoids opening or using any inapplicable non-block devices or
# subdirectories found in the udev directory. Any device node or
# symlink not managed by udev in the udev directory is ignored. This
# setting applies only to the udev-managed device directory; other
# directories will be scanned fully. LVM needs to be compiled with
# udev support for this setting to apply.
obtain_device_list_from_udev = 1
# Configuration option devices/external_device_info_source.
# Select an external device information source.
# Some information may already be available in the system and LVM can
# use this information to determine the exact type or use of devices it
# processes. Using an existing external device information source can
# speed up device processing as LVM does not need to run its own native
# routines to acquire this information. For example, this information
# is used to drive LVM filtering like MD component detection, multipath
# component detection, partition detection and others.
# 
# Accepted values:
#   none
# No external device information source is used.
#   udev
# Reuse existing udev database records. Applicable only if LVM is
# compiled with udev support.
# 
external_device_info_source = "none"
# Configuration option devices/preferred_names.
# Select which path name to display for a block device.
# If multiple path names exist for a block device, and LVM needs to
# display a name for the device, the path names are matched against
# each item in this list of regular expressions. The first match is
# used. Try to avoid using undescriptive /dev/dm-N names, if present.
# If no preferred name matches, or if preferred_names are not defined,
# the following built-in preferences are applied in order until

Bug#881281: ugly scaled icons in the toolar

[Gunter Königsmann]

I had added the scaling because normally gtk+ automatically delivers me the 
icons in the Right  size. But
 - on some icon themes a few icons were grossly of the wrong size. For example 
in my favourite theme I got a 512x512 pixel-sun on a 96dpi display.
 - and on debian a few themes lack some standard icons so wxMaxima falls back 
to the icons it comes with - that are big so scaling them down still doesn't 
produce icons that are too blurry.

 If you
 - extend the patch to just scale the icons if they are obviously way too big
 - and if you limit the scaling to 1/n and 1.5/n with n being an integer (this 
will reduce the blur to a minimum in the cases scaling is necessary)
I'll apply it and upstream it so the next official release no more scales icons 
on wxGTK.

Thanks a lot,
and kind regards,

 Gunter.

Bug#880582: qemu-user detection

[Adam Borowski]

Hi!
There is a way to detect qemu-user: export QEMU_VERSION=meow then execve()
something.  As "meow" is not a legal value of that variable for any guest,
qemu will error out.

Fixing a future version of qemu is not enough: it's usual to run unstable
chroots on a stable host.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ Laws we want back: Poland, Dz.U. 1921 nr.30 poz.177 (also Dz.U. 
⣾⠁⢰⠒⠀⣿⡁ 1920 nr.11 poz.61): Art.2: An official, guilty of accepting a gift
⢿⡄⠘⠷⠚⠋⠀ or another material benefit, or a promise thereof, [in matters
⠈⠳⣄ relevant to duties], shall be punished by death by shooting.

Bug#881313: neovim: Please add "Provides: editor"

[Matthias Urlichs]

Source: neovim
Version: 0.2.1-2
Severity: normal

neovim updates the "editor" alternative but doesn't say it Provides: for
it, forcing me to have some other unused editor installed.

Please fix.

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'oldstable'), (600, 'unstable'), (550, 
'experimental'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Bug#881312: libreoffice-report-builder depends on libreoffice-report-builder-bin which is already installed

[annadane]

Package: libreoffice
Version: 1:5.4.3~rc1-2
Severity: important

Dear Maintainer,

When trying to do a libreoffice upgrade, I get the following: 
libreoffice-report-builder : Depends: libreoffice-report-builder-bin (>= 
1:5.4.3) but 1:5.4.3~rc1-2 is installed. apt-cache policy 
libreoffice-report-builder-bin shows the installed version and the candidate 
version being the same (1:5.4.3-rc1-2) and libreoffice-report-builder-bin is 
listed in the tracker as being included with this update 
(https://tracker.debian.org/news/885045).

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

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

Versions of packages libreoffice depends on:
ii  libreoffice-avmedia-backend-gstreamer  1:5.4.3~rc1-2
ii  libreoffice-base   1:5.4.3~rc1-2
ii  libreoffice-calc   1:5.4.3~rc1-2
ii  libreoffice-core   1:5.4.3~rc1-2
ii  libreoffice-draw   1:5.4.3~rc1-2
ii  libreoffice-impress1:5.4.3~rc1-2
ii  libreoffice-math   1:5.4.3~rc1-2
ii  libreoffice-report-builder-bin 1:5.4.3~rc1-2
ii  libreoffice-writer 1:5.4.3~rc1-2
ii  python3-uno1:5.4.3~rc1-2

Versions of packages libreoffice recommends:
ii  fonts-crosextra-caladea 20130214-2
ii  fonts-crosextra-carlito 20130920-1
ii  fonts-dejavu2.37-1
ii  fonts-linuxlibertine5.3.0-3
ii  fonts-open-sans 1.11-1
ii  fonts-sil-gentium-basic 1.1-7
ii  libreoffice-java-common 1:5.4.3~rc1-2
ii  libreoffice-librelogo   1:5.4.3-1
ii  libreoffice-nlpsolver   0.9+LibO5.4.3-1
ii  libreoffice-ogltrans1:5.4.3~rc1-2
ii  libreoffice-report-builder  1:5.4.3~rc1-2
ii  libreoffice-script-provider-bsh 1:5.4.3~rc1-2
ii  libreoffice-script-provider-js  1:5.4.3~rc1-2
ii  libreoffice-script-provider-python  1:5.4.3~rc1-2
ii  libreoffice-sdbc-postgresql 1:5.4.3~rc1-2
ii  libreoffice-wiki-publisher  1.2.0+LibO5.4.3-1

Versions of packages libreoffice suggests:
ii  cups-bsd  2.2.6-2
ii  default-jre [java6-runtime]   2:1.8-59
ii  ghostscript   9.22~dfsg-1
ii  gstreamer1.0-libav1.12.3-1
ii  gstreamer1.0-plugins-bad  1.12.3-2
ii  gstreamer1.0-plugins-base 1.12.3-1
ii  gstreamer1.0-plugins-good 1.12.3-1
ii  gstreamer1.0-plugins-ugly 1.12.3-1
ii  hunspell-en-us [hunspell-dictionary]  1:2017.08.24
ii  hyphen-en-us [hyphen-hyphenation-patterns]2.8.8-5
pn  iceweasel | firefox | icedove | thunderbird | iceape-bro  
ii  imagemagick   8:6.9.7.4+dfsg-16
ii  imagemagick-6.q16 [imagemagick]   8:6.9.7.4+dfsg-16
ii  libgl11.0.0-1
pn  libreoffice-gnome 
pn  libreoffice-grammarcheck  
pn  libreoffice-help  
pn  libreoffice-l10n  
pn  libreoffice-officebean
pn  libsane   
ii  libxrender1   1:0.9.10-1
pn  myspell-dictionary
ii  mythes-en-us [mythes-thesaurus]   1:5.4.3-1
pn  openclipart2-libreoffice | openclipart-libreoffice
ii  openjdk-8-jre [java6-runtime] 8u151-b12-1
pn  pstoedit  
pn  unixodbc  

Versions of packages libreoffice-core depends on:
ii  fontconfig2.12.3-0.2
ii  fonts-opensymbol  2:102.10+LibO5.4.3-1
ii  libboost-date-time1.62.0  1.62.0+dfsg-4+b2
ii  libc6 2.24-17
ii  libcairo2 1.15.8-2
ii  libclucene-contribs1v52.3.3.4+dfsg-1
ii  libclucene-core1v52.3.3.4+dfsg-1
ii  libcmis-0.5-5v5   0.5.1+git20160603-3+b1
ii  libcups2  2.2.6-2
ii  libcurl3-gnutls   7.56.1-1
ii  libdbus-1-3   1.12.0-1
ii  libdbus-glib-1-2  0.108-3
ii  libdconf1 0.26.1-1
ii  libeot0   0.01-4+b1
ii  libepoxy0 1.3.1-3
i

Bug#879886: [Debian-med-packaging] Bug#879886: libhts2: libhts2 needs to handle ABI changes

[Afif Elghraoui]

On November 9, 2017 6:20:03 PM EST, Diane Trout  wrote:
>
[...]
>
>Anyone want to review? or should I go ahead and release?
>

I think you can release. However, it appears the changelog wasn't updated in 
git since the last upload [1] you'll need to go for a 1.5-3.

regards
Afif

1. 
http://metadata.ftp-master.debian.org/changelogs/main/h/htslib/htslib_1.5-2_changelog

Bug#880942: ITP: ghdl -- VHDL 2008/93/87 simulator

[Paul Wise]

On Fri, 2017-11-10 at 02:35 +0100, Andreas Bombe wrote:

> Is there anything else I forgot to address?

A couple of copy-pastes from DevRef that may be relevant:

The version control system used by the previous maintainer might
contain useful changes, so it might be a good idea to have a look
there. Check if the control file of the previous package contained
any headers linking to the version control system for the package
and if it still exists.

I also think it is a good idea to continue the VCS and debian/changelog
from where the last maintainer left it, for continuity.

https://anonscm.debian.org/git/collab-maint/ghdl.git

Package removals from unstable (not testing, stable or oldstable)
trigger the closing of all bugs related to the package. You should
look through all the closed bugs (including archived bugs) and
unarchive and reopen any that were closed in a version ending in +rm
and still apply. Any that no longer apply should be marked as fixed
in the correct version if that is known. 

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

[Michael Biebl]

Control: tags -1 + moreinfo

Am 10.11.2017 um 01:10 schrieb Alex King:
> After installing the package to get systemd-nspawnd, I created an etch
> image with:
> 
> # cd /var/lib/machines
> # debootstrap --variant=minbase --no-check-gpg --arch=i386 etch etchruby \
> http://archive.debian.org/debian/
> 
> This system can't resolve DNS names:
> 
> # systemd-nspawn --directory etchruby/
> Spawning container etchruby on /var/lib/machines/etchruby.
> Press ^] three times within 1s to kill container.
> etchruby:~# apt-get update
> Err http://archive.debian.org etch Release.gpg
>   Temporary failure resolving 'archive.debian.org'
> Failed to fetch http://archive.debian.org/debian/dists/etch/Release.gpg  
> Temporary failure resolving 'archive.debian.org'
> Reading package lists... Done
> E: Some index files failed to download, they have been ignored, or old ones 
> used instead.
> 
> /etc/resolv.conf inside the container is apparently bind-mounted from the
> host's /lib/systemd/resolv.conf, and cannot be modified inside the container.

I can't reproduce the problem. I don't have systemd-resolved enabled
though. My guess is that you have resolved enabled (but not properly
configured), that's why systemd-nspawn picks up /lib/systemd/resolv.conf

How does your /etc/resolv.conf look like in the container?

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



signature.asc
Description: OpenPGP digital signature

Bug#881134: RFS: runescape/0.2-2 [QA] -- Multiplayer online game set in a fantasy world

[Carlos Donizete Froes]

Fixed 'disclaimer' and 'autobuilding' in d/copyright.

---
Disclaimer:
 This package is not part of the Debian distribution. It is provided in the
 non-free file area as a convenience for Debian users.
 The contents of this package is an unofficial installer of the Runescape
 client and distributed for non-commercial and non-profit use.
 This package does NOT contain official Runescape client
 [https://www.runescape.com] itself as this would violate copyright laws
 and the wishes of Jagex Ltd authors [https://www.jagex.com/terms].
Autobuilding:
 According to the adopted license, there is no problem to create
 this software in various architectures automatically and distribute it.
---

Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780

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

Bug#880942: ITP: ghdl -- VHDL 2008/93/87 simulator

[Andreas Bombe]

On Thu, Nov 09, 2017 at 02:45:37PM +0800, Paul Wise wrote:
> On Mon, Nov 6, 2017 at 7:51 AM, Andreas Bombe wrote:
> 
> > Back then we all agreed that writing free replacements was the way to go
> > but I never got around to help out with that. Turns out upstream has
> > implemented that in the meantime (not yet for VHDL 2008 though) so I
> > guess now is the time to really bring it back.
> 
> Please note the extra steps required when reintroducing packages:
> 
> https://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-pkgs

I haven't contacted the previous maintainer because he orphaned the
package long before it was removed (citing changed interests) and
because he is hardly active in Debian anymore.

Since upstream now offers LLVM and its own code generator as backends in
addition to GCC and I want to package all of these, packaging
requirements have changed considerably so most of it will be new.

Is there anything else I forgot to address?

Bug#881311: git-buildpackage: gbp import-dsc: Ignores option --filter

[Jonas Smedegaard]

Package: git-buildpackage
Version: 0.9.1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I want to fork a package, and track my work using git-buildpackage.

I start out with this command:

  gbp import-dsc --filter='*/gbp.conf' --filter=debian/gbp.conf apt:hashcat

What I expect is a git with no .git* files and no debian/gbp.conf - but
those files exist in the created git.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAloFA/kACgkQLHwxRsGg
ASEdChAAp7f9UNYNJzkfbJLHCpKwBxiQpEj2OyKd5tfTw7ea+7pRSAGO7KISx0Zf
BVZAoCoxuQxWiRuIofhSYxzIp6z5I5QhBxoiU89b+OWS3JQdBP/yypEdEfDFNQgQ
trosu5Rf2EVu4kQY+96V3eyEWHVKNXKFg75/XQjVOSrumHT9EsWT9MypHT1Egphb
UL2DHHyc8lO7AO3gVwqI4JbmZ39xaFK6ipMsim1PPMb+aq+FE1XHZd63z93XstOa
S2Hmhn2mLRyixKxW5X1UbAtC1J4RbBJrr/LjL9KFvmzKf79LcHBKLzESnr7OOZP/
GWCqp+IxYIIzDBEx4TX4i0tS5Oj6LzFzvyGe+z92F1v+zRyq5mm0h6jI7ZsUe07S
EfT9mBKk5JtFxftQfVwcMPr6yvPmRzJ/N8NficULOgmHMk+1NlIH4YDE3+oFvRzm
OuhVwJ9pULIXpBEom3EnYx4NLddL4zGrUX0ugTcP5J5kUfFlpb0xTr3XAiI5qiJt
52hy8kHq8Djj2A0G7GRxKfTVco+PcVd8Glzh82qvOrrEsOWN0fhZO+IFixg3aTXn
ceniF+rB/7rpekyuC4DMGrmiiYIJEcQ96OZjiJhwytHjqK3R2SMTPFnuC9u6OrIY
iVypEgoxroGJBunOawJVXg1RiCI7mqJz1iRCeqak8vM8xlL5OKM=
=AxZM
-END PGP SIGNATURE-

Bug#619421: tuxguitar: no message buffer overruns

[tuxguitar-user]

Package: tuxguitar
Followup-For: Bug #619421

Dear Maintainer,

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

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

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


-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

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

Versions of packages tuxguitar depends on:
ii  default-jre [java2-runtime]2:1.8-58
ii  file   1:5.30-1+deb9u1
ii  libitext-java  2.1.7-11
ii  libjs-jquery   3.1.1-2
ii  libswt-cairo-gtk-3-jni 3.8.2-3
ii  libswt-gtk-3-java  3.8.2-3
ii  libswt-webkit-gtk-3-jni3.8.2-3
ii  openjdk-8-jre [java2-runtime]  8u151-b12-1~deb9u1

Versions of packages tuxguitar recommends:
pn  tuxguitar-alsa  
ii  tuxguitar-oss   1.2-22

Versions of packages tuxguitar suggests:
pn  lilypond   
ii  tuxguitar-jsa  1.2-22

also on 64bit deb9.1 not working.
installed tuxguitar-alsa/fluidsynth/jack/jsa/oss, non working.
'jack server not running', so installed jack. jack_test outputs:

-- no debconf information

Jack server is said being in non-realtime mode...
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*--*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*--*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
*-*-*-*-*-*-*-*-*-*-*-*-*-* Start jack server stress test  
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*--*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*--*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
JACK server started
symbol jack_finish cannot be found in inprocess
!!! ERROR !!! cannot load internal client "inprocess" intclient 0x0 status 0x 1 
!
jack_client_new: deprecated
cannot create new client; jack_test already exists
Client name = jack_test conflits with another running client
Cannot read socket fd = 12 err = Success
Unknown request 0
Cannot connect to the server
JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for -1, skipping 
unlock
!!! ERROR !!! Jackd is in a non-expected realtime mode (RT = 0).
error : port_name is empty (msg from callback)
port_name "jack_test:port" already exists
error : jack_port_set_name: deprecated (msg from callback)
error : jack_port_set_name: deprecated (msg from callback)
*** buffer overflow detected ***: jack_test terminated
=== Backtrace: =
/lib/i386-linux-gnu/libc.so.6(+0x6737a)[0xb72d037a]
/lib/i386-linux-gnu/libc.so.6(__fortify_fail+0x37)[0xb7360f37]
/lib/i386-linux-gnu/libc.so.6(+0xf61d8)[0xb735f1d8]
/lib/i386-linux-gnu/libc.so.6(+0xf57cf)[0xb735e7cf]
/usr/lib/i386-linux-gnu/libjack.so.0(+0x178e3)[0xb76a48e3]
/usr/lib/i386-linux-gnu/libjack.so.0(+0xda13)[0xb769aa13]
jack_test(+0x2659)[0x434659]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xb7281276]
jack_test(+0x6473)[0x438473]
=== Memory map: 
00432000-0043e000 r-xp  08:02 2367954/usr/bin/jack_test
0043e000-0043f000 r--p b000 08:02 2367954/usr/bin/jack_test
0043f000-0044 rw-p c000 08:02 2367954/usr/bin/jack_test
0159d000-015c2000 rw-p  00:00 0  [heap]
b1f0-b1f21000 rw-p  00:00 0 
b1f21000-b200 ---p  00:00 0 
b2089000-b6f0 rw-s  00:13 25717  /dev/shm/jack-1000-0
b6f0-b6f21000 rw-p  00:00 0 
b6f21000-b700 ---p  00:00 0 
b7055000-b7056000 rw-p  00:00 0 
b7056000-b7057000 ---p  00:00 0 
b7057000-b70d7000 rw-p  00:00 0 
b70d7000-b70d8000 rw-s 000

Bug#881303: lvm2: dh_installsystemd fragment generates warning during configuration

[Felipe Sateler]

On Thu, Nov 9, 2017 at 8:29 PM, Michael Biebl  wrote:
> Control: reassign -1 debhelper 10.9.2
>
> On Thu, 09 Nov 2017 21:59:27 + Julian Gilbey  wrote:
>> Package: lvm2
>> Version: 2.02.176-1
>> Severity: normal
>>
>> I don't know whether the bug here lies in dh_installsystemd or in
>> lvm2, so please reassign to dh_installsystemd if this is the wrong
>> package.
>>
>> At the end of lvm2's debian/rules, it says:
>>   dh_installsystemd --remaining-packages
>>
>> But the lvm2 postinst then ends up finishing with the following:
>>
>> # Automatically added by dh_installsystemd/10.10.5
>> if [ -d /run/systemd/system ]; then
>>   systemctl --system daemon-reload >/dev/null || true
>>   if [ -n "$2" ]; then
>>   _dh_action=try-restart
>>   else
>>   _dh_action=start
>>   fi
>>   deb-systemd-invoke $_dh_action  >/dev/null || true
>> fi
>> # End automatically added section
>>
>> and this throws up the warning message:
>>
>> Syntax: /usr/bin/deb-systemd-invoke   [ ...]
>>
>> because no unit file is listed after $_dh_action.
>>
>> I'm inclined to think that this is a debhelper bug...
>>
>
> I agree. Re-assigning to debhelper. dh_installsystemd should not
> generate such a (bogus) start/restart action.
>
> I wonder if this is a regression from dh_systemd_* or if the old tools
> are affected as well.

I think this is a regression. By merging both actions, the "exit if
there are no actionable units" condition changed.

The attached (untested) patch should fix the issue.

-- 

Saludos,
Felipe Sateler
diff --git a/dh_installsystemd b/dh_installsystemd
index 29c60db4..8772d022 100755
--- a/dh_installsystemd
+++ b/dh_installsystemd
@@ -344,43 +344,45 @@ foreach my $package (@{$dh{DOPACKAGES}}) {
}
}
 
-   next if @start_units == 0 && @enable_units == 0;
-
-   for my $unit (sort @enable_units) {
-   my $base = q{'} . basename($unit) . q{'};
-   if ($dh{NO_ENABLE}) {
-   autoscript($package, 'postinst', 
'postinst-systemd-dont-enable', { 'UNITFILE' => $base });
-   } else {
-   autoscript($package, 'postinst', 
'postinst-systemd-enable', { 'UNITFILE' => $base });
+   if (@enable_units) {
+   for my $unit (sort @enable_units) {
+   my $base = q{'} . basename($unit) . q{'};
+   if ($dh{NO_ENABLE}) {
+   autoscript($package, 'postinst', 
'postinst-systemd-dont-enable', { 'UNITFILE' => $base });
+   } else {
+   autoscript($package, 'postinst', 
'postinst-systemd-enable', { 'UNITFILE' => $base });
+   }
}
+   my $enableunitargs = join(' ', sort map { q{'} . basename($_) . 
q{'} } @enable_units);
+   autoscript($package, 'postrm', 'postrm-systemd', {'UNITFILES' 
=> $enableunitargs });
}
-   my $enableunitargs = join(' ', sort map { q{'} . basename($_) . q{'} } 
@enable_units);
-   autoscript($package, 'postrm', 'postrm-systemd', {'UNITFILES' => 
$enableunitargs });

-   # The $package and $sed parameters are always the same.
-   # This wrapper function makes the following logic easier to read.
-   my $startunitargs = join(' ', sort map { q{'} . basename($_) . q{'} } 
@start_units);
-   my $start_autoscript = sub {
-   my ($script, $filename) = @_;
-   autoscript($package, $script, $filename, { 'UNITFILES' => 
$startunitargs });
-   };
-
-   if ($dh{RESTART_AFTER_UPGRADE}) {
-   my $snippet = "postinst-systemd-restart" . ($dh{NO_START} ? 
"nostart" : "");
-   $start_autoscript->("postinst", $snippet);
-   } elsif (!$dh{NO_START}) {
-   # We need to stop/start before/after the upgrade.
-   $start_autoscript->("postinst", "postinst-systemd-start");
-   }
+   if (@start_units) {
+   # The $package and $sed parameters are always the same.
+   # This wrapper function makes the following logic easier to 
read.
+   my $startunitargs = join(' ', sort map { q{'} . basename($_) . 
q{'} } @start_units);
+   my $start_autoscript = sub {
+   my ($script, $filename) = @_;
+   autoscript($package, $script, $filename, { 'UNITFILES' 
=> $startunitargs });
+   };
+   
+   if ($dh{RESTART_AFTER_UPGRADE}) {
+   my $snippet = "postinst-systemd-restart" . 
($dh{NO_START} ? "nostart" : "");
+   $start_autoscript->("postinst", $snippet);
+   } elsif (!$dh{NO_START}) {
+   # We need to stop/start before/after the upgrade.
+   $start_autoscript->("postinst", 
"postinst-systemd-start");
+   }
 
-   $start_autoscript->("postrm", "postrm-systemd-reload-only")

Bug#877773: groovebasin crashes

[Felipe Sateler]

Control: reassign -1 libleveldb1v5 1.20-1
Control: retitle -1 libleveldb1v5: breaks ABI without SONAME bump

On Thu, Oct 5, 2017 at 8:38 AM, Thadeu Lima de Souza Cascardo
 wrote:
>
> Package: groovebasin
> Version: 1.4.0-1
> Severity: grave
>
> groovebasin crashes when simply running with 'groovebasin'. Setting this
> as grave as it seems to make it unusable for any user.
>
> I was using groovebasin during the stretch release cycle and though I
> found some problems related to filename encoding, it was a great player.
>
> After the release, some nodejs updates seemed to require binary NMUs due
> to ABI incompatibilities for some of the libraries used by groovebasin.
> After they were completed, I could upgrade nodejs and groovebasin. But
> for a while, I didn't run groovebasin, so didn't notice the issue. So,
> it's possible that it's related to the nodejs upgrade.

Thanks for this info, it proved helpful. I think the problem is that
leveldb broke ABI without SONAME bump (and transition). Downgrading to
1.19 or rebuilding node-leveldown fixes the crash.

I think (but my C++ fu is not very strong) that the problem is the
addition of the max_file_size to the Options class. ABI tracker seems
to agree with me[1].

Dear leveldb maintainers, please bump soname and do a transition.


[1] 
https://abi-laboratory.pro/tracker/compat_report/leveldb/1.19/1.20/ecd6d/abi_compat_report.html

-- 

Saludos,
Felipe Sateler

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

[Alex King]

Package: systemd-container
Version: 232-25+deb9u1
Severity: normal
Tags: upstream

Dear Maintainer,

After installing the package to get systemd-nspawnd, I created an etch
image with:

# cd /var/lib/machines
# debootstrap --variant=minbase --no-check-gpg --arch=i386 etch etchruby \
http://archive.debian.org/debian/

This system can't resolve DNS names:

# systemd-nspawn --directory etchruby/
Spawning container etchruby on /var/lib/machines/etchruby.
Press ^] three times within 1s to kill container.
etchruby:~# apt-get update
Err http://archive.debian.org etch Release.gpg
  Temporary failure resolving 'archive.debian.org'
Failed to fetch http://archive.debian.org/debian/dists/etch/Release.gpg  
Temporary failure resolving 'archive.debian.org'
Reading package lists... Done
E: Some index files failed to download, they have been ignored, or old ones 
used instead.

/etc/resolv.conf inside the container is apparently bind-mounted from the
host's /lib/systemd/resolv.conf, and cannot be modified inside the container.

This is probably only a problem for non-systemd containers, as systemd
presumably has some workaround.  It also presumably is only a problem if
systemd-resolved is not used (as is standard in Debian.)

This appears to be identified at https://github.com/systemd/systemd/issues/4649
and closed in https://github.com/systemd/systemd/pull/5369, not sure if that's
made it in to a release yet.

Would be nice to have a fix for this in Debian.


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

Kernel: Linux 4.4.96-rh115-20171102201402.xenU.x86_64 (SMP w/1 CPU core)
Locale: LANG=en_NZ.utf8, LC_CTYPE=en_NZ.utf8 (charmap=UTF-8), 
LANGUAGE=en_NZ.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-container depends on:
ii  dbus 1.10.22-0+deb9u1
ii  libacl1  2.2.52-3+b1
ii  libblkid12.29.2-1
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.24-11+deb9u1
ii  libcurl3-gnutls  7.52.1-5+deb9u2
ii  libgcrypt20  1.7.6-2+deb9u2
ii  libip4tc01.6.0+snapshot20161117-6
ii  liblzma5 5.2.2-1.2+b1
ii  libseccomp2  2.3.1-2.1
ii  libselinux1  2.6-3+b3
ii  systemd  232-25+deb9u1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages systemd-container recommends:
ii  btrfs-progs4.7.3-1
ii  libnss-mymachines  232-25+deb9u1

systemd-container suggests no packages.

-- no debconf information

Bug#880011: csound: Macro system on csound make segfault

[Felipe Sateler]

Control: forwarded -1 https://github.com/csound/csound/issues/871

2017-11-08 16:45 GMT-03:00 Mickael Viey :

> Le 08/11/2017 à 14:19, Felipe Sateler a écrit :
>
>> Control: forcemerge -1 880010
>> Control: tags -1 moreinfo
>>
>> On Sat, Oct 28, 2017 at 7:54 AM, Mickael Viey  wrote:
>>
>>> Package: csound
>>>
>>> Version: 1:6.08.0~dfsg-1
>>> Severity: normal
>>>
>>> Dear Maintainer,
>>>
>>>
>>> I have some csd files I made on another platforms which generate
>>> segfault when running with this version of csound. After diagnostic It
>>> appears that the macro system which is responsible.
>>>
>>> By example, this macro works:
>>> #define TIME # 0.25 #
>>> #define freq # 146 #
>>>
>>>
>>> #define T # $freq #
>>> #define Am # $freq * 17 / 16 #
>>> #define AM # $freq * 9/8 #
>>>
>>> But If I had this after te last line:
>>>
>>> #define E # $freq #
>>>
>>> I get a segfault. I will join the complete csd file I used for my tests.
>>>
>> Weird. I can reproduce on a stretch docker container, but I can't
>> reproduce on sid, either with 6.09 or rebuilding 6.08 . I ran out of
>> time, but could you try rebuilding csound and see if the problem
>> persists?
>>
>> Hi,
>
> I am not sure what you mean by "rebuild" but this is what I done:
>

Thanks, but I meant recompile the csound sources, not just reinstall.

Anyway, I have debugged some more. Turns out the error in sid is still
present, it just doesn't cause a crash. I have forwarded upstream to the
above url.

The error is not due to the macro, but due to the 3/2 p7. This is invalid
syntax, and that triggers the crash/malfunction (the crash is in the error
printing code, heh). You can work around the problem by fixing the syntax
error and passing 1.5.


-- 

Saludos,
Felipe Sateler

Bug#850895: bacula: Please migrate to openssl1.1 in buster

[Carsten Leonhardt]

Sebastian Andrzej Siewior  writes:

Hi,

> oh boy. Yes, definitely. Something like that in the attached patch?
> (this time not even compile tested).

adding that patch on top of the others I get the following error when
trying to compile:

Compiling openssl.c
openssl.c: In function 'int init_crypto()':
openssl.c:289:11: error: invalid conversion from 'int (*)(const char*,
stat*) throw ()' to 'int' [-fpermissive]
return stat;
   ^~~~
Makefile:182: recipe for target 'openssl.lo' failed
make[3]: *** [openssl.lo] Error 1


The first set of 5 patches seem to work though, a backup run with them
is almost finished now without apparent problems.

Regards,

Carsten

Bug#881309: RM: pjproject [hurd-i386 kfreebsd-amd64 kfreebsd-i386] -- ROM; FTBFS

[Bernhard Schmidt]

Package: ftp.debian.org
Severity: normal

Hi,

please remove pjproject and all reverse dependencies on hurd-i386 and
kfreebsd-* from unstable. pjproject has been FTBFS on these arches for
quite some time now and upstream is not going to change this. This makes
the versions still available on those architectures outdated and affected
by security bugs.

The list of reverse dependencies to be removed on those architectures
is 

asterisk asterisk-espeak asterisk-flite asterisk-opus asterisk-prompt-de 
asterisk-prompt-es

Thanks,
Bernhard

Bug#881303: lvm2: dh_installsystemd fragment generates warning during configuration

[Michael Biebl]

Control: reassign -1 debhelper 10.9.2

On Thu, 09 Nov 2017 21:59:27 + Julian Gilbey  wrote:
> Package: lvm2
> Version: 2.02.176-1
> Severity: normal
> 
> I don't know whether the bug here lies in dh_installsystemd or in
> lvm2, so please reassign to dh_installsystemd if this is the wrong
> package.
> 
> At the end of lvm2's debian/rules, it says:
>   dh_installsystemd --remaining-packages
> 
> But the lvm2 postinst then ends up finishing with the following:
> 
> # Automatically added by dh_installsystemd/10.10.5
> if [ -d /run/systemd/system ]; then
>   systemctl --system daemon-reload >/dev/null || true
>   if [ -n "$2" ]; then
>   _dh_action=try-restart
>   else
>   _dh_action=start
>   fi
>   deb-systemd-invoke $_dh_action  >/dev/null || true
> fi
> # End automatically added section
> 
> and this throws up the warning message:
> 
> Syntax: /usr/bin/deb-systemd-invoke   [ ...]
> 
> because no unit file is listed after $_dh_action.
> 
> I'm inclined to think that this is a debhelper bug...
> 

I agree. Re-assigning to debhelper. dh_installsystemd should not
generate such a (bogus) start/restart action.

I wonder if this is a regression from dh_systemd_* or if the old tools
are affected as well.

Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#881308: lcgdm FTBFS: gssapi_openssl.h:114:5: error: unknown type name 'STACK'

[Adrian Bunk]

Source: lcgdm
Version: 1.9.0-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes lcgdm FTBFS:

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

...
In file included from Csec_plugin_GSS.c:63:0:
gssapi_openssl.h:114:5: error: unknown type name 'STACK'
 STACK * group;
 ^
Makefile:133: recipe for target 'Csec_plugin_GSI.o' failed
make[2]: *** [Csec_plugin_GSI.o] Error 1

Bug#879886: libhts2: libhts2 needs to handle ABI changes

[Diane Trout]

> As a gotcha, remember that this bug was born out of the fact that
> there
> was a package requiring a >= 1.5 dependency.  I recommend you compile
> the symbol file with something << 1.5 (i.e. 1.4 or just re-add the
> file
> that was removed) and then update it appropriately so there will be
> not
> so tight versions.

Done.

I dug out the previous symbols files, which appeared to have been built
up to 1.3.1, then I applied changes from 1.4.1 and then finally 1.5.

There were a few symbols changes that were not clear cut and so they're
currently removed but were done in a separate commit.

There from 1.3.1 to 1.4.1 three symbols ks_destroy, ks_getuntil2,
ks_init that disappeared from the library, but are in the headers as
macros. The header macros look like they haven't changed much from even
the 1.0 release, so I don't know why they were removed.

From 1.4.1 to 1.5 there was a block of zf* functions that were removed.
However those are from the "private" cram headers and so 1.5 is likely
to cause issues for the programs that are using the cram support.

Anyone want to review? or should I go ahead and release?

Diane

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

Bug#881307: agda-stdlib FTBFS: : commitBuffer: invalid argument (invalid character)

[Adrian Bunk]

Source: agda-stdlib
Version: 0.13-1
Severity: serious

Some recent change in unstable makes agda-stdlib FTBFS:

https://tests.reproducible-builds.org/debian/history/agda-stdlib.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/agda-stdlib.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/agda-stdlib-0.13'
ghc --make GenerateEverything.hs
[1 of 1] Compiling Main ( GenerateEverything.hs, 
GenerateEverything.o )
Linking GenerateEverything ...
./GenerateEverything
agda +RTS -K1G -RTS -i /build/1st/agda-stdlib-0.13 -i 
/build/1st/agda-stdlib-0.13/src /build/1st/agda-stdlib-0.13/Everything.agda
Checking Everything (/build/1st/agda-stdlib-0.13/Everything.agda).
 Checking Algebra (/build/1st/agda-stdlib-0.13/src/Algebra.agda).
  Checking Relation.Binary 
(/build/1st/agda-stdlib-0.13/src/Relation/Binary.agda).
   Checking Data.Product (/build/1st/agda-stdlib-0.13/src/Data/Product.agda).
Checking Function (/build/1st/agda-stdlib-0.13/src/Function.agda).
 Checking Level (/build/1st/agda-stdlib-0.13/src/Level.agda).
 Finished Level.
Finished Function.
Checking Relation.Nullary 
(/build/1st/agda-stdlib-0.13/src/Relation/Nullary.agda).
 Checking Data.Empty (/build/1st/agda-stdlib-0.13/src/Data/Empty.agda).
/build/1st/agda-stdlib-0.13/src/Data/Empty.agda:13,1-31
The HASKELL pragma has been deprecated. Use
{-# FOREIGN GHC data AgdaEmpty #-} instead. This will be an error
in Agda 2.6.
when scope checking the declaration
  {-# HASKELL
  data AgdaEmpty
  #-}
/build/1st/agda-stdlib-0.13/src/Data/Empty.agda:14,1-58
The COMPILED_DATA pragma has been deprecated. Use
{-# COMPILE GHC /build/1st/agda-stdlib-0.13/src/Relation/Nullary.agda:11,13-23
: commitBuffer: invalid argument (invalid character)
debian/rules:13: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1

Bug#881306: jessie-pu: package python-tablib/0.9.11-2 CVE-2017-2810

[Thomas Goirand]

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

Hi,

After fixing Stretch in release team bug #879702, here's the request
for fixing Jessie, since Salvatore asks for it. Debdiff attached.
Package available from:

http://sid.gplhost.com/jessie-proposed-updates/python-tablib/

Please allow me to upload this update for Jessie.
Cheers,

Thomas Goirand (zigo)
diff -Nru python-tablib-0.9.11/debian/changelog 
python-tablib-0.9.11/debian/changelog
--- python-tablib-0.9.11/debian/changelog   2013-05-12 14:21:10.0 
+0200
+++ python-tablib-0.9.11/debian/changelog   2017-10-24 21:15:19.0 
+0200
@@ -1,3 +1,9 @@
+python-tablib (0.9.11-2+deb8u1) jessie; urgency=low
+
+  * CVE-2017-2810: apply upstream patch: use safe load (Closes: #864818).
+
+ -- Thomas Goirand   Tue, 24 Oct 2017 21:15:19 +0200
+
 python-tablib (0.9.11-2) unstable; urgency=low
 
   * Uploading to unstable.
diff -Nru python-tablib-0.9.11/debian/patches/CVE-2017-2810-use_safe_load.patch 
python-tablib-0.9.11/debian/patches/CVE-2017-2810-use_safe_load.patch
--- python-tablib-0.9.11/debian/patches/CVE-2017-2810-use_safe_load.patch   
1970-01-01 01:00:00.0 +0100
+++ python-tablib-0.9.11/debian/patches/CVE-2017-2810-use_safe_load.patch   
2017-10-24 21:15:19.0 +0200
@@ -0,0 +1,17 @@
+Description: use safe load
+Author: Kenneth Reitz 
+Origin: 
https://github.com/kennethreitz/tablib/commit/69abfc3ada5d754cb152119c0b4777043657cb6e
+Bug-Debian: https://bugs.debian.org/864818
+Last-Update: 2017-10-24
+
+--- python-tablib-0.9.11.orig/tablib/formats/_yaml.py
 python-tablib-0.9.11/tablib/formats/_yaml.py
+@@ -46,7 +46,7 @@ def import_book(dbook, in_stream):
+ 
+ dbook.wipe()
+ 
+-for sheet in yaml.load(in_stream):
++for sheet in yaml.safe_load(in_stream):
+ data = tablib.Dataset()
+ data.title = sheet['title']
+ data.dict = sheet['data']
diff -Nru python-tablib-0.9.11/debian/patches/series 
python-tablib-0.9.11/debian/patches/series
--- python-tablib-0.9.11/debian/patches/series  1970-01-01 01:00:00.0 
+0100
+++ python-tablib-0.9.11/debian/patches/series  2017-10-24 21:15:19.0 
+0200
@@ -0,0 +1 @@
+CVE-2017-2810-use_safe_load.patch

Bug#835197: RFP: fonts-eosrei-emojione

[Mike Hommey]

On Sun, Nov 05, 2017 at 11:48:37AM -0500, Jeremy Bicha wrote:
> Control: retitle -1 RFP: fonts-emojitwo -- Color emoji font originally
> released as Emojione 2.2
> 
> On Sat, Aug 19, 2017 at 5:29 PM, Jeremy Bicha  wrote:
> > It appears like Emojione is no longer under a DFSG-compatible license.
> 
> Updating the bug title, since I'm skeptical that even non-free could
> provide the latest Emojione.
> 
> > By the way, my understanding is that the new GNOME color emoji feature
> > requires these:
> 
> All of that is done now in Debian Testing except for fontconfig 2.12.6
> (soon I hope). Also fonts-noto-color-emoji is in the NEW queue.
> 
> Mike, I wonder why Mozilla standardized on the Emojione font. Given
> Emojione's license shift and the fact that it appears like Linux
> distros prefer the Noto emoji, do you think Mozilla would reconsider?
> (Fedora 27 includes the Noto emoji by default. I expect Ubuntu 18.04
> LTS to include fonts-noto-color-emoji by default. Probably Debian
> GNOME Buster too. It is the same emoji used by Google in the latest
> stock Android devices.)

Mozilla is not using https://github.com/eosrei/emojione-color-font. It's
using https://github.com/mozilla/emojione-colr

Mike

Bug#881297: An example debian package

[Steinar Bang]

I currently use this self-packaged debian package:
 https://github.com/steinarb/karaf-deb-packaging

This debian package isn't built according to debian java standards so it
isn't immediately useful for a "real" karaf .deb package, but there may
be stuff in the installation scripts that could be borrowed.

I forked my github project from this project
 https://github.com/DemisR/karaf-deb-packaging
and did the following:
 1. Switched from Oracle Java SDK to openjdk
 2. Switched from using the proprietary karaf-wrapper to using the
included init scrips (and later systemd)
 3. Tried using /var/lib/karaf
 4. Updated the karaf version several times


This document describe (in Norwegian, unfortunately), how to build the
.deb package on a debian system and then start karaf (steps 1, 2 and 3),
and then ssh into karaf (step 5), add an extra maven repository (step 6)
and use maven to provision and start a web application (step 7):
 
https://github.com/steinarb/ukelonn#oppsett-av-webappen-på-en-server-med-debian-gnulinux

Bug#881231: [Pkg-nlp-ja-devel] Bug#881231: chasen-dictutils: writes uninitialized memory to .dat files

[NOKUBI Takatsugu]

On Thu, 09 Nov 2017 16:12:32 +0900,
Vagrant Cascadian wrote:
> > The attached patch initializes memory written to .dat files.
> > Once applied, ipadic can be built reproducibly in our current
> > experimental framework.
> 
> I can confirm that the patch fixed the issue when building on Debian
> Stretch. I'm guessing sid or buster would work as well.

I'll apply the patch.

Bug#881162: tomcat7: Server reports 404 on any request, even /

[Felix Knecht]

I can also confirm that 7.0.28-4+deb7u17 works on our server again.

Bug#881304: gajim does not reconnect after suspend

[W. Martin Borgert]

On 2017-11-09 22:50, Alex wrote:
> Package: gajim
> Version: Gajim does not reconnect after software suspend

Which version? :~)
Could you try the latest master from debian/experimental?


signature.asc
Description: PGP signature

Bug#881297: Prior discussion about packing apache karaf

[Steinar Bang]

Back in September 2015 there were discussions about packaging karaf, but
it doesn't look like anything happened:
 https://lists.debian.org/debian-java/2015/09/threads.html#00086

Bug#881305: wiki.debian.org: Wiki page for Spotify lists libssl1.0.0 in the Stretch section but not available in Stretch

[annadane]

Package: wiki.debian.org
Severity: normal

Dear Maintainer,

On the wiki page for Spotify (https://wiki.debian.org/spotify), in the section 
for Debian Stretch, it says to download the libssl1.0.0 package, which is an 
issue because 1) It provides a Jessie link and 2) That package is not available 
in Stretch.


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

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

Bug#881298: u-boot-imx: Add DHCOM iMX6 PDK support

[Vagrant Cascadian]

Control: tag 881298 pending

On 2017-11-09, Marek Vasut wrote:
> Attached is a patch which adds the DHCOM iMX6 PDK platform into the
> U-Boot-imx package.

Thanks for the patch, applied to git:

  
https://anonscm.debian.org/cgit/collab-maint/u-boot.git/commit/?id=efe85da7ba8f4aa1cd2349cb73dfbe8f4efd0ea2

Will include in the next upload.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#881290: qemu-kvm: Passthrough of SAS2008-based HBA card fails on E3-1225v3 due to failed DMA mapping (-14)

[Johannes Falke]

Alright, thanks for the feedback.

Johannes

On Thu, 9 Nov 2017 22:04:56 +0300 Michael Tokarev  wrote:
> Control: severity -1 minor
>
> 09.11.2017 21:10, Johannes Falke wrote:
> > Package: qemu-kvm
> > Version: 1:2.8+dfsg-6+deb9u3
> > Severity: important
> >
> > Dear Maintainer,
> >
> > there is a bug preventing many people with my combination of hardware
> > from using PCI passthrough. I am not actually sure whether the bug is
> > in kernel/kvm, vfio or qemu, however, as qemu is the highest-level of
> > these, I am reporting the bug here as you will likely know better where
> > the origin of the bug may be found.
>
> Just for you to understand. This bug is _very_ unlikely will be addressed
> here, most likely it'll sit in the bugtracker forever.
>
> The reason is simple: one has to have your hardware to replicate this
issue,
> AND one has to be knowlegeable in the area of device pass-through.
>
> You can _try_ to ask upstream about this, maybe this will work better -
> because at least one of the requiriments will be met in this case. Maybe
> you'll have the ability to communicate this matter and will be able to
> provide enough info or debugging for it to be fixed.  I definitely wont
> be a broken phone between you and upstream.
>
> At any rate, I don't think the severity of this bug is important.
> Qemu works for very large number of users, just very specific use case
> fails.  Marking as minor.
>
> I'm not trying to be rude or something, I'm just describing the situation.
>
> Thanks,
>
> /mjt
>
>

Bug#881304: gajim does not reconnect after suspend

[Alex]

Package: gajim
Version: Gajim does not reconnect after software suspend
Severity: normal

Dear Maintainer,
gajim does not reconnect after suspend to ram.
This is annoying, as I often notice it after quite some time and miss
when people try to reach me.

with kind regards,
Alex


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

Versions of packages gajim depends on:
pn  dnsutils  
pn  gir1.2-gtk-3.0
ii  python2.7.13-2
ii  python-gtk2   2.24.0-5.1
pn  python-nbxmpp 
ii  python-openssl16.2.0-1
ii  python-pyasn1 0.1.9-2
ii  python3   3.5.3-1
pn  python3-gi
pn  python3-gi-cairo  
pn  python3-nbxmpp
pn  python3-openssl   
pn  python3-pyasn1

Versions of packages gajim recommends:
ii  ca-certificates  20161130+nmu1
ii  dbus 1.10.22-0+deb9u1
pn  notification-daemon  
pn  pulseaudio-utils | alsa-utils | sox | oss4-base  
ii  python-crypto2.6.1-7
ii  python-dbus  1.2.4-1+b1
pn  python-gnupg 
pn  python3-crypto   
pn  python3-dbus 
pn  python3-gnupg

Versions of packages gajim suggests:
pn  aspell-en | aspell-dictionary  
pn  avahi-daemon   
pn  dvipng 
pn  gir1.2-gtkspell3-3.0   
pn  gir1.2-gupnpigd-1.0
pn  gir1.2-secret-1
pn  gnome-keyring  
pn  gstreamer0.10-plugins-ugly 
pn  kwalletcli 
pn  libgtkspell0   
ii  libxss11:1.2.2-1
pn  nautilus-sendto
pn  network-manager
pn  python-avahi   
pn  python-gconf   
pn  python-gnome2  
pn  python-gnomekeyring
pn  python-gupnp-igd   
ii  python-kerberos1.1.5-2+b2
ii  python-pycurl  7.43.0-2
pn  python3-avahi  
pn  python3-gconf  
pn  python3-gnome2 
pn  python3-kerberos   
ii  python3-pycurl 7.43.0-2
pn  texlive-latex-base 

Bug#881303: lvm2: dh_installsystemd fragment generates warning during configuration

[Julian Gilbey]

Package: lvm2
Version: 2.02.176-1
Severity: normal

I don't know whether the bug here lies in dh_installsystemd or in
lvm2, so please reassign to dh_installsystemd if this is the wrong
package.

At the end of lvm2's debian/rules, it says:
dh_installsystemd --remaining-packages

But the lvm2 postinst then ends up finishing with the following:

# Automatically added by dh_installsystemd/10.10.5
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
if [ -n "$2" ]; then
_dh_action=try-restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action  >/dev/null || true
fi
# End automatically added section

and this throws up the warning message:

Syntax: /usr/bin/deb-systemd-invoke   [ ...]

because no unit file is listed after $_dh_action.

I'm inclined to think that this is a debhelper bug...

Best wishes,

   Julian

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

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

Versions of packages lvm2 depends on:
ii  dmeventd  2:1.02.145-1
ii  dmsetup   2:1.02.145-1
ii  libblkid1 2.30.2-0.1
ii  libc6 2.24-17
ii  libdevmapper-event1.02.1  2:1.02.145-1
ii  libdevmapper1.02.12:1.02.145-1
ii  liblvm2app2.2 2.02.176-1
ii  libreadline5  5.2+dfsg-3+b1
ii  libsystemd0   235-2
ii  libudev1  235-2
ii  lsb-base  9.20170808

Versions of packages lvm2 recommends:
ii  thin-provisioning-tools  0.7.4-2

lvm2 suggests no packages.

-- no debconf information

Bug#849602: firefox: font EmojiOne must be installed below /usr/share/fonts

[Laurent Bigonville]

blocks 881299 849602
thanks

On Thu, 29 Dec 2016 03:44:07 +0100 Jonas Smedegaard  wrote:

> Firefox 50 and newer ships with the font EmojiOne.
>
> According to Debian Policy, fonts must be made generally available, by
> installing it below /usr/share/fonts and then (if needed) symlinking to
> the custom location expected by the application.
>

Thunderbird actually also needs that font (see #881299)

So the best would to split that font from the firefox and let firefox 
and thunderbird depend on it

Bug#881299: thunderbird: Please install EmojiOneMozilla.ttf in /usr/lib/thunderbird/fonts/

[Laurent Bigonville]

On Thu, 09 Nov 2017 22:04:39 +0100 Laurent Bigonville  
wrote:

>
> Hi,
>
> Could you please install the EmojiOneMozilla.ttf font in
> /usr/lib/thunderbird/fonts/
>
> Currently emoji are not diplayed properly, I just tried on my system and
> add the file in that location fixed it.
>
> Firefox is doing the same by installing that font in
> /usr/lib/firefox/fonts
>

Well actually no

This seems to be against the debian policy, see bug #849602

IMHO, firefox should create a package with that font and thunderbird 
should depends on that package

Bug#881302: RFS: gnustep-sqlclient/1.8.1-2

[Yavor Doganov]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "gnustep-sqlclient".

 * Package name: gnustep-sqlclient
   Version : 1.8.1-2
   Upstream Author : Richard Frith-Macdonald 
 * URL : http://gnustep.org
 * License : LGPL-3.0+
   Section : libs

It builds these binary packages:

 libsqlclient-dev - SQL client library for GNUstep (development files)
 libsqlclient1.8 - SQL client library for GNUstep (runtime library)

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

  https://mentors.debian.net/package/gnustep-sqlclient

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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/gnustep-sqlclient/gnustep-sqlclient_1.8.1-2.dsc

Git repository (please checkout the "experimental" branch):

  https://anonscm.debian.org/git/pkg-gnustep/gnustep-sqlclient.git

Changes since the last upload:

  * Ack NMU; thanks Gert Wollny (Closes: #845851).
  * debian/patches/sparc64-alignment.patch: New; fixes tests failure and
FTBFS on sparc64 (Closes: #880477).
  * debian/patches/spelling-errors.patch: New; fix some spelling errors.
  * debian/patches/series: New file.
  * debian/rules: Remove optimization snippet which is now defined
globally in /usr/share/GNUstep/debian/config.mk.  Build with default
hardening flags.  Remove trailing whitespace.
(override_dh_strip): Pass --dbgsym-migration.
  * debian/control (Build-Depends): Require gnustep-make >= 2.7.0-3 for
the optim variable definition.  Bump debhelper requirement to >= 10.
Add gnustep-base-doc to ensure that proper cross-references are
generated by autogsdoc.
(libsqlclient1.8-dbg): Remove; switch to automatic dbgsym package.
(Vcs-Git, Vcs-Browser): Use secure URIs.
(Standards-Version): Claim compliance with 4.1.1.
  * debian/compat: Bump compat level to 10.
  * debian/copyright: Use https for copyright format; update copyright
years.
  * debian/upstream/signing-key.asc: Replace upstream's binary signing key
with ASCII armored format.
  * debian/upstream/signing-key.pgp:
  * debian/source/include-binaries: Delete.

Bug#881287: python-daiquiri: Add python2 support

[Chris Lamb]

Hi Corey,

> Good point. I think we just need to get moving on our end. We currently
> only ship py2 for core openstack packages because upstream hasn't
> completely moved to py3

Happy to apply in that case; I was just checking it wasn't because "there
is no Python 2 package so we must make one..." :)

Alas your patch doesn't seem to work properly here:

  W: python-daiquiri: empty-binary-package
  W: python3-daiquiri: empty-binary-package

Seems to be installing to debian/tmp and never installing to
debian/python{,2}-daiquiri:

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

(Also note duplicate-short-description :p)


Regards,

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

Bug#881301: gnome-shell: segfault error 4 in libgobject-2.0.so.0.5400.2

[Lucas Dyer]

Package: gnome-shell
Version: 3.26.2-1
Severity: grave
Justification: causes non-serious data loss

Dear maintainers,

Sometimes gnome-shell crashes, randomly while using the computer or not.
Also happens when the screen is locked, even without any programs running.

The file /var/log/syslog has a lot of lines like:
gnome-shell[]: clutter_actor_insert_child_at_index: assertion 
'child->priv->parent == NULL' failed
gnome-shell[]: clutter_text_get_editable: assertion 'CLUTTER_IS_TEXT 
(self)' failed
gnome-shell[]: clutter_text_get_text: assertion 'CLUTTER_IS_TEXT (self)' 
failed
gnome-shell[]: clutter_text_set_text: assertion 'CLUTTER_IS_TEXT (self)' 
failed
gnome-shell[]: invalid unclassed pointer in cast to 'ClutterText'

And sometimes in place of that last line it has:

gnome-shell[]: invalid uninstantiatable type '(null)' in cast to 
'ClutterText'

Attached are three syslog files of the last times the segfault occurred.

Regards,
LD


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (1000, 'unstable'), (200, 'testing'), (100, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages gnome-shell depends on:
ii  caribou  0.4.21-2
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-1
ii  evolution-data-server3.26.2.1-1
ii  gir1.2-accountsservice-1.0   0.6.45-1
ii  gir1.2-atspi-2.0 2.26.2-1
ii  gir1.2-caribou-1.0   0.4.21-2
ii  gir1.2-freedesktop   1.54.1-2
ii  gir1.2-gcr-3 3.20.0-5.1
ii  gir1.2-gdesktopenums-3.0 3.24.1-1
ii  gir1.2-gdm-1.0   3.26.2.1-2
ii  gir1.2-geoclue-2.0   2.4.7-1
ii  gir1.2-glib-2.0  1.54.1-2
ii  gir1.2-gnomebluetooth-1.03.26.1-1
ii  gir1.2-gnomedesktop-3.0  3.26.2-1
ii  gir1.2-gtk-3.0   3.22.25-1
ii  gir1.2-gweather-3.0  3.26.0-1
ii  gir1.2-ibus-1.0  1.5.14-3
ii  gir1.2-mutter-1  3.26.2-1
ii  gir1.2-networkmanager-1.01.9.90-1
ii  gir1.2-nmgtk-1.0 1.8.6-1
ii  gir1.2-pango-1.0 1.40.13-1
ii  gir1.2-polkit-1.00.105-18
ii  gir1.2-rsvg-2.0  2.40.18-2
ii  gir1.2-soup-2.4  2.60.2-1
ii  gir1.2-upowerglib-1.00.99.6-1
ii  gjs  1.50.2-1
ii  gnome-backgrounds3.26.2-1
ii  gnome-settings-daemon3.26.2-1
ii  gnome-shell-common   3.26.2-1
ii  gsettings-desktop-schemas3.24.1-1
ii  libasound2   1.1.3-5
ii  libatk-bridge2.0-0   2.26.0-2
ii  libatk1.0-0  2.26.1-1
ii  libc62.24-17
ii  libcairo21.15.8-2
ii  libcanberra-gtk3-0   0.30-4
ii  libcanberra0 0.30-4
ii  libcroco30.6.12-1
ii  libdbus-glib-1-2 0.108-3
ii  libecal-1.2-19   3.26.2.1-1
ii  libedataserver-1.2-223.26.2.1-1
ii  libgcr-base-3-1  3.20.0-5.1
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libgirepository-1.0-11.54.1-2
ii  libgjs0g [libgjs0-libmozjs-52-0] 1.50.2-1
ii  libglib2.0-0 2.54.2-1
ii  libglib2.0-bin   2.54.2-1
ii  libgstreamer1.0-01.12.3-1
ii  libgtk-3-0   3.22.25-1
ii  libical2 2.0.0-1
ii  libjson-glib-1.0-0   1.4.2-2
ii  libmutter-1-03.26.2-1
ii  libnm-glib4  1.9.90-1
ii  libnm-util2  1.9.90-1
ii  libpango-1.0-0   1.40.13-1
ii  libpangocairo-1.0-0  1.40.13-1
ii  libpolkit-agent-1-0  0.105-18
ii  libpolkit-gobject-1-00.105-18
ii  libpulse-mainloop-glib0  11.1-1
ii  libpulse011.1-1
ii  libsecret-1-00.18.5-4
ii  libstartup-notification0  

Bug#881300: ITP: libmath-utils-perl -- collection of useful mathematical functions not in Perl

[Florian Schlichting]

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

* Package name: libmath-utils-perl
  Version : 1.11
  Upstream Author : John M. Gamble 
* URL : https://metacpan.org/release/Math-Utils
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : collection of useful mathematical functions not in Perl

Math::Utils is a broad collection of useful mathematical functions not
available in core perl. In addition to general-purpose functions such
as log10(), log2(), floor() or fsum(), there are generators to create
comparison functions for floating point (non-integer) numbers as well
as some polynomial operations on plain lists of coefficients.

The package will be maintained under the umbrella of the Debian Perl Group.
It is a new build-dependency of libmath-derivative-perl but seems seems useful
on its own.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.

Bug#881299: thunderbird: Please install EmojiOneMozilla.ttf in /usr/lib/thunderbird/fonts/

[Laurent Bigonville]

Package: thunderbird
Version: 1:52.4.0-1
Severity: normal

Hi,

Could you please install the EmojiOneMozilla.ttf font in
/usr/lib/thunderbird/fonts/

Currently emoji are not diplayed properly, I just tried on my system and
add the file in that location fixed it.

Firefox is doing the same by installing that font in
/usr/lib/firefox/fonts

Kind regards,

Laurent Bigonville

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

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

Versions of packages thunderbird depends on:
ii  debianutils   4.8.2
ii  fontconfig2.12.6-0.1
ii  libatk1.0-0   2.26.1-1
ii  libc6 2.24-17
ii  libcairo-gobject2 1.15.8-2
ii  libcairo2 1.15.8-2
ii  libdbus-1-3   1.12.0-1
ii  libdbus-glib-1-2  0.108-3
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-6
ii  libfontconfig12.12.6-0.1
ii  libfreetype6  2.8.1-0.1
ii  libgcc1   1:7.2.0-12
ii  libgdk-pixbuf2.0-02.36.11-1
ii  libglib2.0-0  2.54.2-1
ii  libgtk-3-03.22.25-1
ii  libhunspell-1.6-0 1.6.2-1
ii  libpango-1.0-01.40.13-1
ii  libpangocairo-1.0-0   1.40.13-1
ii  libpangoft2-1.0-0 1.40.13-1
ii  libpixman-1-0 0.34.0-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++67.2.0-12
ii  libvpx4   1.6.1-3
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc23.1-1
ii  x11-utils 7.7+3+b1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages thunderbird recommends:
ii  hunspell-en-us [hunspell-dictionary] 1:2017.08.24
ii  hunspell-fr-classical [hunspell-dictionary]  1:6.1-1
ii  lightning1:52.4.0-1

Versions of packages thunderbird suggests:
ii  apparmor  2.11.1-3
ii  fonts-lyx 2.2.3-2
ii  libgssapi-krb5-2  1.15.2-2

-- no debconf information

Bug#850895: bacula: Please migrate to openssl1.1 in buster

[Sebastian Andrzej Siewior]

On 2017-11-09 16:53:15 [+], Martin Simmons wrote:
> Hi Sebastian,
Hi Martin,

> Maybe openssl_init_threads and openssl_cleanup_threads (and helper functions)
> in src/lib/openssl.c should also be conditionalized to remove uses of the old
> threading and locking APIs?

oh boy. Yes, definitely. Something like that in the attached patch?
(this time not even compile tested).

> __Martin

Sebastian
>From 7eb1f97ca3a154818ff42e3259899fbc94140fbc Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior 
Date: Thu, 9 Nov 2017 21:55:20 +0100
Subject: [PATCH] crypto: remove most of OpenSSL initcallbacks for 1.1

In OpenSSL 1.1 the thread model atomically initialized the library so
there is no need to invoke the init calls, like it was needed for 1.0.2
and earlier. The may be needed for non-standard inits like no-error
strings or so (not the case here). So the ifdef avoids them.

Also, in 1.1 there is no need to teach OpenSSL how to do locking and so
on. Infect, those functions are null-macros as for 1.0.2 compat. So
another ifdef avoids them, too.

I made four function static and removed them the header file since they
don't seem to be used outside of that openssl.c file.

This leaves us the 1.1 init part down to openssl_seed_prng(). I would
actually suggest to get rid of it. OpenSSL is able to gather some
entropy if needed. I don't think reading 2x 1024KiB from system's
entropy on each invocation of the program is wise. But I leave it to
the maintainer to make a decision, I just point it out.

Signed-off-by: Sebastian Andrzej Siewior 
---
 src/lib/openssl.c | 33 ++---
 src/lib/openssl.h |  4 
 2 files changed, 18 insertions(+), 19 deletions(-)

diff --git a/src/lib/openssl.c b/src/lib/openssl.c
index 64b0e96009a7..d43b3c1344d5 100644
--- a/src/lib/openssl.c
+++ b/src/lib/openssl.c
@@ -41,15 +41,6 @@
 
 /* Are we initialized? */
 static int crypto_initialized = false;
-
-/* Array of mutexes for use with OpenSSL static locking */
-static pthread_mutex_t *mutexes;
-
-/* OpenSSL dynamic locking structure */
-struct CRYPTO_dynlock_value {
-   pthread_mutex_t mutex;
-};
-
 /*
  * ***FIXME*** this is a sort of dummy to avoid having to
  *   change all the existing code to pass either a jcr or
@@ -61,7 +52,6 @@ void openssl_post_errors(int code, const char *errstring)
openssl_post_errors(NULL, code, errstring);
 }
 
-
 /*
  * Post all per-thread openssl errors
  */
@@ -79,6 +69,15 @@ void openssl_post_errors(JCR *jcr, int code, const char *errstring)
}
 }
 
+#if (OPENSSL_VERSION_NUMBER < 0x1010L)
+/* Array of mutexes for use with OpenSSL static locking */
+static pthread_mutex_t *mutexes;
+
+/* OpenSSL dynamic locking structure */
+struct CRYPTO_dynlock_value {
+   pthread_mutex_t mutex;
+};
+
 /*
  * Return an OpenSSL thread ID
  *  Returns: thread ID
@@ -151,12 +150,11 @@ static void openssl_update_static_mutex (int mode, int i, const char *file, int
  *  Returns: 0 on success
  *   errno on failure
  */
-int openssl_init_threads (void)
+static int openssl_init_threads (void)
 {
int i, numlocks;
int stat;
 
-
/* Set thread ID callback */
CRYPTO_set_id_callback(get_openssl_thread_id);
 
@@ -185,7 +183,7 @@ int openssl_init_threads (void)
 /*
  * Clean up OpenSSL threading support
  */
-void openssl_cleanup_threads(void)
+static void openssl_cleanup_threads(void)
 {
int i, numlocks;
int stat;
@@ -216,13 +214,14 @@ void openssl_cleanup_threads(void)
CRYPTO_set_dynlock_destroy_callback(NULL);
 }
 
+#endif
 
 /*
  * Seed OpenSSL PRNG
  *  Returns: 1 on success
  *   0 on failure
  */
-int openssl_seed_prng (void)
+static int openssl_seed_prng (void)
 {
const char *names[]  = { "/dev/urandom", "/dev/random", NULL };
int i;
@@ -247,7 +246,7 @@ int openssl_seed_prng (void)
  *  Returns: 1 on success
  *   0 on failure
  */
-int openssl_save_prng (void)
+static int openssl_save_prng (void)
 {
// ***FIXME***
// Implement PRNG state save
@@ -262,6 +261,7 @@ int openssl_save_prng (void)
  */
 int init_crypto (void)
 {
+#if (OPENSSL_VERSION_NUMBER < 0x1010L)
int stat;
 
if ((stat = openssl_init_threads()) != 0) {
@@ -278,6 +278,7 @@ int init_crypto (void)
 
/* Register OpenSSL ciphers and digests */
OpenSSL_add_all_algorithms();
+#endif
 
if (!openssl_seed_prng()) {
   Jmsg0(NULL, M_ERROR_TERM, 0, _("Failed to seed OpenSSL PRNG\n"));
@@ -309,6 +310,7 @@ int cleanup_crypto (void)
   Jmsg0(NULL, M_ERROR, 0, _("Failed to save OpenSSL PRNG\n"));
}
 
+#if (OPENSSL_VERSION_NUMBER < 0x1010L)
openssl_cleanup_threads();
 
/* Free libssl and libcrypto error strings */
@@ -319,6 +321,7 @@ int cleanup_crypto (void)
 
/* Free memory used by PRNG */
RAND_cleanup();
+#endif
 
crypto_initialized = false;
 
diff --git a/src/lib/openssl.h b/src/lib/openssl.h
index 597517a4fd68..9374a581c735 100644
--- a/src/lib/openssl.h
+++ b/src/lib/openssl.h
@@ -39,10 +39,6 @@
 #ifdef HAVE_OP

Bug#880925: no checks to know if the debdelta mirror is up or down.

[shirish शिरीष]

at bottom :-

On 09/11/2017, A Mennucc1  wrote:
> Dear shirish,
>

Dear A Mennucc1,



> debdeltas.debian.net is the server for serving the deltas, but not the
> one that creates them.
>
> the server that creates deltas is donizetti
>

so if I were to try to find out if both the machines are working
properly or not I should try pinging -

a. debdeltas.debian.net
b. donizetti.debian.net

Would that be good enough to have some idea if they are working or not
or something more ?

Also from what you shared, you will probably be putting a point
release of debdelta as currently it is showing the 'old' one only.

─[$] apt-cache policy debdelta
debdelta:
  Installed: 0.60
  Candidate: 0.60
  Version table:
 *** 0.60 600
600 http://httpredir.debian.org/debian buster/main amd64 Packages
  1 http://httpredir.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status

> a.
>
>


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#745771: util-linux: Enable audit supprt

[Joy Latten]

The attached patch enables audit support in util-linux.

Thanks.

regards,
Joy
diff --git a/debian/control b/debian/control
index 0675acd..a72472a 100644
--- a/debian/control
+++ b/debian/control
@@ -18,7 +18,8 @@ Build-Depends: bc ,
socat ,
systemd [linux-any] ,
bison,
-   zlib1g-dev
+   zlib1g-dev,
+   libaudit-dev
 Section: base
 Priority: required
 Maintainer: LaMont Jones 
diff --git a/debian/rules b/debian/rules
index 104e469..ca76a83 100755
--- a/debian/rules
+++ b/debian/rules
@@ -11,6 +11,7 @@ ifeq ($(DEB_HOST_ARCH_OS),linux)
 CONFOPTS += --enable-raw
 CONFOPTS += --with-selinux
 CONFOPTS += --enable-partx
+CONFOPTS += --with-audit
 ifneq ($(filter stage1,$(DEB_BUILD_PROFILES)),)
 	CONFOPTS += --without-systemd --without-udev
 else

Bug#881204: safeeyes: missing dependencies

[Antonio Russo]

The package should also

Recommends: gir1.2-appindicator3-0.1

so that by default people can get a tray icon.

Bug#881298: u-boot-imx: Add DHCOM iMX6 PDK support

[Marek Vasut]

Package: u-boot-imx
Version: 2017.11-rc

Attached is a patch which adds the DHCOM iMX6 PDK platform into the
U-Boot-imx package.

-- 
Best regards,
Marek Vasut
>From 17be330fa9bb7c64bb5063dcb1828a650da4652c Mon Sep 17 00:00:00 2001
From: Marek Vasut 
Date: Tue, 26 Sep 2017 17:23:48 +0200
Subject: [PATCH] Add DHCOM i.MX6 PDK board support

Add support for the DHCOM i.MX6 PDK board. This board has:
- FEC ethernet
- EHCI USB host
- 3x SDMMC

Signed-off-by: Marek Vasut 
---
 debian/targets  | 3 +++
 debian/u-boot-imx.lintian-overrides | 2 ++
 2 files changed, 5 insertions(+)

diff --git a/debian/targets b/debian/targets
index 04058e41d9..ac7d6e3765 100644
--- a/debian/targets
+++ b/debian/targets
@@ -34,6 +34,9 @@ armhf	exynos		odroid		u-boot.bin
 # Vagrant Cascadian , Odroid-XU4
 armhf	exynos		odroid-xu3	u-boot.bin
 
+# Marek Vasut 
+armhf	imx		dh_imx6		u-boot-with-spl.imx
+
 # Robert Nelson 
 armhf	imx		mx53loco	u-boot.imx
 
diff --git a/debian/u-boot-imx.lintian-overrides b/debian/u-boot-imx.lintian-overrides
index d1e94b0981..bb2d0ad8dc 100644
--- a/debian/u-boot-imx.lintian-overrides
+++ b/debian/u-boot-imx.lintian-overrides
@@ -4,6 +4,7 @@
 # targets could be built on multiple architectures, but could instead install
 # the package for the architecture needed.
 u-boot-imx [armhf]: arch-dependent-file-not-in-arch-specific-directory usr/lib/u-boot/mx53loco/uboot.elf
+u-boot-imx [armhf]: arch-dependent-file-not-in-arch-specific-directory usr/lib/u-boot/dh_imx6/uboot.elf
 u-boot-imx [armhf]: arch-dependent-file-not-in-arch-specific-directory usr/lib/u-boot/mx6cuboxi/uboot.elf
 u-boot-imx [armhf]: arch-dependent-file-not-in-arch-specific-directory usr/lib/u-boot/mx6cuboxi4x4/uboot.elf
 u-boot-imx [armhf]: arch-dependent-file-not-in-arch-specific-directory usr/lib/u-boot/nitrogen6q/uboot.elf
@@ -14,6 +15,7 @@ u-boot-imx [armhf]: arch-dependent-file-not-in-arch-specific-directory usr/lib/u
 
 # These bootloaders need to be statically linked.
 u-boot-imx [armhf]: statically-linked-binary usr/lib/u-boot/mx53loco/uboot.elf
+u-boot-imx [armhf]: statically-linked-binary usr/lib/u-boot/dh_imx6/uboot.elf
 u-boot-imx [armhf]: statically-linked-binary usr/lib/u-boot/mx6cuboxi/uboot.elf
 u-boot-imx [armhf]: statically-linked-binary usr/lib/u-boot/mx6cuboxi4x4/uboot.elf
 u-boot-imx [armhf]: statically-linked-binary usr/lib/u-boot/nitrogen6q/uboot.elf
-- 
2.11.0

Bug#681726: Time to remove eclipse from Testing?

[Jeremy Bicha]

On Fri, Oct 20, 2017 at 5:52 PM, Jeremy Bicha  wrote:
> On Fri, Oct 20, 2017 at 12:47 PM, Markus Koschany  wrote:
>> Am 20.10.2017 um 18:43 schrieb Jeremy Bicha:
>>> Are there any objections to me requesting that the ftpmasters remove
>>> swt-gtk and eclipse from Debian Testing so that we can complete the
>>> webkitgtk removal from Testing?
>>>
>>> Thanks,
>>> Jeremy Bicha
>>
>> Thank you for contacting us. I completely agree with you. Eclipse in its
>> current state should not be a blocker for other packages in testing. I
>> can't promise anything but I will try to get the package in shape again
>> but this process will be quite slow probably, so the request for help is
>> as valid as ever.
>
> Never mind. I tried doing the dak queries and I eventually got more
> than 500 reverse-depends before I gave up. (Attached)
>
> The only other reverse-depends of libswt-webkit-gtk-3-jni in Testing
> now is tuxguitar which was already switched in Unstable to swt4-gtk
> which should work with webkit2gtk.

Have you considered dropping the libswt-webkit-gtk-3-jni dependency
from eclipse-rcp? Then the swt-gtk source package could stop building
libswt-webkit-gtk-3-jni and we could complete the webkitgtk removal
from Debian Testing.

Thanks,
Jeremy Bicha

Bug#881287: python-daiquiri: Add python2 support

[Corey Bryant]

On Thu, Nov 9, 2017 at 3:24 PM, Chris Lamb  wrote:

> Hi Corey,
>
>
Hi Chris,


> > In Ubuntu, the attached patch was applied to achieve the following:
>
> Thanks for the patch. However, is Python 2 support explicitly required by
> a user or reverse-dependency?
>
>
Good point. I think we just need to get moving on our end. We currently
only ship py2 for core openstack packages because upstream hasn't
completely moved to py3. Anyway I think we can start moving some of them
over to py3 only and gnocchi is one of them (it needs daiquiri). So feel
free to nack this bug and I'll fix up our gnocchi package to be py3 only.

Thanks,
Corey

I would like to avoid introducing further Python 2 packages into the
> world - just another we will have to remove later...
>
>
> Best wishes,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
>

Bug#881287: python-daiquiri: Add python2 support

[Chris Lamb]

Hi Corey,

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

Thanks for the patch. However, is Python 2 support explicitly required by
a user or reverse-dependency?

I would like to avoid introducing further Python 2 packages into the
world - just another we will have to remove later...


Best wishes,

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

Bug#880669: irony-mode: FTBFS on arm64: timeout in irony-iotask-schedule/task-update/invalid-msg

[Nicholas D Steeves]

Control: severity -1 important

Downgrading severity by one level for this bug, because no tests were
run with previous versions (eg: failing tests are an improvement over
no tests), and because tests to not always fail:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/irony-mode.html


signature.asc
Description: PGP signature

Bug#879800: welcometoamazon KEMA

[Mary Ann Hansen]

Unsubscribe now.

Mary Ann Hansen
Sent from my iPhone

> On Nov 9, 2017, at 12:36 PM, Amazon Notification  
> wrote:
> 
> Notice for mary
> 
> 
>  
> 
> You may unsubscribe at any time. Unsubscribe Here NOW 23638 W. Lyons Avenue 
> #468 – Newhall, CA 91321 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> This means that you claim that the problem has been dealt with. If this is 
> not the case it is now your responsibility to reopen the Bug report if 
> necessary, and/or fix the problem forthwith. (NB: If you are a system 
> administrator and have no idea what this message is talking about, this may 
> indicate a serious mail system misconfiguration somewhere. Please contact 
> ow...@bugs.debian.org immediately.) --=20 879800: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D879800 Debian Bug 
> Tracking System Contact ow...@bugs.debian.org with problems
> 
> 

Bug#880900: irony-server: fails to upgrade from 'testing' - trying to overwrite /usr/bin/irony-server

[Nicholas D Steeves]

Reopening because I intend to close this bug with an upload to
unstable, and not to experimental.



signature.asc
Description: PGP signature

Bug#879800: welcometoamazon pXgS

[Loretta Vondal]

I never did this with u guys u have the wrong person

On Nov 9, 2017 1:43 PM, "Amazon Notification"  wrote:

Notice for loretta


You may unsubscribe at any time. Unsubscribe Here NOW 23638 W. Lyons Avenue
#468 – Newhall, CA 91321




























































































































This means that you claim that the problem has been dealt with. If this is
not the case it is now your responsibility to reopen the Bug report if
necessary, and/or fix the problem forthwith. (NB: If you are a system
administrator and have no idea what this message is talking about, this may
indicate a serious mail system misconfiguration somewhere. Please contact
ow...@bugs.debian.org immediately.) -- 879800: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=879800 Debian Bug Tracking System Contact
ow...@bugs.debian.org with problems

-- Forwarded message --
From: Rainer Dorsch 
To: Debian Bug Tracking System 
Cc:
Bcc:
Date: Thu, 26 Oct 2017 08:37:39 +0200
Subject: ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)
Package: ffmpeg
Version: 7:3.3.4-2+b1
Severity: normal

Dear Maintainer,

I tried to build ffmpeg 3.4 from source using

dpkg-buildpackage -us -uc

but a test failed in the build process

TESTseek-lavf-flv_fmt
/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/tests/fate-run.sh
fate-seek-lavf-flv_fmt "" ""
"/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard"
'run libavformat/tests/seek /mnt/tmp/rd/debian/ffmpeg/
ffmpeg-3.4/debian/standard/tests/data/lavf/lavf.flv' ''
'/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/tests/ref/seek/lavf-flv_fmt' '' '1'
'' '' '' '' '' '' '' '' ''
 /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/libavformat/tests/seek
/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/
tests/data/lavf/lavf.flv
 TESTapi-seek
 /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/tests/fate-run.sh fate-api-seek "" ""
"/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard" 'run
tests/api/api-seek-test /mnt/tmp/rd/debian/ffmpeg/
ffmpeg-3.4/debian/standard/tests/data/lavf/lavf.flv 0 720' 'null' '' '' '1'
'' '' '' '' '' '' '' '' ''
  /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/api/api-seek-test
/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/data/lavf/lavf.flv
0 720
   /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/ffmpeg -nostdin
-nostats -cpuflags all -threads 1 -idct simple -flags +bitexact -sws_flags
+accurate_rnd+bitexact -fflags +bitexact -hwaccel none -threads 1
-thread_type frame+slice -i /mnt/tmp/rd/debian/ffmpeg/
ffmpeg-3.4/debian/standard/tests/data/fate/vsynth2-zlib.avi -threads 1
-idct simple -dct fastint -s 352x288 -pix_fmt yuv420p -vsync 0 -flags
+bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -f rawvideo
-y /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/
tests/data/fate/vsynth2-zlib.out.rawvideo
   make: Target 'check' not remade because of errors.
   make: Leaving directory '/mnt/tmp/rd/debian/ffmpeg/
ffmpeg-3.4/debian/standard'
   dh_auto_test: cd debian/standard && make -j2 check -k returned exit code
2


If there are more outputs I can provide, please let me know.

thanks
Rainer

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (70, 'experimental')
Architecture: armhf (armv7l)

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

Versions of packages ffmpeg depends on:
ii  libavcodec577:3.3.4-2+b1
ii  libavdevice57   7:3.3.4-2+b1
ii  libavfilter67:3.3.4-2+b1
ii  libavformat57   7:3.3.4-2+b1
ii  libavresample3  7:3.3.4-2+b1
ii  libavutil55 7:3.3.4-2+b1
ii  libc6   2.24-17
ii  libpostproc54   7:3.3.4-2+b1
ii  libsdl2-2.0-0   2.0.6+dfsg1-4
ii  libswresample2  7:3.3.4-2+b1
ii  libswscale4 7:3.3.4-2+b1

ffmpeg recommends no packages.

Versions of packages ffmpeg suggests:
pn  ffmpeg-doc  

-- no debconf information



-- Forwarded message --
From: James Cowgill 
To: 879800-cl...@bugs.debian.org
Cc:
Bcc:
Date: Thu, 09 Nov 2017 17:35:07 +
Subject: Bug#879800: fixed in ffmpeg 7:3.4-2
Source: ffmpeg
Source-Version: 7:3.4-2

We believe that the bug you reported is fixed in the latest version of
ffmpeg, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 879...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated ffmpeg package)

(This me

Bug#881297: RFP: apache-karaf -- A small OSGi based application server provisioned from maven, and with an integrated SSH server.

[Steinar Bang]

Package: wnpp
Severity: wishlist

* Package name: apache-karaf
  Version : 4.1.3
  Upstream Author : d...@karaf.apache.org
* URL : http://karaf.apache.org/download.html
* License : Apache License v2
  Programming Lang: Java
  Description : A small OSGi based application server provisioned from 
maven, and with an integrated SSH server.

Karaf is a small and fast application server for OSGi based
application.

Karaf is provisioned using maven, so it is possible to start with a
clean karaf installation, log in using SSH to karaf's integrated SSH
server and from its command line, run commands that will pull in an
application and its dependencies.

Karaf is also convenient for development: karaf can be set up to
listen for new builds of SNAPSHOT versions in the local repository.
So this means that all you need to do to make karaf pick up new
versions of the code is run
 mvn install
in the module(s) you want karaf to pick up.

Together with remote debugging from eclipse this makes for easy
development and quick turnaround to try out code changes in the
appserver.

Karaf relies on OPS4J ("the pax stuff", e.g. pax-web, pax-jdbc) to
provide the infrastructure that makes up an application server.

Karaf introduces a concept called "features" that makes it resolve the
runtime dependencies of OSGi applications (runtime dependency
resolution have been the achilles heel of OSGi applications).  Karaf
also has a maven plugin that makes it possible to piggy back the
creation of karaf features when creating OSGi bundles.

Bug#879139: Bumping severity to serious for swt-gtk reverse depends

[Jeremy Bicha]

severity -1 serious

Because this is in a way blocking the removal of the unmaintained
webkitgtk from Debian Testing, I am bumping the severity.

See https://bugs.debian.org/880470

Thanks,
Jeremy Bicha

Bug#879800: welcometoamazon mO

[mheslen97233]

Don't have account  wrong email

On Nov 9, 2017 11:43 AM, "Amazon Notification" 
wrote:

> Notice for mike
>
> 
>
> You may unsubscribe at any time. Unsubscribe Here NOW 23638 W. Lyons
> Avenue #468 – Newhall, CA 91321
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> This means that you claim that the problem has been dealt with. If this is
> not the case it is now your responsibility to reopen the Bug report if
> necessary, and/or fix the problem forthwith. (NB: If you are a system
> administrator and have no idea what this message is talking about, this may
> indicate a serious mail system misconfiguration somewhere. Please contact
> ow...@bugs.debian.org immediately.) -- 879800:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879800 Debian Bug
> Tracking System Contact ow...@bugs.debian.org with problems
>
> -- Forwarded message --
> From: Rainer Dorsch 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Thu, 26 Oct 2017 08:37:39 +0200
> Subject: ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)
> Package: ffmpeg
> Version: 7:3.3.4-2+b1
> Severity: normal
>
> Dear Maintainer,
>
> I tried to build ffmpeg 3.4 from source using
>
> dpkg-buildpackage -us -uc
>
> but a test failed in the build process
>
> TESTseek-lavf-flv_fmt
> /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/tests/fate-run.sh
> fate-seek-lavf-flv_fmt "" "" 
> "/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard"
> 'run libavformat/tests/seek /mnt/tmp/rd/debian/ffmpeg/
> ffmpeg-3.4/debian/standard/tests/data/lavf/lavf.flv' ''
> '/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/tests/ref/seek/lavf-flv_fmt' '' '1'
> '' '' '' '' '' '' '' '' ''
>  /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/libavformat/tests/seek
> /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/
> tests/data/lavf/lavf.flv
>  TESTapi-seek
>  /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/tests/fate-run.sh fate-api-seek ""
> "" "/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard" 'run
> tests/api/api-seek-test /mnt/tmp/rd/debian/ffmpeg/
> ffmpeg-3.4/debian/standard/tests/data/lavf/lavf.flv 0 720' 'null' '' ''
> '1' '' '' '' '' '' '' '' '' ''
>   /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/api/api-seek-test
> /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/data/lavf/lavf.flv
> 0 720
>/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/ffmpeg -nostdin
> -nostats -cpuflags all -threads 1 -idct simple -flags +bitexact -sws_flags
> +accurate_rnd+bitexact -fflags +bitexact -hwaccel none -threads 1
> -thread_type frame+slice -i /mnt/tmp/rd/debian/ffmpeg/
> ffmpeg-3.4/debian/standard/tests/data/fate/vsynth2-zlib.avi -threads 1
> -idct simple -dct fastint -s 352x288 -pix_fmt yuv420p -vsync 0 -flags
> +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -f rawvideo
> -y /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/
> tests/data/fate/vsynth2-zlib.out.rawvideo
>make: Target 'check' not remade because of errors.
>make: Leaving directory '/mnt/tmp/rd/debian/ffmpeg/
> ffmpeg-3.4/debian/standard'
>dh_auto_test: cd debian/standard && make -j2 check -k returned exit
> code 2
>
>
> If there are more outputs I can provide, please let me know.
>
> thanks
> Rainer
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (70, 'experimental')
> Architecture: armhf (armv7l)
>
> Kernel: Linux 4.13.0-1-armmp (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages ffmpeg depends on:
> ii  libavcodec577:3.3.4-2+b1
> ii  libavdevice57   7:3.3.4-2+b1
> ii  libavfilter67:3.3.4-2+b1
> ii  libavformat57   7:3.3.4-2+b1
> ii  libavresample3  7:3.3.4-2+b1
> ii  libavutil55 7:3.3.4-2+b1
> ii  libc6   2.24-17
> ii  libpostproc54   7:3.3.4-2+b1
> ii  libsdl2-2.0-0   2.0.6+dfsg1-4
> ii  libswresample2  7:3.3.4-2+b1
> ii  libswscale4 7:3.3.4-2+b1
>
> ffmpeg recommends no packages.
>
> Versions of packages ffmpeg suggests:
> pn  ffmpeg-doc  
>
> -- no debconf information
>
>
>
> -- Forwarded message --
> From: James Cowgill 
> To: 879800-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Thu, 09 Nov 2017 17:35:07 +
> Subject: Bug#879800: fixed in ffmpeg 7:3.4-2
> Source: ffmpeg
> Source-Version: 7:3.4-2
>
> We believe that the bug you reported is fixed in the latest version of
> ffmpeg, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previ

Bug#879800: welcometoamazon OB

[Stephen Hall]

No, bye

On Thu, 9 Nov 2017 at 19:43, Amazon Notification 
wrote:

> Notice for theposhgoose
>
> 
>
> You may unsubscribe at any time. Unsubscribe Here NOW 23638 W. Lyons
> Avenue #468 – Newhall, CA 91321
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> This means that you claim that the problem has been dealt with. If this is
> not the case it is now your responsibility to reopen the Bug report if
> necessary, and/or fix the problem forthwith. (NB: If you are a system
> administrator and have no idea what this message is talking about, this may
> indicate a serious mail system misconfiguration somewhere. Please contact
> ow...@bugs.debian.org immediately.) -- 879800:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879800 Debian Bug
> Tracking System Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Rainer Dorsch 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Thu, 26 Oct 2017 08:37:39 +0200
> Subject: ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)
> Package: ffmpeg
> Version: 7:3.3.4-2+b1
> Severity: normal
>
> Dear Maintainer,
>
> I tried to build ffmpeg 3.4 from source using
>
> dpkg-buildpackage -us -uc
>
> but a test failed in the build process
>
> TESTseek-lavf-flv_fmt
> /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/tests/fate-run.sh
> fate-seek-lavf-flv_fmt "" ""
> "/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard" 'run
> libavformat/tests/seek
> /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/data/lavf/lavf.flv'
> '' '/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/tests/ref/seek/lavf-flv_fmt' ''
> '1' '' '' '' '' '' '' '' '' ''
>  /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/libavformat/tests/seek
> /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/data/lavf/lavf.flv
>  TESTapi-seek
>  /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/tests/fate-run.sh fate-api-seek ""
> "" "/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard" 'run
> tests/api/api-seek-test
> /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/data/lavf/lavf.flv
> 0 720' 'null' '' '' '1' '' '' '' '' '' '' '' '' ''
>
> /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/api/api-seek-test
> /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/data/lavf/lavf.flv
> 0 720
>/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/ffmpeg -nostdin
> -nostats -cpuflags all -threads 1 -idct simple -flags +bitexact -sws_flags
> +accurate_rnd+bitexact -fflags +bitexact -hwaccel none -threads 1
> -thread_type frame+slice -i
> /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/data/fate/vsynth2-zlib.avi
> -threads 1 -idct simple -dct fastint -s 352x288 -pix_fmt yuv420p -vsync 0
> -flags +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -f
> rawvideo -y
> /mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard/tests/data/fate/vsynth2-zlib.out.rawvideo
>make: Target 'check' not remade because of errors.
>make: Leaving directory
> '/mnt/tmp/rd/debian/ffmpeg/ffmpeg-3.4/debian/standard'
>dh_auto_test: cd debian/standard && make -j2 check -k returned exit
> code 2
>
>
> If there are more outputs I can provide, please let me know.
>
> thanks
> Rainer
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (70, 'experimental')
> Architecture: armhf (armv7l)
>
> Kernel: Linux 4.13.0-1-armmp (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages ffmpeg depends on:
> ii  libavcodec577:3.3.4-2+b1
> ii  libavdevice57   7:3.3.4-2+b1
> ii  libavfilter67:3.3.4-2+b1
> ii  libavformat57   7:3.3.4-2+b1
> ii  libavresample3  7:3.3.4-2+b1
> ii  libavutil55 7:3.3.4-2+b1
> ii  libc6   2.24-17
> ii  libpostproc54   7:3.3.4-2+b1
> ii  libsdl2-2.0-0   2.0.6+dfsg1-4
> ii  libswresample2  7:3.3.4-2+b1
> ii  libswscale4 7:3.3.4-2+b1
>
> ffmpeg recommends no packages.
>
> Versions of packages ffmpeg suggests:
> pn  ffmpeg-doc  
>
> -- no debconf information
>
>
>
>
> -- Forwarded message --
> From: James Cowgill 
> To: 879800-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Thu, 09 Nov 2017 17:35:07 +
> Subject: Bug#879800: fixed in ffmpeg 7:3.4-2
> Source: ffmpeg
> Source-Version: 7:3.4-2
>
> We believe that the bug you reported is fixed in the latest version of
> ffmpeg, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> atta

Bug#881190: deb-systemd-invoke syntax error in postinst script

[Bastian Blank]

Control: reassign -1 debhelper/10.10.5

Hi Ben

On Wed, Nov 08, 2017 at 05:55:40PM +, Ben Hutchings wrote:
> # Automatically added by dh_installsystemd/10.10.5
> if [ -d /run/systemd/system ]; then
> systemctl --system daemon-reload >/dev/null || true
> if [ -n "$2" ]; then
> _dh_action=try-restart
> else
> _dh_action=start
> fi
> deb-systemd-invoke $_dh_action  >/dev/null || true
> fi
> # End automatically added section

> I don't know if the bug is in debhelper or in a file in the lvm2
> source.

It's a bug in debhelper.  If dh_installsystemd gets zero units to start,
it will create this empty list.

Bastian

-- 
There's another way to survive.  Mutual trust -- and help.
-- Kirk, "Day of the Dove", stardate unknown

Bug#880669: irony-mode: FTBFS on mips64el and arm64: FAILED 22/41 irony-iotask-schedule/task-update/invalid-msg

[Nicholas D Steeves]

I've uploaded irony-mode_1.2.0-2~exp1_amd64.  I'm giving LLVM+Clang a
try with the new package, as I've read that MacOS users must use Clang
rather than GCC...and I suspect that switching to LLVM+Clang might
close this bug (hypothesis: error on mips64 and arm64 only exists when
building with GCC).  Also, I suspect that upstream intends
irony-server to be compiled with clang ;-)

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#881290: qemu-kvm: Passthrough of SAS2008-based HBA card fails on E3-1225v3 due to failed DMA mapping (-14)

[Michael Tokarev]

Control: severity -1 minor

09.11.2017 21:10, Johannes Falke wrote:
> Package: qemu-kvm
> Version: 1:2.8+dfsg-6+deb9u3
> Severity: important
> 
> Dear Maintainer,
> 
> there is a bug preventing many people with my combination of hardware
> from using PCI passthrough. I am not actually sure whether the bug is
> in kernel/kvm, vfio or qemu, however, as qemu is the highest-level of
> these, I am reporting the bug here as you will likely know better where
> the origin of the bug may be found.

Just for you to understand. This bug is _very_ unlikely will be addressed
here, most likely it'll sit in the bugtracker forever.

The reason is simple: one has to have your hardware to replicate this issue,
AND one has to be knowlegeable in the area of device pass-through.

You can _try_ to ask upstream about this, maybe this will work better -
because at least one of the requiriments will be met in this case. Maybe
you'll have the ability to communicate this matter and will be able to
provide enough info or debugging for it to be fixed.  I definitely wont
be a broken phone between you and upstream.

At any rate, I don't think the severity of this bug is important.
Qemu works for very large number of users, just very specific use case
fails.  Marking as minor.

I'm not trying to be rude or something, I'm just describing the situation.

Thanks,

/mjt

Bug#881296: ITP: belcard -- VCard standard format manipulation library

[Dr. Tobias Quathamer]

Package: wnpp
Severity: wishlist
Owner: "Dr. Tobias Quathamer" 

* Package name: belcard
  Version : 1.0.2
  Upstream Author : Simon Morlat 
* URL : https://www.linphone.org/
* License : GPL-3+
  Programming Lang: C++
  Description : VCard standard format manipulation library

 Belcard is a C++ library to manipulate VCard standard format.
 .
 The package is probably not useful outside the Belledonne
 Communications suite of libraries and programs.


This package is needed as a dependency of the new
linphone upstream version.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#881162: tomcat7: Server reports 404 on any request, even /

[Russell Jackson]

On 11/09/2017 05:47 AM, Markus Koschany wrote:
> updated packages for testing are available at:
> 
> https://people.debian.org/~roberto/
> 
> Any feedback is appreciated. 

I can confirm that the u17 revision packages resolve the 404 issue
for us. I haven't tested it beyond seeing if the context loads and
serves up the initial page.

Many thanks.

-- 
Russell A Jackson
Information Security and Emerging Technologies
California State University, San Bernardino

Bug#881295: RFS: rednotebook/2.3-1 [ITP] [ITA] -- A cross-platform journal

[Phil Wyett]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the package "rednotebook"

* Package name: rednotebook
  Version : 2.3-1
  Upstream Author : Jendrik Seipp 
* URL : http://rednotebook.sourceforge.net/
* License : GPL-2+

It builds those binary packages:

rednotebook - Modern desktop diary and personal journaling tool. It lets you

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

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

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

dget -x https://mentors.debian.net/debian/pool/main/r/rednotebook/rednotebook_2.
3-1.dsc

Changes since the last upload:

rednotebook (2.3-1) unstable; urgency=medium

  [ Jendrik Seipp ]
  * New upstream release
  * Compress backups.
  * Use newer txt2tags version 2.6 and reapply changes to obtain a GPL-2+
version.
  * Remove brittle PDF export. Please export to HTML and print to PDF with
browser instead.
  * Remove intro page from export wizard.
  * Fix: image files were not found on Windows and Mac OS.
  * Print peak memory usage on Linux when program exits.
  * Hide tags panel completely by default instead of only minimizing it.
  
  [Phil Wyett]
  * Update Debian files.
  * ITP: Submission of RedNotebook version 2.x. (Closes: #875264)

 -- Phil Wyett   Wed, 08 Nov 2017 17:04:48 +

Debian packaging repo:

https://gitlab.com/kathenas_external/debian/rednotebook

Regards

Phil

-- 
*** If this is a mailing list, I am subscribed, no need to CC me.***

Playing the game for the games sake.

Web: https://kathenas.org

GitLab: https://gitlab.com/kathenas

Twitter: kathenasorg

Instagram: kathenasorg

GPG: 1B97 6556 913F 73F3 9C9B 25C4 2961 D9B6 2017 A57A

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

Bug#881294: guile-2.0 FTBFS for ia64

[Jason Duerstock]

Package: guile-2.0
Version: 2.0.13+1-4
Severity: normal

Dear Maintainer,

guile-2.0 contains a long-standing bug on the ia64 platform.  The structure 
used for the setjmp()/longjmp()
implementation is not properly initialized when a thread is created.  More 
detail is available here:

https://lists.gnu.org/archive/html/bug-guile/2017-11/msg0.html

I have included a patch against 2.0.13.

Thank you for your time and your work.

Jason


-- System Information:
Debian Release: 7.11
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: ia64

Kernel: Linux 3.2.0-4-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages guile-2.0 depends on:
ii  guile-2.0-libs  2.0.13+1-4

guile-2.0 recommends no packages.

Versions of packages guile-2.0 suggests:
pn  guile-2.0-doc  

-- debconf information excluded
diff --git a/libguile/threads.c b/libguile/threads.c
index dcbd24d..0f688c3 100644
--- a/libguile/threads.c
+++ b/libguile/threads.c
@@ -552,6 +552,7 @@ guilify_self_1 (struct GC_stack_base *base)
   t.base = base->mem_base;
 #ifdef __ia64__
   t.register_backing_store_base = base->reg_base;
+  t.pending_rbs_continuation = 0;
 #endif
   t.continuation_root = SCM_EOL;
   t.continuation_base = t.base;

Bug#881293: libvirt-daemon: libvirtd sefgfault when disconnect and reconnect iso

[Jeff Ketchum]

Package: libvirt-daemon
Version: 3.9.0-1
Severity: important


[  271.168779] libvirtd[1177]: segfault at 10 ip 7f2cae6d9208 sp 
7f2cb80049a0 error 4 in libvirt_driver_qemu.so[7f2cae64d000+173000]

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

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

Versions of packages libvirt-daemon depends on:
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.11.1-3
ii  libaudit1   1:2.8.1-2
ii  libavahi-client30.7-3
ii  libavahi-common30.7-3
ii  libblkid1   2.30.2-0.1
ii  libc6   2.24-17
ii  libcap-ng0  0.7.7-3.1+b1
ii  libcurl3-gnutls 7.56.1-1
ii  libdbus-1-3 1.12.0-1
ii  libdevmapper1.02.1  2:1.02.145-1
ii  libfuse22.9.7-1
ii  libgnutls30 3.5.16-1
ii  libnetcf1   1:0.2.8-1+b2
ii  libnl-3-200 3.2.27-2
ii  libnl-route-3-200   3.2.27-2
ii  libnuma12.0.11-2.1
ii  libparted2  3.2-18
ii  libpcap0.8  1.8.1-5
ii  libpciaccess0   0.13.4-1+b2
ii  libsasl2-2  2.1.27~101-g0780600+dfsg-3
ii  libselinux1 2.7-2
ii  libssh2-1   1.8.0-1
ii  libudev1235-2
ii  libvirt03.9.0-1
ii  libxen-4.8  4.8.1-1+deb9u3
ii  libxenstore3.0  4.8.1-1+deb9u3
ii  libxml2 2.9.4+dfsg1-5+b1
ii  libyajl22.1.0-2+b3

Versions of packages libvirt-daemon recommends:
ii  libxml2-utils   2.9.4+dfsg1-5+b1
ii  netcat-openbsd  1.178-3
ii  qemu1:2.10.0+dfsg-2
ii  qemu-kvm1:2.10.0+dfsg-2

Versions of packages libvirt-daemon suggests:
pn  libvirt-daemon-driver-storage-gluster   
pn  libvirt-daemon-driver-storage-rbd   
pn  libvirt-daemon-driver-storage-sheepdog  
pn  libvirt-daemon-driver-storage-zfs   
ii  libvirt-daemon-system   3.9.0-1
pn  numad   

-- no debconf information

Bug#881292: node-asn1.js FTBFS: Error: Cannot find module 'asn1.js'

[Adrian Bunk]

Source: node-asn1.js
Version: 5.0.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=node-asn1.js&arch=all&ver=5.0.0-1&stamp=1510247742&raw=0

...

cd rfc/2560/ && mocha --reporter spec test/*-test.js
module.js:471
throw err;
^

Error: Cannot find module 'asn1.js'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/<>/rfc/2560/index.js:3:14)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/<>/rfc/2560/test/basic-test.js:5:17)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at /usr/lib/nodejs/mocha/lib/mocha.js:172:27
at Array.forEach (native)
at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14)
at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31)
at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:383:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:496:3
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#881291: libdbd-sqlite3-perl FTBFS with libsqlite3-dev 3.21.0-1

[Adrian Bunk]

Source: libdbd-sqlite3-perl
Version: 1.54-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libdbd-sqlite3-perl.html

...
Test Summary Report
---
t/virtual_table/rt_99748.t  (Wstat: 512 Tests: 24 
Failed: 1)
  Failed test:  24
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 52 tests but ran 24.
Files=105, Tests=3555, 22 wallclock secs ( 0.81 usr  0.26 sys + 12.46 cusr  
1.88 csys = 15.41 CPU)
Result: FAIL
Failed 1/105 test programs. 1/3555 subtests failed.
Makefile:1078: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 2

Bug#881290: qemu-kvm: Passthrough of SAS2008-based HBA card fails on E3-1225v3 due to failed DMA mapping (-14)

[Johannes Falke]

Package: qemu-kvm
Version: 1:2.8+dfsg-6+deb9u3
Severity: important

Dear Maintainer,

there is a bug preventing many people with my combination of hardware
from using PCI passthrough. I am not actually sure whether the bug is
in kernel/kvm, vfio or qemu, however, as qemu is the highest-level of
these, I am reporting the bug here as you will likely know better where
the origin of the bug may be found.

When attempting to pass through this device to a KVM using VFIO, this
results in error -14 (Bad Address):

# qemu-system-x86_64 -enable-kvm -m 10G -net none -monitor stdio -serial
# none -parallel none -vnc :1 -device vfio-pci,host=1:00.0 -S
QEMU 2.9.1 monitor - type 'help' for more information
(qemu) c
(qemu) qemu-system-x86_64: VFIO_MAP_DMA: -14
qemu-system-x86_64: vfio_dma_map(0x7f548f0a1fc0, 0xfebd, 0x2000,
0x7f54a909d000) = -14 (Bad address)
qemu: hardware error: vfio: DMA mapping failed, unable to continue

See also:
https://bugzilla.proxmox.com/show_bug.cgi?id=1556
https://www.redhat.com/archives/vfio-users/2016-May/msg00088.html

This has occurred on Proxmox (Proxmox and Debian packages, Ubuntu kernel), 
Ubuntu,
and pure Debian packages and kernel on Proxmox. However, this error
reportedly does NOT occur for:

- different distributions (Fedora 24, 25)
- different HBA cards (SAS2308, SAS3008)
- different CPU (E3-1220v5)

As such, it seems that this error is either introduced in
Debian or an existing bug that is fixed in RHEL-based systems.

Best regards,
Johannes Falke

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

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

Versions of packages qemu-kvm depends on:
ii  qemu-system-x86  1:2.8+dfsg-6+deb9u3

qemu-kvm recommends no packages.

qemu-kvm suggests no packages.

-- no debconf information

Bug#770872: smartmontools: smartd sends FailedOpenDevice warnings even for devices marked as removable

[Christian Franke]

Fixed upstream since r4399.
https://www.smartmontools.org/changeset/4399

Fix is included in new smartmontools-6.6 release.

Bug#859224: netkit-ftp-ssl: Please migrate to openssl1.1 in Buster

[Mats Erik Andersson]

Let me begin by stating for a fact that the present
source package 'netkit-ftp-ssl' does in fact build
correctly with libssl1.1, as soon as the Build-Depends
stanza is modified to allow libssl in version 1.1.

However, and this is the core of the present issue,
an executable linked to libssl1.1 is so seriously
impaired in functionality as to be useless for all
but the most basic encrypted exchanges. It is my firm
belief that libssl1.1 is buggy in the following respect,
a phenomenon that does not exist in libssl1.0.

A central mechanism for large scale package transmission
in an SSL-protected FTP protocol exchange is the notion
of "reused session identity", meaning that the crypto
engine keeps a track record of related packages during
the full extent of a compound session, in practice during
the often extended time required to send a file larger
than a few kilobytes. Netkit-ftl-ssl achieves this by
use of the function SSL_copy_seesion_id(). This presumably
is a legacy function from the time of SSLeay.

Unfortunately the libssl code base does not include or publish
any documentation on SSL_copy_session_id(), but still offers
the declaration in the header file.

With the advent of libssl1.1 the behaviour of SSL_copy_session_id()
has changed without any mention in the published changelog as far
as I have been able to determine. In effect, SSL_copy_session_id()
is able to arrange reuse of the session identity exactly once --
I repeat to make the point -- exactly ONCE, where libssl1.0 is
able to continually renew the identity for the entire session.
Thus libssl1.1 prevents transmission of files in excess of 3 kB!

The best setup to observe this new behaviour is to use Proftpd
at the server end. It offers a setting to handle misconfigured
or crippled FTP clients:

 # etc/proftpd.conf

 TLSOptions NoSessionReuseRequired

Without this option, a client using netkit-ftp-ssl with libssl1.1
sees a cancelled connection at the time the third package is sent
in a single session, whereas libssl1.0 continues to go on shipping
however many packages remain to cover the requested file's entire
contents.

Due to this changed behaviour I claim that libssl1.1 is buggy,
leading to a crippled client with substantial loss in encrypting
abilities. Regrettably I am not able by myself to resolve this
unfortunate phenomenon with libssl, so I must defer the matter
to the custodians of libssl library proper.

M E Andersson, maintainer of netkit-ftp-ssl

Bug#881289: guessit FTBFS: NoMatches: No guessit.transformer extensions found

[Adrian Bunk]

Source: guessit
Version: 0.11.0-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes guessit FTBFS:

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

...
==
ERROR: Failure: NoMatches (No guessit.transformer extensions found)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File 
"/build/1st/guessit-0.11.0/.pybuild/pythonX.Y_2.7/build/guessit/__init__.py", 
line 99, in 
from guessit.plugins import transformers
  File 
"/build/1st/guessit-0.11.0/.pybuild/pythonX.Y_2.7/build/guessit/plugins/transformers.py",
 line 222, in 
reload()
  File 
"/build/1st/guessit-0.11.0/.pybuild/pythonX.Y_2.7/build/guessit/plugins/transformers.py",
 line 220, in reload
reload_options(all_transformers())
  File 
"/build/1st/guessit-0.11.0/.pybuild/pythonX.Y_2.7/build/guessit/plugins/transformers.py",
 line 179, in all_transformers
return _extensions.objects()
  File 
"/build/1st/guessit-0.11.0/.pybuild/pythonX.Y_2.7/build/guessit/plugins/transformers.py",
 line 111, in objects
return self.map(self._get_obj)
  File "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 252, in 
map
raise NoMatches('No %s extensions found' % self.namespace)
NoMatches: No guessit.transformer extensions found

--
Ran 1 test in 0.116s

FAILED (errors=1)
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/guessit-0.11.0/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose 
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 25

Bug#881288: gcc-7 fails to patch when old distribution detected

[Jason Duerstock]

Package: gcc-7
Version: 7.2.0-12
Severity: normal

Dear Maintainer,

When gcc-7 detects one of many outdated distributions, it attempts to apply the 
"gcc-hash-style-both" patch,
rather than "gcc-hash-style-gnu".  gcc-hash-style-both is sufficiently crufty 
that it fails to apply.

I suggest either removing the detection, or rebasing the patch.  I have 
included a patch to remove the detection.

Thank you for your time and work.

Jason

-- System Information:
Debian Release: 7.11
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: ia64

Kernel: Linux 3.2.0-4-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gcc-7 depends on:
ii  binutils  2.25-5+deb8u1
ii  cpp-7 7.2.0-12
ii  gcc-7-base7.2.0-12
ii  libc6.1   2.13-38+deb7u10
ii  libcc1-0  7.2.0-12
ii  libgcc-7-dev  7.2.0-12
ii  libgcc1   1:7.2.0-12
ii  libgmp10  2:6.1.2+dfsg-1.1
ii  libisl15  0.18-1
ii  libmpc3   1.0.3-2
ii  libmpfr4  3.1.6-1
ii  libstdc++67.2.0-12
ii  libunwind70.99-0.3
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages gcc-7 recommends:
ii  libc6.1-dev  2.13-38+deb7u10

Versions of packages gcc-7 suggests:
pn  gcc-7-doc 
pn  gcc-7-locales 
pn  libasan4-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- debconf information:
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/ at 
/usr/share/perl5/Debconf/Question.pm line 72.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/\${ <-- HERE ([^}]+)}/ at /usr/share/perl5/Debconf/Config.pm line 
30.
--- debian/rules.patch.orig	2017-11-09 12:17:23.775340303 -0500
+++ debian/rules.patch	2017-11-09 12:17:56.799340531 -0500
@@ -39,13 +39,8 @@
 	gcc-textdomain \
 	gcc-driver-extra-langs$(if $(with_linaro_branch),-linaro)
 
-ifneq (,$(filter $(distrelease),etch lenny squeeze wheezy dapper hardy intrepid jaunty karmic lucid))
-  debian_patches += gcc-hash-style-both
-else
-  debian_patches += gcc-hash-style-gnu
-endif
-
 debian_patches += \
+	gcc-hash-style-gnu \
 	libstdc++-pic \
 	libstdc++-doclink \
 	libstdc++-man-3cxx \

Bug#864927: Can we get a simple fix for #864927 into unstable/testing please?

[Steve McIntyre]

On Fri, Sep 15, 2017 at 06:15:08PM +0100, Steve McIntyre wrote:
>It's blocking KDE live builds at the moment...

*tumbleweed*

Two months later, we still have no fix for this "closed" bug anywhere
except experimental. Any chance of this being properly fixed soon?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Arguing that you don't care about the right to privacy because you have
 nothing to hide is no different than saying you don't care about free
 speech because you have nothing to say."
   -- Edward Snowden

Bug#881287: python-daiquiri: Add python2 support

[Corey Bryant]

Package: python-daiquiri
Version: 1.3.0-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear Maintainer,

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

  * d/control, d/rules, d/tests/*: Add python 2 support.


Thanks for considering the patch.


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

Kernel: Linux 4.13.0-16-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru python-daiquiri-1.3.0/debian/control 
python-daiquiri-1.3.0/debian/control
--- python-daiquiri-1.3.0/debian/control2017-09-20 03:29:15.0 
-0400
+++ python-daiquiri-1.3.0/debian/control2017-11-09 10:17:33.0 
-0500
@@ -5,6 +5,10 @@
 Build-Depends:
  debhelper (>= 10),
  dh-python,
+ python-all,
+ python-pbr,
+ python-testtools,
+ python-setuptools,
  python3-all,
  python3-pbr,
  python3-testtools,
@@ -15,6 +19,32 @@
 Vcs-Browser: https://github.com/lamby/pkg-python-daiquiri
 Homepage: https://github.com/jd/daiquiri
 
+Package: python-daiquiri
+Architecture: all
+Depends:
+ ${misc:Depends},
+ ${python:Depends},
+Description: Python library to easily setup basic logging functionality
+ The daiquiri library provides an easy way to configure logging. It also
+ provides some custom formatters and handlers.
+ .
+ Its promise is to setup a complete standard Python logging system with just
+ one function call. Nothing more, nothing less. The interesting features are:
+ .
+  * Logs to stderr by default.
+  * Use colors if logging to a terminal.
+  * Support file logging.
+  * Use program name as the name of the logging file so providing just a
+directory for logging will work.
+  * Support syslog.
+  * Support journald.
+  * JSON output support.
+  * Support of arbitrary key/value context information providing.
+  * Capture the warnings emitted by the warnings module.
+  * Native logging of any exception.
+ .
+ This is the Python 2 version of the package.
+
 Package: python3-daiquiri
 Architecture: all
 Depends:
diff -Nru python-daiquiri-1.3.0/debian/rules python-daiquiri-1.3.0/debian/rules
--- python-daiquiri-1.3.0/debian/rules  2017-09-20 03:29:15.0 -0400
+++ python-daiquiri-1.3.0/debian/rules  2017-11-09 10:17:33.0 -0500
@@ -5,7 +5,7 @@
 export PBR_VERSION = $(DEB_VERSION_UPSTREAM)
 
 %:
-   dh $@ --with python3 --buildsystem=pybuild
+   dh $@ --with python2,python3 --buildsystem=pybuild
 
 override_dh_auto_test:
# Tests require python-json-logger, which is not yet packaged for
diff -Nru python-daiquiri-1.3.0/debian/tests/0001-smoketest 
python-daiquiri-1.3.0/debian/tests/0001-smoketest
--- python-daiquiri-1.3.0/debian/tests/0001-smoketest   2017-09-20 
03:29:15.0 -0400
+++ python-daiquiri-1.3.0/debian/tests/0001-smoketest   1969-12-31 
19:00:00.0 -0500
@@ -1,11 +0,0 @@
-#!/usr/bin/env python3
-
-import daiquiri
-
-daiquiri.setup()
-
-logger = daiquiri.getLogger(__name__)
-
-logger.info("Info")
-logger.warning("Warning")
-logger.error("Error")
diff -Nru python-daiquiri-1.3.0/debian/tests/0001-smoketest-python2 
python-daiquiri-1.3.0/debian/tests/0001-smoketest-python2
--- python-daiquiri-1.3.0/debian/tests/0001-smoketest-python2   1969-12-31 
19:00:00.0 -0500
+++ python-daiquiri-1.3.0/debian/tests/0001-smoketest-python2   2017-11-09 
10:17:33.0 -0500
@@ -0,0 +1,11 @@
+#!/usr/bin/env python2
+
+import daiquiri
+
+daiquiri.setup()
+
+logger = daiquiri.getLogger(__name__)
+
+logger.info("Info")
+logger.warning("Warning")
+logger.error("Error")
diff -Nru python-daiquiri-1.3.0/debian/tests/0001-smoketest-python3 
python-daiquiri-1.3.0/debian/tests/0001-smoketest-python3
--- python-daiquiri-1.3.0/debian/tests/0001-smoketest-python3   1969-12-31 
19:00:00.0 -0500
+++ python-daiquiri-1.3.0/debian/tests/0001-smoketest-python3   2017-11-09 
10:17:33.0 -0500
@@ -0,0 +1,11 @@
+#!/usr/bin/env python3
+
+import daiquiri
+
+daiquiri.setup()
+
+logger = daiquiri.getLogger(__name__)
+
+logger.info("Info")
+logger.warning("Warning")
+logger.error("Error")
diff -Nru python-daiquiri-1.3.0/debian/tests/control 
python-daiquiri-1.3.0/debian/tests/control
--- python-daiquiri-1.3.0/debian/tests/control  2017-09-20 03:29:15.0 
-0400
+++ python-daiquiri-1.3.0/debian/tests/control  2017-11-09 10:17:33.0 
-0500
@@ -1,2 +1,2 @@
-Tests: 0001-smoketest
+Tests: 0001-smoketest-python2 0001-smoketest-python3
 Restrictions: allow-stderr

Bug#850895: bacula: Please migrate to openssl1.1 in buster

[Martin Simmons]

Hi Sebastian,

Maybe openssl_init_threads and openssl_cleanup_threads (and helper functions)
in src/lib/openssl.c should also be conditionalized to remove uses of the old
threading and locking APIs?

__Martin

Bug#857393: closed by Jochen Sprickerhof (Bug#857393: fixed in gazebo 7.8.1+dfsg-2)

[Jochen Sprickerhof]

* Andreas Beckmann  [2017-11-09 16:44]:

For consistency, the fonts-liberation dependency should rather be moved
to gazebo7-common (which contains the font symlinks)


Thanks for noticing, fixed in git.

Cheers Jochen


signature.asc
Description: PGP signature

Bug#879673: ffmpeg 3.4 API compat layer not 100% backwards compatible

[James Cowgill]

Control: clone -1 -2 -3
Control: reassign -2 gst-libav1.0 1.12.3-1
Control: notforwarded -2
Control: severity -2 important
Control: affects -2 - src:kodi src:gst-libav1.0
Control: retitle -2 gst-libav1.0: incorrect use of drain packets in 
avcodec_decode_* api
Control: reassign -3 kodi 2:17.3+dfsg1-5
Control: notforwarded -3
Control: severity -3 important
Control: affects -3 - src:kodi src:gst-libav1.0
Control: retitle -3 kodi: incorrect use of drain packets in avcodec_decode_* api

Hi,

On 07/11/17 17:50, James Cowgill wrote:
> Control: affects -1 src:kodi src:gst-libav1.0
> Control: tags -1 patch
> 
> Hi,
> 
> On 24/10/17 09:52, Sebastian Dröge wrote:
>> Package: ffmpeg
>> Version: 7:3.4-1
>> Severity: serious
>>
>> Hi,
>>
>> ffmpeg 3.4 comes with a new decoding API (among other things), and
>> provides a compatibility layer around that for the old API.
>> Unfortunately this compatibility layer is apparently not 100% backwards
>> compatible or buggy. It breaks at least h264 decoding with gst-
>> libav1.0, but then probably also breaks other packages.
>>
>> gst-libav upstream bug can be found here:
>> https://bugzilla.gnome.org/show_bug.cgi?id=789193
>>
>> We'll try to port over to the new API but it looks like some effort,
>> and even independent of that the compatibility layer should either be
>> fixed or the soname of the libraries has to be updated.
> 
> Unfortunately there doesn't seem to have been a lot of activity on the
> upstream bug report from FFmpeg themselves. Based on what I can infer
> from the source code, I think there is no API breakage here. The
> documentation on draining packets in the old API is pretty poor and it
> "worked" with ffmpeg < 3.4 so people started using it that way. However,
> I think that even under the old API, drain packets can only be sent at
> the end of a stream. This seems to make the most sense and aligns with
> new the API (where the documentation does say that this is required).
> 
> I think the best solution is to apply the attached workaround for the
> time being to the Debian package. The workaround will call
> avcodec_flush_buffers automatically when it detects that a data packet
> has been sent to avcodec_decode_* after the codec has been completely
> drained. This allows gst-libav1.0 and kodi (which I also discovered does
> this) to play video again.
> 
> I am wondering why gst-libav1.0 needs to drain the code at every
> discontinuity in the stream? I would have thought there are two separate
> cases here: seeking where you want to reset the codec, and dropped
> packets where you allow the codec itself to fix the stream (as best it can).

I've applied a slightly modified version of the patch I posted before. I
also posted it upstream, but I don't think they like it at the moment.

In any case, both gst-libav1.0 and kodi incorrectly use the
avcodec_decode_* apis by expecting them to work properly after they have
been drained. You must flush the codec after draining otherwise it won't
work (as can be seen here).

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#881284: dolphin: Copying to cifs mounted shares is limited to filenames <127 characters

[Leos Pohl]

Package: dolphin
Version: 4:16.08.3-3
Severity: important

Dear Maintainer,


   * What led up to the situation?
Mount SMB share using mount -t cifs //server/share /mnt/dir -o 
username=someone,password=secret,domain=dom,uid=1000,gid=1000
Attempt to copy with Dolphin a file with filename longer than 126 characters 
(including extension)
Dolphin responds: Could not write to 
smb://someone@dom@server/share/verylongfnameverylongfname.part

This is not related to any restrictions in Windows share as cp and Krusader can 
copy the file without issues.
The file can be copied within local filesystem and through sftp.


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

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

Versions of packages dolphin depends on:
ii  baloo-kf5  5.28.0-2
ii  kinit  5.28.0-1
ii  kio5.28.0-2
ii  libc6  2.24-11+deb9u1
ii  libdolphinvcs5 4:16.08.3-3
ii  libkf5baloo5   5.28.0-2
ii  libkf5baloowidgets516.04.0-1+b1
ii  libkf5bookmarks5   5.28.0-1
ii  libkf5codecs5  5.28.0-1+b2
ii  libkf5completion5  5.28.0-1
ii  libkf5configcore5  5.28.0-2
ii  libkf5configgui5   5.28.0-2
ii  libkf5configwidgets5   5.28.0-2
ii  libkf5coreaddons5  5.28.0-2
ii  libkf5crash5   5.28.0-1
ii  libkf5dbusaddons5  5.28.0-1
ii  libkf5filemetadata35.28.0-1+b2
ii  libkf5i18n55.28.0-2
ii  libkf5iconthemes5  5.28.0-2
ii  libkf5itemviews5   5.28.0-1
ii  libkf5jobwidgets5  5.28.0-2
ii  libkf5kcmutils55.28.0-2
ii  libkf5kiocore5 5.28.0-2
ii  libkf5kiofilewidgets5  5.28.0-2
ii  libkf5kiowidgets5  5.28.0-2
ii  libkf5newstuff55.28.0-1
ii  libkf5notifications5   5.28.0-1
ii  libkf5parts5   5.28.0-1
ii  libkf5service-bin  5.28.0-1
ii  libkf5service5 5.28.0-1
ii  libkf5solid5   5.28.0-3
ii  libkf5textwidgets5 5.28.0-1
ii  libkf5widgetsaddons5   5.28.0-3
ii  libkf5windowsystem55.28.0-2
ii  libkf5xmlgui5  5.28.0-1
ii  libphonon4qt5-44:4.9.0-4
ii  libqt5core5a   5.7.1+dfsg-3+b1
ii  libqt5dbus55.7.1+dfsg-3+b1
ii  libqt5gui5 5.7.1+dfsg-3+b1
ii  libqt5widgets5 5.7.1+dfsg-3+b1
ii  libqt5xml5 5.7.1+dfsg-3+b1
ii  libstdc++6 6.3.0-18
ii  phonon4qt5 4:4.9.0-4

Versions of packages dolphin recommends:
ii  kio-extras  4:16.08.3-1
ii  ruby1:2.3.3

Versions of packages dolphin suggests:
pn  dolphin-plugins  

-- no debconf information

Bug#830180: PowerPC without altivec causes crash

[John Paul Adrian Glaubitz]

Hi!

On 11/09/2017 05:30 PM, Ondřej Surý wrote:

this has been already fixed by upstream:

https://github.com/libjpeg-turbo/libjpeg-turbo/commit/02fa8f244e549edd3f3acf174b97157590d1b71e


Ah, nice. I didn't see that. Thanks for reporting the issue and
getting it fixed. Much appreciated!


(I gave DRC a Turris 1.x remote shell access for a proper fix...)


Oh, very interesting. Never heard of that platform. Looks like a
project from Czech Republic, isn't it? Do these routers run Debian's
PowerPCSPE port? [1]


I'll pull the fix when I run the next maintenance rounds on my packages.


Thanks!

Adrian


[1] https://project.turris.cz/en/hardware


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

Bug#793675: hplip-gui: No system tray detected

[Julian Andres Klode]

On Thu, Nov 09, 2017 at 05:16:35PM +0100, Benoît Rouits wrote:
> Package: hplip-gui
> Version: 3.17.10+repack0-1
> Followup-For: Bug #793675
> 
> Dear Maintainer,
> 
> This bug occurs also on Gnome3 (in Buster). It seems, at least
> for Gnome3, that the systray is temporarly removed after an
> upgrade, or starts too late ?

There is no system tray in GNOME, it was removed in 3.26. You
need gnome-shell-extension-top-icons-plus to get it back.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
Ubuntu Core Developer  de, en speaker

Bug#830180: PowerPC without altivec causes crash

[Ondřej Surý]

Hi,

this has been already fixed by upstream:

https://github.com/libjpeg-turbo/libjpeg-turbo/commit/02fa8f244e549edd3f3acf174b97157590d1b71e

(I gave DRC a Turris 1.x remote shell access for a proper fix...)

I'll pull the fix when I run the next maintenance rounds on my packages.

Ondrej
-- 
Ondřej Surý 

On Thu, Nov 9, 2017, at 17:15, John Paul Adrian Glaubitz wrote:
> Source: libjpeg-turbo
> Version: 1:1.5.2-2
> Followup-For: Bug #830180
> User: debian-powe...@lists.debian.org
> Usertags: powerpcspe
> 
> So, I just found this bug report because I noticed libjpeg-turbo FTBFS
> on powerpcspe because the source code apparently blindly assumes that
> all powerpc machines support AltiVec which is, of course, not the case:
> 
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I..  -I.. -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2
> -fdebug-prefix-map=/<>=.
> -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong
> -Wformat -Werror=format-security -Wall -pedantic -ffloat-store -c -o
> jsimd_powerpc.lo jsimd_powerpc.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
> -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong
> -Wformat -Werror=format-security -Wall -pedantic -ffloat-store -c
> jsimd_powerpc.c  -fPIC -DPIC -o .libs/jsimd_powerpc.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
> -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong
> -Wformat -Werror=format-security -Wall -pedantic -ffloat-store -c
> jsimd_powerpc.c -o jsimd_powerpc.o >/dev/null 2>&1
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I..  -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -maltivec -g -O2
> -fdebug-prefix-map=/<>=.
> -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong
> -Wformat -Werror=format-security -Wall -pedantic -ffloat-store -c -o
> libsimd_altivec_la-jccolor-altivec.lo `test -f 'jccolor-altivec.c' ||
> echo './'`jccolor-altivec.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wdate-time
> -D_FORTIFY_SOURCE=2 -maltivec -g -O2
> -fdebug-prefix-map=/<>=.
> -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong
> -Wformat -Werror=format-security -Wall -pedantic -ffloat-store -c
> jccolor-altivec.c  -fPIC -DPIC -o
> .libs/libsimd_altivec_la-jccolor-altivec.o
> cc1: error: AltiVec and SPE instructions cannot coexist
> Makefile:603: recipe for target 'libsimd_altivec_la-jccolor-altivec.lo'
> failed
> 
> The check from configure is bogus:
> 
> checking if we have SIMD optimisations for cpu type... yes (powerpc)
> 
> and from the configure.ac:
> 
> powerpc*)
>   AC_MSG_RESULT([yes (powerpc)])
>   simd_arch=powerpc
>   ;;
> 
> This should be done more carefully by actually asking gcc whether the
> target configuration supports Altivec. Blindly assuming it works is
> really a bad idea.
> 
> A proper check would be something like I committed to Firefox upstream
> [1].
> 
> Thanks,
> Adrian
> 
> > [1] 
> > https://github.com/mozilla/gecko-dev/commit/c6b39f0f902898988ca7793af56307640ff81362
> 
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#881283: libmad0: produces different results on s390x/arm64/...

[IOhannes m zmoelnig]

Package: libmad0
Version: 0.15.1b-8.1
Severity: important

Dear Maintainer,

TL;DR: it seems that libmad is not really usable on s390x.

i'm currently trying to find out why sonic-visualiser_3.0.3-1 fails to build
successfully on the s390x and arm64 architectures.
The problem is a failing test when decoding mp3 files.
The test runs fine on most release architectures, but fails on
- arm64
- s390x
- alpha
- hppa
- m68k
- sh4

Now while trying to hunt this down, i think i found an issue with libmad.
Using the following test-program:

#!/usr/bin/env python

import mad
mf = mad.MadFile("sine.mp3")
data = mf.read()

offset = 2048
print([_ for _ in data[offset:(offset+1024)]])


and the attached minimal MP3-file "sine.mp3" i get different results for s390x
(zelenka.debian.org) and amd64 (my laptop):

s390x = [  0,   1,   0,   1, 255, 254, 255, 254, 255, 252, 255, 252, 0, 5, ...
amd64 = [252, 255, 252, 255, 254, 255, 254, 255,   0,   0,   0,   0, 1, 0, ...

I've also ran the file through the 'minimad' example that comes with libmad
(sources), and the output differs on the two architectures (i've attached the
results as 's390x.bin' resp.  'amd64.bin').
i haven't done any checks on architectures that are supposed to be "ok"
(according to my test-suite).

Would it be possible to fix this?
If not, should the failing architectures be marked as "not-for-us"?

mgfasdr
IOhannes


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

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

Versions of packages libmad0 depends on:
ii  libc6  2.24-17

libmad0 recommends no packages.

libmad0 suggests no packages.

-- no debconf information


sine.mp3
Description: audio/mpeg


amd64.bin
Description: Binary data


s390x.bin
Description: Binary data

Bug#830180: PowerPC without altivec causes crash

[John Paul Adrian Glaubitz]

Source: libjpeg-turbo
Version: 1:1.5.2-2
Followup-For: Bug #830180
User: debian-powe...@lists.debian.org
Usertags: powerpcspe

So, I just found this bug report because I noticed libjpeg-turbo FTBFS
on powerpcspe because the source code apparently blindly assumes that
all powerpc machines support AltiVec which is, of course, not the case:

/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
-I.. -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -specs=/usr/share/dpkg/pie-compile.specs 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
-ffloat-store -c -o jsimd_powerpc.lo jsimd_powerpc.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -ffloat-store -c jsimd_powerpc.c  -fPIC 
-DPIC -o .libs/jsimd_powerpc.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -ffloat-store -c jsimd_powerpc.c -o 
jsimd_powerpc.o >/dev/null 2>&1
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
-I.. -Wdate-time -D_FORTIFY_SOURCE=2 -maltivec -g -O2 
-fdebug-prefix-map=/<>=. -specs=/usr/share/dpkg/pie-compile.specs 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
-ffloat-store -c -o libsimd_altivec_la-jccolor-altivec.lo `test -f 
'jccolor-altivec.c' || echo './'`jccolor-altivec.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -maltivec -g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -ffloat-store -c jccolor-altivec.c  
-fPIC -DPIC -o .libs/libsimd_altivec_la-jccolor-altivec.o
cc1: error: AltiVec and SPE instructions cannot coexist
Makefile:603: recipe for target 'libsimd_altivec_la-jccolor-altivec.lo' failed

The check from configure is bogus:

checking if we have SIMD optimisations for cpu type... yes (powerpc)

and from the configure.ac:

powerpc*)
  AC_MSG_RESULT([yes (powerpc)])
  simd_arch=powerpc
  ;;

This should be done more carefully by actually asking gcc whether the
target configuration supports Altivec. Blindly assuming it works is
really a bad idea.

A proper check would be something like I committed to Firefox upstream [1].

Thanks,
Adrian

> [1] 
> https://github.com/mozilla/gecko-dev/commit/c6b39f0f902898988ca7793af56307640ff81362

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

Bug#793675: hplip-gui: No system tray detected

[Benoît Rouits]

Package: hplip-gui
Version: 3.17.10+repack0-1
Followup-For: Bug #793675

Dear Maintainer,

This bug occurs also on Gnome3 (in Buster). It seems, at least
for Gnome3, that the systray is temporarly removed after an
upgrade, or starts too late ?

Indeed, other systray-aware applications also display
errors (ownCloud client, for instance).

Unfortunately i don't know which package concerns the gnome systray...

Thank you for your consideration.



-- Package-specific info:

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

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

Versions of packages hplip-gui depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.0-1
ii  dbus-x11 [dbus-session-bus]   1.12.0-1
ii  gksu  2.0.2-9+b1
ii  hplip 3.17.10+repack0-1
ii  python3-dbus.mainloop.pyqt5   5.9+dfsg-2+b1
ii  python3-pyqt5 5.9+dfsg-2+b1

Versions of packages hplip-gui recommends:
ii  python3-notify2  0.3-3
ii  simple-scan  3.23.2-1

hplip-gui suggests no packages.

-- no debconf information

Bug#878311:

[Mario.Limonciello]

This particular issue is fixed with 
https://github.com/hughsie/appstream-glib/commit/a1481d201d089f9e70a0cf48a0424315e0f6cdaf
 which is part of the recently tagged 0.7.4 release.

Bug#881282: blinker: Version 1.4 is available upstream

[Sebastien Delafond]

Source: blinker
Severity: wishlist
Control: block 849556 by -1 

Version 1.4 is available upstream, could it be packaged in sid ?
mitmproxy 2.0.x depends on >= 1.4.

Cheers,

--Seb

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

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

Bug#881281: ugly scaled icons in the toolar

[Stanislav Maslovski]

Package: wxmaxima
Version: 17.10.1-1
Severity: minor
Tags: patch

Hi,

This version of wxmaxima, as compared to 16.04.2, applies unnecessary scaling 
to the toolbar
icons. The result of this scaling is very aestetically unpleasing to the point 
of being disturbing.

If you look into the source code of ToolBar.c of ver. WxMaxima 16.04.2 you will 
find that the
scaling is only applied when running on Windows or Mac, and disabled elsewhere.
So I did the same change to ver. 17.10.1, which you will find in the attached 
patch.

I have checked that with this patch the toolbar icons look much better in all 
resolutions
available on my display, which are

   1920x1080 60.00*+
   1680x1050 59.95  
   1600x900  60.00  
   1440x900  59.89  
   1280x1024 75.0260.02  
   1280x800  59.81  
   1280x720  60.00  
   1152x864  75.00  
   1024x768  75.0370.0760.00  
   800x600   75.0072.1960.3256.25  
   640x480   75.0072.8159.94  

-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable'), (50, 'testing'), (10, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages wxmaxima depends on:
ii  ibus-gtk3 1.5.14-3
ii  libc6 2.24-11+deb9u1
ii  libgcc1   1:6.3.0-18
ii  libstdc++66.3.0-18
ii  libwxbase3.0-0v5  3.0.3.1+dfsg2-1
ii  libwxgtk3.0-0v5   3.0.3.1+dfsg2-1
ii  maxima5.38.1-8+b1

Versions of packages wxmaxima recommends:
ii  maxima-doc  5.38.1-8

Versions of packages wxmaxima suggests:
ii  fonts-jsmath 0.090709+0-3
ii  texlive-latex-extra  2016.20170123-5

-- no debconf information
Description: Removes ugly icon scaling in toolbar
Author: Stanislav Maslovski 

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

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

--- wxmaxima-17.10.1.orig/src/ToolBar.cpp
+++ wxmaxima-17.10.1/src/ToolBar.cpp
@@ -43,9 +43,11 @@ wxImage ToolBar::GetImage(wxString name)
 Dirstructure dirstructure;
 img = wxImage(dirstructure.ConfigToolbarDir() + wxT("/") + name + 
wxT(".png"));
   }
+/*
   double imgWidth = wxGetDisplayPPI().x*24/72;
   double scaleFactor = imgWidth / img.GetWidth();
   
img.Rescale(img.GetWidth()*scaleFactor,img.GetHeight()*scaleFactor,wxIMAGE_QUALITY_HIGH
 );
+ */
   return img;
 }
 

Bug#881280: update for zsh and fish completions

[Joey Hess]

Package: libghc-optparse-applicative-dev
Version: 0.13.2.0-1+b1
Severity: normal

Version 0.14 added support for zsh and fish completion. git-annex
uses that feature.

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

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

Versions of packages libghc-optparse-applicative-dev depends on:
ii  ghc [libghc-transformers-dev-0.5.2.0-1d020]8.0.2-10
ii  libc6  2.24-17
ii  libghc-ansi-wl-pprint-dev [libghc-ansi-wl-pprint-dev-0.6.  0.6.7.3-3+b3
pn  libghc-base-dev-4.9.1.0-d28d6  
pn  libghc-process-dev-1.4.3.0-996f5   
ii  libghc-transformers-compat-dev [libghc-transformers-compa  0.5.1.4-2+b1
ii  libgmp10   2:6.1.2+dfsg-1.1

libghc-optparse-applicative-dev recommends no packages.

Versions of packages libghc-optparse-applicative-dev suggests:
ii  libghc-optparse-applicative-doc   0.13.2.0-1
ii  libghc-optparse-applicative-prof  0.13.2.0-1+b1

-- no debconf information

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#881272: gcc-5-: broken symlink /usr/lib/gcc-cross//5/libcc1.so -> ../../../..//lib/libcc1.so.0

[Matthias Klose]

On 09.11.2017 15:51, Andreas Beckmann wrote:
> Source: gcc-5
> Version: 5.5.0-3
> Severity: important
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.
> 
>>From the attached log (scroll to the bottom...):
> 
> 0m25.1s ERROR: FAIL: Broken symlinks:
>   /usr/lib/gcc-cross/mips-linux-gnu/5/libcc1.so -> 
> ../../../../mips-linux-gnu/lib/libcc1.so.0
> 
> 
> That seems to be the last broken link in the gcc-5-cross and
> gcc-5-cross-ports packages.
> (gcc-6-* and gcc-7-* look clean now :-)

is this with the gcc-5-cross* packages which are currently built but not 
uploaded?

Bug#857393: closed by Jochen Sprickerhof (Bug#857393: fixed in gazebo 7.8.1+dfsg-2)

[Andreas Beckmann]

On 10/16/2017 09:21 AM, Debian Bug Tracking System wrote:
>  gazebo (7.8.1+dfsg-2) unstable; urgency=medium
>* Fix fonts dependencies (Closes: #878595, #857393, #857393)

For consistency, the fonts-liberation dependency should rather be moved
to gazebo7-common (which contains the font symlinks)


Andreas

Bug#881266: apt-files fails with LZ4F error on calling apt-helper with xargs

[Ara Keary]

> It's definitely not an apt-file problem if apt-helper exits. It seems to me 
> that
> the file is broken. I'd assume your memory or hard disk is failing, or you 
> force
> rebooted while/after apt(-get) update was running and writing that file and we
> maybe do not sync it correctly. Or maybe it's a bug in lz4 decompressor - I 
> don't
> know.
>
> In either case, I've not seen this before. You could also try using "lz4cat"
> from liblz4-tool, that should fail as well. I'd say upload the file, but it's
> probably about 60-90 MB or so, so probably not really an option.
>

It is quite strange indeed: i have installed liblz4-tool, and the
described behaviour has vanished.
After purging liblz4-tool, the correct exptected behvaiour of apt-file remains
Maybe this was due to a problem with the synchronisation of the debian
packages...

Sorry for the noise

Best

Ara