Processed: reopening 878870

[Debian Bug Tracking System]

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

> reopen 878870
Bug #878870 {Done: Carsten Schoenert } [libfreetype6] 
freetype 2.8.1 breaks font rendering
Bug #878834 {Done: Carsten Schoenert } [libfreetype6] 
freetype: Upgrade to 2.8.1 breaks font rendering in various applications
Bug #878929 {Done: Carsten Schoenert } [libfreetype6] 
libfreetype6: font rendering broken in electron applications
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions thunderbird/1:52.4.0-1.
No longer marked as fixed in versions thunderbird/1:52.4.0-1.
No longer marked as fixed in versions thunderbird/1:52.4.0-1.
> thanks
Stopping processing here.

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

Bug#853692: marked as done (ufraw: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 21 Oct 2017 04:49:12 +
with message-id 
and subject line Bug#853692: fixed in ufraw 0.22-2
has caused the Debian Bug report #853692,
regarding ufraw: ftbfs with GCC-7
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.)


-- 
853692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853692
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ufraw
Version: 0.22-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/ufraw_0.22-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
/usr/include/c++/7/bits/std_abs.h:61:3: note: candidate: long long int 
std::abs(long long int)
   abs(long long __x) { return __builtin_llabs (__x); }
   ^~~
/usr/include/c++/7/bits/std_abs.h:70:3: note: candidate: constexpr double 
std::abs(double)
   abs(double __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:74:3: note: candidate: constexpr float 
std::abs(float)
   abs(float __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:78:3: note: candidate: constexpr long double 
std::abs(long double)
   abs(long double __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:84:3: note: candidate: constexpr __int128 
std::abs(__int128)
   abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
   ^~~
/usr/include/c++/7/bits/std_abs.h:102:3: note: candidate: constexpr __float128 
std::abs(__float128)
   abs(__float128 __x)
   ^~~
Makefile:915: recipe for target 'dcraw-dcraw.o' failed
make[4]: *** [dcraw-dcraw.o] Error 1
make[4]: *** Waiting for unfinished jobs
Makefile:901: recipe for target 'dcraw.o' failed
make[4]: *** [dcraw.o] Error 1
ufraw_lensfun.cc: In function 'char* UFRaw::_StringNumber(char*, double)':
ufraw_lensfun.cc:171:7: warning: '%.*f' directive output may be truncated 
writing 1 or more bytes into a region of size 80 [-Wformat-truncation=]
 char *_StringNumber(char *buffer, double number)
   ^
In file included from /usr/include/stdio.h:938:0,
 from /usr/include/glib-2.0/glib/gprintf.h:22,
 from /usr/include/glib-2.0/glib/gstdio.h:23,
 from uf_glib.h:21,
 from ufraw.h:21,
 from ufraw_lensfun.cc:17:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:65:44: note: format output 2 bytes 
into a destination of size 80
__bos (__s), __fmt, __va_arg_pack ());
^
make[4]: Leaving directory '/<>'
Makefile:1037: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/<>'
Makefile:593: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/<>'
dh_auto_build: make -j64 returned exit code 2
debian/rules:16: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: ufraw
Source-Version: 0.22-2

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

Bug#879006: marked as done (gnome-software FTBFS with fwupd 1.0.0-1)

[Debian Bug Tracking System]

Your message dated Sat, 21 Oct 2017 04:03:42 +
with message-id 
and subject line Bug#879006: fixed in gnome-software 3.26.1-2
has caused the Debian Bug report #879006,
regarding gnome-software FTBFS with fwupd 1.0.0-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.)


-- 
879006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-software
Version: 3.26.1-1
Severity: serious

https://buildd.debian.org/status/package.php?p=gnome-software=sid

...
FAILED: plugins/fwupd/gs_plugin_fwupd@sha/gs-plugin-fwupd.c.o 
cc  -Iplugins/fwupd/gs_plugin_fwupd@sha -Iplugins/fwupd -I../plugins/fwupd 
-Iplugins/fwupd/../.. -I../plugins/fwupd/../.. -Iplugins/fwupd/../../lib 
-I../plugins/fwupd/../../lib -I/usr/include/libappstream-glib 
-I/usr/include/uuid -I/usr/include/libgcab-1.0 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
-I/usr/include/gio-unix-2.0/ -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/json-glib-1.0 
-I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/fwupd-1 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=c99 
-fstack-protector-strong -Waggregate-return -Warray-bounds -Wcast-align 
-Wclobbered -Wdeclaration-after-statement -Wempty-body -Wex
 tra -Wformat=2 -Wformat-nonliteral -Wformat-security -Wformat-signedness 
-Wignored-qualifiers -Wimplicit-function-declaration -Winit-self -Winline 
-Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs 
-Wmissing-noreturn -Wmissing-parameter-type -Wmissing-prototypes 
-Wnested-externs -Wno-discarded-qualifiers -Wno-missing-field-initializers 
-Wno-strict-aliasing -Wno-suggest-attribute=format -Wno-unused-parameter 
-Wold-style-definition -Woverride-init -Wpacked -Wpointer-arith 
-Wredundant-decls -Wreturn-type -Wshadow -Wsign-compare -Wstrict-aliasing 
-Wstrict-prototypes -Wswitch-default -Wtype-limits -Wundef -Wuninitialized 
-Wunused-but-set-variable -Wwrite-strings -D_XOPEN_SOURCE=500 
-DI_KNOW_THE_PACKAGEKIT_GLIB2_API_IS_SUBJECT_TO_CHANGE 
-DI_KNOW_THE_GNOME_SOFTWARE_API_IS_SUBJECT_TO_CHANGE -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
'-DG_LOG_DOMAIN="GsPluginFwupd"
 ' '-DLOCALPLUGINDIR="/<>/obj-x86_64-linux-gnu/plugins/fwupd"' 
-MMD -MQ 'plugins/fwupd/gs_plugin_fwupd@sha/gs-plugin-fwupd.c.o' -MF 
'plugins/fwupd/gs_plugin_fwupd@sha/gs-plugin-fwupd.c.o.d' -o 
'plugins/fwupd/gs_plugin_fwupd@sha/gs-plugin-fwupd.c.o' -c 
../plugins/fwupd/gs-plugin-fwupd.c
../plugins/fwupd/gs-plugin-fwupd.c:153:8: error: unknown type name 
'FwupdResult'; did you mean 'FwupdRemote'?
FwupdResult *res,
^~~
FwupdRemote
../plugins/fwupd/gs-plugin-fwupd.c: In function 'gs_plugin_fwupd_setup_remote':
../plugins/fwupd/gs-plugin-fwupd.c:252:11: warning: implicit declaration of 
function 'fwupd_remote_get_filename_asc'; did you mean 
'fwupd_remote_get_filename_cache'? [-Wimplicit-function-declaration]
   fwupd_remote_get_filename_asc (remote),
   ^
   fwupd_remote_get_filename_cache
../plugins/fwupd/gs-plugin-fwupd.c:252:11: warning: nested extern declaration 
of 'fwupd_remote_get_filename_asc' [-Wnested-externs]
../plugins/fwupd/gs-plugin-fwupd.c:252:11: warning: passing argument 2 of 
'gs_utils_get_cache_filename' makes pointer from integer without a cast 
[-Wint-conversion]
In file included from ../plugins/fwupd/../../lib/gnome-software.h:36:0,
 from ../plugins/fwupd/gs-plugin-fwupd.c:31:
../plugins/fwupd/../../lib/gs-utils.h:59:9: note: expected 'const gchar * {aka 
const char *}' but argument is of type 'int'
 gchar  *gs_utils_get_cache_filename (const gchar *kind,
 ^~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:28:0,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/fwupd-1/libfwupd/fwupd-client.h:25,
 from /usr/include/fwupd-1/fwupd.h:32,
 from ../plugins/fwupd/gs-plugin-fwupd.c:24:

Bug#876615: marked as done (librsvg FTBFS with gtk-doc-tools 1.26: gtkdoc-scangobj: error: unrecognized arguments: --nogtkinit)

[Debian Bug Tracking System]

Your message dated Sat, 21 Oct 2017 03:34:11 +
with message-id 
and subject line Bug#876615: fixed in librsvg 2.40.18-2
has caused the Debian Bug report #876615,
regarding librsvg FTBFS with gtk-doc-tools 1.26: gtkdoc-scangobj: error: 
unrecognized arguments: --nogtkinit
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.)


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

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

...
Making all in doc
make[3]: Entering directory '/build/1st/librsvg-2.40.18/doc'
if test "/build/1st/librsvg-2.40.18/doc" != "/build/1st/librsvg-2.40.18/doc" ; 
then \
files=`echo version.xml  rsvg-docs.xml rsvg-sections.txt rsvg-overrides.txt 
rsvg.types`; \
if test "x$files" != "x" ; then \
for file in $files ; do \
destdir=`dirname /build/1st/librsvg-2.40.18/doc/$file`; \
test -d "$destdir" || mkdir -p "$destdir"; \
test -f /build/1st/librsvg-2.40.18/doc/$file && \
cp -pf /build/1st/librsvg-2.40.18/doc/$file 
/build/1st/librsvg-2.40.18/doc/$file || true; \
done; \
fi; \
fi
touch setup-build.stamp
_source_dir='' ; \
for i in .. ; do \
_source_dir="${_source_dir} --source-dir=$i" ; \
done ; \
gtkdoc-scan --module=rsvg --ignore-headers="config.h rsvg-bpath-util.h 
rsvg-cairo-clip.h rsvg-cairo-draw.h rsvg-cairo-render.h rsvg-css.h rsvg-defs.h 
rsvg-filter.h rsvg-image.h rsvg-marker.h rsvg-mask.h rsvg-paint-server.h 
rsvg-path.h rsvg-private.h rsvg-shapes.h rsvg-structure.h rsvg-styles.h 
rsvg-text.h rsvg-xml.h" ${_source_dir} 
--deprecated-guards="RSVG_DISABLE_DEPRECATED" 
if grep -l '^..*$' rsvg.types > /dev/null 2>&1 ; then \
scanobj_options=""; \
gtkdoc-scangobj 2>&1 --help | grep  >/dev/null "\-\-verbose"; \
if test "$?" = "0"; then \
if test "x" = "x1"; then \
scanobj_options="--verbose"; \
fi; \
fi; \
CC="/bin/bash ../libtool --tag=CC --mode=compile gcc  
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security" LD="/bin/bash ../libtool --tag=CC --mode=link gcc 
-lgobject-2.0 -lglib-2.0  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -Wl,-z,defs -Wl,-O1 -Wl,--as-needed" 
RUN="/bin/bash ../libtool --mode=execute" CFLAGS="-I.. -I.. -pthread 
-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/cairo 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/libcroco-0.6 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security" 
LDFLAGS="../librsvg-2.la -lgdk_pixbuf-2.0 -lgio-2.0 -lpangocairo-1.0 
-lpango-1.0 -lgobject-2.0 -l
 cairo -lpng16 -lz -lcroco-0.6 -lglib-2.0 -lxml2 -lgthread-2.0 -pthread 
-lglib-2.0  -Wl,-z,relro -Wl,-z,defs -Wl,-O1 -Wl,--as-needed" \
gtkdoc-scangobj --nogtkinit --type-init-func="g_type_init ()" 
$scanobj_options --module=rsvg; \
else \
for i in rsvg.args rsvg.hierarchy rsvg.interfaces rsvg.prerequisites 
rsvg.signals ; do \
test -f $i || touch $i ; \
done \
fi
usage: gtkdoc-scangobj [-h] [--version] --module MODULE [--types TYPES]
   [--type-init-func TYPE_INIT_FUNC]
   [--query-child-properties QUERY_CHILD_PROPERTIES]
   [--output-dir OUTPUT_DIR] [--cc CC] [--ld LD]
   [--cflags CFLAGS] [--ldflags LDFLAGS] [--run RUN]
   [--verbose]
gtkdoc-scangobj: error: unrecognized arguments: --nogtkinit
Makefile:753: recipe for target 'scan-build.stamp' failed
make[3]: *** [scan-build.stamp] Error 2
--- End Message ---
--- Begin Message ---
Source: librsvg
Source-Version: 2.40.18-2

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

Debian distribution maintenance software
pp.
Michael Biebl 

Bug#874621: screen lock cannot be unlocked in vnc session

[Michael Biebl]

Control: severity -1 important

On Fri, 8 Sep 2017 12:22:37 +0530 Pirate Praveen  wrote:
> package: gnome-shell
> version: 3.22.3-3
> severity: grave
> justification: makes it unusable and it is a regression

Downgrading to important as this certainly doesn't make gnome-shell
unusable.

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



signature.asc
Description: OpenPGP digital signature

Processed: Re: screen lock cannot be unlocked in vnc session

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #874621 [gnome-shell] screen lock cannot be unlocked in vnc session
Severity set to 'important' from 'grave'

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

Bug#878411: gnome-session-bin doesn't set environmental variable of GTK_IM_MODULE

[Michael Biebl]

On Fri, 13 Oct 2017 21:37:35 +0900 Takahide Nojima
 wrote:
> Package: gnome-session-bin
> Version: 3.26.1-1
> Severity: serious
> Tags: patch
> 
>  I updated gnome desktop from debian sid. However, I found I can not
> type Japanese language anymore.
> 
>  I finally found gnome-session-bin correctly set an envirionmental
> variable of QT_IM_MODULE, but it doesn't set GTK_IM_MODULE , and this
> cause gtk can't talk to ibus.
> 
>  So I worte a patch for temporary fix this problem, and attach the
> patch. It works fine in my debian box.
> 
>  How about this patch?

I don't think gnome-session ever set the GTK_IM_MODULE env variable.
It's unclear from your bug report whether this was working before for
you ("I can not anymore Japanes language anymore").
Are you saying that with older gnome-session-bin versions it worked?

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



signature.asc
Description: OpenPGP digital signature

Bug#874526: Keyboard grab doesn't work under Wayland

[Michael Biebl]

On Sat, 14 Oct 2017 15:12:34 -0400 Jeremy Bicha  wrote:
> On Wed, Sep 6, 2017 at 5:58 PM, Josh Triplett  wrote:
> > The mechanism gnome-boxes uses to grab the keyboard doesn't work under
> > the default GNOME Wayland session. This makes it impossible to send
> > Ctrl-Alt-Delete; it always goes to gnome-shell instead.
> 
> Please verify whether you can still reproduce this bug after updating
> to gnome-shell and gnome-control-center 3.26 which are now in Debian
> unstable.

Josh, can you please re-test with an up-to-date sid system.
According to a comment in the upstream bug tracker, this should be fixed.

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



signature.asc
Description: OpenPGP digital signature

Bug#878911: avahi FTBFS with debhelper 10.9.2

[Michael Biebl]

On Tue, 17 Oct 2017 19:45:11 +0300 Adrian Bunk  wrote:
> Source: avahi
> Version: 0.7-3
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/avahi.html
> 
> ...
>dh_systemd_start
> dh_systemd_start: Could not find "avahi-daemon.socket" in the 
> /lib/systemd/system directory of avahi-dnsconfd. This could be a typo, or 
> using Also= with a service file from another package. Please check carefully 
> that this message is harmless.
> dh_systemd_start: Cannot open(avahi-daemon.socket) for extracting the Also= 
> line(s)
> debian/rules:4: recipe for target 'binary' failed
> make: *** [binary] Error 2
> 
> 
> 19:35 < nthykier> bunk: Ideally, avahi would fix this on their end.  Without 
> the fail-on-error, debhelper will silently "not do things" 
>   when the file is unreadable (even if only temporarily).  
> I.e. a "fail-to-fail"-case
> 

avahi-daemon.socket is provided by avahi-daemon, a binary package which
is built from the same source package and avahi-dnsconfd depends on
avahi-daemon.
Niels, can you be a bit more specific why this fails now and what you
think is the proper fix?
A service file having an Also= line referencing a service which pulled
in via Depends seems fine to me.

Michael


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



signature.asc
Description: OpenPGP digital signature

Bug#853692: ufraw: diff for NMU version 0.22-1.2

[Hubert Chathi]

On Sat, 21 Oct 2017 00:31:59 +0200, Andreas Bombe  said:

> Dear maintainer,

> I've prepared an NMU for ufraw (versioned as 0.22-1.2) and uploaded it
> to DELAYED/2. Please feel free to tell me if I should delay it longer.

Hi Andreas,

Thank you for the patch and the NMU.  I was actually just looking at
this the other day, but never actually made a new package for it.  As
you note, the code in there is a bit questionable.  Assigning some
values to an unsigned, and then calling abs on that unsigned value is an
odd thing to do.

It looks like upstream's upstream's patch is to change i and c to int
instead of unsigned, and I will upload a new package soon that does
that.  However, please feel free to leave your NMU in DELAYED/2, as that
will force me to actually upload my package soon. ;)

Thanks

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Bug#878519: closing 878519

[Simon McVittie]

close 878519 52.3.1-6
thanks

This was a mozjs52 bug, not a gjs bug. It got reopened when I reassigned it.

Processed: closing 878519

[Debian Bug Tracking System]

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

> close 878519 52.3.1-6
Bug #878519 [mozjs52] gjs: doesn't seem to work on mips (at least on minkus and 
mips-aql-01)
Bug #878431 [mozjs52] gnome-documents: 3.26 FTBFS on mips during cairo 
configure check
There is no source info for the package 'mozjs52' at version '52.3.1-6' with 
architecture ''
Unable to make a source version for version '52.3.1-6'
Marked as fixed in versions 52.3.1-6.
Marked as fixed in versions 52.3.1-6.
Bug #878519 [mozjs52] gjs: doesn't seem to work on mips (at least on minkus and 
mips-aql-01)
Bug #878431 [mozjs52] gnome-documents: 3.26 FTBFS on mips during cairo 
configure check
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#862472: marked as done (tack: FTBFS: ./tack.h:78:32: error: dereferencing pointer to incomplete type 'TERMINAL {aka struct term}')

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 23:21:11 +
with message-id 
and subject line Bug#862472: fixed in tack 1.08-0.1
has caused the Debian Bug report #862472,
regarding tack: FTBFS: ./tack.h:78:32: error: dereferencing pointer to 
incomplete type 'TERMINAL {aka struct term}'
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.)


-- 
862472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tack
Version: 1.07-1
Tags: buster sid fixed-upstream

With libncurses5-dev from experimental, tack FTBFS.  From the build log:

,
| gcc -c -DHAVE_CONFIG_H -I. -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-DXTSTRINGDEFINES -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/tmp/tack-1.07=. 
-fstack-protector-strong -Wformat -Werror=format-security control.c
| In file included from ./tack.h:51:0,
|  from control.c:22:
| control.c: In function 'alloc_arrays':
| ./tack.h:78:32: error: dereferencing pointer to incomplete type 'TERMINAL 
{aka struct term}'
|  #define CUR_TP  (&(cur_term->type))
| ^
| ./tack.h:79:33: note: in expansion of macro 'CUR_TP'
|  #define MAX_STRINGS NUM_STRINGS(CUR_TP)
|  ^~
| control.c:81:45: note: in expansion of macro 'MAX_STRINGS'
|pads = (struct test_results **)calloc(MAX_STRINGS, sizeof(struct 
test_results *));
|  ^~~
| Makefile:242: recipe for target '../tack-1.07/control.o' failed
`

The reason is the following change in ncurses:

,
| 20170318
|   + change TERMINAL structure in term.h to make it opaque.  Some
| applications misuse its members, e.g., directly modifying it
| rather than using def_prog_mode().
`

The latest upstream snapshot at
ftp://ftp.invisible-island.net/ncurses/current/tack-1.07-20170318.tgz
fixes the problem, it might be good to package it after the stretch
release.  Or persuade upstream to release tack 1.08, since 1.07 is
already over seven years old.
--- End Message ---
--- Begin Message ---
Source: tack
Source-Version: 1.08-0.1

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

Debian distribution maintenance software
pp.
Sven Joachim  (supplier of updated tack 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: Sat, 23 Sep 2017 09:50:54 +0200
Source: tack
Binary: tack tack-dbg
Architecture: source
Version: 1.08-0.1
Distribution: unstable
Urgency: medium
Maintainer: Samuel Bronson 
Changed-By: Sven Joachim 
Description:
 tack   - terminfo action checker
 tack-dbg   - terminfo action checker (debug)
Closes: 716377 862472 873288
Changes:
 tack (1.08-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release.
 - Fixes FTBFS with current ncurses (Closes: #862472).
 - Add error check to setupterm call; ncurses does in fact allow
   hardcopy and generic terminal descriptions (Closes: #716377).
   * Drop Debian patches, all applied upstream.
   * Update debian/watch (Closes: #873288).
   * Don't pass LIBS="-ltic" to dh_auto_configure, tack no longer uses
 the tic library.
   * Pass "--disable-rpath-hack" to configure to avoid a possible rpath
 on /lib64.
   * Update debian/copyright.
Checksums-Sha1:
 d14987de41cc03b516b7de4e7de032a80f655bc2 2168 tack_1.08-0.1.dsc
 5af4dd1d7ef6526a93042c7d2777566dfdd0a3a5 222532 tack_1.08.orig.tar.gz
 01cfe68b4c0baaaf2bb11d62ecedb933ea10703f 267 tack_1.08.orig.tar.gz.asc
 f9bf979ac3d184c108be3b0f8da21e558281fa89 4684 tack_1.08-0.1.debian.tar.xz
 d3e7463b79b98cfa4738a99ee265e026fe9d02f0 5716 tack_1.08-0.1_source.buildinfo
Checksums-Sha256:
 b20c49c0b48b28720074dc41dc993ddbb1c023a4d3688d1a39a277e516ddde13 2168 
tack_1.08-0.1.dsc
 5916dde4e5624c3f1aa82af450db55bff050e80fb5d3f0cb1c94f502220ac907 222532 
tack_1.08.orig.tar.gz
 1188318a55dede6e38648e73cd11a588af17541a937839058c89f0b297aee652 267 

Processed: reassign 878519 to mozjs52, found 878519 in 52.3.1-5, affects 878519

[Debian Bug Tracking System]

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

> reassign 878519 mozjs52
Bug #878519 {Done: Jeremy Bicha } [gjs] gjs: doesn't seem to 
work on mips (at least on minkus and mips-aql-01)
Bug #878431 {Done: Jeremy Bicha } [gjs] gnome-documents: 
3.26 FTBFS on mips during cairo configure check
Bug reassigned from package 'gjs' to 'mozjs52'.
Bug reassigned from package 'gjs' to 'mozjs52'.
No longer marked as found in versions gjs/1.50.1-2.
No longer marked as found in versions gjs/1.50.1-2.
No longer marked as fixed in versions mozjs52/52.3.1-6.
No longer marked as fixed in versions mozjs52/52.3.1-6.
> found 878519 52.3.1-5
Bug #878519 {Done: Jeremy Bicha } [mozjs52] gjs: doesn't 
seem to work on mips (at least on minkus and mips-aql-01)
Bug #878431 {Done: Jeremy Bicha } [mozjs52] gnome-documents: 
3.26 FTBFS on mips during cairo configure check
There is no source info for the package 'mozjs52' at version '52.3.1-5' with 
architecture ''
Unable to make a source version for version '52.3.1-5'
Marked as found in versions 52.3.1-5 and reopened.
Marked as found in versions 52.3.1-5 and reopened.
> affects 878519 gjs
Bug #878519 [mozjs52] gjs: doesn't seem to work on mips (at least on minkus and 
mips-aql-01)
Bug #878431 [mozjs52] gnome-documents: 3.26 FTBFS on mips during cairo 
configure check
Added indication that 878519 affects gjs
Added indication that 878431 affects gjs
> thanks
Stopping processing here.

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

Processed: Re: gnome-characters doesn't start

[Debian Bug Tracking System]

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

> severity 879229 serious
Bug #879229 {Done: Jeremy Bicha } [gnome-characters] 
gnome-characters doesn't start
Severity set to 'serious' from 'important'
> retitle 879229 gnome-characters: doesn't start without gjs >= 1.49
Bug #879229 {Done: Jeremy Bicha } [gnome-characters] 
gnome-characters doesn't start
Changed Bug title to 'gnome-characters: doesn't start without gjs >= 1.49' from 
'gnome-characters doesn't start'.
> thanks
Stopping processing here.

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

Bug#853692: ufraw: diff for NMU version 0.22-1.2

[Andreas Bombe]

Control: tags 853692 + patch
Control: tags 853692 + pending

Dear maintainer,

I've prepared an NMU for ufraw (versioned as 0.22-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru ufraw-0.22/debian/changelog ufraw-0.22/debian/changelog
--- ufraw-0.22/debian/changelog	2017-02-27 14:31:26.0 +0100
+++ ufraw-0.22/debian/changelog	2017-10-20 23:56:09.0 +0200
@@ -1,3 +1,11 @@
+ufraw (0.22-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to avoid using abs() on unsigned values which will fail on gcc 7
+due to ambiguous overload resolution. (Closes: #853692)
+
+ -- Andreas Bombe   Fri, 20 Oct 2017 23:56:09 +0200
+
 ufraw (0.22-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ufraw-0.22/debian/patches/04_no-unsigned-abs.patch ufraw-0.22/debian/patches/04_no-unsigned-abs.patch
--- ufraw-0.22/debian/patches/04_no-unsigned-abs.patch	1970-01-01 01:00:00.0 +0100
+++ ufraw-0.22/debian/patches/04_no-unsigned-abs.patch	2017-10-20 23:53:40.0 +0200
@@ -0,0 +1,24 @@
+Description: Don't use abs() on unsigned values
+ With gcc 7, compilation will fail since the overload resolution for unsigned
+ int is ambiguous. Cast the unsigned int to int rather than removing abs(),
+ since the next if condition a few lines below points to unsigned values being
+ used as containers for signed values.
+ .
+ This is a minimal patch that doesn't change or improve the questionable code
+ on a larger scale. A proper fix should figure what is going on here and how to
+ improve it.
+Author: Andreas Bombe 
+Last-Update: 2017-10-20
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/dcraw.cc
 b/dcraw.cc
+@@ -9245,7 +9245,7 @@
+ if (make[0] == 'O') {
+   i = find_green (12, 32, 1188864, 3576832);
+   c = find_green (12, 32, 2383920, 2387016);
+-  if (abs(i) < abs(c)) {
++  if (abs((int)i) < abs((int)c)) {
+ 	SWAP(i,c);
+ 	load_flags = 24;
+   }
diff -Nru ufraw-0.22/debian/patches/series ufraw-0.22/debian/patches/series
--- ufraw-0.22/debian/patches/series	2017-02-27 14:30:30.0 +0100
+++ ufraw-0.22/debian/patches/series	2017-10-20 23:28:22.0 +0200
@@ -1,3 +1,4 @@
 01_no-gimp-remote.patch
 02_CVE-2015-8366.patch
 03_fix-unsigned-char.patch
+04_no-unsigned-abs.patch

Processed: ufraw: diff for NMU version 0.22-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 853692 + patch
Bug #853692 [src:ufraw] ufraw: ftbfs with GCC-7
Added tag(s) patch.
> tags 853692 + pending
Bug #853692 [src:ufraw] ufraw: ftbfs with GCC-7
Added tag(s) pending.

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

Bug#681726: Time to remove eclipse from Testing?

[Emmanuel Bourg]

Le 21/10/2017 à 00:33, Markus Koschany a écrit :

> Please claim this bug or tell me when you start to work on something
> related to Eclipse or Tycho, so that we avoid double work.

For now I'm just working on swt4-gtk. I'll ping the list if I feel ready
for some tycho/eclipse action.

Bug#681726: Time to remove eclipse from Testing?

[Markus Koschany]

Am 21.10.2017 um 00:24 schrieb Emmanuel Bourg:
> Le 20/10/2017 à 23:52, Jeremy Bicha a écrit :
> 
>> Never mind. I tried doing the dak queries and I eventually got more
>> than 500 reverse-depends before I gave up. (Attached)
> 
> Funny, I never realized that src:eclipse was basically holding most of
> the Java packages. Maybe this package deserves some of my attention
> after all ;)

Please claim this bug or tell me when you start to work on something
related to Eclipse or Tycho, so that we avoid double work.

Thanks

Markus



signature.asc
Description: OpenPGP digital signature

Bug#681726: Time to remove eclipse from Testing?

[Emmanuel Bourg]

Le 20/10/2017 à 23:52, Jeremy Bicha a écrit :

> Never mind. I tried doing the dak queries and I eventually got more
> than 500 reverse-depends before I gave up. (Attached)

Funny, I never realized that src:eclipse was basically holding most of
the Java packages. Maybe this package deserves some of my attention
after all ;)

Bug#681726: Time to remove eclipse from Testing?

[Jeremy Bicha]

On Fri, Oct 20, 2017 at 12:47 PM, Markus Koschany  wrote:
> Am 20.10.2017 um 18:43 schrieb Jeremy Bicha:
>> Are there any objections to me requesting that the ftpmasters remove
>> swt-gtk and eclipse from Debian Testing so that we can complete the
>> webkitgtk removal from Testing?
>>
>> Thanks,
>> Jeremy Bicha
>
> Thank you for contacting us. I completely agree with you. Eclipse in its
> current state should not be a blocker for other packages in testing. I
> can't promise anything but I will try to get the package in shape again
> but this process will be quite slow probably, so the request for help is
> as valid as ever.

Never mind. I tried doing the dak queries and I eventually got more
than 500 reverse-depends before I gave up. (Attached)

The only other reverse-depends of libswt-webkit-gtk-3-jni in Testing
now is tuxguitar which was already switched in Unstable to swt4-gtk
which should work with webkit2gtk.

Thanks,
Jeremy Bicha
jbicha@coccia:~$ dak rm -Rns testing swt-gtk
Will remove the following packages from testing:

libswt-cairo-gtk-3-jni |3.8.2-4 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libswt-glx-gtk-3-jni |3.8.2-4 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libswt-gnome-gtk-3-jni |3.8.2-4 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libswt-gtk-3-java |3.8.2-4 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libswt-gtk-3-jni |3.8.2-4 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libswt-webkit-gtk-3-jni |3.8.2-4 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
   swt-gtk |3.8.2-4 | source

Maintainer: Debian Java Maintainers 


--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
androidsdk-tools: androidsdk-traceview
  androidsdk-uiautomatorviewer
  libandroidsdk-common-java
  libandroidsdk-ddmlib-java
  libandroidsdk-ddmuilib-java
  libandroidsdk-hierarchyviewerlib-java
  libandroidsdk-sdklib-java
  libandroidsdk-sdkstats-java
  libandroidsdk-swtmenubar-java
eclipse: eclipse-rcp [amd64 arm64 armel armhf i386 mips mipsel ppc64el s390x]
piccolo: libpiccolo-java
tuxguitar: tuxguitar

# Broken Build-Depends:
davmail: libswt-gtk-3-java
eclipse: libswt-gtk-3-java (>= 3.8.0~m6)
piccolo: libswt-gtk-3-java
tuxguitar: libswt-gtk-3-java

Dependency problem found.


jbicha@coccia:~$ dak rm -Rns testing androidsdk-tools davmail eclipse piccolo 
swt-gtk
Will remove the following packages from testing:

androidsdk-ddms | 22.2+git20130830~92d25d6-4 | all
androidsdk-hierarchyviewer | 22.2+git20130830~92d25d6-4 | all
androidsdk-tools | 22.2+git20130830~92d25d6-4 | source
androidsdk-traceview | 22.2+git20130830~92d25d6-4 | all
androidsdk-uiautomatorviewer | 22.2+git20130830~92d25d6-4 | all
   davmail | 4.8.0.2479-2 | source, all
   eclipse |   3.8.1-10 | source, all
eclipse-jdt |   3.8.1-10 | all
eclipse-pde |   3.8.1-10 | amd64, arm64, armel, armhf, i386, mips, mipsel, 
ppc64el, s390x
eclipse-platform |   3.8.1-10 | amd64, arm64, armel, armhf, i386, mips, mipsel, 
ppc64el, s390x
eclipse-platform-data |   3.8.1-10 | all
eclipse-rcp |   3.8.1-10 | amd64, arm64, armel, armhf, i386, mips, mipsel, 
ppc64el, s390x
libandroidsdk-common-java | 22.2+git20130830~92d25d6-4 | all
libandroidsdk-ddmlib-java | 22.2+git20130830~92d25d6-4 | all
libandroidsdk-ddmuilib-java | 22.2+git20130830~92d25d6-4 | all
libandroidsdk-hierarchyviewerlib-java | 22.2+git20130830~92d25d6-4 | all
libandroidsdk-sdklib-java | 22.2+git20130830~92d25d6-4 | all
libandroidsdk-sdkstats-java | 22.2+git20130830~92d25d6-4 | all
libandroidsdk-swtmenubar-java | 22.2+git20130830~92d25d6-4 | all
libequinox-osgi-java |   3.8.1-10 | all
libpiccolo-java |  1.2-1 | all
libswt-cairo-gtk-3-jni |3.8.2-4 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libswt-glx-gtk-3-jni |3.8.2-4 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libswt-gnome-gtk-3-jni |3.8.2-4 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libswt-gtk-3-java |3.8.2-4 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libswt-gtk-3-jni |3.8.2-4 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libswt-webkit-gtk-3-jni |3.8.2-4 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
   piccolo |  1.2-1 | source
   swt-gtk |3.8.2-4 | source

Maintainer: Debian Java Maintainers 
, Javier Fernández-Sanguino Peña 
, Alexandre Rossi , Debian 

Bug#878335: marked as done (haskell-x509-util FTBFS: Couldn't match expected type `[ASN1]' with actual type `B.ByteString')

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 21:34:22 +
with message-id 
and subject line Bug#878335: fixed in haskell-x509-util 1.6.4-1
has caused the Debian Bug report #878335,
regarding haskell-x509-util FTBFS: Couldn't match expected type `[ASN1]' with 
actual type `B.ByteString'
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.)


-- 
878335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-x509-util
Version: 1.6.1-3
Severity: serious
Tags: buster sid

Some recent change in unstable makes haskell-x509-util FTBFS:

https://tests.reproducible-builds.org/debian/history/haskell-x509-util.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/haskell-x509-util.html

...
Building x509-util-1.6.1...
Preprocessing executable 'x509-util' for x509-util-1.6.1...
[1 of 1] Compiling Main ( src/Certificate.hs, 
dist-ghc/build/x509-util/x509-util-tmp/Main.o )

src/Certificate.hs:69:24: error:
* Couldn't match expected type `[ASN1]'
  with actual type `B.ByteString'
* In the second argument of `showASN1', namely `asn1'
  In a stmt of a 'do' block: showASN1 8 asn1
  In the expression:
do { putStrLn
   ("  OID:  " ++ show oid ++ " critical: " ++ show critical);
 showASN1 8 asn1 }
/usr/share/cdbs/1/class/hlibrary.mk:147: recipe for target 'build-ghc-stamp' 
failed
make: *** [build-ghc-stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: haskell-x509-util
Source-Version: 1.6.4-1

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated haskell-x509-util 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 21 Oct 2017 00:15:12 +0300
Source: haskell-x509-util
Binary: x509-util
Architecture: source
Version: 1.6.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Description:
 x509-util  - utility for X.509 certificates and chains
Closes: 878335
Changes:
 haskell-x509-util (1.6.4-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #878335)
Checksums-Sha1:
 11eb77868aea2e2b5efb52678118b0cf69ae1f45 2343 haskell-x509-util_1.6.4-1.dsc
 800eb802312a1a24de1232cf1d069fee9d525267 5903 
haskell-x509-util_1.6.4.orig.tar.gz
 2e2455da66bd3c3f33d4c07a12454636b771 2848 
haskell-x509-util_1.6.4-1.debian.tar.xz
 365ba4af63176085e0bfedf5a7838e1ff0047590 7138 
haskell-x509-util_1.6.4-1_amd64.buildinfo
Checksums-Sha256:
 b209bf40bf3706ddba95ee26a4b2a78e3d2aa951e06aeb5835a614a878beb511 2343 
haskell-x509-util_1.6.4-1.dsc
 cb59f386e166b9b4708a4360316912c92794f4f01f023ab547b4d570431e6363 5903 
haskell-x509-util_1.6.4.orig.tar.gz
 920809a583dbcbecda6ff32c1bf3a27b89e93d3c8404a72ae259fe44526b152f 2848 
haskell-x509-util_1.6.4-1.debian.tar.xz
 3eed8604a1c256c6a3f45d99bf73faf758840fdb5f0ffd34ed029beb4786 7138 
haskell-x509-util_1.6.4-1_amd64.buildinfo
Files:
 b2aa9d548e3caab3666fbe738fb1ef45 2343 haskell extra 
haskell-x509-util_1.6.4-1.dsc
 dfaef8bb253ac3b2cb14406be83eed10 5903 haskell extra 
haskell-x509-util_1.6.4.orig.tar.gz
 da1546f4aa38c919e040a137565277c6 2848 haskell extra 
haskell-x509-util_1.6.4-1.debian.tar.xz
 c1a0fb6e167649eebedd4a0217868cd2 7138 haskell extra 
haskell-x509-util_1.6.4-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAlnqaCIUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDxi6xAAzpX/rG9ih34QDhZUdqM7mHfQD+Vw
w0FBwwuPplx/5mb7i93Obii73sVyWTntEGWN7cB5sfEgl0LWrclRr+BQ7zw7z+e1
y46HlxA0KEVLo2Mro7IVRmgMDpqBJwiyuAfVv1IViW+N0irfNPq5VRW+uT0yGwJj
UTex29hrvVQJ4OVJnLhvBlAHui/B6gP+Jxp4zg5LDYV/eaoOSYZThnka7RJJU/Na
mO8H9XxO/0Q6iNG//wkmO3V0jLViSz/+VjNa4N8g1/2ssjYVg7Gd1u6hHoAUM6/t
wq7vcxMDGDAgEvkf1icOwIGj7OAHKVXDyVq9EmQvzlohQFstlUUwGUaf4yOQpvbU

Bug#815632: marked as done (gnubiff: Fails to read config at startup)

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 21:05:18 +
with message-id 
and subject line Bug#815632: fixed in gnubiff 2.2.17-1
has caused the Debian Bug report #815632,
regarding gnubiff: Fails to read config at startup
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.)


-- 
815632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnubiff
Version: 2.2.15-4
Severity: normal

Dear Maintainer,

With 2.2.16-1, gnubiff fails to load the config at startup, with the error:
** (gnubiff:5100): WARNING **: Configuration file () not found!
Settings are then all default.

With 2.2.15-4, all is fine.

Giving the path to the file "gnubiff -c /home/user1/.gnubiffrc" does not help.

With strace, I see (no option given):
- 1st try: open("\270\10[\te/user1/.gnubiffrc", O_RDONLY|O_LARGEFILE)
= -1 ENOENT (No such file or directory)
- 2nd try: open("\20\210\301\te/user1/.gnubiffrc",
O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
- 3rd try: open("08h\te/user1/.gnubiffrc", O_RDONLY|O_LARGEFILE) = -1
ENOENT (No such file or directory)
which looks like a string buffer being overwritten.

Looking at the code, I followed to Options::value_string in
options.cc, but the code hasn't changed between 2.2.15-4 and 2.2.16-1
(no code has changed, actually)
I couldn't locate the dbg package to dig deeper with gdb.

Thanks!
Omen


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

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

Versions of packages gnubiff depends on:
ii  dpkg 1.18.4
ii  gconf-service3.2.6-3
ii  install-info 6.1.0.dfsg.1-2
ii  libatk1.0-0  2.16.0-2
ii  libc62.21-7
ii  libcairo-gobject21.14.2-2
ii  libcairo21.14.2-2
ii  libfam0  2.7.0-17.1+b1
ii  libgcc1  1:5.3.1-9
ii  libgconf-2-4 3.2.6-3
ii  libgdk-pixbuf2.0-0   2.31.5-1
ii  libglib2.0-0 2.46.2-3
ii  libgtk-3-0   3.16.6-1
pn  libpanel-applet-4-0  
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libpopt0 1.16-10
ii  libssl1.0.0  1.0.2d-1
ii  libstdc++6   5.3.1-9
ii  libx11-6 2:1.6.3-1
ii  sox  14.4.1-5

Versions of packages gnubiff recommends:
pn  fam  

gnubiff suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnubiff
Source-Version: 2.2.17-1

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated gnubiff 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: Fri, 20 Oct 2017 21:42:32 +0200
Source: gnubiff
Binary: gnubiff
Architecture: source
Version: 2.2.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 gnubiff- mail notification program for GNOME (and others)
Closes: 815632
Changes:
 gnubiff (2.2.17-1) unstable; urgency=medium
 .
   * QA upload.
   * New upstream release.
 + Fixes failure to read config file.  (Closes: #815632)
   * dh compat 10.
   * Prune stone age versioned dependencies.
   * Drop patches applied upstream.
Checksums-Sha1:
 85b5b8f8ebdd28f6023c814073a67ab05bf45c4b 1893 gnubiff_2.2.17-1.dsc
 c9826a3c71822ae73368ed3e2a60b43780c4ee85 897817 gnubiff_2.2.17.orig.tar.gz
 7da71dd62c976f87366190f46f99e8640cc3ef05 9372 gnubiff_2.2.17-1.debian.tar.xz
 c4cab67d75c65ab43b5ea5b1efc0bf062ec99d18 6160 gnubiff_2.2.17-1_source.buildinfo
Checksums-Sha256:
 12a8eebb5979243a98cdf88852053f4dabf7383e95bea6d92c802d8331207ff3 1893 
gnubiff_2.2.17-1.dsc
 

Bug#879228: libswt-webkit-gtk-4-jni: Missing webkit dependency

[Emmanuel Bourg]

Le 20/10/2017 à 21:40, Jeremy Bicha a écrit :

> I see a similar issue with Help>Documentation with tuxguitar 1.2-23
> (from unstable). Installing libwebkitgtk-3.0-0 fixes it. It does not
> seem to recognize libwebkit2-gtk-4.0-37. But please fix it to not need
> libwebkitgtk-3.0-0 since we are removing that unsupported version from
> Debian Testing soon.

It looks like SWT doesn't support webkit2-gtk well [1][2], upstream is
struggling to fix the remaining issues.

I'll try to upgrade sw4-gtk to the latest 4.7.1 release and see if it's
good enough to load the HTML pages in tuxguitar and azureus.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=516838
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=441568

Bug#879228: libswt-webkit-gtk-4-jni: Missing webkit dependency

[Adrian Bunk]

On Fri, Oct 20, 2017 at 03:40:33PM -0400, Jeremy Bicha wrote:
> On Fri, Oct 20, 2017 at 3:33 PM, Emmanuel Bourg  wrote:
> > Le 20/10/2017 à 20:41, Jeremy Bicha a écrit :
> >> Hopefully, this one can be fixed by just having
> >> libswt-webkit-gtk-4-jni depend on libwebkit2gtk-4.0-37
> >
> > Thank you for the hint Jeremy, this might even fix the embedded browser
> > issue I noticed with Azureus/Vuze. I'll give it a try.
> 
> I see a similar issue with Help>Documentation with tuxguitar 1.2-23
> (from unstable). Installing libwebkitgtk-3.0-0 fixes it. It does not
> seem to recognize libwebkit2-gtk-4.0-37. But please fix it to not need
> libwebkitgtk-3.0-0 since we are removing that unsupported version from
> Debian Testing soon.

The code seems to pick the wrong version when SWT_WEBKIT2 is not set:
https://sources.debian.net/src/swt4-gtk/4.6.0-2/webkitgtk.h/#L31

> Thanks,
> Jeremy Bicha

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: closing 878807

[Debian Bug Tracking System]

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

> close 878807 2:2.6-5
Bug #878807 [wpasupplicant] wpasupplicant: Please port the security fixes to 
2.6 also
Marked as fixed in versions wpa/2:2.6-5.
Bug #878807 [wpasupplicant] wpasupplicant: Please port the security fixes to 
2.6 also
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#879228: libswt-webkit-gtk-4-jni: Missing webkit dependency

[Jeremy Bicha]

On Fri, Oct 20, 2017 at 3:33 PM, Emmanuel Bourg  wrote:
> Le 20/10/2017 à 20:41, Jeremy Bicha a écrit :
>> Hopefully, this one can be fixed by just having
>> libswt-webkit-gtk-4-jni depend on libwebkit2gtk-4.0-37
>
> Thank you for the hint Jeremy, this might even fix the embedded browser
> issue I noticed with Azureus/Vuze. I'll give it a try.

I see a similar issue with Help>Documentation with tuxguitar 1.2-23
(from unstable). Installing libwebkitgtk-3.0-0 fixes it. It does not
seem to recognize libwebkit2-gtk-4.0-37. But please fix it to not need
libwebkitgtk-3.0-0 since we are removing that unsupported version from
Debian Testing soon.

Thanks,
Jeremy Bicha

Bug#878807: closing 878807

[Salvatore Bonaccorso]

close 878807 2:2.6-5
thanks

There was an 2:2.6-5 upload incorporating the CVE fixes but this bug was
not closes. Doing so manually now.

Bug#879231: ruby2.3: CVE-2017-0903: Unsafe object deserialization through YAML formatted gem specifications

[Salvatore Bonaccorso]

Source: ruby2.3
Version: 2.3.3-1
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for ruby2.3.

CVE-2017-0903[0]:
| RubyGems versions between 2.0.0 and 2.6.13 are vulnerable to a
| possible remote code execution vulnerability. YAML deserialization of
| gem specifications can bypass class white lists. Specially crafted
| serialized objects can possibly be used to escalate to remote code
| execution.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-0903
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0903
[1] http://www.openwall.com/lists/oss-security/2017/10/10/2
[2] 
https://github.com/rubygems/rubygems/commit/510b1638ac9bba3ceb7a5d73135dafff9e5bab49

Regards,
Salvatore

Bug#879228: libswt-webkit-gtk-4-jni: Missing webkit dependency

[Emmanuel Bourg]

Le 20/10/2017 à 20:41, Jeremy Bicha a écrit :
> Hopefully, this one can be fixed by just having
> libswt-webkit-gtk-4-jni depend on libwebkit2gtk-4.0-37

Thank you for the hint Jeremy, this might even fix the embedded browser
issue I noticed with Azureus/Vuze. I'll give it a try.

Emmanuel Bourg

Processed: Fixed upstream

[Debian Bug Tracking System]

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

> tags 876725 + fixed-upstream
Bug #876725 [src:ppx-deriving] ppx-deriving FTBFS with OCaml 4.05.0
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#876725: Fixed upstream

[Andreas Stührk]

tags 876725 + fixed-upstream
thanks

This was fixed upstream in 4.2 (
https://github.com/ocaml-ppx/ppx_deriving/commit/b6b02c2ba051bde67c2b454724ff0bf36bc11060
)

Bug#879222: marked as done (haskell-heist FTBFS: Encountered missing dependencies: vector >=0.9 && <0.12)

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 19:04:10 +
with message-id 
and subject line Bug#879222: fixed in haskell-heist 1.0.1.0-3
has caused the Debian Bug report #879222,
regarding haskell-heist FTBFS: Encountered missing dependencies: vector >=0.9 
&& <0.12
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.)


-- 
879222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-heist
Version: 1.0.1.0-2
Severity: serious

https://buildd.debian.org/status/package.php?p=haskell-heist=sid

...
[1 of 1] Compiling Main ( Setup.hs, Setup.o )
Linking debian/hlibrary.setup ...
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
configure_recipe
Running debian/hlibrary.setup configure --ghc -v2 
--package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
--libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
--builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro 
--haddockdir=/usr/lib/ghc-doc/haddock/heist-1.0.1.0/ --datasubdir=heist 
--htmldir=/usr/share/doc/libghc-heist-doc/html/ --enable-library-profiling
Configuring heist-1.0.1.0...
hlibrary.setup: Encountered missing dependencies:
vector >=0.9 && <0.12
/usr/share/cdbs/1/class/hlibrary.mk:142: recipe for target 
'configure-ghc-stamp' failed
make: *** [configure-ghc-stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: haskell-heist
Source-Version: 1.0.1.0-3

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated haskell-heist 
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: Fri, 20 Oct 2017 21:44:50 +0300
Source: haskell-heist
Binary: libghc-heist-dev libghc-heist-prof libghc-heist-doc
Architecture: source
Version: 1.0.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Description:
 libghc-heist-dev - ${haskell:ShortDescription}${haskell:ShortBlurb}
 libghc-heist-doc - ${haskell:ShortDescription}${haskell:ShortBlurb}
 libghc-heist-prof - ${haskell:ShortDescription}${haskell:ShortBlurb}
Closes: 879222
Changes:
 haskell-heist (1.0.1.0-3) unstable; urgency=medium
 .
   * Patch in order to work with newer versions of
 haskell-vector (Closes: #879222)
Checksums-Sha1:
 91915fc5a44758deb8ed68b927a150ae24ec1546 4345 haskell-heist_1.0.1.0-3.dsc
 57daf394faf1672ef8896d5d8b1009a2a0bd3137 4312 
haskell-heist_1.0.1.0-3.debian.tar.xz
 a5dd46891da72f4cdf876fce3dc52a44eb07a86a 5666 
haskell-heist_1.0.1.0-3_source.buildinfo
Checksums-Sha256:
 56b99bc5b84d5b1550b26295d7f3303b14103c307ba590e464abda206e307c3e 4345 
haskell-heist_1.0.1.0-3.dsc
 c8afc32ae81b0f721bcd47b2805df43708c4b0c31ebdb91e5e1f8bdd1a7f1dad 4312 
haskell-heist_1.0.1.0-3.debian.tar.xz
 df8b7cb5ef41a0884c0a4909e465b356b73e210d03b6e0261e2e1a9e1174d03c 5666 
haskell-heist_1.0.1.0-3_source.buildinfo
Files:
 6f5dc977a1bd09bb377f4c970073843b 4345 haskell extra haskell-heist_1.0.1.0-3.dsc
 b4cd0ae52b57e6e45b9b4480707ba3cd 4312 haskell extra 
haskell-heist_1.0.1.0-3.debian.tar.xz
 be9e1aa3fc94534ed9ee1723fb32295f 5666 haskell extra 
haskell-heist_1.0.1.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAlnqRpQUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDw8Ag/+JH3vh7VFHISfL+ax2H5/Mjx13mTu
q2ba1gDjJWijyQFQlOE4JxvP0JmAUQTlwEVMrPNtdp/6vqhazdKMiA0IlAaVVmRC
rT+7xZkwKmEdM7m0SWoLuxZ2QWR+S0+HZny1AFYSH0meeMYmA1UZiX2t7llbIsx5
jsJgr/j1UhwaphZTRxgsM/jetBHDq8fPVcFgUDwP803Lh7uAN+MIc3iu6X14Z5ws
dUyM276i+KlmnDjg3vR72cHd0P56ObMraPz6HGhfdLwAZOOWIpEir2XxEqu+giF7
Tbf48uldJXDr80eLxdpmsa6LwMT6hPpfX/uSg4vBGm1wy9ettCfDO+xCIF03/oYl
60ZtF/7C9jCpKIPZIbjl7SbkpPAPJ5b5eAzx+sGvQLC3FV+t1pc3QR+86tSz3vWh
PaihuhqkBGxGYCRPhrB+fyGYnt0GQABEC0mqvUmcPlFdsY+H3pq9OggUrdf3moZL
DobQylXWvx6U8MaI3dAnavIFH8PZuMFYne09l1pYr2R0AnVoFNi8AZqmXJklSMdx

Processed: bug 879190 is forwarded to http://www.openwall.com/lists/musl/2017/10/20/8

[Debian Bug Tracking System]

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

> forwarded 879190 http://www.openwall.com/lists/musl/2017/10/20/8
Bug #879190 {Done: Reiner Herrmann } [src:musl] musl FTBFS 
on armel: Error: selected processor does not support clz
Set Bug forwarded-to-address to 
'http://www.openwall.com/lists/musl/2017/10/20/8'.
> thanks
Stopping processing here.

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

Bug#878834: marked as done (freetype: Upgrade to 2.8.1 breaks font rendering in various applications)

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 19:00:32 +
with message-id 
and subject line Bug#878870: fixed in thunderbird 1:52.4.0-1
has caused the Debian Bug report #878870,
regarding freetype: Upgrade to 2.8.1 breaks font rendering in various 
applications
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.)


-- 
878870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freetype
Version: 2.8.1-0.1
Severity: important

Dear Maintainer,

I upgraded freetype from 2.8.0 to 2.8.1 today and font rendering in both 
thunderbird and discord
took a really steep nosedive.

Freetype 2.8.0: https://imgur.com/8QLHYDK
Freetype 2.8.1: https://imgur.com/TtDN0pE

Thanks
Christian


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

Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:52.4.0-1

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
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, 17 Oct 2017 18:20:29 +0200
Source: thunderbird
Binary: thunderbird icedove thunderbird-dev icedove-dev thunderbird-dbg 
icedove-dbg lightning iceowl-extension calendar-google-provider 
thunderbird-l10n-all thunderbird-l10n-ar thunderbird-l10n-ast 
thunderbird-l10n-be thunderbird-l10n-bg thunderbird-l10n-bn-bd 
thunderbird-l10n-br thunderbird-l10n-ca thunderbird-l10n-cs thunderbird-l10n-da 
thunderbird-l10n-de thunderbird-l10n-dsb thunderbird-l10n-el 
thunderbird-l10n-en-gb thunderbird-l10n-es-ar thunderbird-l10n-es-es 
thunderbird-l10n-et thunderbird-l10n-eu thunderbird-l10n-fi thunderbird-l10n-fr 
thunderbird-l10n-fy-nl thunderbird-l10n-ga-ie thunderbird-l10n-gd 
thunderbird-l10n-gl thunderbird-l10n-he thunderbird-l10n-hr 
thunderbird-l10n-hsb thunderbird-l10n-hu thunderbird-l10n-hy-am 
thunderbird-l10n-id thunderbird-l10n-is thunderbird-l10n-it thunderbird-l10n-ja 
thunderbird-l10n-kab thunderbird-l10n-ko thunderbird-l10n-lt 
thunderbird-l10n-nb-no thunderbird-l10n-nl thunderbird-l10n-nn-no 
thunderbird-l10n-pa-in
 thunderbird-l10n-pl thunderbird-l10n-pt-br thunderbird-l10n-pt-pt 
thunderbird-l10n-rm thunderbird-l10n-ro thunderbird-l10n-ru thunderbird-l10n-si 
thunderbird-l10n-sk thunderbird-l10n-sl thunderbird-l10n-sq thunderbird-l10n-sr 
thunderbird-l10n-sv-se thunderbird-l10n-ta-lk thunderbird-l10n-tr 
thunderbird-l10n-uk thunderbird-l10n-vi thunderbird-l10n-zh-cn 
thunderbird-l10n-zh-tw icedove-l10n-all icedove-l10n-ar icedove-l10n-ast 
icedove-l10n-be icedove-l10n-bg icedove-l10n-bn-bd icedove-l10n-br 
icedove-l10n-ca icedove-l10n-cs icedove-l10n-da icedove-l10n-de 
icedove-l10n-dsb icedove-l10n-el icedove-l10n-en-gb icedove-l10n-es-ar 
icedove-l10n-es-es icedove-l10n-et icedove-l10n-eu icedove-l10n-fi 
icedove-l10n-fr icedove-l10n-fy-nl icedove-l10n-ga-ie icedove-l10n-gd 
icedove-l10n-gl icedove-l10n-he icedove-l10n-hr icedove-l10n-hsb 
icedove-l10n-hu icedove-l10n-hy-am icedove-l10n-id icedove-l10n-is 
icedove-l10n-it icedove-l10n-ja icedove-l10n-kab icedove-l10n-ko icedove-l10n-lt
 icedove-l10n-nb-no icedove-l10n-nl icedove-l10n-nn-no icedove-l10n-pa-in 
icedove-l10n-pl icedove-l10n-pt-br icedove-l10n-pt-pt icedove-l10n-rm 
icedove-l10n-ro icedove-l10n-ru icedove-l10n-si icedove-l10n-sk icedove-l10n-sl 
icedove-l10n-sq icedove-l10n-sr icedove-l10n-sv-se icedove-l10n-ta-lk 
icedove-l10n-tr icedove-l10n-uk icedove-l10n-vi icedove-l10n-zh-cn 
icedove-l10n-zh-tw lightning-l10n-ar lightning-l10n-ast 

Bug#878929: marked as done (libfreetype6: font rendering broken in electron applications)

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 19:00:32 +
with message-id 
and subject line Bug#878870: fixed in thunderbird 1:52.4.0-1
has caused the Debian Bug report #878870,
regarding libfreetype6: font rendering broken in electron applications
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.)


-- 
878870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfreetype6
Version: 2.8.1-0.1
Severity: normal

Dear Maintainer,

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

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

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

Font rendering in electron applications is now broken (eg basic electron sample
applications/discord).  Building manually this problem does not exist:

apt-get source libfreetype6
cd freetype-2.8.1/
tar xfj freetype-2.8.1.tar.bz2
cd freetype-2.8.1
./configure --without-bzip2 --without-harfbuzz
make -j4
LD_PRELOAD=./objs/.libs/libfreetype.so ~/discordapp/Discord #or other electron
app



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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:52.4.0-1

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
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, 17 Oct 2017 18:20:29 +0200
Source: thunderbird
Binary: thunderbird icedove thunderbird-dev icedove-dev thunderbird-dbg 
icedove-dbg lightning iceowl-extension calendar-google-provider 
thunderbird-l10n-all thunderbird-l10n-ar thunderbird-l10n-ast 
thunderbird-l10n-be thunderbird-l10n-bg thunderbird-l10n-bn-bd 
thunderbird-l10n-br thunderbird-l10n-ca thunderbird-l10n-cs thunderbird-l10n-da 
thunderbird-l10n-de thunderbird-l10n-dsb thunderbird-l10n-el 
thunderbird-l10n-en-gb thunderbird-l10n-es-ar thunderbird-l10n-es-es 
thunderbird-l10n-et thunderbird-l10n-eu thunderbird-l10n-fi thunderbird-l10n-fr 
thunderbird-l10n-fy-nl thunderbird-l10n-ga-ie thunderbird-l10n-gd 
thunderbird-l10n-gl thunderbird-l10n-he thunderbird-l10n-hr 
thunderbird-l10n-hsb thunderbird-l10n-hu thunderbird-l10n-hy-am 
thunderbird-l10n-id thunderbird-l10n-is thunderbird-l10n-it thunderbird-l10n-ja 
thunderbird-l10n-kab thunderbird-l10n-ko thunderbird-l10n-lt 
thunderbird-l10n-nb-no thunderbird-l10n-nl thunderbird-l10n-nn-no 
thunderbird-l10n-pa-in
 thunderbird-l10n-pl thunderbird-l10n-pt-br thunderbird-l10n-pt-pt 
thunderbird-l10n-rm thunderbird-l10n-ro thunderbird-l10n-ru thunderbird-l10n-si 
thunderbird-l10n-sk thunderbird-l10n-sl thunderbird-l10n-sq thunderbird-l10n-sr 
thunderbird-l10n-sv-se thunderbird-l10n-ta-lk thunderbird-l10n-tr 
thunderbird-l10n-uk thunderbird-l10n-vi thunderbird-l10n-zh-cn 
thunderbird-l10n-zh-tw icedove-l10n-all icedove-l10n-ar icedove-l10n-ast 
icedove-l10n-be icedove-l10n-bg icedove-l10n-bn-bd icedove-l10n-br 
icedove-l10n-ca icedove-l10n-cs icedove-l10n-da icedove-l10n-de 
icedove-l10n-dsb icedove-l10n-el icedove-l10n-en-gb icedove-l10n-es-ar 
icedove-l10n-es-es icedove-l10n-et icedove-l10n-eu icedove-l10n-fi 
icedove-l10n-fr icedove-l10n-fy-nl icedove-l10n-ga-ie icedove-l10n-gd 
icedove-l10n-gl icedove-l10n-he icedove-l10n-hr icedove-l10n-hsb 
icedove-l10n-hu icedove-l10n-hy-am icedove-l10n-id icedove-l10n-is 
icedove-l10n-it icedove-l10n-ja icedove-l10n-kab icedove-l10n-ko icedove-l10n-lt
 

Bug#878870: marked as done (freetype 2.8.1 breaks font rendering)

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 19:00:32 +
with message-id 
and subject line Bug#878870: fixed in thunderbird 1:52.4.0-1
has caused the Debian Bug report #878870,
regarding freetype 2.8.1 breaks font rendering
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.)


-- 
878870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird,libfreetype6
Version: libfreetype6/2.8.1-0.1
Severity: serious
Tags: patch fixed-upstream upstream
Forwarded: https://bugzilla.mozilla.org/show_bug.cgi?id=1409188

Hi,

freetype 2.8.1 breaks fonts when using subpixel rendering.

This is already fixed in firefox[1], the same code is also present in
thunderbird and I guess the same patch can be used there.

Could you please have a look at fixing thunderbird?

Regards,

Laurent Bigonville

[1] https://hg.mozilla.org/releases/mozilla-release/rev/8fe8227e5080
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:52.4.0-1

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
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, 17 Oct 2017 18:20:29 +0200
Source: thunderbird
Binary: thunderbird icedove thunderbird-dev icedove-dev thunderbird-dbg 
icedove-dbg lightning iceowl-extension calendar-google-provider 
thunderbird-l10n-all thunderbird-l10n-ar thunderbird-l10n-ast 
thunderbird-l10n-be thunderbird-l10n-bg thunderbird-l10n-bn-bd 
thunderbird-l10n-br thunderbird-l10n-ca thunderbird-l10n-cs thunderbird-l10n-da 
thunderbird-l10n-de thunderbird-l10n-dsb thunderbird-l10n-el 
thunderbird-l10n-en-gb thunderbird-l10n-es-ar thunderbird-l10n-es-es 
thunderbird-l10n-et thunderbird-l10n-eu thunderbird-l10n-fi thunderbird-l10n-fr 
thunderbird-l10n-fy-nl thunderbird-l10n-ga-ie thunderbird-l10n-gd 
thunderbird-l10n-gl thunderbird-l10n-he thunderbird-l10n-hr 
thunderbird-l10n-hsb thunderbird-l10n-hu thunderbird-l10n-hy-am 
thunderbird-l10n-id thunderbird-l10n-is thunderbird-l10n-it thunderbird-l10n-ja 
thunderbird-l10n-kab thunderbird-l10n-ko thunderbird-l10n-lt 
thunderbird-l10n-nb-no thunderbird-l10n-nl thunderbird-l10n-nn-no 
thunderbird-l10n-pa-in
 thunderbird-l10n-pl thunderbird-l10n-pt-br thunderbird-l10n-pt-pt 
thunderbird-l10n-rm thunderbird-l10n-ro thunderbird-l10n-ru thunderbird-l10n-si 
thunderbird-l10n-sk thunderbird-l10n-sl thunderbird-l10n-sq thunderbird-l10n-sr 
thunderbird-l10n-sv-se thunderbird-l10n-ta-lk thunderbird-l10n-tr 
thunderbird-l10n-uk thunderbird-l10n-vi thunderbird-l10n-zh-cn 
thunderbird-l10n-zh-tw icedove-l10n-all icedove-l10n-ar icedove-l10n-ast 
icedove-l10n-be icedove-l10n-bg icedove-l10n-bn-bd icedove-l10n-br 
icedove-l10n-ca icedove-l10n-cs icedove-l10n-da icedove-l10n-de 
icedove-l10n-dsb icedove-l10n-el icedove-l10n-en-gb icedove-l10n-es-ar 
icedove-l10n-es-es icedove-l10n-et icedove-l10n-eu icedove-l10n-fi 
icedove-l10n-fr icedove-l10n-fy-nl icedove-l10n-ga-ie icedove-l10n-gd 
icedove-l10n-gl icedove-l10n-he icedove-l10n-hr icedove-l10n-hsb 
icedove-l10n-hu icedove-l10n-hy-am icedove-l10n-id icedove-l10n-is 
icedove-l10n-it icedove-l10n-ja icedove-l10n-kab icedove-l10n-ko icedove-l10n-lt
 icedove-l10n-nb-no icedove-l10n-nl icedove-l10n-nn-no icedove-l10n-pa-in 
icedove-l10n-pl icedove-l10n-pt-br icedove-l10n-pt-pt icedove-l10n-rm 
icedove-l10n-ro icedove-l10n-ru icedove-l10n-si icedove-l10n-sk icedove-l10n-sl 
icedove-l10n-sq icedove-l10n-sr icedove-l10n-sv-se icedove-l10n-ta-lk 
icedove-l10n-tr icedove-l10n-uk icedove-l10n-vi icedove-l10n-zh-cn 
icedove-l10n-zh-tw lightning-l10n-ar lightning-l10n-ast lightning-l10n-be 
lightning-l10n-bg lightning-l10n-bn-bd lightning-l10n-br lightning-l10n-ca 
lightning-l10n-cs lightning-l10n-cy lightning-l10n-da lightning-l10n-de 
lightning-l10n-dsb lightning-l10n-el lightning-l10n-es-ar lightning-l10n-es-es 

Bug#877299: marked as done (haskell-tls FTBFS: Couldn't match expected type `B.ByteString' with actual type `[asn1-types-0.3.2:Data.ASN1.Types.ASN1]')

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 18:48:55 +
with message-id 
and subject line Bug#877299: fixed in haskell-tls 1.3.11-2
has caused the Debian Bug report #877299,
regarding haskell-tls FTBFS: Couldn't match expected type `B.ByteString' with 
actual type `[asn1-types-0.3.2:Data.ASN1.Types.ASN1]'
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.)


-- 
877299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-tls
Version: 1.3.11-1
Severity: serious

https://buildd.debian.org/status/package.php?p=haskell-tls=sid

...
[4 of 7] Compiling Certificate  ( Tests/Certificate.hs, 
dist-ghc/build/test-tls/test-tls-tmp/Certificate.o )

Tests/Certificate.hs:17:72: error:
* Couldn't match expected type `B.ByteString'
  with actual type `[asn1-types-0.3.2:Data.ASN1.Types.ASN1]'
* In the third argument of `ExtensionRaw', namely `(extEncode ext)'
  In the expression:
ExtensionRaw (extOID ext) critical (extEncode ext)
  In an equation for `testExtensionEncode':
  testExtensionEncode critical ext
= ExtensionRaw (extOID ext) critical (extEncode ext)
/usr/share/cdbs/1/class/hlibrary.mk:147: recipe for target 'build-ghc-stamp' 
failed
make: *** [build-ghc-stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: haskell-tls
Source-Version: 1.3.11-2

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated haskell-tls 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: Fri, 20 Oct 2017 21:24:15 +0300
Source: haskell-tls
Binary: libghc-tls-dev libghc-tls-prof libghc-tls-doc
Architecture: source
Version: 1.3.11-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Description:
 libghc-tls-dev - native Haskell implementation of TLS/SSL protocol
 libghc-tls-doc - native Haskell implementation of TLS/SSL protocol
 libghc-tls-prof - native Haskell implementation of TLS/SSL protocol
Closes: 877299
Changes:
 haskell-tls (1.3.11-2) unstable; urgency=medium
 .
   * Backport upstream patch from v1.4.0 to work with newer
 haskell-x509 (Closes: #877299)
Checksums-Sha1:
 be7fb7137df78b148478ad944d95872ceeb05482 3229 haskell-tls_1.3.11-2.dsc
 1f9bd174466987a179ff3ee4b6685c14de14ff28 4292 
haskell-tls_1.3.11-2.debian.tar.xz
 1222e5be3b905af51de3d086aac3b6a29a8c8cb6 9714 
haskell-tls_1.3.11-2_amd64.buildinfo
Checksums-Sha256:
 957998063d6d81cbfa7ba2c89e5ae0977cbdc417be356b3250c05ca979ff712b 3229 
haskell-tls_1.3.11-2.dsc
 36dd47b4ffc611bf3a15f75ea54aa1832bbec8fd38e591e9e5c4f337aaf274c4 4292 
haskell-tls_1.3.11-2.debian.tar.xz
 11bee74cac89a0515944a982f2def277b947724dc53a65ab42ec6fb37a34241c 9714 
haskell-tls_1.3.11-2_amd64.buildinfo
Files:
 f11ca9eb809991f5a2672f3538fa12c3 3229 haskell extra haskell-tls_1.3.11-2.dsc
 6c34534e992fea1322fa085f55e399e3 4292 haskell extra 
haskell-tls_1.3.11-2.debian.tar.xz
 9367f63b8faee26bc545f458b9007d18 9714 haskell extra 
haskell-tls_1.3.11-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAlnqQjcUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDzhnA/+KiaB7HDEPluy5XQYuUBlHH26/kVb
/GfJjX/eUjIkPiJcjOfMXdBZ8JHJHSks0kmT96wyLv5MZkAd9NfiQxSEuudDyo3H
1SaP93ho+x1IOGpqq/NH0Eq+OnCe1ueAFZhMBgOcTv4TxncBpt+2dKxjIjtEcYSW
Jbq/P1F9xBFkiRHL6wexRDZCKeYNibyDO6tw/0U2DTJTOzedUiSM6hr458rgn5FP
aEfzobrfd2MHS0ZJw5XZkxGACLD9O2BYEW6Ql4hS1X/kJMej4ycR/bjucqjis9Z9
IyJS4EOZWOeDpeEk3bcSpzCfVWIDQvBl5tJAW9bYl1H20BWKY6tR3tGWo+hRLs0A
1tqAOakoDiITLP7H99bNv9HzCAkPBWO9Ycfw0nqtbMuaRS2Ow0DXZmCrg8t4WYU5
kb8iFVegmT4xxSGxGNWiWI38lYRu2SL7DWZ9JrF+IkEHgk8mrthPg3B9Ng7tft8N
BH1Z8ZXpZBVTwEZfIRE9arJr0NsL6yguARZloxNnUhDb0uHIa0g1YkxAP7wLQ0dz
NT+L3TFeT9KapQfZ5fhH+JAZU0qxCfvNPxagz86Sw1Y0EKF+KymI7Dlg6DwCynCo

Bug#866635: cyclograph: depends on libwebkitgtk-3.0-0 which is deprecated

[Federico Brega]

Hi Jeremy,
there is RFS for cyclograph https://bugs.debian.org/869692
I think we should discuss packaging there.

Thanks for your help
--
Federico

Bug#879228: libswt-webkit-gtk-4-jni: Missing webkit dependency

[Jeremy Bicha]

Hopefully, this one can be fixed by just having
libswt-webkit-gtk-4-jni depend on libwebkit2gtk-4.0-37

Thanks,
Jeremy Bicha

Bug#871964: swt-gtk: Build-depends on libwebkitgtk-dev which is deprecated

[Adrian Bunk]

Control: tags 879170 - buster sid
Control: clone 879170 -2
Control: reassign 879170 libswt-webkit-gtk-3-jni
Control: reassign -2 libswt-webkit-gtk-4-jni
Control: retitle -2 libswt-webkit-gtk-4-jni: Missing webkit dependency

On Thu, Oct 19, 2017 at 08:22:26PM -0400, Jeremy Bicha wrote:
>...
> On Tue, Oct 17, 2017 at 5:12 PM, Adrian Bunk  wrote:
> > On Sat, Aug 12, 2017 at 11:43:58PM -0400, Jeremy Bicha wrote:
> >>...
> >> The package does build successfully without the libwebkitgtk-dev
> >> build-dependency.
> >
> > But the resulting library will still dynamically load it.
> >
> >> It feels to me like the libswt-webkit-gtk-3-jni was already broken
> >> since it doesn't have a dependency on any webkitgtk library
> >
> > The missing dependency sounds like a bug.
> >
> >> (I think
> >> the correct one would be libwebkitgtk-3.0-0 but that is still part of
> >> the deprecated libraries which are being removed.)
> >
> > It does use libwebkitgtk-1.0-0:
> > https://sources.debian.net/src/swt-gtk/3.8.2-4/webkitgtk.h/
> >
> > I just tried, and it does work when libwebkitgtk-1.0-0 is installed
> > (and fails without).
> 
> Ok, I am filing a new bug because the missing dependency should be
> fixed in stretch.

Thanks, I'm cloning this for libswt-webkit-gtk-4-jni which has
the same problem of the missing dependency.

> This link says that Eclipse / swt-gtk 4.4 (released in 2014) has
> initial support for gtk3 and webkit2gtk:
> https://www.eclipse.org/swt/R4_4/new_and_noteworthy.html
> 
> Unfortunately, eclipse and swt-gtk are very outdated in Debian:
>...

Current SWT is in src:swt4-gtk.

> Thank you,
> Jeremy Bicha

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#871964: swt-gtk: Build-depends on libwebkitgtk-dev which is deprecated

[Debian Bug Tracking System]

Processing control commands:

> tags 879170 - buster sid
Bug #879170 [src:swt-gtk] libswt-webkit-gtk-3-jni: Needs libwebkitgtk-1.0-0 dep
Removed tag(s) buster and sid.
> clone 879170 -2
Bug #879170 [src:swt-gtk] libswt-webkit-gtk-3-jni: Needs libwebkitgtk-1.0-0 dep
Bug 879170 cloned as bug 879228
> reassign 879170 libswt-webkit-gtk-3-jni
Bug #879170 [src:swt-gtk] libswt-webkit-gtk-3-jni: Needs libwebkitgtk-1.0-0 dep
Bug reassigned from package 'src:swt-gtk' to 'libswt-webkit-gtk-3-jni'.
Ignoring request to alter found versions of bug #879170 to the same values 
previously set
Ignoring request to alter fixed versions of bug #879170 to the same values 
previously set
> reassign -2 libswt-webkit-gtk-4-jni
Bug #879228 [src:swt-gtk] libswt-webkit-gtk-3-jni: Needs libwebkitgtk-1.0-0 dep
Bug reassigned from package 'src:swt-gtk' to 'libswt-webkit-gtk-4-jni'.
Ignoring request to alter found versions of bug #879228 to the same values 
previously set
Ignoring request to alter fixed versions of bug #879228 to the same values 
previously set
> retitle -2 libswt-webkit-gtk-4-jni: Missing webkit dependency
Bug #879228 [libswt-webkit-gtk-4-jni] libswt-webkit-gtk-3-jni: Needs 
libwebkitgtk-1.0-0 dep
Changed Bug title to 'libswt-webkit-gtk-4-jni: Missing webkit dependency' from 
'libswt-webkit-gtk-3-jni: Needs libwebkitgtk-1.0-0 dep'.

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

Bug#878841: closed by Javier Fernández-Sanguino Peña <j...@debian.org> (Bug#878841: fixed in clips 6.30-2)

[Adrian Bunk]

Control: reopen -1

On Tue, Oct 17, 2017 at 09:51:06PM +, Debian Bug Tracking System wrote:
>...
>  clips (6.30-2) unstable; urgency=medium
>  .
>* debian/control:
>   - Add sharutils to Build-Deps as it is required for building the
> documentation (Closes: #878841)
>...

Adding it to Build-Depends-Indep cannot fix the binary-any FTBFS:
https://buildd.debian.org/status/package.php?p=clips

Either building the documentation has to be restricted when building the 
binary-all packages, or this must be moved to Build-Depends.

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#878841 closed by Javier Fernández-Sanguino Peña <j...@debian.org> (Bug#878841: fixed in clips 6.30-2)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #878841 {Done: Javier Fernández-Sanguino Peña } 
[src:clips] clips FTBFS: uudecode: not found
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions clips/6.30-2.

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

Bug#879082: marked as done (haskell-linear FTBFS: Duplicate instance declarations)

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 18:04:55 +
with message-id 
and subject line Bug#879082: fixed in haskell-linear 1.20.7-1
has caused the Debian Bug report #879082,
regarding haskell-linear FTBFS: Duplicate instance declarations
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.)


-- 
879082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-linear
Version: 1.20.6-1
Severity: serious

https://buildd.debian.org/status/package.php?p=haskell-linear=sid

...
Preprocessing library linear-1.20.6...
[ 1 of 22] Compiling Linear.Instances ( src/Linear/Instances.hs, 
dist-ghc/build/Linear/Instances.o )

src/Linear/Instances.hs:30:10: error:
Duplicate instance declarations:
  instance (Hashable k, Eq k) => Apply (HashMap k)
-- Defined at src/Linear/Instances.hs:30:10
  instance [safe] (Hashable k, Eq k) => Apply (HashMap k)
-- Defined in `Data.Functor.Bind.Class'

src/Linear/Instances.hs:33:10: error:
Duplicate instance declarations:
  instance (Hashable k, Eq k) => Bind (HashMap k)
-- Defined at src/Linear/Instances.hs:33:10
  instance [safe] (Hashable k, Eq k) => Bind (HashMap k)
-- Defined in `Data.Functor.Bind.Class'

src/Linear/Instances.hs:41:10: error:
Duplicate instance declarations:
  instance Apply Complex -- Defined at src/Linear/Instances.hs:41:10
  instance [safe] Apply Complex
-- Defined in `Data.Functor.Bind.Class'

src/Linear/Instances.hs:44:10: error:
Duplicate instance declarations:
  instance Bind Complex -- Defined at src/Linear/Instances.hs:44:10
  instance [safe] Bind Complex
-- Defined in `Data.Functor.Bind.Class'

src/Linear/Instances.hs:56:10: error:
Duplicate instance declarations:
  instance Foldable1 Complex
-- Defined at src/Linear/Instances.hs:56:10
  instance [safe] Foldable1 Complex
-- Defined in `Data.Semigroup.Foldable.Class'

src/Linear/Instances.hs:60:10: error:
Duplicate instance declarations:
  instance Traversable1 Complex
-- Defined at src/Linear/Instances.hs:60:10
  instance [safe] Traversable1 Complex
-- Defined in `Data.Semigroup.Traversable.Class'
/usr/share/cdbs/1/class/hlibrary.mk:147: recipe for target 'build-ghc-stamp' 
failed
make: *** [build-ghc-stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: haskell-linear
Source-Version: 1.20.7-1

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated haskell-linear 
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: Fri, 20 Oct 2017 20:45:48 +0300
Source: haskell-linear
Binary: libghc-linear-dev libghc-linear-prof libghc-linear-doc
Architecture: source
Version: 1.20.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Description:
 libghc-linear-dev -
 libghc-linear-doc -
 libghc-linear-prof -
Closes: 879082
Changes:
 haskell-linear (1.20.7-1) unstable; urgency=medium
 .
   [ Sean Whitton ]
   * New upstream release (Closes: #879082)
 .
   [ Ilias Tsitsimpis ]
   * Add missing copyright holder
Checksums-Sha1:
 933c7b4e60054d81cf2e5a2920c6ab9576828505 3909 haskell-linear_1.20.7-1.dsc
 307c26cea8222034b6399b7e125abf1db2a73c62 48183 
haskell-linear_1.20.7.orig.tar.gz
 269b494378b060d02d7257da5d0bc766d7cb6adc 2840 
haskell-linear_1.20.7-1.debian.tar.xz
 51df5ed29eca40634682865248d0b2ee46849774 10322 
haskell-linear_1.20.7-1_amd64.buildinfo
Checksums-Sha256:
 c4c77b9b48c066be6fc72e331ae2fcebd9c4b9a09b2269ff13198409af96baba 3909 
haskell-linear_1.20.7-1.dsc
 4b88b6268d327220a296b6790c82db8ebab52973735af0a9de1c734cdc07cab6 48183 
haskell-linear_1.20.7.orig.tar.gz
 60c8609354acc3cf3e5a19466e6f35d531133c4610b45c9cd7cf7ceb3505f5bb 2840 

Processed: Re: gnome-documents: 3.26 FTBFS on mips during cairo configure check

[Debian Bug Tracking System]

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

> reassign 878431 gjs
Bug #878431 [src:gnome-documents] gnome-documents: 3.26 FTBFS on mips during 
cairo configure check
Bug reassigned from package 'src:gnome-documents' to 'gjs'.
No longer marked as found in versions gnome-documents/3.26.1-1.
Ignoring request to alter fixed versions of bug #878431 to the same values 
previously set
> forcemerge 878519 878431
Bug #878519 {Done: Jeremy Bicha } [gjs] gjs: doesn't seem to 
work on mips (at least on minkus and mips-aql-01)
Bug #878431 [gjs] gnome-documents: 3.26 FTBFS on mips during cairo configure 
check
Severity set to 'serious' from 'important'
878582 was blocked by: 878519
878582 was not blocking any bugs.
Added blocking bug(s) of 878582: 878431
Marked Bug as done
Added indication that 878431 affects src:gnome-documents
Marked as fixed in versions mozjs52/52.3.1-6.
Marked as found in versions gjs/1.50.1-2.
Merged 878431 878519
>
End of message, stopping processing here.

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

Bug#879190: marked as done (musl FTBFS on armel: Error: selected processor does not support clz)

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 17:49:54 +
with message-id 
and subject line Bug#879190: fixed in musl 1.1.17-2
has caused the Debian Bug report #879190,
regarding musl FTBFS on armel: Error: selected processor does not support clz
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.)


-- 
879190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: musl
Version: 1.1.17-1
Severity: serious
Tags: patch

https://buildd.debian.org/status/fetch.php?pkg=musl=armel=1.1.17-1=1508450839=0

...
{standard input}: Assembler messages:
{standard input}:625: Error: selected processor does not support `clz r0,r9' in 
ARM mode
{standard input}:953: Error: selected processor does not support `clz r3,r7' in 
ARM mode
{standard input}:1010: Error: selected processor does not support `clz r3,r6' 
in ARM mode
{standard input}:1148: Error: selected processor does not support `clz r0,r3' 
in ARM mode
Makefile:164: recipe for target 'obj/src/math/fma.lo' failed
make[1]: *** [obj/src/math/fma.lo] Error 1


Fix is attached.
Description: CLZ is only available with ARM >= 5
Author: Adrian Bunk 

--- musl-1.1.17.orig/arch/arm/atomic_arch.h
+++ musl-1.1.17/arch/arm/atomic_arch.h
@@ -82,9 +82,13 @@ static inline void a_crash()
: : : "memory");
 }
 
+#if __ARM_ARCH >= 5
+
 #define a_clz_32 a_clz_32
 static inline int a_clz_32(uint32_t x)
 {
__asm__ ("clz %0, %1" : "=r"(x) : "r"(x));
return x;
 }
+
+#endif
--- End Message ---
--- Begin Message ---
Source: musl
Source-Version: 1.1.17-2

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

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated musl 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: Fri, 20 Oct 2017 18:19:33 +0200
Source: musl
Binary: musl musl-dev musl-tools
Architecture: source
Version: 1.1.17-2
Distribution: unstable
Urgency: medium
Maintainer: Reiner Herrmann 
Changed-By: Reiner Herrmann 
Description:
 musl   - standard C library
 musl-dev   - standard C library development files
 musl-tools - standard C library tools
Closes: 879190
Changes:
 musl (1.1.17-2) unstable; urgency=medium
 .
   * Fix build failure on armel because of unsupported instruction.
 Thanks to Adrian Bunk for providing the patch. (Closes: #879190)
Checksums-Sha1:
 cf1dd1f736c514894d8afe3fd99e2f33ca90bb5e 2985 musl_1.1.17-2.dsc
 0d05654f7b904e0217b7c516461119e6ef00f9d7 11180 musl_1.1.17-2.debian.tar.xz
 92cd44c4e92541f4eb422899ea36ba36e714b394 5529 musl_1.1.17-2_source.buildinfo
Checksums-Sha256:
 e0c1dd153c8a18de91e723910e3b6e9464ff8cb3b360d0d1749da6f4581c9e61 2985 
musl_1.1.17-2.dsc
 508ef39305399d6099054b51e0db728be8a418af84ab4d58c5220d889723b103 11180 
musl_1.1.17-2.debian.tar.xz
 58a8ec517458d8785e2802d6417979b167769436abe4e833e8c81c2c48d8e5b1 5529 
musl_1.1.17-2_source.buildinfo
Files:
 fbfb12529ab0c55cb56af2464f5359ac 2985 libs optional musl_1.1.17-2.dsc
 67b214de01a56e03a805bf5247ec94bf 11180 libs optional 
musl_1.1.17-2.debian.tar.xz
 34049dd19ff59e672815881602ec9aa2 5529 libs optional 
musl_1.1.17-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE2Pb6feok2Q1urHM7zPBJKNsO6qcFAlnqKi8ACgkQzPBJKNsO
6qcigg//Sx5ni1E84bUWw61paIxs+pi0VVZdApQBxxsmOUFNJHosd+XgBgYttA/I
qYrb8V7jm58h0qvpexHFMafdk2LjVIKZtXDNKdugkAE7k/L1FwJQDMlHyCc38XkN
bNfGYrzSll/kaBGBdwrLbz3HJ2R5vUuwi3Q3POQwJ1IhO6W4Fu/Wpt1uq0eRaMcQ
iZN+WlxW+17828J4ciNUru61JIZ+bjg4DcAcI62SWuF5Z05NY7VpD4fXIsaANPfd
Pr7dOKzb+YplhPQZmjVgxLwzAQoUQblhNzjL5AYzPWipFlfUeFB80RTMTrpoliZb
eGj8uKosSlQYKfyLjXuWml2kNYTySkpG4nRHtn3VxWAAbWXFXoB5vaGwJ6tkb5lx
Tgv7Uw0G+XnCwzPnDCINVjNy7eJlJsaZlH0DzAv2i+cgyq1oZ/tUBModEMazCKqt
TsP/SL3fi9SicHkhwtQvEtg/wY+RM9idwP92LDqb/xz6ysE5OtiZ7k7SBWBwKPda
B87EdNNi0pFs7Ww9msDxrgO6u+hdfdNK8v/HPkFtq1OIOdXCnZHmeu3Wfc2iNsHC
sNYZtgGaWYy+LbYwbWLZiEAMavEpWfEPY8ekpchbPS1mPQO+U57DQFz/py1wukQT

Bug#879224: websockify: missing dependency on python-pkg-resources

[Adrian Bunk]

Package: websockify
Version: 0.6.0+dfsg1-1
Severity: serious
Control: affects -1 python-websockify python3-websockify

$ websockify 
Traceback (most recent call last):
  File "/usr/bin/websockify", line 5, in 
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources
$ 

Processed: websockify: missing dependency on python-pkg-resources

[Debian Bug Tracking System]

Processing control commands:

> affects -1 python-websockify python3-websockify
Bug #879224 [websockify] websockify: missing dependency on python-pkg-resources
Added indication that 879224 affects python-websockify and python3-websockify

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

Bug#869887: marked as done (telepathy-logger-qt FTBFS: No such file or directory: spec-logger.xml)

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 20:37:29 +0300
with message-id <20171020173729.xpdyxw3wy2h3wphj@localhost>
and subject line telepathy-logger-qt builds fine now
has caused the Debian Bug report #869887,
regarding telepathy-logger-qt FTBFS: No such file or directory: spec-logger.xml
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.)


-- 
869887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: telepathy-logger-qt
Version: 15.04.0-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes telepathy-logger-qt FTBFS:

https://tests.reproducible-builds.org/debian/history/telepathy-logger-qt.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/telepathy-logger-qt.html

...
[  7%] Generating _gen/stable-spec.xml
cd 
/build/1st/telepathy-logger-qt-15.04.0/obj-x86_64-linux-gnu/TelepathyLoggerQt 
&& /usr/bin/python /build/1st/telepathy-logger-qt-15.04.0/tools/xincludator.py 
/build/1st/telepathy-logger-qt-15.04.0/TelepathyLoggerQt/stable-interfaces.xml 
> 
/build/1st/telepathy-logger-qt-15.04.0/obj-x86_64-linux-gnu/TelepathyLoggerQt/_gen/stable-spec.xml
Traceback (most recent call last):
  File "/build/1st/telepathy-logger-qt-15.04.0/tools/qt-client-gen.py", line 
547, in 
Generator(dict(options))()
  File "/build/1st/telepathy-logger-qt-15.04.0/tools/qt-client-gen.py", line 
44, in __init__
ifacedom = xml.dom.minidom.parse(opts['--ifacexml'])
  File "/usr/lib/python2.7/xml/dom/minidom.py", line 1918, in parse
return expatbuilder.parse(file)
  File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 922, in parse
fp = open(file, 'rb')
IOError: [Errno 2] No such file or directory: 
'/build/1st/telepathy-logger-qt-15.04.0/obj-x86_64-linux-gnu/TelepathyLoggerQt/_gen/spec-logger.xml'
TelepathyLoggerQt/CMakeFiles/telepathy-logger-qt_autogen.dir/build.make:92: 
recipe for target 'TelepathyLoggerQt/_gen/cli-logger.h' failed
--- End Message ---
--- Begin Message ---
Whatever caused this FTBFS seems fixed now:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/telepathy-logger-qt.html

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

Bug#879222: haskell-heist FTBFS: Encountered missing dependencies: vector >=0.9 && <0.12

[Adrian Bunk]

Source: haskell-heist
Version: 1.0.1.0-2
Severity: serious

https://buildd.debian.org/status/package.php?p=haskell-heist=sid

...
[1 of 1] Compiling Main ( Setup.hs, Setup.o )
Linking debian/hlibrary.setup ...
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
configure_recipe
Running debian/hlibrary.setup configure --ghc -v2 
--package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
--libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
--builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro 
--haddockdir=/usr/lib/ghc-doc/haddock/heist-1.0.1.0/ --datasubdir=heist 
--htmldir=/usr/share/doc/libghc-heist-doc/html/ --enable-library-profiling
Configuring heist-1.0.1.0...
hlibrary.setup: Encountered missing dependencies:
vector >=0.9 && <0.12
/usr/share/cdbs/1/class/hlibrary.mk:142: recipe for target 
'configure-ghc-stamp' failed
make: *** [configure-ghc-stamp] Error 1

Bug#879223: websockify FTBFS with Python 3.6 as default

[Adrian Bunk]

Source: websockify
Version: 0.8.0+dfsg1-7
Severity: serious
Tags: buster sid

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

...
==
ERROR: test_list_dir_with_file_only_returns_error 
(test_websocket.WebSocketRequestHandlerTestCase)
--
Traceback (most recent call last):
  File "/build/1st/websockify-0.8.0+dfsg1/tests/test_websocket.py", line 115, 
in test_list_dir_with_file_only_returns_error
FakeSocket('GET / HTTP/1.1'), '127.0.0.1', server)
  File "/build/1st/websockify-0.8.0+dfsg1/websockify/websocket.py", line 114, 
in __init__
SimpleHTTPRequestHandler.__init__(self, req, addr, server)
  File "/usr/lib/python3.6/socketserver.py", line 696, in __init__
self.handle()
  File "/build/1st/websockify-0.8.0+dfsg1/websockify/websocket.py", line 581, 
in handle
SimpleHTTPRequestHandler.handle(self)
  File "/usr/lib/python3.6/http/server.py", line 418, in handle
self.handle_one_request()
  File "/usr/lib/python3.6/http/server.py", line 406, in handle_one_request
method()
  File "/build/1st/websockify-0.8.0+dfsg1/websockify/websocket.py", line 547, 
in do_GET
SimpleHTTPRequestHandler.do_GET(self)
  File "/usr/lib/python3.6/http/server.py", line 636, in do_GET
f = self.send_head()
  File "/usr/lib/python3.6/http/server.py", line 679, in send_head
return self.list_directory(path)
  File "/build/1st/websockify-0.8.0+dfsg1/websockify/websocket.py", line 551, 
in list_directory
self.send_error(404, "No such file")
  File "/usr/lib/python3.6/http/server.py", line 470, in send_error
self.end_headers()
  File "/usr/lib/python3.6/http/server.py", line 520, in end_headers
self.flush_headers()
  File "/usr/lib/python3.6/http/server.py", line 524, in flush_headers
self.wfile.write(b"".join(self._headers_buffer))
  File "/usr/lib/python3.6/socketserver.py", line 775, in write
self._sock.sendall(b)
AttributeError: 'FakeSocket' object has no attribute 'sendall'
 >> begin captured logging << 
websocket.type: INFO: WebSocket server settings:
websocket.type: INFO:   - Listen on localhost:80
websocket.type: INFO:   - Flash security policy server
websocket.type: INFO:   - Web server (no directory listings). Web root: 
/tmp/tmplf5ug5_q-websockify-tests
websocket.type: INFO:   - SSL/TLS support
websocket.type: INFO:   - Recording to '/tmp/tmplf5ug5_q-websockify-tests.*'
websocket.type: INFO: 1 - - [22/Nov/2018 11:41:00] code 404, message No such 
file
- >> end captured logging << -

==
ERROR: test_normal_get_with_only_upgrade_returns_error 
(test_websocket.WebSocketRequestHandlerTestCase)
--
Traceback (most recent call last):
  File "/build/1st/websockify-0.8.0+dfsg1/tests/test_websocket.py", line 101, 
in test_normal_get_with_only_upgrade_returns_error
FakeSocket('GET /tmp.txt HTTP/1.1'), '127.0.0.1', server)
  File "/build/1st/websockify-0.8.0+dfsg1/websockify/websocket.py", line 114, 
in __init__
SimpleHTTPRequestHandler.__init__(self, req, addr, server)
  File "/usr/lib/python3.6/socketserver.py", line 696, in __init__
self.handle()
  File "/build/1st/websockify-0.8.0+dfsg1/websockify/websocket.py", line 581, 
in handle
SimpleHTTPRequestHandler.handle(self)
  File "/usr/lib/python3.6/http/server.py", line 418, in handle
self.handle_one_request()
  File "/usr/lib/python3.6/http/server.py", line 406, in handle_one_request
method()
  File "/build/1st/websockify-0.8.0+dfsg1/websockify/websocket.py", line 545, 
in do_GET
self.send_error(405, "Method Not Allowed")
  File "/usr/lib/python3.6/http/server.py", line 470, in send_error
self.end_headers()
  File "/usr/lib/python3.6/http/server.py", line 520, in end_headers
self.flush_headers()
  File "/usr/lib/python3.6/http/server.py", line 524, in flush_headers
self.wfile.write(b"".join(self._headers_buffer))
  File "/usr/lib/python3.6/socketserver.py", line 775, in write
self._sock.sendall(b)
AttributeError: 'FakeSocket' object has no attribute 'sendall'
 >> begin captured logging << 
websocket.type: INFO: WebSocket server settings:
websocket.type: INFO:   - Listen on localhost:80
websocket.type: INFO:   - Flash security policy server
websocket.type: INFO:   - SSL/TLS support
websocket.type: INFO:   - Recording to '/tmp/tmpb5mdm2se-websockify-tests.*'
websocket.type: INFO: 1 - - [22/Nov/2018 11:41:00] code 405, message Method Not 
Allowed
- >> end captured logging << -

--
Ran 34 tests in 3.397s

FAILED (errors=2)
debian/rules:33: recipe for target 

Processed: Re: Bug#681726: Time to remove eclipse from Testing?

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #681726 [src:eclipse] eclipse: Upgrade to latest upstream release (HELP 
WANTED)
Bug #725377 [src:eclipse] eclipse: Upgrade to latest upstream release (HELP 
WANTED)
Bug #732959 [src:eclipse] eclipse: Upgrade to latest upstream release (HELP 
WANTED)
Bug #738506 [src:eclipse] eclipse: Upgrade to latest upstream release (HELP 
WANTED)
Bug #789928 [src:eclipse] eclipse: Upgrade to latest upstream release (HELP 
WANTED)
Bug #831603 [src:eclipse] eclipse version
Severity set to 'serious' from 'wishlist'
Severity set to 'serious' from 'wishlist'
Severity set to 'serious' from 'wishlist'
Severity set to 'serious' from 'wishlist'
Severity set to 'serious' from 'wishlist'
Severity set to 'serious' from 'wishlist'

-- 
681726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681726
725377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725377
732959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732959
738506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738506
789928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789928
831603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853649: rush: diff for NMU version 1.8+dfsg-1.1

[Adrian Bunk]

Control: tags 853649 + pending

Dear maintainer,

I've prepared an NMU for rush (versioned as 1.8+dfsg-1.1) and uploaded 
it to DELAYED/10. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru rush-1.8+dfsg/debian/changelog rush-1.8+dfsg/debian/changelog
--- rush-1.8+dfsg/debian/changelog	2016-12-13 01:37:55.0 +0200
+++ rush-1.8+dfsg/debian/changelog	2017-10-20 19:38:32.0 +0300
@@ -1,3 +1,11 @@
+rush (1.8+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update to latest intprops.h from gnulib, fixes FTBFS with gcc 7.
+(Closes: #853649)
+
+ -- Adrian Bunk   Fri, 20 Oct 2017 19:38:32 +0300
+
 rush (1.8+dfsg-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru rush-1.8+dfsg/debian/patches/intprops.patch rush-1.8+dfsg/debian/patches/intprops.patch
--- rush-1.8+dfsg/debian/patches/intprops.patch	1970-01-01 02:00:00.0 +0200
+++ rush-1.8+dfsg/debian/patches/intprops.patch	2017-10-20 19:36:55.0 +0300
@@ -0,0 +1,257 @@
+Description: Update to latest intprops.h from gnulib, fixes FTBFS with gcc 7
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/853649
+
+--- rush-1.8+dfsg.orig/gnu/intprops.h
 rush-1.8+dfsg/gnu/intprops.h
+@@ -1,20 +1,18 @@
+-/* -*- buffer-read-only: t -*- vi: set ro: */
+-/* DO NOT EDIT! GENERATED AUTOMATICALLY! */
+ /* intprops.h -- properties of integer types
+ 
+-   Copyright (C) 2001-2016 Free Software Foundation, Inc.
++   Copyright (C) 2001-2017 Free Software Foundation, Inc.
+ 
+This program is free software: you can redistribute it and/or modify it
+-   under the terms of the GNU General Public License as published
+-   by the Free Software Foundation; either version 3 of the License, or
++   under the terms of the GNU Lesser General Public License as published
++   by the Free Software Foundation; either version 2.1 of the License, or
+(at your option) any later version.
+ 
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+-   GNU General Public License for more details.
++   GNU Lesser General Public License for more details.
+ 
+-   You should have received a copy of the GNU General Public License
++   You should have received a copy of the GNU Lesser General Public License
+along with this program.  If not, see .  */
+ 
+ /* Written by Paul Eggert.  */
+@@ -23,7 +21,6 @@
+ #define _GL_INTPROPS_H
+ 
+ #include 
+-#include 
+ 
+ /* Return a value with the common real type of E and V and the value of V.  */
+ #define _GL_INT_CONVERT(e, v) (0 * (e) + (v))
+@@ -49,12 +46,16 @@
+ 
+ /* Minimum and maximum values for integer types and expressions.  */
+ 
++/* The width in bits of the integer type or expression T.
++   Padding bits are not supported; this is checked at compile-time below.  */
++#define TYPE_WIDTH(t) (sizeof (t) * CHAR_BIT)
++
+ /* The maximum and minimum values for the integer type T.  */
+ #define TYPE_MINIMUM(t) ((t) ~ TYPE_MAXIMUM (t))
+ #define TYPE_MAXIMUM(t) \
+   ((t) (! TYPE_SIGNED (t)   \
+ ? (t) -1\
+-: t) 1 << (sizeof (t) * CHAR_BIT - 2)) - 1) * 2 + 1)))
++: t) 1 << (TYPE_WIDTH (t) - 2)) - 1) * 2 + 1)))
+ 
+ /* The maximum and minimum values for the type of the expression E,
+after integer promotion.  E should not have side effects.  */
+@@ -67,29 +68,23 @@
+? _GL_SIGNED_INT_MAXIMUM (e) \
+: _GL_INT_NEGATE_CONVERT (e, 1))
+ #define _GL_SIGNED_INT_MAXIMUM(e)   \
+-  (((_GL_INT_CONVERT (e, 1) << (sizeof ((e) + 0) * CHAR_BIT - 2)) - 1) * 2 + 1)
++  (((_GL_INT_CONVERT (e, 1) << (TYPE_WIDTH ((e) + 0) - 2)) - 1) * 2 + 1)
++
++/* Work around OpenVMS incompatibility with C99.  */
++#if !defined LLONG_MAX && defined __INT64_MAX
++# define LLONG_MAX __INT64_MAX
++# define LLONG_MIN __INT64_MIN
++#endif
+ 
+ /* This include file assumes that signed types are two's complement without
+padding bits; the above macros have undefined behavior otherwise.
+If this is a problem for you, please let us know how to fix it for your host.
+-   As a sanity check, test the assumption for some signed types that
+-bounds.  */
+-verify (TYPE_MINIMUM (signed char) == SCHAR_MIN);
+-verify (TYPE_MAXIMUM (signed char) == SCHAR_MAX);
+-verify (TYPE_MINIMUM (short int) == SHRT_MIN);
+-verify (TYPE_MAXIMUM (short int) == SHRT_MAX);
+-verify (TYPE_MINIMUM (int) 

Processed: rush: diff for NMU version 1.8+dfsg-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 853649 + pending
Bug #853649 [src:rush] rush: ftbfs with GCC-7
Added tag(s) pending.

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

Bug#879221: dropbear-bin: hardcodes dependencies on shared libs

[Emilio Pozuelo Monfort]

Package: dropbear-bin
Version: 2017.75-2
Severity: serious

dropbear-bin has:

Depends: libtomcrypt0, libtommath1, ${misc:Depends}, ${shlibs:Depends}

A rebuild of dropbear against libtopcrypt1 (which bumped the SONAME)
causes it to have:

Depends: libtomcrypt0, libtommath1, libc6 (>= 2.15), libtomcrypt1, zlib1g (>= 
1:1.1.4)

Which is wrong. Please let shlibs do its job and drop the libtomcrypt
and libtommath hardcoded dependencies.

Emilio

Bug#835189: marked as done (python-pyrax: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 15:49:53 +
with message-id 
and subject line Bug#835189: fixed in python-pyrax 1.9.8-1
has caused the Debian Bug report #835189,
regarding python-pyrax: FTBFS (failing tests)
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.)


-- 
835189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-pyrax
Version: 1.9.6-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_2.7/build/pyrax
copying pyrax/autoscale.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/pyrax

[... snipped ...]

test_name (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_pause (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_policy_add_webhook (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_policy_count (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_policy_delete (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_policy_delete_webhook (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_policy_execute (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_policy_get (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_policy_get_webhook (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_policy_init (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_policy_list_webhooks (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_policy_update (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_policy_update_webhook (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_policy_update_webhook_metadata (tests.unit.test_autoscale.AutoscaleTest) 
... ok
test_resume (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_update (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_update_launch_config (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_update_launch_metadata (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_update_metadata (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_update_policy (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_update_webhook (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_update_webhook_metadata (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_webhook_delete (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_webhook_get (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_webhook_update (tests.unit.test_autoscale.AutoscaleTest) ... ok
test_webhook_update_metadata (tests.unit.test_autoscale.AutoscaleTest) ... ok

==
ERROR: test_rax_endpoints (tests.unit.test_identity.IdentityTest)
--
Traceback (most recent call last):
  File "tests/unit/test_identity.py", line 745, in test_rax_endpoints
pyrax.set_setting("auth_endpoint", fake_ep)
  File "pyrax/__init__.py", line 383, in set_setting
return settings.set(key, val, env=env)
  File "pyrax/__init__.py", line 225, in set
dct = self._settings[env]
KeyError: 'alternate'

--
Ran 1269 tests in 1.521s

FAILED (errors=1)
E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover 
-v 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:9: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


[ Because this package is "Arch: all", this is really a FTBFS bug in the
  usual sense and the fact that I was doing "dpkg-buildpackage -A" does
  not really mean anything special ].

It does not always fail, but when it does the error message seems to be the 
same.

Sorry that I don't have a way to reproduce it, but I 

Bug#841623: marked as done (python-pyrax: FTBFS: Forbidden: 'novaclient.v2.client.Client' is not designed to be initialized directly. It is inner class of novaclient. You should use 'novaclient.client

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 15:49:53 +
with message-id 
and subject line Bug#841623: fixed in python-pyrax 1.9.8-1
has caused the Debian Bug report #841623,
regarding python-pyrax: FTBFS: Forbidden: 'novaclient.v2.client.Client' is not 
designed to be initialized directly. It is inner class of novaclient. You 
should use 'novaclient.client.Client' instead. Related lp bug-report: 1493576 
(HTTP 403)
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.)


-- 
841623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pyrax
Version: 1.9.6-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/cloudloadbalancers.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/queueing.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/resource.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/utils.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/cloudnetworks.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/base_identity.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/cloudblockstorage.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/clouddns.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/exceptions.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/image.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/http.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/object_storage.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/clouddatabases.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/cloudmonitoring.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/version.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/cloudcdn.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/manager.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/client.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/fakes.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/autoscale.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> copying pyrax/service_catalog.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax
> creating /<>/.pybuild/pythonX.Y_2.7/build/pyrax/identity
> copying pyrax/identity/keystone_identity.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax/identity
> copying pyrax/identity/rax_identity.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax/identity
> copying pyrax/identity/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyrax/identity
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
> python2.7 -m unittest discover -v 
> /usr/lib/python2.7/dist-packages/novaclient/client.py:830: UserWarning: 
> 'get_client_class' is deprecated. Please use `novaclient.client.Client` 
> instead.
>   warnings.warn(_LW("'get_client_class' is deprecated. "
> test_assure_container (tests.unit.test_object_storage.ObjectStorageTest) ... 
> ok
> test_backwards_aliases (tests.unit.test_object_storage.ObjectStorageTest) ... 
> ok
> test_clt_backwards_aliases (tests.unit.test_object_storage.ObjectStorageTest) 
> ... ok
> test_clt_bulk_delete_async (tests.unit.test_object_storage.ObjectStorageTest) 
> ... ok
> test_clt_bulk_delete_sync (tests.unit.test_object_storage.ObjectStorageTest) 
> ... ok
> test_clt_bulk_delete_sync_413 
> (tests.unit.test_object_storage.ObjectStorageTest) ... ok
> test_clt_cancel_folder_upload 
> (tests.unit.test_object_storage.ObjectStorageTest) ... ok
> test_clt_cdn_request (tests.unit.test_object_storage.ObjectStorageTest) ... ok
> test_clt_cdn_request_cont_not_cdn_enabled 
> (tests.unit.test_object_storage.ObjectStorageTest) ... ok
> test_clt_cdn_request_not_enabled 
> 

Bug#853329: marked as done (binutils-msp430: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 18:28:07 +0300
with message-id <20171020152807.ljcpz2ls7ami5qis@localhost>
and subject line Already fixed in experimental
has caused the Debian Bug report #853329,
regarding binutils-msp430: ftbfs with GCC-7
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.)


-- 
853329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:binutils-msp430
Version: 2.22~msp20120406-5.1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/binutils-msp430_2.22~msp20120406-5.1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
mv -f .deps/archive.Tpo .deps/archive.Plo
/bin/bash ./libtool --tag=CC   --mode=compile x86_64-linux-gnu-gcc 
-DHAVE_CONFIG_H -I. -I. -I. -I./../include  -DHAVE_bfd_elf32_msp430_vec 
-DHAVE_bfd_elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec  
-DBINDIR='"/usr/bin"'  -W -Wall -Wstrict-prototypes -Wmissing-prototypes 
-Wshadow -Werror -g -O2 -MT archures.lo -MD -MP -MF .deps/archures.Tpo -c -o 
archures.lo -DDEFAULT_VECTOR=bfd_elf32_msp430_vec 
-DSELECT_VECS='_elf32_msp430_vec,_elf32_little_generic_vec,_elf32_big_generic_vec'
 -DSELECT_ARCHITECTURES='_msp430_arch' ./archures.c
libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. 
-I./../include -DHAVE_bfd_elf32_msp430_vec -DHAVE_bfd_elf32_little_generic_vec 
-DHAVE_bfd_elf32_big_generic_vec -DBINDIR=\"/usr/bin\" -W -Wall 
-Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 -MT 
archures.lo -MD -MP -MF .deps/archures.Tpo -c 
-DDEFAULT_VECTOR=bfd_elf32_msp430_vec 
"-DSELECT_VECS=_elf32_msp430_vec,_elf32_little_generic_vec,_elf32_big_generic_vec"
 "-DSELECT_ARCHITECTURES=_msp430_arch" ./archures.c -o archures.o
mv -f .deps/archures.Tpo .deps/archures.Plo
/bin/bash ./libtool --tag=CC   --mode=compile x86_64-linux-gnu-gcc 
-DHAVE_CONFIG_H -I. -I. -I. -I./../include  -DHAVE_bfd_elf32_msp430_vec 
-DHAVE_bfd_elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec  
-DBINDIR='"/usr/bin"'  -W -Wall -Wstrict-prototypes -Wmissing-prototypes 
-Wshadow -Werror -g -O2 -MT bfd.lo -MD -MP -MF .deps/bfd.Tpo -c -o bfd.lo bfd.c
libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. 
-I./../include -DHAVE_bfd_elf32_msp430_vec -DHAVE_bfd_elf32_little_generic_vec 
-DHAVE_bfd_elf32_big_generic_vec -DBINDIR=\"/usr/bin\" -W -Wall 
-Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 -MT bfd.lo -MD 
-MP -MF .deps/bfd.Tpo -c bfd.c -o bfd.o
mv -f .deps/bfd.Tpo .deps/bfd.Plo
/bin/bash ./libtool --tag=CC   --mode=compile x86_64-linux-gnu-gcc 
-DHAVE_CONFIG_H -I. -I. -I. -I./../include  -DHAVE_bfd_elf32_msp430_vec 
-DHAVE_bfd_elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec  
-DBINDIR='"/usr/bin"'  -W -Wall -Wstrict-prototypes -Wmissing-prototypes 
-Wshadow -Werror -g -O2 -MT bfdio.lo -MD -MP -MF .deps/bfdio.Tpo -c -o bfdio.lo 
bfdio.c
libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. 
-I./../include -DHAVE_bfd_elf32_msp430_vec -DHAVE_bfd_elf32_little_generic_vec 
-DHAVE_bfd_elf32_big_generic_vec -DBINDIR=\"/usr/bin\" -W -Wall 
-Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 -MT bfdio.lo 
-MD -MP -MF .deps/bfdio.Tpo -c bfdio.c -o bfdio.o
mv -f .deps/bfdio.Tpo .deps/bfdio.Plo
/bin/bash ./libtool --tag=CC   --mode=compile x86_64-linux-gnu-gcc 
-DHAVE_CONFIG_H -I. -I. -I. -I./../include  -DHAVE_bfd_elf32_msp430_vec 
-DHAVE_bfd_elf32_little_generic_vec 

Bug#879123: glee: source for configure is missing

[Simon McVittie]

On Fri, 20 Oct 2017 at 16:22:38 +0200, Markus Koschany wrote:
> So you are basically saying that the situation for configure scripts is
> less clear-cut and you tend to acknowledge that this is a bug but
> usually not a release critical one and it also depends on how the
> copyright holder is treating the generated file.

I only partially agree with this summary; I think it's still in
danger of conflating two issues.

I think having both configure and configure.ac in the source tarball,
using upstream's pre-generated configure without re-generating it, but
having its source code present, is usually a bug but not a RC one.
A concrete example from one of my packages: if I'm reading my old
changelog correctly, dbus (<< 1.4.10-1) was buggy in this way, but I
don't think that bug was RC.

However, I think having configure but not configure.ac is usually
a RC bug, due to DFSG §2. (Exceptional case: if upstream genuinely treats
configure as though it was source - hand-editing it, etc. - then I
would consider it to be technically misguided, but DFSG-compliant.)

> What do you make of this specific case now, a modifiable but unused
> configure file in a source package? Would you remove this file from one
> of your packages given the same circumstances? Is this release-critical
> for you?

I would be annoyed to have to take action for something this trivial
(so I can understand why you are annoyed), but yes, I think it's RC and
requires a +dfsg1 tarball.

I wouldn't be in any hurry to fix that bug for prior releases unless
someone in the stable release team felt strongly about it, though -
we shipped it already, and it isn't a copyright violation, only a
DFSG violation (breaking the rules we set for ourselves, but not the law).

> However I do not think the same
> severity is appropriate for Windows files because they are platform
> specific and usually are only there for the convenience of upstream's
> windows users. They waste disk space but do not impair my freedom.

This depends whether those Windows convenience files come with DFSG
source code or not. If they do, fine, we can accept the "dead weight",
just like we don't bother to remove the pre-generated configure from
source packages where we are going to overwrite it with dh-autoreconf
anyway.

If there is no source code, my understanding is that derived files
without source are equally forbidden by the ftp team regardless of
whether they are used in building our binary packages or not. One
justification for this position is that it is not just about your
freedom to modify what will go into the binary package, but also about
recipients of source code via Debian being able to be confident that
everything they receive is equally DFSG-compliant (for example, in
the past I've cross-compiled Debian's libexpat for Windows as part of
a test environment for dbus). That's consistent with the requirement
that we remove distributable-but-non-Free files like RFCs from source
tarballs even if they aren't used in the binaries, which is another
frequently-disagreed-with but consistently-applied policy.

I personally think the project is sometimes too absolutist in its
interpretation of DFSG §2, but I think I'd have trouble establishing
consensus for any less draconian interpretation. Establishing consensus
for "grey areas" is always difficult, because you get into questions
about where to draw the line, and I don't have a good answer to those
questions beyond "I know an (un)acceptable package when I see one",
which is not particularly principled or defensible.

It's entirely possible that an absolutist position is in fact the
pragmatic thing to do, because establishing consensus about the right
line to draw would be more effort than repacking some tarballs :-)

> Looking at
> https://lintian.debian.org/tags/source-contains-prebuilt-windows-binary.html
> I can still see that we have more than 1000 source packages in the
> archive that ship those files. So I think you are not correct if you
> claim that we treat them as release-critical bugs at the moment
> otherwise I would expect this Lintian tag to be an error not a pedantic
> issue.

I'm surprised this tag is so low-priority, to be honest: I would have
expected the DFSG-maximalist faction among Debian contributors to have
made it at least a warning. Presumably the assumption is that those
prebuilt Windows binaries all come with source code, otherwise they would
have been rejected at NEW time?

Regards,
smcv

Bug#875396: marked as done (haskell-vector: FTBFS on any-i386)

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 14:51:11 +
with message-id 
and subject line Bug#875396: fixed in haskell-vector 0.12.0.1-2
has caused the Debian Bug report #875396,
regarding haskell-vector: FTBFS on any-i386
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.)


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

Hello,

In case you have not noticed, the haskell-vector fails the tests on i386
ports (at least i386 and hurd-i386 failed, kfreebsd-i386 hasn't tried
yet).

Samuel


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

Kernel: Linux 4.13.0 (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)

-- 
Samuel
 Ça peut être une madeleine à sous munitions (avec des composants,
par exemple)
 -+- #runtime -+-
--- End Message ---
--- Begin Message ---
Source: haskell-vector
Source-Version: 0.12.0.1-2

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

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

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated haskell-vector 
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: Fri, 20 Oct 2017 17:14:32 +0300
Source: haskell-vector
Binary: libghc-vector-dev libghc-vector-prof libghc-vector-doc
Architecture: source
Version: 0.12.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Description:
 libghc-vector-dev - Efficient Arrays for Haskell
 libghc-vector-doc - Efficient Arrays for Haskell
 libghc-vector-prof - Efficient Arrays for Haskell
Closes: 875396
Changes:
 haskell-vector (0.12.0.1-2) unstable; urgency=medium
 .
   * Use SSE2 for floating-point operations on i386 (Closes: #875396)
   * Update d/copyright file
 - Bump copyright years
 - Add Debian contributors under debian/* files
Checksums-Sha1:
 0684a441eb4238a908f6e91636f28ac65b0a9c4b 2599 haskell-vector_0.12.0.1-2.dsc
 3ecbd4998b5a28dbfea977ace4e26f1c21739275 4288 
haskell-vector_0.12.0.1-2.debian.tar.xz
 9dce6e6f1e3c492700dadeb9e458729197126f57 8089 
haskell-vector_0.12.0.1-2_amd64.buildinfo
Checksums-Sha256:
 8af9da0a1270a19fd555d082389ab0a58403e0e3f73f324fdd398fed591aee6e 2599 
haskell-vector_0.12.0.1-2.dsc
 e3195c2559e4603db024196a7fe99c208b0417bcf638f7d220d014c3f5bae8ca 4288 
haskell-vector_0.12.0.1-2.debian.tar.xz
 e80b583f5b036956f747b8ebb2450d5dca79cc92d0a4d96b4e4b911a19fc02d1 8089 
haskell-vector_0.12.0.1-2_amd64.buildinfo
Files:
 79414b1beb6c475264316e26c7c3d517 2599 haskell extra 
haskell-vector_0.12.0.1-2.dsc
 ff025b0d06a499182b8df01743dffd95 4288 haskell extra 
haskell-vector_0.12.0.1-2.debian.tar.xz
 3dd0454af2538798acb327afc3791905 8089 haskell extra 
haskell-vector_0.12.0.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAlnqCDUUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDzoWg/+JyS2u4Gw5hcAAV56BtKtAXBdohA9
F8b4XYUFaE6URKYBm+nGqPFAF8TLNgKDek/axJvfcEYZUOOznCoS8CMti2CGy+Z/
gOoR+pjgHfi+zJ8XkaoJ+EkpLerv+mArHDrT/w0gwah9tiuidBJZcO11RhZnzHtH
OZ2GNZNS6tzKVX+KBQ/a0VsosKlMZ+LV6KYvS4mKj8xUgcWfs4ksZPm+LG2H7C12
AAVY1wzQH7uHoyKbc/rODtfjH1A5h0hlRA//17AHkhQ8UMWvkaEotREE7zo16Q6x
yVKaMElMTRdoLjfPkbAg0Flxx7Ff4Le39UxL77eoh9kfOVqnSuMRT/MpmMyY5ric
pEecigcxlkkV3nyvL8kEhVJZGdulWq1es5Gb4rSADHhXFpKc7Wi1RRtKWjAgN/uO
vvTN1PyU/yfze5aMXiWm5oz7bOrxyJzWrK/18YOqGF4stE+b5PqQUS5w1K3jW78H

Bug#867151: marked as done (haskell-xmlhtml FTBFS on 32bit: numericalEscapes Failed)

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 14:51:19 +
with message-id 
and subject line Bug#867151: fixed in haskell-xmlhtml 0.2.5.1-1
has caused the Debian Bug report #867151,
regarding haskell-xmlhtml FTBFS on 32bit: numericalEscapes Failed
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.)


-- 
867151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-xmlhtml
Version: 0.2.4-1
Severity: serious

https://buildd.debian.org/status/package.php?p=haskell-xmlhtml=sid

...
smileyEscapesInLatin   : [OK]
numericalEscapes   : [Failed]
numericalEscapes   
hRenderByteOrderMark   : [OK]
...

 Test CasesTotal
 Passed  199   199  
 Failed  1 1
 Total   200   200  
Test suite testsuite: FAIL
Test suite logged to: dist-ghc/test/xmlhtml-0.2.4-testsuite.log
0 of 1 test suites (0 of 1 test cases) passed.
/usr/share/cdbs/1/class/hlibrary.mk:154: recipe for target 'check-ghc-stamp' 
failed
make: *** [check-ghc-stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: haskell-xmlhtml
Source-Version: 0.2.5.1-1

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated haskell-xmlhtml 
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: Fri, 20 Oct 2017 16:51:06 +0300
Source: haskell-xmlhtml
Binary: libghc-xmlhtml-dev libghc-xmlhtml-prof libghc-xmlhtml-doc
Architecture: source
Version: 0.2.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Description:
 libghc-xmlhtml-dev -
 libghc-xmlhtml-doc -
 libghc-xmlhtml-prof -
Closes: 867151
Changes:
 haskell-xmlhtml (0.2.5.1-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #867151)
   * Update d/patches
 - Drop saner-testsuite, applied upstream
 - Modify no-bytestring-builder to apply cleanly
   * Remove unused build dependencies
Checksums-Sha1:
 28bbae62a596a2376440c03f476d0a5b2a9e5ffa 3093 haskell-xmlhtml_0.2.5.1-1.dsc
 b15bec99682f89c10e09c96919b9d29f2b211240 123788 
haskell-xmlhtml_0.2.5.1.orig.tar.gz
 1e291d7787323018b6a0eec28ebd168d19b5fa76 4024 
haskell-xmlhtml_0.2.5.1-1.debian.tar.xz
 0b60f4fac1b4fb4877809a368841a2031c2c7d2c 8662 
haskell-xmlhtml_0.2.5.1-1_amd64.buildinfo
Checksums-Sha256:
 cdbce932c2a34feb375cec606b3552bbec355e5c6a928b5f0b5d4dd0e01a6828 3093 
haskell-xmlhtml_0.2.5.1-1.dsc
 134de5455473998ebb3a27b237431aaa6fc206616a00de7a0729e9d39b8a12d5 123788 
haskell-xmlhtml_0.2.5.1.orig.tar.gz
 a192bcd916472067e6118f956f12ad4f28992494359339115302c5942c61026c 4024 
haskell-xmlhtml_0.2.5.1-1.debian.tar.xz
 ab314b101c8e7bfe5ad2b2e68dbad37eeaa0cf6cdf4281b1e8721636309d74be 8662 
haskell-xmlhtml_0.2.5.1-1_amd64.buildinfo
Files:
 297bf2934bfd110760636169b35950b3 3093 haskell extra 
haskell-xmlhtml_0.2.5.1-1.dsc
 19bce360f005eda5c0e9782ae3c9b123 123788 haskell extra 
haskell-xmlhtml_0.2.5.1.orig.tar.gz
 f5d56f130b3a3e30e2e148861eac1dc3 4024 haskell extra 
haskell-xmlhtml_0.2.5.1-1.debian.tar.xz
 6227cc13f5320c6bc52b8102a15e70d8 8662 haskell extra 
haskell-xmlhtml_0.2.5.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAlnqAbEUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDzmNxAArW2Fg3oHkz7ozaynONUwFfWLFBRT
uQtsKQXXHJrvRmVvLggEvGXMrsbyI2RcpEX+cMoIvX8e8gg+coBqzOwfIveT6Cek
9Lb6MSwzd78lGsWHTnX1QPYxtwg0LT1hDlrTHPv38X5Q48xOPwdV/Hl8RAg933wX
R9TcxtLQ/RBj5Y/qdr6XkgSFAfezHZp4A6PwwjnAm+xjSbkRGPw2BddtHgXnIpdo
JW8yjuczwmN0xQUcOJ4dKJssQC8p9RdSYrkrIcWNtokseIMIaZBgszYY8vMuCZ+5
x0LoDwUOKEG/vN7N4+rUL1eM5uUtAMtbQIFruIfyv/mKRakHmGfgNpgQEfWbV/jB
1e0p7MAJEquPsVa9jXp9GZa0L+t4UvJaSKPyleXdIFEVvv2VD8MH70tbFhFOa3Gv
a+ZwFLYyxE7ZFjXzDUn5yR2GA5M+vJ0teSn+c4THp6gDY+RhCLOu+EnyBSzsncsj

Bug#879213: bup FTBFS with git 1:2.15.0~rc1-1

[Adrian Bunk]

Source: bup
Version: 0.29-3
Severity: serious
Tags: buster sid

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

...
Differences between bup/ and bup-baseline/
Matching:
  .d..t.. ./
  *deleting   logs/refs/heads/src
  *deleting   refs/heads/src
  >f+ packed-refs
  .d..t.. logs/refs/heads/
  .d..t.. refs/heads/
Against:
  \*deleting[ ]+logs/refs/heads/src
  \*deleting[ ]+refs/heads/src
  \.d\.\.t\.\.\.[.]*[ ]+logs/refs/heads/
  \.d\.\.t\.\.\.[.]*[ ]+refs/heads/
! t/test-rm.sh:51 regex doesn't match   FAILED
 5.322s ok
! t/test-rm.sh  rm /foo (one of many): ...
! t/test-rm.sh:59  rm -rf bup   ok
! t/test-rm.sh:60  mv bup-baseline bup  ok
! t/test-rm.sh:61  echo twisty-maze ok
! t/test-rm.sh:62  bup index srcok
! t/test-rm.sh:63  bup save -n src-2 srcok
! t/test-rm.sh:64  echo twisty-maze ok
! t/test-rm.sh:65  bup index srcok
! t/test-rm.sh:66  bup save -n src-3 srcok
! t/test-rm.sh:67  /build/1st/bup-0.29/t/sync-tree bup/ bup-baseline/ ok
! t/test-rm.sh:68  bup tick ok
! t/test-rm.sh:69  bup rm --unsafe /src ok
Differences between bup/ and bup-baseline/
Matching:
  .d..t.. ./
  *deleting   logs/refs/heads/src
  *deleting   refs/heads/src
  >f+ packed-refs
  .d..t.. logs/refs/heads/
  .d..t.. refs/heads/
Against:
  \*deleting[ ]+logs/refs/heads/src
  \*deleting[ ]+refs/heads/src
  \.d\.\.t\.\.\.[.]*[ ]+logs/refs/heads/
  \.d\.\.t\.\.\.[.]*[ ]+refs/heads/
! t/test-rm.sh:70 regex doesn't match   FAILED
 5.662s ok
! t/test-rm.sh  rm /foo /bar (multiple of many): ...
! t/test-rm.sh:78  rm -rf bup   ok
! t/test-rm.sh:79  mv bup-baseline bup  ok
! t/test-rm.sh:80  echo twisty-maze ok
! t/test-rm.sh:81  bup index srcok
! t/test-rm.sh:82  bup save -n src-4 srcok
! t/test-rm.sh:83  echo twisty-maze ok
! t/test-rm.sh:84  bup index srcok
! t/test-rm.sh:85  bup save -n src-5 srcok
! t/test-rm.sh:86  /build/1st/bup-0.29/t/sync-tree bup/ bup-baseline/ ok
! t/test-rm.sh:87  bup tick ok
! t/test-rm.sh:88  bup rm --unsafe /src-2 /src-4ok
Differences between bup/ and bup-baseline/
Matching:
  .d..t.. ./
  *deleting   logs/refs/heads/src-4
  *deleting   logs/refs/heads/src-2
  *deleting   refs/heads/src-4
  *deleting   refs/heads/src-2
  >f+ packed-refs
  .d..t.. logs/refs/heads/
  .d..t.. refs/heads/
Against:
  \*deleting[ ]+logs/refs/heads/src-4
  \*deleting[ ]+logs/refs/heads/src-2
  \*deleting[ ]+refs/heads/src-4
  \*deleting[ ]+refs/heads/src-2
  \.d\.\.t\.\.\.[.]*[ ]+logs/refs/heads/
  \.d\.\.t\.\.\.[.]*[ ]+refs/heads/
! t/test-rm.sh:89 regex doesn't match   FAILED
 8.243s ok
! t/test-rm.sh  rm /foo /bar (all): .
! t/test-rm.sh:99  rm -rf bup   ok
! t/test-rm.sh:100  mv bup-baseline bup ok
! t/test-rm.sh:101  /build/1st/bup-0.29/t/sync-tree bup/ bup-baseline/ ok
! t/test-rm.sh:102  bup tickok
! t/test-rm.sh:103  bup rm --unsafe /src /src-2 /src-3 /src-4 /src-5 ok
Differences between bup/ and bup-baseline/
Matching:
  .d..t.. ./
  *deleting   logs/refs/heads/src-5
  *deleting   logs/refs/heads/src-4
  *deleting   logs/refs/heads/src-3
  *deleting   logs/refs/heads/src-2
  *deleting   logs/refs/heads/src
  *deleting   refs/heads/src-5
  *deleting   refs/heads/src-4
  *deleting   refs/heads/src-3
  *deleting   refs/heads/src-2
  *deleting   refs/heads/src
  >f+ packed-refs
  .d..t.. logs/refs/heads/
  .d..t.. refs/heads/
Against:
  \*deleting[ ]+logs/refs/heads/src-5
  \*deleting[ ]+logs/refs/heads/src-4
  \*deleting[ ]+logs/refs/heads/src-3
  \*deleting[ ]+logs/refs/heads/src-2
  \*deleting[ ]+logs/refs/heads/src
  \*deleting[ ]+refs/heads/src-5
  \*deleting[ ]+refs/heads/src-4
  \*deleting[ ]+refs/heads/src-3
  \*deleting[ ]+refs/heads/src-2
  \*deleting[ ]+refs/heads/src
  \.d\.\.t\.\.\.[.]*[ ]+logs/refs/heads/
  \.d\.\.t\.\.\.[.]*[ ]+refs/heads/
! t/test-rm.sh:104 regex doesn't match  FAILED
 2.070s ok
! t/test-rm.sh  rm /foo/bar (lone save - equivalent to rm /foo): 
! t/test-rm.sh:120  rm -rf bup bup-baseline src ok
Initialized empty Git repository in 
/build/1st/bup-0.29/t/tmp/test-rm.sh-WbDTyYG/bup/
! t/test-rm.sh:121  

Bug#879123: glee: source for configure is missing

[Markus Koschany]

Am 20.10.2017 um 15:26 schrieb Simon McVittie:
> On Fri, 20 Oct 2017 at 14:36:06 +0200, Markus Koschany wrote:
>> If you insist on severity
>> serious for such a problem, then bug reports with the same severity
>> should be filed against packages
>>
>>  a) that do not recreate their build system at build time
>>  b) all packages that contain a prebuilt object without corresponding
>> source, even when they are not used to build the package, or used at
>> runtime (like .dll and .exe files)
> 
> I don't think those are the same thing at all, and I think trying to
> equate them clouds the issue.

Thanks for your reply. I think we are on the same page. My two points
were exaggerated on purpose meaning I also believe that this topic
deserves a more differentiated point of view which you delivered.

So you are basically saying that the situation for configure scripts is
less clear-cut and you tend to acknowledge that this is a bug but
usually not a release critical one and it also depends on how the
copyright holder is treating the generated file.

What do you make of this specific case now, a modifiable but unused
configure file in a source package? Would you remove this file from one
of your packages given the same circumstances? Is this release-critical
for you?

[...]
>>  b) all packages that contain a prebuilt object without corresponding
>> source, even when they are not used to build the package, or used at
>> runtime (like .dll and .exe files)
> 
> That's my (3.) above, and I think there is consensus that it is a
> release-critical bug. We remove these objects when we find them.
> 
> (If I am wrong about that, then I can stop repacking the Quake series of
> game engines to exclude prebuilt Windows DLLs... but I would not want
> to do that without approval from the ftp team, and the ftp team seem
> highly unlikely to give that approval.)

[...]

Just for clarification: I completely agree that we should remove those
files whenever we can. I have done the same in all of my packages and I
am even more picky when it comes to prebuilt jar files in my Java
packages because there is a real possibility that they are used by
accident during the build process. However I do not think the same
severity is appropriate for Windows files because they are platform
specific and usually are only there for the convenience of upstream's
windows users. They waste disk space but do not impair my freedom.

Looking at
https://lintian.debian.org/tags/source-contains-prebuilt-windows-binary.html

I can still see that we have more than 1000 source packages in the
archive that ship those files. So I think you are not correct if you
claim that we treat them as release-critical bugs at the moment
otherwise I would expect this Lintian tag to be an error not a pedantic
issue.

And this is why it is frustrating for me to read bug reports like this
one, where we have just a modifiable text file but there are arguably
more severe issues right before our eyes. Therefore my plea to use
appropriate severity levels.

Markus



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#878817 closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: Bug#878817: luajit: Please drop mips64el again)

[Debian Bug Tracking System]

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

> # new port, ongoing patch, lets migrate in the meanwhile
> severity 878817 important
Bug #878817 [src:luajit] luajit: jit miscompile on mips64el
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: Better bug title

[Debian Bug Tracking System]

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

> retitle 878817 luajit: jit miscompile on mips64el
Bug #878817 [src:luajit] luajit: Please drop mips64el again
Changed Bug title to 'luajit: jit miscompile on mips64el' from 'luajit: Please 
drop mips64el again'.
> thanks
Stopping processing here.

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

Bug#878519: marked as done (gjs: doesn't seem to work on mips (at least on minkus and mips-aql-01))

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 13:49:28 +
with message-id 
and subject line Bug#878519: fixed in mozjs52 52.3.1-6
has caused the Debian Bug report #878519,
regarding gjs: doesn't seem to work on mips (at least on minkus and mips-aql-01)
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.)


-- 
878519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gjs
Version: 1.50.1-2
Severity: serious
Affects: gnome-documents
X-Debbugs-Cc: debian-m...@lists.debian.org

mozjs52 now works at least partially on mips (although there are thousands
of test failures, #878284) but gjs doesn't even start:

(sid_mips-dchroot)smcv@minkus ~ % js52
js> print("hello, world")
hello, world
js>
(sid_mips-dchroot)smcv@minkus ~ % gjs

(gjs:13738): Gjs-WARNING **: gjs_eval_in_scope called with a pending 
exception

(gjs:13738): Gjs-WARNING **: JS ERROR: TypeError: can't assign to 
properties of (new Number(1.629847465960073e+237)): not an object

JS_EvaluateScript() failed

This causes gnome-documents to FTBFS (#878431, which I can also reproduce
for 3.22.5-2 in unstable):
https://buildd.debian.org/status/fetch.php?pkg=gnome-documents=mips=3.26.1-1=1507913495=0

I thought gjs had build-time tests, but this doesn't exactly look
thorough, so perhaps they aren't run or something:

   dh_auto_test -a
make -j2 test VERBOSE=1
make[1]: Entering directory '/<>'
XMLLINT not set and xmllint not found in path; skipping xml preprocessing.
XMLLINT not set and xmllint not found in path; skipping xml preprocessing.
XMLLINT not set and xmllint not found in path; skipping xml preprocessing.
make[1]: Nothing to be done for 'test'.

We should at least do a smoke-test (run the interpreter with a "hello
world" program, like I added to mozjs52) to demonstrate that it has some
basic level of functionality.

As for the actual bug, sorry, I have no idea. If there isn't a
likely-looking patch in Firefox or something, we might have to go the
architecture-specific removal route, which would mean no gjs and no
task-gnome-desktop on mips. I don't imagine there are very many GNOME
users on mips...

Are the 32-bit mips ports planned to still be release architectures in
buster? How much effort is it worth putting into them?

Regards,
smcv
--- End Message ---
--- Begin Message ---
Source: mozjs52
Source-Version: 52.3.1-6

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated mozjs52 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: Fri, 20 Oct 2017 09:03:39 -0400
Source: mozjs52
Binary: libmozjs-52-0 libmozjs-52-dev
Architecture: source
Version: 52.3.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 libmozjs-52-0 - SpiderMonkey JavaScript library
 libmozjs-52-dev - SpiderMonkey JavaScript library - development headers
Closes: 878284 878519 878669
Changes:
 mozjs52 (52.3.1-6) unstable; urgency=medium
 .
   [ Adrian Bunk ]
   * Disable ion JIT on mips (Closes: #878519, #878284)
   * Rename Fix-crashes-in-AtomicOperations-none-on-s390x.patch to
 Fix-crashes-in-AtomicOperations-none.patch and modify it to
 always use AtomicOperations-sparc.h instead of AtomicOperations-none.h
   * Add tests-increase-timeout.patch:
 - Set timeout to 600 seconds instead of 300 for slower buildds
   * Stop ignoring test failures on mips
 .
   [ Jeremy Bicha ]
   * Much thanks to Adrian Bunk for all of his help in fixing mozjs
 build problems!
 .
   [ Simon McVittie ]
   * Explicitly select gcc/g++ even if clang is installed, overriding ICU's
 configure.ac (Closes: #878669)
Checksums-Sha1:
 122404ce77429604c224072401accb532c4d94fd 2168 mozjs52_52.3.1-6.dsc
 48f3e8d190531ce43e0d18ff29228a4f849e21a9 70472 

Bug#878284: marked as done (mozjs52: build-time test failure on mips: thousands of TEST-UNEXPECTED-FAIL)

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 13:49:28 +
with message-id 
and subject line Bug#878284: fixed in mozjs52 52.3.1-6
has caused the Debian Bug report #878284,
regarding mozjs52: build-time test failure on mips: thousands of 
TEST-UNEXPECTED-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.)


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

Builds of mozjs52 for several platforms failed with similar errors, as
detailed at
https://buildd.debian.org/status/logs.php?pkg=mozjs52=52.3.1-3 and
excerpted below.

Could you please take a look?

Thanks!

On armel:

File "/<>/js/src/tests/lib/manifest.py", line 143, in 
_parse_one
  if xul_tester.test(cond):
File "/<>/js/src/tests/lib/manifest.py", line 110, in test
  cond, out, err))
  Exception: Failed to test XUL condition 'Android'; output was '', stderr was 
'Assertion failure: !joinable(), at 
/<>/js/src/threading/Thread.h:122\n'

On mips, s390x, and the non-release architectures powerpc and sparc64:

File "/<>/js/src/tests/lib/manifest.py", line 143, in 
_parse_one
  if xul_tester.test(cond):
File "/<>/js/src/tests/lib/manifest.py", line 110, in test
  cond, out, err))
  Exception: Failed to test XUL condition 'Android'; output was '', stderr was 
''

On the non-release architecture ppc64:

File "/<>/js/src/tests/lib/manifest.py", line 134, in 
_parse_one
  if xul_tester.test(cond):
File "/<>/js/src/tests/lib/manifest.py", line 110, in test
  cond, out, err))
  Exception: Failed to test XUL condition '!xulRuntime.shell'; output was '', 
stderr was ''

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

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated mozjs52 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: Fri, 20 Oct 2017 09:03:39 -0400
Source: mozjs52
Binary: libmozjs-52-0 libmozjs-52-dev
Architecture: source
Version: 52.3.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 libmozjs-52-0 - SpiderMonkey JavaScript library
 libmozjs-52-dev - SpiderMonkey JavaScript library - development headers
Closes: 878284 878519 878669
Changes:
 mozjs52 (52.3.1-6) unstable; urgency=medium
 .
   [ Adrian Bunk ]
   * Disable ion JIT on mips (Closes: #878519, #878284)
   * Rename Fix-crashes-in-AtomicOperations-none-on-s390x.patch to
 Fix-crashes-in-AtomicOperations-none.patch and modify it to
 always use AtomicOperations-sparc.h instead of AtomicOperations-none.h
   * Add tests-increase-timeout.patch:
 - Set timeout to 600 seconds instead of 300 for slower buildds
   * Stop ignoring test failures on mips
 .
   [ Jeremy Bicha ]
   * Much thanks to Adrian Bunk for all of his help in fixing mozjs
 build problems!
 .
   [ Simon McVittie ]
   * Explicitly select gcc/g++ even if clang is installed, overriding ICU's
 configure.ac (Closes: #878669)
Checksums-Sha1:
 122404ce77429604c224072401accb532c4d94fd 2168 mozjs52_52.3.1-6.dsc
 48f3e8d190531ce43e0d18ff29228a4f849e21a9 70472 mozjs52_52.3.1-6.debian.tar.xz
 5c23327eec83bd741b02f88e28f121bd30e0e406 7723 mozjs52_52.3.1-6_source.buildinfo
Checksums-Sha256:
 29763431d9431ea939287372816c1fabc415b37de6fe2865f6dbe2e9fc3e2d36 2168 
mozjs52_52.3.1-6.dsc
 d03df55ab64522f9e1ed41108ee6b86116465cc2fdf0ddeed9e5691875e0e689 70472 
mozjs52_52.3.1-6.debian.tar.xz
 

Bug#879123: glee: source for configure is missing

[Simon McVittie]

On Fri, 20 Oct 2017 at 14:36:06 +0200, Markus Koschany wrote:
> If you insist on severity
> serious for such a problem, then bug reports with the same severity
> should be filed against packages
> 
>  a) that do not recreate their build system at build time
>  b) all packages that contain a prebuilt object without corresponding
> source, even when they are not used to build the package, or used at
> runtime (like .dll and .exe files)

I don't think those are the same thing at all, and I think trying to
equate them clouds the issue.

If we have a generated/derived file in source packages, there are three
possibilities:

1. Source code is provided, and we regenerate the generated file from it
   (for example, if the generated file is configure, we have configure.ac
   and we run dh-autoreconf; or if the generated file is a binary,
   we have the C/C++/etc. source code and we recompile it from source).
   For files that we actually use, this is the ideal case, and should
   happen if it's practical to do so (it isn't always).

2. Source code is provided, but we don't rebuild the derived file from
   it (for example, we have configure.ac, but we use the pre-generated
   configure script instead of running autoreconf to regenerate configure;
   or we have source code, but we use a prebuilt binary instead of
   rebuilding it). This is normally considered to be a bug, whose
   severity depends on the circumstances:

   - For prebuilt binary executables, this is usually RC, because we
 usually can't know whether the source actually corresponds to the
 binary, we can't meaningfully audit the binary, we can't fix its
 bugs if it has them, and if we can't audit the binary then we
 shouldn't trust it to be non-malicious.

   - For sort-of-human-readable and sort-of-bug-fixable derived files
 like configure, I think there's consensus that this is a bug, but
 usually not a release-critical one; and sometimes regenerating the
 generated file isn't not practical, so we tolerate that bug because
 the alternative (not shipping the software) would be worse.

3. We don't have the source code from which it was generated. I think
   there's consensus that this isn't DFSG-compliant, because DFSG §2
   says we will ship source code (for packages in main and contrib).
   The definition of source code sometimes gets very subjective, but
   Debian usually borrows the "preferred form for modification" concept
   from the GPL as a working definition of source code, and
   Autoconf-generated configure scripts are rarely that
   (more on that later).

Talking about whether or not dh-autoreconf is run is to do with the
difference between what I've called (1.) and (2.) above. I think
the objection that others are raising in this thread is more about
whether the source code is present *at all*, which is the difference
between (2.) and (3.).

>  a) that do not recreate their build system at build time

That's usually my (2.) above, and I think there is consensus
that this is normally a *non-release-critical* bug. We don't solve all
non-release-critical bugs, and software with non-release-critical bugs
can stay in Debian.

Running dh-autoreconf is best-practice (I wouldn't want to claim that
I can audit a generated configure script for malicious code, but if I
replace it with a re-generated version then I don't have to, so this
appeals to my sense of both responsibility and laziness). However, I
recognise that it isn't always feasible. I don't think any of the
participants in this thread are claiming that not running dh-autoreconf
is a RC bug. IMO it could be anywhere from wishlist to important,
depending on how much pain it's causing for continued maintenance.

>  b) all packages that contain a prebuilt object without corresponding
> source, even when they are not used to build the package, or used at
> runtime (like .dll and .exe files)

That's my (3.) above, and I think there is consensus that it is a
release-critical bug. We remove these objects when we find them.

(If I am wrong about that, then I can stop repacking the Quake series of
game engines to exclude prebuilt Windows DLLs... but I would not want
to do that without approval from the ftp team, and the ftp team seem
highly unlikely to give that approval.)

For a configure script, I agree that the situation is less clear-cut
than for a prebuilt binary object. A derived file can sometimes be *a*
preferred form for modification (for instance if a reasonable person could
be expected to generate a skeleton source file from a template once, but
subsequently edit the generated file and never regenerate it). However,
for Autoconf configure scripts, this would be an exceptional case:
Autoconf configure scripts are rarely modified directly, and much more
commonly re-generated from configure.ac or configure.in.

If there is evidence of the copyright holder treating the generated
configure script as the form to be modified (hand-editing it) 

Processed: Re: Bug#878817 closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: Bug#878817: luajit: Please drop mips64el again)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #878817 {Done: Gianfranco Costamagna } 
[src:luajit] luajit: Please drop mips64el again
Bug reopened
Ignoring request to alter fixed versions of bug #878817 to the same values 
previously set

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

Bug#878817: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: Bug#878817: luajit: Please drop mips64el again)

[Adrian Bunk]

Control: reopen -1

16:20 < jcowgill> bunk, LocutusOfBorg: i have a patch for luajit which fixes 
neovim - i haven't tested it on any other lua code yet 
  though
16:21 < bunk> jcowgill: so that's actually a luajit bug?
16:21 < jcowgill> bunk: yes it's a jit miscompile


cu
Adrian

-- 

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

Bug#878284: marked as pending

[Jeremy Bicha]

tag 878284 pending
thanks

Hello,

Bug #878284 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

https://anonscm.debian.org/cgit/pkg-gnome/mozjs52.git/commit/?id=efe726b

---
commit efe726b86930ae6b3ba3f775c3ee755f67300f5a
Author: Adrian Bunk 
Date:   Fri Oct 20 08:51:54 2017 -0400

Stop ignoring test failures on mips

Closes: #878284

diff --git a/debian/changelog b/debian/changelog
index ed5bab6..4bc89f0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -13,6 +13,7 @@ mozjs52 (52.3.1-6) UNRELEASED; urgency=medium
 always use AtomicOperations-sparc.h instead of AtomicOperations-none.h
   * Add tests-increase-timeout.patch:
 - Set timeout to 600 seconds instead of 300 for slower buildds
+  * Stop ignoring test failures on mips (Closes: #878284)
 
  -- Simon McVittie   Sun, 15 Oct 2017 11:34:57 +0100
 

Processed: Bug#878284 marked as pending

[Debian Bug Tracking System]

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

> tag 878284 pending
Bug #878284 [src:mozjs52] mozjs52: build-time test failure on mips: thousands 
of TEST-UNEXPECTED-FAIL
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#878817: marked as done (luajit: Please drop mips64el again)

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 14:48:37 +0200
with message-id <727a677a-793a-ea23-0381-4304ad13b...@debian.org>
and subject line Re: Bug#878817: luajit: Please drop mips64el again
has caused the Debian Bug report #878817,
regarding luajit: Please drop mips64el again
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.)


-- 
878817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: luajit
Version: 2.1.0~beta3+dfsg-5
Severity: serious
Control: affects -1 src:neovim src:knot-resolver

neovim and knot-resolver FTBFS with luajit 2.1.0~beta3+dfsg-5:
https://buildd.debian.org/status/logs.php?pkg=neovim=mips64el
https://buildd.debian.org/status/logs.php?pkg=knot-resolver=mips64el

knot-resolver FTBFS on the buildd, but builds for me on eller.

21:10 < jcowgill> bunk: not sure, but i notice both failed on loongsons
21:10 < jcowgill> gcc has a few workarounds disabling some instructions since 
loongson doesn't quite implement the mips isa properly
21:14 < bunk> jcowgill: that sounds like possibly related to a jit failing on 
this hw

Instead of shipping code that is strongly suspected to be nonworking
on part of the supported hardware of mips64el, it is IMHO better to
disable luajit on mips64el again.
--- End Message ---
--- Begin Message ---
On Wed, 18 Oct 2017 10:23:12 +0100 James Cowgill  wrote:
> Control: affects -1 - src:knot-resolver
> 
> Hi,
> 
> On 16/10/17 21:23, Adrian Bunk wrote:
> > Source: luajit
> > Version: 2.1.0~beta3+dfsg-5
> > Severity: serious
> > Control: affects -1 src:neovim src:knot-resolver
> > 
> > neovim and knot-resolver FTBFS with luajit 2.1.0~beta3+dfsg-5:
> > https://buildd.debian.org/status/logs.php?pkg=neovim=mips64el
> > https://buildd.debian.org/status/logs.php?pkg=knot-resolver=mips64el
> > 
> > knot-resolver FTBFS on the buildd, but builds for me on eller.
> > 
> > 21:10 < jcowgill> bunk: not sure, but i notice both failed on loongsons
> > 21:10 < jcowgill> gcc has a few workarounds disabling some instructions 
> > since loongson doesn't quite implement the mips isa properly
> > 21:14 < bunk> jcowgill: that sounds like possibly related to a jit failing 
> > on this hw
> > 
> > Instead of shipping code that is strongly suspected to be nonworking
> > on part of the supported hardware of mips64el, it is IMHO better to
> > disable luajit on mips64el again.
> 
> It turns out the knot-resolver build failure had nothing to do with
> luajit (see #878976). I haven't investigated the neovim failure
> thoroughly yet.

Since there are workarounds (e.g. not enabling lua on mips64el and one of the 
two failures is unrelated)

and also, neovim seems to build on a mips64el dchroot, I think closing this one 
is the right thing to do

G.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#879123: glee: source for configure is missing

[Markus Koschany]

Am 20.10.2017 um 06:42 schrieb Helmut Grohne:
> On Thu, Oct 19, 2017 at 10:52:41PM +0200, Markus Koschany wrote:
>> I am quoting:
>>
>> https://sources.debian.net/src/glee/5.4.0-2/configure/
>>
>> The license is very liberal. You can argue that it should be mentioned
>> in debian/copyright but that does not make the file non-free or
>> unsuitable for Debian main.
> 
> The license is a lie. It is clear that there is some source file that
> was used to generate configure. Thus configure is a derivative work of
> that file. As Adrian pointed out, very likely the FSF isn't the
> copyright holder for that source file and very likely this permissive
> "you can do anything" license does not apply to the source file.

How do you determine that this license is a "lie" without contacting the
copyright holder or upstream? Even without this information we can
faithfully assume that the FSF as the copyright holder of GNU Autoconf
are aware of any potential licensing issues with their software. They
have even created the "Autoconf Configure Script Exception". [1] Simply
put the upstream developer of glee is allowed to integrate this
configure script in any way he sees fit.

This is not a license issue.

> Saying that a generated configure script is free software is kinda
> stupid. The essence of free software is to provide users with the
> ability to modify it and this freedom is lost when all they have is the
> generated file.

It is stupid to say that you are unable to make modifications to the
package when you were the one who discovered that you don't even need
this file to build the package. How does the mere existence of a text
file impair your freedom in this case?

> 
>> This is not true. The configure file is human readable and the preferred
>> source of modification in this case. Please also note that the author of
>> glee licensed his work under the more liberal BSD-2-clause license. You
>> cannot compare two very distinct issues like minified JS files and
>> automake files and claim consensus has been reached already.
> 
> I have worked with *lots* of configure scripts and I can say that I
> never preferred modifying the generated script. Since configure scripts
> don't have reasonable indentation, the program structure is completely
> lost. Looking at them feels a lot like reading a binary disassembly. I
> contend that "human readable" is not a reasonable assessment either.
> 
>> Again quoted out of context and not relevant in this case. The source is
>> the configure script. Period. Please feel free to discuss this on
>> debian-devel or move it to the CTTE. I am willing to oppose this
>> nonsense and harmful misinterpretation of Debian's Policy whenever and
>> wherever I can.
> 
> If you insist on disucssing this in a larger scope, chances are a ftp
> master will notice and remove glee from stable (given Ximin's findings)
> as it is not clear whether glee is distributable at all.
> 
> Do you realize that my original motivation in reporting this bug was
> that I found a build issue with glee and wanted to write a patch? The
> absence of source makes that difficult and makes DFSG#3 rather
> theoretical. Why does DFGS#3 assure a "right to modify" when
> modification is often impratical? I start to wonder whether we should
> start a GR to clarify DFSG#3 that modification should be practical.
> 
> Helmut

I don't understand your technical problems at the moment. But I
understand that you have filed a serious bug against glee with the
justification that the configure script is not source. I have worked
with even more configure scripts and I also prefer modifying something
else. That does not mean it is not possible. I had to patch countless
configure files directly because dh-autoreconf or other means did not
work for me. Does that mean those packages have release critical bugs
now? I am not only disagreeing with you, I can prove you wrong. When I
can modify a configure file, you should be able to do it too.

Looking forward: I appreciate if you work on glee. If you remove the
file in this process and create your own build system, so be it. However
I cannot accept the severity and justification of this bug without
seeing the bigger picture because glee is not the only package which
contains such a file. There are packages which cannot recreate this file
out-of-the-box right now. If this is an RC bug, then all other affected
packages which are not auto-reconfigured at build time are RC too. That
would definitely need a clarification on debian-devel. I dispute your
assessment that shipping this file is a violation of DFSG 3 because

 a) the license grants you all the required freedoms. It is free
software.
 b) the file is sufficiently modifiable but not needed at all for
building the package

In consequence this is a minor issue at best. If you insist on severity
serious for such a problem, then bug reports with the same severity
should be filed against packages

 a) that do not recreate their build 

Bug#878999: protobuf FTBFS on armhf/i386: testMergeFrom (google.protobuf.internal.message_test.Proto3Test) ... Segmentation fault

[Mattia Rizzolo]

On Wed, Oct 18, 2017 at 01:09:59PM +0300, Adrian Bunk wrote:
> testMapIterationClearMessage 
> (google.protobuf.internal.message_test.Proto3Test) ... ok
> testMapValidAfterFieldCleared 
> (google.protobuf.internal.message_test.Proto3Test) ... ok
> testMapsAreMapping (google.protobuf.internal.message_test.Proto3Test) ... ok
> testMergeFrom (google.protobuf.internal.message_test.Proto3Test) ... 
> Segmentation fault
> debian/rules:74: recipe for target 'override_dh_auto_test-arch' failed
> make[1]: *** [override_dh_auto_test-arch] Error 139


I couldn't reproduce it on abel.d.o, where I can reliably run the test
(attached the log of
for i in $(seq 1 100) ; do
figlet $i
python3.6 setup.py test --cpp_implementation -s 
google.protobuf.internal.message_test.Proto3Test.testMergeFrom || break
done | tee -a ~/test.log
as run on abel after a successful build.

-- 
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  `-
 _ 
/ |
| |
| |
|_|
   
running test
running egg_info
writing protobuf.egg-info/PKG-INFO
writing dependency_links to protobuf.egg-info/dependency_links.txt
writing namespace_packages to protobuf.egg-info/namespace_packages.txt
writing requirements to protobuf.egg-info/requires.txt
writing top-level names to protobuf.egg-info/top_level.txt
reading manifest file 'protobuf.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'protobuf.egg-info/SOURCES.txt'
running build_ext
copying 
build/lib.linux-armv7l-3.6/google/protobuf/pyext/_message.cpython-36m-arm-linux-gnueabihf.so
 -> google/protobuf/pyext
copying 
build/lib.linux-armv7l-3.6/google/protobuf/internal/_api_implementation.cpython-36m-arm-linux-gnueabihf.so
 -> google/protobuf/internal
   
|___ \ 
  __) |
 / __/ 
|_|
   
running test
running egg_info
writing protobuf.egg-info/PKG-INFO
writing dependency_links to protobuf.egg-info/dependency_links.txt
writing namespace_packages to protobuf.egg-info/namespace_packages.txt
writing requirements to protobuf.egg-info/requires.txt
writing top-level names to protobuf.egg-info/top_level.txt
reading manifest file 'protobuf.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'protobuf.egg-info/SOURCES.txt'
running build_ext
copying 
build/lib.linux-armv7l-3.6/google/protobuf/pyext/_message.cpython-36m-arm-linux-gnueabihf.so
 -> google/protobuf/pyext
copying 
build/lib.linux-armv7l-3.6/google/protobuf/internal/_api_implementation.cpython-36m-arm-linux-gnueabihf.so
 -> google/protobuf/internal
 _ 
|___ / 
  |_ \ 
 ___) |
|/ 
   
running test
running egg_info
writing protobuf.egg-info/PKG-INFO
writing dependency_links to protobuf.egg-info/dependency_links.txt
writing namespace_packages to protobuf.egg-info/namespace_packages.txt
writing requirements to protobuf.egg-info/requires.txt
writing top-level names to protobuf.egg-info/top_level.txt
reading manifest file 'protobuf.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'protobuf.egg-info/SOURCES.txt'
running build_ext
copying 
build/lib.linux-armv7l-3.6/google/protobuf/pyext/_message.cpython-36m-arm-linux-gnueabihf.so
 -> google/protobuf/pyext
copying 
build/lib.linux-armv7l-3.6/google/protobuf/internal/_api_implementation.cpython-36m-arm-linux-gnueabihf.so
 -> google/protobuf/internal
 _  _   
| || |  
| || |_ 
|__   _|
   |_|  

running test
running egg_info
writing protobuf.egg-info/PKG-INFO
writing dependency_links to protobuf.egg-info/dependency_links.txt
writing namespace_packages to protobuf.egg-info/namespace_packages.txt
writing requirements to protobuf.egg-info/requires.txt
writing top-level names to protobuf.egg-info/top_level.txt
reading manifest file 'protobuf.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'protobuf.egg-info/SOURCES.txt'
running build_ext
copying 
build/lib.linux-armv7l-3.6/google/protobuf/pyext/_message.cpython-36m-arm-linux-gnueabihf.so
 -> google/protobuf/pyext
copying 
build/lib.linux-armv7l-3.6/google/protobuf/internal/_api_implementation.cpython-36m-arm-linux-gnueabihf.so
 -> google/protobuf/internal
   
| ___| 
|___ \ 
 ___) |
|/ 
   
running test
running egg_info
writing protobuf.egg-info/PKG-INFO
writing dependency_links to protobuf.egg-info/dependency_links.txt
writing namespace_packages to protobuf.egg-info/namespace_packages.txt
writing requirements to protobuf.egg-info/requires.txt
writing top-level names to protobuf.egg-info/top_level.txt
reading manifest file 'protobuf.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'protobuf.egg-info/SOURCES.txt'
running build_ext
copying 

Bug#879190: musl FTBFS on armel: Error: selected processor does not support clz

[Adrian Bunk]

Source: musl
Version: 1.1.17-1
Severity: serious
Tags: patch

https://buildd.debian.org/status/fetch.php?pkg=musl=armel=1.1.17-1=1508450839=0

...
{standard input}: Assembler messages:
{standard input}:625: Error: selected processor does not support `clz r0,r9' in 
ARM mode
{standard input}:953: Error: selected processor does not support `clz r3,r7' in 
ARM mode
{standard input}:1010: Error: selected processor does not support `clz r3,r6' 
in ARM mode
{standard input}:1148: Error: selected processor does not support `clz r0,r3' 
in ARM mode
Makefile:164: recipe for target 'obj/src/math/fma.lo' failed
make[1]: *** [obj/src/math/fma.lo] Error 1


Fix is attached.
Description: CLZ is only available with ARM >= 5
Author: Adrian Bunk 

--- musl-1.1.17.orig/arch/arm/atomic_arch.h
+++ musl-1.1.17/arch/arm/atomic_arch.h
@@ -82,9 +82,13 @@ static inline void a_crash()
: : : "memory");
 }
 
+#if __ARM_ARCH >= 5
+
 #define a_clz_32 a_clz_32
 static inline int a_clz_32(uint32_t x)
 {
__asm__ ("clz %0, %1" : "=r"(x) : "r"(x));
return x;
 }
+
+#endif

Bug#533009: marked as done (lib32ffi5: /emul/ia32-linux deprecated)

[Debian Bug Tracking System]

Your message dated Fri, 20 Oct 2017 09:42:13 +0200
with message-id <606321d4-cac7-fee9-f82a-fb3bdc0c2...@debian.org>
and subject line closing libffi emul32 issue
has caused the Debian Bug report #533009,
regarding lib32ffi5: /emul/ia32-linux deprecated
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.)


-- 
533009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lib32ffi5
Version: 3.0.7-1

On amd64, files in /emul/ia32-linux should be moved to /usr/lib32.


--- End Message ---
--- Begin Message ---
Version: 3.2.1-6

closing this, not an issue anymore in stable, testing and unstable.--- End Message ---

Bug#879185: sane-backends FTBFS with debhelper 10.9.2

[Adrian Bunk]

Source: sane-backends
Version: 1.0.25-4.1
Severity: serious
Tags: buster sid

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

...
   debian/rules override_dh_systemd_enable-arch
make[1]: Entering directory '/build/1st/sane-backends-1.0.25'
dh_systemd_enable --no-enable saned.socket
dh_systemd_enable: Could not find "saned.socket" in the /lib/systemd/system 
directory of libsane. This could be a typo, or using Also= with a service file 
from another package. Please check carefully that this message is harmless.
dh_systemd_enable: Cannot open(saned.socket) to check for [Install]
debian/rules:134: recipe for target 'override_dh_systemd_enable-arch' failed
make[1]: *** [override_dh_systemd_enable-arch] Error 2