date:20190114

Bug#919349: pyvo: Please remove python-astropy-helpers build dependency

2019-01-14 Thread Ole Streicher

Source: pyvo
Version: 0.9.2-1
Severity: serious

Dear maintainer,

python-astropy-helpers (the Python 2 package) is going away soon.
Therefore, please remove it as build dependency from pyvo. I is probably
anyway unused and just forgotten to remove, right?

Cheers

Ole

Bug#919332: casparcg-server: FTBFS in sid (cannot find -lpthreads)

2019-01-14 Thread Petter Reinholdtsen

[Santiago Vila]
> I tried to build this package in sid but it failed:

Thank you for the heads up.

> but the error message suggests a missing build-dependency.

I agree, but libpthread is part of glibc, so it can not be that one.
Perhaps libc6-dev is the missing one?  Seem unlikely, given it is
Build-Essential: yes.  Any idea which one can be missing?

It build for me, but I fail to understand why now. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#784479: [kde4libs] Qt4's WebKit removal

2019-01-14 Thread Pino Toscano

In data lunedì 14 gennaio 2019 22:28:46 CET, Adrian Bunk ha scritto:
> What is actually the overall plan for KDE4 in buster now?

kdelibs 4.x will stay in buster. Period.

Dropping stuff just for the sake of removal is a no-go, especially
when done from people who have NO IDEA about Qt/KDE
libraries/applications.

As I already asked you: Adrian Bunk, please stay away from Qt/KDE
stuff.

Thanks,
-- 
Pino Toscano

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

Bug#784479: [kde4libs] Qt4's WebKit removal

2019-01-14 Thread Pino Toscano

In data lunedì 14 gennaio 2019 12:22:52 CET, Scott Kitterman ha scritto:
> On Thu, 01 Nov 2018 14:04:12 -0300 Lisandro 
> =?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer  wrote:
> > On Wed, 17 Oct 2018 15:57:25 +0200 Ivo De Decker  wrote:
> > > Hi,
> > > 
> > > On Fri, Nov 24, 2017 at 04:59:58PM -0300, Lisandro Damián Nicanor Pérez 
> > Meyer wrote:
> > > > Control: tag -1 patch
> > > > 
> > > > There is patch available for this at 
>  > > > packages.git/tree/trunk/kdelibs-no-kdewebkit.patch?h=packages/kdelibs>
> > > > 
> > > > We might want to wait for the last tandem of KF5 apps though.
> > > 
> > > Is there anything still blocking this?
> > 
> > Yes, at least one co maintainer believes the kde-runtime patch is not 
> > appropriate.
> 
> That patch no longer seems to be available, so I made my own.  Patches for 
> kde4libs and kde-runtime attached.  I looked at the KDE4 packages still in 
> Buster and I don't believe this interferes with anything.  This also fixes 
> the 
> FTBFS with Samba 4.9 by dropping the KDE4 kio_smb.

The samba compatibility issue is a different story, and it can be fixed
by just disabling kio_smb (in case it requires non-trivial work to make
it work again).

> I think we should move forward on these (or some improved version if someone 
> has suggestions).
> 
> Even though there are separate bugs for kde-runtime, since the patch for it 
> was already discussed in this bug, I thought we might as well keep them 
> together.

Did you check that all the packages using kde4libs still build fine?

The removal of kio_thumbnail from kde-runtime is definitely not
appropriate, since it will break the thunbnail support for any
kdelibs 4.x application.

Again: something worth to mention, since apparently it is not clear:
removing bits from either kde4libs or kde-runtime has consequences,
either build time or runtime ones. Randomly chopping pieces without
checking what changes, and potentially what breaks, is generally a
big no-no from me. I do not see how "remove qtwebkit" is an excuse to
start messing up with packages, just for the sake of package removal.

-- 
Pino Toscano

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

Bug#919103: marked as done (libreoffice-kde5: failure to upgrade from stretch: soffice.odg also in libreoffice-kde)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Tue, 15 Jan 2019 07:07:42 +
with message-id 
and subject line Bug#919103: fixed in libreoffice 1:6.1.4-4
has caused the Debian Bug report #919103,
regarding libreoffice-kde5: failure to upgrade from stretch: soffice.odg also 
in libreoffice-kde
to be marked as done.

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


-- 
919103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-kde5
Version: 1:6.1.4-3
Severity: serious
Justification: failure to install/upgrade

Hi,

Testing the upgrade path from stretch to buster for various desktop
tasks, I've noticed the following issue:

Unpacking libreoffice-kde5 (1:6.1.4-3+b1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-q3iqce/43-libreoffice-kde5_1%3a6.1.4-3+b1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/share/templates/.source/soffice.odg', which is 
also in package libreoffice-kde 1:5.2.7-1+deb9u4

which breaks the dist-upgrade.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:6.1.4-4

We believe that the bug you reported is fixed in the latest version of
libreoffice, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Jan 2019 08:25:12 +0100
Source: libreoffice
Binary: libreoffice libreoffice-l10n-za libreoffice-l10n-in libreoffice-core 
libreoffice-common libreoffice-java-common libreoffice-help-common 
libreoffice-writer libreoffice-calc libreoffice-impress libreoffice-draw 
libreoffice-math libreoffice-base-core libreoffice-base 
libreoffice-style-breeze libreoffice-style-colibre libreoffice-style-tango 
libreoffice-style-sifr libreoffice-style-elementary libreoffice-gnome 
python3-uno libreoffice-officebean libreoffice-script-provider-python 
libreoffice-script-provider-bsh libreoffice-script-provider-js 
libreoffice-avmedia-backend-gstreamer libreoffice-avmedia-backend-vlc 
libreoffice-sdbc-hsqldb libreoffice-base-drivers libreoffice-l10n-af 
libreoffice-l10n-am libreoffice-l10n-ar libreoffice-l10n-as 
libreoffice-l10n-ast libreoffice-l10n-be libreoffice-l10n-bg 
libreoffice-l10n-bn libreoffice-l10n-br libreoffice-l10n-bs libreoffice-l10n-ca 
libreoffice-l10n-cs libreoffice-l10n-cy libreoffice-l10n-da libreoffice-l10n-de
 libreoffice-l10n-dz libreoffice-l10n-el libreoffice-l10n-en-gb 
libreoffice-l10n-en-za libreoffice-l10n-eo libreoffice-l10n-es 
libreoffice-l10n-et libreoffice-l10n-eu libreoffice-l10n-fa libreoffice-l10n-fi 
libreoffice-l10n-fr libreoffice-l10n-ga libreoffice-l10n-gd libreoffice-l10n-gl 
libreoffice-l10n-gu libreoffice-l10n-gug libreoffice-l10n-he 
libreoffice-l10n-hi libreoffice-l10n-hr libreoffice-l10n-hu libreoffice-l10n-id 
libreoffice-l10n-is libreoffice-l10n-it libreoffice-l10n-ja libreoffice-l10n-ka 
libreoffice-l10n-kk libreoffice-l10n-km libreoffice-l10n-kmr 
libreoffice-l10n-kn libreoffice-l10n-ko libreoffice-l10n-lt libreoffice-l10n-lv 
libreoffice-l10n-mk libreoffice-l10n-mn libreoffice-l10n-ml libreoffice-l10n-mr 
libreoffice-l10n-nb libreoffice-l10n-ne libreoffice-l10n-nl libreoffice-l10n-nn 
libreoffice-l10n-nr libreoffice-l10n-nso libreoffice-l10n-oc 
libreoffice-l10n-om libreoffice-l10n-or libreoffice-l10n-pa-in 
libreoffice-l10n-pl libreoffice-l10n-pt
 libreoffice-l10n-pt-br libreoffice-l10n-ro libreoffice-l10n-ru 
libreoffice-l10n-rw libreoffice-l10n-si libreoffice-l10n-sk libreoffice-l10n-sl 
libreoffice-l10n-sr libreoffice-l10n-ss libreoffice-l10n-st libreoffice-l10n-sv 
libreoffice-l10n-ta libreoffice-l10n-te libreoffice-l10n-tg libreoffice-l10n-th 
libreoffice-l10n-tn libreoffice-l10n-tr libreoffice-l10n-ts libreoffice-l10n-ug 
libreoffice-l10n-uk libreoffice-l10n-uz libreoffice-l10n-ve libreoffice-l10n-vi 
libreoffice-l10n-xh libreoffice-l10n-zh-cn libreoffice-l10n-zh-tw

Bug#918499: marked as done ([libreoffice] libreoffice: fails with ERROR 4 forking process with apparmor << 2.13.1)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Tue, 15 Jan 2019 07:07:42 +
with message-id 
and subject line Bug#918499: fixed in libreoffice 1:6.1.4-4
has caused the Debian Bug report #918499,
regarding [libreoffice] libreoffice: fails with ERROR 4 forking process with 
apparmor << 2.13.1
to be marked as done.

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


-- 
918499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice
Version: 1:6.1.3-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm running "testing", and recently did a dist-upgrade.  Previously
libreoffice worked fine, but now fails to start.  From the menu,
nothing happens.  From command line, it fails with the subject error:

  % libreoffice
  ERROR 4 forking process

Poking around at the symlinks and scripts, it seems it is actually
trying to execute /usr/lib/libreoffice/program/oosplash:

  % /usr/lib/libreoffice/program/oosplash
  ERROR 4 forking process

I tried running with --strace and was surprised to find the
application actually opened and seemed to work normally.  Looking at
the script, with any of the debug options it runs soffice.bin instead
of oosplash, and indeed this works:

  % /usr/lib/libreoffice/program/soffice.bin  # runs normally

I don't know enough about libreoffice to know if any of this is
Debian-specific.  And don't have the wherewithal right now to download
a stock version from libreoffice.com to see if it exhibits the same
problem.

In case it's useful, I'll attache the strace output below.

Thanks.

-David

 begin strace output 

% strace /usr/lib/libreoffice/program/oosplash
execve("/usr/lib/libreoffice/program/oosplash", 
["/usr/lib/libreoffice/program/oos"...], 0x7ffdeaef6480 /* 54 vars */) = 0
brk(NULL)   = 0x55e538c94000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
readlink("/proc/self/exe", "/usr/lib/libreoffice/program/oos"..., 4096) = 37
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, 
"/usr/lib/libreoffice/program/tls/x86_64/x86_64/libXinerama.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/libreoffice/program/tls/x86_64/x86_64", 0x7ffe049e3460) = -1 
ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/libreoffice/program/tls/x86_64/libXinerama.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/libreoffice/program/tls/x86_64", 0x7ffe049e3460) = -1 ENOENT (No 
such file or directory)
openat(AT_FDCWD, "/usr/lib/libreoffice/program/tls/x86_64/libXinerama.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/libreoffice/program/tls/x86_64", 0x7ffe049e3460) = -1 ENOENT (No 
such file or directory)
openat(AT_FDCWD, "/usr/lib/libreoffice/program/tls/libXinerama.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/libreoffice/program/tls", 0x7ffe049e3460) = -1 ENOENT (No such 
file or directory)
openat(AT_FDCWD, "/usr/lib/libreoffice/program/x86_64/x86_64/libXinerama.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/libreoffice/program/x86_64/x86_64", 0x7ffe049e3460) = -1 ENOENT 
(No such file or directory)
openat(AT_FDCWD, "/usr/lib/libreoffice/program/x86_64/libXinerama.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/libreoffice/program/x86_64", 0x7ffe049e3460) = -1 ENOENT (No 
such file or directory)
openat(AT_FDCWD, "/usr/lib/libreoffice/program/x86_64/libXinerama.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/libreoffice/program/x86_64", 0x7ffe049e3460) = -1 ENOENT (No 
such file or directory)
openat(AT_FDCWD, "/usr/lib/libreoffice/program/libXinerama.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/libreoffice/program", {st_mode=S_IFDIR|0755, st_size=36864, 
...}) = 0
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=263520, ...}) = 0
mmap(NULL, 263520, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fe1f54c
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/libXinerama.so.1", 
O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\20\21\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=14496, ...}) = 0
mmap(NULL,

Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

2019-01-14 Thread Diane Trout

On Tue, 2019-01-15 at 00:08 +0100, Florian Schlichting wrote:
> 
> Before thinking about cleanup, I'd start by making sure that fresh
> installs don't re-create problems. At the moment, purging dnssec-
> trigger
> leaves two keypairs in /etc; and when I rm them manually, and again
> install dnssec-trigger, they're back (in addition to the identically
> named pair in /etc/dnssec-trigger, which does get cleaned up on
> purge).
> Does that not happen for you?

No dnssec-trigger has  been leaving configuration files all over the
place.

I think I've found more of the configuration file installation
locations and fixed them to point to /etc/dnssec-trigger/, but now I'm
encountering the segfault while installing, that caused Axel Beckert to
open this bug so I'm having trouble testing all the fixes.

I did a bit of test driven development, wrote tests for config files in
/etc/, made sure it failed, then fixed the paths, and made sure the
tests pass -- at least when running in autopkgtest.

But I'd like to find the segfault before making another release.

Diane

Processed: bug 919256 is forwarded to https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4218

2019-01-14 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> forwarded 919256 https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4218
Bug #919256 [dnssec-trigger] dnssec-trigger: Failed to upgrade: installed 
dnssec-trigger package post-installation script subprocess returned error exit 
status 1
Set Bug forwarded-to-address to 
'https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4218'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
919256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 919322 is forwarded to https://github.com/svgpp/svgpp/issues/70

2019-01-14 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> forwarded 919322 https://github.com/svgpp/svgpp/issues/70
Bug #919322 [src:agg] CVE-2019-6245 CVE-2019-6247
Set Bug forwarded-to-address to 'https://github.com/svgpp/svgpp/issues/70'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
919322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 919321 is forwarded to https://github.com/svgpp/svgpp/issues/70

2019-01-14 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> forwarded 919321 https://github.com/svgpp/svgpp/issues/70
Bug #919321 [src:svgpp] CVE-2019-6246
Set Bug forwarded-to-address to 'https://github.com/svgpp/svgpp/issues/70'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
919321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#919341: libtool-bin: amd64 /usr/bin/libtool is a zero byte file

2019-01-14 Thread Cyril Brulebois

Cyril Brulebois  (2019-01-15):
> I'm attaching individual patches addressing these, along with a ready to
> use (except for “dch -r”) source debdiff. A quick upload and further
> assessment would likely be a good idea.

Oops, forgot to mention → MR available if that's easier:
  https://salsa.debian.org/mckinstry/libtool/merge_requests/1


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#919341: libtool-bin: amd64 /usr/bin/libtool is a zero byte file

2019-01-14 Thread Cyril Brulebois

Control: severity -1 grave
Control: tag -1 patch

Cyril Brulebois  (2019-01-15):
> For some reasons, libtool and its manpage (from the libtool-bin binary)
> are “sanitized” in binary-indep, which might explain why it's only
> showing up on the maintainer build which was likely using “-b”.
> 
> > $ dpkg-deb -c libtool-bin_2.4.6-7_amd64.deb
> > -rwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/bin/libtool
> > -rw-r--r-- root/root20 2019-01-12 09:10 
> > ./usr/share/man/man1/libtool.1.gz
> 
> The manpage is a gzipped empty file.

I'm afraid the situation is pretty bad, as an empty executable doesn't
do anything but also produces no errors; so I fear any packages having
been built using this version of libtool-bin on amd64 has likely missed
a step or two without that getting noticed…

Cc-ing debian-release@ & debian-wb-team@ for information.

> At least those points need addressing:
>  1. some sed lines have an extra slash before the repetition specifier.
>  2. the for loop isn't set up to bail out on errors
>  3. libtoolize from bin:libtool which is arch:all is “sanitized”
> in binary-arch; looks like a mixup between both targets given
> the already mentioned libtool (binary and manpage)…
>  4. hardcoding the upstream version in debian/rules looks like a recipe
> for a later regression

I'm attaching individual patches addressing these, along with a ready to
use (except for “dch -r”) source debdiff. A quick upload and further
assessment would likely be a good idea.

Setting up something with autopkgtest might be worth it, if only just to
check a few trivial commands (--help comes to mind).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
From e3c73f4532de8f8f83b242011f536729f4db7b05 Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Tue, 15 Jan 2019 03:41:39 +
Subject: [PATCH 1/7] Fix Vcs-* URLs.

---
 debian/changelog | 6 ++
 debian/control   | 4 ++--
 2 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index ace7740..4266654 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libtool (2.4.6-8) UNRELEASED; urgency=medium
+
+  * Fix Vcs-* URLs.
+
+ -- Cyril Brulebois   Tue, 15 Jan 2019 03:41:15 +
+
 libtool (2.4.6-7) unstable; urgency=medium
 
   * Standards-Version: 4.3.0
diff --git a/debian/control b/debian/control
index c2cfefc..0d92424 100644
--- a/debian/control
+++ b/debian/control
@@ -17,8 +17,8 @@ Maintainer: Alastair McKinstry 
 Standards-Version: 4.3.0
 Rules-Requires-Root: no
 Homepage: https://www.gnu.org/software/libtool/
-Vcs-Browser: https://salsa.debian.org:/mckinstry/libtool.git
-Vcs-Git: https://salsa.debian.org:/mckinstry/libtool.git
+Vcs-Browser: https://salsa.debian.org/mckinstry/libtool.git
+Vcs-Git: https://salsa.debian.org/mckinstry/libtool.git
 
 Package: libtool
 Architecture: all
-- 
2.11.0

From 3849d58d6013a1ae557647335b215a6cfe62d725 Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Tue, 15 Jan 2019 03:42:58 +
Subject: [PATCH 2/7] Fix sed syntax errors. Closes: #919341

These errors lead to empty libtool executable and manpage. With thanks
to James McCoy for reporting.
---
 debian/changelog | 2 ++
 debian/rules | 8 
 2 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 4266654..da983ae 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,8 @@
 libtool (2.4.6-8) UNRELEASED; urgency=medium
 
   * Fix Vcs-* URLs.
+  * Fix sed syntax errors leading to empty libtool executable and
+manpage, with thanks to James McCoy for reporting. Closes: #919341
 
  -- Cyril Brulebois   Tue, 15 Jan 2019 03:41:15 +
 
diff --git a/debian/rules b/debian/rules
index 004285f..e502a2b 100755
--- a/debian/rules
+++ b/debian/rules
@@ -163,8 +163,8 @@ binary-indep: build-indep install
 	for f in \
 		debian/libtool-bin/usr/share/man/man1/libtool.1 \
 		debian/libtool-bin/usr/bin/libtool ; do cat $$f | \
-			sed -e 's%/usr/bin/grep%/bin/grep%/g' | \
-			sed -e 's%/usr/bin/sed%/bin/sed%/g' | \
+			sed -e 's%/usr/bin/grep%/bin/grep%g' | \
+			sed -e 's%/usr/bin/sed%/bin/sed%g' | \
 			sed -e 's%/usr/bin/dd%/bin/dd%g' | \
 			sed -e 's%${CURDIR}%/build/libtool-2.4.6%g' | \
 			> debian/tmpff ; \
@@ -193,8 +193,8 @@ binary-arch: build-arch install
 	for f in \
 		debian/libtool/usr/bin/libtoolize ; do \
 		cat $$f | \
-			sed -e 's%/usr/bin/grep%/bin/grep%/g' | \
-			sed -e 's%/usr/bin/sed%/bin/sed%/g' | \
+			sed -e 's%/usr/bin/grep%/bin/grep%g' | \
+			sed -e 's%/usr/bin/sed%/bin/sed%g' | \
 			sed -e 's%/usr/bin/dd%/bin/dd%g' | \
 			sed -e 's%${CURDIR}%/build/libtool-2.4.6%g' | \
 			> debian/tmpff ; \
-- 
2.11.0

From 669ed2faf2510b3931cf4a37ca53ba15a8c0598f Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Tue, 15 Jan 2019 03:46:37 +
Subject: [PATCH 3/7] Fix sanitation of libtool vs. libtoolize.

The former

Processed: Re: Bug#919341: libtool-bin: amd64 /usr/bin/libtool is a zero byte file

2019-01-14 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 grave
Bug #919341 [libtool-bin] libtool-bin: amd64 /usr/bin/libtool is a zero byte 
file
Severity set to 'grave' from 'serious'
> tag -1 patch
Bug #919341 [libtool-bin] libtool-bin: amd64 /usr/bin/libtool is a zero byte 
file
Added tag(s) patch.

-- 
919341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#919341: libtool-bin: amd64 /usr/bin/libtool is a zero byte file

2019-01-14 Thread Cyril Brulebois

Hi James,

James McCoy  (2019-01-14):
> The amd64 package, the only one not built on a buildd, contains a
> zero-byte /usr/bin/libtool.  This makes it completely non-functional.

For some reasons, libtool and its manpage (from the libtool-bin binary)
are “sanitized” in binary-indep, which might explain why it's only
showing up on the maintainer build which was likely using “-b”.

> $ dpkg-deb -c libtool-bin_2.4.6-7_amd64.deb
> -rwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/bin/libtool
> -rw-r--r-- root/root20 2019-01-12 09:10 
> ./usr/share/man/man1/libtool.1.gz

The manpage is a gzipped empty file.

Looking at debian/rules, this cannot possibly work… which is confirmed
by an amd64 build inside a (non-minimal) sid devel schroot, with
“dpkg-buildpackage -b”:
| # Sanitize /usr-merge path builds
| for f in \
|   debian/libtool-bin/usr/share/man/man1/libtool.1 \
|   debian/libtool-bin/usr/bin/libtool ; do cat $f | \
|   sed -e 's%/usr/bin/grep%/bin/grep%/g' | \
|   sed -e 's%/usr/bin/sed%/bin/sed%/g' | \
|   sed -e 's%/usr/bin/dd%/bin/dd%g' | \
|   sed -e 's%/tmp/libtool-2.4.6%/build/libtool-2.4.6%g' | \
|   > debian/tmpff ; \
|   mv debian/tmpff $f ; \
|   done
| sed: -e expression #1, char 25: unknown option to `s'
| sed: -e expression #1, char 27: unknown option to `s'
| sed: -e expression #1, char 27: unknown option to `s'
| sed: -e expression #1, char 25: unknown option to `s'
[…]
| # Sanitize /usr-merge path builds
| for f in \
|   debian/libtool/usr/bin/libtoolize ; do \
|   cat $f | \
|   sed -e 's%/usr/bin/grep%/bin/grep%/g' | \
|   sed -e 's%/usr/bin/sed%/bin/sed%/g' | \
|   sed -e 's%/usr/bin/dd%/bin/dd%g' | \
|   sed -e 's%/tmp/libtool-2.4.6%/build/libtool-2.4.6%g' | \
|   > debian/tmpff ; \
|   mv debian/tmpff $f ; \
|   done
| sed: -e expression #1, char 25: unknown option to `s'
| sed: -e expression #1, char 27: unknown option to `s'

At least those points need addressing:
 1. some sed lines have an extra slash before the repetition specifier.
 2. the for loop isn't set up to bail out on errors
 3. libtoolize from bin:libtool which is arch:all is “sanitized”
in binary-arch; looks like a mixup between both targets given
the already mentioned libtool (binary and manpage)…
 4. hardcoding the upstream version in debian/rules looks like a recipe
for a later regression


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#903201: cinnamon: CVE-2018-13054: privilege escalation in cinnamon-settings-users.py GUI

2019-01-14 Thread Andres Salomon

On Mon, Jan 14, 2019 at 5:39 PM, Andres Salomon  
wrote


It's not a critical bug (cinnamon-settings-users continues running), 
it just can't update
the file.  That needs to be fixed upstream if it's not already, by 
changing ownership or
deleting the old file before dropping privileges.  I've attached a 
patch that deletes the

old file.


I realized that os.remove throws an exception if the file isn't there, 
which isn't what we
want. Here's an updated patch.  It works with .face owned by root, 
owned by the proper

user, or when it doesn't exist at all.
--- /usr/share/cinnamon/cinnamon-settings-users/cinnamon-settings-users.py.orig	2019-01-14 17:24:37.799003654 -0800
+++ /usr/share/cinnamon/cinnamon-settings-users/cinnamon-settings-users.py	2019-01-14 18:41:39.855137769 -0800
@@ -675,6 +675,10 @@
 image.thumbnail((96, 96), Image.ANTIALIAS)
 face_path = os.path.join(user.get_home_dir(), ".face")
 try:
+try:
+os.remove(face_path)
+except:
+pass
 priv_helper.drop_privs(user)
 image.save(face_path, "png")
 finally:
@@ -704,9 +708,14 @@
 user = model[treeiter][INDEX_USER_OBJECT]
 user.set_icon_file(path)
 self.face_image.set_from_file(path)
+face_path = os.path.join(user.get_home_dir(), ".face")
 try:
+try:
+os.remove(face_path)
+except:
+pass
 priv_helper.drop_privs(user)
-shutil.copy(path, os.path.join(user.get_home_dir(), ".face"))
+shutil.copy(path, face_path)
 finally:
 priv_helper.restore_privs()
 model.set_value(treeiter, INDEX_USER_PICTURE, GdkPixbuf.Pixbuf.new_from_file_at_size(path, 48, 48))

Bug#918502: marked as done (golang-github-opencontainers-runtime-tools: autopkgtest needs update for new version of golang-github-hashicorp-go-multierror)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Tue, 15 Jan 2019 02:49:34 +
with message-id 
and subject line Bug#918502: fixed in 
golang-github-opencontainers-runtime-tools 0.8.0+dfsg-1
has caused the Debian Bug report #918502,
regarding golang-github-opencontainers-runtime-tools: autopkgtest needs update 
for new version of golang-github-hashicorp-go-multierror
to be marked as done.

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


-- 
918502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-opencontainers-runtime-tools
Version: 0.7.0+dfsg-1
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:golang-github-hashicorp-go-multierror

Dear maintainers,

With a recent upload of golang-github-hashicorp-go-multierror the
autopkgtest of golang-github-opencontainers-runtime-tools fails in
testing when that autopkgtest is run with the binary packages of
golang-github-hashicorp-go-multierror from unstable. It passes when run
with only packages from testing. In tabular form:
   passfail
golang-github-hashicorp-go-multierror  from testing1.0.0-1
golang-github-opencontainers-runtime-tools from testing0.7.0+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Looking at the
error, it seems you just need to update the reference.

Currently this regression is contributing to the delay of the migration
of golang-github-hashicorp-go-multierror to testing [1]. Of course,
golang-github-hashicorp-go-multierror shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in golang-github-hashicorp-go-multierror was intended and your
package needs to update to the new situation. If needed, please change
the bug's severity.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from
golang-github-hashicorp-go-multierror should really add a versioned
Breaks on the unfixed version of (one of your) package(s). Note: the
Breaks is nice even if the issue is only in the autopkgtest as it helps
the migration software to figure out the right versions to combine in
the tests.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
golang-github-hashicorp-go-multierror/1.0.0-1. I.e. due to versioned
dependencies or breaks/conflicts.
[1]
https://qa.debian.org/excuses.php?package=golang-github-hashicorp-go-multierror

https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-opencontainers-runtime-tools/1651937/log.gz

--- FAIL: TestCheckMandatoryFields (0.00s)
--- FAIL:
TestCheckMandatoryFields/1_error_occurred:__*_'Spec.Version'_should_not_be_empty
(0.00s)
validate_test.go:759:
Error Trace:validate_test.go:759
Error:  Not equal:
expected: "1 error occurred:\n\n*
'Spec.Version' should not be empty"
actual  : "1 error occurred:\n\t*
'Spec.Version' should not be empty\n\n"

Diff:
--- Expected
+++ Actual
@@ -1,3 +1,4 @@
 1 error occurred:
+   * 'Spec.Version' should not be empty

-* 'Spec.Version' should not be empty
+
Test:
TestCheckMandatoryFields/1_error_occurred:__*_'Spec.Version'_should_not_be_empty
--- FAIL:
TestCheckMandatoryFields/1_error_occurred:__*_Spec_can't_be_nil (0.00s)
validate_test.go:759:
Error Trace:validate_test.go:759
Error:  Not equal:
expected: "1 error occurred:\n\n* Spec can't
be nil"
actual  : "1 error occurred:\n\t* Spec can't
be nil\n\n"

Diff:
--- Expected
+++ Actual

Bug#919341: libtool-bin: amd64 /usr/bin/libtool is a zero byte file

2019-01-14 Thread James McCoy

Package: libtool-bin
Version: 2.4.6-7
Severity: serious
File: /usr/bin/libtool

The amd64 package, the only one not built on a buildd, contains a
zero-byte /usr/bin/libtool.  This makes it completely non-functional.

$ dpkg-deb -c libtool-bin_2.4.6-7_amd64.deb
drwxr-xr-x root/root 0 2019-01-12 09:10 ./
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/bin/
-rwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/bin/libtool
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/doc/
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/doc/libtool-bin/
-rw-r--r-- root/root  9329 2019-01-12 09:10 
./usr/share/doc/libtool-bin/changelog.Debian.gz
-rw-r--r-- root/root342562 2015-02-15 12:15 
./usr/share/doc/libtool-bin/changelog.gz
-rw-r--r-- root/root  1976 2019-01-12 09:10 
./usr/share/doc/libtool-bin/copyright
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/man/
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/man/man1/
-rw-r--r-- root/root20 2019-01-12 09:10 
./usr/share/man/man1/libtool.1.gz

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

Kernel: Linux 4.19.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)
LSM: AppArmor: enabled

Versions of packages libtool-bin depends on:
ii  libtool  2.4.6-7

libtool-bin recommends no packages.

libtool-bin suggests no packages.

-- no debconf information

Bug#919340: fenix-plugins: FTBFS: configure.ac:36: error: possibly undefined macro: AC_CHECK_FT2

2019-01-14 Thread Andreas Beckmann

Source: fenix-plugins
Version: 0.0.20070803-7
Severity: serious
Tags: sid buster
Justification: fails to build from source (but built successfully in the past)

Hi,

fenix-plugins cannot be rebuilt any longer in a current pbuilder sid
environment:

 debian/rules build
dh build --with autoreconf
   dh_update_autotools_config
   dh_autoreconf
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:14: installing './compile'
configure.ac:11: installing './missing'
Makefile.am: installing './depcomp'
libtoolize: putting auxiliary files in '.'.
[...]
configure.ac:11: installing './missing'
Makefile.am: installing './depcomp'
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:36: error: possibly undefined macro: AC_CHECK_FT2
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1
dh_autoreconf: autoreconf -f -i agua-1.0 exec-0.4a fgfx-1.0 fire-1.0 fsock-1.0 
image-1.0 mixer-1.0 mpeg-1.0 net-1.0 tcpsock-2.0 ttf-1.0 returned exit code 1
make: *** [debian/rules:31: build] Error 2


Cheers,

Andreas


fenix-plugins_0.0.20070803-7.build.gz
Description: application/gzip

Bug#903201: cinnamon: CVE-2018-13054: privilege escalation in cinnamon-settings-users.py GUI

2019-01-14 Thread Andres Salomon


Hi,

Is there a reason why this hasn't been fixed in stretch yet?  The 
upstream commit is here:


https://github.com/linuxmint/Cinnamon/commit/66e54f43f179fdf041a3e5232178a9910963cfb5

https://github.com/linuxmint/Cinnamon/commit/66e54f43f179fdf041a3e5232178a9910963cfb5.patch

It applies to the version in stretch, and I've tested it.  Here's the 
before:

dilinger@e7470:~$ ls -l .face
-rw-r--r-- 1 root root 9379 Jan 14 17:14 .face

After:
dilinger@e7470:~$ ls -lh .face
-rw-r--r-- 1 dilinger dilinger 2.6K Jan 14 17:19 .face

There is, however, a problem where the root-owned .face cannot be 
overwritten once the

new code drops privileges:

Traceback (most recent call last):
 File 
"/usr/share/cinnamon/cinnamon-settings-users/cinnamon-settings-users.py", 
line 709, in _on_face_menuitem_activated

   shutil.copy(path, os.path.join(user.get_home_dir(), ".face"))
 File "/usr/lib/python2.7/shutil.py", line 119, in copy
   copyfile(src, dst)
 File "/usr/lib/python2.7/shutil.py", line 83, in copyfile
   with open(dst, 'wb') as fdst:
IOError: [Errno 13] Permission denied: '/home/dilinger/.face'

It's not a critical bug (cinnamon-settings-users continues running), it 
just can't update
the file.  That needs to be fixed upstream if it's not already, by 
changing ownership or
deleting the old file before dropping privileges.  I've attached a 
patch that deletes the

old file.

Thanks,
Andres
--- /usr/share/cinnamon/cinnamon-settings-users/cinnamon-settings-users.py.orig	2019-01-14 17:24:37.799003654 -0800
+++ /usr/share/cinnamon/cinnamon-settings-users/cinnamon-settings-users.py	2019-01-14 17:38:06.248595816 -0800
@@ -675,6 +675,7 @@
 image.thumbnail((96, 96), Image.ANTIALIAS)
 face_path = os.path.join(user.get_home_dir(), ".face")
 try:
+os.remove(face_path)
 priv_helper.drop_privs(user)
 image.save(face_path, "png")
 finally:
@@ -704,9 +705,11 @@
 user = model[treeiter][INDEX_USER_OBJECT]
 user.set_icon_file(path)
 self.face_image.set_from_file(path)
+face_path = os.path.join(user.get_home_dir(), ".face")
 try:
+os.remove(face_path)
 priv_helper.drop_privs(user)
-shutil.copy(path, os.path.join(user.get_home_dir(), ".face"))
+shutil.copy(path, face_path)
 finally:
 priv_helper.restore_privs()
 model.set_value(treeiter, INDEX_USER_PICTURE, GdkPixbuf.Pixbuf.new_from_file_at_size(path, 48, 48))

Bug#897623: marked as done (src:fortunate.app: FTBFS with gs_make removed)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Tue, 15 Jan 2019 01:34:03 +
with message-id 
and subject line Bug#897623: fixed in fortunate.app 3.1-2
has caused the Debian Bug report #897623,
regarding src:fortunate.app: FTBFS with gs_make removed
to be marked as done.

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


-- 
897623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fortunate.app
Version: 3.1-1
Severity: important
User: pkg-gnustep-maintain...@lists.alioth.debian.org
Usertags: gs_make-removal

The gs_make wrapper will be removed in the next Debian release of
gnustep-make.  This package will FTBFS with the following error:

 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp
gs_make clean distclean
make: gs_make: Command not found
make: *** [debian/rules:19: clean] Error 127
--- End Message ---
--- Begin Message ---
Source: fortunate.app
Source-Version: 3.1-2

We believe that the bug you reported is fixed in the latest version of
fortunate.app, 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 897...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated fortunate.app package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 13 Nov 2018 12:19:39 +0100
Source: fortunate.app
Binary: fortunate.app
Architecture: source
Version: 3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNUstep maintainers 

Changed-By: Gürkan Myczko 
Description:
 fortunate.app - Display a quotation (fortune) in a window for GNUstep
Closes: 897623
Changes:
 fortunate.app (3.1-2) unstable; urgency=medium
 .
   * debian/rules:
 - modernized. (Closes: #897623)
 - move binary to /usr/games.
   * Bump debhelper version to 11.
   * Bump standards version to 4.2.1.
   * debian/menu: dropped.
Checksums-Sha1:
 ec8faeb1154445db87bbee5d9d11221cd3c8e33f 1875 fortunate.app_3.1-2.dsc
 8cdaa5c032f77fc0a26d32fedd4192ae5606fcdb 4344 fortunate.app_3.1-2.debian.tar.xz
 bbaf13486094e49f09d8d75fac3eaa6247bc5fbc 5430 
fortunate.app_3.1-2_source.buildinfo
Checksums-Sha256:
 de143400b25bb1c8753d3d169342c23996de09d061639437916ff088ea6ea599 1875 
fortunate.app_3.1-2.dsc
 33608f15a0cb0d6c2ef8ebd687d730a5d814687a01f44cf3e7f4db89536bcf4c 4344 
fortunate.app_3.1-2.debian.tar.xz
 afcb6de3fff2b2adf0522d5c5b0942df8789ba2a36f72581cc24f8915a806ddb 5430 
fortunate.app_3.1-2_source.buildinfo
Files:
 0fbc6bb584baab50f3808cb0d1e49a57 1875 games optional fortunate.app_3.1-2.dsc
 4441225877ebe4244a765296a2792a50 4344 games optional 
fortunate.app_3.1-2.debian.tar.xz
 9771cee3398c516629c9dc6b65bf2977 5430 games optional 
fortunate.app_3.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlw9M6cACgkQweDZLphv
fH4nPA/+LSrpUedMr1tCj6ufWF6GwVpWJ5BqHL/+fd63Y0dD649mVLctDzv2zxre
znM81lUidqL7VhUJRGHIs+ZeyUwT2+ZSv8fSJWHTt+6cie+7lRC1I3PUlmY6bJVc
tnHB4pwpNm1awhxiSMjESajG3WgW62rVRcPwfN/W1hHWIhx34TzqQDdmW2DwQhzi
R/NFtt4gSl71toPI37chRmOXLA3QSXH4IkFjbCX/gdN5P/snZb1Dq+yKTxW//4CT
9kYpIvrfzqeEcx6Wa4B+IiKKfeWLqxUjPpMUW7T2cSBBZ+5kRAZADCLJRaDDaLe8
ub9D6tmxqxTjeZtCKsQ4IwMY4AmkqgKxRIt+Q3fBjvJ2TKPc13UQeCsH7UksiWws
1QlbqhKgicXAvxnpFc5h9+lPNxig+Z/7Vqftapf4TQSkLqR55RGhgq8eRZiRgqgG
kNMvcinzzw55VCLfJeD2fxKwur+htxiwTpmeSQJdbS5lSqs/NNK/NEl9RuLCkCpv
PSxpeMkNwY7lC4CdbQTZcu5T8R0kH6Yh6MG+epHwthdUr/Winm89GRz+fIktJRhK
1LPHOMTlSuI/beHOLBhil3RzXEOilJjkXKFxah5T6aOX9deDbL0G+rYD4+eHVQ0V
joMzECchF+hbOtETvmu5zuJohtGLaFrixAf+AOO1EPj12BL2avI=
=0nJ7
-END PGP SIGNATURE End Message ---

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

2019-01-14 Thread Celejar

On Mon, 14 Jan 2019 16:27:18 -0800
Jonathan Nieder  wrote:

> # missing Depends
> severity 919296 serious
> quit
> 
> Celejar wrote:
> >> Celejar wrote:
> 
> >>> Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per
> >>> README.debian) fails with:
> >>>
> >>> warning: git-daemon: unable to open supervise/ok: file does not exist
> [...]
> > ii  runit  2.1.2-22 amd64system-wide service supervision
> > ii  runit-helper   2.7.3all  dh-sysuser implementation 
> > detail
> > un  runit-init   (no description available)
> > un  runit-systemd(no description available)
> > un  runit-sysv   (no description available)
> >
> > I don't install recommends by default, and I do run into trouble
> > sometimes because of that ;). Should I try installing one of them to see
> > if that solves the problem?
> 
> Yes, please.  Please install runit-systemd and then run
> "dpkg-reconfigure git-daemon-run".

Okay, I've installed runit-systemd:

~# dpkg-reconfigure git-daemon-run
Service git-daemon already added.
warning: git-daemon: unable to open supervise/ok: file does not exist

> If I'm lucky then that will get it working.  I'll try to reproduce it
> here and set the right dependencies.

Sorry :/

Again, thanks for the help. I'm likely doing something basic wrong, so
thanks for bearing with me.

> It appears that runit-sysv depends on sysvinit-core, which conflicts
> with systemd-sysv, so adding a Depends by git-daemon-run on
> 'runit-init | runit-systemd | runit-sysv' should do the trick.  I'll
> experiment.
> 
> Thanks,
> Jonathan


Celejar

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

2019-01-14 Thread Different55

On Monday, January 14, 2019 10:37 AM, Ben Greear  
wrote:

> What is the model number of your home AP?
>
> Thanks,
> Ben

It is a Comtrend VR-3033

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

2019-01-14 Thread Jonathan Nieder

# missing Depends
severity 919296 serious
quit

Celejar wrote:
>> Celejar wrote:

>>> Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per
>>> README.debian) fails with:
>>>
>>> warning: git-daemon: unable to open supervise/ok: file does not exist
[...]
> ii  runit  2.1.2-22 amd64system-wide service supervision
> ii  runit-helper   2.7.3all  dh-sysuser implementation detail
> un  runit-init   (no description available)
> un  runit-systemd(no description available)
> un  runit-sysv   (no description available)
>
> I don't install recommends by default, and I do run into trouble
> sometimes because of that ;). Should I try installing one of them to see
> if that solves the problem?

Yes, please.  Please install runit-systemd and then run
"dpkg-reconfigure git-daemon-run".

If I'm lucky then that will get it working.  I'll try to reproduce it
here and set the right dependencies.

It appears that runit-sysv depends on sysvinit-core, which conflicts
with systemd-sysv, so adding a Depends by git-daemon-run on
'runit-init | runit-systemd | runit-sysv' should do the trick.  I'll
experiment.

Thanks,
Jonathan

Processed: Re: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

2019-01-14 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> # missing Depends
> severity 919296 serious
Bug #919296 [git-daemon-run] git-daemon-run: fails with 'warning: git-daemon: 
unable to open supervise/ok: file does not exist'
Severity set to 'serious' from 'grave'
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
919296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#919066: marked as done (xastir-data: missing Breaks+Replaces: xastir (<< 2.1.0-2))

2019-01-14 Thread Debian Bug Tracking System

Your message dated Tue, 15 Jan 2019 00:19:46 +
with message-id 
and subject line Bug#919066: fixed in xastir 2.1.0-3
has caused the Debian Bug report #919066,
regarding xastir-data: missing Breaks+Replaces: xastir (<< 2.1.0-2)
to be marked as done.

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


-- 
919066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xastir-data
Version: 2.1.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../xastir-data_2.1.0-2_amd64.deb ...
  Unpacking xastir-data (2.1.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/xastir-data_2.1.0-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/xastir/Counties/placeholder', which is also 
in package xastir 2.1.0-1+b1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/xastir-data_2.1.0-2_amd64.deb


cheers,

Andreas


xastir=2.1.0-1+b1_xastir-data=2.1.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: xastir
Source-Version: 2.1.0-3

We believe that the bug you reported is fixed in the latest version of
xastir, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dave Hibberd  (supplier of updated xastir package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 14 Jan 2019 23:41:09 +
Source: xastir
Binary: xastir xastir-data
Architecture: source amd64
Version: 2.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Dave Hibberd 
Description:
 xastir - X Amateur Station Tracking and Information Reporting
 xastir-data - X Amateur Station Tracking and Information Reporting
Closes: 919066
Changes:
 xastir (2.1.0-3) unstable; urgency=medium
 .
   * Added Breaks & Replaces to control file (Closes: #919066)
 - Thanks to Andreas Beckmann for catching this one
   * debhelper 12 migration
 - debian/control updated
 - debian/compat removed
   * removed blank directory /usr/lib/xastir
   * updated perl interpreter path in many scripts
 - debian/patches/interpreter-path.patch created
   * Added myself to debian/copyright
Checksums-Sha1:
 1ef33fad6cf226c58a738aa1cbac91adc17b8a93 2016 xastir_2.1.0-3.dsc
 f6e5c3c58868e45ab272e203c1f5154a31c81c58 19684 xastir_2.1.0-3.debian.tar.xz
 a93f6aef239d531a4da894e1165ea8ab90f6e98a 710404 xastir-data_2.1.0-3_amd64.deb
 50480fcaedb1c8e3d85493d7df60cce7671f4a61 1444840 
xastir-dbgsym_2.1.0-3_amd64.deb
 5edfbf49097a8956627c23e867303938326cc760 12847 xastir_2.1.0-3_amd64.buildinfo
 db56f2fed4faffdaf466d9bdcac87925baa04929 943184 xastir_2.1.0-3_amd64.deb
Checksums-Sha256:
 8e2407db094613eed02998528cc50ec27091e4c738e960cae215e76031a0bc02 2016 
xastir_2.1.0-3.dsc
 c74206a23a38ea3a5f1e55c2d0747b4d519ef4e3f8a20b4be54c0bf02dd7d443 19684 
xastir_2.1.0-3.debian.tar.xz
 ee324fe5edfcd3079d47a51242a3cde8ea1270688c5a3e12fb60fccb645eafc1 710404 
xastir-data_2.1.0-3_amd64.deb
 8041511a55ede53a4ddc57b61809b63651fecd679492f62ee84d5595e7d0d156 1444840 
xastir-dbgsym_2.1.0-3_amd64.deb
 434c9f64c327a04686903cba24b8c0560441d3ab5a913da38d13b32bdb1bf8c5 12847 
xastir_2.1.0-3_amd64.buildinfo
 adba3125ac378aaa0fe70d3b55be1c6d9a490ed61845474c9f31cc9309cbb26f 943184 
xastir_2.1.0-3_amd64.deb
Files:
 cf84086c6e055d0dca3f436b45f307cd 2016 hamradio optional xastir_2.1.0-3.dsc
 44db77fc232c000f7d2b627aaf762727 19684 hamradio optional 
xastir_2.1.0-3.debian.tar.xz
 bf4a5521487bde73c911feefd9842cd3 710404 hamradio optional 
xastir-data_2.1.0-3_amd64.deb

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

2019-01-14 Thread Celejar

On Mon, 14 Jan 2019 13:26:37 -0800
Jonathan Nieder  wrote:

> Hi again,
> 
> Celejar wrote:
> > Severity: grave
> >
> > Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per
> > README.debian) fails with:
> >
> > warning: git-daemon: unable to open supervise/ok: file does not exist
> [...]
> > Versions of packages git-daemon-run depends on:
> > ii  adduser  3.118
> > ii  git  1:2.20.1-1
> > ii  runit2.1.2-22
> 
> What is the output of "dpkg -l runit*"?  In particular, do you have
> runit-sysv or runit-systemd installed?

~# dpkg -l runit*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  runit  2.1.2-22 amd64system-wide service supervision
ii  runit-helper   2.7.3all  dh-sysuser implementation detail
un  runit-init   (no description available)
un  runit-systemd(no description available)
un  runit-sysv   (no description available)

I don't install recommends by default, and I do run into trouble
sometimes because of that ;). Should I try installing one of them to see
if that solves the problem?

Celejar

Bug#914565: libcap-ng 0.7.9-2

2019-01-14 Thread Dino Hüllmann

Hi,

I can confirm that the patched package has solved the problem and the bug no 
longer occurs.

Thanks to all involved,
Dino

Bug#919332: casparcg-server: FTBFS in sid (cannot find -lpthreads)

2019-01-14 Thread Santiago Vila

Sorry, I don't really know if it's a missing build-depends or not,
so I might better put the full build log here:

https://people.debian.org/~sanvila/build-logs/casparcg-server/

Thanks.

Bug#919333: schroedinger-coordgenlibs: FTBFS in sid (Can't exec "cmake": No such file or directory)

2019-01-14 Thread Santiago Vila

Package: src:schroedinger-coordgenlibs
Version: 1.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
install -d obj-x86_64-linux-gnu
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
Can't exec "cmake": No such file or directory at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 475.
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. failed to execute: No child 
processes
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. returned exit code 2
make: *** [debian/rules:8: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The above build was made in my autobuilder with "dpkg-buildpackage -B"
but it does also fail here:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#919332: casparcg-server: FTBFS in sid (cannot find -lpthreads)

2019-01-14 Thread Santiago Vila

Package: src:casparcg-server
Version: 2.2.0+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules build-arch
dh build-arch --sourcedirectory=src --buildsystem=cmake
   dh_update_autotools_config -a -O--sourcedirectory=src -O--buildsystem=cmake
   dh_autoreconf -a -O--sourcedirectory=src -O--buildsystem=cmake
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/casparcg-server-2.2.0+dfsg'
dh_auto_configure -- -DENABLE_HTML=OFF
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DENABLE_HTML=OFF ../src
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done

[... snipped ...]

./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
 undefined reference to `pthread_create'
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/cmTC_43642.dir/build.make:87: cmTC_43642] Error 1
make[3]: Leaving directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: *** [Makefile:121: cmTC_43642/fast] Error 2
make[2]: Leaving directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

File 
/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
/* */
#include 

int main(int argc, char** argv)
{
  (void)argv;
#ifndef pthread_create
  return ((int*)(_create))[argc];
#else
  (void)argc;
  return 0;
#endif
}

Determining if the function pthread_create exists in the pthreads failed with 
the following output:
Change Dir: 
/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_24c32/fast"
make[2]: Entering directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_24c32.dir/build.make 
CMakeFiles/cmTC_24c32.dir/build
make[3]: Entering directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_24c32.dir/CheckFunctionExists.c.o
/usr/bin/cc   -g -O2 
-fdebug-prefix-map=/<>/casparcg-server-2.2.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create   -o 
CMakeFiles/cmTC_24c32.dir/CheckFunctionExists.c.o   -c 
/usr/share/cmake-3.13/Modules/CheckFunctionExists.c
Linking C executable cmTC_24c32
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_24c32.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 
-fdebug-prefix-map=/<>/casparcg-server-2.2.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create  -Wl,-z,relro  
-rdynamic CMakeFiles/cmTC_24c32.dir/CheckFunctionExists.c.o  -o cmTC_24c32 
-lpthreads 
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/cmTC_24c32.dir/build.make:87: cmTC_24c32] Error 1
make[3]: Leaving directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: *** [Makefile:121: cmTC_24c32/fast] Error 2
make[2]: Leaving directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'


dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DENABLE_HTML=OFF ../src returned exit code 1
make[1]: *** [debian/rules:6: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>/casparcg-server-2.2.0+dfsg'
make: *** [debian/rules:3: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -B".
At the time of writing this, it has not been tested here yet:

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

but the error message suggests a missing build-dependency.

Thanks.

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

2019-01-14 Thread Michael Biebl

On Sat, 12 Jan 2019 14:54:09 +0100 Axel Beckert  wrote:

> I don't have local access to the affected machine for the weekend and
> hence won't be able to test reboots before Monday again, though.
> 
> I'm though also keen to know if a downgrade to udev 239 will make it
> more stable again, so I'll definitely test that.

Please make sure to also test 240-4

Regards,
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#901185: marked as done (exim4-config: fails to install)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 23:11:08 +
with message-id <20190114231108.ga25...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#901185: exim4-config: fails to install with bash 5 as 
/bin/sh
has caused the Debian Bug report #901185,
regarding exim4-config: fails to install
to be marked as done.

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

-- 
901185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exim4-config
Version: 4.91-5
Severity: grave
Justification: renders package unusable

apt-get -f install
Lecture des listes de paquets... Fait
Construction de l'arbre des dÃ©pendances   
Lecture des informations d'Ã©tat... Fait
0 mis Ã  jour, 0 nouvellement installÃ©s, 0 Ã  enlever et 2 non mis Ã  jour.
4 partiellement installÃ©s ou enlevÃ©s.
AprÃ¨s cette opÃ©ration, 0 o d'espace disque supplÃ©mentaires seront utilisÃ©s.
ParamÃ©trage de exim4-config (4.91-5) ...
/etc/exim4/update-exim4.conf.conf: ligne 32: dc_eximconfig_configtype : 
commande introuvable
/etc/exim4/update-exim4.conf.conf: ligne 32: dc_eximconfig_configtype : 
commande introuvable
dpkg: erreur de traitement du paquet exim4-config (--configure)Â :
 installed exim4-config package post-installation script subprocess returned 
error exit status 127
dpkg: des problÃ¨mes de dÃ©pendances empÃªchent la configuration de exim4-baseÂ 
:
 exim4-base dÃ©pend de exim4-config (>= 4.82) | exim4-config-2Â ; cependantÂ :
 Le paquet exim4-config n'est pas encore configurÃ©.
  Le paquet exim4-config-2 n'est pas installÃ©.
  Le paquet exim4-config qui fournit exim4-config-2 n'est pas encore configurÃ©.

dpkg: erreur de traitement du paquet exim4-base (--configure)Â :
 problÃ¨mes de dÃ©pendances - laissÃ© non configurÃ©
dpkg: des problÃ¨mes de dÃ©pendances empÃªchent la configuration de exim4Â :
 exim4 dÃ©pend de exim4-base (>= 4.91-5)Â ; cependantÂ :
 Le paquet exim4-base n'est pas encore configurÃ©.
 exim4 dÃ©pend de exim4-base (<< 4.91-5.1)Â ; cependantÂ :
 Le paquet exim4-base n'est pas encore configurÃ©.

-- Package-specific info:
Exim version 4.91 #4 built 09-Jun-2018 16:10:39
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DANE DKIM DNSSEC 
Event OCSP PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated

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

Kernel: Linux 4.14.48 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages exim4-config depends on:
ii  adduser3.117
ii  debconf [debconf-2.0]  1.5.66

exim4-config recommends no packages.

exim4-config suggests no packages.

-- Configuration Files:
/etc/exim4/passwd.client [Errno 13] Permission non accordÃ©e: 
'/etc/exim4/passwd.client'

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Version: 5.0~beta1-1

On Sun, 09 Dec 2018 at 15:53:48 +, Luca Boccassi wrote:
> FYI, this was fixed in bash 5.0 beta1:
> 
> $ ./bash --version
> GNU bash, version 5.0.0(1)-beta (x86_64-pc-linux-gnu)
> Copyright (C) 2018 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> 
> This is free software; you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> $ ./bash -o posix -c 'v=ok; v=bug read x  ok

I've checked that the reproducer from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901185#154 also gives
the same output when run with dash or with the recently-uploaded bash
5.0-1, so I think this bug can now be closed.

smcv--- End Message ---

Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

2019-01-14 Thread Florian Schlichting

On Mon, Jan 14, 2019 at 01:31:28PM -0800, Diane Trout wrote:
> I'm a little worried about just rm-ing previously invalid locations for
> configuration files. Might you have suggestions about how to safely
> clean up dnssec-triggers configuration file mess? (At the very least it
> seems like it should check that a configuration file was actually
> created by it before just deleting it)

Before thinking about cleanup, I'd start by making sure that fresh
installs don't re-create problems. At the moment, purging dnssec-trigger
leaves two keypairs in /etc; and when I rm them manually, and again
install dnssec-trigger, they're back (in addition to the identically
named pair in /etc/dnssec-trigger, which does get cleaned up on purge).
Does that not happen for you?

I think you can assume that files named /etc/dnssec_trigger_* belong to
your package. However I don't understand dnssec-trigger enough to judge
if these will always be autogenerated keys that are rendered obsolete by
the keys in /etc/dnssec-trigger, or if some sysadmin might have replaced
them with his own keys, for some reason. That is, if these are
"configuration files" or just "data" that could equally have been put
into /var/lib/dnssec-trigger for example...

Florian

Bug#919326: msmtp: account default not found: no configuration file available

2019-01-14 Thread Simon Deziel

Hi Sergio,

On 2019-01-14 5:40 p.m., Sergio Mendoza wrote:
>   A few days ago, msmtp fails to work.  It all seems to be related to the
> inability to read ~/.msmtprc file.  In other words it seems that
> ~/.msmtprc needs to have mode 644.  This is not at all desired since
> sensible (private) information can be included in that file. The package
> msmtp should run  with no trouble when the user configuration file
> ~/.msmtprc has mode 600.

Indeed, it should work with ~/.msmtprc with mode 0600. Is it working
when you have it set to 0644?

>   I am sending you some useful output so that you can check the relevance of 
> the
> situation (please note that I tried playing with stable, testing and sid
> versions of msmtp and I get the same output -this lead me to think whether
> the problem is with msmtp or with some other related package):
> 
> 
>>
> 
> sergio@quetzalli:~$ echo "Hello World" | msmtp -d ser...@mendozza.org
> ignoring system configuration file /etc/msmtprc: No such file or directory
> ignoring user configuration file /home/sergio/.msmtprc: Permission denied
> falling back to default account
> msmtp: account default not found: no configuration file available
> 
>
> 
>   As such, the bug leaves the package fully unusable.

That's unexpected but could be related to the Apparmor profile changes
that went in recently. Is /home/sergio/.msmtprc a symlink by any chance?
If yes, could you share the output of "ls -l /home/sergio/.msmtprc"?

Could you please also share the output of "dmesg | grep apparmor"

Thanks in advance,
Simon

Bug#918322: initramfs-tools: kernel fails to boot with "Gave up waiting for root file system device"

2019-01-14 Thread Michael Biebl

Am 14.01.19 um 19:45 schrieb Isaac Gelado:
> When I got the initramfs shell I also typed
> 
> udevadm trigger --type=subsystems --action=add
> udevadm trigger --type=devices --action=add
> 
> and tried to continue the boot process, but it failed. Then I typed
> 
> udevadm trigger --type=devices --action=add -v
> 
> and it booted nicely. Somehow, the `-v` flag is trigger some
> additional logic (maybe required to get what to print?) that makes the
> difference.

This issue is fixed in 240-4.
Please update to that version.


-- 
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#919326: msmtp: account default not found: no configuration file available

2019-01-14 Thread Sergio Mendoza

Dear Simon,

  Yes.  I have now checked and I have .msmtprc as a symlink.  If it is not
a symlink then I have no problems and everything runs smooth.  In any case
this is the output you asked for:

root@quetzalli:~# dmesg | grep apparmor | tail -n 20
[1064093.935900] audit: type=1400 audit(1547506649.916:130): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="torbrowser_tor" 
pid=14345 comm="apparmor_parser"
[1064094.438967] audit: type=1400 audit(1547506650.420:131): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=14346 comm="apparmor_parser"
[1064094.440476] audit: type=1400 audit(1547506650.420:132): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=14346 comm="apparmor_parser"
[1064094.461620] audit: type=1400 audit(1547506650.444:133): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/sbin/cupsd//third_party" pid=14346 comm="apparmor_parser"
[1064094.520228] audit: type=1400 audit(1547506650.500:134): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="torbrowser_firefox" 
pid=14343 comm="apparmor_parser"
[1064094.736714] audit: type=1400 audit(1547506650.716:135): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="system_tor" pid=14348 
comm="apparmor_parser"
[1064094.854220] audit: type=1400 audit(1547506650.836:136): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="libreoffice-oopslash" 
pid=14350 comm="apparmor_parser"
[1064094.936866] audit: type=1400 audit(1547506650.916:137): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="torbrowser_plugin_container" pid=14347 comm="apparmor_parser"
[1064095.090757] audit: type=1400 audit(1547506651.072:138): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/bin/man" pid=14351 
comm="apparmor_parser"
[1064095.091543] audit: type=1400 audit(1547506651.072:139): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="man_filter" pid=14351 
comm="apparmor_parser"
[1064102.892009] audit: type=1400 audit(1547506658.872:150): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/bin/evince" 
pid=14349 comm="apparmor_parser"
[1064102.910914] audit: type=1400 audit(1547506658.892:151): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/bin/evince//sanitized_helper" pid=14349 comm="apparmor_parser"
[1064102.914186] audit: type=1400 audit(1547506658.896:152): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/bin/evince-previewer" pid=14349 comm="apparmor_parser"
[1064102.930416] audit: type=1400 audit(1547506658.912:153): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/bin/evince-previewer//sanitized_helper" pid=14349 
comm="apparmor_parser"
[1064102.932260] audit: type=1400 audit(1547506658.912:154): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/bin/evince-thumbnailer" pid=14349 comm="apparmor_parser"
[1064111.250930] audit: type=1400 audit(1547506667.232:155): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="libreoffice-soffice" pid=14344 comm="apparmor_parser"
[1064111.253633] audit: type=1400 audit(1547506667.236:156): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="libreoffice-soffice//gpg" pid=14344 
comm="apparmor_parser"
[1064151.025521] audit: type=1400 audit(1547506707.004:157): apparmor="DENIED" 
operation="open" profile="/usr/bin/msmtp" name="/home/sergio/Private/.msmtprc" 
pid=14560 comm="msmtp" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
[1064177.994021] audit: type=1400 audit(1547506733.971:158): apparmor="DENIED" 
operation="open" profile="/usr/bin/msmtp" 
name="/home/sergio/mail/msmtp/log.txt" pid=14580 comm="msmtp" 
requested_mask="ac" denied_mask="ac" fsuid=1000 ouid=1000
[1064281.325901] audit: type=1400 audit(1547506837.302:159): apparmor="DENIED" 
operation="open" profile="/usr/bin/msmtp" 
name="/home/sergio/mail/msmtp/log.txt" pid=14656 comm="msmtp" 
requested_mask="ac" denied_mask="ac" fsuid=1000 ouid=1000


Cheers,

Sergio.





On Mon, Jan 14, 2019 at 05:59:31PM -0500, Simon Deziel wrote:
> Hi Sergio,
> 
> On 2019-01-14 5:40 p.m., Sergio Mendoza wrote:
> >   A few days ago, msmtp fails to work.  It all seems to be related to the
> > inability to read ~/.msmtprc file.  In other words it seems that
> > ~/.msmtprc needs to have mode 644.  This is not at all desired since
> > sensible (private) information can be included in that file. The package
> > msmtp should run  with no trouble when the user configuration file
> > ~/.msmtprc has mode 600.
> 
> Indeed, it should work with ~/.msmtprc with mode 0600. Is it working
> when you have it set to 0644?
> 
>

Bug#886133: marked as done (ndpi: FTBFS on mips, s390x, powerpc, and ppc64: tests time out)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 23:00:12 +
with message-id 
and subject line Bug#886133: fixed in ndpi 2.6-1
has caused the Debian Bug report #886133,
regarding ndpi: FTBFS on mips, s390x, powerpc, and ppc64: tests time out
to be marked as done.

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


-- 
886133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ndpi
Version: 2.2-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-m...@lists.debian.org
Usertags: mips

Builds of ndpi for mips, s390x, and the non-release architectures
powerpc and ppc64 all failed because running the test suite hit the
autobuilders' inactivity timeouts.  These timeouts are generous enough
(600 minutes on ppc64, 150 minutes on the other three architectures)
that hitting them generally indicates that something managed to hang
or spin indefinitely.  However, I see that the hppa build ran for a
long time before terminating on its own (albeit with test suite
errors), so you may simply need to add progress indicators for the
sake of slow architectures.  (These are inactivity timeouts, so any
output to stdout or stderr resets them.)

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: ndpi
Source-Version: 2.6-1

We believe that the bug you reported is fixed in the latest version of
ndpi, 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 886...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ludovico Cavedon  (supplier of updated ndpi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 Jan 2019 11:17:02 -0800
Source: ndpi
Binary: libndpi-dev libndpi2.6 libndpi-bin libndpi-wireshark
Architecture: source amd64
Version: 2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Ludovico Cavedon 
Changed-By: Ludovico Cavedon 
Description:
 libndpi-bin - extensible deep packet inspection library - ndpiReader
 libndpi-dev - extensible deep packet inspection library - development files
 libndpi-wireshark - extensible deep packet inspection library - wireshark 
dissector
 libndpi2.6 - extensible deep packet inspection library - shared library
Closes: 886133
Changes:
 ndpi (2.6-1) unstable; urgency=medium
 .
   [ Bernd Zeimetz ]
   * [e941738] Update upstream source from tag 'upstream/2.6'
 Update to upstream version '2.6'
 with Debian dir ebb088f5b1a1a88743e71021b4a9c252b397527e
 This will also hopefully fix all test issues.
 Closes: #886133
   * [a7ca26d] Removing patches as they don't apply anymore.
   * [52af6ea] Disable binary patches for tests
   * [61b7054] Install into /usr
   * [9a430fe] Add patch to fix prefix in Makefile.
   * [647cd1a] Fix and activate tests.
   * [65e0c54] Updating git info
   * [e54c89d] Updating symbols file.
   * [f0451ce] Add gitlab CI file.
   * [9a4a0f1] Disable tests which are broken on big endian.
   * [d58ddad] Disabling another test.
 .
   [ Ludovico Cavedon ]
   * Update changelog to snapshot entry.
   * Change SONAME and lib package name to include minory library version.
   * Use libwireshark-dev to determine wireshak plugin path.
   * Add define-have-json-c.patch to ensure ndpiReader is compiled with JSON
 support.
   * Link ndpiReader dynamically against libndpi and avoid lnking against
 unnecessary C++ libraries.
   * Stop adding libcache.h to -dev package.
   * Add DEP3 header to patches/fix-makefile-prefix.
   * Check DEB_BUILD_OPTIONS before running tests.
   * Update Standards-Version to 4.3.0.
   * Update debian/copyright for new upstream code.
   * Update changelog for snapshot upload.
Checksums-Sha1:
 c44514edf43aa9d5961dbb23a237d23139227f53 2088 ndpi_2.6-1.dsc
 dcf7f8b488b68d799d18169bc66954f88c95490f 18011656 ndpi_2.6.orig.tar.xz
 6b3cb0ee69c68b10caf144f430ae90a36cda5d2a 11640 ndpi_2.6-1.debian.tar.xz
 87ba99d49a4ade4419bac34a931eb2cdfacd71f2 99472

Bug#919326: msmtp: account default not found: no configuration file available

2019-01-14 Thread Sergio Mendoza

Package: msmtp
Version: 1.8.1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

  A few days ago, msmtp fails to work.  It all seems to be related to the
inability to read ~/.msmtprc file.  In other words it seems that
~/.msmtprc needs to have mode 644.  This is not at all desired since
sensible (private) information can be included in that file. The package
msmtp should run  with no trouble when the user configuration file
~/.msmtprc has mode 600.
  
  I am sending you some useful output so that you can check the relevance of the
situation (please note that I tried playing with stable, testing and sid
versions of msmtp and I get the same output -this lead me to think whether
the problem is with msmtp or with some other related package):


>

sergio@quetzalli:~$ echo "Hello World" | msmtp -d ser...@mendozza.org
ignoring system configuration file /etc/msmtprc: No such file or directory
ignoring user configuration file /home/sergio/.msmtprc: Permission denied
falling back to default account
msmtp: account default not found: no configuration file available



  As such, the bug leaves the package fully unusable.

Cheers,

Sergio.




-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.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:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages msmtp depends on:
ii  debconf [debconf-2.0]  1.5.69
ii  libc6  2.28-5
ii  libgnutls303.6.5-2
ii  libgsasl7  1.8.0-8+b2
ii  ucf3.0038+nmu1

Versions of packages msmtp recommends:
ii  ca-certificates  20180409

Versions of packages msmtp suggests:
pn  msmtp-mta  

-- debconf information:
  msmtp/sysconfig: false
  msmtp/port: 25
  msmtp/maildomain:
  msmtp/tls: false
  msmtp/auto_from: true
  msmtp/host:

Bug#918623: dizzy: Your vendor has not defined OpenGL macro GL_FRAMEBUFFER_EXT

2019-01-14 Thread Florian Schlichting

Hi Niko,

> >   $ dizzy
> >   GPU features: [x] GLSL [x] FBOs
> >   Your vendor has not defined OpenGL macro GL_FRAMEBUFFER_EXT, used at 
> > /usr/share/perl5/Dizzy/TextureGenerator.pm line 101.
> > 
> > I tested the same qemu VM with stretch and there it was working.
> > After some tests I found it stopped working when
> > libopengl-perl in version 0.7000+dfsg-1
> > entered testing in 2017-08-12.
> > But I am uncertain if the fault is
> > in package dizzy or libopengl-perl.
> 
> I looked at this a bit, and I assume it regressed with
> 
>   
> https://sourceforge.net/p/pogl/code/ci/ad3508bed030b856a8c36c4900727bbd838212dd/
> 
> If I read this correctly, the constants used to be provided
> unconditionally, but are now excluded if things like
> NO_GL_EXT_framebuffer_object are defined.
> 
> Now, our Debian packaging has
> 
>   
> https://sources.debian.org/src/libopengl-perl/0.7000+dfsg-1/debian/patches/add-gl_exclude.h/
> 
> which "adds back" these exclusions, apparently for xvfb compatibility and 
> making
> the build result independent of the build machine hardware.
> 
> My tentative conclusion is that the exclusions we patch in now affect things
> that they didn't earlier, and that we need to fix this on the libopengl-perl
> side somehow. So reassigning.
> 
> Copying Florian, who added the patch back in 2012. Any interest in looking
> at this? :)

well thanks for prodding me, I wouldn't have thought I ever touched
anything OpenGL and probably hadn't read your email otherwise.

When I started working on libopengl-perl in 2012, the update to upstream
version 0.66 was unfinished and the build would fail with an error about
a lacking gl_exclude.h; my idea was to just patch in the gl_exclude.h
that used to be part of the upstream tarball, without really
investigating its content, on the assumption that it would keep the
feature set unchanged.

Upstream's idea about gl_exclude.h is to determine the available GPU
features through probing, for which a 'glversion' binary is compiled and
run from Makefile.PL, preferably "under an X11 shell". My understanding
is that this proved impossible to reconcile with the way we build
packages on buildds, as they don't have GPUs and xvfb doesn't emulate
the relevant features either. Hence debian/patches/disable-glversion
disabled the probing, so when upstream stopped shipping gl_exclude.h,
there was nothing that created it.

I notice that the unpatched Makefile.PL has an option

dist=NO_EXCLUSIONS  Build with no OpenGL Extension exclusions

which will write a gl_exclude.h containing nothing but comments. This
seems aimed at Windows builds, but if I modify
debian/patches/add-gl_exclude.h so that it results in the same basically
empty header file, I can build a package that will run test.pl and
display the 3D graphics apparently without issues.

Do we need to exclude any OpenGL Extensions, at all?

I'd tend to think that there are so many different machines out there
that we would have heard from our users if gl_exclude.h really needed to
be tailored to the individual machine. Then again why would upstream
bother to exclude anything in the first place?

It's probably a bit late in the release cycle to "just find out" by
uploading a -2 with that modified patch.

Hmmm...

Florian

Bug#919322: CVE-2019-6245 CVE-2019-6247

2019-01-14 Thread Moritz Muehlenhoff

Source: agg
Severity: grave

Please see
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6245
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6247

Given that the package isn't exactly fast-moving, how about
revisiting #377270 for buster? Right now we need to coordinate
rebuilds against the fixed agg...

Cheers,
Moritz

Bug#919298: Bug #919298 in libreoffice marked as pending

2019-01-14 Thread Rene Engelhard

Control: tag -1 pending

Hello,

Bug #919298 in libreoffice reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/65b2860d13611b1823ccc5619cfc2385a84ca37e


debian/libreoffice-mysql-connector.maintscript: remove 
$DPKG_MAINTSCRIPT_PACKAGE (closes: #919298)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919298

Bug#919321: CVE-2019-6246

2019-01-14 Thread Moritz Muehlenhoff

Source: svgpp
Severity: grave
Tags: security

Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6246

It will also be affected by CVE-2019-6247 and CVE-2019-6245, as agg
doesn't provide a shared library...

So make sure to add a versioned build-deps on the fixed agg when
that's done.

Cheers,
Moritz

Processed: Bug #919298 in libreoffice marked as pending

2019-01-14 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #919298 [libreoffice-mysql-connector] libreoffice-mysql-connector: fails to 
upgrade from sid: dpkg-maintscript-helper errors out
Added tag(s) pending.

-- 
919298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#919228: marked as done (wrong Recommends:)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 21:51:27 +
with message-id 
and subject line Bug#919228: fixed in toil 3.18.0-2
has caused the Debian Bug report #919228,
regarding wrong Recommends:
to be marked as done.

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


-- 
919228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: toil
Version: 3.18.0-1
Severity: serious
thanks

Package toil Recommends: python3-futures which is not available. So this 
package might not be installable on some systems.

Did you mean python3-future?

  Thorsten
--- End Message ---
--- Begin Message ---
Source: toil
Source-Version: 3.18.0-2

We believe that the bug you reported is fixed in the latest version of
toil, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated toil package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Jan 2019 23:25:16 -0800
Source: toil
Binary: toil
Architecture: source
Version: 3.18.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Description:
 toil   - cross-platform workflow engine
Closes: 919228
Changes:
 toil (3.18.0-2) unstable; urgency=medium
 .
   * Remove errant recommend on python3-futures and depends on python3-pytest*
 (Closes: #919228)
   * Refined the package description, added 'Provides: cwl-runner'
   * Remove the partial mesos support until python3-mesos is packaged
   * Suggests: docker.io | singularity-container | docker-ce
   * Added debian/TODO, updated debian/README.{debian,source}
   * Add basic smoke test ( `toil* --help` ) as an AutoPkgTest
Checksums-Sha1:
 65acde1bb2b49179012086dd5eb1a72d8d4f1794 2117 toil_3.18.0-2.dsc
 886cfe0e0e65cfaf24e3d05f4373e899dfd5ba63 16896 toil_3.18.0-2.debian.tar.xz
 7b0d53f8181d17da74d20fb120e994ac7d22cb09 8606 toil_3.18.0-2_source.buildinfo
Checksums-Sha256:
 086df24eb5eb709883084c39d5325911216ab5e0ade89cdf4abfd10fc2c48fad 2117 
toil_3.18.0-2.dsc
 0ac4f6ee514b7ce0935f30aba97de77829e03bba66ef28c579327296c7123224 16896 
toil_3.18.0-2.debian.tar.xz
 fd54721c44762ea914467fc303a1679b6a49c02196da370748346493e3a1579f 8606 
toil_3.18.0-2_source.buildinfo
Files:
 45ede30e5b6aeffb49d5c66050e34437 2117 net optional toil_3.18.0-2.dsc
 af928d26132caf83c8b4dbe204839ec8 16896 net optional toil_3.18.0-2.debian.tar.xz
 f02c6c52cdd748d5fe0aa3ce5aded500 8606 net optional 
toil_3.18.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAlw8/T4ACgkQPCZ2P2xn
5uKWSRAAgeCm+GQpIVAhHSe8pgybJf5tW/AAETE+2nETCvPYLEW3Ysc8uAEimsAn
0ffztMdNpn3ZHuwfFtpREy/dkzo7EstcyUMLV8pTbv30PWn8Z/nAnWahSzVvHT/y
lGBFiIOkNnKCl44o5YWt0RA/c/TwX7BCyShxGtxIMhV9wj83dDqR0IvHrWoOra6V
CG7VIArKUMfXm5WqtS9S+jiAwi9gjLRTVnOZLRnu0OQc3cPb2Y0qcVfC/WqJHQKe
5ECRLFFGblMjWPZExWZn67hLoaUf0jurUObVBQ4cEoNu+/m/cprEdceIjLtEP9Vl
1P53VSPrzxlUx3N6O0ZxUOc6oMShrGLdrwPEUOywO4mqH25Fh9XA7eRuIobw3rZo
2Zg5eKMGkuBfkycfYF5kQRhWR96DbRxQSPh6eMK8xpAvI4vke+4YJcH7FTuXbw7J
1/Usc/vPk88R23MvfS5DBuQLrzODg+2ChiLIGEPqAp0VVqN9w9pUA2ikHnwR7iCu
yiV4Rxg4sjHjZre3JoCQ7YEwdhXW2fOHEjNO9T9LwrHiXcJo0LpAsc9iEyXmaZ26
M8KjdV/jLyEcBpxXGLVweUMbQWSETLxoa46ASHqeKlC7pfp9rYWBEhaOaob4ztPE
r4Y9iRGLml0As27x1JhI4K36BmDqCzaOh09MwtIPOpAaqK0bxsQ=
=Pl9l
-END PGP SIGNATURE End Message ---

Bug#899530: marked as done (gnome-phone-manager: Invalid maintainer address pkg-bluetooth-maintain...@lists.alioth.debian.org)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 21:49:34 +
with message-id 
and subject line Bug#899530: fixed in gnome-phone-manager 0.69-2.1
has caused the Debian Bug report #899530,
regarding gnome-phone-manager: Invalid maintainer address 
pkg-bluetooth-maintain...@lists.alioth.debian.org
to be marked as done.

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


-- 
899530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnome-phone-manager
Version: 0.69-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of gnome-phone-manager,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package gnome-phone-manager since the list address
pkg-bluetooth-maintain...@lists.alioth.debian.org used in the
Maintainer: field was not transferred to the alioth-lists service that
provides a continuation for the lists in the @lists.alioth.debian.org
domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-bluetooth-maintain...@lists.alioth.debian.org is 7.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gnome-phone-manager
Source-Version: 0.69-2.1

We believe that the bug you reported is fixed in the latest version of
gnome-phone-manager, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gnome-phone-manager package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Jan 2019 23:05:31 +0200
Source: gnome-phone-manager
Binary: gnome-phone-manager
Architecture: source
Version: 0.69-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Bluetooth Maintainers 
Changed-By: Adrian Bunk 
Description:
 gnome-phone-manager - control aspects of your mobile phone from your GNOME 2 
desktop
Closes: 899530
Changes:
 gnome-phone-manager (0.69-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update Maintainer: to the new address. (Closes: #899530)
Checksums-Sha1:
 b681cf0db0e1688467fff1a6521015f97fd70390 2442 gnome-phone-manager_0.69-2.1.dsc
 672b58d37ef962e59b82f422212f9d93d7ee230e 10472 
gnome-phone-manager_0.69-2.1.debian.tar.xz
Checksums-Sha256:
 2d5bfb69102932f201c9c94989c4a8204d9c129fc9ebd39b5c7b7e055125f58a 2442 
gnome-phone-manager_0.69-2.1.dsc
 3fff9e2a242960fba389d5dd8bb89fea22bf4bc39c2ec1ec547257cdb01362c6 10472 
gnome-phone-manager_0.69-2.1.debian.tar.xz
Files:
 118ae1fb9b4563c0bb4322ac33f10c01 2442 gnome extra 
gnome-phone-manager_0.69-2.1.dsc
 845979a15b680610ea951c97579ceed7 10472 gnome extra 
gnome-phone-manager_0.69-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#875696: marked as done (courier-mlm: unsubstituted @piddir@ in /etc/courier/webmlmrc: "PORT=@piddir@/webmlm")

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 21:34:50 +
with message-id 
and subject line Bug#875696: fixed in courier 1.0.5-1
has caused the Debian Bug report #875696,
regarding courier-mlm: unsubstituted @piddir@ in /etc/courier/webmlmrc: 
"PORT=@piddir@/webmlm"
to be marked as done.

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


-- 
875696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: courier-mlm
Version: 0.76.3-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,


courier-mlm failed to install using the command:
  apt install courier-mlm

Errors below:

A instalar courier-mlm (0.76.3-5) ...
Created symlink
/etc/systemd/system/multi-user.target.wants/courier-mlm.service →
/lib/systemd/system/courier-mlm.service.
Job for courier-mlm.service failed because the control process exited
with error code.
See "systemctl status courier-mlm.service" and "journalctl -xe" for
details.
invoke-rc.d: initscript courier-mlm, action "start" failed.
● courier-mlm.service - Courier MLM Daemon
   Loaded: loaded (/lib/systemd/system/courier-mlm.service; enabled;
vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2017-09-13 18:16:10
WEST; 10ms ago
  Process: 19036 ExecStart=/usr/bin/webmlmd start /etc/courier/webmlmrc
(code=exited, status=1/FAILURE)

set 13 18:16:10 myhost systemd[1]: Starting Courier MLM Daemon...
set 13 18:16:10 myhost webmlmd[19036]: @piddir@/webmlm: No such
file or directory
set 13 18:16:10 myhost systemd[1]: courier-mlm.service: Control
process exited, code=exited status=1
set 13 18:16:10 myhost systemd[1]: Failed to start Courier MLM
Daemon.
set 13 18:16:10 myhost systemd[1]: courier-mlm.service: Unit
entered failed state.
set 13 18:16:10 myhost systemd[1]: courier-mlm.service: Failed
with result 'exit-code'.
dpkg: erro ao processar o pacote courier-mlm (--configure):
 subprocesso script post-installation instalado retornou erro do status
de saída 1
A processar 'triggers' para systemd (232-25+deb9u1) ...
Foram encontrados erros enquanto processava:
 courier-mlm
E: Sub-process /usr/bin/dpkg returned an error code (1)


I don't think it's relevant, but I'm running postfix for MTA



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

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

Versions of packages courier-mlm depends on:
ii  courier-base 0.76.3-5
ii  init-system-helpers  1.48
ii  libc62.24-11+deb9u1
ii  libcourier-unicode1  1.4-3+b1
ii  libgcc1  1:6.3.0-18
ii  libgdbm3 1.8.3-14
ii  libidn11 1.33-1
ii  libstdc++6   6.3.0-18
ii  maildrop 2.8.4-2
ii  sysvinit-utils   2.88dsf-59.9

courier-mlm recommends no packages.

Versions of packages courier-mlm suggests:
ii  courier-doc  0.76.3-5

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: courier
Source-Version: 1.0.5-1

We believe that the bug you reported is fixed in the latest version of
courier, 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 875...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Wanner  (supplier of updated courier package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 Jan 2019 20:32:48 +0100
Source: courier
Binary: courier-base courier-mlm courier-mta courier-faxmail courier-webadmin 
sqwebmail courier-pcp courier-pop courier-imap courier-ldap courier-doc
Architecture: source
Version: 1.0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Markus Wanner 
Changed-By: Markus Wanner 
Description:
 courier-base - Courier mail server - base system
 courier-doc - Courier mail server - additional documentation
 courier-faxmail - Courier mail server - Fax<->mail gateway
 courier-imap - Courier mail server - IMAP server
 courier-ldap - Courier mail

Bug#881696: marked as done (courier: Please include /usr/lib/courier/courier/courierfilter in courier-mta)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 21:34:51 +
with message-id 
and subject line Bug#881696: fixed in courier 1.0.5-1
has caused the Debian Bug report #881696,
regarding courier: Please include /usr/lib/courier/courier/courierfilter in 
courier-mta
to be marked as done.

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


-- 
881696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: courier
Version: 0.78.0-2
Severity: grave
Tags: patch
Justification: renders package unusable
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Hi Markus,

In Ubuntu, we discovered that the courier-mta package fails to install
because the courierfilter systemd unit cannot work:

Setting up courier-mta (0.78.0-2) ...
Job for courierfilter.service failed because the control process exited with 
error code.
See "systemctl status courierfilter.service" and "journalctl -xe" for details.
invoke-rc.d: initscript courierfilter, action "start" failed.
ESC[0;1;31m●ESC[0m courierfilter.service - Courier Filter Daemon
   Loaded: loaded (/lib/systemd/system/courierfilter.service; disabled; vendor 
preset: enabled)
   Active: ESC[0;1;31mfailedESC[0m (Result: exit-code) since Tue 2017-10-31 
18:25:07 UTC; 17ms ago
  Process: 4043 ExecStart=/usr/sbin/courierfilter start 
ESC[0;1;31m(code=exited, status=127)ESC[0m

Oct 31 18:25:07 autopkgtest systemd[1]: Starting Courier Filter Daemon...
Oct 31 18:25:07 autopkgtest courierfilter[4043]: /bin/sh: 1: 
/usr/lib/courier/courier/courierfilter: not found
Oct 31 18:25:07 autopkgtest systemd[1]: ESC[0;1;39mcourierfilter.service: 
Control process exited, code=exited status=127ESC[0m

It is surprising to me that this problem has not been reported in Debian,
but I can't see any way that this would work in Debian any better than in
Ubuntu, so I'm filing this bug as 'grave'.

Please find attached a one-liner patch to add the missing file to the
courier-mta binary package.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru courier-0.78.0/debian/courier-mta.install 
courier-0.78.0/debian/courier-mta.install
--- courier-0.78.0/debian/courier-mta.install   2017-09-12 04:49:46.0 
-0700
+++ courier-0.78.0/debian/courier-mta.install   2017-11-13 21:54:14.0 
-0800
@@ -34,6 +34,7 @@
 usr/lib/courier/courier/aliascombine
 usr/lib/courier/courier/aliascreate
 usr/lib/courier/courier/courierd
+usr/lib/courier/courier/courierfilter
 usr/lib/courier/courier/modules/dsn/courierdsn
 usr/lib/courier/courier/modules/esmtp/courieresmtp
 usr/lib/courier/courier/modules/esmtp/courieresmtpd
--- End Message ---
--- Begin Message ---
Source: courier
Source-Version: 1.0.5-1

We believe that the bug you reported is fixed in the latest version of
courier, 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 881...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Wanner  (supplier of updated courier package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 Jan 2019 20:32:48 +0100
Source: courier
Binary: courier-base courier-mlm courier-mta courier-faxmail courier-webadmin 
sqwebmail courier-pcp courier-pop courier-imap courier-ldap courier-doc
Architecture: source
Version: 1.0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Markus Wanner 
Changed-By: Markus Wanner 
Description:
 courier-base - Courier mail server - base system
 courier-doc - Courier mail server - additional documentation
 courier-faxmail - Courier mail server - Fax<->mail gateway
 courier-imap - Courier mail server - IMAP server
 courier-ldap - Courier mail server - LDAP support
 courier-mlm - Courier mail server - mailing list manager
 courier-mta - Courier mail server - ESMTP daemon
 courier-pcp - Courier mail server - PCP server
 courier-pop - Courier mail server - POP3 server
 courier-webadmin -

Bug#910525: marked as done (courier-webadmin is dependent on CGI.pm)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 21:34:51 +
with message-id 
and subject line Bug#910525: fixed in courier 1.0.5-1
has caused the Debian Bug report #910525,
regarding courier-webadmin is dependent on CGI.pm
to be marked as done.

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


-- 
910525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: courier-webadmin
Version: 0.76.3-5
Severity: important

Dear Maintainer,

   * What led up to the situation?

courier-webadmin will not work if CGI.pm is not installed.




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

Kernel: Linux 4.9.0-7-amd64 (SMP w/1 CPU core)
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 courier-webadmin depends on:
ii  apache2 [httpd]2.4.25-3+deb9u5
ii  courier-base   0.76.3-5
ii  debconf [debconf-2.0]  1.5.61
ii  libc6  2.24-11+deb9u3

courier-webadmin recommends no packages.

Versions of packages courier-webadmin suggests:
pn  courier-doc  

-- debconf information:
* courier-webadmin/install-cgi: true
--- End Message ---
--- Begin Message ---
Source: courier
Source-Version: 1.0.5-1

We believe that the bug you reported is fixed in the latest version of
courier, 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 910...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Wanner  (supplier of updated courier package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 Jan 2019 20:32:48 +0100
Source: courier
Binary: courier-base courier-mlm courier-mta courier-faxmail courier-webadmin 
sqwebmail courier-pcp courier-pop courier-imap courier-ldap courier-doc
Architecture: source
Version: 1.0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Markus Wanner 
Changed-By: Markus Wanner 
Description:
 courier-base - Courier mail server - base system
 courier-doc - Courier mail server - additional documentation
 courier-faxmail - Courier mail server - Fax<->mail gateway
 courier-imap - Courier mail server - IMAP server
 courier-ldap - Courier mail server - LDAP support
 courier-mlm - Courier mail server - mailing list manager
 courier-mta - Courier mail server - ESMTP daemon
 courier-pcp - Courier mail server - PCP server
 courier-pop - Courier mail server - POP3 server
 courier-webadmin - Courier mail server - web-based administration frontend
 sqwebmail  - Courier mail server - webmail server
Closes: 875696 879530 881696 910525
Changes:
 courier (1.0.5-1) unstable; urgency=medium
 .
   [ Markus Wanner ]
   * New upstream release 1.0.5.
   * Update and correct debian/copyright, use https links.
   * Refresh patches 0002, 0010, 0012, 0015, 0016, 0019, 0022, 0023,
 and 0024.
   * Extend patch 0018-Fix-default-configuration-for-Debian.patch with
 the piddir addition proposed by Willi Mann. Closes: #875696.
   * d/control: tighten dependency on courier-unicode, eliminate obsolete
 build dependencies dh-autoreconf, autotools-dev and dh-systemd.
   * Bump debian/compat to 11.
   * Bump S-V to 4.2.1.
   * d/rules: drop `--with autotools-dev` and `--with systemd`, use
 dh_installsystemd, instead.
   * Drop patch 0025-Use-SOURCE_DATE_EPOCH.., it got applied upstream.
   * Drop lintian overrides: possible-gpl-code-linked-with-openssl is
 no longer required, since courier is built against gnutls.  And
 package-contains-empty-directory does not apply anymore.
   * Add Vcs-Git and Vcs-Browser links to the new salsa project.
   * Update d/watch to version 4, use https.
   * courier-mta: include binary courierfilter. Closes: #881696.
   * courier-mta.NEWS: correct tab to spaces.
   * courier-webadmin: Add dependency on libcgi-pm-perl. Closes: #910525.
   * courier-webadmin: Correct ownership and permissions on
 /etc/courier/webadmin/password (mode 0600, courier owned).
   * sqwebmail: provide a

Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

2019-01-14 Thread Diane Trout

On Mon, 2019-01-14 at 21:25 +0100, Florian Schlichting wrote:
> Hi,
> 
> in the course of looking into the upgrade failure, I ended up purging
> dnssec-trigger and then installed it again. I notice this creates
> keys
> and config files in both /etc/ and /etc/dnssec-trigger?! Different to
> Alex, I get traceback in the middle of the log (also for subsequent
> attempts to 'apt-get install -f' etc):

... I thought I had fixed that... But apparently I had just found a few
other places that had hardcoded paths that weren't being updated.

Apparently there are still more hardcoded paths.

I'm a little worried about just rm-ing previously invalid locations for
configuration files. Might you have suggestions about how to safely
clean up dnssec-triggers configuration file mess? (At the very least it
seems like it should check that a configuration file was actually
created by it before just deleting it)

Diane

Bug#784479: [kde4libs] Qt4's WebKit removal

2019-01-14 Thread Adrian Bunk

On Mon, Jan 14, 2019 at 06:22:52AM -0500, Scott Kitterman wrote:
> 
> That patch no longer seems to be available, so I made my own.  Patches for 
> kde4libs and kde-runtime attached.  I looked at the KDE4 packages still in 
> Buster and I don't believe this interferes with anything.  This also fixes 
> the 
> FTBFS with Samba 4.9 by dropping the KDE4 kio_smb.
> 
> I think we should move forward on these (or some improved version if someone 
> has suggestions).
> 
> Even though there are separate bugs for kde-runtime, since the patch for it 
> was already discussed in this bug, I thought we might as well keep them 
> together.

What is actually the overall plan for KDE4 in buster now?

A year ago I was told that only qtwebkit should be removed at that 
point, and the rest of KDE4 later for buster.

Someone else told me they were planning to do it after updating
all KDE packages to the latest release.

No matter what advice I followed someone was yelling at me,
so I gave up working on that.

Looking at kde-runtime in buster:

# Broken Depends:
basket: basket
kaccessible: kaccessible
kamerka: kamerka
kcollectd: kcollectd
kdbg: kdbg
kdiff3: kdiff3
keurocalc: keurocalc
kmetronome: kmetronome
kmidimon: kmidimon
kmldonkey: kmldonkey
knutclient: knutclient
kopete: kopete
kover: kover
kppp: kppp
kprinter4: kprinter4
kradio4: kradio4
kredentials: kredentials
kremotecontrol: kremotecontrol
kscd: kscd
kvpnc: kvpnc
syncevolution: syncevolution-libs-kde

Making the bugs in these packages RC (some packages like kdbg or 
kmetronome already have Qt5 versions that someone might upload to
unstable) plus an upload of kopete from experimental to unstable,
that's what would be needed for complete removal of kde-runtime.

Complete removal of kde4libs would add another list of comparable size,
with no obvious blocker.

> Scott K

cu
Adrian

--

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

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

2019-01-14 Thread Jonathan Nieder

Hi again,

Celejar wrote:
> Severity: grave
>
> Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per
> README.debian) fails with:
>
> warning: git-daemon: unable to open supervise/ok: file does not exist
[...]
> Versions of packages git-daemon-run depends on:
> ii  adduser  3.118
> ii  git  1:2.20.1-1
> ii  runit2.1.2-22

What is the output of "dpkg -l runit*"?  In particular, do you have
runit-sysv or runit-systemd installed?

Thanks,
Jonathan

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

2019-01-14 Thread Jonathan Nieder

Hi,

Celejar wrote:

> Severity: grave
>
> Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per
> README.debian) fails with:
>
> warning: git-daemon: unable to open supervise/ok: file does not exist
>
> I see that there's an old, archived bug about this:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570094
>
> But I'm getting the same thing on my uptodate Sid system (and even on
> another Sid system with the version of the package from experimental
> installed).
>
> I know nothing about runit, so perhaps I'm doing something obvious
> wrong, but I'm just trying to follow the directions from the README, and
> getting this.

Thanks for reporting.  I'm cc-ing Debian's runit maintainers, who may
be able to help us track this down.

I haven't tried reproducing this yet, but I will try soon (some time
this week).

Sincerely,
Jonathan

Processed: Re: Bug#919217: Acknowledgement (Missing dependency on devscripts)

2019-01-14 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 +patch
Bug #919217 [lintian-brush] Missing dependency on devscripts
Added tag(s) patch.

-- 
919217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#919217: Acknowledgement (Missing dependency on devscripts)

2019-01-14 Thread Jeroen Dekkers

Control: tag -1 +patch

https://salsa.debian.org/jelmer/lintian-brush/merge_requests/1

Processed: user debian...@lists.debian.org, found 903762 in 7.14.2+dfsg-1exp2, fixed 904118 in 0.7~20161228-1 ...

2019-01-14 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> found 903762 7.14.2+dfsg-1exp2
Bug #903762 [boinc-server-maker] boinc-server-maker: fails to install: 
SyntaxError in /usr/lib/boinc-server-maker/sched/pymw_assimilator.py
Marked as found in versions boinc/7.14.2+dfsg-1exp2.
> fixed 904118 0.7~20161228-1
Bug #904118 [arriero] arriero: arriero.moo fails to import
Marked as fixed in versions arriero/0.7~20161228-1.
> usertags 918408 piuparts
There were no usertags set.
Usertags are now: piuparts.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903762
904118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904118
918408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#916941: marked as done (libvncserver: Multiple security vulnerabilities)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 20:49:14 +
with message-id 
and subject line Bug#916941: fixed in libvncserver 0.9.11+dfsg-1.2
has caused the Debian Bug report #916941,
regarding libvncserver: Multiple security vulnerabilities
to be marked as done.

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


-- 
916941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvncserver
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for libvncserver.

CVE-2018-15126[0]:
| LibVNC before commit 73cb96fec028a576a5a24417b57723b55854ad7b contains
| heap use-after-free vulnerability in server code of file transfer
| extension that can result remote code execution

CVE-2018-15127[1]:
| LibVNC before commit 502821828ed00b4a2c4bef90683d0fd88ce495de contains
| heap out-of-bound write vulnerability in server code of file transfer
| extension that can result remote code execution

CVE-2018-20019[2]:
| LibVNC before commit a83439b9fbe0f03c48eb94ed05729cb016f8b72f contains
| multiple heap out-of-bound write vulnerabilities in VNC client code
| that can result remote code execution

CVE-2018-20020[3]:
| LibVNC before commit 7b1ef0ffc4815cab9a96c7278394152bdc89dc4d contains
| heap out-of-bound write vulnerability inside structure in VNC client
| code that can result remote code execution

CVE-2018-20021[4]:
| LibVNC before commit c3115350eb8bb635d0fdb4dbbb0d0541f38ed19c contains
| a CWE-835: Infinite loop vulnerability in VNC client code.
| Vulnerability allows attacker to consume excessive amount of resources
| like CPU and RAM

CVE-2018-20022[5]:
| LibVNC before 2f5b2ad1c6c99b1ac6482c95844a84d66bb52838 contains
| multiple weaknesses CWE-665: Improper Initialization vulnerability in
| VNC client code that allows attacker to read stack memory and can be
| abuse for information disclosure. Combined with another vulnerability,
| it can be used to leak stack memory layout and in bypassing ASLR

CVE-2018-20023[6]:
| LibVNC before 8b06f835e259652b0ff026898014fc7297ade858 contains
| CWE-665: Improper Initialization vulnerability in VNC Repeater client
| code that allows attacker to read stack memory and can be abuse for
| information disclosure. Combined with another vulnerability, it can be
| used to leak stack memory layout and in bypassing ASLR

CVE-2018-20024[7]:
| LibVNC before commit 4a21bbd097ef7c44bb000c3bd0907f96a10e4ce7 contains
| null pointer dereference in VNC client code that can result DoS.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-15126
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15126
[1] https://security-tracker.debian.org/tracker/CVE-2018-15127
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15127
[2] https://security-tracker.debian.org/tracker/CVE-2018-20019
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20019
[3] https://security-tracker.debian.org/tracker/CVE-2018-20020
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20020
[4] https://security-tracker.debian.org/tracker/CVE-2018-20021
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20021
[5] https://security-tracker.debian.org/tracker/CVE-2018-20022
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20022
[6] https://security-tracker.debian.org/tracker/CVE-2018-20023
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20023
[7] https://security-tracker.debian.org/tracker/CVE-2018-20024
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20024

Please adjust the affected versions in the BTS as needed.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libvncserver
Source-Version: 0.9.11+dfsg-1.2

We believe that the bug you reported is fixed in the latest version of
libvncserver, 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 916...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated libvncserver 
package)

(This message was generated automatically at their request; if you
believe

Bug#892403: starpu-contrib: build-depends on GCC 6

2019-01-14 Thread Samuel Thibault

Control: tags -1 + pending

Andreas Beckmann, le lun. 14 janv. 2019 17:44:01 +0100, a ecrit:
> On 2019-01-10 01:10, Samuel Thibault wrote:
> > Andreas Beckmann, le jeu. 10 janv. 2019 01:02:19 +0100, a ecrit:
> >> I successfully built the package with the attached patch that switched
> >> to GCC 7, but since the build system is a bit special, I'm not going to
> >> upload this myself.
> > 
> > I'll handle it once CUDA 9.2 is uploaded, yes. Thanks for checking that
> > it'll build.
> 
> CUDA 9.2 is now in a good shape in sid.

Good, uploaded, thanks!

Samuel

Processed: Re: Bug#892403: starpu-contrib: build-depends on GCC 6

2019-01-14 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + pending
Bug #892403 {Done: Samuel Thibault } [src:starpu-contrib] 
starpu-contrib: build-depends on GCC 6
Added tag(s) pending.

-- 
892403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#916468: dune: /usr/bin/dune is already provided by the whitedune package

2019-01-14 Thread Paul Gevers

Hi whitedune maintainers,

On Mon, 7 Jan 2019 14:00:45 +0100 =?UTF-8?Q?St=c3=a9phane_Glondu?=
 wrote:
> reassign 916468 whitedune 0.30.10-2.1
> thanks
> 
> Le 14/12/2018 à 20:24, Andreas Beckmann a écrit :
> > automatic installation tests of packages that share a file and at the
> > same time do not conflict by their package dependency relationships has
> > detected the following problem:
> > 
> >   Selecting previously unselected package dune.
> >   Preparing to unpack .../dune_1.6.2-1_amd64.deb ...
> >   Unpacking dune (1.6.2-1) ...
> >   dpkg: error processing archive 
> > /var/cache/apt/archives/dune_1.6.2-1_amd64.deb (--unpack):
> >trying to overwrite '/usr/bin/dune', which is also in package whitedune 
> > 0.30.10-2.1+b2
> >   Errors were encountered while processing:
> >/var/cache/apt/archives/dune_1.6.2-1_amd64.deb
> > 
> > 
> > This is a serious bug as it makes installation fail, and violates
> > sections 7.6.1 and 10.1 of the policy. An optimal solution would
> > consist in only one of the packages installing that file, and renaming
> > or removing the file in the other package. Depending on the
> > circumstances you might also consider Replace relations or file
> > diversions. If the conflicting situation cannot be resolved then, as a
> > last resort, the two packages have to declare a mutual
> > Conflict. Please take into account that Replaces, Conflicts and
> > diversions should only be used when packages provide different
> > implementations for the same functionality.
> > 
> > Here is a list of files that are known to be shared by both packages
> > (according to the Contents file for sid/amd64, which may be
> > slightly out of sync):
> > 
> >   usr/bin/dune
> >   usr/share/man/man1/dune.1.gz
> 
> As discussed on debian-devel, I propose that the whitedune package drops
>  /usr/bin/dune, which is a symlink to whitedune.

Is anybody against dropping the symlink? If not, I can prepare an upload
to fix this RC bug. This bug affecting my package view3dscene, because I
use whitedunes files in its tests. I could drop the dependency but I'd
rather not.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

2019-01-14 Thread Axel Beckert

Hi Diane,

Diane Trout wrote:
> Was dnssec-triggerd running before the upgrade?

I think so.

> Was there then an
> upgrade to openssl 1.1.1? and then finally it wouldn't start?

That one was much earlier IIRC, like weeks ago.

Anyway, I've now got a second machine with the same symptoms, just now
with sysvinit instead of systemd:

Setting up dnssec-trigger (0.17+repack-1) ...
Installing new version of config file 
/etc/NetworkManager/dispatcher.d/01-dnssec-trigger ...

Configuration file '/etc/dnssec-trigger/dnssec-trigger.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** dnssec-trigger.conf (Y/I/N/O/D/Z) [default=N] ? d
--- /etc/dnssec-trigger/dnssec-trigger.conf 2017-01-15 19:10:09.588308480 
+0100
+++ /etc/dnssec-trigger/dnssec-trigger.conf.dpkg-new2019-01-13 
22:10:28.0 +0100
@@ -22,12 +22,10 @@

 # the domain example.com line (if any) to add to resolv.conf(5). default none.
 # domain: ""
-domain: deuxchevaux.org

 # domain name search path to add to resolv.conf(5). default none.
 # the search path from DHCP is not picked up, it could be used to misdirect.
 # search: ""
-search: kub.deuxchevaux.org deuxchevaux.org noone.org debian.org ethz.ch 
lugs.ch

 # the command to run to open login pages on hot spots, a web browser.
 # empty string runs no command.
@@ -50,7 +48,7 @@
 # control-cert-file: "/etc/dnssec-trigger/dnssec_trigger_control.pem"

 # check for updates, download and ask to install them (for Windows, OSX).
-# check-updates:
+# check-updates: no

 # webservers that are probed to see if internet access is possible.
 # They serve a simple static page over HTTP port 80.  It probes a random url:
@@ -65,6 +63,7 @@
 url: "http://fedoraproject.org/static/hotspot.txt OK"

 # fallback open DNSSEC resolvers that run on TCP port 80 and TCP port 443.
+# These relay incoming DNS traffic on the other port numbers to the usual DNS
 # the ssl443 adds an ssl server IP, you may also specify one or more hashes
 # the following on one line: ssl443:{}
 # hash is output of openssl x509 -sha256 -fingerprint -in server.pem
@@ -77,3 +76,12 @@
 ssl443: 185.49.140.67 
7E:CF:B4:BE:B9:9A:56:0D:F7:3B:40:51:A4:78:E6:A6:FD:66:0F:10:58:DC:A8:2E:C0:43:D4:77:5A:71:8A:CF
 ssl443: 2a04:b900::10:0:0:67 
7E:CF:B4:BE:B9:9A:56:0D:F7:3B:40:51:A4:78:E6:A6:FD:66:0F:10:58:DC:A8:2E:C0:43:D4:77:5A:71:8A:CF

+# Use VPN servers for all traffic
+# use-vpn-forwarders: no
+
+# Forward RFC 1918 private addresses to global forwarders
+# use-private-addresses: yes
+
+# Add domains provided by VPN connections into Unbound forward zones
+# add-wifi-provided-zones: no
+

Configuration file '/etc/dnssec-trigger/dnssec-trigger.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** dnssec-trigger.conf (Y/I/N/O/D/Z) [default=N] ? n
[] Restarting : dnssec-triggerdJan 14 21:10:59 dnssec-triggerd[12444] 
error: Error for server-cert-file: /etc/dnssec-trigger/dnssec_trigger_server.pem
Jan 14 21:10:59 dnssec-triggerd[12444] error: Error in SSL_CTX 
use_certificate_file crypto error:140AB18F:SSL 
routines:SSL_CTX_use_certificate:ee key too small
Jan 14 21:10:59 dnssec-triggerd[12444] error: cannot setup SSL context
Jan 14 21:10:59 dnssec-triggerd[12444] fatal error: could not init server
 failed!

On this machine, OpenSSL 1.1.1 was installed in August 2018, i.e.
about half a year ago.

> The error message looks like your openssl keys are too small and all
> attempts to control dnssec-triggerd will fail. I modified dnssec-
> trigger-control-setup to check the key size and delete it if it was too
> small. Did the certificates in /etc/dnssec-trigger get regenerated?

Clearly not. They're from 2016 (on the second machine, the other one
is currently sleeping in my backpack):

/etc/dnssec-trigger # ls -l
total 36
-rw-r--r-- 1 root root 3115 Jan 15  2017 dnssec-trigger.conf
-rw-r--r-- 1 root root 3338 Jan 13 22:10 dnssec-trigger.conf.dpkg-dist
-rw-r--r-- 1 root root 3095 Oct  4  2016 dnssec-trigger.conf~
-rw-r--r-- 1 root root 4640 Dec 20  2016 dnssec.conf
-rw-r--r-- 1 root root 1277 May 28  2016 dnssec_trigger_control.key
-rw-r--r-- 1 root root  822 May 28  2016 dnssec_trigger_control.pem
-rw-r- 1 root root 1277 May 28  2016 dnssec_trigger_server.key

Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

2019-01-14 Thread Florian Schlichting

Hi,

in the course of looking into the upgrade failure, I ended up purging
dnssec-trigger and then installed it again. I notice this creates keys
and config files in both /etc/ and /etc/dnssec-trigger?! Different to
Alex, I get traceback in the middle of the log (also for subsequent
attempts to 'apt-get install -f' etc):

Jan 14 20:51:32 thinkpad systemd[1]: Starting Generate keys and certificates 
for dnssec-trigger...
Jan 14 20:51:32 thinkpad dnssec-trigger-control-setup[6806]: setup in directory 
/etc
Jan 14 20:51:32 thinkpad dnssec-trigger-control-setup[6806]: generating 
dnssec_trigger_server.key
Jan 14 20:51:32 thinkpad dnssec-trigger-control-setup[6806]: Generating RSA 
private key, 3072 bit long modulus (2 primes)
Jan 14 20:51:32 thinkpad dnssec-trigger-control-setup[6806]: 
.
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: 
..
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: e is 65537 
(0x010001)
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: generating 
dnssec_trigger_control.key
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: Generating RSA 
private key, 3072 bit long modulus (2 primes)
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: ...
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: 
.
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: e is 65537 
(0x010001)
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: create 
dnssec_trigger_server.pem (self signed certificate)
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: create 
dnssec_trigger_control.pem (signed client certificate)
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: Signature ok
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: subject=CN = 
dnssec-trigger-control
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: Getting CA Private 
Key
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: Setup success. 
Certificates created.
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: run this script 
again with -i to:
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: #011- enable 
remote-control in unbound.conf
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: #011- start 
unbound-control-setup
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: #011- add root 
trust anchor to unbound.conf
Jan 14 20:51:33 thinkpad dnssec-trigger-control-setup[6806]: if you have not 
done this already
Jan 14 20:51:33 thinkpad systemd[1]: Started Generate keys and certificates for 
dnssec-trigger.
Jan 14 20:51:33 thinkpad systemd[1]: Starting Reconfigure local DNSSEC resolver 
on connectivity changes...
Jan 14 20:51:33 thinkpad dnssec-trigger-script[6819]: Backing up 
/etc/resolv.conf as /run/dnssec-trigger/resolv.conf.backup...
Jan 14 20:51:33 thinkpad dnssec-triggerd: [6822] info: dnssec-trigger 0.17 start
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]: Traceback (most recent call 
last):
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]:   File 
"/usr/lib/dnssec-trigger/dnssec-trigger-script", line 774, in 
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]: main()
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]:   File 
"/usr/lib/dnssec-trigger/dnssec-trigger-script", line 761, in main
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]: Application(sys.argv).run()
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]:   File 
"/usr/lib/dnssec-trigger/dnssec-trigger-script", line 472, in run
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]: self.method()
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]:   File 
"/usr/lib/dnssec-trigger/dnssec-trigger-script", line 556, in run_setup
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]: 
self._unbound_set_negative_cache_ttl(UNBOUND_MAX_NEG_CACHE_TTL)
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]:   File 
"/usr/lib/dnssec-trigger/dnssec-trigger-script", line 641, in 
_unbound_set_negative_cache_ttl
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]: subprocess.check_call(CMD, 
stdout=DEVNULL, stderr=DEVNULL)
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]:   File 
"/usr/lib/python3.7/subprocess.py", line 347, in check_call
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]: raise 
CalledProcessError(retcode, cmd)
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]: subprocess.CalledProcessError: 
Command '['unbound-control', 'set_option', 'cache-max-negative-ttl:', '5']' 
returned non-zero exit status 1.
Jan 14 20:51:34 thinkpad dnssec-triggerd[6822]: chattr: Datei oder Verzeichnis 
nicht gefunden beim Auslesen des Status von /etc/resolv.conf
Jan 14 20:51:34

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

2019-01-14 Thread Ben Greear


On 1/13/19 9:40 AM, Different55 wrote:

Hi! I'm running Debian Sid and recently upgraded wpasupplicant to 2.7. After 
the upgrade finished, NetworkManager popped up saying that the connection to my 
home Wifi failed. I was able to connect to my phone's hotspot still. I attached 
a relevant bit of a log from journalctl.

I also tried Debian's experimental package "2:2.7+git20190108+11ce7a1-1," that 
had the same issue. I didn't have this issue after downgrading to 2.6. According to lshw, 
my wireless adapter is an Intel Wireless 3165.

Let me know if there's anything else I can do to help!

Thanks,
Diff


What is the model number of your home AP?

Thanks,
Ben

--
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com

Bug#919310: kdiff3: ships documentation already in kdiff3-doc

2019-01-14 Thread Andreas Beckmann

Package: kdiff3
Version: 1.7.90-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + kdiff3-doc

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package kdiff3-doc.
  Preparing to unpack .../kdiff3-doc_1.7.90-1_all.deb ...
  Unpacking kdiff3-doc (1.7.90-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kdiff3-doc_1.7.90-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/HTML/en/kdiff3/dirbrowser.png', which is 
also in package kdiff3 1.7.90-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/kdiff3-doc_1.7.90-1_all.deb

To ensure smooth upgrades from the buggy kdiff3 package, kdiff3-doc
should get appropriate Breaks+Replaces.

These files are currently shipped by both packages:

  usr/share/doc/HTML/en/kdiff3/dirbrowser.png
  usr/share/doc/HTML/en/kdiff3/dirmergebig.png
  usr/share/doc/HTML/en/kdiff3/index.cache.bz2
  usr/share/doc/HTML/en/kdiff3/index.docbook
  usr/share/doc/HTML/en/kdiff3/iteminfo.png
  usr/share/doc/HTML/en/kdiff3/letter_by_letter.png
  usr/share/doc/HTML/en/kdiff3/merge_current.png
  usr/share/doc/HTML/en/kdiff3/new.png
  usr/share/doc/HTML/en/kdiff3/open_dialog.png
  usr/share/doc/HTML/en/kdiff3/screenshot_diff.png
  usr/share/doc/HTML/en/kdiff3/screenshot_merge.png
  usr/share/doc/HTML/en/kdiff3/triple_diff.png
  usr/share/doc/HTML/en/kdiff3/white_space.png
  usr/share/doc/kdiff3-doc/html/credits.html
  usr/share/doc/kdiff3-doc/html/dirmerge.html
  usr/share/doc/kdiff3-doc/html/dirmergeoptions.html
  usr/share/doc/kdiff3-doc/html/dirmergevisible.html
  usr/share/doc/kdiff3-doc/html/documentation.html
  usr/share/doc/kdiff3-doc/html/dothemerge.html
  usr/share/doc/kdiff3-doc/html/faq.html
  usr/share/doc/kdiff3-doc/html/features.html
  usr/share/doc/kdiff3-doc/html/find.html
  usr/share/doc/kdiff3-doc/html/git.html
  usr/share/doc/kdiff3-doc/html/index.docbook
  usr/share/doc/kdiff3-doc/html/index.html
  usr/share/doc/kdiff3-doc/html/interpretinginformation.html
  usr/share/doc/kdiff3-doc/html/introduction.html
  usr/share/doc/kdiff3-doc/html/kpart.html
  usr/share/doc/kdiff3-doc/html/merging.html
  usr/share/doc/kdiff3-doc/html/misc.html
  usr/share/doc/kdiff3-doc/html/navigation.html
  usr/share/doc/kdiff3-doc/html/opendialog.html
  usr/share/doc/kdiff3-doc/html/options.html
  usr/share/doc/kdiff3-doc/html/other.html
  usr/share/doc/kdiff3-doc/html/pasteinput.html
  usr/share/doc/kdiff3-doc/html/preprocessors.html
  usr/share/doc/kdiff3-doc/html/printing.html
  usr/share/doc/kdiff3-doc/html/saving.html
  usr/share/doc/kdiff3-doc/html/screenshots.html
  usr/share/doc/kdiff3-doc/html/selections.html
  usr/share/doc/kdiff3-doc/html/startingdirmerge.html


cheers,

Andreas


kdiff3=1.7.90-1_kdiff3-doc=1.7.90-1.log.gz
Description: application/gzip

Processed: kdiff3: ships documentation already in kdiff3-doc

2019-01-14 Thread Debian Bug Tracking System

Processing control commands:

> affects -1 + kdiff3-doc
Bug #919310 [kdiff3] kdiff3: ships documentation already in kdiff3-doc
Added indication that 919310 affects kdiff3-doc

-- 
919310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#919307: casacore-data: Depends: casacore-data-jplde but it is not installable

2019-01-14 Thread Adrian Bunk

Package: casacore-data
Version: 1.1
Severity: serious

The following packages have unmet dependencies:
 casacore-data : Depends: casacore-data-jplde but it is not installable


src:casacore-data-jplde builds casacore-data-jpl-de200
and casacore-data-jpl-de405 but no casacore-data-jplde
binary package.

Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

2019-01-14 Thread Diane Trout

On Mon, 2019-01-14 at 14:35 +0100, Axel Beckert wrote:
> Hi,
> 
> Axel Beckert wrote:
> > The syslog shows again this:
> > 
> > Jan 14 07:18:59 c-cactus2 dnssec-triggerd[22039]: Jan 14 07:18:59
> > dnssec-triggerd[22039] error: Error in SSL_CTX use_certificate_file
> > crypto error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key
> > too small
> 
> Attached the output of "fgrep dnssec /var/log/syslog" from the time
> of
> the package upgrade.
> 
>   Regards, Axel

Was dnssec-triggerd running before the upgrade? Was there then an
upgrade to openssl 1.1.1? and then finally it wouldn't start?

The error message looks like your openssl keys are too small and all
attempts to control dnssec-triggerd will fail. I modified dnssec-
trigger-control-setup to check the key size and delete it if it was too
small. Did the certificates in /etc/dnssec-trigger get regenerated?

See dnssec-trigger/debian/patches/remove-small-keys.patch for the
implementation.

Diane

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

Bug#919301: gitaly: fails to upgrade from 'sid': Could not find gem 'gitaly-proto (~> 1.3)'

2019-01-14 Thread Andreas Beckmann

Package: gitaly
Version: 1.12.0+debian-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../gitaly_1.12.0+debian-1_amd64.deb ...
  Unpacking gitaly (1.12.0+debian-1) over (0.129.0+debian-3) ...
  Setting up gitaly (1.12.0+debian-1) ...
  [ESC][31mCould not find gem 'gitaly-proto (~> 1.3)' in any of the gem sources 
listed in
  your Gemfile.[ESC][0m
  dpkg: error processing package gitaly (--configure):
   installed gitaly package post-installation script subprocess returned error 
exit status 7
  Errors were encountered while processing:
   gitaly


cheers,

Andreas


gitaly_1.12.0+debian-1.log.gz
Description: application/gzip

Bug#918322: initramfs-tools: kernel fails to boot with "Gave up waiting for root file system device"

2019-01-14 Thread Isaac Gelado

When I got the initramfs shell I also typed

udevadm trigger --type=subsystems --action=add
udevadm trigger --type=devices --action=add

and tried to continue the boot process, but it failed. Then I typed

udevadm trigger --type=devices --action=add -v

and it booted nicely. Somehow, the `-v` flag is trigger some
additional logic (maybe required to get what to print?) that makes the
difference.

Cheers!

On Mon, Jan 14, 2019 at 10:41 AM Isaac Gelado  wrote:
>
> Sorry for the late reply. I could not reboot my machine until today.
>
> I added a sleep 5 and it didn’t work.
>
> On Tue, Jan 8, 2019 at 9:15 AM Michael Biebl  wrote:
>>
>> Am 08.01.19 um 18:11 schrieb Isaac Gelado:
>> > As a side hint that might be helpful. I had two kernels 4.18 and 4.19
>> > in my system. This problem started when I first boot 4.19, while I was
>> > able to boot 4.18 without problems. At some point I decided to do an
>> > `update-initramfs -k all -u` and the problem started to also happen
>> > when booting 4.18. I do not understand why when upgrading udev/systemd
>> > from 239-15 to 240-2 the trigger only updated the iniramfs for 4.19.
>>
>> This is expected. udev's postinst runs "update-initramfs -u" which only
>> updates the initramfs of the currently active kernel, not for all of them.
>> For that, as you already mentioned, you need to pass "-k all"
>>
>> Regards,
>> Michael
>>
>> --
>> Why is it that all of the instruments seeking intelligent life in the
>> universe are pointed away from Earth?
>>

Processed: Re: Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

2019-01-14 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> found 919001 47.0+dfsg-6
Bug #919001 [emacspeak] emacspeak: fails to upgrade with emacs 1.26.1+1-3
Marked as found in versions emacspeak/47.0+dfsg-6.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
919001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

2019-01-14 Thread Paul Gevers

HI,

On 13-01-2019 22:49, Pavel Kreuzt wrote:
> It's emacspeak-47.0+dfsg-6

I think I understand the issue. Will upload shortly.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#919298: libreoffice-mysql-connector: fails to upgrade from sid: dpkg-maintscript-helper errors out

2019-01-14 Thread Andreas Beckmann

Package: libreoffice-mysql-connector
Version: 1:6.2.0~rc2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../7-libreoffice-mysql-connector_1%3a6.2.0~rc2-1_all.deb 
...
  dpkg-query: no packages found matching $DPKG_MAINTSCRIPT_PACKAGE
  dpkg-query: error: --listfiles needs a valid package name but 
'$DPKG_MAINTSCRIPT_PACKAGE' is not: illegal package name in specifier 
'$DPKG_MAINTSCRIPT_PACKAGE': must start with an alphanumeric character
  
  Use --help for help about querying packages.
  dpkg-maintscript-helper: error: file 
'/usr/share/doc/libreoffice-mysql-connector' not owned by package 
'$DPKG_MAINTSCRIPT_PACKAGE'
  dpkg-query: error: --listfiles needs a valid package name but 
'$DPKG_MAINTSCRIPT_PACKAGE' is not: illegal package name in specifier 
'$DPKG_MAINTSCRIPT_PACKAGE': must start with an alphanumeric character
  
  Use --help for help about querying packages.
  dpkg-maintscript-helper: error: file 
'/usr/share/doc/libreoffice-mysql-connector/copyright' not owned by package 
'$DPKG_MAINTSCRIPT_PACKAGE'
  dpkg-query: error: --listfiles needs a valid package name but 
'$DPKG_MAINTSCRIPT_PACKAGE' is not: illegal package name in specifier 
'$DPKG_MAINTSCRIPT_PACKAGE': must start with an alphanumeric character
  
  Use --help for help about querying packages.
  dpkg-maintscript-helper: error: file 
'/usr/share/doc/libreoffice-mysql-connector/changelog.Debian.gz' not owned by 
package '$DPKG_MAINTSCRIPT_PACKAGE'
  dpkg-query: error: --listfiles needs a valid package name but 
'$DPKG_MAINTSCRIPT_PACKAGE' is not: illegal package name in specifier 
'$DPKG_MAINTSCRIPT_PACKAGE': must start with an alphanumeric character
  
  Use --help for help about querying packages.
  dpkg-maintscript-helper: error: file 
'/usr/share/doc/libreoffice-mysql-connector/changelog.Debian.amd64.gz' not 
owned by package '$DPKG_MAINTSCRIPT_PACKAGE'
  dpkg-maintscript-helper: error: directory 
'/usr/share/doc/libreoffice-mysql-connector' contains files not owned by 
package $DPKG_MAINTSCRIPT_PACKAGE, cannot switch to symlink
  dpkg: error processing archive 
/tmp/apt-dpkg-install-w3OdOs/7-libreoffice-mysql-connector_1%3a6.2.0~rc2-1_all.deb
 (--unpack):
   new libreoffice-mysql-connector package pre-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-w3OdOs/7-libreoffice-mysql-connector_1%3a6.2.0~rc2-1_all.deb


Without looking at the code I'd suspect you have a redundant
  $DPKG_MAINTSCRIPT_PACKAGE
in libreoffice-mysql-connector.maintscript. Current debhelper compat
levels properly escape the '$' character.


cheers,

Andreas


libreoffice-mysql-connector_1:6.2.0~rc2-1.log.gz
Description: application/gzip

Bug#892403: starpu-contrib: build-depends on GCC 6

2019-01-14 Thread Andreas Beckmann

On 2019-01-10 01:10, Samuel Thibault wrote:
> Andreas Beckmann, le jeu. 10 janv. 2019 01:02:19 +0100, a ecrit:
>> I successfully built the package with the attached patch that switched
>> to GCC 7, but since the build system is a bit special, I'm not going to
>> upload this myself.
> 
> I'll handle it once CUDA 9.2 is uploaded, yes. Thanks for checking that
> it'll build.

CUDA 9.2 is now in a good shape in sid.

Andreas

Bug#899696: marked as done (svrcore: Invalid maintainer address pkg-fedora-ds-maintain...@lists.alioth.debian.org)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 17:55:31 +
with message-id 
and subject line Bug#915510: Removed package(s) from unstable
has caused the Debian Bug report #899696,
regarding svrcore: Invalid maintainer address 
pkg-fedora-ds-maintain...@lists.alioth.debian.org
to be marked as done.

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


-- 
899696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:svrcore
Version: 1:4.1.2+dfsg1-3
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of svrcore,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package svrcore since the list address
pkg-fedora-ds-maintain...@lists.alioth.debian.org used in the
Maintainer: field was not transferred to the alioth-lists service that
provides a continuation for the lists in the @lists.alioth.debian.org
domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-fedora-ds-maintain...@lists.alioth.debian.org is 10.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1:4.1.2+dfsg1-3+rm

Dear submitter,

as the package svrcore has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/915510

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#918261: marked as done (ruby-bcat: Depends: ruby-rack (< 2.0) but 2.0.6-2 is to be installed)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 17:59:19 +
with message-id 
and subject line Bug#919248: Removed package(s) from unstable
has caused the Debian Bug report #918261,
regarding ruby-bcat: Depends: ruby-rack (< 2.0) but 2.0.6-2 is to be installed
to be marked as done.

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


-- 
918261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-bcat
Version: 0.6.2-8
Severity: serious

The following packages have unmet dependencies:
 ruby-bcat : Depends: ruby-rack (< 2.0) but 2.0.6-2 is to be installed
--- End Message ---
--- Begin Message ---
Version: 0.6.2-8+rm

Dear submitter,

as the package ruby-bcat has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/919248

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#915353: marked as done (vdr-plugin-skinenigmang FTBFS due to using freetype-config that was removed in Debian)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 17:41:46 +
with message-id 
and subject line Bug#915353: fixed in vdr-plugin-skinenigmang 
0.1.2+git20180128-2.1
has caused the Debian Bug report #915353,
regarding vdr-plugin-skinenigmang FTBFS due to using freetype-config that was 
removed in Debian
to be marked as done.

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


-- 
915353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-skinenigmang
Version: 0.1.2+git20180128-2
Severity: serious
Tags: ftbfs patch

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-skinenigmang.html

...
In file included from config.h:20,
 from skinenigmang.c:9:
font.h:16:10: error: #include expects "FILENAME" or 
 #include FT_FREETYPE_H
  ^


Fix attached.
Description: freetype-config was removed in Debian, switch to pkg-config
Author: Adrian Bunk 

--- vdr-plugin-skinenigmang-0.1.2+git20180128.orig/Makefile
+++ vdr-plugin-skinenigmang-0.1.2+git20180128/Makefile
@@ -138,9 +138,9 @@ INCLUDES += $(shell pkg-config --cflags
 endif
 endif
 
-ifneq ($(shell which freetype-config),)
-   INCLUDES += $(shell freetype-config --cflags)
-   LIBS += $(shell freetype-config --libs)
+ifneq ($(shell which pkg-config),)
+   INCLUDES += $(shell pkg-config --cflags freetype2)
+   LIBS += $(shell pkg-config --libs freetype2)
 else
INCLUDES += -I/usr/include/freetype -I/usr/local/include/freetype
LIBS += -lfreetype
--- End Message ---
--- Begin Message ---
Source: vdr-plugin-skinenigmang
Source-Version: 0.1.2+git20180128-2.1

We believe that the bug you reported is fixed in the latest version of
vdr-plugin-skinenigmang, 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 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated vdr-plugin-skinenigmang 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Dec 2018 18:17:16 +0200
Source: vdr-plugin-skinenigmang
Binary: vdr-plugin-skinenigmang
Architecture: source
Version: 0.1.2+git20180128-2.1
Distribution: unstable
Urgency: low
Maintainer: Debian VDR Team 
Changed-By: Adrian Bunk 
Description:
 vdr-plugin-skinenigmang - Skin plugin for VDR
Closes: 915353
Changes:
 vdr-plugin-skinenigmang (0.1.2+git20180128-2.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix FTBFS without freetype-config. (Closes: #915353)
Checksums-Sha1:
 c93cbe7d9674c5742b060faca2990b2add9ad68c 2272 
vdr-plugin-skinenigmang_0.1.2+git20180128-2.1.dsc
 26ea9e25ad7b80f1c2c850beb5ad78a7bae0177c 4712 
vdr-plugin-skinenigmang_0.1.2+git20180128-2.1.debian.tar.xz
Checksums-Sha256:
 88d3bdeeac87b829d434d3a1fc21dbe6fcd4d3cc579186c1002faf88c003f124 2272 
vdr-plugin-skinenigmang_0.1.2+git20180128-2.1.dsc
 f57eae0abfc9c9f5a8bab1fb65d1340aa0f9643e9b16a2f6deeaea5a608421e6 4712 
vdr-plugin-skinenigmang_0.1.2+git20180128-2.1.debian.tar.xz
Files:
 1cb5c90745f930066a9020c6ad7749f8 2272 video optional 
vdr-plugin-skinenigmang_0.1.2+git20180128-2.1.dsc
 f07ed31281bd4736a0b609929d29dee1 4712 video optional 
vdr-plugin-skinenigmang_0.1.2+git20180128-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlwqQhAACgkQiNJCh6LY
mLFoUxAAoenMOa30/FAnxqYrYyZlcs4uLvxbXB9owuND8tWrjNrwclgqBzNXx63+
gwsP+eMhpw3CFel8fytXLo/j7wAqH2K6G2PnNNiJ+ulzKTJlRzggkre53KJpiklY
gvmC8kvaK9mHJ/S/4XjbRdHKobmoGUrKmAU3mYgee6glFdvnqboy/gkjgXQjpKwO
P8bGG0QjXafw6xl6PXTPQ5cFWuyohoChQnOF016diatIJT6vT5UbfDVuaNDSnhCV
HqjBss9vRieGRzPedt56TyaeI/PnfJfHLawWTzzxwxd/lVxcnK1l0FTwJEXnJw30
3SHUF1zV3VNWfnVDxZ4q2JsJZpa9mOgzQrRAq2ZiRO70it7GHQE/4b6tI33GB+Dp
NtZZmG3VvbdkYgMQVpRNXVv+NpMfbO2KH4v8/ZR5mr7Hcp0HNMWSkV5LSU77E1+c
ew8b1GuqYJoNuO0/haczNUWIzW8nQ+7z9n9FTdVy/8u/V1KVJqOVxHECdHh18Vic
J/ylhlQVAxiG+CP2JFg7g6zKurqKTx78KM/hPDer/PCJqNsuKrCO1LhBRET/MXg7
bsHDU5sizDzgDZci0UDOk2owH8qjtGLiYkP3exBXFytMgc4Q2nbL96ub/gymhFB8
y65Un+R/i3dFKeJXWc6+4eSrD5W0XmHkhAKn4XNnIj5B5g2K/f8=
=dLGy
-END PGP SIGNATURE End Message ---

Bug#892403: marked as done (starpu-contrib: build-depends on GCC 6)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 17:41:40 +
with message-id 
and subject line Bug#892403: fixed in starpu-contrib 1.2.6+dfsg-5
has caused the Debian Bug report #892403,
regarding starpu-contrib: build-depends on GCC 6
to be marked as done.

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


-- 
892403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: starpu-contrib
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm

Hi,

starpu-contrib build-depends on GCC 6. We now have GCC 7 (default)
and GCC 8 in the archive, so please make your package build with a
newer compiler (preferably the default one) again, since we'd like to
remove GCC 6 from testing before the buster release.

Cheers, Emilio 
--- End Message ---
--- Begin Message ---
Source: starpu-contrib
Source-Version: 1.2.6+dfsg-5

We believe that the bug you reported is fixed in the latest version of
starpu-contrib, 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 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated starpu-contrib 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 Jan 2019 17:52:08 +0100
Source: starpu-contrib
Binary: libstarpu-contrib-dev libstarpu-contrib-1.2-5 
libstarpu-contribfft-1.2-0 libstarpu-contribmpi-1.2-3 starpu-contrib-tools 
starpu-contrib-examples libsocl-contrib-1.2-0
Architecture: source amd64
Version: 1.2.6+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 libsocl-contrib-1.2-0 - Task scheduler for heterogeneous multicore machines
 libstarpu-contrib-1.2-5 - Task scheduler for heterogeneous multicore machines
 libstarpu-contrib-dev - Task scheduler for heterogeneous multicore machines - 
dev
 libstarpu-contribfft-1.2-0 - Task scheduler for heterogeneous multicore 
machines
 libstarpu-contribmpi-1.2-3 - Task scheduler for heterogeneous multicore 
machines
 starpu-contrib-examples - Task scheduler for heterogeneous multicore machines 
- exs
 starpu-contrib-tools - Task scheduler for heterogeneous multicore machines - 
tools
Closes: 892403
Changes:
 starpu-contrib (1.2.6+dfsg-5) unstable; urgency=medium
 .
   [ Andreas Beckmann ]
   * Build with CUDA 9.2 and GCC 7.  (Closes: #892403).
Checksums-Sha1:
 618d7363403ae3ef4b3ffd18def4d279ccfff64b 3174 starpu-contrib_1.2.6+dfsg-5.dsc
 cf5c852d9f4f309098704a7d17890501574931a3 13208 
starpu-contrib_1.2.6+dfsg-5.debian.tar.xz
 75f7ba36bfb46a65612c8103a6a98007e1f8d617 243420 
libsocl-contrib-1.2-0-dbgsym_1.2.6+dfsg-5_amd64.deb
 bc3045ff31d3e031355048fc02f1571e288724ac 46944 
libsocl-contrib-1.2-0_1.2.6+dfsg-5_amd64.deb
 148eb58859fd3415cd42f06f57158dad4de4b037 2428184 
libstarpu-contrib-1.2-5-dbgsym_1.2.6+dfsg-5_amd64.deb
 c50cbb6e166a84b65e08a80ad678ca08e31ae896 386756 
libstarpu-contrib-1.2-5_1.2.6+dfsg-5_amd64.deb
 c6d32a90eefdb01466b94abb55a32df11f253282 563748 
libstarpu-contrib-dev_1.2.6+dfsg-5_amd64.deb
 55d678b90a0a95b3d68c3d46389b0aa73a556c8b 99648 
libstarpu-contribfft-1.2-0-dbgsym_1.2.6+dfsg-5_amd64.deb
 7b9b3af5c0f67174e86e864c4f9c6623d2c31822 39000 
libstarpu-contribfft-1.2-0_1.2.6+dfsg-5_amd64.deb
 6e962571fdcf1a2afaa9cc70f19a9a0a351c04a2 323896 
libstarpu-contribmpi-1.2-3-dbgsym_1.2.6+dfsg-5_amd64.deb
 253933e384b15c08a9b00fa0ff17e4b4e04d5574 75212 
libstarpu-contribmpi-1.2-3_1.2.6+dfsg-5_amd64.deb
 e43cf2df7024fa788d2ee3ca16804f3c1b5a5eed 5220480 
starpu-contrib-examples-dbgsym_1.2.6+dfsg-5_amd64.deb
 81cd13053cb5f8d29a5887b5e0e7bfe0e5eee7aa 273880 
starpu-contrib-examples_1.2.6+dfsg-5_amd64.deb
 4fe2309d4a290b75979c4b8a7db4f38f54179187 337756 
starpu-contrib-tools-dbgsym_1.2.6+dfsg-5_amd64.deb
 0dc2f5f60b1939757e23177c3e5cb319a978a2a3 51836 
starpu-contrib-tools_1.2.6+dfsg-5_amd64.deb
 c3c91424e77e0764640cec350b01f552c079335c 21202 
starpu-contrib_1.2.6+dfsg-5_amd64.buildinfo
Checksums-Sha256:
 f77df85e82304b06fd4c4f489b31075994ae512e0cb5118e74fb093c5759d1c0 3174 
starpu-contrib_1.2.6+dfsg-5.dsc
 c627ad3eaa4ec8bf8acdcea0206ce880e6dd8892dd63c3f9036f67f1649f10ea

Bug#890116: Not fixed upstream

2019-01-14 Thread Andreas Tille

Control: tags 890116 - fixed-upstream
Control: usertags 890116 + status-open
Control: usertags 890116 - status-closed

On Mon, Jan 14, 2019 at 05:16:23PM +, debian-bts-l...@lists.debian.org 
wrote:
> # remote status report for #890116 (http://bugs.debian.org/890116)
> # Bug title: bedtools FTBFS on 32bit: Tools failing:  coverage intersect 
> negativecontrol reldist shuffle split
> #  * https://github.com/arq5x/bedtools2/issues/675
> #  * remote status changed: open -> closed
> #  * closed upstream

I think upstream was wrong in closing the issue.  It was just based on
reading a random last line of the test log and not the full log which
actually contains failures.

Kind regards

Andreas.

-- 
http://fam-tille.de

Processed (with 2 errors): Not fixed upstream

2019-01-14 Thread Debian Bug Tracking System

Processing control commands:

> tags 890116 - fixed-upstream
Bug #890116 [src:bedtools] bedtools FTBFS on 32bit: Tools failing:  coverage 
intersect negativecontrol reldist shuffle split
Removed tag(s) fixed-upstream.
> usertags 890116 + status-open
Unknown command or malformed arguments to command.

> usertags 890116 - status-closed
Unknown command or malformed arguments to command.


-- 
890116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#918322: initramfs-tools: kernel fails to boot with "Gave up waiting for root file system device"

2019-01-14 Thread Isaac Gelado

Sorry for the late reply. I could not reboot my machine until today.

I added a sleep 5 and it didn’t work.

On Tue, Jan 8, 2019 at 9:15 AM Michael Biebl  wrote:

> Am 08.01.19 um 18:11 schrieb Isaac Gelado:
> > As a side hint that might be helpful. I had two kernels 4.18 and 4.19
> > in my system. This problem started when I first boot 4.19, while I was
> > able to boot 4.18 without problems. At some point I decided to do an
> > `update-initramfs -k all -u` and the problem started to also happen
> > when booting 4.18. I do not understand why when upgrading udev/systemd
> > from 239-15 to 240-2 the trigger only updated the iniramfs for 4.19.
>
> This is expected. udev's postinst runs "update-initramfs -u" which only
> updates the initramfs of the currently active kernel, not for all of them.
> For that, as you already mentioned, you need to pass "-k all"
>
> Regards,
> Michael
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

2019-01-14 Thread Celejar

Package: git-daemon-run
Version: 1:2.20.1+next.20190104-1
Severity: grave
Justification: renders package unusable

Any attempt to manage the daemon (e.g., 'sv stat git-daemon', as per
README.debian) fails with:

warning: git-daemon: unable to open supervise/ok: file does not exist

I see that there's an old, archived bug about this:

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

But I'm getting the same thing on my uptodate Sid system (and even on
another Sid system with the version of the package from experimental
installed).

I know nothing about runit, so perhaps I'm doing something obvious
wrong, but I'm just trying to follow the directions from the README, and
getting this.

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

Kernel: Linux 4.19.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)
LSM: AppArmor: enabled

Versions of packages git-daemon-run depends on:
ii  adduser  3.118
ii  git  1:2.20.1-1
ii  runit2.1.2-22

git-daemon-run recommends no packages.

git-daemon-run suggests no packages.

-- no debconf information

Processed: [bts-link] source package src:bedtools

2019-01-14 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:bedtools
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #890116 (http://bugs.debian.org/890116)
> # Bug title: bedtools FTBFS on 32bit: Tools failing:  coverage intersect 
> negativecontrol reldist shuffle split
> #  * https://github.com/arq5x/bedtools2/issues/675
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 890116 + fixed-upstream
Bug #890116 [src:bedtools] bedtools FTBFS on 32bit: Tools failing:  coverage 
intersect negativecontrol reldist shuffle split
Added tag(s) fixed-upstream.
> usertags 890116 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 890116 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
890116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package coreutils

2019-01-14 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package coreutils
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #525359 (http://bugs.debian.org/525359)
> # Bug title: wish there was a libcoreutils
> #  * https://debbugs.gnu.org/12961
> #  * remote status changed: (?) -> pending
> usertags 525359 + status-pending
There were no usertags set.
Usertags are now: status-pending.
> # remote status report for #598018 (http://bugs.debian.org/598018)
> # Bug title: install: temporary insecure file permissions
> #  * https://debbugs.gnu.org/12947
> #  * remote status changed: (?) -> done
> #  * remote resolution changed: (?) -> patch-security
> #  * closed upstream
> tags 598018 + fixed-upstream
Bug #598018 [coreutils] install: temporary insecure file permissions
Added tag(s) fixed-upstream.
> usertags 598018 + status-done resolution-patch-security
There were no usertags set.
Usertags are now: resolution-patch-security status-done.
> # remote status report for #603895 (http://bugs.debian.org/603895)
> # Bug title: coreutils: [manual] ls -  description for --directory is 
> insufficient
> #  * https://debbugs.gnu.org/7433
> #  * remote status changed: (?) -> pending
> usertags 603895 + status-pending
There were no usertags set.
Usertags are now: status-pending.
> # remote status report for #654666 (http://bugs.debian.org/654666)
> # Bug title: mv -f refuses to replace a file with a symlink to the same inode
> #  * https://debbugs.gnu.org/6960
> #  * remote status changed: (?) -> done
> #  * closed upstream
> tags 654666 + fixed-upstream
Bug #654666 [coreutils] mv -f refuses to replace a file with a symlink to the 
same inode
Added tag(s) fixed-upstream.
> usertags 654666 + status-done
There were no usertags set.
Usertags are now: status-done.
> # remote status report for #670478 (http://bugs.debian.org/670478)
> # Bug title: coreutils: Please disable test cp/parent-perm-race on hurd-i386
> #  * https://debbugs.gnu.org/11436
> #  * remote status changed: (?) -> done
> #  * remote resolution changed: (?) -> notabug
> #  * closed upstream
> tags 670478 + fixed-upstream
Bug #670478 [coreutils] coreutils: Please disable test cp/parent-perm-race on 
hurd-i386
Added tag(s) fixed-upstream.
> usertags 670478 + status-done resolution-notabug
There were no usertags set.
Usertags are now: status-done resolution-notabug.
> # remote status report for #695489 (http://bugs.debian.org/695489)
> # Bug title: uniq "loses" non-identical lines with some locales
> #  * https://debbugs.gnu.org/21916
> #  * remote status changed: (?) -> done
> #  * remote resolution changed: (?) -> notabug
> #  * closed upstream
> tags 695489 + fixed-upstream
Bug #695489 [coreutils] uniq "loses" non-identical lines with some locales
Added tag(s) fixed-upstream.
> usertags 695489 + status-done resolution-notabug
There were no usertags set.
Usertags are now: resolution-notabug status-done.
> # remote status report for #718030 (http://bugs.debian.org/718030)
> # Bug title: split man page table mushed
> #  * https://debbugs.gnu.org/14971
> #  * remote status changed: (?) -> done
> #  * remote resolution changed: (?) -> fixed
> #  * closed upstream
> tags 718030 + fixed-upstream
Bug #718030 [coreutils] split man page table mushed
Added tag(s) fixed-upstream.
> usertags 718030 + status-done resolution-fixed
There were no usertags set.
Usertags are now: resolution-fixed status-done.
> # remote status report for #743955 (http://bugs.debian.org/743955)
> # Bug title: coreutils: corrupted files on heavily fragmented ext3 and ext4 
> partitions
> #  * https://debbugs.gnu.org/12656
> #  * remote status changed: (?) -> done
> #  * remote resolution changed: (?) -> fixed
> #  * closed upstream
> tags 743955 + fixed-upstream
Bug #743955 [coreutils] coreutils: corrupted files on heavily fragmented ext3 
and ext4 partitions
Added tag(s) fixed-upstream.
> usertags 743955 + status-done resolution-fixed
There were no usertags set.
Usertags are now: status-done resolution-fixed.
> # remote status report for #911572 (http://bugs.debian.org/911572)
> # Bug title: coreutils: incorrect and inconsistent quoting in ls output
> #  * https://debbugs.gnu.org/33113
> #  * remote status changed: (?) -> pending
> #  * remote resolution changed: (?) -> confirmed
> usertags 911572 + status-pending resolution-confirmed
There were no usertags set.
Usertags are now: resolution-confirmed status-pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
598018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598018
654666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654666
670478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670478
695489:

Bug#919293: FTBFS: Test keys expired 2019-01-06

2019-01-14 Thread Julian Andres Klode

Source: gpgme1.0
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco

See https://dev.gnupg.org/T3815 and
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=commit;h=66376f3e206a1aa791d712fb8577bb3490268f60

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

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

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

Bug#918543: marked as done (ring build depends on libsrtp-dev that is not in buster)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 16:30:58 +
with message-id 
and subject line Bug#918543: fixed in ring 20190101.3.5315d84~ds1-2
has caused the Debian Bug report #918543,
regarding ring build depends on libsrtp-dev that is not in buster
to be marked as done.

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


-- 
918543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ring
Version: 20180119.1.9e06f94~ds120181001.4.a99aaec~ds6-2
Severity: serious
Tags: ftbfs
Control: block 910292 by -1

ring build depends on libsrtp-dev that is not in buster,
see #910292 for background.
--- End Message ---
--- Begin Message ---
Source: ring
Source-Version: 20190101.3.5315d84~ds1-2

We believe that the bug you reported is fixed in the latest version of
ring, 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 918...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexandre Viau  (supplier of updated ring package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 Jan 2019 10:08:09 -0500
Source: ring
Binary: jami jami-daemon ring ring-daemon
Architecture: source
Version: 20190101.3.5315d84~ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Alexandre Viau 
Description:
 jami   - Secure and distributed voice, video and chat platform - desktop c
 jami-daemon - Secure and distributed voice, video and chat platform - daemon
 ring   - transitional package for jami
 ring-daemon - transitional package for jami-daemon
Closes: 918543
Changes:
 ring (20190101.3.5315d84~ds1-2) unstable; urgency=medium
 .
   * Remove unused libsrtp dependency. (Closes: 918543)
Checksums-Sha1:
 739c965d0e539ad6708b37ff5f5f2009ca371224 3043 ring_20190101.3.5315d84~ds1-2.dsc
 b814e385a2caf18d0211d94bf25221426610fb81 11756 
ring_20190101.3.5315d84~ds1-2.debian.tar.xz
 b748234053a22c3a880108078fe90bbd820d955e 5684 
ring_20190101.3.5315d84~ds1-2_source.buildinfo
Checksums-Sha256:
 c93b45db09a9e44d76b5da89807c6ea666800ff26912148980b91539f859638d 3043 
ring_20190101.3.5315d84~ds1-2.dsc
 8ece84621af0b63d82b4eaf3b2cde19becb1dac51d024fe6332b9b6913b7ccd2 11756 
ring_20190101.3.5315d84~ds1-2.debian.tar.xz
 b058e44a8b843094ceaee7bd0de45f7c8bad52fb66f743e0c18092b3d3821952 5684 
ring_20190101.3.5315d84~ds1-2_source.buildinfo
Files:
 97f39d53537b29d75398456f805644de 3043 comm optional 
ring_20190101.3.5315d84~ds1-2.dsc
 1050324cdf39badcda3ccb2095118132 11756 comm optional 
ring_20190101.3.5315d84~ds1-2.debian.tar.xz
 faf849be0bf720803ce85ff8d8dccb3d 5684 comm optional 
ring_20190101.3.5315d84~ds1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEB0B3ii38SjnAyLyMjysRPGU1xacFAlw8pgMACgkQjysRPGU1
xadKHg/+LXIb4UmGsyfD9fVbIjnYBjlC+1b6efZjA3HZjXX9zwHQVpsl3/uwyMd7
yPKiv4WSurC4Uh7nd6SU1hr7Jt9X6GBwBgHpovKfi1Xe/nj6sQVoYBEdVDsw1sm/
62bdYYZvubWuIbgnLHjCgYf5QSeaaz50A+ix8IN+PLXM19MqdlNhstLGFt8ODbm6
E3xt5G4C89GEzk3lfiYOFZpmwFlog8xkSmoWyy0VHB9tm5X32GONCl6C8mzQXP2d
rTSMNIRZ8C6lhMST0IjRke///7NG10D6r2AD9i4q3+/ucMawx9YbV/CumOkhF+td
p22wCc8JQDMwL1WPjOupemYvemG1AeRztZmI2ZHuwBvwwy7ZV/UeIBinviFDe8LA
7EaMkOXhi4jBEM0jmmp0Ppu0334nysPO02Zt3rmPX/ytMwOg0NsMCP9N3pQAS7bs
Ooqf6aQILv4Kw2+8PI0O8MPH1CDbgVBNbOZ9l3PUEfk4geuqCzvmXEIlhDUHenv9
pXqpoGBtEEMccFaXgDATCND4AAuy8yAPj0jAZ1EDLUjHbHVB8LFt1pJs/hlyCVbE
t7TKXZ8FwmcL9uaraIk2oKxEmpwTfJviyncD1GeGdKzYgzfoNSAyggHWlRP9r1aW
8p8Zuds+us0vS4PAchNxZE0iQyGNkep34lD0eF4y8l/sDTCjIVQ=
=XATx
-END PGP SIGNATURE End Message ---

Bug#919138: wpasupplicant 2.7 fails to connect to some Wifi networks

2019-01-14 Thread Andrej Shadura

On Sun, 13 Jan 2019 at 19:54, Different55  wrote:
>
> Hi! I'm running Debian Sid and recently upgraded wpasupplicant to 2.7. After 
> the upgrade finished, NetworkManager popped up saying that the connection to 
> my home Wifi failed. I was able to connect to my phone's hotspot still. I 
> attached a relevant bit of a log from journalctl.
>
> I also tried Debian's experimental package "2:2.7+git20190108+11ce7a1-1," 
> that had the same issue. I didn't have this issue after downgrading to 2.6. 
> According to lshw, my wireless adapter is an Intel Wireless 3165.
>
> Let me know if there's anything else I can do to help!

It seems the attachment’s got lost somehow.
Here’s a copy:
https://bugs.debian.org/919138#36

Also, FYI here’s the current wpasupplicant’s build config in Debian:
https://sources.debian.org/src/wpa/2:2.7-3/debian/config/wpasupplicant/linux/

-- 
Cheers,
  Andrej

Bug#917667: marked as done (biojava4-live: FTBFS: error: package javax.xml.bind.annotation does not exist)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 16:20:32 +
with message-id 
and subject line Bug#917655: fixed in biojava4-live 4.2.12+dfsg-1
has caused the Debian Bug report #917655,
regarding biojava4-live: FTBFS: error: package javax.xml.bind.annotation does 
not exist
to be marked as done.

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


-- 
917655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: biojava4-live
Version: 4.2.11+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/biojava4-live-4.2.11+dfsg'
> cd biojava-jcolorbrewer && ant jar
> Buildfile: 
> /<>/biojava4-live-4.2.11+dfsg/biojava-jcolorbrewer/build.xml
> 
> compile:
> [mkdir] Created dir: 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-jcolorbrewer/classes
> [mkdir] Created dir: /<>/biojava4-live-4.2.11+dfsg/dist
> [javac] 
> /<>/biojava4-live-4.2.11+dfsg/biojava-jcolorbrewer/build.xml:93: 
> warning: 'includeantruntime' was not set, defaulting to 
> build.sysclasspath=last; set to false for repeatable builds
> [javac] Compiling 9 source files to 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-jcolorbrewer/classes
> [javac] Note: 
> /<>/biojava4-live-4.2.11+dfsg/biojava-jcolorbrewer/src/main/java/org/jcolorbrewer/ui/ColorPaletteChooserDialog.java
>  uses or overrides a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
>  [copy] Warning: 
> /<>/biojava4-live-4.2.11+dfsg/biojava-jcolorbrewer/src/main/resources
>  does not exist.
> 
> jar:
>   [jar] Building jar: 
> /<>/biojava4-live-4.2.11+dfsg/dist/biojava4-jcolorbrewer.jar
> 
> BUILD SUCCESSFUL
> Total time: 1 second
> cd biojava-forester && ant jar
> Buildfile: /<>/biojava4-live-4.2.11+dfsg/biojava-forester/build.xml
> 
> compile:
> [mkdir] Created dir: 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-forester/classes
> [javac] 
> /<>/biojava4-live-4.2.11+dfsg/biojava-forester/build.xml:93: 
> warning: 'includeantruntime' was not set, defaulting to 
> build.sysclasspath=last; set to false for repeatable builds
> [javac] Compiling 359 source files to 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-forester/classes
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
>  [copy] Warning: 
> /<>/biojava4-live-4.2.11+dfsg/biojava-forester/src/main/resources 
> does not exist.
> 
> jar:
>   [jar] Building jar: 
> /<>/biojava4-live-4.2.11+dfsg/dist/biojava4-forester.jar
> 
> BUILD SUCCESSFUL
> Total time: 9 seconds
> cd biojava-core && ant jar
> Buildfile: /<>/biojava4-live-4.2.11+dfsg/biojava-core/build.xml
> 
> compile:
> [mkdir] Created dir: 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-core/classes
> [javac] 
> /<>/biojava4-live-4.2.11+dfsg/biojava-core/build.xml:93: warning: 
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set 
> to false for repeatable builds
> [javac] Compiling 176 source files to 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-core/classes
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
>  [copy] Copying 24 files to 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-core/classes
> 
> jar:
>   [jar] Building jar: 
> /<>/biojava4-live-4.2.11+dfsg/dist/biojava4-core.jar
> 
> BUILD SUCCESSFUL
> Total time: 4 seconds
> cd biojava-phylo && ant jar
> Buildfile: /<>/biojava4-live-4.2.11+dfsg/biojava-phylo/build.xml
> 
> compile:
> [mkdir] Created dir: 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-phylo/classes
> [javac] 
> /<>/biojava4-live-4.2.11+dfsg/biojava-phylo/build.xml:93: warning: 
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set 
> to false for repeatable builds
> [javac] Compiling 8 source files to 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-phylo/classes
>  [copy] Copying 2 files to 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-phylo/classes
> 
> jar:
>   [jar] Building jar: 
> /<>/biojava4-live-4.2.11+dfsg/dist/biojava4-phylo.jar
> 
> BUILD SUCCESSFUL
> Total time: 1 second
> cd biojava-alignment && ant jar
> Buildfile:

Bug#917655: marked as done (biojava4-live: FTBFS (cannot find symbol JAXBContext))

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 16:20:32 +
with message-id 
and subject line Bug#917655: fixed in biojava4-live 4.2.12+dfsg-1
has caused the Debian Bug report #917655,
regarding biojava4-live: FTBFS (cannot find symbol JAXBContext)
to be marked as done.

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


-- 
917655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:biojava4-live
Version: 4.2.11+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep  --with javahelper
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/biojava4-live-4.2.11+dfsg'
dh_auto_configure
sed -e 's/BJLIB/biojava4-forester/g' debian/build.xml > 
biojava-forester/build.xml
sed -e 's/BJLIB/biojava4-aa-prop/g' debian/build.xml > biojava-aa-prop/build.xml
sed -e 's/BJLIB/biojava4-core/g' debian/build.xml > biojava-core/build.xml
sed -e 's/BJLIB/biojava4-alignment/g' debian/build.xml > 
biojava-alignment/build.xml
sed -e 's/BJLIB/biojava4-genome/g' debian/build.xml > biojava-genome/build.xml
sed -e 's/BJLIB/biojava4-modfinder/g' debian/build.xml > 
biojava-modfinder/build.xml
sed -e 's/BJLIB/biojava4-phylo/g' debian/build.xml > biojava-phylo/build.xml

[... snipped ...]

[javac]   location: class PeptidePropertiesImpl
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/PeptidePropertiesImpl.java:147:
 error: cannot find symbol
[javac] JAXBContext jc2 = 
JAXBContext.newInstance(aTable.getClass());
[javac] ^
[javac]   symbol:   class JAXBContext
[javac]   location: class PeptidePropertiesImpl
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/PeptidePropertiesImpl.java:147:
 error: cannot find symbol
[javac] JAXBContext jc2 = 
JAXBContext.newInstance(aTable.getClass());
[javac]   ^
[javac]   symbol:   variable JAXBContext
[javac]   location: class PeptidePropertiesImpl
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/PeptidePropertiesImpl.java:148:
 error: cannot find symbol
[javac] Unmarshaller u2 = jc2.createUnmarshaller();
[javac] ^
[javac]   symbol:   class Unmarshaller
[javac]   location: class PeptidePropertiesImpl
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/xml/MyValidationEventHandler.java:34:
 error: method does not override or implement a method from a supertype
[javac] @Override
[javac] ^
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/xml/MyValidationEventHandler.java:36:
 error: cannot find symbol
[javac] if (ve.getSeverity() == ValidationEvent.FATAL_ERROR ||  
ve.getSeverity() == ValidationEvent.ERROR){
[javac] ^
[javac]   symbol:   variable ValidationEvent
[javac]   location: class MyValidationEventHandler
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/xml/MyValidationEventHandler.java:36:
 error: cannot find symbol
[javac] if (ve.getSeverity() == ValidationEvent.FATAL_ERROR ||  
ve.getSeverity() == ValidationEvent.ERROR){
[javac] 
^
[javac]   symbol:   variable ValidationEvent
[javac]   location: class MyValidationEventHandler
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/xml/MyValidationEventHandler.java:37:
 error: cannot find symbol
[javac] ValidationEventLocator  locator = 
ve.getLocator();
[javac] ^
[javac]   symbol:   class ValidationEventLocator
[javac]   location: class MyValidationEventHandler
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/xml/SchemaGenerator.java:36:
 error: method does not override or implement a method from a supertype
[javac] @Override
[javac] ^
[javac] 83 errors

BUILD FAILED
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/build.xml:93:

Bug#917667: marked as done (biojava4-live: FTBFS: error: package javax.xml.bind.annotation does not exist)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 16:20:32 +
with message-id 
and subject line Bug#917667: fixed in biojava4-live 4.2.12+dfsg-1
has caused the Debian Bug report #917667,
regarding biojava4-live: FTBFS: error: package javax.xml.bind.annotation does 
not exist
to be marked as done.

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


-- 
917667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: biojava4-live
Version: 4.2.11+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/biojava4-live-4.2.11+dfsg'
> cd biojava-jcolorbrewer && ant jar
> Buildfile: 
> /<>/biojava4-live-4.2.11+dfsg/biojava-jcolorbrewer/build.xml
> 
> compile:
> [mkdir] Created dir: 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-jcolorbrewer/classes
> [mkdir] Created dir: /<>/biojava4-live-4.2.11+dfsg/dist
> [javac] 
> /<>/biojava4-live-4.2.11+dfsg/biojava-jcolorbrewer/build.xml:93: 
> warning: 'includeantruntime' was not set, defaulting to 
> build.sysclasspath=last; set to false for repeatable builds
> [javac] Compiling 9 source files to 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-jcolorbrewer/classes
> [javac] Note: 
> /<>/biojava4-live-4.2.11+dfsg/biojava-jcolorbrewer/src/main/java/org/jcolorbrewer/ui/ColorPaletteChooserDialog.java
>  uses or overrides a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
>  [copy] Warning: 
> /<>/biojava4-live-4.2.11+dfsg/biojava-jcolorbrewer/src/main/resources
>  does not exist.
> 
> jar:
>   [jar] Building jar: 
> /<>/biojava4-live-4.2.11+dfsg/dist/biojava4-jcolorbrewer.jar
> 
> BUILD SUCCESSFUL
> Total time: 1 second
> cd biojava-forester && ant jar
> Buildfile: /<>/biojava4-live-4.2.11+dfsg/biojava-forester/build.xml
> 
> compile:
> [mkdir] Created dir: 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-forester/classes
> [javac] 
> /<>/biojava4-live-4.2.11+dfsg/biojava-forester/build.xml:93: 
> warning: 'includeantruntime' was not set, defaulting to 
> build.sysclasspath=last; set to false for repeatable builds
> [javac] Compiling 359 source files to 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-forester/classes
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
>  [copy] Warning: 
> /<>/biojava4-live-4.2.11+dfsg/biojava-forester/src/main/resources 
> does not exist.
> 
> jar:
>   [jar] Building jar: 
> /<>/biojava4-live-4.2.11+dfsg/dist/biojava4-forester.jar
> 
> BUILD SUCCESSFUL
> Total time: 9 seconds
> cd biojava-core && ant jar
> Buildfile: /<>/biojava4-live-4.2.11+dfsg/biojava-core/build.xml
> 
> compile:
> [mkdir] Created dir: 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-core/classes
> [javac] 
> /<>/biojava4-live-4.2.11+dfsg/biojava-core/build.xml:93: warning: 
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set 
> to false for repeatable builds
> [javac] Compiling 176 source files to 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-core/classes
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
>  [copy] Copying 24 files to 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-core/classes
> 
> jar:
>   [jar] Building jar: 
> /<>/biojava4-live-4.2.11+dfsg/dist/biojava4-core.jar
> 
> BUILD SUCCESSFUL
> Total time: 4 seconds
> cd biojava-phylo && ant jar
> Buildfile: /<>/biojava4-live-4.2.11+dfsg/biojava-phylo/build.xml
> 
> compile:
> [mkdir] Created dir: 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-phylo/classes
> [javac] 
> /<>/biojava4-live-4.2.11+dfsg/biojava-phylo/build.xml:93: warning: 
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set 
> to false for repeatable builds
> [javac] Compiling 8 source files to 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-phylo/classes
>  [copy] Copying 2 files to 
> /<>/biojava4-live-4.2.11+dfsg/build/biojava4-phylo/classes
> 
> jar:
>   [jar] Building jar: 
> /<>/biojava4-live-4.2.11+dfsg/dist/biojava4-phylo.jar
> 
> BUILD SUCCESSFUL
> Total time: 1 second
> cd biojava-alignment && ant jar
> Buildfile:

Bug#917655: marked as done (biojava4-live: FTBFS (cannot find symbol JAXBContext))

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 16:20:32 +
with message-id 
and subject line Bug#917667: fixed in biojava4-live 4.2.12+dfsg-1
has caused the Debian Bug report #917667,
regarding biojava4-live: FTBFS (cannot find symbol JAXBContext)
to be marked as done.

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


-- 
917667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:biojava4-live
Version: 4.2.11+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep  --with javahelper
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/biojava4-live-4.2.11+dfsg'
dh_auto_configure
sed -e 's/BJLIB/biojava4-forester/g' debian/build.xml > 
biojava-forester/build.xml
sed -e 's/BJLIB/biojava4-aa-prop/g' debian/build.xml > biojava-aa-prop/build.xml
sed -e 's/BJLIB/biojava4-core/g' debian/build.xml > biojava-core/build.xml
sed -e 's/BJLIB/biojava4-alignment/g' debian/build.xml > 
biojava-alignment/build.xml
sed -e 's/BJLIB/biojava4-genome/g' debian/build.xml > biojava-genome/build.xml
sed -e 's/BJLIB/biojava4-modfinder/g' debian/build.xml > 
biojava-modfinder/build.xml
sed -e 's/BJLIB/biojava4-phylo/g' debian/build.xml > biojava-phylo/build.xml

[... snipped ...]

[javac]   location: class PeptidePropertiesImpl
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/PeptidePropertiesImpl.java:147:
 error: cannot find symbol
[javac] JAXBContext jc2 = 
JAXBContext.newInstance(aTable.getClass());
[javac] ^
[javac]   symbol:   class JAXBContext
[javac]   location: class PeptidePropertiesImpl
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/PeptidePropertiesImpl.java:147:
 error: cannot find symbol
[javac] JAXBContext jc2 = 
JAXBContext.newInstance(aTable.getClass());
[javac]   ^
[javac]   symbol:   variable JAXBContext
[javac]   location: class PeptidePropertiesImpl
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/PeptidePropertiesImpl.java:148:
 error: cannot find symbol
[javac] Unmarshaller u2 = jc2.createUnmarshaller();
[javac] ^
[javac]   symbol:   class Unmarshaller
[javac]   location: class PeptidePropertiesImpl
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/xml/MyValidationEventHandler.java:34:
 error: method does not override or implement a method from a supertype
[javac] @Override
[javac] ^
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/xml/MyValidationEventHandler.java:36:
 error: cannot find symbol
[javac] if (ve.getSeverity() == ValidationEvent.FATAL_ERROR ||  
ve.getSeverity() == ValidationEvent.ERROR){
[javac] ^
[javac]   symbol:   variable ValidationEvent
[javac]   location: class MyValidationEventHandler
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/xml/MyValidationEventHandler.java:36:
 error: cannot find symbol
[javac] if (ve.getSeverity() == ValidationEvent.FATAL_ERROR ||  
ve.getSeverity() == ValidationEvent.ERROR){
[javac] 
^
[javac]   symbol:   variable ValidationEvent
[javac]   location: class MyValidationEventHandler
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/xml/MyValidationEventHandler.java:37:
 error: cannot find symbol
[javac] ValidationEventLocator  locator = 
ve.getLocator();
[javac] ^
[javac]   symbol:   class ValidationEventLocator
[javac]   location: class MyValidationEventHandler
[javac] 
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/src/main/java/org/biojava/nbio/aaproperties/xml/SchemaGenerator.java:36:
 error: method does not override or implement a method from a supertype
[javac] @Override
[javac] ^
[javac] 83 errors

BUILD FAILED
/<>/biojava4-live-4.2.11+dfsg/biojava-aa-prop/build.xml:93:

Bug#892784: fixed in zaqar 7.0.0-1

2019-01-14 Thread Ivo De Decker

Control: reopen -1

Hi Thomas,

On Sun, Jan 13, 2019 at 04:55:20PM +, Thomas Goirand wrote:
>* Uploading to unstable:
>  - Fixes FTBFS (Closes: #892784).

It seems the build still fails during the testsuite:

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

Cheers,

Ivo

Processed: Re: Bug#892784: fixed in zaqar 7.0.0-1

2019-01-14 Thread Debian Bug Tracking System

Processing control commands:

> reopen -1
Bug #892784 {Done: Thomas Goirand } [src:zaqar] zaqar FTBFS: 
test failures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions zaqar/7.0.0-1.

-- 
892784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 919138 is forwarded to http://lists.infradead.org/pipermail/hostap/2019-January/039290.html

2019-01-14 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> forwarded 919138 
> http://lists.infradead.org/pipermail/hostap/2019-January/039290.html
Bug #919138 [wpasupplicant] wpasupplicant: Fails to connect to some Wifi 
networks on version 2:2.7-3
Set Bug forwarded-to-address to 
'http://lists.infradead.org/pipermail/hostap/2019-January/039290.html'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
919138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#919075: marked as done (mustache.js FTBFS)

2019-01-14 Thread Debian Bug Tracking System

Your message dated Mon, 14 Jan 2019 15:26:16 +
with message-id 
and subject line Bug#919075: fixed in mustache.js 2.3.2-1
has caused the Debian Bug report #919075,
regarding mustache.js FTBFS
to be marked as done.

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


-- 
919075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mustache.js
Version: 2.3.0-2
Severity: serious
Tags: ftbfs buster sid

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

...
  5) Mustache CLI
   without partials
 reads view data from stdin when first argument equals "-":
 Uncaught TypeError [ERR_INVALID_CALLBACK]: Callback must be a function
  at makeCallback (fs.js:137:11)
  at Object.unlink (fs.js:939:14)
  at test/cli-test.js:86:12
  at ChildProcess.exithandler (child_process.js:285:7)
  at maybeClose (internal/child_process.js:962:16)
  at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
--- End Message ---
--- Begin Message ---
Source: mustache.js
Source-Version: 2.3.2-1

We believe that the bug you reported is fixed in the latest version of
mustache.js, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated mustache.js package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 Jan 2019 15:12:41 +0100
Source: mustache.js
Binary: libjs-mustache node-mustache
Architecture: source
Version: 2.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Xavier Guimard 
Changed-By: Xavier Guimard 
Closes: 919075
Description: 
 libjs-mustache - Mustache rendering engine for Javascript
 node-mustache - Mustache rendering engine for Javascript - NodeJS
Changes:
 mustache.js (2.3.2-1) unstable; urgency=medium
 .
   [ Jelmer Vernooĳ ]
   * Change priority extra to priority optional.
   * Use secure copyright file specification URI.
 .
   [ Xavier Guimard ]
   * Add debian/gbp.conf
   * Declare compliance with policy 4.3.0
   * Change MIT license to Expat
   * Bump debhelper compatibility level to 11
   * Add patch to fix bad fs.unlink() call (Closes: #919075)
   * Hide lintian warning "please use libjs-mustache"
   * Change section to javascript
   * Honor not-check in DEB_BUILD_OPTIONS
   * Add upstream/metadata
   * Import upstream version 2.3.2
   * Update node path in patch
   * Add minimal autopkgtest files
   * Add myself to uploaders
Checksums-Sha1: 
 9919c1a5f72b8bc34a50c088ba4397dc316999d4 2154 mustache.js_2.3.2-1.dsc
 5b5a1631ca9e1b1e615ad1e424b58d84736ea893 42186 mustache.js_2.3.2.orig.tar.gz
 a502e0f5a90fbb33d91e92fbb82b1e87f981c44c 4476 mustache.js_2.3.2-1.debian.tar.xz
Checksums-Sha256: 
 6bd0732480d312ce540418dedebc8fb64f949018c851ced88438096bfb4bd5b5 2154 
mustache.js_2.3.2-1.dsc
 72196502b9c05d9b46814c362417d0319d77337624b629029f0ddc87b3c76c5b 42186 
mustache.js_2.3.2.orig.tar.gz
 142ee7049da46bb97d87774b33fb85d2cca550df8de04efa6898b432127268b9 4476 
mustache.js_2.3.2-1.debian.tar.xz
Files: 
 4378a64c719d524db5f23b59f269c049 2154 javascript optional 
mustache.js_2.3.2-1.dsc
 7cd8564f0500a47b26fa31ccb16a5417 42186 javascript optional 
mustache.js_2.3.2.orig.tar.gz
 ce6bc95a9bd2a47cca73b6b002d482a7 4476 javascript optional 
mustache.js_2.3.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlw8mrsQHHlhZGRAZGVi
aWFuLm9yZwAKCRD210ynyZnu6YW1D/9LRyTmWz4jd2A/YmkDcoUxsq8iXu99PcaK
AapC2hcqexXEVAKh+6INNFfZuegVPNr0R11T+kDlDnwuzozJD+xDUd3Yx8lL37MJ
XFwDexm+y7kRbrVV7/UhA7qoZsOerwZwFjps0oP9C1S5KouyrF9buaHRTRIeuYWc
pvIQoUkSd0nVkon3GMmJHyTIrg5GTy7U/j+WJCfc207xwdLMp7ZDxUGPDUWPOrcu
E2L2NaKjh+IX91pLEZTg75uZMWEew49+rlAXXws3mpQho8nGYPs/MDq2SX6P7V8T
k3/7Bej2d/KV80vdLc26jpjjHxJtTovL1u/rG1cCMq28YEt0zTJjyvxp5reWj6C6
wdW/3JA7+J5/JbNc0dLizuefrG+52QOJYu1+dwYgSbNROMJD8FN905nkcNFVYrT8
Gxmr/16nO/zfoEKGAVrZ0TfAxbyeJRcX33HkHUACHdfKlC3b4QBT3Mband8yFJ4T
m0a3DkNTrO5iUTlunbwA3ljeJhSJj2Reu3FjKuZfrLCOZYx2yaKIqwainGdqzzvS
GHEGNL2DK6bLmmF3nLsJwOvZQiH4rjlayR0NwnL/InRxlJNP2Hkh7leZtu2SXj4M

Bug#916430: Bug #916430 in wifite marked as pending

2019-01-14 Thread Sophie Brun

Control: tag -1 pending

Hello,

Bug #916430 in wifite reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/pkg-security-team/wifite/commit/d64f3529aabe1f9320bbb001c67c0dfccfe811f1


Disable failing test with aircrack-ng >= 1.5 (Closes: #916430)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/916430

Processed: Bug #916430 in wifite marked as pending

2019-01-14 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #916430 [src:wifite] wifite FTBFS: FAIL: testHandshakeAircrack 
(test_Handshake.TestHandshake)
Added tag(s) pending.

-- 
916430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#919286: yotta: /usr/bin/yt is already provided by the python3-yt package

2019-01-14 Thread Andreas Beckmann

Package: yotta
Version: 0.18.5-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package yotta.
  Preparing to unpack .../88-yotta_0.18.5-1_all.deb ...
  Unpacking yotta (0.18.5-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-IIiNld/88-yotta_0.18.5-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/yt', which is also in package python3-yt 
3.5.0-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-IIiNld/88-yotta_0.18.5-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/bin/yt
  usr/share/man/man1/yt.1.gz


Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


python3-yt=3.5.0-1_yotta=0.18.5-1.log.gz
Description: application/gzip

Bug#919075: Bug #919075 in mustache.js marked as pending

2019-01-14 Thread Xavier Guimard

Control: tag -1 pending

Hello,

Bug #919075 in mustache.js reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/mustache.js/commit/4663d0d4968b0900fe54bc6ea95075dcaa7f554e


Add patch to fix bad fs.unlink() call

Closes: #919075


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919075

Processed: Bug #919075 in mustache.js marked as pending

2019-01-14 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #919075 [src:mustache.js] mustache.js FTBFS
Added tag(s) pending.

-- 
919075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

2019-01-14 Thread Axel Beckert

Hi,

Axel Beckert wrote:
> The syslog shows again this:
> 
> Jan 14 07:18:59 c-cactus2 dnssec-triggerd[22039]: Jan 14 07:18:59 
> dnssec-triggerd[22039] error: Error in SSL_CTX use_certificate_file crypto 
> error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small

Attached the output of "fgrep dnssec /var/log/syslog" from the time of
the package upgrade.

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


dnssec-syslog-excerpt.txt.xz
Description: Binary data

Processed: Re: /snap is a FHS violation

2019-01-14 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 normal
Bug #852199 [snapd] /snap is a FHS violation
Severity set to 'normal' from 'serious'
> tags -1 wontfix
Bug #852199 [snapd] /snap is a FHS violation
Added tag(s) wontfix.

-- 
852199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

1 2 >

1 - 100 of 145 matches

Mail list logo