Processed: desktopnova: diff for NMU version 0.8.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 851454 + pending
Bug #851454 [desktopnova] desktopnova: should build-depend on python-minimal; 
FTBFS in Ubuntu
Added tag(s) pending.
> tags 853371 + pending
Bug #853371 [src:desktopnova] desktopnova FTBFS: dbus-server-bindings.h: No 
such file or directory
Bug #866766 [src:desktopnova] desktopnova FTBFS: dbus-server-bindings.h: No 
such file or directory
Added tag(s) pending.
Added tag(s) pending.

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

Bug#853371: desktopnova: diff for NMU version 0.8.1-1.1

[Mattia Rizzolo]

Control: tags 851454 + pending
Control: tags 853371 + pending


Dear maintainer,

I'm sponsoring an NMU on behalf of Unit 193 (CCed) for desktopnova
(versioned as 0.8.1-1.1) and uploaded it to DELAYED/2.
Please feel free to tell me if I should delay it longer.

Regards.


-- 
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  `-
diffstat for desktopnova-0.8.1 desktopnova-0.8.1

 changelog   |   15 +++
 compat  |2 +-
 control |2 +-
 patches/depend-on-generated-files.patch |   16 
 patches/series  |1 +
 5 files changed, 34 insertions(+), 2 deletions(-)

diff -Nru desktopnova-0.8.1/debian/changelog desktopnova-0.8.1/debian/changelog
--- desktopnova-0.8.1/debian/changelog	2011-03-20 16:42:34.0 +0100
+++ desktopnova-0.8.1/debian/changelog	2018-05-16 08:49:31.0 +0200
@@ -1,3 +1,18 @@
+desktopnova (0.8.1-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+
+  [ Juhani Numminen ]
+  * d/p/depend-on-generated-files.patch: Added missing dependency information.
+(Closes: #853371)
+
+  [ Unit 193 ]
+  * d/compat, d/control:
+- Bump to DH 9, gains exported build flags which gives us debug symbols.
+  * d/control: Build-depend on python-minimal. (Closes: #851454)
+
+ -- Unit 193   Wed, 16 May 2018 02:49:31 -0400
+
 desktopnova (0.8.1-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru desktopnova-0.8.1/debian/compat desktopnova-0.8.1/debian/compat
--- desktopnova-0.8.1/debian/compat	2010-07-28 21:28:53.0 +0200
+++ desktopnova-0.8.1/debian/compat	2018-05-16 08:49:31.0 +0200
@@ -1 +1 @@
-7
+9
diff -Nru desktopnova-0.8.1/debian/control desktopnova-0.8.1/debian/control
--- desktopnova-0.8.1/debian/control	2011-11-10 17:52:01.0 +0100
+++ desktopnova-0.8.1/debian/control	2018-05-16 08:49:31.0 +0200
@@ -2,7 +2,7 @@
 Section: misc
 Priority: optional
 Maintainer: Stefan Haller 
-Build-Depends: debhelper (>= 7), cmake, libglib2.0-dev, libgconf2-dev, libgtk2.0-dev, intltool, libxml2-dev, libdbus-glib-1-dev, libxfconf-0-dev
+Build-Depends: debhelper (>= 9), cmake, libglib2.0-dev, libgconf2-dev, libgtk2.0-dev, intltool, libxml2-dev, libdbus-glib-1-dev, libxfconf-0-dev, python-minimal
 Standards-Version: 3.9.2
 Homepage: http://launchpad.net/desktopnova
 
diff -Nru desktopnova-0.8.1/debian/patches/depend-on-generated-files.patch desktopnova-0.8.1/debian/patches/depend-on-generated-files.patch
--- desktopnova-0.8.1/debian/patches/depend-on-generated-files.patch	1970-01-01 01:00:00.0 +0100
+++ desktopnova-0.8.1/debian/patches/depend-on-generated-files.patch	2018-05-16 08:49:31.0 +0200
@@ -0,0 +1,16 @@
+Description: Added missing dependency information.
+ This caused "src/dbus/dbus-server.c:25:10: fatal error:
+ dbus-server-bindings.h: No such file or directory".
+Author: Juhani Numminen 
+Bug-Debian: https://bugs.debian.org/853371
+Last-Update: 2017-12-05
+
+--- a/src/dbus/CMakeLists.txt
 b/src/dbus/CMakeLists.txt
+@@ -23,3 +23,5 @@
+ ${GTHREAD2_INCLUDE_DIRS}
+ ${CMAKE_CURRENT_BINARY_DIR})
+ ADD_LIBRARY(desktopnova-dbus STATIC dbus-server.c)
++
++ADD_DEPENDENCIES(desktopnova-dbus dbus-bindings)
+
diff -Nru desktopnova-0.8.1/debian/patches/series desktopnova-0.8.1/debian/patches/series
--- desktopnova-0.8.1/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ desktopnova-0.8.1/debian/patches/series	2018-05-16 08:49:31.0 +0200
@@ -0,0 +1 @@
+depend-on-generated-files.patch


signature.asc
Description: PGP signature

Processed: desktopnova: diff for NMU version 0.8.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 851454 + pending
Bug #851454 [desktopnova] desktopnova: should build-depend on python-minimal; 
FTBFS in Ubuntu
Ignoring request to alter tags of bug #851454 to the same tags previously set
> tags 853371 + pending
Bug #853371 [src:desktopnova] desktopnova FTBFS: dbus-server-bindings.h: No 
such file or directory
Bug #866766 [src:desktopnova] desktopnova FTBFS: dbus-server-bindings.h: No 
such file or directory
Ignoring request to alter tags of bug #853371 to the same tags previously set
Ignoring request to alter tags of bug #866766 to the same tags previously set

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

Bug#895741: plastimatch FTBFS with libdlib-dev 19.10-1

[Hugo Lefeuvre]

Hi Adrian,

Yes, it is most likely a bug in the dlib package. Last dlib updates made
Debian packaging considerably trickier by separating build of static
files and build of shared libraries. I have just noticed that we ship
the cmake config files of the shared build into the -dev package, which
might be the source of your problems. In fact, we should rather ship the
files produced by the static build (but still, I'm not 100% it's going to
be sufficient).

I have just prepared an upload addressing this issue, but I had
difficulties to build plastimatch with dlib 19.1 (configuration issues,
plastimatch seems to to use deprecated directives), so I couldn't really
test it.

You can find test packages here[0]. Can you try them ?

Regards,
 Hugo

[0] https://people.debian.org/~hle/testpkg/dlib/

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ 9C4F C8BF A4B0 8FC5 48EB 56B8 1962 765B B9A8 BACA


signature.asc
Description: PGP signature

Processed: fix up version numbering for gnucash webkitgtk bug

[Debian Bug Tracking System]

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

> found 790204 1:2.6.19-1
Bug #790204 {Done: Dmitry Smirnov } [src:gnucash] gnucash: 
depends on libwebkitgtk-1.0-0 which is deprecated
Marked as found in versions gnucash/1:2.6.19-1.
>
End of message, stopping processing here.

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

Processed: fix up version numbering for gnucash webkitgtk bug

[Debian Bug Tracking System]

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

> unarchive 790204
Bug #790204 {Done: Dmitry Smirnov } [src:gnucash] gnucash: 
depends on libwebkitgtk-1.0-0 which is deprecated
Unarchived Bug 790204
> found 790204 1:2.6.17-1
Bug #790204 {Done: Dmitry Smirnov } [src:gnucash] gnucash: 
depends on libwebkitgtk-1.0-0 which is deprecated
Marked as found in versions gnucash/1:2.6.17-1.
>
End of message, stopping processing here.

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

Bug#896566: marked as done (gummi: FTBFS against new libsyntex)

[Debian Bug Tracking System]

Your message dated Wed, 16 May 2018 02:37:26 +
with message-id 
and subject line Bug#896566: fixed in gummi 0.6.6-5
has caused the Debian Bug report #896566,
regarding gummi: FTBFS against new libsyntex
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
896566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gummi
Version: 0.6.6-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: sid buster

gummi fails to build against the new version of libsyntex in unstable:
| gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -pthread 
-I/usr/include/gtksourceview-2.0 -I/usr/include/libxml2 -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/poppler/glib -I/usr/include/poppler -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -pthread -I/usr/include/gtkspell-2.0 
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/synctex -export-dynamic -Wall -O2 
-DGUMMI_LIBS=\"/usr/lib/x86_64-linux-gnu/gummi\" 
-DGUMMI_DATA=\"/usr/share/gummi\" -DGUMMI_LOCALES=\"/usr/share/locale\" -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o gui/gui-preview.o gui/gui-preview.c
| gui/gui-preview.c: In function 'synctex_run_parser':
| gui/gui-preview.c:1044:5: error: unknown type name 'synctex_scanner_t'; use 
'struct' keyword to refer to the type
|  synctex_scanner_t sync_scanner = 
synctex_scanner_new_with_output_file(pc->uri, C_TMPDIR, 1);
|  ^
|  struct 
| gui/gui-preview.c:1044:38: warning: initialization makes integer from pointer 
without a cast [-Wint-conversion]
|  synctex_scanner_t sync_scanner = 
synctex_scanner_new_with_output_file(pc->uri, C_TMPDIR, 1);
|   ^~~~
| gui/gui-preview.c:1048:30: warning: passing argument 1 of 
'synctex_display_query' makes pointer from integer without a cast 
[-Wint-conversion]
|  if(synctex_display_query(sync_scanner, tex_file, line, column)>0) {
|   ^~~~
| In file included from gui/gui-preview.c:51:0:
| /usr/include/synctex/synctex_parser.h:202:22: note: expected 
'synctex_scanner_p {aka struct synctex_scanner_t *}' but argument is of type 
'int'
|  synctex_status_t synctex_display_query(synctex_scanner_p scanner,const 
char *  name,int line,int column, int page_hint);
|   ^
| gui/gui-preview.c:1048:8: error: too few arguments to function 
'synctex_display_query'
|  if(synctex_display_query(sync_scanner, tex_file, line, column)>0) {
| ^
| In file included from gui/gui-preview.c:51:0:
| /usr/include/synctex/synctex_parser.h:202:22: note: declared here
|  synctex_status_t synctex_display

Bug#898738: debootstrap fails when specifying components

[Hideki Yamane]

Hi,

 Sorry, and thank you for digging it.

On Tue, 15 May 2018 21:44:38 +0200
Cyril Brulebois  wrote:
> I think I've found the issue. At least partly reverting the commit
> makes retrieving/validating indices work again, possibly because
> un-local-izing names was a bad idea? (I took all hunks from the commit
> that touched the download_release_indices function. Not everything is
> needed I guess.)
> 
> See attached patch, against the offending commit. It doesn't apply to
> master as-is because of the by-hash addition.

 Simply initialize "ext" prevents this failure, could you check attached
 patch, please?


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp
>From 768183053bcd02f050fcd2d50c08024ff48a786f Mon Sep 17 00:00:00 2001
From: Hideki Yamane 
Date: Wed, 16 May 2018 08:55:23 +0900
Subject: [PATCH] Fix download failure when specifying multiple components
 (Closes: #898738)

> # debootstrap --components=main,contrib,non-free unstable unstable http://deb.debian.org/debian
(snip)
> I: Retrieving Packages
> I: Validating Packages
> W: Retrying failed download of
> http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages
> I: Retrieving Packages
> I: Validating Packages
> W: Retrying failed download of
> http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages
(snip)

Fix above by initializing "ext" for each component
---
 functions | 1 +
 1 file changed, 1 insertion(+)

diff --git a/functions b/functions
index fa7c060..74d25b3 100644
--- a/functions
+++ b/functions
@@ -681,6 +681,7 @@ download_release_indices () {
 		bz2i="$(get_release_checksum "$reldest" "$subpath.bz2")"
 		gzi="$(get_release_checksum "$reldest" "$subpath.gz")"
 		normi="$(get_release_checksum "$reldest" "$subpath")"
+		ext=""
 		if [ "$acquirebyhash" != "" ]; then
 			ext="$ext byhash"
 		fi
-- 
2.17.0

Bug#898201: fix?

[Julien]

Hi,

This upstream patch should fix this issue : 
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=37a30b5435a45c3f8e233309fc70fc7de92b2e76

Bug#898754: marked as done (libcatalyst-controller-html-formfu-perl: FTBFS: Can't locate MooseX/Attribute/FormFuChained.pm in @INC)

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 21:05:33 +
with message-id 
and subject line Bug#898754: fixed in libcatalyst-controller-html-formfu-perl 
2.04-1
has caused the Debian Bug report #898754,
regarding libcatalyst-controller-html-formfu-perl: FTBFS: Can't locate 
MooseX/Attribute/FormFuChained.pm in @INC
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
898754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcatalyst-controller-html-formfu-perl
Version: 2.02-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest
Tags: fixed-upstream
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=125102

As noticed by ci.debian.net, this package fails its test suite on current
sid, making it fail to build from source.

 https://ci.debian.net/packages/libc/libcatalyst-controller-html-formfu-perl/

It looks like libhtml-formfu-perl_2.06-1 dropped the
MooseX::Attribute::FormFuChained module, but at least this package is
still using it. This seems to be fixed upstream in 2.03.

Once this is fixed, please also make libhtml-formfu-perl Break the earlier
versions so that partial upgrades cannot end up with broken combinations.
I hope this is also be enough to inform the britney autopkgtest integration
that the packages need to migrate together.

(I see libhtml-formfu-model-dbic-perl was similarly affected but is already
fixed; please consider adding a Breaks entry for that one too if applicable.)

>From my build log:

  [error] Caught exception in TestApp::Controller::Token->form "Can't locate 
MooseX/Attribute/FormFuChained.pm in @INC (you may need to install the 
MooseX::Attribute::FormFuChained module) (@INC contains: t/lib 
/<>/blib/lib /<>/blib/arch /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/<>/blib/lib/HTML/FormFu/Plugin/RequestToken.pm line 8.
  BEGIN failed--compilation aborted at 
/<>/blib/lib/HTML/FormFu/Plugin/RequestToken.pm line 8.
  Compilation failed in require at /usr/share/perl5/HTML/FormFu/Util.pm line 
390.
   at /usr/share/perl5/HTML/FormFu/Role/FormAndElementMethods.pm line 235."
  
  #   Failed test 'GET http://localhost/token/form'
  #   at t/01basic-token.t line 11.
  # 500
  # Internal Server Error
  
  #   Failed test 'Found form'
  #   at t/01basic-token.t line 15.
  Can't call method "find_input" on an undefined value at t/01basic-token.t 
line 17.
  # Tests were run but no plan was declared and done_testing() was not seen.
  # Looks like your test exited with 255 just after 2.
  t/01basic-token.t  
  not ok 1 - GET http://localhost/token/form
  not ok 2 - Found form
  Dubious, test returned 255 (wstat 65280, 0xff00)
  Failed 2/2 subtests 
 
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libcatalyst-controller-html-formfu-perl
Source-Version: 2.04-1

We believe that the bug you reported is fixed in the latest version of
libcatalyst-controller-html-formfu-perl, which is due to be installed in the 
Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Florian Schlichting  (supplier of updated 
libcatalyst-controller-html-formfu-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 May 2018 22:04:14 +0200
Source: libcatalyst-controller-html-formfu-perl
Binary: libcatalyst-controller-html-formfu-perl
Architecture: source all
Version: 2.04-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Florian Schlichting 
Description:
 libcatalyst-controller-html-formfu-perl - Catalyst integration for HTML::FormFu
Closes: 898754
Changes:
 libcatalyst-controller-html-formfu-perl (2.04-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Damyan Ivanov ]
   * declare conformance with Policy 4.1.3 (no changes needed)
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch

Bug#898760: marked as done (icu4j: FTBFS with Java 10)

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 21:05:25 +
with message-id 
and subject line Bug#898760: fixed in icu4j 60.2-2
has caused the Debian Bug report #898760,
regarding icu4j: FTBFS with Java 10
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

icu4j fails to build with Java 10 due to a buggy JDK detection logic:

  Buildfile: /build/1st/icu4j-60.2/build.xml
  
  BUILD FAILED
  /build/1st/icu4j-60.2/build.xml:125: The JDK version is too old or unknown.

It also fails to compile due to changes to the doclet API:

  @compile:
   [echo] build-local: ../../main/shared/../../build-local.properties
   [echo] --- java compiler arguments 
   [echo] source dir: /build/1st/icu4j-60.2/icu4j/tools/build/src
   [echo] output dir: /build/1st/icu4j-60.2/icu4j/tools/build/out/bin
   [echo] bootclasspath:
   [echo] classpath:  /usr/lib/jvm/default-java/lib/tools.jar
   [echo] source: 1.6
   [echo] target: 1.6
   [echo] debug:  on
   [echo] encoding:   UTF-8
   [echo] compiler arg:   -Xlint:none
   [echo] 
  [mkdir] Created dir: /build/1st/icu4j-60.2/icu4j/tools/build/out/bin
  [javac] Using javac -source 1.6 is no longer supported, switching to 1.7
  [javac] Using javac -target 1.6 is no longer supported, switching to 1.7
  [javac] Compiling 17 source files to 
/build/1st/icu4j-60.2/icu4j/tools/build/out/bin
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTaglet.java:17:
 error: package com.sun.tools.doclets.internal.toolkit.taglets does not exist
  [javac] import com.sun.tools.doclets.internal.toolkit.taglets.Taglet;
  [javac]  ^
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:13:
 error: package com.sun.tools.doclets.formats.html.markup does not exist
  [javac] import com.sun.tools.doclets.formats.html.markup.RawHtml;
  [javac] ^
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:14:
 error: package com.sun.tools.doclets.internal.toolkit does not exist
  [javac] import com.sun.tools.doclets.internal.toolkit.Content;
  [javac]  ^
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:15:
 error: package com.sun.tools.doclets.internal.toolkit.taglets does not exist
  [javac] import com.sun.tools.doclets.internal.toolkit.taglets.Taglet;
  [javac]  ^
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:16:
 error: package com.sun.tools.doclets.internal.toolkit.taglets does not exist
  [javac] import 
com.sun.tools.doclets.internal.toolkit.taglets.TagletWriter;
  [javac]  ^
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:24:
 error: cannot find symbol
  [javac] public abstract class ICUTagletAdapter implements Taglet {
  [javac]   ^
  [javac]   symbol: class Taglet
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTaglet.java:19:
 error: cannot find symbol
  [javac] public abstract class ICUTaglet extends ICUTagletAdapter 
implements Taglet {
  [javac]   
  ^
  [javac]   symbol: class Taglet
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:30:
 error: cannot find symbol
  [javac] public Content getTagletOutput(Tag tag, TagletWriter writer)
  [javac] ^
  [javac]   symbol:   class TagletWriter
  [javac]   location: class ICUTagletAdapter
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:30:
 error: cannot find symbol
  [javac] public Content getTagletOutput(Tag tag, TagletWriter writer)
  [javac]^
  [javac]   symb

Processed: your mail

[Debian Bug Tracking System]

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

> severity 898795 important
Bug #898795 [firefox-esr] firefox-esr: [RC]  embedded copy of normalize.css
Severity set to 'important' from 'serious'
> severity 898796 important
Bug #898796 [thunderbird] thunderbird: [RC]  embedded copy of normalize.css
Severity set to 'important' from 'serious'
> severity 898794 important
Bug #898794 [wims-modules] wims-module: [RC]  embedded copy of normalize.css
Severity set to 'important' from 'serious'
> severity 898793 important
Bug #898793 [sympa] sympa: [RC]  embedded copy of normalize.css
Severity set to 'important' from 'serious'
> severity 898792 important
Bug #898792 [rust-src] rust-src: [RC]  embedded copy of normalize.css
Severity set to 'important' from 'serious'
> severity 898791 important
Bug #898791 [rust-doc] rust-doc: [RC]  embedded copy of normalize.css
Severity set to 'important' from 'serious'
> severity 898790 important
Bug #898790 [r-cran-shiny] r-cran-shiny: [RC]  embedded copy of normalize.css
Severity set to 'important' from 'serious'
> severity 898789 important
Bug #898789 [recon-ng] recon-ng: [RC]  embedded copy of normalize.css
Severity set to 'important' from 'serious'
> severity 898788 important
Bug #898788 [libreoffice-help-common] libreoffice-help-common: [RC]  embedded 
copy of normalize.css
Severity set to 'important' from 'serious'
> severity 898787 important
Bug #898787 [src:ldap-account-manager] ldap-account-manager: [RC]  embedded 
copy of normalize.css
Severity set to 'important' from 'serious'
> severity 898786 important
Bug #898786 [src:icingaweb2] icingaweb2: [RC]  embedded copy of normalize.css
Severity set to 'important' from 'serious'
> severity 898785 important
Bug #898785 [src:granafa] granafa: [RC]  embedded copy of normalize.css
Warning: Unknown package 'src:granafa'
Severity set to 'important' from 'serious'
Warning: Unknown package 'src:granafa'
> severity 898782 important
Bug #898782 [src:glances] glances: [RC]  embedded copy of normalize.css
Severity set to 'important' from 'serious'
> severity 898779 important
Bug #898779 [src:cargo-doc] src:cargo-doc: [RC] embedded code copy of 
node-normalize.css
Warning: Unknown package 'src:cargo-doc'
Severity set to 'important' from 'serious'
Warning: Unknown package 'src:cargo-doc'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
898779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898779
898782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898782
898785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898785
898786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898786
898787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898787
898788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898788
898789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898789
898790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898790
898791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898791
898792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898792
898793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898793
898794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898794
898795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898795
898796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#898788: libreoffice-help-common: [RC] embedded copy of normalize.css

[Rene Engelhard]

Hi,

On Tue, May 15, 2018 at 10:56:25PM +0200, Rene Engelhard wrote:
> Which package? Don't see a package shipping it?

#898789 suggests libjs-normalize.css. Which doesn't exist.

Regards,

Rene

Bug#898788: libreoffice-help-common: [RC] embedded copy of normalize.css

[Rene Engelhard]

severity 898788 important
retitle 898788 libreoffice-help-common: embedded copy of normalize.css
thanks

Hi,

On Tue, May 15, 2018 at 10:39:44PM +0200, Bastien ROUCARIÈS wrote:
> Package: libreoffice-help-common
> Version: 1:6.1.0~beta1~git20180507-1
> Severity: serious
> Justification: Policy 4.13

Debian policy 4.13 says "should", not "must". I'd agree with you if this
was non-free, it isn't, though:

rene@frodo:~/data/git/LibreOffice/master/helpcontent2$ head -n 1
./help3xsl/normalize.css
/*! normalize.css v8.0.0 | MIT License |
 * github.com/necolas/normalize.css */

And why are the other ones not RC buggy? Why is chromium
not RC buggy? Why not texlive including poppler? etc.

This is at most important.

> This package include embedded copy of normalize.css
> /usr/share/libreoffice/help/normalize.css
> 
> Please use the package instead to use local copy

Which package? Don't see a package shipping it?

# apt-file search normalize.css
cargo-doc: /usr/share/doc/cargo-doc/doc/normalize.css
coffeescript-doc:
/usr/share/doc/coffeescript/html/annotated-source/public/stylesheets/normalize.css
glances:
/usr/lib/python3/dist-packages/glances/outputs/static/css/normalize.css
grafana-data: /usr/share/grafana/missing-sources/normalize.css
grafana-data: /usr/share/grafana/missing-sources/normalize.css.url
icingaweb2: /usr/share/icingaweb2/public/css/vendor/normalize.css
ldap-account-manager:
/usr/share/ldap-account-manager/style/responsive/105_normalize.css
libreoffice-help-common: /usr/share/libreoffice/help/normalize.css
r-cran-shiny:
/usr/lib/R/site-library/shiny/www/shared/ionrangeslider/css/normalize.css
recon-ng: /usr/share/recon-ng/recon/core/web/static/normalize.css
rust-doc: /usr/share/doc/rust-doc/html/normalize.css
rust-src: /usr/src/rustc-1.24.1/src/librustdoc/html/static/normalize.css
rust-src: /usr/src/rustc-1.25.0/src/librustdoc/html/static/normalize.css
sympa:
/usr/share/sympa/static_content/external/foundation/css/normalize.cs

I don't see a package shipping it?

Regards,

Rene

Bug#898796: thunderbird: [RC] embedded copy of normalize.css

[Bastien ROUCARIÈS]

Package: thunderbird
Severity: serious
Justification: Policy 4.13

This package include embedded copy of normalize.css
mozilla/browser/base/content/aboutaccounts/normalize.css

Please use the package libjs-normalize.css instead to use local copy

Thanks 

Bastien

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

Bug#898795: firefox-esr: [RC] embedded copy of normalize.css

[Bastien ROUCARIÈS]

Package: firefox-esr
Severity: serious
Justification: Policy 4.13

This package include embedded copy of normalize.css
browser/base/content/aboutaccounts/normalize.css
(aka about:accounts)


Please use the package libjs-normalize.css instead to use local copy

Thanks 

Bastien

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

Bug#898794: wims-module: [RC] embedded copy of normalize.css

[Bastien ROUCARIÈS]

Package: wims-modules
Version: 1:4.15b~dfsg1-11
Severity: serious
Justification: Policy 4.13

This package include embedded copy of normalize.css
 /var/lib/wims/public_html/scripts/js/bower_components/normalize.min.css


Please use the package libjs-normalize.css instead to use local copy

Thanks 

Bastien

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

Bug#898793: sympa: [RC] embedded copy of normalize.css

[Bastien ROUCARIÈS]

Package: sympa
Version: 6.2.32~dfsg-1
Severity: serious
Justification: Policy 4.13

This package include embedded copy of normalize.css
/usr/share/sympa/static_content/external/foundation/css/normalize.css


Please use the package libjs-normalize.css instead to use local copy

Thanks 

Bastien

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

Bug#898792: rust-src: [RC] embedded copy of normalize.css

[Bastien ROUCARIÈS]

Package: rust-src
Version: 1.24.1+dfsg1-1
Severity: serious
Justification: Policy 4.13

This package include embedded copy of normalize.css
/usr/src/rustc-1.24.1/src/librustdoc/html/static/normalize.css

Please use the package libjs-normalize.css instead to use local copy

Thanks 

Bastien

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

Bug#898791: rust-doc: [RC] embedded copy of normalize.css

[Bastien ROUCARIÈS]

Package: rust-doc
Version: 1.24.1+dfsg1-1
Severity: serious
Justification: Policy 4.13

This package include embedded copy of normalize.css
/usr/share/doc/rust-doc/html/normalize.css

Please use the package libjs-normalize.css instead to use local copy

Thanks 

Bastien

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

Bug#898790: r-cran-shiny: [RC] embedded copy of normalize.css

[Bastien ROUCARIÈS]

Package: r-cran-shiny
Version: 1.0.5+dfsg-4
Severity: serious
Justification: Policy 4.13

This package include embedded copy of normalize.css
/usr/share/libreoffice/help/normalize.css

Please use the package libjs-normalize.css instead to use local copy

Thanks 

Bastien

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

Bug#898789: recon-ng: [RC] embedded copy of normalize.css

[Bastien ROUCARIÈS]

Package: recon-ng
Version: 4.9.3-1
Severity: serious
Justification: Policy 4.13

This package include embedded copy of normalize.css
/usr/share/recon-ng/recon/core/web/static/normalize.css


Please use the package libjs-normalize.css instead to use local copy

Thanks 

Bastien

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

Bug#898760: Bug #898760 in icu4j marked as pending

[ebourg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/icu4j/commit/c752232e8bdd6ef69363f56b9ae72ae0c9ba25b6


Fixed the build failure with Java 10 (Closes: #898760)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/898760

Processed: Bug #898760 in icu4j marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #898760 [src:icu4j] icu4j: FTBFS with Java 10
Added tag(s) pending.

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

Bug#898788: libreoffice-help-common: [RC] embedded copy of normalize.css

[Bastien ROUCARIÈS]

Package: libreoffice-help-common
Version: 1:6.1.0~beta1~git20180507-1
Severity: serious
Justification: Policy 4.13

This package include embedded copy of normalize.css
/usr/share/libreoffice/help/normalize.css

Please use the package instead to use local copy

Thanks 

Bastien

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

Bug#898787: ldap-account-manager: [RC] embedded copy of normalize.css

[Bastien ROUCARIÈS]

Package: src:ldap-account-manager
Version: 6.3-1
Severity: serious
Justification: Policy 4.13

This package include embedded copy of normalize.css
/usr/share/ldap-account-manager/style/responsive/105_normalize.css

Please use the package instead to use local copy

Thanks 

Bastien

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

Bug#898785: granafa: [RC] embedded copy of normalize.css

[Bastien ROUCARIÈS]

Package: src:granafa
Version: 2.6.0+dfsg-3
Severity: serious
Justification: Policy 4.13

This package include embedded copy of normalize.css
The files:
grafana-data: /usr/share/grafana/missing-sources/normalize.css
grafana-data: /usr/share/grafana/missing-sources/normalize.css.url

(possibly included in some html file)

Please use the package (maybe using suggest) instead to use local copy

Thanks 

Bastien

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

Bug#898786: icingaweb2: [RC] embedded copy of normalize.css

[Bastien ROUCARIÈS]

Package: src:icingaweb2
Version: 2.5.3-1
Severity: serious
Justification: Policy 4.13

This package include embedded copy of normalize.css
icingaweb2: /usr/share/icingaweb2/public/css/vendor/normalize.css

Please use the package (maybe using suggest) instead to use local copy

Thanks 

Bastien

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

Bug#898630: enigmail: efail attack against enigmail

[David Sanders]

I think this bug applies to Thunderbird as well as Enigmail and both 
packages need urgent updates.


The Enigmail part can be corrected by updating to version 2.0.3, but the 
user will still be vulnerable until a new version of Thunderbird is 
released and pushed out to users. Long term the openPGP standard needs 
to be updated to address the issue.


Could the maintainers of Enigmail take for action updating to the 
already released 2.0.3? And forwarding the bug to Thunderbird for 
further action?


Thanks,
David

On Mon, 14 May 2018 15:15:26 +0200 Yves-Alexis Perez  
wrote:

> Package: enigmail
> Severity: grave
> Tags: security
> Justification: user security hole
>
> Hi Daniel,
>
> in case you haven't already heard about it by now, a vulnerability has
> been published against S/MIME and PGP/MIME in various email clients,
> including thunderbird (and enigmail).
>
> I'm unsure if CVE-2017-17688 (OpenPGP CFB gadget attacks) applies
> to Thunderbird/enigmail or only GnuPG, but the PGP/MIME vulnerability
> does apply to enigmail.
>
> Some fixes apparently went in to enigmail 2.0.0 but I'm unsure which of
> them yet, so any pointers appreciated (for example by closing with the
> correct version number :).
>
> I think we'll likely want to release a DSA too.
>
> Regards,
> --
> Yves-Alexis

Bug#898782: glances: [RC] embedded copy of normalize.css

[Bastien ROUCARIÈS]

Package: src:glances
Version: 2.11.1-3
Severity: serious
Justification: Policy 4.13

The files:
glances: /usr/lib/python3/dist-packages/glances/outputs/static/css/normalize.css


Please use the package (maybe using suggest) instead to use local copy

Thanks 

Bastien

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

Bug#895035: osc: crashes with memory corruption when using new libssl1.1

[Simon McVittie]

Control: tags -1 + patch fixed-upstream

On Wed, 02 May 2018 at 17:19:20 +0100, Simon McVittie wrote:
> * https://github.com/openSUSE/osc/issues/398
> 
>   """
>   - m2crypto 0.29 does no SSL_free(...) (which is fixed in 0.30)
> (that's why this bug is not triggered with m2crypto 0.29)
>   - there's a "bug" in ssl_update_cache cache in openssl 1.1.0h (in
> short: the session is not put in the session cache...)
>   - osc currently relies on the fact that the session is in the session
> cache (or more precisely, that there are at least two references to
> the SSL_SESSION), which is, of course, a bug in osc
>   """

The osc crash appears to be fixable by the patch that was applied
upstream (see attached Disable-ssl-session-resumption.patch). If I'm
understanding the commit message correctly, strictly speaking this was
already an osc bug (it made bad assumptions about session caching),
but the regression in openssl changed its impact from "might crash in
rare cases" to "crashes every time".

> * https://github.com/openssl/openssl/pull/5967
> 
>   """
>   Commit d316cdc introduced some extra
>   checks into the session-cache update procedure, intended to prevent
>   the caching of sessions whose resumption would lead to a handshake
>   failure, since if the server is authenticating the client, there needs to
>   be an application-set "session id context" to match up to the authentication
>   context. While that change is effective for its stated purpose, there
>   was also some collatoral damage introduced along with the fix -- clients
>   that set SSL_VERIFY_PEER are not expected to set an sid_ctx, and so
>   their usage of session caching was erroneously denied.
> 
>   Fix the scope of the original commit by limiting it to only acting
>   when the SSL is a server SSL.
>   """

Sorry for the delay in testing this.

Applying openssl commit c84f7d9251446bf76c179bf5da31f25944f4b975
(and reverting osc to the version that crashes) seems
to be another way to address this. See attached
c84f7d9251446bf76c179bf5da31f25944f4b975.patch.

Regards,
smcv
From: Marcus Huewe 
Date: Tue, 8 May 2018 14:23:08 +0200
Subject: Disable ssl session resumption

The old code could potentially yield to a use-after-free situation,
which results in UB. For this, consider the following scenario, where
osc performs several HTTPS requests (assumption: the server supports
ssl session resumption):

- HTTPS Request 1:
  * a new SSL *s connection is established, which also creates a new
SSL_SESSION *ss => ss->references == 1
  * once the handshake is done, the ss is put into the session cache
(see ssl_update_cache) => ss->references == 2
  - osc saves the session ss in a class variable
  - s is SSL_free()d, which calls SSL_SESSION_free => ss->references == 1

- HTTPS Request 2:
  * setup a new SSL *s connection that reuses the saved session ss
=> ss->references == 2
  * once the handshake is done, ssl_update_cache is called, which is a
NOP, because s->hit == 1 (that is, the session was resumed)
  * osc saves the session ss in a class variable
  * s is SSL_free()d, which calls SSL_SESSION_free => ss->references == 1

...

> 2 hours later (see tls1_default_timeout)

...

- HTTPS Request 256:
  * setup a new SSL *s connection that reuses the saved session ss
=> ss->references == 2
  * once the handshake is done, ssl_update_cache is called, but is
_no_ NOP anymore
  * ssl_update_cache flushes the session cache (this is done every
255/256 (depending on the way we count) connections) => ss is
SSL_SESSION_free()d => ss->references == 1
  * osc saves the session ss in a class variable
  * s is SSL_free()d, which calls SSL_SESSION_free:
since ss->references == 1, ss is eventually free()d

- HTTPS Request 257:
  * setup a new SSL *s connection that reuses the saved session ss

Since ss does not exist anymore, the remaining program execution is UB.

(Note: SSL_free(...) is _NOT_ called, if M2Crypto 0.29 is used.
M2Crypto 0.30 calls SSL_free(...) again.)

Due to a bug in OpenSSL_1_1_0h (see openssl commit 8e405776858) the
scenario from above can be triggered with exactly 2 HTTPS requests (the
SSL_SESSION is not cached, because we configured SSL_VERIFY_PEER, but
no sid_ctx was set). This is fixed in openssl commit c4fa1f7fc01.

In order to reliably reuse a session, we probably need to listen to the
session cache changes. Such callbacks could be registered via
SSL_CTX_sess_set_new_cb and/or SSL_CTX_sess_set_remove_cb, but both
functions are not provided by M2Crypto. Another idea is to directly utilize
the session cache, but this also has to be implemented in M2Crypto first.
Yet another approach is to retrieve the session via SSL_get1_session, which
increases the session's refcnt, but this also needs to be implemented in
M2Crypto first (if we choose to use this approach, we also have to make
sure that we eventually free the session manually...).

Fixes: #398 ("SIGSEGV on \"osc commit\"")
Origin: upstream,

Processed: Re: Bug#895035: osc: crashes with memory corruption when using new libssl1.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch fixed-upstream
Bug #895035 [osc] osc: crashes with memory corruption when using new libssl1.1
Added tag(s) fixed-upstream and patch.

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

Bug#898780: coffeescript-doc: [RC] embedded code copy of node-normalize.css

[Bastien ROUCARIÈS]

Package: src:coffeescript-doc
Version: 1.12.7~dfsg-3
Severity: serious
Justification: Policy 4.13

The files:
coffeescript-doc: /usr/share/doc/coffeescript/html/annotated-source/public/
stylesheets/normalize.css
Are embedded copy of node-normalize.css.

Please use the package (maybe using suggest) instead to use local copy

Thanks 

Bastien



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

Bug#898779: src:cargo-doc: [RC] embedded code copy of node-normalize.css

[Bastien Roucariès]

Package: src:cargo-doc
Version: 0.25.0-2
Severity: serious
Justification: Policy 4.13

The files:
cargo-doc: /usr/share/doc/cargo-doc/doc/normalize.css
cargo-doc: /usr/share/doc/cargo-doc/doc/stylesheets/normalize.css

Are embedded copy of node-normalize.css.

Please use the package (maybe using suggest) instead to use local copy

Thanks

Bastien

Bug#898776: numpy.arange does not work on several platforms

[Ole Streicher]

Package: python3-numpy
Version: 1:1.14.3-2
Severity: serious
Control: affects -1 src:astropy
Control: forwarded -1 https://github.com/numpy/numpy/issues/11103

Hi,

On several platforms, numpy.arange does not work properly with 128 bit.
For example on arm64:

Python 3.6.5 (default, May 11 2018, 13:30:17)
[GCC 7.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
>>> numpy.arange(3)
array([0, 1, 2])
>>> numpy.arange(3, dtype=numpy.float128)
array([0., 0., 0.], dtype=float128)

This (or similar) happens on arm64, ppc64el, s390x, riscv64, and others.

This causes an FTBFS for astropy on these platforms, therefore the severity.

Best regards

Ole

Processed: numpy.arange does not work on several platforms

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:astropy
Bug #898776 [python3-numpy] numpy.arange does not work on several platforms
Added indication that 898776 affects src:astropy
> forwarded -1 https://github.com/numpy/numpy/issues/11103
Bug #898776 [python3-numpy] numpy.arange does not work on several platforms
Set Bug forwarded-to-address to 'https://github.com/numpy/numpy/issues/11103'.

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

Bug#898738: debootstrap fails when specifying components

[Cyril Brulebois]

Luca Falavigna  (2018-05-15):
> found 898738 1.0.97
> thanks

Right, I knew I was forgetting something. That happens when I spend too
much time debugging and adjusting the write-up as I go. Thanks for
fixing.

> 2018-05-15 21:19 GMT+02:00 Cyril Brulebois :
> > The issue seems to be the non-free Packages file being checked
> > against the checksum of the contrib one (both sha256 checksum and
> > size in fact), so that can't work.
> 
> Thanks for checking! Indeed the problem can be reproduced from 1.0.97
> (hence adjusting found correctly). I'll have a look in the next few
> days as well.

I think I've found the issue. At least partly reverting the commit
makes retrieving/validating indices work again, possibly because
un-local-izing names was a bad idea? (I took all hunks from the commit
that touched the download_release_indices function. Not everything is
needed I guess.)

See attached patch, against the offending commit. It doesn't apply to
master as-is because of the by-hash addition.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- a/functions
+++ b/functions
@@ -610,10 +617,13 @@ download_release_sig () {
 }
 
 download_release_indices () {
-	local m1="${MIRRORS%% *}"
-	local inreldest="$TARGET/$($DLDEST rel "$SUITE" "$m1" "dists/$SUITE/InRelease")"
-	local reldest="$TARGET/$($DLDEST rel "$SUITE" "$m1" "dists/$SUITE/Release")"
-	local relsigdest="$TARGET/$($DLDEST rel "$SUITE" "$m1" "dists/$SUITE/Release.gpg")"
+	local m1 inreldest reldest relsigdest totalpkgs \
+	  subpath xzi bz2i gzi normi i ext \
+	  donepkgs pkgdest
+	m1="${MIRRORS%% *}"
+	inreldest="$TARGET/$($DLDEST rel "$SUITE" "$m1" "dists/$SUITE/InRelease")"
+	reldest="$TARGET/$($DLDEST rel "$SUITE" "$m1" "dists/$SUITE/Release")"
+	relsigdest="$TARGET/$($DLDEST rel "$SUITE" "$m1" "dists/$SUITE/Release.gpg")"
 
 	download_release_sig "$m1" "$inreldest" "$reldest" "$relsigdest"
 
@@ -621,14 +631,13 @@ download_release_indices () {
 
 	extract_release_components "$reldest"
 
-	local totalpkgs=0
+	totalpkgs=0
 	for c in $COMPONENTS; do
-		local subpath="$c/binary-$ARCH/Packages"
-		local xzi="`get_release_checksum "$reldest" "$subpath.xz"`"
-		local bz2i="`get_release_checksum "$reldest" "$subpath.bz2"`"
-		local gzi="`get_release_checksum "$reldest" "$subpath.gz"`"
-		local normi="`get_release_checksum "$reldest" "$subpath"`"
-		local i=
+		subpath="$c/binary-$ARCH/Packages"
+		xzi="$(get_release_checksum "$reldest" "$subpath.xz")"
+		bz2i="$(get_release_checksum "$reldest" "$subpath.bz2")"
+		gzi="$(get_release_checksum "$reldest" "$subpath.gz")"
+		normi="$(get_release_checksum "$reldest" "$subpath")"
 		if [ "$normi" != "" ]; then
 			i="$normi"
 		elif in_path bunzip2 && [ "$bz2i" != "" ]; then
@@ -639,25 +648,22 @@ download_release_indices () {
 			i="$gzi"
 		fi
 		if [ "$i" != "" ]; then
-			totalpkgs="$(( $totalpkgs + ${i#* } ))"
+			totalpkgs=$(( $totalpkgs + ${i#* } ))
 		else
 			mv "$reldest" "$reldest.malformed"
 			error 1 MISSINGRELENTRY "Invalid Release file, no entry for %s" "$subpath"
 		fi
 	done
 
-	local donepkgs=0
-	local pkgdest
+	donepkgs=0
 	progress 0 $totalpkgs DOWNPKGS "Downloading Packages files"
 	for c in $COMPONENTS; do
-		local subpath="$c/binary-$ARCH/Packages"
-		local path="dists/$SUITE/$subpath"
-		local xzi="`get_release_checksum "$reldest" "$subpath.xz"`"
-		local bz2i="`get_release_checksum "$reldest" "$subpath.bz2"`"
-		local gzi="`get_release_checksum "$reldest" "$subpath.gz"`"
-		local normi="`get_release_checksum "$reldest" "$subpath"`"
-		local ext=
-		local i=
+		subpath="$c/binary-$ARCH/Packages"
+		path="dists/$SUITE/$subpath"
+		xzi="$(get_release_checksum "$reldest" "$subpath.xz")"
+		bz2i="$(get_release_checksum "$reldest" "$subpath.bz2")"
+		gzi="$(get_release_checksum "$reldest" "$subpath.gz")"
+		normi="$(get_release_checksum "$reldest" "$subpath")"
 		if [ "$normi" != "" ]; then
 			ext="$ext $normi ."
 			i="$normi"
@@ -674,7 +680,7 @@ download_release_indices () {
 			ext="$ext $gzi gz"
 			i="${i:-$gzi}"
 		fi
-		progress_next "$(($donepkgs + ${i#* }))"
+		progress_next $(($donepkgs + ${i#* }))
 		for m in $MIRRORS; do
 			pkgdest="$TARGET/$($DLDEST pkg "$SUITE" "$c" "$ARCH" "$m" "$path")"
 			if get "$m/$path" "$pkgdest" $ext; then break; fi
@@ -682,7 +688,7 @@ download_release_indices () {
 		if [ ! -f "$pkgdest" ]; then
 			error 1 COULDNTDL "Couldn't download %s" "$m/$path"
 		fi
-		donepkgs="$(($donepkgs + ${i#* }))"
+		donepkgs=$(($donepkgs + ${i#* }))
 		progress $donepkgs $totalpkgs DOWNPKGS "Downloading Packages files"
 	done
 }


signature.asc
Description: PGP signature

Bug#898738: debootstrap fails when specifying components

[Luca Falavigna]

found 898738 1.0.97
thanks



Hi,

2018-05-15 21:19 GMT+02:00 Cyril Brulebois :
> The issue seems to be the non-free Packages file being checked against
> the checksum of the contrib one (both sha256 checksum and size in fact),
> so that can't work.

Thanks for checking! Indeed the problem can be reproduced from 1.0.97
(hence adjusting found correctly). I'll have a look in the next few
days as well.

-- 
Cheers,
Luca

Processed: Re: Bug#898738: debootstrap fails when specifying components

[Debian Bug Tracking System]

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

> found 898738 1.0.97
Bug #898738 [src:debootstrap] debootstrap fails when specifying components
Marked as found in versions debootstrap/1.0.97.
> thanks
Stopping processing here.

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

Processed: tagging 898665

[Debian Bug Tracking System]

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

> tags 898665 - buster sid
Bug #898665 [installation-guide] [installation-guide] change "Alioth" and "svn" 
to "Salsa" and "git"
Removed tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: adjust version and severity

[Debian Bug Tracking System]

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

> # not a new issue
> found 898658 6.1+20180210-1
Bug #898658 [libncursesw6] f-irc gets SEGV with TERM=xterm-256color
Marked as found in versions ncurses/6.1+20180210-1.
> # and can be worked around
> severity 898658 important
Bug #898658 [libncursesw6] f-irc gets SEGV with TERM=xterm-256color
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#898738: debootstrap fails when specifying components

[Cyril Brulebois]

Hi,

Luca Falavigna  (2018-05-15):
> Source: debootstrap
> Version: 1.0.98
> Severity: serious

Thanks for the heads-up.

> debootstrap fails when specifying components on command line:
> 
> # debootstrap --components=main,contrib,non-free unstable unstable
> http://deb.debian.org/debian
> I: Target architecture can be executed
> I: Checking Release signature
> I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010)
> I: Validating Packages
> I: Retrieving Packages
> I: Retrieving Packages
> I: Validating Packages
> W: Retrying failed download of
> http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages
> I: Retrieving Packages
> I: Validating Packages
> W: Retrying failed download of
> http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages
> I: Retrieving Packages
> I: Validating Packages
> W: Retrying failed download of
> http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages
> I: Retrieving Packages
> I: Validating Packages
> W: Retrying failed download of
> http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages
> I: Retrieving Packages
> I: Validating Packages
> W: Retrying failed download of
> http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages.gz
> W: 
> http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages.gz
> was corrupt
> I: Retrieving Packages
> E: Couldn't download
> http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages

This is likely due to recent changes to add by-hash support, which makes
such errors fatal? (Low on time, can't really check right away.)

Anyway, before, we could see such errors but they wouldn't be fatal.
I've tracked this with the test case you suggested and with “git
bisect”, to this commit:
| commit d45ca044136553c9ef9ca194e8b48668aa6e694f
| Author: Hideki Yamane 
| Date:   Mon Apr 9 22:10:59 2018 +0900
| 
| Clean up with shellcheck


The following patch highlights the issue:
| kibi@wodi:~/debian-installer/packages/debootstrap$ git diff
| diff --git a/functions b/functions
| index 3fc7a7c..847f853 100644
| --- a/functions
| +++ b/functions
| @@ -358,6 +358,7 @@ get () {
| fi
| if [ "$checksum" != "" ]; then
| info VALIDATING "Validating %s %s" 
"$displayname" "$versionname"
| +   info TOTO "verify_checksum $dest2 $checksum 
$siz"
| if verify_checksum "$dest2" "$checksum" 
"$siz"; then
| checksum=""
| fi

See the output:
| I: Retrieving InRelease 
| I: Checking Release signature
| I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010)
| I: Retrieving Packages 
| I: Validating Packages 
| I: verify_checksum 
/scratch/unstable/var/lib/apt/lists/partial/debootstrap.invalid_dists_unstable_main_binary-amd64_Packages.xz
 51576750586b79c6814c968a610c2f15fb3288bf569fe2f7ce86cadaaa7e5a8b 8063628
| I: Retrieving Packages 
| I: Validating Packages 
| I: verify_checksum 
/scratch/unstable/var/lib/apt/lists/partial/debootstrap.invalid_dists_unstable_contrib_binary-amd64_Packages.xz
 78dd59c641a2fec36aef9017a1f0cbbb150a6f3b151024b7fa4aba473a6bada0 63160
| I: Retrieving Packages 
| I: Validating Packages 
| I: verify_checksum 
/scratch/unstable/var/lib/apt/lists/partial/debootstrap.invalid_dists_unstable_non-free_binary-amd64_Packages.xz
 78dd59c641a2fec36aef9017a1f0cbbb150a6f3b151024b7fa4aba473a6bada0 63160
| W: Retrying failed download of 
http://ftp.fr.debian.org/debian/dists/unstable/non-free/binary-amd64/Packages.xz
| I: Retrieving Packages 
| I: Validating Packages 
| I: verify_checksum 
/scratch/unstable/var/lib/apt/lists/partial/debootstrap.invalid_dists_unstable_non-free_binary-amd64_Packages.xz
 78dd59c641a2fec36aef9017a1f0cbbb150a6f3b151024b7fa4aba473a6bada0 63160
| W: Retrying failed download of 
http://ftp.fr.debian.org/debian/dists/unstable/non-free/binary-amd64/Packages.xz
[repeated]

The issue seems to be the non-free Packages file being checked against
the checksum of the contrib one (both sha256 checksum and size in fact),
so that can't work.

Going back to the previous commit (73b0bd2ce6), with the same one-line
patch:
| I: Retrieving InRelease 
| I: Checking Release signature
| I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010)
| I: Retrieving Packages 
| I: Validating Packages 
| I: verify_checksum 
/scratch/unstable/var/lib/apt/lists/partial/debootstrap.invalid_dists_unstable_main_binary-amd64_Packages.xz
 51576750586b79c6814c968a610c2f15fb3288bf569fe2f7ce86cadaaa7e5a8b 8063628
| I: Retrieving Packages 
| I: Validating Packages 
| I: verify_checksum 
/scratch/unstable/var/lib/apt/lists/partial/debootstrap.invalid_dists_unstable_contrib_binary-amd64_Packages.xz
 78dd59c641a2fec36aef9017a1f0cbbb150a6f3b151024b7fa4aba473a6bada0 63160
| I: Retrieving Packa

Processed: tagging 898665

[Debian Bug Tracking System]

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

> tags 898665 + buster sid
Bug #898665 [installation-guide] [installation-guide] change "Alioth" and "svn" 
to "Salsa" and "git"
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#888908: marked as done (using ICU 60.2: Failed test: basic10_4.m:166 ... negativeFormat used for -ve number)

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 19:05:54 +
with message-id 
and subject line Bug#888908: fixed in gnustep-base 1.25.1-3
has caused the Debian Bug report #888908,
regarding using ICU 60.2: Failed test: basic10_4.m:166 ... negativeFormat used 
for -ve number
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
888908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnustep-base
Version: 1.25.1-1
Tags: sid buster
Severity: important

using ICU 60.2 I see the following test failing:

Failed test: basic10_4.m:166 ... negativeFormat used for -ve number

Seems to be architecture independent.
--- End Message ---
--- Begin Message ---
Source: gnustep-base
Source-Version: 1.25.1-3

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

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

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

Debian distribution maintenance software
pp.
Yavor Doganov  (supplier of updated gnustep-base package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 May 2018 15:55:27 +0300
Source: gnustep-base
Binary: gnustep-base-common gnustep-base-runtime libgnustep-base1.25 
libgnustep-base-dev gnustep-base-doc
Architecture: source all amd64
Version: 1.25.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNUstep maintainers 

Changed-By: Yavor Doganov 
Description:
 gnustep-base-common - GNUstep Base library - common files
 gnustep-base-doc - Documentation for the GNUstep Base Library
 gnustep-base-runtime - GNUstep Base library - daemons and tools
 libgnustep-base-dev - GNUstep Base header files and development libraries
 libgnustep-base1.25 - GNUstep Base library
Closes: 888908
Changes:
 gnustep-base (1.25.1-3) unstable; urgency=medium
 .
   * debian/patches/icu-60.patch: Fix FTBFS on big-endian architectures
 (really closes: #888908).
   * debian/templates/control.m4 (Standards-Version): Bump to 4.1.4; no
 changes required.
   * debian/control: Regenerate.
Checksums-Sha1:
 33b790346ac2030d9d42cdcae2d4a08549dc65eb 2927 gnustep-base_1.25.1-3.dsc
 893ed659f993d4230ab6da69952f8e0c51baeb27 114836 
gnustep-base_1.25.1-3.debian.tar.xz
 5d1dadc12845bf714d7e6bf4b8a7278bed7622c2 267928 
gnustep-base-common_1.25.1-3_all.deb
 26867553400f8acd03ea579b04be05a0aa3d3219 1512804 
gnustep-base-doc_1.25.1-3_all.deb
 d3d0381624331e3be85a4e98bd13781be1d5c381 402852 
gnustep-base-runtime-dbgsym_1.25.1-3_amd64.deb
 5b4c8eb882bccd02a3baf1d8ea32cb964ba42981 417164 
gnustep-base-runtime_1.25.1-3_amd64.deb
 69eb976e208cbadcdf3b6c45e986a43f1ff18b20 12620 
gnustep-base_1.25.1-3_amd64.buildinfo
 046d829e5b539cd410a589d5b8b70bb3317dd6e8 1910452 
libgnustep-base-dev_1.25.1-3_amd64.deb
 dfb511c67354fa65dd6c0278762b767055cde3a3 3232680 
libgnustep-base1.25-dbgsym_1.25.1-3_amd64.deb
 0bb73a7920b586f163ea48d16f7635df6e1de1eb 1511036 
libgnustep-base1.25_1.25.1-3_amd64.deb
Checksums-Sha256:
 f8284af232a801ad59531f8cad70077dfb1dd7c1dccda2f4c9a7f34a194903d5 2927 
gnustep-base_1.25.1-3.dsc
 25a8ce247d7550d62954ddd6e5a6157288a64db0f7694613dbe15be7e8df1b57 114836 
gnustep-base_1.25.1-3.debian.tar.xz
 2a7a73147b77e3a2f79903ceb888ef7131ec68db4758aa6598f242f716bb0488 267928 
gnustep-base-common_1.25.1-3_all.deb
 51628a86fdd5240c50d56b8e13234c121057362639dd5cb0750f4b8718a94bdc 1512804 
gnustep-base-doc_1.25.1-3_all.deb
 298edbef3125d5d7b8c2ad1b955d3b52c970daa09485546e359474522ba182e0 402852 
gnustep-base-runtime-dbgsym_1.25.1-3_amd64.deb
 33f8b7f391ac0c3485c8b1ad27da69506a9e65a463809a6ea7f1d0d2d85c2235 417164 
gnustep-base-runtime_1.25.1-3_amd64.deb
 cef98c051ed61a5c9812f332913e472509b2b79f94e440e0a186d08e807c2a26 12620 
gnustep-base_1.25.1-3_amd64.buildinfo
 e5ea6abd8783a791c72ed2f1c5b0a956ef5e0c8da23ceb49c39bcc60792a9364 1910452 
libgnustep-base-dev_1.25.1-3_amd64.deb
 94d2c30809d1e877f88a7596d0358373c184e1e2bd7c40044b533e081fdbe4cd 3232680 
libgnustep-base1.25-dbgsym_1.25.1-3_amd64.deb
 d1fa4346c3d635cc8daf8f9e472a678f267c7585562f2a8747ff8213bf55a668 1511036 
libgnustep-base1.25_1.25.1-3_amd64.deb
Files:
 ffad1cbcf9b7caafde48745001fd210a 2927 

Processed: Move to the package where the bug seems to be

[Debian Bug Tracking System]

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

> reassign 898658 libncursesw6 6.1+20180210-3
Bug #898658 [f-irc] f-irc gets SEGV with TERM=xterm-256color
Bug reassigned from package 'f-irc' to 'libncursesw6'.
No longer marked as found in versions f-irc/1.36-1.
Ignoring request to alter fixed versions of bug #898658 to the same values 
previously set
Bug #898658 [libncursesw6] f-irc gets SEGV with TERM=xterm-256color
Marked as found in versions ncurses/6.1+20180210-3.
> affects 898658 f-irc
Bug #898658 [libncursesw6] f-irc gets SEGV with TERM=xterm-256color
Added indication that 898658 affects f-irc
> thanks
Stopping processing here.

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

Bug#897097: marked as done (uwsgi must drop libapache2-mod-proxy-uwsgi{,-dbg})

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 21:52:41 +0300
with message-id <20180515185241.GB25554@localhost>
and subject line Close the correct bug for the removal of 
libapache2-mod-proxy-uwsgi{,-dbg} from src:uwsgi
has caused the Debian Bug report #897097,
regarding uwsgi must drop libapache2-mod-proxy-uwsgi{,-dbg}
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
897097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uwsgi
Version: 2.0.15-10.4
Severity: serious
Control: affects -1 libapache2-mod-proxy-uwsgi-dbg

libapache2-mod-proxy-uwsgi is now a transitional package
in src:apache2.
--- End Message ---
--- Begin Message ---
Version: 2.0.15-11

cu
Adrian

-- 

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

Processed: Re: Bug#898760: icu4j: FTBFS with Java 10

[Debian Bug Tracking System]

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

> user debian-j...@lists.debian.org
Setting user to debian-j...@lists.debian.org (was ebo...@apache.org).
> usertag 898760 + default-java10
There were no usertags set.
Usertags are now: default-java10.
> tags 898760 + sid buster
Bug #898760 [src:icu4j] icu4j: FTBFS with Java 10
Added tag(s) buster and sid.
>
End of message, stopping processing here.

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

Bug#898658: f-irc gets SEGV with TERM=xterm-256color

[Sven Joachim]

CC'ing ncurses maintainer, it looks like the library might be at fault
here.

On 2018-05-15 03:05 +0900, nozzy123no...@gmail.com wrote:

> Package: f-irc
> Version: 1.36-1+b3
> Severity: serious
>
> Dear Maintainer,
>
>  This version of f-irc always gets SEGV when TERM environmental
> variable set to xterm-256color ,which is default under gnome-terminal.
>
>  However, when I set TERM  to xterm,vt100 or kterm,f-irc seems to work
> well.
>
>  Does anyone fix this problem?

No fix, but at least a backtrace in gdb:

,
| Program received signal SIGSEGV, Segmentation fault.
| _nc_pair_content 
(sp=0x5659daf0, pair=7353, f=0xd1a4, b=0xd1a8) at 
../../ncurses/base/lib_color.c:942
| 942 int bg = BACK_OF(sp->_color_pairs[pair]);
| (gdb) bt full
| #0  _nc_pair_content (sp=0x5659daf0, pair=7353, f=0xd1a4, b=0xd1a8) 
at ../../ncurses/base/lib_color.c:942
| fg = 
| bg = 
| result = 1449406468
| #1  0xf7f713de in pair_content_sp (sp=0x5659daf0, pair=7353, f=0xd216, 
b=0xd218)
| at ../../ncurses/base/lib_color.c:972
| my_f = 0
| my_b = 0
| rc = 
| #2  0xf7f7147a in pair_content (pair=7353, f=0xd216, b=0xd218) at 
../../ncurses/base/lib_color.c:984
| No locals.
| #3  0x5657b88b in init_nick_colorpairs () at nickcolor.c:90
| pair = 7353
| cr = 680
| cg = 0
| cb = 680
| loop = 5
| fg = 0
| bg = 0
| fg_r = 255
| fg_g = 255
| fg_b = 255
| bg_r = 0
| bg_g = 0
| bg_b = 0
| #4  0x5655d7b3 in main (argc=1, argv=0xd394) at main.c:670
| config_loaded = -1
`

To investigate the issue more closely, I set a breakpoint on
pair_content and used the "cont" command with some increments until I
got to the critical value of pair=7353.  Then I single-stepped through
the code:

,
| Breakpoint 1, pair_content (pair=7353, f=0xd216, b=0xd218) at 
../../ncurses/base/lib_color.c:983
| 983 {
| (gdb) step
| 984 return NCURSES_SP_NAME(pair_content) (CURRENT_SCREEN, pair, f, b);
| (gdb) step
| pair_content_sp (sp=0x5659daf0, pair=7353, f=0xd216, b=0xd218) at 
../../ncurses/base/lib_color.c:970
| 970 {
| (gdb) step
| 972 int rc = _nc_pair_content(SP_PARM, pair, &my_f, &my_b);
| (gdb) step
| 970 {
| (gdb) step
| 972 int rc = _nc_pair_content(SP_PARM, pair, &my_f, &my_b);
| (gdb) step
| _nc_pair_content (sp=0x5659daf0, pair=7353, f=0xd1a4, b=0xd1a8) at 
../../ncurses/base/lib_color.c:929
| 929 {
| (gdb) step
| 938 if (!ValidPair(sp, pair)) {
| (gdb) step
| 941 int fg = FORE_OF(sp->_color_pairs[pair]);
| (gdb) step
| 951 if (f)
| (gdb) step
| 941 int fg = FORE_OF(sp->_color_pairs[pair]);
| (gdb) step
| 942 int bg = BACK_OF(sp->_color_pairs[pair]);
| (gdb) step
| 
| Program received signal SIGSEGV, Segmentation fault.
| _nc_pair_content 
(sp=0x5659daf0, pair=7353, f=0xd1a4, b=0xd1a8) at 
../../ncurses/base/lib_color.c:942
| 942 int bg = BACK_OF(sp->_color_pairs[pair]);
`

What is sp->_color_pairs[pair] ?  It is not accessible:

,
| (gdb) print sp->_color_pairs[pair]
| Cannot access memory at address 0x56643004
| (gdb) print sp->_color_pairs[pair-1]
| Cannot access memory at address 0x56643000
| (gdb) print sp->_color_pairs[pair-2]
| $1 = {fg = 0, bg = 0, mode = 0, prev = 0, next = 0}
`

So it seems that the ncurses library did not allocate enough memory to
hold all the color pairs in sp->_color_pairs, resulting in the eventual
heap buffer overflow.

That's how far I have tracked the issue, hopefully Thomas Dickey can
investigate it further and even provide a fix.

Cheers,
   Sven

Bug#898757: musescore: crash on startup

[Thorsten Glaser]

severity 898757 normal
tags 898757 + moreinfo
thanks

Hi Rob,

>After displaying the splash screen, Musescore stops

while I understand your frustration this works for others,
so I’m downgrading the severity. I’m even using it on an
i386 system the same as you are.

Please do the following: install gdb-minimal (unless you
already have gdb installed) and musescore-dbgsym, then run
it from the command line as:

$ gdb /usr/bin/musescore
[…]
(gdb) r
[…]

If you then, at the point of crash, get a “(gdb)” prompt
back, type the command “bt” and press Enter.

Please do paste the complete output.

Thanks,
//mirabilos
-- 
15:39⎜«mika:#grml» mira|AO: "mit XFree86® wär’ das nicht passiert" - muhaha
15:48⎜ also warum machen die xorg Jungs eigentlich alles
kaputt? :)15:49⎜ thkoehler: weil sie als Kinder nie den
gebauten Turm selber umschmeissen durften?  -- ~/.Xmodmap wonders…

Bug#898577: marked as done (pytables: FTBFS - 56 tests fail with 'TypeError: a float is required')

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 18:36:00 +
with message-id 
and subject line Bug#898577: fixed in pytables 3.4.3-2
has caused the Debian Bug report #898577,
regarding pytables: FTBFS - 56 tests fail with 'TypeError: a float is required'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
898577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytables
Version: 3.4.3-1
Severity: serious
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

pytables FTBFS on unstable during the tests step. 56 tests fail with errors 
like:

==
ERROR: test00_description (tables.tests.test_tables.RecArrayTwoWriteTestCase)
Checking table description and descriptive fields.
- --
Traceback (most recent call last):
  File 
"/<>/build/lib.linux-x86_64-2.7/tables/tests/test_tables.py", line 
138, in setUp
self.populateFile()
  File 
"/<>/build/lib.linux-x86_64-2.7/tables/tests/test_tables.py", line 
213, in populateFile
self.initRecArray()
  File 
"/<>/build/lib.linux-x86_64-2.7/tables/tests/test_tables.py", line 
207, in initRecArray
shape=self.expectedrows)
  File "/usr/lib/python2.7/dist-packages/numpy/core/records.py", line 847, in 
array
return fromrecords(obj, dtype=dtype, shape=shape, **kwds)
  File "/usr/lib/python2.7/dist-packages/numpy/core/records.py", line 708, in 
fromrecords
retval = sb.array(recList, dtype=descr)
TypeError: a float is required

Regards,

_g.


- -- System Information:
Distributor ID: PureOS
Description:PureOS GNU/Linux 8
Release:8
Codename:   green
Architecture: x86_64

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlr4msIACgkQ7+hsbH/+
z4MfyggApCe7IWvb2JQUOwpcyVH85TEqaZLZXTRDg4SuC/7WkQfbMj5A+Mh56QXP
BbQPRlIVzgR0jcrC+6VyLHqiKIAsaR4EUuLxP86rcWF4LFrn9I8tqjM/9OCv6zM0
XzSXQfcLXQuulqo01GYk0zB/Yt1PMod3hi76zLUui9UphTNZVx40/v+6iAkmCYko
9YAI0P7DQOtlBmSvePl/KawaiS8TUgeZv/pw9la5CAznlnOD22Pt2uowh7qm8uAO
FtRlt4eG/2/IL8gqS9hdPeeb+8iePOQVKnHDtf3iipvwBucFFsMa5FzEqcZRwLEk
2UdXhOimaAMrihNc6Lzq/T8OuJggLg==
=2eVK
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: pytables
Source-Version: 3.4.3-2

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

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

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

Debian distribution maintenance software
pp.
Antonio Valentino  (supplier of updated pytables 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 14 May 2018 22:21:42 +
Source: pytables
Binary: python-tables python-tables-lib python-tables-dbg python3-tables 
python3-tables-lib python3-tables-dbg python-tables-doc python-tables-data
Architecture: source all amd64
Version: 3.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Antonio Valentino 
Description:
 python-tables - hierarchical database for Python based on HDF5
 python-tables-data - hierarchical database for Python based on HDF5 - test data
 python-tables-dbg - hierarchical database for Python based on HDF5 (debug 
extension)
 python-tables-doc - hierarchical database for Python based on HDF5 - 
documentation
 python-tables-lib - hierarchical database for Python based on HDF5 (extension)
 python3-tables - hierarchical database for Python3 based on HDF5
 python3-tables-dbg - hierarchical database for Python 3 based on HDF5 (debug 
extension
 python3-tables-lib - hierarchical database for Python3 based on HDF5 
(extension)
Closes: 898577
Changes:
 pytables (3.4.3-2) unstable; urgency=medium
 .
   * debian/patches
 - new 0005-Compatibility-with-NumPy-1.14.3.patch (Closes: #898577)
   * debian control
 - drop 

Processed: Re: Bug#898757: musescore: crash on startup

[Debian Bug Tracking System]

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

> severity 898757 normal
Bug #898757 [musescore] musescore: crash on startup
Severity set to 'normal' from 'grave'
> tags 898757 + moreinfo
Bug #898757 [musescore] musescore: crash on startup
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#898768: gnome-twitch: Segfault everytime you try to watch a stream

[Éter]

Package: gnome-twitch
Version: 0.4.1-2
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

Gnome-twitch segfaults everytime you try to watch a stream because of a change
on twitch API.

Upstream patch: https://github.com/dengelt/gnome-
twitch/commit/54b210db90e9698da57bed9ceb5119c6b6e5b686

Upstream bug report: https://github.com/vinszent/gnome-twitch/issues/356

Regards!



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

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

Versions of packages gnome-twitch depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.28.0-2
ii  libc62.27-3
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk-3-0   3.22.30-1
ii  libjson-glib-1.0-0   1.4.2-4
ii  libpeas-1.0-01.22.0-2
ii  libsoup2.4-1 2.62.2-1
ii  libwebkit2gtk-4.0-37 2.20.2-1+b1
ii  libx11-6 2:1.6.5-1

Versions of packages gnome-twitch recommends:
ii  gnome-twitch-player-backend-gstreamer-cairo0.4.1-2
ii  gnome-twitch-player-backend-gstreamer-clutter  0.4.1-2
ii  gnome-twitch-player-backend-gstreamer-opengl   0.4.1-2
ii  gnome-twitch-player-backend-mpv-opengl 0.4.1-2

gnome-twitch suggests no packages.

-- no debconf information

Bug#898767: linux-image-4.16.0-1-amd64: (temporary, unreliable) hang on boot since upgrade to 4.16

[Ralf Jung]

Package: src:linux
Version: 4.16.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

since the upgrade to kerkenl 4.16, the system does not boot reliably any more.
Instead, most of the time, it hangs showing the following messages:

[2.639465] nouveau :01:00.0: bus: MMIO read of  FAULT at 022554 
[ IBUS ]
[2.645516] nouveau :01:00.0: bus: MMIO read of  FAULT at 10ac08 
[ IBUS ]
[2.719537] i915 :00:02.0: firmware: failed to load 
i915/skl_dmc_ver1_27.bin (-2)
[2.719539] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware

The two nouveau messages are old (they already showed with the 4.15 kernel), but
not so the ones about the firmware.  I have firmware-linux installed.

Sometimes this hang seems to not end (I have waited >30sec) and I have to reset
the machine. Other times (like just now), after a few seconds, the kernel
continues to boot.

Kind regards,
Ralf

-- Package-specific info:
** Version:
Linux version 4.16.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-17)) #1 SMP Debian 4.16.5-1 (2018-04-29)

** Command line:
BOOT_IMAGE=/vmlinuz-4.16.0-1-amd64 root=/dev/mapper/vg-root ro quiet splash

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

** Kernel log:
[   46.673568] iwlwifi :02:00.0: loaded firmware version 31.532993.0 
op_mode iwlmvm
[   46.694233] pstore: Registered efi as persistent store backend
[   46.719185] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   46.719294] input: ThinkPad Extra Buttons as 
/devices/platform/thinkpad_acpi/input/input9
[   46.721032] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b52c)
[   46.723565] uvcvideo: Failed to initialize entity for entity 6
[   46.723566] uvcvideo: Failed to register entites (-22).
[   46.723618] input: Integrated Camera: Integrated C as 
/devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0/input/input11
[   46.725324] Bluetooth: Core ver 2.22
[   46.725333] NET: Registered protocol family 31
[   46.725333] Bluetooth: HCI device and connection manager initialized
[   46.725336] Bluetooth: HCI socket layer initialized
[   46.725338] Bluetooth: L2CAP socket layer initialized
[   46.725343] Bluetooth: SCO socket layer initialized
[   46.726976] usbcore: registered new interface driver uvcvideo
[   46.726976] USB Video Class driver (1.1.1)
[   46.730442] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 
8260, REV=0x208
[   46.734238] usbcore: registered new interface driver btusb
[   46.734757] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[   46.741784] Bluetooth: hci0: Device revision is 5
[   46.741785] Bluetooth: hci0: Secure boot is enabled
[   46.741786] Bluetooth: hci0: OTP lock is enabled
[   46.741786] Bluetooth: hci0: API lock is enabled
[   46.741787] Bluetooth: hci0: Debug lock is disabled
[   46.741788] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   46.741961] intel_rapl: Found RAPL domain package
[   46.741962] intel_rapl: Found RAPL domain core
[   46.741963] intel_rapl: Found RAPL domain uncore
[   46.741964] intel_rapl: Found RAPL domain dram
[   46.744394] bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-11-5.sfi
[   46.744400] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[   46.756577] Adding 3903484k swap on /dev/mapper/vg-swap.  Priority:-2 
extents:1 across:3903484k SSFS
[   46.762767] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC298: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   46.762769] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   46.762771] snd_hda_codec_realtek hdaudioC0D0:hp_outs=2 
(0x17/0x21/0x0/0x0/0x0)
[   46.762772] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   46.762773] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   46.762775] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
[   46.762776] snd_hda_codec_realtek hdaudioC0D0:  Dock Mic=0x19
[   46.762778] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[   46.805235] iwlwifi :02:00.0: base HW address: e4:a4:71:65:d2:a4
[   46.828321] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1f.3/sound/card0/input12
[   46.829036] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input13
[   46.829866] input: HDA Intel PCH Dock Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input14
[   46.829915] input: HDA Intel PCH Dock Headphone as 
/devices/pci:00/:00:1f.3/sound/card0/input15
[   46.830007] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1f.3/sound/card0/input16
[   46.881465] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[   46.881627] thermal thermal_zone3: failed to read out thermal zone (-61)
[   46.883846] iwlwifi :02:00.0 wlp2s0: renamed from wlan0
[   47.016727] EXT4-fs (sda2): mounted filesystem with ordered data mode. O

Bug#898384: marked as done (terminology: focus weirdness in 1.2.0)

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 17:49:47 +
with message-id 
and subject line Bug#898384: fixed in terminology 1.2.1-1
has caused the Debian Bug report #898384,
regarding terminology: focus weirdness in 1.2.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
898384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: terminology
Version: 1.2.0-1
Severity: serious

terminology 1.2.0 easily gets stuck in a state where it doesn't receive
keyboard events.  This is triggered by switching keyboard focus away from
terminology, and then back.

Upstream discussion:
 https://sourceforge.net/p/enlightenment/mailman/message/36314861/
 <20180510202714.ga10...@nabu.fau.re>

Ross
--- End Message ---
--- Begin Message ---
Source: terminology
Source-Version: 1.2.1-1

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

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

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

Debian distribution maintenance software
pp.
Ross Vandegrift  (supplier of updated terminology package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 14 May 2018 19:49:50 -0700
Source: terminology
Binary: terminology terminology-data
Architecture: source
Version: 1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Pkg-e Team 
Changed-By: Ross Vandegrift 
Closes: 898384
Description: 
 terminology-data - Enlightenment efl based terminal emulator data
 terminology - Enlightenment efl based terminal emulator
Changes:
 terminology (1.2.1-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #898384)
Checksums-Sha1: 
 eba87300f9519d62c34e93d725a2ae19ca1d105d 2111 terminology_1.2.1-1.dsc
 2033670f37559205b5624d3de6d6c1ab9546b491 4858528 terminology_1.2.1.orig.tar.xz
 51a595fa662f02a71bb5ea8eb59ac2033ffe9c71 9744 terminology_1.2.1-1.debian.tar.xz
Checksums-Sha256: 
 3c5dfc24ce1318f317b9aeefd8e3f823245f4c3e863abffbe55d5095643df660 2111 
terminology_1.2.1-1.dsc
 ac8673a129ed78ef669a8c04e7a136f5ca95226ce5ef375a451421bac41828c6 4858528 
terminology_1.2.1.orig.tar.xz
 0ca0d804e9d16a704b61f05123aff10ddfe37d4aea4386d77049a30d7d2b01c2 9744 
terminology_1.2.1-1.debian.tar.xz
Files: 
 414f95b6f85333b9fa826d727976ca00 2111 x11 optional terminology_1.2.1-1.dsc
 fd3970b3f5383ac34f7f7105d92e74ea 4858528 x11 optional 
terminology_1.2.1.orig.tar.xz
 8699061537b925f09a335a5164f58ba3 9744 x11 optional 
terminology_1.2.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAlr7GSYACgkQpU8BhUOC
FISxvg/8DRL4nqAv5g/P+1ugpX+IqIYyWEZgD8guympli9AnoEPIeYJ+Rjn44xEM
JZLvaYK16OR51QsJKfYyruL2f2AmoYDBOekgdHcs6uye02Hw1ICiEb6p+3BLE1c8
8RFUMlpuc6kBKS3mRl+Yq81yCrZ+9qlV5Eg1nEgSkb5LaxZbgf+T3hDgkgAMvc7Q
Ty01054+RNgP/5823xgJqc9Tc3nTa0THFFQ5Hdr0lwSHdKSi5fnbHvU9KYuODqFd
9Vc+maeuC3A0SFgc/Ivz/8xjjgTut7buL42/9qSxjmxpsfkMNwa8L9hdDGAe31Mv
HFBFgfWzfDCo0Lx/r0Qp/xROJjYaYHdzUc3rSwOBE0hxNJo14oWvk3V9YRqzpsGT
N0mn/6/C+5RJY2D6oDNF40CH/CksQTvylzYY8bI6RnQLPHZ/8yj2Fd/eQ2TGXlKQ
Yg4x7PGyHH8XSV4vEZsx7QjGqeih8UMg+JB9I7aQNF4mVCgk7zW/Ygdx/xXQgA53
Efr/No7qyWMl8h4faOiYEt5BzKUhIhz2tInJJYZQIiF8q7Ly4KgjptQJkcg2Abti
lDLja34Hd4D4UdM37b6kl9IFbSUradsSjsUP6xa/GSYfsktsF/j94LX/gOUCyhUy
Wrl8P1SWzI5kY1mTuGb37chANonsHPMr6WgqyBSgidRLC74W8XM=
=vcHT
-END PGP SIGNATURE End Message ---

Bug#898764: smuxi: FTBFS: dh_clideps: Error: Missing shlibs entry: libncursesw.so.5 or ncurses for: smuxi-frontend-stfl.exe!

[Sven Joachim]

Source: smuxi
Version: 1.0.7-2
Severity: serious

Your package FTBFS in unstable, here is the tail of my build log:

,
|   DLL map: 'ncurses' target: 'libncursesw.so.5'
| dh_clideps: Error: Missing shlibs entry: libncursesw.so.5 or ncurses for: 
smuxi-frontend-stfl.exe!
| Use of uninitialized value $newpkgref in pattern match (m//) at 
/usr/bin/dh_clideps line 508,  line 2.
|   Resolved moduleref via DLL map: ncurses to: libncursesw.so.5
|   Looking for libncursesw.so.5 at libncursesw.so.5
|   Checking smuxi for libncursesw.so.5
|   Looking for libncursesw.so.5 at libncursesw.so.5
|   Checking smuxi-engine for libncursesw.so.5
|   Looking for libncursesw.so.5 at libncursesw.so.5
|   Checking smuxi-frontend-gnome for libncursesw.so.5
|   Looking for libncursesw.so.5 at libncursesw.so.5
|   Checking smuxi-frontend-stfl for libncursesw.so.5
|   Looking for libncursesw.so.5 at libncursesw.so.5
|   Loading clideps-override for smuxi-frontend-stfl...
| Use of uninitialized value $pkgref in concatenation (.) or string at 
/usr/bin/dh_clideps line 539.
| Use of uninitialized value $newpkgref in concatenation (.) or string at 
/usr/bin/dh_clideps line 539.
|   resolved pkgref:  to depends: 
|   Resolved moduleref via DLL map: stfl to: libstfl.so.0
|   Loading clideps-override for smuxi-frontend-stfl...
|   resolved pkgref: libstfl0 to depends: libstfl0
|   running CLI parser command: LANG=C MONO_PATH= MONO_GAC_PREFIX=  
MONO_GAC_PREFIX=$MONO_GAC_PREFIX:debian/smuxi-frontend-stfl/usr 
/usr/bin/monodis --assemblyref smuxi-frontend-stfl.exe 2>&1 > 
/tmp/dh_clideps.sxBP
|   Loading clideps-override for smuxi-frontend-stfl...
|   resolved pkgref: liblog4net1.2-cil (>= 1.2.10) to depends: 
liblog4net1.2-cil (>= 1.2.10)
|   Loading clideps-override for smuxi-frontend-stfl...
|   resolved pkgref: libmono-corlib4.5-cil (>= 4.6.1.3) to depends: 
libmono-corlib4.5-cil (>= 4.6.1.3)
|   Loading clideps-override for smuxi-frontend-stfl...
|   resolved pkgref: libmono-system4.0-cil (>= 4.6.1.3) to depends: 
libmono-system4.0-cil (>= 4.6.1.3)
|   Loading clideps-override for smuxi-frontend-stfl...
|   resolved pkgref: libmono-posix4.0-cil (>= 4.6.1.3) to depends: 
libmono-posix4.0-cil (>= 4.6.1.3)
|   Loading clideps-override for smuxi-frontend-stfl...
|   resolved pkgref: libmono-system-core4.0-cil (>= 4.6.1.3) to depends: 
libmono-system-core4.0-cil (>= 4.6.1.3)
|   (grep -a -s -v cli:Depends debian/smuxi-frontend-stfl.substvars; echo 
"cli:Depends=mono-runtime (>= 3.0~), liblog4net1.2-cil (>= 1.2.10), 
libmono-corlib4.5-cil (>= 4.6.1.3), libmono-posix4.0-cil (>= 4.6.1.3), 
libmono-system-core4.0-cil (>= 4.6.1.3), libmono-system4.0-cil (>= 4.6.1.3), 
libstfl0") > debian/smuxi-frontend-stfl.substvars.new
|   mv debian/smuxi-frontend-stfl.substvars.new 
debian/smuxi-frontend-stfl.substvars
|   grep -a -s -v '^cli:Recommends=' debian/smuxi-frontend-stfl.substvars > 
debian/smuxi-frontend-stfl.substvars.new || true
|   mv debian/smuxi-frontend-stfl.substvars.new 
debian/smuxi-frontend-stfl.substvars
|   grep -a -s -v '^cli:Suggests=' debian/smuxi-frontend-stfl.substvars > 
debian/smuxi-frontend-stfl.substvars.new || true
| dh_clideps: Error: unresolvable module references or missing shlibs entries, 
please check above errors!
|   mv debian/smuxi-frontend-stfl.substvars.new 
debian/smuxi-frontend-stfl.substvars
| debian/rules:32: recipe for target 'override_dh_clideps' failed
| make[1]: *** [override_dh_clideps] Error 255
| make[1]: Leaving directory '/tmp/smuxi-1.0.7'
| debian/rules:53: recipe for target 'binary' failed
| make: *** [binary] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2
`

The reason is that libncursesw.so.5 is no longer guaranteed to be found
on the build system, as it is being superseded by libncursesw.so.6 (see
#894049).  And src/Frontend-STFL/smuxi-frontend-stfl.exe.config contains
the following line:




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

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

Bug#898760: icu4j: FTBFS with Java 10

[Emmanuel Bourg]

Source: icu4j
Severity: serious

icu4j fails to build with Java 10 due to a buggy JDK detection logic:

  Buildfile: /build/1st/icu4j-60.2/build.xml
  
  BUILD FAILED
  /build/1st/icu4j-60.2/build.xml:125: The JDK version is too old or unknown.

It also fails to compile due to changes to the doclet API:

  @compile:
   [echo] build-local: ../../main/shared/../../build-local.properties
   [echo] --- java compiler arguments 
   [echo] source dir: /build/1st/icu4j-60.2/icu4j/tools/build/src
   [echo] output dir: /build/1st/icu4j-60.2/icu4j/tools/build/out/bin
   [echo] bootclasspath:
   [echo] classpath:  /usr/lib/jvm/default-java/lib/tools.jar
   [echo] source: 1.6
   [echo] target: 1.6
   [echo] debug:  on
   [echo] encoding:   UTF-8
   [echo] compiler arg:   -Xlint:none
   [echo] 
  [mkdir] Created dir: /build/1st/icu4j-60.2/icu4j/tools/build/out/bin
  [javac] Using javac -source 1.6 is no longer supported, switching to 1.7
  [javac] Using javac -target 1.6 is no longer supported, switching to 1.7
  [javac] Compiling 17 source files to 
/build/1st/icu4j-60.2/icu4j/tools/build/out/bin
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTaglet.java:17:
 error: package com.sun.tools.doclets.internal.toolkit.taglets does not exist
  [javac] import com.sun.tools.doclets.internal.toolkit.taglets.Taglet;
  [javac]  ^
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:13:
 error: package com.sun.tools.doclets.formats.html.markup does not exist
  [javac] import com.sun.tools.doclets.formats.html.markup.RawHtml;
  [javac] ^
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:14:
 error: package com.sun.tools.doclets.internal.toolkit does not exist
  [javac] import com.sun.tools.doclets.internal.toolkit.Content;
  [javac]  ^
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:15:
 error: package com.sun.tools.doclets.internal.toolkit.taglets does not exist
  [javac] import com.sun.tools.doclets.internal.toolkit.taglets.Taglet;
  [javac]  ^
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:16:
 error: package com.sun.tools.doclets.internal.toolkit.taglets does not exist
  [javac] import 
com.sun.tools.doclets.internal.toolkit.taglets.TagletWriter;
  [javac]  ^
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:24:
 error: cannot find symbol
  [javac] public abstract class ICUTagletAdapter implements Taglet {
  [javac]   ^
  [javac]   symbol: class Taglet
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTaglet.java:19:
 error: cannot find symbol
  [javac] public abstract class ICUTaglet extends ICUTagletAdapter 
implements Taglet {
  [javac]   
  ^
  [javac]   symbol: class Taglet
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:30:
 error: cannot find symbol
  [javac] public Content getTagletOutput(Tag tag, TagletWriter writer)
  [javac] ^
  [javac]   symbol:   class TagletWriter
  [javac]   location: class ICUTagletAdapter
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:30:
 error: cannot find symbol
  [javac] public Content getTagletOutput(Tag tag, TagletWriter writer)
  [javac]^
  [javac]   symbol:   class Content
  [javac]   location: class ICUTagletAdapter
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:43:
 error: cannot find symbol
  [javac] public Content getTagletOutput(Doc holder, TagletWriter 
writer)
  [javac]^
  [javac]   symbol:   class TagletWriter
  [javac]   location: class ICUTagletAdapter
  [javac] 
/build/1st/icu4j-60.2/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUTagletAdapter.java:43:
 error: cannot find symbol
  [javac] public Content getTagletOutput(Doc holder, TagletWriter 
writer)
  [javac]^
  [javac]   symbol:   class Content
  [javac]   location: class ICUTagletAdapter
   

Bug#898734: marked as done (ocaml-rope: FTBFS with dune/1.0~beta20-1)

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 17:22:06 +
with message-id 
and subject line Bug#898734: fixed in ocaml-rope 0.6.1-1
has caused the Debian Bug report #898734,
regarding ocaml-rope: FTBFS with dune/1.0~beta20-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
898734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898734
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocaml-rope
Version: 0.6-1
Severity: serious
Justification: FTBFS

Hi,

ocaml-rope fails to build using the new version of dune/jbuilder
due to dh_missing complaining about uninstalled files.

I will prepare a new upload momentarily.


Best,

  nicoo

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

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: ocaml-rope
Source-Version: 0.6.1-1

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

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

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

Debian distribution maintenance software
pp.
Nicolas Braud-Santoni  (supplier of updated 
ocaml-rope package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 15 May 2018 17:28:19 +0200
Source: ocaml-rope
Binary: librope-ocaml librope-ocaml-dev
Architecture: source amd64
Version: 0.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Nicolas Braud-Santoni 
Description:
 librope-ocaml - ropes ("heavyweight strings") for OCaml (Runtime library)
 librope-ocaml-dev - ropes ("heavyweight strings") for OCaml (Development 
package)
Closes: 898734
Changes:
 ocaml-rope (0.6.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version (2017-12-25)
 Closes: #898734
 .
   * Update debian/watch
   * debian/control: Update Vcs-* and Homepage URLs
   * debian/rules: Put dh_missing list in not-installed
   * Switch to debhelper 11
   * Declare compliance with policy v4.1.4.
 No change required.
Checksums-Sha1:
 54a08c2146488dd1a79ac959bb3d28c267dddf21 2180 ocaml-rope_0.6.1-1.dsc
 34668e6721b841598d17bf229ebde0f26d559472 289191 ocaml-rope_0.6.1.orig.tar.bz2
 262f9f52ff4d268f6504be7709866c5d66a8913c 3200 ocaml-rope_0.6.1-1.debian.tar.xz
 44d2ab8987e37aaa4dafa2a0a8948b4c9bb75d45 9092 
librope-ocaml-dbgsym_0.6.1-1_amd64.deb
 18469914bcbccc287e7953e9d2aead25f4f1312b 202568 
librope-ocaml-dev_0.6.1-1_amd64.deb
 45f32e23f0d432ad267184af9187b991d7d0f609 85736 librope-ocaml_0.6.1-1_amd64.deb
 7ced04494683b1687643a1c5b1add162e48980a4 6879 
ocaml-rope_0.6.1-1_amd64.buildinfo
Checksums-Sha256:
 b791f8abd691cf8cd1887ae52db906169ecd8dce851d4cdd22489eb89315ffed 2180 
ocaml-rope_0.6.1-1.dsc
 62f676f5e5843403b17ee06b2d509995cf8b0d0121725206054bfef0251210ff 289191 
ocaml-rope_0.6.1.orig.tar.bz2
 fb8e1d2f76168390eb79812b30d4d10e39ac22919055f53619fc56617b81b0dc 3200 
ocaml-rope_0.6.1-1.debian.tar.xz
 c696b67cdcbd5e35796b3763dd71090b39c46f698d69cb84c0a3c2bf0547522f 9092 
librope-ocaml-dbgsym_0.6.1-1_amd64.deb
 fb95cdb82d09bea2d40d44a14b2e57286b9498056412517dcabb2575389ded68 202568 
librope-ocaml-dev_0.6.1-1_amd64.deb
 c495bc6cd28f0092c8708cd6400a0e681868746a985ba9263ee172e702aa35b4 85736 
librope-ocaml_0.6.1-1_amd64.deb
 143b8bb43c1581c18b6bc5ad136d016757531c3a9314e5c7b76a7f105e519bf5 6879 
ocaml-rope_0.6.1-1_amd64.buildinfo
Files:
 0c119ada05ae910d8051efb30a30dcbd 2180 ocaml optional ocaml-rope_0.6.1-1.dsc
 b1a34f8a645ee153005565be87e9dbc7 289191 ocaml optional 
ocaml-rope_0.6.1.orig.tar.bz2
 ee377fd679fa0ecbc1707234b45274f6 3200 ocaml optional 
ocaml-rope_0.6.1-1.debian.tar.xz
 69c49fef6e1cb6dbc6fc45c6289b474e 9092 debug optional 
librope-ocaml-dbgsym_0.6.1-1_amd64.deb
 ceaf4839c4124e966d56573bd9527aab 202568 ocaml optional 

Bug#898542: marked as done (qt4-x11: FTBFS with libicu60)

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 16:56:46 +
with message-id 
and subject line Bug#898542: fixed in qt4-x11 4:4.8.7+dfsg-17
has caused the Debian Bug report #898542,
regarding qt4-x11: FTBFS with libicu60
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
898542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qt4-x11
Version: 4:4.8.7+dfsg-16
Severity: serious
Justification: fails to build from source

Hi!

qt4-x11 fails to build from source due to incompatible changes in libicu60:

g++ -c -include .pch/release-shared/QtCore -g -O2 
-fdebug-prefix-map=/<>/qt4-x11-4.8.7+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++98 
-I/usr/include/freetype2 -pthr
ead -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -O2 
-fvisibility=hidden -fvisibility-inlines-hidden -Wall -W -D_REENTRANT -fPIC 
-DQT_SHARED -DQT_BUILD_CORE_LIB -DQT_NO_USING_NAMESPACE -DQT_NO_CAST_TO_ASCII 
-DQT_A
SCII_CAST_WARNINGS -DQT3_SUPPORT -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER 
-DELF_INTERPRETER=\"/lib64/ld-linux-x86-64.so.2\" -DQLIBRARYINFO_EPOCROOT 
-DQT_USE_ICU -DHB_EXPORT=Q_CORE_EXPORT -DQT_NO_DEBUG -DQT_HAVE_MMX 
-DQT_HAVE_3DNOW -DQT_HA
VE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_HAVE_SSE3 -DQT_HAVE_SSSE3 
-DQT_HAVE_SSE4_1 -DQT_HAVE_SSE4_2 -DQT_HAVE_AVX -D_LARGEFILE64_SOURCE 
-D_LARGEFILE_SOURCE -I../../mkspecs/linux-g++-64 -I. -I../../include 
-I../../include/QtCore -I.rc
c/release-shared -Iglobal -I../../tools/shared -I../3rdparty/harfbuzz/src 
-I../3rdparty/md5 -I../3rdparty/md4 -I.moc/release-shared -o 
.obj/release-shared/qlocale_icu.o tools/qlocale_icu.cpp
In file included from /usr/include/unicode/uversion.h:30:0,
 from tools/qlocale_icu.cpp:46:
/usr/include/unicode/umachine.h:347:13: error: 'char16_t' does not name a type; 
did you mean 'wchar_t'?
 typedef char16_t UChar;
 ^~~~
 wchar_t
In file included from tools/qlocale_icu.cpp:46:0:
/usr/include/unicode/uversion.h:167:55: error: 'UChar' does not name a type; 
did you mean 'QChar'?
 u_versionFromUString(UVersionInfo versionArray, const UChar *versionString);
   ^
   QChar
In file included from /usr/include/unicode/unorm.h:24:0,
 from /usr/include/unicode/ucol.h:17,
 from tools/qlocale_icu.cpp:47:
/usr/include/unicode/uiter.h:594:44: error: 'UChar' does not name a type; did 
you mean 'QChar'?
 uiter_setString(UCharIterator *iter, const UChar *s, int32_t length);
^
QChar

I first discovered this issue on m68k [1], but also made a test build on amd64
to make sure this bug is not an artifact.

I unfortunately don't have a patch yet to address this issue.

Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=qt4-x11&arch=m68k&ver=4%3A4.8.7%2Bdfsg-16&stamp=1526192657&raw=0

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Source: qt4-x11
Source-Version: 4:4.8.7+dfsg-17

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

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

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
qt4-x11 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 May 2018 13:24:10 -0300
Source: qt4-x11
Binary: libqtcore4 qtcore4-l10n libqtgui4 libqt4-network libqt4-opengl 
libqt4-script libqt4-scripttools libqt4-sql libqt4-sql-ibase libqt4-sql-mysql 
libqt4-sql-odbc libqt4-sql-psql libqt4-sql-sqlite libqt4-sql-sqlite2 
libqt4-sql-tds libqt4-svg libqt4-xml libqt4-xmlpatterns libqt4-dbus libqtdbus4 
libqt4-qt3support libqt4-designer l

Bug#898757: musescore: crash on startup

[Rob van den Berg]

Package: musescore
Version: 2.2.1+dfsg1-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After displaying the splash screen, Musescore stops

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.14.0-3-rt-686-pae (SMP w/1 CPU core; PREEMPT)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), 
LANGUAGE=nl_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages musescore depends on:
ii  desktop-file-utils   0.23-3
ii  libasound2   1.1.3-5
ii  libc62.27-3
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.1.0-1
ii  libportaudio219.6.0-1
ii  libportmidi0 1:217-6
ii  libpulse011.1-5
ii  libqt5core5a 5.10.1+dfsg-6
ii  libqt5gui5   5.10.1+dfsg-6
ii  libqt5help5  5.10.1-2
ii  libqt5network5   5.10.1+dfsg-6
ii  libqt5printsupport5  5.10.1+dfsg-6
ii  libqt5qml5   5.10.1-4
ii  libqt5quick5 5.10.1-4
ii  libqt5sql5-sqlite5.10.1+dfsg-6
ii  libqt5svg5   5.10.1-2
ii  libqt5webkit55.212.0~alpha2-9
ii  libqt5widgets5   5.10.1+dfsg-6
ii  libqt5xml5   5.10.1+dfsg-6
ii  libqt5xmlpatterns5   5.10.1-2
ii  libsndfile1  1.0.28-4
ii  libstdc++6   8.1.0-1
ii  libvorbisfile3   1.3.6-1
ii  musescore-common 2.2.1+dfsg1-4
ii  qml-module-qtquick-controls  5.10.1-2
ii  qml-module-qtquick-dialogs   5.10.1-2
ii  qml-module-qtquick-layouts   5.10.1-4
ii  qml-module-qtquick2  5.10.1-4
ii  shared-mime-info 1.9-2
ii  xdg-utils1.1.2-2
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages musescore recommends:
ii  libmp3lame0   3.100-2+b1
ii  pulseaudio-utils  11.1-5

Versions of packages musescore suggests:
ii  fluid-soundfont-gm  3.1-5.1
ii  timgm6mb-soundfont  1.3-2

-- no debconf information

Bug#898755: node-miller-rabin: FTBFS and flaky autopkgtests

[Graham Inggs]

Source: node-miller-rabin
Version: 4.0.1-1
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: flaky

Hi Maintainer

Since 2017-12-28, node-miller-rabin has FTBFS in unstable [1] with the 
following error:


  0 passing (2s)
  1 failing

  1) Miller-Rabin
   should test number for primality:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, 
ensure "done()" is called; if returning a Promise, ensure it resolves.

  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)

The same test is run during autopkgtests and often fails, especially on 
the slower architectures which are tested in Ubuntu, but not in Debian.


I believe this is another example of the unreliable timing in tests 
being discussed in #853035.


I was able to work around the problem in Ubuntu by increasing the test 
timeout to 8000ms (4000ms was not sufficient on armhf) as per the patch 
below:


--- a/test/api-test.js
+++ b/test/api-test.js
@@ -4,6 +4,7 @@

 describe('Miller-Rabin', function() {
   it('should test number for primality', function() {
+this.timeout(8000);
 assert(!mr.test(new bn(221)));
 assert(mr.test(new bn(257)));

Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/history/amd64/node-miller-rabin.html

Bug#898754: libcatalyst-controller-html-formfu-perl: FTBFS: Can't locate MooseX/Attribute/FormFuChained.pm in @INC

[Niko Tyni]

Source: libcatalyst-controller-html-formfu-perl
Version: 2.02-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest
Tags: fixed-upstream
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=125102

As noticed by ci.debian.net, this package fails its test suite on current
sid, making it fail to build from source.

 https://ci.debian.net/packages/libc/libcatalyst-controller-html-formfu-perl/

It looks like libhtml-formfu-perl_2.06-1 dropped the
MooseX::Attribute::FormFuChained module, but at least this package is
still using it. This seems to be fixed upstream in 2.03.

Once this is fixed, please also make libhtml-formfu-perl Break the earlier
versions so that partial upgrades cannot end up with broken combinations.
I hope this is also be enough to inform the britney autopkgtest integration
that the packages need to migrate together.

(I see libhtml-formfu-model-dbic-perl was similarly affected but is already
fixed; please consider adding a Breaks entry for that one too if applicable.)

>From my build log:

  [error] Caught exception in TestApp::Controller::Token->form "Can't locate 
MooseX/Attribute/FormFuChained.pm in @INC (you may need to install the 
MooseX::Attribute::FormFuChained module) (@INC contains: t/lib 
/<>/blib/lib /<>/blib/arch /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/<>/blib/lib/HTML/FormFu/Plugin/RequestToken.pm line 8.
  BEGIN failed--compilation aborted at 
/<>/blib/lib/HTML/FormFu/Plugin/RequestToken.pm line 8.
  Compilation failed in require at /usr/share/perl5/HTML/FormFu/Util.pm line 
390.
   at /usr/share/perl5/HTML/FormFu/Role/FormAndElementMethods.pm line 235."
  
  #   Failed test 'GET http://localhost/token/form'
  #   at t/01basic-token.t line 11.
  # 500
  # Internal Server Error
  
  #   Failed test 'Found form'
  #   at t/01basic-token.t line 15.
  Can't call method "find_input" on an undefined value at t/01basic-token.t 
line 17.
  # Tests were run but no plan was declared and done_testing() was not seen.
  # Looks like your test exited with 255 just after 2.
  t/01basic-token.t  
  not ok 1 - GET http://localhost/token/form
  not ok 2 - Found form
  Dubious, test returned 255 (wstat 65280, 0xff00)
  Failed 2/2 subtests 
 
-- 
Niko Tyni   nt...@debian.org

Bug#898752: node-webpack: FTBFS and autopkgtest failure on 32-bit

[Graham Inggs]

Source: node-webpack
Version: 3.5.6-1
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: needs-update


Hi Maintainer

Since the upload of node-mocha 4.0.1-1 to unstable, node-webpack FTBFS 
and fails its autopkgtests on 32-bit architectures [1][2] with the 
following error:


<--- Last few GCs --->

[3260:0x1b59450] 4813705071 ms: Mark-sweep 0.5 (4.0) -> 0.5 (4.0) MB, 
0.9 / 0.0 ms  allocation failure GC in old space requested
[3260:0x1b59450] 4813705072 ms: Mark-sweep 0.5 (4.0) -> 0.5 (4.0) MB, 
0.9 / 0.0 ms  allocation failure GC in old space requested
[3260:0x1b59450] 4813705073 ms: Mark-sweep 0.5 (4.0) -> 0.5 (3.0) MB, 
0.8 / 0.0 ms  last resort GC in old space requested
[3260:0x1b59450] 4813705074 ms: Mark-sweep 0.5 (3.0) -> 0.5 (3.0) MB, 
1.1 / 0.0 ms  last resort GC in old space requested



#
# Fatal javascript OOM in CALL_AND_RETRY_LAST
#

I was able to work around this in Ubuntu by reducing 
--max-old-space-size=4096 to 2048 in debian/rules and debian/tests/control.


Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/history/i386/node-webpack.html
[2] 
https://tests.reproducible-builds.org/debian/history/armhf/node-webpack.html

Processed: tagging 895882

[Debian Bug Tracking System]

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

> tags 895882 + fixed-upstream
Bug #895882 [python3-sphinxcontrib.bibtex] sphinx: version 1.7.2-1 causes 
regression in sphinxcontrib-bibtex (Unknown node: bibliography)
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#898542: qt4-x11: FTBFS with libicu60

[Lisandro Damián Nicanor Pérez Meyer]

JFTR: I'm trying to get this done now.

Bug#896921: [Pkg-salt-team] Bug#896921: Salt 2017.7.5 has been released

[Dirk Heinrichs]

Am 15.05.2018 um 10:23 schrieb Benjamin Drung:

> Am Sonntag, den 13.05.2018, 07:20 + schrieb Dirk Heinrichs:
>> Hi, could the version be bumped, then? 
> It could, but fix was merged after the release of 2017.7.5. So I am
> waiting for the release of of 2017.7.6/2018.3.1 that include the fix. 

Ah, OK.

Bye...

    Dirk

-- 
Dirk Heinrichs 
GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de






signature.asc
Description: OpenPGP digital signature

Bug#894649: marked as done (ext4magic FTBFS with e2fsprogs 1.44.1-1)

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 15:19:18 +
with message-id 
and subject line Bug#894649: fixed in ext4magic 0.3.2-9
has caused the Debian Bug report #894649,
regarding ext4magic FTBFS with e2fsprogs 1.44.1-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
894649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ext4magic
Version: 0.3.2-7
Severity: serious
Tags: buster sid

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

...
inode.c: In function 'dump_inode':
inode.c:409:82: error: 'struct ext2_inode' has no member named 'i_dir_acl'; did 
you mean 'i_file_acl'?
 inode->i_file_acl, LINUX_S_ISDIR(inode->i_mode) ? 
inode->i_dir_acl : 0,

  ^

  i_file_acl
inode.c:416:63: error: 'struct ext2_inode' has no member named 'i_dir_acl'; did 
you mean 'i_file_acl'?
 LINUX_S_ISDIR(inode->i_mode) ? inode->i_dir_acl : 0);
   ^


The "#define i_dir_acl i_size_high" was removed.
--- End Message ---
--- Begin Message ---
Source: ext4magic
Source-Version: 0.3.2-9

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

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

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

Debian distribution maintenance software
pp.
Giovani Augusto Ferreira  (supplier of updated ext4magic 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 15 May 2018 11:43:25 -0300
Source: ext4magic
Binary: ext4magic
Architecture: source
Version: 0.3.2-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Giovani Augusto Ferreira 
Description:
 ext4magic  - recover deleted files from ext3 or ext4 partitions
Closes: 894649
Changes:
 ext4magic (0.3.2-9) unstable; urgency=medium
 .
   [ Raphaël Hertzog ]
   * Update team maintainer address to Debian Security Tools
 
   * Update Vcs-Git and Vcs-Browser for the move to salsa.debian.org
 .
   [ Hilko Bengen ]
   * Add patch to fix FTBFS with new e2fsprogs (Closes: #894649)
 .
   [ Giovani Augusto Ferreira ]
   * Update my email address
   * Update to https Format URI
   * Bumped DH level to 11
   * Bumped Standards-Version to 4.1.4
   * Removed unnecessary dh argument and removed autoreconf build-depends
   * Added a head for the patch
Checksums-Sha1:
 01b302d0c888d338568cb93c5b3c3b95136318e7 2006 ext4magic_0.3.2-9.dsc
 942dad37b04c9f860f6acd64b702189bb61a883c 6244 ext4magic_0.3.2-9.debian.tar.xz
 350ec2d2b5f50c4210ba40e79bb8638b60fb7195 5992 
ext4magic_0.3.2-9_source.buildinfo
Checksums-Sha256:
 6b9b93f977637a7d1dace8fc482f07a67dfb4c3f46b054f0ec386f911ee53305 2006 
ext4magic_0.3.2-9.dsc
 4c6f6e23d38acf8459feab8bb567a0f68c3baea3051fa938e2e4898aeee4a00e 6244 
ext4magic_0.3.2-9.debian.tar.xz
 8c20a41132b4e587b3dd662c2a18ec7d90f1758cf4b239147e047b44af9843e6 5992 
ext4magic_0.3.2-9_source.buildinfo
Files:
 e87f679d50b7c7d095b94c5ddd0ebf66 2006 utils optional ext4magic_0.3.2-9.dsc
 39dbafdc1252bc1d59a7cbe57bf7d592 6244 utils optional 
ext4magic_0.3.2-9.debian.tar.xz
 51285300c454e061b3ccfef8b62f3bb1 5992 utils optional 
ext4magic_0.3.2-9_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEs/UaJxJhnD7NdLjheElO9yN1pmwFAlr686YACgkQeElO9yN1
pmxUTA/9Fmc8Fn5IQLV//nlxqQm8o4aN/+ASXStrU4kxkOcm0+cgMCTWWc3+ReL1
R8zOzVz0uWr1/3TsayW0hMW3VKTU6klaalAy4JehflCKadn6gW5nyTndVgCNj/7T
PBzXGePb9ce1/tahE0NbToC6waMjMgnRYlzYxYgZjQXvQvcNWCYw06+XnYn6+2xM
7XDfXKR4K62xadC/y6uLGsZY7KQkGkxRz8UbpX1lZGtAHbsZH4TA9+Kb5eS5iKqD
muUEXIItBDNHtENxP9VwZmrHhc4N+2q+E3JNoaAyhsVm8YGLHfrQmphX/HsXrEPH
YnhkmnqeuTRDYZ89rJODp/wT9Cb7zpKWUkNZEx8tMG/KaOmXAX/HI+tCu/On8IOl
Av0fE0XB5ySnhI/v5kGzMzeVc9niE8MokC8j6KTKV+75PqqtFuT4vUOzaJ///Jn0
fqJjH2Kf0L/Elh5P5x9HP8A1cFYSZwBEn9zJtPH/AtFaojU3P2ss+kOyXKWLgygC
Dx0Cky8l656NZcBrb+YxtmMb6U+Dkrv03KDWvj2BUMEtfIvRwwDZrwo6aA1pNUjY
MHGqNmSiLgHJ+pEA5KFcrar5EQEEA

Processed: breaks when #included after

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:systemd libmount-dev
Bug #898743 [linux-libc-dev,libc6-dev]  breaks when #included 
after 
Added indication that 898743 affects src:systemd and libmount-dev

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

Bug#898743: breaks when #included after

[Helmut Grohne]

Package: linux-libc-dev,libc6-dev
Severity: serious
Justification: makes systemd ftbfs
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:systemd libmount-dev

systemd FTBFS here, because compiling load-fragment.c fails. I spent a while
minimizing that file and it boils down to:

$ cat test.c
#include 
#include 
$ gcc -c test.c
In file included from test.c:1:0:
/usr/include/x86_64-linux-gnu/sys/mount.h:35:3: error: expected identifier 
before numeric constant
   MS_RDONLY = 1,  /* Mount read-only.  */
   ^
$

linux/fs.h #defines MS_RDONLY and then sys/mount.h tries to create an
enum containing MS_RDONLY. That's a problem.

This is also known in fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1497501

That bug hints that sometimes headers need to #included in a certain
order. If that is the case, this bug should be reassigned to src:systemd
asking that  or  must be #included before
. It also means that  should #include
 before defining its own copies of these macros.

Helmut

PS: Let me briefly curse systemd for their use of cyclic #includes
(unit.h <-> cgroup.h) and #pragma once as that works pretty badly
with creduce. Thank you.

Bug#897975: [gdm3]

[rastersoft]

Package: gdm3
Version: 3.28.1-1

More info: it also fails when booting SID with kernel 4.9.0-6 (from 
Debian Stable).



--- System information. ---
Architecture:
Kernel: Linux 4.16.0-1-amd64

Debian Release: buster/sid
500 unstable ftp.debian.org

--- Package information. ---
Depends (Version) | Installed
-+-===
libaccountsservice0 (>= 0.6.37) | 0.6.45-1
libaudit1 (>= 1:2.2.1) | 1:2.8.3-1
libc6 (>= 2.14) |
libcanberra-gtk3-0 (>= 0.25) |
libcanberra0 (>= 0.2) |
libgdk-pixbuf2.0-0 (>= 2.22.0) |
libgdm1 (= 3.28.1-1) |
libglib2.0-0 (>= 2.39.4) |
libgtk-3-0 (>= 3.0.0) |
libkeyutils1 (>= 1.5.9) |
libpam0g (>= 0.99.7.1) |
libselinux1 (>= 1.32) |
libsystemd0 |
libwrap0 (>= 7.6-4~) |
libx11-6 |
libxau6 |
libxcb1 |
libxdmcp6 |
debconf (>= 0.5) |
OR debconf-2.0 |
gir1.2-gdm-1.0 (= 3.28.1-1) |
adduser |
libpam-modules (>= 0.72-1) |
libpam-runtime (>= 0.76-13.1) |
libpam-systemd |
gnome-session-bin (>= 3.10) |
gnome-settings-daemon (>= 3.24) |
gnome-shell (>= 3.19.92) |
gnome-session |
OR x-session-manager |
OR x-window-manager |
OR x-terminal-emulator |
lsb-base (>= 3.2-14) |
librsvg2-common |
accountsservice (>= 0.6.35) |
policykit-1 (>= 0.105-5~) |
gsettings-desktop-schemas |
libglib2.0-bin (>= 2.35.0) |
dconf-cli (>= 0.20) |
dconf-gsettings-backend (>= 0.20) |
ucf |
x11-common (>= 1:7.6+11) |
x11-xserver-utils |


Recommends (Version) | Installed
=-+-===
zenity | 3.28.1-1
xserver-xephyr | 2:1.19.6-1
x11-xkb-utils | 7.7+4
xserver-xorg | 1:7.7+19
at-spi2-core | 2.28.0-3
desktop-base (>= 6) | 9.0.5


Suggests (Version) | Installed
=-+-=
libpam-gnome-keyring | 3.28.0.2-1
gnome-orca | 3.28.1-1
libpam-fprintd (>= 0.8.0-2) |

--
Nos leemos
 RASTER(Linux user #228804)
ras...@rastersoft.com  http://www.rastersoft.com

Bug#898738: debootstrap fails when specifying components

[Luca Falavigna]

Source: debootstrap
Version: 1.0.98
Severity: serious


debootstrap fails when specifying components on command line:

# debootstrap --components=main,contrib,non-free unstable unstable
http://deb.debian.org/debian
I: Target architecture can be executed
I: Checking Release signature
I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010)
I: Validating Packages
I: Retrieving Packages
I: Retrieving Packages
I: Validating Packages
W: Retrying failed download of
http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages
I: Retrieving Packages
I: Validating Packages
W: Retrying failed download of
http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages
I: Retrieving Packages
I: Validating Packages
W: Retrying failed download of
http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages
I: Retrieving Packages
I: Validating Packages
W: Retrying failed download of
http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages
I: Retrieving Packages
I: Validating Packages
W: Retrying failed download of
http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages.gz
W: http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages.gz
was corrupt
I: Retrieving Packages
E: Couldn't download
http://deb.debian.org/debian/dists/unstable/contrib/binary-amd64/Packages


It works correctly when omitting ---components, or with --components=main only.

-- 
Cheers,
Luca

Bug#898734: ocaml-rope: FTBFS with dune/1.0~beta20-1

[Nicolas Braud-Santoni]

Source: ocaml-rope
Version: 0.6-1
Severity: serious
Justification: FTBFS

Hi,

ocaml-rope fails to build using the new version of dune/jbuilder
due to dh_missing complaining about uninstalled files.

I will prepare a new upload momentarily.


Best,

  nicoo

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

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

Bug#894621: ocaml-rope FTBFS: Error: Library "bytes" not found

[Nicolas Braud-Santoni]

Control: fixed -1 1.0~beta20-1

Hi,

I just checked and this was fixed by my upload of v1.0~beta20-1, ...
which I did because I ran into the same bug while packaging something else ;)

However, ocaml-rope now FTBFS due to dh_missing; I will file a bug and fix that
momentarily.


Best,

  nicoo

On Mon, Apr 02, 2018 at 11:58:01PM +0300, Adrian Bunk wrote:
> Control: reassign -1 jbuilder 1.0~beta19-1
> Control: affects -1 src:ocaml-rope src:ocaml-migrate-parsetree
> 
> On Mon, Apr 02, 2018 at 07:23:01PM +0200, Ralf Treinen wrote:
> > On Mon, Apr 02, 2018 at 08:13:56PM +0300, Adrian Bunk wrote:
> > > On Mon, Apr 02, 2018 at 07:08:52PM +0200, Ralf Treinen wrote:
> > > > Hi,
> > > > 
> > > > On Mon, Apr 02, 2018 at 06:15:11PM +0300, Adrian Bunk wrote:
> > > > > Source: ocaml-rope
> > > > > Version: 0.6-1
> > > > > Severity: serious
> > > > > 
> > > > > Some recent change in unstable makes ocaml-rope FTBFS:
> > > > > 
> > > > > https://tests.reproducible-builds.org/debian/history/ocaml-rope.html
> > > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ocaml-rope.html
> > > > 
> > > > This rather looks like bug #881770 of jbuilder, which was supposed to be
> > > > fixed in jbuilder (1.0~beta18-1), except that recent versions of 
> > > > jbuilder
> > > > fail to compile at all on byte-code architectures.
> > > 
> > > amd64 and arm64 are not byte-code architectures.
> > 
> > You are right. I was looking at the autobuilder status which only
> > displays build-failures on bytecode arches at the moment.
> 
> I just tried with jbuilder 1.0~beta14-1,
> and that fixed the build.
> 
> Likely related beta14 -> beta19 breakage in ocaml-migrate-parsetree:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ocaml-migrate-parsetree.html
> 
> > -Ralf.
> 
> cu
> Adrian
> 
> -- 
> 
>"Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
>"Only a promise," Lao Er said.
>Pearl S. Buck - Dragon Seed
> 
> 

Processed: Re: Bug#894621: ocaml-rope FTBFS: Error: Library "bytes" not found

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.0~beta20-1
Bug #894621 [jbuilder] ocaml-rope FTBFS: Error: Library "bytes" not found
Marked as fixed in versions dune/1.0~beta20-1.

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

Bug#898720: marked as done (E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1 (btrfs-zero-log no longer present))

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 13:49:18 +
with message-id 
and subject line Bug#898720: fixed in btrfs-progs 4.16.1-2
has caused the Debian Bug report #898720,
regarding E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1 
(btrfs-zero-log no longer present)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
898720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: btrfs-progs
Version: 4.16.1-1
Severity: grave
Justification: renders package unusable (fails to install)

Preparing to unpack .../04-btrfs-progs_4.16.1-1_amd64.deb ...
Unpacking btrfs-progs (4.16.1-1) over (4.15.1-2) ...
...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.16.0-1-amd64
E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.16.0-1-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 1

It looks as though btrfs-zero-log (also btrfs-debug-tree,
btrfs-show-super, btrfs-calc-size) were removed in 4.16.1,
but /usr/share/initramfs-tools/hooks/btrfs still wants to install
btrfs-zero-log into the initramfs as requested in #721857. Please either
reinstate btrfs-zero-log, or stop trying to add it to the initramfs
(and include its replacement instead if there is one).

smcv

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

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

Versions of packages btrfs-progs depends on:
ii  libblkid1  2.32-0.1
ii  libc6  2.27-3
ii  liblzo2-2  2.10-0.1
ii  libuuid1   2.32-0.1
ii  zlib1g 1:1.2.11.dfsg-1

btrfs-progs recommends no packages.

Versions of packages btrfs-progs suggests:
pn  duperemove  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: btrfs-progs
Source-Version: 4.16.1-2

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

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

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

Debian distribution maintenance software
pp.
Dimitri John Ledkov  (supplier of updated btrfs-progs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 15 May 2018 14:15:27 +0100
Source: btrfs-progs
Binary: btrfs-progs libbtrfs0 libbtrfs-dev libbtrfsutil1 libbtrfsutil-dev 
python3-btrfsutil btrfs-progs-udeb
Architecture: source
Version: 4.16.1-2
Distribution: unstable
Urgency: medium
Maintainer: Dimitri John Ledkov 
Changed-By: Dimitri John Ledkov 
Description:
 btrfs-progs - Checksumming Copy on Write Filesystem utilities
 btrfs-progs-udeb - Checksumming Copy on Write Filesystem utilities (udeb) 
(udeb)
 libbtrfs-dev - Checksumming Copy on Write Filesystem utilities (development 
head
 libbtrfs0  - Checksumming Copy on Write Filesystem utilities (runtime library)
 libbtrfsutil-dev - Checksumming Copy on Write Filesystem utilities (util 
development
 libbtrfsutil1 - Checksumming Copy on Write Filesystem utilities (runtime util 
lib
 python3-btrfsutil - Checksumming Copy on Write Filesystem utilities (python3 
bindings
Closes: 898719 898720
Changes:
 btrfs-progs (4.16.1-2) unstable; urgency=medium
 .
   * Do not copy_exec btrfs-zero-log into initramfs, superseeded by `btrfs
 rescue zero-log` sub-command. Closes: #898720, #898719.
Checksums-Sha1:
 19c61005246ca28810ed742972d958556f1a684e 2306 btrfs-progs_4.16.1-2.dsc
 f3a3689072545d587741b425850ea23ad1fc992b 16468 
btrfs-progs_4.16.1-2.debian.tar.xz
Checksums-Sh

Bug#898719: marked as done (btrfs-progs: Would make initramfs-tools hook fail)

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 13:49:18 +
with message-id 
and subject line Bug#898719: fixed in btrfs-progs 4.16.1-2
has caused the Debian Bug report #898719,
regarding btrfs-progs: Would make initramfs-tools hook fail
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
898719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: btrfs-progs
Version: 4.16.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When upgrading btrfs-progs from 4.15.1-2 to 4.16.1-1, the trigger of initramfs-
tools would fail:

% sudo apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up initramfs-tools (0.130) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.16.0-1-amd64
E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.16.0-1-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

It looks like a bug in btrfs-progs script.

--
Regards,
Boyuan Yang



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

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: btrfs-progs
Source-Version: 4.16.1-2

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

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

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

Debian distribution maintenance software
pp.
Dimitri John Ledkov  (supplier of updated btrfs-progs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 15 May 2018 14:15:27 +0100
Source: btrfs-progs
Binary: btrfs-progs libbtrfs0 libbtrfs-dev libbtrfsutil1 libbtrfsutil-dev 
python3-btrfsutil btrfs-progs-udeb
Architecture: source
Version: 4.16.1-2
Distribution: unstable
Urgency: medium
Maintainer: Dimitri John Ledkov 
Changed-By: Dimitri John Ledkov 
Description:
 btrfs-progs - Checksumming Copy on Write Filesystem utilities
 btrfs-progs-udeb - Checksumming Copy on Write Filesystem utilities (udeb) 
(udeb)
 libbtrfs-dev - Checksumming Copy on Write Filesystem utilities (development 
head
 libbtrfs0  - Checksumming Copy on Write Filesystem utilities (runtime library)
 libbtrfsutil-dev - Checksumming Copy on Write Filesystem utilities (util 
development
 libbtrfsutil1 - Checksumming Copy on Write Filesystem utilities (runtime util 
lib
 python3-btrfsutil - Checksumming Copy on Write Filesystem utilities (python3 
bindings
Closes: 898719 898720
Changes:
 btrfs-progs (4.16.1-2) unstable; urgency=medium
 .
   * Do not copy_exec btrfs-zero-log into initramfs, superseeded by `btrfs
 rescue zero-log` sub-command. Closes: #898720, #898719.
Checksums-Sha1:
 19c61005246ca28810ed742972d958556f1a684e 2306 btrfs-progs_4.16.1-2.dsc
 f3a3689072545d587741b425850ea23ad1fc992b 16468 
btrfs-progs_4.16.1-2.debian.tar.xz
Checksums-Sha256:
 f704da1181c002efa67212e48aed9f3ff69a2b549342570b4a508ff37f3abb5f 2306 
btrfs-progs_4.16.1-2.dsc
 3591a2c444aaf22aefd272c8506ad1e3d6aa5647f5e54771303cc1d0af784819 16468 
btrfs-progs_4.16.1-2.debian.tar.xz
Files:
 de0f288912e388b86404dd549d443be5 2306 admin optional btrfs-progs_4.16.1-2.dsc
 0908432c5ea902e788406db7e1342662 16468 admin optional

Bug#898725: flex: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

Package: flex
Version: 2.6.4-6.1
Severity: serious

Hello Manoj.

This package currently does not build with "dpkg-buildpackage -A".
This is from my build log:

[...]
rm -f debian/flex/usr/share/doc/flex/flex.pdf
test ! -f debian/flex/usr/share/doc/flex/COPYING ||  \
rm -f debian/flex/usr/share/doc/flex/COPYING
find debian/flex/usr/share/locale  -type d -empty -delete
find: 'debian/flex/usr/share/locale': No such file or directory
debian/rules:57: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:41: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


To reproduce, please try "dpkg-buildpackage -A".

Hint: I have not looked at the reason why it fails, but in cases like
this one it usually helps to split override_dh_install into
override_dh_install-indep and override_dh_install-arch.

[ Note: I'm using X-Debbugs-Cc to Cc Laurent Bigonville, who did the last 
upload ].

Thanks.

Processed: tagging 898719

[Debian Bug Tracking System]

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

> tags 898719 + pending
Bug #898719 [src:btrfs-progs] btrfs-progs: Would make initramfs-tools hook fail
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 898720

[Debian Bug Tracking System]

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

> tags 898720 + pending
Bug #898720 [btrfs-progs] E: /usr/share/initramfs-tools/hooks/btrfs failed with 
return 1 (btrfs-zero-log no longer present)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#898720: E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1 (btrfs-zero-log no longer present)

[Dimitri John Ledkov]

On 15 May 2018 at 13:59, Simon McVittie  wrote:
> Package: btrfs-progs
> Version: 4.16.1-1
> Severity: grave
> Justification: renders package unusable (fails to install)
>
> Preparing to unpack .../04-btrfs-progs_4.16.1-1_amd64.deb ...
> Unpacking btrfs-progs (4.16.1-1) over (4.15.1-2) ...
> ...
> Processing triggers for initramfs-tools (0.130) ...
> update-initramfs: Generating /boot/initrd.img-4.16.0-1-amd64
> E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
> update-initramfs: failed for /boot/initrd.img-4.16.0-1-amd64 with 1.
> dpkg: error processing package initramfs-tools (--configure):
>  installed initramfs-tools package post-installation script subprocess 
> returned error exit status 1
>
> It looks as though btrfs-zero-log (also btrfs-debug-tree,
> btrfs-show-super, btrfs-calc-size) were removed in 4.16.1,
> but /usr/share/initramfs-tools/hooks/btrfs still wants to install
> btrfs-zero-log into the initramfs as requested in #721857. Please either
> reinstate btrfs-zero-log, or stop trying to add it to the initramfs
> (and include its replacement instead if there is one).
>

BAH

will do shortly =)


> smcv
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
> 'stable-debug'), (500, 'proposed-updates'), (500, 'experimental-debug'), 
> (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 
> 'stable'), (100, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), 
> LANGUAGE=en_GB.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages btrfs-progs depends on:
> ii  libblkid1  2.32-0.1
> ii  libc6  2.27-3
> ii  liblzo2-2  2.10-0.1
> ii  libuuid1   2.32-0.1
> ii  zlib1g 1:1.2.11.dfsg-1
>
> btrfs-progs recommends no packages.
>
> Versions of packages btrfs-progs suggests:
> pn  duperemove  
>
> -- no debconf information

-- 
Regards,

Dimitri.

Bug#898720: E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1 (btrfs-zero-log no longer present)

[Simon McVittie]

Package: btrfs-progs
Version: 4.16.1-1
Severity: grave
Justification: renders package unusable (fails to install)

Preparing to unpack .../04-btrfs-progs_4.16.1-1_amd64.deb ...
Unpacking btrfs-progs (4.16.1-1) over (4.15.1-2) ...
...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.16.0-1-amd64
E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.16.0-1-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 1

It looks as though btrfs-zero-log (also btrfs-debug-tree,
btrfs-show-super, btrfs-calc-size) were removed in 4.16.1,
but /usr/share/initramfs-tools/hooks/btrfs still wants to install
btrfs-zero-log into the initramfs as requested in #721857. Please either
reinstate btrfs-zero-log, or stop trying to add it to the initramfs
(and include its replacement instead if there is one).

smcv

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

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

Versions of packages btrfs-progs depends on:
ii  libblkid1  2.32-0.1
ii  libc6  2.27-3
ii  liblzo2-2  2.10-0.1
ii  libuuid1   2.32-0.1
ii  zlib1g 1:1.2.11.dfsg-1

btrfs-progs recommends no packages.

Versions of packages btrfs-progs suggests:
pn  duperemove  

-- no debconf information

Bug#898719: btrfs-progs: Would make initramfs-tools hook fail

[Boyuan Yang]

Source: btrfs-progs
Version: 4.16.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When upgrading btrfs-progs from 4.15.1-2 to 4.16.1-1, the trigger of initramfs-
tools would fail:

% sudo apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up initramfs-tools (0.130) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.16.0-1-amd64
E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.16.0-1-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

It looks like a bug in btrfs-progs script.

--
Regards,
Boyuan Yang



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

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

Bug#897537: tudu: FTBFS: ./configure: 394: ./configure: rmtest.c: not found

[meskio]

Quoting Sven Joachim (2018-05-06 21:50:57)
> It seems to me this is a bug in acr 1.6.1-1.  The configure script
> generated by it is clearly broken, and the same tudu version built
> successfully with acr 1.2-1 back in June 2017.  Maybe the acr
> maintainer can find out what went wrong here.

I submited the bug upstream:
https://github.com/radare/acr/issues/15

I'll try to fix it myself.

-- 
meskio | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 My contact info: http://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.


signature.asc
Description: signature

Processed: Re: Bug#897653: tar 1.30 breaks pristine-tar

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #897653 [tar] tar 1.30 breaks pristine-tar
Added tag(s) patch.

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

Bug#897653: tar 1.30 breaks pristine-tar

[Antonio Terceiro]

Control: tag -1 + patch

On Mon, May 14, 2018 at 11:07:50AM -0700, Bdale Garbee wrote:
> Paul Eggert  writes:
> 
> > On 05/14/2018 07:56 AM, Antonio Terceiro wrote:
> >> I still need to study the  > code a bit further to try to come up with a 
> >> better suggestion.
> > Sorry, the only suggestion I can make is that you should just use the 
> > new GNU tar. The old one was obviously busted and it generated busted 
> > tarballs.
> 
> Antonio, given this, I wonder if maybe the right approach might be to
> come up with a work-around so that pristine-tar can collaborate with tar
> to successfully extract older tarballs from git repos?  I could imagine
> a Debian-specific patch that adds a long-form command-line option to do
> the equivalent of reverting that one patch, and a mod to pristine-tar to
> try that option if reproducing the tarball fails before giving up
> entirely?  
> 
> In this way, Debian developers could continue to be able to rebuild and
> work on packages with older tarballs captured using pristine-tar, but
> all new work would be in the correct format.  This means all developers
> would want to get to tar 1.30 or later as soon as possible, but at least
> we wouldn't lose access to all our existing work.
> 
> What do you think?

Yes. Attached you will find a patch against the Debian tar packaging
repository that adds this new work-around to the existing
Debian-specific pristine-tar patch. I tested it locally and it works.

The accompanying pristine-tar change is this:
https://salsa.debian.org/debian/pristine-tar/commit/dd332ffb672ce27dcacdeec712419683f36c59c8

Thanks
From fdb28a41aac7627baaf405dc28e3328dcacb84a6 Mon Sep 17 00:00:00 2001
From: Antonio Terceiro 
Date: Tue, 15 May 2018 08:36:12 -0300
Subject: [PATCH 1/2] pristine-tar: add support to force using user and group
 names

---
 debian/patches/pristine-tar.diff | 33 +++-
 1 file changed, 24 insertions(+), 9 deletions(-)

diff --git a/debian/patches/pristine-tar.diff b/debian/patches/pristine-tar.diff
index 26e0268f..4f7826ea 100644
--- a/debian/patches/pristine-tar.diff
+++ b/debian/patches/pristine-tar.diff
@@ -1,26 +1,28 @@
 --- a/src/common.h
 +++ b/src/common.h
-@@ -980,4 +980,7 @@
+@@ -980,4 +980,8 @@ void group_map_read (char const *file);
  int group_map_translate (gid_t gid, gid_t *new_gid, char const **new_name);
  
  
 +GLOBAL int debian_longlink_hack;
++GLOBAL int debian_broken_numeric_owner;
 +GLOBAL int pristine_tar_compat;
 +
  _GL_INLINE_HEADER_END
 --- a/src/create.c
 +++ b/src/create.c
-@@ -28,6 +28,9 @@
+@@ -28,6 +28,10 @@
  #include "common.h"
  #include 
  
 +extern int debian_longlink_hack;
++extern int debian_broken_numeric_owner;
 +extern int pristine_tar_compat;
 +
  /* Error number to use when an impostor is discovered.
 Pretend the impostor isn't there.  */
  enum { IMPOSTOR_ERRNO = ENOENT };
-@@ -535,6 +538,11 @@
+@@ -535,6 +539,11 @@ write_short_name (struct tar_stat_info *
return header;
  }
  
@@ -32,18 +34,20 @@
  /* Write a GNUTYPE_LONGLINK or GNUTYPE_LONGNAME block.  */
  static void
  write_gnu_long_link (struct tar_stat_info *st, const char *p, char type)
-@@ -544,6 +552,10 @@
+@@ -544,7 +553,11 @@ write_gnu_long_link (struct tar_stat_inf
union block *header;
  
header = start_private_header ("././@LongLink", size, 0);
+-  if (! numeric_owner_option)
 +  if (pristine_tar_compat) {
 + FILL (header->header.mtime, '0');
 + FILL (header->header.mode, '0');
 +  }
-   if (! numeric_owner_option)
++  if ((pristine_tar_compat && debian_broken_numeric_owner) || ! numeric_owner_option)
  {
static char *uname, *gname;
-@@ -729,7 +741,7 @@
+   if (!uname)
+@@ -729,7 +742,7 @@ write_header_name (struct tar_stat_info
return write_short_name (st);
  }
else if (NAME_FIELD_SIZE - (archive_format == OLDGNU_FORMAT)
@@ -52,7 +56,7 @@
  return write_long_name (st);
else
  return write_short_name (st);
-@@ -1502,7 +1514,7 @@
+@@ -1502,7 +1515,7 @@ dump_hard_link (struct tar_stat_info *st
  	  block_ordinal = current_block_ordinal ();
  	  assign_string (&st->link_name, link_name);
  	  if (NAME_FIELD_SIZE - (archive_format == OLDGNU_FORMAT)
@@ -63,7 +67,7 @@
  	  st->stat.st_size = 0;
 --- a/src/tar.c
 +++ b/src/tar.c
-@@ -1204,6 +1204,26 @@
+@@ -1204,6 +1204,36 @@ expand_pax_option (struct tar_args *targ
return res;
  }
  
@@ -77,6 +81,16 @@
 +	 debian_longlink_hack=0;
 +}
 +
++/* Debian specific environment variable used by pristine-tar to enable use of
++ * user and group names even when --numeric-owner is passed. */
++void debian_broken_numeric_owner_init (void) {
++ char *s=getenv ("TAR_BROKEN_NUMERIC_OWNER");
++ if (s && strcmp(s, "1") == 0)
++	 debian_broken_numeric_owner=1;
++ else
++	 debian_broken_numeric_owner=0;
++}
++
 +/* pristine-tar sets this environment variable to force fields in longlinks
 + * to be zeroed as was the case in tar 1.26. */
 +void pristine_tar_compat_init (void) {
@@ -90,11 +104,12 @@

Bug#885736: marked as done (ggcov: Depends on libgnomeui)

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 11:35:12 +
with message-id 
and subject line Bug#885736: fixed in ggcov 0.9-21
has caused the Debian Bug report #885736,
regarding ggcov: Depends on libgnomeui
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
885736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ggcov
Version: 0.9-19
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui gconf libglade
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnomeui, gconf, and
libglade.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: ggcov
Source-Version: 0.9-21

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated ggcov package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 May 2018 11:44:37 +0100
Source: ggcov
Binary: ggcov
Architecture: source amd64
Version: 0.9-21
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 ggcov  - Graphical tool for displaying gcov test coverage data
Closes: 885736
Changes:
 ggcov (0.9-21) unstable; urgency=medium
 .
   * Standards-Version: 4.1.4
   * Set VCS to salsa.debian.org
   * Set Homepage to new github page
   * Drop B-D on libgnomeui, libglade-dev for GTK2 -> GTK3 transition
   * Disable gui for this upload. Closes: #885736
   * B-D on pkg-config, libglib2.0-dev, libxml-dev
Checksums-Sha1:
 ad0c1a6b96d6933b0f5d189504d03726fefa24e9 1898 ggcov_0.9-21.dsc
 b531c6d00741d3ff907734b70b3a6d77365ec43e 14008 ggcov_0.9-21.debian.tar.xz
 dbc0a9073335aa7bb898e4eda6dbff4bf0b89ca1 5205532 ggcov-dbgsym_0.9-21_amd64.deb
 5babcec75d55cce5453405343ab80b76e823b502 6621 ggcov_0.9-21_amd64.buildinfo
 8d4c5778d7a82e23f7ddd27a7bffa091023d7d04 589976 ggcov_0.9-21_amd64.deb
Checksums-Sha256:
 1f2b97ca29c0893481a67307e8121ad3cd63658d92d1a8627820c33e3db7fd70 1898 
ggcov_0.9-21.dsc
 8376160278cd408378347595bdc6225349bbfabc5467fd206d9570189cfd4cf7 14008 
ggcov_0.9-21.debian.tar.xz
 91722656987d48f0dfa912d03b3a8ca8cb29a9cd2c360edb49d7df2caad1f8c3 5205532 
ggcov-dbgsym_0.9-21_amd64.deb
 76c1ba8ca9d3ae7895820a3ca4550023c04b7983a49c7bbed1d6e1438366a2ca 6621 
ggcov_0.9-21_amd64.buildinfo
 261e7038d6fa76bba2c87af6c43b83b2d5d6340771fd23261697e212973cacde 589976 
ggcov_0.9-21_amd64.deb
Files:
 d9103d40f48eca582dad8a95b70b957f 1898 devel optional ggcov_0.9-21.dsc
 4d1f329a75a45effc1b70bb5d9f99d7d 14008 devel optional 
ggcov_0.9-21.debian.tar.xz
 4297a2c73a6fd726098fff7f9a476609 5205532 debug optional 
ggcov-dbgsym_0.9-21_amd64.deb
 e636c567f47782e03c28907179208abe 6621 devel optional 
ggcov_0.9-21_amd64.buildinfo
 ea4f85fc743bddef6a1303434f7b271a 589976 devel optional ggcov_0.9-21_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAlr6wB0ACgkQy+a7Tl2a
06VWlA/8Cv7bxGyfc7Dj2eV15QT3rdO7WbCxB68hRMDohWKGuEVZpLb/pGmOjElw
nnwT2k7pNKaf4VhB1NZyFL2LlSgVxnOLtOkFuEqT2iKB8yMx3gmrNi91LxJ/h2G8
LYKvomoUtiZHrd3x3sgHjnrW+3aS8GjtgpLdtkbAPU8H8JM1Fpee5cSYgE2SAMPy
AqWTPWWCFJ1rywqW8SmxuK1OFPhZ2h594LVp6la0ZkIIb/HiNj5rSl040maRZDzZ
Zc4uWCDwv37HkzYoHq6IMywYlR9klt4+Astl/jDGdLo9YPy/5q3UqnXNVyL7SbvS
jiCgOOCeZYLlhhpuN85edx1z+pqwwOTEmwBjPiQVugc/yOWjT3cRbSlkb7deBhNr
2byWmuKEs2T9LPti7JtEsQQvR6kU1Z/mpBFjNanATczqVVhLnKFQweKeWlmdTYnV
N0aqRX+P0wxjbQwt8ElONTmEGZNprj8HAQdDBb5fCWRhOjQIdbFtt0hO9b78tI7T
DKzecBq64dVixk+gZDQwPCi5WHH2wjM+qoNdJVQ3srgXfbeHww7hT1l/5/MaScB5
RfJQ9ek4XzG5gr2C

Processed: bug 898633 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=796135

[Debian Bug Tracking System]

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

> forwarded 898633 https://bugzilla.gnome.org/show_bug.cgi?id=796135
Bug #898633 [evolution-data-server] evolution-data-server: efail attack against 
S/MIME
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=796135'.
> thanks
Stopping processing here.

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

Bug#898707: debian/rules build target attempts network access when git is installed

[Thadeu Lima de Souza Cascardo]

Package: crash
Version: 7.2.1-1+b1
Severity: serious
Tags: upstream

When git is installed, the eppic extensions will try to access
github.com to clone the extension code. The clean target does not clean
it up either.

This likely doesn't happen on a system that has just the build
dependencies installed as git is not one of them. But it happens on any
other system that has git installed.

Easy solution here would be to just patch the eppic.mk to just exit.
Ideally, however, we would build the eppic extension by shipping its
code somehow.

I will prepare a patch to do the first.

Cascardo.

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

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.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 crash depends on:
ii  binutils  2.30-19
ii  libc6 2.27-3
ii  liblzo2-2 2.10-0.1
ii  libncurses6   6.1+20180210-3
ii  libsnappy1v5  1.1.7-1
ii  libtinfo6 6.1+20180210-3
ii  zlib1g1:1.2.11.dfsg-1

crash recommends no packages.

Versions of packages crash suggests:
ii  kexec-tools   1:2.0.16-1
ii  makedumpfile  1:1.6.3-2

-- no debconf information

Processed: tagging 896595

[Debian Bug Tracking System]

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

> tags 896595 + fixed-upstream
Bug #896595 [src:gpaw] please avoid distutils usage at runtime
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#894363: marked as done (uwsgi (build) depends on openjdk-8)

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 10:00:17 +
with message-id 
and subject line Bug#894363: fixed in uwsgi 2.0.15-11
has caused the Debian Bug report #894363,
regarding uwsgi (build) depends on openjdk-8
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
894363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uwsgi
Version: 2.0.15-10.4
Severity: serious

openjdk-8-jdk is not expected to be part of the buster release.

If possible, this should be changed to default-jdk
(this currently depends on openjdk-9-jdk).

If a specific version has to be chosen, openjdk-11-jdk
(already in unstable) is what will likely be shipped
in the buster release.
--- End Message ---
--- Begin Message ---
Source: uwsgi
Source-Version: 2.0.15-11

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated uwsgi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 May 2018 12:58:33 +
Source: uwsgi
Binary: libapache2-mod-ruwsgi libapache2-mod-ruwsgi-dbg libapache2-mod-uwsgi 
libapache2-mod-uwsgi-dbg python-uwsgidecorators python3-uwsgidecorators uwsgi 
uwsgi-app-integration-plugins uwsgi-core uwsgi-dbg uwsgi-dev uwsgi-emperor 
uwsgi-extra uwsgi-infrastructure-plugins uwsgi-plugin-alarm-curl 
uwsgi-plugin-alarm-xmpp uwsgi-plugin-asyncio-python 
uwsgi-plugin-asyncio-python3 uwsgi-plugin-curl-cron uwsgi-plugin-emperor-pg 
uwsgi-plugin-fiber uwsgi-plugin-gccgo uwsgi-plugin-geoip 
uwsgi-plugin-gevent-python uwsgi-plugin-glusterfs uwsgi-plugin-graylog2 
uwsgi-plugin-greenlet-python uwsgi-plugin-jvm-openjdk-11 
uwsgi-plugin-jwsgi-openjdk-11 uwsgi-plugin-ldap uwsgi-plugin-lua5.1 
uwsgi-plugin-lua5.2 uwsgi-plugin-mono uwsgi-plugin-psgi uwsgi-plugin-python 
uwsgi-plugin-python3 uwsgi-plugin-rack-ruby2.5 uwsgi-plugin-rados 
uwsgi-plugin-rbthreads uwsgi-plugin-ring-openjdk-11 uwsgi-plugin-router-access 
uwsgi-plugin-servlet-openjdk-11 uwsgi-plugin-sqlite3 uwsgi-plugin-tornado-python
 uwsgi-plugin-xslt uwsgi-plugins-all
 uwsgi-src
Architecture: source amd64 all
Version: 2.0.15-11
Distribution: unstable
Urgency: medium
Maintainer: uWSGI packaging team 
Changed-By: Thomas Goirand 
Description:
 libapache2-mod-ruwsgi - uwsgi module for Apache2 (mod_Ruwsgi)
 libapache2-mod-ruwsgi-dbg - debugging symbols for Apache2 mod_Ruwsgi
 libapache2-mod-uwsgi - uwsgi module for Apache2 (mod_uwsgi)
 libapache2-mod-uwsgi-dbg - debugging symbols for Apache2 mod_uwsgi
 python-uwsgidecorators - module of decorators for elegant access to uWSGI API 
(Python 2)
 python3-uwsgidecorators - module of decorators for elegant access to uWSGI API 
(Python 3)
 uwsgi  - fast, self-healing application container server
 uwsgi-app-integration-plugins - plugins for integration of uWSGI and 
application
 uwsgi-core - fast, self-healing application container server (core)
 uwsgi-dbg  - debugging symbols for uWSGI server and it's plugins
 uwsgi-dev  - fast, self-healing application container server (headers)
 uwsgi-emperor - fast, self-healing application container server (emperor 
scripts)
 uwsgi-extra - fast, self-healing application container server (extra files)
 uwsgi-infrastructure-plugins - infrastructure plugins for uWSGI
 uwsgi-plugin-alarm-curl - cURL alarm plugin for uWSGI
 uwsgi-plugin-alarm-xmpp - XMPP alarm plugin for uWSGI
 uwsgi-plugin-asyncio-python - asyncio plugin for uWSGI (Python 2)
 uwsgi-plugin-asyncio-python3 - asyncio plugin for uWSGI (Python 3)
 uwsgi-plugin-curl-cron - cron cURL plugin for uWSGI
 uwsgi-plugin-emperor-pg - Emperor PostgreSQL plugin for uWSGI
 uwsgi-plugin-fiber - Fiber plugin for uWSGI
 uwsgi-plugin-gccgo - GNU Go plugin for uWSGI
 uwsgi-plugin-geoip - GeoIP plugin for uWSGI
 uwsgi-plugin-gevent-python - gevent plugin for uWSGI (Python 2)
 uwsgi-plugin-glusterfs - GlusterFS storage plugin for uWSGI
 uwsgi-plugin-graylog2 - graylog2 plugin for uWSGI
 uwsgi-plugin-greenlet-python - greenlet plugin fo

Bug#894624: marked as done (uwsgi FTBFS with glusterfs 4.0.1-1)

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 10:00:17 +
with message-id 
and subject line Bug#894624: fixed in uwsgi 2.0.15-11
has caused the Debian Bug report #894624,
regarding uwsgi FTBFS with glusterfs 4.0.1-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
894624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uwsgi
Version: 2.0.15-10.4
Severity: serious

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

...
 CFLAGS="-g -O2 -fstack-protector-strong -Wformat -Werror=format-security" 
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" python 
uwsgiconfig.py -v --plugin plugins/glusterfs debian/buildconf/uwsgi-plugin.ini 
glusterfs
plugins/glusterfs/glusterfs.c:2:10: fatal error: api/glfs.h: No such file or 
directory
 #include 
  ^~~~
compilation terminated.
using profile: debian/buildconf/uwsgi-plugin.ini
detected include path: ['/usr/lib/gcc/x86_64-linux-gnu/7/include', 
'/usr/local/include', '/usr/lib/gcc/x86_64-linux-gnu/7/include-fixed', 
'/usr/include/x86_64-linux-gnu', '/usr/include']
*** uWSGI building and linking plugin plugins/glusterfs ***
x86_64-linux-gnu-gcc -pthread -fPIC -shared -o ./glusterfs_plugin.so -I. -O2 
-I. -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing 
-Wextra -Wno-unused-parameter -Wno-missing-field-initializers 
-DUWSGI_HAS_IFADDRS -DUWSGI_ZLIB -DUWSGI_LOCK_USE_MUTEX -DUWSGI_EVENT_USE_EPOLL 
-DUWSGI_EVENT_TIMER_USE_TIMERFD -DUWSGI_EVENT_FILEMONITOR_USE_INOTIFY  
-DUWSGI_PCRE -DUWSGI_ROUTING -DUWSGI_CAP -DUWSGI_UUID 
-DUWSGI_VERSION="\"2.0.15-debian\"" -DUWSGI_VERSION_BASE="2" 
-DUWSGI_VERSION_MAJOR="0" -DUWSGI_VERSION_MINOR="15" 
-DUWSGI_VERSION_REVISION="0" -DUWSGI_VERSION_CUSTOM="\"debian\"" -DUWSGI_YAML 
-DUWSGI_LIBYAML -DUWSGI_JSON -DUWSGI_SSL -I/usr/include/libxml2 -DUWSGI_XML 
-DUWSGI_XML_LIBXML2 -DUWSGI_PLUGIN_DIR="\".\"" -D_FILE_OFFSET_BITS=64 
-D__USE_FILE_OFFSET64 -DUSE_POSIX_ACLS=1 -I/usr/include/uuid 
-Dglusterfs_plugin=glusterfs_plugin plugins/glusterfs/glusterfs.c -Wl,-z,relro 
-lacl -lgfapi -lglusterfs -lgfrpc -lgfxdr -luuid
*** unable to build glusterfs plugin ***
make: *** [debian/rules:450: debian/stamp-uwsgi-plugin-glusterfs] Error 1
--- End Message ---
--- Begin Message ---
Source: uwsgi
Source-Version: 2.0.15-11

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated uwsgi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 May 2018 12:58:33 +
Source: uwsgi
Binary: libapache2-mod-ruwsgi libapache2-mod-ruwsgi-dbg libapache2-mod-uwsgi 
libapache2-mod-uwsgi-dbg python-uwsgidecorators python3-uwsgidecorators uwsgi 
uwsgi-app-integration-plugins uwsgi-core uwsgi-dbg uwsgi-dev uwsgi-emperor 
uwsgi-extra uwsgi-infrastructure-plugins uwsgi-plugin-alarm-curl 
uwsgi-plugin-alarm-xmpp uwsgi-plugin-asyncio-python 
uwsgi-plugin-asyncio-python3 uwsgi-plugin-curl-cron uwsgi-plugin-emperor-pg 
uwsgi-plugin-fiber uwsgi-plugin-gccgo uwsgi-plugin-geoip 
uwsgi-plugin-gevent-python uwsgi-plugin-glusterfs uwsgi-plugin-graylog2 
uwsgi-plugin-greenlet-python uwsgi-plugin-jvm-openjdk-11 
uwsgi-plugin-jwsgi-openjdk-11 uwsgi-plugin-ldap uwsgi-plugin-lua5.1 
uwsgi-plugin-lua5.2 uwsgi-plugin-mono uwsgi-plugin-psgi uwsgi-plugin-python 
uwsgi-plugin-python3 uwsgi-plugin-rack-ruby2.5 uwsgi-plugin-rados 
uwsgi-plugin-rbthreads uwsgi-plugin-ring-openjdk-11 uwsgi-plugin-router-access 
uwsgi-plugin-servlet-openjdk-11 uwsgi-plugin-sqlite3 uwsgi-plugin-tornado-python
 uwsgi-plugin-xslt uwsgi-plugins-all
 uwsgi-src
Architecture: source amd64 all
Version: 2.0.15-11
Distribution: unstable
Urgency: medium
Maintainer: uWSGI packaging team 
Changed-By: Thomas Goirand 
Description:
 libapache2-mod-ruwsgi - uwsgi module for Apache2 (mod_Ruwsgi)
 libapache2-mod-ruwsgi-dbg - debugging symbols for Apache2 mod_Ruwsgi

Bug#894785: marked as done (apache2: File conflict with libapache2-mod-proxy-uwsgi)

[Debian Bug Tracking System]

Your message dated Tue, 15 May 2018 10:00:17 +
with message-id 
and subject line Bug#894785: fixed in uwsgi 2.0.15-11
has caused the Debian Bug report #894785,
regarding apache2: File conflict with libapache2-mod-proxy-uwsgi
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
894785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apache2
Version: 2.4.33-1
Severity: important

Dear Maintainer,

2.4.30 introduced the mod_proxy_uwsgi, which is currently also available from 
the
uwsgi source package (libapache2-mod-proxy-uwsgi). Packaging should probably
reflect that mod_proxy_uwsgi is now provided directly through apache2 packages.

Preparing to unpack .../apache2_2.4.33-1_amd64.deb ...
Unpacking apache2 (2.4.33-1) over (2.4.29-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/apache2_2.4.33-1_amd64.deb (--unpack):
 trying to overwrite '/etc/apache2/mods-available/proxy_uwsgi.load', which is 
also in package libapache2-mod-proxy-uwsgi 2.0.15-10.4
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Preparing to unpack .../apache2-bin_2.4.33-1_amd64.deb ...
Unpacking apache2-bin (2.4.33-1) over (2.4.29-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/apache2-bin_2.4.33-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/apache2/modules/mod_proxy_uwsgi.so', which is 
also in package libapache2-mod-proxy-uwsgi 2.0.15-10.4
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/apache2_2.4.33-1_amd64.deb
 /var/cache/apt/archives/apache2-bin_2.4.33-1_amd64.deb


-- Package-specific info:

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

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

Versions of packages apache2 depends on:
ii  apache2-bin2.4.29-2
iu  apache2-data   2.4.33-1
iu  apache2-utils  2.4.33-1
ii  dpkg   1.19.0.5
ii  lsb-base   9.20170808
it  mime-support   3.60
ii  perl   5.26.1-5
ii  procps 2:3.3.12-4

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.39

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  w3m [www-browser]0.5.3-36

Versions of packages apache2-bin depends on:
ii  libapr1  1.6.3-2
ii  libaprutil1  1.6.1-2
ii  libaprutil1-dbd-sqlite3  1.6.1-2
ii  libaprutil1-ldap 1.6.1-2
ii  libbrotli1   1.0.3-1
ii  libc62.27-3
ii  libldap-2.4-22.4.45+dfsg-1
ii  liblua5.2-0  5.2.4-1.1+b2
ii  libnghttp2-141.31.0-1
ii  libpcre3 2:8.39-9
ii  libssl1.11.1.0h-2
ii  libxml2  2.9.4+dfsg1-6.1
ii  perl 5.26.1-5
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  w3m [www-browser]0.5.3-36

Versions of packages apache2 is related to:
ii  apache2  2.4.29-2
ii  apache2-bin  2.4.29-2

-- Configuration Files:
/etc/apache2/mods-available/mpm_prefork.conf changed [not included]
/etc/apache2/mods-available/ssl.conf changed [not included]
/etc/apache2/mods-available/status.conf changed [not included]
/etc/apache2/ports.conf changed [not included]
/etc/apache2/sites-available/000-default.conf changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: uwsgi
Source-Version: 2.0.15-11

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated uwsgi package)

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

Bug#898694: Bug #898694 in ruby marked as pending

[santiagorr]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby/commit/2943f7b15ac47c9110b5f8bb5a2346eadefdb83f


Exclude Rinda TestRingFinger and TestRingServer test units requiring network 
access

Closes: #898694

Signed-off-by: Santiago R.R 



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/898694

Processed: Bug #898694 in ruby marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #898694 [src:ruby2.3] FTBFS with cowbuilder when network access is disabled
Added tag(s) pending.

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

Bug#898694: FTBFS with cowbuilder when network access is disabled

[Santiago R.R.]

Source: ruby2.3
Version: 2.3.3-1+deb9u2
Severity: serious

Other than the Failures in #889117, current ruby2.3 package fails to
build due to Rinda TestRingFinger and TestRingServer trying to access
network ressources:

…
  6) Error:
Rinda::TestRingFinger#test_make_socket_ipv4_multicast:
Errno::ENETUNREACH: Network is unreachable - connect(2) for 239.0.0.1:7647
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:431:in `connect'
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:431:in `make_socket'
/build/ruby2.3-2.3.3/test/rinda/test_rinda.rb:782:in 
`test_make_socket_ipv4_multicast'

  7) Error:
Rinda::TestRingFinger#test_make_socket_ipv4_multicast_hops:
Errno::ENETUNREACH: Network is unreachable - connect(2) for 239.0.0.1:7647
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:431:in `connect'
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:431:in `make_socket'
/build/ruby2.3-2.3.3/test/rinda/test_rinda.rb:809:in 
`test_make_socket_ipv4_multicast_hops'

  8) Error:
Rinda::TestRingServer#test_make_socket_ipv4_multicast:
Errno::ENODEV: No such device - setsockopt(2)
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:154:in `setsockopt'
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:154:in `make_socket'
/build/ruby2.3-2.3.3/test/rinda/test_rinda.rb:626:in 
`test_make_socket_ipv4_multicast'

  9) Error:
Rinda::TestRingServer#test_ring_server_ipv4_multicast:
Errno::ENODEV: No such device - setsockopt(2)
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:154:in `setsockopt'
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:154:in `make_socket'
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:108:in `block in initialize'
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:106:in `each'
/build/ruby2.3-2.3.3/lib/rinda/ring.rb:106:in `initialize'
/build/ruby2.3-2.3.3/test/rinda/test_rinda.rb:667:in `new'
/build/ruby2.3-2.3.3/test/rinda/test_rinda.rb:667:in 
`test_ring_server_ipv4_multicast'

15919 tests, 2236057 assertions, 5 failures, 4 errors, 82 skips
…

I am preparing a commit to solve this in the stretch git branch.

cheers,

Santiago


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

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


signature.asc
Description: PGP signature

Processed: Cannot import uwsgidecorator doesn't seem to be that bad of a bug

[Debian Bug Tracking System]

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

> severity 896243 important
Bug #896243 [python-uwsgidecorators] python-uwsgidecorators: uwsgidecorators 
fails to import
Severity set to 'important' from 'serious'
> severity 896244 important
Bug #896244 [python3-uwsgidecorators] python3-uwsgidecorators: uwsgidecorators 
fails to import
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

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

Processed: affects 898501

[Debian Bug Tracking System]

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

> affects 898501 + mailman3 hyperkitty mailman-suite
Bug #898501 [fonts-font-awesome] Broken symlinks
Added indication that 898501 affects mailman3, hyperkitty, and mailman-suite
> thanks
Stopping processing here.

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

Bug#896921: [Pkg-salt-team] Bug#896921: Salt 2017.7.5 has been released

[Benjamin Drung]

Am Sonntag, den 13.05.2018, 07:20 + schrieb Dirk Heinrichs:
> Hi,
> 
> could the version be bumped, then?

It could, but fix was merged after the release of 2017.7.5. So I am
waiting for the release of of 2017.7.6/2018.3.1 that include the fix. 

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL: https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss, Matthias Steinberg, Christoph Steffens

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