Bug#925035: put kzonecheck into knot-dnsutils?

[Daniel Baumann]

tag 925035 + patch
thanks

Hi,

here's a patch for this:

https://git.progress-linux.org/distributions/engywuck/packages/knot/commit/?id=3522350fbb2fde22021ff0438a0c4160d7ab3a1f

Regards,
Daniel

Bug#925586: FTBFS: Could not find xml-apis:xml-apis:debian

[Jongmin Kim]

Package: android-sdk-helper
Version: 0.1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source



Hi,

android-sdk-helper FTBFS on sid/amd64.

Adding the 'libjaxp1.3' to Build-Depends makes build successfully. I did
make a simple patch, but I'm not sure the target:

  1. Build-Depends of 'android-sdk-helper' or
  2. Depends of 'libgradle-core-java'.

The patch[1] adds 'libjaxp1.3' to Build-Depends of this
package(android-sdk-helper), and the package builds successfully.

Thank you!



-- [1] Patch:

--- a/debian/control
+++ b/debian/control
@@ -6,7 +6,8 @@ Uploaders: Kai-Chung Yan 
 Build-Depends: debhelper (>= 10~),
default-jdk-headless (>= 2:1.8) | default-jdk (>= 2:1.8),
gradle-debian-helper,
-   maven-repo-helper
+   maven-repo-helper,
+   libjaxp1.3-java
 Standards-Version: 3.9.8
 Vcs-Browser: 
https://anonscm.debian.org/cgit/android-tools/android-sdk-helper.git
 Vcs-Git: https://anonscm.debian.org/git/android-tools/android-sdk-helper.git



-- Full build log with sbuild:

+--+
| Build environment|
+--+

Kernel: Linux 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) amd64 (x86_64)
Toolchain package versions: binutils_2.31.1-16 dpkg-dev_1.19.6 g++-8_8.3.0-4 
gcc-8_8.3.0-4 libc6-dev_2.28-8 libstdc++-8-dev_8.3.0-4 libstdc++6_8.3.0-4 
linux-libc-dev_4.19.28-2
Package versions: adduser_3.118 ant_1.10.5-2 ant-optional_1.10.5-2 
antlr_2.7.7+dfsg-9.2 apt_1.8.0 autoconf_2.69-11 automake_1:1.16.1-4 
autopoint_0.19.8.1-9 autotools-dev_20180224.1 base-files_10.1 
base-passwd_3.5.46 bash_5.0-2 binutils_2.31.1-16 binutils-common_2.31.1-16 
binutils-x86-64-linux-gnu_2.31.1-16 bnd_3.5.0-4 bsdmainutils_11.1.2+b1 
bsdutils_1:2.33.1-0.1 build-essential_12.6 bzip2_1.0.6-9 
ca-certificates_20190110 ca-certificates-java_20190214 ccache_3.6-1 
coreutils_8.30-3 cpp_4:8.3.0-1 cpp-8_8.3.0-4 dash_0.5.10.2-5 debconf_1.5.71 
debhelper_12.1.1 debian-archive-keyring_2018.1 debianutils_4.8.6.1 
default-jdk-headless_2:1.11-71 default-jre-headless_2:1.11-71 dh-autoreconf_19 
dh-strip-nondeterminism_1.1.2-1 diffutils_1:3.7-2 dirmngr_2.2.13-1 dpkg_1.19.6 
dpkg-dev_1.19.6 dwz_0.12-3 e2fsprogs_1.45.0-1 eatmydata_105-7 fakeroot_1.23-1 
fdisk_2.33.1-0.1 file_1:5.35-4 findutils_4.6.0+git+20190209-2 
fontconfig-config_2.13.1-2 fonts-dejavu-core_2.37-1 g++_4:8.3.0-1 g++-8_8.3.0-4 
gcc_4:8.3.0-1 gcc-8_8.3.0-4 gcc-8-base_8.3.0-4 gettext_0.19.8.1-9 
gettext-base_0.19.8.1-9 gnupg_2.2.13-1 gnupg-l10n_2.2.13-1 gnupg-utils_2.2.13-1 
gpg_2.2.13-1 gpg-agent_2.2.13-1 gpg-wks-client_2.2.13-1 gpg-wks-server_2.2.13-1 
gpgconf_2.2.13-1 gpgsm_2.2.13-1 gpgv_2.2.13-1 gradle_4.4.1-5 
gradle-debian-helper_2.0.2 grep_3.3-1 groff-base_1.22.4-3 groovy_2.4.16-2 
gzip_1.9-3 hostname_3.21 init-system-helpers_1.56+nmu1 
intltool-debian_0.35.0+20060710.5 ivy_2.4.0-5 java-common_0.71 
java-wrappers_0.3 junit4_4.12-8 libacl1_2.2.53-4 libantlr-java_2.7.7+dfsg-9.2 
libaopalliance-java_20070526-6 libapache-pom-java_18-1 libapt-pkg5.0_1.8.0 
libarchive-zip-perl_1.64-1 libasan5_8.3.0-4 libasm-java_7.0-1 
libasound2_1.1.8-1 libasound2-data_1.1.8-1 libassuan0_2.5.2-1 
libatinject-jsr330-api-java_1.0+ds1-5 libatomic1_8.3.0-4 libattr1_1:2.4.48-4 
libaudit-common_1:2.8.4-2 libaudit1_1:2.8.4-2 libavahi-client3_0.7-4+b1 
libavahi-common-data_0.7-4+b1 libavahi-common3_0.7-4+b1 libbcel-java_6.2-1 
libbcpg-java_1.60-1 libbcprov-java_1.60-1 libbinutils_2.31.1-16 
libblkid1_2.33.1-0.1 libbsd0_0.9.1-2 libbsf-java_1:2.4.0-8 libbsh-java_2.0b4-19 
libbz2-1.0_1.0.6-9 libc-bin_2.28-8 libc-dev-bin_2.28-8 libc6_2.28-8 
libc6-dev_2.28-8 libcap-ng0_0.7.9-2 libcc1-0_8.3.0-4 libcdi-api-java_1.2-2 
libcom-err2_1.45.0-1 libcommons-cli-java_1.4-1 libcommons-codec-java_1.11-1 
libcommons-collections3-java_3.2.2-2 libcommons-compress-java_1.18-2 
libcommons-io-java_2.6-2 libcommons-lang-java_2.6-8 libcommons-lang3-java_3.8-2 
libcommons-logging-java_1.2-2 libcommons-parent-java_43-1 libcroco3_0.6.12-3 
libcups2_2.2.10-4 libdb5.3_5.3.28+dfsg1-0.6 libdbus-1-3_1.12.12-1 
libdd-plist-java_1.20-1 libdebconfclient0_0.249 libdom4j-java_2.1.1-2 
libdpkg-perl_1.19.6 libeatmydata1_105-7 libel-api-java_3.0.0-2 libelf1_0.176-1 
libexpat1_2.2.6-1 libext2fs2_1.45.0-1 libfakeroot_1.23-1 libfdisk1_2.33.1-0.1 
libfelix-framework-java_4.6.1-2 libfelix-gogo-runtime-java_0.16.2-1 
libfelix-resolver-java_1.14.0-1 libffi6_3.2.1-9 
libfile-stripnondeterminism-perl_1.1.2-1 libfindbugs-java_3.1.0~preview2-3 
libfontconfig1_2.13.1-2 libfreetype6_2.9.1-3 libgcc-8-dev_8.3.0-4 
libgcc1_1:8.3.0-4 libgcrypt20_1.8.4-5 libgdbm-compat4_1.18.1-4 
libgdbm6_1.18.1-4 libgeronimo-annotation-1.3-spec-java_1.0-1 
libgeronimo-interceptor-3.0-spec-java_1.0.1-4 libglib2.0-0_2.58.3-1 
libgmp10_2:6.1.2+dfsg-4 libgnutls30_3.6.6-3 libgomp1_8.3.0-4 

Bug#917536: debian-archive-keyring: release key for buster

[Jonathan Wiltshire]

On Fri, Dec 28, 2018 at 11:49:01AM +0100, Niels Thykier wrote:
> We need a new release signing key for buster so we can include it in a
> debian-archive-keyring upload before the buster release.

Release key exists, but no point adding it to d-a-k until we have an
archive key as well.



-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

Bug#925595: unblock: flatpak/1.2.4-1 (pre-approval) or 1.2.3-2 (unblock)

[Simon McVittie]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

I would like to follow the 1.2.x stable-branch of flatpak in buster for
as long as it's maintained upstream, similar to what I did with 0.8.x
in stretch. Are the release team happy with this in principle?

In the short term, this means uploading flatpak 1.2.4 to unstable. It
fixes CVE-2019-10063 (incomplete defence against command injection with
TIOCSTI) and some non-security bugs. I attach a proposed diff: may I
upload this if my tests are successful?

If 1.2.4 is not acceptable, please unblock 1.2.3-2 instead, to fix
CVE-2019-10063 but not the non-security bugs (I already uploaded that
version). I've attached the debdiff for that too.

See also #925569, the corresponding stable-update.

Thanks,
smcv
Filtered through
filterdiff -p1 -x doc/reference/html/'**' -x aclocal.m4 -x 'po/*.po' -x 'po/*.pot' -x configure:
 NEWS|   19 +++
 app/flatpak-builtins-list.c |2 +-
 app/flatpak-cli-transaction.c   |2 +-
 common/flatpak-context.c|5 +++--
 common/flatpak-dir.c|3 +--
 common/flatpak-run.c|   30 ++
 common/flatpak-utils-private.h  |4 
 common/flatpak-utils.c  |8 
 common/flatpak-version-macros.h |2 +-
 configure.ac|2 +-
 debian/changelog|   24 +++-
 po/cs.gmo   |binary
 po/de.gmo   |binary
 po/es.gmo   |binary
 po/gl.gmo   |binary
 po/hu.gmo   |binary
 po/id.gmo   |binary
 po/pl.gmo   |binary
 po/pt_BR.gmo|binary
 po/ru.gmo   |binary
 po/sk.gmo   |binary
 po/sv.gmo   |binary
 po/tr.gmo   |binary
 po/uk.gmo   |binary
 po/zh_TW.gmo|binary
 tests/package_version.txt   |2 +-
 26 files changed, 85 insertions(+), 18 deletions(-)

Original/unfiltered diffstat:
 NEWS|  19 
 aclocal.m4  | 194 
 app/flatpak-builtins-list.c |   2 +-
 app/flatpak-cli-transaction.c   |   2 +-
 common/flatpak-context.c|   5 +-
 common/flatpak-dir.c|   3 +-
 common/flatpak-run.c|  30 +++--
 common/flatpak-utils-private.h  |   4 +
 common/flatpak-utils.c  |   8 ++
 common/flatpak-version-macros.h |   2 +-
 configure   |  26 ++---
 configure.ac|   2 +-
 debian/changelog|  24 +++-
 doc/reference/html/FlatpakBundleRef.html|   4 +-
 doc/reference/html/FlatpakInstallation.html |   4 +-
 doc/reference/html/FlatpakInstalledRef.html |  60 +-
 doc/reference/html/FlatpakInstance.html |   4 +-
 doc/reference/html/FlatpakRef.html  |   4 +-
 doc/reference/html/FlatpakRelatedRef.html   |   4 +-
 doc/reference/html/FlatpakRemote.html   |   6 +-
 doc/reference/html/FlatpakRemoteRef.html|   4 +-
 doc/reference/html/FlatpakTransaction.html  |   4 +-
 doc/reference/html/FlatpakTransactionOperation.html |   4 +-
 doc/reference/html/FlatpakTransactionProgress.html  |   4 +-
 doc/reference/html/annotation-glossary.html |   4 +-
 doc/reference/html/api-index-full.html  |  20 +++-
 doc/reference/html/ch01.html|   4 +-
 doc/reference/html/flatpak-Error-codes.html |   4 +-
 doc/reference/html/flatpak-Version-information.html |   6 +-
 doc/reference/html/flatpak.devhelp2 |   4 +
 doc/reference/html/index.html   |   6 +-
 doc/reference/html/object-tree.html |   4 +-
 po/cs.gmo   | Bin 76830 -> 76885 bytes
 po/cs.po| 339 
 po/de.gmo   | Bin 41316 -> 41316 bytes
 po/de.po| 337 ---
 po/es.gmo   | Bin 39897 -> 39897 bytes
 po/es.po| 337 ---
 po/flatpak.pot  | 339 
 po/gl.gmo   | Bin 39989 -> 39989 

Bug#925596: irssi-plugin-xmpp: ABI mismatch with irssi 1.2.0-2

[Daniel Kahn Gillmor]

Package: irssi-plugin-xmpp
Version: 0.54-2.1
Severity: grave
Justification: renders package unusable

I get the following warnings from irssi when trying to use it with
irssi-plugin-xmpp:

10:49 -!- Irssi: xmpp/core is ABI version 13 but Irssi is version 20, 
cannot 
  load
10:49 -!- Irssi: Error loading module xmpp/fe: 
  /usr/lib/x86_64-linux-gnu/irssi/modules/libfe_xmpp.so: undefined 
  symbol: xmpp_subscription
10:49 -!- Irssi: xmpp/core is ABI version 13 but Irssi is version 20, 
cannot 
  load
10:49 -!- Irssi: Loaded module otr/core
10:49 -!- Irssi: Unknown chat protocol: XMPP

I think we need at least a re-build, but we should really use this
opportunity to take advantage of the exported ABI versioning irssi
packaging exposes now that https://bugs.debian.org/811445 is resolved.

The discussion on https://bugs.debian.org/772479 is probably relevant
here too.

I'll be taking a look at this, and will try to figure out a clean
rebuild.

  --dkg

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

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

Versions of packages irssi-plugin-xmpp depends on:
ii  irssi1.2.0-2
ii  libc62.28-8
ii  libglib2.0-0 2.58.3-1
ii  libloudmouth1-0  1.5.3-5

irssi-plugin-xmpp recommends no packages.

irssi-plugin-xmpp suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

[Andrej Shadura]

On Wed, 27 Mar 2019 12:01:40 +0100 Mattia Rizzolo  wrote:
> On Tue, Mar 26, 2019 at 04:35:41PM -0700, tony mancill wrote:
> > Are you sure about the upload of 4.3.22-2 changing the number of binary
> > packages built?  If that is the case, it was completely unintentional.
> 
> Meh, apparently nope, I was tricked by that dpkg change in the Binary
> field... I had only looked at the uploaded .changes, forgetting it
> doesn't list anymore all the produced binaries…
> 
> Sorry for inappropriately pointing at you.
> 
> So, this was instead caused by Andrej's -3 upload, that has
> 
> --- libspring-java-4.3.22/debian/rules  2019-03-04 05:35:23.0 +0100
> +++ libspring-java-4.3.22/debian/rules  2019-03-09 15:46:25.0 +0100
> @@ -5,15 +5,18 @@
> 
>  JAVA_HOME   := /usr/lib/jvm/default-java
> 
> -MODULES = aop beans context context-support core expression instrument jdbc 
> jms messaging orm oxm test tx web webmvc webmvc-portlet
> +# MODULES = aop beans context context-support core expression instrument 
> jdbc jms messaging orm oxm test tx web webmvc webmvc-portlet
> +MODULES = aop beans context context-support core expression instrument jdbc 
> orm oxm test tx web webmvc webmvc-portlet
> 
>  %:
> -   dh $@ --buildsystem=gradle
> +   dh $@ --buildsystem=gradle -Nlibspring-messaging-java 
> -Nlibspring-jms-java
> 
>  override_dh_auto_build:
> dh_auto_build -- jar -x test -x check \
>  -x :spring-orm-hibernate4:compileJava \
>  -x :spring-orm-hibernate5:compileJava \
> +-x :spring-jms:compileJava \
> +-x :spring-messaging:compileJava \
>  -x :spring-instrument-tomcat:compileJava \
>  -x :spring-webmvc-tiles2:compileJava \
>  -x :spring-websocket:compileJava
> 
> 
> (srly?  Using dh -N instead of removing the packages from d/control?!…).

Yes, so that it’s easier to bring them back when they’re unbroken.

> Anyway, this also wasn't mentioned in the changelog...

It was, indirectly:

  * Disable jasperreports support since it is RC-buggy.
  * Don’t build against libreactor-core-java since it depends on RC-
buggy openhft.


-- 
Cheers,
  Andrej

Bug#925599: don't hide information in the "action needed" section by default

[Matthias Klose]

Package: tracker.debian.org

looking at https://tracker.debian.org/pkg/ariba, all "action needed" items
expand to one or two items, and expanding the item doesn't show much more
information. But you have to click three more times to get this information.
Please can you show this information by default, and if it's too long, have a
"more" button, or something like the 1, 2, 3 buttons for the news?

Also, the area used for the "news" probably should be shrinked in favor of the
"action needed" area.

Bug#925559: unblock: netlib-java/0.9.3-5

[Andreas Tille]

Control: tags -1 - moreinfo

On Wed, Mar 27, 2019 at 06:32:00AM +, Niels Thykier wrote:
> > ++  URL url5 = new 
> > URL("file:///usr/share/java/jlapack-xerbla-0.8.jar");
> > ++  URL url6 = new 
> > URL("file:///build/netlib-java-0.9.3/build/classes/");
>^
> 
> Is this redundant or required for building the package.  If it is the
> latter, then sadly we cannot rely on the build-path to be stable, so we
> will need a better fix (e.g. sbuild and pbuilder does not agree on the
> paths AFAIR and even if they did, I would probably still prefer a better
> fix).

Since it turned out that I got an identical result by simply droping
that URL I just removed it.  Here is a full debdiff between the version
in testing and my latest upload (netlib-java_0.9.3-6):



diff -Nru netlib-java-0.9.3/debian/changelog netlib-java-0.9.3/debian/changelog
--- netlib-java-0.9.3/debian/changelog  2019-03-27 08:35:16.0 +0100
+++ netlib-java-0.9.3/debian/changelog  2019-01-13 21:11:05.0 +0100
@@ -1,16 +1,3 @@
-netlib-java (0.9.3-6) unstable; urgency=medium
-
-  * Drop /build/netlib-java-0.9.3 from URLs
-
- -- Andreas Tille   Wed, 27 Mar 2019 08:35:16 +0100
-
-netlib-java (0.9.3-5) unstable; urgency=medium
-
-  * Fix URLClassLoader
-Closes: #923759
-
- -- Andreas Tille   Tue, 26 Mar 2019 16:47:32 +0100
-
 netlib-java (0.9.3-4) unstable; urgency=medium
 
   * Deactivate watch file since in debian/README.source is declared that
diff -Nru netlib-java-0.9.3/debian/patches/add_compile_target.patch 
netlib-java-0.9.3/debian/patches/add_compile_target.patch
--- netlib-java-0.9.3/debian/patches/add_compile_target.patch   1970-01-01 
01:00:00.0 +0100
+++ netlib-java-0.9.3/debian/patches/add_compile_target.patch   2019-01-13 
21:11:05.0 +0100
@@ -0,0 +1,26 @@
+--- a/build.xml
 b/build.xml
+@@ -2,6 +2,7 @@
+ 
+   Builds, tests, and runs the project 
org.netlib.
+   
++  
+   
+   
+   
+@@ -23,6 +24,15 @@
+   
+   
+   
++
++
++
++
++
+   
+   
+   
diff -Nru netlib-java-0.9.3/debian/patches/series 
netlib-java-0.9.3/debian/patches/series
--- netlib-java-0.9.3/debian/patches/series 2019-03-27 08:35:16.0 
+0100
+++ netlib-java-0.9.3/debian/patches/series 2019-01-13 21:11:05.0 
+0100
@@ -1,2 +1,2 @@
 update_classpath.patch
-URLClassLoader.patch
+add_compile_target.patch
diff -Nru netlib-java-0.9.3/debian/patches/URLClassLoader.patch 
netlib-java-0.9.3/debian/patches/URLClassLoader.patch
--- netlib-java-0.9.3/debian/patches/URLClassLoader.patch   2019-03-27 
08:35:16.0 +0100
+++ netlib-java-0.9.3/debian/patches/URLClassLoader.patch   1970-01-01 
01:00:00.0 +0100
@@ -1,45 +0,0 @@
-From: Markus Koschany 
-Date: Mon, 25 Mar 2019 14:44:22 +0100
-Bug-Debian: https://bugs.debian.org/923759
-Subject: URLClassLoader
-

- src/org/netlib/generate/JavaGenerator.java | 14 --
- 1 file changed, 12 insertions(+), 2 deletions(-)
-
 a/src/org/netlib/generate/JavaGenerator.java
-+++ b/src/org/netlib/generate/JavaGenerator.java
-@@ -51,6 +51,8 @@ import org.netlib.util.doubleW;
- import org.netlib.util.floatW;
- import org.netlib.util.intW;
- 
-+import java.net.MalformedURLException;
-+
- /**
-  * Due to the depressing number of LAPACK routines, it is much more efficient 
to
-  * auto-generate the Java code for the wrapper and corresponding Java and JNI
-@@ -643,7 +645,8 @@ class JavaGenerator {
-* @return all classes in a given package
-* @see 
http://forum.java.sun.com/thread.jspa?threadID=757391=4326850
-*/
--  private List> getClasses(String packageName, IClassFilter 
filter) {
-+  private List> getClasses(String packageName, IClassFilter 
filter)
-+  throws MalformedURLException{
-   String packagePath = packageName.replace('.', '/');
- //ArrayList classpath = new ArrayList();
- //String[] classpathString = 
System.getProperty("java.class.path").split(":");
-@@ -658,7 +661,13 @@ class JavaGenerator {
- //log(Level.SEVERE, classpathString[i] + 
" " + ex.getMessage());
- //}
- //}
--  URL [] classpath = ((URLClassLoader) 
ClassLoader.getSystemClassLoader()).getURLs();
-+  URL url1 = new URL("file:///usr/share/java/junit-3.8.2.jar");
-+  URL url2 = new URL("file:///usr/share/java/f2jutil-0.8.1.jar");
-+  URL url3 = new 
URL("file:///usr/share/java/jlapack-blas-0.8.jar");
-+  URL url4 = new 
URL("file:///usr/share/java/jlapack-lapack-0.8.jar");
-+  URL url5 = new 
URL("file:///usr/share/java/jlapack-xerbla-0.8.jar");
-+
-+  URL [] classpath = { url1, url2, url3, url4, url5 };
-   List> result = new ArrayList>();
-   

Bug#925588: calibre sets ebook-edit as default editor for docx files

[Norbert Preining]

Hi Johannes

I agree with you and have been hit myself many times by the same "feature", but 
it has nothing to do with Calibre but with the "special" way how mailcap 
entries are handled in Debian.

Unfortunately at there moment it is "last one wins", which is suboptimal to say 
the least, but nobody stepped forward to work on improving the current system.

I recommend setting mailcap entries personally, as system wide one are 
completely unreliable.

I tend to close this but it reassign to mailcap/whatever package name is, but 
there are already quite a lot of reports to the same effect I guess.

WDYT?

Norbert


On March 27, 2019 5:23:25 PM GMT+09:00, Johannes 'josch' Schauer 
 wrote:
>Package: calibre
>Version: 3.39.1+dfsg-2
>Severity: important
>
>Hi,
>
>I'm unsure where the bug exactly is, so please reassign as necessary.
>
>Steps to reproduce:
>
>Before installing calibre:
>
>$ python3 -c 'import mailcap;
>print(mailcap.findmatch(mailcap.getcaps(),"application/vnd.openxmlformats-officedocument.wordprocessingml.document"))'
>("soffice --nologo --writer '/dev/null'", {'view': "soffice --nologo
>--writer '%s'", 'edit': "soffice --nologo --writer '%s'", 'test': 'test
>-n "$DISPLAY"', 'description': '"Office Open XML Document"',
>'nametemplate': '%s.docx', 'lineno': 651})
>
>After installing calibre:
>
>python3 -c 'import mailcap;
>print(mailcap.findmatch(mailcap.getcaps(),"application/vnd.openxmlformats-officedocument.wordprocessingml.document"))'
>('ebook-edit /dev/null', {'view': 'ebook-edit %s', 'test': 'test -n
>"$DISPLAY"', 'lineno': 86})
>
>It seems that installing calibre leaves my /etc/mailcap in a state that
>makes ebook-edit the default program for opening docx files. I assume
>you agree that is undesirable when libreoffice is also installed?
>
>Thanks!
>
>cheers, josch
>
>
>-- System Information:
>Debian Release: buster/sid
>  APT prefers testing
>APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
>'unstable')
>Architecture: amd64 (x86_64)
>Foreign Architectures: i386, armhf
>
>Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
>Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
>LANGUAGE=en_US:en (charmap=UTF-8)
>Shell: /bin/sh linked to /bin/dash
>Init: systemd (via /run/systemd/system)
>LSM: AppArmor: enabled
>
>Versions of packages calibre depends on:
>ii  calibre-bin  3.39.1+dfsg-2
>ii  fonts-liberation 1:1.07.4-7
>ii  imagemagick  8:6.9.10.23+dfsg-2
>ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.8+dfsg-1
>ii  libjpeg-turbo-progs  1:1.5.2-2+b1
>ii  libjs-coffeescript   1.12.8~dfsg-1
>ii  libjs-mathjax2.7.4+dfsg-1
>ii  optipng  0.7.7-1
>ii  poppler-utils0.63.0-2
>ii  python-apsw  3.16.2-r1-2+b2
>ii  python-chardet   3.0.4-1
>ii  python-cherrypy3 8.9.1-2
>ii  python-css-parser1.0.4-1
>ii  python-cssselect 1.0.3-1
>ii  python-cssutils  1.0.2-1
>ii  python-dateutil  2.6.1-1
>ii  python-dbus  1.2.8-2+b1
>ii  python-feedparser5.2.1-1
>ii  python-html5-parser  0.4.4-1+b1
>ii  python-html5lib  1.0.1-1
>ii  python-lxml  4.2.3-1
>ii  python-markdown  2.6.9-1
>ii  python-mechanize 1:0.2.5-3
>ii  python-msgpack   0.5.6-1+b1
>ii  python-netifaces 0.10.4-1+b1
>ii  python-pil   5.2.0-2
>ii  python-pkg-resources 39.2.0-1
>ii  python-pyparsing 2.2.0+dfsg1-2
>ii  python-pyqt5 5.11.3+dfsg-1+b3
>ii  python-pyqt5.qtsvg   5.11.3+dfsg-1+b3
>ii  python-pyqt5.qtwebkit5.11.3+dfsg-1+b3
>ii  python-regex 0.1.20180609-1+b1
>ii  python-routes2.4.1-1
>ii  python2.72.7.15-4
>ii  xdg-utils1.1.3-1
>
>Versions of packages calibre recommends:
>pn  python-dnspython  
>
>Versions of packages calibre suggests:
>pn  python-unrardll  
>
>-- debconf-show failed


--
PREINING Norbert http://www.preining.info
Accelia Inc. + JAIST + TeX Live + Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#925592: elpa-org: Fails to install, due to byte compile error

[Hilko Bengen]

Package: elpa-org
Version: 9.2.2+dfsg-1
Severity: grave

Dear Maintainer,

when upgrading org-mode from unstable today, it failed in postinst in
compiling the .el files. The full of a subsequent "dpkg --configure
--all" run is attached. It seems to me that the message...

,
| In toplevel form:
| ob-arduino.el:36:1:Error: Cannot open load file: No such file or directory, 
arduino-mode
`

... points to the cause.

Cheers,
-Hilko

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

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

Versions of packages elpa-org depends on:
ii  elpa-htmlize1.54-1
ii  emacsen-common  3.0.4

Versions of packages elpa-org recommends:
ii  emacs  1:26.1+1-3.2
ii  emacs-gtk [emacs]  1:26.1+1-3.2

Versions of packages elpa-org suggests:
ii  ditaa  0.10+ds1-1.2
ii  org-mode-doc   9.2.2-1
ii  texinfo6.5.0.dfsg.1-5
ii  texlive-fonts-recommended  2018.20190227-2
ii  texlive-latex-extra2018.20190227-1

-- no debconf information
Setting up elpa-org (9.2.2+dfsg-1) ...
tsort: -: input contains a loop:
tsort: elpa-htmlize
tsort: emacsen-common
Install elpa-htmlize for emacs
install/htmlize-1.54: Handling install of emacsen flavor emacs
install/htmlize-1.54: byte-compiling for emacs
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
Install elpa-org for emacs
install/org-9.2.2: Handling install of emacsen flavor emacs
install/org-9.2.2: byte-compiling for emacs

In toplevel form:
ob-arduino.el:36:1:Error: Cannot open load file: No such file or directory, 
arduino-mode

In ob-clojure-literate-auto-jackin:
ob-clojure-literate.el:127:14:Warning: reference to free variable
‘cider-connections’
ob-clojure-literate.el:133:14:Warning: cider-jack-in called with 0 arguments,
but requires 1

In ob-clojure-literate-set-local-cider-connections:
ob-clojure-literate.el:141:53:Warning: reference to free variable
‘cider-connections’
ob-clojure-literate.el:146:27:Warning: assignment to free variable
‘cider-connections’

In ob-clojure-literate-support-graphics-result:
ob-clojure-literate.el:289:25:Warning: reference to free variable ‘info’

In ob-clojure-literate-enable:
ob-clojure-literate.el:309:25:Warning: reference to free variable
‘cider-connections’
ob-clojure-literate.el:311:54:Warning: reference to free variable
‘ob-clojure-literate-mode’

In ob-clojure-literate-disable:
ob-clojure-literate.el:325:52:Warning: reference to free variable
‘ob-clojure-literate-mode’

In org-babel-variable-assignments:julia:
ob-julia.el:141:8:Warning: ‘org-number-sequence’ is an obsolete function (as
of Org 9.0); use ‘number-sequence’ instead.

In org-babel-prep-session:mathematica:
ob-mathematica.el:69:8:Warning: function org-babel-prep-session:mathematica
used to take 2 arguments, now takes 3
ob-mathematica.el:69:8:Warning: function ‘org-babel-prep-session:mathematica’
defined multiple times in this file

In toplevel form:
ob-mathomatic.el:45:1:Warning: defcustom for ‘org-babel-mathomatic-command’
fails to specify type
ob-mathomatic.el:45:1:Warning: defcustom for ‘org-babel-mathomatic-command’
fails to specify type

In org-babel-oz-initiate-session:
ob-oz.el:274:19:Warning: reference to free variable ‘oz-compiler-buffer’

In end of data:
ob-oz.el:295:1:Warning: the following functions are not known to be defined:
run-oz, oz-send-string

In molecule-jump:
ob-smiles.el:28:47:Warning: reference to free variable ‘path’
ob-smiles.el:39:2:Warning: ‘org-add-link-type’ is an obsolete function (as of
Org 9.0); use ‘org-link-set-parameters’ instead.

In ob-spice-concat:
ob-spice.el:45:26:Warning: assignment to free variable ‘newtext’
ob-spice.el:46:27:Warning: reference to free variable ‘newtext’

In org-babel-expand-body:spice:
ob-spice.el:110:19:Warning: assignment to free variable ‘newbody’
ob-spice.el:53:19:Warning: assignment to free variable ‘bodylinelist’
ob-spice.el:53:19:Warning: reference to free variable ‘bodylinelist’
ob-spice.el:57:23:Warning: assignment to free variable ‘wordlist’
ob-spice.el:111:48:Warning: assignment to free variable ‘firstword’
ob-spice.el:111:48:Warning: reference to free variable ‘wordlist’
ob-spice.el:98:40:Warning: assignment to free variable ‘varname’
ob-spice.el:66:48:Warning: assignment to free variable ‘varindex’
ob-spice.el:66:31:Warning: reference to free variable ‘varindex’
ob-spice.el:81:26:Warning: reference to free variable ‘varname’
ob-spice.el:84:32:Warning: assignment to free variable ‘newword’
ob-spice.el:86:43:Warning: reference to free variable ‘newword’
ob-spice.el:110:35:Warning: 

Bug#925591: grub-install fails on raid1+efi setup

[Joerg Dorchain]

Package: grub2-common
Version: 2.02+dfsg1-13

# grub-install
Installing for x86_64-efi platform.
efibootmgr: option requires an argument -- 'd'
efibootmgr version 15
usage: efibootmgr [options]
-a | --active sets bootnum active
-A | --inactive   sets bootnum inactive
-b | --bootnum    modify Boot (hex)
-B | --delete-bootnum delete bootnum
-c | --create create new variable bootnum and add to bootorder
-C | --create-only  create new variable bootnum and do not add to bo
otorder
-D | --remove-dups  remove duplicate values from BootOrder
-d | --disk disk   (defaults to /dev/sda) containing loader
-r | --driver Operate on Driver variables, not Boot Variables.
-e | --edd [1|3|-1]   force EDD 1.0 or 3.0 creation variables, or guess
-E | --device num  EDD 1.0 device number (defaults to 0x80)
-g | --gptforce disk with invalid PMBR to be treated as GPT
-i | --iface name create a netboot entry for the named interface
-l | --loader name (defaults to "\EFI\debian\grub.efi")
-L | --label label Boot manager display label (defaults to "Linux")
-m | --mirror-below-4G t|f mirror memory below 4GB
-M | --mirror-above-4G X percentage memory to mirror above 4GB
-n | --bootnext    set BootNext to  (hex)
-N | --delete-bootnext delete BootNext
-o | --bootorder ,,,... explicitly set BootOrder (hex)
-O | --delete-bootorder delete BootOrder
-p | --part part(defaults to 1) containing loader
-q | --quietbe quiet
-t | --timeout seconds  set boot manager timeout waiting for user input.
-T | --delete-timeout   delete Timeout.
-u | --unicode | --UCS-2  handle extra args as UCS-2 (default is ASCII)
-v | --verbose  print additional information
-V | --version  return version and exit
-w | --write-signature  write unique sig to MBR if needed
-y | --sysprep  Operate on SysPrep variables, not Boot 
Variables.
-@ | --append-binary-args file  append extra args from file (use "-" 
for stdin) 
-h | --help show help/usage
grub-install: error: efibootmgr failed to register the boot entry: Operation 
not permitted.

This results in no efi boot variable set. The current workaround
is to  manually copy /boot/efi/EFI/debian/grubx64.efi to
/boot/efi/EFI/boot/bootx64.efi

# dpkg-query -W|grep grub
grub-common 2.02+dfsg1-13
grub-efi-amd64  2.02+dfsg1-13
grub-efi-amd64-bin  2.02+dfsg1-13
grub2-common2.02+dfsg1-13

# efibootmgr -v
BootCurrent: 0004
Timeout: 1 seconds
BootOrder: 0004,0006,0007,0005
Boot0004* UEFI OS   
HD(1,GPT,37db7f15-2cdd-4553-9185-6761a0208897,0x800,0x7d000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot0005* Hard DriveBBS(HD,,0x0)..GO..NOO.S.a.m.s.u.n.g. .S.S.D. 
.8.4.0. 
.S.e.r.i.e.s.>..Gd-.;.A..MQ..L.1.S.C.4.E.N.C.A.6.A.7.1.5.1. .Z. 
. . . BO..NOO.K.I.N.G.S.T.O.N. 
.S.V.3.0.0.S.3.7.A.1.2.0.G.>..Gd-.;.A..MQ..L.0.5.2.0.B.6.8.7.1.5.6.0.0.A.5.3.
 . . . BO..NOO.W.D.C. 
.W.D.6.0.E.F.R.X.-.6.8.L.0.B.N.1.>..Gd-.;.A..MQ..L. . . . .W. 
.-.D.X.W.1.2.5.D.3.8.Y.N.7.VBO
Boot0006* UEFI OS   
HD(1,GPT,b17fefc1-aee4-4936-99c6-595909b8cd80,0x800,0x7d000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot0007* UEFI OS   
HD(1,GPT,695948ea-ba98-4c56-98ee-55e5aa8fb9e4,0x800,0x7d000)/File(\EFI\BOOT\BOOTX64.EFI)

# lsblk 
NAME MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
loop0  7:00   1.2G  1 loop  /nfsexports/tftp/grml
sda8:00 111.8G  0 disk  
├─sda1 8:10   250M  0 part  
│ └─md19:10   250M  0 raid1 /boot/efi
└─sda2 8:20 111.6G  0 part  
  └─md09:00 111.5G  0 raid1 
├─redstar-root   253:00   704M  0 lvm   /
├─redstar-swap   253:10 8G  0 lvm   [SWAP]
├─redstar-usr253:5013G  0 lvm   /usr
├─redstar-var253:6025G  0 lvm   /var
├─redstar-tmp253:7030G  0 lvm   /tmp
└─redstar-mnt253:80 4M  0 lvm   /mnt
sdb8:16   0   5.5T  0 disk  
├─sdb1 8:17   0   250M  0 part  
│ └─md19:10   250M  0 raid1 /boot/efi
├─sdb2 8:18   0 111.6G  0 part  
│ └─md09:00 111.5G  0 raid1 
│   ├─redstar-root   253:00   704M  0 lvm   /
│   ├─redstar-swap   253:10 8G  0 lvm   [SWAP]
│   ├─redstar-usr253:5013G  0 lvm   /usr
│   ├─redstar-var253:6025G  0 lvm   /var
│   ├─redstar-tmp253:7030G  0 lvm   /tmp
│   └─redstar-mnt253:80 4M  0 lvm   /mnt
└─sdb3 8:19   0   5.4T  0 part  
  └─cryptpv  253:20   5.4T  0 crypt 
 

Bug#925593: multi-notifier: always shows the window on the leftmost monitor after hiding in tray

[Ivan Krylov]

The code to remember the window position is obviously there, but the
window position was not stored for some reason. After I manually edited
~/.claws-mail/clawsrc and set mainwin_x to 1280:

mainwin_x=1280
mainwin_y=0
mainwin_maximised=1
mainwin_fullscreen=0
mainwin_menubar=1
mainwin_width=1331
mainwin_height=749

The main window position and size was updated correctly.

-- 
Best regards,
Ivan

Bug#925578: Update Package: Arduino : 1.8.9

[Geert Stappers]

Control: severity normal

On Tue, Mar 26, 2019 at 09:15:36PM -0600, Brian Holaday wrote:


> I created a script for easier install.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923220#42
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923220#52


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#925478: restart action breaks with systemd (Again)

[Helmut Grohne]

On Tue, Mar 26, 2019 at 06:25:07PM +0100, PICCORO McKAY Lenz wrote:
> > Severity: grave 
> 
> Please use appropriate severity levels. `grave' is reserved for data
> loss, security holes are issues that make the package entirely unusable
> by anyone. Refer to https://www.debian.org/Bugs/Developer#severities for
> a more detailed explanation.
> 
> YES i setup some services and when users are acting on those.. data will lose!

This is for typical installations. You can configure most software in a
way that turns a normal bug into a data loss issue. Please apply common
sense.

>  * Please specify versions of the following components:
>* Debian release in use
> 
> jessie (and later i install strech to test)

I'm afraid that jessie is no longer supported. Even stretch won't be
updated for such an issue. You're on your own here. Sorry.

>  * How reliable is the problem? Does it happen every time you restart
>lighttpd?
> 
> nop! only after some time waqs passed
> and specially if some changes are made to configuration

You later indicated that you did not customize the configuration.

>  * In your log I marked the spot where lighttpd occurs in the process
>list. Notably, it lacks the -D flag, but the .service file supplies
>-D. Are you sure that this process is created by the .service file?
> 
> i use the command "service lighttpd restart" and seems in some cases
> if there are a init script wil be converted on the fly to the "great" systemd
> format!

If there is a .service file, the init script won't be used. If you
manage to use the init script anyway, this is not a bug in the lighttpd
package.

>  * Can you try reproducing the failure in a reduced setting (e.g. set up
>a VM with a bare minimal package set)?
> 
> that was a minimal install at VM
> was hapened since jessie.. in wheeze does not happened..

It's a bit surprising that nobody ever bothered to report a problem that
you categorize as grave for years. In any case, working with such old
releases will not move us forward. At this point, only buster and later
releases are relevant.

Please try reproducing the issue on a buster VM. If you do, please
document your steps in detail. Otherwise I will be unable to help you. I
still fail to reproduce the reported problem in any way.

In principle, stretch could still be fixed via a stable update. If you
want to go that route, please provide a patch.

I also failed to reproduce the issue on stretch. The present data
suggests that the issue only affects non-standard configurations of
jessie and stretch. In that case, I won't be working on a solution.

If you want to continue, I urge you to provide more details and avoid
self-contradictory statements.

I also issue a formal warning. Your polemic about init systems is not
welcome here.

Helmut

Bug#925568: Bug#925568: cnvkit: FTBFS: FileExistsError: [Errno 17] File exists: 'build/'

[Andreas Tille]

On Wed, Mar 27, 2019 at 09:10:39AM +0100, Olivier Sallou wrote:
> 
> > During a rebuild of all packages in buster (in a buster chroot, not a
> > sid chroot), your package failed to build on amd64.
> 
> I just did a try on buster.
> 
> It succeeded first time, not on a second rebuild (with same error).

I also was able to reproduce the error in a buster chroot (at first
try).  I was thinking whether --no-parallel might have helped as well
since this is a usual cause for non-predictable racing conditions.

I actually succeeded with


diff --git a/debian/rules b/debian/rules
index 66f96f8..8b15674 100755
--- a/debian/rules
+++ b/debian/rules
@@ -15,7 +15,7 @@ override_dh_auto_build:
  mv $${script} cnvkit-$${script%%.py}; \
done; \
fi
-   dh_auto_build
+   dh_auto_build --no-parallel
cd scripts && for script in cnvkit-*; do \
mv $${script} $${script##cnvkit-}.py; \
  done



 
> I fixed and tested on buster with new patch d/patches/controldir. Git is
> up-to-date and in UNRELEASED state.

Seems your fix goes more to the root of the issue so we should go
with this.
 
> As we are in freeze, should we ask release team to unblock transition
> and then push to unstable?

Yes, please do so.
 
> Though not a bug issue, bug could be forwarded upstream as it raises an
> error to use an existing dir.

Probably.
 
Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#861960: kmail fatal startup error "Invalid parent"

[Rik Mills]

On Thu, 07 Mar 2019 00:59:30 -0600 Nazar Zhuk  wrote:

> After the first time, KMail opens normally. I attempted the following to
> reproduce on subsequent launches but was not successful:
> 
> - stopped akonadi
> - deleted:
> ~/.cache
> ~/.config/akonadi*
> ~/.config/kmail*
> ~/.local/share/akonadi*
> ~/.local/share/kmail*
> 
> --
> Nazar

You also need to remove:

~/.config/specialmailcollectionsrc

to reproduce.

If that files exists with the default content, then there is no startup
crash.

Bug#907495: please ship the x11idle binary

[Sébastien Delafond]

On 27/03 09:26, Michal Politowski wrote:
> Actually I think there is no need to compile x11idle.  As the footnote
> https://orgmode.org/manual/Resolving-idle-time.html#DOCF82 says,
> Debian already provides xprintidle, which seems to work for me.
> 
> Maybe elpa-org could just suggest that package and change the default
> for org-clock-x11idle-program-name?

Hi Michal,

that's a good point, and sounds like an elegant way to solve this in
Debian. I'm pretty busy these days, so I won't have time to work on that
right now, but I'd happily accept a patch in the meantime :)

Cheers,

-- 
Seb

Bug#925589: reportbug: reporting bugs to gitlab

[Salman Mohammadi]

Package: reportbug
Version: 7.5.2
Severity: wishlist

Dear Maintainer,

It would be nice if we could add a feature to be able to optionally
report bugs to
gitlab instead of debbugs.

I would like to volunteer to work on this feature but I need to
familiarize myself first with reportbug
code.

considerations:
- Reporting a bug needs a username on salsa
- Extra dependencies that will be introduced: python3-gitlab



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

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

Versions of packages reportbug depends on:
ii apt 1.8.0
ii python3 3.7.2-1
ii python3-reportbug 7.5.2
ii sensible-utils 0.0.12

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn claws-mail 
pn debconf-utils 
pn debsums 
ii dlocate 1.07+nmu1
pn emacs24-bin-common | emacs25-bin-common 
ii exim4-daemon-light [mail-transport-agent] 4.92-2
ii file 1:5.35-4
ii gnupg 2.2.12-1
pn python3-urwid 
pn reportbug-gtk 
ii xdg-utils 1.1.3-1

Versions of packages python3-reportbug depends on:
ii apt 1.8.0
ii file 1:5.35-4
ii python3 3.7.2-1
ii python3-apt 1.8.4
ii python3-debian 0.1.34
ii python3-debianbts 2.8.2
ii python3-requests 2.21.0-1

python3-reportbug suggests no packages.

-- no debconf information

Bug#925568: Bug#925568: cnvkit: FTBFS: FileExistsError: [Errno 17] File exists: 'build/'

[Mattia Rizzolo]

On Wed, Mar 27, 2019 at 09:38:12AM +0100, Andreas Tille wrote:
> On Wed, Mar 27, 2019 at 09:10:39AM +0100, Olivier Sallou wrote:
> > As we are in freeze, should we ask release team to unblock transition
> > and then push to unstable?
> 
> Yes, please do so.

You can first push to unstable and then open an unblock request.  This
*is* a big issue, the bug is RC, and the package would be removed from
buster otherwise.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

[Mattia Rizzolo]

On Tue, Mar 26, 2019 at 04:35:41PM -0700, tony mancill wrote:
> Are you sure about the upload of 4.3.22-2 changing the number of binary
> packages built?  If that is the case, it was completely unintentional.

Meh, apparently nope, I was tricked by that dpkg change in the Binary
field... I had only looked at the uploaded .changes, forgetting it
doesn't list anymore all the produced binaries…

Sorry for inappropriately pointing at you.


So, this was instead caused by Andrej's -3 upload, that has

--- libspring-java-4.3.22/debian/rules  2019-03-04 05:35:23.0 +0100
+++ libspring-java-4.3.22/debian/rules  2019-03-09 15:46:25.0 +0100
@@ -5,15 +5,18 @@

 JAVA_HOME   := /usr/lib/jvm/default-java

-MODULES = aop beans context context-support core expression instrument jdbc 
jms messaging orm oxm test tx web webmvc webmvc-portlet
+# MODULES = aop beans context context-support core expression instrument jdbc 
jms messaging orm oxm test tx web webmvc webmvc-portlet
+MODULES = aop beans context context-support core expression instrument jdbc 
orm oxm test tx web webmvc webmvc-portlet

 %:
-   dh $@ --buildsystem=gradle
+   dh $@ --buildsystem=gradle -Nlibspring-messaging-java 
-Nlibspring-jms-java

 override_dh_auto_build:
dh_auto_build -- jar -x test -x check \
 -x :spring-orm-hibernate4:compileJava \
 -x :spring-orm-hibernate5:compileJava \
+-x :spring-jms:compileJava \
+-x :spring-messaging:compileJava \
 -x :spring-instrument-tomcat:compileJava \
 -x :spring-webmvc-tiles2:compileJava \
 -x :spring-websocket:compileJava


(srly?  Using dh -N instead of removing the packages from d/control?!…).


Anyway, this also wasn't mentioned in the changelog...


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#925600: apparmor-profiles-extra: adjust autopkgtests to also work on Ubuntu

[Jamie Strandboge]

Package: apparmor-profiles-extra
Version: 1.26
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch

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

  * debian/tests/control:
- try to pull in linux-image-generic for Ubuntu
- also limit Debian kernel to only amd64 and add skip-not-installable
  restriction

Thanks for considering the patch.


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

Kernel: Linux 5.0.0-7-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru apparmor-profiles-extra-1.26/debian/tests/control 
apparmor-profiles-extra-1.26ubuntu1/debian/tests/control
--- apparmor-profiles-extra-1.26/debian/tests/control   2019-02-25 
08:34:49.0 -0600
+++ apparmor-profiles-extra-1.26ubuntu1/debian/tests/control2019-03-26 
17:51:40.0 -0500
@@ -5,5 +5,5 @@
 # Dummy test so that changes to linux-image-amd64 trigger our other 
autopkgtests
 # on ci.debian.net
 Test-Command: /bin/true
-Depends: linux-image-amd64 [amd64]
-Restrictions: superficial
+Depends: linux-image-amd64 [amd64] | linux-image-generic [amd64]
+Restrictions: superficial, skip-not-installable

Bug#924891: glibc: FTBFS: /<>/build-tree/amd64-libc/conform/UNIX98/ndbm.h/scratch/ndbm.h-test.c:1:10: fatal error: ndbm.h: No such file or directory

[Florian Weimer]

* Lucas Nussbaum:

> On 26/03/19 at 23:10 +0100, Aurelien Jarno wrote:
>> On 2019-03-22 17:30, Florian Weimer wrote:
>> > > About the archive rebuild: The rebuild was done on EC2 VM instances from
>> > > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
>> > > failed build was retried once to eliminate random failures.
>> > 
>> > I believe the actual test failure is tst-pkey.
>> > 
>> > Presumably, this rebuild was performed on some Xeon SP CPU.  Do you
>> > know which model?  Do you have any information about the kernel and
>> > hypervisor used?
>> > 
>> > 32-bit protection key support has had issues from time to time.
>> 
>> Do you have some more details about the issue? Is it a glibc or a kernel
>> problem?
>> 
>> If we can't fix the issue easily on the libc side, I guess the way to
>> fix that is to XFAIL that test on 32-bit x86. 
>
> If that's useful, I can easily provide access to an AWS VM to debug this
> issue.

Oh, that would be quite helpful indeed.

Bug#925585: calendarserver: __init__() takes exactly 4 arguments - related to Bug 923230 - recordWithUID instead of recordWithShortName

[Dominik]

Package: calendarserver
Version: 9.2+dfsg-1
Severity: important

Dear Maintainer,

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

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

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


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

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

Versions of packages calendarserver depends on:
ii  adduser  3.115
ii  lsb-base 9.20161125
ii  memcached1.5.6-1
ii  python   2.7.13-2
ii  python-crypto2.6.1-9+b1
ii  python-dateutil  2.7.3-3
ii  python-kerberos  1.1.5-2+b2
ii  python-openssl   16.2.0-1
ii  python-pg80001.10.6-1
ii  python-psutil5.5.1-1
ii  python-pycalendar1:2.1~git20161130.0.e68e150-1
ii  python-service-identity  16.0.0-2
ii  python-setproctitle  1.1.10-1+b2
ii  python-sqlparse  0.2.2-1
ii  python-twext 1:0.1~git20161216.0.b90293c-1
ii  python-twisted   18.9.0-3
ii  python-twisted-core  18.9.0-3
ii  python-tz2018.9-1
ii  python-xattr 0.9.6-1
ii  python-zope.interface4.3.2-1+b2
ii  ssl-cert 1.0.39

Versions of packages calendarserver recommends:
ii  python-pam  0.4.2-13.2

calendarserver suggests no packages.

-- Configuration Files:
/etc/caldavd/caldavd.plist changed:


http://www.apple.com/DTDs/PropertyList-1.0.dtd;>

  


ServerHostName
calendarServer 

HTTPPort
8008


SSLPort
8443
EnableSSL

SSLMethod
TLSv1_2_METHOD

RedirectHTTPToHTTPS



BindAddresses

10.33.34.26
 


BindHTTPPorts



BindSSLPorts




ServerRoot
/var/lib/caldavd

DBType
postgres
DatabaseConnection

endpoint
unix:/var/run/postgresql
database
caldav
user
caldavd
password



DataRoot
/var/lib/caldavd

DocumentRoot
/var/spool/caldavd

ConfigRoot
/etc/caldavd

RunRoot
/var/run/caldavd

Aliases

  



UserQuota
104857600 

MaximumAttachmentSize
10485760 


MaxCollectionsPerHome
50


MaxResourcesPerCollection
1

MaxResourceSize
1048576 


MaxAttendeesPerInstance
100


MaxAllowedInstances
3000



DirectoryService

type
twistedcaldav.directory.nss.NssDirectoryService
params

 recordTypes
 
 users
 groups
 
realmName
example.eu

firstValidUid
1000

lastValidUid
350

groupPrefix
caldavd-

firstValidGid
1000

lastValidGid
350

mailDomain
example.eu

refreshIntervalThreshold
1200

 


AdminPrincipals

  


ReadPrincipals

  


EnableProxyPrincipals









ResourceService

  Enabled
  
  type
  xml
  params
  
xmlFile
/etc/caldavd/resources.xml
  


AugmentService

  type
  xml
  params
  
xmlFiles

  /etc/caldavd/augments.xml

  



EnableAnonymousReadRoot


EnableAnonymousReadNav


EnablePrincipalListings


EnableMonolithicCalendars


Authentication

  
  Basic
  
Enabled


AllowedOverWireUnencrypted

  
  
  Digest
  
Enabled

Algorithm
md5
Qop

  
  
  Kerberos
  
Enabled

ServicePrincipal
sambaDC
  



LogRoot
/var/log/caldavd

AccessLogFile
access.log
RotateAccessLog


ErrorLogFile
error.log

DefaultLogLevel
info 

PIDFile
caldavd.pid


SSLCertificate
/etc/ssl/certs/calendarServer.pem

SSLAuthorityChain


SSLPrivateKey
/etc/ssl/private/calendarServer.key

UserName
caldavd
GroupName
caldavd
ProcessType
Combined
MultiProcess

  ProcessCount
  0 


Notifications

  
  CoalesceSeconds
  3
  Services
  

Bug#925588: calibre sets ebook-edit as default editor for docx files

[Johannes Schauer]

Control: reassign -1 mime-support
Control: retitle -1 update-mime fails to order desktop entries with lower 
priority than /usr/lib/mime/packages

Hi Norbert,

Quoting Norbert Preining (2019-03-27 10:33:11)
> I agree with you and have been hit myself many times by the same "feature",
> but it has nothing to do with Calibre but with the "special" way how mailcap
> entries are handled in Debian.
> 
> Unfortunately at there moment it is "last one wins", which is suboptimal to
> say the least, but nobody stepped forward to work on improving the current
> system.

I'm a bit puzzled though because at the bottom of update-mime(8) it says:

   DESKTOP ENTRIES
   In  addition  to  the  abovementioned  mechanism update-mime also
   parses desktop entries in  /usr/share/applications/  to  generate
   mailcap  entries.  These  entries are given a lower priority than
   those in /usr/lib/mime/packages.

And as far as I can see, the calibre entry does not come from
/usr/lib/mime/packages but from
/usr/share/applications/calibre-ebook-edit.desktop so I had expected it to end
up with a lower priority than the entries from
/usr/lib/mime/packages/libreoffice-writer.

Retitling accordingly.

> I recommend setting mailcap entries personally, as system wide one are
> completely unreliable.

Ah I see. Thanks for explaining the current situation!

> I tend to close this but it reassign to mailcap/whatever package name is, but
> there are already quite a lot of reports to the same effect I guess.

Indeed calibre does not seem to be at fault so I reassigned this to
src:mime-support because that's where update-mime comes from. But I'm a bit
puzzled now because src:mime-support only has eight bugs of which none seem to
be related to this problem. Which reports were you talking about? Am I looking
at the wrong source package?

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#925588: calibre sets ebook-edit as default editor for docx files

[Norbert Preining]

> puzzled now because src:mime-support only has eight bugs of which none seem to
> be related to this problem. Which reports were you talking about? Am I looking

Hmmm, I faintly remember reporting the very same problem years ago, and
have seen it popping up again and again - so I thought ...

Best

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#925594: unblock: lib3mf/1.8.1+ds-3

[John Paul Adrian Glaubitz]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hello!

lib3mf_1.8.1+ds-3 contains an update to the symbols file which fixes
an FTBFS on amd64 (#924841) [1]. Since just a single symbol had to be
updated, the attached debdiff is very small.

lib3mf is necessary for OpenSCAD which is a popular CAD package widely
used for 3D printer modelling among other things, so we should make
sure the lib3mf package ships with Buster.

Thanks,
Adrian

> [1] https://bugs.debian.org/924841

unblock lib3mf/1.8.1+ds-3

-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, sparc64, m68k, sh4, ia64, x32, powerpcspe

Kernel: Linux 4.18.0-2-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
LSM: AppArmor: enabled
diff -Nru lib3mf-1.8.1+ds/debian/changelog lib3mf-1.8.1+ds/debian/changelog
--- lib3mf-1.8.1+ds/debian/changelog2019-01-20 18:42:40.0 +0100
+++ lib3mf-1.8.1+ds/debian/changelog2019-03-26 01:08:07.0 +0100
@@ -1,3 +1,9 @@
+lib3mf (1.8.1+ds-3) unstable; urgency=medium
+
+  * Update symbol file for amd64 (Closes: #924841)
+
+ -- Torsten Paul   Tue, 26 Mar 2019 01:08:07 +0100
+
 lib3mf (1.8.1+ds-2) unstable; urgency=medium
 
   * Update symbol file for hurd, kfreebsd, powerpc and ppc64
diff -Nru lib3mf-1.8.1+ds/debian/lib3mf1.symbols 
lib3mf-1.8.1+ds/debian/lib3mf1.symbols
--- lib3mf-1.8.1+ds/debian/lib3mf1.symbols  2019-01-20 18:42:40.0 
+0100
+++ lib3mf-1.8.1+ds/debian/lib3mf1.symbols  2019-03-26 00:53:53.0 
+0100
@@ -1,4 +1,4 @@
-# SymbolsHelper-Confirmed: 1.8.0 alpha amd64 arm64 armel armhf hppa hurd-i386 
i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k mips mips64el mipsel powerpc 
powerpcspe ppc64 ppc64el riscv64 s390x sh4 sparc64 x32
+# SymbolsHelper-Confirmed: 1.8.1 amd64
 lib3MF.so.1 lib3mf1 #MINVER#
 * Build-Depends-Package: lib3mf-dev
  _ZN10CCOMObjectIN3NMR14CCOMSliceStackEED0Ev@Base 1.8.0+ds
@@ -3495,7 +3495,7 @@
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_yESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base
 1.8.0+ds
  
(optional=templinst|arch=ia64)_ZNSt8_Rb_treeIjSt4pairIKjSt10shared_ptrIN3NMR14CModelResourceEEESt10_Select1stIS6_ESt4lessIjESaIS6_EE16_M_insert_uniqueIS0_IjS5_EEES0_ISt17_Rb_tree_iteratorIS6_EbEOT_@Base
 1.8.0
  
(arch=!ia64)_ZNSt8_Rb_treeIjSt4pairIKjSt10shared_ptrIN3NMR14CModelResourceEEESt10_Select1stIS6_ESt4lessIjESaIS6_EE17_M_emplace_uniqueIJS0_IjS5_S0_ISt17_Rb_tree_iteratorIS6_EbEDpOT_@Base
 1.8.0
- 
_ZNSt8_Rb_treeIjSt4pairIKjSt10shared_ptrIN3NMR14CModelResourceEEESt10_Select1stIS6_ESt4lessIjESaIS6_EE5eraseERS1_@Base
 1.8.0+ds
+#MISSING: 1.8.1# 
_ZNSt8_Rb_treeIjSt4pairIKjSt10shared_ptrIN3NMR14CModelResourceEEESt10_Select1stIS6_ESt4lessIjESaIS6_EE5eraseERS1_@Base
 1.8.0+ds
  
_ZNSt8_Rb_treeIjSt4pairIKjSt10shared_ptrIN3NMR14CModelResourceEEESt10_Select1stIS6_ESt4lessIjESaIS6_EE8_M_eraseEPSt13_Rb_tree_nodeIS6_E@Base
 1.8.0+ds
  
(optional=templinst|arch=ia64)_ZNSt8_Rb_treeIjSt4pairIKjSt10shared_ptrIN3NMR18CPackageResourceIDEEESt10_Select1stIS6_ESt4lessIjESaIS6_EE16_M_insert_uniqueIS0_IjS5_EEES0_ISt17_Rb_tree_iteratorIS6_EbEOT_@Base
 1.8.0
  
(arch=!ia64)_ZNSt8_Rb_treeIjSt4pairIKjSt10shared_ptrIN3NMR18CPackageResourceIDEEESt10_Select1stIS6_ESt4lessIjESaIS6_EE17_M_emplace_uniqueIJS0_IjS5_S0_ISt17_Rb_tree_iteratorIS6_EbEDpOT_@Base
 1.8.0

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

[Andrej Shadura]

On Tue, 26 Mar 2019 16:35:41 -0700 tony mancill  wrote:
> Regarding the OpenHFT, I tried to help the overall situation by
> uploading new versions to experimental several months back but as was
> discussed on the list (I'd have to find the link), was requested to
> hold-off on transitioning them into unstable.

I tried completing that work, but unfortunately I ran into a compiler
bug in openhft-chronicle-wire:

[INFO] Compiling 107 source files to
/tmp/openhft-chronicle-wire/openhft-chronicle-wire/target/classes
compiler message file broken: key=compiler.misc.msg.bug
arguments=11.0.2, {1}, {2}, {3}, {4}, {5}, {6}, {7}
java.lang.AssertionError: exception_index is not set
at jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.java:162)
at jdk.compiler/com.sun.tools.javac.util.Assert.check(Assert.java:95)
at
jdk.compiler/com.sun.tools.javac.code.TypeAnnotationPosition.getExceptionIndex(TypeAnnotationPosition.java:307)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writePosition(ClassWriter.java:908)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writeTypeAnnotation(ClassWriter.java:879)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writeTypeAnnotations(ClassWriter.java:793)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writeCode(ClassWriter.java:1352)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writeMethod(ClassWriter.java:1220)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writeMethods(ClassWriter.java:1715)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writeClassFile(ClassWriter.java:1825)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writeClass(ClassWriter.java:1741)
at
jdk.compiler/com.sun.tools.javac.main.JavaCompiler.genCode(JavaCompiler.java:757)
at
jdk.compiler/com.sun.tools.javac.main.JavaCompiler.generate(JavaCompiler.java:1635)
at
jdk.compiler/com.sun.tools.javac.main.JavaCompiler.generate(JavaCompiler.java:1603)
at
jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:973)
at
jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.lambda$doCall$0(JavacTaskImpl.java:104)
at
jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.handleExceptions(JavacTaskImpl.java:147)
at
jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:100)
at
jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:94)
at
org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126)
at
org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:176)
at
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1129)
at
org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:188)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:181)
at org.debian.maven.Wrapper.main(Wrapper.java:89)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at

Bug#925590: fai-client: remove "libfile-lchown-perl" dependency from fcopy

[Reiner Schulz]

Package: fai-client
Version: 5.3.6
Severity: wishlist

Dear Thomas,

   We like to update "fai-client" on our RHEL7 Servers to the latest version,  
but since 
   fai 5.3.5 there is a dependency to "libfile-lchown-perl", which is not 
available 
   on RHEL7, EPEL or CentOS7.
   
   Functions of "libfile-lchown-perl" are only used two times  in fcopy. (line 
377 and 379)
   
   Building File::lchown from CPAN and deploy to 400 Servers is not ISO/IEC 
27001 like.

   Please find another solution and remove lchown from fcopy.

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

Kernel: Linux 4.9.0-8-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/bash
Init: systemd (via /run/systemd/system)

Versions of packages fai-client depends on:
ii  debconf-utils1.5.61
ii  file 1:5.30-1+deb9u2
ii  iproute2 4.9.0-1+deb9u1
ii  libapt-pkg-perl  0.1.32
ii  libfile-lchown-perl  0.02-2+b2
ii  perl 5.24.1-3+deb9u5

Versions of packages fai-client recommends:
ii  libgraph-perl  1:0.96-2

Versions of packages fai-client suggests:
pn  logtail  

-- Configuration Files:
/etc/fai/fai.conf changed [not included]

-- no debconf information

Bug#925598: upgrade-reports: Successfull upgrading armel NAS box jessie -> stretch, bug stumbled over a known bug

[Alexander Reichle-Schmehl]

Package: upgrade-reports
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
Jessie got removed form the archive ;)
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Read the release notes and followed the steps described
   * What was the outcome of this action?
I now have strech installed, but had to change /bin/sh from bash
to dash
   * What outcome did you expect instead?
Having stretch installed independend of where /bin/sh points to


I just finished my last box from Jessie (with some backports
(dehydrated) and handpicked manual installed packages (e.g. restic)) to
stretch.

During the upgrade however I seem to have run into Bug #870430:
flash-kernel didn't found the dtb file for my device.

Changing the symlink as described via "dpkg-reconfigure dash" solved the
upgrade issue for me, so I'm fine now.

I can't remmeber to have set the default shell to bash myselfe, so
assume it is still the default shell?  Then I think this bu should be
fixed in stable, too.


Best regards and many thanks,
  Alexander


-- System Information:
Debian Release: 9.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv5tel)

Kernel: Linux 4.9.0-0.bpo.6-marvell
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#925597: slapd: slapo-constraint manpage pre-dates the advent of olc

[Christoph Biedl]

Package: slapd
Version: 2.4.47+dfsg-3
Severity: normal

Dear Maintainer,

the slapo-constraint(5) manpage still refers to /etc/ldap/slapd.conf for
configuration, a configuration method that has been abandoned ... many
years ago. It took hours of searching and eventually using strace to
confirm it's completely ignored.

So *please* update the documentation and the examples of usage. The
Administrator's Guide has something about this (12.4.2), and I had to
read the openldap sources to learn the appropriate keywords like
olcConstraintAttribute to find that one.

And while you're on it, it really shouldn't hurt to mention the
constraint module needs to be loaded before it's possible to use it.
This is mentioned in slapd.overlay(5), but that's another piece of
information you'd only find when you already know what you are looking
for.

Constraints still don't work for me, that's something for another day.

Christoph, who had hoped to pass the "setting up constraints" level in ten 
minutes


signature.asc
Description: PGP signature

Bug#925585: Acknowledgement (calendarserver: __init__() takes exactly 4 arguments - related to Bug 923230 - recordWithUID instead of recordWithShortName)

[Rahul Amaram]

I believe this error should be fixed once you install python-twext 
1:0.1~git20161216.0.b90293c-2. This version is currently available in 
unstable.


Could you check and confirm?

Thanks
Rahul.

On 27/03/19 1:38 PM, Dominik wrote:


Sorry I forgot to add the stack trace:

2019-03-27T08:53:13+0100 [caldav-0] [txweb2.server#info] OPTIONS 
/calendars/__uids__/F90C8AD5-6EC5-5153-A94B-9992EAAB8DE5/ HTTP/1.1
2019-03-27T08:53:13+0100 [caldav-0] [txweb2.server#critical] Exception 
rendering request: /calendars/__uids__/F90C8AD5-6EC5-5153-A94B-9992EAAB8DE5/ (1, 1)>

2019-03-27T08:53:13+0100 [caldav-0] Traceback (most recent call last):
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 
1418, in _inlineCallbacks

2019-03-27T08:53:13+0100 [caldav-0] result = g.send(result)
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/twext/who/aggregate.py", line 89, in 
_oneFromSubServices

2019-03-27T08:53:13+0100 [caldav-0] record = yield m(*args, **kwargs)
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 
1613, in unwindGenerator
2019-03-27T08:53:13+0100 [caldav-0] return 
_cancellableInlineCallbacks(gen)
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 
1529, in _cancellableInlineCallbacks

2019-03-27T08:53:13+0100 [caldav-0] _inlineCallbacks(None, g, status)
2019-03-27T08:53:13+0100 [caldav-0] ---  ---
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/twistedcaldav/directory/common.py", 
line 97, in locateChild
2019-03-27T08:53:13+0100 [caldav-0] record = yield 
self.directory.recordWithUID(name)
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/txdav/who/augment.py", line 182, in 
recordWithUID

2019-03-27T08:53:13+0100 [caldav-0] uid, timeoutSeconds=timeoutSeconds
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/twext/who/aggregate.py", line 89, in 
_oneFromSubServices

2019-03-27T08:53:13+0100 [caldav-0] record = yield m(*args, **kwargs)
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 
1418, in _inlineCallbacks

2019-03-27T08:53:13+0100 [caldav-0] result = g.send(result)
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/txdav/who/cache.py", line 636, in 
recordWithUID
2019-03-27T08:53:13+0100 [caldav-0] record, doQuery = 
self.lookupRecord(IndexType 
.uid, 
uid, "recordWithUID")
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/txdav/who/cache.py", line 597, in 
lookupRecord
2019-03-27T08:53:13+0100 [caldav-0] record = 
self._memcacher.memcacheGetRecord(memcachekey)
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/txdav/who/cache.py", line 211, in 
memcacheGetRecord
2019-03-27T08:53:13+0100 [caldav-0] return 
self.unpickleRecord(pickled) if pickled is not None else None
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/txdav/who/cache.py", line 158, in 
unpickleRecord
2019-03-27T08:53:13+0100 [caldav-0] return 
record_class(self._recordService, fields)
2019-03-27T08:53:13+0100 [caldav-0] exceptions.TypeError: __init__() 
takes exactly 4 arguments (3 given)

Bug#925509: netbeans: Netbeans not usable with java in Buster

[Markus Koschany]

Control: forcemerge 925509 925510
Control: severity -1 serious

Am 25.03.19 um 23:26 schrieb Wouter Wijsman:
[...]
> A java.lang.NoSuchMethodError exception has occurred.
> Please report this at 
> https://issues.apache.org/jira/projects/NETBEANS/issues,
> including a copy of your messages.log file as an attachment.
> The messages.log file is located in your
> /home/wouter/.netbeans/10.0/var/log folder.
> 
> The full log can be found here: https://pastebin.com/0wgJNt15
> 
> I hope that helps. I can provide more information if needed.

Hello and thanks for reporting!

java.lang.NoSuchMethodError:
com.sun.tools.javadoc.main.JavadocClassFinder: method
(Lcom/sun/tools/javac/util/Context;)V not found

This look like an incompatibility with Java 11.

Jaroslav and Jan, might this be related to nb-javac again? Here is the
full log.

https://pastebin.com/0wgJNt15

and the link to the full bug report.

https://bugs.debian.org/925509

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

[Andrej Shadura]

On Tue, 26 Mar 2019 15:27:38 +0100 Emmanuel Bourg 
wrote:> I think this was done to remove the openhft packages that are
> incompatible with Java 11. But maybe the affected Spring modules could
> be salvaged by disabling the code using openhft (if it's optional).

I’m not entirely sure it is possible. But maybe someone else is going to
have better luck removing openhft dependencies.

-- 
Cheers,
  Andrej

Bug#925587: unblock: znc/1.7.2-2

[Patrick Matthäi]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package znc

It fixes a security bug:


diff -Naur '--exclude=.svn' 1.7.2-1/debian/changelog 1.7.2-2/debian/changelog
--- 1.7.2-1/debian/changelog2019-01-28 10:58:47.648083837 +0100
+++ 1.7.2-2/debian/changelog2019-03-26 12:58:06.264919659 +0100
@@ -1,3 +1,11 @@
+znc (1.7.2-2) unstable; urgency=high
+
+  * Add upstream patch 01-CVE-2019-9917 to fix a crash on invalid encoding,
+which fixes CVE-2019-9917.
+Closes: #925285
+
+ -- Patrick Matthäi   Tue, 26 Mar 2019 12:46:42 +0100
+
 znc (1.7.2-1) unstable; urgency=medium

   * New upstream release.
diff -Naur '--exclude=.svn' 1.7.2-1/debian/patches/01-CVE-2019-9917.diff 
1.7.2-2/debian/patches/01-CVE-2019-9917.diff
--- 1.7.2-1/debian/patches/01-CVE-2019-9917.diff1970-01-01 
01:00:00.0 +0100
+++ 1.7.2-2/debian/patches/01-CVE-2019-9917.diff2019-03-26 
12:58:06.272919610 +0100
@@ -0,0 +1,108 @@
+# Don't crash if user specified invalid encoding.
+# References: CVE-2019-9917
+# Closes: #925285
+# URL: 
https://github.com/znc/znc/commit/64613bc8b6b4adf1e32231f9844d99cd512b8973
+
+diff -Naur znc-1.7.2.orig/modules/controlpanel.cpp 
znc-1.7.2/modules/controlpanel.cpp
+--- znc-1.7.2.orig/modules/controlpanel.cpp2019-01-27 10:20:05.0 
+0100
 znc-1.7.2/modules/controlpanel.cpp 2019-03-26 12:42:34.298707717 +0100
+@@ -495,7 +495,7 @@
+ #ifdef HAVE_ICU
+ else if (sVar == "clientencoding") {
+ pUser->SetClientEncoding(sValue);
+-PutModule("ClientEncoding = " + sValue);
++PutModule("ClientEncoding = " + pUser->GetClientEncoding());
+ }
+ #endif
+ else
+diff -Naur znc-1.7.2.orig/src/IRCNetwork.cpp znc-1.7.2/src/IRCNetwork.cpp
+--- znc-1.7.2.orig/src/IRCNetwork.cpp  2019-01-27 10:20:05.0 +0100
 znc-1.7.2/src/IRCNetwork.cpp   2019-03-26 12:42:34.302707692 +0100
+@@ -1482,9 +1482,9 @@
+ }
+
+ void CIRCNetwork::SetEncoding(const CString& s) {
+-m_sEncoding = s;
++m_sEncoding = CZNC::Get().FixupEncoding(s);
+ if (GetIRCSock()) {
+-GetIRCSock()->SetEncoding(s);
++GetIRCSock()->SetEncoding(m_sEncoding);
+ }
+ }
+
+diff -Naur znc-1.7.2.orig/src/User.cpp znc-1.7.2/src/User.cpp
+--- znc-1.7.2.orig/src/User.cpp2019-01-27 10:20:05.0 +0100
 znc-1.7.2/src/User.cpp 2019-03-26 12:42:34.302707692 +0100
+@@ -1253,9 +1253,9 @@
+ void CUser::SetDenySetBindHost(bool b) { m_bDenySetBindHost = b; }
+ void CUser::SetDefaultChanModes(const CString& s) { m_sDefaultChanModes = s; }
+ void CUser::SetClientEncoding(const CString& s) {
+-m_sClientEncoding = s;
++m_sClientEncoding = CZNC::Get().FixupEncoding(s);
+ for (CClient* pClient : GetAllClients()) {
+-pClient->SetEncoding(s);
++pClient->SetEncoding(m_sClientEncoding);
+ }
+ }
+ void CUser::SetQuitMsg(const CString& s) { m_sQuitMsg = s; }
+diff -Naur znc-1.7.2.orig/src/znc.cpp znc-1.7.2/src/znc.cpp
+--- znc-1.7.2.orig/src/znc.cpp 2019-01-27 10:20:05.0 +0100
 znc-1.7.2/src/znc.cpp  2019-03-26 12:42:34.302707692 +0100
+@@ -2092,18 +2092,36 @@
+ m_uiForceEncoding++;
+ #ifdef HAVE_ICU
+ for (Csock* pSock : GetManager()) {
+-if (pSock->GetEncoding().empty()) {
+-pSock->SetEncoding("UTF-8");
+-}
++pSock->SetEncoding(FixupEncoding(pSock->GetEncoding()));
+ }
+ #endif
+ }
+ void CZNC::UnforceEncoding() { m_uiForceEncoding--; }
+ bool CZNC::IsForcingEncoding() const { return m_uiForceEncoding; }
+ CString CZNC::FixupEncoding(const CString& sEncoding) const {
+-if (sEncoding.empty() && m_uiForceEncoding) {
++if (!m_uiForceEncoding) {
++return sEncoding;
++}
++if (sEncoding.empty()) {
+ return "UTF-8";
+ }
++const char* sRealEncoding = sEncoding.c_str();
++if (sEncoding[0] == '*' || sEncoding[0] == '^') {
++sRealEncoding++;
++}
++if (!*sRealEncoding) {
++return "UTF-8";
++}
++#ifdef HAVE_ICU
++UErrorCode e = U_ZERO_ERROR;
++UConverter* cnv = ucnv_open(sRealEncoding, );
++if (cnv) {
++ucnv_close(cnv);
++}
++if (U_FAILURE(e)) {
++return "UTF-8";
++}
++#endif
+ return sEncoding;
+ }
+
+diff -Naur znc-1.7.2.orig/test/integration/tests/scripting.cpp 
znc-1.7.2/test/integration/tests/scripting.cpp
+--- znc-1.7.2.orig/test/integration/tests/scripting.cpp2019-01-27 
10:20:05.0 +0100
 znc-1.7.2/test/integration/tests/scripting.cpp 2019-03-26 
12:42:34.302707692 +0100
+@@ -55,6 +55,13 @@
+ ircd.Write(":n!u@h PRIVMSG nick :Hi\xF0, github issue #1229");
+ // "replacement character"
+ client.ReadUntil("Hi\xEF\xBF\xBD, github issue");
++
++// Non-existing encoding
++client.Write("PRIVMSG *controlpanel :Set ClientEncoding $me Western");
++client.Write("JOIN #a\342");
++client.ReadUntil(
++

Bug#925588: calibre sets ebook-edit as default editor for docx files

[Johannes 'josch' Schauer]

Package: calibre
Version: 3.39.1+dfsg-2
Severity: important

Hi,

I'm unsure where the bug exactly is, so please reassign as necessary.

Steps to reproduce:

Before installing calibre:

$ python3 -c 'import mailcap; 
print(mailcap.findmatch(mailcap.getcaps(),"application/vnd.openxmlformats-officedocument.wordprocessingml.document"))'
("soffice --nologo --writer '/dev/null'", {'view': "soffice --nologo 
--writer '%s'", 'edit': "soffice --nologo --writer '%s'", 'test': 'test -n 
"$DISPLAY"', 'description': '"Office Open XML Document"', 'nametemplate': 
'%s.docx', 'lineno': 651})

After installing calibre:

python3 -c 'import mailcap; 
print(mailcap.findmatch(mailcap.getcaps(),"application/vnd.openxmlformats-officedocument.wordprocessingml.document"))'
('ebook-edit /dev/null', {'view': 'ebook-edit %s', 'test': 'test -n 
"$DISPLAY"', 'lineno': 86})

It seems that installing calibre leaves my /etc/mailcap in a state that
makes ebook-edit the default program for opening docx files. I assume
you agree that is undesirable when libreoffice is also installed?

Thanks!

cheers, josch


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

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

Versions of packages calibre depends on:
ii  calibre-bin  3.39.1+dfsg-2
ii  fonts-liberation 1:1.07.4-7
ii  imagemagick  8:6.9.10.23+dfsg-2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.8+dfsg-1
ii  libjpeg-turbo-progs  1:1.5.2-2+b1
ii  libjs-coffeescript   1.12.8~dfsg-1
ii  libjs-mathjax2.7.4+dfsg-1
ii  optipng  0.7.7-1
ii  poppler-utils0.63.0-2
ii  python-apsw  3.16.2-r1-2+b2
ii  python-chardet   3.0.4-1
ii  python-cherrypy3 8.9.1-2
ii  python-css-parser1.0.4-1
ii  python-cssselect 1.0.3-1
ii  python-cssutils  1.0.2-1
ii  python-dateutil  2.6.1-1
ii  python-dbus  1.2.8-2+b1
ii  python-feedparser5.2.1-1
ii  python-html5-parser  0.4.4-1+b1
ii  python-html5lib  1.0.1-1
ii  python-lxml  4.2.3-1
ii  python-markdown  2.6.9-1
ii  python-mechanize 1:0.2.5-3
ii  python-msgpack   0.5.6-1+b1
ii  python-netifaces 0.10.4-1+b1
ii  python-pil   5.2.0-2
ii  python-pkg-resources 39.2.0-1
ii  python-pyparsing 2.2.0+dfsg1-2
ii  python-pyqt5 5.11.3+dfsg-1+b3
ii  python-pyqt5.qtsvg   5.11.3+dfsg-1+b3
ii  python-pyqt5.qtwebkit5.11.3+dfsg-1+b3
ii  python-regex 0.1.20180609-1+b1
ii  python-routes2.4.1-1
ii  python2.72.7.15-4
ii  xdg-utils1.1.3-1

Versions of packages calibre recommends:
pn  python-dnspython  

Versions of packages calibre suggests:
pn  python-unrardll  

-- debconf-show failed

Bug#924937: libpq5: OpenSSL license contamination of GPL reverse-dependencies

[Christoph Berg]

Control: reassign -1 ftp.debian.org

Re: Ansgar Burchardt 2019-03-20 
<751a89074fcaa393f2cc26ff676e9e3434ecd706.ca...@43-1.org>
> the OpenSSL ./. GPL problem (if one sees it as a problem) is larger
> than just libpq5: just looking at a small sample of the direct rdeps of
> libssl1.1, one can find the following GPL-licensed programs linking it:
> 
>   cryptsetup, wesnoth, mydumper, mupdf, gatling, kopete
> 
> Also amanda-client, validns as they contain patches in d/patches
> licensed under the GPL.
> 
> There are probably lots more, especially when you start looking at
> libraries (and their whole dependency trees).
> 
> There is also cups which was reported to switch to Apache-2 which is
> also GPL-2-incompatible...  That has lots of rdeps too (including for
> example all GTK applications).
> 
> Fedora treats OpenSSL as a "system library"[1].  I would guess they
> might do the same for libcups too.
> 
> Ansgar
> 
>   [1] 
> https://fedoraproject.org/wiki/Licensing:FAQ#What.27s_the_deal_with_the_OpenSSL_license.3F

Reassigning to ftp-master to get an answer on if this is a problem for
Debian, or if we can invoke the system library exception, or other
resolutions.

Christoph

Bug#925593: multi-notifier: always shows the window on the leftmost monitor after hiding in tray

[Ivan Krylov]

Package: claws-mail-multi-notifier
Version: 3.14.1-3+b1
Severity: normal

Dear Maintainer,

After I have added a second monitor to my setup, I have noticed that when
I restore the Claws-Mail window from tray (as implemented by multi-notifier
plugin), it always pops up on the leftmost monitor.

Other windows are usually placed on the monitor where the mouse cursor is.
I am using Xfce 4.12; the monitor to the right is set as "primary".

Expected behaviour would be that Claws-Mail window is also created on the same
monitor where the mouse cursor is, or that it remembers its position and size.

Please tell me if there is any other information I could provide to help you
fix this.

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

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), 
LANGUAGE=ru_RU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages claws-mail-multi-notifier depends on:
ii  claws-mail   3.14.1-3+b1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u4
ii  libcairo21.14.8-1
ii  libcanberra-gtk0 0.30-3
ii  libcanberra0 0.30-3
ii  libdb5.3 5.3.28-12+deb9u1
ii  libetpan17   1.6-3
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libglib2.0-0 2.50.3-2
ii  libgnutls30  3.5.8-5+deb9u4
ii  libgtk2.0-0  2.24.31-2
ii  liblockfile1 1.14-1+b1
ii  libnotify4   0.7.7-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  libsasl2-2   2.1.27~101-g0780600+dfsg-3
ii  libx11-6 2:1.6.4-3+deb9u1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages claws-mail-multi-notifier recommends:
ii  notification-daemon  3.20.0-1+b1
ii  xfce4-notifyd [notification-daemon]  0.3.4-1

Versions of packages claws-mail-multi-notifier suggests:
pn  lcdproc
ii  libnotify-bin  0.7.7-2
pn  xosd-bin   

-- no debconf information

Bug#924261: python-certbot 0.28.0-1~deb9u2 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: python-certbot
Version: 0.28.0-1~deb9u2

Explanation: revert to debhelper compat 9, to ensure systemd timers are 
correctly started

Bug#698504: system-config-printer: permission problem

[Debaru]

Dear Maintainer,

Recently, I spent hours to understand why other users can't access to 
system-config-printer.
So, I will be very greatful if you could use Ubuntu solution 
(https://bugs.launchpad.net/ubuntu/+source/cups-pk-helper/+bug/934291
), which may not be perfect but it fix a problem open in 2013 that has not 
found an upstream solution since.

Thanks,

Best regards.

Bug#924891: glibc: FTBFS: /<>/build-tree/amd64-libc/conform/UNIX98/ndbm.h/scratch/ndbm.h-test.c:1:10: fatal error: ndbm.h: No such file or directory

[Lucas Nussbaum]

On 26/03/19 at 23:10 +0100, Aurelien Jarno wrote:
> On 2019-03-22 17:30, Florian Weimer wrote:
> > > About the archive rebuild: The rebuild was done on EC2 VM instances from
> > > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> > > failed build was retried once to eliminate random failures.
> > 
> > I believe the actual test failure is tst-pkey.
> > 
> > Presumably, this rebuild was performed on some Xeon SP CPU.  Do you
> > know which model?  Do you have any information about the kernel and
> > hypervisor used?
> > 
> > 32-bit protection key support has had issues from time to time.
> 
> Do you have some more details about the issue? Is it a glibc or a kernel
> problem?
> 
> If we can't fix the issue easily on the libc side, I guess the way to
> fix that is to XFAIL that test on 32-bit x86. 

If that's useful, I can easily provide access to an AWS VM to debug this
issue.

Lucas

Bug#925568: [Debian-med-packaging] Bug#925568: cnvkit: FTBFS: FileExistsError: [Errno 17] File exists: 'build/'

[Olivier Sallou]

On 3/26/19 9:46 PM, Lucas Nussbaum wrote:
> Source: cnvkit
> Version: 0.9.5-2
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20190325 qa-ftbfs
> Justification: FTBFS in buster on amd64
>
> Hi,
>
> During a rebuild of all packages in buster (in a buster chroot, not a
> sid chroot), your package failed to build on amd64.

I just did a try on buster.

It succeeded first time, not on a second rebuild (with same error).


I fixed and tested on buster with new patch d/patches/controldir. Git is
up-to-date and in UNRELEASED state.

As we are in freeze, should we ask release team to unblock transition
and then push to unstable?


Though not a bug issue, bug could be forwarded upstream as it raises an
error to use an existing dir.


Olivier



>
> Relevant part (hopefully):
>> make[2]: Entering directory '/<>/test'
>> python3 ../cnvkit.py import-picard picard/p2-5_5.targetcoverage.csv 
>> picard/p2-5_5.antitargetcoverage.csv picard/p2-9_5.targetcoverage.csv 
>> picard/p2-9_5.antitargetcoverage.csv picard/p2-20_5.targetcoverage.csv 
>> picard/p2-20_5.antitargetcoverage.csv -d build/
>> python3 ../cnvkit.py import-picard picard/p2-5_5.targetcoverage.csv -d build/
>> python3 ../cnvkit.py import-picard picard/p2-5_5.antitargetcoverage.csv -d 
>> build/
>> python3 ../cnvkit.py import-picard picard/p2-9_2.targetcoverage.csv -d build/
>> WARNING: Ambiguous gene name 'TERT|TERT Promoter'; using 'TERT Promoter'
>> WARNING: Ambiguous gene name 'TERT|TERT Promoter'; using 'TERT Promoter'
>> WARNING: Ambiguous gene name 'TERT|TERT Promoter'; using 'TERT Promoter'
>> Created directory build/
>> Traceback (most recent call last):
>>   File "../cnvkit.py", line 13, in 
>> args.func(args)
>>   File "/<>/cnvlib/commands.py", line 1368, in 
>> _cmd_import_picard
>> os.mkdir(args.output_dir)
>> FileExistsError: [Errno 17] File exists: 'build/'
>> Wrote build/p2-5_5.targetcoverage.cnn with 6646 regions
>> Wrote build/p2-9_2.targetcoverage.cnn with 6646 regions
>> make[2]: *** [Makefile:58: build/p2-5_5.targetcoverage.cnn] Error 1
> The full build log is available from:
>http://qa-logs.debian.net/2019/03/25/cnvkit_0.9.5-2_testing.log
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
>
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
Olivier Sallou
Univ Rennes, Inria, CNRS, IRISA
Irisa, Campus de Beaulieu
F-35042 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Bug#925585: Acknowledgement (calendarserver: __init__() takes exactly 4 arguments - related to Bug 923230 - recordWithUID instead of recordWithShortName)

[Dominik]

Sorry I forgot to add the stack trace:

2019-03-27T08:53:13+0100 [caldav-0] [txweb2.server#info] OPTIONS 
/calendars/__uids__/F90C8AD5-6EC5-5153-A94B-9992EAAB8DE5/ HTTP/1.1
2019-03-27T08:53:13+0100 [caldav-0] [txweb2.server#critical] Exception 
rendering request: /calendars/__uids__/F90C8AD5-6EC5-5153-A94B-9992EAAB8DE5/ (1, 1)>

2019-03-27T08:53:13+0100 [caldav-0] Traceback (most recent call last):
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1418, 
in _inlineCallbacks

2019-03-27T08:53:13+0100 [caldav-0] result = g.send(result)
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/twext/who/aggregate.py", line 89, in 
_oneFromSubServices

2019-03-27T08:53:13+0100 [caldav-0] record = yield m(*args, **kwargs)
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1613, 
in unwindGenerator

2019-03-27T08:53:13+0100 [caldav-0] return _cancellableInlineCallbacks(gen)
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1529, 
in _cancellableInlineCallbacks

2019-03-27T08:53:13+0100 [caldav-0] _inlineCallbacks(None, g, status)
2019-03-27T08:53:13+0100 [caldav-0] ---  ---
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/twistedcaldav/directory/common.py", 
line 97, in locateChild
2019-03-27T08:53:13+0100 [caldav-0] record = yield 
self.directory.recordWithUID(name)
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/txdav/who/augment.py", line 182, in 
recordWithUID

2019-03-27T08:53:13+0100 [caldav-0] uid, timeoutSeconds=timeoutSeconds
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/twext/who/aggregate.py", line 89, in 
_oneFromSubServices

2019-03-27T08:53:13+0100 [caldav-0] record = yield m(*args, **kwargs)
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1418, 
in _inlineCallbacks

2019-03-27T08:53:13+0100 [caldav-0] result = g.send(result)
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/txdav/who/cache.py", line 636, in 
recordWithUID
2019-03-27T08:53:13+0100 [caldav-0] record, doQuery = 
self.lookupRecord(IndexType 
.uid, 
uid, "recordWithUID")
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/txdav/who/cache.py", line 597, in 
lookupRecord
2019-03-27T08:53:13+0100 [caldav-0] record = 
self._memcacher.memcacheGetRecord(memcachekey)
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/txdav/who/cache.py", line 211, in 
memcacheGetRecord
2019-03-27T08:53:13+0100 [caldav-0] return self.unpickleRecord(pickled) 
if pickled is not None else None
2019-03-27T08:53:13+0100 [caldav-0] File 
"/usr/lib/python2.7/dist-packages/txdav/who/cache.py", line 158, in 
unpickleRecord
2019-03-27T08:53:13+0100 [caldav-0] return 
record_class(self._recordService, fields)
2019-03-27T08:53:13+0100 [caldav-0] exceptions.TypeError: __init__() 
takes exactly 4 arguments (3 given)

Bug#907495: please ship the x11idle binary

[Michal Politowski]

Package: elpa-org
Followup-For: Bug #907495

Actually I think there is no need to compile x11idle.
As the footnote https://orgmode.org/manual/Resolving-idle-time.html#DOCF82
says, Debian already provides xprintidle, which seems to work for me.

Maybe elpa-org could just suggest that package and change the default for
org-clock-x11idle-program-name?

-- 
Michał Politowski
Talking has been known to lead to communication if practiced carelessly.

Bug#925524: init-system-helpers: Please provide a stretch backport for debhelper 12~

[wferi]

On Tue, 26 Mar 2019 11:29:29 +0100 =?utf-8?q?Ferenc_W=C3=A1gner?= 
 wrote:
 
> Debhelper compat level 12 is stable and available in stretch-backports,
> but uses the --skip-systemd-native option of invoke-rc.d, thus adds
> init-system-helpers (>= 1.54~) to misc:Pre-Depends.  This is necessary
> to fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887904.
> However, the resulting pre-dependency can't be satisfied in stretch,
> making the resulting binaries of compat 12 packages uninstallable in
> stretch.  Could you please provide a stretch backport of a suitable
> init-system-helpers version to accompany debhelper 12~, or do you
> recommend some other solution to this problem?  (I suppose installing a
> newer version of init-system-helpers manually to a stretch system
> wouldn't break it, but it's rather inconvenient even if you confirm it.)

Hi Niels,

I'm not sure you noticed this report.  In any case, I'd be much
interested to hear your opinion concerning this issue.
-- 
Thanks,
Feri

Bug#833545: marked as done (Hexter - new upstream version)

[Olivier Humbert]

Thank you very much Ross.

--
Site web : https://librazik.tuxfamily.org/
Donation : https://liberapay.com/LibraZiK/
Diaspora : 
https://framasphere.org/people/8c184af0c9450134f6682a053625

Mastodon : https://mastodon.xyz/@LibraZiK

Bug#833520: marked as done (Hexter - French translation of the menu item)

[Olivier Humbert]

Thank you very much for my improvement's incorporation Ross.

--
Site web : https://librazik.tuxfamily.org/
Donation : https://liberapay.com/LibraZiK/
Diaspora : 
https://framasphere.org/people/8c184af0c9450134f6682a053625

Mastodon : https://mastodon.xyz/@LibraZiK

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

[Mattia Rizzolo]

On Wed, Mar 27, 2019 at 12:37:17PM +0100, Andrej Shadura wrote:
> > (srly?  Using dh -N instead of removing the packages from d/control?!…).
> 
> Yes, so that it’s easier to bring them back when they’re unbroken.

But that doesn't help anything.

You removed two packages because a dependency of them was RC buggy,
making other packages uninstallable because of this.

> > Anyway, this also wasn't mentioned in the changelog...
> 
> It was, indirectly:
> 
>   * Disable jasperreports support since it is RC-buggy.
>   * Don’t build against libreactor-core-java since it depends on RC-
> buggy openhft.

We are in freeze, changelogs are read by people who don't always know
what this thing is.  Reading that I would never suspect that binaries
packages have been removed; please try to be more explicit and lengthy
in your changelogs.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#922211:

[Armin Müller]

On Mon, 18 Feb 2019 16:23:19 - cas...@danwin1210.me wrote:
> Is libgdk-pixbuf2.0-0-bin installed?
>

are you sure? cause there is no Package with this name, but 
libgdk-pixbuf2.0-0 is allready installed.



--
Armin Müller
Müller Grundstücksverwaltungs GmbH & Co. KG
Hans-Böckler-Str. 63
55128 Mainz

Telefon: 06131 / 9 35 35 0
Fax: 06131 / 9 35 35 35

Persönlich haftende Gesellschafterin: MGV Müller Verwaltungs GmbH
Vertretungsberechtigter Geschäftsführer: Josef Müller

Registergericht: Mainz
Registernummer: HRA 2170

Steuernummer: 26/200/0201/0

Bug#925602: unblock: ruby-globalid/0.4.2-1

[Utkarsh Gupta]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Hey,

Please unblock package ruby-globalid.

Recently, there was a bug (#925178) reported against the package with
severity: important.
The package was in testing and the bug was reported on 20th March and was
resolved in the latest upload, which was on 24th March.
This also causes regression in the migration of rails' latest update.

Hence, request you to:

unblock ruby-globalid/0.4.2-1

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

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

Bug#925607: unblock: ruby-chromedriver-helper/2.1.0-7

[Utkarsh Gupta]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Hey,

Please unblock package ruby-chromedriver-helper.

There was a bug (#924125) reported against the package with severity:
serious.
The bug was reported on 9th March and was resolved in the lastest upload,
which was on 24th March.
The package had previously migrated to testing on 26th February 2019, until
an RC bug was reported against it.
Hence, requesting you to please unblock the same and let it be a part of
Buster, which it was going to :)


Best,
Utkarsh

unblock ruby-chromedriver-helper/2.1.0-7

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

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

Bug#923815: Acknowledgement (nvidia-legacy-340xx-kernel-dkms does not build against kernel 5.0 source)

[S. R. Wright]

As 4.20.x is going EOL,  it may be prudent to investigate this bug WRT 5.0.x

-- sRw

On 3/5/19 11:51 AM, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 923815: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923815.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
  Debian NVIDIA Maintainers 

If you wish to submit further information on this problem, please
send it to 923...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

Bug#923749: fannj: FTBFS in buster/sid

[Andreas Tille]

Hi,

as far as I understood the Debian Java team agreed that droping the
documentation is an appropriate way to deal with errors like this:

Creating destination directory: "debian/_jh_build.javadoc/api/"
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jre-headless/api/ are in 
named modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.


Do you have any recommendation what is the most simple way to do so for
this package to fit the freeze policy (for sure a fix for the issue
would be helpful as well).

Kind regards

   Andreas.

PS: Daniel, packages touching the topic of neural networks are also
maintained in Debian Science team.  You might like to consider
joining this team and maintain fannj there.  Maintaining this package
in Debian Java team is an alternative as well.  I'd strongly recommend
to do so to maintain the package in a repository on salsa.debian.org

-- 
http://fam-tille.de

Bug#925442: RFS: ibus-table-myanmar/0.1 [ITP][QA][NMU] -- ibus table myanmar keyboard sponsor maintainer request

[Ko Ko Ye`]

Thanks for your information.

Also I will try to fix!
day by day.

Sir Boyuan Yang and  Sir Osamu Aoki guideline is helpful for me.

https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html#name-version

Still learn to gbp


Thank you so much.

With best regards




On Tue, Mar 26, 2019 at 11:00 PM Osamu Aoki  wrote:

> Hi mentors,
>
> On Mon, Mar 25, 2019 at 10:30:38AM +0630, Ko Ko Ye` wrote:
> > Package: sponsorship-requests
>
> I and Boyuan Yang gave some feedback to Ko Ko Ye` on Debian Input Method
> Team .
>
> Although his work seems to serve interesting spectrum of ethnic groups
> which may be served less, the package quality is unfortunately
> substandard.  So this is not a simple sponsor but more of packaging the
> upstream source.
>
> I think he has made decent upstream data, but someone reAlly need to
> spend time with him to get this into shape for bullseye.
>
> Any volunteer?
>
> Regards,
>
> Osamu
>
>

-- 

with regards *Ko Ko Ye`*

+95 97989 22022
+95 94500 22022
+95 9731 47907
kokoye2...@gmail.com
kokoye2...@ubuntu.com

skype: kokoye2007
jitsi: kokoye2007

http://ubuntu-mm.net
http://wiki.ubuntu.com/kokoye2007
http://wiki.ubuntu.com/MyanmarTeam http://loco.ubuntu.com/teams/ubuntu-mm

Bug#925604: unblock: ruby-doorkeeper-openid-connect/1.5.5-1

[Utkarsh Gupta]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Hey,

Please unblock package ruby-doorkeeper-openid-connect.

There was a CVE bug (#924747) reported against the package with severity:
grave.
It was reported on 16th March and was resolved in the latest upload, which
was on 24th March.
Thus, requesting you to please unblock the same and let it be a part of
Buster, as was going to :)


Best,
Utkarsh

unblock ruby-doorkeeper-openid-connect/1.5.5-1

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

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

Bug#922343: python-sievelib: autopkgtest regression: No module named 'pkg_resources'

[Matthias Klose]

Control: severity -1 serious
Control: tags -1 + sid buster

this is a missing dependency in the binary package.

$ fgrep -r pkg_resources /usr/lib/python3/dist-packages/sievelib
/usr/lib/python3/dist-packages/sievelib/__init__.py:from pkg_resources import
get_distribution, DistributionNotFound

Bug#925334: vc4: CMA fills up and screen not updated anymore on raspi3

[Fabian Pietsch]

Package: src:linux
Version: 4.19.28-2
Followup-For: Bug #925334

Dear Maintainer,

the bug is still present in the current version. It took a freshly
booted, idle system 3304 seconds for the bug to occur, though,
so this time rather an hour (than 10-30min as stated before).

After the bug has happened, I get the following information from sysfs:

| root@rpi3:/sys/bus/platform/drivers/vc4_v3d# for I in enabled status 
active_time suspended_time; do echo -n "$I=$(cat 3fc0.v3d/power/runtime_$I) 
"; done; echo
| enabled=enabled status=error active_time=16800 suspended_time=55464216

And again:

| enabled=enabled status=error active_time=16800 suspended_time=55479160

So vc4_v3d which reported the error seems to be in status=error
and counts as suspended. Manual attempts to get it to resume again,
now that more cma is free again, failed, but there are probably ways
I don't know about.

"echo on > .../power/control" changed runtime_enabled=forbidden
(and echo auto > control changed it back to runtime_enabled=enabled),
but runtime_status remained at "error".

Regards, Fabian


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

Kernel: Linux 4.19.0-4-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#802539: Please properly configure HTTPS in security.debian.org

[Pedro Ribeiro]

Package: security.debian.org Followup-For: Bug #802539

Bug#925606: gitlab: Fail to upgrade (error with activesupport gem)

[Pirate Praveen]

On 2019, മാർച്ച് 27 7:31:42 PM IST, David L  wrote:
>Package: gitlab
>Version: 11.8.3-1+fto10+1
>Severity: important
>
>Hi,
>
>Doing an apt-get upgrade fails to install gitlab (upgrading from
>11.8.2).
>
>The error message are:
>
>Bundle complete! 187 Gemfile dependencies, 315 gems now installed.
>Gems in the groups development and test were not installed.
>Use `bundle info [gemname]` to see where a bundled gem is installed.
>Running final rake tasks and tweaks...
>gitlab_production database is not empty, skipping gitlab setup
>fatal: not a git repository (or any of the parent directories): .git
>fatal: not a git repository (or any of the parent directories): .git
>fatal: not a git repository (or any of the parent directories): .git
>fatal: not a git repository (or any of the parent directories): .git
>rake aborted!
>LoadError: cannot load such file -- sprockets/rails/context

I have seen this error and it took me a lot of time to troubleshoot it.

It should work if you remove ruby-bootanap.

We should add Breaks for ruby-bootsnap  
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#888704: xoscope has been compiled without alsa support

[Oswald Buddenhagen]

Package: xoscope
Version: 2.2-1+b1
Followup-For: Bug #888704

indeed, libasound2-dev needs to be added to Build-depends. things work
fine after this is done.

note that esd support is also not built in due to being utterly
obsolete. that's just fine, but i'd suggest to patch the man page
accordingly.

Bug#925608: fannj: New upstream version available

[Andreas Tille]

Package: fannj
Severity: minor

Hi,

the project seems to have moved from code.google.com to

   https://github.com/krenfro/fannj

and has tagged version 0.7.  Please upgrade after Buster release.

Kind regards

Andreas.


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

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

Bug#925609: unblock: rails/2:5.2.2.1+dfsg-1

[Utkarsh Gupta]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Hey,

Please unblock package rails.

There were 2 bugs (#924520 and #924521) reported against the package with
severity: grave and severity: important, respectively.
Both the bugs were reported on 13th March and were resolved in the latest
upload, which was on 19th March.
The package had previously migrated to testing until the two bugs were
reported against it.
Hence, requesting you to please unblock the same and let it be a part of
Buster, which it was going to :)

Note: This should be unblocked after/in/with reference to the unblock
request for ruby-globalid (#925602).


Best,
Utkarsh

unblock rails/2:5.2.2.1+dfsg-1

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

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

Bug#925601: unblock: debmake-doc/1.14-1

[Osamu Aoki]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package debmake-doc

(explain the reason for the unblock here)

 * Mostly translation updates
 * Stop using "expect" to avoid FTBFS

debmake-doc (1.14-1) unstable; urgency=high

  [ Boyuan Yang ]
  * po: Complete Simplified Chinese (zh_CN) translation.
  * po: More updates to German (de) translation.
  * */debian/copyright: Update source repository location for
debmake-doc.
  * Fixes several bugs in the document:
+ Fix url of Debian systemd packaging repository.
+ Fix several typos.

  [ Osamu Aoki ]
  * Remove expect use to avoid FTBFS on some build environment.

 -- Osamu Aoki   Wed, 27 Mar 2019 01:39:56 +0900

(include/attach the debdiff against the package in testing)

asciidoc and po directory are excluded since they are text content
debhello* directory are excluded since it is build log of packages used
for text content generation for the document.

diff -Nru --exclude asciidoc --exclude 'debhello*' --exclude po 
debmake-doc-1.13/debian/changelog debmake-doc-1.14/debian/changelog
--- debmake-doc-1.13/debian/changelog   2019-03-02 06:50:08.0 +0900
+++ debmake-doc-1.14/debian/changelog   2019-03-27 01:39:56.0 +0900
@@ -1,6 +1,22 @@
+debmake-doc (1.14-1) unstable; urgency=high
+
+  [ Boyuan Yang ]
+  * po: Complete Simplified Chinese (zh_CN) translation.
+  * po: More updates to German (de) translation.
+  * */debian/copyright: Update source repository location for
+debmake-doc.
+  * Fixes several bugs in the document:
++ Fix url of Debian systemd packaging repository.
++ Fix several typos.
+
+  [ Osamu Aoki ]
+  * Remove expect use to avoid FTBFS on some build environment. 
+
+ -- Osamu Aoki   Wed, 27 Mar 2019 01:39:56 +0900
+
 debmake-doc (1.13-1) unstable; urgency=high
 
-  * Team upload. 
+  * Team upload.
   * More translation updates.
   * Makefile.dbk: Workaround a known regression inside toolchain
 (itstool).
diff -Nru --exclude asciidoc --exclude 'debhello*' --exclude po 
debmake-doc-1.13/debian/control debmake-doc-1.14/debian/control
--- debmake-doc-1.13/debian/control 2019-03-02 06:50:08.0 +0900
+++ debmake-doc-1.14/debian/control 2019-03-27 01:39:56.0 +0900
@@ -14,7 +14,6 @@
dh-python,
docbook-xml,
docbook-xsl,
-   expect,
faketime,
fonts-arphic-bsmi00lp,
fonts-arphic-gbsn00lp,
diff -Nru --exclude asciidoc --exclude 'debhello*' --exclude po 
debmake-doc-1.13/debian/copyright debmake-doc-1.14/debian/copyright
--- debmake-doc-1.13/debian/copyright   2019-01-11 05:37:15.0 +0900
+++ debmake-doc-1.14/debian/copyright   2019-03-27 01:39:56.0 +0900
@@ -1,6 +1,6 @@
 Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: debmake-doc
-Source: https://anonscm.debian.org/cgit/collab-maint/debmake-doc.git/tree/
+Source: https://salsa.debian.org/debian/debmake-doc
 
 Files: *
 Copyright: 2015 Osamu Aoki 
diff -Nru --exclude asciidoc --exclude 'debhello*' --exclude po 
debmake-doc-1.13/debian/doc-base debmake-doc-1.14/debian/doc-base
--- debmake-doc-1.13/debian/doc-base2019-01-11 05:37:15.0 +0900
+++ debmake-doc-1.14/debian/doc-base1970-01-01 09:00:00.0 +0900
@@ -1,18 +0,0 @@
-Document: debmake-doc
-Title: Guide for Debian Maintainers
-Author: Osamu Aoki
-Abstract: This tutorial document describes the building of the Debian
- package to ordinary Debian users and prospective developers using
- the debmake command.
-Section: Debian
-
-Format: text
-Files: /usr/share/doc/debmake-doc/debmake-doc.en.txt.gz
-
-Format: PDF
-Files: /usr/share/doc/debmake-doc/debmake-doc.en.pdf
-
-Format: HTML
-Index: /usr/share/doc/debmake-doc/html/index.en.html
-Files: /usr/share/doc/debmake-doc/html/*.en.html
-
diff -Nru --exclude asciidoc --exclude 'debhello*' --exclude po 
debmake-doc-1.13/debian/doc-base.debmake-doc-de 
debmake-doc-1.14/debian/doc-base.debmake-doc-de
--- debmake-doc-1.13/debian/doc-base.debmake-doc-de 1970-01-01 
09:00:00.0 +0900
+++ debmake-doc-1.14/debian/doc-base.debmake-doc-de 2019-03-27 
01:39:56.0 +0900
@@ -0,0 +1,18 @@
+Document: debmake-doc-de
+Title: Guide for Debian Maintainers (German)
+Author: Osamu Aoki
+Abstract: This tutorial document describes the building of the Debian
+ package to ordinary Debian users and prospective developers using
+ the debmake command.
+Section: Debian
+
+Format: text
+Files: /usr/share/doc/debmake-doc/debmake-doc.de.txt.gz
+
+Format: PDF
+Files: /usr/share/doc/debmake-doc/debmake-doc.de.pdf
+
+Format: HTML
+Index: /usr/share/doc/debmake-doc/html/index.de.html
+Files: /usr/share/doc/debmake-doc/html/*.de.html
+
diff -Nru --exclude asciidoc --exclude 'debhello*' --exclude po 
debmake-doc-1.13/debian/doc-base.debmake-doc-en 
debmake-doc-1.14/debian/doc-base.debmake-doc-en

Bug#924513: this bug is the exact same as 924906

[Jon Hamill]

Dear maintainers,


I noticed the exact same bug description appears in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924906


Although my bug was requested 5 days earlier it seems that my bug was not given 
the same priority as 924906 - maybe because of my specificity about armhf 
architecture?


Please fold my bug (924513) into the more severe bug listing (924906) in the 
hopes of seeing the patch pulled in from upstream sooner.


Best,

-Jon

Bug#925597: [Pkg-openldap-devel] Bug#925597: slapd: slapo-constraint manpage pre-dates the advent of olc

[Ryan Tandy]

Control: tag -1 upstream

Hi Christoph,

I'm sorry to hear the documentation caused you some frustration here.

On Wed, Mar 27, 2019 at 12:17:18PM +0100, Christoph Biedl wrote:

the slapo-constraint(5) manpage still refers to /etc/ldap/slapd.conf for
configuration, a configuration method that has been abandoned ... many
years ago. It took hours of searching and eventually using strace to
confirm it's completely ignored.


Sort of. It's soft-deprecated but also still supported. But slapd runs 
in cn=config mode (-F) OR slapd.conf mode (-f) ... it sounds like you 
had slapd running in cn=config mode (Debian's default) but tried to add 
some configuration in a slapd.conf file, which indeed would be ignored.



So *please* update the documentation and the examples of usage.


ACK. There is not really an active documentation contributor upstream at 
the moment, and some documentation is still not updated for cn=config, 
as you found. So I'm sorry there is indeed a long tail of older bits and 
not much progress being made.


The Administrator's Guide has something about this (12.4.2), and I had 
to read the openldap sources to learn the appropriate keywords like 
olcConstraintAttribute to find that one.


Maybe too late to help you now, but you can introspect the schema on 
your running slapd instance by making searches under the 'cn=Subschema' 
base. This is the recommended way of finding, for example, what 
configuration classes/attributes are actually available on your specific 
instance.



And while you're on it, it really shouldn't hurt to mention the
constraint module needs to be loaded before it's possible to use it.
This is mentioned in slapd.overlay(5), but that's another piece of
information you'd only find when you already know what you are looking
for.


Others have asked for this before and upstream are resistant to repeat 
this information in every overlay's man page when it can just be 
written once in a central place. (Can you tell we're talking about 
programmers here?) But this bites enough new users and I do tend to 
agree we should have even a breadcrumb in each man page that lets people 
know what they should be looking for...


Better luck on your next try,

Ryan

Bug#925615: kernel-package: make-kpkg fails to build latest kernel

[Matteo Croce]

Package: kernel-package
Version: 13.018+nmu1
Severity: important

Dear Maintainer,

Since kernel commit 3812b8c5c5d5 ("kbuild: make -r/-R effective in top Makefile
for old Make versions") make-kpkg is unable to build a kernel because the
VERSION variable is not valorized in debian/ruleset/misc/version_vars.mk.

While at it, can you please quote all the $(VERSION) occourrences?
This will produce more meaningful error messages than:
/bin/sh: 1: [: -lt: unexpected operator
/bin/sh: 1: [: -eq: unexpected operator
/bin/sh: 1: [: -eq: unexpected operator
/bin/sh: 1: [: -gt: unexpected operator
/bin/sh: 1: [: -ge: unexpected operator
/bin/sh: 1: [: -lt: unexpected operator
/bin/sh: 1: [: -eq: unexpected operator
/bin/sh: 1: [: -eq: unexpected operator

Cfr. https://git.kernel.org/linus/3812b8c5c5d5

Regards,
Matteo Croce
per aspera ad upstream

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic-updates
  APT policy: (500, 'cosmic-updates'), (500, 'cosmic-security'), (500, 'cosmic')
Architecture: arm64 (aarch64)

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

Versions of packages kernel-package depends on:
ii  bc   1.07.1-2
ii  binutils 2.31.1-6ubuntu1
ii  build-essential  12.5ubuntu2
ii  bzip21.0.6-9
ii  dpkg-dev 1.19.0.5ubuntu5
ii  file 1:5.34-2ubuntu0.1
ii  gettext  0.19.8.1-8ubuntu0.1
ii  kmod 25-1ubuntu1.2
ii  po-debconf   1.0.20
ii  xmlto0.0.28-2
ii  xz-utils [lzma]  5.2.2-1.3

Versions of packages kernel-package recommends:
ii  cpio   2.12+dfsg-6
pn  docbook-utils  
ii  kernel-common  13.018+nmu1
pn  uboot-mkimage  

Versions of packages kernel-package suggests:
ii  libncurses-dev  6.1+20180210-4ubuntu1
pn  linux-source

-- no debconf information

Bug#925612: psi-plus: the following option is always enabled:option/messages/chat/raise chat window on receiving new messages

[joe]

Package: psi-plus
Version: 1.4.554-1~bpo9+1
Severity: normal

Dear Maintainer,

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

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

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



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

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

Versions of packages psi-plus depends on:
ii  libc6 2.24-11+deb9u4
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libhunspell-1.4-0 1.4.1-2+b2
ii  libidn11  1.33-1
ii  libminizip1   1.1-8+b1
ii  libqca-qt5-2  2.1.1-4+b2
ii  libqca-qt5-2-plugins  2.1.1-4+b2
ii  libqt5concurrent5 5.7.1+dfsg-3+deb9u1
ii  libqt5core5a  5.7.1+dfsg-3+deb9u1
ii  libqt5dbus5   5.7.1+dfsg-3+deb9u1
ii  libqt5gui55.7.1+dfsg-3+deb9u1
ii  libqt5keychain1   0.7.0-3
ii  libqt5network55.7.1+dfsg-3+deb9u1
ii  libqt5sql55.7.1+dfsg-3+deb9u1
ii  libqt5sql5-sqlite 5.7.1+dfsg-3+deb9u1
ii  libqt5svg55.7.1~20161021-2+b2
ii  libqt5widgets55.7.1+dfsg-3+deb9u1
ii  libqt5x11extras5  5.7.1~20161021-2
ii  libqt5xml55.7.1+dfsg-3+deb9u1
ii  libstdc++66.3.0-18+deb9u1
ii  libx11-6  2:1.6.4-3+deb9u1
ii  psi-plus-common   1.4.554-1~bpo9+1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages psi-plus recommends:
ii  psi-plus-l10n 0.16.330-1
ii  psi-plus-plugins  1.4.554-1~bpo9+1
ii  psi-plus-sounds   0.16.330-1.3
ii  sox   14.4.1-5+deb9u1

Versions of packages psi-plus suggests:
ii  xdg-utils  1.1.1-1+deb9u1

-- no debconf information

Bug#925613: unblock: strip-nondeterminism/1.1.2-1

[Mattia Rizzolo]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear RT,

please consider unblocking strip-nondeterminism; the version in unstable
is a minimal thing fixing a single bug.  Full diff:

diffstat for strip-nondeterminism-1.1.1 strip-nondeterminism-1.1.2

 debian/changelog|8 
 lib/File/StripNondeterminism.pm |4 ++--
 2 files changed, 10 insertions(+), 2 deletions(-)

diff -Nru strip-nondeterminism-1.1.1/debian/changelog 
strip-nondeterminism-1.1.2/debian/changelog
--- strip-nondeterminism-1.1.1/debian/changelog 2019-02-13 09:31:59.0 
+0100
+++ strip-nondeterminism-1.1.2/debian/changelog 2019-03-12 18:47:40.0 
+0100
@@ -1,3 +1,11 @@
+strip-nondeterminism (1.1.2-1) unstable; urgency=medium
+
+  * Call file(1) with the "--" argument placeholder to fix normalisation of
+files starting with a hyphen.
+(Closes: reproducible-builds/strip-nondeterminism#6, #924407)
+
+ -- Chris Lamb   Tue, 12 Mar 2019 17:47:40 +
+
 strip-nondeterminism (1.1.1-1) unstable; urgency=medium

   * dh_strip_nondeterminism: Deduplicate hardlinks via stat(2) to avoid issues
diff -Nru strip-nondeterminism-1.1.1/lib/File/StripNondeterminism.pm 
strip-nondeterminism-1.1.2/lib/File/StripNondeterminism.pm
--- strip-nondeterminism-1.1.1/lib/File/StripNondeterminism.pm  2019-02-13 
09:29:48.0 +0100
+++ strip-nondeterminism-1.1.2/lib/File/StripNondeterminism.pm  2019-03-12 
18:47:00.0 +0100
@@ -25,7 +25,7 @@

 our($VERSION, $canonical_time, $clamp_time);

-$VERSION = '1.1.1'; # 
+$VERSION = '1.1.2'; # 

 sub init() {
$ENV{'TZ'} = 'UTC';
@@ -35,7 +35,7 @@
 sub _get_file_type($) {
my $file=shift;
open(FILE, '-|') # handle all filenames safely
- || exec('file', $file)
+ || exec('file', '--', $file)
  || die "can't exec file: $!";
my $type=;
close FILE;


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#925605: unblock: ruby-carrierwave/1.3.1-2

[Utkarsh Gupta]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Hey,

Please unblock package ruby-carrierwave.

There was a bug (#924830) reported against the package with severity:
serious.
The bug was reported on 17th March and was resolved in the latest upload,
which was on 24th March.
It had previously migrated to testing on 31st January 2019, until an RC bug
was reported against it.
Thus, requesting you to please unblock the same and let it be a part of
Buster, which it was going to :)


Best,
Utkarsh

unblock ruby-carrierwave/1.3.1-2

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

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

Bug#901193: Bug#901003: There is no standard way of removing transitional / dummy packages

[Justin B Rye]

Further thoughts on a revised version:
> Dummy packages
> 
>   Some packages from  have been split into several
> packages in , often to improve system maintainability.  To
> ease the upgrade path in such cases,  often provides
> dummy packages: empty packages that have the same name as
> the old package in  with dependencies that cause the new
> packages to be installed.  These dummy packages are
> considered redundant after the upgrade and can be safely removed.
> 

This talks as if package *splits* are the normal reason for
transitional dummy packages.  Is that even true?  The only specific
case I remember running into for my trial Stretch/Buster upgrades is
apt-transport-https, where on the contrary the reason the package has
become redundant is that its functions have been absorbed into the
main package.

Instead of starting from the developer's point of view and talking
about package-maintenance workflows that can result in the existence
of transitional packages, we should start by describing the symptoms
visible to end users: a package that was directly useful in Stretch
has become a redundant placeholder in Buster.

> 
>   Most (but not all) dummy packages' descriptions indicate their
> purpose. Package descriptions for dummy packages are not uniform,
> however, so you might also find deborphan with the
> --guess-* options (e.g.
> --guess-dummy) useful to detect them in your system.
>  Note that some dummy packages are not intended to be removed after an
> upgrade but are, instead, used to keep track of the current available
> version of a program over time.
> 
>   

I hadn't noticed that deborphan *also* chooses to standardise on the
term "dummy".  It's true that apt-transport-https is a dummy package;
unfortunately, *all* metapackages are empty placeholder dummy-packages
(and some of them use the word "dummy" in their descriptions), so a
command "deborphan --guess-dummy" really ought to find games-all and
linux-image-amd64 and erlang as well.  The thing that's special about
apt-transport-https is that it's a *transitional* package.

If only debtags had been competently implemented this would all have
been solved a decade ago...
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff --git a/en/upgrading.dbk b/en/upgrading.dbk
index a22924f3..37fa449d 100644
--- a/en/upgrading.dbk
+++ b/en/upgrading.dbk
@@ -1311,24 +1311,25 @@ $ aptitude purge '~c'
   
 
   
-Dummy packages
-
-  Some packages from  have been split into several packages in , often
-  to improve system maintainability.  To ease the upgrade path in such cases,
-   often provides dummy packages: empty packages that have the same name as
-  the old package in  with dependencies that cause the new packages to be
-  installed.  These dummy packages are considered redundant after the
-  upgrade and can be safely removed.
-
-
-  Most (but not all) dummy packages' descriptions indicate their purpose.
-  Package descriptions for dummy packages are not uniform, however, so you might
-  also find deborphan with the
+Transitional dummy packages
+
+  Some packages from  may have been replaced in 
+  by transitional dummy packages, which are empty placeholders designed to
+  simplify upgrades. If for instance an application that was formerly a single
+  package has been split into several, a transitional package may be provided
+  with the same name as the old package and with appropriate dependencies to
+  cause the new ones to be installed. After this has happened the redundant
+  dummy package can be safely removed.
+
+
+  The package descriptions for transitional dummy packages usually indicate their
+  purpose. However, they are not uniform; in particular, some dummy
+  packages are designed to be kept installed (e.g. to express a dependency on
+  the current latest version of some program). You might also find
+  deborphan with the
   --guess-* options (e.g.
-  --guess-dummy) useful to detect them in your system.  Note
-  that some dummy packages are not intended to be removed after an upgrade but
-  are, instead, used to keep track of the current available version of a program
-  over time.
+  --guess-dummy) useful to detect transitional dummy packages
+  on your system.
 
   
 

Bug#925611: psi-plus-plugins: otr fails. looks like session starts to initiate but plugin does not "catch" key exchange.

[joe]

Package: psi-plus-plugins
Version: 1.4.554-1~bpo9+1
Severity: normal

Dear Maintainer,

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

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

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



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

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

Versions of packages psi-plus-plugins depends on:
ii  libc6  2.24-11+deb9u4
ii  libgcc11:6.3.0-18+deb9u1
ii  libgcrypt201.7.6-2+deb9u3
ii  libotr54.1.1-2
ii  libqt5core5a   5.7.1+dfsg-3+deb9u1
ii  libqt5dbus55.7.1+dfsg-3+deb9u1
ii  libqt5gui5 5.7.1+dfsg-3+deb9u1
ii  libqt5network5 5.7.1+dfsg-3+deb9u1
ii  libqt5printsupport55.7.1+dfsg-3+deb9u1
ii  libqt5sql5 5.7.1+dfsg-3+deb9u1
ii  libqt5widgets5 5.7.1+dfsg-3+deb9u1
ii  libqt5x11extras5   5.7.1~20161021-2
ii  libqt5xml5 5.7.1+dfsg-3+deb9u1
ii  libsignal-protocol-c2  2.3.1+git20171007-3~bpo9+1
ii  libssl1.1  1.1.0j-1~deb9u1
ii  libstdc++6 6.3.0-18+deb9u1
ii  libtidy5   1:5.2.0-2
ii  libx11-6   2:1.6.4-3+deb9u1
ii  libxcb11.12-1
ii  psi-plus   1.4.554-1~bpo9+1

psi-plus-plugins recommends no packages.

psi-plus-plugins suggests no packages.

-- no debconf information

Bug#923815: Info received (Bug#923815: nvidia-legacy-340xx-kernel-dkms does not build against kernel 5.0 source)

[S. R. Wright]

N.B. The nvidia-current dkms built and is operational against kernel v5.0.5

-- sRw

Bug#925606: gitlab: Fail to upgrade (error with activesupport gem)

[David L]

Package: gitlab
Version: 11.8.3-1+fto10+1
Severity: important

Hi,

Doing an apt-get upgrade fails to install gitlab (upgrading from 11.8.2).

The error message are:

Bundle complete! 187 Gemfile dependencies, 315 gems now installed.
Gems in the groups development and test were not installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
Running final rake tasks and tweaks...
gitlab_production database is not empty, skipping gitlab setup
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
rake aborted!
LoadError: cannot load such file -- sprockets/rails/context
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `block in require'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:258:in
 `load_dependency'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `require'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `block in require'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:258:in
 `load_dependency'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `require'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `block in require'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:258:in
 `load_dependency'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `require'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `block in require'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:258:in
 `load_dependency'
/usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in
 `require'
/usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:81:in
 `block (2 levels) in require'
/usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:76:in
 `each'
/usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:76:in
 `block in require'
/usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:65:in
 `each'
/usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:65:in
 `require'
/usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler.rb:114:in 
`require'
/usr/share/gitlab/config/application.rb:5:in `'
/usr/share/gitlab/Rakefile:5:in `require'
/usr/share/gitlab/Rakefile:5:in `'
(See full trace by running task with --trace)
dpkg: error processing package gitlab (--configure):
 installed gitlab package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 gitlab
E: Sub-process /usr/bin/dpkg returned an error code (1)


Downgrading package to previous working version gives the same error.


Thanks,


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

Kernel: Linux 4.9.23--grs-ipv6-64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  asciidoctor1.5.8-1
ii  bc 1.07.1-2+b1
ii  bundler1.17.3-3
ii  bzip2  1.0.6-9
ii  dbconfig-pgsql 2.0.11
ii  debconf [debconf-2.0]  1.5.71
ii  exim4-daemon-light [mail-transport-agent]  4.92-2
ii  gitlab-common  11.8.3-1+fto10+1
ii  gitlab-workhorse   7.6.0+debian-1+b20
ii  libjs-uglify   2.8.29-6
ii  lsb-base   10.2019031300
ii  nginx  1.14.2-2
ii  nginx-full [nginx] 1.14.2-2
ii  nodejs 10.15.2~dfsg-1
ii  openssh-client 1:7.9p1-9
ii  postgresql-client  11+200
ii  postgresql-client-10 [postgresql-client]   10.5-1
ii  postgresql-client-11 [postgresql-client]   11.2-2
ii  postgresql-contrib 11+200
ii  rake   12.3.1-3
ii  redis-server   5:5.0.3-4
ii  ruby   1:2.5.1
ii  ruby-ace-rails-ap  4.1.1-1
ii  

Bug#925610: ITP: ruby-maxitest -- Minitest + all the features you always wanted

[Utkarsh Gupta]

Package: wnpp
Severity: wishlist
Owner: Utkarsh Gupta 

* Package name : ruby-maxitest
  Version  : 3.1.0
  Upstream Author  : Michael Grosser
* URL  : https://github.com/grosser/maxitest
* License  : Expat
  Programming Lang : Ruby
  Description  : Minitest + all the features you always wanted
 Features:
 1. Ctrl+c stops tests and prints failures
 2. pastable rerun snippet for failures (disabled/integrated on rails 5)
 3. multiple before & after blocks
 4. around blocks around { |t| Dir.chdir(...) { t.call } }
 5. red-green output (disabled/integrated on rails 5)
 6. mtest executable to run by line number and by folder
   (disabled/integrated on rails 5)
 7. full backtrace for errors and assertions with verbose (-v)
 8. And more!

This package is needed to test ruby-premailer.

Best,
Utkarsh

Bug#637348: Icecat free browser

[iandeb]

I'm shocked no one packaged Icecat after all these years. Icecat is
absolutely a package to have in Debian, and it's more in line with DFSG
than Firefox is. This is the browser Debian should have used all these
years instead of Iceweasel. Icecat's additional features over Firefox
are all opt-in, so anyone who don't want them will have no problem, and
there is no telemetry enabled by default. It's also worth noting that
adopting Icecat as the default browser in Debian would avoid any
conflict with Mozilla in the future (although they appear to be solved
now, no one can predict what will happen in the future) and will join
the efforts of the GNU team with the Debian team for a better free
browser that will get more attention in all the Debian-based distributions.

Bug#925617: jh_build initializes javac_opts with javadoc_opts, discard javac options

[Matthias Klose]

Package: src:javatools
Version: 0.72.6
Severity: serious
Tags: sid buster patch

jh_build initializes javac_opts with javadoc_opts, discard javac options,
apparently a typo.

patch at
http://launchpadlibrarian.net/416705136/javatools_0.72.6_0.72.6ubuntu1.diff.gz

Bug#846035: Eagle needs updated to a newer version

[Brian Holaday]

Eagle has been updated to 9.3.0:
https://www.autodesk.com/products/eagle/overview

Bug#925556: UEFI or not, can't mount /dev

[Steve McIntyre]

On Thu, Mar 28, 2019 at 12:37:52AM +0800, 積丹尼 Dan Jacobson wrote:
>> "SM" == Steve McIntyre  writes:
>SM> Please attach the installer syslog so we have a chance to see what
>SM> happened. On the installed system, that's in /var/log/installer/syslog
>
>What should I give at that
>initramfs prompt you see
>that would put it on the screen?
>Then I could take a photograph of it.

Sorry, it's much too big to fit in a single screen for a photo. Try
booting the installer again in rescue mode, mount the rootfs on that
system and copy the file off so you can send it from another machine.

I appreciate that's more effort for you, but we don't have anything
like enough information here to debug this problem yet. You're showing
a system installed with Stretch, using defaults. I've personally run
that installation lots of times when testing on release day and not
seen any problems like this, so more information is needed from the
log files.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Who needs computer imagery when you've got Brian Blessed?

Bug#925618: octave-fits is underlinked

[Sébastien Villemot]

Source: octave-fits
Version: 1.0.7-2
Severity: serious
X-Debbugs-Cc: mcop...@straitcity.com

Le mercredi 27 mars 2019 à 10:04 -0500, Mark Copper a écrit :
> On the off chance of asking twice, what is this about libcfitsio?
> libcfitsio-dev is already installed with ffghps defined in fitsio.h
> 
> octave:1> pkg load fits
> octave:2> read_fits_image('castor_march_1.fit')
> error: 
> /usr/lib/aarch64-linux-gnu/octave/packages/fits-1.0.7/aarch64-unknown-linux-gnu-api-v52/read_fits_image.oct:
> failed to load:
> /usr/lib/aarch64-linux-gnu/octave/packages/fits-1.0.7/aarch64-unknown-linux-gnu-api-v52/read_fits_image.oct:
> undefined symbol: ffghps

This is clearly a bug in the package, that I am hereby reporting.

It looks like a build-dependency on pkg-config is missing (hence the
build system does not pass the correct link flags).

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


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

Bug#925320: [Android-tools-devel] Bug#925320: Acknowledgement (android-platform-tools-apksig: apksigner fails to run on OpenJDK 8 due to UnsupportedClassVersionError)

[Tiago Daitx]

Indeed, openjdk-8 is planned to be removed from buster, but any user
that tries to run apksigner with a java 8 level binary (from openjdk,
oracle, or other vendors) will be unable to do so. In addition to that
Debian derivatives might be affected: Ubuntu is keeping openjdk-8
available for users and to avoid such simply delta I am proposing the
patch to Debian.

The early changelog entry related to the "-source 8" change stated
that this was done to support java 8 level, but it missed the fact
that it should actually have added "-target 8" at the least. I am
aiming to fix that with the "--release 8" flag which is the proper way
to set source/target since OpenJDK 9.

Please note that the jh_build tool from javatools package has a bug
that causes this package to currently FTBFS (with or without my change
as the bug forces -source 7 -target 7 to be used which is incompatible
with the level 8 source code): https://bugs.debian.org/925617

Regards,
Tiago

On Mon, Mar 25, 2019 at 4:52 PM Hans-Christoph Steiner  wrote:
>
>
> Can you tell me more about the use case for this?  my understanding is
> that openjdk-8 will not be supported in buster.
>
> .hc
>
> Tiago Daitx:
> > Hi,
> >
> > Please consider my upload to mentors as a fix for this issue
> > https://mentors.debian.net/package/android-platform-tools-apksig
> > https://mentors.debian.net/debian/pool/main/a/android-platform-tools-apksig/android-platform-tools-apksig_0.8-3.dsc
> >
> > Regards,
> > Tiago
> >
> > ___
> > Android-tools-devel mailing list
> > android-tools-de...@alioth-lists.debian.net
> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/android-tools-devel
> >



-- 
Tiago Stürmer Daitx
Software Engineer
tiago.da...@canonical.com

PGP Key: 4096R/F5B213BE (hkp://keyserver.ubuntu.com)
Fingerprint = 45D0 FE5A 8109 1E91 866E  8CA4 1931 8D5E F5B2 13BE

Bug#925524: init-system-helpers: Please provide a stretch backport for debhelper 12~

[Felipe Sateler]

On Wed, Mar 27, 2019 at 7:33 AM  wrote:

> On Tue, 26 Mar 2019 11:29:29 +0100 =?utf-8?q?Ferenc_W=C3=A1gner?= <
> wf...@debian.org> wrote:
>
> > Debhelper compat level 12 is stable and available in stretch-backports,
> > but uses the --skip-systemd-native option of invoke-rc.d, thus adds
> > init-system-helpers (>= 1.54~) to misc:Pre-Depends.  This is necessary
> > to fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887904.
> > However, the resulting pre-dependency can't be satisfied in stretch,
> > making the resulting binaries of compat 12 packages uninstallable in
> > stretch.  Could you please provide a stretch backport of a suitable
> > init-system-helpers version to accompany debhelper 12~, or do you
> > recommend some other solution to this problem?  (I suppose installing a
> > newer version of init-system-helpers manually to a stretch system
> > wouldn't break it, but it's rather inconvenient even if you confirm it.)
>
> Hi Niels,
>
> I'm not sure you noticed this report.  In any case, I'd be much
> interested to hear your opinion concerning this issue.
>

I'm not opposed to a backport, and I don't think there are many problems
with attempting it. However, I do not have time to prepare and test such a
backport. Help welcome.
-- 

Saludos,
Felipe Sateler

Bug#924129: debian-installer: Kernel for armhf for stretch unbootable

[Cyril Brulebois]

Adam D. Barratt  (2019-03-26):
> As I mentioned on IRC, we can't "push it into stretch" without a point
> release, and the whole point of this exercise was to avoid having to
> schedule another short-notice point release.

FTAOD: That's exactly in line with what I think I tried to convey over
the last few days/weeks, I'm sorry if I failed to get this point
through.

> However, assuming KiBi has no objections, it sounds like we can go
> ahead with getting the -9 ABI kernel into p-u in preparation for the
> 9.9 point release in a few weeks time. Assuming I haven't missed
> anything, the d-i version in p-u should continue to be suitable for
> installing stretch on armhf in the meantime (at least until the p-u
> freeze hits, at which point d-i will get rebuilt against the new
> kernel).

Accepting the bump should be fine at this point, thanks and sorry for
the wait.


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


signature.asc
Description: PGP signature

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

[Emmanuel Bourg]

Le 27/03/2019 à 12:41, Andrej Shadura a écrit :

> I’m not entirely sure it is possible. But maybe someone else is going to
> have better luck removing openhft dependencies.

I'll get a look during the Paris BSP on sunday.

Emmanuel Bourg

Bug#925556: UEFI or not, can't mount /dev

[Steve McIntyre]

On Wed, Mar 27, 2019 at 12:07:11PM +0800, 積丹尼 Dan Jacobson wrote:
>LS> Clearly the initramfs was able to mount /dev and run fsck, but mounting
>LS> it to /root/dev to transfer to the real rootfs failed due to a missing
>LS> directory.
>
>So it booted, meaning it is not a
>https://www.debian.org/releases/stretch/amd64/ch03s06.html.en#UEFI
>problem...

Please attach the installer syslog so we have a chance to see what
happened. On the installed system, that's in /var/log/installer/syslog

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Armed with "Valor": "Centurion" represents quality of Discipline,
  Honor, Integrity and Loyalty. Now you don't have to be a Caesar to
  concord the digital world while feeling safe and proud.

Bug#923810: ITP: ruby-sassc -- Use libsass with Ruby

[Manas Kashyap]

So, As Jonas said , that the way we do in ruby-team , keeping sbuild happy
and checking it from meta build command , is not similar to the way it is
maintained by sass team , so i would like to maintain this ruby-sassc
package in ruby-team , therefore i request , to please delete the repo from
sass team and i will ask in ruby-team to create a desired repo and will add
it there.

On Thu, Mar 7, 2019 at 10:13 PM Manas Kashyap 
wrote:

> sure , i will thanks for the guidance.
>
> On Tue, Mar 5, 2019 at 10:57 PM Jonas Smedegaard  wrote:
>
>> Quoting Manas Kashyap (2019-03-05 17:50:50)
>> > Package: wnpp
>> > Severity: wishlist
>> > Owner: Manas Kashyap 
>> > X-Debbugs-CC: debian-de...@lists.debian.org,
>> debian-r...@lists.debian.org
>> >
>> > * Package name: ruby-sassc
>> >   Version : 2.0.1
>> >   Upstream Author : Ryan Boland.
>> > * URL : https://github.com/sass/sassc-ruby
>> > * License : MIT
>> >   Programming Lang: Ruby
>> >   Description : It combines the speed of libsass, the Sass C
>> > implementation, with the ease of use of the original Ruby Sass library.
>> .
>> >  This library utilizes libsass to allow you to compile SCSS or SASS
>> syntax
>> > to CSS
>>
>> Great!
>>
>> Please consider joining the Sass team, and maintain it there :-)
>>
>> https://tracker.debian.org/teams/sass/
>>
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-sass-devel
>>
>>
>>  - Jonas
>>
>> --
>>  * Jonas Smedegaard - idealist & Internet-arkitekt
>>  * Tlf.: +45 40843136  Website: http://dr.jones.dk/
>>
>>  [x] quote me freely  [ ] ask before reusing  [ ] keep private
>>
>

Bug#925620: Update Package: Arduino : 1.8.9

[Brian Holaday]

Package: arduino
Version: 2:1.0.5+dfsg2-4.1
severity: important
affects: 925578

Hi Geert,

No Problem: I reassigned the bug to the correct package I believe:
arduino-core would need updated assuming I am correct the package is 1.0.5.

On Wed, Mar 27, 2019 at 11:36 AM Brian Holaday 
wrote:

> Hi Geert,
>
> No Problem: I reassigned the bug to the correct package I believe:
> arduino-core would need updated assuming I am correct the package is 1.0.5.
>
> On Wed, Mar 27, 2019 at 12:48 AM Geert Stappers 
> wrote:
>
>> Control: severity normal
>>
>> On Tue, Mar 26, 2019 at 09:15:36PM -0600, Brian Holaday wrote:
>>
>>
>> > I created a script for easier install.
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923220#42
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923220#52
>>
>>
>> Groeten
>> Geert Stappers
>> --
>> Leven en laten leven
>>
>

Bug#925616: ITP: placement -- OpenStack resource placement service

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: placement
  Version : 1.0.0~rc1
  Upstream Author : OpenStack Discuss 
* URL : https://github.com/openstack/placement
* License : Apache-2.0
  Programming Lang: Python
  Description : OpenStack resource placement service

 OpenStack Placement provides an HTTP service for managing, selecting, and
 claiming providers of classes of inventory representing available resources
 in a cloud.

Note: This used to be part of Nova, and this API is now running on a separate
service, that other services may use.

Bug#925619: ITP: python-os-resource-classes -- Resource Classes for OpenStack

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: python-os-resource-classes
  Version : 0.3.0
  Upstream Author : OpenStack Foundation 
* URL : https://github.com/openstack/os-resource-classes
* License : Apache-2.0
  Programming Lang: Python
  Description : Resource Classes for OpenStack

 A resource class is a distinct type of inventory that exists in a cloud
 environment, for example VCPU, DISK_GB. They are upper case with underscores.
 They often include a unit in their name.
 .
 This package provides a collection of symbols representing those standard
 resource classes which are expected to be available in any OpenStack
 deployment.
 .
 There also exists a concept of custom resource classes. These are countable
 types that are custom to a particular environment. The OpenStack placement API
 provides a way to create these. A custom resource class always begins with a
 CUSTOM_ prefix.

Note: This is a new dependency of OpenStack Placement.

Bug#925621: virsh: error: internal error: Failed to probe QEMU binary with QMP:\n

[Thorsten Glaser]

On Wed, 27 Mar 2019, Thorsten Glaser wrote:

> I cannot start any VM any more:
> 
> tglase@tglase:~ $ virsh -c qemu:///system start Netboot
> error: Failed to start domain Netboot
> error: internal error: Failed to probe QEMU binary with QMP:

I’ve just, after a reboot, seen something interesting in syslog,
which indicates that newer libvirt MIGHT be starting the qemu
processes as dæmons in the background, instead of just when the
VMs are started.

Is this true, and, if so, can it be disabled?

My  is a shell script looking like this:

tglase@tglase:~ $ cat /usr/local/bin/qemu-in-chroot
#!/bin/sh
exec schroot -c sid-amd64 -u root -- qemu-system-x86_64 -enable-kvm "$@"

The reason for this is that qemu:x32 cannot give the VMs enough
virtual memory and that I need the amd64 binaries for that, but
I don’t want to always use the amd64 binaries, so I have both,
and amd64 only in chroot (plus the library dependencies are heavy
enough to preclude installation of the amd64 M-A alternative on
the main x32 system).

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*

**!!! NEU !!!** Mit der **tarent Academy** bieten wir ab sofort auch Trainings
und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und
Zukunftstechnologien an. Besuchen Sie uns
auf [www.tarent.de/academy](http://www.tarent.de/academy). Wir freuen uns auf
Ihren Kontakt.

*

Bug#925573: gcc-9-cross-ports: incomplete copyright

[Sean Whitton]

Hello,

On Wed 27 Mar 2019 at 12:16AM +01, Matthias Klose wrote:

> this is for the packaging; sure, I can add myself as a copyright holder, but 
> the
> binary packages take their copyright from the gcc-9-source package.

Thanks.  It would probably be worth noting this in the d/copyright file
for the source package so that users know where they can look.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#919588: [Pkg-javascript-devel] Bug#919588: nodejs: FTBFS nodejs

[Santiago Vila]

On Wed, Mar 13, 2019 at 01:22:17AM +0100, Jérémy Lal wrote:

> Course of action:
> - check if upstream already knows about those two flaky tests
> - report and mark them as flaky, or apply upstream patch fixing them
> - upload... but i'm not sure this will be unblocked.

Please consider disabling at least the tests which fail a lot.
Everybody should be able to build packages without failures, not
just buildd.debian.org.

Thanks.

Bug#925556: UEFI or not, can't mount /dev

[積丹尼 Dan Jacobson]

> "SM" == Steve McIntyre  writes:
SM> Please attach the installer syslog so we have a chance to see what
SM> happened. On the installed system, that's in /var/log/installer/syslog

What should I give at that
initramfs prompt you see
that would put it on the screen?
Then I could take a photograph of it.

Bug#925621: virsh: error: internal error: Failed to probe QEMU binary with QMP:\n

[Thorsten Glaser]

Package: libvirt-clients
Version: 5.0.0-1
Severity: important

I cannot start any VM any more:

tglase@tglase:~ $ virsh -c qemu:///system start Netboot
error: Failed to start domain Netboot
error: internal error: Failed to probe QEMU binary with QMP:

1|tglase@tglase:~ $ sudo tail -4 /var/log/libvirt/libvirtd.log
2019-03-27 17:46:06.808+: 22362: error : 
virQEMUCapsNewForBinaryInternal:4681 : internal error: Failed to probe QEMU 
binary with QMP:
2019-03-27 17:46:06.821+: 22362: warning : virQEMUCapsLogProbeFailure:4628 
: Failed to probe capabilities for /usr/bin/kvm: internal error: Failed to 
probe QEMU binary with QMP:
2019-03-27 17:49:44.508+: 22362: error : 
virQEMUCapsNewForBinaryInternal:4681 : internal error: Failed to probe QEMU 
binary with QMP:
2019-03-27 17:49:44.508+: 22362: warning : virQEMUCapsLogProbeFailure:4628 
: Failed to probe capabilities for /usr/bin/kvm: internal error: Failed to 
probe QEMU binary with QMP:


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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages libvirt-clients depends on:
ii  libacl1 2.2.53-4
ii  libapparmor12.13.2-9
ii  libaudit1   1:2.8.4-2
ii  libavahi-client30.7-4+b1
ii  libavahi-common30.7-4+b1
ii  libc6   2.28-8
ii  libcap-ng0  0.7.9-2
ii  libcurl3-gnutls 7.64.0-2
ii  libdbus-1-3 1.12.12-1
ii  libdevmapper1.02.1  2:1.02.155-2
ii  libgcc1 1:8.3.0-3
ii  libgnutls30 3.6.6-3
ii  libnl-3-200 3.4.0-1
ii  libnl-route-3-200   3.4.0-1
ii  libreadline77.0-5
ii  libsasl2-2  2.1.27+dfsg-1
ii  libselinux1 2.8-1+b1
ii  libssh2-1   1.8.0-2
ii  libvirt05.0.0-1
ii  libxml2 2.9.4+dfsg1-7+b3tarent1
ii  libyajl22.1.0-3
ii  sensible-utils  0.0.12

libvirt-clients recommends no packages.

Versions of packages libvirt-clients suggests:
ii  libvirt-daemon  5.0.0-1

-- no debconf information

Bug#925578: Update Package: Arduino : 1.8.9

[Brian Holaday]

Hi Geert,

No Problem: I reassigned the bug to the correct package I believe:
arduino-core would need updated assuming I am correct the package is 1.0.5.

Bug#924278: stretch-pu: package clamav/0.100.2+dfsg-0+deb9u1

[Sebastian Andrzej Siewior]

On 2019-03-10 23:55:55 [+0100], To sub...@bugs.debian.org wrote:
> We would like to update clamav in stable to 0.101.1 which is the latest
> release provided by upstream.
> This won't be as easy as it was previously because it will trigger a
> transistion (libclamav7 -> libclamav9) in stable similar to what we did
> in unstable (#922004) recently.

upstream released 0.100.3 which fixes three bugs with CVE numbers [0].
There is also 0.101.2.

For Stretch we tend to upload 0.100.3 before we get an approval for this
one (which would be then 0.101.2). Since the 0.100.3 is smaller, it
should be easier/quicker tor review.
Is this okay?

[0] https://blog.clamav.net/2019/03/clamav-01012-and-01003-patches-have.html

Sebastian

Bug#925870: binutils-mips64el-linux-gnuabi64: segfault while cross building gcc-8

[Helmut Grohne]

Package: binutils-mips64el-linux-gnuabi64
Version: 2.31.1-16
User: helm...@debian.org
Usertags: rebootstrap

cross building gcc-8 from amd64 to mips64el fails.

http://crossqa.debian.net/build/gcc-8_8.3.0-4_mips64el_20190326224556.log
| configure:3470: mips64el-linux-gnuabi64-gcc-8  -mabi=32 -o conftest -g -O2 
-minterlink-mips16  -Wl,-z,relro conftest.c  >&5
| collect2: fatal error: ld terminated with signal 11 [Segmentation fault]
| compilation terminated.
| 
/usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/../../../../mips64el-linux-gnuabi64/bin/ld:
 /usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/crtbeginS.o: ABI is incompatible 
with that of the selected emulation
| 
/usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/../../../../mips64el-linux-gnuabi64/bin/ld:
 failed to merge target specific data of file 
/usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/crtbeginS.o
| 
/usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/../../../../mips64el-linux-gnuabi64/bin/ld:
 /usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/crtendS.o: ABI is incompatible 
with that of the selected emulation
| 
/usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/../../../../mips64el-linux-gnuabi64/bin/ld:
 failed to merge target specific data of file 
/usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/crtendS.o
| 
/usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/../../../../mips64el-linux-gnuabi64/bin/ld:
 /usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/crtbeginS.o: in function 
`deregister_tm_clones':
| crtstuff.c:(.text+0xc): relocation truncated to fit: R_MIPS_GOT_PAGE against 
`.tm_clone_table'
| 
/usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/../../../../mips64el-linux-gnuabi64/bin/ld:
 crtstuff.c:(.text+0x10): relocation truncated to fit: R_MIPS_GOT_DISP against 
`__TMC_END__'
| 
/usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/../../../../mips64el-linux-gnuabi64/bin/ld:
 crtstuff.c:(.text+0x14): relocation truncated to fit: R_MIPS_GOT_OFST against 
`.tm_clone_table'
| 
/usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/../../../../mips64el-linux-gnuabi64/bin/ld:
 /usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/crtbeginS.o: in function 
`register_tm_clones':
| crtstuff.c:(.text+0x44): relocation truncated to fit: R_MIPS_GOT_PAGE against 
`.tm_clone_table'
| 
/usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/../../../../mips64el-linux-gnuabi64/bin/ld:
 crtstuff.c:(.text+0x48): relocation truncated to fit: R_MIPS_GOT_DISP against 
`__TMC_END__'
| 
/usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/../../../../mips64el-linux-gnuabi64/bin/ld:
 crtstuff.c:(.text+0x4c): relocation truncated to fit: R_MIPS_GOT_OFST against 
`.tm_clone_table'
| 
/usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/../../../../mips64el-linux-gnuabi64/bin/ld:
 /usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/crtbeginS.o: in function 
`__do_global_dtors_aux':
| crtstuff.c:(.text+0xa0): relocation truncated to fit: R_MIPS_GOT_PAGE against 
`.bss'
| 
/usr/lib/gcc-cross/mips64el-linux-gnuabi64/8/../../../../mips64el-linux-gnuabi64/bin/ld:
 crtstuff.c:(.text+0xa8): relocation truncated to fit: R_MIPS_GOT_OFST against 
`.bss'
| configure:3473: $? = 1

As we can see, ld segfaults. It is unclear to me why it segfaults, but
the segfault seems to be reliable for mips64el, but cannot be reproduced
for e.g. arm64.

Helmut

Bug#925334: vc4: CMA fills up and screen not updated anymore on raspi3

[Romain Perier]

On Wed, Mar 27, 2019 at 03:29:21PM +0100, Fabian Pietsch wrote:
> Package: src:linux
> Version: 4.19.28-2
> Followup-For: Bug #925334
> 
> Dear Maintainer,
> 
> the bug is still present in the current version. It took a freshly
> booted, idle system 3304 seconds for the bug to occur, though,
> so this time rather an hour (than 10-30min as stated before).
> 
> After the bug has happened, I get the following information from sysfs:
> 
> | root@rpi3:/sys/bus/platform/drivers/vc4_v3d# for I in enabled status 
> active_time suspended_time; do echo -n "$I=$(cat 
> 3fc0.v3d/power/runtime_$I) "; done; echo
> | enabled=enabled status=error active_time=16800 suspended_time=55464216
> 
> And again:
> 
> | enabled=enabled status=error active_time=16800 suspended_time=55479160
> 
> So vc4_v3d which reported the error seems to be in status=error
> and counts as suspended. Manual attempts to get it to resume again,
> now that more cma is free again, failed, but there are probably ways
> I don't know about.
> 
> "echo on > .../power/control" changed runtime_enabled=forbidden
> (and echo auto > control changed it back to runtime_enabled=enabled),
> but runtime_status remained at "error".
> 
> Regards, Fabian
> 
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: arm64 (aarch64)
> 
> Kernel: Linux 4.19.0-4-arm64 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_CRAP
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled

Hi,

As discussed on IRC, thanks for your bug report and for the refresh.

Could you test, two stuffs for me ? :

1. The VC4 driver seems to use runtime pm operations, could you try to
disable runtime suspend completly (there are kernel parameters for this
if I remember correctly) ?

2. Your kernel cmdline are... weird, could you try with minimalistic
kernel cmdline ? Only keep console= for logging to uart and/or to your
tty0 and keep your rootfs.


Thanks,
Romain


signature.asc
Description: PGP signature

Bug#925595: unblock: flatpak/1.2.4-1 (pre-approval) or 1.2.3-2 (unblock)

[Niels Thykier]

Control: tags -1 confirmed moreinfo

Simon McVittie:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> I would like to follow the 1.2.x stable-branch of flatpak in buster for
> as long as it's maintained upstream, similar to what I did with 0.8.x
> in stretch. Are the release team happy with this in principle?
> 
> In the short term, this means uploading flatpak 1.2.4 to unstable. It
> fixes CVE-2019-10063 (incomplete defence against command injection with
> TIOCSTI) and some non-security bugs. I attach a proposed diff: may I
> upload this if my tests are successful?
> 
> If 1.2.4 is not acceptable, please unblock 1.2.3-2 instead, to fix
> CVE-2019-10063 but not the non-security bugs (I already uploaded that
> version). I've attached the debdiff for that too.
> 
> See also #925569, the corresponding stable-update.
> 
> Thanks,
> smcv
> 

Hi,

Please go with 1.2.4 and remove the moreinfo tag when it is ready to be
unblocked.

Thanks,
~Niels

Bug#925877: RFS: openliberty/19.0.0.1 [ITP]

[Michael Zhang]

Package: sponsorship-requests
Severity: wishlist

 * Package name    : openliberty
   Version         : 19.0.0.1-1ubuntu1
   Upstream Author : https://groups.io/g/openliberty
 * URL             : https://openliberty.io/
 * License         : EPL-1.0
   Section         : java

  It builds those binary packages:

    openliberty - Server runtime for Java developers

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

  https://mentors.debian.net/package/openliberty
  Alternatively, one can download the package with dget using this command:

    dget -x 
https://mentors.debian.net/debian/pool/main/o/openliberty/openliberty_19.0.0.1-1ubuntu1.dsc
  More information about openliberty can be obtained fromhttps://openliberty.io/
  Changes since the last upload:

  openliberty (19.0.0.1-1ubuntu1) unstable; urgency=medium

  * Fixed many lintian errors and warnings
  * Added template argument in 'create' script
  * Added java weak dependency
  * Added SystemD service files for instance servers

 -- Michael Zhang   Mon, 25 Feb 2019 22:38:40 +
 
 
I've already submitted a RFS previously but many changes have been made 
(including the version).

>From the last email (Note: from the last RFS 
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919590 and ITP 
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916790), changes such as:

"Long description is missing. Short description far exceeds 80 chars.
source/format being "3.0 (native)" is also questionable."

were requested and have been corrected. As for the unacceptable lines in 
d/rules, we are currently in the midst of changing our public Travis CI build 
process to include the creation of the binaries (ex. *.jar).
 
We are currently looking into the debian policy manuals and lintian errors for 
more improvements on our package. We also appreciate any more constructive 
criticism to help us get this package up-to-standard for the Debian repository.

Yours Sincerely,
Michael Zhang

Bug#924802: #924802 looks mpicxx related, might be due to #807666

[Bernhard R. Link]

retitle 924802 madness: FTBFS: failure checking for working mpicxx
block 924802 807666
thanks

Just some quick fly-by observations:

While the are errors about pow in the log, those seem to be harmless and
properly ignored capability checking.

The actual error causing the failure in the log is:

-- Could NOT find MPI_CXX (missing: MPI_CXX_WORKS) 
CMake Error at 
/usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find MPI (missing: MPI_CXX_FOUND) (found version "3.1")
Call Stack (most recent call first):
  /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:378 
(_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.13/Modules/FindMPI.cmake:1671 
(find_package_handle_standard_args)
  external/mpi.cmake:6 (find_package)
  CMakeLists.txt:493 (include)


FindMPI.cmake says:
# If the find procedure fails for a variable ``MPI__WORKS``, then the 
settings detected by or passed to
# the module did not work and even a simple MPI test program failed to compile.


As the build attempt was done using "mpich amd64 3.3-2", most likely
this is related to #807666 (as the description of that bug says it makes using
mpich with c++ fail, which would fit those symptoms).

Bernhard R. Link
-- 
F8AC 04D5 0B9B 064B 3383  C3DA AFFC 96D1 151D FFDC

Bug#864017: release-notes: Assumes /etc/apt/sources.list is used (and not /etc/apt/sources.list.d/*.list or deb822) [general]

[Justin B Rye]

Justin B Rye wrote:
> Sorry, I've run out of coffee!  I'll have another look at this
> tomorrow.

I'm still only running on cheap freeze-dried instant coffee, so the
attached patch will probably still need work, but I think the
reordering of paragraphs makes sense.

In particular:
> diff --git a/en/old-stuff.dbk b/en/old-stuff.dbk
> index 0a53d737..3d1b70ed 100644
> --- a/en/old-stuff.dbk
> +++ b/en/old-stuff.dbk
> @@ -27,14 +27,14 @@ upgraded to the latest  point release.
>  
>  
>  
> -Checking your sources list
> +Checking your APT source-list files
>  
> -If any of the lines in your /etc/apt/sources.list
> -refer to stable, it effectively
> -points to  already. This might not be what you want if
> -you are not ready yet for the upgrade.  If you have already run
> -apt update, you can still get back without
> -problems by following the procedure below.
> +  If any of the lines in your APT source-list files (see  +  
> url="https://manpages.debian.org//apt/sources.list.5.html;>sources.list(5))
> +  contain references to stable, this is 
> effectively pointing to
> +   already. This might not be what you want if you are not yet 
> ready
> +  for the upgrade.  If you have already run apt update,
> +  you can still get back without problems by following the procedure below.
>  

I've let this keep a fuller explanation instead of a crossreference,
partly because I haven't figured out how crossreferences work yet.

[,,,]
> index a22924f3..d241de1f 100644
> --- a/en/upgrading.dbk
> +++ b/en/upgrading.dbk
> @@ -244,16 +244,26 @@
>  
>  
>  
> -  Checking system status
> +  Checking APT configuration status

"System" could mean anything; all the following checks deal with the
status of the package management system in particular.

>
> -The upgrade process described in this chapter has been designed for 
> upgrades
> -from pure  systems without third-party 
> packages.
> -For the greatest reliability of the
> -upgrade process, you may wish to remove third-party packages from your 
> system
> -before you begin upgrading.
> +The upgrade process described in this chapter has been designed for
> +pure Debian stable systems. If your APT configuration 
> mentions
> +additional sources besides , or if you have installed 
> packages
> +from other releases or from third parties, then to ensure a reliable 
> upgrade
> +process you may wish to begin by removing these complicating factors.
>
>
> -Below there are two methods for finding such packages by using either
> +The main configuration file that APT uses to decide what sources it 
> should
> +download packages from is /etc/apt/sources.list, but
> +it can also use files in the 
> /etc/apt/sources.list.d/
> +directory - for details see  +
> url="https://manpages.debian.org//apt/sources.list.5.html;>sources.list(5).
> +If your system is using multiple source-list files then you will need to 
> ensure
> +they stay consistent.
> +  

Inserting the main "first" introduction of the concept of APT
sources-list files, and adding the point that having a whole
collection of different /etc/apt/sources.list.d/*.list files pointing
at different releases is a bad idea.

> +  
> +Below there are two methods for finding installed packages that
> +did not come from Debian, using either
>  aptitude or apt-forktracer.  Please
>  note that neither of them are 100% accurate  (e.g. the aptitude example
>  will list packages that were once provided by Debian but no longer are, 
> such as
>  old kernel packages).

Incidentally, why is it bad that aptitude will detect the fact you've
got an obsolete kernel installed?  On a stable system, it must be:
 * a homebrew kernel-package; or
 * an ancient relic from  or at least
 * a leftover from an old point release;
and any of these would be things you should consider
removing/replacing before the upgrade, i.e. a "true positive".
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff --git a/en/old-stuff.dbk b/en/old-stuff.dbk
index 0a53d737..3d1b70ed 100644
--- a/en/old-stuff.dbk
+++ b/en/old-stuff.dbk
@@ -27,14 +27,14 @@ upgraded to the latest  point release.
 
 
 
-Checking your sources list
+Checking your APT source-list files
 
-If any of the lines in your /etc/apt/sources.list
-refer to stable, it effectively
-points to  already. This might not be what you want if
-you are not ready yet for the upgrade.  If you have already run
-apt update, you can still get back without
-problems by following the procedure below.
+  If any of the lines in your APT source-list files (see https://manpages.debian.org//apt/sources.list.5.html;>sources.list(5))
+  contain references to stable, this is effectively pointing to
+   already. This might not be what you want if you are not yet ready
+  for the upgrade.  If you have already run apt update,
+  you can still get