Bug#907493: ghostscript breaks cups autopkgtest: test times out

2018-09-14 Thread Paul Gevers
Hi Jonas,

On 14-09-18 22:26, Jonas Smedegaard wrote:
> Another release of Ghostscript is now in experimental.  Can someone 
> please test if those autopkgtests still fail?

9.25~dfsg-1~exp1 passed the cups test.

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cups/994233/log.gz

Paul



signature.asc
Description: OpenPGP digital signature


Bug#908796: udev (with sysvinit) fails to find devices at boot

2018-09-14 Thread Trek
On Thu, 13 Sep 2018 19:02:26 -0700
Bill Brelsford  wrote:

> With the --background argument, a race condition exists and
> "udevadm trigger" starts too soon.
> A workaround is to add a short sleep:

can you try if this patch fixes the problem?
my system is not affected so I can't check

thank you!


the sleep timeout could be different depending on the hardware, so it
checks every second if udev is ready, up to 15 seconds

it seems to be there is no reliable method to know if udev is running
fine, so it calls udevadm control -S, that it's essentially a no-op
when udev is just started, but at least it checks if the control socket
is listening

ciao
>From 1c9dd060a25d904aa200c9fdc33e34dc003dd1d8 Mon Sep 17 00:00:00 2001
From: Trek 
Date: Sat, 15 Sep 2018 05:50:03 +0200
Subject: [PATCH] Wait for udev to be ready before trigger under sysvinit

The start-stop-daemon command with the --background argument returns
immediately, too soon to trigger events on some systems. Update the
SysV init script to wait until udev is ready.

Closes: #908796
---
 debian/udev.init | 13 +
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/debian/udev.init b/debian/udev.init
index 9c394bb..4b30297 100644
--- a/debian/udev.init
+++ b/debian/udev.init
@@ -170,11 +170,16 @@ case "$1" in
 # prevents udevd to be killed by sendsigs (see #791944)
 mkdir -p $OMITDIR
 ln -sf $PIDFILE $OMITDIR/$NAME
-log_end_msg $?
+
+# wait for udev to be ready (see #908796)
+timeout=15
+until udevadm control -S || [ $timeout -le 0 ]; do
+timeout=$((timeout-1))
+sleep 1
+done
+udevadm control -S && log_success_msg || log_failure_msg
 else
-log_warning_msg $?
-log_warning_msg "Waiting 15 seconds and trying to continue anyway"
-sleep 15
+log_failure_msg
 fi
 
 log_action_begin_msg "Synthesizing the initial hotplug events"
-- 
2.1.4



Bug#908796: udev (with sysvinit) fails to find devices at boot

2018-09-14 Thread Bill Brelsford
On Sat Sep 15 2018 at 06:28 AM +0200, Trek wrote:
> On Thu, 13 Sep 2018 19:02:26 -0700
> Bill Brelsford  wrote:
> 
> > With the --background argument, a race condition exists and
> > "udevadm trigger" starts too soon.
> > A workaround is to add a short sleep:
> 
> can you try if this patch fixes the problem?
> my system is not affected so I can't check

That fixes it (worked twice, anyway).  Thanks!

Bill



Bug#908463: [Pkg-privacy-maintainers] Bug#908463: torbrowser-launcher: Fails to start "Web Content" processes due to outdated AppArmor policy

2018-09-14 Thread intrigeri
Roger Shimizu:
> On Mon, Sep 10, 2018 at 11:58 PM, gregor herrmann  wrote:
>> On Mon, 10 Sep 2018 10:43:32 -0400, Antoine Beaupré wrote:
>> After upgrading to 0.2.9-4, adequate complains:
>>
>> torbrowser-launcher: obsolete-conffile 
>> /etc/apparmor.d/local/torbrowser.Tor.tor
>> torbrowser-launcher: obsolete-conffile 
>> /etc/apparmor.d/local/torbrowser.Browser.plugin-container
>> torbrowser-launcher: obsolete-conffile 
>> /etc/apparmor.d/local/torbrowser.Browser.firefox

> Sorry, I don't have these errors when upgrading package.

To reproduce, I think you need 1. adequate installed;
2. upgrading from a specific version of the package.

Cheers,
-- 
intrigeri



Bug#901015: transition: protobuf

2018-09-14 Thread Pirate Praveen
On Tue, 11 Sep 2018 09:51:07 +0200
=?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?=  wrote:
> The last package which fails is gazebo which seems to be team
> maintained but it has two NMUs already. There's no bug reported here
> for the protobuf update but upstream aware of it and has a patch[1].
> This one is not yet tested by me, but the upstream BTS contains a
> comment that's a working fix for gazebo 7.x and the original bug
> report[2] states that the fix is in place for the 8.x and 9.x versions
> as well. If you have time, please file a bug for this to the gazeboo
> source package - but as noted its Debian maintainers are not very
> active.

I have reported it as #908854 and it is already fixed upstream in 9.2
version.

I think we can upload protobuf now and raise severity of the gazebo bug
to serious.



signature.asc
Description: OpenPGP digital signature


Bug#908854: gazebo FTBFS with protobuf 3.6 (fixed upstream in 9.2)

2018-09-14 Thread Pirate Praveen
package: gazebo
version: 9.0.0+dfsg5-4.2
severity: important
control: block 901015 by -1
control: tag -1 fixed-upstream, patch

gazebo fails to build from source with protobuf 3.6.1 currently in
experimental. Soon protobuf 3.6.1 will be uploaded to unstable and at
that time the severity will be raised to serious.

This is already fixed upstream in gazebo 9.2 version.

https://bitbucket.org/osrf/gazebo/src/5714795a2e797b7de133708a02a3cc35724099b8/Changelog.md?fileviewer=file-view-default



signature.asc
Description: OpenPGP digital signature


Bug#908463: [Pkg-privacy-maintainers] Bug#908463: torbrowser-launcher: Fails to start "Web Content" processes due to outdated AppArmor policy

2018-09-14 Thread Roger Shimizu
On Mon, Sep 10, 2018 at 11:58 PM, gregor herrmann  wrote:
> On Mon, 10 Sep 2018 10:43:32 -0400, Antoine Beaupré wrote:
>
>> Disabling the apparmor profiles fix this:
>>
>> aa-complain torbrowser.Tor.tor
>> aa-complain torbrowser.Browser.firefox
>
> After upgrading to 0.2.9-4, adequate complains:
>
> torbrowser-launcher: obsolete-conffile 
> /etc/apparmor.d/local/torbrowser.Tor.tor
> torbrowser-launcher: obsolete-conffile 
> /etc/apparmor.d/local/torbrowser.Browser.plugin-container
> torbrowser-launcher: obsolete-conffile 
> /etc/apparmor.d/local/torbrowser.Browser.firefox

Sorry, I don't have these errors when upgrading package.


# dpkg -i torbrowser-launcher_0.2.9-4_amd64.deb
(Reading database ... 272719 files and directories currently installed.)
Preparing to unpack torbrowser-launcher_0.2.9-4_amd64.deb ...
Unpacking torbrowser-launcher (0.2.9-4) over (0.2.9-3) ...
Setting up torbrowser-launcher (0.2.9-4) ...
Installing new version of config file
/etc/apparmor.d/torbrowser.Browser.firefox ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for man-db (2.7.6.1-2) ...


> After getting rid of them, I have a starting torbrowser again.
>
> Looks like some dpkg-maintscript-helper(1) magic is needed here ...

Could you provide an example, or even patch?
Thanks!

BTW. I have pushed not-released-yet 0.2.9-5 to branch debian/sid on salsa.
Maybe you can simply build the package by git-buildpackage, and test
the latest appamor profile from intrigeri.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1



Bug#908852: Debian Stretch can't be installed or booted on Apollo Lake systems.

2018-09-14 Thread Carlos Alberto Lopez Perez
Package: grub-efi-amd64
Version: 2.02~beta3-5
Severity: important
Tags: d-i patch


There is a bug in the version of Grub2 shipped in Debian stable that renders
grub unable to boot in Apollo Lake systems (this are usually recent netbooks
or ultrabooks with Celeron/Atom CPUs).

The issue is that the EFI binary generated by Grub2 from Stretch hangs this
systems completely.

See: https://medium.com/@pawitp/grub-2-issue-on-intel-n4200-97c12d4db8af

The fix is simply to backport this patch 
https://git.savannah.gnu.org/cgit/grub.git/commit/?id=446794de8da4329ea532cbee4ca877bcafd0e534
(which applies cleanly over the grub version in Stretch).


I think it will be a good idea to release a new version of Grub2 for stable
with this patch and generate a new image of the debian installer.

Otherwise it is impossible (well, not impossible, but very difficult) to
install Debian Stretch on this systems.


Note that Debian testing is not affected, as this patch is already included
there. The fix is only necessary for Stretch.


I attach a debdiff of a backport I did myself. I have verified that Debian
Stretch boots fine on my Yepo 737A laptop (Apollo Lake) with this new version
of Grub2.
diff -Nru grub2-2.02~beta3/debian/changelog grub2-2.02~beta3/debian/changelog
--- grub2-2.02~beta3/debian/changelog	2017-02-11 16:09:19.0 +0100
+++ grub2-2.02~beta3/debian/changelog	2018-09-15 01:51:02.0 +0200
@@ -1,3 +1,10 @@
+grub2 (2.02~beta3-6) stable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix boot on Apollo Lake EFI systems.
+
+ -- Carlos Alberto Lopez Perez   Sat, 15 Sep 2018 01:51:02 +0200
+
 grub2 (2.02~beta3-5) unstable; urgency=medium
 
   [ Steve McIntyre ]
diff -Nru grub2-2.02~beta3/debian/patches/fix_boot_apollo_lake.patch grub2-2.02~beta3/debian/patches/fix_boot_apollo_lake.patch
--- grub2-2.02~beta3/debian/patches/fix_boot_apollo_lake.patch	1970-01-01 01:00:00.0 +0100
+++ grub2-2.02~beta3/debian/patches/fix_boot_apollo_lake.patch	2018-09-15 01:49:57.0 +0200
@@ -0,0 +1,31 @@
+From 446794de8da4329ea532cbee4ca877bcafd0e534 Mon Sep 17 00:00:00 2001
+From: "David E. Box" 
+Date: Fri, 15 Sep 2017 15:37:05 -0700
+Subject: tsc: Change default tsc calibration method to pmtimer on EFI systems
+
+On efi systems, make pmtimer based tsc calibration the default over the
+pit. This prevents Grub from hanging on Intel SoC systems that power gate
+the pit.
+
+Signed-off-by: David E. Box 
+Reviewed-by: Daniel Kiper 
+---
+ grub-core/kern/i386/tsc.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/grub-core/kern/i386/tsc.c b/grub-core/kern/i386/tsc.c
+index 2e85289..f266eb1 100644
+--- a/grub-core/kern/i386/tsc.c
 b/grub-core/kern/i386/tsc.c
+@@ -68,7 +68,7 @@ grub_tsc_init (void)
+ #ifdef GRUB_MACHINE_XEN
+   (void) (grub_tsc_calibrate_from_xen () || calibrate_tsc_hardcode());
+ #elif defined (GRUB_MACHINE_EFI)
+-  (void) (grub_tsc_calibrate_from_pit () || grub_tsc_calibrate_from_pmtimer () || grub_tsc_calibrate_from_efi() || calibrate_tsc_hardcode());
++  (void) (grub_tsc_calibrate_from_pmtimer () || grub_tsc_calibrate_from_pit () || grub_tsc_calibrate_from_efi() || calibrate_tsc_hardcode());
+ #elif defined (GRUB_MACHINE_COREBOOT)
+   (void) (grub_tsc_calibrate_from_pmtimer () || grub_tsc_calibrate_from_pit () || calibrate_tsc_hardcode());
+ #else
+-- 
+cgit v1.0-41-gc330
+
diff -Nru grub2-2.02~beta3/debian/patches/series grub2-2.02~beta3/debian/patches/series
--- grub2-2.02~beta3/debian/patches/series	2017-02-11 16:03:45.0 +0100
+++ grub2-2.02~beta3/debian/patches/series	2018-09-15 01:50:47.0 +0200
@@ -57,3 +57,4 @@
 efinet_set_network_from_uefi_devpath.patch
 efinet_set_dns_from_uefi_proto.patch
 grub-install-efibootmgr-check.patch
+fix_boot_apollo_lake.patch


signature.asc
Description: OpenPGP digital signature


Bug#908851: duplicity: fails with NameError when restoring data using ignore-errors option

2018-09-14 Thread Damien Jegou
Package: duplicity
Version: 0.7.18.1-1
Severity: normal

Dear Maintainer,

I found this bug while restoring with duplicity using --ignore-errors flag :

NameError: global name 'util' is not defined

(full traceback is 100% identical to the one in the bug description, see
the link to duplicity's bug tracker).

Bug already reported and solved upstream in duplicity 0.7.12 (debian 9.5
version is 0.7.11-1) : 
https://bugs.launchpad.net/duplicity/+bug/1671852

I applied the fix on my system and I not longer get this error message.


System Information below modified because reportbug was launched on my desktop
instead of the machine where the bug was found (rookie mistake, first
usage of reportbug for me).

Regards,
Damien Jegou.

-- System Information:
Debian Release: 9.5
  APT prefers stable
Architecture: amd64 (x86_64)

-- no debconf information



Bug#908733: redshift: Unable to run, unable to connect to geoclue, unable to get location from provider, free desktop access denied geolocation. disalbed for uid 1000

2018-09-14 Thread Ritesh Raj Sarraf
Please fix your geoclue2 setup. Custom configs for redshift work perfect
and so does properly set geoclue2 setup.



s3nt fr0m a $martph0ne, excuse typ0s

On Thu, Sep 13, 2018, 15:09 Ervin  wrote:

> Package: redshift
> Version: 1.11-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate
> ***
>
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
>
> *** End of the template - remove these template lines ***
>
>
>
> -- System Information:
> Debian Release: 9.5
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages redshift depends on:
> ii  libc6   2.24-11+deb9u3
> ii  libdrm2 2.4.74-1
> ii  libglib2.0-02.50.3-2
> ii  libx11-62:1.6.4-3
> ii  libxcb-randr0   1.12-1
> ii  libxcb-render0  1.12-1
> ii  libxcb1 1.12-1
> ii  libxxf86vm1 1:1.1.4-1+b2
>
> Versions of packages redshift recommends:
> ii  geoclue-2.0  2.4.5-1
>
> redshift suggests no packages.
>
> -- no debconf information
>


Bug#908850: [sponsorship-requests] Need sponsor and maintainer status for geneweb package

2018-09-14 Thread Guillaume Brochu
Package: sponsorship-requests
Severity: normal

---

Hi,


For the last two years, I have worked on the maintenance of the geneweb
package with the help & sponsorship of Christian Perrier (which is still
the official maintainer of the package).
https://tracker.debian.org/pkg/geneweb
https://salsa.debian.org/GuillaumeBrochu-guest/geneweb-package-test

I would like to continue the work on the package, including the migration
of the git repository to Salsa. However, in a recent private communication
with Christian, he informed me that he is no longer available to continue
the sponsorship and package maintenance, and referred me to debian-mentors.

Therefore, I need a new sponsor to continue the work. My objectives are :
- migration of the git repository to Salsa (which was previously here :
https://anonscm.debian.org/cgit/collab-maint/geneweb.git/)
- fix an old bug with the import of a new upstream release and perhaps push
it into the stretch-backports, if possible;
- prepare for Buster;
- start to test the packaging of the next geneweb release (geneweb 7), and
perhaps push it into experimental, if possible.

For this, I need (1) a new sponsor from the Debian developers team and (2)
the transfer of the maintainer status of the geneweb package to me and/or
to the new sponsor.

Thank you and best regards,


Guillaume Brochu


Bug#908849: gerbera: No linefeed before CONNECTION header

2018-09-14 Thread Pelzi
Package: gerbera
Version: 1.1.0+dfsg-2+b2
Severity: normal

Dear Maintainer,

Try to play an audio track served by gerbera using the uPnP protocol. This 
leads to an ordinary http get from client (here VLC running on Mac OS).

As a result, Gerbera will send back an http answer, consisting of an HTTP 
header and content (which is intended to be streamed by the client). Gerbera 
adds "CONNECTION: close" to the last line of the header, whichever that is, 
e.g.: Accept-Ranges: bytesCONNECTION: close
(In certain situations the last header line might happen to be the 
Content-Disposition heder and in that case, VLC turns out to be
uncapable of parsing the header at all and will refuse to play the respective 
track.)

Instead, Gerbera should add another line to the header, i.e.
Accept-Ranges: bytes
CONNECTION: close
These lines must be separated by CR LF, as always in HTTP.


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

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

Versions of packages gerbera depends on:
ii  adduser  3.117
ii  libavformat587:4.0.2-1+b1
ii  libavutil56  7:4.0.2-1+b1
ii  libc62.27-6
ii  libcurl3-gnutls  7.61.0-1
ii  libduktape2032.3.0-1
ii  libexif120.6.21-5
ii  libexiv2-14  0.25-4
ii  libexpat12.2.6-1
ii  libffmpegthumbnailer4v5  2.1.1-0.2+b1
ii  libgcc1  1:8.2.0-5
ii  libixml101:1.8.2-3
ii  libjs-bootstrap  3.3.7+dfsg-2
ii  libjs-jquery 3.2.1-1
ii  libjs-jquery-cookie  12-1
ii  libjs-jquery-ui  1.12.1+dfsg-5
ii  libjs-prototype  1.7.1-3
ii  libmagic11:5.34-2
ii  libmariadbclient18   1:10.1.35-1
ii  libsqlite3-0 3.24.0-1
ii  libstdc++6   8.2.0-5
ii  libtag1v51.11.1+dfsg.1-0.2+b1
ii  libupnp101:1.8.2-3
ii  libuuid1 2.32.1-0.1
ii  lsb-base 9.20170808
ii  zlib1g   1:1.2.11.dfsg-1

gerbera recommends no packages.

Versions of packages gerbera suggests:
ii  firefox-esr [www-browser]  52.9.0esr-1
ii  konqueror [www-browser]4:18.04.0-1
ii  lynx [www-browser] 2.8.9rel.1-2
ii  w3m [www-browser]  0.5.3-36+b1

-- Configuration Files:
/etc/gerbera/config.xml changed [not included]

-- no debconf information



Bug#906466: Upload pending

2018-09-14 Thread Felix Lechner
Control: severity 906466 normal

Hi,

A pending upload is expected to resolve this bug report. To prevent
auto removal, I am downgrading the severity to normal. Thank you!

Felix Lechner



Bug#908848: ITP: python-fleetspeak -- Framework for communicating with a fleet of machines

2018-09-14 Thread Hilko Bengen
Package: wnpp
Owner: Hilko Bengen 
Severity: wishlist

* Package name: python-fleetspeak
  Version : 0.0.7
  Upstream Author : Google
* URL or Web page : https://pypi.org/project/fleetspeak/
* License : Apache-2.0
  Description : Framework for communicating with a fleet of machines

This package will be needed for a GRR upgrade.



Bug#908847: llvm-toolchain-6.0: FTBFS on hurd-i386

2018-09-14 Thread Svante Signell
Source: llvm-toolchain-6.0
Version: 6.0.1-9
Severity: important
Tags: ftbfs, patch
User: debian-h...@lists.debian.org
Usertags: hurd-i386

Hello,

Currently llvm-toolchain-6.0 FTBFS on GNU/Hurd due to missing porting
issues. Attached are three patches to fix this:
lib_Support_Unix_Path.inc.diff
tools_llvm-shlib_CMakeLists.txt.diff
clang_lib_Frontend_ModuleDependencyCollector.cpp.dif

The last patch is a PATH_MAX issue. Maybe it could be integrated with
the already present hurd-pathmax.diff patch.

Additionally the patch debian_rules.diff adds GNU/Hurd to the
architectures capable of using the gold linker.

Thanks!Index: llvm-toolchain-6.0-6.0.1/clang/lib/Frontend/ModuleDependencyCollector.cpp
===
--- llvm-toolchain-6.0-6.0.1.orig/clang/lib/Frontend/ModuleDependencyCollector.cpp
+++ llvm-toolchain-6.0-6.0.1/clang/lib/Frontend/ModuleDependencyCollector.cpp
@@ -97,6 +97,11 @@ struct ModuleDependencyMMCallbacks : pub
 
 }
 
+// For GNU Hurd
+#if defined(__GNU__) && !defined(PATH_MAX)
+# define PATH_MAX 4096
+#endif
+
 // TODO: move this to Support/Path.h and check for HAVE_REALPATH?
 static bool real_path(StringRef SrcPath, SmallVectorImpl ) {
 #ifdef LLVM_ON_UNIX
--- a/debian/rules	2018-09-12 10:48:35.0 +0200
+++ b/debian/rules	2018-09-14 13:35:50.0 +0200
@@ -84,7 +84,7 @@
 	control_vars = '-Vdep:devlibs=libstdc++6-$(GCC_VERSION)-dev'
 endif
 
-BINUTILS_GOLD_ARCHS := amd64 arm64 armhf i386 ppc64 ppc64el sparc sparc64 x32 s390x
+BINUTILS_GOLD_ARCHS := amd64 arm64 armhf i386 ppc64 ppc64el sparc sparc64 x32 s390x hurd-i386
 ifeq ($(shell dpkg --compare-versions $(shell dpkg-query -W -f '$${Version}' binutils) ge 2.23.1-1~exp3 ; echo $$?),0)
 ifneq (,$(filter $(DEB_HOST_ARCH),$(BINUTILS_GOLD_ARCHS)))
 # -fused-ld=gold enables the gold linker (but is not supported by all archs / distro)
Index: llvm-toolchain-6.0-6.0.1/lib/Support/Unix/Path.inc
===
--- llvm-toolchain-6.0-6.0.1.orig/lib/Support/Unix/Path.inc
+++ llvm-toolchain-6.0-6.0.1/lib/Support/Unix/Path.inc
@@ -98,7 +98,7 @@
 #define STATVFS_F_FRSIZE(vfs) static_cast(vfs.f_bsize)
 #endif
 
-#if defined(__NetBSD__)
+#if defined(__NetBSD__) || defined(__GNU__)
 #define STATVFS_F_FLAG(vfs) (vfs).f_flag
 #else
 #define STATVFS_F_FLAG(vfs) (vfs).f_flags
@@ -111,7 +111,7 @@ namespace sys  {
 namespace fs {
 #if defined(__FreeBSD__) || defined(__NetBSD__) || defined(__OpenBSD__) || \
 defined(__minix) || defined(__FreeBSD_kernel__) || defined(__linux__) ||   \
-defined(__CYGWIN__) || defined(__DragonFly__) || defined(_AIX)
+defined(__CYGWIN__) || defined(__DragonFly__) || defined(_AIX) || defined(__GNU__)
 static int
 test_dir(char ret[PATH_MAX], const char *dir, const char *bin)
 {
@@ -187,7 +187,7 @@ std::string getMainExecutable(const char
 
   if (getprogpath(exe_path, argv0) != NULL)
 return exe_path;
-#elif defined(__linux__) || defined(__CYGWIN__)
+#elif defined(__linux__) || defined(__CYGWIN__) || defined(__GNU__)
   char exe_path[MAXPATHLEN];
   StringRef aPath("/proc/self/exe");
   if (sys::fs::exists(aPath)) {
@@ -360,7 +360,7 @@ std::error_code remove(const Twine 
 }
 
 static bool is_local_impl(struct STATVFS ) {
-#if defined(__linux__)
+#if defined(__linux__) || defined(__GNU__)
 #ifndef NFS_SUPER_MAGIC
 #define NFS_SUPER_MAGIC 0x6969
 #endif
@@ -370,7 +370,11 @@ static bool is_local_impl(struct STATVFS
 #ifndef CIFS_MAGIC_NUMBER
 #define CIFS_MAGIC_NUMBER 0xFF534D42
 #endif
+#ifdef __GNU__
+  switch ((uint32_t)Vfs.__f_type) {
+#else
   switch ((uint32_t)Vfs.f_type) {
+#endif
   case NFS_SUPER_MAGIC:
   case SMB_SUPER_MAGIC:
   case CIFS_MAGIC_NUMBER:
Index: llvm-toolchain-6.0-6.0.1/tools/llvm-shlib/CMakeLists.txt
===
--- llvm-toolchain-6.0-6.0.1.orig/tools/llvm-shlib/CMakeLists.txt
+++ llvm-toolchain-6.0-6.0.1/tools/llvm-shlib/CMakeLists.txt
@@ -40,6 +40,7 @@ set_property(TARGET LLVM PROPERTY VERSIO
 list(REMOVE_DUPLICATES LIB_NAMES)
 if(("${CMAKE_SYSTEM_NAME}" STREQUAL "Linux") OR (MINGW) OR (HAIKU)
OR ("${CMAKE_SYSTEM_NAME}" STREQUAL "FreeBSD")
+   OR ("${CMAKE_SYSTEM_NAME}" STREQUAL "GNU")
OR ("${CMAKE_SYSTEM_NAME}" STREQUAL "DragonFly")
OR ("${CMAKE_SYSTEM_NAME}" STREQUAL "SunOS")) # FIXME: It should be "GNU ld for elf"
   configure_file(


Bug#908838: [Aptitude-devel] Bug#908838: aptitude-doc-en: Links to http://debtags.alioth.debian.org/

2018-09-14 Thread Axel Beckert
Control: tag -1 + confirmed
Control: severity -1 normal

Hi,

Mykola Nikishov wrote:
> At least, in file:///usr/share/doc/aptitude/html/en/ch02s04s05.html#searchTag:
> 
> For more information on tags and debtags, see 
> http://debtags.alioth.debian.org. 

Indeed. And there's more alioth URLs which need to be changed:

debian/control:Homepage: https://aptitude.alioth.debian.org/
doc/en/aptitude.xml:  
url='http://cwidget.alioth.debian.org'>.
doc/en/aptitude.xml:  url='http://debtags.alioth.debian.org'/>.
doc/en/aptitude.xml:  url='http://debtags.alioth.debian.org'/>.

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



Bug#881564: A64-OLinuXino

2018-09-14 Thread Rodrigo Exterckötter Tjäder
I built the version of the package on experimental with the patch on
message #10.

Then I installed it and the ATF from atf-allwinner package to a SD
card using "TARGET=/usr/lib/u-boot/a64-olinuxino
u-boot-install-sunxi64 /dev/mmcblk1".

With that SD card on the board I got an U-Boot prompt and managed to
boot into debian-installer using the daily kernel and initrd.

>From that prompt I also managed to boot the Ubuntu installation on the
internal eMMC, and everything seemed to work there.

On the U-Boot prompt neither ethernet nor USB work:

> => dhcp
> No ethernet found.
> => usb start
> starting USB...
> No controllers found

All of this was tested over the serial port, I haven't tested the HDMI
output, nor do I know if it is expected to work.

Even though USB and ethernet are not working I would say the image is
useful enough that it should be included.



Bug#908844: pkg-perl-tools: use xargs -P instead of parallel

2018-09-14 Thread Adam Borowski
Source: pkg-perl-tools
Version: 0.47
Severity: wishlist

Hi!
While looking at users of "parallel" (wrt its licensing problem), I noticed
quite bizarre handling:

PARALLEL=

if which parallel > /dev/null ; then
if parallel --will-cite < /dev/null > /dev/null 2>&1; then
PARALLEL=GNU
else
PARALLEL="moreutils"
fi
else
echo "W: 'parallel' not available, will run sequentially" >&2
echo "W: you may want to install 'parallel' or 'moreutils'" >&2
fi

if [ -n "$PARALLEL" ]; then
if [ "$PARALLEL" = "GNU" ]; then
find . -maxdepth 2 -type d -name .git | \
parallel --will-cite sh -c "GIT_DIR='{}' git gc --quiet"
else
find . -maxdepth 2 -type d -name .git -print0 | \
xargs -r0 parallel -i sh -c "GIT_DIR='{}' git gc --quiet" --
fi
else

All this complexity just because bin:parallel installs an incompatible
executable for this name and diverts it over moreutils' version...

But, there's an even simpler option: use "xargs -P".  You even already
have xargs in the code above...  As xargs is in an Essential package,
you won't even need any dependency anymore.


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

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



Bug#908846: revolt: have a recentish revolt package and have xdg-portal-gtk as a runtime dependency for desktop notifications

2018-09-14 Thread shirish शिरीष
Package: revolt
Version: 0.0+git20170627.3f5112b-3
Severity: wishlist

Dear Maintainer,

Revolt seem to be going through quite a bit of changes, maybe we could
benefit from it.

See https://github.com/aperezdc/revolt/commits/master . I did see
https://salsa.debian.org/matrix-team/revolt.git so it makes sense if
we can have those changes perhaps.


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

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

Versions of packages revolt depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.0-1
ii  gir1.2-webkit2-4.0   2.20.5-1
ii  python3  3.6.5-3
ii  python3-gi   3.28.3-1

revolt recommends no packages.

revolt suggests no packages.

-- no debconf information


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



Bug#908845: dh_gconf: Time to deprecate dh_gconf?

2018-09-14 Thread Jeremy Bicha
Source: debhelper
Version: 11.4
X-Debbugs-CC: gc...@packages.debian.org

My understanding is that we will try to remove gconf from Debian
during the Bullseye cycle. Generally, things that used gconf should
switch to gsettings

I noticed that dh_gconf was mentioned in the most recent debhelper
changelog entry and wondered if it would make sense to formally
deprecate dh_gconf.

I'm not sure what your release schedule is, but maybe dh_gconf should
be removed in compat level 13?

References

https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html


Thanks,
Jeremy Bicha



Bug#908843: terminology: Please add support for WINDOWID environment variable

2018-09-14 Thread Sebastian Reichel
Package: terminology
Version: 1.2.1-1
Severity: wishlist
Tags: upstream

Hi,

Please add support for setting the WINDOWID environment variable,
which is done for example by Xterm and most libvte terminal emulators.
It's a very useful feature to automatically set a nice icon with
xseticon based on the running application.

-- Sebastian



Bug#907079: Not using SNI

2018-09-14 Thread Sebastian Andrzej Siewior
control: tags -1 patch
https://github.com/jcristau/imaplib2/commit/a7ce7da1d573849ac2e1d740d8f3238e0ad8d88c

Sebastian



Bug#908101: thank you for the quick reply Hubert

2018-09-14 Thread shirish शिरीष
Dear Hubert,

Just found out where the nheko git repo. is at
https://salsa.debian.org/matrix-team/nheko, have subscribed to the git
repo. please let me know whenever you have something for me to test.
Am on Debian testing.

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



Bug#907493: ghostscript breaks cups autopkgtest: test times out

2018-09-14 Thread Jonas Smedegaard
Quoting Jonas Smedegaard (2018-08-31 01:25:24)
> Quoting Paul Gevers (2018-08-29 20:24:49)
> > Control: tags -1 moreinfo
> > 
> > Hi,
> > 
> > On 29-08-18 20:20, Jonas Smedegaard wrote:
> > > Thanks - that is indeed helpful, but provides only the _cups_ commands.
> > > 
> > > Inside those are some Ghostscript command (and some data) which I would 
> > > need to check if/what fails with Ghostscript.
> > 
> > Both of them are "ELF 64-bit LSB shared object" so it would help if the
> > cups maintainers could help here.
> 
> Do the freshly released experimental Ghostscript release help anything?

Another release of Ghostscript is now in experimental.  Can someone 
please test if those autopkgtests still fail?

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#895320: ps2pdf crashes

2018-09-14 Thread Jonas Smedegaard
A new release of ghostscript is now in experimental.

Could you please help test if that succeeds?

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#908842: libsdl2: Vulkan support not enabled

2018-09-14 Thread Sean Bryant
Source: libsdl2
Version: 2.0.8
Severity: important
Tags: patch

Dear Maintainer,

   * What led up to the situation?
Ryan Gordon asked on twitter if anyone knew about why Vulkan was disabled in
the Ubuntu libsdl2 package. I tracked this down the Debian source package.
Simon Quigley, an Ubuntu developer confirmed this and asked for it to be fixed
upstream in Debian.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I looked at the commit history and found Vulkan support was disabled with a
note about the package failing to build when Vulkan was enabled. I tracked down
the reason the package failed to build to another option, `SDL_LoadObject` also
being disabled. The commit history doesn't go back far enough to explain why
`SDL_LoadObject` support was also disabled. I sent an email to the sdl
maintainers list to see if I could get some insight but I haven't heard back
and decided to file a bug report.
   * What was the outcome of this action?
I created a patch to enable Vulkan support and SDL_LoadObject support.



-- 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)
>From 5ea55937182a883ad97a51785e1a6936ed4a9bb2 Mon Sep 17 00:00:00 2001
From: Sean Bryant 
Date: Wed, 12 Sep 2018 21:26:53 -0700
Subject: [PATCH] enable vulkan support on linux

---
 debian/rules | 5 +
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/debian/rules b/debian/rules
index 3a28a85..9cc5089 100755
--- a/debian/rules
+++ b/debian/rules
@@ -5,7 +5,7 @@ SHLIBVER = 2.0.8
 DEB_HOST_ARCH_CPU ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU)
 DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
 
-confflags = --disable-rpath --enable-sdl-dlopen --disable-loadso \
+confflags = --disable-rpath --enable-sdl-dlopen --enable-loadso \
 --disable-nas --disable-esd --disable-arts \
 --disable-alsa-shared --disable-pulseaudio-shared \
 --enable-ibus \
@@ -36,9 +36,6 @@ ifeq (kfreefsd,$(findstring kfreebsd,$(DEB_HOST_ARCH_CPU)))
   confflags += --disable-video-wayland
 endif
 
-# the SDL module for Vulkan not compiling even in Linux at the moment
-confflags += --disable-video-vulkan
-
 # disable OpenGLES on Hurd, it does not support it at the moment
 ifeq (hurd,$(findstring hurd,$(DEB_HOST_ARCH_CPU)))
   confflags += --disable--video-opengles
-- 
2.11.0



Bug#908841: add description on systemd timer to cronjob

2018-09-14 Thread Harlan Lieberman-Berg
Package: certbot
Severity: wishlist

As requested by jmorahan in 
https://community.letsencrypt.org/t/certbot-dovecot-postfix-certificate-renewal-issue/72226/11,
we should add descriptive text to the cronjob reminding users that the
systemd timer is controlling if installed.



Bug#904261: [pkg-go] Bug#904261: dh-golang: Don't install files listed in DH_GOLANG_EXCLUDES to dev pacakge

2018-09-14 Thread Clément Hermann
On 9/14/18 3:11 PM, Martín Ferrari wrote:
> On 12/09/18 15:59, Martín Ferrari wrote:
> 
>>> I'm not sure it warrants an upload right away, but it would be nice to
>>> have it before debhelper is updated.
>>>
>>> Could anyone sponsor that ?
>>
>> I would be happy to, but I have not been following dh-golang devel much
>> to decide if we sHould upload now.. Any other opinion?
> 
> I have just uploaded it.
> 
> 

Thanks !

-- 
nodens



Bug#908540: redis: FTBFS randomly (failing tests)

2018-09-14 Thread Santiago Vila
On Tue, Sep 11, 2018 at 08:54:49AM +0100, Chris Lamb wrote:

> I would be curious to know whether you can reproduce there as
> I am likely to merge that into unstable soon.

I've just noticed that the package FTBFS in experimental in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/redis.html

in four different architectures.

Would that be enough to consider that the problem is most probably not
fixed in experimental?

Thanks.



Bug#905068: ITP: golang-github-canonicalltd-dqlite -- Distributed SQLite for Go applications

2018-09-14 Thread Clément Hermann
Hey,

thanks for the quick response!

On 9/14/18 2:24 PM, Free Ekanayaka wrote:
> Hey there,
> 
> I do have the intention to submit the patches upstream, but since 1) the
> work is not fully complete 2) SQLite authors are *extremely*
> conservative when it comes to contributions, that won't happen any time
> soon.

Totally understand.

> Is there anything that prevents you from going with second option? You
> can grab:
> 
> https://github.com/CanonicalLtd/sqlite/releases/tag/version-3.24.0%2Breplication3
> 
> and package it as a new sqlite-replication library. It's fairly safe to
> have it Conflict and Replace the regular sqlite package, since the
> patches onlly add things, they don't modify behavior or change APIs.

That's good to know (the "add only")!

>From the top of my mind, it should be possible, but I need to recheck
the policy, see how other forks do it, and ask the current maintainer of
sqlite3 how they feel about it. Especially as I'm not so familiar with
shared library packaging ^^

I guess normally, it would involve providing a virtual package and
changing the original sqlite3 to do the same. At least that's how it's
done for Mysql/mariadb for instance, but here there is no server binary
in sqlite3, so the situation is a bit different.

If the implementation used a different name, that would allow to have
both installed. Of course, That involves patching the go bindings as
well, and it would have to change again once the patches to sqlite3 are
accepted upstream. If it can indeed take a long time, maybe it's worth it ?


Cheers,

-- 

nodens



Bug#908840: gimp complains about Missing fast-path babl conversion detected

2018-09-14 Thread shirish शिरीष
Package: gimp
Version: 2.10.6-3
Severity: normal

Dear Maintainer,

I was using gimp with an image when saw the warnings on the console -

~/Pictures$ gimp riot-web-settings-screenshot.png
Missing fast-path babl conversion detected, Implementing missing babl fast paths
accelerates GEGL, GIMP and other software using babl, warnings are printed on
first occurance of formats used where a conversion has to be synthesized
programmatically by babl based on format description

*WARNING* missing babl fast path(s): "R'G'B' double" to "CIE Lab double"
*WARNING* missing babl fast path(s): "cairo-ARGB32" to "R'G'B'A u8"

I did see it's a common warning and some have also experienced crashes due to it
as well.

https://forum.manjaro.org/t/missing-fast-path-babl-conversion-detected/50518

While am not experiencing crashes atm, the warnings are disconcerting
at the very least.

FWIW, I did as shared on the manjaro thread without any discernable result -

~/.config$ mv GIMP/ GIMP_old/

$ gimp
Missing fast-path babl conversion detected, Implementing missing babl fast paths
accelerates GEGL, GIMP and other software using babl, warnings are printed on
first occurance of formats used where a conversion has to be synthesized
programmatically by babl based on format description

*WARNING* missing babl fast path(s): "R'G'B' double" to "CIE Lab double"
*WARNING* missing babl fast path(s): "cairo-ARGB32" to "R'G'B'A u8"

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

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

Versions of packages gimp depends on:
ii  gimp-data2.10.6-3
ii  libaa1   1.4p5-44+b2
ii  libbabl-0.1-00.1.56-1
ii  libbz2-1.0   1.0.6-9
ii  libc62.27-6
ii  libcairo21.15.12-1
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.2.0-6
ii  libgdk-pixbuf2.0-0   2.36.12-2
ii  libgegl-0.4-00.4.8-1+b1
ii  libgexiv2-2  0.10.8-1
ii  libgimp2.0   2.10.6-3
ii  libglib2.0-0 2.56.1-2
ii  libgs9   9.22~dfsg-2.1
ii  libgtk2.0-0  2.24.32-3
ii  libgudev-1.0-0   232-2
ii  libharfbuzz0b1.8.8-2
ii  libheif1 1.3.2-1
ii  libilmbase23 2.2.1-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3
ii  liblzma5 5.2.2-1.3
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.3-0 1.3.0-2
ii  libopenexr23 2.2.1-4
ii  libopenjp2-7 2.3.0-1
ii  libpango-1.0-0   1.42.4-1
ii  libpangocairo-1.0-0  1.42.4-1
ii  libpangoft2-1.0-01.42.4-1
ii  libpng16-16  1.6.34-2
ii  libpoppler-glib8 0.63.0-2
ii  librsvg2-2   2.40.20-3
ii  libstdc++6   8.2.0-6
ii  libtiff5 4.0.9-6
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libwmf0.2-7  0.2.8.4-12
ii  libx11-6 2:1.6.6-1
ii  libxcursor1  1:1.1.15-1
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages gimp recommends:
ii  ghostscript  9.22~dfsg-2.1

Versions of packages gimp suggests:
ii  gimp-data-extras  1:2.0.2-1
ii  gimp-help-en [gimp-help]  2.8.2-0.1
pn  gimp-python   
ii  gvfs-backends 1.36.2-1
ii  libasound21.1.6-1

-- no debconf information


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



Bug#908839: Some of my stretch ssh clients can no longer negotiate chacha20-poly1305

2018-09-14 Thread James Cloos
Package: openssh-client
Version: 1:7.6p1-2
Severity: important
File: openssh

This is not the machine which shows this error; I was unable to
install reportbug there due to:

  reportbug : Depends: python3-reportbug (= 7.1.7+deb9u2) but it is not going 
to be installed

On that other machine, any mention of chacha20-poly1...@openssh.com in
the Ciphers list before an alg which both sides support prevents
cipher negotiation.

Other stretch machines work fine (including this one, which already
had reportbug installed).

The other machine is also on 1:7.6p1-2, and is configured very similarly.

One interesting thing from -vv output, is that it ends with:

  Unable to negotiate with IP.ADD.RE.SS port NUM: no matching cipher found. 
Their offer: 
aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.comssh.com,aes256-...@openssh.com

Note the aes256-...@openssh.comssh.com in there.

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

Kernel: Linux 2.6.32-042stab127.2 (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: sysvinit (via /sbin/init)

Versions of packages openssh-client depends on:
ii  adduser   3.116
ii  dpkg  1.19.0.5
ii  libc6 2.25-6
ii  libedit2  3.1-20170329-1
ii  libgssapi-krb5-2  1.15.2-2
ii  libselinux1   2.7-2
ii  libssl1.0.2   1.0.2n-1
ii  passwd1:4.5-1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages openssh-client recommends:
pn  xauth  

Versions of packages openssh-client suggests:
pn  keychain  
pn  libpam-ssh
pn  monkeysphere  
pn  ssh-askpass   

-- no debconf information



Bug#644632: Patch needed

2018-09-14 Thread Bernhard Schmidt
Am 14.09.18 um 21:44 schrieb Christoph Biedl:

Hi,


>> Since nfdump is now started in a systemd unit this needs to be
>> implemented differently, preferably with a systemd generator and
>> instances. Patches (tested, preferably upstreamable) are welcome.
> 
> Still interested? I came into a similar situation in softflowd and
> solved it in the just-uploaded 0.9.9-4. Bonus: Even SysV init is still
> supported. Adjustment for nfcapd should be fairly simple.
> 
> This would also overriding any default settings, thus resolve #843602

Sure, feel free to push directly into the salsa repository and upload.

Bernhard



Bug#908838: aptitude-doc-en: Links to http://debtags.alioth.debian.org/

2018-09-14 Thread Mykola Nikishov
Package: aptitude-doc-en
Version: 0.8.11-3
Severity: minor

At least, in file:///usr/share/doc/aptitude/html/en/ch02s04s05.html#searchTag:

For more information on tags and debtags, see 
http://debtags.alioth.debian.org. 

-- System Information:
Debian Release: buster/sid
  APT prefers stable
  APT policy: (900, 'stable'), (190, 'testing'), (180, 'unstable'), (170, 
'experimental')
Architecture: amd64 (x86_64)

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

aptitude-doc-en depends on no packages.

aptitude-doc-en recommends no packages.

Versions of packages aptitude-doc-en suggests:
ii  aptitude  0.8.11-3

-- no debconf information



Bug#772479: irssi-plugin-xmpp does not work at all on buster

2018-09-14 Thread Antoine Beaupré
On 2018-09-14 14:41:03, Daniel Kahn Gillmor wrote:
> Control: severity 772479 grave
>
> I've got these packages installed:
>
> ii  irssi 1.1.1-1  amd64terminal based IRC client
> ii  irssi-plugin-xmpp 0.54-2   amd64XMPP plugin for irssi
>
> and if i launch a new irssi installation and do:
>
> /load xmpp
>
> then it responds with:
>
> 13:10 -!- Irssi: xmpp/core is ABI version 7 but Irssi is version 13, cannot 
> load
> 13:10 -!- Irssi: Error loading module xmpp/fe: 
>   /usr/lib/x86_64-linux-gnu/irssi/modules/libfe_xmpp.so: undefined 
>   symbol: xmpp_subscription
>
> so irssi-plugin-xmpp does not work at all, rendering this bug report
> severity grave. :(

I think this needs a binNMU.

Alternatively, we could just rebuild to ship what's pending in git and
do some administrativa. Upstream has no new release but two minor
bugfixes/commits.

a.

-- 
The United States is a nation of laws:
badly written and randomly enforced.
- Frank Zappa



Bug#908248: Patch available but not part in mainstream

2018-09-14 Thread Romain Perier
On Mon, Sep 10, 2018 at 08:15:29PM +, tomas.lac...@binaryx.eu wrote:
> Hello team,
> 
> There seems to be patch available, but not part of upstream kernel source yet 
> (checked against 4.18.7 git), provided by AMD employee.
> Applied the patch listed from page below to 4.18.6 kernel from kernel.org and 
> no issues visible related to udev stuck as reported before.
> 
> https://lore.kernel.org/patchwork/patch/974869/ 
> (https://lore.kernel.org/patchwork/patch/974869/)
> 
> BRTL

Hello,

Merge request opened, see 
https://salsa.debian.org/kernel-team/linux/merge_requests/62
(it depends on previous opened merge request, just focus on the HEAD commit)

Thanks,
Regards,
Romain



Bug#908172: update

2018-09-14 Thread Laurent Demailly
It now works and passes lintian:
https://github.com/fortio/fortio/tree/master/debian
you can see the produced x86 artifacts on
https://github.com/fortio/fortio/releases/tag/v1.3.0



Bug#906472: horst: FTBFS in buster/sid (unable to open 'stdarg.h')

2018-09-14 Thread Uwe Kleine-König
Hello,

[Cc += sparse mailing list]

On Fri, Sep 14, 2018 at 05:04:09PM +0300, Adrian Bunk wrote:
> Control: reassign -1 sparse 0.5.2-1
> Control: affects -1 src:horst
> 
> On Sat, Aug 25, 2018 at 10:09:47PM +0200, Christoph Biedl wrote:
> > Santiago Vila wrote...
> > 
> > >   make -j1 check
> > > make[1]: Entering directory '/<>'
> > > sparse -g -O2 -fdebug-prefix-map=/<>=. 
> > > -fstack-protector-strong -Wformat -Werror=format-security -std=gnu99 
> > > -Wall -Wextra -g -I. -DDO_DEBUG -I/usr/include/libnl3 *.[ch]
> > > /usr/include/err.h:25:11: error: unable to open 'stdarg.h'
> > 
> > To reproduce this it's important to remove gcc-7 from the build chroot
> > (apt purge libgcc-7-dev ; apt --purge autoremove).
> > 
> > Problem is, sparse appearently uses hardcoded paths and looks for
> > stdarg.h in (among other places)
> > 
> > | /usr/lib/gcc/x86_64-linux-gnu/7//include/stdarg.h
> > |   ^
> > 
> > ... which fails.
> > 
> > Solution is to rebuild sparse, building horst was successful then.
> > If this is true (please check!), the interesting question is why this
> > wasn't a problem in earlier gcc version bumps.

I think this is a known limitation of sparse and there are three
ways to fix this (in my order of preference):

 a) let horst use cgcc -no-compile instead of sparse; or
 b) let sparse depend on libgcc-7-dev (or whatever provides the
necessary files); or
 c) use autodetection which gcc is used and pick its files.

I'm not sure if a) fixes the problem. It fixed another problem we had
with horst's usage of sparse in the past though[1].

The downside of c) is that running this autodetection on every call to
sparse is probably slowing down sparse a bit which isn't nice.

Best regards
Uwe

[1] https://bugs.debian.org/873508


signature.asc
Description: PGP signature


Bug#644632: Patch needed

2018-09-14 Thread Christoph Biedl
Bernhard Schmidt wrote...

> Since nfdump is now started in a systemd unit this needs to be
> implemented differently, preferably with a systemd generator and
> instances. Patches (tested, preferably upstreamable) are welcome.

Still interested? I came into a similar situation in softflowd and
solved it in the just-uploaded 0.9.9-4. Bonus: Even SysV init is still
supported. Adjustment for nfcapd should be fairly simple.

This would also overriding any default settings, thus resolve #843602

Cheers,

Christoph


signature.asc
Description: PGP signature


Bug#908837: ITP: python-grpc-tools -- Protobuf code generator for gRPC

2018-09-14 Thread Chris Lamb
Package: wnpp
Severity: wishlist
Owner: la...@debian.org
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: python-grpc-tools
  Version : 1.14.1-1
* URL : https://grpc.io/
* License : Apache-2.0
  Programming Lang: Python/C++
  Description : Protobuf code generator for gRPC (Python 3)

gRPC is a modern open source high performance RPC framework. It can
efficiently connect services in and across data centers with pluggable support
for load balancing, tracing, health checkin and authentication. 

It is also applicable in last mile of distributed computing to connect
devices, mobile applications and browsers to backend services.

This package installs the Protobuf code generator for Python 3.


Regards,

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



Bug#908500: cups-browsed: Please consider making cups-browsed a Suggests:

2018-09-14 Thread Brian Potkin
eOn Mon 10 Sep 2018 at 15:16:44 +0100, Brian Potkin wrote:

> Package: cups-browsed
> Version: 1.21.2-1
> Severity: wishlist
> 
> 
> With the introduction of cups 1.6.x the situation in respect to printing
> to remote print queues and printers would have been dire without the
> creation of cups-browsed. However, cups 2.2.4 and later has the ability
> (CUPS Issue #4993) to enumerate queues and printers in print dialogs and
> to auto-create a temporary print queue. This is used by applications
> having the Qt dialog and printing from the command line, although the
> GTK dialog still does its own thing.

Enumeration of queues/printers in GTK apps depends neither on CUPS nor
cups-browsed. A user printing only from GTK apps gains nothing in basic
printing terms from cups-browsed, even if the cups service is operative.

> cups-browsed is installed by default because cups-daemon (quite rightly)
> recommends it. With the changed situation in CUPS and applications it
> would appear that cups-browsed has less relevance with regard to printer
> and print queue discovery and management. The Recommends field lists
> packages that would be found with the cups package because there is a
> strong dependency between it and cups-browsed. cups-browsed would still
> enhance cups if changed to a Suggests:.

A rough characterisation of a recommended package: OMG! cups-browsed
isn't on the system; I cannot do these fundamental and useful things.

"fundamental" and "useful" are arguable, of course, but the ability
of cups-browsed to alter what a GTK app shows would be under the
heading of "Enhances".
 
> The installation of cups-browsed almost as a matter of course on many
> buster systems also masks bugs in CUPS and applications, as it will take
> over the management of queues/printers. A small example is CUPS Issue
> #5045. Another example is with okular. For me, it will not print to a
> temporary queue; with a local cups-browsed queue it will. This would
> probably pass unnoticed as things stand now.

A compromise. Reduce cups-browsed to a Suggests: from now until nearly
the end of the freeze. Give CUPS a better chance to show what it is
capable of without cups-browsed. Return cups-browsed to a Recommends:
before the freeze end if it is indicated. As it stands at present, CUPS
is crippled.

I suppose a major consideration for Debian 10 is to consider what
harm not having cups-browsed as a Recommends: does; it is basically
a printer setup utility like s.c.p. Nobody gets upset when that is
not automatically on the system.

Regards,

Brian.



Bug#908828: tracker.debian.org appears to report that the source package is to be removed, even though it's just the binary

2018-09-14 Thread Raphael Hertzog
Control: reassign -1 qa.debian.org
Control: affects -1 tracker.debian.org

On Fri, 14 Sep 2018, Daniel Kahn Gillmor wrote:
> https://tracker.debian.org/pkg/knot-resolver shows:
> 
>  RM: This package has been requested to be removed.
[...]
> however, #908755 only requests removal of the *binary* package for
> knot-resolver on one architecture (arm64).  The source package itself

This is shown because the RM bug is listed in
https://qa.debian.org/data/bts/wnpp_rm

We don't have any detail about the RM bug. Arguably this file should not
list removal requests for binaries. But this is not under
tracker.debian.org's territory so I'm just reassigning the bug.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/



Bug#908705:

2018-09-14 Thread Damián Barberón
The patches pushed recently from the upstream fixes this. See 


https://gitlab.gnome.org/Jehan/glib/commit/8519368c0eb26ce353e5e1ffd4d23fe8353848dc



Bug#897072: RFS: btrfs-progs/4.17-1~bpo9+1

2018-09-14 Thread Chris Lamb
Nicholas,

> [I] wrote the attached convenience script ;-)  Unfortunately the
> script requires a manual 'apt policy package'

Codswallop. *grin*

How about (untested):

  $ rmadison --suite=stretch-backports $(dpkg-parsechangelog -SSource) \
  | awk '{ print $3 }' | grep . || echo '0~'

Regards,

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



Bug#772479: irssi-plugin-xmpp does not work at all on buster

2018-09-14 Thread Daniel Kahn Gillmor
Control: severity 772479 grave

I've got these packages installed:

ii  irssi 1.1.1-1  amd64terminal based IRC client
ii  irssi-plugin-xmpp 0.54-2   amd64XMPP plugin for irssi

and if i launch a new irssi installation and do:

/load xmpp

then it responds with:

13:10 -!- Irssi: xmpp/core is ABI version 7 but Irssi is version 13, cannot load
13:10 -!- Irssi: Error loading module xmpp/fe: 
  /usr/lib/x86_64-linux-gnu/irssi/modules/libfe_xmpp.so: undefined 
  symbol: xmpp_subscription

so irssi-plugin-xmpp does not work at all, rendering this bug report
severity grave. :(

--dkg


signature.asc
Description: PGP signature


Bug#903579: FWIW I have filed the bug on Debian's behalf

2018-09-14 Thread Sandro Tosi
> While I know barely anything about python, I did however file the bug
> as shared by Bas and maintained by Sandro Tosi as
> https://bugs.python.org/issue34684?@template=item&@pagesize=50&@startwith=0

as you said, you dont know much about python, so please refrain from
engaging in conversations with upstream projects. in particular
CPython is definitely not the right project to open a bug to, most
likely there's no right project and it's something that Debian will
have to handle internally.

if you want to spam the debian bts with your reports, just do that
(well, we can agree some of your reports tend to be really low quality
so you may prefer to engage in discussion in user-support forum first,
such as mailing lists and forum listed at
https://www.debian.org/support) but please dont report bugs upstream
if you're not 100% sure that's the right thing to do.

> @Sandro Tosi maybe you could enlighten upstream more about the issue
> and see if a fix is possible.

there's nothing to enlighten here, CPython is the wrong recipient for this.

Thanks,

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi



Bug#870286: btrfs-progs: btrfs-convert is missing

2018-09-14 Thread Nicholas D Steeves
On Sun, Aug 19, 2018 at 04:31:55PM -0400, Ryan Kavanagh wrote:
> On Mon, Jul 31, 2017 at 05:50:44PM +0200, Adam Borowski wrote:
> > > btrfs-progs (4.12-1) unstable; urgency=medium
> > >   [ Nicholas D Steeves ]
> > >   * Drop btrfs-convert (Closes: #824895, #854489)
> >
> > Yes, there are some caveats, but the man page discusses them at length.
> 
> If you decide to continue to exclude btrfs-convert from btrfs-progs,
> please also drop the manpage:
> 
> rak@zeta:~$ dpkg -S btrfs-convert
> btrfs-progs: /usr/share/man/man8/btrfs-convert.8.gz
> 
> It took me a bit of searching to figure out why there was a manpage but
> no associated binary.

Ryan, You're 100% right.  Duncan, on linux-btrfs, also suggested the
possibility of shipping a dummy script, and it would be easier to
maintain one of those (eg: like fsck.btrfs) than to rebase a patch
with every release.  Please ping me if references to btrfs-convert
aren't patched out by mid-October.  Dmitri, I'm guessing you'll prefer
the dummy script?

Re: upstream btrfs-convert status, there was recently a thread on
linux-btrfs@vger on this topic.  The portion of the wiki page that
said it hasn't been tested much since linux-4.0 was pulled, but the
official status was not clarified.  I specifically asked if SUSE
support btrfs-convert for its paying customers, and a few other
question...no reply.

Currently btrfs-convert will mysteriously fail if ever it cannot
allocate a large enough empty extent of contiguous free space.  IIRC
upstream patches were submitted to output better error messages if
this occurs.

Cheers,
Nicholas


signature.asc
Description: PGP signature


Bug#908835: dom4j: FTBFS because of javadoc error

2018-09-14 Thread Markus Koschany
Source: dom4j
Version: 2.1.1-1
Severity: serious

I just stumbled upon this bug. Apparently the last upload was never
built on our buildd. There is some kind of javadoc error:

javadoc: error - Error fetching URL: file:/usr/share/doc/default-jdk/api/

I may look into this later but filing a bug report now, so that it won't
get lost.

Markus



Bug#897072: RFS: btrfs-progs/4.17-1~bpo9+1

2018-09-14 Thread Nicholas D Steeves
On Fri, Sep 14, 2018 at 07:09:35PM +0100, Chris Lamb  wrote:
> Chris Lamb wrote:
> 
> > > https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.17-1~bpo9+1.dsc
> > 
> > Thanks; uploaded.
> 
> Ah drat, I did not pass "-v4.13.3-1~bpo9+1" and this hit backports-NEW
> (ie. possible REJECT coming our way).

Thank you for sponsoring!  Ah, yes, after that happened to me a couple
of times I wrote the attached convenience script ;-)  Unfortunately the
script requires a manual 'apt policy package' from a system with
stretch-backports enabled, manually copy & pasting the last version.

Cheers,
Nicholas


backport-to-stretch.gz
Description: application/gzip


signature.asc
Description: PGP signature


Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

2018-09-14 Thread Erik Andresen
Or maybe can we have the alternative dependency

pulseaudio | apulse.

A script could check if pulseaudio is available and if not start firefox with 
apulse. 

Unfortunately apulse is only available with buster and later.



Bug#908654: thunderbird: Drop dependency on libgtk2

2018-09-14 Thread Carsten Schoenert
Hi,

Am 12.09.18 um 11:09 schrieb Paride Legovini:
> As far as I can tell, Thunderbird 60 does not hard depend on gtk2 anymore.
> It would be nice to drop the dependency on the libgtk2 Debian package, in
> the framework of a general effort towards finally leaving gtk2 behind.

the build is still depending on libgtk+2-dev. Thus I believe some
dependency is pulled in automatically as the binaries are linked against
this library and dh_shlibdeps is detecting this correctly and finally
the libgtk+2 library is added to the thunderbird package as a required
dependency.

This is more a upstream issue I think. Open a bug report within the
Mozilla bugtracker please so we can add the link to this report here.

I have no time to dig into the autotools related file to try out if this
library could be removed from the Thunderbird build.

-- 
Regards
Carsten Schoenert



Bug#897072: RFS: btrfs-progs/4.17-1~bpo9+1

2018-09-14 Thread Chris Lamb
Chris Lamb wrote:

> > https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.17-1~bpo9+1.dsc
> 
> Thanks; uploaded.

Ah drat, I did not pass "-v4.13.3-1~bpo9+1" and this hit backports-NEW
(ie. possible REJECT coming our way).


Best wishes,

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



Bug#908833: colmap: FTBFS (dh_auto_configure fails)

2018-09-14 Thread Santiago Vila
Package: src:colmap
Version: 3.4-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -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" ..
-- 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
-- Detecting C compile features
-- Detecting C compile features - done

[... snipped ...]

  ^
In file included from /usr/lib/gcc/x86_64-linux-gnu/8/include/immintrin.h:41,
 from 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:2:
/usr/lib/gcc/x86_64-linux-gnu/8/include/avxintrin.h:365:1: error: inlining 
failed in call to always_inline '__m256 _mm256_sub_ps(__m256, __m256)': target 
specific option mismatch
 _mm256_sub_ps (__m256 __A, __m256 __B)
 ^
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:7:35: note: 
called from here
   __m256 c = _mm256_sub_ps(a, b);
  ~^~
In file included from /usr/lib/gcc/x86_64-linux-gnu/8/include/immintrin.h:41,
 from 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:2:
/usr/lib/gcc/x86_64-linux-gnu/8/include/avxintrin.h:1248:1: error: inlining 
failed in call to always_inline '__m256 _mm256_set_ps(float, float, float, 
float, float, float, float, float)': target specific option mismatch
 _mm256_set_ps (float __A, float __B, float __C, float __D,
 ^
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:6:35: note: 
called from here
   __m256 b = _mm256_set_ps(1.0, 3.0, 5.0, 7.0, 9.0, 11.0, 13.0, 15.0);
  ~^~~
In file included from /usr/lib/gcc/x86_64-linux-gnu/8/include/immintrin.h:41,
 from 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:2:
/usr/lib/gcc/x86_64-linux-gnu/8/include/avxintrin.h:1248:1: error: inlining 
failed in call to always_inline '__m256 _mm256_set_ps(float, float, float, 
float, float, float, float, float)': target specific option mismatch
 _mm256_set_ps (float __A, float __B, float __C, float __D,
 ^
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:5:35: note: 
called from here
   __m256 a = _mm256_set_ps(2.0, 4.0, 6.0, 8.0, 10.0, 12.0, 14.0, 16.0);
  ~^~~~
make[2]: *** [CMakeFiles/cmTC_d200f.dir/build.make:66: 
CMakeFiles/cmTC_d200f.dir/src.cxx.o] Error 1
make[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[1]: *** [Makefile:121: cmTC_d200f/fast] Error 2
make[1]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

Return value: 1
Source file was:

#include 
#include 
int main() {
  __m256 a = _mm256_set_ps(2.0, 4.0, 6.0, 8.0, 10.0, 12.0, 14.0, 16.0);
  __m256 b = _mm256_set_ps(1.0, 3.0, 5.0, 7.0, 9.0, 11.0, 13.0, 15.0);
  __m256 c = _mm256_sub_ps(a, b);
  float* f = (float*)
  return 0;
}
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -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" .. returned exit code 1
make: *** [debian/rules:28: 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"
but it also fails here:

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

where you can get a full build log if you need it.

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#908834: please build zstd udeb so that btrfs-progs can use zstd in Debian Installer

2018-09-14 Thread Nicholas D Steeves
Package: zstd
Version: 1.3.5+dfsg-1
Severity: wishlist

Dear Debian Med Packaging Team,

Would you please build a zstd udeb so that btrfs-progs can use zstd in
Debian Installer and Rescue System?  It uses zstd for transparent
filesystem compression.

eg: `chattr +c`, or `btrfs filesystem defrag -c`, or via a mount
option `compress=zstd`.  I believe the first and last of these use the
kernel's libzstd, and that the udeb is primarily required for
`btrfs-repair` to handle zstd extents in the Rescue System.  Also, please 
continue to CC Dmitri Ledkov, Debian's btrfs-progs maintainer.

Cheers,
Nicholas



Bug#908596: Acknowledgement ([quiterss] error while setting the maximum protocol version (99))

2018-09-14 Thread Leo
Hello
I can confirm that updating the package "libqt5network5" from version
5.11.1 + dfsg-7 to 5.11.1 + dfsg-8 has resolved the error.

Thanks for the quick fix
-
Hallo
Ich kann bestätigen, dass mit der Aktualisierung des Pakets
"libqt5network5" von Version 5.11.1+dfsg-7 auf 5.11.1+dfsg-8 der Fehler
behoben wurde.

Danke für die schnelle Lösung



Bug#897072: RFS: btrfs-progs/4.17-1~bpo9+1

2018-09-14 Thread Chris Lamb
Hi Nicholas,

> https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.17-1~bpo9+1.dsc

Thanks; uploaded.

> Gianfranco, who usually sponsors these uploads hasn't replied to this
> RFS since it was opened in April (I hope he's ok!)

Me too. He's about (eg. https://bugs.debian.org/908741) but probably
just busy..


Best wishes,

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



Bug#860417: gnome-menus: blacklist doesn't work with GNOME on Wayland

2018-09-14 Thread Jeremy Bicha
On Sun, Apr 16, 2017 at 10:09 AM Jeremy Bicha  wrote:
> The gnome-menus blacklist doesn't work with the GNOME on Wayland session.
>
> A test case for stretch is to look for the ImageMagick launcher in the
> Activities Overview. (See bug 675617 with my proposed solution for
> that.)

I looked at this a bit more but I don't know what I'm missing.

On Ubuntu for the default Ubuntu session, we override some .desktop's
using /usr/share/ubuntu/applications/. For Ubuntu on Wayland, we have
to include those .desktop files in
/usr/share/ubuntu-wayland/applications/ .

In 17.10, I believe we used /ubuntu/ and /ubuntu-xorg/ for the 2 sessions.

The Debian blacklist uses /usr/share/gnome/applications/ which feels
like it should be correct but it wasn't working for me in VirtualBox.
It did work for the GNOME on Xorg session. I tried locally adding
.desktop's to /gnome-wayland/ and /gnome-xorg/ but they didn't seem to
make a difference.

Thanks,
Jeremy Bicha



Bug#897072: RFS: btrfs-progs/4.17-1~bpo9+1

2018-09-14 Thread Nicholas D Steeves
Hi Chris,

I've been providing a stable-backport of btrfs-progs since early 2016.
Gianfranco, who usually sponsors these uploads hasn't replied to this
RFS since it was opened in April (I hope he's ok!)

tldl, here is the dsc for stretch-backports:

  
https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.17-1~bpo9+1.dsc

Thanks!
Nicholas

On Sat, Sep 01, 2018 at 03:26:20PM -0400, Nicholas D Steeves wrote:
> 
> I noticed that this RFS bug has been open since 4.15.1-2~bpo9+1
> (April).  Are there any problems with the package I haven't addressed?
> Upstream has recently started grumbling again about ancient Debian
> packages ;-)
> 
> Future changes: Dmitri doesn't want to allow no-change backports
> anymore (See #900314), so after this upload I will merge the changelog
> entries for unstable in between the ones for stretch-backports.
> 
> See below for updated links:
> 
> On Fri, Apr 27, 2018 at 09:16:05PM -0400, Nicholas D Steeves wrote:
> > Package: sponsorship-requests
> > Severity: normal
> > 
> > Dear mentors,
> > 
> > I am looking for a sponsor for my continued support of backported
> > "btrfs-progs".  There was an RC bug against btrfs-progs for some time,
> > which is why it didn't migrate to testing, and why I was unable to
> > provide an updated backport.
> > 
> > Hi Gianfranco!
> > 
> > I've CCed you as usual, because you usually take care of sponsoring
> > this package.  Thank you very much for your continued support :-)
> > 
> > Package name: btrfs-progs
> > Version : 4.15.1-2~bpo9+1
> > Upstream Author : linux-bt...@vger.kernel.org
> > URL : http://btrfs.wiki.kernel.org/
> > License : GPL-2
> > Section : admin
> > 
> > It builds these binary packages:
> > 
> >   btrfs-progs - Checksumming Copy on Write Filesystem utilities
> >   btrfs-progs-udeb - Checksumming Copy on Write Filesystem utilities (udeb) 
> > (udeb)
> >   btrfs-tools - transitional dummy package
> > 
> > To access further information about this package, please visit the 
> > following URL:
> > 
> >   https://mentors.debian.net/package/btrfs-progs
> > 
> > Alternatively, one can download the package with dget using this command:
> > 
> > dget -x 
> > https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.15.1-2~bpo9+1.dsc
> > 
> 
> dget -x 
> https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.17-1~bpo9+1.dsc
> 
> > More information about btrfs-progs can be obtained from 
> > http://btrfs.wiki.kernel.org/
> > 
> > Changes since the last upload:
> 
> btrfs-progs (4.17-1~bpo9+1) stretch-backports; urgency=medium
> 
>   * Rebuild for stretch-backports.
>   * Relax debhelper Build-Depends to 11~ to allow backporting.
>   * Restore btrfs-tools transitional package.  This is needed for the
> following packages on stretch: xen-tools, schroot, lxc,
> linaro-image-tools, kvpm, fsarchiver, and libguestfs0.
>   * Add Breaks snapper (<< 0.5.4-4~).  Needed because upstream
> btrfs-progs-4.16.1 changed some library names and locations.
> See Bug #900314 for more information.
>   * Remove debian/source/options, because this source option forces
> regeneration of a new orig.tarball, when the existing one in the
> archive must be used for backports.
> 
>  -- Nicholas D Steeves   Sat, 01 Sep 2018 14:59:26 -0400
> 
> btrfs-progs (4.17-1) unstable; urgency=medium
> 
>   * New upstream release.
> 
>  -- Dimitri John Ledkov   Mon, 23 Jul 2018 14:31:22 +0100
> 
> btrfs-progs (4.16.1-2) unstable; urgency=medium
> 
>   * Do not copy_exec btrfs-zero-log into initramfs, superseeded by `btrfs
> rescue zero-log` sub-command. Closes: #898720, #898719.
> 
>  -- Dimitri John Ledkov   Tue, 15 May 2018 14:15:27 +0100
> 
> btrfs-progs (4.16.1-1) unstable; urgency=medium
> 
>   * New upstream release.
>   * Drop transitional btrfs-tools package.
>   * Drop cross.patch, similar change done upstream.
>   * Package libbtrfs, libbtrfsutil, and python bindings.
> 
>  -- Dimitri John Ledkov   Tue, 08 May 2018 14:17:03 -0700
> 
> btrfs-progs (4.15.1-2) unstable; urgency=medium
> 
>   * If libzstd is provided in both deb & udeb variants (such as Ubuntu
> bionic) enable zstd support. If libzstd is not provided with both deb
> & udeb variants (such as current Debian unstable) disable zstd
> support. If and when libzstd is provided in both deb & udeb variants,
> a binNMU of this package is sufficient to enable zstd support. Closes:
> #886968
>   * Drop obsolete lintian overrides.
>   * Add alternative email address as uploader.
> 
>  -- Dimitri John Ledkov   Sat, 21 Apr 2018 11:59:50 +0100
> 
> btrfs-progs (4.15.1-1) unstable; urgency=medium
> 
>   * New upstream release
> 
>  -- Dimitri John Ledkov   Mon, 19 Feb 2018 15:50:12 +
> 
> btrfs-progs (4.14.1-1) unstable; urgency=medium
> 
>   * New upstream release.
>   * Add libzstd-dev build dependency.
> 
>  -- Dimitri John Ledkov   Thu, 11 Jan 2018 15:43:20 +
> 
> 
> Cheers,

Bug#903579: FWIW I have filed the bug on Debian's behalf

2018-09-14 Thread shirish शिरीष
Dear all,

While I know barely anything about python, I did however file the bug
as shared by Bas and maintained by Sandro Tosi as
https://bugs.python.org/issue34684?@template=item&@pagesize=50&@startwith=0

@Sandro Tosi maybe you could enlighten upstream more about the issue
and see if a fix is possible.

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



Bug#908832: Please include application/wasm MIME type for WebAssembly files

2018-09-14 Thread Josh Triplett
Package: mime-support
Version: 3.61
Severity: normal
File: /etc/mime.types

Browsers require WebAssembly files to get served with the proper MIME
type, application/wasm. To help web servers such as the one in Python,
which read /etc/mime.types, could you please include an entry for
`application/wasm wasm` in /etc/mime.types?

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

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

mime-support depends on no packages.

Versions of packages mime-support recommends:
ii  bzip2 1.0.6-9
ii  file  1:5.34-2
ii  xz-utils  5.2.2-1.3

mime-support suggests no packages.

-- no debconf information



Bug#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure

2018-09-14 Thread gregor herrmann
On Fri, 14 Sep 2018 17:29:59 +0200, Xavier wrote:

> I'll take a look to recent SSL problems (and Net::SMTP dependencies) to
> try to understand.

My first idea was that the problems with IO::Socket::SSL and OpenSSL
1.1.1 might be the cause for this failure; but as it doesn't happen
in my sid chroot I'm out of ideas ...
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Leonard Cohen: I'm Your Man


signature.asc
Description: Digital Signature


Bug#908830: release-notes: Mention the python-magic upstream switch

2018-09-14 Thread Christoph Biedl
Package: release-notes
Severity: normal

Hi there,

'bout time to start contributing to the buster release notes. In my
opinion the python-magic transition[1] is worth to be mentioned. If you
disagree feel free to drop my input as well.

Suggested wording:

==

The python-magic/python3-magic Python bindings for the libmagic file
type detection library switched upstream and provide a broader set of
functions now. A compatibility layer is included so applications relying
on the old function set should not be harmed.

==

Aside, in the eight months since the switch I haven't seen even a single
report about a regression, so consider "should not be harmed" somewhat
an understatment.

Regards,

Christoph

[1] https://bugs.debian.org/877849
https://lists.debian.org/debian-devel/2018/01/msg00449.html

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

Kernel: Linux 4.18.6 (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: unable to detect



signature.asc
Description: PGP signature


Bug#908818: [Pkg-zsh-devel] Bug#908818: Bug#908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-14 Thread TS
Hello,

Daniel Shahaf schrieb/wrote:

--  --
> If you'd like to build it yourself, then first of all thank you for the
> willingness.  The procedure is documented on
> http://ircbots.debian.net/factoids/factoid.php?key=package+recompile ;
> between step 4 and step 5 you should apply the patch, such as by running
> 'patch -p1 < /path/to/patch' and edit the first line of debian/changelog
> to read, say, 5.6.1-1+~foo1 instead of 5.6.1-1.  The plus-tilde
> construct ensures that after you install the package you'll still
> upgrade automatically to any future version.
> 
> The patch is 43446:
> https://github.com/zsh-users/zsh/commit/7c5241edf37fbafc9e1f833aede76c524ce62bcb.patch
> (and http://www.zsh.org/mla/zsh-workers/43446)

For the record build does not finish for me:

Running test: with message two tabs will start menu completion
Test successful.
Running test: with message and _oldlist, two tabs will start menu completion
Test successful.
Running test: partial completion of option with an argument
Test successful.
Running test: with -W options mixed with arguments
Test successful.
../../Test/Y03arguments.ztst: all tests successful.
**
49 successful test scripts, 1 failure, 1 skipped
**
make[3]: *** [Makefile:188: check] Error 1
make[3]: Leaving directory '/home/luke/temp/zsh-build/zsh-5.6.1/obj/Test'
make[2]: *** [Makefile:263: test] Error 2
make[2]: Leaving directory '/home/luke/temp/zsh-build/zsh-5.6.1/obj'
dh_auto_test: cd obj && make -j2 test VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:63: override_dh_auto_test-arch] Error 2
make[1]: Leaving directory '/home/luke/temp/zsh-build/zsh-5.6.1'
make: *** [debian/rules:51: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



Bug#908831: linux-image-4.18.0-1-amd64: After upgrade from kernel 4.17 to 4.18 virt-manager dosent work

2018-09-14 Thread José Gramaxo
Package: src:linux
Version: 4.18.6-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
Upgrade kernel from 4.17 to 4.18
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Downgrade kernel to 4.17 or 4.16
   * What was the outcome of this action?
virt-manager works
   * What outcome did you expect instead?

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


-- Package-specific info:
** Version:
Linux version 4.18.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-29)) #1 SMP Debian 4.18.6-1 (2018-09-06)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.18.0-1-amd64 
root=UUID=5a496e0b-c8dd-48cf-8351-8387b4ee49aa ro quiet splash

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

** Kernel log:
[7.094117] NET: Registered protocol family 31
[7.094119] Bluetooth: HCI device and connection manager initialized
[7.094128] Bluetooth: HCI socket layer initialized
[7.094133] Bluetooth: L2CAP socket layer initialized
[7.094147] Bluetooth: SCO socket layer initialized
[7.107353] Adding 3605500k swap on /dev/sda3.  Priority:-2 extents:1 
across:3605500k SSFS
[7.294419] audit: type=1400 audit(1536942036.132:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=491 comm="apparmor_parser"
[7.297648] audit: type=1400 audit(1536942036.136:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="syslogd" pid=492 
comm="apparmor_parser"
[7.298084] audit: type=1400 audit(1536942036.136:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/irssi" pid=493 
comm="apparmor_parser"
[7.299133] audit: type=1400 audit(1536942036.136:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/{sbin/traceroute,bin/traceroute.db}" pid=490 comm="apparmor_parser"
[7.303412] audit: type=1400 audit(1536942036.140:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=494 
comm="apparmor_parser"
[7.303422] audit: type=1400 audit(1536942036.140:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=494 
comm="apparmor_parser"
[7.303428] audit: type=1400 audit(1536942036.140:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=494 
comm="apparmor_parser"
[7.306308] audit: type=1400 audit(1536942036.144:9): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/smbldap-useradd" 
pid=496 comm="apparmor_parser"
[7.306319] audit: type=1400 audit(1536942036.144:10): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/sbin/smbldap-useradd///etc/init.d/nscd" pid=496 
comm="apparmor_parser"
[7.307094] audit: type=1400 audit(1536942036.144:11): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="ioq3ded" pid=497 
comm="apparmor_parser"
[7.332141] RTL871X: rtw_ndev_init(wlan0)
[7.332982] usbcore: registered new interface driver rtl8723bu
[7.332985] RTL871X: module init ret=0
[7.339141] usbcore: registered new interface driver btusb
[7.342145] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b 
lmp_ver=06 lmp_subver=8723
[7.342151] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_config.bin
[7.342764] bluetooth hci0: firmware: failed to load 
rtl_bt/rtl8723b_config.bin (-2)
[7.342772] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[7.342777] bluetooth hci0: Direct firmware load for 
rtl_bt/rtl8723b_config.bin failed with error -2
[7.342782] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_fw.bin
[7.343981] bluetooth hci0: firmware: direct-loading firmware 
rtl_bt/rtl8723b_fw.bin
[7.345336] Bluetooth: hci0: rom_version status=0 version=1
[7.345355] Bluetooth: hci0: cfg_sz 0, total size 22496
[7.345924] rtl8723bu 1-3:1.2 wlx0013eff300b0: renamed from wlan0
[7.707049] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[7.707053] Bluetooth: BNEP filters: protocol multicast
[7.707062] Bluetooth: BNEP socket layer initialized
[8.092530] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[8.093363] r8169 :03:00.0: firmware: direct-loading firmware 
rtl_nic/rtl8168g-2.fw
[8.166151] r8169 :03:00.0 enp3s0: link down
[8.166272] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[8.176750] IPv6: ADDRCONF(NETDEV_UP): wlx0013eff300b0: link is not ready
[8.898141] RTL871X: RTW_ADAPTIVITY_EN_
[8.898147] AUTO, chplan:0x20, Regulation:0,0
[8.898149] RTL871X: RTW_ADAPTIVITY_MODE_
[8.898150] NORMAL
[9.574918] IPv6: ADDRCONF(NETDEV_UP): wlx0013eff300b0: link is not ready
[9.676931] IPv6: ADDRCONF(NETDEV_UP): wlx0013eff300b0: link is not ready
[   10.729462] IPv6: ADDRCONF(NETDEV_UP): 

Bug#908784: nethack: license incompatibility results in non-distributable binaries

2018-09-14 Thread Vincent Cheng
Hi James,

On Thu, Sep 13, 2018 at 2:51 PM James Cowgill  wrote:
>
> Source: nethack
> Version: 3.4.3-14
> Severity: serious
> X-Debbugs-CC: vch...@debian.org
>
> Hi,
>
> While reviewing the copyright file for the NetHack 3.6.1 upload, I
> noticed that the debian directory (and its patches) are marked as under
> the GPL-2.0. Unfortunately NetHack's special NGPL license is not
> compatible with the GPL (both are copyleft with some conflicting terms),
> so I have come to the conclusion that Debian's version of NetHack is not
> distributable in binary form at all.
>
> Thankfully I think this can be resolved fairly smoothly. If I look at
> the package history, I see that before 3.4.3-14 everything was licensed
> under the NGPL (except for the lisp patches). In this version, the
> copyright file was changed to relicense(?!) the debian/ directory under
> the GPL. Vincent and I are the only people who have claimed copyright
> since that point, and I am fine with licensing my stuff under the NGPL,
> so Vincent is the only person who needs asking.
>
> Vincent, can all your changes to the nethack package be licensed under
> the NGPL instead of the GPL-2.0?

Yes, I'm fine with licensing my changes to nethack under the NGPL as well.

Regards,
Vincent



Bug#907493: Timeout in autopkgtest also in Ubuntu Cosmic with Ghostscript 9.24

2018-09-14 Thread Jonas Smedegaard
Quoting Till Kamppeter (2018-09-14 14:52:28)
> On Ubuntu the timeouts in the CUPS autopkgtest do not happen any more 
> with Ghostscript 9.25 which got released yesterday and is highly 
> recommended by upstream to fix the regressions in 9.24.

Thanks Till, quite helpful!

I am working on Ghostscript 9.25, expecting a release later today.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#908494: lightning: no icon to access calendar after upgrade to TB 60

2018-09-14 Thread Carsten Schoenert
Am 12.09.18 um 01:44 schrieb George B.:
>> The information from the first email is showing that debconf-show was
>> failing. That is unusual and must have a reason.
> 
> I know nothing about debconf-show. Looking on the internet suggests it
> is meant to be run with a package name as an argument. I have tried the
> above 3 packages as arguments and there was no output and return code
> was 0.

debconf-show is used/triggered by reportbug. Seeing this error message
says simply there was something going wrong, and this shouldn't happen
here. It might mean some access rights are not given. If this would be
true it's also possible that Lightning can't be do the job it should do.

>> Is Ctrl+Shift+C showing the Calendar?
> 
> No
> 
>> for me it makes not really sense to do a lot of Q about some really basic
>> things if you can't do some more self research on your side.
> 
> What is it that you want me to do?

Well it means I'm not a help desk person who has a answer for all
possible things, try to start some own initiative and do some research
on the web.

Some thing I've found after some minutes of using a search engine. What
about:

https://support.mozilla.org/de/kb/calendar-updates-issues-thunderbird

-- 
Regards
Carsten Schoenert



Bug#908520: Fwd: Re: Bug#908520: firefox: Needs newer sqlite than what's listed in dependencies

2018-09-14 Thread hetas





 Forwarded Message 
Subject: Re: Bug#908520: firefox: Needs newer sqlite than what's listed 
in dependencies

Date: Tue, 11 Sep 2018 19:38:28 +0300
From: hetas 
To: Mike Hommey 

On 11.09.2018 01:45, Mike Hommey wrote:

On Mon, Sep 10, 2018 at 09:36:42PM +0300, Juho Turunen wrote:

Package: firefox
Version: 62.0-1
Severity: normal

Dear Maintainer,

Firefox in unstable has dependency for sqlite3-0 (>=3.14.0). This version
doesn't seem to be new enough.

After upgrading Firefox from older version I got an  notification saying that
Firefox can't access bookmarks or address history due to places.sql being
locked. After deleting the file I got the same notice again even though Firefox
was able to re-create the file.

Updating sqllite3 to version 3.24.0-1 fixed the issue and the original
places.sqlite was working fine.


What version did you have before that?

Mike



I had 3.16.2-5+deb9u1 installed from stable (Stretch). I have mixed 
system with mostly stable packages, so installing Firefox from unstable 
did not pull the unstable sqlite-package automatically. So I installed 
3.24.0-1 from testing/unstable to fix the issue.


Juho



Bug#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure

2018-09-14 Thread Xavier
Hi all,

looking at CPAN reports [1], no bug found by CPAN testers even on Gregor
machine [2] ;-) (except on Windows, which is a known problem).

I'll take a look to recent SSL problems (and Net::SMTP dependencies) to
try to understand.

Cheers,
Xavier

[1] http://matrix.cpantesters.org/?dist=Net-Server-Mail+0.25
[2]
http://www.cpantesters.org/cpan/report/85f34480-b7e8-11e8-913e-4c12c844a040



Bug#908818: [Pkg-zsh-devel] Bug#908818: Bug#908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-14 Thread Daniel Shahaf
TS wrote on Fri, 14 Sep 2018 16:26 +0200:
> I am not familar with building from source. Need to dig through haystacks of
> documentation first. Not sure i will make it right even then.
> 
> So, do have pre-built .debs somewhere with this patch i can test?
> Otherwise will jump through the pre-said loops if needed.

Upstream just released 5.6.2, which contains this patch.  You could just
wait for it to be packaged in sid.

If you'd like to build it yourself, then first of all thank you for the
willingness.  The procedure is documented on
http://ircbots.debian.net/factoids/factoid.php?key=package+recompile ;
between step 4 and step 5 you should apply the patch, such as by running
'patch -p1 < /path/to/patch' and edit the first line of debian/changelog
to read, say, 5.6.1-1+~foo1 instead of 5.6.1-1.  The plus-tilde
construct ensures that after you install the package you'll still
upgrade automatically to any future version.

The patch is 43446:
https://github.com/zsh-users/zsh/commit/7c5241edf37fbafc9e1f833aede76c524ce62bcb.patch
(and http://www.zsh.org/mla/zsh-workers/43446)

Cheers,

Daniel



Bug#908829: RFP: golang-notabug-themusicgod1-panicparse -- Stylish crashes for the Go language

2018-09-14 Thread Jeff Cliff
Package: wnpp
Severity: wishlist

* Package name: golang-notabug-themusicgod1-panicparse
  Version : 4417700b5a
  Upstream Author : maruel 
* URL : https://notabug.org/themusicgod1/panicparse
* License : Apache-2.0
  Programming Lang: go
  Description : Stylish crashes for the Go language

Parses panic stack traces, densifies and deduplicates goroutines with similar 
stack traces.
Helps debugging crashes and deadlocks in heavily parallelized process.

Panicparse is used by termui ( #890567 ), and was on NSA/Microsoft Github at
https://github.com/maruel/panicparse before Github was taken over.



Bug#908828: tracker.debian.org appears to report that the source package is to be removed, even though it's just the binary

2018-09-14 Thread Daniel Kahn Gillmor
Package: tracker.debian.org
Control: affects -1 src:knot-resolver

https://tracker.debian.org/pkg/knot-resolver shows:


 RM: This package has been requested to be removed. normal

   This package has been requested to be removed. This means that, when
   this request gets processed by an ftp-master, this package will no
   longer be in unstable, and will automatically be removed from testing
   too afterwards. If for some reason you want keep this package in
   unstable, please discuss so in the bug. Please see bug number #908755
   for more information.


however, #908755 only requests removal of the *binary* package for
knot-resolver on one architecture (arm64).  The source package itself
is intended to remain in debian.  So tracker.debian.org looks
a bit scarier than it ought to, for people concerned about the health of
knot-resolver in debian.

not a big deal, but since the goal for tracker is easy access to good
information, i figure you'd want to know.

thanks for maintaining https://tracker.debian.org/ -- it's a very useful
resource for me, both as a package maintainer, and as a user of debian!

  --dkg



Bug#908827: mesa: Fails to build on Stretch, missing min build dep

2018-09-14 Thread Andrea Vettorello
Source: mesa
Version: 18.2.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

Mesa 18.2.0-1 fails to build on Stretch, I can't find the relevant bug report
on freedesktop.org but now it requires xcb-proto >= 1.13.

After compiling and installing xcb-proto and libxcb 1.13-1 from unstable, the
package was built succesfully.



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

Kernel: Linux 4.19.0-rc2-test1 (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)



Bug#908826: vagrant/stable is incompatible with virtualbox/stretch-backports (now 5.2)

2018-09-14 Thread Lucas Nussbaum
Package: vagrant
Version: 1.9.1+dfsg-1+deb9u1
Severity: normal

Hi,

vagrant 1.9.1+dfsg-1+deb9u1 is now incompatible with virtualbox from
stretch-backports (version 5.2.18-dfsg-1~bpo9+1). It worked fine with
virtualbox 5.1.30-dfsg-1~bpo9+1.

vagrant from stretch-backports works fine with virtualbox from
stretch-backports.

When starting vagrant, I get:
$ vagrant up
No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.

(while of course virtualbox is available, and works fine outside of
Vagrant)

Lucas


-- System Information:
Debian Release: 9.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (400, 'testing'), (300, 
'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages vagrant depends on:
ii  bsdtar 3.2.2-2
ii  curl   7.52.1-5+deb9u6
ii  openssh-client 1:7.4p1-10+deb9u3
ii  ruby   1:2.3.3
ii  ruby-bundler   1.16.1-2
ii  ruby-childprocess  0.5.9-1
ii  ruby-erubis2.7.0-3
ii  ruby-i18n  0.7.0-2
ii  ruby-listen3.0.3-3
ii  ruby-log4r 1.1.10-4
ii  ruby-net-scp   1.2.1-4
ii  ruby-net-sftp  1:2.1.2-3
ii  ruby-net-ssh   1:4.2.0-2
ii  ruby-nokogiri  1.6.8.1-1
ii  ruby-rb-inotify0.9.7-1
ii  ruby-rest-client   1.8.0-3

vagrant recommends no packages.

Versions of packages vagrant suggests:
ii  virtualbox  5.2.18-dfsg-1~bpo9+1

-- no debconf information



Bug#906461: florence: diff for NMU version 0.6.3-1.1

2018-09-14 Thread Jérémy Bobbio
Hi!

On 14/09/2018 15:51, Adrian Bunk wrote:
> I've prepared an NMU for florence (versioned as 0.6.3-1.1) and uploaded 
> it to DELAYED/14. Please feel free to tell me if I should cancel it.

Thanks!

Feel free to upload it right away or even take over the package.
I sadly still haven't found enough time and energy to adjust packages to
my current (non-)involvement in Debian.

--
Lunar



signature.asc
Description: OpenPGP digital signature


Bug#908136: src:h2o: FTBFS on amd64

2018-09-14 Thread Apollon Oikonomopoulos
On 15:53 Fri 14 Sep , Apollon Oikonomopoulos wrote:
> The tests in t/50reverse-proxy-proxy-protocol.t and 
> t/40session-ticket.t report no session reuse with OpenSSL 1.1.1 and 
> need further investigation.

t/40session-ticket.t is a false positive: in TLSv1.3 session information 
is sent after the handshake has finished, and the way s_client is 
invoked in the test means that it can exit before it receives the 
session data. Until this is fixed upstream, I patched the test to always 
use TLSv1.2.

t/50reverse-proxy-session-resumption.t needs further investigation, but 
it seems that H2O's client code doesn't support session resumption for 
TLSv1.3 upstreams (which is H2O itself in the test case). I'm tempted to 
just disable the test even if resumption is indeed broken for TLSv1.3 
upstreams.



Bug#908818: [Pkg-zsh-devel] Bug#908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-14 Thread TS
Hi Daniel,

Daniel Shahaf schrieb/wrote:

--  --

> It will be included in upstream 5.6.2 which is due to be released soon.
> It would be great if you could test the issue with this patch and
> report back.
> 
> Cheers,
> 
> Daniel

I am not familar with building from source. Need to dig through haystacks of
documentation first. Not sure i will make it right even then.

So, do have pre-built .debs somewhere with this patch i can test?
Otherwise will jump through the pre-said loops if needed.

kind regards,

 Thilo



Bug#730534: gawk: patsplit values and separators result arrays seem to be switched

2018-09-14 Thread Adrian Bunk
On Tue, Nov 26, 2013 at 11:40:01AM +0200, alex bodnaru wrote:
> Package: gawk
> Version: 1:4.0.1+dfsg-2.1
> Severity: normal
> 
> Dear Maintainer,

Dear Alex,

> thank you for maintaining this package.
> 
> wishing to make a filter in the bluefish editor, i turned to awk.
> i needed to perform a matchall equivalent, so split/patsplit were chosen.
> the gawk man says "patsplit(s, a [, r [, seps] ])" the sepatator matches 
> would be in the last param, as with split.
> in reality, for patsplit they were switched, as opposed to split, 
> where they matched the man.
> i don't know which of them: the man or the program is to be fixed.

first of all apologies for the late reply.

Perhaps I am missing something, but it seems to work for me:

$ echo 'foo,bar.baz' | awk '{n = patsplit($0,a,/[^,|.]*/,b); for(i=1;i<=n;i++) 
print a[i] " " b[i]}'
foo ,
bar .
baz 
$ 

> thanks again,
> alex

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#887490: Offering my help to be part of team

2018-09-14 Thread J. Fernando Lagrange
This part was missing in my last message: -_-'

> […]
> 1. Add repository GPG key:
>

wget -O - http://deb.probesys.com/key | apt-key add -

> […]



signature.asc
Description: OpenPGP digital signature


Bug#908773: Solution

2018-09-14 Thread Marco Righi
Hi,
perhaps the problem is that the main monitor has a lower resolution than
the secondary one.

Command# xrandr
Screen 0: minimum 8 x 8, current 3600 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
VGA-0 connected 1920x1080+1680+0 (normal left inverted right x axis y
axis) 531mm x 299mm
   1920x1080 60.00*+
   1680x1050 59.95
   1600x1200 60.00
   1440x900  59.89
   1280x1024 75.0260.02
   1280x960  60.00
   1152x864  75.00
   1024x768  75.0370.0760.00
   800x600   75.0072.1960.3256.25
   640x480   75.0072.8159.94
DVI-I-1 connected 1680x1050+0+0 (normal left inverted right x axis y
axis) 474mm x 296mm
   1680x1050 60.45*+  59.9559.88
   1600x1200 60.00
   1440x900  59.89
   1280x1024 75.9875.0260.0260.02
   1152x921  65.85
   1152x900  66.00
   1024x768  75.0370.0760.00
   800x600   75.0072.1960.3256.25
   640x480   75.0072.8159.94
HDMI-0 disconnected (normal left inverted right x axis y axis)

I patched the problem by adding the following lines

### MARCO INIZIO ###

GRUB_GFXMODE=640x480

# Hack to force higher framebuffer resolution
GRUB_GFXPAYLOAD_LINUX=640x480

### MARCO FINE ###

in

/etc/default/grub

(and runingn the update-grub command)

Thx
Marco Righi



Bug#908825: ITP: shadowsocks-qt5 -- Cross-platform shadowsocks GUI client

2018-09-14 Thread Boyuan Yang
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: shadowsocks-qt5
  Version : 3.0.1
  Upstream Author : Symeon Huang 
* URL : https://github.com/shadowsocks/shadowsocks-qt5
* License : LGPL-3+
  Description : Cross-platform shadowsocks GUI client

 Shadowsocks-Qt5 is a native and cross-platform shadowsocks client with GUI,
 tray icon support and many advanced features. It can communicate with servers
 using shadowsocks protocol to bypass firewalls and encrypt data transmission.

I intend to co-maintain this package inside Debian Bridges Team.

--
Regards,
Boyuan Yang

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


Bug#853310: android-platform-system-core: ftbfs with GCC-7

2018-09-14 Thread Raphael Hertzog
Hi,

On Thu, 13 Sep 2018, 殷啟聰 | Kai-Chung Yan wrote:
> > It would have helped if you had given me the URL of the repository.
> > Anyway, I'm willing to sponsor the update (even though I don't know much
> > about Android Tools) but I have a few comments:
> 
> Thank you for the sponsor, it will help us a lot!
>
> The repository is at
> .
> Sorry about that, I thought it was too trivial.

It's not hard but I did not know the name of the team on salsa and there
are many packages in the team and the Vcs-Git in the current source
package was obviously outdated. :)

Anyway, I sponsored this upload targetting experimental.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/


signature.asc
Description: PGP signature


Bug#890567: upstream url change

2018-09-14 Thread Jeffrey Cliff
https://notabug.org/themusicgod1/termui
is available, now that Microsoft took over github.


-- 
GENERATION 26: The first time you see this, copy it into your sig on any
forum and add 1 to the generation


Bug#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure

2018-09-14 Thread gregor herrmann
Control: tag -1 + unreproducible

On Fri, 14 Sep 2018 16:52:38 +0300, Adrian Bunk wrote:

> Source: libnet-server-mail-perl
> Version: 0.25-1
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/fetch.php?pkg=libnet-server-mail-perl=all=0.25-1=1536904015=0

Thanks for the bug report.
 
> ...
> Test Summary Report
> ---
> t/starttls.t (Wstat: 9 Tests: 3 Failed: 0)
>   Non-zero wait status: 9
>   Parse errors: No plan found in TAP output
> Files=4, Tests=33,  2 wallclock secs ( 0.05 usr  0.04 sys +  0.67 cusr  0.20 
> csys =  0.96 CPU)
> Result: FAIL
> Failed 1/4 test programs. 0/33 subtests failed.
> make[1]: *** [Makefile:861: test_dynamic] Error 255

Hm, the package builds for me.


The buildd failure is:

# Error: TLS handshake failed SSL connect attempt failed at t/starttls.t line 
116.
# kill 9, 17145 (server)
t/starttls.t .. 
ok 1 - Accepted client for Test01: STARTTLS support
ok 2 - Accepted client for Test02: STARTTLS invalid parameters
ok 3 - Accepted client for Test03: STARTTLS handshake
All 3 subtests passed 


Line 116 in the test is:

   112  my $rv =
   113IO::Socket::SSL->start_SSL( $s,
   114  SSL_verify_mode => IO::Socket::SSL::SSL_VERIFY_NONE, );
   115  
   116  ( defined $rv && ref $rv eq 'IO::Socket::SSL' )
   117or die "TLS handshake failed " . IO::Socket::SSL::errstr();



Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Frank Zappa: CHUCHA


signature.asc
Description: Digital Signature


Bug#887490: Offering my help to be part of team

2018-09-14 Thread J. Fernando Lagrange
Hello,

Thanks for these great pieces of software !

I believe that  creating a team is the way to go and I am glad to offer
my help to be part of it.

I have been told that one of the "Debian ways" to create a team is:
- to do so on https://signup.salsa.debian.org
- add packages to such team repository (must be done by a Debian Developer)
- create a team on https://tracker.debian.org/teams/ to follow packages
- il will create a team+...@tracker.debian.org that can be used as
Debian Maintainer

(I have just created @fernando-guest account there.)


What can I do to help, now ?



I have been able to create packages:
These packages ARE NOT READY FOR PRODUCTION USE.

I have only tested installation on a newly installed Stretch server.


You can find such packages and their sources on http:/deb.probesys.com


To install them on a Debian Stretch installation NOT ON PRODUCTION,
please use following instructions:

1. Add repository GPG key:

2. Add following lines in yours source.list or create a dedicated file:
deb http://deb.probesys.com/debian stretch main
deb-src http://deb.probesys.com/debian stretch main


After package installation, I had to edit RsyncBackupPCPath in BackupPC4
server Web interface to indicate "/usr/bin/rsync_bpc" instead of empty.


Best Regards,
Fernando



signature.asc
Description: OpenPGP digital signature


Bug#906472: horst: FTBFS in buster/sid (unable to open 'stdarg.h')

2018-09-14 Thread Adrian Bunk
Control: reassign -1 sparse 0.5.2-1
Control: affects -1 src:horst

On Sat, Aug 25, 2018 at 10:09:47PM +0200, Christoph Biedl wrote:
> Santiago Vila wrote...
> 
> > make -j1 check
> > make[1]: Entering directory '/<>'
> > sparse -g -O2 -fdebug-prefix-map=/<>=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -std=gnu99 -Wall 
> > -Wextra -g -I. -DDO_DEBUG -I/usr/include/libnl3 *.[ch]
> > /usr/include/err.h:25:11: error: unable to open 'stdarg.h'
> 
> To reproduce this it's important to remove gcc-7 from the build chroot
> (apt purge libgcc-7-dev ; apt --purge autoremove).
> 
> Problem is, sparse appearently uses hardcoded paths and looks for
> stdarg.h in (among other places)
> 
> | /usr/lib/gcc/x86_64-linux-gnu/7//include/stdarg.h
> |   ^
> 
> ... which fails.
> 
> Solution is to rebuild sparse, building horst was successful then.
> If this is true (please check!), the interesting question is why this
> wasn't a problem in earlier gcc version bumps.

Thanks for the analysis, reassigning to sparse.

> Christoph

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#886028: Bug

2018-09-14 Thread Jonas Schäfer
On Sat, 27 Jan 2018 15:41:01 +0100 Jonas Wielicki  wrote:
>[1]: https://www.dovecot.org/pipermail/dovecot/2018-January/110787.html

Upstream claims to have a fix for that issue in 
https://github.com/dovecot/core/commit/
90bd9600a0e38e55c02c6266c1270fdd4138c07d

Wasn't able to test it.

kind regards,
Jonas



Bug#908743: mmm-mode: package cl-lib conflicts with emacs cl-lib

2018-09-14 Thread Julian Gilbey
On Fri, Sep 14, 2018 at 09:21:01PM +1000, Alexander Zangerl wrote:
> On Thu, 13 Sep 2018 12:03:31 +0100, Julian Gilbey writes:
> >Real cl-lib shadowed by compatibility cl-lib?
> >(/usr/share/emacs/site-lisp/mmm-mode/cl-lib.el)
> 
> agh. to support xemacs mmm-mode needs to ship a cl-lib.el
> as xemacs doesn't have one of those.
> 
> looks like the mmm-mode postinstall (which already byte-compiles
> only the applicable files for the emacs platform in question) needs
> to be a bit more agressive
> and get rid of or neuter the cl-lib.el if used with a non-xemacs emacs.
> 
> i'll look into ths in the next few days.

Thanks!

   Julian



Bug#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure

2018-09-14 Thread Adrian Bunk
Source: libnet-server-mail-perl
Version: 0.25-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=libnet-server-mail-perl=all=0.25-1=1536904015=0

...
Test Summary Report
---
t/starttls.t (Wstat: 9 Tests: 3 Failed: 0)
  Non-zero wait status: 9
  Parse errors: No plan found in TAP output
Files=4, Tests=33,  2 wallclock secs ( 0.05 usr  0.04 sys +  0.67 cusr  0.20 
csys =  0.96 CPU)
Result: FAIL
Failed 1/4 test programs. 0/33 subtests failed.
make[1]: *** [Makefile:861: test_dynamic] Error 255



Bug#906461: florence: diff for NMU version 0.6.3-1.1

2018-09-14 Thread Adrian Bunk
Control: tags 906461 + pending

Dear maintainer,

I've prepared an NMU for florence (versioned as 0.6.3-1.1) and uploaded 
it to DELAYED/14. Please feel free to tell me if I should cancel it.

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

diff -Nru florence-0.6.3/debian/changelog florence-0.6.3/debian/changelog
--- florence-0.6.3/debian/changelog	2014-11-07 13:24:29.0 +0200
+++ florence-0.6.3/debian/changelog	2018-09-14 16:45:57.0 +0300
@@ -1,3 +1,10 @@
+florence (0.6.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix the Makefile dependencies. (Closes: #906461)
+
+ -- Adrian Bunk   Fri, 14 Sep 2018 16:45:57 +0300
+
 florence (0.6.3-1) unstable; urgency=medium
 
   * New upstream release. (Closes: #764455)
diff -Nru florence-0.6.3/debian/patches/makefile-dependencies.patch florence-0.6.3/debian/patches/makefile-dependencies.patch
--- florence-0.6.3/debian/patches/makefile-dependencies.patch	1970-01-01 02:00:00.0 +0200
+++ florence-0.6.3/debian/patches/makefile-dependencies.patch	2018-08-18 01:25:51.0 +0300
@@ -0,0 +1,15 @@
+Description: Fix the Makefile dependencies
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/906461
+
+--- florence-0.6.3.orig/src/Makefile.am
 florence-0.6.3/src/Makefile.am
+@@ -16,7 +16,7 @@ florence_CPPFLAGS = -I$(top_srcdir) -DIC
+-DDATADIR="\"$(datadir)/florence\"" $(DEPS_CFLAGS) $(GTK3_CFLAGS)\
+$(LIBGNOME_CFLAGS) $(LIBNOTIFY_CFLAGS) $(XTST_CFLAGS) $(AT_SPI2_CFLAGS) $(INCLUDES)
+ florence_LDADD = $(DEPS_LIBS) $(LIBM) $(X11_LIBS) $(LIBGNOME_LIBS) $(LIBNOTIFY_LIBS)\
+-   $(XTST_LIBS) $(AT_SPI2_LIBS) $(GTK3_LIBS) -lflorence-1.0
++   $(XTST_LIBS) $(AT_SPI2_LIBS) $(GTK3_LIBS) libflorence-1.0.la
+ 
+ libflorence_1_0_la_SOURCES = lib/florence.c
+ library_includedir=$(includedir)/florence-1.0
diff -Nru florence-0.6.3/debian/patches/series florence-0.6.3/debian/patches/series
--- florence-0.6.3/debian/patches/series	2014-11-07 13:24:23.0 +0200
+++ florence-0.6.3/debian/patches/series	2018-08-18 01:25:22.0 +0300
@@ -1,2 +1,3 @@
 0001-Add-nonet-option-to-xmllint-and-xsltproc-calls.patch
 0002-Add-missing-links-on-libflorence.patch
+makefile-dependencies.patch


Bug#908822: long descriptions are empty

2018-09-14 Thread s3v
Source: haskell-yi-mode-haskell
Version: 0.17.1-1
Severity: minor


Dear maintainer,
 Please fix long descriptions for libghc-yi-mode-haskell-{dev,prof,doc}
packages as the current ones are almost empty.

  [...]
  Vcs-Git: https://salsa.debian.org/haskell-team/DHG_packages.git
  X-Description: Yi editor haskell mode
 <- empty
  [...]

Regards



Bug#908823: long descriptions are empty

2018-09-14 Thread s3v
Source: haskell-yi-frontend-pango
Version: 0.17.1-2
Severity: minor


Dear maintainer,
 Please fix long descriptions for libghc-yi-frontend-pango-{dev,prof,doc}
packages as the current ones are almost empty.

  [...]
  Vcs-Git: https://salsa.debian.org/haskell-team/DHG_packages.git
  X-Description: Pango frontend for Yi editor
  <- empty
  [...]

Regards



Bug#908813: [PATCH] spec: user xdelta v3 for rpm builds, too

2018-09-14 Thread Antonio Terceiro
Control: tags -1 + pending

On Fri, Sep 14, 2018 at 12:39:08PM +0300, Markus Lehtonen wrote:
> Package: pristine-tar
> Version: 1.44
> Tags: patch
> 
> Nowadays, it's ubiquitous and pristine-tar supports it.

applied, thanks


signature.asc
Description: PGP signature


Bug#908821: firefox-esr: updated version and firefox crasehst at start

2018-09-14 Thread Kostas Sismanis
Package: firefox-esr
Version: 60.2.0esr-1~deb9u2
Severity: normal

-- Package-specific info:

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

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

Versions of packages firefox-esr depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u3
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.26-0+deb9u1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.40.5-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++66.3.0-18+deb9u1
ii  libvpx4   1.6.1-3+deb9u1
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages firefox-esr recommends:
ii  libavcodec57  7:3.2.12-1~deb9u1

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-3
ii  libgssapi-krb5-2   1.15-1+deb9u1
ii  libgtk2.0-02.24.31-2

-- no debconf information

processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 6
model   : 6
model name  : AMD Athlon(tm) XP 1700+
stepping: 2
cpu MHz : 1466.475
cache size  : 256 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow 3dnowprefetch vmmcall
bugs: fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2 
spec_store_bypass
bogomips: 2932.95
clflush size: 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 6
model   : 6
model name  : AMD Athlon(tm) XP 1700+
stepping: 2
cpu MHz : 1466.475
cache size  : 256 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow 3dnowprefetch vmmcall
bugs: fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2 
spec_store_bypass
bogomips: 2932.95
clflush size: 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts



Bug#904261: [pkg-go] Bug#904261: dh-golang: Don't install files listed in DH_GOLANG_EXCLUDES to dev pacakge

2018-09-14 Thread Martín Ferrari
On 12/09/18 15:59, Martín Ferrari wrote:

>> I'm not sure it warrants an upload right away, but it would be nice to
>> have it before debhelper is updated.
>>
>> Could anyone sponsor that ?
> 
> I would be happy to, but I have not been following dh-golang devel much
> to decide if we sHould upload now.. Any other opinion?

I have just uploaded it.


-- 
Martín Ferrari (Tincho)



Bug#908820: pcl FTBFS on some 32bit architectures: virtual memory exhausted

2018-09-14 Thread Adrian Bunk
Source: pcl
Version: 1.8.1+dfsg1-4
Severity: serious
Tags: ftbfs patch

https://buildd.debian.org/status/package.php?p=pcl=sid

...
[ 41%] Built target pcl_openni_fast_mesh
virtual memory exhausted: Cannot allocate memory
make[3]: *** 
[sample_consensus/CMakeFiles/pcl_sample_consensus.dir/build.make:118: 
sample_consensus/CMakeFiles/pcl_sample_consensus.dir/src/sac_model_cone.cpp.o] 
Error 1


Note that the regression is actually not in pcl,
but gcc using more money.

The following addresses this by reducing the amount
of debug information when building for 32bit architectures:

--- debian/rules.old2018-09-13 18:24:33.134097776 +
+++ debian/rules2018-09-13 18:25:23.897428251 +
@@ -11,9 +11,8 @@
 CFLAGS+=$(CPPFLAGS)
 CXXFLAGS+=$(CPPFLAGS)
 
-DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
-ifneq (,$(filter $(DEB_BUILD_ARCH),mips mipsel))
-   CXXFLAGS+=--param ggc-min-expand=20
+ifeq (32,$(DEB_HOST_ARCH_BITS))
+   CXXFLAGS+=-g1
 endif
 
 ifeq ($(shell dpkg-vendor --derives-from Ubuntu && echo yes),yes)



Bug#908811: prometheus-node-exporter: Adding /mnt and /media as ignored mount points

2018-09-14 Thread Martín Ferrari
Hi Santiago,

On 14/09/18 10:24, Santiago Vila wrote:

> I see that the ignored mount points are not in
> /etc/default/prometheus-node-exporter anymore by default.

No, I moved all that default configuration into the binary's defaults.

> I think this change makes adding/removing ignored mount points more difficult
> for the average user, and I'm not very happy with that.

it is not the simplest, but in the default file you have the
documentation on how to do it, along with the current default value:

#
--collector.filesystem.ignored-mount-points="^/(dev|proc|run|sys|var/lib/docker)($|/)"
#Regexp of mount points to ignore for filesystem
#collector.

> In either case: Would be possible to add /mnt and /media to the list
> of ignored mount points? (Wherever they are now). I still use those
> mount points occasionally and it would be better for them not to be
> monitored.

Yeah, I think that makes sense. I will add them.


-- 
Martín Ferrari (Tincho)



Bug#908136: src:h2o: FTBFS on amd64

2018-09-14 Thread Apollon Oikonomopoulos
Control: tags -1 confirmed upstream

Hi,

On 15:42 Thu 06 Sep , Chris Hofstaedtler wrote:
> Package: src:h2o
> Version: 2.2.5+dfsg1-6
> Severity: serious
> 
> Dear Maintainer,
> 
> when trying to build h2o from source on amd64, inside sbuild, it fails:
> 
> h2o server (pid:14780) is ready to serve requests
> fetch-ocsp-response (using OpenSSL 1.1.1-pre9 (beta) 21 Aug 2018)
> failed to extract ocsp URI from examples/h2o/server.crt
> [OCSP Stapling] disabled for certificate file:examples/h2o/server.crt
> 
> #   Failed test at t/50reverse-proxy-session-resumption.t line 118.
> #  got: '0'
> # expected: '1'
> killing /<>/obj-x86_64-linux-gnu/h2o... received SIGTERM, 
> gracefully shutting down
> killed (got 0)
> killing /<>/obj-x86_64-linux-gnu/h2o... received SIGTERM, 
> gracefully shutting down
> killed (got 0)
> # Looks like you failed 1 test of 5.
> 
> #   Failed test 'lifetime'
> #   at t/50reverse-proxy-session-resumption.t line 121.
> 
> And further failures.
> Please also see the attached build log.

Thanks for the report! It looks like the tests in t/50access-log.t and 
t/40ssl-cipher-suite.t are failing when h2o is built against OpenSSL 
1.1.1, because they don't expect OpenSSL to support TLSv1.3 and are 
confused by TLSv1.3-related output (mostly cipher names).

The tests in t/50reverse-proxy-proxy-protocol.t and t/40session-ticket.t 
report no session reuse with OpenSSL 1.1.1 and need further 
investigation.

That said, I intend to move away from PicoTLS and towards OpenSSL for 
TLSv1.3 support in H2O if it works hassle-free.

Cheers,
Apollon



Bug#907493: Timeout in autopkgtest also in Ubuntu Cosmic with Ghostscript 9.24

2018-09-14 Thread Till Kamppeter

An update:

On Ubuntu the timeouts in the CUPS autopkgtest do not happen any more 
with Ghostscript 9.25 which got released yesterday and is highly 
recommended by upstream to fix the regressions in 9.24.


   Till



Bug#908818: [Pkg-zsh-devel] Bug#908818: Zsh: [7] + 23074 suspended (tty output)

2018-09-14 Thread Daniel Shahaf
TS wrote on Fri, 14 Sep 2018 14:35 +0200:
> This leads me to the impression that this is a race condition.
> Further i have the impression, that this related to #908033.
> 
> If i can help you with any further tests / informations just let me know.

Upstream has committed another patch for #908033; that patch postdates
the 5.6.1-1 package:

[[[
## Branch: master  

43446: More entersubsh() / addproc() wiring.

Fix additional races by passing back use of list_pipe_job
from subshell.

By Peter Stephenson on 09/12/2018 08:22
[**View 
Changes**](https://sourceforge.net/p/zsh/code/ci/7c5241edf37fbafc9e1f833aede76c524ce62bcb/)
]]]

It will be included in upstream 5.6.2 which is due to be released soon.
It would be great if you could test the issue with this patch and
report back.

Cheers,

Daniel



  1   2   >