Bug#900459: dask: Debci regression

[Matthias Klose]

Control: severity -1 important
Control: tags -1 sid buster

ping? it's almost a month. and the distutils issues were sorted out within a few 
days.


On Thu, 31 May 2018 12:23:50 -0700 Diane Trout  wrote:

Hello,

Allow me to first say oops, sorry about that.

Unfortunately there's something going on with python3-distutils and
packages that depend on it (like sphinx) are not installable right now,
so I can't test my fixes.

Also when I was running the tests locally they'd sometimes throw an
exception on shutdown. (Though pytest reports that all of the tests
passed.)

Diane

On Thu, 2018-05-31 at 08:26 +0200, Graham Inggs wrote:
> Source: dask
> Version: 0.17.4-1
> User: debian...@lists.debian.org
> Usertags: regression
> 
> Hi Maintainer
> 
> Since the upload of 0.17.4-1, dask has been failing its own

> autopkgtest [1] with the following error:
> 
>  ERROR collecting dask/bytes/tests/test_http.py

> 
> ImportError while importing test module
> '/usr/lib/python3/dist-packages/dask/bytes/tests/test_http.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3/dist-packages/dask/bytes/tests/test_http.py:3: in
> 
> import requests
> E   ModuleNotFoundError: No module named 'requests'
> !!! Interrupted: 1 errors during collection
> 
> 
> Regards

> Graham
> 
> 
> [1] https://ci.debian.net/packages/d/dask/unstable/amd64/
> 

Bug#899238: RFP: ppx-tools-versioned -- Tools for authors of ppx rewriters

[Mehdi Dogguy]

Indeed :-)

Le 22 juin 2018 05:00:35 GMT+02:00, Andy Li  a écrit :
>On Fri, Jun 22, 2018 at 5:01 AM, Mehdi Dogguy  wrote:
>> Excellent work! I've reviewed it and it looks fine. I'll upload it
>shortly.
>> Would you mind retitling thing bug to an "ITP: ..." and setting
>yourself
>> as its owner?
>
>Thanks, Mehdi.
>I've already updated the title and the owner before working on it as
>seen in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899238
>It is just I'm replying the message in my email client, so the subject
>line is still using the old title :)
>
>Best,
>Andy

-- 
Mehdi

Bug#901963: [pkg-go] Bug#901963: git-lfs: "git lfs help" doesn't work

[Stephen Gelman]

I confirmed that this is a bug with the debian package (also exists in 
upstream’s debian package).  “git lfs help” should work and does with 
upstream’s binaries.  A bug happened to have been recently filed upstream at 
https://github.com/git-lfs/git-lfs/issues/3043 
.  I am investigating this.

Stephen

> On Jun 20, 2018, at 2:25 PM, Kenyon Ralph  wrote:
> 
> Package: git-lfs
> Version: 2.4.2-1~bpo9+1
> Severity: minor
> 
> Dear Maintainer,
> 
> git lfs help doesn't work. It just says 'Sorry, no usage text found
> for "git-lfs"', either when doing "git lfs help" or when doing "git
> lfs help ", such as "git lfs help track".
> 
> Probably the right thing to do would be show the manual pages (which
> are indeed installed and usable), just like "git help" does, e.g.,
> "git lfs help" runs "man git-lfs", "git lfs help track" runs "man
> git-lfs-track", etc.
> 
> -- System Information:
> Debian Release: 9.4
>  APT prefers stable-updates
>  APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.16.0-0.bpo.1-amd64 (SMP w/24 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
> LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
> LC_ALL set to en_US.UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages git-lfs depends on:
> ii  git1:2.17.1-1~bpo9+1
> ii  libc6  2.24-11+deb9u3
> 
> git-lfs recommends no packages.
> 
> git-lfs suggests no packages.
> 
> -- no debconf information
> 
> 

Bug#902097: fuse-zip FTCBFS: uses the build architecture pkg-config

[Helmut Grohne]

Source: fuse-zip
Version: 0.4.4-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

fuse-zip fails to cross build from source, because its Makefiles hard
code the build architecture pkg-config. After making it substitutable,
it mostly cross builds, but it insists on relinking fuse-zip during make
install and dh_auto_install does not pass any cross tools along
(expecting that you build during dh_auto_build). Thus we need to export
build tools ourselves (or fix the Makefile) to make it cross buildable.
Please consider applying the attached patch.

Helmut
--- fuse-zip-0.4.4/debian/changelog
+++ fuse-zip-0.4.4/debian/changelog
@@ -1,3 +1,12 @@
+fuse-zip (0.4.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ cross.patch: Make build tools substitutable.
++ Also substitute build tools for make install.
+
+ -- Helmut Grohne   Thu, 21 Jun 2018 21:34:10 +0200
+
 fuse-zip (0.4.4-1) unstable; urgency=low
 
   * New upstream release (Closes: #795675)
--- fuse-zip-0.4.4/debian/patches/cross.patch
+++ fuse-zip-0.4.4/debian/patches/cross.patch
@@ -0,0 +1,35 @@
+--- fuse-zip-0.4.4.orig/Makefile
 fuse-zip-0.4.4/Makefile
+@@ -7,12 +7,13 @@
+ mandir=$(datarootdir)/man
+ man1dir=$(mandir)/man1
+ manext=.1
+-LIBS=-Llib -lfusezip $(shell pkg-config fuse --libs) $(shell pkg-config 
libzip --libs)
++PKG_CONFIG?=pkg-config
++LIBS=-Llib -lfusezip $(shell $(PKG_CONFIG) fuse --libs) $(shell $(PKG_CONFIG) 
libzip --libs)
+ LIB=lib/libfusezip.a
+ CXXFLAGS=-g -O0 -Wall -Wextra
+ RELEASE_CXXFLAGS=-O2 -Wall -Wextra
+-FUSEFLAGS=$(shell pkg-config fuse --cflags)
+-ZIPFLAGS=$(shell pkg-config libzip --cflags)
++FUSEFLAGS=$(shell $(PKG_CONFIG) fuse --cflags)
++ZIPFLAGS=$(shell $(PKG_CONFIG) libzip --cflags)
+ SOURCES=main.cpp
+ OBJECTS=$(SOURCES:.cpp=.o)
+ MANSRC=fuse-zip.1
+--- fuse-zip-0.4.4.orig/lib/Makefile
 fuse-zip-0.4.4/lib/Makefile
+@@ -1,9 +1,10 @@
+ DEST=libfusezip.a
+-LIBS=$(shell pkg-config fuse --libs) $(shell pkg-config libzip --libs)
++PKG_CONFIG?=pkg-config
++LIBS=$(shell $(PKG_CONFIG) fuse --libs) $(shell $(PKG_CONFIG) libzip --libs)
+ CXXFLAGS=-g -O0 -Wall -Wextra
+ RELEASE_CXXFLAGS=-O2 -Wall -Wextra
+-FUSEFLAGS=$(shell pkg-config fuse --cflags)
+-ZIPFLAGS=$(shell pkg-config libzip --cflags)
++FUSEFLAGS=$(shell $(PKG_CONFIG) fuse --cflags)
++ZIPFLAGS=$(shell $(PKG_CONFIG) libzip --cflags)
+ SOURCES=$(sort $(wildcard *.cpp))
+ OBJECTS=$(SOURCES:.cpp=.o)
+ CLEANFILES=$(OBJECTS) $(DEST)
--- fuse-zip-0.4.4/debian/patches/series
+++ fuse-zip-0.4.4/debian/patches/series
@@ -1 +1,2 @@
 reproducible-build.patch
+cross.patch
--- fuse-zip-0.4.4/debian/rules
+++ fuse-zip-0.4.4/debian/rules
@@ -1,5 +1,9 @@
 #!/usr/bin/make -f
 
+# for relinking fuse-zip during make install
+DPKG_EXPORT_BUILDTOOLS=1
+-include /usr/share/dpkg/buildtools.mk
+
 LDFLAGS:=$(shell dpkg-buildflags --get LDFLAGS)
 CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS)
 CXXFLAGS += $(shell dpkg-buildflags --get CPPFLAGS)

Bug#891833: Please restore SELinux context on /var/lib/spamassassin

[Noah Meyerhans]

On Thu, Mar 01, 2018 at 12:49:48PM +0100, Laurent Bigonville wrote:
> On package installation, the /var/lib/spamassassin directory ends up
> wrongly labeled on disk.

Thanks for this report.

> There are two solutions here to fix this problem, either:
> 
> 1) ship the directory in the package itself and do not create it in the
> postinst script. This has also the advantage that dpkg -S will return
> the owner of the directory.

This seems best.

> 2) Call restorecon just after creating the directory (before creating
> anything else in it), something like:
> "which restorecon >/dev/null 2>&1 && restorecon /var/lib/spamassassin"
> should work.

I don't have much experience with SELinux. Are there any advantages to
using restorecon approach?

Thanks again.
noah



signature.asc
Description: PGP signature

Bug#902096: xastir: [Improvement/Patch included] Add support Multi-GNSS receivers (GNRMC/GNGGA sentences)

[Geoffroy GRAMAIZE]

Package: xastir
Version: 2.0.8-2
Severity: wishlist

Dear Maintainer,

Please find an attached patch to support multi-gnss receivers (added 
support for GNRMC/GNGGA NMEA sentences which have strictly the same 
format as GPRMC/GPGGA sentences).


I've built it on a debian strech, and it worked fine.

Kind regards.


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

Kernel: Linux 4.16.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xastir depends on:
ii  debconf [debconf-2.0]1.5.61
ii  libax25  0.0.12-rc4-1
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.24-11+deb9u3
ii  libcurl3-gnutls  7.52.1-5+deb9u6
ii  libdb5.3 5.3.28-12+deb9u1
ii  libfreetype6 2.6.3-3.2
ii  libgdal202.1.2+dfsg-5
ii  libgeotiff2  1.4.2-2+b1
ii  libgomp1 6.3.0-18+deb9u1
ii  libgraphicsmagick-q16-3  1.3.25-8
ii  libice6  2:1.0.9-2
ii  libjbig0 2.1-3.1+b2
ii  libjpeg62-turbo  1:1.5.1-2
ii  liblcms2-2   2.8-4
ii  liblzma5 5.2.2-1.2+b1
ii  libpcre3 2:8.39-3
ii  libpng16-16  1.6.28-1
ii  libproj124.9.3-1
ii  libshp2  1.4.0-1
ii  libsm6   2:1.2.2-1+b3
ii  libtiff5 4.0.8-2+deb9u2
ii  libwebp6 0.5.2-1
ii  libwmf0.2-7  0.2.8.4-10.6
ii  libx11-6 2:1.6.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxm4   2.3.4-13
ii  libxml2  2.9.4+dfsg1-2.2+deb9u2
ii  libxt6   1:1.1.5-1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages xastir recommends:
ii  festival  1:2.4~release-3+b1
ii  python2.7.13-2

Versions of packages xastir suggests:
ii  direwolf  1.3-2

-- debconf information:
* xastir/install-setuid: true
Index: xastir-2.0.8/src/db.c
===
--- xastir-2.0.8.orig/src/db.c
+++ xastir-2.0.8/src/db.c
@@ -17319,9 +17319,9 @@ void decode_info_field(char *call,
 fprintf(stderr,"decode_info_field: $ (raw gps or ultimeter 2000)\n");
 if (strncmp("ULTW",message,4) == 0 && is_xnum_or_dash(message+4,44))
 done = data_add(APRS_WX5,call,path,message+4,from,port,origin,third_party, station_is_mine, 0);
-else if (strncmp("GPGGA",message,5) == 0)
+else if (strncmp("GPGGA",message,5) == 0 || strncmp("GNGGA",message,5) == 0)
 done = data_add(GPS_GGA,call,path,message,from,port,origin,third_party, station_is_mine, 0);
-else if (strncmp("GPRMC",message,5) == 0)
+else if (strncmp("GPRMC",message,5) == 0 || strncmp("GNRMC",message,5) == 0)
 done = data_add(GPS_RMC,call,path,message,from,port,origin,third_party, station_is_mine, 0);
 else if (strncmp("GPGLL",message,5) == 0)
 done = data_add(GPS_GLL,call,path,message,from,port,origin,third_party, station_is_mine, 0);
Index: xastir-2.0.8/src/gps.c
===
--- xastir-2.0.8.orig/src/gps.c
+++ xastir-2.0.8/src/gps.c
@@ -139,7 +139,7 @@ int decode_gps_rmc( char *data,
 if ( (data == NULL) || (strlen(data) < 37) )
 return(0);  // Not enough data to parse position from.
 
-if (strncmp(data,"$GPRMC,",7) != 0)   // No GPRMC found
+if ( (strncmp(data,"$GPRMC,",7) != 0) && (strncmp(data,"$GNRMC,",7) != 0) )   // No GPRMC found
 return(0);
 
 if(strchr(data,',') == NULL)  // No comma found
@@ -393,7 +393,7 @@ int decode_gps_gga( char *data,
 if ( (data == NULL) || (strlen(data) < 35) )  // Not enough data to parse position from.
 return(0);
 
-if (strncmp(data,"$GPGGA,",7) != 0)
+if ( (strncmp(data,"$GPGGA,",7) != 0) && (strncmp(data,"$GNGGA,",7) != 0) )
 return(0);
 
 if (strchr(data,',') == NULL)
@@ -564,7 +564,7 @@ int gps_data_find(char *gps_line_data, i
  
 
 
-if (strncmp(gps_line_data,"$GPRMC,",7)==0) {
+if (strncmp(gps_line_data,"$GPRMC,",7)==0 || strncmp(gps_line_data,"$GNRMC,",7)==0) {
 
 if (debug_level & 128) {
 char filtered_data[MAX_LINE_SIZE+1];
@@ -652,7 +652,7 @@ DISABLE_SETUID_PRIVILEGE;
 }
 }
 
-if (strncmp(gps_line_data,"$GPGGA,",7)==0) {
+if (strncmp(gps_line_data,"$GPGGA,",7)==0 || strncmp(gps_line_data,"$GNGGA,",7)==0) {
 
 if (debug_level & 128) {
 char filtered_data[MAX_LINE_SIZE+1];
Index: xastir-2.0.8/src/interface.c

Bug#902094: ITP: node-koa-mount -- Mounting middleware for koa

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-koa-mount
  Version : 3.0.0
  Upstream Author : haoxin 
* URL : https://github.com/koajs/mount
* License : MIT
  Programming Lang: Node.js
  Description : Mounting middleware for koa

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902095: ITP: node-promised-ldap -- Promise wrapper over node-ldapjs

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-promised-ldap
  Version : 0.2.0
  Upstream Author : Stewart MacKenzie-Leigh
* URL : https://github.com/stewartml/promised-ldap
* License : MIT
  Programming Lang: Node.js
  Description : Promise wrapper over node-ldapjs

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#901653: mruby: CVE-2018-12248

[Nobuhiro Iwamatsu]

Source: mruby
Version: 1.4.1+20180622+git640fca32-1

Hi,

This bug was fixed in 1.4.1+20180622+git640fca32-1.

Best regards,
  Nobuhiro

2018-06-16 18:10 GMT+09:00 Salvatore Bonaccorso :
> Source: mruby
> Version: 1.4.1-2
> Severity: important
> Tags: patch security upstream
> Forwarded: https://github.com/mruby/mruby/issues/4038
>
> Hi,
>
> The following vulnerability was published for mruby.
>
> CVE-2018-12248[0]:
> | An issue was discovered in mruby 1.4.1. There is a heap-based buffer
> | over-read associated with OP_ENTER because
> | mrbgems/mruby-fiber/src/fiber.c does not extend the stack in cases of
> | many arguments to fiber.
>
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
>
> For further information see:
>
> [0] https://security-tracker.debian.org/tracker/CVE-2018-12248
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12248
> [1] https://github.com/mruby/mruby/issues/4038
> [2] 
> https://github.com/mruby/mruby/commit/778500563a9f7ceba996937dc886bd8cde29b42b
>
> Please adjust the affected versions in the BTS as needed.
>
> Regards,
> Salvatore



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#901652: mruby: CVE-2018-12249

[Nobuhiro Iwamatsu]

Source: mruby
Version: 1.4.1+20180622+git640fca32-1

Hi,

This bug was fixed in 1.4.1+20180622+git640fca32-1.

Best regards,
  Nobuhiro

2018-06-16 18:09 GMT+09:00 Salvatore Bonaccorso :
> Source: mruby
> Version: 1.4.1-2
> Severity: important
> Tags: security upstream
> Forwarded: https://github.com/mruby/mruby/issues/4037
>
> Hi,
>
> The following vulnerability was published for mruby.
>
> CVE-2018-12249[0]:
> | An issue was discovered in mruby 1.4.1. There is a NULL pointer
> | dereference in mrb_class_real because "class BasicObject" is not
> | properly supported in class.c.
>
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
>
> For further information see:
>
> [0] https://security-tracker.debian.org/tracker/CVE-2018-12249
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12249
> [1] https://github.com/mruby/mruby/issues/4037
> [2] 
> https://github.com/mruby/mruby/commit/faa4eaf6803bd11669bc324b4c34e7162286bfa3
>
> Please adjust the affected versions in the BTS as needed.
>
> Regards,
> Salvatore



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#902091: ITP: node-only -- Function to return whitelisted properties of an object

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-only
  Version : 0.0.2
  Upstream Author : TJ Holowaychuk 
* URL : https://github.com/tj/node-only
* License : MIT
  Programming Lang: Node.js
  Description : Function to return whitelisted properties of an object

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902090: ITP: node-ldapjs -- LDAP client and server APIs

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-ldapjs
  Version : 1.0.1
  Upstream Author : Mark Cavage 
* URL : https://github.com/mcavage/node-ldapjs
* License : MIT
  Programming Lang: Node.js
  Description : LDAP client and server APIs

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902093: ITP: node-safe-json-stringify -- Prevent defined property getters from throwing errors

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-safe-json-stringify
  Version : 1.2.0
  Upstream Author : Debitoor
* URL : https://github.com/debitoor/safe-json-stringify
* License : MIT
  Programming Lang: Node.js
  Description : Prevent defined property getters from throwing errors

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902088: ITP: node-ldap-filter -- API for handling LDAP-style filters

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-ldap-filter
  Version : 0.3.3
  Upstream Author : Patrick Mooney 
* URL : https://github.com/pfmooney/node-ldap-filter
* License : MIT
  Programming Lang: Node.js
  Description : API for handling LDAP-style filters

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902092: ITP: node-resolve-path -- Resolve a relative path against a root path with validation

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-resolve-path
  Version : 1.4.0
  Upstream Author : Jonathan Ong  (http://jongleberry.com)
* URL : https://github.com/pillarjs/resolve-path
* License : MIT
  Programming Lang: Node.js
  Description : Resolve a relative path against a root path with validation

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902089: ITP: node-vasync -- Utilities for observable asynchronous control flow

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-vasync
  Version : 2.2.0
  Upstream Author : Dave Pacheco 
* URL : https://github.com/joyent/node-vasync
* License : MIT
  Programming Lang: Node.js
  Description : Utilities for observable asynchronous control flow

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902087: RM: docker-containerd -- ROM; obsolete

[Dmitry Smirnov]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: pkg-go-maintain...@lists.alioth.debian.org
Control: affects -1 docker-containerd

Please remove "docker-containerd" from "unstable".

This package is a private component of Docker that was forked from 
"containerd" package. "docker-containerd" is a Docker's fork of "containerd" 
made exclusively for Docker's consumption.

Docker no longer depends on this package.

-- 
Regards,
 Dmitry Smirnov.

---

Democracy is a pathetic belief in the collective wisdom of individual
ignorance.
-- H. L. Mencken


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

Bug#902086: RM: swarmkit -- ROM; obsolete

[Dmitry Smirnov]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: pkg-go-maintain...@lists.alioth.debian.org
Control: affects -1 swarmkit

Please remove "swarmkit" from "unstable".

Swarmkit is a private Docker component spilled into its own name space.
It has little value of its own; it have circular dependency with Docker and 
Docker is the only user of swarmkit-dev.

-- 
Regards,
 Dmitry Smirnov.

---

Democracy is a pathetic belief in the collective wisdom of individual
ignorance.
-- H. L. Mencken


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

Bug#902085: ITP: node-mv -- UNIX mv(1) for Node.js

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-mv
  Version : 2.1.1
  Upstream Author : Andrew Kelley
* URL : https://github.com/andrewrk/node-mv
* License : MIT
  Programming Lang: Node.js
  Description : UNIX mv(1) for Node.js

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902084: ITP: node-precond -- Precondition checking utilities.

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-precond
  Version : 0.2.3
  Upstream Author : Mathieu Turcotte 
* URL : https://github.com/MathieuTurcotte/node-precond
* License : MIT
  Programming Lang: Node.js
  Description : Precondition checking utilities.

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902083: ITP: node-urijs -- Javascript URL mutation library

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-urijs
  Version : 1.19.1
  Upstream Author : Rodney Rehm 
* URL : https://github.com/medialize/URI.js
* License : MIT
  Programming Lang: Node.js
  Description : Javascript URL mutation library

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902082: ITP: node-pedding -- Just pedding for callback.

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-pedding
  Version : 1.1.0
  Upstream Author : fengmk2 
* URL : https://github.com/node-modules/pedding
* License : MIT
  Programming Lang: Node.js
  Description : Just pedding for callback.

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902079: ITP: node-koa-session -- Koa cookie session middleware with external store support

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-koa-session
  Version : 5.8.1
  Upstream Author : TJ Holowaychuk 
* URL : https://github.com/koajs/session
* License : MIT
  Programming Lang: Node.js
  Description : Koa cookie session middleware with external store support

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902078: ITP: node-koa-send -- Transfer static files

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-koa-send
  Version : 5.0.0
  Upstream Author : haoxin 
* URL : https://github.com/koajs/send
* License : MIT
  Programming Lang: Node.js
  Description : Transfer static files

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902068: ITP: node-co-body -- Request body parsing for co

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-co-body
  Version : 6.0.0
  Upstream Author : TJ Holowaychuk 
* URL : https://github.com/cojs/co-body
* License : MIT
  Programming Lang: Node.js
  Description : Request body parsing for co

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902072: ITP: node-inflation -- Easily unzip an HTTP stream

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-inflation
  Version : 2.0.0
  Upstream Author : Jonathan Ong  (http://jongleberry.com)
* URL : https://github.com/stream-utils/inflation
* License : MIT
  Programming Lang: Node.js
  Description : Easily unzip an HTTP stream

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902081: ITP: node-koa-router -- Router middleware for koa. Provides RESTful resource routing.

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-koa-router
  Version : 7.4.0
  Upstream Author : Alex Mingoia 
* URL : https://github.com/alexmingoia/koa-router
* License : MIT
  Programming Lang: Node.js
  Description : Router middleware for koa. Provides RESTful resource 
routing.

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902064: ITP: node-error-inject -- Inject an error listener into a stream

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-error-inject
  Version : 1.0.0
  Upstream Author : dead_horse 
* URL : https://github.com/stream-utils/error-inject
* License : MIT
  Programming Lang: Node.js
  Description : Inject an error listener into a stream

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902066: ITP: node-http-assert -- Assert with status codes

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-http-assert
  Version : 1.3.0
  Upstream Author : Douglas Christopher Wilson 
* URL : https://github.com/jshttp/http-assert
* License : MIT
  Programming Lang: Node.js
  Description : Assert with status codes

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902069: ITP: node-copy-to -- Copy an object's properties to another object

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-copy-to
  Version : 2.0.1
  Upstream Author : dead_horse 
* URL : https://github.com/node-modules/copy-to
* License : MIT
  Programming Lang: Node.js
  Description : Copy an object's properties to another object

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902063: ITP: node-backoff -- Fibonacci and exponential backoffs.

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-backoff
  Version : 2.5.0
  Upstream Author : Mathieu Turcotte 
* URL : https://github.com/MathieuTurcotte/node-backoff
* License : MIT
  Programming Lang: Node.js
  Description : Fibonacci and exponential backoffs.

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902077: ITP: node-koa-is-json -- Check if a body is JSON

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-koa-is-json
  Version : 1.0.0
  Upstream Author : Jonathan Ong 
* URL : https://github.com/koajs/is-json
* License : MIT
  Programming Lang: Node.js
  Description : Check if a body is JSON

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902065: ITP: node-crypt3 -- Binding of crypt(3) for Node.js

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-crypt3
  Version : 1.0.0
  Upstream Author : Sendnor 
* URL : https://github.com/sendanor/node-crypt3
* License : MIT
  Programming Lang: Node.js
  Description : Binding of crypt(3) for Node.js

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902075: ITP: node-koa-bodyparser -- Body parser for koa

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-koa-bodyparser
  Version : 4.2.1
  Upstream Author : dead_horse  (http://deadhorse.me)
* URL : https://github.com/koajs/bodyparser
* License : MIT
  Programming Lang: Node.js
  Description : Body parser for koa

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902080: ITP: node-koa-static -- Static file serving middleware for koa

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-koa-static
  Version : 5.0.0
  Upstream Author : haoxin 
* URL : https://github.com/koajs/static
* License : MIT
  Programming Lang: Node.js
  Description : Static file serving middleware for koa

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902073: ITP: node-koa-compose -- Middleware composition utility

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-koa-compose
  Version : 4.1.0
  Upstream Author : jongleberry 
* URL : https://github.com/koajs/compose
* License : MIT
  Programming Lang: Node.js
  Description : Middleware composition utility

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902074: ITP: node-is-type-of -- Complete type checking for Node.js

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-is-type-of
  Version : 1.2.0
  Upstream Author : dead_horse 
* URL : https://github.com/node-modules/is-type-of
* License : MIT
  Programming Lang: Node.js
  Description : Complete type checking for Node.js

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902071: ITP: node-is-class -- Check if function is an ES6 class.

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-is-class
  Version : 0.0.5
  Upstream Author : Miguel Mota  
(http://www.miguelmota.com/)
* URL : https://github.com/miguelmota/is-class
* License : MIT
  Programming Lang: Node.js
  Description : Check if function is an ES6 class.

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902076: ITP: node-koa-convert -- Convert koa legacy generator middleware to modern promise middleware.

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-koa-convert
  Version : 1.2.0
  Upstream Author : gyson 
* URL : https://github.com/koajs/convert
* License : MIT
  Programming Lang: Node.js
  Description : Convert koa legacy generator middleware to modern promise 
middleware.

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902070: ITP: node-exeunt -- exiting a node.js process *and flushing stdout and stderr*

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-exeunt
  Version : 1.1.1
  Upstream Author : Joyent (joyent.com)
* URL : https://github.com/joyent/node-exeunt
* License : MPL-2.0
  Programming Lang: Node.js
  Description : exiting a node.js process *and flushing stdout and stderr*

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#902067: ITP: node-is-generator-function -- Native generator function tester

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-is-generator-function
  Version : 1.0.7
  Upstream Author : Jordan Harband 
* URL : https://github.com/ljharb/is-generator-function
* License : MIT
  Programming Lang: Node.js
  Description : Native generator function tester

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#901624: libecore-input1: circular dependency hell

[Ross Vandegrift]

On Thu, Jun 21, 2018 at 07:23:22PM +0200, Andreas Metzler wrote:
> have you seen, Paul Wuse's comment in 900594?
> 
> | Seems like installing all engines by default would be a better fix.
> 
> Any thoughts on that?

Yes, I like that idea.  I tested it out this evening and it's a good
improvement.  efl 1.20.7-6 is ready for upload on salsa, when you have the
chance.

Thanks,
Ross

Bug#902062: ITP: node-bunyan -- JSON logging library for node.js services

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: node-bunyan
  Version : 2.0.2
  Upstream Author : Trent Mick  (http://trentm.com)
* URL : http://github.com/trentm/node-bunyan
* License : MIT
  Programming Lang: Node.js
  Description : JSON logging library for node.js services

First of all, apologies for this barrage of ITPs. I'm working on packaging the
dependencies of a project I'm working on, and Node dependency trees get big -
fast.

This package will be maintained in pkg-javascript-devel. I have already secured
a sponsor.

Bug#899238: RFP: ppx-tools-versioned -- Tools for authors of ppx rewriters

[Andy Li]

On Fri, Jun 22, 2018 at 5:01 AM, Mehdi Dogguy  wrote:
> Excellent work! I've reviewed it and it looks fine. I'll upload it shortly.
> Would you mind retitling thing bug to an "ITP: ..." and setting yourself
> as its owner?

Thanks, Mehdi.
I've already updated the title and the owner before working on it as
seen in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899238
It is just I'm replying the message in my email client, so the subject
line is still using the old title :)

Best,
Andy

Bug#902061: dracut: Can't boot from backup disk because of UUID

[Stefan Monnier]

Package: dracut
Version: 044+241-3
Severity: normal

Dear Maintainer,

The HDD on my little BananaPi homeserver is dying (keeps giving errors
causing SATA coection reset, etc...), so I took it out and plugged
in another HDD that contained a backup copy of the system (basically
and `rsync` of the boot and root partitions).  My U-boot script
specifies the root partition via "root=/dev/mapper/VG-root" so there's
no need for any UUID to find the root partition.  And since dracut
is not configured in "hostonly" mode, I did not expect any problem.

Yet, the boot failed telling me that it couldn't find
/dev/disk/by-uuid/blablabla.

It did put me into some emergency shell where I managed to mount the
LVM partition (which the initrd has successfully found and activated),
rerun dracut and finally get my system to boot successfully.
But given the use of LVM and an explicit "root=..." on the kernel
command line, I don't see any justification for the boot failure.

Indeed, given my setup (and arguably any non-hostonly initrd)
I don't see why any UUID would appear in the inird, yet:

# lsinitrd /boot/initrd.img-4.16.0-2-armmp| grep by-uuid
-rw-r--r--   1 root root  146 Jun 18 15:22 
lib/dracut/hooks/emergency/80-\\x2fdev\\x2fdisk\\x2fby-uuid\\x2f1d3f740e-7a96-434a-8dfb-4a17e3dc563b.sh
-rw-r--r--   1 root root   64 Jun 18 15:22 
lib/dracut/hooks/initqueue/finished/devexists-\\x2fdev\\x2fdisk\\x2fby-uuid\\x2f1d3f740e-7a96-434a-8dfb-4a17e3dc563b.sh
# 

How can I configure dracut to "stay away from UUID since I use
LVM names instead"?  Shouldn't this be the default anyway when
the root partition is on LVM?


Stefan


-- System Information:
Debian Release: 9.4
  APT prefers stable
  APT policy: (990, 'stable'), (50, 'testing')
Architecture: armhf (armv7l)

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

Versions of packages dracut depends on:
ii  dracut-core  044+241-3

dracut recommends no packages.

Versions of packages dracut suggests:
pn  dracut-network  

-- Configuration Files:
/etc/bash_completion.d/dracut changed:
__contains_word () {
local word=$1; shift
for w in $*; do [[ $w = $word ]] && return 0; done
return 1
}
_dracut() {
local field_vals= cur=${COMP_WORDS[COMP_CWORD]} 
prev=${COMP_WORDS[COMP_CWORD-1]}
local -A OPTS=(
[STANDALONE]='-f -v -q -l -H -h -M -N
  --ro-mnt --force --kernel-only --no-kernel 
--strip --nostrip
  --hardlink --nohardlink --noprefix --mdadmconf 
--nomdadmconf
  --lvmconf --nolvmconf --debug --profile --verbose 
--quiet
  --local --hostonly --no-hostonly --fstab --help 
--bzip2 --lzma
  --xz --no-compress --gzip --list-modules 
--show-modules --keep
  --printsize --regenerate-all --noimageifnotneeded 
--early-microcode
  --no-early-microcode --print-cmdline --prelink 
--noprelink --reproducible
  --uefi
  '
   [ARG]='-a -m -o -d -I -k -c -L --kver --add --force-add 
--add-drivers
  --omit-drivers --modules --omit --drivers 
--filesystems --install
  --fwdir --libdirs --fscks --add-fstab --mount 
--device --nofscks
  --kmoddir --conf --confdir --tmpdir --stdlog 
--compress --prefix
  --kernel-cmdline --sshkey --persistent-policy 
--install-optional
  --loginstall --uefi-stub --kernel-image
  '
)
if __contains_word "$prev" ${OPTS[ARG]}; then
case $prev in
--kmoddir|-k|--fwdir|--confdir|--tmpdir)
comps=$(compgen -d -- "$cur")
compopt -o filenames
;;

-c|--conf|--sshkey|--add-fstab|--add-device|-I|--install|--install-optional)
comps=$(compgen -f -- "$cur")
compopt -o filenames
;;
-a|-m|-o|--add|--modules|--omit)
comps=$(dracut --list-modules 2>/dev/null)
;;
--persistent-policy)
comps=$(cd /dev/disk/; echo *)
;;
--kver)
comps=$(cd /lib/modules; echo [0-9]*)
;;
*)
return 0
;;
esac

Bug#846278: Bug 846278

[Matthew Crews]

I want to confirm that this is still a problem in Stretch. I experience the 
same problem as message #25 using Nvidia drivers, only I have no way of 
actually switching TTYs to force a log out!

This is on a brand new install of 9.4.

Bug#902060: pcre2: please use versioned symbols

[Jonathan Nieder]

Package: libpcre2-8-0
Version: 10.31-1
Severity: wishlist
Tags: upstream

Using a symbol version script brings a few advantages to a library:

 1. simplifies library transitions, since multiple versions of the
library with different ABI can share a process image without
producing disaster. See [1] for a description with more detail.

 2. makes appropriate package dependencies for callers easier to
compute, since the symbol version indicates the minimal library
version that introduced each symbol

Advantage (1) is especially important for a popular library like
pcre2.

Filing this as a reminder to anyone interested (including me) to
pursue adding a version script to libpcre2.  See the example [1] for
comparison.  Some references with more details are linked to at [2].

Thoughts of all kinds welcome, as always.

Sincerely,
Jonathan

[1] https://www.mail-archive.com/xz-devel@tukaani.org/msg00015.html
[2] https://gcc.gnu.org/wiki/SymbolVersioning

Bug#902059: RM: docker-runc -- ROM; obsolete

[Dmitry Smirnov]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: pkg-go-maintain...@lists.alioth.debian.org
Control: affects -1 docker-runc

Please remove "docker-runc" from "unstable".

This package is a needless fork of "runc" for private Docker consumption.
When this package was mistakenly introduced, it hijacked "runc" and broke all 
its reverse dependencies.

docker-runc lost its case as runc no longer depends on Docker hence circular 
dependency is broken.

-- 
Regards,
 Dmitry Smirnov.

---

Democracy is a pathetic belief in the collective wisdom of individual
ignorance.
-- H. L. Mencken


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

Bug#902058: RM: golang-github-docker-libnetwork -- ROM; obsolete

[Dmitry Smirnov]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: pkg-go-maintain...@lists.alioth.debian.org
Control: affects -1 golang-github-docker-libnetwork

Please remove "golang-github-docker-libnetwork" from "unstable".

This is not a (reusable) library but a part of Docker code base spilled into 
its own name space. Docker (the only user of this library) stopped depending 
on it to break circular dependency.

-- 
Regards,
 Dmitry Smirnov.

---

Democracy is a pathetic belief in the collective wisdom of individual
ignorance.
-- H. L. Mencken


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

Bug#902032: aptly: please provide an aptly-api service

[Alexandre Viau]

Hello,

I would like to add that I am willing to provide a patch that implements
this.

However, I would only start working on it after aptly is moved to
dh-golang to avoid merging issues. See bug #902038 for that.

Cheers,

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



signature.asc
Description: OpenPGP digital signature

Bug#767018: munin-plugins-extra: iostat_ios plugin should support configuration

[Lars Kruse]

Package: munin-plugins-extra
Followup-For: Bug #767018

Hello,

munin support vd* device names since v2.0.25.
The wrong LVM major block device number is fixed upstream (to be released with
v2.0.38).

Cheers,
Lars

Bug#902057: aptly: please consider backporting 1.2.0 to stretch

[Alexandre Viau]

Package: aptly
Severity: wishlist

Hello,

I would like to use aptly 1.0.0 on stretch, please consider backporting it.

Cheers,

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



signature.asc
Description: OpenPGP digital signature

Bug#870173: wireshark: CVE-2017-9616: Over deep mp4 chunks may cause stack Exhausted

[Balint Reczey]

Control: fixed -1 2.4.6-1

On Sun, Jul 30, 2017 at 8:51 PM Salvatore Bonaccorso  wrote:
>
> Source: wireshark
> Version: 2.2.7-1
> Severity: important
> Tags: upstream security
> Forwarded: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13777
>
> Hi,
>
> the following vulnerability was published for wireshark.
>
> CVE-2017-9616[0]:
> | In Wireshark 2.2.7, overly deep mp4 chunks may cause stack exhaustion
> | (uncontrolled recursion) in the dissect_mp4_box function in
> | epan/dissectors/file-mp4.c.
>
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
>
> For further information see:
>
> [0] https://security-tracker.debian.org/tracker/CVE-2017-9616
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9616
> [1] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13777
>
> Please adjust the affected versions in the BTS as needed.
>
> Regards,
> Salvatore

Thanks, this is now fixed.

Cheers,
Balint

-- 
Balint Reczey
Ubuntu & Debian Developer

Bug#902056: libpam-ssh-agent-auth: doesn't work from script

[sergio]

Package: libpam-ssh-agent-auth
Version: 0.10.3-1
Severity: normal

Hi, Christian.

Really I'm not sure if this a bug, but hope you can help me.

This works:

% cat ssh.sh
#!/bin/sh
echo $SSH_AUTH_SOCK
ssh e

% ./ssh.sh 
# Here I entered passphrase in gpg pinentry
/home/sergio/.gnupg/S.gpg-agent.ssh
Linux e ...
Last login ...
[sergio@e:~]%

This does not:

% cat sudo.sh
#!/bin/sh
echo $SSH_AUTH_SOCK
sudo ls

% ./sudo.sh 
/home/sergio/.gnupg/S.gpg-agent.ssh
[sudo] password for sergio: 


But sudo ls works fine:

% sudo ls
ssh.sh*
sudo.sh*


-- 
sergio.

Bug#900533: bug not fixed in v68

[積丹尼 Dan Jacobson]

reopen 900533
found 900533 68.0.3440.7-1
thanks

Bug still there in 68.0.3440.7-1

$ chromium /var/tmp/Devo\ Big\ Mess-CvKP3_1PL5c.webm
[9096:9096:0622/085518.510602:ERROR:sandbox_linux.cc(378)] InitializeSandbox() 
called with multiple threads in process gpu-process.
Created new window in existing browser session.
[665:683:0622/085518.931996:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[665:665:0622/085518.933523:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN

$ chromium /var/tmp/Devo\ Big\ Mess-CvKP3_1PL5c.mp4
[9341:9341:0622/085603.306119:ERROR:sandbox_linux.cc(378)] InitializeSandbox() 
called with multiple threads in process gpu-process.
Created new window in existing browser session.
[690:702:0622/085603.712554:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[690:690:0622/085603.714148:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN

Click on any YouTube or any movie at all
[638:651:0622/085324.469549:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[638:638:0622/085324.470430:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED

Versions of packages chromium depends on:
ii  chromium-common  68.0.3440.7-1
ii  libasound2   1.1.6-1
ii  libatk-bridge2.0-0   2.26.2-1
ii  libatk1.0-0  2.28.1-1
ii  libavcodec57 7:3.4.2-2+b2
ii  libavformat577:3.4.2-2+b2
ii  libavutil55  7:3.4.2-2+b2
ii  libc62.27-3
ii  libcairo21.15.10-3
ii  libcups2 2.3~b5-1
ii  libdbus-1-3  1.13.4-3
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.5-3
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.1.0-8
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk-3-0   3.22.30-1
ii  libharfbuzz0b1.7.6-1+b1
ii  libicu60 60.2-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.19-3
ii  libnss3  2:3.37.1-1
ii  libopenjp2-7 2.3.0-1
ii  libopus0 1.3~beta+20180518-1
ii  libpango-1.0-0   1.42.1-1
ii  libpangocairo-1.0-0  1.42.1-1
ii  libpng16-16  1.6.34-1
ii  libpulse012.0-1
ii  libre2-4 20180301+dfsg-1
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.1.0-8
ii  libvpx5  1.7.0-3
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.5-1
ii  libx11-xcb1  2:1.6.5-1
ii  libxcb1  1.13-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-1
ii  libxdamage1  1:1.1.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.7+dfsg-1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2
ii  libxss1  1:1.2.2-1+b2
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-7
ii  libgl1-mesa-dri   18.1.2-1

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

-- no debconf information

Bug#772277: munin-async: bashism in /bin/sh script

[Lars Kruse]

Package: munin-async
Followup-For: Bug #772277


Hi,

checkbashism seems to be wrong here:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843913

See the source of "sleep":

  ~# type sleep
  sleep is hashed (/bin/sleep)


Let us wait, until the check in checkbashism is fixed.

Cheers,
Lars

Bug#902055: Recommend libglib2.0-dev in core and depend on in lxqt

[Alf Gaida]

Source: lxqt-metapackages
Severity: normal

We really want it - so i recommend that package in several places where it make 
sense

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

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

Bug#902054: Recommend libglib2.0-bin

[Alf Gaida]

Source: libqtxdg
Severity: normal

We don't depend on, but it would be nice to have.

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

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

Bug#902053: libfm-qt should depend on libglib2.0-bin

[Alf Gaida]

Source: libfm-qt
Severity: normal

LXQt need gio to work without backdraws - so libfm-qt should depend on 
libglib2.0-bin
We want gio - and only recommend the package is to weak imho.

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

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

Bug#902052: [zfs-linux] /usr/share/initramfs-tools/hooks/zdev should be shipped in zfs-initramfs

[Antonio Russo]

Package: zfs-linux
Version: 0.7.9-3
Severity: normal
Tags: patch

--- Please enter the report below this line. ---

As addressed in [1], /usr/share/initramfs-tools/hooks/zdev should be shipped in 
zfs-initramfs,
not zfsutils-linux.

[1] https://salsa.debian.org/zfsonlinux-team/zfs/merge_requests/9

Bug#902051: libxslt: generate-id() not returning unique IDs

[Andrew Ayer]

Package: libxslt
Version: 1.1.29-2.1
Severity: important
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

Nick Bowler has pointed out on the libxslt bug tracker that
debian/patches/0004-Make-generate-id-deterministic.patch has issues,
most notably that generate-id() is not returning distinct IDs for
distinct nodes:

https://bugzilla.gnome.org/show_bug.cgi?id=751621#c15

https://bugzilla.gnome.org/show_bug.cgi?id=751621#c19

This bug could cause stylesheets to break in hard-to-detect ways.  For
example, it could cause the stylesheet to believe that two nodes are
the same when they aren't (if the stylesheet is using the common 
`generate-id(foo) = generate-id(bar)` idiom), or to generate elements
with duplicate id attributes (if generate-id() is being used to generate
the id attribute).

It's not immediately clear how the patch can be fixed, since it relies
on an assumption that is no longer valid.  Thus, I think the patch
should be backed out until we can figure out the correct way to make
generate-id() deterministic.  Unfortunately, this will cause a
regression in reproducibility, but I think that's outweighed by the
breakage.

Regards,
Andrew

Bug#900248: nvidia-driver: update to 390.59 breaks direct rendering

[Andreas Beckmann]

On 2018-05-31 11:12, Luca Boccassi wrote:
> On Thu, 2018-05-31 at 11:07 +0200, Peter De Wachter wrote:
>>> Fortunately another user reported a possible alternative, if you
>>> have
>>> time could you please try to drop a nvidia.conf in
>>> /usr/share/X11/xorg.conf.d with the following content:
>>>
>>> Section "OutputClass"
>>> Identifier  "Nvidia Modules"
>>> MatchDriver "nvidia-drm"
>>> Driver  "nvidia"
>>> Option  "AllowEmptyInitialConfiguration" "true"
>>> ModulePath  "/usr/lib/nvidia"
>>> EndSection

Given that we already have
/etc/nvidia/current/nvidia-drm-outputclass.conf
with this content:

Section "OutputClass"
Identifier "nvidia"
MatchDriver"nvidia-drm"
Driver "nvidia"
EndSection

Does changing this to

Section "OutputClass"
Identifier "nvidia"
MatchDriver"nvidia-drm"
Driver "nvidia"
ModulePath "/usr/lib/xorg/modules/linux"
EndSection

(and reverting any other workarounds applied to the module)
fix the issue?
(that should be the minimal amount of changes ...)

Does this work with the xorg in stretch, too?
(as in "it does not break the driver/xorg in stretch")
(such that we hopefully don't have to handle stretch+buster differently)

Andreas

Bug#902050: kde-plasma-desktop: has severe keyboard latency when displaying remote KDE desktop

[Alan W. Irwin]

Package: kde-plasma-desktop
Version: 5:102
Severity: normal

Dear Maintainer,

Because of 
I currently cannot run this fast box (Ryzen 7 1700, 8 cores, 64GB)
very long with direct X display before it locks up.  So until that bug
is fixed (likely when kernel 4.17 propagates to Debian Buster) I run
various desktops (e.g., xfce, KDE) on this fast box with xdm installed
and configured in such a way that I can actively manage and display
those desktop results on a slow box (connected to the fast box via a
1Gb/s LAN implemented with approprate ethernet hardware on both ends
plus a crossover cable) where I execute "X -query " to
start the X server on the slow "X-terminal" box.

I typically run many instances of konsole and konqueror for my desktop
and for my previous (Jessie) version of Debian, the above X-terminal
method worked so well that it was impossible to tell from latency or
speed issues whether you were running the fast box desktop directly on
the fast box or remotely from the X-terminal.  But that has all
changed for Debian Buster of KDE where if you run, say, 5 idle
instances of konsole, the keyboard on the X terminal starts showing
severe latency issues for the active konsole (where it might take a
half second or so to get a response to an individual key stroke).

I hasten to add this is not an issue that is specific to the konsole
example I gave since similar keyboard latency issues occur for
anything having to do with the keyboard such as typing in a URL in the
location bar of konqueror, editing files, etc.  In constrast, there
appears to not be any obvious KDE desktop latency issues associated
with the mouse or display.  I have also tried running many instances
of konqueror and konsole using an XFCE desktop, and this keyboard
latency issue completely disappears for that case.  In sum, the
network neutrality you expect from X works fine for all of keyboard,
mouse, and display for many konqueror and konsole instances running on
an XFCE desktop, and *just* the keyboard part of those good
network-neutral results fails (i.e., shows severe latency issues) if
running the same number of konqueror and konsole instances on the KDE
desktop running on this fast box.

Because of this annoying KDE desktop issue with keyboard latency for
an X-terminal configuration I must necessarily use for a while, I
currently do all my work using the XFCE desktop.  But I would be happy
to try the KDE desktop remotely in an X terminal environment again if
you have some additional test you would like me to run or if there is
some newer KDE desktop version you would like me to try.

Alan

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

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

Versions of packages kde-plasma-desktop depends on:
ii  kde-baseapps  4:17.08.3+5.102
ii  plasma-desktop4:5.12.5-1
ii  plasma-workspace  4:5.12.5-1
ii  udisks2   2.7.6-3
ii  upower0.99.7-2

Versions of packages kde-plasma-desktop recommends:
ii  kwin-x11  4:5.12.5-1
pn  sddm  
ii  xserver-xorg  1:7.7+19

Versions of packages kde-plasma-desktop suggests:
pn  kdeconnect  

-- no debconf information

Bug#895482: Bug#895473: Bug#895482: Fails to upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 4

[Michael Shuler]

On 06/20/2018 04:33 PM, Sebastian Andrzej Siewior wrote:

On 2018-06-13 08:19:32 [+0200], To Axel Beckert wrote:

I asked upstream what they thing about ignoring these errors because the
perl script does so. On the other hand what about cleaning up these
dangling symlinks?


ca-certificate maintainers: what do we do here?

[ ] we intend to figure out why there are dangling symlinks, no need to
 change "openssl rehash" in anyway.

[ ] we intend to figure out why there are dangling symlinks but in the
 meantime "openssl rehash" should not error out on them.

[ ] "openssl rehash" should not error out on certificates which can not
 be opened. This is the old behavioud and required due to $reason.


[x] I intend to find the time between work, family, and multiple other
projects to attempt to reliably reproduce the problem, in order to
intelligently answer the above.

--
Kind regards,
Michael

Bug#902026: systemd: "systemctl start systemd-timesyncd.service" kills chrony

[Michael Biebl]

Am 22.06.2018 um 01:24 schrieb Michael Biebl:

> Fwiw, I'm aware of
> https://github.com/systemd/systemd/issues/7104
> 

You might also be interested in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895821

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



signature.asc
Description: OpenPGP digital signature

Bug#902049: needrestart is no longer honoring sendnotify setting

[Jon]

Package: needrestart
Version: 3.2-1
Severity: normal

Dear Maintainer,

After the recent update to needrestart it no longer honors the
sendnotify setting in needrestart.conf

-- Package-specific info:
needrestart output:
Your outdated processes:
bash[10762, 10747, 10737], irssi[10746, 3420], weechat[556]

checkrestart output:


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

Kernel: Linux 4.16.0-2-amd64 (SMP w/2 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: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages needrestart depends on:
ii  binutils   2.30-21
ii  dpkg   1.19.0.5+b1
ii  gettext-base   0.19.8.1-6+b1
ii  libintl-perl   1.26-2
ii  libmodule-find-perl0.13-1
ii  libmodule-scandeps-perl1.24-1
ii  libproc-processtable-perl  0.55-1
ii  libsort-naturally-perl 1.03-2
ii  libterm-readkey-perl   2.37-1+b2
ii  perl   5.26.2-6
ii  xz-utils   5.2.2-1.3

Versions of packages needrestart recommends:
ii  sysvinit-core  2.88dsf-59.10

Versions of packages needrestart suggests:
pn  iucode-tool  
pn  needrestart-session | libnotify-bin  

-- Configuration Files:
/etc/needrestart/needrestart.conf changed:
$nrconf{sendnotify} = 0;
$nrconf{blacklist} = [
# ignore sudo (not a daemon)
qr(^/usr/bin/sudo(\.dpkg-new)?$),
# ignore DHCP clients
qr(^/sbin/(dhclient|dhcpcd5|pump|udhcpc)(\.dpkg-new)?$),
# ignore apt-get (Debian Bug#784237)
qr(^/usr/bin/apt-get(\.dpkg-new)?$),
];
$nrconf{override_rc} = {
# DBus
qr(^dbus) => 0,
# display managers
qr(^gdm) => 0,
qr(^kdm) => 0,
qr(^nodm) => 0,
qr(^sddm) => 0,
qr(^wdm) => 0,
qr(^xdm) => 0,
qr(^lightdm) => 0,
qr(^slim) => 0,
qr(^lxdm) => 0,
# networking stuff
qr(^bird) => 0,
qr(^network-manager) => 0,
qr(^NetworkManager) => 0,
qr(^ModemManager) => 0,
qr(^wpa_supplicant) => 0,
qr(^openvpn) => 0,
qr(^quagga) => 0,
qr(^tinc) => 0,
qr(^(open|free|libre|strong)swan) => 0,
# gettys
qr(^getty@.+\.service) => 0,
# systemd --user
qr(^user@\d+\.service) => 0,
# misc
qr(^zfs-fuse) => 0,
qr(^mythtv-backend) => 0,
qr(^xendomains) => 0,
qr(^lxcfs) => 0,
qr(^libvirt) => 0,
qr(^docker) => 0,
# workaround for broken systemd-journald
# (see also Debian Bug#771122 & #771254)
qr(^systemd-journald) => 0,
# more systemd stuff
# (see also Debian Bug#784238 & #784437)
qr(^emergency\.service$) => 0,
qr(^rescue\.service$) => 0,
# do not restart oneshot services, see #862840
qr(^apt-daily\.service$) => 0,
qr(^apt-daily-upgrade\.service$) => 0,
qr(^unattended-upgrades\.service$) => 0,
# ignore rc-local.service, see #852864
qr(^rc-local\.service$) => 0,
# don't restart systemd-logind, see #798097
qr(^systemd-logind) => 0,
};
$nrconf{override_cont} = {
};
$nrconf{blacklist_interp} = [
# ignore temporary files
qr(^/tmp/),
qr(^/var/),
qr(^/run/),
];
$nrconf{blacklist_mappings} = [
# special device paths
qr(^/(SYSV( \(deleted\))?|drm(\s|$)|dev/)),
# aio(7) mapping
qr(^/\[aio\]),
# Oil Runtime Compiler's JIT files
qr#/orcexec\.[\w\d]+( \(deleted\))?$#,
# plasmashell (issue #65)
qr(/#\d+( \(deleted\))?$),
# Java Native Access
qr#/tmp/jna--#,
# Java Foreign Function Interface
qr#^/tmp/jffi#,
];
$nrconf{skip_mapfiles} = (-d '/proc/sys/kernel/grsecurity' ? -1 : 0);
if(-d q(/etc/needrestart/conf.d)) {
  foreach my $fn (sort ) {
  print STDERR "$LOGPREF eval $fn\n" if($nrconf{verbose});
  eval do { local(@ARGV, $/) = $fn; <>};
  die "Error parsing $fn: $@" if($@);
  }
}


-- no debconf information

Bug#882380: initramfs-tools: Update-initramfs can take an unnecessarily long time if other disk activity is ongoing

[Colin Watson]

On Wed, Nov 22, 2017 at 01:05:00AM +0200, Jukka Tastula wrote:
> After generating an initrd update-initramfs calls sync unconditinally. This
> can take a very long time to return if other disk activity, like perhaps a
> long backup job, is running simultaneously. Suggest only syncing the 
> filesystem the initrd is actually placed on instead.

I think this is a good idea, and it would also avoid upgrade problems
such as
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1667512
in the case of things like stuck NFS mounts.

To avoid backport surprises, I would suggest adding a dependency on
coreutils (>= 8.24), which introduced the feature of sync(1) being used
here.

I've put all this in a merge request:

  https://salsa.debian.org/kernel-team/initramfs-tools/merge_requests/6

-- 
Colin Watson   [cjwat...@debian.org]

Bug#902026: systemd: "systemctl start systemd-timesyncd.service" kills chrony

[Michael Biebl]

Am 21.06.2018 um 23:34 schrieb Francesco Poli:
> On Thu, 21 Jun 2018 22:52:37 +0200 Michael Biebl wrote:
> 
> [...]
>> I would check the journal and try to correlate it with other events
>> based on the timestamp
> 
> By looking at the journal timestamps and the root bash history, it
> really seems that chrony was stopped (and timesyncd was started) when I
> issued the commands:
> 
>   # systemctl daemon-reexec
>   # service systemd-logind restart
> 
> I will look more carefully next time, and I will check if/when chrony
> gets stopped.

Fwiw, I'm aware of
https://github.com/systemd/systemd/issues/7104

Your issue, at least how you described it, sounds different though.
If you explicitly start timesyncd, having chronyd stopped is totally
expected.

If you do have an alternative NTP client installed, the Conflicts should
be sufficient. To be sure timesyncd is not started during boot, you can
simply disable it though.


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



signature.asc
Description: OpenPGP digital signature

Bug#901715: debhelper: dh_install unexpected behaviour when ".install" file has an executable bit

[gregor herrmann]

Control: severity -1 wishlist
Control: retitle -1 debhelper: improve documentation for executable config 
files in debhelper(7)

On Mon, 18 Jun 2018 09:34:42 +0300, Nadav Ruskin wrote:

> I see! I understand now, thanks to your explanation. I can use your
> "stupid" script as a small hack to move development back to WSL. Thanks!

Great.

> I showed the documentation to a few of my colleagues and none of them could
> make use of it. It is not intuitive to any of us to expect a configuration
> file to be replaceable with an executable that echoes back configurations.
> Is this common practice in Linux? I highly recommend a simple explanation
> like the one you just said is added to the documentation.

I'm leaving this to the debhelper maintainers, while adjusting the
bug metadata.


Cheers,
gregor, just a happy debhelper user
 
-- 
 .''`.  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: Flying Pickets


signature.asc
Description: Digital Signature

Bug#902048: usbguard: forbids smartphone charge

[Jiff]

Source: usbguard
Version: 0.6.2+ds1-2
Severity: normal

Dear Main tainer,

Hi folks,

   * What led up to the situation?

An attempt to charge my authorized smartphone (SE xperia x10)

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

Even if the energy on symbol was on screen, it didn't charge at all.

   * What was the outcome of this action?

As the phone was discharging, I unplugged it, stopped the usbguard daemon and
re-plugged it in; this time it was charging normally.

   * What outcome did you expect instead?

An authorized smartphone device to correctly charge.


NB: I compiled and intalled the latest stable, version 0.7.0, but the issue's
still here - duno if it is tied to this phone or not (I don't have another one
from another brand to test.)

Jean-Yves



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

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

Bug#901487: libgpuarray 0.7.0

[Rebecca N. Palmer]

Control: tags -1 patch

The only required packaging change to build the new version is to update 
the soname (see below).  I only tested the Python 3 version on pocl, 
which passes (i.e. #870128 is gone as expected).


Other things you might want to look at while you're making an upload:
- libgpuarray3 should probably Depend: ocl-icd-opencl-dev and Recommend: 
libclblas-dev (it dlopen()s them; -dev because it uses the un-numbered 
names)

- the Lintian warnings

#note file rename
--- a/debian/libgpuarray2.install
+++ b/debian/libgpuarray3.install
@@ -1 +1 @@
-usr/lib/libgpuarray.so.2*
+usr/lib/libgpuarray.so.3*
--- a/debian/control
+++ b/debian/control
@@ -31,7 +31,7 @@ Vcs-Browser: https://anonscm.debian.org/
 Vcs-Git: 
https://anonscm.debian.org/git/debian-science/packages/libgpuarray.git

 Homepage: https://github.com/Theano/libgpuarray

-Package: libgpuarray2
+Package: libgpuarray3
 Architecture: any
 Depends: ${misc:Depends},
  ${shlibs:Depends}
@@ -51,7 +51,7 @@ Package: libgpuarray-dev
 Architecture: any
 Section: libdevel
 Depends: ${misc:Depends},
- libgpuarray2 (= ${binary:Version})
+ libgpuarray3 (= ${binary:Version})
 Suggests: libgpuarray-doc 
 Description: development files for libgpuarray
  libgpuarray provides a ndarray (multi-dimensional array) object which
@@ -91,7 +91,7 @@ Section: python
 Depends: ${misc:Depends},
  ${python:Depends},
  ${shlibs:Depends},
- libgpuarray2 (= ${binary:Version})
+ libgpuarray3 (= ${binary:Version})
 Suggests: libgpuarray-doc 
 Description: language bindings for libgpuarray (Python 2)
  libgpuarray provides a ndarray (multi-dimensional array) object which
@@ -132,7 +132,7 @@ Section: python
 Depends: ${misc:Depends},
  ${python3:Depends},
  ${shlibs:Depends},
- libgpuarray2 (= ${binary:Version})
+ libgpuarray3 (= ${binary:Version})
 Suggests: libgpuarray-doc 
 Description: language bindings for libgpuarray (Python 3)
  libgpuarray provides a ndarray (multi-dimensional array) object which

Bug#902026: systemd: "systemctl start systemd-timesyncd.service" kills chrony

[Francesco Poli]

On Thu, 21 Jun 2018 22:52:37 +0200 Michael Biebl wrote:

[...]
> I would check the journal and try to correlate it with other events
> based on the timestamp

By looking at the journal timestamps and the root bash history, it
really seems that chrony was stopped (and timesyncd was started) when I
issued the commands:

  # systemctl daemon-reexec
  # service systemd-logind restart

I will look more carefully next time, and I will check if/when chrony
gets stopped.

Bye and thanks for your help so far!

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgprJeE3QPkJY.pgp
Description: PGP signature

Bug#886969: Bug#886625: push-source should be usable no matter the state of the working tree

[Sean Whitton]

Hello,

On Thu, Jun 21 2018, Ian Jackson wrote:

>> This might be a reason to not remove but instead firmly deprecate
>> build-source, until one can dgit push to security-master.
>
> I don't really mind deprecating it.  Dropping it entirely would be a
> different matter.  It might be embedded in people's workflows.  FTR
> I'm the kind of person who takes ages to remove old stuff.

Fair enough.  I'd like to both deprecate in the docs and add some output
saying it's deprecated.

>>   The reason for limiting dgit subcommands in this way is to restrict
>> dgit's role to being the bidirectional archive<>git gateway, not an
>> all purpose Debian packaging wrapper script like git-buildpackage is.
>
> I keep saying this: I would love for dgit not to be a general purpose
> wrapper but until the .gitignore bug is fixed in all other tools it
> will have to continue to be so (and then for some time afterwards).
>
> (Also, -wgf.)
>
> I mind much less that dgit is a general purpose wrapper (even though I
> have to maintain and test a stupid pile of wrapper and command line
> parsing code) than the fact that users can't use their existing build
> tooling.

As you know, I think these are the right priorities to have.  I agree on
both counts.

Still, it's nice that even with these compromises dgit manages to be
much less a general purpose wrapper that other tools are.

> Also in this area is the need for a way to do an sbuild on a git tree
> which is not a fixed point under (or, even, representable by)
> dpkg-source.  There's a bug about that too.

Yes.  That one's really difficult.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#900373: Update - plasmashell too

[Alex Dănilă]

¡Hola!

I confirm this no longer happens after upgrading 18.1.1. Sorry for the 
late reply, I got a freeze once more after upgrading but it probably was 
something else and it didn't cross my mind to attach gdb.


Alex

On 08/06/2018 09:02, Maximiliano Curia wrote:

¡Hola Alex!

El 2018-06-07 a las 22:29 +0300, Alex Dănilă escribió:
The same started to happen for plasmashell too. It happens from time 
to time when it shows a notification or a pop-up (for example the 
window preview when hovering the task bar). Here's the stack:


This is probably #900145 [1]

Which versions of mesa (libgl1-mesa-dri) and xorg-server 
(xserver-xorg-core) are you running?


[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900145

Happy hacking,

Bug#899238: RFP: ppx-tools-versioned -- Tools for authors of ppx rewriters

[Mehdi Dogguy]

Hi Andy,

On 2018-06-20 11:52, Andy Li wrote:


I've created an initial version of the package in salsa:
https://salsa.debian.org/ocaml-team/ppx-tools-versioned
Tested building it with sbuild (and adt-run) for both amd64 and mips.
Would you review it?



Excellent work! I've reviewed it and it looks fine. I'll upload it 
shortly.

Would you mind retitling thing bug to an "ITP: ..." and setting yourself
as its owner?

Cheers,

--
Mehdi

Bug#902047: RFS: nautilus-hide/0.2.3-4

[Carlos Maddela]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "nautilus-hide"

 * Package name: nautilus-hide
   Version : 0.2.3-4
   Upstream Author : 2015-2017 Bruno Nova 
 * URL : https://github.com/brunonova/nautilus-hide
 * License : GPL-3+
   Section : gnome

  It builds this binary package:

nautilus-hide - Extension for Nautilus to hide files without renaming them

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

  https://mentors.debian.net/package/nautilus-hide


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

dget -x 
https://mentors.debian.net/debian/pool/main/n/nautilus-hide/nautilus-hide_0.2.3-4.dsc

  Changes since the last upload:

  * Update Vcs-* details to official Debian repo.


  Regards,
   Carlos Maddela

Bug#902026: systemd: "systemctl start systemd-timesyncd.service" kills chrony

[Michael Biebl]

Am 21.06.2018 um 22:07 schrieb Francesco Poli:
> On Thu, 21 Jun 2018 21:57:29 +0200 Michael Biebl wrote:
> 
>> Am 21.06.2018 um 21:16 schrieb Francesco Poli:
> [...]
>>> Now, it seems that I will *also* have to manually issue the following
>>> command:
>>>
>>>   # systemctl --now mask systemd-timesyncd
>>>
>>> before installing and configuring chrony.
>>>
>>> Is this correct?
>>>
>>
>> No, this is not correct.
> 
> Weird!
> 
> The fact is that, at some point, I found out that chrony was no longer
> running on my box, while systemd-timesyncd was somehow running instead.
> 
> I am pretty sure I had *not* manually issued a "service
> systemd-timesyncd start" command before that point in time.
> I only issued that command afterwards, while investigating the mystery,
> and saw that it had the power to stop chrony.
> 
> Do you have any idea about what could have happened?

I would check the journal and try to correlate it with other events
based on the timestamp


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



signature.asc
Description: OpenPGP digital signature

Bug#902046: RFS: nautilus-admin/1.1.6-2

[Carlos Maddela]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "nautilus-admin"

 * Package name: nautilus-admin
   Version : 1.1.6-2
   Upstream Author : Bruno Nova 
 * URL : https://github.com/brunonova/nautilus-admin
 * License : GPL-3+
   Section : gnome

  It builds this binary package:

nautilus-admin - Extension for Nautilus to do administrative operations

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

  https://mentors.debian.net/package/nautilus-admin


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

dget -x 
https://mentors.debian.net/debian/pool/main/n/nautilus-admin/nautilus-admin_1.1.6-2.dsc

  Changes since the last upload:

  * Update Vcs-* details to official Debian repo.


  Regards,
   Carlos Maddela

Bug#777667: RFA: topgit -- a Git patch queue manager

[Uwe Kleine-König]

Control: retitle 777667 O: topgit -- a Git patch queue manager

> I request an adopter for the topgit package.
> 
> The package description is:
>  TopGit manages a patch queue using Git topic branches, one patch per
>  branch. It allows for patch dependencies and can thus manage
>  non-linear patch series.
>  .
>  TopGit is a minimal layer on top of Git, which does not limit use of
>  Git's functionality (such as the index). It rigorously keeps history
>  until a patch is accepted upstream. It is also fully usable across
>  distributed repositories.
> 
> I don't actively use topgit anymore since quite some time and the last
> few updates were done by NMUs. So if someone wants to adopt the package,
> please do so.

Given that nothing happend in Debian for topgit since I RFA'd topgit and
the last upstream change was in 2013 I consider topgit dead.

So I orphan topgit.

Best regards
Uwe


signature.asc
Description: PGP signature

Bug#902045: RFS: ncurses-hexedit/0.9.7+orig-5

[Carlos Maddela]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "ncurses-hexedit"

 * Package name: ncurses-hexedit
   Version : 0.9.7+orig-5
   Upstream Author : Adam Rogoyski 
 * URL : http://www.rogoyski.com/adam/programs/hexedit/
 * License : GPL-2.0+
   Section : editors

  It builds this binary package:

ncurses-hexedit - Edit files/disks in hex, ASCII and EBCDIC

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

  https://mentors.debian.net/package/ncurses-hexedit


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

dget -x 
https://mentors.debian.net/debian/pool/main/n/ncurses-hexedit/ncurses-hexedit_0.9.7+orig-5.dsc

  Changes since the last upload:

  * Update Vcs-* details to official Debian repo.


  Regards,
   Carlos Maddela

Bug#898784: ITP: r-cran-rstan -- GNU R interface to Stan

[Benjamin K Goodrich]

I am the upstream maintainer for RStan. Thank you for packaging it for Debian.

I noticed there is a DFSG concern with the R/sysdata.rda file. The
source to generate that file is in tools/stan-functions.R . If you
like, you could drop R/sysdata.rda and regenerate it at build time by
sourcing tools/stan-functions.R .

Bug#877041: ITA: ublock-origin — general-purpose lightweight ads, malware, tracks blocker

[Chris]

Best regards,
Chris

Bug#902044: Request for an update of the Debian speaker's information

[Geert Stappers]

Package: www.debian.org


Dear maintainers of www.debian.org,

It this bugreport the proper way to request
an update on https://www.debian.org/events/speakers/ ?

If not: Please advice for further directions

If yes: See below


Cheers
Geert Stappers
Debian Developer
Recieves e-mail sent to  events@d.o.


On Tue, Jun 19, 2018 at 10:30:34AM +0200, Joost van Baal-Ili?? wrote:
> I believe Jaminy would like to get added to
> https://www.debian.org/events/speakers/ .
> 
> events team: Would a bugreport to www.debian.org be the way to go?
> 
> Bye, Joost
> 
> On Tue, Jun 19, 2018 at 08:54:43AM +0200, Geert Stappers wrote:
> > On Tue, Jun 19, 2018 at 10:38:27AM +0530, Jaminy Prabaharan wrote:
> > > Hi,
> > > 
> > > I have attached the following details to add as Debian speaker.
> > 
> > 
> > That "to add as Debian speaker" is to what?
> > 
> > Please elaborate
> > 
> > 
> > > Name: Jaminy Prabaharan
> > > 
> > > Email: jamin...@gmail.com
> > > 
> > > Previous Talks:
> > >   
> > > http://events.linuxfoundation.org/events/open-source-summit-japan/program/slides,
> > >   https://debconf16.debconf.org/talks/14/,
> > >   https://fosdem.org/2017/schedule/event/improving_rtc/,
> > >   https://lc32018.sched.com/event/FBuX
> > > 
> > > Languages: English
> > > 
> > > Location: SriLanka
> > > 
> > > Topics: Real Time Communication with free software, Embedded applications
> > > with Debian
> > > 
> > > Best Regards,
> > > Jaminy.
> > 
> >  
> > Groeten
> > Geert Stappers
> > DD
> > -- 
> > Leven en laten leven
> 
> 

-- 
Groeten
Geert Stappers
-- 
Leven en laten leven


signature.asc
Description: Digital signature

Bug#902043: asis: FTBFS error: "asis_ul-compiler_options.adb" must be recompiled ("gpr.ads" has been modified)

[Andreas Beckmann]

Source: asis
Version: 2017-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

asis/experimental recently started to FTBFS:

[...]
Changing to object directory of "Asis": "/build/asis-2017/obj/"
/usr/lib/gprbuild/gprlib asis.lexch
/usr/bin/ar cr /build/asis-2017/lib/libasis.a 
/build/asis-2017/obj/a4g-contt-sd.o /build/asis-2017/obj/asis-iterator.o 
/build/asis-2017/obj/asis-expressions.o /build/asis-2017/obj/a4g-mapping.o 
/build/asis-2017/ob
j/a4g-a_debug.o /build/asis-2017/obj/a4g-queries.o 
/build/asis-2017/obj/asis-extensions-strings.o 
/build/asis-2017/obj/a4g-contt-dp.o /build/asis-2017/obj/asis-text-set_get.o 
/build/asis-2017/obj/a4g-a_output.o /b
uild/asis-2017/obj/asis-elements.o 
/build/asis-2017/obj/asis-implementation-permissions.o 
/build/asis-2017/obj/a4g-encl_el.o /build/asis-2017/obj/a4g-a_types.o 
/build/asis-2017/obj/asis-declarations.o /build/asis-
2017/obj/a4g-defaults.o /build/asis-2017/obj/asis-data_decomposition-debug.o 
/build/asis-2017/obj/a4g-a_alloc.o 
/build/asis-2017/obj/asis-compilation_units-times.o 
/build/asis-2017/obj/asis-implementation.o /build
/asis-2017/obj/a4g-a_elists.o /build/asis-2017/obj/a4g-vcheck.o 
/build/asis-2017/obj/a4g-tree_rec.o /build/asis-2017/obj/asis-set_get.o 
/build/asis-2017/obj/asis-ids.o /build/asis-2017/obj/asis-extensions-iterator
.o /build/asis-2017/obj/a4g-decl_sem.o /build/asis-2017/obj/a4g-u_conv.o 
/build/asis-2017/obj/a4g-stand.o 
/build/asis-2017/obj/asis-ada_environments-containers.o 
/build/asis-2017/obj/a4g-itests.o /build/asis-2017/obj/a4g-expr_sem.o 
/build/asis-2017/obj/asis-data_decomposition-aux.o 
/build/asis-2017/obj/a4g-a_stand.o 
/build/asis-2017/obj/asis-data_decomposition-vcheck.o 
/build/asis-2017/obj/a4g-dda_aux.o /build/asis-2017/obj/a4g-asis_tables.o 
/build/asis-2017/obj/a4g-skip_tb.o /build/asis-2017/obj/a4g-a_osint.o 
/build/asis-2017/obj/a4g-unit_rec.o /build/asis-2017/obj/a4g-int_knds.o 
/build/asis-2017/obj/a4g-contt-tt.o /build/asis-2017/obj/asis-extensions.o 
/build/asis-2017/obj/asis-statements.o 
/build/asis-2017/obj/a4g-span_beginning.o 
/build/asis-2017/obj/asis-exceptions.o /build/asis-2017/obj/a4g-get_unit.o 
/build/asis-2017/obj/asis-limited_views.o /build/asis-2017/obj/a4g.o 
/build/asis-2017/obj/asis-extensions-flat_kinds.o 
/build/asis-2017/obj/a4g-knd_conv.o /build/asis-2017/obj/asis-definitions.o 
/build/asis-2017/obj/a4g-a_sem.o /build/asis-2017/obj/a4g-norm.o 
/build/asis-2017/obj/a4g-contt-ut.o 
/build/asis-2017/obj/asis-compilation_units-relations.o 
/build/asis-2017/obj/asis-clauses.o 
/build/asis-2017/obj/asis-data_decomposition-set_get.o 
/build/asis-2017/obj/a4g-span_end.o /build/asis-2017/obj/asis.o 
/build/asis-2017/obj/asis-data_decomposition-extensions.o 
/build/asis-2017/obj/a4g-a_sinput.o 
/build/asis-2017/obj/asis-data_decomposition.o 
/build/asis-2017/obj/asis-compilation_units.o 
/build/asis-2017/obj/asis-errors.o /build/asis-2017/obj/a4g-cu_info2.o 
/build/asis-2017/obj/asis-ada_environments.o /build/asis-2017/obj/asis-text.o 
/build/asis-2017/obj/a4g-a_opt.o /build/asis-2017/obj/a4g-gnat_int.o 
/build/asis-2017/obj/a4g-contt.o /build/asis-2017/obj/a4g-ee_cache.o 
/build/asis-2017/obj/a4g-gnsa_switch.o
/usr/bin/ranlib /build/asis-2017/lib/libasis.a
Changing to object directory of "Generate_Factory": 
"/build/asis-2017/tools/tool_utils/"
/usr/lib/gprbuild/gprbind ada_trees-generate_factory.bexch
/usr/bin/gnatbind -shared -o b__ada_trees-generate_factory.adb 
/build/asis-2017/tools/tool_utils/ada_trees-generate_factory.ali -static -x -O
error: "asis_ul-compiler_options.adb" must be recompiled ("gpr.ads" has been 
modified)
error: "gnatcoll-projects.adb" must be compiled
error: ("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll/gnatcoll-projects.ali" 
is obsolete and read-only)
error: "gnatcoll-projects-krunch.adb" must be compiled
error: 
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll/gnatcoll-projects-krunch.ali" 
is obsolete and read-only)
error: "gnatcoll-projects-normalize.adb" must be compiled
error: 
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll/gnatcoll-projects-normalize.ali"
 is obsolete and read-only)
gprbind: invocation of gnatbind failed
gprbuild: unable to bind ada_trees-generate_factory.adb
make[1]: *** [debian/rules:75: build-factory] Error 4
make[1]: Leaving directory '/build/asis-2017'
make: *** [debian/rules:36: build] Error 2


Andreas


asis_2017-3.log.gz
Description: application/gzip

Bug#902042: stretch-pu: package libdate-holidays-de-perl/1.9-1+deb9u1

[Christoph Biedl]

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

Hello release team,

in continuation of #891807: Two more states in Germany made Reformation
Day (Oct 31st) a holiday. To keep libdate-holidays-de-perl in sync,
I've prepared 1.9-1+deb9u2. The related upload for sid (1.9-3) has been
accepted a few minutes ago. Upload to 9/stretch/stable will follow in a
moment, following the new stable release policy.

FWIW, there are currently no further plans to change holidays in
Germany, so this is hopefully the last update for a long time.

Kind regards,

Christoph

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

Kernel: Linux 4.14.48 (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/dash
Init: unable to detect

diff -Nru libdate-holidays-de-perl-1.9/debian/changelog 
libdate-holidays-de-perl-1.9/debian/changelog
--- libdate-holidays-de-perl-1.9/debian/changelog   2018-03-01 
00:06:15.0 +0100
+++ libdate-holidays-de-perl-1.9/debian/changelog   2018-06-21 
20:40:29.0 +0200
@@ -1,3 +1,10 @@
+libdate-holidays-de-perl (1.9-1+deb9u2) stretch; urgency=medium
+
+  * Mark Reformation Day as a holiday in Niedersachsen and Bremen
+from 2018 on
+
+ -- Christoph Biedl   Thu, 21 Jun 2018 
20:40:29 +0200
+
 libdate-holidays-de-perl (1.9-1+deb9u1) stretch; urgency=low
 
   * Mark Reformation Day as a holiday in Hamburg and
diff -Nru libdate-holidays-de-perl-1.9/debian/patches/refo.patch 
libdate-holidays-de-perl-1.9/debian/patches/refo.patch
--- libdate-holidays-de-perl-1.9/debian/patches/refo.patch  2018-03-01 
00:06:05.0 +0100
+++ libdate-holidays-de-perl-1.9/debian/patches/refo.patch  2018-06-21 
20:40:21.0 +0200
@@ -1,17 +1,20 @@
 Subject: Add new regional holidays from 2018 on
 Author: Christoph Biedl 
 Forwarded: https://rt.cpan.org/Ticket/Display.html?id=124559
-Last-Update: 2018-02-28
+Last-Update: 2018-06-21
 
-Sources (in German):
-Schleswig-Holstein:
-
http://www.spiegel.de/karriere/reformationstag-wird-in-schleswig-holstein-neuer-feiertag-a-1195092.html
-Hamburg:
-
http://www.spiegel.de/karriere/hamburg-reformationstag-wird-feiertag-a-1195881.html
+Source (in German):
+https://de.wikipedia.org/wiki/Reformationstag#Deutschland
 
 --- a/DE.pm
 +++ b/DE.pm
-@@ -121,6 +121,9 @@
+@@ -118,9 +118,15 @@
+ 
+   # Extras for Bremen
+   @{$holidays{'hb'}} = qw();
++  if ($year >= 2018) {
++  push @{$holidays{'hb'}}, qw(refo);
++  }
  
# Extras for Hamburg
@{$holidays{'hh'}} = qw();
@@ -21,7 +24,17 @@
  
# Extras for Hessen
@{$holidays{'he'}} = qw(fron);
-@@ -148,6 +151,9 @@
+@@ -130,6 +136,9 @@
+ 
+   # Extras for Niedersachsen
+   @{$holidays{'ni'}} = qw();
++  if ($year >= 2018) {
++  push @{$holidays{'ni'}}, qw(refo);
++  }
+ 
+   # Extras for Nordrhein-Westfalen
+   @{$holidays{'nw'}} = qw(fron alhe);
+@@ -148,6 +157,9 @@
  
# Extras for Schleswig-Holstein
@{$holidays{'sh'}} = qw();


signature.asc
Description: PGP signature

Bug#902026: systemd: "systemctl start systemd-timesyncd.service" kills chrony

[Francesco Poli]

On Thu, 21 Jun 2018 21:57:29 +0200 Michael Biebl wrote:

> Am 21.06.2018 um 21:16 schrieb Francesco Poli:
[...]
> > Now, it seems that I will *also* have to manually issue the following
> > command:
> > 
> >   # systemctl --now mask systemd-timesyncd
> > 
> > before installing and configuring chrony.
> > 
> > Is this correct?
> > 
> 
> No, this is not correct.

Weird!

The fact is that, at some point, I found out that chrony was no longer
running on my box, while systemd-timesyncd was somehow running instead.

I am pretty sure I had *not* manually issued a "service
systemd-timesyncd start" command before that point in time.
I only issued that command afterwards, while investigating the mystery,
and saw that it had the power to stop chrony.

Do you have any idea about what could have happened?

Thanks for your prompt replies and for any additional help you may
provide!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgplOBkNURRI5.pgp
Description: PGP signature

Bug#902034: transition: ros-geometric-shapes

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 21/06/18 20:25, Jochen Sprickerhof wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear release team,
> 
> I would like to transition ros-geometric-shapes. It's only a dependency
> of ros-robot-model, which I'm maintaining as well.

Sure, go ahead.

Emilio

Bug#902026: systemd: "systemctl start systemd-timesyncd.service" kills chrony

[Michael Biebl]

Am 21.06.2018 um 21:16 schrieb Francesco Poli:

> Some time ago, I just had to install chrony (and set it up) in
> order to make it work, without systemd-timesyncd interfering.
> 
> Now, it seems that I will *also* have to manually issue the following
> command:
> 
>   # systemctl --now mask systemd-timesyncd
> 
> before installing and configuring chrony.
> 
> Is this correct?
> 

No, this is not correct.



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



signature.asc
Description: OpenPGP digital signature

Bug#902026: systemd: "systemctl start systemd-timesyncd.service" kills chrony

[Michael Biebl]

Am 21.06.2018 um 21:16 schrieb Francesco Poli:
> On Thu, 21 Jun 2018 20:47:36 +0200 Michael Biebl wrote:
> 
>> Am 21.06.2018 um 19:36 schrieb Francesco Poli (wintermute):
> [...]
>>> systemd-timesyncd
> [...] 
>>> used to refuse to start, whenever other NTP clients (such as chrony)
>>> were used.
> [...]
>>> But, as soon as I issue:
>>>
>>>   # service systemd-timesyncd start
>>>
>>> chrony dies and systemd-timesyncd starts.
>>
>> If you manually start systemd-timesyncd, then indeed chronyd is stopped
> 
> But then, this can happen whenever services are (re-)started, such as
> at boot time or when "systemctl daemon-reexec" is issued.

It should not happen during boot time, as the ConflictedBy service will
not be started.

daemon-reexec does not restart services.






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



signature.asc
Description: OpenPGP digital signature

Bug#901252: vlc: Fail to launch, QPainter not active

[Pierre Haessig]

Package: src:vlc
Version: 3.0.2-0+deb9u1
Followup-For: Bug #901252

Dear Maintainer,

I face the same problem on my Debian stretch, after upgrading to Vlc 3. Maybe
the bug title can be adapted, because it doesn't exactly fail to lauch, only it
does not open its window. It doesn't crash either (Ctrl+C is needed to exit it
from the command line). In fact it just hangs without opening its window.

The printed lines are, as reported, full of "QPainter::: Painter not
active" messages. I also noticed "QXcbConnection: XCB error ..." which is maybe
a deeper symptom.

Please find attached the log output of $vlc -vv >vlc_log.txt 2>&1.

Best, Pierre



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

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

Versions of packages vlc depends on:
ii  dpkg 1.18.24
ii  vlc-bin  3.0.2-0+deb9u1
ii  vlc-l10n 3.0.2-0+deb9u1
ii  vlc-plugin-base  3.0.2-0+deb9u1
ii  vlc-plugin-qt3.0.2-0+deb9u1
ii  vlc-plugin-video-output  3.0.2-0+deb9u1

Versions of packages vlc recommends:
ii  vlc-plugin-notify  3.0.2-0+deb9u1
ii  vlc-plugin-samba   3.0.2-0+deb9u1
ii  vlc-plugin-skins2  3.0.2-0+deb9u1
ii  vlc-plugin-video-splitter  3.0.2-0+deb9u1
ii  vlc-plugin-visualization   3.0.2-0+deb9u1

vlc suggests no packages.

Versions of packages libvlc-bin depends on:
ii  libc62.24-11+deb9u3
ii  libvlc5  3.0.2-0+deb9u1

Versions of packages libvlc5 depends on:
ii  dpkg 1.18.24
ii  libc62.24-11+deb9u3
ii  libvlccore9  3.0.2-0+deb9u1

Versions of packages libvlc5 recommends:
ii  libvlc-bin  3.0.2-0+deb9u1

Versions of packages libvlccore8 depends on:
ii  dpkg 1.18.24
ii  libc62.24-11+deb9u3
ii  libdbus-1-3  1.10.26-0+deb9u1
ii  libidn11 1.33-1

Versions of packages libvlccore8 recommends:
ii  libproxy-tools  0.4.14-2

Versions of packages vlc-bin depends on:
ii  libc6   2.24-11+deb9u3
ii  libvlc-bin  3.0.2-0+deb9u1
ii  libvlc5 3.0.2-0+deb9u1

Versions of packages vlc-plugin-base depends on:
ii  dpkg 1.18.24
ii  liba52-0.7.4 0.7.4-19
ii  libarchive13 3.2.2-2
ii  libasound2   1.1.3-5
ii  libass5  1:0.13.4-2
ii  libavahi-client3 0.6.32-2
ii  libavahi-common3 0.6.32-2
ii  libavc1394-0 0.5.4-4+b1
ii  libavcodec57 7:3.2.10-1~deb9u1
ii  libavformat577:3.2.10-1~deb9u1
ii  libavutil55  7:3.2.10-1~deb9u1
ii  libbasicusageenvironment12016.11.28-1
ii  libbluray1   1:0.9.3-3
ii  libc62.24-11+deb9u3
ii  libcairo21.14.8-1
ii  libcddb2 1.3.2-5
ii  libchromaprint1  1.4.2-1
ii  libcrystalhd31:0.0~git20110715.fdd2f19-12
ii  libdbus-1-3  1.10.26-0+deb9u1
ii  libdc1394-22 2.2.5-1
ii  libdca0  0.0.5-10
ii  libdvbpsi10  1.3.0-5
ii  libdvdnav4   5.0.3-3
ii  libdvdread4  5.0.3-2
ii  libebml4v5   1.3.4-1
ii  libfaad2 2.8.0~cvs20161113-1
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libfribidi0  0.19.7-1+b1
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libgcrypt20  1.7.6-2+deb9u3
ii  libglib2.0-0 2.50.3-2
ii  libgnutls30  3.5.8-5+deb9u3
ii  libgpg-error01.26-2
ii  libgroupsock82016.11.28-1
ii  libharfbuzz0b1.4.2-1
ii  libjpeg62-turbo  1:1.5.1-2
ii  libkate1 0.4.1-7+b1
ii  liblirc-client0  0.9.4c-9
ii  liblivemedia57   2016.11.28-1
ii  liblua5.2-0  5.2.4-1.1+b2
ii  libmad0  0.15.1b-8+deb9u1
ii  libmatroska6v5   1.4.5-2
ii  libmicrodns0 0.0.3-3
ii  libmpcdec6   2:0.1~r495-1+b1
ii  libmpeg2-4   0.5.1-7+b2
ii  libmpg123-0  1.23.8-1+b1
ii  libmtp9  1.1.13-1
ii  libncursesw5 6.0+20161126-1+deb9u2
ii  libnfs8   

Bug#902033: ogdi-dfsg FTCBFS: does not propagate compiler from ./configure to make

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Helmut,

Thanks for the patch, it's been added in git and a new upload to
unstable will follow shortly.

Kind Regards,

Bas

Bug#902041: openmpi: broken on armel

[Ansgar Burchardt]

Source: openmpi
Version: 3.1.0-7
Severity: serious

OpenMPI seems to be very broken on armel.  The C++ program below hangs
often at a random iteration on abel.d.o (in a sid_armel-dchroot).

I built the program using `mpic++ -Wall -std=c++14 -o test test.cc` and
ran it with two ranks `mpirun -np 2 ./test`.

Ansgar



#include 

#include 

int main(int argc, char** argv)
{
MPI_Init(, );

int rank, size;
MPI_Comm_rank(MPI_COMM_WORLD, );
MPI_Comm_size(MPI_COMM_WORLD, );

for (int j = 0; j < 1024; ++j) {

std::cout << "j = " << j << std::endl;

MPI_Request req[2];

const char out[4] = {1, 2, 3, 4};
char in[4];

int dest = (rank + 1) % size;
int source = (size + rank - 1) % size;

MPI_Isend(out, 4, MPI_BYTE, dest, 0, MPI_COMM_WORLD, [0]);
MPI_Irecv(in, 4, MPI_BYTE, source, 0, MPI_COMM_WORLD, [1]);

MPI_Waitall(2, req, MPI_STATUSES_IGNORE);
}

MPI_Finalize();
return 0;
}

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

[Francesco Poli]

On Wed, 20 Jun 2018 15:33:20 +0100 Brian Potkin wrote:

[...]
> Looking at the debug2 error log lead me to putting
> 
>   PreserveJobHistory No
> 
> in cupsd.conf. This gives reliable and consistent socket activation
> and timing out. How about for you?

Thanks for the suggestion.

Now I am trying with the following configuration:

  $ grep -v '^#' /etc/cups/cupsd.conf | head -n 18
  
  LogLevel warn
  PageLogFormat
  
  MaxLogSize 0
  
  Listen localhost:631
  Listen /var/run/cups/cups.sock
  IdleExitTimeout 60
  PreserveJobHistory No
  
  Browsing No
  BrowseLocalProtocols dnssd
  
  DefaultAuthType Basic
  
  WebInterface No


Judging from the few tests that I could perform (without wiping out the
whole Amazon rainforest, print test after print test!), socket
activation seems to work as intended.
I hope it will go on working correctly...



-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpeUUDKlaAZW.pgp
Description: PGP signature

Bug#886969: Bug#886625: push-source should be usable no matter the state of the working tree

[Ian Jackson]

Sean Whitton writes ("Bug#886969: Bug#886625: push-source should be usable no 
matter the state of the working tree"):
> On Sun, Apr 22 2018, Sean Whitton wrote:
> > I thought of a case where a .dsc is not sufficient and one needs a
> > .changes: services like .
> 
> I thought of one more case recently: uploading to security-master.  You
> can't dgit push there yet, so you need an _source.changes.

You can't do a source-only upload either, so you have to do something
like dgit sbuild.  (Obvs. you don't want to upload to -security
binaries made in your random workstation environment.)

I have been using dgit sbuild -A, and then dput followed by a push to
salsa.  It's quite unsatisfactory really (but better than the
alternatives).

> This might be a reason to not remove but instead firmly deprecate
> build-source, until one can dgit push to security-master.

I don't really mind deprecating it.  Dropping it entirely would be a
different matter.  It might be embedded in people's workflows.  FTR
I'm the kind of person who takes ages to remove old stuff.

I agree that there should be dgit export-dsc, and that it should be
possible to dgit push-source with a dirty tree by using sufficiently
vigorous command line options.

>   The reason for limiting dgit subcommands in this way is to
> restrict dgit's role to being the bidirectional archive<>git
> gateway, not an all purpose Debian packaging wrapper script like
> git-buildpackage is.

I keep saying this: I would love for dgit not to be a general purpose
wrapper but until the .gitignore bug is fixed in all other tools it
will have to continue to be so (and then for some time afterwards).

(Also, -wgf.)

I mind much less that dgit is a general purpose wrapper (even though I
have to maintain and test a stupid pile of wrapper and command line
parsing code) than the fact that users can't use their existing build
tooling.

Also in this area is the need for a way to do an sbuild on a git tree
which is not a fixed point under (or, even, representable by)
dpkg-source.  There's a bug about that too.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#902026: systemd: "systemctl start systemd-timesyncd.service" kills chrony

[Francesco Poli]

On Thu, 21 Jun 2018 20:47:36 +0200 Michael Biebl wrote:

> Am 21.06.2018 um 19:36 schrieb Francesco Poli (wintermute):
[...]
> > systemd-timesyncd
[...] 
> > used to refuse to start, whenever other NTP clients (such as chrony)
> > were used.
[...]
> > But, as soon as I issue:
> > 
> >   # service systemd-timesyncd start
> > 
> > chrony dies and systemd-timesyncd starts.
> 
> If you manually start systemd-timesyncd, then indeed chronyd is stopped

But then, this can happen whenever services are (re-)started, such as
at boot time or when "systemctl daemon-reexec" is issued.
Depending on the order for the various services, this could result in
having to manually restart chrony, just to stop systemd-timesyncd...

> 
> > I thought that systemd-timesyncd should refrain from starting and
> > leave chrony alone.
> 
> No, Conflicts work both ways.
> 
> Afaics, everything is working as expected, so closing this bug report.

Wait, let me clarify how I see it.

Some time ago, I just had to install chrony (and set it up) in
order to make it work, without systemd-timesyncd interfering.

Now, it seems that I will *also* have to manually issue the following
command:

  # systemctl --now mask systemd-timesyncd

before installing and configuring chrony.

Is this correct?

This looks like a regression.
Do you agree?
 


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpylUUBLPTPx.pgp
Description: PGP signature

Bug#902013: [PKG-Openstack-devel] Bug#902013: manila: Add manila-data binary package and init template

[Thomas Goirand]

On 06/21/2018 03:32 PM, Corey Bryant wrote:
> Package: manila
> Version: 1:6.0.0-2
> Severity: normal
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu cosmic ubuntu-patch
> 
> Dear Maintainer,
> 
> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * d/control, d/manila-data.init.in: Add manila-data binary package
> and init template.
> 
> 
> Thanks for considering the patch.

Hi Corey,

Thanks for this patch. Though a small nit-pick: next time, please remove
the definition of PATH, as it's done again later by openstack-pkg-tools.

I'll get to apply all the patches you sent, thanks again!

Cheers,

Thomas Goirand (zigo)

Bug#849400: debian-installer: LUKS on rootfs and boot

[Nathan Schulte]

This problem still persists, on DI Buster Alpha 2 and Alpha 3. Working
around this even as an expert is rather cumbersome; one has to play
with the various menu options, partially configuring disks/partitions
etc., to load the necessary cryptsetup components (and dependencies,
like awk for decrypt_derived script), and it cannot be completed via
the installer.

As the submitter notes, having /boot on an encrypted (LUKS) partition
_is_ supported by GRUB and the other softwares.  Simply making
"continue" not do the same as "go back," as was originally suggested,
would be a big improvement.  Without this, one has to setup with an
unencrypted /boot, and then use rescue mode or other knowledge to
encrypt /boot and finalize the setup.  I found no way to proceed to
install with /boot being encrypted.

--
Nate

Bug#902040: mew FTCBFS: configures for the build architecture

[Helmut Grohne]

Source: mew
Version: 1:6.8-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

mew fails to cross build from source, because it configures for the
build architecture. Normally, I'd suggest using dh_auto_configure, but
mew's ./configure doesn't like --runstatedir. So the attached patch opts
for adding the necessary --build and --host options manually to make mew
cross buildable. Please consider applying it.

Helmut
diff --minimal -Nru mew-6.8/debian/changelog mew-6.8/debian/changelog
--- mew-6.8/debian/changelog2018-06-07 14:01:59.0 +0200
+++ mew-6.8/debian/changelog2018-06-21 21:16:30.0 +0200
@@ -1,3 +1,10 @@
+mew (1:6.8-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 21 Jun 2018 21:16:30 +0200
+
 mew (1:6.8-1) unstable; urgency=medium
 
   * New upstream version 6.8
diff --minimal -Nru mew-6.8/debian/rules mew-6.8/debian/rules
--- mew-6.8/debian/rules2018-06-03 12:12:05.0 +0200
+++ mew-6.8/debian/rules2018-06-21 21:16:29.0 +0200
@@ -8,6 +8,8 @@
 PKGSNAME=mew
 CHG_SUFFIX=`test -f 00changes || ls -1 00changes.* | sed s/00changes// | sort 
-n -t . -k 2,2 -k 3 | tail -1`
 
+include /usr/share/dpkg/architecture.mk
+
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 dpkg_buildflags = DEB_BUILD_MAINT_OPTIONS=$(DEB_BUILD_MAINT_OPTIONS) 
dpkg-buildflags
 CFLAGS=$(shell $(dpkg_buildflags) --get CFLAGS)
@@ -16,7 +18,7 @@
 
 configure-stamp: configure
dh_testdir
-   CFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" 
./configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man
+   CFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" 
./configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man 
--build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE)
grep '^Package: ' debian/control | head -1 | sed -e "s/^Package: //g" > 
debian/PACKAGE
sed -e "s/@PACKAGE@/$(PACKAGE)/g" debian/README.Debian.in > 
debian/README.Debian
sed -e "s/@PACKAGE@/$(PACKAGE)/g" debian/dirs.in > debian/dirs

Bug#886969: Bug#886625: push-source should be usable no matter the state of the working tree

[Sean Whitton]

Hello,

On Sun, Apr 22 2018, Sean Whitton wrote:

> I thought of a case where a .dsc is not sufficient and one needs a
> .changes: services like .

I thought of one more case recently: uploading to security-master.  You
can't dgit push there yet, so you need an _source.changes.

This might be a reason to not remove but instead firmly deprecate
build-source, until one can dgit push to security-master.

However, I think it is fine to drop it.  Firstly, because `dgit build
-S` exists.  Secondly, I take it that the original purpose of the
[s]build* subcommands was as intermediate steps on the way to a dgit
push, and now the build-source intermediate step is not required.
Indeed, our manpages advise users to use dpkg-buildpackage directly when
producing binaries for testing.  The reason for limiting dgit
subcommands in this way is to restrict dgit's role to being the
bidirectional archive<>git gateway, not an all purpose Debian packaging
wrapper script like git-buildpackage is.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#902039: kate4: autopkgtest regularly times out

[Paul Gevers]

Source: kate4
Version: 4:4.14.3-4
User: debian...@lists.debian.org
Usertags: timeout

Dear maintainer,

Your package has an autopkgtest. Great. However, I noticed it sometimes
is on the list of slow tests (it takes more than an hour on the
ci.debian.net infrastructure, which is in principle fine as long as it
has a purpose). I took a quick look and noticed that the test regularly
times out (> 200 times in 2 years; after ~2:47 hours). This rather puts
unnecessary stress on the infrastructure. What is more, when you fix the
regression test to pass again under normal circumstances, if the
time-out issue isn't solved, this will make your test flaky.

Could you please investigate and prevent the test from timing out? In
the absence of a solution, I think you should rather disable the test,
as the last time it ran successfully was 2016-06-18. Fixing the test to
pass again would be very nice.

Thanks for considering.

Paul

PS: most recent test log with time out:
https://ci.debian.net/data/autopkgtest/unstable/amd64/k/kate4/487150/log.gz



signature.asc
Description: OpenPGP digital signature